Develop Bugs

Cannot install stock rom: FAILED (remote: data too large)

I tried installing Cyanogenmod on a Nexus 5X, and it didn't work, so now I'm trying to install the stock rom from this site: https://developers.google.com/android/images#bullhead.
I'm doing this on Ubuntu 15.10. When I run the flash-all.sh script (on any of them), I get this output:
target reported max download size of 536870912 bytes
sending 'bootloader' (4382 KB)...
OKAY [ 0.195s]
writing 'bootloader'...
OKAY [ 0.077s]
finished. total time: 0.272s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.715s]
writing 'radio'...
OKAY [ 0.338s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: BHZ10i
Baseband Version.....: M8994F-2.6.22.0.56
Serial Number........: 00a9164559592811
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (11469 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.073s]
sending 'recovery' (12521 KB)...
OKAY [ 0.393s]
writing 'recovery'...
OKAY [ 0.092s]
erasing 'system'...
OKAY [ 0.089s]
sending 'system' (1950236 KB)...
FAILED (remote: data too large)
finished. total time: 1.210s
I'm not seeing many resources online about this error. The only thing I've seen is to update fastboot, but I've already got the latest installed with this ppa: http://askubuntu.com/questions/34702/how-do-i-set-up-android-adb
Is there anything that I can do to get it working correctly?

adanedhel728 said:
I tried installing Cyanogenmod on a Nexus 5X, and it didn't work, so now I'm trying to install the stock rom from this site: https://developers.google.com/android/images#bullhead.
I'm doing this on Ubuntu 15.10. When I run the flash-all.sh script (on any of them), I get this output:
target reported max download size of 536870912 bytes
sending 'bootloader' (4382 KB)...
OKAY [ 0.195s]
writing 'bootloader'...
OKAY [ 0.077s]
finished. total time: 0.272s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.715s]
writing 'radio'...
OKAY [ 0.338s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: BHZ10i
Baseband Version.....: M8994F-2.6.22.0.56
Serial Number........: 00a9164559592811
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (11469 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.073s]
sending 'recovery' (12521 KB)...
OKAY [ 0.393s]
writing 'recovery'...
OKAY [ 0.092s]
erasing 'system'...
OKAY [ 0.089s]
sending 'system' (1950236 KB)...
FAILED (remote: data too large)
finished. total time: 1.210s
I'm not seeing many resources online about this error. The only thing I've seen is to update fastboot, but I've already got the latest installed with this ppa: http://askubuntu.com/questions/34702/how-do-i-set-up-android-adb
Is there anything that I can do to get it working correctly?
Click to expand...
Click to collapse
the system image always is too large and usually it gets transferred in smaller pieces automatically. I'd try to flash all the images manually on a Windows mashine, following this guide (section 10).
I did it many times this way without issues.

ulxerker said:
the system image always is too large and usually it gets transferred in smaller pieces automatically. I'd try to flash all the images manually on a Windows mashine, following this guide (section 10).
I did it many times this way without issues.
Click to expand...
Click to collapse
Well, I can't get it working on Windows at all, because the driver won't install. (At least I assume that's the reason why-- The driver won't install and fastboot won't show any devices.)
I tried fixing that, but with no luck.
I did also try section 10 from Ubuntu, with the same results for the system part:
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.284s]
sending sparse 'system' (514493 KB)...
OKAY [ 12.333s]
writing 'system'...
OKAY [ 3.149s]
sending sparse 'system' (514543 KB)...
OKAY [ 12.427s]
writing 'system'...
OKAY [ 3.117s]
sending sparse 'system' (524291 KB)...
FAILED (remote: data too large)
finished. total time: 31.327s

Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.

icrunchbanger said:
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
Click to expand...
Click to collapse
My gosh, that finally worked, and I didn't believe it would. I had thought that the one I had gotten from that PPA was the newest, but, apparently not. I actually got it directly from Google (which was a chore in itself, but outside the scope of this thread).
Thank you very much. Now, let's see if I can find out how to mark this as solved...

adanedhel728 said:
My gosh, that finally worked, and I didn't believe it would. I had thought that the one I had gotten from that PPA was the newest, but, apparently not. I actually got it directly from Google (which was a chore in itself, but outside the scope of this thread).
Thank you very much. Now, let's see if I can find out how to mark this as solved...
Click to expand...
Click to collapse
Your welcome. Never trust PPA ?

I got issuse
icrunchbanger said:
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
Click to expand...
Click to collapse
Bro link doesnt work, can you sent me app via email: [email protected]

suleymanov5 said:
Bro link doesnt work, can you sent me app via email: [email protected]
Click to expand...
Click to collapse
You can download android tools from Google
https://dl.google.com/android/repository/platform-tools-latest-linux.zip
Also you can check my github for some nifty scripts .
https://github.com/icrunchbanger/android

Pixel XL is bricked.

Hi folks. Friend managed to brick his pixel XL. Keeps booting into the no-command image, and cannot boot into safe mode. He would like to avoid factory resetting it as not all of his pictures are uploaded into his google drive. (He doesn't like the idea of big brother spying on him). Is there any way to recover the images?

How did he brick it?

ThatZeldaFan50 said:
Keeps booting into the no-command image
Click to expand...
Click to collapse
I can't think of what this is.
Are you talking about the android laying on its side like in my forum picture?
If the phone can be rebooted to Recovery mode, then your friend can use a Computer to transfer the files off the phone.

Mr. Orange 645 said:
How did he brick it?
Click to expand...
Click to collapse
He has no idea. According to him, it just happened during the day.
CZ Eddie said:
I can't think of what this is.
Are you talking about the android laying on its side like in my forum picture?
If the phone can be rebooted to Recovery mode, then your friend can use a Computer to transfer the files off the phone.
Click to expand...
Click to collapse
Sadly, he cannot boot into Recovery mode. It say "/cache not found" or something like that. Sorry, I don't have the phone with me, and I'm not at his house right now.

If he can get to Fastboot then he can flash the stock image on top of the current image without losing any setup apps/data/pics.
Just remove the -w from the script.
My guide will walk him through the process.
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Remember to remove the -w from the script though!
Or download the -w modded script I added to my thread.
If he can't get to either Fastboot OR Recovery then I'd consider that a "hard brick".
Are you sure he really knows how to boot to Fastboot and Recovery? Maybe he's doing that wrong. It's easy to mess up.

ThatZeldaFan50 said:
Keeps booting into the no-command image
Click to expand...
Click to collapse
Oh, is that the stock Recovery?
Cool.
He can use ADB from there to recover and transfer files & stuff.

CZ Eddie said:
If he can get to Fastboot then he can flash the stock image on top of the current image without losing any setup apps/data/pics.
Just remove the -w from the script.
My guide will walk him through the process.
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Remember to remove the -w from the script though!
Or download the -w modded script I added to my thread.
If he can't get to either Fastboot OR Recovery then I'd consider that a "hard brick".
Are you sure he really knows how to boot to Fastboot and Recovery? Maybe he's doing that wrong. It's easy to mess up.
Click to expand...
Click to collapse
If I am running Resurrection and I am on slot B, can just use the flashall in adb regardless of which slot I'm on?
Sent from my Pixel XL using XDA-Developers Legacy app

yankeesfan714 said:
If I am running Resurrection and I am on slot B, can just use the flashall in adb regardless of which slot I'm on?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've never tested that before.
It does write *something* to both slots though.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32980 KB)...
OKAY [ 0.909s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 4.709s]
finished. total time: 5.617s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.062s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio_a' (57192 KB)...
OKAY [ 1.445s]
writing 'radio_a'...
OKAY [ 0.570s]
finished. total time: 2.015s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1611091517
Baseband Version.....: 8996-012511-1611190200
Serial Number........: HT6920203793
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (26209 KB)...
OKAY [ 0.690s]
writing 'boot_a'...
OKAY [ 0.298s]
erasing 'system_a'...
OKAY [ 0.367s]
sending sparse 'system_a' 1/4 (515538 KB)...
OKAY [ 13.254s]
writing 'system_a' 1/4...
OKAY [ 5.541s]
sending sparse 'system_a' 2/4 (521786 KB)...
OKAY [ 13.566s]
writing 'system_a' 2/4...
OKAY [ 5.138s]
sending sparse 'system_a' 3/4 (491987 KB)...
OKAY [ 12.766s]
writing 'system_a' 3/4...
OKAY [ 6.688s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 0.848s]
writing 'system_a' 4/4...
OKAY [ 0.350s]
erasing 'system_b'...
OKAY [ 0.402s]
sending sparse 'system_b' 1/4 (517080 KB)...
OKAY [ 13.417s]
writing 'system_b' 1/4...
OKAY [ 3.986s]
sending sparse 'system_b' 2/4 (514384 KB)...
OKAY [ 13.119s]
writing 'system_b' 2/4...
OKAY [ 4.297s]
sending sparse 'system_b' 3/4 (524287 KB)...
OKAY [ 13.508s]
writing 'system_b' 3/4...
OKAY [ 3.888s]
sending sparse 'system_b' 4/4 (85782 KB)...
OKAY [ 2.247s]
writing 'system_b' 4/4...
OKAY [ 0.810s]
erasing 'vendor_a'...
OKAY [ 0.153s]
sending 'vendor_a' (235322 KB)...
OKAY [ 5.841s]
writing 'vendor_a'...
OKAY [ 3.752s]
Setting current slot to 'a'...
OKAY [ 0.058s]
erasing 'userdata'...
OKAY [ 2.286s]
sending 'userdata' (138957 KB)...
OKAY [ 3.450s]
writing 'userdata'...
OKAY [ 1.300s]
rebooting...
finished. total time: 132.460s
Press any key to exit...

yankeesfan714 said:
If I am running Resurrection and I am on slot B, can just use the flashall in adb regardless of which slot I'm on?
Click to expand...
Click to collapse
It doesn't matter which slot you're on. You can use the flash all. It will automatically flash to the active slot.

Soft/Hard Brick help needed please

From the start: I was previously running the PixelDust ROM and wanted to try the 11 preview so i attempted to flash it via ADB commands. Script ran through the first time and finished overall but had some failed parts under the formatting section and rewriting partitions. With the first time using it i did forget to take out the -W string, well i purposely left it as i dont mind resetting the phone. Fast forward 8 hours, my phone still wont boot past the white google screen after NUMEROUS retries with flashing the 11 preview through ADB as well as using the flash-all. It also now shows the RED "your device is corrupted" screen on initial boot (not the standard yellow warning after unlocking) and seems like it bootloops to the bootloader or google screen and stays there. ANY help greatly appreciated.

Currently trying to use the Deuces flash-all script and latest version of Android 10. Will report

Welcome to Deuces Flashing Script!
v5.0-Windows
Checking if Fastboot exe is accessible..
Checking if Fastboot works correctly
fastboot version eac51f2bb6a8-android
Fastboot Detected!
Checking if device is detected via Fastboot.
Device Detected in Fastboot!
Are you SURE you want to continue?
Press Enter to continue...:
This tool will reformat partitions in your device!
It will attempt to keep your user data!
Data could be lost! - Use At Your Own Risk!
Continue? (y/N) y
Checking if bootloader is unlocked.
Look at device to confirm if script is waiting...
Preparing files for flash...
Extracting C:\Users\Tiffany\Downloads\Deuces-Bootloop-Recovery-Flashing-Script-master\Deuces-Bootloop-Recovery-Flashing-Script-master\taimen110.zip...
target reported max download size of 536870912 bytes
sending 'bootloader' (36356 KB)...
OKAY [ 0.940s]
writing 'bootloader'...
OKAY [ 0.388s]
finished. total time: 1.412s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 0.576s]
finished. total time: 2.198s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.008s
Extracting C:\Users\Tiffany\Downloads\Deuces-Bootloop-Recovery-Flashing-Script-master\Deuces-Bootloop-Recovery-Flashing-Script-master\_work\taimen-qq2a.200501.001.b3\image-taimen-qq2a.200501.001.b3.zip.
Flashing B-Slot items first.
target reported max download size of 536870912 bytes
erasing 'system_b'...
OKAY [ 0.033s]
sending 'system_b' (313556 KB)...
OKAY [ 8.515s]
writing 'system_b'...
OKAY [ 1.475s]
finished. total time: 10.358s
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.086s]
writing 'boot'...
OKAY [ 0.372s]
finished. total time: 1.462s
target reported max download size of 536870912 bytes
sending 'dtbo' (8192 KB)...
OKAY [ 0.217s]
writing 'dtbo'...
OKAY [ 0.079s]
finished. total time: 0.302s
target reported max download size of 536870912 bytes
sending sparse 'system' (524284 KB)...
OKAY [ 26.436s]
writing 'system'...
OKAY [ 2.457s]
sending sparse 'system' (524284 KB)...
OKAY [ 25.678s]
writing 'system'...
OKAY [ 2.472s]
sending sparse 'system' (524284 KB)...
OKAY [ 24.613s]
writing 'system'...
OKAY [ 2.464s]
sending sparse 'system' (524284 KB)...
OKAY [ 25.794s]
writing 'system'...
OKAY [ 2.462s]
sending sparse 'system' (340260 KB)...
OKAY [ 15.858s]
writing 'system'...
OKAY [ 1.593s]
finished. total time: 129.943s
target reported max download size of 536870912 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.004s]
writing 'vbmeta'...
OKAY [ 0.006s]
finished. total time: 0.012s
target reported max download size of 536870912 bytes
sending 'vendor' (349176 KB)...
OKAY [ 9.269s]
writing 'vendor'...
OKAY [ 1.645s]
finished. total time: 10.922s
Format UserData? (y/N) n
Done!
Press Enter to continue...:

