Database Develop

[Q] Can't boot to recovery, can't s-off

Hi,
two weeks ago I sent in my HTC One (O2 Germany branded) because it had a stuck pixel and today I got a brand new replacement phone.
I wanted to get back on to my old ROM etc pretty fast and thought I'd use the AIO Toolkit to unlock/s-off/etc this time instead of doing all on my own.
First thing I did was getting a new unlock token and then unlock the phone, use AIO to flash recovery (bootloader still showed unlocked which I didn't notice at that time of the process) and directly went to s-off to convert my phone to a google edition phone afterwards.
Then things started to visibly not work. Revone was granted root for the preparation process, everything went fine, I rebooted. Then, s-off failed. Now root started to drop errors (was something with memory can't be allocated) and revone gave me -1 and -6 errors.
Then I thought about using recovery and just flash a custom ROM for now and do the firmware part later, when I noticed that recovery isn't working, too.
I'm pretty clueless now, I have relocked and unlocked my phone again, tried to flash all sorts of recoveries (both CWM and TWRP, newest and older versions), tried to revone again (still the above mentioned errors). I also searched a bit on the forums here and found nothing of value (few things which were said to help - still no success).
Fastboot getvar all also drops an error:
C:\Android SDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34VW908233
(bootloader) imei: 354436054362833
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.057s
I'm not a noob, I read carefully what to do when I get a new device, I know where to look for everything here and I've been flashing ROMs and doing all this stuff on my HTC devices for quite some time now. And yes, I have upgraded my HTC drivers.
It's possible that I missed something though. Nobody is perfect. I'm gratefull for every piece of help I get from you people.

eisteh said:
Hi,
two weeks ago I sent in my HTC One (O2 Germany branded) because it had a stuck pixel and today I got a brand new replacement phone.
I wanted to get back on to my old ROM etc pretty fast and thought I'd use the AIO Toolkit to unlock/s-off/etc this time instead of doing all on my own.
First thing I did was getting a new unlock token and then unlock the phone, use AIO to flash recovery (bootloader still showed unlocked which I didn't notice at that time of the process) and directly went to s-off to convert my phone to a google edition phone afterwards.
Then things started to visibly not work. Revone was granted root for the preparation process, everything went fine, I rebooted. Then, s-off failed. Now root started to drop errors (was something with memory can't be allocated) and revone gave me -1 and -6 errors.
Then I thought about using recovery and just flash a custom ROM for now and do the firmware part later, when I noticed that recovery isn't working, too.
I'm pretty clueless now, I have relocked and unlocked my phone again, tried to flash all sorts of recoveries (both CWM and TWRP, newest and older versions), tried to revone again (still the above mentioned errors). I also searched a bit on the forums here and found nothing of value (few things which were said to help - still no success).
Fastboot getvar all also drops an error:
C:\Android SDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34VW908233
(bootloader) imei: 354436054362833
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.057s
I'm not a noob, I read carefully what to do when I get a new device, I know where to look for everything here and I've been flashing ROMs and doing all this stuff on my HTC devices for quite some time now. And yes, I have upgraded my HTC drivers.
It's possible that I missed something though. Nobody is perfect. I'm gratefull for every piece of help I get from you people.
Click to expand...
Click to collapse
Strange.. all i can see here is that in getvar all is no error, this "failed"message appears everytime.
So basically now the only thing you can access is the bootloader?

herwegan said:
Strange.. all i can see here is that in getvar all is no error, this "failed"message appears everytime.
So basically now the only thing you can access is the bootloader?
Click to expand...
Click to collapse
Ok, then I don't have to be worried about the getvar all..
No, I can also boot the Stock ROM fine. I'm just not able to go custom at all.
Also, which might be of interest: Selecting factory reset in the recovery does NOTHING. Phone reboots, everything is still there. Software reset (from the ROM) works fine.

eisteh said:
Ok, then I don't have to be worried about the getvar all..
No, I can also boot the Stock ROM fine. I'm just not able to go custom at all.
Also, which might be of interest: Selecting factory reset in the recovery does NOTHING. Phone reboots, everything is still there. Software reset (from the ROM) works fine.
Click to expand...
Click to collapse
I suspect revone borked something. It's a hack; it happens. You probably need to RUU back to stock, as it sounds like you've messed up something important in your system settings.

iElvis said:
I suspect revone borked something. It's a hack; it happens. You probably need to RUU back to stock, as it sounds like you've messed up something important in your system settings.
Click to expand...
Click to collapse
And as there seems to be no RUU for HTC One O2 Germany.. I'm doomed?
EDIT: As recovery wasn't working before revone, maybe there already was a problem with the phone? I was so happy to get my phone back and now it's even worse than before...

eisteh said:
And as there seems to be no RUU for HTC One O2 Germany.. I'm doomed?
EDIT: As recovery wasn't working before revone, maybe there already was a problem with the phone? I was so happy to get my phone back and now it's even worse than before...
Click to expand...
Click to collapse
You couldchange your cid to htc___001 and flash the open europe RUU 1.28 and at least see if it helps. Then change cid back to O2 germany (not 100% sure if this is possible).

herwegan said:
You couldchange your cid to htc___001 and flash the open europe RUU 1.28 and at least see if it helps. Then change cid back to O2 germany (not 100% sure if this is possible).
Click to expand...
Click to collapse
Which would require s-off which doesn't work.

eisteh said:
Revone was granted root for the preparation process, everything went fine, I rebooted. Then, s-off failed. Now root started to drop errors (was something with memory can't be allocated) and revone gave me -1 and -6 errors.
Click to expand...
Click to collapse
After you ran revone -P, did you reboot with a manual hold of the power button or with adb command? Should use the power button.
I have found that the revone process works better when you don't change to su before ANY of the commands.
Also I have found that a lot of revone issues were adb related and changing to a different USB port or PC helped. On a few systems it worked much better to do all the commands with a terminal emulator on the device rather than an ADB shell session.
Perhaps see if any of those tips helps with a successful s-off.
Regarding your SU app issues, try to clear data from whatever SU app you are using and then reboot and then open the app and make sure it doesn't need the SU binaries updated.
Sometimes it can take 15-20 attempts to get revone to work. How much did you try?

crushalot said:
After you ran revone -P, did you reboot with a manual hold of the power button or with adb command? Should use the power button.
I have found that the revone process works better when you don't change to su before ANY of the commands.
Also I have found that a lot of revone issues were adb related and changing to a different USB port or PC helped. On a few systems it worked much better to do all the commands with a terminal emulator on the device rather than an ADB shell session.
Perhaps see if any of those tips helps with a successful s-off.
Regarding your SU app issues, try to clear data from whatever SU app you are using and then reboot and then open the app and make sure it doesn't need the SU binaries updated.
Sometimes it can take 15-20 attempts to get revone to work. How much did you try?
Click to expand...
Click to collapse
Yes, I did a manual reboot.
Revone is said to work without SU and therefore uses it's integrated rooting process. I'm not rooted otherwise, I'd rather have my recovery working and flash a custom ROM then
I tried to run revone like 10 times (on my old device it took me exactly one try), I will consider your tipps and try again.

[Q] RUU stuck at "checking headers"

I have an HTC One M7 (European unlocked version). I'm trying to restore it to the stock software, but I don't care about the "locked/re-locked" status, so I didn't bother getting s-off. Right now I have the stock odexed ROM that I got from here and TWRP 2.6.3.3.
This is the RUU file I'm trying to use. (The "stock ROM" I have now is version 4.19.401.8 instead, and has support for OTA updates, but it says my phone is up to date even if it's not.)
I know that to get a RUU working on an HTC phone, you have to re-lock the bootloader. So I did. This is my fastboot info now:
Code:
C:\Windows\system32>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSORED
(bootloader) imei: CENSORED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the top the screen says "tampered" and "relocked."
So, still being on fastboot and aware that all the data in the phone would be gone, I ran the RUU file on my windows pc. It started up and I went through the setup. It rebooted my phone to a black screen with a gray htc logo and started the process.
However, I've noticed it's been at 5% and saying "checking headers" for a bit too long now. I waited an hour and it was still stuck. I held down the power button on my phone until it rebooted. It still booted up and worked fine, nothing was deleted. Tried again, same thing. I'm sure I'm using the right RUU file, and the MD5 checks fine. I remember doing this on an htc one v, I was in the same exact situation and everything went through. Why doesn't it work with my m7?
Now my bootloader is locked and if I re-unlock it, it will delete all my stuff. I can still use the phone fine, but I want stock rom, recovery and everything, so I can also get the official sense 6 update. I could do s-off if I really have to, if that's what it takes to get the RUU working. My phone's still rooted, but I don't think the firewater or whatever utility to get s-off works with a locked bootloader. What I'd like to do is just get the RUU working, but it's not. Have I screwed up? Do I re-unlock the bootloader and have to resort to custom roms on this phone? Please help. If I didn't provide enough info, tell me.

XDA Dev said:
I have an HTC One M7 (European unlocked version). I'm trying to restore it to the stock software, but I don't care about the "locked/re-locked" status, so I didn't bother getting s-off. Right now I have the stock odexed ROM that I got from here and TWRP 2.6.3.3.
This is the RUU file I'm trying to use. (The "stock ROM" I have now is version 4.19.401.8 instead, and has support for OTA updates, but it says my phone is up to date even if it's not.)
I know that to get a RUU working on an HTC phone, you have to re-lock the bootloader. So I did. This is my fastboot info now:
Code:
C:\Windows\system32>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSORED
(bootloader) imei: CENSORED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the top the screen says "tampered" and "relocked."
So, still being on fastboot and aware that all the data in the phone would be gone, I ran the RUU file on my windows pc. It started up and I went through the setup. It rebooted my phone to a black screen with a gray htc logo and started the process.
However, I've noticed it's been at 5% and saying "checking headers" for a bit too long now. I waited an hour and it was still stuck. I held down the power button on my phone until it rebooted. It still booted up and worked fine, nothing was deleted. Tried again, same thing. I'm sure I'm using the right RUU file, and the MD5 checks fine. I remember doing this on an htc one v, I was in the same exact situation and everything went through. Why doesn't it work with my m7?
Now my bootloader is locked and if I re-unlock it, it will delete all my stuff. I can still use the phone fine, but I want stock rom, recovery and everything, so I can also get the official sense 6 update. I could do s-off if I really have to, if that's what it takes to get the RUU working. My phone's still rooted, but I don't think the firewater or whatever utility to get s-off works with a locked bootloader. What I'd like to do is just get the RUU working, but it's not. Have I screwed up? Do I re-unlock the bootloader and have to resort to custom roms on this phone? Please help. If I didn't provide enough info, tell me.
Click to expand...
Click to collapse
Great information! Your post is a model of HOW a question should be posted!
Anyway, if 4.x.401.x RUU is NOT working, try another computer, if it is still not working, then yes, S-OFF, flash 1.44 HBOOT, and run the http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ RUU. This will take you back a few months ago, but you will be able to OTA all the way upto Sense 6!

SaHiLzZ said:
Great information! Your post is a model of HOW a question should be posted!
Anyway, if 4.x.401.x RUU is NOT working, try another computer, if it is still not working, then yes, S-OFF, flash 1.44 HBOOT, and run the http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ RUU. This will take you back a few months ago, but you will be able to OTA all the way upto Sense 6!
Click to expand...
Click to collapse
Haha, thanks, I guess nearly 3 years of lurking on these forums taught me something about posting.
I was using a Windows Vista SP2 PC to try this. I've just tried it on my Mac running Windows 7 SP1 with bootcamp, the RUU file (which still checks out with the correct MD5 hash) starts the installshield wizard normally, but as soon as I accept the terms and conditions, the program closes and nothing opens again. I checked on task manager, the process closes shortly after accepting the terms. I tried restarting and looking up for a solution but I couldn't find anything that worked.
Is Vista really the only reason it's stuck at checking headers? I know Vista is rather despised by a lot of people, but by 2014 it did get better. I'd rather use that machine because on my Mac running Windows 7 the RUU could not start up because I've made the Windows partition too small. (It has around 3gb free now whereas the vista machine has more than 150).

Sorry for the double post, but it's probably my last one on this thread.
Even if my boot loader was re-locked, I tried running the firewater program to get s-off, and it worked. (As a bonus it re-unlocked my boot loader without wiping the phone, but I re-locked it again to get the ruu working).
Then I tried downgrading to hboot 1.44, but for some reason it kept giving an error like "failed: remote 42 custom id check fail." I decided to try the sense 5.0 ruu anyway (on my vista PC), and it worked! The phone now says "relocked" but tampered is gone of course, and I have hboot 1.44, android 4.1 and htc sense 5.0, but still s-off.
The first update popped up (and it's not android 4.4 with sense 6, it's something in between) so I'm going to update until no more updates are available. Then I'm going to re-unlock the boot loader because I want to root my phone, and then set up all my stuff. When a new update comes out, I can just flash the original recovery, apply the update and then re-flash twrp to root again.
Thank you for the suggestion to install the older ruu. I'm still stumped on why the newer one didn't work (it would have caused much less hassle), but whatever. At least my phone is much cleaner now. It feels good to have it like this again, I'm not against custom roms but I like the stock software too.
I'm using my iPhone to write this, but trust me, my htc is in full working order now.
Until next problem I can't solve myself
Sent from my iPhone using Tapatalk

Thanks for updating back. Don't S-ON.

SaHiLzZ said:
Thanks for updating back. Don't S-ON.
Click to expand...
Click to collapse
Yeah, I'm not going to. I've updated to android 4.3 now and I'm still downloading updates--it updated hboot to 1.55 but I still have s-off, so I believe it stays s-off if I don't run the command to (I guess irreversibly) go back to s-on, which I don't even know. (I didn't do s-off before because I didn't care about the extra privileges and was afraid of bricking my phone, but now that I have it I don't mind so I'm keeping it).
Sent from my iPhone using Tapatalk

[Q] Need information about current state of this phone I bought.

Hi,
I purchased an HTC One M7 over the internet. It arrived with CyanogenMod on it, but to use my SIM with it, I had to flash AT&T's stock ROM onto the phone. I know little about actually dealing with Phone ROMs & other software things, so I'm unsure what I currently have on this phone.
If I do a factory reset, SuperSU Installer is always an app pre-installed. If I update it and try to root the device, after it reboots, a red triangle with exclamation point comes up with a phone under it. Then after some time, or if I manually do it, it reboots and enters a reboot loop until I go to the boot loader and Factory Reset it again. I read somewhere that this comes up to show that the Recovery is write-protected or something similar.
When booting to the bootloader, this is the information that appears:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
<date>
HBOOT
<commands>
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
SHOW BARCODE
I don't have a warranty to begin with, so I don't particularly care if the TAMPERED message comes up.
If I try and flash CyanogenMod onto the phone using CM's desktop & phone program/app, when the phone reboots, it goes to the bootloader which causes the program on my desktop computer to lose track of the phone.
So, now to my question: What state is this phone in? i.e. Is it rooted? If it is, what is installed on it aside from HBOOT & AT&T's stock ROM, if anything? If it's not, is it because I used AT&T's stock ROM?
My ultimate goal is to get CyanogenMod back on this phone correctly, but everything I've tried with that has hit some roadblock (their desktop program/phone app combo failing, installing TWRP failing, etc.) Any help is appreciated.
Thanks,
Tremor.

Your phone is still S-ON. To be free to do what you want you need to get to S-OFF, methinks.

cichlidiot said:
Your phone is still S-ON. To be free to do what you want you need to get to S-OFF, methinks.
Click to expand...
Click to collapse
Thanks.
That's one thing I was curious about though. If I require S-OFF to install CM, then did my installing of AT&T's ROM cause it to switch to S-ON since it had CM on it before? Just curious.

TremorPV said:
Hi,
I purchased an HTC One M7 over the internet. It arrived with CyanogenMod on it, but to use my SIM with it, I had to flash AT&T's stock ROM onto the phone. I know little about actually dealing with Phone ROMs & other software things, so I'm unsure what I currently have on this phone.
If I do a factory reset, SuperSU Installer is always an app pre-installed. If I update it and try to root the device, after it reboots, a red triangle with exclamation point comes up with a phone under it. Then after some time, or if I manually do it, it reboots and enters a reboot loop until I go to the boot loader and Factory Reset it again. I read somewhere that this comes up to show that the Recovery is write-protected or something similar.
When booting to the bootloader, this is the information that appears:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
<date>
HBOOT
<commands>
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
SHOW BARCODE
I don't have a warranty to begin with, so I don't particularly care if the TAMPERED message comes up.
If I try and flash CyanogenMod onto the phone using CM's desktop & phone program/app, when the phone reboots, it goes to the bootloader which causes the program on my desktop computer to lose track of the phone.
So, now to my question: What state is this phone in? i.e. Is it rooted? If it is, what is installed on it aside from HBOOT & AT&T's stock ROM, if anything? If it's not, is it because I used AT&T's stock ROM?
My ultimate goal is to get CyanogenMod back on this phone correctly, but everything I've tried with that has hit some roadblock (their desktop program/phone app combo failing, installing TWRP failing, etc.) Any help is appreciated.
Thanks,
Tremor.
Click to expand...
Click to collapse
Ok can you boot the phone to the bootloader connect fastboot usb, then in the fastboot command line type
Code:
fastboot getvar all
This will give an output of all the version information for the device. Post it here after removing your IMEI and Serial numbers. You don't want to advertise those
And no you don't need s-off to flash roms, and flashing stock at&t did not and cannot set s-on again.
Let's start with the getvar and take it from there :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

If it goes to boot loader then it sounds like your missing a good recovery image. Flash the recovery and then flash a rom.
Stay away from PC installers and ROM manager.

Danny201281 said:
Ok can you boot the phone to the bootloader connect fastboot usb, then in the fastboot command line type
Code:
fastboot getvar all
This will give an output of all the version information for the device. Post it here after removing your IMEI and Serial numbers. You don't want to advertise those
And no you don't need s-off to flash roms, and flashing stock at&t did not and cannot set s-on again.
Let's start with the getvar and take it from there :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Yes, I entered the bootloader, then I switched to Fastboot which gave me a screen like this:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
<date>
FASTBOOT
<commands>
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I move the selection down to REBOOT or any other command, FASTBOOT changes to FASTBOOT USB and stays that way.
However, my PC says the USB device malfunctioned, and running the "fastboot getvar all" command does this:
Code:
< waiting for device >
When the HTC One is on and plugged in, it shows up just fine as "My HTC One" under Android USB Devices in Device Manager, so the drivers work.
zelendel said:
If it goes to boot loader then it sounds like your missing a good recovery image. Flash the recovery and then flash a rom.
Stay away from PC installers and ROM manager.
Click to expand...
Click to collapse
It only goes to bootloader when I hold down the Volume Down button.
Not sure how to do that. Still learning.

TremorPV said:
Yes, I entered the bootloader, then I switched to Fastboot which gave me a screen like this:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
FASTBOOT
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I move the selection down to REBOOT or any other command, FASTBOOT changes to FASTBOOT USB and stays that way.
However, my PC says the USB device malfunctioned, and running the "fastboot getvar all" command does this:
Code:
< waiting for device >
When the HTC One is on and plugged in, it shows up just fine as "My HTC One" under Android USB Devices in Device Manager, so the drivers work.
It only goes to bootloader when I hold down the Volume Down button.
Not sure how to do that. Still learning.
Click to expand...
Click to collapse
Sounds like a driver problem on the pc side. Check your drivers are installed correctly. Your phone should appear in device manager as "My HTC" Edit :- I see the drivers are working when the phone is on and then fail see this FAQ post Q (2) to fix your drivers after the malfunction message http://forum.xda-developers.com/showthread.php?p=52135024
What operating system do you have on your pc Windows 7, 8 or 8.1. / Mac OSX?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Sounds like a driver problem on the pc side. Check your drivers are installed correctly. Your phone should appear in device manager as "My HTC" Edit :- I see the drivers are working when the phone is on and then fail see this FAQ post Q (2) to fix your drivers after the malfunction message http://forum.xda-developers.com/showthread.php?p=52135024
What operating system do you have on your pc Windows 7, 8 or 8.1. / Mac OSX?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Will do. (at work atm)
Windows 8.1 64 bit, using WIndows 7 64 bit drivers.

TremorPV said:
Will do. (at work atm)
Windows 8.1 64 bit, using WIndows 7 64 bit drivers.
Click to expand...
Click to collapse
That's what I was afraid of, I can't speak from personal experience as I use Windows very little and if I do it's Windows 7. But to the best of my knowledge Windows 8 and 8.1 are a bit finicky when it comes to adb/fastboot especially if your on hboot 1.44.
There's a thread here you may find helpful there are a few solutions discussed here http://forum.xda-developers.com/showthread.php?t=2347317
Personally I prefer Linux. When all else fails Linux doesn't see my guide here it contains everything you need to know to use Linux without installing it on your pc. Just boot from a usb stick, no drivers require. Just Linux and adb/fastboot http://forum.xda-developers.com/showthread.php?p=54272479
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
That's what I was afraid of, I can't speak from personal experience as I use Windows very little and if I do it's Windows 7. But to the best of my knowledge Windows 8 and 8.1 are a bit finicky when it comes to adb/fastboot especially if your on hboot 1.44.
There's a thread here you may find helpful there are a few solutions discussed here http://forum.xda-developers.com/showthread.php?t=2347317
Personally I prefer Linux. When all else fails Linux doesn't see my guide here it contains everything you need to know to use Linux without installing it on your pc. Just boot from a usb stick, no drivers require. Just Linux and adb/fastboot http://forum.xda-developers.com/showthread.php?p=54272479
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Figured. I had heard they worked with 8, but I guess not.
Awesome.
Me too. If only all of my games worked on Linux. Will try this and get back to you.

TremorPV said:
Figured. I had heard they worked with 8, but I guess not.
Awesome.
Me too. If only all of my games worked on Linux. Will try this and get back to you.
Click to expand...
Click to collapse
I hear you about the gaming on Linux. They seem to be making progress though. At least we have Steam now :good:
But yeah my pc dual boots with Windows 7 for gaming.

Danny201281 said:
I hear you about the gaming on Linux. They seem to be making progress though. At least we have Steam now :good:
But yeah my pc dual boots with Windows 7 for gaming.
Click to expand...
Click to collapse
So it worked. Boo ya. Well... kinda. Here is my output:
Code:
(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: >number<
(bootloader) imei: >number<
(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: 3892mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.043s
Useful.
I tried it again to see if I could get it past that FAILED message and this is what I get:
Code:
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 1.002s
wat

TremorPV said:
So it worked. Boo ya. Well... kinda. Here is my output:
Code:
(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: >number<
(bootloader) imei: >number<
(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: 3892mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.043s
Useful.
I tried it again to see if I could get it past that FAILED message and this is what I get:
Code:
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 1.002s
wat
Click to expand...
Click to collapse
The failed message is normal with Hboot 1.44 you will always get that until you update hboot.

Danny201281 said:
The failed message is normal with Hboot 1.44 you will always get that until you update hboot.
Click to expand...
Click to collapse
Ah. Good to know.
So in my journey to learn, I decided I wanted to try updatig HBOOT. Which, from what I've read, requires S-OFF, so I went to Firewater. Unfortunately, I didn't realize I needed S-OFF & Firewater, and did the following with S-ON:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip hboot_firewater>version<.zip
Which failed. My phone still works and can get to the fastboot/HBOOT screen, so from what I can tell, no harm was done.
Running firewater based on the instructions on their webpage doesn't really do anything. It pushes the firewater file to the /tmp on the device, but won't run it. Not sure why. Specifically, this happens:
Code:
adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
That goes fine. This is where the strange things start:
Code:
[email protected]:/ $ su
1|[email protected]:/ $ chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/firewater
error, run firewater as root. su or FU!!!!!!
1|[email protected]:/ $ su /data/local/tmp/firewater
That's exactly as it appears in the Terminal. While it's doing this, I get lots of pop ups on Linux about how it's unable to mount the Android Phone. I check my phone after doing the above commands, and it's on the stock AT&T ROM I installed.
There's nothing mentioned about Firewater and nothing has happened AFAIK. Firewater's page says there should be a prompt or something, but there's not.

TremorPV said:
So it worked. Boo ya. Well... kinda. Here is my output:
Code:
(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: >number<
(bootloader) imei: >number<
(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: 3892mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.043s
Useful.
I tried it again to see if I could get it past that FAILED message and this is what I get:
Code:
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 1.002s
wat
Click to expand...
Click to collapse
Ok so let's get you phone booting again.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Download this and place it in your fastboot folder. Rename it recovery.img
Flash your recovery with fastboot
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Now select recovery from the bootloader menu. Now we can push the Rom.
Download this stock Rom drop it in your fastboot folder and rename it rom.zip
http://www.htc1guru.com/did/guru_reset_m7_1-26-502-12-zip/
And push to the phone with
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes several minutes when it's done install the Rom with twrp recovery.
---------- Post added at 07:37 PM ---------- Previous post was at 07:27 PM ----------
Oh so you have a Rom booting? Ok I'm a little busy for the next hour. If you want to go s-off don't update anything just yet.
Getting s-off will be harder after you update
Use this toolkit to get s-off with revone as your on hboot 1.44 http://forum.xda-developers.com/showthread.php?t=2364445

Danny201281 said:
Ok so let's get you phone booting again.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Download this and place it in your fastboot folder. Rename it recovery.img
Flash your recovery with fastboot
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Now select recovery from the bootloader menu. Now we can push the Rom.
Download this stock Rom drop it in your fastboot folder and rename it rom.zip
http://www.htc1guru.com/did/guru_reset_m7_1-26-502-12-zip/
And push to the phone with
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes several minutes when it's done install the Rom with twrp recovery.
---------- Post added at 07:37 PM ---------- Previous post was at 07:27 PM ----------
Oh so you have a Rom booting? Ok I'm a little busy for the next hour. If you want to go s-off don't update anything just yet.
Getting s-off will be harder after you update
Use this toolkit to get s-off with revone as your on hboot 1.44 http://forum.xda-developers.com/showthread.php?t=2364445
Click to expand...
Click to collapse
ARGH. Didn't read the whole post before doing anything. Finished flashing the recovery.img to the recovery before I finished your post. I needed a different recovery anyway as I don't like the current one, so yay at least. I didn't boot into recovery though, so hopefully I'm fine.
It's fine. Take your time. I've got all day.
Yes, I would like S-OFF just so I can update HBOOT so that if I want to tinker with my phone in the future it will be easier to do. I may not like CyanogenMod, so trying out Kit Kat and other things will be easier (I imagine) without whatever is making it hard to deal with this phone.

Danny201281 said:
I hear you about the gaming on Linux. They seem to be making progress though. At least we have Steam now :good:
But yeah my pc dual boots with Windows 7 for gaming.
Click to expand...
Click to collapse
Same here. Give me my games and a few apps and good bye Windows lol

TremorPV said:
ARGH. Didn't read the whole post before doing anything. Finished flashing the recovery.img to the recovery before I finished your post. I needed a different recovery anyway as I don't like the current one, so yay at least. I didn't boot into recovery though, so hopefully I'm fine.
It's fine. Take your time. I've got all day.
Yes, I would like S-OFF just so I can update HBOOT so that if I want to tinker with my phone in the future it will be easier to do. I may not like CyanogenMod, so trying out Kit Kat and other things will be easier (I imagine) without whatever is making it hard to deal with this phone.
Click to expand...
Click to collapse
Ok so cool, flashing recovery won't cause any issues with s-off later on, so you can flash what ever recovery you preffer.
Hboot can be updated without s-off but once you do it gets much harder to s-off as HTC have implemented patches into the newer firmware to try and prevent it. unless you wanna pay $25 for Sunshine app which should work regardless.
Getting s-off with revone is by far the easiest way to do it for free if your on hboot 1.44 Personally I've never used revone all devices I s-offed were already on higher hboot versions so had to use other methods. So you should read through the link I posted to get that done but it sounds fairly simple using that toolkit. Once your s-off the sky's the limit pretty much.

Danny201281 said:
Ok so cool, flashing recovery won't cause any issues with s-off later on, so you can flash what ever recovery you preffer.
Hboot can be updated without s-off but once you do it gets much harder to s-off as HTC have implemented patches into the newer firmware to try and prevent it. unless you wanna pay $25 for Sunshine app which should work regardless.
Getting s-off with revone is by far the easiest way to do it for free if your on hboot 1.44 Personally I've never used revone all devices I s-offed were already on higher hboot versions so had to use other methods. So you should read through the link I posted to get that done but it sounds fairly simple using that toolkit. Once your s-off the sky's the limit pretty much.
Click to expand...
Click to collapse
Sweet.
Figured. Sounds just like when I jailbroke my old PSP-2000.
I tried that tool, but this is what happened:
Code:
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb reboot
error: more than one device and emulator
Revone & Firewater both say this. This tool does not have a Linux version unfortunately.

TremorPV said:
Sweet.
Figured. Sounds just like when I jailbroke my old PSP-2000.
I tried that tool, but this is what happened:
Code:
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb reboot
error: more than one device and emulator
Revone & Firewater both say this. This tool does not have a Linux version unfortunately.
Click to expand...
Click to collapse
What output do you get from adb devices?

[Q] relock/unroot HTC One M7, hboot 1.57

Hi guys, hope you can help me out...
I just rooted my HTC One (unlock bootloader and install TWRP recovery), WITHOUT installing any custom ROM (i just kept the factory OS, because i couldn't S-Off the phone in order to install the google play edition). The OS i had (and still have) is stock Android 4.4.3 with Sense 6.
The problem is that i need to lock the phone back (in order to benefit from the warranty - technical touchscreen problem).
I tried using Revone to lock the phone back, but i get an error: "Failed to open framebuffer device". I understand that revone doesn't work with hboot 1.57.
Could you please help me with the relocking/unrooting the phone (at least give me a link to a guide that is working for my phone configuration - hboot 1.57) ? And also could you tell me if i need a RUU, or i can just wipe/reinstall the current OS (which i never changed in the first place) ? And if i need a RUU, how can i find the one that was initially installed on the phone ?
Oh, and one more thing: at first, when my phone started, i had a Vodafone screen showing up, and some crappy apps preinstalled. After i rooted an installed twrp recovery, i don't get that vodafone screen anymore, an the crappy apps weren't preinstalled anymore.
Cheers and thanks in advance !

andreih8017 said:
Hi guys, hope you can help me out...
I just rooted my HTC One (unlock bootloader and install TWRP recovery), WITHOUT installing any custom ROM (i just kept the factory OS, because i couldn't S-Off the phone in order to install the google play edition). The OS i had (and still have) is stock Android 4.4.3 with Sense 6.
The problem is that i need to lock the phone back (in order to benefit from the warranty - technical touchscreen problem).
I tried using Revone to lock the phone back, but i get an error: "Failed to open framebuffer device". I understand that revone doesn't work with hboot 1.57.
Could you please help me with the relocking/unrooting the phone (at least give me a link to a guide that is working for my phone configuration - hboot 1.57) ? And also could you tell me if i need a RUU, or i can just wipe/reinstall the current OS (which i never changed in the first place) ? And if i need a RUU, how can i find the one that was initially installed on the phone ?
Oh, and one more thing: at first, when my phone started, i had a Vodafone screen showing up, and some crappy apps preinstalled. After i rooted an installed twrp recovery, i don't get that vodafone screen anymore, an the crappy apps weren't preinstalled anymore.
Cheers and thanks in advance !
Click to expand...
Click to collapse
Ok well first off you need s-off to set your bootloader to ***LOCKED*** and to get back to 100% stock. As your on Hboot 1.57 the only way to gain s-off is with Sunshine App. Which will cost $25 to use.
The stock Rom on your Device won't be a complete stock Rom either. When you unlock the bootloader the device is wiped along with some preload data (crappy apps) which is critical if you want the device back to stock. Or to be able to accept OTA updates. If the device is Vodafone I'm not sure there is an RUU but you should be able to get a full stock Rom from somewhere. Please post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting. And we can see what is available for you. But if you want to go 100% stock to reinstate your warranty you will need s-off first :good:

Danny201281 said:
Ok well first off you need s-off to set your bootloader to ***LOCKED*** and to get back to 100% stock. As your on Hboot 1.57 the only way to gain s-off is with Sunshine App. Which will cost $25 to use.
The stock Rom on your Device won't be a complete stock Rom either. When you unlock the bootloader the device is wiped along with some preload data (crappy apps) which is critical if you want the device back to stock. Or to be able to accept OTA updates. If the device is Vodafone I'm not sure there is an RUU but you should be able to get a full stock Rom from somewhere. Please post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting. And we can see what is available for you. But if you want to go 100% stock to reinstate your warranty you will need s-off first :good:
Click to expand...
Click to collapse
Hey, thanx for the quick answer !
This is the result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
What do you mean by "Or to be able to accept OTA updates" ?? At his moment i won't be able to receive any updates anymore ? :crying:
Also, what about Firewater for S-OFF ?

andreih8017 said:
Hey, thanx for the quick answer !
This is the result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
What do you mean by "Or to be able to accept OTA updates" ?? At his moment i won't be able to receive any updates anymore ? :crying:
Click to expand...
Click to collapse
Unlocking the bootloader wipes /data partition to prevent unauthorized access to your data. Problem is that HTC packed some of their stock apps in /data/preload which mean you don't have these apps anymore after unlocking the bootloader. When installing an ota update, there is a script verifying the integrity of each files to be patched, inluding apps normally present in /data/preload. After the script will find out that these apps are missing, the ota update installation will abort. So no your phone can't install ota update anymore unless you restore your phone back to stock (which can be done with s-off btw).
Also, what about Firewater for S-OFF ?
Click to expand...
Click to collapse
Its discontinued. Firewater was using online resources no more available to do its magic.
From what I see from your "getvar all" you have the pretty standard version of the M7. Follow nkk71's guide linked in my signature. You want to follow the procedure using the 1.28.401.7 ruu.zip

@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,

andreih8017 said:
@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,
Click to expand...
Click to collapse
To safely go back to s-on without risking tampered you should have done it before installing the OTA updates as explained in @nkk71 guide.
So now you should downgrade with the ruu again then set s-on then install OTA updates to avoid the tampered flag returning. :good:

andreih8017 said:
@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,
Click to expand...
Click to collapse
how far did you go with the OTA's? as long as it's pre 7.xx (ie Lollipop), sunshine will still work, in case you the tampered sign back, you can use sunshine again to s-off, and redo it (the guide)
but as danny said, i (personally) only recommend it on 1.xx or 2.xx firmware.... i don't know the reason for tampered [sometimes/often] reappearing so i dont know what's involved or what triggers it

@Danny201281
@nkk71
i took a leap of faith and eneter the "fastboot oem writesecureflag 3" command. It worked like a charm. Afterwards i rebooted the bootloader 3 times and no "tampered" sign, but S-ON. I also rebooted the phone once and still no "tampered" sign, but S-ON. Guess it worked, right ?
As for the OTAs, i went until the last one available for HTC One - 6.09.401.11.
Thanks guys !

andreih8017 said:
@Danny201281
@nkk71
i took a leap of faith and eneter the "fastboot oem writesecureflag 3" command. It worked like a charm. Afterwards i rebooted the bootloader 3 times and no "tampered" sign, but S-ON. I also rebooted the phone once and still no "tampered" sign, but S-ON. Guess it worked, right ?
As for the OTAs, i went until the last one available for HTC One - 6.09.401.11.
Thanks guys !
Click to expand...
Click to collapse
You need to reboot the ROM three times at least, not the bootloader
Sent from my HTC One_M8 using Tapatalk

@nkk71
I did that also. Still working fine, "locked" and S-ON
Thanx,

andreih8017 said:
@nkk71
I did that also. Still working fine, "locked" and S-ON
Thanx,
Click to expand...
Click to collapse
cool, good to hear :good: :good:

[Fixed] Bricked Hboot 1.44 with RUU 1.31 (Explanation on how solved in OP)

[Fixed][Solution]
This should work for anyone who soft bricked there device but still has the 1.44 HBoot to allow them to still flash a recovery. I did not come up with any of this but was helped by nkk71 who showed me the way. I dealt with this problem for over 2 days now non-stop trying to fix it only missing 1 step that made all the difference.
This method is for a HTC One (M7) Sprint Variant:
-Be sure to use HTCDev to unlock your phone and flash a custom recovery. (I used TWRP)
-Be sure to have all the adb and fastboot exe files needed. If you bricked your phone you most likely already do but if not there are tons of links on the forums to help you get all the information you need from them.
-Check to make sure what RUU your phone is at by going into fastboot and using a cmd window type: fasboot getvar all. This will display your phones information. If you happen to be at 1.31 like my phone was you will need to do the next step, if not then find your recovery.
- Fix your version main to say 1.29.651.10 by editing the misc partition
Boot into recovery
In the recovery mount your device. I mounted all parts in TWRP.
Open a cmd window and doucle check that your device is connected by typing: adb devices
(If it shows a set up numbers and letters and then says recovery then that is your device.)
Now type: adb shell
type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
type: adb reboot bootloader
Once it loads back into the bootloader click on fastboot and check to see if your device is connected by typing: fastboot devices
If you see you device type: fastboot oem lock (This will relock your device)
- Now you are ready to run the RUU. (After it runs your phone is back to stock)
If any of this is confusing, there are links below that were used to get me through this. If you need to do this I wish you luck.
Original Post:
So basically I erased everything. Not sure how but phone Bricked. Luckily i have a 1.44Hboot and I simply just burned the recovery back.
Unforunately I've stopped messing with phones for about 2 years so it took me forever to get everything set back up properly. Now my biggest issue is I can't manage to get a ROM to boot anymore. The closest one is ViperOne 8, I've tried Android Revolution HD91.1 (which started all my troubles), NUSenSeven which is having issues for more people as well, and tried a very basic Stock M7 one.
Any information you give please act like I'm stupid. I can do adb and fastboot, but if you just say flash it, please dont expect me to know how. I've forgotten tons.
Anyways, currently my phone shows the:
*Tampered*
*Unlocked*
S-On
I have been trying to get it to S-off and then remove the Tampered but I can't get s-off with Revone.
Gives me Error = 1 and I'm just totally lost. But not I can't even seem to get a ROM to load and when it does I have no Service on this phone anymore and I have to remove the HTCsetupwizard.apk. Unfortunately sometimes this does not show up in system/app and under system might not show anything at all.
If that is standard to happen right after a fresh install without loading then that kind of makes sense. Also, I only wait about 10minutes on booting for the roms. Only Rom I wait longer on is the ViperOne 8 as it shows upgrading.
Please advise, I'm will to try anything. I'm having a huge headache with this and throwing the phone into a wall is becoming a reality.

toxicfumes22 said:
So basically I erased everything. Not sure how but phone Bricked. Luckily i have a 1.44Hboot and I simply just burned the recovery back.
Unforunately I've stopped messing with phones for about 2 years so it took me forever to get everything set back up properly. Now my biggest issue is I can't manage to get a ROM to boot anymore. The closest one is ViperOne 8, I've tried Android Revolution HD91.1 (which started all my troubles), NUSenSeven which is having issues for more people as well, and tried a very basic Stock M7 one.
Any information you give please act like I'm stupid. I can do adb and fastboot, but if you just say flash it, please dont expect me to know how. I've forgotten tons.
Anyways, currently my phone shows the:
*Tampered*
*Unlocked*
S-On
I have been trying to get it to S-off and then remove the Tampered but I can't get s-off with Revone.
Gives me Error = 1 and I'm just totally lost. But not I can't even seem to get a ROM to load and when it does I have no Service on this phone anymore and I have to remove the HTCsetupwizard.apk. Unfortunately sometimes this does not show up in system/app and under system might not show anything at all.
If that is standard to happen right after a fresh install without loading then that kind of makes sense. Also, I only wait about 10minutes on booting for the roms. Only Rom I wait longer on is the ViperOne 8 as it shows upgrading.
Please advise, I'm will to try anything. I'm having a huge headache with this and throwing the phone into a wall is becoming a reality.
Click to expand...
Click to collapse
1- please post a "fastboot getvar all" (excluding IMEI, MEID and s/n)
2- looks like you're on Sprint, which is different that the GSM version of the M7, and has a different partition table
3- you may need to use an RUU to get your partitions back to normal
4- revone wont work on such new ROMs, even if hboot is 1.44 the ROM still plays a factor
let's start with the "fastboot getvar all" output

nkk71 said:
1- please post a "fastboot getvar all" (excluding IMEI, MEID and s/n)
2- looks like you're on Sprint, which is different that the GSM version of the M7, and has a different partition table
3- you may need to use an RUU to get your partitions back to normal
4- revone wont work on such new ROMs, even if hboot is 1.44 the ROM still plays a factor
let's start with the "fastboot getvar all" output
Click to expand...
Click to collapse
1) C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(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: 4117mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.059s
2) Yes on Sprint, but with no activation on this phone now.
3) RUU would be 1.31, I relocked phone and went to use the RUU but don't know how to flash it.
4) I figured that with Revone thats why I attempted the RUU but got stuck there. I'll have to refind the RUU again though as I downloaded about 40GB yesterday and my SSD doesn't have that much room anymore. Waiting for windows 10 which is far away.
BTW, Thank you for the response.

toxicfumes22 said:
BTW, Thank you for the response.
Click to expand...
Click to collapse
Sure, no problem.
toxicfumes22 said:
1) C:\adb\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
2) Yes on Sprint, but with no activation on this phone now.
Click to expand...
Click to collapse
okay, so it's a Sprint M7 with a messed up partition table, so yes, best course of action is probably RUUing
toxicfumes22 said:
3) RUU would be 1.31, I relocked phone and went to use the RUU but don't know how to flash it.
Click to expand...
Click to collapse
There is no 1.31.651.2 RUU (signed and encrypted) as far as I looked (which isnt very far, but I think it would have show up)
toxicfumes22 said:
4) I figured that with Revone thats why I attempted the RUU but got stuck there. I'll have to refind the RUU again though as I downloaded about 40GB yesterday and my SSD doesn't have that much room anymore. Waiting for windows 10 which is far away.
Click to expand...
Click to collapse
revone will need hboot 1.44 (dated pre June 2013) and a compatible ROM to work.
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
then run full 1.29.651.10 RUU.EXE
then you can use revone
or
B) flash newer version RUU.EXE
use sunshine (paid app $25) to get S-OFF
note: you will likely need to update firmware first for the ruu to work properly
hope that points you in the right direction

nkk71 said:
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
Click to expand...
Click to collapse
Nice trick, still learning a lot from you

alray said:
Nice trick, still learning a lot from you
Click to expand...
Click to collapse
it's an "old trick", i take no credit at all for it ... as long as hboot version is the same, fixing the version-main (using adb or even the "misctool" <- it's somewhere on xda, dont have a link handy atm) should work fine
extract:
Code:
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version... [I]<- this is where it would fail, without that fix[/I]
(bootloader) checking hboot version... [I]<- this is where it would fail if hboot is higher[/I]
(bootloader) start image[boot] unzipping & flushing...

nkk71 said:
Sure, no problem.
okay, so it's a Sprint M7 with a messed up partition table, so yes, best course of action is probably RUUing
There is no 1.31.651.2 RUU (signed and encrypted) as far as I looked (which isnt very far, but I think it would have show up)
revone will need hboot 1.44 (dated pre June 2013) and a compatible ROM to work.
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
then run full 1.29.651.10 RUU.EXE
then you can use revone
or
B) flash newer version RUU.EXE
use sunshine (paid app $25) to get S-OFF
note: you will likely need to update firmware first for the ruu to work properly
hope that points you in the right direction
Click to expand...
Click to collapse
I'd like to do option A but unfortunately I do not know how to use adb in recovery. I only know how to use it when android is running. The rest I should be able to do.

toxicfumes22 said:
I'd like to do option A but unfortunately I do not know how to use adb in recovery. I only know how to use it when android is running. The rest I should be able to do.
Click to expand...
Click to collapse
you use adb shell same in recovery (actually better) as you use it in a booted & rooted rom, unfortunately, i can't do that right now, so either @alray will have to help you
or it'll have to wait till tomorrow.

New Getvar all after I guessed that mounting the phone would allow an adb connection
C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(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: 4329mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
So do this mean that I am ready to run the .exe while in fastboot?
Of course after relocking the device. just want to confirm as I tried this earlier but missed the first step which was most likely crucial.

toxicfumes22 said:
New Getvar all after I guessed that mounting the phone would allow an adb connection
C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(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: 4329mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
So do this mean that I am ready to run the .exe while in fastboot?
Of course after relocking the device. just want to confirm as I tried this earlier but missed the first step which was most likely crucial.
Click to expand...
Click to collapse
yes should work fine now, give it a try.

alray said:
yes should work fine now, give it a try.
Click to expand...
Click to collapse
nkk71 said:
you use adb shell same in recovery (actually better) as you use it in a booted & rooted rom, unfortunately, i can't do that right now, so either @alray will have to help you
or it'll have to wait till tomorrow.
Click to expand...
Click to collapse
I have a phone again. Thank you so much.
Imagine someone frustrated for over 2days spending 10+ hours a day readying, flashing and trying everything to get their phone to work with limited knowledge.
Now imagine that same person jumping up and down with joy. (That's me now)
Thank you so much for your help. Your links did the trick, they were what I couldn't find.
Now that I know how to do this, I'm going to try RevOne, flash a new Firmware and then flash one of the new roms I wanted. If any of this fails then I'm done with this stuff for some time, haha.

toxicfumes22 said:
I have a phone again. Thank you so much.
Imagine someone frustrated for over 2days spending 10+ hours a day readying, flashing and trying everything to get their phone to work with limited knowledge.
Now imagine that same person jumping up and down with joy. (That's me now)
Thank you so much for your help. Your links did the trick, they were what I couldn't find.
Now that I know how to do this, I'm going to try RevOne, flash a new Firmware and then flash one of the new roms I wanted. If any of this fails then I'm done with this stuff for some time, haha.
Click to expand...
Click to collapse
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk

nkk71 said:
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
All thanks for you
My only contribution here was to say "give it a try" :laugh:

alray said:
All thanks for you
My only contribution here was to say "give it a try" [emoji23]
Click to expand...
Click to collapse
Sometimes, that is all what is needed
I think the OP agrees.
Sent from my SM-P905 using Tapatalk

nkk71 said:
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
I copied and pasted, its exactly what I used. If it's wrong let me know and I'll fix though.
Another update though is I am now Unlocked with S-Off w/o Tampered. Basically what I wanted.
Now should be my last questions, but it's a good idea to update to the newest firmware correct?
Firmware will never be able to stop me from achieve what I just did to fix the phone correct?

nkk71 said:
Sometimes, that is all what is needed
I think the OP agrees.
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
Yup, I was going to not do a thing until I had a response. I was just worried I'd somehow mess it up. Just one confirmation that it looked good was enough to give me confidence.