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").
Could somebody kindly tell me how to boot into clockwork recovery? I've tried reboot into recovery from cm7s built in poweroff menu, Rom manager, and manually(both pressing down volume at start, or holding the nook-button at start). Searching google the only answer I found is pressing the n-button for two seconds while booting, but that doesn't work. Do you have to have some jedi-like timing to get into recovery? Doesn't matter what I do, I always end up cm7.
BrotherZero said:
Could somebody kindly tell me how to boot into clockwork recovery? I've tried reboot into recovery from cm7s built in poweroff menu, Rom manager, and manually(both pressing down volume at start, or holding the nook-button at start). Searching google the only answer I found is pressing the n-button for two seconds while booting, but that doesn't work. Do you have to have some jedi-like timing to get into recovery? Doesn't matter what I do, I always end up cm7.
Click to expand...
Click to collapse
No Jedi tricks.....I usually hold the n for a 6 count. Also, what version of recovery do you have? Current is 3.0.2.8. I had 3.0.1 do some flaky stuff the other day and had to flash current version
sent from my Ginger-Hero CDMA
Thanks for the reply.
Yeah, that seems to be it. If I go in to Rom Manager, it says I don't even have clockwork installed. So I can't even tell which clockwork I used!
I used this guide when I installed CM7
http://forum.xda-developers.com/showthread.php?t=1030227
So I should have installed Clockwork. A while since I did it, but going by my download map I used 3.0.1.0. But how should I flash the current version when I can't even access recovery?
Just use rom manager to flash the latest and greatest. Makes things a lot easier
BrotherZero said:
Thanks for the reply.
Yeah, that seems to be it. If I go in to Rom Manager, it says I don't even have clockwork installed. So I can't even tell which clockwork I used!
I used this guide when I installed CM7
http://forum.xda-developers.com/showthread.php?t=1030227
So I should have installed Clockwork. A while since I did it, but going by my download map I used 3.0.1.0. But how should I flash the current version when I can't even access recovery?
Click to expand...
Click to collapse
Like Ace said. Boot CM7, open Rom Manager and one of the 1st menu options is flash recovery. Use that and it will install recovery to EMMC.
sent from my Ginger-Hero CDMA
Thanks all. Usually I use cwm manually, wasn't aware of that Rom Manager made everything so easy. =)
OK, so I'm using ICS beta 4 for the Streak, and on ROM manager it says I have CWM 3.0.2. But when I try to boot into it, I either get stock recovery or fast boot. When I click on Software upgrade via update.pkg on SD card, on the stock recovery my screen turns blank and I have to hard reset.
Can someone help me get Clockwork Recovery please? Thanks!
PS. I used NVflash to flash ICS, don't know if that helps, but Im trying to provide sufficient information.
ICS B4 comes rooted with SuperUser7 and CWM 4.0.1.4 installed. Don't think that your supposed to use a ROM manager with it. Not sure how you have another CWM version unless you installed it yourself.
Reflash again and don't use the ROM manager app.
OK, well if it came with it, why can I not boot to it. I downloaded ROM manager but never used it. Never installed and other version of CWM, and if I did install another version, wouldn't I be able to see it? I can not boot to CWM.
Thanks for your suggestion, but reflashing is last option. Does anyone else think they know what's going on?
DO NOT USE ROM MANAGER!
First off, CWR isn't working very well right now, I have a new recovery image I've created that adds some functionality to recovery but its still a work in progress.
To get into recovery mode:
1) Power off device
2) Press Power and Volume+, hold
3) You will come into the Dell recovery menu
4) Use Volume (-) to get to "Install Package" and press Power to select
5) You are now in CWR
When I tried that it lagged a second and then booted normally. I'll post a video in a bit.
Oxymorphiend said:
When I tried that it lagged a second and then booted normally. I'll post a video in a bit.
Click to expand...
Click to collapse
Did you use ROM MANAGER and flash a recovery? If you did, recovery is hosed and you will have to fastboot flash the recovery from the B4 directory.
I did use rom manager. And where would I find it in the directory?
Oxymorphiend said:
I did use rom manager. And where would I find it in the directory?
Click to expand...
Click to collapse
Look in your ICS B4 download, you'll see "recovery.img" file.
Thank you both. I finally signed up when I had my first problem, and you guys hooked me up with speedy replies. Much appreciated.
Hey guys,
when I tried flashing CWM on my new HTC One it just booted in normal mode over and over.
I tried every recovery-image available and it nerver worked.
While playing around I finally got it working without flashing the recovery image to the boot partition!
No need to copy root files and CFW files before flashing the recovery!
Instructions
Unlock your device at http://www.htcdev.com/bootloader/
Reboot into bootloader
> fastboot flash boot boot.img - thanx to Paul O'Brien
> fastboot reboot-bootloader
> fastboot flash recovery recovery.img - thanks to Flyhalf205
> fastboot erase cache
After this you should be able to enter recovery via bootloader or 'adb reboot recovery'.
The recovery image is CWM Touch 6.0.2.8 which worked great for me, didn't try the other ones right now.
I hope I could help
I had issues booting recovery if I used the All in One kit to flash recovery.
So people should flash it manually instead to avoid problems.
Nekromantik said:
I had issues booting recovery if I used the All in One kit to flash recovery.
So people should flash it manually instead to avoid problems.
Click to expand...
Click to collapse
I had problems with AiO-Kit and doing it manually, too.
Only this method worked for me.
zantekk said:
I had problems with AiO-Kit and doing it manually, too.
Only this method worked for me.
Click to expand...
Click to collapse
Ah ok.
only issue for me now is aroma freeze issues.
Nekromantik said:
Ah ok.
only issue for me now is aroma freeze issues.
Click to expand...
Click to collapse
Didn't have that on my One until now.
I flashed my friend's One and it froze 3 times...then it worked.
I think it's recovery-related. Maybe wait for a fix.
zantekk said:
Didn't have that on my One until now.
I flashed my friend's One and it froze 3 times...then it worked.
I think it's recovery-related. Maybe wait for a fix.
Click to expand...
Click to collapse
It is AROMA related, amarullz have to update the binary
You can flash it 3 times or more, should work.
You can also use Hardware Buttons instead of Touch.. will help as well.
Device still rebooting
Can't flash recovery
same here - no access to recovery so far
Same for me too
Why ?
Got a HTC One from Orange france, and NO RECOVERY seems to stick. That thing boots, but i cannot enter recovery
I've tried using the AiO-Kit to flash CWM touch and normal as well as TWRP as well as the two CWMs manually and then this method. Still can't get access to recovery though
Try this? http://forum.xda-developers.com/showthread.php?t=2208029
Sent from my Nexus 4 using xda premium
Lothaen said:
Try this? http://forum.xda-developers.com/showthread.php?t=2208029
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
If you mean clearing the cache as mentioned in that thread I've tried it with no success
SoLdieR9312 said:
It is AROMA related, amarullz have to update the binary
You can flash it 3 times or more, should work.
You can also use Hardware Buttons instead of Touch.. will help as well.
Click to expand...
Click to collapse
Had the same problem again and again flashing TrickDroid on my HTC One (M7). Can confirm, that avoiding touch will relieve things but freezes can still occur. A few times I even could not reset the phone long-pressing the power + volume up buttons, means I was completely stuck on the frozen aroma screen (since a battery pull is not possible with this device). For anybody who may be in the same situation, try the "[FONT="Courier New]fastboot reboot[/FONT] command, this still came through and rebooted the device.
has this method worked for anyone else?
i'd like to try, but since i currently can't access recovery, i'm afraid to flash a new boot.img
pwr2wh8 said:
has this method worked for anyone else?
i'd like to try, but since i currently can't access recovery, i'm afraid to flash a new boot.img
Click to expand...
Click to collapse
Yes, worked for me. I had the same issue. While flashing Renovate rom, Aroma crapped out right at the end where it was installing the kernel. I was then stuck on boot image until i found this thread.
Also, for what it's worth, i thought I'd flash the boot image again after i got my device running again but it killed my wifi. I had to reflash the rom as wifi in settings was `out of order`....
//edit: okay. i've been able to reproduce the crashing. seems it's an aroma/rom issue (i couldn't tell one way or the other). what matters here is flashing boot image with the provided image does the trick. whatever magic it does, i'm able to flash cwm recovery 6.0.3.1 but I have to flash boot image before, else flashing recovery is fruitless.
anyways, thanks. this thread help me solve what i thought was `bricked` device.