Hi,
I recently rooted my HTC Desire with unrevoked 3.32. This gave me root but not S-OFF with Clockworkmod recovery 2.5.0.7
As I've not updated to a custom ROM before I initially wanted to leave the phone as s-on for the added security that gives against malicious software (at least until I was more comfortable that I fully understood the risks).
I then installed ROM Manager 4.7.0.4. It asked me to install clockworkmod recovery (CWM), claiming that there was no CWM installed. ROM manager appeared to install 5.0.2.0 of CWM. However the phone didn't boot into CWM 5.0.2.0 it still booted into 2.5.0.7
Reading around a bit I believe that ROM manager uses fake-flash to load updated versions of CWM when a phone is S-ON. This appears to have failed in my case ROM manager thought it had installed the new CWM but in fact still rebooted into the older version.
This meant that attempting any updates with ROM manager failed. I gave up and used revolutionary to gain s-off, ROM manager then worked as expected.
Is there any official place to report problems with ROM manager? I think this is a bug and would like to notify the author.
If I'm at fault please let me know what I did wrong.
regards,
gbdrbob
Related
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
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
It seems CF-Root v4.1 is the bees-knees when it comes to rooting the Galaxy S II, but unfortunately it is not ROM Manager compatible.
Is there an up to date method to root the SGSII that works with Rom Manager? I found this link: http://www.inspiredgeek.com/2011/04...ng-odin-and-superoneclick-step-by-step-guide/ but I suspect there may be a newer method.
Here are my phone details, just in case:
Android version: 2.3.3
Baseband version: I9100XXKE7
Kernel version: 2.6.35.7-I9100XWKF3-CL276555
bump......
Why don't you just install ROM Manager, then download latest clockwork recovery using ROM Manager?
It will then be ROM Manager compatible.
Because I need to attain root before I can flash clockworkmod. ROM Manager says "An error occurred while attempting to run privileged commands"
I'm on the original galaxy and the easiest way I've found to root is to use odin or hemindall to flash a kernel with cwm. It roots and gives cwm in one action. Also theres a new super one click that I've had success with on many different brands of phones, hts, lg, moto
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
What I meant is, why don't you just flash CF-Kernel, then install ROM manager, then use that to install clockwork recovery.
There is a confusion that rom manager is not compatible with the kernel. That part is not true, rom manager is not compatible with the clockwork recovery that is supplied by the kernel, you just use the clockwork recovery that can be installed with rom manager. The cwm app is not compatible with the recovery installed by rom manager.
Flash codeworkx kernel, root it, and run rom manager to your hearts content.
I'm having this issue too.
I've spent most of the day trying different things.
Regardless of how I root, and what rom and kernel provides the base when I try and update cwm through rom manager then try and reboot into recovery through rom manager I get the failed to verify error.
I've rooted with the chainfire root, with codeworx kernal and then superone click, and it's made no difference.
I've also tried it from rooted stock firmwares, and custom roms.
Still cannot boot into recovery from rom manager.
I've also noticed that despite rom manager saying that I'm using the latest version, when I manually boot into cwm it shows the previous version.
edit: I even went back to stock and rooted using link in first post, then installed rom manager but same error.
Keeps going to 3e system recovery
God it's annoying
Further googling has led me to believe the issue is rom managers not being compatible with 3e recovery.
Apparently we need to have 2e recovery.
Any way to get that?
edit: Or can we disable signature verification in cwm?
re-edit: Well I found this in the cf root thread which will explain why I will never get rom manager to work
CF-Root includes a custom version of CWM4. I always make custom versions, as the originals often do not take some Samsung specific things into account.
CF-Root/CWM4 is NOT compatible with ROM Manager! Manage/perform your backup/restores from CWM directly or using the CWM Manager application included with CF-Root
Where is the standard version then?
peachpuff said:
Flash codeworkx kernel, root it, and run rom manager to your hearts content.
Click to expand...
Click to collapse
Codeworx said himself that his kernel won't work with rom manager.
If anyone is able to install roms through rom manager I'd like to know what rom, kernal, and how they rooted.
JGS2 said:
Codeworx said himself that his kernel won't work with rom manager.
If anyone is able to install roms through rom manager I'd like to know what rom, kernal, and how they rooted.
Click to expand...
Click to collapse
Haven't read that thread but i thought that was the whole point of his kernel, oh well.
Well I finally found a fix.
This time I can boot into recovery from rom manager.
No more failed to verify errors
What you need is this version of clockwork recovery
http://www.multiupload.com/UUX5P7QTU0
Flash it with odin, then use superoneclick version 1.95.
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.