Related
Hi! I trying to compile a kernel for our Lenovo Vibe K5+ and i'm having success on compilling, but, i have two output files in arm (Image and zImage) and just one in arm64 (Image)... I tried to flash via fastboot "fastboot flash boot Image" and zImage, but i always receive:
Code:
target reported max download size of 268435456 bytes
sending 'boot' (18616 KB)...
OKAY [ 0.749s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.750s
The same in both cases... But, i tried to decompress an boot.img of CM13 for our device and recompile with my zImage but when i flash, i reboot and devices stucks in "Lenovo" boot screen...
Since now, thanks!
I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!
gocks said:
I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!
Click to expand...
Click to collapse
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.
dandrumheller said:
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.
Click to expand...
Click to collapse
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??
gocks said:
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??
Click to expand...
Click to collapse
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using
Click to expand...
Click to collapse
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.
gocks said:
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.
Click to expand...
Click to collapse
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.
gocks said:
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.
Click to expand...
Click to collapse
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!
gocks said:
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!
Click to expand...
Click to collapse
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did exactly what you told me and this happened:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.371s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.683s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10820 KB)...
OKAY [ 0.235s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.235s]
finished. total time: 0.501s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257307 KB)...
OKAY [ 5.493s]
writing 'system'...
OKAY [ 3.985s]
finished. total time: 9.478s
The othes lines seems to be ok, but the phone continue stucked on the "Your device has been unlock...." and don´t reboot.
Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.
gocks said:
Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.
Click to expand...
Click to collapse
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.
gocks said:
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.
Click to expand...
Click to collapse
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws
flashallthetime said:
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws
Click to expand...
Click to collapse
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?
gocks said:
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?
Click to expand...
Click to collapse
Which carrier are you with?
And don't sue me if things get worse
flashallthetime said:
Which carrier are you with?
And don't sue me if things get worse
Click to expand...
Click to collapse
Vivo, its a brazilian one.
Relax, if my phone bricks I wont sue you because my wife will kill me first!
I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat
gocks said:
I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat
Click to expand...
Click to collapse
Yes and it seems like you can't right to the system and or data partitions. There's more partitions but they're locked or hidden
Try to format your data in TWRP
and wipe system
I'm on 7.1.2 (patch level July 2017, N2G48B). I would like to boot TWRP to make a backup before updating to the August patch. The device is unlocked. Fastboot fails to boot or flash TWRP:
Code:
fastboot flashing unlock
FAILED (remote: Device already unlocked)
fastboot boot twrp-3.1.1-0-dragon.img
creating boot image...
creating boot image - 13035520 bytes
downloading 'boot.img'...
OKAY [ 0.324s]
booting...
FAILED (remote: image verification failed)
fastboot flash recovery twrp-3.1.1-0-dragon.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
Somebody got an idea?
[Solved] Can't start TWRP any more
Solved, see here: https://forum.xda-developers.com/showpost.php?p=73361170&postcount=426 and the following posts.
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.
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