Database Users

Flash custom recovery on an already rooted Aria with clockworks recovery?

is it possible to switch to another custom recovery after I already got clockworks?
I tried unrevoked but its stuck in the reboot (I believe its trying to root my aria again)

not sure what youre trying to do.... i believe Clockwork is the only Recovery for rooted phones. if you want to flash a custom ROM, well that is something else altogether. please be specific as to what you want to flash to the phone. include a link to the flash too

I was trying to flash psfreedom recovery rom from here
http://psfreedom.com/wiki/HTC_Aria
I believe the method on that website was for unrooted arias without clockworks

zyo said:
is it possible to switch to another custom recovery after I already got clockworks?
I tried unrevoked but its stuck in the reboot (I believe its trying to root my aria again)
Click to expand...
Click to collapse
To flash a different custom recovery on your Aria, you need to rename the zip file LIBEIMG.ZIP on the SD card and boot in HBOOT (Power on the phone by holding down VOL DOWN and the Power Button). When it boots to the HBOOT screen you should see text stating that it found LIBEIMG.ZIP and is installing it.

awesome. now before I go ahead, is there any clockworkx recovery image I can revert back to?

zyo said:
awesome. now before I go ahead, is there any clockworkx recovery image I can revert back to?
Click to expand...
Click to collapse
I'm curious, what recovery are you talking about?

thanks for including the link. the instructions are clear.... Root IS required, Clockwork recovery is recommended, the Freedom Aria flash appears to be a custom ROM.
once the phone is Rooted, boot into Recovery, make a Nandroid backup, and flash downloaded zip file from SD card.
if you need help Rooting, there is all sorts of good methods available on this site. I use the Unrevoked method myself, but it works best on Linux or Mac OS

zedbra said:
thanks for including the link. the instructions are clear.... Root IS required, Clockwork recovery is recommended, the Freedom Aria flash appears to be a custom ROM.
once the phone is Rooted, boot into Recovery, make a Nandroid backup, and flash downloaded zip file from SD card.
if you need help Rooting, there is all sorts of good methods available on this site. I use the Unrevoked method myself, but it works best on Linux or Mac OS
Click to expand...
Click to collapse
hmm I think you are looking at the old method which is a custom rom
The new one is a custom recovery which brings me to the question as I dont think you can flash a custom recovery in the clockwork custom recovery.

its possible im looking at the wrong thing, but far as i can tell it states "Recovery Custom ROM" which is totally different from Custom Recovery ROM
From link posted above:
"Update can be installed in recovery mode in Psfreedom settings menu via Update (local) or Update (net) if you have configured your wifi connection. Put the file on your SDCARD and install it.
Download Recovery custom rom : http://alephzain.klutsh.com/aria-recovery.tgz "

tpbklake said:
To flash a different custom recovery on your Aria, you need to rename the zip file LIBEIMG.ZIP on the SD card and boot in HBOOT (Power on the phone by holding down VOL DOWN and the Power Button). When it boots to the HBOOT screen you should see text stating that it found LIBEIMG.ZIP and is installing it.
Click to expand...
Click to collapse
I have similar questions. I was trying to update my version of clockwork also using unrevoked again, but couldn't get it to work. I guess my questions are:
1. Is there any benefit in updating to a newer version of clockwork? My current version is 2.0.x.x and I believe the latest one is 2.5.0.4.
2. Will this same method work to do so? Can I rename the latest clockwork .zip file like this and get it updated?
I thought using the flash clockwork option in ROM Manager would do it, but it doesn't. If I reboot from ROM Manager it goes to the newer version, but if I reboot otherwise it goes to my original. The couple times I've used it, there appears to be maybe some different features/options in the newer one and I feel like I might be missing out on something!

What's the difference with this recovery?
Sent from my Liberty using XDA App

