adb devices wont show my evo 3d no matter what i tried. usb debuggin checked. running win7 64. reinstalled drivers, sdk, searched and tried almost every method but no luck.
another thing is fastboot shows my device as unlocked, s-off. however, root checker says its not rooted. i dont have any recovery installed because i flashed a stock ruu to try and fix my wifi. which still doesnt work.
ready to give up trying....
any help is appreciated.
eddyz said:
adb devices wont show my evo 3d no matter what i tried. usb debuggin checked. running win7 64. reinstalled drivers, sdk, searched and tried almost every method but no luck.
another thing is fastboot shows my device as unlocked, s-off. however, root checker says its not rooted. i dont have any recovery installed because i flashed a stock ruu to try and fix my wifi. which still doesnt work.
ready to give up trying....
any help is appreciated.
Click to expand...
Click to collapse
S-off and Root are 2 different things. Can't help with the adb problem, unless you want to ditch Windows for Linux. Also, this may seem obvious, but strange things get overlooked sometimes. Have you tried rebooting your router, and verifying that your router itself is not the culprit?
Sent from my PG86100 using Tapatalk 2
eddyz said:
adb devices wont show my evo 3d no matter what i tried. usb debuggin checked. running win7 64. reinstalled drivers, sdk, searched and tried almost every method but no luck.
another thing is fastboot shows my device as unlocked, s-off. however, root checker says its not rooted. i dont have any recovery installed because i flashed a stock ruu to try and fix my wifi. which still doesnt work.
ready to give up trying....
any help is appreciated.
Click to expand...
Click to collapse
Don't give up yet.
Did you turn on debugging in the developer options of system settings for whatever ROM you have installed when you try to run ADB? That's required for the ADB commands to work.
When you say "fastboot" shows the unlocked and S-OFF status you probably mean the bootloader display. If you can get to that, select "fastboot" and connect the phone to your PC and it should change to "fastboot usb". Then issue the "fastboot devices" command from the directory where ADB is installed and it should return the serial number of your device. If it does, your drivers and phone connectivity are fine.
ramjet73
ramjet73 said:
When you say "fastboot" shows the unlocked and S-OFF status you probably mean the bootloader display. If you can get to that, select "fastboot" and connect the phone to your PC and it should change to "fastboot usb". Then issue the "fastboot devices" command from the directory where ADB is installed and it should return the serial number of your device. If it does, your drivers and phone connectivity are fine.
ramjet73
Click to expand...
Click to collapse
yeah, i tried fastboot devices and still nothing shows up.
I dont if you tried this, maybe your cord is bad. You could try swapping out cords. Again not sure, if your led pops up when you hook your phone up to your PC. If it does, does your PC recognize your phones sdcard? It may also help to flash a recovery and gain root. It couldnt hurt to try.
Jsparta26 said:
I dont if you tried this, maybe your cord is bad. You could try swapping out cords. Again not sure, if your led pops up when you hook your phone up to your PC. If it does, does your PC recognize your phones sdcard? It may also help to flash a recovery and gain root. It couldnt hurt to try.
Click to expand...
Click to collapse
yes, it can recognize the sdcard. the cord is fine because i use it for my samsung as well.
i tried to google a pg86img recovery file but couldnt find any. anyone got like cwm or 4ext in pg86img.zip format to link me?
eddyz said:
y anyone got like cwm or 4ext in pg86img.zip format to link me?
Click to expand...
Click to collapse
You can get 4EXT or TWRP from this post.
ramjet73
ramjet73 said:
You can get 4EXT or TWRP from this post.
ramjet73
Click to expand...
Click to collapse
tried both 4ext and twrp. in bootloader when reading the pg86img file, it says "model id error"
eddyz said:
tried both 4ext and twrp. in bootloader when reading the pg86img file, it says "model id error"
Click to expand...
Click to collapse
What model of the Evo 3D do you have?
ramjet73
ramjet73 said:
What model of the Evo 3D do you have?
ramjet73
Click to expand...
Click to collapse
its the gsm version
eddyz said:
its the gsm version
Click to expand...
Click to collapse
Have you tried looking for the gsm version?
eddyz said:
its the gsm version
Click to expand...
Click to collapse
Which GSM version? If you are trying to flash an RUU it makes a difference.
ramjet73
ramjet73 said:
Which GSM version? If you are trying to flash an RUU it makes a difference.
ramjet73
Click to expand...
Click to collapse
i think the european version
eddyz said:
i think the european version
Click to expand...
Click to collapse
so no matter whatr i try, abd or fastboot will not recognise my device.
i boot my device in fastboot mode. plug in the usb and it shows "fastboot sub".
but fastboot devices doesnt show anything.
can anyone help?
eddyz said:
so no matter whatr i try, abd or fastboot will not recognise my device.
i boot my device in fastboot mode. plug in the usb and it shows "fastboot sub".
but fastboot devices doesnt show anything.
can anyone help?
Click to expand...
Click to collapse
anyone got any ideas on how to tackle this?
Related
I got a 3d from a friend who says he was trying to root it. He did the htc unlock I think. The bootloader said unlocked, I relocked it with the relock oem command on cmd. I have tried a few different IMG and exe files and none will work. does anyone have any ideas as to what else I could try? Ive googled and all I keep getting is more downloads for ruu.
Any help will be greatly appreciated.
gamy2121 said:
I got a 3d from a friend who says he was trying to root it. He did the htc unlock I think. The bootloader said unlocked, I relocked it with the relock oem command on cmd. I have tried a few different IMG and exe files and none will work. does anyone have any ideas as to what else I could try? Ive googled and all I keep getting is more downloads for ruu.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
This article tells you how to read and set the CID. It's written for the GSM version, but the "readcid" command seems to work on my CDMA version and has a value of "SPCS_001". If that's not what your phone shows it may be why the RUU's aren't working.
I didn't try the "writecid" command since I don't need to change mine.
ramjet73
ramjet73 said:
This article tells you how to read and set the CID. It's written for the GSM version, but the "readcid" command seems to work on my CDMA version and has a value of "SPCS_001". If that's not what your phone shows it may be why the RUU's aren't working.
I didn't try the "writecid" command since I don't need to change mine.
ramjet73
Click to expand...
Click to collapse
I just did the readcid and it says I have SPCS_001
gamy2121 said:
I just did the readcid and it says I have SPCS_001
Click to expand...
Click to collapse
Are you putting your phone into "fastboot USB" mode in the bootloader before running the RUU.exe from Windows? It's supposed to work if you're booted into Android and just reboot into the bootloader on its own, but sometimes that doesn't work.
Also, try the "fastboot devices" command from the PC directory with ADB before running the RUU.exe and make sure you get a serial number that starts with "HT" as a response.
ramjet73
ramjet73 said:
Are you putting your phone into "fastboot USB" mode in the bootloader before running the RUU.exe from Windows? It's supposed to work if you're booted into Android and just reboot into the bootloader on its own, but sometimes that doesn't work.
Also, try the "fastboot devices" command from the PC directory with ADB before running the RUU.exe and make sure you get a serial number that starts with "HT" as a response.
ramjet73
Click to expand...
Click to collapse
Yes to the fastboot usb - Thats all I can do if I try to boot up it just gets stuck at the white htc screen.
edit: this is what Im getting on the fastboot devices --- SH19THX01975 fastboot
gamy2121 said:
Yes to the fastboot usb - Thats all I can do if I try to boot up it just gets stuck at the white htc screen.
edit: this is what Im getting on the fastboot devices --- SH19THX01975 fastboot
Click to expand...
Click to collapse
I don't recognize that serial number as an Evo 3D. I have two and their serials both start with "HT".
Maybe someone else can help with that.
ramjet73
ramjet73 said:
I don't recognize that serial number as an Evo 3D. I have two and their serials both start with "HT".
Maybe someone else can help with that.
ramjet73
Click to expand...
Click to collapse
Thanks for your help, I did notice on the phone one of the errors was something about hoot being older.
SOLVED*****
Heres what I had to do incase some else ever has this problem.
IDK what the previous owner did but I had to start the RUU on the PC then go into the temp folder and go into the ROM folder with 7zip and take the stock recovery.img and fastboot flash it through cmd. Then I ran the RUU and the phone finally took it.
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"
Hello all, I've just recently recovered my DNA back to stock from a botched ROM install on the 3.06 software. Prior to running the RUU, I used Rumrunner to unlock my bootloader to put CWM on as my recovery. Then I had to re-lock it to run the RUU. Now I'm stuck at re-unlocking it. The HTCdev site is giving me a MID not allowed error and I'm thinking it has something to do with the fact that I used Rumrunner? Call me stupid, the DNA is still relatively new to me. Thank you!!
You shouldn't need to relock it to RUU. The RUU will overwrite your recovery with stock but the bootloader should remain unlocked (and s-off if you did that as well). At this point you should be able to just run rumrunner again to unlock the bootloader and then you can flash a custom recovery and go from there.
Sent from my HTC6435LVW using xda app-developers app
iissmart said:
You shouldn't need to relock it to RUU. The RUU will overwrite your recovery with stock but the bootloader should remain unlocked (and s-off if you did that as well). At this point you should be able to just run rumrunner again to unlock the bootloader and then you can flash a custom recovery and go from there.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Tried doing Rumrunner again, Getting this error, "ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)" I've uninstalled the drivers via device manager, let windows 7 reinstall them and installed/uninstalled HTCsync with no luck.
Edit: Nevermind, tried a different cable. Hate it when that happens.
Edit 2: Rumrunner must have failed, device still relocked.
Hubblemuffin said:
Tried doing Rumrunner again, Getting this error, "ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)" I've uninstalled the drivers via device manager, let windows 7 reinstall them and installed/uninstalled HTCsync with no luck.
Click to expand...
Click to collapse
Does 'adb devices' show your serial number? Did you enable debugging in the developer options?
iissmart said:
Does 'adb devices' show your serial number? Did you enable debugging in the developer options?
Click to expand...
Click to collapse
I don't even see ADB devices in device manager. Just Android USB Devices.
Hubblemuffin said:
I don't even see ADB devices in device manager. Just Android USB Devices.
Click to expand...
Click to collapse
ADB Devices is a command issued from the command prompt. It should return the S/N of the device connected. If there is no response the drivers are not installed on the PC. If you are using Win 8 or 8.1 you will have issues
RLGL said:
ADB Devices is a command issued from the command prompt. It should return the S/N of the device connected. If there is no response the drivers are not installed on the PC. If you are using Win 8 or 8.1 you will have issues
Click to expand...
Click to collapse
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Hubblemuffin said:
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Click to expand...
Click to collapse
Hı, have you find out a solution to this one ?
I am struggling with a similar situation:
http://forum.xda-developers.com/showthread.php?p=51140962
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Hubblemuffin said:
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I have heard if you flash a new hboot the relocked text will go away, but I haven't had this issue myself so I can't personally confirm it. I do recommend updating your hboot and radio, though, for other reasons like better radio signal.
iissmart said:
I have heard if you flash a new hboot the relocked text will go away, but I haven't had this issue myself so I can't personally confirm it. I do recommend updating your hboot and radio, though, for other reasons like better radio signal.
Click to expand...
Click to collapse
Updating the hboot and radio seems a little daunting. Definitely something I want to look in to once I can figure out how to get a ROM on this without calling a mulligan and starting from scratch again.
Hubblemuffin said:
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Click to expand...
Click to collapse
Adb is universal to all android devices, I highly recommend getting used to it if you plan on rooting future devices, the only thing native to HTC is the S-OFF portion of eMMC
Hubblemuffin said:
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Are you S-OFF? If so issue this command in fastboot:
fastboot oem writecid 22222222
Go to htcdev.com and then it will allow you to unlock the bootloader also make sure you have 8 2's in the command.
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.
I've posted the RUU & firmware in the RUU thread, need testers that are already updated for stock rooted ROM...
https://forum.xda-developers.com/sp...nt/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
OMJ said:
I've posted the RUU & firmware in the RUU thread, need testers that are already updated for stock rooted ROM...
https://forum.xda-developers.com/sp...nt/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
Click to expand...
Click to collapse
Awesome!
So, if I am on BadBoyz 3.2 currently, and am S-on, my path forward would be:
Restore my stock, unmodified backup
Lock bootloader
Run/flash RUU
Unlock bootloader
Am I missing anything?
ccs86 said:
Awesome!
So, if I am on BadBoyz 3.2 currently, and am S-on, my path forward would be:
Restore my stock, unmodified backup
Lock bootloader
Run/flash RUU
Unlock bootloader
Am I missing anything?
Click to expand...
Click to collapse
You could make it much shorter:
Run/flash RUU
Kisakuku said:
You could make it much shorter:
Run/flash RUU
Click to expand...
Click to collapse
Really? I had in my head that running the RUU with an unlocked bootloader and custom ROM would bork the device... no?
ccs86 said:
Awesome!
So, if I am on BadBoyz 3.2 currently, and am S-on, my path forward would be:
Restore my stock, unmodified backup
Lock bootloader
Run/flash RUU
Unlock bootloader
Am I missing anything?
Click to expand...
Click to collapse
haha, yeah u could just flash the RUU & that's it....there's no need to lock bootloader anymore
an alternate solution...flash 4.27.651.4 signed firmware, flash latest twrp, flash stock rooted 4.27.651.4 ROM I just posted...data stays intact
OMJ said:
haha, yeah u could just flash the RUU & that's it....there's no need to lock bootloader anymore
an alternate solution...flash 4.27.651.4 signed firmware, flash latest twrp, flash stock rooted 4.27.651.4 ROM I just posted...data stays intact
Click to expand...
Click to collapse
Well, I'll be damned!
I should have any important local data backed up at this point, so it's probably better to just nuke the thing and start with a fully clean install.
So, just windows drivers, run RUU, boom fully stock Nougat build and FW, still unlocked, ready for TWRP and a rooted ROM? That easy? No April Fools?? :cyclops:
:edit:
I may fire this off at work, so I haven't installed HTC drivers on this computer yet. Just plugging the phone in, I see no unknown devices in device manager. I see "0PGA2" in portable devices, and also ADB interface in USB devices. ADB Devices returns:
List of devices attached
HT54LSV05110 offline
Still smart to install HTC drivers? Anything newer than 4.2.0?
ccs86 said:
Well, I'll be damned!
I should have any important local data backed up at this point, so it's probably better to just nuke the thing and start with a fully clean install.
So, just windows drivers, run RUU, boom fully stock Nougat build and FW, still unlocked, ready for TWRP and a rooted ROM? That easy? No April Fools?? :cyclops:
:edit:
I may fire this off at work, so I haven't installed HTC drivers on this computer yet. Just plugging the phone in, I see no unknown devices in device manager. I see "0PGA2" in portable devices, and also ADB interface in USB devices. ADB Devices returns:
List of devices attached
HT54LSV05110 offline
Still smart to install HTC drivers? Anything newer than 4.2.0?
Click to expand...
Click to collapse
I'm using these drivers: https://drive.google.com/open?id=0BzxgIK5ppvWwTzc0RlQyLS1jd2s
as for the RUU, I always prefer using the sd card method....sooo easy!
yep, after flashing ruu, just flash latest twrp...and really at that point, you could just manually flash supersu or magisk (this will keep /system untouched)...I've turned into a Magisk fan
OMJ said:
I'm using these drivers: https://drive.google.com/open?id=0BzxgIK5ppvWwTzc0RlQyLS1jd2s
as for the RUU, I always prefer using the sd card method....sooo easy!
yep, after flashing ruu, just flash latest twrp...and really at that point, you could just manually flash supersu or magisk (this will keep /system untouched)...I've turned into a Magisk fan
Click to expand...
Click to collapse
Thanks for that link. The BMP driver installed,, but the HTC Driver 4.8.0.002 file doesn't do anything. I get a quick "thinking" cursor, then nothing... hmmm.
What's the SD card method? Haven't tried that, but have a big empty card in the phone.
ccs86 said:
Thanks for that link. The BMP driver installed,, but the HTC Driver 4.8.0.002 file doesn't do anything. I get a quick "thinking" cursor, then nothing... hmmm.
What's the SD card method? Haven't tried that, but have a big empty card in the phone.
Click to expand...
Click to collapse
https://forum.xda-developers.com/sp...nt/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
0PJAIMG_Sprint_HTC_One_M9_4.27.651.4_RUU.zip
Rename to 0PJAIMG.zip, copy to sd card, boot into download mode, it should scan card & prompt to install
but read this post 1st...https://forum.xda-developers.com/showpost.php?p=71849332&postcount=1143
looks like you'll need to flash the FW 1st, then RUU
OMJ said:
https://forum.xda-developers.com/sp...nt/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
0PJAIMG_Sprint_HTC_One_M9_4.27.651.4_RUU.zip
Rename to 0PJAIMG.zip, copy to sd card, boot into download mode, it should scan card & prompt to install
but read this post 1st...https://forum.xda-developers.com/showpost.php?p=71849332&postcount=1143
looks like you'll need to flash the FW 1st, then RUU
Click to expand...
Click to collapse
That would be an issue with S-on though, right? I was hoping that the RUU.exe would take care of it all in one shot. Or is firmware flashing first only needed with the SD card method?
ccs86 said:
That would be an issue with S-on though, right? I was hoping that the RUU.exe would take care of it all in one shot. Or is firmware flashing first only needed with the SD card method?
Click to expand...
Click to collapse
I'm not sure...but u can still flash the signed firmware when s-on
I am wanting to run the RUU exe, but am hesitant because ADB doesn't seem to be working properly.
I have tried a few versions of ADB.exe, older ones show the device as "offline", newer ones say "unauthorized".
I've tried every troubleshooting step I can think of, forcing install of latest Google drivers (code 10 driver can't start in device manager), restarting the computer and phone multiple times, toggling USB debugging, manually pushing the adbkey.pub file to data\misc\adb\adb_keys\, toggling the USB connection to "charging" mode, etc.
Nothing seems to work. Best I can tell, the phone should prompt me for an RSA authorization. Any ideas? Does it matter for RUU exe?
ccs86 said:
I am wanting to run the RUU exe, but am hesitant because ADB doesn't seem to be working properly.
I have tried a few versions of ADB.exe, older ones show the device as "offline", newer ones say "unauthorized".
I've tried every troubleshooting step I can think of, forcing install of latest Google drivers (code 10 driver can't start in device manager), restarting the computer and phone multiple times, toggling USB debugging, manually pushing the adbkey.pub file to data\misc\adb\adb_keys\, toggling the USB connection to "charging" mode, etc.
Nothing seems to work. Best I can tell, the phone should prompt me for an RSA authorization. Any ideas? Does it matter for RUU exe?
Click to expand...
Click to collapse
what are u trying to do w/ ADB?
OMJ said:
what are u trying to do w/ ADB?
Click to expand...
Click to collapse
I was really just trying to pull some files, because MTP sucks. When I couldn't get it to work, I wondered if that signified some issue in the USB connectivity which could cause an issue running the RUU exe via USB.
No worries?
ccs86 said:
I was really just trying to pull some files, because MTP sucks. When I couldn't get it to work, I wondered if that signified some issue in the USB connectivity which could cause an issue running the RUU exe via USB.
No worries?
Click to expand...
Click to collapse
maybe you're asb version is old...you can try Minimal ADB and Fastboot
OMJ said:
maybe you're asb version is old...you can try Minimal ADB and Fastboot
Click to expand...
Click to collapse
Yeah, tried that one as well. Says unauthorized.
You think that presents an issue for the RUU? I got the files transferred.
:edit:
Apparently so. The RUU said it couldn't connect to the phone. (Error 170)
Phone says it is "connected as media device" / "use USB for file transfers".
Device manager shows Android USB Devices -> My HTC, and also Portable Devices -> 0PJA2. Can transfer files via MTP.
Do I need to install the whole Android SDK or something?
::edit2::
I uninstalled all HTC and Android drivers / software. Installed HTC Sync Manager (which installs the drivers needed), but when I run it, it says "no phone connected". Same situation where I can see the phone storage as an MTP device, but something seems to be missing.
Sorry for all the handholding!
I think I should just flash the signed firmware (full firmware from RUU in your thread, right?), then the RUU zip version, like you suggested before.
Hmmmm... that didn't work
I wasn't able to run the RRU.exe from my pc. My bootloader was unlocked and i was s-on.
I tried to flash the firmware from the sd card and it stayed on the htc screen. So i just went with the RRU.zip.
I ended up getting the RRU.zip from here and putting it on the sd card and renaming it as mentioned. That worked for me and i am up and running on the nougat.