Database Develop

Magisk without TWRP, with full device encryption?

I have a Samsung Galaxy S7 edge, international version, Android 6, unlocked bootloader, rooted with CF-auto-root, now has SuperSU installed, pure stock rom.
And I am wondering whether it will be possible to install Magisk (even if I have to uninstall SuperSU) without TWRP or any other custom recovery?
Will it also be possible to have full disk encryption (to be honest I don’t know whether my device is currently encrypted - is there a way to check this)?

orifori said:
I have a Samsung Galaxy S7 edge, international version, Android 6, unlocked bootloader, rooted with CF-auto-root, now has SuperSU installed, pure stock rom.
And I am wondering whether it will be possible to install Magisk (even if I have to uninstall SuperSU) without TWRP or any other custom recovery?
Will it also be possible to have full disk encryption (to be honest I don’t know whether my device is currently encrypted - is there a way to check this)?
Click to expand...
Click to collapse
Yes it is possible... Check the magisk release thread for the method applicable for you... About encryption, it works just fine...
Edit: here https://forum.xda-developers.com/showthread.php?t=3473445
Sent from my MI 5 using Tapatalk

Thank you! I need some help regarding the Installation Instructions.
The stock rom I have (which is to be patched by Magisk Manager) is a ZIP file with 5 .tar.md5 files in it...
1 - Where should I copy it - internal phone memory?
2 - Should I copy the ZIP file or the 5 files in it?
3 - Magisk Manager asks for .RAR or .IMG file while I have a .ZIP - should I simply rename the .ZIP to .RAR or...?
4 - Installing CSC_... would do a wipe while HOME_CSC_... would not - and I definitely do not want a wipe - so how to proceed?
5 - If I want full device encryption I just tick Preserve force encryption option (I don't know whether the phone is now encrypted)?

orifori said:
Thank you! I need some help regarding the Installation Instructions.
The stock rom I have (which is to be patched by Magisk Manager) is a ZIP file with 5 .tar.md5 files in it...
1 - Where should I copy it - internal phone memory?
2 - Should I copy the ZIP file or the 5 files in it?
3 - Magisk Manager asks for .RAR or .IMG file while I have a .ZIP - should I simply rename the .ZIP to .RAR or...?
4 - Installing CSC_... would do a wipe while HOME_CSC_... would not - and I definitely do not want a wipe - so how to proceed?
5 - If I want full device encryption I just tick Preserve force encryption option (I don't know whether the phone is now encrypted)?
Click to expand...
Click to collapse
You need to patch and flash the boot image only. That'll be inside the ROM zip. Don't forget to change the output format in the Manager settings to .img.tar.
It usually says under Android settings -> Security if your device is encrypted or not. But I've no idea if Samsung do that. I don't do Samsung.
This has been discussed a few times in the Magisk forums already, so if you search you'll be able to find more info on it. Always do your homework before flashing...
Examples of threads to search and/or read trough:
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
https://forum.xda-developers.com/apps/magisk/magisk-discussion-thread-t3467229
https://forum.xda-developers.com/apps/magisk/flashing-patched-boot-img-odin-t3670503

Worked like a charm, thank you! Extracted AP_... file from the zip archive, them extracted boot.img file from AP_... file and copied it onto the SD card of the phone, then Magisk modified it, I copied it to my laptop and flashed it in Odin (AP field).

Everything works fine, except OTA updates - I try to download updates manually (About device -> Download updates manually) but I get a message "The operating system on your device has been modified in an unauthorized way."
So are OTA updates possible 1. without TWRP and 2. with preserved encryption - like in my case - and how is that possible? Maybe Magisk settings?

orifori said:
Everything works fine, except OTA updates - I try to download updates manually (About device -> Download updates manually) but I get a message "The operating system on your device has been modified in an unauthorized way."
So are OTA updates possible 1. without TWRP and 2. with preserved encryption - like in my case - and how is that possible? Maybe Magisk settings?
Click to expand...
Click to collapse
In order to be able to take an ota, you need stock recovery, with unmodified system, and probably stock boot... (Magisk only touched the boot.img, so you just need to restore that)...
Sent from my MI 5 using Tapatalk

orifori said:
Everything works fine, except OTA updates - I try to download updates manually (About device -> Download updates manually) but I get a message "The operating system on your device has been modified in an unauthorized way."
So are OTA updates possible 1. without TWRP and 2. with preserved encryption - like in my case - and how is that possible? Maybe Magisk settings?
Click to expand...
Click to collapse
You can't update with OTA if you've modified /system or the boot image (Magisk). A custom recovery would also cause it to fail, but that's not an issue for you...
Since you've got a Samsung there are probably more checks as well (unlocked bootloader and such).
You might have to flash updates manually... Best place for answers would be your device's forum.

Didgeridoohan said:
You can't update with OTA if you've modified /system or the boot image (Magisk)
Click to expand...
Click to collapse
So there is absolutely no chance for OTA updates in case of installed Magisk? I have a pure stock rom and the only thing modified is the boot.img file (modified by Magisk in order to gain root).

orifori said:
So there is absolutely no chance for OTA updates in case of installed Magisk? I have a pure stock rom and the only thing modified is the boot.img file (modified by Magisk in order to gain root).
Click to expand...
Click to collapse
You could restore the stock boot image to get the OTA and then re-root.
Don't know if Samsung updates care about KNOX (which will be triggered). I don't think they do, but I don't do Samsung so I can't say for sure...

I am trying to root my phone using magisk. I do not have any custom recovery. I was told that I can still root it by patching my stock boot image. But I couldn't find it anywhere. I do have my phone's stock firmware, and if I'm not wrong it Should be inside it, but the problem is that, the firmware file is in .nb0 format. I do not know how to open it and get access to the boot.img, can someone please help me.
My phone is Infocus m535
This is the firmware ?
mediafire.com/file/y2zru5gda08jder/Infocus_M535_G40-026P-0-00WW-A02.zip
???? Please help

Loku_kika said:
I am trying to root my phone using magisk. I do not have any custom recovery. I was told that I can still root it by patching my stock boot image. But I couldn't find it anywhere. I do have my phone's stock firmware, and if I'm not wrong it Should be inside it, but the problem is that, the firmware file is in .nb0 format. I do not know how to open it and get access to the boot.img, can someone please help me.
My phone is Infocus m535
This is the firmware [emoji116]
mediafire.com/file/y2zru5gda08jder/Infocus_M535_G40-026P-0-00WW-A02.zip
[emoji120][emoji120][emoji120][emoji120] Please help
Click to expand...
Click to collapse
Try 7zip...
You have to have an unlocked bootloader and a working fastboot in order to root without custom recovery...
Sent from my MI 5 using Tapatalk

Loku_kika said:
I am trying to root my phone using magisk. I do not have any custom recovery. I was told that I can still root it by patching my stock boot image. But I couldn't find it anywhere. I do have my phone's stock firmware, and if I'm not wrong it Should be inside it, but the problem is that, the firmware file is in .nb0 format. I do not know how to open it and get access to the boot.img, can someone please help me.
My phone is Infocus m535
This is the firmware
mediafire.com/file/y2zru5gda08jder/Infocus_M535_G40-026P-0-00WW-A02.zip
Please help
Click to expand...
Click to collapse
For future references: Samsungs firmware files can be compressed with their LZ4 format and thus needs to be uncompressed again in the case of a boot.img.lz4 file so that you have boot.img file which magisk then can properly use. Otherwise you might get an error sating something like: unable repack boot image, when trying to patch the boot image with Magisk.

guys i have flash magisk patched image without custom recovery and via fastboot but now I am always boot to recovery.. Phone doesnt start at all.

In focus m535 magisk
OK bro I try it

Sorry

Hi, I try do to same thing on my S7 but with a Oreo 8.0 Android version.
Perhaps it's change something.
And each time I reboot after flash a boot.img patched or even patch TWRP, my phone don't boot and ask me to reset it (in French it write reinistialisation in an tactile screen).
If I reload with Odin a BL, AP ect... my phone restart and I didn't lose any data. But it is no root.
Could you help me please ?

Manual update rooted P10?

Hello,
Some weeks ago I have rooted my P10 with magisk (and twrp as recovery). Now I hot update Infos for new fw B371 (C432). Ota update won't work so I downloaded full Ota with huawei firmware finder. After download phone restarts but no update. It boots to recovery. Do I have to install the update files manually or isn't an update possible.
Thanks

painkiller_one said:
Hello,
Some weeks ago I have rooted my P10 with magisk (and twrp as recovery). Now I hot update Infos for new fw B371 (C432). Ota update won't work so I downloaded full Ota with huawei firmware finder. After download phone restarts but no update. It boots to recovery. Do I have to install the update files manually or isn't an update possible.
Thanks
Click to expand...
Click to collapse
Just flash a stock oreo recovery, and you should be fine.

Use my guide. Tutorial #3 is the right one.
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286

Thanks. So root will be undone with this process? After this I can easily install twrp and magisk again without any problems?
Edit: Testet this, but install of officialupdate.zip failed (put the directory in /cust - boot into TWRP, mount cust and tried to install officialupdate.zip). Install from sdcard won´t work too.

Anyone has a solution to fix this. Removed root but it won't work.

Please post the TWRP log after trying to install officialupdate.zip. I need to know, what's failing so I'm able to help you out.

Jannomag said:
Please post the TWRP log after trying to install officialupdate.zip. I need to know, what's failing so I'm able to help you out.
Click to expand...
Click to collapse
Tried the root method (install from /cust directory) but again error. And here is the log from TWRP:
https://pastebin.com/1EL41MV5
Hope it is ok with pastebin link?
Thanx

painkiller_one said:
Tried the root method (install from /cust directory) but again error. And here is the log from TWRP:
https://pastebin.com/1EL41MV5
Hope it is ok with pastebin link?
Thanx
Click to expand...
Click to collapse
Okay, I can't figure it out, the log says error in line 141 in my script. I tried this on my phone and there's no such error.
What this script does is quiet simple - it just flashes a modified EMUI recovery, where the file and online check are disabled. So, you can flash the recovery from the archive manually via fastboot with "fastboot flash recovery_ramdisk PATH\TO\RECOVERY.IMG".
Then restart and do the update via Settings or FF.
After this you need to reroot, so reinstall TWRP and Magisk / SuperSU.

Jannomag said:
Okay, I can't figure it out, the log says error in line 141 in my script. I tried this on my phone and there's no such error.
What this script does is quiet simple - it just flashes a modified EMUI recovery, where the file and online check are disabled. So, you can flash the recovery from the archive manually via fastboot with "fastboot flash recovery_ramdisk PATH\TO\RECOVERY.IMG".
Then restart and do the update via Settings or FF.
After this you need to reroot, so reinstall TWRP and Magisk / SuperSU.
Click to expand...
Click to collapse
Ok thanks for looking. Don´t know why it won´t work. Device was simply rooted with TWRP + Magisk. Ok will try out manual way. Wiht Archive you mean this: https://forum.xda-developers.com/p10/development/recovery-p10-vtr-l09-t3782163 ?

painkiller_one said:
Ok thanks for looking. Don´t know why it won´t work. Device was simply rooted with TWRP + Magisk. Ok will try out manual way. Wiht Archive you mean this: https://forum.xda-developers.com/p10/development/recovery-p10-vtr-l09-t3782163 ?
Click to expand...
Click to collapse
No, my officialupdate rar achive, it contains the zip for TWRP and a recovery IMG file. This is the right one.

OK then you mean the VTR_RECOVERY_OREO-NoCheck.img. I will check this. Thanks

Jannomag said:
No, my officialupdate rar achive, it contains the zip for TWRP and a recovery IMG file. This is the right one.
Click to expand...
Click to collapse
Update worked only via Firmware Finder. But all is fine now. Reinstalled TWRP and magisk (no data loss) and all is working. Thanks for your help.

painkiller_one said:
Update worked only via Firmware Finder. But all is fine now. Reinstalled TWRP and magisk (no data loss) and all is working. Thanks for your help.
Click to expand...
Click to collapse
Would you mind sharing the steps you took to make it work?
I'm travelling abroad and keep getting the update reminder, and I'm too afraid to get an unusable phone to try anything

Question Rooting Zenfone 8

I understand there is no TWRP recovery for Zenfone 8 yet, but according to other posts, their are other ways to root the phone, e.g. using Magisk boot image patch method.
I tried, but I'm not able to flash the boot image in fastboot. I'm able to boot to fastboot mode, but it's showing no device when I use "fastboot devices" with USB connection. If I enter recovery mode, "adb devices" is showing unauthorized.
I don't know how to proceed. Appreciate your help!

It's solved by plugging the USB cable to USB 2.0 port on the PC

Good to hear it worked out. I was going to suggest installing a driver when in fastboot mode.
How did you get the boot image btw? I've never tried for anything other than a Lineage OS device, for which all the files are easily accesible.

To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.

After opening the bootloader and rooting the phone, are there any disadvantages you discovered? Warning screen on boot, (banking) apps not working, etc.?

DerSteppo said:
After opening the bootloader and rooting the phone, are there any disadvantages you discovered? Warning screen on boot, (banking) apps not working, etc.?
Click to expand...
Click to collapse
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.

dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
OK thanks for the information!

dohanin said:
To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.
Click to expand...
Click to collapse
After rooting, it seems that the official ota update cannot be detected, and it cannot be seamlessly achieved by using the Magisk to install to the unused slot. Is there any other way to achieve the update? For example, OnePlus can choose to install the full ota downloaded from the official website locally.

dohanin said:
To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.
Click to expand...
Click to collapse
Ah, thanks that did help. I didn't know the full firmware was available from the site.

yunyou said:
After rooting, it seems that the official ota update cannot be detected, and it cannot be seamlessly achieved by using the Magisk to install to the unused slot. Is there any other way to achieve the update? For example, OnePlus can choose to install the full ota downloaded from the official website locally.
Click to expand...
Click to collapse
Do you mean you already tried this with Zenfone 8 OTA update after rooting? I did it with firmware "WW-30.11.51.67" and it's still the current one, so I don't know whether it would work or not.

dohanin said:
Do you mean you already tried this with Zenfone 8 OTA update after rooting? I did it with firmware "WW-30.11.51.67" and it's still the current one, so I don't know whether it would work or not.
Click to expand...
Click to collapse
I found ota's solution. Download the "WW-30.11.51.67" firmware from the official website and move it to the main storage directory of the phone. Then the phone should detect the update file, but if the phone does not prompt, then try to restart the device. When the phone restarts and enters the system again, the system will detect the update, and there will be an update launcher notification in the notification bar!
When the system update interface is over, when prompted to restart, install to an unused slot through the Magisk option. Select the installation to keep ROOT to achieve seamless ota.

dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
If you use DRM Info app do you still have Widevine L1 security level? (needed for netflix hd playback) thanks.

grootzy said:
If you use DRM Info app do you still have Widevine L1 security level? (needed for netflix hd playback) thanks.
Click to expand...
Click to collapse
yes, it's showing L1 in Widevine CDM

dohanin said:
yes, it's showing L1 in Widevine CDM
Click to expand...
Click to collapse
Thanks, great news that ASUS are not being dicks with the bootloader unlocking.
For anyone else who isn't too clear on the steps (like me!) - After patching the boot image with magisk you then can use adb to pull that image to a PC and then use adb reboot bootloader and then fastboot boot patched-image.img to check the rooting works without flashing anything and then use adb reboot bootloader again and then fastboot flash boot patched-image.img to write it to the flash memory if everything went smoothly. This worked for me and everything seems great. Obviously you need adb and fastboot set up on your PC for this to work. I'm not sure if this was the intended method but it is what I did.

dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
did you try hiding magisk manager by changing the magisk manager package name? (it's an option in magisk manager).
some apps detect the magisk manager app to guess rooting.
If you hide magisk app + use magiskhide on the bank app it should be working.
please check let me know

fatjoez said:
did you try hiding magisk manager by changing the magisk manager package name? (it's an option in magisk manager).
some apps detect the magisk manager app to guess rooting.
If you hide magisk app + use magiskhide on the bank app it should be working.
please check let me know
Click to expand...
Click to collapse
hi, yes i tried but while most apps are working fine, some banking apps can still detect root. however, for those apps, if i disable the magisk app beforehand, then it can be passed. i could not figure why since the magisk app is already with a random package name. i posted my query in the magisk forum too.
anyway, with this method, i don't need to use work profile now.

Hi everbody.
I hope someone can help me out.
I unlocked my Zenfone 8 with the official unlock tool and i want to relock the bootloader back.
I was using commands like fastboot oem asus-lock, fastboot flashing lock, but nothing works.
Did Asus changed something in Android 11?
In Android 10 the first command was working without problems.
Thanks

You can't lock it back.
Only to change motherboard.

dron39 said:
You can't lock it back.
Only to change motherboard.
Click to expand...
Click to collapse
Oh that's bad news. Thank you very much for your fast answer.

yunyou said:
When the system update interface is over, when prompted to restart, install to an unused slot through the Magisk option. Select the installation to keep ROOT to achieve seamless ota.
Click to expand...
Click to collapse
Can you explain further on this? Are you saying to install the firmware to an unused slot? What exactly is an unused slot? I haven't seen anything like this in magisk.

How To Guide OnePlus 10 Pro NE2215 ***ROOTED*** (EX01 Update! READ BEFORE UPDATING)

This is for the NE2215 Rom.
Step 1: Unlock your bootloader.
Step 2: Download and install Magisk Stable or Canary. Your choice, but I used Canary.
https://github.com/topjohnwu/Magisk
Step 3: You can use either patch the stock boot or use my patched boot rom.
https://androidfilehost.com/?w=files&flid=333790
NOTE: This is for the original stock image when the phone first came out. See below for updates and boot images.
Step 4: Reboot to bootloader
Code:
adb reboot bootloader
Step 5: BOOT the patched boot rom! DO NOT FLASH!
Code:
fastboot boot patched_boot.img
* change patched_boot.img to whatever your filename is.
Step 6: Open Magisk and perform a direct install.
Step 7: Enjoy!
Additional steps to pass safetynet:
Step 8: Open Magisk, open the Settings menu, enable Zygisk, and reboot.
Step 9: Download and install Universal Safetynet Fix (Zygisk) by @kdrag0n.
https://github.com/kdrag0n/safetynet-fix/releases
Step 10: I forget if you really need this or not, but install it anyways.
MagiskHide Props
Step 11: Reboot.
Step 12: Enjoy!
Netflix Error -93:
WARNING: Netflix will not work after bootloader unlock. OnePlus's fault.
Here's how to get Netflix to work, but DRM will drop from L1 to L3.
Step 1: Uninstall Netflix.
Step 2: Flash Shamiko in Magisk and reboot.
Step 3: Install this version of Netflix.
Step 4: Open Netflix and close the app.
Step 5: Update Netflix from Google Playstore.
Step 6: Open Netflix and log in and force close the app.
Step 7: Open the app again and be greeted with error code 93, then force close the app.
Step 8: Open the app again and enjoy Netflix.
Updates:
NE2215_11.A.12
NE2215_11.A.13
NE2215_11.A.14
NE2215_11.A.15
NE2215_11.A.16
NE2215_11.A.17 Stock boot image and OTA. Thanks @mrdark5555
NE2215_11.C.19 Stable Color/OxygenOS 13
NE2215_11.C.20
NE2215_11.C.21
NE2215_11.C.22
NE2215_11.C.26
NE2215_11.C.30
NE2215_11.C.53 (EX01). About damn time! READ BEFORE UPDATING!
NE2215_11.C.54 (13.1.0.522(EX01))
NE2215_11.C.55 (13.1.0.580(EX01))

Hello, did you get the boot.img from the original firmware or did you extract from your device. If you have the full flash file for NE2215 please post a link. Thanks

rabunz1105 said:
Hello, did you get the boot.img from the original firmware or did you extract from your device. If you have the full flash file for NE2215 please post a link. Thanks
Click to expand...
Click to collapse
Got it from my device. I'll try to see if I can dump the files tomorrow.

g96818 said:
Got it from my device. I'll try to see if I can dump the files tomorrow.
Click to expand...
Click to collapse
Would you mind writing a quick tutorial on how to extract the image as well?

Cgrime said:
Would you mind writing a quick tutorial on how to extract the image as well?
Click to expand...
Click to collapse
I tried the trick of booting a patched EU boot to get some sort of temporary root in order to pull my original boot image.

Thank you for this!

Rooted just fine using your boot img. However, phone wont update now.. It says installation error.. Any ideas? Trying to update from a10 to a12 OTA.
Already factory reset phone.. Root still stuck and it wouldnt update.

Morrob95 said:
Rooted just fine using your boot img. However, phone wont update now.. It says installation error.. Any ideas? Trying to update from a10 to a12 OTA.
Already factory reset phone.. Root still stuck and it wouldnt update.
Click to expand...
Click to collapse
do you have NE2215_11_A.12 full zip?

I don't.. I tried updating to it OTA and it fails everytime. I tried oxygen updater but this version of the phone is too new just yet. I don't think the apps been updated.

Morrob95 said:
I don't.. I tried updating to it OTA and it fails everytime. I tried oxygen updater but this version of the phone is too new just yet. I don't think the apps been updated.
Click to expand...
Click to collapse
Did you "flash" the boot image at any point? If so then you're SOL. You need to find the unbrick image or try to relock your bootloader to see if that will restore all your system files.

NE2215_11.A.12 International Boot image & ROOT
CAUTION!
I do not know if are multiple OTA files for those still stuck on a previous versions before NE2215_11.A.12. I recommend just updating it through the system update. I updated through system update.
Not my fault if your phone breaks.
WARNING!!!
Issues I've seen on previous devices:
- A few people have had bootloop issues due to using the wrong rom on the wrong phone. (e.g. Installing the Global ROM on a EU, IN, or CN model)
- If you have "FLASHED" the patched boot vice "BOOT" at anytime prior to this, then you can NOT use OTA unless you want to bootloop or end up in EDL and wipe the phone.
I can't help you if your phone doesn't update properly.
-----------------------------------------------------------------------------------------
International NE2215_11.A.12 OTA Incremental update:
Official: https://android.googleapis.com/packages/ota-api/package/f99da5215db535177dabb71960ec6365a63af389.zip
Mirror: https://www.androidfilehost.com/?fid=14655340768118454642
SHA-1: F99DA5215DB535177DABB71960EC6365A63AF389
MD5: F7D3D8498B61B131D36F0C93F5DCEBEC
Or you can just use the full update package (PENDING)
International NE2215_11.A.12 full rom:
Official:
Mirror:
SHA-1:
MD5:
Two methods are available, PC and non-PC. I refer the non-PC method since it's much easier and it hasn't failed me yet so I'm just going to post instructions for that. You can look at previous update instructions if you want the PC method.
-----------------------------------------------------------------------------------------
NE2215_11.A.12 boot images (For reference only. Download not required):
Stock
boot_b.img | by Xi Jing Pooh for /e/OS supported models
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
SHA-1: 3BCFF2323A03F26FC94BB5A2196CC1B9611EEF53
MD5: 8BEEB2BE49E4A0F40D750E44205F1636
Patched
magisk_patched-24306_yeWsl.img | by Xi Jing Pooh for /e/OS supported models
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
SHA-1: 1676BEAD586662ADF4597CA0AB16A3064D13F633
MD5: 978E7F85AE3AA239E022C69888ACCF98
-----------------------------------------------------------------------------------------
Non-PC Method
See Warning above.
Step 1: You must unroot first. You don't have to completely remove Magisk, just restore images. Open Magisk, click uninstall magisk, and only click restore images. DO NOT REBOOT!
Step 2: Install OTA update. DO NOT REBOOT!
Step 3: Open Magisk and install to inactive slot. Reboot. Boot up took about 30 seconds.

Is there a way to use gpay? I'm an old rooter but I recall safety net check and what not will let you but I don't see that option in magisk app. Or is it a bootloader thing?

Sure it is. Universal safetynet fix by kdrag0n will help with it. And hiding Google Pay, Google services etc via magisk too.

g96818 said:
Did you "flash" the boot image at any point? If so then you're SOL. You need to find the unbrick image or try to relock your bootloader to see if that will restore all your system files.
Click to expand...
Click to collapse
Negative, I booted your boot image and installed the stable magisk.. it's weird though, I even went and booted your stock boot image and tried to do the update, same thing. Then I tried using oxygen updater, it found the update, downloaded it and it hangs half way through and says installation failed as well. I wiped the phone via factory reset, same issue.. is there an msm for the 215 yet that you know of?

After rooting it start to lag horrible but i have read about a fix here on XDA when you have done rooting to flash OTA update again and then root OTA and reboot to fix lags

Morrob95 said:
Negative, I booted your boot image and installed the stable magisk.. it's weird though, I even went and booted your stock boot image and tried to do the update, same thing. Then I tried using oxygen updater, it found the update, downloaded it and it hangs half way through and says installation failed as well. I wiped the phone via factory reset, same issue.. is there an msm for the 215 yet that you know of?
Click to expand...
Click to collapse
Not that I know of. I do know the unbrick tool also fixed update issues. What is your phone model?

HessNL said:
After rooting it start to lag horrible but i have read about a fix here on XDA when you have done rooting to flash OTA update again and then root OTA and reboot to fix lags
Click to expand...
Click to collapse
Idk. The only lag I have seen is opening the app drawer for the first time after restarting. Idk if that is normal or not since I rooted the phone and hour after opening the box.

g96818 said:
Not that I know of. I do know the unbrick tool also fixed update issues. What is your phone model?
Click to expand...
Click to collapse
NE2215, US model. I bought on Amazon and it came in yesterday, here are a bunch of sceenshots. I appreciate it! the help man! I'll maybe try the unbrick tool when I get home. But the phone isnt really... Bricked is it?

Morrob95 said:
NE2215, US model. I bought on Amazon and it came in yesterday, here are a bunch of sceenshots. I appreciate it! the help man! I'll maybe try the unbrick tool when I get home. But the phone isnt really... Bricked is it?
View attachment 5589389View attachment 5589403View attachment 5589413
Click to expand...
Click to collapse
I opted to buy straight from oneplus. I don’t trust what Amazon installs on the phone. It’s always easier to root a vanilla phone than to deal with one that has other peoples bloatware.
Did you unroot from magisk before wiping? I noticed sometimes wiping while rooted doesn’t remove root and magisk. Try doing a full magisk removal vice just restoring the boot and try factory reset, lock, and unlock the bootloader then fully root a10, restore the boot image, and try do the ota update. I’m suggesting this way so that you’ll know that you can update the next time.

g96818 said:
I opted to buy straight from oneplus. I don’t trust what Amazon installs on the phone. It’s always easier to root a vanilla phone than to deal with one that has other peoples bloatware.
Did you unroot from magisk before wiping? I noticed sometimes wiping while rooted doesn’t remove root and magisk. Try doing a full magisk removal vice just restoring the boot and try factory reset, lock, and unlock the bootloader then fully root a10, restore the boot image, and try do the ota update. I’m suggesting this way so that you’ll know that you can update the next time.
Click to expand...
Click to collapse
That I did not! And actually, after doing factory reset the phone was still rooted. Then I did the magisk uninstall. So I'm definitely gonna try that when I get home! I appreciate it!
Unroot, THEN wipe, THEN lock bootloader, THEN OTA, THEN ROOT. Perfect. Thanks man!
Any idea why Netflix won't work with a root? It says unable to contact server, -93. I even tried hiding magisk and doing safety net as well as doing the ignore on magisk for Netflix. Even tried older version apps.

Question Lost root with latest OTA...

Phone updated from 13.0.2.0 to 13.0.4.0 accidentally or by itself, not sure, received the latest OTA and after reboot root is gone...
How can i get root back without loosing data or formatting?

You need to reinstall it using adb method, remember: everytime you update you loose the root

xNAPx said:
You need to reinstall it using adb method, remember: everytime you update you loose the root
Click to expand...
Click to collapse
Will i use data/settings if i reinstall magisk via adb?

You mean lose? Nope you won't as you are not formatting anything

xNAPx said:
You mean lose? Nope you won't as you are not formatting anything
Click to expand...
Click to collapse
Sorry, i meant loose data... And last question, which adb method should i use? I don't have twrp installed either as it wasn't available while i was rooting 13.0.2.0... Not sure if it's available now...?

GODSPD said:
Sorry, i meant loose data... And last question, which adb method should i use? I don't have twrp installed either as it wasn't available while i was rooting 13.0.2.0... Not sure if it's available now...?
Click to expand...
Click to collapse
Adb method doesn't need twrp, it is a bit more difficult to inject the root but you don't need to go through twrp. Just search on Google you will find several guides, I can tell you that you need the boot.img of the installed ROM in order to complete the process. You usually find this file into the fastboot ROM zip package

xNAPx said:
Adb method doesn't need twrp, it is a bit more difficult to inject the root but you don't need to go through twrp. Just search on Google you will find several guides, I can tell you that you need the boot.img of the installed ROM in order to complete the process. You usually find this file into the fastboot ROM zip package
Click to expand...
Click to collapse
So I'm guessing it's the same process as last time, the required boot.img will need to be from the updated 13.0.4.0 version? I barely remember how i did it initially, if you have any guides that work id really appreciate it

For the version 13.0.2.0 I used tge boot.img of the same fastboot ROM, I don't know if it would work with another boot.img honestly

I cannot seem to find the boot.img for the latest ota...
xNAPx said:
For the version 13.0.2.0 I used tge boot.img of the same fastboot ROM, I don't know if it would work with another boot.img honestly
Click to expand...
Click to collapse
cannot find a boot.img for 13.0.4, cannot extract it from payload.bin either via python, nothing seems to be working

xNAPx said:
For the version 13.0.2.0 I used tge boot.img of the same fastboot ROM, I don't know if it would work with another boot.img honestly
Click to expand...
Click to collapse
I tried it and boot looped to the bootloader...try at your own risk

tensux said:
I tried it and boot looped to the bootloader...try at your own risk
Click to expand...
Click to collapse
Did you manage to get it done? Apparently you can extract the 13.0.4 boot.img from the roms payload.bin file but i couldn't get it done myself... Did you manage to root yours?

GODSPD said:
Did you manage to get it done? Apparently you can extract the 13.0.4 boot.img from the roms payload.bin file but i couldn't get it done myself... Did you manage to root yours?
Click to expand...
Click to collapse
no in fact I had to switch to xiaomi.eu. i couldnt get anything else to flash. it kept failing at the same spot, i dont quite remember but had the name "super" in it

Just wait for the fastboot ROM guys

xNAPx said:
Just wait for the fastboot ROM guys
Click to expand...
Click to collapse
if we only knew when and where that will be released

Usually a week or two after the recovery release