Database Users

[Q&A] Fixes and Questions

I have created this thread to clean up the forums a bit and to fix one confusion that most people in the forums which are saying which can mislead people to think that user means that when they don't mean that.
Q: What is the different between brick and soft-brick?
A: This is the issue I was talking about above.
A soft-brick is where you cannot access the kernel or/and rom and a brick is where you cannot access the bootloader so you cannot turn on your device unless you JTag it.
Q: Since I flashed a kernel I got stuck on the splash screen (Google logo bootloader screen), I attempted to reflash but it did not help.
A: Make sure the kernel is supported by the Rom's build number and Android version, to fix this you have to flash a supported kernel, remember that not all kernels are supported.
Q: Since I upgraded to Android 4.3 via OTA I noticed a large battery drain, WHAT IS GOING ON?!?!
A: On day 1 after the upgrade Google Backup will be using your battery for restoring your data so you will have to wait until it is done BUT then it will backup your settings such has brightness and app data but you can switch off "App Data" from the sync settings to stop Google Backup.
Q: A while/day later the issue is gone but Google Services is draining my battery.
A: That is actually Google Maps doing the draining, it is using the internet to locate you, to stop the battery drain go to Settings, Location settings, and disable WiFi & Mobile network location.
Q: Titanium Backup is not restoring my backups, what can I do?
A: Flash SuperSU v1.51 via recovery, this will fix the root issues and the Titanium Backup restore issues.
Q: Root is not working on Android 4.3, I'm panicking!!!!!!!!!!!!
A: Don't worry, flash SuperSU v1.51 has mentioned above to fix root since it now uses the SU Deamon due to the new security.
Q: The stock recovery says "No command.", what can I do?
A: Either keep pressing or hold volume up and power to unlock the menu.
This does not always work for certain users so I would try volume down and power so see if that does anything.
Q: How do I disable the OTA updater?
A: You will need root and an application, thanks to @joshuab227 for the information, the following is from joshuab227's post:
Here's how to disable the auto OTA download on any ROM
Install Autorun Manager from the Play store.
Then enter its recommended advanced mode.
Go into the settings and enable the following : system entries and system app disable.
Disable com.android.gsf.update.SystemUpdateService$Reciever under Google Service Framework
Click to expand...
Click to collapse
Q: The Play Store app and web store will not recognise my device!
A: @ColdEmbrace has got this issue and found the solution so that should explain why the start of the post starts how it starts:
After trying all of the above options my device was still not showing in the store. I went to this link.
play.google.com/settings
I clicked on one of my devices and clicked the update option this loaded my Nexus 4 onto the list it is now available on the web store.
Thanks everyone for the advice and I hope this helps people who are still having issues.
Click to expand...
Click to collapse
Q: My device says that I have no internet connection with a empty signal bar with or without a sim card.
A: The user @matt0401 was one of the victims with this issue and managed to fix this issue with a interesting solution:
Wow, I'm up and running! Weird fix though...
I installed the toolkit and downloaded the ROM, and was attempting to get into fast boot manually because trying to do it during the unlocking process in the toolkit wouldn't work. I thought I remembered the buttons for getting into fast boot from my old Gnex as being "hold power and volume up at same time". I tried this, and the phone went to the white "Google" logo and then vibrated, and then screen went black and the LED notifier at the bottom of the phone glowed red for about 2 seconds. The phone then rebooted, about 10x faster than before might I add, and when I was booted up I saw "No SIM detected... emergency calls only". This would infer my SIM slot was finally being detected, whereas before even with no SIM inserted I just got "No Internet Connection".
I popped my SIM in, rebooted, and the network is connected. Time to review 5 days of missed texts. Thanks for the hand!
tl;dr --> Anybody having this problem, try turning it off, and then turning it back on with the SIM inserted, holding POWER + VOL UP til it does this hard reset type fucntion. When rebooted, the problem should be resolved.
Click to expand...
Click to collapse
Q: I have to reenter my pin code for my sim every time, what do I do?
A: @lucker#1 you guessed it has the same issue has well but he wasn't the OP of the thread that the issue was discussed in but he did sure find a fix, the following is a quote from his post:
i've also had that issue the second day after receiving the phone. I removed the sim, put it back in but that didn't help - i looked at my sim card tray and i realized that a one side of the sim card chip was close to one metal side of the tray and i figured that could be the issue - so what i did is i took a stripe of adhesive tape and made sure they wouldn't touch - I haven't had the issue again and it's been more than 2 weeks.
Click to expand...
Click to collapse
Q: Since I installed Android 4.3 a few of my apps are force closing, what should I do?
A: You have to reinstall that application to fix the issue.
Q: I am getting screen flickering.
A: Flash the correct kernel which supports your Android build and version.
Q: Got a kernel panic, HALP!!!
A: That is pretty rare for the kernel to panic but you can actually easily trigger it, to fix it you must reflash the kernel (make sure it is the correct one!).
Q: Since Android 4.3 on YouTube using Slimport there is a blue graphical glitch, why is it doing that and how to fix it?
A: Since Android 4.3 there is some major bugs, improvements and fixes and the graphical glitch (I got this myself) is due to the new Software Encoder, there is no fix yet but you can go around it by using VPlayer as it apparently supports YouTube videos and it has Hardware Encoding.
If you have any questions and answers please post them here.

