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
Related
Solved thanks to @alray
Ok so the other day I tried going to Android 4.4 Google edition with a rom but s-off never worked. Without noticing s-on I tried installing the rom which soft bricked the phone (Starts up goes past HTC logo and flashes google logo then the screen goes blue).
I made the obvious mistake of not making a back up so I'm stuck. I have access to Bootloader & Recovery. I've tried installing RUU files but the ones I've tried so far get stuck at 7% 'Checking Header'. I'm just looking to get back to a working phone... Any help is appreciated.
If I'm missing any info you need let me know, I'm new to this...
Thanks.
More info:
I'm in Ireland, Europe.
The phone works with different sim cards (So I assume it must be unlocked).
RRU's I've tried:
RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
If you can give me more to try/ that are meant for my phone I would appreciate it.
I've given the bootloader menu as an attachment.
The fastboot getvar all is as follows (this is after I installed the new rom, I don't know what the original ones are):
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: (not sure if you need this)
(bootloader) imei: (not showing this to you)
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4262mV
(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!
Click to expand...
Click to collapse
CorcoranM96 said:
Ok so the other day I tried going to Android 4.4 Google edition with a rom but s-off never worked. Without noticing s-on I tried installing the rom which soft bricked the phone (Starts up goes past HTC logo and flashes google logo then the screen goes blue).
I made the obvious mistake of not making a back up so I'm stuck. I have access to Bootloader & Recovery. I've tried installing RUU files but the ones I've tried so far get stuck at 7% 'Checking Header'. I'm just looking to get back to a working phone... Any help is appreciated.
If I'm missing any info you need let me know, I'm new to this...
Thanks.
More info:
I'm in Ireland, Europe.
The phone works with different sim cards (So I assume it must be unlocked).
RRU's I've tried:
RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
If you can give me more to try/ that are meant for my phone I would appreciate it.
I've given the bootloader menu as an attachment.
The fastboot getvar all is as follows (this is after I installed the new rom, I don't know what the original ones are):
Click to expand...
Click to collapse
the ruu failed because you need s-off to use them with hboot 1.55 (require hboot downgrade to 1.44 which require s-off)
so now your best option is tu install a guru reset. Use this file
boot your phone into your custom recovery and push the file I linked above to your sd card. then install the .zip file with your custom recovery and follow instruction from the graphical user interface (aroma installer)
video tutorial here
so now your best option is tu install a guru reset.
boot your phone into your custom recovery and push the file I linked above to your sd card. then install the .zip file with your custom recovery and follow instruction from the graphical user interface (aroma installer)
Thanks @alray for the reply! I'm trying that now, I'll let you know how I get on!
@alray
This may sound silly but, do you know if I need to buy the 'On the go usb cable' like in his video? I dont think I do since he was running a 1.29.xxx (doesnt support touch screen) but I'll be running a 3.62.401.1 (he doesnt specify if I need one or not...) Just want to make sure before doing anything.
Thanks.
CorcoranM96 said:
@alray
This may sound silly but, do you know if I need to buy the 'On the go usb cable' like in his video? I dont think I do since he was running a 1.29.xxx (doesnt support touch screen) but I'll be running a 3.62.401.1 (he doesnt specify if I need one or not...) Just want to make sure before doing anything.
Thanks.
Click to expand...
Click to collapse
Move the .zip file to your fastboot/adb folder. boot your phone in recovery. then:
Code:
adb push name_of_file.zip /sdcard/
then in recovery select ''install'' and slect the zip you pushed
no need to use otg cable
@alray I'm getting 'Device not found' When I try to do anything with ADB... Any Idea of the problem?
CorcoranM96 said:
@alray I'm getting 'Device not found' When I try to do anything with ADB... Any Idea of the problem?
Click to expand...
Click to collapse
what recovery are you using? You are doing adb command in recovery right?
Solved!
alray said:
what recovery are you using? You are doing adb command in recovery right?
Click to expand...
Click to collapse
Fixed it, I just changed computer... My phone works perfectly and is returned to stock! :good:
Thanks a million @alray!
hi guys, I am stuck in boot mode after removing cyanogen mod, I have tried installing the RUU.exe but it will not complete - I think the reason for this is that S-ON. I can't seem to find a solution to achieve S-off anywhere without having to be into the phones OS.
I have tried pushing the rom to my phone but I just keep getting 'no device found'
The usb recognises the phone but the adb commands do not work at all
any further info suggested would be massively appreciated.
edit:
got adb commands working by following this guide
(not allowed to post links yet)
progress so far:
I have managed to sideload a relevant ROM but it has now been saying 'installing update' for quite a while and I am not sure whether to touch it
on another note, the image verification thing on this forum is very, very annoying.
ok so I sideloaded a ROM and it aborted the installation, totally at a loss now
grantymc said:
ok so I sideloaded a ROM and it aborted the installation, totally at a loss now
Click to expand...
Click to collapse
Boot your phone in bootloader mode and type fastboot getvar all. copy/paste the output here except IMEI and SERIALNO. Also, I need to know what recovery you are using and its version and what custom rom and its version you are trying to flash.
alray said:
Boot your phone in bootloader mode and type fastboot getvar all. copy/paste the output here except IMEI and SERIALNO. Also, I need to know what recovery you are using and its version and what custom rom and its version you are trying to flash.
Click to expand...
Click to collapse
I am using clockwork recovery, I was trying to flash a stock RUU zip - I could not find one to match my exact baseband version so I tried
"RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip" but just got the message 'installation aborted' after sideloading
forgive me I can't paste links yet
I also tried the latest version of CM as this is what I was trying to revert back from this installed but just said 'installing' for nearly an hour then after I rebooted it left with a constant CM loading screen
I have a feeling I need S-OFF but can't seem to achieve through any of the methods described
(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.63.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA385W914634
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b0a25cb2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
grantymc said:
I am using clockwork recovery, I was trying to flash a stock RUU zip - I could not find one to match my exact baseband version so I tried
"RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip" but just got the message 'installation aborted' after sideloading
Click to expand...
Click to collapse
Ruu.zip are not installed with a custom recovery/sideloaded!! It must be flashed via fastboot ruu mode. Anyway this ruu is not for your phone, its a .401 base and you need a .61 base ruu of same version or higher than 3.63.61.1 but afaik there is no ruu for your phone... BTW the 1.20.401.1 ruu is a pre-release version without OTA updates so it a bad idea to use it.
grantymc said:
forgive me I can't paste links yet
I also tried the latest version of CM as this is what I was trying to revert back from this installed but just said 'installing' for nearly an hour then after I rebooted it left with a constant CM loading screen
Click to expand...
Click to collapse
Either because of a bad rom/download or because your recovery version is outdated. Flash twrp 2.6.3.3 or 2.6.3.4. Also clear cache every time your flash something and md5 check your roms/recovery before you flash them.
grantymc said:
I have a feeling I need S-OFF but can't seem to achieve through any of the methods described
Click to expand...
Click to collapse
S-OFF is not require to flash a custom rom like CM only if you want to convert your phone using a ruu not intended for your version.
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.
Hi
Apologies in advance if this is an obvious question; I have looked through the forum but cant find a concise answer to my queries. I am coming from a HOX and my friend gave me his broken screened UK O2 branded LTE M7 as such not yet familiar with the M7. I have replaced the broken screen and fitted a new battery which was a great deal more awkward than working on the HOX!
The CId is 02_001 running HBOOT 1.61 and S-ON, I have unlocked the bootloader via HTC Dev however this is where I become unsure as to what avenues I can explore for flashing.
I'm assuming as I've now unlocked the bootloader I can flash a TWRP recovery but as I'm S-ON I can only flash unencrypted roms and as such cannot flash say the HTC Europe unbranded RUU? I want to try and stay on a stock type unbranded Sense ROM if possible rather than flashing a custom or CM based ROM until I am more familiar with the M7.
There is a plethora of info and hence I'm finding it difficult to get to grips with what ROMs would be suitable.
alangordon73 said:
Hi
Apologies in advance if this is an obvious question; I have looked through the forum but cant find a concise answer to my queries. I am coming from a HOX and my friend gave me his broken screened UK O2 branded LTE M7 as such not yet familiar with the M7. I have replaced the broken screen and fitted a new battery which was a great deal more awkward than working on the HOX!
The CId is 02_001 running HBOOT 1.61 and S-ON, I have unlocked the bootloader via HTC Dev however this is where I become unsure as to what avenues I can explore for flashing.
I'm assuming as I've now unlocked the bootloader I can flash a TWRP recovery but as I'm S-ON I can only flash unencrypted roms and as such cannot flash say the HTC Europe unbranded RUU? I want to try and stay on a stock type unbranded Sense ROM if possible rather than flashing a custom or CM based ROM until I am more familiar with the M7.
There is a plethora of info and hence I'm finding it difficult to get to grips with what ROMs would be suitable.
Click to expand...
Click to collapse
With a S-ON phone you can only flash Signed RUU that are for your phone CID, MID and version-main. You also can't flash older RUU than your version-main.
With S-OFF, you can flash Signed/Un-signed RUU of your choice (you'll have to change your CID and maybe your MID)
Flashing a stock rom (not talking about a RUU here, but a stockish unbranded custom rom) doesn't requires S-OFF, simply flash using custom recovery. ARHD 93 is a good starting point imo.
Many thanks for the reply - I am aware that the question is slightly noobish and as such I am appreciative. I'll install the suggested ROM and work from there.
Again many thanks
Unable to entery custom recovery
okay this is less than ideal... flashed every type of custom recovery to no avail but unable to boot into recovery.
Tried fastboot erase cache before and after flashing recoveries.
When selecting recovery 'entering recovery' appears at the top of the screen, after a few seconds the screen goes black for a second or so then back to the 'entering recovery' which never actually happens - Its like it hangs on loading the recovery.
Result of fastboot allvars query:
(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.206.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3C6W904988
(bootloader) imei: xxxxxxxxxxxxxxxxx
(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: 4047mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-868a9c98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Does anyone have any ideas?
This phone/brick is vexing to say the least!
alangordon73 said:
okay this is less than ideal... flashed every type of custom recovery to no avail but unable to boot into recovery.
Tried fastboot erase cache before and after flashing recoveries.
When selecting recovery 'entering recovery' appears at the top of the screen, after a few seconds the screen goes black for a second or so then back to the 'entering recovery' which never actually happens - Its like it hangs on loading the recovery.
Result of fastboot allvars query:
(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.206.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3C6W904988
(bootloader) imei: xxxxxxxxxxxxxxxxx
(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: 4047mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-868a9c98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Does anyone have any ideas?
This phone/brick is vexing to say the least!
Click to expand...
Click to collapse
Flash mdmower's twrp recovery
http://android.cmphys.com/twrp-m7/
Right it seems I've managed to make a mess of this - I've foolishly relocked the booloader on a custom recovery and now I can't get it unlocked again - It reboots to recovery and just hangs and wont unlock the bootloader.
I've tried using the rom.zip from the RUU and flashing it in fastboot to which it reports it cannot allocate the space in bytes.
I've tried running the RUU which fails at checking headers on step 1/5
RUU I'm trying to use is RUU_M7_UL_K44_SENSE55_MR_O2_UK_4.20.206.16_Radio_4A.23.3263.28_10.38r.1157.04L_release_353143_signed_2
Is the recovery partition perhaps corrupt as I'm getting absolutely nowhere with this paperweight?
I'm now at a loss and most peeved!
alangordon73 said:
Right it seems I've managed to make a mess of this - I've foolishly relocked the booloader on a custom recovery and now I can't get it unlocked again - It reboots to recovery and just hangs and wont unlock the bootloader.
I've tried using the rom.zip from the RUU and flashing it in fastboot to which it reports it cannot allocate the space in bytes.
I've tried running the RUU which fails at checking headers on step 1/5
RUU I'm trying to use is RUU_M7_UL_K44_SENSE55_MR_O2_UK_4.20.206.16_Radio_4A.23.3263.28_10.38r.1157.04L_release_353143_signed_2
Is the recovery partition perhaps corrupt as I'm getting absolutely nowhere with this paperweight?
I'm now at a loss and most peeved!
Click to expand...
Click to collapse
You can't flash a RUU version that is older than your actual version-main when the phone is S-ON. To unlock a bootloader that was relocked with a custom recovery installed, you either need to reflash a signed(official) firmware or a ruu since this is the only thing that the phone will accept in this state (locked and s-on).
Unfortunately i can't find any 7.18.206.51 firmware so you'll have to reflash the whole phone using the 7.18.206.51 RUU which will reset everything back to stock and wipe your files.
https://www.androidfilehost.com/?fid=24352994023702662
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459056_signed.zip
fastboot reboot-bootloader
than you'll be able to unlock again.
Don't forget to use htc_fastboot.exe for the flash zip command (not the regular fastboot.exe). A quick search on androidfilehost.com for "htc_fastboot" and you'll be able to download it if you don't have it already.
Outstanding... Flashed back and unlocked the boot loader. Spent enough time and frustration this week so early night and will try flash a recovery and ArHD tomorrow.
Can't thank you enough
Grrrr... Flashed the recovery suggested above and the phone just does not want to go into recovery.
I've tried:
Powering down from Android and then going into Bootloader just stops on Entering Recovery.
Power down, entering bootloader then reseting the phone - again stops on Enterng Recovery.
Power down from Android, power back up, master reset - again just stops on entering recovery.
screams...
alangordon73 said:
Grrrr... Flashed the recovery suggested above and the phone just does not want to go into recovery.
I've tried:
Powering down from Android and then going into Bootloader just stops on Entering Recovery.
Power down, entering bootloader then reseting the phone - again stops on Enterng Recovery.
Power down from Android, power back up, master reset - again just stops on entering recovery.
screams...
Click to expand...
Click to collapse
Did you tried the old TWRP 2.6.3.3 version? Ive seen a lot of pple only being able to use this version when newer ones will cause the exact problem you are experiencing. Might worth a try.
Solved! TWRP 2.6.3.3 works.
alray said:
With a S-ON phone you can only flash Signed RUU that are for your phone CID, MID and version-main. You also can't flash older RUU than your version-main.
With S-OFF, you can flash Signed/Un-signed RUU of your choice (you'll have to change your CID and maybe your MID)
Flashing a stock rom (not talking about a RUU here, but a stockish unbranded custom rom) doesn't requires S-OFF, simply flash using custom recovery. ARHD 93 is a good starting point imo.
Click to expand...
Click to collapse
Then I can flash any Ruu I want if I change Cid and Mid to match Ruu with S-off? Even if it's from 4.3 to kit Kat or Lollipop?
Thanks and sorry for hijacking the thread.
Enviado desde mi Nexus 5 mediante Tapatalk
JabboMaster said:
Then I can flash any Ruu I want if I change Cid and Mid to match Ruu with S-off? Even if it's from 4.3 to kit Kat or Lollipop?
Thanks and sorry for hijacking the thread.
Enviado desde mi Nexus 5 mediante Tapatalk
Click to expand...
Click to collapse
not exactly,it depend what phone variant you have. If its a M7_UL or M7_U then you can flash any M7_UL or M7_U RUU youd like by changing the CID and MID. If you want to flash a lollipop RUU you need to have at least hboot 1.57 with a 6.xx.xxx.x firmware already installed on the phone. Firmware can easily be updated if needed when s-off.
alray said:
not exactly,it depend what phone variant you have. If its a M7_UL or M7_U then you can flash any M7_UL or M7_U RUU youd like by changing the CID and MID. If you want to flash a lollipop RUU you need to have at least hboot 1.57 with a 6.xx.xxx.x firmware already installed on the phone. Firmware can easily be updated if needed when s-off.
Click to expand...
Click to collapse
Ok, thanks.
Gonna try flashing first a Kitkat Ruu and then updating via Ota to Lollipop.
Enviado desde mi Nexus 5 mediante Tapatalk
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.