Hi,
last year, I rooted my Hero, then I bought a Desire. But now my girlfriend would like to use my Hero. So I took my rooted Hero and tried to reflash a new rom, but on one way or another, it keeps failing.
I tried to re-install a new recovery, but accidentaly chose CDMA-hero instead of GSM-hero. Now I can't get into a recovery. When I try to boot the phone, while holding Home button, I only get the HERO-logo... I can get into fastboot though.
I remember I just installed a rooted stock rom: HTC Generic 2.73.405.66. Now I'm reading that this rom results in troubles installing a recovery. I tried EVERYTHING:
- flashrec: can't backup my image, can't flash a recovery (button greyed out)
- tried to downgrade to 2.73.405.5 as suggested on the homepage of flashrec
- tried the guide on modaco: http://android.modaco.com/content/h...ng-the-patched-recovery-image-on-your-device/
My situation is now: Hero is rooted, but my Hero doesn't have a recovery image...and I really need one to flash a custom rom on it...
Can anyone help me please?
Greetings,
Why not try this :
http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1
Code:
Copy recovery-RA-hero-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
Change to this on my gsm hero today and easy enough to do via adb.
If above doesn't work. Just downgrade to 2.73.405.5 - use the goldcard method in my guide in my sig. Simple.
Steven_belfast said:
Greetings,
Why not try this :
http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1
Code:
Copy recovery-RA-hero-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
Change to this on my gsm hero today and easy enough to do via adb.
Click to expand...
Click to collapse
euhm, the problem is, that I even can't get into recovery since it crashes and keeps showing the HERO-logo... and I already said that I can't downgrade, the process returns an error 'wrong client id' or something... I don't need the goldcard since my Hero is unbranded.
Related
I've been reading up about what to do after I tried to "factory reset" my phone and then was stuck at the htc start up soon, which kept looping.
I've been trying to load recovery.img during fastboot (back+power) and then to apply update.zip during recovery (home+power).
However, the problem is that during fastboot, the device isn't recognized (when I go to adb devices on command prompt, no device is listed). I know that my drivers are good bc the device is found when I start up in the recovery mode. I tried to skip the part where I load recovery.img (since when I try to do that, it tells me that it can't be loaded), and to go straight to apply update.zip, but then the phone tells me that update.zip is either bad or can't be mounted.
I have a Rogers Magic (32A). I am a complete newbie, so any help would be greatly appreciated. I should also say that before I tried to do the factor reset, the phone was on the hero rom loaded by a previous user.
try this:
boot in recovery:
fastboot boot recovery.img
then, push update.zip on your sd card ( need a good rom in the tools folder on your computer)
adb shell mount /sdcard
adb push update.zip /sdcard
and apply update.zip with the recovery menu.
thanks for your reply, but it didn't work:
first, it said "cannot load recovery.img"
and then when I tried to mount, it said "mount: mounting dev/block/mmcblk0p1 on /sdcard failed: Device or resource busy"
replace recovery to correct path to your recovery image. (your phone mut be in fastboot mode power with back button pressed)
ex:
fastboot boot c:\sdk\tools\recovery-RAv1.2.1G.img
then your phone must boot on recovery and you could push update.zip
thanks so much. I figued it out - just a simple problem of the update.zip file being corrupt.
pato17 said:
thanks so much. I figued it out - just a simple problem of the update.zip file being corrupt.
Click to expand...
Click to collapse
i am having the same issues.
any help?
beastmods said:
i am having the same issues.
any help?
Click to expand...
Click to collapse
What exactly have you tried to do?
Sent from my HTC Magic using XDA App
Hi. My magic is having the same issues. Although I believe it is my own doing. I was going to create a gold card and I flashed the sappimg.zip, I can boot the phone into fastboot but it us not seen, when I run the fast boot command it just says waiting on device..
I can boot the phone up normally but it does not want to connect to the market our link my gmail account to it..
All to jailbreak... Any ideas?
Edit....
I must have had a poor internet connection last night. I have got the market working.
Sent from my GT-I9000 using Tapatalk
I am having the same problem.
I have a 32b on vodafone uk.
all the device adb drivers have installed fine. I have tried this on both my laptop and desktop (win 7) and when the phone is turned on - it shows fine under adb devices.
When i boot to fastboot, the phone doesnt show, and therefore i cannot load a custom rom.
Trying to root the phone I have so far used the goldcard method to downgrade to get back to 1.5, if i try to flash the recovery img from the phone (using flash rec) then when i boot to recovery (home+power) it hangs on the vodafone screen - this is why i wont to flash from fastboot.
any ideas?
Thanks
phone rooted?
FlashRec is out of date, I'm pretty sure. Is your phone rooted already, or are you at stock?
Hi all!
I have a big problem...
My Hero wan't boot so I go in the Recovery Console.
But if i want to restore a Backup this message appears:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
E: Can't mount SDCARD:
I tried several SDCARDs... same message.
I've wiped all several times. Reformat the SDCARD...
Access via ADB brings:
error: device not found
Fastboot mode is possible... but
fastboot boot cm-hero-recovery.img
in the konsole brings: "downloading 'boot.img'... FAILED (remote: not allow)"...
What can i do?
This might help?.....
http://forum.xda-developers.com/showthread.php?t=681583
then go to .....
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/
Thanks for the links...
I could re-flash the T-Mobile ROM (2.73.111.26)... The Hero starts and now it works with Android 1.5 ...
I have access to the SDCARD ... but the USB Connectivity doesn't work...
No ADB and no storage Device in Windows...
"fastboot oem eraseconfig" doesn't work... think about the false HBOOT (HBOOT-1.76.0007)...
flashrec also doesn't work... there comes "Flash FAILED: could not run command"
Any ideas?
Had exactly the same.
Forget about the rom, it doesn't matter (i.e. flash whatever you like).
You already got your SD card support back, for the rest you need to update the SPL (search for an unlocked version for your hero, double-check because it can _really_ brick your device if this fails). After that fastboot oem eraseconfig works and your usb is back to normal.
Did that yesterday, worked like a charm and actually makes sense (unlike other suggestions like "reflash N times", "unplug and replug usb or change the cable" and "send in for service"). Your USB is fine (as seen in fastboot), it's just not working after your kernel booted -> Due to messed up configuration parameters in the flash area. Basically the kernel commandline, if you will..
Wich version of SPL I do you flash?
How do you flash it? Like...
fastboot oem rebootRUU
fastboot flash zip SPL_image.zip
in the fastboot konsole?
RecoveryConsole is not useable to me... My Hero is not rooted anymore... And it seems to be very difficult to get root again :-/
What do you mean by?
Swerner1975 said:
I have access to the SDCARD ... but the USB Connectivity doesn't work...
Click to expand...
Click to collapse
According to BTDAGs guide, flashing 2.73.61.5 should enable you to use flashrec to do the custom recovery again.
[solved] NEED HELP! Bricked? No SDcard in Recovery - no Restore - no adb
Thanks for your help. I have solved the problems...
- first I flashed the T-Mobile D ROM like described in the Link (extract rom.zip and flash)
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/
- then I have detected, that flashrec does'nt work on the ROM
- then I created a GOLD Card
- with this I flashed in the OEM fastboot Mode (described here) the HTC Update ROM (_HTC_Hero_RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe)
- then flashrec was working and I was able to flash a Recovery Image
- in the Recovery Console I flashed the unlocked Modaco SPL (from here)
- now it was possible to erase the config, which locked the USB after Kernel Boot (fastboot oem eraseconfig)
- after that I restored the last Nandroid Backup...
- Now I'm happy
Re: NEED HELP! Bricked? No SDcard in Recovery - no Restore - no adb
Excellent news.
-------------------------------------
Sent via the XDA Tapatalk App
adb shows my device is offline. I reinstalled the drivers and updated the sdk.
The only way my cpu will detect it is if it in recovery, It wont detect at fastboot or hboot. Im stuck at the green htc screen. My device wont boot up. Im trying to push system.img.
can any1 help
Do you have debug enabled in settings > applications?
Sent from my T-Mobile G2 using Tapatalk
as long as you can see it in recovery you can push system.img, but if you are looking to flash it you need to use the fastboot binary(sorry no link) and use fastboot flash system system.img
@g_grey
I understand what you are trying to say. But his phone is listed as offline in recovery mode. How would he go about on getting adb to recognize his phone. It would his phone id but after that it would say offline. And where do you find these binaries?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
binaries are found with google(pretty sure it's somewhere in with the other android dev stuff), then just put the binary with your adb binary(sdk/tools) and if it is being seen as offline then the recovery he is using doesn't support adb in which case not really sure.
@OP
if you have clockwork installed i believe there is an option to mount sdcard as you would from the os, then it should appear as a drive on your comp and you can copy files over.
why are you trying to push system.img? what end result are you aiming for?
Thanks I found it right after I posted. His problem is he's stuck at htc screen and s-on so might push system.img and/or userdata.img. can't do anything else. Tried to flash PC10img but says older version yadda yadda. Any suggestions.
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
use the recover from semi brick thread then, didn't know he was with s-on at this point(doh!)
@g_grey
That's what I say. Just downloaded the fastboot binary and hopefully we get some progress
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Same problem
did you come up with a solution? I can get into recovery mode. tried appling and update.zip for both the original and latest version. I have tried factory reset. I can get the serial number with adb devices but it says offline. I had found a solution where I could put the PC10IMG.zip but it says its an older version. but I found via 14344-how-to-fix-a-bricked-g2-or-root-new-g2s-with-kernel-fix pm cyanogenmod that I could push a new misc.img which would get ride of that error message. but I have to be able to use the adb push and/or adb shell.
Hello all,
I have been using the super one click method to root my HTC Magic Saphhire 32A.
It works well so far albeit need to alter some SU files in the program. Running of terminal emulator with the command prompt SU confirmed that I have the superuser rights.
Now the problem is whenever I use ROM manager to reboot in recovery, the phone restart, HTC logo shows, then the next screen I see is a big asterisk and a phone image, after this I pressed Home + power, the screen manage to switch to Android system recovery utility, BUT with only 3 options:
1) Reboot system now
2) Apply sdcard:update.zip
3) Wipe data/factory reset
And in the end of the screen, there is one line highlighted in red: E: can’t open /cache/recovery/command
After the phone been rebooted, I switched off the phone. And Pressed vol - with power button, same issue happen too with the asterisk sign shows on the screen. After unrooting it, the phone recovery mode are back to normal with the 3 androids in skates appear on the screen.
Have anyone face the same problem? Any ways to sort this out? I am planning to back up my stock ROM, and wanted to try out some cyanogenmod ROM. I tried Googled and read lots of forum post but left without a solution. Any helps are appreciated! Cheers!
p/s: I am a noob in Android OS. XD
I have the legend and these is a process of booting the recovery from there as update.zip. have you tried renaming the ROM update.zip and flashing it from there?
Sent from my HTC Legend using XDA App
I fiddled with the ROm manger setting by choosing "delete recovery prior to flashing", and now it makes it worse.
I selected "reboot in recovery" in ROM manager and the phone reboot, but just stuck at the HTC start up screen.
I plugged in the phone while trying another recovery reboot, and it still stuck at the HTC screen, but with a red line on the top saying "fastboot USB". Gosh I think i am going no way with this...
E:Can’t open /cache/recovery/command
Same fault here mytouch 3g unlocked at&t 32b downgraded too cupcake and tried
getting E:Can’t open /cache/recovery/command
home and power button down still cant get you in recovery? you cant flash any other working rom?
32b myTouch 3g 2.2.1
Cyanogen Nightly 271
Hboot - 1.33.0006
Radio - 2.22.19.26i
Kernel - 2.6.35.9
ADW 1.3.3
ClockworkMod Recovery
Slideit keyboard
Did you flash custom recovery with ROM manager? Or you just rooted the phone with 1 click method?
Sorry for the late reply. I am just back from overseas business trips. I used Clockmod ROM Manager and did a backup, tried reboot in recovery, and the phone rebooted itself but stuck at the HTC logo now.
I can confirm that the phone is rooted with super user permission.
The reason being the phone didn't manage to get into recovery mode might be due to the missing recovery.img in the phone. Pushing the img file to phone through Clockmod didn't work apparently, so I tried command prompt from PC fastboot flash recovery c:\recoveryxyz.img. It failed too with an error remote failed.
I tried using the terminal emulator in the phone and tried pushing the recovery image again and it didn't happen too. Can some one please help? Cheers!
Download ROM manager and you have option that says install custom recovery it will install Clockwork, and you have flash alternative recovery it installs amon ra's recovery i prefer most
Will try it tonight and revert for the result. Cheers!
I have tried flashing alternate ROM through ROM manager and for once it managed to boot into recovery mode. BUT the device hang right after that, I can't select any of the options and have to pull the battery out to force shutdown.
I tried using fastboot flash recovery *.img remotely through my PC while the phone is in fastboot USB mode, and my command prompt stated FAILED (remote: not allow)
Urgh, I think I might have missed something here... Could some one please help? Cheers!
p/s: my objective is to upgrade my stock ROM android 1.5 to cyanogen ROM. Cheers!
I don't know whether this info helps but here goes:
phone info:
sapphire pvt 32A ship s-on H
Hboot- 1.76.0007 (SAPP10000)
CPLD - 12
RADIO - 6.35.07.29
AUG 4 2009
callmeneotheone said:
I have tried flashing alternate ROM through ROM manager and for once it managed to boot into recovery mode. BUT the device hang right after that, I can't select any of the options and have to pull the battery out to force shutdown.
I tried using fastboot flash recovery *.img remotely through my PC while the phone is in fastboot USB mode, and my command prompt stated FAILED (remote: not allow)
Urgh, I think I might have missed something here... Could some one please help? Cheers!
p/s: my objective is to upgrade my stock ROM android 1.5 to cyanogen ROM. Cheers!
Click to expand...
Click to collapse
OK here is the thing did you chose right model of your phone? HTC magic is 32A and mytouch and something else is for 32B you maybe flashed the wrong one?
Thanks WoblyGoblin for taking your time to help. Yes, I have selected the correct phone model. I chose HTC Magic.
Did you install the recovery?
Sent from my HTC Magic using XDA App
I am stuck in trying to install recovery img into the phone. can't boot in recovery mode, tried ROM manager and remote push of recovery img into the phone.
Please refer to the previous post for more info. Cheers!
Ok here is the solution for you use this guide but download this apk and this recovery.
If you dont have 1.5 android but 1.6 download Terminal emulator from market and when you start it type first:
su
flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
Hello mate,
i just tried the method and I am stuck at FlashRec backup recovery image step.
I clicked on backup recovery image, but there is a command prompt that says:" backup FAILED: Could not run command.
FYI, I am running on Android 1.5. On the edge of giving up rooting and loading a custom ROM now and without a MARKET apps on the phone.
callmeneotheone said:
Hello mate,
i just tried the method and I am stuck at FlashRec backup recovery image step.
I clicked on backup recovery image, but there is a command prompt that says:" backup FAILED: Could not run command.
FYI, I am running on Android 1.5. On the edge of giving up rooting and loading a custom ROM now and without a MARKET apps on the phone.
Click to expand...
Click to collapse
Did you try terminal emulator app?
And commands that i gave you?
yes mate, have tried flash_image recovery command from the terminal app and tries to restart in recovery without any result.
I have did a few research and read up and found out that I am stuck with the south east asia Magic model without the google based support, with no market apps and it is perfected SPL.
Quite upset by it. LOL!
callmeneotheone said:
yes mate, have tried flash_image recovery command from the terminal app and tries to restart in recovery without any result.
I have did a few research and read up and found out that I am stuck with the south east asia Magic model without the google based support, with no market apps and it is perfected SPL.
Quite upset by it. LOL!
Click to expand...
Click to collapse
Try this
Hello!
I have a big problem.
I might have bricked the device however the things what i can do are the following:
- Boot into recovery (clockworkmod)
- start a usb data connection with a computer (clockworkmod)
- input of the ADB commands through terminal running in the computer
What i did?
Flashed the memory with a Cyanogenmod 6.3 according to official guideline:
http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Update_Guide
and took note and used most procedures from there actually:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Didn't do the engineering hboot.
Everything was working. I got cyanogenmod working.
Then after a while i tried to restore a backup which i had from original HTC configuration which was actually just before i did the cyanogenmod flash with clockworkmod.
So the backup was from the time i already unlocked the phone from locks and had root access.
So again the restore function worked and everything was back to normal.
How i managed to half brick the device?
Yesterday i wanted to put cyanogenmod back to my phone and then the s hit happened.
I admit that i didn't check whether the locks were off i just thought that these should have been off because backup soft was from time i had phone unlocked.
Anyway to cut the long story short - after flashing the memory with cyanogenmod with the help of rom manager the phone didn't boot anymore.
I tried all the options from clockworkmod flash and format and upgrade straight from sd card a new cyanogenmod but nothing worked. Again the white HTC screen and connection through a usb cable.
So probably i have the s-off and who knows what else.
I dont have a root access anymore as well because i already tried it through the terminal. It doesn't recognize the su command.
Question is, how can i put the cyanogenmod back on by only using clockworkmod recovery and working ADB connection through usb link?
Probably have to just get the locks off but the original instructions say i have to have terminal emulator running in phone but i only have clockworkmod recovery soft running at best.
S hit, again very long story, but hope someone can help me!
Cheers!
I had a similar problem yesterday, after flashing ClockwordkMod Recovery to version 3.0.0.5 (it said it had an update) and trying to reinstall CyanoGenmod 6.3 my phone would no longer boot, it got stuck in the white HTC Logo screen.
I'm not really an expert on this stuff, but I managed to "recover" my device by downgrading it again to 1.32.405.6 using this thread: http://forum.xda-developers.com/showthread.php?t=905003. First I had tried to recover a previously backed-up ROM, but that did not work.
I had to put the stock 1.32 PD98IMG.zip file on my SD card using ClockwordMod Recovery (since I could no longer boot), I'm not exactly sure which steps I took to do so, I have tried a lot of things yesterday before I got everything working again.
After this my phone could boot again and I was ready to play around again. I reinstalled CyanogenMod again using an older version of ClockwordMod Recovery. I'm not sure if this is related in any way, but my phone works smooth again..
Once again; I'm really not on expert on how all this stuffs works, I just hope that I can help you on the way with some ideas on how to fix your device.
So probably i have the s-off and who knows what else.
Click to expand...
Click to collapse
I figured out wether my device was S-OFF and/or Eng S-OFF by entering "adb reboot bootloader" from cmd. At the top of the page for me it states:
ACE PVT ENG S-OFF
I believe it stated only SHIP S-OFF when I had the problems you describe.
Thanks man for quick reply!
I definitely try the downgrading solution and i remember i too did the update for clockworkmod rom manager before the flash.
I'll report back tomorrow.
Cheers!
couldn't boot up any roms earlier after upgrading clockworkmod recovery to v3... downgraded to 2.5.1.3 and worked fine
Hi Guys, I have exactly the same problem. It would be really great if you provide me the step by step process to downgrade clockworkmod recovery.
Cheers,
Pav
I'd like to say to you guys that the downgrading solution worked
Didn't have to use any programs inside phone except clocworkmod recovery which was the only thing i had running.
Thank you user jvdminne!
The downgrading solution was in official cyanogenmod guidelines as well but forgot it anyway.
------------
Pavanka!
The downgrading solution from the link is pretty step by step actually.
But anyway, with my half-broken phone the lines didnt do the trick:
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
I had to copy psneuter and misc_version to /tmp folder not into /data/local/tmp.
But anyhow, i already had # root access through computer. Probably from last half flashed system.
So only thing i basically had to do was to cd in windows cmd into folder where i had psneuter and misc_version and after that:
Code:
adb push misc_version /tmp
adb shell chmod 777 /tmp/misc_version
adb shell
in the shell (adb shell):
Code:
cd /tmp
./misc_version -s 1.31.405.6
And after that follow the instructions from previous link.
To get the ADB functions working just follow the guide here or from previous link where it had adb program included, but not sure whether it was working cause i had it from Android SDK package already set.
Hope you got some sense out of it.
Cheers!
Hey
I had similar problems to those mentioned in the beginning with the cyanogen mod...
I installed cyanogen and the it got to the screen with the blue swirlyness and then just kept restarting. I decided to restore a backup and just got stuck on the white htc screen.
I decided to follow this post and now am stuck with this...
I just tried a couple of different things to no avail...
maxa1577 said:
Hey
I had similar problems to those mentioned in the beginning with the cyanogen mod...
I installed cyanogen and the it got to the screen with the blue swirlyness and then just kept restarting. I decided to restore a backup and just got stuck on the white htc screen.
I decided to follow this post and now am stuck with this...
I just tried a couple of different things to no avail...
Click to expand...
Click to collapse
If you had ROOT , S-OFF etc you shouldn't need to go through all this rigmarole, if you can access recovery carry out a full wipe /system /cache /dalvik-cache and reflash your chosen ROM, should be all that's required
ghostofcain said:
If you had ROOT , S-OFF etc you shouldn't need to go through all this rigmarole, if you can access recovery carry out a full wipe /system /cache /dalvik-cache and reflash your chosen ROM, should be all that's required
Click to expand...
Click to collapse
phew cheers for that. First time flashing and I thought I killed me poor desire.