I have used it this way for a nexus one:
NOTE: that only boot, recovery, and system will be flashed - bit misleading
1. Unzip zipped *.img files to a directory
Code:
unzip -d somedir passion.zip
I have these files: android-info.txt, radio.img, splash1.img, boot.img, recovery.img, system.img, hboot_8x50_0.35.0017_100610.nb0, spcustom.img, userdata.img
I used PASSIMG_Passion_Google_WWE_3.13.1700.1_GRK39F_release_signed.zip
2. cd into directory
Code:
cd somedir
3.
Code:
sudo ANDROID_PRODUCT_OUT="./" fastboot flashall
NOTE: ANDROID_PRODUCT_OUT variable is set to current directory "./" and only a space after this to fastboot command. This sets environment variable and runs command.
Code:
Example output
--------------------------------------------
Bootloader Version...: 0.35.0017
Baseband Version.....: 5.12.00.08
Serial Number........: HT9CPP80xxxx
--------------------------------------------
sending 'boot' (2322 KB)...
OKAY [ 0.376s]
writing 'boot'...
OKAY [ 0.979s]
sending 'recovery' (2560 KB)...
OKAY [ 0.403s]
writing 'recovery'...
OKAY [ 1.045s]
sending 'system' (135673 KB)...
OKAY [ 20.775s]
writing 'system'...
OKAY [ 47.087s]
rebooting...
finished. total time: 70.755s
Related
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>
Hello
I compiled android for Volantis ( after downloading the sources from official google repo )
when trying to flash it i have this message
i added the "-S 256M" after finding it online , it didn't work without it too , i think that it doesn't flash the whole image since the image size is 1.5G .
I successfully flash the stock image though .
Code:
fastboot flash -S 256M system system.img
gives this output :
Code:
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.954s]
sending sparse 'system' (233172 KB)...
OKAY [ 11.755s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 7.615s]
sending sparse 'system' (255959 KB)...
OKAY [ 12.817s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 8.801s]
sending sparse 'system' (62570 KB)...
OKAY [ 3.364s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 2.531s]
finished. total time: 47.838s
If anyone has had this problem before and knows the solution , i would be grateful
My Nexus 6P got stuck on a boot loop in the middle of a resource-intensive game. It was on the angler-opm6.171019.030.e1 firmware with a recent-ish version of Lineage OS.
In this state, I can get into the bootloader by keeping the volume down key pressed. However, I can't get into recovery from the bootloader, or do a factory reset, or do anything else. Choosing any option in the bootloader simply causes the phone to reboot.
However, while the bootloader is open, I am able to connect the phone to my computer via USB and run fastboot. At first I tried reflashing individual partitions like the bootloader, the vendor image, the recovery (TWRP) and eventually boot, in the hopes that reflashing one of them would fix the issue. Eventually, I downloaded the latest stock image from Google and reflashed the entire thing using the vendor-provided script:
Code:
fastboot flash bootloader bootloader-angler-angler-03.79.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-angler-angler-03.87.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-angler-opm6.171019.030.k1.zip
It was very thorough. As you can see by the mkfs, it even reformatted my storage (RIP dog pics):
Code:
$ ./flash-all.sh
Sending 'bootloader' (3552 KB) OKAY [ 0.128s]
Writing 'bootloader' OKAY [ 0.209s]
Finished. Total time: 0.366s
rebooting into bootloader OKAY [ 0.125s]
Finished. Total time: 0.126s
< waiting for any device >
Sending 'radio' (48728 KB) OKAY [ 1.303s]
Writing 'radio' OKAY [ 2.178s]
Finished. Total time: 3.512s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: angler-03.79
Baseband Version.....: angler-03.87
Serial Number........: 84B7N15A04004581
--------------------------------------------
Checking product OKAY [ 0.021s]
Checking version-bootloader OKAY [ 0.020s]
Checking version-baseband OKAY [ 0.020s]
extracting boot.img (11 MB) to disk... took 0.122s
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 (18 MB) to disk... took 0.084s
archive does not contain 'recovery.sig'
extracting system.img (1912 MB) to disk... took 11.444s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (188 MB) to disk... took 1.259s
archive does not contain 'vendor.sig'
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6694270 4k blocks and 1676080 inodes
Filesystem UUID: b506d1ce-64e3-40fc-a7ed-cb63d08a0704
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 25600 4k blocks and 25600 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'boot' (12089 KB) OKAY [ 0.338s]
Writing 'boot' OKAY [ 0.181s]
Sending 'recovery' (18961 KB) OKAY [ 0.510s]
Writing 'recovery' OKAY [ 0.275s]
Sending sparse 'system' 1/5 (482664 KB) OKAY [ 12.736s]
Writing sparse 'system' 1/5 OKAY [ 7.243s]
Sending sparse 'system' 2/5 (475570 KB) OKAY [ 12.729s]
Writing sparse 'system' 2/5 OKAY [ 6.745s]
Sending sparse 'system' 3/5 (474890 KB) OKAY [ 13.047s]
Writing sparse 'system' 3/5 OKAY [ 7.821s]
Sending sparse 'system' 4/5 (476548 KB) OKAY [ 12.622s]
Writing sparse 'system' 4/5 OKAY [ 6.947s]
Sending sparse 'system' 5/5 (49108 KB) OKAY [ 1.259s]
Writing sparse 'system' 5/5 OKAY [ 0.712s]
Sending 'vendor' (192565 KB) OKAY [ 5.124s]
Writing 'vendor' OKAY [ 3.262s]
Erasing 'userdata' OKAY [ 0.326s]
Sending 'userdata' (4412 KB) OKAY [ 0.163s]
Writing 'userdata' OKAY [ 0.095s]
Erasing 'cache' OKAY [ 0.024s]
Sending 'cache' (96 KB) OKAY [ 0.032s]
Writing 'cache' OKAY [ 0.030s]
Rebooting
Finished. Total time: 106.097s
Suffice to say this didn't fix the issue. The phone is still on a boot loop.
What else is there to try?
I suspect a hardware issue but I can't run any diagnostics since fastboot doesn't give me shell access.
Thanks in advance!
Bug In Rom
joeymallone said:
My Nexus 6P got stuck on a boot loop in the middle of a resource-intensive game. It was on the angler-opm6.171019.030.e1 firmware with a recent-ish version of Lineage OS.
In this state, I can get into the bootloader by keeping the volume down key pressed. However, I can't get into recovery from the bootloader, or do a factory reset, or do anything else. Choosing any option in the bootloader simply causes the phone to reboot.
However, while the bootloader is open, I am able to connect the phone to my computer via USB and run fastboot. At first I tried reflashing individual partitions like the bootloader, the vendor image, the recovery (TWRP) and eventually boot, in the hopes that reflashing one of them would fix the issue. Eventually, I downloaded the latest stock image from Google and reflashed the entire thing using the vendor-provided script:
Code:
fastboot flash bootloader bootloader-angler-angler-03.79.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-angler-angler-03.87.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-angler-opm6.171019.030.k1.zip
It was very thorough. As you can see by the mkfs, it even reformatted my storage (RIP dog pics):
Code:
$ ./flash-all.sh
Sending 'bootloader' (3552 KB) OKAY [ 0.128s]
Writing 'bootloader' OKAY [ 0.209s]
Finished. Total time: 0.366s
rebooting into bootloader OKAY [ 0.125s]
Finished. Total time: 0.126s
< waiting for any device >
Sending 'radio' (48728 KB) OKAY [ 1.303s]
Writing 'radio' OKAY [ 2.178s]
Finished. Total time: 3.512s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: angler-03.79
Baseband Version.....: angler-03.87
Serial Number........: 84B7N15A04004581
--------------------------------------------
Checking product OKAY [ 0.021s]
Checking version-bootloader OKAY [ 0.020s]
Checking version-baseband OKAY [ 0.020s]
extracting boot.img (11 MB) to disk... took 0.122s
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 (18 MB) to disk... took 0.084s
archive does not contain 'recovery.sig'
extracting system.img (1912 MB) to disk... took 11.444s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (188 MB) to disk... took 1.259s
archive does not contain 'vendor.sig'
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6694270 4k blocks and 1676080 inodes
Filesystem UUID: b506d1ce-64e3-40fc-a7ed-cb63d08a0704
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 25600 4k blocks and 25600 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'boot' (12089 KB) OKAY [ 0.338s]
Writing 'boot' OKAY [ 0.181s]
Sending 'recovery' (18961 KB) OKAY [ 0.510s]
Writing 'recovery' OKAY [ 0.275s]
Sending sparse 'system' 1/5 (482664 KB) OKAY [ 12.736s]
Writing sparse 'system' 1/5 OKAY [ 7.243s]
Sending sparse 'system' 2/5 (475570 KB) OKAY [ 12.729s]
Writing sparse 'system' 2/5 OKAY [ 6.745s]
Sending sparse 'system' 3/5 (474890 KB) OKAY [ 13.047s]
Writing sparse 'system' 3/5 OKAY [ 7.821s]
Sending sparse 'system' 4/5 (476548 KB) OKAY [ 12.622s]
Writing sparse 'system' 4/5 OKAY [ 6.947s]
Sending sparse 'system' 5/5 (49108 KB) OKAY [ 1.259s]
Writing sparse 'system' 5/5 OKAY [ 0.712s]
Sending 'vendor' (192565 KB) OKAY [ 5.124s]
Writing 'vendor' OKAY [ 3.262s]
Erasing 'userdata' OKAY [ 0.326s]
Sending 'userdata' (4412 KB) OKAY [ 0.163s]
Writing 'userdata' OKAY [ 0.095s]
Erasing 'cache' OKAY [ 0.024s]
Sending 'cache' (96 KB) OKAY [ 0.032s]
Writing 'cache' OKAY [ 0.030s]
Rebooting
Finished. Total time: 106.097s
Suffice to say this didn't fix the issue. The phone is still on a boot loop.
What else is there to try?
I suspect a hardware issue but I can't run any diagnostics since fastboot doesn't give me shell access.
Thanks in advance!
Click to expand...
Click to collapse
Hi there,
Well since it's a recent firmware there might be a slight chance that it's a bug that caused your bootloop.
I think you're better of installing another custom ROM without any bugs.
If there are BUGS do tell the developers of that ROM so they will be able to fix it.
And I am 50% sure that it might not be a Hardware Issue that you are able to connect the phone onto your PC and thus the PC recognises it. But keep trying different stock versions of that phone.
If that didn't work install a updated TWRP and then load your another custom ROM on to your SD card or use ADB and flash the ROM. See if that works.
OPTIONAL READING
Hi, let's go:
Scénario: you know nothing Jon Snow, but you want root, so you install fastboot, no matter which twrp, you follow a couple of tutorials you found in the wild and you play around with slot a -slot b twrp option. You find funny erase partitions, that way you have more internal space, maybe. You erase devil cache, and good boy cache and everything, because why not? You do not make backups, 'cause your not a coward, but a little nervous-impulsive. Magisk? it sound cool, I´ll take 4, thanks
Strange, things start going badly: The nokia 3.2 goes crazy and you just have fastboot. You manage to have twrp again thanks to the command fastboot flash boot twrp-3.2-dpl-00eea
Buuuuuuut you cannot install img nor zip files from sdcard using install options, then you discover that there is /sdcard an /external_sdcard¡¡¡ but it does not matter, file is corrupted, even drinking bleach does not improves the situation. Yo cannot install lineage-17.1-20200413-UNOFFICIAL-treble_arm64_avN. img or .zip (ahhhh it is RAR, so I have to change the extension to zip? maybe the system folder?) and you do not even know if you are arm64 a/b or just arm or legs.
You try to install system-quack-arm-ab-vanilla via adb push commands or fastboot commands, you fight with qualcomm drivers, the qfil tool, with not command found little android robot message, your system is corrupt message, go to see google nokia page (why? they are the enemy who bloats my phone!!!) you do not even know if you were in andorid 10 or 9 or 1909? You start filling up your desktop with images boot.img, .exe files OST LA bizarre programme... You try to open the nokia 3.2 to search 2 pins to enable eld supermode-mode with no chance 'cause you are not strong enough and it is really well ... glued? MAybe if I pay someone else tou fix it? 140 euros... 120 dollars, no, wait it is reaaaaaly expensive¡¡¡
REAL HINT
Have a try to download HMDSW_DPL_sprout-015B-0-00WW-B01 and search for boot vbmeta and other .img files and flash them manually via fastboot, if you are lucky as me, you may fix the self provocated prob:
PS C:\Users\ike\Desktop> cd platform-tools-new PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash boot \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\boot.img < waiting for any device >
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash boot \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\boot.img Sending 'boot' (65536 KB) OKAY [ 2.072s]
Writing 'boot' OKAY [ 0.620s]
Finished. Total time: 2.692s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash custom \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\custom.img Sending 'custom' (6204 KB) OKAY [ 0.203s]
Writing 'custom' OKAY [ 0.062s]
Finished. Total time: 0.282s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash persist \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\persist.img Sending 'persist' (32768 KB) OKAY [ 1.038s]
Writing 'persist' OKAY [ 0.315s]
Finished. Total time: 1.354s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash system \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\system.img Sending sparse 'system' 1/6 (523260 KB) OKAY [ 16.927s]
Writing 'system' OKAY [ 6.093s]
Sending sparse 'system' 2/6 (523260 KB) OKAY [ 16.899s]
Writing 'system' OKAY [ 6.657s]
Sending sparse 'system' 3/6 (523260 KB) OKAY [ 16.888s]
Writing 'system' OKAY [ 5.328s]
Sending sparse 'system' 4/6 (492416 KB) OKAY [ 15.869s]
Writing 'system' OKAY [ 6.127s]
Sending sparse 'system' 5/6 (502344 KB) OKAY [ 16.201s]
Writing 'system' OKAY [ 4.613s]
Sending sparse 'system' 6/6 (24680 KB) OKAY [ 0.793s]
Writing 'system' OKAY [ 1.132s]
Finished. Total time: 119.152s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash userdata \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\userdata.img Sending 'userdata' (1268 KB) OKAY [ 0.031s]
Writing 'userdata' OKAY [ 0.031s]
Finished. Total time: 0.079s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash vbmeta \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\vbmeta.img Sending 'vbmeta' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta' OKAY [ 0.000s]
Finished. Total time: 0.016s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash vendor \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\vendor.img Sending 'vendor' (424560 KB) OKAY [ 13.363s]
Writing 'vendor' OKAY [ 3.931s]
Finished. Total time: 17.497s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot reboot Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
PS C:\Users\ike\Desktop\platform-tools-new>
I'm willing to help, as far as I have to stay home because of a biological hacking. And if you do not know what are you doing or you are not confident, do not do it. Thanks
hello
can you please explain step by step?
thank you
kntb said:
hello
can you please explain step by step?
thank you
Click to expand...
Click to collapse
First tell me what have you done so far
Hi
Thanks for guide
but I am unable boot after following all above steps
Just as a tip: I once got mine soft-bricked (that was a scary one. No partitions, can't flash, boot, or erase anything at all, even saw the linux penguin logo instead of "Android One"), but after lots of googling i decided to check my active slot, turned out it was something like "UNAVAILABLE" (or so)
So I just set my active slot to A (or B, doesn't matter) and I recovered everything.
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