Database Info

problem with recovery

Hi guys,
I have a problem with install recovery on my Nexus S. When I'm in the command promt and I typed cmd. Then when I must type ""fastboot flash recovery ...img" it don't work anymore. I've downloaded the newest recovery from here: http://forum.xda-developers.com/showthread.php?t=988686
The file is in my download folder and called "5023-green.img". When I'm in the command promt and go into the download folder and then type "fastboot flash recovery 5023-green.img" it gives an error. It don't recocnize the file
I hope it is clear to understand because it's hard to explain My phone is unlocked and is in fastboot.

giganielsie said:
Hi guys,
I have a problem with install recovery on my Nexus S. When I'm in the command promt and I typed cmd. Then when I must type ""fastboot flash recovery ...img" it don't work anymore. I've downloaded the newest recovery from here: http://forum.xda-developers.com/showthread.php?t=988686
The file is in my download folder and called "5023-green.img". When I'm in the command promt and go into the download folder and then type "fastboot flash recovery 5023-green.img" it gives an error. It don't recocnize the file
I hope it is clear to understand because it's hard to explain My phone is unlocked and is in fastboot.
Click to expand...
Click to collapse
put both fastboot.exe and the recovery.img file in the same folder (for example c:/flash) then open cmd and navigate to that folder, you should see in the command line something like c:/fash/. Now you can do fastboot flash recovery recoveryname.img
Probably you don't have fastboot added to the path or you're not pointing to the correct folder where the recovery image is.

DeuXGod said:
put both fastboot.exe and the recovery.img file in the same folder (for example c:/flash) then open cmd and navigate to that folder, you should see in the command line something like c:/fash/. Now you can do fastboot flash recovery recoveryname.img
Probably you don't have fastboot added to the path or you're not pointing to the correct folder where the recovery image is.
Click to expand...
Click to collapse
Thanks for youre reply but still get the error. I've downloaded a tool package from here: http://www.mediafire.com/?wj0kbm0dooa5wsd
In this package is a fastboot.exe file. I put this file with the 5023-green.img in the same folder but still get error

giganielsie said:
Thanks for youre reply but still get the error. I've downloaded a tool package from here: http://www.mediafire.com/?wj0kbm0dooa5wsd
In this package is a fastboot.exe file. I put this file with the 5023-green.img in the same folder but still get error
Click to expand...
Click to collapse
I use the Android SDK, it has the updated fastboot tool. Anyway are you rooted already? If you're just get the Rom Manager from the market and install CWM from there. If not, try to get the android SDK from here:
http://developer.android.com/sdk/index.html
Install it (make sure that you also have java SE installed) to, let's say, C:/androidsdk
It will prompt you to open the Android SDK manager, say yes, select platform tools and hit download
Now in c:/androidsdk/platform-tools you will have fastboot.exe
Download the recovery from http://www.clockworkmod.com/rommanager to the platform-tools folder
Put your phone in fastboot (volume up+power on)
then open the cmd, navigate to c:/androidsdk/platform-tools and do fastboot devices, it should show you the SN from your nexus. If it doesn't show, then you need to update your ADB driver. You can get it from the Android SDK Manager in the extras.
Now do fastboot flash recovery recoveryname.img
Should work now

DeuXGod said:
I use the Android SDK, it has the updated fastboot tool. Anyway are you rooted already? If you're just get the Rom Manager from the market and install CWM from there. If not, try to get the android SDK from here:
http://developer.android.com/sdk/index.html
Install it (make sure that you also have java SE installed) to, let's say, C:/androidsdk
It will prompt you to open the Android SDK manager, say yes, select platform tools and hit download
Now in c:/androidsdk/platform-tools you will have fastboot.exe
Download the recovery from http://www.clockworkmod.com/rommanager to the platform-tools folder
Put your phone in fastboot (volume up+power on)
then open the cmd, navigate to c:/androidsdk/platform-tools and do fastboot devices, it should show you the SN from your nexus. If it doesn't show, then you need to update your ADB driver. You can get it from the Android SDK Manager in the extras.
Now do fastboot flash recovery recoveryname.img
Should work now
Click to expand...
Click to collapse
Thanks for youre explanation!
I think my ADB driver must have an update because when I type in the command promt c"/androidsdk/platform-tools>fastboot devices he says: "can not find the specified path".
In the Android SDK manager in extras is not shows any ADB driver? I have installed the Google USB Driver and the Google Web Driver in extras but which other file must I download?

