Database Develop

Boot Recovery without RooT?

So i have a friend that tried (and failed) to root his phone. Needless to say hes not very tech savy. He basically tried to install the cm-recovery-1.4 without root. As a result it erased his recovery and now is can't flash his phone.
Does anyone know of a way to install a stock, or otherwise, recovery image without having root?

Reapply the DREAIMG.nbh in bootloader.

That wont work. Becuase he tried to install the cm recovery without root it erased the bootloader.
No bootloader=no flash...Right?

Compliance said:
That wont work. Becuase he tried to install the cm recovery without root it erased the bootloader.
No bootloader=no flash...Right?
Click to expand...
Click to collapse
how exactly did he erase his spl and still manage to have a working phone.
bootloader=spl, bootloader is what you get when you power the phone on using camera and power. if you do not have a secondary processes loader then i can't see how the phone would do anything more then show the spalsh1 screen.
put the DREAIMG.nbh file on the root of sdcard and enter into bootloader (camera and power).

when we try to enter the bootloader(power+camera) it just boots to the grey screen and says no image found and goes directly to the screen with red, blue, green bars and it shows the spl number. (i believe thats the splash screen)
His phone does still work which i find odd as well.
Before this happened he did the following commands (after copying the *.img to the sdcard)
su
"su access denided"
cd /sdcard
flash_image recovery /sdcard/cm-recovery-1.4.img

can't you just flash the boot file from fastboot?

Compliance said:
when we try to enter the bootloader(power+camera) it just boots to the grey screen and says no image found and goes directly to the screen with red, blue, green bars and it shows the spl number. (i believe thats the splash screen)
His phone does still work which i find odd as well.
Before this happened he did the following commands (after copying the *.img to the sdcard)
su
"su access denided"
cd /sdcard
flash_image recovery /sdcard/cm-recovery-1.4.img
Click to expand...
Click to collapse
the recovery image was never flashed since he did not have sudo access. is the image called DREAIMG.nbh exactly, is the sdcard formatted fat32, is your copy of the DREAIMG.nbh for your region and not corrupted.
the splash screen is the logo that pops up whenever you boot your phone up, nothing is wrong with the spl or bootloader screen, it just can't read the DREAIMG.nbh file.
one last thing, why would he cd /sdcard the type /sdcard/cm-recovery-1.4.img that is redundant. the reason he should've cd'ed to /sdcard so is to not type /sdcard in the next command.

Im pretty sure the sdcard is fat32 and we did have DREAIMG.nbh copied to it. I will check the partition and try everything agian.

Compliance said:
Im pretty sure the sdcard is fat32 and we did have DREAIMG.nbh copied to it. I will check the partition and try everything agian.
Click to expand...
Click to collapse
you may need to re-download it if it doesn't work

Help with Recovery.img

I wanted to try Cyanogens new Rom when I bumped into snag on the first step.
I cant get in Recovery mode! I have done it befor to get root access but I dont know what happened. It always freezes at the Rogers Logo when I hold Home and push power.
I have very little knowledge of this stuff but Ive tried to install Cyans Pimped recovery.img but It keeps telling me cannot load recovery.img. I think I only tried through fastboot though, I have attempted to through adb shell but I'm not 100% how that works, so I assumed it failed.** Oh and I also Tried erasing my old Recovery Image, which was successful but didnt help anything
I have root access and I own a Canadian HTC Dream. I have Cupcake, Thanks for your help in advance ^^

Hi, it sounds like you erased the standard recovery image, but haven't sucsessfully flashed a new one, which is why the phone will have.
Try flashing it on your phone using the terminal. First grab "terminal emuator" or "Better Terminal".
Put the recovery image on the root of your SD card and name it recovery.img
Open terminal and type:
su <- when the prompt appears, choose always allow
flash_image recovery /sdcard/recovery.img
It's done when the cursor drops down to the next line. Turn the phone off and hopefully recovery will be working.

Hey thanks for the response but still having the same problem.
When I type su it always says Access Granted Courtesy of yada yada. Im assuming this isnt a problem. I flashed my recovery.img and it didnt give me a response. I guess it worked but yet, Still Freezes on Rogers Logo.
I found the Right Recovery.img for a Rogers Dream but now I cant seem to flash it into the Phone. When I type the cmd in Terminal It doesnt give me any errors. But when i go to Erase it in Fast boot it says the remote partition does not exist. Can anyone figure this one out? Im probably doing something small and stupid wrong but any help would be greatly appreciated.

Sounds like you have few different tutorials mixed up. You don't type cmd in terminal. cmd is Windows command to get into command prompt, from there you type your adb commands so if we assume that you placed your NEW recovery image in the root of you sd card and named it recovery.img you would type
From your computer
Window's key +r
cmd
adb shell
flash_image recovery /sdcard/recovery.img
reboot recovery
OR
From terminal
su
flash_image recovery /sdcard/recovery.img
and wait for # to appear, then type
reboot recovery and see what happens
There's a way to do it from fast boot screen as well, you can find a tut in developement section.
Good luck

