Database Develop

How to FORCE stop phone from showing up as USB drives in Recovery, still no root :(

Okay I don't know if this will help anyone, but I figured out how to stop Windows from detecting the phone as two USB drives when the phone goes into Recovery mode, and to make it show up as Android Composite ADB device.
I do NOT have HTC installed, rather, I'm using the USB 3 drivers that come down through the SDK, so I'm not sure how to do this if you are using the HTC Sync drivers intead.
At any rate, start with the phone off and disconnected. Open the Device Manager. Boot with your prefered method into Recovery mode, then connect the phone. It should detect as USB Mass Storage Device under Universal Serial Bus Controllers. Right click on USB Mass Storage Device and click Uninstall and then OK. Once this is done, disconnect the phone (you can leave it running in Recovery).
Open My Computer and navigate to C:\Windows\inf. Copy the files usbstor.inf and usbstor.pnf to your desktop or wherever, it doesn't matter, just make sure you put them somewhere you can get them later. Then delete them from the C:\Windows\inf folder. These are the drivers that Windows automatically uses for USB storage devices.
Ok, now bring Device Manager back to the foreground and plug the phone back in in Recovery. It should show up as Android Phone with an exclamation mark. If Device Wizard pops up cancel out of it. Now right click on the Android Phone and click update driver. Click Browse my computer for driver software. Click Let me pick from a list... Click Android Phone and Next. Click Have Disk. Browse to your SDK folder into the USB Drivers folder and you should see android_winusb.inf, select that then click OK. You should now have a list of three items to select, this part I am not sure if there is a 'right' or a 'wrong' but I go with Android Composite ADB Interface.
Select that or whichever one you think and this is what it will install as. Bingo, now whenever you connect the phone into Recovery or boot into Recovery with it already connect it correctly detects as the Composite ADB Interface or whichever you selected, but does NOT show up as any USB drives.
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
At any rate, to get everything back to normal as far as your computer being able to use USB storage devices just copy those two files back to the inf folder before you connect them and you should be fine.

bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
.
Click to expand...
Click to collapse
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.

Or you could try what I've done 7 times and achieved ADB Shell 7 times...
1. Turn the phone off.
2. Start running Loop.bat
3. Unplug USB cable.
4. Turn device on in Fastboot by holding in the optical joystick and power.
5. Plug USB in.
6. Hit power button once to get to HBOOT.
7. Wait two seconds for it to do it's thing.
8. Pull off the back of the phone.
9. Hit Vol - to Recovery then hit power.
10. Immediately after doing this continuously push the sd card in and out (about every .5 - .75 seconds)
11. ?????
12. Profit

@DigitalDementia--
How is what you said relevant in this thread?

bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
Click to expand...
Click to collapse
drtrmiller said:
@DigitalDementia--
How is what you said relevant in this thread?
Click to expand...
Click to collapse
Pretty positive it had everything to do with that section of the first post, he said he still couldn't achieve root I attempted to help him. Why don't you explain to me exactly what it doesn't have to do with this thread?

rynosaur said:
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Click to expand...
Click to collapse
The real bummer here - and I should have known better, really - is that this wipes your phone.
I suppose it should be obvious, but take it from someone who's pretty new to Android phones and just wiped their entire phone after following your steps: Please add a warning to your original post.
It's late, I'm tired and irritated, but I'm sort of bummed to know I went from hero to zero in trying to enter shell (again) during recovery all in an effort to get proper perm. root. Sort of ****ty to know that I just lost everything.

still no root
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App

USB drives are ok in recovery
When I am in recovery with adb and working correctly it still shows the 2 USB drives so this is normal and ok, what you have done is fool yourself into thinking that your phone is in correct mode but it really is not, this is why it still does not work, sorry.

rynosaur said:
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Now that I've scorched the earth, I'm hitting this thing hard with every trick I can think of to get the shell in recovery again.
Thankfully, I at least have my app list on appbrain.

After researching around the different forums, I think this maybe my issue. I will have to make this attempt when I get home.
This is what I posted on a different forum. I am not sure if this is a similar experience you were having:
So, for a little a bit I was having issues with finding and modding the usb.inf file. I got that finally resolved... Now as I go to one of the first parts of the procedure, executing the adb shell command. Well at first it said the 2 lines, about the daemon and whatever the second line was. Anyways, the third line did not say "no device found" it went straight to a shell prompt "$" . The instructions made a point in the instructions for it to say " no device found" .
I went ahead with the rest of the instructions. No Luck. And I did both methods. A co-worker of mine told to run adb devices to see if my phone is recognized. I will also make that attempt tonight.
I wanted to know if any of you had some insight. I made sure I was in the right directory.
I will make another attempt on a different machine tonight.
Thanks. Oh yeah, I do have some UNIX experience if that makes a difference.

I had the same problem, used this method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!

kentoe said:
I had the same problem, used this method here
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
Click to expand...
Click to collapse
I rooted in Windows, rather than linux, simply because I like the look of MejDam's procedure better than the linux script posted here on XDA--and his windows procedure is accompanied by his YouTube video
Long story short: I had ADB Composite Device AND the two storage volumes mounted together, as I got shell, and did the other steps in recovery. NB: they were mounted as Generic Storage Volumes, not writeable partitions. The stock recovery on DI does not allow host to mount either partions, although I'd like to see if
Code:
mount /dev/block/mmcblk0p1
worked for the SDcard on the sdcard, cuz then it would be a cinch to mount sdcard/emnc partition into host OS--windows, linux, Atari 2600, etc Worth a try.
Anyhow, my conclusion: a bad driver setup could be a barrier to catching adb shell, but it is certain not the prevailing problem for most, IMHO.

Was wondering if bast525(the creator of the thread) was ever able to adb shell while in recovery, and if so what did you do thanks.

Heh, I wish.... I've tried just about every method posted on these forums, and five different SD cards from Sandisk, PNY, and Kingston. The only thing I haven't tried is rolling back to the pre OTA update, because I don't want to wipe the phone at this point.

Confused and need help

I just got a captivate and i tried to put the phone in download mode to flash a new rom...no luck i tried the two and three button method...no luck. I also tried putting the phone in dl mode by using a command prompt...is there someone out there than can help a noob?

May need to give us some more specifics. I have only been able to get into download mode using the adb method. It may take you some time to get the drivers and everything communicating properly. Google and forum search are your friend.
1) Install the Android SDK.
http://developer.android.com/sdk/index.html
Not sure if it's required, but I also have the android adb driver installed.
http://developer.android.com/sdk/win-usb.html
2) Install the Samsung USB driver. Usually found at the link below, but they took the downloads down for some reason. (Is Samsung about to release an update?)
http://www.samsung.com/us/support/downloads/SGH-I897ZKAATT
3) Enable USB debugging on phone and plug it in.
4) Navigate to your ../android-sdk-windows/tools/ directory in a command prompt.
5) Type "adb devices" without quotes and press enter. Should see your device listed.
6) Type "adb reboot download" without quotes. Good to go.

