Develop Bugs

Lost SD and USB support

Hello,
I have tried attempted to root and flash a new ROM on my phone and now I seem to have lost SD and USB support. it does not recognize any of the SD cards i put it (doesn't realize theres an SD card inside) and does not recognize any USB plugged in.
I have HBOOT .80 and i THINK i got the root correct (lotsa problems along the way so i'm not sure), but i was able to flash a ROM (NexTSENSE) so i think it worked. now, i saw a thread about fixing USB support but that required SD support. and reading that made me feel like i was royally screwed. in any case, any suggestions? I think USB support is still kinda there since I can get it to recognize it in the boot menu. but when i try to do it in recovery and use the flash rom .bat, it says device not found.
it would seem that the main concern right now is that i can't get it to see my SD cards. any of them, even after reformats and whatnot.
i can't connect to HTC Sync or anything of the of the sort. usually when i charge the phone, you get the charging notification but i don't even get that now. sounds like a driver problem but i can't see what is wrong. my computer doesn't even recognize the phone as a device every now and then
Hope i provided sufficient information. New to android scene so don't be too hard on me please =O but yea, any suggestions are welcome. thanks in advance
edit: usb support... ever so slightly back. aka, it charges now. probably was drivers on my lappy getting funny after moving between bootloader and recovery and all that fun stuff

You have the usb brick issue. Check out the thread on that. Also once you are up and running again, root using unrevoked or the fake flash method. All information is available in the dev forum.

ok, i've done some reading and this is what i've found so far. my phone is stuck in USB debug hence no USB support and somewhere along the way, SD support was disabled. from what i see, the fix is to
first:
reload the step1 of root to get back to 1.15 and basic root access.
second:
from there, i can re-enable SD support using the command:
fastboot oem enableqxdm 0
third:
apply USB-Brick fix found in post 1 of thread
and then i should be able to reload ROMs as usual. is this correct?
and where exactly do i put in the command to re-enable SD support? this is what has be confused right now. along with the commands for the USB fix
i am using the tinycore method so i just have the step1.sh. and then in the same console, can i enter that command? should i do it after a reboot? or load back into bootloader to do it. (bootloader or fastloader)

OOOOK. sorry about the continuous posts. putting new info up so it isn't exactly a bump right?
in any case, i used the androidSDK tools and ran the fastboot from there and i think i re-enabled my SD correctly. i was then able to run the USB-brick fix found on modaco forums. all done and done. nowww, since i just went through half the root process (step1.sh with tinycore), do i need to finish it? or since i had already rooted before, is it all done now?

I'm not 100% sure about that as I haven't had to fix the usb brick for ages now!
Download and install titanium backup from the market. If it works fine, then you are rooted. If not, root woth unrEVOked or fakeflash.
All the older root methods that require usb during the root process leave you open to the usb brick again.

Hi fatpandas..
Is your phone ok now? Actually my phone also have a problem like yours last week..until now,i can't fix it..if now your phone ok,can u share with me..thnks in advance..

@csyrix
sorry to hear about your situation. after just being there, i can tell how horrible it is. good news is, if you really have the same problem, then it is definitely fixable.
now, i don't know what method you used to flash yours the first time but from what i've seen, they're mostly the same. what you wanna do first is do that step1 thing where you have a temporary ROM installed. (1.15?) same process as usual.
then you'll need to run 'fastboot oem enableqxdm 0' with phone plugged in while in FASTBOOT (back button + power button thing)
in case you don't know where to put that in, you wanna run that in your command prompt (computer) while operating in the tools folder of the android SDK. (thank god for my limited computer knowledge cuz all the instructions i found just say, "run this command" and like hell if most know how/where)
in any case, the end result will be you having completed step1 and having re-enabled SD support. then turn off phone.
then get the fix from this thread
move that to your SD card (micro SD adapter) and turn back on your phone into bootloader. go to the recovery menu and hold volume up + power to bring up menu and hit the apply: update.zip.
then all should be well. i then moved on to step2 to make sure i had rooted properly. may not be necessary but i remember reading that rooting a rooted device isn't a problem so i just felt the need to do it to be safe.
that should be it. the link provided actually has all the instructions anyways (i hope mine are a bit more clear), but if not, that link should be able to fill in the holes. g'luck sir

Any way to update FW without SD card or computer?

On Thursday the 29th my phone decided to take a dump on itself. Since then it has not been able to:
-Read any micro SD cards
-Connecting to computer doesn't fully allow USB connections, it detects something plugged in, but nothing else. No ADB, no RUU update, no Sync, etc.
-Cannot charge unless off
All of the above happened while trying to get onto the leaked Froyo. I cleared the cache and wiped the data then this happened.
I already ordered a replacement from Sprint (which I have yet to hear about), but I think I can fix this one by updating the OS.
Problem is that it downgraded me to a version earlier than the one that was on the phone when I first got it. Being on this version is causing a problem by not allowing HTC Update to even see any updates.
So basically I need to update without the use of USB or SD card.
Any help?

Have you tried this http://forum.xda-developers.com/showthread.php?t=695243

063_XOBX said:
Have you tried this http://forum.xda-developers.com/showthread.php?t=695243
Click to expand...
Click to collapse
Thanks for the quick response.
That seems like it will be of a lot of help, but unfortunately adb cannot detect the phone.
EDIT:
It's also mildly amusing the way anytime someone also had this problem in that thread (the < waiting for device > in adb due to it not detecting the phone) people would just ignore it and continue on.

I have noticed that the computer can somewhat recognize the phone if it is in HBOOT USB mode. It is enough for the fastboot command to go through but return with a failed.

kbone213 said:
I have noticed that the computer can somewhat recognize the phone if it is in HBOOT USB mode. It is enough for the fastboot command to go through but return with a failed.
Click to expand...
Click to collapse
does adb work while it is in hboot? if so you should be able to push a pc36img.zip to it and fix it that way.

t3project said:
does adb work while it is in hboot? if so you should be able to push a pc36img.zip to it and fix it that way.
Click to expand...
Click to collapse
No, it only is able to recognize some things while in HBOOT. Example would be PDANet, which I used to be able to read the phone in the first place on Windows 7 x64, can see that the phone is connected. Adb still reads no devices though.

I'm pretty sure this happened when trying to wipe the phone to do a clean install. My assumption is that it wiped a file that was otherwise necessary to keep the SD card reader and USB port operational.
Is there any way that I can execute the "fastboot oem enableqxdm 0" somewhere on the phone without using adb?

Did another reset on it. Battery was low and turned the phone off without my knowledge. I turned it on to check if I had any messages or whatnot and got a message saying that the battery is low and that the current being given from the USB is not strong enough to charge it and to switch the cable.
What in the software would cause the current to be low?

Trouble flashing radio..."error: device not found"

Hi all,
I'm using the guide on how to flash a ROM onto my DHD and I'm at the stage of flashing a new radio.
In command prompt when I start with "adb reboot bootloader" it says *daemon started successfully*, however then says "error: device not found".
Not sure what I'm doing wrong, and I can't post it in the guide thread as I have less than 10 posts!
Many thanks for any info

Have you tried to boot to bootloader from the device itself instead of command prompt. And then flashing the radio from command prompt. Has everything else went ok since that stage, sure you've got every bit right and installed?

I will try doing it that way now. I saw that and thought it would work, but didn't want to risk it.
Root, Radio S-off and ENG S-off all worked fine beforehand.
edit: tried that, bootloader rebooted, so I did "fastboot flash radio radio.img" and now getting - unknown partition 'radio.img',...error: cannot determine image filename for 'radio.img'

LawAce said:
I will try doing it that way now. I saw that and thought it would work, but didn't want to risk it.
Root, Radio S-off and ENG S-off all worked fine beforehand.
edit: tried that, bootloader rebooted, so I did "fastboot flash radio radio.img" and now getting - unknown partition 'radio.img',...error: cannot determine image filename for 'radio.img'
Click to expand...
Click to collapse
Ok, good to know you've got root, s-off and eng s-off so you should be out of harms way trying different things. Have you just tried to download the actual radio file again, could be a bad download? And do you have the radio.img file in the same actual folder as the fastboot file?
I remember while I was flashing a radio for the first time the android sdk had installed fastboot in a different folder (there is tools and platform-tools folders, or similar, can't recall the exact name as they are on my laptop and I'm on a different computer just now) than adb etc. and had to manually move it to the same folder. Check the things above and report back

I will try downloading the radio again, and yes I have moved it into the correct folder. It's weird that it's saying device not found, could it be something to do with drivers?

it might be your using a different usb port to the one that was working originally. Pretty sure that caught me out before.

Well it sounds a bit strange but it could somehow be fixed on a specific usb port, although haven't ever heard about such a problem It surely could be a driver issue, just to make sure you have all the necessary adb drivers and htc sync? And didn't have any problems installing hboot (just checking and checking )? Sometimes these are a bit of spirit world issues and a simple reboot (of the computer perhaps in this case) could solve the issue

Just as a quick update, I got it all to work in the end. Now running Revolution 3.2, very pleased!
Thanks for all your help, didn't get to the bottom of it I just kept trying and it randomly worked, didn't do anything differently!

Vispe85 said:
Well it sounds a bit strange but it could somehow be fixed on a specific usb port, although haven't ever heard about such a problem It surely could be a driver issue, just to make sure you have all the necessary adb drivers and htc sync? And didn't have any problems installing hboot (just checking and checking )? Sometimes these are a bit of spirit world issues and a simple reboot (of the computer perhaps in this case) could solve the issue
Click to expand...
Click to collapse
Its true, adb had trouble working through a hub, you should plug you DHD into a usb port that connects direct to the mainboard
Sent from my Desire HD using Tapatalk

I'm having the exact same issue, but you guys are right, plugging into a USB directly connected to the mother board is the trick.

[SOLVED] Not quite bricked... yet

Hi guys,
So I wanted to flash a new rom on my Gnex (GT-i9250). I've done this countless of times, including my old Desire and Sensation, but that doesn't stop me from being an idiot, apparently.
This time I wanted to wipe my phone clean of all data, so I wiped everything.
Everything.
I don't have access to CWM, all I have is a broken bugdroid screen. All I can reach is that. No ADB, no working ROM, only bugdroid.
I have tried to use fastboot to flash it, but that only happened once, my pc did recognize the phone and fastboot listed it as a device, but it refused to comply with any <fastboot flash> commands. I thought this might've been a driver issue with my Windows 7x64, so I decided to look into that. I am not a complete tool when it comes to installing and uninstalling drivers, but I must have done something horribly wrong, because now all that happens when I plug my Gnex to my PC is that the bugdroid screen will freeze, and refuse input from Pbut+VolUp+VolDow, and I have to pull the battery. The device will install "Successfully" as "unknown device". I cannot update it's drivers.
Is it dead? Break it to me gently or give me some high hopes.
As a note I am now on a completely fresh Windows 7x64 and it did the same thing. "Unknown device" bugdroid screen freezes until battery is pulled.

If you can get into fast boot it's not bricked yet. Are you typing the command line in right? You could always try the toolkit to flash recovery or revert to stock. It's easier than hunting down everything individually.
Sent from my Galaxy Nexus using Tapatalk 2

Good to know it isn't wholly bricked - and I am sure I use the commands correctly =)
However when I plug the device to the PC the bootloader screen freezes and becomes unresponsive to input from the power and volume buttons.
I suspect this is what causes the device to become "Unknown device". Subsequently every time I connect it to my PC it freezes. If I boot it up without USB connection it remains responsive.
It also doesn't show up when using <fastboot devices> I assume is because the device is frozen in some manner.

http://forum.xda-developers.com/showthread.php?t=1626895
Use a different USB port and get the drivers right.
Read the drivers part, i believe you know the commands, if not read the flashing part too.

The first problem I am running in to (regardless of USB port) is that whenever I plug my device to the USB the bootloader freezes, and then windows triumphantly cheers that it successfully installed an Unknown Device.
It freezes the second it is plugged in.
Here's some additional information:
Fastboot mode - No boot or recovery IMG
Product name - tuna
Variant maguro.
Bootloader version - PrimeKK15
Lock state - unlocked.

HikerRemastered said:
The first problem I am running in to (regardless of USB port) is that whenever I plug my device to the USB the bootloader freezes, and then windows triumphantly cheers that it successfully installed an Unknown Device.
It freezes the second it is plugged in.
Here's some additional information:
Fastboot mode - No boot or recovery IMG
Product name - tuna
Variant maguro.
Bootloader version - PrimeKK15
Lock state - unlocked.
Click to expand...
Click to collapse
Check your usb port (on the device) for damage; Connect device to the back usb ports of your motherboard;
Reinstall Windows/Install Linux.
If none of the above work/have worked, (and dont use it just because you dont want to try the other stuff i suggested), try omapflash.
Sent from my i9250

I just plugged in my old HTC Desire, worked fine, and now I can find my Gnex with fastboot again!
Unfortunately when I attempt to use any flash commands it reponds:
sending 'bootloader' (2308 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.014s)
Except for the system.img, that one says exceeds buffer size.
Anyone ideas got any bright ideas?
Update: Just tried with the Samsung Galaxy Nexus ToolKit V10, same error is reported. Unknown.
Update # 2: Yup, that does seem to be the issue now. Failed data transfer. Unknown error.

HikerRemastered said:
I just plugged in my old HTC Desire, worked fine, and now I can find my Gnex with fastboot again!
Unfortunately when I attempt to use any flash commands it reponds:
sending 'bootloader' (2308 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.014s)
Except for the system.img, that one says exceeds buffer size.
Anyone ideas got any bright ideas?
Update: Just tried with the Samsung Galaxy Nexus ToolKit V10, same error is reported. Unknown.
Update # 2: Yup, that does seem to be the issue now. Failed data transfer. Unknown error.
Click to expand...
Click to collapse
1. Delete the toolkit.
2. Make sure you're using a rear USB port on your computer. Front ports typically work on a hub-based system and can be somewhat flakey for phone flashing. I've had front ports work a few times and then not work other times. It's strange.
3. If you are using a rear USB port, do you have another cable to try?

1. Already done. I merely tried it out hoping it had some magic trick, it didn't. It only ran the same commands that I had been using.
2. Check, I noticed this when I was taking my old Sensation into the rootz.
3. No, I don't. I suppose it could the cable although it does appear to be in good shape, but I'll see if I can get my hands on one tomorrow.

Your only bet is to find a friend that is willing to lent you his computer for awhile, then do your flashing business over there.
I noticed your bootloader version is outdated too.

Maybe being dim but can't understand why everybody is blaming computer.... probably cos I'm full of drugs (of the prescription variety) for big big bronchitis as the French doctor described it...
Can you boot it into download mode? If so try install through there using Odin plus .pit file and repartition as well
Sent from my GT-P7510 using xda premium

stinky73 said:
Maybe being dim but can't understand why everybody is blaming computer.... probably cos I'm full of drugs (of the prescription variety) for big big bronchitis as the French doctor described it...
Can you boot it into download mode? If so try install through there using Odin plus .pit file and repartition as well
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
I have never tried Odin mode, and I don't know what pit files are. Any chance you could reference a guide? Thanks

Solved!
I did this http://forum.xda-developers.com/showthread.php?t=1827685
And it worked. Looooovely. Nomnom. Thanks much everyone.

Change the subject to SOLVED
Sent from my Galaxy Nexus using xda app-developers app

HikerRemastered said:
Solved!
I did this http://forum.xda-developers.com/showthread.php?t=1827685
And it worked. Looooovely. Nomnom. Thanks much everyone.
Click to expand...
Click to collapse
Glad to be of help....just got out of bed to see your question about Odin and was going to post the link to the thread you found yourself...well done m8!! Long life to your GNex

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

kennyglass123 said:
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
Oops. Sorry about that, Thought I did put it in Q&A.

No USB, am I still able to root and flash TWRP?

My USB stopped working. Is it possible to still utilize the tablet to flash anything? Thanks for the help

I too am looking into this. I've read that towel root has worked in the past but most of what I'm reading is for KK. My USB stopped working but I still have wireless charging. What I read about towel root is that it does not unlock the bootloader. Without an unlocked bootloader, I don't think we can install TWRP/custom ROM. I could be wrong. I hope I am. I'm still checking it out though. I'll update with anything I find because yours is the first post I found with the same issue.

My USB has been broken for years now. You don't need it to flash anything.

IAIRonI said:
My USB stopped working. Is it possible to still utilize the tablet to flash anything? Thanks for the help
Click to expand...
Click to collapse
dopy25 said:
I too am looking into this. I've read that towel root has worked in the past but most of what I'm reading is for KK. My USB stopped working but I still have wireless charging. What I read about towel root is that it does not unlock the bootloader. Without an unlocked bootloader, I don't think we can install TWRP/custom ROM. I could be wrong. I hope I am. I'm still checking it out though. I'll update with anything I find because yours is the first post I found with the same issue.
Click to expand...
Click to collapse
Yes it can be done and unlocking is not required as it is relevant only in fastboot mode. Root it with an exploit apk, eg. towelroot but only up to mid-2014 OS. Then flash TWRP with Flashify, FlashFire or simply use dd in a terminal emulator app....
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p25
But why don't you fix the USB port? Most likely it has a dry joint and only needs minor soldering. If it's really damaged then get a cheap replacement from eBay. DIY info.

k23m said:
Yes it can be done and unlocking is not required as it is relevant only in fastboot mode. Root it with an exploit apk, eg. towelroot but only up to mid-2014 OS. Then flash TWRP with Flashify, FlashFire or simply use dd in a terminal emulator app....
But why don't you fix the USB port? Most likely it has a dry joint and only needs minor soldering. If it's really damaged then get a cheap replacement from eBay. DIY info.
Click to expand...
Click to collapse
I've tried using towelroot and KingRoot to no avail. Android is updated to the latest version is why it's not working I assume. Any ideas how to root?

IAIRonI said:
I've tried using towelroot and KingRoot to no avail. Android is updated to the latest version is why it's not working I assume. Any ideas how to root?
Click to expand...
Click to collapse
Sure, first check my post Unlock bootloader without factory reset, then note these fresh root exploits:
Dirty Cow
Rowhammer
Quadrooter
Nexus 7 2013 has not been updated for months and is vulnerable to the above exploits.
Again, why don't you repair the USB port?

k23m said:
Sure, first check my post Unlock bootloader without factory reset, then note these fresh root exploits:
Dirty Cow
Rowhammer
Quadrooter
Nexus 7 2013 has not been updated for months and is vulnerable to the above exploits.
Again, why don't you repair the USB port?
Click to expand...
Click to collapse
Thanks for the response I'll let you know how it goes. Don't really see the need for it if I'm able to still flash Roms on it. Wireless charging works well enough and transferring files takes some time but it hasn't bothered me so far.

I'd want to root my Nexus 7 2013 as well, with a broken USB port. The reason for wanting root is to change the DPI on the device. Does anyone know how I can root my Nexus 7 2013 on 6.0.1., without the use of the USB port? Towelroot and Kingroot don't work on it.

Possible Temporary Solution
I was able to get the USB port to temporarily work so I could flash TWRP. Just know that nowadays the factory images just reflash the stock recovery right over your custom recovery on the first reboot unless you reboot immediately to Recovery Mode instead. The reason for this post is for those who want to try to avoid taking this well-sealed device apart -- maybe marring it in the process -- to fix a connector they probably don't have on hand..
So here's how I did it:
1) First get your PC to where you can "see" when the device is connected, or at least "hear" that the device has connected, by way of the system's "device connected" sound. There are various locations in Windows that will show you when something has connected.by USB.
2) Get your flashing setup all ready and at the command prompt, with your TWRP recovery.img in the same folder as the adb.exe and fastboot.exe commands. Follow TWRP's Fastboot Install Method (No Root Required) instuctions here to get this environment set up.
3) Follow TWRP's instructions on the same page to enable a) Developer Options and b) USB Debugging on the Nexus 7 2013
4) plug in a USB cable into your PC, ideally with a good solid microUSB connector. If your USB cable/microUSB connector is "meh..." it decreases the likelihood that this will work..
5) take the Nexus 7 2013, upside-down, screen facing you, plug your microUSB cable with a good solid connector into your Nexus 7 2013.
6) Now for the "patience" part. Remember that this isn't quite "linear". You are dealing with three 3D objects, i) the microUSB cable/plug, ii) the port, and iii) the tablet. That said, the port is thankfully probably still in the close vicinity of its now broken/worn connection point(s). (Left-Handers might do the opposite of what I describe). From a right-handed perspective, with the tablet propped on your lap or a desk, take your left thumb and index finger and pinch firmly on the front and the back of the tablet, immediately below the USB port
For me, what worked were (what I will call) the "Leaning Positions". With your right hand, take the plug, move it to different positions and hold, pausing about 3 seconds at each position to hear/see your PC respond to a connection. You would be leaning the cable West, East, North, South. or left, right, forward, backward. What worked for me was to lean the cable West, or to the left, and keep a constant pressure. The pressure or tension shouldn't be extreme. The left hand's pinch should be firm.
The above directions encompass 4 positions. A variation of this, along with leaning, is to also push or press in that same direction. That gives 4 more positions to try.
If these aren't working for you, two last crazy things to try:
A) "lean" in one direction, but "push" or "press" in another direction. There are 12 different positions (would be 16 positions, but you have already tried 4 of those positions above).
B) Still no joy? For this last set of psycho positions, try adding a light twisting pressure to any of the first 8 positions above. Clockwise or counterclockwise.
Hopefully you can find a connection, Once you flash the custom recovery.img to your Nexus, it'll say
Code:
Sending 'recovery' (9030 KB) OKAY [ 0.296s]
Writing 'recovery' OKAY [ 0.485s]
Now you can relax and let go of the tension. BUT do NOT reboot until you are ready to reboot it immediately to Recovery by holding the Vol Up button and the Power button. (there may be other ways, but the other ways I tried didn't work for me.) Once the screen turns on again you should let go of the Power button, but continue to hold the Vol Up button until the Recovery screen