zedbra said:
its possible im looking at the wrong thing, but far as i can tell it states "Recovery Custom ROM" which is totally different from Custom Recovery ROM
From link posted above:
"Update can be installed in recovery mode in Psfreedom settings menu via Update (local) or Update (net) if you have configured your wifi connection. Put the file on your SDCARD and install it.
Download Recovery custom rom : http://alephzain.klutsh.com/aria-recovery.tgz "
Click to expand...
Click to collapse
These are probably two different things. once you got the recovery rom flashed you can upgrade it in recovery mode (hence its different from original clockwork recovery)

Ok bro, I didn't see much info about it so I'm gonna take your word for it.
@brswattt, far as I can tell this is " basically" used for jailbreaking the ps3.

@armyengineer;
you can use unrEVOked to flash the new recovery. if youre a Windows user, download the unrEVOked tool and run the .exe as Administrator. also make sure there are no conflicting s/w on the PC such as HTC Sync and you have all the drivers installed(HBoot, ADB drivers, etc.)
for more info about the PSFreedom Recovery, check out THIS Thread HERE

unrevoked keeps giving me
couldnt find misc
error, is there any other way to flash a recovery?

zedbra said:
@armyengineer;
you can use unrEVOked to flash the new recovery. if youre a Windows user, download the unrEVOked tool and run the .exe as Administrator. also make sure there are no conflicting s/w on the PC such as HTC Sync and you have all the drivers installed(HBoot, ADB drivers, etc.)
Click to expand...
Click to collapse
This still isn't working for me. Everything appears to go well at the start, then I get:
Waiting for root...(safe to restart if this doesn't work)
At which point the only way I can restart is to pull my battery. After doing so, it reboots and I get:
This was a triumph
It is not, however, any such thing. After another minute I get this:
Internal error: couldn't find misc.
So I've still got my original version of clockwork, 2.0.1.3, despite the fact that ROM Manager is telling me I have 2.5.0.1. I'm obviously missing something here.
BTW, if it matters I'm running CM 6.1.0

armyengineer51 said:
I have similar questions. I was trying to update my version of clockwork also using unrevoked again, but couldn't get it to work. I guess my questions are:
1. Is there any benefit in updating to a newer version of clockwork? My current version is 2.0.x.x and I believe the latest one is 2.5.0.4.
2. Will this same method work to do so? Can I rename the latest clockwork .zip file like this and get it updated?
I thought using the flash clockwork option in ROM Manager would do it, but it doesn't. If I reboot from ROM Manager it goes to the newer version, but if I reboot otherwise it goes to my original. The couple times I've used it, there appears to be maybe some different features/options in the newer one and I feel like I might be missing out on something!
Click to expand...
Click to collapse
Although there is a ClockworkMod 2.5.0.4 version, I don't think it is for the Aria. According to ClockworkMod ROM Manager, 2.5.0.1 is the most current one for the Aria so I am believing what ROM Manager is telling me since it is written by the same the vendor.

I have tried CM 6.1.0
original HTC Aria 2.1 International Rom
and FR001 RC1
all no go. I think it has something to do with the phone already been rooted and has clockworks installed which makes unrevoked unhappy

zyo said:
I have tried CM 6.1.0
original HTC Aria 2.1 International Rom
and FR001 RC1
all no go. I think it has something to do with the phone already been rooted and has clockworks installed which makes unrevoked unhappy
Click to expand...
Click to collapse
OK, let's start from the beginning. You asked about installing an alternate recovery (PSFreedom recovery), but apparently it has its own installation procedure that needs to be run on an unrooted Aria.
What you need is to find just the PSFreedom recovery and copy it to your SD called in a file called LIBEIMG.ZIP and that is how you need to install it on a root phone that has ClockworkMod. Perhaps you need to go back to the PSFreedom thread and ask if a LIBEIMG.ZIP can be produced that can be flashed from HBOOT to replace ClockworkMod.
Looks like everything you need is located in the PSFreedom wiki:
http://psfreedom.com/wiki/HTC_Aria

I got a recovery.bin which is suppose to be used with unrevoked.
are you talking about the same one if I just compress it into a zip file?

[GUIDE] Root & recovery WITHOUT oem unlock & wipe (2.3.2 & older, plus now 2.3)

[GUIDE] Root & recovery WITHOUT oem unlock & wipe (2.3.2 & older, plus now 2.3)
UPDATE #2 - Fitchman has reported successful root and rom flash without unlocking the bootloader by using Ginger Break. Full details in this post: http://forum.xda-developers.com/showpost.php?p=13236136&postcount=135
UPDATE - IMPORTANT: This method does not work with Android 2.3.3. Search the forum or this post in this thread for a way to update to 2.3.3 and root without unlocking if you haven't updated yet.
Alternatively, use this method on 2.3.2 and lower, then use titanium to back up everything, store it on your laptop (along with all your sdcard's data), then do the oem unlock step first and then continue from there with the rest of the guide.
Not my original idea, but a consolidation of a discussion between inakipaz and shrivelfig and myself in another thread and being posted here for easier finding by future root-seekers.
Shrivelfig's tested the method to re-root a previously rooted pone with a re-locked bootloader, and inakipaz has done it on a phone that's never had the bootloader unlocked.
The advantage here is that those who chose not to root when they first got the phone won't lose any app data or sdcard data like the methods that have you unlock the bootloader do. The disadvantage is your bootloader remains locked, which may prevent you flashing certain things in the future.
edit: see ravidavi's posts below; he's shown you can even flash custom roms that are clockwork compatible while having a locked bootloader with this method.
Download these two files:
clockwork recovery v3.0.0.5 or clockwork recovery v3.0.0.5 mirror if above not working
su-2.3.6.1-ef-signed.zip
Koush's blog for the latest clockwork updates (find Nexus S in the list).
Also, if you don't already have the necessary android sdk and drivers on your computer, get them from here: http://developer.android.com/sdk/index.html and install them. Some Windows users report better luck just installing pdanet. There's a decent guide for Windows users on installing the sdk here.
Place the recovery file on your laptop where you can access it while using the sdk fastboot commands.
Place the su zip one in the top level folder of your sdcard.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the excellent instructions that Allgamer gives in this GUIDE, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps below.
To navigate in the clockwork recovery, you use the volume keys to scroll up/down through the menus, and the on/off button to select what's highlighted.
(note: some report success without these first 3 steps, others don't get a succesful root without, I recommend doing them)
select mounts and storage.
select mount /system
select go back
select install ZIP from sdcard
select choose zip from sdcard
select su-version#-signed.zip file you downloaded earlier
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
After the phone reboots, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
This method doesn't install busybox, so go to the Market and download/install busybox directly, or get Titanium Backup and check it's "problems?" button and let it install busybox for you. There's also an app called root checker that supposedly verifies you have a working root on your phone.
Once you have a successful root installed, I'd suggest getting back into clockwork recovery and running a nandroid back up from clockwork's backs and restore menu. Then copy that file from your sdcard (in the /clockwork/backups folder) to your laptop for safe-keeping and an easy full system restore to a known working config.
Usual disclaimers about I'm not responsible for damage to your phone or loss of data apply. Use any rooting method at your own risk.
Thanks and all the real credit go to inakipaz, shrivelfig and allgamer, and of course to koush, and ChainsDD for the superuser apk.

Worked perfectly. I used fastboot from my Mac (outlined in the stickied Mac Root thread). Root checker verifies that I have root.
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!

yeah! good work!

Srsly. Awsom.
Someone sticky this....

Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
I would think this method also gives you a way to back up before unlocking the bootloader.
1) fastboot boot into Clockwork as described here
2) Full nandroid backup from Clockwork
3) Mount "SD" from Clockwork over USB, copy everything to computer (since it wipes everything)
4) Go back and unlock the bootloader as usual, resulting in a full wipe
5) Flash Clockwork Recovery again through whichever method
6) Mount "SD" from Clockwork over USB, copy the backup back to phone
7) Restore nandroid
And now you've unlocked the bootloader without amnesia =)
ravidavi said:
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!
Click to expand...
Click to collapse
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!
Also, the fact that you're able to boot into Clockwork using "fastboot boot" - that also means you can install a ROM .zip file right from there.

