• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [International] The HTC One root thread

Crafty, as long as you are still S-Off it is that easy.

Download the stock, unmodified 1.44 hboot from this xda thread: http://forum.xda-developers.com/showthread.php?p=42379041 (assuming tapa hasn't mangled link - should be post 2 of sneakyghost's firmware thread). Follow instructions in the post to flash it. This is how I downgraded mine. With that hboot you can use revone to unlock.

I'm sure you can htcdev unlock anyway, but will have to backup & restore if you do that.

Of course you can try revone now, but people were reporting that it doesn't work.
 
craftycarper said:
Think it was flashing the RUU that locked bootloader.

I was just messing with the phone last week while bored, decided to Supercid, then flash an RUU, can't remember which because i have a new laptop and have downgraded from Win 8 to Win 7 on it so have no files left that i originally used, then changed cid to one of the ones that the OTA's were available on (before UK version was released), then back to Cid htc__001.

Didn't really notice that the bootloader had locked again until i booted to it to check the Hboot version after OTA'ing, so can't 100% say at which point the bootloader was locked again.

Just messing on stock at the moment, been busy at work etc, but it is only a matter of time before i obtain root again, just thought it would be easy option to downgrade firmware and unlock bootloader again using revone.
Click to expand...

the RUU shouldnt have locked your bootloader either. nothing should have,other than the revone tool,or flashing the locked zipfile. :confused:

if you havent changed your mid,sounds like you were allready on a compatible mid,so all you needed wwas the correct release firmware and CID.

ive run cm 10.1 on a couple devices,im gonna have to try 4.2 with sense 5 :D
 
Come to think of it, I may have relocked the bootloader myself prior to running the RUU......there has been a lot of Stella Artois consumed since last week, and what with sorting out the new laptop as well my brain is a bit frazzled!:p
 
craftycarper said:
Come to think of it, I may have relocked the bootloader myself prior to running the RUU......there has been a lot of Stella Artois consumed since last week, and what with sorting out the new laptop as well my brain is a bit frazzled!:p
Click to expand...

lol that will do it :p
 
Well, after the first couple of Stella's tonight i decided to downgrade the Hboot (thanks to Hadron for linking above :thumbup:)

Worked fine, but then when trying Revone to unlock Bootloader again it kept failing, tried to flash CWM recovery...fail, tried to root....fail.....in the end i reflashed a WWE_Europe RUU, updated to 1.29 OTA, unlocked Bootloader again via Revone, installed CWM, and rooted again and left it at that.......for now....mwahhhahahahhahahahhhaaaaaaaaaaaaaaaaa :smokingsomb:

I like messing with my phone....it makes me feel good.:D
 
craftycarper said:
I like messing with my phone....it makes me feel good.:D
Click to expand...

haha! me too :smokingsomb:

its driving me nuts not to flash some other RUUs. i did a few on my international one,since i had an ruu for the fimrware it had on it when i got it. lack of an official t mobile ruu to get back 100% has been keeping me stock(ish) on this one.

ive dumped all the partitions to make myself an unofficial,un-signed ruu.. just need to convince myself that that is good enuff for govt purposes :p
 
Hadron said:
Well that gave me a few nasty moments!

Except all that fastboot boot recovery.img does is lock up my bootloader so that I have to hard shut down. Try newest TWRP, same result. Try CWM touch, same result. Notice that the hboot version has updated, but I'm still unlocked and S-Off, so should be OK. But it is definitely not working.

Bite the bullet, fastboot flash TWRP 2.6 permanently, and yes, it works! Back to rooted and will not be doing any more OTAs :)

I'm writing this in case anyone else was using a temp recovery and finds that it stops working after the update, just to let you know that a proper install did work.

Also, if anyone is thinking of getting the OTA 4.2.2 update but is interested in S-Off, do not return to locked & S-On before running the update. To quote these prescient words:

