Database Info

[Q] [HELP] Nexus S Drivers? I9020T Wind Mobile

I am trying to root my Nexus S. Actually, I'm trying to play around with the ADP developer terminal but I can't seem to get my drivers working. I even called Samsung but they told me they're supposed to not be installed (sigh).
It says that the drivers for Nexus S are missing
it also says the drivers for Android 1.0 are missing
I tried to install the Android 1.0 drivers manually through device manager (I am using Windows 7 64). I have the latest version of the android SDK installed along with the Google USB Driver package, revision 4
I navigate to C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver but windows just says,
"Windows was unable to install your Android 1.0
Windows could not find driver software for your device.
If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
I checked the directory myself and it has a few files in it
android_winusb.inf
androidwinusb86.cat
androidwinusba64.cat
source.properties
Does anyone know what is going on and how I fix this?

Never mind, it just worked.
I right clicked the item in device manager and went to "scan for hardware changes" and then went to properties and navigated to the driver tab and went update driver and put in the directory again except this time with a trailing backslash and it worked.
I also rebooted the phone into regular mode instead of the power button + volume up boot loader.
I'm not sure which of those things made it work since I know I did the scan for hardware changes and properties / update driver thing several times without it working before.
*shrugs*
Thanks

WAIT!!
I spoke too soon. Apparently, when I boot it back into the bootloader (power button + volume up) it changes back to Android 1.0 and says it is missing drivers. Once again it will not let me install the drivers no matter what I try.
Even though I successfully installed the driver in regular mode, now it says the driver can't be found and there's nothing I can do about it.
Please help!

Aro2220 said:
WAIT!!
I spoke too soon. Apparently, when I boot it back into the bootloader (power button + volume up) it changes back to Android 1.0 and says it is missing drivers. Once again it will not let me install the drivers no matter what I try.
Even though I successfully installed the driver in regular mode, now it says the driver can't be found and there's nothing I can do about it.
Please help!
Click to expand...
Click to collapse
uninstall what you installed, then go to PDAnets' website http://junefabrics.com/android/ download the free installer. then start the program, follow the on-screen instructions, and let it install the drivers for you.

"Install to phone failed
Installer fail to open device"
When I go into windows device manager it shows up as Android ADB Interface on my computer...even when in the boot loader.
But if I try adb devices it doesn't list it as a connected device.

Aro2220 said:
Install to phone failed
Installer fail to open device
Click to expand...
Click to collapse
did you go to the phones main settings, applications, development.. and enable usb/android debugging?

Yes, I did that originally before I started having any of these problems.
When the phone is booted normally I can adb devices and it shows up. I can connect to it as well with adb shell and see all my files.
Then, I power down my phone and boot it back up holding the volume up and power button.
Now I am on the FASTBOOT MODE screen:
Code:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKF1
CARRIER INFO - TMB
SERIAL NUMBER - 12345ETC
LOCK STATE - LOCKED
SELECT - VOL UP or VOL DOWN
EXECUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
Now I adb devices and nothing is there.

Aro2220 said:
Yes, I did that originally before I started having any of these problems.
When the phone is booted normally I can adb devices and it shows up. I can connect to it as well with adb shell and see all my files.
Then, I power down my phone and boot it back up holding the volume up and power button.
Now I am on the FASTBOOT MODE screen:
Code:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKF1
CARRIER INFO - TMB
SERIAL NUMBER - 12345ETC
LOCK STATE - LOCKED
SELECT - VOL UP or VOL DOWN
EXECUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
Now I adb devices and nothing is there.
Click to expand...
Click to collapse
do a fastboot devices

Might be because you can't use adb in fastboot.
Sent from my Nexus S MV from the XDA Premium app.

