[GUIDE][ROOT][Moto G6 Plus] Magisk patched boot image OPWS27.113-45-4 - Moto G6 Plus Guides, News, & Discussion

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* thermonuclear war, or you getting fired because the alarms failed and you could not call in.
Please
* Ensure you have an advanced understanding of this device before flashing it! YOU are choosing to make these modifications or your own free will.
*/
Hi, here is patched boot image for Moto G6 Plus. Flash it to acquire root permissions on your device.
Please make sure you have June Firmware OPWS27.113-45-4
Please DO NOT flash on different device, this is only for MOTO G6 PLUS (Evert)
Instructions:
1. Unlock Bootloader
2. Download patched boot image patched_bootOPW27.113-45-4.img
3. Flash it with following command:
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Old April boot image OPW27.113-45: patched_boot.img
Note: If you need to restore the STOCK boot kernel, you can get it from 2nd Post below. Thanks @manos78

Hi,
I confirm that this kernel works! So now you can root your device. :victory:
Thank you @jekyll86!
If you like to test it by hand (with unlocked bootloader), then "fastboot boot stock_boot-MotoG6+-OPW27.113-45.img" and when running Android, then Install lasted Magisk Manager and then update to BETA Channel. This will generate a new patched kernel boot image using your stock boot.
Regards.
Note: If you need to restore the STOCK boot kernel (for an OTA, for example), you can get it from my backup: https://www.sendspace.com/file/i2dxh4

Hi,
One advise: If you patched the kernel with Magisk or flashed this kernel, then you can't do wipe of data using the "restore function of Andoid". It will fail until you flash the stock kernel.
If you see an error, then reflash the stock kernel!
Save a copy!

Thanks, this works perfectly fine with the latest magisk manager (5.7.0) and i managed to get xposed to work as well as gravitybox. I can center my clock again and tweak notifications, navbar longpress and such.
Magisk's package installer did fail to flash xposed but with 3.1.5 xposedinstaller.apk it did work and it flashes and reboots just fine.
I'm working on testing substratum rooted now. I'm just YOLO'ing a AOSP compatible theme on it and i'll see what fails..
If I get into the mood i might even try to flash a 8.1.0 TREBLE version of LOS15.1 or RRO if i can get that TWRP to properly boot via fastboot.

do you have root for xt1922?

and the the normal Motorola g6, still nothing? I'm sorry not to be root
Enviado desde mi moto g(6) mediante Tapatalk

stifmaster81 said:
and the the normal Motorola g6, still nothing? I'm sorry not to be root
Enviado desde mi moto g(6) mediante Tapatalk
Click to expand...
Click to collapse
cfsr4 said:
do you have root for xt1922?
Click to expand...
Click to collapse
Sorry guys, I'd like to help you but I have only G6Plus. If you want to root, you can follow magisk guide and patch boot image by yourself. It's not difficult
Inviato dal mio moto g(6) plus utilizzando Tapatalk

jekyll86 said:
Sorry guys, I'd like to help you but I have only G6Plus. If you want to root, you can follow magisk guide and patch boot image by yourself. It's not difficult
Inviato dal mio moto g(6) plus utilizzando Tapatalk
Click to expand...
Click to collapse
If the magick is for the Motorola g6 version, can you pass that guide please?
Enviado desde mi moto g(6) mediante Tapatalk

I have a question : you took the original boot.img of the firmware, put it into Magisk app and it gave you a pacthed_boot.img ?
I can't get this process working for the Moto G6 non plus that I got
Thank you for your time !

Snearde said:
I have a question : you took the original boot.img of the firmware, put it into Magisk app and it gave you a pacthed_boot.img ?
I can't get this process working for the Moto G4 non plus that I got
Thank you for your time !
Click to expand...
Click to collapse
That's it, what kind of error do you get?
Inviato dal mio moto g(6) plus utilizzando Tapatalk

Snearde said:
I have a question : you took the original boot.img of the firmware, put it into Magisk app and it gave you a pacthed_boot.img ?
I can't get this process working for the Moto G4 non plus that I got
Thank you for your time !
Click to expand...
Click to collapse
Well this sub-forum is for moto g6, not moto g4, your device have a dedicated forum for it and there is already various methods for rooting. you should go look there

Oh yeah sorry I mistyped on my keyboard I meant Moto g6 of course, nevermind this !

