[Q] Rooting SM-G900A with build date after June 3, 2014 - Galaxy S 5 Q&A, Help & Troubleshooting

I have an SM-G900A with a build date of July 22, 2014. Geohot's Towelroot won't work on it. I keep looking for information on rooting this phone, but they all go back to Towelroot or CF-Auto-Root. Chainfire's Auto-Root page doesn't list a file for the SM-G900A. What can I do to get this phone rooted? Is there someone at the AT&T store who can help?

You can downgrade your kernel temporarily, root via towelroot and upgrade your kernel again -> rooted S5. See here.

aregvadfbg said:
You can downgrade your kernel temporarily, root via towelroot and upgrade your kernel again -> rooted S5. See here.
Click to expand...
Click to collapse
Which is the correct firmware to use? This one? http://www.sammobile.com/firmwares/1/?model=SM-G900A&pcode=0#firmware

dgriffi said:
Which is the correct firmware to use? This one? http://www.sammobile.com/firmwares/1/?model=SM-G900A&pcode=0#firmware
Click to expand...
Click to collapse
I can't say for sure for this model, but here someone says the G900AUCU1ANCE 4.4.2 stock firmware can be towelrooted.
He suggests that you downgrade the comlete firmware, not only the kernel. This may be easier because a .tar.md5-file with only the kernel might be hard to find, i only found those for the g900f. After rooting with towelroot you might be able to update to the current firmware via Mobile Odin PRO and keep root, if you can find a version of your current firmware that can be flashed with MOP. I'm not sure about that though, you have to find out yourself, i have only downgraded and re-upgraded the kernel.

aregvadfbg said:
I can't say for sure for this model, but here someone says the G900AUCU1ANCE 4.4.2 stock firmware can be towelrooted.
He suggests that you downgrade the comlete firmware, not only the kernel. This may be easier because a .tar.md5-file with only the kernel might be hard to find, i only found those for the g900f. After rooting with towelroot you might be able to update to the current firmware via Mobile Odin PRO and keep root, if you can find a version of your current firmware that can be flashed with MOP. I'm not sure about that though, you have to find out yourself, i have only downgraded and re-upgraded the kernel.
Click to expand...
Click to collapse
I fiddled with Jodin and failed. Then I dug out an old laptop, put Windows 7 on it, and tried out regular Odin for a bit. For some reason, feeding it the regular .tar.md5 file I get from sammobile.com or samsung-updates.com wouldn't work. I kept getting complaints of "W Rev Check Fail [aboot] fused 2 >Binary 1". The solution was to feed Odin the files individually. Ultimately I followed this: http://forum.xda-developers.com/showthread.php?t=2785363. My SM-G900A is now rooted.

dgriffi said:
I fiddled with Jodin and failed. Then I dug out an old laptop, put Windows 7 on it, and tried out regular Odin for a bit. For some reason, feeding it the regular .tar.md5 file I get from sammobile.com or samsung-updates.com wouldn't work. I kept getting complaints of "W Rev Check Fail [aboot] fused 2 >Binary 1". The solution was to feed Odin the files individually. Ultimately I followed this: http://forum.xda-developers.com/showthread.php?t=2785363. My SM-G900A is now rooted.
Click to expand...
Click to collapse
Nice, thanks for sharing your solution! Which rooting method did work for you?

aregvadfbg said:
Nice, thanks for sharing your solution! Which rooting method did work for you?
Click to expand...
Click to collapse
I followed the referenced directions exactly and then used Towelroot. In retrospect, that was too much. I wound up erasing everything I did with the phone. I should have followed this instead: http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299. I picked up on that one with item 6 to close the hole that Towelroot exploited. I hope that will prevent an OTA from being pushed at me. Another good thing about the latter method, I think it's easily doable with Heimdall.

Nice link!

dgriffi said:
I followed the referenced directions exactly and then used Towelroot. In retrospect, that was too much. I wound up erasing everything I did with the phone. I should have followed this instead: http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299. I picked up on that one with item 6 to close the hole that Towelroot exploited. I hope that will prevent an OTA from being pushed at me. Another good thing about the latter method, I think it's easily doable with Heimdall.
Click to expand...
Click to collapse
At least one problem has cropped up: Wifi passwords are not saved. I flashed it with the ND3 stock kernel and now it's saving passwords again. I don't know what the problem is.
Diagnosis: brainfart
With my phone flashed with the ND3 stock kernel, I allowed the phone to take the OTA update. This put my phone back into the state it was when I walked out of the AT&T store with it. THEN I followed http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299 from beginning to end. Now I have a rooted phone, Towelroot hole patched, and Wifi passwords retained.

