![]() ![]() WifiHistory.db nf log-files.xml sensor_big_data_usage.txt SimCard.dat enterprise locksettings.db-wal sensor_big_data.txt HWParamTime.bin dropbox locksettings.db-shm screen_on_time ![]() Ls: /data/system//heapdump: Permission denied Ls: /data/system//.aasa: Permission denied Ls: /data/system//secure_storage: Permission denied Ls: /data/system//ndebugsocket: Permission denied Ls: /data/system//container: Permission denied Ls: /data/system//users: Permission denied Ls: /data/system//hdcp2_5386: Permission denied Looking at /data/system/ some files might be missing (I've read that unlock data is stored in gatekeeper* files which I can't find, maybe because of insufficient permissions): 1|dreamlte:/ $ ls /data/system/ I understand /data/system_de/0/spblob/xxxxxxxxxxxx.weaver is used in the password verification. LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system_de/0/spblob/xxxxxxxxxxxx.weaver: open failed: ENOENT (No such file or directory) Some suspicious messages: LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/fmmpassword.key: open failed: ENOENT (No such file or directory) Looking at logs - since ADB is working, I've tried looking at adb.exe logcat -b system, but have no idea what to look for. Might be related to missing files (more below). Strangely, it's not throttling (tested the same method with an Android 10 device and immediately got "Request throttled"). The response is always "Old password 'xxxxxx' didn't match". "Guessing" the PIN - I've tried feeding all the possible combinations to adb.exe shell locksettings verify -old xxxxxx Samsung FindMyDevice - can change the PIN if enabled in the settings - disabled it for security reasons. ![]() ![]() Google device manager - can only reset the device for non-enterprise accounts. It is encrypted: > adb shell getprop | find "crypto" Firmware is G950FXXS5DSJ1 build date Sep 30 2019. The device is not rooted and "require PIN when device powers on" is disabled. I haven't restarted the device yet, hoping to "find" the new pattern or somehow bypass the screen lock. I'm guessing the cause is memory corruption or some bug. Social media is a huge deal to them.Įdit: also sell everything so you only have cash in your portfolio, that way they can't use that as an excuse why they can't close your account.A few days ago my unlock pattern was not recognized anymore. Also create a twitter account and hit them up on twitter. TL DR: annoy the hell out of them till they fix it. The idea is to be polite but waste as much of their time as they are wasting yours, to the point where it becomes imperative that your issue is dealt with because the time spent on you is becoming costly. REMEMBER TO BE POLITE, DO NOT GET UPSET OR ANGRY: if you do they will just find a way to get rid of you and not handle your issue. Repeat steps 1-4 every day until resolution or you become such a goddamn everyday annoyance to their customer service department (which is apparently small) that they deal with you. There should be some way they can liquidate the cash in your portfolio and transfer it to you or send you a check. Tell service agent you would like to withdraw your funds effective immediately. (Spoiler: they're going to tell you that's not possible, see step 4) At this point if its longer than 48 hours reiterate how long you have been experiencing this issue and tell them that you really need it resolved within 48 hours. Politely demand an anticipated resolution timeframe for the issue. (I mean the exact minute) That way you avoid getting stuck in the queue or at least are not very high on it.Įxplain to them when you first experienced the issue and how long its been since then. It's my method for dealing with businesses that aren't being helpful.Ĭall them every day right when customer service opens. It sounds like its time for the annoying method. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |