Related
I'm trying to root my phone, but I can't flash any boot or recovery images to it, whether that's the patched boot.img, TWRP, or even the stock factory images themselves. I've already unlocked the bootloader, using
Code:
fastboot flashing unlock_critical
.
I am running the newest version of adb and fastboot, downloaded yesterday:
Code:
$ fastboot --version
fastboot version 0.0.1-4500957
Installed as [REDACTED]
$ adb version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as [REDACTED]
When I try to flash the stock factory images, downloaded straight from Google, I get this series of errors:
Code:
$ adb reboot bootloader
$ ./flash-all.sh
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.201s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.201s
extracting android-info.txt (0 MB) to RAM...
Warning: Could not determine slot for secondary images. Ignoring.
extracting boot.img (40 MB) to disk... took 0.289s
target didn't report max-download-size
archive does not contain 'boot.sig'
extracting dtbo.img (8 MB) to disk... took 0.039s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1936 MB) to disk...
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 (349 MB) to disk... took 4.445s
error: Failed to identify current slot
Other fastboot commands also fail with inconsistent error messages and failure modes:
Code:
$ fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (40960 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s
If I try with the -S flag:
Code:
$ fastboot -S 512K flash boot boot.img
Invalid sparse file format at header magic
sending sparse 'boot' 1/51 (508 KB)...
which hangs indefinitely, never sending even the first segment.
I can try booting directly, which yields the same problem:
Code:
$ fastboot boot boot.img
downloading 'boot.img'...
# hangs indefinitely
Similarly,
Code:
$ fastboot --set-active=_a
hangs indefinitely as well. I have to restart the bootloader to kill it, at which point it just prints the confusing error:
Code:
Device does not support slots
(the Pixel 2 XL does support slots!).
The error messages aren't always consistent; sometimes the first fastboot flash boot boot.img command will appear to hang (requiring a restart, similar to
Code:
--set-active
) instead of printing the error message about max-download-size. I've let that run for about fifteen minutes before having to kill it. Unlike system.img, boot.img is only about 40MB, so it shouldn't take that long to flash - something is clearly wrong.
I've also tried this with multiple cables on different USB ports, with the same sorts of results each time.
Am I missing a step? How can I flash the factory images and the patched boot.img?
Most likely not model specific issue but the Pixel-2XL forum:
https://forum.xda-developers.com/pixel-2-xl/help
i have the same problem, and it seems nothing works, tried every single solution on the internet i could find, multiple cables, adb/fastboot up to date
exact same problem as OP
chimeracoder said:
I'm trying to root my phone, but I can't flash any boot or recovery images to it, whether that's the patched boot.img, TWRP, or even the stock factory images themselves. I've already unlocked the bootloader, using
Code:
fastboot flashing unlock_critical
.
Click to expand...
Click to collapse
You're in the wrong forum, using the wrong unlock command, depending on whether you have Pixel 2 or Pixel 2 XL and likely using the wrong factory image too.
You're in the Pixel 2 forum (5" model), not Pixel 2 XL (6" model). You need to go here; https://forum.xda-developers.com/pixel-2-xl/help
You need to make sure you enable developer option on phone first - then in developer option, tick - allow OEM Unlocking, and USB debugging
then it should allow you to go ahead as you have.
Check this out here. Your issue happens when you play around with the bootloader settings and something gets borked. This tool saved me from having to RMA.
EDIT: Never mind, the culprit was the USB C x USB C cable I was using at the office. Back home, I used my USB A x USB C cable and was able to recover the device.
I'm having the exact same problem! I have a Pixel 2, at January 8.1.0 version (OPM1.171019.013). It was rooted with Magisk latest version. Today I decided to reflash the firmware, without wipe, and the flashing was not successful. Now I'm afraid I have a small brick in my hands.
I'm now using the latest fastboot (0.0.1-4500957) and adb (1.0.39 / 0.0.1-4500957) versions. I don't know if I was on the latest versions when I tried to flash the firmware.
I always flashed the firmware using a USB A port on my Dell XPS 9560 notebook. Today I flashed from a USB C port, I don't know if this was the cause for the failed flash. I'm at the office, and I don't have a USB A x USB C cable available.
My Pixel 2 is stuck at the bootloader. Recovery mode and Download mode options don't do anything, it just goes back to the bootloader screen. Bootloader version is mw8998-002.0059.00. It tells me I'm on slot b, and I can't change slots, issuing fastboot --set-active=a either returns:
Code:
error: Device does not support slots
OR:
Code:
FAILED (remote: unknown command)
When I issue fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img either one of these messages is displayed:
Code:
error: Failed to identify current slot
OR:
Code:
target didn't report max-download-size
sending 'bootloader' (38644 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
Has anyone found a solution?
same problem。
could you solve it?
opooi said:
same problem。
could you solve it?
Click to expand...
Click to collapse
As the post above yours suggests, swap out USB cables.
If that doesn't resolve the issue, try these:
-make sure your SDK tools are up to date
-make sure your files are in the correct "platform tools" folder for using fastboot
-make sure your fastboot commands are correct
There is a link to a Pixel 2 XL "guide" in my sig, it covers most issues and processes for the 2 XL.
Az Biker said:
As the post above yours suggests, swap out USB cables.
If that doesn't resolve the issue, try these:
-make sure your SDK tools are up to date
-make sure your files are in the correct "platform tools" folder for using fastboot
-make sure your fastboot commands are correct
There is a link to a Pixel 2 XL "guide" in my sig, it covers most issues and processes for the 2 XL.
Click to expand...
Click to collapse
yes，i use platform-tools_r28.0.0-linux to fastboot,but it still failed.
I compiled AOSP to run "fastboot flashall -w" for pixel 2 xl.it showed:
target reported max download size of 536870912 bytes
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Warning: RAID stripe-width 1 not an even multiple of stride 2.
Creating filesystem with 13902843 4k blocks and 3481600 inodes
Filesystem UUID: e8137926-c3cb-4ddc-bdd1-311c79ed416c
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Bootloader Version...: TMZ12a
Baseband Version.....: g8998-00164-1710262031
Serial Number........: 710KPCA0244667
checking product...
OKAY [ 0.000s]
sending 'boot_b' (40960 KB)...
FAILED (data write failure (Protocol error))
finished. total time: 0.162s
Click to expand...
Click to collapse
i feel sad to cry,but i can't solve it
@opooi have you made any progress on fixing it? I've had the exact same issue even with the commands hanging. I fixed it somehow, I don't remember how. I think I booted stock recovery and factory reset. I also tried different images and cleaning my driver's and starting fresh. I was going crazy trying everything I could ever think of and then it just flashed. I'm so scared about it happening again. Also another thing to try, try to reboot bootloader a couple times back to back and see if it helps.
Some guy on Reddit just said he uninstalled magisk, then ran the flash-all and his phone started having this issue. It happened to me when I booted twrp, wiped system data cache and then booted to bootloader and tried to flash.
Is it possible to edit the updater-script from a trebalized rom in order to update my vendor and kernel without touching /system?
I think I can probably figure out how to edit the script myself, but I am curious whether anyone has done this. Thanks.
Could you not just find the vendor and kernel images and flash them to their correct partitions using TWRP?
For A-only, devices, yes it should be possible and very easy
For A/B, everything is packed inside payload.bin, so it would be more complicated
(I have somewhere in my todolist to support flashing portion of payload.bin, and copying my own GSI for OTAs, or the other way around, but that's far from now)
But yeah as @ambitiousButRubbish mentions, the easiest is to go through fastboot
Thank both of you for your very helpful answers.
As for flashing the images separately through TWRP or fastboot, when I look inside the zip of a trebalized rom I see "boot.img" which should be flashable for the kernel, but for vendor I see "vendor.new.dat.br", "vendor.patch.dat", and "vendor.transfer.list". How do I flash these to my vendor partition?
And for clarification, yes I am looking at trebalized roms for A-only devices. I did not realize the complications that come into play for A/B.
fastboot flash kernel KERNEL_updated.img
Code:
Sending 'kernel' (24576 KB) OKAY [ 0.684s]
Writing 'kernel' OKAY [ 0.360s]
Finished. Total time: 1.058s
fastboot flash vendor VENDOR_updated.img
Code:
Sending sparse 'vendor' 1/2 (460055 KB) OKAY [ 11.034s]
Writing sparse 'vendor' 1/2 FAILED (remote: 'Command not allowed')
Finished. Total time: 11.066s
Device stuck at "untrusted", reflash original KERNEL.img fixed it.
So, not that easy then?
Mate 9, A only, OmniROM Alpha 3, B375 base, tried to update to B379
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7T in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 7T to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=300020
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
Unfortunately i have not tested this fastboot rom, i did some tests with an user and nothing else, actually you can't flash from normal fastboot mode system, vendor and product images, you need to use "fastboot reboot fastboot" command to reboot in stock recovery with fastbootd enabled, after that using the fastboot commands you can flash system, vendor and product images.
If you have any problems with this fastboot rom or you see errors during the script execution, contact me
Really thanks for this.
Any update on root ?
RohanAJoshi said:
Really thanks for this.
Any update on root ?
Click to expand...
Click to collapse
Unfortunately no, i will check in the next hours, but without a tester should be not easy
mauronofrio said:
Unfortunately no, i will check in the next hours, but without a tester should be not easy
Click to expand...
Click to collapse
I have device.
I can test.
I will pm you my telegram id.
Please check.
Edit : can't pm
My telegram id
RohanAJoshi7
"This will work only if your bootloader is unlocked."
Supposed someone gets into trouble - as seen in another thread with a bricked device.
Wouldn't that happen usually if the bootloader is unlocked?
Like if someone want to do some modifications/tweaking, I believe it requuires to unlock the bootloader.
What other scenario could be happening to get into issues with and locked bootloader?
Please excuse the lack of knowledge on a/b partitions and stuff.
Thank you.
Wifi and speaker did not work anymore after messing with the magisk compatible boot image and/or update to 10.0.3. This fixed it for me, thanks!
Small note though, I was using older drivers which caused some errors while running the bat script. Namely "Flashing is not allowed for Critical Partitions" and " Failed to boot into userspace fastboot; one or more components might be unbootable". After running the 15 seconds adb installer and running the script again everything worked fine: https://forum.xda-developers.com/showthread.php?t=2588979
Rescla said:
Wifi and speaker did not work anymore after messing with the magisk compatible boot image and/or update to 10.0.3. This fixed it for me, thanks!
Small note though, I was using older drivers which caused some errors while running the bat script. Namely "Flashing is not allowed for Critical Partitions" and " Failed to boot into userspace fastboot; one or more components might be unbootable". After running the 15 seconds adb installer and running the script again everything worked fine: https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
please help me Bro My wifi is not working and if someone calls me it auto rejected all call
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.421s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 56734085 4k blocks and 14188544 inodes
Filesystem UUID: 63051112-f179-11e9-b2d0-d132c7036180
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (5024 KB) OKAY [ 0.125s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'metadata' OKAY [ 0.016s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.638s
Sending 'aop' (200 KB) OKAY [ 0.016s]
Writing 'aop' OKAY [ 0.000s]
Finished. Total time: 0.031s
Sending 'bluetooth' (828 KB) OKAY [ 0.031s]
Writing 'bluetooth' OKAY [ 0.000s]
Finished. Total time: 0.078s
Sending 'boot_a' (98304 KB) OKAY [ 2.215s]
Writing 'boot_a' OKAY [ 0.421s]
Finished. Total time: 4.072s
Sending 'dsp' (65536 KB) OKAY [ 1.466s]
Writing 'dsp' OKAY [ 0.234s]
Finished. Total time: 2.496s
Sending 'cmnlib' (384 KB) OKAY [ 0.016s]
Writing 'cmnlib' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.031s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.000s]
Writing 'devcfg' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
sandeep chauhan 2722 said:
please help me Bro My wifi is not working and if someone calls me it auto rejected all call
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.421s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 56734085 4k blocks and 14188544 inodes
Filesystem UUID: 63051112-f179-11e9-b2d0-d132c7036180
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (5024 KB) OKAY [ 0.125s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'metadata' OKAY [ 0.016s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.638s
Sending 'aop' (200 KB) OKAY [ 0.016s]
Writing 'aop' OKAY [ 0.000s]
Finished. Total time: 0.031s
Sending 'bluetooth' (828 KB) OKAY [ 0.031s]
Writing 'bluetooth' OKAY [ 0.000s]
Finished. Total time: 0.078s
Sending 'boot_a' (98304 KB) OKAY [ 2.215s]
Writing 'boot_a' OKAY [ 0.421s]
Finished. Total time: 4.072s
Sending 'dsp' (65536 KB) OKAY [ 1.466s]
Writing 'dsp' OKAY [ 0.234s]
Finished. Total time: 2.496s
Sending 'cmnlib' (384 KB) OKAY [ 0.016s]
Writing 'cmnlib' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.031s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.000s]
Writing 'devcfg' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
Click to expand...
Click to collapse
And others partitions?
mauronofrio said:
And others partitions?
Click to expand...
Click to collapse
flashing process stop here.
i also try to flash manually but when I give 4th command to flash "fastboot flash cmnlib cmnlib.img" it gives me error now I cany use my phone no sound no wifi no calls please help me
sandeep chauhan 2722 said:
flashing process stop here.
i also try to flash manually but when I give 4th command to flash "fastboot flash cmnlib cmnlib.img" it gives me error now I cany use my phone no sound no wifi no calls please help me
Click to expand...
Click to collapse
if some partition fail is not a problem, you should wait a bit
Found Solution
I download this file from support one plus https://support.oneplus.com/app/answers/detail/a_id/4583/kw/7t and install it from as Local upgrade from system update ( While bootloader is still unlock) and after it completed I reboot my device and Volla!! It works. I was also thinking to sideload same file in case local upgrade not work.
I am getting
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784696 KB) OKAY [ 18.274s]
Writing 'system' FAILED (remote: 'Partition not found')
ANy ideas???
I can flash other partitions though
suzook said:
I am getting
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784696 KB) OKAY [ 18.274s]
Writing 'system' FAILED (remote: 'Partition not found')
ANy ideas???
I can flash other partitions though
Click to expand...
Click to collapse
when the device reboot itself in recovery doesn't touch it.
mauronofrio said:
when the device reboot itself in recovery doesn't touch it.
Click to expand...
Click to collapse
I just tried fastboot flash system...it wouldnt work. But what di was the flashall. Thanks
After flashing the stock rom it boots up and everything seems fine. When I try to lock the bootloader I get the "Your device is corrupt. It can´t be trusted anymore and will not boot" I've unlocked the bootloader a few times tried reflashing stock rom but everytime I lock the bootloader I get that error message. Any ideas?
***Downloaded and Installed the stock rom through the system update in settings menu. Locked the bootloader without issues afterwards***
954wrecker said:
After flashing the stock rom it boots up and everything seems fine. When I try to lock the bootloader I get the "Your device is corrupt. It can´t be trusted anymore and will not boot" I've unlocked the bootloader a few times tried reflashing stock rom but everytime I lock the bootloader I get that error message. Any ideas?
***Downloaded and Installed the stock rom through the system update in settings menu. Locked the bootloader without issues afterwards***
Click to expand...
Click to collapse
So after flashed this fastboot rom, you should local update the original .zip rom to be sure that all partitions are replaced
I am stuck on the "The boot loader is unlocked....." and i tried to flash this but i am getting too many errors and post reboot its back on the same screen. Can anybody please help me?
Creating filesystem with parameters:
Size: 232382812160
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 56734085
Block groups: 1732
Reserved block group size: 1024
Created filesystem with 11/14188544 inodes and 938604/56734085 blocks
target reported max download size of 805306368 bytes
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 0.688s]
sending 'userdata' (152025 KB)...
OKAY [ 3.922s]
writing 'userdata'...
OKAY [ 0.000s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 8.001s
error: cannot load 'aop.img'
error: cannot load 'bluetooth.img'
error: cannot load 'boot.img'
error: cannot load 'dsp.img'
error: cannot load 'cmnlib.img'
error: cannot load 'cmnlib64.img'
error: cannot load 'devcfg.img'
error: cannot load 'dtbo.img'
error: cannot load 'LOGO.img'
error: cannot load 'modem.img'
error: cannot load 'oem_stanvbk.img'
error: cannot load 'qupfw.img'
error: cannot load 'storsec.img'
error: cannot load 'multiimgoem.img'
error: cannot load 'hyp.img'
error: cannot load 'imagefv.img'
error: cannot load 'keymaster.img'
error: cannot load 'uefisecapp.img'
error: cannot load 'recovery.img'
fastboot: unknown option -- disable-verity
fastboot: unknown option -- disable-verity
error: cannot load 'opproduct.img'
error: cannot load 'tz.img'
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
error: cannot load 'system.img'
error: cannot load 'vendor.img'
error: cannot load 'product.img'
rebooting...
sathya said:
I am stuck on the "The boot loader is unlocked....." and i tried to flash this but i am getting too many errors and post reboot its back on the same screen. Can anybody please help me?
Creating filesystem with parameters:
Size: 232382812160
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 56734085
Block groups: 1732
Reserved block group size: 1024
Created filesystem with 11/14188544 inodes and 938604/56734085 blocks
target reported max download size of 805306368 bytes
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 0.688s]
sending 'userdata' (152025 KB)...
OKAY [ 3.922s]
writing 'userdata'...
OKAY [ 0.000s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 8.001s
error: cannot load 'aop.img'
error: cannot load 'bluetooth.img'
error: cannot load 'boot.img'
error: cannot load 'dsp.img'
error: cannot load 'cmnlib.img'
error: cannot load 'cmnlib64.img'
error: cannot load 'devcfg.img'
error: cannot load 'dtbo.img'
error: cannot load 'LOGO.img'
error: cannot load 'modem.img'
error: cannot load 'oem_stanvbk.img'
error: cannot load 'qupfw.img'
error: cannot load 'storsec.img'
error: cannot load 'multiimgoem.img'
error: cannot load 'hyp.img'
error: cannot load 'imagefv.img'
error: cannot load 'keymaster.img'
error: cannot load 'uefisecapp.img'
error: cannot load 'recovery.img'
fastboot: unknown option -- disable-verity
fastboot: unknown option -- disable-verity
error: cannot load 'opproduct.img'
error: cannot load 'tz.img'
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
error: cannot load 'system.img'
error: cannot load 'vendor.img'
error: cannot load 'product.img'
rebooting...
Click to expand...
Click to collapse
You should extract all the rom
soft bricked oneplus 7t
mauronofrio said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7T in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 7T to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=300020
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
Click to expand...
Click to collapse
Hi mauronofrio
I downloaded your version of twrp for my oneplus 7t and unlocked the bootloader in an attempt to change to Oxygen OS. Unfortunately the system, vendor and product partitions are locked and 0MB so seem to be stuck, can write to the /recovery directory but that's about it. I try to flash it but always get the mount error on those directories. I downloaded the rom in this post and extracted to a folder but not quite clear how to run the bat command.
Any clues or tips would be most appreciated. By the way I somehow deleted the recovery rom so can't even boot into Hydrogen OS anymore.
thanks
Dave
so I am trying to flash system_ext, product, and odm to fix a strange issue I have, and I am getting this fastboot error whenever I try to flash any of those partitions, and they are fresh out of a payload dump of the oos currently on my phone (11.2.4.4)
flash odm odm.img
target reported max download size of 805306368 bytes
sending 'odm' (55656 KB)...
OKAY [ 1.695s]
writing 'odm'...
FAILED (remote: (odm_a) No such partition)
finished. total time: 1.701s
how is it that I do not have an odm partition (along with system_ext and product) yet my phone boots fine. no matter what .img I attempt to flash in fastboot (product/odm/system_ext), it reports the partition is non-existent.
update: I grabbed the latest platform tools and it flashed.
please close thread mods. thanks
AOSP 13
This is a moto-common project release under the codename amogus. This build supports the following devices: rav, rav_t, sofia, sofiap, sofiap_ao, sofiap_sprout, sofiar.
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's AOSP?
AOSP is Android as Google publish without any modifications.
Whats not working?
Speakerphone on sofia variants
Instructions to install the ROM:
Reboot to bootloader:
Code:
adb reboot bootloader
The following will wipe your internal data:
Code:
fastboot -w
Code:
fastboot update package.zip
You may need to install drivers in device manager after running the last command
It will reboot your device to fastbootd, you might get the following warning:
Code:
FAILED (remote: 'Old partitions are not compatible with the new super layout; wipe needed')
, but you can continue with the following commands
Fastbootd:
Code:
fastboot flash product product.img
Code:
fastboot flash system system.img
Code:
fastboot flash vendor vendor.img
Code:
fastboot reboot
Downloads: Here
Source Code: Here
Sept 2: Fixed USB Mode Switching, Switched to new rebased kernel, Switched to EROFS
Sept 12: EGIS Fingerprint gestures fixed, Switch BtAudio to AIDL and September Patch level
Sept 28:
System Responsiveness has been tuned and improved
Introduce Multigenerational LRU Framework
Tune Dalvik Heap Sizes
Switched to QTI Thermal HAL
DT2W has been fixed for RAV (HIMAX) variants of amogus
Signature Spoofing support has been added to the ROM
Jan 26:
January Security Patch
Feb 27:
Feb security patch
Sept 2: Fixed USB Mode Switching, Switched to new rebased kernel, Switched to EROFS
Is anyone has ported the A12 official version from moto g pro who works in moto g8 power (sofiar)?
im guessing this doesnt come with any gapps installed?
if so would I need to flash gapps with It and from what i could tell do i need to downgrade to the stock android 10 rom to be able to flash cus i have attempted before but since it was on the stock android 11 version it would just get stuck
Sept 12: EGIS Fingerprint gestures fixed, Switch BtAudio to AIDL and September Patch level
Where can i get the files named "vendor.img","system.img" and "product.img"
AlejandroCRI said:
Where can i get the files named "vendor.img","system.img" and "product.img"
Click to expand...
Click to collapse
Inside the zip file you downloaded
Electimon said:
Inside the zip file you downloaded
Click to expand...
Click to collapse
sorry, i saw other .zip and that i wanted was in other folder
Any chance this works on Moto G Stylus 2021 Minsk?
afnz said:
Any chance this works on Moto G Stylus 2021 Minsk?
Click to expand...
Click to collapse
No sorry, that uses a different chipset
Electimon said:
No sorry, that uses a different chipset
Click to expand...
Click to collapse
Alright, thank you for your quick reply!
Sept 28:
System Responsiveness has been tuned and improved
Introduce Multigenerational LRU Framework
Tune Dalvik Heap Sizes
Switched to QTI Thermal HAL
DT2W has been fixed for RAV (HIMAX) variants of amogus
Signature Spoofing support has been added to the ROM
Did someone try this in the Moto g stylus US version?
Hi @Electimon First of all thanks for the big effort of A13 , must be kinda difficult to work on a project like this . Hope you can continue with this as long as you can as we all benefit from your effort on this . But I do have a question if I may of course. I see on the title that it is supported sofiap_sprout and I have that device which is Moto G Pro but When I flash your zip with fastboot update package.zip it tells me that
Checking 'product' FAILED
Device product is 'sofiap_sprout'.
Update requires 'trinket' or 'amogus' or 'rav' or 'sofiar' or 'sofia' or 'sofiap' or 'doha'.
fastboot: error: requirements not met!
then I checked the Zip file and there is a txt file that is android-info and contains the following
require board=trinket|amogus|rav|sofiar|sofia|sofiap|doha
which I believe is where that error comes from and im afraid that if I update by changing the txt file to sofiap_sprout and re zip it might be cathastrofic to my device . Any Idea?
Thanks in Advanced
Nanosochoa said:
Hi @Electimon First of all thanks for the big effort of A13 , must be kinda difficult to work on a project like this . Hope you can continue with this as long as you can as we all benefit from your effort on this . But I do have a question if I may of course. I see on the title that it is supported sofiap_sprout and I have that device which is Moto G Pro but When I flash your zip with fastboot update package.zip it tells me that
Checking 'product' FAILED
Device product is 'sofiap_sprout'.
Update requires 'trinket' or 'amogus' or 'rav' or 'sofiar' or 'sofia' or 'sofiap' or 'doha'.
fastboot: error: requirements not met!
then I checked the Zip file and there is a txt file that is android-info and contains the following
require board=trinket|amogus|rav|sofiar|sofia|sofiap|doha
which I believe is where that error comes from and im afraid that if I update by changing the txt file to sofiap_sprout and re zip it might be cathastrofic to my device . Any Idea?
Thanks in Advanced
Click to expand...
Click to collapse
You can edit the file and try again or unpack and flash manually, I need to add sofiap_sprout to the guard but yes it's supported
Thanks @Electimon o for the faster response.
However I did the steps on the Sofiap_sprout by doing step by step and re zipping the files with the modified txt file and got boot loop and then went into a different recovery with an error messsage a the bottom that says
Error: recovery: [libfs_mgr]dt_fstab : failed to find device for partition OEM
and then im at the Fastbootd page .
Any ideas?
My sofiap sprout was on A12 official from Motorola if that helps.
If anything , this is the whole CMD message (btw the files were re zipped to electimon.zip with the modified txt file adding only sofiap_sprout)
C:\Users\**\Desktop\platform-tools>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.008s]
< waiting for any device >
Finished. Total time: 18.826s
C:\Users\**\Desktop\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.212s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.009s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.240s
C:\Users\**\Desktop\platform-tools>fastboot update electimon.zip
--------------------------------------------
Bootloader Version...: MBM-3.0-sofiap_ao-7380af07e7e-220720
Baseband Version.....:
Serial Number........: ZY227ZQ5RM
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.188s]
extracting boot.img (64 MB) to disk... took 0.472s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.844s]
Writing 'boot_a' OKAY [ 1.456s]
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.184s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (24576 KB) OKAY [ 0.689s]
Writing 'dtbo_a' OKAY [ 0.241s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
extracting recovery.img (64 MB) to disk... took 0.421s
archive does not contain 'recovery.sig'
Sending 'recovery_a' (65536 KB) OKAY [ 1.838s]
Writing 'recovery_a' OKAY [ 1.463s]
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vbmeta_vendor.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition FAILED (remote: 'Old partitions are not compatible with the new super layout; wipe needed')
fastboot: error: Command failed
C:\Users\**\Desktop\platform-tools>fastboot flash product product.img
Sending 'product' (151708 KB) OKAY [ 4.382s]
Writing 'product' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
C:\Users\**\Desktop\platform-tools>fastboot flash system system.img
Resizing 'system_a' OKAY [ 0.007s]
Sending sparse 'system_a' 1/3 (262140 KB) OKAY [ 7.469s]
Writing 'system_a' OKAY [ 2.495s]
Sending sparse 'system_a' 2/3 (262140 KB) OKAY [ 7.545s]
Writing 'system_a' OKAY [ 1.478s]
Sending sparse 'system_a' 3/3 (69652 KB) OKAY [ 1.964s]
Writing 'system_a' OKAY [ 0.468s]
Finished. Total time: 22.635s
C:\Users\**\Desktop\platform-tools>fastboot flash vendor vendor.img
Resizing 'vendor_a' OKAY [ 0.005s]
Sending 'vendor_a' (205840 KB) OKAY [ 5.988s]
Writing 'vendor_a' OKAY [ 1.215s]
Finished. Total time: 7.303s
C:\Users\**\Desktop\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
Hi @Electimon
Just wanted to update the post that I was able to flash it
Had to set active partition a and delete partition a and product partition
and then create logical partition a and product and then
fastboot -w
fastboot --set-active=a
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash vendor vendor.img
and worked .. boot right to AOSP 13 in MOTO G Pro .. RAM usage is awesome... will be trying this as main driver and see what happens so far so good.
Thanks Electimon
Hi @Electimon
Everything is great so far .. Just vfc card cnat be added due to a permission missing but I already checked apps permissions and cache and still showing that but I bypassed that by installing a third party dialer from Fdroid and from there installed the vfc card to the phone contacts and fixed .. Also another thing that its important is the battery that drains so fast .. I mean I was using phhusson GSI for A12 y A11 and the battery was insanely good lasted the whole day with usage but on this rom takes like 5 hours with usage to drain completely the battery .. I know its not mandatory to fix that which im very grateful to you for this but I though you might wanna know .
Thanks in advance
I was asking if updating to stock A11 caused this to not work, happy to report that installing was straightforward
On another note, has anyone figured out getting GApps on this rom?