Hey thanks, That does clear a few things up. I just ended up resetting my phone and it was a breeze from there. Thanks for your help.

not able to root g1!

i already searched all over the place
okay so i rooted my g1 last month and last night it started to get a little laggy. i found a new theme i wanted so i tried to reboot my phone. and it kept getting stuck on the G1 home page. it would start up fine. but i just couldnt get to the recovery page. i got impatient so i tried pressing the camera+power button and i guess i reseted my phone. so today i spent all day trying to re-root my phone and everytime i try to reboot it it comes up with that "exclamation" picture and im sure im doing everything right and im following all the steps. also i am now stuck on the 1.0 firmware will these update eventually?

Relax, you just deleted your custom recovery image. Just download CM 1.4 or Amon_Ra 1.5.2 onto your sd card then try to install the rom you want

i already tried the cyanogen one and it still gives me the same "exclamation" i havent tried to other one yet but i will give it a shot

memphisaccord said:
i already tried the cyanogen one and it still gives me the same "exclamation" i havent tried to other one yet but i will give it a shot
Click to expand...
Click to collapse
Does it boot up fine? Like past the g1 logo then the android logo?

How are you trying to put the custom recovery on ?
You using the terminal emulator ? ADB ? or via fastboot ?
I never had those issue's with my G1.
What you could try is to put the CM recovery 1.4 on and then flash the CyanogemMOD 4.0.4 as that is his most stable cupcake.
If that works try following CM's guide to upgrade to his latest versions.
Hope this helps.

Have you checked to make sure your sdcard is being mounted properly? In recovery, drop to console and execute the following:
# cd /sdcard
# ls
-- if it comes up blank, your card didn't mount. To fix it, execute the following:
# cd /
# mount /sdcard
# cd /sdcard
# s
-- assuming you now see your sdcard's contents, you can get back to recovery as follows:
# recovery

yeah everything boots up fine. i just got a notification to update to 1.6 today so im gonna try and root it again.

[Q] Stuck at Fastboot usb screen

I installed the new zen2.2 rom today and had a working clockwork recovery. Here is where I went stupid, I downloaded the kernel update but rather than running it via update.zip I flashed it using flash_image recovery via adb shell.
Now my phone comes up to fastboot usb and never goes any further, been waiting hours! I have tried booting into fastboot/hboot and it does nothing. I have booted to hboot before successfully but now nothing.
If I run adb devices it shows no devices. If I run fastboot devices it does show my device.
Whats next?

If you cant get into fastboot and you cant get into recovery then you m ight have bricked your phone. Did you try a hard reset?

How do you do a hard reset?
Here is a little more info. I believe it does actually get to fastboot usb as it says so on the top left of the screen and I can run fastboot commands but most commands say error. If I do fastboot devices it shows the device connected.
Little more info - when I try doing a back to basics RUU update it connects, shows the rom version, starts the update and then at about 88% every time, it goes right to a error [171] usb connection error. So its communicating but never finishes. Tried with the sprint RUU stock rom, another that was built by one of the devs in the Hero community and still both do the same.

I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.

ASimmons said:
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
Click to expand...
Click to collapse
Right, I also believe that if I could get a recovery back on the phone I would be good as gold! Here is the problem though. I have tried running "fastboot flash recovery [recovery.img]" but it gives me the below error. I have tried multiple key combination's to get into hboot but nothing works. If anyone has any other key combination's I could try please let me know!
Code:
D:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3720 KB)... FAILED (remote: not allow)
finished. total time: 0.001s

1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img

unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Yeah I think he knows now not to flash kernels... atleast I hope so. +1 for your post.

unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Click to expand...
Click to collapse
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.

casualonejp said:
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
Click to expand...
Click to collapse
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
edit: sorry i dont think fastboot will see the sdcard but try anyways.

ASimmons said:
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
Click to expand...
Click to collapse
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.

casualonejp said:
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
Click to expand...
Click to collapse
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.img
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.

ASimmons said:
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.fimg
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
Click to expand...
Click to collapse
Negative on the fastboot commands. Also did have a nandroid but on old sdcard which died. I read that I could use anothers nandroid backup but I am currently trying to find one to test.
Tried doing the RUU method with stock/custom roms and it gets as far as seeing the image but when I click on "ok" to start the recovery, it goes to "waiting on bootloader" and then at 88% it errors to a 171 error stating usb connection error.

I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.

ASimmons said:
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
Click to expand...
Click to collapse
Ya I have been researching non stop all yesterday evening and today so far all day. I just cant get it to do anything. I will keep researching though. Thanks

Did you fix this yet?

Anyone figure this out yet...I have the same issue and haven't been able to resolve it yet. Still with a brick at this point!

