What's the deal? I downloaded the rollback file on my computer. Put it on my kindle with USB. Performed update. Kindle updated to 3.2.8 just fine. Clicked finish install later. Turned off WiFi. My screen goes to sleep. Woke up kindle with the power button and swiped to unlock to see if it was still working. Kindle went back to sleep and now nothing responds, screen stays totally black. This is a brand new 2 day old kindle. I did this on my last kindle a week ago and the same thing happened. Is this some fake rollback? Its a 3rd gen 8.9 hdx with 4.5.3.
I find it hard to believe something is wrong on the kindle end being this is the second time happening.
Yes, I downloaded the correct file from another xda forum., before anyone asks.
Related
I rooted my kindle fire using kindle fire utility and after the root the kindle shut off and wouldn't come on. The charging light won't even illuminate when plugged in. I tried the 50 second hard reset and nothing happened. Any ideas?
Hi folks! Long time XDA lurker (Nexus 7, 10, and Samsung Galaxy Tab 2 7 forums), first time poster.
I picked up a XOOM off of EBay last week. The device ran well once I got it charged, it did software updates and was running on 4.0.3 with no issues until last night. I went to pop in a micro SD card, and when I pressed the power button to get it out of sleep mode, the screen began flashing colors, cycling between all colors, a checkerboard test pattern at one point, gradients from light to dark, etc. I did a bunch of Google searching last night and found one link where someone had the same issue, but no solution was mentioned. I have also looked here, but no luck. The one link I found last night seems to indicate it's some files from ICS getting corrupted during the update to 4.x, but it wasn't really clear whether that was the case or not.
I have tried the power+vol up button trick; that turns the screen off after a second or two, then the light show begins again. I can't find a way to shut off to be able to get it into recovery mode, and I have tried installing the Lord AIO tool but on running it, it seems to be stuck at the 'list of devices attached' section. Any ideas, other than letting the battery run down to nothing, then maybe it being able to get put into recovery mode? The place I bought it from on EBay does have a 14 day return policy, so I have a few days still to figure this out, but not sure how long it'll take to run the battery down. The light show on the screen does time out after about a minute or two, but I obviously can't keep hitting the power button every two minutes until it does finally drain the battery.
I really like the XOOM, it feels like you're actually holding something real & solid, compared to other tablets, and want to get this back up & running again. Any ideas what I can do next?
Hello all!
I'm having a few problems with my android tablet. 1st, a few months ago the tablet would not turn on after leaving it dead for about a week. I tried to charge it but it wouldn't work, so I left it alone for a few months. Today I decided to try to turn on my tablet and it came back to life! BUT when I turned it on, the tablet showed a white screen with lines going through it after the boot up process ended. I restarted the tablet and it went away. Unfortunately it keeps on doing weird things with the screen but only seems to do that when I'm browsing through the play store/downloading apps. I've restored my tablet as new and it's still giving me these problems. Also, now it won't recognize on my PC. It was recognizing a few minutes ago but now the tablet turns white when I plug it up to the computer. I've tried to look on google for help but I can't find any, also I've posted this on AndroidCentral but they've been no help to me at all... If anyone could at least lead me to the right direction, I would greatly appreciate it. Thanks. BTW tablet is : Ployer MOMO9-3 running 4.0.4 I think. If it needs to be updated, can you please advise on that too.
Also want to note that it'll work for about 45min before it freezes, screen turns different color or gets static like and I'll have to reboot.
First post. Tried searching for the desired info, to no avail. Braving any potential flame spray and asking anyway. Besides... this may entertain you. I've also posted this same question to a couple other forums, to no avail.
I have a P3113 that I had on me when I was caught in a rain storm. I was wearing a rain coat, and the tab was in one of the pockets. The pocket was zipped closed, so I thought the tab would be safe. It wasn't.
I did the regular stuff of turning it completely off right away, then put it in a bag full of rice for about 16 hours or so. When I tried to restart it, no dice. About a day later, it did turn on. It stayed on for about an hour letting me play Fruit Ninja. Then it shut itself down on low battery. I couldn't get it to charge at all during this period. I left it on the charger over night... didn't charge. At that point, I sort of wrote it off, but didn't pitch it.
Fast forward about 2 years. I get bored one night, pop the back off and wire the outermost wires to a freshly charged 3.7V battery from an OG Droid phone. Hit the power button... and it booted up!
While it was running, it wouldn't get very good WiFi, even sitting next to my router. It wouldn't open the Play Store app, and when I managed to log into Play through the browser, Play wouldn't recognize the device. That kept me from being able to download any app updates or any new apps.
Then the machine started running v e r y s l o w. At that point, I decided to throw caution to the wind (I did, after all write this thing off about 2 years ago) and do a factory reset.
Now, when I have the device in recovery mode, and I tell it to reboot, it will shut off and never turn back on. If I manually power on with the power button, it starts up in recovery mode.
The device isn't rooted, and I can't root it at all. At this point, I'm not even sure where the data cable is, not to mention it would never interface with a PC after the initial incident. I have, still, tried to do "apply update from external storage," using a few different roms I have found here and elsewhere. Most recently, I used Tab2Lite_P3113_RC2.zip, but it failed at about 75% complete and gave me a "signature verification failed" error message. In fact, I get the same message for every rom I've tried.
Anyone have any idea at all how to recover this thing? I'm only curious if I can get it running just to play games. I plan on getting a Tab 4 8.0 in March.
So you are using a different battery?
shsagnik said:
So you are using a different battery?
Click to expand...
Click to collapse
Electrically speaking, I'm running 2 batteries in parallel. The OG Droid battery is wired to the factory Tab battery. I can disconnect the Droid battery and the Tab still runs, but still doesn't reboot as it should.
When I select reboot, it powers down, and stays that way until I push the power button. Then it boots right into recovery mode.'
Sorry I can't help you as I don't have requisite knowledge
Sounds like you have a Frankenstein tab,you need a new tab. Time to put it out of its misery.
Pp.
A few months ago I rooted but at the time I didn't want to unlock. Last night I decided to unlock so I could start flashing ROM's and just doing the fun unlocked stuff. I was having the google account not recognized problem so I removed it. After that unlock worked fine. The unlock app ran and my tab rebooted. I wanted to make sure so I shut down and rebooted again. Everything was fine and I indeed was unlocked. I the setup my google account. Then I and surfed here and downloaded a few ROM's to try and TWRP to flash. It was getting late so I put the tab down for the night. It went to sleep (battery was fully charged before I unlocked and had about 90% when I put it down). I watched the 11:00 news then got ready for bed myself. I picked up the tab and put it on it's dock as I do every night to charge and noticed the amber charge light did not come on. Checked the dock and the green charge light was on. Removed the charger and the tab from the dock and plugged in directly. Still no charge light. Tried turning on the tab......dead. Tried resetting with the pin hole switch.........dead. Tried power+volume.......dead.
I lost now. Did unlocking totally break my tab and how? Is there anything I can do other that build a house with my brick? Any help is appreciated.
I can always look on the bright side. I can see a Nexus 9 or Pixel C in my future. :good:
One more thing, I have an old Transformer Prime that I had rooted but that's about it. It still powers up but below is the reason I "retired" it.
My post in the Transformer Prime section on XDA (with no replies):
My prime seems to have given up the ghost. Lots of ANR and processes stopping for no known reason. At the time I was rooted but still locked, been rooted for a few years. I did a factory reset and now I can't re-setup my google account because as soon as the boot finishes I get "unfortunately com.google.process.gapps has stopped" message. After the factory reset I rooted this time using DebugfsRoot_Generic_v2.3 and side loaded a root checker, busybox and SuperSU which all recognizes the root. When I try to boot into recovery (stock Android 4.1.1; Build number 10.4.2.18-20121122) I get the fallen down Android with the red triangle of death.
After all this I've decided to unlock and go the custom recovery/custom ROM route. I went to Asus and downloaded the unlock tool. Side loaded it and it installed fine. When I go to run the unlock the app gives the "Unfortunately Unlock Device Tool has stopped message".
Ok now this is weird. Left it to sit overnight. Connected it to the dock this morning and now it's charging. I'm about done with Asus tablets. I really liked my TF201. With all it's faults (didn't really have that many issues with it) it's WAY better than my TF700. When I bought the 700 I thought all the kinks that the 201 had would have been ironed out. The 700 sucks. I think I'm going to pick up a Pixel C.