Lol
"Is there someone at the ATT store that can help"
Laughing my ass off right now.

Related

[Q] at&t I337UCUFNC1 Root?

Is there any way to gain root for most recent att s4 update? Build number is KOT49H.I337UCUFNC1
I've been asking the same question every since the update as well. I was hoping to install a Custom ROM on my phone, but I am playing it safe until it's been confirmed workable with the latest update. As a back up, I've seen people mention it's possible to rollback this update to NB1. I've had no luck so far pulling up a thread about rolling back updates, though...
kot49h.i337ucufnc1
bluestar23 said:
Is there any way to gain root for most recent att s4 update? Build number is KOT49H.I337UCUFNC1
Click to expand...
Click to collapse
I tried the downgrade method for the NB1 and it failed with Odin3 V3.09 and got stuck with Odin3 V1.85
Root
Also looking for a way to root the i337ucufnc1
I337UCUFNC1 System Status
I was rooted yet my ATT phone still forced 2 ATT push updates. I lost root yet my phone is still showing as custom system status and unlocked custom icon on reboot.
Ditto
Jbjamin said:
I was rooted yet my ATT phone still forced 2 ATT push updates. I lost root yet my phone is still showing as custom system status and unlocked custom icon on reboot.
Click to expand...
Click to collapse
Are you able to access your external SD? I too have the same Build and have lost access to my SD, can't root, or unlock, even using the Network Unlock code from AT&T. I've lost apps, it has slowed waaaaaaaaaaaay down, and the battery is not lasting, even with Powersave. I just got this phone and the guy I bought it from factory reset it. There was an update that accepted, but it stopped and said I had to restart the update for some reason. I did, but it is still 4.4.2, but now has a different Security Software Version, MDF v1.0 Release 2. It won't accept USSD codes and gives me a 'connection error invalid mmi code' message.
Are you having the same issues? I sure wish I could find something on this. Every time I try to search, it changes the I337UCUFBNCI to "Did you mean: i337ucufnb1?" I can't find anything totally, just bits and pieces. UGHHHHHH
Success, I couldn't find a step by step tutorial to fix my issue but thanks to a full nb1 .tar and a couple other files all given by contributors I was able to odin download to reset the custom icon to official then I had to odin download the full nb1 .tar. after doing this I did the ota att nc1 update and my phone is good as factory. Until I decide to root again that is.
If you would like some help let me know
i337ucufnc1 root
Jbjamin said:
Success, I couldn't find a step by step tutorial to fix my issue but thanks to a full nb1 .tar and a couple other files all given by contributors I was able to odin download to reset the custom icon to official then I had to odin download the full nb1 .tar. after doing this I did the ota att nc1 update and my phone is good as factory. Until I decide to root again that is.
If you would like some help let me know
Click to expand...
Click to collapse
I would like some help! How were you able to root fnc1? ! And is safe strap the only custom recovery that will work I'm guessing?
thanks in advance.
adam
I did not root nc1, but it is possible thanks to some very smart contributors. I was previously rooted and wanted to unroot to factory. I became unrooted but my system was still unofficial and custom which I was having a problem getting rid of so I can trade in my phone in the future for credit. Just search nc1 root on xda and you should find the info. Its a bit of a process but you should be able to figure it out. You need to odin download back to nb1 first and go from there. If you would like some additional help I can try to give some advise but I'm no expert or developer just an enthusiast
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
bluestar23 said:
Is there any way to gain root for most recent att s4 update? Build number is KOT49H.I337UCUFNC1
Click to expand...
Click to collapse
It will help you maybe: HERE
Reboot your phone into download mode and use the NB1 full odin tar. http://forum.xda-developers.com/show...66&postcount=2
Use the MK2 downgrade method to obtain root. http://forum.xda-developers.com/show....php?t=2663545
Then use the NC1 keep root http://forum.xda-developers.com/show....php?t=2730144
This should help.
Jbjamin said:
Reboot your phone into download mode and use the NB1 full odin tar. http://forum.xda-developers.com/show...66&postcount=2
Use the MK2 downgrade method to obtain root. http://forum.xda-developers.com/show....php?t=2663545
Then use the NC1 keep root http://forum.xda-developers.com/show....php?t=2730144
This should help.
Click to expand...
Click to collapse
Can you repost those links please because none of them are valid...
Somehow when the post was made the links were messed up so the middle part is missing and just has ... instead. Thanks!
Trying to fix my mothers phone which she accidentally updated!
DornoDiosMio said:
Can you repost those links please because none of them are valid...
Somehow when the post was made the links were messed up so the middle part is missing and just has ... instead. Thanks!
Trying to fix my mothers phone which she accidentally updated!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=50667366
http://forum.xda-developers.com/showthread.php?t=2663545
http://forum.xda-developers.com/showthread.php?t=2730144
There you go
Rooting I337UCUFNC1
Hi. I have followed the threads for a while on rooting my I337. I purchased it used a month ago and really want to root it and install a custom rom. But by reading all the threads I am confused and somewhat worried I will brick it!
Can someone explain to me real clearly what software and files I should use to obtain root on AT&T I337UCUFNC1 and install a custom rom? I am ok with downgrading.
Thanks much.
Rooting the ATT SGH-I337 build I337UCUFNC1
I have this phone: build I337UCUFNC1, and was finally able to root it via the Towelroot method: Towelroot dot com.
fhuddles said:
I have this phone: build I337UCUFNC1, and was finally able to root it via the Towelroot method: Towelroot dot com.
Click to expand...
Click to collapse
i was able to root my I337UCUFNC1 using towelroot as well. however stuck trying to unlock my bootloader to install this custom rom: http://forum.xda-developers.com/showthread.php?t=2537495
any help is appreciated

