adb device unauthorized - Nexus 4 General

I noticed a certain feature of a ROM, so I conducted a test on other ROM.
If you execute the command you see on the screen something like this,
Code:
[FONT="Courier New"]P:\>adb devices
List of devices attached
XXXXXXXXXXXXXXXX unauthorized
P:\>adb shell
error: device unauthorized. Please check the confirmation dialog on your device.[/FONT]
you might like to know that ROMs have a similar property.
Code:
[FONT="Fixedsys"]aokp_mako_nougat_nightly_2017-03-15_ota.zip - NOF27B
aoscp_mako-3.6-20170225-official.zip - NMF26X
CARBON-CR-5.1-MOO-WEEKLY-mako-20170107-1159.zip - NMF26V
Cosmic-OS_mako_7.1.1_20170212_1.3-OFFICIAL.zip - NMF26V
crDroidAndroid-7.1.1-20170307-mako-v2.3.zip - NOF26W
lineage-14.1-20170309-nightly-mako-signed.zip - NOF27B
lineage-14.1-20170312-NIGHTLY-MLQ-mako.zip - NOF27B
MK71.1-mako-201703121057-NIGHTLY.zip - NOF27B
omni-7.1.1-20170228-mako-HOMEMADE.zip - N4F26O
RR-N-v5.8.2-20170227-mako-Unofficial.zip - NOF26W[/FONT]
___________________________________________________________________
Below I present a ROM that behave differently, but for me it's good.
Code:
[FONT="Courier New"]P:\>adb devices
List of devices attached
XXXXXXXXXXXXXXXX device
P:\>adb shell
mako:/ #[/FONT]
Code:
[FONT="Fixedsys"]aicp_mako_n-12.1-NIGHTLY-20170312.zip - NOF27B
aosp_mako-ota-eng_V10.zip - NMF26Q
DU_mako_7.1.1_20170310-1645.v11.2-UNOFFICIAL.zip - N6F26U
liquid_mako-20170226-1613-nougat.zip - NOF26W
NeXus4ever_mako-7.1-r02-20161227.zip - NMF26Q
Nitrogen-OS-mako-20170307.zip - N6F26U
purenexus_mako-7.1.1-20170217-HOMEMADE.zip - NOF26W
saosp_mako-ota-3-8-17.zip - N6F26U
Slim-mako-7.1.1.build.0.14-BETA-20170303-0414.zip - NOF26W
ua_mako-7.1.1-20170201.zip - N6F26Q
XenonHD-170215-Official-mako.zip - NMF26V[/FONT]
___________________________________________________________________
I made a test in Windows 8.1 64-bit, USB cable was still connected.
Only a clean installation and activation of debug USB, if it was not set by default in the ROM.

All you have to do is accept the authorization prompt on your phone, and then the "unauthorized" will appear as "device."

TheSt33v said:
All you have to do is accept the authorization prompt on your phone, and then the "unauthorized" will appear as "device."
Click to expand...
Click to collapse
I am glad that there is someone with a Windows 8.1 64-bit! :highfive:
So I would recommend your mind what has been written on this page 3.
---- edit ----
It seems that this feature has long existed.
Can't connect Nexus 4 to adb: unauthorized.
---- edit 2 - solved ----
I still do not know why one ROM works differently from another.
I have found a solution that points to the cause on the windows side that produces this effect.
Cant connect to Android phone using adb (adb device unauthorized)
I had something like this:
Code:
[HKEY_CURRENT_USER\Environment]
"ANDROID_SDK_HOME"="C:\Android"
but there was no c:\android directory on my hard drive.
After removing the environment variable and restarting the system, there is no longer "unauthorized" on some ROMs.

Related

"Unable to open sync connection" from a virtual machine

