Database Info

[HOWTO] Root Stock i9505G (any version)

This was done on a stock rom (works for 4.4)
I unlocked my bootloader first
http://forum.xda-developers.com/showthread.php?t=2363025&page=1
(you need to do the driver part for adb) (Windows 8 may need to change the "Samsung device", and set the driver to be "Android Bootloader Interface")
if you get a "error: device not found" your drivers are not setup, or you didn't accept the cert on the phone.
Thanks broodplank1337
Download root from
http://download.chainfire.eu/supersu
or for more info read here
http://forum.xda-developers.com/showthread.php?t=1538053
and put it in "C:\adb\sdk\platform-tools" (this is my adb.exe folder)
Download the "Samsung Galaxy S4 (i9505) / Download Recovery" from below
http://www.clockworkmod.com/rommanager
save the recovery-clockwork-6.0.4.4-jfltexx.img to the folder "C:\adb\sdk\platform-tools"
Now open up a command prompt (I did this as "run as administrator")
type "cd C:\adb\sdk\platform-tools" (or what ever the directory you extract your files)
enter this command
adb reboot bootloader <enter>
(or hold vol+/- while booting)
Once in bootloader,
In the command prompt type:
fastboot boot recovery-clockwork-6.0.4.4-jfltexx.img (this takes 1min to load after the file is sent)
This will boot into ClockworkMod
goto "install zip"
goto "install zip from sideload"
in the cmd type
adb sideload UPDATE-SuperSU-v1.80.zip
This sends to the phone and write to the phones Rom.
Now reboot, if asked, select no about the stock recovery overwriting the phone
when you boot into the OS download SuperSu from the market
and we have root without ODIN on a I9505G
I disappear alot and i DON'T read everyone's post
I update this when i need re-root
Sorry for the errors in this post
1. I still receive OTA Update with this root (I had to "clear data" on the "Google Service Framework" and then check for updates).
2. As long as you don't flash a different recover it should allow you to apply new updates. The first time i applied a update it failed half way though it. My phone booted but i could install any apps. It only worked after i put the recovery back and re-updated.
3. Once you have root you can flash a recovery using DD in the shell (backup the recovery first) read "[HOWTO] dump your rom"

Good job on writing this for the i9505g users ^^. I'm glad my root zip worked! hehe

:3
Good one! :good:
btw....
Download ClockworkMod 6.0.3.3 NORMAL from below
http://forum.xda-developers.com/show...light=recovery
aka Miustone_CWM_flash-NORMAL.zip
extract the recovery.img to the folder "C:\adb\sdk\platform-tools"
Click to expand...
Click to collapse
your link is not working... this LINK here is working

hey thanks!!
will give it a try tonight!

Will this work on 4.3?
Sent from my GT-I9505G using xda premium

Attempting to do this and for the life of me I can not get adb sideload to work correctly.
when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.
I want to get this working so that I can root my device and make a backup of my stock images since I just got the 4.3 OTA. When I first got the phone I managed to flash TWRP on it and then put the SU file on the internal memory and flash it from there but I want to get a backup of the stock recovery before going that route in case there is a 4.4 update at a later point.
So could anyone please tell me what I am doing wrong. When my phone is in recovery my computer sees it but adb doesn't.
I am using windows 7 and (I believe) the latest tools from google. I got them right after I got the GES4 so they are at most a month old.

ChaoticUnreality said:
when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.
Click to expand...
Click to collapse
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."

Chahk said:
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Click to expand...
Click to collapse
I'll have to try that when I get home. thanks.

ChaoticUnreality said:
I'll have to try that when I get home. thanks.
Click to expand...
Click to collapse
Another quick trick that has worked for me in the past is to simply plug the cable into a different USB port on the computer. Does the same thing as the other suggestion without going through the extra steps. Either way should resolve your problem.

Finally got a chance to try this worked perfectly once I changed USB ports and redid the drivers. Thanks

