Related
I am trying to root my S5 using Odin for installing custom ROM but unable to root it. As soon as i start the root process, it gives the message of Failed.
help please?
Need a lot more info than that bud, model S5?
Method you are using step by step?
I have S5 SM-G900F
i am connecting it to my laptop in download mode with USB Debugging enabled
Odin is detecting the phone, i added the CF-Auto Root file to Odin
The Odin gave indication that this file is valid
Once i start the operation, it displays this in Message window of Odin
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
The message that i get on my cell phone screen are
UDC START
SYS REV CHECK FAIL : No Version
SECURE MAGICODE CHECK FAIL : recovery
and the process ends up with a FAIL message in Odin
Are you running ODIN as Admin? (Right click > Run as Administrator)
And you've tried a couple different versions from 3.09 > 3.10.7 ?
-
If that still fails, you'll probably need to flash TWRP 2.8.7.0 with ODIN then SuperSU from TWRP recovery
Specifically version 2.8.7.0
And you don't need USB debugging enabled for flashing from download mode, only for connecting while the phone is booted into Android
Try another software
Try flashing already rooted ROM if not considered ?
Don't use kingroot !
regards
Max.
okay let me try this way now
NO DO NOT TRY KINGROOT
Only CF Auto Root or SuperSU from recovery
Anything else is likely to brick your phone
---------- Post added at 15:06 ---------- Previous post was at 15:05 ----------
stalker2106 said:
Try flashing already rooted ROM if not considered ?
Either, you could try KingRoot, it works on some devices,
but it is horribly slow.
regards
Max.
Click to expand...
Click to collapse
Don't give out advice that you have not personally tested on the S5
Are you going to fix his phone for him when you brick it?
I flashed my G900F using Odin3 but i rooted my tablet with KingRoot and it worked well, so i though he could give it a shot ! but if you say its not recommended then i will edit my post, sorry for inconvenience.
Rooting a tablet with kingroot has nothing to do with a Galaxy S5
Again, unless you have successfully performed what you are suggesting on the S5, do not suggest it, a tablet has nothing to do with an S5
Hi, my brother-in-law tried to root his phone but probably didn't know what he was doing with Odin and Kies. I tried to restore the phone with Kies3 but the phone is not recognized and I can't get a recovery code. I've tried the default option of booting into recovery mode and flashing with Odin as Administrator. I'm flashing following a guide on this forum using [Auto Reboot] [F. Reset Time] checked in the options and loading [AP] [CP] [CSC] first. Others have commented not to use the [BL] file. The problem is when I try to flash it fails and I get this message:
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the screen of the phone it says:
UDC START
SYS REV CHECK FAIL : Refer 3 > Binary 1
SECURE CHECK FAIL : system
Click to expand...
Click to collapse
I've tried everything I could flashing each one by one [BL] [AP] [CP] and [CSC]. Apparently the only one that successfully flashed through was [CP]. The phone can boot into recovery mode fine, when I start the phone normally it just hangs on the Samsung Galaxy S5 screen. Any help in the right direction would be appreciated. I have pretty much GoogledFu'd all the information I can and am using the stock Samsung Galaxy S5 SM-G900A firmware. I have tried different USB ports, the stock Samsung USB cable, and an LG USB cable and that didn't help either.
To flash the firmware using Odin you need to put the phone in Download mode (Power + home + volume down) and not recovery mode. Select PDA/AP in Odin, select the firmware and then click start.
DigitalBeating said:
Hi, my brother-in-law tried to root his phone but probably didn't know what he was doing with Odin and Kies. I tried to restore the phone with Kies3 but the phone is not recognized and I can't get a recovery code. I've tried the default option of booting into recovery mode and flashing with Odin as Administrator. I'm flashing following a guide on this forum using [Auto Reboot] [F. Reset Time] checked in the options and loading [AP] [CP] [CSC] first. Others have commented not to use the [BL] file. The problem is when I try to flash it fails and I get this message:
On the screen of the phone it says:
I've tried everything I could flashing each one by one [BL] [AP] [CP] and [CSC]. Apparently the only one that successfully flashed through was [CP]. The phone can boot into recovery mode fine, when I start the phone normally it just hangs on the Samsung Galaxy S5 screen. Any help in the right direction would be appreciated. I have pretty much GoogledFu'd all the information I can and am using the stock Samsung Galaxy S5 SM-G900A firmware. I have tried different USB ports, the stock Samsung USB cable, and an LG USB cable and that didn't help either.
Click to expand...
Click to collapse
Yes, I already have done that and the only thing that writes successfully is the [CP] file. It fails to write to the NAND and does a FAIL! (Auth). Not sure what else I can do.
Alright I think I figured exactly what he did to the phone. Apparently AT&T locked the bootloader on Lollipop and his phone got upgraded to Lollipop while he was sleeping. So he tried to use Odin to flash the AP for the older KitKat back onto the S5 and this softbricked the phone. As far as I have read there is no way to downgrade back currently to KitKat to get root access. I'm trying to look for stock firmware for Lollipop but I can't find anything for this model. I assume if I flash it back to the latest Lollipop version functionality will be restored. Someone said something about flashing a kernel but I don't know. Not really sure what to do now since I can't find official Samsung S5 SM-G900A firmware to flash back either through the recovery or through Odin.
DigitalBeating said:
Alright I think I figured exactly what he did to the phone. Apparently AT&T locked the bootloader on Lollipop and his phone got upgraded to Lollipop while he was sleeping. So he tried to use Odin to flash the AP for the older KitKat back onto the S5 and this softbricked the phone. As far as I have read there is no way to downgrade back currently to KitKat to get root access. I'm trying to look for stock firmware for Lollipop but I can't find anything for this model. I assume if I flash it back to the latest Lollipop version functionality will be restored. Someone said something about flashing a kernel but I don't know. Not really sure what to do now since I can't find official Samsung S5 SM-G900A firmware to flash back either through the recovery or through Odin.
Click to expand...
Click to collapse
I am currently in the same boat. Please tell me you found a fix for this and if so, what was it? Any help is greatly appreciated.
@DigitalBeating and @Theamazingcorey
Here is an AT&T lollipop firmware.....
https://www.androidfilehost.com/?fid=24591000424940454
G900AUCU4COI5_ATT4COI5_v5.1.1_Repair_Firmware
I found it (by chance) on a Russian hosting site. They say it's a 'repair' firmware which means it is more than likely going to be more than one file (it'll probably be bootloader, modem and OS) So you'll have to load each file into it's respective Odin 'slot'.
If I understand how repair firmwares work, it should wipe and format the data partitions (instead of simply overwriting them) as it flashes. This will give the best chance of a successful flash.....
http://i.imgur.com/rVnFwJM.jpg
I cannot thank you enough, that seems to have fixed my problem. I though I was going to be stuck with a paperweight, lol.
Would you happen to know if there is a way to root the the AT&T S5 with 5.1.1?
Glad it worked fella.....
With regards to rooting, everything I've read on XDA indicates AT&T Lollipop can't be rooted....and the possibility of downgrading to achieve root is non existent.......
But there's a LOT if information on XDA, and I'll be the first to admit that I haven't read it all........
http://i.imgur.com/rVnFwJM.jpg
@Theamazingcorey just out of interest, can you confirm what files were inside the zip?
http://i.imgur.com/rVnFwJM.jpg
Thanks for the info. Sorry I was not able to get back to you sooner, I've been slammed these last couple of days. Have family coming into town this evening and between work and getting ready for their visit, I haven't had time to think straight, lol.
Hi, I hope I can get an answer on this. Purchased the Note 4, just went outside of warranty a few weeks ago, and I'm trying to root it.
I set my phone in debug mode, and tried on both ODIN 3.9 and the last RV to no avail and tried to flash CF-Auto-Root-trltecan-trltecan-smn910w8.tar.md5
I don't understand what it is I'm doing wrong. Installed all drivers with Samsung USB Driver, and KIES
Uninstalled KIES as I heard it was not recommended.
It hangs during the download stage at <ID:0/003> recovery.img
Getting real frustrated as documentation doesn't really cover anything for the latest Android version released for this phone.
Any help would be greatly appreciated.
Thank you in advance!
WarDerp said:
Hi, I hope I can get an answer on this. Purchased the Note 4, just went outside of warranty a few weeks ago, and I'm trying to root it.
I set my phone in debug mode, and tried on both ODIN 3.9 and the last RV to no avail and tried to flash CF-Auto-Root-trltecan-trltecan-smn910w8.tar.md5
I don't understand what it is I'm doing wrong. Installed all drivers with Samsung USB Driver, and KIES
Uninstalled KIES as I heard it was not recommended.
It hangs during the download stage at <ID:0/003> recovery.img
Getting real frustrated as documentation doesn't really cover anything for the latest Android version released for this phone.
Any help would be greatly appreciated.
Thank you in advance!
Click to expand...
Click to collapse
DISCLAIMER-_-Try on your own risk.
This is a universal method if you follow all steps correctly you will have permanent root and also custom recovery for flashing roms,zip files,backup roms etc.
1, download TWRP recovery img.tar.
2,download supersu.zip
3,open odin go to options and "uncheck" autoreboot.
4,choose AP tab in odin and upload TWRP recovery.
5,go to device download mode and connect to pc via usb cable.
6,HIT START in odin once odin shows pass remove battery from device.(DO NOT REBOOT YOUR DEVICE)
7,insert battery again and boot into TWRP recovery by pressing (volume up+home+power button)
8,go to install and flash supersu.zip and reboot.
Your device may reboot twice so dont worry its normal
Enjoy root.
TWRP RECOVERY LINK
https://dl.twrp.me/trltecan/twrp-3.0.2-0-trltecan.img.tar.html
SUPERSU.ZIP LATEST
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Thanks for the help! I tried that though and now it's just hanging at the Downloading screen again. Going to give it another five minutes but I really hope I'm not ruining it.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
Click to expand...
Click to collapse
EDIT: Nothing's happened. Trying with latest RV of ODIN
Tried with the latest version of ODIN. Nothing
can the w8 be rooted?
Reviving an old thread? Yes, W8 can be rooted. I did had similar problem with rooting my W8, but I fixed it using similar steps as Trex outlined above.
If you're still having problems, check and make "lock re-activation" is off. "usb debugging" is on.
HappyPlato said:
Reviving an old thread? Yes, W8 can be rooted. I did had similar problem with rooting my W8, but I fixed it using similar steps as Trex outlined above.
If you're still having problems, check and make "lock re-activation" is off. "usb debugging" is on.
Click to expand...
Click to collapse
Know any way to revive via sd card? I hear it's possible.
Sent from my Samsung SM-N900T using XDA Labs
i search a Root for the Samsung Galaxy Tab S5e SM-T725 , for install a Mod PlayStore .....
Are you asking if there is root for the Tab 5se yet?
yes ... is there a root for the tab S5e?
Yes, there is root for the S5e, it is complicated atm...
https://forum.xda-developers.com/galaxy-s10/development/magisk-root-galaxy-s10-series-t3918699
DerZero said:
yes ... is there a root for the tab S5e?
Click to expand...
Click to collapse
I do not understand. how can I ROOT the Galaxy Tab S5e (SM-T725)?
DerZero said:
I do not understand. how can I ROOT the Galaxy Tab S5e (SM-T725)?
Click to expand...
Click to collapse
I have not tried it yet...don't have a lot of time atm. Basically you will need to enable developer mode first to unlock the bootloader your device, the OEM unlock may not appear for 24 hours or more. Once you do that, follow the instructions from this website:
https://topjohnwu.github.io/Magisk/samsung
More or less it is the same, except we don't have a Bixby button. You'll need to hold Volume Up and Volume Down together to boot into download mode. Make sure you practice booting into the various modes first.
nsx2brz said:
I have not tried it yet...don't have a lot of time atm. Basically you will need to enable developer mode first to unlock the bootloader your device, the OEM unlock may not appear for 24 hours or more. Once you do that, follow the instructions from this website:
https://topjohnwu.github.io/Magisk/samsung
More or less it is the same, except we don't have a Bixby button. You'll need to hold Volume Up and Volume Down together to boot into download mode. Make sure you practice booting into the various modes first.
Click to expand...
Click to collapse
I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.
AHE_XDA said:
I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.
Click to expand...
Click to collapse
A few caveats with XAA:
For 'OEM Unlock' to show, you must be connected to WiFi to unlock the Bootloader.
And if you 'Factory Reset' after unlocking it, it disappears completely.
If you change the date, time or year, it doesn't return until you reconnect to WiFi.
Interesting, just got mine today tempted to try this.
---------- Post added at 12:56 AM ---------- Previous post was at 12:52 AM ----------
AHE_XDA said:
I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.
Click to expand...
Click to collapse
Please let us know how it went!
I've managed to unlock the bootloader.
I'll post a few pictures in a moment.
Note: This is for the SM-T720.
AHE_XDA said:
I've managed to unlock the bootloader.
I'll post a few pictures in a moment.
Note: This is for the SM-T720.
Click to expand...
Click to collapse
-----
I've patched the AP file but keeps failing when Odin attempts to write 'Modem':
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5505 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> system.img.ext4
<ID:0/003> dtbo.img
<ID:0/003> vendor.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> vbmeta.img
<ID:0/003> modem.bin
<ID:0/003> FAIL! (Auth)
For those curious; I'm on the latest version of Odin and running stock XAC firmware.
That said, I'm finished trying for now. Perhaps when there are more active participants, we can collaborate.
But I have the 6GB/128GB combination and, for what I use it for, root isn't that essential (just merely a curiosity). The device, with its eMMC storage and mid-range CPU, does really impress me. I've been able to use it as a very competent laptop replacement with DEX and One UI, once you use the Android Studio to uninstall some unnecessary bloat, is night and day from what Samsung use to offer just a couple years back.
Try removing every file from the tar except for boot.img, recovery.img, and vbmeta. That is what worked for PewPewK when he rooted his in another thread. I built my magisk_patched.tar with these 3 files, haven't tried flashing them yet...
AHE_XDA said:
-----
I've patched the AP file but keeps failing when Odin attempts to write 'Modem':
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5505 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> system.img.ext4
<ID:0/003> dtbo.img
<ID:0/003> vendor.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> vbmeta.img
<ID:0/003> modem.bin
<ID:0/003> FAIL! (Auth)
For those curious; I'm on the latest version of Odin and running stock XAC firmware.
That said, I'm finished trying for now. Perhaps when there are more active participants, we can collaborate.
But I have the 6GB/128GB combination and, for what I use it for, root isn't that essential (just merely a curiosity). The device, with its eMMC storage and mid-range CPU, does really impress me. I've been able to use it as a very competent laptop replacement with DEX and One UI, once you use the Android Studio to uninstall some unnecessary bloat, is night and day from what Samsung use to offer just a couple years back.
Click to expand...
Click to collapse
nsx2brz said:
Try removing every file from the tar except for boot.img, recovery.img, and vbmeta. That is what worked for PewPewK when he rooted his in another thread. I built my magisk_patched.tar with these 3 files, haven't tried flashing them yet...
Click to expand...
Click to collapse
Do you happen to have the URL for the thread?
I'm apt to try this again in a week or two.
best would be a root of CF-AUTOROOT or a TWR and a ROOT.ZIP -.-
https://forum.xda-developers.com/ga...ragon-root-waiting-discussion-t3919024/page24
Post #235 is where is says what worked. Good luck! I probably won't have time to try mine until next month.
AHE_XDA said:
Do you happen to have the URL for the thread?
I'm apt to try this again in a week or two.
Click to expand...
Click to collapse
I have Magisk working on my Tab S5e (have had it working since the day after it launched). I was going to post instructions, but we still don't have a Tab S5e forum to post em in.
PewPewK said:
I have Magisk working on my Tab S5e (have had it working since the day after it launched). I was going to post instructions, but we still don't have a Tab S5e forum to post em in.
Click to expand...
Click to collapse
Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.
btonetbone said:
Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.
Click to expand...
Click to collapse
Yeah, sure. I wrote this in an e-mail to someone who messaged me regarding rooting the Tab S5e, but it's a tad bit old. Regardless, I'll paste it verbatim here:
Because my installation process was hardly linear (I ran into many problems along the way), I can't guarantee that these are exclusively the exact steps you would need to take to get it working. But I think this should be a compilation of all the final (working-ish) steps I took.
(1) Setup tablet for first time, go to settings, enable developer mode, and flick the OEM Unlocking switch.
(2) Turn off the Tab S5e and boot into Download Mode by holding Power and Vol Up + Vol Down. Then hold up on the Vol Up button (not just a quick press) as it says to enter Bootloader Unlocking Mode. Follow the instructions there to fully unlock the bootloader.
(3) The tablet will be formatted at this step. After the bootloader is fully unlocked, make sure you boot back into the Tab S5e and perform the set up again. Enable developer options and make sure that the OEM Unlocking switch is turned on. Yes, again. This step is necessary apparently due to some changes Samsung made with their new VaultKeeper service? If you don't you may soft brick the device.
(4) Install @ianmacd's Magisk Manager application on your Tab S5e. Download is here. [Update: TopJonWu's official Magisk build should now work fine.]
(5) Download the latest Tab S5e firmware build. I found my copy here. Extract from it the AP file. Transfer this file to your Tab S5e.
(6) Back in Magisk Manager, go to settings and look for "Update Channel." Here's where I'm a little uncertain of what I did that finally got it to work, so I'll recommend two steps...
(7a) Select the ianmacd update channel and return to the home screen of Magisk. [Update: This shouldn't be necessary anymore, especially if you installed the official Magisk Manager earlier.] Click install, then choose the patch file option. Locate the AP file you transferred earlier and wait for it to finish creating a "magisk_patched.tar" file. Transfer this file to your computer and rename it "magisk_patched_ianmacd.tar," then delete the old magisk_patched on your device.
(7b) Do the same for the Canary (debug) update channel. Patch the AP again, and locate the patched file, copy it to your computer, and rename it to something clear.
(8) This is an odd step I had to follow to avoid errors flashing. It turns out of the several times I tried making the patched images, I almost always inevitably had some file in the archives getting corrupted. So open up both magisk_patched.tar's and test them for errors. I did this in 7-Zip, but there's probably ways to do it in WinRAR, too. If it gives you any error, take a note of which file it failed on because that guarantees your flashing will fail in later steps. In fact, the reason I recommended doing two different methods for patching magisk above was because the first ianmacd patch I tried had a corrupt recovery.img. What I ended up doing to fix it was extracting a working (non-error checking) recovery.img, vbmeta.img, and boot.img from the two different patched Magisks and then recombined them myself into my own Magisk tar. I also kept the meta-inf folder in there for good measure, though I don't think it's necessary? So in the end, I had what I called a "magisk_patched_lite.tar" that contained exactly three images: recovery.img, vbmeta.img, and boot.img, along with the meta-inf folder and ensured 7-Zip did not return any errors on the archive.
(9) Reboot the tablet to Download Mode. Press Vol Up to start. Attach the Tab S5e to your computer, and start Odin (I used v3.13.1_3B_PatcheD).
(10) Put some working archive of the patched magisk in the AP slot and uncheck "Auto Reboot." I don't know if the 'lite' version is sufficient for your first flash, but I suspect that it is (it would not be sufficient if you're pre-patching an updated firmware for the Tab S5e). Let Odin rip and see if you get any errors.
(11) Assuming Odin was successful, hold Power and Vol Down to exit Download Mode, then immediately switch to Power and Vol Up once the screen shuts off. Continue holding these until you are greeted with Recovery mode.
(12) Use the volume keys to select Factory Reset/Wipe Data. Execute that to make sure the tablet is properly formatted.
(13) Use the reboot into system option at the top of recovery. Hold Power and Vol Up until the "Bootloader is Unlocked" warning screen shows up, then release.
(14) If you're lucky, you should eventually see a red warning message about not having Samsung software installed. That's a good sign. My tablet fumbled around these steps and looked like it was gonna bootloop for a while? But eventually, it ran its course and booted.
(15) You hopefully have root installed now. Set up the tablet one last time, install the ianmacd Magisk Manager again and open it up. If it says Magisk is installed, great job, otherwise... I don't know where the issue is because this rooting sequence is way more complicated than for other devices! At some point, I think after a reboot, Magisk Manager asked if it could do some additional setup stuff. Obviously let it do that.
Click to expand...
Click to collapse
I updated a few steps that have changed since writing that up originally. Since the Tab S5e hasn't seen a software update yet, I'll also upload my (hopefully) working copy of the flashable patched_magisk_boot.tar that you can flash in the AP slot in Odin. No guarantees it works, but I can't imagine why it wouldn't. In theory, you should be able to skip several steps above and simply OEM (bootloader) unlock the device, then flash this in Odin.
Also important! Fundmentally, this version of root works very differently from what you may be used to. See here for detailed information. Normally root is installed onto the boot partition, but Samsung did some ****y stuff this generation to be "compliant" with Google's new rules, but still do things in their own special way, so now to achieve root Magisk has to live on the recovery partition.
Magisk living on the recovery partition means that in order to boot with Magisk enabled, you have to boot into recovery. So to boot with root, hold power and vol up until you see the "bootloader is unlocked" warning screen, then release. If you hold Vol Up, you will be taken to recovery, which will boot the system partition with root enabled. Otherwise, your tablet will boot the system partition without root. So if you do not do this step, root will not work (i.e. you'll boot into system without Magisk).
Hope this helps you achieve root.
Great Instructions.
The only other trick to keep in mind, is you have to hold up and power EVERY TIME you boot. If you don't, it'll come up in not root mode.
PewPewK said:
Yeah, sure. I wrote this in an e-mail to someone who messaged me regarding rooting the Tab S5e, but it's a tad bit old. Regardless, I'll paste it verbatim here:
I updated a few steps that have changed since writing that up originally. Since the Tab S5e hasn't seen a software update yet, I'll also upload my (hopefully) working copy of the flashable patched_magisk_boot.tar that you can flash in the AP slot in Odin. No guarantees it works, but I can't imagine why it wouldn't. In theory, you should be able to skip several steps above and simply OEM (bootloader) unlock the device, then flash this in Odin.
Hope this helps you achieve root.
Click to expand...
Click to collapse
btonetbone said:
Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.
Click to expand...
Click to collapse
netjetman said:
The only other trick to keep in mind, is you have to hold up and power EVERY TIME you boot. If you don't, it'll come up in not root mode.
Click to expand...
Click to collapse
Yep, good point. I forgot to include that because in the original e-mail thread, it was already known and implied. But I'll add it to the post here so folks will catch that. Annoying for sure, but at least it works.
Hi all,
I have tried to root my phone with this thread
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-root-android-8-0-oreo-t3840271
Then something went wrong and the phone got bricked as stuck in the Samsung first logo
So I tried to flash those 2 stock firmware (as BL, AP, CP & CSC) but Odin keeps giving me fail and gives me this:
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> skip file list for home binary
<ID:0/007> param.bin
<ID:0/007> modem_debug.bin
<ID:0/007> Home Binary Download
<ID:0/007> Total Binary size: 4141 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> cm.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The 2 stock ROMs I tried to install
https://www.sammobile.com/samsung/g...e/SM-G935F/LYS/download/G935FXXS8ETCA/328694/
and
https://www.sammobile.com/samsung/g...e/SM-G935F/XSG/download/G935FXXS8ETCA/328689/
I can flash a CF and TWRP but that's it nothing else
Tried and wiped everything (Data-Cache-System-Delvike) but in TWRP it says no OS installed
And if I restarted to system it gives me this message:
An error has occurred while updating the device software.
Use the emergency recovery function in the smart switch pc software
But when I do it never shows me the device and it gives me an empty space
Used Odin V3 14.4
What can I do to flash it back to stock then try to root it again please help!!!
You unlock the "OEM lock" and unlocked bootloader before you install the twrp, right?
if you can get in TWRP, format the data in wipe, reboot, choce mount ->data, if it not been mounted.
download a rom.
https://forum.xda-developers.com/s7-edge/development/teamexykings-lightrom-t3918768
https://forum.xda-developers.com/s7-edge/development/rom-hyper-rom-unique-t3808211
https://forum.xda-developers.com/galaxy-s7/development/rom-arcatarc-nfesuperleggera-nfefull-t4101967
or whatever you like.
put the rom on a sdcard. if you dont have one, connet the phone to the pc when you in TWRP, I think you can copy the rom to the phone directly. install the rom.
---------- Post added at 04:00 AM ---------- Previous post was at 03:51 AM ----------
If you wanne install the stock rom, download "samfirm", choce model, choce region , check the"Decrypt Automatically" box on the right, then click "Check Updates", download the rom. Use odin to install it. The Important step is format data in twrp.
WillKK said:
You unlock the "OEM lock" and unlocked bootloader before you install the twrp, right?
if you can get in TWRP, format the data in wipe, reboot, choce mount ->data, if it not been mounted.
download a rom.
https://forum.xda-developers.com/s7-edge/development/teamexykings-lightrom-t3918768
https://forum.xda-developers.com/s7-edge/development/rom-hyper-rom-unique-t3808211
https://forum.xda-developers.com/galaxy-s7/development/rom-arcatarc-nfesuperleggera-nfefull-t4101967
or whatever you like.
put the rom on a sdcard. if you dont have one, connet the phone to the pc when you in TWRP, I think you can copy the rom to the phone directly. install the rom.
---------- Post added at 04:00 AM ---------- Previous post was at 03:51 AM ----------
If you wanne install the stock rom, download "samfirm", choce model, choce region , check the"Decrypt Automatically" box on the right, then click "Check Updates", download the rom. Use odin to install it. The Important step is format data in twrp.
Click to expand...
Click to collapse
Yes oem was unlocked and usb debugger before i did anything first time
I did wipe data and cache and even factory everything now i guess the phone does not have any OS and when i try to flash the 2 rom above it gave me the above error
I guess u did not read everything i wrote there !!!
Will give it a try anyway now
But i can flash any from TWRP even it Says no OS right?
koshac4 said:
Yes oem was unlocked and usb debugger before i did anything first time
I did wipe data and cache and even factory everything now i guess the phone does not have any OS and when i try to flash the 2 rom above it gave me the above error
I guess u did not read everything i wrote there !!!
Will give it a try anyway now
But i can flash any from TWRP even it Says no OS right?
Click to expand...
Click to collapse
Not wipe data, In " wipe" there is a "format data" option on the right, if you choce "format data", it will ask you enter "yes" to confirm, did u do that befor? I didnt see you mention that. In same cases, data will been encrypted, you cant write anything on it. format data can solve that.
WillKK said:
Not wipe data, In " wipe" there is a "format data" option on the right, if you choce "format data", it will ask you enter "yes" to confirm, did u do that befor? I didnt see you mention that. In same cases, data will been encrypted, you cant write anything on it. format data can solve that.
Click to expand...
Click to collapse
Hey buddy at some point yes I have done format also
Good news I tried the 3 ROMs that u sent me and only one of them worked
the other 2 one kept looping and the other the UI kept crashing
Arcatarc NfeSuperleggera so this ROM worked with me thank u very much but now when I try to restore my data in the phone takes a long time then at the end nothing happen and nothing restored
Can u help me with that one!?
koshac4 said:
Hey buddy at some point yes I have done format also
Good news I tried the 3 ROMs that u sent me and only one of them worked
the other 2 one kept looping and the other the UI kept crashing
Arcatarc NfeSuperleggera so this ROM worked with me thank u very much but now when I try to restore my data in the phone takes a long time then at the end nothing happen and nothing restored
Can u help me with that one!?
Click to expand...
Click to collapse
Good to hear that:highfive:
I think he may removed some samsung's functions in order to make the rom lighter. he has a NfeSuperleggera®V2 "Full Stock Experience" rom, just below the light rom, maybe you can try that.
WillKK said:
Good to hear that:highfive:
I think he may removed some samsung's functions in order to make the rom lighter. he has a NfeSuperleggera®V2 "Full Stock Experience" rom, just below the light rom, maybe you can try that.
Click to expand...
Click to collapse
Now all good it took like an hour or 2 for the full restore idk why too long but now all is fine
Thank u very much my friend :good: :highfive: