[Q] No recovery and boot loop. Need help! - One (M7) Q&A, Help & Troubleshooting

Hi everyone!
I hope someone can help me with my issue. I have read 1 million threads about problems similar to mine, and have probably missed the solution between all the endless lines of text. But I hope you guys can help me.
Device information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
My screen
*** TAMPERED ***
*** RELOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31-120-274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 3013,00:54:00.0
This is what I am working with.
I have downloaded countless RUU files, both zips on my mac, and EXE on my pc. My theory is that I need to get S-OFF to flash the RUU on my phone. I can't reach recovery nor the rom itself. I always get the signature fails. All the time. Even when I take out a signatured recovery.img file from the RUU and fastboot flash recovery I can't get passed it.
Basically I need someone to help med with the question; How do I get from here to a completely stock rom?
Can someone please help me or even point me in the right direction?

Sturelarsson said:
Hi everyone!
I hope someone can help me with my issue. I have read 1 million threads about problems similar to mine, and have probably missed the solution between all the endless lines of text. But I hope you guys can help me.
Device information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
My screen
*** TAMPERED ***
*** RELOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31-120-274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 3013,00:54:00.0
This is what I am working with.
I have downloaded countless RUU files, both zips on my mac, and EXE on my pc. My theory is that I need to get S-OFF to flash the RUU on my phone. I can't reach recovery nor the rom itself. I always get the signature fails. All the time. Even when I take out a signatured recovery.img file from the RUU and fastboot flash recovery I can't get passed it.
Basically I need someone to help med with the question; How do I get from here to a completely stock rom?
Can someone please help me or even point me in the right direction?
Click to expand...
Click to collapse
This RUU should work, Leave bootloader locked. No need for S-off
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe

mb_guy said:
This RUU should work, Leave bootloader locked. No need for S-off
Click to expand...
Click to collapse
Thank you for the quick response! I will try it right away.

Sturelarsson said:
Thank you for the quick response! I will try it right away.
Click to expand...
Click to collapse
Yep the ruu should work but don't forget it will not remove the tampered flag and will not set the bootloader to Locked instead of Re-locked.
Dont forget that this ruu will update your hboot to 1.56+ and there is no reliable s-off method for this version atm. So you'll be stock rom with a tampered and relocked bootloader with almost no possiblities to s-off atm.

Dvemen are
alray said:
Yep the ruu should work but don't forget it will not remove the tampered flag and will not set the bootloader to Locked instead of Re-locked.
Dont forget that this ruu will update your hboot to 1.56+ and there is no reliable s-off method for this version atm. So you'll be stock rom with a tampered and relocked bootloader with almost no possiblities to s-off atm.
Click to expand...
Click to collapse
Well I am just happy too see it working again. Have had it like this for the past 2 mounths. So I can wait for a S-OFF for the 1.56.
Thanks for the information though! I have just now downloaded the file. Will test it and report back.

Sturelarsson said:
Well I am just happy too see it working again. Have had it like this for the past 2 mounths. So I can wait for a S-OFF for the 1.56.
Thanks for the information though! I have just now downloaded the file. Will test it and report back.
Click to expand...
Click to collapse
yes but the tampered flag and relocked bootloader will void your warranty if you need to send the device for repair.

alray said:
yes but the tampered flag and relocked bootloader will void your warranty if you need to send the device for repair.
Click to expand...
Click to collapse
Well, in the state my phone is in right now, do I have any other options which maybe keep me in a unlocked state with a possible S-OFF? I just don't see it. Please tell me if you do.

Sturelarsson said:
Well, in the state my phone is in right now, do I have any other options which maybe keep me in a unlocked state with a possible S-OFF? I just don't see it. Please tell me if you do.
Click to expand...
Click to collapse
You should flash a custom rom like arhd first and s-off then run the above ruu.
S-off is difficult to achieve atm on hboot 1.56 which will be flashed with the above ruu.
If something goes wrong with your phone and it must be send for repair, you'll need to set the bootloader to ''LOCKED'' not ''RELOCKED'' and remove the ''TAMPERED'' flag which require S-OFF. Then you'll need to turn back S-ON but it will cause the tampered flag to come back if its done on hboot 1.55+ So you'll also need to downgrade your phone to 1.44/1.54 before turning back S-ON, downgrading require S-OFF.
Just in case, its better to S-OFF before running the RUU imo, otherwise you might be stock with a tampered and relocked bootloader for some time.

alray said:
You should flash a custom rom like arhd first and s-off then run the above ruu.
S-off is difficult to achieve atm on hboot 1.56 which will be flashed with the above ruu.
If something goes wrong with your phone and it must be send for repair, you'll need to set the bootloader to ''LOCKED'' not ''RELOCKED'' and remove the ''TAMPERED'' flag which require S-OFF. Then you'll need to turn back S-ON but it will cause the tampered flag to come back if its done on hboot 1.55+ So you'll also need to downgrade your phone to 1.44/1.54 before turning back S-ON, downgrading require S-OFF.
Just in case, its better to S-OFF before running the RUU imo, otherwise you might be stock with a tampered and relocked bootloader for some time.
Click to expand...
Click to collapse
Okay. It't seemed so hard cause of the signing problems I have had when trying to flash roms through fastboot. My recovery is screwed up and I have tried to flash TWRP on there but it won't let me change any of that stuff. Just signature failure. All the time! Tried the RUU exe file and it got an error saying it was the wrong one for my device..
If you have any suggestions to where I can find a recovery / which rom I would be very happy. :fingers-crossed:

Sturelarsson said:
Okay. It't seemed so hard cause of the signing problems I have had when trying to flash roms through fastboot. My recovery is screwed up and I have tried to flash TWRP on there but it won't let me change any of that stuff. Just signature failure. All the time! Tried the RUU exe file and it got an error saying it was the wrong one for my device..
If you have any suggestions to where I can find a recovery / which rom I would be very happy. :fingers-crossed:
Click to expand...
Click to collapse
Yes obviously you can't flash a recovery because your bootloader is RELOCKED! you need an unlocked bootloader to flash recovery.
And you can't flash rom from fastboot, only from a custom recovery!
Only an ruu can be flashed from fastboot when the phone is in RUU mode (fastboot oem rebootRUU)
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
http://forum.xda-developers.com/showthread.php?t=2183023
Unlock bootloader
flash the recovery and clear cache:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
push the rom to your sdcard:
boot in twrp
adb push <name_of_rom>.zip /sdcard/
flash the rom:
In twrp select ''install''
chose the rom
swipe to flash
reboot after its complete

