Database Users

Using flash_image to upgrade recovery partition failed... now what?

Hello folks,
First time poster here, first time I haven't been able to find a fix already posted...
Anyway, I wanted to try out the new Cyanogen mod after not having tried any new ROMs in a long time. Got 5.0.7 installed and running no problem. Then I noticed on the Cyanogen Mod site that there was also a Cyanogen recovery image. "Might as well have everything from the same source," I thought. I got the file, put it on the SD card, and used the terminal on the phone to execute "flash_image recovery /sdcard/cm-recovery-1.4.img," then tried rebooting into recovery mode. No good. Just get hung up at the "myTouch 3g" screen. At this point, I thought I was well and screwed, but fortunately I'm still able to boot normally.
Tried reflashing the same image, then other recovery partition images. No dice. Where do I go from here? I'm used to fixing stuff I've screwed up through the recovery partition, not the other way around!
I appreciate any help or advice!
Sincerely,
Tom

hey tom,
this will fix you up:
install "rom manager" from the market
flash his recovery image (theres in option for that)
then look for the option that lets you flash Amon Ra 1.7.0
let it load, power off & then check.
trust me this is bound to fix your problem.

[A] Bootloop after flashing a ROM via 3.0.0.5 Recovery image.

What you did .. .. ..
Okay so you've rooted your newly bought MyTouch4G, and you've made sure that s=off and you've flashed Clockwork ROM manager's recovery image that you got from the market. That is all the correct order. But when you flashed a ROM you got stuck in a bootloop.
Am i screwed???
Don't worry you are just in a "soft brick mode", or "limp mode" if you will.
What happened? Why is it doing this?
The Image that you downloaded and installed 3.0.0.5 is for 2.3 (Gingerbread) based ROMs only. [n3rd note] these are ext4 style ROMS. They act and store information differently than 2.2 which are Ext3 ROMs[/n3rd note].
This could also be caused by trying to flash a 2.3 using a older 2.x.x.x version of the Recovery Image. Those will only support the Ext3 style ROMs, which are FroYo (2.2) based ROM.
Okay what do i need to do to fix it, there are two methods.
This is Method one it's the older version.
You must use this method if you do not have the engineering screen
If you are using the 3.0.0.5 Recovery image
To fix your problem you need to flash any 2.3 based ROM, for time sake i will recommend Cyanogen(mod). Link to Cyanogen(mod)'s CM7RC4. While you are there you need to also store the G/Apps.
If you are using the 2.x.x.x Recovery Image
To fix your problem you need to flash any 2.2 based ROM, for time sake i will recommend RoyalGlacier Thread can be found here
- Question: How do i find out what Recovery image i am using
- Answer: Boot the phone into the recovery mode. We'll touch on that in a little bit
Now when you download both of those files you also need to store them to SDCard.
NOTE: If you are using 2.x.x.x and going to flash RoyalGlacier you will not need the g/apps. They have included this in their ROM, and MAKE sure to follow their specific directions for installing the ROM.
- Question: Now how in the world i am going to do that since my phone is in bootloop.
Answer:
Two ways one can do that
1) use a SDcard reader and just plug the card into a main USB port.
2) Mount the SDCard in the phone via the Recovery Image. *** i'd recommend this method since you are going to need to be in recovery anyway ***
Pull the battery from the phone an put it back in, then put the back on the phone. turn the phone on holding the power button along with the volume down rocker button. That will boot the phone into the HBoot (Engineering) Screen. From there you will see an option that says "recovery" [this is what i mentioned earlier, about the different versions] use the volume rocker to select it, then tap the power button to select it. The phone will reboot into what is called the recovery image. From there you will select "mount" then USB. That will mount the SDCard to the Computer.
If you are using the 3.0.0.5 Recovery image
Once you have move Cyanogen(mod) and the g/apps to the SD card unmount the SDCard.
Then navigate to "wipe data/factory reset" you will want to wipe the phone. That will format everything to a fashion that can be written over w/o problems.
Then navigate to "install .zip from sdcard" > " choose .zip " > then flash the main Cyanogen(mod) ROM. Then do the same but flash the g/apps that you downloaded.
Once those are done you can re-boot the phone. That will boot you into cyanogen.
If you are using the 2.x.x.x Recovery image
Please use the link i supplied above to get that ROM up and running once it is done, according to their instructions come back here.
Now i understand that may or may not want Cyanogen nor RoyalGlacier on your phone. Well take care of that
What can i do to prevent this from Happening again?
Once you are up and running (make sure to log into your Google Account) go to the market and download Clockwork ROM manager again, and re-flash the recovery image.
Once you are done with that i HIGHLY suggest upgrading to the newest 3.0.0.6 Recovery image. You can do that one of two ways.
one way is to flash True_Blues method for installing 3.0.0.6 recovery image. Use this thread..
This is the way that i would personally recommend.
The second way is download the 3.0.0.6 recovery image, which i've attached and flash it via the ADB commands. If you want to do it this way you do not need to download Clockwork Rom Manager, you can "just flash it". If you need help with that, if you are using Windows or Mac, see my signature for True_Blue's method on EZ ADB. If you are using Unbutu 10.10 use this This Method to get ADB running. This is the method i used to ADB running on my Linux NetBook.
Download the file that i've attached and store just the recovery image from the .zip to the SDCard, from the ADB commands type
adb shell
su
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
More information on this process can be found here
That will flash the newest recovery image to your phone
Once you have installed the 3.0.0.6 ROM Manager you can wipe and flash ANY MyTouch4G ROM that you want. It will handle both 2.2 (ext3) and 2.3 (ext4) ROM formats.
This is the New Method - Which is a little easier.
AND YOU MUST HAVE THE ENGINEERING HBOOT
Thanks to TeeJay for inspiring this.
I am going to assume that since you have the Engineering Screen you are more familiar with what you are doing so i'll be more to the point with this walk-through.
you will need to have ADB up and running for this method.
1) Download the attached file and store just the .img to your folder from which you preform all of your ADB commands
2) plug the phone into the computer
3) boot the phone into HBoot
4) from the ADB commands change the drive to the folder where you stored the recovery image.
5) type these commands
Code:
fastboot flash recovery recovery.img
the screen should say something to the degree of
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
6) then select "bootloader"
7) navigate to "reboot recovery"
8) flash your ROM of choice.
9) enjoy your ROM of choice.
Please feel free to use this in your signature or link people back to. If you feel i made an error in this post please PM and i'll edit it accordingly.
If this thread has helped you solve your problem please hit the "thanks" button.
THE RECOVERY IMAGE HAS BEEN UPDATED TO THE NEWEST ONE.