Fastboot devices found my device. I was able to unlock it and follow the instructions on http://forum.xda-developers.com/showthread.php?t=895545
But I run into a problem whenever I enter the recovery mode. It just gives me the android with the exclamation mark in a triangle symbolizing that something went wrong.
EDIT: I think I didn't know how to use the recovery module. If you press volume up then power then let go of power or something like that it shows you some command options at the top of the screen.
But I realized that wasn't clockwork and after doing some reading I think when I rebooted the phone it auto-flashed the recovery module back to the default one.
So I flashed clockwork recovery.img again using the same steps except this time I went straight into the recovery option instead of rebooting my phone and then I saw clockwork.
I followed the rest of the steps from that work and everything seems to be working.
Thanks again ;-)

Aro2220 said:
Fastboot devices found my device. I was able to unlock it and follow the instructions on http://forum.xda-developers.com/showthread.php?t=895545
But I run into a problem whenever I enter the recovery mode. It just gives me the android with the exclamation mark in a triangle symbolizing that something went wrong.
Any ideas?
Click to expand...
Click to collapse
fastboot a custom recovery like clockwork or twrp. then flash whatever rooted rom(and gapps) you plan on flashing.

Go To The Link From Your PC and Click the Box Within The YouTube video. Watch the video and in description should be a download link named NexusRootNew
http://m.youtube.com/#/watch?deskto...e.com/watch?v=xwe4sWH67dk&v=xwe4sWH67dk&gl=US
Download it
Extract it
Place into C Drive
Within the file are the drivers, Recovery and superuser
Just follow the Video and u should be ok
Sent from my Nexus S using xda premium

[Q] Nexus S not appearing in device manager in fastboot

I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?

stoo said:
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
Click to expand...
Click to collapse
in the main setting, application, developer settings.. is usb debugging enabled?

stoo said:
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
Click to expand...
Click to collapse
When I first set up ADB and Fastboot on my pc, I was getting a response when writing 'adb devices' in the console. However, 'fastboot devices' returned absolutely nothing.
Solution (with phone connected to pc and usb debugging cheched):
1-shut down the phone
2-press and hold Volume Up key + Power
3-once in bootloader interface, in the pc command prompt, type 'fastboot devices'.
Voila!
By the way, don't mount the phone as usb storage device.

Thanks for the responses guys but yes, USB debugging is enabled and yes, I've used that way to get to fastboot mode as well as adb reboot bootloader

Hi stoo
I have a same issue - did you managed to find solution for yours?
Cheers,
Wiktor

vstar said:
Hi stoo
I have a same issue - did you managed to find solution for yours?
Cheers,
Wiktor
Click to expand...
Click to collapse
easy way to set up fastboot

Any solution
Have the same problem: locked bootloader, not rooted 4.1.2. In ADB everything is ok, drivers ok (in device manager), can get it through "adb devices". But when I boot in fastboot (adb reboot bootloader), I hear the ti-da windows sound (usb unpluged - from adb session), but no ta-di when the phone re-boot in fastboot. No exclamation mark in device manager, nothing. The USB receive nothing when in fastboot. Is it possible that the fastboot image is corrupted? Can I reflash it? Or any other advice?
Thanks
EDIT - SOLVED - at least this step
The problem was the famous "broken power button"! I knew that I had problems with the power button (didn't work - that's why I try to flash a rom (4.2.1 or customized) with sleep tile in notification area).
I thought that the button is all the time OFF and don't switch to ON, but I finally understood that when when I boot in fastmode it freeze before installing device on the PC (I also had no volume up / down navigation in fastboot, a sign that it was frozen). So I ended to consider that the power button was permanently in ON position. I opened my phone and I measure the impedance on the power button. I had ~ 4ohms in off position of the button and 1.8 ohms (cheap multimetter.... probably should be almost 0) in on position. I measured also on volume switch where I had ~ infinite on off position, so I concluded that the button if blocked. I tried to see if I can resurrect it but no choice, so I took it off (unsoldered). I put the battery and the USB cable and boot it. From ADB I reboot it in fastboot and voila! The device popped in device manager! One problem solved! BUT...
I tried to use the Nexus Root Toolkit and it boots in fastmode and try to unlock the bootloader, but it asked me on phone screen if I agree for unlocking. I was able to use the volume to select Yes but I couldn't choose it with power! I had no option but to take the battery off. Starting from that point it was almost impossible to power it again. When I plugged the USB it shown the battery icon (charging). I tried every trick that I found on web, but nothing worked (even to fast plug / unplug many times the USB to overcharge it, but nothing). I was able only by pressing on the middle of volume (so Up and DOWN in the same time) and plus the USB to get to the screen of unlocking bootloader, but without the options YES/NO on the screen. Seems that it saves this state between boots, but why no option? Finally I was unable to boot at all, and it is like totally bricked
I thought that the power button is a simple switch ON / OFF, so I soldered 2 wires and I tried to touch them (short circuit) to simulate the ON, but nothing happened. Is it the button more complex that a simple switch? no ideea...
So now have a better phone than before (at least theoretically it should be able to fastboot), but it values zero because I can't power it on....

