Related
Hi, I am new to rooting my tablet. I manage to unlock my tablet "asus tf700" but i cannot for the life of me understand how to root this. I have read all the threads/posts regarding this issue but since its my first time i dont understand what "flashing" means or "bootloader". Please any step by step advice is greatly appreciated.
I have the ASUS TF700T Infinity Jellybean Android 4.1.1 I believe it is unlocked because I am able to go into that screen and theres four Icons.
Pms or a step by step guide for this noob because i dont understand any of these terms =(
Sorry for the trouble and thanks in advance
Cheers,
deocare
deocare said:
Hi, I am new to rooting my tablet. I manage to unlock my tablet "asus tf700" but i cannot for the life of me understand how to root this. I have read all the threads/posts regarding this issue but since its my first time i dont understand what "flashing" means or "bootloader". Please any step by step advice is greatly appreciated.
I have the ASUS TF700T Infinity Jellybean Android 4.1.1 I believe it is unlocked because I am able to go into that screen and theres four Icons.
Pms or a step by step guide for this noob because i dont understand any of these terms =(
Sorry for the trouble and thanks in advance
Cheers,
deocare
Click to expand...
Click to collapse
also tried reverting back to ICS to do that auto root but had no idea what "fastlooader" was..
sorry im a total noob at this
deocare said:
also tried reverting back to ICS to do that auto root but had no idea what "fastlooader" was..
sorry im a total noob at this
Click to expand...
Click to collapse
Not too worry, it's very simple, just download the zip, then unzip and double click on the bat file, then follow on screen instruction.
Here is a nice instruction for rooting:
http://tutznet.com/root-tf700t-asus-...-infinity.html
this will work with the specs for my tablet? jellybean etc..?
does not work... i tried this debug already it says failed i think because it doesn't support jellybean.
deocare said:
does not work... i tried this debug already it says failed i think because it doesn't support jellybean.
Click to expand...
Click to collapse
no, it's for ics only, I thought you are on ICS? well you downgrade back to .30 then use my method above, If you don't want to downgrade, then you must unlocked first then follow this method:
http://forum.xda-developers.com/showthread.php?t=1916762
You put your device in fastboot mode, by turn off your device, hold volume down and power button, when you will see white text appeared on the screen release both, hit volume down to navigate to the USB icon, then hit volume up to select and now you are fastboot. plug in your usb cable then open fastboot command on your pc and do your thing.
buhohitr said:
no, it's for ics only, I thought you are on ICS? well you downgrade back to .30 then use my method above, If you don't want to downgrade, then you must unlocked first then follow this method:
http://forum.xda-developers.com/showthread.php?t=1916762
You put your device in fastboot mode, by turn off your device, hold volume down and power button, when you will see white text appeared on the screen release both, hit volume down to navigate to the USB icon, then hit volume up to select and now you are fastboot. plug in your usb cable then open fastboot command on your pc and do your thing.
Click to expand...
Click to collapse
sorry i dont understand that concept of flashing can you go through it with me on how to do it
deocare said:
sorry i dont understand that concept of flashing can you go through it with me on how to do it
Click to expand...
Click to collapse
Not a problem, but I need to verify what your setup first.
1. Are you on Jelly Bean?
2. Are you unlocked? (when you turn on your device, it should displays "device is unlocked"
3. Do you have SDK and fastboot/ADB tool installed on your device?
Once you answered all 3 questions, I will recommend the easiest way to root.
buhohitr said:
Not a problem, but I need to verify what your setup first.
1. Are you on Jelly Bean?
2. Are you unlocked? (when you turn on your device, it should displays "device is unlocked"
3. Do you have SDK and fastboot/ADB tool installed on your device?
Once you answered all 3 questions, I will recommend the easiest way to root.
Click to expand...
Click to collapse
1.yes
2.yes
3. maybe? not sure i have been trying alot of random things trying to root it so im not sure if its installed on my device
deocare said:
1.yes
2.yes
3. maybe? not sure i have been trying alot of random things trying to root it so im not sure if its installed on my device
Click to expand...
Click to collapse
OK, we need to verify if your fastboot is working or not. Put your device in fastboot mode (see my thread above..how to select the usb icon). On your pc, go to the folder that you have fastboot command (should be fastboot.exe). Open window command prompt, navigate to the folder where "fastboot.exe" located (usually located in "platform-tools" folder), then execute this :
type in:
fastboot devices
hti enter, you should be device ID show up
again type:
fastboot reboot
then hit enter
Your device should reboot. If it does, your fastboot is working.
buhohitr said:
OK, we need to verify if your fastboot is working or not. Put your device in fastboot mode (see my thread above..how to select the usb icon). On your pc, go to the folder that you have fastboot command (should be fastboot.exe). Open window command prompt, navigate to the folder where "fastboot.exe" located (usually located in "platform-tools" folder), then execute this :
type in:
fastboot devices
hti enter, you should be device ID show up
again type:
fastboot reboot
then hit enter
Your device should reboot. If it does, your fastboot is working.
Click to expand...
Click to collapse
i dont know where this fastboot.exe is
is there a link i can get it from
deocare said:
i dont know where this fastboot.exe is
is there a link i can get it from
Click to expand...
Click to collapse
Here you go, instruction and fastboot download.
http://forum.xda-developers.com/showpost.php?p=27218675&postcount=20
okay i have no idea it does not work i opend cmd prompt got the bootloader but the commands dont work heres a Screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@deocare
first you have to "cd" into the path wehre you store the fastboot.exe.Ideally you've installed a full android sdk with adb, etc. After setup your android sdk and fastboot, make sure that you're tablet is booted in fastboot mode and you've installed the fastboot drivers, e.g. from universal naked driver package. After this you can send fastboot commands to your tablet but please note that it doesn't answer to fastboot devices.
Here are some threads explaining how to setup fastboot and how to after flashing jellybean, e.g. chainfires SU.
thunderger said:
@deocare
first you have to "cd" into the path wehre you store the fastboot.exe.Ideally you've installed a full android sdk with adb, etc. After setup your android sdk and fastboot, make sure that you're tablet is booted in fastboot mode and you've installed the fastboot drivers, e.g. from universal naked driver package. After this you can send fastboot commands to your tablet but please note that it doesn't answer to fastboot devices.
Here are some threads explaining how to setup fastboot and how to after flashing jellybean, e.g. chainfires SU.
Click to expand...
Click to collapse
I installed the drivers already i believe i checked under portable devices and it says "TF700t transfomer pad.." and I am in booted in fastboot mode with the power+volume down key and went over to the USB icon then opened cmd prompt
deocare said:
I installed the drivers already i believe i checked under portable devices and it says "TF700t transfomer pad.." and I am in booted in fastboot mode with the power+volume down key and went over to the USB icon then opened cmd prompt
Click to expand...
Click to collapse
Based on your screen shot, you put the "fastboot folder" on your desktop. Do this.
open cmd
type:
cd\ then hit enter
you should see:
c:\
now type:
cd users\david\desktop\fastboot then hit enter
you should see
c:\users\david\desktop\fastboot>
now type:
fastboot devices then hit enter
you should see device ID
now type:
fastboot reboot then hit enter
your device should reboot.
buhohitr said:
Based on your screen shot, you put the "fastboot folder" on your desktop. Do this.
open cmd
type:
cd\ then hit enter
you should see:
c:\
now type:
cd users\david\desktop\fastboot then hit enter
you should see
c:\users\david\desktop\fastboot>
now type:
fastboot devices then hit enter
you should see device ID
now type:
fastboot reboot then hit enter
your device should reboot.
Click to expand...
Click to collapse
i am gonna assume it is not installed properly doesn't show devices and it says rebooting but doesn't.
deocare said:
i am gonna assume it is not installed properly doesn't show devices and it says rebooting but doesn't.
Click to expand...
Click to collapse
Do you have your table booted in fastboot mode and usb cable plug into your PC?
i doo
deocare said:
i doo
Click to expand...
Click to collapse
OK, you problably don't have android sdk instalaled. Here is the link to install SDK. When you run the sdk installation, only select anything with android packages and install, don't install everything.
http://forum.xda-developers.com/showthread.php?t=1616059
Another question is are you planing to install custom ROM??? or you just want root?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Setup, Preparation and Prerequisites
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
USB Debugging - On your nexus player go to Settings > About > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enter bootloader mode - Hold the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
Once you are in fastboot mode, the light below nexus player will be blinking constantly. You can verify by using "fastboot devices"
ADB Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal storage (pictures, music, etc.). Copy all important files off the nexus player onto a PC or upload them to a cloud.
Driver Installation
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Selecting show all devices
Clicking have disk
Finally selecting Desktop\android-sdk-windows\extras\google\usb_driver\android_winusb.inf as the driver
Alternative you can also download and install the Universal ADB Driver.
Downloads
Root:
Android 7.X:
- Coming Soon-
Android 6.X:
http://cord-cutters.wonderhowto.com/how-to/root-nexus-player-0160218/
http://androidflagship.com/16765-root-nexus-player-android-6-0-marshmallow
Android 5.X:
Download the SuperSU zip below. Extract the zip file and you will have (root.img) to platform-tools folder located on your desktop within the android-sdk-windows folder.
SuperSU (Forum Thread) or SuperSU (Direct link)
Information
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 2 main steps: Unlocking the Bootloader and Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the device in future.
Rooting: You can gain root booting up root.img
1. Unlocking Bootloader
Turn the nexus player off. Then go into bootloader mode by holding the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
Plug nexus player into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your nexus player serial number shows up you are good to go and may continue. If the nexus player is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the nexus player has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
OEM unlock twice
Code:
fastboot oem unlock
Code:
fastboot oem unlock
After you have done, please proceed onto the next section of the guide.
2. Installing a Custom Recovery
http://forum.xda-developers.com/nex...recovery-twrp-2-8-6-0-touch-recovery-t3114717
https://twrp.me/devices/asusnexusplayer.html
3. Rooting
Now that your nexus player has an unlocked bootloader, now this step is to gain root
Android 7.X
- coming soon -
Android 6.X
Require: TWRP, Custom boot.img and flashable supersu
(Refer to above link)
Android 5.0
Warning: This rooting guide is for Android 5.X only!
Boot (not flash) the root image which will give you root with the stock ROM
Confirm that you have downloaded the SuperSU zip from the downloads section above and you have extracted it and it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Make sure the nexus player is in bootloader mode
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot boot root.img
This will install SuperSU on your device, once the command has completed continue.
Open SuperSU and update the binaries.
Keep in mind that the first boot may take longer than usual.
Congrats! Your nexus player now has an unlocked bootloader, and is rooted.
==================================================
How to flash factory image for Nexus Player?
1) Download image file for your nexus player - https://developers.google.com/android/nexus/images
2) Boot your Nexus device into fastboot mode.
3) On your computer, use 7zip to extract the .tgz file you downloaded from the Android Developer website. Use 7zip a second time to extract the .tar file you extracted from the .tgz. When you’re done, you should have a folder with several files in it.
4) Copy all of these files and paste them in the platform-tools folder in the Android SDK on your computer. If you followed the above tutorial, this should be under the C drive, then under Program Files (x86) on Windows. Linux users, you know where you put it.
5) If you have not already done so, connect your Nexus device to your computer. ADB and Fastboot commands should already work at this point if you’ve been following along.
There are two flash-all files. If you’re in Windows, you’ll want to double click the one that has the gear logo and says “Windows Batch File” on the right. If you’re on Linux, you’ll want to double click the flash-all.sh.
At this point a box should pop up and you should see the installation taking place. While this is going on, do not unplug your device for any reason. Let it do its thing.
6) Once the installation process as finished, your device will automatically reboot and you can now safely disconnect your device from your computer.
==================================================
Credits:
- Chainfire (SuperSU and Rooting guide)
- Chromium (Easy to understand and detailed guide format)
- DevinWatson (USB driver guide)
- androidauthority (Flash firmware image guide)
Nice guide.
What about installing BusyBox?
I have a USB OTG cable but the adapter is female on the available USB side...I am not sure how to go about connecting my laptop/PC to the NP in order to perform ADB commands. Do I need a special cable or is there another way?
arecad said:
I have a USB OTG cable but the adapter is female on the available USB side...I am not sure how to go about connecting my laptop/PC to the NP in order to perform ADB commands. Do I need a special cable or is there another way?
Click to expand...
Click to collapse
Don't use the USB OTG cable, use a micro USB cable (same kind of cable that comes with android phones)
I cannot believe I missed that, how embarrassing. Thanks for the response, now I can follow this guide. I was thinking too hard about the OTG cable being a necessary piece of the puzzle.
I am able to get to the bootloader with no problems, I've got ADB and Fastboot installed on my PC, as well as the drivers. However ADB doesn't pick up my NexusPlayer even though fastboot does. Thoughts?
See Attachments
EDIT: Nevermind, I was expecting different responses from adb/fastboot. When in the bootloader adb will not confirm a connection, only fastboot. Sorry for being a noob...
xDragonZ said:
1. Unlocking Bootloader
[*] Turn the nexus player off. Then go into bootloader mode by holding the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
[*] Plug nexus player into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
[COLOR="red"]adb devices[/COLOR]
This command will list the connected devices. If your nexus player serial number shows up you are good to go and may continue. If the nexus player is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under adb devices.
Click to expand...
Click to collapse
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
midnightzak said:
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
Click to expand...
Click to collapse
AFAIK ADB is for Android, and Fastboot is for bootloader.
But i have the oposite problem. Mine NP is getting recognized useing ADB when normaly booted, but when i am in fastboot mode, fastboot isent working. I get no output when run 'fastboot devivces'. I have both tried to set the NP in fastboot mode by using the hiod button and plug in power, and with adb rebbot bootloader.
Any one have a clue why adb works, but not fastboot?
Double check to see if you have the latest version of fastboot. I have read that if you don't have the most up to date version the NP is not recognized.
Sleeepy2 said:
Double check to see if you have the latest version of fastboot. I have read that if you don't have the most up to date version the NP is not recognized.
Click to expand...
Click to collapse
+1 this.
goxboxlive said:
AFAIK ADB is for Android, and Fastboot is for bootloader.
But i have the oposite problem. Mine NP is getting recognized useing ADB when normaly booted, but when i am in fastboot mode, fastboot isent working. I get no output when run 'fastboot devivces'. I have both tried to set the NP in fastboot mode by using the hiod button and plug in power, and with adb rebbot bootloader.
Any one have a clue why adb works, but not fastboot?
Click to expand...
Click to collapse
Have you re-installed the Google driver when you are booted in the bootloader? The driver needs to install twice: once when booted into Android, and once when booted into the bootloader
ADB fastboot for Mac Quick Question??
Hey guys does anyone have any idea on how this can be done on a Mac....I know I know. When I initially plug in my Nexus player with the micro usb, nothing happens on my mac or the Nexus so i am guessing that the drivers are not installed. How would i go about getting these for the Mac? I have already downloaded the slim version of the ADB and Fastboot files with the platform tools into a folder on my desktop named Andriod, so i have these already. And i know that if you hold the button down on the nexus and plug the power in it brings up the bootloader screen. I just need help with the commands in terminal and where to access the drivers from. Also, on the Nexus the Developer options have already been enabled and USB debugging has been turned on. If anyone can help, It would be much appricated! Just started to use terminal commands so yes i am a noob in this department . Thanks agin in advance.
-Jason
MrBoostinduced said:
Hey guys does anyone have any idea on how this can be done on a Mac....I know I know. When I initially plug in my Nexus player with the micro usb, nothing happens on my mac or the Nexus so i am guessing that the drivers are not installed. How would i go about getting these for the Mac? I have already downloaded the slim version of the ADB and Fastboot files with the platform tools into a folder on my desktop named Andriod, so i have these already. And i know that if you hold the button down on the nexus and plug the power in it brings up the bootloader screen. I just need help with the commands in terminal and where to access the drivers from. Also, on the Nexus the Developer options have already been enabled and USB debugging has been turned on. If anyone can help, It would be much appricated! Just started to use terminal commands so yes i am a noob in this department . Thanks agin in advance.
-Jason
Click to expand...
Click to collapse
http://developer.android.com/sdk/win-usb.html
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start developing with your device, read Using Hardware Devices."
http://developer.android.com/tools/device.html
Sleeepy2 said:
http://developer.android.com/sdk/win-usb.html
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start developing with your device, read Using Hardware Devices."
http://developer.android.com/tools/device.html
Click to expand...
Click to collapse
Hey Sleepy2, I just did a brief read through and it states this:
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If that is the case, what would you suggest doing next? Thanks again for helping!
MrBoostinduced said:
Hey Sleepy2, I just did a brief read through and it states this:
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If that is the case, what would you suggest doing next? Thanks again for helping!
Click to expand...
Click to collapse
Open a terminal, navigate to the directory where you downloaded fastboot and go ahead with the commands shown in the first post. You will probably have to add a "./" in front of the commands given that you are on a mac, e.g.,
Code:
fastboot devices
becomes
Code:
./fastboot devices
I seem to be having the same problem as goxboxlive. I have tried installing the drivers about 100x tried on several computers and rebooted many a time. The only thing I can think of from the posts in here was to update fastboot but I dled the android studio and I would assume that has the latest version in there? Otherwise I couldn't find somewhere to download just fastboot from. Any help or recommendations or where I can dl the latest fastboot?
---------- Post added at 02:28 PM ---------- Previous post was at 01:57 PM ----------
Follow up. Got it to work. In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
knobbs said:
I seem to be having the same problem as goxboxlive. I have tried installing the drivers about 100x tried on several computers and rebooted many a time. The only thing I can think of from the posts in here was to update fastboot but I dled the android studio and I would assume that has the latest version in there? Otherwise I couldn't find somewhere to download just fastboot from. Any help or recommendations or where I can dl the latest fastboot?
---------- Post added at 02:28 PM ---------- Previous post was at 01:57 PM ----------
Follow up. Got it to work. In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
Click to expand...
Click to collapse
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
midnightzak said:
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
Click to expand...
Click to collapse
knobbs said:
In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
Click to expand...
Click to collapse
midnightzak said:
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
Click to expand...
Click to collapse
To avoid further confusion, I've updated the post since the OP hadn't yet.
midnightzak said:
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
Click to expand...
Click to collapse
efrant said:
To avoid further confusion, I've updated the post since the OP hadn't yet.
Click to expand...
Click to collapse
Thank you, saw your post that time and wanted to change it but keep forgetting.
Currently working on some basic developer app for Nexus Player.
xDragonZ said:
Thank you, saw your post that time and wanted to change it but keep forgetting.
Currently working on some basic developer app for Nexus Player.
Click to expand...
Click to collapse
It's all good, wasn't terrible let to figure out, and if you're developing even more for the Nexus Player, the more power to ya! Keep it up!
Rooting a Xiaomi Mi 4i on Linux Mint 17.1 Rebecca
- This guide might also be relevant for users of Debian and Ubuntu
Disclaimer: I accept no responsibility for any damage you do to your phone, body, life or anything else in the past present or future.
This has been written as I had so much difficulty in getting my Mi 4i rooted. I kept trying to do it in Windows through Virtual Box but kept failing.
1. Enable Developer Options
- On your phone, go to Settings
- About phone
- Keep tapping on the Android version until the message at the bottom says that you are a developer
2. Enable USB debugging
- On your phone, go to Settings
- Additional settings
- Developer options
- USB debugging
3. Install the tools
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
4. Try and see the devices
- Connect the phone to your computer
- Run the following command at the terminal
Code:
adb devices
- It will now say List of devices attached.
- If you see another line with an 8 character identifier such as bf1b6529 then you can skip step 5
5. Add phone to known devices
- Run the following command on the terminal
Code:
echo 0x2717 >> ~/.android/adb_usb.ini
6. Add your computer to trusted devices on your phone
- Enter the following command on the terminal:
Code:
adb devices
- Look on your phone, it should now be asking you if it can add the machine to the trusted devices, or something like that. I'm writing this from memory.
7. Check that adb devices is working
- Enter the following command on the terminal:
Code:
adb devices
- Check that the device ID is there (8 characters such as bf1b6529)
- Check that it says device after it
8. Kill adb
- Enter the following command on the terminal
Code:
adb kill-server
9. Now for the fun. You will need sudo access for this stage.
- Download boot.img to your computer.
- At the terminal, navigate to the directory where you downloaded boot.img, this will probably be ~/Downloads
- At the terminal:
Code:
adb reboot bootloader
- You will now see a screen like the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- At the terminal:
Code:
sudo su
fastboot devices
- You will now see your device ID followed by fastboot
Code:
fastboot boot boot.img
- You will now see something like the following:
Code:
downloading 'boot.img'...
OKAY [ 1.022s]
booting...
OKAY [ 0.259s]
finished. total time: 1.281s
10. Restart
- At the terminal enter:
Code:
fastboot reboot
- You should now see a textual boot screen wher you can see it actually carrying out the rooting with boot.img
- Then it should boot as normal into Android
- Check your apps. You should now have SuperSU
Thanks for step no 5. After trying all kind of 51-android.rules guide from stackoverflow and your solution work. Now I can detect my device in Linux Mint.
5. Add phone to known devices
- Run the following command on the terminal
Code:
echo 0x2717 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse
thanks....
finally i can connect my mi4i to my linux desktop
Thank you for your guide. I assume this will work on Ubuntu 14.04 as well.
Question to step no.9: "Download boot.img to your current dir" => Which directory do you mean? The root of the phone or on my laptop? Sorry for being newbie. Many thanks.
rmsinaga said:
Which directory do you mean? The root of the phone or on my laptop?
Click to expand...
Click to collapse
You need to download boot.img to your laptop. I've updated Step 9 with the following:
- Download boot.img to your computer.
- At the command line, navigate to the directory where you downloaded boot.img, this will probably be ~/Downloads
Click to expand...
Click to collapse
Step one on the path to rooting my m4i was getting adb to work.
kblade29m said:
Thanks for step no 5. After trying all kind of 51-android.rules guide from stackoverflow and your solution work. Now I can detect my device in Linux Mint.
Click to expand...
Click to collapse
After much googling, much time, and trial and error, I had reached this point. Then I come here and here it is! All made simple.
The next hurdle is that adb devices shows the phone with the word "offline," and that is where...
aembleton said:
- Look on your phone, it should now be asking you if it can add the machine to the trusted devices, or something like that. I'm writing this from memory.
Click to expand...
Click to collapse
...I find I wasn't even seeing the message because the flip cover was closed. Doh.
This is my second Android phone, and I rooted and installed CM on the previous one, a Defy+. Still feel very much a novice, and approaching the rooting is quite scary. Among my worries...
Does this method change the recovery?
Does this method, with boot.img, install a new rom, or does it root the exisiting one?
Will everything else be reset/wiped? (well, backups anyway. Of course).
Will Xiaomi updates still work and be installable?
I am considering using method 1 from "Root/Unroot V6.5.x W/out Losing Stock Recovery [Simplified]" (new member: cannot make that a link) . Any comments?
It is so nice to see the Linux, and especially mint-specific, advice here. Thank you!
(My first post here: usual forum-novice disclaimers apply )
I have used this method to root my mi4i.
Quick answer:
1. No
2. It only roots the existing ROM
3. No
4. You need to full unroot 1st from SuperSU before updating, otherwise it will be bootloop
5. Never tried before
rmsinaga said:
I have used this method to root my mi4i.
Quick answer:
... ... ...
Click to expand...
Click to collapse
Great answer! :good:
Thank you very much for attention to every detail. The only thing putting me off going for this straight away is that I am travelling in just over a week, which doesn't give me any margin for making mistakes (if they can be made, I will make them!).
You mentioned having failed to make stuff work in a virtual machine. Did you try Wine? I failed to make the Mi PC manager software run in Wine.
Simple, painless and absolutely effective
aembleton said:
10. Restart[/B]
- At the terminal enter:
Code:
fastboot reboot
Click to expand...
Click to collapse
(response typed from memory)
Code:
# fastboot reboot
<Waiting for Device>
...amd it goes on waiting. Does anybody get any other response on the terminal screen after this?
Anyway, Be Patient! Probably better to make tea or something away from the screen. After several minutes of Fastboot screen on the phone, the process continues as premised...
aembleton said:
- You should now see a textual boot screen wher you can see it actually carrying out the rooting with boot.img
- Then it should boot as normal into Android
- Check your apps. You should now have SuperSU
Click to expand...
Click to collapse
...and all is well.
After the phone had rebooted, I just ctrl-c-ed the fastboot process and exited from the terminal.
Works wonders, thanks!
Could only find ****ty .exe rooting tools that seemed sketchy and don't have windows installed anymore, so this saved me hours.
My computer could find the phone through adb and got authorized, the phone couldn't find my computer through adb though which was strange but it still worked fine. Thanks alot!
Thad E Ginathom said:
4. Will Xiaomi updates still work and be installable?)
Click to expand...
Click to collapse
rmsinaga said:
4. You need to full unroot 1st from SuperSU before updating, otherwise it will be bootloop
Click to expand...
Click to collapse
Just tried this, it does not work.
Disabled root from SuperSU and updated to the newest weekly developer rom, and my device is now in a boot loop.
I'm currently trying to download the stable fastboot rom from the MIUI forums, but their servers are both incredibly slow and unstable. Doesn't go past 100kb/s and the download loses connection after a while and fails to continue the download. If someone could provide a alternative download link that would be great.
EDIT: Found a hidden link on the rom page for the fastboot rom from the miui page. Go to this page and Ctrl-F Mi4i
zenolijo said:
Found a hidden link on the rom page for the fastboot rom from the miui page. Go to this page and Ctrl-F Mi4i
Click to expand...
Click to collapse
Did this work for you?
I also got into a boot loop after installing the latest update. I installed the latest stable version. This worked, but the Play Store won't start.
aembleton said:
Did this work for you?
I also got into a boot loop after installing the latest update. I installed the latest stable version. This worked, but the Play Store won't start.
Click to expand...
Click to collapse
Well, the stable fastboot rom isn't the global version, so i only used it to get my phone running again and then flashed the stable global version. Everything works as expected now.
How to update ROM using fastboot in Linux?
Do you know how to update ROM using fastboot in Linux?
Sorry to bother you as I'm new in this Linux world.
Thank you.
Thank you man, you have guided us to the land of light, you are our moses, krishna, muhammad and so on and so forth. We can flash left and right without second thoughts. Please keep up your efforts. Thank you one more time.
My phone is, as per previous posts, rooted, using this method.
Can I now flash TWRP recovery from Linux?
Hey, this is a method only for Xiaomi Mi4i? I have an Estar Crystal-clearview and wondering if I can root it by this method? I run the terminal with the adb install and then for the list of devices attached, and I started thinking about!
P.s. Just searched ''root with mint'' and your post was first!
Thad E Ginathom said:
Can I now flash TWRP recovery from Linux?
Click to expand...
Click to collapse
Eventually I got around to doing this using Flashify. I followed the instructions here on the MIUI forum. It was simple and straightforward and I now have TWRP recovery.
However, when I tried to use it to do a backup, it said there was not enough space. But it was long past bedtime, and that is another story that I have yet to investigate. There is probably a simple answer, err... make more space! The absence of SD card slot and the limited internal memory is the big frustration about this phone.
But I want to upgrade MIUI --- and I don't want to do it without an easy backtrack to the previous ROM.
[Solved] Step 9 not working
Goto developer options
Check if 'fastboot mode' is enabled
Thanks
Hi aembleton,
Thanks a lot. it worked just fine.
does this replace recovery too ?
Hey guys, I've long had this issue with my OnePlus One and I for the life of me cannot figure it out after searching and reading mad threads/forums.
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
So I'm following all the instructions possible step by step. I have my OPO in Recovery (TWRP 2.8.6.0) and it won't show up as an ADB Devices...
Yet, noting key parameters here:
- All my drivers are up to date
- My Android SDK is up to date
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Java SE is up to date
FastBoot - Phone is recognized (picture below).
ADB Sideload Mode in TWRP Recovery - ADB Sideload recognizes OPO, but doesn't work still.
But standard ADB is not listed when Recovery is on main page. But I get this prompt whenever the phone boots into recovery or I plug it in via USB when Recovery is active.
This is my command prompt to prove FastBoot recognizes my device, but ADB does not.
What am I doing wrong? Can someone help me? I've noticed this issue as long as I can remember, and have resorted to always having to copy my ROM files through the OS, doing a factory reset, then installing. I have never been able to use ADB Push.
Can someone provide me some pointers?
Thanks!!!
do you have debugging enabled on the phone, and if you do, have you authorized that computer on the phone? (I guess you have already, but just throwing out some ideas you might have forgotten)
CSquared4290 said:
Hey guys, I've long had this issue with my OnePlus One and I for the life of me cannot figure it out after searching and reading mad threads/forums.
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
So I'm following all the instructions possible step by step. I have my OPO in Recovery (TWRP 2.8.6.0) and it won't show up as an ADB Devices...
Yet, noting key parameters here:
- All my drivers are up to date
- My Android SDK is up to date
- Java SE is up to date
FastBoot - Phone is recognized (picture below).
ADB Sideload Mode in TWRP Recovery - ADB Sideload recognizes OPO, but doesn't work still.
But standard ADB is not listed when Recovery is on main page. But I get this prompt whenever the phone boots into recovery or I plug it in via USB when Recovery is active.
This is my command prompt to prove FastBoot recognizes my device, but ADB does not.
What am I doing wrong? Can someone help me? I've noticed this issue as long as I can remember, and have resorted to always having to copy my ROM files through the OS, doing a factory reset, then installing. I have never been able to use ADB Push.
Can someone provide me some pointers?
Thanks!!!
Click to expand...
Click to collapse
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Mr hOaX said:
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Click to expand...
Click to collapse
Thanks Mr. Hoax! I will give that a try and report back.
Interestingly in an attempt to use ADB Sideload to install the latest ROM update from scratch, I took a gamble and did a full format/wipe and was able to install the OS using ADB SideLoad. But afterwards, it still didn't come up under ADB Devices...But will try your recommendations and see what happens.
Elkhantar said:
do you have debugging enabled on the phone, and if you do, have you authorized that computer on the phone? (I guess you have already, but just throwing out some ideas you might have forgotten)
Click to expand...
Click to collapse
Yessir, Debugging was enabled through the OS (I don't know of any other way to enable debugging?)
Mr hOaX said:
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Click to expand...
Click to collapse
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Wug's tookit for bacon hv step by step procedure to install adb n fastboot drivers...gv it a try...i did it myself n it works nice
1+1
CSquared4290 said:
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Click to expand...
Click to collapse
After drivers installation is done, you need to reboot your OPO in bootloader(fastboot) mode and type
fastboot devices
And check out if the prompt shows your device serial number.
I see you're using the nexus driver. Perhaps try a Samsung ADB driver. It works with my phone without problems.
I get the same problem with my work PC, while everything works fine at home.
What CSquared4290 says, applies here:
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
- All my drivers are up to date
- My Android SDK is up to date
The phone is recognised normally under command > fastboot devices.
Symantec Endpoint Protection is running at my work PC. Could this be a reason?
CSquared4290 said:
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Click to expand...
Click to collapse
100% agree with the other posters, really delete all of your old USB ADB drivers, including the Google USB driver. Here's a tool I use for that: http://www.nirsoft.net/utils/usb_devices_view.html
Install Samsung ADB drivers, then when you plug your OPO in you should be able to see it in Device Manager as "Android Device" don't let Windows pick the driver. Right click and pick the browse my computer for drivers, then find the Samsung Android ADB Interface, install that. Unplug your phone, then plug it back in...profit? Good luck!
From my OnePlus X rooting guide. It looks like you need to install the universal adb driver linked in #2 and follow the steps in #3.
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
Click to expand...
Click to collapse
Hi,
did anyone try to upload google apps to the china phone Melrose 2019? I've tried a lot of way to upload it (flash new recovery twrp, adb and sideload, root). thanks for help
Melrose 2019, procesor MT6739WA, android 8.1
Tried both Google play store and services, latest nodpi versions from apkmirror. Both installed fine but services kept needing more permissions than exist and store kept crashing.
---------- Post added at 01:56 PM ---------- Previous post was at 01:54 PM ----------
How did you / where did you find root and twrp?
I have exactly the same problem on my Melrose 2019, any app I install will not go past Permissions....need help for this!
I too need help with this phone anyone got a solution ?
Succesfully installed open_gapps-arm-8.1-pico-20190511, via twrp
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
any link to the twrp file?
sorry I am a new member, I can't post the url link
---------- Post added at 06:20 PM ---------- Previous post was at 05:50 PM ----------
maybe this can help, i got it from here https: //4pda*ru/forum/index.php? showtopic = 935810
frast1 said:
sorry I am a new member, I can't post the url link
---------- Post added at 06:20 PM ---------- Previous post was at 05:50 PM ----------
maybe this can help, i got it from here https: //4pda*ru/forum/index.php? showtopic = 935810
Click to expand...
Click to collapse
can you please write a step-by-step procedure to install twrp? when I flash via fastboot twrp, all is ok, but when I reboot to recovery there is only android and write "no command"
I do not understand what causes you twrp not installed.
I just do it like this, before installing twrp via adb, I need TurnOn OEM unlock. Settings> Developer option> OEM unlock.
then install via adb:
1. Fastboot OEM unlock
2. Fastboot flash recovery
3. Fastboot reboot
This is the tool that I use
adb&recovery
frast1 said:
I do not understand what causes you twrp not installed.
I just do it like this, before installing twrp via adb, I need TurnOn OEM unlock. Settings> Developer option> OEM unlock.
then install via adb:
1. Fastboot OEM unlock
2. Fastboot flash recovery
3. Fastboot reboot
This is the tool that I use
https://drive.google.com/folderview?id=1VSDAGKG4-QD0rMEhkZXDRrvOb_Pn-cYp"]adb&recovery
Click to expand...
Click to collapse
1) command "adb devices" - OK, on command window is "0123456789ABCDEF device"
2) command "adb reboot bootloader" - OK, phone boot to FASTBOOT mode, on phone display is "=> FASTBOOT mode ..."
3) command "fastboot oem unlock", - OK, allow command on phone volume up, then phone return to FASTBOOT mode
4) command "fastboot flash recovery recovery.img", OK on phone display and command window is all OKAY
5) command "fastboot reboot" - phone reboot, all phone settings is on factory settings (china language,... ).
6) after allowing usb debuging - command "adb devices" on command window is "0123456789ABCDEF device"
7) command "adb reboot recovery", phone boot to recovery, but there is no twrp app, there is only green droid (the droid lies on its back, has an open front with a red triangle and a vicar), below the droid image is "no command"
thanks for help
edit: my device is not rooted, can it be a problem?
Step all the same as I did, twrp should have been installed. I don't understand the problem with your droid. Are you a droid with a fingerprint version or non?
The steps are the same as I did, twrp should have been installed. I don't understand the problem with your droid. is your droid with a fingerprint version or not?
I have got fingerprints.
I uploaded the files here
I do not take responsibility !!
http://bit.ly/melrose_2019
Password=
SHMM
frast1 said:
I do not understand what causes you twrp not installed.
I just do it like this, before installing twrp via adb, I need TurnOn OEM unlock. Settings> Developer option> OEM unlock.
then install via adb:
1. Fastboot OEM unlock
2. Fastboot flash recovery
3. Fastboot reboot
This is the tool that I use
adb&recovery
Click to expand...
Click to collapse
You were allowed to give credit to whoever brought it up first ...
(This is me)
Same issue, TWRP not working on Melrose 2019 3GB 32GB + Fingerprint
mamfet said:
1) command "adb devices" - OK, on command window is "0123456789ABCDEF device"
2) command "adb reboot bootloader" - OK, phone boot to FASTBOOT mode, on phone display is "=> FASTBOOT mode ..."
3) command "fastboot oem unlock", - OK, allow command on phone volume up, then phone return to FASTBOOT mode
4) command "fastboot flash recovery recovery.img", OK on phone display and command window is all OKAY
5) command "fastboot reboot" - phone reboot, all phone settings is on factory settings (china language,... ).
6) after allowing usb debuging - command "adb devices" on command window is "0123456789ABCDEF device"
7) command "adb reboot recovery", phone boot to recovery, but there is no twrp app, there is only green droid (the droid lies on its back, has an open front with a red triangle and a vicar), below the droid image is "no command"
thanks for help
edit: my device is not rooted, can it be a problem?
Click to expand...
Click to collapse
I have the same issue ( Melrose 2019 3GB 32GB + Fingerprint ), I tried multiple times but without luck.
Did you perhaps found a sollution?
Thanks
frast1 said:
I do not understand what causes you twrp not installed.
I just do it like this, before installing twrp via adb, I need TurnOn OEM unlock. Settings> Developer option> OEM unlock.
then install via adb:
1. Fastboot OEM unlock
2. Fastboot flash recovery
3. Fastboot reboot
This is the tool that I use
adb&recovery
Click to expand...
Click to collapse
mamfet said:
1) command "adb devices" - OK, on command window is "0123456789ABCDEF device"
2) command "adb reboot bootloader" - OK, phone boot to FASTBOOT mode, on phone display is "=> FASTBOOT mode ..."
3) command "fastboot oem unlock", - OK, allow command on phone volume up, then phone return to FASTBOOT mode
4) command "fastboot flash recovery recovery.img", OK on phone display and command window is all OKAY
5) command "fastboot reboot" - phone reboot, all phone settings is on factory settings (china language,... ).
6) after allowing usb debuging - command "adb devices" on command window is "0123456789ABCDEF device"
7) command "adb reboot recovery", phone boot to recovery, but there is no twrp app, there is only green droid (the droid lies on its back, has an open front with a red triangle and a vicar), below the droid image is "no command"
thanks for help
edit: my device is not rooted, can it be a problem?
Click to expand...
Click to collapse
MrFrankie said:
I have the same issue ( Melrose 2019 3GB 32GB + Fingerprint ), I tried multiple times but without luck.
Did you perhaps found a sollution?
Thanks
Click to expand...
Click to collapse
It does not work on this model.
If you can send the original boot.img file that is on the device and and I will customize you the recocvey.img
shmuel0990 said:
It does not work on this model.
If you can send the original boot.img file that is on the device and and I will customize you the recocvey.img
Click to expand...
Click to collapse
Sorry, I wish I was able to make one. I tried a lot of options like adb and even the OneClickRoot service. But all without luck.
MrFrankie said:
Sorry, I wish I was able to make one. I tried a lot of options like adb and even the OneClickRoot service. But all without luck.
Click to expand...
Click to collapse
https://drive.google.com/folderview?id=1I_vgKf3WQUZuKy5sKAJAH16pZ9-5kp9f
This Recovery.img file is suitable for the 32 GB version
but!!!! I could not and I do not recommend installing it ..
If you can read the 32GB firmware on your phone and upload it here, maybe I can build it for Root
---------- Post added at 02:00 AM ---------- Previous post was at 01:55 AM ----------
As explained in this video from minute 9:31
https://youtu.be/GMAytZ56hac
If you can please do this and upload the file you exported to (it will be a large file ...)
Guys,
can you please write step-by-step manual how to install the Google Play Store on this device? (I have 3 GB/32 BG, fingerprint). I am lama, so I dont know what is adb and how to use it.
Optionaly how to use the recovery image_new.img from post above
shantingshi said:
Guys,
can you please write step-by-step manual how to install the Google Play Store on this device? (I have 3 GB/32 BG, fingerprint). I am lama, so I dont know what is adb and how to use it.
Optionaly how to use the recovery image_new.img from post above
Click to expand...
Click to collapse
As explained in this video from minute 9:31
https://youtu.be/GMAytZ56hac
If you can please do this and upload the file you exported to (it will be a large file ...)
---------- Post added at 10:54 AM ---------- Previous post was at 10:51 AM ----------
shantingshi said:
Guys,
can you please write step-by-step manual how to install the Google Play Store on this device? (I have 3 GB/32 BG, fingerprint). I am lama, so I dont know what is adb and how to use it.
Optionaly how to use the recovery image_new.img from post above
Click to expand...
Click to collapse
The file from the message above is actually a standard recovery.img file that I just adapted to the 32 GB model
It does not work well !!!!!! Caution!
If you can do what I requested and upload the full file, I will create a flash file that can always be done from scratch