Database Develop

Help is appreciated.

Ok so this all started 7 hours ago.
I did a factory reset and I couldn't get passed the gmail account login. I tried multiple times, and tried resetting. Didn't work.
So I looked online to see if I can use wifi, and I could.
http://modmygphone.com/forums/showthread.php?p=51891#post51891
I updated my drivers, downloaded Android SDK.
I got up to the part where I type " adb shell "
It says no devices found. Please help. Thanks in advance :]

Q&A forum?

TmobileDash12 said:
Ok so this all started 7 hours ago.
I did a factory reset and I couldn't get passed the gmail account login. I tried multiple times, and tried resetting. Didn't work.
So I looked online to see if I can use wifi, and I could.
http://modmygphone.com/forums/showthread.php?p=51891#post51891
I updated my drivers, downloaded Android SDK.
I got up to the part where I type " adb shell "
It says no devices found. Please help. Thanks in advance :]
Click to expand...
Click to collapse
More info is needed, like are you on stock OS or what were you exactly trying to do.
And please refer here when you need help, as what you posted is not development

Sorry, thanks for the tip :]
I had so many tabs open i didn't realize i was in the development thread.

TmobileDash12 said:
Sorry, thanks for the tip :]
I had so many tabs open i didn't realize i was in the development thread.
Click to expand...
Click to collapse
It says no device b/c you probably don't have the adb driver installed.I don't have the link for it but it's some where.

Debugging
Please correct me if im wrong, but dont you have to have usb debugging checked off.

Gilbertinho said:
Please correct me if im wrong, but dont you have to have usb debugging checked off.
Click to expand...
Click to collapse
Even with it on you need the driver for your phone to be detected, in vista adb didn't work till i had the driver...Same thing happened in 7.

TmobileDash12 said:
Ok so this all started 7 hours ago.
I did a factory reset and I couldn't get passed the gmail account login. I tried multiple times, and tried resetting. Didn't work.
So I looked online to see if I can use wifi, and I could.
http://modmygphone.com/forums/showthread.php?p=51891#post51891
I updated my drivers, downloaded Android SDK.
I got up to the part where I type " adb shell "
It says no devices found. Please help. Thanks in advance :]
Click to expand...
Click to collapse
First off which OS are you running on your computer Windows,Mac,Linux? 0o
Windows you download the driver through the sdk
Linux you don't need to download anything but the sdk
and mac I don't know XD