Try this... turn your phone off... turn on ODIN in PC... while holding BOTH volume buttons plug in the USB... you should be in download mode

My suggestion is to wait. Do a couple checks before you BRICK your phone. Check this thread for info, http://forum.xda-developers.com/showthread.php?t=784147
There is a wave of phones out now that have 2 or 3 button modes disabled, broken, or something, but they don't work and have caused hard bricks. Most have had to return their phones.

when i try to search for sdk through the command prompt thats in windows it keep saying it not recognized as a internal or external command...now what?

chevy454 said:
when i try to search for sdk through the command prompt thats in windows it keep saying it not recognized as a internal or external command...now what?
Click to expand...
Click to collapse
If you are brave enough to try, then here.
Download the SDK from google. Once done, you can upzip it and buried in there is a folder called Tools. I usually take that folder and copy it to the root of my C: on my pc. So it's, C:\tools.
Plug in your phone, make sure USB debugging is on. Open a cmd windows and cd C:\tools
Now in your command window you should be able to use ADB. adb reboot recovery, adb reboot download, adb shell, etc.
Again, I would verify 100% that my button method for recovery and download work before you start modding. If you soft brick your phone, and your buttons don't work, you are screwed. If buttons work you can recover from a soft brick. I have soft bricked my phone numerous times, I have never been able to get ADB to work, I ALWAYS have to use the buttons to get into download mode.

Can I put the phone in recovery mode using clockworkmod? It doess have to be download mode NOT recovery mode right?

Recovery mode is for installing update.zip files and wiping user data. Download mode is for flashing roms using Odin.

Moved to Q&A as this is not a development question.

chevy454 said:
I just got a captivate and i tried to put the phone in download mode to flash a new rom...no luck i tried the two and three button method...no luck. I also tried putting the phone in dl mode by using a command prompt...is there someone out there than can help a noob?
Click to expand...
Click to collapse
if you are rooted then you can do the latter.
Have you gotten ADB to work?

