Getting "device offline" with adb after 4.4 OTA - Moto X Q&A

This is just weird. I went back to stock to get the 4.4 OTA. Done, now I want to reinstall TWRP and I'm getting the device offline error. Debugging is on, drivers are installed . . . what stupid mistake have I made?
OK - oddly, I reinstalled the sdk and it works. Who knows?

robsw said:
This is just weird. I went back to stock to get the 4.4 OTA. Done, now I want to reinstall TWRP and I'm getting the device offline error. Debugging is on, drivers are installed . . . what stupid mistake have I made?
OK - oddly, I reinstalled the sdk and it works. Who knows?
Click to expand...
Click to collapse
I'm having the same issue, but reinstalling the sdk didnt help.... im lost, i really want this root

robsw said:
This is just weird. I went back to stock to get the 4.4 OTA. Done, now I want to reinstall TWRP and I'm getting the device offline error. Debugging is on, drivers are installed . . . what stupid mistake have I made?
OK - oddly, I reinstalled the sdk and it works. Who knows?
Click to expand...
Click to collapse
nickfromfresno said:
I'm having the same issue, but reinstalling the sdk didnt help.... im lost, i really want this root
Click to expand...
Click to collapse
try turning off/on usb debuggin.. also try revoking the usb debug auths.. check your adb version to be 1.3x..those should fix it

kreegaa said:
try turning off/on usb debuggin.. also try revoking the usb debug auths.. check your adb version to be 1.3x..those should fix it
Click to expand...
Click to collapse
I have this same issue. Device shows up in "adb devices" but, shows to be "offline."
I'm running Windows8, adb version 1.0.29, with an MotoX (ATT). I cd to "platform-tools" to run adb.
---------------------------
Ok, I solved it by locating the 1.0.31 adb files here: http://forum.xda-developers.com/attachment.php?attachmentid=1724500&d=1360704125
I unzipped and replaced the adb files in the "platform-tools" folder with the ones from the above link. My issue was that the older adb files weren't causing the MotoX to prompt me to verify access from my computer. Updated adb files caused the prompt. Once, I verified my computer access - all is good!

shaneaus said:
I have this same issue. Device shows up in "adb devices" but, shows to be "offline."
I'm running Windows8, adb version 1.0.29, with an MotoX (ATT). I cd to "platform-tools" to run adb.
Any suggestions?
Click to expand...
Click to collapse
You need adb version 1.0.32 or above. I had the same problem.

m0biusace said:
You need adb version 1.0.32 or above. I had the same problem.
Click to expand...
Click to collapse
in linux this can be a sign that you need to run ADB as SUDO.

nickfromfresno said:
I'm having the same issue, but reinstalling the sdk didnt help.... im lost, i really want this root
Click to expand...
Click to collapse
There are a couple other things to try.
One, just get the latest ADB platform tools and see if your device shows up online using that adb.
The other thing would be to delete the adb keys on your phone. Remove /data/misc/adb/adb_keys.

Related

Getting Nexus One ADB/USB Mount working (Driver)

