[Q] I think I killed my Nexus S! Please help! (unlocking process/rooting stuff) - Nexus S Q&A, Help & Troubleshooting

So, this is what has happened so far:
I googled for a small and easy to follow guide to unlock my phone so that I can later on install a custom rom. I followed the steps provided here:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
What I didn't notice on the first place was the "UPDATE: DO NOT FOLLOW THIS GUIDE INSTEAD Please see new root method which works on all Nexus S and Nexus S 4G!" link. Don't ask why - really don't know.
The result was having my Nexus S stuck on a screen that shows Google logo on the middle and an unlocked padlock on the bottom.
It seemed, or to be exact, I figured out that, the problem was the .img file mentioned on some point in the middle of this.. tutorial.
So, I decided to follow the newer guide that can be found here:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
Although all went well (didn't have to go all over the same processes up to the .img installatin point), I ended up with the same screen that shows Google logo on the middle and an unlocked padlock on the bottom.
I figured out that I could just install a rom at this point, and decided that I should go back to stock. So, I followed this guide here:
http://nexusshacks.com/nexus-s-hacks/how-to-unroot-nexus-s-i9020ti9020ai9023/
But, when I choose to install the .zip file, I get this error:
assert failed: "getprop ("ro.product.device") == "crespo" || "getprop ("ro.product.device") == "crespo"
E: Error in /sdcard/i9020t_i9023.zip
(status 7)
Installation aborded
..let me add to this point that I have bought my Nexus S from EU, it is an i9023. Let me also add that all I wanted is to flash an ICS rom and I think I have ended with a f****d device I don't know what to do with!
Any help, really, would be so much appreciated since I need to use this phone. I have a backup for calls etc but I need some smartphone features!

I seriously doubt you killed your Nexus S. Temporarily disabled is more like it.
From off position, hold down Power + VOL-UP. You should be greeted with a screen with a green android and 4 options. If you can get there, that's the bootloader, and unless you manage to kill it (which is VERY hard to do), you can reflash everything from there via usb and adb.
What model Nexus S do you have? That's important for helping you to flash it.

nickmv said:
I seriously doubt you killed your Nexus S. Temporarily disabled is more like it.
From off position, hold down Power + VOL-UP. You should be greeted with a screen with a green android and 4 options. If you can get there, that's the bootloader, and unless you manage to kill it (which is VERY hard to do), you can reflash everything from there via usb and adb.
What model Nexus S do you have? That's important for helping you to flash it.
Click to expand...
Click to collapse
Yes, I can enter this menu - there already. My model is an i9023GSM.

OK, then you DONT have a dead phone. You just need to reflash it correctly.
I'm sorry I can't be helpful for longer, because I am at work,but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
On a side note, for ROM selection, are you looking for an Ice Cream Sandwich alpha ROM (android 4.0) (less stable) or the older Gingerbread ROMs (2.3.7)?

nickmv said:
OK, then you DONT have a dead phone. You just need to reflash it correctly.
I'm sorry I can't be helpful for longer, because I am at work,but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
On a side note, for ROM selection, are you looking for an Ice Cream Sandwich alpha ROM (android 4.0) (less stable) or the older Gingerbread ROMs (2.3.7)?
Click to expand...
Click to collapse
You gave me the good news so, thank you for that. Now, I should follow this guide and come back in case I have a problem.
As far as the rom, I wanted to flash an ICS since I cannot wait any longer for Google to release the official update. But right now, anything that can get my device up and running would be really good!

Edit: nvm. >_<

kijp15 said:
Why don't you just use shabby's one click root. Simple & much easier. Saves all sorts of troubles.
Click to expand...
Click to collapse
Will this solve the problem I'm facing? If yes, then it's fine by me.
Ok, just saw the edit, no worries!

nickmv said:
but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
Click to expand...
Click to collapse
OK, stuck already. On Part 2 what I understand is that I have to open the CMD and copy-paste the path to the "tools" folder? Because this is what I do, and after - since this is what I have understand - I type "fastboot oem unlock" and I get "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
What do I do wrong?
EDIT:
Tottaly stuck on Part 2. It seems that there is no fastboot.exe file inside "tools" folder. I don't think the problem is something else - I'm sure I give the right commands since I tryied for fun another folder I have with fastboot.exe inside and it worked - to be exact it just gave me a FAILED messsage since device is already unlocked. Plus, regarding Part 3, Step 1, the first file for download is missing so I used the second link and downloaded 5023-cyan file. Hope this was a right move to do.
EDIT 2:
Ok, here is the story so far: I followed the guide given step by step. The USB drivers has been installed correctly so the device can be connected to the PC.
In the "tools" folder there was no such fastboot.exe file so I manually added one that I've found on the newer guide given on the 1st post. The unlocking process is failing because the device is already unlocked.
I did manage to install after this, the 5023-cyan.img file since this is the only link working from Part 3, Step 1. This gone well too!
Now, I couldn't go on with Part 4, I mean, I could not install the .zip file as it describes so through recovery mode I installed the .zip file succesfully (confirmation message to Nexus S screen).
I reboot and still get the same Google logo on the middle and an unlocked padlock on the bottom.
I cannot understand what I do so wrong? Oh, I'm so disappointed..

OK, people, head's up! I did manage to install the latest stable rom of cyanogenmod and the phone is up and running! It means that somehow everything went well! Now, how do I return back to OEM? Because I just need to make things as they where before..
..or should I give cyanogenmod a chance?

http://forum.xda-developers.com/showthread.php?t=1063664 or use ROM manager and select Stock ROM (you should then receive OTA upgrades to 2.3.6).
On the latter: You colud just back up different ROMs and switch between them using CW.

skatastamoutrasas said:
Will this solve the problem I'm facing? If yes, then it's fine by me.
Ok, just saw the edit, no worries!
Click to expand...
Click to collapse
If you are still facing problems. Try locking your bootloader again with this method. Then it will let you go back on stock. Use v3 it is stable solid and easy to use.
Nexus S + CM9 kangs = Awesomeness

mixtapes08 said:
If you are still facing problems. Try locking your bootloader again with this method. Then it will let you go back on stock. Use v3 it is stable solid and easy to use.
Nexus S + CM9 kangs = Awesomeness
Click to expand...
Click to collapse
Can you give me a CM9 kangs link since as new here, I'm kinda lost?

Ok new problem this time! After I installed my 3rd rom (probably, a totall noob thing to do) which was the OEM one, I tryied to re-enter recovery mode to wipe all data and re-install the rom I want. But now I get this mark of the small green android with a big exclamation mark on top of his head. What is this new hell that found me?

skatastamoutrasas said:
Ok new problem this time! After I installed my 3rd rom (probably, a totall noob thing to do) which was the OEM one, I tryied to re-enter recovery mode to wipe all data and re-install the rom I want. But now I get this mark of the small green android with a big exclamation mark on top of his head. What is this new hell that found me?
Click to expand...
Click to collapse
Try re-flashing the recovery. Either threw rom manager or fastboot.
Fastboot flash recovery "nameofrecovery".img

kijp15 said:
Try re-flashing the recovery. Either threw rom manager or fastboot.
Fastboot flash recovery "nameofrecovery".img
Click to expand...
Click to collapse
Worked just fine! Thank you!

skatastamoutrasas said:
OK, people, head's up! I did manage to install the latest stable rom of cyanogenmod and the phone is up and running! It means that somehow everything went well! Now, how do I return back to OEM? Because I just need to make things as they where before..
..or should I give cyanogenmod a chance?
Click to expand...
Click to collapse
Nice, glad to see you managed to get it working. Honestly, the hassle is kind of worth it, because you learn more about the process anyways.
That being said, give CyanogenMod a chance. There's also several other ROMs. Unless you need stock OS for warranty service, I'd recommend going with one of the many custom ROMs we have here.
There are several minimalistic AOSP-built ROMs that mimic the feel of the stock OS, but are optimized for speed, and still have some very nice tweaks that you may enjoy. Just take a look through the dev section, and you'll see we have tons of options.

nickmv said:
Nice, glad to see you managed to get it working. Honestly, the hassle is kind of worth it, because you learn more about the process anyways.
That being said, give CyanogenMod a chance. There's also several other ROMs. Unless you need stock OS for warranty service, I'd recommend going with one of the many custom ROMs we have here.
There are several minimalistic AOSP-built ROMs that mimic the feel of the stock OS, but are optimized for speed, and still have some very nice tweaks that you may enjoy. Just take a look through the dev section, and you'll see we have tons of options.
Click to expand...
Click to collapse
It did worth the hassle, that's for sure. Now I think it's so easy to unlock a Nexus plus I now have a little more knowledge regarding Android .
I will stick with CM 2.3.7 as it looks just fine. I don't care about warranty, I don't think I will ever need the official service for a software issue. Now I have to re-install my apps, re-sync my accounts and setup the phone the way I want it. It will take a little more time.
But I'm glad that I pulled this through - with your help of course! Guys, you rock!
I wish that I'll be as helpful as you at the near future.

Today's latest CM9/ICS kang is here
I'd also recommend getting a custom kernel.
For batt life, morfic's SEUV kernel.
For reg performance, perhaps Matrix's kernel
MAKE SURE THAT YOU HAVE CLOCKWORKMOD PERMANENTLY INSTALLED BEFORE DOING THIS. It saves time if you mess up. Also, make sure you get the latest gapps HERE
Instructions:
1. Go to clockwork recovery
2. Select data/factory reset/wipe
3. Select clear cache as well
4. Adv Mounts and Storage > wipe /system (note, this wipes android off the phone. It's a good idea since youre going from ver 2.x to 4.x)
5. Choose "flash from zip" (or whatever it's called.....NOT flash from update.zip)
6. Flash the cm9 update file first, then flash the kernel of your choice, then flash the gapps file.
7. Back out of the menu and select reboot.
Take note though, that the new ICS OS has incompatibilities with certain apps while GPU rendering is turned on, etc. It'll prob reboot on you sometimes, etc. For the most part it's stable, but that's completely subjective.
If you do run ICS, make sure you turn on GPU rendering in Dev Options. It takes full advantage of the GPU for UI animations, etc. Sometimes there's a stray app here and there that doesnt play nice, and you'll notice if the window looks really tiny or funny. Turning it off will fix the problem.

nickmv said:
Today's latest CM9/ICS kang is here
I'd also recommend getting a custom kernel.
For batt life, morfic's SEUV kernel.
For reg performance, perhaps Matrix's kernel
Click to expand...
Click to collapse
Two questions:
The link you give me to download the ICS rom keeps loading for ever. So, I choosed this one instead:
http://forum.xda-developers.com/showthread.php?t=1356228
Right or wrong thing to do?
It it essential to install a custom kernel? I ask because I forgot to copy/paste the .zip file and due to lack of time, I procceded without it, installing the ROM and G-APPS.

Related

[Q] Stock OTA 3.2 to Tiamat Katana, is this possible?

My Xoom is completely stock and I just received and installed the 3.2 update. I am pretty disappointed in the SD card support and lack of other features. I held off on rooting and installing Tiamat before as I wanted to see what Google would give us, and well I think I have waited long enough to see that it pales in comparison to what you devs can do.
So now I would like to give the Tiamat kernel a try. So I read through several of the threads and on the Tiamat 2.0.0 Kernel thread it assumes you are on 3.1, where I am already on 3.2. As it took me several months to convince the wifey that I needed my Xoom I do not want to risk bricking it, so I am looking for some help.
-First, is it currently possible to go straight from complete stock 3.2 to Katana?
-Second, and much more difficult, can someone provide me step by step instructions? I've seen several of the threads out there, some of them are very helpfull, some get me part way, but none of them cover this exact upgrade scenario. This just makes me very concerned with doing something wrong or if something changed in 3.2.
I know this is a lot to ask, but I think there are a lot of people who would benefit from this information.
Thanks
HuckFinn said:
My Xoom is completely stock and I just received and installed the 3.2 update. I am pretty disappointed in the SD card support and lack of other features. I held off on rooting and installing Tiamat before as I wanted to see what Google would give us, and well I think I have waited long enough to see that it pales in comparison to what you devs can do.
So now I would like to give the Tiamat kernel a try. So I read through several of the threads and on the Tiamat 2.0.0 Kernel thread it assumes you are on 3.1, where I am already on 3.2. As it took me several months to convince the wifey that I needed my Xoom I do not want to risk bricking it, so I am looking for some help.
-First, is it currently possible to go straight from complete stock 3.2 to Katana?
-Second, and much more difficult, can someone provide me step by step instructions? I've seen several of the threads out there, some of them are very helpfull, some get me part way, but none of them cover this exact upgrade scenario. This just makes me very concerned with doing something wrong or if something changed in 3.2.
I know this is a lot to ask, but I think there are a lot of people who would benefit from this information.
Thanks
Click to expand...
Click to collapse
The quick answer to your question is Yes, you can go from stock 2.3 to Tiamat Katana 2.0 kernel, but you must be rooted.
Are you rooted? If so, and if you have already installed Clockwork Mod Recovery 3.2.0.0 (from solarnz' thread in Development) you can just flash the Katana kernel and you should be fine.
If you are not unlocked and rooted--you can follow the directions here:
http://forum.xda-developers.com/showthread.php?t=1170760
There are actually some more user-friendly (for noobs) instructions http://forum.xda-developers.com/showthread.php?t=1130996 in this thread, but for STEP 5 (ROOTING) you have to substitute the method from jase's post (above) for the instructions for Step 5 in the "idiot's guide" I can't find any 3.2 root files yet. It's the same procedure but a bit more hands on. No matter what you do, you will have to use adb to unlock your bootloader and root, so gather all the necessary files, drivers and print out your instructions.
One thing to know is never try to install a .zip file through adb...that will cause massive headaches. However, it seems pretty hard to actually brick one of these Xooms through updating and flashing. (Don't drop it into water, though!)
Thank you for the information. All the posts asking for help because something did not go right still have me pretty apprehensive. I am not at all interested in over clocking, so it is really the what I assume is proper SD card support and USB tethering that interest me the most.
HuckFinn said:
Thank you for the information. All the posts asking for help because something did not go right still have me pretty apprehensive. I am not at all interested in over clocking, so it is really the what I assume is proper SD card support and USB tethering that interest me the most.
Click to expand...
Click to collapse
It's only by rooting that you are able to get the full functionality of the Xoom. It's great as it is...HC 3.2 is very good and improved, but this device is made to driven like a sports car, not just sat in like a minivan.
okantomi,
Well I have gone back and forth on wether to root or not and you have been very helpful with pointing me to good information. I am hoping you do not mind answering a couple more questions.
-In the "Idiot's guide to flashing" you pointed me to it installed CWM before rooting. Is this the proper order or would you root first? I know I should just follow the guide and give it a shot, but that just seems odd.
-Can you explain to be the difference between the Tiamat kernels and the ROMs? My assumption is that the ROM would include the kernel, but I have a strong feeling that is incorrect. I have read posts of installing the ROM first and then the kernel and I am just more confused.
Thanks, one day I will get there.
HuckFinn said:
okantomi,
Well I have gone back and forth on wether to root or not and you have been very helpful with pointing me to good information. I am hoping you do not mind answering a couple more questions.
-In the "Idiot's guide to flashing" you pointed me to it installed CWM before rooting. Is this the proper order or would you root first? I know I should just follow the guide and give it a shot, but that just seems odd.
-Can you explain to be the difference between the Tiamat kernels and the ROMs? My assumption is that the ROM would include the kernel, but I have a strong feeling that is incorrect. I have read posts of installing the ROM first and then the kernel and I am just more confused.
Thanks, one day I will get there.
Click to expand...
Click to collapse
I've got to be quick...I have to do some work today, lol, but here goes:
Actually, follow the Idiots Guide regarding the adb, moto drivers setup.
Then follow this http://forum.xda-developers.com/showthread.php?t=1170760
It's got all the right files and steps, and though it's pretty much to the point, it's user friendly enough. It will get you rooted, I'm sure.
While the difference between ROMs and kernels is somewhat over my head, the ROM does contain the kernel (it's sort of an all inclusive package to tell the device how to behave, whereas the kernel manages particular functions, but not others. It's more limited.) Because the Honeycomb source code hasn't been released, the developers are somewhat limited in the ROM-development department, but they have been able to work wonders with kernels. However, the Tiamat 1.1 Rom for HC3.1 was great and the new ROM in development for HC3.2 will be great too, if the Katana kernal for HC3.2 is any indicator.
Sorry to be a pest but just want to make sure I understand.
A) Follow the idiot's guide steps 1-2, which covers Xoom driver installation and ADB installation.
B) Then follow the other link (How to root your Xoom from stock 3.2) for unlocking and rooting.
C) Then go back to the idiot's guide, skip step 3 (unlocking-already done above) and do step 4 (CWM Installation), skip step 5 (rooting-already done above), then follow step 6 (installing the new kernel).
Again I really appreciate all the advice.
-HuckFinn
HuckFinn said:
Sorry to be a pest but just want to make sure I understand.
A) Follow the idiot's guide steps 1-2, which covers Xoom driver installation and ADB installation.
B) Then follow the other link (How to root your Xoom from stock 3.2) for unlocking and rooting.
C) Then go back to the idiot's guide, skip step 3 (unlocking-already done above) and do step 4 (CWM Installation), skip step 5 (rooting-already done above), then follow step 6 (installing the new kernel).
Again I really appreciate all the advice.
-HuckFinn
Click to expand...
Click to collapse
I guess that my original idea of using the idiot's guide for everything but step 5 still might work, as long as you substitute any older HC 3.1 specific files with the new ones from jase33's post.Meaning new boot image for old boot image, etc...At some point, someone willcreate a "rootboot"zip for HC3.2 but til then, jase33's way is it.
The Tiamat recovery listed in the Idiot's Guide is still valid and jase33 didn't include a custom recovery in his guide (at least I didn't see it). So I think you can install it earlier or later. I'm not sure it makes a difference, as long as you have it installed so you can flash the new kernel!
I just upgraded from a rooted Viewsonic G tablet to the Xoom WiFi. I have not had a chance to work with it yet. A list of reasons to root would be helpful. Thanks in advance.
.
okantomi said:
I've got to be quick...I have to do some work today, lol, but here goes:
Actually, follow the Idiots Guide regarding the adb, moto drivers setup.
Then follow this http://forum.xda-developers.com/showthread.php?t=1170760
It's got all the right files and steps, and though it's pretty much to the point, it's user friendly enough. It will get you rooted, I'm sure.
While the difference between ROMs and kernels is somewhat over my head, the ROM does contain the kernel (it's sort of an all inclusive package to tell the device how to behave, whereas the kernel manages particular functions, but not others. It's more limited.) Because the Honeycomb source code hasn't been released, the developers are somewhat limited in the ROM-development department, but they have been able to work wonders with kernels. However, the Tiamat 1.1 Rom for HC3.1 was great and the new ROM in development for HC3.2 will be great too, if the Katana kernal for HC3.2 is any indicator.
Click to expand...
Click to collapse
I believe the kernel is the Linux derivative operating system that the Java based android layer runs on top of. Technically ROM means Read Only Memory which is not being used correctly. A ROM really is a factory produced Masked ROM (burned in, fixed) or an EPROM (Erasable Programmable Read Only Memory) as in a chip or integrated circuit.
davidsos said:
I believe the kernel is the Linux derivative operating system that the Java based android layer runs on top of. Technically ROM means Read Only Memory which is not being used correctly. A ROM really is a factory produced Masked ROM (burned in, fixed) or an EPROM (Erasable Programmable Read Only Memory) as in a chip or integrated circuit.
Click to expand...
Click to collapse
Your answer is more technically correct. Thanks.
Random reboots, coming from 3.2 stock OTA
Does anybody else get random reboots in Tiamat Katana coming from 3.2 stock OTA? So far it's been exclusively a sleep-related problem; I haven't seen it reboot during active use. I'm not (over|under)(clocking|volting).
I've tried clearing cache and Dalvik cache. If it matters, I've been using the Overclocked GPU version. I'll try the Standard GPU version of Katana, but that's not a likely fix, since all the problems seem to be sleep-related.
(PS: I've read all the FAQs I could find, but I couldn't find the answer to this one: I'm coming from a Viewsonic G, and I'm used to the ability to nvflash completely back to a working state no matter what. Is there an equivalent method of restoring a Xoom to absolute stock? Thanks!)
Nevermind...I did one more "clear user data" and now it's stable. Tiamat devs, you are gods among men and heroes to all the little children. Thanks!
redhairedscot said:
Nevermind...I did one more "clear user data" and now it's stable. Tiamat devs, you are gods among men and heroes to all the little children. Thanks!
Click to expand...
Click to collapse
And if you set WiFi sleep to NEVER (hardly uses any additional battery) you will not have any more random sleep-related reboots.
CWM after rooting?
I followed the instructions in Post #2 of this thread to root my Xoom (HC 3.2). All seemed to go well. However, I have noticed that when following pingvinen's instructions (linked from Post #2), in http://forum.xda-developers.com/showthread.php?t=1130996, to install Tiamat 2.0.0, the steps include installing CWM before rooting. I can't see that it matters that I install CWM after rooting and before Tiamat installation, but I thought that I had better check. Could somebody please confirm that it doesn't matter whether CWM is installed before or after rooting?
Thank you
Gordon
cwm before root, because you need to flash a new recovery to root and flash a new ROM. I'm a noob, too, and just figuring this out myself, but think I am explaining this right.
one of the many guides I reviewed was by steady Hawkins (now part of team tiamat) over on xoomforums... partly pasted below... I actually rooted using the older files and images he references, then upgraded cwm to 3.2 then flashed tiamat 2.0... probably more steps than necessary, but these were the clearest directions and by going through several rounds of flashing I learned a good bit about the process.
Prerequisites:
1) Copy whatever you want to retain, your device will wipe when it unlocks 2) You must have SDK/ADB set up, for instructions please see- Setting up ADB on Windows 7 64 bit (and other Windows platforms) 3) Open SDK and copy all of the files inside of tools folder and paste them inside of platform-tools folder. Vice versa will work as well. If it asks you if you want to replace files select no. The folder you paste these files into will be the folder you will run ADB commands from. 4) Download the files from the link below. Place recovery.img in the file you will run commands from in ADB. ***Wifi-Only Users***- manually put the System and bootloader zips files onto a sdcard card and insert card into xoom. ***3G/4G Users***- manually put the System, bootloader, and 3G fix zips onto a sdcard and insert card into xoom.
Downloads:
Recovery- http://db.tt/GXNxZkF System- 3.1 System - Downloads - Android Forum Bootloader- Bootloader Patch - Downloads - Android Forum 3G Fix- 3G Fix for 3.1 - Downloads - Android Forum
Notes:
In the following two sections you will see red text. This text represents the command that needs to be entered in ADB/Command Prompt. After each command press enter and wait for your computer to push the info to your Xoom. When you see the next command line come up you are ok to enter the next command. You can copy and paste the commands if you would like.
1) To start the process place your Xoom into USB debugging mode. This is done by going to settings, applications, development, and checking the box next to USB Debugging. 2) Plug your Xoom into your computer, open your command prompt (with the path set to the correct folder) and type adb devices 3) If you get a string of numbers your good to proceed, if not refer back to Setting up ADB on Windows 7 64 bit (and other Windows platforms) to see where you went wrong.
Unlocking:
adb reboot bootloader Xoom will reboot into a screen with text on the upper left corner. While you are on this screen enter the following fastboot oem unlock A bunch of text will appear and you will need to use the down volume rocker to select yes, followed by volume up to confirm Xoom will then wipe, reboot, and your back up and running. At this point you will need to go back and re-enable USB debugging
Flash Recovery Img:
Make sure Xoom is connected to computer. Test connection by running adb devices if you get the string of numbers proceed.
Rename the Recovery img you downloaded ~~~> recovery.img
adb reboot bootloader Xoom will reboot into a screen with text on the upper left corner. While you are on this screen enter the following fastboot flash recovery recovery.img Wait for it to finish, then read the below note before you enter the next command!!!!!!!!! fastboot reboot ***As soon as you enter the "fastboot reboot" command in the previous step, your device will reboot. You have to boot into recovery right away or your Xoom will reflash the stock recovery over the custom recovery you just flashed. Follow these next steps very carefully-
a. When you see the Motorola logo appear, wait approximately 3 seconds. b. Tap the Volume Down button. You should see the words "Android Recovery" appear at the top of the screen. Now tap the Volume Up button to boot into recovery. c. If when attempting to boot into recovery it says 'Starting Fastboot protocol support' then you hit Volume Down too soon. Hold Vol UP + Power to reboot and try again.
Root Time:
***For the following use the volume rocker to move the selector up and down, use the power button to select***
1)Select wipe data/factory reset and confirm 2)Select install zip from SD and confirm 3)Select the system file and confirm After it loads select install zip from SD again and confirm 4)Select the bootloader file and confirm
***3G USERS ONLY- Select 3G fix and confirm***
5)Select Reboot and confirm
At this point Xoom will reboot. Please note the first boot will take a while. After it boots up you will be rooted and you should have SDsupport!
Root info:
To ensure that you are rooted download Terminal Emulator from the market (its free). Open it and type su followed by pressing enter. On the next line you should see #. If you do your dialed in.
To view your SDcard use a file manager program such as Root Explorer. Your sdcard will be located in /sdcard/external.
Big thanks to Bigrushdog for the imgs!!!!!
kosenn said:
I just upgraded from a rooted Viewsonic G tablet to the Xoom WiFi. I have not had a chance to work with it yet. A list of reasons to root would be helpful. Thanks in advance.
.
Click to expand...
Click to collapse
Had my 3g zoom for 4+ months before deciding to root. The advantages I've seen in a few short days rooted:
better performance, faster booting, smoother webpages
full SD card use (write access to go along with read in stock 3.2)
ability to fully and truly back up the device
a very resposive developer community
a very knowledgeable and helpful user community (though they'll help you even stock)
a growing understanding of how this great device works
what I'm not sure of is how much effort and attention it will take to keep up with updates from the dev community, and whether tinkering with this thing will become addictive and end up consuming as much time as my original reasons/uses for buying it in the first place
Thank you for the reply. I thought the thread had died
You say:
cwm before root, because you need to flash a new recovery to root and flash a new ROM. I'm a noob, too, and just figuring this out myself, but think I am explaining this right.
I tried to install CWM (flash with fastboot) on a rooted stock US 3.2 WiFi Xoom. I am not clear why starting with a rooted device would make any difference for flashing a new recovery, before flashing a new ROM. Can you explain further? Nevertheless, I haven't managed to flash a fully functioning CWM. It works but with error messages, as indicated in my post at http://forum.xda-developers.com/showthread.php?t=1130996&page=4.
Maybe I need to go back and unroot.
Thank you
Gordon
1st, a disclaimer that I'm not much more experienced than you (if at all). Take what I offer knowing that.
I actually experienced an identical problem. Like you, I was working from several "guides" at once and I think the issue resultedbfrom mixing instructions for one cwm version with an earlier (or later) version. I THINK the version you have is the same as the one referenced in the guide I pasted. If you'll note his directions, he suggested renaming the recovery document to "recovery.img" before flashing it. When I went back and did that, it worked for me... then I was able to flash the updated cwm 3.2.0.0 with no errors.... then tiamat 2.0
I have no idea, though, whether there are ramifications to being rooted without a error-free recovery.
Thanks again for this ... at least someone has been through the same problems as me!
The version of CWM that I am trying to flash is "recovery-Tiamat-R4c-100611-1150-cwm.img", which is what is shown in the fastboot line in http://forum.xda-developers.com/showthread.php?t=1130996. However, I am not seeing any reference to renaming to recovery.img. Are we looking at different threads?
If necessary, I will go back to stock 3.0.1 and un-root, but I would like to avoid the stress, if possible
Thank you
Gordon

Black screen, forced to remove battery to restart.

Hey guys this is my first post here on the forums so go easy on me
So I bought this phone a couple weeks ago off of eBay. The phone was already rooted when I bought it and it is my first experience with a rooted android. I've been doing my best to learn everything I can about all the different things I can do with a rooted phone and I've learned a lot so far.
One thing that's stumping me though is that my phone will randomly just not turn back on after I lock the screen. This happens very randomly and happened to me last night which meant that my alarm didn't go off and I was late to work.
I've tried searching the forum but I can't seem to find a cause or a fix for this problem. If there is any information that I neglected to include, I apologize and will be happy to include that in another post.
Anything that y'all could do to help me would be greatly appreciated!
Sent from my Nexus S using xda app-developers app
it's happen for me too. JB 4.1 stock rom
Maybe try another kernel. I use AIR and.have heard great things bout MATR1X and Marmite as far as stability.
I would back up your apps and do a wipe and reinstall your ROM. For back ups and system tweakage I.use Android Tuner.
I guess we should know your current set up to help you the best. Please tell us what ROM Kernel combo you ate running.and I will do my best to offer suggestions as I'm sure the test.of the community.here will.
Sent from my phone using my thumbs and a keyboard
happen to me twice in the same day on stock unrooted JB. since then, nothing
Nexism said:
Maybe try another kernel. I use AIR and.have heard great things bout MATR1X and Marmite as far as stability.
I would back up your apps and do a wipe and reinstall your ROM. For back ups and system tweakage I.use Android Tuner.
I guess we should know your current set up to help you the best. Please tell us what ROM Kernel combo you ate running.and I will do my best to offer suggestions as I'm sure the test.of the community.here will.
Sent from my phone using my thumbs and a keyboard
Click to expand...
Click to collapse
Ok I think that the screenshot I attached is what you are asking for. If it isn't please let me know what else you need to know. Like I said earlier, I bought the phone pre-rooted so I'm not very sure how use another kernel or flash a different ROM. The whole process seems a little intimidating to me but I would be willing to try it out. I just really don't want to brick my phone because I don't know what I'm doing haha.
You're running a build based of the SDK.
Simply put. Get that crap off of your phone. Flash official stock , a custom ROM or whatever but that needs to go
albundy2010 said:
You're running a build based of the SDK.
Simply put. Get that crap off of your phone. Flash official stock , a custom ROM or whatever but that needs to go
Click to expand...
Click to collapse
Oh, well that makes me feel great about my purchase
Would you mind telling me what the best way to do this is, or directing me to instructions how to do it? I'm really new to this and I would hate to ruin my phone because of my inexperience.
I really appreciate the help.
NikoStone said:
Ok I think that the screenshot I attached is what you are asking for. If it isn't please let me know what else you need to know. Like I said earlier, I bought the phone pre-rooted so I'm not very sure how use another kernel or flash a different ROM. The whole process seems a little intimidating to me but I would be willing to try it out. I just really don't want to brick my phone because I don't know what I'm doing haha.
Click to expand...
Click to collapse
follow this thread to update to the official stock jellybean
http://forum.xda-developers.com/showthread.php?t=1736645
Cascabreu said:
follow this thread to update to the official stock jellybean
http://forum.xda-developers.com/showthread.php?t=1736645
Click to expand...
Click to collapse
Ok, thanks. Is this the latest update? Please forgive me for the complete noob questions that follow:
1. I've downloaded the file, but how do I open it and perform the update?
2. Will updating it this way cause me to lose root?
Well first off you should be posting in the Q&A section.
Use fastboot to install factory images. You can download fastboot and the driver for it from the links in my signature.
1. Download the factory image for your device and extract all the image files in it, put them in the folder where fastboot.exe is located.
2. Hold shift + right click on the folder where fastboot.exe is located, choose "Open command window here" (if you're using Windows 7)
3. Boot the phone into bootloader/fastboot mode and connect it to the computer. (While the phone is off, hold VOL+ and POWER).
4. The computer should now ask for the driver, point it to the location of the drivers you downloaded.
5. Open up the file "flash-all.sh" that you extracted along with the factory images with a text editor, it will tell you the commands you'll need to type to install the images:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-jro03l.zip
I can't remember if this process will wipe your entire internal storage or not.
Now if you want to root, try this: http://forum.xda-developers.com/showthread.php?t=1479831, although there are other ways to root.
Or you can follow these instructions to install Clockworkmod and using it to flash root: http://dottech.org/25412/how-to-root-nexus-s/.
eksasol said:
Well first off you should be posting in the Q&A section.
Use fastboot to install factory images. You can download fastboot and the driver for it from the links in my signature.
1. Download the factory image for your device and extract all the image files in it, put them in the folder where fastboot.exe is located.
2. Hold shift + right click on the folder where fastboot.exe is located, choose "Open command window here" (if you're using Windows 7)
3. Boot the phone into bootloader/fastboot mode and connect it to the computer. (While the phone is off, hold VOL+ and POWER).
4. The computer should now ask for the driver, point it to the location of the drivers you downloaded.
5. Open up the file "flash-all.sh" that you extracted along with the factory images with a text editor, it will tell you the commands you'll need to type to install the images:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-jro03l.zip
I can't remember if this process will wipe your entire internal storage or not.
Now if you want to root, try this: http://forum.xda-developers.com/showthread.php?t=1479831, although there are other ways to root.
Or you can follow these instructions to install Clockworkmod and using it to flash root: http://dottech.org/25412/how-to-root-nexus-s/.
Click to expand...
Click to collapse
I appreciate the extensive list of instructions you provided. I tried my best to follow them but I couldn't quite figure out what I was doing wrong. I decided to try to install a custom ROM instead and was able to install cm9 pretty easily. Will this be sufficient to remove the aforementioned problem I was having?
If your already rooted then you don't need to go through a lot of that even.though it was a good walkthrough. If you flashed a new ROM then.you have.some sort of recovery in place. As long as you do a full wipe to get the previous owners garbage off of there and then flash a new ROM like CM9 then you should be golden the new ROM will come with it's own kernel so you don't need to start learning about those until you want to.
If I may make a suggestion, give AOKP Build 4 a try the ROM you chose is good but is using old code (ICS) If you just got a new phone why not put the latest on it.
Keep me (us) posted as we the reason a lot of us belong to this forum is to offer any help we can....AOKP4 you won't regret it.
Sent from my phone using my thumbs and a keyboard
That works too, you can flash the stock roms here (using CWM) or stay with the custom rom: http://forum.xda-developers.com/showthread.php?t=1843301
Nexism said:
If your already rooted then you don't need to go through a lot of that even.though it was a good walkthrough. If you flashed a new ROM then.you have.some sort of recovery in place. As long as you do a full wipe to get the previous owners garbage off of there and then flash a new ROM like CM9 then you should be golden the new ROM will come with it's own kernel so you don't need to start learning about those until you want to.
If I may make a suggestion, give AOKP Build 4 a try the ROM you chose is good but is using old code (ICS) If you just got a new phone why not put the latest on it.
Keep me (us) posted as we the reason a lot of us belong to this forum is to offer any help we can....AOKP4 you won't regret it.
Sent from my phone using my thumbs and a keyboard
Click to expand...
Click to collapse
First I want to say thank you to everybody for all the help so far. :highfive: I'm still learning but I am slowly figuring all of this out.
Nexism, I would be interested in trying AOKP build 4 if you wouldn't mind explaining the easiest way to do it or point me somewhere that can explain it to me. I don't know what all goes into flashing a new ROM and I don't want to forget something that will mess up my data or my battery life.
Here is the AOKP thread. Its located in the general section.
http://forum.xda-developers.com/showthread.php?t=1645400
As far as flashing goes...
Download the ROM from the above thread
Download a good app backup app (I use Android Tuner, it seems like everyone else uses Titanium Backup or ROMToolbox all have free versions only thing you'll miss is batch restore)
Back up your $hit
Boot I recovery (phone off, hold vol up while powering phone on) then scroll to recovery
(At this point opinions differ a bit) I go to mounts and storage and format the following data, cache, system, then boot then back out to the main menu and wipe all factory reset (I'm kind of a neat freak just.like to make sure I'm always starting with a clean slate)
Then install your.ROM and Gapps after a few min main recovery menu will come up
Select reboot
Go through the norm set up
Re-install backup app
Restore your apps
Then play around with all.the new features on your Nexus
Sorry if this is too basic of a walkthrough no offense if so. You can PM me if you need more detail. Good luck, happy flashing.
Sent from my phone using my thumbs and a keyboard
Nexism said:
Here is the AOKP thread. Its located in the general section.
http://forum.xda-developers.com/showthread.php?t=1645400
As far as flashing goes...
Download the ROM from the above thread
Download a good app backup app (I use Android Tuner, it seems like everyone else uses Titanium Backup or ROMToolbox all have free versions only thing you'll miss is batch restore)
Back up your $hit
Boot I recovery (phone off, hold vol up while powering phone on) then scroll to recovery
(At this point opinions differ a bit) I go to mounts and storage and format the following data, cache, system, then boot then back out to the main menu and wipe all factory reset (I'm kind of a neat freak just.like to make sure I'm always starting with a clean slate)
Then install your.ROM and Gapps after a few min main recovery menu will come up
Select reboot
Go through the norm set up
Re-install backup app
Restore your apps
Then play around with all.the new features on your Nexus
Sorry if this is too basic of a walkthrough no offense if so. You can PM me if you need more detail. Good luck, happy flashing.
Sent from my phone using my thumbs and a keyboard
Click to expand...
Click to collapse
Awesome, thanks man.
It was exactly what I needed to know - not too basic. I flashed it and now I'm checking it out. Is there any reason I would need to use a custom kernel for anything?
No, only i u find it slow as it is now. If u want a custom kernel go for matr1x one
Sent from my Nexus S using xda app-developers app
Glad to here your Nexus is doing well.
Now that you have a good build make a backup (in recovery) so you will always have a working configuration to go back to then experiment all you want. I may get corrected on this but as long as I have a backup and access to recovery mode I know that the chances of me bricking my phone is slim to none. So I am a flash happy fool. I try everything new when it comes out.
Get comfortable with your new ROM and flashing in general and as you see a need try different stuff out.
I use a custom kernel because I use the on screen navbar and I like to turn off the hardware key backlight. You also have control over CPU min/max Frequency,governors, and I/o schedulers as well as some extra tweak options. If you're like me the more you learn the more you'll flash.
Check out NSTools it is one of the must have apps for our phones.
Again, I am available for anymore help I can.offer.
Sent from my phone using my thumbs and a keyboard

[Q] LG Motion (Possible Cyanogen mod?)

Hey everyone! I would like to start off by saying that I am brand new here, and am surely going to mess up quiet alot... But here goes,
I've recently rooted my phone with a very simple guide, and it's the first device I've every rooted. So I know very little of the process of doing so, (I'm learning slowly).
I also have found a rom that I would like to install, but I would love to know if others think it seems legit? If it is real, I know many people would absolutely love to use it! The rom's URL is (ht tp:// playfuldroidz.com /wiki/ CyanogenMod_10_Motion) (Please remove spaces, sorry as I said i'm new...)
Now I don't mind testing this myself, but being as new as I am at android I honestly do not know how to follow the relatively simple instructions.
(This Is where I need some help, Please be noob cautious!)
Download the .zip & copy to phone or sdcard (make sure 4g or wifi is enabled if dl'd from phone).
Zip can be installed from either internal or external sd in CWM (Which ever you copied it too!)
MAKE A BACKUP!!!
DO A FACTORY RESET!!! - this will wipe data & cache!
Go to install zip from sdcard
Choose zip from sdcard
Select cm-10-xxxxxxxxxx-UNOFFICIAL-l0.zip
Confirm
Repeat Steps 5 -8 for gapps
Reboot
Now my first question I'd love some help with, is how do I perform this backup there talking about? do they just mean my simple go into settings and click backup? Or should I do it some otherway?
Second question: Do they mean the phones built in service of factory reset?
Third Question: To install a Zip from an SD card do I need to simply use ES file explorer, or root file browser? Or is there a custom way to install a Zip file on android?
Fourth and final Question: What is gapps..? Is this something I should get or use?
EDIT: I've got a fifth one also... Thanks to anyone who's stayed this long and is willing to help me.! Will this Cyanogen mod (If working) Work almost exactly like a real nexus Operating system? I've got a nexus 7 tablet running stock android, and I love it! That's why I'm doing this to my phone honestly.
Thank you all greatly!
Prophet968 said:
Hey everyone! I would like to start off by saying that I am brand new here, and am surely going to mess up quiet alot... But here goes,
I've recently rooted my phone with a very simple guide, and it's the first device I've every rooted. So I know very little of the process of doing so, (I'm learning slowly).
I also have found a rom that I would like to install, but I would love to know if others think it seems legit? If it is real, I know many people would absolutely love to use it! The rom's URL is (ht tp:// playfuldroidz.com /wiki/ CyanogenMod_10_Motion) (Please remove spaces, sorry as I said i'm new...)
Now I don't mind testing this myself, but being as new as I am at android I honestly do not know how to follow the relatively simple instructions.
(This Is where I need some help, Please be noob cautious!)
Download the .zip & copy to phone or sdcard (make sure 4g or wifi is enabled if dl'd from phone).
Zip can be installed from either internal or external sd in CWM (Which ever you copied it too!)
MAKE A BACKUP!!!
DO A FACTORY RESET!!! - this will wipe data & cache!
Go to install zip from sdcard
Choose zip from sdcard
Select cm-10-xxxxxxxxxx-UNOFFICIAL-l0.zip
Confirm
Repeat Steps 5 -8 for gapps
Reboot
Now my first question I'd love some help with, is how do I perform this backup there talking about? do they just mean my simple go into settings and click backup? Or should I do it some otherway?
Second question: Do they mean the phones built in service of factory reset?
Third Question: To install a Zip from an SD card do I need to simply use ES file explorer, or root file browser? Or is there a custom way to install a Zip file on android?
Fourth and final Question: What is gapps..? Is this something I should get or use?
EDIT: I've got a fifth one also... Thanks to anyone who's stayed this long and is willing to help me.! Will this Cyanogen mod (If working) Work almost exactly like a real nexus Operating system? I've got a nexus 7 tablet running stock android, and I love it! That's why I'm doing this to my phone honestly.
Thank you all greatly!
Click to expand...
Click to collapse
Question 1,2 and 3.. they are all done through Clockworkmod. Look through the menus you'll see it if you still struggle look on YouTube.
Question 4.. gapps is Google Apps you need to flash this after the ROM to get the play store and all the other standard Google apps.
Question 5.. in your eyes pretty much, it'll look the same but with more features obviously.
Thank you alot!
Thanks! now i've only gotta do one last thing, and see if anyone knows whether or not this website is a reliable source, or atleast if the mod works...
Prophet968 said:
Thanks! now i've only gotta do one last thing, and see if anyone knows whether or not this website is a reliable source, or atleast if the mod works...
Click to expand...
Click to collapse
Just give it a go mate, if in doubt try it out lol (don't quote me on that haha)
Alright I've got one last dumb question
CdTDroiD said:
Just give it a go mate, if in doubt try it out lol (don't quote me on that haha)
Click to expand...
Click to collapse
I was just wondering if there's a chance this clock work mod thing doesn't work on my phone? I don't really know how, or where it is either... and I'd love some help with that... Thank you!
(Edit) I don't think there is a clockwork mod for my device... According to the Rom Manager app I was told to use for installing it.
Prophet968 said:
I was just wondering if there's a chance this clock work mod thing doesn't work on my phone? I don't really know how, or where it is either... and I'd love some help with that... Thank you!
(Edit) I don't think there is a clockwork mod for my device... According to the Rom Manager app I was told to use for installing it.
Click to expand...
Click to collapse
If you did what it said in the instructions *root it, cwm, install custom rom* then after installing the custom rom it has it's own cwm. turn off the phone, turn in back home and press the back and home button together at the same time and it should take you to the rom's cwm. If the phone does a factory reset by pressing the back and home button then you did the installation wrong.
But just in case I'll setup a full instruction for you.
Root your phone.
Which can be done easily, just download this and extract the files: http://www.mediafire.com/?dhdbwflnl1vknx2
once you extract the files put your phone on debugging mode which can be done by going to settings, developer mode, and click usb debug.
once you've done that connect your phone to the pc *make sure it's on charge only* wait for driver installation to finish. once that's done click root. follow instructions on the screen it shouldn't be too hard! after following instructions you should be rooted and have cwm. but to install the recovery go to your apps and find lte 2nd init recovery and then click the top button, agree to super su to use it and you're done with rooting and cwm! now. these files you were talking about, download them and put them on sd which can be done with a file manager. after they've downloaded go to the lte 2nd init and click the bottom button. it will reboot the phone and take you to cwm. While you are in cwm click on the home button to go to external which is the sd, then go to backup and restore, and click backup! this is very important. miss this step and things could go bad. Now all you have to do is follow the instructions you posted yourself and you should be done! if you need any help don't hesitate to message me. I've done this for a long time now.
Whoops forgot to add. the website IS a reliable source. Learned that cause I'm a risk taker and decided to try it out myself. and do not use rom manager or anything like that for recovery. ever. especially on phones that do not have their own recovery mode. also. the CM10 works great in my opinion! But there's a catch. for me at least. even though everything is perfect during phone calls I cannot use my 4g. which is a bad thing for me cause I need it. other than that if that doesn't bother you or anything or don't have service then knock yourself out and install the cm10!
COMPLETED) This mod worked, all things are now finished except one small issue!
So after installing the mod with some great help of someone here on this forums, I've been basically beta testing the mod for a few days. I have nearly no complaints, as almost everything works seemlessly just like you'd except the operating system to. In the end I found one single issue though, which is terribly annoying for me in specific...
My GPS isn't working, which could be one of many things other than the rom. Seeing as I only recognized It yesterday, there may be an outside reason it at random shut off. If anyone know's what can cause this, and a fix for it please comment back!
Thanks to everyone who helped with installing the mod
Check out www.unleashedprepaids.com. have whole section on lg motion custom ROMs help guides everything u need!
Sent from my LG-MS770 using Tapatalk 4
Please help me with the rom
Hey guys not sure if i am suppose to post this here but i couldnt find any where else and i couldnt find an answer with my exact problem, i installed this rom on my moms lg motion and everything went find untill i got to gapps it came up with an error inside of cwm so i just contined all the other flashes i had to do and rebooted i thought that i could just flash gapps later. But i mad a very big booboo i installed the Recovery APK for it in cm 10 i forgot all about pressing reboot and saying reboot into revocovery so i was going to try it though the Recovery APK so i installed the thing and pressed reboot and instead of taking me into recovery it takes me to a screen that says something like "mourning call error" which i dont know what means but i had to take out the battery and turn the phone back on so that worked and i got back to the home screen but i still cant install gapps so she can use all the google sevices i tried rebooting with the built in reboot into recovery (the one that you press reboot when you hold the power button) and that does the same exact thing i have no way of flashing gapps or anything else for that matter can someone please help me i have no idea what to do. everything i working on the phone but that. thank you sorry if i put this in the wrong place.
Confused my droid using this method- would love in on this thread
Sorry if I'm posting in the wrong place-punch me if I have-
I rooted my lgms770 with version f firmware- installed cwm and 2ndinit recovery (2nd init was the only known way (to me anyway) to get into cwm at the time) followed this guide ---
[LgMotion All Things root] and
[GUIDE] Unbrick OR Unroot LG Motion 4G [KDZ] - Android Forums
I am not allowed to post urls yet...sorry...its the the first google hit
I've tried multiple versions of the official LG Firmware flash, from the website, and by following this guide-
AOKP Dirty Unicorns baseless port cm10 - Android Forums Actually, its the unicorns that got me.
With no luck there. I am running Mint16, and had to run the programs through Wine of course, then tried Q4wine, and eventually tried running though Oracle VM, and finally, I wiped my ancient dell of Linux altogether and put WinXP back on it (took 2 hours, that). No cigar. And yes, I did the drivers, all in order, etc, tried again, reinstalled etc
I finally set up adb to try to get into this droid that way, but am having problems with port permissions (I'm going to guess that's on my pc's end-running Mint16)
I can access the factory reset screen (the black and white), download mode, and the battery charges on a black screen with a nice purple font, but I am still stuck in a bootloop. I've employed all known button spamming combos to get back into cwm (there is a nandroid in there somewhere)..but alas...
Help me Obi-Wan-Kenobi's..
Peach
I had the purple letters with no way to get to the factory reset screen i just used the lg online flash tool in upgrade recovery put in the imei of the phone in made sure the phone was in usb download mode then it was fixed but for some odd reason i still cant get my phone to the factory reset option. I apologize sincerely if I wasn't detailed enough if you need any clarification on it then let me know through pm or i could even send u a link to my box folder i keep the install files in.
(Also i have a one click root app for the LGMS770 So if you or anyone would like the link i would be happy to give it to you)
Sent from my MetroPCS LG-MS770 using Tapatalk

Full on Noob, need help if possible.

Okay so, I love my Infuse but getting really tired of not being able to download anything off the play store. Just tired of it's rather less than great performance right now as well. It's is running 2.3.6 GB and want to get this thing up to ICS if possible. Just something running 4.0 so I can use my phone for what I need too. It is not rooted, no cyanogenMod, NOTHING. As the title says, I'm a full on noob here and I apologize if all this is covered in other threads, however I have just gotten to the point where I have found myself even more lost than where I started on what I needed to do/get. If someone can, I will literally need this spelled out to me (no pun intended), in order of the steps I need to take with everything. I'm getting tired of confusing myself even more from all the different stuff I have seen all over the place and I know without some serious guidance, I will just brick my phone. Thanks for any help! :laugh:
I understand this community can be a bit unorganized and confusing so I'll give you my process for rooting and installing custom firmware (there are other ways, but this works for my AT&T Infuse 4G SGH-i997).
First of all, no one uses ICS on the Infuse. There is a ROM, but it's underdeveloped because JB came out so quick. You will need to flash it to get to higher operating systems, but it is by no means a daily driver. Even JB is a little buggy compared to KitKat on the Infuse these days.
The first thing you want to do is root your phone and get a custom recovery.
There are more than a few options for rooting, but I prefer using ODIN (as I understand it, this is the tool Samsung uses to restore soft bricked phones). So this is a good thing to know how to do, in case you ever do soft brick your phone, you'll know exactly what to do.
Read the ODIN instructions in full as I will only briefly explain.
You're going to have to install Samsung drivers.
You'll be using UCLB3_Unbrick_root_1.1.zip. If you used UCLB3_Unbrick_1.1.zip it would just get you back to stock GB with no root added.
To put your phone into download mode, first turn off your phone. Plug a usb cable into your computer. Then with the phone off, hold down both volume buttons and plug the usb cable into your phone. A warning will come up and you push volume up to accept, realizing that you can easily soft brick your phone if you loose power or unplug during a download.
Once downloading is done, the phone will reboot and you'll be disappointed to see that nothing has changed. Except one small thing, you are now rooted and you should have an application called SuperUser that will allow you to do nifty and also dangerous things.
Now follow this step in the ODIN instructions to add the custom recovery (CWM = Clock Work Mod):
The version with root works exactly like the above version, but adds root. To add CWM recovery to the rooted version, download a custom Gingerbread kernel from HERE or HERE and flash the zImage using SGS Kernel Flasher (found in the Play Store) on the phone. If you go this route for root and CWM, your Custom Binary Download counter will not show any custom binary activity.
Click to expand...
Click to collapse
If you follow the link in the second "HERE," you'll get the kernel I prefer since it was most recently updated. Scroll down the downloads section and grab "2013.04.30-CWM-Synthesis-1.2Ghz.zip." (1.2Ghz is stock for our processor, anything higher will be overclocked which I don't recommend).
Extract that and grab the zImage file in the update folder. You're going to copy this to your phone in a second.
But first you need SGS Kernal Flasher, you can get it off the playstore, but I despise having to log in to an OS I'm going to write over in less than a minute so I download the APK from here. Hopefully you know how to install APKs from your SD card and that you'll have to check install from unknown sources.
Now flash the zImage using SGS Kernel Flasher. Your phone will reboot and hang on the Samsung logo and a creepy voice is going to tell you about how she's partitioning your phone and installing Voodoo lag fix. This is normal. Eventually your phone will reboot back into GB and you'll be ready to flash any ROM of your choice by rebooting into recovery.
You reboot into recovery by holding the volume up and volume down button while powering on the phone. This is different than download mode and will take you do a new screen that you control with the volume keys.
You'll be using this to put new software on your phone.
Now you can bassically follow the instructions for getting to CyanogenMod 11 (Kit Kat) from GB.
The first bullet is what I just explained in detail.
Note that I didn't include the links in these instructions, just follow the link above to get to the original post.
Obtain CWM, this can be done using Jscotts Odin back to stock (Follow instructions and use SGS kernal flasher to obtain CWM)
Run Qksters IMEI backup script here
Make certain you are on ICS, this can be done by flashing Entropy's CM9
It is recommended now that you remove your SD Card
CWM: Wipe Cache / Factory Reset
Install ROM: Scroll down for downloads sectoion
... The package will start to install..
... Phone will reboot into the install screen again...
... Continue to install [Automatically] If not manually flash again
... Phone will reboot again and be at the recovery screen...
Install Gapps: Here - Working swipe!
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
Click to expand...
Click to collapse
To be clear, when you flash a ROM, it won't be like flashing the zImage (that was just to get custom recovery). To flash the CM9 ROM or Qksters IMEI backup script for example, you leave the rom in the .zip file and simply put it on your SD card. Once in the recovery screen, you select "Install Update from ZIP" and navigate to the particular ROM you wish to install.
Also after updating to a higher version of Android, your phone will sometimes hang on the install screen for a long time. If it does for more than five minutes, it's safe to pull the battery and try flashing again (and sometimes necessary).
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Lately I've been using CyanFox and I have to say, it's the most stable ROM I've used in a while.
If you have any questions about this, feel free to ask.
Best of luck and happy flashing,
~bokonon9
Thank you muchness!
Thank you very much for helping me in this mess! I greatly appreciate it. I love my Infuse and do not want to get rid of it quite yet so hopefully this will help! Once I get a new usb cord I will get on this. My toddler decided to get a hold of it and it has to set a certain way now and can't be moved. This, is no bueno! Anyways, THANKS AGAIN!!! :laugh:
Goodluck! :laugh: :good:
I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Click to expand...
Click to collapse
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!
wwr said:
I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!
Click to expand...
Click to collapse
i would say go back to stock gb with odin and basically start over but with ics i always let it reboot to get a "feel" for it then i reboot to recovery and wipe basically everything then flash the next level of android which should be cm 10 then i let that boot then repeat that to get to kitkat 4.4.3 CarbonRom....sometimes you have to flash the same rom twice to get it to flash tho
I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall
wwr said:
I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2091900&page=370
read the last post on that page by scmfxt

[Q] SOLVED: Help - KitKat upgrade from stock... ish.

So, I did a stupid thing this morning. I spent the last, probably, five hours backing up all of my apps and data from my TF300, and once that was all done, I wiped the data on my tablet. "What makes that stupid?" What makes that stupid is, it was a miracle that I ever actually managed to root this thing in the first place, and now, I don't know a) if it's still rooted (I doubt it), and b) if I'm even mentally capable of rooting it again (I doubt it).
So, here's my situation, and if someone could just dumb down the steps for me and point me in the right direction, that's all I need. I got my tablet, I don't know, probably early 2012. I can tell you that the tablet is on ICS 4.0.3, and the build number is 9.4.3.29-20120511. It's also unlocked, I don't know if that needed to be mentioned. Now, things are better since I wiped the data on this mother, but ICS, on this tablet in particular, is slow as balls, and I'm done with it, I want KitKat. But I am so far beyond lost after what I did that if I try to work my own way out of it, I'm going to brick this thing.
I wiped the data because I was trying to do something involving the Fastboot menu or something like that. Whenever I selected the USB icon and hit up on the volume strip, the tablet just locks cold. I figured whatever caused that, would probably go away with a data wipe. It didn't. So now my data's gone, my apps are gone, my tablet's not rooted anymore, I have no idea how to get to KitKat, I can't sleep at night, it burns when I pee... let's focus on the tablet stuff for now, I'm signed up to some forums for the other stuff.
I know most of the people that read this topic will be inclined to say, "You're an idiot, read this, this, and this, and take care of it yourself." I know I'm Androidiot, and I'm humbly asking for help. Again, I'm just petrified of following the wrong topic and ruining the whole thing, so if someone could tell me how I'd go about upgrading my tablet from stock ICS to KitKat, I'd appreciate the hell out of it.
Just a little bump, not too big... no love for Tim?
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
zlazaar said:
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
Click to expand...
Click to collapse
Thank you, Zlazaar!
Well, it seems that after my device was wiped, it still didn't remove CWM as a bootloader or whatever, I don't know what I'm saying. When I hold down the power and volume down buttons, I could wait like ten seconds for fastboot, or I could tap vol up to enter the "RCK" menu. I don't know what that means. But I go into it, and I'm at the CWM menu, I think it was 5.5.0.4. You probably know better than me if I need to do anything further than that with CWM, but I should be good on that, right?
I'm almost going to go to the sites that you mentioned to download files and get more information on how to use it all. I appreciate your help, because without it, I'm sitting on an unrooted stock ROM with only most of my apps, because oh yeah, like 70 apps forgot to transfer with that backup I did... so, whoopee.
Thank you again, buddy!
The goal is kitkat, right ?
So, in order to get it you need 2 important things :
1- The latest bootloader, yours can't handle kitkat.
2- a custom recovery supporting kitkat, i.e i'm using TWRP 2.7.1.0 (link in my signature), your CWM is outdated.
The only way i know to update the bootloader is to flash Stock ROM via fastboot as described in tutorial.
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Here is the driver : Universal Naked Driver
After install, you can use fastboot and complet other steps.
Tim 13 said:
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Click to expand...
Click to collapse
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
b..c said:
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
Click to expand...
Click to collapse
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Tim 13 said:
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Click to expand...
Click to collapse
Hi Tim13,
I'm glad to hear that everything went well and my guide helped you!:good: And to answer your question flashing doesn't wipe your data. You have to manually wipe it. And lol:laugh::good: that you didn't kill your tab. I hope you find your tab faster and useful again!
It's just as slow and useless as it was. But honestly, the flashing process was fun, and I learned from it. Plus, TWRP and Cyanogen mod are awesome, and now I know that. lol
Great to see you up and running @Tim 13 :good:
Can you add SOLVED to the thread title
Thx Josh
No, I'm not gonna do that.
I'm just kidding. You're all right, darling. :good:
Edit: Actually, not being a douche, I can't figure out how to edit the thread title. I went to edit the first post and I can't change the title of the post... I'm gonna look around for how to do it a bit more but after that I'm gonna go to bed.
DOUBLE EDIT: Got it, as you can see. Thanks to all that helped out!

Categories

Resources