Great write-up
This was my first ever root on my first ever Android device. It went well.
There were a couple things confusing about the post, I just want to make sure I did things correctly.
]Link to Brood's unlocking the bootloader - Was that just to get the USB drivers installed? I didn't use that Clockworkmod or root.zip file
Not selecting yes on final reboot - With so many "no's", I thought it best to not say yes. Does that mean that if there's another OTA update, root will be lost and have to be redone?
Besides that, the biggest issue was getting good USB drivers. Visiting the Samsung site shows zero downloads for the i9505G phone, so I ended up getting the drivers from "phones-usb-drivers.blogspot.com" (can't post links yet), search Google for "free-download-samsung-gt-i9505g-galaxy", it should be a top hit. The actual download was from Samsung, and that got the drivers working for regular operation and the bootloader.
However, I couldn't find drivers that worked for the sideload of the SuperSU. Ended up having to add entries to the Google USB driver (android_winusb.inf) with the VID and PID values. Here's what I added to the x64 section, in case it helps someone else out:
Code:
;Samsung i9505G (GAA attempt to get adb drivers working)
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
At that point when it booted into CWM recovery, I installed the drivers and was able to complete.
Now the happy owner of SuperSU running phone. Thanks again warwolfx0

I hope no one minds, but, I automated this.
<see new version later in thread>
Download that, extract it to a folder, install Koush's universal ADB driver in the ADB_USB folder, and then execute the run.bat and follow instructions.
Credits:
warwolfx0 for the OP
Koush for the universal ADB driver found here: https://github.com/koush/UniversalAdbDriver

warwolfx0 said:
Now reboot, if asked, select no about the stock recovery overwriting the phone
and we have root without ODIN on a I9505G
Click to expand...
Click to collapse
Sorry for what might be a stupid question, but I was not 100% sure based on how you word this.
So, if we follow your method, will we leave stock google recovery intact? I.e. we aren't overwriting it with cwm recovery? If so, that would be nice. All my other rooted devices I've installed custom recovery, but it would be nice to leave this one 100% stock except for the rooting.
Thanks.

Correct.
Etched in blood by a katana

Chahk said:
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Click to expand...
Click to collapse
I had the same problem but was able to get it working by following the above instructions but then selecting “SAMSUNG Android Phone,” followed by “SAMSUNG Android ADB Interface." (I didn't have an option for "SAMSUNG Mobile USB Composite Device.")

I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan

carrot34 said:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
Click to expand...
Click to collapse
Yes.

carrot34 said:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
Click to expand...
Click to collapse
SamuriHL said:
Yes.
Click to expand...
Click to collapse
I don't have the 9505G yet (couple more days!), but there was a similar issue/discussion on the Nexus 7 board recently, and it was determined that if you were using SuperSU versions prior to 1.55 (which just came out in like the last 24 hours), the root would indeed block OTA's (because of an immutable system flag which was being inadvertently/unnecessarily set by the root process).
Discussion here.
But again, SuperSU 1.55 which just came out fixes the problem, so OTA's will indeed work again. So if you ever get stuck with an OTA, make sure to update SuperSU to latest first.
This is all assuming that the same issue would have presented itself on 9505G, which I would think it might. If not, then ignore this post.

Apparently we also have a device specific Odin flashable auto-root file.
The link below goes to ChainFire's website. The zip includes a version of odin.
http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip

occupational_hazard said:
Apparently we also have a device specific Odin flashable auto-root file.
The link below goes to ChainFire's website. The zip includes a version of odin.
http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip
Click to expand...
Click to collapse
We do. I got to test it yesterday and it works great. Restores the proper stock recovery when finished.
Sent from my Xoom using Tapatalk 4

[Q] Help!! ADB not recognizing my nexus 5!!

I have installed the universal drivers for adb and still nothing what can I do to fix this?

GhostSoldier_US said:
I have installed the universal drivers for adb and still nothing what can I do to fix this?
Click to expand...
Click to collapse
Read this http://forum.xda-developers.com/showthread.php?t=2514396
Sent from my Nexus 5 using Tapatalk

Try this: http://forum.xda-developers.com/showthread.php?t=2588979

Mr hOaX said:
Read this http://forum.xda-developers.com/showthread.php?t=2514396
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Still nothing

Chromium_ said:
Try this: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Still nothing with this too

GhostSoldier_US said:
Still nothing with this too
Click to expand...
Click to collapse
i am sure you are missing something
are you on window 8/8.1??

samersh72 said:
i am sure you are missing something
are you on window 8/8.1??
Click to expand...
Click to collapse
Windows 8.1

GhostSoldier_US said:
Windows 8.1
Click to expand...
Click to collapse
please follow this:
1) uninstall driver
2) From the Window 8.1 Start screen, move your mouse to the top (or bottom) right corner, and click Settings;
3) Click "Change PC Settings";
4) click Update and Recovery;
5) Under Advanced startup, click "Restart Now";
6) Wait for it to restart;
7) Click "Troubleshoot";
8) Click "Advanced options";
9) Click "Startup settings";
10) Click "Restart";
11) Wait for it to restart;
12) Press F7 (i.e, the F7 function key);
Now you can install the driver.

