Hello all, been scouring the web with no avail, so I must come here for your help.
I used some of the guides on this forum in order to root, install CWR, and Cyanogenmod a few months back, but I'm back again today after an OTA update got me stuck in CWR/bootloader.
I can use both of these, and both of these only. I cannot boot into the ROM.
When looking, I've realized the only way to fix this would be to do a full reset and install the ROM again. I've wiped the device with CWR, but I'm not able to flash another ROM onto the device. (I'm looking to flash the GPE ROM this time).
My computer is detecting that something is connected, but even with the ADB drivers and everything, ADB still isn't detecting the device. Any pointers?
Also when looking around, I also noticed that many guides tell me I need to turn S-ON off, and I've tried doing that with rumrunner, but that didn't work since ADB wasn't either.
TLDR; I'm stuck in bootloader/recovery, am not able to flash/sideload due to my PC not detecting the device.
Anyway, THANKS LOADS IN ADVANCE. I've spent all afternoon searching today, and this is my last resort.
-GoldenTatertot
TWRP 2.6.3.3+ and adb sideload will be your friend. Try that and post back results
sent from my mobile device
SaHiLzZ said:
TWRP 2.6.3.3+ and adb sideload will be your friend. Try that and post back results
sent from my mobile device
Click to expand...
Click to collapse
I'm not able to sideload though. My PC isn't detecting the device.
GoldenTatertot said:
I'm not able to sideload though. My PC isn't detecting the device.
Click to expand...
Click to collapse
You need to install HTC sync to ensure the proper drivers are installed.
Download HTC sync manager
Install it,
Remove HTC sync manager but leave drivers
place HTC one on boot loader then fastboot option, connect device to computer wait until android 1.0 installs
Disconnect device and boot to recovery, reconnect device and let drivers install.
Run from computer CMD and get to the place where adb and fastboot exes are located.
Type command adb devices
the if successful prompt to do a adb sideload
Sent from my HTC One using xda app-developers app
TopoX84 said:
Download HTC sync manager
Install it,
Remove HTC sync manager but leave drivers
place HTC one on boot loader then fastboot option, connect device to computer wait until android 1.0 installs
Disconnect device and boot to recovery, reconnect device and let drivers install.
Run from computer CMD and get to the place where adb and fastboot exes are located.
Type command adb devices
the if successful prompt to do a adb sideload
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Alright, I installed and uninstalled HTC sync manager, only uninstalled from PC's native uninstallation process, and not sure if the drivers got uninstalled- didn't ask me about it.
After that, I recall a popup telling me it's installing Android 1.0, which only was active for a moment. I disconnected and booted to recovery, reconnected to computer, and 'adb devices' returned no devices.
Thanks again. Today was the first day at school without my phone this year, and it was dreadful. I'm a total addict.
Do you have a linux distro available which you can try? Preferably Ubuntu. Everytime Windows screwed up, I was able to do adb/fastboot perfectly with Linux.
Install:
sudo apt-get install android-tools-adb android-tools-fastboot
Define rules:
sudo gedit /etc/udev/rules.d/51.android.rules
Write this in that file: SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="Ubuntu"
Save and exit, then do sudo adb / fastboot devices.
svemprala said:
Do you have a linux distro available which you can try? Preferably Ubuntu. Everytime Windows screwed up, I was able to do adb/fastboot perfectly with Linux.
Install:
sudo apt-get install android-tools-adb android-tools-fastboot
Define rules:
sudo gedit /etc/udev/rules.d/51.android.rules
Write this in that file: SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="Ubuntu"
Save and exit, then do sudo adb / fastboot devices.
Click to expand...
Click to collapse
Do you think you could write or link me to a more detailed guide about that? Don't have much knowledge about that kind of stuff. Especially since I don't know what I need to look for.
Ahh, was finally able to get ADB to work on my computer. All good now.
GoldenTatertot said:
Ahh, was finally able to get ADB to work on my computer. All good now.
Click to expand...
Click to collapse
Do you mind telling us the steps? For other people looking for a solution?
Sent from my HTC One using xda app-developers app
Related
I let my cousin borrow my prime while I went out of town for a few days and when I came back my tablet was completely wiped. All that it has on it is fastboot and fastboot only has two options wipe data or usb. My tablet won't show up in adb but when I use fastboot devices command I get 00000 fastboot. I don't know if fastboot is seeing my tablet or not I'm just hoping I can fix it. After taking with people in other forums I've been trying this method
http://forum.xda-developers.com/showthread.php?p=27354963&highlight=fastboot#post27354963
It seems to work until I get to where I have to flash Roach's modded CWM recovery. After inputting the command this is the result I get.
sending 'recovery' (5398 KB)... FAILED (command write failed (Unknown error)) finished
Does anyone here have any idea what's happening with my prime? If so please help, it will be very much appreciated.
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
Sent from my Transformer Prime TF201 using Tapatalk 2
Second option, tell your cousin he owes you 500 bucks, go buy a new prime or infinity and give him the one he broke.
Skitsofrantik said:
I let my cousin borrow my prime while I went out of town for a few days and when I came back my tablet was completely wiped. All that it has on it is fastboot and fastboot only has two options wipe data or usb. My tablet won't show up in adb but when I use fastboot devices command I get 00000 fastboot. I don't know if fastboot is seeing my tablet or not I'm just hoping I can fix it. After taking with people in other forums I've been trying this method
http://forum.xda-developers.com/showthread.php?p=27354963&highlight=fastboot#post27354963
It seems to work until I get to where I have to flash Roach's modded CWM recovery. After inputting the command this is the result I get.
sending 'recovery' (5398 KB)... FAILED (command write failed (Unknown error)) finished
Does anyone here have any idea what's happening with my prime? If so please help, it will be very much appreciated.
Click to expand...
Click to collapse
it is highly unlikely it is bricked for good, you could try running through the steps to enable nvflash, and at the final step rather than booting into android (which you cant) run fastboot boot recovery
I've tried that but thanks for the input
SOTK said:
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
I've tried every driver I could find. I just can't get it to show up in adb devices. going through fastboot seems to work though when i use the command for fastboot to reboot the tablet it reboots. I think I will try TWRP though.
Click to expand...
Click to collapse
lilstevie said:
it is highly unlikely it is bricked for good, you could try running through the steps to enable nvflash, and at the final step rather than booting into android (which you cant) run fastboot boot recovery
Click to expand...
Click to collapse
I'm gonna try this. Thanks for the tip.
Skitsofrantik said:
SOTK said:
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
I've tried every driver I could find. I just can't get it to show up in adb devices. going through fastboot seems to work though when i use the command for fastboot to reboot the tablet it reboots. I think I will try TWRP though.
Click to expand...
Click to collapse
At one time, I had issues getting my PC to recognize my Prime too. You need to completely remove all prior device drivers and THEN install the naked drivers. There's a tutorial in that thread as well as a tool (I think) which you can run on your PC to help you remove previous drivers. Once you know they are gone, follow the directions to install the naked drivers. Its a little cumbersome but the process works. You're gonna keep having issues until you get your PC to recognize your Prime in ADB and Fastboot. You say Fastboot works kinda? So, in the device manager in Windows, it shows your Prime is connected as you're in Fastboot mode? If it doesn't or if it shows as an unrecognized device, I don't see how you're gonna be able to fix your issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Tried NVFlash
I tried NVFlash but I can't get past the first step. When I do this command fastboot -i 0x0b05 flash staging ebtblob.bin I get this result:
sending 'staging' (998 KB)...
OKAY [0.962s]
writing 'staging'...
FAILED (unknown status code)
finished. total time: 10970.597s
Anyone know what's going wrong?
SOTK said:
Skitsofrantik said:
At one time, I had issues getting my PC to recognize my Prime too. You need to completely remove all prior device drivers and THEN install the naked drivers. There's a tutorial in that thread as well as a tool (I think) which you can run on your PC to help you remove previous drivers. Once you know they are gone, follow the directions to install the naked drivers. Its a little cumbersome but the process works. You're gonna keep having issues until you get your PC to recognize your Prime in ADB and Fastboot. You say Fastboot works kinda? So, in the device manager in Windows, it shows your Prime is connected as you're in Fastboot mode? If it doesn't or if it shows as an unrecognized device, I don't see how you're gonna be able to fix your issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Where is the tutorial and tool? I went through it and didn't see it. Even when I completely remove the drivers, when I plug the tablet into the computer when there are no drivers it tries to install it's own drivers and sometimes they install and I get Asus android device in the device manager with Asus fastboot interface as the driver. other times it just fails to install drivers. I know if I get the drivers right I can limp this tablet back to life but it just seems like no matter what drivers i use i just cant get the tablet to show up in adb.
Click to expand...
Click to collapse
Skitsofrantik said:
SOTK said:
Where is the tutorial and tool? I went through it and didn't see it. Even when I completely remove the drivers, when I plug the tablet into the computer when there are no drivers it tries to install it's own drivers and sometimes they install and I get Asus android device in the device manager with Asus fastboot interface as the driver. other times it just fails to install drivers. I know if I get the drivers right I can limp this tablet back to life but it just seems like no matter what drivers i use i just cant get the tablet to show up in adb.
Click to expand...
Click to collapse
If you go into device manager and rightclick the asus android device then update drivers. Now do not let windows choose, do it manually and point windows to the naked driver... Also there are 2 drivers.. one for intel 86 and the other for amd... 64 the numbers are at the end of the file name if I remember correctly... be sure to choose the correct one for your pc chip otherwise yeah you can do it all day and get no where... When you try adb, I will assume you are in recovery mode and not fastboot because they are 2 different horses... If you only have fastboot then you should consider installing an older version of twrp like 2.1... I posted it somewhere in here.... that should get you into recovery where you can adb a rom to the prime.... check for posts by me, I have explained this a few times here.....
From a previous post.....
go here ....http://forum.xda-developers.com/show....php?t=1615990 this is twrp.... download then follow the fastboot install instructions
At this point you probably want to follow the nvflash instructions to install the custom bootloader since twrp says it needs it... go back here and follow instructions... http://forum.xda-developers.com/show....php?t=1774352
start again from ******now boot to recovery....
From the sounds of it you have no rom atm... no big deal... download a rom.. i suggest blackbean or eos...
blackbean found here... http://rootzwiki.com/index.php?/topi...ackbean-(8-15)
eos found here.. http://forum.xda-developers.com/show....php?t=1782413
Download and install http://forum.xda-developers.com/show....php?t=1426502 naked drivers.... follow the instructions...
I prefer blackbean... anyways.... now download nvflash from here http://androidroot.mobi/?p=452
Unzip the file.. put your rom where you find adb.exe shoudl be in C:\nvflash\tf201_nvflashpack if you put the file in C:
*******Now.... boot to recovery... connect tab to the pc.... with the windows open (nvflashpack) clcik in the window... press and hold shift button the right clcik mouse and select open command prompt here... this should give you the command prompt.
Now copy this adb devices right click in the command prompt window and paste... press enter... you should see your transformer...
now type adb push /name of rom you downloaded .zip/ sdcard
This should push the rom to your tab... it will take about 5 minutes be patient....
Install the zip through cwm....
After you accomplish this, you should complete the nvflash instructions and make your backups...
Click to expand...
Click to collapse
adb can't seem to find my device while fastboot does..
I installed the HTCDriver_4.0.1.001 for usb drivers
I can see my device in devicemanagement under Android usb devices > My HTC
this are the cmd results:
C:\Android\fastboot>fastboot devices
FA2AVW103684 fastboot
C:\Android\fastboot>adb devices
List of devices attached
C:\Android\fastboot>
can anyone help me out?
Do you have usb debugging enabled?
Sent from my HTC One X+ using Tapatalk 4 Beta
Roodenburgertje said:
adb can't seem to find my device while fastboot does..
I installed the HTCDriver_4.0.1.001 for usb drivers
I can see my device in devicemanagement under Android usb devices > My HTC
this are the cmd results:
C:\Android\fastboot>fastboot devices
FA2AVW103684 fastboot
C:\Android\fastboot>adb devices
List of devices attached
C:\Android\fastboot>
can anyone help me out?
Click to expand...
Click to collapse
Are you trying to get adb acces to your phone when booted up or in recovery? As already said, in the first case you need to enable USB Debugging in developer options. If your phone is in recovery it may take some minutes for your computer to detect it after starting ADB server.
reaper90 said:
Are you trying to get adb acces to your phone when booted up or in recovery? As already said, in the first case you need to enable USB Debugging in developer options. If your phone is in recovery it may take some minutes for your computer to detect it after starting ADB server.
Click to expand...
Click to collapse
Yes im trying to adb acces from recovery without succes
is it win 8 or 8.1 ?
Win 8.
And i have a international hox+
You can only access adb sideload from your recovery. Every other function of adb is only accessible after your device boots into Android.
wrong wrong wrong, shut up, NasaGeek
Roodenburgertje said:
Yes im trying to adb acces from recovery without succes
Click to expand...
Click to collapse
Works for me without problems on Windows 8. I don't know what driver version i have, i think i installed the driver with htc sync from my phone and uninstalled htc sync later.
Try the following:
1. Connect your phone to your computer and reboot in recovery.
2. Open command line and navigate to the folder where your adb/fastboot files are.
3. Type "adb start-server" and wait some minutes (as i said it may take some minutes to recognize the phone in recovery)
4. Type "adb devices" and now your device should be listed there as in recovery. If not, wait some more time and try again. Shouldn't take longer than 10 minutes. Otherwise there's probably something wrong with your driver and/or adb/fastboot files.
NasaGeek said:
You can only access adb sideload from your recovery. Every other function of adb is only accessible after your device boots into Android.
Click to expand...
Click to collapse
You should have full adb access in recovery .....
Sent from my HTC One X+ using Tapatalk 4 Beta
AndroHero said:
You should have full adb access in recovery .....
Sent from my HTC One X+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
You are quite correct. I don't know what I was thinking. I'll edit my post.
The driver that comes with htc sync works just fine...
Alternate is Koush's universal ADB driver...
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Thermaltake868 said:
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Click to expand...
Click to collapse
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
[email protected] said:
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
Click to expand...
Click to collapse
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Thermaltake868 said:
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Click to expand...
Click to collapse
I always had the device shown as BLANK on "adb" when using windows
whereas on fastboot I never had that issue.....
can u try this
In windows install this MInimal ADB and Fastboot give a try on"fastboot devices" using this
if not working re install the drivers and try the MInimal ADB and Fastboot again
I am suggesting this because it had worked flawlessly for me with proper drivers and MInimal ADB and Fastboot.......
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Thermaltake868 said:
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Click to expand...
Click to collapse
Dude try this USB drivers if nothing works
[email protected] said:
Dude try this USB drivers if nothing works
Click to expand...
Click to collapse
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
EDIT:
I manage to get device ID on adb devices in windows, but when I enter bootloader in fastboot he can't recognized him on command "fastboot devices" he said "device not found", and I can't flash kernel becouse he needs to be in fastboot.
Thermaltake868 said:
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
Click to expand...
Click to collapse
Weird I just installed this and Minimal ADB on my PC and checked....
all good here can see the Device on the adb and fastboot..
try again as administrator or something...might help not sure
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Thermaltake868 said:
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Click to expand...
Click to collapse
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
[email protected] said:
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
Click to expand...
Click to collapse
I am using minimal adb that you gave me, and yes both files are in the folder.
Thermaltake868 said:
I am using minimal adb that you gave me, and yes both files are in the folder.
Click to expand...
Click to collapse
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
[email protected] said:
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
Click to expand...
Click to collapse
I did that too now, and in windows I get adb devices he show me number of my device, my friend told me now that I can flash kernel when I am in OS that I don't have to be in fastboot he will enter fastboot on his own, and I try that too, and as I told he manage to find device via adb, but when he enter bootloader in fastboot he is waiting for device in kernel cmd windows he can't find him.
Make sure your using a USB port that connects directly to your mobo. adb/fastboot is dodgy with USB hubs. Try a port at the back of your PC.
Sent from my HTC One X+ using Tapatalk
I fixed it I had old drivers for USB I installed new from intel chipset did the setup.exe -overall in cmd after that I uninstall htc drivers that I installed before remove them completly restart PC after that install latest HTC Sync connect the phone run the .bat from kernel, and it went successfully.
Thanks for all the help guys
Adb is showing list of devices attached..what is the solution for this..if any one knows how to solve this problem can u help me??
@Vinay23
On the device I'm using, this was under "Default USB Configuration" - advice from others appears to be that selecting PTP is the way to go.
For me, it works =).
Hope that might help out.
I found it here:
“adb devices” returns empty “List of devices attached” on Ubuntu
Based on react native documentation (https://facebook.github.io/react-native/docs/running-on-device) I wanted to connect to ADB in my ubuntu vm (Ubuntu 18.04.2 LTS) but my problem is that i keep ge...
stackoverflow.com
So I have had my Droid DNA for a few months and I've been messing around with it and doing fine. Since I installed TWRP it allows me to delete internal storage...
Oops, there goes my ROM I had saved. Now I'm stuck in either bootloader or recovery. I can't get ADB to recognize my DNA to save my life. It's really really irritating.
I've tried flashing a zip with fastboot since fastboot can recognize my device but ADB can't and it didn't work.
I have Minimal ADB installed and HTC sync manager, but i installed sync after i messed it up so idk if it installed the drivers.
I need a step by step instruction guide to get this to work. I can't find it anywhere. I keep getting no ADB devices and it saying server out of date and what not. I've been searching for hours and hours.
I can't get this to work. I even bought a new phone in the meantime to get me by and that's not exactly what I wanted to do... Any help would be appreciated. Thank you very much!!
No one?
Pretty quite.. I recently had this happen as well.. No fear tho.. If you have twrp already installed your golden.. Download a rom 2 your computer and on twrp goto advanced and sideload.. Command prompt on your computer.. Easiest if found is running xp. Get to your folder of adb hit control and right click poem command prompt here.. adb devices, then adb sideload rom(name). zip.. Your computer will find your device then , and if it didn't send it will allow you to file Explorer.. Throw a rom on your internal reboot into twrp and flash
Æaa..\../
I am lucky I switched to TWRP before this happen, but alas, it's hanging at starting ADB Sideload, doesnt show up in devices either. How do I make it visible so i can just use file explorer from my PC to sideload it?
dyllysoilly said:
I am lucky I switched to TWRP before this happen, but alas, it's hanging at starting ADB Sideload, doesnt show up in devices either. How do I make it visible so i can just use file explorer from my PC to sideload it?
Click to expand...
Click to collapse
You can restrt the phone. Hold down power and volume down together. Then you can reaccess the bootloader from there. If you have twrp you can just go through the file manager instead of messing with sideload.
I'm trying to root my phone on linux, but once i do adb reboot bootloader, my device is nowhere to be found. anyone have a fix? I've searched everywhere.
/thread
Fixed my own issue by plugging the usb cable in the back of my computer. yup, seriously. Thanks to everyone trying to help. Also, thanks for not pointing out what a noob I am.
yepimjosh said:
I'm trying to root my phone on linux, but once i do adb reboot bootloader, my device is nowhere to be found. anyone have a fix? I've searched everywhere.
Click to expand...
Click to collapse
I am not familiar with Linux but on Windows waiting for device comes up when the driver for that phone is installed. May be you can look into it for a solution.
Install the drivers and then give it a try.
yepimjosh said:
I'm trying to root my phone on linux, but once i do adb reboot bootloader, my device is nowhere to be found. anyone have a fix? I've searched everywhere.
Click to expand...
Click to collapse
You need to install adb fastboot these are the instructions you need to type in the terminal you just opened. Type one line at a time and press enter after each. Allow Ubuntu to do it's stuff.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
after you reboot to the bootloader you use fastboot commands ,not adb
clsA said:
You need to install adb fastboot these are the instructions you need to type in the terminal you just opened. Type one line at a time and press enter after each. Allow Ubuntu to do it's stuff.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
after you reboot to the bootloader you use fastboot commands ,not adb
Click to expand...
Click to collapse
I have adb. I'm trying to say, when I'm in recovery mode, my phone is no longer found on my computer. Not just adb, the whole computer
yepimjosh said:
I have adb. I'm trying to say, when I'm in recovery mode, my phone is no longer found on my computer. Not just adb, the whole computer
Click to expand...
Click to collapse
What recovery ? Stock recovery does not support adb
clsA said:
What recovery ? Stock recovery does not support adb
Click to expand...
Click to collapse
Sorry, I'm messing up what I'm trying to say. I have adb and fastboot installed, running on ubuntu 16.04. I plug my phone in, open Terminal, and run adb devies. My device pops up, it's there. So I run adb reboot bootloader, my phone goes on the white screen with the android fellow, and all is good. Now, I i try adb devices again, nothing. I put in lsusb (lists all usb devices connected to computer), and nothing. So, naturally, when i try fastboot oem unlock and my code, I'm stuck on <waiting for device>
yepimjosh said:
Sorry, I'm messing up what I'm trying to say. I have adb and fastboot installed, running on ubuntu 16.04. I plug my phone in, open Terminal, and run adb devies. My device pops up, it's there. So I run adb reboot bootloader, my phone goes on the white screen with the android fellow, and all is good. Now, I i try adb devices again, nothing. I put in lsusb (lists all usb devices connected to computer), and nothing. So, naturally, when i try fastboot oem unlock and my code, I'm stuck on <waiting for device>
Click to expand...
Click to collapse
adb does not work in the bootloader
After reboot bootloader it's fastboot devices
If you get no response try a different usb port
Or different usb cord
Sent from my SM-N920T using Tapatalk
clsA said:
If you get no response try a different usb port
Or different usb cord
Click to expand...
Click to collapse
used the rear usb port and magically decided to work, edited the original post. Thank you for your help and I apologize for the much noobiness you had to encounter.