Well first things first, I was running a stock Tom lollipop 5.0.1 have a custom twrp 2.8.2 I believe, still have it been having it for a while tried 3.0.2 no difference so I switched back anyways I tried flashing stock rom all of them from T-Mobile starting with the original KitKat rom, I tried the stock 5.1.1 T-Mobile Canadian rom and it worked but it rebooted about every 3 minutes , so after trying many Roms also deleted everything off the phone first through teamwin recovery, I finally got a semi stable Tom which is resurrection remix I have 5.7.0 but had 5.6.9 anyways now it works almost perfect reboots maybe 3 times a day and thats with heavy use, by the way the annoying thing is when it attempts to reboot it gets stuck in the Samsung logo, I remove the battery and reinsert it and it boots like a champ, also if reboot trough os same thing happens, sometimes it won't turn on or take a charge unless I leaves the battery removed for a few minutes about 5. It's gets very annoying have tried so many things nothing seems to fix it and I have 3 batteries so if can't be that and original charger could it be a bad power supply ? I will upload pics in a sec one battery is worse than the other two holds no charge,. Stock rom would get stuck in the T-Mobile logo.
http://i296.photobucket.com/albums/...ds/Screenshot_20160704-231050_zpseseysxpj.png
http://i296.photobucket.com/albums/...ds/Screenshot_20160630-152248_zpsx5s1ybst.png
Well for anyone that has tried everything on their note 4 and ir gets stuck in a bootloop but it does power on and reboots very often, i replaced the battery didnt work so i replaced the power switch and that did the trick, no more reboot or bootloop or the phone not wanting to charge
Related
Apologies for opening a new thread for this. I am unable to reply on the dev thread as I have less than 10 posts. So in reference to the following post, I'd like to contribute some experience I had in the last two weeks.
http://forum.xda-developers.com/showthread.php?t=1627689
Across the space of two weeks, I have had a chance to note this symptom on three devices.
Device 1 SGS i9000
Rooted phone and have been on CM9 for as long as I can remember. Wake up one morning to find phone with BLN on, but no ability to wake the phone (power button, home button, volume buttons, nothing works). Popped the battery out, and the bootloop / no recovery went on forever. Had to Odin flash back to Stock 2.3.6 to start again. Since then, any CM9 (nightlies or RC2) attempted always end up in the bootloop, i.e. stock > flash rom, first boot = bootloop. I figured then if I had to go back to 2.3.6, I'd rather go to JB. First JB tried was HellyBean, and the same thing happened. It was only trying pawitp's current alpha CM10 that it worked. Days later reverted back to ICS (Paranoid Android v1.6) due to lags and bugginess.
Important to note, the CWM kernel I have gone through are 6.0.0.3, 6.0.0.8, 6.0.1.0. And Paranoid Android put me back to 5.5.0.4.
Device 2 SGSi9000
Rooted phone and have been on CM9 for as long as I can remember. Phone cut off and rebooted in the middle of a phone call and ended up in bootloop with no recovery. Exactly the same symptom attempting to get the phone back into any of the CM9 roms (nightlies or RC2). Ended putting the phone on Paranoid Android as well.
Device 3 HTC Sensation
Had a lot of trouble trying to flash CM9 on this using CWM. Random bootloop with no recoveries. CWM at that time was 6.0.0.8, which I had lots of trouble flashing Gapps on. More on this device posted here: http://forum.xda-developers.com/showthread.php?t=1786703
And finally, one other observations across all these devices. Somehow with CWM v6.x.x.x I had rather poor battery life. For instance, on CM9 Nightly 07/23, say I started with 100% charge in the morning at 8am, by 12pm, I would be looking at 80% left. Once a week, I will let the phone shut itself down on low power, and charge without switching the phone on. On any other evenings, I would plug the phone and leave it charging overnight, e.g. at 10pm with only 30% left. I have constantly noticed that within a few minutes, it jumps back to 40%, which is rather odd. A 10% charging achieved within minutes is rather unusual.
I have also noted that, when the SGS i9000s ended in the bootloop / no recovery situation, the phone can never be charged. Plugging the phone for charging will the a blank battery icon lit up, with the swirly thing on top of the icon appeared frozen and it stays that way.
Being on lower version of CWM, in this instance, v5.5.0.4., I can observe the units (observed being the keyword here) charges "normally", i.e. no funny 10% charge achieve within minutes. Also, battery life are much better as well, i.e. only 10% drain between 8am (100%) to 12pm (90%).
So, not being a developer but someone that likes to tinker and observed:
- Is it possible that newer version of CWM potentially have some impact to battery life?
- Is it possible that how CM9 is being flashed onto a phone has potential issue? I find it a bit disturbing on an initial flash from stock to CM9, I had to pop the battery out after the flash initially loads a new CWM onto the phone. Then start the flash again with the newly loaded CWM.
I am hoping all these I have experienced in a short amount of time can be helpful to potentially looking into where issue might be. Most people have one phone and tested across different kernels and ROMs. I had the luxury of testing across three devices on a narrower choices of kernels and ROMs.
For the first SGS paragraph I can relate. EVERY ROM would boot loop. I had to flash to stock With repartition ticked. And then flashed semaphore kernel, and formatted system, data and cache. Then I flashed to whatever ROM and was okay.
Also I seem to have the problem with having to pull the battery after a flash to the new recovery. Only happened a few times, but non the less, still happened. Just make sure you flash twice afterward to make sure
Sent from my GT-I9000 using xda premium
AlwaysDroid said:
For the first SGS paragraph I can relate. EVERY ROM would boot loop. I had to flash to stock With repartition ticked. And then flashed semaphore kernel, and formatted system, data and cache. Then I flashed to whatever ROM and was okay.
Also I seem to have the problem with having to pull the battery after a flash to the new recovery. Only happened a few times, but non the less, still happened. Just make sure you flash twice afterward to make sure
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Yup, on every occasion I mentioned above, wipe (system/data/cache) are part of the ritual. Just didn't mention them.
I just think the battery-pulling feels rather odd. Can understand why it's needed, but just feel odd. Wondered if it'd be better to keep kernel and ROM separate, e.g. flash new kernel via Odin, then simply do ROM. This might be a 'cleaner' method perhaps? It feels almost like flashing kernel as part of the process is like modifying Windows files whilst still in Windows, then do a reboot.
For now I have fear against v6.x.x.x kernels. But will likely go back to it once CM10 is stable. We'll see.
I installed Eryigit's Android 2.3.6 ROM onto my SGP 5 and have this battery charging boot loop. Are there any solutions for this yet?
I've flashed CM 9.1 rom 2 weeks ago. Everything was perfect (well, ok camera app was a bit laggy). I installed it through CWM, like wiki says.
2 days ago, I was using phone as Navigation, and battery depleted to 0 (phone switched off). When I plugged it into a charger, battery charging animation was displayed, then phone switched off and so on (loop). Same situation is when I power on. CM logo endless loop.
Recovery doesn't start, download mode is working tho.
I checked different battery, same thing.
Is it software related problem ? Should I just flash phone again via ODIN or Heimdall?
I had something similar like this a few months ago because my nephew was pressing random buttons. I did indeed just reflash the phone again. Lucky for me I had a backup of my data so that fixed most of my problems.
Hope you figure it out,
Currently, I've flashed hardcore Kernel (CM wiki page) to flash CM9.1 rom.... it gives me Status 7 error (get.prop("ro.product.device")). Same with CM 10 Nightly.
Flashing Slim ICS gives me Status 0 error.
What should I do?
Hey just flash stock GB firmware via Odin then u r good to go...
Do post results
If my post helped, don't mind hitting THANKS
Yes it helped. Thanks.
Strange tho, stock 2.3.6 feels faster than CM9.1
Dear all,
I have a Samsung Galaxy Tab S2 8.0 WIFI purchased last year (exactly to the day) in Cali. I believe it came with 5.1.1 XAR version.
A month later, my troubles began. I flashed with 6.0 Samsung WIFI ROM from some other country and the tab soon started to randomly turn off while being used. I am not sure if this is coincidental or not. When restarted, it would sometime fully boot, only to turn off while doing any mundane task surfing etc. and at other times, start and turn off as soon as the SAMSUNG logo comes. Weirdly, when I wait a day or two, it would start fully and work for a few minutes to half an hour
When I put it to charge, only rarely does the green battery logo came up, but most frequently I got a flashing thunderbolt sign.
I sent it to Samsung and it came back apparently with the correct firmware installed and the repair note said, faulty data cable replaced. But in a week of usage, the same problems started. I don't live in the US currently and so I don't have local warranty and don't have any means to send it back to Samsung USA. I've tried all remedies I could find, charging it to 100%, holding volume down and power for 15-30 seconds to simulate a battery reset, etc. to no avail. These days. it wouldn't even stay on long enough to access recovery mode, before turning off.
Yesterday, I installed Nougat 7.0 ROM from XAR on it and tried to start it. same problem. It says updating applications xx out of 26, and then turn off. When I try to access recovery, I got the android logo and when it gets to "Erasing", it would turn off. Then now that the warranty has expired, I installed TWRP (twrp_3.1.0-1_sm-t710_13317.tar) and this time I somehow goto to TWRP recovery mode, I just left it on there to see how long it would last, instead of immediately erasing the caches and restarting.
After that once, I couldn't get it to stay on long enough to access recovery. So I tried to go back to OEM ROM using Smart Switch, but to no avail once again. The Download mode still says Custom even after Smart Switch emergency recovery
I have tried flashing various other things (5.1.1 Samsung ROM, 6.0 ROM from UK with AP, BL and CSC files, TWRP 5.1.1 permissive ROM, TWRP), in various jumbled orde,r out of frustration. Nothing worked. here's a list of ROMs I've tried:
T710XXU2DQCL_T710UVS2DQC1_EON
SM-T710_1_20170406180713_vd28gnex7t_fac
SM-T710_1_20170330211239_qkurg70e9y
5.1.1_T710XXU1BOH7_T710XAR1BOH7_XAR
twrp_2.8.7.1_LL_5.1.1_t710
twrp_3.1.0-1_sm-t710_13317
t710_5.1.1_boot
Right now, the only thing I can access is Download mode and it says Current Binary: Custom, System Status: Custom, AP SWREV B:2 K:0 S:0 and worse than before, the tab turns off at the Powered by Android logo and when I plug it in, it doesn't charge but I get this boot loop (with the just the powered by android screen flashing)
would it help to re-partition and nand erase all and install a fresh ROM with a PIT file, if so can someone please share me their PIT file for this model??
I am out of ideas, and ready to break this expensive brick
appreciate any help,
thanks
V
vvsarana said:
Dear all,
I have a Samsung Galaxy Tab S2 8.0 WIFI purchased last year (exactly to the day) in Cali. I believe it came with 5.1.1 XAR version.
A month later, my troubles began. I flashed with 6.0 Samsung WIFI ROM from some other country and the tab soon started to randomly turn off while being used. I am not sure if this is coincidental or not. When restarted, it would sometime fully boot, only to turn off while doing any mundane task surfing etc. and at other times, start and turn off as soon as the SAMSUNG logo comes. Weirdly, when I wait a day or two, it would start fully and work for a few minutes to half an hour
When I put it to charge, only rarely does the green battery logo came up, but most frequently I got a flashing thunderbolt sign.
I sent it to Samsung and it came back apparently with the correct firmware installed and the repair note said, faulty data cable replaced. But in a week of usage, the same problems started. I don't live in the US currently and so I don't have local warranty and don't have any means to send it back to Samsung USA. I've tried all remedies I could find, charging it to 100%, holding volume down and power for 15-30 seconds to simulate a battery reset, etc. to no avail. These days. it wouldn't even stay on long enough to access recovery mode, before turning off.
Yesterday, I installed Nougat 7.0 ROM from XAR on it and tried to start it. same problem. It says updating applications xx out of 26, and then turn off. When I try to access recovery, I got the android logo and when it gets to "Erasing", it would turn off. Then now that the warranty has expired, I installed TWRP (twrp_3.1.0-1_sm-t710_13317.tar) and this time I somehow goto to TWRP recovery mode, I just left it on there to see how long it would last, instead of immediately erasing the caches and restarting.
After that once, I couldn't get it to stay on long enough to access recovery. So I tried to go back to OEM ROM using Smart Switch, but to no avail once again. The Download mode still says Custom even after Smart Switch emergency recovery
I have tried flashing various other things (5.1.1 Samsung ROM, 6.0 ROM from UK with AP, BL and CSC files, TWRP 5.1.1 permissive ROM, TWRP), in various jumbled orde,r out of frustration. Nothing worked. here's a list of ROMs I've tried:
T710XXU2DQCL_T710UVS2DQC1_EON
SM-T710_1_20170406180713_vd28gnex7t_fac
SM-T710_1_20170330211239_qkurg70e9y
5.1.1_T710XXU1BOH7_T710XAR1BOH7_XAR
twrp_2.8.7.1_LL_5.1.1_t710
twrp_3.1.0-1_sm-t710_13317
t710_5.1.1_boot
Right now, the only thing I can access is Download mode and it says Current Binary: Custom, System Status: Custom, AP SWREV B:2 K:0 S:0 and worse than before, the tab turns off at the Powered by Android logo and when I plug it in, it doesn't charge but I get this boot loop (with the just the powered by android screen flashing)
would it help to re-partition and nand erase all and install a fresh ROM with a PIT file, if so can someone please share me their PIT file for this model??
I am out of ideas, and ready to break this expensive brick
appreciate any help,
thanks
V
Click to expand...
Click to collapse
Well i hve the same problem like you.. idk wht should i do with this condition.. bootloop.. always restart until logo.. :crying:
Please anyone help to solve our problem..
Your issue seems related to power. It seems your device doesn't charge correctly and is turning off due to running out of battery.
What does TWRP report as the charge state?
Do you get the same issue when the device is plugged in to the mains?
ashyx said:
Your issue seems related to power. It seems your device doesn't charge correctly and is turning off due to running out of battery.
What does TWRP report as the charge state?
Do you get the same issue when the device is plugged in to the mains?
Click to expand...
Click to collapse
hi ashyx, I am pretty sure that battery isn't the issue here. even though the grey battery logo with a thunderbolt flashes while turned off and plugged in for charging, after a while it does charge anyhow. I can get it to 100%. Plugging in makes no difference.
I am thinking it could be a power button problem or a faulty usb port perhaps, if it is indeed a hardware fault?
vvsarana said:
hi ashyx, I am pretty sure that battery isn't the issue here. even though the grey battery logo with a thunderbolt flashes while turned off and plugged in for charging, after a while it does charge anyhow. I can get it to 100%. Plugging in makes no difference.
I am thinking it could be a power button problem or a faulty usb port perhaps, if it is indeed a hardware fault?
Click to expand...
Click to collapse
Did you ever resolved this issue? Curious if you have a solution.
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
So recently i bought note 5 N920T T-mobile variant and after few days i encounter a weird problem that i can't figure out what exactly is going on.
Once a sudden my phone freeze and touch screen stop responding then phone goes black screen and a strong white led light turn on while screen is black.
Then after pressing 3button together volume down+home+power the phone reboot normally
Then after few seconds again and again same thing happens.
I was on stock rooted 6.0.1 marshmallow rom with arter kernel permissive since i bought this device.
Things i tried
Factory reset from twrp (didn't change a thing)
I flashed stock rom marshmallow and nougat both via odin (got worse now more freezing and rebooting can't even complete setup )
Again tried flashing 4 files recovery firmware BL+AP+CP+CSC via odin this time with PIT FILE re-partition checked in odin. everything Pass smoothly without errors in odin but again freezing black screen on setup. (same issue)
Tried factory reset+wipe cache after flashing (still same)
At last i tried flashing custom rom "kongloi s8 port final repacked" from twrp after clean wipe it worked finally now no reboots or blackscreen freezing nothing everything works perfect for 2 days.
Then i thought now my phone is fixed so why not try stock again.then again same problem came back.
1 thing i realize that when i run custom kernel specifically a permissive kernel my phone runs without issues.
currently stuck with khongloi rom s8 port this is the only rom working on.my device and cant go back to marshmallow.
I am looking on Google and xda constantly from many days but can't find correct answer.
So please please someone point me out what is this issue
Sorry for the long post TIA