VZ LG GPad 8.3 OTA VK81024A - G Pad 8.3 General

04/17/2015 Update to this posting; -24A OTA rooted 1st time using Stump after dozens of Brute Force fails on 23A-
Can anyone else confirm Stump Root working for 24A on their own devices?
Original Stump Thread; http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
New OTA software update VK81024A just released this week. From what I've read and VZW's PDF, the only thing that was changed was 4G LTE coverage. In my experience with Verizon, they only release updates for this device to patch root methods and add bloat. This would have been my 3rd update to my GPad (had I accepted) without measurable positive impact. I personally cannot believe that they spent the time and money to fix LTE coverage that, in my experience, had no noticeable issue to begin with.
I would still be waiting for Lollipop on my VZ G3, if I didn't go ahead and root/ROM just last month. With the Lollipop ROM being available to the Korean G3 as early as November of LAST YEAR, my faith in Verizon getting us the updates we want and deserve (I purchased a flagship phone, and a popular tablet) is nonexistent.
Okay, I'm done ranting (for now) about the "Great Satan" that is VZW...the only carrier with good coverage here in my area of NY. Does anyone have any experience with this update? Anyone try rooting it (maybe Stumproot will start working again)? I am tempted to accept it if I could assist the community by doing so. Please tell me your thoughts.

VK810 OTA update from 23A to 24A keeps root
For both of my VK810 tablets on 23A:
Previously rooted 4.4.2 w/ Stump.
SuperSU marked w/ "survival mode". Given my history with the LG G3 keeping root w/o needing "survival mode", I doubt that setting "survival mode" was necessary. However, given the pain I went through to root one of my VK810 tablets right out of the box, I decided to keep it set.
The OTA update (still v4.4.2) to VK810-24A kept root.
The referenced Verizon web page ( http://www.vzw.com/lggpadsupport ) for update info shows very minor changes: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-4-1-15.pdf

Just got mine this morning. Hadn't been using the tablet for a few days. Would not take OTA. Downloaded the file but kept kicking an error. Ended up hooking it up USB and using the upgrade assistant. Paranoia got the better of me and I "unrooted" first. Brute force stump (climbed to 6800 I think) did the trick just like before. Must say I was disappointed. I had not read what the "upgrade" consisted off but figured since they jumped from 23A to 24A it would be something substantial. I notice some minor cosmetic changes but that's about it. The 4gLTE "Update: or "Upgrade" isn't going to make much difference in my neck of the woods. 3G is about the best you can hope for here in this little town for the time being.

DeanGibson said:
For both of my VK810 tablets on 23A:
Previously rooted 4.4.2 w/ Stump.
SuperSU marked w/ "survival mode". Given my history with the LG G3 keeping root w/o needing "survival mode", I doubt that setting "survival mode" was necessary. However, given the pain I went through to root one of my VK810 tablets right out of the box, I decided to keep it set.
The OTA update (still v4.4.2) to VK810-24A kept root.
The referenced Verizon web page ( http://www.vzw.com/lggpadsupport ) for update info shows very minor changes: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-4-1-15.pdf
Click to expand...
Click to collapse
Did the same thing as you, OTA installed and still rooted

This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.

Anthony-m said:
This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.
Click to expand...
Click to collapse
On every Android device, if you want to take an OTA, you have to either be 100% stock, or at least have stock recovery, kernel, bootloader, and other partitions, and only have done minor things with the system partition - not have debloated at all.
Sent from my VK810 4G

Anthony-m said:
This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.
Click to expand...
Click to collapse
If the LG Mobile Support Tool factory restores the whole phone (recovery included) then this may be the best option till someone posts the KDZ with rooted 24A. This was my root method and it may work for you.
After searching through forums for weeks looking for viable root options (rollback and Purplerake or Towelroot, ADB scripting, and all others) and running Stump as often as I remembered (probably 30 times on 23A) I finally have it! I didn't see any up to date threads on rooting the VK810 and all the old threads had too many broken links to actually perform the steps.
Here's how it went down;
1.) Installed the latest LG USB drivers from LG's site ( http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427 ).
2.) Download LG Mobile support tool ( https://docs.google.com/file/d/0B687...p2NlhhalU/edit ).
3.) Run the LG Mobile Support Tool program.
4.) Switched tablet USB mode to "Internet Connection / Ethernet" and after a few moments the LG Tool recognized my VK810.
5.) In LG Tool, click on "Options -> Upgrade Recovery" on the upright corner.
6.) It should start downloading stock firmware right away, if it says "Downloading" but there is no file size or progress, then you need to disable firewall.
7.) After the download, it will start "Upgrading".
8.) When the tablet rebooted I was on the latest VZW VK81024A which shocked me because I thought it was going to put the factory image (JB 4.2), but not to give up hope, I retried Stump...1st time rooted the thing!
9.) Followed Stump Root's directions (Reboot after app tells you to, Install SuperSU APK from market, Uninstall StumpRoot) and poof!
10.) Enjoy rooted 24A KitKat
It is very possible that 24A broke the fix VZW had for 23A (even though many people had success with 23A) and one need only take 24A OTA to Stumproot if they were not able to prior, but this is how my experience went down.
MANY thanks to @roirraW "edor" ehT, @jcase, & @jim380 for producing the threads and software that led to my rooting.

