[Q] Rebooting to Recovery issue [ROM]AOSP*****EaglesBlood™*****ICS[March/31st/2012] - T-Mobile LG G2x

Im having an issue with rebooting to recovery allways instead of a normal reboot. Any solutions?
By the way awesome ICS rom, the smoothest ive run so far

I found that if I select recovery then select reboot then recovery again .. it will go to recovery.
C.S.M. made mention of this in The official thread. It seems that the function requires an actual command before it can execute by default. He also mentioned this would be an easy fix in the next build .. being AOSP Build 2.
Sent from my LG-P999 using Tapatalk

Related

[Q]Bootloader>Recovery, Hangs at Google boot.

Attempted to flash update to current CM 7 Nightly build, from Nightly10. When doing so, Bootloader>Recovery(System hangs on Google load screen), Battery is then pulled. Attempts are made without SIM card. Also initiated with ROM Manager v3.0.0.7 +Fix Permissions, with same results.
No luck with returning to previous ROM, or cleaning Cache and Dalvic-cache for same reason.
All other ROM flashing attempts have been flashed on my Nexus S, great success.
Side Note: CM 7 Nightly10 is running great! Boots/Loads with no issue.
Red Fox said:
Attempted to flash update to current CM 7 Nightly build, from Nightly10. When doing so, Bootloader>Recovery(System hangs on Google load screen), Battery is then pulled. Attempts are made without SIM card. Also initiated with ROM Manager v3.0.0.7 +Fix Permissions, with same results.
No luck with returning to previous ROM, or cleaning Cache and Dalvic-cache for same reason.
All other ROM flashing attempts have been flashed on my Nexus S, great success.
Side Note: CM 7 Nightly10 is running great! Boots/Loads with no issue.
Click to expand...
Click to collapse
dont use rom manager, rom could be corrupted while downloading. download it manually then flash from recovery.
simms22 said:
dont use rom manager, rom could be corrupted while downloading. download it manually then flash from recovery.
Click to expand...
Click to collapse
What could cause, or any suggestion on how to fix/pass the system freeze on: Power+VolumeUP>Recovery= Google ... .. ... (snooze, thinking, snooze)
Much help is greatly appreciated, updating to the latest and greatest is inspiring.
Sent from my Nexus S
Red Fox said:
What could cause, or any suggestion on how to fix/pass the system freeze on: Power+VolumeUP>Recovery= Google ... .. ... (snooze, thinking, snooze)
Much help is greatly appreciated, updating to the latest and greatest is inspiring.
Sent from my Nexus S
Click to expand...
Click to collapse
ahhh, i misunderstood you first. try flashing the recovery again.
simms22 said:
ahhh, i misunderstood you first. try flashing the recovery again.
Click to expand...
Click to collapse
I just tried the recovery OS ROM, no progress, still freezing the same. Could you please explain this recovery, that you suggest?
If the system doesn't make it to the next stage/screen, w/the android. I feel like something is missing to pass go, and collect $100 big one's, LOL!
Sent from my Nexus S
Note: I also attempting this through, ROM Manager. As Bootloader triggers same results. ROM's are all DL'ed from http://mirror.teamdouche.net/?device=crespo (Blank Stare)
Sent from my Nexus S
adb update:
cmd
cd c:\androidsdk\tools
fastboot flash recovery recovery.img
ENTER
Figured it out through trial, and error.
Hope this helps fellow XDA members.
Thanks for your efforts, and taking the time to help with this issue.
Sent from my Nexus S
Red Fox said:
adb update:
cmd
cd c:\androidsdk\tools
fastboot flash recovery recovery.img
ENTER
Figured it out through trial, and error.
Hope this helps fellow XDA members.
Thanks for your efforts, and taking the time to help with this issue.
Sent from my Nexus S
Click to expand...
Click to collapse
I do have exactly the same problem.
Which recovery.img did you flash?
stiefa00 said:
I do have exactly the same problem.
Which recovery.img did you flash?
Click to expand...
Click to collapse
Here is the recovery.img that I flashed:
http://www.megaupload.com/?d=C933QJOO
Same recovery.img used when rooting, here is the source:
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
Sent from my Nexus S
Another alternative, Terminal Emulator:
- install recovery to sd-card(no folders)
- Terminal:
su
flash_image recovery /sdcard/name-of-recovery.img
-=Edit=-
Phone should pause for a second and then show you a new blank line. Turn it off and back on. Holding down VolumeUp and Power to ensure it flashed correctly. Done.
Sent from my Nexus S
thx, got it!
Dunno if mine is the same problem.
My recovery seems to "reset" itself after every reboot. I have done it from ROM manager also also fastboot.
1. I flash the recovery
2. reboot
3. recovery comes up fine
4. reboot again, it show me this triangle sign with a exclamation mark inside.
So i need to fastboot/ROM manager everytime I want to go into the clockwork recovery.
ykphuah said:
Dunno if mine is the same problem.
My recovery seems to "reset" itself after every reboot. I have done it from ROM manager also also fastboot.
1. I flash the recovery
2. reboot
3. recovery comes up fine
4. reboot again, it show me this triangle sign with a exclamation mark inside.
So i need to fastboot/ROM manager everytime I want to go into the clockwork recovery.
Click to expand...
Click to collapse
Dude, this is discussed in multiple threads already.
The OTA 2.3.1 and 2.3.2 updates place a new script in the /etc folder that checks the crc on your recovery image at every bootup. If it fails, a backup copy of stock replaces it.
If you want to stay on Clockwork, you need to rename the file /etc/install-recovery.sh to something like /etc/install-recovery.sh.bak
Ah ok thanks! I din know where or what term to search for this.

[Q] Cannot boot into recovery. Laggy phone as well.

I was just about to try updating from NScollab 1.0.39 to 1.0.40 and for some reason my nexus s refuses to boot into recovery. It doesn't seem to exist anymore. Im not sure if it is related or not but my phone became very laggy after my first failed attempt to boot into recovery. I tried fixing user permissions and rebooting many many times but it doesn't seem to help.
What does it do when u try to boot into recovery?
Sent from my HTC Sensation 4G using XDA App
It doesnt do anything. It just reboots into the bootloader.
Thank you for the quick reply
edit:
i tried flashing recovery again through rom manager and now whenever i try to boot into recovery it just hangs at the google logo with the unlocked padlock.
Hmmm
Do me a quick favor.
go here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and download the 4.0.0.2 recovery image and save it to some directory on ur computer
then follow these steps:
1. Open up command prompt/terminal and plug in phone to computer
2. Type "adb reboot bootloader"
3. It will take you to fastboot mode. Now type "fastboot erase recovery"
4. Then type fastboot "flash recovery ____.img"
( ____ is the name of the recovery img file)
5. Now it will flash and once it says "OKAY" then scroll down using volume down into recovery and see what happens
plz get back to me bout this!
IT WORKS! It went into recovery! Thank you so so much! Is there anything else I should do or am i set to go?
i so hate rom manager! i cant believe that people still use it
shahravi94 said:
IT WORKS! It went into recovery! Thank you so so much! Is there anything else I should do or am i set to go?
Click to expand...
Click to collapse
Since it works, you can wipe and flash ns collab lol
Sent from my HTC Sensation 4G using XDA App
Thank you so much for the quick help! btw i updated recovery from rom manager and i ran into the same problem with it not booting into recovery so i am guessing there is a problem with the latest version of recovery? I'll just reflash through the instructions you gave me.
Yeah prolly a ROM manager issue
Sent from my HTC Sensation 4G using XDA App
shahravi94 said:
Thank you so much for the quick help! btw i updated recovery from rom manager and i ran into the same problem with it not booting into recovery so i am guessing there is a problem with the latest version of recovery? I'll just reflash through the instructions you gave me.
Click to expand...
Click to collapse
the recovery generally doesnt stick if flashing it through rom manager. flash it through fastboot and itll stick.
Hmm thanks for the advice! ill keep that in mind

