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!
Related
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.
So heres the deal, i tried to flash miui and it doesnt work at all, i am the dummy who didnt do a nandroid back up, and now im stuck, evo 3d hboot 1.5, twrp 2.0,try to push adb, but its says device not found. i can boot into hboot and twrp but i cant get a rom to load so.. someone please help
hmm
ok so i figured out if i load into twrp and then do adb commands they work. installed new rom but it gets stuck at boot animation, any help would be great.
baloocifer said:
ok so i figured out if i load into twrp and then do adb commands they work. installed new rom but it gets stuck at boot animation, any help would be great.
Click to expand...
Click to collapse
Did you wiped everything before the flash ?
Sent From My RED 3Dimension
yeah i did wipe everything, and i did get roms to load, but everyrom that i try now gets to the actual rom and keeps giving me errors, like htc.bg process force close
did you follow the instructions on how to flash miui to a phone with hboot 1.5 or did you just do it blindly thinking it will work? if you didnt follow the instructions your kernel did not flash
plus you can always mount your sd-card in recovery to transfer a different ROM, zip, ect.......
I have tried a lot of different things. i have loaded into twrp pushed roms then fastboot load recovery then installing with twrp and i seem to get the same results with every different rom.
baloocifer said:
I have tried a lot of different things. i have loaded into twrp pushed roms then fastboot load recovery then installing with twrp and i seem to get the same results with every different rom.
Click to expand...
Click to collapse
What radios are you on software? You should stick with a rom that is built off the latest updates. I have been waiting on a rom to drop built off the latest software update. Are you on the latest software? If you try running old roms built off 2.3.3 and your kernel and radios are the latest you will have issues no matter what you do.
i think i may have been trying flash it all wrong i dont really know what i did right this time but i got it loaded so making a nandroid back up right now thanks for all your guys help
Hello , thank you for reading this. I'm trying to fix my amaze, it's stuck on the HTC boot logo. Phone was running latest tmobile rom, i unlocked the bootloader and rooted it to remove some tmobile bloatware using bloat freezer. Well the phone kept having these weird problems so i looked to install a custom rom. I installed clockworkmod recovery and then put my downloaded rom which was in a ZIP file onto the sd card. I booted into recovery, made a backup, then wiped data, then wiped dalvick cache or w/e it's called. wiped partition, then installed the ROM. the initial setup went good, phone said successful boot but when i restart it stays on the boot logo. So after some reading it looks like i didn't flash the kernel. So i found the boot.img file in the rom zip file but now i'm not sure what to do with it. I can boot into recovery but that is it. How can i flash the kernel with just clockwork recovery mod? Please help! I obviously would really like to get my phone up and running.
So as of now i have some custom roms on the SD card along with the OEM Ruby rom. I tried installing the tmobile stock ruby rom and it just says install aborted and it can not install. What should i do now? I juts want to get the phone working now. Thanks
Install 4ext recovery, it will flash the kernel for you, just make sure to turn on smartflash in the settings before you flash a rom if you're still S-On. If you're S-Off, then no need for smartflash
andy55 said:
Install 4ext recovery, it will flash the kernel for you, just make sure to turn on smartflash in the settings before you flash a rom if you're still S-On. If you're S-Off, then no need for smartflash
Click to expand...
Click to collapse
thank you. is there a way to install 4ext when the phone is just in recovery mode? my phone is just at the clockwork recovery main home screen right now. i can mount the drive and put files on the phone but that is it. thanks again
Okay so the tmobile stock rom is on the sd card. I renamed it to PH85IMG.zip and booted into hboot mode, it found the zip package and there was a loading bar. But then it went back to the boot screen. I tried restarting and it wouldn't move past the HTC quietly brilliant screen. I tried using the all in one tool kit to flash 4ext but it just keeps saying waiting for device. Pretty sure it wont work in clockworkmod recovery. Starting to get worried
NAIAmix said:
Okay so the tmobile stock rom is on the sd card. I renamed it to PH85IMG.zip and booted into hboot mode, it found the zip package and there was a loading bar. But then it went back to the boot screen. I tried restarting and it wouldn't move past the HTC quietly brilliant screen. I tried using the all in one tool kit to flash 4ext but it just keeps saying waiting for device. Pretty sure it wont work in clockworkmod recovery. Starting to get worried
Click to expand...
Click to collapse
Too flash the T-Mobile ruu you would have to relock your bootloader first.
As for flashing 4ext with the toolkit, when it said waiting device, were you in the bootloader, or did u select fastboot?
sent from my
NRGized amaze
powered by Faux
i think he was in recovery. ok so flash 4ext with the toolkit (i think you need to be in fastboot for the toolkit to flash it). then go to tools(in 4ext recovery) scroll down till the end and make sure smart flash is enabled (when it says enable smart flash means its not enabled and you need to click that, if it says disable smart flash then dont touch it you re good). then you can install a custom rom and it wont boot loop
hope this helps
hey guys thank you so much for taking time to help me! i got it flashed with 4ext and now using smartflash i'm able to flash roms onto it. so relieved to get it working, thanks again!
NAIAmix said:
hey guys thank you so much for taking time to help me! i got it flashed with 4ext and now using smartflash i'm able to flash roms onto it. so relieved to get it working, thanks again!
Click to expand...
Click to collapse
Thanks button working? I got u covered
Sent from my SGH-T999 using Tapatalk 2
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