When I try to start my buddy's G tab in recovery mode (power button + volume up), it hangs on the "bird screen" / recovery key detected screen. The only way out is to manually shut it down with the power button.
The first time I started it in recovery I was attempting to install CWM, and the Android recovery screen came up. I couldn't get it to take any commands with home button or any other, so I shut it down manually and tried again. That's when it stopped giving me anything.
Mine didn't act that way ... did I do something wrong, or has VS changed something in their latest updates?
.
.
MikefromTX said:
When I try to start my buddy's G tab in recovery mode (power button + volume up), it hangs on the "bird screen" / recovery key detected screen. The only way out is to manually shut it down with the power button.
The first time I started it in recovery I was attempting to install CWM, and the Android recovery screen came up. I couldn't get it to take any commands with home button or any other, so I shut it down manually and tried again. That's when it stopped giving me anything.
Mine didn't act that way ... did I do something wrong, or has VS changed something in their latest updates?
.
.
Click to expand...
Click to collapse
NV-Flash your device back to a stock firmware and try again. Or you can just NV-Flash a new recovery file. That would also work.
If the stock recovery had a menu that you were trying to select a command from then the device has a ROM based on the 1.2 bootloader and there are a few things you should know.
1) The home key doesn't activate the selected command. It toggles the display. The power key activates the commands.
2) The standard CWM for 1.1 based ROMs doesn't work with 1.2 based ROMs
3) If the device has one of Roebeet's custom 1.2 based ROMs then you can use the built in recovery pack to flash between Stock Recovery and ClockworkMod with a simple command line script. It may even work to recover from the situation you're in now.
K J Rad said:
If the stock recovery had a menu that you were trying to select a command from then the device has a ROM based on the 1.2 bootloader and there are a few things you should know.
1) The home key doesn't activate the selected command. It toggles the display. The power key activates the commands.
2) The standard CWM for 1.1 based ROMs doesn't work with 1.2 based ROMs
3) If the device has one of Roebeet's custom 1.2 based ROMs then you can use the built in recovery pack to flash between Stock Recovery and ClockworkMod with a simple command line script. It may even work to recover from the situation you're in now.
Click to expand...
Click to collapse
Many thanks. I've learned tonight that his tablet has the new 4349 build, and that does have the 1.2 bootloader. That's apparently why CWM didn't load.
Where I am now, though, is that I can't get ANY recovery menu to come up. It merely sticks on the main screen with the recovery key detected message, and I have to manually turn it off to reboot. Therefore, loading anything from a zip would be difficult - which I guess might have saved us since I didn't realize VS had slipped in a new bootloader.
But for future use, I might need to get access to that recovery menu ... how do I do that?
.
.
Sounds like stock recovery got flashed over by cwm for 1.1 bootloader. You could try looking over at another site that is something like [email protected] d®∅¡d.com for the new cwm modified for 1.2 bootloader and load it through nvflash. Good luck.
Thanks!
.
.
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....
recently soft bricked my new AT&T S2.I have clockwork recovery installed (4.0.0.2), and the only buttons that work are home (goes back to the first menu), volume up/down, and power to hide the menus. I can't select anything at all, it seems like I have the international version of the recovery, not one for the S2.Anyways, I can't get into download mode by holding down the home + Vol up+ power, and Odin can't seem to connect to my phone if it's in clockwork recovery and not download mode.Would the jig work? Or is having no ability to boot into download mode pretty much a killer? I can access my phone through ADB, I just don't know my way around adb as well as I would like.Is there any way to flash a different recovery via ADB? Any other solutions to get my phone up and running again? Because right now it's not booting at all.
EDIT: Managed to get back into the system. It's running the International ROM instead of mine though, so the buttons are wonky. Does anyone know where I can find the ODIN files to flash back to stock AT&T S2?
CadellG said:
recently soft bricked my new AT&T S2.I have clockwork recovery installed (4.0.0.2), and the only buttons that work are home (goes back to the first menu), volume up/down, and power to hide the menus. I can't select anything at all, it seems like I have the international version of the recovery, not one for the S2.Anyways, I can't get into download mode by holding down the home + Vol up+ power, and Odin can't seem to connect to my phone if it's in clockwork recovery and not download mode.Would the jig work? Or is having no ability to boot into download mode pretty much a killer? I can access my phone through ADB, I just don't know my way around adb as well as I would like.Is there any way to flash a different recovery via ADB? Any other solutions to get my phone up and running again? Because right now it's not booting at all.
EDIT: Managed to get back into the system. It's running the International ROM instead of mine though, so the buttons are wonky. Does anyone know where I can find the ODIN files to flash back to stock AT&T S2?
Click to expand...
Click to collapse
:facepalm:
First off, that's not how you get into download mode. Turn the phone off, hold both VOLUME BUTTONS ONLY, and plug in the USB cable.
With my phone, If I hold down both volume buttons and power on, it goes to clockwork recovery. If I turn the phone on holding the volume up and the home button, it goes to download (now).
I fixed that issue already though, the problem at hand is that I have the i9100 boot and firmware on here, and need the stock Odin files to fix. Can't find the files though. : /
CadellG said:
With my phone, If I hold down both volume buttons and power on, it goes to clockwork recovery. If I turn the phone on holding the volume up and the home button, it goes to download (now).
I fixed that issue already though, the problem at hand is that I have the i9100 boot and firmware on here, and need the stock Odin files to fix. Can't find the files though. : /
Click to expand...
Click to collapse
http://hotfile.com/dl/145854922/8415983/I777UCKH7_I777ATTKH7_ATT.zip.html
CadellG said:
With my phone, If I hold down both volume buttons and power on, it goes to clockwork recovery. If I turn the phone on holding the volume up and the home button, it goes to download (now).
I fixed that issue already though, the problem at hand is that I have the i9100 boot and firmware on here, and need the stock Odin files to fix. Can't find the files though. : /
Click to expand...
Click to collapse
Also available in the Download Repository linked in my signature.
...me too....
WOW DISREGARD - too stupid to realize soft buttons work with CWM recovery. They didn't before...very premature post, my apologies
For the bootloop, I selected Advanced in CWM recovery, and then selected "Fix permissions" then I installed update from SD card. Now it works! Back to being a noob and hating my life.
-----------
I seem to have bricked my phone too...I was using ROM manager to install cm9 update (yeah, I NOW know I should not have used ROM manager). I used ODIN to re-flash cwm recovery enabled kernel. I can go to recovery, but it does not let me select any of the menu options. And when I boot the phone, it still sends me into a bootloop.
One time it did say "signature verification failed" but it doesn't say that anymore, it just doesn't move. I've read around about signature verification issues, but I haven't found anything that gets me anywhere.
I know this is pretty noobish, but I really appreciate any help!
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.
Hi i have small problem with my phone my phone is at 4.0.4and i installed newest miui and now my kernel is messed up.
I cant open ap fastboot or any else tool there it results black screen is it possible to restore kernel any other way like trough safestrap?
Is there anywhere original kernel for ics that i could install trough cwm??
Ihmejampah said:
Hi i have small problem with my phone my phone is at 4.0.4and i installed newest miui and now my kernel is messed up.
I cant open ap fastboot or any else tool there it results black screen is it possible to restore kernel any other way like trough safestrap?
Click to expand...
Click to collapse
So you tried to install the MIUIv5 on a ICS based phone? That wasn't very smart as there is clearly stated you must be on 4.1.2!
Usually there is no chance to mess up your kernel by flashing a custom rom - our bootloader is locked which makes things like that more difficult.
It looks like a problem with the bootloader and not a messes up kernel - even when I cannot imagine why this happended because you are using Safestrap! Except you were using an old SS version - there would be no guarantee for potential issues when mixing old stuff with new stuff..
If you cannot enter AP fastboot mode it looks really bad for you... Are you sure you cannot enter fastboot??
Force reboot by pressing and holding Power key + Vol Down key, then immediately press and hold BOTH Vol keys when the screen goes off???
Otherwise when you are still able to enter SS you should be able to switch to your stock slot and boot up your stock rom?
dtrail1 said:
So you tried to install the MIUIv5 on a ICS based phone? That wasn't very smart as there is clearly stated you must be on 4.1.2!
Usually there is no chance to mess up your kernel by flashing a custom rom - our bootloader is locked which makes things like that more difficult.
It looks like a problem with the bootloader and not a messes up kernel - even when I cannot imagine why this happended because you are using Safestrap! Except you were using an old SS version - there would be no guarantee for potential issues when mixing old stuff with new stuff..
If you cannot enter AP fastboot mode it looks really bad for you... Are you sure you cannot enter fastboot??
Force reboot by pressing and holding Power key + Vol Down key, then immediately press and hold BOTH Vol keys when the screen goes off???
Otherwise when you are still able to enter SS you should be able to switch to your stock slot and boot up your stock rom?
Click to expand...
Click to collapse
Yeah the mistake happened when i hastly just downloaded the rom and installed it. Never tought it would harm my phone..
My phone works normaly and boots but fastboot does not work :/
Or could the problem come from exessive use of force shutdown? My power button does not work and oftenly i have to force shutdown to open my screen??
Ihmejampah said:
Yeah the mistake happened when i hastly just downloaded the rom and installed it. Never tought it would harm my phone..
My phone works normaly and boots but fastboot does not work :/
Or could the problem come from exessive use of force shutdown? My power button does not work and oftenly i have to force shutdown to open my screen??
Click to expand...
Click to collapse
I don't have any idea why this happened. But you can test something.
1. From recovery's reboot options select "bootloader".
2. Install BMM app (only the app if you're SS user!), open the BMM rebooter and select bootloader or fastboot (if existing).
3. Use RSD lite and your phones fastboot package. Remove everything from its xml file except the kernel - we need something to flash via fastboot for using purposes without messing up your current system. Plug in your phone while being on main system (booted), wait until your phone is being recognized by the computer and press "flash" in RSD lite. Usually RSD boots your phone into fastboot automatically.
Gesendet von meinem XT910 mit Tapatalk 4
Again small problem what makes this hard i cant select the recoverys reboot options the selecting button is power button and it doesnt work.
Maby i throw phone to service mans face and tell him to fix power button
bigger problem
Ihmejampah said:
Again small problem what makes this hard i cant select the recoverys reboot options the selecting button is power button and it doesnt work.
Maby i throw phone to service mans face and tell him to fix power button
Click to expand...
Click to collapse
I kind of have a bigger problem. Under BMM I played 2 ROMS in KEXEC. I wanted to change the names of the ROMS in BMM but BMM indicated problems and asked to undelete. I did and restarted, but now I cannot enter the phone.
Tried to fastboot under RSD but my fastboot file led to "FAIL".
Ran an old "ubrick routine" which helped me before http://forum.xda-developers.com/showthread.php?p=39247094#post39247094 which booted the phone and keeps booting in the JBX logo
In the meantime I tried a number of old fastboot files but all failed.
http://forum.xda-developers.com/showthread.php?t=2231289 did the trick
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.