Related
To those wo have trouble to root their phones!
Try to use a command line lz4 tool, to extract the boot.img from boot.img.lz4. I tried before with 7Zip and it didn't worked. After I tried a command line tool, even the sizes of the boot images were different. This did the trick for me
best regards
nebkas
nebkas said:
To those wo have trouble to root their phones!
Try to use a command line lz4 tool, to extract the boot.img from boot.img.lz4. I tried before with 7Zip and it didn't worked. After I tried a command line tool, even the sizes of the boot images were different. This did the trick for me
best regards
nebkas
Click to expand...
Click to collapse
which one? could u please link to that tool or share here your using?
an-_-dro said:
which one? could u please link to that tool or share here your using?
Click to expand...
Click to collapse
I used that one. Just drop off the boot.img.lz4 on the .exe file.
nebkas said:
I used that one. Just drop off the boot.img.lz4 on the .exe file.
Click to expand...
Click to collapse
i also used that but still not successful >_<
i thought different tool, but anyway thanks.
an-_-dro said:
i also used that but still not successful >_<
i thought different tool, but anyway thanks.
Click to expand...
Click to collapse
I'm sorry. I also flashed the complete downloaded firmware(all files) before I extracted the boot.img.lz4 from it. maybe thats why it worked?
nebkas said:
I'm sorry. I also flashed the complete downloaded firmware(all files) before I extracted the boot.img.lz4 from it. maybe thats why it worked?
Click to expand...
Click to collapse
maybe 4 or 5 attempts with different patched img but i never make it hahaha of course i also flashed complete downloaded firmware after and wait 7 days between each attempt.
I struggled a lot too yesterday(got my device yesterday ). I used also this one to repack the .img and flashed it with the odin version in the bin directory.
7zip is enough to wrap img file to tar
an-_-dro said:
7zip is enough to wrap img file to tar
Click to expand...
Click to collapse
yes, maybe. But who knows what all the apps are doing. that file makes it to a tar.md5.
Thanks OP... it worked on my A605FN.
I was unable to patch the boot image in Magisk Manager as it returned error.
I tried your tool and it patched.
Wouldn't it be simpler to just flash the last Asphyx twrp build, and then flash magisk from twrp?
Sent from my SM-A605FN using Tapatalk
pr1jker said:
Wouldn't it be simpler to just flash the last Asphyx twrp build, and then flash magisk from twrp?
Sent from my SM-A605FN using Tapatalk
Click to expand...
Click to collapse
Sure, but there wasn't any twrp working when I started the Thread
Hello. I am having an issue getting my oem unlock option back. I have followed every tutorial that I could find trying to get rmm back to normal status and have had my a600t1 on for 39 days nonstop. If anyone could give advice or just point me in the right direction I would greatly appreciate it. I'm at a loss. Thanks in advance for any help
guess maybe nobody can help with my issue. i dont know about you all but its polite to answer even if the answer is no.
Just share I have rooted my Samsung Galaxy A6 2018 SM-A600G Android 9 Pie with Magiskm you can watch this video https://youtu.be/1y1p7-Hzm_o
for rooting it, I have to install Magisk twice, one for prevent boot loop after install TWRP and second for rooting after install MagiskManager.
I have a problem with root. I can't set fingerprint because the System crash. After crash i have to install over again. I have notice that twrp recovery have an error when i go in internal storage It have 0mb and i must format
SubGenius said:
Thanks OP... it worked on my A605FN.
I was unable to patch the boot image in Magisk Manager as it returned error.
I tried your tool and it patched.
Click to expand...
Click to collapse
did you have boot.img for this devise but for 9.0 thx
I just received my Galaxy Ultra SM-G998B. Anyone had successfully root your gs21 using magisk? How's the safety net?
Like to hear any feedback before rooting my phone.
Tnx
heya,
anyone got magisk to work yet?
i'm on AP_G998BXXU1AUAC_CL20701476_QB37730003 and trying to install magisk fails by getting immediately stuck on the SAMSUNG boot logo.
i tried, using MagiskManager-v8.0.7.apk (Magisk v21.4):
- extracting AP_G998BXXU1AUAC_CL20701476_QB37730003_REV01_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
- transferring to device (via mtp), patching in manager,
- transferring back via adb pull because the wiki said so
- using Odin3 v3.14.1_3B_PatcheD i flashed BL+CP+CSC+patched_AP, with autoreset on
-> stuck on samsung logo
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried extracting AP, created a tar from boot.img.lz4, patched it on device, transferred back, flashed *just* the patched boot image as AP in ODIN -> same outcome
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried flashing BL+CP+CSC+patched_boot_image, same outcome
then i odin-flashed stock boot tar as AP, device booted normally again
=======
also tried canary magisk; seems like the outcome is always the same. i can reflash stock boot.img and the phone boots fine. i am not sure which canary "version" i had, probably some around 27.01.2021.
thanks for any infos/help
Try magisk canary
I tried rooting the regular S21 but without success yet ( https://forum.xda-developers.com/t/...e-links-and-flashing-discussion-here.4220563/ )
Try magisk canary
Same here with S21+
So for now i lost samsung pass and s health :/
Did someone try patch kermnel locally?
Ziomus said:
Same here with S21+
So for now i lost samsung pass and s health :/
Did someone try patch kermnel locally?
Click to expand...
Click to collapse
Can you describe exactly what you did? So we can cross out the options that don't work ....
Can you do that as well @peterkoarl ?
What exact Magisk app version did you use?
Magisk package version?
Did you patch the AP .tar (large file), or just the boot.img inside?
rodrigofd said:
Can you describe exactly what you did? So we can cross out the options that don't work ....
Can you do that as well @peterkoarl ?
What exact Magisk app version did you use?
Magisk package version?
Did you patch the AP .tar (large file), or just the boot.img inside?
Click to expand...
Click to collapse
thanks for your reply, i updated my OP with all the infos
peterkoarl said:
thanks for your reply, i updated my OP with all the infos
Click to expand...
Click to collapse
Couple things:
* are you keeping your data intact between flashes? i.e. no format?
There's a chance that booting a custom boot.img, on a device that already has data created from a stock boot.img, doesn't work (because of the encryption key)... but I can't say for sure, it's an assumption.
* Also, how long are you really waiting on SAMSUNG logo screen, after flashing magisk'ed boot.img?
I recall that the first boot after doing this, can take several minutes, specially if you have many apps installed
rodrigofd said:
* are you keeping your data intact between flashes? i.e. no format?
There's a chance that booting a custom boot.img, on a device that already has data created from a stock boot.img, doesn't work (because of the encryption key)... but I can't say for sure, it's an assumption.
Click to expand...
Click to collapse
i used CSC, not HOME_CSC - i thought that would mean that data gets wiped?
i did not manually do anything in regards to formatting. what .. could i do?
rodrigofd said:
* Also, how long are you really waiting on SAMSUNG logo screen, after flashing magisk'ed boot.img?
I recall that the first boot after doing this, can take several minutes, specially if you have many apps installed
Click to expand...
Click to collapse
yeah i remember that as well from older devices; i let it sit for at least 10 minutes on the initial flash to make sure, so im pretty sure its stuck.
i just tried (again) using latest canary 6fb20b3e (21406) to patch the whole ~7G AP file,
transferred it back via adb pull,
flashed it together with BL+CP+CSC,
to no avail - again stuck at SAMSUNG logo. gonna wait another 15 minutes but.... it seems stuck.
peterkoarl said:
i just tried (again) using latest canary 6fb20b3e (21406) to patch the whole ~7G AP file,
transferred it back via adb pull,
flashed it together with BL+CP+CSC,
to no avail - again stuck at SAMSUNG logo. gonna wait another 15 minutes but.... it seems stuck.
Click to expand...
Click to collapse
Have you tried patching just the raw boot.img file? (Not tar'ed)
You need to uncompress the boot.img.lz4 file first, so you get a boot.img, copy that file to the phone, and select it with Magisk app.
Then get back the patched *.img file into the PC, rename it back to boot img, put it in a TAR, and flash that TAR with Odin.
peterkoarl said:
heya,
anyone got magisk to work yet?
i'm on AP_G998BXXU1AUAC_CL20701476_QB37730003 and trying to install magisk fails by getting immediately stuck on the SAMSUNG boot logo.
i tried, using MagiskManager-v8.0.7.apk (Magisk v21.4):
- extracting AP_G998BXXU1AUAC_CL20701476_QB37730003_REV01_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
- transferring to device (via mtp), patching in manager,
- transferring back via adb pull because the wiki said so
- using Odin3 v3.14.1_3B_PatcheD i flashed BL+CP+CSC+patched_AP, with autoreset on
-> stuck on samsung logo
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried extracting AP, created a tar from boot.img.lz4, patched it on device, transferred back, flashed *just* the patched boot image as AP in ODIN -> same outcome
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried flashing BL+CP+CSC+patched_boot_image, same outcome
then i odin-flashed stock boot tar as AP, device booted normally again
=======
also tried canary magisk; seems like the outcome is always the same. i can reflash stock boot.img and the phone boots fine. i am not sure which canary "version" i had, probably some around 27.01.2021.
thanks for any infos/help
Click to expand...
Click to collapse
Try to get the vbmeta disabled tar file and place it in Odin's userdata along the other files to flash, disable auto reboot and manually reboot your phone while keeping power+volup pressed which will allow you to wipe data. Reboot and enjoy
peterkoarl said:
heya,
anyone got magisk to work yet?
i'm on AP_G998BXXU1AUAC_CL20701476_QB37730003 and trying to install magisk fails by getting immediately stuck on the SAMSUNG boot logo.
i tried, using MagiskManager-v8.0.7.apk (Magisk v21.4):
- extracting AP_G998BXXU1AUAC_CL20701476_QB37730003_REV01_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
- transferring to device (via mtp), patching in manager,
- transferring back via adb pull because the wiki said so
- using Odin3 v3.14.1_3B_PatcheD i flashed BL+CP+CSC+patched_AP, with autoreset on
-> stuck on samsung logo
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried extracting AP, created a tar from boot.img.lz4, patched it on device, transferred back, flashed *just* the patched boot image as AP in ODIN -> same outcome
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried flashing BL+CP+CSC+patched_boot_image, same outcome
then i odin-flashed stock boot tar as AP, device booted normally again
=======
also tried canary magisk; seems like the outcome is always the same. i can reflash stock boot.img and the phone boots fine. i am not sure which canary "version" i had, probably some around 27.01.2021.
thanks for any infos/help
Click to expand...
Click to collapse
Patch the extracted the boot.img first and rename the patched boot to "boot.img" BEFORE (not after) compressing it to tar.
Also ensure to enable OEM unlocking in Developer options before flashing the patched boot tar
thanks for all the replies.
i tried the "boot.img only" approach first; makes no difference. magisk says it patched it fine, renamed it back to boot.img, tar'ed it into boot.img.tar, flashed that via odin without autoreboot. cant even get into recovery after restarting.
EDIT: i WAS able to enter stock recovery now; i realized that since i need to have the pc/usb cable connected to be able to enter download mode, maybe i need the same for recovery - and yes, volup+power while cable is connected does drop me into recovery. however, even after factory reset there, it wont boot.
EDIT2: yes my bootloader is unlocked, oem option in dev is greyed out.
EDIT3: i re-did the boot.img-only approach and made sure that i got into recovery IMMEDIATELY after odin this time; did a factory reset and cache wipe. hit power off. powered the phone back on. stuck on samsung logo. this does not seem to be going anywhere.
i didnt know anything about vbmeta before, starting to google it now.
DaReDeViL said:
Try to get the vbmeta disabled tar file and place it in Odin's userdata along the other files to flash, disable auto reboot and manually reboot your phone while keeping power+volup pressed which will allow you to wipe data. Reboot and enjoy
Click to expand...
Click to collapse
i.. think i tried exactly this now; i used the vbmeta.tar from https://forum.xda-developers.com/t/howto-flash-a-blank-vbmeta.4136509/ (there are 2 files attached there which are exactly the same, not sure whats going on with that)
in odin, i used BL/CP/CSC from orig rom, the FULL (7gb) magisk patched AP, and the vbmeta.tar in USERDATA
powered off manually, rebooted into recovery, and the first time i got a recovery-android-logo and a text "erasing" for like a second or two. then the device rebooted, and got stuck on samsung logo again.....
peterkoarl said:
i.. think i tried exactly this now; i used the vbmeta.tar from https://forum.xda-developers.com/t/howto-flash-a-blank-vbmeta.4136509/ (there are 2 files attached there which are exactly the same, not sure whats going on with that)
in odin, i used BL/CP/CSC from orig rom, the FULL (7gb) magisk patched AP, and the vbmeta.tar in USERDATA
powered off manually, rebooted into recovery, and the first time i got a recovery-android-logo and a text "erasing" for like a second or two. then the device rebooted, and got stuck on samsung logo again.....
Click to expand...
Click to collapse
Try to reboot to recovery again and do a factory reset.
Btw, find attached the vbmeta disabled tar file I use
DaReDeViL said:
Try to reboot to recovery again and do a factory reset.
Btw, find attached the vbmeta disabled tar file I use
Click to expand...
Click to collapse
thanks, tried, no difference
looking closer at your img, it seems to hold keys for the SM-G981B (Galaxy S20).
i *guess* i need the same thing for my model - my research into how this is done has unfortunately so far been unfruitful....
some more info; when unpacking stock AP, i get the following files:
24/01/2021 14:22 19.864.283 boot.img.lz4
24/01/2021 14:22 658.262 dtbo.img.lz4
24/01/2021 14:25 1.130 metadata.img.lz4
24/01/2021 14:22 2.769 misc.bin.lz4
24/01/2021 14:22 45.072.126 recovery.img.lz4
24/01/2021 14:25 6.207.213.323 super.img.lz4
24/01/2021 14:25 734.568.963 userdata.img.lz4
24/01/2021 14:25 3.751 vbmeta.img.lz4
24/01/2021 14:25 2.815 vbmeta_system.img.lz4
24/01/2021 14:22 12.136.709 vendor_boot.img.lz4
is it possible that this vendor_boot.img is interfering with magisk?
do i need to touch vbmeta_system somehow?
are any of these "new", as in, magisk cannot handle that stuff (yet)?
Try following this guide for the S20 series as it should be the same theoretically. I'm gonna try it as soon as I get my s21 ultra
hello guys just got Android 11 update and I'd like to know how to root, I've never rooted this device defore so i need a full tutorial thanks in advance
Install magisk manager get your phones firmware from samfw or any other site transfer the AP file to your phone open magisk manager click install , patch a file and select the ap file after its patched get the file using adb "adb pull" and then flash it with magisk including bl csc and the rest. Like this response if it helped you
Sloobot said:
Install magisk manager get your phones firmware from samfw or any other site transfer the AP file to your phone open magisk manager click install , patch a file and select the ap file after its patched get the file using adb "adb pull" and then flash it with magisk including bl csc and the rest. Like this response if it helped you
Click to expand...
Click to collapse
worked for me. thank you so much
from samsung galaxy A71 Android 11
AsifMohiuddin said:
worked for me. thank you so much
from samsung galaxy A71 Android 11
Click to expand...
Click to collapse
Im glad to hear that
Do you mean flash it with Odin? I don't see how I can flash the tar with Magisk.
Sloobot said:
Install magisk manager get your phones firmware from samfw or any other site transfer the AP file to your phone open magisk manager click install , patch a file and select the ap file after its patched get the file using adb "adb pull" and then flash it with magisk including bl csc and the rest. Like this response if it helped you
Click to expand...
Click to collapse
Do you mean flash it with Odin? I don't see how I can flash the tar with Magisk. Sorry for the double post. I don't know how I can delete the other message.
Codename_Falcon said:
Do you mean flash it with Odin? I don't see how I can flash the tar with Magisk. Sorry for the double post. I don't know how I can delete the other message.
Click to expand...
Click to collapse
Yes im talking about odin but now there is another method
So what about the Samsung Pass status? R11 ?? A715F/DS
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.
235anders15 said:
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
Click to expand...
Click to collapse
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
sam_htc_touch said:
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
Click to expand...
Click to collapse
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
235anders15 said:
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
Click to expand...
Click to collapse
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
sam_htc_touch said:
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
Click to expand...
Click to collapse
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
sam_htc_touch said:
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
Click to expand...
Click to collapse
Just for the benefit of all (if it matters), noticed that Magisk wasn't passing the Safety Net check and was showing failed for all 3. Used this fix and all is well now (Used the Sept 13 update on the page)
previously patching with stable 11.1.1.1 and broke some major functionality (eg: wifi crash, mess up video player and codec), now try to patch with magisk version, will update later
abhi0039 said:
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.
Click to expand...
Click to collapse
stable.img from there (and the other ones) dont fastboot boot on my OSS 1.1.1.1 fastboot mode.
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
F5:ed said:
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
Click to expand...
Click to collapse
Press and hold vol up, down , power at the same time for a while it will boot to fastboot.
I got boot loop after updating to 11.1.2.2
Any new boot img?
izik.avi said:
I got boot loop after updating to 11.1.2.2
Any new boot img?
Click to expand...
Click to collapse
Haven't tested yet but here you go
rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
This one works great. Thank you.
The attached file in #13 above worked, thank you!
In case someone would like to now "How to do it" until next time this is how I did it:
How to install OOS update and root via created patch.img file in the Magisk app
1. Download the full version eg the OOS 11.x.x.x.zip file on the computer, and copy the file to the phone's internal memory as well.
2. Run the payload_dump program (https://androidfilehost.com/?fid=1899786940962605222) to extract a boot.img from the computer. You have to extract the payload.bin file from the OOS 11.x.x.x.zip file and place it in the Input folder, then run the exe-file and wait for payload to complete, then copy over the boot.img file found in the Output folder to the phone.
3. Go to Magisk app on the phone, click on the top install "Magisk", click "Select and patch a file", search for the boot.img file you created.
4. Now, Magisk will create a patched magic.img file from the boot.img file (can be called eg magic_patched-23000_xt8QR.img)
5. Copy the magisk_patched-xxxxxxx.img to your computer's "Root folder" where you have stored ADB files, etc
6. Now install the OOS 11.x.x.x zip file (should be in the mobile's Internal memory) via Settings> System> System updates and the "gear"> Local upgrade
7. When done, DO NOT reboot but go directly to Fastboot mode + connect cable to the computer
8. On the computer, type from your "Root folder":
fastboot flash boot magisk_patched-xxxxxxx.img
9. Reboot the phone - you are rooted!
rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
raymund08 said:
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
Click to expand...
Click to collapse
Yes
rippledrums said:
Yes
Click to expand...
Click to collapse
Thank you
Can confirm OP fastboot commands and patched boot img are working for 11.1.1.1.I uninstalled magisk by mistake and could regain root, quick and painless
Can anyone help me? flashed patched boot to A and B Slot. But Magisk is N/A. Any idea?
Hi there, did anyone install magisk and root on new global rom using Fastboot?
To get boot.img I used this tool - https://github.com/ssut/payload-dumper-go/releases/tag/1.2.2
After that I patched boot.img in Magisk app as usual and then upload patched img using ADB and fastboot. But as a result - phone endless reboot.
Of course I uploaded original boot.img and the phone is back, but right now I`m trying to understand what I messed up.
Magisk 25.2, rom miui_STARGlobal_V14.0.1.0.TKAMIXM_f8a19b0595_13.0
Any ideas? Thx
Bro, download 14.0.1 global rom and open with winrar then pull out source file boot.img and copy to phone to patch it. Using tool to reverse build boot.img may cause errors.
diorlee90 said:
Bro, download 14.0.1 global rom and open with winrar then pull out source file boot.img and copy to phone to patch it. Using tool to reverse build boot.img may cause errors.
Click to expand...
Click to collapse
This method also causes loop. Phone boots to main screen, but after 10 seconds, it reboots into stock recovery.
Venomz33 said:
This method also causes loop. Phone boots to main screen, but after 10 seconds, it reboots into stock recovery.
Click to expand...
Click to collapse
i used many times without any errors, after patch boot.img via magisk you must copy patched file img to computer and flash via adb_platform-tools. If any error check command again.
diorlee90 said:
i used many times without any errors, after patch boot.img via magisk you must copy patched file img to computer and flash via adb_platform-tools. If any error check command again.
Click to expand...
Click to collapse
I've done exactly the same. Done before but 14 gives this problem. I patched using the command below from CMD.
C:] fastboot flash boot boot.img