Related
AT&T version of this thread: http://forum.xda-developers.com/showthread.php?p=47413669
Started with N900AUCUBMI9, rooted via RDLV (N900AUCUBMI9_OneClickBin)
accepted OTA update (i know) to N900AUCUBMJ5, lost root
Wanted root back, attempted RDLV again, got SECURE CHECK FAIL : cache, stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Found this thread: http://forum.xda-developers.com/showthread.php?p=47411605
Flashed PIT ONLY, successfully booted up into MJ5, unrooted. Should have left it alone there. KNOX flag 0x0
Wanted root back, thought I could downgrade BL, AP/PDA, Phone, CPC to MI9 as suggested in above thread.
BL fails with SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1. AP/PDA, fails with SECURE CHECK FAIL : system. Phone successfully flashed to MI9. CPC fails with SECURE CHECK FAIL : cache
Stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Flashed PIT again, phone tries to boot but "Process system isn't responding" after AT&T globe boot animation, then reboots
Attempted RDLV again, get SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1, presumably because the MI9 BL can't be flashed over the MJ5 BL.
I'm stuck folks. Any suggestions welcome. Am I just going to have to wait for a stock MJ5 package/files similar to the MI9 files in the thread above?
For those reading who were dummies like me and accepted the OTA update, lost their root, tried to re-root with RDLV: flash the PIT file ONLY from the above link and you should be back into MJ5, un-rooted.
Help please?
Well lets see here. I was rooted (Kingo) <Updated ver.
I saw the update.
Un-rooted with the SuperSU app.
Did the update
Re-rooted with Kingo.
Re-did all xposed/winam stuff.
Rebooted
Phone is on new firmware with root and I'm loving it.
The End.
LuckyColdJohnson said:
Well lets see here. I was rooted (Kingo) <Updated ver.
I saw the update.
Un-rooted with the SuperSU app.
Did the update
Re-rooted with Kingo.
Re-did all xposed/winam stuff.
Rebooted
Phone is on new firmware with root and I'm loving it.
The End.
Click to expand...
Click to collapse
yes, that's the way i should have done it (SU persist, un-root, OTA, SU root) but I didn't and now here i am.
I followed the info to flash PIT only and my phone rebooted. Now fc's allot of stuff. Can't get past it. Build number mi9, baseband mj5. Do you think someone will make an mj5 odin? Or any advice would be greatly appreciated.
Same here
Same situation here ;_; can you post just the Pit? the zip is taking forever for the fact that I just need an XML file.
ditto
+1 I was updated and rooted and decided to jack around with a data toggle in notification (/data/data/com.android.providers.settings/databases/settings.db) and here i am
So I flashed the .pit
which let me reboot.
However now I'm in a horrible limbo state where pen imput crashes in an infanite loop making anything on the phone painful to do.
I think it's because my PDA and CSC are MI9 but my phone updated to MJ5.
I tried recovery mode wipe and "reset Phone" in settings and the issues persist.
This lovely mismatch has also rendered my ability to install firmware via Kies imposible. Nulling my plan to just roll back to stock.
Anybody have an odin one click for MJ5? I'd rather be stock than inoperable.
I'm afraid to try the method listed above for Knox flag reasons. If rolling back to MI9 is unreliable and might throw flags.
Hope someone else gets further than I have soon.
LuckyColdJohnson said:
Well lets see here. I was rooted (Kingo) <Updated ver.
I saw the update.
Un-rooted with the SuperSU app.
Did the update
Re-rooted with Kingo.
Re-did all xposed/winam stuff.
Rebooted
Phone is on new firmware with root and I'm loving it.
The End.
Click to expand...
Click to collapse
Where is this kingo?
Sent from the phone with the best specs on the market, "NoTe III"
mnorris0678 said:
+1 I was updated and rooted and decided to jack around with a data toggle in notification (/data/data/com.android.providers.settings/databases/settings.db) and here i am
Click to expand...
Click to collapse
I soft bricked my phone probably 5 or 6 times before getting it to work!
Sent from my SAMSUNG-SM-N900A using Tapatalk
tyiphius said:
I soft bricked my phone probably 5 or 6 times before getting it to work!
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Would you do us a solid, and elaborate on how you fixed it?
bloodyRevolver said:
I'm afraid to try the method listed above for Knox flag reasons. If rolling back to MI9 is unreliable and might throw flags.
Hope someone else gets further than I have soon.
Click to expand...
Click to collapse
FYI, nothing that I have domes so far has tripped KONX. Still at 0x0
bloodyRevolver said:
Would you do us a solid, and elaborate on how you fixed it?
Click to expand...
Click to collapse
+1
Sweet. Your OP lead me to believe that you tripped it somewhere. Honestly I'm beginning to care less and less about it. I honestly think that with a full ODIN of the current OTA WE'd be back in the clear. The inability to roll back after The thing updated without my permission is frustrating to say the least. Coming from iOS I'm also a bit surprised by the lack of OEM firmware existing in the wild.
settings.db
Might anybody have a stock unmodified /data/data/com.android.providers.settings/databases/settings.db file that i can try loading with adb?
Resolved issue with at&t.
Couldn't handle waiting for SM-N900A stock firmware so I took my phone to AT&T retail store (I didn't have warranty with them). They referred me to At&t Device support center and told me that I have a manufacture warranty with samsung for 1 year and since i didn't have any water damage or such, just a boot loop, i can just exchange it for a "like-new" product and might ship between 6 business days.
nikeflight19 said:
Couldn't handle waiting for SM-N900A stock firmware so I took my phone to AT&T retail store (I didn't have warranty with them). They referred me to At&t Device support center and told me that I have a manufacture warranty with samsung for 1 year and since i didn't have any water damage or such, just a boot loop, i can just exchange it for a "like-new" product and might ship between 6 business days.
Click to expand...
Click to collapse
I was offered the same deal. Preferred to hold out hope that we'd get an MJ5 firmware ripped and running before that.
Where can I find this pit file?
WHERE CAN i FIND THE PIT FILE
hunterdg said:
AT&T version of this thread: http://forum.xda-developers.com/showthread.php?p=47413669
Started with N900AUCUBMI9, rooted via RDLV (N900AUCUBMI9_OneClickBin)
accepted OTA update (i know) to N900AUCUBMJ5, lost root
Wanted root back, attempted RDLV again, got SECURE CHECK FAIL : cache, stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Found this thread: http://forum.xda-developers.com/showthread.php?p=47411605
Flashed PIT ONLY, successfully booted up into MJ5, unrooted. Should have left it alone there. KNOX flag 0x0
Wanted root back, thought I could downgrade BL, AP/PDA, Phone, CPC to MI9 as suggested in above thread.
BL fails with SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1. AP/PDA, fails with SECURE CHECK FAIL : system. Phone successfully flashed to MI9. CPC fails with SECURE CHECK FAIL : cache
Stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Flashed PIT again, phone tries to boot but "Process system isn't responding" after AT&T globe boot animation, then reboots
Attempted RDLV again, get SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1, presumably because the MI9 BL can't be flashed over the MJ5 BL.
I'm stuck folks. Any suggestions welcome. Am I just going to have to wait for a stock MJ5 package/files similar to the MI9 files in the thread above?
For those reading who were dummies like me and accepted the OTA update, lost their root, tried to re-root with RDLV: flash the PIT file ONLY from the above link and you should be back into MJ5, un-rooted.
Help please?
Click to expand...
Click to collapse
nabooki said:
WHERE CAN i FIND THE PIT FILE
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2502049
First page of the second link you posted. It's in the zip with all the other MI9 files. If you look further down the thread he also posted another version of the PIT. Read read read read.
Hello all.. Been gone for a bit. Catching up now and hoping for a solution but if anyone has figured this out, please let me know how or provide a link! (Mj5 Odin stock recovery)
So I bought this i537 used a while back, the previous owned never registered it with samsung but I did when I bought it so I do have a warranty on it. I know it was previously rooted then unrooted before I bought it but I don't know if it ever had a custom rom on it. I rooted the phone with activeroot (still on 4.2.2 stock rom) and have since unrooted it with superSU.
I am having problems with the touchscreen and samsung has confirmed warranty coverage and gave me a shipping label but I want to be totally sure it a-ok before I send it in.
When I boot into odin mode there is no KNOX status, is that normal for this device? Did 4.2.2 not come with knox on this device?
Also the status says custom? When the phone WAS rooted it said official ??? seems bass ackwards.
Also, I would like to reload stock 4.2.2 via ODIN just to make sure everything is kosher before sending it it, would this void my warranty?
My phone is also sim unlocked, i imagine this is okay as far as warranty goes? Would reflashing with ODIN break my sim unlock?
Thanks so much!
CaseyR22 said:
So I bought this i537 used a while back, the previous owned never registered it with samsung but I did when I bought it so I do have a warranty on it. I know it was previously rooted then unrooted before I bought it but I don't know if it ever had a custom rom on it. I have rooted the phone with activeroot (still on 4.2.2 stock rom).
When I boot into odin mode there is no KNOX status, is that normal for this device? Did 4.2.2 not come with knox on this device?
Also, I would like to reload stock 4.2.2 via ODIN just to make sure everything is kosher before sending it it, would this void my warranty?
My phone is also sim unlocked, i imagine this is okay as far as warranty goes? Would reflashing with ODIN break my sim unlock?
Thanks so much!
Click to expand...
Click to collapse
Let's start from the top:
This phone came with MF2 (4.2.2), which was then immediately updated to MF3 (4.2.2). Both of these versions came with Knox enabled. If he just rooted then he probably didn't trip the Knox flag, but there could have been other things he did or tried to do that did trip the flag.
If it is indeed the i537, I can guarantee he did not flash a custom ROM. The i537 has a locked bootloader which means no custom recovery and no custom ROMs. However there is the ability to use TouchWiz-based ROMs, if you want to learn more about this and how it works read about SafeStrap.
We do not have official 4.2.2 stock firmware available to flash. We have a pre-release of 4.2.2, a pre-release of 4.3, official 4.3, and an OTA to go from 4.3 to 4.4.2. You can read more about the different firmwares in the i537 Firmware Thread.
Flashing firmware with Odin will erase your SIM unlock, but you can either enter the unlock code again or there are other methods that can be used. I'm not familiar with SIM unlocking so you'll have to do a little searching.
You never mentioned what you're sending the phone in for. I would try flashing the MF1 firmware first to see if it's a software issue. If it's a hardware issue then unfortunately you'll have to send it in.
Devo7v said:
Let's start from the top:
This phone came with MF2 (4.2.2), which was then immediately updated to MF3 (4.2.2). Both of these versions came with Knox enabled. If he just rooted then he probably didn't trip the Knox flag, but there could have been other things he did or tried to do that did trip the flag.
If it is indeed the i537, I can guarantee he did not flash a custom ROM. The i537 has a locked bootloader which means no custom recovery and no custom ROMs. However there is the ability to use TouchWiz-based ROMs, if you want to learn more about this and how it works read about SafeStrap.
We do not have official 4.2.2 stock firmware available to flash. We have a pre-release of 4.2.2, a pre-release of 4.3, official 4.3, and an OTA to go from 4.3 to 4.4.2. You can read more about the different firmwares in the i537 Firmware Thread.
Flashing firmware with Odin will erase your SIM unlock, but you can either enter the unlock code again or there are other methods that can be used. I'm not familiar with SIM unlocking so you'll have to do a little searching.
You never mentioned what you're sending the phone in for. I would try flashing the MF1 firmware first to see if it's a software issue. If it's a hardware issue then unfortunately you'll have to send it in.
Click to expand...
Click to collapse
Thank you for the quick response. I edited the first post to add more details but you must've already quoted me before I hit send.
Basically the problem is the screen will randomly detect 1, 3 or 5 nonexistent touches across the center of the screen (confirmed by enabling "show touches" in the developer options). While this is happening the touchscreen becomes unusable, rebooting several times will eventually fix it but the problem comes back randomly, sometime within a couple minutes and sometimes after several hours.
I did confirm my device is running MF3 and it is absolutely a i537. I'm using the phone on straight talk not ATT so I have not received any OTA updates beyond this point.
So,anyhow I understand I can fix the device status:custom with triangleaway but I don't understand why there is no KNOX counter in ODIN mode and how this may effect my warranty.
Also, if I did ODIN to 4.3 or 4.4 would this trip the knox counter? (Assuming it isnt tripped already).
Thanks for your input, truly appreciated!
CaseyR22 said:
Thank you for the quick response. I edited the first post to add more details but you must've already quoted me before I hit send.
Basically the problem is the screen will randomly detect 1, 3 or 5 nonexistent touches across the center of the screen (confirmed by enabling "show touches" in the developer options). While this is happening the touchscreen becomes unusable, rebooting several times will eventually fix it but the problem comes back randomly, sometime within a couple minutes and sometimes after several hours.
I did confirm my device is running MF3 and it is absolutely a i537. I'm using the phone on straight talk not ATT so I have not received any OTA updates beyond this point.
So,anyhow I understand I can fix the device status:custom with triangleaway but I don't understand why there is no KNOX counter in ODIN mode and how this may effect my warranty.
Also, if I did ODIN to 4.3 or 4.4 would this trip the knox counter? (Assuming it isnt tripped already).
Thanks for your input, truly appreciated!
Click to expand...
Click to collapse
It sounds like it might be a software issue so it would be worth it to try to flash the official 4.3 firmware. Flashing official firmware shouldn't trip the Know flag, but I'm not really an expert on Knox. I have read that Knox being tripped doesn't affect warranty repairs.
Devo7v said:
It sounds like it might be a software issue so it would be worth it to try to flash the official 4.3 firmware. Flashing official firmware shouldn't trip the Know flag, but I'm not really an expert on Knox. I have read that Knox being tripped doesn't affect warranty repairs.
Click to expand...
Click to collapse
Thanks, I went ahead and flashed 4.3 via ODIN and the KNOX status is showing 0x0 so that is a good sign. Has only been about a half hour so I cant say whether or not the touchscreen issue is fixed yet but I will post back and update what happens after a day or so.
Another plus is the update finally got rid of that god awful default font on 4.2 (changing the system font wouldn't change the fontface for plain text in the browser).
Quick update in case anyone is having a similar problem with "phantom touches" in the future.
After flashing to 4.3 the touchscreen problems have continued so i do believe it is a hardware problem that will require disassembly to fix.
Also the phone keeps trying to download the OTA update to 4.4 but I've heard bad things about the update so far so I've left my wifi turned off.
Going to be stuck using a windows 8 phone for a week or while my phone is out for warranty repair.
There is an app in the play store called phone info. There it tells you your knox status without root or being in download mode.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
One final update in case anybody runs into similar problems in the future. Samsung confirmed it was a hardware problem and fixed the phone 100% free of charge under warranty.
It appears they replaced everything which is pretty awesome because I now have a brand new digitizer and bezel without a single scratch or scuff on them. Also my usb port cover flap was feeling pretty worn/sloppy so now thats new and even the USB port itself looks brand new which tells me the motherboard was replaced. I can tell they peeled the old serial/IMEI sticker off the old phone and stuck it on this one.
Surprisingly they didn't update it to 4.4 while it was there which kind of sucks because I'm nervous about doing it myself after reading horror stories on the forums.
Anyway I'm very pleased with Samsung's support!
Well actually it seems fairly straighfoward to go back to stock, if you have the appropriate stock image to flash with Odin. I'm just used to do the whole "unlock bootloader, flash recovery, flash autoroot/rom/whatever" process on other devices and it feels weird to just load up Odin and do everyhing. So that's an insecurity.
I'm more interested in knowing whether Samsung "knows" that you rooted/unlocked the device, for warranty reasons. If sometime I decide to go back to full stock and at some point I need to return/send the device for some service, I want to know if they can tell whether the device had been previously rooted. On my motorola xt1092 unlocking the bootloader requires some sort of code from Moto itself, so even if you go back totally stock you can't get rid of the "unlocked bootloader" msg, let alone that they have you already registered on their system as having non-valid warranty.
YES. Atm there is no root method that won't trip knox and if knox is 0x1 samsung will always know. Some providers don't care about that and will fix ur phone/tablet. Especially if it don't even boot or some mechanic problem, just flash stock firmware with odin. My personally was very insecure when flashed firmware 5.1.1 then kernel and then root with odin (always used TWRP on S4) but all worked ok, just read the guide, real all post and all will be ok. If u wan't then go go stock just flash the same stock firmware and you will have it stock with no root stock recovery but knox will be 0x1
mk89pwnz said:
YES. Atm there is no root method that won't trip knox and if knox is 0x1 samsung will always know. Some providers don't care about that and will fix ur phone/tablet. Especially if it don't even boot or some mechanic problem, just flash stock firmware with odin. My personally was very insecure when flashed firmware 5.1.1 then kernel and then root with odin (always used TWRP on S4) but all worked ok, just read the guide, real all post and all will be ok. If u wan't then go go stock just flash the same stock firmware and you will have it stock with no root stock recovery but knox will be 0x1
Click to expand...
Click to collapse
Thanks for the info! I found out there was a piece of software called "Triangle Away" which helped reset counter to 0x0 when going back to full stock, but i can't find out if it would work on the Tab S2... http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
kokotron said:
Thanks for the info! I found out there was a piece of software called "Triangle Away" which helped reset counter to 0x0 when going back to full stock, but i can't find out if it would work on the Tab S2... http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
Click to expand...
Click to collapse
It was flash counter not knox. Knox is literally impossible to reset. Triangle Away only works on older devices. List can be found here: http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
mk89pwnz said:
YES. Atm there is no root method that won't trip knox and if knox is 0x1 samsung will always know. Some providers don't care about that and will fix ur phone/tablet. Especially if it don't even boot or some mechanic problem, just flash stock firmware with odin. My personally was very insecure when flashed firmware 5.1.1 then kernel and then root with odin (always used TWRP on S4) but all worked ok, just read the guide, real all post and all will be ok. If u wan't then go go stock just flash the same stock firmware and you will have it stock with no root stock recovery but knox will be 0x1
Click to expand...
Click to collapse
Just to reconfirm that, since I was also a little concerned about that (I have a T810 btw, not a T815): While the stock firmware on my device works 'well enough', there are certain things i'd rather it was able to do. Knox however has me holding off (at least until the warranty expires). Does the same apply to the T810? (There is no root method that won't trip knox.)
ATM no. The only way to root Tab s2 is to trip Knox. King root will root your device with no Knox tripping but it will last until you reboot
Been on Xtrestolite for months now and at first it was great, but the battery drains quickly now, can't answer phone calls and fast charging doesn't work (works on other devices).
Basically, I want to use this thread to go back to stock: http://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387
The MM update for T-mobile is coming out soon so I am interested in the stock version of that (so my phone calls work).
My question is basically that I updated the modem and the bootloader to the Xrestolite ROM and the ROM thinks my phone is an S6 edge (just a regular S6).
If I use ODIN to flash stock on my device, does it also flash the stock modem and bootloader for my cell phone provider as well? (USA T-Mo.)
Are there any additional steps I need to do to go back to the stock modem/bootloader/anything else? Will I be able to update to MM OTA?
darklime said:
Been on Xtrestolite for months now and at first it was great, but the battery drains quickly now, can't answer phone calls and fast charging doesn't work (works on other devices).
Basically, I want to use this thread to go back to stock: http://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387
The MM update for T-mobile is coming out soon so I am interested in the stock version of that (so my phone calls work).
My question is basically that I updated the modem and the bootloader to the Xrestolite ROM and the ROM thinks my phone is an S6 edge (just a regular S6).
If I use ODIN to flash stock on my device, does it also flash the stock modem and bootloader for my cell phone provider as well? (USA T-Mo.)
Are there any additional steps I need to do to go back to the stock modem/bootloader/anything else? Will I be able to update to MM OTA?
Click to expand...
Click to collapse
You can restore original firmware using Samsung Kies or Smartswitch.
cwhiatt said:
You can restore original firmware using Samsung Kies or Smartswitch.
Click to expand...
Click to collapse
I plan on using ODIN to flash the original firmware. Does the original firmware include the original bootloader and modem or do I have to do those separately?
darklime said:
I plan on using ODIN to flash the original firmware. Does the original firmware include the original bootloader and modem or do I have to do those separately?
Click to expand...
Click to collapse
I have no idea. I always restored via Kies.
darklime said:
I plan on using ODIN to flash the original firmware. Does the original firmware include the original bootloader and modem or do I have to do those separately?
Click to expand...
Click to collapse
The full stock firmware package will have bootloader and modem. It will take you to basically like you just bought it except Knox will stay tripped.
Sym_Link said:
The full stock firmware package will have bootloader and modem. It will take you to basically like you just bought it except Knox will stay tripped.
Click to expand...
Click to collapse
Thanks for the reply! Since knox is tripped, will I be able to do OTA updates or download apps like Samsung Pay or Android Pay? I heard there is a method like using the app called "Triangle Away" to remove the knox tripped counter.
darklime said:
Thanks for the reply! Since knox is tripped, will I be able to do OTA updates or download apps like Samsung Pay or Android Pay? I heard there is a method like using the app called "Triangle Away" to remove the knox tripped counter.
Click to expand...
Click to collapse
You will be able to get OTA update with tripped knox if fully stock. Samsung Pay will not work if knox is tripped. Android Pay will work if not rooted( it will also work with systemless root and a couple changes to su file but then you are no longer stock and no OTA). There is currently no way of resetting knox short of replacing phone.
s89281b said:
You will be able to get OTA update with tripped knox if fully stock. Samsung Pay will not work if knox is tripped. Android Pay will work if not rooted( it will also work with systemless root and a couple changes to su file but then you are no longer stock and no OTA). There is currently no way of resetting knox short of replacing phone.
Click to expand...
Click to collapse
I'm going to try to use triangle away as an attempt to reset knox. Should I flash the stock firmware first then try Triangle away or vice-versa?
darklime said:
I'm going to try to use triangle away as an attempt to reset knox. Should I flash the stock firmware first then try Triangle away or vice-versa?
Click to expand...
Click to collapse
S6 is not listed as a supported device for triangle away. I would not waste my money trying it. Just flash stock firmware. Only loss is Samsung pay.
s89281b said:
S6 is not listed as a supported device for triangle away. I would not waste my money trying it. Just flash stock firmware. Only loss is Samsung pay.
Click to expand...
Click to collapse
That sucks. I really wanted to try it out. MM is coming out for my S6 in my country soon so I'm hoping battery and RAM management is better because recently on my ROM that was oh-so popular drains the hell out of my standby time and I cannot make/answer phone calls at times. At least I can try Android Pay. Thanks for answering my questions.
Hi all. Succesfully rooted my S8 Tab Ultra and was running fine for the past week.
Just rebooted the tablet and its showing "Custom Binary(boot) Blocked due to remaining installment balance" I've read around the forum and apparently its for people who haven't paid for the device fully which I have, paid in full on pre order.
The only way it seems to get it to boot is to flash the original firmware my model is SM-X900NZAFXAR and I can't find the firmware does anyone know how I can get the tablet to boot?
Tried Samsung support but they didn't help
Hello! Get SamFirm at https://samfirmtool.com/ (v0.5.0 is the latest), for model put SM-X900, for Region put XAR. I haven't received mine yet (not until the middle of next month), but this is the closest I could find to what should be the correct firmware. Click "Check Update", then click "Download". It's been too long for me away from Samsung - I don't remember if it matters if you let it decrypt automatically or not. The answer should become apparent, though. At worst, you'll just have to redownload the firmware with the option to decrypt unchecked in SamFIrm.
You can check your CSC (Region) by (copying/pasting someone else's instructions):
go to settings - about - software information - service provider SW ver. The region code (CSC) will be written there.
I don't know if your CSC will match XAR. I don't find anything for XAA or XAS yet in SamFirm.
Good luck! This is concerning since I had planned on rooting mine.
Thanks for the reply. I've downloaded the XAR firmware but now I have another problem getting the USB device not recognised. Device descriptor request failed. Tried locking the bootloader again now its stuck with a Hash fail on boot and wont turn off. Can't unlock the bootloader again. 99% sure its not the laptops fault its the one i rooted on but will try another pc tomorrow. Will have to try Samsung again as although I have rooted which voids warrenty its there mistake on my device thinking it has finance outstanding that has caused the failure.
Cheers
Jono0907 said:
Thanks for the reply. I've downloaded the XAR firmware but now I have another problem getting the USB device not recognised. Device descriptor request failed. Tried locking the bootloader again now its stuck with a Hash fail on boot and wont turn off. Can't unlock the bootloader again. 99% sure its not the laptops fault its the one i rooted on but will try another pc tomorrow. Will have to try Samsung again as although I have rooted which voids warrenty its there mistake on my device thinking it has finance outstanding that has caused the failure.
Cheers
Click to expand...
Click to collapse
You got the latest Samsung drivers installed, as linked to in the SamFirm\Samsung Driver subfolder? (link leads to https://samsungusbdriver.com/category/download)
Wait... Is OEM Unlock still enabled in Dev Options? It might be salvageable even though you have locked the bootloader...
Thank you edor for the help the tablet is running again now however it is unrooted now and the OEM unlock option is missing. The USB fault was resloved using a different PC not sure whats going on with my laptop.
Once in download mode i was able to download the XAR version of the Tab S8 Ultra fimrware from SamFirm and reflash with Odin which brought it back.
I'm not sure if running XAR csc will cause problems? I am in the UK I think my csc originally was OXM which is the universal one but cant find an OXM version at the moment.
fkofilee I actually locked the bootloader from the download mode menu which i shouldnt have. I don't have the option now so think I need to wait for the OEM unlock to show in settings.
For anyone else who has the "Custom Binary(boot) Blocked due to remaining installment balance" Need to reflash back to original firmware to boot and apparently it will re-check in 7 days so cannot be rooted in that time.
I have an open ticket with Samsung to try and find out why my tablet thinks it has finance. The confirmed on the phone that it was paid in full.
I wonder if the S7 Bootloader that i rooted had anything to do with it. Will retry with the bootloader when i can and report back.
@Jono0907 I'm glad you got it back working. I apologize if the XAR firmware has anything to do with your OEM unlocking not being available. Thank you for the advice for myself and for others to follow if we encounter the same problem. You had used the S7 bootloader? I would expect that to be the problem but as I said, I'm rusty on Samsung, and totally unexperienced in Samsung tablets - I only know what I've read in this section so far.
My tablet is working because of your advise so I'm happy. Found the EUX firmware which feels like it should be what my tablet should be running so will flash that and see if Unlock comes back. Tried all the tricks with date/time to try and trick it but no luck.
Also was going to add my experience with Samsung support. He agreed that if the tablet was wrongly reporting it was in finance then it wouldn't have been my fault but also said Samsung would not help because I had rooted the device. He didnt talk about reflashing firmware just said that I needed to send it to them for a new motherboard to repair Knox at a cost of at least $400(£300)
I planned to root s8 ultra, now afraid. So, is it safe to root it, and can someone put here whole procedure?
Many thanks
It's pretty much always safe because you can go back to "Download Mode" and reflash the original firmware.
It will however trip Knox which is Samsungs securityh (Done by breaking a physical fuse on the motherboard) which cannot be undone. This voids the warrenty and could cause problems with Google Pay and other things.
The basic process for rooting the S8 is
1. The process requires OEM Unlocking which some carriers in USA seem to be blocking. If you can OEM unlock it will be an option within the developers options in settings. Sometimes it doesn't show up right away.
2. Download SamFirm and get the firmware for your device. The Model for the Non-5G Tab S8 is SM-X900 and put in the CSC code for your region. Samsung simplified CSC codes before the release of the Tab S8 so you can see the list on wikipedia when searching for the tablet it is probably better to look up how to check your CSC code on your tablet to make sure you are getting the right one.
3. Install Magisk Manager on your tablet. Extract the firmware and copy the AP file to your tablet. Open Magisk Manager and point it at the AP file that you copied. Once complete it should give you a Magisk Patched file copy it back to your computer.
4. Install Odin and Samsung USB drivers. In Odin Select the Magisk Patched file for AP then add the BL file that you downloaded from SamFirm and the CSC file. (This will factory reset the tablet). You can leave CP and Userdata blank.
5. Reboot the tablet into Download Mode. This can be done by powering it off connecting it the the PC and when you see the charge symbol hold down Volume up and Volume down till you get to the Download Mode Menu. From here you need to press the option for OEM Unlock and then go to the download screen. Now press start in Odin.
That's pretty much it
ivanox1972 said:
I planned to root s8 ultra, now afraid. So, is it safe to root it, and can someone put here whole procedure?
Many thanks
Click to expand...
Click to collapse
I want clearly explanation, I don't know about this.
Jono0907 said:
It's pretty much always safe because you can go back to "Download Mode" and reflash the original firmware.
It will however trip Knox which is Samsungs securityh (Done by breaking a physical fuse on the motherboard) which cannot be undone. This voids the warrenty and could cause problems with Google Pay and other things.
The basic process for rooting the S8 is
1. The process requires OEM Unlocking which some carriers in USA seem to be blocking. If you can OEM unlock it will be an option within the developers options in settings. Sometimes it doesn't show up right away.
2. Download SamFirm and get the firmware for your device. The Model for the Non-5G Tab S8 is SM-X900 and put in the CSC code for your region. Samsung simplified CSC codes before the release of the Tab S8 so you can see the list on wikipedia when searching for the tablet it is probably better to look up how to check your CSC code on your tablet to make sure you are getting the right one.
3. Install Magisk Manager on your tablet. Extract the firmware and copy the AP file to your tablet. Open Magisk Manager and point it at the AP file that you copied. Once complete it should give you a Magisk Patched file copy it back to your computer.
4. Install Odin and Samsung USB drivers. In Odin Select the Magisk Patched file for AP then add the BL file that you downloaded from SamFirm and the CSC file. (This will factory reset the tablet). You can leave CP and Userdata blank.
5. Reboot the tablet into Download Mode. This can be done by powering it off connecting it the the PC and when you see the charge symbol hold down Volume up and Volume down till you get to the Download Mode Menu. From here you need to press the option for OEM Unlock and then go to the download screen. Now press start in Odin.
That's pretty much it
Click to expand...
Click to collapse
Succesfully rooted a magisk patched AP. Then later I tried to flash another one with an updated firmware, resulting in a soft brick. Does reflashing unpatched stock rom via Odin wipe all my data? Even if I flash HOME_CSC?
emko7 said:
Succesfully rooted a magisk patched AP. Then later I tried to flash another one with an updated firmware, resulting in a soft brick. Does reflashing unpatched stock rom via Odin wipe all my data? Even if I flash HOME_CSC?
Click to expand...
Click to collapse
Sorry mate never done the HOME CSC flash I've always been happy to wipe the device hopefully someone here knows?
emko7 said:
Succesfully rooted a magisk patched AP. Then later I tried to flash another one with an updated firmware, resulting in a soft brick. Does reflashing unpatched stock rom via Odin wipe all my data? Even if I flash HOME_CSC?
Click to expand...
Click to collapse
Uh-oh. I was just getting ready to update to the latest firmware, Maybe I'll have to wait, see how this plays out.
lloydsw said:
Uh-oh. I was just getting ready to update to the latest firmware, Maybe I'll have to wait, see how this plays out.
Click to expand...
Click to collapse
For what it's worth on my S8 Ultra, I updated from rooted April update to rooted May's update perfectly fine without wiping data. Always do backups, though, things happen.
roirraW edor ehT said:
For what it's worth on my S8 Ultra, I updated from rooted April update to rooted May's update perfectly fine without wiping data. Always do backups, though, things happen.
Click to expand...
Click to collapse
Yup, worked fine on my S8. Sigh of relief!