Download This file and extract.
hit Windows Key + r
Type in devmgmt.msc
right click on nexus one
click update
update from location on computer.
select that folder.
---------------Notes-------------
Be sure to enable debugging on your phone via Settings>Applications>Devlopment>USB debugging.
Confirmed working on:
Win 7 Ultimate x64/x86
Win 7 Home Edition x86?
Win Vista
XP Home x86
XP Pro x64/x86
O.S
What O.S you had this working on?
@th3fallen
143!!
I got it working on win7 Ultimate version
This works for Windows 7 Home Premium Edition as well.
In order to get ADB working on Linux (Ubuntu 9.04) I had to edit /etc/udev/rules.d/51-android.rules (I may have created this file for the G1) and add:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
What I was seeing was the device would sort of show up when I ran adb devices, but it would list ????????? as the ID and no permissions.
~Kenny
I was able to access it by using dream, magic and adb testing device didnt need any specific driver.
I did this to get it working on win 7 ultimate x64
NexVision said:
I was able to access it by using dream, magic and adb testing device didnt need any specific driver.
Click to expand...
Click to collapse
You need the latest refresh of the drivers (and tools for updated fastboot, etc.) from the SDK. If you go to a Windows command prompt and run Android, assuming the tools directory is in your path, you can select the update for both. It will fail in updating tools, since you are using an app in it, but don't close the app, just reapply at that point and it will work on the second go. Then when you install the N1, you will have the drivers you need to install as before.
Not meaning to argue with you but what I was saying is I have had no issues doing anything via adb with it as a magic I have done fastboot as well hey maybe its just working for me.
kfk2 said:
In order to get ADB working on Linux (Ubuntu 9.04) I had to edit /etc/udev/rules.d/51-android-rules (I may have created this file for the G1) and add:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
What I was seeing was the device would sort of show up when I ran adb devices, but it would list ????????? as the ID and no permissions.
~Kenny
Click to expand...
Click to collapse
Hmm...I have that already in my /etc/udev/rules.d/51-android.rules (mine has .rules, not -rules...I'm assuming that's a typo in your post?) and I'm still coming up with ?????????? as the device and no permissions, all attempts to do anything with adb result in it telling me I don't have permission to do these things.
Swervo said:
Hmm...I have that already in my /etc/udev/rules.d/51-android.rules (mine has .rules, not -rules...I'm assuming that's a typo in your post?) and I'm still coming up with ?????????? as the device and no permissions, all attempts to do anything with adb result in it telling me I don't have permission to do these things.
Click to expand...
Click to collapse
Yah that was a typo.. The no permissions error appears to me that adb doesn't have access to the /dev/ devices used. I'm not at home so I cannot lookup what device is created and used in /dev/ for you to check the permissions. I know I killed the adb server and restarted it a few times while trying to get mine to work, along with updating to the latest sdk. So you may want to try those things, you could also try running adb as root and seeing if that fixes it (if so, then it's a simple permission error with udev not creating it with correct permissions).
Alrighty, I think I got it. I'm no udev expert (in fact, I'm rather useless at it), but this worked for me.
1) Make sure USB debugging is turned on on the phone.
2) Plug the phone into the USB port on the machine.
3) Make sure /etc/udev/51-android.rules has
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Click to expand...
Click to collapse
in it.
4) run
adb kill-server
Click to expand...
Click to collapse
5) As root, run
service udev restart
Click to expand...
Click to collapse
6) run
adb start-server
Click to expand...
Click to collapse
Worked for me to get the device recognized.
Hey guys, I have the Android 1.5 SDK/ADB installed on my computer.. so I don't know what will happen when I mount my N1 (haven't tried yet). I want to be able to mount my N1 normally without ADB or anything, 'cause I'm not going to root it for a while. Thanks!
Confirmed on Vista
I can confirm that the instructions in the OP work on Vista. Thanks a lot, th3fallen.
Alleviate said:
Hey guys, I have the Android 1.5 SDK/ADB installed on my computer.. so I don't know what will happen when I mount my N1 (haven't tried yet). I want to be able to mount my N1 normally without ADB or anything, 'cause I'm not going to root it for a while. Thanks!
Click to expand...
Click to collapse
Nothing will happen, ADB doesn't start interacting with your phone without you explicitly telling it to. Also, if you don't have debugging turned on on your phone, then it won't even if you do explicitly tell it to. Feel free to mount the drive on it.
ADB and Root
Maybe I'm doing something wrong, but I can't get ADB to recognize my phone. ADB is all set up correctly, I have it updated (I believe) to the most recent version. I installed the updated USB driver and I see the "Android Phone" in my device manager. I have USB Debugging checked off in my phone settings. ADB worked fine for my G1, but it doesn't recognize my Nexus One.
I shouldn't have to root the phone to have ADB working should I? Can anybody think of something I overlooked? I am running Windows XP Professional SP3
Okay, so I navigated to the "1.1-nexusone-superboot" folder in the command prompt and tried
Code:
adb-windows devices
and my device showed up. Now I want to move those files to where I originally had my adb files in C:\android-sdk-windows\tools so that all I have to type is
Code:
adb devices
to have my phone listed. I tried replacing the files in my \tools folder and renaming them to what they were named before, but that didn't work. Could somebody please help me get this set up properly?
ccunningham83 said:
Okay, so I navigated to the "1.1-nexusone-superboot" folder in the command prompt and tried
Code:
adb-windows remount
and my device showed up. Now I want to move those files to where I originally had my adb files in C:\android-sdk-windows\tools so that all I have to type is
Code:
adb devices
to have my phone listed. I tried replacing the files in my \tools folder and renaming them to what they were named before, but that didn't work. Could somebody please help me get this set up properly?
Click to expand...
Click to collapse
in your command prompt you have to be in the c:\android-sdk-windows\tools\ directory for it to work
ccunningham83 said:
Maybe I'm doing something wrong, but I can't get ADB to recognize my phone. ADB is all set up correctly, I have it updated (I believe) to the most recent version. I installed the updated USB driver and I see the "Android Phone" in my device manager. I have USB Debugging checked off in my phone settings. ADB worked fine for my G1, but it doesn't recognize my Nexus One.
I shouldn't have to root the phone to have ADB working should I? Can anybody think of something I overlooked? I am running Windows XP Professional SP3
Click to expand...
Click to collapse
I was having the same problem yesterday. But i'm on Vista. Nothing seemed to work, but ADB was working fine on my Mytouch. At any rate, I ended up going to download the most recent SDK and trying adb again from a command prompt @ the tools location of the newest SDK, and then everything worked. I don't know if that was something I should have done in the first place and I just didn't know it (duh), but that's what worked for me.

