Database Develop

[Q] Bricked M7-ul! Maybe beyond repair...??

To anyone who wants a challenge....
First: I installed twrp in preparing for flashing a custom rom.
2nd: Format/wiped sys/dalvik/cache
3rd: when trying to flash recieved error: remote not allowed!
4th: received the advice to relock then unlock again and that would fix the error problem.
5th: relocked bootloader... (has always been S-on)
6th: felt I had been denied, critical, need to know information.... fastboot ver was 1.55 and no longer able to unlock. Is there a fix for this yet? Can anyone please help me? I will compensate for time if needed.... I feel I have tried everything and read a couple hundred pages of threads on the subject but seems no one has answered the same question or has had different variables.
7th: Begging for help.... PLEASE!!!
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4035mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Thank you in advance to any suggestions or information!!
Bda714
[email protected]

bda714 said:
To anyone who wants a challenge....
First: I installed twrp in preparing for flashing a custom rom.
2nd: Format/wiped sys/dalvik/cache
3rd: when trying to flash recieved error: remote not allowed!
4th: received the advice to relock then unlock again and that would fix the error problem.
5th: relocked bootloader... (has always been S-on)
6th: felt I had been denied, critical, need to know information.... fastboot ver was 1.55 and no longer able to unlock. Is there a fix for this yet? Can anyone please help me? I will compensate for time if needed.... I feel I have tried everything and read a couple hundred pages of threads on the subject but seems no one has answered the same question or has had different variables.
7th: Begging for help.... PLEASE!!!
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4035mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Thank you in advance to any suggestions or information!!
Bda714
[email protected]
Click to expand...
Click to collapse
why can't you unlock at htcdev like everyone else ?

really.....?
clsA said:
why can't you unlock at htcdev like everyone else ?
Click to expand...
Click to collapse
Do you really think I would be asking for help if it were that easy?? When I flash unlock token it says writing and OK but does nothing....

bda714 said:
To anyone who wants a challenge....
First: I installed twrp in preparing for flashing a custom rom.
2nd: Format/wiped sys/dalvik/cache
3rd: when trying to flash recieved error: remote not allowed!
4th: received the advice to relock then unlock again and that would fix the error problem.
5th: relocked bootloader... (has always been S-on)
6th: felt I had been denied, critical, need to know information.... fastboot ver was 1.55 and no longer able to unlock. Is there a fix for this yet? Can anyone please help me? I will compensate for time if needed.... I feel I have tried everything and read a couple hundred pages of threads on the subject but seems no one has answered the same question or has had different variables.
7th: Begging for help.... PLEASE!!!
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4035mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Thank you in advance to any suggestions or information!!
Bda714
[email protected]
Click to expand...
Click to collapse
@nkk71 same problem here.. These are Dev edition One's.
Sent from my HTC One using Tapatalk

bda714 said:
To anyone who wants a challenge....
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
Click to expand...
Click to collapse
clsA said:
why can't you unlock at htcdev like everyone else ?
Click to expand...
Click to collapse
bda714 said:
Do you really think I would be asking for help if it were that easy?? When I flash unlock token it says writing and OK but does nothing....
Click to expand...
Click to collapse
Well, it's not bricked, BUT you pretty much can't do anything at the moment!
For anybody reading this: STOP flashing a US Dev Edition firmware 4.06.1540.x on your non-Dev Edition phones with a relocked bootloader and S-On, chances of HTCdev getting to unlock bootloader again is close to zero, or really zero.​
(please anybody feel free to correct me)​
I don't know if this is due to updated hboot, or what HTCdev unlock generator takes into account, but if for example it takes into account CID and firmware, then your firmware .1540. is not "stock"; for CWS__001 it should be a .502. firmware.
So what are the options: wait for an ATT OTA 4.06 (or above) to be released extract the firmware.zip in it (which is signed) and flash that, then try to get an unlock token and hope it works.
I'm sorry this is not the answer you're looking for, but unfortunately it's the only I have. Maybe someone else has a better idea.
EDIT: since US-Dev Edition is supposed to be unlocked anyway, has anybody tried "fastboot oem unlock"??
EDIT 2: try it in both normal mode and in "fastboot oem rebootRUU" mode.
^^ doesn't work

