Recent content by pxan8

adb doesn't show the device fastboot device works

I am trying this right now. I am downloading the OTA as we speak. Thank you for your time and all the help BTW ---------- Post added at 03:49 PM ---------- Previous post was at 03:31 PM ---------- adb: sideload connection failed: no devices/emulators found adb: trying pre-KitKat sideload...

same :crying:

yes. I get "FAILED (remote: 'flashing unlock is not allowed') fastboot: error: Command failed"

For the life of me I can't understand what made me uncheck the oem unlock from the developer options before locking the bootloader. From what i get I just wasted a perfectly good device. It seems that nothing can be done. I don't seem to find any way to unlock the bootloader when the oem unlock...

I was running latest android 10 rooted with magisk (patched boot image) and just got a new phone. I wanted to give it to my wife. I rushed and locked the bootloader. I forgot I was rooted. Now when I boot i get no valid image. I can get to bootloader but not in recovery. Edit I unchecked the...

Please help. I locked my bootloader while rooted with magisk and didn't return to stock. Am I screwed? Did i brick my device or is there a way to fix it?

I couldn't make a proper call without the line dropping for almost a month. Since I disabled OK Google voice detection my problem has been fixed. It's been 2 weeks now without any problems.

There is a problem with the July release and mtp. It has something to do with the kernel. Either flash another kernel or flash the June release where everything works as expected.

Go to settings/Apps, find Phone, go to app info, scroll to advanced and change "modify system settings" to Yes. The block option will appear.

Great work. Extremely smooth. The only problem, though minor, that I've encountered is the "android is updating" screen when I enable the option to unlock the phone after a reboot with fingerprint as mentioned by a few others.

Run the same command without the ✳ at the end settings put global policy_control immersive.navigation=

Definitely better than the build.prop. At least this way the phone is stable :D

No, just the terminal command. If I change the build.prop I get system Ui force close. Unfortunately haven't figured out how to stop the fc pop ups. I just put the navbar in permanent immersive mode. Terminal "Su" "settings put global policy_control immersive.navigation=*"