Is there a way to get into USB drive mode with a dead screen? Had a truck drive over my Vibrant, which completely pulverized the screen. The rest of the phone is still working fine, and I'd like to get my data off the internal drive. But since the screen doesn't work there's no way I can think of to activate USB drive mode. Any tricks to get this done?
I cannot remember which program it was, but there is one that you can use to control your phone. It gives the screen shot of your phone and lets you control the buttons and menu's with your mouse as though you were using your fingers on your phone. I believe you have to have USB debugging enabled though for it to work. You could use that to mount the phone to your pc. Or you could use ADB to get into it and copy everything off the internal sd.
download droid explorer and just plug it in.
Thanks, will give that a try tonight.
Samsung fascinate
rooted
windows 7 with Samsung 64 bit drivers installed
back to stock DL01 and then OTA DL09 about five times today.
Here is the problem, when i mount my phone, intermittantly Windows 7 doesnt give me the pop up window that lets me view my sd card files. It gives me a pop up window with 2 choices:
Option # 1. View your files - this really doesnt let me view anything except 4 files one of them being a " Bootloader file "
Option # 2. Install Bootstrap Loader exe.
I have had my phone since september and rooted, rom"ed OTA"ed all of it and today this started happening.
When i look in Drives and Printers my phone is listed as a CD Drive and not a Mass Storage Drive.
Just curious if any one else has had this issue and what might have caused it to start happening.
I installed Samsung Kies earlier this afternoon but uninstalled it since it was pretty much worthless to fascinate owners and the U.S. isnt supported.
Any input would be appreciated. Thanks in advanced for any info.
have you tried re downloading the drivers from samsung.com? it worked for me.
This has been talked about in several places already. It is a common bug with DL09. The best solution is to flash one of adrynalyne's 1/18 test kernels found here. I hope this helps!
BTW: make sure it is one of the kernels with the cd fix
when im on 2.1 aosp, i have that same issue, to fix reboot with debugging enabled
Seems to be related to some new 'Media sync' option.
I did some playing around and the following seemed to let me 'mount'
the phones as before. ( But I dont like it. )
Hoping for some direction from Verizon tech on
a) what is media sync ?
b) how do I turn off permanently If I dont need or want to use it?
Unplug phone from usb cable.
Then on Phone... Menu...Settings..USB settings
Change to ' Ask on connection'.
then press home button.
Plug in USB cable.
When prompted...Press 'Mass storage'.
Now wait...wait..wait. Took about 30 to 45 seconds.
Annunciator bar should have usb symbol. Drag it open.
Press usb connected....Press Mount..
My laptop now recognized the SD card on E drive.
Copy files as usual.
When done...Open Anunciator bar and 'Turn Off' USB storage.
Media Sync is a mode that allows programs such as Windows Media Player and Rhapsody to access your SD card and copy over DRM protected music.
Sent from my Samsung Fascinate
Thanks for this, it worked
not sure if it helps with the problems with 2.2 but whenever i had this issue on 2.1 this is what i did, turn off your phone with the usb cable in and turn it back on with the phone still plugged in. It always seemed to work for me
From your homescreen when you hit menu go to usb settings then make sure the little radio button for mass storage device is selected. That was my problem after the latest OTA from verizon. Also it takes like 15 seconds for it to all sync up.
i have searched these forums hi and low, googled, etc. still cant find an answer....
on djo5,dl09 i was able to plug my phone into the usb port in my car, then mount my sd card, and it would automatically connect and find my music and start playing it.
on either dl30, or eb01, i cannot get it to work.
it is very frustrating. everytime i try, (all different combinations debugging on/off mass storage/ ask on connect, etc.)
i get a "device connect failed" message.
does anyone else have this issue?
has anyone been able to get this to work?
Another fix when it shows up as a CD-ROM drive is to right click and eject. Seems to work every time for me.
Sent from my SCH-I500 using XDA App
zparlet said:
not sure if it helps with the problems with 2.2 but whenever i had this issue on 2.1 this is what i did, turn off your phone with the usb cable in and turn it back on with the phone still plugged in. It always seemed to work for me
Click to expand...
Click to collapse
Thanks your idea of reboot while still plugged in saved me. Tried every other idea with no cure.
Thanks for the post.
Just installed Superclean 2.6 and had issues. I tried ejecting the CD Rom device in Windows, but that didn't work. I changed the usb settings from Mass Storage to Ask On Connection and then tried it again. This time I received the Android guy asking to mount the drive. Yay! It worked! It does however show both a CD rom drive and the mass storage drive in Windows XP.
On another note, I found that if I plug in my phone without unlocking the password first it locks up the phone until I unplug the usb cable attached to the pc.
Make sure you are using a USB cable that has a good connection (like the original one). I bought some aftermarket cables, and while they are good enough for charging, I really think they fit too loose to keep a secure connection.
apnews said:
Seems to be related to some new 'Media sync' option.
I did some playing around and the following seemed to let me 'mount'
the phones as before. ( But I dont like it. )
Hoping for some direction from Verizon tech on
a) what is media sync ?
b) how do I turn off permanently If I dont need or want to use it?
Unplug phone from usb cable.
Then on Phone... Menu...Settings..USB settings
Change to ' Ask on connection'.
then press home button.
Plug in USB cable.
When prompted...Press 'Mass storage'.
Now wait...wait..wait. Took about 30 to 45 seconds.
Annunciator bar should have usb symbol. Drag it open.
Press usb connected....Press Mount..
My laptop now recognized the SD card on E drive.
Copy files as usual.
When done...Open Anunciator bar and 'Turn Off' USB storage.
Click to expand...
Click to collapse
4GivenByChrist said:
Another fix when it shows up as a CD-ROM drive is to right click and eject. Seems to work every time for me.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thanks guys, this combination worked perfectly for me.
Just fyi, this is due to Verizon bloatware that has been inserted I to the kernel. Adrynalyne and company managed to flush it out of the Eclair kernel, but since we don't have kernel source code for the Froyo kernel yet, there's nothing that can be done at this time. When source is available, this will be fixed by our devs.
Sent from XDA Premium on my Super Clean Fascinate
So let's start off saying I messed up bad. REALLY BAD. I'm not the one who is braindead, by the way. It's my vibrant.
http://i.imgur.com/R6UfS.jpg
I have an important recording in one of the folders in my internal data that I would be willing to go very far to restore. The recording would be impossible to reproduce, even under the same circumstances and people involved.
I've been able to boot up the phone (supposedly) because I hear the hardware battery charging sound. Only two of the indicator lights on the bottom light up. The touchscreen seems to be unresponsive, but I could be wrong because the sounds for the phone were disabled before the accident. "HEY MAN YOU SHOULD HAVE USED A CASE" - I did have a case on.
Anyway, when I connected it to the desktop (drivers already installed, done this dozens of times) it said unknown device. I tried other USB ports, still got nothing. I took it to the laptop, same issue. Tried to force install the drivers, that didn't work either. The battery is fully charged. I can restart the phone and the boot times combined with indicator lights at the bottom tell me the phone is "working"
I have Droid Explorer installed, the program I usually use to access the file system. It doesn't find any devices connected. Not sure about ADB. I read somewhere on the forums that you can get into recovery mode by pressing HOME+POWER+VOL UP. I'm not sure if the home button works but I tried this with no luck.
"HEY MAN WHY DON'T YOU BACKUP" - I do. On the first of every month. It hasn't been the first of November, therefore I don't have this backup.
Tell me my friends, is this phone to be euthanized? I would also preferably not want to buy a new screen. Any sort of help is appreciated.
Hey question, is the recording you want on the SD card or the internal memory of the phone, reason I ask is if its on the SD card, you can pull that out, mount it on your lappy or whatever and use the proper SW to explore the card, and retrieve your audio file you want, otherwise, if not then yes you still need a way to overcome the detection of phone to access the two drives for the internal memory of the phone, so you can retrieve your audio file. Yes drivers are the first thing that comes to my mind, however if the phone was being detected prior to damaging it then IDK why that would change unless there is a HW issue from the trauma of dropping it, was the phone detected prior to dropping it with 0 defects and since you damaged it that functionality is no longer working???? I mean your confident its fully booting up, and technically the phones functional except the screen is hosed, do I have this scenario right, and as such is the reason why you cant navigate to the folder you need in order to retrieve your file????
Look you also gotta find a way to see what your doing with the phone so you can get it into mass storage mode, then you'll be able to extract the audio and whatever files you want, BTW replacing the glass isn't that bad, unless your not confidant about doing fragile mechanical work on phones!! And replacing the capacitive glass face would restore the phone to an operable state where you could once again be interactive with it.
Of course if the recording was on the external SD card I wouldn't have a problem with it. It looks like the trauma messed up the hardware, but I can't be sure anymore. Of course If I fix the screen and connect to wifi I can recover it but a screen would cost me another $150 and I'm not sure if that's such a good idea. If only I knew someone else with the same phone, then I could borrow their screen temporarily!
I sort of know exactly everything that you're saying, it's just that there's no solution to the problem so I'll have to either get an expert to recover my files or buy a new screen. Looks like I will need quotes on this.
I have a phone with a cracked screen that still works. That screen with your mobo could be used to at least get a display and pull the files you need. PM me, and I'm sure we can work something out.
Sent from my SGH-T959 using XDA App
I literally had this same problem. I'll tell you what I did. You need to set up adb on your computer. There are plenty of instructional videos on that. Once you have adb setup for sure, then connect your usb and power the phone on. You should hear your phone recognize your device. Open up cmd on your pc and type in adb devices. You should see your phone listed. Now download a program called "Android commander" it's for windows. Android commander uses adb features to see, copy, erase, and basically manipulate all the media on your device without being able to see your screen or enable mass storage. I used this trick to pull pictures of my daughter being born off my vibrant before sending it back to Tmobile for my replacement. I also was able to delete su and any traces of being rooted or having custom roms on my device thus avoiding my warranty being voided. Hope this helps. If you need further help, feel free to add me on google talk. I'm happy to help. I know how I felt when this happened to me. [email protected]
Sent from my T959 using xda premium
Well, I wrote a very thorough post explaining my situation, and when I tried to post it I was informed I was trying to register for my forum account instead. *facepalm* So with that thirty minutes wasted, let's try this again.
I have a Kindle Fire HDX 7. Software 4.5.2. I rooted it with an exploit, deleted some Metrics system files, and then after rebooting came up to a broken "desktop." The main Favorites window flashes from white to gray at me, there are no icons in it. I can't run any apps. I can get to the Settings menu, enable ADB, MTP, etc., but I can't turn on Wi-Fi or do updates. I did a Factory Reset, but that just erased all my content. If I reboot from this situation, I get stuck at the orange animated logo screen forever. If I hold the Volume + button and choose Factory Default from there, I can get back to the flashing Favorites desktop window, but still can't do anything just as before.
I have installed the Android SDK for Windows, installed the adb_usb.ini files, and the device is not recognized by Windows at all. It charges, but that's it. I tried using Ubuntu and SoupKit. They also don't see the Kindle as being there. No matter how many times I reboot the Kindle, all the SoupKit commands just hang at "Waiting for Device".
I made a Factory Cable. When I plug it in, the Kindle doesn't turn on. Holding down the power button does nothing. If I plug back in a regular USB, it turns right on. If I plug the Factory Cable in at the Flashing favorites screen, I hear the "plugged in" chime and the charging icon appears on the battery, but nothing else happens. If I try to reboot from there, with the Factory Cable still in, it shuts down but won't restart. I am open to the possibility I messed up the cable, but continuity seems good with my meter from both ends of the cable and from the solder joints to the micro-USB end, etc.
Has anyone seen the flashing desktop behavior? What should I be doing to try to get my Kindle recognized, so I can push the stock firmware back to it to fix this? Any help would be greatly appreciated. I made a foolish mistake and I can't seem to correct it myself, so I'm hoping someone else out there has the answer I'm overlooking. Thank you for your time.
Make sure you have the Kindle Fire ADB drivers installed.
EncryptedCurse said:
Make sure you have the (link text clipped due to restrictions on <10 posters) installed.
Click to expand...
Click to collapse
I had already installed the Google USB driver using the SDK Manager, and also modified adb_usb.ini and so forth, to no effect. I tried the instructions at the above link, though, since that Add-On site was something new. It appears some things have changed since that article was written, though, since the only thing available from the Add-On site from Amazon now is just the Kindle USB driver. I installed it, but Windows still doesn't recognize the Kindle. I rebooted the computer and the Kindle just to be sure.
To be clear, when I say it doesn't recognize it, I mean it doesn't even appear in Device Manager as an unknown device. No matter which computer, USB port, or cable I use, Windows 7 and Ubuntu simply do not see a device as there. The Kindle chimes and shows the charging icon, but Windows doesn't see anything as being plugged in.
From what I'm reading, it appears the factory cable I made is useless with the Fire HDX line.
I notice that the SuperSU app is still installed for what it's worth. I can't run anything, so it's kind of hopeless. I can't seem to find the original exploit that I used, but I basically just tapped a button that said "Gimme Root" and then I had super user access. Dangerous, dangerous super user access.
I'm not opposed to opening the Kindle up and tinkering with things, if there's any chance that will help correct this problem.
Valence1981 said:
I made a Factory Cable. When I plug it in, the Kindle doesn't turn on. Holding down the power button does nothing. If I plug back in a regular USB, it turns right on. If I plug the Factory Cable in at the Flashing favorites screen, I hear the "plugged in" chime and the charging icon appears on the battery, but nothing else happens. If I try to reboot from there, with the Factory Cable still in, it shuts down but won't restart. I am open to the possibility I messed up the cable, but continuity seems good with my meter from both ends of the cable and from the solder joints to the micro-USB end, etc.
Click to expand...
Click to collapse
"Factory cables" (sometimes called fastboot cable) are useless on all HDX models. Stick with a standard, high quality USB cable. I realize this seems counter intuitive but Amazon has done their best to make the latest generation of devices inaccessible to those looking to leverage the hardware or simply recover and non-functioning device.
Your issue with 'seeing the device' is likely due to Windows drivers. If the suggestion from @EncryptedCurse doesn't work suggest deleting all related entries from device manager when the device is tethered, reboot and then reconnect. Windows should install the correct drivers assuming you downloaded the Kindle specific ones in advance. There are shortcuts to this procedure (eg: a reboot really isn't necessary) if you know your way around Windows.
Davey126 said:
"Factory cables" (sometimes called fastboot cable) are useless on all HDX models. Stick with a standard, high quality USB cable. I realize this seems counter intuitive but Amazon has done their best to make the latest generation of devices inaccessible to those looking to leverage the hardware or simply recover and non-functioning device.
Your issue with 'seeing the device' is likely due to Windows drivers. If the suggestion from @EncryptedCurse doesn't work suggest deleting all related entries from device manager when the device is tethered, reboot and then reconnect. Windows should install the correct drivers assuming you downloaded the Kindle specific ones in advance. There are shortcuts to this procedure (eg: a reboot really isn't necessary) if you know your way around Windows.
Click to expand...
Click to collapse
I plugged the Kindle in (I'm at the Settings menu on it, since staying at the launcher/home/favorites screen just threatens to give me epilepsy with its constant flashing), I removed all the USB host controllers and root hubs, then scanned for hardware changes to reinstall them. The Kindle is not found, as a recognized device or an unknown one. As I said, when I boot from a thumb drive into Ubuntu, it doesn't find it either. When I run adb devices, it says no device is found. I have heard of people getting it to take ADB commands anyway, despite the not found error, by just repeatedly rebooting the Kindle, but it hasn't worked for me.
Valence1981 said:
I plugged the Kindle in (I'm at the Settings menu on it, since staying at the launcher/home/favorites screen just threatens to give me epilepsy with its constant flashing), I removed all the USB host controllers and root hubs, then scanned for hardware changes to reinstall them. The Kindle is not found, as a recognized device or an unknown one. As I said, when I boot from a thumb drive into Ubuntu, it doesn't find it either. When I run adb devices, it says no device is found. I have heard of people getting it to take ADB commands anyway, despite the not found error, by just repeatedly rebooting the Kindle, but it hasn't worked for me.
Click to expand...
Click to collapse
My bad - I overlooked some key details in your original post even though clearly stated. If you are not seeing the the device from any host (and you have certainly done the things I would have suggested) there is little you can do to recover via standard methods. A couple longshot suggestions:
- change cables. I know you tried a homebuilt cable but grab a couple standard cables just to rule out a bad wire; crappy usb cables are more common than people think
- check for a bent/missing pin in the micro-usb port; possible you aren't making a data connection (for others benefit, data and charge use different pins)
I realize both the above are highly unlikely given the sequence of events that lead up to your current problem. Running out of ideas ...
I doubt this will help, but one long shot on Windows is try to use the HDX toolkit to install the adv drivers. It won't do anything else with this build, but if this is a driver issue, it could possibly fix it. Also, if you can try revoking adb permissions if you can get to that window and try a different usb port.
These are all last ditch efforts though.
I tried the HDXToolkit driver install. It seemed promising, but it still doesn't see the Kindle. Checking the connector to see if the data pins were damaged was a good idea, but unfortunately they look unmangled. I am using a regular USB cable at this point, by the way.
I can't disable ADB mode on the Kindle itself. I can go to the Developer menu and try to disable it, but it just kicks me back to Settings and the option stays set to On when I go back to it. I can switch between MTP and CTP for whatever that's worth.
I appreciate the optimism. I'm quite upset with myself for doing this to my Kindle, as I really was getting a lot of use out of it. I can't help but be a little mad at Amazon, too, for making it so hard to fix this.
Oh, I was also going to mention that when I go to the stock recovery window with the option between reboot and factory restore, at the bottom under the Kindle logo it says "No Command" not sure what the significance is of that. I've seen where some people get a lot of error messages in that area.
Valence1981 said:
I tried the HDXToolkit driver install. It seemed promising, but it still doesn't see the Kindle. Checking the connector to see if the data pins were damaged was a good idea, but unfortunately they look unmangled. I am using a regular USB cable at this point, by the way.
I can't disable ADB mode on the Kindle itself. I can go to the Developer menu and try to disable it, but it just kicks me back to Settings and the option stays set to On when I go back to it. I can switch between MTP and CTP for whatever that's worth.
I appreciate the optimism. I'm quite upset with myself for doing this to my Kindle, as I really was getting a lot of use out of it. I can't help but be a little mad at Amazon, too, for making it so hard to fix this.
Oh, I was also going to mention that when I go to the stock recovery window with the option between reboot and factory restore, at the bottom under the Kindle logo it says "No Command" not sure what the significance is of that. I've seen where some people get a lot of error messages in that area.
Click to expand...
Click to collapse
Some very left-field ideas:
- try enabling bluetooth. Obviously if you can get that working there is a way to move files to/from device which might provide additional repair/recovery options.
- there is a rumor that long pressing power (40+ sec) performs some type of 'hard reset' on the device. Never see it work but worth a try.
If the device is still within warranty reach out to Amazon. They are pretty good about providing replacements (say it died during an update) although it will likely be a refurb. Who knows, might get one with a low enough fimware level to unlock. That opens a entirely new set of options.
It would appear that the HDX can't use Bluetooth for file transfers, only for connecting peripherals like keyboards and speakers. I'm going to try it anyway.
I have done the long power button hold down, but it doesn't seem to do anything.
I believe I should be in warranty. I got my Kindle for Christmas, so it's only about 6 months old. I'd rather not have to lie to customer service, though. So I'm still prodding at this trying to find a solution. If I could just get WiFi to work, so I could download a firmware update, I think that might help, but of course everytime I put in my network information and tell it to save it, it kicks me back to the Settings window and I get no connection.
The 40 second Hard Reset never worked in my case, although My Kindle didn't even boot up after my stupidity.
Valence1981 said:
It would appear that the HDX can't use Bluetooth for file transfers, only for connecting peripherals like keyboards and speakers. I'm going to try it anyway.
I have done the long power button hold down, but it doesn't seem to do anything.
I believe I should be in warranty. I got my Kindle for Christmas, so it's only about 6 months old. I'd rather not have to lie to customer service, though. So I'm still prodding at this trying to find a solution. If I could just get WiFi to work, so I could download a firmware update, I think that might help, but of course everytime I put in my network information and tell it to save it, it kicks me back to the Settings window and I get no connection.
Click to expand...
Click to collapse
Understand the ethical concern. Stating it died during an update is technically correct provided you don't indicate who was doing the updating. If asked if the device is rooted then you should come clean (which could impact Amazon's decision whether to replace). I have a great relationship with Amazon and believe honesty will ultimately get you further than deception.
So it doesn't appear there is anything else I can do about this. The Kindle isn't recognized by any computer I have, using Windows XP or 7, or using Ubuntu. I read that XP might be able to see it if I disabled ADB, but it's permanently turned on and if I try to turn it off it kicks me back to the Settings menu without actually changing the setting. Since no computer can see it, I don't think there is anything I can do to recover it. Unless someone figures out a way to flash the ROM by taking the thing apart and doing it manually, which I don't think is going to happen anytime soon. I can't believe I ruined my Kindle. Looks like all that's left is contacting support and seeing if they'll help me with a replacement.
Actually, one other thing. If I have to send the old one back, won't they notice that SuperSU is installed and realize what I did?
Valence1981 said:
So it doesn't appear there is anything else I can do about this. The Kindle isn't recognized by any computer I have, using Windows XP or 7, or using Ubuntu. I read that XP might be able to see it if I disabled ADB, but it's permanently turned on and if I try to turn it off it kicks me back to the Settings menu without actually changing the setting. Since no computer can see it, I don't think there is anything I can do to recover it. Unless someone figures out a way to flash the ROM by taking the thing apart and doing it manually, which I don't think is going to happen anytime soon. I can't believe I ruined my Kindle. Looks like all that's left is contacting support and seeing if they'll help me with a replacement.
Actually, one other thing. If I have to send the old one back, won't they notice that SuperSU is installed and realize what I did?
Click to expand...
Click to collapse
Sorry for your troubles. Amazon is pretty easy going - at least in my region. If the device is in warranty and you simply describe the symptoms without going into too much detail you should get a replacement. I don't believe they inspect devices beyond looking for obvious physical damage. The device will likely get 'reprogrammed' and be sold as a refurb. It makes little economic sense to have a tech inspect returned devices unless they are looking for something specific or a pattern of failures. Good luck.
Any have file APQ8074.hex and 8074_msimage.mbn for unbrick QHUSB?