The 4.2.2 update comes with a new bootloader (1.54 in my case), and revone cannot handle it (yet?). So if you are S-On and accept this update then you won't be able to S-Off using revone, at least for a while. I've not checked the other S-Off method. If you are S-Off when the update is applied, you will still be S-Off afterwards. So right now, if you think you might be interested in S-Off, do it before updating to 4.2.2.
Click to expand...

I have a similar problem.

I have yet to root this phone (I'm on Three UK carrier, so I assume the GSM method is correct) although the bootloader is unlocked via the HTCDev method.

I recently updated the phone to 4.2.2 and another small update afterwards.

I tried booting the temp image and got the same frozen bootloader issue as hadron above. Tempted to flash the permanent recovery but would like to take a backup of the original first if possible in case anything goes wrong, so I can flash it back.

Is this possible?

Apologies if the answer is found in this thread, I'm new to Android and have read this up and down a few times.
 
I can't think of a way, though Scotty knows the loopholes better than I do :)

With a custom recovery you could back up everything else, and if necessary you could fastboot flash a stock recovery image if you can't get a backup. I found a few examples available for download at xda-developers - can't guarantee they would be identical to the one on your phone, though I suspect the stock recovery doesn't vary much, and some UK users have made them work. So this would probably work, though I've not tried it.

The other way is to use an RUU, but that will do a factory reset in the process, and it would need to be a 4.2.2 RUU if you are S-On. In any case I've not found a Three UK RUU yet :(.

Of course, if the worry if the custom recovery not working, in that case you can just flash a different custom recovery (TWRP or ClockWorkMod).

So the chances of being stuck without a recovery at all are slim, but it would be good to have a way of returning to stock if needed. In the absence of an RUU I think you could probably do that by restoring a backup of everything else and then flashing a stock recovery, though the bootloader would still indicate that the phone had been modified. An RUU would be cleaner for that purpose.
 
I think I'll flash the TWRP recovery in a little while tonight.

No guts no glory!

I'll report back on how it went.
 
Success!

I am now rooted with TWRP!

This reminds of the time I first flashed a motherboard BIOS on my first gaming PC when I was a teenager...I was crapping myself over the horror stories people told about failed flashes and bricked motherboards haha.

Same feeling really, once you've done it once it's all good.

I think I may leave the custom ROM's alone for the meantime, (not sure Cyanogen for example will even work on this phone/carrier) and just enjoy my root access.

Ace guide, and thanks for the reply Hadron!
 
not much more to add,other than that the phones nowadays are doing such complex checks,that downgrading the hboot is not possible without s off(or really nasty method of purposely bricking it in a certain way,so that you can "recover" it to an older hboot with a jtag-like method)

if you can find an OTA package,from someone else with your same firmware,it will contain a recovery image that you can use to flash back to stock if needed. hopefully you have made an unrooted nandroid as well for back to stock purposes,and move it somewhere safe on your PC,just in case ;)

id be careful mix-n matching recoveries. different builds,and even different versions of the same build,typically have different md5s,so there are differences,however subtle they may be. :)
 
I'm having difficulties to select which ROM to use. I've used Trickdroid for few days and then, without any reason, switched to InsertCoin. I had no issues with neither of them, but I guess it's because this whole world is new to me, I'd like to try more and find best for me. I installed Google Edition of InsertCoin, but because I like HTC Zoe, it wasn't one for me. ViperRom is told to be good but when I installed it first time (first custom for me, actually), some apps wouldn't install but gave some error message about installation to SD card.
I know that people does have their own personal preferences and some like me doesn't know yet, but which ROM do you prefer and why? I'd like to find something to stick in with and maybe throw few bucks to developer..
 
HenryLuo said:
I'm having difficulties to select which ROM to use. I've used Trickdroid for few days and then, without any reason, switched to InsertCoin. I had no issues with neither of them, but I guess it's because this whole world is new to me, I'd like to try more and find best for me. I installed Google Edition of InsertCoin, but because I like HTC Zoe, it wasn't one for me. ViperRom is told to be good but when I installed it first time (first custom for me, actually), some apps wouldn't install but gave some error message about installation to SD card.
I know that people does have their own personal preferences and some like me doesn't know yet, but which ROM do you prefer and why? I'd like to find something to stick in with and maybe throw few bucks to developer..
Click to expand...

