Attempting to extract the boot.img from your latest Essential PH-1 rom and all I'm seeing is a payload.bin
Is there a way to extract it from the bin?
Trying to flash Magisk which requires flashing a custom boot.img before Magisk.zip
Thanks!
Use Android kitchen
Bro try to use zip extractor and even you could use Android kitchen to extract boot.img to ramdisk &split-img
You could find required files therefore
jAm-0 said:
Attempting to extract the boot.img from your latest Essential PH-1 rom and all I'm seeing is a payload.bin
Is there a way to extract it from the bin?
Trying to flash Magisk which requires flashing a custom boot.img before Magisk.zip
Thanks!
Click to expand...
Click to collapse
I have a boot.img file that i can use to root my Samsung J2 SM-J260F - if I flash this with Odin everything is Ok. Now I want to edit a file in the ramdisk of the boot.img to make the phone boot on power. However simply unpacking the Boot.img and unzipping the ramdisk then repacking fails - even when i do not edit anything in the ramdisk. When the repacked boot.img is flashed with Odin the device gets into a boot loop.
I am using the Carliv Image Kitchen for Androidv1.3 tool to do the packing and unpacking.
Is there some specific aspect of the Samsung boot.img such as a signature that is causing this to fail?
Progress update
The only unpacking tool that seemed to correctly repack the image was MTK_Extractor_V2.63 - all of the other (many) utilities I tried did not seem to repack the ramdisk correctly and caused the phone to boot into the recovery screen.
Changing the init.rc and init_samsungexynos7570.rc files as follows finally led to success.
In file init.rc
delete everything under "on charger" then add back setprop sys.powerctl reboot
Under "service lpm /system/bin/lpm"
delete class sec-charger critical and replace with trigger late-init
In file init_samsungexynos7570.rc
delete everything under "on property:ro.bootmode=charger"
AndyJN said:
I have a boot.img file that i can use to root my Samsung J2 SM-J260F - if I flash this with Odin everything is Ok. Now I want to edit a file in the ramdisk of the boot.img to make the phone boot on power. However simply unpacking the Boot.img and unzipping the ramdisk then repacking fails - even when i do not edit anything in the ramdisk. When the repacked boot.img is flashed with Odin the device gets into a boot loop.
I am using the Carliv Image Kitchen for Androidv1.3 tool to do the packing and unpacking.
Is there some specific aspect of the Samsung boot.img such as a signature that is causing this to fail?
Click to expand...
Click to collapse
Did you unlocked the bootloader?
Also i would recommend you to use a custom recovery like TWRP to flash boot.img
AndyJN said:
I have a boot.img file that i can use to root my Samsung J2 SM-J260F - if I flash this with Odin everything is Ok. Now I want to edit a file in the ramdisk of the boot.img to make the phone boot on power. However simply unpacking the Boot.img and unzipping the ramdisk then repacking fails - even when i do not edit anything in the ramdisk. When the repacked boot.img is flashed with Odin the device gets into a boot loop.
I am using the Carliv Image Kitchen for Androidv1.3 tool to do the packing and unpacking.
Is there some specific aspect of the Samsung boot.img such as a signature that is causing this to fail?
Click to expand...
Click to collapse
TBM 13 said:
Did you unlocked the bootloader?
Also i would recommend you to use a custom recovery like TWRP to flash boot.img
Click to expand...
Click to collapse
Which.... does not exist. J2 Core doesnt get the same love.
I recommend Android Image Kitchen (AIK) by Osmosis. Havent failed me once in my case.
Prove N. said:
Which.... does not exist. J2 Core doesnt get the same love.
Click to expand...
Click to collapse
I'm sorry, my bad.
has anyone tried to port the 9 pie firmware from J260A to other J260F/M/G?
Hi everyone!
I need to edit an APK in stock ROM (system.img) of my device. I have unpacked system.img and repacked with some programs on Windows. But When I unpack and repack the system.img file and change it with original system.img file (even though I didn't change any APK or anything), I can flash it through fastboot or port 9008 successfully. BUT When I try to start my phone, It stuck on MI Logo screen.
So There is no problem with flash any rom. But I want to unpack rom and edit an APK then repack it. This is my issue. How can I do it? I think there is a problem on unpack/repack step. I'll be glad if anyone can help me about it.
Thanks in advance!
p.s. I can't flash a recovery rom because of I can't run phone.
Hey everyone, I'm trying to root my Xiaomi Mi a2 lite without twrp since, if i understand correctly, it needs the data partition to be formatted as it cant decrypt it, and I don't really need it anyway. I wanted to use Magisk manager to patch a boot image and flash it to get root, but the app explicitly asks for .img files. I've been looking everywhere and I can only find zip archives or .tgz files of my firmware. I'd appreciate any help, and btw my build number is 11.0.21.0
Ame76 said:
Hey everyone, I'm trying to root my Xiaomi Mi a2 lite without twrp since, if i understand correctly, it needs the data partition to be formatted as it cant decrypt it, and I don't really need it anyway. I wanted to use Magisk manager to patch a boot image and flash it to get root, but the app explicitly asks for .img files. I've been looking everywhere and I can only find zip archives or .tgz files of my firmware. I'd appreciate any help, and btw my build number is 11.0.21.0
Click to expand...
Click to collapse
A TGZ file is a TAR Archive file that has been compressed using Gnu Zip (gzip).
You can uncompress tgz files using 7-zip:
7-Zip
7-zip.org
VD171 said:
A TGZ file is a TAR Archive file that has been compressed using Gnu Zip (gzip).
You can uncompress tgz files using 7-zip:
7-Zip
7-zip.org
Click to expand...
Click to collapse
oooh thank you so much, feeling pretty stupid rn
Obviously, first you need unlocked bootloader, or your device will get bricked.
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. (Attention: TAR and NOT tgz.)
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file and wait until it finish.
6. Open the folder "Downloads" and uncompress the file magisk_patched.tar to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img. (You need to flash patched vbmeta because vbmeta verifies if any partition was changed.)
Done, you are rooted.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.
You can use 7-Zip: https://7-zip.org
VD171 said:
Obviously, first you need unlocked bootloader, or your device will get bricked.
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. (Attention: TAR and NOT tgz.)
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file and wait until it finish.
6. Open the folder "Downloads" and uncompress the file magisk_patched.tar to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img. (You need to flash patched vbmeta because vbmeta verifies if any partition was changed.)
Done, you are rooted.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.
You can use 7-Zip: https://7-zip.org
Click to expand...
Click to collapse
thanks dude, you're really helping me out with this
VD171 said:
Obviously, first you need unlocked bootloader, or your device will get bricked.
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. (Attention: TAR and NOT tgz.)
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file and wait until it finish.
6. Open the folder "Downloads" and uncompress the file magisk_patched.tar to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img. (You need to flash patched vbmeta because vbmeta verifies if any partition was changed.)
Done, you are rooted.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.
You can use 7-Zip: https://7-zip.org
Click to expand...
Click to collapse
Hey i seem to be having a problem, i extracted the .tar file and i can see the boot.img file but i can't find the vbmeta.img one
Ame76 said:
Hey i seem to be having a problem, i extracted the .tar file and i can see the boot.img file but i can't find the vbmeta.img one
Click to expand...
Click to collapse
Actually i've looked around and everyone only shares the boot file, maybe flashing vbmeta is unnecessary for this device?
Maybe.
Hey guys can someone please upload the boot.img from the FW V13.0.5.0.SKOEUXM?
I did a big mistake and thought that android 12 can boot in twrp (recovery). Flashed a wrong boot.img and cant get my phone working now. Only Fastboot is working - the normal Recovery didnt boot so i cant even install the Update through the orignal system recovery.
Cause theres only a Recovery zip of it online i cant use the MiFlash Tool, since a downgrade to Android 11 isnt possible
thanks a lot!
You can download the OTA zip file from Xiaomi firmware updater or by using the app MiuiDownloader from Playstore
Unzip, you will find payload.bin inside - use the PC tool (there is a thread on XDA) Payload_Dumper to dump boot.img and other images
Anyway, here is the link to the boot-stock-lisa_EEA_V13.0.5.0.SKOEUXM_12.0.img
I had extracted and renamed (name does not matter):
File on MEGA
mega.nz
oh god! thank you very much!
will test it in few minutes
edit: It worked instantly! you made my day
Can someone please upload the boot.img from V13.0.2.0(SKOMIXM) to root?