nkk71 said:
Well, it's not bricked, BUT you pretty much can't do anything at the moment!
For anybody reading this: STOP flashing a US Dev Edition firmware 4.06.1540.x on your non-Dev Edition phones with a relocked bootloader and S-On, chances of HTCdev getting to unlock bootloader again is close to zero, or really zero.​
(please anybody feel free to correct me)​
I don't know if this is due to updated hboot, or what HTCdev unlock generator takes into account, but if for example it takes into account CID and firmware, then your firmware .1540. is not "stock"; for CWS__001 it should be a .502. firmware.
So what are the options: wait for an ATT OTA 4.06 (or above) to be released extract the firmware.zip in it (which is signed) and flash that, then try to get an unlock token and hope it works.
I'm sorry this is not the answer you're looking for, but unfortunately it's the only I have. Maybe someone else has a better idea.
EDIT: since US-Dev Edition is supposed to be unlocked anyway, has anybody tried "fastboot oem unlock"??
EDIT 2: try it in both normal mode and in "fastboot oem rebootRUU" mode.
Click to expand...
Click to collapse
I don't mess with any of that unless I'm s-off, so i won't be testing it anytime soon

[Q] HTC One stuck in bootloader with relocked bootloader and s-on

This the problem .
I have rooted my one but removed the software , it has s-on and relocked bootloader .
TWRP is no longer on the phone .
HBoot is 1.54000
Cid is GGOGL001
I sthere a sollution for this problem ?

Peter.henssen said:
This the problem .
I have rooted my one but removed the software , it has s-on and relocked bootloader .
TWRP is no longer on the phone .
HBoot is 1.54000
Cid is GGOGL001
I sthere a sollution for this problem ?
Click to expand...
Click to collapse
can you unlock your bootloader via htcdev? or fastboot oem unlock?
post your fastboot getvar all minus imei/sn

No to both questions , i cannot confirm the unlock confirmation .
Fastboot oem unlock doesnt work .
alray said:
can you unlock your bootloader via htcdev? or fastboot oem unlock?
post your fastboot getvar all minus imei/sn
Click to expand...
Click to collapse

Peter.henssen said:
No to both questions , i cannot confirm the unlock confirmation .
Fastboot oem unlock doesnt work .
Click to expand...
Click to collapse
post your fastboot getvar all

c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4274mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Peter.henssen said:
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4274mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
you can tru to restore with a ruu.zip

It boots into the google screen but no further , i can get into the bootloader .
alray said:
post your fastboot getvar all
is your still booting?
Click to expand...
Click to collapse

Peter.henssen said:
It boots into the google screen but no further , i can get into the bootloader .
Click to expand...
Click to collapse
maybe you could try to restore with a ruu.
http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/

Stuck
Hi I was wondering if anyone can help. I am Stuck in Bootloader with S 0on and relocked also is there anything i can do? does anyone have RUU for 4.4 5.5 sense?

gerry8 said:
Hi I was wondering if anyone can help. I am Stuck in Bootloader with S 0on and relocked also is there anything i can do? does anyone have RUU for 4.4 5.5 sense?
Click to expand...
Click to collapse
Hi gerry, just received your pm. Can you post an updated ''fastboot getvar all'' and describe the situation a little more (what rom are you on, what recovery/version and what you did before you wre stuck in bootloader)

alray said:
Hi gerry, just received your pm. Can you post an updated ''fastboot getvar all'' and describe the situation a little more (what rom are you on, what recovery/version and what you did before you wre stuck in bootloader)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA41ES902933
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3442mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
@alray Here it is I was S off unlocked and flashed Viper Rom. It wouldnt reboot so I tried to go back to Stock and for some reason I relocked and S on. I have no recovery cant get to it. I tried old RUU but wont work. cause i read cant downgrade. reboot phone goes straight to Bootloader

gerry8 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA41ES902933
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3442mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
@alray Here it is I was S off unlocked and flashed Viper Rom. It wouldnt reboot so I tried to go back to Stock and for some reason I relocked and S on. I have no recovery cant get to it. I tried old RUU but wont work. cause i read cant downgrade. reboot phone goes straight to Bootloader
Click to expand...
Click to collapse
your Verizon you have to s-off to do anything (unlock bootloader)
go back and get s-off instructions for Verizon