OK So I am in the exact same situation.
Nexus S, Broken power button, adb can see the device, fastboot cannot. fastboot cannot be navigated with the volume keys.
I also want to put an other rom onto it, but firstly I want to put TWRP recovery on it, as it supports touch, CW needs the power
button which like mentioned does not work.
I would rather not unsolder my power button to get into fastboot, any suggestions on how that might still be achieved?
thx
catalinu said:
Have the same problem: locked bootloader, not rooted 4.1.2. In ADB everything is ok, drivers ok (in device manager), can get it through "adb devices". But when I boot in fastboot (adb reboot bootloader), I hear the ti-da windows sound (usb unpluged - from adb session), but no ta-di when the phone re-boot in fastboot. No exclamation mark in device manager, nothing. The USB receive nothing when in fastboot. Is it possible that the fastboot image is corrupted? Can I reflash it? Or any other advice?
Thanks
EDIT - SOLVED - at least this step
The problem was the famous "broken power button"! I knew that I had problems with the power button (didn't work - that's why I try to flash a rom (4.2.1 or customized) with sleep tile in notification area).
I thought that the button is all the time OFF and don't switch to ON, but I finally understood that when when I boot in fastmode it freeze before installing device on the PC (I also had no volume up / down navigation in fastboot, a sign that it was frozen). So I ended to consider that the power button was permanently in ON position. I opened my phone and I measure the impedance on the power button. I had ~ 4ohms in off position of the button and 1.8 ohms (cheap multimetter.... probably should be almost 0) in on position. I measured also on volume switch where I had ~ infinite on off position, so I concluded that the button if blocked. I tried to see if I can resurrect it but no choice, so I took it off (unsoldered). I put the battery and the USB cable and boot it. From ADB I reboot it in fastboot and voila! The device popped in device manager! One problem solved! BUT...
I tried to use the Nexus Root Toolkit and it boots in fastmode and try to unlock the bootloader, but it asked me on phone screen if I agree for unlocking. I was able to use the volume to select Yes but I couldn't choose it with power! I had no option but to take the battery off. Starting from that point it was almost impossible to power it again. When I plugged the USB it shown the battery icon (charging). I tried every trick that I found on web, but nothing worked (even to fast plug / unplug many times the USB to overcharge it, but nothing). I was able only by pressing on the middle of volume (so Up and DOWN in the same time) and plus the USB to get to the screen of unlocking bootloader, but without the options YES/NO on the screen. Seems that it saves this state between boots, but why no option? Finally I was unable to boot at all, and it is like totally bricked
I thought that the power button is a simple switch ON / OFF, so I soldered 2 wires and I tried to touch them (short circuit) to simulate the ON, but nothing happened. Is it the button more complex that a simple switch? no ideea...
So now have a better phone than before (at least theoretically it should be able to fastboot), but it values zero because I can't power it on....
Click to expand...
Click to collapse