jekyll86 said:
That's it, what kind of error do you get?
Inviato dal mio moto g(6) plus utilizzando Tapatalk
Click to expand...
Click to collapse
Hi !
Well I took the boot.img from the Moto G6 firmware in this subforum. I used magisk manager to patch this .img from my phone. (Boot.img was > 20MB whereas patched_boot.img is ~ 12MB, sounds strange..)
When I boot on this .img with fastboot, I got a bootloop and it gets back to the original kernel. So I tried to flash it, and it is stuck at boot. The "Warning, bootloader unlocked" shows the "N/A" code, and then the M logo shows up and never moves even after 10 minutes.
The fact that patched_boot.img is significantly smaller than boot.img sounds strange to me. I must be missing something.. too bad. I wanted to provide a patched_boot.img for moto G6 (mine is XT1925 reteu) on this subforum, but since I'm not able to boot from it it is not ready yet

Snearde said:
Hi !
Well I took the boot.img from the Moto G6 firmware in this subforum. I used magisk manager to patch this .img from my phone. (Boot.img was > 20MB whereas patched_boot.img is ~ 12MB, sounds strange..)
When I boot on this .img with fastboot, I got a bootloop and it gets back to the original kernel. So I tried to flash it, and it is stuck at boot. The "Warning, bootloader unlocked" shows the "N/A" code, and then the M logo shows up and never moves even after 10 minutes.
The fact that patched_boot.img is significantly smaller than boot.img sounds strange to me. I must be missing something.. too bad. I wanted to provide a patched_boot.img for moto G6 (mine is XT1925 reteu) on this subforum, but since I'm not able to boot from it it is not ready yet
Click to expand...
Click to collapse
It seems an issue with magisk manager that doesn't patch your kernel correctly. Report this problem in magisk thread.
Inviato dal mio moto g(6) plus utilizzando Tapatalk

Snearde said:
Hi !
Well I took the boot.img from the Moto G6 firmware in this subforum. I used magisk manager to patch this .img from my phone. (Boot.img was > 20MB whereas patched_boot.img is ~ 12MB, sounds strange..)
When I boot on this .img with fastboot, I got a bootloop and it gets back to the original kernel. So I tried to flash it, and it is stuck at boot. The "Warning, bootloader unlocked" shows the "N/A" code, and then the M logo shows up and never moves even after 10 minutes.
The fact that patched_boot.img is significantly smaller than boot.img sounds strange to me. I must be missing something.. too bad. I wanted to provide a patched_boot.img for moto G6 (mine is XT1925 reteu) on this subforum, but since I'm not able to boot from it it is not ready yet
Click to expand...
Click to collapse
Hi,
Please take note of this:
- Moto G6 and Moto G6 are a very different hardware devices: different SoC, different ROM, and different kernel. So, you can't interchange kernels.
- This forum is, in fact, for "Moto G6 family", that's the Moto G6, Moto G6+ and Moto G6 play.
- This thread in the Title indicates [Moto G6 Plus] so this kernel is only for G6+, it doesn't work in your G6.
- Before flash a kernel it's a good idea to boot it for try it. If it fails... never flash it!
So, your only solution is reflash stock G6 kernel. You have a copy of it?

Yes, I only booted from the kernel with "fastboot boot" command, I didn't flashed it on my phone
Anyway thanks for your help, I will explain my issue on the magisk thread !
Have a nice day

With the bootlock unlocked, is the cell fhone more vulnerable?

cfsr4 said:
With the bootlock unlocked, is the cell fhone more vulnerable?
Click to expand...
Click to collapse
Bootloader unlocking does not make your phone more vulnerable, but rooting it.
Normally, Android apps work in isolated environments and cannot gain access to other apps or the system. However, an app with root access rights can venture out of its isolated environment and take full control over the device. So if you install malicious app, with root access they can do more damages.
Root your phone only if you need to root it and you know what you are doing.

@jekyll86
Hi I have OPW27.113-25 Firmware instead of -45. will this work any way? because I can't get my Boot.img to creat my own patched boot.img
thanks!

pelpa87 said:
@jekyll86
Hi I have OPW27.113-25 Firmware instead of -45. will this work any way? because I can't get my Boot.img to creat my own patched boot.img
thanks!
Click to expand...
Click to collapse
I advise you to update your phone. Anyway, you can test it without flashing with the following command:
Code:
fastboot boot patched_boot.img
if the the device boot up, you can flash it, otherwise don't flash and wait for update

Related

Root h850 with Nougat 7.0

