Database Users

[Q] app download killed phone

I so hope someone can help.
Downloaded an app which i then couldnt close no matter what so i pulled out the battery put it back in and now all i have is a black screen and cant use my phone at all.
Tried hooking up to Kies but it wont let me do anything as saying app is still open.
Really hoping i dont loose everything can anybody help???!!!!

what app was it ?

ph1n1c said:
I so hope someone can help.
Downloaded an app which i then couldnt close no matter what so i pulled out the battery put it back in and now all i have is a black screen and cant use my phone at all.
Tried hooking up to Kies but it wont let me do anything as saying app is still open.
Really hoping i dont loose everything can anybody help???!!!!
Click to expand...
Click to collapse
What was the app, and where did you download it from?
And if you hooked your phone up to kies and it saw it....then the phone must be powered up. Remove the battery again, wait 10 minutes, then replace it.
Sent from my GT-I9000 using XDA Premium App

From the silence I assume he realised he hadn't actually turned his phone off at all and sorted it out...or the app killed HIM as well.
Sent from my GT-I9000 using XDA Premium App

Nope im not dead and im a she not a he.
Yes the phone has power but only shows a black screen.
Yes the battery has actually been out all night.
No Kies did not tell me anything i got a box up on my phone when it conected saying could not connect as application open.
The application was called Kids mode by zoodles.
They have sent me 2 ways to reset my phone one of which to hold down the volume button then press the power button which shows a menu choose clear storage using the volume button and the phone should be restored....it doesnt do any of that just turns on.
The other way is this
a) Install the Android SDK from a website they mentioned
b) Connect the phone to the computer with a USB cable
c) Type "adb uninstall com.zoodles.kidmode"
of which i am currently attempting to understand.
If you know any different then your help would be appreciated.

oh and the app itself i found on the android market on my phone

try getting into recovery by pressing vol up+home button+power and release when the S logo pops up

Thank you for that. It didnt work.
Have been defeated all this messing about so have taken in to have system rebooted.

I had the same almost and am still locked in the "Logo of Limbo" ( the big S) after 10 days and dealers trying this and that. Can't say it was an app that caused it, but it seems resetting SGS is a task and a half sometimes

ph1n1c said:
Thank you for that. It didnt work.
Have been defeated all this messing about so have taken in to have system rebooted.
Click to expand...
Click to collapse
Well, it's not pressing but holding:
Shut down the phone
Hold Vol-Up+Home and power
Release power when you see "Galaxy S, GT-i9000, Samsung" blinks
if this doesnt work, try Vol+Down instead of Up, and update the status here with what you see.

[GUIDE] The 5 second bootloop! aka: Don't let your battery die!

