Database Info

cannot access adb and cannot bypass registration?

ok so i downloaded the SDK and the windows drivers. i downgraded the phone to rc29 and have just enabled adb on the phone using the command <enter>setprop persist.service.adb.enable 1<enter> and <enter>telnetd<enter>. i opened up CMD in windows and changed the directory where i needed and tried to run adb and it gave me this error: "* daemon not running. starting it now *
* daemon started successfully *
error: device not found"
why did it give me this error? and alo im stuck at the part where im supposed to "copy a busybox binary" using adb push. i dont know exactly what im supposed to do to do that step. i am a noob at this stuff so please be kind and use noob terms and steps.
Thanks
PS: i did connect the phone to the pc with the data cable and the add new hardware thing popped up and i installed the drivers like i was supposed to. it said something about they were installed correctly but may not be working properly, whatever that means.

Try this....
Unplug the phone.
Reboot the computer.
When fully rebooted, plug the phone back in and see what the computer does.
Did it say, "Found new hardware" or some such message?
Did it say that it couldn't find a driver?

Okay - after the OTA updates, I'm now having the same problem! Ouch!
Plugging in, running DOS Command...
c:\> adb devices
Reports that there are no devices attached!
BUG!!!!!!!!!!!!!!!

[Q] adb returns 'error: device not found'

I have android running on a cubieboard, I am trying to install an app from within the device itself. The device has a serial port interface so I have access to the file system and command line access. when I run "adb install <appname>" all I get is 'error: device not found', what is this and how do I find out what device is not found.

xvart said:
I have android running on a cubieboard, I am trying to install an app from within the device itself. The device has a serial port interface so I have access to the file system and command line access. when I run "adb install <appname>" all I get is 'error: device not found', what is this and how do I find out what device is not found.
Click to expand...
Click to collapse
Make sure USB Debugging is turned on in the Settings on your device.

xvart said:
I have android running on a cubieboard, I am trying to install an app from within the device itself. The device has a serial port interface so I have access to the file system and command line access. when I run "adb install <appname>" all I get is 'error: device not found', what is this and how do I find out what device is not found.
Click to expand...
Click to collapse
You need to install or update your drivers
sent from my 1920 overclocked note 2 running jedi xp12

[Q] Trying to Root - adb not recognised

Hi,
I'm trying to root but getting the message 'adb not recongised as an internal or external command, operable program or batch file'. What does this mean? I've installed fastboot/flashmode and z3 drivers via flahstool. Am on UK Generic .98 firmware.
Thanks

Ok did some googling and found it was to do with the paths in windows. Updated environmental variables as per the below:
http://www.google.co.uk/url?sa=t&rc...0_IbQh9eEAUHHz45h5DM6_g&bvm=bv.87611401,d.cGU
So in mine, I've got SDK tools saved down in C:\Program Files\Tools and have set up my variable as ANDROID_TOOLS pointing to there, then ANDROID_PLATFORM_TOOLS pointing to their location in C:\Program Files\Platform-Tools and then set Path as %Path%%ANDROID_PLATFORM_TOOLS%;%ANDROID_TOOLS%
But when I run the rooting tool I now get 'The system cannot find the path specified' then *daemon not running. starting it now on port 537* then *daemon started succesfully* it begins sending files and then get several 'cannot stat' and 'unable to open' messages before the final:
'Error: Seems your kernel / device is not supported /system/bin/sh: data/local\tmp\getroot: not found
I am now on Global Generic firmware .23.0.a.2.93. Model is D6603, not locked to any carrier, and bootloader is unlockable.
Can someone please help? I need to get rooted ASAP as I'm home visting family before the weekend and said to my dad I'd root his phone before I head back to London.
Thanks.

Never mind - solved and now rooted! Absolutely no idea how - something within the extracted version of giefroot tool was extracted further to somewhere else, ran the tool again and it worked!

ADB sideload problem connection reset

I have a Pixel presently running NDE63P, not rooted, bootloader locked. I downloaded the NDE63X OTA image, verified the download with the SHA-256 hash, and attempted to put it on the phone. Adb is version 1.0.36 from latest Android Studio. Adb loads the image into memory and then immediately puts out the message "failed to read command: Connection reset by peer", and returns me to the command prompt:
Code:
D:\Users\Nick\Downloads\Google>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
FA69X0309603 device
D:\Users\Nick\Downloads\Google>adb reboot recovery
D:\Users\Nick\Downloads\Google>adb sideload sailfish-ota-nde63x-59a512a1.zip
serving: 'sailfish-ota-nde63x-59a512a1.zip' (~0%) * failed to read command: Connection reset by peer
On the phone screen, I see:
Code:
Finding update package...
Opening update package...
Verifying update package...
and nothing further.
After rebooting both phone and PC I also tried the sideload using an older version of adb from adb-setup-1.4.3.exe. That version doesn't give an error msg about "failed to read command", but it never gets beyond 0% serving of the update, and viewing the adb process in Windows task manager shows it consuming no CPU and performing no I/O (I let it run for about half an hour before killing the process and rebooting the phone). I'm using the USB C<->A cable that came with the phone, and tried it in a couple of different ports in the PC.
Any suggestions on why this problem happens?