cmstlist said:
Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
Click to expand...
Click to collapse
"fastboot boot" only launches the recovery no unlock needed. "fastboot flash" flash the recovery

cmstlist said:
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!.
Click to expand...
Click to collapse
It worked! Here's the process I used, starting from a completely unmodded Nexus S.
1: Use the method detailed here to gain root access without unlocking the bootloader.
2: Using a root-enabled file explorer (I used Super Manager), rename install-recovery.sh (in /etc) to install-recovery.sh.old . You'll need to remount as r/w to do this. NOTE: You don't *have* to do this step, but if you don't, then you can only use clockwork once after which it will be erased on reboot.
3: Using ROM Manager, install Clockwork Recovery.
4: Pleasure yourself, because your bootloader is still locked and nothing was erased.
I have yet to try actually flashing a custom ROM. Does this mean that it can also be done without unlocking bootloader?

Well damn, whaddaya know. I just flashed MoDaCo r10 without unlocking the bootloader, and without losing any personal data on /sdcard.
I figure someone at XDA should like this.
Pretty much followed distortedloop's advice. Starting from a fully stock Nexus S with Android 2.3.2 (GRH78C):
* Root using the method on this thread.
* Rename install-recovery.su to install-recovery-old.su. (in /bin)
* Install Clockwork Recovery from ROM Manager.
* Download whatever ROM you want (compatible with Clockwork), rename to update.zip, and copy to sdcard.
* Reboot into Clockwork.
* Wipe cache, reset to factory (IF REQUIRED BY NEW ROM). This was my first install of MoDaCo, and that requires it. This step does NOT erase your personal files on sdcard, just all android-related files.
* Install update.zip from Clockwork.
* Continue self-pleasuring ... you now have a custom rom without touching your bootloader or wiping your personal sdcard data.
Maybe it's just because I'm a noob here, but it seems to me that this is a BIG deal. All root/ROM installation methods that I've seen so far have required an unlocked bootloader. This seems to be the first time a Nexus S has been unlocked and custom-ROM'd without unlocking the bootloader and wiping the entire /sdcard.
Ravi

Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
What's really odd is now we have to wonder what's the purpose of the oem unlock erasing your sdcard? Speculation was that it was a security feature to keep people from accessing your data if they stole your phone; they couldn't flash something on the phone to get access, but clearly they can. Fastboot into a custom recovery and you own the phone.
Perhaps this is a security hole Google will try to fix some day?
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.

