I can't flash anything.
Well....Almost, I do have CM10 "working" No camera at the moment, I think I can find cam drivers to push, but I don't intend to stay JB.
I'm wondering if the CID may be incorrect (it's a bestbuy refurb...my last insurance replacement) but I haven't messed with that on any of my previous phones.
I gave up after several failed RUU.exe fixes and grabbed "rom.zip" from the %temp% folder while it was loaded. Here is my fastboot session:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>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.170s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.040s]
finished. total time: 0.040s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip Rom.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th
e block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th
e block size 4096
OKAY [112.640s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 226.710s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th
e block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th
e block size 4096
OKAY [ 82.260s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 196.330s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip Rom.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th
e block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 81416344 is not a multiple of th
e block size 4096
OKAY [ 80.333s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 194.897s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Bootloader After That:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-1.01.20.1225
OpenDSP-v35.120.274.0718
OS-6.23.651.7
eMMC-boot 2048 MB
Aug 13 2015, 12:15:24.0
Click to expand...
Click to collapse
I resent my HTC bootloader unlock token, CWM loaded.
Just to be thorough, here is CWM recovery when I try to flash:
-- Installing: /sdcard/0/Download/rom.zip
Finding update package...
Opening update package...
Installing update...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
E:Error in data/media/0/Download/rom.zip
(Status 0)
Installation aborted
Click to expand...
Click to collapse
I'm thinking maybe I somehow destroyed the file system? But now that I'm back to a "working" CM10 backup it looks fine in Root Explorer.
Is this possible in recovery? Would flashing the RUU not just rebuild everything?? Isn't that the point of HTC's RUU?
I, of course, lost the one stock backup that I had, but I can make and restore backups from this CM10 flash I have going.
I'm thinking that I need a backup from another M7spr to try (or a factory system .img I can fastboot, but that seems not to exist)
If it would help I can upload both rom.zips ... there was a discrepancy in file sizes.
As stated, both were pulled from the %temp% folder while RUU updater was running.
Previously,
cm-10.2-20131214-SNAPSHOT-InstallerWPPQ50S-m7spr-signed.zip is all that would even flash, I can't load gapps and camera drivers are apparently borked. (I tried taking a shot of the eclipse last night) - I tried Viper, CM 11 & 12 and a PA rom, all fail to flash in recovery. Well, CM12 worked with the CM recovery but I had zero APNs loaded. ...now I wish that I would have stuck that out.
Okay Seriously...WTH?!
Here is my getvar in fastboot:
(vivid)[email protected]:~$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [][][][][][][][][][][][]
(bootloader) imei: [][][][][][][][][][][][][][][]
(bootloader) meid: [][][][][][][][][][][][][][]
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4004mV
(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
all: Done!
finished. total time: 0.037s
Click to expand...
Click to collapse
"cidnum" is SPCS_001...anything else I'm missing?!
Circular Pastry said:
Okay Seriously...WTH?!
Here is my getvar in fastboot:
"cidnum" is SPCS_001...anything else I'm missing?!
Click to expand...
Click to collapse
Get as far away from CWM as possible....that's your issue.
Fastboot flash the latest TWRP for your device and you should have much better results on current roms.
CWM is pretty much deprecated.
Sent from my HTC6535LVW using Tapatalk
santod040 said:
Get as far away from CWM as possible....that's your issue.
Fastboot flash the latest TWRP for your device and you should have much better results on current roms.
CWM is pretty much deprecated.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
So...
just to show that my noob level hadn't completely reset completely, I HAD tried TWRP....it seriously did the stupid thing where it "locked" and then wouldn't respond to my swipe. ...ASSuming that the troubles of CWM from years gone by had run their course (thinking, hey...who's this Phill Z guy?) I just thought screw it, I pushed CWM and have been beating my head against the wall ever since.
Wrong. I pushed a clean dl of TWRP, I have Android L back up, and now I'm back to playing with the M7.
Thanks santod040 ...I'm an idiot!
Related
Hi everyone:
I previously posted about my silly 77% battery percentage problem. . So the advice I heard from most people is to revert to stock completely.
Tengo un AT&T M7 HTC One.
So I tried downloading:
1) RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
2) RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe
and running them on Windows; neither one worked. Usually just quit; or 170 errored out.
older rommmmm: sudo fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1029872 KB)...
OKAY [ 41.245s]
writing 'zip'...
(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 (Value too large for defined data type))
finished. total time: 52.616s
Next I tried manually extracting the rom.zip and flashing it as follows:
older rommmmm: sudo fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1029872 KB)...
OKAY [ 41.245s]
writing 'zip'...
(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 (Value too large for defined data type))
finished. total time: 52.616s
....
So I'm a little at a loss for what to do now?
arooni said:
Hi everyone:
I previously posted about my silly 77% battery percentage problem. . So the advice I heard from most people is to revert to stock completely.
Tengo un AT&T M7 HTC One.
So I tried downloading:
1) RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
2) RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe
and running them on Windows; neither one worked. Usually just quit; or 170 errored out.
older rommmmm: sudo fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1029872 KB)...
OKAY [ 41.245s]
writing 'zip'...
(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 (Value too large for defined data type))
finished. total time: 52.616s
Next I tried manually extracting the rom.zip and flashing it as follows:
older rommmmm: sudo fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1029872 KB)...
OKAY [ 41.245s]
writing 'zip'...
(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 (Value too large for defined data type))
finished. total time: 52.616s
....
So I'm a little at a loss for what to do now?
Click to expand...
Click to collapse
1- post the output of ''fastboot getvar all'' excluding imei and serialno
2- have you checked MD5 value of both ruu beofre flashing them?
alray said:
1- post the output of ''fastboot getvar all'' excluding imei and serialno
2- have you checked MD5 value of both ruu beofre flashing them?
Click to expand...
Click to collapse
[sudo] password for david:
(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.1540.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: aserial#
(bootloader) imei: animei#
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4284mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
and yes... checked md5sum before any flash attempts
Change your CID to BS_US001 and try this one on windows http://www.androidruu.com/getdownlo...3_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe
I'm trying to flash an RUU for my HTC One but it keeps failing. It is a Rogers phone, I'm flashing a Rogers RUU. This is the RUU I'm using:
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
When I try to run the exe, it gets stuck at step 1/5 checking headers. I've extracted the rom.zip file and tried to flash with fastboot but that fails also. This is what I'm getting:
Code:
e:\Swap>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
e:\Swap>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 190479322 is not a multiple of t
he block size 4096
sending sparse 'zip' (1490937 KB)...
error: write_sparse_skip_chunk: don't care size 190479322 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 190479322 is not a multiple of t
he block size 4096
OKAY [ 49.636s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 49.831s
e:\Swap>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 190438362 is not a multiple of t
he block size 4096
sending sparse 'zip' (1490937 KB)...
error: write_sparse_skip_chunk: don't care size 190438362 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 190438362 is not a multiple of t
he block size 4096
OKAY [ 49.670s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 49.866s
Here is my fastboot getvar all:
Code:
e:\Swap>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.22.631.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
I have tried with my original CID ROGER001 and superCID. Any assistance would be greatly appreciated!
Cyotik said:
I'm trying to flash an RUU for my HTC One but it keeps failing. It is a Rogers phone, I'm flashing a Rogers RUU. This is the RUU I'm using:
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
When I try to run the exe, it gets stuck at step 1/5 checking headers. I've extracted the rom.zip file and tried to flash with fastboot but that fails also. This is what I'm getting:
Code:
e:\Swap>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
e:\Swap>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 190479322 is not a multiple of t
he block size 4096
sending sparse 'zip' (1490937 KB)...
error: write_sparse_skip_chunk: don't care size 190479322 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 190479322 is not a multiple of t
he block size 4096
OKAY [ 49.636s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 49.831s
e:\Swap>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 190438362 is not a multiple of t
he block size 4096
sending sparse 'zip' (1490937 KB)...
error: write_sparse_skip_chunk: don't care size 190438362 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 190438362 is not a multiple of t
he block size 4096
OKAY [ 49.670s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 49.866s
Here is my fastboot getvar all:
Code:
e:\Swap>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.22.631.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
I have tried with my original CID ROGER001 and superCID. Any assistance would be greatly appreciated!
Click to expand...
Click to collapse
you need to flash the firmware first when using 4.xx.xxx.x RUUs. Then the ruu will flash fine, its a common bug for all 4.xx.xxx.x ruu, must be on 4.xx.xxx.x firmware before flashing.
Btw, imo, I would change my cid to BS_US001 and flash the latest dev edition ruu (6.07.1540.2) instead of flashing the 4.19.631.9 Rogers version which mean you'll be up to date, receive the next ota faster and have no Rogers bloatwares.
alray said:
you need to flash the firmware first when using 4.xx.xxx.x RUUs. Then the ruu will flash fine, its a common bug for all 4.xx.xxx.x ruu, must be on 4.xx.xxx.x firmware before flashing.
Btw, imo, I would change my cid to BS_US001 and flash the latest dev edition ruu (6.07.1540.2) instead of flashing the 4.19.631.9 Rogers version which mean you'll be up to date, receive the next ota faster and have no Rogers bloatwares.
Click to expand...
Click to collapse
Okay, I changed CID and flashed firmware 6.06.401.1 from this thread. Here is fastboot getvar all now:
Code:
e:\Swap\dev>fastboot getvar all
(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.06.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(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: 4292mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
Still not able to flash the RUU though, I used the rom.zip from the dev edition RUU you recommended.
Code:
e:\Swap\dev>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.042s]
finished. total time: 0.042s
e:\Swap\dev>fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 98606579 is not a multiple of th
e block size 4096
sending sparse 'zip' (1478649 KB)...
error: write_sparse_skip_chunk: don't care size 98606579 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 98606579 is not a multiple of th
e block size 4096
OKAY [ 49.111s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 49.327s
e:\Swap\dev>fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 97504755 is not a multiple of th
e block size 4096
sending sparse 'zip' (1478649 KB)...
error: write_sparse_skip_chunk: don't care size 97504755 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 97504755 is not a multiple of th
e block size 4096
OKAY [ 49.090s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 49.298s
Cyotik said:
Okay, I changed CID and flashed firmware 6.06.401.1 from this thread. Here is fastboot getvar all now:
Code:
e:\Swap\dev>fastboot getvar all
(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.06.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(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: 4292mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
Still not able to flash the RUU though, I used the rom.zip from the dev edition RUU you recommended.
Code:
e:\Swap\dev>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.042s]
finished. total time: 0.042s
e:\Swap\dev>fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 98606579 is not a multiple of th
e block size 4096
sending sparse 'zip' (1478649 KB)...
error: write_sparse_skip_chunk: don't care size 98606579 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 98606579 is not a multiple of th
e block size 4096
OKAY [ 49.111s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 49.327s
e:\Swap\dev>fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 97504755 is not a multiple of th
e block size 4096
sending sparse 'zip' (1478649 KB)...
error: write_sparse_skip_chunk: don't care size 97504755 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 97504755 is not a multiple of th
e block size 4096
OKAY [ 49.090s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 49.298s
Click to expand...
Click to collapse
Why did you flashed the 6.06.401.1 firmware?.
6.06.401.1 is not even for Rogers or Dev edition, its European (.401)
If using the dev edition RUU then flash the Dev edition firmware first (6.07.1540.2).
If using the Rogers RUU then flash the Roger firmware first (4.19.631.9).
---------- Post added at 12:55 AM ---------- Previous post was at 12:52 AM ----------
Or maybe it would be simpler for you to use one of my reset rom to flash in twrp recovery? I can guide you if needed, i'll still be online for the next 2 hours.
was running stock android with unlocked bootloader. wanted to install cm. used wugfresh nrt and rooted and installed twrp. then used twrp to flash cm and open gapps. everything did just fine. was running cm.
then found out i was not rooted?. then followed this video https://www.youtube.com/watch?v=84D2-UnUIA4&t=38s to root.
ended up bricking? i can get to the start screen by entering bootloader mode but whenever i choose any option ....
start, restart bootloader, recovery mode, factory, etc.. nothing happens
i am able to use platform tools and run the command fastboot devices and it is listed.
i am getting failures when trying to run flash-all.bat and flash recovery
This is what i get when i try the flash-all.bat
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 0.456s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.733s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 3.788s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.009s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) current-slot: not found
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
target reported max download size of 536870912 bytes
(bootloader) has-slot:boot: not found
archive does not contain 'boot.sig'
(bootloader) has-slot:recovery: not found
archive does not contain 'recovery.sig'
(bootloader) has-slot:system: not found
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
wiping userdata...
Creating filesystem with parameters:
Size: 59743535104
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14585824
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3646496 inodes and 274946/14585824 blocks
wiping cache...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-72.00
Baseband Version.....: D4.01-9625-05.42+FSG-9625-02.113
Serial Number........: REDACTED
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is 'moto-apq8084-72.00'.
Update requires 'moto-apq8084-72.01'.
finished. total time: 0.020s
Press any key to exit...
This is what i get when i try to run fastboot flash recovery twrp.img
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'twrp.img'
C:\Program Files (x86)\Android\android-sdk\platform-tools>
it says on the bottom of the screen..........
AP Fastboot flash mode secure
BI info
Baseband info
Product/Variant info
Serial Number info
CPU info
eMMC info
DRAM info
Console [Null]
Battery OK charging
Device is UNLOCKED Status Code 3
Transfer Mode: USB Connected
Am i screwed? Seems like i should be able to flash twrp to have a recovery and then flash another rom.
TIA,
johnboyinfl
If you're unlocked you can't be bricked.... Just flash the latest factory image and start all over..
I never use the flash all script, i flash all files individually. You can also use Nexus Root Toolkit to flash the image.
[email protected] said:
was running stock android with unlocked bootloader. wanted to install cm. used wugfresh nrt and rooted and installed twrp. then used twrp to flash cm and open gapps. everything did just fine. was running cm.
then found out i was not rooted?. then followed this video https://www.youtube.com/watch?v=84D2-UnUIA4&t=38s to root.
ended up bricking? i can get to the start screen by entering bootloader mode but whenever i choose any option ....
start, restart bootloader, recovery mode, factory, etc.. nothing happens
i am able to use platform tools and run the command fastboot devices and it is listed.
i am getting failures when trying to run flash-all.bat and flash recovery
This is what i get when i try the flash-all.bat
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
... TRUNCATED.
Click to expand...
Click to collapse
This is the point where it went south.
Am i screwed? Seems like i should be able to flash twrp to have a recovery and then flash another rom.
Click to expand...
Click to collapse
I think you're screwed. It messed up your partition table (that's what GPT is), AND in doing so probably destroyed the data that it had to "backup and restore".
There is a possibility that if you try a few more times to flash the bootloader (just the bootloader, DO NOT use flash-all.bat), and are able to get it successfully written, then you may be able to follow that with the rest of the partitions, but I wouldn't count on it.
Also, try this from a LINUX box. Windows is a bloated mess and introduces a lot of unknown variables. More bloat and more variables = less certainty of a successful outcome. In fact, I would NEVER suggest trying fastboot from windows, since you stand a much higher chance of sending corrupt data across the line. Unlike update.zip's, fastboot does NOT validate the data integrity.
---------- Post added at 03:52 PM ---------- Previous post was at 03:50 PM ----------
blanco2701 said:
If you're unlocked you can't be bricked.... Just flash the latest factory image and start all over..
Click to expand...
Click to collapse
OF COURSE you can brick an unlocked device!
All you have to do is delete part of the bootloader, and then you can no longer boot to fastboot.
I never use the flash all script, i flash all files individually. You can also use Nexus Root Toolkit to flash the image.
Click to expand...
Click to collapse
NEVER use anything that is called a "root toolkit".
There is nothing special about root, it is as easy to add root as running "fastboot flash boot boot.img"
i have tried multiple times to just flash the bootloader and still no luck. i would say i am screwed. just went out and bought something cheap because i am getting ready to head away for the holidays. not sure what i might get myself after the holiday.
thanks for the help.
johnboyinfl
might have made some progress.... not sure... this is where i am at after multiple attempts flashing just the bootloader...
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-shamu-moto-apq8084-72.01.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT entries.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 0.462s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
----------------------------------------------------------
TIA
johnboyinfl
[email protected] said:
might have made some progress.... not sure... this is where i am at after multiple attempts flashing just the bootloader...
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-shamu-moto-apq8084-72.01.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT entries.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 0.462s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
----------------------------------------------------------
TIA
johnboyinfl
Click to expand...
Click to collapse
If you are flashing all of the factory images (.img) files manually, what happens if you try the following commands? This will wipe your device completely. NOTE: Each line below is just one command.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot reboot
update...
i think i am still out of luck.... failed to write primary GPT....
Doesn't look good.
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 0.451s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.634s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 14.629s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) current-slot: not found
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
target reported max download size of 536870912 bytes
(bootloader) has-slot:boot: not found
archive does not contain 'boot.sig'
(bootloader) has-slot:recovery: not found
archive does not contain 'recovery.sig'
(bootloader) has-slot:system: not found
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
wiping userdata...
Creating filesystem with parameters:
Size: 59777200128
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14594043
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3653632 inodes and 275392/14594043 blocks
wiping cache...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
TIA
johnboyinfl
RMarkwald said:
If you are flashing all of the factory images (.img) files manually, what happens if you try the following commands? This will wipe your device completely. NOTE: Each line below is just one command.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>cd C:\Program Files (x86)\Android\android-sdk\platform-tools\
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
ZX1G325LRV fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase boot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
erasing 'boot'...
(bootloader) Erase allowed in unlocked state
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.005s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.005s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase recovery
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.006s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase system
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Erase allowed in unlocked state
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.006s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.004s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-shamu-moto-apq8084-72.01
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
error: cannot load 'bootloader-shamu-moto-apq8084-72.01'
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash radio radio-shamu-d4.01-9625-05.42+fsg-9625-02.113
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
error: cannot load 'radio-shamu-d4.01-9625-05.42+fsg-9625-02.113'
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
error: cannot load 'boot.img'
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'recovery.img'
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash cache cache.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
error: cannot load 'cache.img'
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
I've not done this with Windows and use linux but I've run into issues with fastboot if I don't run it as root. Try it again running fastboot as an administrator in Windows in case there are permission problems.
Also, show the output of fastboot getvar all.
Did you unlock the bootloader? fastboot oem unlock
How about booting directly into twrp?
fastboot boot recovery twrp-3.0.3-0-shamu.img
If you can do this you might be able to use a flashable image or perhaps for erase some partitions.
You in trouble son...
There is a restore brick thread... Where it talks about blankflashing...
Start there...
May the force be with you...
hi Guys
I'm in the forum for a very long time as an assistant helper now it has got me hard I have an Axon 10 Pro with curly boot loader and trying to flash a TWRP I have somehow the device or SotA and SlotB have shrunk. The Axon Bootet permanently in 0.5 second cycle and also a FULL Restot or FULL Flash with EDL Tool has not changed anything. Likewise, a new flash about fastboot with the command (fastboot flash boot_a boot.img) the same for boot_b then try with fastboot command (fastboot boot twrp.img) Recovery to start without success fastboot erase boot_a and boot_b has also flashing new but it does not start. Always bootloop
Shogunes said:
hi Guys
I'm in the forum for a very long time as an assistant helper now it has got me hard I have an Axon 10 Pro with curly boot loader and trying to flash a TWRP I have somehow the device or SotA and SlotB have shrunk. The Axon Bootet permanently in 0.5 second cycle and also a FULL Restot or FULL Flash with EDL Tool has not changed anything. Likewise, a new flash about fastboot with the command (fastboot flash boot_a boot.img) the same for boot_b then try with fastboot command (fastboot boot twrp.img) Recovery to start without success fastboot erase boot_a and boot_b has also flashing new but it does not start. Always bootloop
Click to expand...
Click to collapse
Wrong Forum check here.
Hey guys, What's up?
Some months ago, my friend suggested that he can upgrade my phone to Lollipop and instal another ROM...after that, my phone is so so buggy! It's always crashing, constantly rebooting and many others problems.
So, I decided to go back to the Stock ROM, but it's seems a little difficult to me.
Can anyone please help me get my phone back to Stock ROM?
Tell me what to do first and help me find the right files for my phone?
Here it's the info about my phone:
C:\Fastboot>fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA362W900989
(bootloader) imei: 354436052980347
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3848mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Thanks alot!!!
EliSoares said:
Hey guys, What's up?
Some months ago, my friend suggested that he can upgrade my phone to Lollipop and instal another ROM...after that, my phone is so so buggy! It's always crashing, constantly rebooting and many others problems.
So, I decided to go back to the Stock ROM, but it's seems a little difficult to me.
Can anyone please help me get my phone back to Stock ROM?
Tell me what to do first and help me find the right files for my phone?
Here it's the info about my phone:
Thanks alot!!!
Click to expand...
Click to collapse
Flashing the 7.19.401.51 RUU will bring your phone back to stock
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
follow instructions from post #1
RUU at post #2
alray said:
Flashing the 7.19.401.51 RUU will bring your phone back to stock
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
follow instructions from post #1
RUU at post #2
Click to expand...
Click to collapse
Hey! Thanks!!!
I'm trying do flash, but appears this error:
FAIL02 data length is too large
FAILED (data size is too large(1641983 KB) for device to download ZIP file 'RUU.
zip'
Click to expand...
Click to collapse
What i have to do ?
EliSoares said:
Hey! Thanks!!!
I'm trying do flash, but appears this error:
What i have to do ?
Click to expand...
Click to collapse
Make sure you are using the fastboot version provided by the OP and that you are using the signed version of 7.19.401.51 not the decrypted one.
Hi,
I bought the HTC One M7 from other person, I found the Software Information is:
- Android Version: 5.0.2
- HTC Sense Version: 6.0
- Software number: ViperOne 8.0.0
When I check the my bootloader variable is show below
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: SH39WW903924
(bootloader) imei: 35786**********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
How can I turn to the Stock ROM? Because of the the orginal "cidnum" was changed, so how to find the right Stock ROM with my device?
Please help me.
Thank you very much
NomercyB said:
Hi,
I bought the HTC One M7 from other person, I found the Software Information is:
- Android Version: 5.0.2
- HTC Sense Version: 6.0
- Software number: ViperOne 8.0.0
When I check the my bootloader variable is show below
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: SH39WW903924
(bootloader) imei: 35786**********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
How can I turn to the Stock ROM? Because of the the orginal "cidnum" was changed, so how to find the right Stock ROM with my device?
Please help me.
Thank you very much
Click to expand...
Click to collapse
You can pretty much use any RUU you'd like to brink it back to stock, just make sure the MID match the RUU. If you really need it to be on the same exact rom it came with, for an obscure reason, you canf ind the original CID stored on the MFG partition. You'll need to dump the MFG to your computer and explore it using HxD. Or simply flash the 7.19.401.51 RUU
CID stored on the MFG partition
alray said:
You can pretty much use any RUU you'd like to brink it back to stock, just make sure the MID match the RUU. If you really need it to be on the same exact rom it came with, for an obscure reason, you canf ind the original CID stored on the MFG partition. You'll need to dump the MFG to your computer and explore it using HxD. Or simply flash the 7.19.401.51 RUU
Click to expand...
Click to collapse
Thank you very @alray.
As you know I am a newbie on this issue, so I really don't know how to find CID stored on the MFG partition.
Could you give me your hand to how to find it?
Thank you.
NomercyB said:
Thank you very @alray.
As you know I am a newbie on this issue, so I really don't know how to find CID stored on the MFG partition.
Could you give me your hand to how to find it?
Thank you.
Click to expand...
Click to collapse
From a rooted rom or from a custom recovery execute theses commands:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bakup.img
exit
then copy mmcblk0p6_backup.img from your sdcard to your computer and open it with HxD, look at position 1209C
position 1209C
alray said:
From a rooted rom or from a custom recovery execute theses commands:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bakup.img
exit
then copy mmcblk0p6_backup.img from your sdcard to your computer and open it with HxD, look at position 1209C
Click to expand...
Click to collapse
Sorry, sir @alray I don't know how to find the position 1209C. When I press F3 on HxD and find the the 1209C it couldn't find, maybe I don't know how to find it, how should I do?
NomercyB said:
Sorry, sir @alray I don't know how to find the position 1209C. When I press F3 on HxD and find the the 1209C it couldn't find, maybe I don't know how to find it, how should I do?
Click to expand...
Click to collapse
scroll down to offset 12090 and then look at column 0C. That's the first byte of your original CID, most likely x48 for the letter "H" if your phone had a common CID (ie starting with HTC__)
Just after that, at 120AB you can find your MID.
btw you would be fine with 7.19.401.51, just saying again...
mmcblk0p6_bakup.img
alray said:
From a rooted rom or from a custom recovery execute theses commands:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bakup.img
exit
then copy mmcblk0p6_backup.img from your sdcard to your computer and open it with HxD, look at position 1209C
Click to expand...
Click to collapse
alray said:
scroll down to offset 12090 and then look at column 0C. That's the first byte of your original CID, most likely x48 for the letter "H" if your phone had a common CID (ie starting with HTC__)
Just after that, at 120AB you can find your MID.
btw you would be fine with 7.19.401.51, just saying again...
Click to expand...
Click to collapse
Thank you so much for you kindly guide me. My mmcblk0p6_bakup.img couldn't find the number 12090 as you mentioned.
Anyway, I downloaded Stock ROM Version 7.19.401.51, If I flash it my mobile can receive OTA update?
Flash Stock ROM 7.19.401.51
alray said:
scroll down to offset 12090 and then look at column 0C. That's the first byte of your original CID, most likely x48 for the letter "H" if your phone had a common CID (ie starting with HTC__)
Just after that, at 120AB you can find your MID.
btw you would be fine with 7.19.401.51, just saying again...
Click to expand...
Click to collapse
When I flash Stock ROM 7.19.401.51 I found the message below:
F:\HTC\HTCOneRoot\fastboot_adb(1.0.32)_071114_r21>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.043s]
finished. total time: 0.044s
F:\HTC\HTCOneRoot\fastboot_adb(1.0.32)_071114_r21>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 165469715 is not a multiple of the block size 4096
sending sparse 'zip' (1478649 KB)...
error: write_sparse_skip_chunk: don't care size 165469715 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 165469715 is not a multiple of the block size 4096
OKAY [ 58.964s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 59.169s
F:\HTC\HTCOneRoot\fastboot_adb(1.0.32)_071114_r21>fastboot reboot
rebooting...
finished. total time: 0.036s
How should I do?
NomercyB said:
Thank you so much for you kindly guide me. My mmcblk0p6_bakup.img couldn't find the number 12090 as you mentioned.
Anyway, I downloaded Stock ROM Version 7.19.401.51, If I flash it my mobile can receive OTA update?
Click to expand...
Click to collapse
Ota update? Device reached EOL Last year. 7.19.401.51 is the final version. I wouldnt expect any update but if there is one, yes youll be able to install it.
NomercyB said:
When I flash Stock ROM 7.19.401.51 I found the message below:
F:\HTC\HTCOneRoot\fastboot_adb(1.0.32)_071114_r21>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.043s]
finished. total time: 0.044s
F:\HTC\HTCOneRoot\fastboot_adb(1.0.32)_071114_r21>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 165469715 is not a multiple of the block size 4096
sending sparse 'zip' (1478649 KB)...
error: write_sparse_skip_chunk: don't care size 165469715 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 165469715 is not a multiple of the block size 4096
OKAY [ 58.964s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 59.169s
F:\HTC\HTCOneRoot\fastboot_adb(1.0.32)_071114_r21>fastboot reboot
rebooting...
finished. total time: 0.036s
How should I do?
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash the ruu, not the regular version from Google.
Flash Stock ROM 7.19.401.51
alray said:
Ota update? Device reached EOL Last year. 7.19.401.51 is the final version. I wouldnt expect any update but if there is one, yes youll be able to install it.
You must use htc_fastboot.exe to flash the ruu, not the regular version from Google.
Click to expand...
Click to collapse
Thank you very much for your good suggestion, I tried many times for flashing but it's not complete, I also used htc_fastboot.exe. Maybe it happens with my Windows OS.
I try again with Windows OS that is lower than Windows 10 Enterprise 64 bit.
NomercyB said:
Thank you very much for your good suggestion, I tried many times for flashing but it's not complete, I also used htc_fastboot.exe. Maybe it happens with my Windows OS.
I try again with Windows OS that is lower than Windows 10 Enterprise 64 bit.
Click to expand...
Click to collapse
With Hboot 1.57 windows 10 shouldn't be a problem, only if you were on hboot 1.44.
Can you copy/paste the output of your command windows after executing "fastboot flash zip ruu.zip" so I can see why it's failing...
Same problem
alray said:
With Hboot 1.57 windows 10 shouldn't be a problem, only if you were on hboot 1.44.
Can you copy/paste the output of your command windows after executing "fastboot flash zip ruu.zip" so I can see why it's failing...
Click to expand...
Click to collapse
I still face the same problem when I flash RUU.zip from the original file "PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_unsigned.zip". It shows the error message:
C:\HTC FASTBOOT>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.043s]
finished. total time: 0.044s
C:\HTC FASTBOOT>fastboot flash zip ruu.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 167235091 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 167235091 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 167235091 is not a multiple of t
he block size 4096
OKAY [ 93.787s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 93.991s
C:\HTC FASTBOOT>fastboot reboot-bootloader
Please help me to find out the problem.
Thank you very much
NomercyB said:
I still face the same problem when I flash RUU.zip from the original file "PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_unsigned.zip". It shows the error message:
C:\HTC FASTBOOT>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.043s]
finished. total time: 0.044s
C:\HTC FASTBOOT>fastboot flash zip ruu.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 167235091 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 167235091 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 167235091 is not a multiple of t
he block size 4096
OKAY [ 93.787s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 93.991s
C:\HTC FASTBOOT>fastboot reboot-bootloader
Please help me to find out the problem.
Thank you very much
Click to expand...
Click to collapse
Might want to try to signed version? Not sure why you are trying to flash this one.
alray said:
Might want to try to signed version? Not sure why you are trying to flash this one.
Click to expand...
Click to collapse
I will try to use signed version from you suggestion. You want to know why I am trying to use this one. Because I could not find out the original CID number and you ever suggested me to use 7.19.401.51 RUU, so I downloaded 7.19.401.51 RUU to flash my rom to restore to the stock ROM.
Okay, if you have any good solution to suggest me please help me to the stock ROM. The reason why I try to return to stock rom because my phone flashed with viper rom and now WIFI signal is stuck on "Turning WIFI on" then give the error message.
That's why, I would like to return to stock rom.
---------- Post added at 04:00 AM ---------- Previous post was at 03:01 AM ----------
alray said:
Might want to try to signed version? Not sure why you are trying to flash this one.
Click to expand...
Click to collapse
I tried with signed version but it still show the error as the message below
C:\HTC FASTBOOT>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.109s]
finished. total time: 0.109s
C:\HTC FASTBOOT>fastboot flash zip ruu.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 174325923 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 174325923 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 174325923 is not a multiple of t
he block size 4096
OKAY [106.361s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 106.564s
C:\HTC FASTBOOT>fastboot reboot
rebooting...
finished. total time: 0.109s
Please help me.
Thanks.
I've got an HTC One M7 on EE in the UK (was TMobile I think originally).
I flashed it with LineageOS, which seemed to work great except it didn't recognise the SIM card. I gather I'll need to S-OFF it first to unlock the SIM? And that Sunshine is the way to go for my 1.61 hboot version.
Despite flashing with a stock ROM though Sunshine's test complains the kernel or ROM aren't close enough to stock. Any ideas? Thanks in advance.
Code:
(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.19.61.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4194mV
(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
This is the stock RUU I've tried.
M7 CWM Nandroid Backup CID ORANG001 2.24.61.1
htconer said:
This is the stock RUU I've tried.
M7 CWM Nandroid Backup CID ORANG001 2.24.61.1
Click to expand...
Click to collapse
This file is not a RUU, it's a cwm backup and it's also way to old to fit your device.
I know 3 methods to sim-unlock,
1-the first one consist of entering the sim unlock code (you must purchase one) when booting the phone. The foreign sim card must be inserted to be prompted to enter the code, the phone must also run a stock (or close to stock) rom.
2- Sieempi's method, requires S-OFF and some hardware (external hard drive, usb otg y-cable, 5v power source)
3- Sunshine experimental sim-unlock, not really sure if it's working, never heard about anyone using this method.
The lastest RUU version I was able to find for your phone is 7.19.61.10 and since your version-main is higher than that you'll either need s-off to flash it or to edit your version-main in your misc partition.
https://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
RUU at post #2 of that thread, instructions how to edit your version-main at the end of post #2. Instructions how to flash ruu at post #1
Thanks.
Sounds like you'd suggest putting a foreign SIM in and getting an unlock code over Sunshine then? I guess if I can pass the Sunshine checks though I'll be in a better place for doing that.
The version-main change seems to have worked. Haven't been able to flash the RUU though, am I doing something wrong?
Code:
$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.235s]
finished. total time: 0.235s
$ fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Orange_UK_7.19.61.10_Radio_4T.35.3218.16_10.33Q.1718.01L_release_428118_signed.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 184138016 is not a multiple of the block size 4096
sending sparse 'zip' 1/2 (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 184138016 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 184138016 is not a multiple of the block size 4096
OKAY [ 60.996s]
writing 'zip' 1/2...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 202.278s
I've tried running the flash zip command multiple times. Thought it sounded like a file corruption issue, but the MD5 seems ok to me.
Code:
$ md5 PN07IMG_M7_UL_L50_SENSE60_MR_Orange_UK_7.19.61.10_Radio_4T.35.3218.16_10.33Q.1718.01L_release_428118_signed.zip
MD5 (PN07IMG_M7_UL_L50_SENSE60_MR_Orange_UK_7.19.61.10_Radio_4T.35.3218.16_10.33Q.1718.01L_release_428118_signed.zip) = 95a5ad2186235bc346d55ef9d8530dce
htconer said:
Thanks.
Sounds like you'd suggest putting a foreign SIM in and getting an unlock code over Sunshine then? I guess if I can pass the Sunshine checks though I'll be in a better place for doing that.
The version-main change seems to have worked. Haven't been able to flash the RUU though, am I doing something wrong?
Code:
$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.235s]
finished. total time: 0.235s
$ fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Orange_UK_7.19.61.10_Radio_4T.35.3218.16_10.33Q.1718.01L_release_428118_signed.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 184138016 is not a multiple of the block size 4096
sending sparse 'zip' 1/2 (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 184138016 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 184138016 is not a multiple of the block size 4096
OKAY [ 60.996s]
writing 'zip' 1/2...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 202.278s
Click to expand...
Click to collapse
Answer to your question is written in red in the instructions/post #1 of the RUU collection thread
You can buy a sim unlock code online for less than 10$ if you don't want to s-off with Sunshine.
Ah. Bit slow getting used to the expanding bits on this forums posts. Guess I need htc_fastboot.exe then?
Unfortunately, sort of, I don't have a Windows machine or know anyone with one I can borrow and the htc fastboot for mac complains the file is too big.