giganielsie said:
Thanks for youre explanation!
I think my ADB driver must have an update because when I type in the command promt c"/androidsdk/platform-tools>fastboot devices he says: "can not find the specified path".
In the Android SDK manager in extras is not shows any ADB driver? I have installed the Google USB Driver and the Google Web Driver in extras but which other file must I download?
Click to expand...
Click to collapse
The google USB driver is the ADB driver. If you go into your Device manager in windows, with your Nexus in fastboot and connected to the PC, can you see a ADB device? Or do you see a yellow exclamation mark? You sure you're in the androidsdk folder in the command prompt?
Let's try a different thing. Copy adb.exe, fastboot.exe and AdbWinApi.dll to C:/windows/system32
Reboot just in case and try to do again fastboot devices from the cmd
Should work now

DeuXGod said:
The google USB driver is the ADB driver. If you go into your Device manager in windows, with your Nexus in fastboot and connected to the PC, can you see a ADB device? Or do you see a yellow exclamation mark? You sure you're in the androidsdk folder in the command prompt?
Let's try a different thing. Copy adb.exe, fastboot.exe and AdbWinApi.dll to C:/windows/system32
Reboot just in case and try to do again fastboot devices from the cmd
Should work now
Click to expand...
Click to collapse
Also don't work
This is the error:
{
"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"
}
In that folder are all of the files I needed so it should work though he don't work
And my phone also recognize as Android ADB Interface.
Edit: It's working!!! My brother fixed it! Thanks for the replies!!!:good::victory:

Now I have recovery but now I have another problem. When I reboot my phone, I can't go anymore to recovery. I see then a green android with a open stomach. Anybody a solution? It looks like there is something went wrong with the install of the recovery but what?
And I have root permission now but with rom manager I can install recovery but when I reboot into recovery, the green android with open stomach come back...

Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app

DeuXGod said:
Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Thanks!!! It looks like it works! Thanks for youre fast replies:good::good:

I didn't want to create another thread because I am somewhat having the same problem and I really don't know what to do. I have an M200 version on T-Mobile USA and I got the JB OTA yesterday and everything was running fine until, about 30 mins ago. The phone slowed down and the started to reboot and it keeps rebooting sometimes into safe mode. I took out the battery and tried the recovery mode, but this is what I get.

GripR said:
I didn't want to create another thread because I am somewhat having the same problem and I really don't know what to do. I have an M200 version on T-Mobile USA and I got the JB OTA yesterday and everything was running fine until, about 30 mins ago. The phone slowed down and the started to reboot and it keeps rebooting sometimes into safe mode. I took out the battery and tried the recovery mode, but this is what I get.
Click to expand...
Click to collapse
Do you have unlocked bootloader? If you have just flash CWM from the fastboot, enter in recovery and do a full wipe and install another ROM or even the stock image. Don't forget to remove the system/etc/install-recovery.sh file if you flash the stock ROM so CWM won't be overwritten every time you do a reboot.

DeuXGod said:
Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
from the dead droid reboot with power+ vol up
enter jb and with a file manager (like es file..or something else) delete both:
-/system/recovery-from-boot.p
-/system/etc/install-recovery.sh
reboot and reinstall cwm via fastboot

Only problem with that is he will require root access to do that.
Which I am assuming he currently doesn't have.
Anyways as someone already stated. Unlock bootloader if it isn't already. That will wipe your data off the phone.
Boot or flash a custom recovery.
Flash su.zip or supersu etc to get root
Boot up and make sure you actually have root.
Do as above poster said and remove those files.
Either flash recovery from a app like goo manager or rom manager. Hell now that that I think about it. I think rom manger has the option to remove those files for you when it flashes cwm. Or reboot into the bootloader and flash the recovery with fastboot. It will stick. Keep in mind that you need to download the fastboot version of the recovery if you go that route. It will be a .img. the others will be a .zip .
If you don't know how to use fastboot. Read the quides/stickies etc.

[Q] Help a noob out with rooting

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?

[TOOL] Android ADB and Fastboot MSI installer with PATH variable

