Database Info

[Q] Recovery of files

Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated

bahagiga said:
Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated
Click to expand...
Click to collapse
You don't need to boot in recovery, boot in bootloader only.

polobunny said:
You don't need to boot in recovery, boot in bootloader only.
Click to expand...
Click to collapse
I think I might have confused the terms bootloader and recovery mode, what I meant was I press the vol up button and the power button at the same time which then opens the bootloader I guess? anyways, still the same issue for me.

bahagiga said:
I think I might have confused the terms bootloader and recovery mode, what I meant was I press the vol up button and the power button at the same time which then opens the bootloader I guess? anyways, still the same issue for me.
Click to expand...
Click to collapse
Yes that's the bootloader.
Have you installed the ADB drivers? You don't need only the adb and fastboot executable, but also the drivers.
Under Windows, you can install the PDANet software which makes driver installation a breeze on most cases.
http://junefabrics.com/android/

polobunny said:
Yes that's the bootloader.
Have you installed the ADB drivers? You don't need only the adb and fastboot executable, but also the drivers.
Under Windows, you can install the PDANet software which makes driver installation a breeze on most cases.
link
Click to expand...
Click to collapse
Hmm, on the third step where it says "installing pdanet to your phone" it just like freeze and on my phone in the bottom it says "FASTBOOT STATUS - FAILInvalid Command"
what should I do??

bahagiga said:
Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated
Click to expand...
Click to collapse
Can you boot into "recovery" and mount the sd from there?
Sent from my Nexus S 4G using xda premium
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
If you can get to bootloader you should be able to get into recovery. And from there you should be able to mount your sd.
Sent from my Nexus S 4G using xda premium

Bkadleck said:
Can you boot into "recovery" and mount the sd from there?
Sent from my Nexus S 4G using xda premium
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
If you can get to bootloader you should be able to get into recovery. And from there you should be able to mount your sd.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I tried but I dont think I can, when I try it just goes into that 'bootup screen, with the Google text and lock icon'. :/ Not sure what to do

Im still stuck and havent been able to get around this, any helpful information is appreciated. Thanks in advance

Hey guys, Im still stuck with this issue. Anyone who has some tips on what to do or has an idea of what it could be? I just formatted my PC yesterday Windows 7 32bit and everything should be up to date.
Kind regards,
baha

If there's anyone out there I would greatly appreciate your help! I have some pictures that are very valuable to me (pictures of my dog) and would really love to see if I could recover them.
I cannot start up my phone the "normal" way, I can only start up the Fastboot mode. I have the Samsung phone drivers installed along with the Google USB drivers. I have attached a picture that shows that there should be no problems with the drivers. I have tried to use the google usb drivers specifically but still the same. I have also attached a picture of the command prompt and as you can see nothing really happens. I have tried different tutorials and all kinds of ways trying to make it work but I have no clue what the problem is since I am not getting any other error message.
Any help is appreciated, please!
I typed fastboot devices in the cmd prompt and it actually listed a device serial number which matches then one stated on my phone in the fastbootmode. Any idea what to do or what this means?

Device not being detected in recovery mode?

I'm trying to install the 4.4.1 update but my device isn't being detected in recovery mode and thus adb sideload is not working. Would really appreciate some help. I've tried almost every solution that I've googled and nothing seems to be working.

I had a similar issue. Found the naked drivers and they seemed to work after uninstalling the other drivers and rebooting my PC.
Sent from my Nexus 5 using xda app-developers app

jkimbro said:
I had a similar issue. Found the naked drivers and they seemed to work after uninstalling the other drivers and rebooting my PC.
Click to expand...
Click to collapse
Any chance you could post those drivers? Mine works fine, but it would certainly help others if you could post them, or at least post a link to where you found them.

You just need the Google drivers from their website:
http://developer.android.com/sdk/win-usb.html

I had to force the installation of the drivers for the "AOSP on Hammerhead" device in the device manager.
I couldn't even get the device to show until I pressed VolUp in recovery and selected the ADB option in the recovery.
I used USB ADB Composite Interface or something like that by pointing the device manager's Update Driver dialog to the USB drivers from the SDK that EddyOS pointed at.
Windows 7 x64