You sound like me a few years ago, you will try many roms when new to it, and you may still keep trying new roms when they come out, eventually you will find yourself going back to one that you previously liked and will stick with it.

It takes time....keep trying them , nothing wrong with that.

My choice is OrDroid.:)
 
The beauty of the nandroid backup is that it's no big deal to try a new ROM - if you don't like it, just use the nandroid to revert :)

I am holding off getting into the ROM game just now because I'm kinda busy and know how addictive it gets. But soon, my precious, soon.....
 
Yeah, I do have Nandroid of my Insercoin at the moment, been restoring it quite few times when new ROMs are been tested. Now I installed Android Revolution 12.01 and restored user apps with data from Titanium Backup + created manually all necessary accounts and system settings. I'll create Nandroid backup from this also when I'm sure that everything is working fine, let's try and see.
I've read elsewhere that it's not necessary to create full wipe if moving from one rom to another IF base is same. Is it so? Devs tell that you should do full wipe if you are coming from different ROM.
 
They will always recommend a full wipe to avoid any issues, may not be necessary, try without, if there are issues then try again with wipe.
 
Yeah, it depends on how similar the base is. If you have issues then you won't get support unless you did a wipe, and rightly so, since there's no way of telling what problems incompatible data might cause (I've seen some pretty odd and unlikely things in the time I've been here). So wipe first is always the clean and safe way.

Having said that, you can often get away with it if the bases are similar enough. Your call, but if there are any oddities and you didn't wipe first, do wipe and try again before you blame the ROM. :)
 
Now I have tested few ROMs and found that best for me is InsertCoin. ROM itself seems very good and developer seems to take it seriously and gives great support.
Only thing I'm missing is possibility to change for how long does led blink on notifications. I'd like to change it to blink until screen is opened (or until notification is checked from notification center), but so far this is the best. Gonna give developer few euros when I have my paypal set up.
 
glad youre having fun with your phone. also think its cool to donate to devs... ive donated to the creators of all the root tools ive used,as well as a few rom devs,and if i really like a play store app,i always buy the paid version,even if its not much different.

most folks work on their apps and roms in their spare time,so its great to support them. :cool:

hopefully he can work in the mod that youre after :)
 
When I did this with my EVO V 4G I was careless but I really want to know will our warranty end if we do S-off, what if down the road my htc one has battery issues or dead pixels. Also would this work with windows 8 due to driver issues.
 
nfs13epic said:
When I did this with my EVO V 4G I was careless but I really want to know will our warranty end if we do S-off, what if down the road my htc one has battery issues or dead pixels. Also would this work with windows 8 due to driver issues.
Click to expand...

you prolly have a beter chance of voiding your warranty by unlocking the bootloader and staying s-on. s-off lets you return the phone to 100% out of the box stock locked and s-on.

if you do not go s off,best you can do is relocked and anyone that cares to can check your hboot screen and see that youve tinkered with it ;)

not to mention s-off lets you do lots of other cool stuff :p
 
Hi guys! Just got my new sim-free HTC One 64gb and wanted to know if the methods still work on it if i follow the first page instructions?..
anyone know what the easiest method to root it?

sorry for sounding a knob.. its been a while since i rooted my previous phone, the htc desire.

thanks in advance!
 
The HTCDev method certainly will. Otherwise it depends on your software version.

As long as you've not updated to 4.2.2 all methods will. If you have then the S-Off tools won't work, and you'll probably have to permanently install recovery (the temp method seems not to work with the latest firmware).

The key is hboot version. Everything works with 1.44, only HTCDev with 1.54.
 
You must log in or register to reply here.
Back
Top Bottom