Last week on Thursday, I allowed Verizon to install their Software Update 21 (April 2020.) It made it as far as the going through the optimizing apps and then was stuck in a boot loop. The phone would be usable for about a minute, then would freeze, and then reboot. If I clicked on the System Update option in settings, it would say that a system update was in progress. I chatted with Verizon, and they ended up telling me that the only way to stop the update was to do a factory reset, which I am doing everything I can not to do that as I don't want to lose my data.
I changed it into maximum power mode and it did stop the update for that time being and I was able to use the phone, texting, etc. This allowed me to at least connect the phone to my computer to backup all of the directories. After many reboots, on Friday it finally stopped doing the update and gave me an error which I think was 410. It thought it was updated, though did show as failed. When checking for updates, it said it was the current version. Twice I was able to get the phone to stop by freezing when going to the app and stopping some programs (sadly, I was not able to remember the exact combination that worked) which allowed me to use the phone like normal. All this while, I was uninstalling a large amount of the apps that I had installed hoping that would minimize whatever may have been causing the problem.
Went to each of the google and samsung apps, stopped, disable, and reverted them all back to factory defaults. Guess that was a bad idea, from then on I received an error as soon as the phone started which caused it to go directly into recovery mode. I chatted with samsung and they thought it might be a hardware issue. I still think it is related to their software update, so not a hardware issue.
By using Odin, I loaded the firmware from March 2020, and when it rebooted, it did go as far as optimizing the apps, though anytime it booted up, it would never get past the white verizon loading screen. It took me hours before I discovered that Odin was failing to load the firmware on the phone as the Windows 10 laptop only had USB 3.0 ports which don't always work with Odin, and ended up being successful using my old Windows XP laptop as the USB 2.0 ports worked fine. After a bit hanging on the verizon loading screen, it would reboot and never went past. I have been able to load the March and April 2020, though none of them will ever get past that white verizon loading screen. I did see something say that in loading TWRP, I could possibly do a full backup of the phone which is what I would like to do.
One time I only loaded the AB file for a different version than I had loaded, and it was the first time it went beyond the white screen, only to tell me that the verification failed and it would need for me to do a factory reset. I was able to reboot the phone without actually doing the reset.
I have read many posts here and the forums on androidcentral, and with so many things, I really needed to post to get guidance from people here that can point me in the right direction for any other things that I can try. As you have read, doing everything that I can to get the phone working by keeping my data. Any help would really be appreciated.
Related
I'm hoping someone on here can help me. I've had a few lingering issues that I can't seem to resolve. I run AOKP, but at this point, I may go completely back to stock to see if the issues resolve.
- The main issue is the random freezes on boot. It is really random, but definitely has gotten worse over the past few months. Basically, the phone freezes at the first boot screen about 60-75% of the times I reboot. I've had to pull the battery sometimes once (if I'm lucky), and sometimes 3-4x, just to get it to boot past the Samsung screen. This is compounded by the second issue I'm having:
- Loss of data. Actually, more specifically, it is data not coming back when I leave a no-signal area. I live in a no-signal area and depend on a VZW home tower. I don't get a solid signal until about 2 miles out from my house, just after I leave the neighborhood. After I clear the area, I get a strong cell signal, but data never becomes available. Toggling mobile data or cycling airplane mode does not resolve it. I have to reboot, which can bring me to the stuck boot screen, where I'm pulling my battery to get back up and running (often when I'm driving... which really sucks).
This weekend, I wiped the phone as fully as I could. I don't believe I restored it completely to stock, as the phone still showed the unlocked icon when booting. I did, however, restore the phone to the stock MDK ROM, re-rooted, reinstalled TWRP (through GooManager), and reinstall the 11/14 AOKP ROM. It did not seem to help.
Shortly after wiping the phone, I was 99% sure I had figured out the boot issue. For some reason, I got the idea to pop out my sdcard while it was stuck at the boot screen. As soon as I popped the card out, it moved past the Samsung screen and changed to the Google "X". The card was a SanDisk Ultra 32GB, which some people have had dismounting issues with, so I thought I hit the jackpot. I tested it several times, and as soon as I popped the card out, it would start booting each time.
I was excited when I hit the road this morning. Unfortunately, the data bugged hit me as soon as I got out of the neighborhood. As before, I had to reboot to get it back. That is when it stuck on boot again. I did not have an sdcard in, though. It took for cycles of pulling the battery before I finally booted up.
I'm stuck. I really don't know what else to do. I've tried every ROM/radio/kernel combination out there, except for bone stock. I used a combination of different guides to get as close to stock as I could, but I still didn't get there. I'm sure I missed something, but I'm not sure what. The steps I took to restore are below.
Is there a PIT file I can use to repartition the phone? I know that is frowned upon unless the phone is completely bricked, but I don't know what else to try. Just from experience, I'd doubt it's a hardware issue... but who knows:
Steps I took to "restore" phone:
- Flashed SCH-I545_MDK_562219_Stock_Restore.tar.md5 in Odin
- Rebooted, then went back to Odin to install MD2 kernel
- Booted into stock ROM, enabled dev options, USB debugging, etc...
- Rooted, rebooted, installed GooManager
- Installed TWRP through GooManager
- Installed 11/14 AOKP, gapps, faux 0123m, and MJ7 radio
I have a sprint note 4. I don't have it activated currently and use it as a tablet of sorts. Recently it's been giving me problems and I've wanted to break it. I got it about 2 years ago, and since then I rooted it, then installed twrp recovery, then flashed custom software. The software I used was called Dr.Ketans I believe, it combined the note 5 and s6 edge plus softwares. It started to crash occasionally so I installed cyanogenmod onto it. It worked for a bit, but now when Turing the device on, it takes like 10-15 minutes to boot up. And it only stays on for 5 minutes before it crashes and freezes. When it does that, the only way I can boot it up again is take the batter out and put it back in a few times because sometimes I get an error message. The error message barely happens but it says something along the line of "cant boot up". If I use twrp, my phone doesn't freeze. I've tried reinstalling the software, I've tried formatting the entire phone and refreshing. Nothing seems to work. I've even tried changing my kernel but I'm not entirely sure what it is, and how it affects the phone. I'm not the smartest with phones, but I'm good with following directions and googling. If anybody can help me I'd greatly appreciate it cause I've been dealing with this issue for 3 months.
Reinstall the original firmware and make sure it doesn't freeze / crash with it and then you can reinstall the custom software. Make sure that you have the required recovery, bootloader, and baseband version to run the newer custom roms. The requirements should be located in the OP.
I appreciate the response. I will try this as soon as possible. Should i use odin to flash or would it be possible to use twrp recovery? Also, what do you mean when you say the requirements are in the OP?
You should use Odin to recover to make sure you have a fresh start.
The requirements of the rom you pick afterwards should be in the OP.
I got my hands on a Galaxy Grand 2 sm-g7105. Performed a factory reset from device and the system worked nicely enough. A particular third party app I wanted to use wouldn't load so I kept tweaking.
I rooted and set up a CWM recovery with Odin, then considered going with Resurrection Remix. I made a backup with CWM, wiped the device and set it up. It looked great but 'audioFX.apk' or something along those lines kept crashing every 30 seconds or so. It didn't cause me any problem besides the annoying crash notification, so i figured I could just remove the apk and be done with it. To my dismay, then the notification then piled up non-stop and the system become unusable.
I went and restored the backup on CWM. Then I'd get error notifications for this and that stopping working (basically the apps present on the backup that weren't on the stock rom), so I figured the backup was useless. Another mistake, I guess.
Performed another wipe, deleted the backup for space. Tried removing every piece of bloatware I could find before unrooting (I wanted to do that). Finally everything seemed to roll... except I deleted some important apk, SecDownloadManager I've come to believe, and at that point the Play Store couldn't update a thing, it got stuck on 'Downloading'.
So I did another wipe, just to find out that didn't restore the missing apks. Got my hands on a stock rom for my model (a different build than my origibal one, but to hell with it... right?). I got that working work Odin, but to my surprise that didn't seem to completely restore the apk mess, and I got a ton of crash apl notifications and even after logging on Google the play store didn't let me in to try and see if apps could update.
Finally, I found what is supposed to be the device's original rom. Odin'd it all the way. Everything seems to be where it belongs, but I cannot really check 'cause... NOW THE ****ING WI-FI WON'T TURN ON. It's not like it doesn't connect to my network, it just won't activate. I press the switch, or goes back off.
I tried rebooting, taking out the battery for some seconds, performing a factory reset from within the system, wiping from CWM, dialing *#0011# to access service mode and deactivating power-saving mode. Nothing works.
HELP, please.
I'd be happy if the WiFi just worked, but knowing why the hell a stock rom should give any headache or what I'm doing wrong for it to go so wrong might be a step towards the solution.
PS: I'm writing this as I recall, so the details might not be completely spot-on, but the broader problems were those.
My phone (Nexus 4) appears to be soft-bricked, and will not boot up. When I turn on the device, it appears to get part way through the boot process but it never completes, and the bootsplash just keeps spinning forever. The top of the phone where the radios/gps/etc are gets very hot during this time.
I've tried: clearing caches within TWRP, factory reset, loading a couple new ROMs, wiping all partitions and reformatting, updating TWRP. Nothing seems to help.
I'm starting to think it's a hardware problem, but I'm hoping that someone might be able to give me some ideas that I haven't tried yet. I can get into TWRP and can load ROMs.
Some background: My phone is a Nexus 4 (mako) and had Cyanogenmod 13.1 prior to the issues, which has been running fine since last year. Recently my phone was acting glitchy/slow, so I decided to clear the cache and dalvik cache a couple weeks ago. This worked great and got things working well again. When I set things up again I also decided to start using DroidWall, which was the only app on my phone using root. About a week ago I also replaced the battery inside the phone since my old battery was shot and could barely keep a charge. The new battery has been working well, and does not appear to be the part of the phone heating up when the phone is stuck booting.
An update. I found that with the Slim ROM loaded, I can run `adb logcat` while the phone is booting to see what's happening. Lineage OS does not seem to ever get far enough to be seen by adb.
When viewing the Slim logcat, there are a lot of logs generated. Within, there are some DEBUG and backtraces displayed. And, I think the phone may be stuck trying the same thing over and over again as I've seen a section appear about the camera several times.
Earlier today I opened up my phone again, and noticed some pressure contacts on the back cover of the case. I cleaned them all to make sure they were making good contact, but it hasn't helped.
Hi all,
Last night my phone started to randomly reboot itself, even in Safe Mode! It's now to the point where I can't even login -- I enter my pin, the 'Phone is starting' overlay shows for a while, and then it suddenly reboots. I haven't installed a new app for at least 2 weeks at this point, and the reboot was happening before I updated my apps. After updating, things seemed to get worse maybe?
Is there any way I can salvage my phone or do I have to hard factory reset via hardware buttons?
Its called bootloop. you need to flash your phone to fix this problem and flashing can fix all the software issues of your device.
I was afraid of that... Just a bit worrying that it happened randomly when running stock.
Ok, thanks!
I had same issue when ran android 9 in 2019, however, I fix this issue by doing a clean flash. Yes, you will lose everything, so make sure you do a backup via google.
Tom_usborne said:
Its called bootloop. you need to flash your phone to fix this problem and flashing can fix all the software issues of your device.
Click to expand...
Click to collapse
If you didn't add an app or update that caused it either the boot load got corrupted or it's a hardware issue. The flash memory should not spontaneously get corrupted unless it's defective ie a hardware issue. However anything is possible... quantum physics.
More than likely it was a poorly written app or update that caused it. 3rd party launchers and power management apps are prime suspects. It may take a week or more to manifest its self as a boot loop. Any signs of system lagging or instability should be taken seriously as they are the only warnings you may get before a boot loop*.
A virus or rootkit** is another prime candidate.
Do a factory reset now. Be wary of which apps you load and avoid any updates until the system is know to be stable. Then add apps and updates one at a time. Updates many times aren't really needed.
Over a year ago I had 2 back to back boot loops on my Note 10+... yes, and 2 factory resets and full reloads.
The prime suspects were as I mentioned above. Neither one was reloaded after the 3red factory reset. A year latter that 3rd reload is still running fast and stable. Fun times
**if your Android version is 9 or above a factory reset will purge any virus or rootkit as long as you don't inadvertently reintroduce it. Be careful what apps you load and what you download.
If the Android version is 8 or below, they are suspectable to a nasty rootkit that requires a firmware reflash to purge. Pie and above are not.
1. For me, it was also itself rebooting, only while phone were in pocket / case. So do not use any of them (searched on reddit forum, was exactly same topic)
2. Maybe sim ejection tool is not correct be inside, don't often open and close it