Hi, with Android 12 on my Zenfone 8 I could delete my advertising ID. With Android 13 I can't delete it, only reset it. Does this this just affect Z8s or for Android 13 on all phones?
I see there is still option reset and delete advertising ID on my Z8 with Android 13, WW_33.0210.0210.210 and if I delete it, then I have option to get a new one.
Bzucko said:
I see there is still option reset and delete advertising ID on my Z8 with Android 13, WW_33.0210.0210.210 and if I delete it, then I have option to get a new one.
Click to expand...
Click to collapse
Thanks, had another look and found the delete option.
Related
Hi everyone, I searched a lot on this forum and others and I couldn't find an answer to my problem (or even if my problem is a big deal). I flashed Assonance with the include kernel, my first ROM flash =-) and I did a lot of research before I did it and decided to backup my Android ID...which I did, BUT I only wrote down the number and now when I enter it into "Android ID Changer v1.5" I click "Change ID" and it automatically reboots but does NOT change my ID...yes I have busy box and super user access. Can anybody help me? Is this even a big deal?
on the root of your SD card, create a file name udpate.id (yes, udpate, it's a typo, but that's what the startup script reads) and put only your android id in it. then restart your phone and check if the idea has changed. also it's not that big of a deal, but the problem with these custom roms is that everyone on the same rom ends up with the same android id (i think?) which causes us to queue up for downloads on the market instead of downloading instantly.
slifer315 said:
on the root of your SD card, create a file name udpate.id (yes, udpate, it's a typo, but that's what the startup script reads) and put only your android id in it. then restart your phone and check if the idea has changed. also it's not that big of a deal, but the problem with these custom roms is that everyone on the same rom ends up with the same android id (i think?) which causes us to queue up for downloads on the market instead of downloading instantly.
Click to expand...
Click to collapse
Thanks! Just a regular .txt file? Like make one from notepad?
Endoran said:
Thanks! Just a regular .txt file? Like make one from notepad?
Click to expand...
Click to collapse
Yes, but save it as a .id or save the .txt and rename the extension to .id.
jhedfors said:
original post in General....
Click to expand...
Click to collapse
When I have to factory reset my device, I want to be able to avoid re-verifying my debit card in Google Pay card - unfortunately, I have to call in for this, and it is a pain....
Would backing up the settings_ssaid.xml file in /data/system/users/0, and restoring that file be enough for Google Pay to think that nothing has been changed?
I did actually restore that file successfully, but not until after I had opened up Google Pay once.
Prior to Oreo, restoring the Android_ID in Titanium Back seemed to do the trick, but that does not work any more.
I am asking in the Magisk forum, as someone might be aware of what the Google Pay app might be using, and how to make it appear not like a new device.
I tried restoring the the ID found in the settings_ssaid.xml file, but it did not help. Also the device fingerprint is being reported with the same value. I wonder what Google Pay could be looking at to determine that the ROM is different. ROM name, or some other property?
Hi
I posted the thread here as i think it's the most appropriate, pardon if im wrong.
The toast message "Omniswitch restricted mode, failed to gain system permissions" is shown in the notification list.
How do I give it that? i installed via Magisk, and i also tried flashing the zip from TWRP.
the magisk manager doesn't list it in #superuser where for example substrantum and solid explorer are listed.
I'm in the same issue android 13, nothing doesn't work...
If an app restrict you, do this and this is an example, see attachment
Pandemic said:
If an app restrict you, do this and this is an example, see attachment
Click to expand...
Click to collapse
actually that , there is no such option is not found !!! - Tap More and then Allow restricted settings.
DroidBatteria said:
actually that , there is no such option is not found !!! - Tap More and then Allow restricted settings.
Click to expand...
Click to collapse
Oke kinda stra ge because i have Xperia 1 iii with A13 and have that option when an app restrict an option then i just do that.
I have an A13 OmniSwitch APK which used to work on December security update but now for January it does not. It only shows the overlay if there are no recent apps but does FC when recent apps are available.
is it working on android 11\12\13 ???
If this question is directed at me, you can find working OmniSwitch for 11 and 12 in the appropriate thread. Mine did work on earlier A13 but not lately.
nickelnine said:
If this question is directed at me, you can find working OmniSwitch for 11 and 12 in the appropriate thread. Mine did work on earlier A13 but not lately.
Click to expand...
Click to collapse
ok , what I 'm trying to make work on a13 but without success , I 've tried all the traditional ways , but it does not work ... I wanted to know how to work on a13 ...
Flash this zip then copy OmniSwitch to /system/priv-app. Be aware it may not work on newer A13 patched ROMs.
Thanks for trying to help, I really appreciate it!!
I had already tried the way you said, but without success!
image 1 - I can install everything correctly, but when I run it, this error appears!! I just need to fix this error!
image 2 - I also tried changing the installation location, and it still didn't change anything!!!
I also tried changing the installation location, and it still didn't change anything!!!
I've scoured the entire internet [google] for a solution to - Restricted mode failed to get system permissions Android 13 app - but there is no mention of it!! there are no speeches except this one!
I have read many negative comments about Android 12 system update. It is scheduled to be installed tomorrow, but I want to cancel the update and free up space it is taking. How can I accomplish that?
it'll probably be stored in the root folder, possibly in /data/ somewhere (that's a guess based on where custom roms store downloaded updates).
just checked my phone and there's 2 folders, one called ota and another called ota_package in /data/
on another note, if you can find a copy of Dec or Nov you can still flash back to those even after flashing OneUI 4 first release.
3mel said:
it'll probably be stored in the root folder, possibly in /data/ somewhere (that's a guess based on where custom roms store downloaded updates).
just checked my phone and there's 2 folders, one called ota and another called ota_package in /data/
on another note, if you can find a copy of Dec or Nov you can still flash back to those even after flashing OneUI 4 first release.
Click to expand...
Click to collapse
o I won't be able to access the root folder without rooting the phone then. Thank you. I was trying to avoid reloading the system and was hoping to a way to disable the update and delete the OTA.
maybe ADB can get there without root, not sure on that.
auto install was updated. Will see how the phone performs. I could have done factory reset but figured might as well test drive Android 12 first before doing all the leg work. Thank you for the suggestion.
Hi,
i have problems with file access under latest android 11 rooted firmware. I want to connect through ftp and want to backup files from internal storage and sdcard but with primitive ftpd and rooted access i can not see content in /storage/emulated/0 for me its empty :-(.
I have problems with a tasker task to move files from internal to external storage after the firmware update.
Is there any way to get access again with ftp for the full file system with root?
best regards,
Thomas
Hello,
I just want to know if it was a temporary problem or it's the same on Android 12 too ?
If not, how did you fix this problem please ?
Thank you
the problems exists still on the latest Android 12 version on S10e so still no solution yet :-(
My guess is that this isn't a problem with Android, but that your FTPd service doesn't have root access. If it doesn't have root access, it can't see the folder. If it's not "root aware" it won't be able to ask for root access either. That's my guess.
I'm not familiar with "primitive ftpd" so I don't know if it has this capability, maybe it does.
In the past, for remote access, I have used some file explorer apps that have root capability... those allowed me to remote into the phone. But that was a long time ago - these days I just connect from my phone to the network drive instead, and push files that way (instead of "pulling" from a remote server). This is safer since you aren't leaving an open FTP socket on the phone, which is a bad idea from a security standpoint.
till the last december update (this was an update i made maybe after about one year without updates) all access was fine and since then every access is impossible, its not only ftp, its tasker shell with root access too, worked before fine and now its horrible,
Samsung seems to break some folders, you can access the external sd card with /storage/emulated/[idforsdcard]/ but if you go one level up the folder /storage/emulated/ ist empty and does not show any subfolder, same if you are in /storage/emulated/0/Android and enter the data subfolder samsung takes you to /data
it is so strange what samsung does i don't understand
Thank you very much for your answer
Sorry for this ridiculous question, but even a factory reset can't help you regain access to all your folders ?
Precisely, I also see that Samsung is restricting its phones more and more so that we can't use many functions of our phones as before
I'm currently on Android 10, but with all that I hear, I'm afraid of Android 11 and Android 12
i have fresh installed VC6 Firmware (Android 12 March Update) with factory reset and all access problems still the same, so its the "scoped storage" feature and maybe some samsung addons what leads to this problems
if you want full access to your phone then Android 11 & 12 makes it hard to get and some apps are not optimized for this new scoped storage
FWIW, I have a non-rooted, pure stock phone. I can use FX to go to /storage/emulated/0 and see everything properly. I'm on A11, Snapdragon, S10+.
This implies your app is not being allowed to see the storage. This seems to confirm that it's an app issue - ie, the FTPd may not be able to deal with the new structures on A11/A12. As you noted, it might be this "Scoped Storage" feature... which the app is not able to work with?