I'm trying to upload an APK with ADB+Eclipse into a (real device) HTC Legend from a virtual machine with XP Pro guested on a real machine with Win7 x64.
I installed USB Driver, modified it to support HTC Legend, then set HTC Legend with USB Debug... in VM XP Pro I see into ADB the HTC Legend connected (I think so...)
Code:
C:\android\android-sdk-windows\tools>adb devices
List of devices attached
HT03SNX02682 device
I think that HT03SNX02682 is the serial number that ADB give to my device, correct?
Then I try to upload from Eclipse using run configuration of Eclipse...
but this is the log...
Code:
[2010-06-14 13:02:23 - HelloWorld21] ------------------------------
[2010-06-14 13:02:23 - HelloWorld21] Android Launch!
[2010-06-14 13:02:23 - HelloWorld21] adb is running normally.
[2010-06-14 13:02:23 - HelloWorld21] Performing android.helloworldapp21.HelloWorld21 activity launch
[2010-06-14 13:03:15 - HelloWorld21] WARNING: Application does not specify an API level requirement!
[2010-06-14 13:03:15 - HelloWorld21] Device API version is 7 (Android 2.1)
[2010-06-14 13:03:15 - HelloWorld21] Uploading HelloWorld21.apk onto device 'HT03SNX02682'
[2010-06-14 13:03:21 - HelloWorld21] Failed to upload HelloWorld21.apk on device 'HT03SNX02682'
[2010-06-14 13:03:21 - HelloWorld21] java.io.IOException: Unable to open sync connection!
[2010-06-14 13:03:21 - HelloWorld21] Launch canceled!
if I try to install from prompt dos with adb install... the process doesn't stop (stall?).
I tryed also to see logcat but seems doesn't log nothing... (I'm newbie in android dev)
thank in advance for your help
I had the same problem, even if with my emulator.
Occasionally, the Device view in the Eclipse DDMS would list many copies of the device, all of them Offline, and I wouldn't be able to run anything on the device if I tried to plug it back in.
What seems to fix this is running
adb kill-server
from the command line. It cleans up the list of Offline devices and allows me to run applications on the device again.
Hope it works,

[GUIDE] How to transfer files in Linux