[Q] adb returning "error: closed"

Hi,
I'm currently trying to use adb to push some data into my phone but i always get "error: closed". I'm using windows 7 x64 and im running it from cmd.
Almost everything i tried using adb (push, shell, remount) returns this. I've searched over the forums and tried "adb devices" as well to see if my phone is connected, but what is different from the others is i am getting
List of devices attached
XXXXXX host
instead of what most other people got
List of devices attached
XXXXXX device
Is this a problem? What am i missing? Thanks a lot for ur time in reading this
Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices
Guich said:
Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices
Click to expand...
Click to collapse
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip
Did you update the SDK Manager??? Try updating that, my ADB problem were gone after i updated them.....
xlxcrossing said:
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip
Click to expand...
Click to collapse
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?
jflora1 said:
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?
Click to expand...
Click to collapse
Try to download this, un-zip and try the tips with this
Guich said:
Try to download this, un-zip and try the tips with this
Click to expand...
Click to collapse
I downloaded the zip but haven't had any success, still getting an error:closed message
ozo012 said:
I downloaded the zip but haven't had any success, still getting an error:closed message
Click to expand...
Click to collapse
which recovery are you on? (name and version number please)
nkk71 said:
which recovery are you on? (name and version number please)
Click to expand...
Click to collapse
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
isnt "error closed" something to do with out of date adb?
ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
nkk71 said:
isnt "error closed" something to do with out of date adb?
Click to expand...
Click to collapse
Umh, no, i don' think
Guich said:
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
Umh, no, i don' think
Click to expand...
Click to collapse
I haven't tried rebooting the device seems to be the only thing I left out.
I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.
worked for me
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload
morheb said:
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload
Click to expand...
Click to collapse
Yay. That Just worked for me using Crunchbang Debian. Thanks morheb that little tweak of using 'sideload' was the key
Can anyone help me push vold.fstab file with adb?
Stock Recovery on mediatek platform. with adb i got same error as this thread. Error:closed
KoolAidBigMan said:
I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.
Click to expand...
Click to collapse
Perfect - worked for me - exact same issue - adb wasnt recognising my phone was in sideload and sideload command wouldnt work but push would - plus getting error closed message on adb usb command. Googled the above adb file, downloaded, 15 second install and now sideloading is working on my SG2 with CWM recovery 6.0.2.9 (kitkat). I was obviously using an outdated ADB driver (1.0.29).
Thanks a lot KoolAidBigMan !! Big up...
Jimbo
EDIT : Spoke too soon - now getting another error when trying to sideload.. will google it.. failed to write data 'protocol fault (no status)'
EDIT : Sorted. Ended up getting round it by pushing the files instead - found instructions on Cyanogenmod forums. Thanks once again.
http://forum.xda-developers.com/sho...wQFjAA&usg=AFQjCNGgPmMne0aYCd9RojZZhy89cQjnCw
Try this
Sent from my C6916 using XDA Free mobile app
Link not working?? Im ok now anyway.. Time to test my screen casting to my Chromecast.. :fingers-crossed:
mtk6572 have same error
I have same error.. but I know that my phone's usb debugging is not enable.. so I got this error:close..
My phone is on bootloop so I can't enable the usb debugging.. Is there any way to enable the usb debugging using adb commands? I trying to push the framework-res.apk on my phone.. because it is the cause of the bootloop.
i'm a nood