Bump!, Not much people are reading this...
Sent from my Nexus 4 using xda app-developers app

Bump once again and the last time.
Sent from my Nexus 4 using Tapatalk 4

[Q] S4 i9506 solk2 port - thanks, and issues observed

Hi - I'm very new to the forum and less new to custom ROMs and software.
In the last few days I installed solk2's unofficial CyanogenMod port, 20140711 root build. Went well; overjoyed to be rid of Samsung's bloatware. Thanks!
Since then, updated to first 20140808 and now 20140813. Used CWM recovery (installed via theunlockr dot com/2013/12/09/install-custom-recovery-samsung-galaxy-s4-gt-i9506shv-e330s/) directly instead of CM Updater - updater downloads the builds but when it reboots into recovery to apply them the process there cannot find the build file to install.
I've noticed:
1) When making / receiving calls, the face sensor doesn't appear to work any more - before CM, the sensor would notice when the phone is held to my cheek and blank the display, and light it up when I move the phone away. No longer.
2) The front start button doesn't appear to wake up the device from sleep any more (maybe I've missed a setting to toggle for that?)
3) the CM updater doesn't appear to work, as mentioned above
4) CyanDelta doesn't know about this set of nightlies I think - I've tried it a couple of times and it doesn't pick up deltas
5) the power button doesn't wake the device when it has darkened due to being on a call; instead it may cause the device to flash its screen up but then immediately darken again
1 & 5 make it quite difficult to control the phone during calls. Initially I thought this might have to do with ShakeCall, but the issues persist after uninstalling that.
I've cleared my cache and dalvik cache after the most recent flash to 0813.

I should say, this is relating to http://forum.xda-developers.com/showthread.php?t=2767448 and I'd have posted there but I cannot yet.

This is still an issue for me with cm-11-20140909.
Is there anything I can do to help find and fix these items?

Is this the right place to ask, even? Does @solk2 work?

pfm102 said:
This is still an issue for me with cm-11-20140909.
Is there anything I can do to help find and fix these items?
Click to expand...
Click to collapse
Proximity sensor fixed a long ago. There something wrong in yours phone. Install this recovery. Then try clean install of latest nightly or SNAPSHOT-M10 and set update recovery in Developer settings. Recovery you have has different mount points so thats why it can't find updates.
Delta updates isn't supported though.

solk2 said:
Proximity sensor fixed a long ago. There something wrong in yours phone. Install this recovery. Then try clean install of latest nightly or SNAPSHOT-M10 and set update recovery in Developer settings. Recovery you have has different mount points so thats why it can't find updates.
Delta updates isn't supported though.
Click to expand...
Click to collapse
Thank you very much - I'm running 20140914 and the proximity sensor now works during calls.

New EU firmware! (EU1.1.124b)

So, it just popped up while my phone was idle, without anyone calling it in here first, YotaPhone finally decided to give us EU users the RU124 firmware! It looks from the changelog to be the exact EU equivalent to its RU counterpart, including YotaTravel, the return of the YotaStore and other stuff. It's been so long that I don't even remember, but I should be fine flashing this and then reflashing SuperSU and Xposed without losing anything, correct?

If you have stock recovery it will install fine. If not you should be able to grab the update zip from /cache and side load. Then reflash what you want.
Sent from my iPhone using Tapatalk

Yep I'm still on the stock recovery (I just boot TWRP every time I need it). Gotcha, then I'm just dumping my Titanium Backup folder onto my PC as a precaution, and then I'll update and report back on SU\Xposed.

Looks like whatever Yota pushed at 117MB was the wrong thing - a failed update attempt and a reboot later, it's now 0.94 GB. Seems like it's the correct size in ftp://fw.ydevices.com/YotaPhone2/Firmwares/EU/ so now it should work.

