Database Info

Device isn't working properly after wiping...

So I have a problem with my Nexus 5. Yesterday I tried all kinds of different Lollipop roms and at the end of the day I sticked to Cataclysm. I liked it and my phone was all set up but I noticed there were a lot of unnecessary folders on my internal storage and a nested 0 folder (0 inside /0). I didn't like that so I thought about making a nandroid backup, storing it on my computer (together with my music etc.), wiping everything and restoring it by using TWRP and then eventually putting my music back.
So after I stored a backup on my computer, I started my device into recovery mode and chose the option 'advanced wipe'. Usually I would do a lot of research for everything I do but in this case I was a bit lazy to do that, I tried digging into the search results of Google concerning wiping but I gave up after some unsatisfying results. So I checked every box in the list, including data and system and went through with the wiping. So because my storage was completely wiped I didn't have a 'WRTP/BACKUPS' folder anymore. I made a backup from the stuff I had (which was only a few mb's) so I would have that folder again (otherwise I wouldn't be possible to locate my nandroid backup). I wanted to transfer my nandroid from my computer to my phone by connecting it through USB but for some reason the Nexus 5 didn't show up on my PC when it was booted in recovery (this sometimes happens for some reason)
I managed to do it by using 'adb push Cataclysm folder' in cmd. I went into recovery and restored my backup. My phone booted and I thought everything was as it should be. The wallpaper was black but that was logical because my internal storage was wiped, including my custom wallpaper. But then I noticed something strange, my status bar disappeared, sames goes for my navigation bar. I really have no idea what happened because I've restored nandroid backups before and everything went fine.
So then I put a clean version of Cataclysm on my phone and for some reason it asks me to insert a SIM-card into my device while it has one. I skipped that step and then it asked for my home Wi-Fi and I chose mine, then it checked the connection way longer than it would normally do. After I was done with all the steps my homepage entered my screen and guess what, my status bar and also my navigation bar were absent. It was like my cell phone was in immersive mode all the time. Then I tried flashing the KitKat factory image by going into recovery with my phone and opening 'flash-all.bat' on my PC but then it said '< waiting for devices >' while I enabled USB debugging... I opened cmd and typed 'adb decives' and mine showed up, so it was connected (although it now says 'unauthorized' when my phone is normally booted).
Then I flashed clean Cataclysm again and it again said I had to insert my SIM-card and it then again checked the connection with the Wi-Fi for a couple of minutes. When I was done with the installation I tried replacing the wallpaper with one from Lollipop but it didn't work although there was a preview available. There was again no status bar and navigation bar. I then opened chrome and went to this website and now I'm typing this on my Nexus 5 which has a permanent immersive mode now.
So I don't have much in my internal storage anymore, only a TWRP folder with backups, nothing more, not even a 0 folder if I'm not wrong. There's something wrong with my mobile connection and definitely something going on with my navigation bar and status bar. I hope anyone could help me with this because this is really frustrating becausr I tried to fix it for the last couple of hours, unfortunately without any result...
EDIT: I forgot to mention that when I was trying to figure out how to send the nandroid without being able to access my internal storage via my computer, I booted in recovery, went to 'advanced' and then to 'adb sideload' and tried that because I saw it somewhere on the internet. I somehow believe this contributed to the problem I have.
EDIT2: Now, when I try to power off my phone by holding the power button, it reboots the device instead, what's going on... And as I said, I have a black screen as wallpaper for some reason and I can't change this, but if I open my weather widget, the widget window shows up with my chosen wallpaper on the background, what kind of sorcery is this?
EDIT3: I wanted to download a terminal emulator from Google Play to do this but I couldn't get to 100% so I thought there was something wrong with the app on my device. I googled the apk and I wanted to download it from Zippyshare and when I clicked on the button 'download now', the phone showed the message 'no SD card', so I guess that's the culprit of all of this?
TL;DR My phone is acting really weird (no status or navigation bar, phone reboots instead of asking whether I want to have it shut down when I hold the power button, the wallpaper being strange, SIM-card isn't being recognised) after I wiped data and system and actually everything...

Reboot to bootmanager , flash a factory image , wipe , start over . Something must have gotten corrupted in your nandroid backup.
Regarding ADB not working , you also need to authorize the pc you are working from . You will get a prompt on your phone when connecting . If you dont , go to developer setting , wipe ADB credentials , reconnect the phone.
Also , adb push works fine for single files but it sometimes borks when you are pushing big/many files.
Edit : I hope you didn't wipe EFS as well ( though AFAIK TWRP doesn't wipe it on a advanced wipe) . If you did it's time to return it to stock and send it to LG/Google

Niflheimer said:
Reboot to bootmanager , flash a factory image , wipe , start over . Something must have gotten corrupted in your nandroid backup.
Regarding ADB not working , you also need to authorize the pc you are working from . You will get a prompt on your phone when connecting . If you dont , go to developer setting , wipe ADB credentials , reconnect the phone.
Also , adb push works fine for single files but it sometimes borks when you are pushing big/many files.
Edit : I hope you didn't wipe EFS as well ( though AFAIK TWRP doesn't wipe it on a advanced wipe) . If you did it's time to return it to stock and send it to LG/Google
Click to expand...
Click to collapse
Thank you for reading my huge explanation. After hours of searching and trying a lot of things with my device I figured out how to fix it. Do you remember I said that when I tried to flash the factory image with 'flash-all.bat' that it responded with '< waiting for devices >' ? Well, after reinstalling the drivers countless times and trying to find the culprit I realised I was trying to flash it with TWRP being open, and not the bootloader... So after I was aware of that I finally managed to put stock Lollipop on my phone, then I wiped everything and flashed Cataclysm. It felt pretty satisfying to have a working phone again, it's a pity I had to start from scratch but on the other side, I now how a phone without any rubbish.
Regarding adb push, if I would like to ever push a rom or a big file onto my phone in case I would ever have a similar annoyance, what do you recommend me to do it with?
And what is EFS exactly and what happens if I would ever wipe that? Thank in advance!

