Hello
The touch screen on my hero has broken.
It's not responding in some places.
I have to send it in for repairs.
Im running Modaco 3.0 & amon ra recovery image on the phone.
As this problem with the screen is a warranty issue, i have to revert the phone back to the standard os & standard recovery image.
Anyone know how to do this?
I can't find any guide for this.
I want to flash the phone with the standard htc hero rom and at the same time get the standard htc recovery image back.
This is a European unbranded phone.
I'm guessing you made a Nandroid backup before flashing to MoDaCo Custom ROM? If so, restore the backup via the boot menu and the recovery image to the original one (guessing you backed that one up too).
Code:
mount -a
flash_image recovery /sdcard/recovery-backup.img
reboot
And that should be it.
Also, I think that if you download the latest ROM upgrade for Hero via htc.com, even the recovery image also be reverted to the original one. However, someone will have to confirm.
Don't have a nandroid backup. Formated the card,swaped card and so on..
:'c said:
Also, I think that if you download the latest ROM upgrade for Hero via htc.com, even the recovery image also be reverted to the original one. However, someone will have to confirm.
Click to expand...
Click to collapse
I would say you're right on that solution!
Yes, just run the RUU for generic Hero's and everything will be set back to factory.
Regards,
Dave
Related
Hi everyone,
I currently have the htc official 1.5 ROM but did use nandroid a while back to try out another ROM, but reverted back to 1.5.
I have recived the OTA update message but when i click install it reboots loading nandroid, i then have to select reboot phone (from the nandroid menu), it reboots then no update.
I have tried this many times.
Thanks for your time.
maddock said:
Hi everyone,
I currently have the htc official 1.5 ROM but did use nandroid a while back to try out another ROM, but reverted back to 1.5.
I have recived the OTA update message but when i click install it reboots loading nandroid, i then have to select reboot phone (from the nandroid menu), it reboots then no update.
I have tried this many times.
Thanks for your time.
Click to expand...
Click to collapse
You could just move the back-up off the phone and into the PC...
How would i go about completly removing nandroid as i no longer need it?
Thanks,
The probable reason you cannot install the htc offical ota update is because you have custom recovery/bootloader.
If you want to install the ota, you need to revert back to the stock recovery.
2 ways to do this.
Either flash a RUU
or
If you made a backup of your recovery, (When you flashed a custom recovery using flashrec, you should have made a backup and it can be found in your sd card as recovery-backup.img) use flashrec and type in the path to recovery-backup.img.
Do note that if you install 2.1 official from htc, you will not be able to root until someone finds a way to root it.
Custom ROM =
I don't have a solution but this is why I stayed away from custom ROMs.
I have a Evo 3d, hboot 1.50 latest radios, prl, pri. I had OMJ's latest Rom, and used Flash Image Gui to flash a custom Kernel package; I flashed Tiamuts "Tiamat_E3D-v1.1.0-Sense" http://downloads.tiamat-dev.com/8x60/110/Tiamat_E3D-v1.1.0-Sense.zip, and rebooted, then my phone was locked up on just the HTC screen.
I can still access the Bootloader, and Fastboot, and Recovery. I tried rolling back to my nandroid backup, and also reflashing the stock kernel through recovery (as the Rom won't ully load), and now all I get is a black screen after the HTC logo, and the phone is responsive to power and capacitive buttons, but no display at all.
Tried full wipe, and reflash of OMJ, even CleanRom.... Just black screen after HTC logo.... Any Ideas ? With Bootloader, Fastboot, and Recovery, you'd think I could unbrick, but no luck.
I'm sorry... I'm not a complete noob, I've been on the scene since early TP2s, and always rooted and custom rom’ed my Evo 4g.... Please help guys. Thanks in advance.
blckout99 said:
I have a Evo 3d, hboot 1.50 latest radios, prl, pri. I had OMJ's latest Rom, and used Flash Image Gui to flash a custom Kernel package; I flashed Tiamuts "Tiamat_E3D-v1.1.0-Sense" http://downloads.tiamat-dev.com/8x60/110/Tiamat_E3D-v1.1.0-Sense.zip, and rebooted, then my phone was locked up on just the HTC screen.
I can still access the Bootloader, and Fastboot, and Recovery. I tried rolling back to my nandroid backup, and also reflashing the stock kernel through recovery (as the Rom won't ully load), and now all I get is a black screen after the HTC logo, and the phone is responsive to power and capacitive buttons, but no display at all.
Tried full wipe, and reflash of OMJ, even CleanRom.... Just black screen after HTC logo.... Any Ideas ? With Bootloader, Fastboot, and Recovery, you'd think I could unbrick, but no luck.
I'm sorry... I'm not a complete noob, I've been on the scene since early TP2s, and always rooted and custom rom’ed my Evo 4g.... Please help guys. Thanks in advance.
Click to expand...
Click to collapse
Since you're on the HTC unlock method, in order for the custom recovery to properly work, i.e. flash all partitions including the kernel/boot partition, you have to access the custom recovery differently than the traditional method.
The proper command and method to access the custom recovery in order for the HTC unlock method to grant it write access to the kernel/boot partition is through fastboot. The full command is: fastboot boot c:\cwm-recovery.img . Once you've temporarily fastboot booted the custom recovery, you can then properly flash a ROM or restore a nandroid as both will be allowed write access to the kernel/boot partition.
Appreciate your support in using my application! Hope that helps!
Deleted my own question. I think I found a thread where it will be more appropriate.
Like joeykrim stated, you must access the recovery from fastboot to be able to flash kernels, nandroids and what not from recovery if you used HTC's method to unlock you phone. You are not bricked. It is fully fixable.
I have Clockwork Recovery flashed, always have (the only version compatible with Hboot 1.50, v4.0.1.4). I still have full access to the Bootloader, Customer Recovery, and Fastboot. But despite reflashing a fresh Rom (2 in fact), full wipes, reflashing boot.img with stock kernel; all the phone will do is boot past the HTC screen, vibrate, and the screen goes black. Capacitive buttons are responsive, and so is the power button, just no display. ...... Idk what else to Flash to get this phone booting again, any ideas ?
I had same problem I have 1 file name PG86IMG.zip I don't remember from where I downloaded 1st Iplaced this on SD root folder and turn on phone with volume down and power button and it care of everything
Sent from my PG86100 using XDA App
blckout99 said:
I have a Evo 3d, hboot 1.50 latest radios, prl, pri. I had OMJ's latest Rom, and used Flash Image Gui to flash a custom Kernel package; I flashed Tiamuts "Tiamat_E3D-v1.1.0-Sense" http://downloads.tiamat-dev.com/8x60/110/Tiamat_E3D-v1.1.0-Sense.zip, and rebooted, then my phone was locked up on just the HTC screen.
I can still access the Bootloader, and Fastboot, and Recovery. I tried rolling back to my nandroid backup, and also reflashing the stock kernel through recovery (as the Rom won't ully load), and now all I get is a black screen after the HTC logo, and the phone is responsive to power and capacitive buttons, but no display at all.
Tried full wipe, and reflash of OMJ, even CleanRom.... Just black screen after HTC logo.... Any Ideas ? With Bootloader, Fastboot, and Recovery, you'd think I could unbrick, but no luck.
I'm sorry... I'm not a complete noob, I've been on the scene since early TP2s, and always rooted and custom rom’ed my Evo 4g.... Please help guys. Thanks in advance.
Click to expand...
Click to collapse
You arent bricked if you can still get into fastboot, recovery, etc. I would recommend using this app called Flash Image GUI on the market, it's only $0.99 and I am (as we speak) flashing ziggy's dual core kernel. Oh wait my phone rebooted now. Its fast as all get out and my WiFi works (yay). But like I said this method is the EASIEST way to flash kernels!
up7up said:
I had same problem I have 1 file name PG86IMG.zip I don't remember from where I downloaded 1st Iplaced this on SD root folder and turn on phone with volume down and power button and it care of everything
Click to expand...
Click to collapse
I think the file you're referring to is the RUU (ROM Update Utility) file which can be placed in the root of the sdcard as PG86IMG.zip and flashed to competely reload all stock software (radios, system, kernel, etc) on the device.
These files are available at http://goo-inside.me/shooter/ruu.
blckout99 said:
I have Clockwork Recovery flashed, always have (the only version compatible with Hboot 1.50, v4.0.1.4). I still have full access to the Bootloader, Customer Recovery, and Fastboot. But despite reflashing a fresh Rom (2 in fact), full wipes, reflashing boot.img with stock kernel; all the phone will do is boot past the HTC screen, vibrate, and the screen goes black. Capacitive buttons are responsive, and so is the power button, just no display. ...... Idk what else to Flash to get this phone booting again, any ideas ?
Click to expand...
Click to collapse
Seems as if there is some issue with the display. If you confirm you have adb access to the device, I would think the issue lies in the android /system. If you don't have adb access, I would think the issue lies in the kernel/ramdisk.
Either way, if you want to eliminate both issues, reflash my Stock ROM - [ROM] joeykrim-original-1.2.0 Odex *Stock Rooted 2.08.651.2*, which will reload the stock kernel and the stock system with only adding in root access. I run this ROM as my daily ROM and it works great for keeping the phone stock but allowing root access.
Make sure to access the custom recovery through, fastboot boot c:\android\cwm-recovery.img . If you load the custom recovery through adb reboot recovery, or bootloader and selecting recovery from the menu, the HTC unlock method will not grant recovery write access to the kernel/boot partition.
Worse case, my stock ROM with stock Kernel doesn't resolve the display issue, you should flash the stock RUU files at http://goo-inside.me/shooter/ruu . If that doesn't resolve the issue, you'll prob need to exchange/return the device as it would seem to be a hardware issue.
Hope that helps! Good luck!
Hello! I'm new-ish here... As in I just opened an account to post after watching from the sidelines for a few months now.
Anyway,
I'm having problems with my phone. I was running ViperLTE 2.1.1 and recently switched to CyanogenMod. My sdcard wouldn't work correctly, so I tried to go back to stock, and my phone never made it past the "HTC" boot screen. I've tried reflashing and whatnot almost a dozen times, including restoring my nandroid backup, with no luck. Now I can't even access it via adb. What do I do?
Fastboot the stock boot image. The instructions are in the development section. Are you s off?
Sent from my Incredible 4G LTE using Tapatalk 2
MJL99 said:
Fastboot the stock boot image. The instructions are in the development section. Are you s off?
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
I'm not s-off, and I have tried that multiple times, and at this point I can't get to adb or fastboot. I'm having trouble even accessing the bootloader.
EDIT: I got to the bootloader and adb/fastboot, but still flashing any boot image does nothing to fix the problem, and I'm still stuck at the htc screen.
19wolf said:
I'm not s-off, and I have tried that multiple times, and at this point I can't get to adb or fastboot. I'm having trouble even accessing the bootloader.
EDIT: I got to the bootloader and adb/fastboot, but still flashing any boot image does nothing to fix the problem, and I'm still stuck at the htc screen.
Click to expand...
Click to collapse
You are flashing the stock boot image right? From here for example.
Code:
fastboot flash boot boot.img
Are you installing a stock(-based) ROM or restoring a nandroid?
mdmower said:
You are flashing the stock boot image right? From [[Link removed because of new-user limits]] for example.
Code:
fastboot flash boot boot.img
Are you installing a stock(-based) ROM or restoring a nandroid?
Click to expand...
Click to collapse
Yeah. I'm repeatedly flashing the stock boot image and restarting, to no avail. According to the CyanogenMod forum, I need to install a stock-based ROM and then format my sdcard (to fix my initial problem)... and then restore my nandroid afterwards. At this point, it would be nice to just be able to restore the nandroid and have a phone that makes calls for a day-trip I'm going on tomorrow.
19wolf said:
Yeah. I'm repeatedly flashing the stock boot image and restarting, to no avail. According to the CyanogenMod forum, I need to install a stock-based ROM and then format my sdcard (to fix my initial problem)... and then restore my nandroid afterwards. At this point, it would be nice to just be able to restore the nandroid and have a phone that makes calls for a day-trip I'm going on tomorrow.
Click to expand...
Click to collapse
Just to check, after flashing the stock boot.img, you have installed a stock ROM or restored a stock-based ROM from a nandroid right (i.e. you're sure the backup is not from CyanogenMod)? The boot image alone isn't going to do anything. Also, depending on whether you were running Viper 1.x or 2.x, you need a different boot.img. The boot.img for Viper 1.x can be found here.
If restoring your nandroid backup doesn't work, freshly install Stock (or Viper).
mdmower said:
Just to check, after flashing the stock boot.img, you have installed a stock ROM or restored a stock-based ROM from a nandroid right (i.e. you're sure the backup is not from CyanogenMod)? The boot image alone isn't going to do anything. Also, depending on whether you were running Viper 1.x or 2.x, you need a different boot.img. The boot.img for Viper 1.x can be found here.
If restoring your nandroid backup doesn't work, freshly install Stock (or Viper).
Click to expand...
Click to collapse
I'll try that when I get to the computer, but do I need to use twrp or can I continue to use cwm? Also I can't access the sd card via my computer to put the rom onto it because it doesn't mount when I'm booted into recovery
19wolf said:
I'll try that when I get to the computer, but do I need to use twrp or can I continue to use cwm? Also I can't access the sd card via my computer to put the rom onto it because it doesn't mount when I'm booted into recovery
Click to expand...
Click to collapse
Either TWRP or CWM will work. There is a test version of CWM that enables USB mass storage support... but I haven't yet tested the feature under Windows.
I got it to work, via side-loading the zip and then flashing the boot.img. I don't know why I was having so many problems before... But they're better now. Thanks for your help
im having major issues here with my device it all started with me trying to flash it to cynogenmod 10 which apparantly my device has the s-on so i was stuck in the cmod boot logo, luckily i backed up my device prior to that with the stock rom and everything so i restored successfully back to my stock rom. then i was reading along some forums to see what the problem was and i came accrosss this forum "http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-s-h-boot-1-15-a.html" which gave me a few options on how to flash kernels with the right one that will work with cynogen mod, i chose option 1 because it said it is recommended which the steps were to take the rom "boot.img" file and copy it over to the android sdk platform tools folder and open up a cmd and i flashed the rom "boot.img" which according to the forum that contains the kernel that belongs with that rom i did what it ask went to fastboot mode and typed in fastboot boot boot.img, which succeeded, when i rebooted the device it boots up acting like it is trying to open up recovery mode which is twrp recovery, after that it does nothing it blacks out and a little white bar flashes on top of the screen from time to time then it turns off and reboots and do same cyckle, i attempted to go back to twrp and restore my stock rom which said it succeeded but when i rebooted it did the same thing acted like it was tryning to boot up to recovery being inforemd with those red letter about developmental purposes only stuff, so i factory rested my device wiped dalvik cache and cache and even wiped the system rom and restored my back up with stock rom and nothing works still, please help i am stuck please!!
You probably need to pull the boot.img from a stock ROM and send it via fastboot since your trying to go back to your stock backup.
thanks, but now i got the cynogen mod 10 to boot up now for some reason the touch screen does not respond to the touch neither does the capacative touch buttons work either do you have any idea what it could be?
If you have the 3.16 OTA update then you're touchscreen firmware is incompatible. If this is the case your stuck with 3.16 based roms. Cm will not work for you.
Sent from my EVO using Tapatalk 2
well the 3.16 ota update is that the latest one?
Yes. If you have the 3.16 update the only way your going to get cm to work is to s-off and downgrade you're tp firmware.
Sent from my EVO using Tapatalk 2
do you know were i can find these recourses on how to do this? i know that it has something to do with dirtyracun or something like that but i didnt really didnt understand their website on how to s-off and how to i downgrade my tp firmware
droidman89 said:
do you know were i can find these recourses on how to do this? i know that it has something to do with dirtyracun or something like that but i didnt really didnt understand their website on how to s-off and how to i downgrade my tp firmware
Click to expand...
Click to collapse
I'll try..
First and foremost you need to go here http://themikmik.com/showthread.php?13192-RADIOS-RECOVERY-FLASHABLE-Jewel-Radio-Collection&p=220556&viewfull=1#post220556 and download the boot.img only for whatever version of the stock rom your backup is.
Put it in your sdk tools and open a command prompt and fastboot flash boot boot.img
Go to twrp recovery and WIPE cache, dalvik, factory reset, and system.
Restore your stock backup.
Reboot.
If you can get back to your stock rom, then you should read up on dirty racun or possibly facepalm to gain s-off if you want to run cm.
Hello Everyone,
I know that this is an old phone but could you please help me to install a stock rom or one that will work.
The problem
The phone is stuck in a boot-loop the person who asked me to look at it said that have been happening since the phone fell very hard.
What I did
I managed to get the HTC dev unlocked and flash cwm recovery (the latest version). At present the phone can only boot in recovery and the bootloader.
What I would like to do next
I would like to flash a rom anyone that can work with the current firmware, I think I will be able to update it from there.
So please any help will be greatly appreciated.
Thank You
The real problem here is that the latest firmware does not have a RUU (the HTC firmware restoration file)... CWM is not really recommended anymore, you should change to the latest TWRP, then I would recommend flashing the ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2260154
It is as close to stock as you can get in a non-bootable state. Remember that when you flash a rom on this device well it is S-ON, you must manually flash the boot image with fastboot.