Well I tried using Hasoon2000's tool and my HTC One will NOT boot into a custom recovery, it just reboots every time I tell it to boot into Recovery, whether I used the All-In-One Toolkit or not.
EDIT: I got it. I flashed the stock recovery image, then CWM, and it's working just fine now. Mod, feel free to delete this post (or not, up to you).
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.
Here's the situation:
I recently s-off'd my Legend (Bell Canada variant) in order to try out ogo2's NewSense ROM and do some metamorph stuff. I also attempted in install ClockworkMod 3.0.2.8 via the fastboot method which seemed to work just fine.
I used ogo2's NewSense beta 2 without any difficulty, but decided to switch back to CM7 via a backup I made earlier. No problems so far.
Here's the problem:
Yesterday I tried to flash beta 4, and this is where things got a bit weird.
When I use Rom Manager to try flashing beta 4, it loads ClockworkMod 2.5.0.7. Likewise, if I reboot into recovery from ROM Manager, I end up in ClockworkMod 2.5.0.7.
If, however, I manually boot into recovery then I end up in ClockworkMod 3.0.2.8.
I've tried flashing beta 4 manually and through ROM Manager and each time the ROM seems to install just fine but I end up stuck at the splash image. Naturally, I try to manually boot into recovery so I can restore, but it often just reboots or gets stuck at the splash image before CWM can load. Not a problem anymore.
I have to do a couple of battery pulls before I can sucessfully enter recovery (when I do, it's CWM 3.x).
Since then I've restored to CM7, but I can't flash beta 4 and the CWM disparity doesn't seem right to me. In otherwords, my phone is completely usable but CWM doesn't seem right.
Does anyone have any insight into this problem or a possible solution?
The issue lies in the way ROM Manager deals with recoveries. When the Legend was first given ROM Manager support S-OFF was a thing of dreams, we had to use the fakeflash method to get to CWM, so Koush made ROM Manager use fakeflash with some phones. Ours was one of them. When you "flash" a recovery using ROM Manager a fakeflash .zip is downloaded to your phone and stored somewhere, then using a method I don't fully understand ROM Manager reboots to recovery and "flashes" the fakeflash .zip. Now, because S-OFF we can flash recoveries to the recovery partition, but Koush hasn't updated his app to allow us to make use of it, nor has he made an updated version of CWM in fakeflash format for it. If someone cared enough they could probably get support for the latter at least. Because Koush hasn't updated his stuff to make use of new developments for our phone, ROM Manager assumes S-ON and still uses the fakeflash method, hence CWM 2.0.5.1 when using ROM Manager.
Thanks for the info. I was beginning to suspect something along those lines but it's always nice when someone who actually knows something about it gives an explanation.
I've seen on the Cyanogen forum that there is a fake flash 3.0.2.8. Anyone who can confirm this? I can't manage to get it to work :S
Sent from my HTC Legend using Tapatalk
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!
Not sure what I have going on to be honest. Unlocked and rooted via HTCDev/guide posted here, worked wonderfully. Kept stock rom but flashed a custom kernel to maintain root, noticed the camera didn't work afterward. Tried to flash a stock/rooted rom/kernel combo and no dice. At the moment I am only able to boot into the bootloader and enter fast boot, but I can't get into recovery, even tried different recoveries with the same effect, it boots into recovery for a split second then black screen, a minute later I'm stuck at the htc recovery loading screen. Has anyone experienced this, and is there a way to load a stock .img (not a recovery, but rom) through the cmd prompt? My searches have been unsuccessful thus far. Thanks in advance.
Why don't you flash the RUU?
Sent from my HTC One using Tapatalk 4
Try reflashing recovery via fastboot. Sounds like you recovery IMG got borked.
Sent from my HTC One using Tapatalk 4
Ok guys, Heres what I do & what happens,
(model # C6833)
1- root device
2- install new boot kernel (adv-stock-v4) (( Even tried v5))
3- unlock bootlader (only had to do it the first time, bootloader stays unlocked)
4- install cwm/TWiRP
5- get into TWIRP or CWM & wipe as I should
6- install rom. (It wont install)
7- reboot
8- stuck @ sony logo. & then reboots,
9- reinstall stock rom
This happens every time I try to install a rom.
I also get the message before I reboot, no root, would you like cmw/twirp to fix it, I go with yes. & ive tryed no as well. no difference. Still get stuck @ Sony logo & get reboot loop.
Any ideas ?
Im not new at rooting & roming.
Hey, it sounds like you're installing NUT's dual recovery and are trying to flash a CM/AOSP based ROM? I didn't find it possible to flash non-Sony ROMs using that recovery, myself. What you need to do is to first flash the kernel (boot.img) from the ROM you're trying to flash. You can do this using fastboot with the phone set to fastboot mode. The FlashTool program comes with what you need, and there's a guide to using it in the development forum. The kernel contains the recovery (either CWM or TWRP), so after flashing that, you can boot to recovery and install any CM/AOSP ROM you wish.
Triflot said:
Hey, it sounds like you're installing NUT's dual recovery and are trying to flash a CM/AOSP based ROM? I didn't find it possible to flash non-Sony ROMs using that recovery, myself. What you need to do is to first flash the kernel (boot.img) from the ROM you're trying to flash. You can do this using fastboot with the phone set to fastboot mode. The FlashTool program comes with what you need, and there's a guide to using it in the development forum. The kernel contains the recovery (either CWM or TWRP), so after flashing that, you can boot to recovery and install any CM/AOSP ROM you wish.
Click to expand...
Click to collapse
I did the flashtool thing. ( I'll edit my post ) I did the boot.img & Im trying to use SlimRom. Everything seems to be fine until I try & install the rom. Then it goes to hell.
Btw, Slimrom is compatable.
So what's the actual error message you get upon installing a ROM?
Something like, installation canceled. could not install rom. It goes threw a few steps. gets a few things installed (or so it seems) & then it hangs & I get that message. I thought, at first, it may have been a corrupt download. But after a few times of downloading it. I kinda think its no longer that.
Have you tried another ROM? Someone else is also having boot trouble with Slim in its development thread.
No actually, I have not. I will soon though now. And report back. First I need a stock U.S. rom. Just in case. Cant seem to find one.
Been using a CE (Central Europe) based stock rom.