biggest trouble ever installing 2.2 - Hero CDMA Q&A, Help & Troubleshooting

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™

Related

How to install Cyanogen 1.3 recovery??

Can someone please help me install this? I've tried the terminal way and the update.zip way and I still see JF 1.43 recovery utility.
You sure you did it correctly? Try again make sure you redownload the image file. It should be roughly 4000kb.
Su
Flash_image recovery /sdcard/cm-recovery-1.3.1.img
domiiniicano said:
Can someone please help me install this? I've tried the terminal way and the update.zip way and I still see JF 1.43 recovery utility.
Click to expand...
Click to collapse
first obviously make sure you have root, do this buy going into Terminal Emulator and typing su then press enter you should see this (#) and make sure the .img file that you downloaded (Cyanogen's Recovery 1.3.1) is in the root of your SD card, this is where all your folders are like (DCIM) (make sure you don't rename the .img file) once all that is verified then go back to Terminal Emulator and type su again and when you get the (#) symbol type
flash_image recovery /sdcard/cm-recovery-1.3.1.img exactly how you see it because it is case sensitive then press enter, now turn off or reboot back in to Recovery and verify that it worked.

No recovery screen after cyanogen recovery 1.4

hi i tried searching for this but couldnt really find anything on it. i tried updating to the cyanogen recovery.img 1.4 using terminal as the guide said here http://forum.xda-developers.com/showthread.php?t=533731, however now whenever i boot into recovery, the bootloader screen comes up instead. i have tried reflashing the recovery numerous times but the problem still persists. am i doing something wrong? any help would be great. thanks in advance
also i am rooted currently running JF 1.5 rom with latest radio and hard spl.
Put the recovery image on the SD card yourself. Get the file from here http://forum.xda-developers.com/showthread.php?t=523558
i have also tried that. once i placed the file on the sd card, i opened up terminal and typed in the command:
flash_image recovery /sdcard/cm-recovery-1.4.img
after i pressed enter nothing happend on screen, so i turned off the phone and tried to boot into recover, but the bootloader screen still appears. am i typing in the wrong command or something?
Do it again and this time wait for the # to appear again. Then type reboot and hold home button while it's booting. Should take you to Cyan's awesome recovery screen
Good luck
... Have you tried flashing it from fastboot like cyanogen recommended if you ran into any issues?
djosiah said:
i have also tried that. once i placed the file on the sd card, i opened up terminal and typed in the command:
flash_image recovery /sdcard/cm-recovery-1.4.img
after i pressed enter nothing happend on screen, so i turned off the phone and tried to boot into recover, but the bootloader screen still appears. am i typing in the wrong command or something?
Click to expand...
Click to collapse
After you open the terminal, did you type "su"?
billquinn1 said:
After you open the terminal, did you type "su"?
Click to expand...
Click to collapse
yeah i did type in su. i have been away for a few days so i ma going to try the suggestions mentioned. and no i havent tried doing it using fastboot as i havent got adb set up yet. i will also try that later. thanks for the suggestions.
I have the same problem. When holding power+home, it flashes t-mobile G1, then the screen disintegrates and it reboots a couple times, finally stopping on a blank black screen.
I have no problem booting straight into the O.S., I've just lost my recovery.
I've done this before and it worked, but I recently had a catastrophic failure and had to start from scratch.
If all else fails or you don't fell like using adb, should be fine if you downgrade and re-root, etc.... unless there is something else messing up your recovery partition.
Put the recovery.img file on the root of your sdcard
Then try:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system
cat /sdcard/recovery.img > recovery.img
flash_image recovery recovery.img
I've gone from JF 1.5ADP to Modaco using the cyanogen 1.4 recovery without any problems.
when you flash using terminal, you need to wait till you get the # back, and then restart the phone
which recovery image were you previously using as I was using JF 1.43 recovery
djosiah said:
hi i tried searching for this but couldnt really find anything on it. i tried updating to the cyanogen recovery.img 1.4 using terminal as the guide said here http://forum.xda-developers.com/showthread.php?t=533731, however now whenever i boot into recovery, the bootloader screen comes up instead. i have tried reflashing the recovery numerous times but the problem still persists. am i doing something wrong? any help would be great. thanks in advance
also i am rooted currently running JF 1.5 rom with latest radio and hard spl.
Click to expand...
Click to collapse
Hi djosiah
did you read this post ?
http://forum.xda-developers.com/showthread.php?p=4569666#post4569666
(Please substitude by the file name "update-cm-4.0.4-signed.zip" by "cm-recovery-1.4.img" in my post - sorry, I was misaken as to the file name ...!!)
My problem was a corrupted cm-recovery-1.4.img (a few thousand bytes of the MBs were missing ...!) A new downloaded cm-recovery-1.4.img (from another URL) solved the problem finally. The rest was cream - totally happy now.
Good luck!
My problem was solved.
Unroot the phone
reformat sd card using gparted live cd to fat32
redo root
flash new radio
flash new spl
flash cyanogen rom
flash cyanogen recovery
tada

Help! my sprint hero 200 keeping restart

my hero has keeping restart .
the list what i do :
1 . update 2.1rom
2.SPC --unlock
3.write the esn and imsi and a-key
4.then my phone keeping restart
5.use ruu 1.56 recovery,has the same result
what could i do ?
can you boot into recovery!?
before i use ruu1.56,the recovery is good ,now ,it doesn't work again.
when i get into root screen ,select the recovery ,then ,the phone display the Triangle warning sign
galaxyzhang said:
before i use ruu1.56,the recovery is good ,now ,it doesn't work again.
when i get into root screen ,select the recovery ,then ,the phone display the Triangle warning sign
Click to expand...
Click to collapse
reflash your recovery image via adb, and nandroid back!!
somebody told me try the ruu1.29,to Resume Original state,it seems 2.1 rom can lower to 1.56,but can't to 1.29 .
another details :my phone restart ,first display:"no service",if the Problem is the signal module, or it was bad ESN? Lead to restart the phone non-stop?
galaxyzhang said:
somebody told me try the ruu1.29,to Resume Original state,it seems 2.1 rom can lower to 1.56,but can't to 1.29 .
another details :my phone restart ,first display:"no service",if the Problem is the signal module, or it was bad ESN? Lead to restart the phone non-stop?
Click to expand...
Click to collapse
sorry thats too deep for me. am i understanding you correctly; you used the 2.1 RUU?
try and boot from your sd card lmao!
seriously, can anyone find that thread? that would be a great read.
mountaindont said:
reflash your recovery image via adb, and nandroid back!!
Click to expand...
Click to collapse
how ? is there some guide ?
thank you !
galaxyzhang said:
how ? is there some guide ?
thank you !
Click to expand...
Click to collapse
um yes. in the guides thread.
sticky wiki!
LOL! Is this **** for real?
This is how to do it. Download a recovery image (Amon_Ra, ClockworkMod, GodSpeed), name it "recovery.img" and put it on the root of your SD card. Then, run these commands (i'm assuming you have ADB).
Code:
adb shell
su
cd /sdcard
flash_image recovery recovery.img
reboot recovery
It will be slow in the flash_image command, don't freak.
HeroMeng said:
This is how to do it. Download a recovery image (Amon_Ra, ClockworkMod, GodSpeed), name it "recovery.img" and put it on the root of your SD card. Then, run these commands (i'm assuming you have ADB).
Code:
adb shell
su
cd /sdcard
flash_image recovery recovery.img
reboot recovery
It will be slow in the flash_image command, don't freak.
Click to expand...
Click to collapse
Thank you very much!
I did what you told me ,but when i type the last cmd ,
the result :flash_image :not found
what the problem?
did you have the file in your sd card?
macvalentine said:
did you have the file in your sd card?
Click to expand...
Click to collapse
yes.i copy the recovery.img to the sdcard
maybe i used <RUU_Hero_C_Sprint_1.56.651.2_signed_release> damaged the recovery mod.

[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!

flashing recovery, after root access, help please.

i have two recovery images on my sdcard, and neither of them are flashing, i rooted using z4root. that was the only method i could find to root my phone after the weeklong search. ive recently had to re root because i got a refurb. either way they stuck me with .7 i updated to .2 because i could not root .7 got it rooted , yay, but now i am having the hardest time flasing a recovery image. i tried using rom manager to get clockworks but the download from the market would not download, so i put it on my sdcard and did it myself. so i have rom manager now, but it keeps telling me i need reliable connection, im on wifi and i have five bars. ive had no luck.
i pushed both the recovery images i have on my sd card, and i tried to flash them but it keeps telling me they cant find them.
kyle-markss-macbook:tools kylemarks$ ./adb shell
$ su
# flash_image recovery /sdcard/recovery-RA-heroc-v1.5.2.img
flash_image: not found
# flash_image recovery /sdcard/recovery.img
flash_image: not found
# kyle-markss-macbook:tools kylemarks$
is what im getting in my terminal. i need help. please.
i have two recovery images on my sdcard, and neither of them are flashing, i rooted using z4root. that was the only method i could find to root my phone after the weeklong search. ive recently had to re root because i got a refurb. either way they stuck me with .7 i updated to .2 because i could not root .7 got it rooted , yay, but now i am having the hardest time flasing a recovery image. i tried using rom manager to get clockworks but the download from the market would not download, so i put it on my sdcard and did it myself. so i have rom manager now, but it keeps telling me i need reliable connection, im on wifi and i have five bars. ive had no luck.
i pushed both the recovery images i have on my sd card, and i tried to flash them but it keeps telling me they cant find them.
kyle-markss-macbook:tools kylemarks$ ./adb shell
$ su
# flash_image recovery /sdcard/recovery-RA-heroc-v1.5.2.img
flash_image: not found
# flash_image recovery /sdcard/recovery.img
flash_image: not found
# kyle-markss-macbook:tools kylemarks$
is what im getting in my terminal. i need help. please.
Click to expand...
Click to collapse
If you haven't already checked it. Try making sure the recovery is named .img & not. img.img on your sd card
Edit also make sure the recovery img is not in any folder. As in just on your sd/card
Yea its me again. With the
Modified Hero
Just get rom manager from the market and install clockwork recovery from the app. It sounds like you dont have the binary for flash_image.
sent from a series of tubes.
il Duce said:
Just get rom manager from the market and install clockwork recovery from the app. It sounds like you dont have the binary for flash_image.
sent from a series of tubes.
Click to expand...
Click to collapse
i installed the rom manager from apk. the market wouldn't download it for some reason. but it wont let me install the recovery, it says i dont have a reliable signal, which i do.
laie1472 said:
If you haven't already checked it. Try making sure the recovery is named .img & not. img.img on your sd card
Edit also make sure the recovery img is not in any folder. As in just on your sd/card
Yea its me again. With the
Modified Hero
Click to expand...
Click to collapse
check, check and check.
i have two on the root of my sdcard named, recovery.img and the other one is recovery-RA-heroc-v1.5.2.img they are both the same file, i just used recovery.img as instructed in the old how to root by regaw, back when i knew what i was doing, ahaha.
Sent you a pm
Sent from my HTC Hero CDMA using XDA App
just a wild guess, but how about
flash_image recovery /mnt/sdcard/recovery-RA-heroc-v1.5.2.img
?

Categories

Resources