Database Info

[Q] i9023 doesn't ask to connect storage to pc when I plug it in anymore?

I have i9023 runinng stock 2.3.6.
I want to back up some things from the storage but when I plug it ito my PC I don't get the notification thing to click to connect the storage anymore. Just the USB debugging icon pops up.
Any ideas why this is? Don't think I changed anything

Plug the phone into your computer, turn the phone off. While still plugged in boot into fastboot and you should hear your computer make the sound it makes when you normally plug your phone in. Unplug the phone and it should make another sound. Finally plug the phone back in and it should make said noise, click reboot and it should be able to connect. I don't know what causes this but it's happened to me about 3 times and everytime iv done these steps to fix it.
Sent from my Nexus S using XDA App

The only thing worked for me was to remove the battery.

If you done that before, just restart your pc and your phone, and connect them again.
I think you maybe disable some usb service. after restarted it will be fine.

thanks after messing around rebooting the phone etc I think the problem was the computer, doh. rebooted THAT and now all working fine
thanks for the replies =)

Help!! Nexus S stuck in Downloading...

Hey guys, so I just came across a Nexus S GT-i9020T but it has a problem! The problem is right after it's turned on, it immediately goes into "Downloading... Do not turn of target!!!" with an android sweeping up icon... Now I just bought this off a guy and he only told me that the last thing he did was install some Cybermod 9 skank mod??? he claims the phone was working fine until he went to reboot and got this Downloading.. screen from there on out.. Now I can't even get the phone recognized on my Windows 7 computer but I'm really new to this stuff and thought if i could get this fixed i'd have a cheap new/used Nexus S.. I've tried the Volume Up + Power hold, and other variants and cannot get the phone into bootloader. Also, when I plug in the USB cable there's no charging icons, and it seems the battery is getting low and dying so I'm going to buy an external battery charger to keep it topped up while I try to repair it. Please tell me what I can try to get this thing working! Thank you!

r3ap3r911 said:
Hey guys, so I just came across a Nexus S GT-i9020T but it has a problem! The problem is right after it's turned on, it immediately goes into "Downloading... Do not turn of target!!!" with an android sweeping up icon... Now I just bought this off a guy and he only told me that the last thing he did was install some Cybermod 9 skank mod??? he claims the phone was working fine until he went to reboot and got this Downloading.. screen from there on out.. Now I can't even get the phone recognized on my Windows 7 computer but I'm really new to this stuff and thought if i could get this fixed i'd have a cheap new/used Nexus S.. I've tried the Volume Up + Power hold, and other variants and cannot get the phone into bootloader. Also, when I plug in the USB cable there's no charging icons, and it seems the battery is getting low and dying so I'm going to buy an external battery charger to keep it topped up while I try to repair it. Please tell me what I can try to get this thing working! Thank you!
Click to expand...
Click to collapse
check if the volume down is stuck. power button + volume down get you into download mode.

Not quite sure how to tell if the volume down button is stuck... I can hear it clicking when i push it.. Hitting around the volume button area doesnt seem to do anything.. Any key combo I hold always brings me into "Downloading.."
Edit: I opened up the phone and the volume keys seem to be working fine

Do you have the Android SDK? I'd think if you got those, you'd be able to issue the ADB commands and reboot into the bootloader that way.

Yes i have the Android SDK installed properly, however i'm not sure if i have the correct USB Drivers since i just got this phone and havent ever hooked it up to my PC before.. I've worked on my Galaxy S and Galaxy Nexus before, but i've since updated USB drivers to 1.4.8..... I tried 'adb devices' in a terminal and can't get the PC to recognize the phone at all, but thats about all i know for commands. What else can I try??

ok so i found a list of commands, tried 'adb reboot-bootloader' but its saying error: device not found... Now my battery is almost completely dead and phone only comes on for 3-4 seconds so i think i need to go buy that external battery charger before i continue because the phone will NOT charge via usb cable attached to phone..

I haven't updated my SDK in ages and it still recognizes my device. In my case, sometimes my USB ports act funky and won't recognize my phone. I'd have to either restart the PC or switch ports and it would work. Let us know if you get the phone fully charged up

chronophase1 said:
I haven't updated my SDK in ages and it still recognizes my device. In my case, sometimes my USB ports act funky and won't recognize my phone. I'd have to either restart the PC or switch ports and it would work. Let us know if you get the phone fully charged up
Click to expand...
Click to collapse
So i picked up the charger and now have a charged battery! Still not sure how to get the PC to recognize the phone though... Was I right in installed the 1.4.8 Samsung mobile phone driver or is there another driver i need to use like pdanet???

OK!! Got the PC to recognize the phone being plugged in but it's still showing up as "Unknown Device" under device manager.. I'm guessing this means I don't have the right drivers, or?? Also I'm not getting anywhere under terminal "adb devices" or "adb reboot-bootloader".. saying error: device not found

Install the drivers through pdanet