Towelroot rooting fails

Hello everyone,
After getting my S5 yesterday one of the first things I did was try to root it via towelroot. Unfortunately it said phone not currently supported which is weird seeing as I found out it worked for others.
Anyway is it because I'm running too updated firmware or anything else of which I am not yet aware. If so I'd love to find out which version I need to flash and where I can find it. I also tried the automated towelroot with EasyRootToolkit(v12) and others but it got stuck on creating VM.
If anyone could help out I'll greatly appreciate it.
lyubor said:
Hello everyone,
After getting my S5 yesterday one of the first things I did was try to root it via towelroot. Unfortunately it said phone not currently supported which is weird seeing as I found out it worked for others.
Anyway is it because I'm running too updated firmware or anything else of which I am not yet aware. If so I'd love to find out which version I need to flash and where I can find it. I also tried the automated towelroot with EasyRootToolkit(v12) and others but it got stuck on creating VM.
If anyone could help out I'll greatly appreciate it.
Click to expand...
Click to collapse
If your firmware is ANGx Towelroot doesn`t work. Downgrade to an older version like ANE2 or follow this method http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044.
..
Sorry about that, I was trying to find out more general information before going into specifics.
Anyway, my model's information's below
Model: SM-G900F
Version: 4.4.2
Build: KOT49H.G900FXXU1ANG9
Kernel: 3.4.0 ~ Fri. Jul 25 2014
..
I have the same problem.
I purchased mine a few days ago, and the kernel is from August. The model is 901F. It doesn't look like there's any older version to download.
How can I root it?
HippyBob said:
I have the same problem.
I purchased mine a few days ago, and the kernel is from August. The model is 901F. It doesn't look like there's any older version to download.
How can I root it?
Click to expand...
Click to collapse
Maybe Towelroot will be updated to a newer version for the NGx kernels in the future, for now there is only CF Auto Root for root which will trip the KNOX void warranty flag. Check if the 901F is supported by CF Root first.
gee2012 said:
Maybe Toewlroot will be updated to a newer version for the NGx kernels in the future, for now there is only CF Auto Root for root which will trip the KNOX void warranty flag.
Click to expand...
Click to collapse
Ah I see. As long as I can use the phone with the rom of my choice, along with having root access, I don't need the Knox void warranty flag to be intact. I had a look around yesterday, and CF Auto root didn't support 901F iirc. Would it still be safe to try without bricking it?
Edit: Ah I see you edited your post. Will just have to wait I guess.
HippyBob said:
Ah I see. As long as I can use the phone with the rom of my choice, along with having root access, I don't need the Knox void warranty flag to be intact. I had a look around yesterday, and CF Auto root didn't support 901F iirc. Would it still be safe to try without bricking it?
Click to expand...
Click to collapse
I would wait on Chainfire for a file suited for your device, you can (soft) brick a phone with the wrong file. You could also Google around for a compatible custom recovery for your device and then flash the latest superSU.zip file for your device to get root.
..
fffft said:
You didn't look very hard. There are firmware builds going back to May.
Use Odin to write an older firmware version, then Towel root will prevail.
.
Click to expand...
Click to collapse
Well I searched for firmwares for 901F. I found ones for other models such as 900F. Would I be able to use a 900F firmware on a 901F model?
..
fffft said:
You attached your post to a thread discussing the 900F and Towel root. Instead of hijacking someone else's thread, you should start your own. Particularly because you have a different, derivative model further confusing the subject under discussion.
The 900F has firmwares dating back to May. Your 901F doesn't. An extended search is your best option. As a very recent model and running 4.4.4 as well as a new kernel build you will have to see what exploits are found for your device. You might want to post some information in the CF-Autoroot thread to see if your device can be accommodated. Or you can wait it out and see what Chainfire, Geohot, et al can do with your model.
.
.
Click to expand...
Click to collapse
Ah sorry, just didn't want to add more threads when the subject would be pretty much the same. Will create one next time. I will play the waiting game and just endure TouchWiz.
HippyBob said:
Ah sorry, just didn't want to add more threads when the subject would be pretty much the same. Will create one next time. I will play the waiting game and just endure TouchWiz.
Click to expand...
Click to collapse
Or install Nova, Apex or any other launcher and a different icon pack from Play and turn off apps/widgets you don`t use
Hi,
I had very same problem with GS3. I solved problem with a Windows based Kingo ROOT software. No need ti downgrade etc. Everything went so smoothly and easy.

