• 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

Ok, I'll try that. Before the flash I would plug it in and it would come up in Win Explorer as a drive on my computer. I could then transfer files that way. Not sure what getting adb working would do now for me. I did do the 7 tap on the build no. and check usb debugging already. I'll look for the "mount as a media device" switch. What if I go to recovery and then plug it into the computer so the OS isn't fighting it?

I found the mass storage thing. It's greyed out and says "insert media" so it's like it doesn't know to view the /sdcard/ folder as a separate drive. Nothing happens when I tap it. There are a few posts around about this and I wonder if it's a bug in CM.
 
Mike W said:
Ok, I'll try that. Before the flash I would plug it in and it would come up in Win Explorer as a drive on my computer. I could then transfer files that way. Not sure what getting adb working would do now for me. I did do the 7 tap on the build no. and check usb debugging already. I'll look for the "mount as a media device" switch. What if I go to recovery and then plug it into the computer so the OS isn't fighting it?

I found the mass storage thing. It's greyed out and says "insert media" so it's like it doesn't know to view the /sdcard/ folder as a separate drive. Nothing happens when I tap it. There are a few posts around about this and I wonder if it's a bug in CM.
Click to expand...

im not sure if youve found the right setting.. my nexus has the sd card greyed out in storage also. when i plug it in,i get an icon in the status bar that takes me to 2 settings when i tap it. one is to "mount as storage media" and the other is something else,to mount as an mtp device,i think. i have to uncheck the storage media setting,and check it again before the nexus will show up in windows explorer as a drive. ill try and get more definate menu settings later.

you definately will not be able to mount as a media device in recovery. youll have to be in the booted OS. it may be a cm bug,this is the first phone ive ever had ive not run cm on :eek:

you might try the GPE rom,wich is still nice AOSP,just with beats audio and missing some cm features ;) unless there are some particular cm features you cant live without,the GPE would give you a nice AOSP fix :cool:
 
I guess i want to mount as a media device. Not sure what you mean about "get adb working". Is there some functionality I could get with adb, like access to the phone's memory? I tapped the build number, enabled usb debugging and that pops up when I plug it in, but no access in win explorer. I did find the "mount as a media device" switch, but it's greyed and says insert card, suggesting it doesn't recognize the /sdcard/ folder as a drive. There's a few posts around about similar problems, making me think it's a CM 10.2 problem. There was some add on app made for a Galaxy or something running 10.1 that addressed the problem, but doubt that would help. What would happen if I plugged the phone in when in recovery? Or maybe there's a way to wirelessly transfer files to/from the phone on my home network?
 
Mike W said:
I guess i want to mount as a media device. Not sure what you mean about "get adb working". Is there some functionality I could get with adb, like access to the phone's memory? I tapped the build number, enabled usb debugging and that pops up when I plug it in, but no access in win explorer. I did find the "mount as a media device" switch, but it's greyed and says insert card, suggesting it doesn't recognize the /sdcard/ folder as a drive. There's a few posts around about similar problems, making me think it's a CM 10.2 problem. There was some add on app made for a Galaxy or something running 10.1 that addressed the problem, but doubt that would help. What would happen if I plugged the phone in when in recovery? Or maybe there's a way to wirelessly transfer files to/from the phone on my home network?
Click to expand...

By "get adb working" I simply meant getting the phone to comunicate with the pc via a command window so that adb commands can be used(adb devices,adb reboot bootloader,and so on). I thot that was what you were after when you first asked since you mentioned installing the drivers.

I understand what you want to do,I'm just not sure what else to tell you. Could be a bug with cm,that's why I suggested trying the GPE Rom.

If you want to stick with cm,search the development thread and see if others have come up with a workaround. If there's an app that will mount sd card,or let you transfer data wirelessly,that's where you'll find it. Only other thing I can think of is to use the comand window and adb commands to pull certain files from the phone to the pc. It would be somewhat clunky and cumbersome,but technically should work.
 
Ok I got stuck in flashing the temporary recovery img...Please help

Everything went fine till I flashed recovery. The green bar did come up on the phone but after that nothing. it froze and the buttons didn't even work. Had to force shut down...Any suggestions?

I didn't wait too long before forcing shut down. Was a bit scared to brink it. Maybe something like 40 sec to 1 min max....Is the rebooting slow? Should I try to wait longer?

Thanks guys

edit: Oh, I used the international one because I live in India...

Oh snap...Read the earlier posts and realized I have the hboot 1.55...So basically I can't temp root. Sorry for reposting the same problem!
Anyway if anyone finds a solution please let me know! Don't want to perm root till I get Kitkat :)
 
Technically it's the recovery which would be temp, not the rooting. ;)

TBH the only thing I can think of would be to get hold of the stock recovery for your phone model/software version, flash the custom recovery, root the phone, then flash the stock recovery back. What I don't know is how exactly the stock recovery should match for an OTA update to work. I guess you could extract a stock recovery from an RUU.

Or you could just root and flash a custom ROM based on 4.4 right now, and not wait for the OTA.
 
Caro332 said:
Ok I got stuck in flashing the temporary recovery img...Please help

Everything went fine till I flashed recovery. The green bar did come up on the phone but after that nothing. it froze and the buttons didn't even work. Had to force shut down...Any suggestions?

I didn't wait too long before forcing shut down. Was a bit scared to brink it. Maybe something like 40 sec to 1 min max....Is the rebooting slow? Should I try to wait longer?

Thanks guys

edit: Oh, I used the international one because I live in India...

