Help! I have a newer HDX 7 that is stuck trying to reboot. The device powers up to the gray kindle fire screen but sits there for a minute or so and then the screen flashes and it starts all over. The device does not recognize the power button. I've tried the hold the button for 40 seconds to reset but it just keeps going through this loop while holding the power button. When I connected it to my PC (Win7), it does not see the device. If I connect another Andriod device, it sees it imeadiately.
I'm a complete noob with this but I'm actually in IT, just not in this area. This is my sons device so I'm not sure exactly what he was doing at the time it started this but my guess would be playing MineCraft. Amazon's wonderful support says it just needs to be replaced but it's out of warranty. My son and I were just about to start an online coding course so I'd like to get this back up and running so we can start that. Any help would be appreciated. After searching the web, you guys seem to be the only ones able to root or fix any software/os issues with these devices.
Thanks,
Doug
Leav320 said:
Help! I have a newer HDX 7 that is stuck trying to reboot. The device powers up to the gray kindle fire screen but sits there for a minute or so and then the screen flashes and it starts all over. The device does not recognize the power button. I've tried the hold the button for 40 seconds to reset but it just keeps going through this loop while holding the power button. When I connected it to my PC (Win7), it does not see the device. If I connect another Andriod device, it sees it imeadiately.
I'm a complete noob with this but I'm actually in IT, just not in this area. This is my sons device so I'm not sure exactly what he was doing at the time it started this but my guess would be playing MineCraft. Amazon''s wonderful support says it just needs to be replaced but it's out of warranty. My son and I were just about to start an online coding course so I'd like to get this back up and running so we can start that. Any help would be appreciated. After searching the web, you guys seem to be the only ones able to root or fix any software/os issues with these devices.
Thanks,
Doug
Click to expand...
Click to collapse
Your options are limited given the device is largely invisible via tether (even then there would be little recourse as adb is probably disabled). Did you try a factory reset? Amazon's crippled recovery environment can be accessed via power + vol-up from a cold start. Release the power button after the gray Kindle logo appears. If the recovery menu comes up the only option is 'factory reset'. I realize you may not be able to access recovery given the non-responsive power button.
Any chance you son is old/savvy enough to trying rooting the device? The symptoms suggest either a failed automatic update (rare but it does happen) or botched attempt to root via the wrong method. Obviously a spontaneous hardware failure is also possible albeit unlikely.
Do you know what version of Fire OS was running just prior to the boot loop?
There is still a small chance adb may help even if the device is not recognized by Windows explorer. However, if as Davey said, it is disabled, things are limited.
Again, do you know what version is you were running?
Have you installed adb?
Have you tried recovery?
Sent from my KFTHWI using Tapatalk
Davey126 said:
Your options are limited given the device is largely invisible via tether (even then there would be little recourse as adb is probably disabled). Did you try a factory reset? Amazon's crippled recovery environment can be accessed via power + vol-up from a cold start. Release the power button after the gray Kindle logo appears. If the recovery menu comes up the only option is 'factory reset'. I realize you may not be able to access recovery given the non-responsive power button.
Any chance you son is old/savvy enough to trying rooting the device? The symptoms suggest either a failed automatic update (rare but it does happen) or botched attempt to root via the wrong method. Obviously a spontaneous hardware failure is also possible albeit unlikely.
Do you know what version of Fire OS was running just prior to the boot loop?
Click to expand...
Click to collapse
No, Unless it updated automatically, it was the same version that was on there when it was delivered around 4/14.
No, My son would not have tried rooting this on his own.
I was incorrect when I stated that the system wasn't recognizing the power button. When I try the hold the power button for 40 secs or the Power button + Vol up button to restart, the boot loop gets shorter.
lekofraggle said:
There is still a small chance adb may help even if the device is not recognized by Windows explorer. However, if as Davey said, it is disabled, things are limited.
Again, do you know what version is you were running?
Have you installed adb?
Have you tried recovery?
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
I have installed ADB on my PC but it doesn't see the device (although I'm not sure I'm using it correctly). What command should I be issuing to see if the device is connected. If I use "adb devices" I get the response in the attached screen shot.
If by recovery, you mean the recovery on the device, the power+volume up button doesn't work.
I appreciate all of the help!
Leav320 said:
No, Unless it updated automatically, it was the same version that was on there when it was delivered around 4/14.
No, My son would not have tried rooting this on his own.
I was incorrect when I stated that the system wasn't recognizing the power button. When I try the hold the power button for 40 secs or the Power button + Vol up button to restart, the boot loop gets shorter.
I have installed ADB on my PC but it doesn't see the device (although I'm not sure I'm using it correctly). What command should I be issuing to see if the device is connected. If I use "adb devices" I get the response in the attached screen shot.
If by recovery, you mean the recovery on the device, the power+volume up button doesn't work.
I appreciate all of the help!
Click to expand...
Click to collapse
Given the delivery date and age of device I STRONGLY recommend you reach out to Amazon for a replacement vs trying to resolve on your own. A new version of Fire OS is currently rolling out which MAY have triggered the behavior you are seeing. Bit of a bummer given your son's course plans but a worthwhile delay IMHO.
I agree with Davey.
Sent from my KFTHWI using Tapatalk
Related
Recently my DNA has been getting laggy and restarting occasionally, and yesterday after sending a simple text message it decided to enter a reboot-loop that I think is probably fatal.
When I plug it in to any power, it turns on, shows the white/green HTC screen, and then immediately shuts down, and repeats the cycle. I have not been able to get it to turn off (while on power), and cannot turn it on (even into the loop) while off power. HOWEVER, I CAN use the vol - shortcut to get to the bootloader screen BUT I cannot select anything, as it immediately shuts down when I try to do something.
My DNA is running the latest stock software (OTA from Verizon, i think 4.4.2), and i have not modified it (S-ON, unrooted etc...).
Any and all help would be appreciated!
Bonus: on the 95% chance it is dead, should i go moto x/droid turbo or stick with a *gasp* iphone 5 for 2 months until gs6/htc m9?
androidnj7 said:
Recently my DNA has been getting laggy and restarting occasionally, and yesterday after sending a simple text message it decided to enter a reboot-loop that I think is probably fatal.
When I plug it in to any power, it turns on, shows the white/green HTC screen, and then immediately shuts down, and repeats the cycle. I have not been able to get it to turn off (while on power), and cannot turn it on (even into the loop) while off power. HOWEVER, I CAN use the vol - shortcut to get to the bootloader screen BUT I cannot select anything, as it immediately shuts down when I try to do something.
My DNA is running the latest stock software (OTA from Verizon, i think 4.4.2), and i have not modified it (S-ON, unrooted etc...).
Any and all help would be appreciated!
Bonus: on the 95% chance it is dead, should i go moto x/droid turbo or stick with a *gasp* iphone 5 for 2 months until gs6/htc m9?
Click to expand...
Click to collapse
At any point can you get it to answer
Fastboot devices
?
dottat said:
At any point can you get it to answer
Fastboot devices
?
Click to expand...
Click to collapse
I can not get it to receive any signals from me in the bootloader as it shuts down immediately. I tried connecting it to my computer for use with adb, but fastboot WAS enabled and developer tools were DISABLED (i think), plus it cannot keep a constant connection, so that wasn't working.
After doing some research I think I can save it IF I can get it to a stable state from the one it is currently in, and then using the bootloader screen to do a factory reset ( or use
"adb reboot recovery"), but like I said that is depenednet on getting it to stop the boot loop.
I also tried doing something called an RUU (I have limited knowledge of this, i sued the dottat one), but since it cannot establish a constant connection, it did not work.
Im open to any suggestions at this point! Thanks
I seem to have posted my reply in haste.
I have installed the "minimal adb and fastboot" tool that was suggested for basic fastboot use. Fastboot will not recognize it when I use "fastboot devices".
I did install the HTC drivers a while ago, but I suspect they may not work, could that be the issue? I am running win 8.1.
Thanks
androidnj7 said:
I seem to have posted my reply in haste.
I have installed the "minimal adb and fastboot" tool that was suggested for basic fastboot use. Fastboot will not recognize it when I use "fastboot devices".
I did install the HTC drivers a while ago, but I suspect they may not work, could that be the issue? I am running win 8.1.
Thanks
Click to expand...
Click to collapse
Possibly. What does the device show up as in device manager?
dottat said:
Possibly. What does the device show up as in device manager?
Click to expand...
Click to collapse
For the 5-10 seconds its "on" every cycle, it shows up as a CD Drive (not the HTC6435 etc etc that it usually does)
androidnj7 said:
For the 5-10 seconds its "on" every cycle, it shows up as a CD Drive (not the HTC6435 etc etc that it usually does)
Click to expand...
Click to collapse
Hold volume up and power until the screen flickers and immediately switch to volume down only. Get it right and you will land in boot loader. Need boot loader to show fastboot usb
dottat said:
Hold volume up and power until the screen flickers and immediately switch to volume down only. Get it right and you will land in boot loader. Need boot loader to show fastboot usb
Click to expand...
Click to collapse
Yes I have gotten into the bootloader before but as soon as it shows up (and i try to select using the vol +/-) it shuts down and restarts right away. Basically, I cant even get the bootloader in a stable state.
androidnj7 said:
Yes I have gotten into the bootloader before but as soon as it shows up (and i try to select using the vol +/-) it shuts down and restarts right away. Basically, I cant even get the bootloader in a stable state.
Click to expand...
Click to collapse
Fastboot usb is going to be your only option. If you aren't able to stay there it's hardware. Any chance a button is stuck?
dottat said:
Fastboot usb is going to be your only option. If you aren't able to stay there it's hardware. Any chance a button is stuck?
Click to expand...
Click to collapse
You are right unfortunately, I can absolutley not stay in the bootloader with any sort of stability. I read on another thread that opening it up and disconnecting the battery from the motherboard would help, so thats what I did. As soon as I sealed it back up, the reboot-loop started right up again. My guess is that the motherboard is fried, its either that or the battery is holding no charge whatsoever.
If the board is fried, im done right?
if its the battery, is there any way to manually charge not going through the board?
Thanks for all your help btw!
I've been a lurker of this forum for years. I just joined and I've always done my research before posting anything. But I'm at a loss right now and I do not know what to do.
I have a Kindle Fire HDX 7" (Thor), yesterday I was trying to flash an Android ROM on it. I got up to the point where I was in TWRP, and I accidentally factory reset the Kindle thru TWRP. When the Kindle rebooted, it showed a screen that said something like...
"Kindle Fire System Recovery; Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue."
The choices it gave me were, "Reboot your Kindle" and "Reset to Factory Defaults"
I rebooted my Kindle as a first choice, and it booted back to the same screen. So then I reset to factory defaults. Nothing worked and it kept bringing me back to that screen. I'm guessing there is no bootloader or anything on the Kindle.
I left the Kindle on for hours as I was trying to find my fastboot cable knowing that I would probably need it to fix this problem. I then turned off the Kindle hours later (press and hold until screen shut off). I did have a full battery prior to trying to put an Android ROM on the Kindle.
This morning I found my fastboot cable, but when I pressed the power button on the Kindle, it will not turn on. No response from it at all. Did I drain the battery?
When I plug my Kindle to my computer using the fastboot cable, it was showing me "QHSUSB_BULK" in the USB device list. I tried ADB, but it says "error: device not found".
When I plug my Kindle to charge, it doesn't show the low battery/charging indicator like it used to.
What should I do next? Is my Kindle permanently bricked?
I need mad help right now!
Try to boot into twrp, but you may bricked your device permanently because you did a factory reset with the default kindle recovery
Sent from my KFTHWI using XDA Free mobile app
MinerBoy004 said:
Try to boot into twrp, but you may bricked your device permanently because you did a factory reset with the default kindle recovery
Sent from my KFTHWI using XDA Free mobile app
Click to expand...
Click to collapse
Okay, one question, how would I boot into TWRP? I ask only because the Kindle is not starting up, and when I plug the fastboot cable, the computer is not recognizing it.
Junava said:
I've been a lurker of this forum for years. I just joined and I've always done my research before posting anything. But I'm at a loss right now and I do not know what to do.
I have a Kindle Fire HDX 7" (Thor), yesterday I was trying to flash an Android ROM on it. I got up to the point where I was in TWRP, and I accidentally factory reset the Kindle thru TWRP. When the Kindle rebooted, it showed a screen that said something like...
"Kindle Fire System Recovery; Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue."
The choices it gave me were, "Reboot your Kindle" and "Reset to Factory Defaults"
I rebooted my Kindle as a first choice, and it booted back to the same screen. So then I reset to factory defaults. Nothing worked and it kept bringing me back to that screen. I'm guessing there is no bootloader or anything on the Kindle.
I left the Kindle on for hours as I was trying to find my fastboot cable knowing that I would probably need it to fix this problem. I then turned off the Kindle hours later (press and hold until screen shut off). I did have a full battery prior to trying to put an Android ROM on the Kindle.
This morning I found my fastboot cable, but when I pressed the power button on the Kindle, it will not turn on. No response from it at all. Did I drain the battery?
When I plug my Kindle to my computer using the fastboot cable, it was showing me "QHSUSB_BULK" in the USB device list. I tried ADB, but it says "error: device not found".
When I plug my Kindle to charge, it doesn't show the low battery/charging indicator like it used to.
What should I do next? Is my Kindle permanently bricked?
I need mad help right now!
Click to expand...
Click to collapse
By TWRP you mean safestrap recovery? If you flashed through safestrap other ROM than Nexus for Safestrap 1.0.1 (which one BTW? Did you flash by accident ROM for Hdx 8.9?) that could be the first reason for bricking your kindle... Safestrap is not TWRP, is only TWRP based and works differently than TWRP 2.8.5.0, also safestrap is located on system partition, but TWRP 2.8.5.0 when installed is flashed to recovery partition...
Doing factory reset through safestrap should be relatively safe unless you mess with advanced wipe and delete/wipe system partition - this effectively erase content of /system including safestrap recovery, this could be the second reason for bricking your kindle.
If you had installed real cuber signed TWRP 2.8.x.x, then the only thing I can think of is that you tried to flash one of amazon update bins with TWRP, these bins when installed replace content of the recovery partition with Amazon FireOS recovery, successfully deleting real TWRP in the process, but this should end with booting to FireOS...
Junava said:
Okay, one question, how would I boot into TWRP? I ask only because the Kindle is not starting up, and when I plug the fastboot cable, the computer is not recognizing it.
Click to expand...
Click to collapse
Just hold the volume up button (+) when it's booting.
However, I'm not really sure of your situation, because TWRP should've replaced the stock recovery.
I finally got it to turn on somehow. And this is the screen that it's giving me (see attachment). I tried both of the options given and it'll bring me back to the same screen.
Also, before I was able to power on the Kindle, it'll say QHSUSB BULK in the connected usb devices when I use my fast-food cable on it. But when I have the Kindle powered on it says Unknown Device.
If I can get the Kindle to respond to adb I can probably work from there. But my computer is not recognizing it.
What version of fireos you had? maybe is possible to unlock bootloader.. but you should know mmc manfid and serial. We don't know yet how to get emmc serial from bootloader only.
dpeddi said:
What version of fireos you had? maybe is possible to unlock bootloader.. but you should know mmc manfid and serial. We don't know yet how to get emmc serial from bootloader only.
Click to expand...
Click to collapse
I had to rollback as I was following the guide on the post in the developmental forum on here. Will the manufacturer id be on the box? I still have the original box for the Kindle.
Sent from my VS980 4G using XDA Free mobile app
Actually you can get it from adb without root
My Kindle is not communicating with adb. I've been trying all week and doing a lot of researching. I either get an "Unknown Device" or "QHSUSB BULK" in the connected usb list.
Sent from my VS980 4G using XDA Free mobile app
Dies it go in fastboot mode with vol+ vol- power?
Junava said:
I finally got it to turn on somehow. And this is the screen that it's giving me (see attachment). I tried both of the options given and it'll bring me back to the same screen.
Also, before I was able to power on the Kindle, it'll say QHSUSB BULK in the connected usb devices when I use my fast-food cable on it. But when I have the Kindle powered on it says Unknown Device.
If I can get the Kindle to respond to adb I can probably work from there. But my computer is not recognizing it.
Click to expand...
Click to collapse
How did you get to that screen? do you remember what you pressed?
dpeddi said:
Dies it go in fastboot mode with vol+ vol- power?
Click to expand...
Click to collapse
Nope.
Silverclaw280 said:
How did you get to that screen? do you remember what you pressed?
Click to expand...
Click to collapse
I held the power button for maybe a good 30 seconds and it powered on and took me to that screen. I'd usually have to keep trying to get the Kindle to power on, and when I do, that screen is all it'll do.
Turn kindle off.. then press and keep pressed vol+ and vol- and keep them pressed. Turn on kindle while pressing both volume. You should enter into fastboot. If we found a relation between emmc serial and kindle serial number you should be able to fix it. (I think your boot.img is corrupted)
Silverclaw280 said:
How did you get to that screen? do you remember what you pressed?
Click to expand...
Click to collapse
I was able to get back to that screen by following the steps in this quoted post.
My Kindle gets the same status. It was safestraped, locked on 3.2.8. Tried to update it with OTA to 4.1.1, it downloaded firmware, checked and rebooted, after that device won't boot up and on connect to pc detects as QHSUSB_BULK. The only way i found is to ask replacement at support
modi said:
My Kindle gets the same status. It was safestraped, locked on 3.2.8. Tried to update it with OTA to 4.1.1, it downloaded firmware, checked and rebooted, after that device won't boot up and on connect to pc detects as QHSUSB_BULK. The only way i found is to ask replacement at support
Click to expand...
Click to collapse
(reposting as a warning to those who may stumble across this thread)
This seems to be the recent fate for many who have rolled back to 3.2.8 and not blocked OTA using HDX Toolkit or an equivalent blocker (renaming otacerts is not reliable). It appears Amazon attempts to push an update that ultimately corrupts the boot partition. Not much you can do to fix it with current techniques/exploits.
If the device is still under warranty Amazon will likely replace it. Just say it died during an update.
Having some new trouble with my Kindle 8.9... Tried walking through [Rollback][Downgrade][Thor][Apollo] 3.2.8 rollback-OTA captured , but hit a snag. The downgrade went great... got back into the OS with no problems. Tried stepping through the upgrades and got to 4.1.1. After starting the 4.5.1 update, the HDX rebooted to a black screen. Nothing works to power it on. I've already searched and tried
holding power for 2 mins + - nothing happened
holding for 40 seconds per Amazon support, then powering on - nothing happened
ADB cannot see it
When I connect it to my computer, it used to show up as the bulk loader device. I installed the Qualcomm driver, then it was showing up as a Qualcomm 9800 something or other. Now when I connect it via USB, it shows up, but isn't recognized.
Any suggestions would be appreciated!
enjid said:
Having some new trouble with my Kindle 8.9... Tried walking through [Rollback][Downgrade][Thor][Apollo] 3.2.8 rollback-OTA captured , but hit a snag. The downgrade went great... got back into the OS with no problems. Tried stepping through the upgrades and got to 4.1.1. After starting the 4.5.1 update, the HDX rebooted to a black screen. Nothing works to power it on. I've already searched and tried
holding power for 2 mins + - nothing happened
holding for 40 seconds per Amazon support, then powering on - nothing happened
ADB cannot see it
When I connect it to my computer, it used to show up as the bulk loader device. I installed the Qualcomm driver, then it was showing up as a Qualcomm 9800 something or other. Now when I connect it via USB, it shows up, but isn't recognized.
Any suggestions would be appreciated!
Click to expand...
Click to collapse
Without ADB your options are few. If you purchased the device directly reach out to Amazon. Tell them it died during an auto-upgrade. Might offer an exchange or discount on a refurb.
Your other option is a factory reset from the Kindle recovery menu (press power and vol-+ from cold start). Given the current state of your device I doubt it could make things worse. If you can't get into recovery that may indicate the recovery partition is damaged which also impacts upgrades/rollbacks. Unfortunately, that doesn't answer the why/how or offer any further solution to your problem.
Hi,
I have amazon fire hd6.
Yesterday i have rooted using kingroot 4.1. And it was working fine.
I have installed google apps, and it was working for a minute or so.
Than i guess google play had an update and stopped working.
Than i went all stupid, and tried removing google packages from the programs.
The first one was google search and fter removing it the system became unstable so i rebooted and voila stuck at fire logo screen.
Actually, at this stage i can see kindle in device manager as MTP device, and can browse the files from windows. When i connect usb it gives the charging sound so everything seems to work but launcher never cames.
I tried adb but shows no devices, as usb debugging was off on the kindle side.
Is there anything i can do?
Some people are talking about a recovery menu holding power and both volume buttons but i could never get it. Am i doing something wrong?
Any suggestions?
ygulsen said:
Hi,
I have amazon fire hd6.
Yesterday i have rooted using kingroot 4.1. And it was working fine.
I have installed google apps, and it was working for a minute or so.
Than i guess google play had an update and stopped working.
Than i went all stupid, and tried removing google packages from the programs.
The first one was google search and fter removing it the system became unstable so i rebooted and voila stuck at fire logo screen.
Actually, at this stage i can see kindle in device manager as MTP device, and can browse the files from windows. When i connect usb it gives the charging sound so everything seems to work but launcher never cames.
I tried adb but shows no devices, as usb debugging was off on the kindle side.
Is there anything i can do?
Some people are talking about a recovery menu holding power and both volume buttons but i could never get it. Am i doing something wrong?
Any suggestions?
Click to expand...
Click to collapse
I think your problem is nothing too seriously. All you have to do is factory reset through recovery. First turn off your tablet, then hold power + volume up at the same time. When to see amazon logo, quickly release power button. Bam, in recovery.
first check the adb shell and see if you have su access. then check adb logcat to see if it is something you can fix
---------- Post added at 03:29 PM ---------- Previous post was at 03:27 PM ----------
nvm just saw what you said about adb devices... This device is way too easy to brick and we currently have no restore method. I ended up replacing the motherboard on my bricked fire hd6. I bought a fire hd6 with a broken screen on ebay and replaced my device with that motherboard
droidnext said:
I think your problem is nothing too seriously. All you have to do is factory reset through recovery. First turn off your tablet, then hold power + volume up at the same time. When to see amazon logo, quickly release power button. Bam, in recovery.
Click to expand...
Click to collapse
are you sure this is the right procedure for this device?
tried this 100s times but no recovery.
actually i am thinking that this device does not have a recovery thing. As with just 3 buttons i have tried every alternative.
ygulsen said:
are you sure this is the right procedure for this device?
tried this 100s times but no recovery.
actually i am thinking that this device does not have a recovery thing. As with just 3 buttons i have tried every alternative.
Click to expand...
Click to collapse
I just try to help you how to go to recovery. I made 10 out of ten everytime. You just need 2 button, not 3 (power + volume up). Unless you're trolling. Good luck and bye bye
droidnext said:
I just try to help you how to go to recovery. I made 10 out of ten everytime. You just need 2 button, not 3 (power + volume up). Unless you're trolling. Good luck and bye bye
Click to expand...
Click to collapse
you got me wrong mate, i have tried your suggestion and actually thx for that. But after amazon logo there goes the fire logo and nothing happens.
This is for amazon fire 4th gen hd 6 right?
And by 3 buttons, i mean, i have tried every two button alternative and no recovery. The device has only 3 buttons.
Maybe my recovery is also broken?
Thx anyways.
Hello everybody,
I bought the Nabi 2, as refurbished, for my little child and from the beginning I am having problems to turn it on or wake it up from sleep. It is not rooted, has everything stock and I have also applied all available official updates (OTA).
The problem is to turn it on, both from sleep or from powered down state. For example, being in sleep mode (display off) for a few hours, to wake it up I have first to press the power button for about 10 seconds, than release it and press again until... the start up Logo appears, as it was completely shut down! Maybe through pushing the power button first time I turn it off unintentional, so the second time it has to power up and load the OS? But just pushing the power button shortly will not wake it up at all from sleep mode... Is this a known problem and is there a solution for it?
Thanks in advance for each advice!
Conrad
Conrad-007 said:
Hello everybody,
I bought the Nabi 2, as refurbished, for my little child and from the beginning I am having problems to turn it on or wake it up from sleep. It is not rooted, has everything stock and I have also applied all available official updates (OTA).
The problem is to turn it on, both from sleep or from powered down state. For example, being in sleep mode (display off) for a few hours, to wake it up I have first to press the power button for about 10 seconds, than release it and press again until... the start up Logo appears, as it was completely shut down! Maybe through pushing the power button first time I turn it off unintentional, so the second time it has to power up and load the OS? But just pushing the power button shortly will not wake it up at all from sleep mode... Is this a known problem and is there a solution for it?
Thanks in advance for each advice!
Conrad
Click to expand...
Click to collapse
The only semi known issue I have seen is when you put the tablet to sleep and it's charging. In some instances the tablet will lock up at some point after going to sleep. When you try to wake in up via power button it is locked up. When you hold the power button for 10sec you are hard powering it off and then it reboots. If yours wasn't charging then I haven't read much about anyone having a similar problem.
aicjofs said:
The only semi known issue I have seen is when you put the tablet to sleep and it's charging. In some instances the tablet will lock up at some point after going to sleep. When you try to wake in up via power button it is locked up. When you hold the power button for 10sec you are hard powering it off and then it reboots. If yours wasn't charging then I haven't read much about anyone having a similar problem.
Click to expand...
Click to collapse
Thanks for your reply, aicjofs.
In my case it happens always, no matter if charging or not... and it's annoying.
Would rooting and installing a custom ROM solve the problem? If yes, is there a custom ROM dedicated to kids, similar with the stock one?
Conrad
Wrong Section Buddy !!!
StariX37 said:
Wrong Section Buddy !!!
Click to expand...
Click to collapse
and why ???
StariX37 said:
Wrong Section Buddy !!!
Click to expand...
Click to collapse
:thumbdown:
Ignore this guy. I have a friend with the same power on issue with her Nabi 2, and I'm interested to read the solution here.
...no other hints concerning my problem ?
Please, if somebody has an idea, just reply here.
Conrad-007 said:
...no other hints concerning my problem ?
Please, if somebody has an idea, just reply here.
Click to expand...
Click to collapse
I'm still struggling with the random problems on my Nabi...
Is it possible to check the integrity and/or health of internal memory, find and mark bad blocks, etc. using a computer (Windows or Linux) connected through USB? If yes, how? Do I need to flash TWRP or something else on the Nabi before?
Thanks in advance for your help.
Conrad
Conrad-007 said:
I'm still struggling with the random problems on my Nabi...
Is it possible to check the integrity and/or health of internal memory, find and mark bad blocks, etc. using a computer (Windows or Linux) connected through USB? If yes, how? Do I need to flash TWRP or something else on the Nabi before?
Thanks in advance for your help.
Conrad
Click to expand...
Click to collapse
The latest TWRP should have a section under the wipe menu where you can repair the file system which is probably easiest, although you need to be careful what you are doing in there as it is called the "wipe" tab for a reason. Should be able to go to wipe menu, select data partition checkbox, select change or repair filesystem(don't swipe to wipe, click the words check/repair etc) and select check in the next screen.
To do a filesystem check the partition can not be mounted so you do it from recovery not in Android. Since stock recovery you can't use ADB you pretty much need TWRP one way or another.
If you don't want to use the graphical interface in TWRP you can do it over USB with ADB and use e2fsck on the partitions after unmounting them, but it's going to be doing the same thing you will just see a more verbose version if you do it over adb.
Thanks a lot, aicjofs.
I will try to root and install first TWRP, as my Nabi is still untouched.
One thing I remarked: at the moment, when I go in the (stock) recovery and want to do a "Wipe data/factory reset", 2 lines are displayed before "-- Wipping data...": "E: missing bitmap stage_empty (Code -l)" and "E:missing bitmap stage_fill (Code -l)". After that, the wiping process seems to run normal, as I get the message "Data wipe complete." at the end.
Do you know what that lines are meaning? Could those lines help to debug the main problem ?
Update: NO WAY to get TWRP on my Nabi, regardless how hard I try...
NabiLab 2015 recognize the Nabi without problems, but as soon as I select "Recovery installer", Nabi should reboot-bootloader (I suppose), but hangs at Nabi Logo (the small icon in the middel of screen) forever. Also in Control Panel, the device is shown as ""Fastboot" with the error symbol and the indication that the driver should be installed again (but of course, when I try to do it, Windows tells me that the newest drivers for that device are already installed).
I also tried with using directly adb in a cmd window, with the same result, as soon as I type "adb reboot-bootloader" and press enter.
I am really out of ideas...
Conrad-007 said:
Update: NO WAY to get TWRP on my Nabi, regardless how hard I try...
NabiLab 2015 recognize the Nabi without problems, but as soon as I select "Recovery installer", Nabi should reboot-bootloader (I suppose), but hangs at Nabi Logo (the small icon in the middel of screen) forever. Also in Control Panel, the device is shown as ""Fastboot" with the error symbol and the indication that the driver should be installed again (but of course, when I try to do it, Windows tells me that the newest drivers for that device are already installed).
I also tried with using directly adb in a cmd window, with the same result, as soon as I type "adb reboot-bootloader" and press enter.
I am really out of ideas...
Click to expand...
Click to collapse
The hang with Nabi logo is because the fastboot driver is somehow broke. You will likely have to install it manually. Which driver are you using?
I gave most of the driver options here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
aicjofs said:
The hang with Nabi logo is because the fastboot driver is somehow broke. You will likely have to install it manually. Which driver are you using?
I gave most of the driver options here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Click to expand...
Click to collapse
You were right! I've installed the "nacked" driver on a fresh windows 7 and now I have TWRP on my Nabi 2!!! Thanks a lot!!!
Now is there a way to get rid of the freezing problem when I attach the charger while Nabi is on? Right now, if I attach the charger this way, Nabi 2 will freeze completely and only a reboot can get the normal functionality back!?!
Charging the Nabi in "off" state works however...
Conrad-007 said:
You were right! I've installed the "nacked" driver on a fresh windows 7 and now I have TWRP on my Nabi 2!!! Thanks a lot!!!
Now is there a way to get rid of the freezing problem when I attach the charger while Nabi is on? Right now, if I attach the charger this way, Nabi 2 will freeze completely and only a reboot can get the normal functionality back!?!
Charging the Nabi in "off" state works however...
Click to expand...
Click to collapse
I dont have Nabi2's anymore but both my kids tablets did the same thing. I never really found a solution. I did buy a cable from Nabi store that has the orange braid covering. It seemed to make a difference, but it still happened from time to time.
Happy New Year!
As I mentioned, I was finally able to install TWRP and did all wiping, cleaning, repairing tasks that were available
After that I flashed the "Nabixus 0.1beta for Nabi 2" ROM which worked very nice.
But... I still have the same problems starting up the Nabi!
When I finally succeed to start it (after many trials), it works well, but if I let it go in standby and wait more that a few minutes, I am not able to wake it up again and I have to do a restart (about 10 sec. hold the Power button down).
What I`m not getting at all: is this a software or a hardware problem? Can my Nabi 2 be repaired after all, or I just have to scrap it?
The last thing I could still think to try would be to repair the partition table through TWRP / Adb / Adb shell. Should I try it? Where can I get a good partition table for my NV7A and, after having it, which commands are required?
... aicjofs, please... help
Conrad-007 said:
Happy New Year!
As I mentioned, I was finally able to install TWRP and did all wiping, cleaning, repairing tasks that were available
After that I flashed the "Nabixus 0.1beta for Nabi 2" ROM which worked very nice.
But... I still have the same problems starting up the Nabi!
When I finally succeed to start it (after many trials), it works well, but if I let it go in standby and wait more that a few minutes, I am not able to wake it up again and I have to do a restart (about 10 sec. hold the Power button down).
What I`m not getting at all: is this a software or a hardware problem? Can my Nabi 2 be repaired after all, or I just have to scrap it?
The last thing I could still think to try would be to repair the partition table through TWRP / Adb / Adb shell. Should I try it? Where can I get a good partition table for my NV7A and, after having it, which commands are required?
Click to expand...
Click to collapse
You can't repair the partition table from adb/TWRP. It's read only. You could through nvflash but I don't think the partition table could possibly cause the issue. I think you are meaning fix super blocks and inodes of the filesystem? Even that is a stretch if it's happening how you describe it but with a try. Did you try repair filesystem like we talked about earlier? If not backup all the data and try a wipe data. That will make sure to blow away and reformat the data partition.
It could be hardware. I know for sure the charging system causes it when plugged in but not about the first boot stuff or when it's not charging.
Thank you aicjofs for your answer,
yes, I did attempt to repair the system, data, cache and it was successfully. I did it several times. I also wiped everything a few times and installed the Nabixus ROM afterwards. Nothing helped. It's like the operating system needs to "get warm" somehow, because I have to try to power on the system many times, until I get it work... but after that, if the Nabi goes in standby, I have to start the whole thing over
How can I check for damaged blocks, etc.? If I can do it and find some, could they be marked as "bad" and isolated? Would it make sense?