clsA said:
your Verizon you have to s-off to do anything (unlock bootloader)
go back and get s-off instructions for Verizon
Click to expand...
Click to collapse
@clsA i cant get out of bootloader. I am stuck how can i achieve s off and unlock bootloader from there

gerry8 said:
@clsA i cant get out of bootloader. I am stuck how can i achieve s off and unlock bootloader from there
Click to expand...
Click to collapse
Okay, before I can help, I'll need to know some more info. How did this happen, what were you doing, were you flashing an ruu? Let's get that taken care of before we can help you.

Truth6199 said:
Okay, before I can help, I'll need to know some more info. How did this happen, what were you doing, were you flashing an ruu? Let's get that taken care of before we can help you.
Click to expand...
Click to collapse
read post 11
he's pretty much screwed unless he can flash a RUU

clsA said:
read post 11
he's pretty much screwed unless he can flash a RUU
Click to expand...
Click to collapse
I didn't even see that post. Man oh man. If he can't flash an ruu, he is really screwed...

screwed
Does anyone have the kit kat RUU for Verizon..... Since i am dead in the water lol

gerry8 said:
Does anyone have the kit kat RUU for Verizon..... Since i am dead in the water lol
Click to expand...
Click to collapse
just keep an eye on the Verizon forums it will show up their first

Thanks
clsA said:
just keep an eye on the Verizon forums it will show up their first
Click to expand...
Click to collapse
@clsA Thank you

@clsA any update on ruu 4.4
Sent from my GT-P3113 using XDA Premium 4 mobile app

Would like some help with s-offing my m7.

So a few days ago, i received an HTC One M7 from my dad. Having rooted and played around with other devices before, I immediately looked up all the guides and necessities to get this thing up and running. It was running Lollipop when i got it, so that means its running HBOOT 1.61.0000. After digging around some more, I learned that It isnt possible to s-off with this version of bootloader. And to go around this, I have to downgrade with a RUU. Now here's my real problem, I cant find a RUU compatible with my CID. I'll paste what i got from the fastboot getvar all command below and any help would be great.
Currently, I am unlocked and rooted. I will be using the stock lollipop rom again.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.708.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34TW915195
(bootloader) imei: 355859051010403
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 3951mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-dd14e948
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

BeefBrisket said:
So a few days ago, i received an HTC One M7 from my dad. Having rooted and played around with other devices before, I immediately looked up all the guides and necessities to get this thing up and running. It was running Lollipop when i got it, so that means its running HBOOT 1.61.0000. After digging around some more, I learned that It isnt possible to s-off with this version of bootloader. And to go around this, I have to downgrade with a RUU. Now here's my real problem, I cant find a RUU compatible with my CID. I'll paste what i got from the fastboot getvar all command below and any help would be great.
Currently, I am unlocked and rooted. I will be using the stock lollipop rom again.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.708.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34TW915195
(bootloader) imei: 355859051010403
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 3951mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-dd14e948
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
You can stop looking for RUUs because you need to be s-off in order to downgrade h-boot. You can s-off your phone with sunshine, but that costs 25$

donkeykong1 said:
You can stop looking for RUUs because you need to be s-off in order to downgrade h-boot. You can s-off your phone with sunshine, but that costs 25$
Click to expand...
Click to collapse
What about the Guru Reset Roms/Tools? I tried installing a 4.3 Asia WWE guru rom and HBOOT was still the same. If I go down to 4.1.? will it downgrade? I would just like to know if there's anything else before I lay down USD$25 on sunshine.

BeefBrisket said:
What about the Guru Reset Roms/Tools? I tried installing a 4.3 Asia WWE guru rom and HBOOT was still the same. If I go down to 4.1.? will it downgrade? I would just like to know if there's anything else before I lay down USD$25 on sunshine.
Click to expand...
Click to collapse
As I said before - you can't downgrade h-boot with s-on. Sunshine is the only way to s-off your phone. OK, there is a gold card option, but that is even more expensive than sunshine, and it's complicated to do

Attempting to return m7 to stock to unlock phone for all sim cards.

