[Q] I think I bricked my phone - T-Mobile HTC One (M7)

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.

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)

Installed Cyanongen 11, Revert to stock and im stuck! AT&T HTC One M7 (Please Help!)

Installed Cyanongen 11, Revert to stock and im stuck! AT&T HTC One M7 (Please Help!)
Greetings,
I am in a predicament. I installed and used the cyanogenmod 11 beta installer because it looked very easy (and it was), all went well. But, I needed to revert back to stock to unlock my sim with a newly purchased sim unlock code, and I botched my phone in the process and I am stuck running in circles.
What I can do: Lock and Relock bootloader (with tampered and unlocked flags), flash a recovery.
What I can't do: everything else... ruu's fail, flashing fails, and it's a never ending circle.
I can't get S-OFF due to being stuck in the bootloader and while in recovery, I am unable to mount /cache, /system, etc. Nothing seems writeable and nothing seems to be able to flash or install. I have tried, fastboot oem rebootRUU, etc. I have tried sideloading... and everything else that I have read around the net.
Getvar:
(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: 1.00.000.0
(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: 4214mV
(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
When locking bootloader to attempt to RUU I get this:
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.110s
When launching RUU exe I get: ERROR [155]: UNKNOWN ERROR ( I Have tried several different RUU's)
Please help! I am without a phone and I am like a chicken with its head cut off right now...
Any help would be highly appreciated...
OCTechs said:
Greetings,
I am in a predicament. I installed and used the cyanogenmod 11 beta installer because it looked very easy (and it was), all went well. But, I needed to revert back to stock to unlock my sim with a newly purchased sim unlock code, and I botched my phone in the process and I am stuck running in circles.
What I can do: Lock and Relock bootloader (with tampered and unlocked flags), flash a recovery.
What I can't do: everything else... ruu's fail, flashing fails, and it's a never ending circle.
I can't get S-OFF due to being stuck in the bootloader and while in recovery, I am unable to mount /cache, /system, etc. Nothing seems writeable and nothing seems to be able to flash or install. I have tried, fastboot oem rebootRUU, etc. I have tried sideloading... and everything else that I have read around the net.
Getvar:
(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: 1.00.000.0
(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: 4214mV
(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
When locking bootloader to attempt to RUU I get this:
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.110s
When launching RUU exe I get: ERROR [155]: UNKNOWN ERROR ( I Have tried several different RUU's)
Please help! I am without a phone and I am like a chicken with its head cut off right now...
Any help would be highly appreciated...
Click to expand...
Click to collapse
Did you use this thread to downgrade your version main?
http://forum.xda-developers.com/showthread.php?t=2398717
I don't have experience with this but I wonder what recovery you should have before trying to relock bootloader. do you have custom recovery installed?
mb_guy said:
Did you use this thread to downgrade your version main?
http://forum.xda-developers.com/showthread.php?t=2398717
I don't have experience with this but I wonder what recovery you should have before trying to relock bootloader. do you have custom recovery installed?
Click to expand...
Click to collapse
Yes, I have tried. I will try again and post the results...
Results:
Code:
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT3********* recovery
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.115s
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>fastboot oem reboot
RUU
...
(bootloader) Start Verify: 3
OKAY [ 0.051s]
finished. total time: 0.052s
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>fastboot flash rom.
zip
unknown partition 'rom.zip'
error: cannot determine image filename for 'rom.zip'
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>fastboot flash zip
rom.zip
sending 'zip' (1029872 KB)...
OKAY [ 45.155s]
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: 146.955s
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>fastboot flash zip
rom.zip
sending 'zip' (1029872 KB)...
At this point.. I let it sit for 15 minutes and nothing happened.
I managed to flash a firmware provided by Android Revolution 4.06.1540.2.zip, renamed it to "firmware.zip" and was able to pull that off successfully (I think "see code below") but even after that, I tried to manually flash the rom.zip and install it via the exe and still no profit. :/
Code:
< waiting for device >
sending 'zip' (43288 KB)...
OKAY [ 2.976s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,24
(bootloader) [RUU]UZ,boot,35
(bootloader) [RUU]UZ,boot,47
(bootloader) [RUU]UZ,boot,59
(bootloader) [RUU]UZ,boot,72
(bootloader) [RUU]UZ,boot,82
(bootloader) [RUU]UZ,boot,93
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,6
(bootloader) [RUU]UZ,recovery,12
(bootloader) [RUU]UZ,recovery,21
(bootloader) [RUU]UZ,recovery,29
(bootloader) [RUU]UZ,recovery,38
(bootloader) [RUU]UZ,recovery,45
(bootloader) [RUU]UZ,recovery,50
(bootloader) [RUU]UZ,recovery,67
(bootloader) [RUU]UZ,recovery,75
(bootloader) [RUU]UZ,recovery,83
(bootloader) [RUU]UZ,recovery,88
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ..... Bypassed
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,6
(bootloader) [RUU]UZ,radio,12
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,24
(bootloader) [RUU]UZ,radio,30
(bootloader) [RUU]UZ,radio,37
(bootloader) [RUU]UZ,radio,43
(bootloader) [RUU]UZ,radio,49
(bootloader) [RUU]UZ,radio,55
(bootloader) [RUU]UZ,radio,62
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,74
(bootloader) [RUU]UZ,radio,81
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,93
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,24
(bootloader) [RUU]WP,radio,49
(bootloader) [RUU]WP,radio,74
(bootloader) [RUU]WP,radio,99
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,42949671
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,42949671
(bootloader) ...... Successful
OKAY [ 27.115s]
finished. total time: 30.095s
It did however change my GetVar slightly (below):
Code:
(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: 4276mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
OCTechs said:
I managed to flash a firmware provided by Android Revolution 4.06.1540.2.zip, renamed it to "firmware.zip" and was able to pull that off successfully (I think "see code below") but even after that, I tried to manually flash the rom.zip and install it via the exe and still no profit. :/
Code:
< waiting for device >
sending 'zip' (43288 KB)...
OKAY [ 2.976s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,24
(bootloader) [RUU]UZ,boot,35
(bootloader) [RUU]UZ,boot,47
(bootloader) [RUU]UZ,boot,59
(bootloader) [RUU]UZ,boot,72
(bootloader) [RUU]UZ,boot,82
(bootloader) [RUU]UZ,boot,93
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,6
(bootloader) [RUU]UZ,recovery,12
(bootloader) [RUU]UZ,recovery,21
(bootloader) [RUU]UZ,recovery,29
(bootloader) [RUU]UZ,recovery,38
(bootloader) [RUU]UZ,recovery,45
(bootloader) [RUU]UZ,recovery,50
(bootloader) [RUU]UZ,recovery,67
(bootloader) [RUU]UZ,recovery,75
(bootloader) [RUU]UZ,recovery,83
(bootloader) [RUU]UZ,recovery,88
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ..... Bypassed
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,6
(bootloader) [RUU]UZ,radio,12
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,24
(bootloader) [RUU]UZ,radio,30
(bootloader) [RUU]UZ,radio,37
(bootloader) [RUU]UZ,radio,43
(bootloader) [RUU]UZ,radio,49
(bootloader) [RUU]UZ,radio,55
(bootloader) [RUU]UZ,radio,62
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,74
(bootloader) [RUU]UZ,radio,81
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,93
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,24
(bootloader) [RUU]WP,radio,49
(bootloader) [RUU]WP,radio,74
(bootloader) [RUU]WP,radio,99
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,42949671
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,42949671
(bootloader) ...... Successful
OKAY [ 27.115s]
finished. total time: 30.095s
It did however change my GetVar slightly (below):
Code:
(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: 4276mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
Click to expand...
Click to collapse
I'd suggest you post here and see if @clsA thinks his rom will help you
http://forum.xda-developers.com/showthread.php?t=2674222
not sure now that you changed your firmware version and hboot is 1.56
mb_guy said:
I'd suggest you post here and see if @clsA thinks his rom will help you
http://forum.xda-developers.com/showthread.php?t=2674222
not sure now that you changed your firmware version and hboot is 1.56
Click to expand...
Click to collapse
Yea, I'll look into it but as far as having S-ON and 1.56, life seems really bleak.
(last time i'm using cyanogenrom) I can say that much.
clsA's custom rom says it needs to be installed in recovery, which isn't much of an option for me as it would have to be sideloaded,
which thus far has gotten me no-where.
I'm at a loss...
OCTechs said:
Yea, I'll look into it but as far as having S-ON and 1.56, life seems really bleak.
(last time i'm using cyanogenrom) I can say that much.
clsA's custom rom says it needs to be installed in recovery, which isn't much of an option for me as it would have to be sideloaded,
which thus far has gotten me no-where.
I'm at a loss...
Click to expand...
Click to collapse
What is your current recovery?
Is Your device a developer edition or stock at&t us
mb_guy said:
What is your current recovery?
Click to expand...
Click to collapse
I have tried:
openrecovery-twrp-2.6.3.3-m7.img
openrecovery-twrp-2.6.3.4-m7.img
recovery-clockwork-6.0.4.3-m7att.img
recovery-clockwork-touch-6.0.4.6-m7.img
and a few stock recoveries. The last flashed recovery was twrp 2.6.3.3. I can get into recovery, but nothing seems to work... such as mounting /cache, /system, etc. I can get sideload to work (sometimes) and have tried sideloading ruu's and stock roms and tried to install for zip, but no luck, everything fails.
I went from stock to Cyanogenrom 11 beta installer and it worked fine... but it never red flagged as "developer edition" S was never turned off (which was stupid on my part for not doing that first) before trying to RUU, which got me in this mess in the first place. As for it being stock or developer edition, I am not sure... I can unlock the bootloaded with the HTCDEV provided Unlock_code.bin, just fine. When executing "fastboot oem lock" it flags as a *tampered, relocked, and security warning".
OCTechs said:
I have tried:
openrecovery-twrp-2.6.3.3-m7.img
openrecovery-twrp-2.6.3.4-m7.img
recovery-clockwork-6.0.4.3-m7att.img
recovery-clockwork-touch-6.0.4.6-m7.img
and a few stock recoveries. The last flashed recovery was twrp 2.6.3.3. I can get into recovery, but nothing seems to work... such as mounting /cache, /system, etc. I can get sideload to work (sometimes) and have tried sideloading ruu's and stock roms and tried to install for zip, but no luck, everything fails.
I went from stock to Cyanogenrom 11 beta installer and it worked fine... but it never red flagged as "developer edition" S was never turned off (which was stupid on my part for not doing that first) before trying to RUU, which got me in this mess in the first place. As for it being stock or developer edition, I am not sure... I can unlock the bootloaded with the HTCDEV provided Unlock_code.bin, just fine. When executing "fastboot oem lock" it flags as a *tampered, relocked, and security warning".
Click to expand...
Click to collapse
That is normal behavior for bootloader flags. Is your bootloader now unlocked? I noticed a couple of posts back it was relocked. twrp and other custom recoveries need it unlocked to work.
The firmware you flashed is developer edition.
mb_guy said:
That is normal behavior for bootloader flags. Is your bootloader now unlocked? I noticed a couple of posts back it was relocked. twrp and other custom recoveries need it unlocked to work.
Click to expand...
Click to collapse
Yes, I can unlock and relock the bootloader by executing commands:
#fastboot oem lock
and
#fastboot flash unlocktoken Unlock_code.bin
I can install the recoveries once it's unlocked ofcourse, but I relock it in-order to try to RUU or install any sort of stock rom.
OCTechs said:
Yes, I can unlock and relock the bootloader by executing commands:
#fastboot oem lock
and
#fastboot flash unlocktoken Unlock_code.bin
I can install the recoveries once it's unlocked ofcourse, but I relock it in-order to try to RUU or install any sort of stock rom.
Click to expand...
Click to collapse
Why not reinstall twrp and try and sideload @clsA's rom. Or otg cable if you have.
OCTechs said:
Yes, I can unlock and relock the bootloader by executing commands:
#fastboot oem lock
and
#fastboot flash unlocktoken Unlock_code.bin
I can install the recoveries once it's unlocked ofcourse, but I relock it in-order to try to RUU or install any sort of stock rom.
Click to expand...
Click to collapse
Your really in panic mode it seems and your heading for disaster if you don't stop and listen.
First you don't relock to flash anything but a RUU
if you getting error on RUU your using the wrong one
you cid and MID are both stock AT&T ... simply flash the stock AT&T RUU
From your Second post
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 146.955s
Click to expand...
Click to collapse
This just means you used the wrong rom.zip .. if it's a decrypted RUU/ Rom.zip you need S-off to flash it.
Why have you kept flashing different recovery's ?
are you doing all the steps to flash recovery ?
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
then you simple sideload the rom of your choice ...
Are you MD5 checking all your downloads ?
here's the last AT&T RUU it should flash on your current setup (lock the bootloader first) >> http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
---------- Post added at 07:20 PM ---------- Previous post was at 07:17 PM ----------
mb_guy said:
Why not reinstall twrp and try and sideload @clsA's rom. Or otg cable if you have.
Click to expand...
Click to collapse
this would seem the simple choice .. but if he has never cleared the cache from fastboot everything will fail. He also mention trying to mount things in recovery ??? I have never once mounted anything in recovery except my usb-otg device.
clsA said:
Your really in panic mode it seems and your heading for disaster if you don't stop and listen.
First you don't relock to flash anything but a RUU
if you getting error on RUU your using the wrong one
you cid and MID are both stock AT&T ... simply flash the stock AT&T RUU
From your Second post
This just means you used the wrong rom.zip .. if it's a decrypted RUU/ Rom.zip you need S-off to flash it.
Why have you kept flashing different recovery's ?
are you doing all the steps to flash recovery ?
then you simple sideload the rom of your choice ...
Are you MD5 checking all your downloads ?
here's the last AT&T RUU it should flash on your current setup (lock the bootloader first) >> http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
---------- Post added at 07:20 PM ---------- Previous post was at 07:17 PM ----------
this would seem the simple choice .. but if he has never cleared the cache from fastboot everything will fail. He also mention trying to mount things in recovery ??? I have never once mounted anything in recovery except my usb-otg device.
Click to expand...
Click to collapse
Yes, you are 100% right and can sense my tension via chat, lol. I'm freaking out, kinda. Because, I am certain that I screwed up...
Here is where I went wrong (I started fresh on my girlfriends phone which is identical to mine "she has 1.55 though"), I didn't realize Cyanogenrom's > settings > Superuser > settings > "Apps & ADB" (allow access), So when I tried to S-OFF with Rumrunner, it failed because of this... and I was unable to achieve S-OFF. I wasn't thinking and attempted to flash a RUU and everything botched. Now it seems like my phone is stuck in bootloader and a halfway working recovery menu due to the permissions and being unable to mount anything. I have been trying to use the (above RUU) file and it fails and errors out while running the exe. I have taken the "rom.zip" out of the file and attempted to flash that but since it's S-ON it fails.
You have given me hope though, on the fact that "i didn't md5 verify" the downloads and it could possibly be fixed. So that's good news, and I honestly thank you for being here for me man.
OCTechs said:
Yes, you are 100% right and can sense my tension via chat, lol. I'm freaking out, kinda. Because, I am certain that I screwed up...
Here is where I went wrong (I started fresh on my girlfriends phone which is identical to mine "she has 1.55 though"), I didn't realize Cyanogenrom's > settings > Superuser > settings > "Apps & ADB" (allow access), So when I tried to S-OFF with Rumrunner, it failed because of this... and I was unable to achieve S-OFF. I wasn't thinking and attempted to flash a RUU and everything botched. Now it seems like my phone is stuck in bootloader and a halfway working recovery menu due to the permissions and being unable to mount anything. I have been trying to use the (above RUU) file and it fails and errors out while running the exe. I have taken the "rom.zip" out of the file and attempted to flash that but since it's S-ON it fails.
You have given me hope though, on the fact that "i didn't md5 verify" the downloads and it could possibly be fixed. So that's good news, and I honestly thank you for being here for me man.
Click to expand...
Click to collapse
you can flash rom zip .. just not decrypted rom zip
what error did you get with the at&t ruu rom.zip ?
it helps if I can see you command screens for possible errors
the normal procedure to recover from CM 11 is to just flash stock recovery to your phone and do a factory reset with the stock recovery ... then flash TWRP / clear cache / factory reset in twrp and sideload a rom
clsA said:
what error did you get with the at&t ruu rom.zip ?
Click to expand...
Click to collapse
Primarily this error: FAILED (status read failed (Too many links)) when attempting to ruu the rom.zip
clsA said:
you can flash rom zip .. just not decrypted rom zip
the normal procedure to recover from CM 11 is to just flash stock recovery to your phone and do a factory reset with the stock recovery ... then flash TWRP / clear cache / factory reset in twrp and sideload a rom
Click to expand...
Click to collapse
What stock recovery we be best to flash?
And what are the commands in order to sideload the rom from TWRP?
# adb sideload rom.zip ?
Should this automatically begin the installation procedure for the rom?
Or, will I have to attempt to "install from zip" in twrp afterwards?
When I tried to clear cache in twrp, I would get a failed flag "unable to mount /cache" etc.
and it basically did nothing, and it would fail when trying to mount it in twrp.
Update:
When trying to "factory reset" in twrp 2.6.3.3 it Failed.
Code:
E: unable to mount '/cache'
OCTechs said:
What stock recovery we be best to flash?
And what are the commands in order to sideload the rom from TWRP?
# adb sideload rom.zip ?
Should this automatically begin the installation procedure for the rom?
Or, will I have to attempt to "install from zip" in twrp afterwards?
When I tried to clear cache in twrp, I would get a failed flag "unable to mount /cache" etc.
and it basically did nothing, and it would fail when trying to mount it in twrp.
Click to expand...
Click to collapse
the recovery from you current version number is the one you want
you can extract it from a decrypted rom.zip
being your on kitkat this one should work
http://d-h.st/71m
TWRP / Advanced / Sideload
From PC adb /fastboot folder
you use
adb sideload rom.zip
clsA said:
the recovery from you current version number is the one you want
you can extract it from a decrypted rom.zip
being your on kitkat this one should work
http://d-h.st/71m
TWRP / Advanced / Sideload
From PC adb /fastboot folder
you use
adb sideload rom.zip
Click to expand...
Click to collapse
After installing the stock recovery (and trying to access it) it gives me the recycling symbol for a moment, then it bootloops with the HTC logo... So I factory reset within the bootloader, cleared cache, reboot-bootloader, installed twrp 2.6.3.0, cleared cache, reboot-bootloader, and im going to attempt to install the ruu exe from the above post, if that fails, then i'll try to sideload.
Success! Im very happy now... Two days running in circles and 2am ers... I got it to work!
I thank you very much man and I owe you big time bro.
I will post my steps on what I did from start to finish so maybe down the line it will help someone else out.

[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

[Q]Problems during flashing stock ROM on HTC One M8

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

Categories

Resources