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
Related
Hey guys,
Sorry if I am in the wrong place for this question but I am completely stuck. I recently bought a HTC One M7 which was rooted. I did not know this when I was buying it. The new update came out and my phone asked me to update. I hit yes. My phone switched off and didn't come back on. After extensive research I got it back on to find the following:
1) It was rooted
2)Bootloader started up and TWRP is on the phone
3) There is now nothing on the phone. No firmware or packages at all
4) When I try to flash anything I get the error message: can't mount to system. I can mount to everything else ok just not internal storage.
I am unsure what recovery image and RUU to use. The phone (I was told was unlocked) was O2(Giffgaff).
Details are:
***Tampered***
***Unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
Radio-4A.21.3263.04
OpenDSP-v32.120.724.0909
OS-3.62.206.1
eMMC-boot 2048MB
Oct 18 2013, 00:29:38. 0
IMAGE CRC
rpm: 0xC5567FC
sbl1: 0x9FE7A28C
sbl2: 0XA915A4DD
sbl3: 0xB221B6BB
tz: 0XCCD5DF62
radio: 0XEFA42613
hboot: 0xC174663B
boot: 0x94C89910
recovery: 0x59BF6CD
system: 0xFF83AB1
Any help at this stage would be greatly appreciated! I am about to just give up and bin it...
Thanks in advance!
When does it fail mounting system? When flashing a ROM in TWRP or flashing an RUU?
aooga said:
When does it fail mounting system? When flashing a ROM in TWRP or flashing an RUU?
Click to expand...
Click to collapse
it seems to be both. I try to flash RUU via fastboot and I get a signature fail. So I try to flash a ROM to the phone and it says failed to mount system. I put the items on a usb and tried it but get an 'unable to unzip' error. Its a bit above me to be honest. Thank you so much for helping.
olimoh8464 said:
it seems to be both. I try to flash RUU via fastboot and I get a signature fail. So I try to flash a ROM to the phone and it says failed to mount system. I put the items on a usb and tried it but get an 'unable to unzip' error. Its a bit above me to be honest. Thank you so much for helping.
Click to expand...
Click to collapse
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...
Devilish_Angel said:
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...
Click to expand...
Click to collapse
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?
olimoh8464 said:
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?
Click to expand...
Click to collapse
... run it from desktop while phone in bootloader. no need to run boot image ...
olimoh8464 said:
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?
Click to expand...
Click to collapse
RUU must match your CID number.
I add you here link to a good thread:
http://forum.xda-developers.com/showthread.php?t=2358738
tetakpatalked from Nexus 7 flo
Devilish_Angel said:
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...
Click to expand...
Click to collapse
This is wrong. You can flash the ruu that mathches the cid and mid of your phone even with a locked bl.
Sent from my GT-I9505 using Tapatalk
Thank you for the advice and the link! I will go try this now and let you know how I get on!
aooga said:
This is wrong. You can flash the ruu that mathches the cid and mid of your phone even with a locked bl.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
... did i say something different than what you are saying ...
@aooga Angel's point was S-On, I think.
tetakpatalked from the legendary i9000
olimoh8464 said:
Hey guys,
Sorry if I am in the wrong place for this question but I am completely stuck. I recently bought a HTC One M7 which was rooted. I did not know this when I was buying it. The new update came out and my phone asked me to update. I hit yes. My phone switched off and didn't come back on. After extensive research I got it back on to find the following:
1) It was rooted
2)Bootloader started up and TWRP is on the phone
3) There is now nothing on the phone. No firmware or packages at all
4) When I try to flash anything I get the error message: can't mount to system. I can mount to everything else ok just not internal storage.
I am unsure what recovery image and RUU to use. The phone (I was told was unlocked) was O2(Giffgaff).
Details are:
***Tampered***
***Unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
Radio-4A.21.3263.04
OpenDSP-v32.120.724.0909
OS-3.62.206.1
eMMC-boot 2048MB
Oct 18 2013, 00:29:38. 0
IMAGE CRC
rpm: 0xC5567FC
sbl1: 0x9FE7A28C
sbl2: 0XA915A4DD
sbl3: 0xB221B6BB
tz: 0XCCD5DF62
radio: 0XEFA42613
hboot: 0xC174663B
boot: 0x94C89910
recovery: 0x59BF6CD
system: 0xFF83AB1
Any help at this stage would be greatly appreciated! I am about to just give up and bin it...
Thanks in advance!
Click to expand...
Click to collapse
Post a fastboot getvar all
RUU.exe files or ROM Update Utility files are executable files that run on Windows PC
RUU.zip files are simply the same as above but rather than using a Windows exe file to run them, they are packaged in a zip file that can be flashed in Fastboot mode
The RUU has to match your CID/MID. If your S-On, the RUU as to be same version or higher
Sent from my Nexus 7 using XDA Premium 4 mobile app
Devilish_Angel said:
... did i say something different than what you are saying ...
Click to expand...
Click to collapse
Uh..yeah. You said:
when bootloader is unlocked and phone s-on, no ruu will work
Click to expand...
Click to collapse
bored_stupid said:
Post a fastboot getvar all
RUU.exe files or ROM Update Utility files are executable files that run on Windows PC
RUU.zip files are simply the same as above but rather than using a Windows exe file to run them, they are packaged in a zip file that can be flashed in Fastboot mode
The RUU has to match your CID/MID. If your S-On, the RUU as to be same version or higher
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks! Is there any way you could tell me the correct RUU to download? I will post a fastboot getvar all after work this evening. I tried one that I thought was right but when I click to run it as administrator I get prompted with the normal are you sure? click yes and nothing happens. It just doesn't run. Tried downloading it again but still nothing. Any ideas?
olimoh8464 said:
Thanks! Is there any way you could tell me the correct RUU to download? I will post a fastboot getvar all after work this evening. I tried one that I thought was right but when I click to run it as administrator I get prompted with the normal are you sure? click yes and nothing happens. It just doesn't run. Tried downloading it again but still nothing. Any ideas?
Click to expand...
Click to collapse
Yeah no problems. Off to work myself now, but will post correct link if any and possible other solutions.
Sent from my HTC One using XDA Premium 4 mobile app
bored_stupid said:
Yeah no problems. Off to work myself now, but will post correct link if any and possible other solutions.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
C:\Users\milo\Desktop\Newest>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W900013
(bootloader) imei: 3578640********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3965mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
OMG My phone literally did the same exact thing today!! I woke up, a few things were force closing so I decided that I would just reboot the phone...... Big mistake, once I did that, the phone just stayed in the booting up animation. So I figured hey what ever ill just reflash the ROM in TWRP.......Nope, couldn't boot into recovery either, the phone would flash the TWRP screen then just reset itself. Again, I thought no biggie ill just reinstall TWRP. This (again) proved to be useless, after multiple (successful) install's the phone still refused to boot into TWRP. So I finally got CWM to install, a noticed a few things at the bottom of the screen about something not being mounted properly, I didn't pay that much attention to it, i just wanted my phone back at that point. I tried to wipe my phone for a fresh flash, but as soon as the wipe began the phone reset itself. At this point I was on the brink of throwing this thing into the torrential down-pour that god decided to place in my city.
Next I tried to install Viper ROM because I knew it had a wipe functionality built into it's Aroma installer. Went through all the checklists got to the start install screen, clicked next, and then began to wipe......... and then reset again........
So finally I got TWRP reinstalled, and go install a fresh ROM and and immediately met with a screen full of : "Unable to Mount XXXXXXX" (Picture attached). So then I figure alright well my last resort has to be to use a RUU. Found this nice little thread (http://forum.xda-developers.com/showthread.php?t=2316726) and decided to use the FUU (4.19.401.11 Full Wipe). Unfortunately all that did was move my HBoot from 1.4 (or something like that) to 1.5 (or something like that), put the tamper flag back, and bring back the annoying red text at the bottom of the phone at boot (the thing about development build, blah blah blah). I reinstalled TWRP yet again hoping for the best, but still nothing. It cant seem to mount anything (what ever that means).
So now im here, stuck using my old One X. Any suggestions or answers or criticism would be very much appreciated.
Thank you!!!!!
olimoh8464 said:
C:\Users\milo\Desktop\Newest>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W900013
(bootloader) imei: 3578640********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3965mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
This is the RUU.exe you require. Run from PC
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_353143_signed_2-exe/
Sent from my HTC One using XDA Premium 4 mobile app
bored_stupid said:
This is the RUU.exe you require. Run from PC
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_353143_signed_2-exe/
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for that! I have downloaded it and tried to run it but it doesn't open? I get the loading message after I click run as administrator but nothing happens. Do I need HTC sync installed or deleted for this?
Thanks
olimoh8464 said:
Thanks for that! I have downloaded it and tried to run it but it doesn't open? I get the loading message after I click run as administrator but nothing happens. Do I need HTC sync installed or deleted for this?
Thanks
Click to expand...
Click to collapse
Did you check the MD5
4961fdbbadba53c9640f3638f56faec1
When you say nothing happens.. Doesn't it even try to run?
Sent from my HTC One using XDA Premium 4 mobile app
Hello,
I hope somebody can help me with a new HTC One. It stucks in bootloops. Sometimes I can get to the lockscreen: But when I unlock the device the HTC-logo shows up and the phone restarts again. Some ideas to solve my problems? I thought I could flash the ruu with fastboot? but it failed - well, maybe it was the wrong firmware or did another mistake..
The device is locked - so no recovery and no root, but I can reach the bootloader
Hboot 1.57.0000
firmware 5.12.206.3
UPDATE
Oh well. It is an O2-model.. so I need an O2-ruu and if I can't find an O2-ruu I can't unbrick my phone??!!
seven09 said:
Hello,
I hope somebody can help me with a new HTC One. It stucks in bootloops. Sometimes I can get to the lockscreen: But when I unlock the device the HTC-logo shows up and the phone restarts again. Some ideas to solve my problems? I thought I could flash the ruu with fastboot? but it failed - well, maybe it was the wrong firmware or did another mistake..
The device is locked - so no recovery and no root, but I can reach the bootloader
Hboot 1.57.0000
firmware 5.12.206.3
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.206.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4294mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
UPDATE
Oh well. It is an O2-model.. so I need an O2-ruu and if I can't find an O2-ruu I can't unbrick my phone??!!
Click to expand...
Click to collapse
1st of all delete IMEI No & serial number from your post above
Go to bootloader select recovery
In recovery wipe cache and restart
( If recovery not show menu then press volume up 1st + power button 2nd for 5 secs then leave power button then volume it will show menu )
If wipe cache not working you have to factory reset your phone from bootloader
This problem arises when any installed app trouble with boot or corrupt app data
Thanks for your reply..
but nothing worked. I opened the bootloader and installed cwm. After that I tried to restore an old backup, which I found on the Internet and flashed a custom rom as well... :S
Oh now it boots
But every 2 min my device reboots... ??
seven09 said:
Thanks for your reply..
but nothing worked. I opened the bootloader and installed cwm. After that I tried to restore an old backup, which I found on the Internet and flashed a custom rom as well... :S
Oh now it boots
But every 2 min my device reboots... ??
Click to expand...
Click to collapse
what backup version? If using a backup it must be the same version as your firmware (version shown in bootloader).
You should try to flash a custom like ARHD 83, easiest way to get your device booting again. (use TWRP 2.6.3.3)
There is no RUU for this version, so forget RUU unless you want to convert your phone to another version (s-off required)
alray said:
what backup version? If using a backup it must be the same version as your firmware (version shown in bootloader).
You should try to flash a custom like ARHD 83, easiest way to get your device booting again. (use TWRP 2.6.3.3)
There is no RUU for this version, so forget RUU unless you want to convert your phone to another version (s-off required)
Click to expand...
Click to collapse
hmmm, I already tried AHD 83. but I still get reboots very often
Yes there is no RUU. I thought I could maybe try to get s-off, change the cid and install another RUU.. But I dunno if it would solve my Reboot-problem.. Maybe, but I do not want to pay 25 bucks for nothing (sunshine - HBoot 1.57)
seven09 said:
hmmm, I already tried AHD 83. but I still get reboots very often
Yes there is no RUU. I thought I could maybe try to get s-off, change the cid and install another RUU.. But I dunno if it would solve my Reboot-problem.. Maybe, but I do not want to pay 25 bucks for nothing (sunshine - HBoot 1.57)
Click to expand...
Click to collapse
If you achieve S-Off to flash a Ruu, and your phone still have the rebooting issue, then youll know its an hardware problem. 25$ worth it imo
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, I'm relatively new to this and my english is pretty bad so sorry in advance but I've tried to fix this for a few hours now and I've only made the situation worse for myself
I found my "old" HTC One M7 a couple of days back so I thought it would be a good idea to root it and play around with xposed framework and some cool modules I heard about. So I managed to unlock the bootloader, flash CWM Recovery and root my phone. No problems so far.
Now, yesterday I wanted to remove xposed framework from my phone so I thought I could just recover from the backup I made in CWM Recovery before I installed the framework. Turns out that was not the greatest of ideas and my phone got stuck on the boot screen.
I didnt think of it like such a big deal and I tried to factory reset and wipe the phone to maybe get it working again. Turns out that was not the greatest idea either and now I cant go into recovery, I can't flash a new recovery and my computer wont recognizes my phone at all (Except for fastboot)
I've installed and uninstalled all drivers I could possibly think of and find and I still cant find a solution to my problem. I tried to flash a RUU but that didnt work either. I can barely do anything with my phone anymore and I can't think of anything else I havent tried. Please help
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.19.401.30
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4129mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e2a13e5
hbootpreupdate: 11
gencheckpt: 0
My bootloader shows the Tempered , Relocked and Security Warning flags
deleted
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
vilan22 said:
Hey guys, I'm relatively new to this and my english is pretty bad so sorry in advance but I've tried to fix this for a few hours now and I've only made the situation worse for myself
I found my "old" HTC One M7 a couple of days back so I thought it would be a good idea to root it and play around with xposed framework and some cool modules I heard about. So I managed to unlock the bootloader, flash CWM Recovery and root my phone. No problems so far.
Now, yesterday I wanted to remove xposed framework from my phone so I thought I could just recover from the backup I made in CWM Recovery before I installed the framework. Turns out that was not the greatest of ideas and my phone got stuck on the boot screen.
I didnt think of it like such a big deal and I tried to factory reset and wipe the phone to maybe get it working again. Turns out that was not the greatest idea either and now I cant go into recovery, I can't flash a new recovery and my computer wont recognizes my phone at all (Except for fastboot)
I've installed and uninstalled all drivers I could possibly think of and find and I still cant find a solution to my problem. I tried to flash a RUU but that didnt work either. I can barely do anything with my phone anymore and I can't think of anything else I havent tried. Please help
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.19.401.30
version-misc: PVT SHIP S-ON
serialno: SH36EW905338
imei: 357864055623936
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4129mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e2a13e5
hbootpreupdate: 11
gencheckpt: 0
My bootloader shows the Tempered , Relocked and Security Warning flags
Click to expand...
Click to collapse
You need to flash firmware again, search on arhd's website they have all the firmwares and after that ruu will work, I don't remember step by step process but you can always search on google. For RUU to work you need to flash firmware first, its mandatory.
RUU contains the firmware, so there is no need to flash anything except the actual RUU. You problem is relocked bootloader and custom recovery. First thing you need to do is unlock your bootloader again. Then we can talk about other steps to get your phone working again
donkeykong1 said:
RUU contains the firmware, so there is no need to flash anything except the actual RUU. You problem is relocked bootloader and custom recovery. First thing you need to do is unlock your bootloader again. Then we can talk about other steps to get your phone working again
Click to expand...
Click to collapse
Alright, I unlocked the bootloader again. What now?
vilan22 said:
Alright, I unlocked the bootloader again. What now?
Click to expand...
Click to collapse
Now download TWRP recovery and flash it via fastboot
donkeykong1 said:
Now download TWRP recovery and flash it via fastboot
Click to expand...
Click to collapse
Done and working!
vilan22 said:
Done and working!
Click to expand...
Click to collapse
Great! Now, download ARHD ROM, and tranfer the zip to your phone using MTP option in recovery
While you wait, you might want to edit your "fastboot getvar all" and remove your IMEI and serial no [emoji6]
donkeykong1 said:
Great! Now, download ARHD ROM, and tranfer the zip to your phone using MTP option in recovery
While you wait, you might want to edit your "fastboot getvar all" and remove your IMEI and serial no [emoji6]
Click to expand...
Click to collapse
Alright, do I flash the ROM now?
vilan22 said:
Alright, do I flash the ROM now?
Click to expand...
Click to collapse
Yep! Flash away [emoji4]
donkeykong1 said:
Yep! Flash away [emoji4]
Click to expand...
Click to collapse
Flashed successfully and it seems to be working just fine Thanks for the help! Learned alot from this
vilan22 said:
Flashed successfully and it seems to be working just fine Thanks for the help! Learned alot from this
Click to expand...
Click to collapse
Great! Enjoy your phone, and feel free to ask if you need anything [emoji4]
Hey guys, so recently I purchased a htc one m7 (sprint) off of ebay. I planned to fix it because it was listed as in a bootloop. I thought this would be easy to fix, but I have run into some trouble. The phone does not boot, it just sits on the htc screen. Phone is currently s-on. I have full access to fastboot, but thats it. I feel like I have looked everywhere for a solution, but nothing has worked for me. Any help would be greatly appreciated.
Things I have tried:
1. factory reseting from bootloader menu.
2. entering recovery mode through bootloader menu. (goes back into bootloop, assuming recovery is corrupted)
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
4. flashing twrp (fails due to locked bootloader)
5. using a RUU.exe to flash back to stock (bootloop, gets hung up on "waiting for bootloader..". If i manually put it back into fastboot I get a connection error)
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop. Tried flashing without rebootRUU and got a verification error.
So, any ideas or is this thing bricked? Thanks.
Are you trying to run the RUU while already in fastboot, or are you trying to let the exe boot to fastboot for you? I'm assuming that you are running the RUU from fastboot, and the rebootRUU from the exe is looping you again?
Have you tried flashing the stock recovery?
Have you tried fastboot erase cache? (probably won't help in your situation, but why not?)
Those are some things you could try.
I am having this thread moved to the M7 Q&A forum. You'll have a good chance there of someone providing the steps you need to take to get yourself fixed up.
I suggest that you post the results of fastboot getvar all (minus you IMEI/MEID and serial# of course) so we have a better understanding of your firmware version and such.
Good luck!
yeah, im running the exe while in fastboot, and the rebootRUU loops me. I havent flashed stock recovery. will that allow me to flash anything to get this working? and i did try to wipe cache from fastboot.
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
murphyhobo said:
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Danny201281 said:
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
murphyhobo said:
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
Click to expand...
Click to collapse
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
xunholyx said:
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
Click to expand...
Click to collapse
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
murphyhobo said:
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
Click to expand...
Click to collapse
Unfortunately I think it is a lost cause . If the bootloader is not stable then it's almost certainly a hardware problem.
Even if it was some low level software issue without a stable bootloader there is no way to flash anything to the device.
Maybe sell it on eBay as Spares to try get something back from it.
Sent from my SM-T230 using Tapatalk
Alright, thanks for the help!
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
raghav9 9 said:
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
Click to expand...
Click to collapse
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
alray said:
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
Click to expand...
Click to collapse
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
raghav9 9 said:
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Sorry but what you are saying is making me believe you didn't read what the OP said at all except maybe the first few lines...
Use firewater or revan to s-off first
Click to expand...
Click to collapse
Firewater is discontinued and doesn't work anymore, Revone S-OFF is for hboot 1.44 only, OP's phone is on 1.61. Achieving S-OFF requires a booting phone, exactly what the OP doesn't have. And BTW there a much newer RUU he could use than the one you have posted above that wouldn't requires S-OFF.
Then unlock by htc dev
Click to expand...
Click to collapse
I guess you missed that part:
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
Click to expand...
Click to collapse
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Not possible since like OP said:
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop.
Click to expand...
Click to collapse
Its either a corrupt bootloader/firmware or an hardware problem and like Danny said its a lost cause.