ADB problem and no OS on device

Last night, on TWRP I formated data on the SD card, which is why I have no OS. Now looking for how to fix this on xda/google, I get into the bootloader, have fastboot usb and try to adb shell but I keep getting the "error no device found". I already installed latest drivers from HTC on to my laptop and still nothing. Any other idea?
windows 8?
First off, make sure you have HTC Sync Manager installed because that will give you the proper drivers in order to be able to use ADB commands.
Afterwards, make sure you install Java JDK and Android SDK.
Just follow this tutorial here: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Follow it word for word and make sure you install JDK X86 even if you have a X64 computer. And then download SDK Manager, put it in C:/ drive, open SDK Manager, and download the necessary tools (also all in the tutorial).
I was in the same position as you just before yesterday and I followed this tutorial with success.
skinsfanbdh said:
windows 8?
Click to expand...
Click to collapse
Windows 7, and mac.
Evolancer13 said:
Windows 7, and mac.
Click to expand...
Click to collapse
try downloading all in one toolkit and try that. just make sure to read the onscreen instructions as you go through the process
TarekElsakka said:
First off, make sure you have HTC Sync Manager installed because that will give you the proper drivers in order to be able to use ADB commands.
Afterwards, make sure you install Java JDK and Android SDK.
Just follow this tutorial here: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Follow it word for word and make sure you install JDK X86 even if you have a X64 computer. And then download SDK Manager, put it in C:/ drive, open SDK Manager, and download the necessary tools (also all in the tutorial).
I was in the same position as you just before yesterday and I followed this tutorial with success.
Click to expand...
Click to collapse
skinsfanbdh said:
try downloading all in one toolkit and try that. just make sure to read the onscreen instructions as you go through the process
Click to expand...
Click to collapse
I'll look into both things, thanks.
EDIT: even on my mac adb does not see any devices, before when I entered ./adb devices it would show "list of devices:" and it would be blank.
Good luck, man. It's fairly easy once you read the tutorial carefully and follow all the steps to the word. After it's all done and the command prompt says Sideload 100%, boot into TWRP, tap INSTALL and then scroll down to sideload.zip and that's your ROM. Also after copying the desired ROM to platform-tools in the SDK folder, rename it to rom.zip, it seems to work 100% that way while it struggles a bit with long names.
TarekElsakka said:
Good luck, man. It's fairly easy once you read the tutorial carefully and follow all the steps to the word. After it's all done and the command prompt says Sideload 100%, boot into TWRP, tap INSTALL and then scroll down to sideload.zip and that's your ROM. Also after copying the desired ROM to platform-tools in the SDK folder, rename it to rom.zip, it seems to work 100% that way while it struggles a bit with long names.
Click to expand...
Click to collapse
Still getting the error: device not found.
I even ran the all in one tool kit and attempted the "ADB sideload a ROM" follow the steps but get an error on CMD "C:\users\(username) is not recognized as an internal or external command, operable program or batch file"
I really do not understand why adb is not working, I did s-off and supercid myself maybe less than a week ago.
Are you sure you followed all the steps in the tutorial including installing JDK, using SDK Manager to download some tools and such? And are you sure you have the proper drivers installed (e.g HTC Sync Manager)? I used to get that error before I installed it. Go to Device Manager while in ADB mode in TWRP and see if the device is recognized or if there's a yellow sign beside it indicating that there are no drivers for it.
TarekElsakka said:
Are you sure you followed all the steps in the tutorial including installing JDK, using SDK Manager to download some tools and such? And are you sure you have the proper drivers installed (e.g HTC Sync Manager)? I used to get that error before I installed it. Go to Device Manager while in ADB mode in TWRP and see if the device is recognized or if there's a yellow sign beside it indicating that there are no drivers for it.
Click to expand...
Click to collapse
It came up under Android USB Devices as My HTC. When I was following the steps on the link you provided, when I tried to update the drivers with the google usb driver wouldnt work, it would say "windows had determined the driver software for your device is up to date". When I go into My HTC properties says the driver version is 2.0.7.18.
The Google USB drivers did not work for me either, only the ones provided by HTC Sync Manager did. I have not experienced that problem, mate, so I do not know what to do at this point, I am very sorry. If you are not able to fix this, I suggest getting an OTG cable and directly loading the ROM from the PC to your SD card. I ordered one a couple of days ago and it is coming tomorrow, it's very helpful
TarekElsakka said:
The Google USB drivers did not work for me either, only the ones provided by HTC Sync Manager did. I have not experienced that problem, mate, so I do not know what to do at this point, I am very sorry. If you are not able to fix this, I suggest getting an OTG cable and directly loading the ROM from the PC to your SD card. I ordered one a couple of days ago and it is coming tomorrow, it's very helpful
Click to expand...
Click to collapse
Crap, I appreciate your help though.
EDIT: nevermind googled it, gonna pick one up. Phoneless till wednesday
I am sorry to hear that, but I suppose that's the only thing you can do at the moment. Even if somehow get ADB working, do not cancel your order because OTG cables aren't only used for mounting the device, but also for things like connecting gamepads and controllers to play games on your device.
USB 3
If you have USB3 port adb.exe wan't recognize your device.
I triend first on USB3 and after on other older computer on USB2 all was fine
Evolancer13 said:
Last night, on TWRP I formated data on the SD card, which is why I have no OS. Now looking for how to fix this on xda/google, I get into the bootloader, have fastboot usb and try to adb shell but I keep getting the "error no device found". I already installed latest drivers from HTC on to my laptop and still nothing. Any other idea?
Click to expand...
Click to collapse
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip
tash2013 said:
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip
Click to expand...
Click to collapse
check first with "adb devices" to see does your PC recognize your HTC
tash2013 said:
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip
Click to expand...
Click to collapse
Tash2013 YOU ARE AMAZING! Got my One back up running!
Oh man I'm so glad it's working. I thought you already knew that it is sideload not shell lol.
Sent from my HTC One using Tapatalk 4 Beta
TarekElsakka said:
Oh man I'm so glad it's working. I thought you already knew that it is sideload not shell lol.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
If I knew I would have tried lol, and it no one said anything about sideload but oh well.
Haha! Damn. I am glad it worked out, though.

