Database Users

US996 - Boot.img // Magisk

I was wondering if anybody had a stock boot.img for the US996, version h if its important.
The reason I'm looking for it is to install magisk on my device. I'm on WETA if it matters.
NOTE:
I downloaded the .kdz from lg-firmwares but it didnt seem to contain a 'boot.img' file, and the only source I've found for a boot.img is at
Code:
https://build.nethunter.com/misc/us996/v10d/?C=N&O=D
but it seems this is a very old version (assuming they change).
Thanks!
Also, If anyone has tips/guide for installing magisk on the US996 it would be awesome! Been having some troubles with it.

Give a thanks to @dwertz for this post, it might help.
dwertz said:
For Verizon:
You don't need to do the entire root process over. Get the KDZ for 12A from here https://forum.xda-developers.com/v20/development/vs995-kdz-t3527538
Get the LGExtract tool from here https://forum.xda-developers.com/showthread.php?t=2600575
Extract the kdz. It will be a bunch of files and a dz file. Extract the dz file. There should be a boot_6.bin file. Rename it to boot.img. Put that on your sdcard
Here is the link to my VS995 boot.img (This is the already extracted VS995 12A boot.img) skip the above steps https://drive.google.com/file/d/0B-JjsdrM6j0bQWRuVTNkX1FkWHc/view?usp=sharing
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
UnSu https://forum.xda-developers.com/showpost.php?p=63615067&postcount=2439
Install a terminal emulator - it makes it easier.
Make sure you have these files below on your sdcard:
boot.img from above kdz that you extracted
Magisk 11.1.zip
UnSU.zip
ReStock1.0 kernel
1. Install the Magisk Manager App
2. Go into SuperSu app do a full unroot.
3. Go into Terminal emulator and type "Reboot Recovery"
4. In TWRP Flash UnSu.zip (to remove any traces of SU)
5. Flash boot.img (this is the stock boot.img)
6. Flash Magisk.zip (magisk contains its own SU)
7. Flash ReStock 1.0 kernel.
8. Reboot
9. Open Magisk app and check to see if Safetynet passes. It should.
Maybe I will upload the boot.img when I get home from work to make the process a little easier.
Click to expand...
Click to collapse

Here's a US996 10h stock boot image,
https://mega.nz/#!SZoQBITQ!PUl1Q4wFb2rVMv8qzbf8p1Jp6yp8sFwRLSW8LnrszaM
Extracted from the kdz

McNutnut said:
Here's a US996 10h stock boot image,
https://mega.nz/#!SZoQBITQ!PUl1Q4wFb2rVMv8qzbf8p1Jp6yp8sFwRLSW8LnrszaM
Extracted from the kdz
Click to expand...
Click to collapse
Where is the boot.img file? is it 'system.img'?

DP2 Q Beta (T-Mobile) with magisk looking for patched twrp

Hi I got DP2 to run on T-Mobile with magisk by patching the boot.img with magisk manager and after flashing images and formatting. I was wondering if anyone had a patched boot with twrp. I guess the recovery is inside the boot img for dp2 and maybe even dp3 I was hoping someone could share it I'll patch it again with magisk manager and make a shared backup so others could try and maybe get dp3 to work ,I've tried, thought I got it , and failed.
But yeah thanks for the time
On stable version I used 9.0.11
Unpack the dp2 zip and flash the system.img, vendor.img, and boot.img using twrp
format the system, vendor, boot
Reboot bootloader and flash the vbmeta
fastboot flash vbmeta vbmeta.img
Once boot download magisk and upload same boot.img to phone and patch using magisk manager

Magisk and Android 11

Hi, I'm interesed on android beta 11 but I have a lot of customizations root related in Android 10, (includes soli radar use and GSM doze, for example).
The question is Magisk Canary version works on 11? Or the better is wait for a update or android stable version?

Hi, root is working with the canary version of magisk. Most of the apps who needs root are working....( Titanium Backup,Adaway) The only app that isn t working for me is Swift installer for theming.....
Greetz

