AFAIK hiding the SSID only changes behaviour for initial connection as one has to know the SSID to be able to connect instead of just choosing from the list.

Also the WiFi will at some point confirm its network name to devices who would try to connect to it which could be intercepted by a third party that would try to connect to it.

In my opinion hiding the SSID is just a tiny security by obscurity measure that only protects from everyday users.

Here is some interesting read about the situation with some examples:

https://www.acrylicwifi.com/en/blog/hidden-ssid-wifi-how-to-know-name-of-network-without-ssid/

It is not possible without coding up a custom solution.

I find a way to unlock device without waiting. You need to: Mi Account and SIM-card with same number, that registred in Mi-account. Then, you need to link account to device (in internet much of instructions). Then the main step: download another version of Mi Unlock 5.5.0224.55, and unlock with this version. It do next steps: bypass the unlock time, unlock without getting any keys/tokens.

In the Android environment, who is this "shell" user that I'm SSH-ing through ADB, as I attempt to see how much I could do with my Amazon Fire 10 tablet?

Said user's level seems very, very client-level, yet I get the impression it is the same administrator user directly calling the commands to facilitate the installation of the packages.

How does it work within the Android system?

My Android ID has changed since a factory reset. Now some apps/services don't work. Besides using Titanium Backup, how can I restore/change back to the previous Android ID? I already know what the ID is.

Android 7 | Rooted

I had a working Samsung S10 which was already rooted with Magisk (v20.*). Due to a Magisk update (v24.1) my root got broken... So I need the manual way.

I successfully patched the stock "recovery.img" trough Magisk "Select and Patch a file" method since the "Direct Install" is not working any more for some reason I don't understand ("Installation Failed. Unable to detect target image"). The official website recommends to flash the "recovery.img" trough "fastboot". But then I discovered fastboot is not available for Samsung phones. So I need to use Odin. But Odin is not accepting *.img files...

I do not want to loose my current Android installation because it's very customised. But I need my root back.. I searched and searched for days for a working solution to manage this. So this request is my last hope as I can really not find a way to manage this...

How can I safely flash this "magisk_patched" "recovery.img" to my "Samsung S10" without wiping any data? And does this Magisk patched "recovery.img" contains my existing TWRP recovery? Or do I need to reinstall it after the upgrade? I remember when I first rooted my phone it was quite complicated to do this since the Samsung S10 does not have a ramdisk so the recovery partition is shared with TWRP and the Magisk su.

Does anyone has any good advice how to manage this without losing my data (and Android10 installation)? Magisk delivered me a 6.2GB "magisk_patched-24300_8m9cQ.tar" file but I'm scared to flash it trough Odin as I don't want to loose my data on my "512GB sdcard" internal storage.

I know this is a complicated situation but any help would be highly appreciated as I really don't know what to do any more to manage this.

Some of my apps only ask for a permission to read external storage, not to write. I trust these apps (even my banking app), so I guess they are not looking at my files. Any idea why they need this permission? Is this a useless permission?

Official Xposed is dead since years (sadly). So No hope in doing these things via it...

Make script to debloat and run it after every factory reset...

like this one

https://github.com/jasineri/android-bloatware

I have a rooted Oneplus 7 Pro. Today my phone said that an OTA had finished downloading and to reboot to install the update. I had been postponing this update and decided to finally go through with it.

I went through all the steps to keep my root, uninstall magisk, download OTA, flash twrp ab retension script, install magisk to inactive slot, and finally reboot. I am now stuck at the boot animation.

When I try to boot into TWRP, the screen keeps flashing at the TWRP loading screen but I can never actually get into it. I am able to ADB into the phone at this point though and the recovery.log says something about Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) Does anyone know know how to fix this? Any help would be greatly appreciated!

Edit: I have made a little progress. I was able to change the partition back to the original partition and while I still can't boot, I can get into TWRP now.

Edit2: I updated my TWRP and can now get into TWRP on both partitions. On the old partition I can decrypt my data with pattern (and was able to back everything up), but on the new partition it is asking for a password and I don't have one. Still get stuck on the boot animation are both partitions. I have also tried uninstalling all my magisk modules (except for one adb one) and that didn't help either.