Hey guys,
I have been trying to flash my Tablet for a few hours now. I would constantly get problems trying to flash. I'd reboot and go into fastboot again and then it would flash successfully. This works for everything (boot.img, recovery.img, system.img) however i can never get userdata.img to flash correctly. I am using the steps from nVidia to do this. Ill post the steps here as well as the exact error im getting.
Steps:
Code:
SHIELD TABLET RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD TABLET, connect your SHIELD TABLET
via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD TABLET into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method:
- Turn off the device
- Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
To flash this recovery image to your SHIELD TABLET, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Unlocking the Bootloader
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.
My CMD window:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 12.593s]
finished. total time: 12.594s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.022s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata
.img
target reported max download size of 570425344 bytes
erasing 'userdata'...
OKAY [ 12.548s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 23.951s]
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 46.546s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 570425344 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.425s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 10.476s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase recovery
erasing 'recovery'...
OKAY [ 5.034s]
finished. total time: 5.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 570425344 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.416s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 10.463s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
sending 'recovery' (9758 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 570425344 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.414s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 10.462s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.030s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 570425344 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.428s]
writing 'recovery'...
OKAY [ 0.281s]
finished. total time: 0.711s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 570425344 bytes
sending 'boot' (7608 KB)...
OKAY [ 0.339s]
writing 'boot'...
OKAY [ 0.226s]
finished. total time: 0.567s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 570425344 bytes
erasing 'system'...
OKAY [ 0.637s]
sending sparse 'system' (556772 KB)...
OKAY [ 24.041s]
writing 'system'...
OKAY [ 20.876s]
sending sparse 'system' (555305 KB)...
OKAY [ 24.219s]
writing 'system'...
OKAY [ 19.289s]
sending sparse 'system' (56409 KB)...
OKAY [ 2.431s]
writing 'system'...
OKAY [ 1.964s]
finished. total time: 93.461s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata
.img
target reported max download size of 570425344 bytes
erasing 'userdata'...
OKAY [ 10.050s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 23.801s]
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 43.929s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata
.img
target reported max download size of 570425344 bytes
erasing 'userdata'...
OKAY [ 5.048s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 23.702s]
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 38.796s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot staging blob
usage: fastboot [ <option> ] <command>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash staging blob
target reported max download size of 570425344 bytes
sending 'staging' (17491 KB)...
OKAY [ 0.742s]
writing 'staging'...
FAILED (remote: (FileWriteFailed))
finished. total time: 10.807s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash staging blob
target reported max download size of 570425344 bytes
sending 'staging' (17491 KB)...
OKAY [ 0.752s]
writing 'staging'...
OKAY [ 0.495s]
finished. total time: 1.249s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dtb tegra124-tn8-
p1761-1270-a04-e-battery.dtb
target reported max download size of 570425344 bytes
sending 'dtb' (68 KB)...
OKAY [ 0.027s]
writing 'dtb'...
OKAY [ 0.011s]
finished. total time: 0.039s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata
.img
target reported max download size of 570425344 bytes
erasing 'userdata'...
OKAY [ 12.662s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 23.825s]
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 46.542s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.002s]
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery G:\recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (26708 KB)...
OKAY [ 0.813s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.813s
(yes, the recovery.img is at disk G)
Try fastboot oem device-info
Sent from my Redmi Note 3 Pro using Tapatalk
I have a problem which through thorough google searches, I haven't been able to find an answer to. I'm trying to flash a custom recovery onto an LG G5, as probably presumed in the topic name, utilizing fastboot and it never seems to flash so I tried to go into the stock recovery and found that there wasn't a recovery at all. It simply shows the android bot with an open stomach and says no command. How would I go about getting a recovery on it, if at all possible?
Command Prompt Log:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (19100 KB)...
OKAY [ 0.721s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.744s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.024s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.759s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.795s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot format recovery
Formatting is not supported for file system with type ''.
After several searches on the net, unlock the bootloader and to do
the ROOT this phone Huawei y 6 2018, but now they are stranded
in the installation of the Twrp recovery.
Fastboot gives me this error:
Code:
PS D:\Cellulare\adb-and-fastboot> fastboot flash recovery twrp-3.2.1-1.img
target reported max download size of 535822336 bytes
sending 'recovery' (14638 KB)...
OKAY [ 0.453s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.469s
PS D:\Cellulare\adb-and-fastboot>
How do I solve?
same probleme
I was trying to upgrade from Android 11 to 12 with an Android 12 GSI using Fastboot, but whenever I try to install the system.img, it always fails with the error:
(bootloader) Preflash validation failed FAILED (remote failure)
Click to expand...
Click to collapse
I have seen that this error is common if you have the bootloader locked, but mine is unlocked.
Here's the full list of commands I used:
Code:
F:\Programs\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (52224 KB)...
OKAY [ 1.276s]
writing 'boot_b'...
OKAY [ 0.779s]
finished. total time: 2.056s
F:\Programs\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 805261312 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.005s]
writing 'vbmeta_b'...
(bootloader) WARNING: vbmeta_b anti rollback downgrade, 0 vs 16
OKAY [ 0.036s]
finished. total time: 0.041s
F:\Programs\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805261312 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/3 (786340 KB)...
OKAY [ 19.870s]
writing 'system_b' 1/3...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.962s
Why do I get this error, and is there any way to solve it?
ByteSeb said:
I was trying to upgrade from Android 11 to 12 with an Android 12 GSI using Fastboot, but whenever I try to install the system.img, it always fails with the error:
I have seen that this error is common if you have the bootloader locked, but mine is unlocked.
Here's the full list of commands I used:
Code:
F:\Programs\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (52224 KB)...
OKAY [ 1.276s]
writing 'boot_b'...
OKAY [ 0.779s]
finished. total time: 2.056s
F:\Programs\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 805261312 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.005s]
writing 'vbmeta_b'...
(bootloader) WARNING: vbmeta_b anti rollback downgrade, 0 vs 16
OKAY [ 0.036s]
finished. total time: 0.041s
F:\Programs\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805261312 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/3 (786340 KB)...
OKAY [ 19.870s]
writing 'system_b' 1/3...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.962s
Why do I get this error, and is there any way to solve it?
Click to expand...
Click to collapse
You need to be in fastboot d to flash system images. In regular fastboot, type fastboot reboot fastboot.
Beetle84 said:
You need to be in fastboot d to flash system images. In regular fastboot, type fastboot reboot fastboot.
Click to expand...
Click to collapse
It seems like that was working, but now I get this error:
FAILED (remote: Operation not permitted)
Click to expand...
Click to collapse
Here's the commands I used:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot_a' (52224 KB)...
OKAY [ 1.373s]
writing 'boot_a'...
OKAY [ 1.584s]
finished. total time: 2.958s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 268435456 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.003s]
writing 'vbmeta_a'...
OKAY [ 0.047s]
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/7 (262108 KB)...
OKAY [ 7.087s]
writing 'system_a' 1/7...
OKAY [ 1.746s]
sending sparse 'system_a' 2/7 (262120 KB)...
OKAY [ 7.075s]
writing 'system_a' 2/7...
OKAY [ 1.723s]
sending sparse 'system_a' 3/7 (262112 KB)...
OKAY [ 7.015s]
writing 'system_a' 3/7...
OKAY [ 1.746s]
sending sparse 'system_a' 4/7 (262124 KB)...
OKAY [ 7.001s]
writing 'system_a' 4/7...
OKAY [ 1.736s]
sending sparse 'system_a' 5/7 (262088 KB)...
OKAY [ 7.013s]
writing 'system_a' 5/7...
FAILED (remote: Operation not permitted)
finished. total time: 43.777s
ByteSeb said:
It seems like that was working, but now I get this error:
Here's the commands I used:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot_a' (52224 KB)...
OKAY [ 1.373s]
writing 'boot_a'...
OKAY [ 1.584s]
finished. total time: 2.958s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 268435456 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.003s]
writing 'vbmeta_a'...
OKAY [ 0.047s]
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/7 (262108 KB)...
OKAY [ 7.087s]
writing 'system_a' 1/7...
OKAY [ 1.746s]
sending sparse 'system_a' 2/7 (262120 KB)...
OKAY [ 7.075s]
writing 'system_a' 2/7...
OKAY [ 1.723s]
sending sparse 'system_a' 3/7 (262112 KB)...
OKAY [ 7.015s]
writing 'system_a' 3/7...
OKAY [ 1.746s]
sending sparse 'system_a' 4/7 (262124 KB)...
OKAY [ 7.001s]
writing 'system_a' 4/7...
OKAY [ 1.736s]
sending sparse 'system_a' 5/7 (262088 KB)...
OKAY [ 7.013s]
writing 'system_a' 5/7...
FAILED (remote: Operation not permitted)
finished. total time: 43.777s
Click to expand...
Click to collapse
if you update adb, you will see that it gives you an error for no space (atleast for me it did). To fix this, since your phone uses AB partitioning, you will need to do fastboot delete-logical-partition product_a and it should be good since you are using a GSI
Thanks! That worked
GigaPVP said:
if you update adb, you will see that it gives you an error for no space (atleast for me it did). To fix this, since your phone uses AB partitioning, you will need to do fastboot delete-logical-partition product_a and it should be good since you are using a GSI
Click to expand...
Click to collapse
i tried "fastboot delete-logical-partiton product_a" (a partition was active)
but error message occurs "unknown command delete-logical-partiton "
~using latest platform toot
~installing Android 13 GSI arm64+GSM .img
~on pixel 3