Database Develop

Restore Recovery Image?

I'm trying to install Cyanogen 4.1.99, but I think I screwed up. According to Fingerlickin I need to install cyanogen's recovery image. First, before I even tried this endeavor, I was running Cyanogen 4.11.1 with the EnochXTra theme. I flashed the recovery image as instructed but, when I rebooted (probably where I messed up) I didn't see the usual recovery mode menu, just some triangle with a "!" in it facing a phone/pda (and NO text). Now I can't flash update.zip files. (Yes I tried ALT+S).
Also Fingerlickin pointed me towards fastboot. I know it's the key right now, but I don't know where to go from here. I think I still have root because I have adb running and could "su" without any complaints.
(I decided to start a new thread because the one I was in had a different problem. Also I would search the forum but I don' know what to search for.)

Tactical Fart said:
I'm trying to install Cyanogen 4.1.99, but I think I screwed up. According to Fingerlickin I need to install cyanogen's recovery image. First, before I even tried this endeavor, I was running Cyanogen 4.11.1 with the EnochXTra theme. I flashed the recovery image as instructed but, when I rebooted (probably where I messed up) I didn't see the usual recovery mode menu, just some triangle with a "!" in it facing a phone/pda (and NO text). Now I can't flash update.zip files. (Yes I tried ALT+S).
Also Fingerlickin pointed me towards fastboot. I know it's the key right now, but I don't know where to go from here. I think I still have root because I have adb running and could "su" without any complaints.
(I decided to start a new thread because the one I was in had a different problem. Also I would search the forum but I don' know what to search for.)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=523558
instructions are in the OP. if you can boot into the rom, use
Code:
flash_image recovery /sdcard/cm-recovery-1.4.img
after putting the new recovery on your SD card
if that doesnt work
Code:
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
with fastboot
instructions to set up fastboot
http://forum.xda-developers.com/showthread.php?t=532719
you shouldnt need to flash the SPL if you have HardSPL or DangerSPL already. Just make sure you have the right drivers, and use the 1.6 SDK since its already out
If you have any others questions or need clarification, post here again

When I was in the rom, I used the terminal emulator, and when I tried to use "su" it said "uid 10031 not allowed to su". I tried "flash_image recovery /sdcard/cm-recovery-1.4.img" under adb and that flopped. Under fast boot I get "Error: cannot load 'cm-recovery-1.4.img'.
*Is nervous*

Tactical Fart said:
When I was in the rom, I used the terminal emulator, and when I tried to use "su" it said "uid 10031 not allowed to su". I tried "flash_image recovery /sdcard/cm-recovery-1.4.img" under adb and that flopped. Under fast boot I get "Error: cannot load 'cm-recovery-1.4.img'.
*Is nervous*
Click to expand...
Click to collapse
what spl do you have and is the recovery.img in the folder you are using fastboot from?

david1171 said:
what spl do you have and is the recovery.img in the folder you are using fastboot from?
Click to expand...
Click to collapse
He has the DangerSPL
and do as david said. the cm recovery image must be in the same folder as the fastboot executable

B-man007 said:
He has the DangerSPL
and do as david said. the cm recovery image must be in the same folder as the fastboot executable
Click to expand...
Click to collapse
reading fail, that's what little sleep for the past few days does
i have a android folder on my C:\ drive with fastboot.exe, adb.exe, and the AdbWinApi.dll so that is the folder i use whenever i need fastboot, i keep the adb.exe and AdbWinApi.dll file in my system32 folder so i can use adb easier.

david1171 said:
reading fail, that's what little sleep for the past few days does
i have a android folder on my C:\ drive with fastboot.exe, adb.exe, and the AdbWinApi.dll so that is the folder i use whenever i need fastboot, i keep the adb.exe and AdbWinApi.dll file in my system32 folder so i can use adb easier.
Click to expand...
Click to collapse
O dont worry he didnt mention it in this thread, it was in the other thread.
I do the same thing haha
@Technical Fart
Don't worry to much, your phone is still booting, its not bricked. Just take it slow and read everything carefully. since you got fastboot already set up, the hardest part is over.

Problem Fixed!!! I didn't know that you had to have the image in that same directory that you had the fastboot command in. Thank-you so much! It feels good to be in a cyanogen rom again.

Tactical Fart said:
Problem Fixed!!! I didn't know that you had to have the image in that same directory that you had the fastboot command in. Thank-you so much! It feels good to be in a cyanogen rom again.
Click to expand...
Click to collapse
NP
Can you please put [SOLVED] in the title?

B-man007 said:
NP
Can you please put [SOLVED] in the title?
Click to expand...
Click to collapse
How do I do that?

Tactical Fart said:
How do I do that?
Click to expand...
Click to collapse
select edit, go advanced, edit the title to include [SOLVED]

ADB working...not so much for fastboot
Hey guys,
I can't seem to get fastboot up and running. My adb is running fine but in all my noobishness I don't know how to get the recovery image running using adb. Is there anyway to do it or am I gonna have to figure out how to get the fastboot going?

to get fastboot going, you phone has to be in bootloader, in fastboot usb mode, and you need to be operating from a folder that has the fastboot.exe, adb.exe and the AdbWinApi.dll (for windows at least). then whatever you are wanting to transfer via fastboot needs to be in that folder as well.

I have all of those things in the tools file. Fastboot shows on my phone but when I type fastboot devices it shows nothing. Also, I tried doing the fastboot commands and it said it is waiting for the device.
When I type fastboot shell to get in to su it gives me the option list as if I just typed in fastboot.
Should I redo the whole adb install process?

Ok, tried going another method and downgrading or changing my rom...no go. Looks like it keeps aborting each installation. This is getting really lame really fast.
Edit: I fixed the problem with my fastboot finally. Apparently when I plugged up my phone in fastboot it recognized it as a mass storage device so I had to uninstall those drivers at startup and reinstall the adb drivers. I think I've spent 4 hours total on trying to fix what happened after this rom and sadly enjoyed the challenge.

simplyTravis said:
Ok, tried going another method and downgrading or changing my rom...no go. Looks like it keeps aborting each installation. This is getting really lame really fast.
Edit: I fixed the problem with my fastboot finally. Apparently when I plugged up my phone in fastboot it recognized it as a mass storage device so I had to uninstall those drivers at startup and reinstall the adb drivers. I think I've spent 4 hours total on trying to fix what happened after this rom and sadly enjoyed the challenge.
Click to expand...
Click to collapse
good to see you got the answer yourself
trust me, those long seemingly pointless hours troubleshooting pays off in the long run. you have a better understanding of how everything works

Hi - I have flash_image in the sdk tools folder but when I do:
ad push flash_image /system/bin is says cannot stat no such file or directory.
Please help!

Erris Bueller said:
Hi - I have flash_image in the sdk tools folder but when I do:
ad push flash_image /system/bin is says cannot stat no such file or directory.
Please help!
Click to expand...
Click to collapse
did you mount the /system directory?
from CMD:
adb shell
#mount -a
then try it.
afterwards then
#umount -a

[Q] Hero CM7 RC2 stable I think!

flashed CM7 RC2 I think month or so ago. Phone's been running fine slow but fine. Today Im texting the gf and look down and see blank wall paper. Reboot teh phone htc screen comes up vibrates then starts over. Cant do **** with this think besides stick down the front of my pants! Ive powered and booted to hboot, fastboot etc., cant get it to go into recovery any help would be greatly appreciated before I have a stroke!

FAIL. This should be in Q+A. Can you start ADB and access the device? Are you s-off? How did you root the phone? What have you tried? What recovery do you have? Can you read? Is the battery full? Did you search?

well since I rooted the phone about 2 [email protected]##ing years ago memory does not serve. S-off dont know does it do that when you flash the rom or install clockworkmod recovery or the several other steps that you follow when you flash the new ROM? If you have to flash it with the image then no that wasn't an option when I loaded this ROM.
ADB automatically starts when the system boots so I don't have to start it, yes its running no I cannot see the device. Battery was about 75% when the screen went blank.
Im going to ignore the can you read and should be in the Q&A comment el duce as this is the place where the experts play and the other 10000 questions about boot looping reside. Does anyone wanna help or just be an a...?

Questions don't belong in the Development section <---please click link and read....moved to general...

TMcGuire17 said:
well since I rooted the phone about 2 [email protected]##ing years ago memory does not serve. S-off dont know does it do that when you flash the rom or install clockworkmod recovery or the several other steps that you follow when you flash the new ROM? If you have to flash it with the image then no that wasn't an option when I loaded this ROM.
ADB automatically starts when the system boots so I don't have to start it, yes its running no I cannot see the device. Battery was about 75% when the screen went blank.
Im going to ignore the can you read and should be in the Q&A comment el duce as this is the place where the experts play and the other 10000 questions about boot looping reside. Does anyone wanna help or just be an ass?
Click to expand...
Click to collapse
I might be an a.., but I am helping, that's why I asked a bunch of questions. You are not s-off, you would know if you were. ADB is a program you use on your computer, not the phone. I asked because you can flash a recovery image using ADB even though the phone won't boot - so my new question here would be do you have ADB on your computer? You should have ADB if you rooted a long time ago, before there were 1-click root methods. I would recommend charging your phone, since many reboots would kill it. Wait til the charging light turns green. Once it's green boot into the bootloader, then access your phone via ADB and see if recognizes the device. If it does we can work from there. As to your BS about posting in dev because it felt better, that's lame as hell, I would have helped in q+a as well, but I would've been less of an ass because you were posting in the correct section. Anyway, charge it up, and reply if you know how to use ADB or not, then we can move on.
EDIT: I just reread your posts, did you say you can boot into your ROM, just not recovery? If so you can also flash a recovery image using terminal emulator. Let me know.

@TMcGuire17
Let’s take the aggression down about 5 notches and remember that when asking for help it is important to post in the correct section. The fact that you want your question answered quickly does not change the fact that this thread has no place in development. XDA is not tech support and while members can be very helpful you should not expect answers from anyone. When you have to search for the answer or figure out a solution…you are able to learn…understand…and then help others…and that is what XDA is about. Calling people names is never acceptable...I have edited your post. I am tempted to close this thread but I will leave it open in the hopes that you find your answer…but any more name calling or bickering and this thread is closed.
@il Duce
Thanks for helping...but next time leave out the "FAIL. This should be in Q+A" and just report the post...it is only going agitate the situation.
Thanks!
krook6023 (mod team)

krook6023 said:
@il Duce
Thanks for helping...but next time leave out the "FAIL. This should be in Q+A" and just report the post...it is only going agitate the situation.
Thanks!
krook6023 (mod team)
Click to expand...
Click to collapse
LOL ok my bad. I get angry. It's the Irish in me.

Well there you have it! Im as Irish as they come any good conversation between Irish is gonna start with either a beer or a fight. Now that intro's are over....I do have adb loaded need to update it. I'll be back later to check it out and see if I can access the device.
Peace

TMcGuire17 said:
Well there you have it! Im as Irish as they come any good conversation between Irish is gonna start with either a beer or a fight. Now that intro's are over....I do have adb loaded need to update it. I'll be back later to check it out and see if I can access the device.
Peace
Click to expand...
Click to collapse
Scotch-Irish actually, red beard to prove it, lol. You shouldn't need to update your adb If you have adb, and on windows, and it's old, try this: open command prompt from your start menu. type "cd C:\android-sdk-windows\tools" (or just copy paste that with no quotes) then type "adb devices" and if it says "random numers phone" like "2222555555 HTC recovery" or whatever, you're good. Report back.

I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running

TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
So now does it show your device?
sent from a series of tubes.

No it still wont execute the command

If it does, type "adb shell" enter "su" enter "flash_image recovery /sdcard/nameof yourrecovery.img"

Thanks il Duce. If I get adb running Ill try it and post back.

TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
Hey TMcGuire, If you updated to the latest SDK, the new path for ADB is no longer \Tools (unless you moved a bunch of files) Try c:\androidsdk\platform-tools

TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
This is not the correct path. Try typing "cd C:\androidsdk\tools" enter, then try "adb devices" OH YEAH and do you know if you had usb debugging on in the phone settings? You may have to run the RUU if you didnt. That can be done from fastboot, but try the other command first, then the flash command.
Edit, platform tools like posted above mine, sorry I dont have the new sdk.
sent from a series of tubes.

Thanks guys. Yes I have the new sdk and I did find the correct directory for the adb. I can run it now but still no device. Im not sure if I had debugging on or not I thought it did but.......ran adb shell device not found. How about a quick tut on fastboot!

so here is where Im at. fastboot lists my device. I've try to flash the rom from fastboot but no go. Tried to copy the ROM renamed update.zip to the sdcard via fastboot then I was gonna run update but it returned: sending '/sdcard' (72819 KB) FAILED (sounds familiar )(remote not allow)

TMcGuire17 said:
Thanks guys. Yes I have the new sdk and I did find the correct directory for the adb. I can run it now but still no device. Im not sure if I had debugging on or not I thought it did but.......ran adb shell device not found. How about a quick tut on fastboot!
Click to expand...
Click to collapse
look here:http://forum.xda-developers.com/showthread.php?t=958968
read the info, I think jasonmaloney put the zip you need near the end of the thread.

Read, tried failed. It wont push anything to the device. Always comes back as failed remote: not allow

[Q] Half bricked my Htc Hero.

Has anyone not been able to boot into recovery mode on their phone. When I go into ROM manager and try to change ROMS or something it just turns off?

Probably the obvious answer, but have you tried reflashing a recovery?

Yeah If that's when you press the home button, down on the volume and on button at the same time.

HTC_HERO!!! said:
Yeah If that's when you press the home button, down on the volume and on button at the same time.
Click to expand...
Click to collapse
no, reflashing, throught Rom Manager or ADB.
I personally think RM is the devil, it does all the stuff for you so when you run into this problem you crap your pants. Do you have adb and sdk goodies?

I am downloading them right now.

HTC_HERO!!! said:
I am downloading them right now.
Click to expand...
Click to collapse
cool, then once you get it all set up and made sure, it recognizes it, place the recovery.img of your choice to the root of your sd card,
then type in a command prompt
adb shell
# <--- (should get that)
flash_image recovery /sdcard/(file name).img

Ok I have downloaded and Installed Android SDK , Java RE, Java RE JDK. Is there anything else I would need to access the device through SDK?

HTC_HERO!!! said:
Ok I have downloaded and Installed Android SDK , Java RE, Java RE JDK. Is there anything else I would need to access the device through SDK?
Click to expand...
Click to collapse
lol well you only needed the sdk, those other javas are for developing and other such things. but no problem with being overly prepared. but thats all you need.
just follow these steps, http://wiki.cyanogenmod.com/index.php?title=Howto:_Install_the_Android_SDK

Hey coffehandle Thanks for the tips.
I read up on that link you posted, and entered some commands that were posted to and it said, that there's not enough space on the phone. Then after doing som3 research I found out that somehow I had deleted the recovery image binary . Installed that fixed all the issues.
Flashed RockSteady ROM its pretty good. Over clocked to 700mhz. ADW launcher. Right now I'm playing Angry Birds Rio. Thanks to all the people at Xda.
Sent from my HERO200 using XDA Premium App

[Q] Nexus one bricked :( and lost recovery mode

can you help me fix this problem
after wipe all data, cache and anotherthing wipe (it's name very hard to remember ).
I cant use recovery mode, my phone can open fastboot and bootloader, but can't open recovery mode (it's only show a android logo when i press "recovery")
please help me (

I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.

justflikwalk said:
I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.
Click to expand...
Click to collapse
can you show me more, i dont know adb commands, and push new recovery is "recovery clockwork" and "recovery RA". I tried apply them, but it's not work,may be i wrong in some thing, it's the first time i use android phone . throught usb, i have "fastboot usb"
please help me

http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide

but my phone cant connect with PC, atlthough i installed google usb driver.

i might be wrong but cant you just flash a original ruu, than root and reinstall recovery

#1)Go and download yourself a recovery.img file that is compatible with your device and put the image on the root of your SD card (that means on the main directory and not in a folder)
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
#3)Open up your terminal and type in
Code:
su
to gain root access. If you are root the next line should show the
Code:
# symbol
#4)At the next line type in
Code:
flash_image recovery /sdcard/name-of-recovery.img
you will need to replace the code that says name-of-recovery.img with the exact name of the file on your SD card.
#5)Hit enter, wait a few seconds and viola ! you have a recovery again.
Good luck man.

hxq88 said:
but my phone cant connect with PC, atlthough i installed google usb driver.
Click to expand...
Click to collapse
Try the driver from this thread.
It helped me set up my ADB for the N1
http://forum.xda-developers.com/showthread.php?t=613217

#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone

hxq88 said:
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone
Click to expand...
Click to collapse
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?

baseballfanz said:
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?
Click to expand...
Click to collapse
i typed ADB devices on command prompt, it'show
View attachment 763802
and it's my driver after update from your link
View attachment 763803
what is passimg method, is the way rename room.zip => PASSIMG.zip

You did have debugging turn on correct?
Not sure what else to suggest except the passimg method, worth a shot.
Sent from my Transformer TF101 using Tapatalk

And... if you try to install a stock rom? When starts the HBOOT automatically detect the rom and ask to install. One time you've installed the rom, root & install recovery
I think that work because, It happens to me 1 week ago.

[Q] i need help for my "bricked" phone.. i know it can be fix :-/

well while rooting my phone, installing the recovery and custom rom.. i made a slight (big) mistake towards the ending of root kit process by hasoon. When we are about to flash the custom rom, we're supposed to wipe everything so there wouldn't be any problems later on. We all know a fresh install always gives the best results. When i was wiping everything, i forgot to put Android Revolution HD on my sd so now i have recovery but i can't install a stock rom, custom rom, and i can't restore my phone. please someone help me.. i unfortunately have to go to work in 20 mins but when i get out of work i would greatly appreciate it if i had a few answers that can help me out with my situation. I don't care if its a hard process. this isn't my first phone i root so im not that noobie (at least i don't think so) so all im asking is to be pointed in the right direction and i would greatly appreciate that. Please and thanks for the help everyone. Hope we're all enjoying this amazing phone

Use the all-in-one toolkit in the dev forum to sideload the ROM from your PC. Rename the ROM something simple like arhd.zip on your PC to make it easier.
This helped me with a similar problem.
Sent from my HTC One using xda premium

thanks for getting me on the right track.. i honestly feel really close to having a phone again but now cwm is messing me up now. whenever i try to sideload.. i keep getting "failed to open driver control: No such file or directory" then it says "restarting adbd..." and then it just repeats with the no driver control. did this happen to u? :-/

Josh112191 said:
thanks for getting me on the right track.. i honestly feel really close to having a phone again but now cwm is messing me up now. whenever i try to sideload.. i keep getting "failed to open driver control: No such file or directory" then it says "restarting adbd..." and then it just repeats with the no driver control. did this happen to u? :-/
Click to expand...
Click to collapse
I have exactly the same problem. ADB sideload isn't working for me as the device isn't showing up in adb when booted into recovery... I've been doing this for years... I don't know how I could have done something so stupid :'(
EDIT:
I managed to fix this by installing CWM touch recovery and using LINUX to sideload the ROM .zip for installation. Good look sorting it out!

No didn't get anything like that. Maybe if you can get a USB OTG cable and try load the ROM that way through CWM from a USB or micro sd adapter?
I'm not sure if this would work as I haven't tried it - just a suggestion to try.
Sent from my HTC One using xda premium

Sideload from CWM Recovery
Just went through the whole boot loop due to Aroma freezes at the beginning of the installation, but CWM Recovery is still accessible so I went the ADB Sideload method and push the file to be installed because I didn't have any backup on the internal memory.
Just a couple of guides from the guys at XDA that got me back:
make sure you have the most up to date ADB Tools
From your phone go to Recovery>install zip from sideload
From CMD prompt, check that adb can see your device by 'adb devices' command, it should show your device number with sideload next to it.
If it doesn't see it, try 'adb kill-server' and then 'adb start-server'
Then 'adb sideload custom.zip' (custom= name of ROM zip file)
You should see the percentage completion then it will start the installation on your phone.
I am also newbie at this, was panicking and looked around here having this bricked phone next to me for 24hrs, but I asked around and they got me back in.
Good luck.

boot to recovery and push rom to phone....
'adb push /path/to/ROM/on/your/computer /path/on/device' (without quotes)

xdracco said:
boot to recovery and push rom to phone....
'adb push /path/to/ROM/on/your/computer /path/on/device' (without quotes)
Click to expand...
Click to collapse
I'd be interested to see an example of the command for future reference??
For example, the ROM is saved in C:\fastboot
Thanks.

xdracco said:
boot to recovery and push rom to phone....
'adb push /path/to/ROM/on/your/computer /path/on/device' (without quotes)
Click to expand...
Click to collapse
This is what I was going to suggest.
Sent from my HTC One using xda app-developers app

redbull123 said:
I'd be interested to see an example of the command for future reference??
For example, the ROM is saved in C:\fastboot
Thanks.
Click to expand...
Click to collapse
Code:
adb push C:\fastboot\My_Rom.zip /sdcard/Download/
Try to have no spaces in the file name. linux based systems hate that.
Then when you boot into recovery, head over to:
install zip from sdcard -> choose zip from sdcard -> Download/
You'll find your ROM there.
HTH

What model do u have?
Sent from my HTC One using xda app-developers app