Database Develop

Will SuperSU still patch boot.img if i force installation in the system partition?

My OnePlus 3 is running Oxygen OS 4.0.1/Android 7.0 (stock ROM and kernel/boot.img) with the latest TWRP. I want to root my device with SuperSU in system mode (I'll be modifying the system partition so systemless doesn't matter for me). But for root to work, the boot.img must be patched, right? So will flashing SuperSU take care of that automatically if I flash it in system mode? Thanks.

How to use Magisk??? (add lost txt)

Hi to all
I have rooted OP3T and every time when I install new update, BETA small or full version zip file, I need again to install stock.zip from boatloader , then again, install TWRP and Super Su.
I hear that with Magisk I can easy install any update without lost TWRP and Root. I have flash Magisk and install from Google Store Magisk Manager.
So my question is how to install new update with Magisk and dont lost TWRP and Root?
Please tell me step by step
thx a lot for your answers

Magisk doesn't touch the recovery. And you'll still have to flash the Magisk zip since the boot image is updated whenever you update your system (Magisk modifies the boot image).
What does stay after an update (as long as you don't wipe /data) is any Magisk modules that you have installed. If you have a bunch of modules that change build.prop values, debloat system apps, change screen density, replaces system UI sounds, etc, you won't have to do those changes again after an update. They are found in the Magisk image in /data and will be loaded by Magisk at boot.
Even if you've wiped /data, it's just a matter of flashing the Magisk and module zips in TWRP after updating your system. No tedious manual editing of build.prop or deleting apps, etc. It literally takes seconds...
If you have issues with loosing TWRP after an update, you can easily fix that, right after updating. Just keep a copy of the recovery image on your device and flash it in TWRP.

Magisk Install Error - insufficient Partition Size

Hello. I'm attempting to install magisk on a Samsung Galaxy Tab 4 10.1 (SM-T530NU). Base android has been replaced with crDroid (crDroid-7.1.1-20170312-v2.3).
When I go to flash the magisk .zip via TWRP the log reads:
...
-Flashing new boot image
! Insufficient partition size
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/download/Magisk-v17.1(17100)'
Updating partition details...
...done.
I have tried the following:
made sure to have the latest zip from Magisk Manager
removed previous partial installs of Magisk by using the flashable remover
unrooted supersu (which I'm also no longer able to flash now, systemless or not, to reestablish root and try other methods--it sticks on the boot screen)
reflashed base crDroid
pulling Magisk 17.3 separately from Manager and using that to flash
I haven't found any resources on whether the 'insufficient partition size' problem is with TWRP or the Magisk flashing process so I haven't found anything to try specifically to fix that.
The last thing I have to try is making the flashable boot image and fastbooting it.
Linked here is an image of the TWRP output: imgur . com/a/CATYid4
Thanks

did you manage to fix this

[GUIDE] [OTA] [TWRP] Android Pie - TWRP, Decrypt, Magisk and OTA

Post my other thread for Android Oreo with OTA with TWRP ( https://forum.xda-developers.com/as...to/rom-update-stock-firmware-keeping-t3808269 ), wanted to continue the same but found pretty good solutions to have the process more quick and seamless.
So to have rooted Pie with TWRP and to flash OTA please follow below procedure.
Files needed,
Latest Pie full OTA file from Asus website.
Latest TWRP from here.
Decrypt File for Pie (recommedned).
Magisk (optional).
Debloat File (optional).
Steps to be followed to update to latest OTA,
Flash the latest TWRP and boot into it.
Flash downloaded full OTA package (point-1 above) from Asus website then reboot to recovery from TWRP menu.
Mount /system & /vendor partitions and flash decrypt-pie.zip file (point-2 above).
Reboot to recovery again, mount /system & /vendor and flash Magisk. (point-3 above)
Reboot to recovery and mount /system & /vendor and flash Debloat zip (point-4).
Finally reboot to system and HIT THANKS if it worked for you. This helps me and also gives confidence/credibility to others to try.
Post issues if any below.

It's not working bro

This ROM package works very well but cam2api is getting disabled. Did the build.prop method after root and also the fastboot method. It works for a few days than gcam stops.

As pointed out in the guide, official Pie zip is to be DL and flashed through TWRP. However, since it is official zip, will it flash successfully through TWRP recovery instead of Stock Recovery ?
Also, can anybody confirm if the phone is now system-as-root after upgrade to Pie ? (I am on v340 Oreo and system-as-root is not mandatory for devices upgrading to Pie).
Edit: Ok, so took the plunge and successfully updated from stock rooted v340 (Oreo) to v56 (Pie). Did everything as per the guide except for 2 steps:
1) Used TWRP flashable ROM instead of stock ROM zip.
2) Did not reboot to TWRP recovery after flashing updated recovery. Instead, continued through updated recovery, flashed ROM and then rebooted to recovery.

Bugs in the update v056 (Pie):
1) Sometimes "Recent Apps" list goes blank / stops working. Workaround: Reboot to safe mode and check "Recent Apps" (it usually is working), reboot to normal mode and everything works fine again.
2) Cam2Api breaks, even if you enable <persist.camera.HAL3.enabled=1> it will not work.
Add these lines to build.prop, save and reboot:
persist.camera.HAL3.enabled=1
persist.vendor.camera.HAL3.enabled=1
persist.camera.stats.test=5
persist.vendor.camera.test=5
persist.camera.eis.enable=1
(DO NOT FORGET to backup your original build.prop !)

[GUIDE] How to Restore Stock Kernel from ROM

I posted the original version of this guide in the Pixel Experience forum because I needed a way to recover the stock Oniichan kernel from the PE ROM after I had flashed other kernels over it, without first backing up my boot partition. This is because the latest Oniichan kernel isn’t posted online, unlike Genom, Predator, etc. This solution uses OrangeFox and can be applied to any ROM with minor modification.
The ROM file that you flashed to your phone should include a boot image file called boot.img which contains the kernel. So, we simply extract boot.img from the ROM and flash this image to the Android boot partition. This will replace the new kernel with the stock kernel from our ROM, after which we re-flash Magisk if we need root (no need to re-flash modules), and we should be back to stock. Here are the steps to restore your stock kernel:
1. Retrieve a copy of your current ROM zip file
2. Expand zip file and extract boot.img
3. Save boot.img to phone storage (e.g., SD card)
4. Reboot phone into OrangeFox recovery
5. Do OrangeFox backup of boot partition (e.g., to SD card)
6. Select the boot.img file and attempt to flash it normally
7. From choice of target partitions select “Boot”
8. Swipe right to install image as instructed
9. Flash should complete in 10-15 seconds
10. Re-flash Magisk to restore root if needed (no need to re-flash modules)
11. Reboot phone to system
12. In settings check kernel version to verify desired kernel was restored
FYI, you can use this method to extract the kernel from any ROM and flash it to your phone, but you should first verify that the new kernel is compatible with your current ROM before you flash it. Please let me know if you have any questions. Good luck!

thx
Thanks

mirdem said:
Thanks
Click to expand...
Click to collapse
You're welcome.

I just flashed Pixel and NGK (both latest) today. By flashing the boot.img does it remove all of my data? Or It'll flash only for the kernel itself?