djquick said:
Install the drivers through pdanet
Click to expand...
Click to collapse
The problem with PDAnet is that I can't actually turn the phone on to enable debugging so PDAnet doesn't fully install - unless i'm mistaken but it still shows as Unknown device in device manager

Anyone??????? Just to recap, on my Nexus S when i turn the phone on i'm stuck on the "Downloading... Do not turn off target" screen (can't use volume up + power) always goes to download screen.. The phone shows up as "Unknown Device" in device manager.. Odin doesnt pick it up, adb devices shows no devices... Ive tried a few different drivers such as pdanet, samsung 1.4.8, with no success.... Please someone must know a solution?

go go linux, bit of a pita but the drivers shouldn't give any problems

I have ubntu on a usb stick already but i don't really know how to use it all that well... will it have drivers already or do i need to download some linux usb samsung driver?

http://source.android.com/source/initializing.html
this has the info on the driver bit see configuring usb access, the rest would just be getting adb and fastboot for linux

I really can't figure out Ubuntu.. i even seemed to brick it somehow off a usb stick.. try to boot it and just get a black screen after the UBUNTU logo loading screen... man i'm hopeless lol

Aaaaaaaaaanybody?

dewaffelhaus8 said:
http://source.android.com/source/initializing.html
this has the info on the driver bit see configuring usb access, the rest would just be getting adb and fastboot for linux
Click to expand...
Click to collapse
OK after a few hours of messing around I got Ubuntu up and running, installed JDK, SDK, and still no devices found when i bring up a terminal and type 'adb devices' while the Nexus S is on and in downloading do not turn off target!! mode.... Tried Unbrickable resurrector with no success saying it can't find device either... I know I have usb drivers and adb installed correctly because i can plug in my Gnex and get the adb device # no problem... This is super frustrating!!

bump

Wish I knew of another way to help. I'm out of ideas.

Elephone P3000s not working

My phone only shows the the elephone 2 e sign when I turn it on. I have tried pressing the on and volume key when I turn it on but nothing happened. I have followed some instructions on the elephone manufacturer site about installing drivers to my computer and then trying to reinstall the firmware. Unfortunately my computers (I have tried on three different ones) does not identify that a device is connected to the computer. Therefore I can't proceed to install the driver as according to my computer it is not installed. I have tried 2 different leads as well. I would be grateful for some help as I have no idea where to go from here.

Facing a similar issue, and since there's still no reply to this thread, I would like to add up a few findings I have on this matter to maybe help others and get helped.
My P3000S is also reaching the Elephone logo and displays it for a minute and then restarts, repeating the process (aka boot-loop).
The same happens whether it is connected or not connected to the charger/computer through a USB cable. (I've tried new cables but that's not the case).
When disconnected I can stop the boot-loop only by holding down the on/off button for a few seconds (or removing the battery of course).
When connected to the the charger or computer through the USB cable I have no way to stop the boot-loop (holding down on/off just restarts it).
Now with the battery removed..:
If I connect it to the charger/computer, though the charging red light turns on normally, I can't turn on the phone using the on/off button.
However, when connected through USB to a windows computer, I can see in the device manager that, right when I connect the phone it shows up as "Mediatek Preloader USB VCOM Port" under COM ports group, for 1 second and then disappears as if it was disconnected. There's no repetition here I have to manually hold down the on/off button or disconnect and reconnect the phone from the cable to cause this to happen again.
So, I am unable to flash anything nor turn the phone on because I practically only have 1 second of its presence in my devices list.
Also, I have tried all possible combinations with the volume up/down keys and the on/off button in order to enter recovery mode, with no success..
In case anyone has faced something similar or has any ideas on a possible fix on this phone please feel free to reply.

At last a reply to my initial message. Unfortunately it was someone with the same problem as me. I took out a paypal case against the person I bought the phone from and eventually they repaired it. Unfortunately they never told me how. To make matters worse it broke again within 2 months. The phone is now sat in a draw doing nothing. I have given up on it and will never buy another Elephone phone again.

Bootloop Amazon Fire Phone

Hello there everyone, hope you guys are doing great. Well, this thread might be a bit stupid at first since many others might have posted something related to it but since I couldn't find the exact answer, I had to post a newer thread.
I have a Fire Phone which used to run great and perfect and I had been using it the other day while charging it with an Aspor Powerbank which does run great. The Fire Phone got stuck due to a few NOT FOR THE FIRE PHONE apps such as the Instagram and the rest. When stuck, I held the power button for 10-15 seconds to do a reset and it did work while it was still on charging. Now the phone wouldn't turn on without the AC power via the USB. It gets stuck in a boot-loop. Just shows the Amazon logo and restarts again. Nothing works at all, not even the recovery mode or the rest or even resets without the USB plugged in.
I did try to upgrade but was of no use at all, did try the Cynogen OS by flashing it in. It didn't work at all and the same issue persists. I have removed the battery and plugged it back in but again of no use. The battery does charge if you think it's the battery, The battery does stay there active and great. I did try changing the USB cable and the Adapter. Nothing!
One more thing, when plugged in to AC, I can go to the Recovery Mode and then remove the USB cable, the Recovery Mode does stay active on battery power for countless hours. What should I do?
Is it the USB port? Is the battery? Or is it just me?

