Related
Hi all.
I have a problem with my Desire.
I can't charge my phone when i connect it to my computer, i have to turn it off in order to charge it. I can't use it with my computer as an usb device.
It may help you, i have this problem with some roms. Now i use an RUU with root access and the problem is still there.
If you have any questions that might help you to help me, i will answer them.
Nobody?
Anyone doesn't have the same problem?
Does this happens on other computers too.
Try installing htc sync, just for the drivers, and then remove it.
Yes, i tried several times.
It still doesn't work
Different usb cable?
Sent from my HTC Desire using XDA App
do you have a custom rom? if yes download the file from here http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
and flash through recovery. reboot to see it working.
Does it charge on AC?
If so...that's normal. The phone draws less power from the cable when connected to USB. When connected to an AC adapter it will draw all it needs.
If that's your problem follow this link for more info and a fix.
http://forum.xda-developers.com/showthread.php?t=844284
almost sure he has a usb brick. let him follow the modaco link to read about his symptoms. he has a corrupted misc partition.
mariosraptor said:
almost sure he has a usb brick. let him follow the modaco link to read about his symptoms. he has a corrupted misc partition.
Click to expand...
Click to collapse
I agree with Mariosraptor.
Even though usb supplies less power, it still should show a charging indication.
Sounds like the misc partn problem. Flashing a modded misc partn should fix it.
Thanks guys.
It worked.
That was an USB brick.
Now i know how to fix it.
Thanks again
that is indeed nice to hear mate. good job!!!!
Hi there! First of all I don't speak english very well.
My Galaxy Nexus hard bricked yesterday.
tl;dr no boot animation, no recovery mode, no download mode, no response from computer.
I thought it had just a low battery level, I found it turned off. So I tried to recharge it but it gave no signals, no battery icon, nothing.
After an all night long recharge I tried to turn it on, to enter in download mode or in recovery mode but nothing works. I also tried to connect it with my computer with and without battery, no response, no "OMAP" device found, no sound from Windows for plugging it in, nothing.
I found this thread here in xda, many people has been redirected to it and found their solution to the brick problem.
I tried to follow all the steps but when I plug in the phone and start the .bat file nothing happens, just stuck on "Waiting for device".
The phone is unlocked and rooted. I'm running AOKP JB-MR1 Build 2 and Franco Kernel for a month, never had problems with them, never installed other ROMs after that.
What should I do now? Should I try to do something or just bring it to a support center? The phone is still in warranty, there would be any problem because it has a non-stock ROM?
I've red about a jig to force the Odin mode, should I buy it? (I found this one)
Thanks for the help.
Have you tried booting into Odin mode
ntb81 said:
Have you tried booting into Odin mode
Click to expand...
Click to collapse
Yes, it doesn't work.
have you your warranty on it?
return it and get a new one
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Beauenheim said:
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
Click to expand...
Click to collapse
Yeah, that's why I'm not sure to send it in for warranty. So have I to try with a JTAG first?
[bman123] said:
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Click to expand...
Click to collapse
I'm not understanding that too, I don't know what happened. Suddendly it stopped working. Maybe is just a battery problem, I'll try to use another one before bringing it to the shop where I bought it.
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
---------- Post added at 06:12 AM ---------- Previous post was at 06:02 AM ----------
galiganu said:
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
Click to expand...
Click to collapse
so right after I wrote that I plugged my phone into USB of my PC without battery. when I inserted the battery it started showing me the battery sign and I could started the phone. 3 minutes later it went black again, but the trick didnt work again.
any ideas? thanks
Try This !!
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Tech.Nik said:
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Click to expand...
Click to collapse
Please could you explain a bit more how to go about this? I have a Verizon Galaxy Nexus in a somewhat similar condition. This one is recognised as an OMAP 4430 device. I downloaded OMAP Flasher, installed drivers and tried to bring it back to life but after running the batch file I get this error: Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE). Can the resistor trick work on this and if yes, how can I go about it? I am not faint-hearted; I think I can handle it if given the right instructions.
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
galiganu said:
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
Click to expand...
Click to collapse
Yeah, the faulty USB port is a very common issue.
Since yesterday my phone refuses to charge while booted into android (CM 10.1.2 Stable).
However it has absolutely no problems charging while turned off, in bootloader or hboot.
Also it will not be detected by PC usb so I can't flash a different ROM. What the hell is going on?
How do I get out of this mess?
Just to be clear I've already hard resetted the phone. It would appear that the usb drivers on the phone are to blame?
Need some help guys.
satwikpanda said:
Since yesterday my phone refuses to charge while booted into android (CM 10.1.2 Stable).
However it has absolutely no problems charging while turned off, in bootloader or hboot.
Also it will not be detected by PC usb so I can't flash a different ROM. What the hell is going on?
How do I get out of this mess?
Just to be clear I've already hard resetted the phone. It would appear that the usb drivers on the phone are to blame?
Need some help guys.
Click to expand...
Click to collapse
Install HTC drivers in your PC again.
virgolib said:
Install HTC drivers in your PC again.
Click to expand...
Click to collapse
Here's what I've tried so far:
Reinstalled HTC drivers
Installed a different recovery
Installed a different ROM with a stock kernel
VOodOO magic
Nothing has worked so far.
If I turn the phone off I can use adb to flash ROMS and such. However USB will not work when the device is on:
No charging or data transfer over USB. Otherwise phone appears to be working perfectly.
satwikpanda said:
Here's what I've tried so far:
Reinstalled HTC drivers
Installed a different recovery
Installed a different ROM with a stock kernel
VOodOO magic
Nothing has worked so far.
If I turn the phone off I can use adb to flash ROMS and such. However USB will not work when the device is on:
No charging or data transfer over USB. Otherwise phone appears to be working perfectly.
Click to expand...
Click to collapse
Hace you open USB debugging on?
virgolib said:
Hace you open USB debugging on?
Click to expand...
Click to collapse
Yes its on.
My digitizer has also been wonky lately. Wondering if the 2 issues are related.
satwikpanda said:
Yes its on.
My digitizer has also been wonky lately. Wondering if the 2 issues are related.
Click to expand...
Click to collapse
It's was happened to me with Sony Xperia Z, when usb debugging on all are working, but actually it's not a normal condition.
My pc is windows64bit and happening this problem so changed to win32 all are OK, So I think this may be driver conflict in PC.
Therefore if possible you try with another PC.
virgolib said:
It's was happened to me with Sony Xperia Z, when usb debugging on all are working, but actually it's not a normal condition.
My pc is windows64bit and happening this problem so changed to win32 all are OK, So I think this may be driver conflict in PC.
Therefore if possible you try with another PC.
Click to expand...
Click to collapse
Tried different cords and PCs.
Even wall chargers do not work.
Also comfirmed that a middle strip of around 10% of my screen area is dead to touch.
All signs indicate hardware damage. Might take it to HTC to get fixed now.
satwikpanda said:
Tried different cords and PCs.
Even wall chargers do not work.
Also comfirmed that a middle strip of around 10% of my screen area is dead to touch.
All signs indicate hardware damage. Might take it to HTC to get fixed now.
Click to expand...
Click to collapse
Yes it will be sure hardware failure, sorry.
Been trying to figure this out for the last few days, Google support has been too. I've tried the basics, different usb cord stock and not, factory reset going to stock, different kernels, different roms.
I can only get my nexus 7 2013 to charge when I go to bootloader, then to power off, then uplug the cord and plug back in fast. Once the device is on I get nothing when I plug the usb in, computer or AC. I used to be able to connect to PC no problem. I use the OTG cable a lot for HDDs and my camera, now nothing works. Tried USB debugging on and off and MTP.
I would just say the usb port broke somehow and go for an RMA but since it charges while it's off I feel like it's software related... If you guys have any suggestions I would really appreciate it.
morgang321 said:
Been trying to figure this out for the last few days, Google support has been too. I've tried the basics, different usb cord stock and not, factory reset going to stock, different kernels, different roms.
I can only get my nexus 7 2013 to charge when I go to bootloader, then to power off, then uplug the cord and plug back in fast. Once the device is on I get nothing when I plug the usb in, computer or AC. I used to be able to connect to PC no problem. I use the OTG cable a lot for HDDs and my camera, now nothing works. Tried USB debugging on and off and MTP.
I would just say the usb port broke somehow and go for an RMA but since it charges while it's off I feel like it's software related... If you guys have any suggestions I would really appreciate it.
Click to expand...
Click to collapse
If you've tried different kernels, roms, and I assume different a PC, USB ports, USB cable, then you've eliminated software as a possibility, as well as external hardware, I would do a backup, (unroot and flash back to stock and relock is applicable) then RMA it, you're only delaying the inevitable by waiting it could be some corruption in the emmc, or some other hardware fault that might act unreliably.
mdamaged said:
If you've tried different kernels, roms, and I assume different a PC, USB ports, USB cable, then you've eliminated software as a possibility, as well as external hardware, I would do a backup, (unroot and flash back to stock and relock is applicable) then RMA it, you're only delaying the inevitable by waiting it could be some corruption in the emmc, or some other hardware fault that might act unreliably.
Click to expand...
Click to collapse
Is there a way I can put it to full stock, bootloader and recovery through just the device. Since I can't connect to PC. The only way I came across was through the toolkits.
morgang321 said:
Is there a way I can put it to full stock, bootloader and recovery through just the device. Since I can't connect to PC. The only way I came across was through the toolkits.
Click to expand...
Click to collapse
Well, you can boot into a custom recovery I assume, so you can flash a rom from there (you can get zips from here), then you can root the device (needed for next step), that part is easy enough, the following is only theoretical, go into the OS, install that bootloader lock/unlock app, lock the bootloader, then unroot from within SuperSU (that last part I'm not sure of since you just relocked the bootloader, so not sure if it will work.) Of course even if all that did work, you will still have a custom recovery, so hopefully they won't see that, I believe there are apps which can install custom recoveries from within the OS, but I don't think they flash the stock one.
Maybe someone else more knowledgeable knows of a better/effective way and they will chime in and correct me, etc.
4963955171
mdamaged said:
Well, you can boot into a custom recovery I assume, so you can flash a rom from there (you can get zips from here), then you can root the device (needed for next step), that part is easy enough, the following is only theoretical, go into the OS, install that bootloader lock/unlock app, lock the bootloader, then unroot from within SuperSU (that last part I'm not sure of since you just relocked the bootloader, so not sure if it will work.) Of course even if all that did work, you will still have a custom recovery, so hopefully they won't see that, I believe there are apps which can install custom recoveries from within the OS, but I don't think they flash the stock one.
Maybe someone else more knowledgeable knows of a better/effective way and they will chime in and correct me, etc.
Click to expand...
Click to collapse
I do think this will work. I don't think flashing a recovery voids warranty if you aren't rooted and unlocked... Thank you for the help man. Wish it wasn't RMA but is what it is...
morgang321 said:
I do think this will work. I don't think flashing a recovery voids warranty if you aren't rooted and unlocked... Thank you for the help man. Wish it wasn't RMA but is what it is...
Click to expand...
Click to collapse
No problem, good luck, let me know what happens.
mdamaged said:
No problem, good luck, let me know what happens.
Click to expand...
Click to collapse
I just did another factory reset. This time with Elemental kernel, stock 4.4.2 from google. Probably the 4th time I've factory reset but first time with this kernel. All of a sudden I got ADB connected to PC, first time I've had any response from usb while tablet was up and running for 3 days. Might not have to RMA after all
morgang321 said:
I just did another factory reset. This time with Elemental kernel, stock 4.4.2 from google. Probably the 4th time I've factory reset but first time with this kernel. All of a sudden I got ADB connected to PC, first time I've had any response from usb while tablet was up and running for 3 days. Might not have to RMA after all
Click to expand...
Click to collapse
I hope it stays fixed, sometimes problems caused by hardware can be intermittent. Keep testing it daily.
I need help, my ZF2 suddenly cannot be detected by my windows 7 laptop and pc. When I tried to plug in usb 3 port, it wont get detected. If in usb 2/1 port, it will be detected but with the yellow exclamation mark. I tried updating mtp but it wont update (shows device is up to date). I tried reinstalling ROM and factory reset thru the ROM, but still not working.
I returned to stock but still it wont get detected on my pc or laptop. I ****ed everthing up when I returned to stock since I cant root it back anymore since it wont get detected by adb.
Evereything is up to date including 15sec adb installer 1.4.2 or 1.4.3 and intel usb driver 1.10 from 1.9.
I will try to reformat thru stock recovery and see if it will work. But before doing that, any suggestion or ideas?
Does it charge while connected to the laptop?
Have you tried using other micro USB cables?
FrameCall said:
Does it charge while connected to the laptop?
Have you tried using other micro USB cables?
Click to expand...
Click to collapse
Yes, it charged when I plugged it on different port. And yes, I have tried different cables, samsung, asus and dont know brand chords. All cables only shows usb device malfunction code 43 and all charged my phone when plugged to ports.
Anybody? Suggestions? Ideas?
Anyone?
Can you check and see if fast charging works?
24imelqui said:
Anyone?
Click to expand...
Click to collapse
Which recovery you installed?
trinimike100 said:
Can you check and see if fast charging works?
Click to expand...
Click to collapse
Fast charging dont work anymore. It will take atleast 2 hrs to charge the phone.
mr_gourav2000 said:
Which recovery you installed?
Click to expand...
Click to collapse
I used to have a twrp 3.0.0-0 recover then flash .165 recovery then flash .165 stock ROM. And after reboot, still cant get detect by any port. It just charged my phone. Then I updated to .174 but still no detection.
24imelqui said:
I used to have a twrp 3.0.0-0 recover then flash .165 recovery then flash .165 stock ROM. And after reboot, still cant get detect by any port. It just charged my phone. Then I updated to .174 but still no detection.
Click to expand...
Click to collapse
Try this.
http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
mr_gourav2000 said:
Try this.
http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
Click to expand...
Click to collapse
I have already returned to stock rom and recovery all is good, but my problem still exist. I cant get my phone to get detect by my PC or laptop. It just charged and it show usb device malfunction code 43. I got all drivers installed since I was able to root and flash custom roms before. Im asking if hard reseting thru stock recovery will fixed my problem and if you have any others ideas please share. Like how to root my device again without using pc/lwptop.
24imelqui said:
I have already returned to stock rom and recovery all is good, but my problem still exist. I cant get my phone to get detect by my PC or laptop. It just charged and it show usb device malfunction code 43. I got all drivers installed since I was able to root and flash custom roms before. Im asking if hard reseting thru stock recovery will fixed my problem and if you have any others ideas please share. Like how to root my device again without using pc/lwptop.
Click to expand...
Click to collapse
Try this may help you -
Switch off mobile
Plug in usb and connect to laptop or pc.
Now power on your mobile.
Look what happened?
mr_gourav2000 said:
Try this may help you -
Switch off mobile
Plug in usb and connect to laptop or pc.
Now power on your mobile.
Look what happened?
Click to expand...
Click to collapse
Still usb device malfunction code 43. Thanks man
I had the same issues when my Zenfone's chip set fried - PC did not recognise the phone, phone did not recognise USB drives, fast charging not working. To be precise what happened: one day I plugged in the cable (original one, with original charger), the phone showed high temperature warning and shut down. Then after a while I turned it back on but USB wasn't working any more, except for the slow charging. Sent in for a warranty repair, it was stuck there for like 2 months before they sent me a new phone.
Had the same problem, it turned out that my zenfone 2's charging port and microphone had been damaged. Replaced the parts from a third party repair man as my warranty was void. He returned me a very well functioning and no more problematic zennie within a week
It surely isn't a software problem..
Hope it helped..
Abhishek1108 said:
Had the same problem, it turned out that my zenfone 2's charging port and microphone had been damaged. Replaced the parts from a third party repair man as my warranty was void. He returned me a very well functioning and no more problematic zennie within a week
It surely isn't a software problem..
Hope it helped..
Click to expand...
Click to collapse
j4nitor said:
I had the same issues when my Zenfone's chip set fried - PC did not recognise the phone, phone did not recognise USB drives, fast charging not working. To be precise what happened: one day I plugged in the cable (original one, with original charger), the phone showed high temperature warning and shut down. Then after a while I turned it back on but USB wasn't working any more, except for the slow charging. Sent in for a warranty repair, it was stuck there for like 2 months before they sent me a new phone.
Click to expand...
Click to collapse
I have the same problem also. Can you tell me what part needed to be replaced? I already tried replacing the usb sub board but it did not work.
trinimike100 said:
I have the same problem also. Can you tell me what part needed to be replaced? I already tried replacing the usb sub board but it did not work.
Click to expand...
Click to collapse
I went to a 3rd party repairman and he said he just replaced the flex data cable or something like that, he also said it is common for zenfone smartphone. Then my phone is detectable again.