Related
Long story short, I'm writing an app that needs to edit a value in the database:
Code:
/data/data/com.motorola.android.providers.settings/databases/settings.db
I know this can be done, I just can't figure out how to do it, even after many days of searching, posting, reading bad information and trying code samples from people who obviously never tested what they posted because none of them have worked. The one common thread is that everything I read suggests this will only work on a rooted phone where su permissions can be obtained. That's fine, and I have been told I need to do this first:
Code:
Process p = Runtime.getRuntime().exec("su");
Ok so now what? How do I use that "p" object to open and edit the database? For simplicity, I don't want to use any "helper classes" for database access. I just want to do something like this:
Code:
myDB = this.openOrCreateDatabase("/data/data/com.motorola.android.providers.settings/databases/settings.db", MODE_PRIVATE, null);
myDB.execSQL("CREATE TABLE IF NOT EXISTS test_table (test_column VARCHAR);");
myDB.execSQL("INSERT INTO test_table (test_column) VALUES ('test_value');");
Any help would be GREATLY appreciated.
Unfortunately, 'su' only grants permissions for shell scripts and command-line executables, NOT to the application calling 'su'.
I wrote an app a long time ago that added "unknown sources" by a similar method. Believe me, I spent a long time on this problem and ended up just writing a ARM executable to do the work and called it in a shell with 'su -c ...'.
Thanks. Tell me, with apps like sqlite editor that can open and edit any db on the device, how are they doing it?
SixHouse said:
Thanks. Tell me, with apps like sqlite editor that can open and edit any db on the device, how are they doing it?
Click to expand...
Click to collapse
I'm not familiar with it, but if I had to guess, I'd bet it uses the sqlite3 command line utility to do the actual database work and fires it off with su.
Gene Poole said:
I'm not familiar with it, but if I had to guess, I'd bet it uses the sqlite3 command line utility to do the actual database work and fires it off with su.
Click to expand...
Click to collapse
That could be. Do you know where I can find that command line utility?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to General
Did you look here: http://developer.android.com/reference/android/database/sqlite/SQLiteDatabase.html#OPEN_READWRITE
I assume you did, but that is all I have.
I'm asking my question here, because in "Android Q&A" I didn't get any response (maybe it's too "hacking-related").
So, here it is: I want to ask you how to get real path of installed application. It would be awesome to get database of Applications Settings (i guess there are paths to each installed application). And I don't need general answers (like "they're installed in /system/app or /data/app") - I need to know where EXACTLY Android look for SPECIFIC installed app - a path to it.
In terminal type:
pm list packages -f
Disclaimer - this is your vehicle you are messing with. If you are not comfortable with potentially permanently damaging the head unit, stop here.
Now for the good stuff.
Credit where credit is due: this method relies on the recent "dirtycow" exploit. I used the POC Android exploit code located here:
https://github.com/timwr/CVE-2016-5195
This exploit in simple terms takes advantage of a Linux kernel bug that allows a (small) file to be "overwritten", when a user only has read access to that file. It doesn't actually modify filesystem contents, but any application that reads the file after the exploit is used will read the "new", post-exploit contents instead of the original.
The scripts attached use the dirtycow binary to overwrite the "/system/etc/factory_reset.sh" shell script with a nefarious version. This script is executed when you perform a factory reset operation through the settings menu, and gets executed as the root user .
The nefarious script is quite simple - it just calls another script that is uploaded and performs a reboot. The second script mounts the /system partition as R/W, then copies over an su binary and sets appropriate permissions, then syncs and mounts read only again.
Please note that the attached "rootme.sh" script is intended to be run from a Linux machine - if I get the time (or enough donations), or if someone else cares to, it can be ported over to a Windows batch file easily enough.
Updated the attached zip to include a Windows batch file.
Steps:
Download the attached zip file
Extract to a machine capable of connecting to your Pilot over ADB
Modify "rootme.sh" (*nix) or "rootme.bat" (Windows) to use the correct IP
- Change the "172.16.1.217" lines to reflect the correct IP for your Pilot
Execute "rootme.sh" (*nix) or "rootme.bat"
- ./rootme.sh should do it for *nix
- for Windows, open a command prompt, navigate to "rootme.bat" location and type "rootme.bat"
- Watch output for completion
Perform factory reset operation
- Note - should the exploit function correctly, this step should NOT perform any factory reset operations. However, you should fully expect everything to be reset if the exploit failed or some other problem occurred when attempting to use a nefarious factory_reset.sh script.
After the Pilot reboots, you should be able to get a shell over ADB as normal, except now issuing an "su" command will drop you to root!
Update - thanks to purespin figuring out the signature mechanisms, we can now install apps! I've attached OneClick.zip, which contains a series of scripts to automate the rooting & app installation process.
That said, be careful, use these at your own risk, etc.
Extract zip file to some folder then open up a command prompt in that folder. Also drop the APKs you wish to install to that folder.
Type OnceClickInstall.bat [YourHeadUnitIP] [APKToInstall.apk]
The script will root your device if it's not already, then go ahead and perform steps necessary to install the APK (one reboot required if already rooted).
This basically performs the steps described in purespin's post to get a signature of the APK, download and modify the whitelist XML file, upload it back, reboot, then install the APK.
There's one prompt in the script that asks you too look things over - pay attention here, if any issues crop up at this point damage can be avoided, continuing in a bad state will have undefined results.
Updated the scripts to back up the white list on each run to /data/local/tmp/whitelist-(timestamp).xml.
Updated to handle APKs with more than one signature.
Edit: As suggested by wpg_moe, a Git Hub project has been set up here:
https://github.com/jersacct/2016PilotOneClick.git
Changes & suggestions are encouraged and welcomed, but this is a part time hobby project for me, so expect movement to be "lumpy", as I'm mostly only able to work on this during the weekends.
would this work on a 2016 civic android headunit? should be the same concept for it?
This is GREAT news!!! We will start to test it on a 2016/Civic/Touring. It reminds of of the hacking a linksys firmware via tftp.
sheryip said:
would this work on a 2016 civic android headunit? should be the same concept for it?
Click to expand...
Click to collapse
I don't have a Civic to test with, but I would imagine Honda uses the same factory reset mechanism on both models.
The included scripts are pretty straightforward - if you care to crack them open you'll see the operations they perform pretty plainly. I think the absolute worst you could suffer if you attempt this is that you factory reset your head unit. Remember your favorite radio stations if you decide to give it a shot.
Yes, I am able to root the 2016 Pilot using the method provided by jersacct. It is super easy and strait-forward!
Now the question is what is next I have been working as programmer for the last 20 years but I don't have much knowledge of Android hacking. What's the starting point?
I'd say step 2 is to get the system info from a Ridgeline or a '17 pilot when they come out so we can try to put Android Auto or Car Play on the 16 models. Navigation would be nice but with AA/CP, you wouldn't need it.
Yep, this is just a first step. We still have to work around the white list service Honda put in place that's preventing installation of other APKs. I have not been successful in replacing the ApplistUpdate.apk with a modified version or replacing /data/system/whitelist.xml with a modified version. In either case the service is still preventing installation of new APKs.
I have a couple of workaround theories I'm working on - tracking down and modifying the service's source to always allow APK installation (effectively disabling the white list check), using the service's own interface to add APKs to the white list (much like S_Mike has done for the EU versions), stripping out or disabling the service entirely.
I think it would be much easier to get APKs installed than porting Android Auto or Car Play over. I would be much happy if we can achieve what they have done on EU versions.
jersacct said:
Yep, this is just a first step. We still have to work around the white list service Honda put in place that's preventing installation of other APKs. I have not been successful in replacing the ApplistUpdate.apk with a modified version or replacing /data/system/whitelist.xml with a modified version. In either case the service is still preventing installation of new APKs.
Click to expand...
Click to collapse
Any summary on how S_Mike did that (using the service's own interface to add APKs to the white list)? If not, I might spend some time to loop through the 139-page thread after work
jersacct said:
I have a couple of workaround theories I'm working on - tracking down and modifying the service's source to always allow APK installation (effectively disabling the white list check), using the service's own interface to add APKs to the white list (much like S_Mike has done for the EU versions), stripping out or disabling the service entirely.
Click to expand...
Click to collapse
I have a pilot 2016. But i dont have a Linux machine. So how can i use this. Even if i use this, if i will not have access to install apks then what is the use. I am a bit confused. I am also a developer and have been rooting my phones to install custom roms, but that was all with the guides that i found on the internet. Didn't try any thing fancy.
ammarbukhari said:
I have a pilot 2016. But i dont have a Linux machine. So how can i use this.
Click to expand...
Click to collapse
I've updated the attachment to include a Windows batch file, and updated the instructions.
Rooting the device with this method doesn't mean you can unlock all the Android goodies we're hoping for. It will, however, help a person so inclined to defeat the Honda installation restrictions.
There is no zip file
jersacct said:
I've updated the attachment to include a Windows batch file, and updated the instructions.
Rooting the device with this method doesn't mean you can unlock all the Android goodies we're hoping for. It will, however, help a person so inclined to defeat the Honda installation restrictions.
Click to expand...
Click to collapse
Thanks, have you had any luck installing an apk? That's what I'm looking to do on my Ridgeline.
Sent from my Nexus 6P using Tapatalk
ammarbukhari said:
There is no zip file
Click to expand...
Click to collapse
Sorry, corrected.
enyce9 said:
Thanks, have you had any luck installing an apk? That's what I'm looking to do on my Ridgeline.
Click to expand...
Click to collapse
Not yet, still working on this.
The system doesn't just check the white list. It checks the certs as well. If it's isn't sign by the developer for Honda the package installer won't install the apk.
Guys, you probably have to change the signature of the APK in the list from that code to "PREINSTALL", without the "". I have a 2015 Honda HR-V and that's the way we can install apps on our head unit. Some people had problem to install apps after updating Honda applications, because it changed "PREINSTALL" to the app signature. After a factory reset, they got the PREINSTALL again for "HondaAppCenter_A1.apk". So, try removing the signature code to PREINSTALL for some APK and use that APK name to install the app.
maecar said:
Guys, you probably have to change the signature of the APK in the list from that code to "PREINSTALL", without the "". I have a 2015 Honda HR-V and that's the way we can install apps on our head unit. Some people had problem to install apps after updating Honda applications, because it changed "PREINSTALL" to the app signature. After a factory reset, they got the PREINSTALL again for "HondaAppCenter_A1.apk". So, try removing the signature code to PREINSTALL for some APK and use that APK name to install the app.
Click to expand...
Click to collapse
I think the protection mechanisms in this version are entirely different. There are no "process_controls.list" or "allowed_installations.list" files present in the entire filesystem, nor does a grep across the entire filesystem return any results for "HondaAppCenter". These tell me that the protection mechanisms are not the same as previous or EU versions.
I've attached what I believe to be a component of the replacement mechanisms, an XML file describing full app names, sometimes signatures, and fields describing permissions. Any edits to this file don't seem to be regarded, so I'm still digging in to the core services that make up the white list mechanism.
Did you update whitelist.xml file directly or update the whitelist.xml file in ApplistUpdate.apk?
What a coincidence this is, as I heard about the Dirty Cow exploit just the other day and spent time trying to root my 64 bit Samsung smartphone to no avail. I did hear that it works on 32 bit android platforms and how about this for a case in point.
Jersacct, thanks for making this available to the community! I can understand that the first hurdle is getting the system to stop blocking / removing non-whitelisted apps and it sounds like you are just getting to this point now. Keep up the good work and please let us know if there are any minor details that you need worked out that can be delegated to the community, i.e. testing, troubleshooting or research.
Looking forward to having more capabilities with my 2016 Honda Pilot!
purespin said:
Did you update whitelist.xml file directly or update the whitelist.xml file in ApplistUpdate.apk?
Click to expand...
Click to collapse
I've attempted both approaches, with no luck. It may be that my ApplistUpdate.apk replacement was flawed somehow, so I'm not sure there. Because you modify the zipped whitelist.xml in the APK, you also have to resign the APK before installation, Android won't reinstall an app with different signatures without uninstalling original, and because it's a system app it won't let you uninstall.....blah blah I deleted the original (after backing up) and replaced it with modified version, still no positive result. I attempted to add eu.chainfire.supersu (picked at random, could be anything) to the list of allowed apps in these cases but still couldn't get it installed.
I think my next approach will be to edit the system services (in /system/framework/services.(.jar,.odex)) and see if I can disable all whitelist checks.
Now that root is available, it's only a matter of time before someone gets around Honda's restrictions.
Hi together,
does anyone having an idea how could i get the APK(Source code) from the app "com.huawei.iconnect" without Root Access? (Or does anyone having root and likely to share it?)
I would like to dig deeper in what this app is actually doing. Huawei did not yet give an appropiate answer
( Realted Topic if anyone is interested why i am asking: https://forum.xda-developers.com/t/...e-huawei-system-app-p20.4298153/post-85341835 )
houdang said:
Hi together,
does anyone having an idea how could i get the APK(Source code) from the app "com.huawei.iconnect" without Root Access? (Or does anyone having root and likely to share it?)
I would like to dig deeper in what this app is actually doing. Huawei did not yet give an appropiate answer
( Realted Topic if anyone is interested why i am asking: https://forum.xda-developers.com/t/...e-huawei-system-app-p20.4298153/post-85341835 )
Click to expand...
Click to collapse
I use fx file explorer on my tv and i used the feature to easily get the APK from the app.
Or you can use pretty much any apk extractor app that is there on the web to complete your task.
System apps r read-only i think idk if it works for you but it did for me
@houdang
You decompile the app by an online-decompiler like this one
APK Decompilers - Online Android APK Decompiler
Decompile Android APK files online ✅. We will decompile your Android apk for free so you can get access to the Java source code and other resources
www.apkdecompilers.com
Yeah, of crs i know how to decompile an APK, but where is this App located? I don't find that app nor don't i know where i can get the APK from.
App is called "com.huawei.iconnect"
You can query an APK's path via ADB
Code:
adb devices
adb shell "pm path <PACKAGE_NAME>"
In your other thread you mentioned you have deinstalled "com.huawei.iconnect".
Hence it sholud be obvious you can't find it no longer on phone.
Naaa i tried it to find it before uninstalling
But that's a helpful command, didn't know that.
I used the adb shell to deactivate/deinstall.
I gonna give it a try, Thanks !!
Yup guys, i found it, couldn't copy directly but through adb i was able to get it.
The online decompiler just gave me one Java file looking really weird. I will try another decompiler and see if i can find something. That app looks strange .. Many XML/HTML files.. nearly no code - at least with that decoder mention in the beginning.
Thanks for the help!
Ongoing discussion with HUAWEI about this app, see my another thread
Huawei - excessive mobile data usage (huawei system app ?!! ) - P20
Hello together, actually till now i was a silent reader and never had any big issues, but the topic i have since Saturday giving me question marks all over and i would kindly ask if any of you guys have any (even litte) ideas-- I'm using a...
forum.xda-developers.com
Recovering WhatsApp messages from Android phone without root
I did this on 19-20 November 2021
My phone is a stock Huawei P20 Pro CLT-L09 up to date with all Android/EMUI/app updates, connected to Windows 10 PC by USB.
This worked and I have good verifiable and complete data even though I am opted in to the multi-device beta, with the caveat that most viewing tools are not (yet) updated to understand the new database structure that it uses.
If you already have a crypt14 encrypted WhatsApp message database, this will recover the keyfile to allow decryption too - key from phone tested against my crypt14 database I downloaded from the Google Drive backup.
I used this method rather than exporting chats due to the 10,000/40,000 message limits on chat exports with/without media. Also that I didn't really want to export each chat individually.
Tools used on Windows 10:
GitHub - p4r4d0x86/WhatsApp-Key-DB-Extractor: Allows WhatsApp users to extract their cipher key and databases on non-rooted Android devices.
Allows WhatsApp users to extract their cipher key and databases on non-rooted Android devices. - GitHub - p4r4d0x86/WhatsApp-Key-DB-Extractor: Allows WhatsApp users to extract their cipher key and ...
github.com
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
https://aapks.com/apk/whatsapp/version/7518022/ if this link dies, you need an APK of WhatsApp of an old enough version. This is v2.11.431 and worked for me.
https://github.com/B16f00t/whapa/ (I actually put this in a Linux VM, with an additional sudo apt install python3-tk required to get that running)
The WhaGoDri tab in Whapa works brilliantly for recovering a Google Drive backup of your database (if you use 2FA, set an app-specific password for this tool) - as of October 2021, this now downloads a msgstore.db.crypt14 encrypted format. All the media associated with it is still unencrypted and downloads just fine. Personally I ran this first to have a clean data set to work from, and it's by far the easiest way to get the media. If you don't do this, then copy the media off the phone manually.
Starting out:
I would suggest opting out of the WhatsApp multi-device beta if you're currently in. I didn't - but if you do, then your final output should be better supported by existing tools for reading WhatsApp chats such as https://andreas-mausch.de/whatsapp-viewer/.
I backed everything up to Google Drive manually and downloaded all files from that backup with Whapa. After that you will need to set WhatsApp on the phone to "Never" back up to Google Drive and press backup again to create the local backups needed - otherwise the tools will fail.
Put your phone into developer mode, enable Android debugging over USB, personally I set it to permit during charging too so if it's connected, it's debugging. Fewer points of failure. Install the Windows Android drivers.
Unzip the WhatsApp Key DB Extractor into a folder (I created one on the desktop)
Add the old version of WhatsApp to the tmp folder and call it LegacyWhatsApp.apk
Now I needed to EDIT the WhatsAppKeyDBExtract.ps1 script (I used this rather than the batch script, if you want to use the bat file you're on your own!)
Following line 91 (should be after "Install complete" of LegacyWhatsApp.apk and before "If ($sdkver -ge 23)") I added the following line:
Read-Host 'Please open WhatsApp now'
As to why I added this point to pause in the program - it seemed to work better than not opening WhatsApp - it allows Android to set permissions for the old app to work better in the next steps.
Now you're ready to start!
Right-click the WhatsAppKeyDBExtract.ps1 script and select Run.
It will unload and save out your newest version of WhatsApp, and load in the legacy version. Once you are prompted to open WhatsApp from the line we added above, open the newly-installed old version and allow it all permissions requested. Don't worry that it then crashes out.
Then press Enter in the Powershell window and let it complete.
Note this may all take quite a lot of time - my crypt14 database from Google Drive was about 250MB, the unencrypted database upwards of 500MB, and the transfer time was probably about 5 minutes. So don't worry if it doesn't look like it is doing a lot!
At this point you are done! Check the findings: in the extracted folder, you should have the three critical files
1. msgstore.db which is your unencrypted message database (if you want to sanity check this, use a tool like DB Broswer (SQLite) or just a text editor and look for readable text to show it is not encrypted)
2. wa.db which is needed to assign contact names to the messages
3. whatsapp.cryptkey - this last one will let you decrypt the crypt14 file we saved from Google Drive earlier using Whapa. This is usually the hard one to get without rooting the phone!
If the process goes wrong at any point you might have the phone in a weird state. Personally I found uninstalling the old version of WhatsApp (ensuring that the checkbox was set to KEEP the data on the phone), reinstalling the newest version from the Google Play Store, opening that and letting it reload the WhatsApp chat backup from the phone was sufficient to get me ready to start again with no data loss.
As I mentioned at the start. Current tools (WhatsApp Viewer and Whapa) don't cope with the changed database structure that the multi-device beta uses in the same files. It doesn't look too complex to work out which old fields correspond to new ones to modify the readers, but that is an exercise for another day...
Things that DIDN'T work:
https://github.com/EliteAndroidApps/WhatsApp-Key-DB-Extractor - too old and the java code throws an error on the version on Android, ultimately failing to recover anything useful
https://github.com/SimonGhoul/Manual-WhatsApp-Key-DB-Extractor - not that it doesn't work per se, just the more automated version above has fewer steps for a novice user to screw up with!
https://www.imyfone.com/transfer-backup-restore-whatsapp/ - failed to decrypt the Google Drive recovered version (and I wasn't wild about giving my Google account creds to a random Chinese company either), also failed on some sort of timeout when recovering data through USB.
KingoRoot (both PC-based or APK directly) - doesn't support a P20 Pro CLT-L09 on latest version of Android, so no root for me that way
TWRP rooting - this will wipe the phone entirely and I was not convinced I'd get my data back from Google Drive! So I didn't try this
https://mobiletrans.wondershare.com/ - actually, technically speaking this works perfectly (as long as you follow the instructions *exactly* and are very patient). But I didn't like the proprietary interface and clunky chat export mechanism, nor the having-to-pay-for-it part
Things I haven't tried:
Importing anything to iOS. I'm making a clean start on my new phone!
Questions / comments / support:
Honestly I just documented this as it worked for me on this date with the current versions of stuff, I couldn't find any other instructions that worked without modification. I don't hack around with WhatsApp and phones for fun or for a living, I just wanted a readable backup to go back to as I'm switching to iOS. So... I probably won't check this again, but I hope it helps provide a data point and links/instructions for something that works.
Thank you @lightbrigade for this helpful article. I got the message store decrypted and could see message through Whatsapp viewer and SQLite browser. But I'm not able to locate deleted message in either of those tools. Do you know which table contains deleted messages by any chance?
Thanks, this was the closest I got after hours of trying to export my chats.
I successfully got my database backup using Whapa (crypt14 encrypted)
as well as the key using db extractor.
I also did a manual backup of my database (also crypt14 encrypted)
Unfortunately, msgstore.db in the "extracted" folder is still encrypted after using db extractor.
I tried decoding crypt14 databases using Whatsapp Viewer, but I got the error message:
"Decryption failed. Error during unzipping (inflate). In 99% this means you tried to use an invalid key."
Why is this key invalid? My P30 pro can't be rooted with EMUI 10...
TheReini said:
Thanks, this was the closest I got after hours of trying to export my chats.
I successfully got my database backup using Whapa (crypt14 encrypted)
as well as the key using db extractor.
I also did a manual backup of my database (also crypt14 encrypted)
Unfortunately, msgstore.db in the "extracted" folder is still encrypted after using db extractor.
I tried decoding crypt14 databases using Whatsapp Viewer, but I got the error message:
"Decryption failed. Error during unzipping (inflate). In 99% this means you tried to use an invalid key."
Why is this key invalid? My P30 pro can't be rooted with EMUI 10...
Click to expand...
Click to collapse
I have the excact same issue. Decrypting with "WhatsApp-Key-DB-Extractor" works, but i only decrypts my current messages. I need to decrypt an old G-Dirve backup. The "whatsapp.cryptkey" created by the Tool does not work with with "WhatsApp Viewer" or "whapa".
I have a rooted device, but i cannot find the key file on my device, so i cannot test it this way.
Oh my god, I finally managed to decrypt my chats...
I'm not sure if my approach works in your case, but maybe it's worth a try...
#No root needed
#No risk of losing current Chats
Instructions:
1) Make a cloud backup of your chats.
2) Download Bluestacks and allow root access
3) Install Whatsapp on Bluestacks and load your backup
4) Create a local backup in Whatsapp on Bluestacks
5) Download a root file explorer (I used "Root Browser") and copy the key file from
/data/data/com.whatsapp/files
to some path on bluestacks sdcard
6) Open the preinstalled file explorer (Media-Manager) and export both the keyfile from 5) and your database from /sdcard/Whatsapp/Databases to your local Windows machine.
(Key file can also be extracted on the phone itself (without Bluestacks Emulator) using
WhatsApp-Key-DB-Extractor-master)
7) Clone the following repository to your local machine and decrypt your database
GitHub - ElDavoo/wa-crypt-tools: Decrypts WhatsApp .crypt12, .crypt14 and .crypt15 files.
Decrypts WhatsApp .crypt12, .crypt14 and .crypt15 files. - GitHub - ElDavoo/wa-crypt-tools: Decrypts WhatsApp .crypt12, .crypt14 and .crypt15 files.
github.com
Failed tries:
- Whapa always exported a 0 byte database
- WhatSoup Web Scraper kept crashing after some minutes on Windows, as well as Linux VMware
- WhatsApp Viewer threw an Error: unzipping (inflate), invalid key
!!! Important !!!
Windows Text Editor doesn't display the decrypted database in a readable way.
You have to open it in some kind of SQL software or test it online here:
SQL Online Compiler - Next gen SQL Editor
SQL OnLine - Next gen SQL Editor: SQLite, MariaDB / MySQL, PostgreSQL, MS SQL Server. User-friendly interface for data science. No registration for start, No DownLoad, No Install. Online test SQL script. Online Open/Save SQLite file. Online view all table DB. Fiddle link SQL text and DB file...
sqliteonline.com
Hey everyone, I ended up using this app:
GitHub - p4r4d0x86/WhatsApp-Key-DB-Extractor: Allows WhatsApp users to extract their cipher key and databases on non-rooted Android devices.
Allows WhatsApp users to extract their cipher key and databases on non-rooted Android devices. - GitHub - p4r4d0x86/WhatsApp-Key-DB-Extractor: Allows WhatsApp users to extract their cipher key and ...
github.com
But it didnt work and ended up deleting my local backups... is there anyway to recover it?
Google drive back up is a week old.
Samsung s22 non-rooted phone
Any help would be appreciated.
Doesn't work for accounts that transferred accounts to another phone.
Key file gets deleted from old phone if you use whatsapp on another device.
Hello folks,
I am getting a
Performing Streamed Install
adb: failed to install tmp\LegacyWhatsApp.apk: Failure [-26: Package com.whatsapp new target SDK 19 doesn't support runtime permissions but the old target SDK 31 does.]
Click to expand...
Click to collapse
on WhatsApp-Key-DB-Extractor-master with Android 12 (Realme RMX3393).
Using the APK mentioned in the inital post as legacy APK.
Any ideas how to cirumvent that or what else to try?
By the way Whapa to downlowd the Drive data worked like a charm but I am unable to get my hands on the key.
The people that achieved the extraction could they state on what OS the ewxtraction was successful?
I could get relatively easily down to an Android version 10 ... ;-)
hi, sorry but couldnt understand if this process would solve my problem, so im asking; i made a backup for my Whatsapp to Drive then made a factory reset to my phone, installed Whatsapp, before i restored my real back, i did a new backup and i realized that, my real backup gone, only one i could restore is the new one which is nothing inside, is there a way to get older backup in Drive, or do you guys think can i get those files on my internal storage via any data recovery software? Thanks in advance!