Hi, can someone help me? I'm on the Pixel 4 Android 11 Beta, I installed the new Magisk manager (the Canary version I think?), and patched the boot image, but after flashing I'm stuck in the bootloader and I can't even turn off the phone anymore. Also, I saw 4 channels in the settings of the manager, stable, beta, canary and canary (debug), but I don't know which one to use and if it matters? Help is really appreciated!

bjonkheer said:
Hi, can someone help me? I'm on the Pixel 4 Android 11 Beta, I installed the new Magisk manager (the Canary version I think?), and patched the boot image, but after flashing I'm stuck in the bootloader and I can't even turn off the phone anymore. Also, I saw 4 channels in the settings of the manager, stable, beta, canary and canary (debug), but I don't know which one to use and if it matters? Help is really appreciated!
Click to expand...
Click to collapse
what boot.img do you use? i´m a little cofused because the image for download is flame-rpp4.200409.015-factory-8012c549 but my pixel says are in rpp4.200409.020 I´m scared for the bootloop or something if I flash the 015 boot image.
***Edit:
Forget it, I found and download the RPB1.200504.020

caballero221 said:
what boot.img do you use? i´m a little cofused because the image for download is flame-rpp4.200409.015-factory-8012c549 but my pixel says are in rpp4.200409.020 I´m scared for the bootloop or something if I flash the 015 boot image.
***Edit:
Forget it, I found and download the RPB1.200504.020
Click to expand...
Click to collapse
How did you root I have difficult to do it years Root pixels and pixel 4 won't root.
Any guide apriciated.

caballon said:
How did you root I have difficult to do it years Root pixels and pixel 4 won't root.
Any guide apriciated.
Click to expand...
Click to collapse
It's really simple: you download the build from Google the build you have installed on your phone, unzip It, and unzip it again and again the archives inside the unzip folder until you see the boot.img
Copy this boot.img and paste to your internal storage, install the magisk Canary apk and select install magisk zip. Select "patch selected image" in the instalation metod, and select the boot.img copypasted before. Copy the new patched boot.img to your computer and flash to your phone via fastboot mode.
Sent from my Pixel 4 using XDA Labs

caballero221 said:
It's really simple: you download the build from Google the build you have installed on your phone, unzip It, and unzip it again and again the archives inside the unzip folder until you see the boot.img
Copy this boot.img and paste to your internal storage, install the magisk Canary apk and select install magisk zip. Select "patch selected image" in the instalation metod, and select the boot.img copypasted before. Copy the new patched boot.img to your computer and flash to your phone via fastboot mode.
Click to expand...
Click to collapse
In the bootloader or fastboot mode.

caballon said:
In the bootloader or fastboot mode.
Click to expand...
Click to collapse
In the bootloader, via fastboot commands
Sent from my Pixel 4 using XDA Labs

I get the problem when I try to flash patched boot img, I end up in the bootload with status 'no valid boot slot to boot'. Any hints?
Can anybody upload patched magisk boot img for pixel 4 .020 ?

I get the same error in beta2, I think must flash the same boot.img of the zip (patched, obviously) but this means clean flash (flash-all) every update and lost the data
Sent from my Pixel 4 using XDA Labs

Has anyone managed to root android 11 beta3? when I try to flash patched boot img, I end up in the bootload with status "no valid boot slot to boot".

Do you use Magisk Canary to patch?
You update via OTA or full flash?
Sent from my Pixel 4 using XDA Labs

caballero221 said:
Do you use Magisk Canary to patch?
You update via OTA or full flash?
Sent from my Pixel 4 using XDA Labs
Click to expand...
Click to collapse
I've used latest Magisk Canary. I've update via ota the i've used Factory Image (cancelled -w) to reboot the phone to normality .
I've also a Pixel 3 that i root without no problem with the same method.

grigiotitan said:
I've used latest Magisk Canary. I've update via ota the i've used Factory Image (cancelled -w) to reboot the phone to normality .
I've also a Pixel 3 that i root without no problem with the same method.
Click to expand...
Click to collapse
I don't know why, but since beta 2 the method don't work. My pixel 4 fall in bootloop in the same way, and only fix flashing the OTA. Before, I think only work with full whipped beta installation and patch specific the boot.img of the full beta img flashed, but not tested yet
Sent from my Pixel 4 using XDA Labs

