Hey guys so i got a used Atrix 2 AT&T (MB865) running 2.3.6. Every time i reboot the phone all the data seems to get wiped and the android setup screen appears. I tried to FXZ to 2.3.5 using RSDLite and the correct replacement packages and the phone goes through the process but when it says its done the phone goes into stock recovery. I try rebooting out of stock recovery and the phone boots back into 2.3.6 with the setup screen but the problem is still there. Also, when i try to OTA to ICS the update installs, but the phone goes to stock recovery after reboot. Please help
Atrix 2
(MB865)
Android version 2.3.6
system version 55.13.25.MB865.ATT.en.US
Baseband version 2011-11-16 23:52 Off.Bld
LUD_EDISION_R1D7_PATCH_36_111116_2336
Webtop version WT-1.3.0-176
Kernel version [email protected] #1
Build number 5.5.1-175_EDMR1.25
Try doing a factory reset or stock recovery reset and see if that sticks through a reboot.
ΧΔΑ Fraternity's Godfather. Read About Our History!
Apex_Strider said:
Try doing a factory reset or stock recovery reset and see if that sticks through a reboot.
ΧΔΑ Fraternity's Godfather. Read About Our History!
Click to expand...
Click to collapse
Sorry man i tried both and its still stuck on 2.3.6 and wipes on reboot
Popwii said:
Sorry man i tried both and its still stuck on 2.3.6 and wipes on reboot
Click to expand...
Click to collapse
Charge your battery up, and try using RSD to flash the Official ICS image. Maybe something isn't getting patched or overwritten in the upgrade to ICS.
The ICS image can be found here, and if you don't know how to use RSDlite, check the noob guide. All the details are there.
41rw4lk said:
Charge your battery up, and try using RSD to flash the Official ICS image. Maybe something isn't getting patched or overwritten in the upgrade to ICS.
The ICS image can be found here, and if you don't know how to use RSDlite, check the noob guide. All the details are there.
Click to expand...
Click to collapse
Tried flashing the ics file and it stops at 4/19 and says Failed mbmloader is not returning Help
Popwii said:
Tried flashing the ics file and it stops at 4/19 and says Failed mbmloader is not returning Help
Click to expand...
Click to collapse
First, make sure your drivers and RSDlite are up to date. This isn't totally necessary, but you might as well have a clean slate to go from. So make sure your phone is unplugged from your pc, uninstall MotoDeviceManager, reboot, then install it again from here.
RSDlite 6 is here
After everything is fresh, connect your phone and give it a few minutes to detect and install your drivers. Once that's done, boot into fastboot and verify that it sees your device, if you're already in fastboot then just verify.
Code:
fastboot devices
On your phone screen it should tell you what bootloader version you have, it should say 0A.72, if not, then stop and post back what it says. Otherwise, open RSDlite, and try to flash the Official ICS FXZ you downloaded previously. By the way, the FXZ should be named InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip and the MD5sum should be 2BF9CCD528C05D26523ACC5B38AC76C6 if neither of those match, you need to make sure you have the right FXZ and make sure that the MD5sum matches what I posted.
So, if all is well and everything checks out, point RSDlite to the FXZ and start the flash, be patient. If it still fails, then you might try this. It's a way to flash the Official AT&T ICS FXZ without RSDlite, just download it, extract it, and follow the simple instructions in the readme.txt. Make sure RSDlite is closed before you run the .bat file. If you have to resort to this method, and it works for you, make sure you find Alteredlikeness around here and thank him, he put the script together.
If none of that works, then post back and we'll go from there.
Ok so i booted into fastboot and it says the bootloader is 0A.65
Popwii said:
Ok so i booted into fastboot and it says the bootloader is 0A.65
Click to expand...
Click to collapse
Alright, your bootloader is still for 2.3.6, obviously the OTA attempt never flashed the new one, or it never went properly. You might download the 2.3.6 FXZ here the MD5 sum for it is FCC0FBFDEDEAE084F90E34BF2523EB27
Flash it with RSDlite, that will hopefully get you on a clean and stable GB 2.3.6 After that, if you want to get on ICS and need some help, post back, or if getting back to 2.3.6 doesn't work, post back.
Um ok so i tried flashing that file and it stopped at 3/20 flash mbmloader mbmloader.bin phone return fail
Popwii said:
Um ok so i tried flashing that file and it stopped at 3/20 flash mbmloader mbmloader.bin phone return fail
Click to expand...
Click to collapse
How did you get into the state you're in originally? Did you try to flash something? A rom? A FXZ? You said you got a used Atrix2, was it messed up from the get go? Anyway, download this unzip it and follow the directions in the readme.txt. You'll need to unzip the Official ICS 4.0.4 FXZ that you downloaded previously as well. Basically unzip the ICS FXZ on your desktop (not the 2.3.6), then unzip the restore script and put everything in your unzipped 4.0.4 FXZ, put your phone into fastboot mode and run the restore-to-ics.bat file. Post back with results.
*Note - keep an eye on your bootloader version, if it changes from 0A.65 do NOT try and flash anything Gingerbread, you'll have to stick strictly to ICS if that changes.
Alright so i copied the batch files into the ics fxz and when i try flashing after the bootloader flashes the atrix2 says flash faliure at the top and when the entire flash is done it just returns to fastboot as if nothing happened. Also, when i reboot the phone the first time after the flash it boots into stock recovery
Popwii said:
Alright so i copied the batch files into the ics fxz and when i try flashing after the bootloader flashes the atrix2 says flash faliure at the top and when the entire flash is done it just returns to fastboot as if nothing happened. Also, when i reboot the phone the first time after the flash it boots into stock recovery
Click to expand...
Click to collapse
I'm running out of ideas. Since you can get into recovery, maybe try putting the ICS OTA on your SDcard. From the recovery, do a factory reset, wipe the cache, then try updating from external storage.
If all of that doesn't work, you might try another USB port, or another computer, and try RSDlite and the ICS FXZ again. According to your bootloader, you're still on 2.3.6, so the ICS FXZ should work and just replace everything. Maybe Jim or someone can help you along.
Here is a link to the 1st ICS leak, you can put that on your SDcard and flash it from recovery. Also, since it is the 1st leak build, you can restore to GB using a specific method outlined here. But if you can at least get the ICS leak to flash, you still have an option to update to the Official ICS.
Do not try to flash GB once you update. If you manage to get on ICS leak 1, it is possible to flash GB, but it is a modified version. Just to be clear.
41rw4lk said:
I'm running out of ideas. Since you can get into recovery, maybe try putting the ICS OTA on your SDcard. From the recovery, do a factory reset, wipe the cache, then try updating from external storage.
If all of that doesn't work, you might try another USB port, or another computer, and try RSDlite and the ICS FXZ again. According to your bootloader, you're still on 2.3.6, so the ICS FXZ should work and just replace everything. Maybe Jim or someone can help you along.
Here is a link to the 1st ICS leak, you can put that on your SDcard and flash it from recovery. Also, since it is the 1st leak build, you can restore to GB using a specific method outlined here. But if you can at least get the ICS leak to flash, you still have an option to update to the Official ICS.
Do not try to flash GB once you update. If you manage to get on ICS leak 1, it is possible to flash GB, but it is a modified version. Just to be clear.
Click to expand...
Click to collapse
It seems that he previous owner put ubuntu on the phone because when i use root file explorer i see folders like /osh so i was wondering could that be conflicting also it says 2.6 gb available out of 7 gb so maybe something else is installed that is protecting from fxzing
Popwii said:
It seems that he previous owner put ubuntu on the phone because when i use root file explorer i see folders like /osh so i was wondering could that be conflicting also it says 2.6 gb available out of 7 gb so maybe something else is installed that is protecting from fxzing
Click to expand...
Click to collapse
Most likely seeing directories from webtop, and ICS does away with webtop, so it shouldn't affect FXZing. What state is the phone in currently? Can it boot? (I assume yes because you mentioned a root file explorer). Did you try to update through the stock recovery? If it can boot, I would try and get it back to as stock as possible, factory reset and all that, wipe cache, dalvik. Double check your software version, model, kernel. firmware, all that and verify that you have a 2.3.6 AT&T device.
41rw4lk said:
Most likely seeing directories from webtop, and ICS does away with webtop, so it shouldn't affect FXZing. What state is the phone in currently? Can it boot? (I assume yes because you mentioned a root file explorer). Did you try to update through the stock recovery? If it can boot, I would try and get it back to as stock as possible, factory reset and all that, wipe cache, dalvik. Double check your software version, model, kernel. firmware, all that and verify that you have a 2.3.6 AT&T device.
Click to expand...
Click to collapse
Yes the phone boots but needs to be re activated every boot and after 2-3 it reboots by itself. Also, the factory reset doesnt seem to work because it just restarts my phone when done through android and when doing the hard reset way through stock recovery it doesnt fix the problem
Popwii said:
Yes the phone boots but needs to be re activated every boot and after 2-3 it reboots by itself. Also, the factory reset doesnt seem to work because it just restarts my phone when done through android and when doing the hard reset way through stock recovery it doesnt fix the problem
Click to expand...
Click to collapse
Install a custom recovery if you don't have one, I'll attach Atrix2Bootstrap just in case. Reboot into custom recovery, and try to factory reset from there. Even if that doesn't work, try to wipe the cache, the dalvik, and your battery stats, then fix permissions. Post back with what worked or didn't work, and make sure the battery is charged up.
41rw4lk said:
Install a custom recovery if you don't have one, I'll attach Atrix2Bootstrap just in case. Reboot into custom recovery, and try to factory reset from there. Even if that doesn't work, try to wipe the cache, the dalvik, and your battery stats, then fix permissions. Post back with what worked or didn't work, and make sure the battery is charged up.
Click to expand...
Click to collapse
I dont think i can install a custom recovery because everytime i root it reboots and the root isnt installed.
Popwii said:
I dont think i can install a custom recovery because everytime i root it reboots and the root isnt installed.
Click to expand...
Click to collapse
Since you can at least boot in android, you should verify some info.
Go to Settings > About Phone and note
System version -
Model number -
Firmware-
etc -
Post back with all of your info, be specific.
Download superuser from the market and install it.
Open your command prompt and type
Code:
adb shell
su
See if you get a permission denied, or if you get root #
Post all of the requested info.
41rw4lk said:
Since you can at least boot in android, you should verify some info.
Go to Settings > About Phone and note
System version -
Model number -
Firmware-
etc -
Post back with all of your info, be specific.
Download superuser from the market and install it.
Open your command prompt and type
Code:
adb shell
su
See if you get a permission denied, or if you get root #
Post all of the requested info.
Click to expand...
Click to collapse
(MB865)
Android version 2.3.6
system version 55.13.25.MB865.ATT.en.US
Baseband version 2011-11-16 23:52 Off.Bld
LUD_EDISION_R1D7_PATCH_36_111116_2336
Webtop version WT-1.3.0-176
Kernel version [email protected] #1
Build number 5.5.1-175_EDMR1.25
Popwii said:
(MB865)
Android version 2.3.6
system version 55.13.25.MB865.ATT.en.US
Baseband version 2011-11-16 23:52 Off.Bld
LUD_EDISION_R1D7_PATCH_36_111116_2336
Webtop version WT-1.3.0-176
Kernel version [email protected] #1
Build number 5.5.1-175_EDMR1.25
Click to expand...
Click to collapse
You should try to downgrade to 2.3.5 and start from the beginning. Since your system is borked and you can't update, hopefully downgrading will at least get you to something stable that you can work with. The noob guide will tell you how to downgrade from 2.3.6 to 2.3.5, just pay attention because you'll most likely have to replace some FXZ files since the 2.3.6 you're on is most likely from an OTA.
About 1/3rd of the way down the page you'll see "How to flash the FXZ once applying the OTA update and get back to 2.3.5", follow those instructions.
Related
Hi guys,
Here's what happened. My phone ran out of battery and died while I was out earlier. I came home, charged it up, and turned it on. I get a notification saying that a system update to 4.04 is available. I went ahead and downloaded it, then rebooted my phone. When it started back up, all I got was the android and an exclamation mark inside a triangle. I couldn't turn it off, so I pulled the battery and turned it on again. This time it booted up fine, but when I check for system updates, it says my system is up to date, but I'm still on 2.3.6. How do I update my phone to 4.04??
Here's some background info about the phone.
Nexus S I9020A
Baseband version I9020AUCKF1
Kernel version 2.6.35.7-gf5f63ef [email protected] #1
Build number GRK39F
The phone is rooted with the Superuser app installed, but the bootloader is still locked to my carrier, Rogers. I used something called DooMLoRD root to root my phone. All I had to do was run a batch file that did everything for me. I'm assuming that the failure to install ICS properly was due to the root.
Please help me figure this out! Tell me what I need to do and I'll do it.
ICS failure would have been due to the root. First, you'll need to unroot. To do that, assuming you have used the bog-standard DooMLoRD script, there is a link in the original thread that gives you a way to unroot. Pretty straight forward, this may or may not work to re-root 4.0.4 though.
After this, try opening up the dialer and typing *#*#checkin#*#* - hopefully an update will show. If not, you can probably manually update from here, assuming you are on stock 2.3.6 (and now unrooted).
Alright, I've unrooted using the method advised. Using the dialer, I typed *#*#checkin#*#*, and I get a notification that says "checkin succeeded", but no new updates are available.
I took a look at the thread you suggested, and on page two there seems to be a .zip file that I'm assuming contains the update. How do I install the update from the .zip file?
full installation instructions: http://andwise.net/?p=275
I followed your instructions, and I get a Status 7 error, and the installation is aborted. I did a little reading and found that the status 7 error has something to do with Google making it so that you can't manually update using the stock bootloader.
Apparently the only way for me to get 4.04 involves a full wipe, unlocking the bootloader, then flashing CWM, then flashing 4.04 using CWM. Is there any way to avoid all of this so I can keep my data?
error 7 is not because you didn't do a full wipe. you can update without a full wipe, however if you have problems later full wipe could fix it.
could you type this in the command prompt:
adb shell getprop ro.build.fingerprint
and let me know the output of it
C:\Users\sm1ke>adb shell getprop ro.build.fingerprint
adb server is out of date. killing...
* daemon started successfully *
google/sojua/crespo:2.3.6/GRK39F/189904:user/release-keys
OK so you have to use the file for i9020A. Be sure to backup before.
Sent from my Galaxy Nexus using xda premium
andwise said:
OK so you have to use the file for i9020A. Be sure to backup before.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, I used the file for the i9020A, as referenced in your instructions.
http://android.clients.google.com/packages/ota/google_crespoa/IEzMw3FU.zip
Copied the update to the SD card, renamed the file to "update.zip", then turned off the phone. Booted into fastboot mode, went to Recovery, and I got a warning sign. Pressed power, then vol up to enter main recovery, then selected apply update from /sdcard, and chose update.zip from list. At this point I get the status 7 error.
Btw, thank you so much for trying to help me out guys! I really appreciate it.
You can't apply the ota update zip in stock recovery manually anymore.
Boot the phone normally and see if the ota notification comes.
Or look into how to do it manually with cmw etc
I can't say for sure since i don't use stock recoveries or the 850MHz variant, but i'm pretty sure it is 4.0.3 recoveries and greater don't allow manual updating, 2.3.6 should allow you to do it perfectly fine. However some other people have said they had issues with updating the i9020A, pretty sure with a status 7 error.
Guaranteed way is unlocking bootloader method, will remove all personal data though. Best way, for now at least, is give it a few days and follow the steps in the update thread (OP), maybe they'll work for you. Or maybe it'll just pop out for itself soon.
Sorry i can't really help more than that, hope you can get yourself on stock ICS soon
just force into CWM.
flash ICS 4.0.3
flash incremental update 4.0.3 -> 4.0.4.
ur problem solved
As harbb says for 4.0.3 you need cwm for 2.3.6 usually no but you have to have your bootloader unlocked. In fact I would suggest to flash to cwm anyway and make nandroid backups.
Sent from my Galaxy Nexus using xda premium
Alright, thanks guys.
I'll look into flashing CWM and all that, never done it before.
Its easy http://andwise.net/?p=268
Sent from my Galaxy Nexus using xda premium
albundy2010 said:
You can't apply the ota update zip in stock recovery manually anymore.
Boot the phone normally and see if the ota notification comes.
Or look into how to do it manually with cmw etc
Click to expand...
Click to collapse
I successfully applied the 4.0.4 update from stock recovery from 2.3.6 on a i9020a.
Sent from my Nexus S (Telus ) using xda premium
rhagemeyer said:
I successfully applied the 4.0.4 update from stock recovery from 2.3.6 on a i9020a.
Sent from my Nexus S (Telus ) using xda premium
Click to expand...
Click to collapse
Which update file did you use?
try going from 2.3.6 to 4.0.3 then do the incremental update to 4.0.4
Alright, so I've decided to try using CWM, since nothing else seemed to work. I unlocked the bootloader, and flashed the CWM recovery image. Then I went into Recovery, this time it looked a little different (blue text, gear and hat image in the background). I went to the option to install update from sdcard, chose the update file for 2.3.6 to 4.04 for the i9020a, and I'm still getting a status 7 error.
I'll try updating from 2.3.6 to 4.03, then from there going to 4.04, but I read about the radio not working on 4.03 or something. Will I have to worry about that, or will the update to 4.04 fix the issues from 4.03?
Also, if anyone has a link to the 4.03 OTA for i9020a I'd appreciate it.
sm1ke said:
Which update file did you use?
Click to expand...
Click to collapse
I believe I used IEzMw3FU.zip
Richard
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.
HOLD ON UPDATING!!! There are a bunch of people having data and wifi issues with this release. I have not had them but that doesn't mean you won't. Update at your OWN risk. You've been warned.
If you would like to update the software but not the baseband (probable cause for data/wifi issues) then just use my Nandroid linked below and leave your current baseband.
To everyone that keeps trying to relock their phones and flash the RUU to get the update it will NOT work. If you look at your software version you will see that it has added and R2 in it. I don't know why it does this, maybe it's a why for HTC to screw over the hackers yet again. Here is how to get the update.
There are 2 ways to get the update.
First: Use my Stock Rooted 1.84 Nandroid that I posted here. Simple but you will have to flash the radio separate.
Second: More steps but worked for me. NOTE: Only works if your on stock rooted phone. Will not work on custom ROM. Get Stock 1.53 Nandroid here. Credit to Reviewers for posting.
This will NOT wipe your phone nor do you need to wipe your phone if you are on Stock Rooted.
1a - This step only needed if you are on a custom ROM. If your on Stock Rooted then proceed to step 1b.
Download the above linked Nandroid (for 1.53) and restore it in Recovery. Reboot.
1b - Download this tool and use it to flash stock recovery. It will auto reboot your phone into bootloader so just start with your phone normally booted.
Credit goes to hasoon2000 for creating the tool!
2 - Your phone will reboot, once booted back up go to Settings>About Phone>Software Update. It will find the update and download then prompt to install. Select yes and let your phone update and reboot.
3 - Fire up the tool from step 1b again and this time flash CWM Recovery (whichever you prefer).
4 - After reboot is complete reboot again back into recovery and flash this to restore SU permissions (seems the update breaks them, at least for me).
Credit goes to Chainfire for creating this!
5 - Reboot, Done.
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
DigitalMonk said:
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
Click to expand...
Click to collapse
Did you totally wipe your phone? If not then the update is in your " download" folder
Sent from my HTC One S
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
DigitalMonk said:
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Try deleting that file and checking again. Back it up to your computer first of course.
setzer715 said:
Try deleting that file and checking again. Back it up to your computer first of course.
Click to expand...
Click to collapse
Didn't work for me. I got about 2 downloads out of the servers, and then they aren't sending it anymore. Weak.
No go so far. Copied it to my PC, deleted it from my Download folder, re-booted and then checked for an update 3 different times and nothing so far.
With all of the people having wifi and data issues TMO may have stopped sending it until they figure out what is going on. I do know for a fact that TMO tests any software update the send so something may have gone haywire with it. Maybe got radio mixed up.
DigitalMonk said:
I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Wait.. I didn't know this. You mean even if we "unroot" and flash stock recovery (and using stock ROM of course), we cannot flash this ourselves?
I currently have the CWM touch recovery and root, u/l bootloader, etc., and TMO has sent me 2 updates, both were in the Downloads folder. I didn't notice that it updated (as I never confirmed) but they obviously didn't install.
But I would have done the above if I had known we couldn't just flash it ourselves. WTF T-mobile?? Those of us who know how to flash a file should at least not be prevented from doing so (especially since we need to have the original recovery installed).
Sent from my HTC One-S (rooted), stock ROM
Hey there, So I got a problem. First off im not new to rooting and flashing custom roms been doing for some time now and im loving it. Heres my problem that I got on my rooted Atrix 2. I was running Gingerbread 2.3.6 then AT&T came out with Ice Cream so I did the update and before I updated message popped up and said once you update to Ice Cream you will no longer be able to switch to Gingerbread ok no big deal . So I updated everything went smooth. Phone rebooted started playing with the phone loved everything EXCEPT! I tried attaching picture to text message and if its to big to attach usually phone says to resize or cancel so I press resize and I get a message "saying message limit reached!?!" I never had no problem with Gingerbread so after using the new Ice Cream I decided to flash a rom 4.0.4 ICSupercharged Fixed Leak #2. Flashed rom no problem hoping it would fix the picture image resize problem NOPE! Still get same message. So I got pissed and got the 2.3.6 fxz.zip file and flash the phone BUT! while I was all hot! I forgot to BACK UP RECOVERY my phone. So after getting 2.3.6 back on my phone now when I turn my phone on it stay on at the Motorola Dual-Core screen sometimes restarts looping and just stays on same screen. So I know that in Android factory recovery I cant install any zip. files because they are not digitally signed so every time I try install update from sdcard I get error E: signature verification failed. I ran into this before but I had a back up made so I could recover phone. But not this time I need your help! Im stuck until I either have a signed custom image or stock recovery. Please help me I desperately need my phone to be back working. THANKZ!
Did you use one of the leaks from here or are you in the official ICS? If you're on the first leak, you can still get back to 2.3.5 or 2.3.6 safely. If you used the ota, or the second leak, I think you'll have to use the fxz found here:
http://forum.xda-developers.com/showthread.php?t=1961310
I just went to setting about phone and did check for update and Download ICS from AT&T installed it then I flashed the leak#2. I have the FXZ for 2.3.6 and 2.3.5 The FXZ worked when it was done the phone restarted and just loops and stays on Motorola Dual-Core Screen. I used the FXZ before and had this problem but last time I did a backup of the phone so after I used the FXZ I went into Stock Android recovery and used the back up. But another thing dunno but shouldnt the FXZ have a custom recovery/backup file in the zip. Oh and after doing the FXZ my phone is now unrooted says (S) that means its not rooted correct?
I got that FXZ from the link you gave me. Dont matter what zip I out and try to apply It says E: verification signature fail. Because its not Digital Signed.
white22b said:
I got that FXZ from the link you gave me. Dont matter what zip I out and try to apply It says E: verification signature fail. Because its not Digital Signed.
Click to expand...
Click to collapse
Wait, where are you trying to apply these zips from? Please tell me it is not the stock recovery. You MUST use bootstrap or bootmenu or similar to get CWM on your phone.
Fxz is to be used with rsd lite, not flashed in recovery. It'll return your phone back to stock, unrooted, no custom anything. After you use it you'll have to re root and install a custom recovery to flash any zips.
jimbridgman said:
Wait, where are you trying to apply these zips from? Please tell me it is not the stock recovery. You MUST use bootstrap or bootmenu or similar to get CWM on your phone.
Click to expand...
Click to collapse
Yes in stock recovery mode. Yea but can you install bootstap or bootmenu in stock recover mode its a APK file. I thought you can only install zip. files? And to root the phone i have to have it on and when you plug the usb cable to the phone you select charge only. I think I need someone to make a back up of their phone and send it to my email or something and then I can put it in my sdcard and go into recovery mode and try installing it.
white22b said:
Yes in stock recovery mode. Yea but can you install bootstap or bootmenu in stock recover mode its a APK file. I thought you can only install zip. files? And to root the phone i have to have it on and when you plug the usb cable to the phone you select charge only. I think I need someone to make a back up of their phone and send it to my email or something and then I can put it in my sdcard and go into recovery mode and try installing it.
Click to expand...
Click to collapse
If you can only get into recovery mode and can't boot you need to use the fxz. If you can boot into android, you install the bootstrap apk then allow it root permissions, and hit boot into bootstrap from within the app. You can then flash any ROM from there.
Sounds like you need to do some reading. I would not do any flashing or hacking until you learn the ins and outs of this phone. It is quite different from other phones since it has a locked bootloader.
Yea and now my phones battery is dead and I have a white LED light on?