good summary. originally when i flashed cm7 I had to search a bit to come up with what you said above. one addition, CWM lets you mount sd storage to usb so you can copy files to sdcard (say the recovery image). then update CWM 3.0.0.6 with ADB.

leo221 said:
good summary. originally when i flashed cm7 I had to search a bit to come up with what you said above. one addition, CWM lets you mount sd storage to usb so you can copy files to sdcard (say the recovery image). then update CWM 3.0.0.6 with ADB.
Click to expand...
Click to collapse
Added that method as well.

May want to mention that the opposite could be true as well > same boot loop but from flashing 2.3 rom with recovery 2.5.1.2

Thank you for this!! Exactly what I needed...!

austengeist said:
Thank you for this!! Exactly what I needed...!
Click to expand...
Click to collapse
Glad it helped, just make sure to hit the "Thanks" button in the first post.

dang man you're the Q&A champ, every time i'm on this you're answering questions.
well this worked like a charm, idk why people on xda always make things more complicated than it has to be.

option94 said:
May want to mention that the opposite could be true as well > same boot loop but from flashing 2.3 rom with recovery 2.5.1.2
Click to expand...
Click to collapse
Added.
aalsmadi1 said:
dang man you're the Q&A champ, every time i'm on this you're answering questions.
well this worked like a charm, idk why people on xda always make things more complicated than it has to be.
Click to expand...
Click to collapse
Well i work in the Imported Automotive parts. My job requires me to basically sit around and answer the phone when it rings. We have our own "call center" room. I just pick up the phone and answer question and sell parts. Like right now i'm working on a engine rebuild kit for a 1975 2Ton Mercedes Bens..... so i get some free time from time to time, and XDA is one of a few sites they allow me to visit.... BGR/ Android and Me, Android Central are the others....
I can see why some people blow up, spend +$200.00 on a phone then turn around and blow through something w/o taking the time to read something and then you get stuck in a bootloop.... i can see why people go bonkers. But slowing down and reading would solve alot of problems. Heck i've got 3 great threads in my signature that would solve alot question that one could have with a new device.

fixed my problem

Thread stuck.

Great guide!

Same issue, except i flashed 3.0.0.6 beforehand to prevent any problems. Iced Glacier flashed okay, I just didn't care for it much. Ive wiped all the necessary parts prior to flashing as I would before flashing any roms. Ive managed to retrieve and restore a previous back (I can haz backups) so Im not stuck. I would like to be in the cool kids cyanogen club. Any ideas?

