Database Develop

How to flash rom zip with payload.bin inside via twrp?

I easily flash any roms via twrp, but recently some rom come with payload.bin inside the zip. I cant manage to flash it via twrp, it ends up with error with zip format?
I saw a thread that mentions to unpack the payload.bin and put all unpacked files into fastboot folder, then fastboot these files separately.
Is there any way to make it as easy as it used to.

stevedat said:
I easily flash any roms via twrp, but recently some rom come with payload.bin inside the zip. I cant manage to flash it via twrp, it ends up with error with zip format?
I saw a thread that mentions to unpack the payload.bin and put all unpacked files into fastboot folder, then fastboot these files separately.
Is there any way to make it as easy as it used to.
Click to expand...
Click to collapse
Actually. Its not that hard the using the fastboot version. You will just extract the file then run the batch file. Then wait to finish. Better than ota. Retain my data.

Identity77 said:
Actually. Its not that hard the using the fastboot version. You will just extract the file then run the batch file. Then wait to finish. Better than ota. Retain my data.
Click to expand...
Click to collapse
You mean that if I come from other Rom, just wipe all in twro, then flash it by using batch file and just connected the phone to pc as fastboot mode.

stevedat said:
You mean that if I come from other Rom, just wipe all in twro, then flash it by using batch file and just connected the phone to pc as fastboot mode.
Click to expand...
Click to collapse
I Didnt try with other rom. It has the a and b thing. I got problem with ota because im rooted with magisk. Got into bootlloop. This fastboot thing saves me. And i was able to upgrade to latest.

[MAGISK]Root OnePlus 7 Pro With Patched Boot Image 9.5.3 | 9.5.4

Prerequisites :
Running Stock OOS
Unlocked Bootloader
Fastboot
Disclaimer : I am not responsible for any damage to your device.
Click to expand...
Click to collapse
Download : [ALL VARIANTS]
OOS Patched Boot Images (Credits : @Bradl79 for maintaining the folder)
9.5.4 Boot Images :
OOS 9.5.4 Patched [EU Version/1913]
OOS 9.5.4 Patched [Global | Indian Version /1917 | 1911]
Want To Maintain Root On New OTAs?:
#171
Patched Boot Image Not Available For Your Model Yet? :
#6
Instructions :
Download the patched boot image
Install the latest version of Magisk Manager
Reboot the phone in fastboot mode
Use the following command via command prompt :
Code:
fastboot flash boot boot_patched.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Credits :
gururoop (Stock Firmware)
b1czu (Instructions)
Regards,
acervenky

Included the stock as well as patched image.
Link to repository : Github
Regards,
acervenky

Reserved 2

Am Trying To Port OnePlus 6T TWRP Recovery. Just Got My Hands On The Stock Recovery. Will Update If It Works

acervenky said:
It seems that the size difference is vast, so I would request one of you to download the stock boot.img from the repository, patch it and rechceck the file size.
You can try the patched boot.img and inform whether it works, for any issues/help PM me.
Link to repository : Github
Regards,
acervenky
Click to expand...
Click to collapse
I am upgrading the firmware to 9.5.3 right now. As soon as it finishes, I would try and report back
EDIT : The patched boot image on my phone is 56.32 MB so yes there is substantial size difference. Let me try booting from it

You can also patch the boot.img yourself.
Here is how:
.) Download latest Stock OOS
.) Extract boot.img using payload.bin dumper (needs python)
.) Install Magisk Manager on your device
.) Copy boot.img to your device
.) Patch boot.img using Magisk Manager
.) Copy patched boot.img to your pc, reboot your phone to fastmode and use 'fastboot boot patched_boot.img' to boot from patches bootimage.
.) Run Magisk Manager, choose direct install
-> Voila, you have a rooted OP7pro.

Kingmohdarif said:
Am Trying To Port OnePlus 6T TWRP Recovery. Just Got My Hands On The Stock Recovery. Will Update If It Works
Click to expand...
Click to collapse
zanderzone said:
I am upgrading the firmware to 9.5.3 right now. As soon as it finishes, I would try and report back
EDIT : The patched boot image on my phone is 56.32 MB so yes there is substantial size difference. Let me try booting from it
Click to expand...
Click to collapse
Please post the screenshots if you guys have successfully rooted, will update the OP accordingly
GoodSoul said:
You can also patch the boot.img yourself.
Here is how:
.) Download latest Stock OOS
.) Extract boot.img using payload.bin extractor (needs python)
.) Install Magisk Manager on your device
.) Copy boot.img to your device
.) Patch boot.img using Magisk Manager
.) Copy patched boot.img to your pc, reboot your phone to fastmode and use 'fastboot boot patched_boot.img' to boot from patches bootimage.
.) Run Magisk Manager, choose direct install
-> Voila, you have a rooted OP7pro.
Click to expand...
Click to collapse
Yes if you're on another version of OOS, this method works
Regards,
acervenky