Looking to go AOSP from Stock KK [4.4.4]

Sooooooooooo,
I have a Z1 [C6903] that I picked up yesterday. It came with 14.2.A.1.136 Jellybean 4.3.
I wanted to
Unlock bootloader
Install custom recovery
Root
Install any nice AOSP ROM [preferably LP-based]
I installed the Minimal ADB-Fastboot 1.4.
I also installed the Flashtool 0.9.18.2.
I also installed the Z1 device, Fastboot, and Flashmode drivers [version 1.6.2] from the driver folder. It first failed, and then I disabled driver verification then everything went smooth!
Device manager recognized the phone in MTP and Fastboot, and Flashmode modes. Drivers installed correctly I presume.
Then the challenges arrive:
adb devices returned it as "offline"
Android studio couldn't push a project to it because it was offline
fastboot devices identified it, but fastboot -i 0x0fce getvar version returned an error [getvar:version FAILED (command write failed (Unknown error))]
Things I've tried to do to rectify the connectivity issue:
I'm using a SurfacePro 4 so I can't switch USB ports [only have one].
I've tried different cables - they yield the same result.
I've enabled and disabled USB debugging, revoked access, unplugged and replugged, rebooted, etc. Still no change in result.
Since the device had some OTA updates pending, I ran those and now i'm on 4.4.4 with 14.4.A.0.157, with some other updates currently waiting for me to accept so they can download. I've decided to post here for help and won't run those updates unless it increases my profit
PS: Even after the updates, adb and fastboot still are unchanged in their results.
Help please
Update:
It was a freaking USB cable. I had tried two of them. None had worked.
I finally unleashed my Anker USB cable and Boom! We good to go!!!
Thanks all!:highfive::highfive::highfive::highfive:
Make sure to enable USB debugging in Developer Options at the bottom of the Settings app
tomascus said:
Make sure to enable USB debugging in Developer Options at the bottom of the Settings app
Click to expand...
Click to collapse
Did this and more. Still to no avail.
The phone shows up in the computer, it just doesn't show as online when I run the adb devices command.
That's what I need help with.
Thanks
ahh have you tried using
Code:
adb kill-server
adb start-server
and trying again?
What should happen is the authorisation window pops up on your phone
tomascus said:
ahh have you tried using
Code:
adb kill-server
adb start-server
and trying again?
What should happen is the authorisation window pops up on your phone
Click to expand...
Click to collapse
Excellent! I did that, too. even manually closed and restarted adb.exe to no avail.
The thing is, my Z1 DOES NOT show me the authorization pop-up! Ever!
I've done this a million times on other phones, and I know the procedure. It's just that this Z1 is not showing the authorization popup
Thoughts?
boydee said:
Excellent! I did that, too. even manually closed and restarted adb.exe to no avail.
The thing is, my Z1 DOES NOT show me the authorization pop-up! Ever!
I've done this a million times on other phones, and I know the procedure. It's just that this Z1 is not showing the authorization popup
Thoughts?
Click to expand...
Click to collapse
Find a quiet corner and cry
Tried running adb as admin?
tomascus said:
Find a quiet corner and cry
Tried running adb as admin?
Click to expand...
Click to collapse
Tried this, too!
No change, anywhere.
I actually went ahead and tried adb on another PC with minimal adb-fastboot and adb drivers installed, and it returned the same "offline" response
Whoa!:angel:
@boydee
this could work with you
i assume that you rooted your phone you will do that:
1. open your favorite file explorer(suggest: ES File Manger)
2.go to /data/misc/adb/
3.delete "adb_keys" file
4.enable usb debugging
5.reinstall your drivers
6.open command and kill adb server(adb kill-server)
7.connect your device and run command (adb devices)
8.look at your device you will find text box telling you a new pc check always trust bla bla and click trust or something like that
9.you will see something like that
http://imgur.com/ReQtofb
How to upgrade to kitkat 4.4.4 India version of c6903 Sony Xperia Z1 pls help
DectonX said:
@boydee
this could work with you
i assume that you rooted your phone you will do that:
1. open your favorite file explorer(suggest: ES File Manger)
2.go to /data/misc/adb/
3.delete "adb_keys" file
4.enable usb debugging
5.reinstall your drivers
6.open command and kill adb server(adb kill-server)
7.connect your device and run command (adb devices)
8.look at your device you will find text box telling you a new pc check always trust bla bla and click trust or something like that
9.you will see something like that
http://imgur.com/ReQtofb
Click to expand...
Click to collapse
Hey, thanks for the advice!!
Finally got root [without use of PC] and when I open the /data/misc/adb/, the folder is EMPTY
A little confused there.
I did the same procedure for the PC [deleting from C:/Users/boydee/.android/] but it also was to no avail.
k9rockstar said:
How to upgrade to kitkat 4.4.4 India version of c6903 Sony Xperia Z1 pls help
Click to expand...
Click to collapse
Hey there! Please check here for a firmware file that works for you.
When you've downloaded, use the Flashtool to flash it to your phone.
If you want help flashing it to your phone, check this thread out.
Hope that helps
boydee said:
Hey, thanks for the advice!!
Finally got root [without use of PC] and when I open the /data/misc/adb/, the folder is EMPTY
A little confused there.
I did the same procedure for the PC [deleting from C:/Users/boydee/.android/] but it also was to no avail.
Click to expand...
Click to collapse
This could problem with installing drivers as PC don't detect adb in debugging mode
So disable driver verification again and install drivers from flashtool remember to check
1. Fastboot drivers
2. Flashmode drivers
3. Xperia Z1 drivers
And restart
If the problem not fixed try adb universal drivers just Google it
I was have same problem with win 8.1 but I didn't all that I just installed win 7 and do it
Remember to backup ta before unlock to backup your DRM keys