Update from RU1.1.112 to RU1.1.124 issue
https://r.tapatalk.com/shareLink?ur...share_tid=3436224&share_fid=3793&share_type=t
Sent from my iPhone using Tapatalk

Just as expected the 0.94 GB update file worked, I reflashed SuperSU and Xposed and the phone is working great on 1.124b.

What version were you coming from?
Sent from my iPhone using Tapatalk

EU1.87. I wanted to go to the RU version but never could get a KitKat RU firmware to boot on my device, so I just gave up and went back to the latest EU firmware.

Ah OK that makes sense. Glad you got it working.
Sent from my iPhone using Tapatalk

Go mine today (1.1.44HK)
Updated to EU 1.1.124b with official yotaflasher.
No Su nor any hack.
So far no bug, it's a great device.

Hi there!
I'm waiting for my yotaphone 2 from this new wave from chinese shops. I ordered the International version. Is it safe to flash the EU version firmware over the "international" version?
And please, can anyone provide an alternative downolad link for the yota flasher?
The one from offcial website:
https://yotaphone.com/us-en/ypflasher/
is a corrupted zip file.
Thanks!
Edit:
I could get it from here:
ftp://fw.ydevices.com/YotaPhone2/YotaPhoneFlasher/

Seems there's a bug.
Almost each time i try to unlock phone (with power button) from EDP the pin keyboard isn't showing up, i must tap all over the EDP screen, way it's relocking then i can have the keyboard again.

Solved by using gesture instead of pincode

satsuki_yatoshi said:
Solved by using gesture instead of pincode
Click to expand...
Click to collapse
Gutted they removed the Instagram Cover instead of fixing it!

Rarelyamson said:
Gutted they removed the Instagram Cover instead of fixing it!
Click to expand...
Click to collapse
they removed the Instagram Cover instead of fixing it!
Click to expand...
Click to collapse
Instagram restricted access to its API, so none of 3rd party apps now work properly. Thats why Instagram Cover was removed.

Hello
I deployed this great update a few days ago, and it clearly brings numerous improvements and fixes.
One visibly new bug annoys me a lot anyway, and that's why I am posting :
When I type a SMS on the EPD, lots of freezes occur. And today, I found a simple pattern. I type a word, and then I back-delete one or a few letters of it. Then I add new letters, and that frequently freezes the EPD for a long moment.
It's not 100%, lots of times it freezes under these conditions, few other times it does not.
I setup 3 languages to choose from (thanks to the update !) and the auto correction is ON.
Does someone else experience the same issue ? Any workaround or fix ?
Thanks

Appens to me 2 times, each time i needed to look/unlook the edp screen to solve

My problem is that with the latest update I need to restart my phone until it starts charging. Otherwise it will not charge ... does this happen to anybody else? Probably I should try to reset ...

no charge bug here

No charge bug here neither. Quite the opposite in fact, I would even say that autonomy obviously improved since this update.
And I confirm I have the same bug with the PIN keyboard not showing up on the EPD when using the Powa button. It happens very often after using the other screen, but unlocking by tapping twice is an easy and efficient workaround.
Surprising obvious bugs anyway, I hope the Yotagods watch us and intend to fix them.

[Rom] Mokee 7.1.2 for Lenovo Vibe Shot

https://download.mokeedev.com/?device=zoom

Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..

X10MINISTER said:
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
Click to expand...
Click to collapse
Rom works but it wasn't maintained. No new bug correction from february.

stuccamelo said:
Rom works but it wasn't maintained. No new bug correction from february.
Click to expand...
Click to collapse
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this

X10MINISTER said:
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
Click to expand...
Click to collapse
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good

stuccamelo said:
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
Click to expand...
Click to collapse
So, it mean that u also facing the hotspot problem.?

Can u change/install fonts in mokee roms? Cause I have an issue with changing font style using iFont apps..its say installed but after reboot font style doesnt change. Any solution?

linux shall eternally bloat all search engines with expired ?=
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.

Dr Tungsten said:
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Click to expand...
Click to collapse
There are a lot of recent updates for this rom. I flashed the most recent (2017-11-21 date). I didn't make a lot of testing but the problem you refered has been solved and the performance and stability seems good.
The only issue I noticed so far is that the phone does not start automatically from the shutdown state when an alarm is set.

@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..

