I got ahold of an old phone and it was working fine until I attempted to connect it to my PC. It wouldn't even react, and my roommate (who gave it to me) took out the battery, which then caused this endless bootloop. If it's on the charger, it keeps blinking the battery (which looks empty and has the spinning circle in it), and if it's off, it just keeps blinking the Samsung logo. I can boot it into recovery and wipe (because it doesn't bootloop there for some reason), and it will boot into Android (sometimes) and then immediately bootloop all over again. I have attempted to Odin a stock ROM to it but it doesn't stay in downloader mode long enough. It just bootloops again. I can't even root this damned thing. Help!
Solved it. Don't know why, but it did NOT like the SD card I put in it. Would only work in recovery. Finally rooted and flashed Basix. Yay!
Maybe there is a hardware problem i.e. your phone's power button has stuck from inside (not the plastic button but the inside buuton).Try fixing that.
Sent from my Aqua Trend using Tapatalk
Itzabhaysingj said:
Maybe there is a hardware problem i.e. your phone's power button has stuck from inside (not the plastic button but the inside buuton).Try fixing that.
Click to expand...
Click to collapse
And how am I supposed to do that?
Great, I'm back where I started. A bootlooping paperweight. Now I can't even get it to boot into recovery. ****ing piece of ****.
Related
My sister said she spilled a little water on the screen of her phone the other day and it started boot looping.
Ive been trying to reflash it, but there are some issues...
If the phone is plugged in, it will cycle the charging battery on and off... unable to get into download or recovery.
If its not, it used to show the galaxy boot screen and turn on and off... now it just stays frozen on that screen. In either instance i was unable to get into recovery or download mode.
I got into recovery a couple of times when it actually booted the ROM, but everytime i would use the power button to try to make a selection the phone would just reboot and go into a cycle again.
I also got it into download mode once through the ROM but it cant get the ROM to boot anymore...
I might be able to get it into recovery but when i do it just reboots when i select anything.
and help would be awesome
thanks.
OH, when i actually got the ROM to boot it would throw an array of system errors and force closes. I also think the water had nothing to do with it and something she did after the water is what started causing the problems
I got recovery and i flashed a new kernal and ROM and erased everything and its still freezing at first Galaxy boot screen.
probably because the phone is water damaged?
See if the guide in the second link of my signature will help.
Thanks ill give it a shot.
But a major problem is that i am unable to get it to boot into download mode.
So i got CWM to boot, and i reflashed the kernal and ROM, with no luck.
CWM read catch error. Unable to mount... format... ect...
From what ive been reading the internal catch is fried....
Anyone have a motherboard they want to ship me? LOL :laugh:
Thanks lumin30, I finally found a way to get the phone into download mode. (take the battery out, Put it back in, hold buttons, plug USB in, press power button) after a few reboots it would finally go.
I followed the link and got it back to stock and it booted. Now letting it sit to settle in and hopefully it will be functional again.
This thread can be deleted! :good:
I think i might have wrecked my P5110!
I rooted it to Cyanogen mod about 6 month ago to CM10.1.1 and that was great.
I had been using the built in updater to get the latest Cyanogen firmware without any problem. Decided to try a CM 10.2 nightly but was having big problems with it draining battery, crashing and rebooting for no apparent reason.
No problems thinks I, just unwind it to an older version of CM from the built in Cyanogen Mod Updater. I selected 10.1.3 RC2, and left it be.
Came back to it some time later to find the old logo spinning there. Figured it was still running and left it some more, and some more, and some more and it just kept spinning. I guess its knackered. I DID NOT wipe the cache and data as i was doing it from within Cyanogen so naively thought it would work okay.
Okay thinks I, go into recovery, wipe the cache. No dice. Try as i may i can NOT get ClockWorkRecovery to come up, only ODIN.
Talk about fools rush in. Simple thinks I, reinstall CWM from ODIN, go back into CWM, wipe the cache, see if that works.
flashing goes smoothly, but try as i may i can no longer get into ODIN or CWM, only into a never ending circle of Cyanogen bootup.
Any suggestions for a next step. Had the worst day at work and really shouldn't have bothered touching the damn thing!
Oh, I might well have spotted the problem
I thought I was flashing the CWM for P5110, but a closer inspection of the filename
GT-P5100_ClockworkMod-Recovery_6.0.1.0.tar
Shows quite clearly what i've done.
I'm guessing there is no coming back from this?
Vannystick said:
Oh, I might well have spotted the problem
I thought I was flashing the CWM for P5110, but a closer inspection of the filename
GT-P5100_ClockworkMod-Recovery_6.0.1.0.tar
Shows quite clearly what i've done.
I'm guessing there is no coming back from this?
Click to expand...
Click to collapse
Flash stock firmware via pc odin this will solve your issues. ....
Sent from my GT-N7100 using XDA Premium 4 mobile app
Every time you flash with ANY ROM you need to wipe data or bootloop obviously will appear.
Vannystick said:
i can no longer get into ODIN or CWM, only into a never ending circle of Cyanogen bootup.
Click to expand...
Click to collapse
Even though your recovery may be screwed up, it's strange that you can't get to the download mode... So, what exactly happens if you force reboot by holding power for several seconds, and immediately after that hold power and Volume Up together while it's powering up?
When stuck in the CM boot up, pressing and holding the power button would force a shut down, but the tab would then instantly reboot.
Holding the volume up (or down, i was desperate) until the samsung logo appeared wouldn't get me to ODIN, it would go to the CM boot screen.
If i plugged it into the charger once in the CM splash, and powered down, it would take me to the charge screen. Pulling the plug would then turn it off, without it rebooting.
Initially this wouldn't work, but perhaps because i was being impatient. All the instructions i had read say that the volume button can be released once the samsung logo pops up, perhaps i've miss read. Ultimately i found (more by accident than anything), you need to keep the volume button pressed until the second time the samsung logo pops up, then it will enter ODIN.
I managed to download a a stock rom from SamMobile, and flash it in.
It still wouldn't boot though, until i went into recovery and wiped data/cache. It also then took rather a long time to boot back up, presumably unpacking various 'stuff', had me a little concerned, so i left it alone for a few hours and came back to find the first boot welcome screen.
Lesson to be learned, always wipe the cache/data before an update, even if the previous half dozen CM updates had been fine.
I think what actually screwed things up was going from a 10.2 beta BACK to a 10.1 RC ROM.
Oh well, its working happily again, and not falling over like on the 10.2 beta. And i dont need to buy a RIFF box!
I was having terrible GPS reception and I tried the antenna fix- sliding a tiny peace of thick paper under the antenna connectors:
https://www.youtube.com/watch?v=K1-uCIb-t8I
After powering up the phone booted once, then rebooted after couple of seconds and has been bootlooping on Google logo since.
- Takes much more time than normally to power on, then falls into Google logo bootloop,
- Cannot go into bootloader, power + vol buttond doesn't do a thing,
- If I hold vol up + vol down while bootlooping it powers off,
- Plugging in doesn't change anything, no charging indicator when powered off.
Is there anything I can do ?
Did I kill my phone ? If so, how ? What could I have damaged by simply prying the cover open ?
Are all the connections secure?
I checked all the connectors, they're ok.
After a day or so the phone got back to the living- I was able to boot and play around for a while.
Then I tried to update (I got the Lolipop OTA), which failed...
Downloaded the factory image and the flash attempt always gets stuck at " sending 'system'"...
Bootloader, radio, recovery, boot, everything gets flashed, then it gets stuck at flashing "system".
Any ideas ?
EDIT:
Flashed 4.4.4 in NRT without any problems, boots normally, still cannot flash Lolipop ...
Heniuro said:
After a day or so the phone got back to the living- I was able to boot and play around for a while.
Then I tried to update (I got the Lolipop OTA), which failed...
Downloaded the factory image and the flash attempt always gets stuck at " sending 'system'"...
Bootloader, radio, recovery, boot, everything gets flashed, then it gets stuck at flashing "system".
Any ideas ?
EDIT:
Flashed 4.4.4 in NRT without any problems, boots normally, still cannot flash Lolipop ...
Click to expand...
Click to collapse
Might need to wait for 5.1
5.0 is buggy
Last night I tried to flash TWRP just because I wanted to go to a custom ROM- alas, the phone now will not go past the google logo. It usually hangs there for 10-ish seconds and then reboots. Occasionally hangs there indefinitely. It's not a power button issue- the button worked just fine before flashing and I've confirmed it still works normally with a multimeter.
I tried to reflash stock using the Google images and "flashall.bat", which says it succeeded- but the phone still loops. I can get into fastboot, but I get the bootloop even in recovery. Running the similar script through Nexus Root Toolkit always fails on flashing the system partition- usually a buffer error due to a sparse header. Can't even seem to get it to do the "fastboot boot TWRP.img" or whatnot. I've flashed KitKat, Lollipop, and MM stock roms to no avail- they all say they succeed, then continue to bootloop.
I've tried just about everything I've seen on here- but not being able to get into recovery hampers efforts like repairing the persist partition.
Help?
When you boot into recovery, the phone reboots itself? If it does, it could be a sign of a failing power button.
When flashing a stock ROM, are you flashing userdata.img and then performing a factory reset/wipe before booting the phone with a stock ROM for the first time?
When I can get into recovery (without a restart), the phone is totally fine.
I think part of the issue is that the battery ran down while I was trying to do the repair- hence it trying to restart and failing. Power button still seems fine (again, confirmed with a multimeter). I left it plugged in to my iPad charger (since that's a 2A charger) overnight and it was still blinking red in the morning. I moved it upstairs and now I can't even make it that far.
Perhaps the battery was just shot by the time I got the "repair" done, hence the boot loops. Is there any way to revive it shy of cutting open the battery + charging manually (with a bench supply) or just replacing the battery altogether? I may try doing a motherboard swap with my working Nexus 5 just to see if it is in fact the battery.
When the phone is powered off and connected to a power source, do you ever see a flashing red LED? You flashed the correct twrp for the hammerhead?
I would try a new battery because it seems like everything is working.
I've tried Carbon but that one wouldn't actually boot up, just shut my screen off and would shut itself off.
AospExtended ROM, is just sitting at these bouncing dots.
Ressurection Remix, sits at the boot screen of whatever that...logo is supposed to be.
I'm at my witts end here and about to smash this piece of junk. Nothing on this phone has ever worked right since I got it. Figured I'd fix it by getting rid of their trash UI and do custom roms but apparently it can't even do THAT right.
Upgrade your device to EMUI 8. Then flash one of the Treble ROMs.
I can't even get into TWRP anymore. It just keeps going into the EMUI recovery everytime I hold down all 3 buttons.
Spykez0129 said:
I can't even get into TWRP anymore. It just keeps going into the EMUI recovery everytime I hold down all 3 buttons.
Click to expand...
Click to collapse
I've found out myself of why those custom roms wont boot, because you did not clear cache and dalvik before you booted to the custom rom. You wont have to smash ur phone if you do this.
SuperSwordSmasher said:
I've found out myself of why those custom roms wont boot, because you did not clear cache and dalvik before you booted to the custom rom. You wont have to smash ur phone if you do this.
Click to expand...
Click to collapse
That's something I do automatically without thinking. That stuff was finicky back in the OG Droid days so I always do it like 3 times just to make sure.
Anything else that would cause it to get stuck at the booting up screen? I get passed the blue screen and the your device is insecure or whatever. Then it just goes into the fancy booting logo and just sits there. Never on any of the phones I've rooted over the past decade ever got stuck like this.
WOHOOO! I MADE PROGRESS!
My phone is now stuck in a never ending bootloop and can't seem to get into any recovery. Can't even shut the phone off because it just turns itself back on. Backwards progress is where it's AT!
Bump, any ideas?
I went back to Motorola and bought an X4 but I'd like to get this working again so I can sell it.
Spykez0129 said:
Bump, any ideas?
I went back to Motorola and bought an X4 but I'd like to get this working again so I can sell it.
Click to expand...
Click to collapse
What honor 8 model do you use? It should not be Bootlooping then, if there is no solution you can always go to stock.
You could flash twrp again, with fastboot
Boot with power + volume up to boot into twrp
Use dload method