Yes, it should have been better for me to have also a possibility to enter in fastboot with the power button blocked in ON position, but I didn't find. And now I know no way how to power it up...

fastboot drivers
http://www.samsung.com/us/support/owners/product/GT-I9020PWAATT#
has anybody considered using this executable from samsung ..
from what i understood when installing it ,it only unzips the contents at programfiles/Samsung/drivers
then you can check this thread to install them spesifically http://forum.xda-developers.com/showthread.php?t=1901617
..In short.
Go to
"Device Manager"
find
"Android 1.0" or something like that (i had my device in fastboot/bootloader mode, dont know if it was necessary)
install drivers from the drivers directory and install
P.S. Mine is an ordinary 9023nexus s (slcd) though
be a bit more careful with nexus s4g

[Completed] fastboot does not accept command / recovery no command problem

Hello.I have a Gigaset qv1030 with Nvidia Tegra 4 cpu.
The main idea is that i cannot enter the android due to not knowing the password.So i ''tried'' to went to recovery for a fresh wipe/factory reset.Problem is no key combination does start up recovery.
Power+volume up does only power up the tablet / Power volume down does nothing and freezes the tablet (need to hold power for it to resests).
Only thing that does work however is if i press Volume up and power , after first vibration pressing volume down (with all 3 button now pressed) goes me into bootloader (says Unlocked) , and have the following options continue , reboot , fastboot protocol , recovery kernel , power off.
Fastboot protocol only restarts the tablet at the same point back into the bootloader (useless i guess)
Recovery kernel brings up an green android sitting on it's back with a red triangle saying no command. (tried every combination found , nothing seems to work)
Adb debugging is not set up in the settings i guess , and fastboot does appear in device manager if connected to a PC but it just does not accept any drivers (neither the modified google_usb drivers with tegra enabled , neither some found on the internet trough drivescape).So no device is found by the PC .
I did however finally installed the drivers using the drivescape driver with extracting driver , restarting with no driver signature and installing the driver using device manager update driver.Fastboot still does not see the tablet.
Connecting it while on the password screen, PC does recognize the tablet but that's it . No adb recognition.
This is as far as i got , idk what to do . Please help?
# PS yes i did not own the tablet , i got scammed by someone , and hoped to do the best out of the situation.
i think it is android 4.2

Duplicate, Please see my response from here:
http://forum.xda-developers.com/general/xda-assist/recovery-command-t3519232
Closed.

Neffos X-1 stuck in bootloop

Heya folks,
I have just attempted my first time flashing TWRP on my TP-Link Neffos X-1 following this guide: https://rootmygalaxy.net/twrp-root-...nd_Install_TWRP_Recovery_On_TP-Link_Neffos_X1.
Its looking kinda grim. It starts with the orange state Message and that the device will boot in 5 seconds, however after that it starts with an infinite bootloop. I also cannot access the Recovery (vol up + power), for it simply doesnt work anymore after the guide. When I plug it into my pc, it will automatically start with the bootloop (I can shut the phone off with vol down + power).
Attempting to get into fastboot mode over ADB (adb reboot bootloader), returns with the message error: device '(null)' not found. I think that is due to it not being recognized in the device manager(it doesnt show my phone anymore but unknown device). I tried to install the phone driver for the uknown device, however that keeps failing. I think its due to the phone permanently connecting and reconnecting to the pc.
So I'm wondering of what to do. I guess the biggest issue is that the drivers are not recognized, but as long as the phone keeps on restarting every couple of seconds i doubt i can properly install the driver. You guys got any ideas?

My guess is you haven't installed on Windows PC the appropriate Android USB Driver matching the device

I mean the appropriate USB driver had to be there for me to flash it with the TWRP in the first place, right?

Think I clearly said that the additionally required USB-driver has to be installed on Windows PC.

I have this one installed https://rootmydevice.com/download-neffos-usb-drivers/, is this the additionally required usb driver?

