I flashed the "firmware package" from Android Revolution HD and decided to go back to my original ROM (the latest ICS release). Since I dont know what is different on their "firmware package" vs the HTC update, I would like to take the recovery.img and system.img files out of the HTC release and put in 4ext and flash everything else back to stock. And then use 4ext to restore the OS. Can I do this? or do I need to edit the android-info.txt file? Or if there is a site that gives info on editing the PHxxIMG files that would be handy too. The only other option I see is to flash the entire ICS release, then flash recovery, then restore from nandroid. Any input is appreciated, thanks.
Related
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
Whenever I attempt to flash a ROM via TWRP, I get an error that says no MD5 file found and it just says Failed.
Am I placing the .zip in the wrong location on the SD or am I missing something else entirely?
I'm unfamiliar with HTC phones, I've been with Motorola for the past few years so please enlighten me as to what the issue might be.
Just to make it clear, I am unlocked and rooted and I've flashed the boot.img before attempting to flash the corresponding ROM.
have u upgraded ur hboot version??perhaps u have to move the rom zip into phone storage...are u changing the name of the rom zip???(dont do that)
try reflashing TWRP from fastboot...
turn Force MD5 check on all zips off
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.
I have D/L a few stock recovery .img files with different file sizes.
Q: Are all TMO stock recovery images same?
I have 4.3 sense 5.0 latest firmware and would like the kitkat OTA.
Q: What stock recovery .img do I need to flash and where may I get it?
Thanks.
Oh this is for USA country code..NEW YORK.
I am rooted using the TWRP recovery.. latest 3.3
Thanks.
Whenever I have had need to swap back over to the stock recovery (such as the KK upgrade, which I'm just getting finished up right now) I've always used the stock recovery image from the zip file that Behold_this puts together in his thread, http://forum.xda-developers.com/showthread.php?t=2355814
I think it's been updated now to include the KK firmware, so you may or may not want to download the previous version. If you are curious, the size of the recovery.img that I have is 11.6MB (12,245,248 bytes).
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.