So i have a Verizon S7 Edge, I switch providers to Cricket (AT&T) and was having issues with signal, read somewhere flashing the AT&T version of firmware to it would help, It did, So i went ahead and rooted it aswell.
Was working fine for a week, until now... I was trying to open Authy to login to Github and it kept crashing, after the 4th try i restarted my phone (i have done this before) Now everytime it gets to the end of the AT&T boot screen it just freezes, I have tried restarting it and running is 'safe mode' still does the same.
I am charging it right now and i am going to "TRY" a factory reset.
Anyone have any ideas why this happend? Its really annoying because now i have to wait to recover my Authy.
Phone runs Android 6, never got the update so i may try flashing that if i get my phone working again...
Related
Hi,
I appear to have gotten my phone into a bootloop. Nothing I did should have caused this. It was working perfectly when I went to sleep last night and when I woke up the battery was really hot and it kept restarting. It boots to the lockscreen (note: not a black screen, i can see my homescreen), vibrates a couple times then restarts. I have tried safe mode which does not fix, reflashing my rom, wiping cache/dalvik, booting with simcard and sdcard out... I would love to avoid wiping data if possible (and I'm not even sure if that would help at this point). Is this a hardware issue?
I believe you did all you can possibily do. the last choice is to Odin back to stock. you will have to either stick with the bootloop or lose your data but save your phone. by the way, no one can really help you unless you tell us your phone's firmware version and you have to tell us whether your phone is canadian or ATT or whatever...
Verizon Note 3 here, I received the Lollipop ota today and thought no harm in taking it as I was already stuck without root on 4.4.4.
It worked ok for the first couple minutes, then a reboot, then same thing, about 5 minutes and a reboot. Sometimes ~2 minutes, seems using it in any situation made the reboots happen. I did a factory reset thinking that would clear things up. Unfortunately now it is even worse, as it's rebooting anywhere from the first touch to the screen, to about 15 seconds of activity, literally dozens of reboots.
I downloaded the update on my pc and installed via Odin hoping that the ota was just corrupted or some bad luck like that. Nothing changed at all.
It will idle after booting just fine, I just can't do much of anything, every touch of the screen feels like a roll of the dice. Every few reboots or so I can make it to settings maybe but haven't been able to actually change much of anything, not that it would seem to matter here.
I've flashed via Odin twice, cleared the cashe many times, factory reset 3 or 4 times. Am I screwed here? What else to try?
*UPDATE* I flashed back to 4.4.4 with Odin and no more issues. It appears that my device alone is completely incompatible with the new firmware.
I should also note that I tried airplane mode, safe mode, and removing the sd card with no improvements.
After hours of messing with this thing and nearly giving up, not half an hour after I post here for help, I seem to have found a solution, although hopefully not a permanent one. The problem was happening when I would touch the screen, not scrolling ever, but making selections. On a whim I turned off sound and bam, no crashes.
I would still love it if someone had some insight about this problem, or better yet a solution.
I'm not sure yet if it is just the keypress sound that is killing it, or all sounds. I never did have any issues with the stock keyboard clicks now that I think of it, only the menu press sound. In any case it's not every time it made the sound, just half the time or so. Anything anybody could add to this would be appreciated.
*Edit* Not a solution, but it did help.
Well it's not as stable as I'd hoped. More like before the first factory reset now, but still not good at all. The various sounds definitely trigger crashes quickly(menu options, volume pings, mp3 songs from sd card), but regular silenced menu presses do sometimes as well still. Phone also bootloops several times often before it can get booted stable and 100% always crashes immediately if I try to unlock the screen in the first 5-10 seconds after booting up. Not sure if I'll be able to call or text as it's too late to test that atm. I'll update tomorrow, any insight appreciated.
I would say a bad download but I don't remember if ODIN checks MD5 sums (pretty sure it does). I would do a full wipe and reflash the stock image with odin
I am 100% stock not rooted never been rooted 5.0 vzw and I have had a couple of reboots. Never ever had one on this phone before. My old note 3 was rooted but I got this replacement after the root exploits had all been closed.
ehh not all have been closed
What is the root exploit for Verizon Note 3 with 5.0?
recDNA said:
What is the root exploit for Verizon Note 3 with 5.0?
Click to expand...
Click to collapse
None at the current time but CVE-2014-8609 seems like it could be some use
I spoke too soon when I said the phone was usable now. At best 5 minutes of light use as anything seems to crash it now. I did get a fresh image and used it with Odin with exactly the same result which makes me think its my phones hardware or something. Just seems crazy that it was working just fine before the update. The reason I pushed to 4.4.4 and lost root is because my phone suddenly started an issue where it would crash when making or receiving calls. It wasn't caused by any new apps or anything, just out of nowhere. I tried everything then updated as a last resort, carelessly I went to 4.4.4 instead of staying at 4.4.2 and lost chance of root, but it solved the problem I was having. I wonder if the issue is related somehow.
I was able to odin back to 4.4.4 and it's working fine so far, I assumed that you would not be able to revert back like the last ota and just tried it as a nothing to lose last effort. This is very important news to anybody that is having major issues with 5.0. Maybe, just maybe I'll try it again if they make an update patch for reported issues.
But for now, 4.4.4 it is for me.
VZW Note 3 update to Lollipop
I just finished the Lollipop update and my phone is working great for the past 30 minutes. Seems a little slower then usual but have had no issues besides my phone locking up after downloading the update, may have been due to my phone running down to 14%, but after removing the battery for 20 secs and putting it back on, phone came back on, I plugged into charger and started the update. Will post later if I have any issues.
I have been trying unsuccessfully through odin to downgrade but it keeps failing in odin, I downloaded the official firmware from sammobile.
Just curious if u r tried reinstalling newer odin? Try different USB port and cable. At this point maybe even try different pc if u have access to 1
Hello, my galaxy started to freeze and crash 2 months ago. At first i didn't mind it because it just happens once in a while. But 3 weeks ago, the freeze and crash became more frequent up to a point that even though i'm not doing anything to the phone, it just freeze then restarts. I researched the web and found some solutions, first i've tried to reset to factory settings. i used the wipe data/factory reset in recovery mode. it said the reset is successful then i've restarted the phone and i just loops on the samsung black screen or just crashes during the welcome screen. Then i tried to reinstall the firmware using odin. first i used the 4.4.4 tar (from this forum), the odin said the flash is okay, but when the phone starts up, it just loops on the samsung black screen or just crashes during the welcome screen. so i tried using the downgrade to 4.4.2 tar (from this forum), after successfully flashing it, my phone started to boot. but after i completed the first time process and i'm updating/downloading apps, it started to freeze and crash again, this became a frequent thing again. it just freeze and crashes anytime. i've tried reflashing the 4.4.2 again using a different cord and port, but the same thing still happens. Do you guys know if there is still some way to solve this?
Note: I've got this phone from my father when i visited him in the USA (last June 2015), then when i went home (in the Philippines), i didn't unlock the phone so i it didn't have any sim card since then. is this a factor in the phone's behavior?
Thank you
Up.. hopes someone can help me with this
Update: I've tried using another battery and the situation is still the same.
Hey, I just woke up, and I have to get to work, but I just wanted to let people know that I charged my phone last night and this morning it was dead. Pulled it off wireless charger and plugged into OEM charger and attempted to boot phone, got stuck at AT&T logo. Restarted into recovery and it tried to install an update!!! My phone is rooted, debloated, and should have been OTA blocked!!! Still having access to ADB on boot logo, I pulled my text messages (still had root?) and went for a factory reset. This restored functionality. As far as I can tell, its still debloated?!? Assuming Samsung or AT&T tried to screw the customization...
Has this happened to anyone else? I really haven't done anything weird minus root and eng boot fixes...! Waiting on Google Play app restoration so I can poke around and gather more details... but device build is still PE1 and I am still on eng boot.
I have a similar issue. My phone was on this morning, but I started getting lots of force closes from random applications. Tried to make a call and it closed phone, then I hear someone through the speaker. Kept force closing but a call was stuck open. I couldn't end it without restarting the phone. On reboot I'm stuck at the ATT logo and phone is hot as hell right now. Going to shut down until I have time to deal with it, as I'm at work right now.
I'm on lunch, whatever happened it forced me to factory reset, unfortunately I didn't back up my device storage, and only pulled mmssms.db so restoring my messages is even a pain right now. Was forced to rerun root.bat. doesn't look like it changed my stock rom any, but a major pain in the ass. Lost my flashfire backup and everything else I didn't bother to sync to my PC. Anyone else have any insight or issues?
madsc13n41s4 said:
I'm on lunch, whatever happened it forced me to factory reset, unfortunately I didn't back up my device storage, and only pulled mmssms.db so restoring my messages is even a pain right now. Was forced to rerun root.bat. doesn't look like it changed my stock rom any, but a major pain in the ass. Lost my flashfire backup and everything else I didn't bother to sync to my PC. Anyone else have any insight or issues?
Click to expand...
Click to collapse
Once you rooted did you use titanium and freeze the AT&T updates. Also being as flash fire isn't a custom recovery (meaning you have to boot your phone up to use it) if never leave my backup on the phone, at least move it to your external SD.
Yes, and I have learned. I didn't previously have an SD card for this phone
This is a pretty weird one, so I'm gonna cut to the chase...
Several weeks ago I got my a new phone (Galaxy s7 Edge, AT&T, Qualcomm) and everything was fine. I'd never rooted a phone before and wanted to try it out, even though the Edge was still pretty new. After about 2-3 weeks of owning my phone, I followed a guide to root. The root only worked after a factory reset, so I lost my apps and pictures, but it wasn't a big deal because it was just a couple weeks' worth of stuff. Everything works fine for a month or so, and then most of the apps started crashing. Some, like Google Chrome or Spotify would work, but most didn't. All the services on my phone also stopped. I figured it was a problem with the root and said oh well and factory reset my phone. I set it up normally again and all was well. But then things got weird.
Now, after about 1 week, my phone will do the same thing as when rooted. First Snapchat stops working, followed by a multitude of other apps. Google Play store stops opening, I'm unable to install apps, and several core features of the phone just freeze up. If i try rebooting (how I discovered the issue), my phone gets stuck in a bootloop and I have to factory reset to work again. My phone did this again today after a few times so finally I'm coming here for help. I also recently discovered that factory resetting my phone from the settings app did nothing, as soon as I rebooted it went into a bootloop. So the only way to recover my phone is to factory reset from the recovery mode. It may also be worth noting that I used ODIN to flash the AP, BL, CP, and CSC stock firmware (G935AUCU1APB5 etc...) after I wanted to unroot. I have absolutely no clue what's wrong and any fixes or even an explanation would be greatly appreciated.
go into recovery and try cleaning the caches, there maybe stray bits of old code floating around.
Cosmic Blue said:
go into recovery and try cleaning the caches, there maybe stray bits of old code floating around.
Click to expand...
Click to collapse
Yeah I've done that a couple times. I went ahead and did it just now though so we'll see