Oh btw, I did try installing the Stock Update available on Amazon.com and the PC (Windows 8 64-bit) does recognize the phone on ADB mode. Does list the serial of the phone when connected but when side-loading an update via the ADB, it says that it doesn't read! Gives an error. How do I work on that? I did try installing the ADB drivers again but still nothing. Did try downloading the updates from other sites and even a downgraded file, nothing works. What should I do?

Unable to connect to PC in any mode

Hi all, I'm afraid I already know the answer to my question but I'll still ask if there's even a slight chance to get this fixed on my own.
I had this issue on Android 8.1 where my Pixel kept saying "Supplying power to connected device via USB" even without anything connected to it, (it started doing that one day without any reason) tapping the notification allowed me to switch to "Charge this device" and then turn on MTP mode, battery life was terrible but I wasn't that much bothered by it because I am an Android developer so I kept it connected in USB Debugging mode most of the time anyway.
When I got the notification for Android 9 update I decided to update hoping it'd fix the USB issue but after the update it now always says "Charging connected device" and tapping the notification does bring up the "USB Preference" screen and it allows me to switch to "USB Controlled by this device" and it starts charging but there's no way to switch "Charge only" mode to anything else, ADB does not see it, fastboot does not see it and there's no persistent notification on the phone about it being connected via USB at this point (in any mode). My understanding is that this is a hardware issue but Oreo still allowed me to workaround this and get the USB debugging connected.
Is there anyway I can get back to Oreo without using fastboot flash or any other solution to this?
Thanks for reading.
PS. I'm on Ubuntu but I can access a Windows machine if required and bootloader is already unlocked.

I'm curious if you're able to connect to a USB OTG storage device.

I'm having this issue connecting it to my windows 10 laptop.. the cable recognizes it.. starts charging.. shows option on phone to change type of connection.. but not matter which one i change it too, the computer will not pull lit up as a drive to see the files..

Jaws4God said:
I'm having this issue connecting it to my windows 10 laptop.. the cable recognizes it.. starts charging.. shows option on phone to change type of connection.. but not matter which one i change it too, the computer will not pull lit up as a drive to see the files..
Click to expand...
Click to collapse
Same here! I plug the cable into the Windows 10 computer, I even can change the mode from charging to MTP file transfer, but the device won't show up in the Windows Explorer. It appears under connected devices though.

My Pixel 2 XL would not connect to PC for file browsing if USB debugging of Android Apps was enabled in developer settings. Didn't matter which option I chose to connect. IDK if that is expected or not, but it took me a while to figure out. Happened Spring 2018, idk if Google fixed it.

pyro226 said:
My Pixel 2 XL would not connect to PC for file browsing if USB debugging of Android Apps was enabled in developer settings. Didn't matter which option I chose to connect. IDK if that is expected or not, but it took me a while to figure out. Happened Spring 2018, idk if Google fixed it.
Click to expand...
Click to collapse
I don't think i've tried to turn that mode off.. i'm so used to needing it on for the computer to recognize and connect to all my previous Android Devices.. thanks for the recommendation...

post-mortem said:
I'm curious if you're able to connect to a USB OTG storage device.
Click to expand...
Click to collapse
Couldn't find any OTG cable to try that but strangely enough a few days back I connected it to PC for charging and Nautilus popped up, same cable, same USB port and it started working all of sudden. Did verify with a couple of other cables and different ports and everything is working fine since.
"Charging connected device" notification never appeared again, only thing different (when it started working again) was that I was out of the air conditioned room most of those days, might it be moisture or something like that?
I'm back to my normal routine for a few days now and it's still 100% normal, will have to see if it stays that way.
Sorry for late response.

Here's an update in case someone else runs into this situation, I can say this with 99% certainty that is caused by the blackish residue build-up around the USB port over time. It's not too much that it's visible just by looking into the port but it's enough to make the device behave like this.
Here's what I did to get rid of it, took a match stick (don't use anything metal) and broke it in half making a sharp edge on both broken pieces, took the non coated piece and inserted sharp edge in the bottom side of the port and gently wiggled it around while applying some pressure towards the connector (just a little bit, make sure you don't break anything), did this for about 45 seconds then took out the match stick and the part that was touching the connector had turned blackish (I guess this is when you know you have 'cleaned' it enough?), repeated the same process on the top side of the port with a new match stick piece (guess you can use the same one after cleaning it with a tissue), the only difference was that this time applied the pressure in opposite side (other side of connector), device was on during all this time.
It builds up again after a while (~3 months) so I had to repeat the entire process again when it started doing that again at the start of December but it wasn't that annoying this time because I knew exactly what was wrong and how to get rid of it, device is still working fine 100%.
I'm simply sharing my experience and not encouraging anyone to do this but if you do decide to try this be sure not to use anything metal and don't break the connector inside the port (turning the device off would be a good idea too) and you'll be fine and if something does go wrong I won't be responsible.