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
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.
Hey guys,
I am doing this rom flash for a mate of mine.
I am trying to flash the tastyginger rom, but i am having some real difficulties while flashing the rom.
He has a dutch htc hero from hi. He has the latest rom according to the update utility thingy. it is the 2.1-update1 version. i believe i've read something about nand locks, and i think his phone has exactly that. the first step to flash a new rom is to root the phone. Rooting the phone works, gives no errors.
But when i try to flash the recovery image, it says it cant find the flash_image file.
it is should be located in the system folder on the phone but it isn't. i've tried to install it with android sdk, but the thing just is really acting weird. htc sync isn't working with the phone. it says there isn't a phone in the usb.
Now to make it clear, can somebody give me a clear tutorial on how to flash the thing correctly? I've done this before on my hd2. i've flashed the cyanogen 2.6 rom to my phone.
have you tried rom manager to flash rom its the easiest way i know. the way i rooted was with universal androot apk then installed rom manager clicked on flash clockworkmod recovery then went to install rom from sd card in rom manager scrolled down to the rom i wanted to flash choice it and pressed ok i then select backup existing rom and wipe data and cache and pressed ok then it will ask reboot and install and press ok and let it do its thing then wait untill it reboots and it should of installed rom which you wait to boot should have a custom splash screen that comes up and wait until your prompted to input details and such. hope this helps.
hey, thanks for the advice.
i let him try this method, but when he chose the htc hero gsm to install the cwm, the app refused to install it and gave this error message:An error occured while attempting to run privileged commands.
I forget to mention that the method you posted, that we already tried it.
But thanks for the effort!
pretty certain this is the tut. i used, i also had to use the gold card method -.-;
http://forum.xda-developers.com/showthread.php?t=645253
rom manager has been down lately everyone has had trouble flashing clockwork recovery, but ra recovery second from bottom is a secondary choice however other features of rom manager might not work if you use this you will have to boot into recovery manually.you also need super user to use this as well.
http://zenthought.org/content/project/flashrec
Use this apk, i have always used this method!
Download clockwork or ra recovery rename it to recovery.img and copy to sdcard
Backup recovery with flashrec
then type sdcard/recovery.img
flash recovery and done!
I've done the recovery succesfully at the guys phone. It works bloody well. Thanks dudes! You can lock it up if you want to.
Sent from my HTC HD2 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!
Is ROM Manager fully functional on this phone now? Just wondered if all of the options: CWM, Updates, Fix permissions, etc. are all working for folks - with no issues. Will it update to CWM Touch?
Thanks for any input.
im running touch flawless but i cant seem to download and go straight to recovery i have to manual but cwm is working fine
I posted a lengthy question earlier on this....for me, ROM Manager 6.0.1.5 (non touch) insatalls and seems to work fine, however when I try to do a backup of my current ROM it does not fully do it.
Uninstalling ROM Manager and flashing via fastboot the posted CWM recovery, I was able to do a successful Nandroid.
Just sucks not being able to use ROM Manager to backup your current ROM...for me at least.
At the Rom Manager Website I see both versions for the DNA:
http://www.clockworkmod.com/rommanager
It says the version number (for both) should be 6.0.1.5. Currently running 6.0.1.2 on my phone.
But on my phone, if I click on Flash ClockworkMod Recovery, it says Unsupported Device. Hmmmmm
Any update on this?
Is ROM Manager now supporting the DNA?
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.