Related
Hi,
I have had my lg Optimus G for quite sometime now, almost since it came out. I have had it rooted since day 1 of owning it. We received the JVC firmware update, and i followed the instructions to install and re-root. It was all working just fine, wireless tether, all my root apps, ect. I went to test to see if my boot loader was still installed and i restarted my phone trying to bring up the custom recovery. It brought up the stock recovery menu. The only thing i can do now is go into stock recovery or download mode. It keeps rebooting. I just tried to LNGST but it just simply does the same thing after it reboots, it goes right back to stock recovery menu, or i can get it into download mode if its plugged in. Any suggestions on what i can try next? or is my phone completely pooched. I was using the JVB .bin during LNGST. Please any help you can provide would be awesome, this is my main means of communication.
[email protected] said:
Hi,
I have had my lg Optimus G for quite sometime now, almost since it came out. I have had it rooted since day 1 of owning it. We received the JVC firmware update, and i followed the instructions to install and re-root. It was all working just fine, wireless tether, all my root apps, ect. I went to test to see if my boot loader was still installed and i restarted my phone trying to bring up the custom recovery. It brought up the stock recovery menu. The only thing i can do now is go into stock recovery or download mode. It keeps rebooting. I just tried to LNGST but it just simply does the same thing after it reboots, it goes right back to stock recovery menu, or i can get it into download mode if its plugged in. Any suggestions on what i can try next? or is my phone completely pooched. I was using the JVB .bin during LNGST. Please any help you can provide would be awesome, this is my main means of communication.
Click to expand...
Click to collapse
A factory reset should get you going. You'll probably lose your SD with stock recovery reset though.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
A factory reset should get you going. You'll probably lose your SD with stock recovery reset though.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well actually nothing in that menu worked, so i ended up trying teenybins a minute ago the stock zvb and it appears to have fixed my phone. I just reinstalled zvc on it. Im going to reroot and unlock with feegee again, i didnt unlock it last time, maybe thats what the issue was.
So i just Re-installed ZVC, and Re-rooted, and used Free-gee to gain unlock again. I have reboot several times and it looks like im good to go. Hopefully this forum will help people if they ever get the issues i did.
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
cvall91 said:
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
Click to expand...
Click to collapse
I thought rooted phones weren't allowed to update via Kies or OTA.
allenjthomsen said:
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I guess I'll try to download it again and see if that works. Do you know if that's through Kies or through manually downloading it then using Odin?
Techngro said:
I thought rooted phones weren't allowed to update via Kies or OTA.
Click to expand...
Click to collapse
Well it seemed to update for me. At least the verification process went through. I used Wanam Xposed and had the fake system status thing checked. Either way something went wrong and didn't finish the updating process and got stuck at boot logo with no recovery options.
The OTA update did not work though. I was able to get the update downloading after Wanam, but once the download finished, the update failed before trying to install. Did not try OTA again though I just went to Kies, then Odin. But all 3 methods failed.
My unrooted, stock Nexus 7 was on 4.4. I received an OTA notification about 5.0.1 so accepted the upgrade. After the reboot and seeing the Android with the open stomach, it fails with Error against the Android. All I can do is long power off/volume up to power off and then power on again. It then reverts back to 4.4.
After about an hour I received another 5.0.1 update, went the same process and received the same error.
Does anybody know what that could be? I guess I could factory reset the device there is nothing on the tablet that hasn't been saved in my Google account anyway.
Thanks
Wanted to say I experienced the same thing earlier today, except I didn't get an immediate second chance at the OTA. I have the wifi-only version of the N7 2013, and it is also not rooted.
Browsed around the net and various places to see if others had this issue, but no luck. Not really sure what the problem is unless the download got messed up somehow?
Same issue here. Download the update. It shows verified. Reboots, starts to flash and then the android error
Reboot and it is still 5.0
Happy to report that when I got another crack at the ota the update went fine. Still confused as to what could've caused the problem though.
Well it killed my N7 it seems. Got the error message then shut itself down. Now it won't boot up no matter what I do. Any ideas?
My update just stays in the notification area. After the failure I just power the tablet off with long press of the power button and volume up.
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
kendoori said:
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
Click to expand...
Click to collapse
Tried sideloading the factory image?
Sent from my Nexus 5 using XDA Free mobile app
Since my N7 is a secondary device (my main device is a N5 which received the Lollipop upgrade fine), I might just leave it on KitKat rather than muck around with sideloading Lollipop. KitKat works fine for me at the moment. But it's really annoying that a stock N7 cannot get an OTA upgrade and goes into an Android error state.
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Same problem! I managed to workaround the issue by using fastboot replacing system.img boot.img recovery.img with stock ones!
chrismast said:
Tried sideloading the factory image?
Click to expand...
Click to collapse
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
kendoori said:
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
Click to expand...
Click to collapse
If I am not wrong, there is a way of flashing the factory image without wipe by modifying one of the scripts, never did it though myself.
Sent from my Nexus 5 using XDA Free mobile app
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
kendoori said:
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
Click to expand...
Click to collapse
jep, that's what I was saying earlier: factory image. For the 5.0.1 update you only need system.img and boot.img, at least that way it worked for me and my N7 2013 is running fine so far.
I dont get 5.0 on my nexus 7 2013, wifi, 32 Gb(flo, ktu84p)
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
I just got my update!!!!!
German8835 said:
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
Click to expand...
Click to collapse
Oh man! It's crasy, I was waiting so long, and exactly on this day when I write to thread I get my update!
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
JasonJoel said:
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
Click to expand...
Click to collapse
That is indeed strange...If you are pure stock it should work I guess? You could still try to sideload the 5.0.1 as well (did the same as I did not want to wait for OTA). You can do it without full wipe, just wipe cache in the process. (You need only to flash system and boot.img, wipe cache, reboot). Nevertheless let me know if you get the "error" solved, would be interested to know.
newkydawg said:
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Click to expand...
Click to collapse
I was skeptical but this worked when I was having a similar problem to the OP Thanks. I have no idea how 5.0.1 is different though.
Hey all, Before I start, ive searched and search and have not been able to find the solution.
I have my LS980 which was rooted. I learned about the zvg upgrade and tot back to stock zve.
Then I accepted the OTA to zvg and all was good so for I was at total stock ZVG.
I searched how to root and I tried the one click root method but something in the script would pause at the waiting for device...
so, I uninstalled all my LG drivers and root programs, Rebooted my computer and then made sure my phone was enabled debugging.
I then ran the LG root script v1.2, the program ran through without any problems. I entered download when it prompted me to and the phone was immediately detected and the su script continued. I left everything connected until it said don! then the control c and n to reboot.
This is the problem now, when the phone reboots it stays at the LG splash screen and the led alternates colors slowly. I cant get it into download mode but I'm able to boot back into stock recovery. I've tried to reboot system repeatedly for 4 or 5 times in a row (hoping something will change and let it boot), but nothing the longest I've left it at the LG screen is 45 minutes. I'm getting frustrated with this, Im really want to get this update rooted. So far the only way I can get the phone to boot is to side load the zvg ota update from stock recovery. can anyone tell me what I need to do to get past my last step and get rooted boot stock zvg?
thanks in advance. I usually can find all the information I need on xda but im stuck on this one.
Is zvg actually taking? I know with the GUI version. It would progress to 90%get stuck and never proceed. Them I would wait 5 minutes. Disconnect and reboot phone. I would have root
I can't tell.. The script run all the way through but i have yet been able to boot. It keeps hanging at the lg screen. Like i said ive waited up to 45 minutes on this state then from the screen I'll just adb to recovery and side load stock zvg update. To get the phone to boot but no root.
When the phone boots back up do you verify you are on zvg. Have you tried re-installing 1 click root for windows. Just in case
Yes I'mback on zvg, because since i can't get the phone to boot i have to adb to stock recovery and sideload the zvgupdate.zip. and then reboot I'm still on stock unrooted zvg.
jcsheriff said:
Yes I'mback on zvg, because since i can't get the phone to boot i have to adb to stock recovery and sideload the zvgupdate.zip. and then reboot I'm still on stock unrooted zvg.
Click to expand...
Click to collapse
Are you able to use the 1.3 version.
The problem i had with 1.3 was that it would hang after waiting for device.. So fast is why i went with 1.2.
I'll be home in a little bit and try the 1.3 Again, because i still had the problem when i switched to 1.2.. Until i deleted and reinstalled all drivers and root programs. I'll Report back
jcsheriff said:
The problem i had with 1.3 was that it would hang after waiting for device.. So fast is why i went with 1.2.
I'll be home in a little bit and try the 1.3 Again, because i still had the problem when i switched to 1.2.. Until i deleted and reinstalled all drivers and root programs. I'll Report back
Click to expand...
Click to collapse
From phone on, with USB debugging on. It should show an authorization key. Select always and OK. It will copy files over and day rebooting to download mode. That will fail. Unplug phone. Shut off. Hold volume up connect phone. The rest will go to 90%. Wait 5 minutes. Reboot phone to system.
I appreciate your advise.. I just deleted and reinstalled the lg drivers again and then ran v1.3. I got the same result..out loads the files then fails at reboot. I discover the phone and reboot to download mode then reconnect. Then i wait and wait..i hear the computer recognize the device but i continue to wait 20 minutes and nothing. I tried it several times with the same result. I then reinstalled the lg drivers uninstalled v1.3 and executed 1.2 when prompted to put device in download mode the device was connected/recognized after about 10 minutes out shows all the files installed and expanded then instructs me how too exit then reboot. I disconnect reboot and waited another 30 minutes.. Still nothing..so once again i adb to stock recovery then sideload the zvg update. Then the phone boots but still no root.
jcsheriff said:
I appreciate your advise.. I just deleted and reinstalled the lg drivers again and then ran v1.3. I got the same result..out loads the files then fails at reboot. I discover the phone and reboot to download mode then reconnect. Then i wait and wait..i hear the computer recognize the device but i continue to wait 20 minutes and nothing. I tried it several times with the same result. I then reinstalled the lg drivers uninstalled v1.3 and executed 1.2 when prompted to put device in download mode the device was connected/recognized after about 10 minutes out shows all the files installed and expanded then instructs me how too exit then reboot. I disconnect reboot and waited another 30 minutes.. Still nothing..so once again i adb to stock recovery then sideload the zvg update. Then the phone boots but still no root.
Click to expand...
Click to collapse
Question, when you connect in download mode and it just sits there. Go to device manager and check com port. Maybe it is connecting to the wrong port.
I think mine originally connect to port 41, when it should be 3.
I've verify the port assignment and I've tried port 3 port 4 and port 41...but the scripts always find the device and identify the port as Whatvi have assigned it to. I've even tied several other computer some running win 7 and others running win 8.1
I just read someone else's post that they were having problems but fixed with newer lg drivers, that his were old.
I noticed I've found a few variations of the driver. Any idea of link to the most current one?
finally rooted
Tekone said:
Maybe you should try this method. Restore to ZVE and rootz it with Lg one click v1.2. Once you confirmed it's rooted, then adb sideload on stock recovery to upgrade to ZVG. When you upgraded to zvg, try the Lg one click root v1.2 again Usually, that Lg One click root v1.2 will stuck on and take awhile, but it did it's job. Also to change the port number after used the LgFlashtool. Alot time, the port 41 don't work with Lg one click root.
Click to expand...
Click to collapse
This worked flawlessly for me. However once i rerooted after sideload. When the script ask you to put the phone inn download mode.. I saw the su script push but the machine appeared to stop working. I left it connected and waited 25 minutes to make sure all was good. Then i pressed and power button and held it down until the phone reset. The script showed complete and the phone booted all the way through. It did take about 10 minutes to boot, then super user was installed and i was rooted.
Hello everyone.
Yesterday my phone finally told me that my download of the new Android 6.0 was ready for my phone which is rooted, but running stock ROM. I downloaded it, and pushed install. I left it by itself so it had the space it needed, no pressure and all that, and anxiously returned to discover the new Android. Bummer, it looked just like before! After trying to install it again, I saw how it failed. I will explain it step by step:
1. When I push install, it starts unpacking the update.
2. After about 2-5 minutes standing still at 0%, the little loading screen disappears and the phone return to normal.
3. When another 1-3 minutes have passed, it suddenly restarts itself into recovery, where it seems it tries to upgrade the software.
4. The screen gives me a series of errors, like: Cannot mount E Data/Android/providers, E is not a valid argument etc.
5. When it finalizes, it tells me the installation is aborted, the log is saved, and then the phone reboots. Rinse repeat.
Hope someone can help!
You need the stock (never rooted) ROM and stock recovery, to update by OTA.
Restore a stock ROM for your version using TWRP, then install stock recovery again.
I am using CWM, is it the same method I should use for that as well?
Yes. Same thing for CWM. Restore to a stock ROM that has never been rooted using CWM then flash stock recovery again before attempting to download the OTA again.