Hi!
Got my G Pro last week, today i rooted it (SU & SuperUser said it worked) and tried to install the actual CWM via the ROM Manager. ROM Manager said it was ok but when i try to start the recovery it only shows the Android robot, lying on his back, front flap open and an red triangle with an exclamation mark over it. After about 30 seconds the phone restarts (to normal mode).
It isn't possible to start recovery via the shortcut, there will always be the official message about the recovery.
TIA!
Dr.Soong said:
Hi!
Got my G Pro last week, today i rooted it (SU & SuperUser said it worked) and tried to install the actual CWM via the ROM Manager. ROM Manager said it was ok but when i try to start the recovery it only shows the Android robot, lying on his back, front flap open and an red triangle with an exclamation mark over it. After about 30 seconds the phone restarts (to normal mode).
It isn't possible to start recovery via the shortcut, there will always be the official message about the recovery.
TIA!
Click to expand...
Click to collapse
In short, you cannot use the standard CWM from ROM Manager without Loki. You must use a Lokified version, i.e. a version which includes the Loki exploit, such as the one that FreeGee installs.
No other recovery will work without Loki, because the LG OG Pro has a locked bootloader.
Sad, but true. With a fully unlocked bootloader, this device would be the king of all devices, IMO.
donalgodon said:
Sad, but true. With a fully unlocked bootloader, this device would be the king of all devices, IMO.
Click to expand...
Click to collapse
I agree with you man.!!
Thank you for the answer, so i downloaded FreeGee and tried to install the recovery, after downloading the recovery it says "boot md5sum mismatch" and does not install the recovery. Almost tried it a couple of times, it never worked.
Got it, after applying the official LG-Update FreeGee does its magic. Thank you for your help.
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.
[Q] Problems w/ Root & Custom Recovery on LG LS980...and I only have Ubuntu access...
First off I'm running Ubuntu 14.04 and I'm probably not as tech savvy as I should be for someone running Ubuntu. I do not have access to a Windows computer. My gf has a Macbook Air but I know she's tired of me running my phone experiments on it. Here's the problem that I'm in. I have spent hours upon hours of research and made numerous attempts at this and I just can't figure it out. I have an LG LS980 and I'm running the ZVE update (phone already had ZVE on it when I bought it). I do not have root or CWM or TWRP. I have been trying to root, install CWM or TWRP and then switch to CM 11. I originally rooted my phone, then, because of an incessant error issue (it would pop up repeatedly every second making the phone unusable) I had to factory reset. Since that factory reset I have not been able to achieve root. I have tried everything (IOROOT, STUMP, TOWELROOT) nothing. Stump says that I'm rooted but SUPERSU says I have no binary. I figured I'd just go straight to a custom recovery and then flash a rom that is already rooted. However it appears that there is no TWRP or CWM for LG LS980 without root. I just can't figure out how to get root status back and how to install a custom recovery. I'm stuck and I need help. I've read about going back to a stock ZVC and starting all over again but I don't know how to do that. I appreciate any future help from you all.
Using LG Flash Tool, you can tot back to stock, and retry rooting. There are a couple of guides floating around here, I'd look for one of them and just follow it exactly to get root and TWRP set up, then you can try your hand at a custom ROM.
Edit- Not sure if LG Flash Tool works on Ubuntu. If it doesn't or you just want to play it safe, I'd borrow a friend's laptop to run it. It's pretty quick, like 5-10 mins if I remember correctly.
Yes I have read that but does anyone know how to do that on Ubuntu?
I have a Verizon LG G3 and wanted to root to change the ROM. I used kingroot to root and then was able to add superuser, root checkers showed I had root and superuser access. I read online a few people were able to use flashify to put Twrp on their device. I selected the VS985 and after it was done it would not boot into recovery. The phone loads and runs fine but now ot shows the phone does not have root, superuser says it needs update and fails, and I cannot even do a factory reset.
How do I fix the recovery so I can either finish the root and recovery installation, or just go back to stock?
Thanks!
Phone is on Marshmallow. Guides I found to fix say you need to be on lollipop. Phone boots right now, so I do not want to risk trying too much since it boots now.
Fixed it using lg flashtool but with this dll file http://forum.xda-developers.com/show...4&postcount=84
Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app
title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.
Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app
Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.
Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk