Develop Bugs

[Help] Kindle fire powers off instantly

So I am trying to get my Kindle to stay on long enough to flash to stock, but when I turn it on it is at the yellow recovery symbol. When I use the "Boot into normal" Mode on KFU, it will turn on after about 10 seconds. But after the Kindle is on, about 5 seconds later it just powers off. It is fully charged. How could you fix this?

http://forum.xda-developers.com/showthread.php?t=1623244

I charged it all night and it still dies right away. Also I cannot put FFF or anything on it because it isn't detected in recovery, only when it turns on for the 5 seconds. How do you fix this?

Very likely it isn't charging use USB to charge maybe you'll get lucky sending anything to the device in this state is to dangerous

Thepooch said:
Very likely it isn't charging use USB to charge maybe you'll get lucky sending anything to the device in this state is to dangerous
Click to expand...
Click to collapse
So you're saying I should just plug it in for the night, then try booting it again? What should I do after I get it on?

Well you haven't got that far and there's no promise it will even work because of the bootloader your running if it doesn't work then your looking at something different to fix it

Thepooch said:
Well you haven't got that far and there's no promise it will even work because of the bootloader your running if it doesn't work then your looking at something different to fix it
Click to expand...
Click to collapse
I don't have a bootloader. I am just running everything normal, except it's rooted.

any progress? If you have a yellow triangle that is the bootloader just to clarify

Thepooch said:
any progress? If you have a yellow triangle that is the bootloader just to clarify
Click to expand...
Click to collapse
It is plugged in still, I will try it out now. Also thanks for clarifying that.

Did you hold the power button down for 20-30 sec? If its fully charged, then either you have to do a 20-30 sec hard reset or its stuck in fastboot mode. Well, actually, no, its not in fast boot mode if it turns off. So try the hard reset.

[Q] Charging Bootloop

When I plug my phone into my a charger and it is charging my phone gets stuck into a bootloop where I can't turn it off nor turn it on. It wont even go to the Samsung logo, it just is black and keeps turning on/off. Only way I have to get around this is by unplugging, pulling battery, reboot recovery, plug back in, then I can reboot to system. Any ideas on a solution to this?

riku-vomoto said:
When I plug my phone into my a charger and it is charging my phone gets stuck into a bootloop where I can't turn it off nor turn it on. It wont even go to the Samsung logo, it just is black and keeps turning on/off. Only way I have to get around this is by unplugging, pulling battery, reboot recovery, plug back in, then I can reboot to system. Any ideas on a solution to this?
Click to expand...
Click to collapse
Don't try to power it on while plugged in. Ain't much else to suggest there. I find doing the button combo for download mode then pressing vol-dn at the warning screen works too. This is the normal it's not a bootloop. The way these charge w/ the power off is strange.

billard412 said:
Don't try to power it on while plugged in. Ain't much else to suggest there. I find doing the button combo for download mode then pressing vol-dn at the warning screen works too. This is the normal it's not a bootloop. The way these charge w/ the power off is strange.
Click to expand...
Click to collapse
Okay sounds good; thought it was just a problem with my phone but guess not lol. Thanks for the quick reply !

riku-vomoto said:
When I plug my phone into my a charger and it is charging my phone gets stuck into a bootloop where I can't turn it off nor turn it on. It wont even go to the Samsung logo, it just is black and keeps turning on/off. Only way I have to get around this is by unplugging, pulling battery, reboot recovery, plug back in, then I can reboot to system. Any ideas on a solution to this?
Click to expand...
Click to collapse
What recovery and rom are you using? This is not a normal behavior. It doesn't happen on my phone using Stock rom/TWRP recovery.

poit said:
What recovery and rom are you using? This is not a normal behavior. It doesn't happen on my phone using Stock rom/TWRP recovery.
Click to expand...
Click to collapse
That's weird as I'm on my 5th s3 since 6-21 and this has been normal behavior on every one regardless of rom. The S2 did the same stupid shiit. Its almost impossible to turn these on while plugged in and shut off.

poit said:
What recovery and rom are you using? This is not a normal behavior. It doesn't happen on my phone using Stock rom/TWRP recovery.
Click to expand...
Click to collapse
I usually use freeg3 from Clark, but I flash about every ROM when they are updated to try it out; I use TWRP to flash them all. My phone is infected with anthrax, but It was before and after it. I even tried flashing the stock .tar from odin :/

When the screen is black, simply hold the power button in until you see the Samsung logo.
Sent from my SPH-L710 using xda premium

I just confirmed again that my phone doesn't do that. With the phone on, I plugged into the charger. Power off, wait until the green battery icon appears. Hold power button, phone boots normally.
I'd guess somewhere along the way you acquired a wonky bootloader. You could probably try just replacing the bootloader, I know there is a way to do that but I'm not sure how. Probably someone else could quote the procedure off the top of their head. If not, I would guess a full odin to stock would fix it also.

My phone does this too. Sometimes it shows a charging battery, sometimes it vibrates, and sometimes I even see the Samsung logo, but it always refuses to turn on while it is plugged up.

My phone doesn't do this. It looks to be a hit or miss on if your phone will do it.
Generating random authentication keys

Or it could have to do with a particular flash that has corrupted the boot loader. People need to be clear what roms they are on, and if they have ever tried to go back to FULL stock through Odin to fix this. Until they have reflashed the Stock Bootloader, there is no way to know what's going on.

[Q] Kindle Fire (1st Gen) will not turn on post failed root.

Hello,
1st ever post. I tried to root my KF. During root lost power, when power restored got the yellow triangle of death. Was able to enter TWRP, while trying to restore, lost power again. Unfortunately now for me, I am unable to turn the KF on so that I can work on restoring it.
I have tried to power cycle it many times. Holding power button for 20 secs and what not. No effect. I have left my KF plugged in for over 8 hours to charge the battery with the stock charger. Have retried to hold power button with no effect.
I know that once I get my KF to turn on I will be able to fix this but I am at a loss. Multiple Google searches have not come up with out any luck.
Please help if you can.
Thanks
Tater

Tater Noobsauce said:
Hello,
1st ever post. I tried to root my KF. During root lost power, when power restored got the yellow triangle of death. Was able to enter TWRP, while trying to restore, lost power again. Unfortunately now for me, I am unable to turn the KF on so that I can work on restoring it.
I have tried to power cycle it many times. Holding power button for 20 secs and what not. No effect. I have left my KF plugged in for over 8 hours to charge the battery with the stock charger. Have retried to hold power button with no effect.
I know that once I get my KF to turn on I will be able to fix this but I am at a loss.
Click to expand...
Click to collapse
I had a similar problem, though I did not end up losing power. When I found myself in a boot loop, I plugged in so that I wouldn't lose too much power while I was figuring out what was going on.
In my case, if I remember correctly, I had somehow managed to put my Kindle in a fastboot mode[1] that allowed me to do a few useful things before I had root[2], but was still in fastboot mode. After about four days of wondering how on earth I was going to sort out this brand new electronic brick I'd been given, I decided to try reading up on how to use fastboot. I don't remember which command I used (sorry, too many weeks and too much sleep deprivation have passed!), but I think it may have been "continue".
[1.] Yeah, somehow. Could have been automated by the root script I probably shouldn't have used (I probably didn't read enough directions before proceeding), could have been when I was trying to use fastboot to do something or other. See footnote 2.
[2.] ...like install the bootloader and recovery.

dzdzjb said:
I had a similar problem, though I did not end up losing power. When I found myself in a boot loop, I plugged in so that I wouldn't lose too much power while I was figuring out what was going on.
In my case, if I remember correctly, I had somehow managed to put my Kindle in a fastboot mode[1] that allowed me to do a few useful things before I had root[2], but was still in fastboot mode. After about four days of wondering how on earth I was going to sort out this brand new electronic brick I'd been given, I decided to try reading up on how to use fastboot. I don't remember which command I used (sorry, too many weeks and too much sleep deprivation have passed!), but I think it may have been "continue".
[1.] Yeah, somehow. Could have been automated by the root script I probably shouldn't have used (I probably didn't read enough directions before proceeding), could have been when I was trying to use fastboot to do something or other. See footnote 2.
[2.] ...like install the bootloader and recovery.
Click to expand...
Click to collapse
I would certainly do those things, but i can't even turn the unit on for the comouter to notice that i have aperipheral plugged in... in this lies the problem.

Tater Noobsauce said:
I would certainly do those things, but i can't even turn the unit on for the comouter to notice that i have aperipheral plugged in... in this lies the problem.
Click to expand...
Click to collapse
Your bootloader is shot. You need to look into Firekit, usbboot and the "shorting trick".

Is my M8 bricked?

Ok folks, normally I figure these things out but this one has me a bit concerned.
I was in ViperROM HUB and installed a font package, it needed to restart in recovery to install, so I allowed it. I turned to my computer and when I next looked at my phone the screen is off and refuses to come on. When depress the power button I get a vibration feedback but the screen won't come on. I tried VOL DOWN and POWER but nothing is happening. Im gonna let the battery run dead and see if that will resolve it.
Has anyone encountered anything like this before?

3NE said:
Ok folks, normally I figure these things out but this one has me a bit concerned.
I was in ViperROM HUB and installed a font package, it needed to restart in recovery to install, so I allowed it. I turned to my computer and when I next looked at my phone the screen is off and refuses to come on. When depress the power button I get a vibration feedback but the screen won't come on. I tried VOL DOWN and POWER but nothing is happening. Im gonna let the battery run dead and see if that will resolve it.
Has anyone encountered anything like this before?
Click to expand...
Click to collapse
Hey!
I dont think its bricked.
Ghost helped me out with my problem, see below solution.
Try holding POWER + VOLUME UP for 20 seconds and it should restart.
However my case was different I was stuck in HTC logo screen and no way to restart.

On the M8 it is Power and Vol Up to perform a "battery pull".
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Thanks grega_slo and gaiden0000 for the quick response and spot on advice.
I did that before but it didn't work, it works now…guess I didn't hold VOL UP long enough.