samersh72 said:
please follow this:
1) uninstall driver
2) From the Window 8.1 Start screen, move your mouse to the top (or bottom) right corner, and click Settings;
3) Click "Change PC Settings";
4) click Update and Recovery;
5) Under Advanced startup, click "Restart Now";
6) Wait for it to restart;
7) Click "Troubleshoot";
8) Click "Advanced options";
9) Click "Startup settings";
10) Click "Restart";
11) Wait for it to restart;
12) Press F7 (i.e, the F7 function key);
Now you can install the driver.
Click to expand...
Click to collapse
What was suppose to happen when I press F7? I pressed it and nothing happened. I tried adb devices and its still not showing up and I tried the back up and still nodda

GhostSoldier_US said:
What was suppose to happen when I press F7? I pressed it and nothing happened. I tried adb devices and its still not showing up and I tried the back up and still nodda
Click to expand...
Click to collapse
did you re-install the driver at the end??
restart your pc
connect your N5
i want you to download attached zip, unzipp it, and open a cmd (shift + right click) in it and type
Code:
adb devices
look at your device screen to allow adb
please be sure before that "usb debug" is enabled from developer options.
please try other usb cable or other usb port

samersh72 said:
did you re-install the driver at the end??
restart your pc
connect your N5
i want you to download attached zip, unzipp it, and open a cmd (shift + right click) in it and type
Code:
adb devices
look at your device screen to allow adb
please be sure before that "usb debug" is enabled from developer options.
please try other usb cable or other usb port
Click to expand...
Click to collapse
Still nothing i've tried 3 cables 6 usb ports