Need root for Verizon SM-T337V Update 4.4.4

Ostensibly, srsroot supports rooting SM-T337V build KTU84P.T337VVRU2ANK1 Android version 4.4.4. It actually doesn't, and it doesn't appear that any other exploit exists. My business needs this. I'm not sure if this is right place to post, but we can definitely offer a bounty if this exploit does not yet exist.
Meditato said:
Ostensibly, srsroot supports rooting SM-T337V build KTU84P.T337VVRU2ANK1 Android version 4.4.4. It actually doesn't, and it doesn't appear that any other exploit exists. My business needs this. I'm not sure if this is right place to post, but we can definitely offer a bounty if this exploit does not yet exist.
Click to expand...
Click to collapse
Sorry just to eliminate the obvious, have you tried towelroot, and if that doesn't work, have you tried the newer method of flashing a kernel from an older build, rooting with towelroot, and flashing the latest kernel?
I've tried Towelroot- it does not support this update.
ODINing an old image over a new one is generally a bad idea- on Samsung devices, it has a nasty tendency of disabling the network devices.
Sent from my Nexus 5 using XDA Free mobile app
Meditato said:
I've tried Towelroot- it does not support this update.
ODINing an old image over a new one is generally a bad idea- on Samsung devices, it has a nasty tendency of disabling the network devices.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Not an entire firmware image, just a .tar of an older kernel, that's how I rooted my Galaxy S4 Active and my Tab 4 SM-T530NU
thisisapoorusernamechoice said:
Not an entire firmware image, just a .tar of an older kernel, that's how I rooted my Galaxy S4 Active and my Tab 4 SM-T530NU
Click to expand...
Click to collapse
Do you know of any links of this for the SM-T337V? Also, are you sure that the exploits in towelroot, srsroot, cfroot, etc are just kernel exploits and not dependent on other utilities or parts of the userspace? We just tried to flash the 4.4.2 kernel back over the 4.4.4 update and ended up almost bricking a test tablet.
To be clear, our tablets are already the latest update, so we have to find some way of rooting them that doesn't involve just rooting the previous version and then just never updating it.
Meditato said:
Do you know of any links of this for the SM-T337V? Also, are you sure that the exploits in towelroot, srsroot, cfroot, etc are just kernel exploits and not dependent on other utilities or parts of the userspace? We just tried to flash the 4.4.2 kernel back over the 4.4.4 update and ended up almost bricking a test tablet.
To be clear, our tablets are already the latest update, so we have to find some way of rooting them that doesn't involve just rooting the previous version and then just never updating it.
Click to expand...
Click to collapse
OK I don't think you see what I'm getting at. I understand you don't want to do a wholesale downgrade to a previous version, I get that. But the exploit in towelroot works on the older version's kernel. So, correct me if I'm wrong, but the kernel file is simply boot.img inside the tar.md5 file, which you can open as an archive in winrar or 7zip. So what I'm suggesting, and someone correct me if I'm wrong, but I'm pretty sure this is what they're doing to root the Tab 4 10.1, Galaxy S4, and Galaxy S5. So while on the latest SM-T337V firmware, extract the boot.img from the older firmware, create a tar just for the boot.img (may or may not need linux or at least cygwin to do that, honestly don't know for sure), flash that older kernel tar in Odin, quickly root your tablet with towelroot, then flash the current kernel. Sorry but I'm not sure if you want to install SuperSU before or after that last step.
But that's how the latest Samsung builds are being rooted
deleted
thisisapoorusernamechoice said:
OK I don't think you see what I'm getting at. I understand you don't want to do a wholesale downgrade to a previous version, I get that. But the exploit in towelroot works on the older version's kernel. So, correct me if I'm wrong, but the kernel file is simply boot.img inside the tar.md5 file, which you can open as an archive in winrar or 7zip. So what I'm suggesting, and someone correct me if I'm wrong, but I'm pretty sure this is what they're doing to root the Tab 4 10.1, Galaxy S4, and Galaxy S5. So while on the latest SM-T337V firmware, extract the boot.img from the older firmware, create a tar just for the boot.img (may or may not need linux or at least cygwin to do that, honestly don't know for sure), flash that older kernel tar in Odin, quickly root your tablet with towelroot, then flash the current kernel. Sorry but I'm not sure if you want to install SuperSU before or after that last step.
But that's how the latest Samsung builds are being rooted
Click to expand...
Click to collapse
We've tried this. As stated in the other thread about this OTA update, this doesn't appear to work. In our case, ODIN failed with _xmitdata error. Not even flashing the new kernel works.
Whelp, with the bootloader locked, downgrading not working, and Verizon/Samsung unwilling to help, it looks like we're SOL.
How to t337 rom install on t332?
Meditato said:
Whelp, with the bootloader locked, downgrading not working, and Verizon/Samsung unwilling to help, it looks like we're SOL.
Click to expand...
Click to collapse
I'm in the same boat as you but with the TM-537V. Also tried the downgrade kernel, towelroot, upgrade method and it failed. Are you still looking or have you given up on this?
any news?
any update on this? anyone figure out how to root the sm-t337v 4.4.4???
Meditato said:
Whelp, with the bootloader locked, downgrading not working, and Verizon/Samsung unwilling to help, it looks like we're SOL.
Click to expand...
Click to collapse
M,
are you still looking into this ? do you have or can you post/link the current bootimg in question ?
if so do you posess a tab that can be used as a guinea-pig?
I am trying to sort out an approach to a recovery for the sm-t337a and maybe tinkering with this might get
some answers to both problems at the same time.
thanks.
m
what i am thinking, ketut's degas bootimg tools seem to work unpacking and repacking a signed stock bootimg for the sm-t23xx without modification, from what i can get the signatures relates to sizes of portions of the bootimg. I have a thought that some combination of modifying the
img in question and changing compression, or just managing to change that i byte that makes secure=1 secure=0 might be a start
but need someone who can and is willing to experiment.
recovery.img too if you could.
also run in terminal [no need for root] the following
ls /proc/config.gz
i just want to see if it's there
my last thought is, if you have a device to "throw away" is to try flat out over-writing the locked bootloader with one that isn't?
evrkusd said:
I'm in the same boat as you but with the TM-537V. Also tried the downgrade kernel, towelroot, upgrade method and it failed. Are you still looking or have you given up on this?
Click to expand...
Click to collapse
Hi , now @sub77 upload new TWRP 2860 for all models , including T537V too . You may try to install it and in the success case , you may try to install superSU from recovery . Goodluck
repey6 said:
Hi , now @sub77 upload new TWRP 2860 for all models , including T537V too . You may try to install it and in the success case , you may try to install superSU from recovery . Goodluck
Click to expand...
Click to collapse
Thanks. I'm not sure if it's tested for 537V though! Did you see anyone saying that they used it for 537V or that the new version supports 537V?
evrkusd said:
Thanks. I'm not sure if it's tested for 537V though! Did you see anyone saying that they used it for 537V or that the new version supports 537V?
Click to expand...
Click to collapse
No , of course . It's new .
repey6 said:
No , of course . It's new .
Click to expand...
Click to collapse
I just tried flashing TWRP 2.8.6.0 to my SM-T537V with Odin and it failed
uroboch said:
I just tried flashing TWRP 2.8.6.0 to my SM-T537V with Odin and it failed
Click to expand...
Click to collapse
Did you try using the flashify app to install the TWRP img file? That's how I've been installing TWRP to my Tab 4
thisisapoorusernamechoice said:
Did you try using the flashify app to install the TWRP img file? That's how I've been installing TWRP to my Tab 4
Click to expand...
Click to collapse
I did not. I will give it a shot and let you know the outcome. I wont be able to use it as it requires root.
thisisapoorusernamechoice said:
Did you try using the flashify app to install the TWRP img file? That's how I've been installing TWRP to my Tab 4
Click to expand...
Click to collapse
Were you able to do this on an LTE Tab 4? or which one?