Hi all,
I've recently destroyed my current contracts phone, and have reacquired my old HTC One m7 as a backup, however it's currently locked to O2-UK, and I need to unlock it to take my EE sim. I have had an unlatching code from O2 which SHOULD unlock the phone for use with any sim card. However, because I have rooted it, the unlatch code gives an "Incorrect code" error every time, so I guess I'm gonna have to return it to stock to unlock, then potentially reroot. My issue is I am struggling to find a stock O2 RUU file, presumably because the handset is so old, all the links I've found are dead.
My getvar all info is as follows:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.14.206.2
(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___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3927mV
(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!
Can anyone offer any assistance at all?

wingnutz said:
Hi all,
I've recently destroyed my current contracts phone, and have reacquired my old HTC One m7 as a backup, however it's currently locked to O2-UK, and I need to unlock it to take my EE sim. I have had an unlatching code from O2 which SHOULD unlock the phone for use with any sim card. However, because I have rooted it, the unlatch code gives an "Incorrect code" error every time, so I guess I'm gonna have to return it to stock to unlock, then potentially reroot. My issue is I am struggling to find a stock O2 RUU file, presumably because the handset is so old, all the links I've found are dead.
My getvar all info is as follows:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.14.206.2
(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___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3927mV
(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!
Can anyone offer any assistance at all?
Click to expand...
Click to collapse
The four o2 RUUs posted in the "Lollipop RUU' thread are still available for download.
Direct link to the latest version: https://androidfilehost.com/?fid=24352994023702662
Don't forget to flash using htc_fastboot.exe (the standard fastboot.exe won't work)
Btw many owners of the M7 were able to sim unlock using this unlock code method simply by flashing a "close to stock" custom rom (i.e ARHD) instead of going back full stock using a ruu.

alray said:
The four o2 RUUs posted in the "Lollipop RUU' thread are still available for download.
Direct link to the latest version: https://androidfilehost.com/?fid=24352994023702662
Don't forget to flash using htc_fastboot.exe (the standard fastboot.exe won't work)
Btw many owners of the M7 were able to sim unlock using this unlock code method simply by flashing a "close to stock" custom rom (i.e ARHD) instead of going back full stock using a ruu.
Click to expand...
Click to collapse
Oh really? That is interesting to know. Thankyou for that little snippet, and especially for the link, I will give that a try and report back.

alray said:
Btw many owners of the M7 were able to sim unlock using this unlock code method simply by flashing a "close to stock" custom rom (i.e ARHD) instead of going back full stock using a ruu.
Click to expand...
Click to collapse
Just a quick reply to say thankyou very much to alray for your advice, I managed to unlatch my handset by flashing ARHD to the phone, entered the code which was accepted this time, and im now back running ViperOne again. Nice one mate. :good:

Need help.. Bricked after firmware flash only fastboot with black screen

I need help with my old HTC One 802w which was kept in dark for long time, picked 2 days ago to just play with and bricked after may be wrong firmware flash, I attempted flash due to network signals issue (This was the reason to retire it earlier.) Below are the details of what happened, hope someone guide me to revive it or is it just a paper weight now..?
getvar all, when phone was working.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: T3.16.1229.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.15.1403.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: 123456789012
(bootloader) imei: xxxxxxx (sensored)
(bootloader) meid: 00000000000000
(bootloader) product: m7cdtu
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN078****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4010mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
This is what i did with this in attempt to update...
1: Changed the mid from PN078**** to PN071000
Tried to flash following which failed everytime with "wrong device id" even before changing mid as well as after changing.
PN07IMG_M7C_DUG_K443_SENSE60_MR_HTC_Europe_6.13.401.3_Radio_1237.28.35.0516_release_391892_signed.zip
PN07IMG_M7C_DTU_L50_SENSE60_MR_HTCCN_CHS_CMCC_7.19.1403.31_Radio_1237.29.35.0903_release_426134_signed.zip
This what I flashed and phone bricked..
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.30_Radio_4T.35.3218.16_10.33Q.1718.01L_release_449611_combined_signed.zip
Phone now is with blacked out display in fastboot mode.
fastboot can only pull this info...getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: (Sensored) I noticed that phone imei is changed too, not the same when it was working.)
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3489mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Note: I unlocked bootloader from HTCdev 2 days ago and re-locked to flash stock firmware.
with TWRP recovery twrp-3.0.2-0-m7cdtu, S-OFF, bootloder re-locked.
I was unable to unlock re-locked bootloader with "fastboot oem unlock".
Phone is showing in fastboot as "????????????? fastboot"
Any chance to get it back to life..? Appreciate any help. Thanks.

shahper1 said:
I need help with my old HTC One 802w which was kept in dark for long time, picked 2 days ago to just play with and bricked after may be wrong firmware flash, I attempted flash due to network signals issue (This was the reason to retire it earlier.) Below are the details of what happened, hope someone guide me to revive it or is it just a paper weight now..?
getvar all, when phone was working.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: T3.16.1229.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.15.1403.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: 123456789012
(bootloader) imei: xxxxxxx (sensored)
(bootloader) meid: 00000000000000
(bootloader) product: m7cdtu
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN078****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4010mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
This is what i did with this in attempt to update...
1: Changed the mid from PN078**** to PN071000
Tried to flash following which failed everytime with "wrong device id" even before changing mid as well as after changing.
PN07IMG_M7C_DUG_K443_SENSE60_MR_HTC_Europe_6.13.401.3_Radio_1237.28.35.0516_release_391892_signed.zip
PN07IMG_M7C_DTU_L50_SENSE60_MR_HTCCN_CHS_CMCC_7.19.1403.31_Radio_1237.29.35.0903_release_426134_signed.zip
This what I flashed and phone bricked..
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.30_Radio_4T.35.3218.16_10.33Q.1718.01L_release_449611_combined_signed.zip
Phone now is with blacked out display in fastboot mode.
fastboot can only pull this info...getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: (Sensored) I noticed that phone imei is changed too, not the same when it was working.)
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3489mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Any chance to get it back to life..? Appreciate any help. Thanks.
Click to expand...
Click to collapse
The RUU you were able to flash is not for compatible with your phone. Your phone, the dual-sim variant ''M7CTDU', despite having the same commercial ''HTC One'' name and similar product code ID is a completely different phone from the ''M7_UL'' .
The M7_UL RUU was accepted by your phone as a valid firmware because it passed CID check (because your phone having superCID 11111111) and MID check because the PN0710000 is the correct MID for that version. Your case is unfortunately a good example why S-OFF isn't for everyone.
You now have an incompatible bootloader on your phone, maybe corrupt partitions as well. Now you wont be able to flash the correct ruu using fastboot. Maybe jtag is an option but probably won't worth the money for a 6+ years old phone.
Note: I unlocked bootloader from HTCdev 2 days ago and re-locked to flash stock firmware.
with TWRP recovery twrp-3.0.2-0-m7cdtu, S-OFF, bootloder re-locked.
I was unable to unlock re-locked bootloader with "fastboot oem unlock".
Phone is showing in fastboot as "????????????? fastboot"
Click to expand...
Click to collapse
-You don't need to re-lock the bootloader to flash stock firmware if your phone is s-off, only if it's s-on.
-fastboot oem unlock can't be used to unlock the bootloader, you have to pull your identifier_token, submit it to htcdev.com and flash the Unlock_code received from htcdev