Hey guys,if your stuck at fastboot(As I just was tonight), try in your CMD(if running Windows) fastboot reboot-bootloader or fastboot reboot to reboot as normal,I'll try to keep you updated to get through all this. I am at a loss right now but searching for answers first before i go about asking.
Answer to MY problem(maybe not yours): OK,I have come to the conclusion here tonight that I had a soft brick. What I did was remove the battery,put the battery back in,restarted the phone normally,then I ran the HTC Sprint Hero MR 2.27.651.6 on my computer(essentially restoring back to unrooted factory settings). This worked for me. I am totally refreshed and happy that my phone is ok and all. Yes I may have to go back and re-root but this only take me bout 20 minutes most to root and re-flash a CyanMod7 Nightly Rom. Hope my info can help out somebody!

biggest trouble ever installing 2.2

so back when i had 1.5 on my hero i had no problem at all installing roms. so when i updated to 2.1 stock awhile back i tried to root it and install a rom on it with the command prompt and unevoked method. it got it rooted and when i got to the recovery menu i nanidroid backedup and wiped and installed it. it then got stuck on the htc boot screen so i tried different rom and still would hang on it. so i said screw it and stayed on stock. i then later used the unlock univeral to root it but i can not stand the stock rom it is so slow and lags so i tried the offiical htc update from .6 to .7 to see if it would be faster but once it downloaded and i pressed install it would yet again hang on the htc screen. i cant even make calls with out lagging. so i tried once more to install 2.2 on it with a recovery img. i download rom manger and put froyo on the sd card but it would yet again hang when i click install rom from sd card. what do i do?!!!!!
update: i tried doing it through the teminal but it say flash_recovery not found
so i tried to do it through rom manger and it did the back up and installed it through the recovery menu but once it was done and rebooted it yet again is stuck on the htc boot screen.

help please!

It might b the recovery ur using if your able to boot into any rom access terminal you can get it from the market try to flash a different recovery I recommend. Darchstar RA 1.6 once u download it place it on the root of ur SD card not in any folders / then open up terminal and type su once the # appears type flash_image recovery /sdcard/ recovery- name of recovery. img wen that's done type reboot recovery and you should boot into recovery then try and flash ur rom from there hope this helps good luck
Root-Hack-Mod-Always™

laie1472 said:
It might b the recovery ur using if your able to boot into any rom access terminal you can get it from the market try to flash a different recovery I recommend. Darchstar RA 1.6 once u download it place it on the root of ur SD card not in any folders / then open up terminal and type su once the # appears type flash_image recovery /sdcard/ recovery- name of recovery. img wen that's done type reboot recovery and you should boot into recovery then try and flash ur rom from there hope this helps good luck
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
ill try this when i get home tonite. thanks!

i tried doing it through the teminal but it say flash_recovery not found
so i tried to do it through rom manger and it did the back up and installed it through the recovery menu but once it was done and rebooted it yet again is stuck on the htc boot screen.

I recommend you boot into recovery - wipe your system / cache / dalvik cache and then flash the 2.2 rom of your choice -
if you were just flashing rom after rom without flashing then that could be a lot of your troubles -
also - you mentioned that the recovery file was not found on your sdcard - did you remember to unzip it first before attempting to flash it through terminal emulator? because it wont work otherwise ...
if you have extracted it to the root of your sdcard you shouldnt have any trouble
type
su
flash_image recovery /sdcard/nameofyourrecovery.img
reboot recovery
and you should be good to go - let me know how you do and we'll see if we can't help you further if needed
good luck!

cbwhat said:
i tried doing it through the teminal but it say flash_recovery not found
Click to expand...
Click to collapse
did you type:
su
flash_image recovery /sdcard/yourrecovery.img
or su
flash_recovery like your post shows - because you dont want to do it like that - just checking -

Vandelay007 said:
did you type:
su
flash_image recovery /sdcard/yourrecovery.img
or su
flash_recovery like your post shows - because you dont want to do it like that - just checking -
Click to expand...
Click to collapse
no it i type in
su
flash_image recovery /sdcard/recovery7.img
flash_image not found

cbwhat said:
no it i type in
su
flash_image recovery /sdcard/recovery7.img
flash_image not found
Click to expand...
Click to collapse
you said that you are doing this in a terminal window? (i am assuming that is on the phone) is your phone connected via usb to your computer? is the sdcard mounted by the computer? if it is unplug the usb and try again. if the computer has mounted the sdcard you can't access it from the phone.

i dont have it plugged in when i use the terminal on the phone

cbwhat said:
i dont have it plugged in when i use the terminal on the phone
Click to expand...
Click to collapse
ok just checking.... that was the only thing that i could think of that would stop you from reading the sdcard.

It may sound silly, bt when I do it I always make sure I account for case sensitivity...
Like flash_image recovery /sdcard/RA-Darchstar.img
Have you tried that?
Sent from my HERO200 using XDA App

yep make sure everything that has a capitals in it i capitalized in the terminal

this may sound silly as well.. sometimes when i use adb to push i mistype the location for example: adb push myfile.ext /adcard
everything goes fine until i go to find the file....
don't know though.

i still can't figure out how to install a custom rom.

Try backing up you sd and reformatting it on ur pc then just place the recovery img on your sd and nothing else then try to flash it good luck feel free to pm me I know how u feel man so if I can help I will good luck
Root-Hack-Mod-Always™