So far, despite what driver I pick for the device, it shows the code 10, device couldnt be started - probably because it never gets past the starting screen but keeps rebooting

slayingduck said:
Heya folks,
I have just attempted my first time flashing TWRP on my TP-Link Neffos X-1 following this guide: https://rootmygalaxy.net/twrp-root-...nd_Install_TWRP_Recovery_On_TP-Link_Neffos_X1.
Its looking kinda grim. It starts with the orange state Message and that the device will boot in 5 seconds, however after that it starts with an infinite bootloop. I also cannot access the Recovery (vol up + power), for it simply doesnt work anymore after the guide. When I plug it into my pc, it will automatically start with the bootloop (I can shut the phone off with vol down + power).
Attempting to get into fastboot mode over ADB (adb reboot bootloader), returns with the message error: device '(null)' not found. I think that is due to it not being recognized in the device manager(it doesnt show my phone anymore but unknown device). I tried to install the phone driver for the uknown device, however that keeps failing. I think its due to the phone permanently connecting and reconnecting to the pc.
So I'm wondering of what to do. I guess the biggest issue is that the drivers are not recognized, but as long as the phone keeps on restarting every couple of seconds i doubt i can properly install the driver. You guys got any ideas?
Click to expand...
Click to collapse
Try this TWRP file: TWRP_3.2.3_NeffosX1_TP902A_by_kiruha_21.img

The thing is, I cannot flash anything due to my phone constantly rebooting while inserted in the pc usb-slot. Neither ADB nor my device manager recognize the device and as mentioned before, I cannot install any drivers

slayingduck said:
The thing is, I cannot flash anything due to my phone constantly rebooting while inserted in the pc usb-slot. Neither ADB nor my device manager recognize the device and as mentioned before, I cannot install any drivers
Click to expand...
Click to collapse
Some MTK devices has this: Press both VOL+ & Power buttons. Only remove 2 buttons when you see Bootloader mode (recovery; fastboot; reboot system) or directly in the Recovery mode. Now you can use fastboot.
With the SPFT you can use same tip above. In the SPFT choose DOWNLOAD and plug USB device. Process to flash stock ROM or stock recovery.img & boot.img start.
If not start pugging USB: choose DOWNLOAD - press VOL- and plug USV device. You can try with buttons like only VOL- or VOL+ or combo buttons VOL+&VOL- or VOL-&VOL+ or other button combination.
You can try FIRMWARE UPGRADE too.
That's depend about LOCKED or Unlocked bootloader process that you made before actions!
If you unlocked bootloader so only need patience. If not so that's no good.

Not able to power off phone no matter what

