I want to root my phone and install the ATT & Telus Elegancia rom. I just want to go over the steps I plan on doing and hopefully create a guide for those who are new to this phone and would like to flash ROMs successfully.
Here are the steps I plan to take. I just want to make sure I won't brick my phone. Also in the case that I do brick the phone, will the RUU RUU_EVITARE_UL_JB_45_Cingular_US_1.15.502.9_Radio_1.09.55.17_18.20.95.55L_release_290329_signed.exe work for this phone?
Using hasoon2000's HTC One X+ All-In-One Toolkit V1.1
1. Install HTC Drivers
2. Enable USB Debugging (Setting>Applications>USB Debugging.
3. Unlock bootloader by
-. Register at HTC DEV
-. Get token ID
-. Submit token ID
-. Get unlock_code.bin
-. Place in data folder of the toolkit
-. Unlock bootloader.
4. Wait for phone to reboot and put back in usb debugging
5. Flash ATT TWRP Recovery
8. Close the tool kit
9. Place Elegancia_ATT_2.1.0.zip on SD
10. Extract Kernel_Flasher_ATT_2.1.0.rar
11. Click installboot.img to flash the kernel
12. Boot into recovery
13. Wipe cache?
14. Flash Rom
Once you unlock and have recovery installed you are good 2 go. Follow Rom install instructions. No neet to permaroot, that was before we had custom roms, or if someone just wants their stock rom rooted. The custom rom you install will be rooted already. So Unlock, Install Recovery, Flash Kernel, Flash rom. Yes that is the correct ruu.
nugzo said:
Once you unlock and have recovery installed you are good 2 go. Follow Rom install instructions. No neet to permaroot, that was before we had custom roms, or if someone just wants their stock rom rooted. The custom rom you install will be rooted already. So Unlock, Install Recovery, Flash Kernel, Flash rom. Yes that is the correct ruu.
Click to expand...
Click to collapse
Sweet thank you!
Where do I find the kernel flasher?
Sent from my HTC One X+ using xda premium
In hasoon2000's toolkit
Sent from my HTC One X+ using xda app-developers app
guys whats the difference between att one x+ and international? why are there two recoveries?
i thought only original one X was different (snapdragon vs tegra...)
-=knop=- said:
guys whats the difference between att one x+ and international? why are there two recoveries?
i thought only original one X was different (snapdragon vs tegra...)
Click to expand...
Click to collapse
US version has LTE, international doesn't. The devices are just different enough to require two different sets of ROMs
Sent from my HTC One X+
Thunder350 said:
US version has LTE, international doesn't. The devices are just different enough to require two different sets of ROMs
Sent from my HTC One X+
Click to expand...
Click to collapse
Hey guy. Newbie question here. I want to root my device so I can do Google Talk video chat over LTE instead of WiFi. I can follow all the instructions, just wondering if that will wipe my phone completely?
Unlocking your bootloader, which is necessary in order to root, will indeed completely wipe your phone.
So the short answer is yes, it will completely wipe your phone.
Related
Apologies in advance but a bit of a newbie question......
I am the recent new owner of an HTC One X+ on the UK Vodafone network and am keen to get Andorid Revolution HD 6.2 running on it rather than the stock setup.
My system as it stands is as follows:-
Android version: 4.1.1
HTC Sense version: 4+
Software number: 1.14.161.18
Kernel version: 3.1.10-g262c6aa
HBOOT: 1.30.0000
CID (Via CID Getter): VODAP001
I have unlocked the bootloader (S-ON) via htcdev.com and gained SuperSU status and flashed TWRP International thanks to hasoon2000's excellent All-In-One Toolkit v2.1 (http://forum.xda-developers.com/showthread.php?t=1994961) and am now a little worried about taking the next step I guess!
I have the ARHD 6.2 rar file downloaded, the flash_boot_6.x_0.1.rar to flash boot.img and I have also downloaded the firmware (1.17.401.1.zip) as per the requirements according to mike1986. from here (http://forum.xda-developers.com/showthread.php?t=1995685).
My plan is to use hasoon2000's Toolkit to flash the boot.img, run the wipe command via TWRP (do I also need to upgrade the firmware using the 1.17.401.1.zip via TWRP - and how do I go about that with no writeable SD card) and then ADB sideload the Android Revolution HD 6.2 ROM but I am hanging fire on this process until I can get a little reassurance that this is the correct approach and will work, I think it's the virtual SD card and the fact I cannot actually have the files sat on an SD card that is making me a little apprehensive.
I hope I'm on the right lines because I was very happy with my Desire HD with Android Revolution HD on it prior to my upgrade and am looking forward to getting back to using the most popular ROM on my new phone!
Any help would be muchly appreciated......and please tell me if any of the above is likely to cause me problems!!
you can not use the firmware zip from mike1986.
you have a Vodafone branded Phone. there are no Updates for hboot.
(Check the CIDs at the thread)
skdubg said:
you can not use the firmware zip from mike1986.
you have a Vodafone branded Phone. there are no Updates for hboot.
(Check the CIDs at the thread)
Click to expand...
Click to collapse
Thanks skdubg,
yeah i had looked at that and that was my main concern.
so since mike's rom requires hboot 1.35 i have to wait for vodafone to release a software update from hboot 1.30 to 1.35?
were this to happen would i then be in a position to flash a custom rom (provided the CID appeared on the list of course) or is the fact it's a branded phone a complete sticking point?
pablihno said:
Thanks skdubg,
yeah i had looked at that and that was my main concern.
so since mike's rom requires hboot 1.35 i have to wait for vodafone to release a software update from hboot 1.30 to 1.35?
were this to happen would i then be in a position to flash a custom rom (provided the CID appeared on the list of course) or is the fact it's a branded phone a complete sticking point?
Click to expand...
Click to collapse
As long as you have the latest hboot you can flash any custom rom. It's not your CID preventing it. Problem is vodaphone does not usually release RUU's and if you flash a custom rom and end up with glitches/errors because you have an older hboot. There is no way to return to stock (except a nandroid).
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
As long as you have the latest hboot you can flash any custom rom. It's not your CID preventing it. Problem is vodaphone does not usually release RUU's and if you flash a custom rom and end up with glitches/errors because you have an older hboot. There is no way to return to stock (except a nandroid).
Click to expand...
Click to collapse
Thanks for the explanation AndroHero, I was under the impression if things didn't match up entirely then there was a risk of bricking.
So my best plan of action would be:-
1. Create a full nandroid of my system as it stands from TWRP
2. Flash the boot.img relating to the custom rom
3. Sideload and flash the custom rom through the All-In-One Toolkit
4. See how I get on!
Either that or stick with stock I guess...
Yeah you shouldnt run into too many issues doing it that way. There is a million in one chance of bricking your phone flashing a rom with any hboot. Infact while S-On doing anything wont "brick" your phone. As long as you have a backup to return too. You'll be fine
You dont need to "sideload" the rom, just boot into android on your voda rom, connect to pc, and copy the rom .zip to the root of the device that appears.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
Yeah you shouldnt run into too many issues doing it that way. There is a million in one chance of bricking your phone flashing a rom with any hboot. Infact while S-On doing anything wont "brick" your phone. As long as you have a backup to return too. You'll be fine
You dont need to "sideload" the rom, just boot into android on your voda rom, connect to pc, and copy the rom .zip to the root of the device that appears.
Click to expand...
Click to collapse
Cool, well that makes me feel a bit more confident about going further, thanks.
I would usually take that route but with the "virtual sd" i seem to be having issues writing directly to the device through windows explorer despite the device appearing it tells me the "Device has either stopped responding or been disconnected" every time I attempt to copy straight to the internal storage - that's the only reason why I'm thinking I need to "sideload" the rom.zip
I recently bought a htc one x plus and as the person as i am, i quickly unlocked the bootloader, installed a custom recovery (ClockworkMod recovery) and kernel. But then i tried to flash a AOKP Jelly Bean 4.2.1 Custom ROM and after flashing it, it would just hang around the AOKP boot logo (a horse head with rotating rings around it). Then, without thinking, i relocked the bootloader (with a custom rom) to send it for warranty. Now, it would only go to the bootloader screen. After going through a few forums, i found out that this could be repaired by using the correct ruu for my device but they all say that i have to flash a stock recovery and boot.img before relocking the bootloader in order for the ruu to work. So my question is can i reunlock my bootloader to flash the stock recovery and boot.img without bricking the device and can flashing the correct ruu repair my phone. Please reply, i'm so desperate. The htc guys wanted me to pay $400 just to repair it and since i rooted the phone, warranty does not cover it.
Shaarven said:
I recently bought a htc one x plus and as the person as i am, i quickly unlocked the bootloader, installed a custom recovery (ClockworkMod recovery) and kernel. But then i tried to flash a AOKP Jelly Bean 4.2.1 Custom ROM and after flashing it, it would just hang around the AOKP boot logo (a horse head with rotating rings around it). Then, without thinking, i relocked the bootloader (with a custom rom) to send it for warranty. Now, it would only go to the bootloader screen. After going through a few forums, i found out that this could be repaired by using the correct ruu for my device but they all say that i have to flash a stock recovery and boot.img before relocking the bootloader in order for the ruu to work. So my question is can i reunlock my bootloader to flash the stock recovery and boot.img without bricking the device and can flashing the correct ruu repair my phone. Please reply, i'm so desperate. The htc guys wanted me to pay $400 just to repair it and since i rooted the phone, warranty does not cover it.
Click to expand...
Click to collapse
You can unlock the boot again if you kept the code you received when you did it the 1st time round. Once you have unlocked it you can then flash any Rom. Did you make a nand backup before installing the custom Rom? If you did you can reinstall the custom recovery and restore the phone to stock.
I currently run the viper 3.4.2 rom, you could also install this after installing the custom recovery.
Sent from my HTC One X using xda app-developers app
Hi Sharveen,
Please do youself a favor, and don't use the CWM Recovery, this Recovery is not adapted for this phone, I strongly suggest that you install TWRP Recovery, the latter is way more complete and rigorously tested on the HTC One X+.
TIP : Please read, read, read as much as you can before doing any changes to your phone, that can save you lots of problem.
First make sure your SDK tool (adb) is correctly installed and also the HTC's drivers. (There is a link for a tutorial in my signature.)
Download the correspondent recovery for your phone International OR AT&T/Telus (N.B. Links are available in the Sticky FAQ)
Flash the Recovery.
Clear Cache
Reboot in Recovery
DO A COMPLETE BACKUP OF YOUR ACTUAL ROM. BE SURE TO KEEP IT IN A SAFE PLACE
Install your correspondent version of any ROM.zip you want that is already on your storage. (Otherwise,Sideload a ROM to be able to flash one inRecovery)
Flash the boot.img of your desired ROM
Clear Cache Again
Reboot
Should work
Thank you soo much for replying and no, i did not make a nandroid backup when i tried to flash the rom. So can flashing a correct ruu repair my phone and hopefully get it back to stock rom...
Is your SDK/ADB tool correctly installed?
Shaarven said:
Thank you soo much for replying and no, i did not make a nandroid backup when i tried to flash the rom. So can flashing a correct ruu repair my phone and hopefully get it back to stock rom...
Click to expand...
Click to collapse
Yess ruu will bribg back your phone to stock....it will restore everythings
What is your software version?
Sent from my HTC One X+ using Tapatalk 2
If you want to flash a RUU you need to install the original Recovery then flashing the correspondent RUU. Just let us know what is your preference, but as far as I am concern, your original backup wasn't made too bad, but you can still install a modded ROM.
This is gonna be your call for the continuity.
Shaarven said:
Thank you soo much for replying and no, i did not make a nandroid backup when i tried to flash the rom. So can flashing a correct ruu repair my phone and hopefully get it back to stock rom...
Click to expand...
Click to collapse
You could try searching the forum to see if someone has a nand backup for your phone. Only problem with ruu's is they haven't released the more up to date ones, so if your phone had the latest ota I doubt you will be able to use the ruu method. Personally I would use a custom Rom until you can find a nand for your phone.
Sent from my HTC One X using xda app-developers app
anyen said:
Yess ruu will bribg back your phone to stock....it will restore everythings
What is your software version?
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
My software version is 3.1204.168.32 and i did find an ruu in android files with the exact version (x.xxxx.168.xx).
Lucky Thirteen said:
If you want to flash a RUU you need to install the original Recovery then flashing the correspondent RUU. Just let us know what is your preference, but as far as I am concern, your original backup wasn't made too bad, but you can still install a modded ROM.
This is gonna be your call for the continuity.
Click to expand...
Click to collapse
The original recovery will be contained in the %temp% folder created by the ruu when opened but do i have to flash the boot.img which is also contained in the folder and also most of the forums says that you have to flash the boot.img after flashing the recovery while some says that you could relock the bootloader and flash the ruu after flashing the recovery only. So in my situation, do i have to flash the boot.img or not.
One X Plus Stock Rom (RUU)
Please help me, I couldn't find a RUU for my HTC One X +
It s on relocked mode now.
ENRC2B_U PVT SHIP-SON RL
HBOOT-1.35.0000
CPLD-NONE
MICROP-NONE
RADIO-3.1204.168.32
eMMC-bootmode:disabled
CPU-bootmode:disabled
HW Secure bOOT:enabled
nihat38 said:
Please help me, I couldn't find a RUU for my HTC One X +
It s on relocked mode now.
Click to expand...
Click to collapse
if you unlock your phone, you can only "relock" it, it will not become "locked" forever, even use RUU program
Unread Storage
after flashing ViperX+ 1.1.0 with sense4+ on my HTC OneX+, the storage can't be read at all.. what's wrong with my hox+?
I prefer not to format it via my PC, coz I haven't backup my data
xidia said:
after flashing ViperX+ 1.1.0 with sense4+ on my HTC OneX+, the storage can't be read at all.. what's wrong with my hox+?
I prefer not to format it via my PC, coz I haven't backup my data
Click to expand...
Click to collapse
I guess you have flashed older version then your radio and unlit file..
Try to download latest version of the ROM.
Sent from my HTC One X+ using XDA Premium 4 mobile app
[email protected] said:
I guess you have flashed older version then your radio and unlit file..
Try to download latest version of the ROM.
Sent from my HTC One X+ using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I thought I can just flash older ROM, without any radio and unlit file procurement.. *wanna experience once more the sexy older carousel home screen*
My HTC One M8 is currently Viper
My CID is 1111111.
Custom Recovery is TWRP
I tried to use the hansoon2000 program and followed the instructions according to this
http://theunlockr.com/2014/06/08/how-to-unroot-the-htc-one-m8-video/
The problem I am running to is that everytime I use the commands hansoon does not recognize my phone.
I have the proper drivers needed.
Also do I need to flash the CID in order to do this.
My main goal is to restore this M8 as if I took it out of the box.
AT&T HTC One M8
naimskyline91 said:
My HTC One M8 is currently Viper
My CID is 1111111.
Custom Recovery is TWRP
I tried to use the hansoon2000 program and followed the instructions according to this
http://theunlockr.com/2014/06/08/how-to-unroot-the-htc-one-m8-video/
The problem I am running to is that everytime I use the commands hansoon does not recognize my phone.
I have the proper drivers needed.
Also do I need to flash the CID in order to do this.
My main goal is to restore this M8 as if I took it out of the box.
AT&T HTC One M8
Click to expand...
Click to collapse
Most people here would never recommend using a toolkit. Are you just trying to return to stock? Just flash the ruu. Htc sync must be installed, fastboot off, usb debugging enabled.
http://forum.xda-developers.com/showthread.php?t=2757462
naimskyline91 said:
My HTC One M8 is currently Viper
My CID is 1111111.
Custom Recovery is TWRP
I tried to use the hansoon2000 program and followed the instructions according to this
http://theunlockr.com/2014/06/08/how-to-unroot-the-htc-one-m8-video/
The problem I am running to is that everytime I use the commands hansoon does not recognize my phone.
I have the proper drivers needed.
Also do I need to flash the CID in order to do this.
My main goal is to restore this M8 as if I took it out of the box.
AT&T HTC One M8
Click to expand...
Click to collapse
You will need to change your cid back to the at&t cid as well once you install the official ruu.
Sent from my HTC One_M8 using XDA Free mobile app
naimskyline91 said:
My main goal is to restore this M8 as if I took it out of the box.
AT&T HTC One M8
Click to expand...
Click to collapse
The question I would ask is "why"? AT&T doesn't require being stock to fulfill warranty. Only reason to return to "stock" is to sell/trade the phone.
Do you get any response if you type (command prompt on your computer with adb/fastboot set up):
fastboot devices
or
adb devices
If your computer doesn't return the phone model number, you have a fundamental USB connectivity issue you need to solve or else fastboot/adb/toolkits aren't going to work at all.
Also, this is the wrong forum section, and should be posted in Q&A. I've requested to mods to move the thread.
Moved to Q&A forum.
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Need to wait for hboot to be modded to have that removed
Wonders_Never_Cease said:
Need to wait for hboot to be modded to have that removed
Click to expand...
Click to collapse
Ah okay thanks. Wasnt sure if Hboot was universal or if it was by build.
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Wonders_Never_Cease said:
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Click to expand...
Click to collapse
I'm on build 2.22.401.5 running VenomOne rom, S-Off, rooted all the good stuff. Will your hboot mod work for mine?
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Wonders_Never_Cease said:
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Click to expand...
Click to collapse
OK and I can just install either one of those hboots over my existing one and it wont brick my phone or is this more to this?
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Wonders_Never_Cease said:
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Click to expand...
Click to collapse
Found it, thanks man. Gonna mess with it a little later.
CavyS said:
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Click to expand...
Click to collapse
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
thinkhope said:
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
Click to expand...
Click to collapse
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
CavyS said:
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
Click to expand...
Click to collapse
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
redpoint73 said:
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
Click to expand...
Click to collapse
It was just easier for me to fallow a set of instructions going step by step than jumping around just to avoid 1 easy step.
thinkhope said:
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah still works, you might of read that Firewater for some people doesnt work on 4.4.3. For me Firewater worked and I'm S-Off for some people it doesnt and you have to use Sunshine in that case.
thinkhope said:
So the toolkit still works??
Click to expand...
Click to collapse
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
redpoint73 said:
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
Click to expand...
Click to collapse
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Click to expand...
Click to collapse
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
redpoint73 said:
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
Click to expand...
Click to collapse
I definitely did have the evita. Had to alter the cid to make htc dev believe it was a different phone or something like that, if I remember correctly.
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Well, sounds easy enough. I will be attempting later tonight after work. Thanks for all of your help. If it's OK, mind if I PM you if something goes wrong?
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Click to expand...
Click to collapse
S-off is needed to flash radio, hboot, SIM unlock, and some other things. But not for root or to flash ROMs. Pretty much similar to how things were on the EVITA; with the exception that boot.img will flash automatically along with the ROM (not possible on most hboots on the EVITA, and had to be flashed manually with fastboot).
It sounds like you are already on the "official" 2.23 software (Android 4.4.3) by OTA? If so, you don't need to update firmware (radio, hboot, etc.) as the OTA already updated it. Otherwise, s-off is needed to flash the firmware manually; which is pretty much required for any 2.xx Sense based custom ROMs (otherwise there will be serious bugs like very long boot times, broken WiFi, Bluetooth). While s-off is not strictly needed to flash the ROM (it will flash correctly) things just won't run right if firmware is outdated. This is the only reason you would "need" to have s-off for flashing ROMs. AOSP and GPE ROMs won't suffer this issue.
But if you are already on the new OTA, this isn't an issue for flashing any ROM. You can verify by looking at the hboot version and baseband. If you are on hboot 3.18 and baseband 1.19; your firmware is up to date, and won't be an issue for running any ROMs.
thinkhope said:
mind if I PM you if something goes wrong?
Click to expand...
Click to collapse
I actually prefer you just posting to the forums. Either to an existing relevant thread, or start a new one if a relevant one does not already exist.
Couple reasons for this:
- Info given to you can help others reading the forums, and benefit the community as a whole instead of being hidden away in PM
- You can get help from more than just one user. I don't claim to even remotely know everything, and often its helpful to have more than one set of eyes on a problem (especially the tougher ones). And I might not even be online to help.
In particular for the 2nd point: my wife and I are going to be having a baby, with scheduled induction tomorrow (Sept. 5) unless it happens by itself sooner. So I won't be available to help you when that happens, anyway!
In any case, good luck!
http://www.androidauthority.com/community/threads/how-to-root-the-htc-one-m9-5-0-2-windows.18546/
I have not tried it yet, but on the site it says it works for the att variant... I'll try it tomorrow when I get mine...
Sent from my Nexus 5 using XDA Free mobile app
cables2590 said:
http://www.androidauthority.com/community/threads/how-to-root-the-htc-one-m9-5-0-2-windows.18546/
I have not tried it yet, but on the site it says it works for the att variant... I'll try it tomorrow when I get mine...
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Those are good instructions :good:.
Captain_Throwback said:
Those are good instructions :good:.
Click to expand...
Click to collapse
Hey Captain! Had to switch to AT&T for work so I'm here now. I want to root, but I'm sure there will be a bevy of updates in the near future, so I was wondering if you know if the stock AT&T M9 Recovery is available or even RUU?
I tried using those instructions, but there is no fastboot option in when I reboot using the Volume Down / Power button. Trying adb reboot fastboot just reboots the phone.
dratsablive said:
I tried using those instructions, but there is no fastboot option in when I reboot using the Volume Down / Power button. Trying adb reboot fastboot just reboots the phone.
Click to expand...
Click to collapse
Fastboot works in Download mode. That's where you need to be.
OK I can get to download mode with
adb reboot bootloader
fastboot devices returns my device serial number
But when I use fastboot oem get_identifier_token I get an error:
C:\fastboot>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.004s
When booted into bootloader I get this on the screen:
Software Status Official
LOCKED
S-ON
REBOOT
REBOOT TO BOOTLOADER
BOOT TO DOWNLOAD MODE
BOOT TO RECOVERY MODE
POWER DOWN
OK I was able to get the bootloader unlocked and rooted. My problem was trying to use Windows. When my device was connected, and I tried adb devices, it would list my device 3 times. Therefore I had problems using any adb commands, so I decided to use Fedora Linux.
First time I was using the wrong mode, bootloader, instead of download. Then when I did get to download, I was getting <Waiting for Device> I figured I probably needed to use sudo. Once I did that, the unlock process worked, and was able to install root afterwards.
Now what I need to know, is there a way to easily remove that AT&T tattoo on the back of the phone?
i don't think its possible to get root on the M9 at&t until we get S-OFF
basedboii said:
i don't think its possible to get root on the M9 at&t until we get S-OFF
Click to expand...
Click to collapse
Not true, I have an AT&T M9 and was able to root using the instructions.
I'm rooted and running LeeDroid rom from the international m9 thread.
basedboii said:
i don't think its possible to get root on the M9 at&t until we get S-OFF
Click to expand...
Click to collapse
I'm also AT&T and was able to root with instructions. Why would rooting need S-off??
Sent from my HTC One M9 using XDA Free mobile app
borillako said:
I'm also AT&T and was able to root with instructions. Why would rooting need S-off??
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't. We need s-off to change the CID and flash other ruu's, such as the dev edition ruu. I believe we need s-off to completely return to stock(removing the tampered flag).
lyall29 said:
I'm rooted and running LeeDroid rom from the international m9 thread.
Click to expand...
Click to collapse
Does everything work? I've unlocked the bootloader but have not installed twrp out of fear over messing something up and not being able to update / receive necessary future updates.
Sent from my HTC One M9 using Tapatalk
dantegl36 said:
Does everything work? I've unlocked the bootloader but have not installed twrp out of fear over messing something up and not being able to update / receive necessary future updates.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Yes everything appears to be working fine. I haven't had any problems in the week I've had the phone. As long as you flash the newest twrp beta(I'm using 2.8.6.3) and make a backup of your stock system before flashing any mods, then you should be able to return to stock without any problems.
Go here... http://forum.xda-developers.com/showthread.php?t=3066720 and read about specific device issues in post 2. Make sure that you read the entire OP (especially post 2) before asking questions in the thread.
Go here... http://forum.xda-developers.com/showthread.php?t=3066720 and read about specific device issues in post 2. Make sure that you read the entire OP (especially post 2) before asking questions in the thread.[/QUOTE]
Thanks for the link. I read through the first two posts and have a question. Why is it so important to receive OTA update? I thought after rooting, custom recovery,and installed custom rom, you just update (manually flash) the custom rom's new updates as they come out. And the versions of the custom rom is usually based on the new official OTA release anyways no?
mf1tym said:
Go here... http://forum.xda-developers.com/showthread.php?t=3066720 and read about specific device issues in post 2. Make sure that you read the entire OP (especially post 2) before asking questions in the thread.
Click to expand...
Click to collapse
Thanks for the link. I read through the first two posts and have a question. Why is it so important to receive OTA update? I thought after rooting, custom recovery,and installed custom rom, you just update (manually flash) the custom rom's new updates as they come out. And the versions of the custom rom is usually based on the new official OTA release anyways no?[/QUOTE]
I think the OTA file needs to be modified so it can be flashed by a custom recovery.