Related

No OTA updates after restore to Stock Firmware

Hey all,
Having a small issue with my Verizon LG G2.
When I first got it on launch, I rooted it, installed loki (to bypass the locked boot loader) and have been running custom ROMs.
This is the way I ahve been running it since, on 12B, with loki and CM11.
Before I installed custom roms I did a image backup using Clockwork.
Yesterday I bought a Droid Turbo, so it was time to restore the G2 in preparation for sale.
I attempted to restore my original backup of the stock image, but it failed (stating something about an inability to restore/system, resulting in a soft bricked phone.
I fixed this by downloading the LG Flash tool, and the stock 24A .kdz image, putting the phone in download mode and flashing it.
The LG flash tool seemed a bit buggy, complaining about not finding servers, but eventually flashed the phone with the .kdz.
Everything seems to have worked well. Root is gone, clockwork is gone, (and I assume loki is gone as well, but I can't tell) but now I can not do the latest OTA updates, and am stuck on 24A.
It's not that it downloads the OTA, and then fails to install it, but rather it complains that it is unable to download the updates at all.
I was thinking this might have something to do with the fact that the CDMA radio is now unactivated (since I got a new phone) and it somehow needs to verify with the Verizon network prior to downloading, so I grabbed a working SIM and popped it it in. Even with 4G via the SIM, the OTA downloads don't succeed.
Does the CDMA radio need to be activated in order for a phone to receive OTA updates? If not, I ahve something else wrong going on, and would appreciate any suggestions regarding fixing it.
The plan was to sell the LG G2 to pay for my Droid Turbo upgrade, but I don't want to sell the phone to someone if I think it may be having issues.
I would appreciate any thoughts and suggestions from you guys!

OTA update when rooted D855

Hey, I have a LG D855, and I'm rooted on A6NL D855 V10G. My phone suggested to OTA update to V10I. Now I want to know if it's safe to do so. And if that's the case, what would happen to my root? I'd actually be glad to be rid of my root since I think it's lagging my device. So, what exactly would happen if I updated? Anybody with experience?
Would think although showing an ota when you download it it won't install as it will detect your root. In order to update you will have to return to unrooted state. A search will show a couple of threads instructing how to.
From what I understand, as long as you haven't made any changes within the system folder or installed a custom recovery, the OTA should install just fine. Worst case is if anything has been changed, it will tell you and it won't install. But yes, you will lose root once it is installed.
root and ota should be ok.
but be very careful if your g3 is bumped!! if you had installed bump! on your device, an ota update fails and the reboot always ended in the recovery. i tried almost erverything - no way out. i had no chance to reboot into the system!!
only flashing back to stock had fixed the problem (incl. loosing all personal data).
kd
Mendeltje1313 said:
Hey, I have a LG D855, and I'm rooted on A6NL D855 V10G. My phone suggested to OTA update to V10I. Now I want to know if it's safe to do so. And if that's the case, what would happen to my root? I'd actually be glad to be rid of my root since I think it's lagging my device. So, what exactly would happen if I updated? Anybody with experience?
Click to expand...
Click to collapse
When u are rooted, it will download the new update (ota), but it will give a error when it installs. You have to update via pc.
Sent from my LG-D855 using XDA Free mobile app
Just had this happen to me on LG G3 for AT&T
Was rooted, got prompted to install the update, I kept declining until it stopped asking.
Then my phone died, after plugging it in and restarting my phone, it instantly jumped into the update window with no other options.
It updated automatically, and it didn't stop or error because of my root. I'm on 4.2.2 now, most up-to-date version on AT&T.
To make it clear: I'm rooted with TowelRoot, NOT with Bump!

SM-G870A Failing to Update Past 4.4.2

Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
MGArcher007 said:
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
Click to expand...
Click to collapse
Have you resolved this issue, if so, would you mind sharing how you did it. I've been combing the net for a few days trying to discover what is going on and your issue appears to be exactly what I am experiencing. I've read about flashing back to my stock firmware using Odin but I cannot get into download mode, when I try and get there, the phone only says "recovery reboot" in blue small font on the top of the screen and reboots.
Thanks
Ladies and gents, I apologize for abandoning this thread. I forgot exactly how I got to get the phone to update, but if I recall correctly, it had to do with me putting the phone in download mode, downloading the original firmware and using ODIN to flash it. Afterward, the "unlocked" padlock symbol disappeared and the phone was able to get the OTA update from AT&T.
I have since moved from an LG G4 to a V20 and that is what I am currently playing with. I also have a Samsung Galaxy S6 Edge (which T-Mobile replaced my G4 with when the touch screen stopped responding). I was quite stoked to find out that there is a way to root it and (seemingly) unlock the bootloader, so I'll be toying with that this weekend to see what I can do. I'd love nothing more than to just wipe that Samsung-ified Android and install a vanilla Android or CM.
Good luck to anyone who is still trying to fix this issue. Again, my apologies. I'll dig through my archives and see if I can piece together what I did to get it going again. I still have the S5 Active. Best phone by far. It's a great backup phone for when the new stuff goes kaput.

(Soft?)-Bricked My S7 with a Flashfire Update, Need Help to Fix It?

So I've been rooting me phone for a while and have managed to never f*** up, till now, and I sincerely hope you guys can help me.
After rooting my S7 a while back, I just recently noticed SuperUser telling me that I didn't have root anymore, so I decided to follow these instructions to re-root my phone:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I successfully followed all the steps to get root, but when I opened Flashfire it told me I could install a new update while maintaining root, so since my android is at 6.0.1, I did that and it bricked my phone.
On boot it says "Startup Failed - Use the Verizon Software Repair Assistant . . . " and on top it also says "Custom binary blocked by SECURE BOOT." I have tried going into recovery mode and deleting the system cache, but that doesn't do it. So is there any way to get the phone to properly boot while not deleting my data? I was rooting my phone precisely so I could use Titanium Backup again, so I don't have any backups stored anywhere. I have heard that flashing a recovery image with Odin can work, but would that delete my files? Someone please lend me your expertise.
My phone is a Verizon S7.
Fixed
I am surprised that no one responded to me, but what's important is that, miraculously, I managed to un-brick the phone myself without losing any data! What I did was, as my last hope (since Odin wasn't able to flash the stock image, a la the traditional soft-brick fix), decide to follow the on-screen instructions my phone was giving me and to download and run something called the "Verizon Software Repair Assistant," which can be found in the top google results after searching for the quoted name (xda doesn't let me post the link).
After putting my phone into download mode, I plugged it in, ran the software and let it work overnight. Checking on it in the morning, I found my phone, not only completely functional and working, but updated to Android 7.0 (it was 6.0.1 previously before the failed Flashfire OTA update) and still holding all of my data intact.
So, the interesting thing that I learned is that flashing to stock via Odin to fix a soft-bricked phone should not be the default resolution for potentially most people, as the carrier's default (in my case, Verizon's) repair utility managed to completely fix my phone without any side effects or data loss.
Is there anyone who could chime in on why the Repair Utility did not wipe my phone's memory, even though it warned it would?
**Note**
Verizon links to the Windows version of the repair assistant on their site, but to get the Mac version (which I used), the only way you can get it is by changing the end of the url they mention within the thread from "Win" to "Mac."
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
*Detection* said:
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
Click to expand...
Click to collapse
I guess I am not acquainted with this forum enough then, thanks!
Most likely the cause of the fault would be updating via FlashFire and keeping root. When the update was flashed, it most likely flashed the stock kernel and patched it for root, which is not a compatible root for our devices. Flashing the root kernel with Odin probably would have made the phone boot normally.

GS5 verizon 4.4.4 to rooted marshmallow

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?

Categories

Resources