I am running Windows XP
I updated my drivers and installed them.
[Though I don't know if they were successfully installed]
Maybe someone can use TeamViewer with me to help me?

kinda sounds like the setup wizard FC bug that happens in some of the roms.. what were you flashing? if it was a buggy rom, might wanna try a previous version and reflash the new one after the setup.
let's hear some more info as to what you were doing that may have caused the problem.

http://forum.xda-developers.com/showthread.php?t=452316
I flashed to RC29.
I have 3g [IDK if that counts as a data plan thing]
I can't go past the gmail login [even though i did before, strange]
So i tried doing the wifi bypass. And now I'm stuck

Nexus One ADB Driver Endless Reinstalls

I have 2 Nexus One's. The first was rooted and I had the ADB USB driver (v3) installed on my Windows XP Pro SP3 desktop and all worked fine.
I now have a second Nexus One. I rooted it, and after turning on "USB debugging" and wanting to use it with ADB, the driver USB installed again. But now I get constant "Found New Hardware Wizard" install loops, for both phones with "USB debugging" turned on.
Every time I plug either phone in, or reboot, Windows wants to reinstall the ADB driver. Right after it completes a driver install it wants to do it again.
Solutions I've tried; I have rebooted after install, uninstalled the drivers from Device Manager, deleted the drivers manually from the registry, removed any possibly associated hidden drivers that were marked error in Device Manager, and combinations of the above in various order.
I know that USB driver install loops on Windows can happen to any type of device, not just the Nexus, but in my case it's only on the ADB driver for Nexus One.
Can anyone suggest what I can do other than what I listed to stop the ADB driver endless install loop, or what is causing it?
Thank you.

ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...

johng75 said:
ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...
Click to expand...
Click to collapse
No, I haven't found a solution to this yet. And you are the only person here that has replied.
I did contact Google and HTC and asked for their help. But since the phone is rooted I got the expected replies from both, that rooting violates warranty so they refused to help. I was expecting that, but have heard that the occasional tech support person at Google will still offer support within reason. But not in my case.
If and when I figure this out, I'll post it here to help you out.

johng75 said:
ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...
Click to expand...
Click to collapse
Hi JohnG75,
Just wanted to let you know my constant ADB driver reinstalls have stopped. But unfortunately I have nothing constructive to point out as a solution. I spent hours online researching for a possible solution, and found nothing worthwhile yet. I've posted in several places and got no helpful replies other than trying System Restore and going back to a point before this happened. Of course that's hardly a guaranteed fix, plus you loose any other updates and installs you have made since then.
In my case, I left "USB debugging" turned off on my phone since I wrote you last, and the only thing that has changed system wise for me, is I have installed 2 unrelated device drivers since, and MS has pushed out a security update. So today when I turned "USB debugging" back on in the phone, it did a single device install, and it didn't repeat. So hopefully this resolves it for me.
If I were to take a guess as to what appears to have solved it in my case, I would say it was the new unrelated device driver installs. Perhaps it cleared whatever was wrong in the device driver system. So maybe if you were to install some new device driver you need, or uninstall an existing one, reboot and then reinstall that same device driver, perhaps it will clear whatever is messed up in your device drivers.
Sorry I can't be of more help, and my suggestion is only a guess based on my only recent system changes.
There is very little documented solutions to this problem out there, only lots of people that have complained about the same type of problem, with every sort of device you can think of. And the solutions documented are always specific to those exact devices.

[Q] Problem rooting Stock froyo captivate

Hi All,
I just purchased my Captivate yesterday from Costco (Expecting to still get the 2.4 Eclair) but unfortunately I got the Froyo 2.2 on my new captivate.
I tried rooting it using superoneClick and it just gets stuck on "Waiting for Device". I have drivers properly installed on my windows 7 64 bit machine (because I can use the phone and access its internal SD card).
Can anyone have suggestion or faced similar problems?
I have tried disabling/re-enabling usb debgging while it says "Waiting for the device"

Search the forum. There are a few threads floating around on different ways to root the stock froyo build. I don't know why the superoneclick wont work in your case but a search will turn up some info for you.

thanks. I will search the the threads and will post my results here in this thread for someone like me struggling with the same problem.

If you were planning on flashing a custom ROM after rooting anyway, you could use Odin one-click from download mode to flash 2.1 eclair, and then go from there.

Are you sure you are enabling debugging? I just used superoneclick on my phone last night after I flashe dback to stock.
First thing I do is change the phone in settings to - Ask on Connection, then I enable debugging.
Also you could try a different USB port on your computer and also make sure you have all of your necessary drivers installed.
I hope you get it figured out!

PeteSeiler2010: I haven't tried different USB port yet. I will try tonight and see if it goes through.
For usb debugging, I tried that as I mentioned. Let me just conform what I did. When it says "Waiting for device" for several seconds, I disconnected USB cable from either phone or computer (because it says that if you are stuck on "waiting for device", disable and re-enable usb debugging) because without disconnecting the cable, phone didn't let me disable the USB debugging..
So looks like I am missing something here??

22andy2 said:
PeteSeiler2010: I haven't tried different USB port yet. I will try tonight and see if it goes through.
For usb debugging, I tried that as I mentioned. Let me just conform what I did. When it says "Waiting for device" for several seconds, I disconnected USB cable from either phone or computer (because it says that if you are stuck on "waiting for device", disable and re-enable usb debugging) because without disconnecting the cable, phone didn't let me disable the USB debugging..
So looks like I am missing something here??
Click to expand...
Click to collapse
want a much easier method? install speedmod kernel using odin, reboot into recovery, advanced features (not the CWM version), and choose the option that says something like "root phone" and choose the "simple" option. congratulations, you are now rooted and running a custom kernel with CWM that can install a custom ROM.
next time, please do not post this in development as this has NOTHING to do with development. Q&A or general next time, please.

How did someone with no posts, post a question in this section? I thought you had to have a minimum of 10 posts to post in here.

I am sorry if I have missed that rule for the new posting but I am new (just two days old) into the android world and for the xda forums as well..

22andy2 said:
I am sorry if I have missed that rule for the new posting but I am new (just two days old) into the android world and for the xda forums as well..
Click to expand...
Click to collapse
So why is your join date Dec 2007?

CB650 Wolf said:
So why is your join date Dec 2007?
Click to expand...
Click to collapse
thats when I just registered.. I will be the active member now as I officially own the android phone.
I really appreciate all of you guys work and I didn't mean to offend any one by posting the thread here.
I already apologize for missing the rule for the 10 minimum posts on forum before posting.

I rooted my device successfully by using odin. Thanks all of you for the suggestions.

Can't get Oneplus 3T recognized via ADB

I'm sure I'm not the only person who's had this issue but I've read through a bunch of threads and can't seem to find any that mirror the issues I'm seeing.
I downloaded the latest google drivers here:
https://developer.android.com/studio/run/win-usb.html
I changed the USB mode from charging to file transfer (not sure if that matters but one of the threads said this helped discover the ADB device needs, which was the case for me)
When I look at the device manager, I see this:
http://pasteboard.co/5UkUolhM2.png
I actually thought I was going to see this (based on a few user posts I read) but no luck . . .
http://pasteboard.co/5Uo9QvP8z.png
I hate asking such a basic question (I'm trying to root my phone but I'm already stuck at the backup stage . . . heh) but I've honestly tried to look through the threads and resolve it but I haven't found a solution yet. It doesn't mean one doesn't exist (I apologize if one does, I honestly have tried to solve this myself).
I apologize for the links rather than pics but it doesn't seem to want to let me use the IMG tags (do they not work with *.png?).
Any help you can give me would be greatly appreciated. Thanks!

I have a somewhat similar problem. Which I can attribute to some sort of driver/inf screw up
Any device i connect to my Win 10 PC in MTP mode gets recognized in device manager as MTP device and I can't do anything about it.
Unless I go back to driver setting, have it automatically find updated drivers, which it doesn't.
But then right after, if i go to manually select driver and switch it from MTP to MTP USB - it fixes everything
Any idea how to fix that. I'm sure it's a similar issue to this.

I couldn't use the Google drivers, I had to use the OnePlus Driver package.
Beside, did you guys enable USB debugging?
Cheers
Tom

if device manager is showing any unknown devices then start with that when you can plug in the phone without problems have a look at this.
https://forum.xda-developers.com/showthread.php?t=2317790

Which adb version do you use?
Sent from my ONEPLUS A3003 using Tapatalk

I've actually tried installing those drivers (on the partition), the google drivers, a fastboot and ADB program, and even an all in one tool for drivers and none of them worked.
That said, I might have found my problem. I've tried several approaches and found out the the virus protection on this computer (Cylance) is blocking everything. Also explains some issues I had getting things to work with some home automation projects . . . I'll have to find another computer for development.
I'll give you guys an update once I have one. Thanks for the quick replies.

I wanted to follow up on this since I got it up and working just fine.
First off, thanks to everyone that helped, either those that provided answers, or those that confirmed they were seeing the same issues.
It does appear that cylance (my antivirus) was blocking a number of things. I have a different laptop with a fresh version of windows 10 (not a requirement, just making note of this) and protected by bit defender and set it up with that. This is what I did:
1) Plug phone into computer
2) Went to pulldown menu, clicked on "charging mode" and changed it to "transfer files"
3) A partition was found on my computer called "Oneplus Drivers" (on the my computer page, next to the C drive). I double clicked on the directory and it installed the drivers to my computer
4) I downloaded and installed Minimal ADB with fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790. (You'll need to click a few links to get to the actual download but I wanted everyone to know that it's a legitimate link and not just my own personal/questionable source)
5) I ran minimal adb and typed "adb devices". It will show your device as "unauthorized" initially because it hasn't been accepted on your device. Open your device and click allow or ok or something to that effect (didn't think to take a screenshot). Your call if you want it to always remember that device.
6) Type "adb devices" again and it should show your device labeled "device"
So yeah, that's how I got the basic ADB up and working. Hopefully you guys resolve this as well. Good luck!

