Hi all,
Excuse my poor english.
I want to upgarde my firmware with 1.17.401.3.zip and I have no Wifi, no signal, nothing.
I try to swipe all and I want install (I think) the true firmware: 1.17.401.1.zip
At this time, I have nothing, no system and I cannot boot.
I have access at recovery TWRP, I can send files with adb push and that's it.
I'm blocked now. I want to install the firmware 1.17.401.1.zip with
Code:
fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.101s
D:\HTC One X+>fastboot oem rebootRUU
...
(bootloader) Save data from original MSC...
(bootloader) Save data from SIF...
(bootloader) Update partition data to SIF partition
(bootloader) Update partition data from original MSC...
(bootloader) [MSG] OKAY
OKAY [ 0.193s]
finished. total time: 0.194s
D:\HTC One X+>fastboot flash zip firmware.zip
sending 'zip' (13262 KB)...
OKAY [ 1.658s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
[B]FAILED (remote: 43 main version check fail)[/B]
finished. total time: 2.600s
D:\HTC One X+>fastboot reboot
I receive "FAILED (remote: 43 main version check fail".
Do you have a solution for me ?
Thanks a lot.
Jack
Related
Hello,
How do I upgrade my Radio on my DNA. The screenshots shows what I have in my bootloader screen. Please help me. Thanks
Trying to flash
envy270 said:
Hello,
How do I upgrade my Radio on my DNA. The screenshots shows what I have in my bootloader screen. Please help me. Thanks
Click to expand...
Click to collapse
This is what I get when I am trying to flash firmware:
C:\android-sdk-windows\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (33119 KB)...
OKAY [ 2.587s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.799s
My phone's Wi Fi is stuck at "turning on" and I have random reboots every once and a while so I'm trying to to reset the phone to get it working again. I did a factory reset through the Android OS a couple times before this and it didn't fix it either.
I followed the instructions here:
http://forum.xda-developers.com/showthread.php?t=2612740
I installed the latest hboot, radio and recovery using the instructions provided.
Here's the output.
Code:
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip PL83IMG_3.06_hboot.zip
target reported max download size of 1514139648 bytes
sending 'zip' (558 KB)...
OKAY [ 0.200s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.252s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip PL83IMG_3.06_Radio.zip
target reported max download size of 1514139648 bytes
sending 'zip' (18052 KB)...
OKAY [ 1.773s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 4.771s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip PL83IMG_3.06_Recovery.zip
target reported max download size of 1514139648 bytes
sending 'zip' (11248 KB)...
OKAY [ 1.204s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.122s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.043s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.038s]
finished. total time: 0.039s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip 306_firmware_part1.zip
target reported max download size of 1514139648 bytes
sending 'zip' (14638 KB)...
OKAY [ 1.486s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 3.134s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.043s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip 306_firmware_part2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (40276 KB)...
OKAY [ 2.611s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 8.396s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip 306_firmware_part2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (40276 KB)...
OKAY [ 2.605s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 8.387s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip SENSE_5_RUU_ROM.zip
target reported max download size of 1514139648 bytes
sending 'zip' (920285 KB)...
OKAY [ 30.591s]
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: 1602.307s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
As you can see from the output, when I try to do the RUU, it fails. After letting it sit at "(bootloader) Read zipped android_info fail" for 20 minutes I disconnected the phone, rebooted it and tried it again, same result.
I also re-downloaded the RUU zip in case it was corrupted.
Why is it failing?
shortstop20 said:
My phone's Wi Fi is stuck at "turning on" and I have random reboots every once and a while so I'm trying to to reset the phone to get it working again. I did a factory reset through the Android OS a couple times before this and it didn't fix it either.
I followed the instructions here:
http://forum.xda-developers.com/showthread.php?t=2612740
I installed the latest hboot, radio and recovery using the instructions provided.
Here's the output.
Code:
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip PL83IMG_3.06_hboot.zip
target reported max download size of 1514139648 bytes
sending 'zip' (558 KB)...
OKAY [ 0.200s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.252s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip PL83IMG_3.06_Radio.zip
target reported max download size of 1514139648 bytes
sending 'zip' (18052 KB)...
OKAY [ 1.773s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 4.771s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip PL83IMG_3.06_Recovery.zip
target reported max download size of 1514139648 bytes
sending 'zip' (11248 KB)...
OKAY [ 1.204s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.122s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.043s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.038s]
finished. total time: 0.039s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip 306_firmware_part1.zip
target reported max download size of 1514139648 bytes
sending 'zip' (14638 KB)...
OKAY [ 1.486s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 3.134s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.043s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip 306_firmware_part2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (40276 KB)...
OKAY [ 2.611s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 8.396s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip 306_firmware_part2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (40276 KB)...
OKAY [ 2.605s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 8.387s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip SENSE_5_RUU_ROM.zip
target reported max download size of 1514139648 bytes
sending 'zip' (920285 KB)...
OKAY [ 30.591s]
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: 1602.307s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
As you can see from the output, when I try to do the RUU, it fails. After letting it sit at "(bootloader) Read zipped android_info fail" for 20 minutes I disconnected the phone, rebooted it and tried it again, same result.
I also re-downloaded the RUU zip in case it was corrupted.
Why is it failing?
Click to expand...
Click to collapse
I'm in the same boat. I'm on the OTA 4.4.2 with the new radio and hboot. I'm trying to revert back to 3.06 hboot(1.54) and keep getting the same error message you're getting. I want to RUU back to stock 4.2.2 so I can unlock and s-off again and THEN use the OTA packages that has been posted. I got ahead of myself when 4.4.2 came out and now I can't unlock or s-off until I can get the 3.06 hboot flashed.
abwilder0221 said:
I'm in the same boat. I'm on the OTA 4.4.2 with the new radio and hboot. I'm trying to revert back to 3.06 hboot(1.54) and keep getting the same error message you're getting. I want to RUU back to stock 4.2.2 so I can unlock and s-off again and THEN use the OTA packages that has been posted. I got ahead of myself when 4.4.2 came out and now I can't unlock or s-off until I can get the 3.06 hboot flashed.
Click to expand...
Click to collapse
I just want my damn Wi Fi to work and for the phone to quit rebooting randomly! Haha. :crying:
shortstop20 said:
My phone's Wi Fi is stuck at "turning on" and I have random reboots every once and a while so I'm trying to to reset the phone to get it working again. I did a factory reset through the Android OS a couple times before this and it didn't fix it either.
I followed the instructions here:
http://forum.xda-developers.com/showthread.php?t=2612740
I installed the latest hboot, radio and recovery using the instructions provided.
Here's the output.
Code:
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip PL83IMG_3.06_hboot.zip
target reported max download size of 1514139648 bytes
sending 'zip' (558 KB)...
OKAY [ 0.200s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.252s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip PL83IMG_3.06_Radio.zip
target reported max download size of 1514139648 bytes
sending 'zip' (18052 KB)...
OKAY [ 1.773s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 4.771s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip PL83IMG_3.06_Recovery.zip
target reported max download size of 1514139648 bytes
sending 'zip' (11248 KB)...
OKAY [ 1.204s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.122s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.043s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.038s]
finished. total time: 0.039s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip 306_firmware_part1.zip
target reported max download size of 1514139648 bytes
sending 'zip' (14638 KB)...
OKAY [ 1.486s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 3.134s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.043s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip 306_firmware_part2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (40276 KB)...
OKAY [ 2.611s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 8.396s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip 306_firmware_part2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (40276 KB)...
OKAY [ 2.605s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 8.387s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip SENSE_5_RUU_ROM.zip
target reported max download size of 1514139648 bytes
sending 'zip' (920285 KB)...
OKAY [ 30.591s]
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: 1602.307s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
As you can see from the output, when I try to do the RUU, it fails. After letting it sit at "(bootloader) Read zipped android_info fail" for 20 minutes I disconnected the phone, rebooted it and tried it again, same result.
I also re-downloaded the RUU zip in case it was corrupted.
Why is it failing?
Click to expand...
Click to collapse
Rename the Hboot file to PL83IMG ONLY
make sure those files on your adb folder don't be like PL83IMG.zip
the Zip extension on Windows is hidden so if you rename adding zip at the end will be zip.zip
finanandroid said:
Rename the Hboot file to PL83IMG ONLY
make sure those files on your adb folder don't be like PL83IMG.zip
the Zip extension on Windows is hidden so if you rename adding zip at the end will be zip.zip
Click to expand...
Click to collapse
Like this? I don't see any difference in the output.
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip PL83IMG.zip
target reported max download size of 1514139648 bytes
sending 'zip' (558 KB)...
OKAY [ 0.201s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.252s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
shortstop20 said:
Like this? I don't see any difference in the output.
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip PL83IMG.zip
target reported max download size of 1514139648 bytes
sending 'zip' (558 KB)...
OKAY [ 0.201s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.252s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
Click to expand...
Click to collapse
Make sure you have enable USB debugging and fastboot disable
Put your phone on Fastboot USb mode
make sure you have the files on your adb folder
shift + Right click inside your adb folder> Open command windows here
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip firmware1.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip firmware2.zip
fastboot flash zip firmware2.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot reboot
However note if you are flashing the firmwares those already have the Hboot 3.06
ready to RUU 3.06.
finanandroid said:
Make sure you have enable USB debugging and fastboot disable
Put your phone on Fastboot USb mode
make sure you have the files on your adb folder
shift + Right click inside your adb folder> Open command windows here
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip firmware1.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip firmware2.zip
fastboot flash zip firmware2.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot reboot
However note if you are flashing the firmwares those already have the Hboot 3.06
ready to RUU 3.06.
Click to expand...
Click to collapse
When I use the command "adb reboot bootloader" I get "error: device not found. I am in fastboot USB mode, fast boot is turned off. USB debugging is on(in the GUI, is there a way to turn it on/off in the fastboot USB mode?). The adb files are in the same location as my fastboot files and the .zip files. That location is: C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools
finanandroid said:
Make sure you have enable USB debugging and fastboot disable
However note if you are flashing the firmwares those already have the Hboot 3.06
ready to RUU 3.06.
Click to expand...
Click to collapse
I'm not sure what you mean by this. It seems everything is going smoothly until I try to do the RUU.
shortstop20 said:
When I use the command "adb reboot bootloader" I get "error: device not found. I am in fastboot USB mode, fast boot is turned off. USB debugging is on(in the GUI, is there a way to turn it on/off in the fastboot USB mode?). The adb files are in the same location as my fastboot files and the .zip files. That location is: C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools
Click to expand...
Click to collapse
usb debugging is ok have to be on checked
setting>about phone>software info>more>build number tap seven time to unhide developer tab
back to setting look for developer tab> usb debugging
CD : Adb Devices should giving your phone S number
like FA769O9898, if not you have a not working adb
change usb port
update adb
---------- Post added at 10:41 PM ---------- Previous post was at 10:37 PM ----------
shortstop20 said:
I'm not sure what you mean by this. It seems everything is going smoothly until I try to do the RUU.
Click to expand...
Click to collapse
try to download the 3.06 RUU Exe it run by itself
just put this Ruu exe not the Rom.zip in the same adb folder
connect your phone usb pc, right click as administrator and wait...
but you have to have ADB working
type adb devices to see your phone serial number
RUU EXE
https://docs.google.com/file/d/0B32gqnbh2ZecYTlvV1dlZTVRS0E/edit?pli=1
Reboot into bootloader to see what Hboot version you have installed
---------- Post added at 11:16 PM ---------- Previous post was at 10:41 PM ----------
shortstop20 said:
I'm not sure what you mean by this. It seems everything is going smoothly until I try to do the RUU.
Click to expand...
Click to collapse
meant in the output file that you posted seems
that you ran the firmware=new hboot
and you as well ran the PL83IMG_3.06_hboot.zip
or you flash the new firmwares or the new hboot but not both
OK, I didn't realize I need to have the RUU .EXE in my adb folder.
I'm downloading the RUU and I will try that.
I do see my phone listed when I type "adb devices".
I followed your instructions but the ZIP RUU failed again at the same spot.. I will try the EXE.
The RUU EXE failed as well.
shortstop20 said:
I followed your instructions but the ZIP RUU failed again at the same spot.. I will try the EXE.
Click to expand...
Click to collapse
Recall before to run the RUU.exe check your bootloader to see the hboot version
have to be 1.54.0000 in order to run it. if not update hboot http://forum.xda-developers.com/devdb/project/dl/?id=4888
if you hboot match right click the RUU.exe and run it as administrator.
finanandroid said:
Recall before to run the RUU.exe check your bootloader to see the hboot version
have to be 1.54.0000 in order to run it. if not update hboot http://forum.xda-developers.com/devdb/project/dl/?id=4888
if you hboot match right click the RUU.exe and run it as administrator.
Click to expand...
Click to collapse
That's the file I've been trying to flash all this time but my phone says I have hboot 1.57.
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.039s]
finished. total time: 0.040s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash zip PL83IMG.zip
target reported max download size of 1514139648 bytes
sending 'zip' (558 KB)...
OKAY [ 0.201s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.253s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
shortstop20 said:
That's the file I've been trying to flash all this time but my phone says I have hboot 1.57.
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.039s]
finished. total time: 0.040s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash zip PL83IMG.zip
target reported max download size of 1514139648 bytes
sending 'zip' (558 KB)...
OKAY [ 0.201s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.253s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
Click to expand...
Click to collapse
Are you S-off ? unlocked?
You can not Run 3.06 Ruu with the hboot 1.57.
flash stock Rom http://forum.xda-developers.com/showthread.php?t=2560010
finanandroid said:
Are you S-off ? unlocked?
You can not Run 3.06 Ruu with the hboot 1.57.
flash stock Rom http://forum.xda-developers.com/showthread.php?t=2560010
Click to expand...
Click to collapse
This is a completely stock phone. No S-off, no boot loader, stock ROM(4.4.2)
shortstop20 said:
My phone's Wi Fi is stuck at "turning on" and I have random reboots every once and a while so I'm trying to to reset the phone to get it working again. I did a factory reset through the Android OS a couple times before this and it didn't fix it either.
I followed the instructions here:
http://forum.xda-developers.com/showthread.php?t=2612740
I installed the latest hboot, radio and recovery using the instructions provided.
Here's the output.
Code:
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip PL83IMG_3.06_hboot.zip
target reported max download size of 1514139648 bytes
sending 'zip' (558 KB)...
OKAY [ 0.200s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.252s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip PL83IMG_3.06_Radio.zip
target reported max download size of 1514139648 bytes
sending 'zip' (18052 KB)...
OKAY [ 1.773s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 4.771s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip PL83IMG_3.06_Recovery.zip
target reported max download size of 1514139648 bytes
sending 'zip' (11248 KB)...
OKAY [ 1.204s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.122s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.043s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.038s]
finished. total time: 0.039s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip 306_firmware_part1.zip
target reported max download size of 1514139648 bytes
sending 'zip' (14638 KB)...
OKAY [ 1.486s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 3.134s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.043s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip 306_firmware_part2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (40276 KB)...
OKAY [ 2.611s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 8.396s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip 306_firmware_part2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (40276 KB)...
OKAY [ 2.605s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 8.387s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot reboot
-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem re
bootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.042s]
finished. total time: 0.042s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
zip SENSE_5_RUU_ROM.zip
target reported max download size of 1514139648 bytes
sending 'zip' (920285 KB)...
OKAY [ 30.591s]
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: 1602.307s
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
C:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
As you can see from the output, when I try to do the RUU, it fails. After letting it sit at "(bootloader) Read zipped android_info fail" for 20 minutes I disconnected the phone, rebooted it and tried it again, same result.
I also re-downloaded the RUU zip in case it was corrupted.
Why is it failing?
Click to expand...
Click to collapse
The reason might be your phone already updated with the latest firmware. (>3.06).
Fastboot screen will show the current version of you mobile firmware and OS. Have a look into it.
if the firmware is updated to latest version already, you need to downgrade it before flashing OTA: 3.06.605.4.
shortstop20 said:
This is a completely stock phone. No S-off, no boot loader, stock ROM(4.4.2)
Click to expand...
Click to collapse
Unfortunately You will have to wait for the RUU.exe (coming soon) for hboot 1.57.0000 because security is lock down
wont let you to downgrade to hboot 1.54.0000
factory reset then go to wifi advanced>change the wifi frequency band from auto to 2.4 only restart the phone
trying to down grade my dna
Can someone help me i got my droid dna and im getting some problems i i will like to return the phone to stock i try runnung ruu buy it fails i get error 155 someone say is my h oot i got hboot 1.57 and they told me i had to downgrade to hboot 1.54 or lower i dont how to do that if someone would help me how to do it im s-off runni g 4.4.2 KitKat.
azteca1 said:
Can someone help me i got my droid dna and im getting some problems i i will like to return the phone to stock i try runnung ruu buy it fails i get error 155 someone say is my h oot i got hboot 1.57 and they told me i had to downgrade to hboot 1.54 or lower i dont how to do that if someone would help me how to do it im s-off runni g 4.4.2 KitKat.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2935556
Oh can flash the provided hboot to successfully flash the ruu in that thread.
Sent from my HTC6500LVW using XDA Free mobile app
I'm fourteen, so ignore any absence of knowledge about any of this. I'm using a stock, non-rooted DNA running android 4.4.2.
So, I've been spending today trying to unlock my DNA's bootloader. I found this nifty program Moonshine, so I decided to use it. On the forum post for the moonshine it told me in order to use it for the DNA I had to flash the 2.06 firmware. This is what it gave me...
c:\Android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.041s
c:\Android\sdk\platform-tools>fastboot flash zip dna2.06firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (33119 KB)...
OKAY [ 2.664s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 8.543s
So, any help would be appreciated.
In DNA General, there is a thread titled, "Am I too late to root", it has all the info you will need.
Swantexan said:
In DNA General, there is a thread titled, "Am I too late to root", it has all the info you will need.
Click to expand...
Click to collapse
I'll check it out, thanks.
[Q] Stock ROM will not flash to device due to "remote: data length is too large"
Today I felt adventurous and decided to flash CyanogenMod 12 to my device. Everything went just fine and it was up and running. After about 3 hours of playing around I decided to go back to stock. This is where the problems arose. I downloaded the ROM from Google and ran the flash-all.sh file but it failed because the system partition was not large enough. I fiddled around until I gave up and decided to flash CyanogenMod back. I downloaded the recovery image as dictated by this article: wiki.cyanogenmod[dot]org/w/Install_CM_for_flounder and when I ran "fastboot flash recover openrecovery-twrp-2.8.4.0-flounder.img" in the terminal this was the output:
Code:
target reported max download size of 518205818 bytes
sending 'recover' (13116 KB)...
OKAY [ 0.813s]
writing 'recover'...
(bootloader) Device State : Unlocked
FAILED (remote: partition does not exist!)
finished. total time: 1.235s
I fully understood that flashing ROMs would void warranty and could brick my device and it seems I have paid the consequences. If it is of any help my boot loader is currently unlocked. If any of you could help me solve this problem I would be elated. I do not view myself as computer illiterate so I will do all that is asked of me and if necessary I can post more information, thanks!
Turns out I forgot a single y in recovery. Now I have a problem that when I run the flash-all.sh script provided by Google in the Stock ROM it fails:
Code:
[email protected]:~/Downloads/volantis-lrx22c$ ./flash-all.sh
< waiting for device >
target reported max download size of 518205818 bytes
sending 'bootloader' (2970 KB)...
OKAY [ 0.209s]
writing 'bootloader'...
(bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.249s]
finished. total time: 5.459s
rebooting into bootloader...
OKAY [ 0.021s]
finished. total time: 0.021s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.43.0.0114
Baseband Version.....: N/A
Serial Number........: XXXXXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7812 KB)...
OKAY [ 0.600s]
writing 'boot'...
(bootloader) Device State : Unlocked
OKAY [ 0.734s]
sending 'recovery' (8434 KB)...
OKAY [ 0.616s]
writing 'recovery'...
(bootloader) Device State : Unlocked
OKAY [ 0.751s]
erasing 'system'...
OKAY [ 0.899s]
sending 'system' (1771684 KB)...
[B]FAILED (remote: data length is too large)[/B]
finished. total time: 3.627s
Any help on this?
Flash each image individually.
Lokke9191 said:
Flash each image individually.
Click to expand...
Click to collapse
^^^Yep. This is what I did back in December... And it eventually worked.
---
Hi, @weenercow...
As I remember it, fastboot flashing system.img was problematic, to say the least. My laptop didn't immediateely respond to the command...
Code:
fastboot flash system system.img
...for a good 10 minutes or so.
I was also was getting a lot of <target reported max download size of 518205818> errors, with other fastboot flashed partitions (recovery, data, vendor, etc).
But they did get 'sent' and accordingly 'written' without problems.
It was system.ing that was problematic....
It seems, that due the size of the system.img (1.68Gb), it gets split up into 'chunks' and sent and written in pieces.
---
Anyhow, take a look at my (rather longish) post here, which documents my experiences, and the sort of thing you **might** expect to see...
http://forum.xda-developers.com/showpost.php?p=57272090&postcount=25
---
Good luck, and hope this helps.
Rgrds,
Ged.
I had a similar problem and I had to update my sdk and or fastboot to newer versions. I was running a very old version that didn't allow for larger file sizes.
when i reboot it , it can't open
i was unlock BootLoader，
all 7.11 system image was been recovery, not useful
reboot it
your device is it can not be trusted and may not to work properly
visit this link on an other device
g.co/ABH
press power to pause boot
ADB command code
C:\ADB>flash-all
Sending 'bootloader' (2901 KB) OKAY [ 0.212s]
Writing 'bootloader' (bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.463s]
Finished. Total time: 5.684s
rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.040s
< waiting for any device >
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 3.50.0.0143
Baseband Version.....: N/A
Serial Number........: HT4ADJT01784
--------------------------------------------
Checking product OKAY [ 0.003s]
Checking version-bootloader OKAY [ 0.004s]
extracting boot.img (8 MB) to disk... took 0.027s
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting recovery.img (10 MB) to disk... took 0.033s
archive does not contain 'recovery.sig'
extracting system.img (1453 MB) to disk... took 8.673s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (122 MB) to disk... took 0.785s
archive does not contain 'vendor.sig'
Couldn't parse erase-block-size '0xUnknown command'.
Couldn't parse logical-block-size '0xUnknown command'.
F2FS-tools: mkfs.f2fs Ver: 1.10.0 (2018-01-30)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is disabled
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 53714944 (26228 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: Overprovision ratio = 1.240%
Info: Overprovision segments = 328 (GC reserved = 169)
Info: format successful
Couldn't parse erase-block-size '0xUnknown command'.
Couldn't parse logical-block-size '0xUnknown command'.
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: 177cbd32-7522-11e8-8a10-bd7422ec86f1
Superblock backups stored on blocks:
32768
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'boot' (8636 KB) OKAY [ 0.552s]
Writing 'boot' (bootloader) Device State : Unlocked
OKAY [ 0.829s]
Sending 'recovery' (11204 KB) OKAY [ 0.662s]
Writing 'recovery' (bootloader) Device State : Unlocked
OKAY [ 0.946s]
Sending sparse 'system' 1/4 (478340 KB) OKAY [ 24.143s]
Writing sparse 'system' 1/4 (bootloader) Device State : Unlocked
OKAY [ 20.047s]
Sending sparse 'system' 2/4 (468227 KB) OKAY [ 23.647s]
Writing sparse 'system' 2/4 (bootloader) Device State : Unlocked
OKAY [ 19.934s]
Sending sparse 'system' 3/4 (499117 KB) FAILED (command write failed (Unknown error))
Finished. Total time: 108.734s
Press any key to exit...
can anybaby help me？ how to fix it？
my English not good。
夏默秋殇 said:
when i reboot it , it can't open
i was unlock BootLoader，
all 7.11 system image was been recovery, not useful
reboot it
your device is it can not be trusted and may not to work properly
visit this link on an other device
g.co/ABH
press power to pause boot
ADB command code
C:\ADB>flash-all
Sending 'bootloader' (2901 KB) OKAY [ 0.212s]
Writing 'bootloader' (bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.463s]
Finished. Total time: 5.684s
rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.040s
< waiting for any device >
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 3.50.0.0143
Baseband Version.....: N/A
Serial Number........: HT4ADJT01784
--------------------------------------------
Checking product OKAY [ 0.003s]
Checking version-bootloader OKAY [ 0.004s]
extracting boot.img (8 MB) to disk... took 0.027s
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting recovery.img (10 MB) to disk... took 0.033s
archive does not contain 'recovery.sig'
extracting system.img (1453 MB) to disk... took 8.673s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (122 MB) to disk... took 0.785s
archive does not contain 'vendor.sig'
Couldn't parse erase-block-size '0xUnknown command'.
Couldn't parse logical-block-size '0xUnknown command'.
F2FS-tools: mkfs.f2fs Ver: 1.10.0 (2018-01-30)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is disabled
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 53714944 (26228 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: Overprovision ratio = 1.240%
Info: Overprovision segments = 328 (GC reserved = 169)
Info: format successful
Couldn't parse erase-block-size '0xUnknown command'.
Couldn't parse logical-block-size '0xUnknown command'.
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: 177cbd32-7522-11e8-8a10-bd7422ec86f1
Superblock backups stored on blocks:
32768
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'boot' (8636 KB) OKAY [ 0.552s]
Writing 'boot' (bootloader) Device State : Unlocked
OKAY [ 0.829s]
Sending 'recovery' (11204 KB) OKAY [ 0.662s]
Writing 'recovery' (bootloader) Device State : Unlocked
OKAY [ 0.946s]
Sending sparse 'system' 1/4 (478340 KB) OKAY [ 24.143s]
Writing sparse 'system' 1/4 (bootloader) Device State : Unlocked
OKAY [ 20.047s]
Sending sparse 'system' 2/4 (468227 KB) OKAY [ 23.647s]
Writing sparse 'system' 2/4 (bootloader) Device State : Unlocked
OKAY [ 19.934s]
Sending sparse 'system' 3/4 (499117 KB) FAILED (command write failed (Unknown error))
Finished. Total time: 108.734s
Press any key to exit...
can anybaby help me？ how to fix it？
my English not good。
Click to expand...
Click to collapse
Have you tried flashing images 1 at a time? Fastboot flash system system.img
Fastboot flash vendor vendor.img
Etc.
madbat99 said:
Have you tried flashing images 1 at a time? Fastboot flash system system.img
Fastboot flash vendor vendor.img
Etc.
Click to expand...
Click to collapse
yes ，the code
C:\ADB>fastboot flash bootloader bootloader-flounder-3.50.0.0143.img
Sending 'bootloader' (2901 KB) OKAY [ 0.210s]
Writing 'bootloader' (bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.447s]
Finished. Total time: 5.677s
C:\ADB>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.040s
C:\ADB>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.026s]
Finished. Total time: 0.027s
C:\ADB>fastboot flash boot boot.img
Sending 'boot' (8622 KB) OKAY [ 0.520s]
Writing 'boot' (bootloader) Device State : Unlocked
OKAY [ 0.834s]
Finished. Total time: 1.356s
C:\ADB>fastboot flash system system.img
Sending sparse 'system' 1/4 (478340 KB) OKAY [ 24.182s]
Writing sparse 'system' 1/4 (bootloader) Device State : Unlocked
OKAY [ 19.999s]
Sending sparse 'system' 2/4 (468231 KB) OKAY [ 23.622s]
Writing sparse 'system' 2/4 (bootloader) Device State : Unlocked
OKAY [ 19.938s]
Sending sparse 'system' 3/4 (499117 KB) FAILED (command write failed (Unknown error))
Finished. Total time: 95.634s
C:\ADB>fastboot flash cache cache.img
Sending 'cache' (6248 KB) OKAY [ 0.349s]
Writing 'cache' (bootloader) Device State : Unlocked
OKAY [ 0.712s]
Finished. Total time: 1.073s
C:\ADB>fastboot flash vendor vendor.img
Sending 'vendor' (125361 KB) OKAY [ 5.914s]
Writing 'vendor' (bootloader) Device State : Unlocked
OKAY [ 5.715s]
Finished. Total time: 11.640s
C:\ADB>fastboot reboot
Rebooting
Finished. Total time: 0.057s
C:\ADB>
Not sure why that 3rd system sparse chunk is failing. And not even trying the 4th.
Maybe try flashing twrp to recovery and flash a custom rom. Maybe LineageOS.
the recovery photo 。
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[url]https://forum.xda-developers.com/album.php?albumid=14996&pictureid=57661[/URL]
madbat99 said:
Not sure why that 3rd system sparse chunk is failing. And not even trying the 4th.
Maybe try flashing twrp to recovery and flash a custom rom. Maybe LineageOS.
Click to expand...
Click to collapse
The twrp can't load internal Storage 。 when i select storage ，it's 0 MB
i only try fix it in fastboot。
夏默秋殇 said:
The twrp can't load internal Storage 。 when i select storage ，it's 0 MB
i only try fix it in fastboot。
Click to expand...
Click to collapse
Make sure you have the newest twrp. Format data. Not wipe. Format. In twrp wipe-->advanced wipe-->format-->internal storage. Maybe fastboot erase userdata
madbat99 said:
Make sure you have the newest twrp. Format data. Not wipe. Format. In twrp wipe-->advanced wipe-->format-->internal storage. Maybe fastboot erase userdata
Click to expand...
Click to collapse
it's failed
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/vebdor_image'
E:Unable to find partition size for '/misc'
E:Unable to find partition size for '/persistent'
E:Unable to find partition size for '/system_image'
E: primary block device 'dev/block/platform/sdhci-tegra.3/by-name/UDA' for mount point '/data' is not present!
E:Unable to set bootlader message.
Failed to mount '/cache'(Invalid argument)
Updating partition details....
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Full SELinux support is present
Failed to mount '/cache' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Unable to wipe Data
can somebody help me?
hello？anybody？
hello？
Please make sure you are on a recent version of the adb tools. links for multi os download
Can you try 'fastboot format system' while in bootloader? Does it do a format? If it does you could try the full flash procedure again.
Perhaps twrp recorvery can also help.
flash twrp on your device by using 'fastboot flash recovery twrp-file-you-downloaded.img & fastboot boot twrp-file-you-downloaded.img'
In twrp you should try the format function.
Hi
Hey all.. Im not exactly new here . I just read and read
FMFL
Got same error while LOCKING Bootloader thingy .....
Just keep trying to boot to recovery (Power and and Vol DN then quickly UP) that took me all of 5 minutes to gain the upper hand but I did prevail.... 9 took me hours to get the nutz to hit the Flash Button kept going back and forth re reading a lot of useless **** on a few other sights dont know why i even looked there When all the stuff is always right here
Really its because of all you people here.
Thank you for all the reading keeps my mind young!
Ron T
IT Dept.
Deskside support partner
AECOM
Mississauga, ON
aecom.com
Imagine it. Delivered
---------- Post added at 01:44 AM ---------- Previous post was at 01:41 AM ----------
wow I cant say ****? Tee Hee
No i dont post nearly enough
Roffl I had a couple sites with forums only for satellite TV Hacking I left everything wide open .. ya a few bans but it was needed i guess LOL
CYa
Thx
Ron T
IT Dept.
Deskside support partner
AECOM
Mississauga, ON
aecom.com
Imagine it. Delivered
hallo
help me with the current image have been destroyed and can not boot
hello xda communities i have a realme c1 device after updates my phone show these thing ,,the current image have been destroyed and can not boot.please flash the corrrect image or contact custamer service,,
also show these options-
power off
restart
recovery mode
fastboot mode
back to previous page
and
i can not flash it because of this -
Device state - Locked:
please help me please
goldi gupta said:
hello xda communities i have a realme c1 device after updates my phone show these thing ,,the current image have been destroyed and can not boot.please flash the corrrect image or contact custamer service,,
also show these options-
power off
restart
recovery mode
fastboot mode
back to previous page
and
i can not flash it because of this -
Device state - Locked:
please help me please
Click to expand...
Click to collapse
Try asking in a Realme forum. You posted in Nexus 9, and old tablet Google produced prior to the Pixel line.
Hi,
I entered 0 (zero) before the serial number (I have 7 digit serial number), got an img file from Lenovo. In the "tool all in one" program I unlocked the bootloader. Unfortunately, after restarting the phone does not turn on. I can see only Lenovo logo. What ideas how to fix it?