[International] The HTC One root thread

Last Updated:

  1. rfic

    rfic Member

    i'm using bulletproof-m7-2.1 kernel (http://forum.xda-developers.com/showthread.php?t=2233665) for my stock rom 4.1.2; since i need to remove the camera files inside the zip file, i re-zip whole package after delete the camera file -- is there any special setting i need to use for the zip file?

    really appreciate!

  2. scotty85

    scotty85 Guides Guide

    you shouldnt have to do anything special. that kernel definately should install with a recovery flash. only things i can think of,are that you have possibly disturbed some of the install files by deleteing the camera files,or that modifying the zip simply breaks the signiture.

    you can try toggling signiture verificaTION off,if there is such a setting,i cant remember off the top of my head. you could also try re-signing the file after you modify and rezip it. there are free signing utilities if you search.

    id also give it as shot using CW instead of twrp,if all else fails.

    you could also flash the kernel without modifiying it and see if it installs that way(make a nandroid first so you can get back to how you are)
  3. rfic

    rfic Member

    you are absolutely right!

    i just try to install original kernel, seems working!

    but i did turn off signature, so how i can re-zip the folder?
  4. scotty85

    scotty85 Guides Guide


    try googling "android file sign utility" or "android file sign app" or something to that affect. the one i have is from PPCGeeks and i think is called "android signer"

    you could also try it with cw instead of twrp.
    rfic likes this.
  5. HenryLuo

    HenryLuo Member

    I have TrickDroid 8.0, SuperSU and ClockworkMod's recovery. I do have couple of questions, where only one is more related to HTC One than another's.
    1) Is root (and SuperSU) ROM specific, do I need to re-root if I change ROM?
    2) I have tried to install ClockworkMod's touch recovery, but for some reason touch doesn't work. What should I do?
    3) If I install latest TWRP (, does it work correctly with RomManager that I'm also using?

    I'm newbie of what it comes to Android in general and I haven't understood this rooting / custom recovery / rom even that much. I unlocked bootloader, rooted and installed custom ROM couple of days ago but it was more like doing what was told rather than understanding..
  6. scotty85

    scotty85 Guides Guide

    hope that helps. other questions,feel free to ask :)
  7. HenryLuo

    HenryLuo Member

    Thank you scotty85 for your reply.

    For some reason, seems that my phone doesn't work with touch version of recoveries. I've tried Clockwork touch and TWRP 2.6 and neither one supported touch. I'm not sure though if I would need to update something more as well.

    I installed ViperRom using ClockWork recovery's non-touch version and found it quite difficult. I have tried using TWRP recoveries, but because touch doesn't work, there is nothing I've been able to do with it.

    Below is code how I flashed recovery, touch just doesn't work.

    Code (Text):
    2. Hopeinen:sdk-tools luosut$ ./fastboot flash recovery cwr_recovery.img
    3. sending 'recovery' (7270 KB)...
    4. OKAY [  1.110s]
    5. writing 'recovery'...
    6. OKAY [  0.781s]
    7. finished. total time: 1.892s
    8. Hopeinen:sdk-tools luosut$ ./fastboot reboot
    9. rebooting...
    11. finished. total time: 0.034s
    12. Hopeinen:sdk-tools luosut$  
    edit: Finally got it right. I found new version of recovery that has support for latest firmware, file was named as "recovery-clockwork-touch-". Now touch works :)
  8. scotty85

    scotty85 Guides Guide

    glad you are sorted. i just read that the touch panel firmware for 2.17.401.1 has new drivers that break the touch in custom recoveries and was just coming here to ask what firmware you are on,but looks like you beat me to the punch :D

    also thanks for sharing your solution :)

    where did you find the link for the new touch recovery?
  9. HenryLuo

    HenryLuo Member

    Can't remember where I found that exact file, but I just searched and found official thread with new file from here (xda-thread) and this is direct download link. File is not the same that I flashed earlier, but I just downloaded and flashed file that I linked and it works correctly.

    Now that I'm rooted, do I have to manually flash firmwares (where to find?) or do I get everything I need from ROM files?
  10. scotty85

    scotty85 Guides Guide

    hmmm,thats the same file that im currently running. it is newer than the one that you linked earlier,so maybe it is new touch panel compatible.

    at any rate,you will not be able to take OTA updates while running a custom recovery. the stock recovery and an OTA are how the non-rooted stock general public will get new firmware.

    roms will only contain software. they will replace your current boot and system images.

    when an OTA for your particular region/carrier happens,you will need to update firmware manually. while s on,the process is more complicated,as these firmware files are official,signed by htc,so youll have to relock the bootloader and flash them via the bootloader(more details on that later).

    an s on phone is still doing plenty of security checks. not the least of wich is "main version",and also an hboot version check,so you are NOT allowed to go backwards. only what youre running or newer. also being checked are signiture,carrier id(cid),model id(mid),and lock status(wether bootloader is locked or unlocked)

    as such,you can only install firmware that will go with your particular set of variables. for example,you cannot install european firmware on a t mobile branded phone,or t mobile firmware on an att phone,etc.,becasue the firmware package will fail the CID and MID tests.

    you also cannot go backwards. if you install new firmware and dont like it,too bad. youre stuck until a new package comes out. becasue of this,id recomend only installing firmware or running full ruus from "release keys",official builds. i.e., the build that is pushed out via an OTA.

    htcdev unlock is not lifting many of the security checks. pretty much it is just granting us access to boot,system,and recovery. it has limitations- you cannot change splash image,or any other partition,and the recovery partition is not allowed to write the boot image, so the rom flashing process is a bit trickier.

    if youre just going to run rooted stock roms,its possible to stay s-on without much aggrivation. however if you intend to flash alot of different roms,and like to tinker with things alot,id pretty strongly recomend to become s off.

    this makes updating firmware alot easier,not to mention you can go backwards if you want,you can flash other partitions(like splash image),recovery can now properly install the boot image,making rom flashing a bunch easier,plus you are now able to get rid of the telltale relocked watermark.

    i would not worry too much about firmware just yet... consider going s off before the exploits are patched,and just enjoy rom flashing and using your phone for now :)

    hope that helps :)

    edit: oops,forgot your other question. if youre running a stock build,you can collect your own firmware files. when an OTA hits,let the phone download it. you will find a .zip file in your downloads folder that the phone would use to update. remove this zip from the downloads folder(remember your custom recovery cannot install it) and put it somewhere safe on your PC. using a utility such as 7 zip you can extract it and get to the "firmware" zipfile inside.

    aside from that,firmware files can be found over on xda,in threads such as this one.

    you can also find the entire OTA package here: http://androidfiles.org/ruu/?developer=M7 and here: http://shipped-roms.com/index.php?category=android&model=HTC One
    HenryLuo likes this.
  11. HenryLuo

    HenryLuo Member

    I noticed that in clockwork recovery there is possibility to format /data and another option to /data and /data/media. Does this mean that when doing full wipe, I can format everything else except that /data and /data/media and keep my virtual sd content?
  12. scotty85

    scotty85 Guides Guide

    all you typically need to do is "wipe data/factory reset" in order to flash a new rom,and it will affectively wipe every thing that you need. its a good idea to also wipe cache,and dalvik cache for good measure.

    as long as you dont wipe or format sdcard then you should be fine :) however i have found some things to wipe the internal sd that havent on other phones(like running an ruu) so its a good idea to back up the internal sd periodically,or prior to doing anything that could potentially have the unexpected result of wiping it,if you have things on it that you dont want to lose.
    HenryLuo likes this.
  13. clsA

    clsA Well-Known Member

    in android 4.1.2 /data/media is the internal sdcard
    so formating /data or /data/media is not recommended unless you really want a complete wipe (backup sdcard to pc first).
    In 4.2.2 sdcard has moved to /data/media/0
    if you update to 4.2.2 your pc will not see whats in /data/media.
    HenryLuo and scotty85 like this.
  14. HenryLuo

    HenryLuo Member

    Thanks guys. I was asking this only because when I unlocked, rooted, flashed custom recovery, I managed to clear my SD card as well (I wasn't paying attention enough, because I was watching tv show AND having like seventh glass of wine when I decided to start tweaking)
    No worries though, because only pictures were important and they were uploaded to Dropbox before. Now I was asking this, because I have backed up my ROM using Clockwork Recovery and I have took backups using Titanium Backups and even though I did download them to computer, I wish they wouldn't be deleted from virtual SD.

    As there were options to format
    - /data/
    -/data/ and /data/media
    I guess that formatting only /data/ does some sort of "delete everything except /data/media"

    Edit: I re-installed TrickDroid to get different setup and noticed that it asked if I wanted to full wipe or not. I chose not to, but if I was about to install different ROM situation was different:
    Question: Should I always format different mounts (everything else but "/data and /data/media") BEFORE installing ROM and in install process format nothing?
    scotty85 likes this.
  15. Hadron

    Hadron Well-Known Member Contributor

    Well that gave me a few nasty moments!

    I'd decided to stay on temp recovery until the update arrived. So it arrives today, I take a nandroid, then by mistake install it before copying the update file (as I'd intended to - just pressed the button in a thoughtless moment). Installs fine, all seems to work but of course I'm not rooted. OK, will fastboot boot recovery.img, take a backup of the unrooted 4.2.2 ROM, then root....

    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.
    scotty85 likes this.
  16. scotty85

    scotty85 Guides Guide

    thanks hadron,great info. thats an interesting bit of info with the temp recovery. cant wait to find out more about that... if that was a fluke that it wouldnt boot,or a new "feature" of hboot 1.54

    if someone else has captured the OTA,youre not neccesarily stuck on the OTA situation. firmware.zip inside the OTA zip will have a matching stock recovery inside,so being s off,you can easily pull that and re-install it if you get a notion :)

    good advice on s off prior to OTA. folks need to understand that exploits are blocked,and they need to take advantage of them while they work. also once s off,hold onto it! it wont affect normal operations of a 100% stock phone,there is never a reason to s on unless you have to for legitimate warranty purposes. never think "well ill just s off later" or "ill s on to take the OTA then s off again". you may find yourself stuck :eek:
    Hadron likes this.
  17. Hadron

    Hadron Well-Known Member Contributor

    It wasn't a fluke - I've seen it confirmed over at XDA. :(

    Between that and revone's incompatibility with 1.54 (from reports on XDA you can relock while running 1.54 but not unlock again!) I decided that 1.54 was taking away too many of my options. Plus, what's the advantage of a newer hboot anyway? So I've downgraded my hboot back to 1.44, and just confirmed that fastboot boot recovery.img works again.

    Note for anyone reading this who thinks that means there's a work-around: you have to be S-Off already in order to downgrade hboot.
    scotty85 likes this.
  18. scotty85

    scotty85 Guides Guide

    wow! i assume you mean the s-on crowd cant re-unlock? even with a new token? :eek:

    i assume the s-off crowd is still able to change the lock flag?

    i tend to always run the newest hboots,along with the newest firmware. ive learned the hard way mix-and matching stuff doesnt always work out. but it would irritate me not to be able to fastboot boot stuff :mad:

    lack of a real t mobile ruu has kept me from venturing too far from my stock firmware. its really annoying me,as id love to flash european firmwar,change my mid,and get euro updates :cool:

    thanks again for the info,my good sir. :)
  19. Hadron

    Hadron Well-Known Member Contributor

    I think the S-On crowd will be fine with HTCDev, though I did spot some discussion of new tokens.

    What I meant was that the S-Off crowd are not able to change the lock flag in both directions, at least not using revone. Couple of people at XDA tried it, and while able to lock they could not unlock: see this post and the one below it, for example. Of course if you are S-Off you can just change the hboot, but that was the point where I decided I'd feel happier running a hboot where the tools worked.
    scotty85 likes this.
  20. GalaxyNexus

    GalaxyNexus Well-Known Member

    What about the Google edition?
  21. scotty85

    scotty85 Guides Guide

    how to root? just the same as the guide:
    -install recovery
    -flash superuser

    as long as its a gsm m7_u or m7_ul,use the standard gsm recovery :)
  22. craftycarper

    craftycarper Well-Known Member

    I went back to stock (via Supercid and flashing RUU, then changing cid to one of the ones that the new OTA updates were available on last week)

    So am now on Hboot 1.54, S-Off (Revone) locked bootloader and unrooted.

    Is it just a case of downgrading firmware again to 1.44 and then i can revone again to unlock bootloader again?
  23. scotty85

    scotty85 Guides Guide

    did the OTA turn you to locked? :eek:

    what ruu did you run? did you change your mid as well?

    on to your quesstion :)

    have you tried the zip files to change the lock status flag? http://androidforums.com/internatio...t/732395-how-reset-your-lock-status-flag.html

    try flashing the query,then unlock zips with CW recovery(they dont seem to work with twrp). as long as the new hboot hasnt introduced some sort of write protection on mmcblk0p3 :)eek:) then the zips should work. or you could manually hex edit p3.

    failing that,yes you can simply swap back to hboot 1.44. unlock it with revone,or the zip files, then upgrade back and it should stay unlocked. if not,hadron has discovered there does not seem to be any consequenses to simply staying on 1.44.

    failing all that... you could do it the old fashioned way. with a new unlock_code.bin :p
  24. Hadron

    Hadron Well-Known Member Contributor

    The OTA did not relock my bootloader.
    scotty85 likes this.
  25. craftycarper

    craftycarper Well-Known Member

    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.

Share This Page