I was too having the same issue but solved using this easy method https://youtu.be/LbAq6d2Du0U

jbrookley said:
I'm sure I'm not the only person who's had this issue but I've read through a bunch of threads and can't seem to find any that mirror the issues I'm seeing. ...
Click to expand...
Click to collapse
Try the ones here? > http://www.technobuzz.net/download-oneplus-3-usb-drivers/

hello2010 said:
Try the ones here? > http://www.technobuzz.net/download-oneplus-3-usb-drivers/
Click to expand...
Click to collapse
I'm confused, I posted a solution to this 2 posts ago. Are these drivers any better than the ones that are on the phone itself as described in my previous post?

jbrookley said:
I'm confused, I posted a solution to this 2 posts ago. Are these drivers any better than the ones that are on the phone itself as described in my previous post?
Click to expand...
Click to collapse
I haven't compared them so I can't comment. The above link was where I learned to install the drivers once (because it worked the first time). If your connection is working fine now, just treat the info in the link as added reference.

hello2010 said:
I haven't compared them so I can't comment. The above link was where I learned to install the drivers once (because it worked the first time). If your connection is working fine now, just treat the info in the link as added reference.
Click to expand...
Click to collapse
Oh, ok! All caught up!

Having the same issue. Didn't have any issue with my old Huawei Ascend Mate 2 though.

