Related
Howdy XDA, lurking for a few weeks now, first time posting.
I have a Vodafone Smart 2, which runs pretty much the same hardware as the Alcatel V860. I previously rooted it myself, removed crapware, blah blah. This worked fine until I updated the firmware through the Firmware Upgrade Manager, which restored all the crapware on my phone and somehow removed my root privileges.
Now, when I try to root using the same method I used to root the phone previously, I run into an error. Normally, I would root from a zip file on the SD card through the bootloader/recovery menu. Now, when I try to access this menu, I'm greeted with a message stating: 'All data will be lost, continue?' in various languages.
This obviously doesn't allow me to root my phone through the familiar method, which was, as far as I know, the only method to root this particular type of phone. I have tried using the sdk manager but this came up as a dead end.
I would be extremely grateful if anybody can give me any information or ideas as to how to root this phone again?
Cheers.
Maybe you're pressing the wrong buttons? I remember that if I pressed volume down + power button instead of volume up a different thing happened.
Scorpius666 said:
Maybe you're pressing the wrong buttons? I remember that if I pressed volume down + power button instead of volume up a different thing happened.
Click to expand...
Click to collapse
Hi there, thanks for replying.
Normally I would hold the power & the volume + buttons, which would bring me to the bootloader menu. Doing so now just brings up the 'All data will be lost, continue?' message.
Interestingly enough, holding the power & the volume - buttons causes the phone to freeze on the android startup logo, which leaves me with no other option than the pull the battery and try again.
Can't you use adb reboot recovery or sth like that?
Sent from my GT-I9100 running CM10
MemoryController said:
Can't you use adb reboot recovery or sth like that?
Sent from my GT-I9100 running CM10
Click to expand...
Click to collapse
Hi there, using the command 'adb reboot-recovery' simply refreshes the list that first comes up when you execute adb.exe within Command Prompt.
I am able to reboot using the 'adb reboot' command though, so the drivers must be in working order.
seanmaxwell99 said:
Hi there, using the command 'adb reboot-recovery' simply refreshes the list that first comes up when you execute adb.exe within Command Prompt.
I am able to reboot using the 'adb reboot' command though, so the drivers must be in working order.
Click to expand...
Click to collapse
Hi there
do what you did using "adb reboot" dos command, but type in " adb reboot recovery " instead while the phone is on, phone goes off and on into boot menu , where you can do your rooting(update.zip) from sdcard.
hope that helps you,
Cannot find my phone using adb/fastboot! Nothing on the screen! :'(
I got the Nexus5 2-3 weeks back, it's a good phone, everything works great!
Today finally I decided to root it and flash some customized roms.
1. My Nexus 5 had like 70% battery. I went to bootloader, unlock and root using below commands.
fastboot-windows.exe oem unlock
fastboot-windows.exe boot image\CF-Auto-Root-hammerhead-hammerhead-nexus5.img
Click to expand...
Click to collapse
2. The phone got rebooted, and then I saw a new Android 4.4. Until now everything looks fine.
Then I went to bootloader again and ran the below command.
fastboot flash recovery recovery-clockwork-6.0.4.4-hammerhead.img (which I got from cwm official site)
Click to expand...
Click to collapse
3. After this step was done, i used volume button to go to "Recovery" (I'm still at bootloader).
Now I used the below command to put the rom on my phone.
adb push myromname.zip /sdcard
Click to expand...
Click to collapse
Then I used volume key and choose "install zip from /sdcard". He was saying "Cannot open directory" twice, then "Cannot find zip file" or something.
Then I was searching the issue on google, and got some answer, and wanna have a try.
I think I touched "power" button accidently. The display was gone (and it never came back). I pushed "power" button again, nothing happened.
I tried "adb devices" and "fastboot devices", nothing worked. (I tried those toolkits, but they need at least "fastboot" working I guess).
When I connected my phone to my PC in device manager I can see "LGE AndroidNet USB Serial Port (COM4)". I don't know what that means.
I tried holding "power" key and "volumn down", but after ~15 seconds it disconnected from PC and then connected back again. Nothing changed on the phone side.
And I holded three buttons together, I got some new device called "QHSUSB_DLOAD". It can't find the driver for this one, and I have no idea what is it.
Does anyone get the same situation? Can someone help me with that? I'm sorry for the pool English! :crying:
njql007 said:
Cannot find my phone using adb/fastboot! Nothing on the screen! :'(
I got the Nexus5 2-3 weeks back, it's a good phone, everything works great!
Today finally I decided to root it and flash some customized roms.
1. My Nexus 5 had like 70% battery. I went to bootloader, unlock and root using below commands.
2. The phone got rebooted, and then I saw a new Android 4.4. Until now everything looks fine.
Then I went to bootloader again and ran the below command.
3. After this step was done, i used volume button to go to "Recovery" (I'm still at bootloader).
Now I used the below command to put the rom on my phone.
Then I used volume key and choose "install zip from /sdcard". He was saying "Cannot open directory" twice, then "Cannot find zip file" or something.
Then I was searching the issue on google, and got some answer, and wanna have a try.
I think I touched "power" button accidently. The display was gone (and it never came back). I pushed "power" button again, nothing happened.
I tried "adb devices" and "fastboot devices", nothing worked. (I tried those toolkits, but they need at least "fastboot" working I guess).
When I connected my phone to my PC in device manager I can see "LGE AndroidNet USB Serial Port (COM4)". I don't know what that means.
I tried holding "power" key and "volumn down", but after ~15 seconds it disconnected from PC and then connected back again. Nothing changed on the phone side.
And I holded three buttons together, I got some new device called "QHSUSB_DLOAD". It can't find the driver for this one, and I have no idea what is it.
Does anyone get the same situation? Can someone help me with that? I'm sorry for the pool English! :crying:
Click to expand...
Click to collapse
I`am afraid your N5 is killed in action (truly bricked), you have to turn it in for warranty/repair and have the motherboard replaced. Nothing you can do anymore afaik
I don't understand your first step...
CF Auto root unlocks the BL so it's not necessary to do it.
Moreover the right steps are the following:
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
Click to expand...
Click to collapse
Primokorn said:
I don't understand your first step...
CF Auto root unlocks the BL so it's not necessary to do it.
Moreover the right steps are the following:
Click to expand...
Click to collapse
That`s because some users only start reading OP`s after they got into trouble
If u don't know what you're fully doing, then why risk it
Sent from my Nexus 5 using xda app-developers app
dicecuber said:
If u don't know what you're fully doing, then why risk it
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I thought I'm following the correct steps …
Thanks all who have replied, I have decided to give it back to Google
Just call for RMA and tell them your phone won't power on--just that. It happens so they won't question it.
Sent from my Nexus 5 using Tapatalk
Hi,
I'm trying to sideload the final 5.0 build to my Nexus 5.
The ADB drivers are installed. This command prompt is opened in the desktop. I manage to get to the point in Recovery Mode where I need to flash the 'update.zip' (which I have named exactly that and this happens.
Anyone help me please?
Thanks beforehand.
I'm not a regular here, if I have broken the rules, please let a moderator know and sort me out. If this is an illegal thread, please delete it. Apologies.
ibz100 said:
Hi,
I'm trying to sideload the final 5.0 build to my Nexus 5.
The ADB drivers are installed. This command prompt is opened in the desktop. I manage to get to the point in Recovery Mode where I need to flash the 'update.zip' (which I have named exactly that and this happens.
Anyone help me please?
Thanks beforehand.
I'm not a regular here, if I have broken the rules, please let a moderator know and sort me out. If this is an illegal thread, please delete it. Apologies.
Click to expand...
Click to collapse
Your usb drivers are not installed correctly, reinstall the drivers and enable usb debugging in developer options. Check if you succeeded by typing in cmd (while the phone is in fastboot): fastboot devices. You should see a serialnumber if all went well.
Hi, @ibz100. It actually looks like your drivers are installed properly. At least your ADB drivers. You only use ADB while booted into the android OS, or from recovery. However, while you're booted into the bootloader (also known as fastboot mode) you'll want to use "fastboot" commands.
So boot back into the bootloader either the same way using ADB while booted into the OS, or from a powered down state hold Volume down(-) & Power keys. You can also use both volume keys + power to access the Nexus 5's secondary bootloader.
Once in fastboot mode, run the command
Code:
fastboot devices
If your serial number appears like it did for ADB devices, then your fastboot drivers are successfully installed. If not, then we need to get your fastboot drivers set up.
Read here if you need to install them. Feel free to reply here if you're having trouble installing them and I can help you through that as well.
Also useful: http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
If your drivers are properly installed, run the command "fastboot" without quotations to see a list of available commands to be used in fastboot. If you're still not sure what to do, just ask.
If you want to use ADB to apply the update.zip, boot into recovery mode (I'm going to assume you're using a stock recovery). Use the commands I mentioned above to get to the bootloader. Now use the volume keys to navigate from "Start" to "Recovery Mode" With Recovery selected, key the Power button. You should see a picture of an android with an exclamation mark with the text "No Command". From there hold down the Power button and tap Volume UP(+) once. This will boot you into stock recovery mode. From there use the volume keys to navigate to "Apply update from ADB". Power key to select.
Check out the Roll-up sticky guide by @rootSU for all the information you need to get yourself up and running.
http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
Again, if you need any more help just reply and let me know, I'm more than happy to help.
Try loading koush's universal adb drivers I was having the same problem but this solved it for me. Sidelosd worked a treat and running lollipop without problems so far...
Thabk you everybody, I'll try your recommended (re)installation of my fastboot drivers later and get back to you if I have any further updates on my situation.
Big thanks for all the replies guys, I really was taken aback by the sheer effort you put into helping people around here. Rest assured that it doesn't go unappreciated. Keep up the good work!
ibz100 said:
Thabk you everybody, I'll try your recommended (re)installation of my fastboot drivers later and get back to you if I have any further updates on my situation.
Big thanks for all the replies guys, I really was taken aback by the sheer effort you put into helping people around here. Rest assured that it doesn't go unappreciated. Keep up the good work!
Click to expand...
Click to collapse
Well I've had my fair share of driver issues. I blame my PC. Anyways, I know how frustrating it can be.
However going back to what I said before, since your ADB drivers are properly installed (being as your device ID showed up and reboot bootloader worked) I wouldn't think it's too far fetched that you already have fastboot drivers installed. Before you try deleting/reinstalling them, I would first boot into the bootloader and run the command "fastboot devices" (no quotes). If you device ID shows up in fastboot, there's no need to mess with your drivers.
Again, the reason ADB "stopped recognizing your device" is because you booted into fastboot mode. While you're in fastboot, you need fastboot commands.
If you boot back into the OS, or into recovery, ADB will recognize your device again. That's how it's supposed to be.
So power down the phone. Hold Volume Down(-) & Power until the phone boots into the bootloader and type;
Code:
fastboot devices
If your ID shows up in a similar fashion to the way it did in your screenshot, you're golden. Let us know how it goes! :good:
I'm on Android 5.0.1. I changed my PIN screen lock of my xperia and 20 minutes later I forgot it out of lots of things happening at once. I try to guess it 120 times (5.0 doesn't have "Enter google password" after x tries) without any progress (I was still at school at this point). I tried to boot to recovery and wipe it, but because I had Cyanogenmod recovery it didn't work. (it doesn't work at all, when I try to wipe it, it just displays the Android and flashes a few times and that's it.). At home, I tried to use Android Device Manager to erase it, but it just rebooted into Android. I tried to unlock the screen with the lock feature, but it didn't work at all, nothing happened (if I put something in the text field it allowed me to call owner. Pressing back or home puts me back in the lock screen "swipe up to unlock" state. I tried reflashing it with flashtool, but I couldn't even connect my device through ADB, it only said
Code:
04/034/2015 18:34:13 - INFO - Device connected with USB debugging off
04/034/2015 18:34:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
even though USB debugging was on, even the notification said so. ADB just doesn't find it at all. When I plug my device in my computer the window that pops up says "This folder is empty". Am I really screwed? I guess my only chance is to keep guessing the password... I don't remember the first number or how many numbers were in it... help?
pefu19 said:
I'm on Android 5.0.1. I changed my PIN screen lock of my xperia and 20 minutes later I forgot it out of lots of things happening at once. I try to guess it 120 times (5.0 doesn't have "Enter google password" after x tries) without any progress (I was still at school at this point). I tried to boot to recovery and wipe it, but because I had Cyanogenmod recovery it didn't work. (it doesn't work at all, when I try to wipe it, it just displays the Android and flashes a few times and that's it.). At home, I tried to use Android Device Manager to erase it, but it just rebooted into Android. I tried to unlock the screen with the lock feature, but it didn't work at all, nothing happened (if I put something in the text field it allowed me to call owner. Pressing back or home puts me back in the lock screen "swipe up to unlock" state. I tried reflashing it with flashtool, but I couldn't even connect my device through ADB, it only said
Code:
04/034/2015 18:34:13 - INFO - Device connected with USB debugging off
04/034/2015 18:34:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
even though USB debugging was on, even the notification said so. ADB just doesn't find it at all. When I plug my device in my computer the window that pops up says "This folder is empty". Am I really screwed? I guess my only chance is to keep guessing the password... I don't remember the first number or how many numbers were in it... help?
Click to expand...
Click to collapse
Hi bro.
Download this file Here.
Extract it on your desktop.
Now this file will install the cwm recovery.
Open a command window in the folder you have extracted.
Type
fastboot flash boot boot.IMG
Now before pressing enter you just need to power off your phone connecting it to the computer while holding volume + key .
Now you can press enter.
After you flash the recovery boot to recovery and make a factory reset.
Note: after this process the WiFi may not work you just need to install this app http://forum.xda-developers.com/xperia-l/development/app-recoveries-recovery-installer-t3187915 and give root and install TWRP.
And don't worry windows won't show the internal or the external memory because your phone is locked it's kind of protecting your files .
Don't forget to hit thanks
n78 shadow said:
Hi bro.
Download this file Here.
Extract it on your desktop.
Now this file will install the cwm recovery.
Open a command window in the folder you have extracted.
Type
fastboot flash boot boot.IMG
Now before pressing enter you just need to power off your phone connecting it to the computer while holding volume + key .
Now you can press enter.
After you flash the recovery boot to recovery and make a factory reset.
Note: after this process the WiFi may not work you just need to install this app http://forum.xda-developers.com/xperia-l/development/app-recoveries-recovery-installer-t3187915 and give root and install TWRP.
And don't worry windows won't show the internal or the external memory because your phone is locked it's kind of protecting your files .
Don't forget to hit thanks
Click to expand...
Click to collapse
I did what you told me to do, and it says < waiting for device > in the console. The device displays a blue LED after I volume+ and plug the USB in. I then enter the command and it's just stuck at < waiting for device >.
pefu19 said:
I did what you told me to do
Click to expand...
Click to collapse
Did you have fastboot driver installed?
If not go to flashtool folder then to drivers there you will see a exe file ,open it and install fastboot drivers and xperia l derivers.
Edit: and I think it should be installed automatically by windows just wait for it.
n78 shadow said:
Did you have fastboot driver installed?
If not go to flashtool folder then to drivers there you will see a exe file ,open it and install fastboot drivers and xperia l derivers.
Edit: and I think it should be installed automatically by windows just wait for it.
Click to expand...
Click to collapse
I think I have them installed, but when I go to the flashtool drivers folder and install those drivers, I select xperia L drivers and the 2 on top, it says Install Failed for all of them
What windows do you use???
If 8 I think it won't work , you should try it on another one
n78 shadow said:
What windows do you use???
If 8 I think it won't work , you should try it on another one
Click to expand...
Click to collapse
I have Windows 10 x64
pefu19 said:
I have Windows 10 x64
Click to expand...
Click to collapse
Sorry bro that won't work try it on another computer with 7 or lower.
Don't forget to hit thanks if I hleped you
pefu19 said:
I have Windows 10 x64
Click to expand...
Click to collapse
windows 10 has a special 3rd party driver protection... you must disable it and install fastboot driver... AND you need a USB2.0 because 3.0 has known issues
Sent from my Xperia T using XDA Free mobile app
In Window 10 go to setting>update&security>Recovery>Advanced startup and restart pc >then choose troubleshoot>Advanced Option>Startup Setting and restart>and it will ask option choose Disable Driver signature enforcement and done......
if you have any problem ask...:laugh:
Hi guys. Looks like I deleted the Fire UI. Now, I dont get pop up messages. I dont have the notification bar or the soft keys. And now that the pop up boxes wont pop up, I cant authorize the tablet. Which means I cant do any modding to it, to fix it. Just dont know what to do at this point. Any ideas would be greatly appreciated.
Xpun3414 said:
Hi guys. Looks like I deleted the Fire UI. Now, I dont get pop up messages. I dont have the notification bar or the soft keys. And now that the pop up boxes wont pop up, I cant authorize the tablet. Which means I cant do any modding to it, to fix it. Just dont know what to do at this point. Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
HD 8 or 10? Get a copy, untampered SystemUI.apk from the same device, or as close to it. Must be from an Amazon tablet. Boot to recovery and adb sideload it.
DragonFire1024 said:
HD 8 or 10? Get a copy, untampered SystemUI.apk from the same device, or as close to it. Must be from an Amazon tablet. Boot to recovery and adb sideload it.
Click to expand...
Click to collapse
I have the new HD 10 7th Gen 10". Cant do the ADB thing at all. Since I cant authorize it. Even in recovery mode.
Xpun3414 said:
I have the new HD 10 7th Gen 10". Cant do the ADB thing at all. Since I cant authorize it. Even in recovery mode.
Click to expand...
Click to collapse
in recovery shouldn't matter. You can only adb sideload Amazon signed software in recovery. I will give you a copy of mine as soon as I have access to it.
DragonFire1024 said:
in recovery shouldn't matter. You can only adb sideload Amazon signed software in recovery. I will give you a copy of mine as soon as I have access to it.
Click to expand...
Click to collapse
ADB wont work, since I cant authorize the tablet.& in recovery mode the pc & ADB wont even see the tablet
Xpun3414 said:
ADB wont work, since I cant authorize the tablet.& in recovery mode the pc & ADB wont even see the tablet
Click to expand...
Click to collapse
If you can't boot to recovery at all, you might be perma bricked.
Sent from my Moto E4 using XDA Labs
Xpun3414 said:
ADB wont work, since I cant authorize the tablet.& in recovery mode the pc & ADB wont even see the tablet
Click to expand...
Click to collapse
So, to make sure we're all talking the same thing:
Can you boot into recovery mode? (To boot into recovery mode: When the tablet's off, press and hold the power and volume up button. The volume up button is the one closer to the power button. Once the Amazon logo pops up, release the power button but keep holding the volume up button. Eventually, it should boot to a text-only page.)
If you can boot into recovery mode, are you seeing the recovery menu? It should offer you a text-based menu, with options:
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
Assuming you can boot into the recovery menu, connect the device to your computer. Select "apply update from ADB," using the volume buttons to maneuver and the power button to select.
It should say: Now sent the package you want to apply to the device with "adb sideload <filename>"...
With the device connected to your computer, go to where your adb software is; type: adb devices . . . does that list the device? (AFAIK, the recovery menu should allow ADB even if you don't have ADB enabled in the system proper; I'm not 100% certain of that, but it's a pretty useless recovery menu if it doesn’t . . .)
If it does list with the adb devices command, then it should be ready to sideload. At this point, you'll need an update file to sideload (which will wipe your system and should convert it to a factory-restored tablet). That's beyond the scope of this troubleshooting, but there are other guides online. However, make sure you choose the same sideloading package as your operating system version. (For example, my tablet has 5.5.0.0, so I sideload update-kindle-40.5.9.1_user_591450020.bin)
To be honest, if you're tech-savvy, then it's quite probable you've already done all this, and apologies for spelling it all out . . . but, reading what you're saying, I'm having a hard time even envisioning what you're getting stuck on.
GamerOfRassilon said:
So, to make sure we're all talking the same thing:
Can you boot into recovery mode? (To boot into recovery mode: When the tablet's off, press and hold the power and volume up button. The volume up button is the one closer to the power button. Once the Amazon logo pops up, release the power button but keep holding the volume up button. Eventually, it should boot to a text-only page.)
If you can boot into recovery mode, are you seeing the recovery menu? It should offer you a text-based menu, with options:
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
Assuming you can boot into the recovery menu, connect the device to your computer. Select "apply update from ADB," using the volume buttons to maneuver and the power button to select.
It should say: Now sent the package you want to apply to the device with "adb sideload <filename>"...
With the device connected to your computer, go to where your adb software is; type: adb devices . . . does that list the device? (AFAIK, the recovery menu should allow ADB even if you don't have ADB enabled in the system proper; I'm not 100% certain of that, but it's a pretty useless recovery menu if it doesn’t . . .)
If it does list with the adb devices command, then it should be ready to sideload. At this point, you'll need an update file to sideload (which will wipe your system and should convert it to a factory-restored tablet). That's beyond the scope of this troubleshooting, but there are other guides online. However, make sure you choose the same sideloading package as your operating system version. (For example, my tablet has 5.5.0.0, so I sideload update-kindle-40.5.9.1_user_591450020.bin)
To be honest, if you're tech-savvy, then it's quite probable you've already done all this, and apologies for spelling it all out . . . but, reading what you're saying, I'm having a hard time even envisioning what you're getting stuck on.
Click to expand...
Click to collapse
ok heres the thing.
A) when in android, ADB see the device. But I cant authorize ADB on the tablet, due to no pop up box & no notification bar.
B) I can boot into recovery (yes I can see it) but,when in recovery. the pc/ADB doesnt see the tablet at all. so sideloading doesnt work.
C) I would think being in recovery mode, you wouldnt need to authorize ADB. Im thinkin', maybe because I cant authorize it in Android, I cant do anything in recovery. IE: sideload.
Heres what I get when the tablet is in recovery mode..
Ok today, while in recovery mode, I plugged in the tablet & I got this.....
Xpun3414 said:
Ok today, while in recovery mode, I plugged in the tablet & I got this.....
Click to expand...
Click to collapse
Yeah, that's all a poser.
At this point, about the only other advice I can offer is to try a different USB port (on your computer), and/or a different USB cable. And if all THAT fails, try a different COMPUTER with different usb cables. (I had some strange errors with getting my Kindle to be recognized by the computer, until I switched to a different port . . . and I've had a problem with the device not charging at all depending on which cable I'm using.)
And if that doesn't yield anything different . . . I'm out of ideas, I'm afraid.
Xpun3414 said:
ok heres the thing.
A) when in android, ADB see the device. But I cant authorize ADB on the tablet, due to no pop up box & no notification bar.
B) I can boot into recovery (yes I can see it) but,when in recovery. the pc/ADB doesnt see the tablet at all. so sideloading doesnt work.
C) I would think being in recovery mode, you wouldnt need to authorize ADB. Im thinkin', maybe because I cant authorize it in Android, I cant do anything in recovery. IE: sideload.
Heres what I get when the tablet is in recovery mode..
Click to expand...
Click to collapse
Xpun3414 said:
Ok today, while in recovery mode, I plugged in the tablet & I got this.....
Click to expand...
Click to collapse
GamerOfRassilon said:
Yeah, that's all a poser.
At this point, about the only other advice I can offer is to try a different USB port (on your computer), and/or a different USB cable. And if all THAT fails, try a different COMPUTER with different usb cables. (I had some strange errors with getting my Kindle to be recognized by the computer, until I switched to a different port . . . and I've had a problem with the device not charging at all depending on which cable I'm using.)
And if that doesn't yield anything different . . . I'm out of ideas, I'm afraid.
Click to expand...
Click to collapse
Sideloading in recovery does not require ADB authorization !!! All you need to do is to get the correct drivers loaded, to make sure that your PC can see your Fire. Recovery is for restoring things, if it needed ADB authorization, it would defeat its purpose.
Get USBDeView, and see which devices it shows when the Fire is in recovery, and plugged into a PC USB port. Then try to locate correct drivers. You may want to delete any driver related to this Fire in USBDeView, then plug it back in, make windows try to get the driver for it again.
GamerOfRassilon said:
Yeah, that's all a poser.
At this point, about the only other advice I can offer is to try a different USB port (on your computer), and/or a different USB cable. And if all THAT fails, try a different COMPUTER with different usb cables. (I had some strange errors with getting my Kindle to be recognized by the computer, until I switched to a different port . . . and I've had a problem with the device not charging at all depending on which cable I'm using.)
And if that doesn't yield anything different . . . I'm out of ideas, I'm afraid.
Click to expand...
Click to collapse
I can't believe I didn't think about that. Totally sliped my mind.
Anyway. Used a different usb cable & a different pc and BAM ! Flawless recovery. Thank you for your help.
-------------