Related
Hi All,
I've been having a nightmare with my phone, my PIN lockscreen wont accept my pin number on my S2. Now before you think i've nicked it check my posting history on the S2 forums, you'll see i've been posting there for a while.
I've CAN access the phone by removing settings.db, from
/data/data/com.android.providers.settings/databases/settings.db
the lockscreen request dissapears then, but it wont let me create a new pin as it still thinks a pin is set.
I've followed this thread:-
http://forum.xda-developers.com/showthread.php?t=1409304
regarding removing a pin, but when i try to reset my pin it wont take it, or more to the point it does take the values (i checked them using an SQL browsing tool) but it still asks me for a pin.
Reformatting System, Cache and Data via clockwork mod recovery and flashing 2different roms didnt help either as the pin screen keeps coming back for some reason.
Would anyone know if flashing back to stock via Odin would help, does that Wipe the phone completely? Or even better, anyone know why this is happening and prevailing between wipes?
The only thing i havent tried yet is wiping /emmc/ (internal memory card) and trying again.
I've been at this for 2 days now, can anyone shed some light on this?
Ok as per above a follow up:-
I have fixed this by removing cryptlockscreen* files in EFS. I can also now enter new pins or patterns etc as before.
The is a problem however when i try to create a new pin, it takes it and everything looks ok, but when i try to enter my pin on the lockscreen again it still wont take it and i have to do the same process again. (Wipe out the relevant files in EFS)
I've been able to secure my device simply by using a pattern lock instead but its not an ideal solution.
Does anyone know why, after deleting the files above i should STILL have an issue?
Remember, this went from working perfectly to not, possibly due to wavesecure and it would be good to get to the bottom of this.
TheBlueRaja said:
Ok as per above a follow up:-
I have fixed this by removing cryptlockscreen* files in EFS. I can also now enter new pins or patterns etc as before.
The is a problem however when i try to create a new pin, it takes it and everything looks ok, but when i try to enter my pin on the lockscreen again it still wont take it and i have to do the same process again. (Wipe out the relevant files in EFS)
I've been able to secure my device simply by using a pattern lock instead but its not an ideal solution.
Does anyone know why, after deleting the files above i should STILL have an issue?
Remember, this went from working perfectly to not, possibly due to wavesecure and it would be good to get to the bottom of this.
Click to expand...
Click to collapse
You cannot do this. You need to extract the password salt to quickly brute force such a thing. Use adb to extract data for sqlite. If rooted attempt a factory reset in recovery. Seriously this is some forensics stuff.
Good luck.
Hello folks,
idk if anyone of you guys had a hard time with the same annoying 'feature' on ics roms which forces you to set a PIN/password/pattern lock when you try to install enterprise certificates into your credential storage.
As for myself I need some of these certs to log into the WLAN at my university (which is 802.1x protected). But I don't feel the need of locking my phone.
So I exploited this to go around setting a password for the secure lock screen.
-------------------------------------------------------------------------------
Prerequisites are a rooted phone, a root file browser or adb tools and apparently your certificates.
I tested this on AOKP build 38 and 39 on a rooted HTC Sensation XE and will check this on two other devices the upcoming week.
UPDATE: seems to work even easier, I made the changes inline since the previous workaround did not work in every case.
Step 1:
Download the certificates to your SD card and/or install directly via browser/email etc. Do as you are asked and set up a PIN/password/pattern lock. Remember it
Step 2:
now with your root file browser go to /data/misc/ and recursively copy the folders keychain and keystore to a save place.
These are the folders containing the certificate files.
(See [System settings > security > Trusted credentials] for installed certificates)
With adb tools you can for example do this:
Code:
adb shell
su
cp -R /data/misc/keychain /sdcard/certificates/
cp -R /data/misc/keystore /sdcard/certificates/
Step 3:
Go to [System settings > security] and click [Clear credentials] at the bottom of the menu. Now your previously installed certs are wiped and you are free to set the lock method to [none], [slide] or [face lock] again.
Step 4:
Finally fire up your root file browser again, set /system as read/write and copy the in Step 2 backed up directories back to /data/misc/. They are now installed as the before but since CertInstaller.apk does not get involved, noone forces you to lock your phone.
in adb shell:
Code:
cp -R /sdcard/certificates/* /data/misc/
Now you should be able to find your newly added certificates in the System list under [System Settings > Security > Trusted credentials] in the [User] tab and thus be able to log into your desired WLAN.
I hope this helps some people out there. When I get deeper into developing maybe I will find a 'cleaner' method for this.
have a good night,
.eXa
Thank you for sharing! I have been really looking for this kind of hack.
Sadly I can't use it as my certificate has a different structure: it seems to install 3 files in /data/misc/keystore/
The files are 1000_USRCERT_Polimi ; 1000_USRCERT_Polimi and .masterkey
I tried copying these files to the new directory and even changing the file extension but it did not work.
I don't know if this issue is rom or certificate related.. anyway I am using a stock rom on samsung galaxy s3.. perhaps samsung manages differently certificates..
Have you any clue on this? Thank you!
hey, thanks for the reply.
alright, I figured something new, maybe try the updated version of the tutorial and pls tell me if that works for you.
greetings
.eXa said:
hey, thanks for the reply.
alright, I figured something new, maybe try the updated version of the tutorial and pls tell me if that works for you.
greetings
Click to expand...
Click to collapse
You were fast! and I think you made it: I can now select the certificate in the wifi options dialog (so it's correctly installed).. but I can't test the access to the network until monday.. Anyway I am convinced that it made the trick and it was really simple, I must say.
Thank you so much , this will be useful to many people!
Your trick helped me only partially. It allowed me to install the certificates just fine. But as soon as I try to connect to any 802.1x protected Wi-Fi network, the phone bugs me again with setting the screen lock. So I need a workaround for accessing the key storage.
I tried it and sadly it does not work: it asks me a password to activate the credential storage.. only problem is that I never set a password for it so I can't insert it and use the certificate. Too bad but I think it depends on the certificate.. anyway thank you very much for the help provided!
so, back from vacation.
@grgur: in your setup it is the 802.1x wlan that forces you by corporate policy to lock your phone. i am still trying to figure this out, i will try and search the system where stored wlan access points are stored. update will come as i find a solution to this.
@grievous: which version of android are you on? try clearing your credential storage first, then set up the password and then add the certificates. after that proceed with my tutorial.
since i am in the middle of learning for my exams i have really no time to go on with my android studies... it seems like in the long haul someone has to "fix" the app that handles phone lock and device policies. i know who the bad boy is but i am lacking time right now, so hopefully i get this done by the end of august.
i'll keep you up to date with my progress.
greetings
Is there a one-click fix for this yet? Bloody annoying...
Working great on stock rooted JellyBean nexus 7. Muchos grazis!
As soon as i go back to university (politecnico di milano) i will use your suggestion! Has anyone already tried with polimi wifi network?
.eXa said:
@grievous: which version of android are you on? try clearing your credential storage first, then set up the password and then add the certificates. after that proceed with my tutorial.
Click to expand...
Click to collapse
pippodream said:
As soon as i go back to university (politecnico di milano) i will use your suggestion! Has anyone already tried with polimi wifi network?
Click to expand...
Click to collapse
I was using a samsung stock rom 4.0.4 and the tutorial worked but when trying to connect again it asked me for a credential pwd (that I never set). Now I'm on CM10 so there should be no problem. As soon as I get to Polimi I'll try
doesn't work for me (SGS2 AOKP JB)
Hi!
I've tried to apply this solution to my device (SGS2 AOKP JB), but after clearing the credentials and copying back the keystores/keychains the user credentials cannot be found (Trusted credentials > User is empty).
Could anyone please help me with this one?
Thank you in advance.
zsszabolcs said:
Hi!
I've tried to apply this solution to my device (SGS2 AOKP JB), but after clearing the credentials and copying back the keystores/keychains the user credentials cannot be found (Trusted credentials > User is empty).
Could anyone please help me with this one?
Thank you in advance.
Click to expand...
Click to collapse
I have the same problem. And unfortunately I didn't find solution for that.
Wysłane z Android 4.1.2 za pomocą Tapatalk 2
In fact i was really searching for this i will try this tomorrow !
Sadly exchange with client certificate refuses to work after trying this hack It says that it can't found the cert it needs..
I have found the permanent solution !!!
I hope this will solve everyone's problem here.
These are the steps I have done after installing Eduroam certificates from my university:
1. Obviously I have installed CA
2. I had to choose which lock screen style will I use (I only could have choose between pattern, PIN, and password), it doesn't matter which lock screen style you choose between those three.(FYI I have chosen pattern)
3. After that I have failed to swipe my lock pattern correctly 15 times
4. The "Unlock with your Google account / unlock with your PIN/password" screen appeared.
5. Choose the "Unlock with your Google account" and type in your username and password
6. After that the "Choose your lock style" screen appears. DO NOT CHOOSE ANY OF THEM, since swipe still can't be chosen
7. Just press back to exit this menu.
8. Lock your screen and unlock it ---> You have swipe unlock enabled along with the CA certificates !!!
bubr3g said:
I have found the permanent solution !!!
I hope this will solve everyone's problem here.
These are the steps I have done after installing Eduroam certificates from my university:
1. Obviously I have installed CA
2. I had to choose which lock screen style will I use (I only could have choose between pattern, PIN, and password), it doesn't matter which lock screen style you choose between those three.(FYI I have chosen pattern)
3. After that I have failed to swipe my lock pattern correctly 15 times
4. The "Unlock with your Google account / unlock with your PIN/password" screen appeared.
5. Choose the "Unlock with your Google account" and type in your username and password
6. After that the "Choose your lock style" screen appears. DO NOT CHOOSE ANY OF THEM, since swipe still can't be chosen
7. Just press back to exit this menu.
8. Lock your screen and unlock it ---> You have swipe unlock enabled along with the CA certificates !!!
Click to expand...
Click to collapse
It won't work for me. After 10 failures it says that I have to wait 30 seconds for another try. I have Samsung Galaxy SII with Omega v21 (based on Samsung-stock Android 4.2.1).
TrojanPL said:
I have the same problem. And unfortunately I didn't find solution for that.
Wysłane z Android 4.1.2 za pomocą Tapatalk 2
Click to expand...
Click to collapse
Same thing here. Although files are backup up, there is no certificate showing up on the list. It would be great if someone found a solution, this lock is driving me nuts.
Hi, this seems almost too easy, and it's more of a workaround than a solution, but it works:
Try to login to your network
Accept the request to set up the mandatory screen lock and set one up (any kind)
Connect to your network
Go into Android settings/Security and change the screen lock type to None
Your network credentials are now saved and there is no longer a screen lock.
astarothcy said:
Hi, this seems almost too easy, and it's more of a workaround than a solution, but it works:
Try to login to your network
Accept the request to set up the mandatory screen lock and set one up (any kind)
Connect to your network
Go into Android settings/Security and change the screen lock type to None
Your network credentials are now saved and there is no longer a screen lock.
Click to expand...
Click to collapse
The last time I tried this with my CyanogenMod install, removing a pattern/password/pin was not possible because of the certificates. Only after removing the certificates, the screen-lock-type could be changed to a non-pattern/pin/password type.
earlier today I found out my little sister knew my pattern so I changed it. But when I changing the pattern I didn't pay attention a lot and know I forgot the pattern.My data and WiFi are disabled.I can't sign in to my google account with the phone now.
My question: I can't sign in because data/wifi is off? If yes is there a way to turn on wifi or data without unlocking phone?
I'll be thankful if someone help me because I can't loose my apps and setting
I'm using Galaxy mini CM 7.2 official
Hi, you can go into recovery mode and make a data wipe, but you will loose all apps and configurations.
On CM10.2 is it possible to activate wifi or data from lock screen but i don't kow cm 7, sorry
ayadgalaxymini said:
earlier today I found out my little sister knew my pattern so I changed it. But when I changing the pattern I didn't pay attention a lot and know I forgot the pattern.My data and WiFi are disabled.I can't sign in to my google account with the phone now.
My question: I can't sign in because data/wifi is off? If yes is there a way to turn on wifi or data without unlocking phone?
I'll be thankful if someone help me because I can't loose my apps and setting
I'm using Galaxy mini CM 7.2 official
Click to expand...
Click to collapse
Right go into recovery mode and do a factory data reset like they said above might delete your internal memory but hey you get your phone back!
☆☆DeMeNtEd_ChAmP☆☆
I know I can do factroty reset but I'm looking for a way to unlock phone without loosing my data
ayadgalaxymini said:
I know I can do factroty reset but I'm looking for a way to unlock phone without loosing my data
Click to expand...
Click to collapse
if you have usb debugging enabled you can break it with adb by using adb shell commands
follow this guide in my blog http://www.blog-android.com/general/break-pattern-lock/ for more details and dont use that aroma method it is only for mediatek devices
you can try the other methods given there
ayadgalaxymini said:
earlier today I found out my little sister knew my pattern so I changed it. But when I changing the pattern I didn't pay attention a lot and know I forgot the pattern.My data and WiFi are disabled.I can't sign in to my google account with the phone now.
My question: I can't sign in because data/wifi is off? If yes is there a way to turn on wifi or data without unlocking phone?
I'll be thankful if someone help me because I can't loose my apps and setting
I'm using Galaxy mini CM 7.2 official
Click to expand...
Click to collapse
I don't know why you facing this! if I forget my password/pin my phone gives me a option to enter my gmail id and password and then directs me to change the password/pin! this occurs even If I remove my SIM card also!
anyway a probable solution for you - http://forum.xda-developers.com/showthread.php?t=2225695
I am just sharing my experience
I had locked gionee m2 without root and without debugging enabled I was able to disable lock with out wiping data
What I did was
1)flashed carliv touch recovery using special flash tool
Use PC to Flash*recovery.img*using sp-flash tools. (Please be aware of how to install required drivers etc..)
Select original scatter file of your version of ROM. If You are using stock ROM, Make sure that you have not altered the phone partitioning earlier.*
Be careful and Remember to select/tick only 'recovery' in the list. You can also check preloader if you like. and select ONly 'download' button. (NOT firmware upgrade!). Connect your switched off phone to your PC. Wait till your task is complete. Shows you a green circle.
2)backup of data was made using carliv touch recovery (ofcourse with locked phone data)just in case anything goes wrong.
At this moment carliv touch recovery was working but boot and power options were not functioning
3)now flashed rooting file this time by carliv touch recovery
4)carliv touch recovery has aroma file manager too. But I was not able to open lock by this method as
Aroma File Manager, Click on menu option and go to settings*
Select Mount All Partitions*
Now, exit from Aroma File Manager and reflash it.*
Now, you will see each partition is mounted
5. Now, go to /data/system
Note : If you have sd-ext mod to increase internal storage, go to /sd-ext/system/
6. Now, If you have to remove pattern lock, long press and delete gesture.key
If you want to remove password, delete password.key
7. Exit the Aroma File Manager
8. Reboot*
9. Enjoy*
Didn't enjoyed this method somehow I don't know but it didn't worked for me as this folders didn't showed above said files.
5)now I flashed pattern password disable. Zip file using carliv recovery
And on booting phone screen asking for google id and password was gone link http://forum.xda-developers.com/attachment.php?attachmentid=1900741&d=1366570627
This was my method to unlock pattern locked gionee m2 phone but this can help you out too
Sent from my HM NOTE 1LTE using Tapatalk
Thats the problem...Android Device Manager is useless cuz there is already a pattern...I tried almost 100 times and there is no "forgot your password?" option...I need at least do a copy of my pictures.
Is there any solution to this? I feel like a real idiot...I was trying a different pattern and I forgot It...I cant believe it...
I think there's a file not sure if it is directly under /data/system or one of it's sub directories, but basically what I did was to boot to TWRP , use the built it file manager and delete that file. I could then access my phone. I will search maybe I kept the file name somewhere.
EDIT:
Just remove this file /data/system/gesture.key
and reboot.
wizardwiz said:
I think there's a file not sure if it is directly under /data/system or one of it's sub directories, but basically what I did was to boot to TWRP , use the built it file manager and delete that file. I could then access my phone. I will search maybe I kept the file name somewhere.
EDIT:
Just remove this file /data/system/gesture.key
and reboot.
Click to expand...
Click to collapse
How I do that? my phone is not rooted, the bootloader is locked and debugging mode is off :S
Jerber said:
How I do that? my phone is not rooted, the bootloader is locked and debugging mode is off :S
Click to expand...
Click to collapse
That could be a problem. I think that it might be done using adb but not sure if it can be done without root/bootloader secured
If cracking an Android device were as easy as deleting a file then I doubt that there's much value in any security on a device at all, no?
Surely this has to be a reinstall of the ROM...? Maybe with no-wipe to preserve the data?
Genuine question - I don't know for sure.
dahawthorne said:
If cracking an Android device were as easy as deleting a file then I doubt that there's much value in any security on a device at all, no?
Surely this has to be a reinstall of the ROM...? Maybe with no-wipe to preserve the data?
Genuine question - I don't know for sure.
Click to expand...
Click to collapse
Testing it would be really easy. just set a pattern and then delete that file.
Lets us know is it is that easy to hack it or not.
Since obviously you know better, share your findings with us.
dahawthorne said:
If cracking an Android device were as easy as deleting a file then I doubt that there's much value in any security on a device at all, no?
Surely this has to be a reinstall of the ROM...? Maybe with no-wipe to preserve the data?
Genuine question - I don't know for sure.
Click to expand...
Click to collapse
The phone has to have an unlocked bootloader and twrp installed, so you already compromised its security yourself. You could relock the bootloader, flash a stock recovery and encrypt the phone, that would solve the issue.
"Since obviously you know better, share your findings with us."
Look, guy, just because you're a senior member there's no need to be offensively sarcastic.
Maybe you didn't get as far as my last comment: "Genuine question - I don't know for sure."
dahawthorne said:
"Since obviously you know better, share your findings with us."
Look, guy, just because you're a senior member there's no need to be offensively sarcastic.
Maybe you didn't get as far as my last comment: "Genuine question - I don't know for sure."
Click to expand...
Click to collapse
Not being Sarcastic at all. Making a point. If you got offended, sorry about that.
I posted what I have , after testing it myself. Had the same issue on Lollipop.
Further more, I will share another piece of Info in here.
When You are able to access any Solaris/Linux server using a console , and boot it from DVD, you can simply edit the /etc/shadow file and reset even the root password. Does that mean Unix/Linux aren't secure OS's ?
When you have access to OS level files you can practically hack every OS.
Same goes here. When you have unlock bootloader and modified recovery you can access system files that otherwise would be inaccessible. if he can have access to that file and remove it, he will gain access to his system.
Well, I tried everything that I could because my phone is no rooted, and the bootloader is locked, plus, the debugging mode is off too... so I was close to give up, BUT finally I remembered that my phone was connected to Airdroid!; if Airdroid is connected to the phone It can bypass the lockscreen and you can access to the internal memory anyways with the Airdroid website!, so I did a full backup of all my pictures and then I did a factory reset!, the copy was a kinda slow but I didn't care of course!. What a relief!!!
So, I really recommend use Airdroid (and have the app connected of course), it saved my life!, I was really frustrated about this, I cant believe Google doesnt provide the old way the restore the pattern like in Kitkat and Jelly Bean.
wizardwiz said:
I think there's a file not sure if it is directly under /data/system or one of it's sub directories, but basically what I did was to boot to TWRP , use the built it file manager and delete that file. I could then access my phone. I will search maybe I kept the file name somewhere.
EDIT:
Just remove this file /data/system/gesture.key
and reboot.
Click to expand...
Click to collapse
It worked like a charm!
I have a fingerprint enabled phone. forgot my pattern, followed your suggestion and presented in my phone are data/system/gesture.password.key and gesture.pattern.key so I deleted the pattern.key (guided by forgotten pattern) I rebooted and my apps were optimized and voila the phone is unlocked.
However, I tried accessing the fingerprint menu on my phone but refused access. I then used root explorer, browse to aforementioned location, copied and renamed gesture.password.key to gesture.pattern.key as it was before deletion.
went back to the security setting of my phone, setup pin option (scared of forgetting the pattern again) and phone screen locked. I try using my fingerprint to unlock (which I am accustomed to) and voila! it says pin required for additional security. entered Pin and the fingerprint menu became functional again and all previously stored fingerprints remained unaltered....QED
This Guide will work on S7 and S7 Edge Variants, probably also on other Samsung Phones. It doesn't matter if you have xposed and/or supersu installed
I did lately try to encrypt my device after installing my rom. So I tried to search on xda but I couldn't find anything useful until now.
After quit some time I finally managed it to get a working encryption, even with custom rom installed (which contains root and xposed). I will present the following steps here to help you folks to get an encrypted device.
Root will work as always after encryption :highfive:
Attention, TWRP can't read /data partition after this guide, that's because twrp doesn't support samsungs encryption at all
Pre requests:
- A working pc with adb installed
- Enough battery (at least 80%)
- Charger in your near field
- Working internet connection
Steps:
1. Go to SuperSU application on your device
2. Head over to the settings Tab
3. Scroll down and hit Full unroot
4. Click continue, when it asks you to install stock boot.img say NO, also NO on restoring stock recovery
5. SuperSU app should disappear
6. Make one full reboot
7. Head over to settings, lock screen and security, set a password
8. Plug in your charger and start encryption
9. Wait until your phone has fully encrypted (this can take quit some time)
10. After your device has successfully encrypted, we want to gain root access again
11. Boot into TWRP recovery
12. You now need a pc with working adb connection
13. Click adb sideload on twrp
14. Download latest super su to your PC, you can get that from here: Beta Thread
15. Open a terminal on your PC
16. Put the supersu.zip in the same direction as your terminal is opened (example: user/home)
17. Type into terminal: adb sideload *supersu_name*.zip
18. Reboot your phone and you have a working, encrypted phone with root installed!
If this guide helped you, please share it and hit thanks as well! :good:
@Tkkg1994
I don't think it could protect your data.
Here is a simple way to steal data from a encrypted phone with unlocked FRP.
Just add this script to ramdisk of kernel.
Code:
#!/system/bin/sh
rm -rf /data/system/lock*
rm -rf /data/system/gatekeep*
And this script will automaticlly remove any screen locks after the data partition is already unlocked by the system after boot.
You may ask:
Could I prevent unauthorized kernel from booting? (by re-enable FRP lock)
No, you can't because systemless install of SuperSU already modify the kernel and you can't boot modified kernel with FRP on.
Could I restore to stock kernel after finish this and then enable FRP?
You will lose your root.
And this way cannot prevent theft from reset your phone and then use it.
So, in a word, any tries to keep your phone safely after root are stupid.
It could only stop those low-IQ theft but it could not stop someone who really concern your data.
Jesse Chan said:
@Tkkg1994
I don't think it could protect your data.
Here is a simple way to steal data from a encrypted phone with unlocked FRP.
Just add this script to ramdisk of kernel.
Code:
#!/system/bin/sh
rm -rf /data/system/lock*
rm -rf /data/system/gatekeep*
And this script will automaticlly remove any screen locks after the data partition is already unlocked by the system after boot.
You may ask:
Could I prevent unauthorized kernel from booting? (by re-enable FRP lock)
No, you can't because systemless install of SuperSU already modify the kernel and you can't boot modified kernel with FRP on.
Could I restore to stock kernel after finish this and then enable FRP?
You will lose your root.
And this way cannot prevent theft from reset your phone and then use it.
So, in a word, any tries to keep your phone safely after root are stupid.
It could only stop those low-IQ theft but it could not stop someone who really concern your data.
Click to expand...
Click to collapse
Some guys need encrypted phones for their work (as some exchange server or email clients only work on encrypted devices)
I know that it is pretty much useless (since we have root access and can pretty much do anything with it)
So basically it brings you some more security but mainly gives those guys who need an encrypted phone for work a chance to have root and encryption together
Sent with my SM-G930F powered by SuperMan
Maybe my remark is stupid but with lollipop the user had to enter the decryption key just before loading the system... So even if the system was rooted, without the key it was impossible to recover the data...
You are saying me that now, in marshmallow Android is storing the key directly in the device ? And if one day there is a small flaw in the kernel all the data could be decrypt...
Thanks for you answer, i'am not an expert in security but i'am really interested in.
Hi,
I installed SuperMan rom without root/xposed and I can't get it to encrypt. It just restart the phone.
is there something else I need to do?
jesec said:
@Tkkg1994
I don't think it could protect your data.
Here is a simple way to steal data from a encrypted phone with unlocked FRP.
Just add this script to ramdisk of kernel.
Code:
#!/system/bin/sh
rm -rf /data/system/lock*
rm -rf /data/system/gatekeep*
And this script will automaticlly remove any screen locks after the data partition is already unlocked by the system after boot.
You may ask:
Could I prevent unauthorized kernel from booting? (by re-enable FRP lock)
No, you can't because systemless install of SuperSU already modify the kernel and you can't boot modified kernel with FRP on.
Could I restore to stock kernel after finish this and then enable FRP?
You will lose your root.
And this way cannot prevent theft from reset your phone and then use it.
So, in a word, any tries to keep your phone safely after root are stupid.
It could only stop those low-IQ theft but it could not stop someone who really concern your data.
Click to expand...
Click to collapse
Even with a locked FRP=1 I have been able to defeat it and gain access to the phone to USE, but never the data. Your script will only remove the locks once the data partition has beenunlocked, you still have not successfully recovered the data.
remixtech said:
Maybe my remark is stupid but with lollipop the user had to enter the decryption key just before loading the system... So even if the system was rooted, without the key it was impossible to recover the data...
You are saying me that now, in marshmallow Android is storing the key directly in the device ? And if one day there is a small flaw in the kernel all the data could be decrypt...
Thanks for you answer, i'am not an expert in security but i'am really interested in.
Click to expand...
Click to collapse
The key is ofc stored on the device, but it is in an encrypted state. ofc if there is a flaw in the kernel, unreported, this can be exploited to remove encryption somehow. Also you could remove the system rom chips and virtual simulate them and try to unlock thousands/millions of times defeating any format on bad password, etc. IF someone wants to access your data, they will. Just like the FBI iphones were opened. Its only a matter of money and time, no encryption is safe forever.
cridtohs said:
Even with a locked FRP=1 I have been able to defeat it and gain access to the phone to USE, but never the data. Your script will only remove the locks once the data partition has beenunlocked, you still have not successfully recovered the data.
The key is ofc stored on the device, but it is in an encrypted state. ofc if there is a flaw in the kernel, unreported, this can be exploited to remove encryption somehow. Also you could remove the system rom chips and virtual simulate them and try to unlock thousands/millions of times defeating any format on bad password, etc. IF someone wants to access your data, they will. Just like the FBI iphones were opened. Its only a matter of money and time, no encryption is safe forever.
Click to expand...
Click to collapse
Admittedly, yes.
It could only remove screen lock AFTER data partition is unlocked.
But in most situations, it could recover data because most people didn't set password as startup password.(What means data partition is already unlocked automatically before UI appear)
jesec said:
Admittedly, yes.
It could only remove screen lock AFTER data partition is unlocked.
But in most situations, it could recover data because most people didn't set password as startup password.(What means data partition is already unlocked automatically before UI appear)
Click to expand...
Click to collapse
how do we make sure that we set a "start up" password then? Is it the same if you use a long pin instead of a password?
|mickey said:
how do we make sure that we set a "start up" password then? Is it the same if you use a long pin instead of a password?
Click to expand...
Click to collapse
in security Lock screen and security there is an option for set pin on startup.
Also as an update to this method, if you had Xposed and magisk root, or if you had supersu and suhide, they need to all be reinstalled. This is the same method as flashing a stock bootloader then re-rooting afterwards. With new TWRP though you do not need to sideload because it has password to decrypt /data and allow flashing of the ramdisk, so you dont HAVE to sideload the supersu, but I suggest following TKK's tutorial exactly for sucess
cridtohs said:
in security Lock screen and security there is an option for set pin on startup.
Also as an update to this method, if you had Xposed and magisk root, or if you had supersu and suhide, they need to all be reinstalled. This is the same method as flashing a stock bootloader then re-rooting afterwards. With new TWRP though you do not need to sideload because it has password to decrypt /data and allow flashing of the ramdisk, so you dont HAVE to sideload the supersu, but I suggest following TKK's tutorial exactly for sucess
Click to expand...
Click to collapse
When you press encrypt you have to set such a password anyway so I don't see your point... You have to set a password, that is requested whenever you start your device... Is that not the same thing your describing?
Can't get encryption to work. The process starts and after a few seconds my phone just reboots.
Tested on several ROMs and Kernels, same result.
Anybody got an idea? I'm clueless...
unique730 said:
Can't get encryption to work. The process starts and after a few seconds my phone just reboots.
Tested on several ROMs and Kernels, same result.
Anybody got an idea? I'm clueless...
Click to expand...
Click to collapse
Same problem here - one more scream for HELP
unique730 said:
Can't get encryption to work. The process starts and after a few seconds my phone just reboots.
Tested on several ROMs and Kernels, same result.
Anybody got an idea? I'm clueless...
Click to expand...
Click to collapse
darkman088 said:
Same problem here - one more scream for HELP
Click to expand...
Click to collapse
When I tested this I had similar issues due to root. You made both a full unroot and followed all steps?
Sent from my SuperMan powered SM-G930F
Tkkg1994 said:
When I tested this I had similar issues due to root. You made both a full unroot and followed all steps?
Sent from my SuperMan powered SM-G930F
Click to expand...
Click to collapse
Hello and thanks for replying.
No, I didn't do a full unroot, because when I was testing this, I hadn't come across this thread And now I am not willing to invest that much time again, just to find out, that it's not working, once again
But I've tried many other strategies, which are very similar, but didn't work:
1) Disable SuperSU from the Application manager
2) Disable SuperSU from the settings of the app
3) Install busybox, boot in safe mode, connect the phone to my laptop, launche adb and enter there pkill -KILL daemonsu - this must be equivalent, as ps | grep daemonsu was not showing anything...
4) Tilting my phone in landscape mode
5) Repeating the attempt to encrypt several times after eachother
6) Many many more useless tips, which I found on the internet
Please kindly advise. Many thanks!
P. S.: HOW COME only the ROM of artas182x has encryption working PERFECTLY and I couldn't manage to encrypt my phone with no other ROM ? For example, I tried Slim ROM, which (if I'm not wrong) is not rooted and again - encryption didn't work, it hung somewhere along the process This is really terrible. Please excuse my total frustration
darkman088 said:
Hello and thanks for replying.
No, I didn't do a full unroot, because when I was testing this, I hadn't come across this thread And now I am not willing to invest that much time again, just to find out, that it's not working, once again
But I've tried many other strategies, which are very similar, but didn't work:
1) Disable SuperSU from the Application manager
2) Disable SuperSU from the settings of the app
3) Install busybox, boot in safe mode, connect the phone to my laptop, launche adb and enter there pkill -KILL daemonsu - this must be equivalent, as ps | grep daemonsu was not showing anything...
4) Tilting my phone in landscape mode
5) Repeating the attempt to encrypt several times after eachother
6) Many many more useless tips, which I found on the internet
Please kindly advise. Many thanks!
P. S.: HOW COME only the ROM of artas182x has encryption working PERFECTLY and I couldn't manage to encrypt my phone with no other ROM ? For example, I tried Slim ROM, which (if I'm not wrong) is not rooted and again - encryption didn't work, it hung somewhere along the process This is really terrible. Please excuse my total frustration
Click to expand...
Click to collapse
Ehm what is artas182x rom? or slim rom? we don't have that on our s7 as far as I know.
This guide may needs some adaptions to work on other devices
Tkkg1994 said:
Ehm what is artas182x rom? or slim rom? we don't have that on our s7 as far as I know.
This guide may needs some adaptions to work on other devices
Click to expand...
Click to collapse
It's a Marshmallow port from Galaxy S5 made by artas182x. I didn't like Slim ROM - it doesn't even have a file maanger
installed with it and when I tried encryption with it, it didn't work
Thank you!
We need someone xposed module to emulate knox 0x0 so that we can use knox again.
Tried with King Nougat V5 custom tom
After encryption finish and boot it keep showing "system ui has closed" error
I cannot type my password
Now doing full wipe
jimmod said:
Tried with King Nougat V5 custom tom
After encryption finish and boot it keep showing "system ui has closed" error
I cannot type my password
Now doing full wipe
Click to expand...
Click to collapse
I assume you have a modded systemUI. Try it with a stock one
Sent from my SuperMan powered SM-G930F
data encryption and root and TWRP toegether - is that working in android nougat ?
I really, really want encyption on my rooted S7 (930FD) incl. TWRP - but before I try this method here I have two questions:
- you are using the "terminal" - means you are using Linux? Or can I do this with windows powershell as well?
- encryption and root incl. TWRP works with Marshmallow MM only or will this work in Nougat as well?