distortedloop said:
Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
...
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.
Click to expand...
Click to collapse
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi

ravidavi said:
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Click to expand...
Click to collapse
I'm thinking that something like Superboot might need to have the bootloader unlocked, since it replaces the boot image, right? But I'm not sure.
ravidavi said:
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi
Click to expand...
Click to collapse
There's only a page and a half of posts in the development section right now, so it's not likely to disappear any time soon, but you could ask a mod (theimpaler747 is ours) via PM to sticky it. I thought about asking myself, but seemed a bit tacky to ask for my own thread.
Meanwhile, I'd been linking people to various posts I'd made in other threads suggesting this might work, but once inakipaz and shrivelfig confirmed it, I'm just now pointing people here. I just hope people see this before wiping their phones unnecessarily.
Really, the other guides should just be updated to skip the oem unlock step. That's really the only different thing we're doing here.

i'm just waiting for more people "newbies" to confirm this actually works for them, before making it a sticky

In theory if you really really screw up your phone, you might need fastboot flash in order to recover it. But if fastboot also lets you boot into an img recovery... then you still have a recovery route that doesn't require unlocking.
Sent from my Nexus One using XDA App

I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App

qreffie said:
I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
yes because you still have the original recovery installed

distortedloop said:
Perhaps this is a security hole Google will try to fix some day?
Click to expand...
Click to collapse
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.