Hi! I have an LG G5 h850 and I've flashed this ROM (a full flashable zip of Android Nougat 7.0 stock). The problem is I can't seem to root my phone.
If I flash any SuperSU zip with TWRP 3.1.0.0, the phone won't be able to boot afterwards (it will get stuck at the LG logo).
I've iunlocked my bootloader using the official procedure (fastboot getvar unlocked returns "yes") and I've also flashed no verity opt encrypt 5.1 after wiping data: my TWRP can access internal storage.
What am I missing? Is there a specific SuperSU zip which works on a Nougat h850? Has the problem got something to do with dm-verity?
I have an LG G5 H850 with TWRP 3.1.0..0 and SuperSU 2.65 installed. I did not install the no-verity and my phone is operating normally. Just need a way to get rid of the "your phone is unlocked" screen on boot up.
Sent from my LG-H850 using Tapatalk
N or M?
Stransky said:
I have an LG G5 H850 with TWRP 3.1.0..0 and SuperSU 2.65 installed. I did not install the no-verity and my phone is operating normally. Just need a way to get rid of the "your phone is unlocked" screen on boot up.
Sent from my LG-H850 using Tapatalk
Click to expand...
Click to collapse
Are you sporting Nougat or Marshmallow? With Android M I rooted it with no problems.
Nougat and i had no problems rooting.
Sent from my LG-H850 using Tapatalk
Stransky said:
Nougat and i had no problems rooting.
Sent from my LG-H850 using Tapatalk
Click to expand...
Click to collapse
That's astounding. Do you remember the procedure you followed? Is the ROM the same I used (LG-H85020A-Flashable.COMPLETE.zip)? Is the precise SuperSU version UPDATE-SuperSU-v2.65-20151226141550?
Patching sepolicy failure
I've proceeded to reinstall N and SuperSU 2.65 and I see the following message:
Code:
- Patching sepolicy
--- Failure, aborting
Given Android N requires systemless mode, hence boot image patching, could this be the cause? What should I do?
HisDudeness3008 said:
That's astounding. Do you remember the procedure you followed? Is the ROM the same I used (LG-H85020A-Flashable.COMPLETE.zip)? Is the precise SuperSU version UPDATE-SuperSU-v2.65-20151226141550?
Click to expand...
Click to collapse
The ROM is the same (H85020a) but my phone was updated OTA.
Sent from my LG-H850 using Tapatalk
---------- Post added at 06:22 PM ---------- Previous post was at 06:15 PM ----------
Further to my last I used @autoprime's unlocking the G5 bootloader thread and followed the instructions on it, including the installation of TWRP etc.
Sent from my LG-H850 using Tapatalk
Enter password to unlock
Stransky said:
The ROM is the same (H85020a) but my phone was updated OTA.
Sent from my LG-H850 using Tapatalk
Click to expand...
Click to collapse
I see... I couldn't update OTA because when it had to install the downloaded update it just rebooted to TWRP.
Anyway, after getting that error message, I flashed a newer version of SuperSU. It patched sepolicy successfully and even booted (I don't know what I did different than other times). Anyway, it prompted me with an "Enter password to unlock message", with some attempts already out (23/30).
Could it be because I have decrypted data partition? I read the decryption and root access are mutually exclusive. I decripted just because, after the 30th failed boot attempt, I tried it just to change something and see if it worked.
If I have to choose between the two, I'll choose root access. How do I restore encryption?
Sorry, have no idea, I don't use encryption.
Sent from my LG-H850 using Tapatalk
Stransky said:
Sorry, have no idea, I don't use encryption.
Sent from my LG-H850 using Tapatalk
Click to expand...
Click to collapse
I mean the default setup of the G5, whereas TWRP can't access internal storage and will ask you for a password upon starting, to which you have to hit "cancel".
When I hit cancel in TWRP in answer to the password I then swipe below to allow modifications. At least that is what I am offered on the swipe window.
Sent from my LG-H850 using Tapatalk
Yeah, that is indeed the default behaviour. However, at some point I've flashed no-verity-opt-encrypt zip. This removes the encryption. TWRP doesn't have to ask you for a password you do not know, and can thus modify /data partition. This, however, prevents you from rooting your device. And, apparently, prevents me from booting my phone right now. Is there any way to revert the effects of no-verity-opt-encrypt?
I am sorry, I am not even remotely akin to a developer, I only follow their instructions so am not aware if it is possible to revert the no- verity effects. The only suggestion I can come up with is to do a factory reset backbto stock Nougat and then redo the installation of TWRP etc omitting "no-verity" option. But I would check with someone like Autoprime first to see if this will work and not create more problems. Sorry I can't be of more help.
Sent from my LG-H850 using Tapatalk
No problem, you've been of enough help! I thank you for your time.
I know, I'm not akin to a developer as well, but I have the bad habit of getting myself into developer trouble
Solved one: I unbricked my phone. Followed this excellent guide from by dksoni411. I thank him with all my heart, as well as AutoPrime, Hyelton, bullghost and anyone else who contributed.
Solved two: I finally managed to root my h850. Don't know what I did different from the other dozen times I tried. From stock Nougat 7.0 I rebooted to fastboot mode via adb, flashed TWRP in fastboot, booted into recovery without allowing normal boot to happen before it, flashed SuperSU (v2.79-20161211114519), didn't wipe cache or dalvik, and rebooted. Upon boot, phone reset once and then booted straight into Nougat, with SuperSU apk installed. Yay!
HisDudeness3008 said:
Solved one: I unbricked my phone. Followed this excellent guide from by dksoni411. I thank him with all my heart, as well as AutoPrime, Hyelton, bullghost and anyone else who contributed.
Solved two: I finally managed to root my h850. Don't know what I did different from the other dozen times I tried. From stock Nougat 7.0 I rebooted to fastboot mode via adb, flashed TWRP in fastboot, booted into recovery without allowing normal boot to happen before it, flashed SuperSU (v2.79-20161211114519), didn't wipe cache or dalvik, and rebooted. Upon boot, phone reset once and then booted straight into Nougat, with SuperSU apk installed. Yay!
Click to expand...
Click to collapse
Tnx man! :good: U should post step by step what u did to root as separate thread, cuz U have been a tremendous helper, u know?? U solved Huuuuuge problem , so U can be great helper to those who could came into similar troubles :victory:

[Magisk] [EMUI 8.0] Root Honor View 10, Mate 10 (Pro) (Huawei Treble Devices)

Magisk has officially landed on the lovely Treble enabled Huawei devices! Props to Huawei reaching out and sent me a device for development
Instead of holding it off and wait till the next proper release, I decide to release it here so those willing to root their device can give it a try.
These Huawei Treble devices use an interesting setup: it no longer has a boot and recovery partition, but instead has a kernel partition, a ramdisk partition, and a recovery_ramdisk partition. Both boot and recovery share the same kernel, but with separate ramdisks on separate partitions. Since Magisk modifies the ramdisk in boot images, the patches will have to be applied to the ramdisk partition. This nature will very likely to also slightly change how custom recovery will be installed, my bet is similar to Pixel devices which ships with a full ramdisk image, and should be flashed to the recovery_ramdisk partition.
This build is only tested with Honor View 10, but it should work with Mate 10 and Mate 10 Pro in theory since these devices are very similar.
Enough of the rambling, let's get right into it!
Instructions
If your device have TWRP support, just directly flash it via TWRP. For devices without TWRP yet (currently all Huawei Treble devices), you can follow the instructions below:
Install latest Magisk Manager from the Official Thread
Go to Settings > Update Settings > Update Channel > Custom, and insert the following URL: https://goo.gl/jefZKH
Follow the instructions of "Install Via Magisk Manager" in the main thread, but instead of providing the boot image (which these devices do NOT have), provide the stock ramdisk.img.
If you are using EU View 10 with model BKL-L09, you can download the stock ramdisk.img I extracted from official OTAs in the attachments
If you have stock ramdisk images for other devices, please share them and I'll add them to the OP.
Make sure you are installing Magisk-v15.4(1541), which is only available through the custom channel you've set in step 2.
Pull the patched image with adb pull /sdcard/MagiskManager/patched_boot.img, and flash the patched ramdisk via fastboot:
fastboot flash ramdisk patched_boot.img
Reboot and you shall have a properly rooted device passing SafetyNet, start playing with some Magisk modules!
Donation
https://www.paypal.me/topjohnwu
topjohnwu said:
Magisk has officially landed on the lovely Treble enabled Huawei devices! Props to Huawei reaching out and sent me a device for development
Instead of holding it off and wait till the next proper release, I decide to release it here so those willing to root their device can give it a try.
These Huawei Treble devices use an interesting setup: it no longer has a boot and recovery partition, but instead has a kernel partition, a ramdisk partition, and a recovery_ramdisk partition. Both boot and recovery share the same kernel, but with separate ramdisks on separate partitions. Since Magisk modifies the ramdisk in boot images, the patches will have to be applied to the ramdisk partition. This nature will very likely to also slightly change how custom recovery will be installed, my bet is similar to Pixel devices which ships with a full ramdisk image, and should be flashed to the recovery_ramdisk partition.
This build is only tested with Honor View 10, but it should work with Mate 10 and Mate 10 Pro in theory since these devices are very similar.
Enough of the rambling, let's get right into it!
Instructions
If your device have TWRP support, just directly flash it via TWRP. For devices without TWRP yet (currently all Huawei Treble devices), you can follow the instructions below:
Install latest Magisk Manager from the Official Thread
Go to Settings > Update Settings > Update Channel > Custom, and insert the following URL: https://goo.gl/jefZKH
Follow the instructions of "Install Via Magisk Manager" in the main thread, but instead of providing the boot image (which these devices do NOT have), provide the stock ramdisk.img.
If you are using EU View 10 with model BKL-L09, you can download the stock ramdisk.img I extracted from official OTAs in the attachments
If you have stock ramdisk images for other devices, please share them and I'll add them to the OP.
Make sure you are installing Magisk-v15.4(1541), which is only available through the custom channel you've set in step 2.
Pull the patched image with adb pull /sdcard/MagiskManager/patched_boot.img, and flash the patched ramdisk via fastboot:
fastboot flash ramdisk patched_boot.img
Reboot and you shall have a properly rooted device passing SafetyNet, start playing with some Magisk modules!
Donation
https://www.paypal.me/topjohnwu
Click to expand...
Click to collapse
Finally!! [emoji16] was waiting for this.... Thank You.
Sent from my BKL-L09 using Tapatalk
Awesome mate. This also working with Huawei P10 plus running Treble V9. Thank you thank you :good:
Nice! Great job
We can do this follow instructions from completely stock bkl l09 C636? My 1st honor phone.. Not sure it have those locked boot loader like xiaomi or not..
Help..
Hey man, Thanks a lot.. It's really nice to have magisk for v10.. I am kind of a noob.. Can u provide step by step instructions and Patched Img for Indian version BKL-09..
Thanks
does this require an unlocked bootloader?
Root Final Stage issue!
I have done all the steps but on the last stage when I try to flash ramdisk it's giving me an error failed (remote: command not allowed) please help...thanks
Rj_Param said:
I have done all the steps but on the last stage when I try to flash ramdisk it's giving me an error failed (remote: command not allowed) please help...thanks
Click to expand...
Click to collapse
This could be due to locked bootloader...
bhargavpa said:
This could be due to locked bootloader...
Click to expand...
Click to collapse
Thanks... Let me try again after unlocking bootloader.
Sent from my BKL-L09 using Tapatalk
Wow, that's freaky fast man.. you are wonderful.
since we don't have official firmware released yet and out of concern I'm asking, is there any chance of bootloop or brick?
I understand it shouldn't be if we follow steps in OP, but sometimes people miss a step or do something else, so what's the worst can we expect?
Narasimha12 said:
Wow, that's freaky fast man.. you are wonderful.
since we don't have official firmware released yet and out of concern I'm asking, is there any chance of bootloop or brick?
I understand it shouldn't be if we follow steps in OP, but sometimes people miss a step or do something else, so what's the worst can we expect?
Click to expand...
Click to collapse
So long as you have a backup of your device's ramdisk image, you should be fine. The ramdisk for the Honor View 10 is attached to the OP.
Does the ramdisk.img work for indian variants?
shihabsoft said:
Does the ramdisk.img work for indian variants?
Click to expand...
Click to collapse
Yes it's working... Just finished installing magisk...so far everything is fine but somehow SafetyNet is not working.
Sent from my BKL-L09 using Tapatalk
Rj_Param said:
Yes it's working... Just finished installing magisk...so far everything is fine but somehow SafetyNet is not working.
Sent from my BKL-L09 using Tapatalk
Click to expand...
Click to collapse
so you unlocked bootloader right? and also any honor features broke??? like camera modes etc etc...and share bootloader unlock process too...
@topjohnwu
Its doesn't work with my twrp 3.2.1-0 for P10plus. A older twrp version works.
It's a twrp version thing or do I need to add something?
Rj_Param said:
Yes it's working... Just finished installing magisk...so far everything is fine but somehow SafetyNet is not working.
Sent from my BKL-L09 using Tapatalk
Click to expand...
Click to collapse
Thanks for letting me know. So what are those software changes happened right after bootloader unlocking?
To install Magisk and gain root in your honor view 10 you have to unlock your bootloader first.
##Please backup your data before proceeding with the process. You will loose all your data if you unlock the bootloader. ##
Please follow below steps to unlock bootloader
1) Create a Huawei ID on this page https://goo.gl/GkkdxE if you don’t have one already.
2) After creating a Huawei id, fill out the details.
3) You will need your phone’s IMEI number, to know that dial * # * # 1357946 # * # * on the dialer app. Fill the required fields and click the Submit button.
4) Save the unlock code you received.
5) Now connect your Honor View 10 to the PC with a USB cable.
6) In the ADB command window, type the following command to boot your Honor View 10 into fastboot mode.
adb reboot bootloader
7) To unlock the bootloader, type the following command and hit Enter. Replace key with the unlock key you’ve previously saved. For example, fastboot oem unlock 44801904392841
fastboot oem unlock [unlock key]
Sent from my BKL-L09 using Tapatalk
FWIW the Honor View 10's ramdisk works on the Huawei Mate 10 Pro. I would definitely not try that with any non-Kirin 970 device, though.
Rj_Param said:
To install Magisk and gain root in your honor view 10 you have to unlock your bootloader first.
##Please backup your data before proceeding with the process. You will loose all your data if you unlock the bootloader. ##
Please follow below steps to unlock bootloader
1) Create a Huawei ID on this page https://goo.gl/GkkdxE if you don’t have one already.
2) After creating a Huawei id, fill out the details.
3) You will need your phone’s IMEI number, to know that dial * # * # 1357946 # * # * on the dialer app. Fill the required fields and click the Submit button.
4) Save the unlock code you received.
5) Now connect your Honor View 10 to the PC with a USB cable.
6) In the ADB command window, type the following command to boot your Honor View 10 into fastboot mode.
adb reboot bootloader
7) To unlock the bootloader, type the following command and hit Enter. Replace key with the unlock key you’ve previously saved. For example, fastboot oem unlock 44801904392841
fastboot oem unlock [unlock key]
Sent from my BKL-L09 using Tapatalk
Click to expand...
Click to collapse
I know the procedure, but once you unlock the bootloader does any security features get disabled? And does it just wipe /data or including the internal storage?

