Database Users

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)

[Q] ClockworkMod help!

Hi,
a friend asked me to install CyanogenMod 7 on his ZTE blade after using it on my wildfire.
started by rooting using Universal AndRoot, went perfectly... superuser granted
then installed Rom Manager and clicked Flash Clockwork Mod, selected ZTE Blade, let it install, but i cannot boot into recovery.
the Clockwork version is somthing like 5.0.2.0 which i have read is not supported on a Gen1 device.
the phone still works so i have got time to find a perfect seolution
My question is:
If i install RecoveryManager to use "recovery-clockwork-3.0.0.6-blade.img" to change the clockwork version will this allow me to flash an older version of CWM?
will i then be able to boot into ClockworkMod and flash "update-cm-7.0.0-Blade-signed.zip" on the Gen1 ZTE Blade?
Thanks for all the help

Just use Rom manager to downgrade cwm, no need to carry out a restore.
sent using tapatalk

I have tried using the 'all clockworkmod versions' and selecting the version I want, the bar at the top is downloading, then it says 'error' something to do with privileged scripts or something.
Sorry I don't have the phone here at the moment, but will tomorrow.
I have checked superuser and root access ect, but all is working.
Any ideas
Thanks for your help

Fastboot is enabled in gen1 phones.
So just download a blade-gen1-recovery seperarely and flash the img file from fastboot. The fastboot command will be "fastboot flash recovery recovery.img"
As for the cm7 version u mentioned I don't know whether it is gen1 or gen2. But u can make ur stock rom nandroid backup and check the cm7 and if it is incompatible it wont boot.
And gen1 to gen2 firmware upgrade is needed for using gen2 roms.
Sent from my Blade using XDA App

cyanogenmod >
wiki >
ZTE_Blade_(Gen1):_Radio_Conversion_and_Recovery
Read that guide to convert to Gen2 and install ClockworkMod Recovery.

Hi,
thank you all for your replies, i have now read that CyanogenMod wiki info page you requested, very good infomation. will work on this when Clockwork is working.
as for FastBoot.... i have never used that on a ZTE before, pressing POWER and VOLUME DOWN does nothing but make the android logo flash and POWER and VOLUME UP and MENU does the exact same!
i am open to all advice and infomation, i am paranoid of bricking his phone
Thanks for all your help everyone!

just follow instructions

ME860 with stock 2.3.4 flashing CM7 not fully booted

I have a ME860 with official 2.3.4 updated, i yesterday unlocked the Bootloader with IHOP_Bell.sbf and have CWM flashed successfully. But my phone booted into command line saying OS not detected and was stucked at the command line with 14modes available.
I got into Recovery and flashed to CM7(latest Bat2F.zip) and it completed without error. Now the command line says OS will Boot in 5 secs but is again stucked with Cold Boot Linux Reading ODM Fuse:1 displayed.
I am new to this can someone help me out here ? Thank you

Are you messing around with RSD at all?
Sent from my Atrix XDA Premium App

the only time i used RSD is to flash the IHOP_Bell.sbf to enable unlocking the bootloader. As for flashing the CWM i did tru the Fastboot command from the computer. After that I have never touch RSD at all.
the phone boots up showing unlocked on the top left of the screen. however what i found a bit strange was, right after i flashed the IHOP_bell.sbf, the phone always boots up in the bootloader mode. i thought it was normal that way, so from there i selected the fastboot mode and the phone did boot into fastboot. then i connect the USB cable and entered the fastboot oem unlock and successfully unlocked the phone.
after that, i flashed the CWM recovery mode using moto-fastboot flash recovery and it was done, and i am able to get into CWM recovery options too.
Actually i am thinking of flashing the HKTW fruitcake sbf, do u think it is a good idea ? or should i try something else first?

I wouldn't touch that. I personally never used that. I would wait till another user comments.
Sent from my Atrix XDA Premium App

i tried the fruitcake anyways, and it actually booted up !!
i took a look at the phone details. my phone is now MB860 instead of ME860 which i had b4. anyways there seems to be minor bug with this stock HKTW ROM cuz in the phone details , the version number has a userdebug name in it. so i guess thats way its not stable
will try to flash CM7 again

CM7 still not working, any ideas anyone ??

minusioner said:
CM7 still not working, any ideas anyone ??
Click to expand...
Click to collapse
What CWM are you using? If it doesn't support ext4 that might be your problem. The things you've successfully flashed are all ext3.
Make sure you're using ROM Manager's or romracer's. Those are the only ones that support ext4.

Need to know what recovery you have installed & did you wipe data/factory rest & wipe both caches before flashing CM7????
Sent from my MB860 using xda premium

thank you guys ! i was using this CWM recovery-en-goapk-0630-1029.zip
also from xda so i thought everything was good
so now i have CM7 up and running !!!!

I thought that was deprecated? I may be wrong
I use romracers and sometimes the one in rom manager
but ididnt like it
Sent from my MB860 using xda premium

minusioner said:
thank you guys ! i was using this CWM recovery-en-goapk-0630-1029.zip
also from xda so i thought everything was good
so now i have CM7 up and running !!!!
Click to expand...
Click to collapse
Hello, i got one ME860 Atrix from Hong Kong, and updated the stock rom to 2.3.4 already.
I would like to try the Neutrino rom, as it so beautiful
i have unroot it by using superoneclick 2.2, installed RSD 5.3.1,
then i have confused what is my next step for unlock bootloader process...
i should flash the IHOP_Bell.sbf or OLYEM_U4_2.1.1_SIGNED_UCAOLYPORTFR_P014_A004_M001_HWolympus_1g_1FF.sbf
?? anyone can help me Anyway, thanks a lot~~

Motorola ME860 successful unlocked IHOP_Bell.rar
Then install recovery from fastboot
and ROM from CWM

[Q] flash recovery via adb shell?!

Hi,
I'm desperate! Problems startet when the phone (defy, green lense) could not be charged anymore. Always getting a question mark. Tried the original charger as well as third party charger.
Anyway, right now my recovery is screwed and I cannot boot the phone anymore!
How do I get out of this mess?
First I'd like to get recovery working, I guess. Have adb access but how do I flash a recovery via adb? Or better question where do I get the recovery image file? Cannot find any .img - always .zip files.
(I'd appreciate a solution that doesn't involve Windows)

You can't flash a recovery via adb, since boot loader on defy is locked. I suggest you read up on the beginner's guide and learn how to flash an sbf. Your phone will be then as it was out of the box
Sent from my Nexus 7 using XDA Premium HD app

Damnit!
Worst custom rom phone ever..
Thanks!

Well, actually once you're rooted then installing a recovery is actually installing just an apk 2ndinit search for it once you've flashed an sbf
And we've got really good developers fortunately
Sent from my MB526 using xda premium