Database Users

[Video Guide] Newbie root OnePlus X root | Temporary TWRP | Permanent TWRP | Fastboot

Thanks to @eng.stk for his excellent work with the TWRP
Download auto fastboot adb driver installer, SuperSU.zip, TWRP, adb command set package: http://www.mediafire.com/?r58t64b8auweicy
Normal speed OnePlus X root video guide
Fast speed

All done as shown on the video, thanks... Now my oneplus x have root access, twrp recovery. But once the is removed from computer, if i try to enter in twrp recovery mode was never possible(by combination of power +volume keys press). It is only possible by adb command prompt via computer. Can anyone please help me with this issue.?

Hello Harsha, do you mean
A) when you go to recovery from boot it's stock recovery...
Or
B) you can't enter recovery at all from boot...
If A, try "fastboot flash recovery [name of recovery]. img"
If B, from power off, hold VolDown+Power. Try to release power button right after the vibrate, but continue to hold VolDown.

Small question.
My phone doesn't want to provide me the RSA key when switching to developer mode.Any other suggestions than the ones you provide in the video?(i have tried on two different windows devices running windows 10 and windows 8.1)

galbe90 said:
Small question.
My phone doesn't want to provide me the RSA key when switching to developer mode.Any other suggestions than the ones you provide in the video?(i have tried on two different windows devices running windows 10 and windows 8.1)
Click to expand...
Click to collapse
I assume you tried switching back and forth between MTP and charge only.
Here are several if you haven't tried already:
Revoke all authorizations in dev options, disable USB debugging, then enable USB debugging again
kill and restart the server (adb kill-server and adb start-server)
a different USB cable
a different USB port in the PC
USBdeview to remove all adb and phone drivers, then reinstall drivers again: https://www.mediafire.com/folder/89110vv87cl1j/www.chinaphonearena.com_Tutorial_downloads

6p with OS X 10.11 - Recovery adb devices not detected

I am hoping someone can give me some pointers on what to look at... I have two Macs where I have encountered this problem. When in recovery, I type
Code:
adb devices
into the terminal and I get no devices found. When my Nexus 6p is booted into full OS mode I can see the device serial number reported, and I can even issue
Code:
adb reboot recovery
commands.
Any ideas what needs to happen to get the device to work properly in recovery mode with adb? I've gone through several of the tutorials and haven't found any smoking guns. I do NOT have adb in my path, but I do change to that folder and run ./adb to execute.
Some background
Both Macs run OS X 10.11, El Capitan
The Nexus 6p is on 6.0.1, MMB29Q, stock recovery and ROM, not rooted
ADB/Fastboot were installed via the Google Android SDK

Idk how different it is, but I use OSX 10.10.5. I type: ./adb or ./fastboot before commands. With the phone in the bootloader, do you have an issue when you run:
./fastboot devices
Sent from my Nexus 5X using Tapatalk

I used both on my Macbook Pro last night on 10.11.
When you plug the phone in, is it being recognized by the OS? (Or, if you have Android File Transfer installed, does it pop open immediately?)

Follow this tutorial, it will fix your ills.
http://forum.xda-developers.com/showthread.php?t=1917237

gewecht said:
I am hoping someone can give me some pointers on what to look at... I have two Macs where I have encountered this problem. When in recovery, I type
Code:
adb devices
into the terminal and I get no devices found. When my Nexus 6p is booted into full OS mode I can see the device serial number reported, and I can even issue
Code:
adb reboot recovery
commands.
Any ideas what needs to happen to get the device to work properly in recovery mode with adb? I've gone through several of the tutorials and haven't found any smoking guns. I do NOT have adb in my path, but I do change to that folder and run ./adb to execute.
Some background
Both Macs run OS X 10.11, El Capitan
The Nexus 6p is on 6.0.1, MMB29Q, stock recovery and ROM, not rooted
ADB/Fastboot were installed via the Google Android SDK
Click to expand...
Click to collapse
See here.
And here for issues with El Cap.

Thanks for the pointer... However, the problem persists.
I ran the installer after disabling System Integrity Protection (done in Recovery) and rebooted into OS X
I was able to detect the Nexus when the Android OS was running, but not in recovery (same behavior).
I rebooted to recovery and re-enabled System Integrity Protection. Rebooted again. No change in behavior.
So I'm really not what else I could or should be looking at.
BTW, it looks like the only benefit of disabling SIP is allowing the installation of the files into /usr/local/bin. Once it is installed I'm thinking you can re-enable SIP.
Any other thoughts?
uicnren said:
See here.
And here for issues with El Cap.
Click to expand...
Click to collapse