[Q] White triangle with exclamation (sigh) instead of recovery mode

Hi,
I rooted my Samsung Infuse and flashed CM7 as explained in http://forum.xda-developers.com/showthread.php?t=1311960
It looks awesome, many thanks to the people who put it together. ( I couldn't reply there since I am a "noob")
My phone boots fine in to CM7 and I can make calls and use other hardware, no problem so far.
I was trying to get Gapps by going to Rom Manger -> Download ROM -> Scroll down to Google Apps. It reboots and ends up at the screen with the white triangle around an exclamation and the android icon. I do not get the ClockworkMod menu. I have to press and hold the power button to reboot normally and get back to CM7.
Am I missing the recovery executable file? I looked in /system/bin and /sbin and it is not there. Should I copy the one I used earlier in to /system.bin ?
Thank you.
I believe cwm can show that when it is working, on some builds you can toggle between it showing the files being copied and that screen with the power button if I remember right.
Thanks for the reply, Dani897.
I am trying to get the Google apps installed which I couldn't since the recovery mode isn't showing up.
Any hint how I can get them on?
suryathesun said:
Thanks for the reply, Dani897.
I am trying to get the Google apps installed which I couldn't since the recovery mode isn't showing up.
Any hint how I can get them on?
Click to expand...
Click to collapse
Not really sure, I don't run CM7. But if you are using ROM manager it might just start flashing and never enter the menu.
If it is hanging maybe you can find gapps.zip on xda somewhere and put it on the sd card. Then use the reboot into recovery option instead of the flash ROM option in ROM manager.
Why not install the. Apk's instead of flashing the Google aps
Sent from my SAMSUNG-SGH-I997R using xda premium
Dani897 said:
Not really sure, I don't run CM7. But if you are using ROM manager it might just start flashing and never enter the menu.
If it is hanging maybe you can find gapps.zip on xda somewhere and put it on the sd card. Then use the reboot into recovery option instead of the flash ROM option in ROM manager.
Click to expand...
Click to collapse
Thanks Dani897, didn't realize the reboot has recovery option. Now I have the Gapps installed.
In fact, CWM showed up when I rebooted into recovery mode. Wonder why ROM Manager couldn't do that.
suryathesun said:
Thanks Dani897, didn't realize the reboot has recovery option. Now I have the Gapps installed.
In fact, CWM showed up when I rebooted into recovery mode. Wonder why ROM Manager couldn't do that.
Click to expand...
Click to collapse
If I remember correct ROM manager has several options, 1 is to download and flash roms, 1 is to flash from sd card 1 is to reboot into recovery. if you use the first two options it goes into recovery but not the menu, it skips strait to flashing so you don't needed to do any more work, it only shows the menu if you reboot into recovery.
Sarius24 said:
Why not install the. Apk's instead of flashing the Google aps
Sent from my SAMSUNG-SGH-I997R using xda premium
Click to expand...
Click to collapse
Thanks for the reply Sarius24, I will try that the next time.
Do you happen to know of a reliable source for such apk's?
Dani897 said:
If I remember correct ROM manager has several options, 1 is to download and flash roms, 1 is to flash from sd card 1 is to reboot into recovery. if you use the first two options it goes into recovery but not the menu, it skips strait to flashing so you don't needed to do any more work, it only shows the menu if you reboot into recovery.
Click to expand...
Click to collapse
Good to know that. In fact, I tried the "Download ROM" option which downloaded the Gapps zip and rebooted in to the white triangle screen.
Now moving onto fixing other issues
Thank you.

Recovery loop ****** fixed******** With resolution

For all who are having issues with custom recovery not working, rebooting etc. flash the linked file. The issue stems from using reboot to recovery commands in android rather than using vol-,power button combo from power off. In the future, ONLY use the combo.
Major thanks to gee one for the file.
http://www.mediafire.com/?5ih9s5i59xys9zd
Been on various versions of ics for a while now. As I don't use my tf all the time (might go a couple of weeks without touching) i came to update to latest revolver today and every time I reboot it takes me back to cwm. I can cold boot into the system but thats not a good resolution, especially as i am thinking of selling.
Tried wiping system, reflashing and booting from cwm or off.
Sent from my Transformer TF101 using xda premium
Did you use ROM manager to flash CWM? It can cause bootloops.. Try roaches repacked touch thread, he's got a diff of the fix there.
Hmm. Tried flashing roaches touch but it wont stick. Also tried updating to the latest from rom manager but that wont stick either.
I use 4ext recovery on my desire z but the app isnt available from tablets (mine anyway).
I run linux and dont have adb setup. Is there any other way to flash recovery?
Sent from my Transformer TF101 using xda premium
No, what I mean is, use the fix in Roach's thread to fix recovery. Don't just ROM manager, it just doesn't work on the tf101 very well. Use Gnufabio's RecoveryInstaller app (in development) to flash CWM 3.2.0.1 then update to a later if you wish, manually without ROM manager.
^^
Reading your post, if you have no access to android on your tab (you have ubuntu only) then you need to set up adb to fix it. I assume you're running android though.
Your right. I could cold boot to android. After following your aim I landed on a nice little file to flash that wipes the reboot to recovery. The initial issue was worse than I thought. Anything I flashed wouldn't take regardless of what the scrolling text said.
Even though this thread is so short I am going to update the OP with the details for others as it seems quite a common issue.
To summarise, its all fixed.
Sent from my Transformer TF101 using xda premium
The bad thing is .. I can't even cold boot into android ..
As of my knowledge cold-booting is volume-down + power.
This only takes me to recovery again, no matter what I do..
So when you hit the button combo do you see the asus screen with some writing at the top left? Something along the lines of 'press up for recovery or wait 5 secs for other options'.
Sent from my HTC Vision using xda premium
If you can access adb shell from recovery, flash a new recovery using:
su
dd if=/your/blob/here of=/dev/block/mmcblk0p4
reboot
Place the recoveryblob extracted from the CWM flashable zip somewhere on your tf accessible from cwm.
MarkyG82 said:
For all who are having issues with custom recovery not working, rebooting etc. flash the linked file. The issue stems from using reboot to recovery commands in android rather than using vol-,power button combo from power off. In the future, ONLY use the combo.
Major thanks to gee one for the file.
http://www.mediafire.com/?5ih9s5i59xys9zd
Been on various versions of ics for a while now. As I don't use my tf all the time (might go a couple of weeks without touching) i came to update to latest revolver today and every time I reboot it takes me back to cwm. I can cold boot into the system but thats not a good resolution, especially as i am thinking of selling.
Tried wiping system, reflashing and booting from cwm or off.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Had to use it tonight big thanks..
I have the same problem, after flash a kernel [KERNEL][ICS] Harmony (OC/UV), boot loop on recovery (rogue XM 1.5.0), tried in adb to push a recovery blob, but don't work....
Line error is /sbin/sh: push: not found
The same with the other comand, like: device, /sbin/sh: device: not found
I have tried a flash, new rom, new kernel, new recovery, any trick but nothing!!!
in adb only reboot comand work
Help me please
try the /temp/ folder or somewhere like that, which doesn't need system write permissions, or mount the system as writable. The commands to use after getting the blob on are a few posts up.
I've try this, dd if=/sdcard/blobrecovery of=/dev/block/mmcblk0p4 end adb whrite new recoveryblob, but after reboot won't work, restart anytimes on recovery....
If nothing else works, try NvFlash (in my sig) just released for Sbkv2
I also facing same problem. When i switch on my pad every time going to recovery mod can't go to android. restart anytimes on recovery....
Try a reflash of recovery, if all else fails, Nvflash.
Ok so run into same problem. However I can't get ADB to recognize it, I also can't get it to cold boot. Then lastly I can't get the version on her to see the sd card so I can't even load files onto the tablet to even try running the one script that was on here. Any suggestions from here?
Ok so managed to get it back to cold boot after running a new rom into it. Dunno why that'd work but it did. Gonna keep this file in place permanently. Would still like to see other options if you were in my spot since everything seems to rely on everything I was missing.
Nvflash. Yet again, only true rescue in a really bad brick situation.
MarkyG82 said:
Your right. I could cold boot to android. After following your aim I landed on a nice little file to flash that wipes the reboot to recovery. The initial issue was worse than I thought. Anything I flashed wouldn't take regardless of what the scrolling text said.
Even though this thread is so short I am going to update the OP with the details for others as it seems quite a common issue.
To summarise, its all fixed.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Hi Marky,
Can you help me how you fix your problem because i also facing same problem.
Minnaing.
Can you cold-boot to android? Volume down + power and wait.
yes, I can go cool-boot to android.with Vol+

[Q] My Oneplus stuck on bolt symbol

So anyway i'm new here,,,,i just buy my oneplus several days ago,after several days of usage i found that i have microphone issue with ok google,so i look for option and i found some help here (i cant post link,its from youtube)
But to do that i must root oneplus so i did it,i instal supersu and using twrp recovery,after the phone rooted,i check again using root checker and it work,after that i tried to do method from youtube to fix my microphone,
After i found the mixed-path.xml,i changed the value but i cant save it,so go out and change the permission,then go to that file again,strangely i can't find the syntax again,i open the same file but the syntax is not there anymore...so i go out to homescreen and then try to reboot.
The problem now is my phone won't boot up,it stuck on the logo that look like bolt spinning,,,,any idea what should i do now?
I'm confused when you say the bolt symbol. Is it the one of the CyanogenMod Inc logo?
Boot into twrp. Fully turn your phone off and then hold volume down + power, adb sideload and then flash one of the zips of your choice. http://forum.xda-developers.com/showthread.php?t=2835010
Be more careful next time. If this helped you, give it a thanks
Sent from my One using Tapatalk
zephiK said:
I'm confused when you say the bolt symbol. Is it the one of the CyanogenMod Inc logo?
Boot into twrp. Fully turn your phone off and then hold volume down + power, adb sideload and then flash one of the zips of your choice. http://forum.xda-developers.com/showthread.php?t=2835010
Be more careful next time. If this helped you, give it a thanks
Sent from my One using Tapatalk
Click to expand...
Click to collapse
U know bolt symbol like hexagon spinning,actually few hours ago i tried wipe cache from recovery mode then reboot but still stuck at hexagon spinning,so give up and then i go to recovery mode to factory reset,but still it stuck at hexagon symbol,so i tried using fast boot and using twrc i tried to flash cm11 but i can't find it,it seem it get deleted too from facrory reset,,,so i googling and have an idea flashing new cyanogen m9 on my oneplus,but now the problem is i don't really understand how to send file from my pc to my oneplus,,,the command i dont get it,is there any simple tutorial for that matter?thanks btw
foxzeaker77 said:
U know bolt symbol like hexagon spinning,actually few hours ago i tried wipe cache from recovery mode then reboot but still stuck at hexagon spinning,so give up and then i go to recovery mode to factory reset,but still it stuck at hexagon symbol,so i tried using fast boot and using twrc i tried to flash cm11 but i can't find it,it seem it get deleted too from facrory reset,,,so i googling and have an idea flashing new cyanogen m9 on my oneplus,but now the problem is i don't really understand how to send file from my pc to my oneplus,,,the command i dont get it,is there any simple tutorial for that matter?thanks btw
Click to expand...
Click to collapse
Did you try ADB Sideload as I mentioned? Do you have ADB set up?
To elaborate what I said on earlier,
- you need to boot your phone into recovery
- factory wipe
- advanced in twrp -> sideload
- while you're at this, select the two options to wipe and then swipe.... then type,
Code:
adb sideload <name-of-zip>.zip
and then once you type that it'll be sent to the phone and then you can sideload flash. After that reboot and then your phone will start up again.
ADB Sideload: http://teamw.in/ADBSideload
@foxzeaker77, just to clarify, it isn't called a bolt symbol, it's boot, and more correctly, boot animation.
Transmitted via Bacon

Categories

Resources