Accidentally allowed the battery to drain too low... At first the device would boot up just fine and would get to the OS then shut off. So I downloaded the updated FFF 1.4A.zip flashable bootloader, placed it on the device and was about to install it, in hopes of alleviating this issue, but the device shut off after the file transfer, before I could flash it, and now it will not turn back on.
I'm running this bootloader - http://forum.xda-developers.com/showthread.php?t=1615093 ...
As I said, it won't even turn on (no green light) when I push the button at this point.
When I plug it into the USB cable and/or the wall-charger, the "FIREFIREFIRE Extended Bootloader" screen and the green light just flashes over and over...
Any ideas?
If I could just get it to STOP FLASHING the bootloader screen and get into recovery I have "fff-u-boot_v1.4a.zip" waiting to be flashed...
I had put that file on the device to fix this problem but it shut off on me right after the transfer and it has been flashing the bootloader screen since then...
All I need is to get into recovery!!!!! ARGH!!
I have read from the experts, that you should plug it in, hold the power button down for at least 10 seconds (this makes sure it is off) and let it charge for a couple of hours.
Sent from my Amazon Kindle Fire using xda app-developers app
Yea... I've tried that... However, no matter what I plug it into, USB cable or stock "wall-charger", the bootloader screen just flashes. The power button is unresponsive during this. Holding it down does nothing...
I'm hoping to avoid having to do this - http://forum.xda-developers.com/showthread.php?t=1806620&highlight=battery+dead
But I'm preparing for this last resort as it's becoming increasingly clear that this may be necessary.
Anyone have any other ideas?
Problem solved, new bootloader installed!
For some strange reason the bootloader screen stopped flashing after I decided to try plugging it into the stock wall charger again. It stopped flashing and allowed me to access recovery. I unplugged it and it stayed on long enough for me to install the new bootloader...
All is now good. What is strange however is the bootloader didn't stop the boot process. She booted up right into the OS and stayed on. I plugged it in, navigated to Settings > Battery and it is charging!
VERY WEIRD but very cool!
So for those of you having issues with charging, it's absolutely necessary to have FFF 1.4A bootloader installed! If you cannot get into recovery or the device will not turn on, just keep trying the stock wall charger. Just plug it in and keep plugging it in. Keep on messing with it. Eventually, somehow, it will take enough of a charge to get you into recovery...
Related
OK.
I will put in a detailed info about what happened.
A week back, my wildfire's touchscreen started to function abnormally.
I was rooted and on Cyanogenmod 7.0.3
So, I flashed the phone with DK custom FROYO to make it look like sense so that the warranty is not void and took it to the HTC store.
They replaced the touchscreen for a flat fee (It was water damage according to them. But the phone was never used in wet conditions nor exposed to water)
But anyway, the phone was working fine when I brought it home from their store.
Then I flashed CM7.0.3 again.
And everything was working fine.
I OCed acc. to CM's settings to 652-352 Mhz.
And left the phone to charge in charger overnight.
When I woke up, the phone was off and there was just the red LED light blinking.
I tried to boot it again, but nothing works.
Pressing the power button does not do anything.
The phone still boots into recovery. At times.
I don't know what makes it boot into recovery. But at times it does, at times it doesn't. (Right now it's not booting into recovery no matter what I do)
Just the red LED keeps on blinking.
Please help.
I am not familiar with pushing commands onto the wildfire since I use a mac.
Please suggest any methods. If they involve using command line, I can use my windows PC for that. But please give a how-to of length enough for a noob ) ) to understand.
Thank you.
Pulz
EDIT :
I got to boot into recovery once. Tried to reflash CM7.0.3
It came to "Installing update" and then failed to go further.
Tried to install DK Custom Froyo 4.5
And it went to opening package and then failed to go further.
Now entering into a panic mode !
Red light blinking generally occurs when phone is hot and plugged in to wall socket. Is it so at that time ?
Unplug the charger or usb. Remove the battery and reinstall the battery. Try to boot into hboot mode (volume down + power) or fastboot mode (trackpad + power) . If your phone can boot into hboot/fastboot mode and has no restarts or power offs, then I think you can solve it.
Try to clear storage from hboot menu. Or factory reset from recovery once you enter it. If still it is not solved, try using "pc49img" method of flashing an RUU from the hboot menu. Hope it helps. Shouldn't help if there is hardware issue.
Sent from my Blade using XDA App
hye another noob here running on cm7.
actually i have the similiar problem my wildfire start rebooting over and over again but the cause is different.
this problem happen after i want to know what class my micro sd is.
what i do is i go to settings>storage>unmount sd card.
so after knowing the class were i insert back the card then the problem happens.
my phone start to crash then cm7 logo appear after that i enter my pin no so brought me back to the home screen after few seconds the logo appear again so i have 2 repeat the same steps...
this happen many times what i do is i remove the battery wait few hours then turn back on..
so help me if someone have the similiar problem and solutions.. thanks!!
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.
Just the title. This is an absolute disaster. It won't turn off, it just boot loops in recovery. I can't turn it off, I can't install a new recovery or anything via ADB because it's not recognized (with or without Kies). The only thing I seem capable of doing is just letting it sit on the charger attempting to boot into TWRP and failing. I'm at my wits' end.
Does anyone have ANY ideas? I'm seriously close to smashing it with a hammer and throwing it in the trash.
SomeGuyDude said:
Just the title. This is an absolute disaster. It won't turn off, it just boot loops in recovery. I can't turn it off, I can't install a new recovery or anything via ADB because it's not recognized (with or without Kies). The only thing I seem capable of doing is just letting it sit on the charger attempting to boot into TWRP and failing. I'm at my wits' end.
Does anyone have ANY ideas? I'm seriously close to smashing it with a hammer and throwing it in the trash.
Click to expand...
Click to collapse
Maybe about same problem you got? http://forum.xda-developers.com/galaxy-tab-pro-12-10-8/help/bricked-tablet-downloading-t3094492
Which model is it? 12.2, 10.1, or 8.4,
Sent from my SM-N910T using XDA Free mobile app
Just recovered my tablet from the same issue. In order to get into download mode, I had to let the battery fully drain. Then, holding the home and vol down keys, I plugged it into the charger. Plugging the charger in while the battery was drained automatically powered it up. After I saw the download warning, I released the buttons and entered download mode as usual. Then I flashed the latest TWRP with Odin.
No other combination of booting or button pressing worked. Trying to enter download with home+vol down and pressing power did not work for me either.
Good luck and PM me if you have any questions about this. I hope I explained it correctly.
Okay so here's what happened. I unlocked my device just fine, and attempted to install a ROM, didn't work, So i decide I'm going to try to install cyanogenmod. I go this (wikiDOTcyanogenmodDOTORG/w/Install_CM_for_a5 )wiki tutorial [/URL] and I attempt to flash clockworkmod recovery via this link (builderDOTunstableappsDOTCOM/#/latest/clockworkmodrecovery/a5) When i flash, it installs. But then upon booting I get the app for developement only screen, and it's stuck showing my battery charge screen, with the orange charge light. Anyways I can't boot using the power down volume combo. I'm currently waiting on the battery to die so I can reflash the stock recovery, because fastboot won't recognize the device when I plug it in, even though my computer makes the device connected tone. So should I just wait until the battery dies? Or is there something else I can do?
Any help will be appreciated, thanks
Solved
I actually solved my problem. I waited for the phone to die, powered it on normally. Then to reset the device and held the power and up button as soon as the screen went black hit down on the volume and got into my bootloader.
I just wiped my phone with TWRP using the "advanced" settings and ticked everything. Obviously not a good idea as I think I have wiped everything including the ROM from my phone. Any idea how to get it going again? It just goes to the "Sony Xperia" screen and stays there when booting. I'm not sure how to get back into TWRP (i used to get there from a utilities app that restarted the phone into recovery). I have TWRP backup on my computer before I did the stupid thing...
Thanks for any help!
I've tried to flash from Emma and and Xperia Companion but I can't enter Flashmode (hold the volume down button and connect to computer). It just automatically turns on and shows the Sony/Xperia screen and the LED is solid RED.
I let it run down over night and still unable to enter Flashmode.
I assume TWRP is still there as it was the program that wiped the phone. Any ideas how I can get into TWRP?
The computer does not recognise the phone either. It was rooted and had an unlocked bootloader before it happened.
Thanks!
Hold power down and press power button. Release power button when phone vibrates but keep holding vol down until you see twrp logo. If you don't see it after maybe 10 seconds. If nothing happens you can try pressing power button and when you see led light keep pressing or holding (try both) vol down. If that doesn't work then you can try flashing with flashtool. You can check my thread for downloads and instructions
col320ce said:
I just wiped my phone with TWRP using the "advanced" settings and ticked everything. Obviously not a good idea as I think I have wiped everything including the ROM from my phone. Any idea how to get it going again? It just goes to the "Sony Xperia" screen and stays there when booting. I'm not sure how to get back into TWRP (i used to get there from a utilities app that restarted the phone into recovery). I have TWRP backup on my computer before I did the stupid thing...
Thanks for any help!
Click to expand...
Click to collapse
In sim card slot there is a small red button. Hold it down with toothpick or paper clip until you feel three vibrations. That will shut off your phone.
Now you can try Flashtool or Emma.
Thanks so far ... here is an update.
After letting it run down overnight it eventually let me get it into flashmode. Xperia Companion doesn't work (unlocked) but Emma is trying to work. It has taken a few hours to download the software as the phone only stays in flashmode for about 30 seconds but it was able to eventually download the software. Now it is trying to load it but it gets to 11% and the phone goes out of flashmode (but automatically re enters it without me doing anything) and the cycle continues. Is there any way to force it to stay in flashmode?
I've tried the suggestions above to get to TWRP but nothing seems to work.
I can think of 2 reasons. Either emma is broken (never used it, can't tell) or your connection to pc gets interrupted by bad cable or broken connector. Why don't you try flashtool instead of emma?
col320ce said:
Thanks so far ... here is an update.
After letting it run down overnight it eventually let me get it into flashmode. Xperia Companion doesn't work (unlocked) but Emma is trying to work. It has taken a few hours to download the software as the phone only stays in flashmode for about 30 seconds but it was able to eventually download the software. Now it is trying to load it but it gets to 11% and the phone goes out of flashmode (but automatically re enters it without me doing anything) and the cycle continues. Is there any way to force it to stay in flashmode?
I've tried the suggestions above to get to TWRP but nothing seems to work.
Click to expand...
Click to collapse
Silly question, but did you recharge your battery after letting it run overnight?
PiixJu said:
Silly question, but did you recharge your battery after letting it run overnight?
Click to expand...
Click to collapse
I wiped whole storage few times as he did (Without letting it run overnight tho) and you can't charge your battery without system or recovery. If your battery drains in this situation you are SOL
yeah I think that is my problem. The phone won't charge and that's why it only stays on for 30 seconds before losing connection.
Can I charge the battery out of the phone? I know it a pain to pull out ... but I've done it before as it needs changing every 12 mths or so.
Not sure about that. I mean there has to be a way to charge it outside phone but you would need special equipment since you can't just use random charger. Since you said you charged your batteries before you could try to use one of them and hope that they have charge in them for flashing. I saw that @munjeni has a lot of experience with this phones hardware so you could try and contact him and ask if he knows about contact points on motherboard for charging
Ok. Got it going again eventually. Not sure exactly what I did that made it work but FYI these are the things that I did that seemed to help:
Charged it on my ASUS tablet charger today - seemed to do a better job than the other charger I was using (it was a Nokia). It seems to hold a very small charge but was not charging the battery properly. Hooked it up to Emma which had already managed to download the software and put the phone under my laptop (trying to warm the battery to squeeze everything our of it). 355 seconds later it had copied the software and the phone was able to turn on normally again. The phone was getting to about 60% of the software copied across before I used the ASUS charger and the heating the phone technique.
BTW I couldn't get flashtool to work. It recognised the phone but stopped saying USB debugging was off.
Thanks for everyones help!!