[Q] using rommanager with alpharev recovery - Desire Q&A, Help & Troubleshooting

Hi
Just noticed, after installing the newest rom manager that I cannot use it.
It says I must have clockworkmod recovery installed.
I am using the alpharev version, and I do not intend to go back to CWM recovery...
is there anything I can do to disable this nuisance?

Symbiot78 said:
Hi
Just noticed, after installing the newest rom manager that I cannot use it.
It says I must have clockworkmod recovery installed.
I am using the alpharev version, and I do not intend to go back to CWM recovery...
is there anything I can do to disable this nuisance?
Click to expand...
Click to collapse
Don't use Rom Manager, it only (or mostly) causes trouble. If you have to flash, do it manually.

I have no problem with rom manager so far. Is there a way to flash the alpharev recovery? (in case I get some problems)

Please use the Q&A Forum for questions Thanks
Moving to Q&A

ROM manager both sucks and blows (and that's a difficult achievement).
If you want custom recovery look on my guide.

Related

Can't boot into ClockworkMod Recovery.

Haven't got enough posts to publish in the dev part of the forum and I can't find anyone with a DHD and this problem.
I'm on mike1986' Android Revolution HD 2.0.7 with senseless and trying to upgrade to 2.0.8 - with senseless.
I can't boot into ClockworkMod Recovery through Rom Manager or the boot menu (vol down at boot). Running 2.5.1.3 and it just hangs on the HTC screen. Tried flashing it twice from Rom Manager - no joy.
Looking for any advice - the rest of the phone runs fine btw.
Sent from my Desire HD using XDA App
Try to use the LASTEST version of CWM. i had this issues before coz i'm using the old version that i got from torrent. after i installed/ overwrite the old one, it works like charm! gud luck!
Cheers for the help, one question tho. As far as I am aware the latest CWM is 2.5.1.3. should I try using the "flash an older CWM" in Rom Manager?
All done, a massive thanks dude for the help.
Jambolia said:
Cheers for the help, one question tho. As far as I am aware the latest CWM is 2.5.1.3. should I try using the "flash an older CWM" in Rom Manager?
Click to expand...
Click to collapse
Well, this is what you need to check before u want it to works..
1. Firstly, NOT to update your phone with latest firmware that is 17.2/17.5 (this will not work for ALL attempt)
2. Root your phone - apps needed (superuser & VISIONary+)
3. ROM Manager (get the latest one and granted as superuser) with the right Flash CWM Recovery.
4. S-OFF (check on the pinned DHD Android development thread)
i think that's all.. other might add in some info if i got myself less on it.. thank you
I'd try flashing an older recovery and flashing back to the newest. Remember you can also get to recovery by switching off and charging.
Sent from my HTC Desire HD using XDA App

[Q] Most stable CM recovery

Hey, just a quick question;
the CyanogenMod 7 update guide states
'NOTE: the ClockworkMod version 2.5.0.7 installed by Unrevoked3 is widely reported not to work with new "PVT4" batches of the Desire. To find out version of the device: '
I have found this to be true, and two times have I had the problem of having a phone which cannot mount an sd card.
So, what is the most stable version of the recovery for my HTC Desire? In Rom Manager I have the options of versions 2.5.0.7, 2.5.1.3 and 2.5.1.1.
Thanks!
I'm currently using 3.0.0.5 I believe it is, works fine apart from it no longer supports the installation of ROM's/Mods that use the old style install-script.
CM 2.5.1.8 is most stable for me coz working fine, try this
Ok so if I want to use the new 3.0.0.5, all I need to do is download the .zip and flash it like I would a rom through recovery? I actually think I may be using AmonRa 2.0.1; Rom Manager is lying to me - so will i also be safe if I flashed it from AmonRa? Sorry for being cautious; I'm sick of the command prompt.
No. Using a zip file only fake flashes the recovery so it's only there for the one time and when you reboot it it's gone. You need to actually permanently flash the .img file. You need S-Off for this. You can use fastboot or the Android Flasher, either way is fine. Also Rom Manager is gay for the Desire. Don't use it. BTW, I'm using 3.0.0.5 built by Kali. I have the fake flash 2.5.0.7.zip file incase I need it.
Meaple said:
No. Using a zip file only fake flashes the recovery so it's only there for the one time and when you reboot it it's gone. You need to actually permanently flash the .img file. You need S-Off for this. You can use fastboot or the Android Flasher, either way is fine. Also Rom Manager is gay for the Desire. Don't use it. BTW, I'm using 3.0.0.5 built by Kali. I have the fake flash 2.5.0.7.zip file incase I need it.
Click to expand...
Click to collapse
Oh ok. Thanks, that was useful! I will probably stick with the recovery I have now and just not use Rom manager then (after all that may be the cause of my problems) , I'm not too keen on S-Offing right now.
So why would someone want to fake flash a recovery?

Unrevoked and install the original android recovery

Hi, I'm thinking about to root the phone with Unrevoked, but I don't want to lose the original android recovery,
1. is there a method to flash the original recovery instead of the Clockwork mod recovery?
because I like to use it with fake flash and it is the best way to use always the latest updated Clockwork.
not possible with unrevoked i belive.
but what's the problem ? just use it, you will get CWM 2.5.0.7 and keep a fake-flash.zip on sd and launch it from 2.5.0.7
No, I like to leave the original android recovery because are 2 times that I have to send him to assistance and I don't like to send it with a custom recovery.
dzumagos said:
not possible with unrevoked i belive.
but what's the problem ? just use it, you will get CWM 2.5.0.7 and keep a fake-flash.zip on sd and launch it from 2.5.0.7
Click to expand...
Click to collapse
Quick question out of curiosity: why is CWM 2.5.0.7 flashed on a GSM Desire by default? They're up to 3.2.0.0 at least. Is there something wrong with later versions?
Is a metod to reflash the original android recovery from clockwork mod recovery?
You can't use the stock recovery to flash a custom ROM so it's just not worth it. Keep the RUU for your phone for if you need to go back to stock
ninpoumike said:
Hi, I'm thinking about to root the phone with Unrevoked, but I don't want to lose the original android recovery,
1. is there a method to flash the original recovery instead of the Clockwork mod recovery?
because I like to use it with fake flash and it is the best way to use always the latest updated Clockwork.
Click to expand...
Click to collapse
Sorry not possible, because you cannot use fakeflash from the original unmodified recovery(it was made for the old root method, which modífied the recovery to allow test-keys, so even though it looked like the original HTC recovery, it weren't).
However you can easily just use fakeflash(via rommanager) even though you have clockwork mod installed as well. It'll just open the fake flash recovery instead when the update.zip is flashed, so just root normally using unrevoked.
Sintel said:
Quick question out of curiosity: why is CWM 2.5.0.7 flashed on a GSM Desire by default? They're up to 3.2.0.0 at least. Is there something wrong with later versions?
Click to expand...
Click to collapse
Newest clockworkmod version uses a newer script for flashing. Some developed things (roms, etc.) does not support this script yet. So one won't be able to flash things.

Cannot flash CWM 5.0.2.0 with rom manager in miui

Hello everyone,
i used to have rom manager and cwm 2.5.0.7 working fine under MIUI.Then i decided to replace the cwm files with the 4ext recovery.All went ok and i was able to fakeflash with rom manager and boot into 4ext until one i day i decided to fakeflash via rom manager the newest cwm 5.0.2.0 Although it says flashing complete when i try to reboot into recovery it gets me to the old 2.5.0.7
Any ideas?
Are you s-off? If yes, flash recovery via fastboot.
No, i m not
Actually i dont want to replace my permanent recovery.Just to be able to use the fakeflash version in rom manager!
Follow these instructions:
go to settings > applications > manage applications > ROM Manager > #uninstall#
End of all your problems. ROM Manager is a third party app that just causes problems, it is a lot safer to just boot into recovery manually (power off, hold volume down & power, use volume keys to navigate RECOVERY, press power to boot into recovery)
If you want to fakeflash through recovery, all you need is the recovery.zip, and fakeflash it like you'd flash a ROM.
Ivanovic said:
Hello everyone,
i used to have rom manager and cwm 2.5.0.7 working fine under MIUI.Then i decided to replace the cwm files with the 4ext recovery.All went ok and i was able to fakeflash with rom manager and boot into 4ext until one i day i decided to fakeflash via rom manager the newest cwm 5.0.2.0 Although it says flashing complete when i try to reboot into recovery it gets me to the old 2.5.0.7
Any ideas?
Click to expand...
Click to collapse
I agree with the other: dont use rom manager
anyway, u can't flash it beacuase the last version of rom manager do not use fakeflash anymore, it's need s-off now
so, u must s-off, then better if u flash it with fastboot, and use the recvoery manually
Thanks for the replies people
Nothing wrong with 2.5.0.7, it does the job. Remember to press the 'Thanks' button rather than just saying "thanks".
Offcourse its nothing wrong.But i used a fake flash version of 4ext recovery via rom manager thats why i started this thread.Because i m no longer able to fakeflash another recovery via rom manager.I know it can be done via permanent recovery.
Ivanovic said:
Offcourse its nothing wrong.But i used a fake flash version of 4ext recovery via rom manager thats why i started this thread.Because i m no longer able to fakeflash another recovery via rom manager.I know it can be done via permanent recovery.
Click to expand...
Click to collapse
as i said, latest rom manager does not support fakeflash anymore!
I had the same problem, then I go s-off and was able to flash recovery also via RomManager...
I believe ROM manager doesn't support fake flash on the desire as this was breaking many desires that had true flash versions of recovery.
It got so bad at Android forums, we had to create a thread warning people.
http://androidforums.com/desire-all-things-root/356192-warning-do-not-use-rom-manager.html
Anyway for me 2.5.0.7 is still my favourite recovery.
Don't really understand the need for ROM manager anymore. It made lots of sense before Unrevoked came along. Now it seems to me just helping the lazy get lazier (but of course this is just my opinion)
rootSU said:
ROM manager doesn't support fake flash on the desire as this was breaking many desires that had true flash versions of recovery.
It got so bad at Android forums, we had to create a thread warning people.
http://androidforums.com/desire-all-things-root/356192-warning-do-not-use-rom-manager.html
Anyway for me 2.5.0.7 is still my favourite recovery.
Don't really understand the need for ROM manager anymore. It made lots of sense before Unrevoked came along. Now it seems to me just helping the lazy get lazier (but of course this is just my opinion)
Click to expand...
Click to collapse
Created a thread in Desire General section with the same topic and linked to your post respectively to the one on androidforums.

Updgrading Clockwork mod

During the summer I rooted my phone and i have Clockworkmod v2.5.0.7 installed.
I am trying to upgrade to the latest version and it never seems to stick.
Using Rom manager. It says that im flashed to v5.0.2.0 yet when i boot to recovery from rom manager it loads to v2.5.0.7. Does the same thing if i choose to flash a rom though ROM MANAGER. each time v2XXX loads
So i fire up recover and try loading the zip. Bingo it works. The screen turns from green to blue and V5.0.2.0 is now there for me to use. But if i reboot and later return to recovery its back to the old V2xxxx..
Any ideas why this is happening? Is it really necessary to move on to the V5xxxx versions? I was going to try out some new roms and they failed to load yesterday through v2.5.0.7 yet the rom i had been using loaded fine.
Thanks in advance..
When you use Rom Manager to flash a rom or reboot into recovery from Rom Manager, it boots the recovery from a downloaded recovery file. It's known as fake flash or in other words, it's temporary. If you want a permanent recovery, you would need to flash a recovery.img through fastboot.
Meaple said:
When you use Rom Manager to flash a rom or reboot into recovery from Rom Manager, it boots the recovery from a downloaded recovery file. It's known as fake flash or in other words, it's temporary. If you want a permanent recovery, you would need to flash a recovery.img through fastboot.
Click to expand...
Click to collapse
if your Desire is s-off, then ROM Manager flashes recovery normally.
Sent from my HTC Desire using XDA App
rom manager now works only if u have s-off..no fake flash anymore is possible
revolutionary.io will upgrade cwm if you want
I think this thread answers one of my own questions but will ask it anyway to confirm; when I rooted my Desire (via Unrevoked) a few months back, the ROM Manager app that continues to be updated via the market offers the option to upgrade the version of CWM... is it OK to proceed with this?
I've been wary of upgrading from the version installed via the rooting process, just in case, but seeing this thread has made me think there isn't actually an issue with whatever version of recovery you have installed?
TKG26 said:
I was going to try out some new roms and they failed to load yesterday through v2.5.0.7 yet the rom i had been using loaded fine.
Click to expand...
Click to collapse
Out of curiosity - what roms you tried to load? As far as I know 2.5.0.7 was the last cwm supporting both amend and edify scripting and it never failed for me personally.
To upgrade recovery (or hboots) I always use Fastboot Commander and it's very easy to use and never let me down.
erklat said:
Out of curiosity - what roms you tried to load? As far as I know 2.5.0.7 was the last cwm supporting both amend and edify scripting and it never failed for me personally.
Click to expand...
Click to collapse
I agree. Unless you need to maintain an ext 4 partition (as 2.5.0.7 converts it to lower apparently when backing up) I see no reason to change from 2.5.0.7.
I use it even today. Best recovery IMHO.

Categories

Resources