I had installed Kali Nethunter 3 on my Nexus 9 with TWRP, then it started to bug out, so I 'factory reset' it to stock Marshmallow, but when I look in the 'About Tablet' it is still showing [email protected] #2 in the kernal version. I would like to flash stock Nougat, but I cant get my ADB to authorize. I cant get the RSA key authorization dialogue to come up on my device. I do have USB debugging enabled.
If I plug it in while the adb server is started, it does generate adbkey files inside the .Android folder on the Windows machine. I was thinking that I could put these adbkey files into whatever folder they are supposed to be in, on the nexus 9 (data/something...? my data folder looks empty).
Alternatively, could I just put the nougat image onto my nexus 9 and flash it back to stock using TWRP? Ideally making my kali root kernal go away forever? I am not concerned about losing any data.
Not really sure what I am doing here, I just want stock unrooted Nougat and I want my ADB to work again (so I can use it to debug my Android Studio apps)! Thanks.
Can you get a fastboot connection?
Sent from my Nexus 5X using Tapatalk
ritchea said:
Can you get a fastboot connection?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
with my cmd prompt in the platform-tools, if i type 'fastboot.exe devices' nothing happens, it just goes to the next line.
Type fastboot devices
Sent from my Nexus 9 using Tapatalk
junkomatic said:
with my cmd prompt in the platform-tools, if i type 'fastboot.exe devices' nothing happens, it just goes to the next line.
Click to expand...
Click to collapse
and when i type 'fastboot start-server' it says: "< waiting for any device >".
ADB at least can see the device - just says its unauthorized.
I'm not familiar with either of the commands you mentioned as I've never used them. If 'fastboot devices' doesn't return your device, try updating all PC device drivers related to android while connected to fastboot. You don't need adb to install google images, but you need your PC to recognize device (as you know).
EDIT: Is your tab rooted? If so, you can use FlashFire to run the installation without a computer.
If no joy so far, disconnect tab, remove all drivers and let PC redo them when you reconnect. You should get the authorization prompt again.
Sent from my Nexus 9 using Tapatalk
ritchea said:
I'm not familiar with either of the commands you mentioned as I've never used them. If 'fastboot devices' doesn't return your device, try updating all PC device drivers related to android while connected to fastboot. You don't need adb to install google images, but you need your PC to recognize device (as you know).
Click to expand...
Click to collapse
It shows up in my windows devices as Nexus 9, and inside the android studio device manager it is showing the device as unauthorized. I suppse i will try updating all the drivers again.
ritchea said:
I'm not familiar with either of the commands you mentioned as I've never used them. If 'fastboot devices' doesn't return your device, try updating all PC device drivers related to android while connected to fastboot. You don't need adb to install google images, but you need your PC to recognize device (as you know).
EDIT: Is your tab rooted? If so, you can use FlashFire to run the installation without a computer.
If no joy so far, disconnect tab, remove all drivers and let PC redo them when you reconnect. You should get the authorization prompt again.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
yeah it was rooted for kali nethunter. i will check out flashfire, thanks.
FlashFire works great.
Sent from my Nexus 9 using Tapatalk
junkomatic said:
yeah it was rooted for kali nethunter. i will check out flashfire, thanks.
Click to expand...
Click to collapse
so actually it was unrooted during my last factory reset. i finally figured out how to use fastboot to update to nougat, and all the remnants of kali in the kernal is gone. my ADB is working fine now, and i can test on my nex9 from android studio. i used this guide: http://wccftech.com/flash-nbd91k-android-7/
life is good. thanks guys.
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...
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Tommyboy77 said:
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Click to expand...
Click to collapse
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
es0tericcha0s said:
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
Click to expand...
Click to collapse
adb devces does not work in clockwork mod either.....what is the easiest way to get this custom rom sent to my internal sd card if the phone wont boot up and os is wiped off the phone? it is an htc one...
adb should work in CWM... You might have to manually load the driver. Even if every driver works when the phone is booted and all, Windows can still have issues finding the right one in recovery. Check in your device manager. If that doesn't work, then you'll have to see if your recovery supports USB OTG and see if you can load like that. If none of that works, you'll have to reload the OS via RUU and start over with root/recovery/etc.
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
C13v3r0n3 said:
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Neither of those things are options for the OP. He can't boot, so he can't mount USB (mounting USB in recovery hasn't worked for most phones since JB where most phones don't support USB mount - only MTP) and he can't sideload because he hasn't been able to get ADB working.
His options now are:
Find out why the adb driver isn't loading so he can just adb commands to push the file or sideload
USB OTG
Return to stock via RUU
I unlocked the bootloader and went to root. on the first reboot after rooting it's stuck on the boot animation. When i plug the device into my PC and use the cmd prompt "adb devices" it won't see it. I help the power button and vol down to get to fastboot and my pc still won't see it. i've tried to factory reset though fast boot, says erasing, then reboots and still stuck. I updated everything in adb and still nothing. Everything went fine with unlocking the bootloader, but rooting it totally messed something up.
I can't seem to figure out how to get my PC to see this thing again. It's kind of a crap tablet to begin with, and now i brick it? totally frustrated.
Thanks
when you connect to pc,did you hear pop up connect sound..if yes then you connect to your pc..download google factory image,flash system.img,boot.img and all other .img image..hopefully you can restore tab back to nermal..good this is your tablet already unlocked bootloader.
Sent from my Nexus 9 using Tapatalk
Adb can do almost nothing when your device is in fastboot mode. Use fastboot to see if your device is connected to your computer if you didn't do so.
try "fastboot devices".
corkiejp said:
try "fastboot devices".
Click to expand...
Click to collapse
I just got "waiting for any device". I have the path set up to "C:\android-sdk\tools;C:\android-sdk\platform-tools". I haven't changed anything since i unlocked the bootloader so i'm just confused.
kacang87 said:
when you connect to pc,did you hear pop up connect sound..if yes then you connect to your pc..download google factory image,flash system.img,boot.img and all other .img image..hopefully you can restore tab back to nermal..good this is your tablet already unlocked bootloader.
Click to expand...
Click to collapse
The safely removed hardware icon does show up in the task bar. When i got to printers and devices there is an "android".
https://www.dropbox.com/s/a5chez6r9cuxjzo/Capture.JPG?dl=0
Can i use that port to force adb to see it? Not sure if this helps
gotta run to work, i'll mess with it this afternoon. Thanks guys.
First make sure your in "fastboot" mode and not in the bootloader.
Your device should show up as under Android Device as "Android Bootloader Interface" in device manager on your PC.
If not there then your drivers are not configured correctly, Nexus Root Toolkit has a guide on how to setup drivers correctly.
corkiejp said:
First make sure your in "fastboot" mode and not in the bootloader.
Your device should show up as under Android Device as "Android Bootloader Interface" in device manager on your PC.
If not there then your drivers are not configured correctly, Nexus Root Toolkit has a guide on how to setup drivers correctly.
Click to expand...
Click to collapse
I tried uninstalling the drivers from device manager and that didn't seem to do it. I went into the sdk and deleted them from the sdk then reinstalled them through the sdk and that seemed to work. I feel like i should have thought of that! duh. flashing CM13 now! hope i can get this to work haha jeeze.
thanks for the help guys
Hi all,
I'm here because i don't know where else to look..
I've got a nexus 9 tablet running 5.1.1, its rooted with an unlocked bootloader, running twrp custom recovery, i was trying to flash a new rom, now all i get is a constant google logo upon bootup, I can enter recovery and fastboot and all of that, but none of my computers can see the tablet in adb or fastboot when I plug it in via usb, so Im not able to flash anything from my computer, does anyone have any ideas? or have I totally ****ed my nexus 9?
I have 2 laptops running Ubuntu, and my desktop is Windows 7 with all the necessary drivers, I've never had issues connecting my devices in the past, so I'm kinda at a loss.
have you flash all the .img file manually..if yes then try to factory reset first and see what happen..if no then you need to flash stock recovery and then factory reset..hopefully it help
Sent from my Nexus 9 using Tapatalk
Check your drivers in windows again.
Nexus Root Toolkit has a driver guide if needed.
Hope your not trying "adb devices" while in fastboot mode? Try "fastboot devices" while in that mode.
kacang87 said:
have you flash all the .img file manually..if yes then try to factory reset first and see what happen..if no then you need to flash stock recovery and then factory reset..hopefully it help
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
I have tried to do that, factory reset just resulted in no change to the tablet
corkiejp said:
Check your drivers in windows again.
Nexus Root Toolkit has a driver guide if needed.
Hope your not trying "adb devices" while in fastboot mode? Try "fastboot devices" while in that mode.
Click to expand...
Click to collapse
no, no, I know not to use adb devices while in fastboot, but I can put my tablet in fastboot, but any time I try to give it a command via my laptop, it just says "waiting on device", its like the computer doesn't recognize that the tablet has been connected...
Baskinmfr said:
no, no, I know not to use adb devices while in fastboot, but I can put my tablet in fastboot, but any time I try to give it a command via my laptop, it just says "waiting on device", its like the computer doesn't recognize that the tablet has been connected...
Click to expand...
Click to collapse
change your cable connect to computer..some cable cannot sent data..happen to me
Sent from my Nexus 9 using Tapatalk
Can you enter recovery? If you can then use your computer to copy the zip file of a rom and install it. Otherwise check your cable, I had problems with the one htc gave me.