Related
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)
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
By the title, you can assume the situation is not very pretty and this poor individual needs some help. You would be correct in your assessment. This was me yesterday, freaking out after the new OTA update crippled my device and made me fear the worst (bricking). As a new Rom developer/flasher, I certainly worry about bricking my device, but have luckily not…yet. I certainly won’t deny the amount of tinkering that I do with my phone and flashing custom Roms, which might have assisted in my near meltdown, however, I thought it may be a good idea to share this experience (issue + solution) with the rest of the community, to hopefully save someone long periods of stress and research.
Note: I am only assuming the OTA is what caused the problem, but this could be incorrect, feel free to correct me.
Key Factors:
Custom Recovery: TWRP
Custom Rom (at the time of meltdown): Google Play Edition
Device: Verizon HTC One m8
OTA update ran.
Decided I wanted to go back to something closer to Sense and noticed that the ViperOne rom was getting some awesome reviews.
Downloaded Rom
Attempted to go into Recovery, but was greeted by the following error message:
HBoot
Model ID incorrect
Update failed
Press power to reboot
Downloaded Flashify and was able to get into recovery.
I knew I would need to deal with this error eventually, but thought maybe flashing the new Rom would assist in that area.
Flashed ViperOne rom, flash failed.
I swiped to unlock and the phone rebooted…
Then the real fun began.
My phone would boot to HTC logo with the read development disclaimer at the bottom:
“This build is for development purposes only. Do not distribute outside of HTC without HTC’s written permission. Failure to comply may lead to legal action.”
I freaked out for a bit, researched a ton and finally began to put the bits and pieces together:
At this screen it is possible to reboot, but then you will just boot into Hboot error, so pretty pointless (from what I know, feel free to chime in If you know of a way to get into recovery/fastboot from here).
I downloaded the latest version of TWRP
While on the HTC One screen, I plugged my phone into the computer and entered: adb devices.
At first, the command yielded no results, but after about 3 minutes, the device was recognized, but offline.
After 4 minutes, the device was recognize and looked to be available.
I then issued the following command:
Adb reboot bootloader
Success! This booted me into the fastboot usb method, which gave me a huge glimpse of hope.
Next, I ran the command to reflash the custom recovery:
Fastboot flash recovery [insert recovery file name here].
I received a successful message flash, however, after a reboot, I experienced the same problem as before.
I attempted to boot into recovery from the menu UI, but the option was not available. The journey continues:
I attempted the steps outlined above and then flashed the TWRP recovery image to boot instead of as recovery:
Fastboot flash boot [insert recovery file name here].
reboot-bootloader
This time, I was able to select “Recovery”, and booted into TWRP.
I then installed the GPE Rom again.
After the GPE rom installed, I rebooted into TWRP and checked to see if my restores were available, and luckily enough they were still in the same place (phew!).
This little article will hopefully help someone, as all the information I found for this issue was scattered throughout the web and I was luckily able to piece it together for my specific issue.
Ultimately, typing the ADB and Fastboot by themselves and reading through the commands in the CMD prompt, helped me figure out the commands needed to be successful in my endevours.
This would have been deeply helpful for me a week and a half ago. I actually bricked my device during the process of S-Off and unlocking the bootloader, after which, my device wouldn't be recognized on my computer (I missed a step in the process). Luckily for me, Verizon gave me an exchange, even though the phone was rooted and the only screen that'd boot up was TWRP. Apparently since I was in the 14-day return window, rooting or unlocking your device doesn't disqualify you from doing an exchange.
The first ROM I flashed after getting the new device and unlocking it was the same Google Play Edition. I had some issues getting in to recovery. I reflashed TWRP and have been fine ever since. I'm thinking it may be a bug in that ROM that causes devices to lose discoverability or for recovery to fail.
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.
Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.
blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.
I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.
@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!