after a long time lost I finally got TWRP and magisk working on my device.
For those who need it for their devices I put here the boot.img and the twrp recovery.
It has only been tested on my device which is a rockchip px3 MTCE-XRC with android 7.1
The boot. img has the latest version of magisk canary build and so have to install the corresponding manager.
Of course the main credits go to those who created these apps.
My device is working fine but I can not guarantee that it will work on all MTCE or MTCD devices.
Test at your own risk. I do not take any responsibility if anything goes wrong.
I do not expect any thanks but it would be nice if anyone who tested gave some feedback so that other members can use it more confident
tuga_z said:
I do not expect any thanks but it would be nice if anyone who tested gave some feedback so that other members can use it more confident
Click to expand...
Click to collapse
Possibly lack of interest because users will be unable to upgrade Android and unable to update MCU in TWRP. This is a well known discussed limitation.
marchnz said:
Possibly lack of interest because users will be unable to upgrade Android and unable to update MCU in TWRP. This is a well known discussed limitation.
Click to expand...
Click to collapse
The great advantage of using TWRP is that we can easily backup the entire system to restore everything if something goes wrong when we need update the system and easily we install a stock recovery if we need to do some rom or mcu update. The image boot with magisk installed I just put it here because I've seen a lot of people complaining that they can not install magisk on rockchip devices.
tuga_z said:
after a long time lost I finally got TWRP and magisk working on my device.
For those who need it for their devices I put here the boot.img and the twrp recovery.
It has only been tested on my device which is a rockchip px3 MTCE-XRC with android 7.1
The boot. img has the latest version of magisk canary build and so have to install the corresponding manager.
Of course the main credits go to those who created these apps.
My device is working fine but I can not guarantee that it will work on all MTCE or MTCD devices.
Test at your own risk. I do not take any responsibility if anything goes wrong.None I have uploaded this file but I cannot install it with the magisk application. Magisk version V7.0.0 I can't update
Click to expand...
Click to collapse
Related
Does anyone have a suggestion of the easiest way to update android to the latest March security update after installing TWRP and rooting with xceede's kernel as per oRAirwolf's guide?
I see there is an updated version of the kernel available but cannot work out how to update android system without OTA or custom ROMs.
Many thanks, sorry for my ignorance.
zezayer said:
Does anyone have a suggestion of the easiest way to update android to the latest March security update after installing TWRP and rooting with xceede's kernel as per oRAirwolf's guide?
I see there is an updated version of the kernel available but cannot work out how to update android system without OTA or custom ROMs.
Many thanks, sorry for my ignorance.
Click to expand...
Click to collapse
I would recommend downloading the latest factory image (or whatever version you want to update to) and flashing all of the partitions individually (EXCEPT USERDATA, as that will wipe your device). This is what I've done for years on all my Nexus devices when updating. You'll just have to re-flash TWRP and Xceed after upgrading. Shouldn't be too difficult. Some may say you really only need to flash certain partitions like system, boot, vendor etc., but I always find it better to err on the side of caution to make sure I don't bork anything in the process.
tl;dr
See Step 9 from this post from the Nexus 6P forums (obviously, make sure you replace the angler image files with the appropriate Pixel C images): http://forum.xda-developers.com/showpost.php?p=62924118&postcount=2
Success: - Thanks for the tips.
Downloaded MXC14G vendor image from google. (Link)
Unzipped system and vendor from the image.
Downloaded xceed's modified MXC14G boot image. (Link)
Flashed system, vendor and xceeds boot via fastboot.
Rebooted into system and let it all update.
Finally rebooted into TWRP to reflash Xposed / Viper etc.
zezayer said:
Success: - Thanks for the tips.
Downloaded MXC14G vendor image from google. (Link)
Unzipped system and vendor from the image.
Downloaded xceed's modified MXC14G boot image. (Link)
Flashed system, vendor and xceeds boot via fastboot.
Rebooted into system and let it all update.
Finally rebooted into TWRP to reflash Xposed / Viper etc.
Click to expand...
Click to collapse
What version of Viper are you using? There seem to be various version out there now, which have been modified for specific devices. Please post a link to the one that you are using? Any issues with it?
SmokinCharger said:
What version of Viper are you using? There seem to be various version out there now, which have been modified for specific devices. Please post a link to the one that you are using? Any issues with it?
Click to expand...
Click to collapse
I'm using the Loliviper flashable zip. Working really well.
zezayer said:
I'm using the Loliviper flashable zip. Working really well.
Click to expand...
Click to collapse
Which specific version. I noticed that there are various loliviper versions that are device specific
I used the nexus 5 version which was recommended for the 6p and other nexus phones http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
Works well!
zezayer said:
I used the nexus 5 version which was recommended for the 6p and other nexus phones http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
Works well!
Click to expand...
Click to collapse
Thank you.
I'm a little lost on Root for the Pixel XL. I am currently running unlocked with Screw'd ROM - 3.1.2-****ery-20170712-1454. This is a BETA, but has been running really smooth for the last 2 days.
Security Patch Level - July 5, 2017
Vendor - NJH47D
Last time I tried to apply root while running PureNexus the phone continued to boot loop and I had to eventually flashall.bat and start over.
1. What version of SuperSU should I be flashing? The latest and newest or is there other versions that work better?
2. What are the correct steps? Is wipe cache/dalvik necessary before? Do I need to install anything on the phone beforehand?
Boot to TWRP, Flash SuperSU, Reboot? Easy as that?
I see this version being talked about a lot - SR3-SuperSU-v2.79-SR320170114223742.zip, but it isn't the latest available that I can see. The SuperSU thread states to install the latest version and using google brings me to many versions of SuperSU.
Lastly, after rooting will apps like SnapChat work? If not how to you bypass this?
So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?
jws86 said:
So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?
Click to expand...
Click to collapse
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.
sakumaxp said:
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.
Click to expand...
Click to collapse
Is there a guide to Root with Magisk somewhere floating around?
jws86 said:
Is there a guide to Root with Magisk somewhere floating around?
Click to expand...
Click to collapse
I believe it's the same as when you flash supersu, don't quote me on that
sakumaxp said:
I believe it's the same as when you flash supersu, don't quote me on that
Click to expand...
Click to collapse
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?
jws86 said:
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?
Click to expand...
Click to collapse
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet
sakumaxp said:
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet
Click to expand...
Click to collapse
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?
jws86 said:
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?
Click to expand...
Click to collapse
Myself I've never been on screwd before, I would assume so, but in my experience the pixel XL is more complicated than my previous phones
If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.
jhs39 said:
If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.
Click to expand...
Click to collapse
I think I got which versions of magisk and magisk manager I need to use from the other thread I had posted earlier. This helps to clear some things up for me though. I have both the .apk and the zip on my phone now. Getting a bit of a charge and I guess I'll go ahead and try it.
It worked, I'm officially rooted .Thanks for the help!
jws86 said:
It worked, I'm officially rooted .Thanks for the help!
Click to expand...
Click to collapse
Cool.
Hey, guys, I wanted to ask if someone tried OTA updates working with the new method of rooting released with magisk 14- a rooting method in which we do not need root or custom recovery beforehand, we just need to provide stock boot image dump to the magisk manager. This method will do us good because if OTA's still work after root we can be rooted on the stock roms without having to download full OTA's when a new update arrives. If someone can confirm working OTA's on the OOS open beta with this root method, it would be really helpful. Thank you!
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Puddi_Puddin said:
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Click to expand...
Click to collapse
Bro, I know how to work with TWRP. Your comment does not answer the question.
blaze95rs said:
Bro, I know how to work with TWRP. Your comment does not answer the question.
Click to expand...
Click to collapse
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Puddi_Puddin said:
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Click to expand...
Click to collapse
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
blaze95rs said:
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
Click to expand...
Click to collapse
See it for yourself! Its something most people do not recommend.
Puddi_Puddin said:
See it for yourself! Its something most people do not recommend.
Click to expand...
Click to collapse
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
blaze95rs said:
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
Click to expand...
Click to collapse
That doesn't matter. I get that it can be installed without a custom recovery. But that doesn't mean it won't conflict with possible ota's. Again, see it for yourself. Most people including me do rather play it the safe way.
I have recently updated to the lateset Oxygen OS Beta i had Magisk installed, i use Sparks Latest twrp version, with this you can install OTA updates. I dit not unlinstalled Magisk first, you do need the full rom file, but for me when i wanted to install the OTA, it found i had rooted and autmatacly downloaded the full rom. After you installed the update you can install the latest version of Magisk.
Just wondering. I have my bootloader for my Moto G Power (Sofia XT2041-4) unlocked and I'm trying to root my device but I can't install Magisk without it seems. So I would like to know if TWRP works with the Moto G Power (Sofia US).
FYI, you can install magisk without twrp by getting the boot image on your phone and using the magiskmanager app to patch that, then flashing it.
Twrp does work with sofia though. Just fastboot flash recovery twrp.img
You can find the latest compatible twrp image in this forum.
nero075 said:
FYI, you can install magisk without twrp by getting the boot image on your phone and using the magiskmanager app to patch that, then flashing it.
Twrp does work with sofia though. Just fastboot flash recovery twrp.img
You can find the latest compatible twrp image in this forum.
Click to expand...
Click to collapse
There needs to be a one stop shop for this sort of thing. All the help I'm getting is spread out and sources for the files we need spread out as well. This is the most frustrated I've been with Android rooting and I've been rooting for years.
nero075 said:
FYI, you can install magisk without twrp by getting the boot image on your phone and using the magiskmanager app to patch that, then flashing it.
Twrp does work with sofia though. Just fastboot flash recovery twrp.img
You can find the latest compatible twrp image in this forum.
Click to expand...
Click to collapse
Could you please point out on where could I read specific instructions (link) about how to root Moto G power sofia Android 11 (without TWRP, via Magisk) and / if flashing custom ROM on Android 11 could be successful. All I found online is instructions for Android 10. Many folks reporting that available test TWRP twrp-3.4.0-0-sofia-test9.img for sofia not working properly. Particularly, touchscreen not working. Any help would be appreciated.
Thanks.
alpheus said:
Could you please point out on where could I read specific instructions (link) about how to root Moto G power sofia Android 11 (without TWRP, via Magisk) and / if flashing custom ROM on Android 11 could be successful. All I found online is instructions for Android 10. Many folks reporting that available test TWRP twrp-3.4.0-0-sofia-test9.img for sofia not working properly. Particularly, touchscreen not working. Any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
I only did android 10, sorry.
Seeing a lot of issues with Android 11 and 12 unlocking the bootloader and applying root. Is now not a good time to upgrade or should I wait for a boot image?
Not quite sure what you're referring to, but there are zero issues with unlocking the bootloader or rooting your device...
I can't speak for TWRP. I have had issues with it the last few versions so I had to make due without it. If I am mistaken about having twrp on the OP9 Pro on the newest LE2125 c61 update, I'd be interested.
Anyway, my response is mostly to address your question regarding root. Here are the steps that worked for me.
[OnePlus 9 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
I have been rooted since day one on both A11 & A12. I'm running stock and haven't had a single issue.
Avoid TWRP, it's known to not work properly on A12
If you like to flash a custom ROM. Follow the instructions and you will be fine.
I am coming off the oneplus 7pro was enjoying TWRP and Magisk, with Exposed now I am hearing TWRP isn't working on anything above 10.0 ver. Guess I have to do so more research or pay Monfrio a ransom to work on TWRP.
intense21 said:
I am coming off the oneplus 7pro was enjoying TWRP and Magisk, with Exposed now I am hearing TWRP isn't working on anything above 10.0 ver. Guess I have to do so more research or pay Monfrio a ransom to work on TWRP.
Click to expand...
Click to collapse
there is no need for TWRP...
Smedslund said:
I have been rooted since day one on both A11 & A12. I'm running stock and haven't had a single issue.
Avoid TWRP, it's known to not work properly on A12
If you like to flash a custom ROM. Follow the instructions and you will be fine.
Click to expand...
Click to collapse
How do you root without twrp? or you mean to just boot twrp and not install it?
CtrlValCanc said:
How do you root without twrp? or you mean to just boot twrp and not install it?
Click to expand...
Click to collapse
Use Magisk, patch bootimg , install and reboot.
Read this usefull guide.
Smedslund said:
Use Magisk, patch bootimg , install and reboot.
Read this usefull guide.
Click to expand...
Click to collapse
thank you, i couldn't find what boot.img to download (and how), but this guide has already all!
CtrlValCanc said:
thank you, i couldn't find what boot.img to download (and how), but this guide has already all!
Click to expand...
Click to collapse
I always just sideload. (downdload magisk apk & rename to zip before)
this way you do not need the extra boot.img I think.
vincemue said:
I always just sideload. (downdload magisk apk & rename to zip before)
this way you do not need the extra boot.img I think.
Click to expand...
Click to collapse
could you explain better? I never used sideload before. What commands do you use?
CtrlValCanc said:
could you explain better? I never used sideload before. What commands do you use?
Click to expand...
Click to collapse
If you want to install any add-ons, Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB, then adb sideload filename.zip those packages in sequence. (GAPPS or Magisk for example)
for example for magisk:
download the newest magisk apk version
after download, rename it and instead of .apk do it .zip
go into revovery and click Apply Update, then Apply from ADB
command is : "adb sideload Magisk-v2X.X.zip"
you must exchange X for your version.
Boot images gets patched
please note that I am not an expert, that is just what I found somewhere and use since then.
if you need more information you could also check the install instructions for lineageOS to get to know some basics: https://wiki.lineageos.org/devices/lemonadep/install