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?
Related
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
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
When I try to download the ROM from ROM manager, it tells me that I need install Clockworkmod Recovery, but when I pressed install, it came up with a Confirm Phone Model page which does not have Galaxy 5 as a option. So I am now just stuck here, what should I do, or is the free version of ROM manager pure not very useful?
hozza94 said:
When I try to download the ROM from ROM manager, it tells me that I need install Clockworkmod Recovery, but when I pressed install, it came up with a Confirm Phone Model page which does not have Galaxy 5 as a option. So I am now just stuck here, what should I do, or is the free version of ROM manager pure not very useful?
Click to expand...
Click to collapse
did you root your phone?
what rom are you actually using?
did you try to update Rom Manager to an earlier version?
I assume your phone is rooted already. Don't continue if it's not.
I thought there was an official one released for the phone. Are you using the newest version of ROM Manager?
If yes, and our phone model is still not listed, then you'll need to install Clockworkmod Recovery by following this thread:
http://forum.xda-developers.com/showthread.php?t=1151396
It involves downloading a program called ODIN. You need to flash (transfer) the Clockworkmod file to your phone through USB. It's all in the thread above.
I had the same problem - installing the latest Rom Manager (free version) from the store didn't have Galaxy5 listed as a ClockworkMod possibility.
I flashed the whole thing by hand with ODIN and installed CyanogenMod - and presto; the version supplied with it had Galaxy5 support and I had no problem doing the "read only partition" installation.
Rom Manager is pretty crappy anyway - I prefer manual installation over it...
DO NOT - i repeat - DO NOT USE ROM MANAGER.
Theres no compatible version of CWMR it does offer. Flashing any of the other versions, which are made for other phones, might brick your device to the state that Im currently trying to revert (d/l mode only, but seemingly unflashable).
Rigardi said:
DO NOT - i repeat - DO NOT USE ROM MANAGER.
Theres no compatible version of CWMR it does offer. Flashing any of the other versions, which are made for other phones, might brick your device to the state that Im currently trying to revert (d/l mode only, but seemingly unflashable).
Click to expand...
Click to collapse
Why did you say that??? If the phone is rooted you can download CWM by RomManager without fear.. the important is that when the popup with phones versions come up, you choose only - ONLY! - Galaxy 5 voice! If this voice is not present into the popup, don't choose nothing at all! Choosing another phone might brick yours!
I downloaded and installed and even only update CWM by RomManager a lot of times and everything was always fine! No problem at all!!
You cannot scare people for nothing: your problems are not bug or issues, but only YOUR problems! and YOUR errors!!!
So, boyz, don't worry installing CWM by RomManager.. but remember to choose only Galaxy 5 voice, no other phone, 'cause you could brick your phone selecting a CWM that is not compatible with our GT-I5500..
I've tried installing ClockworkMod via ROM Manager, and it seemed to work. But when I booted in recovery mode it was still the default android recovery. I downloaded ClockworkMod Touch and it installed fine (was able to use it after it installed), but once again when I rebooted it was android recovery.
I've searched around but can't find anything...am I supposed to set CWM as the default somehow, or...?
SunshineCat said:
I've tried installing ClockworkMod via ROM Manager, and it seemed to work. But when I booted in recovery mode it was still the default android recovery. I downloaded ClockworkMod Touch and it installed fine (was able to use it after it installed), but once again when I rebooted it was android recovery.
I've searched around but can't find anything...am I supposed to set CWM as the default somehow, or...?
Click to expand...
Click to collapse
Rom manager does not fully support SGS2. So do not use it. You cant install a permanent recovery by flashing zip files in stock recovery. Which will only give you a temporary recovery which you will loose after rebooting. If you are on ICS 4.0.4 do not wipe anything in stock recovery. Give more info about what android version you are running on. If you are on ICS flash siyah kernel v5 using odin. Then you will get root and a safe kernel which has proper recovery
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.