Database Info

[TUTORIAL] Prepare Your AT&T HTC One X for Custom ROMs

OUT OF DATE USE THE ONE CLICK 1.85 ROOT TOOL IN THE FORUMS
As the ROM chefs go to work, we want to be sure that we are ready to flash the ROMs when they come to be available! This guide will help you set up your phone so that you can flash custom ROMs.
After this process you will have a phone on the latest firmware (1.85 at the moment) with bootloader unlock, rooted, and busybox installed.
This guide assumes you are on a root friendly firmware (as of now, it is firmwares 1.82.502.3 and below).
This is really going to be done in a four step process. First we need to root the device in order to access the place where the CID is stored so that we can change it and get unlocked. After changing the CID, we can unlock via htcdev.com. Then we can go on to installing a custom recovery and finally rooting!
From there I will give you some tips on installing ROMs.
NOTE: THIS PROCESS IS EXTREMELY DANGEROUS. IT MAY BE A BIT CONFUSING. READ OVER THE STEPS BEFORE STARTING. IF YOU DO NOT THINK YOU WANT TO RISK YOUR DEVICE BECOMING A BRICK THEN DO NOT ATTEMPT THIS. THIS VERY EASILY COULD RUIN YOUR DEVICE.
BACKUP EVERYTHING BEFORE STARTING AS EVERYTHING ON YOUR DEVICE WILL PROBABLY BE WIPED.
I, XDA, AND THE ORIGINAL TOOL CREATORS DO NOT TAKE RESPONSIBILITY FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. IT IS SOLELY YOUR RESPONSIBILITY FOR WHAT YOU DO TO YOUR DEVICE.
Click to expand...
Click to collapse
Your warranty will be void if you unlock the bootloader. If you just root though then you can return to 100% stock by running the RUU.
This guide is for Windows only at the moment though I will try to post Mac and Linux guides at some point.
ORIGINAL TOOL THREADS:
One Click Root for 1.82 and below: http://forum.xda-developers.com/showthread.php?t=1644167
Spoof CID Script: http://forum.xda-developers.com/showthread.php?t=1672284
I will try to keep this as up to date as possible! Taking a visit to the index of the development forums (http://forum.xda-developers.com/showthread.php?t=1671237) is also a good idea!
Last Updated: 5/28/12

0. Getting the prerequisites:
Download the package at the bottom of the first post to get started.
Extract the package somewhere you will remember (like on your desktop).
Connect your device via USB and make sure you have USB Debugging enabled under settings.
Click to expand...
Click to collapse
1. Root your device
1. Open the folder you downloaded and navigate to the "root" directory.
2. Double click on the root-windows.bat file
3. Let the root run and do not touch your device. It will reboot several times- do not touch it or you may brick your device. Just let it do its thing and eventually after around 3 minutes you will have a rooted device in your hand.
Click to expand...
Click to collapse
2. Get the unlock token
In order to unlock the bootloader we will need to change a value called the CID. This will allow the htcdev.com site to unlock our phones.
1. Go to the downloaded folder and go to the "change_cid" folder.
2. Click on the "Spoof-CID.bat" file. Follow the instructions. Your CID will change from CWS__001 (stock AT&T CID) to 11111111 (called "SuperCID," will allow you to flash anything)
3. Log in to htcdev and go here: http://www.htcdev.com/bootloader/unlock-instructions (NOTE: This skips the agreements you need to click through as some of the buttons on their website are wonky. Doing this assumes you agree to their policies that are listed there)
4. Follow the instructions very carefully (they are written very well) untill the point where you get the file "Unlock_code.bin" via email. Stop there.
5. You should now have the file for bootloader unlock. MAKE SURE TO SAVE THAT FILE "Unlock_code.bin" TO THE "generic" FOLDER IN THE PACKAGE YOU DOWNLOADED! YOU WILL NEED IT LATER.
Click to expand...
Click to collapse
3. Run the RUU to update to latest firmware
1. Download the latest RUU from the xda forums (should be an .exe file)
Currently it is version 1.85.502.3 and you can download it here:
http://briefmobile.com/download-htc-one-x-att-1-85-update
2. Follow its instructions very carefully. It will take approximately 20 minutes to complete. BE PATIENT. IF YOU UNPLUG YOUR PHONE HERE YOU WILL GET A BRICK.
3. Let your phone reboot and go through initial setup again
Click to expand...
Click to collapse
4. Unlock your bootloader using Unlock Token
1. Navigate to the "generic" folder in cmd (you should have added the Unlock_code.bin file to this folder already) and plug your phone in in fastboot mode. To do this, first shut off your phone. Wait for it to turn off. Then hold the volume down button. Press the power button for 3 seconds while still holding the volume down key. Let go of the power button but keep holding the volume down button untill you see a white screen with a bunch of small text on it. Use the volume up and down keys and the power button to select the FASTBOOT option. Plug your phone into your computer. Then wait for the FASTBOOT text to turn into FASTBOOT USB.
2. Type the following into cmd on your computer:
fastboot flash unlocktoken Unlock_code.bin
NOTE: This step might take quite a few tries. For some it works on the first time. For others, it may take around 20 times. Just keep typing in the command until you get a sucessful flash. We aren't sure why it does this at the moment but just keep trying and don't give up.
3. Use the volume keys to say that you do want to unlock your bootloader and wait for reboot
4. Bootloader should be unlocked! Congrats, most of the grunt work is done! Go to Settings - Developer Options - Enable USB Debugging. This will allow us to continue
5. Re-set up phone and enable USB debugging again
Click to expand...
Click to collapse
5. Install a custom recovery so that we can gain root access
1. Currently there are two recovery options: ClockWorkMod Touch and TWRP (TeamWinRecoveryProject). Both are pretty much the same as they both use touch input but TWRP does have some other nice features like a built in file browser and more. It is also more touch optimized. ClockWorkMod is more "old school" and I personally feel more comfortable using it, but using TWRP is fine as well. It doesn't really matter which recovery your choose, both are good choices. Download whichever one you want below:
CWM Touch: http://forum.xda-developers.com/showthread.php?t=1677304
TWRP: http://forum.xda-developers.com/showthread.php?t=1677447
2. Drag the .img recovery file you just downloaded into the "generic" folder
3. Connect your phone via fastboot
4. Type the following:
fastboot flash recovery <insert name of recovery .img file here>
Replace the stuff between the <> with the name of the file you just downloaded
5. Wait for your device to reboot. Then type into cmd which is cd'ed to the "generic" folder:
adb reboot recovery
6. Make sure your recovery works as soon as it is done loading and then press "reboot system"
7. Follow its instructions
Click to expand...
Click to collapse
6. Root your system
1. Connect your phone as a "Disk Drive" and drag the "root.zip" file in the "root" folder to your phone's memory
2. Reboot into recovery with the adb command (adb reboot recovery)
3. Go to install zip from sdcard and navigate to the zip file you downloaded. Say "yes" and watch it flash
4. Reboot system now
5. Go to the play store and download any app that has "Busybox installer" in its name (the one by JRummy16 works good I believe)
Click to expand...
Click to collapse
If all goes well, you should be sitting at an AT&T HTC One X which is on the latest RUU leaked firmware (1.85.502.3 at this moment), rooted, busyboxed, and unlocked.
Congrats!
If you want to flash any ROMs, download the .zip file of the ROM, place it on your phones memory, and then install the zip like you did to the root.zip file.
Enjoy your AT&T HTC One X!

CREDITS:
kennethpenn: For initial root, getting all the RUUs from the "source" and for giving the HTC One X's situation prime press appearance on his website, BriefMobile.com
grankin01: For finding out how to edit the CID originally
designgears: For creating the One Click Super CID tool for bootloader unlock
paulobrien: For porting CWM Touch to our device
sk08: For leading the way in terms of MODs and organizing an S-OFF thread to get this thing fully ours
JSLEnterprises: For initially being there to help organize a bootloader unlock
Team Nocturnal: For their awesome ROM
Click to expand...
Click to collapse
If you want to thank or donate to someone, please do not do so to me. The people above are the ones that deserve the thanks and the donations to encourage them to keep doing the fantastic work they have been doing! I'm just a high school student
Some common terminology:
Deoxdexed: OEMs package their apps with .odex files because they are more optimized for your device. However, this makes the file uneditable by developers and things like mods cannot be used with odexed ROMs. A ROM with "deodexed" as a feature means it is easier to use mods with that ROM
Busybox: A collection of linux tools that are helpful for flashing ROMs and doing other basic Android tasks
RUU: ROM Update Utility, made by HTC, completely reflashes device firmware, useful if you get bricks. Only for Windows.
Root: Allows you to edit system level files
S-OFF: (currently unattainable) Security-OFF, it is a "feature" in HTC phones that allows us to modify almost any part of your system.
Unlocked Bootloader: Allows us to flash custom images to the device.
Click to expand...
Click to collapse

As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.

HydroSkillet said:
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
Click to expand...
Click to collapse
Wasnt sure, there are still a few people asking how to do it since it is a bit complicated with the 1.85 update breaking root so I just compiled everything into a master one.
And yeah, I use a lot of the scripts in the package I put for download.
Anyway, mods do what you think with this thread! And this might be in the wrong section, wasnt sure if it goes in general or development.

Please keep this up. As it is the most aggregated list of instructions, I'm sure it will help many who have just gotten their phone. Great work by the way.

HydroSkillet said:
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
Click to expand...
Click to collapse
As I agree with you, a "one stop shop" that can be pointed out to for the noobs who got their mommy's to buy them their cool phone should at least keep the redundant questions to a minimum.

you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG

squishy5 said:
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
Click to expand...
Click to collapse
Locked boot loader yes.
Root for cwm no.
Sent from my HTC One X using xda premium

squishy5 said:
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
Click to expand...
Click to collapse
Why don't you read before you comment on things like this?
I never "Unlock the bootloader"
I simply get the Unlock token from HTC.
So stop acting like you know everything, because you dont
Don't ever use caps with me and expect me to come back with a nice response. I put this out for the community, not for some kid who thinks he knows it all to come back and say that I did it wrong when he didn't even read the post properly.
And you don't need root to install CWM, just an unlocked bootloader.
Stop calling my stuff wrong if you yourself don't even know what is right

rohan32 said:
Why don't you read before you comment on things like this?
I never "Unlock the bootloader"
I simply get the Unlock token from HTC.
So stop acting like you know everything, because you dont
Don't ever use caps with me and expect me to come back with a nice response. I put this out for the community, not for some kid who thinks he knows it all to come back and say that I did it wrong when he didn't even read the post properly.
And you don't need root to install CWM, just an unlocked bootloader.
Stop calling my stuff wrong if you yourself don't even know what is right
Click to expand...
Click to collapse
He put his foot in his mouth, apology should be coming oh and Good job man, Good job. Thanks for the work, this should be a sticky.

This is a great write up and would have been extremely helpful last night. I will admit I have done a lot of reading before I unlocked the bootloader and updated to 1.85, but it was still very confusing at some points. The htcdev site actually gave me the most trouble because I didn't realize most of the steps were completed and I could skip all the way to entering the token and the site was simply used for entering the token and getting the unlock file.
And yes, I almost said the same thing about the relock step. I had to read it twice to realize you didn't unlock yet. That's another thing that confused me last night was unlocking/relocking immediately.
I think this should be a sticky and all the other tutorials and such should be deleted. This is a perfect summary IMO and will use it when I unlock my friends one x
Sent from my HTC One X

My problem with this is that you packaged it all up while the individual threads for each thing are updating and you are severing up potentially outdated scripts.

designgears said:
My problem with this is that you packaged it all up while the individual threads for each thing are updating and you are severing up potentially outdated scripts.
Click to expand...
Click to collapse
I agree. While it is nice to have a all-in-one, you should be linking to the threads since they are updating them on a daily basis instead of linking to their scripts. Ive already had to change JeepFreaks script this morning as he updated it. It would make your world a lot easier if you did it that way, and also not risk giving some new user outdated scripts.
I think this should go in the General section as the first few pages should redirect to the original threads anyway.

Red5 said:
I agree. While it is nice to have a all-in-one, you should be linking to the threads since they are updating them on a daily basis instead of linking to their scripts. Ive already had to change JeepFreaks script this morning as he updated it. It would make your world a lot easier if you did it that way, and also not risk giving some new user outdated scripts.
I think this should go in the General section as the first few pages should redirect to the original threads anyway.
Click to expand...
Click to collapse
Sure thing, I will add to the original post for the links.
Also I will try to keep this updated, but yeah I might not catch all the updates

Thank you so much Rohan! Really appreciate it! Took me about 4 hours to get this done but it was worth it. Now to install cleanrom. Thanks again. This is my first time doing something like this.

Duse ijuat saw this and I'm going to do this and flash clean from when I get home and I read through this I honestly love you for doing this it helps more than you think thanks a lot
Deffinitlet should be stickied
Sent from my HTC One X using XDA

These are the best instructions! Wish i had them when all this shenanigans started. Thx

ethantarheels123 said:
Please keep this up. As it is the most aggregated list of instructions, I'm sure it will help many who have just gotten their phone. Great work by the way.
Click to expand...
Click to collapse
I agree. This guide is very helpful for me. I consider myself to be fairly computer literate and have flashed ROMs on previous phones, but I am a complete n00b to android and linux. Looking around some of the other threads -- it appears to me that there are many people who could have much confusion resolved by reading this. Thanks for the thread.
-- Jon

Not quite sure what's going on with my update...
I'm using the exe that updates the RUU and it gets stuck on the "sending to phone" step. Reboots the bootloader once, gets stuck again (as far as I can tell , nothing is ever sent) and then gives me an error telling me "The ROM Update Utility cannot update your Android Phone. Please get the correct ROM Update Utility and try again"
i've got the correct drivers installed (was having some trouble related to that a couple days ago but have since figured it all out ) would it be better to just do the update manually? (On my evo you just change the update file to Update.zip and it automatically installs it for you when you boot into bootloader)
maybe I'll have to look into it further, but just curious if anyone's run into this issue or figured out how to get past it as of yet...
Edit: Just an update- I'm betting its because I forgot to relock my bootloader before updating. So anyone who's already completed SOME of the steps in the second post here, make sure you relock your bootloader if you haven't already done so.
Edit1.5: This assumption was correct and the bootloader is now unlocked.
Edit 2- Almost done here... Busybox wont install. Tried two different apps, neither one worked. No indication as to why (got very vague error messages to the effect of "busybox was not installed")
Edit 3- FIXED- Ok, figured it out. As far as I can tell, the process should be Root first, THEN install busybox. It doesn't work without root privelages (at least that was my experience here)

Rooted Nexus S OTA Upgrade to 4.1

I am new here so please bear with me.
I have a "rooted" Nexus S i9020. When I bought it it had Android 4.0.4 installed. Recently I have been receiving a message telling me that a system update to Android 4.1 is ready to be installed. I have tried accepting the update, but halfway through it stalls and all I see is a triangle with an exclamation mark in it. The phone will then not respond and requires removal and refitting of the battery to restart it. Luckily, it has returned to working order with 4.0.4 still installed.
Is the phone not accepting the update because it is rooted?
Can I get the OTA update without erasing all data and settings?
I have an app. called Superuser v.3.1.3 on the phone. It has a box to tick marked "temp unroot" and another "OTA survival".
Would either of these tools be any use?
I have tried to understand all the information given on the forum posts but there is just too much to take in.
Can someone explain what I have to do to get the phone updated without "bricking" it?
When I enter Bootloader mode it says:
FIRST BOOT MODE
PRODUCTNAME HERRING
HW VERSION REV 11
BOOTLOADER VERSION I9020 XXKL1
BASEBAND VERSION I9020 XXKI1
SER.NO etc.
LOCK STATE LOCKED
Is this information helpful? I have read about "clockwork mods" and "Roms", but I don't know what you mean.
Thank you in advance.

Clockworkmod replaces your stock recovery and then giving you options to flash ROMs etc. If you want to learn more... start with the sticky threads in development.
Your phone is rooted so if you want to get the update you need to temp. Unroot using the superuser app like you mentioned. Try to get the update. Please report back if it helped
Sent from my Nexus S using xda app-developers app

so far no brick...
kwibis said:
Clockworkmod replaces your stock recovery and then giving you options to flash ROMs etc. If you want to learn more... start with the sticky threads in development.
Your phone is rooted so if you want to get the update you need to temp. Unroot using the superuser app like you mentioned. Try to get the update. Please report back if it helped
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
I ticked the "temp unroot" box and tried installing the update again. Same result. Install stops with exclamation mark triangle and grinning android. Restart by taking out the battery. Ok, I still have a phone. Running Android 4.0.4, but now there is no upgrade available and I will have to wait until they get around to offering it again before I can experiment further. If I check for updates, it tells me that I am up to date.
I wish that there was more information. I mean, what's the point of a triangle with an exclamation mark? Why can't it tell me what the problem is? Then I might be able to fix it.
Thank you for taking the trouble to reply.
PS. This device cost me £150, I really don't want to break it, and I would like to be in control of it. If I brick it, then I suppose I will sigh, then go down to Carphone Warehouse and sign a contract for a locked, dumbed down, boring, toe-the-line Samsung SIII. But I would much rather be the master of a rogue, rooted, rough and ready-for-anything Nexus S.

monkey shoulder said:
I ticked the "temp unroot" box and tried installing the update again. Same result. Install stops with exclamation mark triangle and grinning android. Restart by taking out the battery. Ok, I still have a phone. Running Android 4.0.4, but now there is no upgrade available and I will have to wait until they get around to offering it again before I can experiment further. If I check for updates, it tells me that I am up to date.
I wish that there was more information. I mean, what's the point of a triangle with an exclamation mark? Why can't it tell me what the problem is? Then I might be able to fix it.
Thank you for taking the trouble to reply.
PS. This device cost me £150, I really don't want to break it, and I would like to be in control of it. If I brick it, then I suppose I will sigh, then go down to Carphone Warehouse and sign a contract for a locked, dumbed down, boring, toe-the-line Samsung SIII. But I would much rather be the master of a rogue, rooted, rough and ready-for-anything Nexus S.
Click to expand...
Click to collapse
The triangle with an exclamation mark is most likely your stock recovery, that somehow got restored. Re-flash CWM or TWRP, then try to apply the OTA again.

Can't you be rooted and not have cwm?
Sent from my Nexus S using xda app-developers app

Install rom manager... the cwm 6.0.1.0 applies the ota.
Make sure you tick ota survival in superuser and after the ota cwm will ask you is you want to keep the stock recovery for next boot or keep the cwm.
Then it asks you to fix root rightz..select fix . And now you got the 4.1.1 rooted by ota
Sent from my Nexus S using xda app-developers app

monkey shoulder said:
I am new here so please bear with me.
I have a "rooted" Nexus S i9020. When I bought it it had Android 4.0.4 installed. Recently I have been receiving a message telling me that a system update to Android 4.1 is ready to be installed. I have tried accepting the update, but halfway through it stalls and all I see is a triangle with an exclamation mark in it. The phone will then not respond and requires removal and refitting of the battery to restart it. Luckily, it has returned to working order with 4.0.4 still installed.
Is the phone not accepting the update because it is rooted?
Can I get the OTA update without erasing all data and settings?
I have an app. called Superuser v.3.1.3 on the phone. It has a box to tick marked "temp unroot" and another "OTA survival".
Would either of these tools be any use?
I have tried to understand all the information given on the forum posts but there is just too much to take in.
Can someone explain what I have to do to get the phone updated without "bricking" it?
When I enter Bootloader mode it says:
FIRST BOOT MODE
PRODUCTNAME HERRING
HW VERSION REV 11
BOOTLOADER VERSION I9020 XXKL1
BASEBAND VERSION I9020 XXKI1
SER.NO etc.
LOCK STATE LOCKED
Is this information helpful? I have read about "clockwork mods" and "Roms", but I don't know what you mean.
Thank you in advance.
Click to expand...
Click to collapse
Unlock your bootloader first (will erase SD card) How to is in these.
http://forum.xda-developers.com/showthread.php?t=1007782
http://forum.xda-developers.com/showthread.php?t=1623481
after that do this
http://forum.xda-developers.com/showthread.php?t=1785672

this is hard...
thank you all, i am working on it, but i still don't understand.
Jayjay: I downloaded the SDK and followed the instructions in the guide you suggested, but my PC does not recognize the Android device.
When I try to browse for the driver software I get a Hardware Update Wizard, and then I'm up to my ass in alligators. "Choose Hardware Type" it says but none of them are accepted. There is no choice called "Android Bootloader Interface". There are 2 folders, one for i386 and one for amd64, my PC is athlon64X2 so I look in there, and there are 3 "dll"s but nothing with that name.
Anyway I thought my phone was already rooted, why do I have to root it again? Must it be done in a certain way so that you can be sure that it was done properly?
I will keep trying, but this is bloody hard work.

are you sure?
raducux said:
Install rom manager... the cwm 6.0.1.0 applies the ota.
Make sure you tick ota survival in superuser and after the ota cwm will ask you is you want to keep the stock recovery for next boot or keep the cwm.
Then it asks you to fix root rightz..select fix . And now you got the 4.1.1 rooted by ota
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
I have read this on another forum:
Please note that you cannot flash clockwork on Samsung Phones using ADB, or ROM Manager (you'll hard brick the device). If there is a version of clockwork (specific to that particular Samsung device) it must be flashed using Odin.
So what do I believe?

monkey shoulder said:
Jayjay: I downloaded the SDK and followed the instructions in the guide you suggested, but my PC does not recognize the Android device.
When I try to browse for the driver software I get a Hardware Update Wizard, and then I'm up to my ass in alligators. "Choose Hardware Type" it says but none of them are accepted. There is no choice called "Android Bootloader Interface". There are 2 folders, one for i386 and one for amd64, my PC is athlon64X2 so I look in there, and there are 3 "dll"s but nothing with that name.
Anyway I thought my phone was already rooted, why do I have to root it again? Must it be done in a certain way so that you can be sure that it was done properly?
I will keep trying, but this is bloody hard work.
Click to expand...
Click to collapse
So you didn't get through part 1 in this? http://forum.xda-developers.com/showthread.php?t=895545
This can help you with the drivers. Install and run.
http://junefabrics.com/android/download.php
I heard people using this, I've never tried it http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/ or http://forum.xda-developers.com/showthread.php?p=23573589
You are rooted but your bootloader is locked so you have to unlock it to reflash a rom, including 4.1.1. You can't do the OTA in the current state of your phone. http://forum.xda-developers.com/showpost.php?p=29519097&postcount=11
More info http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Hope this helps.
monkey shoulder said:
I have read this on another forum:
Please note that you cannot flash clockwork on Samsung Phones using ADB, or ROM Manager (you'll hard brick the device). If there is a version of clockwork (specific to that particular Samsung device) it must be flashed using Odin.
So what do I believe?
Click to expand...
Click to collapse
clockworkmod website. Pick nexus s http://www.clockworkmod.com/rommanager/

Getting tired...
jayjay3333 said:
So you didn't get through part 1 in this? http://forum.xda-developers.com/showthread.php?t=895545
This can help you with the drivers. Install and run.
http://junefabrics.com/android/download.php
I heard people using this, I've never tried it http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/ or http://forum.xda-developers.com/showthread.php?p=23573589
You are rooted but your bootloader is locked so you have to unlock it to reflash a rom, including 4.1.1. You can't do the OTA in the current state of your phone. http://forum.xda-developers.com/showpost.php?p=29519097&postcount=11
More info http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Hope this helps.
clockworkmod website. Pick nexus s http://www.clockworkmod.com/rommanager/
Click to expand...
Click to collapse
When I plug the phone into the PC a "New Hardware Wizard" starts. I guided it to the "\\android-sdk\extras\google\usbdriver" folder and it "cannot install this hardware because it cannot find any software". The folder "USB driver" has a file called "android_winusb.inf", which appears to contain information specifically relating to the Nexus S, but the sub folders contain .dlls which are not recognized by the wizard, and there is no file called "Android Bootloader Interface" anywhere.
So I tried again. This time I let the wizard search for software, and it found an Acer USB driver which it installed. But when I connect the phone it is still not recognised, and the wizard wants to run again.
Ok this time I try the PDA net software that JayJay recommends. I'm not sure what it's supposed to do, but when I try to connect my phone the PC says "Error 2DAnet driver is either not installed or must be reset, try to reboot you computer", which I do, with no improvement. Oh and a pop up from the systray sez "Broadband error 13"
I am assuming that when the phone is "recognized", I will have full access to the file system. At the moment, when I connect, it calls the phone " usb mass storage device, drive J " and is treating it as if it is a memory stick. I have successfully backed up photos, music and downloaded files to the PC. One of the things I have been trying to do is get at the wallpaper photo which I have read is in "data\data\com.android.settings\files\wallpaper.jpg" but I cannot find such a folder on my phone, so I assume it must be one of those things you get to see when you've got this "android debug bridge " thing.
I am getting tired now I have been at this for hours.
Tomorrow I will try the "ROM Manager"
Goodnight.

Progress
So I download the ROM Manager. On the first Run the screen goes black and stays black. A great start. I reboot and get Rom manager. It is trying to sell me google chrome. No thank you I want Android 4.1.
Rom manager tells me that my ROM "is not set up to receive over the air updates - please contact ROM developer." Who might that be? Is it called Herring? I have no idea who supplied the 4.0.4 ROM for this device. I try to backup the current ROM and Rom manager wants to reflash the ClockworkMod recovery.
Now I have discovered that I have CWM installed already. (It must have been there for the previous owner to have installed ICS.) I have CWM 5.0.2.0.
Still, best to have the latest version...and so I flash the CWM.
This fails 3 times and I have to reboot each time. I then try updating Superuser to the latest version. This also fails and hangs the phone, just a screen saying "downloading manifest". No sign of progress, no status bar, no rotating thingy. Eventually I reboot and try again. ( I am getting confident about this reboot game, I've had to do it lot's of times and so far it hasn't let me down, and brings me back to a working phone.)
When Superuser has finally settled down to v3.1.3, su binary v3.1.1 I have another shot at flashing CWM from ROM manager. Yeah! This time it sticks!
I now have CWM 6.0.1.0
So I back up my ROM...this seems ok apart from a message "no sd-ext found"... but I don't know what that means so I ignore it.
Now I try applying the 4.1.1 update. All looks good for a while with a little android with a dodecahedran or something in its belly. Then..clunk!
The little android is on it's back with it's legs in the air. There is a report that I send to rommanager. It is long, (would you like me to Post it?)
basically it says:
" can't open /dev/tty0: no such file or directory"
"unable to get recovery.fstab info for datadata fstab generation"
"failed to verify whole file signature"
"failed to open /sys/class/android-usb/android0/state: no such file or directory" - this over and over again...
Now I think I have a BIG problem.
I get the feeling that something is corrupted and there are bits missng from my file structure. This would explain why I could not find a "data/data" directory and a whole lot else.
Actually beginning to enjoy this, I may end up with £150 paperweight, but I am learning a lot about code. Like when I got the SDK ADB installed and typed help then found that I couldn't send the output on the Command Line to the printer so I had to look it up on Wikipedia...
I am still learning. I think I need to know where to get the true Google Android 4.1.1 from if I cant get it over the air.
I have read about a thing called Nexus Root Toolkit by a chap called Wug fresh or something, I am not unfamiliar with DOS but my command line skills are a bit rusty.
I started with Algol 60 you know.
Goodnight

Close but no cigar...
OK. I have backed up my rom, using Titanium Backup.
I have "unlocked" my bootloader using the downloaded Android SDK ADB fastboot.exe ( It's in "platform tools" now, not "tools")
I have CWM 6.0.1.0 , Superuser 3.1.3 with OTA survival ticked.
Now all I have to do is wait until the OTA upgrade is offered again. ( It seems to come round randomly, every few days.)
Ssh! wait.. Yes! After leaving the phone overnight, the upgrade was waiting for me in the morning. I tap install..
...and fail again.!
This time its:
E: failed to verify whole file signature
E: error in /cache/9ZGgDXDi.zip (status 7)
installation aborted.
Why do you guys make it sound so easy?
I clear my cache ( if there is an error in it, it makes sense to clear it.)
I'll try again tomorrow.

monkey shoulder said:
OK. I have backed up my rom, using Titanium Backup.
I have "unlocked" my bootloader using the downloaded Android SDK ADB fastboot.exe ( It's in "platform tools" now, not "tools")
I have CWM 6.0.1.0 , Superuser 3.1.3 with OTA survival ticked.
Now all I have to do is wait until the OTA upgrade is offered again. ( It seems to come round randomly, every few days.)
Ssh! wait.. Yes! After leaving the phone overnight, the upgrade was waiting for me in the morning. I tap install..
...and fail again.!
This time its:
E: failed to verify whole file signature
E: error in /cache/9ZGgDXDi.zip (status 7)
installation aborted.
Why do you guys make it sound so easy?
I clear my cache ( if there is an error in it, it makes sense to clear it.)
I'll try again tomorrow.
Click to expand...
Click to collapse
Ok now just get the proper factory image. You are a Nexus S i9020 just check if you are a T or an A (look under the battery). Flash Android 4.1.1 (JRO03E). Follow part 1 of this guide http://forum.xda-developers.com/showthread.php?t=1785672
Then flash clockwork and super su
Stock, rooted, profit!

stick with it...
monkey shoulder said:
OK. I have backed up my rom, using Titanium Backup.
I have "unlocked" my bootloader using the downloaded Android SDK ADB fastboot.exe ( It's in "platform tools" now, not "tools")
I have CWM 6.0.1.0 , Superuser 3.1.3 with OTA survival ticked.
Now all I have to do is wait until the OTA upgrade is offered again. ( It seems to come round randomly, every few days.)
Ssh! wait.. Yes! After leaving the phone overnight, the upgrade was waiting for me in the morning. I tap install..
...and fail again.!
This time its:
E: failed to verify whole file signature
E: error in /cache/9ZGgDXDi.zip (status 7)
installation aborted.
Why do you guys make it sound so easy?
I clear my cache ( if there is an error in it, it makes sense to clear it.)
I'll try again tomorrow.
Click to expand...
Click to collapse
Its a bit confusing to begin with mate, but read and re-read the many tutorials and guides on here, take it slowly and step by step and youll get there in the end.
Youll be flashing custom ROMs before you know it! (take your time and always backup)
Is worth it. :good:
S

It is good that in the process you learnt lot of things. Now you have fastboot working and you know how use fastboot.
Now that the OTA is giving errors, the best way is to flash the Jelly Bean factory image which is available from Google. As per suggestions from
jayjay3333 said:
Ok now just get the proper factory image. You are a Nexus S i9020 just check if you are a T or an A (look under the battery). Flash Android 4.1.1 (JRO03E). Follow part 1 of this guide http://forum.xda-developers.com/showthread.php?t=1785672
Then flash clockwork and super su
Stock, rooted, profit!
Click to expand...
Click to collapse
Go to the link to download the image files first, then flash the 3 files using the fastboot commands provided. The overall process of flashing the factory images does not take more than 5 mins.
Best of luck.

nearly there...
jayjay3333 said:
Ok now just get the proper factory image. You are a Nexus S i9020 just check if you are a T or an A (look under the battery). Flash Android 4.1.1 (JRO03E). Follow part 1 of this guide http://forum.xda-developers.com/showthread.php?t=1785672
Then flash clockwork and super su
Stock, rooted, profit!
Click to expand...
Click to collapse
Ok I downloaded the jro03e file it is 191Mb
The download is a .tar file not a tar.gz It is called soju_jro03e_factory_c9f5a67d.tar. It is196,458 kb
The instructions say I should 'extract' it, using 7zip, which gives me a file with the same name but no extension! Windows identifies it as a ".file". It is now 207,410 kb.
The instructions say there is a folder inside which I should extract. No such thing is visible.
The next part of the instructions says I should modify the file names before running. Does that mean:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju_jro03e_factory_c9f5a67d.tar
Is that right? Shouldn't all those hyphens be underscores?
Is that xxkl1 or xxki1 the same or different? ( looks like a typo).
Does only the last bit change?
Ready when you are!

oops silly me...
Well it looks like I don't understand 7Zip very clearly.
After a bit of fiddling about I "extracted" the .tar file, then "extracted" the resulting file to get a folder with a bootloader image, a radio image and an image-soju-jro03e.zip
I tried to follow the XDA instructions given here http://forum.xda-developers.com/showthread.php?t=1785672
but it seems I don't understand how to use ADB fastboot either, because when I entered the commands all I got was a list of options, a sort of helpfile for the fastboot command.
I am just not comfortable with the command line, you make one mistake and you've got to enter it all again.
Anyway I decided to try the "Nexus Root Toolkit" http://www.wugfresh.com/dev/nexus-root-toolkit/
After ensuring that my drivers were OK, I pointed the toolkit at the files and executed them individually. ( There is a "flash-all.sh" , but I don't understand how to use that. )
first of all I flashed the bootloader... Success! I now have bootloader crespo i9020xxlc2.
I didn't bother with the radio, I already have radio-crespo-i9020xxki1.
So I try to flash the jro03e.zip... Damn! The toolkit cannot find my device! Funny, it was perfectly happy before the bootloader flash...maybe that has changed something. I start again, reboot everything, check drivers... yes all ok. This time the toolkit is happy and offers to install the .zip, I include a full nandroid backup and drag and drop the image-soju-jro03e.zip to the install/flash.zip box.
TWRP v2.2.0 does it's thing and after a lot of stuff happens on the phone screen I get a menu, from which I access a report that basically says: "Error flashing zip". My heart sinks...
Other attempts with different settings result in the same:
"signature verification failed"
"no MD5 file found"... etc... etc...
So I reboot again and am relieved to find that I still have a phone.But it is still 4.0.4.
Ah! but now it has the image.zip on the SD! Progress! My heart soars with new hope!
This time I use ROM Manager to install the .zip from SD... But no such luck, "installation aborted", the little green android is flat on its back again.
Rom Manager generated a recovery log. (would you like me to post it?) Basically it says:
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mtdblock4 on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
Installing update...
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/!ReadyToFlash/image-soju-jro03e.zip")
Have you any idea what that all means?
Will I ever get JB 4.1 on this phone?
Its beginning to look like there is something fundemental missing.
Please help!
S.

its gone quiet...
This thread doesnt seem to be getting attention anymore so I shall start a new one.
Is that ok? Its a new question "what does this recovery log tell me?", but it is still the same problem. The trouble is there are too many questions and it is very difficult to know what to ask.
I am still trying to get Android 4.1 on my phone. I have read the various instructions and tried to follow them but they did not work in the way I expected. Part of the problem is that I do not understand what I am doing. I don't understand the tools I am using.
I think it would help a great deal to see the file structure on my phone.
Is there a program that can look at that like windows explorer? Then I might be able to see what I am doing. At the moment I have no idea what is on my "SD card". The Nexus S doesnt actually have one of course, but I understand that it has 16Gb of storage that work like an SD card.
Now In the course of this project, I have "Backed up" with Rom Manager, but I don't know where that backup is, or what it is called. I did a "Nandroid backup" with the Nexus Root Toolkit but I have no idea where that is (is it on PC, or on the phone somewhere?) or what it is called. I assume it will be found automatically by the software when it needs to restore it. I have not backed up with "Titanium Backup" beause I am not sure how to do it. When I select "Backup/Restore" it displays a long list of files, some in red some in green, which say they are not backed up yet. Which ones do I select? All of them? I have no idea.There are so many options in the menus that I am terrified of Titanium, and don't know where to start, and it is going to take days to read the helpfiles. Is Titanium saying they are not backed up because it didn't back them up, or because it can't recognise the backups that were made with Rom Manager? If I backup everything with Titanium, is it going to make backups of the backups that another program made?
I'd like to be sure that I have just one good copy of the backup, that I havent filled my memory with useless junk.
S

[Q] My Asus TF300T is on stock Android 4.0.3, what to do next?

The darn thing just started nagging me with an update notice that comes back every ten minutes. I read somewhere that updating is going to stop me from doing certain advanced things, so I finally got the last push to go for either CM10 or CleanRom, depending on which one gives me the most advanced and pleasant experience.
But before doing so, it's recommended to get some kind of flash info file or something from it that doesn't come out when upgraded to the latest firmware but does on the old 4.0.3. What would be the best way to go from now on?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Found something myself, thank me very much!
http://androidroot.mobi/t3_nvflash/
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

do yourself a favor if you gonna go with a custom rom, Energy rom and TWRP recovery!

What are their advantages when compared to CM10 or Clean?
Sent from my Galaxy Nexus using xda app-developers app

This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...

Lex_Michdeandroid said:
This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...
Click to expand...
Click to collapse
Your tablet will say it is unlocked in the upper left part of the screen when The Asus logo appears at boot.
Sent from my Transformer Pad TF300T using Tapatalk HD

Hi, if your tablet is still on stock 4.0.3 (ICS bootloader), I recommend doing NVflash first
http://forum.xda-developers.com/showthread.php?t=1894867
If you have already updated to JB bootloader it won't work.

It doesn't say Unlocked, so I guess that's why I don't see the USB option when I try to get into Fastboot?
I'm also not able to get ADB commands recognized on my win7x64... Am I doing it wrong? What's the proper method/order of events here? Isn't there a really n00b-proof version of a guide here, or is it something I should write as soon as I get out of this mess and get it working?
Sent from my Galaxy Nexus using xda app-developers app

Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596

pjc21 said:
Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596
Click to expand...
Click to collapse
Perhaps I'm not really looking in the right location, but the Asus website says I need to choose an operating system and gives me no option to choose. This way I'm not able to download the apk...
Edit:
Tried clicking the links with the tab and it started the download... Device now has an unlocked bootloader. On to the next one...
Edit2:
Ah, now I get it. Pay attention to where that Android SDK stuff is being installed. Mine got installed in the folder I unpacked the installation files! So somewhere 256 folders deep on the Desktop was the right 'adb.exe' file. Make sure the tf300_nvflashpack files are in the same directory and open the command prompt there. After that I got back to the http://androidroot.mobi/t3_nvflash/ website and entered the commands. One moment please, back in a flash!
Edit3:
Now I have 5 files in /mnt/sdcard/AndroidRoot and I uploaded them to my Dropbox. I'm guessing they are the right files...
blob.bin
blob.log
bootloader.ebt
create.bct
recovery.bct
To be sure I uploaded them all.
Copied these files into the SDK folder, along with the other zipped files for nvflash so the nvflash command works to get the other three backup files.
Edit4:
Went on following the guide and checked the video to see if I was really going the right way. Finally I have all files backed up. Goddamn what a journey, but it makes you grow a pair of balls. Now on to the next hurdle, getting a proper ROM, because stock is really getting on my nerves.
So CleanRom, CM10 or Energy ROM? Should I first upgrade to JB? Without or with the popup I'm constantly getting?

Lex,
You have alot of the same questions I do/did, and I have your original post open in another window to respond to all your questions. I'm working on writing a guide for all this stuff so this is rather helpful. If I respond to a question twice, please forgive me as I'm literally just going down the list and answering em as I read em.
In your first post, the file you're referring to is gathered via NVFlash. I haven't used NVFlash yet, but what I understand is that if you use this tool it basically backs up your ICS (4.0.3) bootloader information. The newest firmware change is to Android Jelly Bean (4.1.1) and that re-locks your bootloader. Once you go to JB, you cannot go back. So this servers as a backup (again, this is just how I interpret the information from their website. I don't know how correct my interpretations are, and have actually opened a thread to ask for clarification about this program).
For the drivers, all I did was download the android SDK and install the 'android tools' and "extra - google drivers' from the list. My laptop was just recently wiped-out so I have no prior drivers installed, nor have I connected my tablet to my computer yet (just got a replacement tablet last weekend). I didn't use the universal driver or any other add-ons. Just use the SDK, it will install drivers, and then it will detect your device. I verified this by typing "adb devices" in command prompt and it detected the serial # of my device.
Within that same post, you had some confusion about ADB. It's just an executable, and you have to use the command prompt window from whichever directory it is installed to. So once you unzip the Android SDK or wherever you installed ADB to, use the command line commands "cd directory/where/adb/is/installed" to navigate to it, or use shift + right click within that folder and it will have an option to "open command prompt here" with admin privileges. That makes life a bit easier. Other people also install their SDK to C:\android\SDK or something similar, so it's less to type.
In order to determine if your bootloader is unlocked, look at your tablet in the top left hand corner when it boots up. It will say "Device is unlocked" and list a bunch of numbers (which if I remember correctly would just be the firmware information). Your device will not be unlocked until you actually download the unlock tool from asus' website and push the file via adb to your tablet and install it. That is, you have to take a very specific, very advanced overt action to unlock it. Nothing else and no one else can do it for you nor can it be done accidentally.
Next post (#8 in the thread): You are correct that fastboot will not show unless you are unlocked. I just verified this on my not-unlocked, not-rooted new tablet, and cannot enter fastboot mode. Your ADB commands wont work if your drivers are not correctly installed.
Post #10: You have to select "Android" under the OS drop-down box to find the unlocker app. As for the location of the ADB.exe, mine was found in this subfolder within the android SDK: <whereveryouunzippedit>\Android SDK x86_64\adt-bundle-windows-x86_64\sdk\platform-tools
That folder contained the correct (and I think only) adb.exe I needed.
For your last part, I think you should try out a number of ROM's to see which you like best. I've tried all the major ones (CM9, CM10, CleanRom, Hydro, Blackbean, and some of the stock rooted/de-odexed) ROMs and used Blackbean for the longest time because of how slick it looks (all black) and how easy it is on my eyes.
Make sure you document the steps you took so you can remember them in the future. I'm working on writing a guide right now and documenting my steps to go from a stock, locked, and not-rooted tablet to a rooted unlocked and custom flash tablet.
I really hope I was able to clarify some things. I am by NO MEANS an expert but I've spent many hours experimenting and think that I wish I had someone to answer my questions when I was first learning, rather than learning by mistake.
Hopefully this helps,
Opethfan89

Hi, I use Energy rom which I find pretty good, you will need to update to JB first as Energy, CM10 & Clean rom are all JB bootloader compliant. My tab came with JB pre installed so not sure what the best way to update is but would assume since you still have stock recovery would be with OTA update (popup notice). Here is a guide to update to JB but I think this is if you have already installed a custom recovery as it looks like you flash back to stock recovery first, thats why I think if your getting update notice and still have stock recovery, go with that.
http://forum.xda-developers.com/showthread.php?t=1845377
Once you have updated to JB stock here is a guide to install custom recovery (CWM or TWRP), root & install custom roms.
http://forum.xda-developers.com/showthread.php?t=2041627
Here is link to TWRP recovery (I had issues with CWM).
http://forum.xda-developers.com/showthread.php?t=1672108
Hope this helps.

opethfan89 said:
Lex,
You have alot of the same questions I do/did,
[..]
Hopefully this helps,
Opethfan89
Click to expand...
Click to collapse
I can only click the thanks button once, but I clicked the f- out of it that one time. Although I already got to the point where my stuff is backed up, it is really good for my/our fellow adventure-seekers to have an answer to these FAQuestions. It's awesome you took the time and effort to type that much words to help out someone you don't even know. Thanks again!
pjc21 said:
Hi, I use Energy rom which I find pretty good,
[..]
Hope this helps.
Click to expand...
Click to collapse
Same goes for you! Tomorrow I will be trying as much ROMS as I can to see which one suits me best. Also repeating this process is the best way to learn something and since I'm unbrickable, I am going to flash the hell out of it for a few days. I'll try to post my steps and findings here so I (and perhaps others with the same trouble) can benefit from it in the future.

Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:

pjc21 said:
Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:
Click to expand...
Click to collapse
It's upgrading now. Of course I forgot I lost root with the last OTA update and I forgot to make sure I rooted the thing so it was able to use the rootkeeper after upgrading to JB. I hope there is some documentation on rooting JB, because at the time this all happened root was not possible yet. It's past 1 AM over here, so I guess it's best to save this quest for later when I had some sleep.
Edit:
Just for kicks I tried 'Root Checker' and it said 'no root'. Then I saw 'Rootkeeper' was installed. Opened it up, tapped the restore button... Device rooted! Guess my memory is really failing big time... One down, # to go.
Edit2:
Installed TWRP:
Just downloaded the .blob from their website and
put it in the platform-tools folder.
Then renamed it to TWRP.blob.
Turned off tablet,
plugged in USB cable in the tablet ONLY,
hold volumeDown button,
plug into laptop holding button,
waiting...
choose USB logo,
open cmd-line in the platform-tools folder,
run command: "fastboot -i 0x0B05 flash recovery twrp.blob"
waiting...
Done. Let's see if it works...
Edit3:
At first I didn't understand how to get into TWRP (DOH!),
Hold volDown, power on, choose RCK.
Edit4:
Been having a fight with TWRP when I try to install CM10.1 (latest nightly: 20130121). Gives me an error status 7 or something...
Code:
Verifying update package...
assert failed: getprop("ro.product.device") == "tf300t" ||
getprop("ro.build.product") == "tf300t"
E:Error in /external_sdcard/CROMS/****.zip
(Status 7)
Error flashing zip ' /external_sdcard/CROMS/****.zip'
Of course, ****.zip is a long filename I didn't want to type completely here.
Will try to figure out whats wrong later today, first I'm going to try restoring the backup I made earlier, just to see how a complete backup works when the tablet is wiped back to factory settings.
Edit5:
The backup stuff is really cool! My tablet is back the way it was even though I wiped it completely!
Back to the ROM rumble... baked_tf300t_blackbean-6_jb-bl_b6.zip gives me the same error. Starting to get annoyed again... Let's try something different, CleanROM. Download is taking ages... I'm restoring again, so I can use the tablet for the rest of the day. As soon as I feel like it I will try again, for now I'm giving it 'the finger'.
Edit6:
Cleanrom is installing now. I guess CM (baked is CM based right?) was causing some trouble...
Done installing...
Wipe Cache/Dalvik...
Reboot...
Android is upgrading...
Might need to choose the small font, my screen is really clogged up with stuff. Didn't expect to keep my settings etc., thought it would be completely wiped. I'm going to restore and then reinstall with the highest DPI setting first, then I'll wander around the rom to check if I like it.
Edit7:
I think I'll stick with this one for a few days, runs fine if you ask me, maybe take the time to finally update my Galaxy Nexus to CM...

[Q] Rooting, Flashing, Upgrade services needed!

I've searched & found 'How to....' threads on here but TBH I'm not a techy and most of it doesn't make sense to me.
I did try to upgrade from 4.0.4 to 4.1 this week and almost succeeded until some 'signature not recognised' message appeared. So I'm going to attempt another way (if possible/allowed) and ask if there's anybody out there who'd be willing to root (whatever that means), flash (ditto) and upgrade to 4.1 for me in return for payment.
I really hope this isn't against forum rules - it's a genuine, last-ditch attempt.
I live in the West Mids but travel a big chunk of the country each week so could possibly deliver the thing.
Here's hoping for an avalanche of replies.....

Can anyone tell me why I get the 'signature not verified' message please?
I've downloaded the upgrade from an October thread on this forum.

Which xoom do you have (wifi, 3g/4g, international, family)? Are you rooted yet?

dfib1 said:
Which xoom do you have (wifi, 3g/4g, international, family)? Are you rooted yet?
Click to expand...
Click to collapse
Thanks for replying!!
It's the wi-fi model. As for 'is it rooted?' - I would say not. One, because it's hardly been used and two, because I have no idea what 'rooted' means.

junctiontwo said:
Thanks for replying!!
It's the wi-fi model. As for 'is it rooted?' - I would say not. One, because it's hardly been used and two, because I have no idea what 'rooted' means.
Click to expand...
Click to collapse
Sorry I took so long to answer.
As for being rooted if you are the only one to have own the xoom and don't know what it means then you are most likely not rooted. Root is like getting administrator rights in windows. It gives you the ability to customize your device, install custom roms and also completely screw up your device .
You should be able to go to settings-about tablet--update (or system update) and it will check for your update and ask you to start the download and install. If this does not happen then you can flash back to Honeycomb (which I can walk you through this will also wipe all your data or maybe for a fresh start) and let your device automatically update to ICS (4.04) and the JB (4.1).
I can also walk you through rooting and installing a custom JB rom like you asked for free.

dfib1 said:
Sorry I took so long to answer.
As for being rooted if you are the only one to have own the xoom and don't know what it means then you are most likely not rooted. Root is like getting administrator rights in windows. It gives you the ability to customize your device, install custom roms and also completely screw up your device .
You should be able to go to settings-about tablet--update (or system update) and it will check for your update and ask you to start the download and install. If this does not happen then you can flash back to Honeycomb (which I can walk you through this will also wipe all your data or maybe for a fresh start) and let your device automatically update to ICS (4.04) and the JB (4.1).
I can also walk you through rooting and installing a custom JB rom like you asked for free.
Click to expand...
Click to collapse
Please don't apologise - you're the only one to answer!
I've tried the system update and have been told that there are none. (In my ignorance I actually thought it would update to 4.1.2 automatically!).
Your offer to walk me through the rooting & upgrade is extremely generous and I accept without hesitation.
If it's flashed back to HC, will it default back to ICS or move to JB?
A huge 'Thanks'.
James
PS. Having tried numerous times very recently to upgrade there's no data to erase so that's not an issue....

I am going to give you the steps to unlock your xoom, install a recovery, root, install CWM Rogue Touch recovery (better than the one you used to root) and then install stock JB.
Now that we are talking root I am going to ask a moderator to moved this thread to the root section.
Here is how I rooted my xoom.
follow the directions here but instead of doing step 1 follow this for adb install http://www.support-4-you.com/main/i...ged-adb-installation&catid=40:how-tos&Itemid= it is a 1 click adb install then follow from step 2 on.
When you are done there you can install CWM Rogue Touch screen recovery
Download CWM Rogue Touch zip and put on the root of your external sd card. ( if you don't have a sd card we will do it another way just let me know)
Boot into recovery by turning your xoom off.
1. press power
2. when the moto dual core logo comes on wait 3 seconds and press volume down
3. recovery should be displayed across the top press volume up.
You can skip steps 1- 3 now that you are rooted if you download Quick Boot open it, select recovery and the grant Super user permission
4. go to install zip from sd card (just like when you rooted) and find the CWM Rogue Touch Zip and install
5. reboot your xoom
6. you now have CWM Rogue Touch installed.
To install JB on your xoom you do need an sd card for this part
DownloadJB stock for wifi xoom and copy to your sd-card
Here is the thread discussing this [JB]Stock Android 4.1.1 JRO03H, Root, via CWM Recovery (US Wi-Fi MZ604) and also there steps for installing it but I will post them for you here.
boot into recovery
select backup and let it backup your current system (a Parachute)
then select wipe factory/data ( I Can't remember excactly what it says because I use a different one)
then select install zip from sd card
locate the JB rom you copy to your sd-card and install.
reboot system (it will take some time the first time)
sign in to android with your gmail account.
You are on JB
Good luck and don't worry if something goes wrong we can get you out of 99.99% of any issues that arise.

dfib1 = I cannot thank you enough.....
The frustrating thing is I'm about to leave the house and am working away until the weekend so can't try it until then! I'll let you know the outcome.
Have a great day :good:

If you need help with his excellent guide just post here or hit with a pm
Sent from my Xoom using xda app-developers app

Ok, a quick mid-procedure question....
(I'm doing something fundamentally wrong because I can't quite finish the upgrade).
Do I install the folders onto the Xoom from the SD in a zipped or un-zipped state? I've tried both but no luck so far in completing the task.
I've rooted successfully as my PC recognizes the device. I believe I've installed CWM ok - is there a way to confirm this?
On the final 4.1 install I get the 'installation aborted' message as 'signature not verified'. One thing I may be doing wrong is installing the wrong files? On selecting the JRO03H folder I'm then given file choices and I'm clicking on what I think are the most obvious. I can post a list of the choices if it helps?
Sorry to be such a newbie pain - I realize that these questions are irritating to those 'in the know'!

did you reboot after fastbooting the recovery? the recovery says clockwork at the top. It should also be touch screen controlled
When you move the zip over leave it as a zip on you xoom and when you flash the recovery will unzip it for you.

what step are you up to?

Sorry for the late update. I've tried the whole procedure several times from the very beginning, even removing previously installed Rogue & JB software, but STILL get the same error messages as previously described. I've re-booted at the right time according to the instructions but this still makes no difference, and have checked the 'USB de-bugging' option.
I did make a couple of basic errors in the Command function to begin with but realised these & corrected them. My device serial no. appeared so I assume I rooted successfully? I'm able to change Developer settings which I couldn't before. I even installed the USB drivers independently via the Motorola website.
I have a free day today so am going to make a bucket of coffee, make myself comfortable and start again.
One quick point - I'm in the UK and assume you two helpful guys are in the US? Looking at numerous sites it seems our respective Xoom models have different procedures which is maybe why this isn't working?
Thank you again for your seemingly endless patience.......

i believe you are getting these issues because you might still be running the stock recovery.
lets just backup and start fresh.
You followed the instructions mentioned before and I assume you have adb and fastboot installed.
Connect your xoom and make sure usb debugging is on.
open up a command line and type adb reboot bootloader
I'm going to assume because of the previous steps you unlocked the bootloader if not type in the command line fastboot oem unlock
You can download the recovery from here http://bit.ly/iLRAIV
If unlocked at the bootloader type fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img Note:make sure the img file is in the same folder where your fasboot.exe is in the sdk
after it has been flashed reboot device by hold volume up and power.
Move the JB stock rom into your sd card. you can download the rom from here http://www.mediafire.com/?qhbhlbvu859bv0f
after the device restarts type adb reboot recovery
in recovery Wipe everything except the sd card. Then flash the above jb rom. In theory everything should work. If you keep getting the error get back to us because Im going to give up and guide you through the install of the Team EOS Jellybean 4.1 rom that I know works without issues. PM if you want to have my direct contact info for gtalk so we can discuss further for any issues.

OK I've just tried another 8 times to root the thing, c-a-r-e-f-u-l-l-y following the instructions step-by-step.
1. I don't have the 'from SD card' option, instead have 'from USB drive'. I have a 16Gb flash drive connected via an adaptor for the Xoom which doesn't appear to prevent anything as it reads the contents of the card just fine, unless you can tell me otherwise?
2. In Recovery I get these options:
* reboot system now
* apply update from USB drive
* wipe data/factory reset
* wipe cache partition
3. Even when trying the very first install (Rogue), I get:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E: signature verification failed
Installation aborted
I love a challenge and always get a buzz when I manage to do something that is foreign to me i.e computers. On this occasion however I'm fast getting to the stage where I think it'd be easier to leave things at 4.0.4.
My reason for wanting the upgrade in the first place is because I'm comparing this tablet to my work-supplied Galaxy Tab 2 running 4.1.1. Realistically I don't think the two will ever be comparable and I'm probably foolish to think this could be the case. It only remains to say that I am so very grateful to both of you for taking so much time & effort in talking me though the procedures.
I consider myself pretty 'switched on' but this has me foxed!
Cheers guys - have a great weekend. Hope the snow doesn't cause you problems!

here are the outline of the steps
1. unlock your xoom
2. fastboot a recovery to install custom recovery on your xoom
3. reboot into new recovery
4. flash universal root zip to root your phone
5. reboot phone that is now rooted.
6. reboot phone into custom recovery again
7. flash jb update
I think you have missed step 1 or 2.
When you type fastboot oem unlock what does it say?

Hmmm, I MAY be one step closer?
After typing' fastboot oem unlock' the tablet has gone into 'Starting Fastboot protocol support' but appears to be stuck. Do I wait until it's done it's thing?
OR would it be a whole lot easier for all concerned if we tried your other suggestion dfib and flashed back to HC and then to JB?

What if you type adb devices? Does a bunch of numbers show up or does it say waiting for device?

Hold the front page!!!!!!!
I just watched a video on how to unlock and it's worked. You were quite correct - I had missed your point 1 above and probably point 2. I'm moving onto the next bit now....

Great let us know what happens. I will be around for a while.

Upgrade from Nougat (7.1.1.) to latest Pie

So iv had this device for quite some time now. Updating the phone through the internet doesnt do anything and goes into loop and restarts. So im stuck on this Android version for a long time.
Im a little bit of a newbie when it comes to firmware flashing rooting etc. I am on an Xperia XZ Premium G8141 with Build number 45.0.A.5.1
I already have the bootloader unlocked.
What would be the right steps for me to take in order to upgrade to Android Pie safely? Maybe even root the phone?
Stock Android Pie would be the best option for me i think

So i managed to Upgrade on my own to Android 8
Downloaded firmware from XperiFirm and flashed it on my device with newflasher
Still when i go to system updates it doesnt update. It downloads a 1.5 gb file then restarts and the update is still there.
Any solutions?

Your device is unlocked. OTA is broken. You must flash 9.0 manually. And no there is no way to re-lock the bootloader that I know of. If you would like me to tell you dee way to do that PM me or reply back here

lonewolfbtown said:
Your device is unlocked. OTA is broken. You must flash 9.0 manually. And no there is no way to re-lock the bootloader that I know of. If you would like me to tell you dee way to do that PM me or reply back here
Click to expand...
Click to collapse
i would like to know how yes. thanks
lets do that here and not over pm so maybe more people looking for something like that could find it also
i would like to have Android 9 Pie and also maybe give it a try to root it.
Iv never done that before and since its not my main device i would give it a go and install some custom apps and modifications.

Ok ? I'm at work right now but once I get home I'll write you up a guide here on how to get to pie, how to flash twrp, how to root phone, and how get xposed if that's what u want or existenze room working.

lonewolfbtown said:
Ok I'm at work right now but once I get home I'll write you up a guide here on how to get to pie, how to flash twrp, how to root phone, and how get xposed if that's what u want or existenze room working.
Click to expand...
Click to collapse
thats great! thanks alot for taking the time and patience to do this. much appreciated!

I just know how it feels to have ur thread go ignored. So I try to help anyone in any thread I see.
Do you want volte for T-mobile cause I can make that happen. Also do u have fastboot and adb drivers installed?

lonewolfbtown said:
I just know how it feels to have ur thread go ignored. So I try to help anyone in any thread I see.
Do you want volte for T-mobile cause I can make that happen. Also do u have fastboot and adb drivers installed?
Click to expand...
Click to collapse
im not sure what you mean with volte for T-mobile. If it has to do with networks im actually in Greece and we dont use T-Mobile here. I saw a Greek Android version up to 8.0.0. which i have installed right now
I have fastboot and adb drivers already installed, but the adb driver seems to be giving me some error and exclamation mark in device manager for some reason. The phone is recognised by Xperia Companion for example though

figure out that error. right click on the driver and look in details and report back. An xperia companion should most likely be useless at this point since u unlocked it

Well from a translation of Greek it says "not possible to start this device (code 10)"
Its the Sony sa0116 adb interface driver right? That's the one I could find
Sent from my iPhone using Tapatalk

First if your phone blows up, freezes, dies or boot loops it is not my fault. I will help if i can but if you blame me. I will not feel bad
First things first Here's what you need!!!
-flashtool- If you can find the xperia ftf downloader only more power to you. http://www.flashtool.net/index.php
-newflasher, This is the correct tool for flashing new firmware on the xz premium https://forum.xda-developers.com/crossdevice-dev/sony/progress-newflasher-xperia-command-line-t3619426
-twrp image: https://dl.twrp.me/maple/
-root aka magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
-minimal adb. Not gonna link it. so easy to search. INSTALL THIS BEFORE EVERYTHING ELSE
Ok here we go to getting to 9.0 and root:
Getting your firmware
-First install flashtool after you download it.
-Once its installed you want to navigate your explorer to where it was installed, and find the drivers folder. Click the drivers exe and it will come up with many options. You want adb and fastboot. I think its the first two. Click install
-Drivers installed? OK moving on! Open flashtool and navigate to xperifirm. Should be on the toolbar. Another window will pop up with a bunch of xperia phones and years. Find your phone. click your region. In the right screen of the window it will show what firmware is available. Most recent pie version will end in .24. If unsure, GOOGLE THE FIRMWARE NUMBER.
-CLICK ON THAT FIRMWARE AND IT WILL BEGIN TO DOWNLOAD. after download it will unpack it
-Once it unpacks and finishes, close the download window. Close xperifirm. Dont touch flash tool. Leave THAT OPEN. Flashtool will then unpack the ftf (which is important that it does) and the bottom bar will have progress bar. It will be clear when it finishes or fails but you will see red letters if it did.
-Firmware unpacked? Great! Extract your newflash firmware. All items in the zip must go into the folder where your firmware was downloaded. Mine looks like this C:\Users\rocke\.flashTool. It will be in the download folder and it will have your unpacked firmware. Go into that folder and it will have a bunch of files from your ftf. Move your new flasher files in there. Make sure boot folder is emptied into the main folder where are the others are and new flasher. Delete boot folder.
Flashing time
-hold volume down and plug in phone to pc. Green light should come one.
-Open Newflasher.exe
-a few questions will appear. I dont type = yes on both questions cause its kinda pointless unless you need gordon gate drivers and u want to back up something that i think i dont need/
-WHoooooosh! Command lines will start popping up and your phone is being flashed. Let its do its thing
-Eventually it will tell you you can disconnect your phone after u close the window. Boom android 9
Give me the root captain!!!
root.....a dangerous but such a fun little thing
-first your twrp. Hold volume up and plug in phone. Blue Light will come on. the twrp image must go in the minimal adb folder. Other wise adb will think your crazy and say it doesnt exist.
-type this in minimal adb fastboot devices. it will show if a fastboot device is available. If not we have problem with drivers. If yes. Then we keep trucking on
-flash twrp. type this command in fastboot flash recovery twrp.img (rename image obviously) It will flash it to the phone.
-Reboot phone into recovery. Volume down and power button. Release at sony logo or it might be the unlocked bootloader warning. Cant remember. Either way release power button on that logo and keep holding volume down.
Boom your in twrp.
-if magisk wont move over to your sd card in twrp. its time to adb push
-adb push magisk.zip /sdcard
it will move the file.
-Find where you pushed it and install magisk. It will do its thing.
If you followed the instructions your phone should be rooted and you want need a drm fix to cover the holes of the BL unlock. If hit any snags message me or reply here

Thanks for taking the time to write this.
The first part of flashing Android 9 I already know how to do. As I mentioned I my second post in this thread I already upgraded from Android 7 to Android 8. My problem was that XperiFirm doesn't have Android 9 for my device and Android 8 is the latest I could find to download. I would have already flashed Android 9 otherwise
As for the rooting part I will have a look when I'm back at home
Sent from my iPhone using Tapatalk

Yes I understand that. If you want 9 u need to use xperiafirm and get a different region that has access to it. If you use Greece ftf that is still on oreo. Chance is you'll be on 8 for a long time

I'll try and find one with Android 9 then when I get the time to do that. Also pretty busy with work
Sent from my iPhone using Tapatalk

ce1 matches the europe basebands. that i know is for sure on 9.0

i think i will give a try to a custom Rom instead like this one :
https://forum.xda-developers.com/xz...tenz-pie-v3-5-0-beta-31-01-19-t3895452/page28