Okay, so I got hboot 2.09 unlocked. I then proceeded to follow QBKing77 instructions for rooting and installing openrecovery. I downloaded the root files from the link he provides. When I type in "fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img" and hit enter, it tells me error: cannot load fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img,: Unkown Error. Can anyone offer any suggestions here? Thanks.
cmparramore said:
Okay, so I got hboot 2.09 unlocked. I then proceeded to follow QBKing77 instructions for rooting and installing openrecovery. I downloaded the root files from the link he provides. When I type in "fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img" and hit enter, it tells me error: cannot load fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img,: Unkown Error. Can anyone offer any suggestions here? Thanks.
Click to expand...
Click to collapse
Do you have android SDK instaslled?
bigdaddy619 said:
Do you have android SDK instaslled?
Click to expand...
Click to collapse
Yes I actually went back through the entire process, and checked the path to make sure it was installed correctly. Rebooted the computer and the phone, but still getting unknown error message.
try this open your sdk folder and press shift and right click platform tools and select open cmd window here
that will put you in a writeable folder
Unfortunately I do not get that option. Running windows XP.
hmmmm
is the .img file in your platform tools folder?
drivers installed?
does your pc recognize your phone when you plug the USB in?
---------- Post added at 05:47 AM ---------- Previous post was at 05:36 AM ----------
try downloading this it has all the files you need
once you open cmd window point to this folder
http://d-h.st/5zT
Yes, Yes & Yes
try this
DOH!! Dang, it helps if you use the right directory. I am such a dunce. Thanks for all the help and sorry for being such a goonhead, maybe I need some more coffee!!
hahaha no worries
hey do you know if there coming up with a s-off for hboot 2.09
cmparramore said:
Yes, Yes & Yes
Click to expand...
Click to collapse
Worked for me. and I'm hboot 2.09 also. I don't have windows xp but when I open the sdk directory. hold shift and right click I get a prompt saying "open command window here" I then issue the fastboot flash recovery openrecovery-twrp-2.3.3.0-jewel.img command. it flashes just fine. I think you're missing a step or two.
Please take a look at my thread on rooting/superuser/TWRP installs. It's a pretty good guide. I tried to take the mystery out of this process.
http://forum.xda-developers.com/showthread.php?t=2038123
I am having issues rooting via qbking77's method on Youtube.
I'm stuck at the 5:42 mark where I need to mount USB storage via Teamwin / TWRP recovery.
The 'Mount Cache/Mount SD Card/Mount Internal' aren't' checked on my phone and I can't check them manually. When I click on 'Mount USB Storage'. My computer pops up a message telling me that 'You need to format the disk drive in F:before you can use it. I'm not sure what to do next.
Any suggestions? Thanks.
Thanks this forum helped me find my problem while following qbking77 video on how to root. I realized after quite a few tries that the twrp img file had changed a bit since the video was posted. When bigdaddy619 check for file I found file to be openrecovery to have some different numbers.
Also the actual root file towards the end of the video name/version had changed also. Little details make a big difference.
Im having an issue trying to install openrecovery as well. Ive followed all of qbking77's instructions in the videos. Im running HBOOT 2.09 which is already unlocked. I have SDK tools and everything as well. When i get to the step to install openrecovery, I go to the folder containing the file and shift+right click and open a cmd window. This is what I get:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>fastboot flash recovery openrecovery-tw
rp-2.5.5.0-jewel.img
< waiting for device >
sending 'recovery' (8196 KB)...
And thats it. It locks up and doesn't go any further. I've tried several times and retraced my steps through the whole install procedure with the same result. Can you fellas help me out?
PooPCovington said:
Im having an issue trying to install openrecovery as well. Ive followed all of qbking77's instructions in the videos. Im running HBOOT 2.09 which is already unlocked. I have SDK tools and everything as well. When i get to the step to install openrecovery, I go to the folder containing the file and shift+right click and open a cmd window. This is what I get:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>fastboot flash recovery openrecovery-tw
rp-2.5.5.0-jewel.img
< waiting for device >
sending 'recovery' (8196 KB)...
And thats it. It locks up and doesn't go any further. I've tried several times and retraced my steps through the whole install procedure with the same result. Can you fellas help me out?
Click to expand...
Click to collapse
When you type adb devices and hit enter, what happens?
Sent from my EVO using xda premium
FinZ28 said:
When you type adb devices and hit enter, what happens?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
When I type "adb devices" with my phone connected and in bootloader menu this is what i get:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>adb devices
List of devices attached
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>
Not sure if that's what i'm supposed to get, but if I instead type "fastboot devices" I get this:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>fastboot devices
HT25PS403929 fastboot
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>
PooPCovington said:
When I type "adb devices" with my phone connected and in bootloader menu this is what i get:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>adb devices
List of devices attached
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>
Not sure if that's what i'm supposed to get, but if I instead type "fastboot devices" I get this:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>fastboot devices
HT25PS403929 fastboot
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>
Click to expand...
Click to collapse
My bad, forgot you were in fastboot. Looks like everything is working as it should, though, so I can't think of why you would be having the problems you are
Sent from my EVO using xda premium
FinZ28 said:
My bad, forgot you were in fastboot. Looks like everything is working as it should, though, so I can't think of why you would be having the problems you are
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Anyone else have any ideas? I've rooted this phone before in the past and never had a problem unlocking and rooting or unrooting and relocking so this is most peculiar. I've tried qbking77's method, i've also tried other tutorials out there as well as attempting to use other versions of openrecovery but it just won't root.......
PooPCovington said:
Anyone else have any ideas? I've rooted this phone before in the past and never had a problem unlocking and rooting or unrooting and relocking so this is most peculiar. I've tried qbking77's method, i've also tried other tutorials out there as well as attempting to use other versions of openrecovery but it just won't root.......
Click to expand...
Click to collapse
Try uninstalling everything HTC from your PC
reboot PC and device
re-install drivers including HTC Sync(you can delete it afterwards and the drivers will remain)
plug in your device via usb cable it should install the drivers again also boot into the bootloader drivers should install again
You should be good to go now
Related
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
navenine said:
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
Click to expand...
Click to collapse
Try this, starting over. You shouldnt run into any hiccups.
tailsthecat3 said:
Try this, starting over. You shouldnt run into any hiccups.
Click to expand...
Click to collapse
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
navenine said:
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
Click to expand...
Click to collapse
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
tailsthecat3 said:
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
Click to expand...
Click to collapse
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
hey im trying to use the ruu to get back to stock , just re locked the phone , and im STILL getting errors with ruu, its saying Update Failed : Hboot version is older , im on hboot 1.5000 .........Im losing my mind trying to get this thing back to stock and out of htc screen logo bootlooping.........any ideas?
navenine said:
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
Click to expand...
Click to collapse
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
tailsthecat3 said:
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
Click to expand...
Click to collapse
this just got even worse, I uninstalled the drivers, and now I can't reinstall them. I can't find them. My computer wont recognize my phone at all. I've tried to goto the device manager and find them online automatically, and I've tried the google USB drivers from the extra folder from the SDK Manager...
if you can point me toward the USB drivers that'd be great, but regardless, what your saying is I need to connect my phone while its in the bootloader? not once its booted? or are you saying I need to boot my phone through the bootloader selecting "fastboot" first?
thanks again
-Nave
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
navenine said:
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
Click to expand...
Click to collapse
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
I pushed everything over, got it into the fastboot USB and then typed the "fastboot flash recovery recovery.img" command line
my script was:
sending 'recovery' <5068 KB>...
Okay [ 1.207s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote:signature verify fail>
finished. total time: 1.855s
any ideas?
tailsthecat3 said:
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
Click to expand...
Click to collapse
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
navenine said:
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
Click to expand...
Click to collapse
Where were you going wrong? And what'd you do to correct it? So everyone knows, in case they encounter the same issues.
Sent from my Google Nexus S 4G via XDA Premium
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
navenine said:
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
Click to expand...
Click to collapse
I appreciate that, thank you.
I've been trying regaw methode to root but havn't had much luck. I get the message "you see this window now because we are waiting for your EVO 4G LTE to reconnect to the computer after reboot". What went wrong. Is there a better way to root?
dvrdwn said:
I've been trying regaw methode to root but havn't had much luck. I get the message "you see this window now because we are waiting for your EVO 4G LTE to reconnect to the computer after reboot". What went wrong. Is there a better way to root?
Click to expand...
Click to collapse
You could try zedomax's method founf here http://forum.xda-developers.com/showthread.php?t=1671577 but read through the thread to make sure it works with the base you are running meaning your firmware
bigdaddy619 said:
You could try zedomax's method founf here http://forum.xda-developers.com/showthread.php?t=1671577 but read through the thread to make sure it works with the base you are running meaning your firmware
Click to expand...
Click to collapse
thanks for the reply. unfortunitly I have ver. 2.13
dvrdwn said:
thanks for the reply. unfortunitly I have ver. 2.13
Click to expand...
Click to collapse
well click the link and look around and see if people are have success with v2.13
HTC Dev Unlock
Requirements
HTC Drivers
ADB Tools Mini SDK
Setup
Install HTC Drivers if necessary
Extract ADB Tools anywhere, doesnt matter
Open ADB Tools and hold shift+right click, select open command window here
In phone settings, enable usb debugging and disable fasboot
Connect the phone to pc
Steps
In the command window type adb start-server
Next type adb reboot bootloader
Type fastboot devices to make sure you are connected
Type fastboot oem get_identifier_token
Right click and select mark, click and drag from the top arrows <<<< Identifier Token Start >>>> to the bottom arrows <<<<Identifier Token End >>>> and make sure not to highlight any empty spaces as this will confuse the website, right click and it will be saved to clipboard
Now go to HTC Dev and if you don't already have an account, sign uo for it
Go to unlock bootloader and select other device and accept the agreements
Skip the steps until you get the to token submit window and paste the token you copied earlier and submit.
Go to your email and download the unlock_bin code
Put the code in the ADB Tools folder
Type fastboot flash unlocktoken Unlock_code.bin
When the phone prompt comes up to unlock bootloader hit yes, now you are unlocked, re-enable usb debugging and disable fastboot
Type adb reboot bootloader
Type fastboot devices to make sure phone connected
Type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img
Type erase cache
Reboot phone and you will have unlock and recovery, all thats missing is to restart phone in bootloader and select recovery to flash a rom. Both meanrom and viper have built in kernel installers, should the phone get stuck booting just extract the boot.img from the rom and put it in adb, with phone in fastboot type fastboot flash boot boot.img
for the life of me, I could not get the regawMOD root to work for me, I ended up doing a one click root and feeding the panda for s-off :good:
dvrdwn said:
I've been trying regaw methode to root but havn't had much luck. I get the message "you see this window now because we are waiting for your EVO 4G LTE to reconnect to the computer after reboot". What went wrong. Is there a better way to root?
Click to expand...
Click to collapse
You just have to manually reboot bootloader and it will continue
epic4gt said:
You just have to manually reboot bootloader and it will continue
Click to expand...
Click to collapse
not sure how to do that.
Power button while holding volume down. Or, while running regaw, you may be able to just hold power for a minute at the appropriate times.
from my flying AOKP'd Evo LTE and xda premium
O.K. I've done the bootloader thing manualy and have gotten as far as "flashing recovery". the phone rebooted and it got as far as my phone starting up like I had just reset it. My bootloader say it's unlocked with S on. I don't think I'm rooted yet. What I'm trying to do is use my phone as a hot spot using wifi tether or something like it. Thats it. I've tried the unrooted software and it does'nt work.
So did it flash the recovery?
from my flying AOKP'd Evo LTE and xda premium
scottspa74 said:
So did it flash the recovery?
from my flying AOKP'd Evo LTE and xda premium
Click to expand...
Click to collapse
I'm not sure. How can I tell?
It should have said ok and something like write time 2.96s or something, connect adb and use adb reboot or hold power and when phone shuts of let go of power and hold power and volume down and select recovery from bootloader
So you don't want to flash another rom? Just flashing meanrom is less of a hassle then downloading the zip for superuser and busy box, flashing it in recovery and then installing a WiFi tether app
Twrp should of flashed. U should update to New twrp tho. The goo app makes it really easy to update your recovery
---------- Post added at 07:36 PM ---------- Previous post was at 07:32 PM ----------
I got stuck on recovery but it did flash it. I think it the newest hboot 1.19 that's holding up the root step. All your doing is unlocking your phone for recovery.
---------- Post added at 07:43 PM ---------- Previous post was at 07:36 PM ----------
om4 said:
It should have said ok and something like write time 2.96s or something, connect adb and use adb reboot or hold power and when phone shuts of let go of power and hold power and volume down and select recovery from bootloader
So you don't want to flash another rom? Just flashing meanrom is less of a hassle then downloading the zip for superuser and busy box, flashing it in recovery and then installing a WiFi tether app
Click to expand...
Click to collapse
Yeah. Just flash mean Rom so you don't have to fastboot a boot.img if you choose an aosp Rom you will have to.
Want to unlock your bootloader to install a custom recovery and root your One but have no idea how because you have a Mac?
Never fear, Gunnyman is here.
The procedure is actually pretty painless and only takes a few minutes
Some prerequisites:
ADB and Fastboot binaries for OS X, I've attached them to this post.
Your recovery of choice, I'm using Clockwork Mod Recovery, because TWRP seems to have problems with some Aroma installer based ROMS. Get CWM for the One from here
SuperUser.zip
a Unix friendly text editor. I really like Text Wrangler and it's free.
Android File Transfer for Mac macs don't work with MTP mode without this.
In developer Options on the phone, turn on USB Debugging
EDIT:
Thanks to user Shivasmith I now know you can skip textwrangler and
If you hold down the "Alt" (i.e. Option) key on the Mac keyboard in terminal you can do a "column select."
So when you generate the codes for the HTCdev unlock website, you can just do a straight copy-paste without going into TextWrangler. It made it that much quicker
So thanks for the tip!
I've been using macs for 10 years and never knew that.
1. Unzip the adb and fastboot binaries and put them where you can find them. I have a directory on my Mac called /Android and that's where my phone stuff lives, but you can put it anywhere.
2. Put the cwm recovery (or twrp if you prefer) in the same folder as adb and fastboot.
3. Got to htcdev.com and create an account there if you don't already have one.
4. Log in to htcdev.com and choose unlock bootloader.
5. pick the last option for Unlisted device.
6. Open a terminal window and navigate to where you installed fastboot,adb, and your recovery eg: cd /Users/Gunnyman/Android
7. In Terminal execute the following commands ./adb reboot bootloader once in bootloader mode In terminal execute the following command: ./fastboot oem get_identifier_token
8. Open Text Wrangler
9. Copy the output from the terminal window into Text Wrangler make sure you include every line AFTER "please cut the following message"
10. Use Text Wrangler to DELETE (bootloader) from every line and make sure the columns line up exactly.
11. Copy and Paste this output into the box you are provided on HTC Dev. This part is quite annoying, getting the lines to line up.
12. Submit your token. When successful you will be sent a key via email.
13. Put the Unlock.bin file you got via email in the same directory as adb and fastboot on your mac.
14. execute the following command in terminal with the phone in fastboot mode ./fastboot flash unlocktoken Unlock_code.bin
15. Say yes to the prompts on the phone. Bootloader will unlock and the phone will be factory reset (there is NO way to avoid this)
16. OK Now the bootloader is unlocked. Time to install a recovery. In Terminal ./adb reboot bootloader
17. In terminal ./fastboot flash recovery name_of_the_recovery.img
18. After recovery has flashed POWER DOWN PHONE COMPLETELY Then restart it
19. connect phone to the Mac Android File Transfer should fire up
20. Put the Superuser.zip file on your phone
21. in Terminal ./adb reboot recovery
22. Flash the SuperUser.zip in recovery.
23. Pat yourself on the back your phone is now rooted.
great tutorial...thanks. quick question since i have the dev edition (unlock bootlader) can i just follow all these steps but go straight to # 16 to root my One?
thanks again.
Absolutely
WHEN I enter the "fastboot flash unlocktoken Unlock_code.bin i get a "denied " message in the terminal can anyone figure this out for me
What are the cons of rooting the phone and installing a custom recovery?
I know that it voids the warranty. Is there anything else besides that?
Some people reported some functions not working.
Or is that just when you install a custom ROM?
pedromartinez1983 said:
WHEN I enter the "fastboot flash unlocktoken Unlock_code.bin i get a "denied " message in the terminal can anyone figure this out for me
Click to expand...
Click to collapse
I've seen it once before. It was solved by creating a new account on HTC.dev. And getting a new key.
No cons. Rooting doesn't do anything except add access to the super user account built into the device.
gunnyman said:
No cons. Rooting doesn't do anything except add access to the super user account built into the device.
Click to expand...
Click to collapse
Thanks man
Sent from my HTC One using xda app-developers app
gunnyman said:
No cons. Rooting doesn't do anything except add access to the super user account built into the device.
Click to expand...
Click to collapse
Gunny! Good to see you made the right moves for this phone too!
Im reading stuff about att updating that wont allow to unlock bootloader? Is this true?
Sent from my HTC One using Tapatalk 2
MrPlNK said:
Gunny! Good to see you made the right moves for this phone too!
Im reading stuff about att updating that wont allow to unlock bootloader? Is this true?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Not so far.
SU keeps aborting installation when I try to install it, any ideas?
broopa said:
SU keeps aborting installation when I try to install it, any ideas?
Click to expand...
Click to collapse
Youre flashing zip from recovery?
Sent from my HTC One using Tapatalk 2
MrPlNK said:
Youre flashing zip from recovery?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yeah, from CWM. I tried fixing permissions with no luck.
broopa said:
Yeah, from CWM. I tried fixing permissions with no luck.
Click to expand...
Click to collapse
Did you turn phone on when you flashed recovery and then turn off then boot to recovery?
Sent from my HTC One using Tapatalk 2
I turned off phone, booted phone into BL menu then from there into CWM.
broopa said:
I turned off phone, booted phone into BL menu then from there into CWM.
Click to expand...
Click to collapse
Did you let the phone turn on and boot and then turn it off? Its important because when you unlocked bootloader/flashed recovery it completely reset your system meaning you need to boot it up and let it install the necessary stuff during boot animation (why it always takes so long the first time you boot up)
Sent from my HTC One using Tapatalk 2
I am pretty sure I did, I will reflash the recovery and see if that fixes it.
Edit: I just noticed I am unable to go back and reflash the the recovery. Is there a stock att version without root and CWM already on them so I can start from scratch?
Nice one gunnyman. Never disappoint. Its actually simpler to do on a mac because there isn't any driver installation. I just hope that AT&T allows us to do this for a while so that all of us here can get out key. Thats really all you need. You don't even need to do it, but its always a good idea to just get the key so if AT&T decides to block it again, you're safe.
If you guys are having trouble getting TWRP or CWS to work, make sure you have fastboot turned off in the power settings. It caused mine to not mount data sometimes.
This is a good right up. Finally have a way to do this on my Mac
hi guys im a total noob bought a droid dna on craigslist that was rooted. i tried to set back to stock with ruu got message error 158. i then tried hboot method and when i put cmd fastboot oem writeflagsecure 3 my phone now says tampered ,relocked, security warning and when you reboot just keeps going to fast boot menu.again im new to this and dont know what im doing so maybe i shouldnt have dabbled with it...ill attach a pic of the screen its a red employee edition droid dna... thanks for any help you can offer
Leave it alone! Go to recovery and delete data and reboot the phone.
Sent from my HTC6435LVW using XDA Premium HD app
ifi try recovery or anything just brings me back to the same screen
worm1977 said:
hi guys im a total noob bought a droid dna on craigslist that was rooted. i tried to set back to stock with ruu got message error 158. i then tried hboot method and when i put cmd fastboot oem writeflagsecure 3 my phone now says tampered ,relocked, security warning and when you reboot just keeps going to fast boot menu.again im new to this and dont know what im doing so maybe i shouldnt have dabbled with it...ill attach a pic of the screen its a red employee edition droid dna... thanks for any help you can offer
Click to expand...
Click to collapse
Did you know if it had an Engineer's HBOOT before? Writeflagsecure 3 is to remove S-OFF. You didn't need to do that to go stock.
Try flashing a recovery?
If this for insurance purposes? Just wondering what you're trying to do with your phone since it was working when you got it.
karn101 said:
Did you know if it had an Engineer's HBOOT before? Writeflagsecure 3 is to remove S-OFF. You didn't need to do that to go stock.
Try flashing a recovery?
If this for insurance purposes? Just wondering what you're trying to do with your phone since it was working when you got it.
Click to expand...
Click to collapse
i think i tried to flash recovery. i just want to get it to work so i can use it or sell it. when it poered up normally it had the red writing on the bottom that said for htc developer purposes also instead of the dna boot up it said htc one
worm1977 said:
i think i tried to flash recovery.
Click to expand...
Click to collapse
That isn't a good sign. What steps did you take to flash a recovery?
karn101 said:
That isn't a good sign. What steps did you take to flash a recovery?
Click to expand...
Click to collapse
tried recovery then reboot on phone just takes me to the same screen. also believe i tried fastboot-flash recovery
worm1977 said:
tried recovery then reboot on phone just takes me to the same screen. also believe i tried fastboot-flash recovery
Click to expand...
Click to collapse
No offense, but you keep saying things like "i think" or I "believe"; if you want our help, we need to know if you did it or not.
What recovery were you flashing?
Basically, what I'm saying is you might have deleted your recovery since you're saying that you keep ending up on the bootloader. You need to flash a recovery into your phone. If this doesn't make sense, just let me know and I'll point you in the right direction.
EDIT:
Follow these directions and then select RECOVERY from your bootloader. Let us know what happens please.
http://forum.xda-developers.com/showthread.php?t=1994662
karn101 said:
No offense, but you keep saying things like "i think" or I "believe"; if you want our help, we need to know if you did it or not.
What recovery were you flashing?
Basically, what I'm saying is you might have deleted your recovery since you're saying that you keep ending up on the bootloader. You need to flash a recovery into your phone. If this doesn't make sense, just let me know and I'll point you in the right direction.
Click to expand...
Click to collapse
It had clock work mod on it.no offense taken im just new to this and its kind if confusing to me.since it wouldnt boot thru ruu thats when I tried the hboot method.i dont quite understand the cmd's and flashing I guess.
karn101 said:
No offense, but you keep saying things like "i think" or I "believe"; if you want our help, we need to know if you did it or not.
What recovery were you flashing?
Basically, what I'm saying is you might have deleted your recovery since you're saying that you keep ending up on the bootloader. You need to flash a recovery into your phone. If this doesn't make sense, just let me know and I'll point you in the right direction.
EDIT:
Follow these directions and then select RECOVERY from your bootloader. Let us know what happens please.
http://forum.xda-developers.com/showthread.php?t=1994662
Click to expand...
Click to collapse
ok after i download do i just try to flash thru the adb commands?
worm1977 said:
It had clock work mod on it.no offense taken im just new to this and its kind if confusing to me.since it wouldnt boot thru ruu thats when I tried the hboot method.i dont quite understand the cmd's and flashing I guess.
Click to expand...
Click to collapse
I hear you, it can be overwhelming at first. I've been flashing since the WM 6.5 days and still don't know as much as some of the people here!
When you select RECOVERY, it's bringing you back to the BOOTLOADER screen, right?
If that's the case, the RECOVERY may have been removed, which is why I'm saying to flash a new one in. Did you follow the instructions on that thread I linked to?
---------- Post added at 04:04 AM ---------- Previous post was at 03:53 AM ----------
worm1977 said:
ok after i download do i just try to flash thru the adb commands?
Click to expand...
Click to collapse
Just saw this. No, you should be using fastboot commands, not ADB
fastboot flash recovery recovery.img
To begin, do you have the Android SDK installed on your computer? (Platform Tools)
You save the TWRP .img file in that folder.
Shift+Right Click on the folder and click Open Command Prompt Here
The phone should be connected to the PC
From the BOOTLOADER, go to FASTBOOT
It should say FASTBOOT USB
You can double check by typing 'fastboot devices'
Then run 'fastboot flash recovery recovery.img'
recovery.img will be named whatever your TWRP file is named
Then for good measure do 'fastboot reboot'
Now, you should be back in BOOTLOADER
Go to RECOVERY, and what do you see?
karn101 said:
I hear you, it can be overwhelming at first. I've been flashing since the WM 6.5 days and still don't know as much as some of the people here!
When you select RECOVERY, it's bringing you back to the BOOTLOADER screen, right?
If that's the case, the RECOVERY may have been removed, which is why I'm saying to flash a new one in. Did you follow the instructions on that thread I linked to?
---------- Post added at 04:04 AM ---------- Previous post was at 03:53 AM ----------
Just saw this. No, you should be using fastboot commands, not ADB
fastboot flash recovery recovery.img
yeah fastboot sorry. im at work now ill try it when i get home in 2 hours i have the sdk downloaded
To begin, do you have the Android SDK installed on your computer? (Platform Tools)
You save the TWRP .img file in that folder.
Shift+Right Click on the folder and click Open Command Prompt Here
The phone should be connected to the PC
From the BOOTLOADER, go to FASTBOOT
It should say FASTBOOT USB
You can double check by typing 'fastboot devices'
Then run 'fastboot flash recovery recovery.img'
recovery.img will be named whatever your TWRP file is named
Then for good measure do 'fastboot reboot'
Now, you should be back in BOOTLOADER
Go to RECOVERY, and what do you see?
Click to expand...
Click to collapse
i get home in 2 hours ill try then. i have sdk installed and was using fastboot commands
worm1977 said:
i get home in 2 hours ill try then. i have sdk installed and was using fastboot commands
Click to expand...
Click to collapse
Cool. Same here. I work 2300-0700 hours.
karn101 said:
Cool. Same here. I work 2300-0700 hours.
Click to expand...
Click to collapse
down loaded that goo manager tried fastboot flash recovery GooManager_2.1.2.img said unknown error cant load GooManager
worm1977 said:
down loaded that goo manager tried fastboot flash recovery GooManager_2.1.2.img said unknown error cant load GooManager
Click to expand...
Click to collapse
You need to flash a recovery twrp is probably the best one. Goomanager is a app use to download and install ROMs.
Sent from my HTC6435LVW using Tapatalk 2
coachcrey said:
You need to flash a recovery twrp is probably the best one. Goomanager is a app use to download and install ROMs.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
What he said ^^
Here are the direct links.
http://techerrata.com/browse/twrp2/dlx
I'd suggest downloading 2.5 as 2.6 gave me issues.
karn101 said:
What he said ^^
Here are the direct links.
http://techerrata.com/browse/twrp2/dlx
I'd suggest downloading 2.5 as 2.6 gave me issues.
Click to expand...
Click to collapse
I've had no problems with 2.6 personally but either one will work. Once your in
Recovery you can download a ROM on your computer and on adb use.
adb push "C:\Documents and Settings\Josh\My Documents\Downloads\ViperDNA_1.3.5.zip" sdcard
Clearly that's how I would do it via my computer after you type adb push you can hit the space bar and drag the file to the command prompt and drop it there that will do the dirty work lol then you just hit space and tell it to install on the sdcard.
Dont let your phone or computer go to sleep or the push will corrupt the file it can take up to 10 mins to transfer the file and once you hit enter it won't acknowledge its actually transferring Dont worry it is. It will tell you when its done how long it took and how much it transfered. After that you can flash the ROM and you should be golden man!
Sent from my HTC6435LVW using Tapatalk 2
coachcrey said:
I've had no problems with 2.6 personally but either one will work. Once your in
Recovery you can download a ROM on your computer and on adb use.
adb push "C:\Documents and Settings\Josh\My Documents\Downloads\ViperDNA_1.3.5.zip" sdcard
Clearly that's how I would do it via my computer after you type adb push you can hit the space bar and drag the file to the command prompt and drop it there that will do the dirty work lol then you just hit space and tell it to install on the sdcard.
Dont let your phone or computer go to sleep or the push will corrupt the file it can take up to 10 mins to transfer the file and once you hit enter it won't acknowledge its actually transferring Dont worry it is. It will tell you when its done how long it took and how much it transfered. After that you can flash the ROM and you should be golden man!
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
thanks guys im going to try it when i get home in the morning...lol i got alot to learn!!
worm1977 said:
thanks guys im going to try it when i get home in the morning...lol i got alot to learn!!
Click to expand...
Click to collapse
Not a problem man I hope this helped let me know if your still having issues I'm no dev but I have gathered a plethora of knowledge over the years playing with stuff.
Sent from my HTC6435LVW using Tapatalk 2
@worm1977 any luck man?
Sent from my HTC6435LVW using Tapatalk 2
Hello,
I was recently given a bootlooping Evo 4G Lte. I have been trying to figure out how to get this thing out of a bootloop and havent been able to do it. I, unfortunately, have no history on what happened to this device. Currently, it bootloops on the "Mean Bean" loading screen but will go no further. I can get into the bootloader, which says it is Unlocked, S-On, but I am unable to boot it into a recovery, it just returns back to bootloader. I have tried fastbooting twrp, but it fails (remote: image update error), and I have tried fastbooting the Mean Bean kernel thinking maybe thats all it needs, but that failed as well. Anybody have an insight? Much appreciated! Thanks.
Mike
I would run the 3.17 RUU. Hit the top link in my sig and look at the last post in the thread. You can run it from the bootloader. You'll need to re-root afterwards but it should get your phone back in working condition.
Sent from my HTC EVO 4G LTE
FinZ28 said:
I would run the 3.17 RUU. Hit the top link in my sig and look at the last post in the thread. You can run it from the bootloader. You'll need to re-root afterwards but it should get your phone back in working condition.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Thanks for the quick reply. I downloaded the RUU and ran it. However it sits and says "Waiting for bootloader" then errors out with "USB connection issue". The usb is working. The reason I never ran the RUU in teh first place was because i thought i read that you cant RUU with and unlocked bootloader. Is that not true? or is that my problem?
Mike
Not 100% sure but I will check with someone who used this tool recently and see if they were still unlocked at the time. Were you connected via Fastboot USB? Sounds more like a driver issue.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Shouldn't matter. I know of a couple of users who were having phone issues and had unlocked bootloaders when they ran this tool. Were you connected via Fastboot USB? Sounds more like a driver issue.
Click to expand...
Click to collapse
Yeah I was connected and it said fastboot USB. It said rebooting to bootloader and rebooted, still said fastboot USB. Then it sat at a screen that said "waiting for bootloader" and after a while error ed out.
You can try relocking. You just need to run the command "fastboot oem relock" from a command line while connected via fastboot USB mode.
Sent from my HTC EVO 4G LTE
FinZ28 said:
You can try relocking. You just need to run the command "fastboot oem relock" from a command line while connected via fastboot USB mode.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I have since tried relocking to see if that was it, and it did the same thing.
Mike
Hopefully @YoFayce can shed some light on the matter since he recently used this on his phone.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Hopefully @YoFayce can shed some light on the matter since he recently used this on his phone.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
crazymike1234 said:
I have since tried relocking to see if that was it, and it did the same thing.
Mike
Click to expand...
Click to collapse
you can use the stock RUU and you can leave the bootloader unlocked as it will not affect anything.. it will fix your looping problem (Amongst others) as in gps not working ect.. once your done you will need to fastboot over your TWRP and from there mod as normal Good Luck! and ill be watching if you need any help!
YoFayce said:
you can use the stock RUU and you can leave the bootloader unlocked as it will not affect anything.. it will fix your looping problem (Amongst others) as in gps not working ect.. once your done you will need to fastboot over your TWRP and from there mod as normal Good Luck! and ill be watching if you need any help!
Click to expand...
Click to collapse
Problem is the ruu keeps error in out. I am beginning to think it may still be a driver problem. Someday I will get this done!
Mike
crazymike1234 said:
Problem is the ruu keeps error in out. I am beginning to think it may still be a driver problem. Someday I will get this done!
Mike
Click to expand...
Click to collapse
When in doubt update your android SDK remove the htc drivers reboot install drivers reboot and you should be good to go! Check the integrity of your USB cable and if possible use a rear USB port (More Power) Painful process yes but well worth it.. HTC drivers act strange till you reboot OOOh and make sure your using the proper HTC drivers for windows 32 bit or 64 bit!
YoFayce said:
When in doubt update your android SDK remove the htc drivers reboot install drivers reboot and you should be good to go! Check the integrity of your USB cable and if possible use a rear USB port (More Power) Painful process yes but well worth it.. HTC drivers act strange till you reboot OOOh and make sure your using the proper HTC drivers for windows 32 bit or 64 bit!
Click to expand...
Click to collapse
The drivers seem to be ok, but I am still not able to get any further. The RUU finds my phone, then reboots again to bootloader, but it just sits there saying "Waiting for bootloader" until it errors out due to "USB Connection error". I have tried a few different cables, and different USB ports. Not sure what the problem is but it just wont go any further. I re-unlocked my bootloader with htcdev. I have tried fastbooting a recovery to the phone but it errors out. I just cant get anything to work so I can boot anything. I really just want to get something working...anything! Any other ideas? Thanks.
Mike
use an sd card put a recovery image on the root of the sd boot into bootloader apply the recovery you should then have a recovery if you did it right, go into twrp mount device add a rom flash in recovery viola.
Sinistertensai said:
use an sd card put a recovery image on the root of the sd boot into bootloader apply the recovery you should then have a recovery if you did it right, go into twrp mount device add a rom flash in recovery viola.
Click to expand...
Click to collapse
Sinister,
Thanks for the reply. I put TWRP on the sdcard (named PJ75IMG, right?) and tried to apply that when I rebooted to recovery last night and it failed. It tries to load it but gives a few errors quick (No Image) Did I do it wrong?
Mike
crazymike1234 said:
Sinister,
Thanks for the reply. I put TWRP on the sdcard (named PJ75IMG, right?) and tried to apply that when I rebooted to recovery last night and it failed. It tries to load it but gives a few errors quick (No Image) Did I do it wrong?
Mike
Click to expand...
Click to collapse
make sure the file is just the PJ75IMG no additional text and it should be .zip If I recall correctly. make sure its on the root of the sdcard not internal but sd or external and it should be at the top level e.g. sdcard/ make sure its not in any other folders after you do that hold power and vol down get to hboot screen itll scan and then just follow the instructions.
Sinistertensai said:
make sure the file is just the PJ75IMG no additional text and it should be .zip If I recall correctly. make sure its on the root of the sdcard not internal but sd or external and it should be at the top level e.g. sdcard/ make sure its not in any other folders after you do that hold power and vol down get to hboot screen itll scan and then just follow the instructions.
Click to expand...
Click to collapse
Thats exactly what I did. It is the only thing on the sdcard. It says no gift file, Loading, no image for 4 different things. Then returns to the bootloader.
Mike
crazymike1234 said:
Thats exactly what I did. It is the only thing on the sdcard. It says no gift file, Loading, no image for 4 different things. Then returns to the bootloader.
Mike
Click to expand...
Click to collapse
zip files probably corrupt then. download another do the same process make sure you've got a good file use md5 checks
Sinistertensai said:
zip files probably corrupt then. download another do the same process make sure you've got a good file use md5 checks
Click to expand...
Click to collapse
Hmmm, Ill try download again. I got it from the main TWRP site.
crazymike1234 said:
Hmmm, Ill try download again. I got it from the main TWRP site.
Click to expand...
Click to collapse
careful on the vol down press you might be holding it too long and its canceling the update.
Sinistertensai said:
careful on the vol down press you might be holding it too long and its canceling the update.
Click to expand...
Click to collapse
Well, which recovery file should I be using? When I use the main TWRP ones (ie openrecovery-twrp-2.6.0.0-jewel.img) it gives me the errors like I said above. I now see they have a few labeled like this PJ75IMG-twrp-2.3.1.0-jewel.zip. When I use these, it tries to continue but says "Main Version Is Older. FAILED"