alray said:
Yes obviously you can't flash a recovery because your bootloader is RELOCKED! you need an unlocked bootloader to flash recovery.
And you can't flash rom from fastboot, only from a custom recovery!
Only an ruu can be flashed from fastboot when the phone is in RUU mode (fastboot oem rebootRUU)
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
http://forum.xda-developers.com/showthread.php?t=2183023
Unlock bootloader
flash the recovery and clear cache:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
push the rom to your sdcard:
boot in twrp
adb push <name_of_rom>.zip /sdcard/
flash the rom:
In twrp select ''install''
chose the rom
swipe to flash
reboot after its complete
Click to expand...
Click to collapse
Thanks for everything! I have unlocked boot loader and flashed recovery. Launched in twrp and pushed the rom to the sdcard. But when I try to flash from recovery it just fails. Something wrong with cache. I tried to wipe cache / dalwik and do a complete clean install but same problem again. Can't even wipe cache. I will update you with exactly what says if needed.
Edit: This is exactly what it says when I try.
Updating partition details...
Error flashing zip '/sdcard/rom.zip'
Updating partition details

Well never mind the last post. The problem was in safari which always decompresses the zip file before it can be accessed. When I compressed it again and pushed it over to the M7 I got "failed flash" problem. I tried downloading through google chrome instead, the zip was intact, and I was able to flash the rom!
I just want to say thank you for your time and effort in this small problem. It literally took me 30 minutes to get my phone from f**cked to working again. Thank you sooo much! Next time I'm going to ask for help here at the forums instead of just reading myself blind and not getting anywhere.
Sincerely

Related

[Q] Restoring 100% to stock, not working as it should...

Hi guys,
First of all, I did read all the topics conserning to RUU, S-On/S-Off, rumrunner, moonshine, firewater, revone, and so on but I can't seem to figure out how to properly do this.
Currently the HTC is running MIUI v5 4.5.16 JB4.2. But for warranty it has to go back to the store and I want to restore it to completly stock ROM etc. without any evidence I had a custom ROM running.
What I did was, follow the steps to unlock the bootloader, flash a custom recover (TWRP v2.6.3.0) and finally root it after MIUI was flashed.
The info you guys prolly need are as followed:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.26.3263.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: .................
(bootloader) imei: ................
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.038s
Click to expand...
Click to collapse
I tried to get S-Off but I keep getting strange errors on all of the given methods. This should work somehow I guess but how? Can somebody give me some kind of "roadmap" how to do it properly?
Currently fastboot shows:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.26.3263.05
OpenDSP-v32.120.274.0909
OS-4.19.161.11
eMMC-boot 2048MB
Mar 5 2014,15:58:33.0
Click to expand...
Click to collapse
At the moment I'm downloading "RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe". But I already noticed that if I turn S-On (fastboot oem lock) then the phone is stuck in fast boot mode...
Thanks!
I think S-off is danger may u brick ur phone, it's better to leave it
ahmed blue said:
I think S-off is danger may u brick ur phone, it's better to leave it
Click to expand...
Click to collapse
Yeah but what if I need it to go back to stock ROM?
Now it's running stock ROM but I still get "TAMPERED" and "UNLOCKED" in the bootloader. I once went into the stock recovery, and once rebooted it reset itself and everything was back factory install -again- ...?
This is the fastboot output right now after flashing Guru Reset M7 2.24.161.1.zip :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...................
(bootloader) imei: ....................
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4185mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
The OTA update to 4.3 even fails once it reboots itself for installation. Something wrong or normal?
EDIT:
I've done "fastboot oem lock" and now it's showing (as expected) "RELOCKED".
BETA911 said:
Yeah but what if I need it to go back to stock ROM?
Now it's running stock ROM but I still get "TAMPERED" and "UNLOCKED" in the bootloader. I once went into the stock recovery, and once rebooted it reset itself and everything was back factory install -again- ...?
This is the fastboot output right now after flashing Guru Reset M7 2.24.161.1.zip :
The OTA update to 4.3 even fails once it reboots itself for installation. Something wrong or normal?
EDIT:
I've done "fastboot oem lock" and now it's showing (as expected) "RELOCKED".
Click to expand...
Click to collapse
Yup it will do, the only way to get rid of those flags tampered and unlocked / relocked is to go s-off, which strange messages are you getting whilst trying to s-off ?
I have a backup of the Vodafone Rom which you can restore through twrp, I'll send a link when I get home in a couple of hours, but it won't get rid of those flags, 401.RUU is the wrong RUU, you need 161.
---------- Post added at 05:43 PM ---------- Previous post was at 05:34 PM ----------
Ps there is no danger going s-off, as long as your flashing the correct software for your phone, the only danger is when you don't know what your doing and try to flash something wrong, it won't warn you, won't error and won't fail to flash, but at reboot it also won't come back on again.
Seanie280672 said:
Yup it will do, the only way to get rid of those flags tampered and unlocked / relocked is to go s-off, which strange messages are you getting whilst trying to s-off ?
I have a backup of the Vodafone Rom which you can restore through twrp, I'll send a link when I get home in a couple of hours, but it won't get rid of those flags, 401.RUU is the wrong RUU, you need 161.
---------- Post added at 05:43 PM ---------- Previous post was at 05:34 PM ----------
Ps there is no danger going s-off, as long as your flashing the correct software for your phone, the only danger is when you don't know what your doing and try to flash something wrong, it won't warn you, won't error and won't fail to flash, but at reboot it also won't come back on again.
Click to expand...
Click to collapse
Well... It said it had a OTA update (like before) to 4.3 and I downloaded it. Reboot, installed, reboot --> bootloop. Now it's "HTC - quietly brilliant", black screen for couple of seconds and reboot to start from HTC logo again...
It's really beginning to piss me of.
But anyway, thanks for the help! A TWRP backup of 161 would be nice, then I'll install that one. The servers at htc1guru are giving me headache, speed is only between 50 and 250 kb/sec! I tried to download more then once but they keep failing on me when they reach bigger sizes and at this speed it's really really annoying to start over again...
Does "M7 CWM Nandroid Backup CID VODAP102 1.29.161.7" work for me? I guess not because it's 1.29 and I already have a higher version so it will give me the touchscreen issues?
To be honest, if this phone finally makes it to the store for repair I hope they can't repair it and let me choose an other phone. I had multiple Android phones the past years (with sometimes more then 2-3 different roms per week) and never had any of these long stretching problems!
The problem your having with the ota sounds like whilst you were installing the guru reset file, you must select to wipe data and also install stock recovery, it will fail without stock recovery.
Well, I did select to install the stock recovery and stock radio in the aroma installer. So I'm out of clues why it's giving me so much problems...
EDIT:
I unlocked the bootloader again and flashed TWRP. I'll try with your Vodafone image once you have time to share it with me. Already big thanks for the help!
here's the backup, you will need to extract the zip file and put the folder named backup into SDCARD/TWRP/BACKUPS/"your device serial number/
https://drive.google.com/uc?export=download&confirm=5940&id=0B_nEcSZr5peRZnpMSHRPRjlzX2c
This will put you on Vodafone 4.4.2 with sense 5.5, however you cant send your phone back until you have got rid of those 2 flags in the bootloader, only way to do that is s-off.
Ignore the folder called recovery, its just TWRP recovery to flash.
After installing, download the stock recovery from the link below and flash it to get OTAs
http://d-h.st/Cyq
Hit the thanks button please.
Just finished installing it! It works so far, although it came up with a new 5.16.161.2 update right now (already has been downloaded...). What should I do?
Currently it's still in TAMPERED and UNLOCKED state with TWRP installed.
BETA911 said:
Just finished installing it! It works so far, although it came up with a new 5.16.161.2 update right now (already has been downloaded...). What should I do?
Currently it's still in TAMPERED and UNLOCKED state with TWRP installed.
Click to expand...
Click to collapse
there is no way out of this without s-off, I don't even understand why you are putting efforts on installing ota/guru reset/nandroid backup at this point.
you are on hboot 1.56 means you should try to s-off using firewater.
then you'll be able to remove the tampered flag and set the bootload back to "LOCKED" (not RE-LOCKED)
follow guide linked in my signature for going back to stock
try to s-off using firewater + arhd 31.6 rom
alray said:
there is no way out of this without s-off, I don't even understand why you are putting efforts on installing ota/guru reset/nandroid backup at this point.
you are on hboot 1.56 means you should try to s-off using firewater.
then you'll be able to remove the tampered flag and set the bootload back to "LOCKED" (not RE-LOCKED)
follow guide linked in my signature for going back to stock
try to s-off using firewater + arhd 31.6 rom
Click to expand...
Click to collapse
I know. I tried to get s-off but none of the given tools succeeded. They all complete their full cycle and eventually after the last reboot I go and check the state and it still says s-on... Then I did read I need a proper ROM so the tools can work (better). I tried to install ARHD like you mention, but after flashing it was stuck in a bootloop again. Clearing the cache and davlik didn't solve it.
At the moment I only need to know if it's safe to update to the new 5.16.161.2 update while it's unlocked... I got TWRP installed but I know I have to flash the stock recovery in order to make the update work. But I'm afraid I'm going to brick it again if I lock it again, as I don't know if it's needed to let the update complete without any errors.