Hello m8!
I want you to try this on Windows 8.1 step by step:
1. Download and install Android SDK and make sure you have downloaded the latest USB Driver from SDK Manager.
2. Now connect your nexus 5 to your windows pc and open Device Manager (Control Panel -- Device Manager)
3, Now select your nexus 5 (it will be displayed as usb mobile or some random name). Right click and click on "Update driver software"
4. Now on the next screen select "Browse my computer for driver software" and navigate to "xxxx/Android\android-sdk\extras\google\usb_driver" (xx being the path where you've installed the SDK).
5. Put a tick on "Include sub folders" and hit next.
Driver will be installed again successfully and you will be able to use adb commands!
If not, disconnect your device. Go to settings-developer options and select "Revoke USB Debugging authorization". Now again connect your Nexus 5 to your PC and accept the Authorization message you will get.
I'm sure this will work.

GhostSoldier_US said:
Still nothing i've tried 3 cables 6 usb ports
Click to expand...
Click to collapse
weird!
i guess the problem is in window 8.1
you must Disable Driver Signature Enforcement first
see here for a fix http://forum.xda-developers.com/showpost.php?p=49985898&postcount=139
and here for driver http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875

vin4yak said:
Hello m8!
I want you to try this on Windows 8.1 step by step:
1. Download and install Android SDK and make sure you have downloaded the latest USB Driver from SDK Manager.
2. Now connect your nexus 5 to your windows pc and open Device Manager (Control Panel -- Device Manager)
3, Now select your nexus 5 (it will be displayed as usb mobile or some random name). Right click and click on "Update driver software"
4. Now on the next screen select "Browse my computer for driver software" and navigate to "xxxx/Android\android-sdk\extras\google\usb_driver" (xx being the path where you've installed the SDK).
5. Put a tick on "Include sub folders" and hit next.
Driver will be installed again successfully and you will be able to use adb commands!
If not, disconnect your device. Go to settings-developer options and select "Revoke USB Debugging authorization". Now again connect your Nexus 5 to your PC and accept the Authorization message you will get.
I'm sure this will work.
Click to expand...
Click to collapse
Nothing

samersh72 said:
weird!
i guess the problem is in window 8.1
you must Disable Driver Signature Enforcement first
see here for a fix http://forum.xda-developers.com/showpost.php?p=49985898&postcount=139
and here for driver http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875
Click to expand...
Click to collapse
I'm about to just give up... Still nothing.

GhostSoldier_US said:
I'm about to just give up... Still nothing.
Click to expand...
Click to collapse
there is something wrong!
any way, try another pc.

samersh72 said:
there is something wrong!
any way, try another pc.
Click to expand...
Click to collapse
1 step ahead of you. I tried a win7 pc and still nothing could something be wrong with my n5?

GhostSoldier_US said:
1 step ahead of you. I tried a win7 pc and still nothing could something be wrong with my n5?
Click to expand...
Click to collapse
if you connect you phone without usb debug, i guess the pc make a sound, when connected, enable usb debuug, do you hear a sound from pc?

samersh72 said:
if you connect you phone without usb debug, i guess the pc make a sound, when connected, enable usb debuug, do you hear a sound from pc?
Click to expand...
Click to collapse
I do hear the noise while in debug mode

GhostSoldier_US said:
I do hear the noise while in debug mode
Click to expand...
Click to collapse
i guess the devices is ok.
i dont know where you are missing something.

[Q] USB Problem (searched everywhere)

Since the last windows update from this week windows cant detect my nexus 5. I tried everything. It keeps showing up like "Unknown USB Device (Device Descriptor Request Failed)" And i doesn't show up immediately when i plug in the phone. It takes like 10 seconds, then it shows that with a yellow triangle.
Hope that someone can help me. There is also a thread on Reddit (/r/Nexus5) about this.

hhamzah49 said:
Since the last windows update from this week windows cant detect my nexus 5. I tried everything. It keeps showing up like "Unknown USB Device (Device Descriptor Request Failed)" And i doesn't show up immediately when i plug in the phone. It takes like 10 seconds, then it shows that with a yellow triangle.
Hope that someone can help me. There is also a thread on Reddit (/r/Nexus5) about this.
Click to expand...
Click to collapse
It would help to know what "everything" you have tried.

rootSU said:
It would help to know what "everything" you have tried.
Click to expand...
Click to collapse
uninstall every driver related to android. Uninstall every usb driver. Reinstall everything. Try every sort of install. Install via toolkit. Nothing worked.
I tried other cables, doesnt work. Other computer. On other computers it does work (which arent updated to the latest windows). But the problem isnt something in the hardware because it really started after the update.

none ??

In Device Manager, click on the yellow triangle and then uninstall the driver. Once done unplug the phone and then plug it back in again... Windows should then install the correct driver.
Here's something else to try...
http://androidcowboy.com/2013/11/install-nexus-5-drivers/
If either of those doesn't work you could try a System Restore to a date before the update. Then when Windows update pops up again have a look at what it wants to install to see if you can figure out what caused the problem, then right click and select Hide Update.

hhamzah49 said:
none ??
Click to expand...
Click to collapse
are you on window 8 / 8.1?

samersh72 said:
are you on window 8 / 8.1?
Click to expand...
Click to collapse
8.1 with latest updates
@CitizenLee
already tried that, the problem is that it doesnt recognize it as nexus 5.

hhamzah49 said:
8.1 with latest updates
@CitizenLee
already tried that.
Click to expand...
Click to collapse
uninstall driver and do this:
1) From the Window 8.1 Start screen, move your mouse to the top (or bottom) right corner, and click Settings;
2) Click "Change PC Settings";
3) Click Update and Recovery ;
4) Under Advanced startup, click "Restart Now";
5) Wait for it to restart;
6) Click "Troubleshoot";
7) Click "Advanced options";
8) Click "Startup settings";
9) Click "Restart";
10) Wait for it to restart;
11) Press F7 (i.e, the F7 function key);
Now you can install the driver.