Description
After always having to search for the latest versions of Android's ADB and Fastboot tools instead of downloading the whole Android SDK for just 1 mb in a few files, I decided to make my own MSI installer using the latest versions of ADB and Fastboot.
You can install it wherever you want and it will work from any path in the command prompt. The installer will append the installation folder location to the system PATH variable, allowing you to run ADB or Fastboot without you having to change the command prompt path to where they are installed.
This installer is 32-bit and 64-bit compatible.
Usage
The default installation path is C:\ADB so you can easily add your flashable files in there.
After installing Android ADB Fastboot you can open a command prompt and type adb or fastboot commands right away, you don't need to change paths. Keep in mind that you need admin privileges, though.
To open a command prompt with administrator rights on Windows 8, just right click on the bottom left corner of the screen or use the Win+X shortcut and then click on Command Prompt (Admin).
Click to expand...
Click to collapse
If you have Windows 7 or Vista, the quickest way to do it is to type CMD on the Start Menu search box and press Ctrl+Shift+Enter instead of just pressing Enter.
Click to expand...
Click to collapse
Requisites
You need to have ADB Debugging under Developer Options on your device. You also need the drivers for every device you want to use with ADB installed and working.
You can type adb devices on a command prompt. If your device is listed, the drivers are working and good to go for ADB and Fastboot use.
Click to expand...
Click to collapse
Download
I will always check the ADB version whenever a new Android SDK is released and I will update my installer when needed.
The download link and screenshots are on my website.
http://rubenalamina.mx/custom-installers/android-adb-fastboot/
Latest version of the installer: 1.5 (ADB 1.0.36) updated on 2016.09.21

Thanks mate, it really help people with lacks internet connection like mine
Sent from my WT19i using xda app-developers app

Installer updated to version 1.2 with the new ADB and Fastboot included in Android SDK 23.0.2.

Installer updated to version 1.3 based on the Android SDK 24.0.2.

no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.

Nightmare-Rex420 said:
no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.
Click to expand...
Click to collapse
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.

ajua said:
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.
Click to expand...
Click to collapse
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.

Nightmare-Rex420 said:
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.
Click to expand...
Click to collapse
Try using PowerShell. Also, see if you are able to run the ADB that comes with the SDK but run it from the folder where it is located.

[GUIDE] Nexus Player - How to Unlock Bootloader and Root using USB cable

