Database Develop

A Request for the Unrevoked Team

I don't want to jump on IRC and I don't know where else to post this, but I have a small request, if possible. Can you fine folks make the recovery flasher so that you can add your own updated recovery images? Currently, the flasher only only installs clockwork 2.0.1.0 and there is a version 2.0.1.3 available, but no way to make it stick.

Install ROM Manager from Koush on the android market, and update your recovery that way.

It does not stick. Please read my post. Its easy enough for you to check yourself. I have Rom Manager already. It cannot work any magic. Once you reboot, you are back to the original version that the recovery flasher puts on there.

really? mine works great....

Boot into clockwork and look at the version number. No, it does not.
Rom Manager thinks its flashing an updated version, but thats not the case.

Look... I am not a liar, and don't appreciate being called a liar. I am just trying to help you. In my ROM Manager it says current and latest is 2.0.1.3. In my Clockwork Recovery it says version 2.0.1.3. I have restarted it three times into recovery, and it says the same number. So, sir, please refrain from being a jerk, and sorry if I came off that way.
And I just confirmed with another friend that his works great also.

Post an image please.
Nobody called you a liar, and if you think I am being a jerk, you are way too sensitive.

I have this same problem. Mine is at 2.0.1.0. I believe koush was in the irc channel last night saying something about it.

Thanks for the update.

fennellchrid said:
Look... I am not a liar, and don't appreciate being called a liar. I am just trying to help you. In my ROM Manager it says current and latest is 2.0.1.3. In my Clockwork Recovery it says version 2.0.1.3. I have restarted it three times into recovery, and it says the same number. So, sir, please refrain from being a jerk, and sorry if I came off that way.
And I just confirmed with another friend that his works great also.
Click to expand...
Click to collapse
Apparently if you reboot into recovery using rom manager it will show you are in the updated version, but if you boot into recovery manually from a completely shut down phone you will see that you are actually in the old version and you were never updated at all. The thought is that if you reboot into recovery from rom manager it loads their recovery image but if you manually boot into recovery it doesn't. The reason is that the nand is still locked, so rom manager can't actually reflash the recovery image without being in recovery at the time.

I am currently at work... If I had a camera I would. Ask some other people to do it, and I promise they will tell you the same thing. If you read in the Recovery Reflash Tool forum, you will see others talking about this very same thing.

I see just as many from the other side of the fence. What do you think of that?

sdorn77 said:
Apparently if you reboot into recovery using rom manager it will show you are in the updated version, but if you boot into recovery manually from a completely shut down phone you will see that you are actually in the old version and you were never updated at all. The thought is that if you reboot into recovery from rom manager it loads their recovery image but if you manually boot into recovery it doesn't. The reason is that the nand is still locked, so rom manager can't actually reflash the recovery image without being in recovery at the time.
Click to expand...
Click to collapse
This makes sense. This is how I rebooted into recovery. Thanks!
Update - Sorry, you were right. What he said is true. Mine is still 2.0.0.7, just shows up at 2.0.1.3 when you reboot via the ROM Manager. Again, I apologize.

that's correct, koush's rom manager uses a fake flash to upgrade the recovery versions. It does not stick if you boot normally into recovery without rom manager. If we weren't pursuing other things you will like even more we would make a way to flash custom recoveries. But we will instead work to eventually give you true nand unlocked everything. just in the meantime except what you have please. You don't always have to have the latest! I
If a serious issue is found requiring a real update we will get to it.

Please don't take this as a demand, or dissatisfaction. I am very happy with what you folks have done so far and can certainly wait for whatever the team decides to do I was just reading that some versions of Clockwork were having trouble with Froyo and was looking to the future. Thanks for replying

sdorn is correct. Hitting recovery from ClockworkMod is 2.0.1.3 and a fresh boot into recovery (adb, hboot) is 2.0.1.0. The recovery will probably have to be flashed from unrevoked's tool to get up to the latest version or until NAND is unlocked outside of hboot.

not sure how but i have clock work 2.0.1.3 as my clockwork and it says in every time i bring it up if i knew how to take a screen shot in recovery id show ya,

junjlo said:
not sure how but i have clock work 2.0.1.3 as my clockwork and it says in every time i bring it up if i knew how to take a screen shot in recovery id show ya,
Click to expand...
Click to collapse
Power the phone off, and then boot into recovery by holding Vol Down + Power and selecting RECOVERY. You have 2.0.1.0 installed.