Regarding ADB push / twrp MTP mode you jst need to remember not to try and upload the entire content of a sdcard backup or > 3-4 gigs. Big files rarely missbehave , but I screwed up my SD permissions when trying to restore my sdcard ( thousands of files and about 14 gb total).
EFS is a secure partition that stores your GSM/network id and profile - IMEI and so on. AFAIK it's pretty hard to erase but it is possible if you play around with format/repartition commands. Just follow the guides and instructions on this forum and it should be fine.
Corrupted or erased EFS = no network connectivity besides WiFi . And since tampering with it is illegal in some countries the only way to fix it is by RMA/warranty.
I'm glad you've fixed it - I'm not surprised it was a simple mistake , I've been there myself ( tried for an hour to flash a factory image unsuccessfully only to realize I had my phone plugged in a USB3 socket ) .
Don't forget to make a nandroid now that you are set up with your fav. ROM - it will come in handy sometime.

Niflheimer said:
Regarding ADB push / twrp MTP mode you jst need to remember not to try and upload the entire content of a sdcard backup or > 3-4 gigs. Big files rarely missbehave , but I screwed up my SD permissions when trying to restore my sdcard ( thousands of files and about 14 gb total).
EFS is a secure partition that stores your GSM/network id and profile - IMEI and so on. AFAIK it's pretty hard to erase but it is possible if you play around with format/repartition commands. Just follow the guides and instructions on this forum and it should be fine.
Corrupted or erased EFS = no network connectivity besides WiFi . And since tampering with it is illegal in some countries the only way to fix it is by RMA/warranty.
I'm glad you've fixed it - I'm not surprised it was a simple mistake , I've been there myself ( tried for an hour to flash a factory image unsuccessfully only to realize I had my phone plugged in a USB3 socket ) .
Don't forget to make a nandroid now that you are set up with your fav. ROM - it will come in handy sometime.
Click to expand...
Click to collapse
I'll definitely make a nandroid, just in case. Thanks for the help and the clarification!

Try wiping your bum more thoroughly

HELP Forgot Pattern in Android 6.0

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

Pixel is stuck at "Pixel is starting"