GeorgeTsak said:
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
Click to expand...
Click to collapse
This is not my main phone right now so I spend very limited time using or testing it but you are right, I have just checked that with this ROM the device is unable to pass the SafeNet test so far. On the other hand I have not problems at all playing videos with youtube app or rooting the device. I'm using supersu v2.82 and TRWP-3.0.2-0 for lenovo 6.0 by wzsx150 (didn't try Magisk)

has anyone managed to install this ROM?
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.

mrtowel said:
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
Click to expand...
Click to collapse
I think you need a different TWRP version. Try this one:
https://drive.google.com/file/d/0B1Sms71Oe6FIQnl4STlhSk96b0E/view?usp=sharing

Help me!
I'm new to these things. Installing roms and ****s. Can someone help me with the step by step procedure of installing this room on my Lenovo vibe shot. Thanks in advance.

The same probvlem with TWRP
piccolo2k2 said:
I think you need a different TWRP version. Try this one:
Click to expand...
Click to collapse
I have exactly the same problem.
Did you resolved it? Tried also mentioned "Twrp by rahul.rar", but the same problem - unable to mount /system partition.
Thanks for reply,
st

bug fix?
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?

hhaekal said:
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
Click to expand...
Click to collapse
Im using it right now.. Im still have the problem with:
-hotspot tethering,bluetooth tethering
-usb mtp
-suddenly shutdown when on wifi
Have someone had the problem with delay in receiving whatsapp messages?

Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?

Alex_135 said:
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Click to expand...
Click to collapse
Hi,
I'm using the release and there is no bug with WIFI.

Linaxx said:
Hi,
I'm using the release and there is no bug with WIFI.
Click to expand...
Click to collapse
How about wifi tethering problem? Does it remain error when wifi tethering are enabled?

September 2019 Security update for Mi A2 is now available

69.5MB in size so no major changes are to be expected...

Downloaded it just now...no major changes...no bugs encountered...

Weird noise while switching camera modes seems to have gone

Patched boot of last update ?

parkpark9999 said:
Patched boot of last update ?
Click to expand...
Click to collapse
Stock and patched (Magisk 19.3) images of /boot partition:
Note: I recommend to
- copy stock image to /downloads,
- patch it with Magisk (thus a copy of stock image will be saved in /data for further "Uninstallation of Magisk")
- copy patched image to PC (or take the one attached)
- boot patched image via fastboot
- make "Direct installation" in Magisk
This method will enable you to "Uninstall Magisk" by <Restore partitions> command when preparing to download next OTA

Darshan28 said:
Weird noise while switching camera modes seems to have gone
Click to expand...
Click to collapse
Yes i can confirm that.
Is seems THat WI-Fi Is more stable now also.

ki69 said:
Yes i can confirm that.
Is seems THat WI-Fi Is more stable now also.
Click to expand...
Click to collapse
No, the sound is still there but a lot quieter (tested with a sound meter )