need support to downgrade

guys i need support , i want to downgrade my sony from 7.1.1 to 6.0.1 to root and backup that key but i ended up twice with
ERROR - Processing of system.sin finished with errors.
please help , i cant find anything usefull than extract that file and install it , but that wont work if i soft brick it
Do you use the latest Flashtool(0.9.23.2) to flash the FTF file?
If yes, sometimes just flash FTF again right after error occurs may fix the problem.
f870103 said:
Do you use the latest Flashtool(0.9.23.2) to flash the FTF file?
If yes, sometimes just flash FTF again right after error occurs may fix the problem.
Click to expand...
Click to collapse
its sloved, it seems it was a corrupt fileso i dled the koran ver and that worked, thx , the only problem is back up ta, i cant find out howto without losing the drm kry,
i watched a couple youtubes, i readed a few guides but nothing is clear enough how to , i got that script but it say device not found , i tried in dwonload mode and local charging mode
Use this tool to backup your TA partition.
You need to backup it in Android system with adb access, not Download mode or Flash mode.
To check if your computer has adb access, simply type "adb devices" in the command window.
f870103 said:
Use this tool to backup your TA partition.
You need to backup it in Android system with adb access, not Download mode or Flash mode.
To check if your computer has adb access, simply type "adb devices" in the command window.
Click to expand...
Click to collapse
i installed adb and drivers and alot other stuff to get it to work like flashtool and so , but can't seems to get it to work, best i could do is rollback rom
thats why i asked if someone can pass me a guide i can folow and understand, because simple im missing something
i never had it this hard with samsung
would be nice if i had more support on this mather
Wesley_NL said:
i installed adb and drivers and alot other stuff to get it to work like flashtool and so , but can't seems to get it to work, best i could do is rollback rom
thats why i asked if someone can pass me a guide i can folow and understand, because simple im missing something
i never had it this hard with samsung
would be nice if i had more support on this mather
Click to expand...
Click to collapse
I see you have enabled ADB on your device, and connected to your computer. But ADB did not find your device.
Maybe you should re-install your adb driver.
You can download ADB Installer by @Snoop05 here.
After installing ADB driver correctly, you should see your device on adb device list.
f870103 said:
I see you have enabled ADB on your device, and connected to your computer. But ADB did not find your device.
Maybe you should re-install your adb driver.
You can download ADB Installer by @Snoop05 here.
After installing ADB driver correctly, you should see your device on adb device list.
Click to expand...
Click to collapse
i get more details now, so am i good now ?
-edit guess not
Wesley_NL said:
gumm i get more details now, so am i good now ?
Click to expand...
Click to collapse
It's "adb deviceS" not "adb device".
f870103 said:
It's "adb deviceS" not "adb device".
Click to expand...
Click to collapse
oops my bad lol i simply copy pasted missed s
but still not able to see phone i guess ?
Wesley_NL said:
oops my bad lol i simply copy pasted missed s
but still not able to see phone i guess ?
Click to expand...
Click to collapse
Yes. adb still can't find it. Did you try ADB Installer I mentioned before?
f870103 said:
Yes. adb still can't find it. Did you try ADB Installer I mentioned before?
Click to expand...
Click to collapse
uhuh i did,
but i did not install it as admin so i tried again and i guess i have a result now
but in ta still no device found
Wesley_NL said:
uhuh i did,
but i did not install it as admin so i tried again and i guess i have a result now
but in ta still no device found
Click to expand...
Click to collapse
Just type "adb devices" again.
f870103 said:
Just type "adb devices" again.
Click to expand...
Click to collapse
i did after reinstall, adb devices, go to ta folder and pressed the bat file and error device not found while adb see it right ?
-edit, i tried again this time in 1 windows but same result
Wesley_NL said:
i did after reinstall, adb devices, go to ta folder and pressed the bat file and error device not found while adb see it right ?
Click to expand...
Click to collapse
Well, try another installer in the attachment.
f870103 said:
Well, try another installer in the attachment.
Click to expand...
Click to collapse
still not T.T something is blocking it probaly ?
maby the android studio ? although i removed the google driver and reinstalled that adb driver but no luck
I've PM you for the problem.

Categories

Resources