Hi,
I have been running cm10.1 for a while on my galaxy note. I recently upgraded to 10.2 nightlies. Yesterday I opened the stock camera app (not focal) and when i clicked on capture the phone froze. So I had to pull out the battery. After that the phone would not start. I had full charge when my phone froze. When I connect a charger I get a battery logo with a loading circle icon. However this icon keeps flashing like a loop.
I am not able to go into recovery. But I can go into download mode only when I connect a charger or to the computer. However when I press volume up to confirm download mode, it exits it and the battery loop starts again.
Could someone please help me fix the issue.
Thanks
try another battery please
ThaiDai said:
try another battery please
Click to expand...
Click to collapse
Thanks ThaiDai. I put back my old defective original samsung battery and it booted.
I have similar issue. Flashed CM10.2 everything seemed to be working OK until I tried to go back into recovery and flash an update. Will not reboot from an attempt to go into recovery unless you plug in until you get green battery icon, then unplug and phone will boot. Once booted everything seems to work ok, you can reboot phone, download and install from play store, even reboot the phone, but any attempt to go into recovery will cause the device not to restart.
So, I can't flash anything, including a new recovery.. LOL... I'm wondering if this might be a battery issue as well, but I don't have a spare battery to try.
Related
Hello,
FYI; I'm running a Galaxy S i9000 with Slim Bean 3.1 (4.1.2) and semaphore kernel 2.6.5 (was 2.6.0)
So today I woke up my battery was a low at 5%. But everything was normal and had been for a long time. I fell back asleep as I have the day off.
Woke up an hour or two later and my phone was dead. So I put my phone into charge.
Came back about 40 minutes later, enough charge to boot the phone, check my messages, but as I pressed the power button it just went into bootloop. And it hasn't done anything but that since. Every time I try to turn the phone on, the Galaxy S logo appears, then semaphore kernel logo appears, then disappears and reappears and then the whole process repeats.
And I tried plugging in the phone again to charge, but every time I do, the empty battery icon appears, it disappears and reappears, then turns off and turns back on again to do the exact same thing.
So on and off charge, it won't do anything but repeat a few steps over and over.
I cannot enter recovery, cannot boot the phone, the phone does not respond to being plugged into the charger, but I can enter download mode.
So I started googling and trying to fix my problem.
So far I have tried:
- Several three button combos to enter recovery.
- Using ADB to enter recovery (but as the phone isn't on, this doesn't do anything)
- Pulling out the battery, putting it in holding three button combos
- Trying different batteries
- Charging the phone
- Flashing semaphore JB 2.6.5 using ODIN
So basically the phone is bootlooping; when in charge, charge looping (is that even a thing?); and won't respond to any attempts to boot into recovery or boot at all.
I'm trying to avoid just wiping the phone using ODIN and reinstalling from GB to JB (which I have done before, and know how to do).
I'm currently leaving it to bootloop until the battery is actually dead and then I'll see if I can try all over again. Doubt it though.
Try a Devil I9000 kernel .tar from here:
http://rootaxbox.no-ip.org/derteufel/jellybean/
Bejda said:
Try a Devil I9000 kernel .tar from here:
http://rootaxbox.no-ip.org/derteufel/jellybean/
Click to expand...
Click to collapse
What would that do?
It can be or battery this happens with me if the battery is dead it will only go into download mode.....
Sent from my GT-I9000 using xda premium
Zorigo said:
What would that do?
Click to expand...
Click to collapse
Flash it like you did with semaphore .tar,there's good chances your device will just boot fine as if nothing happened.
Such boot loops are a long unexplained story but if you want to use semaphore try 2.6.6 version if it matches your rom,I was having many cwmless bootloops like you had and it didn't happened anymore since this version.
Ahh thanks for the info
I just got impatient and reinstalled everything from the ground up so everything's okay now and I have semaphore 2.9.x on slim (4.2.2)
Hi all
I reflashed an old i9000 with CM10.1 for my wife recently, and everything seemed to be working fine. Then it started behaving a bit funny and this week it started rebooting at random. I thought "no worries, I'll just do a fresh flash with stock GB".
However, before I could even give that a go the phone started acting even weirder. As soon as I put the battery in it powers on (without me even pushing the button) but it resets every time it hits the Samsung splash screen. Earlier today I could get it to go into CWM recovery and after clearing cache I actually got it to boot up. But by the time I had downloaded the stock GB files the phone was just constantly resetting at the Samsung logo and now I can't even get it to load CWM recovery using the 3-button method.
I can get it to enter Download mode, and it shows up in Odin just fine. But within 5 seconds it resets itself again so I can't actually perform a flash.
Any suggestions? Or is the phone just plain busted?
mrfurion said:
Hi all
I reflashed an old i9000 with CM10.1 for my wife recently, and everything seemed to be working fine. Then it started behaving a bit funny and this week it started rebooting at random. I thought "no worries, I'll just do a fresh flash with stock GB".
However, before I could even give that a go the phone started acting even weirder. As soon as I put the battery in it powers on (without me even pushing the button) but it resets every time it hits the Samsung splash screen. Earlier today I could get it to go into CWM recovery and after clearing cache I actually got it to boot up. But by the time I had downloaded the stock GB files the phone was just constantly resetting at the Samsung logo and now I can't even get it to load CWM recovery using the 3-button method.
I can get it to enter Download mode, and it shows up in Odin just fine. But within 5 seconds it resets itself again so I can't actually perform a flash.
Any suggestions? Or is the phone just plain busted?
Click to expand...
Click to collapse
I'm just going to answer my own question as I've solved the problem but it may benefit someone else to know how.
It got to the point where the phone wasn't even booting to the Samsung splash screen, but I could still get Download mode to show up for 5 seconds (not long enough to flash). Then in a moment of desperation I got the original Samsung microUSB cable and plugged that in, and booted into Download mode again. This time Download mode stuck! And I was able to flash a clean GB ROM which is now working fine.
So the take-out from my experience is this: sometimes you really do have to use the original Samsung USB cable.
Weird.
Thanks for reporting howto ...:good: good to know
mrfurion said:
I'm just going to answer my own question as I've solved the problem but it may benefit someone else to know how.
It got to the point where the phone wasn't even booting to the Samsung splash screen, but I could still get Download mode to show up for 5 seconds (not long enough to flash). Then in a moment of desperation I got the original Samsung microUSB cable and plugged that in, and booted into Download mode again. This time Download mode stuck! And I was able to flash a clean GB ROM which is now working fine.
So the take-out from my experience is this: sometimes you really do have to use the original Samsung USB cable.
Weird.
Click to expand...
Click to collapse
mrfurion said:
I'm just going to answer my own question as I've solved the problem but it may benefit someone else to know how.
It got to the point where the phone wasn't even booting to the Samsung splash screen, but I could still get Download mode to show up for 5 seconds (not long enough to flash). Then in a moment of desperation I got the original Samsung microUSB cable and plugged that in, and booted into Download mode again. This time Download mode stuck! And I was able to flash a clean GB ROM which is now working fine.
So the take-out from my experience is this: sometimes you really do have to use the original Samsung USB cable.
Weird.
Click to expand...
Click to collapse
I have a similar issue where I'm trying to flash my stock ROM on my Epic4gTouch. When it opens up the download mode error I start to flash and all seems to work before it reboots. Every 5 seconds. I tried the original cable and it did not help. Any ideas??
NerdsBestAdvice said:
I have a similar issue where I'm trying to flash my stock ROM on my Epic4gTouch. When it opens up the download mode error I start to flash and all seems to work before it reboots. Every 5 seconds. I tried the original cable and it did not help. Any ideas??
Click to expand...
Click to collapse
put the cable and press button power the phone go mode charging at this time make the phone in download mode
its ok for me:good:
So I recently rooted and installed twrp recovery with cyanogenmods most recent nightly. It was running smooth as butter for about a week. The battery ran dead the other night so I hooked it up to a charger and it only charged enough to show the root boot and battery symbol. Then nothing it just won't charge.
Funny thing is, when I plug it in regularly I get nothing, but if I leave it plugged in, take the battery out then back in, I get the battery charge logo for a few seconds then again nothing.
Anything I can do to remedy, troubleshooting steps before I insure it?
Kernel and battery probably have nothing to do with it.
Did you install A kernel other than Cyanogenmods' built in kernel?
Anyways, to "unbrick":
Can you put the phone in to Recovery (hold all three "home, power, volume up", and let go when you see "recovery booting" in blue text. I'm assuming you have A custom recovery installed since you have cyanogemod on it.
You can work with it from there. Wipe Cache/dalvik or wipe data/factory reset to see if it comes back to life.
See if it goes in to recovery like that, than it can be saved.
There's also odin which will bring it back to stock like when you first got it. Using A Windows PC.
Odin stock/unroot tutorial: http://galaxynote4root.com/galaxy-note-4-root/how-to-unroot-galaxy-note-4-with-stock-firmware/
You will want A newer odin than whats in the tutorial:http://cdn.droidviews.com/wp-content/uploads/2015/03/Odin3_v3.10.7.zip
and the latest firmware that's not in the tutorial (download the first link, "full rom")
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
If you have troubles with this let me know.
I had an LG with the same issue of only showing the battery symbol, then shutting off. It's dead to this day.
Yeah I have team win recovery. I tried a few times getting it into recovery but didn't have luck.
I have only had my used Note 4 a week, but just wanted to say maybe your battery is going bad. I remember reading about some people having problems like lockups and not booting, only to discover the battery was causing it. One guy posted a youtube video about it
https://www.youtube.com/watch?v=-Q-4pYUxOsc
.
my galaxy note 4 (sm-n910t) caught in bootloop . i dont know what caused it. the phone simply restarts upto first bootscreen, ie upto 'samsung galaxy note 4' and then vibrates and then restarts.this process continues upto battery is down or i pull out battery.the phone is not entering to recovery mode but enters to download mode.
i have tried installing stock rom from sammobiles but it won't help.i have also installed custom recovery twrp but that also won't help to enter to recovery mode,
i am trapped pls help..
You didn't mention how you tried to install the stock ROM . Did you use Odin?
I just fixed mine with the same issue. I was able to boot into recovery and download mode but mostly download mode without bootloop when I had the usb cable plugged in. I used ADB when I could to boot into download mode, but the buttons worked too. Trying to restart the phone only lopped after the Google screen.
I followed several guides here to flash stock with Odin and wipe cache etc but none solved my boot loop issue. almost gave up but there is a video on You Tube that said the battery warping in the cause of the boot loop. The battery, after/during quick charge, may heat up and change shape causing the issue. Today I installed my new battery purchased on amazon and no more issues.
Now I am on stock and have to find a good rom.
If you do decide to flash back to stock there are a lot of good guides. You may find yourself stuck on the T-mobile screen for 15 minutes when booting for the first time but that is ok. If you still boot loop after installing stock and wiping cache I would try the battery.
Nabeel mhd said:
my galaxy note 4 (sm-n910t) caught in bootloop . i dont know what caused it. the phone simply restarts upto first bootscreen, ie upto 'samsung galaxy note 4' and then vibrates and then restarts.this process continues upto battery is down or i pull out battery.the phone is not entering to recovery mode but enters to download mode.
i have tried installing stock rom from sammobiles but it won't help.i have also installed custom recovery twrp but that also won't help to enter to recovery mode,
i am trapped pls help..
Click to expand...
Click to collapse
hi OP,
did you find any solution to your problem?
Hello all. I'm also pasting this in the T-mobile thread in case it can be of benefit to someone. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk
chrismcnally123 said:
I just fixed mine with the same issue. I was able to boot into recovery and download mode but mostly download mode without bootloop when I had the usb cable plugged in. I used ADB when I could to boot into download mode, but the buttons worked too. Trying to restart the phone only lopped after the Google screen.
I followed several guides here to flash stock with Odin and wipe cache etc but none solved my boot loop issue. almost gave up but there is a video on You Tube that said the battery warping in the cause of the boot loop. The battery, after/during quick charge, may heat up and change shape causing the issue. Today I installed my new battery purchased on amazon and no more issues.
Now I am on stock and have to find a good rom.
If you do decide to flash back to stock there are a lot of good guides. You may find yourself stuck on the T-mobile screen for 15 minutes when booting for the first time but that is ok. If you still boot loop after installing stock and wiping cache I would try the battery.
Click to expand...
Click to collapse
Thanks sir! I have the same issue! it's working now after replace the battery
Today I left my phone in a cab and got it back in the evening. But after I got my phone it was stuck in a boot loop (after force restart - power button press and hold - it will go to battery icon and automatically restart after a few minutes and again goes to battery icon). Please see the video to understand the boot loop. Unfortunately, Developer options of the phone were not enabled.
Can boot to recovery but can boot to fastboot.
Can you please help me to boot my phone back to normal or sideload a ROM via adb.
tia
Was able to fix the issue. Followed below steps,
1. Kept phone until the battery fully drains
2. Plugged into the charger and charged the phone up to around 65% while the phone is switched off.
3. Switched on the phone when the cable is disconnected.
4. This time the phone was booted to recovery. No battery logo anymore
5. From recovery, rebooted the phone. But again it was booted to recovery.
6. Wiped all data and rebooted.
7. Phone was booted to MIUI os but had to set up the phone again from the beginning.
jayanath said:
Today I left my phone in a cab and got it back in the evening. But after I got my phone it was stuck in a boot loop (after force restart - power button press and hold - it will go to battery icon and automatically restart after a few minutes and again goes to battery icon). Please see the video to understand the boot loop. Unfortunately, Developer options of the phone were not enabled.
Can boot to recovery but can boot to fastboot.
Can you please help me to boot my phone back to normal or sideload a ROM via adb.
tia
Click to expand...
Click to collapse
Same problem bro, did u resolve it???
I think your battery is empty. Leave it on power for a while and check if its charging. Maybe the charginglevel is too low for booting up.
opg2000 said:
I think your battery is empty. Leave it on power for a while and check if its charging. Maybe the charginglevel is too low for booting up.
Click to expand...
Click to collapse
I hope it was that simple ..it seems probably like a bad update. My gfs phone did the similar today
The digitizer stopped working, I force reset the phone and boom ..recovery mode - Trying everything but it doesn't work. Wipe surely would work but she has pictures and videos so I'm trying to avoid that. Plug it to charging but she remembers it had like 75% of battery ...geez (hoping for a miracle)
EDIT: Probably this happen from the bad xiaomi update, anyway I did wipe the data and as expected it work without an issue, I'll unlock this phone and ditch MIUI (I mean I did it to my phone Xiaomi Mi Mix 2S from day 1 - I hate miui) ..now my gf has a reason to hate it too
A factory reset could be painful, since you would lose everything on the device. I saw a guy tap all over the back of the phone with two fingers, and boom! The Redmi Note 10 Pro boot normally! I tried it on a friend's phone, and it worked.
Hello,I had a kind of a similar thing.
I left my phone to charge and when I was back it seems to be stuck in a boot loop(MIUI14)
Well,I tried to force restart but the same.
Before I go to recovery mode,accidently,I putted the phone in fastboot mode.I restarted it in the try to go to recovery mode but the phone started normally.After boot,it's shows an update compete message,so te problem was from an android security path update whatever.
AlexfxDru said:
Hello,I had a kind of a similar thing.
I left my phone to charge and when I was back it seems to be stuck in a boot loop(MIUI14)
Well,I tried to force restart but the same.
Before I go to recovery mode,accidently,I putted the phone in fastboot mode.I restarted it in the try to go to recovery mode but the phone started normally.After boot,it's shows an update compete message,so te problem was from an android security path update whatever.
Click to expand...
Click to collapse
I have important apps on the phone and I wasnt thinking about a factory reset anyway but hopefully it worked in that way