shrivelfig said:
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.
Click to expand...
Click to collapse
I can confirm that the Nexus One does not allow this "fastboot boot" on a locked bootloader. Maybe this was just an oversight?
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.

I can confirm that this method works, without unlocking the BL or erasing the SD part.

This is pretty cool. I wish I new about this before I unlocked the bootloader days after I received my phone. I too wonder if this was intentional or an oversite. Google did want this phone to be for developers, but like other's said, this is also a bit of a security hole. The wiping of the sd card on unlock would protect the person if the phone was stolen, like if there was confidential corporate stuff on there. Even if you password protect your phone, someone could fastboot clockwork, mount the sd card and retrieve all the information that was on there.

cmstlist said:
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.
Click to expand...
Click to collapse
It's also been done by Samsung with some versions of the Galaxy S line (some of the "leaked" roms, and even one official kies push (IIRC) changed the bootloader, causing people the ability to use 3 button mode for Odin access, and causing others to lose it.

Boot loader is unlocked but i don't have root access Nexus One Running 2.3.3

hello everyone. i been a long time lurker of this site but never had the courage/motive to post. but i have an issue.
after much reading of how great rooting your phone can be. i too wanted to do it. so i looked n looked until i decided that id tryout CM7 cyanogen site
i believe i was able to unlock the bootloader/device. everytime i power up my phone regular start up starts with an unlocked lock at the bottom(like its supposed to right lol)
but here is as far as i get to go. i backed up my apps with astro file manager. then downloaded rom manager n as soon as i open it says "you must root your phone for ROM manager to function. superuser was not found at "/system/xbin/su". use goo search on ur computer to root your phone"
im stuck here because well im a noob and dont know why this is showing up. i was kinda hoping one of you guys could help me out here...

Taking straight from the wiki. Please read it before asking questions.
very generic explanation of steps needed to update a stock phone to custom ROM:
Download the ROM of your choice.
Copy the downloaded ROM image to the SD card
Root if you don't want to unlock bootloader (or just unlock bootloader).
Flash custom recovery image (if not done while rooting)
Turn off the phone
Turn on the phone while holding Volume Down
Select "BOOTLOADER" from the menu
Select "RECOVERY" from the menu
Select "Wipe"
Select "Wipe data / factory reset"
Select "Wipe Dalvik cache"
Return to main recovery menu
Select "Flash update.zip" or "Flash ZIP file"
Turn off verification, if such option is presented
Select your downloaded ROM image
Wait for the flash to finish successfully, if it didn't - do not continue!
Return to main recovery menu
Reboot the phone
You can follow a video walkthrough for this here: How to Flash a Custom ROM

To add to the post above, look at my signature and make sure you read and execute the relevant guide.

Just to clarify what the others are saying. You don't have root because you didn't root your phone.
You only unlocked the bootloader, which allows you to flash partitions through fastboot.

you havent rooted ,just unlocked bootloader

Echo?
Sent from my Nexus One using XDA Premium App

apollofroyo said:
you havent rooted ,just unlocked bootloader
Click to expand...
Click to collapse
yea i since realized that. ive now flashed 2.2.
but cant get the to root it yet
trying to figure things out.. maybe rooting wasnt such a good idea since i cant figure it out

rawskillz said:
yea i since realized that. ive now flashed 2.2.
but cant get the to root it yet
trying to figure things out.. maybe rooting wasnt such a good idea since i cant figure it out
Click to expand...
Click to collapse
since you have a unlocked bootloader you can do fastboot flash..
get amon ra recovery and do fastboot flash recovery recovery.img
after you do that it should say sending flashing and done with no errors
from then reboot into recovery and do a nandroid of rom then do wipe and wipe and flash selected rom you want.. cm7 plus gapps after reboot and you haverom..
nexus one is ez to gainroot if you unlockboot loadder.. if you dont then it gets more complicated..

