Hi,
I recently tried to install audio_hq magisk module, but i tried SE enforce. Now my phones boots for ages, then says that the android system is corrupt and that i should factory reset the phone or try again. However, I’d like to not lose my app data and the settings i spent a while tuning. I have access to fastboot, bootloader is unlocked, phone is rooted. I heard something about installing twrp and fixing perms (if that’s the problem) or using adb to modify the module file to disable SE, but i cannot find twrp for my phone. I have LiveBoot if a picture of the logs is needed or something
How can i fix this without losing my data ?
CSAE
Related
I have been trying to root Motorola Moto E XT1023 which comes with a standard stock Android 4.4.4 KitKat.
I have tried many ways. I have been able to unlock the boot loader and able to copy and paste various variations of the SuperSU zip file to the root directory of the phone and to unzip this file with TWRP recovery and or with CWM recovery ( have not tried stock recovery yet but I am not sure whether I have 4.4.4.KitKat stock recovery image ).
Anyway, the zip file unzips and gives all standard messages as per the YouTube videos. I have noticed, in some installation, when the SuperSU got unzippes, there is a missing line : " SETTING PERMISSIONS ". I have also noticed the " PARTITION MISMATCH " message when TWRP recovery is written. However, I have seen people also having this on YouTube and their devices rooted perfectly.
I guess, the final goal of the rooting process is to install SuperSU which I have done in many different ways and many different versions. Regardless, although SuperSU installation says " SUCCESS ", I DO NOT HAVE THE SU ICON IN THE GENERAL APP LIST AND VARIOUS ROOT CHECKERS REPORT THE CELLPHONE HAS NOT BEEN ROOTED.
I WONDER WHETHER THERE IS SOMETHING ELSE I HAVE TO DO TO SETUP THE SUPERSU AFTER UNZIPPED. OR DO I USE WRONG VERSIONS. WHICH IS THE CORRECT VERSION? which IS THE CORRECT TWRP VERSION?
I have also tried to use the popular batch installers ( version 2 and 3 ). The same result.
I have also tried to use mfastboot V 2 for everything. Also tried the general purpose fastboot for everything. The same result.
I have not slept for 2 nights because of thie problem with the inability to root the cellphone, something which normal people with normal Moto E XT1023 do on YouTube for less than 30 minutes.
PLEASE, HELP!
Hi there,
All you need is in this thread: [SCRIPT] Moto E XT1023 super easy ROOT, RECOVERY, & RESTORE
For more questions related to your device please ask directly here: Motorola Moto E Help and Troubleshooting
Good luck
Problem solved!
PROBLEM SOLVED!
USED THE BATCH SUPER UTILITY V 3. I THINK WHAT HAVE HELPED WAS TO DO A FACTORY RESET AFTER THE TWRP REBOOT. FACTORY RESET REBOOTS AFTER PREPARING THE SYSTEM. THE TWRP REBOOT DID NOT DO MUCH BUT THE REBOOT OF THE FACTORY RESET THEREAFTER DID. TWRP DID SHOW UP AFTER THE FACTORY RESET REBOOT AND INSTALLED SOMETHING.
I have tried to install XDA and some XDA APK before rooting. I have also had the Motorola protection and tracking enebled. I am not sure whether these have created the problem.
Here is what I have done to root the device :
ON THE PC :
UNINSTALLED MALWAREBYTES TO REINSTALL AFTER.
STOPPED WINDOWS DEFENDER REAL PROTECTION TO START AFTER.
KINGO ROOT DID NOT WORK.
ON THE CELLULAR TELEPHONE :
Did not remove the SIM card and signed in normally after the factory reboot. Rmoving the SIM card and not logging in after factory reset may help.
UNINSTALLED CLEAN MASTER ANTIVIRUS AND THE WHOLE PACKAGE, BATTERY DOCTOR, ES, A COUPLE OF COMMAND SHELL PROGRAMS, ALIEXPRESS, EBAY, ADOBE, SWIFT KEYBOARD, ETCETERA, SOME MAINLY STARTUP PROGRAMS.
DISABLED INFORM MOTOROLA IN TWO PLACES OF SETTINGS.
AFTER THE BATCH, TWRP AND INSTRUCTIONS, DID FACTORY RESET WITH DISCONNECTED USB CABLE.
THE FACTORY RESET REBOOTED AND THE TWRP DID SOME JOBE DURING REBOOT.
AFTER THE FACTORY RESET REBOOT, SU ICON WAS IN THE APP LIST AND WORKED. THE DEVICE WAS ROOTED.
DISABLED THE AUTOMATICALLY STARTED UPDATES AFTER THE FACTORY REBOOT RESET TO REENABLE THEM AND INSTALL THEM AFTER.
CHECKED WITH 4 ROOT CHECKERS. ALL REPORTED THE DEVICE WAS ROOTED OK.
StevenStanleyBayes said:
PROBLEM SOLVED!
Click to expand...
Click to collapse
Glad to hear that.
Thread closed.
I have Xperia XZ running XZ_eXistenZ_Oreo_v8.0.0_patch_F883x_41.3.A.2.192. I have TWRP recovery on it. I flashed DRM, Safety net, Magisk 16.3, Magisk SE Linux Manager on it. Whenever I try connecting to the internet with magisk it crashes. Without connecting to the internet it works, but thats not really a fix, just a work around and even then the applications still do not work. however I noticed when I took Existence superuser rights off, it no longer crashed. This is not the main problem I am facing. I tried reading off of this website Look, I have flashed, re-flashed, done the advanced wipe, mounted data, wiped dalvik, cache. Am I missing a certain step that somebody could clue me into that perhaps I might be missing? Someone out there has solved it. Im new to magisk. I used to use SUPERSU but that was on an old phone that I cant remember the name of LONG ago. Where might I find the logs, I can post those and we can start getting somewhere
The module that did this was "liboemcrypto disabler" and was advertised as allowing DRM content to be viewed in full HD despite my bootloader being unlocked. It immediately put me in a boot loop after installing. I removed the magisk module from recovery but I was stuck in a boot loopstill and ended up having to wipe. I've done a full wipe, I've fully erased and decrypted the phone with ALL IN ONE tool and then installed a new stock ROM via fastboot. I then used TWRP to wipe EVERYTHING and then used ALL IN ONE TOOL to erase the phone and then used MSM tools to reflash a stock ROM and start from scratch while also choosing to wipe all data in the process. Netflix not working has persisted through all of this, it seems this module has touched a drm file that is normally out of reach in the wiping process / it's not replaced when doing a clean install. Another odd thing is that throughout this whole process, Nova Launcher stayed installed throughout all of the wipes. Any time I try to open Netflix it either says I need to update and clicking okay brings me to the play store where it tells me Netflix is not compatible on my device. Sometimes I get other error messages but it's always the same, Netflix doesn't work. The odd thing is I got it working on Pie in the process of unlocking my tmobile bootloader with the Android 10 DP3 so I could root it. Netflix actually worked for a second while I was on Pie, up until I updated to Android 10. This leads me to believe that the drm Android 10 is using is different from Pie and upgrading put me back to relying on the ruined drm file. I've even tried installing and uninstalling the magisk module that screwed all of this up hoping it would replace the original drm file but I've had no luck. This is such an odd problem. I had no clue any magisk module had the power to give your phone problems that literally can't be fixed through full wipes and reinstalls. I've tried removing netflix from ADB and reinstalling the apk manually but there's still no luck. The other streaming services that normally rely on this DRM are fine. If anyone has the slightest idea of what to do here I'd love to hear it! Are all drm files the same for everyone? If I were to aquire the drm file that was replaced while installing this thing could that possibly fix it? The file that is modified is under /vendor/lib/ and is named "liboemcrypto.so"
Hi everyone,
I hope some of you are still following up on this device or maybe my query is not too specific after all...
To give you some background: When I rooted my Zenfone 3 Ultra in April 2019 the storage was encrypted such that I had to enter a key each time I powered it up. After ~ 1 year or so I could not access the OS anymore after a reboot because it said the key I entered was wrong. So I went to twrp and did a wipe in order to set everything up again, this time not using device encryption. I noticed that after this wipe the flash light and third party apps using the camera would cause crashes (black screen or immediate reboot). I could live with it so far but recently I thought more and more often that it would be nice to finally use the camera in third party apps. So yesterday I had some time and decided to address the issue by doing a factory reset.
Now the factory reset did not resolve the issue. I remembered that when I had rooted the device (and everything was still working) I had created a nandroid backup in twrp which I then restored. I included everything in the restore which was offerd by twrp, i.e. Boot, Data (excl. storage), System and System Image. Still the same issue. I am not sure anymore if I created the one nandroid backup which I still have before or after rooting but when I boot up the device and install Magisk Manager, Magisk is shown with the version I installed back then.
According to the ZU680KL unlock/root thread unlocking is not possible anymore. However, I would like to keep root / be able to regain it. I assume the latest firmware (UL-ASUS_A001-WW-14.1010.1804.75-user.zip) as well as the corresponding boot.img and recovery.img which @ndi provided in this thread (thanks!) would allow me to go back further. However, I noticed that in my boot menu it says "DEVICE STATE - locked", which already makes me kind of nervous due to the unlocking issue above. I just don't want to try anything else on my own because I am afraid to do something foolish. So maybe you can help me with these two questions:
With everything being as it is, how could I start as clean as possible without loosing root / the ability to root again?
If I was willing to sacrifice root access, how could I proceed to bring everything back to stock?
Or maybe you have some other idea to fix the camera issue. Any help will be appreciated.
Many thanks!
Hello again everyone,
I decided to move on and go back to stock. Eventhough I was not able to maintain/regain root, there is an approach that might be applicable to our device as well. Also, I would like to share what I found out regarding my initial goals (i.e. camera issues and resetting a rooted device).
Camera issues: It seems to me that these appear on (some?) ZU680KL devices running Android 7 (Nougat). They can affect the flashlight or the camera in general, as you can read here. I decided to go back to the latest Android 6 (Marshmallow) realease as suggested in the same thread. The system no longer crashes when I use the flashlight or the camera is used by a third party app. However I sometimes still need to start the camera app in order to make it work in third party apps.
Going back to stock: A guide for the Zenfone 3 siblings can be found here. I went back to stock using TWRP and a MicroSD card (with boot.img, recovery.img and ROM zip file):
I first flashed the boot and recovery (i.e. TWRP) partition with the stock images for the ROM I was planning to flash.
Then I booted into stock recovery and flashed the ROM zip file. The key combination to get into stock recovery was a little weird ('volume -' followed by 'volume +' while keeping 'power' pressed). It had to be entered during the 'no command' notification that was shown after choosing recovery from the fastboot menu.
After successfully flashing the ROM, I wiped cache and data and rebooted. I ran into a "Dm-Verity in EIO mode" error (see attached). This error had already occured after my last try to restore a nandroid backup in TWRP but I could resolve it with the steps described in this youtube video and repeated (2.). When I think about it now I guess I should have started with (3.) right away because of the Dm-Verity issue.
Regaining root: I think this is something yet to be done but it does not seem completely hopeless.
I hope this can be of help if you face any of these issues.
Hello,
About two months ago I successfully rooted that phone through Magisk. Now I am facing the told problem. I searched for some problems like mine, but it is not because of updates. I do not remember I have done something dangerous for the system. However, I tried to install this package. When I tried with the Android package installer, I got an error "it could not be installed". Then I tried to do it through this app manager for rooted devices, and it just stayed loading for a while until I just closed it. I entered the custom app manager and I realized that the app was recognized as an installed app, but however, I could not see it in the poco app launcher. I launched the app and it worked fine, but when tried to make f-droid a system app it displayed an error "/ directory could not be remounted as read-write". I left it be and removed that app. Everything fine... But the next morning the phone was asking for the SIM unlocking code. I unlocked both, the SIM and the phone, but after about five minutes it rebooted to MIUI recovery 5.0. If once in recovery mode the phone is inactive for a while, it automatically reboots to system. The rebooting time once unlocked the SIM was decreasing to two minutes. Apparently, it only will reboot if the SIM is unlocked, and the time is five minutes when the phone is cold and it decreases as it is being restarted. The phone it is not too hot when rebooted.
Thank you if you spent your time by reading the text above. Now the question: How can I fix it without losing my data? Regards.
PD: I do not have enough time to make a backup till it is rebooted, at least from system, and safe mode did not solve the issue.
You tried to install an obsolete app for moving apps to system, an app from 2016... no less?! What were you thinking?
Let me be honest and tell you that that move was extremely stupid. Chalk up your mistake to a brain fart, take the loss and try to reflash the firmware without formatting anything prior to doing so. Leave internal storage, dalvik, cache and everything else untouched. You just might make the phone bootable to backup your data, and then do a PROPER flash procedure.
Tomo123 said:
You tried to install an obsolete app for moving apps to system, an app from 2016... no less?! What were you thinking?
Let me be honest and tell you that that move was extremely stupid. Chalk up your mistake to a brain fart, take the loss and try to reflash the firmware without formatting anything prior to doing so. Leave internal storage, dalvik, cache and everything else untouched. You just might make the phone bootable to backup your data, and then do a PROPER flash procedure.
Click to expand...
Click to collapse
So therefore, which partition should I reflash with the stock ROM?
MxtApps said:
Hello,
About two months ago I successfully rooted that phone through Magisk. Now I am facing the told problem. I searched for some problems like mine, but it is not because of updates. I do not remember I have done something dangerous for the system. However, I tried to install this package. When I tried with the Android package installer, I got an error "it could not be installed". Then I tried to do it through this app manager for rooted devices, and it just stayed loading for a while until I just closed it. I entered the custom app manager and I realized that the app was recognized as an installed app, but however, I could not see it in the poco app launcher. I launched the app and it worked fine, but when tried to make f-droid a system app it displayed an error "/ directory could not be remounted as read-write". I left it be and removed that app. Everything fine... But the next morning the phone was asking for the SIM unlocking code. I unlocked both, the SIM and the phone, but after about five minutes it rebooted to MIUI recovery 5.0. If once in recovery mode the phone is inactive for a while, it automatically reboots to system. The rebooting time once unlocked the SIM was decreasing to two minutes. Apparently, it only will reboot if the SIM is unlocked, and the time is five minutes when the phone is cold and it decreases as it is being restarted. The phone it is not too hot when rebooted.
Thank you if you spent your time by reading the text above. Now the question: How can I fix it without losing my data? Regards.
PD: I do not have enough time to make a backup till it is rebooted, at least from system, and safe mode did not solve the issue.
Click to expand...
Click to collapse
flash the stock firmware with miflashtool and select de option "save_user_data" and done, the firmware will be flashed and your data will stay there
tutibreaker said:
flash the stock firmware with miflashtool and select de option "save_user_data" and done, the firmware will be flashed and your data will stay there
Click to expand...
Click to collapse
OK, that flash was successful, the root and the custom recovery were lost, but it is still rebooting. Should I flash all?
MxtApps said:
OK, that flash was successful, the root and the custom recovery were lost, but it is still rebooting. Should I flash all?
Click to expand...
Click to collapse
if you flash all your data will be lost, any way to install custom recovery and save your data from it ?