[Q]Problems during flashing stock ROM on HTC One M8 - Android Q&A, Help & Troubleshooting

Update: Fixed. Please delete thread.
Hi guys,
I have an HTC One M8 which was rooted, with TWRP and running CM 12, S-ON. I just wanted to put the stock ROM back on it, I don't care about the flags that says that the software is modified or anything like that.
For that I followed this thread.
Step 1: lock the bootloader. -> this worked. The status is now RELOCKED. ***Software modified***
Trying to flash TWRP doesn't work though, neither is the device listed through adb, bellow what I get in the command prompt.
C:\miniadb_m8> fastboot flash recovery openrecovery-twrp-2.8.4.0-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (16092 KB)...
OKAY [ 1.740s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.321s
C:\miniadb_m8>adb devices
List of devices attached
C:\miniadb_m8>fastboot devices
xxxx fastboot
I looked up the RUU for my devices based on the information I got back by using fastboot getvar all and came across another post on this forum for my device (HTC__038) and tried flashing that RUU.zip file, bellow the output.
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.013s]
finished. total time: 0.013s
C:\adb>htc_fastboot flash zip RUU.zip
sending 'zip'... (53966 KB) OKAY
sending time = 2.648 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
Execution time is 8(s).
I can't get around this, was wondering if someone can point me in the right direction, based on my device info:
C:\miniadb_m8>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxx
(bootloader) imei: xxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any help is appreciated, thanks a lot.
Cheers,
Adrian

Related

[Q] S-Off, but a locked bootloader.

