hi.
i have never had problems with my hero before but suddenly i'm unable to flash anything on it. i have always been on the stock recovery with S-OFF and rooted.
i flashed VanillaEclair 6.2 a while back and had no problems.
yesterday when i tried to flash another rom, i got signature verification error. I thought i'd flash TWRP or CWMR to bypass the signature verification but when i tried to flash it, i got the same error.
i tried to flash the recovery through rom manager but it failed...even with adb!
frustrated, i thought to use the official rom RUU...i ran the RUU, it went halfway in flashing the rom and then gave error.
now i don't have any recovery and pressing 'home+power' leaves me at the HERO screen forever.
luckily i can still boot in android so my device is not bricked.
I have tried pushing the recovery via adb but even the fastboot doesn't work.
i tried starting from scratch to check for the bootloader lock. fastboot oem get_identifier_token returns an error.
phone is working fine but i don't like the rom and want to be able to flash via custom recovery.
please help!
much appreciated.
http://wiki.cyanogenmod.com/wiki/HTC_Hero_(GSM):_Full_Update_Guide Check the installing a custom recovery page, use the FLASH_IMAGE method
Related
Early today, I was working on a G2 trying to get it rooted with a custom ROM installed. I managed to root the phone and disable the bootloader security. From here, I attempted to install clockwork recovery via rom manager... here's where the disaster starts.
Everything seemed to be going well (no errors), so I tried to load a custom ROM. The Rom installation started but failed partway through. This is when I noticed that the clockwork recovery wasn't working properly. It was flickering and none of the options worked (screen just flashed or turned black if you selected anything). So at this point, the phone would not boot since the ROM installation didn't complete, and I had a buggy recovery image installed.
Unfortunately, the fun doesn't stop here. I figured that I should load the PC10IMG.zip and start from scratch... bad idea. This flashed the bootloader (relocking it) then failed-- leaving me with a bad ROM, bad recovery image, and a locked bootloader. Luckily for me, I was able to use adb via the buggy recovery to unlock the bootloader again.
At this point, I got a bit antsy and jumped the gun. I decided to use fastboot to erase and load a new recovery image. Unfortunately, I realized that I didn't have a recovery.img file to flash... just after I used the fastboot erase recovery command.
I'm hoping that someone here has a recovery.img file compatible with the T-Mobile G2 so I can flash the recovery partition with fastboot. If anyone has any better ideas I'm open to suggestions.
Thanks in advance for any help.
Install amon recovery. It's much better then clockword. Do it using adb
Sent from my HTC Hero using XDA App
Just an update. I couldn't get into adb but I was able to flash clockwork via fastboot. For whatever reason, the amon recovery would go through. Nevertheless, I installed cyanogen using clockwork and everything is gravy!
Im stuck in a pickle. I tried to update to neutrino 2.8 but got caught in a boot loop. I followed instructions that worked last time and tried to repair my recovery and it wiped the recovery and all other system data, but fastboot wont reboot or install the recovery image it only wipes the and formats. help please
Your details are not that clear. Either you are not using fastbook incorrect, or you have somehow borked the bootloader/
If the latter, you can try using RSDlite to reflash the bootloader. See the threads on how to unlock your bootloder for these steps. This is as close to going back to square one as you can.
BTW, you might also say how you did this. If just using CWM to install zips it is really hard to screw up your recovery.
I am trying to use fastboot to flash a recovery But when i flash the recovery i get
error cannot load recovery
or
waiting on device
But it will sucessfully wipe and format, just not flash or for some reason reboot the phone
I have it figured out to the point where now i try to flash the recovery and it hangs at
Waiting for Device
I tried everything i can think of
reboot
Re-install drivers
re download file
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You need to unlock again in order to flash back a custom recovery. You also need to have the stock splash screen before you ruu. Had the exact same issue you had. Stock h-boot, stock splash screen and relock and all should be good.
That is my main problem. All of the unlock methods require me to load load an apk to change the CID. I can't do that in fastboot. Is there another unlock method I'm missing that allows you to do it from the fast boot mode?
Sent from my LG-D800 using Tapatalk
if u have your original unlock code from htc dev I think u can fastboot flash that code to unlock again. its in the forum somewhere just not sure where it is.
try this thread, good luck
http://forum.xda-developers.com/showthread.php?t=2160677
You don't have to run a apk to change the cid just Google change cid commands, you do it through adb change it to 22222222 then redo the HTC dev to get your unlock.bin again if u don't have it.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You device most likely can't downgrade due to having a locked device. Have you tried flashing the 2.07 ruu
Thank you for all of the replies. Actually the change of the CID command might have worked but I didn't see that reply before I had tried another method found in this thread: http://forum.xda-developers.com/showthread.php?t=2570548.
I was truly stuck in fastboot and couldn't flash a custom recovery at all. Well I used the advice from a previous thread and edited the firmware .zip posted in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2314771. I had initially tried to flash the .zip posted but when I tried to boot into the recovery it wouldn't work. So I opened the .zip file without extracting it and removed the recovery.img from the .zip, I then took the TWRP custom recovery and inserted it into the .zip (if you extract the zip this will not work; you need to use software that can edit a zip without extracting it. On the Mac, which I was using, I used Spring). I renamed the TWRP recovery to "recovery.img" to match what I had previously deleted.
Then I flashed this edited firmware.zip by using the following command in usb fastboot mode (here's the link for my edited file):
fastboot oem rebootRUU
fastboot flash zip YOUREDITEDFILE.zip
fastboot reboot
This then allowed me to boot into recovery. I thought I had figured it out and could now sideload a ROM using the "adb sideload" command and flash some type of ROM that would boot. This failed miserably; it would allow me to push the file, but the install would always fail before it completed.
So then I found this thread here: http://forum.xda-developers.com/showthread.php?t=2570548. I first flashed the two .zip files that were posted in post #44. then I flashed the full RUU posted in post #1. This gave me a bootable stock ROM. Praise God!!!
Finally I went back to this thread: http://forum.xda-developers.com/showthread.php?t=2293919, and flashed the following code.
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Not sure why I had such a terrible time, but I'm glad its over and the DNA is finally sold. Thank you for all your help!
trying to restore my dna back to stock
I got my dna locked again and now I am running the ruu file and i am stuck at 6%. Can someone help please!! Tried it by double clicking the ruu file and running it like that, and i also ran it in administration and both ways i am stuck at 6%
Hello everybody!
The last day my phone got stuck on bootloader screen. It just wouldn't boot the OS.
So I tried to fix that by flashing other rom. I have unlocked it trough MiUnlock.
Flashed in fastboot TWRP(rosy) recovery. It could boot TWRP but after a reboot, would launch MiRecovery.
After that the Android didnt start no more. After a new flash of TWRP I was able to enter recovery. I tried to flash a custom rom. After that the VOLUME UP + POWER wouldnt launch recovery no more (Also VOLUME DOWN+UP+POWER buttons, wont boot the Recovery)
Now i found an EDL mode to flash rom through XiaoMiFlash. Did it, Made the steps from tutorials. That, has changed the device to COM10 in MiFlash which let me try different official roms, and i always get the same error message: cannot receive hello packet, MiFlash is trying to reset status!
Also tried too flash a recovery img.
Tried everything i found on that, nothing worked to get those packets...
My only hope was to fastboot flash recovery TWRP or MiRecovery. And then flash new rom to fix my phone.
Tried many version of Twrp, but no success to actually flash.
I have tried removing recovery via adb and flashing another. Logs shows success but no effect on phone.
Still can't acces recovery mode on my phone.
Bootloop stuck. Shows MI logo and that its Unlocked.
Doesnt work flashing via fastboot - TWRP or MiRecovery images.
My phone is bricked for a week now. Please share a solution if you got one.
SOLVED
Good news. finally flashed chinese version through miflash tool.
had to rename some files from rom.
Flashed through BOOTLOADER.
need some help i have curtana model. I successfully unlocked the bootloader then i went to flash the eu rom but it failed in twrp. i tried to reboot the phone but I got the system is destroyed screen. I still have access to fastboot but no recovery nor the os also. I tried to flash the stock rom with the flash tool but I've never had a success flashing a rom. the tool stays in flashing mode without a fail or success state. i left it all night and nothing happened. when in fastboot I'm still able to run fastboot commands but i cant flash manually any kind of recovery i still get the system destroyed screen.
do I still have hope to boot this device or not