{
"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!

[ROOT][GUIDE] How to install TWRP and root Wiko Jerry (Magisk)

Hi guys,
On this post I will share with you a method to root Wiko Jerry.
You will get a TWRP recovery installed too.
Sorry if my english is a bit bad
Sorry if the print screens if you find are in Portuguese, as it would be boring to change my Windows language.
DISCLAIMER:
I AM NOT responsible for bricked devices and lost warranties.
If you don't feel safe modifying your device DO NOT do anything.
Backup the data you have on your phone. Accidents can happen.
That said, let's go to the fun!
What you need:
Your Wiko Jerry
This TWRP 3.1.1 recovery: https://mega.nz/#!rZM2XIhY!tuneB9pGNQzhbGWz1kRY-mzeCGtRjUAP2QqX791r4Go
ADB / Fastboot on your computer. I will explain how to set it up on your PC later.
Magisk flashable ZIP. Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Connect your phone to your PC with your USB cable.
1- Preparing your PC:
If you already have ADB on your PC, you can skip this part.
After downloaded the files you need, let's get your computer ready.
You will need fastboot and ADB for this method, so download from here:
Installing ADB on Windows:
Open this link and click on SDK Platform-tools for Windows.
After downloaded, extract the ZIP anywhere you want.
You should now have a folder like this:
{
"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"
}
Keep the folder open (or just minimize it) and go ahead to the next step.
Installing ADB on Linux:
Run one of this commands on your terminal.
-Ubuntu/Debian based Linuxes (APT):
Code:
sudo apt install android-tools-adb android-tools-fastboot
-Fedora (YUM):
Code:
sudo yum install android-tools
Test with:
Code:
sudo adb version
You should get something like this:
Code:
Android Debug Bridge version 1.0.40
Version 4986621
2- Getting your phone ready:
To get your phone ready you need to enable ADB on Settings.
Open Settings>About phone and tap "Buid number" 7 times.
Go back one time and you sholud get a "Developer options" menu on Settings.
Open the "Developer options" and enable "USB debugging" option.
Now you have ADB enabled on your device.
3- Installing TWRP on your phone
Do you remember the TWRP file you downloaded before? Now you will need it.
-Copy the TWRP_3.1_JERRY.img file to your platform-tools folder.
-Rename the file to recovery.img.
-Open a command prompt.
-On command prompt do this to open your platform-tools folder on it:
Code:
cd INSERT PATH TO YOUR platform-tools FOLDER
Now, unlock your phone and run this command:
Code:
adb devices
It should appear something like this on your PC:
Code:
List of devices attached
<your-device-id> offline
And this on your phone:
On that window, check the box and tap OK. This will allow your phone to communicate with ADB running on your PC.
Check if everything is ok doing the "adb devices" command again. If it is ok, this will show up:
Code:
List of devices attached
<your-device-id> device
Now, on your command line run the command:
Code:
adb reboot-bootloader
Your phone will reboot in fastboot mode. It should look like this:
Run this on your command line:
Code:
fastboot flash recovery recovery.img
If you get <waiting-for-device> on command prompt, check this:
-Open Device Manager (Win key+X, click on Device Manager)
-Find a device called "fastboot Gadget" or similar name with a exclamation mark.
-Right click it and click on "Update drivers..."
-Click on second option on the setup (search manually)
-Click on the second option again.
-On the list, look for Universal Serial Bus Devices and double click it
-Inside the Manufacturer list select WinUsb Device
-On the right list select ADB Device and double click it
-Click on yes
-After installed, close and its fixed!
​When the command finishes, you should get this:
Code:
Sending 'recovery' (12866 KB) OKAY [ 0.550s]
Writing 'recovery' OKAY [ 0.762s]
Finished. Total time: 1.317s
Congratulations! Now you have TWRP on your phone!
4- Booting into TWRP and root the phone with Magisk
Now you need to turn off your phone. You can just take the battery out and put it again.
This phone has a weird way to boot into the recovery. You need to press the power button and a second later, the VOL+ button.
The Wiko logo will appear and the phone MUST NOT VIBRATE. If it vibrates, the normal Android will start.
Do this procedure anytime you want to go into TWRP.
Connect your USB cable.
Tap "Keep Read Only"
In your PC, go to This PC and open the JERRY device.
Copy the previously downloaded Magisk ZIP file into the Internal Storage.
In TWRP, tap Install
Search for the Magisk ZIP in the file explorer.
Swipe to confirm the flash
Tap Home button
Tap Reboot
Tap System
Android should boot normally
Warning: It could take a few seconds to Magisk Manager to appear on apps list.
Congratulations! You have done it! You have TWRP and Magisk!

help
i always get error remote replacing recovery not allowed something like that
what should i do
edit : its this error
remote: 'download for partition 'recovery' is not allowed

GnarlyBuzzard50 said:
i always get error remote replacing recovery not allowed something like that
what should i do
edit : its this error
remote: 'download for partition 'recovery' is not allowed
Click to expand...
Click to collapse
hey you'll need to unlock your bootloader first
FIRST BACKUP EVERYTHING USEFUL FROM YOUR PHONE, THI WILL FACTORY RESET YOUR DEVICE
after getting adb working (debug on and all that stuff)
enter in your cmd prompt
Code:
adb reboot bootloader
then wait till your phone is in fastboot mode
now you'll type in cmd
Code:
fastboot flashing unlock
read carefully what appears in your phone screen and accapt it (at your own risk, it will probably void your warranty)
now type in cmd
Code:
fastboot reboot
done

TWRP file is not working

Code:
fastboot flashing unlock
Click to expand...
Click to collapse
I get "Unlock Failed"

When I try to enter recovery mode, it says: no command

is this recovery image meant for the SPD or the MTK variant?
Tried this on an SPD Jerry & it didn't work
Any other help?

KitK4t said:
Hi guys,
On this post I will share with you a method to root Wiko Jerry.
You will get a TWRP recovery installed too.
Sorry if my english is a bit bad
Sorry if the print screens if you find are in Portuguese, as it would be boring to change my Windows language.
DISCLAIMER:
I AM NOT responsible for bricked devices and lost warranties.
If you don't feel safe modifying your device DO NOT do anything.
Backup the data you have on your phone. Accidents can happen.
That said, let's go to the fun!
What you need:
Your Wiko Jerry
This TWRP 3.1.1 recovery: https://mega.nz/#!rZM2XIhY!tuneB9pGNQzhbGWz1kRY-mzeCGtRjUAP2QqX791r4Go
ADB / Fastboot on your computer. I will explain how to set it up on your PC later.
Magisk flashable ZIP. Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Connect your phone to your PC with your USB cable.
1- Preparing your PC:
If you already have ADB on your PC, you can skip this part.
After downloaded the files you need, let's get your computer ready.
You will need fastboot and ADB for this method, so download from here:
Installing ADB on Windows:​
Open this link and click on SDK Platform-tools for Windows.​After downloaded, extract the ZIP anywhere you want.​You should now have a folder like this:​
Keep the folder open (or just minimize it) and go ahead to the next step.​​
​​Installing ADB on Linux:​
Run one of this commands on your terminal.​-Ubuntu/Debian based Linuxes (APT):​
Code:
sudo apt install android-tools-adb android-tools-fastboot
-Fedora (YUM):​
Code:
sudo yum install android-tools
Test with:​
Code:
sudo adb version
You should get something like this:​
Code:
Android Debug Bridge version 1.0.40[/INDENT]
[INDENT]Version 4986621
​
​
2- Getting your phone ready:
To get your phone ready you need to enable ADB on Settings.
Open Settings>About phone and tap "Buid number" 7 times.
Go back one time and you sholud get a "Developer options" menu on Settings.
Open the "Developer options" and enable "USB debugging" option.
Now you have ADB enabled on your device.
3- Installing TWRP on your phone
Do you remember the TWRP file you downloaded before? Now you will need it.
-Copy the TWRP_3.1_JERRY.img file to your platform-tools folder.
-Rename the file to recovery.img.
-Open a command prompt.
-On command prompt do this to open your platform-tools folder on it:
Code:
cd INSERT PATH TO YOUR platform-tools FOLDER
Now, unlock your phone and run this command:
Code:
adb devices
It should appear something like this on your PC:
Code:
List of devices attached
<your-device-id> offline
And this on your phone:
On that window, check the box and tap OK. This will allow your phone to communicate with ADB running on your PC.
Check if everything is ok doing the "adb devices" command again. If it is ok, this will show up:
Code:
List of devices attached
<your-device-id> device
Now, on your command line run the command:
Code:
adb reboot-bootloader
Your phone will reboot in fastboot mode. It should look like this:
Run this on your command line:
Code:
fastboot flash recovery recovery.img
​If you get <waiting-for-device> on command prompt, check this:​
-Open Device Manager (Win key+X, click on Device Manager)​-Find a device called "fastboot Gadget" or similar name with a exclamation mark.​-Right click it and click on "Update drivers..."​-Click on second option on the setup (search manually)​-Click on the second option again.​-On the list, look for Universal Serial Bus Devices and double click it​-Inside the Manufacturer list select WinUsb Device​-On the right list select ADB Device and double click it​-Click on yes​-After installed, close and its fixed!​​
​​When the command finishes, you should get this:
Code:
Sending 'recovery' (12866 KB) OKAY [ 0.550s]
Writing 'recovery' OKAY [ 0.762s]
Finished. Total time: 1.317s
Congratulations! Now you have TWRP on your phone!
4- Booting into TWRP and root the phone with Magisk
Now you need to turn off your phone. You can just take the battery out and put it again.
This phone has a weird way to boot into the recovery. You need to press the power button and a second later, the VOL+ button.
The Wiko logo will appear and the phone MUST NOT VIBRATE. If it vibrates, the normal Android will start.
Do this procedure anytime you want to go into TWRP.
Connect your USB cable.
Tap "Keep Read Only"
In your PC, go to This PC and open the JERRY device.
Copy the previously downloaded Magisk ZIP file into the Internal Storage.
In TWRP, tap Install
Search for the Magisk ZIP in the file explorer.
Swipe to confirm the flash
Tap Home button
Tap Reboot
Tap System
Android should boot normally
Warning: It could take a few seconds to Magisk Manager to appear on apps list.
Congratulations! You have done it! You have TWRP and Magisk!
Click to expand...
Click to collapse

<thanks man, worked fine for me.
just like he says...
adb reboot-bootloader
fastboot flash recovery <pathoftherenamedTWRP.img>
Take the battery out, back in
press and hold start button, sec later vol down button too
Now TWRP should start
read only
transfer the magisk.zip file to internal storage(PC)
install button(TWRP, Smartphone)
tap on the magisk.zip file and swipe to accept
wait till its done
press on reboot
done

Zaki4t said:
is this recovery image meant for the SPD or the MTK variant?
Tried this on an SPD Jerry & it didn't work
Any other help?
Click to expand...
Click to collapse
Worked for me. Where can i see which i have. maybe i can help

z0mb13m4ch1n3 said:
Worked for me. Where can i see which i have. maybe i can help
Click to expand...
Click to collapse
and if you messed up(like I do in my first try) here...
Wiko Mobile: Kundenbereich / Verbindung.
customer-de.wikomobile.com
take out the battery, theres the imei number
youll download a .exe file. stressed me in linux and lend a win 7 laptop. 5min or so and i had a factory fresh jerry to try again

The problem is there is no WinUsb there i dont have it.

Hi, I have a big trouble i followed all the instructions and everything was just fine, until the step 4- Booting into TWRP and root the phone with Magisk, after a take out and put the battery again in the cell, it doesn't boot from logo, just reset an reset, I already try o hard reset, try to enter TWRP, I try all kind of button combination, nothing works can someone helpme. Thks...