Related
Hi, I have been the happy owner of an international HTC One X for just over a month now. I'm from Australia and my carrier is Vodafone.I have been using the Lee-Droid One Xtreme Rom without issue for almost the entire time I've owned the phone, however two days ago some huge issues appeared.
First the handset resest itself, this had happened before but this time it was stuck on the "HTC Quietly Brilliant" splash screen. I tried to wipe the cache from recovery but recovery wouldn't boot. I plugged the phone into my laptop and used "fastboot erase cache" which seemed to work but did not solve my problem, still hanging at the splash screen.
I then noticed that my bootloader had somehow locked itself again so I flashed my Unlock_code.bin again, the handset displayed the usual prompts which I followed but when my phone reset I was greeted with the now familiar hanging bootsplash plus a warning about the ROM being for internal HTC use only.
I also noticed this message in my terminal:
FAILED (status read failed (Cannot send after transport endpoint shutdown))
Can someone please help me here? I'm hesitant to send the phone away because I unocked the bootloader via htcdev.com so my warranty is invalid most likely.
Thanks for your time and sorry if this is a duplicate thread, I had done a few searches already and found nothing that spunded like my problem though.
Did your bootloader say locked or relocked
Sent from my HTC One X using Tapatalk 2
Did u flash de cwm last recovery? There are some problems with usb, try to use another One, install drivers, restart pc.
Htc One X Venom ViperX Rom & Show-p Kernel
@KrisPerry - the bootloader says either :
***LOCKED***
or
***LOCKED***
***SECURITY WARNING***
@drangonesdenano
last recovery I flashed CWM 5.8.4.0
have tried restarting pc, no change.
i use linux so there are no drivers to reinstall.
none of the cables i have fit, but this is the original htc cable, it seems to be in decent condition, i'll try and see if i can borrow one from a friend though.
sorry for taking a while to reply to you guys, i've been having login troubles with the xda site. thankyou for your help thusfar. any ideas?
Try closing and opening bootloader again, then flash recovery if not working properly. Has to do with usb ... I think ..not to cable. Then tell us
Htc One X Venom ViperX Rom & faux123 b004b7 Kernel
dragonesdenano said:
Try closing and opening bootloader again, then flash recovery if not working properly. Has to do with usb ... I think ..not to cable. Then tell us
Htc One X Venom ViperX Rom & faux123 b004b7 Kernel
Click to expand...
Click to collapse
hi, sorry for taking so long to reply, i have been having some major troubles with both my computer and then getting enough charge into the phone. i ended up writing this script:
Code:
#!/bin/sh
while true
do
./fastboot getvar battery-voltage
./fastboot reboot-bootloader
sleep 10
done
writing from a different pc with a fresh linux mint install i've tried unlocking the bootloader again but this time i'm getting this from the terminal:
Code:
./fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (No such device))
finished. total time: 9.179s
what do you think? i bought a second usb cable and have been switching between the two but it makes no difference... i can't flash recovery because the bootloader is locked and i seem to be stuck in a bootloop so i can't boot into CWM either.
i've been reading about people flashing RUU's, is that what i need to do?
Just a gentle bump on this thread, I've been without a phone for over a week now and it's getting pretty annoying (first world problems). Has anyone seen this before? What should I do? Any help would be greatly appreciated.
Cheers, Toby.
RUUs
So I'm looking into the possibility of flashing an RUU, what are my options for doing so under Linux?
I've found this link: http://forum.xda-developers.com/showthread.php?t=1465747
Has anyone used openRUU? Does it work for the HOX?
The only other option I can see is making a Windows virtual machine... My only concern is installing the drivers, will that work seeing as I can only access fastboot?
Also I'm not sure exactly where to find an RUU... I've checked out this link: http://www.filefactory.com/f/7cc7b2fbdd03c031/
but my RUU (1.29.862.11) wasn't there and I've struggled to find a download elsewhere....
any clues?
Any help would be devoured thankfully.
Toby.
Free bump...
Sent from my HTC One X using xda premium
TobyJamesJoy said:
So I'm looking into the possibility of flashing an RUU, what are my options for doing so under Linux?
I've found this link: http://forum.xda-developers.com/showthread.php?t=1465747
Has anyone used openRUU? Does it work for the HOX?
The only other option I can see is making a Windows virtual machine... My only concern is installing the drivers, will that work seeing as I can only access fastboot?
Also I'm not sure exactly where to find an RUU... I've checked out this link: http://www.filefactory.com/f/7cc7b2fbdd03c031/
but my RUU (1.29.862.11) wasn't there and I've struggled to find a download elsewhere....
any clues?
Any help would be devoured thankfully.
Toby.
Click to expand...
Click to collapse
The RUU doesn't do anything fancy, it just packages the boot.img, recovery? and ROM, and uses the same method we would use to flash the bits individually.
If there is no RUU for your version, I hope you took the advise of making a backup.
Update
whynot66 said:
Free bump...
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks man!
So I've set out on a mission and made a Virtualbox Windows XP install, installed the sdk and HTC sync, configured the usb settings, and the virtual install seems to be able to detect my handset in fastboot.
Good times.
I was able to run all the fastboot commands I wanted, including "fastboot oem get_identifier_token" which wasn't previously working on the Linux side and now through some kind of voodoo works a charm under Linux too. After running this command I visited the htcdev site and requested a new Unlock_code.bin but that didn't work, still getting FAILED errors...
One thing I have noticed is that every time I run "fastboot oem get_identifier_token" I get a dramatically different token, wil this result in a different Unlock_code.bin? Maybe one of the will work eventually (doubtful).
On the other hand it seems that I've got everything ready to flash an RUU, I just need that RUU... So does anyone know where I can find it?
BenPope said:
The RUU doesn't do anything fancy, it just packages the boot.img, recovery? and ROM, and uses the same method we would use to flash the bits individually.
If there is no RUU for your version, I hope you took the advise of making a backup.
Click to expand...
Click to collapse
I've read this thread:
http://forum.xda-developers.com/wiki/HTC_One_X
and flashing the RUU seems to be the only way to go seeing as my bootloader is locked and won't unlock. Becuase you flash RUUs with a locked bootloader right?
I've read about vodafone releasing this RUU so I'm pretty sure it exists, I'm just not sure how to get it.
I did make a nandroid backup of the stock rom, is it possible to flash that?
I don't care how much data I lose, so long as I get a functional telephone in return.
TobyJamesJoy said:
I've read this thread:
http://forum.xda-developers.com/wiki/HTC_One_X
and flashing the RUU seems to be the only way to go seeing as my bootloader is locked and won't unlock. Becuase you flash RUUs with a locked bootloader right?
I've read about vodafone releasing this RUU so I'm pretty sure it exists, I'm just not sure how to get it.
I did make a nandroid backup of the stock rom, is it possible to flash that?
I don't care how much data I lose, so long as I get a functional telephone in return.
Click to expand...
Click to collapse
Hmmm, so you were unlocked but.now it won't unlock? Odd.
With a stock recovery, you should still be able to flash signed ROMs, perhaps not your backup though.
If it's not on filefactory, it's probably not widely available. Google is your friend, I guess.
BenPope said:
Hmmm, so you were unlocked but.now it won't unlock? Odd.
With a stock recovery, you should still be able to flash signed ROMs, perhaps not your backup though.
If it's not on filefactory, it's probably not widely available. Google is your friend, I guess.
Click to expand...
Click to collapse
yeah, weird huh?
forgive my ignorance but what exactly is a signed rom?
i'm not sure what recovery i've got at the moment, last one i flashed was CWM 5.8.4.0 but that won't boot anymore.. do i need recovery to flash my backup?
in my backup i have a boot.img, recovery.img the md5 sum and a few tarballs (cache, data, system), if i flash recovery.img will i get the stock recovery? or do i need an unlocked bootloader to do that?
and if i get stock recovery what can i flash from there with a locked bootloader?
you were saying that an RUU does the same things as flashing the components individually, but also you say that i might not to be flash my backup, so i'm a bit confused.... n00bdom......
TobyJamesJoy said:
yeah, weird huh?
forgive my ignorance but what exactly is a signed rom?
i'm not sure what recovery i've got at the moment, last one i flashed was CWM 5.8.4.0 but that won't boot anymore.. do i need recovery to flash my backup?
in my backup i have a boot.img, recovery.img the md5 sum and a few tarballs (cache, data, system), if i flash recovery.img will i get the stock recovery? or do i need an unlocked bootloader to do that?
and if i get stock recovery what can i flash from there with a locked bootloader?
you were saying that an RUU does the same things as flashing the components individually, but also you say that i might not to be flash my backup, so i'm a bit confused.... n00bdom......
Click to expand...
Click to collapse
A signed ROM is an official one from HTC, signed by their private key. The CID also has to match your phone. Then the standard recovery will allow it to be flashed.
I find it strange that you are locked.with a nonstandard recovery. I think you should get back to unlocked before proceeding.
Try unlocking your phone from scratch using the normal procedure.
Why doesn't that work? What stage fails? What error do you get?
BenPope said:
A signed ROM is an official one from HTC, signed by their private key. The CID also has to match your phone. Then the standard recovery will allow it to be flashed.
I find it strange that you are locked.with a nonstandard recovery. I think you should get back to unlocked before proceeding.
Try unlocking your phone from scratch using the normal procedure.
Why doesn't that work? What stage fails? What error do you get?
Click to expand...
Click to collapse
I've tried this numerous times, everything works right up to the final stage. My device is recognised by fastboot, I can get the identifier token, flash the Unlock_code.bin, it writes to the handset properly, the handset displays the black screen with "yes" and "no" options and the warnings about voiding your warranty, i choose "yes" and the phone reboots into fastboot while the terminal reads like so:
Code:
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (No such device))
that's under Linux, in my Windows XP virtual box it reads the same except the final line is:
Code:
FAILED (status read failed (Unkown error))
I've tried this on two different PCs, one running arch linux, another on ubuntu 12.04, also on a fresh install of Linux Mint 13. I've tried every different usb port available and I've tried generating different Unlock_code.bin files - nothing seems to work.......
Brickland.
Idea
This may have something to do with my udev rules, these are the ones i'm currently using, I can't remember now where i found them but they govern how the OS handles certain devices. Here's my /etc/udev/rules.d/51-android.rules
Code:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0fff", MODE="0666", OWNER="tobias"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c02",SYMLINK+="android_adb"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c01",SYMLINK+="android_fastboot"
does anyone with some linux knowhow see anything wrong with them?
or am i barking up the wrong tree?
TobyJamesJoy said:
This may have something to do with my udev rules, these are the ones i'm currently using, I can't remember now where i found them but they govern how the OS handles certain devices. Here's my /etc/udev/rules.d/51-android.rules
Code:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0fff", MODE="0666", OWNER="tobias"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c02",SYMLINK+="android_adb"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0bb4",ATTRS{idProduct}=="0c01",SYMLINK+="android_fastboot"
does anyone with some linux knowhow see anything wrong with them?
or am i barking up the wrong tree?
Click to expand...
Click to collapse
I think you only need this (and a fraction of it at that) if adb devices shows nothing.
TobyJamesJoy said:
I've tried this numerous times
Snip
Brickland.
Click to expand...
Click to collapse
I have no idea, I've never unlocked mine.
Sorry dude, but I'm sure it can be recovered, you just to find the right incantation.
BenPope said:
I think you only need this (and a fraction of it at that) if adb devices shows nothing.
Click to expand...
Click to collapse
hmm, i'm not sure i follow you but you have hit on one glaring omission of mine, i've never been able to get adb working.... maybe i should forage around for tips in that area.
are you saying that i only need the proper udev rules to get adb working and i should be able to do it with a fraction of the code? what do you mean by "if adb devices shows nothing"?
Hi all,
I have spent the last week trying to solve my problem. Basically I tried to unlock the bootloader on my HTC desire HD using the instructions supplied by HTCDEV. Something happened during the unlocking process and now I have an unlocked bootloader and a phone that doesnt boot. The unlocking process didnt go through as I didnt get to the part where I have to work with the token. However, if I boot into bootloader, it shows that it is unlocked and s-on. I can get to the fastboot menu and the phone only boots to the HTC screen.
I have followed the instructions from the many posts in this forum without any luck. I cant seem to be able to flash anything through fastboot. I keep getting errors such signature failed error 132 and error 131. I cant access recovery. It gives out errors whenever i try to access it. ADB doesnt work. The device doesnt get picked up in windows. I tried flashing recovery without any luck. The CID is HTC_612. The firmware version is 1.31.405.6.
I tried to use an RUU but I always get the error that the RUU that i am using is not the one for my rom or that the signature verification is wrong.
Any advice?
Thanks
Galam said:
Hi all,
I have spent the last week trying to solve my problem. Basically I tried to unlock the bootloader on my HTC desire HD using the instructions supplied by HTCDEV. Something happened during the unlocking process and now I have an unlocked bootloader and a phone that doesnt boot. The unlocking process didnt go through as I didnt get to the part where I have to work with the token. However, if I boot into bootloader, it shows that it is unlocked and s-on. I can get to the fastboot menu and the phone only boots to the HTC screen.
I have followed the instructions from the many posts in this forum without any luck. I cant seem to be able to flash anything through fastboot. I keep getting errors such signature failed error 132 and error 131. I cant access recovery. It gives out errors whenever i try to access it. ADB doesnt work. The device doesnt get picked up in windows. I tried flashing recovery without any luck. The CID is HTC_612. The firmware version is 1.31.405.6.
I tried to use an RUU but I always get the error that the RUU that i am using is not the one for my rom or that the signature verification is wrong.
Any advice?
Thanks
Click to expand...
Click to collapse
Damn. If you had S-OFF you could have flashed a recovery and it would have been easier for you. Post in the thread linked in my signature (Ace Think Tank) and you'll hopefully get some help from someone (most likely Glevitan)
Galam said:
Hi all,
I have spent the last week trying to solve my problem. Basically I tried to unlock the bootloader on my HTC desire HD using the instructions supplied by HTCDEV. Something happened during the unlocking process and now I have an unlocked bootloader and a phone that doesnt boot. The unlocking process didnt go through as I didnt get to the part where I have to work with the token. However, if I boot into bootloader, it shows that it is unlocked and s-on. I can get to the fastboot menu and the phone only boots to the HTC screen.
I have followed the instructions from the many posts in this forum without any luck. I cant seem to be able to flash anything through fastboot. I keep getting errors such signature failed error 132 and error 131. I cant access recovery. It gives out errors whenever i try to access it. ADB doesnt work. The device doesnt get picked up in windows. I tried flashing recovery without any luck. The CID is HTC_612. The firmware version is 1.31.405.6.
I tried to use an RUU but I always get the error that the RUU that i am using is not the one for my rom or that the signature verification is wrong.
Any advice?
Thanks
Click to expand...
Click to collapse
thanks GuyInTheCorner I have posted the question is the thread as required.
Hey guys, my HTC M8 is stuck at bootlogo and it wont reboot into recovery or unable to unlock bootloader. Tried factory reset but still same problem. Currently downloading RUU_M8_UHL_L50_SENSE60_MR_hTC_Asia_India_4.18.720.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_417228_signed.exe but I dont know if it will work.. I am posting some screenshots, so I request you to please help.
and I also know how to carryout fastboot commands
also the phone is not getting detected using those htc_fastboot commands..
stuck at <waiting for device>
Sachin7843 said:
Hey guys, my HTC M8 is stuck at bootlogo and it wont reboot into recovery or unable to unlock bootloader. Tried factory reset but still same problem. Currently downloading RUU_M8_UHL_L50_SENSE60_MR_hTC_Asia_India_4.18.720.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_417228_signed.exe but I dont know if it will work.. I am posting some screenshots, so I request you to please help.
and I also know how to carryout fastboot commands
also the phone is not getting detected using those htc_fastboot commands..
stuck at <waiting for device>
Click to expand...
Click to collapse
The RUU probably won't work. Try extracting the firmware.zip from the 4.18.720.10 ota and flash. That should work.
Sent from my HTC One_M8 using Tapatalk
First you need to update the adb and fastboot drivers on your laptop for them to detect your HTC One M8.
There are multiple reasons they might not be working. I advise trying each solution you come across until one works for you and you are able to detect your phone through fastboot again.
After that follow with the official bootloader unlock way provided by HTC.
RELOCKED
S-ON
OS : 2.10.401.1
CID: HTC_0031
Hello Guys,
I have a major problem getting my HTC M9 back to stock!
My first problem began when i was trying to update my ViberRom from 5.1.1 to Marschmallow, the problem that i had was that my recovery could not update. But when i updated it to 3.0.0 or something like that, i couldn't boot my ViberRom (because that was still 5.1.1).
So in order to fix that problem i thought that i could return my HTC M9 back to stock with an RUU, however since i have the EU/International version (2.10.401.1), i could not use the .exe version HTC provided themselves on their own website. After looking on the internet i found an RUU which corresponded with my version (2.10.401.1) it was a ZIP file so i needed to either flash it or put it on my SD card.
After a while a new problem arose, I have no S-OFF, but after reading several threads i did not matter as long as i had the right RUU version or higher (as well as matching CID, MID). Several articles and threads also mentioned that when i wanted to flash an RUU with S-On i would need to re-lock my bootloader and so i did.
With a locked bootloader i tried flashing the RUU, but everytime when i do it my FASTBOOT.EXE crashes!
Sorry if i am being a NOOB right now, but i really don't know what to do now, My Rom won't boot and i cant acces my recovery. I already treid Unlocking my bootloader again, and after completing every step, including choosing the option to unlock it on the phone itself using the volume buttons, it still states: RELOCKED
I really hope you guys can help me with my problem!!
Kind regards,
Roan
(sorry for anything that may be not clear, English is not my native language)
Roanvdw said:
RELOCKED
S-ON
OS : 2.10.401.1
CID: HTC_0031
Hello Guys,
I have a major problem getting my HTC M9 back to stock!
My first problem began when i was trying to update my ViberRom from 5.1.1 to Marschmallow, the problem that i had was that my recovery could not update. But when i updated it to 3.0.0 or something like that, i couldn't boot my ViberRom (because that was still 5.1.1).
So in order to fix that problem i thought that i could return my HTC M9 back to stock with an RUU, however since i have the EU/International version (2.10.401.1), i could not use the .exe version HTC provided themselves on their own website. After looking on the internet i found an RUU which corresponded with my version (2.10.401.1) it was a ZIP file so i needed to either flash it or put it on my SD card.
After a while a new problem arose, I have no S-OFF, but after reading several threads i did not matter as long as i had the right RUU version or higher (as well as matching CID, MID). Several articles and threads also mentioned that when i wanted to flash an RUU with S-On i would need to re-lock my bootloader and so i did.
With a locked bootloader i tried flashing the RUU, but everytime when i do it my FASTBOOT.EXE crashes!
Sorry if i am being a NOOB right now, but i really don't know what to do now, My Rom won't boot and i cant acces my recovery. I already treid Unlocking my bootloader again, and after completing every step, including choosing the option to unlock it on the phone itself using the volume buttons, it still states: RELOCKED
I really hope you guys can help me with my problem!!
Kind regards,
Roan
(sorry for anything that may be not clear, English is not my native language)
Click to expand...
Click to collapse
Fastboot crashes because it can't handle files over 2 GB. There is a different fastboot you need to use called htc_fastboot. Search the forum for a link. Or I'll find one if i can. Commands are exactly the same as fastboot, just add "htc_" in front of fastboot.
Here you go:
https://www.androidfilehost.com/?fid=95916177934550031
jollywhitefoot said:
Fastboot crashes because it can't handle files over 2 GB. There is a different fastboot you need to use called htc_fastboot. Search the forum for a link. Or I'll find one if i can. Commands are exactly the same as fastboot, just add "htc_" in front of fastboot.
Here you go:
Click to expand...
Click to collapse
IT WORKED, very grateful man, very weird that i could not find this problem in the forum though, maybe i just suck at searching.
i have the same problem, i cant even find RUU.zip file, if you could help me with that, would really appreciate it
My phone is having a bowl of bootloops right now lol.
I have a unlocked htc 10, i unlocked the bootloader (S-on since leedroid thread didn't say it was necessary), flashed the latest TWRP formatted data part, rebooted recovery again, swiped allow modifications, flashed the marshmallow version of the ROM and nothing but bootloops. what am i missing? thanks
first time HTC owner here coming from a 6p so show mercy
drago10029 said:
My phone is having a bowl of bootloops right now lol.
I have a unlocked htc 10, i unlocked the bootloader (S-on since leedroid thread didn't say it was necessary), flashed the latest TWRP formatted data part, rebooted recovery again, swiped allow modifications, flashed the marshmallow version of the ROM and nothing but bootloops. what am i missing? thanks
first time HTC owner here coming from a 6p so show mercy
Click to expand...
Click to collapse
Are you on MM firmware or N?
Also S-OFF is the way to go.
andybones said:
Are you on MM firmware or N?
Also S-OFF is the way to go.
Click to expand...
Click to collapse
I was on latest stock nougat before I started the process. since the I have tried flashing both leedroid marshmallow zip and the nougat magisk zip also. and what's the deal with s-off?
Everywhere i look they're all how to's about s-off lol. seems hard to find a thread on what s-off is, if it's needed to for a specific ROM or not :/ that being said leedroid it wasn't needed as quoted below. thanks!
If you wish to s-off first, please follow >> THIS GUIDE << by @jcase & return when your device is back up and running.
First boot will take approximately 15 minutes due to Art optimization
Click to expand...
Click to collapse
UPDATE: things have gotten worse.... I was attempting to relock the bootloader since RUU was failing with error 155, someone in a diff HTC thread said locked bootloader was needed for RUU. now phone flashes HTC logo then powers off. buttons pressed not going to recovery right now anyone wanna chime in? please...
@defcomg you know anything about HTC phones? I am currently stuck in the sunken place lol
drago10029 said:
I was on latest stock nougat before I started the process. since the I have tried flashing both leedroid marshmallow zip and the nougat magisk zip also. and what's the deal with s-off?
Everywhere i look they're all how to's about s-off lol. seems hard to find a thread on what s-off is, if it's needed to for a specific ROM or not :/ that being said leedroid it wasn't needed as quoted below. thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=1680928
andybones said:
https://forum.xda-developers.com/showthread.php?t=1680928
Click to expand...
Click to collapse
hmmmm according to that post the TWRP i flashed should have reverted on reboot and that hasn't been the case at all since it has survived multiple reboots... any thoughts on that?
"...Basically, all changes made to these partitions while the phone is running is not permanent, and will be reset upon a reboot..."
EDIT: also does that mean unless I have S-off none of the custom ROMs will flash? so what's the point of unlocking a bootloader is that needs to be disabled also
drago10029 said:
hmmmm according to that post the TWRP i flashed should have reverted on reboot and that hasn't been the case at all since it has survived multiple reboots... any thoughts on that?
"...Basically, all changes made to these partitions while the phone is running is not permanent, and will be reset upon a reboot..."
EDIT: also does that mean unless I have S-off none of the custom ROMs will flash? so what's the point of unlocking a bootloader is that needs to be disabled also
Click to expand...
Click to collapse
Keep in mind the date on that post is from a few years back (2012). You can't put all your eggs into one basket, so to speak. I was just giving you 1 article I found from a simple Google Search. Encryption and TWRP have changed quite a lot, especially since Nougat.
From my small amount of time, I think you may be confused about what the difference is between an unlocked bootloader and S-OFF, which I'd need to even go back and read that article, but thought it touched a little on it
The 10 has changed quite a bit too from past phones. Before you'd need to be S-OFF and unlocked bootloader. Now S-OFF unlocked and S-OFF locked are basically the same, but that can be found in threads if you'd like to find more info on that.
Most the info is there, you just need to search. If you need help finding articles, I can try and help with that. I've been surprised with the great info I've found after awhile of coming up empty.
I'm just now seeing all the new posts that came from before I posted and have been on my phone and don't have the time to catch up on it all right now.
Hope things get squared away for you soon, I'll check in when I can.
It seemed you were in a simple bootloop, but I'm not 100%. I think your issue was flashing MM ROM on N firmware. Can't do that.
Also, Verizon doesn't allow us to unlock bootloader on Htc-dev. So if we want to root, we must S-OFF.
andybones said:
Keep in mind the date on that post is from a few years back. You can't put all your eggs into one basket, so to speak. I was just giving you 1 article I found from a simple Google Search. Encryption and TWRP have changed quite a lot, especially since Nougat.
I'm just now seeing all the new posts that came from before I posted and have been on my phone and don't have the time to catch up on it all right now.
Hope things get squared away for you soon, I'll check in when I can.
Click to expand...
Click to collapse
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
drago10029 said:
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
Click to expand...
Click to collapse
What method have you tried for the SW?
is it an RUU or just firmware?
I suggest the sdcard method.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure.
https://www.androidfilehost.com/?fid=24545065934258327
Either remove your current fastboot.exe and rename this one to it, or keel it as htc_fastboot.exe and use the correct, htc_fastboot flash, over fastboot flash
andybones said:
What method have you tried for the SW?
is it an RUU or just firmware?
I suggest the sdcard method.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure.
https://www.androidfilehost.com/?fid=24545065934258327
Either remove your current fastboot.exe and rename this one to it, or keel it as htc_fastboot.exe and use the correct, htc_fastboot flash, over fastboot flash
Click to expand...
Click to collapse
bear in mind I'm still learning all this HTC stuff lol
is it an RUU or just firmware? It's an RUU.exe for HTC 10 unlocked edition that i got from there website
I suggest the sdcard method. you mean installing custom ROM zip from sd card? otherwise i'm not sure what you mean.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure. hmmm well I used fastboot.exe from minimal adb & fasboot to unlock bootloader and that worked fine, and should i still i just replace fastboot in platform tools folder with fastboot.exe from htc website?
also so s-off shouldn't be needed to install the ROMs? just bootloader unlock?
drago10029 said:
bear in mind I'm still learning all this HTC stuff lol
is it an RUU or just firmware? It's an RUU.exe for HTC 10 unlocked edition that i got from there website
I suggest the sdcard method. you mean installing custom ROM zip from sd card? otherwise i'm not sure what you mean.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure. hmmm well I used fastboot.exe from minimal adb & fasboot to unlock bootloader and that worked fine, and should i still i just replace fastboot in platform tools folder with fastboot.exe from htc website?
also so s-off shouldn't be needed to install the ROMs? just bootloader unlock?
Click to expand...
Click to collapse
Keep in mind this is me helping in my free time.
Use the linked htc_fastboot.. It's made for htc, it's why I mentioned it..
I've seen many ppl have RUU fail by not using this.
Also an RUU/firmware have 3 methods to install.
I suggest the sd-card method. Safest.
Search. Search. Search. ...
Option 1
Copy 2PS6IMG.zip (THIS IS FOR VERIZON, YOUR CARRIER WILL NEED TO BE RENAMED CORRECTLY) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
--Taken from
Also read here. This is a great thread.
There's a lot of info out there.
Just search and do your homework.
It's easy to turn that device into a useless brick.
Especially being S-OFF... Secuirty-off..
I know it can be overwhelming, but the info is out there, and if not, just ask, as others most likely have the same question and this will help them.
And correct, with S-OFF isn't needed to flash ROMs. Only bootloader unlock.
andybones said:
Keep in mind this is me helping in my free time.
Use the linked htc_fastboot.. It's made for htc, it's why I mentioned it..
I've seen many ppl have RUU fail by not using this.
Also an RUU/firmware have 3 methods to install.
I suggest the sd-card method. Safest.
Search. Search. Search. ...
Option 1
Copy 2PS6IMG.zip (THIS IS FOR VERIZON, YOUR CARRIER WILL NEED TO BE RENAMED CORRECTLY) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
--Taken from
Also read here. This is a great thread.
There's a lot of info out there.
Just search and do your homework.
It's easy to turn that device into a useless brick.
Especially being S-OFF... Secuirty-off..
I know it can be overwhelming, but the info is out there, and if not, just ask, as others most likely have the same question and this will help them.
And correct, with S-OFF isn't needed to flash ROMs. Only bootloader unlock.
Click to expand...
Click to collapse
my bad, i hope i didn't come off rude or anything. i do appreciate all your help and i understand it. I do the same here when i have the free time.
I will ask some question's on both those threads you linked. I came across one of them but no s-off and didn't wanna pay for sunshine app. also topjohnwu thread about stock and guides would be helpful if it listed which phones the code names correlate to.
in the end I see your point, keep researching and asking. and I do that very often and promise. today was different since a bunch of PC failed to install updates at work (post wannacry) lol and dealing with my bootlooping phone, my mind was scattered. iv'e bricked before but never on a phone this expensive *__*
thanks again andy!
JUST AN UPDATE: i restored via twrp after i got the bootlooping to stop. I completely forgot I had made one -__- (more scatter brains) so I'm good to go now.... kinda.
drago10029 said:
my bad, i hope i didn't come off rude or anything. i do appreciate all your help and i understand it. I do the same here when i have the free time.
I will ask some question's on both those threads you linked. I came across one of them but no s-off and didn't wanna pay for sunshine app. also topjohnwu thread about stock and guides would be helpful if it listed which phones the code names correlate to.
in the end I see your point, keep researching and asking. and I do that very often and promise. today was different since a bunch of PC failed to install updates at work (post wannacry) lol and dealing with my bootlooping phone, my mind was scattered. iv'e bricked before but never on a phone this expensive *__*
thanks again andy!
JUST AN UPDATE: i restored via twrp after i got the bootlooping to stop. I completely forgot I had made one -__- (more scatter brains) so I'm good to go now.... kinda.
Click to expand...
Click to collapse
You didn't come off rude at all, I was actually hoping you didn't take my response as being rude. S-OFF and sunshine is completely worth the $25. However, for a normal user like yourself, you don't need it.
Glad to hear that you're somewhat good to go, lol.
You can always pm me or tag me in a post if needed and I'll do my best to help.
andybones said:
You didn't come off rude at all, I was actually hoping you didn't take my response as being rude. S-OFF and sunshine is completely worth the $25. However, for a normal user like yourself, you don't need it.
Glad to hear that you're somewhat good to go, lol.
You can always pm me or tag me in a post if needed and I'll do my best to help.
Click to expand...
Click to collapse
glad no guns are being drawn here
and since no you offered lol.... how do i get my CID and MID? using the fastboot you kindly spotted me...
fastboot getvar all and fastboot oem readcid: both return nothing but fastboot not recognized..... etc. etc. I am in download mode (unlocked and s-on if that matters)
drago10029 said:
glad no guns are being drawn here
and since no you offered lol.... how do i get my CID and MID? using the fastboot you kindly spotted me...
fastboot getvar all and fastboot oem readcid: both return nothing but fastboot not recognized..... etc. etc. I am in download mode (unlocked and s-on if that matters)
Click to expand...
Click to collapse
Fastboot isn't recognized? As in it's not working?
drago10029 said:
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
Click to expand...
Click to collapse
2.48.617.3? I don't think there is such a thing. Do you mean 2.41.617.3?
andybones said:
Fastboot isn't recognized? As in it's not working?
Click to expand...
Click to collapse
xunholyx said:
2.48.617.3? I don't think there is such a thing. Do you mean 2.41.617.3?
Click to expand...
Click to collapse
1st things 1st, SOS is no more. was trying to flash leedroid magisk file, thinking it was a ROM until i noticed the file size so I went back to stock via TWRP backup (i forgot I made) since RUU was giving 155 error.
2nd the HTC fastboot wasn't working for some reason.. adb devices cmd detected nothing, it worked at my job though since i have android studio/platform tools there (shrug) so used that fastboot instead.
3rd I did mean SW 2.48.617.1 that's the exact OS version # that download mode reports currently and was the last official update i took several days before going custom route.
drago10029 said:
1st things 1st, SOS is no more. was trying to flash leedroid magisk file, thinking it was a ROM until i noticed the file size so I went back to stock via TWRP backup (i forgot I made) since RUU was giving 155 error.
2nd the HTC fastboot wasn't working for some reason.. adb devices cmd detected nothing, it worked at my job though since i have android studio/platform tools there (shrug) so used that fastboot instead.
3rd I did mean SW 2.48.617.1 that's the exact OS version # that download mode reports currently and was the last official update i took several days before going custom route.
Click to expand...
Click to collapse
Okay. Cool that you got it fixed. But you did say you were trying to update from 2.48.617.1 to 2.48.617.3, so that's why I said there was no .3
xunholyx said:
Okay. Cool that you got it fixed. But you did say you were trying to update from 2.48.617.1 to 2.48.617.3, so that's why I said there was no .3
Click to expand...
Click to collapse
oooh i see lol.. too many numbers.