I used the payload dumper that Gregory Montoir created for extracting the files from an OTA. I thought I would post the output files here so people can use the boot.img for Magisk and whatnot, thought it would be helpful for other people not to have to use the payload dumper like I had to. I can also upload the Magisk patched file too if anyone wants it for easy Magisk flashing on Oxygen OS 10.3.2.
Download : https://drive.google.com/drive/folders/1_tRSJMkOXKKuTNRryzqmjmPfvbE_9lFG?usp=sharing
https://github.com/AndroidDumps/oneplus_oneplus6t_dump/
Related
It seems that Magisk is more complicated to install now. I did flash the latest version as a zip, as I have always done, but I understand that method is deprecated and suppose it might break or otherwise go way in the future.
The whole process of getting one's boot.img seems complicated for people who are not seasoned ROM developers. Of course I understand there are instructions one can read and learn how to get the boot.img, etc., but given that one has to have a ROM .zip to install the ROM, couldn't an option for Magisk be to extract the boot.img from the ROM .zip if that's what the user has on hand?
Shred00 said:
It seems that Magisk is more complicated to install now. I did flash the latest version as a zip, as I have always done, but I understand that method is deprecated and suppose it might break or otherwise go way in the future.
The whole process of getting one's boot.img seems complicated for people who are not seasoned ROM developers. Of course I understand there are instructions one can read and learn how to get the boot.img, etc., but given that one has to have a ROM .zip to install the ROM, couldn't an option for Magisk be to extract the boot.img from the ROM .zip if that's what the user has on hand?
Click to expand...
Click to collapse
The zip method still works fine for most devices, i still use it on my Pixel 2XL
Download the latest magisk-xxxx.apk, make a copy and rename it to magisk-xxxx.zip, flash via custom recovery
Or
If on Windows 64 Bit, you can use this payload dumper (which doesnt require Python to be installed) to extract the img files, including boot.img, doesnt get any easier:
payload_dumper-win64.zip | Tool by geminids14 for Utilities
Extract payload.bin in xiaomi weekly build zip for MI A1
androidfilehost.com
I still use the zip method as it requires less fiddly steps
73sydney said:
The zip method still works fine for most devices, i still use it on my Pixel 2XL
Click to expand...
Click to collapse
I flashed it on my Oneplus6 (A/B device) running LineageOS 18.1 with TWRP and it worked, but it did not survive an OTA update, which I guess is topjohnwu/Magisk#3820. I was wondering if that not surviving an OTA update was one of the reasons ZIP flashing is being deprecated.
73sydney said:
If on Windows 64 Bit,
Click to expand...
Click to collapse
Not. Am on Linux.
73sydney said:
you can use this payload dumper (which doesnt require Python to be installed) to extract the img files, including boot.img, doesnt get any easier:
payload_dumper-win64.zip | Tool by geminids14 for Utilities
Extract payload.bin in xiaomi weekly build zip for MI A1
androidfilehost.com
I still use the zip method as it requires less fiddly steps
Click to expand...
Click to collapse
Understood. And I understand the palaver one needs to go through to use the boot.img patching once one has a ROM ZIP. It just seems that that is all something that could be baked into the Magisk Manager to make the whole process a bit less of an ordeal.
WARNING: DO NOT ATTEMPT TO USE THE BOOT.IMG ON ANY DEVICE OR FIRMWARE VERSION EXCEPT THE ONE STATED!!! IT WILL MOST LIKELY RESULT IN A SOFT BRICK/BOOTLOOP!
Hello everyone,
Today my Xiaomi Mi 11 received its MIUI 12.5 OTA update. I snagged the OTA update and extracted the boot.img from the payload.bin. Thought I would save you all some trouble since the Rom can currently not be downloaded online (c.miui, etc). If you need any of the other files, let me know. I already have 12.5.1.0 installed on mine with Magisk working.
Device: Xiaomi Mi 11 (VENUS)
MIUI: 12.5.1.0 (RKBMIXM) - Global Rom
If you need it for a different xiaomi device/variant:
Snagging the OTA
Start update in Updater.
Use a file explorer and go to the "Download" folder. There should be a folder named "downloaded_rom" go into it.
Wait for OTA to download, it will start the "updating" phase and will say "updating" instead of "downloading." Copy the zip that is in the "downloaded_rom" folder somewhere else.
Now you have the OTA rom.
** This has to be done during the updating phase since the folder is deleted, otherwise.
Extracting the boot.img
Copy rom zip to a PC (Windows)
Extract .zip
Download and Extract the Payload Dumper Tool from here: Payload Dumper Tool (make sure you have Python Installed)
Copy the Payload.Bin and Payload.Properties files to the extracted payload dumper tool folder.
Click Shift+Right-Click in the folder with Payload_Dumper.py file and the Payload files in it. Select the option to open Powershell
Type "python -m pip install protobuf" and hit enter. Let it install.
Type "python payload_dumper.py payload.bin" and hit enter.
Now you should have the boot.img file.
iamrance.asa said:
AVISO: NÃO TENTE USAR O BOOT.IMG EM QUALQUER DISPOSITIVO OU VERSÃO DE FIRMWARE, EXCETO O INDICADO !!! PROVÁVEL RESULTARÁ EM UM TIJOLO MACIO / BOOTLOOP!
Olá a todos,
Hoje meu Xiaomi Mi 11 recebeu sua atualização MIUI 12.5 OTA. Eu peguei a atualização OTA e extraí o boot.img do payload.bin. Pensei em poupar alguns problemas para vocês, já que a ROM atualmente não pode ser baixada online (c.miui, etc). Se você precisar de qualquer um dos outros arquivos, me avise. Já tenho 12.5.1.0 instalado no meu com Magisk funcionando.
Dispositivo: Xiaomi Mi 11 (VENUS)
MIUI: 12.5.1.0 (RKBMIXM) - Rom global
Click to expand...
Click to collapse
Works with version EEA?
g0mes1 said:
Works with version EEA?
Click to expand...
Click to collapse
It's not pulled from it but if you want to try, you can use "fastboot boot " then the location of where you downloaded the boot.img. If it doesn't work, then you can just restart the phone and it will boot with the oem boot.img. If it does work, then you should patch it in magisk and use the "fastboot boot" command with the patched img, then "direct install" with magisk manager. That's the safest method to use it on the EEA ROM since this is from the Global ROM.
iamrance.asa said:
WARNING: DO NOT ATTEMPT TO USE THE BOOT.IMG ON ANY DEVICE OR FIRMWARE VERSION EXCEPT THE ONE STATED!!! IT WILL MOST LIKELY RESULT IN A SOFT BRICK/BOOTLOOP!
Hello everyone,
Today my Xiaomi Mi 11 received its MIUI 12.5 OTA update. I snagged the OTA update and extracted the boot.img from the payload.bin. Thought I would save you all some trouble since the Rom can currently not be downloaded online (c.miui, etc). If you need any of the other files, let me know. I already have 12.5.1.0 installed on mine with Magisk working.
Device: Xiaomi Mi 11 (VENUS)
MIUI: 12.5.1.0 (RKBMIXM) - Global Rom
Click to expand...
Click to collapse
Hi,
Where did you find the OTA update file?
Want to update my EEA but need the boot.img to patch with Magisk after updating.
Thanks in advance!
rippledrums said:
Hi,
Where did you find the OTA update file?
Want to update my EEA but need the boot.img to patch with Magisk after updating.
Thanks in advance!
Click to expand...
Click to collapse
When you download in Updater, it is stored in /sdcard/download/downloaded_rom but it deletes itself so you'll need to grab it while it's in the updating phase.
iamrance.asa said:
WARNING: DO NOT ATTEMPT TO USE THE BOOT.IMG ON ANY DEVICE OR FIRMWARE VERSION EXCEPT THE ONE STATED!!! IT WILL MOST LIKELY RESULT IN A SOFT BRICK/BOOTLOOP!
Hello everyone,
Today my Xiaomi Mi 11 received its MIUI 12.5 OTA update. I snagged the OTA update and extracted the boot.img from the payload.bin. Thought I would save you all some trouble since the Rom can currently not be downloaded online (c.miui, etc). If you need any of the other files, let me know. I already have 12.5.1.0 installed on mine with Magisk working.
Device: Xiaomi Mi 11 (VENUS)
MIUI: 12.5.1.0 (RKBMIXM) - Global Rom
If you need it for a different xiaomi device/variant:
Snagging the OTA
Start update in Updater.
Use a file explorer and go to the "Download" folder. There should be a folder named "downloaded_rom" go into it.
Wait for OTA to download, it will start the "updating" phase and will say "updating" instead of "downloading." Copy the zip that is in the "downloaded_rom" folder somewhere else.
Now you have the OTA rom.
** This has to be done during the updating phase since the folder is deleted, otherwise.
Extracting the boot.img
Copy rom zip to a PC (Windows)
Extract .zip
Download and Extract the Payload Dumper Tool from here: Payload Dumper Tool (make sure you have Python Installed)
Copy the Payload.Bin and Payload.Properties files to the extracted payload dumper tool folder.
Click Shift+Right-Click in the folder with Payload_Dumper.py file and the Payload files in it. Select the option to open Powershell
Type "python -m pip install protobuf" and hit enter. Let it install.
Type "python payload_dumper.py payload.bin" and hit enter.
Now you should have the boot.img file.
Click to expand...
Click to collapse
No matter what I do, I just get this error :
payload_dumper\payload_dumper.py", line 86, in <module>
assert op.type in (op.REPLACE, op.REPLACE_BZ, op.REPLACE_XZ), \
AssertionError: unsupported op
Even tried doing the extraction on my phone using Termux and get the same error. I'm trying to extract boot.img from EEA 12.5.1.0.RKBEUXM OTA ROM.
Sld_Ultra said:
No matter what I do, I just get this error :
payload_dumper\payload_dumper.py", line 86, in <module>
assert op.type in (op.REPLACE, op.REPLACE_BZ, op.REPLACE_XZ), \
AssertionError: unsupported op
Even tried doing the extraction on my phone using Termux and get the same error. I'm trying to extract boot.img from EEA 12.5.1.0.RKBEUXM OTA ROM.
Click to expand...
Click to collapse
That is referring to the type of compression so it could be a number of things. If you have python3 installed (and working), then check the your payload.bin to see if it's healthy (should be around 3GB in size). I wouldn't imagine they'd use a different compression type on it.
iamrance.asa said:
That is referring to the type of compression so it could be a number of things. If you have python3 installed (and working), then check the your payload.bin to see if it's healthy (should be around 3GB in size). I wouldn't imagine they'd use a different compression type on it.
Click to expand...
Click to collapse
Around 3GB?! Okay, you meant extract the boot.img from a full OTA ROM of 12.5.1.0.RKBEUXM. I was using the OTA incremental ROM which is 656MB in size, which I copied from the download folder during it's update phase.
The zip file name was "miui-blockota-venus_eea_global-V12.0.13.0.RKBEUXM-V12.5.1.0.RKBEUXM-9a04415c08-11.0", that I was using. But the full OTA ROM I find for 12.5.1.0.RKBEUXM is stable beta, ctsprofile for safetynet won't pass so I installed the safetynet fix module in magisk. The magisk props module wouldn't work.
Sld_Ultra said:
Around 3GB?! Okay, you meant extract the boot.img from a full OTA ROM of 12.5.1.0.RKBEUXM. I was using the OTA incremental ROM which is 656MB in size, which I copied from the download folder during it's update phase.
The zip file name was "miui-blockota-venus_eea_global-V12.0.13.0.RKBEUXM-V12.5.1.0.RKBEUXM-9a04415c08-11.0", that I was using. But the full OTA ROM I find for 12.5.1.0.RKBEUXM is stable beta, ctsprofile for safetynet won't pass so I installed the safetynet fix module in magisk. The magisk props module wouldn't work.
Click to expand...
Click to collapse
Oh. This is how large the 12.5.1 update was on my phone when I updated with updater. I just pulled it from the downloaded_rom folder from the official update. The payload.bin on it is 3.03GB. I did this because the stable 12.5.1 ROM isn't available online yet.
What should I do, if my device is Poco F2 Pro?
AniTigerRu said:
What should I do, if my device is Poco F2 Pro?
Click to expand...
Click to collapse
Snagging the OTA and unloading the bin should be the same for the Poco F2 Pro. That's if you have a new OTA that isn't available in a full zip yet.
You can check here for full official ROM downloads if it is available. Just make sure you use the right variant if your bootloader isn't unlocked.
Hope some people smarter than me use this as a method of developing some Custom ROMs for our device
Hello folks,
I am trying to create a lineage build following this guide:
Building LineageOS for your device
How I build a custom ROM for my android device on my own, and how to do that with your own device.
medium.com
but I am struggling to find the device vendor files for the Mi 11. Does anyone know where or how to get them?
Best wishes
hi if that helps. : https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/venus-r-oss
jejemc said:
hi if that helps. : https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/venus-r-oss
Click to expand...
Click to collapse
thank you I already found the repo for the Kernel Files and the Device Tree. But I also need the vendor files which are not included in this repo. Maybe they can be extracted from miui rom file but I don't know.
Download the latest MIUI rom and follow these instructions:
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Oh and once you have the vendor.img file from above to extract that check here:
Kitchen [Windows][Tool] CRB [V3.2.5]
Welcome to CRB Android Kitchen Screenshot Short description CRB Android Kitchen is a user-friendly software application designed to help users build custom ROMs for Android devices. It supports Android 10, 11, 12, and 13 and the Ext4, F2FS...
forum.xda-developers.com
Sage said:
Download the latest MIUI rom and follow these instructions:
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Click to expand...
Click to collapse
This tool is easier/better: payload-dumper-go.
Github
psf_burner said:
thank you I already found the repo for the Kernel Files and the Device Tree. But I also need the vendor files which are not included in this repo. Maybe they can be extracted from miui rom file but I don't know.
Click to expand...
Click to collapse
Any updates ?
DarckZian said:
Any updates ?
Click to expand...
Click to collapse
Currenrly I am struggling to set up the build as it is my first time. I will let you know if I can get something working.
Unfortunately I will not be able to create a working build as I am missing to much know how. If there is enyone I can help creating necessary files let me know.
where can download boot.img
I downloaded the rom for A8+ from: https://www.sammobile.com/samsung/g...e/SM-A730F/BRI/download/A730FXXU7CUI2/1583269
but after unzipping, I don't see the boot.img file.
YT_iceice said:
where can download boot.img
I downloaded the rom for A8+ from: https://www.sammobile.com/samsung/g...e/SM-A730F/BRI/download/A730FXXU7CUI2/1583269
but after unzipping, I don't see the boot.img file.
Click to expand...
Click to collapse
For installing Magisk, you should patch the whole AP.
For detailed instructions visit the Magisk website with good documentation.
If you still want the boot.img .... then unzip the AP by first removing .gz.
Ok
serach for a Payload dumper
Hello
Unable to flash magisk with any gsi img file. I transfer the img to Android device and with the latest magisk 24.1. I patch to file, but fails on each img which so far has been.
Pixel Experience
ProtonAOSP
Dot OS
AOSP
ProtonAOSP
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
No TWRP on any of the devices that want to install Magisk.
The error is Unsupported/Unknown Image format.
thanks