[GUIDE] Magisk for Android 11 Developer Preview 3 & 4 (NA, EU, IN)

As some may have noticed magisk is not working out of the box on the Android 11 Developer Preview on both the OnePlus 8 and OnePlus 8 Pro.
This is due to a missing /apex folder in the ramdisk of the boot.img. See github bug report here: https://github.com/topjohnwu/Magisk/issues/2994
I've patched the ramdisk with the missing /apex folder and latest magisk canary build for the OnePlus 8 and OnePlus 8 Pro. These images are unified for the North American, European, and Indian models.
Android 11 Developer Preview 3 Magisk Patched for OnePlus 8 Pro (IN2025, IN2023, IN2021): https://www.androidfilehost.com/?fid=8889791610682915784
Android 11 Developer Preview 4 Magisk Patched for OnePlus 8 Pro (IN2025, IN2023, IN2021): https://www.androidfilehost.com/?fid=8889791610682931280
Android 11 Developer Preview 3 Magisk Patched for OnePlus 8 (IN2015, IN2013, IN2011): https://www.androidfilehost.com/?fid=8889791610682915786
Android 11 Developer Preview 4 Magisk Patched for OnePlus 8 (IN2015, IN2013, IN2011): https://www.androidfilehost.com/?fid=8889791610682931278

xian1243 said:
As some may have noticed magisk is not working out of the box on the Android 11 Developer Preview 3 on both the OnePlus 8 and OnePlus 8 Pro.
This is due to a missing /apex folder in the ramdisk of the boot.img. See github bug report here: https://github.com/topjohnwu/Magisk/issues/2994
I've patched the ramdisk with the missing /apex folder and latest magisk canary build for the IN2015 and IN2015 (OnePlus 8 and OnePlus 8 North American models). These will not work on the European or other models (although the process for fixing those is the same).
Android 11 Developer Preview 3 Magisk Patched for OnePlus 8 Pro (IN2025): https://www.androidfilehost.com/?fid=8889791610682915784
Android 11 Developer Preview 3 Magisk Patched for OnePlus 8 (IN2015): https://www.androidfilehost.com/?fid=8889791610682915786
Click to expand...
Click to collapse
Thanks for the effort! I will download DP3 and report back.:good:

Thanks worked for me on Oneplus 8 IN2011 Indian variant
xian1243 said:
As some may have noticed magisk is not working out of the box on the Android 11 Developer Preview 3 on both the OnePlus 8 and OnePlus 8 Pro.
This is due to a missing /apex folder in the ramdisk of the boot.img. See github bug report here: https://github.com/topjohnwu/Magisk/issues/2994
I've patched the ramdisk with the missing /apex folder and latest magisk canary build for the OnePlus 8 and OnePlus 8 Pro. These images are unified for the North American, European, and Indian models.
Android 11 Developer Preview 3 Magisk Patched for OnePlus 8 Pro (IN2025, IN2023, IN2021): https://www.androidfilehost.com/?fid=8889791610682915784
Android 11 Developer Preview 3 Magisk Patched for OnePlus 8 (IN2015, IN2013, IN2011): https://www.androidfilehost.com/?fid=8889791610682915786
Click to expand...
Click to collapse
How it worked for me ?
Steps i did !
1 . downloaded above magisk patched img
2. then installed latest magisk canary apk v : eec19ba9
3. Then patched the above downloaded boot.img with canary magisk
4. finally flashed using fastboot command i.e fastboot flash boot filename.img
5. reboot ( enjoy )

Aquib1999 said:
How it worked for me ?
Steps i did !
1 . downloaded above magisk patched img
2. then installed latest magisk canary apk v : eec19ba9
3. Then patched the above downloaded boot.img with canary magisk
4. finally flashed using fastboot command i.e fastboot flash boot filename.img
5. reboot ( enjoy )
Click to expand...
Click to collapse
Hello,
Thanks for your efforts, which one should I use on my IN2017 T-Mobile (Converted to Global) if possible.
Thanks:good:

Doesn't work for me on the T-Mobile variant converted to global then DP3, Magisk just says Installed: N/A.

