Database Users

ADB not working

Hi,
I'm following the instructions for how to prepare my Magic to load a new ROM from the Wiki (http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking) but I'm having problems with ADB not recognising the device.
If I boot into Fastboot mode, and use fastboot devices my phone is listed, but adb devices returns no results.
1) is it necessary to have adb working?
2) If so, any suggestions as to why it's not?
I've followed the instructions to the letter so far, and I'm worried that my phone might be a pre-production model (I review phones for a magazine - I want to try new ROMs so I can report on the new features in 1.6 and later as they come out.)
When booted normally, in Device Manager under Device Instance Path I see:
USB\VID_0BB4&PID_0C02&MI_01\6&29B48A3A&0&0001
Dunno if this helps, but the Wiki says something about changing the driver .ini file - I can't find this .ini file either, where would I look?
BTW I'm running Windows 7 release.

bpdlr said:
Hi,
I'm following the instructions for how to prepare my Magic to load a new ROM from the Wiki (http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking) but I'm having problems with ADB not recognising the device.
If I boot into Fastboot mode, and use fastboot devices my phone is listed, but adb devices returns no results.
1) is it necessary to have adb working?
2) If so, any suggestions as to why it's not?
I've followed the instructions to the letter so far, and I'm worried that my phone might be a pre-production model (I review phones for a magazine - I want to try new ROMs so I can report on the new features in 1.6 and later as they come out.)
When booted normally, in Device Manager under Device Instance Path I see:
USB\VID_0BB4&PID_0C02&MI_01\6&29B48A3A&0&0001
Dunno if this helps, but the Wiki says something about changing the driver .ini file - I can't find this .ini file either, where would I look?
BTW I'm running Windows 7 release.
Click to expand...
Click to collapse
I had this problem and what I had to do was:
be sure no USB drives/memory cards were connected
connect the phone
uninstall USB Mass storage device from device manager under usb controllers
disconnect/reconnect the phone
install the driver from the sdk/usb_driver folder

Thanks, but...
I tried this, but still not luck with adb. I now see a new "ADB Interface" section in Device Manager, and an "HTC Dream Composite ADB Interface" device underneath, but adb devices command still returns no devices.

Sorted!
Well, I'm not sure how but I managed to get it to work, and am now the proud owner of a Magic running Cyanogen mod

[solved] fastboot problem for Dell Streak under Linux

Hi,
need some help with fastboot.
Entering "./fastboot devices" gives no results.
Streak waits with white screen and displays FASTBOOT_MODE.
I did not install the SDK, but took the adb tool from the current SDK.
Entering "./adb devices" list one device - works!
I noticed that it is important to use the adb from the current SDK currently adb version 1.0.26 (an old adb version 1.0.25 did not work).
Streak with Stock Froyo
Linux / Ubuntu 10.04
Streak is recognized as (lsub): Bus 001 Device 011: ID 413c:b007 Dell Computer Corp.
Any idea? Are there different fastboot-binaries out there? All the ones I have found are 127435 bytes.
Thanks a lot
Arnd

I have exactly the same problem on ubuntu 10.04 with standard 2.2 Froyo.
adb devices shows the Streak but fastboot devices shows nothing. I have played with this for a while without success. I would love to have this working any help would be appreciated. I am using android-sdk-r07-linux_x86.tgz and fastboot 130.4 kb.
The streak is detected on USB and I can turn on and access USB storage.

Solved
Just found out, "./fastboot devices" simply does not work - unfortunate.
But try "sudo ./fastboot -i 0x413c reboot" - this will show "rebooting..." and actually reboot the device. Must be with sudo.
That means fastboot works.
I suppose, no need to install the SDK, no need to put any rules files into /etc/udev/rules.d
Arnd

[Q] Working with ADB & Fastboot

Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!

feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.

feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
Which OS are you using (Windows, Mac, Linux)?

Elrondolio said:
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
Click to expand...
Click to collapse
It's the latest SDK.
bsara said:
Which OS are you using (Windows, Mac, Linux)?
Click to expand...
Click to collapse
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Hope this helps someone. Cheers!

feered said:
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Click to expand...
Click to collapse
I had the same issue on Ubuntu. You need to run ADB with sudo...why? I have no idea...but I found a post suggesting it on StackOverflow and it worked...so I'm not questioning it.
Before doing anything below, have you installed adb via apt-get? If so, remove it and just put a link to your SDK manager adb and fastboot in a folder included in your PATH or add the directory to the path, then start a new shell before proceeding. The adb and fastboot provided by apt-get are old.
Do the following:
Have your device plugged in and fully booted and with USB debugging enabled
run this command: "sudo adb kill-server && adb start-server"
You should be prompted on the device to authorize the access of your computer via adb
run "adb devices" to make sure that it all worked correctly

[how to]restore software status official

