Ok, so I was preparing to update to 5.02 now that the UK version is out, but it seems my phone has completely lost recovery.
I'm sure I installed TWRP recovery previously, and I'm currently still on 4.4.4 Rooted with SuperSU installed and I installed TWRP as part of setting that up. However, my phone now will not boot into recovery at all. When I power on the phone, there is no notification LED for me to start pressing Volume Up or Down, it just boots normally into Android. If I just hold down the power button until it turns on, then hold the Volume Down button, the phone vibrates a few times, then just boots normally.
The only thing I can think that's changed is that the phone doesn't have the original MicroSD card in it that I used to have (and that one I no longer have access to).
I have tried re-installing TWRP using this thread, http://forum.xda-developers.com/showthread.php?t=2785598, and running the install.bat on the Z2-lockeddualrecovery2.8.10-RELEASE version, and this seemed to go through the process successfully, but no luck. The phone just rebooted to normal Android rather than recovery, and I'm still only able to boot to normal Android, so it seems I've lost recovery entirely.
So is there any way I can get TWRP recovery back on the phone so I can proceed with installing a pre-rooted FTF of 5.02?
EDIT/UPDATE - Ok, I went into SuperSU on the phone and had it forget all of the current Superuser access for Busybox and ADB, then re-ran the installer. This time when the phone rebooted it booted into PhilTouchZ recovery rather than TWRP that I was expecting...? Or is it the same thing?
EDIT/UPDATE 2 - Ok, powered off the phone, then powered back on holding the Volume Down button. Now in TWRP. I have to re-learn Android every time I update/re-root
Related
I flashed my Vibrant using the gingerbread bootloader found here http://forum.xda-developers.com/showthread.php?t=1117990 and this 2.3.4 rom with voodoo lagfix found here http://forum.xda-developers.com/showthread.php?t=1228306.
The gingerbread bootloader has recovery and downloading key remapped, for downloading its VOLUP and POWER and for recovery its supposed to be VOLDOWN and POWER. Getting into downloading mode works fine but I can't get recovery to boot all the time, I got it to boot to the ClockworkMod Recovery with Voodoo Lagfix (red colored recovery a few times) but I think I used the combination of VOLDOWN and POWER and then pressed VOLUP and VOLDOWN only to get it to boot.
Recently however I have been unable to boot into recovery at all, VOLDOWN+POWER doesn't work (only causes a boot loop) and VOLUP+VOLDOWN+POWER then release power at Vibrant logo also doesn't work.
Can someone tell me an easy key combination to get into recovery? I really don't want to install ADB.
Is there not an option in the power menu to boot into recovery?
Have you tried an app to do it for you?
worst case, just flash something else...
You need to make sure your phone is completely off before trying to access recovery. The screen on the vibrant when it is almost off is also black, but that does not necessarily mean its off.
I somehow lost clockwork mod recovery, I think the rom I used uses the red cwm recover mode, whereas the ROM manager wants the green cwm recovery.
protohamster said:
I somehow lost clockwork mod recovery, I think the rom I used uses the red cwm recover mode, whereas the ROM manager wants the green cwm recovery.
Click to expand...
Click to collapse
I actually think the Red recovery mode is prefered or is the latest version unless u had the E signature verification error. I am almost sure u can re flash another or update the recovery via SD root
Depends on what rom you have loaded it could be Blue or amber as well.
Make sure you have Rom manager downloaded (I assume you do) and enable it. Then, turn off and then pull the battery. Then re-insert the battery and go into recovery manually by holding the vol+ and - and power button. Here is a thing to remember, usually it is... let the screen blink 2 times and after the second blink release the buttons and it should go into recovery. But, depending on the rom it could be 3 times or 4. You may need to experiment on that. I have found if one suffers from getting into recovery ....once you have done it manually rom manager and all the others afterwards work perfectly. Software can be quirky....
hope you get it....
Title pretty much says it all, trying to figure out how to get a Onda v973, I think version 2 to boot into recovery via the power/home buttons. Which are the only buttons on the device. I was able to get it to boot into recovery via adb reboot recovery. Seems there was a way with v971 and v972 if you hold the home button + power till the logo comes up. But when I press the home and power, the device never turns on. It will only turn on if just the power button is pressed. Though I do hear it making some sound at one point when I have both depressed.
I have CWM and Cyanogenmod 10.1 installed on my v973. I did not turn off signature verification, the compatibility package failed, and I did not catch that till after I rebooted. Now I have both on there, but no touch screen drivers. With USB debugging not enabled, when the device boots it shows in adb devices, but is unauthorized. I am just trying to reboot into recovery/CWM so I can turn off signature verification, install the compatibility package, and have a working tablet again.
Even with stock firmware I could not get it to enter recovery. I started by using the upgrade tool to install TWRP. Then had to use adb reboot recovery to get into TWRP. Which did not have working touchscreen drivers. I could not get the device to stop booting in recovery mode/TWRP. I then used adb to push CWM to the device and cat it to overwrite TWRP. From there used CWM to install Cynogenmod and stop booting into recovery. I did backup the factory rom, but never got a chance to download it from the internal storage.
I will try using the PhoenixSuit to restore a stock firmware and start over again. But do not run Windows, attempting to use it via Windows running in VirtualBox on Linux. Either way, still would like to know how to get this device to boot into recovery using power/home buttons. I have asked Onda the same question. Does seem like its changed since previous models and/or versions. Hopefully there is a way as if not will be the first android device I have come across with no physical means to enter recovery mode.
Ok, so I rooted my LGOG E970. I figured I better unlock it as well, so I used FreeGee and unlocked it. I tried to download CWM but it said it couldnt download file. So I thought I would reboot my phone. Now, all I get is the google logo, with the unlocked key underneath, and it then goes to the LG logo and back to Google and shuts off. I tried to hold down power and volume down, nothing, and power volume up nothing.:crying:
any ideas? Thanks in advance! I love this phone!
CJ
You too, huh?
I did this the other night, and when the CWM failed to install I went to download it myself... That's when I saw that CWM for geeb is 6.0.3.8, not 6.0.4.5 like FreeGee shows. (Looks like FreeGee has moved on to targeting G2 or another... Oops.)
I hope you backed up your EFS, because mine was screwed up and I needed to manually restore it from the backup I'd taken. (I've had my phone rooted for 9+ months, finally got fed up with stock and was looking to get onto a 4.4 ROM)
So here's what I did:
Held power button until phone was properly off (failed boot seemed to be a still partially on state)
Held volumn up first, then started holding power.
When phone vibrated slightly, I let go of power and kept holding volume up... You should be in boot loader now.
When your phone is in the bootloader, connect to your PC (Make sure you have the proper drivers if you use Windows; I use Linux which doesn't have the same nonsense setup for drivers like Windows does)
Make sure "fastboot devices" shows your phone and then type: fastboot flash recovery _____recovery file name.img____
Press volume down twice to select "Recovery", and press power once to select it... You should be booted into the recovery that you just installed.
Once you're in a recovery, you can push a ROM zip via ADB, flash, wipe data/dalvik cache and reboot.
thanks, Just a little more help
aedren said:
You too, huh?
I did this the other night, and when the CWM failed to install I went to download it myself... That's when I saw that CWM for geeb is 6.0.3.8, not 6.0.4.5 like FreeGee shows. (Looks like FreeGee has moved on to targeting G2 or another... Oops.)
I hope you backed up your EFS, because mine was screwed up and I needed to manually restore it from the backup I'd taken. (I've had my phone rooted for 9+ months, finally got fed up with stock and was looking to get onto a 4.4 ROM)
So here's what I did:
Held power button until phone was properly off (failed boot seemed to be a still partially on state)
Held volumn up first, then started holding power.
When phone vibrated slightly, I let go of power and kept holding volume up... You should be in boot loader now.
When your phone is in the bootloader, connect to your PC (Make sure you have the proper drivers if you use Windows; I use Linux which doesn't have the same nonsense setup for drivers like Windows does)
Make sure "fastboot devices" shows your phone and then type: fastboot flash recovery _____recovery file name.img____
Press volume down twice to select "Recovery", and press power once to select it... You should be booted into the recovery that you just installed.
Once you're in a recovery, you can push a ROM zip via ADB, flash, wipe data/dalvik cache and reboot.
Click to expand...
Click to collapse
I try to go to recovery and it just goes blank. What program with my crazy windows would be best to get a stock file to the phone? Or any other ideas>
thanks again
ZombieGeek said:
I try to go to recovery and it just goes blank. What program with my crazy windows would be best to get a stock file to the phone? Or any other ideas>
thanks again
Click to expand...
Click to collapse
Yeah, the stock recovery won't boot if you try it either. I forgot to tell you that. If you drop in a custom recovery (TWRP or CWM), it will work fine and you can both create a backup of your data and flash a new ROM...
If you want to try to get back to stock, LGNPST is what you should try. But to be completely honest, I don't know if you can LGNPST from the state that it's in. I haven't tried, and I'm using a custom ROM now (the whole reason I unlocked the bootloader to begin with).
bummer
aedren said:
Yeah, the stock recovery won't boot if you try it either. I forgot to tell you that. If you drop in a custom recovery (TWRP or CWM), it will work fine and you can both create a backup of your data and flash a new ROM...
If you want to try to get back to stock, LGNPST is what you should try. But to be completely honest, I don't know if you can LGNPST from the state that it's in. I haven't tried, and I'm using a custom ROM now (the whole reason I unlocked the bootloader to begin with).
Click to expand...
Click to collapse
again, thanks so much! you are my hero, only problem is, I loaded the kit kat bu houstonn and now I have no cellular? I hate it when your phone isnt a phone lol
ZombieGeek said:
again, thanks so much! you are my hero, only problem is, I loaded the kit kat bu houstonn and now I have no cellular? I hate it when your phone isnt a phone lol
Click to expand...
Click to collapse
Yeah, I got that too. I don't know if I got it fixed due to changing ROM, using the suggested recovery from the ROM, or if it was due to me restoring my EFS backup.
I flashed the TeamWin recovery found in the PSX instructions. Then I flashed PSX + Latest kernel + Banks Gapps + Banks Google Camera + AT&T NFC fix + SuperSU. I manually restored EFS from an ADB shell while in recovery.
When I booted I had: LTE works, Wifi works, NFC works, Camera works, ART works... The only things failing for me are the following:
Cell provider shows up as "Maritime" (display bug; as mentioned, LTE works fine and I'm on AT&T)
Settings > Developer Tools > Geeky Process Stats (does nothing)
Settings > Lockscreen > Slider Shortcuts (crashes as soon as I tap the middle ring)
LogCat is spammed with "QCOM PowerLock: Failed to acquire lock" whenever my finger is on the screen.
/system/xbin/mount --bind doesn't work (neither does mount -o bind). It gets sorta half-way-there, because the target directory can't be removed, but isn't bound properly it seems.
Other than that, it's been fast and smooth.
Hello, today I wanted to restore my previous CWM backup. So i started with cleaning partitions before restoring. I've begun with system and my phone hang. I waited about 30 minutes, then pulled out battery with hope I'll try again via CWM. The thing is - I can't boot it into recovery: Volume Up/Volume Down+Power leads to normal start up (LG screen and nothing further). So i connected it to PC and wanted to make it right via ADB. Unfortunely it seems I had USB Debugging turned off, and ADB isn't recognizing my phone now... What should I do now?
I have rooted D620r with unlocked bootloader.
silent_hunter said:
Hello, today I wanted to restore my previous CWM backup. So i started with cleaning partitions before restoring. I've begun with system and my phone hang. I waited about 30 minutes, then pulled out battery with hope I'll try again via CWM. The thing is - I can't boot it into recovery: Volume Up/Volume Down+Power leads to normal start up (LG screen and nothing further). So i connected it to PC and wanted to make it right via ADB. Unfortunely it seems I had USB Debugging turned off, and ADB isn't recognizing my phone now... What should I do now?
I have rooted D620r with unlocked bootloader.
Click to expand...
Click to collapse
You must never delete partitions before restoring a backup especially system!!
CWM will do that for you...
Boot your device in factory reset mode (which simply boots CWM) by doing the following key combination: (while your device is off - pull and plug the battery to be sure) press and hold Vol - and power, when you see the LG logo, release the power button and press it again. Hold them until you see the facory reset mode, then simply enter YES. It will reboot to CWM.
Vagelis1608 said:
You must never delete partitions before restoring a backup especially system!!
CWM will do that for you...
Click to expand...
Click to collapse
Weird, I was always doing this when I had HTC Desire S
Used this countless times and always worked!
Ok, i've done as You said, something like CWM loading screen appeared, and then went back to LG Screen. LG Screen standing still and nothing happens
The only good thing is that I can access ADB for 20 seconds when CWM is "loading", but no action can be executed - every command ends up with "waiting for device".
Thanks for Your reply, though! :highfive:
EDIT:
I solved my problem by using "Emergency software restore" mode featured in "LG User Support Tool". I got clean, unrooted system now and I need to modify it again but...
...THAT'S WHY I REGISTERED HERE!
Lock bootloader
Hello everyone.
I was just going to try out CM11, but got one question. Is it possible to lock the bootloader and revert everything to stock? There were some talks about new stock ROMs coming out and they might not work after a custom ROM.
Ok guys so I have a Sony Xperia Z Ultra and I decided to install Marshmallow 6.0 on it (which wasn't released for my phone). I downloaded the boot, cache, system and userdata imgs of Marshmallow 6.0 and installed them using fastboot, then I was supposed to boot in recovery mode and wipe the caches and do a reset, before installing the G-apps zip file and completing the entire process. So I tried to start recovery mode which I had previously installed already and it failed, starting in safe mode instead. Then I re-installed the recovery using a batch file in a directory downloaded from NUT's XDA Developers download site, which failed on the first try. So I tried again and it was installed, meaning my phone will automatically reboot into recovery right after it was done. My phone rebooted but my screen remained black and nothing happened. I tried holding down the power button and it vibrated but nothing happened again. I tried holding down the power and volume down button for 30sec and more, tried it with the volume up button too and it didn't work. I tried connecting my phone to the pc but it won't recognize it (of course) and I tried holding the volume up button upon connecting to enter fastboot but that failed as well. Now it's stuck like this and I'm hoping its battery drains out and it powers off. Help.
Update: I went to sleep and now that I've woken up, the screen is still going with the low battery red light. I don't know for how long it will continue, but the problem remains.
Update: Now my pc recognizes it but all adb commands have no effect.
Jissatsu said:
Ok guys so I have a Sony Xperia Z Ultra and I decided to install Marshmallow 6.0 on it (which wasn't released for my phone). I downloaded the boot, cache, system and userdata imgs of Marshmallow 6.0 and installed them using fastboot, then I was supposed to boot in recovery mode and wipe the caches and do a reset, before installing the G-apps zip file and completing the entire process. So I tried to start recovery mode which I had previously installed already and it failed, starting in safe mode instead. Then I re-installed the recovery using a batch file in a directory downloaded from NUT's XDA Developers download site, which failed on the first try. So I tried again and it was installed, meaning my phone will automatically reboot into recovery right after it was done. My phone rebooted but my screen remained black and nothing happened. I tried holding down the power button and it vibrated but nothing happened again. I tried holding down the power and volume down button for 30sec and more, tried it with the volume up button too and it didn't work. I tried connecting my phone to the pc but it won't recognize it (of course) and I tried holding the volume up button upon connecting to enter fastboot but that failed as well. Now it's stuck like this and I'm hoping its battery drains out and it powers off. Help.
Update: I went to sleep and now that I've woken up, the screen is still going with the low battery red light. I don't know for how long it will continue, but the problem remains.
Update: Now my pc recognizes it but all adb commands have no effect.
Click to expand...
Click to collapse
you should give some info... like what rom youre using. also use twrp 3.x with mm
you cant expect help without telling the error messages you get...
you can always power off your phone with holding vol down + power for 30sec
MusterMaxMueller said:
you should give some info... like what rom youre using. also use twrp 3.x with mm
you cant expect help without telling the error messages you get...
you can always power off your phone with holding vol down + power for 30sec
Click to expand...
Click to collapse
YEAH ok here's my issue. NO MATTER WHAT recovery I install (through the app or fastboot) IT DOES NOT WORK. Any earlier version of TWRP, it will boot into, but the screen is unresponsive, while the latest version of TWRP simply acts like it isn't there as the phone never boots into recovery, this has been happening on MM and now it's happening on my latest stock. After the failed MM attempts I've downloaded the latest C6833 stock and everything is fine, but I'd like to be able to install custom roms like everyone else. It took me a day or two to learn how to actually do that, but I still have no idea why NO recovery works for me. My device is rooted, bootloader unlocked, all that crap. I tried many kernel links on your site, especially that main one that the mod posted, but the links are dead. Help.
Jissatsu said:
YEAH ok here's my issue. NO MATTER WHAT recovery I install (through the app or fastboot) IT DOES NOT WORK. Any earlier version of TWRP, it will boot into, but the screen is unresponsive, while the latest version of TWRP simply acts like it isn't there as the phone never boots into recovery, this has been happening on MM and now it's happening on my latest stock. After the failed MM attempts I've downloaded the latest C6833 stock and everything is fine, but I'd like to be able to install custom roms like everyone else. It took me a day or two to learn how to actually do that, but I still have no idea why NO recovery works for me. My device is rooted, bootloader unlocked, all that crap. I tried many kernel links on your site, especially that main one that the mod posted, but the links are dead. Help.
Click to expand...
Click to collapse
there is other way to enter twrp 3.0.2 with new bootloader, power + vol down (instead of up!)
read op of twrp thread and follow instructions carefully and it'll work. also for the twrp i build you must be on a rom which uses sony aosp device tree (like aicp). otherwise i wont guarantee that it will work.
MusterMaxMueller said:
there is other way to enter twrp 3.0.2 with new bootloader, power + vol down (instead of up!)
read op of twrp thread and follow instructions carefully and it'll work. also for the twrp i build you must be on a rom which uses sony aosp device tree (like aicp). otherwise i wont guarantee that it will work.
Click to expand...
Click to collapse
I tried holding the button down like you said, tried rebooting to recovery from TWRP manager itself, with root access granted of course. Nothing. Can you link the post or something? However I don't think anything in it will fix my issue.
Sounds like you flashed a recovery for another model. I had this issue with a ROM awhile back.
Didn't read the walls of text.
I recommend using you flashtool and flashing a stock ftf. Re-root, recovery and flash again.
---------- Post added at 06:16 AM ---------- Previous post was at 06:11 AM ----------
Edit. Read somethings. There are plenty of ROMs on xda do not flash the old way which is part by part. Flash the most recent Sony firmware, and you should be able to flash MM ROMs.
I have copy's of the recovery if needed.
I did flash the latest FTF using the flash tool, but I need a working recovery in order to install the gapps and still no recovery works on my device.
check here
http://forum.xda-developers.com/xpe...2-0-togari-t3452968/post68481255#post68481255