Yeah I didn`t know about VOLUP either
It scared the crap out of me when I S-OFFed the device and was stuck haha

grega_slo said:
Yeah I didn`t know about VOLUP either
It scared the crap out of me when I S-OFFed the device and was stuck haha
Click to expand...
Click to collapse
having the same problem. flashed cyanogen nightly and when it rebooted got to the splash and then black. nothing. none of the above methods seems to bring it back. I can hold the power and vol up and get the splash to reappear but still goes to black. any thoughts of have I really bricked this phone?

cquinn said:
having the same problem. flashed cyanogen nightly and when it rebooted got to the splash and then black. nothing. none of the above methods seems to bring it back. I can hold the power and vol up and get the splash to reappear but still goes to black. any thoughts of have I really bricked this phone?
Click to expand...
Click to collapse
Fastboot clear cache and format eternal storage youll be good
Sent from my One M8 using XDA Premium HD app

cquinn said:
having the same problem. flashed cyanogen nightly and when it rebooted got to the splash and then black. nothing. none of the above methods seems to bring it back. I can hold the power and vol up and get the splash to reappear but still goes to black. any thoughts of have I really bricked this phone?
Click to expand...
Click to collapse
Put the usb cable in then press vol up and power until it restarts. As soon as you hear the ding on your pc press and hold vol down and power, you should then boot into hboot MENU.

pbedard said:
Fastboot clear cache and format eternal storage youll be good
Sent from my One M8 using XDA Premium HD app
Click to expand...
Click to collapse
when i use this either from fastboot or adb command prompt all I get is < waiting for device >
---------- Post added at 08:18 AM ---------- Previous post was at 08:10 AM ----------
ashyx said:
Put the usb cable in then press vol up and power until it restarts. As soon as you hear the ding on your pc press and hold vol down and power, you should then boot into hboot MENU.
Click to expand...
Click to collapse
never seem to hear a 'ding' or any other sound but no matter how I time it - power/vol up then power/vol down still results in htc splash then just black. Phone was quite warm (not quite hot) when I went to bed last night and this morning battery was at "0". When I first plugged it in and pushed the power button it alternated from the battery charging display to the TWRP locked screen but I couldn't seem to get it to stay on the TWRP screen no matter what I did. Now that I've used power/vol up I don't seem to get the battery or TWRP. just black or when trying power/vol up I get the splash. Power/vol down gives nothing - just black
EDIT: Just tried - let battery go dead. Plug in to computer hold power/vol down. Screen goes from battery icon to blank and back to battery icon.
EDIT: Pulled and reformatted sd card in Evo 4g LTE. Retried fastboot command still just shows "waiting for device". Even tried adb reboot bootloader and reply "device not found"

Could I use adb to reflash ruu? If so would the command be adb flash (filename)
Was beginning to lose hope of ever fixing this but a HUGE shout out to Simer03 who provided the critical piece of information - namely - add a ROM zip to your sd card. Hope nobody else ever has this problem but just in case
Post #4 here

Nothing is going to work unless you can either enter the boot loader or boot into the os.
You should still be able to access hboot unless that is corrupt. At the very least you need to hear the ding on your pc so you know the pc has recognized your device is connected.
Try again with vol up and power, hold until it reboots you should then hear that ding. If not check you have the necessary usb drivers installed on your pc or try a different usb cable.

Probably hard bricked - not sure

Hi,
after running a rooted Kitkat for a year or so I thought I wanted to install CM12.1. So I wiped and flashed via CWM Recovery and also flashed some GApps (probably the wrong one). After flashing (with confirmation that everything was successful), I wanted to reboot but after clicking on reboot, the screen just went black. Waiting for 5 mins, nothing changed.
Pushing the Power-On button lets the phone vibrate once, that's it. Pushing Vol+ or Vol- together with Power-On does not change anything. Connecting a charger to the phone, let the red LED flash once.
What can I do to revive my phone....?
Suggestions or hints are greatly appreciated

aalemann said:
Hi,
after running a rooted Kitkat for a year or so I thought I wanted to install CM12.1. So I wiped and flashed via CWM Recovery and also flashed some GApps (probably the wrong one). After flashing (with confirmation that everything was successful), I wanted to reboot but after clicking on reboot, the screen just went black. Waiting for 5 mins, nothing changed.
Pushing the Power-On button lets the phone vibrate once, that's it. Pushing Vol+ or Vol- together with Power-On does not change anything. Connecting a charger to the phone, let the red LED flash once.
What can I do to revive my phone....?
Suggestions or hints are greatly appreciated
Click to expand...
Click to collapse
Try holding power and volume up together for 8-10 seconds, just to make Sir it's totally powered off, then connect the charger and see if it starts charging. Older batteries don't do well in this phone. It wseems to me you might have had the sudden-battety-drain phenomenon when you flashed.

levone1 said:
Try holding power and volume up together for 8-10 seconds, just to make Sir it's totally powered off, then connect the charger and see if it starts charging. Older batteries don't do well in this phone. It wseems to me you might have had the sudden-battety-drain phenomenon when you flashed.
Click to expand...
Click to collapse
Thanks, that seemed to have work. I am now a happy user of CM12.1 on my Xperia Z1 Compact