OEM_NV_Backup BT_MAC_MISSING notification after every reboot - OnePlus 2 Q&A, Help & Troubleshooting

We been having this issue with our Malaysian OPT with OOS 2.1.0 and later OOS 2.1.1.
Every time it reboots, the error message OEM_NV_Backup BT_MAC_MISSING will pops up. It can be swipe off. No other error on the phone, everything else works fine. Not a big issue but just annoying.
This happens on both stock recovery, stock kernel, locked bootloader and unlock bootloader with AK Kernel, TWRP recovery.
Btw, the Bluetooth works in case you're wondering if BT_MAC_MISSING notification screws up the BT. And we have try factory resets and clean install.
Anyone has any ideas on this. Thanks.

Related

Help! My Back capacitive key stopped working.

Hi All,
I have a N900W8 and was in the middle of testing the new stock rom (N900W8VLU2DOC4 from Sam mobile) I flashed via Odin, and some sort of new user guide pop-up hit the screen. I must have touched elsewhere on the screen or hit the back button (or something, I can't quite remember what happened), dismissing the pop up, and suddenly my back key stopped working. The menu key still works, and lights up both keys when pressed, and nothing else is wrong.
Since this happened, I have completely wiped the phone (advanced wipe via TWRP, and then formatted the internal storage), and re flashed the stock rom. I refuse to believe this is just a coincidence, since it could have happened at any point other than when I was flashing roms, and I'd like to think this isn't just random bad luck.
For those interested, here is the complete sequence of events:
1. Was running the Tweaked Kitkat rom, and decided it was time to update.
2. Downloaded the above mentioned stock firmware
3. Flashed firmware via odin
4. Loaded TWRP 2.8.7.0
5. Factory wiped the phone
6. Flashed Aryamod via TWRP. Chose the wrong kernel, as per Arya's OP (was supposed to pick stock, but opted for the custom kernel that I later found out isn't the best one for my model of note), but everything seemed to work fine.
7. Used the phone for most of today, but had crappy service. Looked into my baseband version, and noticed I was still running the Kitkat bootloader and modem for some reason. I guess the new ones didn't stick when I flashed the new stock rom.
8. Hastily flashed the stock rom again via Odin, but forgot to factory wipe
9. Got "Unfortunately, the process.android.process.acore has stopped" every 10 seconds or so. Looked up that I forgot to factory reset.
10. Flashed TWRP again
11. Factory wiped the phone again
12. Went through the setup process
13. A few minutes after setup was complete, that random popup showed up and the back button stopped working.
Any thoughts or suggestions? For the moment, I can map the menu key to act as a back button, but that's significantly less than ideal. Any and all help is GREATLY appreciated. Hopefully this is just my screw up (and it's fixable) rather than my back key dying. I guess I'll mention that it's kept in an otter box defender case, and isn't usually dropped, hence thinking it's software related.
Thanks in advance everyone!
try stock using odin

Nexus 4 CM13 Boot Stall

I'm running CM13 20160204 with 20160204 Gapps and latest Xposed on my Nexus 4, although I've been having this problem with the nightlies for a few weeks. My storage is encrypted (has to be for work).
After doing a clean install, everything is fine for a few days. Eventually, the phone will randomly reboot. It reaches the PIN entry screen, and I'm able to enter the PIN with no problem. HOwever, it proceeds to the flash screen and just stays there. The flash animation continues, but it never proceeds further.
I'm able to access /data through TWRP without problem. I've tried wiping system, cache and dalvik and reinstalling with no success. I really don't like having to factory reset every week.
Does anyone have any ideas?
farside268 said:
I'm running CM13 20160204 with 20160204 Gapps and latest Xposed on my Nexus 4, although I've been having this problem with the nightlies for a few weeks. My storage is encrypted (has to be for work).
After doing a clean install, everything is fine for a few days. Eventually, the phone will randomly reboot. It reaches the PIN entry screen, and I'm able to enter the PIN with no problem. HOwever, it proceeds to the flash screen and just stays there. The flash animation continues, but it never proceeds further.
I'm able to access /data through TWRP without problem. I've tried wiping system, cache and dalvik and reinstalling with no success. I really don't like having to factory reset every week.
Does anyone have any ideas?
Click to expand...
Click to collapse
If anyone is following, I went without Xposed this week and had the same problem.

Help - G935A stuck on AT&T Logo - 3 vibrtations