My bootloader-unlocked Google Pixel runs Android Pie and it uses file-based encryption. Both system partitions are unmodified.
In an effort to get TWRP to successfully decrypt my Pixel's encrypted data, I performed a combination of:
Renaming these files (i.e., appending .bak to their names):
Code:
/data/system/gatekeeper.password.key
/data/system/gatekeeper.pattern.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
Copying the files back to their original names.
Setting and removing a lock pattern/password/PIN.
Now, my Pixel does not move past the "Pixel is starting" page. I can access Settings, but I have no access to my applications and files. How do I fix this so that I can get it to move past "Pixel is starting"?

I once ran into this issue, it has something to do with fingerprint and encryption, somehow it unlocks but it won't decrypt.
The only solution I've found is to wipe the device. Since you can power on the device, I suggest you to backup what you can with adb or from twrp, and do an advanced wipe, with even "format data" enabled (warning: you lose also /sdcard files), then reflash the stock factory image from fastboot.
This should remove the corrupted lock files and set it up like new.

TENN3R said:
I once ran into this issue, it has something to do with fingerprint and encryption, somehow it unlocks but it won't decrypt.
The only solution I've found is to wipe the device. Since you can power on the device, I suggest you to backup what you can with adb or from twrp, and do an advanced wipe, with even "format data" enabled (warning: you lose also /sdcard files), then reflash the stock factory image from fastboot.
This should remove the corrupted lock files and set it up like new.
Click to expand...
Click to collapse
Hang on. Did you skim my post? I'm trying to get it to decrypt or, if the decryption is not the problem, just get past "Pixel is starting" and get to my things on it. Wiping it won't fix that!
Fingerprints are not used to decrypt the device.

Bump.

Anyone else? What could be the cause of this? Would it give an error message if it couldn't find the right files?

TENN3R said:
I once ran into this issue, it has something to do with fingerprint and encryption, somehow it unlocks but it won't decrypt.
The only solution I've found is to wipe the device. Since you can power on the device, I suggest you to backup what you can with adb or from twrp, and do an advanced wipe, with even "format data" enabled (warning: you lose also /sdcard files), then reflash the stock factory image from fastboot.
This should remove the corrupted lock files and set it up like new.
Click to expand...
Click to collapse
Are you there?

TENN3R said:
I once ran into this issue, it has something to do with fingerprint and encryption, somehow it unlocks but it won't decrypt.
The only solution I've found is to wipe the device. Since you can power on the device, I suggest you to backup what you can with adb or from twrp, and do an advanced wipe, with even "format data" enabled (warning: you lose also /sdcard files), then reflash the stock factory image from fastboot.
This should remove the corrupted lock files and set it up like new.
Click to expand...
Click to collapse
Were you able to recover your data?

Bump.

Unfortunately not. I just wiped the device, maybe there is some way but I really don't know. Wiped and setup again

Bump.

Bump.

Someone please help.

Master Melab said:
Someone please help.
Click to expand...
Click to collapse
Wipe your phone maybe.

what is wrong with you all you needed to do to decrypt in twrp is disable your lock screen security, none of this other bull**** lmao.

Please help.

SnowFuhrer said:
Wipe your phone maybe.
Click to expand...
Click to collapse
That won't achieve the desired result as I'm trying to recover my data.

sudoxd said:
what is wrong with you all you needed to do to decrypt in twrp is disable your lock screen security, none of this other bull**** lmao.
Click to expand...
Click to collapse
First, I got into this mess by trying to get that to work. Second, how is this a solution?

Master Melab said:
First, I got into this mess by trying to get that to work. Second, how is this a solution?
Click to expand...
Click to collapse
it is a solution, unless there is something wrong with your phone which is caused by an entirely different issue, to access your data in twrp all you needed to do was disable your lock screen security

Unfortunately I don't think there's a way you can do it. The issue the OP is facing is that the system is unable to decrypt your user data at all, regardless of whether or not you are in TWRP or Stock Android, Stock Recovery, etc.
Trying to read between the lines on the AOSP File-based encryption https://source.android.com/security/encryption, your data is always encrypted - regardless of whether or not you have some security set (pin, password, etc). It's just a matter of whether or not the pin etc is part of the metadata used in the decryption. When you altered the security files that stored the information, you lost the ability to decrypt (probably the files have additional information that is passed with your pin to unlock the encryption keys). Removal of the files needed to be done within the system by removing the security, not by removing the files whilst it is encrypted. (Sorry if this isn't exactly what happened, it's hard to tell the exact sequence of events from the OP, i.e. whether or not it was all done in system, and when reboots were done.)
I did something like this before, and got the same result. Sorry but you'll have to rely upon the latest Google backups you had...

