Need help.. Bricked after firmware flash only fastboot with black screen - One (M7) Q&A, Help & Troubleshooting

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..?

Related

[Q] HTC One US unlocked 32 GB stuck on boot screen after OTA update

I got an OTA update on my HTC One US unlocked 32 GB version. The OTA update installed on the phone but the phone never booted up.
I went into the bootloader and tried factory reset but no success.
Now I want to flash my phone using RUU, but I am not getting correct RUU for my phone. I have unlocked the bootloader from HTCDEV website.
Details are :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.1540.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT367W910917
(bootloader) imei: 354439059958431
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4100mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-076e0e17
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I tried many RUU matching the mid and cid number of my phone for example : htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_brightstarus_wwe_4-19-1540-9_radio_4a-23-3263-28_10-38r-1157-04l_release_353887_signed_3-exe/ but it gave image error. Please help
still having trouble
do u have s-off if not when trying to flash a ruu you need to relock bootloader b4 running ruu
s_rupainwar said:
I got an OTA update on my HTC One US unlocked 32 GB version. The OTA update installed on the phone but the phone never booted up.
I went into the bootloader and tried factory reset but no success.
Now I want to flash my phone using RUU, but I am not getting correct RUU for my phone. I have unlocked the bootloader from HTCDEV website.
Details are :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.1540.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT367W910917
(bootloader) imei: 354439059958431
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4100mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-076e0e17
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I tried many RUU matching the mid and cid number of my phone for example : htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_brightstarus_wwe_4-19-1540-9_radio_4a-23-3263-28_10-38r-1157-04l_release_353887_signed_3-exe/ but it gave image error. Please help
Click to expand...
Click to collapse
That ruu should work for you but you are s-on, so as stated above you will need to relock to flash it.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Then run the ruu while connected with fastboot usb. :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

HTC One 801n Black Screen