alray said:
The RUU you were able to flash is not for compatible with your phone. Your phone, the dual-sim variant ''M7CTDU', despite having the same commercial ''HTC One'' name and similar product code ID is a completely different phone from the ''M7_UL'' .
The M7_UL RUU was accepted by your phone as a valid firmware because it passed CID check (because your phone having superCID 11111111) and MID check because the PN0710000 is the correct MID for that version. Your case is unfortunately a good example why S-OFF isn't for everyone.
You now have an incompatible bootloader on your phone, maybe corrupt partitions as well. Now you wont be able to flash the correct ruu using fastboot. Maybe jtag is an option but probably won't worth the money for a 6+ years old phone.
-You don't need to re-lock the bootloader to flash stock firmware if your phone is s-off, only if it's s-on.
-fastboot oem unlock can't be used to unlock the bootloader, you have to pull your identifier_token, submit it to htcdev.com and flash the Unlock_code received from htcdev
Click to expand...
Click to collapse
Thanks alot for the detailed reply, I never used HTC phones that much so didn't have much of info to be at safe side while flashing.
You are right its not worth it to spend that much effort for 6 years old phone and this was the reason only for me to be so careless and there is also not much support anymore online for One M7.
Anyway, appreciate your time and support.
By the way, I relocked the unlocked bootloader which I did from HTCDev only. So oem unlock should work on re-locked bootloader..?