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.
Related
New to the G2 world, unit just came in yesterday, rooted with stump root brute force. Worked well, got busybox, flashify, sqlite, and tibu all working. Tried to flash twrp 2.8.5.0 in flashify and think I fubared my recovery. When I try to boot into recovery using quickboot, I get white text up top
ERROR: boot certification verify
Secure boot failure
Then screen quickly goes black, from there I can hold power button and reboot, only issue when booting phone, upon unlock I get com.google.process.location has stoped, otherwise phone seems to function perfectly.
If I use hardware buttons to boot into recovery, I get a white screen with two option, yes or no to factory reset. Assuming this is stock LG recovery, regardless not sure if I should try CWM or stick with my trusty twrp. A lot of stuff on the forum about downgrading bootloaders/ firmwares, making sure modems match the rom flashing. At this point I just want a custom recovery. Any help would be very much appreciated. Don't want to screw it up anymore.
Nerds, help a brother out... this forum sucks compared to note 3 section.
I think I replied elsewhere recognize your username. Use autorec.
If you can get into Android.
thor1k said:
I think I replied elsewhere recognize your username. Use autorec.
If you can get into Android.
Click to expand...
Click to collapse
I use this Autorec, it stated it completed and gave option to boot into recovery or to exit, do we need to use this program to initiate recovery or should it be an option when I choose reboot?
I see everyone mention to use this Autorec apk but I did not see any sticky on our phone about how to use it after we install it or any mention of enabling or using recovery after the install on any of the 6 threads I located with its reference...
When it ran it said 2.7.0.0 in the header, is the version I used old?
If you used this Autorec, what next? Thanks..
sobitthen said:
I use this Autorec, it stated it completed and gave option to boot into recovery or to exit, do we need to use this program to initiate recovery or should it be an option when I choose reboot?
I see everyone mention to use this Autorec apk but I did not see any sticky on our phone about how to use it after we install it or any mention of enabling or using recovery after the install on any of the 6 threads I located with its reference...
If you used this Autorec, what next? Thanks..
Click to expand...
Click to collapse
it's an option for me when I reboot because of GravityBox and Xposed framework, but you can use the usual method to get to recovery after it's flashed. Use the app to get to the recovery once to make sure it's there, then you can safely do the "factory reset" on startup (it won't actually reset it'll just go to recovery) to go to the recovery.
yeah there isn't too much clear documentation about the whole process but follow the steps in sequence that are listed under the Guide section here: http://forum.xda-developers.com/showthread.php?t=2715496
finally you may need to update the touch firmware after-- I did at least: http://forum.xda-developers.com/showthread.php?t=2736166
thor1k said:
it's an option for me when I reboot because of GravityBox and Xposed framework, but you can use the usual method to get to recovery after it's flashed. Use the app to get to the recovery once to make sure it's there, then you can safely do the "factory reset" on startup (it won't actually reset it'll just go to recovery) to go to the recovery.
yeah there isn't too much clear documentation about the whole process but follow the steps in sequence that are listed under the Guide section here: http://forum.xda-developers.com/showthread.php?t=2715496
finally you may need to update the touch firmware after-- I did at least: http://forum.xda-developers.com/showthread.php?t=2736166
Click to expand...
Click to collapse
I tried to see if the TWRP manager would detect it, said it wasn't there, so installed Clockwork manager and it installed some old version of recovery, wouldn't let me choose the IMG file for touch I had downloaded, there was option for boot into recovery within that app, I did, and poof, I was into TWRP .
Unknown waters since never used it. I tried same method as other ROMs, although did not factory reset, or see option to install new ROM like in CWM, wiped dalvik n cache, installed zip of cm12, gapps, su, wiped cache again, it started process of updating android, hope all is well, that app was new and different for me and I was expecting the good old clockwork I used for years to be there so I didn't research it too much since I thought it failed to load since our device is not on list of supported devices.
Looks like it worked, and it knew my previous device and all my apps from my other Lollipop Atrix HD I had, likely through Google back-up, and is downloading all my apps for me, even before logging into Cyanogen account, which usually did that for me...
Was like 40 apps to load, will see if she still works after all the apps load, didn't think I had that many on previous device, hope not every app I ever tried out...
Will try and uninstall the CWM app if that is still there since TWRP seems to load, or just keep to initiate recovery mode for updates..
---------- Post added at 03:44 PM ---------- Previous post was at 03:05 PM ----------
No, that must not have been the correct way...
All was fine until I opened up Facebook, then every single app on my phone started to open up, settings were moving about, like a dozen people were in my phone remotely changing up every setting possible...
ruh roh...
After another forced reboot it seems to be working fine for now, although the phone is now called a AT&T Lge LG-D801 in Google Play when it is a D800.
As many of you may know, Nvidia has recalled their Shield Tablets. I'll be getting a replacement soon. I'll be rooting it as soon as possible when I get it, but first I have a few questions.
First of all, I rooted my tablet using a guide at IBTimes (that used info from XDA forums) installing CWM recovery.
After rooting I installed Link2SD, pretty much the reason I rooted, to save up some space on my internal memory. Everything was going fine, until I received the recall notice. I moved all my app files back to the internal memory, deleted Link2SD, ran a full unroot on SuperSU, (after a while of hanging on the "Please Wait" screen the app just crashed, it wouldn't load up and Root Checker said I had no root access after rebooting.
I don't know whether this was supposed to happen or whether it should have gone more smoothly, please give me an answer to this and tell me if it affected my system in any way) and fastboot flashed the stock recovery.img.
However when I tried to install the update, I got a red triangle error. After checking the log I got an error saying "Package expects build fingerprint of ... or ..., this device has ...."
I can't remember what the fingerprints were, but the first one was something that began with "nvidia/", had a bunch of numbers in the middle followed by an underscore, then it ended with "/release-keys".
However the device's current build fingerprint was exactly the same as the first, except that it cut off halfway through, right after the numbers and the underscore.
I tried resetting my cache, I tried a wipe of the user data. The only way to fix this for me was to re-install a bunch of stock images - recovery.img, boot.img, system.img, etc.
I don't want to wipe my data next time. So I ask for this in my answer:
- An explanation of what the error means
- How this error is caused
- A way to fix this error without wiping my device
- How to prevent this error
- If what happened to SuperSU in my case is normal and if it affected my device in some way
- And, if possible, a way to install the update successfully without getting this error and without having to unroot or remove CWM, and details on how to do this method and any risks.
Thanks in advance. An answer soon would be appreciated.
Hi there,
You'd be best served asking for help from the experts who own your device here:
Shield Tablet Q&A, Help & Troubleshooting
Good luck
Alright, here's the issue. I messed up real bad with my phone. I own a Moto E 1st gen (XT 1022). After receiving the Lollipop 5.1 update I noticed that I didn't have the multi-user option on my phone. Did a little googling and I realized this option was not available to Moto E users for some reason. After a little bit of searching, I found an apparent way to fix this by replacing the build.prop file in device/system with an edited build.prop. I tried doing that in hope to get the multi user option. But somehow it didn't work for me and then my phone didn't boot up correctly. So I tried restoring a backup I had earlier created using TWRP. That didn't work either. So then tried clearing dalvik and cache. Even that didn't work.
But here's the most terrible and stupid thing I did after that: from the wipe menu of TWRP, I checked all the boxes (cache, system, data, EXTERNAL SD EVEN) and cleared everything...!! -_- Now trying to reboot shows "No OS installed. Do you wish to reboot?"
So basically, its a complete junk now. It won't boot up. Just shows the bootloader unlocked warning.
Please could anyone help me reviving the phone...
XDA Visitor said:
Alright, here's the issue. I messed up real bad with my phone. I own a Moto E 1st gen (XT 1022). After receiving the Lollipop 5.1 update I noticed that I didn't have the multi-user option on my phone. Did a little googling and I realized this option was not available to Moto E users for some reason. After a little bit of searching, I found an apparent way to fix this by replacing the build.prop file in device/system with an edited build.prop. I tried doing that in hope to get the multi user option. But somehow it didn't work for me and then my phone didn't boot up correctly. So I tried restoring a backup I had earlier created using TWRP. That didn't work either. So then tried clearing dalvik and cache. Even that didn't work.
But here's the most terrible and stupid thing I did after that: from the wipe menu of TWRP, I checked all the boxes (cache, system, data, EXTERNAL SD EVEN) and cleared everything...!! -_- Now trying to reboot shows "No OS installed. Do you wish to reboot?"
So basically, its a complete junk now. It won't boot up. Just shows the bootloader unlocked warning.
Please could anyone help me reviving the phone...
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
Looks like all is not lost yet, should be about to fastboot flash those images (system, recovery, etc) back. Consider your device factory reset though (as in, all personal info lost).
Please create an account, so you can post in the rest of the site. Then, venture over to the > Motorola Moto E > Moto E Q&A, Help & Troubleshooting forum to explain your predicament in hopes of getting stock fastboot images (or any other solution they cam come up with).
Hope this helps, and good luck!
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.
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