Root available ?

Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
cubano2031 said:
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
Click to expand...
Click to collapse
Sent from my LGE LM-X410.FGN using XDA Labs
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Rebel_X said:
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Click to expand...
Click to collapse
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
Thanks a lot!! And it was as simple as that. It works fine. :good:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
MAREK10747 said:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
Click to expand...
Click to collapse
Hi,me devie is I4293
I have unrar the rom , so i get the boot_X-FLASH-ALL-8F02.sin
would you mind to make the kernel for me?
the file is here :
https://drive.google.com/file/d/1sywqfBtELSTgRXtTBEvlI454K_1ul-1h/view?usp=sharing
my gmail is [email protected]
you can send it to me.
thank you.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
yishisanren said:
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
Click to expand...
Click to collapse
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Zaben said:
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Click to expand...
Click to collapse
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
yishisanren said:
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
Click to expand...
Click to collapse
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
wang4632 said:
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
Click to expand...
Click to collapse
older version can not patch boot.img, because when you click "install the zip",it will let you update the new verison.
Any news on the boot loop situation? I also encounterd this problem and back to running original boot.img. having an unlocked bootloader is useless without root ?
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Did you lose any feature like super vivid mode and camera focusing after unlocking the bootloader?
can't find the driver, the model is l421dual sim, can't rooting, have i already patched the boot img?
My I4293 stuck in bootloop~~help ~!
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
This phone cannot be rooted at this time due to the lack of the img.patch and no driever.
Zack_U said:
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
Click to expand...
Click to collapse
Are you still stuck? For all of the latest Sony phones try NewFlasher instead.
https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
Flashtool doesn't support our phones. Magisk 19.1+ currently doesn't work with our phones. Hopefully 19.4 will fix that.