Hi all!
Long story short, basically my OnePlus Nord gen 1 is bricked (no recovery, no ROM). In the current state all it is able to do is boot into the bootloader. The bootloader gives several 'options' such as "boot to recovery", and more importantly, "power off". But no matter what option I choose, the phone ends up rebooting back into the bootloader.
I've tried to follow guides on XDA instructing how to unbrick the device, to no avail. The main guide I'm trying to follow is the MSMdownloadTool guide, but that requires me to power off the device to enter EDL mode (which it isn't doing).
The device seems to be stuck in fast boot mode, but isn't using fastbootd so I can't make changes to critical partitions. Since it is stuck in fastboot mode, adb commands don't work. I've tried reflashing the recovery, but that didn't work. I've tried clearing cache but there I'm running into 'cannot generate userdata' (fastboot erase cache spat out "failed; check device logs").
As for hardware buttons, using volume down + volume up or even volume down+power does nothing, volume up + power button or holding all 3 just restarts the bootloader, and holding just the power button does nothing except for repeatedly select "start"(causing it to reboot back into bootloader).
I feel if I can just get it into EDL mode somehow, everything else will fall into place. Any help at all will be much appreciated

zeuses23 said:
Hi all!
Long story short, basically my OnePlus Nord gen 1 is bricked (no recovery, no ROM). In the current state all it is able to do is boot into the bootloader. The bootloader gives several 'options' such as "boot to recovery", and more importantly, "power off". But no matter what option I choose, the phone ends up rebooting back into the bootloader.
I've tried to follow guides on XDA instructing how to unbrick the device, to no avail. The main guide I'm trying to follow is the MSMdownloadTool guide, but that requires me to power off the device to enter EDL mode (which it isn't doing).
The device seems to be stuck in fast boot mode, but isn't using fastbootd so I can't make changes to critical partitions. Since it is stuck in fastboot mode, adb commands don't work. I've tried reflashing the recovery, but that didn't work. I've tried clearing cache but there I'm running into 'cannot generate userdata' (fastboot erase cache spat out "failed; check device logs").
As for hardware buttons, using volume down + volume up or even volume down+power does nothing, volume up + power button or holding all 3 just restarts the bootloader, and holding just the power button does nothing except for repeatedly select "start"(causing it to reboot back into bootloader).
I feel if I can just get it into EDL mode somehow, everything else will fall into place. Any help at all will be much appreciated
Click to expand...
Click to collapse
You might be able to enter EDL mode by opening the device and using a jumper to touch certain contact points on the board and force it into EDL mode. I don't know your hardware so I don't know which points to tell you to use the jumper on, you'll have to do some research to figure that out based on the specific device you have.

zeuses23 said:
The device seems to be stuck in fastboot mode, but isn't using fastbootd so I can't make changes to critical partitions.
Click to expand...
Click to collapse
unrelated. you can flash super.img from fastboot. flashing critical partitions maybe needs unlocking.

Hello if this can help my device was dead , not even fastboot or recovery was working and was bootlooping. What i did is installing MTK authentication bypass ( i dont know if your phone is mtk cpu ) , then i instaled libUsb driver that came packed with that tool.
Then you open libusb driver installer, and when you keep pressed power + vol down to enter Brom mode, it should detect a com port that disappear in few seconds, what u need to do is click install driver as soon you see that com port appear.
Now you open the bypass tool with phone disconnected, click on bypass, and then connect the cable, now enter Brom mode with power + vol down, and the tool will say Success.
Now your phone is ready to use with any flash tool ,like sptools.
Hope this helps.

Droidriven said:
You might be able to enter EDL mode by opening the device and using a jumper to touch certain contact points on the board and force it into EDL mode. I don't know your hardware so I don't know which points to tell you to use the jumper on, you'll have to do some research to figure that out based on the specific device you have.
Click to expand...
Click to collapse
Hey, thanks for the suggestion! But i would very much prefer not to open up my device. I've also heard that there is an EDL cable, but I don't know if that'll work either. Lets see
aIecxs:
unrelated. you can flash super.img from fastboot. flashing critical partitions maybe needs unlocking.
Click to expand...
Click to collapse
Thanks for your reply! A silly question, but what does super.img do? I tried flashing the critical partitions after running "fastboot oem unlock_critical", but that still gave me the error.
innergat:
Hello if this can help my device was dead , not even fastboot or recovery was working and was bootlooping. What i did is installing MTK authentication bypass ( i dont know if your phone is mtk cpu ) , then i instaled libUsb driver that came packed with that tool.
Then you open libusb driver installer, and when you keep pressed power + vol down to enter Brom mode, it should detect a com port that disappear in few seconds, what u need to do is click install driver as soon you see that com port appear.
Now you open the bypass tool with phone disconnected, click on bypass, and then connect the cable, now enter Brom mode with power + vol down, and the tool will say Success.
Now your phone is ready to use with any flash tool ,like sptools.
Hope this helps.
Click to expand...
Click to collapse
Hey innergat, unfortunately I believe my phone has a qualcomm chipset, so this probably won't work

Dynamic partitions are logical partitions hosted in physical super partition. logical partitions can only be accessed from fastbootd, physical partitions from fastboot.

To enter EDL mode try selecting power off and then immediately hold volume up + volume down.