Is there any way to downgrade OF1

I know this has been discussed and there are many post on downgrading from 5.0. The problem is there is more than one version on 5.0. So far the info I've found says the latest "upgrade" to OF1 disables Odin downgrades entirely. I've tried several methods for downgrading 5.0/lollipop
but odin always fails. Is there any fix for this?
So I kept throwing stuff at it and now it's soft bricked. I guess the question now is, is there any way ti fix this when Odin won't work?????
EDIT: I guess odin will work for for reflashing 5.0 or even back to 4.4.4 so now I'm back where I started.
jellyhead said:
I know this has been discussed and there are many post on downgrading from 5.0. The problem is there is more than one version on 5.0. So far the info I've found says the latest "upgrade" to OF1 disables Odin downgrades entirely. I've tried several methods for downgrading 5.0/lollipop
but odin always fails. Is there any fix for this?
Click to expand...
Click to collapse
Uhm. What? I'm OF1. Odin works fine. If you're having problems, you did something wrong or did something you shouldn't have done. Theres only one version of OF1. There's only one version of 5.0. If youre referring to root custom ROMs, once you upgrade from 4.4.2, root is no longer possible on the Verizon Note 3.That's all their is to it.
Sent from my SM-N900V using Tapatalk
Dravekx said:
Uhm. What? I'm OF1. Odin works fine. If you're having problems, you did something wrong
Click to expand...
Click to collapse
Yeah, I figured that out. I thought Odin wouldn't work because I first tried to flash back to 4.3 then 4.4.2. I then tried various other rooting methods and obviously none worked. The phone ended up soft bricked and it was then I found that I could flash 4.4.4 or 5.0. I had assumed Odin was disabled entirely with the locked bootloader.
jellyhead said:
Yeah, I figured that out. I thought Odin wouldn't work because I first tried to flash back to 4.3 then 4.4.2. I then tried various other rooting methods and obviously none worked. The phone ended up soft bricked and it was then I found that I could flash 4.4.4 or 5.0. I had assumed Odin was disabled entirely with the locked bootloader.
Click to expand...
Click to collapse
Yeah. I did the same one time. Once you flash 4.4.4 or above it locks the bootloader. Downgrading won't fix it. Once it's locked, it's locked. Really sucks. I was working on a root method with some friends, but we all upgraded to the note 5 and S6EP... so it went to a dead stop. Too bad. There's about 20k worth of good donations for an unlock/root. Gl!