Now works on 32bit and 64bit Linux
Just a quick guide on how to configure Linux for file transfers using MTP. I wrote the instructions and config for Ubuntu Natty 32bit and 64bit, though the same process will work on other platforms - the only real difference being the package manager commands and possibly the config file locations.
The attached files are for the Galaxy Tab 10.1v but should work for the 10.1g / 10.1 as well. See the end of the post to learn how to modify this config to work for other devices.
How to configure for gMTP and other Media Sync tools
1) Install aptitude
Code:
sudo apt-get install aptitude
2) Install mtp-tools and mtpfs
Code:
sudo aptitude install mtpfs mtp-tools
3) Download the attached file ( View attachment 98-gtab.zip for 32bit Linux or View attachment 98-gtab.rules-AMD64.zip for 64bit Linux ) to your desktop.
4) Extract the 98-gtab.rules file to your desktop
5) Copy the rules file to /etc/udev/rules.d/
Code:
sudo cp ~/Desktop/98-gtab.rules /etc/udev/rules.d
6) Reboot
7) Connect your Tab
8) Run the following command to confirm it is working:
Code:
ls /dev | grep gtab
...which should return "gtab" if successful. If not, follow the "Modifying" guide below.
9) Download / install gMTP
Code:
sudo apt-get install gmtp
10) Open gMTP and select "connect" from the menu
11) Hit the thanks button
12) Go nuts!
Setting up for Automount (Optional, but recommended)
***You must have completed Steps 1-8 above before proceeding***
1) Edit your fstab file to add your gtab:
Code:
sudo gedit /etc/fstab
2) Add this to the end of the file:
Code:
#gtab
mtpfs /media/gtab fuse user,noauto,allow_other 0 0
3) Save and exit
4) Open fuse.conf for editing:
Code:
sudo gedit /etc/fuse.conf
5) Find the following line and remove the #
Code:
#user_allow_other
6) Save and exit
7) Open and edit the groups file:
Code:
sudo gedit /etc/group
8) Find the details for the group 'fuse' and append your username to the end of the line eg.
Code:
fuse:x:104:<YOUR USER NAME>
9) Save and exit
10) Create the folder to mount your Tab:
Code:
sudo mkdir /media/gtab
11) Take ownership of the folder:
Code:
sudo chown <YOUR USER NAME>:users /media/gtab
12) Reboot
13) Plug in your Tab.
14) Click on the Places menu and click gtab.
15) You're in business!
Modifying for other devices
If the above doesn't work immediately on the 10.1g / 10.1 (I have only tested on the 10.1v), you can easily edit the rules file to support your device.
1) Install lsusb
Code:
sudo apt-get install lsusb
2) Run lsusb
Code:
lsusb
3) Check the output of this command to find your device. The 10.1v is shown like this:
Code:
Bus 001 Device 010: ID 04e8:6860 Samsung Electronics Co., Ltd
4) Make a note of the Vendor and Product IDs. In the example above, the vendor ID is 04e8 and device ID is 6860 (note 04e8:6860 in the output).
5) Open the rules file for editing (if it's not already in /etc/udev/rules.d, copy it there now)
Code:
sudo gedit /etc/udev/rules.d/98-gtab.rules
6) Find this line:
Code:
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6860", MODE="0666" SYMLINK+="gtab"
7) Replace the Vendor ID (04e8) and Product ID (6860) with the ones that you got from step 3 above.
8) Save and exit
9) Reboot
10) Follow step 7 onward in the first guide above
11) Hit the thanks button
If you modify it for a particular device, please post the contents of your new 'rules' file here.
32bit RULES FILE:
Code:
ACTION!="add", GOTO="gtab_rules_end"
SUBSYSTEM!="usb|usb_device", GOTO="gtab_usb_end"
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6860", MODE="0666" SYMLINK+="gtab"
LABEL="gtab_usb_end"
LABEL="gtab_rules_end"
64bit RULES FILE:
Code:
ACTION!="add", GOTO="gtab_rules_end"
SUBSYSTEM!="usb|usb_device", GOTO="gtab_usb_end"
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6860", MODE="0777" SYMLINK+="gtab"
LABEL="gtab_usb_end"
LABEL="gtab_rules_end"
Tested, walked through the steps to my friend (Skype ). Works 100% on Linux Mint too
Everything worked for me up to the GMTP part - I can grep through /dev and I can see the "gtab" device there. But GMTP insists "Detect: No raw devices found."
I'm still running Maverick, but I added the maverick-backports repo, which has gmtp, so I would think it would work.
This is a Samsung Galaxy Tab 10.1v (from Google I/O). Any ideas?
EDIT: I also tried the automounting option with FUSE. Attempts to cd into it with bash or open it from the Places menu in GNOME both give the message "Transport endpoint is not connected".
EDIT again:
OK, I disabled USB Debugging and now have a different set of problems. mtp-detect sees the device now, but the message upon running it is:
Code:
libmtp version: 1.0.3
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
04e8:6860 @ bus 2, dev 26
Attempting to connect device(s)
ignoring usb_claim_interface = -16ignoring usb_claim_interface = -22PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Device or resource busy
outep: usb_get_endpoint_status(): Device or resource busy
usb_clear_halt() on IN endpoint: Device or resource busy
usb_clear_halt() on OUT endpoint: Device or resource busy
usb_clear_halt() on INTERRUPT endpoint: Device or resource busy
LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
Konklone said:
Everything worked for me up to the GMTP part - I can grep through /dev and I can see the "gtab" device there. But GMTP insists "Detect: No raw devices found."
I'm still running Maverick, but I added the maverick-backports repo, which has gmtp, so I would think it would work.
This is a Samsung Galaxy Tab 10.1v (from Google I/O). Any ideas?
EDIT: I also tried the automounting option with FUSE. Attempts to cd into it with bash or open it from the Places menu in GNOME both give the message "Transport endpoint is not connected".
Click to expand...
Click to collapse
Can you post the output from 'lsusb' ?
re the "Transport endpoint is not connected" - I just got this same error on 64bit Natty. Will try and see if I can find out why..
Ah, just saw your reply. I edited my post up above, but the gist is - you can't do this while USB Debugging is enabled. The Tab has to be running its "MTP Application".
Now I'm getting the stranger errors above. I'm going to try mounting it with FUSE now to see if that helps for some reason.
EDIT: For the record, I'm using the correct vendor and product IDs in my rules file:
Code:
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6860", MODE="0666" SYMLINK+="gtab"
Konklone said:
I edited my post up above, but the gist is - you can't do this while USB Debugging is enabled.
Click to expand...
Click to collapse
You may be right. When I wrote this guide, I was using a VM. It is possible that the fact that I was using both MTP and ADB at the same time has something to do with how VMWare presents the devices to the guest OS.
Now I am using 'bare metal' Natty 64 bit and have the same problem as you.
I have to go out for a while but will look at it again when I get back.
EDIT: Just tried mtp-detect and it is finding the device. I suspect USB Debug is not the issue, but I'll leave it in your capable hands - really got to go now
EDIT2: See here http://www.usb.org/developers/devclass_docs/MTP_1.0.zip OK - Im really REALLY going now. Back online in a few hours
I couldn't get anywhere until I turned off USB debugging. When USB debugging is enabled, I *can* use adb to get into the shell, see files, install apps, etc. I can even transfer files over adb, through the command line! Can you get MTP to detect it with USB debugging enabled?
With USB debugging off, I have once in a great while (only twice in all my attempts) while gotten mtp-detect to connect to the device and print sane output describing the device. Even when those happened, running the command immediately again didn't connect correctly, and gave me the same error messages I was getting before. Both times I got it to connect, it was soon after plugging in the cable, but it doesn't happen every time.
Intermittent heisenbugs are the worst, yet I don't think I have a busted cable, given that adb works perfectly consistently.
Maybe I should try this again after updating to Natty...I'd been meaning to do it anyhow...
EDIT: One thing I notice is that on the Tab, when the "MTP Application" is running after plugging in, the 5-dot "in progress" animation is extremely choppy, as if the device were very very busy. If the device were very very busy for some reason, this could explain why a successful connection can happen only once in a great while. I'll try rebooting the device, I guess.
EDIT2: I rebooted the device, and I removed the USB extension cord I was using, but neither helped, still getting the same intermittent success. (I got mtp-detect to connect to it a few more times - all soon after plugging in the cable, and none were repeatable without unplugging and replugging it in.) The animation actually wasn't choppy before, that's just how it looks - 5 discrete animation frames, one for each dot.
Something interesting though: this time I had the Tab resting on my knee, and I felt a haptic buzz after running mtp-detect on one occasion. I looked down and saw the MTP Application restart itself. Then I ran mtp-detect again and I felt 3 haptic buzzes in quick succession, followed by a successful detection and output. But when running mtp-detect *again*, no dice.
This is messed up.
Messed up indeed.
Konklone said:
Can you get MTP to detect it with USB debugging enabled?
Click to expand...
Click to collapse
Yes, both work simultaneously on 32bit Natty
Note that you have to unmount the gtab for mtp-detect to work. I compared the output from mtp-detect on the 32bit working VM and the 64bit non-working 'bare metal' machine and the output was identical. I suspect this means that mtpfs is not where the problem is
Re the strange problem with haptic feedback - I have had mine power off all by itself when testing some different parameters in the rules file.
[64bit working]
OK. Problem solved... kind of. There seems to be some kind of bug in fuse which requires the filesystem to mount with higher permissions to run properly (at least on Natty AMD64)
If you use the new 64bit rules file I have attached, it should work. Basically it uses 777 permissions instead of 666. Not great, but working nonetheless.
New rules file for 64bit:
Code:
ACTION!="add", GOTO="gtab_rules_end"
SUBSYSTEM!="usb|usb_device", GOTO="gtab_usb_end"
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6860", MODE="0777" SYMLINK+="gtab"
LABEL="gtab_usb_end"
LABEL="gtab_rules_end"
EDIT: If someone wants to experiment with lesser permissions and see what the minimum is and post back, that would be helpful for all.
Sigh, thank you for taking so much time to help me so far, but I wonder if I'm a lost cause.
I spent a bunch of today finishing my upgrade to Natty, including a full wipe and reinstall. (I have a 32-bit machine, btw.) Now I can't even get it to detect my MTP device at all (mtp-detect says "No raw devices found."), with or without debugging enabled.
One possibly important topic - it's really surprising to me that yours works either way, because lsusb shows that a different product ID is exposed to the host, depending on whether debugging is on or not. With debugging disabled, it's 6860, like your example. With debugging enabled, it's 685e. When I run lsusb, only one of those will show up, never both. So if yours is the same device, I have no idea how your rules file could be agnostic to debugging being enabled. If yours is not, then that might explain our different experiences.
Anyway, I've Thanks'd all your posts in this thread, solved or not. I appreciate your help.
Konklone said:
With debugging enabled, it's 685e. When I run lsusb, only one of those will show up, never both
Click to expand...
Click to collapse
You're more than welcome.
I noticed that in Windows, both devices appear in device manager. That is a very strange problem you have discovered.
I just posted instructions and files to give you root access! Might take your mind off the MTP issues for a while
Who knows... the problem might just go away
Konklone said:
One possibly important topic - it's really surprising to me that yours works either way, because lsusb shows that a different product ID is exposed to the host, depending on whether debugging is on or not. With debugging disabled, it's 6860, like your example. With debugging enabled, it's 685e. help.
Click to expand...
Click to collapse
Are you sure? On my device its the other way around. Without debugging its 685e and with debugging its 6860?
ajvogel said:
Are you sure? On my device its the other way around. Without debugging its 685e and with debugging its 6860?
Click to expand...
Click to collapse
Ok I got it working on my device, I switched on usb debugging in settings. lsusb now returns 6860 and I am able to mount the galaxy tab using the process outlined above.
This is craziness. Is my Galaxy Tab a rare mutant piece of hardware who had its USB numbers switched?
Also - I noticed that Ubuntu somehow automounts my tablet and can read/write to its disk, through a Nautilus plugin. But I still get nothing with mtp-detect. I don't understand how the world works.
I've also got an I/O tablet (updated to 3.1) and I followed this tutorial, so thanks for the help you provided! I managed to copy some files to the device but it ended up freezing my computer (running Ubuntu 10.10).
So I unplugged the tablet, and saw that effectively those few pictures and pdf files had been copied to the device successfully. Pictures are in the Gallery, pdf can be read with Aldiko... but the funny thing is that when I mounted again the tablet -using Ubuntu again- it shows all folders as empty!
That is, 0 files in all tablet folders.
I tried "showing all hidden files" with Nautilus. No luck, nothing is shown. Went to the folder using command line, did an ls -la (just in case who knows! maybe it would show something!). No luck either, directories are apparently empty and have "1 January 1970" as modification date... if it helps.
I can see the files inside the folders using ADB but it's obviously not ideal, specially compared with simply using Nautilus.
Does it happen to you too?
Anyone get this working? I'm having the same exact issues as Konklone. I'm on Maverick and tried the different udev rules and it still doesn't work. I'm gonna be pissed if I have to buy the stupid Samsung USB adapter just to get USB mass storage.
[ASK]Noobs need solution
gMTP tells me that there is no device. Any ideas?
I'm having the same issue. First try I was able to plug in and mount to my netbook. Tried to plug into my mac and it didn't work. Hasn't worked since then, i'm considering doing a factory reset.
I'm running Ubuntu 10.10 64-bit. Note that you do have to enable backports to install gmtp.
Edit /etc/apt/sources.list, uncomment the lines with:
Code:
deb (http-url) maverick-backports main restricted universe multiverse
deb-src (http-url) maverick-backports main restricted universe multiverse
Run
Code:
sudo apt-get update && sudo apt-get install gmtp
I had to unplug the device and replug it back in a couple of times before gmtp would connect to it properly. It seems to be pretty flaky.
Wow...........
This is nonsense ..... is there a way to enable USB Mass Storage or are we completely hosed with MTP?