gewecht said:
Thanks for the pointer... However, the problem persists.
I ran the installer after disabling System Integrity Protection (done in Recovery) and rebooted into OS X
I was able to detect the Nexus when the Android OS was running, but not in recovery (same behavior).
I rebooted to recovery and re-enabled System Integrity Protection. Rebooted again. No change in behavior.
So I'm really not what else I could or should be looking at.
BTW, it looks like the only benefit of disabling SIP is allowing the installation of the files into /usr/local/bin. Once it is installed I'm thinking you can re-enable SIP.
Any other thoughts?
Click to expand...
Click to collapse
I did some further digging... When the Nexus is booted into Android I can see the device (identified as "Nexus 6p") in the USB chain in OS X's "System Information" tool. In the bootloader screen, OS X shows "Android" and fastboot does detect the device.
However, when I've rebooted into recovery I cannot see anything connected - not a device in recovery, not a Nexus 6p. Nothing!

gewecht said:
I did some further digging... When the Nexus is booted into Android I can see the device (identified as "Nexus 6p") in the USB chain in OS X's "System Information" tool. In the bootloader screen, OS X shows "Android" and fastboot does detect the device.
However, when I've rebooted into recovery I cannot see anything connected - not a device in recovery, not a Nexus 6p. Nothing!
Click to expand...
Click to collapse
Mind if I ask, what are you trying to do in recovery?

have you tried unplugging and replugging the usb type c while you were on adb/recovery screen? i had the same problem but unplug and replug worked for me.

bluwavemarshall said:
have you tried unplugging and replugging the usb type c while you were on adb/recovery screen? i had the same problem but unplug and replug worked for me.
Click to expand...
Click to collapse
I finally figured out what was going on.
When in Recovery mode, I could never see the Nexus 6p attached to the OS X machine. However, on a hunch, I enabled the sideload ZIP with ADB option (this is stock recovery), and suddenly I was able to see the 6p in OS X System Information, and detect it via "adb devices".
Not sure if this is expected behavior or not, but it seems that there is a portion of the USB interface in stock recovery that only loads on this device once you have enabled the sideload feature in recovery.
Thanks to everyone for the suggestions.

gewecht said:
I finally figured out what was going on.
When in Recovery mode, I could never see the Nexus 6p attached to the OS X machine. However, on a hunch, I enabled the sideload ZIP with ADB option (this is stock recovery), and suddenly I was able to see the 6p in OS X System Information, and detect it via "adb devices".
Not sure if this is expected behavior or not, but it seems that there is a portion of the USB interface in stock recovery that only loads on this device once you have enabled the sideload feature in recovery.
Thanks to everyone for the suggestions.
Click to expand...
Click to collapse
ADB works in OS mode, while USB debugging is enabled. Where stock recovery is concerned, only sideload mode will be available, since it doesn't require ADB access for anything else.
EDIT: And yes. It is expected behaviour of the stock recovery.

Glad you figured it out! Cool

I had the same problem, how did you "enable the sideload ZIP with ADB option "?

I'm having the same issue on my Pixel. How did you "enabled the sideload ZIP with ADB option (this is stock recovery)"??
---------- Post added at 11:54 PM ---------- Previous post was at 11:50 PM ----------
How do I "enabled the sideload ZIP with ADB option"?
gewecht said:
I finally figured out what was going on.
When in Recovery mode, I could never see the Nexus 6p attached to the OS X machine. However, on a hunch, I enabled the sideload ZIP with ADB option (this is stock recovery), and suddenly I was able to see the 6p in OS X System Information, and detect it via "adb devices".
Not sure if this is expected behavior or not, but it seems that there is a portion of the USB interface in stock recovery that only loads on this device once you have enabled the sideload feature in recovery.
Thanks to everyone for the suggestions.
Click to expand...
Click to collapse

Phone stuck without os and can't access to fastboot or adb

guys I'm in a bad situation, phone is without OS and I can only access to recovery or bootloader, I have a twrp installed and I can't access to an USB otg (simple usb doesn't even blink like they are not working, If I connect an hdd it doesn't recognize it but gives it power) and I can't access to the phone as MTP or with adb devices or adb sideload. Even on bootloader mode device isn't showed when I try the command "fastboot devices" and it says "download mode = DISABLED".
so I only have access to twrp with those limitations, I need a big help, phone is with BTL unlocked and with expired warranty.
thanks in advance