rawskillz said:
yea i since realized that. ive now flashed 2.2.
but cant get the to root it yet
trying to figure things out.. maybe rooting wasnt such a good idea since i cant figure it out
Click to expand...
Click to collapse
wow thanks alot. it was way easier than i thought it would be. now going to backup my apps and flash cyanogen 7 . the problem is i had installed sdk b4 in wrong folder etc. will take future note. thanks to all

Nexus S i9020a + CM7

Can someone please direct me to the a step by step guide on how to Root and put CM7 on the Nexus S i9020a variant? Most of the stickies are for the T-mobile version and Its getting to be a bit confusing on which guide to follow. Please help this noobie!!!

use gingerbreak then rom manager it's that simple
http://forum.xda-developers.com/showthread.php?t=1044765

Quick note once you install CM7 do not use the 2g/3g feature it will break your 3g

Break 3g? as in damage it permanently? Thanks for the link for gingerbreak so basically that will root my nexus s then I can install CM 7 with out any special instructions since it has different radio compared to the tmobile version?

i used gingerbreak then rom manager to install clockwork recovery and CM7. Do some reading the 3g bug for I9020A has been discussed a few times. Just stay away from the 2g/3g toggle and everything will be fine. I don't think it permanently breaks it just is a pain in the A to fix. I have a I9020A and this was the simplest way I've found.

don't we have to flash a clockwork compatible kernel first, before flashing cm7?
Also, doesn't clockwork rom manager fail on sns? I have cwr from the main stickies, but rom manager doesn't see it (it works), and can't download roms, unless cwr from rom manager, which I heard fails.
Sent from my Nexus S using XDA App
So I downloaded CM7 7.0.2 - and gapps - flashed in order (nandroid first) and voila! no hastle! This ROM is great!

No, those are the only steps i took

CM7 comes with its own AOSP kernel. Just flash the rom, you'll get the kernel bundled. (Of course you can always use a great kernel from the developers thread) don't forget to flash gapps.
Sent from my Nexus S using XDA Premium App

jruweaver said:
Quick note once you install CM7 do not use the 2g/3g feature it will break your 3g
Click to expand...
Click to collapse
He means don't use the 2g/3g toggle widget as that will cause some problems, it hasn't been fixed yet. If you do want to change it though, do it manually through the settings.
Sent from my Nexus S using XDA App

I tried using gingerbreak on my i9020a but it runs for longer than 15 mins so I guess it doesn't work. What are my other options for rooting?
edit: I guess it's because I installed 2.3.6.. is it possible to downgrade easily?

drleospaceman said:
I tried using gingerbreak on my i9020a but it runs for longer than 15 mins so I guess it doesn't work. What are my other options for rooting?
edit: I guess it's because I installed 2.3.6.. is it possible to downgrade?
Click to expand...
Click to collapse
Follow one of the root guides, all you really need to do is unlock the bootloader and install Clockwork Recovery.
Once that is done, download the zip for cm7 and use CWM to flash it.

Matridom said:
Follow one of the root guides, all you really need to do is unlock the bootloader and install Clockwork Recovery.
Once that is done, download the zip for cm7 and use CWM to flash it.
Click to expand...
Click to collapse
Thanks

Matridom said:
Follow one of the root guides, all you really need to do is unlock the bootloader and install Clockwork Recovery.
Once that is done, download the zip for cm7 and use CWM to flash it.
Click to expand...
Click to collapse
Exactly the steps I took. Took all of 10 minutes
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot recovery
Install .zip from SD
Select CM7
reboot system

Mr Kyle said:
Exactly the steps I took. Took all of 10 minutes
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot recovery
Install .zip from SD
Select CM7
reboot system
Click to expand...
Click to collapse
Agreed, but it's a matter of getting the correct CWM image for our phones. Also, for people who are setting up their phones for the first time, the drivers needed for fastboot need to be installed, fastboot/SDK needs to be downloaded etc...
Hence why i referenced the rooting guides.

