Database Develop

[Q] Problem with flash a working ROM

I did extensive search on multiple forums but did not get answer. Hope someone can help here.
The timeline and issue look like this:
* unlocked phone and installed TWRP 2.5 for m7wls. This part was good.
* HTC released 4.3 OTA. I was unable to take it because of TWRP.
* In the middle, probably a wrong zip (Android_Revolution_HD-One_4.0_GE.zip) was loaded by twrp. Now, twrp cannot mount USB at all.
* Tried CWM recovery, works but cannot mount USB either.
* Flashed back stock boot and stock recovery: http://forum.xda-developers.com/showthread.php?t=2236418
* Tried to do fastboot oem rebootRUU then fastboot flash zip. But none of the zip I found can pass. Failed with 24 parsing android-info fail
To summarize, no USB mount, no OTG yet (ordered a cable yesterday), fastboot seems working, twrp/cwm recovery looks good. Can anyone please help? Thank you!
Device: Sprint HTC One unlocked, S-ON, HBoot 1.44.0000
Desktop: Windows 8 64-bit
C:\temp> 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: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(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.043s

xmmmm said:
* In the middle, probably a wrong zip (Android_Revolution_HD-One_4.0_GE.zip)
Click to expand...
Click to collapse
This isn't for our phone. Where did you get this? I haven't seen this in our forum.
Sent from my HTCONE using Tapatalk 2

hcyplr29 said:
This isn't for our phone. Where did you get this? I haven't seen this in our forum.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
Most likely, it is for GSM version.

xmmmm said:
Most likely, it is for GSM version.
Click to expand...
Click to collapse
Try this. http://forum.xda-developers.com/showthread.php?p=45988642
Sent from my HTCONE using Tapatalk 2

I will give a try. But why this rom could prevent twrp/cwm from mounting USB?
Thank you.
hcyplr29 said:
Try this. http://forum.xda-developers.com/showthread.php?p=45988642
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse

xmmmm said:
I will give a try. But why this rom could prevent twrp/cwm from mounting USB?
Thank you.
Click to expand...
Click to collapse
you flashed a GSM rom on a CDMA phone and messed up your partitions, at this point you can only try to sideload a rom (for your phone m7wls) or RUU, to run ruu you will need to get s-off.

Aldo101t said:
you flashed a GSM rom on a CDMA phone and messed up your partitions, at this point you can only try to sideload a rom (for your phone m7wls) or RUU, to run ruu you will need to get s-off.
Click to expand...
Click to collapse
Thanks, I will try this as well. Moving to a Windows 7 PC to do all this. May I ask which ROM I should load? Thank you.

xmmmm said:
Thanks, I will try this as well. Moving to a Windows 7 PC to do all this. May I ask which ROM I should load? Thank you.
Click to expand...
Click to collapse
any rom in the sprint forum which ever one appeals to ya

The problem is resolved.
Some factors to consider if someone else run into the same issue. Most of these are mentioned in other threads as well.
1. Windows 7 x64 OK. (Previous was Windows 8 x64)
2. HTC Driver 3.0.0.007 (Previous was 4.1.0.001)
3. Installed UniversalAdbDriverSetup6.msi. Without this, adb always gave device not found error.
4. Rollback to 1.29.651.10 by doing below and then run RUU from Windows. Ignore the lseek64 error.
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
fastboot oem lock
The device is still S-ON and relocked with stock recovery after above steps. There is no more tampered alert in hboot.
By the way, when adb started working, I tried to use "adb push rom.zip /sdcard" and install the stock 1.31.651.2 zip from twrp. But it seems the system constantly freeze up with this approach. RUU is definitely the best and easiest way to do.
Many thanks to all who contributed the ideas.

xmmmm said:
The problem is resolved.
Some factors to consider if someone else run into the same issue. Most of these are mentioned in other threads as well.
1. Windows 7 x64 OK. (Previous was Windows 8 x64)
2. HTC Driver 3.0.0.007 (Previous was 4.1.0.001)
3. Installed UniversalAdbDriverSetup6.msi. Without this, adb always gave device not found error.
4. Rollback to 1.29.651.10 by doing below and then run RUU from Windows. Ignore the lseek64 error.
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
fastboot oem lock
The device is still S-ON and relocked with stock recovery after above steps. There is no more tampered alert in hboot.
Many thanks to all who contributed the ideas.
Click to expand...
Click to collapse
Best Driver is Universal Naked Driver
And if you dont need full blown SDK Minimal ADB and Fastboot

Konfuzion said:
Best Driver is Universal Naked Driver
And if you dont need full blown SDK Minimal ADB and Fastboot
Click to expand...
Click to collapse
Good to know. Thank you!

[Q] HTC ONE (m7) 64GB Developer Edition

Hello everybody, I´m a little newbie here so need some URGEN HELP.
1.- I bought an HTC ONE (m7) 64GB Developer Edition from SWAPPA with ClockworkMod Recovery and CyanogenMod 11 on it.
2.- While looking into XDA-Developer was following a thread to get it back to stock recovery using nandroid so I can flash an RUU from HTCDEV
While doing that seems that I erase everything from the phone and now it´s giving me an error mounting e:/ drive and It doesn´t recognize the phone in ADB mode.
I´m stuck with the CWM without the ability to get files into /sdcard/0/clockworkmode/backups
Can someone help me or point me in the right direction to get back to the stock android that the HTC Developer Edition (m7) comes in factory default.

ulises.boom said:
2.- While looking into XDA-Developer was following a thread to get it back to stock recovery using nandroid so I can flash an RUU from HTCDEV
Click to expand...
Click to collapse
you don't need stock recovery to use a ruu. Recovery is overwritten by the ruu.
ulises.boom said:
While doing that seems that I erase everything from the phone and now it´s giving me an error mounting e:/ drive and It doesn´t recognize the phone in ADB mode.
I´m stuck with the CWM without the ability to get files into /sdcard/0/clockworkmode/backups
Can someone help me or point me in the right direction to get back to the stock android that the HTC Developer Edition (m7) comes in factory default.
Click to expand...
Click to collapse
Just flash the latest dev edition ruu http://www.htc1guru.com/2014/03/android-dev-ruu/

@alray Thanks for the prompt response.
I will download and try that later today after work.
But some questions so I don´t do something stupid:
I have to restart the phone on Fastboot mode or Recovery Mode for the RUU to work, as the phone is starting with the Gray and red triangle and an admiration mark.?
Thanks

ulises.boom said:
@alray Thanks for the prompt response.
I will download and try that later today after work.
But some questions so I don´t do something stupid:
I have to restart the phone on Fastboot mode or Recovery Mode for the RUU to work, as the phone is starting with the Gray and red triangle and an admiration mark.?
Thanks
Click to expand...
Click to collapse
you can run the ruu.exe in bootloader mode if you want, it will then switch to ruu mode by itself. If the phone were booted in the OS the ruu.exe will make it reboot in ruu mode.

@arlay Sorry to tell you that it didn´t work.
Let me explain a little of what I have here:
It seems that I erase everythin in the Phone except by the Fastboot and Recovery.
I´m having the following errors:
E:Can´t mount /cache/recovery/
E: unknown volume "/sdcard/.android_secure
Running the RUU I got Error 155.
And another thing, it can find /system/xbin/su
Do I hava a recobrable one or a brick?
I have it on s-on and could not made it s-off with revone
alray said:
you can run the ruu.exe in bootloader mode if you want, it will then switch to ruu mode by itself. If the phone were booted in the OS the ruu.exe will make it reboot in ruu mode.
Click to expand...
Click to collapse

ulises.boom said:
@arlay Sorry to tell you that it didn´t work.
Let me explain a little of what I have here:
It seems that I erase everythin in the Phone except by the Fastboot and Recovery.
I´m having the following errors:
E:Can´t mount /cache/recovery/
E: unknown volume "/sdcard/.android_secure
Running the RUU I got Error 155.
And another thing, it can find /system/xbin/su
Do I hava a recobrable one or a brick?
I have it on s-on and could not made it s-off with revone
Click to expand...
Click to collapse
1- can you post a "fastboot getvar all" (excluding IMEI and s/n)
2- with S-On you need to relock bootloader for RUU (same or higher version) to work
3- for S-Off, you should also try rumrunner and firewater

@nkk71 Here is the results of the getvar
List of devices attached
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4281mV
(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
nkk71 said:
1- can you post a "fastboot getvar all" (excluding IMEI and s/n)
2- with S-On you need to relock bootloader for RUU (same or higher version) to work
3- for S-Off, you should also try rumrunner and firewater
Click to expand...
Click to collapse

ulises.boom said:
@nkk71 Here is the results of the getvar
List of devices attached
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-main: 1.29.1540.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
finished. total time: 0.062s
Click to expand...
Click to collapse
Personally, I would use this ruu.exe : http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
it's the same version as your current one, which would give you a chance to S-Off, if you wish.... a higher version, could make that more difficult.
the RUU will work but you need to lock your bootloader using fastboot oem lock
I know it's ironic that the Dev Edition is bootloader unlocked be default, but RUU's wont work with that.

@arlay & @nkk71 Thanks a million for helping me solve my problem.
I have a functional HTC ONE m7ul Developer Edition back in business.
Now to wait for a KitKat Update to put it on the Mobile.
nkk71 said:
Personally, I would use this ruu.exe : http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
it's the same version as your current one, which would give you a chance to S-Off, if you wish.... a higher version, could make that more difficult.
the RUU will work but you need to lock your bootloader using fastboot oem lock
I know it's ironic that the Dev Edition is bootloader unlocked be default, but RUU's wont work with that.
Click to expand...
Click to collapse

I´m a very happy man again.
Have been receving and updating the phone with already three OTA Updates without any issues so far.
Many thanks to the guys/girls on XDA-Developers for this very helpful site.
ulises.boom said:
@arlay & @nkk71 Thanks a million for helping me solve my problem.
I have a functional HTC ONE m7ul Developer Edition back in business.
Now to wait for a KitKat Update to put it on the Mobile.
Click to expand...
Click to collapse

ulises.boom said:
Hello everybody, I´m a little newbie here so need some URGEN HELP.
1.- I bought an HTC ONE (m7) 64GB Developer Edition from SWAPPA with ClockworkMod Recovery and CyanogenMod 11 on it.
2.- While looking into XDA-Developer was following a thread to get it back to stock recovery using nandroid so I can flash an RUU from HTCDEV
While doing that seems that I erase everything from the phone and now it´s giving me an error mounting e:/ drive and It doesn´t recognize the phone in ADB mode.
I´m stuck with the CWM without the ability to get files into /sdcard/0/clockworkmode/backups
Can someone help me or point me in the right direction to get back to the stock android that the HTC Developer Edition (m7) comes in factory default.
Click to expand...
Click to collapse
Is this the link you talking about?
http://www.youtube.com/watch?v=rpA71FXddyU

[Q] Trouble unrooting my M7

Hello,
So I am trying to unroot my M7 and i have encountered and I thought I have overcome a number of issues. I feel that I should start from the beginning to give you all the best picture of my situation.
I purchased the phone used and it came with the pink camera issue. So after asking Mr. Google, who said that updating might solve the problem. I went ahead to try to update but only to discover that I cant because the phone is rooted.
Okay, so at that point, i decided that since I wont be benefiting from the rootedness of the phone, and spurred on with the news of a new update coming out soon, I decided to unroot and I found this guide.
htc-one (dot) wonderhowto (dot) com/how-to/return-your-rooted-unlocked-htc-one-back-factory-settings-for-warranty-repairs-0149204/
First problem I encountered was that was that adb could not find the device, so I installed the drivers. (took me a few hours)
After that I followed the guide and locked the device and turned S-on. up to this point, it is going smoothly.
Then I downloaded the RUU RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2,
Problem was that it was really slow to load and after i accepted the legal contract, it would suddenly shut down with no warning or explanation.
So I jumped into the literature and installed all the C++ things and then it worked. Sounds great. Big smile on my face, until it starts to freeze at 5% header 1/5.
Great. so that is where I am stuck.
When i am at cmd and type in
C:\Users\Andrew Lee\Downloads\Desktop>cd htcone
C:\Users\Andrew Lee\Downloads\Desktop\htcone>adb push revone /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop\htcone>adb push revone /data/local/tmp/
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>fastboot getvar all
(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: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
also I cannot quit bootloader on the phone. and when i go into device manager, it is under android USB devices, named my HTC and under other devices, there is two base system devices and both have the yellow icons next to it.
I have installed HTC sync in an effort to install the proper drivers and that did not work.
So I am in a pickle. I would prefer to unroot it but atp I dont care anymore, I just want to use the phone.
I have tried to use the zip RUU way of installing the RUU but because it cannot find the device, it is futile. When I plug in the phone, I do here the sound.
I am on Windows 7. I also have a Mac as an alternative.

If you have a Mac, I would use that! You don't have to deal with any driver issues on the Mac or on Linux, like the saying goes... It just works!(tm)
From what you posted, I see that you are S-ON with SuperCID, but I'm not sure what system you originally had, android version, ROM, etc. I assume you are on Telus, since you are trying to flash a Telus RUU. I also see you are trying to run revone.. Are you trying to get S-OFF, or unroot, or get the entire phone completely back to stock? What recovery do you have installed?
Also, FYI - adb doesn't work while you are in the bootloader.

commandaria said:
Hello,
So I am trying to unroot my M7 and i have encountered and I thought I have overcome a number of issues. I feel that I should start from the beginning to give you all the best picture of my situation.
I purchased the phone used and it came with the pink camera issue. So after asking Mr. Google, who said that updating might solve the problem. I went ahead to try to update but only to discover that I cant because the phone is rooted.
Okay, so at that point, i decided that since I wont be benefiting from the rootedness of the phone, and spurred on with the news of a new update coming out soon, I decided to unroot and I found this guide.
htc-one (dot) wonderhowto (dot) com/how-to/return-your-rooted-unlocked-htc-one-back-factory-settings-for-warranty-repairs-0149204/
First problem I encountered was that was that adb could not find the device, so I installed the drivers. (took me a few hours)
After that I followed the guide and locked the device and turned S-on. up to this point, it is going smoothly.
Then I downloaded the RUU RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2,
Problem was that it was really slow to load and after i accepted the legal contract, it would suddenly shut down with no warning or explanation.
So I jumped into the literature and installed all the C++ things and then it worked. Sounds great. Big smile on my face, until it starts to freeze at 5% header 1/5.
Great. so that is where I am stuck.
When i am at cmd and type in
C:\Users\Andrew Lee\Downloads\Desktop>cd htcone
C:\Users\Andrew Lee\Downloads\Desktop\htcone>adb push revone /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop\htcone>adb push revone /data/local/tmp/
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>fastboot getvar all
(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: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
also I cannot quit bootloader on the phone. and when i go into device manager, it is under android USB devices, named my HTC and under other devices, there is two base system devices and both have the yellow icons next to it.
I have installed HTC sync in an eff noort to install the proper drivers and that did not work.
So I am in a pickle. I would prefer to unroot it but atp I dont care anymore, I just want to use the phone.
I have tried to use the zip RUU way of installing the RUU but because it cannot find the device, it is futile. When I plug in the phone, I do here the sound.
I am on Windows 7. I also have a Mac as an alternative.
Click to expand...
Click to collapse
Did you run the command fastboot oem writesecureflag 3 and lock the bootloader? You will have to unlock the bootloader again using htc's unlock token, install custom recovery and install a guru reset (can be found on here) for version 2.24.401.1 which is what your current software is according to your fastboot getvar all
In order to send your phone for repairs, your phone must read as LOCKED and tampered message removed from your bootloader. Your CID must also be reset to the original. To do this you need s off though
To get s off follow the guides for rumrunner or firewater
Do NOT update your firmware past 1.54, its harder to obtain s off. You CAN still get it using sunshine, it costs $25 tho but is awesome and works with stock ROMs
Finally, i wouldnt do the command fastboot oem writesecureflag 3 again on later hboots ie 1.55 or above. This can reset the tamper message on the bootloader
Good luck

synt3k said:
If you have a Mac, I would use that! You don't have to deal with any driver issues on the Mac or on Linux, like the saying goes... It just works!(tm)
From what you posted, I see that you are S-ON with SuperCID, but I'm not sure what system you originally had, android version, ROM, etc. I assume you are on Telus, since you are trying to flash a Telus RUU. I also see you are trying to run revone.. Are you trying to get S-OFF, or unroot, or get the entire phone completely back to stock? What recovery do you have installed?
Also, FYI - adb doesn't work while you are in the bootloader.
Click to expand...
Click to collapse
I cant remember what is the original system it had But i think it was xposed.. It was the last application when it was listed alphabetically. The phone was originally telus, but I am on rogers. i was not sure with RUU to use so I used Telus because I read somewhere that because it is not gsm but cmda I needed to use telus (the article said sprint but I assumed that I would use telus) But, as I am on rogers, would I than need to have s-off and then install the RUU
I am trying to get it back to stock. Not for warranty purposes.
Also I do not know about recovery because when I chose recovery in bootloader, nothing happens.
Also thanks for replying, I really appreciate it,
stovie_steve said:
Did you run the command fastboot oem writesecureflag 3 and lock the bootloader? You will have to unlock the bootloader again using htc's unlock token, install custom recovery and install a guru reset (can be found on here) for version 2.24.401.1 which is what your current software is according to your fastboot getvar all
In order to send your phone for repairs, your phone must read as LOCKED and tampered message removed from your bootloader. Your CID must also be reset to the original. To do this you need s off though
To get s off follow the guides for rumrunner or firewater
Do NOT update your firmware past 1.54, its harder to obtain s off. You CAN still get it using sunshine, it costs $25 tho but is awesome and works with stock ROMs
Finally, i wouldnt do the command fastboot oem writesecureflag 3 again on later hboots ie 1.55 or above. This can reset the tamper message on the bootloader
Good luck
Click to expand...
Click to collapse
Thank you for replying, I did run writesecureflag 3 as per the instructions I was following (really regret it now, should have came here first)
I do not need to send in the phone for repair, the post just sounded more legitimate, I just want to have stock because all i do with my phone is the basic functions, I never saw a need to fettle around with it .
So, I assume from reading both posts that I need to unlock my bootloader again? Do i need s-off if I want to do stock RUU? Do i also need s-off if I want to use rogers on a telus phone?
Also, would sunshine allow me to install the stock RUU? It seems to only unlock and s-off
Thank you all for replying, I really appreciate it.

stovie_steve said:
Did you run the command fastboot oem writesecureflag 3 and lock the bootloader? You will have to unlock the bootloader again using htc's unlock token, install custom recovery and install a guru reset (can be found on here) for version 2.24.401.1 which is what your current software is according to your fastboot getvar all
In order to send your phone for repairs, your phone must read as LOCKED and tampered message removed from your bootloader. Your CID must also be reset to the original. To do this you need s off though
To get s off follow the guides for rumrunner or firewater
Do NOT update your firmware past 1.54, its harder to obtain s off. You CAN still get it using sunshine, it costs $25 tho but is awesome and works with stock ROMs
Finally, i wouldnt do the command fastboot oem writesecureflag 3 again on later hboots ie 1.55 or above. This can reset the tamper message on the bootloader
Good luck
Click to expand...
Click to collapse
Hi,
So i followed your instructions, and low and behold, it worked. I used Guru_Reset_M7_2.24.401.1
But problem is I cannot update, when i press update, it says that it is already updated.
How would I fix it so I can update?
Thank youuu

commandaria said:
Hi,
So i followed your instructions, and low and behold, it worked. I used Guru_Reset_M7_2.24.401.1
But problem is I cannot update, when i press update, it says that it is already updated.
How would I fix it so I can update?
Thank youuu
Click to expand...
Click to collapse
Are you now s off with an unlocked bootloader and did you run the sunshine app? If you did, you can run almost any RUU

[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.

[Q] M7 softbrick (or not?) - help needed!

Hi guys!
I've been trying to get my dear One M7 alive now for 4-5 evenings. Really thought it was bricked for good, but finally made some progress. Here's what happened:
S-OFF, rooted since always but on stock/OTA from HTC. Been updating through OTAs just flashing back stock recovery before update and then switching back. I've been using CWM. I was already on the Lollipop 5.0.2 with Sense 6.0 (sofware revision 7.19.401.2) but received another minor OTA couple of weeks ago. Didn't make note of the new revision, nor the reason for the update but just followed my usual steps. Everything seemed to go as usual, but once booting back up after the update the phone got stock on the boot animation (the htc one w/beats audio just after the sound).
Immediately tried a restore from a backup I have, but continued in the same situation. Tried several/different wipes (even the data partition in the end), but no luck. Tried the best I could to search for info, but all I could find was what I'd already done. Tried to download some RUU's but the files seems corrupted and I cannot get it working. I tried to switch to TWRP, taking a new backup (of my restored, but still not working CWM-backup). Same situation. Then I tried to flash a Cyanogenmod version, and was close to giving up when it didn't work as well. Luckily I tried a couple of times more (perhaps after throwing the phone in the wall a few times) and just out of nowhere it suddenly booted and seems to be working normally. Full of hope I tried a restore again, but back to boot animation. Tried to download a clean stock install file I found on XDA with the same version as mine, but just get stuck again. Once I restore the Cyanogenmod backup, it boots perfectly.
Perhaps I am missing something obvious, but I've been doing these things for many years know (starting with the Desire @ nikez), and this just seems odd. I could seriously need some help to get it back working again as I like the stock Sense 6.0 with Lollipop.
For info some details (btw; I verified it against the data I noted just after my original Lollipop OTA early this year, and it is still identical, so i don't see any vitals have changed):
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: **removed**
(bootloader) imei: **removed**
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4081mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks in advance for any good advice!!

tormagj said:
I was already on the Lollipop 5.0.2 with Sense 6.0 (sofware revision 7.19.401.2) but received another minor OTA couple of weeks ago. Didn't make note of the new revision
Click to expand...
Click to collapse
Its 7.19.401.22
nor the reason for the update
Click to expand...
Click to collapse
bug fixes
but just followed my usual steps.
Click to expand...
Click to collapse
Won't work for this ota, you must be 100% stock.
Thanks in advance for any good advice!![
Click to expand...
Click to collapse
flash the 7.19.401.22 ruu, it will update and fix your phone.
http://forum.xda-developers.com/showpost.php?p=59436794&postcount=2

alray said:
Its 7.19.401.22
flash the 7.19.401.22 ruu, it will update and fix your phone.
http://forum.xda-developers.com/showpost.php?p=59436794&postcount=2
Click to expand...
Click to collapse
Thanks alot alray, I'll test it and report back if I manage to fix my beloved phone. I guess I didn't see that "second generation" in post two

unbricked htc one m7
tormagj said:
Hi guys!
I've been trying to get my dear One M7 alive now for 4-5 evenings. Really thought it was bricked for good, but finally made some progress. Here's what happened:
S-OFF, rooted since always but on stock/OTA from HTC. Been updating through OTAs just flashing back stock recovery before update and then switching back. I've been using CWM. I was already on the Lollipop 5.0.2 with Sense 6.0 (sofware revision 7.19.401.2) but received another minor OTA couple of weeks ago. Didn't make note of the new revision, nor the reason for the update but just followed my usual steps. Everything seemed to go as usual, but once booting back up after the update the phone got stock on the boot animation (the htc one w/beats audio just after the sound).
Immediately tried a restore from a backup I have, but continued in the same situation. Tried several/different wipes (even the data partition in the end), but no luck. Tried the best I could to search for info, but all I could find was what I'd already done. Tried to download some RUU's but the files seems corrupted and I cannot get it working. I tried to switch to TWRP, taking a new backup (of my restored, but still not working CWM-backup). Same situation. Then I tried to flash a Cyanogenmod version, and was close to giving up when it didn't work as well. Luckily I tried a couple of times more (perhaps after throwing the phone in the wall a few times) and just out of nowhere it suddenly booted and seems to be working normally. Full of hope I tried a restore again, but back to boot animation. Tried to download a clean stock install file I found on XDA with the same version as mine, but just get stuck again. Once I restore the Cyanogenmod backup, it boots perfectly.
Perhaps I am missing something obvious, but I've been doing these things for many years know (starting with the Desire @ nikez), and this just seems odd. I could seriously need some help to get it back working again as I like the stock Sense 6.0 with Lollipop.
For info some details (btw; I verified it against the data I noted just after my original Lollipop OTA early this year, and it is still identical, so i don't see any vitals have changed):
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: **removed**
(bootloader) imei: **removed**
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4081mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
**************************************************************************************************
hello sir,
I have htc one m7 sprint manufactured in new zealand.The problem started when I by mistake deleted all the partitions like delvin cache,system,internal
storage,etc in the factory reset option of the bootloader.My phone has unlocked bootloader and latest twrp installed before the problem occurred and android
version 4.2 installed which i think has been deleted as it says when rebooting from the bootloader and it rebooted normally just stucks at hTC logo.
I have installed fastboot,adb(not working properly) by sdk tools on windows 7 32 bit pc and also htc sync manager and latest java.
I request you to reply me as soon as possible as i have just lost my all the patience doing all the methods suggested on the like fastboot,etc and
typing the commands.You are my last hope,please help me.
Htc one bootloader details are:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0315
OpenDSP-v26.120.274.020
eMMC-boot
May 8 2013,16:30:08:1
I have only basic knowledge of android tools and computer.
Thanks a lot for your time and i am waiting for your reply.
Click to expand...
Click to collapse

tormagj said:
Thanks alot alray, I'll test it and report back if I manage to fix my beloved phone. I guess I didn't see that "second generation" in post two
Click to expand...
Click to collapse
@alray - that freaking worked like a charm! Thanks a lot, a donation is on it's way, really thought my beloved phone was gone.
Installed the RUU version 7.19.401.22 as indicated, and that did the trick. I got an error message about HBOOT while flashing it, tried it twice since I saw it mentioned in several threads but the message continued. However, the phone booted normally afterwards so I couldn't care less right now
Code:
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device XXXX.
Also tried desperately to restore the data partition from my cwm backup, but then the phone wouldn't boot again. Last resort now will be to manually restore some of the apps through Titanium from my cwm - but what the heck, lost data is better than lost phone.
Although a minor update, seems like HTC did some serious changes since a lot of the normal stuff doesn't work. Any idea of what??
Anyways, thanks again - really appreciated!

rakeshrinawa said:
hello sir,
I have htc one m7 sprint manufactured in new zealand.The problem started when I by mistake deleted all the partitions like delvin cache,system,internal
storage,etc in the factory reset option of the bootloader.My phone has unlocked bootloader and latest twrp installed before the problem occurred and android
version 4.2 installed which i think has been deleted as it says when rebooting from the bootloader and it rebooted normally just stucks at hTC logo.
I have installed fastboot,adb(not working properly) by sdk tools on windows 7 32 bit pc and also htc sync manager and latest java.
I request you to reply me as soon as possible as i have just lost my all the patience doing all the methods suggested on the like fastboot,etc and
typing the commands.You are my last hope,please help me.
Htc one bootloader details are:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0315
OpenDSP-v26.120.274.020
eMMC-boot
May 8 2013,16:30:08:1
I have only basic knowledge of android tools and computer.
Thanks a lot for your time and i am waiting for your reply.
Click to expand...
Click to collapse
Hi @rakeshrinawa,
I should probably leave it to the pro's to help you out, but I would suggest the following (sure somebody will correct me if I'm on thin ice here):
- Boot into fastboot, open a command prompt and write "fastboot getvar all". Then you'll see the same variables that I posted above, amongst other the version of your software, your CID and some other information that might be useful for the guys helping.
- Look at the selection posted by @alray here http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 (either first or second post).
- You need to find the RUU that fits your phone (correct CID and version), and keep in mind the note in the top:
When you update you must go one step at a time. For example if you are on 6.xx.xxx.xx then you can flash 7.xx.xxx.xx . But if you are on 5.xx.xxx.xx then you cannot flash the 7.xx.xxx.xx you must first flash a 6..xx.xxx.xx.
Click to expand...
Click to collapse
- The trick is to find the right file, but I'm not the right guy to tell you which one. Once you have it, just follow the "How to flash" instructions step by step and hopefully you'll have an almost new phone again just like I had.
- I see your S-ON, so take note of the instructions saying you need to relock the bootloader (item 4 in How to flash). Or perhaps you could just as well S-OFF it ​
I am sure it's possible to solve your issue, keep on trying! Good luck!

rakeshrinawa said:
hello sir,
I have htc one m7 sprint manufactured in new zealand.The problem started when I by mistake deleted all the partitions like delvin cache,system,internal
storage,etc in the factory reset option of the bootloader.My phone has unlocked bootloader and latest twrp installed before the problem occurred and android
version 4.2 installed which i think has been deleted as it says when rebooting from the bootloader and it rebooted normally just stucks at hTC logo.
I have installed fastboot,adb(not working properly) by sdk tools on windows 7 32 bit pc and also htc sync manager and latest java.
I request you to reply me as soon as possible as i have just lost my all the patience doing all the methods suggested on the like fastboot,etc and
typing the commands.You are my last hope,please help me.
Htc one bootloader details are:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0315
OpenDSP-v26.120.274.020
eMMC-boot
May 8 2013,16:30:08:1
I have only basic knowledge of android tools and computer.
Thanks a lot for your time and i am waiting for your reply.
Click to expand...
Click to collapse
Relock your bootloader
Code:
fastboot oem lock
and flash the old sprint ruu:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
fastboot reboot
Then you should update your phone to latest version before unlocking the bootloader, flashing a custom recovery/rom (if you are planning to)

thanks for your reply dear
@alray
Actually this is the only info my bootloader is showing as I have formatted data in the factory reset option.The model no of the phone is PN072(SPRINT) and before this problem,ANdroid 4.2 was installed and now i have installed TWRP 2.6.3.0 and again formatted data and now adb sideload is not working,kindly suggest me the correct softwares which can make my htc one m7 work and do my normal things and can u send me step by step list of softwares to be installed like twrp and adb on my pc as i have 32bit windows 7 on my pc.
Thanks a lot for your reply dear friend and you guys are just amazingly helpful.Keep it on.
---------- Post added at 02:20 AM ---------- Previous post was at 02:07 AM ----------
[/COLOR @alray
I think i have the wrong version of twrp on my phone so adb sideload is not working and i just download your files and simply flash them and will they make my phone work even when i have performed format data and by factory reset in the bootloader?

rakeshrinawa said:
@alray
Actually this is the only info my bootloader is showing as I have formatted data in the factory reset option.The model no of the phone is PN072(SPRINT) and before this problem,ANdroid 4.2 was installed and now i have installed TWRP 2.6.3.0 and again formatted data and now adb sideload is not working,kindly suggest me the correct softwares which can make my htc one m7 work and do my normal things and can u send me step by step list of softwares to be installed like twrp and adb on my pc as i have 32bit windows 7 on my pc.
Thanks a lot for your reply dear friend and you guys are just amazingly helpful.Keep it on.
Click to expand...
Click to collapse
Step you need to do posted above
RUU also posted above
you'll also need adb / fastboot either by downloading the android sdk (SDK Tools only) or minimal adb and fastboot
Save the ruu in the same folder you have installed minimal adb and fastboot or if installed the android sdk, make sure the ruu is in \Android SDK Tools\platform-tools.
Start a command prompt: Start menu --> program --> minimal adb and fastboot --> minimal adb and fastboot.exe or if using the sdk, go to \Android SDK Tools\platform-tools hold shift and right click in the folder and select "start a cmd prompt here".
Reboot your phone in bootloader / fastboot usb mode (make sure "fastboot usb" is shown in red)
then type:
Code:
fastboot oem lock
fastboot reboot-bootloader
This will relock your bootloader, required to flash the ruu
Code:
fastboot oem rebootRUU
once rebooted in ruu mode (black screnn with silver htc logo):
Code:
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
First flash will report "flush image again immediately, so do the same command again:
Code:
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
Wait for the ruu to flash then when you see sucessful message:
Code:
fastboot reboot

HI
@alray
I have HTC ONE M7 sprint variant with model no.PN072 which supports both gsm and cdma and I Was not able to use wcdma or 3g mode when using Android version 4.2.
So keeping all these things,and spending 10 hours in downloaading your files,will they work on my htc and won't create future problems like in google updates etc?
---------- Post added at 05:53 AM ---------- Previous post was at 05:14 AM ----------
[/COLOR @alray
I am sorry to say that before I read your reply,I was actually following instructions from
http://forum.xda-developers.com/showthread.php?t=2503646
and so I have flashed the firmware 5.03.651.3 s-on which is of 39886 bytes and now my new details of bootloader are:
***TAMPERED***
***RELOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v26.120.274.0202
OS-5.03.651.3
eMMC-boot 2048MB
May 15 2014,16:31:22.1
and my fastboot getvar all details are:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 1.01.20.0515
version-cpld: None
version-microp: None
version-main: 5.03.651.3
version-misc: PVT SHIP S-ON
serialno: ***REMOVED***
imei: ***REMOVED***
meid: ***REMOVED***
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4262mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
AND when I downloaded the odex file mentioned by him in the 8c step,I got the error of
remote 12:signature verify failed
and tried then,but got the same error again.
My bootloader is still relocked.
now tell me what should I do?
Hope you bear my stubbornness and Reply.....
Thanks

rakeshrinawa said:
@alray
I have HTC ONE M7 sprint variant with model no.PN072 which supports both gsm and cdma and I Was not able to use wcdma or 3g mode when using Android version 4.2.
So keeping all these things,and spending 10 hours in downloaading your files,will they work on my htc and won't create future problems like in google updates etc?
---------- Post added at 05:53 AM ---------- Previous post was at 05:14 AM ----------
[/COLOR @alray
I am sorry to say that before I read your reply,I was actually following instructions from
http://forum.xda-developers.com/showthread.php?t=2503646
and so I have flashed the firmware 5.03.651.3 s-on which is of 39886 bytes and now my new details of bootloader are:
***TAMPERED***
***RELOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v26.120.274.0202
OS-5.03.651.3
eMMC-boot 2048MB
May 15 2014,16:31:22.1
and my fastboot getvar all details are:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 1.01.20.0515
version-cpld: None
version-microp: None
version-main: 5.03.651.3
version-misc: PVT SHIP S-ON
serialno: ***REMOVED***
imei: ***REMOVED***
meid: ***REMOVED***
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4262mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
AND when I downloaded the odex file mentioned by him in the 8c step,I got the error of
remote 12:signature verify failed
and tried then,but got the same error again.
My bootloader is still relocked.
now tell me what should I do?
Hope you bear my stubbornness and Reply.....
Thanks
Click to expand...
Click to collapse
flash the 5.03.651.3 ruu posted in that thread.

hi
alray said:
flash the 5.03.651.3 ruu posted in that thread.
Click to expand...
Click to collapse
I flashed it with fastboot and it says signature verify failed,tried again and got the same message.
What should I do now,Please help me,I am totally exhausted.

rakeshrinawa said:
I flashed it with fastboot and it says signature verify failed,tried again and got the same message.
Click to expand...
Click to collapse
Its says signature verify fail because you are trying to flash a rom (stock odexed) using fastboot, you must flash this rom using a custom recovery which will require to unlock the bootloader again so the simplest is to keep your bootloader relocked and flash the RUU

hello
alray said:
Its says signature verify fail because you are trying to flash a rom (stock odexed) using fastboot, you must flash this rom using a custom recovery which will require to unlock the bootloader again so the simplest is to keep your bootloader relocked and flash the RUU
Click to expand...
Click to collapse
****
ok then can you send me the link of ruu file i have to flash as adb is not working in my phone and I can unlock my bootloader if you have a solution after that.
waiting for your reply.

rakeshrinawa said:
****
ok then can you send me the link of ruu file i have to flash
Click to expand...
Click to collapse
lol I think we have some communication issues here :laugh:. The RUU is in the same thread you linked me at post #10. All sprint RUU are listed at the beginning of that thread (in the first few lines of the OP), you need the 5.03.651.3 RUU, download it and lauch it (double click, its an .exe file). Make sure your phone is in bootloader when you launch the ruu.