acervenky said:
Download: OOS 9.5.3 Patched
Click to expand...
Click to collapse
Your patched boot.img is about 56mb in size while my extracted boot.img is 100mb in size. There might be something wrong with your boot.img ...
zanderzone said:
EDIT : The patched boot image on my phone is 56.32 MB so yes there is substantial size difference. Let me try booting from it
Click to expand...
Click to collapse
Did it work?

GoodSoul said:
Your patched boot.img is about 56mb in size while my extracted boot.img is 100mb in size. There might be something wrong with your boot.img ...
Did it work?
Click to expand...
Click to collapse
That extra 44mb is most likely empty space, which patching with Magisk removes like on other devices.

bmg1001 said:
That extra 44mb is most likely empty space, which patching with Magisk removes like on other devices.
Click to expand...
Click to collapse
You might be right since after 56% of the file everything is just blank.

GoodSoul said:
You might be right since after 56% of the file everything is just blank.
Click to expand...
Click to collapse
Same thing happens on the Essential Phone. Extracting the image with dd gives you a ~60mb boot image but Magisk brings it down to 23mb.

bmg1001 said:
Same thing happens on the Essential Phone. Extracting the image with dd gives you a ~60mb boot image but Magisk brings it down to 23mb.
Click to expand...
Click to collapse
Well then the patched image should work without any problems, and others who want to root with TWRP there's an unofficial version out as well
Regards,
acervenky

Thanks for the patched boot.img but this command did not work for me
Code:
fastboot boot patched_boot.img
For me this has worked
1. Install Magisk Manager
2.. Reboot device to bootloader
3.. open cmd at the location of the extracted patched_boot.img
4.. In cmd type
Code:
fastboot flash boot_a patched_boot.img
5.. In cmd type
Code:
fastboot flash boot_b patched_boot.img
6.. In cmd type
Code:
fastboot reboot
7.. Open Magisk Manager, it will prompt you with additional files are needed to complete Magisk install, go ahead and download the files.
8. After a few seconds, install will be complete and you will be rooted!

b0uNz said:
Thanks for the patched boot.img but this command did not work for me
Code:
fastboot boot patched_boot.img
For me this has worked
1. Install Magisk Manager
2.. Reboot device to bootloader
3.. open cmd at the location of the extracted patched_boot.img
4.. In cmd type
Code:
fastboot flash boot_a patched_boot.img
5.. In cmd type
Code:
fastboot flash boot_b patched_boot.img
6.. In cmd type
Code:
fastboot reboot
7.. Open Magisk Manager, it will prompt you with additional files are needed to complete Magisk install, go ahead and download the files.
8. After a few seconds, install will be complete and you will be rooted!
Click to expand...
Click to collapse
Hey man
Thanks for this, your commands worked but unfortunately I messed up my phone. Kinda new to rooting. Just realized I was on 9.5.4 on a GM1913. The patched boot image on here for 9.5.3 broke my wifi and the settings app completely unstable, it crashes constantly.
Not sure if the problem was that I used the boot image for 9.5.3 on 9.5.4 or because the patched boot image on here was intendend for other versions of the OP7P and not the European GM1913.
Does anyone have a flashable zip for the GM1913? Alternatively a stock or patched boot image intended for 9.5.4 GM1913? Any help would be much appreciated, still no OP7 here https://www.oneplus.com/support/softwareupgrade so I am stuck with a non working phone

b0uNz said:
Thanks for the patched boot.img but this command did not work for me
Code:
fastboot boot patched_boot.img
Click to expand...
Click to collapse
What error did you got when you tried that command? Did you oem unlock first and enabled usb debugging?

@acervenky @b0uNz @GoodSoul
Unlike older OnePlus phones, the current bootloader of the OnePlus 7 Pro doesn't allow 'fastboot boot' (also known as tethered booting) command. The situation is same as Essential PH-1 as well some other phones.
You will get something like the following:
Code:
downloading 'boot.img'...
OKAY [ 1.215s]
booting...
FAILED (remote: unknown command)