Mr Kyle said:
Exactly the steps I took. Took all of 10 minutes
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot recovery
Install .zip from SD
Select CM7
reboot system
Click to expand...
Click to collapse
Which recovery img file should I use from here?
http://forum.xda-developers.com/showthread.php?t=988686&highlight=i9020a
Thanks
edit: nevermind, I guess the color names are just cosmetic?

drleospaceman said:
Which recovery img file should I use from here?
http://forum.xda-developers.com/showthread.php?t=988686&highlight=i9020a
Thanks
edit: nevermind, I guess the color names are just cosmetic?
Click to expand...
Click to collapse
Yep, it's just the color you want your recovery to be. I flashed the cyan a couple of days ago for somebody else and no issues.. typical clockwork recovery

So I flashed the recovery file, but when I boot into recovery now, there's just the triangle with the ! in it and nothing happens.. did I do something wrong?
edit: reflashed it and it works

drleospaceman said:
So I flashed the recovery file, but when I boot into recovery now, there's just the triangle with the ! in it and nothing happens.. did I do something wrong?
Click to expand...
Click to collapse
How did you flash it? That's the stock recovery.. should be 'fastboot flash recovery nameof.img' without quotes obviously.

drleospaceman said:
So I flashed the recovery file, but when I boot into recovery now, there's just the triangle with the ! in it and nothing happens.. did I do something wrong?
edit: reflashed it and it works
Click to expand...
Click to collapse
somebody after reboot no CWR on recovery use this solved your problem
clockworkmodrecovery rom manager find and install
open it and touch flash clockworkmod recovery(first item)
select reboot into recovery manual
mount and storage select
mount USB storage
unmount
++++ go back +++++
install from zip sdcard
find
'' super user.zip'' flash
reboot
find and isntall ''es file explorer'' select setting mark root explorer and mount file system after
select phone in file explorer find ''etc'' folder select and find ''install-recovery.sh'' file and rename file for example ''install-recovery.sheski'' and
open rom manager again touch flash clockworkmod recovery(first item)
check it...
please click thanks button

[GUIDE] Install ClockworkMod Recovery image after updated to 2.3.4 (GRJ22).

Not applicable
Delete this thread

Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!

Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.

Let me answer myself.
I don't think the latest rom 2.3.4 is compatible with the clockwork you supplied. So I have to flash my phone back to GRH78. I downloaded the stock ROM from the internet. and then push all the images file into /sdcard/clockworkmod/backup/2010.xxx.
Next, I restore the image in clockwork menu.
after restore, reboot the phone, now I am back in business.
When the phone is boot, i lost the root again, so i went to modaco.com and get Paul's package. run it, restart, I got the root.
Finally, go to market place and get ROM Manager, install the clockwordmod. and I have a 'proper' phone.
although I don't have the least rom, at least i got a working phone that is rooted.

bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
I have the same problem. How did you handle it?

