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.
Related
hello
I have now gained s-off (locked bootloader), completed supercid, and flashed ics ruu.
I am not trying to flash cwm and then finally re-root
However, in command prompt my computer can no longer find my device when in fastboot usb and I type "adb devices"
I was able to see my device to complete supercid when still on GB
Do i need to do something after flashing ics for adb to work again?
thanks for help with this as I am trying to get cwm on
Is your ICS rooted? Also, I don't think ADB will recognize your phone in fastboot. Also, recheck to see if USB Debugging is on.
But try ADB devices after your rooted and with the phone on.
Don't quote me on this...
Thank you GlacierGuy
windcan said:
hello
I have now gained s-off (locked bootloader), completed supercid, and flashed ics ruu.
I am not trying to flash cwm and then finally re-root
However, in command prompt my computer can no longer find my device when in fastboot usb and I type "adb devices"
I was able to see my device to complete supercid when still on GB
Do i need to do something after flashing ics for adb to work again?
thanks for help with this as I am trying to get cwm on
Click to expand...
Click to collapse
After a couple hang ups I am so happy to say that with GlacierGuy help, I got it.
Now onto a good ROM
Thank you GlacierGuy
score one for double G
Looks like I got the same issue, so what have you done to get it back to visible mode?
windcan said:
After a couple hang ups I am so happy to say that with GlacierGuy help, I got it.
Now onto a good ROM
Thank you GlacierGuy
Click to expand...
Click to collapse
lexamol said:
Looks like I got the same issue, so what have you done to get it back to visible mode?
Click to expand...
Click to collapse
Well for one make sure USB debugging in checked off. Settings>develop options>USB debugging.
And if your just trying to flash a recovery no need for adb, just download 4ext updater from the 4ext website onto your phobe, or 4ext from the market and flash recovery with your phone
sent from my NRGized Amaze,
powered by faux kernel v.12
My beloved rezound has gone kaput.
I had clean rom on my phone until it stopped booting past the white HTC screen.
I decided to flash a new rom on the phone, as I couldn't seem to find the version of clean rom I had before.
My question is: Is there any way to flash the new boot.img from the phone itself? Or is it required to be connected to the computer itself?
To repair my phone it looks like the only thing I can do is re-flash Clean Rom (Because of the boot.img)
Is this true?
Thanks for any help in advance!
mainmanluke said:
My beloved rezound has gone kaput.
I had clean rom on my phone until it stopped booting past the white HTC screen.
I decided to flash a new rom on the phone, as I couldn't seem to find the version of clean rom I had before.
My question is: Is there any way to flash the new boot.img from the phone itself? Or is it required to be connected to the computer itself?
To repair my phone it looks like the only thing I can do is re-flash Clean Rom (Because of the boot.img)
Is this true?
Thanks for any help in advance!
Click to expand...
Click to collapse
You can boot the phone into hboot and flash the boot.img from fastboot on your computer, but you'd be hard pressed to do it without a PC
AshtonTS said:
You can boot the phone into hboot and flash the boot.img from fastboot on your computer, but you'd be hard pressed to do it without a PC
Click to expand...
Click to collapse
Following what procedure exactly? adb devices brings up nothing when the phone is in HBOOT mode. I'm assuming you
don't use the same method as you would with an RUU or radio?
Apologies for my stupidity, I seem to be mixing this up.
(Plus I'm stressed because I have an interview with google tonight )
mainmanluke said:
Following what procedure exactly? adb devices brings up nothing when the phone is in HBOOT mode. I'm assuming you
don't use the same method as you would with an RUU or radio?
Apologies for my stupidity, I seem to be mixing this up.
(Plus I'm stressed because I have an interview with google tonight )
Click to expand...
Click to collapse
You'll need to use fastboot rather than adb (same general procedure tho)
Make sure to highlight the fastboot tab in hboot and press the power button to select it, then on your computer type "fastboot flash boot <path to boot.img>" then when it finishes, "fastboot reboot" and you should be good.
Good luck with your interview
Adb is really great for pushing and pulling files from your system or sdcards. Flashing stuff is great for fastboot.
AshtonTS said:
You'll need to use fastboot rather than adb (same general procedure tho)
Make sure to highlight the fastboot tab in hboot and press the power button to select it, then on your computer type "fastboot flash boot <path to boot.img>" then when it finishes, "fastboot reboot" and you should be good.
Good luck with your interview
Click to expand...
Click to collapse
Well, I seem to be stuck at "< waiting for device >" even when in fastboot :/ Any ideas?
Also, talking to the hiring manager tomorrow, will be with Google soon
mainmanluke said:
Well, I seem to be stuck at "< waiting for device >" even when in fastboot :/ Any ideas?
Also, talking to the hiring manager tomorrow, will be with Google soon
Click to expand...
Click to collapse
make sure your PC has the drivers installed. The ones for fastboot are different but should've been installed with the adb drivers. Check Windows Device Manager for anything that might not have installed correctly.
Also make sure you open the command prompt with admin privileges if you're running vista/7.
You should be able to write a boot image via hboot with a PH98IMG.zip on your sdcard. That way you don't need a computer.
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
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?
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.