Hi
I had this tablet for about two years, ran amazon Fire toolbox on it and everything was fine.
Couple of days ago it turned off, I think the battery level was around 15%. I was not able to turn it back on.
I decided to charge it overnight. Next morning I tried to turn it on but it stuck on Amazon logo.
I tried to do Power + Volume and was able to see the menu, attempted to do restart, then factory reset - and had this bunch of errors. Then I did the power down from the menu, and after that it doesn't turn on even to recovery any more, the screen is black, no logo, no backlight.
When I connect it to computer (the same I ran amazon fire toolbox on) there is an unknown device, but that's it, adb and fastboot don't see any devices.
Update: another windows machine recognized it as a Mediatek USB port and was able to install drivers.
When connected, it appears to be in a loop - Mediatek USB port device appears and in several seconds dissappears, in cycle.
Any help will be highly appreciated!
Thank you!
undersky said:
Hi
I had this tablet for about two years, ran amazon Fire toolbox on it and everything was fine.
Couple of days ago it turned off, I think the battery level was around 15%. I was not able to turn it back on.
I decided to charge it overnight. Next morning I tried to turn it on but it stuck on Amazon logo.
I tried to do Power + Volume and was able to see the menu, attempted to do restart, then factory reset - and had this bunch of errors. Then I did the power down from the menu, and after that it doesn't turn on even to recovery any more, the screen is black, no logo, no backlight.
When I connect it to computer (the same I ran amazon fire toolbox on) there is an unknown device, but that's it, adb and fastboot don't see any devices.
Update: another windows machine recognized it as a Mediatek USB port and was able to install drivers.
When connected, it appears to be in a loop - Mediatek USB port device appears and in several seconds dissappears, in cycle.
Any help will be highly appreciated!
Thank you!
Click to expand...
Click to collapse
Your eMMC probably died (notice the input-output errors), try to use amonet. If the script reports "read error" then nothing can be done.
Related
Looking for thoughts and suggestions.....
My Vadafone 845 (Huawei U8120) went through the wash the other day. I took the battery out as soon as I found it and let it dry out for 2 days... turned it on and nothing.
So I baked at 60 degrees for a couple hours (with the battery removed) and now it turns on but doesn't boot the OS. I just hangs on an hourglass in the middle of the screen.
Interestingly, the phone will not turn on when the charger is connected or if it is connected to USB. If I turn the phone on and then connect the USB, the phone doens't turn off... I can even remove the battery and the power via USB keeps it going. Unfortunately, the computer does not register that a device is connected.
Recovery and bootloader modes don't work.
I can however get into firmware update mode and was even able to successfully update the firmware.... with no change to the phones behavior.
So does anyone have any thoughts on how I might be able to resurrect my phone?
Hi,
so if you have seen of a thread directly relevant to this please post the link...
My HTC Desire is bricked to the point it won't even display anything on the screen.
I have had Cyanogen7 installed for over a month. It was working OK, then I power cycled it. It did not boot fully, restarting at the swirly arrow cyanogen screen. Next, I entered boot loader, and exited that when I removed the battery. I then required HOME and MENU buttons to be pressed in addition to VOL DOWN + POWER in order to enter boot loader.
It took 35 seconds to leave the initial splash screen.
It took an extra 10 seconds for the OS to hit the point where it restarted, and it stayed constantly restarting the swirly arrow cyanogen screen every 10 seconds.
And now the piece-de-resistance – I installed the Android SDK, hoping to run fastboot to at least recover my data. After SDK installed I connected the Desire to my PC, and now it won't even turn on. Before the SDK USB drivers were installed it would enter HBOOT. Now, absolutely nothing. Not even a splash screen. Tried all button presses when turning on, removing SD and SIM, left battery out for 1 min, still nothing.
After following the instructions here:
wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
I installed the generic USB divers, and power cycled my PC. Left the USB cable connected for 10 min in-case the battery had run down (battery sitting at 3.2V). Still no joy.
This is the worst value paperweight I have ever bought.
Any advice on how to recover this would be great.
-WT.
So, I am in new territory here. My tf300t suddenly stopped working. I had previous unlocked the tablet (years back) but never installed a custom rom. It was working fine for a few years and I factory wiped along the way a couple times. So a couple months ago I did a factory reset again and it seemed fine for a few weeks. Yesterday I picked it up and I can't get it to turn on. Here are the symptoms:
It will charge and shows a green LED
Can only get a Black screen and will not boot, no ASUS screen or anything
I tried holding power for 30 seconds
I tried holding power and volume down for 30 seconds
I tried the tiny reset hole with a paper clip and the same with power button
When I connect to my computer with a USB it shows up as APX on Windows 10
Is it just dead now? Bricked? Thanks for any insight! Seems strange but maybe it decided to die.
teedoe said:
So, I am in new territory here. My tf300t suddenly stopped working. I had previous unlocked the tablet (years back) but never installed a custom rom. It was working fine for a few years and I factory wiped along the way a couple times. So a couple months ago I did a factory reset again and it seemed fine for a few weeks. Yesterday I picked it up and I can't get it to turn on. Here are the symptoms:
It will charge and shows a green LED
Can only get a Black screen and will not boot, no ASUS screen or anything
I tried holding power for 30 seconds
I tried holding power and volume down for 30 seconds
I tried the tiny reset hole with a paper clip and the same with power button
When I connect to my computer with a USB it shows up as APX on Windows 10
Is it just dead now? Bricked? Thanks for any insight! Seems strange but maybe it decided to die.
Click to expand...
Click to collapse
I have no idea what happened to your tablet. If I were in your boots, I would install "Minimal ADB & Fastboot" from here: http://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/. Then please check whether the USB driver are installed or not. If not get them here: https://androidmtk.com/download-asus-usb-drivers.
Connect your tablet via USB with your PC. The devise manager should show "Android Phone" => ASUS Composite ADB Interface and "Portable Devices" => TF300
After that seen you have access via ADB to your tablet. Then please flash the latest Asus firmware update to get your tablet on a clean stock rom. For assistance please search the forum. Good luck!
Hi. First of all, thanks for taking the time to read this. I know it's a long post, I'm just trying to be as detailed as possible.
I've a Moto G XT-1032 that stopped working a couple days ago. It has the original battery, original software. It didn't came with an original charger, so I have been using a Samsung Galaxy Tab one. The phone is almost two years old.
This is how it all started: It had low battery. When I got home it connected itself to the wi fi, and tons of whatsapp messages came at the same time. It went off.
I thought maybe it had drained the battery. Plugged it in to charge, didn't get the led on, and the battery showed 0% for an instant. Then the phone turned itself on, got the M logo and then the screen went black (like... some sort of backlight is on, but the screen is just black)
I turn it off, and it goes back on. No battery image, straight to the M logo, and then black screen. I tried holding power + vol down keys for more than 120 secs, finger pain is the only I got. It can access fastboot mode, but doesn't matter which option I pick, normal powerup, recovery, factory... I select them and then press vol up, but it just goes to the white screen with the M logo, then black screen.
When I plug the charger, and go to fastboot mode, it doesn't show battery charging. Just says battery low (or battery ok). When I plug it to the computer via the usb cable, and access fastboot, it shows battery charging.
The computer doesn't detect the device at all. First time I plugged it, it tried to install drivers, but failed. I downloaded them from motorola's page.
If I open motorola device manager, it tells me there aren't updates for my phone... So... I guess it's recognizing it? But I still can't see it. Windows only shows me my C and D drives, but not the phone. Tried different usb cables, different usb ports. Nothing changes.
I sent it to a service, they tested the battery and charging port, they said those were fine. But didn't find the problem.
Any ideas? Suggestions?
Thanks in advance!
I have a Pixel 3 that decided to randomly shut off and not turn on anymore. An Android update applied today, all was fine. Battery wasn't low. It warms up when charging, but no other signs of life, nothing on the screen when charging, no status lights, no haptic feedback. I tried holding power for 30+ seconds and nothing happens. I charged it for hours and still nothing.
If I plug it in to my PC it appears in device manager as a Qualcomm com device. I installed the Qualcomm flash utility and I can see the device but that is it. I can't get it to boot to recovery or anything as it simply does not power on in any way. I can't get ADB to recognize it connected and can't boot it to get it into developer mode.
It is in great shape, is treated gently, not sure what went wrong. My wife uses it often for gaming and uses it while charging frequently, maybe it was just too much.
I think I am just screwed, but maybe an image exists that is compatible with the Qualcomm flash utility? I haven't been able to find one, and the image supplied by Google doesn't look to be the right format.