HTC One rooted - Return for Warranty [SOLVED]

Hi,
I have a HTC One that is rooted, and has the problem with the camera (Pink in dark places).
I've have MIUI custom rom, but to return for warranty i need to have the oficila rom.
What do i need to do for restore to the official rom, to turn s-on, and delete all races of a root phone.
I've only changed the software, not the CID.
MY CID is HTC_304.
Thanks for all the help
nurogo said:
Hi,
I have a HTC One that is rooted, and has the problem with the camera (Pink in dark places).
I've have MIUI custom rom, but to return for warranty i need to have the oficila rom.
What do i need to do for restore to the official rom, to turn s-on, and delete all races of a root phone.
I've only changed the software, not the CID.
MY CID is HTC_304.
Thanks for all the help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2541082
please post a "fastboot getvar all" (excluding IMEI and s/n) and i'll check which files you need
nkk71 said:
http://forum.xda-developers.com/showthread.php?t=2541082
please post a "fastboot getvar all" (excluding IMEI and s/n) and i'll check which files you need
Click to expand...
Click to collapse
Thanks,
Here is the data of "fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4232mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Thanks
nurogo said:
Thanks,
Here is the data of "fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4232mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Thanks
Click to expand...
Click to collapse
Anyone, please?
nurogo said:
Anyone, please?
Click to expand...
Click to collapse
use the 1.28.401.7 RUU http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
follow guide linked by nkk71
nurogo said:
Thanks,
Here is the data of "fastboot getvar all":
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) security: on
Thanks
Click to expand...
Click to collapse
I thought you said you were S-OFF, but you are actually S-ON, so bootloader can only show RELOCKED
so two choices:
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
B) RELOCK bootloader (though you may have a hard time with a RELOCKED bootloader for warranty):
fastboot oem lock (to RELOCKED bootloader)
then use the ruu.exe alray linked
nkk71 said:
I thought you said you were S-OFF, but you are actually S-ON, so bootloader can only show RELOCKED
so two choices:
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
B) RELOCK bootloader (though you may have a hard time with a RELOCKED bootloader for warranty):
fastboot oem lock (to RELOCKED bootloader)
then use the ruu.exe alray linked
Click to expand...
Click to collapse
Thanks for all the help.
If I have understood correctly, i will not be able to get s-on after installing the stock rom.
I have to put s-off in order to install the stock rom?
Then to put in s-on, always appears relocked?
There are possibilities to install the stock rom without removing the S-ON?
nurogo said:
Thanks for all the help.
If I have understood correctly, i will not be able to get s-on after installing the stock rom.
I have to put s-off in order to install the stock rom?
Then to put in s-on, always appears relocked?
There are possibilities to install the stock rom without removing the S-ON?
Click to expand...
Click to collapse
no, sorry if I confused you.
for bootloader to say LOCKED (the same way it was when you first got it), you need to get S-OFF.
with S-OFF, you can set it back to LOCKED, and completely "out of the box", (using the ruu.zip process with the file i linked earlier), and can even go back S-ON (as mentioned in my guide) and it will still say LOCKED.
but without S-OFF, you can only get bootloader to show RELOCKED.
I hope that makes it a bit clearer.
nkk71 said:
no, sorry if I confused you.
for bootloader to say LOCKED (the same way it was when you first got it), you need to get S-OFF.
with S-OFF, you can set it back to LOCKED, and completely "out of the box", (using the ruu.zip process with the file i linked earlier), and can even go back S-ON (as mentioned in my guide) and it will still say LOCKED.
but without S-OFF, you can only get bootloader to show RELOCKED.
I hope that makes it a bit clearer.
Click to expand...
Click to collapse
Thanks,
Now i get it.
This is the guide i must follow, right?
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
nurogo said:
Thanks,
Now i get it.
This is the guide i must follow, right?
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
Click to expand...
Click to collapse
yes, first get s-off - should be easy enough considering your current getvar output, you have plenty of options, once you have s-off, you can use ruu.zip method to return to 100% "out of the box"
nkk71 said:
yes, first get s-off - should be easy enough considering your current getvar output, you have plenty of options, once you have s-off, you can use ruu.zip method to return to 100% "out of the box"
Click to expand...
Click to collapse
Tried to put s-off, but it gives the error:
revone failed (error code = 1)
Why this error? What i did wrong?
nurogo said:
Tried to put s-off, but it gives the error:
revone failed (error code = 1)
Why this error? What i did wrong?
Click to expand...
Click to collapse
what date is show in bootloader, if it is before June 2013, then install the ROM mentioned here:
http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and try revone again, otherwise use rumrunner or firewater if revone is giving you a hard time.
nkk71 said:
what date is show in bootloader, if it is before June 2013, then install the ROM mentioned here:
http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and try revone again, otherwise use rumrunner or firewater if revone is giving you a hard time.
Click to expand...
Click to collapse
Done...
Now i have s-off...
Now, what do i have to do is follow step by step the post #4 of your guide, correct?
http://forum.xda-developers.com/showpost.php?p=47794203&postcount=4
nurogo said:
Done...
Now i have s-off...
Now, what do i have to do is follow step by step the post #4 of your guide, correct?
http://forum.xda-developers.com/showpost.php?p=47794203&postcount=4
Click to expand...
Click to collapse
yes correct, follow instructions in the guide, if you already have a custom recovery installed:
1) use adb commands to remove TAMPERED and set LOCKED
2) flash the following ruu.zip: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
3) bootup once to make sure everything is OK, do not take OTA updates
4) if you believe S-ON is necessary for warranty, then go S-ON
after that you can take any OTAs you like,
but why bother since it's going to repair. where they will most like update it anyway
nkk71 said:
yes correct, follow instructions in the guide, if you already have a custom recovery installed:
1) use adb commands to remove TAMPERED and set LOCKED
2) flash the following ruu.zip: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
3) bootup once to make sure everything is OK, do not take OTA updates
4) if you believe S-ON is necessary for warranty, then go S-ON
after that you can take any OTAs you like,
but why bother since it's going to repair. where they will most like update it anyway
Click to expand...
Click to collapse
Thanks for all the help,
After do all that, how do i remove all traces of custom rom's (folders, files, TWRP, etc..)?
is there a way to format the phone, removing all that (like formating a hard drive)?
nurogo said:
Thanks for all the help,
After do all that, how do i remove all traces of custom rom's (folders, files, TWRP, etc..)?
is there a way to format the phone, removing all that (like formating a hard drive)?
Click to expand...
Click to collapse
The ruu will take care of that, it will wipe everything off your phone, including anything on the virtual sdcard
Sent from my HTC One using Tapatalk
Ok.. Here's the situation
Removed TAMPERED and now it says LOCKED
But when i try to copy the ruu.zip it says:
load_file: could not allocate 1034027008 bytes
error: cannot load "ruu.zip": Not enough space..
How can i solve this?
I have 20GB free of space...
nurogo said:
Ok.. Here's the situation
Removed TAMPERED and now it says LOCKED
But when i try to copy the ruu.zip it says:
load_file: could not allocate 1034027008 bytes
error: cannot load "ruu.zip": Not enough space..
How can i solve this?
I have 20GB free of space...
Click to expand...
Click to collapse
Cannot load = MyFileNameIsWrong
Sent from my HTC One using Tapatalk
nkk71 said:
Cannot load = MyFileNameIsWrong
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Check it, but it stays the same..
Look at the image
nurogo said:
Check it, but it stays the same..
Look at the image
Click to expand...
Click to collapse
type dir in the command window
you probably see it's names RUU.zip.zip

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