Here's the life story of my phone as far as tampering with the system files.
HTC Dev Unlock to get an unlocked bootloader
Flashed TWRP to my recovery partition
Made a backup, but I think I just included the default partitions and no more no less.
Flashed SuperSU
Used Rumrunner S-Off for AT&T 3.17.502.3 successfully
In preparation for AR31, I attempted to flash the 3.63.X.X firmware.zip, and failed miserably. One person later pointed out that it was because I was using the wrong model. Here's the log:
Code:
C:\adb>adb reboot bootloader
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4230mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.075s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.048s]
finished. total time: 0.050s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.497s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.915s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.520s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.941s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.040s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.090s
C:\adb>fastboot oem writecid 11111111
...
(bootloader) Start Verify: 0
(bootloader) Input CID is super CID
(bootloader) Start Verify: 0
OKAY [ 0.082s]
finished. total time: 0.082s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.041s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.084s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.505s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.540s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.040s
After that failed, I decided I was just going to forget about it (as it was optional and I didn't want to risk anything worse than an error message), and instead, install Android Revolution by itself instead. As I entered my bootloader, I was greeted by *TAMPERED* / *LOCKED*. The bootloader was still S-OFF, so I assumed I could install AR31 regardless. It worked, but as I'm preparing to flash the proper firmware.zip from http://forum.xda-developers.com/showthread.php?t=2485651, it is a bit worrying to me. I already tried fastboot flash Unlock_code.bin so that I could just unlock the bootloader again and restore from the previous backup, but it refused to do so and gave me an error.
Anyways, with the information out there, should I even be worried about this considering I have S-Off? In either case, how do I solve the situation? It's a little worrying to me.
FreeK200 said:
Here's the life story of my phone as far as tampering with the system files.
HTC Dev Unlock to get an unlocked bootloader
Flashed TWRP to my recovery partition
Made a backup, but I think I just included the default partitions and no more no less.
Flashed SuperSU
Used Rumrunner S-Off for AT&T 3.17.502.3 successfully
In preparation for AR31, I attempted to flash the 3.63.X.X firmware.zip, and failed miserably. One person later pointed out that it was because I was using the wrong model. Here's the log:
Code:
C:\adb>adb reboot bootloader
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4230mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.075s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.048s]
finished. total time: 0.050s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.497s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.915s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.520s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.941s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.040s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.090s
C:\adb>fastboot oem writecid 11111111
...
(bootloader) Start Verify: 0
(bootloader) Input CID is super CID
(bootloader) Start Verify: 0
OKAY [ 0.082s]
finished. total time: 0.082s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.041s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.084s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.505s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.540s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.040s
After that failed, I decided I was just going to forget about it (as it was optional and I didn't want to risk anything worse than an error message), and instead, install Android Revolution by itself instead. As I entered my bootloader, I was greeted by *TAMPERED* / *LOCKED*. The bootloader was still S-OFF, so I assumed I could install AR31 regardless. It worked, but as I'm preparing to flash the proper firmware.zip from http://forum.xda-developers.com/showthread.php?t=2485651, it is a bit worrying to me. I already tried fastboot flash Unlock_code.bin so that I could just unlock the bootloader again and restore from the previous backup, but it refused to do so and gave me an error.
Anyways, with the information out there, should I even be worried about this considering I have S-Off? In either case, how do I solve the situation? It's a little worrying to me.
Click to expand...
Click to collapse
it failed because you where not in ruu mode here is a great guide for firmware flashing
http://forum.xda-developers.com/showthread.php?t=2316726
jerrycoffman45 said:
it failed because you where not in ruu mode here is a great guide for firmware flashing
http://forum.xda-developers.com/showthread.php?t=2316726
Click to expand...
Click to collapse
I believe I was in RUU mode. If you look in the log, I used "fastboot oem rebootRUU" prior to trying to flash the firmware, and I had the black background with a silver htc logo when I attempted this as well. In either case, unless I'm missing something entirely, I already realize that I did that incorrectly (trying to flash firmware with the wrong model ID), and I already have the correct firmware with the correct model id waiting. What I'm looking for though is for a solution to unlock my bootloader again. Somewhere along this process, my bootloader went from Unlocked to locked, and I didn't have anything to do with it aside from the failed flashes on the firmware. In no way, shape or form, did I even attempt to lock my bootloader again, so when I was preparing to flash the AR31 rom, it came as a surprise that it was locked.
FreeK200 said:
I believe I was in RUU mode. If you look in the log, I used "fastboot oem rebootRUU" prior to trying to flash the firmware, and I had the black background with a silver htc logo when I attempted this as well. In either case, unless I'm missing something entirely, I already realize that I did that incorrectly (trying to flash firmware with the wrong model ID), and I already have the correct firmware with the correct model id waiting. What I'm looking for though is for a solution to unlock my bootloader again. Somewhere along this process, my bootloader went from Unlocked to locked, and I didn't have anything to do with it aside from the failed flashes on the firmware. In no way, shape or form, did I even attempt to lock my bootloader again, so when I was preparing to flash the AR31 rom, it came as a surprise that it was locked.
Click to expand...
Click to collapse
Since you're s-off, you should be able to unlock using the process outlined here (http://forum.xda-developers.com/showthread.php?t=2475914)

[Q] I think I bricked my phone

While trying to get S-Off on about every method I could, and reflashing RUU. I think I bricked it.
What happened was that I attempted to relock the phone. (fastboot oem lock), so I could reflash back to stock.
I'd done this already without any issues. But this time, when I did, it got stuck on booting to the boot loader. It wouldn't boot into recovery nor into the ROM. After about an hour, I finally got it to boot again. However, The only way I could do this was to flash the unlock token.
The issue here is now that when it boots into the fastboot bootloader, it shows some graphical issues and refuse to take the RUU, even when manually flashing it.
D:\One_All-In-One_Kit_v\rumrunner_HTC_0.5.0>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.035s]
finished. total time: 0.035s
D:\One_All-In-One_Kit_v\rumrunner_HTC_0.5.0>fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1180758 KB)...
OKAY [ 42.850s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 143.395s
Click to expand...
Click to collapse
I'd done this previosly to revert to stock without issues, not an hour before.
fastboot getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36DW903729
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4267mV
(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!
finished. total time: 0.056s
Click to expand...
Click to collapse
The phone is currently on Android 4.4.2, Sense 5.5, stock.
The RUU I'm using is:
RUU_M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2(2)
I have the OTA zip for 4.4.2, as well as the firmware.zip from it.
None of it works, and all errors up with the above error.
And no, I don't have S-Off.
Additionally, when connecting to fasboot USB, it does some screen tearing, distorting the text. I suspect that I've damaged the firmware and the phone is basically a brick. It does boot, but I cannot reflash the RUU.

[SOLVED] "Unfortunately,Nfc Service has stopped." Help!

So I bought and HTC One M7 of Swappa and the phone came with the "Unfortunately, Nfc Service has stopped" pop up upon turning on, the phone has been factory reset by the previous owner. No matter how many times I press the "Ok" button, the pop up comes right back up. This means that I am unable to do anything that would require me to navigate the phone. So no access to dev options which means no usb debugging . I can't run rumrunner because that requires usb debugging and I'm stuck with a locked bootloader, s-on, and i always get the same
(bootloader) [ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.009s
error message
and I've tried to flash the correct ruu files with no luck. I always get the same
C:\Users\tranny\Desktop\HTC One\Fastboot>fastboot flash zip Rom.zip
sending 'zip' (1516464 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.688s
error message.
I'm lost and have no idea what to do.:crying:
Here is the getvar
C:\Users\tranny\Desktop\HTC One\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(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: 4137mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.053s
Thanks in advance for any and all help!!!
soleved: unlocked dev mode between pop up messages

my DX's Model ID is blank ?

i have a DX and i tried up some RÓMs
But now i can't boot my phone and it has vibrated 7 times when i turned on / boot to bootloader
I relocked bootloader
I install RUU.zip but it had error
sending 'zip' (375648 KB)...
OKAY [ 35.104s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 107.404s
Click to expand...
Click to collapse
i checked var and here is
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: UNKNOWN SHIP S-ON
(bootloader) serialno: u+næg"öa6ü?¡S+?
(bootloader) imei: 358835
(bootloader) meid:
(bootloader) product: proto
(bootloader) platform: HBOOT-8225
(bootloader) modelid: ¦ò£e¦˜ªñ(Éè·-Q-~=¼-Q)¼=p±/ `oj\±
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-f3c065d3
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.009s
Click to expand...
Click to collapse
My serial and model id is invalid and now i can't unlock bootloader.
please help me
Sorry dude. It most probably is bricked. I had same problem and only fix was another motherboard.
Sent from my HTC Desire X using XDA Free mobile app

my DX's Model ID is blank ?

i have a DX and i tried up some RÓMs
But now i can't boot my phone and it has vibrated 7 times when i turned on / boot to bootloader
I relocked bootloader
I install RUU.zip but it had error
sending 'zip' (375648 KB)...
OKAY [ 35.104s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 107.404s
Click to expand...
Click to collapse
i checked var and here is
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: UNKNOWN SHIP S-ON
(bootloader) serialno: u+næg"öa6ü?¡S+?
(bootloader) imei: 358835045727473
(bootloader) meid:
(bootloader) product: proto
(bootloader) platform: HBOOT-8225
(bootloader) modelid: ¦ò£e¦˜ªñ(Éè·-Q-~=¼-Q)¼=p±/ `oj\±
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-f3c065d3
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.009s
Click to expand...
Click to collapse
My serial and model id is invalid and now i can't unlock bootloader.
please help me

Categories

Resources