Stuck on clockwork recovery - Blade General

So, I converted my Blade from gen 1 to gen 2, and now it will only ever boot into recovery. I have an update.zip on my sd card that I am trying to apply, but it just hangs on the same screen.
Is there anything I can do?
edit: I managed to run the update.zip (I used the stock orange ROM) but now it's just hanging on the green android.
edit2: Another update, now I can't access clockwork recovery at all.
edit3: Yep, another update. Through the method outlined here I managed to get it back to recovery. I tried to install Swedish Springs but it still boots into ClockworkMod Recovery.

Related

Unlockr didn't totally work. Did nandroid restore. Not sure where I am now.

I tried yesterday to one-click root my MT3G following unlockr.
Got the Amon-Ra recovery on there, but it hung on the green MT3G splash screen when I tried flashing cyanogen 4.1.11 .
Waited like over 20 minutes. So I took out battery, and tried to boot again. Same thing. So I rebooted into recovery and tried flashing ROM again.
No matter what ROM I tried, I got a "E:Can't open /sdcard/update.zip (bad)" message. (I redownloaded ROMs from different sources given the message thinking maybe they were bad or incomlplete, but nothing worked).
I finally did a nandroid restore.
Now I'm not sure where I am. Given that I restored my stock nandroid backup, my understanding is I'm no longer rooted. Though, I am still able to boot into the Amon-Ra recovery. which I thought would have not still been possible. I downloaded better terminal and tried typing "su" but it wouldn't let me continue, so that confirms not rooted, right?
Do I run the recovery flasher app again (which is still on the phone), and reflash a recovery image? Or should I delete the app and redownload the recovery flasher apk.
Just not sure how to safely retry.
You need to provide more details about your process. I actually unrooted mine previously done with Cyanogen Recovery and rerooted with same instructions on that site only this time with Amon Ra recovery image without problems. In my case I wanted the option of formatting partitions. Maybe you should try Cyanogen stable Rom first, like 3.68.1 version. I had an issue with 4.1.11.1 after I partitioned the card so I did 3.68.1>4.0.4>4.1.11.1.

[Q] Can't boot into recovery after flashing new CW 3.0.2.4 recovery help!!!

