Yesterday, I attempted to install a new rom. I had been using CM11 nightlies up till this point, and after being annoyed about certain aspects of my phone not working. I wanted to try something new.
I found ViperOne, and went to install it, thinking that it'll be the standard, run-of-the-mill install with no problems to be had. After getting through the install procedure and attempting to reboot to system, my phone dropped me back off at the bootloader. Thinking that I had forgotten to wipe something, I went into the recovery, wiped data, dalvik cache, and the cache, and attempted the install again. Once again, my phone dropped me off at the bootloader.
I thought, maybe I had a bad download. Re-downloaded the rom, same result. "Oh, I'll just try something else then". I found a Google Play Edition rom for my device, and decided to try that. It got stuck in a bootloop. After some googling, I attempted wiping the data/cache/dalvik cache again hoping it would help. Nope, still stuck in bootloop.
At this point (and after having running into a very similiar situation before) I decided to go for broke. I did a full wipe of the phone, and sideloaded CM10.1.3 (only stable CM rom for this device afaik). As it was installing, I noticed an error. "Unable to mount /data". I've had this problem before, and the way I fixed it last time was to install and run a stock rom. At this point in time, I was also getting frustrated and decided to put the stock rom back on my phone so it would at least be functional.
I found a stock rom and installed it just fine. The phone didn't even get stuck in a bootloop either. However, once the phone had finally booted up, I found that the touchscreen was unresponsive. I remember having this issue the last time I tried to use a stock rom. After a little bit of research, I had found that the problem stems from installing the wrong version of the rom. It was suggested on one of the websites to put "fastboot getvar version-main" into adb to find out what version I needed. It returns "version-main: ".
It was at this point that I remembered that I had made a backup of my phone before I attempted rooting. After some searching around, I managed to find it. That being said, I have no idea what to do with it. The folder where I made the backup contains a handful of .win files and some md5 checksums.
Since then I have been attempting seemingly random RUU versions in hopes of stumbling across the right one. It's been 5 hours, and I haven't had any success.
I would greatly appreciate any and all help that can be provided. If you guys need additional information (I'm not sure what I should include), let me know. I know some of the more basic ADB commands and their functions, so bear with me if I ask some questions about how to do certain things.
Boot into bootloader/fastbootusb and type the below command and post the readout here.
fastboot getvar all
BD619 said:
Boot into bootloader/fastbootusb and type the below command and post the readout here.
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4323mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-005bf6a40e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You can try one of the RUU's found here or follow the guide
Sidenote: don't use the 4.06.651.4 RUU unless you flash the 4.06.651.4 s-on firmware first.
BTW I removed
serialno:
imei:
meid:
BD619 said:
You can try one of the RUU's found here or follow the guide
Sidenote: don't use the 4.06.651.4 RUU unless you flash the 4.06.651.4 s-on firmware first.
Click to expand...
Click to collapse
I've tried several different RUU's, including the one's I could find here, and none of them have worked. Not sure if it really matters, but I attempted the 4.06.651.4 RUU earlier, but it failed.
BD619 said:
BTW I removed
serialno:
imei:
meid:
Click to expand...
Click to collapse
Why shouldn't those be shared? Are they considered sensitive information?
Ooops for got the link
http://forum.xda-developers.com/showthread.php?t=2503646
Yes they could be considered sensitive.
BD619 said:
Yes they could be considered sensitive.
Click to expand...
Click to collapse
I have no idea what those numbers represent. Why are important?
crazy-asian said:
I have no idea what those numbers represent. Why are important?
Click to expand...
Click to collapse
I have always been told not to include those...could be a way for someone to hack your device but that's just my guess.
http://en.wikipedia.org/wiki/Mobile_equipment_identifier
I had this happen to me also. Ends up i had to flash a new firmware on the phone and it booted right up. Also make sure you are using twrp recovery when you flash this rom. I used cwm and think that is where all my problems started. Hope ya get it worked out and may not be your problem but is exactly what happened to me and have i fixed it.
BD619 said:
http://forum.xda-developers.com/showthread.php?t=2503646
Click to expand...
Click to collapse
I had tried all but one of those in that list. That one that I hadn't used yet appears to be working. Thank you so much for the help.
Oh god, now I'm back on the stock rom... Any recommendations for a good rom? I enjoy the stock look and feel of android, but running the CM nightlies has been giving me a headache.
crazy-asian said:
Oh god, now I'm back on the stock rom... Any recommendations for a good rom? I enjoy the stock look and feel of android, but running the CM nightlies has been giving me a headache.
Click to expand...
Click to collapse
I'm running BadSeed Sixth Sense
But it's all personal preference everyone will have a different opinion.
Fastboot, on the phone side, isn't connecting to my computer.
crazy-asian said:
Fastboot, on the phone side, isn't connecting to my computer.
Click to expand...
Click to collapse
Are you in bootloader?
BD619 said:
Are you in bootloader?
Click to expand...
Click to collapse
Yes, and it is in fastboot mode.
crazy-asian said:
Yes, and it is in fastboot mode.
Click to expand...
Click to collapse
When you type fastoot devices you don't get a response?
BD619 said:
When you type fastoot devices you don't get a response?
Click to expand...
Click to collapse
correct
crazy-asian said:
correct
Click to expand...
Click to collapse
Ok go back to my guide and you can get the proper drivers and instructions to get them installed correctly
BD619 said:
Ok go back to my guide and you can get the proper drivers and instructions to get them installed correctly
Click to expand...
Click to collapse
Didn't solve the problem, phone still isn't in "fastboot USB"
crazy-asian said:
Didn't solve the problem
Click to expand...
Click to collapse
Try a different port(usb2 are best)
Try a different cable
Different PC
If you have android sdk setup try updating it.
Related
Hi all,
I have the revolution HD Rom installed on my device and I got an unlock code online from a site I trust and bought from in the past (I say that to point out that I don't think that the problem is with the key itself)
When I tried to apply it though, it said that it is wrong...
I know it sounds weird, but my research shows that it might be related to me having a custom rom installed - something about changing the baseband?
Either way, I'd love for some community help on this - is this possible?
If so, what is the quickest/painless way to get back to stock? will that require a full factory reset?
will I lose the unlock again when I switch back to the rom?
Please help as I'm currently out of the country and have no phone
Thanks!!!
eladkatz said:
Hi all,
I have the revolution HD Rom installed on my device and I got an unlock code online from a site I trust and bought from in the past (I say that to point out that I don't think that the problem is with the key itself)
When I tried to apply it though, it said that it is wrong...
I know it sounds weird, but my research shows that it might be related to me having a custom rom installed - something about changing the baseband?
Either way, I'd love for some community help on this - is this possible?
If so, what is the quickest/painless way to get back to stock? will that require a full factory reset?
will I lose the unlock again when I switch back to the rom?
Please help as I'm currently out of the country and have no phone
Thanks!!!
Click to expand...
Click to collapse
You can either restore a nandroid of your stock ROM or flash an RUU. Try your code again after going to stock and it'll work.
eladkatz said:
Hi all,
I have the revolution HD Rom installed on my device and I got an unlock code online from a site I trust and bought from in the past (I say that to point out that I don't think that the problem is with the key itself)
When I tried to apply it though, it said that it is wrong...
I know it sounds weird, but my research shows that it might be related to me having a custom rom installed - something about changing the baseband?
Either way, I'd love for some community help on this - is this possible?
If so, what is the quickest/painless way to get back to stock? will that require a full factory reset?
will I lose the unlock again when I switch back to the rom?
Please help as I'm currently out of the country and have no phone
Thanks!!!
Click to expand...
Click to collapse
You posted in the wrong section. That's what Q&A is for.
Sent from my HTC One using XDA Premium 4 mobile app
gamer765 said:
You can either restore a nandroid of your stock ROM or flash an RUU. Try your code again after going to stock and it'll work.
Click to expand...
Click to collapse
Thanks for the reply man, I was going to follow the instructions on http://forum.xda-developers.com/showthread.php?t=2265618 but they link to more info on RUUs and the link is broken
How do I know which ruu do I need?
Thanks again!
eladkatz said:
Thanks for the reply man, I was going to follow the instructions on http://forum.xda-developers.com/showthread.php?t=2265618 but they link to more info on RUUs and the link is broken
How do I know which ruu do I need?
Thanks again!
Click to expand...
Click to collapse
What region is the phone from and what carrier? It's probably better if you can post your CID, which you can obtain by using the CID Getter app on the play store.
gamer765 said:
What region is the phone from and what carrier? It's probably better if you can post your CID, which you can obtain by using the CID Getter app on the play store.
Click to expand...
Click to collapse
I have a US AT&T phone, my CID is CWS_001
Thanks
eladkatz said:
I have a US AT&T phone, my CID is CWS_001
Thanks
Click to expand...
Click to collapse
You don't need to do all that, just use a Guru Reset ROM for your firmware, that will work (confirmed from several other users, with the same situation as yours). can you post a "fastboot getvar all" (remove IMEI and s/n) and I'll point you in the right direction
eladkatz said:
I have a US AT&T phone, my CID is CWS_001
Thanks
Click to expand...
Click to collapse
Just restore a stock AT&T nandroid and you should be good to go. Afterwards, you can install custom ROMs, your unlock will stick.
EDIT: You can restore this nandroid http://www.htc1guru.com/dld/htcone-32gb-att-1-26-502-10-twrp-stock-zip/
Make a nandroid of your current ROM first if you want to return to it afterwards. The above is a TWRP nandroid.
nkk71 said:
You don't need to do all that, just use a Guru Reset ROM for your firmware, that will work (confirmed from several other users, with the same situation as yours). can you post a "fastboot getvar all" (remove IMEI and s/n) and I'll point you in the right direction
Click to expand...
Click to collapse
Thanks, see below, not sure if it worked...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4082mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.041s
eladkatz said:
Thanks, see below, not sure if it worked...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4082mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.041s
Click to expand...
Click to collapse
Try this one: http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-12-zip/
It's slightly newer than your version but I think it should work, you can deselect "stock recovery" and "stock radio" during the install, as you won't need those.
BTW: why don't you S-Off? (just a question, I'm in no way implying you do anything you're not comfortable with!!)
gamer765 said:
Just restore a stock AT&T nandroid and you should be good to go. Afterwards, you can install custom ROMs, your unlock will stick.
EDIT: You can restore this nandroid http://www.htc1guru.com/dld/htcone-32gb-att-1-26-502-10-twrp-stock-zip/
Make a nandroid of your current ROM first if you want to return to it afterwards. The above is a TWRP nandroid.
Click to expand...
Click to collapse
I have clockwork mod recovery, can I use that to do the twrp nandroid recovery?
Also, in the url you are directing to, it says:
This Nandroid should not be needed. I have
a Stock ROM + Recovery Reset Installer which can
reset stock ROM and allow OTA updates. See Here:
http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-12-zip
Click to expand...
Click to collapse
Should I use that one instead?
eladkatz said:
I have clockwork mod recovery, can I use that to do the twrp nandroid recovery?
Also, in the url you are directing to, it says:
Should I use that one instead?
Click to expand...
Click to collapse
Sorry, I didn't get your question, and lots of different approaches to the same thing. If you want my opinion:
1- do a nandroid backup of your current setup
2- copy (or pull) everything to your PC, just in case
3- use the Guru Reset (http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-12-zip/), that's a flashable zip in custom recovery, do not select "stock recovery" (actually you have to uncheck it)
4- do not take any OTAs
5- use your SIM unlock code
6- restore your nandroid backup
if in step 5 the SIM unlock code doesn't work, then you can explore other options
That's my humble opinion.
Hit the Thanks button if I've helped
nkk71 said:
BTW: why don't you S-Off? (just a question, I'm in no way implying you do anything you're not comfortable with!!)
Click to expand...
Click to collapse
I guess because I'm not sure what that is, I've seen it mentioned as something that allowes to install custom RUUs but I'm not sure how that would help here...
eladkatz said:
I guess because I'm not sure what that is, I've seen it mentioned as something that allowes to install custom RUUs but I'm not sure how that would help here...
Click to expand...
Click to collapse
I guess the stock reset is fine, the main goal is to get you back to the stock carrier ROM for the unlock code to work.
nkk71 said:
Sorry, I didn't get your question, and lots of different approaches to the same thing. If you want my opinion:
1- do a nandroid backup of your current setup
2- copy (or pull) everything to your PC, just in case
3- use the Guru Reset (http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-12-zip/), that's a flashable zip in custom recovery, do not select "stock recovery" (actually you have to uncheck it)
4- do not take any OTAs
5- use your SIM unlock code
6- restore your nandroid backup
if in step 5 the SIM unlock code doesn't work, then you can explore other options
That's my humble opinion.
Hit the Thanks button if I've helped
Click to expand...
Click to collapse
Thanks for the tip,
I followed the instructions to the letter and now it seems like I'm stuck on the HTC ONE boot screen...
I tried restarting once (after letting it idle for a good 10 minutes I think)
now I'm just staring at it, not really sure what my next step should be... could it just be that I need to wait?
On a positive note, I can still access fastboot/recovery so I guess worst case, I can do a factory reset - that oughta fix it, right?
Question about that - if I do that, will I still be able to do the nandroid restore and go back to my original state?
Thanks
eladkatz said:
Thanks for the tip,
I followed the instructions to the letter and now it seems like I'm stuck on the HTC ONE boot screen...
I tried restarting once (after letting it idle for a good 10 minutes I think)
now I'm just staring at it, not really sure what my next step should be... could it just be that I need to wait?
Click to expand...
Click to collapse
What's up with that, 2nd person today (out of 2) having problems with the Guru Resets
did you wipe in the Installer? did you make sure the download is not corrupt (MD5 sum)?
The way I usually know if the bootup is stuck or not, is: after a few minutes (something like 2 or 3 minutes, maybe less) the screen will change brightness, if it does I know it's not stuck, if the brightness doesn't change, I force a reboot and reflash.
I recommend you reboot to recovery, and restore your backup, just to have a functioning phone, then check the MD5 sum of your download to make sure it's OK.
I'm about to flash the Guru Reset that also got the other guy "stuck", to see if it works or not....
eladkatz said:
Thanks for the tip,
I followed the instructions to the letter and now it seems like I'm stuck on the HTC ONE boot screen...
I tried restarting once (after letting it idle for a good 10 minutes I think)
now I'm just staring at it, not really sure what my next step should be... could it just be that I need to wait?
On a positive note, I can still access fastboot/recovery so I guess worst case, I can do a factory reset - that oughta fix it, right?
Question about that - if I do that, will I still be able to do the nandroid restore and go back to my original state?
Thanks
Click to expand...
Click to collapse
FYI: http://forum.xda-developers.com/showpost.php?p=47085377&postcount=44
(it's a different Guru Reset, but same principle applies)
nkk71 said:
FYI: http://forum.xda-developers.com/showpost.php?p=47085377&postcount=44
(it's a different Guru Reset, but same principle applies)
Click to expand...
Click to collapse
I eventually just restored to factory defaults, proceeded to unlock and then went back to the nandroid backup, worked like a charm!
Thanks for all the help and support
hi, im trying to get my htc one m7sprint back to stock. I haven't used it recently and am thus very confused on how to get back to stock recovery and rom.
heres's some information about the phone
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.00.20.0913_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.04.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Mod Edit
(bootloader) imei: Mod Edit
(bootloader) meid: Mod Edit
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4102mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-371c4f408e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Mod Edit = removed sensitive material
Easiest way would be to RUU...they can be found in Android Development, use 3.04.651.2 or higher.
when you say use 3.04 or higher could you tell me if this would work?
http://forum.xda-developers.com/showthread.php?t=2250904
I don't see a version number in this one
amskhan1 said:
when you say use 3.04 or higher could you tell me if this would work?
http://forum.xda-developers.com/showthread.php?t=2250904
I don't see a version number in this one
Click to expand...
Click to collapse
That one is older(version 1.29.651.10) then what you are currently on...so no you cannot use it.
This one matches what you are currently on.
http://forum.xda-developers.com/showthread.php?t=2508907
The higher the number the newer it is.
They can all be found HERE.
Hi, im having trouble running the ruu i'm getting the 170 error and my phone is still in fastboot usb mode. also when i try to reboot the phone into normal android it goes straight into bootloader. Do you know how to solve these problems? i found this information online, but i don't know how to get the drivers considering my phone is stuck in fastboot and isnt rebooting
https://sites.google.com/site/communityhelpsareebro/how-to-fix-error-170-usb-connection-error
amskhan1 said:
Hi, im having trouble running the ruu i'm getting the 170 error and my phone is still in fastboot usb mode. also when i try to reboot the phone into normal android it goes straight into bootloader. Do you know how to solve these problems? i found this information online, but i don't know how to get the drivers considering my phone is stuck in fastboot and isnt rebooting
https://sites.google.com/site/communityhelpsareebro/how-to-fix-error-170-usb-connection-error
Click to expand...
Click to collapse
Try installing HTC Sync Manager it will install drivers needed.
Once it's installed you no longer need it so you can uninstall from your PC if you wish.
BD619 said:
Try installing HTC Sync Manager it will install drivers needed.
Once it's installed you no longer need it so you can uninstall from your PC if you wish.
Click to expand...
Click to collapse
thanks
Hey im, still getting error 170, with ruu version 2.0.5.2013. I already installed htc sync manager. I get to the part where it says verifying info on your pda phone.... please wait.
but after that it says error 170, usb connection error.
My phone is tagged with ****tampered*** , relocked, and security warning
Do you have any suggestions. (I have another htc one if i need to install some driver on my pc.
When i start my phone it only boots into bootloader. do i need an os on the phone for this?
amskhan1 said:
Hey im, still getting error 170, with ruu version 2.0.5.2013. I already installed htc sync manager. I get to the part where it says verifying info on your pda phone.... please wait.
but after that it says error 170, usb connection error.
My phone is tagged with ****tampered*** , relocked, and security warning
Do you have any suggestions. (I have another htc one if i need to install some driver on my pc.
When i start my phone it only boots into bootloader. do i need an os on the phone for this?
Click to expand...
Click to collapse
Only other things I can suggest are...
Make sure you are using the latest RUU.
Try a different cable OEM is best.
Try a different USB port (USB2 work the best).
Try a different PC.
BD619 said:
Only other things I can suggest are...
Make sure you are using the latest RUU.
Try a different cable OEM is best.
Try a different USB port (USB2 work the best).
Try a different PC.
Click to expand...
Click to collapse
kk thnx I'll try it
another question
amskhan1 said:
kk thnx I'll try it
Click to expand...
Click to collapse
I finally got the ruu to recognize my device, but it says from image version(3.04.651.2) to : image version then its just blank.
Is there supposed to be something there?
amskhan1 said:
I finally got the ruu to recognize my device, but it says from image version(3.04.651.2) to : image version then its just blank.
Is there supposed to be something there?
Click to expand...
Click to collapse
Yeah the version number of the RUU you are trying to flash.
Maybe you are using an older RUU?
I think i was using the 3_04_651_2 one that you suggested.
amskhan1 said:
I think i was using the 3_04_651_2 one that you suggested.
Click to expand...
Click to collapse
That one should work just fine...did you proceed and get an error or just stop when you saw the missing version?
BD619 said:
That one should work just fine...did you proceed and get an error or just stop when you saw the missing version?
Click to expand...
Click to collapse
I just stopped when i saw a missing version, didn't know if it would break the phone, so i should continue?
amskhan1 said:
I just stopped when i saw a missing version, didn't know if it would break the phone, so i should continue?
Click to expand...
Click to collapse
Yeah give it a shot.
I have an m7 ATT with HBoot 1.44, S-off, and rooted with a CM12 nightly. CID is CWS_001. I'm switching to T-Mobile and as expected when I throw my t-mobile SIM in and punch in the the unlock code it doesn't work. Unless someone knows of a better solution I need to restore the stock rom, but I don't have a nandroid backup of it anymore. I've been doing research for awhile, but there is a lot of information on this topic and I'm a bit lost. What I've come up with seems to suggest that I won't be able to use my touchscreen if I flash a Stock nandroid because they are all so old. I could really use some advice on how to proceed from this point.
Have you looked at this?
http://www.htc1guru.com/guides/return-stock-guide/
Sent from my Nexus 7 using Tapatalk
ZBell said:
Have you looked at this?
http://www.htc1guru.com/guides/return-stock-guide/
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I did come across that in my research. Is that the only solution? Also, it uses an RUU versioned 1.2x. Is that not a problem like it is in nandroids versioned 1.2x? I'm worried about not being able to use the device afterward. Also, if possible I would like to avoid using a method that is so destructive to existing data. I have data backups of course, but it's just another thing that can go wrong later.
Dr3x1 said:
I did come across that in my research. Is that the only solution? Also, it uses an RUU versioned 1.2x. Is that not a problem like it is in nandroids versioned 1.2x? I'm worried about not being able to use the device afterward. Also, if possible I would like to avoid using a method that is so destructive to existing data. I have data backups of course, but it's just another thing that can go wrong later.
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number please.
you are right, your unlock code will only work with stock rom.
Seanie280672 said:
post your fastboot getvar all please without imei and serial number please.
you are right, your unlock code will only work with stock rom.
Click to expand...
Click to collapse
I'm doing an adb backup at the moment, but I'll post that soon. One question I do have though is if I fully restore this device and then unlock the SIM, can I then re S-off+root and restore the adb backup and maintain my sim unlock? I backed up everything (apk shared system, etc).
Dr3x1 said:
I'm doing an adb backup at the moment, but I'll post that soon. One question I do have though is if I fully restore this device and then unlock the SIM, can I then re S-off+root and restore the adb backup and maintain my sim unlock? I backed up everything (apk shared system, etc).
Click to expand...
Click to collapse
are you s-off ? when you restore stock rom, simply unlock your phone with the code you have and then the easiest thing for you to do after that is just convert your phone to a full T_Mo phone using the RUU, you will not loose s-off at all, no need to re-s-off, after that just flash a custom recovery, root and copy all your stuff back.
Seanie280672 said:
are you s-off ? when you restore stock rom, simply unlock your phone and then the easiest thing for you to do after that is just convert your phone to a full T_Mo phone using the RUU, you will not loose s-off at all, no need to re-s-off, after that just flash a custom recovery, root and copy all your stuff back.
Click to expand...
Click to collapse
Yea I'm S-Off. That's good to know. Now my phone isn't getting recognized by windows/adb while in the bootloader though. Yet another problem I have to figure out. I'll get back to you when it's working again. I've had no end to driver issues today. :-/
Dr3x1 said:
Yea I'm S-Off. That's good to know. Now my phone isn't getting recognized by windows/adb while in the bootloader though. Yet another problem I have to figure out. I'll get back to you when it's working again. I've had no end to driver issues today. :-/
Click to expand...
Click to collapse
if you have Windows 8 or 8.1 with HBOOT 1.44 it wont work, you will need to use windows 7, XP or a bootable Linux distro.
... -_- FML. Yea I'm using Windows 8.1. I thought I'd waited long enough to let the OS mature and that I wouldn't have any issues so I just upgraded recently. Will a VM using Oracle Virtualbox work fine?
Dr3x1 said:
... -_- FML. Yea I'm using Windows 8.1. I thought I'd waited long enough to let the OS mature and that I wouldn't have any issues so I just upgraded recently. Will a VM using Oracle Virtualbox work fine?
Click to expand...
Click to collapse
Yeah windows 8 stucks, windows 10 stucks even more, the only 2 good thing about either of those OS's is the boot speeds, yeah Virtualbox should work.
This is frustrating. I've been working on this for hours. I can't get adb on ubuntu to recognize my device either. It's probably more an issue with virtualbox and it sharing the USB device than anything. Can anyone recommend a simple linux distro for this purpose?
Ok so for the time being my phone is a brick, but I don't think it's unrecoverable. I'm now able to communicate with my device properly even on windows 8.1. Although everything I've done so far was on a friend's linux laptop since my VM wasn't working (I didn't want to make a bootable CD and I don't have any USB flash drives lying around). I attempted to flash what I thought was the correct stock RUU zip but I must have done something wrong. Here is the information you requested:
sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <snip>
(bootloader) imei: <snip>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3919mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the moment I'm sitting on the HTC logo with 4 triangles in the corner. AKA: A brick.
I can still communicate with it via the command line with fastboot. When I unplug the device I get the white bootloader screen, but the only option is: RUU. Also I appear to be on fastboot 1.55 now so I must have flashed the wrong thing.
Dr3x1 said:
Ok so for the time being my phone is a brick, but I don't think it's unrecoverable. I'm now able to communicate with my device properly even on windows 8.1. Although everything I've done so far was on a friend's linux laptop since my VM wasn't working (I didn't want to make a bootable CD and I don't have any USB flash drives lying around). I attempted to flash what I thought was the correct stock RUU zip but I must have done something wrong. Here is the information you requested:
sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <snip>
(bootloader) imei: <snip>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3919mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the moment I'm sitting on the HTC logo with 4 triangles in the corner. AKA: A brick.
I can still communicate with it via the command line with fastboot. When I unplug the device I get the white bootloader screen, but the only option is: RUU. Also I appear to be on fastboot 1.55 now so I must have flashed the wrong thing.
Click to expand...
Click to collapse
which RUU did you flash ? link please
@Seanie280672 http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Dr3x1 said:
@Seanie280672 http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Click to expand...
Click to collapse
try this one instead, im not so sure the one you flashed contained the firmware, this one will be official stock: http://androidruu.com/getdownload.ph...5_signed_2.exe
I thought you were on HBOOT 1.44? which is why windows 8 couldnt see your phone, what else did you flash to get to 1.55 ?
Seanie280672 said:
try this one instead, im not so sure the one you flashed contained the firmware, this one will be official stock: http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
Also, I thought you were on HBOOT 1.44? which is why windows 8 couldnt see your phone, what else did you flash to get to 1.55 ?
Click to expand...
Click to collapse
I was on Hboot 1.44. I could use adb when the phone was on, but I couldn't use fastboot commands when the phone was in the bootloader. As to why I'm on 1.55 now, It must have been included in the zip I flashed. I wasn't on 1.55 before. Now that I am I'm able to use fastboot commands from my windows machine though.
I don't currently have access to a linux machine so will the exe you linked keep me on Hboot 1.55? I don't want to not be able to talk to my phone again on windows if I can avoid it.
Edit: http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
This RUU is the one recommended by the guide I was following (I have the same device as the example device used in the guide). I didn't use it because it's an exe and I was on a linux machine at the time. I could try using that one, but I know it contains HBOOT 1.44.
Dr3x1 said:
I was on Hboot 1.44. I could use adb when the phone was on, but I couldn't use fastboot commands when the phone was in the bootloader. As to why I'm on 1.55 now, It must have been included in the zip I flashed. I wasn't on 1.55 before. Now that I am I'm able to use fastboot commands from my windows machine though.
I don't currently have access to a linux machine so will the exe you linked keep me on Hboot 1.55? I don't want to not be able to talk to my phone again on windows if I can avoid it.
Click to expand...
Click to collapse
yup if that RUU works, then yes you will still beable to use windows 8, that file will come with 1.54 or 1.55, failing that you can flash this firmware first using fastboot: https://www.androidfilehost.com/?fid=23329332407574042
dont forget to flash twice
and then this matching RUU: https://www.androidfilehost.com/?fid=95916177934536694
the 4 red triangles basically mean you have a bad firmware, or wrong firmware, or some sort of conflict going on between rom and firmware at the moment, which makes sense to me as im pretty sure 1.26.502 should come with HBOOT 1.44 not 1.55.
@clsA is the best man for AT&T products, maybe he can confirm the above.
---------- Post added at 11:02 PM ---------- Previous post was at 11:00 PM ----------
Dr3x1 said:
Edit: http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
This RUU is the one recommended by the guide I was following (I have the same device as the example device used in the guide). I didn't use it because it's an exe and I was on a linux machine at the time. I could try using that one, but I know it contains HBOOT 1.44.
Click to expand...
Click to collapse
see the difference there is that one is signed, making it official.
Right, thanks. I'll do that and get back to you.
Great Success!
The phone booted, greeting me with that ugly ATT logo and music I'd hopped to never hear again lol. The sim unlock code took so now I should flash a Tmobile RUU then?
Also I am still on HBoot 1.55 so that's good, I guess.
Edit: It seems I have no cellular network connection with TMobile right now. Yet more things for me to figure out. >_< Maybe if I'm lucky flashing a Tmobile RUU will fix that too. Any recommendations on which one to use?
Edit 2: I just needed to update the APN settings. I knew that of course I'm just tired because I"ve been working on this for too long. I would still like a suggestion on whether or not I should bother flashing another RUU. My end goal is to be rooted using a CM12 nightly like I was doing before. Should I change my CID, flash a stock Tmobile RUU and then Cyanogen mod? I also appear to have lost root, but I expected that.
Update:
http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
I'm guessing this is the right one. I've updated my CID and MID for Tmobile and re-rooted. Do I really need to flash that RUU now? I can just safely go back to Cyanogen Mod at this point right?
Hey guys, I'm relatively new to this and my english is pretty bad so sorry in advance but I've tried to fix this for a few hours now and I've only made the situation worse for myself
I found my "old" HTC One M7 a couple of days back so I thought it would be a good idea to root it and play around with xposed framework and some cool modules I heard about. So I managed to unlock the bootloader, flash CWM Recovery and root my phone. No problems so far.
Now, yesterday I wanted to remove xposed framework from my phone so I thought I could just recover from the backup I made in CWM Recovery before I installed the framework. Turns out that was not the greatest of ideas and my phone got stuck on the boot screen.
I didnt think of it like such a big deal and I tried to factory reset and wipe the phone to maybe get it working again. Turns out that was not the greatest idea either and now I cant go into recovery, I can't flash a new recovery and my computer wont recognizes my phone at all (Except for fastboot)
I've installed and uninstalled all drivers I could possibly think of and find and I still cant find a solution to my problem. I tried to flash a RUU but that didnt work either. I can barely do anything with my phone anymore and I can't think of anything else I havent tried. Please help
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.19.401.30
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4129mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e2a13e5
hbootpreupdate: 11
gencheckpt: 0
My bootloader shows the Tempered , Relocked and Security Warning flags
deleted
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
vilan22 said:
Hey guys, I'm relatively new to this and my english is pretty bad so sorry in advance but I've tried to fix this for a few hours now and I've only made the situation worse for myself
I found my "old" HTC One M7 a couple of days back so I thought it would be a good idea to root it and play around with xposed framework and some cool modules I heard about. So I managed to unlock the bootloader, flash CWM Recovery and root my phone. No problems so far.
Now, yesterday I wanted to remove xposed framework from my phone so I thought I could just recover from the backup I made in CWM Recovery before I installed the framework. Turns out that was not the greatest of ideas and my phone got stuck on the boot screen.
I didnt think of it like such a big deal and I tried to factory reset and wipe the phone to maybe get it working again. Turns out that was not the greatest idea either and now I cant go into recovery, I can't flash a new recovery and my computer wont recognizes my phone at all (Except for fastboot)
I've installed and uninstalled all drivers I could possibly think of and find and I still cant find a solution to my problem. I tried to flash a RUU but that didnt work either. I can barely do anything with my phone anymore and I can't think of anything else I havent tried. Please help
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.19.401.30
version-misc: PVT SHIP S-ON
serialno: SH36EW905338
imei: 357864055623936
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4129mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e2a13e5
hbootpreupdate: 11
gencheckpt: 0
My bootloader shows the Tempered , Relocked and Security Warning flags
Click to expand...
Click to collapse
You need to flash firmware again, search on arhd's website they have all the firmwares and after that ruu will work, I don't remember step by step process but you can always search on google. For RUU to work you need to flash firmware first, its mandatory.
RUU contains the firmware, so there is no need to flash anything except the actual RUU. You problem is relocked bootloader and custom recovery. First thing you need to do is unlock your bootloader again. Then we can talk about other steps to get your phone working again
donkeykong1 said:
RUU contains the firmware, so there is no need to flash anything except the actual RUU. You problem is relocked bootloader and custom recovery. First thing you need to do is unlock your bootloader again. Then we can talk about other steps to get your phone working again
Click to expand...
Click to collapse
Alright, I unlocked the bootloader again. What now?
vilan22 said:
Alright, I unlocked the bootloader again. What now?
Click to expand...
Click to collapse
Now download TWRP recovery and flash it via fastboot
donkeykong1 said:
Now download TWRP recovery and flash it via fastboot
Click to expand...
Click to collapse
Done and working!
vilan22 said:
Done and working!
Click to expand...
Click to collapse
Great! Now, download ARHD ROM, and tranfer the zip to your phone using MTP option in recovery
While you wait, you might want to edit your "fastboot getvar all" and remove your IMEI and serial no [emoji6]
donkeykong1 said:
Great! Now, download ARHD ROM, and tranfer the zip to your phone using MTP option in recovery
While you wait, you might want to edit your "fastboot getvar all" and remove your IMEI and serial no [emoji6]
Click to expand...
Click to collapse
Alright, do I flash the ROM now?
vilan22 said:
Alright, do I flash the ROM now?
Click to expand...
Click to collapse
Yep! Flash away [emoji4]
donkeykong1 said:
Yep! Flash away [emoji4]
Click to expand...
Click to collapse
Flashed successfully and it seems to be working just fine Thanks for the help! Learned alot from this
vilan22 said:
Flashed successfully and it seems to be working just fine Thanks for the help! Learned alot from this
Click to expand...
Click to collapse
Great! Enjoy your phone, and feel free to ask if you need anything [emoji4]
Hey guys, so recently I purchased a htc one m7 (sprint) off of ebay. I planned to fix it because it was listed as in a bootloop. I thought this would be easy to fix, but I have run into some trouble. The phone does not boot, it just sits on the htc screen. Phone is currently s-on. I have full access to fastboot, but thats it. I feel like I have looked everywhere for a solution, but nothing has worked for me. Any help would be greatly appreciated.
Things I have tried:
1. factory reseting from bootloader menu.
2. entering recovery mode through bootloader menu. (goes back into bootloop, assuming recovery is corrupted)
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
4. flashing twrp (fails due to locked bootloader)
5. using a RUU.exe to flash back to stock (bootloop, gets hung up on "waiting for bootloader..". If i manually put it back into fastboot I get a connection error)
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop. Tried flashing without rebootRUU and got a verification error.
So, any ideas or is this thing bricked? Thanks.
Are you trying to run the RUU while already in fastboot, or are you trying to let the exe boot to fastboot for you? I'm assuming that you are running the RUU from fastboot, and the rebootRUU from the exe is looping you again?
Have you tried flashing the stock recovery?
Have you tried fastboot erase cache? (probably won't help in your situation, but why not?)
Those are some things you could try.
I am having this thread moved to the M7 Q&A forum. You'll have a good chance there of someone providing the steps you need to take to get yourself fixed up.
I suggest that you post the results of fastboot getvar all (minus you IMEI/MEID and serial# of course) so we have a better understanding of your firmware version and such.
Good luck!
yeah, im running the exe while in fastboot, and the rebootRUU loops me. I havent flashed stock recovery. will that allow me to flash anything to get this working? and i did try to wipe cache from fastboot.
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
murphyhobo said:
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Danny201281 said:
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
murphyhobo said:
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
Click to expand...
Click to collapse
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
xunholyx said:
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
Click to expand...
Click to collapse
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
murphyhobo said:
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
Click to expand...
Click to collapse
Unfortunately I think it is a lost cause . If the bootloader is not stable then it's almost certainly a hardware problem.
Even if it was some low level software issue without a stable bootloader there is no way to flash anything to the device.
Maybe sell it on eBay as Spares to try get something back from it.
Sent from my SM-T230 using Tapatalk
Alright, thanks for the help!
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
raghav9 9 said:
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
Click to expand...
Click to collapse
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
alray said:
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
Click to expand...
Click to collapse
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
raghav9 9 said:
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Sorry but what you are saying is making me believe you didn't read what the OP said at all except maybe the first few lines...
Use firewater or revan to s-off first
Click to expand...
Click to collapse
Firewater is discontinued and doesn't work anymore, Revone S-OFF is for hboot 1.44 only, OP's phone is on 1.61. Achieving S-OFF requires a booting phone, exactly what the OP doesn't have. And BTW there a much newer RUU he could use than the one you have posted above that wouldn't requires S-OFF.
Then unlock by htc dev
Click to expand...
Click to collapse
I guess you missed that part:
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
Click to expand...
Click to collapse
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Not possible since like OP said:
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop.
Click to expand...
Click to collapse
Its either a corrupt bootloader/firmware or an hardware problem and like Danny said its a lost cause.