Related
Hi,
Ive got a HTC One here with the problem mentioned in the title. The phone is completely stock, locked bootloader, not rooted, S-ON.
The phone does not get past the HTC screen at all, it stays there for a few seconds and turns off. I can get into the bootloader, but cannot get adb to work. However fastboot is working fine.
Ive tried to unlock the bootloader so that I can try to get a custom recovery and install a ROM that way, but everytime I try to unlock it it restarts and gets stuck again. Comes up as locked once back into the bootloader.
Tried flashing an RUU, but the ones Ive tried bring up a singature failed error, I assume due to the locked bootloader.
Searched, looked, and read through many threads/posts for the past few hours and I cant find anything to help me.
This is what getvar all brings up...
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 4320mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
Please help! Im stuck...just like my phone is!
Install custom recovery
Then you have 2 options
ADB sideload
USB otg both work good
I recommend twrp recovery
Then connect usb then Mount usb with custom Rom in it flash your Rom
Otherwise if you have ruu exe file with same version 3.62.401.1 in your getvar you can install in fastboot mod
HTC One 1.56 S-Off MaximusHD 33
selim97 said:
Hi,
Ive got a HTC One here with the problem mentioned in the title. The phone is completely stock, locked bootloader, not rooted, S-ON.
The phone does not get past the HTC screen at all, it stays there for a few seconds and turns off. I can get into the bootloader, but cannot get adb to work. However fastboot is working fine.
Ive tried to unlock the bootloader so that I can try to get a custom recovery and install a ROM that way, but everytime I try to unlock it it restarts and gets stuck again. Comes up as locked once back into the bootloader.
Tried flashing an RUU, but the ones Ive tried bring up a singature failed error, I assume due to the locked bootloader.
Searched, looked, and read through many threads/posts for the past few hours and I cant find anything to help me.
This is what getvar all brings up...
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 4320mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
Please help! Im stuck...just like my phone is![/QUOTE
What RUU did you try. Link please
With S-On you can flash RUU same version or higher, it will not allow you to flash RUU lower version
Have you tried a hard reset from within the bootloader or fastboot erase cache or the bright light trick. If that fails are you still within warranty, if so send it in for service.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
One of the RUU was an older version, that didnt work for obvious reasons. I then found one for the same version I have but it was called Guru Reset, so I think it may have been slightly modified, that didnt work either.
I have already tried the suggestions you mentioned but its not working. Anything I select from within the bootloader just reboots the phone over again, except fastboot.
I have just found and flashed a newer version of the RUU exe at http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
This seemed to be working, it even said it was complete. But the phone did not reboot itself, I switched it on, and ran into the same problem. Tried erasing cache, again nothing. Tried manually flashing the zip, but I get an error about data length is too large. No idea what is going wrong here.
Unfortunately no warranty.
This is what getvar brings up after the flash...
Code:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.23.3263.28
version-cpld: None
version-microp: None
version-main: 4.19.401.9
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 4282mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
Im desperate to get this fixed! Please help!
Bootloader ? Locked or unlocked ?
Unlock bootloader with HTCdev
Flash custom recovery
Flash guru reset
HTC One 1.56 S-Off MaximusHD 33
yatin kumar said:
Bootloader ? Locked or unlocked ?
Unlock bootloader with HTCdev
Flash custom recovery
Flash guru reset
HTC One 1.56 S-Off MaximusHD 33
Click to expand...
Click to collapse
Bootloader is locked, cannot be unlocked as mentioned in first post. The phone just reboots itself after I select yes to unlock bootloader.
What can be done?
selim97 said:
Bootloader is locked, cannot be unlocked as mentioned in first post. The phone just reboots itself after I select yes to unlock bootloader.
What can be done?
Click to expand...
Click to collapse
try firewater s off 2nd method
It supports many HTC phone
HTC One 1.56 S-Off MaximusHD 33
yatin kumar said:
try firewater s off 2nd method
It supports many HTC phone
HTC One 1.56 S-Off MaximusHD 33
Click to expand...
Click to collapse
Thanks for the input... but that unfortunately wont work either because adb is not working for me, I can only get fastboot to work.
Any other suggestions?
Phone is dead. Throw it away.
SaHiLzZ said:
Phone is dead. Throw it away.
Click to expand...
Click to collapse
Really!? No possible way around this then??
The phone may not be dead, but he combination of locked bootloader and S-ON may be too much. You really need to fix one or the other somehow..
Try the download from here and check MD5 once downloaded
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
How did you try to install the zip manually. Post links and steps please.
PS. adb will only work in booted os or recovery.
Sent from my Nexus 7 using XDA Premium HD app
selim97 said:
Thanks for the input... but that unfortunately wont work either because adb is not working for me, I can only get fastboot to work.
Any other suggestions?
Click to expand...
Click to collapse
I don't really know about this but try search flashing Rom in fastboot
But it not gonna work as s on
Last way service center with paying
HTC One 1.56 S-Off MaximusHD 33
bored_stupid said:
Try the download from here and check MD5 once downloaded
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
How did you try to install the zip manually. Post links and steps please.
PS. adb will only work in booted os or recovery.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That one seems to have the same MD5 as the one Ive already tried...but no worries I am downloading it right now and will give it a go. Willing to try anything to get it back to life!
I extracted the zip and tried flashing using this guide http://forum.xda-developers.com/showthread.php?t=2497614
I get an error saying the data length is too large, no idea what that means.
Thanks for the help so far, if you have any other ideas/suggestions please do let me know.
NxNW said:
The phone may not be dead, but he combination of locked bootloader and S-ON may be too much. You really need to fix one or the other somehow..
Click to expand...
Click to collapse
I know
When I tried unlocking the bootloader it went through to the phone and came up allowing me to select yes or no, but as soon as I press the power button to confirm my selection thats it back to a bootloop.
Try flashing the rom.zip again only this time, try this
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip. (yes twice).
Rename rom.zip to name of the file name.
Sent from my Nexus 7 using XDA Premium HD app
bored_stupid said:
Try flashing the rom.zip again only this time, try this
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip. (yes twice).
Rename rom.zip to name of the file name.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Hi,
Downloaded RUU from the link you provided, MD5 matched. Ran the RUU, but same problem of not being able to boot up.
Followed your instructions on flashing the rom.zip, but I get the same error of data length is too large.
I noticed on the guru website something about encrypted and decrypted zips, maybe the zip needs additional steps before being flashed, maybe thats why Im getting the errors with the zip?
Because you are S-On the RUU needs to be signed
You cannot flash an unsigned RUU
It also needs to be specifically for your phone.
Sent from my Nexus 7 using XDA Premium HD app
Hi, so I followed the instructions to flash the Android Revolution HD rom, everything went well till the phone rebooted, it's now stuck on the htc logo, I still have access to the bootloader, recovery and fastboot, I just dont know what to do next :silly:. Any help is welcome.
jabyz said:
Hi, so I followed the instructions to flash the Android Revolution HD rom, everything went well till the phone rebooted, it's now stuck on the htc logo, I still have access to the bootloader, recovery and fastboot, I just dont know what to do next :silly:. Any help is welcome.
Click to expand...
Click to collapse
Which recovery are you using ?
Seanie280672 said:
Which recovery are you using ?
Click to expand...
Click to collapse
I'm using clockworkmod recovery, the normal one, not the touch based one, and I can't use adb neither.
jabyz said:
I'm using clockworkmod recovery, the normal one, not the touch based one, and I can't use adb neither.
Click to expand...
Click to collapse
adb works in recovery and when booted in android OS
fastboot works in bootloader only.
jabyz said:
I'm using clockworkmod recovery, the normal one, not the touch based one, and I can't use adb neither.
Click to expand...
Click to collapse
I'm pretty sure the op thread states to use twrp recovery, please download and flash version 2.6.3.3 through fastboot then when you get into recovery do a standard wipe not an advanced wipe and try flash the Rom again
Seanie280672 said:
I'm pretty sure the op thread states to use twrp recovery, please download and flash version 2.6.3.3 through fastboot then when you get into recovery do a standard wipe not an advanced wipe and try flash the Rom again
Click to expand...
Click to collapse
Ok, let me try that recovery and I'll follow your recomendations
EDIT: After installing TWRP recovery it wont start, I just see a logo and then it goes to the htc logo and nothing happens, tried the newest version and I've already tried all the older versions, what else should I try?
Are you on an international device or a spirit or verzion device ?
Can you also post a fastboot getvar all too please, be sure to remove the serial number and imei before posting though
Seanie280672 said:
Are you on an international device or a spirit or verzion device ?
Can you also post a fastboot getvar all too please, be sure to remove the serial number and imei before posting though
Click to expand...
Click to collapse
I don't know why I forgot to mention it but yes I'm using a verizon htc one, anyway here is my getvar all
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 1.13.41.0109_2
version-cpld: None
version-microp: None
version-main: 3.11.605.1
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid:
product: m7_wlv
platform: HBOOT-8064
modelid: PN0731000
cidnum: VZW__001
battery-status: good
battery-voltage: 3921mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
jabyz said:
I don't know why I forgot to mention it but yes I'm using a verizon htc one, anyway here is my getvar all
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 1.13.41.0109_2
version-main: 3.11.605.1
version-misc: PVT SHIP S-OFF
product: m7_wlv
platform: HBOOT-8064
modelid: PN0731000
cidnum: VZW__001
security: off
Click to expand...
Click to collapse
your lucky your phone still works
go to the Verizon forums for the files for your phone
Thanks for the heads up, do i need the official stock rom? or can i flash another rom? and how do i transfer the files to my phone? my pc doesnt recognize it.
jabyz said:
Thanks for the heads up, do i need the official stock rom? or can i flash another rom? and how do i transfer the files to my phone? my pc doesnt recognize it.
Click to expand...
Click to collapse
first you need to get the correct recovery back on your phone then find a stock rom in the Verizon forums
If you goto the twrp site, just Google twrp recovery, you can probably download one for particular model, also I'm pretty sure roms like arhd and viper one have links in the main op thread the verzion editions of their roms, that's if of course you want a custom Rom.
Thanks
thanks for your help, I was able to get the phone working properly again, so it turned out I did have adb working but only when in the CWMR, so I pushed the rom.zip to my phone using adb and then I flashed it using CWMR, I still don't know why TWRP wouldn't work. But thanks a lot for your help. I guess the thread can be closed now.
Hi Everyone,
Okay so I have spent the last 3 hours following various guides in order to restore my ViperOne ROM HTC One M7 to a stock HTC ROM along with locking the bootloader again, everything I've tried has failed though. I'm wondering if anyone here can help me as I need to sell this phone ASAP but can't do that until I restore to stock.
Anyway, the bootloader was unlocked using the HTCDev website and I then installed the custom ROM after that. The Bootloader version appears to be 1.57, not sure if that actually matters.
I tried locking the bootloader which worked and then tried to restore using the O2 UK RUU which failed (The app just crashes at the same point every time).
So I'd really appreciate any help from you guys
Thanks in advance
sheppy1 said:
Hi Everyone,
Okay so I have spent the last 3 hours following various guides in order to restore my ViperOne ROM HTC One M7 to a stock HTC ROM along with locking the bootloader again, everything I've tried has failed though. I'm wondering if anyone here can help me as I need to sell this phone ASAP but can't do that until I restore to stock.
Anyway, the bootloader was unlocked using the HTCDev website and I then installed the custom ROM after that. The Bootloader version appears to be 1.57, not sure if that actually matters.
I tried locking the bootloader which worked and then tried to restore using the O2 UK RUU which failed (The app just crashes at the same point every time).
So I'd really appreciate any help from you guys
Thanks in advance
Click to expand...
Click to collapse
Post a fastboot getvar all with the imei and serialno removed. I am guessing that the RUU you ran was for an earlier version and unless you are S-OFF you can only run RUUs that are same OS version or higher.
You will need to use this guide to return to stock.
majmoz said:
Post a fastboot getvar all with the imei and serialno removed. I am guessing that the RUU you ran was for an earlier version and unless you are S-OFF you can only run RUUs that are same OS version or higher.
You will need to use this guide to return to stock.
Click to expand...
Click to collapse
Hi! Sorry for the late reply, please find below the output that you requested:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 3811mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
You were correct, I was trying to boot a lower version. I heard that people have had luck using Firewater to S-OFF with CM11 installed. It didn't help me though. Anything you might be able to suggest would be a massive help! Thanks
sheppy1 said:
Hi! Sorry for the late reply, please find below the output that you requested:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 3811mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
You were correct, I was trying to boot a lower version. I heard that people have had luck using Firewater to S-OFF with CM11 installed. It didn't help me though. Anything you might be able to suggest would be a massive help! Thanks
Click to expand...
Click to collapse
Based on your getvar all you have a Int'l (.401) phone not an O2 UK branded phone. You will need to follow the directions of this site for stock rom 5.11.401.10 and you should be back whole. You can get the stock firmware if you need it from this site: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One%2F401%2F Just select the 5.11.401.10 firmware.
For S-OFF, you need to be as close to stock as you can. If you are getting "whelp not able to S-OFF" then you might look at Sunshine S-OFF, but there is a price use it.
I realised that I had the international version shortly after posting my information back to you in this thread. Okay so I'm not really interested in getting S-OFF, I only wanted it to be able to use the RUU to restore to stock. So if I just follow method 1 from the post you linked me too, will I be back to get back to stock sense? I assume that I would still see "relocked" and "tampered" in my bootloader?
Thanks for all your help so far!
That worked a charm!!! I'm back on stock FW!!! Thank you! One thing though, will the person I sell the phone too be able to get software updates in future?
sheppy1 said:
I realised that I had the international version shortly after posting my information back to you in this thread. Okay so I'm not really interested in getting S-OFF, I only wanted it to be able to use the RUU to restore to stock. So if I just follow method 1 from the post you linked me too, will I be back to get back to stock sense? I assume that I would still see "relocked" and "tampered" in my bootloader?
Thanks for all your help so far!
That worked a charm!!! I'm back on stock FW!!! Thank you! One thing though, will the person I sell the phone too be able to get software updates in future?
Click to expand...
Click to collapse
If you have stock rom, stock recovery & stock firmware, he/she should be able to get OTA assuming you did not put a custom recovery or root after flashing the stock fw.
majmoz said:
If you have stock rom, stock recovery & stock firmware, he/she should be able to get OTA assuming you did not put a custom recovery or root after flashing the stock fw.
Click to expand...
Click to collapse
That's great news! Would the fact that I ran the stock FW recovery zip from your link mean that I no longer have TWRP on my phone or do I have to do something else to get rid of that too?
sheppy1 said:
That's great news! Would the fact that I ran the stock FW recovery zip from your link mean that I no longer have TWRP on my phone or do I have to do something else to get rid of that too?
Click to expand...
Click to collapse
Yes, you will have stock recovery, stock radio and stock hboot.
majmoz said:
Yes, you will have stock recovery, stock radio and stock hboot.
Click to expand...
Click to collapse
Thanks for all your help!
Should my bootloader still say "tampered"?
sheppy1 said:
Should my bootloader still say "tampered"?
Click to expand...
Click to collapse
Yes, you would have to be S-OFF to reset it.
Okay thank you! Was just thinking that something sill wasn't back to stock so thought I'd check
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.
Hey guys, so recently I purchased a htc one m7 (sprint) off of ebay. I planned to fix it because it was listed as in a bootloop. I thought this would be easy to fix, but I have run into some trouble. The phone does not boot, it just sits on the htc screen. Phone is currently s-on. I have full access to fastboot, but thats it. I feel like I have looked everywhere for a solution, but nothing has worked for me. Any help would be greatly appreciated.
Things I have tried:
1. factory reseting from bootloader menu.
2. entering recovery mode through bootloader menu. (goes back into bootloop, assuming recovery is corrupted)
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
4. flashing twrp (fails due to locked bootloader)
5. using a RUU.exe to flash back to stock (bootloop, gets hung up on "waiting for bootloader..". If i manually put it back into fastboot I get a connection error)
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop. Tried flashing without rebootRUU and got a verification error.
So, any ideas or is this thing bricked? Thanks.
Are you trying to run the RUU while already in fastboot, or are you trying to let the exe boot to fastboot for you? I'm assuming that you are running the RUU from fastboot, and the rebootRUU from the exe is looping you again?
Have you tried flashing the stock recovery?
Have you tried fastboot erase cache? (probably won't help in your situation, but why not?)
Those are some things you could try.
I am having this thread moved to the M7 Q&A forum. You'll have a good chance there of someone providing the steps you need to take to get yourself fixed up.
I suggest that you post the results of fastboot getvar all (minus you IMEI/MEID and serial# of course) so we have a better understanding of your firmware version and such.
Good luck!
yeah, im running the exe while in fastboot, and the rebootRUU loops me. I havent flashed stock recovery. will that allow me to flash anything to get this working? and i did try to wipe cache from fastboot.
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
murphyhobo said:
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Danny201281 said:
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
murphyhobo said:
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
Click to expand...
Click to collapse
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
xunholyx said:
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
Click to expand...
Click to collapse
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
murphyhobo said:
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
Click to expand...
Click to collapse
Unfortunately I think it is a lost cause . If the bootloader is not stable then it's almost certainly a hardware problem.
Even if it was some low level software issue without a stable bootloader there is no way to flash anything to the device.
Maybe sell it on eBay as Spares to try get something back from it.
Sent from my SM-T230 using Tapatalk
Alright, thanks for the help!
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
raghav9 9 said:
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
Click to expand...
Click to collapse
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
alray said:
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
Click to expand...
Click to collapse
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
raghav9 9 said:
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Sorry but what you are saying is making me believe you didn't read what the OP said at all except maybe the first few lines...
Use firewater or revan to s-off first
Click to expand...
Click to collapse
Firewater is discontinued and doesn't work anymore, Revone S-OFF is for hboot 1.44 only, OP's phone is on 1.61. Achieving S-OFF requires a booting phone, exactly what the OP doesn't have. And BTW there a much newer RUU he could use than the one you have posted above that wouldn't requires S-OFF.
Then unlock by htc dev
Click to expand...
Click to collapse
I guess you missed that part:
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
Click to expand...
Click to collapse
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Not possible since like OP said:
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop.
Click to expand...
Click to collapse
Its either a corrupt bootloader/firmware or an hardware problem and like Danny said its a lost cause.