pro_granade said:
Doesn't work for me on the T-Mobile variant converted to global then DP3, Magisk just says Installed: N/A.
Click to expand...
Click to collapse
Same issue. Only have options to patch a boot file or download zip

NikoZBK said:
Same issue. Only have options to patch a boot file or download zip
Click to expand...
Click to collapse
You on a T-Mobile phone converted?

pro_granade said:
You on a T-Mobile phone converted?
Click to expand...
Click to collapse
That's right

NikoZBK said:
That's right
Click to expand...
Click to collapse
Hmm, I'll look into it and see what it's doing.

Can you add 2010 patched

i have dp4 patched it just doesnt pas safty net to the converted tmo

Will update this with DP4 shortly. FWIW, SafteyNet will not pass on DP4 yet as it hasn't been certified by Google.

xian1243 said:
Will update this with DP4 shortly. FWIW, SafteyNet will not pass on DP4 yet as it hasn't been certified by Google.
Click to expand...
Click to collapse
You have to use magiskhide propsconfig and it will pass safety net on dp4.. use the finger print file for op8 and all will be good..
Edit. Seems magiskhide breaks WiFi on dp4 on my phone though

Aquib1999 said:
How it worked for me ?
Steps i did !
1 . downloaded above magisk patched img
2. then installed latest magisk canary apk v : eec19ba9
3. Then patched the above downloaded boot.img with canary magisk
4. finally flashed using fastboot command i.e fastboot flash boot filename.img
5. reboot ( enjoy )
Click to expand...
Click to collapse
can you explain step 3-4?? i got the patched img from above and clicked
magisk install
select and patch a file
choose the dp3_op8p img
then it says "unsupported/unknown image format, installation failed"

The images I've created are already patched with the latest magisk canary, no need to patch them again. Just flash in fastbootd.

When I fastboot flashed the patche image It gave error messages in the terminal window and the phone went into qualcomm crashdump mode :/

thanks dev can you add open beta 1

this is a link to the ob1 patched boot img i made with the latest magisk canary. it worked for me. if you cant extract the boot.img maybe try this
https://drive.google.com/file/d/19vl9wt5HAYFRuy5mGJlsg2cGXJVxY2CT/view?usp=drivesdk

42o247 said:
this is a link to the ob1 patched boot img i made with the latest magisk canary. it worked for me. if you cant extract the boot.img maybe try this
https://drive.google.com/file/d/19vl9wt5HAYFRuy5mGJlsg2cGXJVxY2CT/view?usp=drivesdk
Click to expand...
Click to collapse
cts profile false

42o247 said:
this is a link to the ob1 patched boot img i made with the latest magisk canary. it worked for me. if you cant extract the boot.img maybe try this
https://drive.google.com/file/d/19vl9wt5HAYFRuy5mGJlsg2cGXJVxY2CT/view?usp=drivesdk
Click to expand...
Click to collapse
Hi, 8 or 8pro?
Thanks

Would someone please share global OOS11 stable patched_boot.img?

Everytime I have to extract a payload.bin it never works when I need it to... Would someone please share their patched.boot.img for the global stable OOS11?
Thank a TON!!

Here is the patched Magisk 21.0 boot image for US phones (international). I didn't name it anything fancy, just trying to get it uploaded for people.
Remember to flash in both slots in fastboot.
Couldn't post the image here since it's too big. Hopefully my drive link works.
https://drive.google.com/file/d/1IH_lWwTHfapcoltXKldR18Qlt_Zf50t9/view?usp=sharing

open beta 3 patched boot.img in2025
How about a patched boot.img for open beta 3 for in2025? finally got open beta 2 rooted and updated to 3 , tried installing magisk direct and to inactive slot which failed every time. Kinda disappointed by the lack of support for this phone.

If you can get a hold of a full rom for beta 3, you should be able to get a copy of the stock boot.img using Payload Dumper. You can patch it using Magisk Manager w/o root and try booting with it first (before flashing it directly).
If the latest Magisk Manager from the Stable branch doesn't detect root properly (shows N/A), I'd recommend trying the Beta Branch.
Once you confirm you have root detected and working properly, you can reboot back into Fastboot and flash the boot.img you used.