For a week my G935A worked fine... direct out of the box I flashed ENG Kernel and Rooted, then installed apps and configured - no issues.
Today it was working then it hung on wake.. I tried to reboot and now it gets stuck at the AT&T logo and vibrates 3 times - over and over
I can get to Odin and Recovery screens easily so I tried to flash the ENG Kernel again & deleting Cache Partition few times - didnt fix it.
Also tried booting into Safe Mode - it never gets there, stays at AT&T logo.
When I go into the Recovery menu, I see at the bottom, in red... "dm-verity verification failed"
Anyone know how I can recover from this without Factory Reset? It took 6 hours to reinstall and config all my apps - really want to avoid that.
thx for the help!
as far as I know there is no way to fix and save your stuff. I had the same problem with G930A and even doing a factory reset would only allow my phone to boot but then I get apps crashing and then a reboot puts you back at ATT logo and the vibrates. Best to ditch the whole engboot and go back to stock until a more stable rooting method comes out.
Some searches shows posts that say using Odin to flash HOME_CSC without having to wipe and everything survive
... Where can I get HOME_CSC? I dl'd stock rom and dont see it in there.
thx!
Same here this morning on my 930A w/ PK1....went to watch a youtube vid and everything google related began crashing.
Only been on engboot for a couple days but did flash the v15 debloat last night. hmmmm.
Any luck with the files or procedure LivinOne?
Update: Flashed the PK1 CSC and got into recovery.
Wiped cache and reboot, same failure mode....sad face.
Flashed CSC again, into recovery, factory reset, wiped cache.
Back to setting my "new" device up.
Dec 30 update: Same crash, SEMI same problem.
I get the single vibration followed by the 3 vibrations after I put my pin in from a restart.
Same symptoms prior, all background activities began crashing.
Running all PK1 files from QRhinehardt post.
Any thoughts?
I ended up wiping and flashing the T-Mobile firmware and using the ENG bootloader (but not rooted yet). It is WAY faster than the AT&T was. I've only had issues with Wifi Calling (it doesnt seem to work most of the time)
s7 at&t
Hi, did you first flash with eng bootloader and then tmobile rom? I miss this step...I appreciate your help please
Single vibration followed by the 3 vibrations
Hi, were you able to fix the problem? I'm also getting the single vibration followed by the 3 vibrations.
Do you know why is this occurring? I performed a wipe cache and factory reset but still nothing.
bweegn said:
Same here this morning on my 930A w/ PK1....went to watch a youtube vid and everything google related began crashing.
Only been on engboot for a couple days but did flash the v15 debloat last night. hmmmm.
Any luck with the files or procedure LivinOne?
Update: Flashed the PK1 CSC and got into recovery.
Wiped cache and reboot, same failure mode....sad face.
Flashed CSC again, into recovery, factory reset, wiped cache.
Back to setting my "new" device up.
Dec 30 update: Same crash, SEMI same problem.
I get the single vibration followed by the 3 vibrations after I put my pin in from a restart.
Same symptoms prior, all background activities began crashing.
Running all PK1 files from QRhinehardt post.
Any thoughts?
Click to expand...
Click to collapse

I337 extreme lag, random reboots, no recovery

Recently bought a new out-of-the box Galaxy S4 I337 from Amazon. Had i known how much trouble it would give me, i would have picked something else. When i first turned the device on, it was almost totally unusable due to lag and random reboots. Software version was 4.4.2. I used Odin to flash a rootable NB1 onto the device. Still had lag and random reboots. Upgraded to lollipop using this guide: https://forum.xda-developers.com/galaxy-s4-att/help/guide-att-samsung-galaxy-s4-sgh-i337-t3383078 and still have lag and random reboots. Also, the first time i upgraded to lollipop, i installed safestrap not knowing it wouldn't work on lollipop. Obviously, my recovery disappeared. When i figured out what was going on, i did a fresh install of lollipop. I got recovery back, but today when i tried to boot into recovery to wipe the cache, i discovered it had mysteriously stopped working again. If i attempt to boot into recovery, it just skips to the Samsung logo. I didn't install safestrap or any other custom recovery this time.
When i turn the phone on, either it hangs at the AT&T white splash logo and refuses to load at all, or advances to the lock screen. I have disabled animations and every widget i could on the lock screen and yet when i attempt to unlock the phone, it usually freezes. If i repeatedly swipe the phone for thirty seconds or so, it unlocks but it is still frozen and i have to continue swiping to prevent it from locking again. Eventually i'm able to navigate the phone normally, until it randomly reboots or freezes. Sometimes i see an error message that Touchwiz home, Process System, or SystemUI has stopped working or is not responding. This is always accompanied by a freeze. Also, choosing an option in the dialogue that comes up when i press the power button (shut down, reboot, etc) invariably causes the device to soft reboot. Other times a soft reboot happens totally at random, even if i'm not doing anything. Anybody have any idea what's going on or did Amazon just sell me a dud? All of these issues have been happening since before i rooted the device or upgraded it, except for the disappearing recovery mode.
Thanks in advance for your help.
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
StoneyJSG said:
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
Click to expand...
Click to collapse
Just wanted to bump this to thank you for your reply. Never got the phone to work but i was able to get it back to stock and return it. I got a refurbished S5 instead.

Messed my phone up after installing custom kernel

Hello everyone,
I flashed the latest franco kernel on my op3t but the phone became very slow, so I reverted back to the stock kernel, but the problem still present. for example, when I open YouTube app, it shows a static reload arrow and it takes 4-5 seconds to load videos, same with app downloads from the store, it shows the same reload arrow for a couple of seconds before it gives me the option to download the app or cancel, also Lastpass lags for 4-5 seconds after login.
Another thing that got messed up is the reboot/shutdown animation, instead of the spinning circle animation, I get a static flickering one.
I flashed the stock kernel again, flashed the os, did a factor reset, a complete wipe but still have the same problem
any ideas ?.
Start over again. Wipe everything via TWRP. And I really mean EVERY partition via advanced wipe option. Connect your phone to your PC and upload a full stock ROM. Reboot once again from TWRP into your recovery. Let your phone boot and see, if your problem is fixed.
Are you sure you're flashing the right packages for OP3T and not the OP3?
Sent from my ONEPLUS A3000 using Tapatalk
Solved the issue by downgrading to MM and then flashing 4.1.6 again. Thank you

Categories

Resources