Hey all,
I have an HTC One running GE on Sense (it's 4.2.2), with Bulletproof. My computer is an HP, running on Win 8.1.
I made the mistake of not formatting on the upgrade from 4.1 and that's taken away like 4 GB of space for me to use. I was trying to reformat so I could get some of that back, but when I put the phone in download mode in CWM, ADB can't find the phone.
Obviously, I can't reformat without having a ROM ready to install.
I've done a number of things to get it to show up in ADB:
a) checked for HTC sync (not present)
b) checked for other drivers in device manager (not present)
c) enabled the install of unsigned drivers (apparently this needed to be done separately in Win 8.1)
d) tried to point the system to the Universal Naked Drivers (the system says no suitable drivers found)
e) enabled USB debugging
Results are the same - ADB is unable to find it. I see the device under device manager, but when I try to have it use the drivers I want, it says it cannot find them.
Is there something I'm doing wrong here?
karankshah said:
Hey all,
I have an HTC One running GE on Sense (it's 4.2.2), with Bulletproof. My computer is an HP, running on Win 8.1.
I made the mistake of not formatting on the upgrade from 4.1 and that's taken away like 4 GB of space for me to use. I was trying to reformat so I could get some of that back, but when I put the phone in download mode in CWM, ADB can't find the phone.
Obviously, I can't reformat without having a ROM ready to install.
I've done a number of things to get it to show up in ADB:
a) checked for HTC sync (not present)
b) checked for other drivers in device manager (not present)
c) enabled the install of unsigned drivers (apparently this needed to be done separately in Win 8.1)
d) tried to point the system to the Universal Naked Drivers (the system says no suitable drivers found)
e) enabled USB debugging
Results are the same - ADB is unable to find it. I see the device under device manager, but when I try to have it use the drivers I want, it says it cannot find them.
Is there something I'm doing wrong here?
Click to expand...
Click to collapse
windows 8.1 and your older hboot do not get along.
do you have access to another pc long enough to get s-off on your phone so you can run a RUU ?
clsA said:
windows 8.1 and your older hboot do not get along.
do you have access to another pc long enough to get s-off on your phone so you can run a RUU ?
Click to expand...
Click to collapse
I do, but if I need to get s-off first I have a few more questions.
1) Do I need to try to run adb when the phone is on the HBOOT screen or when the phone is in CWM/TWRP's sideload option?
2) What method of getting s-off am I going to be able to use from win7/the version of TWRP I'm in?
3) Is there a way to upgrade the HBOOT so it does work better?
4) What is an RUU?
Some of these questions are probably total noob questions, but it's mostly because the current GE+Sense/Bulletproof combination is insanely stable and this is my first HTC phone.
karankshah said:
I do, but if I need to get s-off first I have a few more questions.
1) Do I need to try to run adb when the phone is on the HBOOT screen or when the phone is in CWM/TWRP's sideload option?
2) What method of getting s-off am I going to be able to use from win7/the version of TWRP I'm in?
3) Is there a way to upgrade the HBOOT so it does work better?
4) What is an RUU?
Some of these questions are probably total noob questions, but it's mostly because the current GE+Sense/Bulletproof combination is insanely stable and this is my first HTC phone.
Click to expand...
Click to collapse
1. you run adb when the phone is plugged into the pc and booted up or when the phone is in twrp/cwm .. it doesn't work in bootloader
2.revone we hope or rumrunner maybe
3. hboot is part of the firmware update .. you need s-off first
4. A RUU is a Retail update utility it's how the carrier returns your phone to stock (out of the box condition)
If you looking to just gain back the space lost from the update all you need is a root explorer
and go to /data/media thats your old sdcard - you can delete what you don't want from here
the new sdcard is located at data/media/0
clsA said:
1. you run adb when the phone is plugged into the pc and booted up or when the phone is in twrp/cwm .. it doesn't work in bootloader
2.revone we hope or rumrunner maybe
3. hboot is part of the firmware update .. you need s-off first
4. A RUU is a Retail update utility it's how the carrier returns your phone to stock (out of the box condition)
If you looking to just gain back the space lost from the update all you need is a root explorer
and go to /data/media thats your old sdcard - you can delete what you don't want from here
the new sdcard is located at data/media/0
Click to expand...
Click to collapse
Thanks boss - I ended up running with revone off an old computer and I seem to be up and running for the moment.
Ok
Sent from my HTC One using Tapatalk 4
karankshah said:
Thanks boss - I ended up running with revone off an old computer and I seem to be up and running for the moment.
Click to expand...
Click to collapse
Also if you still want to return to stock now that your s-off
all the files/info you need are here >> http://www.htc1guru.com/downloads
Related
When I first got my Rezound months and months ago, I found and installed one of the stock, rooted ROMS on this site, and installed it.
Much to my annoyance, Verizon has been trying to push the latest update to my phone, so I came back to get the latest relevant ROM. I found http://forum.xda-developers.com/showthread.php?t=1835422 ("stock rooted deodexed 4.03.605.02") and flashed it from Recovery.
The problem is, whenever I try to boot the phone, it gets to the white screen with the green HTC logo, and just sits there. Did I miss a step or something? It's been a long while since I last flashed a ROM, and I'm sure I forgot something...
Thanks.
beleynn said:
When I first got my Rezound months and months ago, I found and installed one of the stock, rooted ROMS on this site, and installed it.
Much to my annoyance, Verizon has been trying to push the latest update to my phone, so I came back to get the latest relevant ROM. I found http://forum.xda-developers.com/showthread.php?t=1835422 ("stock rooted deodexed 4.03.605.02") and flashed it from Recovery.
The problem is, whenever I try to boot the phone, it gets to the white screen with the green HTC logo, and just sits there. Did I miss a step or something? It's been a long while since I last flashed a ROM, and I'm sure I forgot something...
Thanks.
Click to expand...
Click to collapse
looks like you tried to update to a ICS rom from a stock rom.
are you s-off or dev unlocked?
synisterwolf said:
looks like you tried to update to a ICS rom from a stock rom.
are you s-off or dev unlocked?
Click to expand...
Click to collapse
Dev unlocked.
beleynn said:
Dev unlocked.
Click to expand...
Click to collapse
you are going to need to re lock the bootloader and run the ruu.
this will wipe your internal sd card so please back it up
here are the steps:
1. back up rom
2. back up internal sd card
3. fastboot oem lock command
4. download the latest ruu
5. pull the zip out of it and name it PH98IMG.zip
6. place on root of external sd card
7. make sure you have 70% or more on the battery
8. boot into hboot and let it run.
8.1 first pass will be quick and it will ask you to reboot, say yes and grab a beer because the next part will take some time.
9. boot into stock rom
10. dev unlock and all that fun stuff again
synisterwolf said:
you are going to need to re lock the bootloader and run the ruu.
this will wipe your internal sd card so please back it up
here are the steps:
1. back up rom
2. back up internal sd card
3. fastboot oem lock command
4. download the latest ruu
5. pull the zip out of it and name it PH98IMG.zip
6. place on root of external sd card
7. make sure you have 70% or more on the battery
8. boot into hboot and let it run.
8.1 first pass will be quick and it will ask you to reboot, say yes and grab a beer because the next part will take some time.
9. boot into stock rom
10. dev unlock and all that fun stuff again
Click to expand...
Click to collapse
Thanks, but a few questions:
first, when I first got the phone and rooted it, S-Off wasn't available at the time (which is why I didn't do it then). Would it be better (and/or easier) to do that instead of dev unlock?
second, how do I "fastboot oem lock"? It's been months since I last flashed a ROM, and, as always, I forgot how to do these things.
Thanks again.
beleynn said:
Thanks, but a few questions:
first, when I first got the phone and rooted it, S-Off wasn't available at the time (which is why I didn't do it then). Would it be better (and/or easier) to do that instead of dev unlock?
second, how do I "fastboot oem lock"? It's been months since I last flashed a ROM, and, as always, I forgot how to do these things.
Thanks again.
Click to expand...
Click to collapse
s-off is a lot easier. i would recommend it. makes updating easy but you do run the risk of a brick so be careful
to re lock the bootloader you need to plug your phone into the pc.
make sure ADB debuging is on
then CD into your folder with ADB and Fastboot. (for me is C:\android )
then you type " fastboot oem lock"
you will see it say lock on top.
(if you are going to s-off then do not run this command. you need to be dev unlocked for s-off to work)
EDIT:
if you dont have ADB or Fastboot. i have a mini version for you to use. it will have everything needed to do this without having to download the whole android SDK link
synisterwolf said:
s-off is a lot easier. i would recommend it. makes updating easy but you do run the risk of a brick so be careful
to re lock the bootloader you need to plug your phone into the pc.
make sure ADB debuging is on
then CD into your folder with ADB and Fastboot. (for me is C:\android )
then you type " fastboot oem lock"
you will see it say lock on top.
(if you are going to s-off then do not run this command. you need to be dev unlocked for s-off to work)
EDIT:
if you dont have ADB or Fastboot. i have a mini version for you to use. it will have everything needed to do this without having to download the whole android SDK link
Click to expand...
Click to collapse
I *had* ADB, then I built a new PC, so thanks for the link.
Once I do S-Off, do I still follow the other steps except for 3?
synisterwolf said:
s-off is a lot easier. i would recommend it. makes updating easy but you do run the risk of a brick so be careful
to re lock the bootloader you need to plug your phone into the pc.
make sure ADB debuging is on
then CD into your folder with ADB and Fastboot. (for me is C:\android )
then you type " fastboot oem lock"
you will see it say lock on top.
(if you are going to s-off then do not run this command. you need to be dev unlocked for s-off to work)
EDIT:
if you dont have ADB or Fastboot. i have a mini version for you to use. it will have everything needed to do this without having to download the whole android SDK link
Click to expand...
Click to collapse
Ok, so I got to step 9 no problem (your ADB/Fastbook download was 1000x easier than downloading the whole damn package from Google).
Can I now just load up the rooted stock ROM I found earlier, or do I have to do the Dev unlock first?
beleynn said:
I *had* ADB, then I built a new PC, so thanks for the link.
Once I do S-Off, do I still follow the other steps except for 3?
Click to expand...
Click to collapse
If you are s-off you dont need to OEM lock the phone because s-off > dev unlock
so once you are s-off all you need to do is this:
1. download RUU of your choice
2. place on the root of the sd card
3. back up your internal sd because it will be wiped
4. make sure you have 70% battery or better
5. boot into hboot and let hboot take care of the rest.
5.1 first pass of the install will go quickly and ask for a reboot. it will boot back into hboot and continue the install.
6. boot into the stock rom once.
or if you want s-on
1. do the htc dev unlock fun
2. need to load up an engineering hboot to do fastboot commands.
once you have dev unlock then you can do recovery, then load any ICS rom that is meant for our phone. if you wanted to go back to GB you would need s-off so you can downgrade with a GB RUU. (but why would we want to go backwards. )
optional
if you want to install a recovery and you want to do it the fastboot way, you will need an engineering hboot which you can get from the s-off site
or
if you find a recovery that is in zip form just let hboot install it for you.
sorry but ive been trying t unlock and root my rezound for months and no i know i have a great quide on phandroid but i cant get unlocking to work. i type the adb devices command and my phone shows up but then when i type"fastboot devices" my phone wont be recognized by my computer can someone help me asap. i have a windows 8 64bit laptop
I have unlocked on windows 8 64bit before. Same way as any other Windows. Go into your device manager and see if your phone is an unconfigured device and make sure adb on phone is turned on.
Sent from my HTC6435LVW using Tapatalk 2
Can you help me with that
Flyhalf205 said:
I have unlocked on windows 8 64bit before. Same way as any other Windows. Go into your device manager and see if your phone is an unconfigured device and make sure adb on phone is turned on.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
How do i do that and im new so i dont really understand alot but itrecognizes it when i do "adb devices" but not "fastboot devices"
Can you give me a link to how you unlocked and rooted your rezound please? up to date
I would start here:
http://forum.xda-developers.com/showpost.php?p=37515020&postcount=444
That'll give you an overview of what you will need to do to get a custom ROM on there. Also, there's a folder attached there that has what you need to use fastboot.
If you don't have your unlock token from HTC yet, go here:
http://www.htcdev.com/bootloader/
Here's a guide to unlocking:
http://forum.xda-developers.com/showthread.php?t=1416109&highlight=unlock
There's a link to "One Click Root" at the bottom but I don't know if that's current. I've never used it. You can just flash Amon Ra after unlocking. Get it here:
http://forum.xda-developers.com/showthread.php?t=1339679
Just download v3.16. Don't worry about the attached files. Just grab it from the v3.16 link right above the attachments. Put that in the same folder you're using for flashing and type this:
fastboot flash recovery {nameofrecovery}
Then navigate in there to developer section and root.
Then make a nandroid immediately and append it with "_stock" so you always have it to go back to.
Now you are ready to flash a custom ROM.
Since you are s-on you will need to flash the kernel from the ROM after you flash the ROM. Some ROMs create one on your sd card in which case you will probably end up at the bootloader with it asking if you want to update, say yes. If not, you need to pull it from the ROM, put it in the "android" folder and flash in fastboot. I would pull it out ahead of time in case so you're ready.
fastboot flash boot boot.img (or whatever the name of the kernel is)
i flashed fresh evo lte yesterday via goo manager to update radios, ran flash img gui to go back to aosp, then flashed cm10.1 but it wouldnt boot. eventually i ended up formatting my internal SD, removing my external SD completely, flashing back to fresh evo and it worked, but still no internal storage. i dont know why but im wondering if my internal storage is labeled wrong, or just toasted.. no access to fastboot or adb. no form of formatting so far has worked
im on hboot 1.15.0000, radio 1.05.11.0606, s-on, twrp 2.2.2.0
jmacphee9 said:
i flashed fresh evo lte yesterday via goo manager to update radios, ran flash img gui to go back to aosp, then flashed cm10.1 but it wouldnt boot. eventually i ended up formatting my internal SD, removing my external SD completely, flashing back to fresh evo and it worked, but still no internal storage. i dont know why but im wondering if my internal storage is labeled wrong, or just toasted.. no access to fastboot or adb. no form of formatting so far has worked
im on hboot 1.15.0000, radio 1.05.11.0606, s-on, twrp 2.2.2.0
Click to expand...
Click to collapse
A rom will not update your firmware/radios
If I remember correctly CM,AOSP,AOKP roms mount your internal storage differently.
Your TWRP is veryyyyyy old
Y U NO S-OFF it will save you alot of headaches
FacePalm in Original Dev takes about 5 minutes now goooooo
Once S-OFF you can update your firmware/radios manually
bigdaddy619 said:
A rom will not update your firmware/radios
If I remember correctly CM,AOSP,AOKP roms mount your internal storage differently.
Your TWRP is veryyyyyy old
Y U NO S-OFF it will save you alot of headaches
FacePalm in Original Dev takes about 5 minutes now goooooo
Once S-OFF you can update your firmware/radios manually
Click to expand...
Click to collapse
heh i did this all before s-off was even an option ill your suggestion, i wasnt sure how to go about s-off now that i have no internal storage:/
edit: need a working adb environment for that:/ ill try flashing my last aosp rom to see if that will get me a working adb enviroment to mount the storage then push the kernel through.
I don't think it'll be possible to get S-off right now w/o adb access. i wonder if relocking would allow you to flash a stock ruu and restart. That's probably not possible w/o adb either though.
What does "adb devices" say when you connect your phone? Are you checking the obvious and making sure that usb debugging is enabled?
i decided to reinstall java and android sdks, and it appears i have restored a working adb environment. i try to get s-off now before bed.
edit: nope. well fastboot not working at least.
CNexus said:
What does "adb devices" say when you connect your phone? Are you checking the obvious and making sure that usb debugging is enabled?
Click to expand...
Click to collapse
C:\android-sdk\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
then after killing htc sync
C:\android-sdk\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>adb devices
List of devices attached
HT24YSxxxxx device
C:\android-sdk\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>
jmacphee9 said:
i decided to reinstall java and android sdks, and it appears i have restored a working adb environment. i try to get s-off now before bed.
edit: nope. well fastboot not working at least.
Click to expand...
Click to collapse
Make sure you update android-sdk then reboot your PC plug your phone back in and it should install more drivers it did for me anyways after I updated
I suggest doing the following:
Uninstall all drivers and HTC Sync
Reboot computer
Grab the *standalone* drivers from here: http://forum.xda-developers.com/showthread.php?t=2246355
Run the installer from above
Reboot computer again
Plug in your phone, have it install drivers
Reboot your computer and phone
Now plug in your phone one last time and it should install the rest of the drivers
CNexus said:
I suggest doing the following:
Uninstall all drivers and HTC Sync
Reboot computer
Grab the *standalone* drivers from here: http://forum.xda-developers.com/showthread.php?t=2246355
Run the installer from above
Reboot computer again
Plug in your phone, have it install drivers
Reboot your computer and phone
Now plug in your phone one last time and it should install the rest of the drivers
Click to expand...
Click to collapse
unfortunately that didn't help:/
I don't mind keeping it rooted/unlocked etc but i want the rom to be stock. Going to be giving this phone to a family member and I just don't want to deal with any tech support issues for the phone so I'd like to put it back to stock so if they need to call sprint, everything is going to look normal.
I'm downloading the RUU_Jewel exe file from here http://d-h.st/QhK - i'm just not sure what to do with it. Last time i flashed any roms on this phone i downloaded a zip file and installed it through recovery.
Does this exe run from my desktop and install over usb? I assume root will be gone if i install this. and s-off will remain off?
thanks
Don't run that RUU. Hit the top link in my sig and scroll down to the RUU section for instructions on how to install a RUU. Then scroll down to the bottom of the same post and download the 4.13.651.4 RUU. The RUU will install the stock ROM, therefore removing root and your custom recovery. You will remain S-off but your bootloader will be relocked. It is run from your computer.
Just a quick note. This RUU will change the partition setup for the internal storage. If you have anything on your internal storage and want to save it, back it up to your computer before running the RUU, as the RUU will wipe the internal storage.
Magnum_Enforcer said:
Don't run that RUU. Hit the top link in my sig and scroll down to the RUU section for instructions on how to install a RUU. Then scroll down to the bottom of the same post and download the 4.13.651.4 RUU. The RUU will install the stock ROM, therefore removing root and your custom recovery. You will remain S-off but your bootloader will be relocked. It is run from your computer.
Just a quick note. This RUU will change the partition setup for the internal storage. If you have anything on your internal storage and want to save it, back it up to your computer before running the RUU, as the RUU will wipe the internal storage.
Click to expand...
Click to collapse
Thanks - can you tell me what the difference is between your file and the one i downloaded? The one i downloaded previously is RUU_JEWEL_CL_JB43_SENSE50_MR_Sprint_WWE_4.13.651.3_Radio_1.13.11.1105_NV_3.02_003_PRL25007_release_353492_signed_one_step
And i dont care about anything getting erased - i want to totally wipe the phone clean anyhow so everything should be erased before I give it them.
Thanks
Oh and if it makes any difference, the current rom on the phone is the viper 3.17 rom
The difference has to do with some fixes related to the roaming options. I think that's the only major difference, at least that I can recall.
Magnum_Enforcer said:
The difference has to do with some fixes related to the roaming options. I think that's the only major difference, at least that I can recall.
Click to expand...
Click to collapse
Is there any way to restore it using a rom? I tried resetting it using the RUU file but it's not working. It starts doing it's thing, says it's waiting for the bootloader at which point the phone restarts, shows me the HTC logo and then after a few minutes it says it failed and the phone stays on the HTC logo until i reset it.
Or do you have any suggestions on how to work around this problem?
Thanks
A ROM will only install software, not firmware. You need to do both, hence the RUU. Install HTC Sync on your computer so that you have the latest drivers. Reboot to the bootloader and connect your phone and computer in Fastboot USB mode. Afterwards, double-click the RUU file to start the installer. Shouldn't have any issues otherwise.
Magnum_Enforcer said:
A ROM will only install software, not firmware. You need to do both, hence the RUU. Install HTC Sync on your computer so that you have the latest drivers. Reboot to the bootloader and connect your phone and computer in Fastboot USB mode. Afterwards, double-click the RUU file to start the installer. Shouldn't have any issues otherwise.
Click to expand...
Click to collapse
I'm actually fine if it just installs the software - as long as if she calls sprint the interface she sees is the one they expect her to see. She's not going to be bring the phone into a sprint store ...actually she wont even be on sprint, she uses straight talk. So it doesn't matter if the phone is rooted/unlocked etc. Just needs to be the interface support will expect there to be if she ever calls them and they tell her to do something.
thanks
merkk said:
I'm actually fine if it just installs the software - as long as if she calls sprint the interface she sees is the one they expect her to see. She's not going to be bring the phone into a sprint store ...actually she wont even be on sprint, she uses straight talk. So it doesn't matter if the phone is rooted/unlocked etc. Just needs to be the interface support will expect there to be if she ever calls them and they tell her to do something.
thanks
Click to expand...
Click to collapse
Good enough. Just flash a Sense ROM and call it a day, then. I would at least make sure that you update the firmware version to match that of the ROM you decide to use. That's fairly simple since the phone is S-off.
there is a tool to do just this in Android Development. I'd start there
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.