NZedPred said:
Trying to read between the lines on the AOSP File-based encryption https://source.android.com/security/encryption
Click to expand...
Click to collapse
I've tried, but I am unable to follow all of it.
NZedPred said:
your data is always encrypted - regardless of whether or not you have some security set (pin, password, etc). It's just a matter of whether or not the pin etc is part of the metadata used in the decryption.
Click to expand...
Click to collapse
I'm aware of that.
NZedPred said:
When you altered the security files that stored the information, you lost the ability to decrypt (probably the files have additional information that is passed with your pin to unlock the encryption keys). Removal of the files needed to be done within the system by removing the security, not by removing the files whilst it is encrypted. (Sorry if this isn't exactly what happened, it's hard to tell the exact sequence of events from the OP, i.e. whether or not it was all done in system, and when reboots were done.)
Click to expand...
Click to collapse
The files I touched have nothing to do with decryption, only unlocking.
NZedPred said:
I did something like this before, and got the same result.
Click to expand...
Click to collapse
Could you please explain what you did?

Asking for help Blu G90

Forgive if I put this in the wrong section.
Q: my father recently passed away and I'm trying to recover some data that is on his phone. I physically have his phone. Blu G90. Is there a way to bypass or disable the native pin lock?
Usb debug not enabled. Default set to charge only for pc.
Pretty sure wipe at 15 is set so can't brute force.
I have a couple of forensics applications that can see it when it goes to bootloader but then they crash as soon as I try to grab an image or mount /system.
I'm literally begging for any assistance I can get.
Thanks in advance

AntiMatter2112 said:
Forgive if I put this in the wrong section.
Q: my father recently passed away and I'm trying to recover some data that is on his phone. I physically have his phone. Blu G90. Is there a way to bypass or disable the native pin lock?
Usb debug not enabled. Default set to charge only for pc.
Pretty sure wipe at 15 is set so can't brute force.
I have a couple of forensics applications that can see it when it goes to bootloader but then they crash as soon as I try to grab an image or mount /system.
I'm literally begging for any assistance I can get.
Thanks in advance
Click to expand...
Click to collapse
Since the device is locked (bootloader locked) so the permissions to change/modifiy/copy something into phone cannot obtain the internal storage files.
Only unlocking bootloader and for it is need format phone as internal storage so the device erasing all files. The pin lock can remove with adb-fastboot commands or TWRP.
But again, with locked bootloader, without chance to have internal files.

DragonPitbull said:
Since the device is locked (bootloader locked) so the permissions to change/modifiy/copy something into phone cannot obtain the internal storage files.
Only unlocking bootloader and for it is need format phone as internal storage so the device erasing all files. The pin lock can remove with adb-fastboot commands or TWRP.
But again, with locked bootloader, without chance to have internal files.
Click to expand...
Click to collapse
thanks for the reply. i was afraid of that. even after factory reset, if i root, theres a chance at partial data recovery? or is it completely gone?

AntiMatter2112 said:
thanks for the reply. i was afraid of that. even after factory reset, if i root, theres a chance at partial data recovery? or is it completely gone?
Click to expand...
Click to collapse
You can try an official unlock. Maybe it can have some result or maybe not. Trying is the attitude.
Write Google support and try to legally show some death certificate and supporting documents over your father's phone number. Write down the situation and wait for some response from them.
The only practical way would be to try a backup of the internal partition. But it depends on your knowledge with Smart Phone Flash Tool. Also you must know how to "cut" the file in the right parts.
There would be a very small possibility of restoring the internal files with a backup of userdata or in its entirety (called ROM_1).
The next step would be to unlock the phone, install TWRP and restore the file made from userdata.
Perhaps at that point you have a 1% chance of removing the PIN and booting the device without a password.
But this should only be done if Google gives you a negative answer.
Another way is with carrier company. But I think help in nothing.
Understand that despite having a userdata file with PIN, there is encryption involved and that is what makes the whole process difficult.
I know the TWRP made for BLU G90 has active decryption. But I don't know how it will behave with a userdata file made with stock ROM.
Unfortunately there is no guarantee that files like photos, docs, etc can be in userdata as this refers to internal storage. Already userdata is in ROOT storage.
So even if there is an application or software capable of restoring files, there is also the possibility that it will not be successful or have corrupted files. This will depend on your choice and risk carrying out the process.

