Related
Hello everyone,
I wrote this walkthrough to show you how to unlock the bootloader,install custom recovery and gain root privileges on your Android One by using Linux.
Some of the instructions in this guide are not mandatory to accomplish the task but I decided to include them anyway just for informational purposes because this guide is intended for novice users.
This is my personal method and I will provide you with detailed information to avoid mistakes so read carefully and have fun.
Requisites:
*Backup your data before proceeding!
*Android One
*A Linux distro (Debian/Ubuntu/Mint/ElementryOS or etc)
*android_one_root.zip (Download it from http ://goo.gl/B3LjRJ ) [Note: Remove spaces from the link ]
Let's begin.
Chapter 1: Developer options, Android debugging & Android Tools
Phase 1: Developer options and Android debugging.
Go to Settings > About phone and tap 7 times on Build number to enable Developer options. You will see a little pop-up that says "You have enabled development settings!".
Go back to Settings menu and scroll down to Developer options. Tap on it and then enable Android debugging. You will be asked to allow USB Debugging, confirm by tapping on OK.
Phase 2: Installing Android tools (ADB & Fastboot) on Linux. (I'm using Ubuntu 15.04 here)
Open Terminal and run this command to install ADB and Fastboot tools:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Chapter 2: Unlock the bootloader.
In this chapter we will focus on the Linux Terminal rather than the phone. Don't be scared, it will be easy enough and you will have the opportunity to learn something new. :fingers-crossed:
Now you can connect your Android One phone to your computer.
Once your phone has been connected to your pc, open the Terminal and run this command:
Code:
adb devices
Check the phone. Your computer's RSA fingerprint will be shown and you will be asked to allow USB debugging. Confirm by tapping on OK.
Note: If you see offline instead of device, run the adb devices command once again.
If adb devices output looks like this:
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
???????????? no permissions
Run these commands:
Code:
sudo adb kill-server
sudo adb start-server
sudo adb devices
Put yourphone in Fastboot Mode by running this command:
Code:
adb reboot-bootloader
EASY WAY: You can put your phone in Fastboot Mode by holding down Power button and Volume up simultaneously for few seconds (it works either phone on or off).
Commands in Fastboot Mode need Administrator privileges on your pc, that's why we will use sudo.
Run this command to make sure that Fastboot Mode is working correctly:
Code:
sudo fastboot devices
Next command will unlock the bootloader:
Code:
sudo fastboot oem unlock
The phone will reboot and it will restore factory settings. All personal data and settings will be lost.
Once the reboot is complete, download & extarct the "android_one_root.zip" file to your pc.Now copy both "eu.chainfire.supersu.apk" and "update.zip" file to your phones sd card.Then install "eu.chainfire.supersu.apk" in your phone.
Then put the device back in Fastboot Mode by holding down Power button and Volume up simultaneously for few seconds (it works either phone on or off).
Chapter 3: Install Custom Recovery.
You will find three custom recovery in the archive.Choose one of them. (I'm using TWRP here)
So put the recovery's .img file on your pc's Desktop.
On Terminal, change the current working directory by running this command: (Change Desktop to ypur current working directory)
Code:
cd Desktop
nstall TWRP Recovery by running this command: (If you want to flash CWM/PHILZ recovery,just replace TWRP.img to CWM.img/PHILZ.img )
Code:
sudo fastboot flash recovery TWRP.img
Now it's time to enter Recovery Mode. To do that, hold down Power button and Volume up.
In TWRP Recovery tap on Install, scroll down to the update.zip archive and select it. Perform a swipe to confirm the installation and lastly reboot your phone.
Once the reboot is complete, go to google play store and install "Root Checker" to check your device root status.
Congratulations, you made it!
If you are using phliz recovery mode
before install custom recovery format userdata
code
sudo fastboot format userdata
otherwise it will stuck in recovery mode
somehow I managed to install the OTA MM update that I was holding off until I could unlock, root, blah, blah, blah.
I'm now on 20i.
And it responds to adb (v1.032) and fastboot commands from Terminal on my OSX MacBook Air.
Has anyone "authorized" (aka - fastboot oem unlock) their 811 and flashed TWRP from a Mavs Mac ?
Or do I need to go to my Bootcamp partition to accomplish?
Seems like to should work from Mavs direct, but …….
Bootcamp not needed.
system settings (tap on Build number until it says you’re a developer.)/developer/check oem unlock & USB debug
USB connect to Mac. I use Android File Transfer. I found it less annoying and very fast.
But it will not work with the LG drivers installed. aka LGUnitedMobileMacDriver_v4.23.zip, or LGMobileMacDriver_v5.2.zip, or LGBridge_Mac.dmg.
in Terminal:
adb devices - should reveal the devices serial - LGH811xxxxxxxxx. If not, your Mac and adb/fastboot are not set up properly.
adb reboot bootloader
fastboot devices - should reveal serial again. xxxxxxxx
fastboot oem unlock - this will WIPE the G4s internal SD that comes with the phone.
fastboot getvar unlocked - to confirm unlock
fastboot reboot - and set-up as a new device.
If you're on MM, and you set it up previously, restore should happen automatically upon reboot, after you enter your google or ID, etc.
If it seems to be taking too long, restart.
Make sure you recheck that USB debug is checked in developer options.
and then to flash TWRP and SuperSu so as to root.
Terminal:
adb reboot bootloader
fastboot boot (drag and drop the {I shortened the name of the file after duping} twrp.img into the Terminal window)
This will boot you into a temporary TWRP recovery. (v2.8.7.2)
Install twrp.img (select zip or img button bottom right)
Then install SuperSu 2.6.7.zip.
REBOOT SYSTEM
check root -
Terminal:
adb shell. should get #. if not - su. should get #.
troubleshooting.
May have to re-enter developer mode
sys settings/about/software/more/tap build number 7 times fast.
unplug USB.
Toggle USB debugging in Developer. Should get prompt about RSA.
re-plug USB
adb kill-server
adb devices
If TWRP isn't recognizing your b.u., write a new back-up. This creates the path TWRP wants to see. Copy your old b.u. into the new folder:
TWRP/BACKUPS/LGH811#########/2016-10-23--15-58-36_MRA58K
RenameÂ*the old b.u. the same as the new b.u. and toss the new one.
Reboot Recovery and you now should now able to to restore from the old b.u.
I have mi a2 with android 10 stock rom. Never unlocked bootloader. Now, I want to flash it back to android 9. Could some one please tell me how to do it? Thank you
So, you are writer, not reader (hint: search works well in these forums), but here is a brief:
1. Save all your data to google cloud, to PC, etc. (there are numerous 3rd party tools, for example SMSBackupRestore, MyPhoneExplorer, etc., which enable partial backups of your data);
2. Get developers rights in phone (search here for instructions), and in "Developers options" check "OEM unlocking" and "USB debugging" to ON; "Automatic system updates" to OFF;
3. Download and unpack latest https://developer.android.com/studio/releases/platform-tools, get somewhat acquainted with Android ADB and fastboot commands;
4. Ensure that "Android Device" drivers are correctly installed:
- attach phone in "No data transfer", "File transfer" (MTP), stock recovery and fastboot (bootloader) modes (search here for instructions to go to fastboot and stock recovery modes), and ensure that DeviceManager shows "Android Device" drivers working in each mode;
- possible Capcha here: MiA2 is very selective in work with PC motherboard USB subsystem, usually needs to be connected to USB2.x port to operate via ADB/fastboot;
- open CMD shell with administrative rights in the dir platform-tools were unpacked to, attach phone in "File transfer" (MTP), stock recovery and fastboot (bootloader) modes and ensure that following commands return valid responses:
Code:
ADB devices - l
in first 2 modes, and
Code:
fastboot devices
in bootloader mode;
- Capcha here: phone will prompt to approve PC for USB debugging, you'll need to approve, checking "do not ask again" is reasonable;
5. switch phone to bootloader mode (by phone buttons or with 'ADB reboot bootloader' command) and unlock phone with 2 commands (rebooting phone each time):
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
- in bootloader mode in CMD shell type "fastboot getvar all" and see is phone is really unlocked, what is current slot, etc.
6. Download Android 9.0 [V10.0.17.0.PDIMIXM] from https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849 (last V10.0.18.0 had bugs) and unpack it (note that ROM image is packed twice) to the dir platform-tools were unpacked to (or copy of this dir);
7. Open CMD shell with administrative rights in the prepared dir (if not done before), attach phone in fastboot (bootloader) mode and type in flash_all command thus starting "flash_all.bat" command file;
- executing this file will erase user data;
- read output of fashing process in CMD window to be aware of possible errors;
8. It is recommended to make factory reset after changing major Android versions, either from stock recovery (Capcha: seeing "No command" press Power and click Vol+ to see list of commands), or from CMD shell with "fastboot -w" command.
9. Make initial phone setup again.
Note: you may try to skip steps 8 (wiping) and 9, and in step 7 use "flash_all_except_data.bat" command in attempt to preserve /data partition in phone, but I am pretty much sure that factory reset would be needed if not immediately than in a day or two.
Hello,
despite presumably doing everything correctly, Tool spews this error when I'm trying to relock the BL by using "fastboot oem asus-lock" command:
FAILED (remote: 'Command not supported in default implementation')
1. I have connected the phone to the side port.
2. Tool folder is directly in C:\ directory.
3. ADB binaries are installed correctly.
4. Phone is in fastboot mode and detected, but the tool cannot detect correctly which phone it is and asks me to choose the model manually, but ROG 3 is not on the list, so I chose ROG Phone 2. Does it matter? If so, what do I do? I also set priviledges for Tool-all-in-one systemwide, does it matter?
Also, should I use the command line in Advanced Options of the tool, or should I rightclick the folder and summon the command line from there? Please help, I don't have any more ideas! Thank you!
use the side usb port (the top black one, not the bottom orange one) and try the command again through FB
Thank you for fast response!
I'm constantly using the sideport, and the command still fails with the message above.
What I can add is that EVERY fastboot process fails with the SAME message, so it's not just relocking that is the problem, but it seems that every fastboot command cannot be executed on my ROG Phone 3 (aside from fastboot devices, which correctly shows my device as connected).
Which suggests to me that something is wrong with my setup. Anybody has any idea?
When I try to relock my rog phone 3 I do the list devices command and it shows my device, I then reboot into fastboot
and type command fastboot oem asus-lock and all it says is <waiting for device> how can I relock bootloader???????? If there was an apk to unlock it shouldnt there be an apk to relock it?
You need install fastboot drivers on your pc, so device manager will see your phone
When I open PowerShell and run the command "fastboot devices" my phone isn't getting detected. My phone is connected to my PC, I've installed platform tools & adb as well as the correct ROM. I'm pretty new to rooting so I'm not sure what's going on. I don't have a SIM Card so that might be the issue, but I'm trying to find a root guide that doesn't require sim.
What I've installed;
Latest USB Driver (MTP USB Device)
Latest ADB/Fastboot from android.com/studio/releases/platform-tools
Installed Fastboot ROM MIUI V13.0.6.0.SKDMIXM Stable from https://xiaomirom.com/en/rom/xiaomi.../#download-xiaomi-11t-pro-stable-fastboot-rom
Device Specs:
- MIUI Global 13.0.6 Stable (SKDMIXM)
- Android ver. 12 SKQ1.211006.001
Following this guide to root and have been following step by step up to 3:12:
WhalePC said:
When I open PowerShell and run the command "fastboot devices" my phone isn't getting detected. My phone is connected to my PC, I've installed platform tools & adb as well as the correct ROM. Not sure what's going on.
Following this guide to root and have been following step by step up to 3:12:
Click to expand...
Click to collapse
Maybe you summarized the command in your statement but with power shell the command is "./fastboot devices"
Do you see the device icon in the taskbar?
NOSS8 said:
Maybe you summarized the command in your statement but with power shell the command is "./fastboot devices"
Do you see the device icon in the taskbar?
Click to expand...
Click to collapse
Yeah i see the icon on my taskbar. Just tried running it via "./fastboot devices" and no devices show up. I haven't unlocked the bootloader yet (haven't enabled Mi Unlock status) yet is that maybe the issue? If so, is there a way to root without the need of a sim card?
WhalePC said:
Yeah i see the icon on my taskbar. Just tried running it via "./fastboot devices" and no devices show up. I haven't unlocked the bootloader yet (haven't enabled Mi Unlock status) yet is that maybe the issue? If so, is there a way to root without the need of a sim card?
Click to expand...
Click to collapse
You generally shouldn't need a SIM card to use ADB or fastboot commands.
Are you sure you have the correct drivers installed? Does the device appear under adb devices when in Android?
V0latyle said:
You generally shouldn't need a SIM card to use ADB or fastboot commands.
Are you sure you have the correct drivers installed? Does the device appear under adb devices when in Android?
Click to expand...
Click to collapse
How do i check that I have the correct drivers installed? I ran adb devices and it showed my device 3d37ace2 device was connected.
EDIT: Here's how I enter into fastboot and excute commands;
- Plug in phone into PC and wait for icon to show up on taskbar
- Open Powershell in platform-tools folder
- Power off phone and enter fastboot (hold down power button+vol down)
- Once Fastboot text shows up on my phone I run the command "fastboot devices" in powershell
WhalePC said:
How do i check that I have the correct drivers installed? I ran adb devices and it showed my device 3d37ace2 device was connected.
EDIT: Here's how I enter into fastboot and excute commands;
- Plug in phone into PC and wait for icon to show up on taskbar
- Open Powershell in platform-tools folder
- Power off phone and enter fastboot (hold down power button+vol down)
- Once Fastboot text shows up on my phone I run the command "fastboot devices" in powershell
Click to expand...
Click to collapse
This looks like a good place to start. It's possible you have a generic ADB driver installed and may need a device specific one.
V0latyle said:
This looks like a good place to start. It's possible you have a generic ADB driver installed and may need a device specific one.
Click to expand...
Click to collapse
Just reinstalled the latest ADB/Fastboot from https://androidmtk.com/download-15-seconds-adb-installer and still have the same issue. I also installed Xiaomi AB/Fastboot Tools to check if it can identify my device and it does.
Running adb shell in cmd prompt outputs:
Code:
C:\Users\Whale>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
vili:/ $
But once it's in fastboot it responds with:
Code:
C:\Users\Whale>adb shell
adb.exe: no devices/emulators found
Same for Powershell:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
3d37ace2 device
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
Currently, when my phone is turned on (not in fastboot), my device is detected as 3d37ace2 (codename: vili), but as soon as it goes to Fastboot, it no longer can detect the device.
WhalePC said:
Just reinstalled the latest ADB/Fastboot from https://androidmtk.com/download-15-seconds-adb-installer and still have the same issue. I also installed Xiaomi AB/Fastboot Tools to check if it can identify my device and it does.
Running adb shell in cmd prompt outputs:
Code:
C:\Users\Whale>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
vili:/ $
But once it's in fastboot it responds with:
Code:
C:\Users\Whale>adb shell
adb.exe: no devices/emulators found
Same for Powershell:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
3d37ace2 device
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
Currently, when my phone is turned on (not in fastboot), my device is detected as 3d37ace2 (codename: vili), but as soon as it goes to Fastboot, it no longer can detect the device.
Click to expand...
Click to collapse
ADB commands won't work in fastboot and vice versa. When your device is in Android or recovery, you can use ADB commands, but when it's in bootloader mode, you have to use fastboot commands. ADB shell won't do anything for you in fastboot because there's no kernel running, much less a shell.
Since your device isn't appearing under fastboot devices it's most likely a driver issue. You need two separate drivers; the ADB driver is not device specific, but the bootloader driver is.
Case in point: This is what appears when my Pixel 5 is connected while booted into Android:
When I reboot to bootloader, this is what I see:
So, this is what I suggest:
Reboot to bootloader, connect to your PC, and look at Device Manager to see if anything comes up as unrecognized. Make sure it's the right device by unplugging the USB cable; it should disappear. You'll then need to update the driver, and point it to the the Xiaomi driver folder.
V0latyle said:
ADB commands won't work in fastboot and vice versa. When your device is in Android or recovery, you can use ADB commands, but when it's in bootloader mode, you have to use fastboot commands. ADB shell won't do anything for you in fastboot because there's no kernel running, much less a shell.
Since your device isn't appearing under fastboot devices it's most likely a driver issue. You need two separate drivers; the ADB driver is not device specific, but the bootloader driver is.
Case in point: This is what appears when my Pixel 5 is connected while booted into Android:
View attachment 5731657
When I reboot to bootloader, this is what I see:
View attachment 5731663
So, this is what I suggest:
Reboot to bootloader, connect to your PC, and look at Device Manager to see if anything comes up as unrecognized. Make sure it's the right device by unplugging the USB cable; it should disappear. You'll then need to update the driver, and point it to the the Xiaomi driver folder.
Click to expand...
Click to collapse
Thanks fam, was able to solve it by installing a different driver from this video:
.
Now I'm getting an error:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot flash boot magisk_patched.img
Sending 'boot_a' (196608 KB) OKAY [ 4.210s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
which I assume means I need to unlock my bootloader via Mi Unlock status?
WhalePC said:
Thanks fam, was able to solve it by installing a different driver from this video:
.
Now I'm getting an error:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot flash boot magisk_patched.img
Sending 'boot_a' (196608 KB) OKAY [ 4.210s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
which I assume means I need to unlock my bootloader via Mi Unlock status?
Click to expand...
Click to collapse
Yep. I don't know how it works on Xiaomi devices but try fastboot flashing unlock
Unlocking your bootloader will wipe data, so if you need to back anything up, do that first.
Enter in FASTBOOT MODE: press Power+Volume down button for 4-5 sec in the same time,the phone reboot, at the vibration release the power button.Now plug in the phone to the PC.
Having the bootloader locked does not prevent seeing the device in Fastboot mode.(***Not useful at the moment)
To root you must first unlock the bootloader.(***your bootloader is locked)(FAILED (remote: 'Flashing is not allowed in Lock State')
Unlock the bootloader
You must have a Xiaomi account and a valid sim.
Procedure:
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html
Why look for tutorials on You tube'Sometimes good, sometimes fake) while on XDA(Always good )in the How to section of your device these tutorials exist and specify that the bootloader must be unlocked.
https://forum.xda-developers.com/t/root-xiaomi-11t-pro.4441213/
https://forum.xda-developers.com/t/...structions-for-xiaomi-11t-pro-global.4362515/
check debugging via USB option.
WhalePC said:
When I open PowerShell and run the command "fastboot devices" my phone isn't getting detected. My phone is connected to my PC, I've installed platform tools & adb as well as the correct ROM. I'm pretty new to rooting so I'm not sure what's going on. I don't have a SIM Card so that might be the issue, but I'm trying to find a root guide that doesn't require sim.
What I've installed;
Latest USB Driver (MTP USB Device)
Latest ADB/Fastboot from android.com/studio/releases/platform-tools
Installed Fastboot ROM MIUI V13.0.6.0.SKDMIXM Stable from https://xiaomirom.com/en/rom/xiaomi.../#download-xiaomi-11t-pro-stable-fastboot-rom
Device Specs:
- MIUI Global 13.0.6 Stable (SKDMIXM)
- Android ver. 12 SKQ1.211006.001
Following this guide to root and have been following step by step up to 3:12:
Click to expand...
Click to collapse
You will need to manually configure fastboot drivers.