Related
So after reading about a dozen or so threads, all of the FAQ's, asking in the wrong forum, and 3 other sites, I have come to a roadblock. Here is my situation in its entirety...
Got a brand new Kindle Fire HD 7" for Christmas, obviously couldn't leave it alone. I have rooted about a dozen models of Android phone, and jailbroken multiple iPhones, so I know the trials and tribulations of this process...
So I attempt to root my KF using the Bin4ry and Qemu method. I have a AWFUL time getting the drivers to properly recognise my KF. I end up finding another person's issue such as mine, and go through the LONG way of downloading the adt bundle, and installing all of the google software and drivers that way. EUREKA! Drivers work, KF recognised by my machine. First shot with Bin4ry after the driver mishap, works fine. Takes 2 attempts with the second step with the Qemu method, but again, I get there. after the first time booting up, I factory reset the Kindle. Still have SU on the apps list. Cool! Now what?
I boot the machine and shut it down about 5 times just to check stability, and hard shutdown (power button for 20+ seconds) twice. Every time all is ok, and SU is still there.
Now time to play. I again go through reading a couple threads on changing the launcher, and decide to go with the Nova launcher for now. I download it from the Play store, yet can't seem to find it on my KF. I for some god awful reason decide "well I saw it a couple threads ago, that someone had an issue with the launcher change the name of launcher.apk to launcher.apk1 and then it worked" so obviously I go and do that. Enter the final time I would boot my KF.
Upon reboot, I get the stock/standard "kindle fire" screen with no animation at full brightness. It then goes black for a split second, and comes back with the "kindle fire" screen, but now with the animated "shiny streak" that goes across the logo. I left it there multiple times for a half hour +, no change.
So I don't freak out yet, cause it turned on, and I find it can't be all that bad. So I check for it in device manager...nothing. Check My Computer just to see if its recognised for memory storage...nothing. I run the Bin4ry script again, just to see...nothing. Run Qemu just to be thorough...nothing. Restart my computer, repeat ALL above steps...nothing. Still never see's the KF, also never makes a tone at me when I plug the kindle into the cable. Change USB ports, repeat all, nothing. Back all of the drivers out, and reinstall all of them. Restart. Nothing. Download kindle unbrick utility, that still doesn't see the KF. No adb shell commands ever let me even see that it is seen somehow my my computer.
So now I am stuck. It still seems to me to be a driver issue, but I seriously cannot see how that is possible. I guess while waiting for a response from one of the guru's here, I will repeat my process of backing all of the previous drivers out and reinstalling them. There is NO other software on the kindle except for the Nova launcher and whatever the Bin4ry and Qemu methods install on it.
Sorry for the long post, but I figured it would be better than leaving you guys to ask more questions, though I'm sure you will anyways. My KF is running 7.2.3 before all of this happened...
Thanks for any help, sorry to be that guy!
Jordan
skeeter7424 said:
So after reading about a dozen or so threads, all of the FAQ's, asking in the wrong forum, and 3 other sites, I have come to a roadblock. Here is my situation in its entirety...
Thanks for any help, sorry to be that guy!
Jordan
Click to expand...
Click to collapse
Well the good news is you don't have a driver issue, Its seems you are just stuck in a boot loop and at that point in the boot process adb is not recognized. Check out this thread on how to restore it: http://forum.xda-developers.com/showthread.php?t=1951254
By the way you will need a factory cable. There is a link in the above thread for where to purchase(someone told me they've gotten them on amzon as well). Don't worry they are cheap, about $10-15.
So I see it listed all over the place, but I take it the factory cable is not the one that was supplied in the box?
edit: now i have found what everyone is talking about and have found the writeup on the cable. I am currently sitting at my desk making myself this cable now...we'll see how this goes!
So I got the factory cable made correctly, plugged it in, boom, computer recognizes it. I reload software from the kindle unbrick utility. Now it goes into straight bootloop, KF home screen, blank, KF home screen, blank. Tried with both the factory cable and the stock cable. No changes. Am letting it completely die today to attempt to plug into computer and let it recognize. Should I do this part with the stock cable or the factory modded cable?
skeeter7424 said:
I reload software from the kindle unbrick utility.
Click to expand...
Click to collapse
What are you referring as "the kindle unbrick utility"? Did you try to use KFHD System.img Restore Tool ?
Yes I am. The issue is that the KF boots to the "Kindle" opening screen, then switches to a screen that says "Fastboot" with "amazon kindle" below it. I then get a tone from my computer that is recognized, then about a quarter second later, the KF blacks out, and I get a tone from my comp that says disconnect. It then tones back and forth between connected and not. This happens with both the factory cable and the stock cable.
skeeter7424 said:
Yes I am. The issue is that the KF boots to the "Kindle" opening screen, then switches to a screen that says "Fastboot" with "amazon kindle" below it. I then get a tone from my computer that is recognized, then about a quarter second later, the KF blacks out, and I get a tone from my comp that says disconnect. It then tones back and forth between connected and not. This happens with both the factory cable and the stock cable.
Click to expand...
Click to collapse
What happens when you just turn it on with no cable hooked up. Also did you use the tool that corresponds with the system version your device was running before the problem tat started it. If you used the wrong backup then you will need to use the method to downgrade at the bottom of the restore tool post
Sent from my KFJWI using xda premium
onemeila said:
What happens when you just turn it on with no cable hooked up. Also did you use the tool that corresponds with the system version your device was running before the problem tat started it. If you used the wrong backup then you will need to use the method to downgrade at the bottom of the restore tool post
Sent from my KFJWI using xda premium
Click to expand...
Click to collapse
The same thing happens when trying to boot with no cable. Kindle fire screen, quick to Fastboot/Kindle Fire screen, black.
Also, now with a little more research, I should explain how the computer actually tones when this happens. Right when the KF boots, I get an "unplugged" tone, then right after that I get 3 tones, which after looking at different hardware forums, means that the device is not recognized. It will then go back and forth between the unplugged tone, and the 3 beeps, now with the KF being blacked out. If I then long hold the power button it gives me one "final" unplugged tone.
I used the backup for 7.2.3 which was what was on my KF before I started. Again, that tool will not recognize my KF. All I get with the KFHD_SRT tool is "waiting for device"
Thanks again guys for the help with this!
skeeter7424 said:
The same thing happens when trying to boot with no cable. Kindle fire screen, quick to Fastboot/Kindle Fire screen, black.
Also, now with a little more research, I should explain how the computer actually tones when this happens. Right when the KF boots, I get an "unplugged" tone, then right after that I get 3 tones, which after looking at different hardware forums, means that the device is not recognized. It will then go back and forth between the unplugged tone, and the 3 beeps, now with the KF being blacked out. If I then long hold the power button it gives me one "final" unplugged tone.
I used the backup for 7.2.3 which was what was on my KF before I started. Again, that tool will not recognize my KF. All I get with the KFHD_SRT tool is "waiting for device"
Thanks again guys for the help with this!
Click to expand...
Click to collapse
You made your own factory cable right? Did you use a resistor and if so what size? Sounds like you could have shorted something out, cause I've never heard of this problem but I know you can do a lot of damage to both device and pc if a factory cable is not made correctly with at least a 1k resistor(if I remember correctly).
Do you get the fastboot screen. And also I did not use resistor when I made my cable and it works just fine. Only thing weird Is That once I have fastboot screen I have to unplug my fastboot cable and use original cable in order to flash anything but I have had no other issues. Hope this helps.
Sent from my KFTT using XDA Premium HD app
Need a bandaid?
Try this.
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
That kindle is hard bricked, there's a slight chance of fixing if it is flashing fastboot mode for a few seconds, but I give it a 10% chance of fixing. We can't fix omap4440 bricks because while we have the means to interface with that device, we need a signed xloader for the kindle to let us flash the other partitions. We can't get the signed xloader (believe its called xloader, might be called something else) unless someone at amazon or TI were nice enough to leak it and probably get fired in the process.
On another note is that android adb composite device staying there the entire time the kindle is plugged in? If it does then you may be able to fix the kindle, I haven't heard of omap4440 and the adb composite being there at the same before. I would guess that adb is the fastboot interface but usually it says Tate when drivers aren't installed and in this case it doesn't but still has an exclamation. I'm curious....
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Well, @stunts513, it also shows that a kindle fire is plugged in with adb enabled. So he might not be 100% out of hope.
It sounds like the bootloader does indeed work, but there is a small problem. I am not sure what that problem is, but if the fastboot logo even shows at all, there is a small chance you could get it up and running again. Download the kfhd7 bootloader provided by @Hashcode and see if you can "fastboot flash" it before the screen goes black. Type in the command and the second you see the orange kindle fire logo, hit enter. Keep in mind that it might work. I am not responsible if it ruins your device further. It shouldn't, though.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Well, I wouldn't say 100% out of hope...
http://forum.xda-developers.com/showthread.php?t=2391047
Or you could try using "fastboot boot" to boot the bootloader. This takes barely less time so if the fastboot flash fails, try this.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Same exact problem, did anyone find a fix?
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
I have the same problem Word for Word just a few extra details: I did have TW RP installed and I had just recently installed Kinology which was working but I went Back into TW RP again to try to Flash CM and didnt have all the files I needed But went ahead and removed my OS somehow leaving me stuck in TWRP Trying to figure out away to get the files over to it. At some point it ended up in Fastboot mode and I fell asleep so it was running with just the Fastboot logo for several hours and I woke up and saw that it was turned back off at which point I attempted to reboot back into recovery (TWRP) but discovered it would only show Kindle Fire for <1 second then Fastboot <1.5 seconds and back to a black screen. If it's connected to the computer it will make a sound as if the device was recognized but then a strange sound I have not heard I guess meaning the device was not installed correctly; Then this is repeated not stop until a reset on the device is done just the correct amount of time where it doesn't turn back on but the sound stops on the computer and the KFHD screen stays off. I'm new to Android and rooting, etc. but in the last 45+days since I got this KFHD7 used, I have used XDA countless times for a variety of reasons and I intend to be a contributing member from this day forward, even if only in a very limited capacity. I have grown to respect the incredible work of Hashcode among others on XDA and being a noob to Android customization as well as these forums, I have been reflecting on my years being tied down by iOS devices; can't help but feel like I wasted so much time and money, trying to so the things that Android was already capable of doing. I think I may need to f-around and jailbreak my iPhone 4S pretty soon when I'm able to scoop up a real nice Android phone and leave ios behind for good like I should have done when I switched from the very first iPhone on Cingular Wireless!! But yeah sorry, um... Little long-winded on my first ever reply on XDA. I'll try not to make a habit of that. I was just wondering if anyone made any progress on this issue, and thought my 2¢ could potentially be helpful, disregarding all the ios b.s. My Kindle Fire is Hard Bricked and I'm keeping my fingers crossed that I can squeeze something out of that "10% chance for recovery." Thanks a billi.
Steveohookem said:
I have the same problem Word for Word just a few extra details: I did have TW RP installed and I had just recently installed Kinology which was working but I went Back into TW RP again to try to Flash CM and didnt have all the files I needed But went ahead and removed my OS somehow leaving me stuck in TWRP Trying to figure out away to get the files over to it. At some point it ended up in Fastboot mode and I fell asleep so it was running with just the Fastboot logo for several hours and I woke up and saw that it was turned back off at which point I attempted to reboot back into recovery (TWRP) but discovered it would only show Kindle Fire for <1 second then Fastboot <1.5 seconds and back to a black screen. If it's connected to the computer it will make a sound as if the device was recognized but then a strange sound I have not heard I guess meaning the device was not installed correctly; Then this is repeated not stop until a reset on the device is done just the correct amount of time where it doesn't turn back on but the sound stops on the computer and the KFHD screen stays off. I'm new to Android and rooting, etc. but in the last 45+days since I got this KFHD7 used, I have used XDA countless times for a variety of reasons and I intend to be a contributing member from this day forward, even if only in a very limited capacity. I have grown to respect the incredible work of Hashcode among others on XDA and being a noob to Android customization as well as these forums, I have been reflecting on my years being tied down by iOS devices; can't help but feel like I wasted so much time and money, trying to so the things that Android was already capable of doing. I think I may need to f-around and jailbreak my iPhone 4S pretty soon when I'm able to scoop up a real nice Android phone and leave ios behind for good like I should have done when I switched from the very first iPhone on Cingular Wireless!! But yeah sorry, um... Little long-winded on my first ever reply on XDA. I'll try not to make a habit of that. I was just wondering if anyone made any progress on this issue, and thought my 2¢ could potentially be helpful, disregarding all the ios b.s. My Kindle Fire is Hard Bricked and I'm keeping my fingers crossed that I can squeeze something out of that "10% chance for recovery." Thanks a billi.
Click to expand...
Click to collapse
When you remove your OS off any device without one to install, its like giving someone a car with no steering wheel. You now need to push a ROM thru TWRP using ADB. Try using the solution that helped me, which I provided to another user in this thread:
http://forum.xda-developers.com/showthread.php?p=45188927#post45188927
Sent from my Amazon Kindle Fire HD using xda app-developers app
---------- Post added at 06:10 AM ---------- Previous post was at 05:56 AM ----------
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
Creepy never seen that happen on either of my two KFHD7s. Have you tried uninstalling that driver completely? Or uninstalling those drivers thru "Device Manager" AND all others installed for /example the ones provided by Hashcode, then reinstalling them WITH the device still connected? Many times I've realized that these Kindle Fires love to have drivers juggled around. The fastboot cable I made at home using a Samsung USB does FBmode instantly. Try holding the power button for about 20 seconds while unplugged, make sure when you let go it doesn't power back on. If alls well, have the fastboot cable plugged in already to your computer, then attach it to the KF. See if that helps. If not, then believe it or not it might be a hardware failure if the screen goes black as you mentioned...
Sent from my Amazon Kindle Fire HD using xda app-developers app
r3pwn said:
Well, @stunts513, it also shows that a kindle fire is plugged in with adb enabled. So he might not be 100% out of hope.
It sounds like the bootloader does indeed work, but there is a small problem. I am not sure what that problem is, but if the fastboot logo even shows at all, there is a small chance you could get it up and running again. Download the kfhd7 bootloader provided by @Hashcode and see if you can "fastboot flash" it before the screen goes black. Type in the command and the second you see the orange kindle fire logo, hit enter. Keep in mind that it might work. I am not responsible if it ruins your device further. It shouldn't, though.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
My bad the picture must have not loaded up last time, or I wouldn't have said that much. But more than likely he has a hard brick. Slim chance of fixing it though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
hi guys from Italy, i have the same very problem...now is the end of Settember....any good news about?????????
Not very much, unless you wanna try hooking up your emmc to a USB card reader like kurohyou did and trying to flash the stock partitions from Linux, no there really isn't any new news. That's basically the only way we have to recover from a hard brick, and it still isntna perfected process, he got his kf2 to a soft brick state after un-hardbricking it, but he couldn't un-softbrick it yet, so he is currently working on that part last I heard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hello, I have the exact same problem with my KFHD7 and I was reading this thread with the hope that someone would have find a solution.
Is there a solution out there for this problem yet?
Juls69 said:
Hello, I have the exact same problem with my KFHD7 and I was reading this thread with the hope that someone would have find a solution.
Is there a solution out there for this problem yet?
Click to expand...
Click to collapse
i think someone finished mapping the rest of the points out on the motherboard but i'm not positive, I'll have to find the thread but the only fix is to solder the kindles motherboard contact point for the emmc to a sdcard reader and hook it up to a pc running linux and flash the bootloader partition with the dd command. Keep in mind I'm referring to the hd 7 2012 model, i don't believe anyone has mapped the points for the 2013 model yet.
edit: foudn the thread: http://forum.xda-developers.com/showthread.php?t=2674737&page=3
use the tutorial for the kf2 or kfhd8.9" but use the contact points mentioned there, might take some researching to know what each of those corresponds to on the sdcard reader. Not everybody is up to soldering on their kindle to fix a hard brick.
Hello,
i found these Thread, because i have the same problems.During the boot the kindle shows the kindle logo then the fastboot logo and the screen goes black. But if use a fastboot-code at the right time, the kindle stay in the fastboot-mode. So i tried to flash the Bootloader and so from Hashwell. The output of fastboot says everythings ok, no errors, but my kindle doesn't leave the bootloop. What i done wrong? I read about the Kindle Fire First Aide-Kit, but i cant find an downloadlink, that still work.
Maybe someone of you can help with this problem.
First of all it's working again so I'm not really looking for any help to get it running but still I thought this is worth mentioning
I wanted to import a .mobi book to Nexus 7. This book was sent to me by a friend and I wasn't completely sure what it was. Not even sure if a .mobi file could cause this. But here it goes:
I tried to import this ebook to Aldiko, turned out, it does not even find the file - so I've downloaded Moon Reader from Play Store which found the book and offered me to import it. While importing it the app froze and superuser showed me that "Shell" asked root permissions but was denied. Eventually the tablet itself froze. After a few minutes the message occured that Moon reader does not response and I chose to kill the app. Then the display turned black and the tablet seemed to have turned off.
After that point the tablet was not responsive anymore. No matter what I tried, it would not respond to anything. Battery was at 40% before but I connected it to the charger anyways. I've tried to boot up again and this time I got some disfigured weird glitches but nothing like a bootscreen. After some time it actually booted into Android (at that point it was an older PACman ROM). As soon as I've tried to unlock the screen the tablet made some weird noises (sounded like R2D2 ) and turned black again.
Again the only reaction to pressing the power button were some glitches...I left the device untouched for a few minutes and tried booting again, this time holding volume down button and it got me into download mode where I was able to choose recovery mode which then gave me the chance to restore a backup. After that it worked as if all the above never occured
However I've decided to flash cm10.2 nightly build then since I had my little issues with PACman on Nexus 4. Though I don't blame the ROM. But quite frankly I don't have the slightest idea why this happened, what caused it and what exactly this issue was.
So I just thought maybe someone encountered similar before and might be able to tell me, what all this was about.
Besides I've checked this .mobi file with virustotal.com and not one antivirus raised alarm. Still don't know what was inside that .mobi, but I don't really wanna try it on any other device
Anyone ever had this?
This is a very strange problem. I never saw anything similar in my life and I searched for someone with a similar problem but I cannot find anything. So I am posting this thread, maybe someone here knows what I should do.
This tablet has been riddled with problems, but this one makes it close to useless. I had several problems since I got the tablet where it won't wake up after sleeping and you had to reboot the thing, where the dock is not available after sleeping and you have to undock and redock it, where the battery drains while sleeping etc etc. Annoyances but I can live with them. I know there is a fix for the dock and you have to send it to Asus, but shipping is expensive so I'll learn to live with it.
This problem though.. this is a big one. So just to clarify, the tablet is rooted with the original 4.4.2 ROM. I did not make any changes in the past week. Yesterday morning, I woke up and used it normally. Later that morning I unplugged it from the charger and that's when I noticed this problem. So while it is connected to the charger the tablet will function normally. After I unplug it the tablet will freeze after a few seconds, reboot on its own and then it will boot until the icons start coming up. Usually after this you get the lockscreen, but instead the screen will black out. After a few seconds the icons start coming back and the the screen will black out again and so on. This loop will continue forever unless you plug the charger in. When you plug in the charger, the icons will come up and after you get the lock screen (instead of the black screen), and you can use it normally. If you unplug it again, the boot loop starts again. This behavior is the same whether using the dock or not.
I don't want to do a factory reset just yet if I can. Last time I did a factory reset, the tablet would not boot and I had to send it back for a replacement. When I get to the fastboot screen, trying RCK I get the dead Android with the red exclamation, and cold booting does nothing.
Any suggestions please? Any kind of log I can get to help? I can post a video if the problem is not clear.
Thanks.
pantera1989 said:
This is a very strange problem. I never saw anything similar in my life and I searched for someone with a similar problem but I cannot find anything. So I am posting this thread, maybe someone here knows what I should do.
This tablet has been riddled with problems, but this one makes it close to useless. I had several problems since I got the tablet where it won't wake up after sleeping and you had to reboot the thing, where the dock is not available after sleeping and you have to undock and redock it, where the battery drains while sleeping etc etc. Annoyances but I can live with them. I know there is a fix for the dock and you have to send it to Asus, but shipping is expensive so I'll learn to live with it.
This problem though.. this is a big one. So just to clarify, the tablet is rooted with the original 4.4.2 ROM. I did not make any changes in the past week. Yesterday morning, I woke up and used it normally. Later that morning I unplugged it from the charger and that's when I noticed this problem. So while it is connected to the charger the tablet will function normally. After I unplug it the tablet will freeze after a few seconds, reboot on its own and then it will boot until the icons start coming up. Usually after this you get the lockscreen, but instead the screen will black out. After a few seconds the icons start coming back and the the screen will black out again and so on. This loop will continue forever unless you plug the charger in. When you plug in the charger, the icons will come up and after you get the lock screen (instead of the black screen), and you can use it normally. If you unplug it again, the boot loop starts again. This behavior is the same whether using the dock or not.
I don't want to do a factory reset just yet if I can. Last time I did a factory reset, the tablet would not boot and I had to send it back for a replacement. When I get to the fastboot screen, trying RCK I get the dead Android with the red exclamation, and cold booting does nothing.
Any suggestions please? Any kind of log I can get to help? I can post a video if the problem is not clear.
Thanks.
Click to expand...
Click to collapse
Hi, to start this reply, I'll let you know that I am no professional at any of this stuff. I am a regular person that has had experience with flashing ROMs and whatnot. In my opinion, this seems like a software (maybe hardware) related problem. So there are a couple of options you have here.
1. Are you still under your warranty period? You could return it and get another one (easy fix)
2. You could try to factory reset, and if it doesn't turn on, rma the tablet (which it sounds like it may be cheaper to just buy a new one anyways)
3. You could try unlocking the bootloader. Then install a custom ROM (kind of risky, but might be less risky than #2)
Overall, you are not in an amazing spot with your tablet. It saddens me to see all the problems with asus's tablets. I have been with them since the transformer prime because of their laptop like tablet makes it easy to use in school, but its always been a struggle staying with their lineup. I have returned their tablets multiple times. Please update when you can
Sent from my SCH-I545 using Tapatalk 2
If you have a microSD in the tablet take it out and try to boot it. I have seen the weirdest problems because of a card on the fritz....
Second possibility: Hardware. The behavior (working fine when connected to power) seems to indicate it doesn't get the charge it needs from the battery. Could be that it is going kaputt. It's not totally fried but enough that the tablet does not get a reliable charge from the battery.
Third option would be to reflash the firmware. That would eliminate a software problem. You will loose root if you do that...
Since you're still on the original firmware, I assume you did not unlock the bootloader and rooted with Towelroot - correct?
Whatever you do, backup everything you care about off the tablet now....
Thanks for your replies/suggestions. I could not use towelroot as it was on 4.4.2 (I think I read it is not possible). The bootloader is unlocked. This is my second tablet as I had returned the original one. I tried putting Cromi-X on it, and when I got to the step to factory reset it (using fastboot), the thing just was stuck in an endless loop. I could not even get to fastboot and my PC wouldn't recognize it. All it did was boot to the ASUS logo (and the message that the bootloader was unlocked) and reboot.
So this is the replacement unit and the charging issue was the problem. I say was because believe me or not the tablet is now smashed to bits. Since it must always be connected with a charger to work, I was carrying it around docked as I usually do and forgot that it was plugged in. I have resorted to an extra long extension cord with the charger plugged in to walk around. Anyway I forgot it was plugged in, the extension cord reached its limit and the charger cord yanked the tablet out of my hands and onto its side - screen facing away. I sweared, feared the worst and went to pick it up. The good news is that it still boots. The bad news is that the screen is completely smashed. The back cover is bent at one corner and the glass is smashed at that corner with cracks running to the other side. The touchscreen is not working anymore either. To add insult to the injury the tablet still only boots up with the charger plugged in..so there's that.
I don't know what to do now. I have contacted ASUS for a possible RMA but got no response yet. The thing is I don't feel like spending more money on it given the problems experienced. A screen with digitizer on ebay is about €75..so not exactly cheap.
I guess we can close this thread as it is now pointless. I hope no one has to go through my experience and that maybe it was a one off thing.
Thanks again to whoever replied. I appreciate it.
Alrighty, folks. I've searched the far reaches of the internet, gone through hundreds of pages on this forum alone, and I think I may just have a different set of issues than most.
The symptoms: Long-time thought-to-be-bricked TouchPad with partition for WebOS and Android... Jelly Bean? I think? so long ago... ended up not being bricked, but rather in need of the factory original charging cylinder for proper power flow. When I got it back in somewhat working order, it, PROBLEM 1, got stuck on the Android loading screen (where the word "Android" gets repeatedly swept across with shininess - remember, this is OLD) and never budged from there. I've restarted it who knows how many times by holding down the power and home buttons. I can scroll through the menu with the volume keys, can load WebOS perfectly fine, can launch Android, but it just stays on the loading screen.
Obvious choice is to wipe the whole deal and start fresh. No worries. Except I wanted to get some design sketches off of it, and, PROBLEM 2, my computer was no longer recognizing it as an external drive, or anything, really. I've looked at darn near every "computer won't recognize TouchPad" thread I could find over the past 14 hours. Finally found one with the driver software that could have been my missing link, and my computer won't accept it as a driver. This is a whole other can of worms for someone who has the patience. I will admit that the one fix I haven't tried for this is using a factory original cable. That cable was awful and it broke on me a long time ago. I will try another cable tomorrow, though, as I'm traveling and only have one on me now.
I managed to get my pictures etc off of the TouchPad by booting WebOS and putting it into USB drive mode there (which my computer magically reconizes ). However, I still can't access files in the standard recovery mode to actually do any wiping/software things. I'm well aware that the solution is to go to The Three Dots and switch that developer slider so that my computer knows what's what, but sadly I can't get to the settings menu. There must be another way.
I discovered just a bit ago that I can boot into ClockworkMod; however, I'm not really sure what to do once I'm in there. I can do a factory reset, yes? Would that help?
TL;DR
TouchPad which cannot connect to computer will load everything but Android.
WHAT I'VE TRIED: booting partially through WebOS with WebOS Doctor running and then trying to pick up the connection with TPToolkit when the Dr recognizes the WebOS side of things, new drivers, sacrificing a goat and doing a ceremonial dance around it, etc.
GOALS: Get TouchPad recognized as a USB drive, using ClockworkMod, which is apparently the only thing I have going for me.
Any and all help gratefully accepted. Thank you all in advance!