Android 10 worked....

Blu G5 "data too large"?

Update: Worked through many issues below. Latest issue is that all AOSP images that I've tried so far are having infinite boot loops with recovery mode unavailable, but I am now able to revert to stock.
-----------------------------
Blu G5 "data too large"?
Hi! I'm trying to flash Treble AOSP (Android 10 or 11) to a Blu G5 dual-SIM (originally Android 9 Pie) GSM/HSPA/LTE phone. It's got a Unisoc SC9863A Octa-Core 1.6GHz ARM Cortex-A55 chipset, 2 GB of RAM and 32 GB of internal storage. The treblechecker app said it's A-only (single partition) ARM64.
I started with a factory reset, then used adb and a modified fastboot (from Hovatek) under linux to get the identifier token and unlock the bootloader. The issue is that every system image that I've tried to flash failed due to "data too large", and some were even smaller than the stock image!
Code:
[email protected]:~/Desktop/Blu-G5-AndroidUpgrade/platform-tools_r31.0.2-linux/platform-tools# ./fastboot flash system system-roar-arm64-aonly-vanilla.img
target didn't report max-download-size
sending 'system' (1745204 KB)...
FAILED (remote: data too large)
finished. total time: 0.001s
Since there was a newer (r31.0.3) version of fastboot for Windows, I tried that but I'm still getting the same failure:
Code:
C:\platform-tools>fastboot flash system system-arm64-aonly-vanilla-nosu.img
Sending 'system' (1282352 KB) FAILED (remote: 'data too large')
fastboot: error: Command failed
So far, I've tried each of the following separately, but each just hangs on this phone:
Code:
C:\platform-tools>fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta' ^C
Code:
C:\platform-tools>fastboot delete-logical-partition product
Deleting 'product' ^C
Any ideas?
EDIT 1: This is what worked to flash it with AOSP 11.0 v312 (although now it's in an infinite boot loop so I guess I shouldn't have skipped over AOSP 10):
Code:
C:\platform-tools>fastboot -S 300M flash system system-roar-arm64-aonly-gapps.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/9 (307196 KB) FAILED (remote: 'data too large')
fastboot: error: Command failed
C:\platform-tools>fastboot -S 256M flash system system-roar-arm64-aonly-gapps.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/10 (262108 KB) OKAY [ 11.080s]
Writing 'system' OKAY [ 9.083s]
Sending sparse 'system' 2/10 (262112 KB) OKAY [ 11.067s]
Writing 'system' OKAY [ 9.002s]
Sending sparse 'system' 3/10 (262100 KB) OKAY [ 11.080s]
Writing 'system' OKAY [ 14.711s]
Sending sparse 'system' 4/10 (262124 KB) OKAY [ 11.075s]
Writing 'system' OKAY [ 8.981s]
Sending sparse 'system' 5/10 (262128 KB) OKAY [ 11.082s]
Writing 'system' OKAY [ 8.940s]
Sending sparse 'system' 6/10 (262128 KB) OKAY [ 11.074s]
Writing 'system' OKAY [ 8.937s]
Sending sparse 'system' 7/10 (262120 KB) OKAY [ 11.079s]
Writing 'system' OKAY [ 9.004s]
Sending sparse 'system' 8/10 (256832 KB) OKAY [ 10.940s]
Writing 'system' OKAY [ 15.842s]
Sending sparse 'system' 9/10 (262142 KB) OKAY [ 11.120s]
Writing 'system' OKAY [ 11.342s]
Sending sparse 'system' 10/10 (131693 KB) OKAY [ 5.578s]
Writing 'system' OKAY [ 5.648s]
Finished. Total time: 209.427s
Of course it can't connect by adb, and when I try to get it into recovery mode (by Volume Up + Power buttons together until recovery mode screen appears, then when you see the BLU logo release the Power button, but keep holding Volume Up until the recovery mode screen comes), it just freezes. Any unbricking ideas?
EDIT 2: I've just tried the SPD Upgrade Tool (SPDFlashTool.com) R25.20.3901 with the stock ROM BLU_G0090_V9.0.04.04, but the tool can't seem to access the phone during the infinite boot loops or when I freeze it my trying to enter recovery mode...
EDIT 3: I guess it was only soft-bricked since unbricked once with battery pull then Vol-DOWN and Power until knocked down Android ("No Command") icon showed for an instant, then used SPD Upgrde Tool for back to stock. Loaded stock, set USB debugging, used cmd for abd and tried to reboot to fastboot, but it entered bootloop so bricked again. It's almost as if these might have A/B boot partitions after all, but I don't know how to switch between them. I'll try again later...
EDIT 4: Got back to stock with SPD Upgrade Tool again and all seemed fine. Factory Reset, and enabled USB debugging. Then flashed to AOSP 10.0 v201 this time, but got an infinite boot loop with no recovery mode again. Anyone know what I'm doing wrong? At least I found a way to get back to stock more easily afterwards by priming SPD Upgrade then holding power and volume buttons between the automatic reboots until the stock firmware started reflashing.
Code:
Microsoft Windows [Version 10.0.19043.1237]
(c) Microsoft Corporation. All rights reserved.
C:\platform-tools>adb devices -l
List of devices attached
[16 digits redacted] device product:BLU_G5 model:G5 device:G0090 transport_id:1
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot devices
[16 digits redacted] fastboot
C:\platform-tools>fastboot flash -S 256M system system-arm64-aonly-vanilla-nosu.img
Sending sparse 'system' 1/5 (262140 KB) OKAY [ 11.697s]
Writing 'system' OKAY [ 8.947s]
Sending sparse 'system' 2/5 (262140 KB) OKAY [ 11.662s]
Writing 'system' OKAY [ 8.923s]
Sending sparse 'system' 3/5 (262140 KB) OKAY [ 11.703s]
Writing 'system' OKAY [ 8.914s]
Sending sparse 'system' 4/5 (262140 KB) OKAY [ 11.755s]
Writing 'system' OKAY [ 8.919s]
Sending sparse 'system' 5/5 (233792 KB) OKAY [ 10.400s]
Writing 'system' OKAY [ 7.957s]
Finished. Total time: 100.914s
C:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s

