Related
I'm not tech savvy when it comes to Android and I need some help to root my teen's Motorola Moto E 2015, preferably today.
I need to root it to then disable the guest account, so that when I install the ScreenTime app my son can't bypass it by using the guest account. That's a shortcoming of ScreenTime.
I read a bit about ROMs and would like to use CyanogenMod.
But other than my choice of ROM, I haven't found what I believe to be reliable instructions on what to do now step by step. I really do need idiot-proof step by step instructions.
Is there a super Android geek here who has time to take me through the process or offer advice and links to such sources?
Hello,
Welcome to XDA.
Try the thread linked below, there is a YouTube video in the first post that walks you through rooting your device.
http://forum.xda-developers.com/moto-e-2015/general/root-moto-e-2015-t3086819
If you have further questions about your device, try posting your questions in the forum linked below.
http://forum.xda-developers.com/moto-e-2015/help
The experts there may be able to help. Good luck.
Got this far
Found instructions on CyanogenMod Wiki - wiki.cyanogenmod.org/w/Install_CM_for_surnia[/url
but only got as far as step 5. What terminal on my computer? Command Prompt? I typed adb reboot bootloader into Command Prompt but it said adb command is not recognized.
Unlocking the device
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Enable OEM unlock in the Developer options settings on the device. (Note: Not all devices have this setting, so continue with next step if yours does not.)
4. Connect the device to the computer through USB.
5. From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
6. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
* If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
* If you see "no permissions fastboot", try running fastboot as root.
7. From the same terminal, type the following command to obtain your bootloader unlock code:
fastboot oem get_unlock_data
8. Visit the Motorola Bootloader Unlock website and follow the instructions there to obtain your unlock key and unlock your bootloader.
9. If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
10. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
Installing recovery using fastboot
See All About Recovery Images for more information about custom recoveries and their capabilities.
1. Make sure your computer has working fastboot and adb.
2. Download recovery -- you can directly download a recovery image using the link below, or visit twrp.me to obtain the latest version of TeamWin Recovery Project for your device.
Recovery: Downloadmd5: 5fdfe1871589c0a152f3f7e541b6c892
3. Connect the Moto E 2015 LTE to the computer via USB.
4. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
5. Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloaderor by using the hardware key combination for your device while it is powered off.
6. Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
* If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
* If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
7. Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.imgwhere the latter part is the filename of the recovery image.
8. Once the flash completes successfully, reboot the device into recovery to verify the installation. Boot to recovery instructions: Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
* Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.
Installing CyanogenMod from recovery
1. Make sure your computer has working adb.
2. Download the CyanogenMod package for your device that you'd like to install to your computer.
Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.
3. Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
* Using adb: adb push filename.zip /sdcard/
Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.
4. If you are not already in recovery, boot to recovery mode now.
* Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
5. In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
6. Optional (Recommended): Select the Backup button to create a backup.
7. Select Wipe and then Factory Reset.
8. Select Install (if you're running Cyanogen recovery this is Apply Update).
9. Navigate to /sdcard and select the CyanogenMod .zip package.
10. Follow the on-screen notices to install the package.
11. Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod the first and then install any subsequent packages on top of it).
12. Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.
ipzma said:
Found instructions on CyanogenMod Wiki - wiki.cyanogenmod.org/w/Install_CM_for_surnia[/url
but only got as far as step 5. What terminal on my computer? Command Prompt? I typed adb reboot bootloader into Command Prompt but it said adb command is not recognized.
Unlocking the device
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Enable OEM unlock in the Developer options settings on the device. (Note: Not all devices have this setting, so continue with next step if yours does not.)
4. Connect the device to the computer through USB.
5. From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
6. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
* If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
* If you see "no permissions fastboot", try running fastboot as root.
7. From the same terminal, type the following command to obtain your bootloader unlock code:
fastboot oem get_unlock_data
8. Visit the Motorola Bootloader Unlock website and follow the instructions there to obtain your unlock key and unlock your bootloader.
9. If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
10. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
Installing recovery using fastboot
See All About Recovery Images for more information about custom recoveries and their capabilities.
1. Make sure your computer has working fastboot and adb.
2. Download recovery -- you can directly download a recovery image using the link below, or visit twrp.me to obtain the latest version of TeamWin Recovery Project for your device.
Recovery: Downloadmd5: 5fdfe1871589c0a152f3f7e541b6c892
3. Connect the Moto E 2015 LTE to the computer via USB.
4. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
5. Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloaderor by using the hardware key combination for your device while it is powered off.
6. Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
* If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
* If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
7. Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.imgwhere the latter part is the filename of the recovery image.
8. Once the flash completes successfully, reboot the device into recovery to verify the installation. Boot to recovery instructions: Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
* Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.
Installing CyanogenMod from recovery
1. Make sure your computer has working adb.
2. Download the CyanogenMod package for your device that you'd like to install to your computer.
Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.
3. Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
* Using adb: adb push filename.zip /sdcard/
Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.
4. If you are not already in recovery, boot to recovery mode now.
* Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
5. In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
6. Optional (Recommended): Select the Backup button to create a backup.
7. Select Wipe and then Factory Reset.
8. Select Install (if you're running Cyanogen recovery this is Apply Update).
9. Navigate to /sdcard and select the CyanogenMod .zip package.
10. Follow the on-screen notices to install the package.
11. Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod the first and then install any subsequent packages on top of it).
12. Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.
Click to expand...
Click to collapse
Have you installed the adb/fastboot program? Do a Google search for adb/fastboot for windows. Then verify that you have your moto E USB drivers downloaded and installed. You should be able to enter adb commands when that is set up. To verify that adb is working and that your device is recognized you type: adb devices
That should give you a set of numbers and letters, if so then your device is recognized, continue with the commands from your guide.
The YouTube video will walk you through step by step with a visual guide instead of trying to make sense of written instructions, just emulate the operators' actions following the video and you can't go wrong.
Sent from my SCH-I535 using Tapatalk
ipzma said:
Found instructions on CyanogenMod Wiki - wiki.cyanogenmod.org/w/Install_CM_for_surnia[/url
but only got as far as step 5. What terminal on my computer? Command Prompt? I typed adb reboot bootloader into Command Prompt but it said adb command is not recognized.
Unlocking the device
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Enable OEM unlock in the Developer options settings on the device. (Note: Not all devices have this setting, so continue with next step if yours does not.)
4. Connect the device to the computer through USB.
5. From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
6. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
* If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
* If you see "no permissions fastboot", try running fastboot as root.
7. From the same terminal, type the following command to obtain your bootloader unlock code:
fastboot oem get_unlock_data
8. Visit the Motorola Bootloader Unlock website and follow the instructions there to obtain your unlock key and unlock your bootloader.
9. If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
10. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
Installing recovery using fastboot
See All About Recovery Images for more information about custom recoveries and their capabilities.
1. Make sure your computer has working fastboot and adb.
2. Download recovery -- you can directly download a recovery image using the link below, or visit twrp.me to obtain the latest version of TeamWin Recovery Project for your device.
Recovery: Downloadmd5: 5fdfe1871589c0a152f3f7e541b6c892
3. Connect the Moto E 2015 LTE to the computer via USB.
4. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
5. Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloaderor by using the hardware key combination for your device while it is powered off.
6. Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
* If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
* If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
7. Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.imgwhere the latter part is the filename of the recovery image.
8. Once the flash completes successfully, reboot the device into recovery to verify the installation. Boot to recovery instructions: Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
* Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.
Installing CyanogenMod from recovery
1. Make sure your computer has working adb.
2. Download the CyanogenMod package for your device that you'd like to install to your computer.
Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.
3. Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
* Using adb: adb push filename.zip /sdcard/
Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.
4. If you are not already in recovery, boot to recovery mode now.
* Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
5. In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
6. Optional (Recommended): Select the Backup button to create a backup.
7. Select Wipe and then Factory Reset.
8. Select Install (if you're running Cyanogen recovery this is Apply Update).
9. Navigate to /sdcard and select the CyanogenMod .zip package.
10. Follow the on-screen notices to install the package.
11. Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod the first and then install any subsequent packages on top of it).
12. Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.
Click to expand...
Click to collapse
Sorry, I meant to tell you that the command prompt is where you type your commands.
Sent from my SCH-I535 using Tapatalk
I tried when it was stock and it didn't work, then have put a couple different ROMs and it doesn't work. I does connect so I would think it's not a provision issue but something internally maybe? Currently I have Ephemeral Mate 9 rom. I checked the internet on the phone while the laptop is connected and it is working on the phone just fine. Is there something I can check with Root Explorer or SQLite Editor? I have a nexus 6 that works fine so maybe there is a value I can compare and see if something needs to be changed.
Did it wooooo hoooooo!!! Found an article and followed step by step and it worked great. I guess the custom rom doesn't have it baked in.
a. Setup ADB and fastboot drivers on your PC
b. Download TWRP recovery for your device
c. Download stable version of Systemless SuperSU [HERE]
Instruction
1. Flash TWRP recovery image
2. Flash Systemless SuperSU in TWRP recovery
3. While still in TWRP recovery, select Mount and check system. Make sure you allow changes.
4. Connect your phone to your PC and issue the below commands:
adb shell
echo "net.tethering.noprovisioning=true" >> /system/build.prop
adb reboot
5. Now, install Terminal Emulator app from the Play Store and launch it.
6. In Terminal Emulator, enter below code one by one:
su
settings put global tether_dun_required 0
exit
7. Now, open SuperSu, scroll to the bottom and tap on Full unroot. You do not need to patch you back to the stock recovery. If it hangs, just reboot and try doing it again.
You have now unlocked tethering and being an unrooted device, you can continue to use Android Pay. And, to get OTA update on your Nexus phone, do the following.
===============================================================================
TUTORIAL REVISED AND WRITTEN BY @parcek
===============================================================================
FURTHER UPDATED FOR ROOTING NOOBS: 10 Steps
Two Methods: Windows and Linux
Originally posted by @brad2192: https://forum.xda-developers.com/android/development/lg-aristo-2-root-t3746425
Credit to @tecknight for updated files: https://forum.xda-developers.com/showpost.php?p=76837384&postcount=2
@brad2192: Updated Tutorial due to people using TWRP (the original tutorial was released before TWRP was released for this device)
1) Backup all apps and data using LG Backup phone apps
2) Enable USB debugging and Unlock OEM. There are two methods in which you will to accomplish this:
First Method: Smartphone GUI
A) On your Lg Aristo 2 Smartphone go into General Tab (If in Tab View), If in list view, scroll down towards System section
"System Settings > About Phone > Software Information > Click on "Build Number" 10 times.
Now go to "System Settings > About Phone > Developer Options > Enable OEM unlock."
and also "System Settings > About Phone > Developer Options > Enable USB debugging."
Second Method: Windows Command Prompt or Linux Terminal:
Windows:
B) Click and drag "adb" file into command prompt and type "reboot bootloader" after it. Press enter.
Click and drag "fastboot" file into command prompt and type "flashing unlock" after it. Press enter.
Linux:
C)Type in your terminal "adb reboot bootloader" and press enter.
Type in your terminal "fastboot flashing unlock."
NOTE: Below has the information which will teach you how to download ADB and FASTBOOT.
3) Download the following:
Updated - TWRP
Updated - Magisk
(Add this file into your phone's SD Card.)
Updated - boot image
Update: Windows:
B)This is how you download ADB and FASTBOOT for Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
4) Open Command Prompt. Then click and drag the adb file (from the latter download link a.k.a platform-tools) into command prompt then press space and type "reboot bootloader" after and then press enter OR power down phone and hold volume down while plugging in USB)
5) Open Command Prompt. Then click and drag the fastboot file (from the latter download link a.k.a platform-tools) into command prompt and then type "flash recovery" after it and then click and drag "newtwrp.img" into command prompt and press enter.)
6) Open Command Prompt. Then click and drag fastboot (from the latter download link a.k.a platform-tools) into command prompt and then type "flash boot" after it and then click and drag "bootimglistedabove.img" into the command prompt after and then press enter) then follow step 7).
Update: Linux:
C) Depending on kernel, for this sake we will use a debian based kernal.
This is how you download ADB and FASTBOOT for Linux: Open terminal and type: "Sudo apt-get install adb && sudo apt-get install fastboot"
4) Open terminal and type: adb reboot bootloader
5) Open terminal and type: fastboot flash recovery (and then click and drag newtwrp.img onto the terminal) and hit enter
6) Open terminal and type: fastboot flash boot (and then click and drag bootfilelistedabove.img onto the terminal) and hit enter
This applies towards both Windows and Linux: continuation after their last listed step written above.
Step 7) Remove battery from phone, in order to force a shut down.
8) Boot into Recovery-TWRP Mode.
How to boot into LG Aristo 2 TWRP Recovery:
a) The phone is off.
b) Hold the volume key and power key at the same time.
c) When the LG logo appears, let go of the power key (while still holding the volume down key) and then click and hold the power key once again.
d)You will be prompted to LG Aristo 2's stock recovery mode asking you if you are sure you would like to delete ur phone.
e) Go to the option "yes" and enter.
f) It will then warn you that can remove all data from your phone.
g) Go to the option "yes" and enter.
You will be in TWRP after this.
TWRP Mode:
9) In TWRP go to "Wipe > Format Data" and then type "yes" and confirm it. (Do not hit reboot, click back a few time and hit reboot > recovery)
10) In TWRP go to "Install > Select Storage" and select your SD Card. Then look for where you placed the "magisk" zip file. Install it.
Your phone is now rooted.
On TWRP menu: Reboot.
Restore your phone if you created an LG backup of your important files (like lets say contacts or applications).
-----------------------------------------------
If any mistakes were made and you phone becomes locked, here is how to go into download mode to repair your LG Aristo 2 into its default stock rom. Credit to @tecknight: https://forum.xda-developers.com/showpost.php?p=76837800&postcount=4
1) Power off phone.
2) connect usb to Lg Aristo 2 phone (without connecting the usb into the PC or laptop)
3) Hold volume up key and then connect USB into computer
4) download LG Bridge
5) detect phone
6) click on "Update Error Recovery"
Your LG Aristo 2 will be repaired and factory resetted.
-------------------------------------------------------------
What root means: In terms of PC language, Root means the superuser that has privileges to Add, Modify, and or Delete any kind of system files without prevention. Pretty much, it's like the actual Administrator account on a PC. Natively, whenever we buy a phone, it is as if to say, we are only using a guest account. Since the android OS is basically a Linux based computer (correct me if i am wrong) we can do anything we like... You want iOS emoji's on an android? A custom boot animation? Having root privileges allows you to go beyond your guest user restrictions because you then become the Admin.
Explaining the function of the provided Magisk app: It allows root privileges for programs intended for rooted phones.
There are other popular programs alternative of Magisk app, such as the SuperSU app: http://www.mediafire.com/file/2dljobq6yw93w76/UPDATE-SuperSU-v2.82-20170528234214.zip
--------------------------------
After being officially done setting up your rooted phone, make sure you disable OEM Unlock to avoid seeing the caution message before every boot.
--------------------------
How to backup your phone.
Also, using ADB, backup your phone.
Windows: Click and drag ADB file onto command prompt and paste " backup -apk -shared -all -f "C:\Users\UserName\Desktop\backupfilename.ab" "
Linux: Open terminal and type " adb backup -apk -shared -all -f "C:\Users\UserName\Desktop\backupfilename.ab" "
Update: For those who are encountering "Now unlock your phone and confirm operation" when typing the latter code, there is an alternative and much more easier and safer way to backup your phone.
Boot into TWRP and click on "backup" and then select what you would like to back up and then swipe to confirm the operation.
-----------------------------------------------------------------
Confirmed Successful rooting for LG Aristo 2 - June 2018
Thank You Brad and Tec!
Salam Aleykom.
You are a lifesaver my friend
Senorhamburgler said:
You are a lifesaver my friend
Click to expand...
Click to collapse
Brad I have a question, is there any way to get a custom ROM on this phone? If not how come? How does it all work?
And are you with Metro PCS as well? What apps can a safely delete to get this phone as close to a stock version of android as I can? Can I seriously just wipe out EVERY metro app? Hows your phone functioning?
tribal1209 said:
Brad I have a question, is there any way to get a custom ROM on this phone? If not how come? How does it all work?
And are you with Metro PCS as well? What apps can a safely delete to get this phone as close to a stock version of android as I can? Can I seriously just wipe out EVERY metro app? Hows your phone functioning?
Click to expand...
Click to collapse
Until there is a custom recovery built, we won't have custom roms. Dont wipe out every metro app. Anything you arent sure about, look up, or just freeze the app and test results. My phone is fine except SuperSU wont work properly due to the binary being occupied, but this is the best we have so far. I debloated no problem.
tribal1209 said:
Brad I have a question, is there any way to get a custom ROM on this phone? If not how come? How does it all work?
And are you with Metro PCS as well? What apps can a safely delete to get this phone as close to a stock version of android as I can? Can I seriously just wipe out EVERY metro app? Hows your phone functioning?
Click to expand...
Click to collapse
Senorhamburgler said:
Until there is a custom recovery built, we won't have custom roms. Dont wipe out every metro app. Anything you arent sure about, look up, or just freeze the app and test results. My phone is fine except SuperSU wont work properly due to the binary being occupied, but this is the best we have so far. I debloated no problem.
Click to expand...
Click to collapse
Root is the only thing needed, not a custom recovery. Apps like Magisk Manager can flash custom images. The reason there is no ROMs built for this device, I can tell you in my opinion there is no need for a Custom ROM. Magisk Manager has plenty of customizations available as well as many other root apps. Basically, custom recoveries are obsolete, it is not needed for gaining root access nor flashing files. Magisk can do it as well as Flashfire.
I need help.... Abd is not functioning it states "the term abd is not recognised as the nane of a cmdlet, function, scrip file of operable program."
Does not exist in current location.... Windows PowerShell does not load conmands by default...
MinaSaotome said:
I need help.... Abd is not functioning it states "the term abd is not recognised as the nane of a cmdlet, function, scrip file of operable program."
Does not exist in current location.... Windows PowerShell does not load conmands by default...
Click to expand...
Click to collapse
Hey man, I would press the Windows Key+R and type" "cmd"
Then, as long as your adb is located at C:\adb type: "cd C:\adb"
Then use adb, I hate how Windows 10 forces it on users!
Hey, I am so sorry to bother you but when I enter in the fourth step of your tutorial, it tells me "flash boot" command doesn't exist. Is there something I'm doing wrong?
---------- Post added at 01:15 AM ---------- Previous post was at 01:01 AM ----------
4btn said:
Hey, I am so sorry to bother you but when I enter in the fourth step of your tutorial, it tells me "flash boot" command doesn't exist. Is there something I'm doing wrong?
Click to expand...
Click to collapse
Okay, after messing around with it a few, I found that once it goes off into fastboot... my computer can't recognize it anymore?
brad2192 said:
Hey guys, spent a few hours figuring out how to root. Pretty Simple!
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
For those skeptical, proof of root here.
X-210 Stock .KDZ Backup HERE (Should not be needed.)
Click to expand...
Click to collapse
Do I need to unlock the bootloader first? I have it rebooted into fastboot and it's giving me instructions to do that, but won't let me push the boot image. If I do need to unlock it, does it wipe my device?
tge101 said:
Do I need to unlock the bootloader first? I have it rebooted into fastboot and it's giving me instructions to do that, but won't let me push the boot image. If I do need to unlock it, does it wipe my device?
Click to expand...
Click to collapse
Yes, that is what OEM unlock means. In doing so you do need to unlock the bootloader.
brad2192 said:
Yes, that is what OEM unlock means. In doing so you do need to unlock the bootloader.
Click to expand...
Click to collapse
Just wanted to make sure but does it wipe it?
tge101 said:
Just wanted to make sure but does it wipe it?
Click to expand...
Click to collapse
Yes, when you use "fastboot oem unlock" it unfortunately erases all data. One of our forum members is working on a TWRP at the moment that might be available today. You could wait to do this so you can create a backup.
brad2192 said:
Yes, when you use "fastboot oem unlock" it unfortunately erases all data. One of our forum members is working on a TWRP at the moment that might be available today. You could wait to do this so you can create a backup.
Click to expand...
Click to collapse
That'd be cool. But, wouldn't the bootloader still need to be unlocked for me to flash TWRP?
tge101 said:
That'd be cool. But, wouldn't the bootloader still need to be unlocked for me to flash TWRP?
Click to expand...
Click to collapse
I'm an idiot, yes LOL. Sorry, just got to work and I am tired you are correct. So, if you would like I suggest just using my tutorial. I believe there is ways of using LG backup to save most of your user data.
brad2192 said:
I'm an idiot, yes LOL. Sorry, just got to work and I am tired you are correct. So, if you would like I suggest just using my tutorial. I believe there is ways of using LG backup to save most of your user data.
Click to expand...
Click to collapse
All good, if I lose it I lose it. Is there a thread for the TWRP development?
I posted a test twrp on my blog for aristo 2
cannot open root_boot.img
hey maybe someone can help me out
previously already unlocked the bootloader on the phone so i skipped that step but i keep getting the error that it can not open root_boot.img
downloaded the file and moved into users/appdata/local/android/sdk/platform-tools
thats where adb.exe so i figured that is the adb folder maybe yes or no
could anyone help me out
greatly appreciate it
tge101 said:
All good, if I lose it I lose it. Is there a thread for the TWRP development?
Click to expand...
Click to collapse
Update: TWRP HERE
TJ-yesthelegend said:
hey maybe someone can help me out
previously already unlocked the bootloader on the phone so i skipped that step but i keep getting the error that it can not open root_boot.img
downloaded the file and moved into users/appdata/local/android/sdk/platform-tools
thats where adb.exe so i figured that is the adb folder maybe yes or no
could anyone help me out
greatly appreciate it
Click to expand...
Click to collapse
What are you typing into ADB to get that error?
Do you have to de-encrypt the phone for root? I am thinking of getting an Aristo2, currently using the MotoE4 (which I hate!), and rooting that requires de-encryption (I love encryption!). This is the MetroPCS version your talking about? Thank you...
DISCLAMER: DOING THIS MIGHT RESET YOUR PHONE SO PLEASE BACKUP YOUR FILES BEFORE DOING THIS
now lets get started
download this tool (even if you already have adb and fastboot)*
https://forum.xda-developers.com/showthread.php?t=2317790
and go to your phone's settings then System > about phone and press on build number until it tells you: "you have developer options"
now go to System > developer options and enable android debugging and OEM Unlocking
now plug your phone into the pc and open the file: "cmd-here.exe" from the tool you downloaded
now type adb devices and it will probably tell you unauthorized, if it does then open your phone and click on accept
if you dont see any thing other than "list of devices attached" then download this
open it and input in, N and then Y so you dont install adb but you do install the phone's drivers
now type adb devices and you should see random numbers, if it says unauthorized just go back to when I said how to fix it
so now that everything is working type in the command prompt: adb reboot bootloader
now you should see a russian cat fixing a android machine with blue text: "FASTBOOT"
now type "fastboot oem unlock" and it should unlock your phone
now type "fastboot reboot"
--------------------------------------------------------
good, Now you have the bootloader unlocked
--------------------------------------------------------
If you are now put in the setup screen don't do it, just shut down your phone and then when it's shutdown hold on the power button and volume down buttons until you enter fastboot again
now go to this page: https://github.com/CosmicDan-Android/android_device_xiaomi_tissot/releases and download the latest boot only and regular versions
put them both in the adb (tool) folder and type in the command prompt: "fastboot boot boot-recovery.img"
if your phone doesnt do anything (doesn't do anything in the 30s after you input the command) then restart it and get it back in fastboot and type fastboot --set-active=b
and then type the previous command again, if that doesnt work then restart your phone back to fastboot again
and then type fastboot --set-active=a and the command "fastboot boot boot-recovery.img" and it should work
so now you will be in twrp, good!
type "adb push (regular twrp zip name, remember to put .zip at the end!) /sdcard/"
example:"adb push TWRP-Installer-3.2.1-with-Tissot-Manager-2.5.zip /sdcard/"
and then in your phone go to install and you should already be in /sdcard if not then go there and then tap on the zip and swipe on the thing
after it finishes installing go to reboot and then tap on recovery
--------------------------------------------
good now you have TWRP installed!
-------------------------------------------
Now its up to you, do you want to install only root or rom and root? its up to you
Root Only:
Download Magisk (you can also use SuperSU but I strongly recommend magisk)
put it in your adb (tool) folder and type "adb push (magisk's zip name, remember to put .zip at the end!) /sdcard/"
example:"adb push Magisk-v17.1.zip /sdcard/"
go to install, press on the zip file and swipe on the thing and click on restart system at the end
and congrats! you have root on your phone!
Rom:
If were talking about a treble rom then you should follow this guide: https://forum.xda-developers.com/mi-a1/how-to/treble-stock-to-treble-everything-to-t3793734 but if not you can continue using this one
download your favorite rom and download magisk (you can also use SuperSU but I strongly recommend magisk)
also go to opengapps.org choose arm64 and the android version your rom is and I recommend the nano variant
now in twrp tap on Wipe and Advanced Wipe and choose everything there (you dont have to choose micro SDcard tho) and swipe THIS WILL RESET YOUR PHONE AGAIN BUT YOU PROBABLY DONT CARE ABOUT THAT RIGHT NOW
now in the command prompt type: "adb push (rom zip name, remember to put .zip at the end!) /sdcard/"
example:"adb push RR-O-v6.1.0-20180709-Official /sdcard/"
and install it, some roms include gapps and other things in their installation for example: pixel experience. but most roms don't have that
so if you check the xda page and they say nothing about including opengapps in the rom then you should be able to fully follow the next steps.
type "adb push (magisk zip name, remember to put .zip at the end!) /sdcard/" and install it
then type "adb push (opengapps zip name, remember to put .zip at the end!) /sdcard/" and install it
now tap on reboot system and congrats! you just rooted and custom rom-ed your phone!
* "even if you already have adb and fastboot" the reason for this is because that link uses the newest version (or new enough) that is surprisingly not common in other places I downloaded adb and fastboot. the new version adds a new command that is used in the guide if you are experiencing a certain problem
I hope I helped you, if you have any questions or problems post them in the comments
a big THANK YOU
Months ago I rooted and installed a new ROM for first time in my life and, although I read another guides, with them I always break my phone, so I must flash and start again. And your guide, 4 months later, saved me again. I don't know why, really. Maybe because is super friendly. But thank you, again. The only thing I'll add is wtf to do when TWRP asks if install in slot a or b because that's the point I always mess it :'(
Thank you forever
vainille said:
The only thing I'll add is wtf to do when TWRP asks if install in slot a or b because that's the point I always mess it :'(
Click to expand...
Click to collapse
You mean when you flash the rom it asks you which slot to install to?
Hi,
during the update the phone got stuck, daughter restarted couple of times but it always got to the 76%, hang there and then restarted itself in the endless loop.
I've tried the the hard reset (Power+VolUP) and it got to the screen saying "No Command". Then I pressed the same combo again to get to the bootloader and tried the wipe / reset. During that process I got the error message "E: Can't send SPI message. Try again" and then it said it was successful, but rebooting did nothing, got stuck in the restart loop.
So I've done the research and wanted to to upload the OTA update, have done that but that didn't do anything.
So I've found some articles on how to upload the stock rom/image but I'm unable to do so as sending adb commands is disabled due to the phone being LOCKED. I've learned that the USB debugging needs to be enabled, however I'm unable to get into the OS to set it up, so found this article:
How to enable USB Debugging in Android using recovery mode?
One million questions, Is it possible to Enable USB Debugging in Android Using Recovery Mode or any other technique? Well, the answer is Yes! It is now
www.isrgrajan.com
which outlines the following steps (in summary):
Download the Stock ROM for your device- Google it, I am dam sure you can find it. [DONE]
Download SuperSU from UPDATE-SuperSU-v1.65.zip [DONE][looks pretty old though]
Steps to Enable USB Debugging Using Recovery Mode
Unzip the stock ROM. [DONE]
Within the extracted folder, you will find the system.img well extract it too using Ext4 Unpacker [DONE but plenty of folder are empty, but eventually plentu of APK along]
Also, extract the Update-SuperSU.v1.65.zip file. [DONE, again, looks pretty old]
Now open the folder where you have extracted the system.img files [DONE]
Grab any .apk file from this folder and change the extension from .apk to .zip [PROBLEM: the apks are all over the shop. Which APK shall I pick up?]
And Copy the RSA Certificated to the Update-SuperSU.v1.65 folder (delete previous files if exist) [PROBLEM: unable to find any "RSA Certificated" like files once I open ANY apk]
Also, copy the build.prop to the system folder located within Update-SuperSU.v1.65 folder [BLOCKED by previous step]
Locate the update-script file within this folder and edit it using Notepad++ [BLOCKED by previous step]
You need to update the build.prop file after adding the following line at the bottom [BLOCKED by previous step]
persist.service.adb.enable=1
Next step is updating SQLite Database [WHERE would I do this step?]
Which can be done by adding the following code to the update-script file
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "UPDATE global SET value=1 WHERE name='adb_enabled'"
What would I do then? How to actually apply the changes back to the phone?
Does anyone know of better / latest step by step process of enabling / unlocking the device or is my device now completely and unrepairably bricked?
Thank you.
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
jwoegerbauer said:
https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd
Click to expand...
Click to collapse
For a while (since when, I don't know) persistent properties are not shared as individual files in /data/property.
They are all packed inside /data/property/persistent_properties.
Try setprop instead.
jwoegerbauer said:
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
will give it a go. thank you.
jwoegerbauer said:
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
I've tried the steps but I'm crashing on sending any commands to the device. While I'm in the recovery, I see the following details and options:
```
Android Recovery
google/blueline/blueline
12/SP1A.210812.016.B2/8602260
user/release-keys
Use volume up/down and power
Warning: Previous installation has failed. Your device may fail to boot if you reboot or power off now
- Reboot system now
- Reboot to bootloader
- Enter Fastboot
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Mount /system
- View recovery logs
- Run Graphics Test
- Run Locale Test
- Power Off
```
where I run the adb command:
`adb shell mount data` I get the `adb.exe: no devices/emulators found`.
when I go to the `Apply update from ADB` and run the command above I get `error: closed`.
Basically I'm unable to run any adb commands as of the first message, and the only place I can it's from within the update. I've noticed that while in the 'Update via ADB', then in the Win Device Manager I can see that the driver is changed to `Android Composite ADB Interface` and only now it's accepting very limited commands. `adb devices` command generates: `<device id number>: sideload`.
When in the fastboot, it switches to `Android Bootloader Interface` in the DEvice manager.
When in recovery, the device is disconnected from the computer. (is not listed in the device manager)
any thoughts. thanks
Note: that phone was never rooted.
Bootloader looks like this at the moment:
```
Fastboot Mode
Product revision: blueline MP1.0(ROW)
Bootloader version: b1c1-0.4-7617406
Basebandversion...
serial number:
secure booth: PRODUCTION
NOS Production: yes
DRAM: 4GB
Device State: Locked
Boot slot: a
```
vajnorcan said:
I've tried the steps but I'm crashing on sending any commands to the device. While I'm in the recovery, I see the following details and options:
```
Android Recovery
google/blueline/blueline
12/SP1A.210812.016.B2/8602260
user/release-keys
Use volume up/down and power
Warning: Previous installation has failed. Your device may fail to boot if you reboot or power off now
- Reboot system now
- Reboot to bootloader
- Enter Fastboot
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Mount /system
- View recovery logs
- Run Graphics Test
- Run Locale Test
- Power Off
```
where I run the adb command:
`adb shell mount data` I get the `adb.exe: no devices/emulators found`.
when I go to the `Apply update from ADB` and run the command above I get `error: closed`.
Basically I'm unable to run any adb commands as of the first message, and the only place I can it's from within the update. I've noticed that while in the 'Update via ADB', then in the Win Device Manager I can see that the driver is changed to `Android Composite ADB Interface` and only now it's accepting very limited commands. `adb devices` command generates: `<device id number>: sideload`.
When in the fastboot, it switches to `Android Bootloader Interface` in the DEvice manager.
When in recovery, the device is disconnected from the computer. (is not listed in the device manager)
any thoughts. thanks
Note: that phone was never rooted.
Bootloader looks like this at the moment:
```
Fastboot Mode
Product revision: blueline MP1.0(ROW)
Bootloader version: b1c1-0.4-7617406
Basebandversion...
serial number:
secure booth: PRODUCTION
NOS Production: yes
DRAM: 4GB
Device State: Locked
Boot slot: a
```
Click to expand...
Click to collapse
On my pixel3, /dev/block/dm-4 is mounted to /data. Try "adb shell mount /dev/block/dm-4 /data".
The instructions you are following are very old, and likely obsolete. SuperSu is also obsolete. Try to find a newer method.
dcarvil said:
On my pixel3, /dev/block/dm-4 is mounted to /data. Try "adb shell mount /dev/block/dm-4 /data".
The instructions you are following are very old, and likely obsolete. SuperSu is also obsolete. Try to find a newer method.
Click to expand...
Click to collapse
the issue is I'm unable to run that command `adb shell mount...` with the `no devices/emulator found` message. I believe it's because the device is not even listed in the device manager (windows) when in recovery mode. When in the update mode, then it's listed in the DM. See my post above, I've updated it few times. Thanks
Btw on that link if you check the posts there are newer ones (1.5y back) claiming it works so might actually work
If you're unable to sideload the OTA via PC, I don't think there's any other option besides paying for a repair, or replacing the device. A locked bootloader definitely makes recovery a lot harder.
V0latyle said:
If you're unable to sideload the OTA via PC, I don't think there's any other option besides paying for a repair, or replacing the device. A locked bootloader definitely makes recovery a lot harder.
Click to expand...
Click to collapse
I'm able to sideload the OTA, but restart goes into start being stuck and back and forth but never gets any further than the first google load screen
vajnorcan said:
I'm able to sideload the OTA, but restart goes into start being stuck and back and forth but never gets any further than the first google load screen
Click to expand...
Click to collapse
Were you using adb/fastboot before this happened? Was the device recognised then? If not, are you sure you have the right drivers?
AlexKarimov said:
Were you using adb/fastboot before this happened? Was the device recognised then? If not, are you sure you have the right drivers?
Click to expand...
Click to collapse
I've used the adb to upload the ota and that went, according the message ok, but the system won't start up. Device is recognized only when I choose the "Apply update from ADB" option in recovery mode. The moment I choose it, it shows up as a device in device manager and "adb devices" lists it ok. In fastboot mode it does list it in device manager, but "adb devices" doesn't list it.
It's the latest driver
vajnorcan said:
I've used the adb to upload the ota and that went, according the message ok, but the system won't start up. Device is recognized only when I choose the "Apply update from ADB" option in recovery mode. The moment I choose it, it shows up as a device in device manager and "adb devices" lists it ok. In fastboot mode it does list it in device manager, but "adb devices" doesn't list it.
It's the latest driver
Click to expand...
Click to collapse
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
AlexKarimov said:
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
Click to expand...
Click to collapse
This requires OEM Unlocking to be enabled so it won't be much help here.
Rescue Mode might work though.
@vajnorcan try this:
Boot to bootloader and select Rescue Mode using the volume buttons, then press Power to enter it.
On your PC, go to pixelrepair.withgoogle.com and connect the USB cable to your device. Select your carrier or select "Other" if device is unlocked.
I don't know whether this will actually work...I haven't heard of anyone using this tool to successfully recover.
AlexKarimov said:
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
Click to expand...
Click to collapse
'fastboot devices' is reading the device, which is good. but trying the online flash tool fails due to the device being locked. :/
V0latyle said:
This requires OEM Unlocking to be enabled so it won't be much help here.
Rescue Mode might work though.
@vajnorcan try this:
Boot to bootloader and select Rescue Mode using the volume buttons, then press Power to enter it.
On your PC, go to pixelrepair.withgoogle.com and connect the USB cable to your device. Select your carrier or select "Other" if device is unlocked.
I don't know whether this will actually work...I haven't heard of anyone using this tool to successfully recover.
Click to expand...
Click to collapse
The google tool has found and connected to the device, but it ends up in an error (on the device) and saying "disconnected", looked promising, but not for long. thanks.