A little background. A few months ago I purchased a Samsung Galaxy S4 Active SG-I537 from a person on Craigslist after my HTC One M7's microphone died. Anyway, I thought the phone was fully stock. I started to become suspicious that this was not the case when I checked for software updates from AT&T and the updates began to fail repeatedly. I downloaded a root checker from the Google Play store and, confirming my suspicions, I had root access. I didn't really like finding this out this way, but it was my own fault for not asking. Having installed CyanogenMod on both a Galaxy S1 Fascinate and an S2 Skyrocket, I knew something about these things and decided to just live with it as the phone seemed to work otherwise.
Recently I tried playing video on my DirecTV app and found that the app would not function on a rooted phone. That coupled with the fact that I am hearing that Android 5.0 Lollipop will soon be released for the S4 Active made me want to return the phone to a stock firmware. So I began reading. The problem I have is that I have no idea whatsoever how the phone was rooted. I know that the firmware was 4.2.2 UCUAMF3. So I downloaded ODIN and the full ODIN package of UCUCNE3 and then followed the below guide to a T.
Everything seemed to work, I got a pass green light from ODIN. But I have a circle with a line thru it where the AT&T wording usually appears. The 'about device' page in the settings also says 'Baseband version' is unknown. and I have no cell abilities. I can do everything from the smartphone end via WiFi. But I have no cell phone capabilities. Can't make calls, etc. What I need now is someone to point in the proper direction of where to look for the knowledge on how to fix this problem. Any help would be greatly appreciated.
Thanks.
Code:
Quote:
MF3 to MF2 (Official: Released 2013-06-21)
Quote:
MF3 to MF3 (Official: Released 2013-06-21)
Quote:
MF3 to MI2 (Leaked: Released 2013-09-25)
Quote:
MF3 to ML2 (Official: Released 2014-01-07)
Quote:
MF3 to NC9 (Official: Released 2014-04-16)
Quote:
MF3 to NE3 (Official: Released 2014-06-06)
Download the NE3 Full Odin Package from the i537 Firmware Thread.
Extract SGH-I537UCUCNE3_v4.4.2_ATT_ALL.zip using a program such as 7-zip.
Download the Windows program Odin. For more information about what Odin is and where to get it, please read the Odin section in the first post.
Open the version of Odin that you downloaded (preferably Odin v3.07)
Once opened, you need to load the files for the Bootloader, PDA, Phone, and CSC. The required files are located in the Odin Files folder. It should look exactly like the screenshot below with the appropriate checkboxes checked.
Next put your phone in download mode. For more information on how to put your phone in download mode, please read the download mode section in the first post.
Once your phone is in Download Mode, connect it to your computer using the cable that came with your phone. IMPORTANT: Odin and Samsung phones are very finicky when flashing firmware, the only usb cable that is guaranteed to work is the cable that came with your phone. You may use other usb cables, but Odin may not detect your phone. If Odin does not detect your phone try connecting to a different usb port or a different computer.
If your phone has connected properly it should show up properly in the Odin window similar to the following picture:
Once Odin has detected your phone, hit Start. It will take a long time to flash the package to your phone and will completely wipe your phone. DO NOT DISCONNECT THE CABLE OR TURN OFF YOUR COMPUTER. If the process is abruptly interrupted you risk permanently bricking your phone, so be careful.
When the program has finished it is safe to disconnect everything and reboot your phone. Your phone will be completely stock, unrooted and you will have to setup your phone from scratch again. If you wish to root the NE3 firmware, please visit the towelroot website.
tried asking the person you bought it from?
I've heard that installing a firmware/rom twice in a row can help things. try that! good luck!
If IMEI is null (check by dialing *#06#) and similar situation like this?
http://forum.xda-developers.com/showthread.php?p=56473692
O-T said:
If IMEI is null (check by dialing *#06#) and similar situation like this?
http://forum.xda-developers.com/showthread.php?p=56473692
Click to expand...
Click to collapse
Wow, I spent 7 hours on this yesterday and couldn't find that thread. I guess my search skills aren't what I thought they were. A huge thanks, O-T. I'm back up and running. I flashed the MF1 modem to get the service menu back up and selected the correct option. I was then able to reflash the NE3 firmware and now I have baseband and IMEI properly identified and working. Took another couple of hours but I'm there. Again, mucho thanks.
Related
Hi. I have an AT&T Galaxy S4 Active which was (supposedly) factory unlocked. It does accept another SIM so I know it was at least partially unlocked. I have also rooted the phone thanks to your help here. (Big thanks for that!!!) But I would like to be able to use the phone as a hotspot and can't seem to get it to perform. I get an error message that there is a network error please try again later. It occurred to me that this might be due to the AT&T APN still being listed as "default", although I have entered my carrier's APN info.
Is there a way to remove the AT&T APN? Or, alternatively, does anyone have another trick I might use? Any and all assistance would be greatly appreciated!
Is your phone sgh-i537 ?
We have several of those and all are unlocked. They arrived (large shipment) from vendor, all rooted with a locked down android 4.3 (ML2) and mobile hotspot would not work......system update would not work....
Here's what I finally did:
1. Installed Odin 3.09
2. Downloaded full image (1.2 GB) for ATT ML2 (Android 4.3)
3. Reflashed over *existing* ML2 the official ML2 which killed root and any other customizations (desired!)
4. At this point, connected to ATT System Update, it found automatically the 444 MB update to Android 4.4.2
5. Rooted with towelroot.com
6. Hotspot works now fine on all of them.
Mine is an i537 and I`m in almost the same boat. I can not enable a wifi hotspot. My phone was originally branded AT&T but I am running it on Wind which uses AWS frequency like TMobile. My phone is rooted with towel and the radio file has been modified for AWS.
Can I do what xdafly said but still modify the radio file for AWS? How about the 444mb update from AT&T? Can I update that way even tho I'm using a sim from another provider? Is there a file I can download with the same update in it?
Unable to comment on the radio file but perhaps someone else has more details on that and will post.
However, as to your question on the 444 MB update, I also tried on a few of our i537 the download links found in the ATT Stock Firmware thread
As you will discover there, if you have an unmodified ML2 (Android 4.2) or WISH TO make it so, you can install Odin (links are there) and you can download the ML2 image (links are there) and THEN you can download the 444 MB file, place it on a microSD card, drop into Stock Recovery and select the (renamed) update.zip and your ML2 will now be NE3 (Android 4.4.2).
At this point you have the official ATT i537 firmware and you can root with towelroot.com and make any other desired changes.
xdafly said:
Unable to comment on the radio file but perhaps someone else has more details on that and will post.
However, as to your question on the 444 MB update, I also tried on a few of our i537 the download links found in the ATT Stock Firmware thread
As you will discover there, if you have an unmodified ML2 (Android 4.2) or WISH TO make it so, you can install Odin (links are there) and you can download the ML2 image (links are there) and THEN you can download the 444 MB file, place it on a microSD card, drop into Stock Recovery and select the (renamed) update.zip and your ML2 will now be NE3 (Android 4.4.2).
At this point you have the official ATT i537 firmware and you can root with towelroot.com and make any other desired changes.
Click to expand...
Click to collapse
I537UCUBML2 (4.3) Released 2014-01-07 is the right ML2 to use? It is the 1.2GB Oden file. Sorry for such a simple question. I'm pretty new to this and don't want to use the wrong file and brick my phone.
HalfinchWrench said:
I537UCUBML2 (4.3) Released 2014-01-07 is the right ML2 to use? ...
Click to expand...
Click to collapse
Yes, that is the one for i537. The 1.2 gb download will contain 4 parts and you will need to find Odin (easy to find as there are many filehosts). Read the discussion threads to alleviate any concerns but it is simply a matter of opening the archive somewhere on your system, installing Odin and then just inside Odin open and point each of the 4 parts, reboot your phone to Downloading....mode (Vol Down, Power, Home) and connecting USB cable....
Thanks xdafly! I'm gonna download a couple of big files and do some reading till my eyes bleed!
I have an i537 running 4.4.2 (NE3) with the MF1 baseband (to be useable on AWS) and I still have the same issues with WiFi tethering (hotspot) that I had on ML2.
@xdafly your suggestion of 4.4.2, was that to help hotspot run while using non-ATT SIM cards? If so, am I missing a step? (I am currently not rooted, how does that help in this case?)
Let me pre-apologize because this has probably been asked a million times already but I haven't been able to find it.
Here's the quick rundown:
I towel rooted my AT&T galaxy S5
Afterwards it failed to complete any upgrades
This led me to think the same thing will happen when lollipop rolls out
I followed the unroot/downgrade guide posted by shortydoggg
This changed my firmware to an earlier version than what I had
I now get the update notices but the update won't complete
Instead of failing at 25% when I had towelroot, it now fails at 32%
I saw a post about the bootloader being incorrect but I haven't seen a solution yet
Big question? How do I resolve this where I will be able to receive the newest updates?
OTA updates are depenant on so many conditions (file permissions, ...) That they often fail even if you didn't root your device and simply reset/reflshed the ROM using Samsung Kies. I've been there.
If you can fully wipe and reflash the ROM using Samsung kies and the OTA still fails, locate your nearest att service center (not mobile retail stores), and take it in. Show them the OTA errors out (don't check for updates for 24 hours so you can let the att rep do it and see it) and they will reflash the ROM for you using their proprietary software. This will most likely get your OTA updates working again. Their software is similar to our Odin but for some reason it also does some extra stuff to your phone that Odin and kies don't.
You can take it in and they'll flash it for you even if kies doesn't recognize your phone. Just go in and complain about the OTA failing, don't make any suggestions and let the att tech genius offer you if you wanna flash and say yes please
Oh and don't forget to backup your files before hands.
*** Your question most likely belongs to the Q&A section.
GatMaster45 said:
Let me pre-apologize because this has probably been asked a million times already but I haven't been able to find it.
Here's the quick rundown:
I towel rooted my AT&T galaxy S5
Afterwards it failed to complete any upgrades
This led me to think the same thing will happen when lollipop rolls out
I followed the unroot/downgrade guide posted by shortydoggg
This changed my firmware to an earlier version than what I had
I now get the update notices but the update won't complete
Instead of failing at 25% when I had towelroot, it now fails at 32%
I saw a post about the bootloader being incorrect but I haven't seen a solution yet
Big question? How do I resolve this where I will be able to receive the newest updates?
Click to expand...
Click to collapse
Just follow step 3 under notes from this guide.
http://forum.xda-developers.com/showpost.php?p=55133105&postcount=1
shortydoggg said:
Just follow step 3 under notes from this guide.
http://forum.xda-developers.com/showpost.php?p=55133105&postcount=1
Click to expand...
Click to collapse
Sorry for being a little dense but there is more than one step 3.
Do you mean step 3 under the first section:
3. Place your phone into "Download Mode" (press and hold the Home, Volume Down, and Power keys until the phone powers on and displays warning screen, then press Volume Up key) and flash the G900A_ND3_Stock_Kernel using Odin's PDA slot(AP in Odin v3.09+)
Or the step 3 under the Notes section:
3. Should the NG3 ota update fail consider returning to stock NCE by flashing the G900A_Downgrade_to_NCE.tar using Odin's PDA slot(AP in Odin v3.09+) then taking the NG3 OTA update (or place the G900A_NCEtoNG3_OTA.zip onto your ext-sdcard and sideload from stock recovery). Once updated to NG3 continue from Step 2 above.
Thank you for your help
Step 3 under the notes section.
I've got three problems.
Won't over-the-air update
Computer can't recognize phone no matter what I do even when installing drivers separately, in "normal" mode, that is, with the phone booted and running.
Driver updates are useless
But Download mode works. So here's what I want to do. Knox is still factory-fresh and shows no alteration. I want to go back to completely stock rom in the hopes that over-the-air will then work as well as re-enabling computer to phone access (Mac/PC Kies).
Download mode works (99.99% sure). The phone works absolutely great, except for the three problems stated above. So can I do this? Here are the version numbers as found on the phone. I need help really bad here.
bodycode said:
I've got three problems.
Won't over-the-air update
Computer can't recognize phone no matter what I do even when installing drivers separately, in "normal" mode, that is, with the phone booted and running.
Driver updates are useless
But Download mode works. So here's what I want to do. Knox is still factory-fresh and shows no alteration. I want to go back to completely stock rom in the hopes that over-the-air will then work as well as re-enabling computer to phone access (Mac/PC Kies).
Download mode works (99.99% sure). The phone works absolutely great, except for the three problems stated above. So can I do this? Here are the version numbers as found on the phone. I need help really bad here.
Click to expand...
Click to collapse
Since you can get into download mode I would just Odin flash the NC2 files http://forum.xda-developers.com/showpost.php?p=54803130&postcount=136 to return your phone to stock. BUT once you do and you do the OTA Update, you will be on stock Lollipop and it CAN NOT be rooted! ONLY way to root it, is flash the NC2 files and root it (Just a heads up). IF you don't want root and want Stock Lollipop then just flash these files with Odin [100% Stock] Lollipop 5.0 (N900AUCUEOC1) Odin Tars http://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609
Attempted to root, no rooted kernels currently working for this model. now attempting to get back to stock. Anyone seen the SM-N920R6 firmware?
try rooting it with kernel for the n920p model. that worked for me
Mr.niceguy09 said:
try rooting it with kernel for the n920p model. that worked for me
Click to expand...
Click to collapse
Does this really work? for the n920r6?
DEATHoWAR said:
Does this really work? for the n920r6?
Click to expand...
Click to collapse
It worked for me. Be very careful tho. once you root it, you can,t go back since there is no stock firmware for these model.
Mr.niceguy09 said:
It worked for me. Be very careful tho. once you root it, you can,t go back since there is no stock firmware for these model.
Click to expand...
Click to collapse
Why did your phone throw the custom binary by frp lock? Did you do OEM unlock first?
Sent from my SM-N920R6 using XDA-Developers mobile app
SM-N920R6 stock firmware
I grabbed firmware for the SM-920R6 from SmartSwitch so I can probably help you out. I know how you feel, it's sad how hard it is to find anything for this phone! If you need the firmware I'll have to upload it to google drive or something this evening...
Successful un-brick and root of SM-N920R6
Using the software SamFirm and manually entering in all of the information for my phone I was able to download the correct SM-N920R6 firmware.
Here is what I had to type in the SamFirm program:
Model: SM-N920R6
Region: LRA (This really isn't a "region" it's a sales code which is why it took me forever to figure out - it can be found in System/csc/customer.xml but will be the same for all Cellcom customers)
*SELECT MANUAL CHECK BOX AND ENTER THE FOLLOWING*
PDA: N920R6WWU1BPD3
CSC: N920R6LRA1BPD3
Phone: N920R6WWU1BPD3
***MAKE SURE YOU CLICK "Decrypt automatically" (check box on right side) before you download so you get the usable zip file as well (you won't need the .enc4 file it also downloads (that is the original encrypted file)).
***You'll also want to click the "Check Update" button before downloading the firmware, but you'll get the prompt to do this by the SamFirm program.
Once you have the firmware unzipped just place it in the "AP" section on the Odin program, hit start, and you're all set!
Happy un-bricking, Cellcom customers!!
Note: After your phone reboots with the stock firmware if it hangs on the screen that has a Samsung logo dimming in and out just reboot into download mode (hold power, volume down, and home button simultaneously), and then restart the phone from the download mode menu (i.e. don't go to "continue" on the download mode screen). I tried the above recovery method a few times and it only hung on this screen once, but I was able to get out of it using the method I just described without issue.
**********************CONTINUE READING**************************
If you were frantically looking for the firmware as I was you may be telling yourself, "I'm never going to try to root this thing again!" But wait! You now have the ultimate "Un-rooting" tool at your disposal (the stock firmware!).
That being said I went further in search of achieving a successful root and..was successful! (The root achieved was using CF Auto Root which leaves the stock firmware alone. Unfortunately no custom kernels exist as of this post for this phone so this is as best we can do at the moment.
I used the file "CF-Auto-Root-nobleltespr-nobleltespr-smn920p.tar.md5" (as users pointed out above to start this thread - the "p" version works for the SM-N920R6). You just need to download that file and flash it the same way as you flashed the firmware (i.e. put it in the "AP" section of Odin and hit start. It takes a few minutes and after it's done showing all of its text as it installs the program on your phone your phone will have a black screen - don't worry it just needs to be turned on and you're rooted!
mcfasa09 said:
The root achieved was using CF Auto Root which leaves the stock firmware alone. Unfortunately no custom kernels exist as of this post for this phone so this is as best we can do at the moment.
I used the file "CF-Auto-Root-nobleltespr-nobleltespr-smn920p.tar.md5" ...
Click to expand...
Click to collapse
This trips knox, right? Can you still use Samsung Pay?
It does trip KNOX and as a result you cannot use Samsung Pay on the device (Even if you flash stock back Samsung Pay will forever be disabled on the device).
Its been a week since i got my note 5 sm-n920r6 , the person i bought it from told me to of a issue with it. He told me ever since update to naugat 7.0 the back button stop working so am seeking from anyone who can help me to get marshmallow 6.0 to downgrade to 6.0, please.
If someone who might still be on 6.0 on their note 5 SM-N920R6 can extract it from their phone or other means ,it would truly appreciated.
I use the samfirm to get the 7.0 firmware so i could flash to stock when i want, here is a link of the firmware for the SM-N920R6 if anyone might want it: https://mega.nz/#!IJYFEa5T
To access the firmware use this key: !e94lEjxPChsStdqniA2R6DwPe0s3bgvdDvvOLHmtRlM
desmond462 said:
Its been a week since i got my note 5 sm-n920r6 , the person i bought it from told me to of a issue with it. He told me ever since update to naugat 7.0 the back button stop working so am seeking from anyone who can help me to get marshmallow 6.0 to downgrade to 6.0, please.
If someone who might still be on 6.0 on their note 5 SM-N920R6 can extract it from their phone or other means ,it would truly appreciated.
I use the samfirm to get the 7.0 firmware so i could flash to stock when i want, here is a link of the firmware for the SM-N920R6 if anyone might want it: https://mega.nz/#!IJYFEa5T
To access the firmware use this key: !e94lEjxPChsStdqniA2R6DwPe0s3bgvdDvvOLHmtRlM
Click to expand...
Click to collapse
Does SamFirm trip knox? I hate being stuck on Marshmallow
aXnumeric said:
Does SamFirm trip knox? I hate being stuck on Marshmallow
Click to expand...
Click to collapse
I cannot say because i didn't notice whether it was trip or not, not that it bother me if it did. But i did manage to find the marshmallow firmware and flash back to marshmallow from naugat successfully, even though it didn't fix back button and now am back on naugat firmware.
---------- Post added at 04:02 AM ---------- Previous post was at 03:48 AM ----------
For those of us who are using this model N920R6 , i have being able to flash custom roms from the Sprint section without any issues. When i flash custom roms for other models i find i must flash the twisted kernel v2 for sprint model or your own stock kernel but even with that i have no data, so i don;t use those roms. But as for the sprint custom roms they run faultless with normal bugs that might be in a custom roms.
At first when i get this model i was piss because their is actually no support for this model until i try the sprint custom roms,it was awesome and now bit more happy.
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!