[Guide]Magisk Modules Disabler for booting into Magisk core-only Mode

Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/sho....php?t=2073775
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel3.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3Remove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291
Amazing! Thanks
I can confirm this worked on Android 10/Q. I can't use the canary patch method for magisk because I forgot to remove the modules before upgrading to Android 10. This method works like a charm, it removed the incompatible modules allowed me to by pass the bootloop.
Thank you so much for sharing!
For those who are wondering, these are the steps:
adb reboot bootloader
fastboot flash boot image-new.img
fastboot reboot
Done!
wao20 said:
For those who are wondering, these are the steps:
adb reboot bootloader
fastboot flash boot image-new.img
fastboot reboot
Done!
Click to expand...
Click to collapse
Second step should be:
fastboot boot image-new.img
Tulsadiver said:
Here is a fastboot bootable image to boot you into Magisk core-only mode. If you bootloop due to flashing a bad module, in fastboot:
fastboot boot image-new.img
You will boot with root but modules disabled.
Tested by me and @123SIT whom contributed on the project.
Made from Pixel 3 XL but should work on the Pixel 3 also.
Image
https://mega.nz/#!NE5yGaBA!0HLSWvdD4x4cOmo35HrDGrGNxTAUGW4LpkpVv1ygwVI
Thanks to @ApeironTsuka for his guide and everyone on the Magisk support thread like @jcmm11 for their patience and help.
Click to expand...
Click to collapse
Any idea if this works on the Pixel 2 and 2XL?
Sent from my Pixel C using Tapatalk
Alxoom33 said:
Any idea if this works on the Pixel 2 and 2XL?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
No, but you have TWRP. You don't need it.
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Sent from my Pixel 2 XL using Tapatalk
Alxoom33 said:
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Click to expand...
Click to collapse
Only since the update to android 10
Alxoom33 said:
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I just came across a time when I couldn't even boot TWRP on my Pixel 2. Here is a boot with root, core-mode Magisk image for Pixel 2 XL.
https://www.androidfilehost.com/?fid=1899786940962594367
Tulsadiver said:
I just came across a time when I couldn't even boot TWRP on my Pixel 2. Here is a boot with root, core-mode Magisk image for Pixel 2 XL.
https://www.androidfilehost.com/?fid=1899786940962594367
Click to expand...
Click to collapse
Yeah, I remember those days. Thanks for the image. Can it be flashed in TWRP or strictly adb/fastboot?
Sent from my Pixel 2 XL using Tapatalk
Alxoom33 said:
Yeah, I remember those days. Thanks for the image. Can it be flashed in TWRP or strictly adb/fastboot?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I've only used fastboot.
Tulsadiver said:
Here is a fastboot bootable image to boot you into Magisk core-only mode. If you bootloop due to flashing a bad module, in fastboot:
fastboot boot image-new.img
You will boot with root but modules disabled.
Tested by me and @123SIT whom contributed on the project.
Made from Pixel 3 XL but should work on the Pixel 3 also.
Image
https://mega.nz/#!NE5yGaBA!0HLSWvdD4x4cOmo35HrDGrGNxTAUGW4LpkpVv1ygwVI
Thanks to @ApeironTsuka for his guide and everyone on the Magisk support thread like @jcmm11 for their patience and help.
Click to expand...
Click to collapse
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
FcukBloat said:
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
Click to expand...
Click to collapse
Here is a link to it on my GDrive. Can you please let me know when you've got it so I can delete it?
https://drive.google.com/file/d/1rg5wENhILz8ah8jSdLne2OtaLYGOhdBI/view?usp=sharing
sliding_billy said:
Here is a link to it on my GDrive. Can you please let me know when you've got it so I can delete it?
https://drive.google.com/file/d/1rg5wENhILz8ah8jSdLne2OtaLYGOhdBI/view?usp=sharing
Click to expand...
Click to collapse
got it! thanks this time too!
FcukBloat said:
got it! thanks this time too!
Click to expand...
Click to collapse
No problem. It's good to be a pack rat. I hope it worked.
FcukBloat said:
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
Click to expand...
Click to collapse
Mega link seems to be working. Open with chrome, not mega app.
Edit: I've added a AFH download link.
i tried with chromium based browser (vivaldi) from both phone and pc and link didn't work, probably it was a WiFi problem, thanks for adding alternative link though. and your core mode image worked like a charme! and thanks again also to sliding billy for initial mirror support
Just what I needed. Thank you
How did you create it? I want to make sure I have one of these images on hand in the future when I need to fix things
Simply works, thank you!
Holy cow, thanks man. I can't believe @topjohnwu let this slide through. Without TWRP wtf are you supposed to do, reflash the whole OTA/factory image?!
EDIT: Wait, now I can boot and apparently have root but I can't access any of my rooted apps. It says "waiting for root". Magisk Manager gives me an "app not installed" error but it is installed on the device. When I click it it says "upgrade to full Magisk Manager" and does nothing. How am I supposed to delete the module folder?
EDIT: Can't access terminal, can't do anything. Permission denied via ADB as well.
EDIT: DO NOT DELETE MAGISK MANAGER OR ALTER IT IN ANY WAY WHEN USING CORE MODE. You will be stuck like me. I had to nuke my phone and reflash everything. PIA

