Related
Anybody taken the same update? Universal root isn't working for me, it's saying it's a read only system. Any help??
((PROBLEM FIXED!!!)) HAVE PHONE ROOTED BEFORE, THEN USE TITANIUM BACKUP TO FREEZE AT&T APPS. Then update...enjoy still having root!
Try to flash again the older version with lg flash tool and root then.
Sent from my LG-E986 using xda app-developers app
rooting technique doesn't work
Won't take the update if you are rooted. Already tried.
Waiting for root safe confirmation before accepting an update that includes nothing more than Roms here have had for a while?
Sent from my LG-E980 using XDA Premium 4 mobile app
you should never take an update unless you're SURE it can be rooted. I bought an s4 in the store and before I left the worker updated my phone for me to, and it turns out that update is what locked down the bootloader and to this day if you have that firmware you still can't unlock the bootloader.. so before anyone accepts updates research first or you might end up with a stock phone, forever.
You can root S4 though. Big difference between unlocking boot loader and rooting lol
Sent from my LG-E980 using XDA Premium 4 mobile app
I wasn't talking about root. I was talking about the boot loader
sent from my lg g pro via tapatalk
deadenz said:
I wasn't talking about root. I was talking about the boot loader
sent from my lg g pro via tapatalk
Click to expand...
Click to collapse
That's what he's saying, basically the OP's problem differs slightly from yours in that although your phone was updated there was was still a means to root your phone even after losing the ability to unlock you boot loader. Meanwhile after updating the OP can't even get root. Someone correct me if I'm wrong though...
likemiketoo said:
That's what he's saying, basically the OP's problem differs slightly from yours in that although your phone was updated there was was still a means to root your phone even after losing the ability to unlock you boot loader. Meanwhile after updating the OP can't even get root. Someone correct me if I'm wrong though...
Click to expand...
Click to collapse
that was my whole point. don't take updates unless you research first and make sure there is a root method.
deadenz said:
that was my whole point. don't take updates unless you research first and make sure there is a root method.
Click to expand...
Click to collapse
I can CONFIRM 100% that you CAN UPDATE to 10p once you are rooted and use TITANIUM BACKUP to FREEZE the AT&T APPS. Tried twice...worked flawlessly both times. Hope I helped someone.:good:
I just rooted and updated to the P version. Kept root. I don't even have TBU installed, either, so freezing ATT apps is not a variable necessarily.
Sent from my LG-E980 using xda app-developers app
How can I force my phone to download this update if I'm rooted and on T-Mobile?
It doesn't matter if you freeze the apps. It matters if the apps are uninstalled.
Sent from my Optimus G Pro using XDA Premium 4 mobile app
Neroga said:
It doesn't matter if you freeze the apps. It matters if the apps are uninstalled.
Sent from my Optimus G Pro using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I never uninstalled them, only tried without being frozen, then with. Only updated with freezing. Not sure about uninstalling them.
Root sticks after the update. Your recovery must be stock, not CWM or TWRP. I didn't need to freeze anything, though I never deleted/disabled anything prior to the update.
What about the OP's question: Can anyone root AFTER taking the update? I assume his phone was not rooted prior to the update.
I just tried this myself on my "clean" phone and can confirm the univ root method does not work any more after the 10p update.
.
I'm having the same problem, hopefully somebody figures out a way way around this, I hate not being rooted.
Sent from my LG-E980 using XDA Premium 4 mobile app
jreed3786 said:
Won't take the update if you are rooted. Already tried.
Click to expand...
Click to collapse
looks like if your rooted but do not freeze, uninstall, or modify apps in any way that it will in fact update. Then after update go in and freeze the apps.
bailey37821 said:
looks like if your rooted but do not freeze, uninstall, or modify apps in any way that it will in fact update. Then after update go in and freeze the apps.
Click to expand...
Click to collapse
You might be on to something here! Definitely going to try tomorrow...even though I'm updated at the moment, and rooted!
well I had the similar issue as the OP. I was rooted, running CWM recovery and had removed most of the AT&T stock apps. I saw the update available and like a fool I accepted the update and then was stuck in CWM recovery boot loop. Nothing worked to get out of the loop so I decided to reflash with stock TOT file. Then I took the 10p update and found the Universal Root file not working (I updated before rooting).
I need to have root... so next try I reflash stock TOT file, root with Universal Root, accept update to 10p and all is good. I can once again remove AT&T stock apps, disable carrier-iq, use Freegees to go back to custom recovery, etc, etc, etc... all good now! :good:
FreeGee updated recently and now gives me the option to install CWM-6.0.4.7 or TWRP-2.6.3.3. Has anyone tried this yet?
morganstein said:
FreeGee updated recently and now gives me the option to install CWM-6.0.4.7 or TWRP-2.6.3.3. Has anyone tried this yet?
Click to expand...
Click to collapse
I'll tell you right now, i'm not going to try. Without knowing for sure I can have download mode back. No way
Sent from my Nexus 7 using Tapatalk
secret.animal said:
I'll tell you right now, i'm not going to try. Without knowing for sure I can have download mode back. No way
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Ha. That's what I'm waiting for.
Why aren't you wanting to try auto-rec.
http://forum.xda-developers.com/showthread.php?t=2715496
One button operation
Sent from my Nexus 7 using Tapatalk
Already answered.
Deleted.
How rude stealing my post 3 minutes before me secret.animal. lol
I have used it quite a few times and it works fine. Only thing is for me it would hang on install. I would just close the app, clear all tasks by holding down home button, run it again and it would say completed. I know that sounds weird but that used to happen on my old optimus g.
Sent from my LG-LS980 using xda app-developers app
leroybrute said:
Already answered.
Deleted.
How rude stealing my post 3 minutes before me secret.animal. lol
Click to expand...
Click to collapse
Sorry cuz, I got lucky that time.
Sent from my LG-LS980 using Tapatalk
secret.animal said:
Why aren't you wanting to try auto-rec.
http://forum.xda-developers.com/showthread.php?t=2715496
One button operation
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I've been following the AutoRec thread for a couple days and I'm a little concerned that there's no follow up yet on those white lines that some are getting. I did notice that FreeGee no longer gives me a warning about ZVC being incompatible. Any body know if this means FreeGee is now safe?
whouston.jr said:
I've been following the AutoRec thread for a couple days and I'm a little concerned that there's no follow up yet on those white lines that some are getting. I did notice that FreeGee no longer gives me a warning about ZVC being incompatible. Any body know if this means FreeGee is now safe?
Click to expand...
Click to collapse
I had no issues with autorec. But I tot, rooted then used autorec.
I'm only guessing but it could be because of that. Some that had the lines already had twrp but had broken download before they used autorec. Like I said though, it's a guess.
leroybrute said:
I had no issues with autorec. But I tot, rooted then used autorec.
I'm only guessing but it could be because of that. Some that had the lines already had twrp but had broken download before they used autorec. Like I said though, it's a guess.
Click to expand...
Click to collapse
i got white lines and I was stock rooted, ls980, 4.4.2. had to .tot back.
mtg981 said:
i got white lines and I was stock rooted, ls980, 4.4.2. had to .tot back.
Click to expand...
Click to collapse
Have you rooted again and tried autorec since?
leroybrute said:
Have you rooted again and tried autorec since?
Click to expand...
Click to collapse
I also was rooted on stock ZVC. I installed autorec and let it do its thing. First try, I could not do a backup in TWRP. It would fail everytime. Then I booted to system and thought everything was fine till the screen went off. White lines slowly appeared and stayed. Only fix was to reboot. That got boring so I tot back to ZVC and used ioroot25 to root and then installed autorec. White lines again when screen off then back on. I think waiting until the dev can figure out what is being altered on our ls980, we have to wait.
sclarktay4 said:
I also was rooted on stock ZVC. I installed autorec and let it do its thing. First try, I could not do a backup in TWRP. It would fail everytime. Then I booted to system and thought everything was fine till the screen went off. White lines slowly appeared and stayed. Only fix was to reboot. That got boring so I tot back to ZVC and used ioroot25 to root and then installed autorec. White lines again when screen off then back on. I think waiting until the dev can figure out what is being altered on our ls980, we have to wait.
Click to expand...
Click to collapse
Did you wipe cache and dalvik and try autorec again?
Seems strange that it's working fine for a lot of us and not for others.
leroybrute said:
Did you wipe cache and dalvik and try autorec again?
Seems strange that it's working fine for a lot of us and not for others.
Click to expand...
Click to collapse
I can only think there is some tweak in the modified kernel that breaks us. Ota, tot, no matter what. I can see no matter what in TWRP, but in system it fails. I gone every way.
Just have to wait a bit longer.
Sent from my Nexus 7 using Tapatalk
secret.animal said:
I can only think there is some tweak in the modified kernel that breaks us. Ota, tot, no matter what. I can see no matter what in TWRP, but in system it fails. I gone every way.
Just have to wait a bit longer.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Agreed on modified kernel.
I hope @Cloudyfa sticks around for us, to help the ones that need it. He has contributed so much to the G2 community.
My big concern is that freegee doesn't give any info as to what version of ZVC OTA it's compatible with, and neither does the autorec thread for that method. Like in the ZVA-> ZVC thread, there's a zip of the OTA... which is slightly different than getting the official OTA through system updates on the phone. So I'm afraid to try either method and end up with an unrecoverable brick because I'm on the official OTA.
Anyone on completely stock ZVC, rooted, that has successfully used either method?
agentfusion said:
My big concern is that freegee doesn't give any info as to what version of ZVC OTA it's compatible with, and neither does the autorec thread for that method. Like in the ZVA-> ZVC thread, there's a zip of the OTA... which is slightly different than getting the official OTA through system updates on the phone. So I'm afraid to try either method and end up with an unrecoverable brick because I'm on the official OTA.
Anyone on completely stock ZVC, rooted, that has successfully used either method?
Click to expand...
Click to collapse
Auto-rec works fine. The modified kernel that every app or by manual has used is the same at the time.
The worst it will do if it does not work is give you lines in your display after the screen shuts off. A reboot fixes that. But to fix completely, is to tot back to zvc and stay just rooted.
Sent from my Nexus 7 using Tapatalk
Stock rooted zvc. Auto-rec worked for me. No lines. Everything works.Just downloaded app. From download folder pressed on the app let the phone install it. Then ran it. I did not have download mode at first so reran the app and download mode worked.
secret.animal said:
Auto-rec works fine. The modified kernel that every app or by manual has used is the same at the time.
The worst it will do if it does not work is give you lines in your display after the screen shuts off. A reboot fixes that. But to fix completely, is to tot back to zvc and stay just rooted.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yep. Worked perfectly. No lines at all. Haven't tested download mode yet but system and recovery both work. Wooohoooo.
Glad to hear it worked!
Hi All,
With all the threads about bricked phones, I wanted to take the safer route and outright ask for the best method to upgrade to KitKat on a rooted phone running 4.2.2 stock? I've already 'bricked" my phone once last year doing an OTA update, so I'm trying to avoid doing that again. I know this is a noob question, but I haven't been able to locate a sprint specific guide consolidating all of the information out there. Any help is appreciated.
Sprint LS980ZV7
4.2.2 stock on a rooted phone
twrp installed
IOroot25
Kernel: 3.4.0
thadeus_d3 said:
Hi All,
With all the threads about bricked phones, I wanted to take the safer route and outright ask for the best method to upgrade to KitKat on a rooted phone running 4.2.2 stock? I've already 'bricked" my phone once last year doing an OTA update, so I'm trying to avoid doing that again. I know this is a noob question, but I haven't been able to locate a sprint specific guide consolidating all of the information out there. Any help is appreciated.
Sprint LS980ZV7
4.2.2 stock on a rooted phone
twrp installed
IOroot25
Kernel: 3.4.0
Click to expand...
Click to collapse
Use this thread for the files
http://forum.xda-developers.com/showthread.php?p=51557219
Or you can use this one to flash zvc tot file straight to phone.
http://forum.xda-developers.com/showthread.php?p=45293512
The second post as you read will give information I thought a bit more clear on Sprint.
@#***This will wipe your phone as in complete. Nothing will be left of yours. So copy anything off internal [email protected]#***
Follow the directions, use ioroot25. Root.
If you want custom recovery.
http://forum.xda-developers.com/showthread.php?p=51857807
Use auto-rec from above thread. Thank cloudyfa for putting that together.
If you reboot after and screen shuts off and you get white lines.
You might a well tot back to zvc and just root. @Cloudyfa on that same thread is working out the details to fix.
Sent from my Nexus 7 using Tapatalk
secret.animal said:
Use this thread for the files
http://forum.xda-developers.com/showthread.php?p=51557219
Or you can use this one to flash zvc tot file straight to phone.
http://forum.xda-developers.com/showthread.php?p=45293512
The second post as you read will give information I thought a bit more clear on Sprint.
@#***This will wipe your phone as in complete. Nothing will be left of yours. So copy anything off internal [email protected]#***
Follow the directions, use ioroot25. Root.
If you want custom recovery.
http://forum.xda-developers.com/showthread.php?p=51857807
Use auto-rec from above thread. Thank cloudyfa for putting that together.
If you reboot after and screen shuts off and you get white lines.
You might a well tot back to zvc and just root. @Cloudyfa on that same thread is working out the details to fix.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply. I'll give this a shot tonight!
I have a question: I already screwed up and applied the KitKat update to my rooted G2 without thinking. It's now stuck booting to TWRP, where I was a moron and of course didn't create a backup at any point. Is there a way for me to sideload the ROM onto my phone at this point?
Any ideas?
Coop1979 said:
I have a question: I already screwed up and applied the KitKat update to my rooted G2 without thinking. It's now stuck booting to TWRP, where I was a moron and of course didn't create a backup at any point. Is there a way for me to sideload the ROM onto my phone at this point?
Any ideas?
Click to expand...
Click to collapse
Even sideload may not help you, if you can access down load mode. You might get to use tot, back to stock.
But there is no stock zvc yet for ls980.
Sent from my Nexus 7 using Tapatalk
secret.animal said:
Even sideload may not help you, if you can access down load mode. You might get to use tot, back to stock.
But there is no stock zvc yet for ls980.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for that suggestion. I was able to use Download Mode to fix my G2 and then OTA the KitKat update. Your post saved my phone.
Sent from my Nexus 7 using Tapatalk
I must have gotten lucky...wasn't thinking and took the OTA a while ago. Lost root but phone is fine.
Now...I'm off to find it again so I can get tether working
thadeus_d3 said:
Thank you for the reply. I'll give this a shot tonight!
Click to expand...
Click to collapse
To the OP, can I ask which method you chose and how it went? I need to do this as well and I'm in the same boat as you (rooted ZVA with custom recovery).
Thanks.
Ed
esoh said:
To the OP, can I ask which method you chose and how it went? I need to do this as well and I'm in the same boat as you (rooted ZVA with custom recovery).
Thanks.
Ed
Click to expand...
Click to collapse
I actually read a bit more and decided to hold off on the update. I'm happy with my phone's performance, so I really don't have the time to troubleshoot should the update go awry.
thadeus_d3 said:
I actually read a bit more and decided to hold off on the update. I'm happy with my phone's performance, so I really don't have the time to troubleshoot should the update go awry.
Click to expand...
Click to collapse
I'm the same way, but I figured that I should just go ahead.
So I'll throw that out, anyone pick one of these methods have a preference? I'm on TWRP, rooted, stock ZVA. Some mods including tether and camera. Thanks.
H i all Let me start by apologizing as I'm sure I'm doing something here that I'm not supposed too. Although I am new to XDA, until recently I didn't know I was such a tech virgin.. I have spent off and on months trying to figure out why my LG G2 has prematurely entered mechanical menopause. I have read scores of articles, tried numerous "fixes", various roots etc, but I can't get it right because I can't make out what's wrong. About the phone: Sprint Lg G2 LS980 ZVE running Android 4.4.2. I rooted my phone not long after I got it, which was back before the latest updates. Unfortunately I lost my phone for several months and when I got it back it had of course been updated. When installing a root checker the phone says Not Rooted, when it's in download mode or when I tried to use Stumproot it says I'm already Rooted. Upon opening SuperSU I get this warning, "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3 you need to manually re-root - consult the relevant forums for your device." Upon opening BusyBox I get this message, "There was a problem opening a shell with root access. This is either being caused by Superuser/SuperSU or by a device that is improperly rooted. Try removing permissions, uninstalling and then reinstalling this application, blah blah blah, but of course SuperSU acts as previously mentioned when opened. I don't know what to do besides potentially flash stock but I really don't want to do that. I am a stubborn, learn by doing kind of techie but after months of learning everything but the answer, I raise the white flag. Please someone tell me there is an easy/obvious answer that I missed as I'd rather be a moron with an ignorant miss, than a stubborn ass with time consuming fixes in my immediate future.
Thank you so much, Jo
You will have to use the zve tot that's the only way to fix it, then stump will work perfectly.
Sent from my LG-LS980 using XDA Free mobile app
Thank you
I have gone through the process of flashing back to stock twice now and both times it ends in an error that says there is no kdz file. Any advice please?
Kdz is for Verizon or other carriers. Sprint is strictly tot. Make sure you are following the right directions.
Sent from my LG-LS980 using Tapatalk
i would suggest zv8 and root and custom recovery , after the zvc onto zve,zvd root with stumproot, also do not upgrade(OTA) on a custom recovery, i would hightly consider, downgrade to zv8 updgrade all the way to zvd stumproot and then install custom recovery
Even better, downgrade zv8, root via ioroot25, install auto-rec.
Flash upgraded TWRP, flash resurrection remix, gapps. And be done with it.
Sent from my LG-LS980 using Tapatalk
secret.animal said:
Even better, downgrade zv8, root via ioroot25, install auto-rec.
Flash upgraded TWRP, flash resurrection remix, gapps. And be done with it.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
yup that is the right way^ thats what i have done i always downgrade because most people who try to get there MSL dont realize you can get it be downgrading to zv8 root and install the recovery, all on that version.
Do you lose band 26/41 LTE by running zv8? I agree with above, must use a tot file to return to stock, then root will work.
secret.animal said:
Even better, downgrade zv8, root via ioroot25, install auto-rec.
Flash upgraded TWRP, flash resurrection remix, gapps. And be done with it.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
How stable is this ROM? Does GPS and everything work on it? Only thing stopping me from doing this is losing stability of stock.
KelevrA_8 said:
How stable is this ROM? Does GPS and everything work on it? Only thing stopping me from doing this is losing stability of stock.
Click to expand...
Click to collapse
I've had no issues and funny thing you ask about GPS. I have never had an issue with any rom with GPS. Though many others do.
secret.animal said:
I've had no issues and funny thing you ask about GPS. I have never had an issue with any rom with GPS. Though many others do.
Click to expand...
Click to collapse
Good deal
Hi all,
I'm running a Sprint Note 2 (SPH-L900). I finally bit the bullet this week and upgraded from CM 11 to CM 12.1. However in the upgrade from KitKat to Lollipop, I seem to have lost root. I tried reinstalling SuperSU via both apk and by flashing in Philz recovery, but whenever I reopen SuperSU, I get a message that says "The SU binary is missing and SuperSU cannot install it. If you recently upgraded to Android 5.0, you need to manually re-root. Please consult the forums."
I've looked in the forums, but it seems like the answer that worked for most people is to flash SuperSU from recovery, which I have already done. Do I have to flash a file again through ODIN download mode like I did when I first rooted? If that's the case, can I flash a file which includes CWM on top of Philz that I already have, and will that be compatible with Lollipop?
I'd like some guidance so I don't accidentally brick my phone. Thanks for any guidance in advance!
Well all 5.1.1 roms come rooted. You just have to enable developer options (google it) and allow root for apps. If you want supersu then you need the newest version which only the new twrp has (although I think there is still issues with twrp for our device). I suggest using CyanideL if you like cm. CyanideL can be found under the development section.
FYI there is almost no brick on this device that cannot be recovered from. Flashing roms/recoveries/kernels are no real worries.
Sent from my GT-N7105 using XDA Premium 4 mobile app
jlmancuso said:
Well all 5.1.1 roms come rooted. You just have to enable developer options (google it) and allow root for apps. If you want supersu then you need the newest version which only the new twrp has (although I think there is still issues with twrp for our device). I suggest using CyanideL if you like cm. CyanideL can be found under the development section.
FYI there is almost no brick on this device that cannot be recovered from. Flashing roms/recoveries/kernels are no real worries.
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. I forgot about developer options; did that and set option to all Root Access for Apps only, but my apps still don't have root. Any other ideas?
pillzbury said:
Thanks. I forgot about developer options; did that and set option to all Root Access for Apps only, but my apps still don't have root. Any other ideas?
Click to expand...
Click to collapse
My other suggestion is not to use stock cm.
Sent from my SPH-L900 using XDA Premium 4 mobile app