j03x2 said:
Having the same issue. Didn't have any issue with my old Huawei Ascend Mate 2 though.
Click to expand...
Click to collapse
Have you tried any of the solutions that were posted?

Didgeridoohan said:
Have you tried any of the solutions that were posted?
Click to expand...
Click to collapse
Problem solved now. For some reason the USB Debugging flag changed without me doing it.

Unable to unlock bootloader due to errors within ADB and fastboot

Hello,
this is my first thread/post on this forum, if I did anything wrong please don't be super harsh and inform me to what to do better, thanks.
So why am I asking for help anyways you may ask, well I had my old Xperia Z1 laying around here for quite a while now and wondered if I could do anything productive with it.
So I came up with the idea to install a CFW like Lineage OS or something else.
This is not my first rooted and cfw phone but the first one what gives me nightmares and a headache.
So after reading all of the nice guides how to root it and how to unlock it, nothing of them is working for me, most of the threads have missing files which I cannot find on google or other just simply won't work for me.
First of all, I have rooted my phone via KingRoot in the meantime since the other methods where not working either.
I have turned on usb-debugging and also allowed installation from unknown sources.
And there we start with the first problem, downloaded the google SDK and installed all adb things I needed, did not work, then I tried it from the official sony website, downloaded the usb-driver folder and tried to install it manually, won't work either, because the device manager always gave me error code 10 "device cannot be started", I tried different sources and even die google studio thing and everything ended up with the same result.
Same error code even when I tried to activate fastboot on my phone by pressing down the volume up button, pluging the usb cable in, and yet again the same error message for this device too.
I am using windows 10 and never had such problems before with sony devices.
I hope someone of you can help me out to find a solution, if you need any further information, just let me know.

Did you solve this?
I have the same problem

snailer said:
Did you solve this?
I have the same problem
Click to expand...
Click to collapse
This may sound stupid or ridiculous, but yes I managed to work it out and was able to install the CWF on my phone which is working perfectly fine.
Since nobody was willing to help me I just skipped the part where I wanted to post my solution but yeah, this may help you too.
So what did I do? Simply I stopped using Windows 10 for this project, I just used one of my older PC's which still had Windows 7 Ultimate on it.
I just rooted the phone via KingRoot, since it was the only solution what kinda worked out for me, then I was able to install all needed SDK, fastboot and ADB files on my PC and was able to use the ones from the Sony site itself this time and after plugin in the phone to the PC, it installed everything else what was needed for the device manager.
After that was done with no error I was finally able to unlock the phone via the command which you can find also on the Sony website.
If you find this helpful or need any extra information just let me know, maybe I can help you then. Oh and if you found out a solution for you what worked, would be nice to hear that too.
Greetz