Symptoms: The Kindle Fire starts booting normally, but then shuts off prematurely or reboots spontaneously before the device completes the startup process. In extreme cases, the bootlogo may not even appear on the display and only the power switch LED lights up before the device shuts off again.
Cause: The battery has been depleted to the point that not enough power gets delivered to the CPU. The CPU detects the low power condition and its safety features power off the device.
Solution: Use the stock 1.8 amp AC charger to recharge the battery. In most cases, this seems to be enough to get power to the CPU and battery that it will begin to charge again.
In some rare instances, not even the AC charger will be enough to charge the battery. Why? The Kindle Fire's hardware does not have the ability to charge its battery offline. The device needs to be up and running so the ramdisk can handle the battery charging operation and that requires the CPU to be powered up. If the battery cannot provide enough power to the CPU, it shuts off automatically and the boot process stops or restarts... a classic catch-22.
Devices without FireFireFire 1.4 (or later) will need to upgrade to that version. This bootloader stops the boot process for a low battery condition (less than 3%) and charges the battery to its specified minimum before continuing to boot.
If the device has an earlier version of FFF, use the temporary fastboot mode feature to fastboot flash the new version using fastboot. If the device is using the stock bootloader (white/orange "kindle fire" bootlogo), a factory cable is probably necessary to put the device into fastboot mode.
Although the preferred method of installing this bootloader is through TWRP, it is dangerous in this situation because TWRP could shut down without warning. Because of this potential for a premature TWRP shutdown and a bad flash as a result, fastboot must be used under these circumstances. The device can be powered entirely from the USB port while running the bootloader, so it's much safer in this regard. Be sure to check the MD5 sum of the distribution, extract the contents of the zip archive and find the binary inside the cache directory. Flash this file using fastboot.
Using an older version of FFF...
Code:
fastboot flash bootloader /path/to/u-boot.bin
fastboot reboot
With the stock bootloader...
Code:
fastboot -i 0x1949 flash bootloader /path/to/u-boot.bin
fastboot -i 0x1949 reboot
Note: In both cases above, the "/path/to/u-boot.bin" must be replaced with the actual path to the file's location.
After a reboot, the bootloader will automatically stop the boot process and begin charging. The backlight is normally off in battery charging mode to conserve power, but press and hold the power button for a few seconds and a battery charging notification will appear on the display.
Note: Currently, neither FFF 1.4 nor 1.4a will display a bootlogo before entering battery charging mode, so the device may appear to be bricked. Press and hold the power button for a few seconds to display the battery charging notice. In addition, these versions will only enter battery charging mode when hooked up to USB power and not the AC wall charger. The developer is aware of both situations and has indicated that he intends to implement fixes for these issues.
Credits
pokey9000 - For providing information about the Kindle Fire hardware
SBlood86 - For sharing his experiences and initial ideas for a fix
Hashcode - For fixing/implementing battery charging on the bootloader​

+1
Sent from my Amazon Kindle Fire using xda premium

My kindle fire is running Firefirefire 1.4a and when it boots normal mode it loads the Kindle Fire screen then restarts it's self. Trying to boot it in any other mode never boots it. The thing is charged but i cannot get it booting at all.

What if I do not have the stock charger?
I charge it using my PC?
Please help, I am lost without my kindle.

Kindle Fire Restarts on its own
A long while back, I rooted the kindle fire using the kindle fire utility .95. It worked fine for months. Then today, the device suddenly restarted and went into the "press power button to for recovery" page with the yellow triangle.
I can get it to go into the system for about 10 seconds but then it just restarts. To get in, I use the kindle fire utility and put it into normal boot mode. It goes in fine but then it restarts. I do have access to fastboot and i can get in. Battery power is near full so that wasn't the problem.
Anyways, after trying everything I found in the internet, i found the best solution was to use this thread:
[GUIDE] Kindle Fire For Beginners
Assuming you're already in fastboot mode, go down to post number 3 and start at step number 6. I got the u-boot.bin from this page Amazon Update
(you have to extract it). The twrp file I got from the kindle fire utility page.
The last step I did was step number 7 which was to reboot. Once I rebooted, it went into twrp recovery but said it couldn't access the memory or something of the sort. Then it did some sort of update and sort of took a long time to update. Then it restarted, paused for around 30+ seconds on the flashing kindle fire logo,and now its perfect.
Tip: To get into fastboot mode, the exact steps I took were:
1. Shut down Kindle completely.
2. From the kindle fire utility, select 1 and then select 1 again. It should come as waiting for device. After that plug in the kindle and let it do its things. Once the kindle fire logo pops up, keep on spamming 2 in the kindle fire utility to select fastboot mode till it lets you get in. You have to do it before it starts to shut down again.
After that, the fastboot things should be working and you can do the rest of the stuff starting from number 6.
I hope this helps some one.

JoshuaLintag said:
What if I do not have the stock charger?
I charge it using my PC?
Please help, I am lost without my kindle.
Click to expand...
Click to collapse
You need something with a higher charging output than a pc. The stock of charger puts out 1.8 amps, so you need a charger that is close to that. I know that some aftermarket iPad chargers are 2.1 amps so that may work if you can get one of those.
Sent from my Kindle Fire using xda premium

