last day (33 days later) » 

11:07 AM
1
A: Halp...soft-bricked A40 after uninstalling apps ADB!

alecxsencryption is hardware-backed therefore userdata can decrypted on device itself only. to get adb access you need combination ROM + DID token. Still userdata is not accessable unless device is unlocked/decrypted with lock screen credentials (might not possible from adb in current boot state). Fact...

 
This doesn't qualify as an acceptable solution - what exactly am I supposed to do with this information? And could you please elaborate what "combination ROM" and "FRP" is? Most importantly: Can you actually point out a critical system app that has been disabled? I've posted the complete PowerShell output leading up to the moment of crash. If this is really caused by a critical Android system app, you should be able to identify it from the above list. Much appreciated!
Also, I never said that my device is encrypted, at least I didn't activate any encryption on my part (not sure if such functionality is even supported by default on stock Android systems). Or does Android automatically encrypt user data using lock screen credentials as the encryption key?
Finally, the link you've posted in your comment (forum.xda-developers.com/t/4043673) contains zero useful information.
PS.: I can access both recovery mode and download mode. In the latter, the information text displayed includes "FRP LOCK: OFF", "OEM LOCK: ON(L)" as well as the device id (DID). Does this mean that FRP is already unlocked? I never registered a Google account, btw
(Information added to question)
No, it does not. Your answer doesn't give any useful instructions, furthermore it makes wrong assumptions regarding encryption and FRP lock state. You basically just threw in some lingo without actually caring about a concrete solution, furthermore you didn't properly read the question and the information contained therein. Finally, you imply that I've disabled system apps without any proof although I've posted the ADB shell output leading up to the crash. Face it: You just ranted based on wrong assumptions, but didn't actually provide any solution. Sorry, not accepted.
 
instructions for what? factory reset? there is no solution and therefore no instructions. feel free to downvote. you might figure out which was the critical package from this list (I haven't checked your package list it's homework for device owners. only device owner can trial & error, I don't own samsung device)
 
What about said combination ROM?
And actually...that list on XDA that you've linked might have been the exact one I used for disabling the bloatware packages! I copied the list, replaced disable-user with uninstall and packed everything into a batch file. So, yeah
@alexcxs What is a "DID token bypass" and what do you mean by "current bootloader level"? Screen lock has been set (unlock via fingerprint sensor).
Wait...Android is just a Linux port, right? I know from desktop Linux that, in case my disk is encrypted e.g. with LUKS, I can simply do sudo cryptsetup luksOpen and then mount the volume. Can't I do the same with my phone?
 
encryption is hardware-backed therefore userdata can decrypted on device itself only. It's not even android, TEE is another proprietary OS. besides that you have Exynos chipset there is not even a way to dump raw partitions (like qualcomm EDL mode)
 
Okay, I just read similar information in another discussion. Sounds a bit disheartening. Also very frustrating, because this seems to imply that big corps and agencies have access to my data while I, as the owner, don't (even though I'm holding all the keys in my hand). I don't like this philosophy at all
"Trusted Environment" sounds a bit Orwellian, too, as it seems that the owner him-/herself is not actually part of that trusted circle (which contains the personal data).
 
11:07 AM
you may ask Alexander Tarasikov if there is any exploit I am not aware of
 
 
6 hours later…
4:39 PM
@kerstin92 something like this (unfortunately not for Exynos 7904) fredericb.info/2020/06/…
 

  last day (33 days later) »