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?
Related
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
[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.
Hi,
I am trying to revive my Asus and running into following problem. I read multiple threads and forums and have executed multiple commands in cmd fastboot. Getting following errors:
First I was running into error that "vrl needs to be flashed" which I found a correct (I hope) file and flashed the vrl, and then flashed CM13 or stock ROM from Asus website. Which fastboot returns with "OKAY flashed partition system. Time 28 seconds" Still wont boot and stuck on boot logo.
C:\adb>fastboot devices
G5NPFP026657RFA fastboot
C:\adb>fastboot flash system UL-P023-CN-4.7.3.0-user.zip
(bootloader) system partition type: ext4
target reported max download size of 1019215872 bytes
erasing 'system'...
(bootloader) Erasing partition: system
OKAY [ 0.031s]
sending 'system' (907352 KB)...
(bootloader) Ready to receive: 0x376162fc size of data
OKAY [ 28.448s]
writing 'system'...
(bootloader) Flashing partition: system
FAILED (remote: VRL need to be flashed!)
finished. total time: 28.511s
C:\adb>fastboot flash vrl vrl2.bin
(bootloader) vrl partition type: raw
target reported max download size of 1019215872 bytes
sending 'vrl' (128 KB)...
(bootloader) Ready to receive: 0x00020000 size of data
OKAY [ 0.016s]
writing 'vrl'...
(bootloader) Flashing partition: vrl
OKAY [ 0.078s]
finished. total time: 0.094s
C:\adb>fastboot flash system UL-P023-CN-4.7.3.0-user.zip
(bootloader) system partition type: ext4
target reported max download size of 1019215872 bytes
erasing 'system'...
(bootloader) Erasing partition: system
OKAY [ 0.047s]
sending 'system' (907352 KB)...
(bootloader) Ready to receive: 0x376162fc size of data
OKAY [ 28.424s]
writing 'system'...
(bootloader) Flashing partition: system
OKAY [ 0.031s]
finished. total time: 28.518s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.016s
Any of the senior members or other who have more knowledge, please shade some light here and tell me what am I doing wrong??
I also get below error at times, and my computer gets stuck every time I execute below command and it takes forever for it to get back to working by itself unless I try to close the application.
C:\adb>fastboot update system "C:\adb\UL-P023-WW-4.7.3.0-user.zip"
W/ ( 448): Unable to open 'system': No such file or directory
error: failed to open zip file 'system': I/O Error
C:\adb>fastboot flash system UL-P023-WW-4.7.3.0-user.zip
(bootloader) system partition type: ext4
target reported max download size of 1019215872 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 175719111 is not a multiple of t
he block size 4096
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 1.102s
Very much keen to read some good replies. Thanks in advance guys.
Hey Guys i need help
I want to go back to the original OS from GrapheneOS. But whenever I want to flash the Google Stock Image via Fastboot, an error appears. The online flash tool from Google also breaks off when flashing.
Fastboot Error:
FAILED (remote: failed to flash partition (system_b))
Why did you flash a custom rom if you have no clue on what you are doing? Ask the rom developer your question.
Always research and read about what modding you are interested in.
Lesson learned!
"Biffer"??
What kind of adb tools are you using?
vandyman said:
Why did you flash a custom rom if you have no clue on what you are doing? Ask the rom developer your question.
Always research and read about what modding you are interested in.
Lesson learned!
Click to expand...
Click to collapse
The device was from ebay with custom rom installed. That's why I wanted to go back.
ExodusCrowley said:
Hey Guys i need help
I want to go back to the original OS from GrapheneOS. But whenever I want to flash the Google Stock Image via Fastboot, an error appears. The online flash tool from Google also breaks off when flashing.
Fastboot Error:
FAILED (remote: failed to flash partition (system_b))
Click to expand...
Click to collapse
Are you using the latest Platform Tools?
ExodusCrowley said:
The device was from ebay with custom rom installed. That's why I wanted to go back.
Click to expand...
Click to collapse
Ah I see.
Download the Pixel factoy image. Unzip it. Run flash-all.bat. There are a few how to guides on this. Or just follow the Google developers guide.
Android platform - tools versions 32 or 33 will work on your PC for adb/fastboot commands.
Make sure you install the official Google usb driver on your PC or the platform tools will not work right.
Lughnasadh said:
Are you using the latest Platform Tools?
Click to expand...
Click to collapse
yes
target reported max download size of 261095424 bytes
sending 'bootloader_b' (10862 KB)...
OKAY [ 0.343s]
writing 'bootloader_b'...
(bootloader) Flashing pack version slider-1.0-8062051
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_b
(bootloader) Validating partition pbl_b
(bootloader) Validating partition bl2_b
(bootloader) Validating partition abl_b
(bootloader) Validating partition bl31_b
(bootloader) Validating partition tzsw_b
(bootloader) Validating partition gsa_b
(bootloader) Validating partition ldfw_b
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition partition:0
(bootloader) Flashing partition partition:1
(bootloader) Flashing partition partition:2
(bootloader) Flashing partition partition:3
(bootloader) Flashing partition bl1_b
(bootloader) Flashing partition pbl_b
(bootloader) Flashing partition bl2_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition bl31_b
(bootloader) Flashing partition tzsw_b
(bootloader) Flashing partition gsa_b
(bootloader) Flashing partition ldfw_b
(bootloader) Loading sideload ufsfwupdate
OKAY [ 2.954s]
finished. total time: 3.298s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.018s
target reported max download size of 261095424 bytes
sending 'radio_b' (80220 KB)...
OKAY [ 3.111s]
writing 'radio_b'...
(bootloader) Flashing pack version g5123b-93368-211225-M-8029609
(bootloader) Flashing partition modem_b
OKAY [ 0.316s]
finished. total time: 3.436s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.009s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 1.270s
target reported max download size of 261095424 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (16 MB) to disk... took 0.142s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (849 MB) to disk... took 62.433s
archive does not contain 'system.sig'
extracting system_other.img (22 MB) to disk... took 0.400s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took -0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (459 MB) to disk... took 31.867s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: slider-1.0-8062051
Baseband Version.....: g5123b-93368-211225-B-8029609
Serial Number........: 1C231FDF6002U5
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.009s]
checking version-baseband...
OKAY [ 0.009s]
sending 'boot_b' (65536 KB)...
OKAY [ 1.999s]
writing 'boot_b'...
OKAY [ 0.279s]
sending 'dtbo_b' (16384 KB)...
OKAY [ 0.567s]
writing 'dtbo_b'...
OKAY [ 0.077s]
sending sparse 'system_b' 1/4 (254972 KB)...
OKAY [ 9.461s]
writing 'system_b' 1/4...
(bootloader) image size (894066688) biffer than partition size (0)
FAILED (remote: failed to flash partition (system_b))
finished. total time: 12.578s
Press any key to exit...
Click to expand...
Click to collapse
Complete flash log
Platform Tools and Android USB drivers are up to date
After flashing via Linux it worked.
ExodusCrowley said:
Complete flash log
Platform Tools and Android USB drivers are up to date
Click to expand...
Click to collapse
Something is not updated right in your Pc.
alin919 said:
Something is not updated right in your Pc.
Click to expand...
Click to collapse
I have no idea where the error was. It worked with Linux.
Hi everyone. I am trying to wipe my pixel 6, as I want to install a custom rom.
When trying to wipe, this happens.
fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: variable (partition-type:cache) not found)
erasing 'userdata'...
OKAY [ 0.191s]
erasing 'cache'...
FAILED (remote: partition not found)
finished. total time: 0.196s
When trying to flash a bootloader, It gives me this error:
sending 'bootloader' (11506 KB)...
OKAY [ 0.269s]
writing 'bootloader'...
(bootloader) Flashing pack version slider-1.2-8318357
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_a
(bootloader) Validating partition pbl_a
(bootloader) failed: invalid rollback counter
(bootloader) image(pbl_a): rejected, fails validation
(bootloader) failed to validate partition (pbl_a)
FAILED (remote: failed to flash partition (bootloader))
finished. total time: 0.347s
I believe these two errors are connected, but I am not sure why this is happening. I am aware google did something regarding preventing bootloader rollback with android 13, and I recall accidentally installing it OTA once and having to rollback to 12.
You flashed Android 13 at some point (the "invalid rollback counter" error). Once Android 13 is installed you cannot install older bootloaders. Period.
The other error? Raw format means no formatting at all. In essence you have a blank drive. You may want to try restoring using Google's flash tool prior to installing your chosen ROM.