Hi guys, hope you can help me out...
I just rooted my HTC One (unlock bootloader and install TWRP recovery), WITHOUT installing any custom ROM (i just kept the factory OS, because i couldn't S-Off the phone in order to install the google play edition). The OS i had (and still have) is stock Android 4.4.3 with Sense 6.
The problem is that i need to lock the phone back (in order to benefit from the warranty - technical touchscreen problem).
I tried using Revone to lock the phone back, but i get an error: "Failed to open framebuffer device". I understand that revone doesn't work with hboot 1.57.
Could you please help me with the relocking/unrooting the phone (at least give me a link to a guide that is working for my phone configuration - hboot 1.57) ? And also could you tell me if i need a RUU, or i can just wipe/reinstall the current OS (which i never changed in the first place) ? And if i need a RUU, how can i find the one that was initially installed on the phone ?
Oh, and one more thing: at first, when my phone started, i had a Vodafone screen showing up, and some crappy apps preinstalled. After i rooted an installed twrp recovery, i don't get that vodafone screen anymore, an the crappy apps weren't preinstalled anymore.
Cheers and thanks in advance !
andreih8017 said:
Hi guys, hope you can help me out...
I just rooted my HTC One (unlock bootloader and install TWRP recovery), WITHOUT installing any custom ROM (i just kept the factory OS, because i couldn't S-Off the phone in order to install the google play edition). The OS i had (and still have) is stock Android 4.4.3 with Sense 6.
The problem is that i need to lock the phone back (in order to benefit from the warranty - technical touchscreen problem).
I tried using Revone to lock the phone back, but i get an error: "Failed to open framebuffer device". I understand that revone doesn't work with hboot 1.57.
Could you please help me with the relocking/unrooting the phone (at least give me a link to a guide that is working for my phone configuration - hboot 1.57) ? And also could you tell me if i need a RUU, or i can just wipe/reinstall the current OS (which i never changed in the first place) ? And if i need a RUU, how can i find the one that was initially installed on the phone ?
Oh, and one more thing: at first, when my phone started, i had a Vodafone screen showing up, and some crappy apps preinstalled. After i rooted an installed twrp recovery, i don't get that vodafone screen anymore, an the crappy apps weren't preinstalled anymore.
Cheers and thanks in advance !
Click to expand...
Click to collapse
Ok well first off you need s-off to set your bootloader to ***LOCKED*** and to get back to 100% stock. As your on Hboot 1.57 the only way to gain s-off is with Sunshine App. Which will cost $25 to use.
The stock Rom on your Device won't be a complete stock Rom either. When you unlock the bootloader the device is wiped along with some preload data (crappy apps) which is critical if you want the device back to stock. Or to be able to accept OTA updates. If the device is Vodafone I'm not sure there is an RUU but you should be able to get a full stock Rom from somewhere. Please post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting. And we can see what is available for you. But if you want to go 100% stock to reinstate your warranty you will need s-off first :good:
Danny201281 said:
Ok well first off you need s-off to set your bootloader to ***LOCKED*** and to get back to 100% stock. As your on Hboot 1.57 the only way to gain s-off is with Sunshine App. Which will cost $25 to use.
The stock Rom on your Device won't be a complete stock Rom either. When you unlock the bootloader the device is wiped along with some preload data (crappy apps) which is critical if you want the device back to stock. Or to be able to accept OTA updates. If the device is Vodafone I'm not sure there is an RUU but you should be able to get a full stock Rom from somewhere. Please post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting. And we can see what is available for you. But if you want to go 100% stock to reinstate your warranty you will need s-off first :good:
Click to expand...
Click to collapse
Hey, thanx for the quick answer !
This is the result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
What do you mean by "Or to be able to accept OTA updates" ?? At his moment i won't be able to receive any updates anymore ? :crying:
Also, what about Firewater for S-OFF ?
andreih8017 said:
Hey, thanx for the quick answer !
This is the result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
What do you mean by "Or to be able to accept OTA updates" ?? At his moment i won't be able to receive any updates anymore ? :crying:
Click to expand...
Click to collapse
Unlocking the bootloader wipes /data partition to prevent unauthorized access to your data. Problem is that HTC packed some of their stock apps in /data/preload which mean you don't have these apps anymore after unlocking the bootloader. When installing an ota update, there is a script verifying the integrity of each files to be patched, inluding apps normally present in /data/preload. After the script will find out that these apps are missing, the ota update installation will abort. So no your phone can't install ota update anymore unless you restore your phone back to stock (which can be done with s-off btw).
Also, what about Firewater for S-OFF ?
Click to expand...
Click to collapse
Its discontinued. Firewater was using online resources no more available to do its magic.
From what I see from your "getvar all" you have the pretty standard version of the M7. Follow nkk71's guide linked in my signature. You want to follow the procedure using the 1.28.401.7 ruu.zip
@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,
andreih8017 said:
@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,
Click to expand...
Click to collapse
To safely go back to s-on without risking tampered you should have done it before installing the OTA updates as explained in @nkk71 guide.
So now you should downgrade with the ruu again then set s-on then install OTA updates to avoid the tampered flag returning. :good:
andreih8017 said:
@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,
Click to expand...
Click to collapse
how far did you go with the OTA's? as long as it's pre 7.xx (ie Lollipop), sunshine will still work, in case you the tampered sign back, you can use sunshine again to s-off, and redo it (the guide)
but as danny said, i (personally) only recommend it on 1.xx or 2.xx firmware.... i don't know the reason for tampered [sometimes/often] reappearing so i dont know what's involved or what triggers it
@Danny201281
@nkk71
i took a leap of faith and eneter the "fastboot oem writesecureflag 3" command. It worked like a charm. Afterwards i rebooted the bootloader 3 times and no "tampered" sign, but S-ON. I also rebooted the phone once and still no "tampered" sign, but S-ON. Guess it worked, right ?
As for the OTAs, i went until the last one available for HTC One - 6.09.401.11.
Thanks guys !
andreih8017 said:
@Danny201281
@nkk71
i took a leap of faith and eneter the "fastboot oem writesecureflag 3" command. It worked like a charm. Afterwards i rebooted the bootloader 3 times and no "tampered" sign, but S-ON. I also rebooted the phone once and still no "tampered" sign, but S-ON. Guess it worked, right ?
As for the OTAs, i went until the last one available for HTC One - 6.09.401.11.
Thanks guys !
Click to expand...
Click to collapse
You need to reboot the ROM three times at least, not the bootloader
Sent from my HTC One_M8 using Tapatalk
@nkk71
I did that also. Still working fine, "locked" and S-ON
Thanx,
andreih8017 said:
@nkk71
I did that also. Still working fine, "locked" and S-ON
Thanx,
Click to expand...
Click to collapse
cool, good to hear :good: :good:

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

Hi guys!
I've been trying to get my dear One M7 alive now for 4-5 evenings. Really thought it was bricked for good, but finally made some progress. Here's what happened:
S-OFF, rooted since always but on stock/OTA from HTC. Been updating through OTAs just flashing back stock recovery before update and then switching back. I've been using CWM. I was already on the Lollipop 5.0.2 with Sense 6.0 (sofware revision 7.19.401.2) but received another minor OTA couple of weeks ago. Didn't make note of the new revision, nor the reason for the update but just followed my usual steps. Everything seemed to go as usual, but once booting back up after the update the phone got stock on the boot animation (the htc one w/beats audio just after the sound).
Immediately tried a restore from a backup I have, but continued in the same situation. Tried several/different wipes (even the data partition in the end), but no luck. Tried the best I could to search for info, but all I could find was what I'd already done. Tried to download some RUU's but the files seems corrupted and I cannot get it working. I tried to switch to TWRP, taking a new backup (of my restored, but still not working CWM-backup). Same situation. Then I tried to flash a Cyanogenmod version, and was close to giving up when it didn't work as well. Luckily I tried a couple of times more (perhaps after throwing the phone in the wall a few times) and just out of nowhere it suddenly booted and seems to be working normally. Full of hope I tried a restore again, but back to boot animation. Tried to download a clean stock install file I found on XDA with the same version as mine, but just get stuck again. Once I restore the Cyanogenmod backup, it boots perfectly.
Perhaps I am missing something obvious, but I've been doing these things for many years know (starting with the Desire @ nikez), and this just seems odd. I could seriously need some help to get it back working again as I like the stock Sense 6.0 with Lollipop.
For info some details (btw; I verified it against the data I noted just after my original Lollipop OTA early this year, and it is still identical, so i don't see any vitals have changed):
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: **removed**
(bootloader) imei: **removed**
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4081mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks in advance for any good advice!!
tormagj said:
I was already on the Lollipop 5.0.2 with Sense 6.0 (sofware revision 7.19.401.2) but received another minor OTA couple of weeks ago. Didn't make note of the new revision
Click to expand...
Click to collapse
Its 7.19.401.22
nor the reason for the update
Click to expand...
Click to collapse
bug fixes
but just followed my usual steps.
Click to expand...
Click to collapse
Won't work for this ota, you must be 100% stock.
Thanks in advance for any good advice!![
Click to expand...
Click to collapse
flash the 7.19.401.22 ruu, it will update and fix your phone.
http://forum.xda-developers.com/showpost.php?p=59436794&postcount=2
alray said:
Its 7.19.401.22
flash the 7.19.401.22 ruu, it will update and fix your phone.
http://forum.xda-developers.com/showpost.php?p=59436794&postcount=2
Click to expand...
Click to collapse
Thanks alot alray, I'll test it and report back if I manage to fix my beloved phone. I guess I didn't see that "second generation" in post two
unbricked htc one m7
tormagj said:
Hi guys!
I've been trying to get my dear One M7 alive now for 4-5 evenings. Really thought it was bricked for good, but finally made some progress. Here's what happened:
S-OFF, rooted since always but on stock/OTA from HTC. Been updating through OTAs just flashing back stock recovery before update and then switching back. I've been using CWM. I was already on the Lollipop 5.0.2 with Sense 6.0 (sofware revision 7.19.401.2) but received another minor OTA couple of weeks ago. Didn't make note of the new revision, nor the reason for the update but just followed my usual steps. Everything seemed to go as usual, but once booting back up after the update the phone got stock on the boot animation (the htc one w/beats audio just after the sound).
Immediately tried a restore from a backup I have, but continued in the same situation. Tried several/different wipes (even the data partition in the end), but no luck. Tried the best I could to search for info, but all I could find was what I'd already done. Tried to download some RUU's but the files seems corrupted and I cannot get it working. I tried to switch to TWRP, taking a new backup (of my restored, but still not working CWM-backup). Same situation. Then I tried to flash a Cyanogenmod version, and was close to giving up when it didn't work as well. Luckily I tried a couple of times more (perhaps after throwing the phone in the wall a few times) and just out of nowhere it suddenly booted and seems to be working normally. Full of hope I tried a restore again, but back to boot animation. Tried to download a clean stock install file I found on XDA with the same version as mine, but just get stuck again. Once I restore the Cyanogenmod backup, it boots perfectly.
Perhaps I am missing something obvious, but I've been doing these things for many years know (starting with the Desire @ nikez), and this just seems odd. I could seriously need some help to get it back working again as I like the stock Sense 6.0 with Lollipop.
For info some details (btw; I verified it against the data I noted just after my original Lollipop OTA early this year, and it is still identical, so i don't see any vitals have changed):
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: **removed**
(bootloader) imei: **removed**
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4081mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
**************************************************************************************************
hello sir,
I have htc one m7 sprint manufactured in new zealand.The problem started when I by mistake deleted all the partitions like delvin cache,system,internal
storage,etc in the factory reset option of the bootloader.My phone has unlocked bootloader and latest twrp installed before the problem occurred and android
version 4.2 installed which i think has been deleted as it says when rebooting from the bootloader and it rebooted normally just stucks at hTC logo.
I have installed fastboot,adb(not working properly) by sdk tools on windows 7 32 bit pc and also htc sync manager and latest java.
I request you to reply me as soon as possible as i have just lost my all the patience doing all the methods suggested on the like fastboot,etc and
typing the commands.You are my last hope,please help me.
Htc one bootloader details are:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0315
OpenDSP-v26.120.274.020
eMMC-boot
May 8 2013,16:30:08:1
I have only basic knowledge of android tools and computer.
Thanks a lot for your time and i am waiting for your reply.
Click to expand...
Click to collapse
tormagj said:
Thanks alot alray, I'll test it and report back if I manage to fix my beloved phone. I guess I didn't see that "second generation" in post two
Click to expand...
Click to collapse
@alray - that freaking worked like a charm! Thanks a lot, a donation is on it's way, really thought my beloved phone was gone.
Installed the RUU version 7.19.401.22 as indicated, and that did the trick. I got an error message about HBOOT while flashing it, tried it twice since I saw it mentioned in several threads but the message continued. However, the phone booted normally afterwards so I couldn't care less right now
Code:
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device XXXX.
Also tried desperately to restore the data partition from my cwm backup, but then the phone wouldn't boot again. Last resort now will be to manually restore some of the apps through Titanium from my cwm - but what the heck, lost data is better than lost phone.
Although a minor update, seems like HTC did some serious changes since a lot of the normal stuff doesn't work. Any idea of what??
Anyways, thanks again - really appreciated!
rakeshrinawa said:
hello sir,
I have htc one m7 sprint manufactured in new zealand.The problem started when I by mistake deleted all the partitions like delvin cache,system,internal
storage,etc in the factory reset option of the bootloader.My phone has unlocked bootloader and latest twrp installed before the problem occurred and android
version 4.2 installed which i think has been deleted as it says when rebooting from the bootloader and it rebooted normally just stucks at hTC logo.
I have installed fastboot,adb(not working properly) by sdk tools on windows 7 32 bit pc and also htc sync manager and latest java.
I request you to reply me as soon as possible as i have just lost my all the patience doing all the methods suggested on the like fastboot,etc and
typing the commands.You are my last hope,please help me.
Htc one bootloader details are:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0315
OpenDSP-v26.120.274.020
eMMC-boot
May 8 2013,16:30:08:1
I have only basic knowledge of android tools and computer.
Thanks a lot for your time and i am waiting for your reply.
Click to expand...
Click to collapse
Hi @rakeshrinawa,
I should probably leave it to the pro's to help you out, but I would suggest the following (sure somebody will correct me if I'm on thin ice here):
- Boot into fastboot, open a command prompt and write "fastboot getvar all". Then you'll see the same variables that I posted above, amongst other the version of your software, your CID and some other information that might be useful for the guys helping.
- Look at the selection posted by @alray here http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 (either first or second post).
- You need to find the RUU that fits your phone (correct CID and version), and keep in mind the note in the top:
When you update you must go one step at a time. For example if you are on 6.xx.xxx.xx then you can flash 7.xx.xxx.xx . But if you are on 5.xx.xxx.xx then you cannot flash the 7.xx.xxx.xx you must first flash a 6..xx.xxx.xx.
Click to expand...
Click to collapse
- The trick is to find the right file, but I'm not the right guy to tell you which one. Once you have it, just follow the "How to flash" instructions step by step and hopefully you'll have an almost new phone again just like I had.
- I see your S-ON, so take note of the instructions saying you need to relock the bootloader (item 4 in How to flash). Or perhaps you could just as well S-OFF it ​
I am sure it's possible to solve your issue, keep on trying! Good luck!
rakeshrinawa said:
hello sir,
I have htc one m7 sprint manufactured in new zealand.The problem started when I by mistake deleted all the partitions like delvin cache,system,internal
storage,etc in the factory reset option of the bootloader.My phone has unlocked bootloader and latest twrp installed before the problem occurred and android
version 4.2 installed which i think has been deleted as it says when rebooting from the bootloader and it rebooted normally just stucks at hTC logo.
I have installed fastboot,adb(not working properly) by sdk tools on windows 7 32 bit pc and also htc sync manager and latest java.
I request you to reply me as soon as possible as i have just lost my all the patience doing all the methods suggested on the like fastboot,etc and
typing the commands.You are my last hope,please help me.
Htc one bootloader details are:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0315
OpenDSP-v26.120.274.020
eMMC-boot
May 8 2013,16:30:08:1
I have only basic knowledge of android tools and computer.
Thanks a lot for your time and i am waiting for your reply.
Click to expand...
Click to collapse
Relock your bootloader
Code:
fastboot oem lock
and flash the old sprint ruu:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
fastboot reboot
Then you should update your phone to latest version before unlocking the bootloader, flashing a custom recovery/rom (if you are planning to)
thanks for your reply dear
@alray
Actually this is the only info my bootloader is showing as I have formatted data in the factory reset option.The model no of the phone is PN072(SPRINT) and before this problem,ANdroid 4.2 was installed and now i have installed TWRP 2.6.3.0 and again formatted data and now adb sideload is not working,kindly suggest me the correct softwares which can make my htc one m7 work and do my normal things and can u send me step by step list of softwares to be installed like twrp and adb on my pc as i have 32bit windows 7 on my pc.
Thanks a lot for your reply dear friend and you guys are just amazingly helpful.Keep it on.
---------- Post added at 02:20 AM ---------- Previous post was at 02:07 AM ----------
[/COLOR @alray
I think i have the wrong version of twrp on my phone so adb sideload is not working and i just download your files and simply flash them and will they make my phone work even when i have performed format data and by factory reset in the bootloader?
rakeshrinawa said:
@alray
Actually this is the only info my bootloader is showing as I have formatted data in the factory reset option.The model no of the phone is PN072(SPRINT) and before this problem,ANdroid 4.2 was installed and now i have installed TWRP 2.6.3.0 and again formatted data and now adb sideload is not working,kindly suggest me the correct softwares which can make my htc one m7 work and do my normal things and can u send me step by step list of softwares to be installed like twrp and adb on my pc as i have 32bit windows 7 on my pc.
Thanks a lot for your reply dear friend and you guys are just amazingly helpful.Keep it on.
Click to expand...
Click to collapse
Step you need to do posted above
RUU also posted above
you'll also need adb / fastboot either by downloading the android sdk (SDK Tools only) or minimal adb and fastboot
Save the ruu in the same folder you have installed minimal adb and fastboot or if installed the android sdk, make sure the ruu is in \Android SDK Tools\platform-tools.
Start a command prompt: Start menu --> program --> minimal adb and fastboot --> minimal adb and fastboot.exe or if using the sdk, go to \Android SDK Tools\platform-tools hold shift and right click in the folder and select "start a cmd prompt here".
Reboot your phone in bootloader / fastboot usb mode (make sure "fastboot usb" is shown in red)
then type:
Code:
fastboot oem lock
fastboot reboot-bootloader
This will relock your bootloader, required to flash the ruu
Code:
fastboot oem rebootRUU
once rebooted in ruu mode (black screnn with silver htc logo):
Code:
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
First flash will report "flush image again immediately, so do the same command again:
Code:
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
Wait for the ruu to flash then when you see sucessful message:
Code:
fastboot reboot
HI
@alray
I have HTC ONE M7 sprint variant with model no.PN072 which supports both gsm and cdma and I Was not able to use wcdma or 3g mode when using Android version 4.2.
So keeping all these things,and spending 10 hours in downloaading your files,will they work on my htc and won't create future problems like in google updates etc?
---------- Post added at 05:53 AM ---------- Previous post was at 05:14 AM ----------
[/COLOR @alray
I am sorry to say that before I read your reply,I was actually following instructions from
http://forum.xda-developers.com/showthread.php?t=2503646
and so I have flashed the firmware 5.03.651.3 s-on which is of 39886 bytes and now my new details of bootloader are:
***TAMPERED***
***RELOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v26.120.274.0202
OS-5.03.651.3
eMMC-boot 2048MB
May 15 2014,16:31:22.1
and my fastboot getvar all details are:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 1.01.20.0515
version-cpld: None
version-microp: None
version-main: 5.03.651.3
version-misc: PVT SHIP S-ON
serialno: ***REMOVED***
imei: ***REMOVED***
meid: ***REMOVED***
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4262mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
AND when I downloaded the odex file mentioned by him in the 8c step,I got the error of
remote 12:signature verify failed
and tried then,but got the same error again.
My bootloader is still relocked.
now tell me what should I do?
Hope you bear my stubbornness and Reply.....
Thanks
rakeshrinawa said:
@alray
I have HTC ONE M7 sprint variant with model no.PN072 which supports both gsm and cdma and I Was not able to use wcdma or 3g mode when using Android version 4.2.
So keeping all these things,and spending 10 hours in downloaading your files,will they work on my htc and won't create future problems like in google updates etc?
---------- Post added at 05:53 AM ---------- Previous post was at 05:14 AM ----------
[/COLOR @alray
I am sorry to say that before I read your reply,I was actually following instructions from
http://forum.xda-developers.com/showthread.php?t=2503646
and so I have flashed the firmware 5.03.651.3 s-on which is of 39886 bytes and now my new details of bootloader are:
***TAMPERED***
***RELOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v26.120.274.0202
OS-5.03.651.3
eMMC-boot 2048MB
May 15 2014,16:31:22.1
and my fastboot getvar all details are:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 1.01.20.0515
version-cpld: None
version-microp: None
version-main: 5.03.651.3
version-misc: PVT SHIP S-ON
serialno: ***REMOVED***
imei: ***REMOVED***
meid: ***REMOVED***
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4262mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
AND when I downloaded the odex file mentioned by him in the 8c step,I got the error of
remote 12:signature verify failed
and tried then,but got the same error again.
My bootloader is still relocked.
now tell me what should I do?
Hope you bear my stubbornness and Reply.....
Thanks
Click to expand...
Click to collapse
flash the 5.03.651.3 ruu posted in that thread.
hi
alray said:
flash the 5.03.651.3 ruu posted in that thread.
Click to expand...
Click to collapse
I flashed it with fastboot and it says signature verify failed,tried again and got the same message.
What should I do now,Please help me,I am totally exhausted.
rakeshrinawa said:
I flashed it with fastboot and it says signature verify failed,tried again and got the same message.
Click to expand...
Click to collapse
Its says signature verify fail because you are trying to flash a rom (stock odexed) using fastboot, you must flash this rom using a custom recovery which will require to unlock the bootloader again so the simplest is to keep your bootloader relocked and flash the RUU
hello
alray said:
Its says signature verify fail because you are trying to flash a rom (stock odexed) using fastboot, you must flash this rom using a custom recovery which will require to unlock the bootloader again so the simplest is to keep your bootloader relocked and flash the RUU
Click to expand...
Click to collapse
****
ok then can you send me the link of ruu file i have to flash as adb is not working in my phone and I can unlock my bootloader if you have a solution after that.
waiting for your reply.
rakeshrinawa said:
****
ok then can you send me the link of ruu file i have to flash
Click to expand...
Click to collapse
lol I think we have some communication issues here :laugh:. The RUU is in the same thread you linked me at post #10. All sprint RUU are listed at the beginning of that thread (in the first few lines of the OP), you need the 5.03.651.3 RUU, download it and lauch it (double click, its an .exe file). Make sure your phone is in bootloader when you launch the ruu.

Help - Bricked HTC One (M7) - No Recovery - No Operating System - Only Fastboot

Close this thread mod.
I will move to my old thread: http://forum.xda-developers.com/htc-one/help/planning-to-buy-bricked-htc-one-m7-t3376521
MihailMojsoski said:
So, my HTC One M7 is bricked.
This is all the information:
I can get ONLY into fastboot and hboot.
The is is all the data from the phone when i go to hboot:
*** RELOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.18.161.51
eMMC-boot 2048MB
Nov 18 2015, 13:59:56.22095
Recovery is not working,
also when i start the phone it boots to HBOOT or FASTBOOT
Click to expand...
Click to collapse
And what was done to the phone before it got bricked?
alray said:
And what was done to the phone before it got bricked?
Click to expand...
Click to collapse
Don't know.
I got this phone from a friend.
Edit: Also when i try to flash recovery i get error:
FAILED (remote: signature verify fail)
MihailMojsoski said:
Don't know.
I got this phone from a friend.
Click to expand...
Click to collapse
So this is the broken phone you was planning to buy like you have explained in your other thread, why creating a new thread for this? You already have one with post #2 reserved by yourself for this purpose....
"your friend" probably relocked the bootloader with a custom recovery/rom installed. The phone can't boot custom software when the bootloader is locked. You'll have to unlock the bootloader or flash a ruu.
If a custom recovery was installed you'll probably not be able to unlock it since the unluck process requires the stock recovery installed on the phone.
This phone is s-on so you can only flash ruu same or newer version as the current version installed and unfortunately there is no ruu for this version. There's a way to bypass this but you'll need a custom working custom recovery......
Let's try to unlock your bootloader first using htcdev.com then report in your original thread and close this one.
Sent from my HTC One using XDA Labs
Edit: Also when i try to flash recovery i get error:
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
The bootloader is locked, you can't flash the recovery partition on a locked bootloader.
alray said:
So this is the broken phone you was planning to buy like you have explained in your other thread, why creating a new thread for this? You already have one with post #2 reserved by yourself for this purpose....
"your friend" probably relocked the bootloader with a custom recovery/rom installed. The phone can't boot custom software when the bootloader is locked. You'll have to unlock the bootloader or flash a ruu.
If a custom recovery was installed you'll probably not be able to unlock it since the unluck process requires the stock recovery installed on the phone.
This phone is s-on so you can only flash ruu same or newer version as the current version installed and unfortunately there is no ruu for this version. There's a way to bypass this but you'll need a custom working custom recovery......
Let's try to unlock your bootloader first using htcdev.com then report in your original thread and close this one.
Sent from my HTC One using XDA Labs
The bootloader is locked, you can't flash the recovery partition on a locked bootloader.
Click to expand...
Click to collapse
Hey, so i tried finding the right RUU but i failed.
Also this is my getvar:
(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.18.161.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT**********
(bootloader) imei: ***HIDE***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-7661b1d7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Edit: Also would this work: https://www.androidfilehost.com/?fid=24052804347763901
Edit2: I tried unlocking the bootloader, but when i selected "YES", it got stucked on a screen with 3 androids and when i pressed the power button it vibrated. I will try again but i will give it some time, and i will tell you if it will work.
Alray's right, the problem seems quite difficult to walk around. Maybe you can send the phone to http://www.fonefunshop.co.uk I'm almost certain they'll figure out a way to fix it.
You can try to unlock the bootloader.. That ruu is unlikely to get you out of this mess cause it seems you're on a newer firmware version. But again, it won't hurt to try.. especially at this stage.
monrokhoury said:
Alray's right, the problem seems quite difficult to walk around. Maybe you can send the phone to http://www.fonefunshop.co.uk I'm almost certain they'll figure out a way to fix it.
You can try to unlock the bootloader.. That ruu is unlikely to get you out of this mess cause it seems you're on a newer firmware version. But again, it won't hurt to try.. especially at this stage.
Click to expand...
Click to collapse
I unlocked the phone, but i fail to install a recovery.
Code:
C:\Users\User\Desktop>fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9594 KB)...
OKAY [ 1.227s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.338s
monrokhoury said:
Alray's right, the problem seems quite difficult to walk around. Maybe you can send the phone to http://www.fonefunshop.co.uk I'm almost certain they'll figure out a way to fix it.
You can try to unlock the bootloader.. That ruu is unlikely to get you out of this mess cause it seems you're on a newer firmware version. But again, it won't hurt to try.. especially at this stage.
Click to expand...
Click to collapse
Also i live in Macedonia, so i can't send them the phone.
I can only fix it manually.

Categories

Resources