Yep, had issues with my work PC (Win 7 Pro x64) - had to manually point Device Manager to the android_winusb.inf so it would find the drivers. Bit of a ballache but all working after that!

greenkabbage said:
I couldn't even get the device to show until I pressed VolUp in recovery and selected the ADB option in the recovery.
Click to expand...
Click to collapse
ADB isn't enabled on stock recovery, and sideload is not the same thing. From Google's POV, ADB access on recovery would be a heavy security risk, since you can still access recovery even with your bootloader locked. That's why they created sideloading.
a hammerhead wrote this.

beekay201 said:
ADB isn't enabled on stock recovery, and sideload is not the same thing. From Google's POV, ADB access on recovery would be a heavy security risk, since you can still access recovery even with your bootloader locked. That's why they created sideloading.
Click to expand...
Click to collapse
ADB Server may not be enabled, but ADB obviously is, otherwise you wouldn't be able to connect in order to Sideload, which you can certainly do with stock recovery (even with a locked bootloader). Also, if ADB wasn't available on the device, it wouldn't show up with the "ADB Devices" command.
Now, maybe you mean it's not available once you boot into recovery until you select "apply update from ADB." That may be true (not sure), but that's not what I got from your statement.

jt3 said:
Any chance you could post those drivers? Mine works fine, but it would certainly help others if you could post them, or at least post a link to where you found them.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2513339

jt3 said:
ADB Server may not be enabled, but ADB obviously is, otherwise you wouldn't be able to connect in order to Sideload, which you can certainly do with stock recovery (even with a locked bootloader). Also, if ADB wasn't available on the device, it wouldn't show up with the "ADB Devices" command.
Now, maybe you mean it's not available once you boot into recovery until you select "apply update from ADB." That may be true (not sure), but that's not what I got from your statement.
Click to expand...
Click to collapse
Try it. Select "apply update from ADB", and then try to get a ADB prompt like you would normally, you know, ls /sdcard/, something.

[Q] [HELP]Moto G (4.4.2) USB debugging wont work

Hey guys, i have the following problem.
So I want to unlock the bootloader of my Moto G but to do that I must use USB debugging. But if I use the command "adb devices" it gets always shown as offline. So I did a little research and found out, that since 4.4.2 a Pop-Up should show up to allow USB debugging with the connected PC.
Problem is this Pop-Up won't show up...
Could you please help me. I couldn't find a solution. Really frustating

Have you enabled USB debugging in Developer Options in settings?
Sent from my XT1032 using Tapatalk

Of course I did ^^

battlemaxi said:
Hey guys, i have the following problem.
So I want to unlock the bootloader of my Moto G but to do that I must use USB debugging. But if I use the command "adb devices" it gets always shown as offline. So I did a little research and found out, that since 4.4.2 a Pop-Up should show up to allow USB debugging with the connected PC.
Problem is this Pop-Up won't show up...
Could you please help me. I couldn't find a solution. Really frustating
Click to expand...
Click to collapse
For my XT1031, I had to use the Motorola USB drivers for ADB to work, and Kush's Universal ADB drivers for Fastboot to work.
And if you are using Windows 8/8.1, then you have to disable to forced signature verification in order to install the Universal ADB drivers.
Also, for ADB to work in Windows, I had to set the phone's USB computer connection to Camera (PTP), instead of Media Device.

I'm using Motorolas Drivers. I downloaded them from the official website.
My ADB is also on the latest version (1.0.3.1). Also tried to factory reset my phone. Nothing works, the pop-up wont show up...