Are you placing the update file in the same folder as your ADB location. You might want to consider using a new folder location for the ADB. If you use your downloads location you could possibly use the wrong file while updating since there are so many items typically in that folder. For example I use "Android" folder on my desktop and only keep my SDK, ADB etc. in there so it's always pretty clean and easy to find. You open that folder and shift-right click and open command prompt here or if you've got a Mac it is very similar, cd desktop, cd android.

I think you missed a step
With the device powered on and USB debugging enabled, execute: adb reboot recovery The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the*Power*button and press*Volume Uponce, and a menu will appear. Select the option*Apply update from ADB.
Sent from my Pixel using Tapatalk

jay661972 said:
I think you missed a step
With the device powered on and USB debugging enabled, execute: adb reboot recovery The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the*Power*button and press*Volume Uponce, and a menu will appear. Select the option*Apply update from ADB.
Click to expand...
Click to collapse
No, I did all that, and then selected "Apply update from ADB" before running "adb sideload <image>.zip" on the PC.
In any case, I found a workaround that didn't involve using ADB:
1. Copy the 820Mb NDE63V OTA image file I downloaded from the PC to Android/data/com.google.android.gms/cache on the phone.
2. Check for an update in Settings / About Phone / System updates. The phone found and downloaded a 47Mb update and then applied NDE63V.
About now shows Android security patch level as 5 November 2016 and Build number NDE63V.

NickJHP said:
No, I did all that, and then selected "Apply update from ADB" before running "adb sideload <image>.zip" on the PC.
In any case, I found a workaround that didn't involve using ADB:
1. Copy the 820Mb NDE63V OTA image file I downloaded from the PC to Android/data/com.google.android.gms/cache on the phone.
2. Check for an update in Settings / About Phone / System updates. The phone found and downloaded a 47Mb update and then applied NDE63V.
About now shows Android security patch level as 5 November 2016 and Build number NDE63V.
Click to expand...
Click to collapse
Did not work. Strongly suggests it was just coincidence that you got your OTA prompt after doing the steps.

Not to necro an old thread, but I had a similar issue and came across the solution. If anyone else encounters this problem, try different USB cords and USB ports. Very likely a USB port isn't supplying the proper data transfer.

Having Problems using ADB after a reboot

Hello, I hope that this topic can be opened here, if not please move it or let me know and I will delete it.
In adb I am getting the error "failed to check server version: protocol fault (couldn't read status): No error" and I cannot see my device when I use the command "adb devices". Moreover, it seems like my phone is not letting me authorize my laptop for USB debugging despite trying different options to getting it to work. I have tried different trouble shooting methods that I have found online, but nothing has worked so far. If anyone has any ideas, it would be greatly appreciated.
I am using a POCO F2 Pro that has had its bootloader unlocked and I am running Xiaomi.eu version 12.0.4 (stable) and using a Windows 10 machine to connect with my phone. I did not have much problems with the flashing off TWRP, using ADB commands, or flashing the ROM when I did all of these things last month.
Now, however, I have been having some problems. I believe it started when I tries to update the System FW a few days ago in the phone instead of flashing it manually. Because it was the stable version, and because the option existed in my system settings, I thought that I would be able to update it without going through those steps. The update downloaded and I got the correct file, but when I hit install, I did not get the new FW, despite the phone rebooting. I've been having problems with adb since this time, I believe.

Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.

Saratoga79 said:
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Click to expand...
Click to collapse
Hello, thanks for your reply. I tried that yesterday, but I gave it another try today. This was the error that I received when I ran the command in Powershell:
Program 'adb' failed to run: No application is associated with the specified file for this operationAt line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~.
At line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: ) [], ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed
When I ran the command in Command Prompt, I got the error "failed to read response from server".
Trying to start the server also lead to an error "protocol fault (couldn't read status): No error
---------
Part of my issues may be coming from the fact that I no longer get the authorize USB debugging on my phone, even after I have revoked the authorizations. I've tried different ports, different USB cables, and even factory resetting my phone, to no luck.

Try using the latest platform tools from Google.

batuken said:
Try using the latest platform tools from Google.
Click to expand...
Click to collapse
From what I know, I am using the latest SDK platform tools. I initially downloaded from that site either in late July or early August, and yesterday I deleted the old files and re-installed them from the website. Is there an additional step that I might have missed in removing the old files from my computer?
Additionally, the .android folder in my user profile is now empty (no adb_key file(s) inside).