WARNING: Caused my phone to get stuck in a bootloop during update.
I'm not rooted and haven't unlocked bootloader. Trying to find a solution.
Edit: after a bunch of tries and some time charging, it finally booted and displayed a "Couldn't update" error. I'm back to august patch with a working phone. I guess I'll wait for more people to report on this update.
A question: In case my phone gets stuck in a bootloop for good when updating, should leaving the "OEM Unlocking" option enabled be enough to save it and allow me to flash a fresh iso?
I mean, only leave the option enabled, but not actually unlocking the bootloader (I don't want to reset the phone unless necessary).

Wifi has indeed improved a lot! I have now connection to the WiFi with the September update where it did not even find the network with the August update. Big improvement here! It now shows the same behaviour as an Galaxy S7, which is really good with WiFi. Major thing... Thanks Xiaomi!
Edit: it looks like this was only accidentally. On other places WiFi is still far more worse than on other devices. Where other devices find multiple WiFi networks with decent speeds, the Mi A2 find no network at all. If it finds finally one, then the speeds are dramatic. I ditch the phone and I'll go for the S10.

JassyNL said:
Wifi has indeed improved a lot! I have now connection to the WiFi with the September update where it did not even find the network with the August update. Big improvement here! It now shows the same behaviour as an Galaxy S7, which is really good with WiFi. Major thing... Thanks Xiaomi!
Click to expand...
Click to collapse
I'm not sure but seems the range became reduced. Need to test again.

WiFi speeds seem to have increased, camera noise is gone for me. So far no complaints

danannnn said:
WARNING: Caused my phone to get stuck in a bootloop during update.
I'm not rooted and haven't unlocked bootloader. Trying to find a solution....
Click to expand...
Click to collapse
Used to happen with many previous OTA updates to many people. Why should this update be fully safe? That's why experienced stock MiA2 users recommend to keep bootloader and critical unlocked.
danannnn said:
Edit: after a bunch of tries and some time charging, it finally booted and displayed a "Couldn't update" error. I'm back to august patch with a working phone.
Click to expand...
Click to collapse
Good that this method worked for you.... usually works but needs great patience and dedication.
danannnn said:
A question: In case my phone gets stuck in a bootloop for good when updating, should leaving the "OEM Unlocking" option enabled be enough to save it and allow me to flash a fresh iso?
I mean, only leave the option enabled, but not actually unlocking the bootloader (I don't want to reset the phone unless necessary).
Click to expand...
Click to collapse
Yes, enough, but please consider following:
- now with working phone you can save most of your user data to PC (and to Google), then unlock and then restore data;
- when you will be forced to unlock phone in bootloop, you won't be able to save/restore user data
- after unlocking you will have ability to make TWRP backup of your /data partition

Audio is definitely louder.

Aerobatic said:
Stock and patched (Magisk 19.3) images of /boot partition:
Note: I recommend to
- copy stock image to /downloads,
- patch it with Magisk (thus a copy of stock image will be saved in /data for further "Uninstallation of Magisk")
- copy patched image to PC (or take the one attached)
- boot patched image via fastboot
- make "Direct installation" in Magisk
This method will enable you to "Uninstall Magisk" by <Restore partitions> command when preparing to download next OTA
Click to expand...
Click to collapse
Sorry for the question, i'm on 10.0.13.0, can i boot the 10.0.14.0 patched and update, because i uninstalled magisk and all of the modules and the update fails, says it couldn't update.

Anyone thinks that the screen takes quite a while to light up after the fingerprint is recognised?

tatitar said:
Sorry for the question, i'm on 10.0.13.0, can i boot the 10.0.14.0 patched and update, because i uninstalled magisk and all of the modules and the update fails, says it couldn't update.
Click to expand...
Click to collapse
To answer your question, no, you can't update by doing that.
It is highly probable that your system partition have been remounted rw (read/write). For Android to successfully update, it is important for any of the root apps to never remount system as rw.
To check if this is the cause, check Matlog (an app for logcat) after the error when performing the update. Filter "update engine" and check a message in regards to system mounting.
If this is correct, then, to be successful in updating to the September security level, you will need to flash the August's system partition from a fastboot package, and then try the update once again
---------- Post added at 04:28 AM ---------- Previous post was at 04:23 AM ----------
LeChevalierR said:
Anyone thinks that the screen takes quite a while to light up after the fingerprint is recognised?
Click to expand...
Click to collapse
I see that this have a chance to occur when a person updates to a newer patch level. This is based on the messages i have seen in this forum board though it is unknown if it really the cause.
I read that deleting your fingerprints and add them back as new "fixes" this issue. I recommend you to try it out first

Aerobatic said:
...
Click to expand...
Click to collapse
Thanks for the all the explanations.
I guess I'll just keep "OEM Unlocking" enabled for now if its enough to save me from disaster. I don't mind losing my phone data, I consider it transient anyway. I'm just too lazy to set it all up again unless I really need to.
After making sure OEM Unlocking was enabled, that I got fastboot all set up and working, etc., I went ahead and attempted to update again, this time with no issues.

New bug encountered? I was watching a video from YouTube I opened through a WhatsApp link and all of a sudden my back button was there but home and recent apps buttons disappeared and they didn't come back until I reset my phone!

My screen makes some weird noises when it register touch, like squeking or static noise behind the screen, it is hard to explain. It start to hear when touchscreen register touch and it last about 2-3 seconds, then it stop, and when i touch it again the sound is back and so on. It's very annoying

I can do confirm that the camera sound is gone, although I can still hear it if I concentrate enough. It might be what is used to sound before so I can't really tell.
WiFi is definitely improved and it now searches for available networks faster
Overall system speed is improved specially with those awkward keyboard lags in the previous update.
Also LTE Signal got better I can tell
.
.
But I do have a little doubt about the battery life cause my phone had about 14% of charge last night which I forgot to plug in the charger and it was dead in the morning which has never happened before. It usually had at least 5% when that happened before. Still am not sure if that's the real deal so I'm gonna just wait some more to see battery performance.
But the update itself seems stable and bugless enough so it's definitely recommended to install it especially if you're dealing with camera sound...
P.S. : No camera2API nor ARCore