Since a lot of people request it, here is the stock Kernel from the Oxygen 4.7.2 ROM
You can flash it with TWRP as boot
edit : no modules are included, this is just the boot image. If you are unsure if your custom kernel changed some modules, better reflash the full Oxygen 4.7.2. zip !!
Oxygen 4.7.2. boot Image
Thanks. Helpful.
Looks like 4.7.2 modules are missing withing flashable zip, it is important because if somebody flash a custom kernel with their own modules, they won't be restored as default (resulting infinite boot/bootloop). Either you have to precise to flash back stock firmware full zip (which already contains stock kernel), or you have to adapt the script and find the right modules to be included :good:
(just an advice) :highfive:
Hello, maybe someone have the stock-kernel for 4.7.6 too?
Thanks in advance
Related
Does anyone have the link to the full ROM that includes this update please? I'm on TWRP and so cannot flash OTA (I also don't have access to a computer at the moment to flash stock recovery)
Thanks,
You can also reflash full 2.0.1 rom then immediately flash the 8MB OTA file. This works.
Then if you use Xposed, boot, go to recovery again and you can reflash Xposed (then clean dalvik/cache again is recommended I suppose).
Everything OK following these steps for me (stable official Xposed for LL 5.1 realeased today ).
http://forum.xda-developers.com/showpost.php?p=62618113&postcount=25
Here's a stock ROM thread over on the OP forums, seems to be the one to keep an eye on
https://forums.oneplus.net/threads/oneplus-2-stock-rom-collection-updated-01-09.347627/
I flashed magMa ux 8.5 rom for my n900t and i saw the Magisk systemless root and i got intrested! So i installed Magisk v12 with SuperSU but i found there was conflict with it so i wanted Magisk v12 with MagiskSU!
I tried dirty flashing the Magisk v12 + MagiskSU over the Magisk V12 + SuperSU! Which caused (im guessing here) caused my boot.img to get corrupted or damaged because it installs into ramdisk!
I tried a nandroid back to my old rom which, worked, wiped in twrp to reflash the rom, which also worked, but installing the magisk to the ramdisk and what it does ends up failing!
I can still boot into my system with root but it causes some conflicts with apps, such as snapchat as it thinks i have magisk still but i only have supersu! And i cannot full unroot from SuperSU app because, i think the boot.img is corrupted!
Would flashing a stock boot.img fix my problems, then reflashing rom again? Or would i have to reflash the whole stock samsung rom and things?
Im on Note 3 N900T! If reflashing the boot.img would work could someone provide a link to download the N900T!!! boot.img?
Thanks
What you call boot.img is the kernel.
Stock kernel won't work with a MM port like magma.
I advise you to do a full wipe from twrp then flash magma.
Before that, refer to the rom's thread for extensive informations about Magisk and systemless root.
I've accidentally deleted last backup, and now left with magisk modified img. There are some problems with magisk 13.3 [unable to install any module, solutions are welcome.] so need to clean my phone and install it again.
Someone please upload stock boot.img
On build NPN25.137-67
I'd like to see the same. I think I might have backed up a Magisk modified boot image but I'm not 100% certain. I'm on the -83 release for US retail. If someone could provide the boot.img (or a twrp backup of it) of the 100% stock version on NPN25.137-83 that would be fantastic.
Hello this is my post here on this forum.
I´ve recently decrypted my OP5 running oreo open beta 4 with dm-verity.
My question is: If i flash a custom kernel do i have to reflash the no dm verity file again? Or only if i update the rom?
Thanks in advance and Merry Christmas everyone!
If you flash a custom kernel that enforces encryption, then you would have to flash the no-dm-verity zip after the kernel flash as well. If, however, the kernel doesn't modify the encryption status, then you don't need to flash that zip after flashing your custom kernel.
If you aren't sure if the kernel you're wanting to flash enforces encryption or not, search or ask in the kernel's thread. Or you can always flash the no-dm-verity zip post the kernel flash, in case you aren't sure and don't want to take any risk. Even if the kernel doesn't force encryption and you flash the no-dm-verity zip, there won't be any issues, so don't worry about that.
Hey, i need help please.
I recenty flashed ( successfully ) RR Rom, but before that i used a patched_boot.img for root, it also worked fine. However, i installed faulty Magisk modules and now i can't boot, i tried magisk_uninstlaler but it didn't work and i'm assuming it's because of the patch_boot. Can someone please help ? is there another way i can reboot/uninstall magisk or if someone can just link me the stock boot.img
Thanks.
EDIT: I have successfully removed the faulty modules using methods in TWRP and rebooted my phone - but anyway, do you think i need to reflash stock boot.img ?
You can find stock ROM files (including boot.img) here:
The latest one: http://en.miui.com/download-333.html
Current + previous versions: https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/