parodiniccolo said:
guys I'm in a bad situation, phone is without OS and I can only access to recovery or bootloader, I have a twrp installed and I can't access to an USB otg (simple usb doesn't even blink like they are not working, If I connect an hdd it doesn't recognize it but gives it power) and I can't access to the phone as MTP or with adb devices or adb sideload. Even on bootloader mode device isn't showed when I try the command "fastboot devices" and it says "download mode = DISABLED".so I only have access to twrp with those limitations, I need a big help, phone is with BTL unlocked and with expired warranty.
thanks in advance
Click to expand...
Click to collapse
Download mode=disabled is the default (normal) displayed in bootloader mode. You seem to infer that is what fastboot returned when you typed devices? MTP works in TWRP automatically when it loads. Sounds like you may have a PC driver/cable issue. When you plug the device into your PC, how is it recognized?

v12xke said:
Download mode=disabled is the default (normal) displayed in bootloader mode. You seem to infer that is what fastboot returned when you typed devices? MTP works in TWRP automatically when it loads. Sounds like you may have a PC driver/cable issue. When you plug the device into your PC, how is it recognized?
Click to expand...
Click to collapse
I'm on mac so I don't have any driver issues and other phones works fine with mtp in TWRP

Up please

parodiniccolo said:
I'm on mac so I don't have any driver issues and other phones works fine with mtp in TWRP
Click to expand...
Click to collapse
You are using OSX, right? Fastboot commands should start with ./ before each command. For example: ./fastboot devices, or ./fastboot flash, or ./fastboot reboot bootloader. Same applies for adb commands. If you are already familiar with flashing images, read my post below about OSX and fastboot.
Do not click into the thread because it is for the Nexus 5X new users guide.
Edit: Whoops! Initially shared the wrong link above. Follow this link instead:
https://forum.xda-developers.com/showpost.php?p=68758793&postcount=3
Sent from my Nexus 5X using Tapatalk

"Waiting for any devices" with Moto G4

Excuse me for my bad English. I am new on this Forum. Please help me, I have a big problem!
I can’t use Fastboot command, because ewery time I got the „Waiting for devices” error message 
1) I have a Motorola Moto G4 phone (XT 1622, athene)
2) This mobile are not rooted.
3) I want to unlock my bootloader, after this I want to install TWRP, and after this I van root my mobile, for install the custom Lineage OS.
4) On my phone I activated at the Developper Otions the USB debugging, and OEM Unlocking.
5) I connected my phone to my PC, I used first time Windows 10. On this system my Moto G4 are identified: Motorola ADB interface. No problem with identification, no any yelow exclamation matrk, no unidentified device!
6) I have installed the correct ADB and Fastboot driver v.1.4.3 (link is made from this site)
7) I have installed the Motorola driver from the official Motorola site.
8) All ADB command work fine, for example adb devices, adb reboot bootloader, etc.
9) But no fastboot command work, when I tested the fastboot devices, I got the „Waiting for devices”. Of corse befor this, I rebooted my phone in fastboot mode! If I use any fastboot command, I got this error message.
10) I try to use the excellent tools (thank you for this): Universal Fastboot & ADB tool, latest version, but the situation in this case is the same, „Waiting for devices”.
11) Of corse I rebooted the PC after instalation of the drivers, the fastboot.exe is in the right paths, etc.
12) I have installed the Universal USB Driver with the Universal Fastboot & ADB tool, Install drivers button, PC rebooted after this.
13) I used Windows 10, Windows XP, and Ubuntu, and in all cases I got the „Waiting for devices”
14) Under Ubuntu I got this message, despite that on Ubuntu the ADB and Fastboot driver installations are cleare.
15) I tested all on many other PC.
16) Every time I connected my phone to the PC only on USB 2.0 port, I changed the USB port, and I changed the USB cable too.
17) I read hundred ot tutorilas on youtube, on differant Forums, but none of them helped.
18) I uninstalled or reinstalled a many timet he ADB and fastboot drivers (I tested a lot of drives from the net), and I installet a many times the official Motorola driver, and the Google universal USB driver, but nothing
Please tell me what can I do for solve this devil situation, Please help me! Thank you again!

TA-1000 Pie not detected while in recovery/sideload

as the title says my ta-1000 isn't detected by the adb/fastboot while in recovery mode > apply update from adb
this is not a driver problem as i've tried on both windows and fwul linux.
also, on windows there's no device at all, not unknown or known
i have usb debugging enabled and adb works on both windows and linux while the phone is turned on normally
as soon as i do adb reboot recovery the phone disconnects and never appears
also, the phone is detected while in download mode
i need to sideload an update to revert the recovery back to nougat so i can downgrade
sideloading used to work just fine in nougat/oreo but not in pie
no, i can't install from sd card since i gave mine away to my nephew, figured i don't need it considering the phone has 32gb of space and i don't even use it
anyone solution to this?