Related
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.
I managed to drop a glass container of baby food on my captivate, thus cracking my screen and making the phone unusable.... terrific!
I am looking to see if there is a way to force my phone to mount to my Mac so that I can backup then clear my internal sd card. I do not even know where to start. Any advice would be appreciated. Thanks
I'm not to sure about doing this on a mac, but if you have usb debugging turned on on your phone then you can use an adb like program to mount the sd card. If not.... Idk if it's even possible at all.
Sent from my SAMSUNG-SGH-I897 using XDA App
yeah you should always leave the phone in debugging mode just in case you need adb. the development kit is available for mac and adb is included. adb should work in recovery mode. it is one of the few top of the line andriod phones that is still debugging enabled in recovery mode.
adb is command line based so i hope you are comfortable with that.
I could use the help of you gurus trying to get some data off my phone since I sat on it yesterday and horribly mangled the screen. The screen wont come on but it sounds like the phone is still working. The screen also doesnt respond to touching it not surprisingly
Really all I want to do is get my texts off of the thing, but with the screen not working, and ADB seeming to be disabled, im not sure how to go about that.
Is there any way for me to:
A) Remotely enable ADB(im guessing no)
B) Remotely enable Wifi(so I can use an app that is already on my phone to control it from my computer)
Any help is appreciated!
BB
If you had a custom kernel on the phone before it broke there is an option in clockwork to restart adb you would just use up down vol buttons and power buttons. I will give you a Button sequence in a minute. Just gotta reboot my phone
[Edit ]
I just rebooted my phone and the dark core kernel does not have the option to restart but I do know some kernels do post what you are tuning and maybe someone else knows. Also there is the TV OUT option just plug into your tv and see if you don't get a picture maybe its on by default. Good luck(;~}
Sent from my phone on vacation
Thanks for the reply! I was unaware you could restart ADB from CWM. I am running Serendipity VII with the most up to date Serendipity kernel I will try to find out if they support it(if anyone reading this can look in CWM and give me the key sequence that would be so awesome)
http://forum.xda-developers.com/showthread.php?t=1107894
I thought about the TV out option but I would still be unable to input anything from the touchscreen so would be a bit limited with what I can do
Thanks for the assist!
BB
Baconbreath said:
Thanks for the reply! I was unaware you could restart ADB from CWM. I am running Serendipity VII with the most up to date Serendipity kernel I will try to find out if they support it(if anyone reading this can look in CWM and give me the key sequence that would be so awesome)
http://forum.xda-developers.com/showthread.php?t=1107894
I thought about the TV out option but I would still be unable to input anything from the touchscreen so would be a bit limited with what I can do
Thanks for the assist!
BB
Click to expand...
Click to collapse
The only thing I can think of, if find out where the texts live, ADB into the phone and pull them to your PC.
I use SMS Backup app, but if you don't already have it, it won't do you any good at this point.
You know, Maybe what you can try is a nandroid backup from ADB. You may be able to save the entire ROM and contents, then pull it from your device to your PC.
Also the key sequence for mount usb in recovery might be useful but you don't get access to system only the sd card.
Sent from my phone on vacation
That would be really helpful key combo too to get some photos off of it..and maybe Tibu backed up apps. Mental note: use google+ cloud storage for photos and video in the future
BB
I gave up on this for a while....but tonight I decided to give it a go again with results! Posting steps here in case someone else runs into this...
I took the phone full apart to see if there was any damage internally besides the mashed screen and I couldnt find any. Put it back together and oddly ADB started working!
After much searching...I was able to find this solution:
http://androidcommunity.com/forums/...s-storage-through-the-recovery-console-19999/
for a step by step, all I did was :
Adb root
Adb reboot recovery
Running:
ADb devices
Showed:
List of devices attached
32326B102E3E00EC recovery
then run:
adb shell
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
and the SD card became mountable and I was able to rescue my stranded data
BB
My wife seems to have corrupted her internal SD card, absolutely no idea how. She was bone stock, not even rooted. I could not get stock to even boot past the boot animation, so I tried one of the GB 1 Clicks and boogs KJ3 kernel to get CWM, now I can boot to the launcher, but it bootloops from there. I don't want to format the internal SD until I can get her pictures from it if possible, so my question is: is there a way to get the pictures off, if they even still exist? I have tried mounting in CWM and all i get is a lost directory, now I can't even mount USB storage.
Boot into recovery, then use adb to pull from /mnt/sdcard
Don't need to mount with adb.
Just tried this, I get an empty directory. Tried using adb shell and still showing an empty directory. Any other thoughts, or am I going to have to reformat?
Ouch....I think a format is in order.
sorry man
Well I got it to boot with the kk4 1 click and it runs, but the gallery is empty, so I assume I'm hosed. Any thoughts on cause, she says that earlier she got a message in the notification area about removing her sd card (she has no external, just an internal)?
Try this
Set your screen timeout to the max. Reboot y your phone. Keep touching the screen, don't let it go to sleep. Keep doing that as you pull everything from the phone.
About adb
If you don't set a destination folder in your command, it won't pull. If she's on 2.1, you don't use the mnt part. Place a folder directly on your c drive, so that it's address path is c:\your folder name
This makes your adb command
adb pull \sdcard\ c:\your folder name
Do all of this without letting the phone go to sleep. Maybe it will work for you.
Adb pull /sdcard c:\your folder
Forward slash on phone, backslash on pc.
studacris said:
Adb pull /sdcard c:\your folder
Forward slash on phone, backslash on pc.
Click to expand...
Click to collapse
Yeah, your right.
Appreciate both of your input, but now adb won't even recognize that the phone is attached in the stock kk4 1 click, even in recovery. Like I said the gallery is totally empty and my USB storage on the about phone shows that all of the storage is available, so I'm gonna guess it's all gone. I'll try flashing one of the custom kernels for kk4 just to give it one last try, but I'm not holding out much hope here.
How are you trying to connect to your computer with adb? All you have to do is turn usb debugging on and plug in. open a command prompt terminal. Any of that sound familiar?
There should be a "my files" app you can explore the sdcard that way.
Pictures are in DCIM/camera folder.
the stock 1 click did not have a usb debugging option. Got it to work connecting with samurai 1.4.3, but the directories are showing empty or nonexistent.
Studacris,
You must have been posting while I replied. I've used the my files app and it shows dcim as empty. Now, my wife has decided she's gonna give up on the phone since this was her warranty replacement after her first 1 completely bricked after our daughter played with it. Never could get that one to even boot, although, I've found that this one won't boot to download with a jig, have to use the battery pull, vol +/vol -, insert usb cable method.
Thanks again for the attempts, but I think it's a lost cause, so I'm giving up.
Flash it back to stock and get it replaced again.
Hi all,
the question seems simple, but I am unable to solve it, would be very grateful for somebody helping me out.
I have an unlocked HTC One
Bootloader is working, OS is upgraded to 2.24.401.1
Recovery is installed and working TWRP 2.6.1.0
When starting the phone, the system asks to connect to WiFi but does not find a network in the air, hence I am not able to continue that route.
When connecting it to a Windows PC, it is recognized, the usual "drives"are mounted as the drivers are installed.
I see the HTC One but it is read-only and a file cannot be copied to it.
I tried to use the adb push xxxx /storage command but this also says the system is read-only.
I just lack the knowledge on how to continue, I cannot flash a rom as it is not copied to the device.
Please be so kind to guide me in the right direction.
Ruud
When you connect the phone to the PC - the phone will show its connected on the top (notification bar) pull that down and select /USB connected then choose
HTC Sync Manager
Now connect the phone to the pc and it will be seen as a media devise open it and in root copy the rom and anything else you need
leave the phone with that setting then when you need to move photo, music, docs or whatever its is just a matter of finding the correct file and copy/paste
L0rdNels0n said:
When you connect the phone to the PC - the phone will show its connected on the top (notification bar) pull that down and select /USB connected then choose
HTC Sync Manager
Now connect the phone to the pc and it will be seen as a media devise open it and in root copy the rom and anything else you need
leave the phone with that setting then when you need to move photo, music, docs or whatever its is just a matter of finding the correct file and copy/paste
Click to expand...
Click to collapse
Thanks, but your explanation is for normal usage, as said, I had a read-only system, this did not work for me.
I understand that the command adb remount did the trick, after that at least adb was able to do its task.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Ruud Westerhout said:
Hi all,
the question seems simple, but I am unable to solve it, would be very grateful for somebody helping me out.
I have an unlocked HTC One
Bootloader is working, OS is upgraded to 2.24.401.1
Recovery is installed and working TWRP 2.6.1.0
When starting the phone, the system asks to connect to WiFi but does not find a network in the air, hence I am not able to continue that route.
When connecting it to a Windows PC, it is recognized, the usual "drives"are mounted as the drivers are installed.
I see the HTC One but it is read-only and a file cannot be copied to it.
I tried to use the adb push xxxx /storage command but this also says the system is read-only.
I just lack the knowledge on how to continue, I cannot flash a rom as it is not copied to the device.
Please be so kind to guide me in the right direction.
Ruud
Click to expand...
Click to collapse
Do you have USB debugging mode activated when you connect to a PC?
Also you can adb sideload a rom when you are in recovery.
Thanks farang4u,
As I said, Matt helped me out and the last Wipe Data which I did this morning was also the trick, so now all seem fine with my phone again.
Thanks all.