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.
My phone is stuck in a bootloop at the white HTC screen. I am able to go to the HBOOT screen but I can't boot into recovery. Also, my phone doesn't show up when I plug it into the computer. It does say FASTBOOT USB though. Also, I have relocked the bootloader. I'm on Hboot 2.27. I have tried flashing the RUU but that hasn't done anything.
At this point I just want my phone working right now. I wouldn't mind losing root and doing a full reset if it meant my phone was working. Also I would like to point out that my phone won't charge its battery. I had to buy a new battery that has a charge on it to use my phone.
Thanks!
So you tried flashing an RUU through bootloader with a higher version than what you were on before, it flashed successfully, and it still won't boot? Did you try flashing the RUU twice? If not, try. If you have already, someone else will have to help you. You can also flash an RUU from your computer using fastboot if it's not working from the bootloader, but I'm not sure what the command would be. Just keep in mind that any device that fastboot recognizes is not at all bricked.
Did you try flashing a recovery in hboot?
Tyler 3 said:
My phone is stuck in a bootloop at the white HTC screen. I am able to go to the HBOOT screen but I can't boot into recovery. Also, my phone doesn't show up when I plug it into the computer. It does say FASTBOOT USB though. Also, I have relocked the bootloader. I'm on Hboot 2.27. I have tried flashing the RUU but that hasn't done anything.
At this point I just want my phone working right now. I wouldn't mind losing root and doing a full reset if it meant my phone was working. Also I would like to point out that my phone won't charge its battery. I had to buy a new battery that has a charge on it to use my phone.
Thanks!
Click to expand...
Click to collapse
Were you using clockwork mod recovery?
You need to flash the RUU twice, and that means that it will probably reboot itself back to hboot and then you have to select bootloader again maybe in order to let it see the RUU and continue, do NOT count this as the second RUU flash, even if it reboots a few times and you restart it or it restarts itself, let it update until you get to the screen that says update successful press power to reboot. Now press power and count that as the first time, let it reboot and then once it boots to the first screen you want to pull the battery and boot to hboot again and say yes to the update again and continue until it says update complete, press power to reboot and then let the phone boot and you can skip through the setup screens without signing in.
Now that the phone is booted, just run the command to unlock the bootloader. Your Unlock_code.bin file should still be in your fastboot folder so it only takes running the command "Fastboot flash unlocktoken Unlock_code.bin" in the command prompt. If your fastboot.exe is located inside the Platform-Tools folder, then back out to where you're looking at the Platform Tools folder, hold shift on your keyboard and right click on the folder, choose open command window here. Then type the command I put in quotes up above, and say yes to the unlock on your phone.
That's why you skipped through the setup earlier, no use in signing in until after you unlock because the unlock wipes the phone clean.
With your bootloader unlocked and phone working like it should, you will want to flash a custom recovery. DO NOT flash the official clockwork mod or you will have the battery problem you're currently experiencing. I would flash amon ra 3.15, because it just works, but if you want to use something else, use Fly Half's recoveries which are posted in the development section and do not update your recovery with rom manager, do not even get close enough to rom manager to let your phone smell the apk, it may get sick.
first off, I'm an idiot with this whole thing and shouldn't be doing it probably. i just don't know enough about it to be playing with expensive phones like this so i understand I deserve whatever i get.
i was running a custom rom on an S-ON phone. i forgot the name of the rom (was made by TEAM COOL or something). But I wanted to unroot and go back to normal stock ROM and download the JB update. First, in the SU app, I did a complete unroot. that did nothing except not let me use the app anymore.
then I tried doing the RUU way of going back, but when it would go to the loading bootloader portion, the usb would disconnect and it would fail with error 171.
so then, and i don't know how i got here, but i went into recovery and did a factory reset and now i have no rom. I have tried installing meanrom but it fails after some line regarding a kernal. my phone won't do anything except boot to the white HTC screen or into the bootloader.
i have no idea what to do, I just want it working at this point.
i've been searching forums like crazy but all the solutions are things I already have done or things that won't work for me.
If you haven't done so yet, you need to relock the bootloader before running ruu. Put your phone in fastboot and using SDK or ADB Tools, type fastboot oem lock
om4 said:
If you haven't done so yet, you need to relock the bootloader before running ruu. Put your phone in fastboot and using SDK or ADB Tools, type fastboot oem lock
Click to expand...
Click to collapse
thank you for your help! however, whenever i do this, it just says < waiting for device >
so i finally got a rom to install--clean rom. that is the one i used to have. but when i reboot, it gets stuck on a black screen and won't go any further.
I had the same thing happen. Had to run a boot.img flash utility i found on another thread elsewhere on xda. The flash utility was updated for jb. If i can locate where i found it then i will get back to you.
Sent from my EVO using Tapatalk 2
I was curious if you ever found that rom or if anybody can help me? The phone is still out of commission. It's been tough to make it through the holidays especially since my laptop was stolen the very next day that all this happened
bump again. I'm assuming the phone is bricked for good if the brightest minds on the subject don't even know
i'm using my dad's old evo 4g for now.
unclefarkus said:
bump again. I'm assuming the phone is bricked for good if the brightest minds on the subject don't even know
i'm using my dad's old evo 4g for now.
Click to expand...
Click to collapse
Have you tried meanbean? It has the boot.img flash tool baked in for s-on, just follow the instructions to the tee in the OP... It's in the Android development thread... Good luck
Sent from my EVO using xda app-developers app
Sounds like you need to flash a Rom that has the s-on installer or fastboot flash the kernel for the Rom you have installed
Most roms come with the kernel installer built in now days. just keep trying to flash em. fyi if your phone turns on , even a little bit , you are not bricked
I am trying to flash meanbean. I wiped the cahes and did factory reset, then flashed the ROM. It's been on "Installing /system..." for about 30 minutes now. Something seems wrong. I'm scared to interrupt it in case that's normal or if interrupting it will break it for good.
Well, I think that might be because my twrp version is really old...2.1.8. I tried updating but had no luck.
Now nothing flashes. It gets to 'verifying partition sizes' then fails. Tried this on several roms that would previously flash, just not work.
unclefarkus said:
Well, I think that might be because my twrp version is really old...2.1.8. I tried updating but had no luck.
Now nothing flashes. It gets to 'verifying partition sizes' then fails. Tried this on several roms that would previously flash, just not work.
Click to expand...
Click to collapse
Update twrp through goomanager, its in the market, then try again.
Sent from my EVO using xda premium
mrlakadaddy said:
Update twrp through goomanager, its in the market, then try again.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
lol how could he do that if he dont have any rom installed...dafuq?
You need to FASTBOOT install it:
Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery TWRP.img
Boatiy said:
lol how could he do that if he dont have any rom installed...dafuq?
You need to FASTBOOT install it:
Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery TWRP.img
Click to expand...
Click to collapse
Don't forget the clear cache commands
Sent from my EVO using xda app-developers app
I have given this a go, however, as I should expect by now, nothing happens.
It says "waiting for device" and that's it
Upon typing "adb devices" nothing shows up.
Furthermore, when I go to Fastboot, Fastbook usb does show up, but I get a message on the computer saying the usb device has malfunctioned.
unclefarkus said:
I have given this a go, however, as I should expect by now, nothing happens.
It says "waiting for device" and that's it
Upon typing "adb devices" nothing shows up.
Furthermore, when I go to Fastboot, Fastbook usb does show up, but I get a message on the computer saying the usb device has malfunctioned.
Click to expand...
Click to collapse
Can you get into bootloader? If so go to the TWRP website and download the hboot zip. Put on external sd card and enter bootloader.
Sent from my EVO using Tapatalk 2
Perhaps what is happening when you try oem lock and get that error is that adb is still running from a prior attempt or because of some other program. Try opening your task manager and ending all processes of adb and other programs that connect to the phone. Then try oem locking again and go from there.
Sent from my EVO using xda premium
I made a little bit of progress!
I determined that Windows 8 was the reason I get the usb malfunctioning message. I obtained a Windows 7 computer and it worked like a charm.
That said, I'm not out of the woods yet.
I relocked the phone using fastboot and then have been attempting to flash a stock RUU now that the usb issue is sorted out.
That seems to work but it gets stuck at "sending....." for as long as 35 minutes. I've tried about 4 times, giving between 20-35 minutes and it won't go beyond sending.
I can at least fastboot now; but the phone is locked. Which is fine; I just want back to stock anyways.
Tampered
Re-locked
S-On
Hboot-1.19.0000
Radio-1.12.11.0809
OpenDSP-v29-1.0.45.0622
eMMC-boot
Aug 9 2012
I flashed the 2.13.651.1 RUU by the way.
Any new advice haha?
I loaded a PJ img via sd card and it's alive and updating to JB OTA right now! Thanks for all the help over the past month folks
..In the past 24 hours I've done a lot to this phone, some good, some bad, some mix guidance that caused my own user error.
I have CWM Recovery 6.0.3.2 on my screen. I was trying to install SkyDragon's 11.1, BUT I did not copy files to the SD card. I forgot, I was not paying attention, I don't know... but I didn't realize thi was an issue until I could not load the files from the CWM menu. so my current setup right now is...
HTC One DEVELOPERS EDITION!
I have CWM on my device. (so I have wiped EVERYTHING)
Sky Dragon attempted and went though all steps.
I can use command prompt to communicate to device SOMETIMES but can't "push the files" through. but I can communite to device (it's detected which mean adb is working)
I can't turn on phone.
Fastboot is accessable.
I have done the HTC developers website
These guides are not working for me so I thought it couldn't hurt to ask... Let e know what else I need to share...
UPDATE: when I attempted to run Dev RUU, it says it will upgrade this version. Image Version L: 1.29.1540.17
to 1.29.1540.16
was downloading brightstar for 3.22.1540.1 and still same.
mcooke said:
..In the past 24 hours I've done a lot to this phone, some good, some bad, some mix guidance that caused my own user error.
I have CWM Recovery 6.0.3.2 on my screen. I was trying to install SkyDragon's 11.1, BUT I did not copy files to the SD card. I forgot, I was not paying attention, I don't know... but I didn't realize thi was an issue until I could not load the files from the CWM menu. so my current setup right now is...
HTC One DEVELOPERS EDITION!
I have CWM on my device. (so I have wiped EVERYTHING)
Sky Dragon attempted and went though all steps.
I can use command prompt to communicate to device SOMETIMES but can't "push the files" through. but I can communite to device (it's detected which mean adb is working)
I can't turn on phone.
Fastboot is accessable.
I have done the HTC developers website
These guides are not working for me so I thought it couldn't hurt to ask... Let e know what else I need to share...
UPDATE: when I attempted to run Dev RUU, it says it will upgrade this version. Image Version L: 1.29.1540.17
to 1.29.1540.16
was downloading brightstar for 3.22.1540.1 and still same.
Click to expand...
Click to collapse
still the same what ? ..did you relock the bootloader to run the RUU ?
fastboot oem lock
then fastboot reboot-bootloader
then run the RUU
clsA said:
still the same what ? ..did you relock the bootloader to run the RUU ?
fastboot oem lock
then fastboot reboot-bootloader
then run the RUU
Click to expand...
Click to collapse
cmd 1: Locked
cmd 2: Okay!
3: trying now... nvm last reply
Help,
i wanted to try different roms on my HTC One (M7). After i loaded a slim rom, i had locked the bootloader and it started boot looping. Wiped my phone clean, now i can't flash or push any file on my phone. What can i do to fix this?
shado2us said:
Help,
i wanted to try different roms on my HTC One (M7). After i loaded a slim rom, i had locked the bootloader and it started boot looping. Wiped my phone clean, now i can't flash or push any file on my phone. What can i do to fix this?
Click to expand...
Click to collapse
Sounds like a bit of a pickle. I'll need a bit more info to make sure I point you in the right direction.
Which version (carrier) of the M7 is it?
Do you still have a custom recovery? Which one?
S-On?
What version of the software did you have on the phone before modifying?
PC/Mac/Linux? Which version?
Do you have working adb and fastboot drivers?
Have you re-unlocked the bootloader? (You should if you want to do more custom stuff)
Are you going back to Sense or a non Sense based rom?
Curious as to why you would relock the bootloader unless you had planned on returning to stock with an RUU...?
es0tericcha0s said:
Sounds like a bit of a pickle. I'll need a bit more info to make sure I point you in the right direction.
Which version (carrier) of the M7 is it?
Do you still have a custom recovery? Which one?
S-On?
What version of the software did you have on the phone before modifying?
PC/Mac/Linux? Which version?
Do you have working adb and fastboot drivers?
Have you re-unlocked the bootloader? (You should if you want to do more custom stuff)
Are you going back to Sense or a non Sense based rom?
Curious as to why you would relock the bootloader unless you had planned on returning to stock with an RUU...?
Click to expand...
Click to collapse
i am using Straight Talk
twrp
S-off
stock 4.4.2
pc win7
yes
either
it happened by itself, didn't want to go back to lock
shado2us said:
i am using Straight Talk
twrp
S-off
stock 4.4.2
pc win7
yes
either
it happened by itself, didn't want to go back to lock
Click to expand...
Click to collapse
Ok, so far so good. however I'm not clear if the "yes" answer is for the working adb / fastboot drivers or if you have re-unlocked the bootloader. You're using ST, but is the phone originally an ATT, T-mo, or International version? And does the PC recognize when you plug in the phone while in TWRP? If so, are there any error messages like USB Device Not Recognized or anything of the sort?
es0tericcha0s said:
Ok, so far so good. however I'm not clear if the "yes" answer is for the working adb / fastboot drivers or if you have re-unlocked the bootloader. You're using ST, but is the phone originally an ATT, T-mo, or International version? And does the PC recognize when you plug in the phone while in TWRP? If so, are there any error messages like USB Device Not Recognized or anything of the sort?
Click to expand...
Click to collapse
trying to re-unlock
originally international
pc does recognize
when i try to do recovery:
target reported max download size of 1526722560 bytes
sending 'recovery' (9944 KB)...
OKAY [ 1.180s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.233s
when i try to fastboot flash, adb push and adb sideload other files:
error: device not found
Ok, so seems like there is a couple things going on. First off, if you are trying to unlock the bootloader, then why are you trying to send recovery? And secondly, sounds like you are having some issues with drivers perhaps. When you go to your Device Manager, do you have any yellow exclamation points for HTC? Fastboot options only work in bootloader and adb will only work in recovery or booted into the OS. Here's what we should do, check drivers, re-unlock the bootloader, fastboot flash the latest recovery, then make sure adb is working to either sideload a rom or push one to your internal storage.
es0tericcha0s said:
Ok, so seems like there is a couple things going on. First off, if you are trying to unlock the bootloader, then why are you trying to send recovery? And secondly, sounds like you are having some issues with drivers perhaps. When you go to your Device Manager, do you have any yellow exclamation points for HTC? Fastboot options only work in bootloader and adb will only work in recovery or booted into the OS. Here's what we should do, check drivers, re-unlock the bootloader, fastboot flash the latest recovery, then make sure adb is working to either sideload a rom or push one to your internal storage.
Click to expand...
Click to collapse
i have no kernal/rom on my phone. fastboot, adb and sideload doesn't work to put files on my phone. just got throught trying to unlock with my wifes macbook air and still wont unlock. i am getting very frustrated with all of this not working.
shado2us said:
i have no kernal/rom on my phone. fastboot, adb and sideload doesn't work to put files on my phone. just got throught trying to unlock with my wifes macbook air and still wont unlock. i am getting very frustrated with all of this not working.
Click to expand...
Click to collapse
If it's not working on the PC then it's an issue with drivers, cord, or ports. Most likely drivers. You never mentioned what your Device Manager says when you plug the phone in. Step number 1 was to check drivers, yet you didn't mention trying to troubleshoot that or anything of the sort.
es0tericcha0s said:
If it's not working on the PC then it's an issue with drivers, cord, or ports. Most likely drivers. You never mentioned what your Device Manager says when you plug the phone in. Step number 1 was to check drivers, yet you didn't mention trying to troubleshoot that or anything of the sort.
Click to expand...
Click to collapse
it shows
android usb devices
my htc
shado2us said:
it shows
android usb devices
my htc
Click to expand...
Click to collapse
In what mode on the phone are you that it shows this and are there any yellow exclamation points? Are you using a USB 2.0 or 3.0 port? 2.0 is recommended. When you are in the bootloader and choose fastboot, does it change to fastboot usb on the phone?
es0tericcha0s said:
In what mode on the phone are you that it shows this and are there any yellow exclamation points? Are you using a USB 2.0 or 3.0 port? 2.0 is recommended. When you are in the bootloader and choose fastboot, does it change to fastboot usb on the phone?
Click to expand...
Click to collapse
in fastboot mode drivers are good; in recovery mode the driver is under other devices named one and that is yellow with error code 28. my ports are 2.0. yes it does change
shado2us said:
in fastboot mode drivers are good; in recovery mode the driver is under other devices named one and that is yellow with error code 28. my ports are 2.0. yes it does change
Click to expand...
Click to collapse
Ok, well if fastboot drivers are working, then what trouble are you having doing the unlock again? Just gotta use the unlock.bin file you got from HTC. But your adb drivers are messed up in recovery so that will prevent you from being able to adb push or sideload. This is not an uncommon issue with HTCs in recovery on Windows. See if the drivers from here: http://forum.xda-developers.com/showthread.php?t=2232799 will get you back on track. If that doesn't work, try the Universal Naked Driver.
es0tericcha0s said:
Ok, well if fastboot drivers are working, then what trouble are you having doing the unlock again? Just gotta use the unlock.bin file you got from HTC. But your adb drivers are messed up in recovery so that will prevent you from being able to adb push or sideload. This is not an uncommon issue with HTCs in recovery on Windows. See if the drivers from here: http://forum.xda-developers.com/showthread.php?t=2232799 will get you back on track. If that doesn't work, try the Universal Naked Driver.
Click to expand...
Click to collapse
nope, nothing. when i go to fastboot flash unlocktoken Unlock_code.bin, it does not go to the disclaimer, nothing happens. the universal naked drivers worked for adb.
shado2us said:
nope, nothing. when i go to fastboot flash unlocktoken Unlock_code.bin, it does not go to the disclaimer, nothing happens. the universal naked drivers worked for adb.
Click to expand...
Click to collapse
Well something has to happen, as in, what does it say on the CMD prompt when you enter the command? And if the drivers work for adb, then you wouldn't see the exclamation point in your device manager and you would be able to connect via adb in recovery.
ok, now I am at stock again. Not going to install slim roms unless I have all the files I need.
Sent from my HTC One using xda app-developers app
Glad you are back up again! Did you get an RUU to return to stock then? But yea, as a general rule of thumb, I never modify a device that I don't have the files and guide on how to return to stock.