Hi,
Due to HTC's special touches, the recovery image doesnt stay flashed, and on normal boot its flashed over (meaning if i try to go to recovery after a normal boot, i get the red triangle stuff, and have to pull the battery). I was wondering if this would potentially cause troubles if i was trying to flash a custom ROM from recovery? in other notes, i do find sometimes i have to pull the battery 4 or 5 times to get it to normally boot (thats without holding the buttons >.>).
Thanks in advance.
HTC HERO recovery image flashing problems
I am having exactly the same problem!
I did a quite a bit of research on how to root, backup and flash my HERO and every guide I found describes the process using Universal AndRoot + Rom Manager and it seems there should be no problems. I already rooted my phone successfully, installed Rom Manager and flashed either ClockworkMod 2.5.0.1 or RA Recovery 1.7.0.1 which are able to boot but only once. The next time I reboot I get the red triangle warning and it loads into stock recovery (by pressing vol_up + powroff buttons), so the custom recovery lasts only one boot cycle. I was able to backup but I don't want to risk to wipe and flash since there is a chance it might stuck in the bootscreen loop afterwards and I won't be able to do anything.
There is a thing with s-off and SPrecovery which helps to resolve the problem but it doesn't look like there is anything for HERO.
Any help would be appreciated.
ps I tried to manually flash recovery from inside the phone and from windows command line with the same result.
forum.cyanogenmod.com/topic/8182-how-to-root-your-hero
posted some similar comments over there, and the only init script that i can find when in recovery.
Yeah I posted my question there too.
I was able to find some information about the issue (he is talking about Villain ROM but I think it doesn't really matter):
pulser_g2:
Repeat the process again, as I think stock ROMs try and overwrite the recovery each time they boot. When you finish the process, immediately nandroid and flash VR12. That will then flash a new recovery, AmonRA 1.6.2a, and you will be sorted
Click to expand...
Click to collapse
So it looks like we should just go ahead and flash a custom rom which, in theory, will eliminate the problem.
yeah was tempted to just flash, but sending duck my system img for him to dissect anyway.
yeah worked fine, running cm6.1 now
Yeah once you root you have to flash a custom rom before reboot or u loose the root
I learnt it after lots of reboots and re roots.
but now I wanted to know if I could save the original rom which i have as nand backup to make as an update.zip like custom rom for safe keepimg
I flashed CM6.1 -based TastyFroyo 1.2 and I can confirm custom recovery stays flashed now.
Related
I have successfully been able to root and install everything on my Mytouch4G just fine, however, when I tried to install my wife's Vibrant, I am stuck. Here is what I have done:
1) I rooted successfully using superoneclickv1.9.1
2) I installed ROM Manager and also downloaded the Auxora ROM to get ready to install
3) When I flash CWM recovery, it says current and latest recover is 2.5.1.2 (concern here that my mytouch says 3.0.2.4 - do different phones install differently with CWM?). When I look at all CWM recoveries I also notice there is two seemingly more current versions available 2.5.1.3 and 2.5.1.4. I have left it at .2 but wondering why all the versions.
4) When I reboot into recovery, I always get the stock recovery and have not been able to get CWM recovery so I am unable to flash my Auxora ROM. I ran update packages numerous times, and get a signature verification error. I have tried a recovery 3e patch that does not work either. I also gave a try at downloading and SDK, but received temp root errors (phone is already rooted).
After reading many posts, I cannot seem to get a direct answer on what I should do to get CWM to actually boot properly, so I can flash a ROM. Someone said to flash the stock JDK rom, but if I can't boot into recovery, how can I flash anything.
Any help would be greatly appreciated.
You need to get a program for your pc called odin to get back to stock. you can find that and instructions on how to use it if you search for the daily updated vibrant bible its GREAT
http://forum.xda-developers.com/showthread.php?t=849028
going to stock eclair heres a a great guide
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Every once n a while I haft do the install packages thing twice before it gives me clockwork green
. Hope this helps.. o n btw u should look at some of the other roms in the bible before u try auxora
yes u should go back to stock eclair for every rom, in my opinion. Then after that do the 3 button combo and install packages and u will have to do it twice and then the green screen will kick in and ready to rock a new rom.
i hope this helps
What is your current firmware?
I see you posted over in the "NOOB GUIDE" thread, you should really try to root using the method posted there and not any one click root apps.
This should be the root method everyone uses:http://forum.xda-developers.com/showthread.php?t=723479
After root your phone recovery should be blue. Choose "reinstall packages" gives you green recovery(this may need to be repeated multiple times to work possibly including flashing CwMRecovery with ROM manager. I recently did it 5 times b4 i got green recovery)Once you access green recovery chose "apply sdcard:update.zip" go into advanced and choose "reboot recovery" This should give you red recovery. Do a nandroid backup and flash away. Good luck!
Another option you could do is to download SGS kernel flasher from the market and flash a voodoo injected kernel with that app. Then when you boot into recovery you will have red voodoo recovery and you can flash away.
Odin to stock the best way to flash a new rom
Sent from my SGH-T959 using XDA Premium App
jman531 said:
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Click to expand...
Click to collapse
The stock 2.2 that Samsung distributed with their Kies tool has a recovery that checks signatures. Everything earlier does not check signatures. So either use something earlier to get CWM running, or use a ROM that doesn't have the stock 2.2 recovery in the first place, or mod your recovery using the method described in http://forum.xda-developers.com/showthread.php?t=833423
Using Odin to go back to stock Eclair between your flashes of modded roms has the benefit of taking care of this, and also can clear up left over bits and pieces that may interfere with the proper function of your new ROM.
ok, i followed the instructions and am back to eclair, however, whenever I install packages, it just reboots the phone, not even back into stock recovery. I use the 3 key method and get into recovery, run install packages, and the phone just boots back up...its like it isn't running the update.zip file...
UPD: When i load rom manager and try to reboot into recovery, it says the application superuser permissions has stopped unexpectedly and keeps force closing now....titanium backup wont run now either, my root permissions seem whacked after going back to eclair?
UPD2: I followed instructions to unroot and reroot here: http://forum.xda-developers.com/showthread.php?t=739300
It removed superuser, then added it back again, but I still get the unexpected error and it appears my root is not in place. I am back to eclair, and now need a certain way to get my root fixed, so I can try and flash CWM recovery. Without root working, it is not letting me. My wife hates me now for doing this to her phone, so those of you that are married, I would appreciate your assistance to get back on her good side...before Mother's day...please? =)
Ok, thanks for all the help, however, I am really back where I started. I can only get stock recovery, and for the life of me, cannot get CW recovery to load. I used ODIN to go back to eclair on the vibrant, have a good root on the phone now, and no matter how many times i reinstall packages i cannot get clockworkmod recovery to load, ever. Any more thoughts out there?
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
thanks...It is rooted, but not sure about busybox...the stock recovery is 2e now since I went back to eclair, so not sure i should follow that link as it talks about modifying 3e and making it backwards compatable. I did use that process before I went back to eclair, and it didn't work for me. I have uninstalled rom manager, and reinstalled...and it is different in that it shows a flashed recovery 2.5.1.2, and never asks me for my phone type anymore...it used to ask me and i had to select vibrant....is the recovery supposed to be 2.5.1.2? when I show all recoveries it lists .1, .2, .3, .4 so wondering if I should use .3 or .4...why does it stay at .2?
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
OK>>> I GOT IT... Thanks to everyone who helped...Here is what was needed:
1) Install ODIN, install back to eclair
2) uninstall ROM Manager, reinstall
3) I needed to select the 2.5.1.2 recovery from the list again (this was important as it somehow knew of the previous load, but files were missing, or something was just wrong.) It finally loaded properly, and asked for phone type again, so selected vibrant
4) I rebooted into recovery, and instead of install packages, i rebooted once, as starkiller suggested
5) After reboot, went back into recovery from rom manager, and this time installed updates, and it showed that it replaced the recovery with CWM.
6) It rebooted into stock recovery however, so I once again selected install updates, and it went right into CWM recovery, and now I am flashing happy!!!
Thanks again everyone...this was soooooo different than my mytouch4g!
If you have the Kies update of Froyo, the 3e mod will sometimes not work. I've gotten to CWM though , but its best to downgrade then flash a ROM from there.
I just wanted to bump this thread because it really helped me.
I've messed around with numerous android phones, and I've never had thie issues I've had with this phone getting into recovery to flash ROMs
Thank you!
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!
I followed this guide here to root my EVO 3D:
http://forum.xda-developers.com/showthread.php?t=1239821
Then my friend who already had a rooted Galaxy S told me to get ROM Manager and it installed Clockwork Recovery. I didn't know you only needed one recovery since I'm noob at this and when I tried to install a Custom ROM with Clockwork, it just boots and I get the Sprint logo and nothing happens. I try to boot into TWRP and nothing also happens. I think having two recoverys is going a major issue with my phone and I'm unable to install any roms. Is there anyway to go back to just having the TWRP Recovery and get rid of the ClockWork/ROM Manager? Or will I have to reset everything and root again?
Huh... Sounds like the hboot 1.5 is giving you issues... Use image GUI app for 1.5 to flash right from normal android mode( everyday user mode) look the thread in themes and apps to get it installed. Let me know how it goes here. No link as I'm using the tapa app
Shot from my shooter in 3D
injected with cleanrom2.7
r2thek said:
I followed this guide here to root my EVO 3D:
http://forum.xda-developers.com/showthread.php?t=1239821
Then my friend who already had a rooted Galaxy S told me to get ROM Manager and it installed Clockwork Recovery. I didn't know you only needed one recovery since I'm noob at this and when I tried to install a Custom ROM with Clockwork, it just boots and I get the Sprint logo and nothing happens. I try to boot into TWRP and nothing also happens. I think having two recoverys is going a major issue with my phone and I'm unable to install any roms. Is there anyway to go back to just having the TWRP Recovery and get rid of the ClockWork/ROM Manager? Or will I have to reset everything and root again?
Click to expand...
Click to collapse
You can't have 2 recoveries installed at the same time...if you initially had TWRP, when you flashed clockwork it would've over-written TWRP. You don't need to reset anything or re-root to get back to TWRP. You should just be able to flash TWRP again. Use the method from the thread you initially followed. Just the part about flashing TWRP is all you need to do. I've never tried it, but you could also try flashing it with the app flash gui image, or something to that nature. Joeykrim developed it and I've heard it works nice, here's where to find info about it, http://forum.xda-developers.com/showthread.php?t=1192527. If your phone won't boot, the flash gui image app prob wouldn't be the best way. I would just boot your phone to fastboot, re-flash TWRP recovery, then flash a rom and try rebooting.
I don't have hboot 1.5, so I'm not up to date on the 'special' ways you need to flash, but I know that you need to boot into recovery from fastboot in order to flash a kernel, and I'm not sure if there's other steps you need to to take in the flashing process, so research that and make sure you're doing it correctly. If you don't boot to recovery from fastboot, the kernel won't flash and you'll be stuck in boot loops or something like that. Good luck.
Thank you guys! The flash image gui thing made the fix very seamless. I just flashed TWRP again and now it's showing up. Flashing synergy nitely now. Woot!
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 was trying to switch my phone over to CWM from TWRP. I tried flashing using ROM manager but it was always rewritten. I decided to grab the .img file from the CWM site and flash it in terminal emulator like I had done with TWRP before. It seemed to flash but when i rebooted I got the message that the system software was not authorized. I thought the file I downloaded was loki but I guess not. Do I have to odin back to stock now or is there another method?
So I just realized it was being stupid and was stuck trying to boot recovery. I booted to download mode and selected cancel to force it out of this loop. Once it did this I was able to boot the system and restore a proper recovery.
On a side note, does anyone know why flashing CWM doesn't stick. I read some things about the recovery being flashed every boot but all the information was out dated, I couldn't find anything about the S4.
thecaptain0220 said:
On a side note, does anyone know why flashing CWM doesn't stick. I read some things about the recovery being flashed every boot but all the information was out dated, I couldn't find anything about the S4.
Click to expand...
Click to collapse
ROM manager does work...try flashing then reboot at least once before booting recovery...and if you are running a stock tw rom some will attemt to overwrite custom recovery...in newer cwm it will ask you if you want to disable recovery install...clicking yes will stop the process keeping custom cwm