After installing Magisk succesfully,I try to revert back to stock boot.img used fastboot flash.
Then My phone stuck in fastbootmode,no matter which methode used to reboot.
Only solution is flash Magisk patched boot.img,then everything goes ok.
My question is how can I revert back to stock boot.img to get ota update?
use DM-VERITY & FORCEENCRYPT DISABLER
Related
Hi,
Sprint Note 5 here. Basically I'm just trying to get my phone to be unrooted to pass SafetyNet (Android Pay, Pokemon Go, and others) but have some system modications (adaway and removed boot sounds mainly).
What I did do is flash stock odin firmware, then twrp, supersu, and make my changes. Then if I just unroot with supersu it still fails SafetyNet. If I unroot and tell SuperSU to restore boot.img then I get a bootloop. Probably due to TWRP still being there and not stock Recovery? So I thought maybe from there I can just flash boot and recovery via odin but that didn't seem to work either. Is it possible to take the stock firmware and flash whatever I need except system? Or not possible to alter system and go back to stock boot/recovery?
Edit: I took stock firmware, extracted it, removed system.img, and repacked it up (sboot.bin, modem.bin, recovery.img, cm.bin, boot.img, cache.img) and flashed it . It works but then brings me to some "system update" screen and then stock recovery with a verity failed error. Reboot to device just bootloops. Maybe I need to just remove more than just system?
I have a problem with SuperSU and magisk. I flash in twrp the root zip and then magisk, after that when I want to update it says this;
! Boot img patched by other programs
! please restore stock boot img
Click to expand...
Click to collapse
I don't have any custom rom, i'm actually oos 5.0.3. I first try to root but dm-verity was triggered and then followed all the steps to disable it.
Any solutions?
Nube420 said:
I have a problem with SuperSU and magisk. I flash in twrp the root zip and then magisk, after that when I want to update it says this;
Click to expand...
Click to collapse
Magisk is a root zip. It sounds like you are flashing SuperSU and Magisk. You can only use one or the other, not both!
Reflash stock ROM (or at least stock boot.img). Then flash Magisk. That's it.
Getting the error message that boot.img is modified is normal and expected in your case. SuperSU patched the boot image. Now Magisk is looking for the stock image to patch, and finding a patched one.
I have a pending OTA that I'm postponing. I'm unblocked and I have Magisk and TWRP; is it safe to install the OTA or before/after OTA installation I have to do something else ?
no it is not safe, it will brick your device, the only way you can install the OTA is by removing magisk, reinstalling the stock recovery (and make sure it boots when booting to recovery instead of TWRP) then apply the OTA and if it was relocked you need to unlock again and reinstall TWRP and magisk.
it is safe, magisk will be removed, bevause a new boot image will be flashed when updating, just make sure to flash stock emui8 recovery in recovery_ramdisk partition
which version of magisk works on this rom without stuck to twrp again?
i've tried 16.4,16.7,18.0,18.1 all of them doesnt work and kept sending back to twrp after i flashed it...
i need root access to backup and restore imei...
djpsycho666 said:
which version of magisk works on this rom without stuck to twrp again?
i've tried 16.4,16.7,18.0,18.1 all of them doesnt work and kept sending back to twrp after i flashed it...
i need root access to backup and restore imei...
Click to expand...
Click to collapse
All of them work, your issue is encrypted data.
So remove it, then you can install Magisk 18.1 which has built DM-Verity, ForceEncrypt
Other than formatting your data,
You can first try flashing SuperSu >>> once you have established that you have working root via SuperSu >>> remove it by using the SuperSu removal file.
Next, reflash the boot.img that you will extract form the Rom's zip file ( simply unpack the file and grab it. )
Flash boot.img to boot, then flash Magisk 18.1 > Success!
okay so ive successfully rooted my phone,next step is enter diag mode,ive done that either through adb cmd,but problem comes when i hit restore button on qfil,diag connection became unstable,disconnected and then connected again on qpst port detector...but it remains connected on device manager...any idea what caused it?
My model is sm-a305g. Whenever i try to flash magisk it ends up in bootloop. And i don´t know what am i doing wrong. I also tried to root via odin, patching de boot.img and flashing it with odin, but odin stops and never flash the img. please help.
hello, i think the problem is, bacuse you do not flash disable dm verity forceencrypt