Hopefully someone here can help me, as I'm not finding anything useful about this. I'm trying to install the current version of Ubuntu Touch on my 2012 Nexus 7 (grouper), but this is the response I get when trying to flash the boot partition:
Code:
[email protected] ~/Downloads> fastboot flash boot "vivid-preinstalled-boot-armhf+grouper.img"
sending 'boot' (8526 KB)...
OKAY [ 1.045s]
writing 'boot'...
FAILED (remote: (InvalidSize))
finished. total time: 1.068s
I've never seen this error before, and I don't know what to do to fix it. Does anyone have any advice?
Related
I have a xt907 and after playing around with rooting, I goofed bigtime and now I can only boot to the fastboot menu.
Im trying to flash the default images back on,. but I keep getting errors. I've tried the firmware versions found at the sbf-droid page.
All the Versions except for the last one give me the same error on the system.img
Code:
sending 'system' (262144 KB)... OKAY [ 19.976s]
writing 'system'... INFOPreflash validation failed
FAILED (remote failure)
The last one Android 4.4.2 Blur_Version.183.46.10.XT907.Verizon.en.US - gives me the error
Code:
~/droid/VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml$ ./moto-fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 19.986s]
writing 'system'... INFOProtocol error (multiflash unexpected)
Any help?
Have you tried with rsd lite?
Edit: and you said you rooted did you unlock the bootloader?
Hi,
My phone pop up messages saying some services stopped. So I turned it off and then it stuck in a boot loop circle. (same problem in this thread, http://forum.xda-developers.com/nexus-4/help/help-im-stuck-bootloop-4-circles-t2864835)
First, I tried to enter recovery mode, failed.
then, I tried to fix my recovery ...
Code:
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.351s]
finished. total time: 0.355s
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot flash recovery recovery-clockwork-touch-6.0.4.7-mako.img
sending 'recovery' (8838 KB)...
OKAY [ 0.492s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.512s
also tried the latest "openrecovery-twrp-2.7.1.0-mako.img" downloaded from http://techerrata.com/browse/twrp2/mako
same error
Code:
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7928 KB)...
OKAY [ 0.454s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.473s
here's the fact about my phone:
- CWM (recovery-clockwork-touch-6.0.4.7-mako.img)
- SuperSU (UPDATE-SuperSU-v1.93.zip)
- rooted before the 4.4.4 update, didn't fix the root after ATO update
- Standard Kernel, no custom ROM.
I did suffer the "randomly turning off" problem before (http://forum.xda-developers.com/nexus-4/help/nexus-4-randomly-off-intermittently-t2077148).
What could be the problem for the flash write failure? Is there any other way to recovery the data?
Many Thanks.
Hey guys I was on CM 12 latest stable I believe, and downloaded the Lollipop image from here : http://www.androidauthority.com/2012-nexus-7-wifi-lollipop-factory-image-566274/
It won't let me update, it's probably an easy fix but I'm not sure what file to flash. Running flash-all.bat runs and then says it's missing some files and that my bootloader is 4.18, instead of 4.23.
What's going on? I tried to download bootloader 4.23 and flash it myself but got this:
C:\Users\Nemesis\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.270s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.410s
C:\Users\Nemesis\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.270s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.410s
EDIT: fixed the problem by replacing the bootloader in the archive with this one http://forum.xda-developers.com/showpost.php?p=45043044&postcount=15
Hello guys,
I know this question is very common but I have looked many posts and couldn't find any that solved my problem.
I am trying to flash the stock moto X pure edition (xt1575) again in my device. The trouble starts because fastboot doesn't work.
I already installed Motorola device manager (2.5.4) and booted windows without driver signature enforcement.
I tried adb-setup-1.4.3.exe and installing android SDK, but still get same trouble.
The phone works and get normally funcional when android is loaded, but no responde in fastboot screen!
I am using windows 10.15063.296 (creators update). When I open device manager, now I see "Motorola adb device" with an exclamation.
A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forget-windows-use-linux-is-a-usb-bootable-distro-for-your-android-recovery-needs-xda-spotlight/
jason2678 said:
A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forg...or-your-android-recovery-needs-xda-spotlight/
Click to expand...
Click to collapse
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk
Belotto said:
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk
Click to expand...
Click to collapse
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me
jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
I really wasn´t successful...
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> adb reboot-bootloader
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.370s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash motoboot motoboot.img
error: cannot load 'motoboot.img'
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.137s]
writing 'logo'...
OKAY [ 0.200s]
finished. total time: 0.337s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.518s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.888s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (41040 KB)...
OKAY [ 1.534s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.887s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (509631 KB)...
OKAY [ 17.857s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.357s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot
rebooting...
finished. total time: 0.016s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase userdata
erasing 'userdata'...
OKAY [ 6.423s]
finished. total time: 6.423s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.015s]
finished. total time: 0.015s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.017s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US>
jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
Sagar_1401 said:
https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me
Click to expand...
Click to collapse
I have tried it before... wasn't working but i realized that i needed to push "allow oem unlock" and "usb debugging" buttons ... LOL.
Hey guys, i wanted to unlock bootloader, and so i UNLOCKED BOOTLOADER, FLAHSED TWRP, TRIED TO FLASH CUSTOM ROM.
the twrp compared tz version and ended up in an error, so i searched online to know that, we need to update the system.
so i flashed recovery.img on top of twrp and rebooted where the fastboot got lost and ended up in a dead boot.
no vibrations, no led, no charging, no fast boot.
then i flashed using qfil using qualcom husb and got back the fastboot.
but this time, in fastboot, when i try to flash boot, system or recovery, it says, ::ARTITION TABLE DOES NOT EXIST.
so i tried to flash the gpt_both0.bin file as partition, and gave an error message of::: CANNOT FLASH THIS PARTITION IN LOCKED STATE.
i tried to fastboot boot twrp.img and ended up::: UNLOCK DEVICE TO USE THIS COMMAND.
so im pretty much got my bootloader locked and im unable to unlock it so i can flash stuffs.
the question is, how to flash the bootloader using fastboot so i can flash the rest and continue/??
Code:
C:\adb>fastboot devices
5072e4de fastboot
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24869 KB)...
OKAY [ 0.784s]
writing 'boot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.799s
C:\adb>fastboot flash partition gpt_both0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.016s
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (29968 KB)...
OKAY [ 0.944s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.952s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.950s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.950s
https://www.androidfilehost.com/?fid=24671318762849134 you need to flash this fisrt before flash custom rom
Same Problem XDA devs Pl Help
Kabeesh said:
Hey guys, i wanted to unlock bootloader, and so i UNLOCKED BOOTLOADER, FLAHSED TWRP, TRIED TO FLASH CUSTOM ROM.
the twrp compared tz version and ended up in an error, so i searched online to know that, we need to update the system.
so i flashed recovery.img on top of twrp and rebooted where the fastboot got lost and ended up in a dead boot.
no vibrations, no led, no charging, no fast boot.
then i flashed using qfil using qualcom husb and got back the fastboot.
but this time, in fastboot, when i try to flash boot, system or recovery, it says, ::ARTITION TABLE DOES NOT EXIST.
so i tried to flash the gpt_both0.bin file as partition, and gave an error message of::: CANNOT FLASH THIS PARTITION IN LOCKED STATE.
i tried to fastboot boot twrp.img and ended up::: UNLOCK DEVICE TO USE THIS COMMAND.
so im pretty much got my bootloader locked and im unable to unlock it so i can flash stuffs.
the question is, how to flash the bootloader using fastboot so i can flash the rest and continue/??
Code:
C:\adb>fastboot devices
5072e4de fastboot
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24869 KB)...
OKAY [ 0.784s]
writing 'boot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.799s
C:\adb>fastboot flash partition gpt_both0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.016s
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (29968 KB)...
OKAY [ 0.944s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.952s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.950s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.950s
Click to expand...
Click to collapse
:fingers-crossed: