Does anyone else have a problem entering CWM recovery 1.4.2?
When I try to enter CWM recovery rev1.4.2, after the 'acer' logo and 4th line - 'Booting recovery kernel image', my screen goes blank(black screen) for about 25-30seconds. Then, it automatically reboots into normal mode (i.e. lock screen, which I'm able to enter as normal). CWM up to Rev1.3.4 is ok. Reverting back to 1.3.4 is the only way to enter recovery.
ps: I get exactly the same results with rev1.4 and 1.4.1 (i.e. auto reboots into normal mode)
There is a 1.4.5 version out. Think since yesterday.
erica_renee said:
There is a 1.4.5 version out. Think since yesterday.
Click to expand...
Click to collapse
Where did you find it. It's still 1.4.2 on tegraowners website.
Update the Acer recovery installer app.then use it to reinstall the latest recovery.is what I did. Im sorry I typed it incorrectly.
Acer recovery installer latest version
erica_renee said:
Update the Acer recovery installer app.then use it to reinstall the latest recovery.is what I did. Im sorry I typed it incorrectly.
Acer recovery installer latest version
Click to expand...
Click to collapse
I had a feeling you were talking about the Acer Recovery Installer. BTW, the latest version of it is v2.42.
That's what I used to install Thor's rev1.4.2. I also use adb method as well. My problem starts after I've installed thor's latest clockwork recovery image (which is rev1.4.2) using either of the ADB method or the Acer Recovery installer. Sorry, should have made my question clearer.
Does anyone know how find the log of a failed boot into CWM to find out why it failed? Internet searches aren't giving me anything. I can enable 'report error' in rev1.3.2 which gives me a log of the recovery boot, but it is only for that boot. I can't do that when I upgrade to rev1.4.2. Because I can't even get to the recovery page. Something is stopping it from booting into CWM.
Related
Searched, but couldn't find an answer to this. I rooted and installed ROM Manager so I can do a nandroid backup before installing a custom ROM. However, when I press back up in ROM Manager, it restarts and hangs/freezes on the HTC MyTouch 4g splash screen.
What am I doing wrong?
Have you flashed CWM recovery after installing Rom Manager. You must flash the recovery before you can backup/restore or install roms. I almost did that myself but luckily i read the thread concerning it again and flashed REcovery before trying to back up rom.
Yeah, I did that first and the problem remains. I just uninstalled and reinstalled ROM Manager and am about to try "backup current rom" again (unless I should reboot into recovery and back up from clockwork recovery?).
FWIW; Current recovery is ClockworkMod 2.5.1.2
anyone?
Did you ever find a solution to this problem? I just started getting exactly the same. Cant reboot manually into clockwork recovery or from Rom manager :/
If you have flashed a recovery beyond that supported by ROM manager, you will not be able to perform recovery functions from the app (i.e. backup). CW3 is required for CM7 ROMs, but will not be supported by ROM manager until the CM7 RC drops. You can still manually boot to recovery (I always Vol up when powering then select Recovery) and if you have CM7 nightly installed, it has a "reboot to recovery" option in the reboot menu.
You need CWM3 to use CM7.
neronian said:
anyone?
Click to expand...
Click to collapse
Sometimes it is necessary to flash clockwork recovery more than once before it will actually stick. Also, occasionally it will freeze on the splashscreen after a backup, but a battery pull and turning out the phone should be fine.
Sent from my HTC Glacier using XDA App
Here's what's going on:
The Clockworkmod Recovery that you can download from the Market only supports up to CyanogenMod 6.x. For CM7, you need to install Clockworkmod Recovery 3.x, but that version isn't available on the Market yet.
What this means is that you need to find the image file for a CWR 3.x on these forums and manually install it through either a terminal emulator or fastboot. The post below explains how to do it:
http://forum.xda-developers.com/showpost.php?p=10862819&postcount=3
If you flash CM7 using CWR 2.x, your phone won't boot. There's just no way around it.
hammondnav said:
Here's what's going on:
The Clockworkmod Recovery that you can download from the Market only supports up to CyanogenMod 6.x. For CM7, you need to install Clockworkmod Recovery 3.x, but that version isn't available on the Market yet.
What this means is that you need to find the image file for a CWR 3.x on these forums and manually install it through either a terminal emulator or fastboot. The post below explains how to do it:
http://forum.xda-developers.com/showpost.php?p=10862819&postcount=3
If you flash CM7 using CWR 2.x, your phone won't boot. There's just no way around it.
Click to expand...
Click to collapse
Careful with the terminology there. ROM Manager, the app you download from the Market, is a GUI front-end to the CWM recovery image, but you can download and install CWM without using ROM Manager at all. Just because you have ROM Manager installed doesn't mean that CWM recovery is also successfully installed.
TeeJay3800 said:
Careful with the terminology there. ROM Manager, the app you download from the Market, is a GUI front-end to the CWM recovery image, but you can download and install CWM without using ROM Manager at all. Just because you have ROM Manager installed doesn't mean that CWM recovery is also successfully installed.
Click to expand...
Click to collapse
Thanks for pointing that out. I didn't imply that CW ROM Manager and CW Recovery are the same thing though...
hammondnav said:
Thanks for pointing that out. I didn't imply that CW ROM Manager and CW Recovery are the same thing though...
Click to expand...
Click to collapse
You said "the Clockworkmod Recovery that you can download from the Market", and that kinda does. No biggie though.
Just an update for my problem, it turned out that clockwork recovery had corrupted for whatever reason and couldn't be reinstalled from rom manager. As I wanted to test Cm7 anyways I just ended up flashing clockwork recovery 3 manually through fastboot and its all gravy again
Sent from my Desire HD using XDA App
How to flash clockwork recovery from fastboot or fron clockwork recovery 2.51?
Sent from my SGH-T959 using XDA App
Thanks, everyone. What happened with mine, I have no idea, but I randomly opened rom manager and was greeted with an update to the recovery. So I downloaded it and voila - I can now boot into recovery and do backups, etc...
PLEASE USE THE CWM UPDATE BY KOUSH ONLY.. ALSO, PLEASE BE ADVISED THAT CWM VERSION 5.5.0.4 has been reported to have some freeze issues, contact Koush and forward a logcat or provide information so he can resolve. Until then, use an earlier version until all the bugs are gone..... thank you--- oka1 moderator
Today I noticed That Koush Has released CWM 5.5.04 for Our device. So simply You can Download Rom manager from Market and then just install the CWM.
AllCredits go to KOUSH.
Here IS the .img file.
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-tf101.img
Installed fine. Reboot to recovery still doesn't work for me. Still works fine when using the app from the market though. Thanks for the heads up.
Reboot to recovery messed up my tab, so it would only boot into recovery (booting to Android was done manually).
works either manually or via market app reboot to recovery, via ClockworkMod restart the system, is not in recovery
"reboot system now" does not work, reboot into recovery again.
Same to me on my tab. Don't install it yet.
Unable to install either through rom manager
or
Terminal method
Rom manger says it installed it but when I reboot to revocery (via another app)
it's still the old one
Terminal emulator says image not found no matter where I store it or what directory I point to
Seems like I'm missing something.
The linked .img file is a blob file with the SOS partition. It can be flashed through the staging partition. If you extract it or strip out the header, it will be a regular .img file that can be flashed through cwm (with a little work).
I haven't flashed it yet.
Same here, unable to boot android again (recovery loop), is there any way to flash the old one from adb?
Thanks
bug
since i have instal it i can't go out of the recovery when i do restart and it reboot in recovery again
go out by pressing power button + volume down , wait a moment and you can select recovery or boot android os
If you go into advanced there's no option to return.
Wasn't there a bug about installing recovery with Rom Manager that causes constant boots into recovery?
let me look...
EDIT: This may or may not apply, but ...
http://forum.xda-developers.com/showthread.php?t=151963
Official, yes, see here the 5.5.0.4 for tf101, the .img and .zip:
http://download.clockworkmod.com/recoveries/
I should have read more of this thread before flashing. Because now mine does what everyone else is doing. Goes back into the recovery in a loop..
If You have problems return to the older:
http://forum.xda-developers.com/showthread.php?t=1346180
=================
mine flashed fine from rom manager pro on Eos-tf101-5 All menu's seem to work fine, but there is no external SD access only internal. Still can't access recovery from rom manager but that's the same standard issue with the rom.
it support tf101g or not ?
Cant flash a new recovery either.
Tried reflashing rogue and still boot loops into cwm.
Downloaded current cwm from web link above and flashed. Still boot loops into recovery.
Sent from my Transformer TF101 using Tapatalk
I would love to go back to the older one...But my Tab doesnt show the sdcard at all. Only internal memory...weird
Flashing the IMG via NVFLASH broke recovery for me. Installing it through ROM Managers works fine.
I can access my recovery, and flash roms from the SD, however no matter what ROM I tried, I get a boot loop.
I have Skrilax_CZ bootloader v8
CWM Recovery v5.5.0.x
Any suggestions or ideas?
Thank you!
Another note, I used to have a working rom in my downloads folder on the device, however from recovery, when i go to choose zip from internal storage i get "E:Can't mount /sdcard/"
Thank you!
jrichardsMav said:
Another note, I used to have a working rom in my downloads folder on the device, however from recovery, when i go to choose zip from internal storage i get "E:Can't mount /sdcard/"
Thank you!
Click to expand...
Click to collapse
Just tried to do a restore on a backup I made sometime ago.
I got "Error formating data"
Rebooted, and I get a screen saying
"Encryption Unscuccessful" with a button to reset tablet
I press that, tablet reboots to recovery, and i get an android bot with a spinning pentagram, then the bot is on its back with a red exclamation point.
Okay got it booting! Well, booting to honeycomb, everything is kind of a blur right now, but I flashed a 3.2 rom
got the enter a password screen
did the following:
http://forum.xda-developers.com/showpost.php?p=33607638&postcount=9
Now i can boot to android, but i can't boot to a recovery!!
Help?! lol
jrichardsMav said:
Okay got it booting! Well, booting to honeycomb, everything is kind of a blur right now, but I flashed a 3.2 rom
got the enter a password screen
did the following:
http://forum.xda-developers.com/showpost.php?p=33607638&postcount=9
Now i can boot to android, but i can't boot to a recovery!!
Help?! lol
Click to expand...
Click to collapse
Im actually on 3.1! and I've rooted 3.1. I'm trying to install a recovery image now, TWRP or CWM. I've tried the Goomanager method and the Acer REcovery Installer method, both force close before the recovery is installed.
jrichardsMav said:
Im actually on 3.1! and I've rooted 3.1. I'm trying to install a recovery image now, TWRP or CWM. I've tried the Goomanager method and the Acer REcovery Installer method, both force close before the recovery is installed.
Click to expand...
Click to collapse
Had to install ARI from PLAY, not MARKET.
Now flashing 4.2 + gapps. Crosses fingers.
jrichardsMav said:
Had to install ARI from PLAY, not MARKET.
Now flashing 4.2 + gapps. Crosses fingers.
Click to expand...
Click to collapse
Everything working. 4.2.1 on A500 is very nice. Multi user is beautiful.
Sorry have only just seen your posts - awesome you managed to get yourself fixed!!!!
So you had HC 3.1 with the v8 bootloader and you flashed the JB rom directly from there?? I know doing it this way has worked for me in the past its great to know someone else has luck doing it as well...
one more thing can you edit the subject line of your original post to "fixed" or "solved" - this will help others who may be in the same postion!!!
thanx and have a great 2013!!!
dibb
Sure can, if I can figure out how to edit the title.
I had 4.1, a tegraowners rom, then i had a random reboot and no matter what rom I flashed it would fail.
I tried to install a 3.1 rom, which gave me the encrypted message asking me for a password.
I then booted to fastboot, ran a few commands that I found, and got 3.1 working.
Rooted, Installed a new recovery (mine was botched) and got 4.2 working on it!
I'd like to learn more about rom development. Any good places to start?
Thanks for that...can't help re rom dev but XDA have new site"xda-university" there's a bit about rom dev there that may be helpful...good luck tho
Sent from my GT-I9300 using Tapatalk 2
Hey all, trying to flash CM10.2 on my G2 and I'm not able to boot into a custom recovery. Here's how I did everything.
Rooted - all was successful as far as I can tell. Was able to install Titanium backup and backup files and allow root.
I downloaded ROM Manager and installed CWM. When I went to boot into recovery, i get the error with the Android a red triangle exclamation point above him. So I tried to switch to TWRP through Rom manager, no luck. I tried to 'flash' TWRP through the command prompt and download of the recovery file, no luck.
I saw somewhere to download SuperSU, so I did that and tried again, and same issues. When I 'cleaned' SuperSU, uninstalled and reinstalled it but this time chose 'use custom recovery' - it tied to reboot into recovery, saw a standing up right android with a spinning icon, but then went to the same error.
Obviously I'm missing something somewhere. Can't figure out what.
Thanks for any help!
Don't use rom manager. Either use adb and push the recovery or use the app flashify to install the recovery. There are many threads ids the development sections on how to install recoveries
Sent from my LG-D800 using Tapatalk
tdevaughn said:
Don't use rom manager. Either use adb and push the recovery or use the app flashify to install the recovery. There are many threads ids the development sections on how to install recoveries
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Thanks, Is there a way to undo what I've done from rom manager? Because I used adb to push the recovery and still had the same issue, and using flashify to flash the image doesn't seem to work. Booting into recovery just gets me to stock recovery asking 'do you want to factory wipe your device'
Edit: When I boot to recovery from within flashify, it gives a 'boot certification error' upon booting
goldenmonkey1 said:
Thanks, Is there a way to undo what I've done from rom manager? Because I used adb to push the recovery and still had the same issue, and using flashify to flash the image doesn't seem to work. Booting into recovery just gets me to stock recovery asking 'do you want to factory wipe your device'
Edit: When I boot to recovery from within flashify, it gives a 'boot certification error' upon booting
Click to expand...
Click to collapse
Are you using a recovery that has been Loki'd. The G2 needs this to by pass the bootloader. By that error it does not seem you used the correct recovery file.
Jimi Mack said:
Are you using a recovery that has been Loki'd. The G2 needs this to by pass the bootloader. By that error it does not seem you used the correct recovery file.
Click to expand...
Click to collapse
I used the one from here - http://forum.xda-developers.com/showthread.php?t=2449670 - 2.6.3.3 and just flashed it with flashify most recently. But I was having the same issue when I installed it via adb and 'option 1' as shown there.
Yeah, when flashing that recovery image using option 1, I still get "secure booting error - boot certification verify" after I reboot into recovery
Huh, I got it.
Reading this post here - http://forum.xda-developers.com/showpost.php?p=48118278&postcount=567
Someone else was having the same issue as me. The newest recovery gave him that same error. Flashed 2.6.3.2 and it worked fine. (So far)
Glad to hear. Good Luck.
Just wondering if you can help me guys.
So, after i've rooted my device and placed CMW version 5.0.2.6 into it. suddenly after clicked reboot system in recovery mode, it just returns to recovery mode. Its like a reboot loop, but its in the recovery mode. PLEASE help me.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
jasonaleclim said:
Just wondering if you can help me guys.
So, after i've rooted my device and placed CMW version 5.0.2.6 into it. suddenly after clicked reboot system in recovery mode, it just returns to recovery mode. Its like a reboot loop, but its in the recovery mode. PLEASE help me.
Click to expand...
Click to collapse
Format everything
Mount everything
INSTALL A ROM which is compatible with cwm** version 5.0.2.6
jasonaleclim said:
Just wondering if you can help me guys.
So, after i've rooted my device and placed CMW version 5.0.2.6 into it. suddenly after clicked reboot system in recovery mode, it just returns to recovery mode. Its like a reboot loop, but its in the recovery mode. PLEASE help me.
Click to expand...
Click to collapse
How did you install cwm?
There's only two ways to get cwm on 5360
Temp cwm
Flash this in stock recovery every time you need cwm
Perminant cwm
This is built into a custom kernel & replaces stock kernel & recovery
If you chose the later it's most likely the kernel you
flashed is not compatible with the rom/file system you are using
More information about what you are using & what you did is required
If all else fails flash stock rom via odin and start again