Use Rom Manager for best results when backing/restoring...
USB OTG Info:
USB OTG will show up as external_sd. If external_sd is not mounting, reboot recovery. You must enter recovery with usb already inserted.
Installation:
Inscrutions can be found here @ http://www.techgeekal.com/2013/03/1...ckworkmod-touch-recovery-v6-0-2-8-on-htc-one/(outdated)
Unlock bootloader at http://www.htcdev.com/bootloader/
Make sure fastboot is unchecked in power options and turn phone completely off
Boot into HBOOT then Fastboot
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
OR
Flash via Rom Manager(must have root already).
Video Tutorials:
How To Unlock The Bootloader EASIEST Method - https://www.youtube.com/watch?v=r0gzJdwCxX0
How To ROOT EASIEST METHOD - https://www.youtube.com/watch?v=S1KmsxO84UU
Downloads:
You can now flash in Rom Manager in rom if rooted
Classic - http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.3.2-m7tmo.img
OR
Touch - http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.3-m7tmo.img
PC USB Mass Storage:
You can't! http://teamw.in/DataMedia
Mirror for files http://d-h.st/users/flyhalf205/?fld_id=11322#files or http://www.clockworkmod.com/rommanager
Many thanks. Testing tomorrow morning.
Syn Ack said:
Many thanks. Testing tomorrow morning.
Click to expand...
Click to collapse
Thanks! I am assuming this works. ha :laugh:
This seems like an appropriate place to ask, with HTCDev unlock, how "unlocked" is the device currently? Like in terms of recoveries, kernels, radios, etc.? I ask here cuz I'm most curious about the functionality of CWM Recovery and how much time I'm gonna have to play around in it.
I saw koush state that its basically the status and simplicity of a Nexus device , just curious
TechSavvy2 said:
This seems like an appropriate place to ask, with HTCDev unlock, how "unlocked" is the device currently? Like in terms of recoveries, kernels, radios, etc.? I ask here cuz I'm most curious about the functionality of CWM Recovery and how much time I'm gonna have to play around in it.
I saw koush state that its basically the status and simplicity of a Nexus device , just curious
Click to expand...
Click to collapse
Well to unlock the phone. Basically just gives you access to boot, system, and recovery partitions. But to flash roms, you must flash the boot.img in fastboot after flashing the rom .zip in recovery. You would need s-off on a HTC phone to flash radios, splash screens...etc...
This works just fine. I did this early today using the post from the international version as all the GSM versions seem to be the same at least as far as the recovery is concerned. I rooted and I use Koush's SuperUser
This worked great for me as well, first attempt to get into recovery failed but the next one worked just fine. Now lets see if I cant' hunt down some of those wake locks. :victory:
Flyhalf205 said:
Use Rom Manager for best results when backing/restoring...
USB OTG Info:
USB OTG will show up as external_sd. If external_sd is not mounting, reboot recovery. You must enter recovery with usb already inserted.
Installation:
Inscrutions can be found here @ http://www.techgeekal.com/2013/03/1...ckworkmod-touch-recovery-v6-0-2-8-on-htc-one/(outdated)
Unlock bootloader at http://www.htcdev.com/bootloader/
Make sure fastboot is unchecked in power options and turn phone completely off
Boot into HBOOT then Fastboot
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
OR
Flash via Rom Manager(must have root already).
Video Tutorials:
How To Unlock The Bootloader EASIEST Method - https://www.youtube.com/watch?v=r0gzJdwCxX0
How To ROOT EASIEST METHOD - https://www.youtube.com/watch?v=S1KmsxO84UU
Downloads:
You can now flash in Rom Manager in rom if rooted
Classic - http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.3.2-m7tmo.img
OR
Touch - http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.3-m7tmo.img
PC USB Mass Storage:
You can't! http://teamw.in/DataMedia
Mirror for files http://d-h.st/users/flyhalf205/?fld_id=11322#files or http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
well instructions..useful guidelines...
Related
Hello, I rooted and used this method to root and install recovery:
http://forum.xda-developers.com/showthread.php?t=1690919
Then I installed Mean ROM and everything went smoothly.
I tried installing a kernel:
First, I tried this:
http://forum.xda-developers.com/showthread.php?t=1814037
and then I tried this:
http://forum.xda-developers.com/showthread.php?t=1800399
Both of them say they installed, but when I open Antutu CPU Master, I cannot overclock, I even went on the settings and about phone and it looked like the kernel was still the same.
Is there a specific method in which to flash the kernel?
Can someone help?
Thanks
I believe that you have to be S-OFF (preferred) or HTC Dev Unlocked to flash kernels successfully.
Also, if you took the latest OTA, you're now on a version of hboot, which doesn't allow flashing kernels.
Sent from my r00ted, unlocked, 100% tricked-out LTEVO
If you are on the new H-boot, you cannot flash kernels from recovery. Simple as that.
You can fastboot flash them. Theres a thread about it in the general section. I'd suggest reading up on it
Rxpert said:
If you are on the new H-boot, you cannot flash kernels from recovery. Simple as that.
You can fastboot flash them. Theres a thread about it in the general section. I'd suggest reading up on it
Click to expand...
Click to collapse
Can someone please provide me the link or a walkthrough on what to do?
I dont have anything installed on my computer at all and am completely new to this.
If your using TWRP 2.2.1 then maybe you can use the HTC Dumlock to flash kernels? I'm S-off so I don't have to use it.
Try this:
http://forum.xda-developers.com/showthread.php?t=1693205
Sent from my r00ted, unlocked, 100% tricked-out LTEVO
Here are the instructions for flashing a kernel on the latest hboot:
http://forum.xda-developers.com/showthread.php?t=1794867
You basically just need to flash the entire boot image instead of just the kernel. I know there is an an Enoch boot image available in the official thread, not sure about Evilz.
To do a fastboot flash you'll need the sdk installed. There is a good how to video here if you've never done it before:
http://www.youtube.com/watch?v=oaNM-lt_aHw
Sent from my EVO LTE
Another good source of info:
http://wiki.cyanogenmod.com/wiki/Fastboot
Sent from my r00ted, unlocked, 100% tricked-out LTEVO
Might be able to flash using Flash Imgae GUI.
Edit: Nvm. premo15's first link talks about using it.
I tried Flash Image GUI, but it messed up my rom, now I keep getting a Reboot Loop on the HTC Screen with the Developer Warning.
I then tried to clear all data and install the Mean Rom again, and when I do, it says that the ROM is installed in the Recovery, but When it boots, it goes back to the Reboot Loop.
Can someone Please Help me!
gokuman56 said:
I tried Flash Image GUI, but it messed up my rom, now I keep getting a Reboot Loop on the HTC Screen with the Developer Warning.
I then tried to clear all data and install the Mean Rom again, and when I do, it says that the ROM is installed in the Recovery, but When it boots, it goes back to the Reboot Loop.
Can someone Please Help me!
Click to expand...
Click to collapse
You have to extract the boot.img from mean rom and use fastboot to install it. premo15's first link also talked about using fastboot to install. If you want to install a custom kernel then just take the boot.img out of the fashable zip and use fastboot.
Okay,
I got ADB to Work, but whenever I do an ADB Command, such as adb reboot bootloader. It says Device Not Found, I installed the appropriate drivers and it also makes a device connected sound when I plug in the phone. When I open device manager, it shows all drivers installed.
Can someone help me with this issue, lol, I've been having so many issues with modding this phone....
gokuman56 said:
Okay,
I got ADB to Work, but whenever I do an ADB Command, such as adb reboot bootloader. It says Device Not Found, I installed the appropriate drivers and it also makes a device connected sound when I plug in the phone. When I open device manager, it shows all drivers installed.
Can someone help me with this issue, lol, I've been having so many issues with modding this phone....
Click to expand...
Click to collapse
You can type in adb devices to show connected devices. Make sure Android debugging is on in Settings -> Developer Options.
My Phone will not Boot at all. I cannot Enable ADB Debugging, I can go to the Bootloader Menu or the Recovery Menu.
I pressed fastboot and enabled fastboot-usb, and it made a connecting noise, but with adb, it will say phone not found
gokuman56 said:
My Phone will not Boot at all. I cannot Enable ADB Debugging, I can go to the Bootloader Menu or the Recovery Menu.
I pressed fastboot and enabled fastboot-usb, and it made a connecting noise, but with adb, it will say phone not found
Click to expand...
Click to collapse
Try going into recovery from the bootloader and then try the "adb devices" command. I've noticed that I can't issue adb commands while in fastboot also...not sure why. If you can get it to display your device while in recovery, then you know your communication is good. Go back into fastboot and you should be able to do the "fastboot flash boot" command, but rebooting with the adb command will not work for some reason. After you flash the boot image, there should be an option to reboot on your phone that you can select with the volume keys.
Sent from my EVO LTE
Thanks! Got it!
when you flash a boot img, what folder does it go in? i have the same problem but i have a mac.
[FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-13
My friend's phone had the annoying bootloop problem. I'm posting this because after a lot of searching, I found nothing to fix the bootloop, just people asking about it. Here's a simply fix.
BOOTLOOP FIX:
If you already tried unlocking/ and you're still S-On, then set everything back to stock:
Flash the attached stock recovery,
fastboot oem lock to be locked again.
Use the latest RUU to update the phone.
At this point the stock, locked phone should function normally.
I have busted this phone a ton of times trying to get different recoveries and roms to work, and this method has always fixed the bootloop.
At this point you can try whatever tutorial you like to downgrade or customize the phone...and if it breaks, hopefully this method will still work for you. If it doesn't work the first time, try running the RUU a second time. Or third.
CUSTOM RECOVERY:
If you want to unlock and install custom stuff:
Use the HTC Dev unlock method.
Fastboot install CWM Recovery v5.8.0.1 from their website -
The ONLY recovery that I've found to be compatible with HBOOT 1.58 is CWM v5.8.0.1. Everything else leaves the phone in an infinite bootloop. Maybe others have had different experiences.
To fastboot install the CWM recovery, rename the file to recovery.img (for simplicity) and type in a command prompt (same directory as fastboot and recovery.img):
fastboot flash recovery recovery.img
Then, to enter into recovery, either pull the battery and enter recovery through the bootloader menu, or type in:
fastboot boot recovery.img
This should get you into the working CWM recovery. If it doesn't, it's because HTC hates people that buy their phones.
If you feel like giving up and running stock, all you need to do is reflash the stock recovery, and relock the phone using fastboot oem lock - and now it should run the stock rom...and if it doesn't, then rerun the RUU. Tedious.
HBOOT Downgrade & S-Off:
If you have: Stock 2.89 RUU / Locked / S-On
Unlocked with HTC Dev method
Flash CWM 5.8.0.1 from the CWM website:
fastboot flash recovery recovery.img - then
fastboot boot recovery.img (to enter recovery)
Flash the SetMainVersionLOW.zip file attached (thanks ramjet73)
Relock the phone with: fastboot oem lock
Use the Unknownforce/closeone hboot downgrade with live CD using the 2.89 RUU's rom.zip (from windows temp folder) renamed to PG86IMG.zip - go to the Unknownforce/closeone thread for this part: http://forum.xda-developers.com/showthread.php?t=1563342
Then flash the standard 1.13 RUU on your windows system (may also work with the PG86IMG.zip method, have not tested)
Then use revolutionary 0.4pre4 to S-Off
Finally, you need to flash a custom recovery which you can do from revolutionary, or from fastboot as listed above. Once the recovery is installed, you should be able to install a compatible custom rom and kernel.
You bootloader screen should now say REVOLUTIONARY on top instead of UNLOCKED or RELOCKED etc... and show HBOOT 1.40.1100.
Thanks to Unkownforce, closeone, and ramjet73 for making this possible.
PS. Screw up your phone at your own risk.
In case anybody was wondering, the RUU I've been using is the latest one at the time of this post: RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to be one of the stock versions I guess, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
mnomaanw said:
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to one of the stock versions, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
Click to expand...
Click to collapse
Yeah, don't ever do the write secure flag command. That's bad news. Running a ruu will not s- on, and you're better staying s-off
Sent from my PG86100 using xda app-developers app
Reset s-on, and
fastboot oem lock to be locked again.
Click to expand...
Click to collapse
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
xHausx said:
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
Click to expand...
Click to collapse
@xHausX
Totally agree. The only reason to set S-ON once S-OFF is achieved is to return to 100% stock for warranty service or to sell the phone.
Nice to see you in these parts again and Happy New Year!
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
I updated the OP. I read somewhere else that it was necessary, this phone was never S-Off, so I wasn't sure.
Thanks
Everytime i run the ruu for my 3d it will finish as it has completed and boot. But whenever i remove my battery to switch it with a secondary, i used to do this before bed every night, i get a bootloop and cant boot untill i boot into bootloader and select the recovery option which wipes the phone and boots untill then next time i remove the battery. Why wont the RUU fix this? ive ran it multiple times. And also whenever im in the stock recovery and i select factory reset or any of the options i get "invalid option" "sucess rebooting by reason oem-00" what does this mean!?! can this be my sd? cause i cant mount cache recovery command or mount anything in recovery for that matter. if i need an sd ill buy one. just dont wanna find out its not my sd. and ive run the RUU about 7 times in total and nothing helps. thanks
ramjet73 said:
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
Click to expand...
Click to collapse
Yeah, I put WIP because it still never worked right, it was just the only one that ever actually loaded. I still hate this phone, I wish HTC was as nice as Samsung. It's so easy to work with Samsung, I always get mad trying to work around HTC's crippling B.S. Still better than Motorola though.
bootloop in my Htc Evo 3D hboot 1.53.007
How do you flash the stock recovery?
jcthelight said:
How do you flash the stock recovery?
Click to expand...
Click to collapse
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
i have hboot 1.53 with s-on stuck on bootloop and i did as u said i flashed stocked recovery from temp folder from ruu-ics-35-ara.exe still my phone is in boot loop. Even i tried oem lock and run ruu.exe file upto 65% process goes fine then suddenly shows 100% process complete and reboot device(still stuck on bootloop).... plz give me suggestion to get rid of this thing.....
"RUU_SHOOTER_U_ICS_35_S_HTC_ARA_3.28.415.2_Radio_11.77.3504.00U_11.25.3504.06_M_release_264795_signed.exe"
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
I'm a little confused. I've never rooted this phone so it's completely stock. My phone keeps powercycling. When I type in "fastboot flash recovery recovery.img" my cmd prompt tells me FAILED (remote: signature verify fail).
Any suggestions?
Re: [FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-
Dang it! Why does it seem like developers have quit developing fully functioning roms for this phone? I live in a good 4g area so those roms without it are out of the question for me. And the others are having major issues with cameras, video playing, text messaging that keep it from being a daily....
And after using jellybean these ICS roms feel very incomplete even though they're more functional. I know you developers are busy people but please, can ICS get freshened up. Or just ignore me if y'all think the camera/text thing will be resolved very soon.
Sent from my PG86100 using xda premium
I recently went from being HTC Dev unlocked 1.58 to JuopunutBear S-Off. Before I was able to do fastboot commands but coundn't flash a recovery. I figured that maybe doing Jbear might do something for the issue since I wanted to S-Off anyway. Due to some ignorance I did the Jbear process and wiretrick to achieve S-off. But, Instead of using a Jbear Bootloader I though I could downgrade also by flashing a 1.13 RUU. I did it and my phone worked. When I went to the bootloader it read: S-Off 1.40 ect. (with no Locked/Unlocked bar at top). I wanted to flash a ROM and it didn't work so I thought i should try to unlock the phone bootloader. This did not work.
I then found out I had to use a Jbear bootloader and I am now on: Hboot 1.50.5050 with S-Off and (Joupunutbear) at top. Now whenever I try to use fastboot or adb commands I get the error *device not found* or -waiting for device-. I want to flash a recovery and then a rom but neither is possible now.
Things I have researched and checked:
1. htc sync drivers work/are up to date(i used them before this issue occurred and have tried others)
2. usb debugging is on.
3. I can not do a logcat. I get the same error.
4. I tried to install the recovery through the rom manager app but it got the same error.
Any help in advance would be appreciated.
(I apologize if there is already a solution on the site. I have searched to the best of my ability.)
If your phone boots up, go to developer options and make sure android debugging is enabled
Otherwise, it sounds like you are in boot loader. You need to navigate to fast boot
Then when your USB is connected it should read fast boot USB
Flash recovery
Make a backup
Wipe all partition except SD
Flash ROM/gapps whatever
Reboot
Sent from my Evo V 4G using xda app-developers app
hossman said:
If your phone boots up, go to developer options and make sure android debugging is enabled
Otherwise, it sounds like you are in boot loader. You need to navigate to fast boot
Then when your USB is connected it should read fast boot USB
Flash recovery
Make a backup
Wipe all partition except SD
Flash ROM/gapps whatever
Reboot
Sent from my Evo V 4G using xda app-developers app
Click to expand...
Click to collapse
I have rooted my two previous phones, one of them being HTC android so I have some experience. What I'm saying is that I have usb debugging on and I boot to bootloader, then fastboot and get fastboot-usb.
Despite doing everything correctly it still gives errors with the device. For example, i tried again this morning and waited until it said -waiting for device- to go into fastboot and it did something different:
* attached an image of my commands since I coundn't link them. (new user)
the second command is what happens when i start in fastboot usb.
All commands dealing with fastboot result in *Device not found*
Thanks for the response, I understand those common issues get posted a lot.
Alright, so I flashed a new rom, but for some reason it wouldn't boot up, it wouldn't get past the white htc screen. So when I went into recovery to flash a different rom somehow my sdcard was formatted, so I have nothing on my sdcard to flash and my phone won't boot up so I can't access USB storage. Also because it was a new rom, I wasn't able to enable usb debugging so adb isn't working. I can still use fastboot and I can still access CWM but I can't find a way to push a file onto my phone. I tried sideloading but adb isn't working, and I went into mounts and storage and tried "mount usb storage" and it doesn't mount. I tried reinstalling the HTC drivers to get adb working but no luck there. Please not sure what else to try from here, any help would be greatly appreciated.
two methods that will quickly fix issue you are having
method one
seeing as you say sdcard hopefully that means otg cable and sdcard reader or usb storage device. if this is the case proceed to put rom of choice on usb or sdcard and flash via that way and hope your s-off or you will need to flash kernel boot.img in fastboot and modules in recovery..
method 2.
go into fastboot <<< already there
enter fastboot oem relock <<<< locks your bootloader again
run RUU <<< puts you back at 1.15 og firmware
then update to latest firmware <<< will be 2.07 i believe
moonshine your device and enjoy the benefits of custom roms <<< happy ever after
t1gartist said:
two methods that will quickly fix issue you are having
method one
seeing as you say sdcard hopefully that means otg cable and sdcard reader or usb storage device. if this is the case proceed to put rom of choice on usb or sdcard and flash via that way and hope your s-off or you will need to flash kernel boot.img in fastboot and modules in recovery..
method 2.
go into fastboot <<< already there
enter fastboot oem relock <<<< locks your bootloader again
run RUU <<< puts you back at 1.15 og firmware
then update to latest firmware <<< will be 2.07 i believe
moonshine your device and enjoy the benefits of custom roms <<< happy ever after
Click to expand...
Click to collapse
Thank you so much for the information!
I managed to solve the issue by flashing TWRP via fastboot, once I flashed TWRP, the drivers installed automatically and adb was able to see my device, afterwards I was able to push a ROM to my sdcard via adb, flashed it in recovery and bam phones working again.
that works too good deal and happy flashing... btw for me TWRP i always had better lucky with also CWM is notorious for formating all of your data and being as the DNA has no true sdcard its a deal breaker for me in my experiences so enjoy
I am on a (completely stock) AT&T HTC One (4.4.2) and I was thinking about trying out some custom ROMs. Can I just use the HTC dev tool to unlock the boot loader? How would I root after that?
I am still new to it so that's about as far as I've gotten in the process. Especially since most of the tutorials I've seen are older and do not exactly mention 4.4.2.
P.S. ~ Kingo root seems to have a very simple HTC boot loader unlock tool as well as an easy method to root. I used the root method on my GS4 a while back and it went pretty well. Are there any downsides to using these?
Kwwolves2012 said:
I am on a (completely stock) AT&T HTC One (4.4.2) and I was thinking about trying out some custom ROMs. Can I just use the HTC dev tool to unlock the boot loader? How would I root after that?
I am still new to it so that's about as far as I've gotten in the process. Especially since most of the tutorials I've seen are older and do not exactly mention 4.4.2.
P.S. ~ Kingo root seems to have a very simple HTC boot loader unlock tool as well as an easy method to root. I used the root method on my GS4 a while back and it went pretty well. Are there any downsides to using these?
Click to expand...
Click to collapse
Getting started with rooting and putting Roms on your phone is no time to get Lazy !
The steps are very simple but learning it the correct way comes in handy down the road.
unlock the bootloader at htcdev.com
use the drivers and adb/fastboot I'm posting below
after you bootloader is unlocked
you use fastboot to flash custom recovery on the phone
TWRP 2.6.3.3 is recommend - Download TWRP
The commands to flash it are
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Now enter recovery and on Exit it ask to Root the phone
choose Yes - swipe to root
when the phone boots up go in the app drawer and open SuperSU
it will ask to update choose yes and TWRP method of install
Your phone is now unlocked / rooted / with custom recovery
Now is the time to make a backup in TWRP and copy it to your PC for safe keeping. Your now all set to flash custom roms
links
SuperSU
HTC Drivers
clsA said:
Getting started with rooting and putting Roms on your phone is no time to get Lazy !
The steps are very simple but learning it the correct way comes in handy down the road.
unlock the bootloader at htcdev.com
use the drivers and adb/fastboot I'm posting below
after you bootloader is unlocked
you use fastboot to flash custom recovery on the phone
TWRP 2.6.3.3 is recommend - Download TWRP
The commands to flash it are
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Now enter recovery and on Exit it ask to Root the phone
choose Yes - swipe to root
when the phone boots up go in the app drawer and open SuperSU
it will ask to update choose yes and TWRP method of install
Your phone is now unlocked / rooted / with custom recovery
Now is the time to make a backup in TWRP and copy it to your PC for safe keeping. Your now all set to flash custom roms
links
SuperSU
HTC Drivers
Click to expand...
Click to collapse
Alright, thank you very much. I will look into this.