Titokhan said:
@acervenky @b0uNz @GoodSoul
Unlike older OnePlus phones, the current bootloader of the OnePlus 7 Pro doesn't allow 'fastboot boot' (also known as tethered booting) command. The situation is same as Essential PH-1 as well some other phones.
You will get something like the following:
Code:
downloading 'boot.img'...
OKAY [ 1.215s]
booting...
FAILED (remote: unknown command)
Click to expand...
Click to collapse
Yep, that's the same error I got initially. Do you have any idea as to what went wrong with my phone?
I am wondering if I messed up because I flashed the patched boot.img for 9.5.3 while being on 9.5.4, or if it's because it was for the wrong version, I have a GM1913.
Are boot images unique for each model, like GM1913, GM1917 etc?

Titokhan said:
@acervenky @b0uNz @GoodSoul
Unlike older OnePlus phones, the current bootloader of the OnePlus 7 Pro doesn't allow 'fastboot boot' (also known as tethered booting) command. The situation is same as Essential PH-1 as well some other phones.
You will get something like the following:
Code:
downloading 'boot.img'...
OKAY [ 1.215s]
booting...
FAILED (remote: unknown command)
Click to expand...
Click to collapse
Thanks for reporting, I'll update the OP accordingly.
Regards,
acervenky

Hey guys, for anyone that has OOS 9.5.4. Here is a patched boot image for it! https://www.androidfilehost.com/?fid=1395089523397968832

mingo_mgx said:
Hey guys, for anyone that has OOS 9.5.4. Here is a patched boot image for it! https://www.androidfilehost.com/?fid=1395089523397968832
Click to expand...
Click to collapse
Hey man, thank you! :good::good: You might have just saved my day. Quick question before I flash it though, is this for the GM1913 or GM1917?
---------- Post added at 10:12 PM ---------- Previous post was at 10:03 PM ----------
mingo_mgx said:
Hey guys, for anyone that has OOS 9.5.4. Here is a patched boot image for it! https://www.androidfilehost.com/?fid=1395089523397968832
Click to expand...
Click to collapse
Never mind, I couldn't wait so I tried it and my phone is fixed! I am rooted and wifi and the settings are working again. Thank you so much.
@acervenky, could you add the 9.5.4 boot image to the OP? Just to avoid any other noobs like myself messing up their brand new phone like I did with the wrong boot image..
Also does anyone know if boot images are specific to different models? Are they different on GM1913, 1915, 1917 etc? Would be good to mention that in the OP too if so.

Dirty Flash December Update

This is probably a dumb question... I have the Google store unlocked Pixel 4XL. I'm currently on the October factory image. I want to update to the December update.
Is there any reason I can't just dirty Flash the December update factory image and then use Magisk to patch the boot image from the factory update?
Or is there and easier way to get to the new update for unlocked Pixels that doesn't include the alternate method in the guide section of the forums?

ihuntinde said:
This is probably a dumb question... I have the Google store unlocked Pixel 4XL. I'm currently on the October factory image. I want to update to the December update.
Is there any reason I can't just dirty Flash the December update factory image and then use Magisk to patch the boot image from the factory update?
Or is there and easier way to get to the new update for unlocked Pixels that doesn't include the alternate method in the guide section of the forums?
Click to expand...
Click to collapse
Having an "unlocked" phone doesn't necessarily mean it is bootloader unlocked. Just wanted to confirm you are bootloader unlocked already. If yes, just d/l the December full image (make sure to get the RIGHT ONE) and edit the flash-all.bat to remove the wipe flag. You will lose root, but if you extract the boot.img from the image beforehand, patch it with Magisk Manager and put it in your adb folder before starting, you just run the script, boot back to fastboot and then flash the patched boot.img. May sound a bit complicated, but patching the image and pre-placing it before you start makes things go quicker. Good luck! :good:

v12xke said:
Having an "unlocked" phone doesn't necessarily mean it is bootloader unlocked. Just wanted to confirm you are bootloader unlocked already. If yes, just d/l the December full image (make sure to get the RIGHT ONE) and edit the flash-all.bat to remove the wipe flag. You will lose root, but if you extract the boot.img from the image beforehand, patch it with Magisk Manager and put it in your adb folder before starting, you just run the script, boot back to fastboot and then flash the patched boot.img. May sound a bit complicated, but patching the image and pre-placing it before you start makes things go quicker. Good luck! :good:
Click to expand...
Click to collapse
Thanks for the reply. I can confirm that I have an unlocked bootloader.

Just as a point of frustration........
for the last 24 hours I've been fighting this issue with must be flashed in fastbootd... so, i download the new platform-tools... replace my existing platform-tools... all is good, right?
NOPE....
I have another platform-tools on my C: drive... that is assigned in my Path Variable... so it's trying to use the old platform tools... GRRRRR...
needless to say, i'm all fixed up now. Probably didn't have to stay up until 2:00am trying to get back to the October update...