Rooted Verizon Galaxy S5 (G900V) - Upgrade from Kitkat to Lollipop and Keep Root?

I have a Verizon Galaxy S5 (G900V) that I rooted a couple of years ago and never updated any further. It's currently running 4.4.4 / NK2 and I've been looking at upgrading to a Lollipop build. I have the Toshiba 11x eMMC so it doesn't sound like Marshmallow is an option if I want to keep root. I've spent significant time rooting through the forums and I can't seem to find a method to update my phone from KitKat to Lollipop (while keeping root) that is current, has the necessary files available to download, and works. Using FlashFire and G900V_OE1_Stock_Rooted_ROM.zip followed by Odin and an OD5 bootloader is failing on my phone for whatever reason. The other methods, including muniz_ri's, don't seem to have current files available for download.
I've fried my brain searching with no success. If anyone could point me to current directions/files to upgrade from KitKat to a solid Lollipop build while maintaining my root access, it would be GREATLY appreciated.
Thank you.
I would Odin this file https://www.androidfilehost.com/?fid=24438995911970571
That will take you to stock PB1 then follow this guide to get root https://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Then I would use flash fire or LP safe strap to flash a ROM I recommended
https://forum.xda-developers.com/ve...ang5litre-edition-5-0-pb1-devnon-dev-t3381850 or https://forum.xda-developers.com/ve...enix-rom-9-0-ported-g900v-ported-rom-t3188443
OrneryTX said:
I have a Verizon Galaxy S5 (G900V) that I rooted a couple of years ago and never updated any further. It's currently running 4.4.4 / NK2 and I've been looking at upgrading to a Lollipop build. I have the Toshiba 11x eMMC so it doesn't sound like Marshmallow is an option if I want to keep root. I've spent significant time rooting through the forums and I can't seem to find a method to update my phone from KitKat to Lollipop (while keeping root) that is current, has the necessary files available to download, and works. Using FlashFire and G900V_OE1_Stock_Rooted_ROM.zip followed by Odin and an OD5 bootloader is failing on my phone for whatever reason. The other methods, including muniz_ri's, don't seem to have current files available for download.
I've fried my brain searching with no success. If anyone could point me to current directions/files to upgrade from KitKat to a solid Lollipop build while maintaining my root access, it would be GREATLY appreciated.
Thank you.
Click to expand...
Click to collapse
You have root so just skip the rooting part everything you need is here to https://forum.xda-developers.com/showpost.php?p=71202995&postcount=3
jrkruse said:
You have root so just skip the rooting part everything you need is here to https://forum.xda-developers.com/showpost.php?p=71202995&postcount=3
Click to expand...
Click to collapse
So if I'm reading that correctly, I can skip to step #9 of the "Directions For Users With CID 11' Toshiba eMMC" section and then use the EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip and VZW_BPB1_ODEX_DEODEX_V9.zip files. Is that correct?
OrneryTX said:
So if I'm reading that correctly, I can skip to step #9 of the "Directions For Users With CID 11' Toshiba eMMC" section and then use the EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip and VZW_BPB1_ODEX_DEODEX_V9.zip files. Is that correct?
Click to expand...
Click to collapse
Yes. You must have safestrap and use it to flash EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip and rom
jrkruse said:
Yes. You must have safestrap and use it to flash EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip and rom
Click to expand...
Click to collapse
Success! Now on 5.0 and PB1 with no significant issues during or after the upgrade.
Many thanks!
jrkruse said:
Yes. You must have safestrap and use it to flash EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip and rom
Click to expand...
Click to collapse
Let me add a caveat to that success story. I do notice that I don't have the Safestrap recovery option during the boot up process and it looks like this is expected behavior for Lollipop. The "Reboot to Recovery" option with the app is also not active or functional. What's the best way to get back the full Safestrap functionality? I found the below thread of yours but I'm not sure if the files and instructions are current. Thoughts?
https://forum.xda-developers.com/verizon-galaxy-s5/development/safestrap-5-0-lollipop-t3313800
jrkruse said:
Yes. You must have safestrap and use it to flash EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip and rom
Click to expand...
Click to collapse
OrneryTX said:
Let me add a caveat to that success story. I do notice that I don't have the Safestrap recovery option during the boot up process and it looks like this is expected behavior for Lollipop. The "Reboot to Recovery" option with the app is also not active or functional. What's the best way to get back the full Safestrap functionality? I found the below thread of yours but I'm not sure if the files and instructions are current. Thoughts?
https://forum.xda-developers.com/verizon-galaxy-s5/development/safestrap-5-0-lollipop-t3313800
Click to expand...
Click to collapse
I think I see where I went wrong with Safestrap but it's going to be a little while before I can investigate further. Don't want to brick my phone at work and not be able to phone home.
I'll update after I do some more troubleshooting.
Thanks again.

Categories

Resources