Related
My mac is unable to detect my phone since I flashed Cyan 6 Test 8 Koush, as such I am unable to use adb. Given that I use a mac I assume this is not a driver issue. Phone is able to recharge via USB and USB debugging is enabled. I have found this issue (USB Brick) for the desire on this site but it involves flashing a rom unique to that device. Any ideas on how to resolve issue? Other than USB brick issue, everything is in order.
My card reader is able to read SD card and I have copied to my HD, so I assume issue is with USB on phone.
The only thing I can think of is that your phone somehow got stuck on "Charge Only" mode. In the stock version you can go to Settings, Connect to PC and then change some options there... I do not use this rom though so I'm sorry I can't help you other any further (I'm sure you likely already knew about the above info... if no one responds to you with an answer within a couple days I'd consider asking the Indian Prince of Roms himself... and I know he uses a Mac).
I assume you are mounting your system in recovery while trying to get adb?
Sent from my Incredible using Tapatalk
Yes. Device is not found. Can't view contents via finder either. When I pop out SD card and insert into reader contents are visible.
Sent from my Incredible using XDA App
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
This should also fix usb bricks.
Referencing:
http://forum.xda-developers.com/showthread.php?t=691639
Obviously you will need to try it from a terminal emulator.
I recently had the same issue - on a PC - where my CM6 test 8 install would charge but not register as a USB device and give me device malfunction warning messages. Turns out it was a problem with a non-HTC branded micro USB cable I was using.
Odd thing is it worked fine for a month or so, then decided to not work anymore out of any USB port. Switching over to the original cable fixed the problem. Now the other cable is relegated to the stock charger.
This should also fix usb bricks.
Referencing:
Obviously you will need to try it from a terminal emulator.[/QUOTE]
Thank you. I am on the road, so I won't be able to implement your solution until later. The procedure you outlined seems simple enough. I will reread. Is it ok if I email you with any questions, or would you prefer that I address my questions via this forum?
tdiman said:
I recently had the same issue - on a PC - where my CM6 test 8 install would charge but not register as a USB device and give me device malfunction warning messages. Turns out it was a problem with a non-HTC branded micro USB cable I was using.
Odd thing is it worked fine for a month or so, then decided to not work anymore out of any USB port. Switching over to the original cable fixed the problem. Now the other cable is relegated to the stock charger.
Click to expand...
Click to collapse
Funny thing is that I did not notice the problem until I changed cables. I was using a third party w/no problems, problem only surfaced when I used original cable. Hopefully I will have same luck as you, if not, adrynalyne posted near idiot proof instructions. I just hope that I am brighter than your average idiot, no promises.
adrynalyne, if my hboot is .77 could I simply flash PBI131.img to revert back to original? If not, could I use terminal emulator on my phone to execute necessary commands?
Answer from adrynalyne was "Well, yeah. the PB31IMG.zip should work, as long as it lets you. The other method would need to be done if it won't."
I was able to resolve the problem by switching usb cord to a 3rd party from htc, go figure. Nevertheless, the USB issue has been cited in other forums and if anybody else runs into the problem, follow directions above, i.e. follow links.
TY to all who gave me advice, esp. adrynalyne.
hey, umm.. im having a similar problem. when i try to plug in my droid incredible with the leaked 8/1 froyo rom, nothing comes up on my PC, i am able to acces my sd card by going to computer, and then clicking my sd card. but when i did this, i also noticed that there was a new cd drive, which comes from my phone. does anyone know if this is a usb brick?
Apparently there is a vzw ISO. There are instructions on how to remove in another post. Search USB bricked. I can't post links otherwise I would.
Sent from my Incredible using XDA App
Well, i tired it, but it didnt fix my auto start problem... and now, the cd drive doeant have a name, its juat cd drive:f
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
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?
Hello guys, just gonna state my problem and ask a few questions.
So, here it is. If I connect my phone to pc/laptop nothing happens, no notifs appear on my phone neither mtp or mass storage. But, when I connect my phone through electricity socket it charges up. Oh, another thing sometimes when I connect my phone to pc/laptop ports it charges up but still no connection to storage/or phone. This just happened last night after from my hospital duty and got home and tried to flash fxp128(love this work) and my phone wont be recognized at all.
So, I've searched up google not that deep but, I found some issues just like mine. Some said its a the laptop problem just need a restart, change cables, remove battery, try in different computer/laptop and etc cases like those. Alreadt tried everthing of those but non seems to work. So, i think my phone hardware(the usb port in my phone) is really the problem. My questions are:
It is repairable?
The repair fee costly or not?
Will this thing will likely come up again?(low chance/high chance of getting this problem again.)
PS: I remember that while on the hospital(free time) i tried to open the rom manager but it fc's when i try launching it.(everytime)
- and my 8gb type 4 sd is broken even through card reader it cant be read. ( dont know what caused this) so i change to class 2 4gb my spare card.
Hope you answer me guys, thank you!
tbh. your phone worked perfectly, and after flashing fxp128 you get problems and directly assume your phone is broken Instead of going back to stock and figure out if it really is.
Usb connection problem could also be caused by not having the com.sonyericsson.usbux "systemapp" or other things.
reply
sashake said:
tbh. your phone worked perfectly, and after flashing fxp128 you get problems and directly assume your phone is broken Instead of going back to stock and figure out if it really is.
Usb connection problem could also be caused by not having the com.sonyericsson.usbux "systemapp" or other things.
Click to expand...
Click to collapse
how can i go back to stock if my phone cant be detected in my computer? can't even go for fastboot and flashmode.
Did you make a NaNdroid back up with CWM? That would be your best bet at this point.
reply
calar714 said:
Did you make a NaNdroid back up with CWM? That would be your best bet at this point.
Click to expand...
Click to collapse
Did have a nandroid backup but on fxp 127. Tried to use it but still no luck. Any suggestions/ideas?
If you're using windows, try to uninstall the portable device at device manager window, while the usb is attached to your phone. Then disconnect the phone after you've uninstalled. After that reconnect it once more and see to it that the drivers are installed properly. It's usually USB mass storage or MTP USB device storage.
So just as the title says, but here's a little back story (might help).
I'm trying to help out a friend with his Bell Mobility i747M. He wanted to try out Lollipop, so I looked into it and said I could do it. Last I even touched his phone was quite a while ago when he wanted me to flash CM11, back when KK was still pretty new. So it's been over a year. I flashed CWM back then, got the ROM installed, and everything has been good ever since. Fast forward to now, and he wants to try Lollipop. I figured the first thing I should do is update the bootloader/radio, which went perfectly fine (after some researching, I chose 4.3/MK5 for his i747M). I tested them by booting back to the ROM and checking About Phone - everything was good. So I booted back to the old version of CWM, and thought it would be a good idea to get a more modern recovery. CWM or TWRP didn't matter, just as long as it was more up to date (I thought it might help with Lollipop compatibility). So I decided on TWRP, and I got the latest version (2.8.4.0 as of now) and flashed it. Successfully flashed, then rebooted recovery. TWRP is there and working. Great. Next step... I had the Lollipop ROM and Gapps already downloaded and ready to go, so in TWRP, I proceeded to wipe everything (system, data, cache, internal sd).
Uh oh... Half way through wiping, the phone reboots itself! Now there's no ROM, so naturally it has nothing to boot to. Try going back to TWRP, and I see the splash screen again. OK, false alarm... Well, not really... Because now it just reboots itself after the splash screen, every time. Can't get into TWRP no matter what! I can access download mode, but Odin doesn't recognize the phone. Yes, I have the drivers. In fact, the device isn't detected by Windows at all.
So here we are. Download mode boots, but Odin doesn't work because there's no communication through USB at all. There's no ROM on the phone because it was wiped. And TWRP won't boot beyond the splash screen.... Now what?? I tried the 80MB MK5 debricking .img on a 64GB microSD. It does nothing - besides, USB isn't reading anyway, so it's not like I can proceed with Odin.
I'm at a stalemate here... Any suggestions?
My friend's gonna kill me if I killed his phone I'm pretty experienced with several devices, but not much with Samsung. I've never seen anything like this happen before...
When connecting to the computer, have you tried different USB 2.0 ports and USB cables? Have you tried different computers? Different operating systems?
Is the phone recognized using adb or fastboot commands?
audit13 said:
When connecting to the computer, have you tried different USB 2.0 ports and USB cables? Have you tried different computers? Different operating systems?
Is the phone recognized using adb or fastboot commands?
Click to expand...
Click to collapse
Yeah, I figured that would be the case. Just about done downloading Ubuntu which I'll boot from USB. I'll post back with results once that's ready. I should have it booted within 10 minutes. Once I get there and verify the phone connects, what would be my next step? Should I try flashing stock 4.3 first?
I would confirm the bootloader that is on the phone before flashing anything from sammobile.com.
You may be able to use fastboot commands to get the information by typing fastboot getvar all.
OK, in Linux now. ADB/fastboot won't connect. Tried different USB ports and cables, ones that I know work. No luck...
The only thing I can boot to in the phone is Download mode, so that's where I'm trying from.
For the record, ADB picks up my Nexus 5, so I know it's all set up right.
I'm gonna retry the debrick img, using dd to write it this time.
Bloodflame said:
OK, in Linux now. ADB/fastboot won't connect. Tried different USB ports and cables, ones that I know work. No luck...
The only thing I can boot to in the phone is Download mode, so that's where I'm trying from.
For the record, ADB picks up my Nexus 5, so I know it's all set up right.
I'm gonna retry the debrick img, using dd to write it this time.
Click to expand...
Click to collapse
No luck. wrote to the SD successfully, and it just boots to download mode. Nothing else.
ADB and fastboot still do nothing
Maybe the phone's USB port is flaky?
Have you tried Kies to see if it recognizes the phone?
audit13 said:
Maybe the phone's USB port is flaky?
Have you tried Kies to see if it recognizes the phone?
Click to expand...
Click to collapse
I don't have Kies, but I'm doubting that would work anyway. There's absolutely no communication between the computer and phone. Nothing happens when I plug it in. No sound, no indication anything was even plugged in. Running lsusb in a terminal doesn't show the phone either.
Edit: Downloading Heimdall (Linux-compatible Odin)...
Bloodflame said:
I don't have Kies, but I'm doubting that would work anyway. There's absolutely no communication between the computer and phone. Nothing happens when I plug it in. No sound, no indication anything was even plugged in. Running lsusb in a terminal doesn't show the phone either.
Click to expand...
Click to collapse
Okay, forget kies. Sounds like a USB port issue. Does the phone start charging when connected to a power source?
audit13 said:
Okay, forget kies. Sounds like a USB port issue. Does the phone start charging when connected to a power source?
Click to expand...
Click to collapse
Plugging into the wall makes the phone vibrate every couple of seconds, but nothing shows up on screen, and there's no indicator light.
The vibrations lead me to believe it's detecting something, but no indicator light worries me (unless that's just because there's no kernel)
The red light does come on if I plug it in without the battery.
Heimdall fails to detect the device as well (no surprise there)
If the phone was bricked, it would usually be recognized as a some sort of device under Windows' device manager which leads me to conclude that it is a USB port issue.
audit13 said:
If the phone was bricked, it would usually be recognized as a some sort of device under Windows' device manager which leads me to conclude that it is a USB port issue.
Click to expand...
Click to collapse
I agree that it is weird, because it's not coming up as a device at all, in either Windows or Linux, yet it does receive power.
I'm guessing here but it appears to me that the only left to try is a debrick image. Is it possible the battery is drained and needs to be charged?
audit13 said:
I'm guessing here but it appears to me that the only left to try is a debrick image. Is it possible the battery is drained and needs to be charged?
Click to expand...
Click to collapse
The debrick image is what I've been trying. It's on a 64GB microSD. And I made a new one from Linux a few minutes ago (booted back to Windows now).
The battery was about 80% before all this started, and the phone powers on without being plugged in, so I doubt it's the battery.
Maybe you need a different SD card? Based on posts I have seen, it seems that certain brand/size combinations work while others don't.
audit13 said:
Maybe you need a different SD card? Based on posts I have seen, it seems that certain brand/size combinations work while others don't.
Click to expand...
Click to collapse
I only have one card over 16gb...
Either way, I still have the USB problem. I'll need USB to flash with Odin. The debrick card only seems useful when Download mode isn't working, but that part works fine on the phone, even without the debrick card. My problem is with recovery. If I could run that from the SD, I think I would be fine - just flash a ROM. But I'm not finding anything for that (not surprised).
I thought it could potentially be a corrupt driver, so I tried using USBDeview to uninstall all disconnected devices. I tested it with a portable hard drive, which indeed had to reinstall after. So the program works as intended. However, the phone still isn't detected when I plug it in. No sound, no notification saying it's installing or install failed - absolutely nothing. Power goes to the phone through USB, with multiple cables and USB ports. Just no data connection.
I'm starting to think there's just nothing I can do...
The phone may need a USB port replacement. I know of no way to push recovery to the phone from as SD card without USB capabilities.
audit13 said:
The phone may need a USB port replacement. I know of no way to push recovery to the phone from as SD card without USB capabilities.
Click to expand...
Click to collapse
Yeah, that's what I'm thinking. Found this, and it's cheap enough... But that shipping!
You'd be better off getting it from China with free shipping. The problem is the amount of time required to get the part.
Maybe contact a cell repair shop to see how much it would cost to have them replace it. Soldering is not my strongest skill
audit13 said:
You'd be better off getting it from China with free shipping. The problem is the amount of time required to get the part.
Maybe contact a cell repair shop to see how much it would cost to have them replace it. Soldering is not my strongest skill
Click to expand...
Click to collapse
Yeah, doesn't look easy. I already tore down to here, and visibily, it looks OK. I'm not so sure about soldering either :silly:
I appreciate your assistance.