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)
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!
First of all I did check other forums, etc. before coming here. I also spent countless hours researching the rooting process. Here is my problem:
I'm attempting to root an HTC One x+ (AT&T) that I purchased on amazon. I'm using a Windows 8.1 system, and The latest Windroid tool (v2.3). With the tool I was able to unlock bootloader. The next step (flash a recovery) is where I believe I made my mistake. For my phone there was 2 choices (global and AT&T). I hence learned that my phone is evitare-ul, so I should have used the AT&T version, but I flashed it with the Global TWRP. I also made some errors in that I somehow wiped out the stock ROM (still don't know how that happened). I posted a question in the HTC One x+ forum, and was answered by LLoir (Thank you). The response was:
"You need TWRP for the EVITAREUL and then use the sideload function to put a rom on, also you need to manually flash the boot.img in fastboot. There's no MTP for TWRP Evitareul hence the reason for sideload."
Being new to "rooting" I wasn't sure what Llior was saying, ergo all the research. OK, so I found the TWRP-evitare-ul, but it WON'T FLASH! (Via Windroid). Windroid says it worked, but there is no recovery installed. I am however able to flash and remove the "global TWRP". Lloir answer also referenced 'NO MTP for TWRP evitareul", so I assume it is indeed the global TRWP I had flashed (it does has MTP wish I can enable or disable). When "enabled" my windows computer sees my phone, when "disabled" it doesn't see anything connected. I Need Help in Finding a way to Flash the "TWRP - evitareul" onto my phone.
A related issue is that after each Flash attempt when I attempt to reboot The screen on my phone changes from the "bootloader" screen to the "htc" screen And nothing more. Windroid is waiting and waiting and waiting. I end up pressing the power and volume down button combo to get back to bootloader. With the "global TWRP" I can boot to recovery, but I am in limbo when I try to flash with the "TWRP evitareul". It never installs! I'm guessing I have a booting issue.
Based on various forum articles I believe I'm to get the "Boot.img" to flash when I exe the rom file? I really rather just have the "zip" version I can use with Windroid. I'll need guidance and help there.
As it stands right now I have unlocked bootloader and apparently have the wrong TWRP installed. I have issues with my phone being recognized by my computer, and at various times my computer states there is a problem with windroid (when phone connected via usb). Is using a windows 8.1 system an issue. I can go to my old XP
In summary I need:
1) Find a way to flash the correct TWRP into my HTC One x+
2)be able to flash a ROM (MagioRom).
3)Flash the boot/img.
Guidance and help is appreciated. At least point me in the right direction. This is why I posted here. Please excuse my ignorance. Thanks
dpsrams said:
First of all I did check other forums, etc. before coming here. I also spent countless hours researching the rooting process. Here is my problem:
I'm attempting to root an HTC One x+ (AT&T) that I purchased on amazon. I'm using a Windows 8.1 system, and The latest Windroid tool (v2.3). With the tool I was able to unlock bootloader. The next step (flash a recovery) is where I believe I made my mistake. For my phone there was 2 choices (global and AT&T). I hence learned that my phone is evitare-ul, so I should have used the AT&T version, but I flashed it with the Global TWRP. I also made some errors in that I somehow wiped out the stock ROM (still don't know how that happened). I posted a question in the HTC One x+ forum, and was answered by LLoir (Thank you). The response was:
"You need TWRP for the EVITAREUL and then use the sideload function to put a rom on, also you need to manually flash the boot.img in fastboot. There's no MTP for TWRP Evitareul hence the reason for sideload."
Being new to "rooting" I wasn't sure what Llior was saying, ergo all the research. OK, so I found the TWRP-evitare-ul, but it WON'T FLASH! (Via Windroid). Windroid says it worked, but there is no recovery installed. I am however able to flash and remove the "global TWRP". Lloir answer also referenced 'NO MTP for TWRP evitareul", so I assume it is indeed the global TRWP I had flashed (it does has MTP wish I can enable or disable). When "enabled" my windows computer sees my phone, when "disabled" it doesn't see anything connected. I Need Help in Finding a way to Flash the "TWRP - evitareul" onto my phone.
A related issue is that after each Flash attempt when I attempt to reboot The screen on my phone changes from the "bootloader" screen to the "htc" screen And nothing more. Windroid is waiting and waiting and waiting. I end up pressing the power and volume down button combo to get back to bootloader. With the "global TWRP" I can boot to recovery, but I am in limbo when I try to flash with the "TWRP evitareul". It never installs! I'm guessing I have a booting issue.
Based on various forum articles I believe I'm to get the "Boot.img" to flash when I exe the rom file? I really rather just have the "zip" version I can use with Windroid. I'll need guidance and help there.
As it stands right now I have unlocked bootloader and apparently have the wrong TWRP installed. I have issues with my phone being recognized by my computer, and at various times my computer states there is a problem with windroid (when phone connected via usb). Is using a windows 8.1 system an issue. I can go to my old XP
In summary I need:
1) Find a way to flash the correct TWRP into my HTC One x+
2)be able to flash a ROM (MagioRom).
3)Flash the boot/img.
Guidance and help is appreciated. At least point me in the right direction. This is why I posted here. Please excuse my ignorance. Thanks
Click to expand...
Click to collapse
you should continue ask your question in http://forum.xda-developers.com/htc-one-x2/help/htc-one-x-stuck-twrp-v2-8-5-0-os-t3071068
also see HOX+ Tutorial for Unlocking, Rooting & installing a custom ROM [BEGINNERS FRIENDLY ]
No reply, thread will be closed.
It seems no matter how much this topic gets discussed, people still use old methods and they either fail, or they break something like WiFi, Mobile Data, infinite bootloop, or getting stuck on the boot logo... THIS DOESN'T HAVE TO HAPPEN and it IS repairable, usually without reflashing the entire image. The problem comes from using an old method, outdated SuperSU, or incorrect method. This guide will help you correct most issues, or help you to flash root correctly the FIRST time.
I have written rooting guides for multiple Moto device, and I have owned many Moto devices as well, so I have some idea what I am saying and I have tested these methods extensively, they work.
------------------------
This guide covers ALL Moto X 2015 models that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1575 or XT1572, the method is identical (untested on Chinese XT1570, but it should work). In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z with the appropriate TWRP image.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question, no offense, but do not PM me with a question because you think it is too stupid to ask in public (we all started as noobs), or because you want me to hold your hand and do it for you, I will politely tell you no and ask you to post in the thread.
If you are coming here because you followed an old guide where you used a special boot.img file and now you have no service (WiFi and/or mobile data) and you don't have a TWRP backup to restore first, well, the RIGHT way to fix it is to reflash the current stock firmware image and start over... why? Because the various "help" people give to have you flash the radio files that match the kernel (ie. boot image) that was patched for the old style root method, has now put you in a mismatched firmware environment and could potentially brick on the next OTA. If you are in this situation and don't know for to properly fix it... go to the FAQ section in post #3 below (WIP-incomplete).
If came are coming here to root the first time, or you just thought you could flash SuperSU and reboot and now stuck in either a bootloop or stuck on the boot logo... Your in luck, read on, because we can fix that in a jiffy!
tl;dr version for advanced users: Skip to "How to do it" section to root, or "Do the prep" section to fix a bad root.
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto X P/S, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See the official TWRP pages for clark here. I will NOT teach you how to use TWRP in this thread, if you are going to root you need to understand that your self, but if you get in a real bind I may knudge you in the right direction. I will tell you that there are two modes, flashed or booted, the later is much better if you plan to take an OTA later as long as you don't do something stupid like flash Xposed.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device, you can always fine the latest stable version here: https://download.chainfire.eu/supersu/ As of this posting update UPDATE-SuperSU-v2.82-20170528234214.zip (version 2.82) is the current stable version and it has been tested and verified to work.
NOTE: Unless otherwise stated, do not use a beta version for rooting Moto devices. SuperSU versions with even numbers are stable versions, while odd numbered versions are beta editions.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
5) Backup your device with TWRP to your SD card, even if you just unlocked and the phone is as blank as a printed page from a 1988 HP DeskJet printer with it's original cartridges still installed, backup... You will always have a good point to return to if the worst happens.
Do the prep:
Note that the hidden Do the prep section is ONLY for repairing a bad flash, SuperSU has been updated and as of version 2.79 the hidden section should no longer be needed for general purpose root on a working device, you just flash SuperSU. If you flashed an older version and are bootlooped, perform this section and continue.
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, when you have your backups and are ready to root, first go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press ENTER (there is no confirmation returned). You can verify this worked correctly by entering 'cat /data/.supersu' in the terminal and see if it returns "SYSTEMLESS=true", if not, you did it wrong, try the echo command again. Now press exit/back and press the HOME key.
After you have successfully entered the command in the TWRP Terminal you may continue
How to do it:
Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
Again, this is somewhat dated information and only applies to fixing a bootlooping device when improperly rooted.
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
NOTE: I no longer own this device, but will help where I can and will keep this thread open to assist users where ever possible, but I no longer have a device to test/verify things with.
Alternate Method #1
Some users have noted that the above method doesn't seem to work, we don't know why as it seems inconsistent but we can't pin it down specifically to user error, certain model number or build, or anything else, as it works 98% of the time...
But if the above method fails, the alternative is to download and copy to SD card or internal storage SuperSU 2.62-3 ßeta version available here and flash it through TWRP like normal.
Reserved - FAQ (oops, guess I already did that)
I'm so glad I found this thread! I've been procrastenating fixing my phone because of all the crappy methods. This one very easy to follow!
But still can't manage to get my WiFi working
I don't get it. But somehow my nandroid backup failed too, because it's only some 2.X MB big and I don't seem to recover anything....
So I guess I'll have to keep trying..
FYI:
1) Moto X Style 6.0
2) TWRP 3.0.2-0
3) Tried both 2.78 and 2.62. Currently running 2.62
4) SYSTEMLESS=true
Jorinde123 said:
I'm so glad I found this thread! I've been procrastenating fixing my phone because of all the crappy methods. This one very easy to follow!
But still can't manage to get my WiFi working
I don't get it. But somehow my nandroid backup failed too, because it's only some 2.X MB big and I don't seem to recover anything....
So I guess I'll have to keep trying..
FYI:
1) Moto X Style 6.0
2) TWRP 3.0.2-0
3) Tried both 2.78 and 2.62. Currently running 2.62
4) SYSTEMLESS=true
Click to expand...
Click to collapse
Find the latest rom image for the version you have installed, and flash the radios with fastboot.
acejavelin said:
Find the latest rom image for the version you have installed, and flash the radios with fastboot.
Click to expand...
Click to collapse
Thanks for your quick reply. Tried that, didn't work.. The ROM i'm currently running is MPH24.49-18 btw... I'm now trying it the hard way, just reverting everything step by step. But the first step (flashing gpt.bin) is already giving me the preflash error. This is going to be a lot harder than I thought and it's been too long since I've been flashing these things.
Used to flash my Moto Milestone and my Sony X10, can you imagine.
Jorinde123 said:
Thanks for your quick reply. Tried that, didn't work.. The ROM i'm currently running is MPH24.49-18 btw... I'm now trying it the hard way, just reverting everything step by step. But the first step (flashing gpt.bin) is already giving me the preflash error. This is going to be a lot harder than I thought and it's been too long since I've been flashing these things.
Used to flash my Moto Milestone and my Sony X10, can you imagine.
Click to expand...
Click to collapse
Because you are not on 49-18, if you were on the latest OTA for 6.0 you were on 49-18-4. Pre-flash validation failure confirms your using the wrong version. Look in my sig for the return to stock thread, there are links to current roms and discussion of the 'preflash validation error'.
Wasn't systemless method only intended for not altering the system partition in such way not to break compatibility with Android Pay and such apps that don't allow root?
Maybe I got it wrong when I first saw the appearance on the scene of systemless root. From what you are saying the auto detect it's supposed to detect with which method the device is compatible (not only detects if system was already modified? let's say like by TWRP).
I wasn't able to flash SuperSu newest stable versions either, all ended up stuck at boot, except for the 2.62 version (updatable later through playstore and binaries thorugh app via normal update). Honestly I haven't tried systemless as for me I through it was a waste (as said I through it wasn't meant for other purpose).
ATM I'm using CM's own root, but I will report as soon as I will try SU again. I never had problems with modem/wifi with SU, only that it didn't boot on newer stable builds.
Got the Moto X Pure a few days ago. It came with 6.0. This procedure works. Thank you!
ban.codrut said:
Wasn't systemless method only intended for not altering the system partition in such way not to break compatibility with Android Pay and such apps that don't allow root?
Maybe I got it wrong when I first saw the appearance on the scene of systemless root. From what you are saying the auto detect it's supposed to detect with which method the device is compatible (not only detects if system was already modified? let's say like by TWRP).
I wasn't able to flash SuperSu newest stable versions either, all ended up stuck at boot, except for the 2.62 version (updatable later through playstore and binaries thorugh app via normal update). Honestly I haven't tried systemless as for me I through it was a waste (as said I through it wasn't meant for other purpose).
ATM I'm using CM's own root, but I will report as soon as I will try SU again. I never had problems with modem/wifi with SU, only that it didn't boot on newer stable builds.
Click to expand...
Click to collapse
No, although that was one thing we thought we would gain (which we didn't), Systemless root is to get around Marshmallow security. Root is detected by SafetyNet API, and it detects pretty much any system modification, systemless or not
Currently Using TWRP 3.0.2.0 . Just unlocked bootloader and haven't done anything else . Recovery flash went well during the initial process of unlocking . Now Im trying to make a backup of the stock Rom , everytime I try to make one I keep getting failed at the end of the process ? Is this a known bug ? I have been doing google searches for the past hour and still unable to find anything to indicate anyone else is having this problem . Unless I didn't use the correct terms while searching . Any help would be appreciated
SouthernEvo said:
Currently Using TWRP 3.0.2.0 . Just unlocked bootloader and haven't done anything else . Recovery flash went well during the initial process of unlocking . Now Im trying to make a backup of the stock Rom , everytime I try to make one I keep getting failed at the end of the process ? Is this a known bug ? I have been doing google searches for the past hour and still unable to find anything to indicate anyone else is having this problem . Unless I didn't use the correct terms while searching . Any help would be appreciated
Click to expand...
Click to collapse
It is not a known issue... Where are you storing the backup, internal storage or SD card?
acejavelin said:
It is not a known issue... Where are you storing the backup, internal storage or SD card?
Click to expand...
Click to collapse
Was backing up to the SD Card . Been messing with it and now its working for some weird reason . I appreciate your quick response though
I used windroid to unlock the bootloader and install twrp( don't reboot system but rather boot into recovery to make twrp stick) , from there I just flashed supersu and I was good to go. Many methods out there but this worked for me.
Thank you so much for this guide. I have to say, as a new Motorola user coming from Samsung phones exclusively, this whole process made me feel like a real noob again.
I made the switch from iOS to Android back when the Galaxy S2 came out because I grew tired of the jailbreak cat and mouse games on the iPhones and iPads. Learning to root and flash ROMs on all my subsequent Samsung devices was fairly simple and very enjoyable. This Moto X Pure though was a real tasker for me. I honestly never knew about the extra steps you had to take to unlock, twrp and root this phone. I really wish manufactures would help us make this much easier.
Anyway, thank you again for your help. I'll be seeing y'all around the forums as a new MXPE user!
acejavelin said:
No, although that was one thing we thought we would gain (which we didn't), Systemless root is to get around Marshmallow security. Root is detected by SafetyNet API, and it detects pretty much any system modification, systemless or not
Click to expand...
Click to collapse
Thank you for clarifying a misconception I had on systemless root
(I intentioned to reply to you earlier, but the mad busy week made me forget about my intent )
I'm going to try right now the latest stable with systemless method (rather than flashing the older version) on a full wiped clean stock to see if it works. (Even tho I see lots of feedbacks here inspiring me to believe it would)
In what order?
acejavelin said:
It seems no matter how much this topic gets discussed, people still use old methods and they either fail, or they break something like WiFi, Mobile Data, infinite bootloop, or getting stuck on the boot logo... THIS DOESN'T HAVE TO HAPPEN and it IS repairable, usually without reflashing the entire image. The problem comes from using an old method, outdated SuperSU, or incorrect method. This guide will help you correct most issues, or help you to flash root correctly the FIRST time.
I have written rooting guides for multiple Moto device, and I have owned many Moto devices as well, so I have some idea what I am saying and I have tested these methods extensively, they work.
------------------------
This guide covers ALL Moto X 2015 models that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1575 or XT1572, the method is identical (untested on Chinese XT1570, but it should work). In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z with the appropriate TWRP image.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question, no offense, but do not PM me with a question because you think it is too stupid to ask in public (we all started as noobs), or because you want me to hold your hand and do it for you, I will politely tell you no and ask you to post in the thread.
If you are coming here because you followed an old guide where you used a special boot.img file and now you have no service (WiFi and/or mobile data) and you don't have a TWRP backup to restore first, well, the RIGHT way to fix it is to reflash the current stock firmware image and start over... why? Because the various "help" people give to have you flash the radio files that match the kernel (ie. boot image) that was patched for the old style root method, has now put you in a mismatched firmware environment and could potentially brick on the next OTA. If you are in this situation and don't know for to properly fix it... go to the FAQ section in post #3 below (WIP-incomplete).
If came are coming here to root the first time, or you just thought you could flash SuperSU and reboot and now stuck in either a bootloop or stuck on the boot logo... Your in luck, read on, because we can fix that in a jiffy!
tl;dr version for advanced users: Skip to "How to do it" section
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto X P/S, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See the official TWRP pages for clark here. I will NOT teach you how to use TWRP in this thread, if you are going to root you need to understand that your self, but if you get in a real bind I may knudge you in the right direction. I will tell you that there are two modes, flashed or booted, the later is much better if you plan to take an OTA later as long as you don't do something stupid like flash Xposed.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device, you can always fine the latest stable version here: https://download.chainfire.eu/supersu/ As of this posting SR4-SuperSU-v2.78-SR4-20161115184928.zip is the current stable version and it has been tested and verified to work.
NOTE: Unless otherwise stated, do not use a beta version for rooting Moto devices. SuperSU versions with even numbers are stable versions, while odd numbered versions are beta editions.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
5) Backup your device with TWRP to your SD card, even if you just unlocked and the phone is as blank as a printed page from a 1988 HP DeskJet printer with it's original cartridges still installed, backup... You will always have a good point to return to if the worst happens.
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. You can verify this worked correctly by entering 'cat /data/.supersu' and see if it returns "SYSTEMLESS=true", if not, you did it wrong, try the echo command again.
Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Click to expand...
Click to collapse
I really appreciate the help, but I have one question. Do I flash SuperSu and then type the command into the terminal, or do I type the terminal command first?
Thanks again for your help,
Matt
Iglooian said:
I really appreciate the help, but I have one question. Do I flash SuperSu and then type the command into the terminal, or do I type the terminal command first?
Thanks again for your help,
Matt
Click to expand...
Click to collapse
First, a little etiquette lesson, please don't quote long posts (especially the first post) for no reason, at the very least edit it down to only show the relevant parts so people don't have to scroll through a long meaningless quote.
And to answer your question, you enter the terminal command first, then install SuperSU, that is how it is ordered in the first post instructions. If you read the entire first post, it explains what the command does, and logic therefore lets you know it must be done first.
acejavelin said:
First, a little etiquette lesson, please don't quote long posts (especially the first post) for no reason, at the very least edit it down to only show the relevant parts so people don't have to scroll through a long meaningless quote.
And to answer your question, you enter the terminal command first, then install SuperSU, that is how it is ordered in the first post instructions. If you read the entire first post, it explains what the command does, and logic therefore lets you know it must be done first.
Click to expand...
Click to collapse
Actually, it was unclear what order I was supposed to do it in; we call that a clarifying question, but thanks anyway.
Iglooian said:
Actually, it was unclear what order I was supposed to do it in; we call that a clarifying question, but thanks anyway.
Click to expand...
Click to collapse
Fair enough... I will edit the "How to do it" section to make it more clear.