I am new to the Kindle Fire, as in I don't have one yet. But, this seems like kind of a big deal or does it only happen on rooted, customized Kindle Fires in which case Amazon probably doesn't care quite so much?
If this happens on a fully stock Fire when it goes dead I would imaging a ton of these being returned if something like this happened to gramps or someone less tech savvy...which I have a feeling is a huge number of Kindle Fire owners.

Evo_Shift said:
I am new to the Kindle Fire, as in I don't have one yet. But, this seems like kind of a big deal or does it only happen on rooted, customized Kindle Fires in which case Amazon probably doesn't care quite so much?
If this happens on a fully stock Fire when it goes dead I would imaging a ton of these being returned if something like this happened to gramps or someone less tech savvy...which I have a feeling is a huge number of Kindle Fire owners.
Click to expand...
Click to collapse
A new Kindle Fire purchased from Amazon comes with a stock wall charger. It does not come with a USB cable.

Evo_Shift said:
I am new to the Kindle Fire, as in I don't have one yet. But, this seems like kind of a big deal or does it only happen on rooted, customized Kindle Fires in which case Amazon probably doesn't care quite so much?
If this happens on a fully stock Fire when it goes dead I would imaging a ton of these being returned if something like this happened to gramps or someone less tech savvy...which I have a feeling is a huge number of Kindle Fire owners.
Click to expand...
Click to collapse
I think a more appropriate answer to your question can be found in the OP...
A couple of users have reported flashing back to the stock boot image to get out of this situation. The idea is that some ramdisks on custom ROMs may not be as efficient as stock when it comes to the battery charging software.
Click to expand...
Click to collapse

My Kindle starts up and turns off 2 seconds from turning it on.
ADB won't detect it also the KFU. help

JoshuaLintag said:
My Kindle starts up and turns off 2 seconds from turning it on.
ADB won't detect it also the KFU. help
Click to expand...
Click to collapse
This is a joke right? You're just toying with me, right? I mean, if you were serious then you wouldn't be very bright considering the answer to your problem is in the OP.
Oh, and also in this thread, WHERE I ALREADY TOLD YOU THE ANSWER!

soupmagnet said:
This is a joke right? You're just toying with me, right? I mean, if you were serious then you wouldn't be very bright considering the answer to your problem is in the OP.
Oh, and also in this thread, WHERE I ALREADY TOLD YOU THE ANSWER!
Click to expand...
Click to collapse
Maybe it's because you talked about your military background, but I get flashes of Full Metal Jacket during some of your "motivational teaching" posts...
You little scumbag!
I got your name!
I got your ass!
You will not laugh!
You will not cry!
You will learn by the numbers!
I will teach you!​
Anybody else?

kinfauns said:
Maybe it's because you talked about your military background, but I get flashes of Full Metal Jacket during some of your "motivational teaching" posts...
You little scumbag!
I got your name!
I got your ass!
You will not laugh!
You will not cry!
You will learn by the numbers!
I will teach you!​
Anybody else?
Click to expand...
Click to collapse
"Tough love" is better than no love at all.
Sent from my DROID BIONIC using Tapatalk

JoshuaLintag said:
My Kindle starts up and turns off 2 seconds from turning it on.
ADB won't detect it also the KFU. help
Click to expand...
Click to collapse
There will be times when I tell myself "Maybe you're being too hard on people".
Then I see stuff like this and snap out of it.

fzdolfan said:
"Tough love" is better than no love at all.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
I'll go with that. Maybe he didn't appreciate my tongue in cheek effort at humor... or I'm dating myself by quoting a 25 year old movie.

kinfauns said:
I'll go with that. Maybe he didn't appreciate my tongue in cheek effort at humor... or I'm dating myself by quoting a 25 year old movie.
Click to expand...
Click to collapse
That's a great movie BTW. Although, my love/hate relation with it is due to my drill sergeants watching it before every cycle to get themselves "motivated"
Ah, good times