samersh72 said:
uninstall driver and do this:
1) From the Window 8.1 Start screen, move your mouse to the top (or bottom) right corner, and click Settings;
2) Click "Change PC Settings";
3) Click Update and Recovery ;
4) Under Advanced startup, click "Restart Now";
5) Wait for it to restart;
6) Click "Troubleshoot";
7) Click "Advanced options";
8) Click "Startup settings";
9) Click "Restart";
10) Wait for it to restart;
11) Press F7 (i.e, the F7 function key);
Now you can install the driver.
Click to expand...
Click to collapse
Thanks for your quick answer. Didnt help. It still shows up at device manager as "Unknown USB Device (Device Descripter Request Failed)"
If i try to update driver software via device manager it tells me it failed to update with Code 10.
Tried phone on my old laptop with windows 7 and it immediately connected as Nexus 5.

hhamzah49 said:
Thanks for your quick answer. Didnt help. It still shows up at device manager as "Unknown USB Device (Device Descripter Request Failed)"
If i try to update driver software via device manager it tells me it failed to update with Code 10.
Tried phone on my old laptop with windows 7 and it immediately connected as Nexus 5.
Click to expand...
Click to collapse
take a look here:
http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
i suggest Universal Naked Driver http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1

samersh72 said:
take a look here:
http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
i suggest Universal Naked Driver http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
Thanks for your quick answer, doesnt work though. When i choose the extracted Universal Naked Driver it tells me that it already has installed the latest drivers for this device.

hhamzah49 said:
Thanks for your quick answer, doesnt work though. When i choose the extracted Universal Naked Driver it tells me that it already has installed the latest drivers for this device.
Click to expand...
Click to collapse
did you follow steps in mentioned link?
try this also http://forum.xda-developers.com/showthread.php?t=2588979

Here try this:
Make sure android sdk with platform tools and usb_driver is installed on your PC and then,
Follow these steps:
1. Connect your phone to your pc and head over to control panel---device manager and select your phone from there.
2. Right click on it and select update driver software.
3. Now select "Browse my computer for driver software"
4. Put this path "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver" (C:\Program Files (x86) may differ on your pc depending on where you have installed the SDK)
5. Put a tick on "Include subfolders" and click next.
6. The drivers will be installed again and everything should work now.
Make sure you accept the authorization request popup on your device when you connect to your PC.

vin4yak said:
Here try this:
Make sure android sdk with platform tools and usb_driver is installed on your PC and then,
Follow these steps:
1. Connect your phone to your pc and head over to control panel---device manager and select your phone from there.
2. Right click on it and select update driver software.
3. Now select "Browse my computer for driver software"
4. Put this path "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver" (C:\Program Files (x86) may differ on your pc depending on where you have installed the SDK)
5. Put a tick on "Include subfolders" and click next.
6. The drivers will be installed again and everything should work now.
Make sure you accept the authorization request popup on your device when you connect to your PC.
Click to expand...
Click to collapse
samersh72 said:
did you follow steps in mentioned link?
try this also http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Thanks for all your replys, but as i told you, it doesnt show up as anything related to android. it shows up like this: http://imgur.com/a/W3JEO
This problem also comes when i plugin a normal usb device to put files on.

Same happen to me you have to install adp again

hhamzah49 said:
This problem also comes when i plugin a normal usb device to put files on.
Click to expand...
Click to collapse
That, and the fact it works on your old laptop tells me it's most likely a problem with the USB ports or controller on your PC. Do you have your motherboard disk? If so try reinstalling the drivers. Check USB settings in BIOS too.

CitizenLee said:
That, and the fact it works on your old laptop tells me it's most likely a problem with the USB ports or controller on your PC. Do you have your motherboard disk? If so try reinstalling the drivers. Check USB settings in BIOS too.
Click to expand...
Click to collapse
But how come it worked fine just a few days ago

