Hello,
i have a big problem. I tried to flash the overclocked kernel with my EUR Xoom. This bricked it.
I only get into fastboot. How to restore a clockwork recovery image i made before or how to get into clockwork.
Or do I have to do something else to restore the Xoom?
EDIT: I just flashed the boot.img from the clockwork recovery. That worked!
Related
not sure if this is what everyone is already doing, but I was trying to figure out how it might work
stock ota 2.3.1 os
fastboot oem unlock
flashed clockworkmod recovery
boot into recovery nandroid backup stock non-rooted os (just in case )
flash su-2.3.6.1....zip
nandroid backup again
take the boot.img from this nandroid backup and fastboot flash boot
onicrom said:
not sure if this is what everyone is already doing, but I was trying to figure out how it might work
stock ota 2.3.1 os
fastboot oem unlock
flashed clockworkmod recovery
boot into recovery nandroid backup stock non-rooted os (just in case )
flash su-2.3.6.1....zip
nandroid backup again
take the boot.img from this nandroid backup and fastboot flash boot
Click to expand...
Click to collapse
No.
10chars
fastboot oem unlock
flash cwm recovery
nandroid backup
mount /system
flash the su-2361 zip
boot up
rename/delete /etc/recovery.sh (or whatever the exact file is)
download rom manager, flash latest cwm (as of right now it's 3.0.0.5)
reboot to recovery to make sure cwm loads properly and updated.
done.
nxt said:
download rom manager, flash latest cwm (as of right now it's 3.0.0.5)
Click to expand...
Click to collapse
Caution with the 3.0.0.5 latest CWM. I can't get into CWM recovery with that one; I had to downgrade back to 3.0.0.0. The phone just stalls at the Google screen on boot up with it.
Another person's reported the issue in another thread here. I emailed koush, but no response yet.
@nxt, you've tested 3.0.0.5 and it works as expected?
distortedloop said:
Caution with the 3.0.0.5 latest CWM. I can't get into CWM recovery with that one; I had to downgrade back to 3.0.0.0. The phone just stalls at the Google screen on boot up with it.
Another person's reported the issue in another thread here. I emailed koush, but no response yet.
@nxt, you've tested 3.0.0.5 and it works as expected?
Click to expand...
Click to collapse
Not nxt, but I haven't had any issues with 3.0.0.5. Flashing, restoring, or anything at all.
unremarked said:
Not nxt, but I haven't had any issues with 3.0.0.5. Flashing, restoring, or anything at all.
Click to expand...
Click to collapse
Interesting. I wonder what the quirk is on mine and the other guy's. I haven't tried flashing it from fastboot, but selecting reboot to recovery from within ROM Mgr will not load recovery, it just hangs. No issues with 3.0.0.0.
distortedloop said:
Interesting. I wonder what the quirk is on mine and the other guy's. I haven't tried flashing it from fastboot, but selecting reboot to recovery from within ROM Mgr will not load recovery, it just hangs. No issues with 3.0.0.0.
Click to expand...
Click to collapse
Works fine for me normally. I personally don't use rom Manager to do anything though. I manually reboot into recovery and do recovery stuff. I have not tried selecting reboot to recovery via ROM Manager. That might be the issue.
How does the fake flash with CWM via Rom Manger work? Is it like the flash that's used with the Vibrant, where it's just an update.zip that's temp installed when booting into recovery? Or is it something different?
aczarney said:
How does the fake flash with CWM via Rom Manger work? Is it like the flash that's used with the Vibrant, where it's just an update.zip that's temp installed when booting into recovery? Or is it something different?
Click to expand...
Click to collapse
Yes, it puts the update.zip onto the sdcard. If you get stuck in a bootloop, there is no way to recover other than doing a factory reset if you flash the recovery this way.
On the other hand, if you flash CWR through NVFlash, if you get into a bootloop, you can press Vol - and Power to access the recovery.
I tried using superboot to root my nexus s, but ended up with having a stuck google screen upon reboot.
Is there anyway I can recover my phone to the original state. I can get into the boot screen by pressing up volume and the power button and I have downloaded an original rom; however, I don't know how to upload this rom
into the phone.
I unlocked the bootloader, and have the android SDK installed. I do have a response when I use the command "fastboot devices"
Is there any possible way to save my phone? Please help, Thanks in advance
is there a recovery image saved under the recovery option?
Hey I'm having the exact same problem as the OP.
I don't have a recovery image saved in recovery, so I tried to flash the latest CWM recovery image through adb, but the device isn't found.
My phone was rooted, then upgraded to 2.3.4, then got 2.3.6 OTA, but lost root. Tried to root with Superboot and now my phone's stuck.
How can I get my phone to work again?
ri ch said:
Hey I'm having the exact same problem as the OP.
I don't have a recovery image saved in recovery, so I tried to flash the latest CWM recovery image through adb, but the device isn't found.
My phone was rooted, then upgraded to 2.3.4, then got 2.3.6 OTA, but lost root. Tried to root with Superboot and now my phone's stuck.
How can I get my phone to work again?
Click to expand...
Click to collapse
You have to flash CWM using fastboot, not adb.
fastboot flash recovery recovery.img
Once you have the custom recovery flashed you can flash superuser in CWM to get root back or just flash one of the custom ROMs that include superuser.
Yes, I did exactly that.
I really have no idea what I'm doing so I'm extremely grateful for people who do.
Thanks
I am in the same boat as these other chaps. After installing the 2.3.6 OTA update I tried to root with Superboot and now my Nexus S just sits on the Google screen with the open padlock.
I've tried installing CWM recovery, as well as the boot.recovery.img that comes with Superboot, and it seems to install successfully. After rebooting my phone still sits on the Google screen, however.
Am I doing something wrong here (I'd previously rooted with few problems)?
EDIT: I should mention that after flashing the .img I'm trying to boot into recovery - at this point it just sits on the Google screen.
EDIT 2: Never mind, I sorted it. I tried using a different recovery.img (from this thread) and I was then able to get into recovery and restore a backup.
Hey
I installed CWM and a new rom... ok that's not the problem...
First thing:
after installing the final version of the rom... and installing CWM it says it doesn't have a cwm recovery... interesting is that when I boot in recovery via power and volume up it enters in cwm recovery...
another question...
after restoring the original rom, via cwm it restores the original recovery too?
if I select factory reset via CWM recovery, will it put back to stock recovery?
main interest:
how to remove cwm flash recovery, and restore the original one?
Im kinda outta the know, but i see a few Rogers guys that cant root since the 1.94( i think) update but can unlock thru htcdev. Some of you guys are having trouble getting a flashed recovery to stick, so you cant get a rooted rom flashed. Well, there is a VERY simple solution for you guys.
You have your recovery.img in your adb/fastboot folder and your in your device bootloader.
fastboot flash recovery nameofrecovery.img
Ya ya, you tried that, But Wait!
Now
fastboot boot nameofrecovery.img
That WILL boot you into your custom recovery. Now u can nandroid and flash your rooted rom. Once booted up, go download goomanager and install recovery from there. That one WILL stick.
If you ever temporarily need to use the stock recovery, simply put the stockrecovery.img into your adb/fastboot folder and just do
fastboot boot stockrecovery.img
do whatever, after you reboot you will still have your custom recovery, since all you did was boot the stock recovery, not flash it. Also works vice versa
Added:
if you boot a cwm recovery at first steps, after installing recovery thru goomanager go make a new nandroid because twrp wont restore a cwm backup.
Hope this helps out a little:beer:
Could have used this info a few days ago
Bookmarking this.
Sent from my HTC One XL using xda premium