Related
Grab it here:
General: http://koush.tandtgaming.com/recoveries/
Direct Link: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.4-inc.img
Use unrEVOked v3.1 to flash custom recoveries (at your own risk, of course)
1) Download
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.4-inc.img
2) DO NOT PLUG IN YOUR PHONE
3) Run unrEVOked v3.1
4) Under FILE choose CUSTOM RECOVERY
5) Point to the img file
6) Plug in your phone
Updated, no issues. Thanks!
Thanks. I updated without issue.
is it better than the old?
Sent from my Incredible using XDA App
jdkoreclipse said:
is it better than the old?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Yes.. it's 0.0.0.3 times better than the old!
If you rooted with unrevoked 3.0 can you just use that with this image?
Sent from my Droid Incredible using the XDA App
Flashed to 2.5.0.4 no problem. But ROM Manager still indicates 2.5.0.1 is installed.
So how do I get ROM Manager to indicate the right recovery version?
UPDATE: Just after I posted this...I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?
i don't really see a point in updating since it already works for me now...
rom manager reports the older version for me, but booting into recovery it is reporting the newest .4 version
Lexus One said:
Flashed to 2.5.0.4 no problem. But ROM Manager still indicates 2.5.0.1 is installed.
So how do I get ROM Manager to indicate the right recovery version?
UPDATE: Just after I posted this...I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?
Click to expand...
Click to collapse
ROM Manager cannot flash recovery because NAND is still locked. Only through the unrevoked tool does NAND temporarily unlock in order to flash clockwork. So if you followed the steps correctly using the unrevoked tool then you have the correct version. Booting into recovery (I think you can't boot through ROM Manager, boot manually or via boot loader) should show the updated version.
Lexus One said:
I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?
Click to expand...
Click to collapse
Boot into recovery via ROM Manager. Note the version. Then boot into recovery "manually" (hold volume down while powering on). Note the version again. Notice anything different?
elborak said:
Boot into recovery via ROM Manager. Note the version. Then boot into recovery "manually" (hold volume down while powering on). Note the version again. Notice anything different?
Click to expand...
Click to collapse
recovery by ROM Manager I get 2.5.0.1
recovery by vdown & Pon I get 2.5.0.4
Thanks, now I'm confused even more. Why are they different? And when I go back into ROM Manager it still reports 2.5.0.1. So my original question still stands: How do I get ROM Manager to display the correct version of recovery which is really 2.5.0.4? Even more...why does the recovery manager report 2.5.0.1 when booting into recovery via ROM Manager? This is reallyyyy strange!
I answered your question two posts back...
s197 said:
I answered your question two posts back...
Click to expand...
Click to collapse
Thanks for responding. I understand. But that doesn't answer my question about how to get ROM Manager to report the correct version. Do you know the answer to this?
What is even more confusing is when I boot into ClockworkMod recovery from the ROM Manager and the version of ClockworkMod Recovery is reported on screen as 2.5.0.1 when it is really 2.5.0.4....this just blows me away! It is like ROM Manager is substituting its own version number into the newer version of recovery.
Lexus One said:
Thanks for responding. I understand. But that doesn't answer my question about how to get ROM Manager to report the correct version. Do you know the answer to this?
What is even more confusing is when I boot into ClockworkMod recovery from the ROM Manager and the version of ClockworkMod Recovery is reported on screen as 2.5.0.1 when it is really 2.5.0.4....this just blows me away! It is like ROM Manager is substituting its own version number into the newer version of recovery.
Click to expand...
Click to collapse
If i understand this correctly: The version that ROM Manager reports and boots into is actually a virtual version. This is because, due to the fact that NAND isn't unlocked yet ROM manager can't actually write to it, So when it is "flashing the recovery" it really is only flashing a "virtual recovery". This is why you could on some phones have an older version of recovery flashed and ROM manager would report a newer version that is available.
In short to answer your question, you can't get ROM manager to report the newer version until rom manager has that newer version in it's list, which it currently does not. And even when it is in the list it makes no difference anyway, because unless you boot into recovery using the power button and volume button, the recovery that you boot into will be a virtual one anyway.... so it really makes no difference what ROM Manager is reporting.
And if i am incorrect in my understanding then, disregard all of this but i remember another post with all this in it.
obsidianblackhawk said:
<snip> And if i am incorrect in my understanding then, disregard all of this but i remember another post with all this in it.
Click to expand...
Click to collapse
Thanks. I appreciate your feedback on this. It would explain why I am seeing a different version for the ROM Manager. What I still don't understand is why ROM Manager misleads you into thinking you are booting to the recovery partition. I mean, why even have an option in the program to "Reboot into Recovery" if you are really NOT booting into the recovery partition, but rather a virtual recovery. So, what would happen if you tried to use the virtual recovery as opposed to the real recovery (which in this case is a different version)? Anyone know, or have tried it?
Lexus One said:
Thanks. I appreciate your feedback on this. It would explain why I am seeing a different version for the ROM Manager. What I still don't understand is why ROM Manager misleads you into thinking you are booting to the recovery partition. I mean, why even have an option in the program to "Reboot into Recovery" if you are really NOT booting into the recovery partition, but rather a virtual recovery. So, what would happen if you tried to use the virtual recovery as opposed to the real recovery (which in this case is a different version)? Anyone know, or have tried it?
Click to expand...
Click to collapse
other than flashing a new recovery, the recovery that rom manager boots into works exactly the same as the "real one" in fact i don;t do it the "hard way" any more.
This is probably a dumb question but do I open the img file after I plug in the phone?
Lexus One said:
how to get ROM Manager to report the correct version.
Click to expand...
Click to collapse
Easiest way is this:
1) Uninstall ROM Manager.
2) Reinstall ROM Manager.
ROM Manager will now display no version, as opposed to the wrong version.
And then...
Never again use the "Flash ClockworkMod Recovery" command in ROM Manager. If you want to update recovery, use the unrevoked flasher with the custom recovery option.
Changes?...
Solved!
Hi,
I have SLCD Nexus one(2.2) and I want to install custom rom.
But it shows black screen because it's not OLED.
Solved!! - Most custom roms having new kernels work, if it doesn't have new kernel installing new kernel works!
I've got the same problem. I even tried brute force, because I got everything working but got stuck on a black screen recovery, which I tried to get working for hours. I thought it might be the new rom or the new hboot, so I flashed a new image via fastboot. Now I'm stuck at a black screen os (thank god fastboot still works) - but I'd need a stock slcd rom to get back to where I started.
Could someone be so kind and upload an slcd rom? Or even better some slcd custom recovery+slcd+new hboot compliant custom rom?
I think, that a lot of people will get in this trap, because there are no warnings, that even the newest cm/ra_recovery won't work on a new nexus one.
Thanks in advance.
Update: Solved on my own. Now I'm just waiting for some slcd recovery + mod. ;-)
This is Amon Ra's Nexus One SLCD recovery dl.dropbox.com/u/4481275/recovery-RA-nexus-v1.8.0.1-aw.img
Well, at least be glad that fixing a dark Nexus One is probably much easier than fixing a dark HTC Desire!
I suggest this sequence if you have an SLCD N1:
1) Root first, then load ROM Manager
2) Install custom recovery but keep your ROM for now. Boot into recovery. If it's dark, wrong recovery - try again.
3) ONLY once you have a working recovery should you even think about trying other ROMs. And don't forget to take a full nandroid backup first. You should be able to restore that backup safely from recovery.
Zorr0theOne said:
This is Amon Ra's Nexus One SLCD recovery dl.dropbox.com/u/4481275/recovery-RA-nexus-v1.8.0.1-aw.img
Click to expand...
Click to collapse
Thanks, but I'm asking for custom rom, not recovery.
Anyway, thank you very much.
cmstlist said:
Well, at least be glad that fixing a dark Nexus One is probably much easier than fixing a dark HTC Desire!
I suggest this sequence if you have an SLCD N1:
1) Root first, then load ROM Manager
2) Install custom recovery but keep your ROM for now. Boot into recovery. If it's dark, wrong recovery - try again.
3) ONLY once you have a working recovery should you even think about trying other ROMs. And don't forget to take a full nandroid backup first. You should be able to restore that backup safely from recovery.
Click to expand...
Click to collapse
Thanks, but I'm asking for custom rom, not fix. (I already fixed it)
Anyway, thank you very much.
i have same problem as wisechild but u said u have fixed it and just waiting for custom rom if so how did u fix it. i no the recovery works in the background, when the screen is dark cause if u do a backup in rom manager and let it run despite dark screen it shows up when u go back to rom manager. the trouble is i have the hboot 0017 instead of 0012 so can't install cm roms. is there a rom that works with that hboot.
found solution, the latest Kang-o-rama rom work with the korean hboot 0.35.0017 . Installed it using rom manager install from sdcard option. despite not being able to see the recovery screen just let it run for like 5 mins then it reboots and u got a custom rom.
aljnbaptiste said:
found solution, the latest Kang-o-rama rom work with the korean hboot 0.35.0017 . Installed it using rom manager install from sdcard option. despite not being able to see the recovery screen just let it run for like 5 mins then it reboots and u got a custom rom.
Click to expand...
Click to collapse
Thanks, but I'll wait for custom rom supporting FM(ie NXSense).
Anyway thank you very much.
If you'd like a specific ROM to support SLCD, best to request this directly on the thread for that ROM.
I wonder if there is a component which can be swapped in easily to provide SLCD support?
wisechild said:
Solved!
Solved!! - Most custom roms having new kernels work, if it doesn't have new kernel installing new kernel works!
Click to expand...
Click to collapse
Can you verify with a ROM like CM6 or Evil Sense.
Please, do tell us how you implemented a fix .
Hmm
Can anyone help please?
I previously flashed an old Amon Ra recovery onto my N1 SLCD & suffered the blank screen fate. Since rooted with universal androot and tried to copy over and flash using adb shell (for some reason fastboot flash recovery doesn't seem to work - i still get the blank screen). However, adb shell denies permission to become su even though following root i can become su using terminal emulator on the phone ... Anyone have any ideas?
rob_2010 said:
Can anyone help please?
I previously flashed an old Amon Ra recovery onto my N1 SLCD & suffered the blank screen fate. Since rooted with universal androot and tried to copy over and flash using adb shell (for some reason fastboot flash recovery doesn't seem to work - i still get the blank screen). However, adb shell denies permission to become su even though following root i can become su using terminal emulator on the phone ... Anyone have any ideas?
Click to expand...
Click to collapse
I think fastboot flash recovery requires an unlocked bootloader.
With adb shell you have to type su and then, on the phone, look for the permissions dialog to come up. After you accept, it will give you a root shell. If it's not asking you for the permissions, I'm not sure what else to do.
I think you could also conceivably run flash_image from the terminal emulator as root and flash the correct recovery that way.
shundi82 said:
I've got the same problem. I even tried brute force, because I got everything working but got stuck on a black screen recovery, which I tried to get working for hours. I thought it might be the new rom or the new hboot, so I flashed a new image via fastboot. Now I'm stuck at a black screen os (thank god fastboot still works) - but I'd need a stock slcd rom to get back to where I started.
Could someone be so kind and upload an slcd rom? Or even better some slcd custom recovery+slcd+new hboot compliant custom rom?
I think, that a lot of people will get in this trap, because there are no warnings, that even the newest cm/ra_recovery won't work on a new nexus one.
Thanks in advance.
Update: Solved on my own. Now I'm just waiting for some slcd recovery + mod. ;-)
Click to expand...
Click to collapse
how did you solve the problem, i'm stuck with a blank screen os also the keys light up and work but no screen
Flash AmonRa's 1.8.0.1 recovery that supports SLCD, and then flash any ROM you like - most of them support SLCD now, and if you see that the one you flashed doesn't - flash another.
Jack_R1 said:
Flash AmonRa's 1.8.0.1 recovery that supports SLCD, and then flash any ROM you like - most of them support SLCD now, and if you see that the one you flashed doesn't - flash another.
Click to expand...
Click to collapse
cant really troubleshoot now cause i'm at work but how would i be able to enable usb debugging if i cant see the screen?
You couldn't get stuck in ROM if you flashed a recovery that doesn't support SLCD, because you wouldn't be able to install ROM without it - and you couldn't get stuck without ROM if you only flashed a recovery that doesn't support SLCD. So one of them should be working for you, and enable to make the other work.
That is unless you used ROM manager, which flashed the recovery for you and did all the stuff - and it didn't show anything, because Clockwork recovery doesn't support SLCD (so you would get your ROM installed for you and not see it, and then you'd get stuck with a ROM that doesn't support SLCD).
If that's the case, run the recovery and try to connect ADB (recovery runs ADB interface).
Jack_R1 said:
You couldn't get stuck in ROM if you flashed a recovery that doesn't support SLCD, because you wouldn't be able to install ROM without it - and you couldn't get stuck without ROM if you only flashed a recovery that doesn't support SLCD. So one of them should be working for you, and enable to make the other work.
That is unless you used ROM manager, which flashed the recovery for you and did all the stuff - and it didn't show anything, because Clockwork recovery doesn't support SLCD (so you would get your ROM installed for you and not see it, and then you'd get stuck with a ROM that doesn't support SLCD).
If that's the case, run the recovery and try to connect ADB (recovery runs ADB interface).
Click to expand...
Click to collapse
that was the case. i'll try in a few hours when i get home. once i'm in adb i would try to flash amon ra's recovery and start over correct?
Indeed, correct.
Use recovery flashing guide from Wiki. If you're rooted without unlocking - follow the "flash_image method" guide. If you find out that you need to install busybox - download the APK and install using ADB, instead of downloading from the Market.
I wrote this how-to, I think it might help you.
h**p://forum.xda-developers.com/showthread.php?t=785581
cestbibi said:
I wrote this how-to, I think it might help you.
http://forum.xda-developers.com/showthread.php?t=785581
Click to expand...
Click to collapse
It's essentially the same guide as in Wiki, but executed through ADB - which is good. I'll add your guide to the Wiki for reference, with a link. I saw, it doesn't require Busybox (uses "cat >" instead of "cp").
Hi
I have N1 and I want to install the best recovery
so which recovery you suggest me to put in it
and thank you
Amon or Clockwork.....
There is no "best", just try and see which one suits you the most...For me, it's definitely Amon_Ra.
i tried Clockwork but i didnt like it
Amon_Ra is awusome
Clockwork works great for me!
OK, why don't we discuss why we prefer the recovery we use...
I prefer Clockworkmod because it works with ROM Manager. Amon Ra doesn't...
Also, Clockworkmod lets you browse through sub-folders when flashing zips. I haven't used Amon for a while, so I don't know if this feature has been added in the newer version?
Also, I've noticed possible install issues between Amon and the 0.35 hboot.
I've no idea what Amon can do better than Clockworkmod?
Sent from my Nexus One using XDA App
danger-rat said:
OK, why don't we discuss why we prefer the recovery we use...
I prefer Clockworkmod because it works with ROM Manager. Amon Ra doesn't...
Also, Clockworkmod lets you browse through sub-folders when flashing zips. I haven't used Amon for a while, so I don't know if this feature has been added in the newer version?
Also, I've noticed possible install issues between Amon and the 0.35 hboot.
I've no idea what Amon can do better than Clockworkmod?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I don't like my recovery being controller in-OS, Amon_Ra allows browsing through folder too. Also, I have 0.35 hboot (I have an SLCD nexus) and had issues installing the newest Amon_Ra CM themed, but the normal version worked just fine.
It's not so much a matter of which does more than the other, just preference! Not bashing anyone, both Amon_Ra and Koush are doing great work and we all have to thank them for that, because they allowed our Nexus to flash some super awesome custom ROMs
As long as it flashes (unsigned), does NAND backups/restore and wipes, you're fine.
I agree, it is preference.
If Amon worked with ROM Manager, I'd probably be using it too...
Sent from my Nexus One using XDA App
I prefer Amon, especially with the 2.0 update that added the ability to select a .zip from within folders. I had some poor experiences with clockwork corrupting nandroid backups, and haven't had the same experience with Amon's.
Does anyone know how I can revert my current CWM 3.0 back to an earlier version? 3.0+ doesn't support flashing zips in recovery.
Thanks
justsignbythex said:
Does anyone know how I can revert my current CWM 3.0 back to an earlier version? 3.0+ doesn't support flashing zips in recovery.
Thanks
Click to expand...
Click to collapse
uhhh... it doesnt?
Bottom of the rom manager menu. "flash alternative recoveries" i believe.
liam.lah said:
Bottom of the rom manager menu. "flash alternative recoveries" i believe.
Click to expand...
Click to collapse
no i think he means like flashing a zip'd rom or kernel other than update.zip?
and you most certainly can flash a zip in recovery... i just did it 2 seconds ago and im on 3.0.0.5
liam.lah said:
Bottom of the rom manager menu. "flash alternative recoveries" i believe.
Click to expand...
Click to collapse
Did not see this at all.
Thanks!
I tried flashing a newer radio earlier through recovery (update.zip), but it would say something about not being able to do it anymore (forgot the exact phrasing). Something about Edify scripting and Gingerbread.
The newer ClockworkMod recoveries have dropped support for the old Amend scripted .zip files is all.
Rusty! said:
The newer ClockworkMod recoveries have dropped support for the old Amend scripted .zip files is all.
Click to expand...
Click to collapse
So we shouldn't update CWM recovery to the lastest version to flash roms or make backups? Rather stick with an older version from the bottom of the menu?
Ive been keeping with an older version but just want some clarification if i can update to lastest CWM version?
Depends. Most newer updates are being made in Edify now (install-binary & updater-script), so you'll mostly be OK.
But if you do want to use things with Amend then it's either older CWM or Amon Ra recoveries for you.
It says that i need to update a script or something and something about android 1.5. I'm currently on the cm 7 nightly #21. I've tried various sense roms like fresh rom 2.4, espresso hero, etc. If i go to rom manager, it says the clockworkmod recovery is 2.5.0.7 even though it says 3.0.0.5 if i go to recovery. Don't really know what to do so if you know what to do, please reply.
Mobiono said:
It says that i need to update a script or something and something about android 1.5. I'm currently on the cm 7 nightly #21. I've tried various sense roms like fresh rom 2.4, espresso hero, etc. If i go to rom manager, it says the clockworkmod recovery is 2.5.0.7 even though it says 3.0.0.5 if i go to recovery. Don't really know what to do so if you know what to do, please reply.
Click to expand...
Click to collapse
Those ROMs must be using amend scripts and the latest recovery uses edify. There are a few things you could do:
1. Flash an older recovery - CWM 2x or RA 1.x and then flash the ROM
2. Update the scripts to edify and then flash the ROM
andythegreenguy said:
Those ROMs must be using amend scripts and the latest recovery uses edify. There are a few things you could do:
1. Flash an older recovery - CWM 2x or RA 1.x and then flash the ROM
2. Update the scripts to edify and then flash the ROM
Click to expand...
Click to collapse
Would you happen to have a copy of a CWM 2x ? I've been looking for the link since you posted.
Mobiono said:
Would you happen to have a copy of a CWM 2x ? I've been looking for the link since you posted.
Click to expand...
Click to collapse
just go to rom manager and tell it to flash ClockworkMod Recovery and it should install the 2.5 version..
pstevep said:
just go to rom manager and tell it to flash ClockworkMod Recovery and it should install the 2.5 version..
Click to expand...
Click to collapse
I'm getting errors trying to flash every version besides 2.5.1. How do i kill 3.0.0.5 and replace it? Its weird since on rom manager, it says I'm on 2.5.0.7 but when i actually go to recovery, its says its 3.0.0.5.
I don't have any problems flashing sense . Id try uninstalling and installing again from market not through TB.
Sent from my HERO200 using XDA App
Mobiono said:
I'm getting errors trying to flash every version besides 2.5.1. How do i kill 3.0.0.5 and replace it? Its weird since on rom manager, it says I'm on 2.5.0.7 but when i actually go to recovery, its says its 3.0.0.5.
Click to expand...
Click to collapse
In Rom Manager scroll down to the bottom and select flash alternate recovery then scroll to the top and select flash Clockwork Mod recovery. Should be good to go after that
Sent from my HTC Hero CDMA using XDA App
Use method 2 from the ROMRepo. The only difference is is that if you have the latest ROM Manager, the folder that has the newest recovery image will be mirror.kanged.net. That's how I'm able to flash the different images. Edit the recoveries in that folder.
It wont allow me to post the link so just grab it from the OP of the aospCMod ROM.
Sent from my HTC Hero CDMA using XDA App
Mobiono said:
It says that i need to update a script or something and something about android 1.5. I'm currently on the cm 7 nightly #21. I've tried various sense roms like fresh rom 2.4, espresso hero, etc. If i go to rom manager, it says the clockworkmod recovery is 2.5.0.7 even though it says 3.0.0.5 if i go to recovery. Don't really know what to do so if you know what to do, please reply.
Click to expand...
Click to collapse
I don't like flashing Sense roms from CW and my phone doesn't either. Usually what I'll do is since I'm on CW 3.0.1.9 I just make a backup of what I want to keep on my PC, wipe everything including the /recovery option and flash RA's recovery. For ME, it seems to work better these days. Many months ago when my Hero was still fresh I could flash everything. At least it overclocks to 807 without an issue.
Oh btw, if you run a google for "RA recovery heroc" you'll find it. Info on flashing a recovery is everywhere within XDA, after a while you just remember these things