This media is not supported in your browser
VIEW IN TELEGRAM
No deleted account found from
๐ฌ Send /lang to change language of the bot
88 scanned users from this group ๐ซ๐ป๐ฌ Send /lang to change language of the bot
This media is not supported in your browser
VIEW IN TELEGRAM
Forwarded from fatalcoder524
Hi Guys,
โ โ โ โ โ โ โ โ โ โ โ โ
Due to some changes in boot.img structure, present magiskboot had some issues when unpacking and repacking boot.img for Kernels 6.6 and above. Some of you might have noticed that first flash using Kernel Flasher worked fine but subsequent flashes show the
This is also the reason why KPN either failed to patch or you get a non bootable phone. It was noticed in a timely manner and the issue was fixed in CI version of magiskboot.
We have replaced the magiskboot in our AK3 zips and we request everyone to follow the below procedure for next update. Might not be needed for all but its better to have a clean working paritions all the time.
If you don't have Custom Recovery:
If you have Custom Recovery:
โ โ โ โ โ โ โ โ โ โ โ โ
Due to some changes in boot.img structure, present magiskboot had some issues when unpacking and repacking boot.img for Kernels 6.6 and above. Some of you might have noticed that first flash using Kernel Flasher worked fine but subsequent flashes show the
Boot.img is bigger than partition size error
This is also the reason why KPN either failed to patch or you get a non bootable phone. It was noticed in a timely manner and the issue was fixed in CI version of magiskboot.
We have replaced the magiskboot in our AK3 zips and we request everyone to follow the below procedure for next update. Might not be needed for all but its better to have a clean working paritions all the time.
If you don't have Custom Recovery:
1. Patch stock init_boot / vendor_boot using KSUN / Wild_KSU using Select File option.
2. Copy patched img to PC.
3. Flash stock boot.img using fastboot.
4. Flash patched init_boot.img / vendor_boot.img using fastboot.
5. Reboot.
6. Flash AK3 zip using Kernel Flasher / KSUN / Wild_KSU.
7. Dont reboot.
8. Flash stock init_boot.img / vendor_boot.img using Kernel Flasher.
9. Reboot
If you have Custom Recovery:
1. Flash stock boot.img using recovery.
2. Don't Reboot.
3. Flash AK3 zip using recovery.
4. Reboot
This is 100% not required for all, but i recomend everyone to do it so that you wont face any issue in future. This is not required for 6.1 and bellow.
This media is not supported in your browser
VIEW IN TELEGRAM
This media is not supported in your browser
VIEW IN TELEGRAM
This media is not supported in your browser
VIEW IN TELEGRAM
This media is not supported in your browser
VIEW IN TELEGRAM
This media is not supported in your browser
VIEW IN TELEGRAM
A Glimpse Into DexProtector
by Romain Thomas
https://www.romainthomas.fr/post/26-01-dexprotector
https://github.com/romainthomas/dexprotector
by Romain Thomas
https://www.romainthomas.fr/post/26-01-dexprotector
https://github.com/romainthomas/dexprotector
Romain Thomas
A Glimpse Into DexProtector | Romain Thomas
This blog post provides a high-level overview of DexProtector's security features and their limitations
This media is not supported in your browser
VIEW IN TELEGRAM
This media is not supported in your browser
VIEW IN TELEGRAM