Related
Hi all! I'm new here (at least at account level) and with my first thread I want to help people which can't flash 6.0+ roms in official 2.8.x TWRP for our Moto X 2013 (like @dziarski in TWRP 2.8.7.0 thread).
I have Moto X 2013 (XT1052 model for reference) and I unlock bootloader, root and put costum roms not so long ago but here out to resolve this.
You need to upgrade your TWRP because TWRP <3.x don't support 6.0+ rom flashing well (edit: mochi579 below report twrp 2.8.7.0 can work for flashing too even I recommend latest 3.0.x version for avoid all problem especially with 7.x roms). I advice you to check out unofficial TWRP 3.0.2-0 by fantastic TeamMEX here.
This updated version grant you to flash both 6.0+ and 7.0 roms (tested myself) without any error.
There are my ROMs test to try this TWRP:
Legenda: (Android version)
TWRP 2.8.6.0 official:
Resurrection Remix 5.7.4 (6.0.1) -> failed immediately with this error
Code:
E: Error executing updater binary in zip "/..."
Error flashing zip "/..."
After some research I understood I need to updated my TWRP and here's the result
TWRP unofficial 3.0.2-0 by @TeamMex:
RR 5.7.4 (6.0.1) again -> succes without problem (I use right now)
CM13 (6.0.1) -> succes
CM14 (7.0) -> succes
OctOS Oct-M (6.0.1) -> succes
Xperience 11.0.0_rxx (7.0) -> succes
All succes without any error during flashing.
Just in case I want to add my step even its very common:
1) Make a NANDroid backup if I don't have it already
2) Wipe Cache, Data, System, ART/Dalvick cache
3) Optional factory reset (cache,art/dalvik and data)
4) Flashing ROM + Gapps from OpenGapps (remember to select ARM)
5) Reboot and finish
If there's a problem in the post or its wrong place (its here or Q&A) please let me know
Thank you WOrld1. But I'm flashing cm13, cm 14 & xpe 11 using TWRP 2.8.7.0 and it's working perfect except some known bugs.
mochi579 said:
Thank you WOrld1. But I'm flashing cm13, cm 14 & xpe 11 using TWRP 2.8.7.0 and it's working perfect except some known bugs.
Click to expand...
Click to collapse
Hi,
I was using 2.8.6.0 because in the root thread by Kidjoe here in General he write about a possible read error about SD card in the phone (clearly a bug because we don't have it xD), so my experience with 2.8.7.0 is zero unfortunately but I think it's very similar.
I have zero problem flashing the rom I listed, for various reason some mod I flashing more than one time (never because flashing problem, usually rom itself problem or just jumping back and forth).
I flash xperience 2 times, cm13/14 and OctOS one time and Resurrection Remix many times if we include backup when coming back from these ROMs.
The only know bug I experienced in 3.0.2-0 is slow flashing in "normal" condition. Just follow the note in the op of recovery thread:
Code:
NOTE: If you have slow format on ext4 go to Settings->Use rm -rf instead of formatting
Copy pasted from TeamMEX thread.
I tried all methods which are there on site but each time same and only problem is coming that is my phone is not getting rooted correctly I tried so many times but when I'll check with root checker it says it's not rooted but I successfully unlocked bootloader but I can't complely root it, can someone help me?
What device do you have and what ROM are you running?
If you're rooting on the stock Motorola ROM, do you have TWRP flashed/booted, then flashed ElementalX? Afterwards, what root managers are you using? You could try magisk 16 or 15.3. However, if you've previously used SuperSU or another root manager, you may have to re-flash the original stock kernel (then flash ElementalX then root) to remove any remainders of the old root managers, else they may interfere with magisk to the point of the root not being stable.
I have Moto g4 plus XT 1643 and I tried to root with by using twrp latest version and lineage os 14.1 athene. The was working fine but my phone is still showing that this device is not rooted
MsK96918 said:
I have Moto g4 plus XT 1643 and I tried to root with by using twrp latest version and lineage os 14.1 athene. The was working fine but my phone is still showing that this device is not rooted
Click to expand...
Click to collapse
What root manager are you using? The official Lineage OS (as of Jan 2017) does not come with a root manager, you must download and flash your own. You could either use the Lineage_SU_addon (you'd want the arm variant for 14.1) or magisk or SuperSU as a root manager.
I am new in this so I don't know that much details so can you help me by giving me link so that I can go through step by step and try to do what you are saying
MsK96918 said:
I am new in this so I don't know that much details so can you help me by giving me link so that I can go through step by step and try to do what you are saying
Click to expand...
Click to collapse
1)Download the Lineage SU addon (from here https://download.lineageos.org/extras - you want the arm 14.1 zip) OR magisk (from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 ) Only download one, please and if you want to switch, you ideally want to restore your backup or dirty flash the custom ROM to restore the Lineage kernel.
2)Reboot your device to TWRP.
3)In TWRP backup your device. Keep this backup safe.
4)In TWRP, go to 'Install' and flash the package you downloaded.
5)Wipe cache and Dalvik in TWRP after the flash.
6)Reboot.
7)Verify you have root.
You may also wish to browse the Lineage 14.1 thread for our device here: https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101 Please use the search function by the page numbers to quickly search the thread for information
echo92 said:
1)Download the Lineage SU addon (from here https://download.lineageos.org/extras - you want the arm 14.1 zip) OR magisk (from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 ) Only download one, please and if you want to switch, you ideally want to restore your backup or dirty flash the custom ROM to restore the Lineage kernel.
2)Reboot your device to TWRP.
3)In TWRP backup your device. Keep this backup safe.
4)In TWRP, go to 'Install' and flash the package you downloaded.
5)Wipe cache and Dalvik in TWRP after the flash.
6)Reboot.
7)Verify you have root.
You may also wish to browse the Lineage 14.1 thread for our device here: https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101 Please use the search function by the page numbers to quickly search the thread for information
Click to expand...
Click to collapse
Thank you bro i finally rooted my device correctly . It help alot thank you once again
Hi I'm new to XDA Forums, I was searching for posts about rooting my Moto g4 Plus. I would like to know Why we should flash a kernel before flashing SuperSU or Magisk ? Nb: I just only want the root access. Not in a plan to flash a custom rom. Thanks in Advance.
vinayroffl said:
Hi I'm new to XDA Forums, I was searching for posts about rooting my Moto g4 Plus. I would like to know Why we should flash a kernel before flashing SuperSU or Magisk ? Nb: I just only want the root access. Not in a plan to flash a custom rom. Thanks in Advance.
Click to expand...
Click to collapse
The stock Motorola kernel in stock Nougat ROMs appears to have anti rooting measures included (I think DM Verity?) If you attempt to root on this stock Nougat kernel, you'll likely soft brick/bootloop your device.
A custom kernel (e.g. elementalX v2.0.1 for stock) does not have these anti rooting defences, so it's safer to root with magisk. I would recommend magisk as super SU hasn't been updated in some time.
It appears that this need to flash a custom kernel before rooting applies to Nougat stock ROMs; marshmallow stock ROMs and the Oreo soak test stock ROM appear not to require a custom kernel.
As an aside, custom kernels and root are not necessary to flash custom ROMs. The only tools you require are an unlocked bootloader and the correct TWRP. The kernels included with these custom ROMs may also have anti rooting measures disabled, so it's safer to directly root without having to use a custom kernel.
Hi Everybody,
did one of you manage to get Magisk running on your 1380F?
I'm on latest Firmware / ROM and rooted by temporary booting CWM and flashing SuperSU, like in the tutorials over here.
If I flash Magisk, no matter if pre-rooted or not, via Magisk Manager or CWM --> The tablet recognises that the boot image was manipulated, doesn't boot anymore.
It jumps directly to the stock recovery...
Any ideas?
Thanks in Advance,
McK
How did you go about flashing via the temp cwm? I'm trying to flash the stock from but cant find a recovery for this lenovo 1380F. I tried using the tetherd temp cwm and selected T3, it appears to run fine with no errors but I don't see the recovery menu on the device
Dear everyone:
I am a new member of the xda community, First of all please forgive me for my English level and this stupid question ,I have a question about root Redmi 7A. We are known Redmi 7A used asr 32-bit , maybe that's why it's difficult to ROOT it? On the Xiaomi website , I can not find a Developement Developer ROM of the Redmi 7A. if have then I can flash it to get Root privilage. I have tried genneral way to root it , but all failed.
firstly , my Redmi 7A is unlock (bootloader) and I have flashed TWRP (WRP-3.3.1-1003-REDMI7A-CN-wzsx150.img) and Global ROM 10.2.5 (download from https://mirom.ezbox.idv.tw/en/phone/pine/roms-global-stable/#info_18104 )， then installed Magisk manager. then I use patched boot.img method, or I flash magisk use install zip from TWRP method , the phone can boot normally, but magisk manager claims that magisk is not installed. yes, my problem is the same as this post https://forum.xda-developers.com/redmi-7a/help/unable-to-root-redmi-7a-miui-11-0-6-t4011525
However, I did not understand how he ended up being successful, Do I need to download a specific patched magisk_patch.img? Therefore, I think I need a more detailed tutorial.
All help would be greatly appreciated !
In addition, I still have a question, which domain does magisk access when updating and pathing? Because in China, this domain may not be accessible. I need to enable the VPN service to update or patch normally.
Try mokee ROM, with add on su
xsstest said:
Dear everyone:
I am a new member of the xda community, First of all please forgive me for my English level and this stupid question ,I have a question about root Redmi 7A. We are known Redmi 7A used asr 32-bit , maybe that's why it's difficult to ROOT it? On the Xiaomi website , I can not find a Developement Developer ROM of the Redmi 7A. if have then I can flash it to get Root privilage. I have tried genneral way to root it , but all failed.
firstly , my Redmi 7A is unlock (bootloader) and I have flashed TWRP (WRP-3.3.1-1003-REDMI7A-CN-wzsx150.img) and Global ROM 10.2.5 (download from https://mirom.ezbox.idv.tw/en/phone/pine/roms-global-stable/#info_18104 )， then installed Magisk manager. then I use patched boot.img method, or I flash magisk use install zip from TWRP method , the phone can boot normally, but magisk manager claims that magisk is not installed. yes, my problem is the same as this post https://forum.xda-developers.com/redmi-7a/help/unable-to-root-redmi-7a-miui-11-0-6-t4011525
However, I did not understand how he ended up being successful, Do I need to download a specific patched magisk_patch.img? Therefore, I think I need a more detailed tutorial.
All help would be greatly appreciated !
In addition, I still have a question, which domain does magisk access when updating and pathing? Because in China, this domain may not be accessible. I need to enable the VPN service to update or patch normally.
Click to expand...
Click to collapse
Add-on-su on mokee open source ROM works fine, can enable root from developer options only, magisk and supersu don't work.
I have been trying to make them work but it seems impossible, I have looked in system/xbin and found no su files, maybe the problem is in the meta-INF because it doesn't properly know where to install it.
Hi,
I have a Xiaomi Mi 9T Pro Global with :
- Bootloader unlocked
- TWRP v3.3.1-0 (lastest)
- Magisk Manager v7.5.1 (lastest)
- Magisk v20.4 (lastest)
So I am rooted and want to keep it (with my data). ^^
Problem: I am still on MIUI v10.3.3.0 and can't install OTA because it makes me reboot on TWRP
I found some different posts like :
Link: https://www.the***********.com/install-ota-update-rooted-android-device-guide/
-> It doesn't work for me because I don't have the A/B partition (message from Magisk when I tried to flash it) and I don't have the "Install to Inactive Slot (After OTA)" option...
Link: https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
-> I don't know if I have to do it, and when? (if needed, I have the boot.img of my current Global v10.3.3.0)
It seem I have to restore my stock recovery?
-> I see how to do it from TWRP, but I don't have the recovery.img file
How can I install OTA without lose my root and my data?
Thank you in advance,
Best regards.
ptit developer said:
Hi,
I have a Xiaomi Mi 9T Pro Global with :
- Bootloader unlocked
- TWRP v3.3.1-0 (lastest)
- Magisk Manager v7.5.1 (lastest)
- Magisk v20.4 (lastest)
So I am rooted and want to keep it (with my data). ^^
Problem: I am still on MIUI v10.3.3.0 and can't install OTA because it makes me reboot on TWRP
I found some different posts like :
Link: https://www.the***********.com/install-ota-update-rooted-android-device-guide/
-> It doesn't work for me because I don't have the A/B partition (message from Magisk when I tried to flash it) and I don't have the "Install to Inactive Slot (After OTA)" option...
Link: https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
-> I don't know if I have to do it, and when? (if needed, I have the boot.img of my current Global v10.3.3.0)
It seem I have to restore my stock recovery?
-> I see how to do it from TWRP, but I don't have the recovery.img file
How can I install OTA without lose my root and my data?
Thank you in advance,
Best regards.
Click to expand...
Click to collapse
You can keep TWRP and Magisk module, you will only need to patch the boot image and install it from TWRP to regain root after the OTA
- Download full Recovery/zip package 2.4 GB for your MI/IN/EU/RU you currently have with MIUI 10
- Flash that zip from TWRP (Install, zip)
- Reboot to TWRP, not to Android, otherwise you will loose TWRP
- Backup Boot in TWRP
- Reboot to Android. You shouldn't have lost your apps and settings. Magisk Manager will be there but no root
- From Magisk Manager take Install, keep Preserve AVB and Preserve Encryption (first two) but UNCHECK Recovery mode
- Choose to Patch image and navigate to the Boot backup you just made in TWRP, boot.emmc.win, 128 MB
- Reboot to TWRP, take Install, Image (not zip) and navigate to magisk_patched.img in Download
- Upon installing keep in TWRP and Wipe Dalwik and Cache, ONlY
-Reboot to Android - you will have root, your previous modules, rooted apps, all
PS: Doing OTA from System Update requires stock Recovery - that's why it reboots for you to TWRP and fails.
To be able to do OTA that way, you would need to first flash back your stock Recovery.
Then OTA update will fail and you wouldl have to force Full OTA.
At the end, you would also loose root - hence the above procedure is simpler, you even don't need PC, you will keep TWRP and you will only need to patch and install the patched boot image to regain root
Hi and thank you @zgfg,
So if I correctly understand, to be able to make OTA without losing my data and restore root, I have to :
1. Install stock ROM
-> When I did it on previous phone, I always lose everything, so are you sure?
2. Restart in TWRP (to not lose it)
3. Backup boot via TWRP
4. Go in Magisk Manager, and check "keep Preserve AVB" and "Preserve Encryption", but uncheck "Recovery mode"
5. Click on "Install" and choose "Patch image", then selected the boot image previous made with TWRP
6. Reboot in TWRP to install (image, not zip) this file created in the 5.
7. Wipe Dalvik and Cache
8. Enjoy
I found the following link on mi.com to allow me to download the Global v10.3.3.0 (zip and tar.gz) :
Link: https://c.mi.com/thread-2459743-1-0.html
Is it the good one?
Can I simply extract the boot.img of the file downloaded in the 1. and go directly to the 4. ?
Thank you in advance,
Best regards.
ptit developer said:
Hi and thank you @zgfg,
So if I correctly understand, to be able to make OTA without losing my data and restore root, I have to :
1. Install stock ROM
-> When I did it on previous phone, I always lose everything, so are you sure?
2. Restart in TWRP (to not lose it)
3. Backup boot via TWRP
4. Go in Magisk Manager, and check "keep Preserve AVB" and "Preserve Encryption", but uncheck "Recovery mode"
5. Click on "Install" and choose "Patch image", then selected the boot image previous made with TWRP
6. Reboot in TWRP to install (image, not zip) this file created in the 5.
7. Wipe Dalvik and Cache
8. Enjoy
I found the following link on mi.com to allow me to download the Global v10.3.3.0 (zip and tar.gz) :
Link: https://c.mi.com/thread-2459743-1-0.html
Is it the good one?
Can I simply extract the boot.img of the file downloaded in the 1. and go directly to the 4. ?
Thank you in advance,
Best regards.
Click to expand...
Click to collapse
In the first post you said that you already have v10.3.3.0 and that you want to update
Hence why would you now download v10.3.3.0 - you should download v11 (supposidely), that the same newer version that OTA offers you
Yes, you can extract boot.img from that newer MIUI (v11) that you will download and flash but that requires PC - in my instructions you simply use TWRP and make backup of the boot image upon you do update
By extracting boot.img from v11 you will not save any step, you still must flash its zip (not tgz) from TWRP and you must nevertheless reboot to TWRP first
---
By flashing OTA zip (full, 2.4 GB) from TWRP, you should not loose your data and apps. I did it with Mi 9T (not PRO - you are not on the PRO forum) but things must work the same way for PRO for Global or EU (you must update to the same Global, EU, Indian, Russian as you already have, just fownload the same newer version that OTA offers you)
Hi back,
Yes, I am in Global (EU) v10.3.3.0 and I should want to use OTA (first I have, it is to go on v10.3.4.0, and I guess, I will have more after until v11).
So I can use directly v11 one?
Thank you in advance,
Best regards.
ptit developer said:
Hi back,
Yes, I am in Global (EU) v10.3.3.0 and I should want to use OTA (first I have, it is to go on v10.3.4.0, and I guess, I will have more after until v11).
So I can use directly v11 one?
Thank you in advance,
Best regards.
Click to expand...
Click to collapse
Better follow what OTA gives you. Find and download Recovery/zip for that Global v10.3.4.0 and install as suggested.
Later similarly follow the version numbers the same way as they come by OTA