So I was having battery issues when I noticed my OTG had stopped working. But what's worse was the USB port was not either, so now I have no way to use fastboot and RSD Lite. Not good. So I installed a new OEM battery and USB port. The battery would not even take a charge and phone just bootlooped instantly. Reinstalled original battery, which now seemed to be charging much better for some reason. But the USB port still did not work, although it will now register as a unrecognizable device on Windows 8. A pop-up says there's an unknown issue with the device and to try again. Drivers are fine. I really want to restore the phone to original factory settings, meaning the original boot kernel, etc. I had upgraded the fastboot, radio, and recovery to a material look and I doubt that is related, but I still want it factory so that it will take OTA updates and I can sell it to someone who just wants a phone which does what your average owner needs it to do, lol. So anyone have any ideas? Is the main board toast?
Delete the drivers and reinstall.
Already done. No help but ty.
I forgot to say that I have 2 Nexus 5's, I upgraded to the 32Gb when my original 16Gb started having battery issues, which, I might add, I resolved this morning by booting into bootloader and allowing it to charge in that state, so it stopped looping the "dead battery loop" as I called it, and charged up to 95% by the time I rebooted into the OS. Seems to be working fine now, will check battery drain soon, but focusing on the OTG/USB port issue. I'm thinking the battery issue is related. I think I somehow connected it to too much amperage and cooked the main board's USB infrastructure, if that makes sense. So it might explain the battery issues also. Now it has a new battery, and all is well there at least. Oh, and I get a screen I have no idea where it came from. It comes up only when the charger is connected but the phone is off. I will try to get it up on here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://www.dropbox.com/s/mc3lakd26parpdd/IMG_20151129_134355.jpg?dl=0
Idk if that first try came out ok cuz I don't see it on my phone, so I put up a link, does anyone have any idea why that is coming up when plugged in and not turned on? Weird.
And does anyone want a N5 16Gb w/ unlocked BL, MultiROM flashed and stock, rooted Android 6.0 and CM 12.1 installed? Cheap money? It just can't be connected via USB except to charge. But battery is brand new, ? Great as a dev device, should keep getting ROMs and official updates for years to come, look at the N4, still getting love, and the N5 is far more popular.
Oh, and screen is mint condition, and casing is good but for a couple little flaws, but it's a great functioning phone but for the OTG and fastboot problem. But no matter, it can be worked around, just don't fully wipe it, lol
Related
Hello XDA-members,
I hope you can help me, I've been browsing this forum for quite a while now and I actually am rather optimistic looking at the high amount of leet tweakorz populating this place :> Shouldn't cheer too early though.
I've got some details which might be required in order to analyse the situation.
About a week ago, I downgraded to stock Milestone EU ROM 2.1, coming from the G.O.T. 2.2.1 custom rom, due to the power drainage which I thought was the price of the custom ROM.
I browsed around the interwebz in order to find a custom froyo rom not sucking ma powaz, but in fact I found out that the power drainage could be caused by failing to clean out the cache (including dalvik, etc) before flashing a custom rom. So, before I installed the stock ROM, I made sure I properly did this, after the installation I cleaned it again and then installed the G.O.T. 2.2.1 again , through the new OpenRecovery v2.0.1. Rooted it, installed the custom theme they included with the ROM, and overclocked it to I think 800 Mhz.
After this, everything worked fine for about 1,5 weeks, although I noticed it started to suck power again (60% gone in a night of a nice, cozy, sleepy rest without any applications, wi-fi or 3g connection on background), so I did something incredibly stupid. Still a bit sleep-drunk, I went into the openrecovery menu and cleaned the cache, dalvik and (I think it's) clear settings.
After rebooting, I noticed the theme that GOT included was replaced for the standard layout for froyo. Also, the device was barely responding to my commands, for about 5 minutes. I rebooted it, and after about a minute of processing it worked fine.
I didn't get to know if this was actually increasing battery life again, because I went to sleep yesterday night with the phone having about 40%, and this morning I woke up and the phone was empty (at least, so I thought). A few hours ago I connected it to the charger, later I found that the phone wouldn't power up anymore. It simply doesn't react to the power button, screen doesn't show power or anything. I also tried power button in combination with x, or camera, but both methods didn't do anything as well.
So, that was it. Maybe those were a bit too much details. TL;DR: I installed a custom rom, cleaned out all the cache, and my phone won't start up anymore. I hope anyone knows this problem, and possibly a solution?
Thanks for reading, Bullehr
Men i have the same problem with my girlfriend milestone .
Try to take out the battery for a minute and then put it back again, that's do the trick for me .
Sorry for my English it's not my native language
The problem generally is given by the fact that the phone needs some power to "boot" in power charging mode. What you need is a second battery, or a little trick to charge the battery...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I cut an usb cable and used it directly on battery-phone contacts
I have flashed back to stock once again. I accepted the EE4 update and still I am without HDMI out.
Also when I try to set up the TV Out shortcut with Any Cut...every time I open it, it force closes saying that com.android.settings has unexpectedly quit.
It also happened with the SIM Toolkit.
I wiped this phone a hundred times and tried all various roms. What has been damaged?
Stay stock and go to the store, warranty replacement
Sent from my SCH-I510 using XDA App
The Droid Charge is covered under manufacturer's warranty for 1 year, correct?
My HDMI port hasn't been able to play audio, ever. I purchased a couple different adapters and cables while testing, nothing worked I'm thinking my best bet would be to take it to a Verizon store to get a new one?
WWWAAAAAA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's a software issue....it's gotta be!!!
The HDMI used to work fine. This is God punishing me. I like stock....I just wanted TW4 on my phone. I didn't wanna root it again, but they made me do it.
WWWAAAAAA
Rominucka said:
WWWAAAAAA
It's a software issue....it's gotta be!!!
The HDMI used to work fine. This is God punishing me. I like stock....I just wanted TW4 on my phone. I didn't wanna root it again, but they made me do it.
WWWAAAAAA
Click to expand...
Click to collapse
Could it be the cable? I bought a cheapo $6 hdmi cable and my kids kinked it; now it doesn't work.
I am such a *****.
It's either the cable or the TV.
I just checked with a new cable on a different TV and it worked.
I forgot to bring my cable to the store because I was a little preoccupied with the fact that my phone had no service and the stats showed no existing MEID or phone number when I woke up and I had to flash it back to ED1 yet again to fix that. What's odd, is that now my Device ID has been wiped from the VZW system (i'm a rep); it just shows my SIM, which (I was told) is all I really need.
I gotta stop ****ing with this thing. At least if I felt like I was learning something it would be OK, but I'm going around in circles here.
I'm still getting force closes on the TV Out hidden menu. I have an idea though.....open the Charge here at the store, load the TV Out shortcut and see if it quits. If it doesn't I'll be PISSED!!!
Rominucka, you ever get the TV Out forced closed issue resolved? I'm seeing the same behavior after rolling back to FE from GB (multiple ROMS, .pit wipes, EE1-EE4 upgrades, stock/3rd-part kernels, etc, etc, etc...). All FE builds give me a FC on TV Out (and at least one other, but I don't recall if it is the SIM Toolkit like yours or not).
As a side note, HDMI doesn't work (it recognizes the cable and the sound quits playing, but it does not mirror the image). I suspect it may be the cable (paid all of $2 for it) and will try a different cable&TV this weekend to see.
I'm just flashed to 1.7. Was on 1.6 and had this problem. I can't connect to any pc's over usb. I just bought a new cord because the original was sucked into a vacuum.
Anyways when I plug in the TF to a pc I get a bubble pop up that says "the connected usb device as malfunctioned"
Or on my wifes pc it tried to install the driver but it always fail. I have uninstalled and reinstalled the asus pc suite but it hasn't helped anything.
I'm getting worried its a hardware issue any help would be awesome!
Heres a shot of the error I'm getting.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas out there?
Yeah i'm now getting the same problem. I'm using prime 1.9.1 and also i have re installed the suite/drivers. I would really like it if someone could give this question an answer. Also i have Windows x64
did you enable usb debugging on the tf?
Yah it sucks I never got mine working. Now the battery is draining over night if I leave it unplugged, thats with wifi off. But I can't even consider rma over the usb because it is rooted.
I'm also facing the same problem. Detection on my pc is like a hit & miss affair. Wonder if this got to do with a faulty usb/data cable?
greeny2010 said:
I'm also facing the same problem. Detection on my pc is like a hit & miss affair. Wonder if this got to do with a faulty usb/data cable?
Click to expand...
Click to collapse
I replaced mine with an asus cable. Not some knock off, and it didn't help anything.
I returned one not long after purchasing because of a similar issue. Tried on many PC's and different cables, made no difference. I think it is a hardware fault, reasonably common too. Can you not flash back to stock to RMA?
iGBH said:
I returned one not long after purchasing because of a similar issue. Tried on many PC's and different cables, made no difference. I think it is a hardware fault, reasonably common too. Can you not flash back to stock to RMA?
Click to expand...
Click to collapse
The problem is you need to plug it into a pc to reflash it. I had a thread going on this before, I think someone recomended a method for that had came out where you could flash without a pc. I'm a little nervous honestly to mess with it because it something goes wrong without the usb port working its done.
So my TF101 appears to be completely dead. I had it rooted and rom'd running KatKiss 4.3,not sure of which number . I loved it too. Anyway, before it died, it rebooted and would not leave the "updating apps"screen so I did a factory install which fixed the problem but only temporarily. A few days later the same thing happened. This time I could not even reboot it. I left it charged overnight but could not get it to boot at all. I think I have tried everything. I tried booting with and without being on the keyboard dock, I have tried plugging into the computer, tried hdmi to a monitor to see if the screen went bad. I tried seeing if the computer recognized it in APX mode. NOTHING. The USB charges the keyboard dock but does nothing for the tablet. The computer does not see it period. It looks completely dead. It is out of warranty but I even called ASUS and all they would do is charge me $340 to send it in.
I would love to troubleshoot to see if it is a board or battery or whatever gone bad , but I cannot find anything on the Web. Can anyone help. Otherwise it's a lovely paperweight.
It's possible that the battery has come to the end of it's life and won't hold any charge, which would explain why APX mode won't work, the PC can't power on the TF via USB, only trickle charge it while it's powered off / screen is off, but if the battery is dead then that's not gonna happen either
Not sure if the charger needs the battery for it to power on the TF too or not
You could try disconnecting the battery and plugging in the charger
Here is a good teardown video to show exactly how to get that done
https://www.youtube.com/watch?v=k-6dKsGJ4VY
Im not 100% sure, but if the dock battery is fine, you could check and see if the connections are the same and swap them over
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Still DEAD
Detection,
Thanks for the awesome YouTube of breaking down the TF101. Unfortunately, I swapped batteries and still no good. Nothing happens. It looks like the old battery has power too, based on my multimeter. Is there anyone else with suggestions at this point or do I leave it as a nice paperweight?
THansk....
Apologies for resurrecting this thread. My TF101 (with dock) had also gone dead after running one of the KatKiss ROMs (maybe 4.2). Wouldn't charge, wouldn't turn on even to the bootloader or recovery. Charged it for days, nothing. I left it for dead and forgot about it for over 6 months. Uncovered it the other, dusted it off, charged it and it magically powered up. Everything was still on the tablet as it was before it went unresponsive.
My guess is that a microcontroller responsible for powering up the tablet got into a bad state. Even when powered off, these very low power microcontrollers remain on to handle the button press that powers on the device. It took the tablet being absolutely, fully discharged to clear it out of that bad state. Not just 0% as reported by the battery firmware, but a true complete emptying of the battery where its voltage drops below what the microcontroller needs to remain running.
Hopefully if you still have the TF101 after all this time, try charging it up all the way and see if it comes back to life.
i was looking though my closet today and found my old tablet, which got bricked 3 years ago when i switched to a new rom that screwed up my device
well i plugged it into my computer and then i got the battery charging screen you get when plugging in your device when it is turned off, but on the battery it is showing the loading circle on the battery, i have a picture of what im talking about
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
<- sorry for the low quality
when i try to attempt to get into download mode i cant get into it it just shuts off and i plug it in again and in around 5 minutes it will go back to the screen on the picture
i have installed the samsung drivers and kies, and i still cant get it unbricked, if possible, give me tips on how to resolve this issue, because a extra tablet could be handy
thanks,
justotirik
JustOtirik said:
i was looking though my closet today and found my old tablet, which got bricked 3 years ago when i switched to a new rom that screwed up my device
well i plugged it into my computer and then i got the battery charging screen you get when plugging in your device when it is turned off, but on the battery it is showing the loading circle on the battery, i have a picture of what im talking about
<- sorry for the low quality
when i try to attempt to get into download mode i cant get into it it just shuts off and i plug it in again and in around 5 minutes it will go back to the screen on the picture
i have installed the samsung drivers and kies, and i still cant get it unbricked, if possible, give me tips on how to resolve this issue, because a extra tablet could be handy
thanks,
justotirik
Click to expand...
Click to collapse
Keep it in charging for a few good hours and see if it goes somewhere in download or recovery. A hard brick won't even show a battery icon.
Without a working download or recovery mode, there is hardly any help.
Tried with another set of charger and cables?
billysam said:
Keep it in charging for a few good hours and see if it goes somewhere in download or recovery. A hard brick won't even show a battery icon.
Without a working download or recovery mode, there is hardly any help.
Tried with another set of charger and cables?
Click to expand...
Click to collapse
i would have a extra charger if my tab didnt have a iphone like charger instead of a micro usb traditional charger