Help, after a day or so of use, I rooted my kindle and installed google apps cause I couldn't install apps from the amazon apps store, i live abroad.
So, I was done modding my kindle, and after a day of regular use, my kindle began to shut down by itself and then it turns itself on and gets stuck in boot logo, I can manage to reboot it again using the normal boot command in kindle fire utility, but after 1 or 2 seconds of being on normally, its shuts itself down again and gets back to boot logo, any idea?
I would like to restore it to the original software (6.2.2) and try all over again if its possible, I can't send it back to amazon for warranty, I live outside the US so its not an option,
Please help!
Here is a video of what happens
http://www.youtube.com/watch?v=5zYtNZkpy7Y

luishawk said:
Help, after a day or so of use, I rooted my kindle and installed google apps cause I couldn't install apps from the amazon apps store, i live abroad.
So, I was done modding my kindle, and after a day of regular use, my kindle began to shut down by itself and then it turns itself on and gets stuck in boot logo, I can manage to reboot it again using the normal boot command in kindle fire utility, but after 1 or 2 seconds of being on normally, its shuts itself down again and gets back to boot logo, any idea?
I would like to restore it to the original software (6.2.2) and try all over again if its possible, I can't send it back to amazon for warranty, I live outside the US so its not an option,
Please help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=25400963
That link will take you to a thread that will explain what your problem is and how to fix it.

luishawk said:
Help, after a day or so of use, I rooted my kindle and installed google apps cause I couldn't install apps from the amazon apps store, i live abroad.
So, I was done modding my kindle, and after a day of regular use, my kindle began to shut down by itself and then it turns itself on and gets stuck in boot logo, I can manage to reboot it again using the normal boot command in kindle fire utility, but after 1 or 2 seconds of being on normally, its shuts itself down again and gets back to boot logo, any idea?
I would like to restore it to the original software (6.2.2) and try all over again if its possible, I can't send it back to amazon for warranty, I live outside the US so its not an option,
Please help!
Here is a video of what happens
http://www.youtube.com/watch?v=5zYtNZkpy7Y
Click to expand...
Click to collapse
Well, I think we've reached a new low today. You post a question...
http://forum.xda-developers.com/showthread.php?t=1648813
... and I answer it by providing a link to a thread that not only tells you what the problem is, but also suggests possible fixes. Instead of actually trying the fix... one of which is as simple as plugging in your charger! You copy/paste the same post into a thread that already gives you the answer in the OP!
I don't like going negative in my posts, but stuff like this really makes me wonder why I take the time...

After 5s bootloop, now my kindle fire total battery die, can't use stock 1.8 amp AC charger or usb - pc, usb - iphone charger. It not show 5s bootloop now .
Any solution ?
I wish to read this topic earlier

Kindle Fire NEVER ROOTED OR TAMPERED WITH in boot loop!

Ok so I have been reading around and most of what I found about my specific problem (boot loop with never putting any custom restore or root or ANYTHING on it) was pretty much was useless. I am not a complete beginner I have put custom mods on many of my devices, defy, atrix, dell streak, ect, and I have used ADB among other things (not that I am a pro at it mind you!)
I realize theres a thread up for this here
http://forum.xda-developers.com/showthread.php?t=1356257
but I want to know if this will work or is for people WHO HAVE NEVER DONE ANY MODIFICATIONS TO THEIR KINDLE FIRE
If it is then I will give it a shot.
What happened is (to my knowledge) my daughter was playing with it, and the next morning, it was boot looping, and quickly. So when I turn it on, it shows kindle fire then goes black, then repeats or once in a while will make it to the slide to unlock but 2-3 seconds after goes black and continues the bootloop
ANY HELP GREATLY APPRECIATED!

I recommend giving Amazon a call and get the device replaced.... If you still have a warranty?