DragonPitbull said:
You can try an official unlock. Maybe it can have some result or maybe not. Trying is the attitude.
Write Google support and try to legally show some death certificate and supporting documents over your father's phone number. Write down the situation and wait for some response from them.
The only practical way would be to try a backup of the internal partition. But it depends on your knowledge with Smart Phone Flash Tool. Also you must know how to "cut" the file in the right parts.
There would be a very small possibility of restoring the internal files with a backup of userdata or in its entirety (called ROM_1).
The next step would be to unlock the phone, install TWRP and restore the file made from userdata.
Perhaps at that point you have a 1% chance of removing the PIN and booting the device without a password.
But this should only be done if Google gives you a negative answer.
Another way is with carrier company. But I think help in nothing.
Understand that despite having a userdata file with PIN, there is encryption involved and that is what makes the whole process difficult.
I know the TWRP made for BLU G90 has active decryption. But I don't know how it will behave with a userdata file made with stock ROM.
Unfortunately there is no guarantee that files like photos, docs, etc can be in userdata as this refers to internal storage. Already userdata is in ROOT storage.
So even if there is an application or software capable of restoring files, there is also the possibility that it will not be successful or have corrupted files. This will depend on your choice and risk carrying out the process.
Click to expand...
Click to collapse
Thanks for the reply. Google was pretty useless. They told me to contact Blu and Blu said to contact Google. I successfully hard reset and root. Went through setup to try a restore from his drive backup and it wanted the unlock pin in order to restore. Google was again quite useless. Since this is a matter if his estate i served Google with a notice of preservation on the backup, since it expires pretty soon. I'm going to try next to roll back to an older version, before the unlock pin requirement to restore Google backup. Grabbed a cellebrite image earlier so I can mess around with it later tonight. I'm hoping that because of the unlock requirement that the pin file is still there after reset.

Bypassing lock on old ZTE FLASH N9500

Found my old phone from high school. Turned it on and looks like I never factory reset it, and I would love to see all of the photos and messages I left behind, however I can not for the life of me remember the pin I used. Browsed around and tried to delete the gesture.key using ADB but permission is denied, and I wasn't able to find a custom recovery tool for this specific phone either. Anyone have any possible solutions? Thank you

Shiiiba said:
Found my old phone from high school. Turned it on and looks like I never factory reset it, and I would love to see all of the photos and messages I left behind, however I can not for the life of me remember the pin I used. Browsed around and tried to delete the gesture.key using ADB but permission is denied, and I wasn't able to find a custom recovery tool for this specific phone either. Anyone have any possible solutions? Thank you
Click to expand...
Click to collapse
If you cannot remember the PIN, you're most likely going to have to factory reset. There is no way around this that I know of, unfortunately.

you can just dump the whole userdata partition off flash memory in EDL mode, loop mount partition image from linux and modify it's content (like deleting locksettings.db)

Shiiiba said:
Hi there, thanks for responding to my forum post. I can give it a shot, however I was wondering if you would be willing to help me with attempting this. Im familiar with root and devices but I’ve not had any experiencing with dumps or tools like the one you provided on github. I have an extra ZTE Flash to test on but some extra insight would be nice. I also had two questions:
1: can I just take the locksettings.db and somehow retrieve my pin from it instead of modifying and dumping?
2: if I do end up having to dump, will the environment be the same (IE logged in apps, id like to see my message history in apps that are there)
Thanks so much, and sorry for disturbing.
Click to expand...
Click to collapse
you need a firehose programmer matching your SoC and OEM. the tool comes with collection (loaders) for quite few devices, just give it a try.
1. might be possible with password.key
2. yes by just deleting locksettings.db nothing is changed