DHSdrone said:
Same issue, except i flashed 3.0.0.6 beforehand to prevent any problems. Iced Glacier flashed okay, I just didn't care for it much. Ive wiped all the necessary parts prior to flashing as I would before flashing any roms. Ive managed to retrieve and restore a previous back (I can haz backups) so Im not stuck. I would like to be in the cool kids cyanogen club. Any ideas?
Click to expand...
Click to collapse
Meaning you want to run Cyanogen(mod)? Well jump over to their site and download the ROM of your picking; Nightlies are alpha builds, and the RC's are beta builds. I've ran both and both are extremely stable. I have links supplied in the first post. and directions for that matter. just make sure to do a nandroid backup before wiping and flashing.

Thanks ....Saved ME LIFE

Posting so I can see the "thanks" button. Doubley thanks you saved my bacon....err phone!! Hmmmm bacon!

Ok I am having one Problem PLEASE HELP!!!
When I click "wipe data/factory reset" it just shows the clockwork icon (hat and arrow) and nothing happens.
In fact, this happens with all of the options in the clockwork recovery.
I am running clockwork 3.0.0.5. I had CM7 and I did something stupid, tried flashing another ROM via rom manager....I did back up everything though.
Please tell me I am not bricked!!!

b0rnsusp3ct said:
Ok I am having one Problem PLEASE HELP!!!
When I click "wipe data/factory reset" it just shows the clockwork icon (hat and arrow) and nothing happens.
In fact, this happens with all of the options in the clockwork recovery.
I am running clockwork 3.0.0.5. I had CM7 and I did something stupid, tried flashing another ROM via rom manager....I did back up everything though.
Please tell me I am not bricked!!!
Click to expand...
Click to collapse
Pull the battery. Hold vol down power on them restore cm7. Then flash cwm 3.0.0.6.
Sent from my Inspire 4G using XDA Premium App

b0rnsusp3ct said:
Ok I am having one Problem PLEASE HELP!!!
When I click "wipe data/factory reset" it just shows the clockwork icon (hat and arrow) and nothing happens.
In fact, this happens with all of the options in the clockwork recovery.
I am running clockwork 3.0.0.5. I had CM7 and I did something stupid, tried flashing another ROM via rom manager....I did back up everything though.
Please tell me I am not bricked!!!
Click to expand...
Click to collapse
What button are you pressing to select the option? you should just use the trackpad.

Loll...wow, I am such a noob i def. shouldn't be rooting or anything.
Thanks so much!

b0rnsusp3ct said:
Loll...wow, I am such a noob i def. shouldn't be rooting or anything.
Thanks so much!
Click to expand...
Click to collapse
Why do you say that?

[INFO/DISCUSSION] ClockWorkMod Recovery 5.5.0.4 Tf101

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.

Original transformer bricked

I updated the CMW recovery via ROM manager and now my tablet is bricked. I can only get into the recovery but it does not recognize my external sdcard and this is where my rom are. so there's no way to flash the rom.
Btw, the serial# start with B50.
Does anybody know i can resolve this?
Thanks
:crying:

pcurator said:
I updated the CMW recovery via ROM manager and now my tablet is bricked. I can only get into the recovery but it does not recognize my external sdcard and this is where my rom are. so there's no way to flash the rom.
Btw, the serial# start with B50.
Does anybody know i can resolve this?
Thanks
:crying:
Click to expand...
Click to collapse
'No way to flash the rom' is not right. Seeing you have a B50, you should be able to do it with the nvflash method. Search this forum for the methods, there are a lot of threads with instructions.
Good luck.

pcurator said:
I updated the CMW recovery via ROM manager and now my tablet is bricked
Click to expand...
Click to collapse
NEVER EVER use ROM manger on the TF101, it is a well-known source of bricks.
Bad news: you lost all your data and there's no way around it.
Good news: you can use nvflash/wheelie to reflash the device.

pcurator said:
I updated the CMW recovery via ROM manager and now my tablet is bricked. I can only get into the recovery but it does not recognize my external sdcard and this is where my rom are. so there's no way to flash the rom.
Btw, the serial# start with B50.
Does anybody know i can resolve this?
Thanks
:crying:
Click to expand...
Click to collapse
You're not bricked, just needed to do a little searching.
Cold boot:
Hold Vol Down plus Power button
Wait till you see the options of Cold boot Linux or Wipe data
Choose Cold boot Linux and it should boot into the OS (Unless you wiped the system)
Use PERI to fix your recovery
http://forum.xda-developers.com/showthread.php?p=26737790
If that don't work there's a thread that show you how to fix it via terminal our adb shell.
http://forum.xda-developers.com/showthread.php?t=1530337&
Of course NVFlash work too.

A500 Bootloop. Tried to flash TegraOwners Rom, now no rom works

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