1) Stock recovery. No it will no flash with twrp or cwm
2) All root removed completely from your system
3) Xposed framework completely removed from your system, uninstalling will not work,you need to flash the xposed Disabler zip
4) Any mods to any system file must be reverted to stock
5) Running the stock odex ROM
6) Any system apps frozen must be unfrozen
If you have at any point of time flashed any 4.4.2 firmware along with the boot loader 30.B3 or 30.B4
DO NOT FLASH THE OTA, YOU WILL HAVE A HARD BRICKED MOTO
HOPE THIS HELPS
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I was Following this from the General Forum. I've removed root(with superSu), but I can't boot into Recovery to flash the Xposed disabler zip; it just boots normally.
Okay, It seems like the PwnMyMoto Disabled recovery, so it could do the Disable Write Protect bug. How do i get that back to normal
Related
Hi, everyone:
I'm newbie of xPosed framware. My device is Nexus6 with 6.0.1 android installed. According the guide line of installing the xPosed framework, I flashed the TWRP recovery. Now my device works well with xPosed framework. But one issue is that after I receiving the Android system update, and pressing install, then my Nexus6 ran the system update and rebooted. But after my device rebooting, it still showed that I need to install the same Android system update patch. So it means the installation failed. I assume is it because of flashing TWRP recovery? Am I assumption correct?
Based on my assumption, I wonder can I roll back to the Android default recovery image? According this, can my device normally install the system update, or even the future OTA?
Thanks!
newcarcrazy said:
Hi, everyone:
I'm newbie of xPosed framware. My device is Nexus6 with 6.0.1 android installed. According the guide line of installing the xPosed framework, I flashed the TWRP recovery. Now my device works well with xPosed framework. But one issue is that after I receiving the Android system update, and pressing install, then my Nexus6 ran the system update and rebooted. But after my device rebooting, it still showed that I need to install the same Android system update patch. So it means the installation failed. I assume is it because of flashing TWRP recovery? Am I assumption correct?
Based on my assumption, I wonder can I roll back to the Android default recovery image? According this, can my device normally install the system update, or even the future OTA?
Thanks!
Click to expand...
Click to collapse
In order for OTA to work, you have to be completely stock unrooted.
Sent from my SPH-A120
Since you have a Nexus device, you can skip the OTA and just install the factory image from https://developers.google.com/android/nexus/images#shamu. However, you may want to flash the partitions individually instead of using the script so you don't have to redo TWRP and such.
Hi folks,
i hope i im the right Forum as it seams more a xposed as supersu problem.
I have a Moto X Style rooted with System-less SuperSU 2.78 and Xposed "xposed-v86.1-sdk23" by romracer, Stock ROM 6.0.
Just got a notification that there is a security update available, proceeded but won´t flash. Stops with Error Code 7.
I thought OTA would work with system-less.
Tried also with disable Xposed. Same result. By the way when the phone reboots for flashing it goes into The Recover TWRP 3.0.2 GUI. Anyway i saw the error when switching to the log view.
Any idea whats wrong or i miss?
May i have to restore custom recovery, and if so can i flash the stock recovery with the existing TWRP or do i have to go ADB?
Thanks
Thomas
You have to flash stock recovery image (and probably also boot image) for OTA to work.
Simply use fastboot to flash those. Leave system intact.
Thanks, will do so.
I want to switch from SuperSU 2.79 to Magisk. I tried the unrooting option in SuperSU but the phone doesnt boot, it stays on the google image. Reflashed SuperSU 2.79 and phone boots without a problem.
Then i booted into botloader and flashed the original stock boot.img from n6f27c factory image, but same result, phone stays at the google image and doesnt boot. Reflasing supersu 2.79 fixes the problem.
What would be the best way to move from supersu to magisk without having to completely wipe phone and flash n6f27c factory file.
Would flashing boot.img and system.img be enough? And then install magisk from twrp to get root again or is there another option that works.
TMG1961 said:
I want to switch from SuperSU 2.79 to Magisk. I tried the unrooting option in SuperSU but the phone doesnt boot, it stays on the google image. Reflashed SuperSU 2.79 and phone boots without a problem.
Then i booted into botloader and flashed the original stock boot.img from n6f27c factory image, but same result, phone stays at the google image and doesnt boot. Reflasing supersu 2.79 fixes the problem.
What would be the best way to move from supersu to magisk without having to completely wipe phone and flash n6f27c factory file.
Would flashing boot.img and system.img be enough? And then install magisk from twrp to get root again or is there another option that works.
Click to expand...
Click to collapse
Try using unsu.zip. You can find it in osm0sis' odds and ends thread. Scroll down through the first post.
ktmom said:
Try using unsu.zip. You can find it in osm0sis' odds and ends thread. Scroll down through the first post.
Click to expand...
Click to collapse
Thanks, that did the trick. Rooted with Magisk now.
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Akash731 said:
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Click to expand...
Click to collapse
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Akash731 said:
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Click to expand...
Click to collapse
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
pradeeppk said:
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
Click to expand...
Click to collapse
I don't want to try custom rom's as this is my main device guess I'm stuck with the encryption then thanks for your help. :good:
Edit:-
Tried TWRP r20 it decrypts fine thanks
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
gewe said:
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
Click to expand...
Click to collapse
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
I am using stock ROM, and yes, also Magisk (installed later). IIRC Magisk is not needed for TWRP to work. When I receive the next OTA notification, I will test this.
The thread you are referring to is for a OnePlus 3T. For our device this is the thread: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910.
Since there is no official TWRP for the Moto G5S Plus, I took the following text from the TWRP page for the Moto G5S.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Instead of that you can also use fastboot reboot-bootloader, and then from the bootloader start recovery.
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
gewe said:
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
Click to expand...
Click to collapse
As like you said this is the first time in my life i need to flash magisk to stick twrp.
I usualy doesn't use root or custom roms, install twrp, remove unnecessary apps from stock system, replace host files with adaway hosts, replace or edit gps config files. and continue using stock.
This is the main routine from Android 1.5
(Samsung spica (i think it was the first Android phone from Samsung)).
It may be due to security reason stock kernel or system delete twrp.
When installing magisk it patch stock boot image, that may be the reason of twrp remains after flashing magisk.
Received an update today , if i use standart ota updater via settings, does it overwrite the twrp and root stuff i have or it wont? Coz i never done this before, always using custom roms and now latest stock miui 11 with root.
You could flash the zip rom through the recovery, but keep in mind this. Let the phone boot with the new update, then go back to recovery (if you get the stock recovery, reflash it with fastboot), then flash magisk
So it is overwriting twrp and magisk even if i install it directly from twrp?
meezy5 said:
Received an update today , if i use standart ota updater via settings, does it overwrite the twrp and root stuff i have or it wont? Coz i never done this before, always using custom roms and now latest stock miui 11 with root.
Click to expand...
Click to collapse
You will loose Magisk/root but not Magisk Manager app and all Magisk data like modules, apps granted root, etc - once you re-root, everything will be there again.
I only suggest that you first un-hide Magisk Manager (if hidden for you), at the end you can hide it again
If you update via OTA, you will loose TWRP. If you don't want to flash TWRP again, then download the same full MIUI 12 zip package you got OTA notification for, and flash it from TWRP (without wiping, formatting or so), and immediately thereafter reboot first back to TWRP, and only then to MIUI 12
If you would like to update truly by OTA, you would have to flash the stock recovery back before starting the OTA.
Hence the way as described above, you save first on flashing stock recovery, and later on flashing TWRP back
Ok thanks so after twrp flash i have to reboot back to twrp , do i have to install force encrypt then to prevent overwriting twrp by miui or not?
meezy5 said:
Ok thanks so after twrp flash i have to reboot back to twrp , do i have to install force encrypt then to prevent overwriting twrp by miui or not?
Click to expand...
Click to collapse
See posts #933, #935-#937 in the TWRP thread:
https://forum.xda-developers.com/showpost.php?p=82945031&postcount=936