Related
I rooted according the directions found here: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/ after getting a new Nexus S 4G.
Even after locking the bootloader. It goes to the Android-with-box then to the Exclaimation-point-inside triangle. When I volume-up and power-button from that screen, an "Android Recovery <3e>" comes up...
Does anyone know what might be going on? And how do I get my custom recovery to stick?
Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App
mikeyinid said:
Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Apparently alot of people have this issue, me included. I seen some posts about using root explorer to change the name of the recovery image if it shows up in system /ext. Sounds crazy but I hear it doesn't show up on all phone's. IV come to terms with having to fastboot every time I flash but I'd love to see a fix. Have you tried Amons recovery?
TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Have you flashed recovery through Rommanager when your phone boots up?
You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?
mbh87 said:
You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?
Click to expand...
Click to collapse
No, I dont think your wrong bro. It makes sense. Ill test your theory soon.
Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...
I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.
david1171 said:
I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.
Click to expand...
Click to collapse
I just had CWM, never had any issues. Im not sure what dictates whether that file is there or not. Im guessing that since tony is so quiet though he got it figured out..
whats amazing is i dont have this script and its one of the things holding the one click up :x
also its part of init.rc so technically a new kernel would.. in theory wipe that out...
mikeyinid said:
Have you flashed recovery through Rommanager when your phone boots up?
Click to expand...
Click to collapse
I did flash CWM through Rom Manager. That didn't work the first few times. It stalled...
mikeyinid said:
Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...
Click to expand...
Click to collapse
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.
Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
TonyArmstrong said:
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App
I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.
mikeyinid said:
Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.
TonyArmstrong said:
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.
Click to expand...
Click to collapse
OCD, I know the feeling lol. What got it to stick?
derekwilkinson said:
I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.
Click to expand...
Click to collapse
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.
TonyArmstrong said:
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.
Click to expand...
Click to collapse
well the "make sure it sticks" flashing with rom manager doesn't make any sense. the only way the recovery would be overwritten is if the ROM you flash over writes it or in fastboot
mikeyinid said:
OCD, I know the feeling lol. What got it to stick?
Click to expand...
Click to collapse
Yeah, I'm very anal when it comes to this kind of stuff...I was a developer for a little bit (Java middleware, then on to the front-end stuff) where regression testing was important. Sometimes, it's best to reload things piece by piece to see what breaks what. Then go from there.
I haven't gotten it to stick yet; gonna get some sleep and start over tomorrow. I used fastboot to push the stock boot, bootloader, system, recovery, and userdata IMGs a moment ago, and the phone is back to bone stock.
So I have a I-9020A with at&t. I have rooted followed by flashing -su and roms instructions using instructions on the net. But after following that process and then going backwards (flashing stock w/ no root locking bootloader) I have realized after that I have more questions.
So first: Unlocking the Bootloader erases the phone. Unlocking the bootloader is needed to flash CWM and SU. I have read many many things about NANDROID, how is NANDROID different from CWM?
So I guess my next question is: How does one remove SU? In the process of rooting and flashing CWM and ROMs I make a backup prior to going to deep... that Backup will have SU, I have unrooted, but SU is still on the phone and I cannot seem to remove it.
Another question is: where are the data files on the phone for apps like Plants vs Zombies? I would like to move them off my phone prior to root, though I'm not sure if that is possible (is it?).
The last question is: If I wanted to muck around with ICS and the source code, is it as simple as flashing the source as explained on the google site? because they make it sound rather easy.
Thanks for any and all help,
toonhead
toonhead85 said:
So I have a I-9020A with at&t. I have rooted followed by flashing -su and roms instructions using instructions on the net. But after following that process and then going backwards (flashing stock w/ no root locking bootloader) I have realized after that I have more questions.
So first: Unlocking the Bootloader erases the phone. This process is needed to flash CWM (but not -su?). I have read many many things about NANDROID, but I have no idea what that is except a backup of a stock rom. When I power my phone off and press Vol up and power on then go to recovery I get an Android w/ a triangle with an exclamation and cant do anything at that point.
So I guess my next question is: How does one backup a stock rom (like you would using CMW) without rooting? or is there not a way and I should just except that when I root for the first time I should expect to loose everything and take off things like pics ect before hand.
The last question is: If I wanted to muck around with ICS and the source code, is it as simple as flashing the source as explained on the google site? because they make it sound rather easy.
Thanks for any and all help,
toonhead
Click to expand...
Click to collapse
Sounds like you should have read more.
When you open the bootloader (the lock) it will wipe your personal data off the phone (not SD storage). This just means you get it as if you just bought it from the store. There is no way around it but happens only once and you'll never have to do it again. Unless you lock it back
Once the bootloader is unlocked you can now flash a custom recovery such as CWM which will let you manage and back up your phone with whatever ROM you want/have.
Once recovery is on your device you also have to root the phone. For this you'll need a zip flashable file with the superuser apk and SU binary files. Flash it in recovery and you should be good to go.
The last step is to install a ROM of your choice. You can just run what the phone has and it will work fine and even take updates without a problem. However, every time you want to flash something you'll need to flash CWM again because the stock image flashes the default recovery on reboot. There is a file you can delete to prevent this from happening. I forgot the path so look around. However, I would recommend you flash a stock ROM which already comes loaded with good stuff and all other things are done for you Just stop by the development section and pick a ROM you like.
Naroid is just a backup.
Oh, and BTW, mocking around with ICS... I would leave that for later. First get your head around basic flashing/rooting stuff. Changing the source code requires knowledge of code and even phone hardware. I'm guessing it's not for you just yet
obsanity said:
Sounds like you should have read more.
When you open the bootloader (the lock) it will wipe your personal data off the phone (not SD storage). This just means you get it as if you just bought it from the store. There is no way around it but happens only once and you'll never have to do it again. Unless you lock it back
Once the bootloader is unlocked you can now flash a custom recovery such as CWM which will let you manage and back up your phone with whatever ROM you want/have.
Once recovery is on your device you also have to root the phone. For this you'll need a zip flashable file with the superuser apk and SU binary files. Flash it in recovery and you should be good to go.
The last step is to install a ROM of your choice. You can just run what the phone has and it will work fine and even take updates without a problem. However, every time you want to flash something you'll need to flash CWM again because the stock image flashes the default recovery on reboot. There is a file you can delete to prevent this from happening. I forgot the path so look around. However, I would recommend you flash a stock ROM which already comes loaded with good stuff and all other things are done for you Just stop by the development section and pick a ROM you like.
Naroid is just a backup.
Oh, and BTW, mocking around with ICS... I would leave that for later. First get your head around basic flashing/rooting stuff. Changing the source code requires knowledge of code and even phone hardware. I'm guessing it's not for you just yet
Click to expand...
Click to collapse
i was going to write something similar. toonhead85 you should do a bit more research and reading before you start hacking on your phone. youve hearts in the right place, but youre not quite ready just yet. at least take small steps at first
A little more clarification or nandroid backups:
Nandroid is a specific type of backup of the phone's system files. I think that includes system rom and radio. I not sure if any data is included in the backup. You should make a nandroid backup of the stock rom bbefore you flash any custom roms. If something goes wrong with a rom flash or if you want to restore to a previous stock or custom rom, you can restore from the backups you have made. You create these nandroid backups by booting into recovery and selecting the backup option (I think maybe named backup and restore). Backups are usually found on your SD card, but you can copy them to your computer to save additional copies.
If you want to also backup apps, get a good backup program from the market. Two that I have used are Titanium Backup for Root and MyBackups for Root. They can backup and restore apps and data as well as system data.
Thanks for all of the amazing replys. I do know that I am not at the point where I wanna muck around in the system to much as this is my one and only phone. But I would like to at some point.
But something I wanna know is this: If in flash CWM, can I use it without root? Say to make a backup of the stock rom before flashing SU? I only ask because I am currently at work and can't test the idea.
Another question is this: I know how to get to the stock recovery, but from what I read you use the VOL UP to get the "Menu". When I push any (hardware) button I get nothing and the image being displayed is an Android with a triangle and there is an exclimation point in it. Any thoughts?
a nandroid saves everything in your phone, just how it is at that moment. and when you restore it, your phone goes back to that very moment you made that nandroid backup. all your data remain. everything. its like you didnt do anything in between backing up and restoring
simms22 said:
a nandroid saves everything in your phone, just how it is at that moment. and when you restore it, your phone goes back to that very moment you made that nandroid backup. all your data remain. everything. its like you didnt do anything in between backing up and restoring
Click to expand...
Click to collapse
and you need root to use NANDROID? Or just an unlocked bootloader and to flash it over?
toonhead85 said:
and you need root to use NANDROID? Or just an unlocked bootloader and to flash it over?
Click to expand...
Click to collapse
unlocked bootloader
FANTASTIC!!! Thank you all so very much!!
simms22 said:
unlocked bootloader
Click to expand...
Click to collapse
And CWM recovery.
You don't need root to backup but remember that when you reboot it will flash back to stock recovery (the triangle). You can simply repeat the adb command to flash CWM again.
Sent from my Nexus S 4G
And CWM recovery.
You don't need root to backup but remember that when you reboot it will flash back to stock recovery (the triangle). You can simply repeat the adb command to flash CWM again.
Click to expand...
Click to collapse
So I could flash unlock my bootloader > flash CWM > Make a backup and save it to my computer then when i reboot my phone it would automatically reflash the stock recovery? and if this is correct, then all i would need to do is flash CWM to restore the saved backup?
So here's a question, is it the action of flashing SU that keeps the phone from removing CWM and reinstalling stock recovery?
You must rename the /system/etc/install-recovery.sh file or it will keep replacing the stock recovery. See this post, item 2.
Just got T-Mobile OTA 1.63.531.2
I can't get it to flash with CM Recovery. Tried with sig verification off. Phone should be s-offed.
Here it is if anyone wants:
http://lts.cr/Bhqv
.....next time post in the general. And rename it PG59IMG.zip and flash it in hboot
Thanks. I posted here so someone can see the source for developing if needed.
How do I get to hboot again with cm recovery?
pull your battery then put it back in and hold volume down and power. Then it will say confirm and press yes
Revolutionary hboot finds the zip file, does the loading bar but then does nothing. Have to choose fastboot, recovery, factory reset, simlock or image crc.
well it shouldve flashed...idk what to say....is in the root of the sdcard and named PG59IMG.zip
Yup I'm going to try the variant at
http://forum.xda-developers.com/showpost.php?p=23802172&postcount=7
This type of file is not a file to flash with the bootloader
Ran into this before trying to manually update a mytouch 4g
Is a regular update file like we used to do with update files on nexus one a so forth.
They have changed the way the updates work though and can not be flashed manually from what I have seen..
Needs to be in like a secure location probably /cache/ota or something like that.
Crap, so what do I do? Do I need to use that full update that does seem to work? But that also does a wipe?
ohh ya your right now that i look at the update.zip....just download the full update and flash that in hboot...dont forget to rename to PG59IMG.zip
Anyway to avoid a wipe?
well backup all your apps with titanium backup...then restore them with titanium
I've manually flashed the OTA updates that come to the phone. They flash thru stock recovery, not hboot or CWM. I don't think it matters what you name it, you just select it. And I'm not positive, but it might require a fully stock device.
Edit: I was S-OFF when I did tho. I think Blue might have tried with S-ON, and it wouldn't happen. Can't remember for sure tho
lol too much work to get stock recovery...just let him flash the full image
xmc wildchild22 said:
lol too much work to get stock recovery...just let him flash the full image
Click to expand...
Click to collapse
Ah yeah, I didn't read the whole thread carefully enough. But in any case, just letting people know those OTA update packages do work in stock recovery, lol.
aw man, i want stock recovery now. i have way too many customizations to lose it all
wing_addict_usa said:
aw man, i want stock recovery now. i have way too many customizations to lose it all
Click to expand...
Click to collapse
You can DL and flash stock recovery easily enough, just go to Blue6IX's Developer Reference thread, and go to the Recovery section. It could be worth a try, but I'm not sure the update will work with your customized setup. Might have to do as xmc suggested.
You need a stock recovery to flash an OTA - as mentioned above, it's not a PG59IMG.zip type of file or any other that hboot can process.
Custom recoveries can't process this type of update.
This thread should probably be in general, as it's more of asking for help then providing a solution.
Sent from a digital distance.
I have a zip I made the other day I named it some crazy file name and flashed in cwm, It's bone stock deodexed thanks to blue....while I'm getting ready for Easter I can upload the ROM or whatever....It's a simple kitchen zip
Sent from my myTouch_4G_Slide using Tapatalk
Hi everyone... I've tried searching and seen references to this kind of thing, but no download links or guides...
So I've got my Nexus S (bootloader unlocked, rooted, stock 2.3.4 until attempting the following, I have no Sim card in this phone), and I tried to flash 2.3.6, and while the update appeared to run just fine, the wifi won't turn on, just gives "error". So I attempted several things, reflashing the update, flashing the 4.04 update (which was the original point), etc, but they all give the following; installation aborted, assert failed, error in xxx.zip, "status 7".
Anyways... I'm a bit at a loss, I've never had this problem, or any problems flashing ROMs on other phones or updates. It seems no update.zip, or any .zip, will install. Back in my captivate days, there was a very handy program called Odin, and it had a master clear functionality that brought you back to the stockest of stock. Ideally... is there a tool like this for the Nexus S? I don't care about whether or not it re-locks the bootloader, I can unlock it again in just a couple minutes... but I need help.
I've read guides about "return to stock" but they all involve flashing a .zip. I need a way to push past that, and get back to 2.3.4, or alternatively, a way to completely reinstall 2.3.6.
I know an Odin exists for the Nexus S, but is there a way to use that to reset to stock?
Thank you so much anyone who can help...
Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
And as always, make sure you backup properly before flashing -anything-.
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.
Harbb said:
Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
Click to expand...
Click to collapse
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Harbb said:
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.
Click to expand...
Click to collapse
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?
Dareoth said:
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
Click to expand...
Click to collapse
Some people supposedly had troubles with the ICS update and keeping all data as-is, though i've not experienced it myself, but it is definitely possible and with such a big update, if it's in your power to start fresh it is always the best option. It was more of a general statement, not directed at your situation - something to keep in mind
Dareoth said:
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Click to expand...
Click to collapse
You can flash the latest CWM through fastboot from your PC or Mac, you can grab the latest file from here. Name it whatever you like and put it in a known folder (preferrably current folder) and : fastboot flash recovery recovery.img
Dareoth said:
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?
Click to expand...
Click to collapse
Of course i do
Great, I'm all set now. Thanks so much.
(Also for linking to that ref guide again, I had read it three times, but I didn't get how to use it until I went in going, I just need the fastboot commands, which is all that guide gives.)
Your welcome mate. All you need for that is setting up the android SDK or essentially downloading platform-tools seperately. There are guides all over the place describing how to do this for Windows, Mac and Linux as it is no different from getting oem unlock to work, they're just mostly disguised as rooting guides.
Once you do it the first time it's quite simple, but it can definitely be confusing before that
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
I heard there are problems flashing stock rom with CWR if the stock recovery isnt removed? Thats why I dont know if I should flash the stock image.
Is the process of flashing rom with CWR recovery the same as with stock recovery?
My phone is the i9023.
Thanks a bunch in advance.
Gambler_3 said:
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
Is the process of flashing rom with CWM recovery the same as with stock recovery?
Thanks in advance.
Click to expand...
Click to collapse
Baseband version? under about phone
billchen0014 said:
baseband version? Under about phone
Click to expand...
Click to collapse
i9023xxki1.
Sorry should have specified my phone in the OP.
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
You suppose thats better to do manually so I will have latest version of recovery and superuser?
And yes I am aware of the data loss waited sometime to finish all my games now I am ready to lose all my app data.
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
Do it this way. The one click is fine but using Android SDK and going through all that will help you in the long run. This way you know the process in case something goes wrong. It may be confusing at first but worth it. It will teach you a lot more than flashing a one click!
I learnt a lot from this and feel much more experienced and capable because of it. I know I will be able to solve any major issues using Android Debug Bridge (adb).
Okay then I am gonna try the manual way and gonna take out time for it. Now I just need to know what do I flash once I have unlocked bootloader and installed CWR?
I just want the stock google rom and receive OTA if nexus S continues to be supported by google.
You won't need to reinstall the ROM if you are currently on 4.0.4. The ROM stays there as-is. Feel free to do your wipes in recovery and reflash stock 4.0.4 through CWM if you must. You flash CWM to your phone and then superuser through CWM.
Steps:
Setup ADB/fastboot
Bootloader --> fastboot oem unlock --> agree
Bootloader --> fastboot flash recovery recovery.img --> this will give you CWM
Recovery --> flash superuser.zip and, if you must, wipe and reflash ICS (flash su AFTER this if done)
Reboot --> bingo
Also note, with stock ROMs it will replace your current recovery with stock recovery on each boot. If you want to keep CWM, delete /system/etc/flash-recovery.sh when you first boot. You'll have to reflash recovery afterward and it will stick.
Oh I was of the impression that unlocking bootloader wipes everything means it wipes the OS as well. That is nice if it's just data and not the OS, dont think I would reflash it if it's not needed.
Can you explain what you mean by will have to reflash recovery? I will have to do that even if I delete that file on first boot? And whats the drawback if I dont delete that file and stick with stock recovery?
As soon as you boot into stock android it will replace the recovery. So if that file is there on first boot, it will replace it while booting and you will be without CWM (stock instead). After first boot you can delete the file (you can reflash a ROM which has this deleted, or delete it yourself from a stock ROM, or even use adb or a recovery-based file manager to delete the file, then you won't have this problem at all) and it will no longer reflash stock recovery, but you would already have the stock one and need to flash CWM one more time to get it to stick. Easiest way is to just flash CWM and delete it within android imo, saves mounting commands and the such.
No downside really. If you need to flash something for one reason or another you'll just have to reflash CWM before you do so. Once rooted, ROM Manager can do this for you within android anyway.
I had already downloaded and installed the drivers from the one click root thread and my computer shows the android adb thing when I connect my phone with USB debugging.
But as you guys suggested I am gonna do the manual way. So do I just skip the installing driver on computer in the part 1 of this guide?
http://forum.xda-developers.com/showthread.php?t=1007782
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Gambler_3 said:
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Click to expand...
Click to collapse
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
DeuXGod said:
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
Click to expand...
Click to collapse
He has the i9023 to my knowledge. It is completely normal, though. Bootloader and recovery for i9020 and i9023 series are the same, this can be attributed to the issue with 4.0.3 recovery backlight not turning on.
If fastboot recognises your phone in the bootloader (the fastboot menu), your drivers are installed an working perfectly.
Finally got to the unlock bootloader screen, didnt do it just yet but now I know how to do it.
I must say the guide is a bit outdated, the software has changed quite a bit seems. The most frustrating part was that the fastboot file is actually in the platform tools folder instead of the tools folder which I didnt figure for a while. I will hold off rooting when I have a whole day off because once I lose everything I would be very anxious to get my phone back to normal which will take time.
Thanks for the help harbb, if I have any problem flashing recovery and superuser I will come back for more help.
And yes I have the LCD version i9023.
Btw the guide said the fastboot will be in the tools folder but the tools folder had a read me that "adb has moved to the platform tools folder" this is how I figured to go to that folder and thats where the fastboot file actually was.
Now it says I should put the recovery image in the tools folder so should I do that or put it in the platform tools folder?
In the instructions for the flashing recovery I am not understanding one thing.
6 - Then back on the SNS select Power Off (Reboot also works)
Part 4 - Root
1 - Power ON the SNS
So after flashing recovery I have to reboot? Since I am on stock rom that would bring back the stock recovery so how would I flash superuser then?
If I delete the stock recovery can I still get OTA updates?
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Harbb said:
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Click to expand...
Click to collapse
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Gambler_3 said:
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Click to expand...
Click to collapse
Good work, been wandering what you were up to on this
Hope you enjoy the possibilities.