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
It sounds melodramatic but maybe someone else has encountered the same problem and can help.
I got my phone last week and used it for a couple hours before I decided to root and flash a custom ROM onto the phone. I didn't realize that the kernel had dmverity and proceeded to try and root my phone like any other phone.
I followed the usual steps in installing root for the first time. I used Odin to flash twrp onto the phone and proceeded to restart into recovery. I had forgotten to copy supersu to my phone before I restarted it and this is where my problems began. I swiped on the twrp page where it warns of dmverity but because I didn't transfer supersu I had to restart the phone and get it on. The problem being the phone was now stuck in a bootloop and I somehow managed to get supersu onto the memory and flashed it. I was able to boot into the rom but it was extremely unstable. I could work for maybe 5 minutes before the phone froze, got very hot, then shut down. It would go into a bootloop and succeed maybe 1/20 times, all the while the phone got very hot. I flashed a custom rom onto it and it kind of worked but would still freeze and restart every once in a while. I found the stock bootloader, rom, cp, csc, and flashed those. My phone is now stock everything but the crashes still occur frequently (basically every time I try to use it) and I'm at a total loss as to what to do.
I've rooted all of my phones since I got my S3 several years ago and I've never had a problem like this. Anyone know how I can fix this? My phone is model G935w8 so I know it has the exynos processor and rooting is possible, but I must've done something horribly wrong for it to be like this. Any help is appreciated.
Ever since I got this phone, There has always been this error "SIM card not detected" and it's extremely annoying to deal with as you have to restart the phone every time until it works (It took me 8 restarts to fix it today)
It's definitely not a hardware issue as my phone is brand new and so is my brother's phone (Tried both slots as well) and the sim card isn't even a year old
I've seen some people with the same issue. How in the world can this be fixed? I really don't want to return the phone as I like it very much
I'm rooted right now with stock rom but this has also occurred the first day (Totally stock)
This is happening to me as well and it's infuriating to say the least. I don't recall seeing the issue stock, it only seems to happen once I load magisk but I haven't fully tested that.
The issue is also usually preceeded by a reboot that gets stuck in the android one screen, meaning that I have to reboot the phone 3 times before it actually works. VERY annoying.
I think I'll re-flash the phone using the script that keeps my data and will run it stock for a few days to see if there's any difference.
Same here. I didn't experience a similar issue on 16.4 but there are other issues there. Hopefully when stable comes out, it'll work correctly.
I ran the phone re-flashed to stock yesterday and didn't run into the issue. The flashing process re-locks the bootloader so I think it's either:
1- Some issue with having an unlocked bootloader
2- Magisk 16.0 bug
3- Magisk 16.0 bug while bootloader is unlocked (I don't know if magisk can be installed but the bootloader re-locked after installing)
I had exactly the same issue on an Asus Zenfone 2. I was wondering if it was a sim card problem.
hacktek said:
I ran the phone re-flashed to stock yesterday and didn't run into the issue. The flashing process re-locks the bootloader so I think it's either:
1- Some issue with having an unlocked bootloader
2- Magisk 16.0 bug
3- Magisk 16.0 bug while bootloader is unlocked (I don't know if magisk can be installed but the bootloader re-locked after installing)
Click to expand...
Click to collapse
I did find the cause and how to fix it
The cause is the stock rom itself, It has issues regarding baseband but it doesn't happen to everyone and I don't know why
The only fix that I've found is to flash a custom rom.
I've been using aex rom for 2 weeks now and I haven't got a single issue so far
Hey guys. So I just installed the latest pie update today. The phone rebooted normally, though a while late, I noticed my sd card was not detected so I rebooted it again only this time, it refused to even turn on no matter what I did. It isn't rooted or anything.
Anyone faced this problem too?
So tl;dr version - i was using my tablet, saw an update to magisk, installed it, now it boots to black screen while running sambones rom
[SM-P580] [BQK1] SaMBoNeS
TWRP 3.2.3.0 --> 3.3.1.0
longer story:
i was trying to get a game to run, it wasnt...and realized it has been a while for a restart, so i checked to see if anything needs to be updated and saw magisk needed an update. i didnt note what version it was before but it was a version or two earlier than what it was trying to install.
rebooted to blackscreen no samsung logo
have tried restarting a dozen times, booted to TWRP, tried to force normal system boot through the UI, nothing.
I tried installing a new kernal [SiriKernel], it made it to the samsung logo, waited 15 - 20 minutes and it never made it past. restored a backup using TWRP
updated TWRP to 3.3.1.0, still no luck.
i had this problem a long time ago, and cannot figure out how i fixed it....it may have fixed itself but it isnt this time. any advice would be appreciated. I am trying to avoid wiping and starting again if at all possible because the problem seems familiar. also trying to stick to a rom for use with adaptive storage. if i do have to wipe if that can be done on a newer stock OS that's fine as well but last time i messed with this tablet it wasnt