Related
THESE ARE UNSUPPORTED. YOU ARE RESPONSIBLE TO ANYTHING THAT HAPPENS AS A RESULT OF YOUR ACTIONS.
WARNING: THESE BOOT IMAGES HAVE BEEN CAUSING BOOT LOOPS FOR SOME USERS. THEY INCLUDE PEOPLE WHO ARE USING NON-STOCK FIRMWARE, FIRMWARE FROM ANOTHER DEVICE (such as using "c" firmware on a "i" device) AND THE ONE PERSON WHO'S TRIED THE "8" BOOT IMAGE. INSTALL AT YOUR OWN RISK AND BE SURE YOU HAVE A METHOD TO RECOVER ANOTHER BOOT IMAGE.
ALL QUESTIONS/COMMENTS/REQUESTS SHOULD GO HERE: http://forum.xda-developers.com/note5/help/qa-stock-kernels-selinux-enforcing-t3222324
I've taken the stock boot image (kernel) from a few different devices and repacked them in order to make them safe for use with SuperSU.
These kernels are Samsung stock SEAndroid enforcing. That means higher security (but also the chance that some *root* programs fail.) The ramdisk is modified to allow SuperSU to work, and to prevent boot loops when you're using a modified device. The ramdisk is also modified to work around the samsung kernel bug that would prevent some devices from going into deep sleep.
Other than these changes, they are completely, 100% stock. They will NOT auto-root your device (though it is safe to install SuperSU after installing this kernel), they won't grow new hair on your head, and most certainly won't find you a spouse.
For details on the changes, please read this thread:
http://forum.xda-developers.com/note5/orig-development/kernel-discussion-root-recompiling-t3219990
As these are STOCK kernels (not recompiled), all your hardware should continue to work properly. From my own tests, I have no reboot issues, no NFC issues, etc.
Each file attached here has a file name that reflect the firmware I pulled it from. Read it carefully. Don't use a kernel that shouldn't be used on your device!
Files ending with ".tar.zip" can be unzip'd (they contain only a .tar file) and applied via ODIN (PDA/AP section.) The files must be unzipped before used in ODIN. These ".tar.zip" files can NOT be flashed with TWRP or CWM.
Files ending with just ".zip" are meant to be flashed via TWRP or CWM. You can also extract the .img files from the .tar.zip files mentioned above and flash those directly with TWRP (using the proper options.)
Yes, this will trip KNOX if it's not already tripped...
Enjoy..
Gary
N9208ZTU1AOH4
OP updated to include a big red boot loop warning...
Added N920T (T-Mobile) to the top post.
Added modified boot images for the T-Mobile "M" leak N920TUVU2DOK5. The origin of the boot image is @danon.brown. Thanks to @gharris040604 for testing this...
Added N920LKLU2AOJ6 to the first post.
added N920GDDU2AOJ5 to the first post.
I have just bought oneplus 7 t pro and want to root it. How do I extract boot.img from the firmware so I can patch it using magisk ? Any help in rooting this device would be greatly appreciated. Thanks
you should wait the stock rom or you can try to boot the oneplus 7t twrp and backup the boot.img
Thanks
Will try and report back
boots into the twrp 7t recovery but boot.img is not being backed up . It fails to mount any partition . adb pull command not working .
I have boot image
are you able to patch it with magisk ?
ask77 said:
are you able to patch it with magisk ?
Click to expand...
Click to collapse
unfortunately not
I have now extracted boot.img and patched it with magisk but the output image is of 36.44 MB while the original image is of 96 MB so I am a bit wary in flashing this image as I do not want to go into a boot loop also I have a boot.img and a recovery.img both are identical in size and are identified by magisk as stock boot.img . i am uploading the install log . I will research a bit more before flashing the patched boot img to achieve root
ask77 said:
I have now extracted boot.img and patched it with magisk but the output image is of 36.44 MB while the original image is of 96 MB so I am a bit wary in flashing this image as I do not want to go into a boot loop also I have a boot.img and a recovery.img both are identical in size and are identified by magisk as stock boot.img . i am uploading the install log . I will research a bit more before flashing the patched boot img to achieve root
Click to expand...
Click to collapse
try just doing fastboot boot patchedbootimghere.img
if it bootloops you can just restart the phone and it will be back to normal since its not flashed
HolyChickenGuy said:
try just doing fastboot boot patchedbootimghere.img
if it bootloops you can just restart the phone and it will be back to normal since its not flashed
Click to expand...
Click to collapse
Thanks will do that.
sorry no go . It either goes to crashdump or is stuck with the fastboot screen
ask77 said:
sorry no go . It either goes to crashdump or is stuck with the fastboot screen
Click to expand...
Click to collapse
I'm having the same results
Sent from my OnePlus 7T Pro
same there no luck. just the crash dump screen
digitalashley said:
same there no luck. just the crash dump screen
Click to expand...
Click to collapse
Make sure to check Preserve AVB 2.0/dm-verify in advance settings before patching boot.img, then use command
fastboot boot imagenamehere.img, after boot, perform direct install to preserve root.
when manually updating is full OTA or factory image better or safer?
what are the pros and cons of each?
if you are rooted will it make a difference?
custom kernel issues people should know about before updating?
If you're rooted, download the factory image, extract the boot.img from the zip, patch it in magisk and move the patched image to your PC.
Sideload the OTS, reboot to bootloader, flash the patched boot.img and pretty much that's it.
This is how i do it
Basically what Svid said. However, you can also use Payload Dumper to extract the boot.img from the payload.bin in the OTA.zip - saves you the download of the full factory image. Nowadays mostly a preference kinda thing since downloading speed is rarely an issue.
Custom kernels will get wiped upon updating anyway, so make sure the kernel is updated for 12.1/L before flashing again. I know bluspark is not yet compatible, so you have to wait for that one. Also, the Pixel Addon Features Magisk module causes a bootloop for now.
I have been trying to build a custom aosp based ROM for pixel 4a, I have made changes to few xml files that goes into vendor/etc/ folder. I built a script to extract vendor blobs from the official vendor image provided by google and also generated build instructions for corresponding files.
I'm able to build the vendor image successfully. All the vendor files are present in the custom built vendor img, when I checked.
After flashing the images, the phone gets stuck in google logo.
I have made sure that bootloader is unlocked., osp version and vendor build version match.
1. Is there a way to build vendor image? Is my approach correct?
2. How can boot loop be debugged? -- ADB is not available at this point of time in boot process.. I'm also not able to boot into recovery, I keep getting bootloader screen.
Any help, links, refs, guides would be helpful
If you are rooting after or during the build process both boot.img and vendor_boot.img files need to be patched. If you are at bootloader(fastboot) you can fastboot flash vendor.img etc
toolhas4degrees said:
If you are rooting after or during the build process both boot.img and vendor_boot.img files need to be patched. If you are at bootloader(fastboot) you can fastboot flash vendor.img etc
Click to expand...
Click to collapse
I'm able to flash the vendor image. I don't want to root the phone. When I use the official vendor image, the phone boots but not when I use vendor image that I built. Is there a way to build vendor image? or How can I debug boot loop?
toolhas4degrees said:
If you are rooting after or during the build process both boot.img and vendor_boot.img files need to be patched. If you are at bootloader(fastboot) you can fastboot flash vendor.img etc
Click to expand...
Click to collapse
Yes, he can use magisk manager to patch the image then flash them in fastboot mode using adb like you said
poppopret_ said:
I have been trying to build a custom aosp based ROM for pixel 4a, I have made changes to few xml files that goes into vendor/etc/ folder. I built a script to extract vendor blobs from the official vendor image provided by google and also generated build instructions for corresponding files.
I'm able to build the vendor image successfully. All the vendor files are present in the custom built vendor img, when I checked.
After flashing the images, the phone gets stuck in google logo.
I have made sure that bootloader is unlocked., osp version and vendor build version match.
1. Is there a way to build vendor image? Is my approach correct?
2. How can boot loop be debugged? -- ADB is not available at this point of time in boot process.. I'm also not able to boot into recovery, I keep getting bootloader screen.
Any help, links, refs, guides would be helpful
Click to expand...
Click to collapse
Did you already check the tutorials or how-to's available on XDA e.g. the tutorials of @AlaskaLinuxUser like
[Guide][Video Tutorial] How to build Custom ROMs and Kernels![10,P,O,N,M,L]
Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it was helpful to you in your Android career! Praise...
forum.xda-developers.com
or
[Guide][Video Tutorial] Intermediate to Advanced Custom Rom and Kernel Building
Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it is helpful to you in your Android career! Praise God...
forum.xda-developers.com
The XDA University might also be of good help:
XDA-University
Tutorials, How-To Guides and More. Learn about mobile phone development, hacking, flashing, rooting and many other topics!
forum.xda-developers.com
Just search a bit and you'll find much more.
There is a new OTA so please check that your still on may or july patch before using these:
***First and foremost I am NOT responsible for anything you do with the information posted, nor do I know how to help you unbrick your device, this is for testing purposes ONLY. If you cannot source the stock boot image for your current build/security patch wait for someone to post it and patch it yourself.****
It's always best to pull your own stock image and patch it with magisk YOURSELF. This is just to save some time for people who know exactly what their doing. If you have any doubt whatsoever DO NOT FLASH.
***Warning this MAY BRICK YOUR DEVICE IF YOUR NOT ON THE RIGHT SECURITY PATCH ***""
You will lose radios if you flash this to the wrong device, I have successfully recovered by flashing the correct boot image and have helped someone else recover with mismatching images by flashing the correct modems. I do not have the time to find the modems and troubleshoot your device so be careful please.
Flashing boot images from mismatching security patches on this device leads to no-boot and/or loss of radio functionality(cellular,wifi,Bluetooth).
The May patched boot image does NOT work for devices with the the latest security patch. Confirm that you are on the May 05, 2022 security patch BEFORE flashing MAY image. ( NOT JUNE OR JULY)
Works on build number GN2200_11_A.05
Only tested on TMOBILE variant and probably won't work for anything else(Metro apps are installed but disabled on the TMobile variant so it's possible that it MIGHT work for those devices but don't take that as any kind of reassurance that it would work***
The same boot image should work for both A and B slot but dont do anything unless you have a backup to recover from.
If you have read all the above and are 100% sure of what your doing, Flash the boot image, reboot and install magisk app as usual.
Magisk patched May boot image(should work for A/B):
magisk_boot_b.img
drive.google.com
[/URL]
here are the July (GN2200_11_A.06)Images:
Stock:
https://drive.google.com/file/d/1eALH0BxkhGPEBVSMLXfSOwp0xtySXLe4/view?usp=sharing
Magisk Patched July Image:
n20julybootmagisk.img
drive.google.com
**Edit**: According to JWhitley the images DO work for Metro by T-Mobile devices"
updated with july boot images
Darn, probably should've rooted first before updating to August patch.
PsYk0n4uT said:
updated with july boot images
Click to expand...
Click to collapse
You, kind stranger, are amazing! Thanks!
Rogo00 said:
You, kind stranger, are amazing! Thanks!
Click to expand...
Click to collapse
Flash vbmeta with
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you have issues and that should at least get you going if security checks prevent booting.
PsYk0n4uT said:
Flash vbmeta with
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you have issues and that should at least get you going if security checks prevent booting.
Click to expand...
Click to collapse
Where is the vbmeta image?
PsYk0n4uT said:
There is a new OTA so please check that your still on may or july patch before using these:
***First and foremost I am NOT responsible for anything you do with the information posted, nor do I know how to help you unbrick your device, this is for testing purposes ONLY. If you cannot source the stock boot image for your current build/security patch wait for someone to post it and patch it yourself.****
It's always best to pull your own stock image and patch it with magisk YOURSELF. This is just to save some time for people who know exactly what their doing. If you have any doubt whatsoever DO NOT FLASH.
***Warning this MAY BRICK YOUR DEVICE IF YOUR NOT ON THE RIGHT SECURITY PATCH ***""
You will lose radios if you flash this to the wrong device, I have successfully recovered by flashing the correct boot image and have helped someone else recover with mismatching images by flashing the correct modems. I do not have the time to find the modems and troubleshoot your device so be careful please.
Flashing boot images from mismatching security patches on this device leads to no-boot and/or loss of radio functionality(cellular,wifi,Bluetooth).
The May patched boot image does NOT work for devices with the the latest security patch. Confirm that you are on the May 05, 2022 security patch BEFORE flashing MAY image. ( NOT JUNE OR JULY)
Works on build number GN2200_11_A.05
Only tested on TMOBILE variant and probably won't work for anything else(Metro apps are installed but disabled on the TMobile variant so it's possible that it MIGHT work for those devices but don't take that as any kind of reassurance that it would work***
The same boot image should work for both A and B slot but dont do anything unless you have a backup to recover from.
If you have read all the above and are 100% sure of what your doing, Flash the boot image, reboot and install magisk app as usual.
Magisk patched May boot image(should work for A/B):
magisk_boot_b.img
drive.google.com
[/URL]
here are the July (GN2200_11_A.06)Images:
Stock:
https://drive.google.com/file/d/1eALH0BxkhGPEBVSMLXfSOwp0xtySXLe4/view?usp=sharing
Magisk Patched July Image:
n20julybootmagisk.img
drive.google.com
Click to expand...
Click to collapse
posting as a confirmation that the . img files provided here do play nice on the Metro by T-Mobile phone versions with currently
JWhitley said:
posting as a confirmation that the . img files provided here do play nice on the Metro by T-Mobile phone versions with currently
Click to expand...
Click to collapse
Thanks I was thinking they might since it's basically the same carrier but I didn't want to encourage anything untested
iKlover said:
Where is the vbmeta image?
Click to expand...
Click to collapse
Please see the response in the other thread
hawk1500 said:
Darn, probably should've rooted first before updating to August patch.
Click to expand...
Click to collapse
You can use DSU sideloader and boot a prerooted GSI, pull your stock images from whatever patch your on, easy way is to just use Partitions Backup and Restore app from playstore if you don't wanna use command line tools much. Install magisk and patch the extracted boot.img. save all your backups to your PC and flash the patched image in fastboot
PsYk0n4uT said:
You can use DSU sideloader and boot a prerooted GSI, pull your stock images from whatever patch your on, easy way is to just use Partitions Backup and Restore app from playstore if you don't wanna use command line tools much. Install magisk and patch the extracted boot.img. save all your backups to your PC and flash the patched image in fastboot
Click to expand...
Click to collapse
What "Partitions Backup and Restore app" are you talking about? This one? https://play.google.com/store/search?q=partitions+backup+and+restore&c=apps
famewolf said:
What "Partitions Backup and Restore app" are you talking about? This one? https://play.google.com/store/search?q=partitions+backup+and+restore&c=apps
Click to expand...
Click to collapse
yep