Hi guys, i flashed Guru' Reset with CWM and after the phone turned on it only shows black screen with statusbar and after 1-2 mins it restarts again. I have (S-ON, Bootloader UNLOCKED)
arber95 said:
Hi guys, i flashed Guru' Reset with CWM and after the phone turned on it only shows black screen with statusbar and after 1-2 mins it restarts again. I have (S-ON, Bootloader UNLOCKED)
Click to expand...
Click to collapse
You have not provided much information.
Which GURU reset you used ? Which firmware you were on before flashing it ?
Also attach you phone to pc in fastboot mode, open command prompt and type in fastboot getvar all
Copy, paste the result over here. Make sure you remove IMEI and Serial No from it.
Also it's generally advised to use TWRP with HTC One.
Judging from my Bootloader mode info my OS Version was 2.24.401 so i flashed Guru_Reset_M7_2.24.401.1 with TWRP (i don't know which firmware it was on because it was bricked when i got it, it kept restarting)
Here is the info from cmd
C:\fastboot>fastboot getvar all
(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__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
(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
all: Done!
finished. total time: 0.042s
I am a newbie to HTC, sorry ..
arber95 said:
Judging from my Bootloader mode info my OS Version was 2.24.401 so i flashed Guru_Reset_M7_2.24.401.1 with TWRP (i don't know which firmware it was on because it was bricked when i got it, it kept restarting)
Here is the info from cmd
C:\fastboot>fastboot getvar all
(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__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
(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
all: Done!
finished. total time: 0.042s
I am a newbie to HTC, sorry ..
Click to expand...
Click to collapse
can you go into settings ?
GOOD news is that you can achieve S-OFF on this HBOOT version for free and very easily.
Just do as it is said in this thread.
http://forum.xda-developers.com/showthread.php?t=2487888
S-OFF has many advantages. And if you follow the guidelines and always read before doing anything, you won't get into any trouble.
Once you achieve S-OFF. you can install any firmware on your phone.
abdulwakil said:
can you go into settings ?
GOOD news is that you can achieve S-OFF on this HBOOT version for free and very easily.
Just do as it is said in this thread.
http://forum.xda-developers.com/showthread.php?t=2487888
S-OFF has many advantages. And if you follow the guidelines and always read before doing anything, you won't get into any trouble.
Once you achieve S-OFF. you can install any firmware on your phone.
Click to expand...
Click to collapse
You cant get s-off without a working rom on the phone, so thats got to be fixed first.
@arber95 reflash the guru reset file using TWRP 2.6.3.3 recovery, it should work then.
Hold down power button + volume down, the 2 lights on the bottom will flash approx 15 times, just keep holding, when the lights stop flashing, release to power button only, this will take you back to the bootloader.
Flash TWRP 2.6.3.3 recovery using fastboot commands http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
enter recovery, hopefully the guru reset file is still there on your internal storage, if not you'll have to push it to your internal storage using adb, then uplug your phone and flash it.
Seanie280672 said:
You cant get s-off without a working rom on the phone, so thats got to be fixed first.
@arber95 reflash the guru reset file using TWRP 2.6.3.3 recovery, it should work then.
Click to expand...
Click to collapse
I helped him RUU to stock.
He didn't want S-OFF. Just a working phone. He used ruu after incrementally flashing signed firmwares to 4.19.401.9..
Strangely his phone dialer was Fcing even after stock RUU 4.09.401.9
Last thing I know he catched 4.09.401.11 OTA and updated to it.
Don't know if the problem got solved.
As @abdulwakil noted. I'm back to Stock 4.4.2 with no root and relocked bootloader. Now my problems are: Dialer FC, i cant swipe notification center at all, and the phone restarts every exactly 4 minutes (which is strange), and it's not reading the simcard or getting signal (which it used to before)
@Seanie280672, help needed.
arber95 said:
As @abdulwakil noted. I'm back to Stock 4.4.2 with no root and relocked bootloader. Now my problems are: Dialer FC, i cant swipe notification center at all, and the phone restarts every exactly 4 minutes (which is strange), and it's not reading the simcard or getting signal (which it used to before)
Click to expand...
Click to collapse
Sounds to me like you have the IMEI / Baseband problem, the only fix if the RUU didnt fix it is to send it off for repair, dont send it to HTC, they will charge you as your bootloader is re-locked, unlocking your bootloader voids your waranty, try your carrier if your on contract, its a hartdware problem and no amount of flashing will fix it.
Only way to hide that you ever unlocked your bootloader is to get s-off and falsh a very early rom, then lock and s-on before updating, however, now your probably on HBOOT 1.56, s-off is only possible through sunshine and will cost $25.
Seanie280672 said:
Sounds to me like you have the IMEI / Baseband problem, the only fix if the RUU didnt fix it is to send it off for repair, dont send it to HTC, they will charge you as your bootloader is re-locked, unlocking your bootloader voids your waranty, try your carrier if your on contract, its a hartdware problem and no amount of flashing will fix it.
Only way to hide that you ever unlocked your bootloader is to get s-off and falsh a very early rom, then lock and s-on before updating, however, now your probably on HBOOT 1.56, s-off is only possible through sunshine and will cost $25.
Click to expand...
Click to collapse
This is my present getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4214mV
(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
all: Done!
Seanie280672 said:
Sounds to me like you have the IMEI / Baseband problem, the only fix if the RUU didnt fix it is to send it off for repair, dont send it to HTC, they will charge you as your bootloader is re-locked, unlocking your bootloader voids your waranty, try your carrier if your on contract, its a hartdware problem and no amount of flashing will fix it.
Only way to hide that you ever unlocked your bootloader is to get s-off and falsh a very early rom, then lock and s-on before updating, however, now your probably on HBOOT 1.56, s-off is only possible through sunshine and will cost $25.
Click to expand...
Click to collapse
his phone was working on cm12, how come ?
arber95 said:
This is my present getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(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__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4214mV
(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
all: Done!
Click to expand...
Click to collapse
please remove your imei and serial from your post.
You could try flashing this, this is a full wipe firmware, it will wipe everything and re-build your partitions is the same firmware you have now: https://www.androidfilehost.com/?fid=23329332407579671
I would recommend after that to straight away, flash TWRP recovery and then push a custom KK sense rom to your internal storage and flash it, see if you have the same problem., if the problem still persists, you have a hardware issue.
Seanie280672 said:
please remove your imei and serial from your post.
You could try flashing this, this is a full wipe firmware, it will wipe everything and re-build your partitions is the same firmware you have now: https://www.androidfilehost.com/?fid=23329332407579671
I would recommend after that to straight away, flash TWRP recovery and then push a custom KK sense rom to your internal storage and flash it, see if you have the same problem., if the problem still persists, you have a hardware issue.
Click to expand...
Click to collapse
He is on 4.09.401.11 firmware. and S-ON
abdulwakil said:
his phone was working on cm12, how come ?
Click to expand...
Click to collapse
Someone else had the same problem recently, I was just trying to find the thread, i'll call for some expert advice, cant quite remember, CM12 / 11 does something slightly different
@clsA @nkk71 @Danny201281
---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------
abdulwakil said:
He is on 4.09.401.11 firmware. and S-ON
Click to expand...
Click to collapse
not according to his fastboot getvar all he's not. (bootloader) version-main: 4.19.401.9
Seanie280672 said:
not according to his fastboot getvar all he's not. (bootloader) version-main: 4.19.401.9
Click to expand...
Click to collapse
lol, he hasn't posted the present getvar all output. let him do that.
abdulwakil said:
lol, he hasn't posted the present getvar all output. let him do that.
Click to expand...
Click to collapse
well here is 401.11 full wipe https://www.androidfilehost.com/?fid=23329332407579952
I'm sorry for being silly guys, but phone got a new update
This is the new getvar
(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.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3900mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
arber95 said:
I'm sorry for being silly guys, but phone got a new update
This is the new getvar
(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.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3900mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
And is it still playing up ?
This is all the wipe and non wipe firmware files, https://docs.google.com/spreadsheets/d/tvdrXmIGYk0OWi0jtqih_0g/htmlview?pli=1, obviously you can only go up as your s-on, im surprised though that you can update whilst having those problems and they're not being fixed by the updates, I would be tempted to update as far as 6.09.401.5 full wipe, then flash twrp 2.6.3.3 and flash trhis rom by clsA
https://www.androidfilehost.com/?fid=95916177934521009
arber95 said:
I'm sorry for being silly guys, but phone got a new update
This is the new getvar
(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.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3900mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Yeah definitely sounds like unknown imei and baseband although I would expect you to only see the HTC logo after unlocking the screen.
For some reason CM roms work even with this issue. I believe it's because there is no Sense overlay with CM But I'm not exactly sure why they work.
Can you go to Settings>About>Phone Identity. And check your IMEI number is it displayed as Unknown?
Also Settings>About>Software information>More. And check your baseband is it displayed as Unknown.?
Seanie280672 said:
And is it still playing up ?
This is all the wipe and non wipe firmware files, https://docs.google.com/spreadsheets/d/tvdrXmIGYk0OWi0jtqih_0g/htmlview?pli=1, obviously you can only go up as your s-on, im surprised though that you can update whilst having those problems and they're not being fixed by the updates, I would be tempted to update as far as 6.09.401.5 full wipe, then flash twrp 2.6.3.3 and flash trhis rom by clsA
https://www.androidfilehost.com/?fid=95916177934521009
Click to expand...
Click to collapse
Again Sim not recognised, dialer FC, notification center doesn't open, and now it restarts more often (every 2 mins or so)

Help (M7 HTC)

Hi all,
Really need some basic English help with a phone I've got.
Story goes that I accepted an OTA update for what I'm assuming was Lollipop, short and sweet version of this story is that the OTA soft bricked my phone, my own fault for doing it on a dodgy wifi connection.
Anyway, I managed to flash a custom ROM onto the phone and it's been fine ever since ... however as it's a work phone they have decided to change from O2/3 Ireland to Vodafone Ireland and the phone would not accept the unlock code due to it running a custom ROM and having the bootlocker unlocked/tampered (S-ON was always the case throughout, I never could manage to turn that OFF)
Now I was told that by connecting to a PC and running FASTBOOT I could lock the BOOTLOCKER back up and then flash an official ROM back to the phone to make it 'stock'.
Can I do this?? Nope.!!! I've got as far as getting the phone into the black screen with HTC written on it but every ROM I've tried just fails to update.
This is the results of a var/getall
(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: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(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: 4232mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 12.082s
Can anybody help me at all? All I want to do is get the phone up and running and then use the SIM unlock code so I can then use my new SIM.
Thank you in advance.

m8 sprint unable to flash any stock rom.

pls experts help me fix this.
i got m8 whl for flash new rom.
after i flashed RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651.14_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_426232_signed_2.exe
i lost imei and base band then again i try
RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_Harman_4.25.654.18_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_446220_signed_2.exe
with this file also no imie or baseband ,
then i start mess my self.
i was root phone then change mid to europe, then phone start to restart it self, then i was wiped all in TWRP.
then try install RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
its failed then again try flash sprint rom now that also false
then i try ViperOneM8+5.0.1.zip rom
its flash done but reboot bootloader,
then try with cm-13.0-20160208-NIGHTLY-m8.zip
then its keep restart CM logo
now last try i gave for Bad_Boyz_Sprint_ONE_M8_Marshmallow_v4.0.zip
now its say this device is not M8 WHL and its false and stop instaling
bellow is getvarr all details(now status) imei show corect from beginning to now in fast boot mode but meid was zeros from start.
MID was modelid: 0P6B70000 before i change.
this phone customer purchase while is in Singapore.
C:\Users\143\Desktop\Dream\android-sdk-windows\platform-tool
l
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45P*******
(bootloader) imei: 990**********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
pls i need help from experts.
Change your MID back to Sprint then run this RUU (choose the correct one for your device)
[how to] change your MID without an eng bootloader
Non H/K = RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651 .14_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_42 6232_signed_2.exe
H/K = RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_Harman_4 .25.654.18_Radio_1.09.20.0209_NV_SPCS_1.52_003_rel ease_446220_signed_2.exe
Sloth said:
Change your MID back to Sprint then run this RUU (choose the correct one for your device)
[how to] change your MID without an eng bootloader
Non H/K = RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651 .14_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_42 6232_signed_2.exe
H/K = RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_Harman_4 .25.654.18_Radio_1.09.20.0209_NV_SPCS_1.52_003_rel ease_446220_signed_2.exe
Click to expand...
Click to collapse
bro thank u so much fast reply,
but my problem is to change the MID again i must power on phone and put in ADB mode
at the moment phone can go fast boot and recovery mode only, cannot flash with any files to power on,
i need help for change mid in fast boot or recovery or must change product id m8_WHL to m8_UL then it will fix.
i think this is only solution????
but dont know how to do with fastboot or recovery mode
If you change it to m8_UL it will not work it has to remain Sprint if you want a working phone.
You can issue adb commands from recovery...not 100% sure it will work so try at your own risk.
Sloth said:
If you change it to m8_UL it will not work it has to remain Sprint if you want a working phone.
You can issue adb commands from recovery...not 100% sure it will work so try at your own risk.
Click to expand...
Click to collapse
my dear bro, u was correct that ADB comands work on recovery mode and now MID back sprint
new get var all.
but still ERROR 155 with all RUU exe
C:\Users\143\Desktop\Dream\android-sdk-windows\platf
l
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45***********
(bootloader) imei: 99000***********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Which RUU are you trying to use?
He tried to flash Bad boyz 4.0 M ROM so possible that he went for the 6.20 RUU.
fazargsm said:
my dear bro, u was correct that ADB comands work on recovery mode and now MID back sprint
new get var all.
but still ERROR 155 with all RUU exe
Click to expand...
Click to collapse
after i change with older hboot zip flashing done with
RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651.14_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_426232_signed_2.exe
RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_Harman_4.25.654.18_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_446220_signed_2.exe
these both files but no imei and baseband unknown problem. but with fast boot show all imei and radio ver.
bellow getvar all details with both flashed files.
is that no problem MEID is 14 zeros????
pls tel me what i did wrong?????
pls help me now fix imei base band problem.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.25.651.14
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT4********
(bootloader) imei: 990004*********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 26d3ff23
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.25.654.18
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45PSF0*****
(bootloader) imei: 99000499*******
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 631e3609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.021s
Click to expand...
Click to collapse
Do you have the Harmon Kardon Edition M8?
Sloth said:
Do you have the Harmon Kardon Edition M8?
Click to expand...
Click to collapse
RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_Harman_4 .25.654.18_Radio_1.09.20.0209_NV_SPCS_1.52_003_rel ease_446220_signed_2.exe
this one is H/K????
i was flashed with both roms.
fazargsm said:
RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_Harman_4 .25.654.18_Radio_1.09.20.0209_NV_SPCS_1.52_003_rel ease_446220_signed_2.exe
this one is H/K????
i was flashed with both roms.
Click to expand...
Click to collapse
What does your boot loader say not what you're trying to flash.
EVOuser94 said:
What does your boot loader say not what you're trying to flash.
Click to expand...
Click to collapse
phone is now on after flash that above firmware but say no sim , some times show imei and baseband some times show unknown what issue that could be?????
bro maybe its phone sim locked???
its always say no sim, but show imei and baseband, in *#*#4636#*#* menu i cant on off radio option(its keep on and after i slect Turn off Radio nothing happen) after i select gsm only or gsm and umts its automatically change to CDMA evdo option,
all ways show no sim some times show preparing sim then again no sim. thats the problem now i have..
really thank u so much for helping me.
i think my problem is MEID 000000000 as i follow on
http://forum.xda-developers.com/spr...d-problems-t3253678/post65086461#post65086461
this post number 5,
as i know MEID must same as IMEI and without last digit,
but in my phone MEID 000000 i was try
fastboot writemeid 99********* this comand but not done
pls any one know write meid comand on fast boot or adb?????

Tampered, Re locked and security Warning

Hello
I was just doing the trail and error to install custom rom by reading some articals. may be i was stupid not paying much attention to what exactly it says. i was happy that i was able to unlock the bootloader and installed the twrp custom recovery everything works fine till now, phone booted to Android too. and when i wanted the recovery its taken me to twrp recovery. here here i have done something and now i have completely lost the phone. now i ended up with tampered relocked and security warning and more over my phone always boots in to fastboot mode only. i can't either go twrp or Android just the fast boot. how can i come out of this mess.
my phone is HTC one bought in India no network lock. any help will be appreciated greatly.
Device details
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.21.707.151
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA*******5
(bootloader) imei: 354********5
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3796mV
(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
and it always stuck in fast boot
Device details
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.21.707.151
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA*******5
(bootloader) imei: 354********5
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3796mV
(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
and it always stuck in fast boot
vaspraveen said:
Hello
I was just doing the trail and error to install custom rom by reading some articals. may be i was stupid not paying much attention to what exactly it says. i was happy that i was able to unlock the bootloader and installed the twrp custom recovery everything works fine till now, phone booted to Android too. and when i wanted the recovery its taken me to twrp recovery. here here i have done something and now i have completely lost the phone. now i ended up with tampered relocked and security warning and more over my phone always boots in to fastboot mode only. i can't either go twrp or Android just the fast boot. how can i come out of this mess.
my phone is HTC one bought in India no network lock. any help will be appreciated greatly.
Device details
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.21.707.151
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA*******5
(bootloader) imei: 354********5
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3796mV
(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
and it always stuck in fast boot
Click to expand...
Click to collapse
You either wiped /system or formatted /data hence why you can't boot in your OS anymore...
Flashing custom software (recovery, roms, kernels) requires an unlocked bootloader (like you already know) but booting custom softwares also requires an unlocked bootloader, that's why you can't access twrp anymore now that it'S relocked, even if it's still there on your phone.
Flash the 7.19.707.151 RUU, your phone will be back to 100% stock and from there you'll be able to unlock your bootloader again, flash twrp and a rom. There is a sticky thread in the general section (lolliopop ruu collection), you'll find instructions how to flash the ruu there.
alray said:
You either wiped /system or formatted /data hence why you can't boot in your OS anymore...
Flashing custom software (recovery, roms, kernels) requires an unlocked bootloader (like you already know) but booting custom softwares also requires an unlocked bootloader, that's why you can't access twrp anymore now that it'S relocked, even if it's still there on your phone.
Flash the 7.19.707.151 RUU, your phone will be back to 100% stock and from there you'll be able to unlock your bootloader again, flash twrp and a rom. There is a sticky thread in the general section (lolliopop ruu collection), you'll find instructions how to flash the ruu there.
Click to expand...
Click to collapse
Hello Alray
Thank you for the suggestion, the problem is i can only use fastboot USB and nothing else as it is not allowing me. any suggestions how i can flash .zip ruu. some times it says signature error. and also am getting this ROM 7.21.707.105 is this not good, i am new to this post and was unable to find the one you suggested.

Categories

Resources