Wow, why risk messing up your phone with flashing a boot.img when you can just rename /etc/install-recovery.sh to something like /etc/install-recovery.bak?
Here's one way to rename (courtesy of Matridom). Another is to use Root Explorer.
Matridom said:
The new update applies the install-recovery.sh script into our phones (not there previously.
Boot into the bootloader
flash CWM
select recovery from the bootloader (DO NOT reboot the phone)
apply the su binary
boot into the OS and test root
make sure busybox is properly installed
run ADB shell
then:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
Boot back into the bootloader and re-flash CWM, should stay permanent now.l had applied the SU binary at the same time as the OTA update, then renamed the installer script and flashed back CWM.
Click to expand...
Click to collapse

andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
same here someone please help ?

This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App

bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
Hi Bante, I am sorry for the inconvenience. I have revert back the CWM Recovery to 3.0.2.4. You can download it at the link above, and try it again
I hope that the problem you mention wont persist anymore

zero383 said:
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am sorry but not all people can successfully use Command Prompt to do so.
I cant use command prompt, as it says "Image cant be loaded".
So I had to use this method.
I search around the forum and seen this as a quite common problem,
so I decided to share it
Hope you understand.
Anyway, thanks for your method too Cheers

andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist

16vMK1 said:
same here someone please help ?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist

Wow people like to make things complicated. Why install an entire rom to get ride of a script?
if you can flash cwm, you should have some basic understanding of fastboot, adb and the search options in the forums. the answers are all there already.
Sent from my Nexus S

No disrespect, I agree flashing recoverys should only be done after you understand how to use the tools to do it. there is no reason someone who is going to mod systems on their nexus shouldn't be able to use fastboot and adb properly. all the right drivers are in the sdk.
Sent from my Nexus S 4G using Tapatalk

nxt said:
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Click to expand...
Click to collapse
This is what I did.
I rooted my NS, which had 2.3.3
Used phone with stock 2.3.3 until I figured out which ROM I want to flash.
Before I flashed any ROM, did a Nandroid Backup through CWM.
Used the ROM for a few days, but when I saw that official update is ready for download for i9020A, did do a restore from the Nandroid backup I created.
Updated from 2.3.3 to 2.3.4, phone works fantastic, video chat also works great.
After update when I tried using any of the apps required SU permission, they didn't work. I tried installing a couple of .apk files, couldn't either install it or after installation it didn't work.
Thought let me try wiping my phone clean and start all over again, may be I will use a custom ROM again, downloaded ROM, went to ROM Manager to reboot into recovery, nothing happens.
Tried booting into Recovery option manually by pressing Volume Up and Power button, nothing happens but the Bot with an Arrow appears on screen.
So, I thought I will follow this procedure to reflash CWM to my phone and get it going. I was able to use the command FastBoot once, and suceeded pushing .img file to my phone but now whenever I try using the commands from my computer, this error message appears : "This application has failed to start becasue AdbWinApi.dll was not found. Re-installing the application may fix this problem."
Why this error message if I have the sdk on my computer already through which I was once able to push .img file without any troubles?
Can anyone tell me what would be a possible solution?
Also, how can I fix this problem and get ClockWorkMod Recovery installed on my NS again?
How can I get stock recovery image on my phone if I want start all over again from scratch?
Thx a million.
Edit ::: I found the answer as to how to how to install CWM again. Thx anyways.
Other question still remains a puzzle... why am I not able to install certain programs or if did manage to install, can't run them?

I ran your method and I think I'm stuck at some step...
My phone now default boots into CWM 3.0.2.4
Recovery boots to a newer recovery I flashed.
How do I get my phone to default boot into the OS again?
Edit: nevermind, just downloaded the full 2.3.4 rom, extracted and flashed the original boot.img.

dreamsforgotten said:
All the right drivers are in the sdk.
Click to expand...
Click to collapse
After installing the sdk and a platform, I have adb, but where is fastboot?

I was getting the same error as "Image cant be loaded". after hours of struggling I found that It's only because I was not in the same directory as the img file. silly eh?

hi,did you repaiar your phone,i have try everything but it just keep going in clockwork mode,if i than pres reboot now in clockworkmode it stays on google padlock
i realy need phone if you can help or someone else,than ....

just tried this method of window7 (thanks for the work) with cwm 3.0.2.4, but got the same result like the others in this thread: cant boot the android 2.3.4, the system is always booting into the cwm, no way out.
I don't think this tool works as it should.
:-(
EDIT:
I didn't realize that window7's tool would install the cwm into the boot-partition instead of the recovery-partition.
To get my boot partition back I downloaded the 2.3.4 firmware image from http://forum.xda-developers.com/showthread.php?t=1056062 and extracted the boot.img from the zip.
with "fastboot flash boot boot.img" I restored my orginal boot partition an can boot into android again.
(fastboot is part of the android sdk)