Related
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
While you're at bootloader, connect USB and then flash a stock RUU.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Thanks for the reply. Will i lose s-off with this?
Tones1971 said:
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
Click to expand...
Click to collapse
You didn't say what version of the Evo 3D you have (CDMA or GSM) or what bootloader is installed, but if it's a Sprint CDMA model I would recommend flashing the Sprint ICS RUU.exe from Windows after putting the phone into fastboot mode in the bootloader. You may have to relock the bootloader with the "fastboot oem lock" command first if it shows "***UNLOCKED***" at the top of the screen.
That will fix a lot of problems, especially when the phone is in an indeterminate state. After flashing the RUU you can HTC unlock, flash a custom recovery and then root the stock ROM or flash a rooted ROM.
ramjet73
Sorry it is a UK GSM (Europe). I have revolutionary bootloader installed. Got an RUU to try now thanks.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Tones1971 said:
Thanks for the reply. Will i lose s-off with this?
Click to expand...
Click to collapse
^^^^ He got it first with the short version.
No, you won't lose S-OFF and won't need to relock the bootloader first if that's your current status.
And if it's a GSM model everything still applies, you just need a different RUU, which you already have.
ramjet73
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Tones1971 said:
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Click to expand...
Click to collapse
Error 170 means that the RUU utility can't find the phone. There's a readme.doc for running the RUU here, and the error codes are towards the end of that.
Are you putting it into "fastboot" mode in the bootloader, which should change to "fastboot usb" when it is connected to a computer? You also need to have the HTC USB drivers active, which can be accomplished by installing HTC Sync.
ramjet73
Tones1971 said:
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Click to expand...
Click to collapse
adb push into a bootlooping phone?
do you have the drivers for the phone? (if not download and install HTC Sync as they come with it)
did you try flashing a custom recovery img through fastboot? (go to bootloader select fastboot, connect USB, type "fastboot flash recovery nameOfYourRecoveryImg.img")
Yeah have tried installing custom recovery through fast boot again, and im in fastboot ok when trying to run the RUU. Also have HTC Sync installed from when i had the phone.. Drivers seemed to be ok as i was able to install the custom recovery with adb, alhough i still got bootloop after that.
Ive a few other things to try when i get home from work. Im sure it shouldnt be too difficult to resolve. Hopefully anyway.
Well this isnt going smoothly at all. Used another PC and was able to get the RUU to run.
However it now comes up with Error 131 Customer ID problem. The RUU was for HTC Europe (non branded). The phone was sim free. When i posted months back my cid was HTC_001. I checked it here: http://forum.xda-developers.com/showpost.php?p=22394863&postcount=172
However now when i get my CID it is showing as CID0202. Any way i can get an RUU to install? Any idea how a CID could change?
EDIT: noticed i used a different command last time.
fastboot getvar cid shows CID0202
adb shell getprop ro.cid now shows device not found (previously showed CID_001)
Thats typing both commands in same window, one after the other. One gets CID0202, the other device not found???
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
dessolator666 said:
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
Click to expand...
Click to collapse
Thanks for this. Ill see if i can find anything else out about it. So saves running the RUU exe and no cid check done then?
Need to bump this as im not getting anywhere. No RUU's will install, error 31 customer error. Have flashed recovery via ADB and through PG86IMG.ZIP, but still cant get in to recovery as it just continually reboots.
S-OFF with revolutionary. Anybody any ideas please?
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Tones1971 said:
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Click to expand...
Click to collapse
You need to stop cross posting in the d3rp Q&A thread and your own thread if you want more help. Cross-posting is stongly discouraged on XDA and it's really confusing when you are asking for help in one thread while getting different advice in another.
It sounds to me like all the CID changes on your phone have left it in an indeterminate state and I'm not sure at this point what is the correct CID and RUU for your model. If you could detemine that, set the CID correctly and flash the right RUU the phone should work, but it might be too late if you have in fact been flashing firmware that doesn't match your phone because the right RUU may not back that out properly.
That's all I can offer at this point, but since I don't know the history of your phone and how it got the various CID's you have reported, you will probably be the one that needs to figure it out.
ramjet73
So... was running the MikVirgin ICS rom on my S-on 1.50 Evo 3d. Was going to bring it back to scratch and go through the S-Off process to run something better. I have Revolutionary 4.0.1.4 installed and fastboot on my computer. For the life of me, I cannot get the phone to accept anything now :\ Trying to run the RUU gives me the 170 error and any rom I try loops at the boot loader (not the white HTC screen, but the boot image for the rom).
Help would be appreciated
bl4ckllama said:
So... was running the MikVirgin ICS rom on my S-on 1.50 Evo 3d. Was going to bring it back to scratch and go through the S-Off process to run something better. I have Revolutionary 4.0.1.4 installed and fastboot on my computer. For the life of me, I cannot get the phone to accept anything now :\ Trying to run the RUU gives me the 170 error and any rom I try loops at the boot loader (not the white HTC screen, but the boot image for the rom).
Help would be appreciated
Click to expand...
Click to collapse
The 170 error is normally a USB connectivity issue caused by a bad USB cable or Windows driver problems. You also need to have your bootloader relocked if you are S-ON.
See this post for RUU.exe troubleshooting steps. If you planning to get S-OFF you might be interested in trying my guide.
ramjet73
ramjet73 said:
The 170 error is normally a USB connectivity issue caused by a bad USB cable or Windows driver problems. You also need to have your bootloader relocked if you are S-ON.
See this post for RUU.exe troubleshooting steps. If you planning to get S-OFF you might be interested in trying my guide.
ramjet73
Click to expand...
Click to collapse
Yeah, I've tried it in Relocked status, and still no go. Even under fastboot USB (and I made sure the drivers are there) it won't recognize the phone is attached. I've factory wiped and I'm going to try and re-install the Mikvirgin rom again.
bl4ckllama said:
Yeah, I've tried it in Relocked status, and still no go. Even under fastboot USB (and I made sure the drivers are there) it won't recognize the phone is attached. I've factory wiped and I'm going to try and re-install the Mikvirgin rom again.
Click to expand...
Click to collapse
Have you tried another cable and/or PC?
ramjet73
I had a similar (not identical) problem, and I solved it by pulling the zip out of the exe by letting it run without plugging the phone in and then looking through the folders in my temp folder until I found rom.zip. Renamed it PG86IMG, put it on my sd card, re locked with fastboot, and boom! Phone rescued.
Sent from my Nexus 7 using xda premium
Was finally able to get it loaded with an ICS rom after doing a factory reset, installing the rom, and then manually installing the boot file through fastboot. Maybe I'll try again tomorrow, doing the s-off procedure first Thanks for the input all!
Hello. So I've tried multiple times flashing ROMs to my device, and have always had problems somewhere along the line. The furthest I got was successfully flashing this ROM, but it ended up in a boot loop. I believed it was due to my device being S-ON, even though I've successfully rooted and unlocked my bootloader via HTCdev and thus I've been attempting to get S-OFF. I tried JuopunutBear but got an error message related to checking my adb and fastboot drivers (Which I'm fairly sure are up to date and working) and I think the problem is I am on HBOOT 1.57. I've been attempting to downgrade using this guide (Which uses Revolutionary to get S-OFF in which case I wouldn't need JuopunutBear). I only got a bit of the way in, however, before I got stuck. After relocking my device it tells you to put the RUU zip on your device, but my computer isn't detecting my device and I'm stuck in the bootloader. I've tried shutting it off, trying all the options in the bootloader, taking out the battery, entering commands into adb, and probably some other things I've forgot, but I'm still stuck on the bootloader and my device isn't detected at all on my computer (Either in command prompt or in the explorer window).
Essentially what I'm asking here is:
How do I get my phone unstuck from bootloader?
Do I need S-OFF to be able to flash ROMs?
If I don't need S-OFF, what was I doing wrong? Should I try a different ROM?
And I suppose I may as well ask if that's a worthwhile ROM. I want something that optimizes my device and allows for custom themes, but otherwise I'm not too picky.
Specs:
Windows Vista (With ADB and fastboot, as well as HTC Sync and other phone drivers. Essentially I think I have all the software I'd need installed.)
HTC EVO 3D CDMA with Virgin Mobile as the carrier.
HTCdev unlocked bootloader
S-ON
HBOOT 1.57
Stock ROM
4ext recovery
Any and all help would be greatly appreciated!
(Also I apologize if I didn't give all the information needed or if I posted this in the incorrect spot. I figured this would be the most appropriate spot since although I have issues with specific processes it's also a fairly general request for help.)
UPDATE: I tried re-unlocking my phone using HTCdev so I'm no longer stuck in bootloader. I'm going to be trying the HBOOT Downgrade Toolkit guide again sometime today or tomorrow to see if I can get it working. I think one of the problems before was that I didn't put the RUU on the sdcard beforehand and then my device wasn't being recognized so i couldn't put it there then. If I put it on beforehand I should be able to update successfully and get past the step I was stuck on before.
If you're son u can only flash sence ROMs.
Sent from my PG86100 using xda app-developers app
cj_302 said:
If you're son u can only flash sence ROMs.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Er, I'm not quite sure what you're saying here.
UPDATE: I tried re-unlocking my phone using HTCdev so I'm no longer stuck in bootloader. I'm going to be trying the HBOOT Downgrade Toolkit guide again sometime today or tomorrow to see if I can get it working. I think one of the problems before was that I didn't put the RUU on the sdcard beforehand and then my device wasn't being recognized so i couldn't put it there then. If I put it on beforehand I should be able to update successfully and get past the step I was stuck on before.
It will be your hboot causing the problems.
Most recoveries allow you to mount usb storage so you can use that option to connect to your pc and move the ruu across without removing your sdcard etc.
Download G Cloud Backup for Android, up to 8 GB Free.Use this code: [KWLYRO] at signup and we'll both earn space: https://play.google.com/store/apps/details?id=com.genie9.gcloudbackup
Semi-noob here, would appreciate any help!
S-Off using revone, flashed CWM, and then ROM'd. Found an issue with the phone (wireless charger not working), so need to return to stock before bringing to Verizon. Used adb to S-On, and now, I am STUCK in Fastboot (or is it called Hboot?)!
None of the "options in Fastboot do anything (Bootloader, Reboot, Reboot Bootloader, Factory Reset). I can't get anywhere past Fastboot!
I think my problem was that I did not flash the stock ROM first, before S-on again. The phone no longer goes into Bootloader, so I don't know how to flash a ROM at this point.
Any help would be majorly appreciated! Thank you, oh wise ones...
geeDoh said:
Semi-noob here, would appreciate any help!
S-Off using revone, flashed CWM, and then ROM'd. Found an issue with the phone (wireless charger not working), so need to return to stock before bringing to Verizon. Used adb to S-On, and now, I am STUCK in Fastboot (or is it called Hboot?)!
None of the "options in Fastboot do anything (Bootloader, Reboot, Reboot Bootloader, Factory Reset). I can't get anywhere past Fastboot!
I think my problem was that I did not flash the stock ROM first, before S-on again. The phone no longer goes into Bootloader, so I don't know how to flash a ROM at this point.
Any help would be majorly appreciated! Thank you, oh wise ones...
Click to expand...
Click to collapse
The good news is, if you really are stuck in fastboot, you can still use adb/fastboot commands to get your phone working again. There is an important distinction between fastboot and hboot, though: fastboot is basically the bootloader's "debug" mode, while hboot is the regular bootloader mode. You won't be able to do much if your bootloader says "hboot" above the available options, but if it says "fastboot" or "fastboot usb" you're fine.
You should try to get s-off again (assuming you haven't relocked your bootloader) either via revone or facepalm, then flash a stock rom and proceed from there.
Clarification: if you have relocked your bootloader, unlock, then get s-off.
Used adb to S-On? Meaning what exactly? Did you lock beforehand?
I currently have S-on. I used revone's method to S-off.
I think the problem is that I have relocked the bootloader (phone shows LOCKED) with a custom ROM installed. I think I should have flashed a stock ROM before relocking. Would this have caused the problem I'm having?
I am not sure how to get S-off again, because I am stuck on the FASTBOOT. Selecting Bootloader/Reboot/Reboot Bootloader just returns me to the same screen. When I try to enter any line items (in Terminal), adb says there are no devices connected (this is probably due to the fact that my phone no longer boots to the homescreen). Any suggestions of how to get S-off again??
Thanks...
What method did you use for S-ON? There are guides here that lay out every step needed to return to stock.
Also when in fastboot, you need to use fastboot, not adb. Type in fastboot devices. Does your device ID show?
I would suggest trying to run the RUU. Although it may not work depending on HBOOT version and the fact you are now S-ON.
Can you boot into Recovery? If so, is there a ROM still on the phone? If so, try flashing it...
geeDoh said:
I currently have S-on. I used revone's method to S-off.
I think the problem is that I have relocked the bootloader (phone shows LOCKED) with a custom ROM installed. I think I should have flashed a stock ROM before relocking. Would this have caused the problem I'm having?
I am not sure how to get S-off again, because I am stuck on the FASTBOOT. Selecting Bootloader/Reboot/Reboot Bootloader just returns me to the same screen. When I try to enter any line items (in Terminal), adb says there are no devices connected (this is probably due to the fact that my phone no longer boots to the homescreen). Any suggestions of how to get S-off again??
Thanks...
Click to expand...
Click to collapse
Does the unit show up in device manager? You may need to install a driver.
Phaded said:
What method did you use for S-ON? There are guides here that lay out every step needed to return to stock.
Also when in fastboot, you need to use fastboot, not adb. Type in fastboot devices. Does your device ID show?
I would suggest trying to run the RUU. Although it may not work depending on HBOOT version and the fact you are now S-ON.
Can you boot into Recovery? If so, is there a ROM still on the phone? If so, try flashing it...
Click to expand...
Click to collapse
Oh, using Fastboot gave me my device ID. What can I do now??
I can't get into Recovery from Fastboot USB. The option for Bootloader and Reboot Bootloader are there, but selecting them just returns me to Fastboot USB. I assume this is because I am already S-On again...?
geeDoh said:
Oh, using Fastboot gave me my device ID. What can I do now??
I can't get into Recovery from Fastboot USB. The option for Bootloader and Reboot Bootloader are there, but selecting them just returns me to Fastboot USB. I assume this is because I am already S-On again...?
Click to expand...
Click to collapse
Select bootloader, then recovery. The menus look the same, but they are different.
If you can boot into recovery, what is it? Stock or custom?
Phaded said:
Select bootloader, then recovery. The menus look the same, but they are different.
If you can boot into recovery, what is it? Stock or custom?
Click to expand...
Click to collapse
When I select Bootloader -> Recovery, the HTC screen flashes, then I'm returned to Fastboot USB.
geeDoh said:
When I select Bootloader -> Recovery, the HTC screen flashes, then I'm returned to Fastboot USB.
Click to expand...
Click to collapse
That's because you have unsigned boot.img and/or recovery and relocked the device.
You need to RUU or unlock again to boot to anything.
Any tips on how to unlock again? (and once I am unlocked, i assume I need to load Recovery, and from there, flash a stock ROM?)
geeDoh said:
Any tips on how to unlock again? (and once I am unlocked, i assume I need to load Recovery, and from there, flash a stock ROM?)
Click to expand...
Click to collapse
Run Moonshine.
If that fails, RUU to stock.
You didn't happen to make an unlock_code.bin with htc did you?
No, i didn't. Not even sure what that is...haha...
I'm going to run RUU, and hope that works! Thanks for everyones input...
still no luck! =T
So, I've tried running RUU (this is the RUU file I'm using: RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed), but after it runs for a while (it says it is erasing data, then sending to the phone),
RUU says I am currently on 2.06, so is this the correct RUU file?
Another option for me, other than putting the phone back to stock, is for me to completely brick it. I tried unplugging and powering off the phone while RUU was running, but it still comes back to Fastboot. Suggestions?
Thanks again....
geeDoh said:
So, I've tried running RUU (this is the RUU file I'm using: RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed), but after it runs for a while (it says it is erasing data, then sending to the phone),
RUU says I am currently on 2.06, so is this the correct RUU file?
Another option for me, other than putting the phone back to stock, is for me to completely brick it. I tried unplugging and powering off the phone while RUU was running, but it still comes back to Fastboot. Suggestions?
Thanks again....
Click to expand...
Click to collapse
Just run the RUU. There is only one RUU. You are on 2.06, that's why it tells you that. Let the whole thing run.
You cannot downgrade via RUU. You need to unlock the phone, s-off it (facepalm should suffice) then you can RUU back to 1.15 if you choose.
beaups said:
You cannot downgrade via RUU. You need to unlock the phone, s-off it (facepalm should suffice) then you can RUU back to 1.15 if you choose.
Click to expand...
Click to collapse
Ah forgot he went back to S-On.
Phaded said:
Ah forgot he went back to S-On.
Click to expand...
Click to collapse
I have the same problem. Since it was relocked, the htc dev site can't give the bin file to unlock it again. So I'm stuck in fastboot usb mode and I can't do anything about it. If only I can unlock it again, then I can move on from there.
okyere said:
I have the same problem. Since it was relocked, the htc dev site can't give the bin file to unlock it again. So I'm stuck in fastboot usb mode and I can't do anything about it. If only I can unlock it again, then I can move on from there.
Click to expand...
Click to collapse
Still have the token? Or the email that it got sent in?
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.