Hi,
I am a little bit confused by apps like
iMyFone LockWiper​
Do they work ? How do they work without erasing user data ?
If a phone has a password and finger-print lock with USB debugging disabled and bootloader locked, the data should be encrypted.
How are these apps working ?
Or is this just snake-oil ?
Phone in question is Samsung J7 Pro, Android 12 (no root, stock rom, bootloader locked, usb debugging disabled, password and fingerprint protection)
Thanks.
Use
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jwoegerbauer said:
Use
Click to expand...
Click to collapse
Wait so these apps actually work??
How??
How do they get past the encryption?
sreyan32 said:
Wait so these apps actually work??
How??
How do they get past the encryption?
Click to expand...
Click to collapse
Why not simply give it a try?
jwoegerbauer said:
Why not simply give it a try?
Click to expand...
Click to collapse
Well I can't give it a try because I don't have a phone which I can sacrifice if things go wrong.
And also the point of asking this question was to find out what is actually secure on the phone if it gets lost.
Is there a way to bypass the lockscreens ? How do I protect against that ?
as you can read there is stated "only for early Samsung devices"
early Samsung devices uses FDE full-disk encryption up to Android 10. encryption key is generated with 'default_password' no credentials used, that allow reset screen lock by deleting locksettings.db file.
However, on locked bootloader that's only possible by gaining root access temporary installing official Samsung signed firmware (such as combination firmware) or via exploit. Maybe Samsung employer has leaked private signing key to that itoolab.com company - we don't know...
Android OEM key leak means sideloaded "updates" could be hiding serious malware
Samsung, LG, and MediaTek are among the companies affected.
www.xda-developers.com
but I know it won't work for your device, because Android 12 must run FBE file-based encryption
Related
Kids were on it downloading random apps. See attached photo. Tried restarting in safe mode; I can't get pass the locked screen. I should be able to do a factory reset; but I want to salvage some photos. Help
"PHONE LOCKED. Follow the link from the other device for instructions"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
babble1 said:
Kids were on it downloading random apps. See attached photo. Tried restarting in safe mode; I can't get pass the locked screen. I should be able to do a factory reset; but I want to salvage some photos. Help
"PHONE LOCKED. Follow the link from the other device for instructions"
Click to expand...
Click to collapse
What does that link do? Is it ransomware?
Rolo42 said:
What does that link do? Is it ransomware?
Click to expand...
Click to collapse
It's an expired link.
is it really locked and encrypted or just a lock screen that can be bypassed
klau1 said:
is it really locked and encrypted or just a lock screen that can be bypassed
Click to expand...
Click to collapse
I doubt it's encrypted; just a lock screen and I can't figure out how to bypass it.
babble1 said:
I doubt it's encrypted; just a lock screen and I can't figure out how to bypass it.
Click to expand...
Click to collapse
try this
https://support.t-mobile.com/docs/DOC-28805
klau1 said:
try this
https://support.t-mobile.com/docs/DOC-28805
Click to expand...
Click to collapse
I did - didn't work
can u get into download mode?
if so flash TWRP recovery then use inbuilt file manager to copy need files to sdcard then do a full wipe and install
Either do the post above or try using the online Android device manager or Samsung find my mobile and lock and unlock the device, that might do something, I'm not sure
Maybe a dumb question but what happens when you click the unlock button?
Hi,
I always used to have full device encryption on my Z5 turned on, but after update to Nougat I'm honestly not sure if it's enabled anymore.
You see, with Android 6.0 the device would always ask me for the encryption pin when turning on, so before Android starts booting up - presumably to decrypt the system partition.
But after upgrading to Nougat it doesn't do that anymore - it just boots right into the system, where obviously it asks me for my pin to unlock the screen, but that lack of the pin input screen on boot is worrying to me.
In the settings, it still says that encryption is enabled.
Does anyone know if if this is expected?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
gambiting said:
Hi,
I always used to have full device encryption on my Z5 turned on, but after update to Nougat I'm honestly not sure if it's enabled anymore.
You see, with Android 6.0 the device would always ask me for the encryption pin when turning on, so before Android starts booting up - presumably to decrypt the system partition.
But after upgrading to Nougat it doesn't do that anymore - it just boots right into the system, where obviously it asks me for my pin to unlock the screen, but that lack of the pin input screen on boot is worrying to me.
In the settings, it still says that encryption is enabled.
Does anyone know if if this is expected?
Click to expand...
Click to collapse
Disable and enable again, thats the reason to always wipe between updates.
Hi, thanks for replying - I don't think I can disable encryption, clicking on the "encrypt device" doesn't do anything. I guess I need to do full wipe, restore from backup, then encrypt again?
gambiting said:
Hi, thanks for replying - I don't think I can disable encryption, clicking on the "encrypt device" doesn't do anything. I guess I need to do full wipe, restore from backup, then encrypt again?
Click to expand...
Click to collapse
Yes, that would be best.
I had the same issue, the problem was I was using an app that isn't by sony or google and was enabled as a device administrator. Uninstalling it solved the problem
Technical question. If I do root in oneplus 6 then generally this "android, embedded, hardware encryption" will be at risk now, yes? Getting to the files on my phone is now possible, yes? Such a simple scenario. I lose the phone or someone steals and by unlocked bootloader and TWRP can easily preview and rip files from the phone, yes? So it this situation encryption doesnt work. Am I right? However, if I won`t do root and will not unlock the bootloader, then encryption works and without my password or fingerprint there, the phone is only suitable for factory reset, so photo files, etc. are still 100% safe. I understand correctly? What do you think?
Post scriptum... and this fuc#@ng root is just so that you can record conversations in android pie because Google blocked this function
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lxxxxxxl said:
Technical question. If I do root in oneplus 6 then generally this "android, embedded, hardware encryption" will be at risk now, yes? Getting to the files on my phone is now possible, yes? Such a simple scenario. I lose the phone or someone steals and by unlocked bootloader and TWRP can easily preview and rip files from the phone, yes? So it this situation encryption doesnt work. Am I right? However, if I won`t do root and will not unlock the bootloader, then encryption works and without my password or fingerprint there, the phone is only suitable for factory reset, so photo files, etc. are still 100% safe. I understand correctly? What do you think?
Post scriptum... and this fuc#@ng root is just so that you can record conversations in android pie because Google blocked this function
Click to expand...
Click to collapse
You are epic but, YES!
P.S. I would love someone to convincingly defend unlocking bootloader but preventing the breach of encryption.
That would be nice.
nabbed said:
You are epic but, YES!
P.S. I would love someone to convincingly defend unlocking bootloader but preventing the breach of encryption.
That would be nice.
Click to expand...
Click to collapse
Any solution? Maybe TWRP for password or something? It should be some kind of solution.
I have a Samsung J400M and since the 23rd of May I am trying to solve the error "Could not do normal boot. Invalid Kernel Length". The device was running Android 9 and this error appeared without any explanation.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can only access the device's download mode.
OEM and FRP are locked and I cannot unlock and I cannot identify my binary number.
I tested firmwares and several versions (new and old) of Odin, but so far I have not achieved any positive results.
I tried to solve by FWRP, but I was also not successful, because I believe that with OEM blocked, I can't get anything. Right?
The image below is the Odin screen. That was as far as I could go so far.
Can anybody help me?
How can I unlock the OEM on this device without having access to Android? Any other solution?
hpernaf said:
I have a Samsung J400M and since the 23rd of May I am trying to solve the error "Could not do normal boot. Invalid Kernel Length". The device was running Android 9 and this error appeared without any explanation.
I can only access the device's download mode.
OEM and FRP are locked and I cannot unlock and I cannot identify my binary number.
I tested firmwares and several versions (new and old) of Odin, but so far I have not achieved any positive results.
I tried to solve by FWRP, but I was also not successful, because I believe that with OEM blocked, I can't get anything. Right?
The image below is the Odin screen. That was as far as I could go so far.
Can anybody help me?
How can I unlock the OEM on this device without having access to Android? Any other solution?
Click to expand...
Click to collapse
Unlock the boot loader with fast boot if possible with Samsung phones. If you can flash twrp which I presume you can't, flash RMM bypass zip and hope for the best. Good luck.
So I got the first step, flashing TWRP. But, there's only a version of TWRP for the a10, would this work?
you don't really need twrp for root, just follow this guide
Installation
The Magic Mask for Android
topjohnwu.github.io
imalreadycrying said:
you don't really need twrp for root, just follow this guide
Installation
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
my phone doesn't show an oem bootloader unlock option
is it grayed out or do you just not see it
imalreadycrying said:
is it grayed out or do you just not see it
Click to expand...
Click to collapse
doesn't exist.
do you have dev options?
imalreadycrying said:
do you have dev options?
Click to expand...
Click to collapse
yes
send me a screen recording if you can, dev options should look like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have previously tried Kingo/King Root which worked on my KitKat Nabi tablet, I tried that on my a10e it failed. Root checker says there is no root for andr 11 on the a10e
whatever you do, do NOT use kingoroot, it basically installs a outdated version of SuperSU (which isn't liked by the community anymore because the original developer sold it to some random company) and bloats ur system up.
Yep, no OEM bootloader unlock option in dev settings
it may be possibly locked to your carrier. again, you can send me a screen recording or get an unlocked phone
My phone appears to be unlocked already, there is no sign of Verizon still being on here. I have since upgraded phones and the SIM card isn't in anymore.
Do I have to factory reset to fully get rid of the OEM?
i found this youtube video with some quick searching. it's in hindi but you can get the gist of it.
I most certainly dont have to disable automatic time right?
i don't know, after you get the option maybe you can set it back
i followed and nothing happened
did you reboot your phone after the fact?
yep, nothing works