[Q] Kindle Fire HD bricked.

I read up on guides to fixing it, ordered a fastboot cable.
Back story: I stupidly wiped my entire KFHD, OS and all
Still can access TWRP, my question is, can it be fixed? Can i just plug my fastboot cable in and transfer CyanogenMod 10.1 and flash it?
Thank you for you help.
I think i can help you a little bit , did you try the adb sideload option?
if not , the only thing you need to do its send the .zip file via adb sideload and you are done
Use the factory/fastboot cable only to get into fastboot, but don't use it to enter commands or transfer files. Switch cables and use adb to transfer a new ROM to your sdcard
ThatLatinGuy said:
I think i can help you a little bit , did you try the adb sideload option?
if not , the only thing you need to do its send the .zip file via adb sideload and you are done
Click to expand...
Click to collapse
no. my kindle is wiped and I cannot connect it to my pc. It's detected but I can't find the empty folder to put stuff in
EDIT: Googled adb sideload and tried it out, my kindle isn't detected when i use the adb devices command. That's probably why it isn't working.
EDIT2: Fixed, many thanks to ThatLatinGuy.
RaptorYeshua said:
no. my kindle is wiped and I cannot connect it to my pc. It's detected but I can't find the empty folder to put stuff in
EDIT: Googled adb sideload and tried it out, my kindle isn't detected when i use the adb devices command. That's probably why it isn't working.
EDIT2: Fixed, many thanks to ThatLatinGuy.
Click to expand...
Click to collapse
You are welcome , and if you need something else just tell me
Can You Help Me?
I have a similar issue. It looks like the OS has been wiped from my Kindle Fire HD 7. My PC does detect it and I can see folders. They are empty, mostly. On start up I get "Kindle Fire". Then I get to a welcome screen with an android icon. I press start and it sits for a bit then a window pops up saying that there was an error. My PC does not detect my Kindle as ADB and it will not boot up in fastboot.
Rednival said:
I have a similar issue. It looks like the OS has been wiped from my Kindle Fire HD 7. My PC does detect it and I can see folders. They are empty, mostly. On start up I get "Kindle Fire". Then I get to a welcome screen with an android icon. I press start and it sits for a bit then a window pops up saying that there was an error. My PC does not detect my Kindle as ADB and it will not boot up in fastboot.
Click to expand...
Click to collapse
I think we need a little more information.
1. What were you trying to do when the OS disappeared?
2. Do you have a fastboot cable?
3. Did you back-up your Kindle stock images?
4. What do you want to achieve at the end? Stock OS or modified OS or what?
Did you follow the instructions for putting the kindle into ADB mode before the OS disappeared?
calkenneth said:
I think we need a little more information.
1. What were you trying to do when the OS disappeared?
2. Do you have a fastboot cable?
3. Did you back-up your Kindle stock images?
4. What do you want to achieve at the end? Stock OS or modified OS or what?
Did you follow the instructions for putting the kindle into ADB mode before the OS disappeared?
Click to expand...
Click to collapse
as calkenneth said we need more details if you want help , tell us what happened and who did you get wipe your os , then i will do my best to help you
Hi, I have a similar problem and was not sure whether to start a new thread or not.
I had tried rooting the 7HD and it only kind of worked.
It is still working for some things but not Netflix and Amazon video streaming so I would like to go back to the stock ROM. I have tried everything I have found online, and nothing is working. Unfortunately, the root I used did not include adding TWRP.
I just tried adb sideload as mentioned above but the instructions call for v1.0.029 or later and mine is 1.0.026 and I can't find a download link to that later version.
I have a fastboot cable and after four or five tries starting the 7hd, it will boot and stop at the Fatsboot but I can't do anything with it as it appears locked up.
With the standard cable I can see the Kindle on my win7pro-x64.
I have Superuser showing on the 7hd carousel.
When I plug the 7hd in, windows tries to install the drivers and then says, "drivers were not installed correctly. The Device Manager shows Kindle under "Other devices" but it has a yellow question mark.
...and when I run abd shell, it gets started OK, but hen says "Device not found," even though I can see the Folders with Windows Explorer.
Thanks for anything you can offer to get this unrooted.
Harry
I have the exact same problem as the OP, I tried sideloading but all I get is a bunch of gibberish adb related in the cmd window whenever I enter anything, i.e. adb push, adb device, adb sideload same stuff comes up in the cmd window but nothing is sideloaded onto the device. What am I doing wrong ? I was attempting to install paranoid android port, was wiping everything and in my eagerness I wiped the system/OS, can still enter twrp.... a bit of help would be appreciated!
CreamEggKing said:
I have the exact same problem as the OP, I tried sideloading but all I get is a bunch of gibberish adb related in the cmd window whenever I enter anything, i.e. adb push, adb device, adb sideload same stuff comes up in the cmd window but nothing is sideloaded onto the device. What am I doing wrong ? I was attempting to install paranoid android port, was wiping everything and in my eagerness I wiped the system/OS, can still enter twrp.... a bit of help would be appreciated!
Click to expand...
Click to collapse
It would he helpful to know exactly what messages you are receiving...
soupmagnet said:
It would he helpful to know exactly what messages you are receiving...
Click to expand...
Click to collapse
this is the message I recieve, a bunch of commands and explanation as to what adb commands do. :good:
I think either my xda app is glitching or that photo got resized so small the text is unreadable. But I am throwing a guess that the command syntax was wrong so adb threw up its default usage text. BTW here's a tip, instead of screen-shotting your PC, right click in the command prompt and press mark, it will let u highlight the text, when done highlighting, tap enter on the keyboard to copy, then you can paste the text here, preferably in code brackets if there is a lot. I find it funny most people don't know this considering how often most people use copy and paste now days, then again Microsoft didn't exactly label it very well. What exactly did you type into the command prompt?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I think either my xda app is glitching or that photo got resized so small the text is unreadable. But I am throwing a guess that the command syntax was wrong so adb threw up its default usage text. BTW here's a tip, instead of screen-shotting your PC, right click in the command prompt and press mark, it will let u highlight the text, when done highlighting, tap enter on the keyboard to copy, then you can paste the text here, preferably in code brackets if there is a lot. I find it funny most people don't know this considering how often most people use copy and paste now days, then again Microsoft didn't exactly label it very well. What exactly did you type into the command prompt?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
the pic came up small because it is a thumbnail to the larger pic which is in photobucket, didnt want to flood he page with an overly large photo, thanks for the pro tip! didn't know that but it shall come in handy in future.
I typed in adb sideload /pa_tate-3.90-20130801.zip and then got the following:
hope it helps! yes I'm aware my first name is in there, not bothered! )
C:\Users\Wil>adb sideload pa_tate-3.90-20130801.zip
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
Click to expand...
Click to collapse
do I need to provide more detail ? because I'm pretty sure everything you need to know is right there. The OP solved his issue, would of been helpful if he said how?
Everything we need is right there, I'm trying to figure out why its doing that be cause the syntax looks correct to me. I'll do some checking on mine, have to ask, u did put the file your trying to side load in the same folder as the adb command right?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Everything we need is right there, I'm trying to figure out why its doing that be cause the syntax looks correct to me. I'll do some checking on mine, have to ask, u did put the file your trying to side load in the same folder as the adb command right?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
doh!
Its always the simple things we forget to do! Will try it in the morning and let you know! Cheers bub.
I placed the file in the android sdk folder at C:/Android SDK still no joy, keep getting the same message pop up..... is there a specific folder within android sdk it needs to be in ? build tools ? temp ? platform-tools ?
On a side not Amazon has agreed to send me another one. Theyve asked that I return this one after I get the new one, question, would they be bothered if I didn't ? Or would they try to charge me for the price of a second one ? latter option seems more likely imho...
The adb command I believe is in the platform tools folder, put it in there and try it. Also just call amazon and ask them to cancel it and tell them you got it working, I doubt there would be any problems.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
yeah I figured it was the platform tools folder, still nothing, I have tried various syntax entries followed the guidelines laid out by twrp for sideloading, still no joy, same bunch of adb commands are displayed after enter.... I do not know what I am doing wrong, this is not my first time working adb or with rooted devices.....