So.. for those that need it, here are my exact steps for a bootloader unlocked Pixel 4XL bought from the Google Store:
1. Download full factory image from here: https://developers.google.com/android/images#coral (10.0.0 (QQ1B.191205.012.A1, Dec 2019))
2. Extract the zip file, open the zip inside of that extracted folder and copy the boot.img to your phone's Downloads folder.
2a. I used a usb cable to my PC and put the phone in File transfer / Android Auto to do this)
3. In Magisk Manager, click Install. Click Install again in the popup. Choose Select and Patch a File.
4. Find the boot.img that you copied to your phone's Download folder. Select it.
5. Copy the magisk_patched.img file from your phone's Download folder to the unzipped factory image folder.
5a. Refer to 2a above. You may have to disconnect the usb cable and reconnect. For some reason, my PC wasn't refreshing the folder with the patched file until I did this.
6. With your phone connected and in File transfer mode. Open a command prompt in the folder you unzipped the factory image to.
6a. You may be able to shift and right-click then click Open Command Prompt window here. That will open the command prompt at that exact folder instead of having to navigate to it through the command prompt. If you are a newer version of Windows 10, you may only see the Powershell option. I am not sure if Powershell will work. However, to get to a "command prompt" to be able to run the flash-all and fastboot commands. Simply type cmd and hit <enter>. Then you can use the adb, flash-all, and fastboot commands as explained below. ** WARNING: I DID NOT USE POWERSHELL, USE AT YOUR OWN RISK **
6b. Type adb reboot bootloader.
7. Remembering this is a dirty flash (i.e, keeping all of your data) edit the flash-all.bat file in any type of editor (even notepad). Look for the line that says fastboot -w update image-coral-qq1b.191205.012.a1.zip and remove the -w. So, the line just above echo Press any key to exit... should look like this:
7a. fastboot update image-coral-qq1b.191205.012.a1.zip
8. Wait for the flashing to finish and for your phone to reboot and fully boot back up.
9. Once it's connected, put your phone in File Transfer usb mode again.
10. Open a command prompt and type adb reboot bootloader
10a. See 6a
11. Once the phone is in fastboot mode, type fastboot flash boot magisk_patched.img
12. Once that is done, type adb reboot.
You should now be on the December update and rooted.
If you get the error that says "should be flashed in fastbootd", I can confirm that you do not have a new enough version of fastboot.exe. You can do one of two things. First, download the latest platform tools from here: https://developer.android.com/studio/releases/platform-tools
1. Either hunt down every copy of your platform-tools folder (I had multiple for some dumb reason) and consolidate to just one, then update your platform-tolls. Then update your system environment variables and point it to this new folder (making sure it's the only folder pointing to a platform-tools version).
2. Download the new version and copy the fastboot.exe and adb.exe directly into the folder with the flash-all.bat. This will guarantee you are using the correct version.
Hope this helps someone...

ihuntinde said:
Just as a point of frustration........
for the last 24 hours I've been fighting this issue with must be flashed in fastbootd... so, i download the new platform-tools... replace my existing platform-tools... all is good, right?
NOPE....
I have another platform-tools on my C: drive... that is assigned in my Path Variable... so it's trying to use the old platform tools... GRRRRR...
needless to say, i'm all fixed up now. Probably didn't have to stay up until 2:00am trying to get back to the October update...
Click to expand...
Click to collapse
This happens more than you know. Glad you got it sorted. Next time (in a couple of weeks) it will be a snap.

Update after root pixel 4a 5g

Hi, I have unlock the boot loader and root my pixel 4a 5g in february update.
I don't understand how update it when new update comes ?
I can update it with Ota when comes in settings/System/Update ?
Or I do flash system image with fastboot and then flash the boot.img with Magisk to flash it in Fastboot mode ?
But I see : Flashing a new system image deletes all user data !!?
Before on Oneplus and later Xiaomi is more easy with Twrp. But now it's very complicated to update my freshly updated Pixel 4a 5g and Root
Please that it is the easiest procedure to update every month with Magisk installed. Previously I stopped all the Mods installed so as not to have a similar bootloop for Substartum .. Thank you
Thanks

Here's what I do:
- Download full factory image
- Unzip the archive
- There will be flash-all.bat (for Windows) and flash-all.sh (Linux) files created. You will need to edit the appropriate file to remove the -w flag on the "fastboot -w update image-bramble-rq1c.210205.006.zip" command near the bottom of the script.
- Within the archive you just unzipped, a directory will be created i.e. bramble-rq1c.210205.006 and within that there will be another zip file i.e. image-bramble-rq1c.210205.006. This zip file also needs to be uncompressed to extract the individual .img files including boot.img.
- Copy boot.img to your phone (Download directory is a good place)
- Flash the update using the edited flash-all script
- Once flashing is complete and the phone has rebooted, go into Magisk Manager and Install Magisk using the "select and patch a file" method. Navigate to the Downloads directory and select boot.img. Once complete, there will be a patched boot image named something like magisk_patched_bEKaK.img created in the Download directory. Copy that file back to your PC and then use fastboot to flash it to your phone i.e. "fastboot flash boot magisk_patched_bEKaK.img".
- Reboot phone and profit!

weissbierdood said:
Here's what I do:
- Download full factory image
- Unzip the archive
- There will be flash-all.bat (for Windows) and flash-all.sh (Linux) files created. You will need to edit the appropriate file to remove the -w flag on the "fastboot -w update image-bramble-rq1c.210205.006.zip" command near the bottom of the script.
- Within the archive you just unzipped, a directory will be created i.e. bramble-rq1c.210205.006 and within that there will be another zip file i.e. image-bramble-rq1c.210205.006. This zip file also needs to be uncompressed to extract the individual .img files including boot.img.
- Copy boot.img to your phone (Download directory is a good place)
- Flash the update using the edited flash-all script
- Once flashing is complete and the phone has rebooted, go into Magisk Manager and Install Magisk using the "select and patch a file" method. Navigate to the Downloads directory and select boot.img. Once complete, there will be a patched boot image named something like magisk_patched_bEKaK.img created in the Download directory. Copy that file back to your PC and then use fastboot to flash it to your phone i.e. "fastboot flash boot magisk_patched_bEKaK.img".
- Reboot phone and profit!
Click to expand...
Click to collapse
Thank you very much.
Have a good day..
I have now the good procedure to update it. Thanks

[STOCK][FASTBOOT][Root] Revive bootloop with Fastboot Flashable Images, RealMe 5 Pro(IN)

I tried to root this phone, and got bootloop. The screen only showed "Realme", vanished, and showed this again. I can only boot to BOOTLOADER.
I tried Flash Tool. Download the ".ofp" file from google. Didn't work. As it only supports Realme older than RM5P. No use.
Tried to use MSM Tools. Difficult. As it is only supposed to be used by Oppo/Realme service centers and needs passwords. So, MSM is out of the way.
Then, I remember, the easiest thing that can be done is flashing through FASTBOOT with fastboot img files. Sadly, I tried to seach google, in vain. Just found one kind person offered a complete set of files. But it was old. Still in Android 9. How could I revive my phone and update it?
Then I found a thread about TWRP by @BabluS It could flash OZIP files. That's it. So, my plan is :
Download official OTA Ozip file from Realme site (Software update site... Indonesia). The name is like RMX1971EX_11_OTA_xxx.ozip (will show if you click "download"). Put it in external SD.
Flash the BabluS TWRP. Wipe dalvic, cache, data, system. Back to boot bootloader
Flash the fastboot files one by one (and the phone gets the old Realme version.)
- boot.img
- dtbo.img
- system.img
- vbmeta.img
- vendor.img
Update the phone to the current version through TWRP (Click Install. Click Storage (?), choose ext sdcard, find the OZIP file).
Wipe data through TWRP again .... It worked...!
Note:
When unlocking, in-deep-test, one has to wait for 15 minutes. Processing... Please wait... I tried several times, waiting for hours, in vain. Then tried to click "verify". Looked like it was Reviewed already.
Get the fastboot files through this link.
The boot.img contains stock recovery!
Get the BabluS TWRP here.
Error flash:
- "Invalid sparse file format at header magic". Just ignore the error. Wait for 5 minutes or more until is is finished.
Big thanks to @BabluS and @acervenky for your great work ....

good

...Thanks man...
could you please write the flash commands down ?
Cz I don't know the pertition name for dtbo.img file and vbmeta.img file
(<Fastboot flash ??? dtbo.img>)

Mehedi Hassan 09 said:
...Thanks man...
could you please write the flash commands down ?
Cz I don't know the pertition name for dtbo.img file and vbmeta.img file
(<Fastboot flash ??? dtbo.img>)
Click to expand...
Click to collapse
It is probably the same name
So the command for dtbo.img would be: fastboot flash dtbo dbto.img
same for vbmeta.img