battlemaxi said:
I'm using Motorolas Drivers. I downloaded them from the official website.
My ADB is also on the latest version (1.0.3.1). Also tried to factory reset my phone. Nothing works, the pop-up wont show up...
Click to expand...
Click to collapse
Dude, you need to follow the instructions step by step and provide more info about what's going on.
1. Is your "Enable ADB debugging" enabled? You said yes.. does your phone show "Android debugging enabled" icon when you plug it into your computer? If not, you don't have it enabled !
2. If you see the notification, go to Device Manager (hope you are using Windows, or I can't really help you), then can you find your device there? If the USB drivers are installed correctly, then you should see "Android Device" then a "Motorola ADB Interface" inside it. If not, you will see a yellow exclamation with something like "Motorola device"..
3. Did you change your phone's USB computer connection to Camera (PTP)??

If adb says that the device is "offline" but you see its ID, then you didnt authorize (on the phone) the pc to access USB Debugging, its a new feature of 4.4.When you connect your phone, a prompt should appear (check the status bar if it doesnt), saying a computers with RSA Key XX:XX:XX:XX:XX:XX:XX requested access to USB Debugging.
good luck

First of thanks for your help, much appreciated
1. Yes I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated"
2. Yes if I go into the Device Manager I can see Android Device
3. Yes I ded change my USB-Setting to PTP
Any other ideas ?

battlemaxi said:
First of thanks for your help, much appreciated
1. Yes I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated"
2. Yes if I go into the Device Manager I can see Android Device
3. Yes I ded change my USB-Setting to PTP
Any other ideas ?
Click to expand...
Click to collapse
Actually you do not need adb to unlock the bootloader only mfastboot which does not need adb to work all you do is boot into the bootloader then follow this
http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6

liveroy said:
If adb says that the device is "offline" but you see its ID, then you didnt authorize (on the phone) the pc to access USB Debugging, its a new feature of 4.4.When you connect your phone, a prompt should appear (check the status bar if it doesnt), saying a computers with RSA Key XX:XX:XX:XX:XX:XX:XX requested access to USB Debugging.
good luck
Click to expand...
Click to collapse
As mentioned above (first post of the thread) I know that I gotta allow my PC to connect properly to the phone. But the problem is that pop-up thingy wont show up. So I'm not able to allow USB debugging for my PC...
robin0800 said:
Actually you do not need adb to unlock the bootloader only mfastboot which does not need adb to work all you do is boot into the bootloader then follow this
http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6
Click to expand...
Click to collapse
Everytime I try to do this i get the errormessage, that those commands or not known even if I'm at the right folder with the fastboot.exe within it. Because of that I thought I would need the connection to be online (I'm kinda new to all of this ).

battlemaxi said:
As mentioned above (first post of the thread) I know that I gotta allow my PC to connect properly to the phone. But the problem is that pop-up thingy wont show up. So I'm not able to allow USB debugging for my PC...
Everytime I try to do this i get the errormessage, that those commands or not known even if I'm at the right folder with the fastboot.exe within it. Because of that I thought I would need the connection to be online (I'm kinda new to all of this ).
Click to expand...
Click to collapse
Just follow those instructions to the letter and any thing you don't understand or get an error message report back here

battlemaxi said:
First of thanks for your help, much appreciated
1. Yes I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated"
2. Yes if I go into the Device Manager I can see Android Device
3. Yes I ded change my USB-Setting to PTP
Any other ideas ?
Click to expand...
Click to collapse
Hmmm... so.. what do you see when you type "adb devices" ?
Also, in your Device Manager, is the Motorola ADB interface properly installed? (no issues)?
And yes, to unlock the bootloader you just need Fastboot... when you boot to Fastboot and type "fastboot devices" do you see anything?

Okay, I will Unlock my Bootloader tomorrow but I would like to fix this issue, because I might encounter it in the future :/

battlemaxi said:
Okay, I will Unlock my Bootloader tomorrow but I would like to fix this issue, because I might encounter it in the future :/
Click to expand...
Click to collapse
Well, are you sure you fastboot works?
If so, it's very weird why adb won't...
And yeah, ADB is very useful... if not lifesaving...

Okay I'm sure fastboot works, cause I just unlocked my phone. So got anyone any ideas how I could Allow USB debugging ? :/

battlemaxi said:
Okay I'm sure fastboot works, cause I just unlocked my phone. So got anyone any ideas how I could Allow USB debugging ? :/
Click to expand...
Click to collapse
Can you see adb in the computer device manager program