How To Guide Root Tool Oneplus Nord 2 Oxygen 11.3 DN2103_11_A.xx EEA

Flash at your own risk. I am not responsible for any damage or data loss to the device during this process!​Can you download from here
https://mega.nz/file/TcRnmILA#WBnTsOgyK6QMfBnxk9KnBHq5bxEhXTGKCgTHpuXVEVc
Unlock your bootloader see the Guide from @Eastw1ng
Unlocking the bootloader
Since there is no proper information about unlocking the bootloader for the newer versions of Oneplus Nord 2, this is how I got it to unlock and actually work. For my system it did reset the device, clearing all the files and factory restoring...
forum.xda-developers.com
Extract zip
Run 1. ROOTinstaller.bat
Only for
Oneplus Nord 2 Oxygen 11.3
DN2103_11_A.07 EEA
DN2103_11_A.09 EEA
DN2103_11_A.10 EEA
DN2103_11_A.11 EEA
Looking at other of your posts, I guess that to root the phone we should run:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta2.img
fastboot flash boot nord2_stock_boot_A07.img
Click to expand...
Click to collapse
(replacing nord2_stock_boot_A07.img by the exact version, if needed).
Is that right?
Dr-Noob said:
Looking at other of your posts, I guess that to root the phone we should run:
(replacing nord2_stock_boot_A07.img by the exact version, if needed).
Is that right?
Click to expand...
Click to collapse
Hi, yes but you can download my root installer from my Megadrive and start the batch file. You can choose in the screen for v7, v9 and v10
Thanks! It worked perfectly. I saw the .bat file, but I'm using Linux. For the record, the steps I followed were:
1. Unlock the bootloader (use "fastboot getvar all" to check if the bootloader is unlocked or not)
adb reboot bootloader
fastboot flashing unlock
fastboot reboot
Click to expand...
Click to collapse
The phone will reboot. Complete the initial setup (unlocking the bootloader makes the phone to do a factory reset...).
2. Check the exact OS version
3. Flash the provided .imgs (IMPORTANT: Make sure to replace the boot img by the one aimed for the specific OS you are using)
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta2.img
fastboot flash boot nord2_stock_boot_A07.img
fastboot reboot
Click to expand...
Click to collapse
4. Install the magisk manager APK (https://github.com/topjohnwu/Magisk/releases).
Does the Magisk pass safetynet? And is this based on EU variant?
manis99 said:
Does the Magisk pass safetynet? And is this based on EU variant?
Click to expand...
Click to collapse
This is EU variant abd Magisk passes saftynet if you flash Riru and Universal Safetynet Fix v2.1.0 modules.
Thanks for this! There were rumors the OnePlus Nord 2 could never be rooted because it has a mediatek processor and that got me pretty disappointed. So it's very nice to see people are finding ways to do it! I'll still wait until there are some stable custom recovery options in case I screw up.
Kenaestic said:
Thanks for this! There were rumors the OnePlus Nord 2 could never be rooted because it has a mediatek processor and that got me pretty disappointed. So it's very nice to see people are finding ways to do it! I'll still wait until there are some stable custom recovery options in case I screw up.
Click to expand...
Click to collapse
yes there is always a certain risk, but do not worry, because as long as you have the EU (Version A07/09/10) variant, you can restore the 2 files via fastboot and go back to stock. soon TWRP and OrangeFox will appear, only the MSM tool is missing
Worked like a charm!
On Mac so just grabbed the commands out of the .bat file.
Thanks mate!
With future version updates, will we need to root again?
You can also use this process it's tedious but you get twrp with root access
TUTORIAL TWRP AND ROOT NORD 2 OXYGEN OS 11 ( Links updated!)
SO finally I successfully rooted with TWRP and root access.thanks to all developers @Eastw1ng @TheMalachite Following are all download links combined in one post Also there are two threads like unlocking boot loader and twrp but there are some...
forum.xda-developers.com
HofaTheRipper said:
This is EU variant abd Magisk passes saftynet if you flash Riru and Universal Safetynet Fix v2.1.0 modules.
Click to expand...
Click to collapse
Thanks, this worked!
Any one got full A11 new update zip
pankspoo said:
Qualcuno ha ricevuto il nuovo zip di aggiornamento completo di A11
Click to expand...
Click to collapse
yes but i didn't install it
the BAT is incorrect for a.11 version
This may seem like a dumb question but how do I find what "A.xx" for example "A.07"
NotReeceHarris said:
This may seem like a dumb question but how do I find what "A.xx" for example "A.07"
Click to expand...
Click to collapse
Nvm Dumb question
Do we have an A.14 option?
Thread closed as OP's request.

Categories

Resources