Lock
Mods may want to lock this thread ... it continues to be a debate when the question was answered by Shadowmite.

fennellchrid said:
This makes sense. This is how I rebooted into recovery. Thanks!
Update - Sorry, you were right. What he said is true. Mine is still 2.0.0.7, just shows up at 2.0.1.3 when you reboot via the ROM Manager. Again, I apologize.
Click to expand...
Click to collapse
Very classy response.

[Solved][Q] Nexus one SLCD - custom rom

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").

[GUIDE] Manually update your Nexus S to GRH78

http://android.clients.google.com/p...553.signed-soju-GRH78-from-GRH55.a71a2082.zip
Download the OTA package here
Rename it to update.zip, and place it on the root of your internal storage
Shut down your phone, and reboot into the bootloader by holding volume up and powering back on
Choose "recovery" from the list, and select it with the power button
When you see the red triangle press volume up and choose to update
Credit Gbhil for the file
IF YOU ARE ON CWM:
Just got an Android 2.3.1 update for Nexus S. It's on ROM manager if you want it. Make sure you flash recovery 3.0.

Also, for this to work you must be on Stock Recovery. This will not flash properly if you are using clockwork recovery

momohammed20 said:
Also, for this to work you must be on Stock Recovery. This will not flash properly if you are using clockwork recovery
Click to expand...
Click to collapse
Correct. Koush is currently looking at fixing this for CWM.

Can we try to update and flash the zip using adb?

This was just tweeted:
Just got an Android 2.3.1 update for Nexus S. It's on ROM manager if you want it. Make sure you flash recovery 3.0.

edit nevermind got update

I just got prompted OTA for this update. Anyone know it I was to accept it, would I have any problems since I changed my recovery to ClockWork recovery?
I know it's been said it's on rom manager now, I am just curious if there would be any potential problems of accepting OTA updates with the stock recovery gone.

I have cwm recovery flashed and looked in Rom manager but is getting that "the rom you are using does not support ota updates etc" How did you manage to get Rom manager to update it to GRH78??

ive tried every way listed on xda but still get a "error 7" when trying to flash the update. i am using stock rom with clockwork 3.0. anyone having the same issue or any way to fix it?

usb disabled?
Got the message from Google to update. So I let it do its thing, said unable to update zip and now seems my usb connection is broken. Any help will be greatly appreciated. I'm on NS despite my sig Also on CWR 3.0 unlocked

are we supposed to be able to install this 2.3.1 update that we download from rom manager?

nsavani said:
ive tried every way listed on xda but still get a "error 7" when trying to flash the update. i am using stock rom with clockwork 3.0. anyone having the same issue or any way to fix it?
Click to expand...
Click to collapse
Koush is gonna repackage it later tonight for those with error 7

demo23019 said:
are we supposed to be able to install this 2.3.1 update that we download from rom manager?
Click to expand...
Click to collapse
How did you get it to download? I hope Koush gets CWM to play nice with the updates.

yungfresh said:
How did you get it to download? I hope Koush gets CWM to play nice with the updates.
Click to expand...
Click to collapse
Well there is very little info in OP
and could be worded little better to avoid confusion
You have to put on Wifi and go to download ROM for some reason if you on on mobile network it wont show the update in rom manager
Dont bother it wont. From what i gathered we have to wait for modified version

Download the zip, choose to open with rom manager and it will flash fine with cw recovery 3.0.0.
Sent from my Nexus S using XDA App

dirk1978 said:
Download the zip, choose to open with rom manager and it will flash fine with cw recovery 3.0.0.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
not for me

demo23019 said:
Well there is very little info in OP
and could be worded little better to avoid confusion
You have to put on Wifi and go to download ROM for some reason if you on on mobile network it wont show the update in rom manager
Dont bother it wont. From what i gathered we have to wait for modified version
Click to expand...
Click to collapse
Got great news! I got it to work! All I did was put the .zip file on the root of my sd and used Rom manager to "download rom" chose the .zip file and voila!! It installed everything fine. I am officially on GRH78. Hope that helps people out!

is this with the paid version or non-paid?

the CWM update will work of you have not used Koush's rooboot.img and are running a the rooted boot.img.
He said he will release a version later tonight that should work with rootbootimg installed as well.

glad im on stock recovery + root.

Help! Can't get into recovery/clockwork...

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. =)

[Q] Cannot boot to CWR

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.