AustinFire said:
I recommend giving Amazon a call and get the device replaced.... If you still have a warranty?
Click to expand...
Click to collapse
Why would I even try to fix it if I had a warrant? .... thanks anyways...
so ive downloaded the drivers and its basically not working, and the method for deleting the drivers (the one some idiot posted at least) will only work IF THE DEVICE STAY CONNECTED... Which it obviously isnt... and the 3-4 seconds of it saying KINDLE FIRE isnt long enough for me to find it in the device manager... by the time that updates its already rebooting...
so please anybody.... i dont understand why it would be so difficult.... I JUST NEED A RECOVERY I DONT NEED ANY OF MY STUFF

I have tried running ADB shell it says device not found....

If it is a hardware problem, then flashing is pointless. It did this on its own. Processor or board issue. Given the variety of things I see posted, hardware is an issue at least 1/3 of the time, my guess.
Sent from my Amazon Kindle Fire using xda app-developers app

Ixthusdan said:
If it is a hardware problem, then flashing is pointless. It did this on its own. Processor or board issue. Given the variety of things I see posted, hardware is an issue at least 1/3 of the time, my guess.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I would agree with you but i had installed some apps prior that seemed to make it glitchy and slow, and my daughter probably just triggered something (she is 3 and just constantly opens and taps things, i caught her in settings before) ... im pretty positive its software, especially since I read a few people with the same exact symptoms of mine... (it shows logo then reboots repeatedly, but sometimes makes it to the slide screen for like 4 seconds then it goes back to boot loop) Im sure I could fix it but I need help with getting my ADB in order or im screwed xD

I have also read several places that my problem could be fixed with a factory cable...

Have you tried a hard reset (hold the power button down for 30 seconds then power back on)? That should clear any stuck apps. It also sounds similar to a low power boot loop. If you haven't tried charging it you might want to put it on the charger overnight and see what that does. Other than that I don't know why a stock KF would bootloop.
Sent from my Amazon Kindle Fire using xda premium

Dead Battery
This is covered in a sticky post
http://forum.xda-developers.com/showthread.php?t=1623244

JimCo06 said:
Have you tried a hard reset (hold the power button down for 30 seconds then power back on)? That should clear any stuck apps. It also sounds similar to a low power boot loop. If you haven't tried charging it you might want to put it on the charger overnight and see what that does. Other than that I don't know why a stock KF would bootloop.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I have tried all of that, many times in fact. I also think its odd that it got stuck in a bootloop but from what ive read stock KF do that sometimes and its usually as simple as changing the way it boots which is why I think the factory cable is what I really need...

kinfauns said:
This is covered in a sticky post
http://forum.xda-developers.com/showthread.php?t=1623244
Click to expand...
Click to collapse
like i said... thats why i think i need a factory cable (fastboot)... but the problem here is i dont have a factory cable... lmao!
so basically im stuck at the fact that the drivers arent working, thus the KF is not being recognized, making fastboot impossible, or am i wrong? somebody please clarify...

Untraumatized said:
like i said... thats why i think i need a factory cable (fastboot)... but the problem here is i dont have a factory cable... lmao!
so basically im stuck at the fact that the drivers arent working, thus the KF is not being recognized, making fastboot impossible, or am i wrong? somebody please clarify...
Click to expand...
Click to collapse
You don't know whether or not your fastboot drivers are working because you must first put the device into fastboot mode to see if Windows will load the appropriate drivers.
Your problem is that on a stock device unable to boot into the system, 2 out of the 4 possible ways of putting the KF into fastboot mode are unavailable to you. The remaining options are to use a factory cable or to crack the case open to get access to the motherboard.
http://forum.xda-developers.com/showthread.php?t=1668159
There's another thread on the forums here about someone who disconnected the battery and hardwired it to a charger, but that seems like a really bad idea to me. A factory cable is your best/safest first step to getting out of your situation.

Plugged in my N7 while off, and now it's dead.

It is showing a black screen (with backlighting) and sometimes when I plug it in it shows the Google logo. Tried reseting it, and doing everything I have read, but nothing works. If I unplug it, it shuts off and won't boot. Any help?