Question "No command" screen after installing custom rom

Hello lads, after trying trying to install multiple android 13 custom roms I have issue booting my phone. Keep getting this annoying "no command" screen after it tries to reboot few times. Could anyone help me with this one ? I know that issue should be very easy resolvable. My daily driver used to be stock most recent (not beta) firmware.

naujokellis said:
Hello lads, after trying trying to install multiple android 13 custom roms I have issue booting my phone. Keep getting this annoying "no command" screen after it tries to reboot few times. Could anyone help me with this one ? I know that issue should be very easy resolvable. My daily driver used to be stock most recent (not beta) firmware.
Click to expand...
Click to collapse
Did you erase your boot image by chance? Reflash /boot and /init_boot

Ok, i will do. I havent deleted it for sure, but i did flashed bootloader to all slots, would that could effect booting up ? as i have some errors during installation of custom ROM, but installation finished with successful message.
BTW with original firmware it booted up without a problem. And I still used stock firmware for another day after playing with bootloader or boot files.
Bootloader Version...: slider-1.2-9152140
Baseband Version.....: g5123b-107485-221101-B-9242015
Serial Number........: 1A281FDEE007L3
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.089s]
extracting boot.img (64 MB) to disk... took 0.286s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.350s]
Writing 'boot_b' OKAY [ 0.079s]
extracting dtbo.img (16 MB) to disk... took 0.069s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.566s]
Writing 'dtbo_b' OKAY [ 0.022s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.002s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_b' OKAY [ 0.002s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.020s]
Resizing 'product_b' OKAY [ 0.003s]
Resizing 'system_b' OKAY [ 0.002s]
Resizing 'system_a' OKAY [ 0.003s]
Resizing 'vendor_b' OKAY [ 0.002s]
Resizing 'vendor_a' OKAY [ 0.002s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (2234 MB) to disk... took 12.826s
Invalid sparse file format at header magic
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.005s]
Sending sparse 'product_b' 1/9 (261666 KB) OKAY [ 9.032s]
Writing 'product_b' OKAY [ 0.457s]
Sending sparse 'product_b' 2/9 (261399 KB) OKAY [ 9.334s]
Writing 'product_b' OKAY [ 0.495s]
Sending sparse 'product_b' 3/9 (260861 KB) OKAY [ 9.410s]
Writing 'product_b' OKAY [ 0.473s]
Sending sparse 'product_b' 4/9 (261912 KB) OKAY [ 9.286s]
Writing 'product_b' OKAY [ 0.471s]
Sending sparse 'product_b' 5/9 (262080 KB) OKAY [ 9.405s]
Writing 'product_b' OKAY [ 0.462s]
Sending sparse 'product_b' 6/9 (261344 KB) OKAY [ 9.402s]
Writing 'product_b' OKAY [ 0.550s]
Sending sparse 'product_b' 7/9 (261391 KB) OKAY [ 9.325s]
Writing 'product_b' OKAY [ 0.498s]
Sending sparse 'product_b' 8/9 (256403 KB) OKAY [ 9.318s]
Writing 'product_b' OKAY [ 0.633s]
Sending sparse 'product_b' 9/9 (183972 KB) OKAY [ 6.660s]
Writing 'product_b' OKAY [ 0.356s]
archive does not contain 'product_services.img'
extracting system.img (967 MB) to disk... took 4.577s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.007s]
Sending sparse 'system_b' 1/4 (262108 KB) OKAY [ 9.344s]
Writing 'system_b' OKAY [ 0.451s]
Sending sparse 'system_b' 2/4 (254041 KB) OKAY [ 9.211s]
Writing 'system_b' OKAY [ 1.016s]
Sending sparse 'system_b' 3/4 (261996 KB) OKAY [ 9.528s]
Writing 'system_b' OKAY [ 0.433s]
Sending sparse 'system_b' 4/4 (200872 KB) OKAY [ 7.233s]
Writing 'system_b' OKAY [ 0.374s]
extracting system_other.img (20 MB) to disk... took 0.141s
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.007s]
Sending 'system_a' (21248 KB) OKAY [ 0.766s]
Writing 'system_a' OKAY [ 0.092s]
extracting vendor.img (534 MB) to disk... took 2.574s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
Resizing 'vendor_b' OKAY [ 0.006s]
Sending sparse 'vendor_b' 1/3 (259740 KB) OKAY [ 9.475s]
Writing 'vendor_b' OKAY [ 0.467s]
Sending sparse 'vendor_b' 2/3 (262132 KB) OKAY [ 9.323s]
Writing 'vendor_b' OKAY [ 0.483s]
Sending sparse 'vendor_b' 3/3 (21572 KB) OKAY [ 0.764s]
Writing 'vendor_b' OKAY [ 0.100s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 0.163s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.004s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting OKAY [ 0.000s]
Finished. Total time: 189.359s

naujokellis said:
Hello lads, after trying trying to install multiple android 13 custom roms I have issue booting my phone. Keep getting this annoying "no command" screen after it tries to reboot few times. Could anyone help me with this one ? I know that issue should be very easy resolvable. My daily driver used to be stock most recent (not beta) firmware.
Click to expand...
Click to collapse
Sounds like the stock android recovery. If you see the above, just hold power and volume up to enter recovery.

jamescable said:
Sounds like the stock android recovery. If you see the above, just hold power and volume up to enter recover
Click to expand...
Click to collapse
OK, this is the screen I am getting, but I am looking for solution why any custom rom does not run on my phone. I know that installing stock firmware would fix issue, but i do not want to use stock firmware. I will try to install stock firmware and reinstall custom ROM later, but i do not think that would fix issue I am having.

naujokellis said:
OK, this is the screen I am getting, but I am looking for solution why any custom rom does not run on my phone. I know that installing stock firmware would fix issue, but i do not want to use stock firmware. I will try to install stock firmware and reinstall custom ROM later, but i do not think that would fix issue I am having.
Click to expand...
Click to collapse
It may help others to help you if you describe in detail (e.g. exact steps and commands used, etc.) your method of installation and any other pertinent details, such as version of Platform Tools used, etc..

naujokellis said:
OK, this is the screen I am getting, but I am looking for solution why any custom rom does not run on my phone. I know that installing stock firmware would fix issue, but i do not want to use stock firmware. I will try to install stock firmware and reinstall custom ROM later, but i do not think that would fix issue I am having.
Click to expand...
Click to collapse
Use android recovery to wipe data and see if that works

jamescable said:
Use android recovery to wipe data and see if that works
Click to expand...
Click to collapse
did that multiple times before installing every custom ROM

Lughnasadh said:
It may help others to help you if you describe in detail (e.g. exact steps and commands used, etc.) your method of installation and any other pertinent details, such as version of Platform Tools used, etc..
Click to expand...
Click to collapse
Im using Linux Mint 21.1
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/adb
commands used before reinstalling stock firmware:this and this thread
after reinstalling latest stock firmware (canceling beta version) only used guides how to install custom rom using fastboot mode. ( fastboot update rom.zip )
I have a questio tho, do i need to root my phone with magisk before being able to install custom rom ? I feel like I am missing something, thats why it does not work

naujokellis said:
Im using Linux Mint 21.1
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/adb
commands used before reinstalling stock firmware:this and this thread
after reinstalling latest stock firmware (canceling beta version) only used guides how to install custom rom using fastboot mode. ( fastboot update rom.zip )
Click to expand...
Click to collapse
That could be the issue, idk. I have always used windows. I know some people have issues with Mac and Linux so...

jamescable said:
That could be the issue, idk. I have always used windows. I know some people have issues with Mac and Linux so...
Click to expand...
Click to collapse
That would be insane, as I would have had issues before, linux is my daily driver

naujokellis said:
That would be insane, as I would have had issues before, linux is my daily driver
Click to expand...
Click to collapse
Then idk. I have been flashing Roms since Motorola droid 1 android froyo days and have heard of numerous people having some weird issue with Linux one time or another

naujokellis said:
Version 28.0.2-debian
Click to expand...
Click to collapse
Is that Platform Tools version 28.0.2? If so, that's like 4 years old. The latest Platform Tools version is 33.0.3.

Lughnasadh said:
Is that Platform Tools version 28.0.2? If so, that's like 4 years old. The latest Platform Tools version is 33.0.3.
Click to expand...
Click to collapse
OK, i will double check on that and I will update platform tools