I've got a S4 AT&T running OK2 with root and it ran my AirVoice Wireless SIM perfectly fine for a month while I researched and got a new phone. I'd now like to use it as a backup phone with a FreedomPOP SIM but it's giving me grief about "SIM network unlock PIN". This is the carrier lock correct? I found a tutorial that has you go into the Service Mode and turn off NETWORK LOCK. This tutorial doesn't seem to work (missing the options) in OK2. Do I have to downflash to 4.2.2 in order to get these options? If so, how do I go about doing that? I put OK2 with root on this phone but that process took 2 days and with all the mixed info out there and different versions, it's confusing to say the least.
My other question is, I tried flashing TWRP (jflteatt) and I believe I ended up with the "software not authorized by AT&T" error. Doing some reading, it looks like this may be due to not using a loki'd TWRP?
Any pointers/tips would be much appreciated. All this Samsung stuff is way over my head despite having rooted, recoveried and rom'd maybe a dozen Android devices. I much prefer LG and Moto
natenkiki2004 said:
I've got a S4 AT&T running OK2 with root and it ran my AirVoice Wireless SIM perfectly fine for a month while I researched and got a new phone. I'd now like to use it as a backup phone with a FreedomPOP SIM but it's giving me grief about "SIM network unlock PIN". This is the carrier lock correct? I found a tutorial that has you go into the Service Mode and turn off NETWORK LOCK. This tutorial doesn't seem to work (missing the options) in OK2. Do I have to downflash to 4.2.2 in order to get these options? If so, how do I go about doing that? I put OK2 with root on this phone but that process took 2 days and with all the mixed info out there and different versions, it's confusing to say the least.
My other question is, I tried flashing TWRP (jflteatt) and I believe I ended up with the "software not authorized by AT&T" error. Doing some reading, it looks like this may be due to not using a loki'd TWRP?
Any pointers/tips would be much appreciated. All this Samsung stuff is way over my head despite having rooted, recoveried and rom'd maybe a dozen Android devices. I much prefer LG and Moto
Click to expand...
Click to collapse
Yeah you're carrier locked. I think you can only downgrade to NB1 from OK2, not sure you can carrier unlock on NB1 or not. As for installing TWRP you can't due to the locked bootloader. You can only use safe strap recovery and boot only custom touch wiz roms. Loki only works on the MDB and MDL bootloaders, once you've upgraded the bootloader past MDL, you can't go back.
If the AT&T phone is like the i337m and m919, you may be able to flash down to 4.4.2, flash a 4.2.2 modem, root, run regionlockaway, upgrade modem back to 4.4.2.
Thanks for the replies. I grabbed NB1 from here: https://forum.xda-developers.com/showthread.php?t=2616221
and flashed it via Odin. All went well but when it came time to follow various instructions I found online, they either yielded no unlock or the options weren't in the menu. I don't think the free unlock trick via the service menu works on 4.4.2/NB1.
I researched a bit more and feel very stupid with one of the results that came up... AT&T offers online unlocking of their devices and you don't even have to be one of their customers! I figured I could go to one of their retail stores but also figured they would deny me since I'm not a customer. I'll be jiggered though, here it is: https://www.att.com/deviceunlock/
Slapped my IEMI in with my e-mail and in less than an hour or so, I got my unlock code for free. AT&T said they would e-mail it but I checked back on the status page and found the code there. Hopefully this helps other people.
So, moving forward now, is OK2 the best I can do with a locked bootloader? I ran it for a while but I found that I burned through my data real quick because when I would leave my WiFi coverage and come back, it would reconnect but for some reason wouldn't actually use WiFi (data was still on, had the 4G icon) until I restarted the phone. Basically, every time I left and came back home, I had to restart my phone. Is this a known issue, did I botch something in the install process? I may make another thread for this.
*EDIT*
Running OK2 for a while, I no longer have the WiFi issues I had before. Doing some thinking, I can only attribute the issue to either incorrectly followed steps the first time around flashing OK2 or the use of the debloater script found in the OK2 downloads thread. I've been using Link2SD to remove system apps and so far haven't removed anything that has affected WiFi.
Related
Hi,
I bought an S4 which was previously rooted. Last owner unrooted it and used triangle away to make sure all was as stock looking as possible.
Last week I did a factory reset on the phone as I was having issues with it. After the reset it shows all the stock apps and standard Rogers bloatware. BUT it now has a couple of Bell Bloatware apps as well!!!
I need to send the phone in for repair as I am getting "intermittent SIM card not detected, phone is restarting error". Should I be worried that Samsung will detect that the phone was at one time rooted?
What should I do?
Thanks
rezadue said:
Hi,
I bought an S4 which was previously rooted. Last owner unrooted it and used triangle away to make sure all was as stock looking as possible.
Last week I did a factory reset on the phone as I was having issues with it. After the reset it shows all the stock apps and standard Rogers bloatware. BUT it now has a couple of Bell Bloatware apps as well!!!
I need to send the phone in for repair as I am getting "intermittent SIM card not detected, phone is restarting error". Should I be worried that Samsung will detect that the phone was at one time rooted?
What should I do?
Thanks
Click to expand...
Click to collapse
When the last owner unrooted the phone, they likely used one of the odin files from here which are all Bell based for I337M (Canadian S4). There is a thread in here where this happened to another user and they returned the phone to stock Rogers instead of Bell, you will need to search for that thread. The bigger concern is Knox is probably tripped on the phone, when it boots up there will be some tiny text it the top left corner, yellow and red I believe, there is a thread about that here too.... If Knox is tripped (pretty sure it is) then all you can do is try to get it repaired by Samsung, I wouold be interested to find out if they do it or not.....
Thanks for the reply.
I shut the phone down and then turned it back on, paying close attention to evenrything. There is no small text in any corner. What is odd id that the phone goes through its boot sequence, gets to the lockscreen, and then goes through the boot sequence again a second time.
And for clarification, I have all the Rogers bloat, but I have three Bell bloat apps too!
I will do a search again to see if I can find the threads you have mentioned.
Gage_Hero said:
When the last owner unrooted the phone, they likely used one of the odin files from here which are all Bell based for I337M (Canadian S4). There is a thread in here where this happened to another user and they returned the phone to stock Rogers instead of Bell, you will need to search for that thread. The bigger concern is Knox is probably tripped on the phone, when it boots up there will be some tiny text it the top left corner, yellow and red I believe, there is a thread about that here too.... If Knox is tripped (pretty sure it is) then all you can do is try to get it repaired by Samsung, I wouold be interested to find out if they do it or not.....
Click to expand...
Click to collapse
rezadue said:
Thanks for the reply.
I shut the phone down and then turned it back on, paying close attention to evenrything. There is no small text in any corner. What is odd id that the phone goes through its boot sequence, gets to the lockscreen, and then goes through the boot sequence again a second time.
And for clarification, I have all the Rogers bloat, but I have three Bell bloat apps too!
I will do a search again to see if I can find the threads you have mentioned.
Click to expand...
Click to collapse
You have to go into download mode to see the text.
Sent from Black<3's I337 running Foxhound ROM
Put the phone in download mode and no small text.
Now that the phone is not rooted, can I put it in download mode, attach it to a PC and flash a stock Rogers 4.3 ROM via ODIN? Do I need root for this?
rezadue said:
Oh, and one other question. Now that the phone is not rooted, can I put it in recovery mode, attach it to a PC and flash a stock Rogers 4.3 ROM via ODIN? Do I need root for this?
Click to expand...
Click to collapse
Not to ODIN it no. Root not required.
Found the other thread, you have spoken of. It seems like that guy got bloatware from Bell INSTEAD of Rogers. I have blaotware from Rogers(ok
) AND Bell(Not ok).
http://forum.xda-developers.com/showthread.php?t=2422497
Almost same issue here on my N900W8. My phone is working fine and rooted, except I got the Rogers AND Bell apps too before rooting and flashing CWM (only way I knew of at the time to force boot following seandroid enforcing error). I data wiped, downloaded and flashed the labeled "Rogers" stock ROM from SamMobile, and first time I ever saw bloatware from two carriers on any phone.
I disabled the Bell apps thinking that was all, but instead of 4G, I get H+. LTE connects fine outdoors, but H+ seems slightly slower than the 4G I'm used to. Which makes me wonder if LTE speeds are impacted too, hope not. Anyway, it's a bother because I am rarely in an LTE zone.
Tomorrow, I will try unrooting with SuperSU (is this even important if I'm wiping & flashing?), data wiping with CWM, re-flashing same file from SamMobile and not flashing anything more, and trying emergency recovery with Kies. Anyone know if this will work or change anything in the end? Or is Kies 3 also affected by the Knox counter? CSC (OYA) is the same as the non-rooted up-to-date S4 in the house.
Thanks
OP, have you tried using someone else's SIM card? Just a thought.
Hi everyone, long time reader, first time poster.
First of all, i want to let you all know how i appreciate all the hard work you guys do on here. i was able to get all the info i needed to get my ATT n7105 back to stock after running CM 10.2 for the last year on it.
Back on topic...i have an S4 i337 running 4.3 MK2. when i first flashed it, for the longest time i couldnt figure out why i couldnt get signal or wifi, and found out needed to flash the MK2 modem firmware also (thanks for the info on that also). now the issue i am having is that now the phone has no sound at all, tried playing music, recieving a call (which makes the phone go total bonkers too), or even the beep it makes when adjusting the volume. I have tried searching for info on sound issues, but that was one thing i was unsuccessful with.
when i first got the phone, it had 4.2.2 (not sure of the firmware) and wanted to unlock it to use any carrier rather than just ATT. the only way of unlocking it, rather than getting an unlock code, was to go into service mode, and navigate through some menus, but i read that with 4.2.2, i could not, so i done an /ota update, which brought me straight to 4.4.3. after the unpdate, tried doing the service mode again, and had no luck, so tried downgrading to 43].3, than went to hell trying to get it working, untill coming across these forums, and got it working again with 4.3 MK2, but as mentioned, with no sound.
Any advice on what to try?
Thanks in advance.
RTyper56 said:
Hi everyone, long time reader, first time poster.
First of all, i want to let you all know how i appreciate all the hard work you guys do on here. i was able to get all the info i needed to get my ATT n7105 back to stock after running CM 10.2 for the last year on it.
Back on topic...i have an S4 i337 running 4.3 MK2. when i first flashed it, for the longest time i couldnt figure out why i couldnt get signal or wifi, and found out needed to flash the MK2 modem firmware also (thanks for the info on that also). now the issue i am having is that now the phone has no sound at all, tried playing music, recieving a call (which makes the phone go total bonkers too), or even the beep it makes when adjusting the volume. I have tried searching for info on sound issues, but that was one thing i was unsuccessful with.
when i first got the phone, it had 4.2.2 (not sure of the firmware) and wanted to unlock it to use any carrier rather than just ATT. the only way of unlocking it, rather than getting an unlock code, was to go into service mode, and navigate through some menus, but i read that with 4.2.2, i could not, so i done an /ota update, which brought me straight to 4.4.3. after the unpdate, tried doing the service mode again, and had no luck, so tried downgrading to 43].3, than went to hell trying to get it working, untill coming across these forums, and got it working again with 4.3 MK2, but as mentioned, with no sound.
Any advice on what to try?
Thanks in advance.
Click to expand...
Click to collapse
You don't have sound or the ability to call because your bootloader and non-hlos don't match. You can get sound by flashing the NB1 or NC1 modems(including non-hlos.bin) but that will break your wifi which can be fixed by using bypasslkm.
Sure, ill give that a try.
What if i were to update it to 4.4.3? any certain modems required there?
muniz_ri said:
You don't have sound or the ability to call because your bootloader and non-hlos don't match. You can get sound by flashing the NB1 or NC1 modems(including non-hlos.bin) but that will break your wifi which can be fixed by using bypasslkm.
Click to expand...
Click to collapse
Whenever i tried flashing NB1 or NC1, i get an error saying "signature verification failed, then later on give an error "unknown path \sdcard1" after wiping data, then reboots. and when the phone rebooted, it goes through the first time setup after a wipe, and then checking the modem, and its still NK2.
I really would like to get it to the current version.
RTyper56 said:
Whenever i tried flashing NB1 or NC1, i get an error saying "signature verification failed, then later on give an error "unknown path \sdcard1" after wiping data, then reboots. and when the phone rebooted, it goes through the first time setup after a wipe, and then checking the modem, and its still NK2.
I really would like to get it to the current version.
Click to expand...
Click to collapse
Follow these instructions to get to Stock, Rooted NC1: http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3
muniz_ri said:
Follow these instructions to get to Stock, Rooted NC1: http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3
Click to expand...
Click to collapse
Awesome! thank you very much
With the instructions you provided, i was able to get my i337 in working order.
your assistance is greatly apreciated
Hi everyone,
Its been a long time since the bootloader was version MDL. As you may be aware this was the last version that could be fully rooted and custom recovery'd before the MF3 firmware locked everybody down. Well a year and a half later and my MDL Phone is having an issue that I can't fix. The Phone keeps failing to recognize the SIM card that is in it (Image), and previously it would randomly disconnect (Image). I've tried getting a new SIM card and that failed to fix the issue; I clean-installed by ROM to eliminate that as a cause, but no luck.
I'm fairly sure my only option now is to go to AT&T and have them fix or more likely replace the phone. Is there any possible way I could get a phone with MDL still? Or are there any alternatives I could try? I don't know what to do now. Thank you.
Tryer1234 said:
Hi everyone,
Its been a long time since the bootloader was version MDL. As you may be aware this was the last version that could be fully rooted and custom recovery'd before the MF3 firmware locked everybody down. Well a year and a half later and my MDL Phone is having an issue that I can't fix. The Phone keeps failing to recognize the SIM card that is in it (Image), and previously it would randomly disconnect (Image). I've tried getting a new SIM card and that failed to fix the issue; I clean-installed by ROM to eliminate that as a cause, but no luck.
I'm fairly sure my only option now is to go to AT&T and have them fix or more likely replace the phone. Is there any possible way I could get a phone with MDL still? Or are there any alternatives I could try? I don't know what to do now. Thank you.
Click to expand...
Click to collapse
I wouldn't go to at&t. The first thing they'll do is "upgrade" you to nj4. You said you Chan installed the rom, does that mean you odin'd the stock firmware? If not I'd flash the mdl firmware in Odin
Sent from my Nexus 9 using XDA Free mobile app
Well, there are several options; if you are on mdl, with a custom recovery like CWM or TWRP, you can flash updated modem firmware (see http://forum.xda-developers.com/showthread.php?t=2496517), to see if it is just the firmware (this will not affect the bootloader); you might also be suffering from the "sim removed" problem, documented here and here
Good luck!
Hi, I have been trying to get my s4 i9505 networked unlock. It's currently on EE. I bought it from someone who has gone abroad so can't ask them to get ee to do it. I have tried 3 online unlocking sites, the last was recommended on here but non of them can do it. I have tried to install several firmwares but hoping that would remove the ee lock But they all seem to be ee firmware. Is there a firmware that you can tell me about which will do what I want. Or is there a way I can conect to my computer and do a hardware unlock. Hope someone can help as getting desperate now.
A friend of mine has a insurance supplied s4 i9505 Which is unlocked. Is there a way we can copy the firmware on his and install on my or completely clone the phone . ?
Installing firmware will not remove a carrier unlock. Downgrading firmware from Android 4.4.2 to Android 4.2 may work if attempting to use the free unlocking methods on the forums. Naturally, using those methods have risks, up to and including totally bricking the phone. The carrier lock mechanism is part of the modem firmware as RegionLock Away modifies the modem when it functions. Hardware unlocking probably can be done, but I couldn't tell you how it's done. I also can't tell you if copying your friend's modem will help your cause. I CAN tell you that completely cloning his phone is completely illegal and you could render both his and your phones completely useless by trying it.
Strephon Alkhalikoi said:
Installing firmware will not remove a carrier unlock. Downgrading firmware from Android 4.4.2 to Android 4.2 may work if attempting to use the free unlocking methods on the forums. Naturally, using those methods have risks, up to and including totally bricking the phone. The carrier lock mechanism is part of the modem firmware as RegionLock Away modifies the modem when it functions. Hardware unlocking probably can be done, but I couldn't tell you how it's done. I also can't tell you if copying your friend's modem will help your cause. I CAN tell you that completely cloning his phone is completely illegal and you could render both his and your phones completely useless by trying it.
Click to expand...
Click to collapse
Thank you for the reply, can I install a modem . I think I have read that you can't down grade the firmware ? If this is wrong. Where can I find the 4.2 firmware . Thanks
You can try, but I don't believe it will help any. While I said that the carrier lock is part of the modem firmware, it's not as simple as installing new modem firmware. The modem firmware that people commonly install really only controls the radios, while the carrier lock is in a different part. That part doesn't usually get touched by a new firmware install. In my experience, the carrier lock reared its ugly head when I destabilized the NV memory of my S4, which caused a reset to the golden backup in the phone.
I also had a SIM tray issue which popped up at the same time, and only by rolling back the firmware to 4.2.2 was I able to get to a stage to unlock the phone, using RegionLock Away. It is possible to roll back the firmware itself, but you cannot roll back the bootloader. Using old firmware with a new bootloader results in a "Kernel is not SEAndroid Enforcing" complaint upon boot.
To cut this down to basics, you can install a 4.2.2 modem and attempt one of the unlock methods available, as long as you are fully aware of the risks involved. If you choose this route you can download a modem from the appropriate thread on XDA and install it through Odin. You'll need to do a search to find it, but it shouldn't be too difficult. Full ROMs are available from www.sammobile.com or www.samsung-updates.com.
Strephon Alkhalikoi said:
You can try, but I don't believe it will help any. While I said that the carrier lock is part of the modem firmware, it's not as simple as installing new modem firmware. The modem firmware that people commonly install really only controls the radios, while the carrier lock is in a different part. That part doesn't usually get touched by a new firmware install. In my experience, the carrier lock reared its ugly head when I destabilized the NV memory of my S4, which caused a reset to the golden backup in the phone.
I also had a SIM tray issue which popped up at the same time, and only by rolling back the firmware to 4.2.2 was I able to get to a stage to unlock the phone, using RegionLock Away. It is possible to roll back the firmware itself, but you cannot roll back the bootloader. Using old firmware with a new bootloader results in a "Kernel is not SEAndroid Enforcing" complaint upon boot.
To cut this down to basics, you can install a 4.2.2 modem and attempt one of the unlock methods available, as long as you are fully aware of the risks involved. If you choose this route you can download a modem from the appropriate thread on XDA and install it through Odin. You'll need to do a search to find it, but it shouldn't be too difficult. Full ROMs are available from www.sammobile.com or www.samsung-updates.com.
Click to expand...
Click to collapse
Ok thanhs you the info , looks like I'm a bit stuck . I don't really understand why the unlocking sites can't generate a Code. If I put another sim into the phone it doesn't tell me I an incorrect sim .
unlock
Is there anyone on here in uk who can offer to unlock this phone for me
I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
bkenobi69 said:
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Try to dial *#0808# in the stock phone application.
You should see a menu with several options.
Select "MTP+ADB" under USB settings and press "OK".
Then you'll be able to connect your phone via MTP or ADB to your PC.
If there's no menu, then (assuming you're rooted) open a good file browser (ES, Root Explorer or something) and open the file /efs/carrier/HiddenMenu (it's a simple text file) and replace OFF with ON there.
Save the changes and reboot the phone.
Now the menu should be operational.
Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.
bkenobi69 said:
Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.
Click to expand...
Click to collapse
Currently root is impossible for MM on G900V CID11.
Impossible means you cannot gain it now, most likely it's forever.
There's no internet site which can help.
You must choose: root on LP or unrooted MM.
You must decide if you want a stock ROM or something (TW-based) else too.
It's a good idea to flash and use a stock firmware for the time while you're thinking.
Interesting... I guess I must have been reading things wrong because I thought I could go to MM with root. I'll try going to Lollipop then but first I'm going to just flash back to JB 4.4.4.
I downloaded 4.4.4 from Samsung and was going to write it with Odin, but it says FAIL when I try to flash. I suspect I just tripped Knox...
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
I'll look around to find a guide, but if you have a suggestion, I'd certainly listen!
bkenobi69 said:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Click to expand...
Click to collapse
This means that you've upgraded your phone's firmware while experimenting.
Now you cannot directly flash 4.4.4 with Odin, you're limited to 5.0 (BOK3) and above.
Ok. I'll read the guides on the head of this list and see if I can find the right information.
FWIW, I was following the same how-to that most of the stickies point to and say is safe. I wonder how I got to a position that I'm in now when I did the same as recommended. Painiac's thread points to the same thing I did:
https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848
I think I may have tried to flash a MM stock rom though when it got into a boot loop. I suspect that would be the issue.
Bootloop is not a problem in this case.
Just reboot to the recovery and perform a factory reset from there.
The phone will boot but the first boot will take 10-15 min.
bkenobi69 said:
I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Marshmallow can not be rooted on CID 11 devices. The Samsung drivers are found here: https://www.samsung.com/us/support/owners/product/galaxy-s5-verizon You can follow the 5.0 root guide here: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529 to downgrade to 5.0. If you want to downgrade past that to a version lower than 5.0, you will still have to follow that guide then follow the instructions here (I recommend you to follow the root guide for 5.0 above then skip steps 1 and 2 on this page): https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858 . You can find stock firmwares here: https://forum.xda-developers.com/showthread.php?t=2784880 (stock firmware, kernel, and modem files) and if you get bootlooped or bricked, just reflash the combination file from the root guide. If you want to root 4.4.4, follow the downgrade method using all of the NK2 files but the flash the NGC kernel, run through the setup, then use towelroot and flash the NK2 kernel after that. If you ever get stuck on the red Verizon screen, just pop the battery out and reboot.
That's about all anyone can do and a run down of everything.
Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.
bkenobi69 said:
Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.
Click to expand...
Click to collapse
Understandable, I can't believe it is 2018 and we still haven't invented a way to compress 1.7GB into 1.7MB archives to make life easy on low connections. How is battery life on 4.4.4 and which update of 4.4.4 are you on? I've been having an issue with my phone dropping a percent every 2 minutes on 5.0/6.0. It would be nice find a version to root along with excellent battery life.
The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!
Ok, I tethered to my wife's phone and am burning her data (shhhh, don't tell her).
I grabbed all of the OC4 files, the PB1 rom, and lolliroot. I think I have everything I need so long as OC4 is a good place to end up.
bkenobi69 said:
The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!
Click to expand...
Click to collapse
Here are some files (that I been hunting for about an hour for). Just gonna reference this for future use and anyone who comes across this thread. http://rootjunkysdl.com/files/?dir=Galaxy S5
Nice find!
I have the phone up and running on stock PB1 currently. I'm going to let it sit to see what the battery is like prior to rooting. While I haven't gotten it hooked back up to my account yet nor do I have it rooted, I feel pretty confident now that I'm on the right track. Thanks!
Just to finish out this topic, I have not successfully completed attaining root on 5.0. I flashed PB1 to the phone and then followed this guide for installing KingRoot:
https://androidforums.com/threads/root-question.1120150/
I got the lolliroot files from here:
https://www.androidfilehost.com/?fid=312968873555011514
Thanks to all who offered help!
Qyuck question... I've got my phone working well bow, but there's one issue with apps I'm not sure how to address. I want to use Verizon Visual Voicemail but I can't find it on the Play store. I disabled updates so I wouldn't get the marshmallow update and break root. but, with updates turned off, VVM won't get pushed. Any suggestions?