Oh snap...Read the earlier posts and realized I have the hboot 1.55...So basically I can't temp root. Sorry for reposting the same problem!
Anyway if anyone finds a solution please let me know! Don't want to perm root till I get Kitkat :)
Click to expand...

Sorry for the confusion... I need to either add a warning to the OP or just remove the temp recovery section since newer hboots are no longer allowing it

As hadron said,best option now if you don't want to flash a roms is to install the recovery and then re-install the stock recovery. What is your build number? We can try and find your stock recovery.

The us developer edition has gotten its update,you definately could flash a custom rom and not have to wait for it from your carrier :cool:
 
Thanks guys. Not sure exactly where is it that the phone is getting stuck. I don't think I am rooted because when I try to install use SU, it tells me there is no SU binary.
Can I install recovery even if I'm not rooted?
 
But the problem is I'm not able to install recovey. Guess I might go for the perm rooting then...Let's see. Will ponder a little before I take a decision. Thanks!
 
Caro332 said:
But the problem is I'm not able to install recovey. Guess I might go for the perm rooting then...Let's see. Will ponder a little before I take a decision. Thanks!
Click to expand...

you are unable to launch a temporary recovery. you should be able to install the permanent recovery just fine.

are you having an error installing it? as we said,if you give us your build number,we can try and help you find a stock recovery to install afterwards so youre still stock.
 
Well now that I finally pulled the trigger and got the HTC One I'm looking at rooting it. I wanted to check and make sure the Superuser v1.25 file is the current file to use with 4.3.
 
biker57 said:
Well now that I finally pulled the trigger and got the HTC One I'm looking at rooting it. I wanted to check and make sure the Superuser v1.25 file is the current file to use with 4.3.
Click to expand...

there have been several updates since then. last i looked it was up to 1.80,the most current version will always be at the link provided. :)
 
scotty85 said:
you are unable to launch a temporary recovery. you should be able to install the permanent recovery just fine.

are you having an error installing it? as we said,if you give us your build number,we can try and help you find a stock recovery to install afterwards so youre still stock.
Click to expand...
sorry for not answering earlier. With all the holidays and all, got kind of busy.
When I try to flash recovery, it just freezes. That's it.

My build number is 3.63.707.4 CL271278
 
Caro332 said:
sorry for not answering earlier. With all the holidays and all, got kind of busy.
When I try to flash recovery, it just freezes. That's it.

My build number is 3.63.707.4 CL271278
Click to expand...

That's what Scotty suffered with hboot 1.55 (post #106 in this thread). But it seemed, to say the least, weird that that didn't work, and I've not seen widespread reports of this. I don't know whether Scotty learned more?

I suppose you could try rumrunner s-off (http://forum.xda-developers.com/showthread.php?t=2487888). If that runs then if you still can't flash recovery you would be able to change hboot.
 
Caro332 said:
sorry for not answering earlier. With all the holidays and all, got kind of busy.
When I try to flash recovery, it just freezes. That's it.

My build number is 3.63.707.4 CL271278
Click to expand...

as hadron said,i was unable to fastboot boot anything as well with hboot 1.55,and am still not on hboot 1.56. seems to be a new "feature" of the bootloader :rolleyes: im finding it true across the board,DNA is unable to fastboot boot anything on its newest update as well :mad: it is also true my first experiences with hboot 1.55,i was unable to fastboot flash as well,but i have been able to since then,may have been a wierd fluke on that particular hboot/day.

im afraid that your only option will be to follow the directions for a permanent recovery,and when youre done,you can just use that same process to flash the stock recovery back. let me know if you have the freezing with fastboot flash recovery recoveryname.img,and i will pack up a recovery for you to install in a slightly different manner.

you are in luck,that some kind soul has uploaded an OTA pacakge for your build,wich will contain your stock recovery(and other firmware). you can find the pacakge here: OTA M7 U JB43 SENSE55 MR HTC Asia WWE 3.63.707.4-2.24.707.3 Release - HTC1Guru

and it would be nice to thank mr crushalot here for his contributions and hosting an assortment of OTAs and RUUs in his thread here on android forums(http://androidforums.com/internatio...any-versions-rom-recovery-radio-get-otas.html)

im downloading your ota package currently. if you wish you can download it as well(its a hefty update at 706 MB) or you can just let me extract it and upload the recovery for you.

just holler if you have questions :)
 
Hey, I've got the AT&T HTC One and I'm on a Macbook Pro. Will I be able to use this guide to get root and possibly kit-kat?
Thanks
 
Hey guys. I'm a bit new to this so I'm not entirely sure if this is a dumb question, but I'm just wondering if this method will work for my Sprint htc one running 4.4.2 or are there newer versions of any files/different operations need since I'm running the most recent android version?
 
thefisch6 said:
Hey guys. I'm a bit new to this so I'm not entirely sure if this is a dumb question, but I'm just wondering if this method will work for my Sprint htc one running 4.4.2 or are there newer versions of any files/different operations need since I'm running the most recent android version?
Click to expand...

Yes the basics are the same but it's vital you get a recovery made only for Sprint Here >> Techerrata Downloads - Browsing m7wls

So unlock your bootloader at HTCDEV.com
flash the custom recovery
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
fastboot erase cache
fastboot reboot-bootloader

enter recovery and on exit choose yes to install Root

you now ready to backup your phone and install custom Rom's
 
Also, for the record, I can root and flash custom recovery before "backing up" my stock setup, right? Or is there a way I'm supposed to do that before flashing twrp?
 
You can use Helium to do an app/data backup before starting.

Unlocking the bootloader will wipe the phone, so I'd recommend backing up first (there is a red warning about this in the first post of the thread).
 
You must log in or register to reply here.
Back
Top Bottom