battlemaxi said:
Okay I'm sure fastboot works, cause I just unlocked my phone. So got anyone any ideas how I could Allow USB debugging ? :/
Click to expand...
Click to collapse
Couldn't wait till tomorrow to unlock the bootloader huh?
Hmm... Did you use the Motorola USB drivers from the Motorola Device Manager 2.4.5?
And everything is properly installed in Device Manager? No devices with yellow exclamation?
And ADB devices shows no list of devices attached?
So weird...

battlemaxi said:
As mentioned above (first post of the thread) I know that I gotta allow my PC to connect properly to the phone. But the problem is that pop-up thingy wont show up. So I'm not able to allow USB debugging for my PC...
Everytime I try to do this i get the errormessage, that those commands or not known even if I'm at the right folder with the fastboot.exe within it. Because of that I thought I would need the connection to be online (I'm kinda new to all of this ).
Click to expand...
Click to collapse
You can revoke all authorized devices for adb access.The option is right below the USB Debugging switch in Developer Options.
Then reboot your moto g and try again.

liveroy said:
You can revoke all authorized devices for adb access.The option is right below the USB Debugging switch in Developer Options.
Then reboot your moto g and try again.
Click to expand...
Click to collapse
Even if you revoke, you should see the device listed if you run "adb devices"...

neozen21 said:
Couldn't wait till tomorrow to unlock the bootloader huh?
Hmm... Did you use the Motorola USB drivers from the Motorola Device Manager 2.4.5?
And everything is properly installed in Device Manager? No devices with yellow exclamation?
And ADB devices shows no list of devices attached?
So weird...
Click to expand...
Click to collapse
Nope
I guess I have the newest Version, cause I downloaded it from Motorola.com
Yes everything is working no yellow thingys what so eher..
If I use the 'ADB devices' command the ID of my device shows up but as already mentioned it's offline.
Gesendet von meinem XT1032 mit Tapatalk

Softbrick? some custom rom advice please

Hello everyone,
I have done something utterly stupid with my Nexus 5, I wiped the internal storage and lost my roms, I really wasnt thinking.
I have tried looking at options like adb sideload but cant find a decent tutorial
Could I just get a micro usb to usb adapter and install a rom off that?
Would anyone be able to point me in the right direction with adb sideload?
Other problems are I can't get on the android SDK because the CMD box only flashes up.
Does the adb sideload option in TWRP actually do anything if you wait for it? Its been waiting for about 1 hour now and nothings happening.
Please guys any help is appreciated

osamarchie2000 said:
Hello everyone,
I have done something utterly stupid with my Nexus 5, I wiped the internal storage and lost my roms, I really wasnt thinking.
I have tried looking at options like adb sideload but cant find a decent tutorial
Could I just get a micro usb to usb adapter and install a rom off that?
Would anyone be able to point me in the right direction with adb sideload?
Other problems are I can't get on the android SDK because the CMD box only flashes up.
Does the adb sideload option in TWRP actually do anything if you wait for it? Its been waiting for about 1 hour now and nothings happening.
Please guys any help is appreciated
Click to expand...
Click to collapse
Why don't you flash the factory image using fastboot?
The Cmd box you are referring to happens because you need to navigate to that directory using Cmd and run it from there. You cannot just click it.

Thanks but I cant get the SDK to work at all. Im still looking into it but at the moment it wont work

Please somebody help me with the SDK, I dont know what else to do.
I cant open the SDK manager and I cant open it through eclipse either.
Someone else must have had this problem before

Click the link in my signature and then "adb and fastboot. What is it?"
This will help you configure adb properly. It also helps you learn commands. Like adb push.
adb sideload is the same as push but you type sideload instead.
FYI as much as people round here say it, there is no such thing as a soft brick. Its brick or not brick.
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client

Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?

osamarchie2000 said:
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
Click to expand...
Click to collapse
Show down and don't panic. Your device is easily fixed. Hold the power button for 20 seconds. This will shut down the phone. Then press and hold the vol down then press the power button. That'll bring your into the bootloader.
Sent from my Nexus 5 using XDA Free mobile app