So... I was rooted using gfree method and had recovery 2.5.1.4 installed running the ice glacier rom. Then I decided i was going to upgrade to a gingerbread rom so I updated my rom manager and flashed the new CW 3.0.2.4 rom and now it wont boot into recovery. When I try to boot into recovery it shows the mytouch logo for a bit, the screen turns black and the phone reboots. I tried to flash the old recovery again but I get an error message saying: An error occurred while flashing your recovery. I can still flash CW 3.0.2.4 and CW 3.0.0.5 but both will not boot into recovery.
I also tried flashing the 3.0.2.4 recovery manually through fastboot flash recovery recovery.img but I still get the same problem. I couldn't find an active download link for the 2.5.1.4 recovery to try to flash manually so I don't know if it helps to do this.
I read on the forum somewhere to revert back to stock recovery using the stock PD15IMG IMG file and try again. This took me back to stock and I was able to boot into the stock recovery. Then i reran visionary for permroot again, deleted my clockworks folder from my sdcard and tried again, but the problem came back.... Mytouch logo then black screen then auto reboot.
My root access still works fine but I cant get into recovery to flash a new rom.... and now I am stuck on a stock rom. :[ After 6 hours of trying to fix the issue I'm still very confused.
Any help / suggestions would be appreciated Thanks.
Its doing this after you go into hboot and select "Recovery"?
JDV28 said:
Its doing this after you go into hboot and select "Recovery"?
Click to expand...
Click to collapse
Yes, from Hboot and from rom manager, but sometimes if i try from rom manager it will also hang at the white mytouch logo screen.
Update
Ok. So i have a partially functional recovery again i found the recovery image for 2.5.1.2 and flashed it using fastboot flash. I am now able to get into recovery again and install custom froyo roms, but every time i try to upgrade to a higher version like 3.0.0.5 or 3.0.2.5 no matter which method i use, I still get the same reboot while trying to get into recovery.
Please help. Thanks

[Q] Apparently I screwed up. SOLVED!

I have my nook rooted and all of that and for some reason I decided to wipe the thing clean in CWM recovery and now it won't boot to anything unless I boot from SD. I've tried booting into a rom from SD and installing CWM recovery again through rom manager and it says that is has flashed successfully but when I tell it to restart it goes back to the rom on the SD of course, so I tried taking the SD out and holding down the N and booting into recovery and I get nothing no loading screen no nothing, am I not getting CWM installed? Is there a zip I can flash from CWM on SD to flash it?
EDIT!!!!! If i had remembered to format the right things then I wouldn't have had an issue.
If you are having the problem described above remember to format BOOT, System, and Data. And then flash your rom.
See post#4 here: http://forum.xda-developers.com/showthread.php?t=1205047
Thank you I don't know what I was thinking, if I had just formated the right things it would have worked just fine, I am a tard sometimes.

Recovery not "sticking" ?

Hey guys, I have a weird issue. I recently (re)aquired a MyTouch 3G Slide after selling my old one. The other I rooted back when rooting was still super-hard. I bought it the day it came out, and had CyanogenMod7 running beautifully and everything.
The "new" mytouch 3g slide I aquired was factory reset (s-on) on 2.1. I tried to update to 2.2, but HTCs website doesnt seem to have the files anymore. So I rooted it using UniversalAndroot. I tried to run RomManager to flash recovery, but as you know, it no longer supports 2.1 and below, so that sucked.
I found an old version on here, flashed it as update.zip, and everything was good.
Now that I'm rooted I flash CyanogenMod7 and GAPPS. Everything installs fine, except GAPPS didn't. So I reboot into recovery, and I see it's stock again. Hmmm, strange. I install update.zip again, recovery comes back, I flash GAPPS again, this time only the market installs. Fine with me.
I reboot into recovery to make a back-up after installing everything. Strange...stock recovery AGAIN. Install update.zip, everything is fine, create my backup, reboot and I update CWM through RomManager, everything's good. Reboot into recovery. STOCK RECOVERY AGAIN.
It seems the only way to get into CWM is to flash update.zip (luckily only takes a few seconds), but is there anyway to make it stick? I had to force update SuperUser as well, and a few other things.
So my question is, if I downgrade to stock 2.2 from HTC, root, then reupgrade to Cyanogenmod 7, would all my issues be fixed?
Update.zip will NOT change the recovery; it will only allow you to use the custom recovery for that certain time. You must obtain the recovery image(recovery.img) and then boot into fastboot(press vol-down+power, then press power) and, on your computer, move the recovery.img to the same directory as fastboot and then, still on your computer, type fastboot flash recovery recovery.img, and there you go

ASCER A500, bootload v9, TWRP 2.6.3 unable to boot primary ROM

I have an Acer A500, it has the v9 bootloader installed. I also have TWRP 2.6.3 installed as the secondary ROM, the recovery is also completely broken, fastboot and zip will not install on it (TWRP 2.6 is to big), but recovery using 2.4.4.0 does boot. That fine since with secondary and recovery installed I can use TWRP from either, which works great, but if I install a ROM it only boots once, then poof, its as if there is no kernel it will not boot. To boot a new ROM I have to format everything except the external SD (which I have removed) then install the ROM reboot to TWRP install it again, then reboot at which time it will boot about 1 is 3 times, if it fails try again and repeat.
Now the ACER is basically useless now as I can not boot safely to anything other than TWRP, I've tried 2 4.0.3 ROMs but I can not get the Installers to run, I've tried 2 10.1 ROMS boot both booted only once and also a 4.3 ROM (build 5 and 6) boot again both booted only once. I'm out of ideas I'd flash almost anything at this point to reset, but then there is that Windows 8.1 issue in which I can not get ACER driver to work (Duh!), and I do not think the issue is going to be fixed, I can only come up with 2 options 1 the internal storage is going bad, or the entire setup is just toast, since it can work, it just does not do so more than once.
Currently I have 10.2 (build6) running, so long as I do not need to reboot, so for now it is charging.
Any suggestions,
ERIC
egandt said:
Now the ACER is basically useless now as I can not boot safely to anything other than TWRP
ERIC
Click to expand...
Click to collapse
I have same problem with TWRP. Try to replace TWRP with TouchRecovery

Categories

Resources