Related
http://forum.xda-developers.com/showthread.php?t=1409304
trying to follow those instructions to change from swipe to password lock, but I can't find lockscreen.password_type in the database. In short, here's my problem:
http://android.stackexchange.com/questions/51180/using-adb-to-change-the-screen-lock
I'm trying to change swipe lock to password lock without using the UI. The database is supposed to contain the salt value which I can somehow (how?) use to hash up a default password, and (in theory) overwrite or create the password.key file, thereby changing the password. On my password-protected device, I can neither see lockscreen.password_type nor lockscreen.password_salt in the settings.db:secure table (or in the entire db for that matter). I'm wondering if it's been moved, or if something is wrong with my system.
bump for fast moving board?
Guys,
my OP3 is bootloader unlocked, rooted and encryption switched off.
Standard system was OOS 3.1.2. I installed the update to 3.2.1 via TWRP zip and found some bugs, so I decided to use the [ROM] [6.0.1] Unofficial CyanogenMod 13
from Grarak. Did a full wipe installed and all is ok. Now comes the strange thing:
I wanted to restore the original backup and it worked. When I rebooted, the system asks me for the SIM card sim and then the system says:
"for the new start of the device you need to enter the pin"
The ony pin I ever used for the card and not knowingly for the device doesn't work.
Neitehr 0000 nor 1234 works. Which means I can't restore the nand backup.
Does anyone have an idea what this behaviour is and how to work around?
That is normal before doing a Nandroid u have to delete the pin, there exist a way around it deleting ur pin keys in trwp, its listed on this site somewhere
Bradl79 said:
That is normal before doing a Nandroid u have to delete the pin, there exist a way around it deleting ur pin keys in trwp, its listed on this site somewhere
Click to expand...
Click to collapse
found the thread. but unfortunately didn't find the corresponding workaround. can you remember where this was?
OK found it in the OnePlus 3 Forum.
This works:
HOW TO FIX
------------------------
Simply boot into TWRP and enter your PIN (if you've set one) to decrypt the stroage. If you don't have TWRP (for whatever reason) you can do so via ADB too but ONLY if you've connected your phone to your PC beforehand and also accepted it's fingerprint on the phone itself.
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Go into Settings > Security and set your preferred unlock method again, Android will ask you if you want to set a boot-time code too. Select whatever you want here, it's a nice security addition but can be annoying sometimes.
Enjoy your phone again!
ihobahobby said:
found the thread. but unfortunately didn't find the corresponding workaround. can you remember where this was?
OK found it in the OnePlus 3 Forum.
This works:
HOW TO FIX
------------------------
Simply boot into TWRP and enter your PIN (if you've set one) to decrypt the stroage. If you don't have TWRP (for whatever reason) you can do so via ADB too but ONLY if you've connected your phone to your PC beforehand and also accepted it's fingerprint on the phone itself.
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Go into Settings > Security and set your preferred unlock method again, Android will ask you if you want to set a boot-time code too. Select whatever you want here, it's a nice security addition but can be annoying sometimes.
Enjoy your phone again!
Click to expand...
Click to collapse
Thanks for sharing I wasn't aware and had to wipe my phone twice.
ihobahobby said:
found the thread. but unfortunately didn't find the corresponding workaround. can you remember where this was?
OK found it in the OnePlus 3 Forum.
This works:
HOW TO FIX
------------------------
Simply boot into TWRP and enter your PIN (if you've set one) to decrypt the stroage. If you don't have TWRP (for whatever reason) you can do so via ADB too but ONLY if you've connected your phone to your PC beforehand and also accepted it's fingerprint on the phone itself.
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Go into Settings > Security and set your preferred unlock method again, Android will ask you if you want to set a boot-time code too. Select whatever you want here, it's a nice security addition but can be annoying sometimes.
Enjoy your phone again!
Click to expand...
Click to collapse
Where in twrp do I have to enter the pincode ? After I choose to restore ? Is that all or do have to delete the files also when I have twrp ?
magnum73 said:
Where in twrp do I have to enter the pincode ? After I choose to restore ? Is that all or do have to delete the files also when I have twrp ?
Click to expand...
Click to collapse
Good question. I did also look for the pin entry, but haven't found. Was also not necessary maybe because I had switched off encyption earlier. I just deleted the namend files (which were for me only the locksetting files).
After that rebooted to system and everything works fine. Once you did that, better create a new backup without the fingerprint installed and you're safe next time.
Can u back it up and then do a restore from ur nandroid and restore files, I use multi fingerprints and have my gf on there also I hate resetting things up
I know this is what I need to do. I just can't find these files anywhere. Guess I have to start from scratch.
?
ihobahobby said:
found the thread. but unfortunately didn't find the corresponding workaround. can you remember where this was?
OK found it in the OnePlus 3 Forum.
This works:
HOW TO FIX
------------------------
Simply boot into TWRP and enter your PIN (if you've set one) to decrypt the stroage. If you don't have TWRP (for whatever reason) you can do so via ADB too but ONLY if you've connected your phone to your PC beforehand and also accepted it's fingerprint on the phone itself.
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Go into Settings > Security and set your preferred unlock method again, Android will ask you if you want to set a boot-time code too. Select whatever you want here, it's a nice security addition but can be annoying sometimes.
Enjoy your phone again!
Click to expand...
Click to collapse
THANK YOU SO MUCH! I just got stuck between ROMs and used my nandroid backup but could not get past the lock screen.
Hello there,
Until I bricked it, I used a Huawei Media Pad M2 10.0 LTE (M2-A01L)
I edited build.prop in order to change the hostname permanently by
adding net.hostname = NEWHOSTNAME
I couldn't save the file, so I copied it, edited it and wrote it back to /system using File Explorer and root permission.
(I used KingRoot)
Afterwards the device didn't boot anymore.
I am able to reach the recovery and fastboot mode.
After I tried a factory reset, i tried changing the permissions of build.prop by
way of connecting the tablet to my laptop and using adb shell.
The device cannot be found.
I successfully used adb to unlock my bootloader so the driver is correctly installed
but since I did the factory reset, I guess the usb debugging mode is no longer active.
Installing a stock ROM by copying it to the external sd card in the dload folder proved ineffective
as well. I tried two ROMs but every time, the installation failed.
I would be very grateful for any suggestions since I didn't find a thread that could rescue me and my device!
Well, I tried a previously used firmware and tried to install it via sd card using another pc and now it worked.
Perhaps it was a permission issue since the image was write protected.
Well, I'm glad it worked
Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
Code:
adb devices
iii) now use the command
Code:
adb reboot-bootloader
In fastboot use this command to unlock bootloader
Code:
fastboot oem unlock
Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Code:
expdb
nvdata
nvram
proinfo
protect1
protect2
secro
8) Copy these files in some place where it is safe ( I have copied it to Internal Storage in a folder named PartitionsBackup)..
9) Next, go back to root folder again, and open data/nvram/md/NVRAM/NVD_IMEI and copy the MP0B_001 file to internal storage. Do Not copy this file in the same place as the previous files, but remember where you have copied this file.
These are all the partitions that store the device's IMEI .
10) After copying everything mentioned, Reboot to recovery and flash the desired Custom Rom.
11) Make sure the rom is rooted, and again install FX File Explorer from play store, enable root access as above.
Do Not Forget To Backup Everything Before Doing Anything!
12) Now select the files that you have copied in internal storage (Assuming PartitionsBackup). And copy those files. ( Note: Do Not Copy the MP0B_001 file!)
13) Now open root folder, go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder and paste all the files you have copied, and if asked select Merge/Overwrite files.
14) Reboot.
15) Now go back to internal storage, copy the MP0B_001 file where you have saved it. Go back to root folder and open data/nvram/md/NVRAM/NVD_IMEI and copy the file, select Merge/Overwrite. Now long press the file and select Security, update permissions as Read, Write for both root and radio. Dis-select everything else.
16) Reboot aand Done! Voila ! You should get back the IMEI for your device :victory:
I know its a long post, but it works for Custom ROMs.!
Hope it helps!
Hit Thanks If you feel it works! :highfive:
can you please help me on step 13 because every time i reboot the device the by-name folder contents reset to the original value. my by-name folder backup is 72 mb while when i look in the folder after i reboot it is only 170 bytes
---------- Post added at 06:12 AM ---------- Previous post was at 06:07 AM ----------
also when i wait for a while after rebooting for like 4-6 hours when i looked at my baseband and imei it is not unknown anymore
and my sim is restored but when i reboot again the baseband value and imei is set back to unknown. this happened even before im not following your solution. can it be a hardware issue? would really appreciate any help thx
Cyteezy said:
can you please help me on step 13 because every time i reboot the device the by-name folder contents reset to the original value. my by-name folder backup is 72 mb while when i look in the folder after i reboot it is only 170 bytes
---------- Post added at 06:12 AM ---------- Previous post was at 06:07 AM ----------
also when i wait for a while after rebooting for like 4-6 hours when i looked at my baseband and imei it is not unknown anymore
and my sim is restored but when i reboot again the baseband value and imei is set back to unknown. this happened even before im not following your solution. can it be a hardware issue? would really appreciate any help thx
Click to expand...
Click to collapse
I didn't get you. Do not backup the whole by-name folder. Just copy the files mentioned above. And when you go into the custom ROM, just restore the files copied in the same by-name folder.
No. It might not be a hardware problem.
PraneethMv said:
Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
Code:
adb devices
iii) now use the command
Code:
adb reboot-bootloader
In fastboot use this command to unlock bootloader
Code:
fastboot oem unlock
Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Code:
expdb
nvdata
nvram
proinfo
protect1
protect2
secro
8) Copy these files in some place where it is safe ( I have copied it to Internal Storage in a folder named PartitionsBackup)..
9) Next, go back to root folder again, and open data/nvram/md/NVRAM/NVD_IMEI and copy the MP0B_001 file to internal storage. Do Not copy this file in the same place as the previous files, but remember where you have copied this file.
These are all the partitions that store the device's IMEI .
10) After copying everything mentioned, Reboot to recovery and flash the desired Custom Rom.
11) Make sure the rom is rooted, and again install FX File Explorer from play store, enable root access as above.
Do Not Forget To Backup Everything Before Doing Anything!
12) Now select the files that you have copied in internal storage (Assuming PartitionsBackup). And copy those files. ( Note: Do Not Copy the MP0B_001 file!)
13) Now open root folder, go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder and paste all the files you have copied, and if asked select Merge/Overwrite files.
14) Reboot.
15) Now go back to internal storage, copy the MP0B_001 file where you have saved it. Go back to root folder and open data/nvram/md/NVRAM/NVD_IMEI and copy the file, select Merge/Overwrite. Now long press the file and select Security, update permissions as Read, Write for both root and radio. Dis-select everything else.
16) Reboot aand Done! Voila ! You should get back the IMEI for your device :victory:
I know its a long post, but it works for Custom ROMs.!
Hope it helps!
Hit Thanks If you feel it works! :highfive:
Click to expand...
Click to collapse
Can anyone help me in restoring IMEI in stock ROM?
While flashing using SN writer or maui meta tool it says "Have been in meta mode. Long press power button to normal reboot". After that nothing. It boots back and I still see the INVALID IMEI message.
MisledMew said:
Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
iii) now use the command
In fastboot use this command to unlock bootloader Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Can anyone help me in restoring IMEI in stock ROM?
While flashing using SN writer or maui meta tool it says "Have been in meta mode. Long press power button to normal reboot". After that nothing. It boots back and I still see the INVALID IMEI message.
Click to expand...
Click to collapse
SN write tool can be a little complicated to do. I personally prefer Maui Meta 3G. You can search for guides on SN write tool. There are many....
Facing problem with maui meta 3g
On my mobile it shows its in "Have been in meta mode. Long press power button to normal reboot".
it won't work ahead .... some error like kernel checksum and no permission grant type.. rather i installed drivers of mediatek its not working...
plz help out
Ni$hant said:
On my mobile it shows its in "Have been in meta mode. Long press power button to normal reboot".
it won't work ahead .... some error like kernel checksum and no permission grant type.. rather i installed drivers of mediatek its not working...
plz help out
Click to expand...
Click to collapse
Do you have all drivers installed correctly? ADB, VCOM, USB Drivers?
Also, That message screen is Meta Mode. From that screen only you can do the IMEI process.
Note: This Only works for stock rom. Use this guide.
https://forum.hovatek.com/thread-12328.html
For custom Roms, use my guide.
Device: Lenovo A2016a40 (MY6735M) also known as Lenovo vibe b
Android Version - 6.0 Marshmallow
I can't find any folder named 'nvram' on 'data' directory of root folder
Hello dev's! Unfortunately, in January, my brother passed away, and I have been tasked with trying to get into his phone and recover any important images really to pass along to his wife and daughter. Needless to say, I don't know his PIN code - and I am down to 2 guesses before the phone is wiped. So here I am.
Pardon my lack of technical language here but my brother did install Team Win Recovery Project 3.1.1-0 so I have been able to get to "recovery mode". Unfortunately, his partition is encrypted and I have been unable to guess that password either.
Because his drive is encrypted, I can't get into /data to remove any .key files. I have successfully been able to figure out how to sideload zip files via ADB that are supposed to bypass the PIN screen but I have had no luck. The google "find my phone" method is not working probably because the phone isn't connecting to a network.
I have read through an alpha security post about a malicious charger hack but I don't see where to download that tool.
So - does anyone know of any possible application or ZIP file I can sideload that will either help remove the decryption password or completely and successfully bypass the PIN?
Can I update TWRP to a newer version in hopes that the encryption is removed?
Any help is appreciated!
FWIW, my brother was on these forms as Colomonster - and I know that he loved tinkering with his phone daily.
There's no efficient way of breaking the data partition if it's encrypted, sorry.
Any old version of twrp might do the trick and then in /data/system folder delete these files ( if they are there )
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
@catsruul I figured this would be the case but it does look like I get inifinite guesses, so there’s always that
@cpt.macp thanks for this tip! Can I downgrade via sideloading? I’ll have to look up a tutorial.. thanks!
You said any important photos correct?
https://support.google.com/accounts/troubleshooter/6357590?hl=en
I assume that your brother used Google Photos and any photos he took were most likely backed up to that. You can talk to Google about retrieving said data, you will need to prove things of course though. You will need to get a court order issued, that is if it is even approved, and everything else required should be on that page. Best of luck! Sorry to say but if the /data is encrypted you are pretty much screwed, although TWRP should decrypt in when it enters recovery so idk. That webpage is your best shot imo.
thanks @ZVNexus for the tip. I do have access to his Google account but because my brother was a super sleuth, he didn't have his images automatically upload to his photo drive. the photos that are there are few and from 2015
With access to his account, I do see his "activity", which I am not even sure he knew was being tracked (oh Google!) and I see that he used things like
Code:
Used com.android.gallery3d
and
Code:
Used org.cyanogenmod.snap
both of which look like photo apps.
you mentioned that TWRP should decrypt when I enter recovery.. what do you mean by that? if it is encrypted then it should always ask for a password right?
I wonder if this app is available anywhere for download and use.
HTML:
https://alephsecurity.com/2017/03/26/oneplus3t-adb-charger/
Lonoshea said:
thanks @ZVNexus for the tip. I do have access to his Google account but because my brother was a super sleuth, he didn't have his images automatically upload to his photo drive. the photos that are there are few and from 2015
With access to his account, I do see his "activity", which I am not even sure he knew was being tracked (oh Google!) and I see that he used things like
Code:
Used com.android.gallery3d
and
Code:
Used org.cyanogenmod.snap
both of which look like photo apps.
you mentioned that TWRP should decrypt when I enter recovery.. what do you mean by that? if it is encrypted then it should always ask for a password right?
I wonder if this app is available anywhere for download and use.
HTML:
https://alephsecurity.com/2017/03/26/oneplus3t-adb-charger/
Click to expand...
Click to collapse
I meant that even if the chip was encrypted TWRP should have let you touch the data partition. My phone is also encrypted but TWRP allows me to touch those partitions. Strange. Hopefully others can help.
Lonoshea said:
Hello dev's! Unfortunately, in January, my brother passed away, and I have been tasked with trying to get into his phone and recover any important images really to pass along to his wife and daughter. Needless to say, I don't know his PIN code - and I am down to 2 guesses before the phone is wiped. So here I am.
Pardon my lack of technical language here but my brother did install Team Win Recovery Project 3.1.1-0 so I have been able to get to "recovery mode". Unfortunately, his partition is encrypted and I have been unable to guess that password either.
Because his drive is encrypted, I can't get into /data to remove any .key files. I have successfully been able to figure out how to sideload zip files via ADB that are supposed to bypass the PIN screen but I have had no luck. The google "find my phone" method is not working probably because the phone isn't connecting to a network.
I have read through an alpha security post about a malicious charger hack but I don't see where to download that tool.
So - does anyone know of any possible application or ZIP file I can sideload that will either help remove the decryption password or completely and successfully bypass the PIN?
Can I update TWRP to a newer version in hopes that the encryption is removed?
Any help is appreciated!
Click to expand...
Click to collapse
I'm confused: if the partition is encrypted, you will generally be asked for a password during the boot process. If you're unable to enter the correct password (which AFAIK has unlimited tries), the phone simply won't boot. So you will never arrive at the lockscreen where you're supposed to enter the PIN (which offers a number of tries before wiping). With an encrypted partition, entering the recovery will prompt you for the same password you're supposed to enter during the boot process. Again, unlimited tries. As long as you're unable to do that the partitions will be 'invisible'. You can still wipe/partition them and that will remove the encryption as well as all of your data. But it seems the device you're working on works differently?
Either way: in order to gain access, you will need to either know the PIN directly (if the phone boots without a boot password) or gain access to the encrypted partition through TWRP, allowing you to remove the files responsible for the PIN lock. I'm sorry for your loss, but if it would work in any other way it simply wouldn't be secure for any Android user out there who is using encryption. Even google shouldn't be able to decrypt the phone, though it's theoretically possible they do have some kind of backdoor.
At this point, your best bet is probably trying to brute force the partition password. That would probably take a very long time, but I'm sure there's tools and organizations specializing in that sort of work.