In Windows I cannot find it at all, running adb devices gives me an error.
In ubuntu it shows up as ??????????? but i have no permissions for some reason, so I cannot do the steps to Bump
Anyone have a way to fix this so I can Bump and finally get on to flashing the Modem, then custom roms finally!
You can also install it from Terminal Emulator, right on the phone, rather than adb. In TE, skip the "adb shell" line, input the 2nd - 4th lines, starting from "su".
chewyTree said:
In Windows I cannot find it at all, running adb devices gives me an error.
In ubuntu it shows up as ??????????? but i have no permissions for some reason, so I cannot do the steps to Bump
Anyone have a way to fix this so I can Bump and finally get on to flashing the Modem, then custom roms finally!
Click to expand...
Click to collapse
You can also use Flashify to flash the bump'd TWRP recovery - that's what I did, worked beautifully. You can find Flashify in the Play Store.
For Linux, you must run sudo adb devices... Then the rsa key will pop up on the phones screen, then your good to go. You must run the sudo command first, or you'll need to run the adb kill-server command, then start again with elevated permissions. If your on 11c, you must be in ptp mode, for 10b ethernet mode.
For Windows, well who cares, use Linux...
annoyingduck said:
For Linux, you must run sudo adb devices... Then the rsa key will pop up on the phones screen, then your good to go. You must run the sudo command first, or you'll need to run the adb kill-server command, then start again with elevated permissions. If your on 11c, you must be in ptp mode, for 10b ethernet mode.
For Windows, well who cares, use Linux...
Click to expand...
Click to collapse
Thank you all. Those adb kill commands were it. Everything worked out fine.. but now when i do the rest of the steps i boot into system recovery (not twrp) but like the phone system recovery, and it seems like thats not what i should be booting into.
annoyingduck said:
For Linux, you must run sudo adb devices... Then the rsa key will pop up on the phones screen, then your good to go. You must run the sudo command first, or you'll need to run the adb kill-server command, then start again with elevated permissions. If your on 11c, you must be in ptp mode, for 10b ethernet mode.
For Windows, well who cares, use Linux...
Click to expand...
Click to collapse
Yeah but those things are spendie and my 3 kids devour any dollars I get lol
WHATSAMATTA U ALUMNI
Related
Hello,everyone.I've got a Sprint optik(zte v55) 7" pad coming with HC 3.2.
After I flash a modified kernel, Its usb debugging mode can't work properly and my pc can't recgonize it.
Before I flash the kernel, when I switched to usb debugging mode and connect to my pc(runing win7), v55 will display a icon in taskbar showing it's connected with pc, my pc will show a new driver that showing the dirs and files in v55's internal storage, and when I run command "adb devices", it will show v55 is connected.
now, all the above is not happening anymore.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
Click to expand...
Click to collapse
Can anybody know what should I do now ? My intention is to root and flash CM10 to v55,and can be recongize by my pc again.
The kernel I flashed into is in http://forum.xda-developers.com/showthread.php?t=1473555,kernel #60 for v55.
mdky said:
Hello,everyone.I've got a Sprint optik(zte v55) 7" pad coming with HC 3.2.
After I flash a modified kernel, Its usb debugging mode can't work properly and my pc can't recgonize it.
Before I flash the kernel, when I switched to usb debugging mode and connect to my pc(runing win7), v55 will display a icon in taskbar showing it's connected with pc, my pc will show a new driver that showing the dirs and files in v55's internal storage, and when I run command "adb devices", it will show v55 is connected.
now, all the above is not happening anymore.
Can anybody know what should I do now ? My intention is to root and flash CM10 to v55,and can be recongize by my pc again.
The kernel I flashed into is in http://forum.xda-developers.com/showthread.php?t=1473555,kernel #60 for v55.
Click to expand...
Click to collapse
Hi, here are some things to keep in mind when using adb.
Be sure of the command you are issuing
Insure you are in fact cd'd to wherever on your pc the adb binary is located
Insure your jdk is included in your path on your pc
To make things easier you can always also add the tools and platform-tools folder of the android sdk to your path
Lets make sure you are properly set up first before you start flashing things randomly.
For more info, you should check Android's page on ADB if you would like. http://developer.android.com/tools/help/adb.html
I'm not sure if any of this is actually directly related to your issue, but it is nice to start with the basics.
wildstang83 said:
Hi, here are some things to keep in mind when using adb.
Be sure of the command you are issuing
Insure you are in fact cd'd to wherever on your pc the adb binary is located
Insure your jdk is included in your path on your pc
To make things easier you can always also add the tools and platform-tools folder of the android sdk to your path
Lets make sure you are properly set up first before you start flashing things randomly.
Click to expand...
Click to collapse
Thank you for reply.
The adb command I use is install by v55's driver.Everytime I use adb, I always go into the driver's dir (C:\Program Files\ZTE Tablet V55 USB Driver) which adb.exe is in.
And this dir is in my path.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
mdky said:
Thank you for reply.
The adb command I use is install by v55's driver.Everytime I use adb, I always go into the driver's dir (C:\Program Files\ZTE Tablet V55 USB Driver) which adb.exe is in.
And this dir is in my path.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
Click to expand...
Click to collapse
Ooook now we're getting somewhere, I think
Make sure when you send your fastboot flash command you send it like so:
Code:
fastboot flash recovery recovery.img
Replace 'recovery.img' with the actual name of the img, whatever it is.
Also if you are getting the device offline error try killing server:
Code:
adb kill-server
and then restart it
Code:
adb start-server
See if that helps.
wildstang83 said:
Ooook now we're getting somewhere, I think
Make sure when you send your fastboot flash command you send it like so:
Code:
fastboot flash recovery recovery.img
Replace 'recovery.img' with the actual name of the img, whatever it is.
Also if you are getting the device offline error try killing server:
Code:
adb kill-server
and then restart it
Code:
adb start-server
See if that helps.
Click to expand...
Click to collapse
I will try these command when I get home, thank u!:good:
"adb kill-server" and "adb start-server" works fine.They turn v55's "adb devices" from "offline" to "recovery".
And I run command "adb reboot-bootloader", it seems that v55 is in bootload mode.
But after that,I run command "fastboot flash recovery CWMrecovery.img",it returns '<waiting for device>' and stuck there.
Before I flash the kernel #60, I can run "fastboot boot CWMrecovery.img" to boot to cwm,so I think it's not likely be the driver's problem,am I right?
mdky said:
"adb kill-server" and "adb start-server" works fine.They turn v55's "adb devices" from "offline" to "recovery".
And I run command "adb reboot-bootloader", it seems that v55 is in bootload mode.
But after that,I run command "fastboot flash recovery CWMrecovery.img",it returns '<waiting for device>' and stuck there.
Before I flash the kernel #60, I can run "fastboot boot CWMrecovery.img" to boot to cwm,so I think it's not likely be the driver's problem,am I right?
Click to expand...
Click to collapse
Sorry to take so long to reply. I think it is not a driver issue. Do you know if debugging/adb is even enabled in the ramdisk? This generally would have to be done by the dev who created the kernel. Speaking of that, have you tried to contact that dev for further support? For sure they would know more than me since I don't own the device myself. I just know enough to be slightly dangerous, lol
wildstang83 said:
Sorry to take so long to reply. I think it is not a driver issue. Do you know if debugging/adb is even enabled in the ramdisk? This generally would have to be done by the dev who created the kernel. Speaking of that, have you tried to contact that dev for further support? For sure they would know more than me since I don't own the device myself. I just know enough to be slightly dangerous, lol
Click to expand...
Click to collapse
It's very nice of you to keep help me here ,thanks again:good:!
After keep trying in past two days, I found that in ftm mode adb is enabled, and 'adb reboot bootloader' truly made the device into bootloader mode.
On my win7 pc, It can't be recognized.I switch to my old xp pc,and install the driver come from other zte user,and then...fastboot works.
Now I have the v55 running CM10,Awesome!Thanks to all contributors.
Still, my win7 pc and xp pc can't recognize my v55 through usb.But it's not big deal now.I can use tf and wifi and other ways to transfer file to v55.
mdky said:
It's very nice of you to keep help me here ,thanks again:good:!
After keep trying in past two days, I found that in ftm mode adb is enabled, and 'adb reboot bootloader' truly made the device into bootloader mode.
On my win7 pc, It can't be recognized.I switch to my old xp pc,and install the driver come from other zte user,and then...fastboot works.
Now I have the v55 running CM10,Awesome!Thanks to all contributors.
Still, my win7 pc and xp pc can't recognize my v55 through usb.But it's not big deal now.I can use tf and wifi and other ways to transfer file to v55.
Click to expand...
Click to collapse
Oh wow, that is quite the ordeal, but atleast its something huh, lol
I wonder if you could run adb and fastboot commands in xp mode on your win7 pc?
I know there is a way to run programs in XP mode, its just been awhile since I've done it.
And its no problem to keep trying to help, even if I don't know the device and all that. Maybe I can learn to while we are at it, and maybe make a new friend along the way
This is the method I used to S-Off several devices (8 in total) on Windows 7 64 bit.
Remember, Team Unlimited does not recommend that you use any OS that is not supported as the drivers can cause some issues.
I have included a method that will test whether your drivers in your current setup will perform in a way that reduces the chance of all hell breaking loose.
Before starting, make sure you have downloaded and installed the HTC drivers for your phone and have Adb downloaded. A great place to get this is from “Team fireballas FakeCid AUTOMATIC bootloader unlock” thread.
We will need this file for a later process as well. (File Download)
Once downloaded, unzip it to C:\Root.
Verifying that your drivers are working correctly. (Typed commands are in red)
1) Attach your phone to you computer with the supplied USB cable.
2) Enable USB Debugging (Settings>Developer Options>USB Debugging)
3) Open a command prompt and navigate to the location you extracted the adb files to by typing: cd\
Then type: cd c:\Root\stuff
Your Prompt should read:
c:\Root\stuff>
4) Now type adb devices
You should see the following output in the command prompt.
C:\ Root\stuff >adb devices
List of devices attached
HT26KS311633 device
Your device will have a different device ID than what is listed above. Just make sure it shows a device ID and device listed after it.
5) Now type: adb reboot bootloader
At this point your phone should reboot into the bootloader with Fastboot selected.
6) Type: fastboot devices
You should see the following output in the command prompt.
C:\inc4>fastboot devices
HT26KS311633 fastboot
Ensure that your device is listed. Your device will have a different device ID than what is listed above. Just make sure it shows a device ID and fastboot listed after it.
7) Type: fastboot reboot
You should see the following output in the command prompt.
C:\inc4>fastboot reboot
rebooting...
finished. total time: 0.070s
Your phone should be rebooting.
You have now verified that your drivers are working correctly even after rebooting into fastboot.
At this point I cannot give you alternative instructions per Team Unlimited. So follow the directions listed HERE.
When you reach step 12 which states:
“Temproot your phone via any method available - we cannot help with this step and it is REQUIRED!”
Follow the following steps that were originally written by captainrewind in the “Team fireballas FakeCid AUTOMATIC bootloader unlock” thread.
Go to Settings -> Connect to PC and change Default connection type to Disk drive and disable Ask me.
Navigate to the folder in the command Prompt by typing
cd c:\Root\stuff
Now that you're there, type:
adb devices
If your phone pops up in the list, you're good to go!
Next, type
adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet!
Now type:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
(errors will appear, ignore)
Accept the restore on the device, then type:
adb reboot
(At this time, you are temprooted, and the phone UI will be in an unusable state, with temproot shell.)
After reboot type:
adb shell
Verify that the prompt is "#" (meaning root) or "$" (meaning normal user). If it's not "#", please start over.
You can now return to Team Unlimited’s instructions and continue with step 13.
This should take you the rest of the way to S-Off.
*Madmoose* said:
I have included a method that will test whether your drivers in your current setup will perform in a way that reduces the chance of all hell breaking loose.
Click to expand...
Click to collapse
Excellent suggestion and great advice. Always make sure your computer can recognize your device in all device states before attempting root.
I found the hard way on a Kindle Fire and now always do this test (a couple of times) to make sure the device being rooted can be seen in all states by the PC. For whatever reason, my (original) Kindle Fire has a different USB Enum for each state and my Windows 7 64-Bit computer didn't recognize it in fastboot which caused a lot of irritation.
This is helpful but I believe unlimited specifically asked not to have any other how to threads
Sent from my Nexus 7 using Tapatalk 2
This isn't a how to about Unlimited's process. And frankly, they can request anything they want, but they will not control other peoples threads. They were talking about their own thread.
*Madmoose* said:
Next, type
adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet!
Now type:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
(errors will appear, ignore)
Accept the restore on the device, then type:
adb reboot
Click to expand...
Click to collapse
I'd like to comment on this part, since it threw me off a bit and scared the daylights out of me.
After you issue the "while..." command, you'll get infinitely scrolling errors/warnings, or at least I did in Ubuntu. Just ignore them, nothing is wrong. While they are infinitely repeating in your terminal, just accept the restore on the phone and they stop. I don't remember the exact text of the error, but if someone could put it here that would probably be helpful to anyone wondering.
Very cool. Thanks madmoose!
Is It Working with HTC ONE V (GSM) ???
No dude this is the incredible 4G threads
I am so going to do this. Soon. Hawk might have an Ecliptic release some day.
Linch89 said:
No dude this is the incredible 4G threads
Click to expand...
Click to collapse
Will this make my laptop s-off
Sent from my Nexus 7 using Tapatalk 2
Only if your laptop is an Incredible 4G...
Add me to the list of S-OFF via Win7 64bit. I restored my Viper TWRP backup and all is running smootly. Now, I am off to customize my bootloader with RegawMOD Bootloader Customizer.
Used a modified version of this to achieve s-off but what really helped me was the "Verifying that your drivers are working correctly." section. When I had tried unlocking earlier I keep getting stuck in the error looping screen when restoring the fakebackup. This little set of instructions pointed me in the right directions for getting the drivers installed correctly.
Many thanks MadMoose and Happy New Year! :victory:
Many thanks to MadMoose. Everything worked for me on Win7 64bit as well, and would have worked more smoothly if I had done it your way
Yesssssssssssssssssss
Wow what a journey, used it on my 64 bit computer per another post here that gave a very nice detailed instructions. had to relock, temproot, s off, flash recovery, and then restore... but i would do it 100 times again! thanks everyone for your activeness in this community, hopefully it continues to grow
Has anyone tried to get s-off with Windows 8 x64 yet? I copied in the drivers, tried all the commands, and they replied normally. Will I brick my phone if I try?
I'm afraid it won't work unlimited said that 64 win7 wasn't officially supported it just happens to work
It may work but unlimited won't help/support you if you have problems.
bberryhill0 said:
It may work but unlimited won't help/support you if you have problems.
Click to expand...
Click to collapse
I'm just wondering if it doesn't work, then am I bricked? Or can I just pull the battery and restart?
spectre559 said:
I'm just wondering if it doesn't work, then am I bricked? Or can I just pull the battery and restart?
Click to expand...
Click to collapse
Went ahead with s-off in win 7 x64. Success!
I looked all over the internet for help with this phone. I rooted it for a friend and a week later, he said he restarted the phone and everything started force closing.
I troubleshot all day, and came to figure out that my only known to me as of now, is flashing CWM to it, via ADB. I am having several issues with setting up ADB, and getting the phone to communicate with my computer. Device manager DOES show that there is an ADB device installed correctly, so what would my next move be? I got the phone into FTM mode, (fastboot?) and I know that that is what I need to do to get ADB to communicate with my phone.
halp pls
Really no one can help???
bamp
cammiso94 said:
bamp
Click to expand...
Click to collapse
ADB Drivers for Windows Vista/7
Tutorial- http://www.youtube.com/watch?v=RDA8PpPSFuk
If you havn't found this yet...
Your answer is here: androidforums.com/flash-all-things-root/ Good luck!:good:
CWM Beta
From Android Forums ... Thanks to Junkie2100
this is an unfinished copy of cwm, tested to be almost completely functional
standard warnings apply, use at your own risk, you try to blame me for breaking your phone i will laugh at you
instructions:
fastboot method is possible, but i will go through the terminal/adb method
download the recovery file, and put it on the root of your sd. no folders, just directly on the sd
get your phone rooted and get a copy of terminal emulator or connect to it through adb on your computer, adb will require zte drivers and the adb program on the pc. the choice is yours
fire up adb by typing
Code (Text):
adb shell
in the command prompt, if its not working you dont have adb in the directory youre in, just copy adb.exe and the two .dll files to c:\windows\system32\ and itll work from anywhere, or learn how command prompt works
or fire up terminal emulator on the phone
on adb shell or terminal emulator type
Code (Text):
su
dd if=/sdcard/flash_cwm_test2.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
you will then need to run
Code (Text):
reboot recovery
and then hit reboot when cwm comes up, if it asks to disable recovery flashing press yes or it will put stock recovery back next time the rom boots
known bugs:
unmounting doesnt work
downloads:
w.ww.4shared.com/file/2qBR2Kfr/flash_cwm_test2.html
i apologize for it being 4shared, if someone wants to make a mirror ill put it up
Okay so as we all know Bootloader was unlock and they specify the steps, but im not able to do the command prompt section.(Below)
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-2.8.0.0_vs985-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I have the twrp image on my storage, but i used mtp not Ethernet due to the reason that Ethernet mode won't read my phone.
Can anyone help me on how to void my warranty and get CP working
Please no hating, barely learning this stuff
Thanks!!
You need to have USB debugging enabled on your phone, adb installed on your computer and the LG drivers installed. If you have all that the steps to unlock are quite clear.
Also your phone needs to be on and you need to keep an eye on it as you will have to enable a couple of things when they pop up on your phone, one is to allow your computer to see your phone in debugging mode and the other is to Grant super user permission.
batsup606 said:
Okay so as we all know Bootloader was unlock and they specify the steps, but im not able to do the command prompt section.(Below)
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-2.8.0.0_vs985-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I have the twrp image on my storage, but i used mtp not Ethernet due to the reason that Ethernet mode won't read my phone.
Can anyone help me on how to void my warranty and get CP working
Please no hating, barely learning this stuff
Thanks!!
Click to expand...
Click to collapse
You need to be able to get the phone operating in Ethernet mode; otherwise the computer cannot pass it commands. Alternatively, you can use a terminal emulator ON your phone itself. That's what I did as I didn't want to boot my desktop rig up before I left. It works exactly the same, except you don't type "adb shell", just open the term emu and start with the SU line.
It works fine if you do it from a terminal emulator on ur phone just fyi
laxattack said:
It works fine if you do it from a terminal emulator on ur phone just fyi
Click to expand...
Click to collapse
Can confirm. This is the way I did it since I don't have access to a computer until later tonight. Just type the exact commands (except for adb shell) in a terminal emulator and you are done.
I can also confirm this is working.
I had to download the LG updater or whatever (when you first plug the phone in; says installer) despite Win7 saying it had autoinstalled the drivers then ADB could see the device when in ethernet mode.
Also the last command didn't work (guess I didn't have the TWRP in the right place) and was forced to do a battery pull after the Factory Reset (didn't erase my data or settings), booted fine and then I just flashed the recovery with Flashify (and now can get into recovery) but YMMV.
FLASHIFY
Hey whats up the easiest way to install this is an app called Flashyify in play store works great im unlocked without using adb. Let the roms begin. Thanks for the hard work that everyone put in. Just put twrp image on phone before you open flashyify and open and install and recovery will be installed
airintak25 said:
Hey whats up the easiest way to install this is an app called Flashyify in play store works great im unlocked without using adb. Let the roms begin. Thanks for the hard work that everyone put in. Just put twrp image on phone before you open flashyify and open and install and recovery will be installed
Click to expand...
Click to collapse
+1
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.