Put it in my USB 3.0 port and it works. Looks like its "fixed".

hhamzah49 said:
Put it in my USB 3.0 port and it works. Looks like its "fixed".
Click to expand...
Click to collapse
I have the same problem, but i dont have USB 3.0 Did you found any other solution ?

hhamzah49 said:
Put it in my USB 3.0 port and it works. Looks like its "fixed".
Click to expand...
Click to collapse
Just like that?
Sent from my Nexus 5 using Tapatalk

Wiped EVERYTHING by Mistake NEED HELP

Accidentally wiped everything using TWRP and have no OS now. Can't use ADB or fastboot as when I boot to it it says device not found. Any suggestions PLEASE?

Is it a driver issue? You have to get the drivers loaded or you may be stuck. What steps have you taken so far.
I had this happen to me as well on another device but I loaded up drivers and then used adb to push files back over on a N4

playya said:
Is it a driver issue? You have to get the drivers loaded or you may be stuck. What steps have you taken so far.
I had this happen to me as well on another device but I loaded up drivers and then used adb to push files back over on a N4
Click to expand...
Click to collapse
Basically all you can do there is re-install the drivers, cause it seems they're non-existent or incorrect.
-reload the drivers [force them perhaps if on win 7]
-connect to pc with phone in fastboot
-in twrp go to advanced > sideload > start process
-add your rom to your adb folder
open a command window in your adb folder [shift + right click for short] then type adb sideload myfile.zip , and the phone will flash the file, and you can reboot.

Nosferatu1923 said:
Accidentally wiped everything using TWRP and have no OS now. Can't use ADB or fastboot as when I boot to it it says device not found. Any suggestions PLEASE?
Click to expand...
Click to collapse
teh roxxorz said:
Basically all you can do there is re-install the drivers, cause it seems they're non-existent or incorrect.
-reload the drivers [force them perhaps if on win 7]
-connect to pc with phone in fastboot
-in twrp go to advanced > sideload > start process
-add your rom to your adb folder
open a command window in your adb folder [shift + right click for short] then type adb sideload myfile.zip , and the phone will flash the file, and you can reboot.
Click to expand...
Click to collapse
I believe above post was meant for you OP
Sent from my A0001 using Tapatalk

I get the error "device not found" in adb shell when I type a command

Hello. As the title says I get that error. I need to run adb shell to use some commands. When I type "adb devices" I don't get any device listed (the long name).
My OS is Windows 8.1 64bit.
Thanks.

KodRoute said:
Hello. As the title says I get that error. I need to run adb shell to use some commands. When I type "adb devices" I don't get any device listed (the long name).
My OS is Windows 8.1 64bit.
Thanks.
Click to expand...
Click to collapse
Whats your device?

LS.xD said:
Whats your device?
Click to expand...
Click to collapse
Nexus 5. In SDK Manager it says that Google USB Drivers are installed. I don't get it. When I use the phone to flash images in fastboot it works perfectly but ADB doesn't work.

KodRoute said:
Nexus 5. In SDK Manager it says that Google USB Drivers are installed. I don't get it. When I use the phone to flash images in fastboot it works perfectly but ADB doesn't work.
Click to expand...
Click to collapse
Try to disable/enable USB debugging again and check if the adb device is listed in your device manager.
You can also try this ADB/fastboot bundle (Includes the google drivers) and work on all folders

LS.xD said:
Try to disable/enable USB debugging again and check if the adb device is listed in your device manager.
You can also try this ADB/fastboot bundle (Includes the google drivers) and work on all folders
Click to expand...
Click to collapse
Yeah after a while I wanted to check if usb debugging was checked and it wasn't. Turns out now works.

KodRoute said:
Yeah after a while I wanted to check if usb debugging was checked and it wasn't. Turns out now works.
Click to expand...
Click to collapse
May you press "thanks" for my posts if i helped you ?!

KodRoute said:
Yeah after a while I wanted to check if usb debugging was checked and it wasn't. Turns out now works.
Click to expand...
Click to collapse
Doh! I hate when that happens. It's always the little things.