Hello, I have been having issues with my SGH-M919 doing a bootloop recently. Since 2014 I have been running CyanogenMod. Overtime it has been working flawlessly. Ocassionally I would make a backup, then proceed to flash the latest nightly rom. Going from CM11, CM12, then CM12.1. Over the past month, or month and a half, I have been experiencing radio issues. The modem would fail to have a decent signal, or I would get no data, and wifi, and/or airplane mode would fail to enable or disable until reboot. Recently, I had notice a conenction issue just a few days ago, and after reboots the radio would fail to initialize. I recieved a call, and it rebooted. So fed up with radio issues I suspected a bad rom configuration. When I rebooted after backing up and flashing the CM12/1 05.14.2015 build, I got nothing but a bootloop. I tried restoring the backup but had the same result. I tried installing a previous rom build with same results. Cleared dalvid cache, and still got the same result. I ended up completely wiping the phone, all options under the wipe options under PhilZ Touch recovery. Upon reboot I was stuck in download mode. Eventually getting odin to repartition without a pit file, it failed using the only available stock rom I had available, odin failed and kies wouldnt cooperate AT ALL. I eventually found a PhilZ mirror cause the site keeps returning "invalidcust" on downloading. So I flashed the recovery and sideloaded the latest rom and got it to boot. After rebooting to install gapps, it worked, then afer setting up google play store, I had noticed I was not getting any data, and upon reboot, bootloop came back. The actual point of reboot/crash varies. Sometimes is hangs a few seconds at the samsung logo, then not even a few seconds after the bootanimation starts... it reboots. and at other times it stays around 8-10 seconds before a reboot. I suspect, faulty hardware, or I need to flash the stock rom to get the hardware to refresh properly.
Any help would be greatly appreciated.
Update:
Upon booting with USB cable connected to a power source, it boots properly. A few moments after unplugging, it reboots, then bootloops. So...Bad battery? Even though it shows it as being at like 70/80 %?
Sounds like a bum battery... Had a similar issue with a S2.
Sent from my SM-T320 using XDA Premium HD app
You need to odin full stock firmware NK2.
Then evaluate battery.
Pp.
Related
Hi...I've searched everywhere and I haven't seen anything close to my issue. But if there is and I missed it I apologize in advance and I appreciate any help/advice.
Well I rooted my phone from 4.3 with no issues. I used safe root so it wouldnt trip knox. I flashed sokp's 4.4.2 ROM with the proper gapps and agni kernel. My issue started after I tried updating my camera with photosphere 4.3. I went to use the 3d feature and it shut my phone off and started to loop. Also flashed the camera fix zip but that didn't help either. I got into recovery using cwm and wiped everything from the cache to data, almost to the point of no service. So i flashed beanstalk 4.3 rom hoping it would solve problem but it didn't. I even did a factory reset (didnt work) and found a rooted stock ROM I flashed thru Odin then back to beanstalk, all to no avail. Now I have to keep my phone plugged into a power source in order for my phone load past "sgn2" screen. And if I unplug it then it resets phone and loops. I also noticed that with beanstalk I have no kernel(well it reads unavailable). I was thinking that maybe after the camera failed that some data or something maybe corrupted. Is there a way to wipe everything to the beginning, like fresh from at&t, so It will stop looping and I don't have to keep my phone plugged into the wall?
Also with mean bean I can uplug my phone for a few min before it resets but if I try to open any apps it resets. It seems as though my phone isn't getting enough power.
Again all help is greatly appreciated
I have been an XDA lurker for years and have never had a need to post since everyone on here is so great about solving issues as they emerge. Anyway I have searched high and low for any answers to my problem with no success. My phone was rooted running a kit kat rom (Dirty Unicorns) when this issue occurred. A couple days ago I sent a mms and noticed my data was off so I turned it on via the power menu and my phone rebooted. Now this is something I have encountered with certain custom roms so I thought nothing of it. The phone went through the reboot process but then it rebooted again after about 3 minutes of normal operation. Since then the time to reboot has gotten worse until now it wont go past the Samsung boot screen. I have tried nandroid restores, cache/data wipes, and finally pushing stock roms via ODIN. None of these change the reboot behavior. Finally, as if everything else wasn't enough, I can no longer flash roms via any custom recovery. This to was something that also degraded over time. At first I was able to flash .zip files for the first few hours but eventually that to would also send my phone into a bootloop. I am clueless what to try next. Any help would be greatly appreciated. Thanks.
I'm not sure how else to describe these two problems I have.
Just for reference, I am using Cyanide L RC 7.1 from here: http://forum.xda-developers.com/galaxy-s3-att/development/rom-cyanide-l-v1-android-5-0-2-t2980174,
and I am using TWRP 2.8.5.0 for d2att. I have a i747M on Rogers.
Problem #1: boot loop only when plugged into AC charging
In the past week, I found that my phone gets stuck in a boot loop only when the phone is plugged into the AC charger. It will boot up, show the Samsung logo, then the Cyanogenmod logo with Cid, then show the Cyanide L boot animation. Once the animation is over, the phone just reboots. This happens endlessly (I didn't let it go on for more than 20 minutes, I didn't have time to wait). However, if I let the phone boot while it's not plugged in, then it boots up just fine. It also boots up just fine if I am plugged in via USB as a data connection to a computer. This only happens when I am plugged in via AC.
I have tried different combinations of USB cable and USB AC adapters. Doesn't seem to make a difference. I thought maybe it's a battery thing and borrowed a colleague's battery (also i747M), no dice.
Thoughts on what's causing it to boot loop like this?
Problem #2: Cannot wipe Data in TWRP
I discovered this problem when I was trying to update to the latest version of Cyanide L RC 8. I booted into recovery (TWRP 2.8.5.0) and proceeded to dirty flash the ROM. First boot had terrible com.android.phone FCs every 5 seconds. So I booted back into recovery a couple more times to reflash, same problem. I decided to do a clean flash and do a factory wipe. That's when the problem began. Once it reads "wiping Data without erasing /data/media" (or words to that effect) TWRP would freeze (the animated progress bar at hte bottom stops moving) and the phone would just reboot. The phone then gets stuck in an endless boot loop. I tried this numerous times, same problem. Couldn't restore a NANdroid either because it wipes Data before restoring.
I had to boot up into Download mode to use Odin to flash a custom ROM back and work my way back to a NANdroid I had. Took me the better part of 2 days without a working phone to get back to my latest NANdroid backup.
Any ideas what causes this freeze + crash in TWRP? I have reflashed TWRP, but I'm too afraid to test it out, only to lose another 2 days like that.
Thanks
Maybe you'll have better luck with Philz Touch recovery for the d2lte?
No luck with Philz Touch recovery. Tried that one, and also the latest TWRP. Seems to be the exact same behaviour with trying to wipe the Data partition.
I'm currently half way through using Odin to flash a stock TW 4.3 ROM to the phone. Hoping that this might solve my problems - perhaps something went awry during a recent ROM flashing, and I'm hoping that using Odin to nuke and pave my phone will fix it.
Fingers crossed...
daver68 said:
No luck with Philz Touch recovery. Tried that one, and also the latest TWRP. Seems to be the exact same behaviour with trying to wipe the Data partition.
I'm currently half way through using Odin to flash a stock TW 4.3 ROM to the phone. Hoping that this might solve my problems - perhaps something went awry during a recent ROM flashing, and I'm hoping that using Odin to nuke and pave my phone will fix it.
Fingers crossed...
Click to expand...
Click to collapse
If Odin doesn't get it try a wipe in the stock Samsung recovery.
What bootloader is on your phone? Hopefully, it is 4.3 or newer and you are using the stock ROM from sammobile.com.
audit13 said:
What bootloader is on your phone? Hopefully, it is 4.3 or newer and you are using the stock ROM from sammobile.com.
Click to expand...
Click to collapse
I'm on NF2, so definitely not an issue with the bootloops and bricking that might happen by being on 4.2 or earlier.
Flashing with Odin worked perfectly, and yes I used a ROM from sammobile.com. After that, I flashed SuperSU and TWRP 2.8.6.0 through Odin as well, before downloading another ROM to test wiping, flashing, more wiping, and more flashing. So far no crashes in TWRP when wiping data.
I haven't been able to re-produce the boot loop when plugged into AC, it's only been a day, but we'll see if that rears its head again.
Well, it was a good 2 weeks, but now I'm back to having the same issues. This time I'm on a different ROM, but the two issues are the same.
I'm currently on S3Rx, 4.4 Touchwiz.
If plugged into AC (wall adapter), I get bootloops. If plugged into USB into a computer, it's fine.
Going into TWRP and doing anything with the /data partition causes the device to freeze up and then restart itself.
Is it possible that my storage hardware (the memory itself) might be failing?
daver68 said:
Well, it was a good 2 weeks, but now I'm back to having the same issues. This time I'm on a different ROM, but the two issues are the same.
I'm currently on S3Rx, 4.4 Touchwiz.
If plugged into AC (wall adapter), I get bootloops. If plugged into USB into a computer, it's fine.
Going into TWRP and doing anything with the /data partition causes the device to freeze up and then restart itself.
Is it possible that my storage hardware (the memory itself) might be failing?
Click to expand...
Click to collapse
The problem 1: you mentioned that the you are suffering with the problem of rebooting in the loop that occurs only when you use the AC wall outlet for charging. You must see in its rectifying circuitry detail. The problem may be there.
I eventually found a solution, though I don't know if it was a solution to the root problem.
My problem was that I was getting bootloops when plugged into AC charger. My solution, how ever random it seems, was simply to flash back to stock (via ODIN) to 4.4.2. Since then, my Problem 1 and Problem 2 were solved. This completely wiped everything on my phone (luckily I did a complete backup to my computer), but it also solved both of my problems.
It seemed the problem #1 was not caused by a bad charger or cable, as one might have thought.
So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
ride1226 said:
So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
Click to expand...
Click to collapse
You really have to investigate by adb. Look into the dmesg output and logcat as well. Maybe your sdcard is corrupt or 100 other issues are possible as well. What device do you own? H811? unlocked?
.
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
kunate said:
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
Click to expand...
Click to collapse
There are several users reporting that the latest cm version bootloop the best option is to start in download mode and Flash with LGUP Stock ROM.
You could also try to boot into Download Mode and then flash the latest twrp and then Boot into Factory Reset Mode again
After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
AussieMouse said:
After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
Click to expand...
Click to collapse
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
It worked! Thank you so very much!
And I'm not a huge fan of updating my Android devices due to past experiences, but if this happens again, I might just update it to Marshmallow.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
@ashyx
i love you man...this worked for me too...thank you...now i need to reinstall TWRP again and see what's cooking......
I had this problem recently too, with the added complexity that the "Factory Reset" option in recovery wasn't working -- it would say something like "MDM does not allow factory reset" and then just reboot.
Fixed it by directly flashing TWRP with heimdall, then booting into the new TWRP recovery, performing a factory reset, and then rebooting the OS. This time it got pass the bootloop.
i flashed new twrp for T700 it's bootloop cannot enter the twrp menu keep bootlooping ...what's the solution for this?please help
Help ME!
What are "stock firmware" and "MM"? and where to get it?
I've replaced the power button thinking it was a hardware issue but now I'm not sure. I've also installed a few different stock roms but still have the same problem. Does anyone have any insight as to what could be going wrong and what I can try to get it fixed? Thanks for any help you can give. The device is a Samsung SM T-800