LG Aristo 2 ROOT (LM-X210[Build- X210MA10i]) - Miscellaneous Android Development
===============================================================================
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...
Related
Elaboration on "how to root"
I think this thread can eventually turn into a sticky. I am going to ask all the common / newbie questions relating to the post by toast that is quoted below. Please contribute clear answers in the thread and I'll include them here at the top: Q: What does RUU stand for? A: ROM Upgrade Utility. It is used when a new ROM is available by your carrier. Don't use this since it will nullify your root. Q: Where can I find photos of the root process? A: Right Here, thanks to pingpongboss Q: Where can I find the details and download locations of the custom roms available? A: ??? Q: What is a custom recovery? A: ??? Q: What is a recovery partition? A: ???? Q: What things are we not able to do since we don't have the ability to toastcfh said: Write to system or recovery while in android - Flash a custom recovery that can be booted into by holding vol down and powering on Click to expand... Click to collapse A: 1) You cannot remove unwanted applications inside of android that couldn't normally be removed. You must remove them prior to boot. 2) ??? Q: What are all those code snipbits? A: ?? Q: What is the point of the "recovery instructions"? A: ?? toastcfh said: HOW TO ROOT YOUR HTC EVO DO NOT USE A RUU FROM SPRINT IF U WANNA MAINTAIN ROOT. WAIT FOR ME OR SOMEONE HERE TO MAKE A ROOT UPDATE.ZIP. Major thanx for those who helped: keishou (for the rooted build. without it none of this would be possible) maejrep (for testing and modding a recovery for the EVO) Flipz (for hosting the files) Paul (for his recovery work on the desire and legend) Amon_RA (for his recovery source on github) WHAT THIS ROOT METHOD WILL DO: - wipe all of your data so brace for that. backup or what not - Allow you to flash custom roms - Boot into a custom recovery - Write to system, boot and recovery partitions through recovery WHAT THIS ROOT METHOD SADLY WONT ENABLE YOU TO DO: - Write to system or recovery while in android - Flash a custom recovery that can be booted into by holding vol down and powering on THINGS YOU WILL NEED: download files below: - PC36IMG.zip - evorecovery INSTUCTIONS FOR ROOTING: - Put the PC36IMG.zip on the root of your sdcard Code: adb push PC36IMG.zip /sdcard - Power off the phone - Hold volume down while powering the phone on. continue to hold volume down until you see the WHITE bootloader screen. - After a few seconds it will begin to checking for files, and find PC36IMG.zip. while its doing this it will show a blue progress bar while its checking. (this takes 30 - 60 seconds to finish) - It will then list all the images in the zip and ask you if want to flash. SAY YES - When its finished it will ask you if you would like to reboot. AGAIN... SAY YES - At this point it will boot into a rooted rom. - YOU ARE NOW ROOT!!! - rename the PC36IMG.zip on your sdcard: - plug your phone into a usb port on your desktop and do: Code: adb shell mv /sdcard/PC36IMG.zip /sdcard/root-PC36IMG.zip RECOVERY INSTRUCTIONS: - Extract the evorecovery.zip to your desktop - plug your phone into a usb port on your desktop - In a shell: Code: adb reboot recovery - this will reboot your EVO into recovery mode. at this point turn your attention to the directory u extracted the evorecovery.zip to. Code: For Windows XP ~~> Run recovery-windows.bat For Vista and Windows 7 do it as Admin - in a shell do: Code: For Linux ~~> ./recovery-linux.sh - at this point turn your attention to the phone and navigate to create a Nandriod Backup. you can now flash custom roms, write, and make changes to system. - to flash a custom rom put the rom on the root of your sdcard. wipe data, dalvic cache and chose the option to flash update.zip from sdcard. RECOVERY NAVIGATION: - Code: Volume up/down moves through the list and Power selects. RECOVERY SOURCE: - http://github.com/jhansche/amonra_bootable_recovery/tree/supersonic Code: git clone git://github.com/jhansche/amonra_bootable_recovery.git git checkout supersonic Click to expand... Click to collapse
Pics of the rooting process: http://androidforums.com/htc-evo-4g/90122-root-out.html
pingpongboss said: Pics of the rooting process: http://androidforums.com/htc-evo-4g/90122-root-out.html Click to expand... Click to collapse Phenomenal. Added to the original post. Could you please help with some of the other questions if possible? Thanks
forumsid987 said: Phenomenal. Added to the original post. Could you please help with some of the other questions if possible? Thanks Click to expand... Click to collapse Where to find custom roms: in this subforum xD the rest of the questions I don't know how to answer correctly. Custom recovery lets you flash custom roms and make nandroid backups?
forumsid987 said: Q: Where can I find the details and download locations of the custom roms available? A: ??? Q: What is a custom recovery? A: ??? Q: What is a recovery partition? A: ???? Q: What things are we not able to do since we don't have the ability to A: 1) You cannot remove unwanted applications inside of android that couldn't normally be removed. You must remove them prior to boot. 2) ??? Q: What are all those code snipbits? A: ?? Q: What is the point of the "recovery instructions"? A: ?? Click to expand... Click to collapse In order top to bottom: As they become available you will find them in this forum. I will release a fresh rom for evo once I can test on my own device. It will be posted here, as well as at http://geekfor.me like always. The green and black screen that you see that lets you flash a custom rom and create a nandroid backup, that is a custom recovery. The problem is because of NAND protection we can't currently flash that recovery and have it stick. That's why you have to run the bat/sh script each time, to load it manually. It's the partition that the recovery resides on (the part of the internal storage memory). Aside from not writing to system while booted (which was answered already) all that means is that instead of being able to boot directly in to the custom recovery view power button + home button or volume down, you need to run that script to get in to recovery. That's the only thing not being able to load the custom recovery means. Code snipbits? Um, because how else would you know how to get in to recovery so that you can flash a rom / create a backup / etc??
Is there any chance of fixing that recovery issue? Having to run the script to access it each time is going to get old fast. ------------------------------------- Sent via the XDA Tapatalk App
In the rooting instructions it keeps mentioning just plug phone into usb port on a pc and in shell do this. I am on windows 7..what shell?
maybe change the thread title to FAQ on how to root rather than elaboration, might attract more attention. i was going to answer the questions which haven't been answered but flipzmode did a great job and the 1st post hasn't been updated. once the 1st post has been updated i'll check back and add more detailed if there is anything left to help with! MrDSL said: In the rooting instructions it keeps mentioning just plug phone into usb port on a pc and in shell do this. I am on windows 7..what shell? Click to expand... Click to collapse good question, this would be good to add to the guide above. the shell on windows 7 means the command prompt. never used win 7 but on win xp and vista, start->run->cmd and it pops open the command prompt, navigate to where you extracted the zip file contents to, cd c:\evo-root\ . then run the .bat file by typing recovery-windows.bat . on linux the terminal interface is called a shell because it actually brings up a shell binary, /bin/sh or /bin/bash . google these binaries for more detailed information. on windows the shell, is basically the command line which is now emulated in windows, where back in the days of DOS it was the actual system with windows loaded on top as a GUI... sorry prob too much information!
Is there an alternative to reboot recovery that does not require ADB?
forceOnature said: Is there an alternative to reboot recovery that does not require ADB? Click to expand... Click to collapse an alternative way to reboot into recovery without using adb? boot into the bootloader and select recovery? use the quick boot GUI to reboot directly into recovery? use connectbot and connect localhost, type reboot recovery? you'll be needing ADB for a good chunk of the custom recovery process in order to load this Froyo ROM. adb isnt too bad, just dive in and we're all here to help!
MrDSL said: In the rooting instructions it keeps mentioning just plug phone into usb port on a pc and in shell do this. I am on windows 7..what shell? Click to expand... Click to collapse Start -> Accessories -> Right-Click on "Command Prompt" -> select "Run as Administrator". If you don't need to run as admin, you can do Start -> type cmd -> Enter and it'll come up.
adb driver for windows 7 http://depositfiles.com/en/files/yd61xorii
Anyone have some solid "Adb on Mac" instructions? LIke how to get it going on a mac... Just switched from PC... Thanks
a5ehren said: Start -> Accessories -> Right-Click on "Command Prompt" -> select "Run as Administrator". If you don't need to run as admin, you can do Start -> type cmd -> Enter and it'll come up. Click to expand... Click to collapse I believe Start -> type cmd -> Shift+Enter will run as admin also.
JustinChase said: I believe Start -> type cmd -> Shift+Enter will run as admin also. Click to expand... Click to collapse Simply put im on a mac and a windows at the same time.. I cannot get the bat to run correctly I see it run but it looks like a fc and then it closes.. On the mac I get asked for this.. sudo: ./adb-mac: command not found sudo: ./adb-mac: command not found new-host:~ GodDriven$ sudo: ./adb-mac: command not found Please help?
[HOW-TO] Unlock and Root Moto G via Recovery/SuperSU
Unlocking the Bootloader is Required! This will erase all data and void your warranty! Since all data will be wiped it's best to do this immediately after getting the phone. At least unlocking the bootloader. I won't add a disclaimer, because if you trust some guide from some guy on the internet you should know what that means without being told explicitly. For me the bootimage method posted on Modaco does not work and apparently others seem to have trouble as well (see the poll at Modaco). And since I couldn't find any guide here on XDA I thought I'd write one. XDA helped me a lot when I got my DHD, so maybe now I can help back. This is based on soyd's guide at swedroid.se which I used to finally get my phone rooted after some unsuccessful attempts. The guide is for Windows, but could probably be easily adapted to Linux/Mac by using the appropriate drivers/tools. I followed these steps to successfully root my Moto G (16 GB, german retail, Android 4.4.2, OTA 176.44.1). Here're the neccessary steps: Install Motorola and ADB Drivers Unlock Bootloader Flash Recovery Flash SuperSU Enjoy Install Motorola and ADB Drivers Do not connect your phone to your PC just yet. If you already have ADB drivers and Motorola drivers installed, just skip this step. Download these files: Motorola Drivers ADB Tools (thx to androidpit.info) mfastboot.exe (only download that file from the G-Drive folder - thx to whoever uploaded it) Run the MotorolaDeviceManager_2.4.5.exe you just downloaded and install it Extract the two folders from adb-tools_treiber.zip Open ADB-Treiber folder and run UniversalAdbDriverSetup.msi Copy mfastboot.exe to ADB-Tools folder Now this next part might be optional, but some things might not work without it and there's no real harm so: Enable USB-Debugging On your phone, open Preferences Scroll all the way down to About this phone Scroll all the way down to Build-Number Tap 7 times on that entry You'll get a message "You're a developer now" Go back and open the new item Developer options Check USB-Debugging Connect your phone to the PC Drivers will be installed and the phone will ask you to confirm USB debugging from that computer Unlock Bootloader There are probably lots of guides around, but to have it all in one place, here's yet another one: !YOU WILL LOOSE YOUR WARRANTY AND ALL DATA BY UNLOCKING THE BOOTLOADER! Switch off your phone Hold Volume-Down and press and release Power to boot into Fastboot A text screen should appear Connect the phone via USB to the PC Open a command prompt and browse to the ADB-tools folder you just created Type: Code: fastboot oem get_unlock_data You'll get five lines of characters, all beginning with (bootloader): Code: (bootloader) 0A40040192024205#4C4D3556313230 (bootloader) 30373731363031303332323239#BD00 (bootloader) 8A672BA4746C2CE02328A2AC0C39F95 (bootloader) 1A3E5#1F53280002000000000000000 (bootloader) 0000000 Copy all lines into one long string without the (bootloader) part! You want something like 0A40040192024205#4C4D355631323030373731363031303332323239#BD00 and so on. Open Motorola Unlocker Site (you need to sign-in) Copy the string in the box at 6. and press Can my device be unlocked? A Request my Unlock Key button should appear. Check I Agree to the legal stuff and press that button Check your mail for the unlock key In the ADB-tools folder type: Code: fastboot oem unlock [I]paste_your_key_here[/I] The phone should reboot and greet you with a nice warning about you having lost your warranty. Flash Recovery Now that the booloader is unlocked you have to flash a custom recovery to be able to flash SuperSU. Download the CWM image from this post. The file should be named something like recovery-clockwork-6.0.4.7-falcon.img. Copy the file to the ADB-Tools folder you created earlier and rename it to CWM.img Your phone should still be connected to your PC and have finished rebooting and be in stock ROM. In the ADB-Tools folder type: Code: adb reboot bootloader The phone should reboot and the bootloader will come up again To make sure all's working as expected type: Code: fastboot devices You should get a response similar to: Code: List of devices attached TA93005M6V device To flash the custom recovery, type: Code: mfastboot flash recovery CWM.img On the phone you might get a message about size mismatch, just ignore it. Now you have to enter the newly flashed CWM recovery. Take your phone and: Press Volume-Down to scroll to the Recovery menu item Press Volume-Up to select that item (yes, Vol-Up selects) The phone will boot into recovery Now is a good time to backup your system. Press Volume-Down to scroll to Backup and Restore Press Power to select that item Press Volume-Down to scroll to Backup to /sdcard Press Power to select that item Backup will commence, once it's finished go back to the main menu and select Reboot, then confirm with YES You phone will reboot into the stock ROM. Flash SuperSU Now you can finally flash SuperSU and be done with the whole business. Download the newest SuperSU and save the file to your phone's SD-Card's root directory. The phone should show up as an MTP device in Windows file explorer. In ADB-Tools folder type: Code: adb reboot recovery The phone will reboot and once CWM Recovery has come up, use the Vol-Up/Down keys to scroll and Power to select Select Install zip Select zip from /sdcard Select /0 You should find a file like UPDATE-SuperSU-v1.94.zip there. Select that file, confirm YES and wait for the flashing to finish Go back to the Main menu and select Reboot, confirm YES The phone should once again reboot into normal stock ROM operation. To check if all went well, open the app drawer, tap on SuperSU and if no error message comes up... You're done!
I hope there are no mistakes anywhere in this guide and also that it might be helpful to some people... Please comment if some things should be changed or improved.
Already guide is there general section.. http://forum.xda-developers.com/showthread.php?t=2585755 But you guide is simple and understandable.. So better stick this thread in this section.. Sent from my XT1032 using XDA Premium 4 mobile app
cdma moto g...? Hey.. what about boost mobile moto g?? Its XT1031 and after pasting that string on motorola website it says your moble's bootloader can't be unlocked??
unlocking the bootloader worked great but it wont let me flash the recovery
keifus.rahn said: unlocking the bootloader worked great but it wont let me flash the recovery Click to expand... Click to collapse How you flashed it? Explain the steps you tried.. Sent from my XT1032 using XDA Premium 4 mobile app
bondisback said: Hey.. what about boost mobile moto g?? Its XT1031 and after pasting that string on motorola website it says your moble's bootloader can't be unlocked?? Click to expand... Click to collapse I followed each step on this guide and i was using it threw android sdk but every time i select recovery on my device it says commands not found this is what i get in my comand prompt- target max sparse size error cant load recovery.img
keifus.rahn said: I followed each step on this guide and i was using it threw android sdk but every time i select recovery on my device it says commands not found this is what i get in my comand prompt- target max sparse size error cant load recovery.img Click to expand... Click to collapse Has anyone found success with a boost mobile variant please?
This was the easiest way for me and I used ROM manager to flash my recovery http://www.theandroidcop.com/how-to-root-motorola-moto-g/ Sent from my XT1031 using XDA Premium 4 mobile app
Remove the Spaces bur2000 said: I hope there are no mistakes anywhere in this guide and also that it might be helpful to some people... Please comment if some things should be changed or improved. Click to expand... Click to collapse I had the same problem at first. When you copy and paste the code on the website it put spaces between the code. There cant be any spaces then it will work. Hoped this helps XD
Thanks Great guide, I used it to root my Moto G I got today but I had problems with flashing the Clockworld recovery. It simply would not work, said error. But I tried TWRP and it worked. But I also named it recovery.img and used your command but replaced CVM.img with recovery.img. Got rid of ALL of the bloatware. I was stuck at first because I didn't start the command promt inside of the adb tools folder.
Recovery issue Guys I had a similar issue while flashing the cwm. When I flash it in the first boot it works, I can enter in the interface and can create a backup or flash one, but after a reboot it do not enter again. I tried entering via fastboot -> Recovery and received the dead android icon with the "No command" message. Tried installing via PlayStore and had the same result, even with the TWRP. Any ideas ?
Install TWRP and root LG v10 H901 T-Mobile
Download Search for TWRP recovery for LG V10 H901 (File: twrp-2.8.7.0-h901.img (31.7 MB)) Backup Apps and Data While this process should not wipe any of your data, a backup is highly recommended. Once you install a custom recovery like TWRP, make sure you backup your system, data,etc. from the recovery. It will be helpful in case anything goes wrong. Prerequisites This guide is compatible with LG V10 H901 only. Do not try it on any other devices or variants. Unlocked bootloader is required to install a custom recovery like TWRP on your device. Click here. Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here. Install Motorola USB Drivers on your computer. Open Settings> Developer options and enable USB Debugging on your device. Go to Developer options and enable Allow oem unlock. How to Install TWRP Recovery on LG V10 H901 Download the recovery image file. Extract if in case a zip file. Now transfer the file to your PC where you can easily locate it. Make sure you have setup ADB and fastboot on your PC. Also accept Always allow from this computer when you plug in the device for first time to enable USB Debugging. Now power off your device and unplug it from your PC. Boot into the bootloader or fastboot mode. To do so, press and hold volume down and the power button simultaneously for 5-6 seconds. When you see the bootloader screen, connect your device to the PC using a USB cable.(Choose fasboot if option is available) Alternatively, you can also issue the following command through your cmd or terminal, while connected to the PC in order to boot into the bootloader. "adb reboot bootloader" Navigate to the location where you have placed the recovery file. Rename the recovery file to a simple one, like recovery.img. While the folder with recovery.img file is open, hold shift key on keyboard and right-click on an empty space and select “Open command window here” option to launch a cmd window. Now issue the following command in the command prompt to check your device connectivity "fastboot devices" Now flash custom recovery. Issue the following command for that. "fastboot flash recovery recovery.img" Custom recovery will now be installed on your device. Now boot your phone in recovery mode. You can do this by turning your device off and then press and hold volume down and power keys at the same time. Or you can simply enter the following command. "fastboot boot recovery.img" Once into the recovery, you can backup your current ROM, data, EFS and more. Once you have installed TWRP, you are all set to install custom packages onto the device’s system. Alternatively, while on Linux or Mac OS, you can issue “./fastboot flash recovery recovery.img” command to flash the TWRP recovery. Root As you already have TWRP, simply flash the SuperSU file (version 2.56) to gain root access
@TheJesus @KAsp3rd, thanks guys for everything you've done over the past few days. no shade to @joe01gun but if people are going to use these instructions make sure you search the rest of the forum for what thejesus and kasp3rd put together to get us to this point - definitely appreciated. thanks @joe01gun for putting these additional instructions together.
Your post says the following: Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here. yet, there's no link to the necessary files to "unzip" them. Any suggestions? Thank you for the help, but where do we get fastboot set up on our PCs? Yes, this is getting confusing with the steps outlined above. I followed the first step and had to take out the battery because I was stuck in fastboot screen with small tiny text in the top left that didn't respond to any manipulation with the volume keys on the back of the device and wouldn't restart any way until I took out the battery.
sanjsrik said: Your post says the following: Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here. yet, there's no link to the necessary files to "unzip" them. Any suggestions? Click to expand... Click to collapse I think it's cause he's not allowed to post links yet cause he's too new. I followed this guide http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 You can get twrp from the development forum.
Why Intended to put the information condensed.... Yep....new Links could not be uploaded.
joe01gun said: Intended to put the information condensed.... Yep....new Links could not be uploaded. Click to expand... Click to collapse Your condensed thread is more convoluted than the actual development thread which also includes the links to everything. I'm still wondering why you have install Motorola USB drivers for an LG phone..
Understood Understood
The one on development is straightforward and I managed to make it done. If you don't lock the bootloader back, you will see bootloader unlocked when starting up. If you have root enabled file explorer, you should remove /system/priv-app/adaptclient folder to avoid annoying root request from adapt.
Please use the main dev thread for instructions on what to do, found below. Having duplicates for what is essentially the same thing can cause confusion and just takes up unnecessary space. So I have closed the thread. [Recovery][LG-H901] Unofficial TWRP Forum moderator, matt4321
Toolless Mi A1 rooting guide NOOB FRIENDLY (bootloader, twrp, root, rom)
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?
[GUIDE] [SUPPORT] How to root, optimize, and repair Xiaomi Redmi Go.
The One-for-All Guide to rooting, improving, and fixing various errors in Xiaomi Redmi Go!Hello everyone! This thread that I made is for all people who wants to modify and gain full access, as well as to repair their Xiaomi Redmi Go devices the well-guided way, I've noticed that nobody has made an all-in-one guide for this phone so I decided to do it, this thread will keep on expanding depending on what I will discover about this phone, but for now, here is the thread, i expect that you have at least a little amount of knowledge when it comes to phones such as ADB and Developer Options. What can we do with Xiaomi Redmi Go: 1. We can root it, and the best root manager for this phone is Magisk, SuperSU is also good, but if you're planning to use your phone for mobile banking, then Magisk is right for you. (Unfortunately this isn't true right now due to ctsProfile being hard to manipulate, Redmi Go supports hardware backed key attestation which means your device will definitely be not certified no matter what you do, so until we get a new method, don't root your phone if you want to use apps like Google Pay 2. TWRP is the current custom recovery available for this phone, it has flaws, but its currently the best out there, so its worth the shot to install it, the thread for it will guide you. 3. No custom kernels, people said that they have managed to install AOSP 9 and GSI on this device and made it boot up, but for me, it's better to wait for the official ROM update, after all, the device is still supported. Prerequisites: 1. Xiaomi Redmi Go 2. An internet connection, a strong one is recommended if you want to download a ROM. 3. A computer with SDK Platform Tools ready to use, this is required, the link is here: https://developer.android.com/studio/releases/platform-tools Don't forget to also get its driver! The link is also here: https://developer.android.com/studio/run/win-usb The drivers are tricky to install but I will guide you on doing it in the easiest way possible, please continue on the thread. 4. SD card, your user data will be erased later, better back your files up, this is a warning. 5. Turning on "OEM unlocking" and USB Debugging in Developer Options, this is also really important! Table of contents: 1. Unlocking the bootloader (and setting up ADB) 2. Rooting 3. Applying the custom recovery 4. Additional modifications 5. Stock ROM links 6. Bonus Section WARNING: I am not responsible for anything that happens to your device as you follow my guide, do not blame me if you turned your device into a paperweight, made it explode, made it fly or whatever it may be, you chose to modify this phone and you should be accountable for it, you must know the consequences of what you're doing, try to point your finger at me because of what YOU did and I will laugh at you. I am ready to assist though, so please feel free to ask some questions! Let us begin, this will take several minutes, so please be patient and avoid rushing. 1. Unlocking the bootloader. NOTE: This requires your computer to have SDK Platform Tools extracted to any location as long as its easy to access, and its really complicated to talk about it here, this step doesn't include the method where you request a code from Xiaomi, but I've provided a link for it. A. First, get your phone up, and open the folder on where the SDK Platform Tools are placed, make sure that your in the directory where you see the .exe files of the SDK, now, hold Shift on the keyboard and click "Open Command Prompt here" and type "adb reboot bootloader", without quotes don't forget! This applies to all the steps that I will provide, don't forget to change the USB connection mode of your phone to PTP for it to be detected by ADB! (Only applies to Windows 8/8.1) Once your phone is asking for an authorization, check "Always allow this computer" then tap allow. B. Once your device has been booted up into Fastboot or the bootloader, check first if your device is being detected, type "fastboot devices", if yes then proceed, if no, then stop here for now. 1B. If this happens then you may have to check your drivers and see if its installed correctly, once your device can be seen at "adb devices" it should also been seen in "fastboot devices" and when the phone is in adb sideload, if not then you have to reinstall ADB, get the proper drivers and do it again. C. Now, type "fastboot oem unlock-go", the terminal will warn you that all of your user data will be removed, if you have them backed up then and go ahead and enter the command, if not, then just type "fastboot reboot" and start backing up your files, then do this again. D. The phone will boot up and say "Erasing", to confirm that your phone has its bootloader unlocked, once it boots up again see if it says "Unlocked" on the bottom part of your screen, if there is then congratulations, it should be unlocked at this point. 1D. https://www.getdroidtips.com/unlock-bootloader-xiaomi-redmi-go/, this one particular link provides you on how to unlock the bootloader by entering a certain code, I believe this is a safer method but requires a bit of time, go here if you're interested. NOTE: The phone supports the command "fastboot flashing unlock_critical" if you are going to unlock your phone with the normal command (fastboot oem unlock_go/fastboot flashing unlock), consider using this 2nd command too, what it does is that it allows you to also flash partitions you supposedly don't have access to, just be very careful not to flash any wrong file! It will be useful to make the "flash_all.bat" script work that you can find on the fastboot ROM for this device, more below! Once your bootloader has been unlocked, you can now proceed to the other steps that I provided here, don't forget to enable USB Debugging on your Developer Options. 1.2 Setting up ADB 1. Grab your phone, unlock and open your Developer Options then enable "USB Debugging", then change your connection type to "PTP" if you are using Windows 8/8.1, I am not sure if this is required on 7, but it is not needed on Windows 10. 2. Go to this link: https://developer.android.com/studio/releases/platform-tools and download the .zip file, then extract it to a location that is easy to access, like your desktop. 3. Get the official Google drivers here: https://developer.android.com/studio/run/win-usb download the .zip file as well, and extract it too. 4. Go to the extracted folder of your SDK Platform Tools, and go to the directory where you can see various .exe files such as "adb.exe", now, hold the Shift key then click the Right mouse button, then click "Open command prompt here" If this doesn't work for you, open up CMD with admin rights, then type in cd *the location of your platform tools* say on mine, I will input cd C:\Users\James\Downloads\platform-tools_r31.0.3-windows\platform-tools then enter 5. Open your Device Manager by pressing Windows + R, put "devmgmt.msc" without any quotes then Enter, do not close the Device Manager until you're done with all the steps! And please be fast here too or else ADB will not work, now go to your extracted folder of the Google USB driver, and look for the file "android_winusb.inf", copy the location path of it as you will need the exact location path of the file later, in my case it was "C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\android_winusb.inf". 4A. There are 3 main ADB devices that you have to install, Android ADB Interface, Android Bootloader Interface and Android Composite ADB Interface, so I will divide this into 3 sections, have your Device Manager, and the exact location of the .inf. NOTE: Turn off the internet connection of your computer, why? Because, if you let Windows install the drivers for you, the drivers may be incorrect and will break things apart, as we will encounter several "Unknown devices" in the Device Manager and we have to update them with the extracted files from Google. Android ADB Interface 1. Now, make sure that USB Debugging is enabled, now plug in your phone and let the drivers install WHILE your computer is offline, now go to your Device Manager after the driver installation and you should see that there is a driver named "Android" with an exclamation mark. 2. Select the "Android" driver with an exclamation mark, then click "Update device driver", click "Browse my computer for driver software" then click "Let me pick from the list of devices on my computer", click Next, then click "Have Disk", now, remember the location path you copied earlier? Now paste that path (like C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\) to the white bar under "Copy manufacturers files from:", overwrite the A:\ with your copied path then Browse, select the "android_winusb.inf" and click OK, now, select the "Android ADB Interface", once the driver has been installed and the interface doesn't give errors such as "The device cannot start", then you're good to go. NOTE: If you plug your phone and there is no "Android" device with exclamation mark, you can proceed to try and see if adb detects your device by typing "adb devices" in the command right now, it should be since this is what I experienced when setting up my device in Windows 10, this step usually applies only if you are using Windows 8/8.1 Android Bootloader Interface 1. To test, go to the command prompt you opened earlier, and type "adb devices", the device should now be detected at this point, when it does, type "adb reboot bootloader". 2. Now, make sure USB Debugging is enabled on the device before booting it into bootloader, now plug in your phone again and let the drivers install WHILE your computer is offline, Go to your Device Manager after the driver installation and you should see that there is a driver named "Android" with an exclamation mark. 3. Select the "Android" driver with an exclamation mark, then click "Update device driver", click "Browse my computer for driver software" then click "Let me pick from the list of devices on my computer", click Next, then click "Have Disk", now, remember the location path you copied earlier? Now paste that path (like C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\) to the white bar under "Copy manufacturers files from:", overwrite the A:\ with your copied path then Browse, select the "android_winusb.inf" and click OK, now, select the "Android Bootloader Interface", once the driver has been installed and the interface doesn't give errors such as "The device cannot start", then you're good to go. Android Composite ADB Interface 1. Before proceeding, type "fastboot devices", the device should now also be detected on fastboot, now, type "fastboot reboot", and afterwards, enable "USB Debugging" on the Developer Options, then go your command prompt, then type "adb reboot recovery". 2. Now, now plug in your phone again and let the drivers install WHILE your computer is offline, now go to your Device Manager after the driver installation and you should see that there is a driver named "Android" with an exclamation mark. 3. Select the "Android" driver with an exclamation mark, then click "Update device driver", click "Browse my computer for driver software" then click "Let me pick from the list of devices on my computer", click Next, then click "Have Disk", now, remember the location path you copied earlier? Now paste that path (like C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\) to the white bar under "Copy manufacturers files from:", overwrite the A:\ with your copied path then Browse, select the "android_winusb.inf" and click OK, now, select the "Android Composite ADB Interface", once the driver has been installed and the interface doesn't give errors such as "The device cannot start", then you're good to go. 2. Applying the recovery/custom recovery A. Open up your phone and ensure that USB Debugging has been enabled, now, open up your command prompt just like in Step 1 in Unlocking the Bootloader and type "adb reboot bootloader" B. Next up, type "fastboot flash recovery path/to/recovery.img", substitute the path/to/ with the actual location of your recovery, and please make sure that the name of the image is "recovery.img"! Or else it will not overwrite/update the recovery, you can also put your recovery.img directly within the platform-tools folder so that all you have to type is "fastboot flash recovery recovery.img" then press enter. C. Once your done, reboot the phone and press Volume Up + Power at the same time, and the recovery will start. (You may want to do this else the recovery will be automatically removed and replaced with the stock one) 1C. For the stock recovery, once you press the combination, the phone will say "No command", at this point, hold your Power button and press Volume up one time to get into recovery. https://forum.xda-developers.com/android/development/recovery-twrp-3-3-0-redmi-t3929282 here is the link of the TWRP recovery, I encourage you to follow the steps mentioned in the post properly. WARNING: The fix I provided below is now pushed here for 1 certain reason, before you try to root your phone and do everything else, you must decrypt your internal storage first and it is quite easy, first you must get the decrypt.zip linked in this thread (if the .zip cannot be found, I still have a copy of it), go to TWRP and do "format data", not Wipe Data! How so? Once you reboot to TWRP, it will show you the "Wipe" button, tap that, then the "Format Data" button should show up, this will require you to type in "yes" so type it in, then once it is done formatting, go back to the main TWRP screen, tap "Reboot", then "Reboot to Recovery", afterwards you must go to "Install" then proceed to install the "decrypt.zip", after that you can now flash .zip files from your internal storage too, but beware that you must do this every time you update your device! 3. Rooting your phone A. To get started, install TWRP for your phone first. B. Get the .zip file of Magisk/SuperSU so you can install them, the links are https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 C. Reboot your phone to recovery or just plug it in, open the command prompt again just like in the previous step and put "adb reboot recovery" without quotes. D. Tap "Install" on your TWRP recovery and select the respective installation .zip file of your chosen root management app, and wait for it to finish. 1D. The .zip for both SuperSU and Magisk can be installed through "adb sideload", if incase you don't have an SD card! It may also work with fastboot as well but I need someone to confirm this. E. When it's done, wipe the cache first, then reboot. 1E. If the root management app didn't appear in your phone after boot, just install the APK of it in the Play Store and check if root has been applied, if not, repeat step C and D again. BONUS: It may be useful also to grab EdXposed or LSposed for Magisk and the link is here: https://forum.xda-developers.com/t/...or-of-xposed-oreo-pie-q-r-2020-07-19.4070199/ and here: https://forum.xda-developers.com/t/...e-magisk-module-edxposed-alternative.4228973/, please choose only one! You will use the normal Xposed if you're using a different root management app such as SuperSU, the link is here: https://forum.xda-developers.com/showthread.php?t=3034811 What this does is that if the app is an Xposed/EdXposed/LSposed framework module, any modifications it does to your phone will be based on memory only, it won't modify your phone directly which means your device will be clean, and if it incase the said modification bricks your phone, you can easily recover from it too! BONUS 2: I also recommend getting the Busybox module from Magisk itself, it can easily be downloaded from the Magisk app, you will need this module if you want your root applications to work more efficiently and avoid errors, as most of them requires Busybox to work, don't use the Busybox installer apps on Play Store as they modify /system directly, only use it if you are using SuperSU. 4. Additional modifications Once you've managed to root your phone and everything else, what I recommend you could do with your device is to get the following apps: Titanium Backup - It has the ability to back up apps on your phone, and even its data! this app could do so much more than with what I just mentioned. LSpeed - A root boosting app that has almost every root tweak packed into it, its really convenient to use! I do not recommend using Entropy tweaks as I heard it is a placebo. Greenify - For me, this is the only legit battery saving app aside from LSpeed which also offers tons of battery saving features, it requires Xposed to have more options you have to buy it to gain full functionality ROM Toolbox - This app pretty much contains everything a rooted user needs, such as a terminal and root-based file manager. System app uninstaller (optional) - Just in case if you're planning to remove some bloatware (the list of it is below) Root Browser - An alternative to ROM Toolbox, this root explorer is really popular and gets the job done without any interruptions. Terminal emulator - This will allow you to enter various commands on your phone, like being able to reboot the phone without using any keys. In order to make the phone as fluid as possible, just leave it with stock ROM installed, try to also use lite apps like Facebook Lite to reduce RAM and battery consumption. Kernel Adiutor - Another great root application, it's like LSpeed but it doesn't automate tweaks, it instead allows you to modify most of it on your own, then it reapplies your tweaks every time your cellphone will boot up if you tap the "Apply on startup" switch. the link for the app is here: https://m.apkpure.com/kernel-adiutor-root/com.grarak.kerneladiutor NOTE: Most of these apps can be found on the Play Store, and please don't install any more similar root boosting apps such as HEBF, scripts such as V6 Supercharger, or modifying files like build.prop, it is due to the fact that this will conflict with LSpeed, as LSpeed contains most of the tweaks that past scripts and apps provide, this will result in your phone slowing down a lot, Greenify will require Xposed Framework which is mentioned above on the Rooting section, the link to LSpeed is here https://github.com/Paget96/LSpeed, because the app has been removed from Play Store. WARNING: The perf.zip https://forum.xda-developers.com/android/development/-t3935220 here, that was provided in Xiaomi Redmi Go forum section must be applied with extreme caution, you have to make a backup of your build.prop in /system, and build.prop + default.prop in /vendor for easy recovery, you can use ZipMe to easily make a backup for these files. 5. Stock ROM links https://xiaomirom.com/en/rom/redmi-go-tiare-global-fastboot-recovery-rom/, this link so far provides all the ROMs (both recovery and fastboot) available for download on this phone, and they are actually light enough, so it will be easy to download them. https://xiaomifirmwareupdater.com/archive/miui/tiare/ a new link I've found recently, this rom contains the .tgz format of the latest ROM for the Xiaomi Redmi Go, which could be used for fastboot and Mi Flash Tool, just search for the model and go for Global. NOTE: Most of the ROMs for this phone provided on several sites, even on the actual Xiaomi website, has an invalid format of .zip, and doesn't contain a flashall script, as a result, Mi Flash Tool will never be able to use these ROMs, you could not also use adb sideload and fastboot for these ROMs, only the stock recovery of the phone could install the ROM, due to the links provided above finally giving the latest ROM versions for the phone, extracting the stock recovery is very easy now, you can do it yourself but if you need a link, tell me. 5A. Applying the stock ROM This section will be divided into 2 sections, flashing the ROM through recovery, flashing the ROM through fastboot manually, or automatically with flash_all.bat Stock recovery method. A. Download the stock ROM with .zip format and put it into your SD Card. B. Flash your recovery back to stock with the steps given above, boot into your stock recovery, then using your Power button and volume keys to navigate, select "Apply update from SD card". C. Select the .zip file and wait for the update to finish. D. The device will boot up automatically after, if not, just go back to the main menu of the recovery and select "Reboot system", enjoy! Fastboot manual flashing method. A. Ensure that you have prepared your device and computer for ADB, now grab the ROM given in this thread in .tgz format, and keep extracting the file until you see the files such as "flash-all.sh" after extraction, as you need to extract the .tgz ROM two times before you could use it properly. B. Now go to the extracted folder of the stock ROM, go the "images" folder and copy the following image files: boot.img, system.img, recovery.img (make a backup of this file somewhere!), vendor.img, cache.img, userdata.img, persist.img, and splash.img. C. Paste them to the extracted folder of your SDK Platform Tools where various .exe files are located such as "adb.exe", or in my case the location is "C:\Users\Symphony\Downloads\platform-tools_r29.0.4-windows\platform-tools". D. Now open your command prompt on this directory, or Shift + Right click, then plug in your phone, now type "adb reboot bootloader" so your phone will go to bootloader, don't forget to enable "USB Debugging" and PTP connection mode before rebooting! (only applies to Windows 8/8.1, it may vary on Windows 7 but it is different on 10, no need for PTP connection mode, you can just turn on USB debugging and that's all) E. Now, this is a little tricky, but try to follow me as much as you can, make sure first that you are detected with "fastboot devices", input the following commands that I will give so you can flash the ROM to your phone, now go to the command prompt and: To flash the boot.img to your phone, put the command: "fastboot flash boot boot.img" For the recovery, the command is: "fastboot flash recovery recovery.img" For the system or main OS: "fastboot flash system system.img" For cache: "fastboot flash cache cache.img" For persist: "fastboot flash persist persist.img" For the vendor or additional system files: "fastboot flash vendor vendor.img" For data or apps: "fastboot flash userdata userdata.img" For splash or probably boot animation: "fastboot flash splash splash.img" D. After that, type "fastboot reboot", and enjoy! Fastboot automatic flashing method (NEW!) A. Extract the fastboot ROM 2 times as instructed, after getting the files, grab all the files and copy it to the directory of your platform tools where files such as "adb.exe" can be found, just copy all the files in there and that's all you have to do. B. Open the "flash_all.bat" on Notepad and remove the following lines: fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *tiare" || echo Missmatching image and device fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *tiare" || exit /B 1 Afterwards, save the .bat file, that should be ready to use now C. As instructed above, you must also do "fastboot flashing unlock_critical" after unlocking your bootloader the normal way, this will act as your 2nd unlock command, without this, the flash_all.bat will not work as it should be. D. Boot up your phone in fastboot mode, open up your adb devices and make sure that your phone is seen in "fastboot devices", once it does, type in "flash_all.bat" without any quotes and execute it, the command will now automatically flash everything without you doing anything else, it will also automatically reboot after doing so. Bonus section: 1. TWRP-compatible stock ROM For this part, in order for you to generate a TWRP-flashable stock ROM is by basically making it yourself, you have to make sure that your patch is latest, and its pretty much a good idea to just tick everything in the backup selection except for the recovery, as well as the cache as you don't need those. Once you have it, go ahead and keep it somewhere safe but easy to find, so if case that you need to use it, you could get it immediately, this is extremely useful so please just do it, as of now, I've confirmed that only the /data backup was usable, but please try to confirm if other partition backups are working for you. Certain custom ROMs that can boot up in this device could be flashed through TWRP though, and the links of them are provided here in this thread. 2. GSI, AOSP 9 and custom ROMs The link for AOSP is provided here: https://forum.xda-developers.com/android/development/redmi-aosp-9-t3922192 The link for GSI is right here: https://forum.xda-developers.com/android/general/tested-gsi-redmi-t3924705 These images/ROMs can be applied with TWRP, just make sure to follow the steps mentioned in these posts to avoid inconvenience, don't forget to take precautions too! I haven't tried them, but so far I believe that these are stable to use. There are also custom ROMs released for the device but I am lazy to link all of them, they can easily be found by going here: https://forum.xda-developers.com/tags/xiaomi-redmi-go/ Please take note that I haven't tested these custom ROMs yet and I most likely never will, since the stock ROM for the device is already good enough, you can comment here and tell me what custom ROMs are stable so I can link them here for future reference. 3. Current status My phone is still working, yes! and it's still staying strong, updated to 2.25 using the fastboot method and it is still fast, the only issue currently is that SafetyNet is a lot more secure than before, so it will be impossible to use stuff like Google Pay for now. I usually decided to lay low and just stay with my LSpeed, Kernel Adiutor and Greenify, all I had to do is to tinker with these apps and my phone just reached into a whole new level! The performance improvement is nice, that I didn't need to use a custom ROM anymore. 4. How to install a OTA update after rooting your device Due to the changes made by Google on SafetyNet, and the fact that this device will always require you to wipe the device every update, it is pretty much the same, it doesn't matter anymore if you are certified or not, you will still receive an OTA update even if your device is not certified as long as you are using the stock ROM, you only won't be able to install it, and if you want to install the OTA update you must install it by flashing the updated fastboot ROM, I have links for it above, you can try installing the OTA updates yourself through the settings but you will still have to do a factory reset anyway, you have to also unroot also and revert to stock recovery, else the installation will fail, and your device may slower afterwards. 5. Bloatware you can safely remove (NEW!) So, like I said above, as much as how lightweight the device is, there are still bloatware that you can remove if you really want, but it's only 3 of them: Mi Video Mint Browser Mi Music The rest such as Mi Share and Mint Launcher are also bloatware, you can remove them but to me they are useful so I didn't, do not remove the "Cleaner" app, if it however says something like "com.CleanMaster", you can try removing it but take caution as your Play Store may be removed along with it too. Credits to everyone who made the apps/tools that I mentioned here! such as @topjohnwu for the Magisk, and @YasiR Siddiqui for the TWRP, @Paget96 for the awesome LSpeed app, @rovo89 for the Xposed Framework and many more, you guys totally rock!
Hello and thank you for this tutorial. I'd like to ask. Do You know a way where I can unlock the bootloader without permissions or oem unlock? I have a soft-bricked device and for me, there is no way I can get into the OS and manually switch the Oem unlock setting. I've tried different softwares, different adb commands, different region firmwares, still no luck. I can't also get into the the download mode. I mean, yeah, I get the "no command" screen but after pressing power button + up volume button my phone restarts into the fastboot mode and there is no way I can normally boot. It's looping to fastboot mode over and over...
TheAngryGuitarist said: Hello and thank you for this tutorial. I'd like to ask. Do You know a way where I can unlock the bootloader without permissions or oem unlock? I have a soft-bricked device and for me, there is no way I can get into the OS and manually switch the Oem unlock setting. I've tried different softwares, different adb commands, different region firmwares, still no luck. I can't also get into the the download mode. I mean, yeah, I get the "no command" screen but after pressing power button + up volume button my phone restarts into the fastboot mode and there is no way I can normally boot. It's looping to fastboot mode over and over... Click to expand... Click to collapse Can you please elaborate all of what you've done so far? I will also ask you a few questions. 1. Is your phone usable with the platform tools? I mean with adb and such. 2. Did you try going into recovery and flashing stock ROM through there? 3. Is your phone being detected by "fastboot devices"? The fastboot mode of Redmi Go is its download mode, and i've provided the link for the stock ROM that's usable thru fastboot mode, as well as on how to apply it.
My phone is usable with adb and such, the recovery mode was not working, only the fastboot. I've tried flashing stock rom with the flash tool but I had no success with a bricked soft and a locked bootloader. I've finally fixed it by going into the edl mode by test point method then I flashed the stock rom, and I've fixed my problem this way. I couldn't unlock the bootloader manually from adb or the unlocker tool, but I've did it in the edl way.
TheAngryGuitarist said: Hello and thank you for this tutorial. I'd like to ask. Do You know a way where I can unlock the bootloader without permissions or oem unlock? I have a soft-bricked device and for me, there is no way I can get into the OS and manually switch the Oem unlock setting. I've tried different softwares, different adb commands, different region firmwares, still no luck. I can't also get into the the download mode. I mean, yeah, I get the "no command" screen but after pressing power button + up volume button my phone restarts into the fastboot mode and there is no way I can normally boot. It's looping to fastboot mode over and over... Click to expand... Click to collapse TheAngryGuitarist said: My phone is usable with adb and such, the recovery mode was not working, only the fastboot. I've tried flashing stock rom with the flash tool but I had no success with a bricked soft and a locked bootloader. I've finally fixed it by going into the edl mode by test point method then I flashed the stock rom, and I've fixed my problem this way. I couldn't unlock the bootloader manually from adb or the unlocker tool, but I've did it in the edl way. Click to expand... Click to collapse Can you please elaborate the term "edl mode"? Good job then, usually, before you modify the phone and start doing something crazy out of stock, your number one step is to really unlock the bootloader, and in order to make things more easier, you should allow your OEM to be unlocked through the developer options, after that you can now unlock the bootloader with fastboot.
_XblackshadowX_ said: Can you please elaborate the term "edl mode"? Good job then, usually, before you modify the phone and start doing something crazy out of stock, your number one step is to really unlock the bootloader, and in order to make things more easier, you should allow your OEM to be unlocked through the developer options, after that you can now unlock the bootloader with fastboot. Click to expand... Click to collapse Yes, it's the emergency download mode. You use it when there is nothing you can do about the soft of your device. It automatically unlock the bootloader and you can flash the stock rom. Well, my problem was another. I did not tried to flash roms or recoveries with a locked bl. My phone automatically rebooted into the fastboot mode and from there I was not able to start my phone normally. I've tried rebooting fastboot from adb, unlock bl from adb, no success. I had to dissamembly the phone and make a short-circuit to the test points while slowly pushing in the mtp cable with the battery disconnected. Once I saw the Qualcomm driver on device manager I was able to flash the stock rom. You can search if you want to, for the test pins of this device. Btw, thank for your advice, you are really helpful to the community! ?
TheAngryGuitarist said: Yes, it's the emergency download mode. You use it when there is nothing you can do about the soft of your device. It automatically unlock the bootloader and you can flash the stock rom. Well, my problem was another. I did not tried to flash roms or recoveries with a locked bl. My phone automatically rebooted into the fastboot mode and from there I was not able to start my phone normally. I've tried rebooting fastboot from adb, unlock bl from adb, no success. I had to dissamembly the phone and make a short-circuit to the test points while slowly pushing in the mtp cable with the battery disconnected. Once I saw the Qualcomm driver on device manager I was able to flash the stock rom. You can search if you want to, for the test pins of this device. Btw, thank for your advice, you are really helpful to the community! Click to expand... Click to collapse Woah, you really had to open the phone before doing it, that's an interesting method! That part where your phone booted into fastboot was kind of scary, any ideas why it booted into fastboot in the first place? It has to be reported if incase, seems like a dangerous bug.
_XblackshadowX_ said: Woah, you really had to open the phone before doing it, that's an interesting method! That part where your phone booted into fastboot was kind of scary, any ideas why it booted into fastboot in the first place? It has to be reported if incase, seems like a dangerous bug. Click to expand... Click to collapse I'm not really sure if a malware caused this issue or a failed system update over-night.
TheAngryGuitarist said: I'm not really sure if a malware caused this issue or a failed system update over-night. Click to expand... Click to collapse I usually had failed system updates numerous times because when i install them, the phone has already been modified by a lot, and that's actually riskier. That's why i recommend unrooting and putting back the stock recovery before updating first, still works on mine even with "Device is not certified" by Play Store.
The TWRP linked here is for Pie 9, I couldn't get it to boot on my phone, it shows vertical lines. This is the older version for Oreo 8... https://forum.xda-developers.com/android/general/twrp-xiaomi-redmi-beta-t3918993 I formatted the phone from TWRP it so it was no longer encrypted. Mounted the drive from TWRP and installed the "decrypt.zip" from the other TWRP... https://forum.xda-developers.com/android/development/recovery-twrp-3-3-0-redmi-t3929282
I unlocked the bootloader successfully. In the setting up ADB step, I don't clearly understand. When I connect my device to the pc, no drivers are installing. And there is no driver named "Android" with an exclamation mark. But my device is getting recognized in "portable devices >> redmi go". I'm very new with adb it would be a lot of help. I've attached the screenshot of my device manager,
bhattinb said: I unlocked the bootloader successfully. In the setting up ADB step, I don't clearly understand. When I connect my device to the pc, no drivers are installing. And there is no driver named "Android" with an exclamation mark. But my device is getting recognized in "portable devices >> redmi go". I'm very new with adb it would be a lot of help. I've attached the screenshot of my device manager, Click to expand... Click to collapse Did you try turning on USB Debugging on Developer Options? Did you try installing the USB drivers from Google?
_XblackshadowX_ said: Did you try turning on USB Debugging on Developer Options? Did you try installing the USB drivers from Google? Click to expand... Click to collapse Yeah, I've done everything you told, I also turned the connection mode to PTP also. Somehow it just not showing that android with an exclamation mark. after that, I even tried to use the 15-second ADB installer. after installing that I tried to flash recovery but that just didn't do anything. After using that flashing command, I had the same stock recovery. I'm really thankful you took the time to answer my question.
Help!! My device stuck on screen saying your system has been destroyed. What I had done is locked the bootloader using command fastboot oem lock then this happened. Now i can boot device in stock recovery and bootloader too but when i am trying to unlock bootloader it says device is lock and also i am not able to flash anything. Plz help.
I am not able to flash TWRP on my redmi go
How to update the redmi go to the latest version without formatting/Factory Reset should I just follow Fastboot flashing method and if so which files should I just flash. Thank you
bhattinb said: I unlocked the bootloader successfully. In the setting up ADB step, I don't clearly understand. When I connect my device to the pc, no drivers are installing. And there is no driver named "Android" with an exclamation mark. But my device is getting recognized in "portable devices >> redmi go". I'm very new with adb it would be a lot of help. I've attached the screenshot of my device manager, Click to expand... Click to collapse Hi! sorry for the late reply, if this is the case then it's fine, you can just connect the device, open up adb tools, type adb devices and ensure that your USB debugging is on, and the device will connect immediately, at that point all you need is the adb driver for Fastboot
akki_007 said: Help!! My device stuck on screen saying your system has been destroyed. What I had done is locked the bootloader using command fastboot oem lock then this happened. Now i can boot device in stock recovery and bootloader too but when i am trying to unlock bootloader it says device is lock and also i am not able to flash anything. Plz help. Click to expand... Click to collapse oh no, but why lock your bootloader? you can try using a recovery ROM, you must have a spare SD Card within you, grab a recovery ROM, put it in your sd card then put it into the phone and use it on stock recovery, you should be able to apply it and boot back into the system, please update me
igpraan said: I am not able to flash TWRP on my redmi go Click to expand... Click to collapse you must have unlocked bootloader if you want to do so.
niknah said: The TWRP linked here is for Pie 9, I couldn't get it to boot on my phone, it shows vertical lines. This is the older version for Oreo 8... https://forum.xda-developers.com/android/general/twrp-xiaomi-redmi-beta-t3918993 I formatted the phone from TWRP it so it was no longer encrypted. Mounted the drive from TWRP and installed the "decrypt.zip" from the other TWRP... https://forum.xda-developers.com/android/development/recovery-twrp-3-3-0-redmi-t3929282 Click to expand... Click to collapse that's strange, the TWRP I linked isn't giving me any vertical lines