Device Offline Error on HTC One

Okay, I am trying to run the firewater script in order to get S-OFF. But I have run into the "device offline" error when I try to connect my Mac to my HTC One. I understand from reading why I am getting the error, and that it is due to a new "feature" of Android 4.2.2+ which gives us secure usb debugging.
Here is the rub, though: When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’.
But that is not what is happening! Whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization. The trick, according to this thread [http://forum.xda-developers.com/member.php?u=4159439] would seem to be to remove the
adb key from the device, so as to trigger the confirmation window to allow USB debugging. But I can not find the location of this file on my HTC One, so I have no way to remove it.
Please tell me where this file is located if you know it. I have ES File Explorer installed on my rooted HTC One, Dev. Edition, running Android 4.4.2. but that path nets me an empty folder.
Thank you for any and all assistance that you provide.
SOLUTION FOUND! - See my reply below.
Okay, typed into terminal:
cd Android/HTCOneRoot
./adb-mac version (This command gives the version of ADB that the Mac is using.)
Android Debug Bridge version 1.0.29 (Terminal returns this answer; ADB needs to be at least version 10.3.1 to properly work and fix the "device offline" error.)
Here are the steps I then followed to fix problem:
1. I unplugged my HTC One from the computer.
2. Downloaded and installed Android Studio from the Android Developers’ site into my Applications folder
3 Updated my Platform Tools, as follows:
Control-clicked on the Android Studio Application and selected “Show Package Contents” from the pulldown menu.
Followed this path to the platform tools: Android Studio/sdk folder/platform-tools folder/adb & fastboot
Option copied both adb and fastboot from platform tools to my user directory ~/Android/HTCOneRoot.
Closed Android Studio
4. Restarted the computer.
5. Launched Terminal and typed cd Android/HTCOneRoot( my user directory where my adb and fastboot are stored)
6. Typed into my terminal the command, “./adb version”
Following this command prompt, Terminal responded with “Android Debug Bridge version 1.0..3.1. (Yes!!)
7. Typed into Terminal, ./adb devices
My device did not show up right away!
8. So, I unplugged my device. Shut down my Mac and restarted it.
9. Relaunched Terminal and typed cd Android/HTCOneRoot
10. Typed ./adb kill-server
11. Then typed, .adb start-server
Terminal responded with: daemon not running. starting it now on port 5037 *
daemon started successfully *
12. Plugged in device again, and the device dialog about RSA appeared. (Whew!)
13. Clicked “OK” on the dialogue box.
14. Now typed ./adb devices and my device's serial number shows up, followed by the word "device" (not "device offline")
14 All done! No more device offline errors.
Hey all,
Has anyone a guide on how to update ADB version for Windows?
I am using unrooted HTC One (UK) on v 4.3
RickCov said:
Hey all,
Has anyone a guide on how to update ADB version for Windows?
I am using unrooted HTC One (UK) on v 4.3
Click to expand...
Click to collapse
mini-sdk-1.0.31-windows.rar
download and extract to a folder of your choice, that's all.
let me also add that post the described method - ./adb devices command came up with the device and serial, but unauthorized.
With the phone connected via usb I went to Dev. Options, unchecked USB Debugging then rechecked it, instantly the confirmation dialog box came up regarding the RSA Key for my laptop. Check the box so it remembers your computer and hit save.
I was having the exact issue described by OP and simply by getting the newest version of ADB and unchecking and rechecking debugging I got the authorization. Thanks all who offered suggested and posted links to files.
and this helped as well
metropical said:
let me also add that post the described method - ./adb devices command came up with the device and serial, but unauthorized.
With the phone connected via usb I went to Dev. Options, unchecked USB Debugging then rechecked it, instantly the confirmation dialog box came up regarding the RSA Key for my laptop. Check the box so it remembers your computer and hit save.
Click to expand...
Click to collapse
http://goo.gl/WyyzhX

[how to]remove your "tampered" banner

*this thread is for desire 510 it will NOT work on m7(or anything older). search your device general forum for a specific thread
if you have recently s-off'ed using an exploit that did not remove your tampered banner from the bootloader screen,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:
i have tested this my cricket desire 510 variant(a11_ul),but use this info at your own risk. if it melts your phone into a little pile of plastic 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.
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/mmcblk0p6 bs=1 seek=5314564
(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 tamered is gone
other useful threads:
lock/unlock without htcdev: http://forum.xda-developers.com/desire-510/general/how-to-lock-unlock-bootloader-htcdevs-t3179874
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 p6.
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 p6 by:
adb shell
su (if needed to get a #)
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6
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.
one more
scotty1223 said:
one more
Click to expand...
Click to collapse
btw.32bit Desire 510 Cricket support WCDMA?
bl4ckluna said:
btw.32bit Desire 510 Cricket support WCDMA?
Click to expand...
Click to collapse
Yes
Sent from my HUAWEI ALE-L04 using Tapatalk
find Problem....that device only Support WCDMA USA Band....not support ASIA (
Correct me, please.
Correct me if I'm wrong, please! But isn't the only way, currently, to get S-off for our phone, is to pay $25 when using Sunshine?
JimFritzMI said:
Correct me if I'm wrong, please! But isn't the only way, currently, to get S-off for our phone, is to pay $25 when using Sunshine?
Click to expand...
Click to collapse
Sunshine is one way to skin the cat. I am Not sure if there are others
Sent from my HUAWEI ALE-L04 using Tapatalk
That seems like an elusive answer...
scotty1223 said:
Sunshine is one way to skin the cat. I am Not sure if there are others
Sent from my HUAWEI ALE-L04 using Tapatalk
Click to expand...
Click to collapse
Almost as if there were other ways...
I seriously considered paying for it to be done, when I first started. However, I can't seem to find a reason to do so.
this is great. but how do you get S-OFF on the desire 510.
also if you get S-OFF won't that void the warranty anyway?

Categories

Resources