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)
Related
The Ultimate Guide to the Nexus S
(and a ROM list, too!)
I decided to make a thread on unlocking the bootloader, rooting, installing ROMs & kernels because if you're kind of new to Android, all this can be very overwhelming.
I'll try my best to keep this updated, but I can't make any promises.
This should clear up any doubts and misconceptions you may have, but if you have a question for me, feel free to post here. Don't PM me, please.
Click to expand...
Click to collapse
First and Foremost
Messing around in non-userspace is dangerous. If you mess up a radio flash, for example, you'll mess up your phone pretty bad. Be careful, and if you aren't sure what you're doing, don't do it.
Also, when you unlock your bootloader, there is a warning stating that your warranty is void. However, if your phone needs repairs, simply restore the stock ROM and relock the bootloader (I'll explain how to do all this below) and Samsung will almost certainly accept it for repairs.
Click to expand...
Click to collapse
Requirements
A computer (this guide will be geared towards Windows because, sadly, it's the most widespread OS out there.).
A Google Nexus S.
A MicroUSB cable.
Time and patience.
Half a brain.
Click to expand...
Click to collapse
Identifying your phone
Turn your phone off and remove the battery cover and the battery. There will be a sticker below the battery with model information. Look for where the Model information is. If the model is GT-i9020, you have a SAMOLED screen Nexus S. If the model is GT-i9023, you have a SLCD screen Nexus S. This is important because some kernels and ROMs are compatible only with one or the other version of the phone.
Click to expand...
Click to collapse
Unlocking the BOOTLOADER!
A word of warning: Unlocking the bootloader wipes your user data and your internal storage (music, photos, movies...). You might want to back them up.
You need to unlock the bootloader in order to flash ROMs and kernels on your phone. Luckily for you, the bootloader in the Nexus S is very easy to unlock.
To unlock the bootloader, put your phone in bootloader mode. This is done by turning your phone off and then turning it back on while holding the volume up button.
When in bootloader mode, you'll see some text in the upper right corner of the screen. None of this really matters, except for the very last line of text, which reads "LOCK STATE - LOCKED". This indicates your bootloader is still locked. If it reads "LOCK STATE - UNLOCKED", your bootloader is unlocked.
To unlock the bootloader, you need some tools.
1. Android SDK (this is a custom version of the Android SDK that includes the recovery image and only contains the tools needed for fastboot: the guide will teach you how to use it, but if for some reason it doesn't work for you, you can download the Android SDK from Google.) - http://www.multiupload.com/OAGYXGQ20J
2. PDAnet (you don't actually need PDAnet, you only need the drivers it comes with) - http://pdanet.co/bin/PdaNetA302.exe
Now that you have the necessary tools, it's time to get down to business. Install PDAnet and extract the .zip with the Android SDK you downloaded into C:\ to make your life easier.
Press the Windows key (it's in the middle of Ctrl and Alt) and R at the same time. The Run window will pop up. Type "cmd" into the box (without quotes).
The Windows command prompt will appear.
In the command prompt, type "[COLOR="Cyan]cd C:\bootloader[/COLOR]". Afterwards, type in "[COLOR="Cyan"]fastboot devices[/COLOR]". Your device should be identified. Afterwards, type in "fastboot oem unlock". There will be a prompt on your phone. Select the first option. Your bootloader is unlocked!
After unlocking, turn off your phone and put it in bootloader mode again, by holding the power button and volume up at the same time. This time, type in "fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img". This installs ClockworkMod Recovery on your phone. You can access it by selecting RECOVERY in the bootloader menu.
Your phone now has an unlocked bootloader and a custom recovery image, which means you are now ready to flash custom ROMs.
If you don't want to install a custom ROM
That was a lot of work, wasn't it?
Click to expand...
Click to collapse
Installing custom ROMs!
To install a custom ROM, you need to download a custom ROM first. You can find a list of ROMs and kernels in the second post.
Before you install ANYTHING, I recommend you back up the stock ROM by accessing "Backup and Restore" and selecting "Backup". Don't be lazy, this is your lifeline in case you need to return your phone to Samsung!
After you download the ROM, place it on a folder in your internal storage. Turn off your phone, go into ClockworkMod Recovery (by accessing bootloader mode and selecting Recovery) and from there, go into "Mounts and Storage", format /system, /data, /cache and /boot. DO NOT FORMAT /sdcard!
Afterwards, go back to the main menu, select "Apply zip from sdcard" and choose the .zip file you want to install. Installing a kernel is just like installing a ROM, except you don't format any partitions.
Click to expand...
Click to collapse
Congratulations, you have a custom ROM on your Nexus S!
If you have any questions, feel free to post them below!
Also, press that Thanks button down there please I do appreciate it
Click to expand...
Click to collapse
Thanks go out to:
-> The CyanogenMod team!
-> Koush!
-> The XDA community!
Click to expand...
Click to collapse
-khartaras
I might need this later...
First Troll responding to this thread!
So, khartaras, you basically did the same for the x8, while back.
Good job...
Good post but please indicate the rooting guide is for windows as it will confuse mac users.
Sent from my Nexus S MV from the XDA Premium app.
Can I have unroot guide please??
Having been a member on this forum for years I must admit it has been incredible the wealth of information I've gained from it. I've had all sorts of phones/pdas and I'ved used this site to help me get the most out of it and to help m "tame" the device and stop rubbish from the vendors being installed on there when I don't want it.
A couple of years ago I got an HTC Desire. Great phone although limited memory. I was happy with it. Didn't bother to root it or anything. I then got a Motorola Xoom. Didn't bother rooting that either. I got myself an HTC Sensation now. I decided one day that I was going to unlock/root the thing to see if I could do it.
Somehow, I think I managed it. I haven't really noticed a difference but then I haven't put a custom rom on it. On all my old Windows mobiles I always had a custom rom.
Now, going back to the Xoom. It's an original Xoom. I bought it in May 2011. It is running Android 3.2 after Motorola sent out an update. All is good.
However, I would like to have ICS on it. This is where my problems begin. I've tried following so many different how-to's on how to do this unyet none so far have worked. So, either I'm completely stupid or, the guides are not easy to follow or the process (that is always touted as easy) is not very easy.
So I am asking for help. Here is what I understand are the steps that I need to acheive.
1. I need to unlock the device
2. I need to install a recovery image
3. I need to install ICS
Questions: I *think* I have done 1. How do I check? After what I believe is a convoluted process, I have installed the Android SDK. I have the drivers for the device on the [Windows 7 64bit] PC and I can see it listed when I type adb devices.
Why do I need to unlock the device? What does the act of unlocking it do? When I followed this:
http://forum.xda-developers.com/showthread.php?t=1242241
I got to step 3. I typed in the first command:
adb reboot bootloader
After much faffing around I found out from another site I needed USB Debugging enabled. Nobody told me this. No, it isn't obvious that I need this.
The boot screen appeared and gave a message at the top and then I typed in:
fastboot oem unlock
I followed the instructions on the screen. I unlocked the device. It took a while. When it rebooted I found I had to set the device back up again as if it was the first time I'd used it. "Great!" I am thinking, I've lost everything. Thankfully I backed up what I wanted so I am not bothered. Slowly the apps appeared to come back after it synched with Google. I'm assuming stuff gets backed up somewhere.
I typed:
fastboot reboot
It rebooted.I typed:
adb reboot bootloader
It rebooted into the bootloader. Now here is where things started to go off track. I typed the next command:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
I get this:
unknown partition 'recovery-Tiamat-R4c-100611-1150-cwm.img'
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img'
So what now?
I cannot believe the process to unlock and flash a rom is so unbelievably convoluted. I've read dozens of walkthroughs, how-to's and forums and each one seems to be very similar unyet there is always something different on there to what I get on my screen or something doesn't happen quite the same way.
Here is what I am trying to acheive:
I have Android 3.2 on my Xoom and I would like it to be ICS.
We'll assume that I am completely stupid and need serious handholding to get to ICS. Is there anyone that can help with these seemingly simple steps?
One thing I keep reading is about the recovery image file. Is this related to Cyanogenmod? I am assuming as it is called a recovery image file it helps you get back when things go wrong.
Thanks and much love to the person that takes up the reigns and helps me out here.
Hi!
If you are rooted already that's pretty easy. But if not, try using LordAIOTool to root (yea it's mine and I think it's worth a try). After you are rooted flash a new recovery - download from development section - after, rename the recovery to recovery.img and then use the following commands on adb, fastboot and this recovery folder (simultaneously)
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Then after keep clicking the vol- after 2s of your tablet appears on Motorola logo. Then keep cycling until appears Android Recovery then press vol+
You are on recovery now, just select install zip from sdcard...
Good luck
Sent from my MZ601 using XDA Premium HD app
If you wanted your xoom rom'd, then you could try wesamothman's guide: http://forum.xda-developers.com/showthread.php?t=1717402 It is great for beginners and the experienced alike.
This is for the wifi only xoom MZ604. There is another guide by him i believe for the MZ602
Do I need to flash a new rom to get root on my MZ604? What is the easiest way to just root the stock 4.0.4 firmware? I have no desire for a different rom. I just want to root it.
Hey there.
If you don't want to flash a custom ROM and only want to root it, try this:
1) unlock your bootloader.
2) thru ADB, flash a recovery image.
3) thru Recovery, flash superuser flashable zip: http://www.4shared.com/zip/g3yzbrIa/...?cau2=403tNull
I ran the first couple of steps to unlocking. That is as far as I have got. As I said, I have tried so many of these walkthroughs and not one of them has all the steps. They all make an assumption somewhere along the line.
For example: xxlordxx replied with:
"If you are rooted already that's pretty easy".
I'm not, that is the problem.
Again:
1. adb reboot bootloader
2. fastboot flash recovery recovery.img <---- This didn't work and gave me the error I pointed out earlier and that is where it all stopped. Noone explains what to do when it goes wrong.
Anything passed this stage is irrelevant until I can sort out the problem above.
yosterwp, you mentioned wesamothmans guide. I will try that one as it looks a bit more "dummies guide-like" and it is for my exact device which is the MZ604 wifi only. I hadn't seen this one as it was only posted a couple of days ago
Just so I know, can someone anser these questions? I'm sure they're very simple but I don't know.
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
2. Is unlocking the same as setting s-off?
3. If not, what is the difference?
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
5. What is Cyanogenmod and do I need it or is this another custom rom?
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Thanks for everything so far. I will let you know how I get on with wesamothmans guide.
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
wesamothman said:
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
Click to expand...
Click to collapse
You did
Much love!
Hi guys.
I posted a thread the other day asking for help with superoneclick, I have since taken on board the advice given, and scrapped the superoneclick route. Instead I followed this guide http://forum.xda-developers.com/showthread.php?t=1525100 , which was going really well, up to the point where I go into recovery, and try to install from sd card. I tried the method with the reaper v2.1, and now also with blind roms pacman rom, and neither show up when I go to install from the sd card. I downloaded the roms, and unzipped them in the sd card, not in a file, just into the card itself, they then show up, but only as "boot" and not as "boot.img" as I'm sure it should say, they also still say they are a "winzip file", which surely if they were unzipped, they wouldn't say this?
Seemingly everything else I did is working as it should, I have an unlocked bootloader, I have enabled adb and fastboot, it's just the putting the rom on the sd card and then locating it when I go into EXT4.
Can anyone please shed some light on to what I may be doing wrong?
4) Open the rom (.zip file) you downloaded in step 1 and put the ''boot.img'' file in ''C:\android-tools'' seems to be the part where it all goes wrong?
Thanks for now.
Geez, so many things done wrong.
I hope someone will have patience to explain all of them to you, I'll just tell you 2 things:
1) Guides assume that people can tell file names from file extensions, and know how to see both.
2) I highly suggest you leave your phone alone. You don't have enough knowledge to safely proceed, and definitely don't have enough knowledge to pull yourself out of trouble, which you'll eventually get into.
Jack_R1 said:
Geez, so many things done wrong.
I hope someone will have patience to explain all of them to you, I'll just tell you 2 things:
1) Guides assume that people can tell file names from file extensions, and know how to see both.
2) I highly suggest you leave your phone alone. You don't have enough knowledge to safely proceed, and definitely don't have enough knowledge to pull yourself out of trouble, which you'll eventually get into.
Click to expand...
Click to collapse
I appreciate any feedback or criticism, as long as the end result is me figuring out how to root my phone.
I THOUGHT I'd followed the guide pretty closely. I'm inexperienced,yes, buy so is everyone when they try doing something for the first time. I've been reading all I can to help give myself some much needed knowledge.
But guess I'm doing something not right, I'd very much appreciate someone being uber patient with me,and showing/telling me what it is I'm doing wrong.
Thank you.
What needs to be on the sd card is the zip file of the rom, not unzipped or anything. Then you can install the rom from recovery, assuming you did all the other steps right.
teadrinker said:
What needs to be on the sd card is the zip file of the rom, not unzipped or anything. Then you can install the rom from recovery, assuming you did all the other steps right.
Click to expand...
Click to collapse
He has unlocked bootloader, which means - telling him how to install it without explaining what to do after (flashing boot.img) is a great idea - if you want to get his phone not to boot anymore.
Jack_R1 said:
He has unlocked bootloader, which means - telling him how to install it without explaining what to do after (flashing boot.img) is a great idea - if you want to get his phone not to boot anymore.
Click to expand...
Click to collapse
^^^^ Which will be why my phone now wont go past the white screen displaying HTC.
But I can still boot into 4EXT recovery, but when I do the backup/restore, it does nothing, just comes back to 4ext, or if I reboot, the white htc screen.
As it will go into 4EXT, it's not bricked, I guess it cant find the stock rom in the system to restore back to.
Not sure where to go now....Ebay for a replacement perhaps :silly:
nixon. said:
^^^^ Which will be why my phone now wont go past the white screen displaying HTC.
But I can still boot into 4EXT recovery, but when I do the backup/restore, it does nothing, just comes back to 4ext, or if I reboot, the white htc screen.
As it will go into 4EXT, it's not bricked, I guess it cant find the stock rom in the system to restore back to.
Not sure where to go now....Ebay for a replacement perhaps :silly:
Click to expand...
Click to collapse
Sounds like if your tire goes flat to trash the whole car for parts lol
Jack_R1 said:
He has unlocked bootloader, which means - telling him how to install it without explaining what to do after (flashing boot.img) is a great idea - if you want to get his phone not to boot anymore.
Click to expand...
Click to collapse
He was following a guide which included flashing boot.img, so I (perhaps over optimistic) assumed the right boot.img had been flashed.
---------- Post added at 07:12 PM ---------- Previous post was at 07:07 PM ----------
nixon. said:
^^^^ Which will be why my phone now wont go past the white screen displaying HTC.
But I can still boot into 4EXT recovery, but when I do the backup/restore, it does nothing, just comes back to 4ext, or if I reboot, the white htc screen.
As it will go into 4EXT, it's not bricked, I guess it cant find the stock rom in the system to restore back to.
Not sure where to go now....Ebay for a replacement perhaps :silly:
Click to expand...
Click to collapse
Yes your problem now is that you haven't flashed the boot.img from the rom you've installed.
deleted
nixon. said:
Hi guys.
I posted a thread the other day asking for help with superoneclick, I have since taken on board the advice given, and scrapped the superoneclick route. Instead I followed this guide http://forum.xda-developers.com/showthread.php?t=1525100 , which was going really well, up to the point where I go into recovery, and try to install from sd card. I tried the method with the reaper v2.1, and now also with blind roms pacman rom, and neither show up when I go to install from the sd card. I downloaded the roms, and unzipped them in the sd card, not in a file, just into the card itself, they then show up, but only as "boot" and not as "boot.img" as I'm sure it should say, they also still say they are a "winzip file", which surely if they were unzipped, they wouldn't say this?
Seemingly everything else I did is working as it should, I have an unlocked bootloader, I have enabled adb and fastboot, it's just the putting the rom on the sd card and then locating it when I go into EXT4.
Can anyone please shed some light on to what I may be doing wrong?
4) Open the rom (.zip file) you downloaded in step 1 and put the ''boot.img'' file in ''C:\android-tools'' seems to be the part where it all goes wrong?
Thanks for now.
Click to expand...
Click to collapse
In step 1 you copied the ROM zip file from your PC to your phone.
In step 4, you should open the PC zip file, not the file on the phone's sdcard. X(
That's the only thing you did incorrectly!
Sent from my Nexus 7
BillGoss said:
In step 1 you copied the ROM zip file from your PC to your phone.
In step 4, you should open the PC zip file, not the file on the phone's sdcard. X(
That's the only thing you did incorrectly!
Sent from my Nexus 7
Click to expand...
Click to collapse
^^^ thanked
Thank you for pointing out my mistake, now at least I realise what I was doing wrong, although now my phone is beyond my own repair, I shall have to see if I can send it off somewhere to get fixed.
Thanks again
nixon. said:
^^^ thanked
Thank you for pointing out my mistake, now at least I realise what I was doing wrong, although now my phone is beyond my own repair, I shall have to see if I can send it off somewhere to get fixed.
Thanks again
Click to expand...
Click to collapse
Why is it beyond your repair? Have you flashed the boot.img from the ROM?
Exactly, just flash the boot.img from the rom you flashed and it should work fine.
And if "flashing boot.img" sounds too complicated, try googling "fastboot flash boot boot.img", and going to Youtube for tutorials.
Your mistakes that I referenced earlier weren't only unpacking the ROM - this wasn't the problematic part - but when you did unpack the ROM and didn't understand anything from the boot.img file you saw, it meant that you have no idea about files and extensions, which usually means that it would be a bad idea to expect you to be able to freely use command prompt without detailed directions (and the guides always assume some level of knowledge - some more, some less). If you were to follow a better guide, the one that gets you S-OFF, it wouldn't matter - but since you've unlocked the bootloader and forced yourself to have to flash boot.img by fastboot, I didn't count on a happy ending should you proceed. I hate to be right in these cases.
You need to learn several things:
1. What are file extensions and what do they mean (mostly for yourself, but also for further understanding of the issue).
2. How to enable your OS to show file extensions to you, so you can see them and understand what file you're looking at.
3. How to open command prompt (you already did that - when you unlocked. now you need to do it to communicate with the phone in the same way).
4. How to use fastboot to flash boot.img (kernel) from command prompt.
Not too complicated, but it would have been better to learn that in your free time while having a functional phone, rather than in a rush to bring a non-working phone back to life.
Good luck.
Make sure phone is on 4.1.1 or 4.1.2, if not, put phone in usb debugging mode and open the RUU file and run it.
RUU downloads
make sure it matches your baseband though
download Hasoon2000 all in one/AIO for HTC One X
put phone in usb debugging and plugged in to android home screen
use chopper, step 2 on the list of options to the left, and make sure you get cid 1111111
use AIO to get into bootloader
select unlock bootloader in AIO
phone will reboot to factory android, skip ahead to android home page
hit finish or ok on AIO message
after success, get into usb debug and android homescreen and use AIO to flash TWRP, then boot into recovery and flash install to wipe TWRP
after CMD screens finish, reboot to phone, then use AIO to reboot into recovery
in TWRP select reboot into phone and itll prompt to flash SU and finish install to root
one booted to android file supersu app in app section, finish download thru playstore
open supersu app again and finish updates thru twrp, it will reboot into recovery, install zip, and reboot again to android
device is still cid111111
put soffbin file in adb location of of sdk, the platform tools folder usually
use AIO to flash one x zip file and follow prompts
after closing final cmd screen after failed 92, use AIO to boot up device in step 5
complete s-off with phone screen unlocked, close the cmd's as prompted
boot into bootloader, check for s-off
if s-off, boot into recovery
while in recovery;
enable usb mode
transfer CM and gapps files to device (or whatever rom and gapps)
wipe cache and dalvik and system
factory wipe
installCM and gapps
reboot
I'm hoping someone has links to the soffbin and one x zip files because they didnt work in AIO if I remember, a friend sent them to me.
enjoy
While you meant well, there might be a couple of problems with this.
1) This method will only work on certain firmware versions. You didn't properly note those firmware versions, you only noted Android versions which is irrelevant. A phone can be on 4.1.x without having the correct firmware version to use this method.
2) Using an RUU is a great way to update your device to the latest firmware, but there are instances where this will brick phones. For example, SuperCID + s-on + RUU = brick. That hasn't been noted in your post at all.
3) There are already explicit guides to unlocking/rooting for each firmware version here in our device forum. Creating another "guide" without all of the correct information is dangerous. It can also cause confusion due to the fact that there are different methods for different firmware versions.
My advice to anyone reading this who wants to root their device is this: work out which firmware/hboot you have and find the method already listed on this forum. There is a link in my signature to a resource thread, you'll find everything you'll ever need there.
To the OP: I'm not trying to cut you down, I hope you understand my reasons for this post after reading the information above.
Sent from my Evita
timmaaa said:
To the OP: I'm not trying to cut you down, I hope you understand my reasons for this post after reading the information above.
Click to expand...
Click to collapse
It all looks like constructive criticism to me, so hopefully it will be taken as such the the OP.
I agree, this isn't any more helpful than what is already out there, and not nearly comprehensive enough. It also needs a lot of cleanup, such as numbered steps and proper capitalization and punctuation. Some people might think this is nitpicky. But if you care enought to write it up, than do it in a way that is easy to read.
In his defense, this forum is crazy-messy.
I was a longtime ThunderBolt user, and on that forum there were clear paths to do what you needed to do. I will note that the ThunderBolt had only one version, and was only on Verizon.
My wife has an AT&T HOX. Not XL. She's on JB and her phone is slow and the battery lasts about 6 hours with moderate use. Nothing has been done to her phone to unlock, root, or S-off. But her phone is in such bad shape I'm thinking about stepping in.
Not trying to sound like a jerk, but all I care about is how I would go about taking a stock AT&T HOX through the rooting and romming process. I don't have Linux. I don't have a HTC OneXL. I'm not Canadian (Not that there's anything wrong with that, eh?).
Is there a CONSOLIDATED guide that will take me from stock to flashaholic? This thread attempts to answer this, and I applaud the OP. Hopefully we can work on perfecting this gem...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I don't think our forum is messy at all. There are different guides for a reason. Different firmware versions have different methods and therefore have separate threads. All you need to do is find out the firmware version the phone is on, and find the appropriate method. The concerns I raised are all valid and I stated them for a reason.
Sent from my Evita
First off, i'm sorry if the title is misleading and/or belong in the wrong part of this forum.
So, I'm late to the party, just got myself a Z5 E6653 and when I look for guides on how to obtain root they kind of out-of-date. So i'm here to make sure the path I choose to follow will be the correct one as I dont want to lose my TA partition. As far as I know, according to this guide to back up my TA partition I have to downgrade to Lollipop, but I found something interesting about backing up TA partition on Marshmallow using dirtycow method (sorry Nougat users).
So, the steps I'm proposed is, if my device is already on stock MM unrooted, locked bootloader.
1. Go here Sony cross-devices development and download file called backupTA_v2.zip this shouldnt makes us need to downgrade
2. Run the BackupTA.cmd file if you're on windows
3. There will be errors about dirtycow failed but the script automatically retry, me myself got screen-full of retries before the script actually backed up my TA partition and you'll be presented with .imgfile called TA_devicemodel_somenumbers_timestamp.img about 2MB in size (am i correct so far? this is why i want to make sure this will work)
4. Save your file in a very secure place.
That concludes the Backup TA part of rooting process am I on the right path so far?
To get unlocked bootloader according to this :
Given that you have downloaded flashtool and installed the drivers in the \drivers folder in flashtool installation
!!THIS WILL WIPE ALL DATA!!
1. Click the BLU button at top then open Sony developer website
2. Select device and follow instruction until you get a key
3. Paste the key to flashtool
4. THAT'S IT?
Now after this we can use fastboot command to flash kernel and the kernel includes recovery.
Are these steps correct so far?
I might as well add these here.
To get kernel and recovery up and running, I'll be taking androplus kernel for example, I'm assuming it works with stock ROM.
1. Get the kernel .zip here at Androplus homepage
2. And download latest TWRP recovery from androplus download page, at this time of writing it should be TWRP-3.0.2.2-e6653.img
3. Notice that it's in .zip format which we cannot use yet since we don't have custom recovery.
4. Open the zip file you just downloaded and you should see boot.img That's your brand new shining kernel, extract it outside put it in a folder along with your favorite fastboot.exe file
5. Go to fastboot, as far as I know you go to fastboot by turning off the device -> hold volume down then plug USB cable. (see note)
6. First, according to Androplus page, flash the kernel first using the command
Code:
fastboot flash boot boot.img
7. Then the recovery
Code:
fastboot flash recovery TWRP-3.0.2.2-E6653.img
8. Reboot by unplugging the USB cable
Note: some interesting thing I found while trying to enter fastboot or flashmode that it might not work if your USB port is powered How to tell if your port is powered? I'm not sure. You will have to change port and hope for the best ^_^
Yes. Explained many times. Not hard to do.. 4-5 minutes then WHOLA!
sceryavuz said:
Yes. Explained many times. Not hard to do.. 4-5 minutes then WHOLA!
Click to expand...
Click to collapse
Ahaha, sorry. Those guides are "old" in android way of changing things very fast, and I haven't seen a guide which includes backup TA partition on marshmallow so I wasn't sure it'd work correctly. Now that I know it worked, I can proceed to unlock my bootloader.
Any tips or Kernel/Rom I should use for first time flash?
webslasher said:
Ahaha, sorry. Those guides are "old" in android way of changing things very fast, and I haven't seen a guide which includes backup TA partition on marshmallow so I wasn't sure it'd work correctly. Now that I know it worked, I can proceed to unlock my bootloader.
Any tips or Kernel/Rom I should use for first time flash?
Click to expand...
Click to collapse
LineageOS, CarbonROM, eXistenZ, SunKernel..
Dear both,
I was just doing quite the same, so it was nice to read the short summary. Honestly, I'm doing these "Flash ROM stuff" very rarely, so I'm not 100% confident how to bring back those DRM/TA. I recorded it - the device came with Android LP 5.11, so this was easy done by iovyroot.
Anyway, I have the TA-backup - so I'm also going to unlock the Boot Loader now. :good:
Good to know I spend a day on reading so many related stuff, and it could be done in 4-5 min
sceryavuz said:
LineageOS, CarbonROM, eXistenZ, SunKernel..
Click to expand...
Click to collapse
I will try Existenz as I want to keep it stock looking, thanks!
bosquarid said:
Dear both,
I was just doing quite the same, so it was nice to read the short summary. Honestly, I'm doing these "Flash ROM stuff" very rarely, so I'm not 100% confident how to bring back those DRM/TA. I recorded it - the device came with Android LP 5.11, so this was easy done by iovyroot.
Anyway, I have the TA-backup - so I'm also going to unlock the Boot Loader now. :good:
Good to know I spend a day on reading so many related stuff, and it could be done in 4-5 min
Click to expand...
Click to collapse
I'm glad to find someone that is going to go through these procedures too! I will also proceed to unlock my bootloader what rom and kernel do you plan to flash?
Hi, thanks for this. I just got the Z5 today so my first port of call was coming here and finding out how to root it. I previously had the Z2 and Z2 tablet which I rooted last year with the help of the members here, I hope the process for this isn't too different for this one. I think I forget more than I remember so the guide is helpful.