The latest OTA updates fixes the issue with 3 button combos
Once you install the update, reboot, then try to get into recovery or download modes. Should be fine after the update

i just got my phone back after cracking the screen but i still cant get adb to work and i cant install clockworkmod because it will not let me connect to the server

Screen broken, need to recover data from internal storage

Hello, my Samsung Galaxy S I9000 fell and the screen is broken.
When I turn on the phone, I can hear the start up sound. When I connect it to PC, the drives are recognized but not mounted as I cannot select the menu in the phone.
USB debugging was not selected.
Is there a way to access the internal storage as I need to recover the data?
Please help.

1)activate phone in recovery mode (POWER+VOL UP+HOME)
2)connect the phone via usb to a computer
3)use adb to recover your files (i would recommend checking this guide or any other you can find, if you dont know how to use adb: http://forum.xda-developers.com/showthread.php?t=619153 )

You can mount USB Storage in CWM Recovery if you have it. If not try to flash a kernel with it, like CF-root or Speedmod.

Having the same problem, however I can't enable USB Debugging as my touchscreen is non-responsive and my android device doesn't support OTG USB mice etc

jleafe said:
Having the same problem, however I can't enable USB Debugging as my touchscreen is non-responsive and my android device doesn't support OTG USB mice etc
Click to expand...
Click to collapse
you have a big problem, have you try with linux, like ubuntu, perhaps you have more luck

You can flash cf root which comes with CWM recovery. Then mount USB storage with cwm recovery (press volume up+home+power) then you can access the internalbsd card.

similar problem
Hi I have a very similar problem with my Xperia S LT26i. I dropped it into the bath and it was only in the water for about 30 seconds. Now the touchscreen is not working and the colour has stared to bleed out of the screen. the screen was fine first (looked normal) but now it is very faint and mono-colour which seems to keep changing for dark to white.
I have plugged it into three different computers now and the phone is shown but nothing in it is shown. The USB debugging was not enabled, as previously I didn't know this had to be enabled. Please tell me there is a way around this? the phone itself is still working as I have had a phone call and texts come through. really want to save my data please help!
PC companion doesn't read it either as it says the phone has to have USB debugging enabled. also apparently the Xperia S doesn't have a recovery mode.

Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it
Click to expand...
Click to collapse
Link here

[Q] Recovering files from broken phone

First of all, i have tried to solve this problem for hours and so far i don't have found anything that could help me.
So my screen is broken, completetely black, and i would like to save some files from my galaxy S(files are NOT on external SD card). Connecting phone to computer doesnt help because i should turn mass media mode on, and thats kind of hard when the touch screen is not working. Kies recognizes my phone(tries to connect), but can't connect because i should turn some other mode on? I have read that it could be possible to save files with ADB and i even tried but i didnt find any suitable instructions. So could anybody tell me how to save my holiday pictures :crying:

tuotanin said:
First of all, i have tried to solve this problem for hours and so far i don't have found anything that could help me.
So my screen is broken, completetely black, and i would like to save some files from my galaxy S(files are NOT on external SD card). Connecting phone to computer doesnt help because i should turn mass media mode on, and thats kind of hard when the touch screen is not working. Kies recognizes my phone(tries to connect), but can't connect because i should turn some other mode on? I have read that it could be possible to save files with ADB and i even tried but i didnt find any suitable instructions. So could anybody tell me how to save my holiday pictures :crying:
Click to expand...
Click to collapse
Hi,
I have a solution for you
No need to turn on mass storage.
What you need:
USB cable
Working pc
Android SDK http://developer.android.com/sdk/index.html
USB Driver http://developer.android.com/sdk/win-usb.html
1. Download and install this tool: http://de.codeplex.com/releases/view/107423
2. Boot your phone into recovery (worked for me) ( volume up+home+power)
3. Connect your usb cable
4. Start Droid Explorer and search for your sd card

cixty said:
Hi,
I have a solution for you
No need to turn on mass storage.
What you need:
USB cable
Working pc
Android SDK
USB Driver
1. Download and install this tool:
2. Boot your phone into recovery (worked for me) ( volume up+home+power)
3. Connect your usb cable
4. Start Droid Explorer and search for your sd card
Click to expand...
Click to collapse
Thank you for your answer. I think i can't get my phone into recevory mode. At least Droid explorer doesn't find it. When i try to boot it into recovery, my computer makes that "connected sound" several times, so i think the phone really is broken... Also, when the phone is connected to computer with usb cable, and i put the battery into the phone, i can hear that connected sound immediately, so i guess the phone automatically boots on? Well i keep trying but i think it is not possible to boot this phone into recovery mode

tuotanin said:
I have read that it could be possible to save files with ADB and i even tried but i didnt find any suitable instructions. So could anybody tell me how to save my holiday pictures :crying:
Click to expand...
Click to collapse
What you need therefore is a (rooted) phone and USB debugging must be enabled - at least I never tried withouit thos options turned on. Since you don't need to do sthg with su I think technically you can go without root as well, but did never run it without so not sure on that. Hope you had USB debugging active before your screen broke...
Install the adb tools on your pc if you haven't already. (google is your friend )
What you want to do now is connect your phone to the PC, open up a terminal session (within windows e.g. execute -> cmd ) and then fire up those commands:
Code:
adb
lot of stuff, ignore - if it doesn't work: google installing drivers and the adb tools
Code:
adb devices
here your phone should be listed if it is in debugging mode.
then just
Code:
adb pull [pathToYourHolidaypics] [pathToSaveOnHarddisk]
so for example:
Code:
adb pull /sdcard/DCIM Holidaypics
and you photos should be rescued. Good luck!

2 Be said:
What you need therefore is a (rooted) phone and USB debugging must be enabled - at least I never tried withouit thos options turned on. Since you don't need to do sthg with su I think technically you can go without root as well, but did never run it without so not sure on that. Hope you had USB debugging active before your screen broke...
Install the adb tools on your pc if you haven't already. (google is your friend )
What you want to do now is connect your phone to the PC, open up a terminal session (within windows e.g. execute -> cmd ) and then fire up those commands:
Code:
adb
lot of stuff, ignore - if it doesn't work: google installing drivers and the adb tools
Code:
adb devices
here your phone should be listed if it is in debugging mode.
then just
Code:
adb pull [pathToYourHolidaypics] [pathToSaveOnHarddisk]
so for example:
Code:
adb pull /sdcard/DCIM Holidaypics
and you photos should be rescued. Good luck!
Click to expand...
Click to collapse
Thank you for your answer. Unfortunately, this method doesn't find my phone either.. I think that USB debugging mode was on but can't say for sure. Maybe my Samsung is just completely broken. I guess we are out of ways to recover files . Thank you for your help and of course feel free to post anything if anybody have any idea.

tuotanin said:
Thank you for your answer. Unfortunately, this method doesn't find my phone either.. I think that USB debugging mode was on but can't say for sure. Maybe my Samsung is just completely broken. I guess we are out of ways to recover files . Thank you for your help and of course feel free to post anything if anybody have any idea.
Click to expand...
Click to collapse
if usb debugging off, mtp still working so pc must detect ur fone unless its already not working.if pc recognised ur fone when plugged in, use any partition backup app in pc to backup da entire partition
n i m sorry if its doesnt help u
Sent from my GT-I9000 using xda premium

compacity said:
if usb debugging off, mtp still working so pc must detect ur fone unless its already not working.if pc recognised ur fone when plugged in, use any partition backup app in pc to backup da entire partition
n i m sorry if its doesnt help u
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
It should be in USB storage mode. I dont know what mode is on atm. Even Kies doenst recognize phone

File/Photo Recovery Mission - Phone dropped - USB debugging off

hello
dropped my N6 on to a marble floor, the screen is black and touch is not responding. the phone seems to be working otherwise. usb debugging is off, the phone is fully stock (stock recovery, bootloader is locked, encryption is the marshmellow default, phone is not rooted). There is no lockscreen pin or pattern, just the standard slide to unlock. photos are not auto-backed up online, so I need access to the phone itself.
when I plug the phone into my computer, I cannot file explore it because I need to enable a prompt on the phone to MTP instead of charge only. as USB debug if off I cannot use ADP PULL / SDCARD.
I have two ideas:
1) use Wug's nexus root toolkit and do something there like put TWRP on, and then use TWRP to avoid the USB debug being off. I'm not sure on the details of this though! Any guide on the steps here? the power and volume hardware keys work, so in theory I can get into recovery with the right steps.
2) get a micro-usb hub, and plug in a wired mouse as well as connect to my computer, then blindly click about hoping that I enable MTP or USB debugging. I can then either copy files off in windows explorer or use Vysor to control the phone over ADB and email files etc as needed. Would this work? I don't have a hub so would need to spend £5-10 buying one
Many thanks in advance for any help!

Option 1 won't work because the bootloader is locked. You'll have to try option 2.