I use Magisk for rooting the phone, and it requires patching boot.img, which I obtained from the global ROM's zip file available here on XDA. It works fine, but I would prefer patching the current boot.img, keeping it up to date at the same time.
How to extract boot.img from the firmware without root and with the stock recovery only (fastboot is available)? Or is it possible to dump the whole firmware, and get boot.img from the dump?
tigers2 said:
I use Magisk for rooting the phone, and it requires patching boot.img, which I obtained from the global ROM's zip file available here on XDA. It works fine, but I would prefer patching the current boot.img, keeping it up to date at the same time.
How to extract boot.img from the firmware without root and with the stock recovery only (fastboot is available)? Or is it possible to dump the whole firmware, and get boot.img from the dump?
Click to expand...
Click to collapse
I think not. But you can search for your machine's software updates in realme ui 4.0 downgrade program rom on that site official and extract payload.bin
Related
I am looking to learn how to extract a boot image to patch. The last source for patched boot images has not updated since 9.5.10. I would like to be less dependent and be able to do it on my own.
Can someone put together a quick tutorial on how to extract a boot.img so I can run it though Magisk and create a patched one?
https://forum.xda-developers.com/showpost.php?p=79548858&postcount=6
I have the current rooted AA boot image in the guide in my signature. I extract them directly from the phone.
ozfive said:
I am looking to learn how to extract a boot image to patch. The last source for patched boot images has not updated since 9.5.10. I would like to be less dependent and be able to do it on my own.
Can someone put together a quick tutorial on how to extract a boot.img so I can run it though Magisk and create a patched one?
Click to expand...
Click to collapse
1)Download payload dumper.
2)Extract payload file from rom zip.
3)Put payload file in payload_input folder.
4)Run exe file.
5)After process complete check payload_output folder. All extracted there.
Download payload dumper from here :- https://forum.xda-developers.com/attachment.php?attachmentid=4760222&d=1558078935
Patched boot images are irrelevant and only necessary for devices without a working TWRP recovery. If you want to root, either boot TWRP once or boot and install TWRP (recommended) and then install the magisk zip from there.
larsdennert said:
I have the current rooted AA boot image in the guide in my signature. I extract them directly from the phone.
Click to expand...
Click to collapse
How do you extract the boot.img from the phone? I have the tmo version and would like to say on the stock room with root.
Sent from my GM1915 using Tapatalk
You need root to extract a partition, but if you have root then you have no need for it except to share it so someone else can get root.
In other words are you rooted already? If not, you'll need to use the other instructions or get a rooted or non rooted image from someone with a T-Mobile phone.
I'm going to guess you could fastboot boot boot.img to any rooted boot image for the one plus 7 pro, have root and then install magisk.
larsdennert said:
You need root to extract a partition, but if you have root then you have no need for it except to share it so someone else can get root.
In other words are you rooted already? If not, you'll need to use the other instructions or get a rooted or non rooted image from someone with a T-Mobile phone.
I'm going to guess you could fastboot boot boot.img to any rooted boot image for the one plus 7 pro, have root and then install magisk.
Click to expand...
Click to collapse
Not rooted yet, but everything I have read so far is that you need a patched boot.img to root, or you can create one from the boot.img in an oos package with magisk manager. The problem is, there isn't a tmo oos package out there yet, so it looks like rooting the tmo software isn't possible at the moment. Is this correct?
Sent from my SM-T550 using Tapatalk
Is your bootloader unlocked? That would be step one. Read up on the thread for that.
Not yet, but will be....trying to get my research done before I go for it... don't want to mess it up, been a few years since I rooted a phone.
Sent from my GM1915 using Tapatalk
I want to install the Magisk but not achieved yet because of TWRP is not available and the stock boot.img not found.
Now OTA is coming(1.02.709.7), so I tried to obtain boot.img from the OTA image by the following steps but didn't succeeded.
Download the OTA image by checking the system update on the device.
The image will be stored on /sdcard/Download/OTA_1.01.709.1-1.02.709.7.zip
Copy the OTA image to PC and extract the file "payload.bin".
Use the payload dumper(Thanks to vm03), dump the boot partition from payload.bin but failed with the following error.
Processing boot partition.Unsupported type = 9
* Type of 9 is IMGDIFF according to what I found (no further info).
* I modified "payload_dumper.py" to dump only the boot partition.
Could someone please share the stock boot.img or TWRP for this device?
or tell me another way to achieve this.
Thanks.
I'm looking for it, too. :crying:
Did you get the 1.03.709.1 version boot.img file?
I don't think OTAs contain the whole boot.img, only the binary diff of the new version.
so far nobody has found a boot.img ? the device is around for some months now...
Is there still nothing? Not even a boot.img?
I will post my stock boot.img, recovery.img, and SW version # once I get to my computer.
Should be able to extract it with ADB/commands.
I'm not able to get anything using ADB/fastboot and no root method is working for me. I wish I had an OTA file to work with so I could patch the boot.img and try that but OTAs have already been done on this phone.
The only thing I've managed to do is unlock the bootloader.
Here is a copy of the OTA zip I'm running on
https://drive.google.com/file/d/122ky9if8FqTKz0tvqVi_8-FkA-GjHX9A/view?usp=drivesdk
And here is the payload.bin from that OTA
payload.bin
drive.google.com
So far I haven't managed to get the boot.img and I have a long day tomorrow. Maybe you guys can come up with something?
Well I downloaded the automated script version of payload dumper located here:
How to extract payload.bin from OTA update or firmware
In a few rare cases, you may need to extract the payload.bin that is part of firmware and OTA update files from some OEMs to get the stock boot and system images. This helps when you are looking un…
nerdschalk.com
And that payload.bin seems to only contain abl.img. Nothing else which is unfortunate.
like i've written before, the OTA simply does not contain the whole boot.img - only the binary difference from the previous build.
with only the difference it is not possible to reconstruct a whole boot.img
the only options i see is wait for a RUU or the kernel source to be published
Another OTA came through 227MB, extracted and only thing in there is abl.img again.
is this will work
HTCdev - HTC Kernel Source Code and Binaries
www.htcdev.com
can we find boot.img
Did you get the 1.00.468.1 version boot.img file?
I'll try to port twrp this week.
Just wait for the good news
4096abcd said:
I'll try to port twrp this week.
Just wait for the good news
Click to expand...
Click to collapse
please make one also for htc u20 5g if possibile
lostic-b said:
please make one also for htc u20 5g if possibile
Click to expand...
Click to collapse
Still there's no way to unlock the bootloader of U20
Hi,
I have very awkward problem, when trying to root my xperia xz. I was trying almost everything to fix it, but nothing helped. I used different Magisk version, downloading different stock roms from Xperifirm that fits mine fw, extracting kernel.sin, dumping with flashtool to kernel.elf, and renaming to boot.img, but still the problem occured. I was also trying to root via twrp, but still the same problem. I read tons of guides, but found nothing useful, searched in google and nothing. It seems like the problem is quite rare. I also noticed, that every boot.img, which Magisk can patch, has size below 20MB, for example, boot.img from ROMs downloaded by Xperifirm, have around 35MB, and boot.img transferred from my phone has 65MB. And second thing, when i was trying to modify boot.img via rootkernel, only kernels that rootkernel could modify, were the kernels patchable by Magisk. Rootkernel was getting stuck with kernels from Xperifirm and from my phone. When flashed kernel, that Magisk could patch, bootloop occurred. My stock rom is oreo 8.0.0 41.3.A.2.192-R2E, bootloader is unlocked. Maybe my phone is just unrootable? Or kernels from stock roms are encrypted somehow, and i just don't know how to decrypt them? Every help is really appreciated, thanks.
try to root with twrp
Raghaov said:
try to root with twrp
Click to expand...
Click to collapse
I tried, but it didnt work, i wrote that earlier
Blaska122 said:
Or kernels from stock roms are encrypted somehow, and i just don't know how to decrypt them?
Click to expand...
Click to collapse
Here is what you need to extract your kernel (boot.img) from offical firmware. You will also need to repack it (very simple, just unpack ~ repack) with AIK in order for it to boot properly rooted.
&(*) said:
Here is what you need to extract your kernel (boot.img) from offical firmware. You will also need to repack it (very simple, just unpack ~ repack) with AIK in order for it to boot properly rooted.
Click to expand...
Click to collapse
Thanks for answer!
Thank you all for help, but I recently change my phone, so the thread can be archived.
So I see a lot of people using magisk patched boot images that are really old. It'd be better to patch the image yourself from magisk and use that. The problem might be that it's not that easy to extract it.
You can find most of the stuff from stock rom extracted by me here. The files were extracted from the Indian varient. Make sure to use the appropriate files for your stock rom. The index site does have other files like some old and unstable kernels so don't go flashing everything you see from the root directory. This just started as a personal archive. The domain is free, so idk how long it'll stay active either.
As always, use everything at your own risk.
Do Magisk versions newer than v24.3 work this way?
newt23 said:
Do Magisk versions newer than v24.3 work this way?
Click to expand...
Click to collapse
Yes, patching the boot image is the recommended way to install Magisk.
The official guide does ask to patch AP wholly for samsung devices, but patching the boot image itself is faster.
Official Guide
I don't understand why I get bootloops if I update to v25.x from v24.3 from the Magisk app (using direct method). As I understand it, it also (re-)patches the boot image.
newt23 said:
I don't understand why I get bootloops if I update to v25.x from v24.3 from the Magisk app (using direct method). As I understand it, it also (re-)patches the boot image.
Click to expand...
Click to collapse
That's how I updated too. Try flashing the magisk zip directly.
Or, only update the magisk app, patch the boot image, rename it as boot.img, put it in a tar file, and then flash it to "AP" using Odin.
Hmm... this is funny. I patched the stock boot image and flashed it using Odin and still got bootloops. I took a full nandroid backup beforehand so I was able to get everything working by flashing TWRP again and restoring the previous boot image.
I get bootloops if I install v25.x from TWRP after installing a rom or update to v25.x from v24.3 directly or by patching the stock boot image. The only one that's left now is flashing v25.x zip from TWRP (while having a functioning system with v24.3) but something tells me it's going to end in bootloops too.
Hey everyone, I messed up today trying to root with Magisk using a firmware zip with a different incremental version (but same OOS version) as my device. After flashing the patched boot.img my device is stuck in a bootloop. Unable to boot into system (the text "turn off" with a progress/loading bar shown on my wallpaper), fastboot is still available.
Firmware version before flashing: IN2013_11.C.36_1360_202210310935
Firmware version that the wrong boot.img was extracted from: IN2013_11.C.36_1360_202210171428 (from this thread, under "signed flashable zips>Europe")
Magisk version: 25.2
Recovery: stock
TWRP?: no
I would rather not have to go through the MSM route/fully restore to stock firmware as I am under the impression that these will wipe my data.
I'm now looking for anyone who has the full firmware zip for OOS 12 incremental version (IN2013_11.C.36_1360_202210310935) so that I can extract the stock boot.img file myself. I'm hoping that this manages to fix my mistake.
If anyone is currently running this version and also has TWRP it would also be great if you can follow this guide to extract your boot.img directly from your device.
Another option I am looking into is to flash a stock ROM (with a different build number but the same OOS version: IN2013_11.C.36_1360_202210171428) into my inactive slot without wiping data, I'm not sure if that's wise. Does anyone know if that will work?
update:
- tried booting into older versions of IN2013 firmware using fastboot boot boot.img to no avail.
- Based on the fact that I definitely did an OTA incremental update after upgrading to OOS 12 before, maybe the boot.img was tied to the incremental update zips instead. So, I tried extracting boot.img from incremental update zips (from here, importantly did not have C.36 incremental zips yet) using the FastbootEnhance payload dumping tool, but got the error "multiple dst in one operation" and was unable to continue with this idea.
possible solutions:
1. Flash a full stock firmware to partition A and boot to that. Will this wipe my data?
2. Wait for a full stock firmware zip of IN2013_11.C.36_1360_202210310935 and extract the boot.img myself to flash.
3. Wait for an incremental update zip for C.36 to be uploaded.
4. Somehow find and transfer the stock boot.img that Magisk supposedly makes a backup of when you patch boot.img with the app.
update 2: FIXED
Tried IN2015_11.C.36_1360_202210310935 from this thread for fun. Extracted the boot.img from this one and flashed it. It somehow worked even though it's for a different version????
Doubled checked Oxygen Updater and I am indeed running OTA version IN2013_11.C.36_1360_202210310935.