Try booting into bootloader to reboot device =D
Sent from my Nexus 7 using xda app-developers app

nygfan760 said:
It is showing a black screen (with backlighting) and sometimes when I plug it in it shows the Google logo. Tried reseting it, and doing everything I have read, but nothing works. If I unplug it, it shuts off and won't boot. Any help?
Click to expand...
Click to collapse
Hi, nygfan760...
If you're getting some sort of response, then that's a good sign.
First, just LONG PRESS the POWER-BUTTON (for around 30 seconds); this will force power-down the device and reset it.
Try powering up from there.
-------
If that doesn't work...
...try to enter BOOTLOADER/FASTBOOT mode...
Press both Vol+/- buttons... and HOLD... whilst 'Holding'.., now press the POWER-BUTTON.
You should get the BOOTLOADER SCREEN... with UP and DOWN arrows, adjacent to the volume UP and DOWN keys... with the START option adjacent to the POWER-BUTTON.
Press the POWER-BUTTON... Hopefully you device will START...
Rrgrds,
Ged.

Hi, I also had similar problems with my Nexus 7. I was able to get in bootloader after multiple tries. Kind of randomly... didn't understand why. Unit would finally boot but turn off randomly again.
I gave a try and removed the back of the unit to take a look... I saw that the battery was nearly unplugged. I simply popped the connector in and voila! no more SOD, turning off, nothing.
So, the Nexus was probably turning itself off because there was randomly no more power comming from the battery. (and also could'nt charge it)
Here's a link on how to remove the back shell : http://www.ifixit.com/Teardown/Nexus+7+Teardown/9623/1
Look at Step 4.

None if it worked. Luckily I was still able to return it to office depot. Thanks for the suggestions!
Sent from my LG-E970 using xda app-developers app

Is there any way to fix my hard-bricked Fire HD 8 7th gen (douglas )?

My Fire HD 8 7th gen (douglas) won't fully boot up.
I pressed and held the power button, but the screen didn't show anything.
The reason why this happened is because the battery ran out during the Fire OS update.
I tried connecting it to a Windows PC, but I didn't see anything that looked like it in the device manager.
Is there any way to fix this condition?
If you need more information, please contact me.
I'm sorry. I can't speak English, so I use translation software.

Hide0302 said:
My Fire HD 8 7th gen (douglas) won't fully boot up.
I pressed and held the power button, but the screen didn't show anything.
The reason why this happened is because the battery ran out during the Fire OS update.
I tried connecting it to a Windows PC, but I didn't see anything that looked like it in the device manager.
Is there any way to fix this condition?
If you need more information, please contact me.
I'm sorry. I can't speak English, so I use translation software.
Click to expand...
Click to collapse
See
https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-8-2017-douglas-t3962846
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
See
https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-8-2017-douglas-t3962846
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I tried to fix it this way, but nothing appears on the display anymore! There's really nothing on display, not even the Amazon logo.
What I did specifically was to run gpt-fix-16G.sh. Then I saw "Hacked fastboot" on the screen. After that, FireOS came to be able to use normally, so I left it as it was.
But next day, nothing was shown on the screen anymore. Again, I tried gpt-fix-16G.sh and bootrom-step.sh, but It succeeds but does not show the screen. Once, TWRP was displayed for a moment. Also, the backlight was working correctly when operating TWRP. Otherwise, nothing else appeared on the screen.
Is it possible to get out of the current situation?
Translated with www.DeepL.com/Translator (free version)

Postscript
My Fire seems to turn on correctly.
I found that pressing and holding the power button and volume up button turns it on, and holding the power button for more than 20 seconds turns it off.
So why isn't the screen on?

When I tried to connect Fire to my PC, I periodically get a device connection sound and a device disconnect sound for a moment. I heard it. I looked into it in detail and found that the MediaTek Preloader USB VCOM (Android) seems to be causing it.
Perhaps the Preloader is not working properly.