*this thread is for m9+. it will NOT work on m7,m8,m9(or anything else). search your device general forum for a specific thread
if you have recently s-off'ed using an exploit that changed your banner in the bootloader screen to software status: modified,then this thread is for you.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on
the usual disclaimers:
this has been tested,but if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for schooling me on echo command protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info) wich started off my love for chasing such things.
- @omar302 for getting the ball rolling,providing dumps,and lots of testing. he s-on'ed his phone several times during the tests,and has provided a huge amount of valuable info
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and lower)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "tampered flag"
enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p11 bs=1 seek=39940
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify software status: official
if this does not work for you
*first reread this thread in its entirety. make sure you have met the prerequisites,and double check your code and make sure you have not forgotten a step,or screwed something up trying to type it (especially if using a terminal emulator),and check that you have not gotten any errors.
if youre still confident you did things correctly,you need to PM me:
1)the results of: fastboot getvar all
2)a link to an uploaded p11.
you get fastboot getvar all by:
-place phone in fastboot
-enter in fastboot getvar all right click,click mark,highlight in white,hit enter or right click to copy
you dump p11 by:
adb shell
su (if needed to get a #)
dd if=/dev/block/mmcblk0p11 of=/sdcard/mmcblk0p11
transfer the file on internal storage to your pc and upload it
im not trying to be a ****,but its not helpful to post "didnt work" if you screwed something up,or if your not willing to help find a solution. especially if others have found it to work on their same variant.
important:
from now on,i will need a copy of your cmd window as well if we want to get to the bottom of whats happening. some folks seem to be simply writing extra bytes,wich is screwing up the flag location. please make sure this shows an entire session,not just a last part where it looks correct. we cant figure it out if you only show part of what you did.

mine too

scotty1223 said:
mine too
Click to expand...
Click to collapse
@Scotty. What we need is how to change from Relocked to Locked on Bootloader.

deleted. Better to wait Scotty's stock guide.

west2cool said:
@Scotty. What we need is how to change from Relocked to Locked on Bootloader.
Click to expand...
Click to collapse
You cannot do it without turning s on. P9 is now being protected,and any attempts to modify it in any manner result in security being turned back on
Planning a back to stock guide once I'm fairly certain it can be done safely
Sent from my Nexus 9

yvtc75 said:
echo -ne ......
Click to expand...
Click to collapse
Don't do this unless you're ready to be stock and s on,and have all your ducks in a row. It could leave you bricked or stuck in the bootloader with a security warning.
There's good reason I didn't post it.
Sent from my Nexus 9

Just to confirm that it worked fine on my phone as per the screen photo in OP post. Also, just a warning to others, S-Off through SunShine might give you problems or would fail in case of repeated attempts (going back & forth between S-ON & S-OFF).
Thanks again to @scotty1223 for his help & work time this possiblef or the M9+.

Worked for me! Thanks!

omar302 said:
Just to confirm that it worked fine on my phone as per the screen photo in OP post. Also, just a warning to others, S-Off through SunShine might give you problems or would fail in case of repeated attempts (going back & forth between S-ON & S-OFF).
Thanks again to @scotty1223 for his help & work time this possiblef or the M9+.
Click to expand...
Click to collapse
Could you please detail, what problems? I s offed twice, but I'll be cautious if I knew there might be a problem

tbalden said:
Could you please detail, what problems? I s offed twice, but I'll be cautious if I knew there might be a problem
Click to expand...
Click to collapse
Apparently SunShine has some security system that detects if you are unlocking many times & then would just stop stop working & gives you message that your device is acting in an unusual way. I then had to contact their support to get it resolved.

i am rooted but s on, how can i s off to use your method? can someone help me

Rabia said:
i am rooted but s on, how can i s off to use your method? can someone help me
Click to expand...
Click to collapse
Currently they are using sunshine
Sent from my HTC One using Tapatalk

scotty1223 said:
Currently they are using sunshine
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
is that the paid thing, do they send a file accross or is it a physical thing

Rabia said:
is that the paid thing, do they send a file accross or is it a physical thing
Click to expand...
Click to collapse
http://theroot.ninja
Sent from my HTC One using Tapatalk

Rabia said:
is that the paid thing, do they send a file accross or is it a physical thing
Click to expand...
Click to collapse
You install the app & run it on your phone with a internet connection, after the app makes some tests & confirms your device is compatible you will be prompted to pay through the app itself ($25.00). The app itself will run & phone restart & then you get S-OFF. My M9+ was also from UAE (official-UAE version) & S-OFF worked from the 1st time. Very simple process.

Stock Locked bootloader?? @scotty1223

jureca said:
Stock Locked bootloader?? @scotty1223
Click to expand...
Click to collapse
Not possible currently. Attempting to modify p9 will cause you to turn s on. It may be possible to use it to your advantage if you need to be 100% stock,but I haven't had a chance to come up with a process that I believe would be 100% safe for all users
Sent from my Nexus 9 using Tapatalk

scotty1223 said:
Not possible currently. Attempting to modify p9 will cause you to turn s on. It may be possible to use it to your advantage if you need to be 100% stock,but I haven't had a chance to come up with a process that I believe would be 100% safe for all users
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
Ok thank you, see if you can :good:

Nexus 7 2012 bricked, adb/fastboot connection ok but unauthorized. Can You help?

Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?

Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.

Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.

Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.

Following
I have the same error and like to follow

Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.

thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.

No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.

Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.