osamarchie2000 said:
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
Click to expand...
Click to collapse
Power + volume down button brings you in the bootloader, from there go into recovery (navigate with volume buttons and select with power button)
In recovery follow this guide: http://forum.xda-developers.com/showthread.php?t=2559200.
Or flash the factory image in the bootloader. (that should work because you need to unlock your bootloader in fastboot)

Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys

osamarchie2000 said:
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
Click to expand...
Click to collapse
Yeah that will work too. Water damage is never good for a phone even if it stil works after that. But that's another story

osamarchie2000 said:
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
Click to expand...
Click to collapse
Yes you can. You'll have to "tell" twrp where to find the rom zip.
Sent from my Nexus 5 using XDA Free mobile app

Only problem now is I cant get the SDK to work for my life. Ive spent 5 hours trying to fix my phone already today, I have the JDK installed. I open the eclipse thingy and when i try to open the SDK with eclipse it wont work either. Please somebody help with this

osamarchie2000 said:
Only problem now is I cant get the SDK to work for my life. Ive spent 5 hours trying to fix my phone already today, I have the JDK installed. I open the eclipse thingy and when i try to open the SDK with eclipse it wont work either. Please somebody help with this
Click to expand...
Click to collapse
You don't need the SDK. You're not developing here
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client

TWRP cant find any of the files on my USB-OTG

with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?

osamarchie2000 said:
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
Click to expand...
Click to collapse
Did you read my thread that I told you to read?
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client

osamarchie2000 said:
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
Click to expand...
Click to collapse
Here's a hint, read rootSU's sticky rollup and look for the 15 second fastboot adb installer.
Sent from my Nexus 5 using XDA Free mobile app

Very sorry, Ive just re-read what Im looking for
Appologies

thankyou all, phone is well and good and im on CM11.
Thanks guys, anyone who helped is the best

Botched Graphene install on Pixel 3A - need help restoring default settings

Hello,
I am hoping for some advice on how to revert my phone back to its original "factory settings" after a botched instal of GrapheneOS onto an unlocked Google Pixel 3A.
I got to the point at which I needed to Flash the Graphene Rom to the phone, but rather than installing, I received a message from Smart Screen MS edge asking if I really wanted to run as it's protecting my PC - I clicked run anyway and a blank command line window appeared for a second. Now my pc doesn't seem to be recognising the pixel 3A when I type ADB devices. My phone is currently in Fastboot mode "unlocked" and I'm hoping for some advice on what to do next. I'm total noob, so unsure how to start the process over (return the phone to it's previous state) before, maybe, trying again on a different PC.
I have since turned on my phone and Android 11 is still present and seems to work fine (however it gives me a warning on startup that the bootloader is unlocked.
Any help would be very much appreciated - thank you in advance.

Is all what happened that your phone now:
complains about "'maybe not safe bootloader unlocked".
This is just what android does when the bootloader is unlocked.
This you did before trying the flash.
If you want the warning gone simply lock it again.
However if you into the market for graphene OS then I would recomend: along with following their guide to a t to also read up here on xda about the general rooting unlocking thing a bit more so you get the overall process a bit better perhaps next time.
About windows. There are so many tools out there to help ya with disabling some of it's spying, turning off smartscreen, auto - uploads of all your data to M$oft, etc etc.
It's not hard to find.

Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.

Ignore

deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go

Tamsta_T said:
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go
Click to expand...
Click to collapse
Hey there,
This is brilliant - thanks for all the advice. Having this support is helping me gain the confidence to learn more, research more, and then give it a go.
All the best.

deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
thats if I am not wrongly remembering my experience:
because now your phone is in fastboot mode thus it won't show up with that command anymore.
Try: 'fastboot devices'
I imagine you put it into fastboot through: 'reboot fastboot' when you where in adb?
When in fastboot you can go on and flash the recovery and such.
Are you still in need of help here?

Hey, thanks for the clarification - been away and so haven't implemented all suggestions, yet.
I typed "adb reboot booloader" which I assumed put it into fastboot mode and then unlocked it using "fastboot flashing unlock".
I tried fastboot devices but the PC still doesn't see the phone. I'm going to try the update usb driver suggested by Tamsta_T and see how it goes.
Thanks for your help.