So as a little side project I've tasked myself to review the security features and potential risks to data being stored within the Android OS and I've been using my Captivate as the test rat. Since pretty much everyone with an android device uses Gmail I wanted to focus first on the Gmail app. I know that information for many apps are stored under the /data/data/[app package]/databases directory structure in an SQL Lite *.db file.
That being said, I wanted to inquire with everyone here about being able to access the /data/data directory and all info there-in WITHOUT having to root the device. Im sure there might be some on that but Im just trying to be thorough in my review...any potential thief would obviously just instantly root and delve right in afterward the data but what other potential ways are there to get into that directory, if there are any?
I've been playing around with ADB and from what I can tell that is not a viable path. The only thing I could think of is somehow tricking the ADB daemon into thinking my phone is a development phone which would allow ADB to run as root but haven't found that to be possible.
So in any case, just looking for insight from the more experienced folk as to other avenues of attack against the user data beyond the obvious root method. Thanks very much for any help!
You can run adb shell as root if the phone is in clockworkmod recovery - but if someones going to the trouble of dropping a clockwork update.zip could just as well and as easy drop a root update.zip on the phone.
If someone physically gets a hold of your phone anything tied the google account/s on the phone would have to be considered compromised - as these phones are so easy to root anyway.
I just thought of another thing, if someone were to get a hold of your phone and have access to a computer with odin they could pretty quickly do a system dump (grab every file off your phone) return where you could find it without you ever knowing they got it.
dayv said:
I just thought of another thing, if someone were to get a hold of your phone and have access to a computer with odin they could pretty quickly do a system dump (grab every file off your phone) return where you could find it without you ever knowing they got it.
Click to expand...
Click to collapse
you dont need odin. adb will do it too
Pirateghost said:
you dont need odin. adb will do it too
Click to expand...
Click to collapse
Can you do a system dump in adb without root?
dayv said:
Can you do a system dump in adb without root?
Click to expand...
Click to collapse
yes
adb pull /system
Pirateghost said:
yes
adb pull /system
Click to expand...
Click to collapse
Learn new things every day.
I like this phone allot, but there just is no way to secure it against someone physically gets their hands on it.
Pirateghost said:
yes
adb pull /system
Click to expand...
Click to collapse
Yep thats actually very easy to do however it doesn't contain any critical private data really. I looked through the directories and while there is some interesting information that can be gleaned (e.g. the generic APN configs and other hardware information) there isn't any actual private stuff such as Gmail data, authentication info for apps, etc. That is all contained within the /data/data directory from what I understand.
You CAN get a list of all the packages on the device through /SYSTEM as well as all the APK's of the installed apps but otherwise not much I've found to be worrisome.
I'll have to check out Odin and see what that can offer from a non-root perspective.
Pirateghost said:
yes
adb pull /system
Click to expand...
Click to collapse
But, that is why you don't leave USB debug on all the time - and why there is a warning when you do turn it on.
PIN or pattern lock keep prying eyes out, and protect your phone from ADB, but not if you leave USB debug on. But, like other hardware, if someone has physical access and enough time, they can get to your data.
So now that Im rooted, is there an easy way to write up a script to copy all files in the /data/data and whatever other folders I decide onto my PC?
Related
I just got my captivate 1 month ago (first android). I rooted the phone and installed Cognition 2.3b6 right when i got it. I have never backed up the phone.
2 days ago the phone dropped from about 18 inches onto the bathroom floor. Cracking the interior of the screen. Origintally i could see the top half, the touchscreen hardly works. Now i can only see a faint blue color when i boot hte phone. It still works, i get alarms and feel it vibrate.
I understand that I might be able to do a nandroid backup (is it possible to do it blind?), but is that the correct thing to do? Will that change the deviceID of my replacement phone from AT&T (insurance replacement).
I would like to get the data backed up and transferred over asap so i can pack the old phone up and ship it off before the holidays.
Thank you guys!
adb pull /sdcard
Some one else might be able to help you with the specifics, but pull the /sdcard data from your phone.
From a phone
what?
I figured i need to probably copy it to the sd card. But from what i understand, some applications rely on DeviceID's and not the actual phone. Ergo, if you do a complete nandroid backup it will also copy over the DeviceID (from what i understand, correct me if i'm wrong).
Or is that something different than what you are suggesting?
Your data is stored in /sdcard. The external sdcard is /sdcard/external_sd for froyo, cant remember file path for 2.1. What else could you be wanting to transfer to the new phone?
From a phone
I've never done it before, I want to be able to transfer all data (ie, installed apps, cached notebooks for evernote, preferences, etc) to the other phone.
I have never done this before on an android phone and don't know the best way to tackle this using a cracked screen (can't even unlock the phone)
I think I can manage to do a nandroid backup ( http://www.youtube.com/watch?v=sEqbjUb4WxM ) but i'm concerned about the device id
Cassetti said:
I've never done it before, I want to be able to transfer all data (ie, installed apps, cached notebooks for evernote, preferences, etc) to the other phone.
I have never done this before on an android phone and don't know the best way to tackle this using a cracked screen (can't even unlock the phone)
I think I can manage to do a nandroid backup ( http://www.youtube.com/watch?v=sEqbjUb4WxM ) but i'm concerned about the device id
Click to expand...
Click to collapse
There are 2 way i can think of.
1- Like mentionned in prior post do a adb pull /sdcard
2- Boot into recovery and try to a backup from there blindly (following online pictures/video of the different menus and pressing the buttons accordingly).
I don't see the big deal about your deviceid. Many users have had a auto generated id with roms. It will be ported with the nandroid. Not sure just how wide spread the use of deviceid is used in apps.
Thanks I was really confused about the whole DeviceID thing. Figured it was best to play it safe.
I'll give it a try, i'm sure i can manage to do a nandroid backup on my phone
I'll keep you posted
There are ways of getting your device id back. First of all theres a market app that can backup the device id on your new phone and restore it back after you restore the backup http://www.appbrain.com/app/android-id-changer/adaptive.cogid Or you could search around the forums and/or google for ways of changind and backing up your device id, there are multiple ways of doing it. And don't forget about backing up your sdcard, like boborone said, do an adb pull /sdcard from the clockworkmod screen (adb works from recovery in case you didn't know).
Hell man, you can adb pull the whole phone if you want.
From a phone
Can you send the link to where i can find out how to do and adp full pull from the pc? The only instructions i'm seeing are for the android sdk (bit confused)
the sdk is downloaded to your pc, and then you run that command from a terminal/command prompt with the phone connected.
kmac1914 said:
the sdk is downloaded to your pc, and then you run that command from a terminal/command prompt with the phone connected.
Click to expand...
Click to collapse
Do i need to have left the phone in USB debugging mode? I believe 3 days before the accident, i turned off USB debugging on purpose (for file transfers)
Check out my Screencast video...It may help you here.
http://forum.xda-developers.com/showthread.php?t=877652
Cassetti said:
Do i need to have left the phone in USB debugging mode? I believe 3 days before the accident, i turned off USB debugging on purpose (for file transfers)
Click to expand...
Click to collapse
I believe you can use adb from recovery screen.
connexion2005 said:
Check out my Screencast video...It may help you here.
http://forum.xda-developers.com/showthread.php?t=877652
Click to expand...
Click to collapse
Thanks, the screencast helped, but i honestly think that 2 days before i did this, I turned off usb debugging (so i could use my phone as a hard drive)
I think that is why whenever i plug in my phone, it vibrates really hard and droid explorer doesn't find any devices. Suggestions?
Seeing as root has already been achieved, can someone please post a system dump of their Bionic please...
Thanks!
tell me how and i can help, i deleted the dam bloat at least some
I don't know what you consider "bloat", but just as long as you didn't delete any core Motorola files, connect via adb and issue the following commands:
adb shell
su
busybox tar czvf /sdcard/systemdump.tgz /system
exit
exit
adb pull /sdcard/systemdump.tgz
Click to expand...
Click to collapse
There's you go, a system dump.
If you can somehow get everything back to stock and just rooted, a complete system dump would be better...
jfgirard0423 said:
tell me how and i can help, i deleted the dam bloat at least some
Click to expand...
Click to collapse
did a system dump followed these instructions
The easiest way, I think, would be:
install the android SDK (developers.android.com)
start CMD
type in "cd c:\PATH_TO_YOUR_SDK\tools (<-- so there's a tools folder inside the sdk folder)
on your phone: Setting -> Applications -> Developer -> USB Debug Mode (dunno how its spelled correctly)
connect your phone with your pc
let windows find your phone
back to cmd console: adb pull /system
the full system dump shall be in YOUR_SDK_FOLDER\tools\system
but i go to my sdk folder / tools but there is no system folder ???? help
or at least tell me what file in there you need
I had made a backup of "My Accounts 2.3.4" before deleting and to my displeasure I realized it was tied into the actual Setup menu. I attempted to restore but it seems to be on an endless loop. Fortunately I had already finished all my account syncs but it would be nice to be able to fix this problem. Suggestions or am I SOL for the time being?
The app package "com.motorola.blur.setup"
Oh, by loop I meant Titanium Backup. Everything is working a ok. Just wondering if there was something I missed.
hey i am a total noob when it comes to the bionic coming from my dinc. what is the easiest way to delete the stock apps that come on my bionic that are taking up at least half of my internal memory. pretty pissed to get the phone home and find out i only have like seven or so gbs of memory on the phone so whats the easiest way to delete bloatware. help me out thanks a ton.
Try the commands I posted...
And unfortunately, I need everything in /system
Thanks!
jfgirard0423 said:
did a system dump followed these instructions
The easiest way, I think, would be:
install the android SDK (developers.android.com)
start CMD
type in "cd c:\PATH_TO_YOUR_SDK\tools (<-- so there's a tools folder inside the sdk folder)
on your phone: Setting -> Applications -> Developer -> USB Debug Mode (dunno how its spelled correctly)
connect your phone with your pc
let windows find your phone
back to cmd console: adb pull /system
the full system dump shall be in YOUR_SDK_FOLDER\tools\system
but i go to my sdk folder / tools but there is no system folder ???? help
or at least tell me what file in there you need
Click to expand...
Click to collapse
I thought P3droid did a system dump, but that might have been the pre-release BIONIC.
http://www.mydroidworld.com/forums/...id-bionic-system-dumps-partial.html#post99195
I pulled a system dump using the adb instructions.
I'm rooted and have installed a few root apps, but I haven't deleted any apps other than the golf game which did not require root to delete.
Here's the file, 228.5MB.
voc627 said:
I had made a backup of "My Accounts 2.3.4" before deleting and to my displeasure I realized it was tied into the actual Setup menu. I attempted to restore but it seems to be on an endless loop. Fortunately I had already finished all my account syncs but it would be nice to be able to fix this problem. Suggestions or am I SOL for the time being?
The app package "com.motorola.blur.setup"
Oh, by loop I meant Titanium Backup. Everything is working a ok. Just wondering if there was something I missed.
Click to expand...
Click to collapse
Several people have been having this same problem attempting to restore system apps. Eagerly waiting for someone to figure out a solution. In the meantime, do NOT rely on backups of your system apps.
Just got my Verizon MotoMaker Moto X in, rooted it, and am trying to remove the ****-ton of horrible, bloated system apps.
Unfortunately, it seems like every time I delete the .apk's from /system/app (using root adb or TitatiumBackup) the damn things come right back after reboot.
Is there some backup directory copies of the .apk's are stored in to get restored?
I seriously need to figure out how to zap these apps, or I am just going to send this phone right back - I'm not paying $400 for a device that is completely compromised right from the start.
PityOnU said:
Just got my Verizon MotoMaker Moto X in, rooted it, and am trying to remove the ****-ton of horrible, bloated system apps.
Unfortunately, it seems like every time I delete the .apk's from /system/app (using root adb or TitatiumBackup) the damn things come right back after reboot.
Is there some backup directory copies of the .apk's are stored in to get restored?
I seriously need to figure out how to zap these apps, or I am just going to send this phone right back - I'm not paying $400 for a device that is completely compromised right from the start.
Click to expand...
Click to collapse
Has nothing to do with the phone , its an issue with your root method slapmymoto, you need to have the system set as r/w AFAIK
Sent on my Moto X
flashallthetime said:
Has nothing to do with the phone , its an issue with your root method slapmymoto, you need to have the system set as r/w AFAIK
Sent on my Moto X
Click to expand...
Click to collapse
I've been lying in bed, staring at the ceiling, thinking the same thing. Gave up on sleeping, so now I'll have another run at this.
Figure I'll flash back to 4.2.2 and follow the steps to upgrade to 4.4 and then root. Hopefully I will have better luck.
PityOnU said:
Just got my Verizon MotoMaker Moto X in, rooted it, and am trying to remove the ****-ton of horrible, bloated system apps.
Unfortunately, it seems like every time I delete the .apk's from /system/app (using root adb or TitatiumBackup) the damn things come right back after reboot.
Is there some backup directory copies of the .apk's are stored in to get restored?
I seriously need to figure out how to zap these apps, or I am just going to send this phone right back - I'm not paying $400 for a device that is completely compromised right from the start.
Click to expand...
Click to collapse
You need to make sure you are in r/w mode. Reboot to recovery first.
mjphillips1981 said:
You need to make sure you are in r/w mode. Reboot to recovery first.
Click to expand...
Click to collapse
This was the issue. This is my first experience with a firmware lock on a file system. Now I know!
Thanks for the help all!
Hi All,
Since I am getting nowhere and no replies for my questions, I am going to rephrase them differently here so hopefully someone can jump in and give me a helping hand... (and please forgive if I seem to bombard the forums with questions).
My Note 3 SM-N900A, build KOT49H.N900AUCUCNC2, running 4.4.2. It is having issues with permissions that effectively block the phone from seeing any SD Card, USB, and internal memory space. It won't access any remote resources like internet or Google Play...either
Issues arose after I changed platform.xml. I since then unrooted the phone and uninstalled SuperSU. I can see that these 3 changes were reckless on my part, that I just put the phone into a very bad state that made it very very difficult to recover. I am still banging my head for the blunders but obviously that didn't help fix the phone. :crying:
I would like to know if there is a way to gain access to the phone's system area again to fix the permission issues. Can I use ADB Shell along with USB debugging? If yes, what are the commands I need? Can I somehow send towelroot and SuperSU to the phone via Odin and execute them? The reason I ask this is that I have no way to access any storage area on the phone, and there is no way to go online to download apps. Or can I put the phone into service mode by typing in the *# numbers on the keypad and hopefully fix it there?
Thank you
At this point I'm not even sure if adb would be able to access your memory card to push TowelRoot to it. You might be best off restoring using the stock Odin files, lick your wounds, start over and chalk it up as a learning experience.
http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my AT&T Galaxy Note 3 using Tapatalk®
OK, Something Positive
andygev35 said:
At this point I'm not even sure if adb would be able to access your memory card to push TowelRoot to it. You might be best off restoring using the stock Odin files, lick your wounds, start over and chalk it up as a learning experience.
http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Ah, thanks for replying. I was really worrying about that too.
However, I just installed ADT on my PC and connected to the phone via USB debugging. Using the adb shell ls command, I could see the entire directory structure. I was able to get to the system folder too.
I pulled the platform.xml back and attached to this message. Could you or someone please take a look and let me know if anything is wrong in the file? I made very small changes and reverted them. So it should be same as original, but I am not so sure. Also do you know if the encoding of the file is wrong so that Android couldn't read it?
At this point, it appears all is NOT lost. I just need some of your experts to guide me thru the commands needed to regain the access to my SD card or storage from the phone.
Now, let me bring in another point: Prior to having all this snafu, I granted ES File Explorer root access so that I could overwrite the platform.xml file. I don't know if doing that messed up the system. If it did, what would be the most straight forward way, simplest way to try to get back to normal? Provided now adb seems to be able to access the files and directory.
I know I could try install towelroot again, but would like to see if I can bring the system back to normal operation first.
Thanks
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
vbcomer said:
Ah, thanks for replying. I was really worrying about that too.
However, I just installed ADT on my PC and connected to the phone via USB debugging. Using the adb shell ls command, I could see the entire directory structure. I was able to get to the system folder too.
I pulled the platform.xml back and attached to this message. Could you or someone please take a look and let me know if anything is wrong in the file? I made very small changes and reverted them. So it should be same as original, but I am not so sure. Also do you know if the encoding of the file is wrong so that Android couldn't read it?
At this point, it appears all is NOT lost. I just need some of your experts to guide me thru the commands needed to regain the access to my SD card or storage from the phone.
Now, let me bring in another point: Prior to having all this snafu, I granted ES File Explorer root access so that I could overwrite the platform.xml file. I don't know if doing that messed up the system. If it did, what would be the most straight forward way, simplest way to try to get back to normal? Provided now adb seems to be able to access the files and directory.
I know I could try install towelroot again, but would like to see if I can bring the system back to normal operation first.
Thanks
Click to expand...
Click to collapse
Here's the original stock platform.xml if it helps you.
andygev35 said:
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Edit: instead of using adb push, use "adb install towelroot.apk" (if that's the actual package name). Go through the rooting process, download the ES File Explorer apk to your computer install it using adb. Hopefully if all that works, you'll be able to check and fix any permissions that got messed up with your platform.xml. It should be rw-r-r.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
A Step Forward
andygev35 said:
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
OK. You are right. adb doesn't have write access yet.
I tried this and got success:
C:\AndroidDev\sdk\platform-tools>adb install tr.apk
1767 KB/s (113099 bytes in 0.062s)
pkg: /data/local/tmp/tr.apk
Success
What should I do next? Does it mean the tr.apk has been installed?
Thanks
Update: I saw the Towelroot app in the App Drawer, but after clicking on it and choosing "make it ralr", I got message "Unfortunately, towelroot has stopped."
vbcomer said:
OK. You are right. adb doesn't have write access yet.
I tried this and got success:
C:\AndroidDev\sdk\platform-tools>adb install tr.apk
1767 KB/s (113099 bytes in 0.062s)
pkg: /data/local/tmp/tr.apk
Success
What should I do next? Does it mean the tr.apk has been installed?
Thanks
Click to expand...
Click to collapse
Sounds as though towelroot is now installed. Go to your app drawer and run it.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
andygev35 said:
Sounds as though towelroot is now installed. Go to your app drawer and run it.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Yeah, it is installed in the App drawer, but running it gave me error "Unfortunately, towelroot has stopped.".
I went ahead and install both ES File Explorer and SuperUser packages. From ES FE, I could look at the /system/ect/permissions/platform.xml and could see that it had a different date, its date is older, 3/15/2014. I think it came with the N900AUCUCNC2 that I flashed with Odin yesterday.
So, it appears the permission come from a different place or source, I would like to know where Android actually sees the permissions. You know, how did it think that it needed to lock down read/write access to storage areas while the /system folder has been replaced.
Thanks
vbcomer said:
Yeah, it is installed in the App drawer, but running it gave me error "Unfortunately, towelroot has stopped.".
I went ahead and install both ES File Explorer and SuperUser packages. From ES FE, I could look at the /system/ect/permissions/platform.xml and could see that it had a different date, its date is older, 3/15/2014. I think it came with the N900AUCUCNC2 that I flashed with Odin yesterday.
So, it appears the permission come from a different place or source, I would like to know where Android actually sees the permissions. You know, how did it think that it needed to lock down read/write access to storage areas while the /system folder has been replaced.
Thanks
Click to expand...
Click to collapse
I'm at the limit of my experience here... Did you do the all in one restore or the 4 file restore?
Sent from my AT&T Galaxy Note 3 using Tapatalk®
andygev35 said:
I'm at the limit of my experience here... Did you do the all in one restore or the 4 file restore?
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Thanks for hanging in and helping, you don't know how much I appreciate your time!
I did the all in one first. That didn't help. Then I did it again with the re-partition with PIT file. But that didn't help either. I didn't try the 4 files individually for fear of losing data.
vbcomer said:
Thanks for hanging in and helping, you don't know how much I appreciate your time!
I did the all in one first. That didn't help. Then I did it again with the re-partition with PIT file. But that didn't help either. I didn't try the 4 files individually for fear of losing data.
Click to expand...
Click to collapse
I think you've just about done everything you can do without a complete Odin reinstall and reformat. If adb pull is working for you I suggest pulling the folders you want to save and doing the complete 4 file install with the PIT file as well.
Someone more experienced than I may be able to get you back up without losing your but tbh with the amount of troubleshooting you've done already I think a full Odin reinstall is your best option and will prevent any issues that could stem from this further down the line.
The only thing I can think of with towelroot is that it needs internet access to run were you connected to wifi when you ran it? It's probably not that simple but figured it couldn't hurt to try!
brisinger08 said:
I think you've just about done everything you can do without a complete Odin reinstall and reformat. If adb pull is working for you I suggest pulling the folders you want to save and doing the complete 4 file install with the PIT file as well.
Someone more experienced than I may be able to get you back up without losing your but tbh with the amount of troubleshooting you've done already I think a full Odin reinstall is your best option and will prevent any issues that could stem from this further down the line.
The only thing I can think of with towelroot is that it needs internet access to run were you connected to wifi when you ran it? It's probably not that simple but figured it couldn't hurt to try!
Click to expand...
Click to collapse
Hi there,
Thanks for replying. I am kind of afraid I will have to go down that route, but at the same time trying not to if I could.
One of the other reasons I didn't try the 4 files was because I thought the all-in-one, as its name suggested, would be equivalent to those 4 files.
Is there a way to pull the SMS, MMS, call logs from the phone via adb? Do you know where those records are kept?
Thanks
vbcomer said:
Hi there,
Thanks for replying. I am kind of afraid I will have to go down that route, but at the same time trying not to if I could.
One of the other reasons I didn't try the 4 files was because I thought the all-in-one, as its name suggested, would be equivalent to those 4 files.
Is there a way to pull the SMS, MMS, call logs from the phone via adb? Do you know where those records are kept?
Thanks
Click to expand...
Click to collapse
The all-in-one file is the same as the 4 files, the only difference is installing it doesn't wipe the internal storage.
Have you tried running adb backup? That would be a heck of a lot easier than pulling a bunch of folders...if that doesn't work the databases are in /data/data
Calls: /data/data/com.android.providers.contacts
SMS and MMS: data/data/com.android.providers.telephony
Is there is any shell command to long tap
Hello!
So I have become a crazy cat collector with Nougat. But I recently switched roms so I dont have my beautiful cats anymore. :crying: What files can I copy from my old rom to get them back into my new one?
I found this article:
https://www.reddit.com/r/Android/comments/4tualq/what_i_know_about_cats_the_android_nougat_easter/
It didn't specifically say that cats can be restored but i tried copying the xml file from directory below. But it was a no-go
/root/data/data/com.android.egg/shared_prefs/mprefs.xml
Is there anyway I can be reunited with my cats. Please let me know.
God Bless
-The Cat Lady
You could try backing up the android easter egg app in tibu and restoring data when you flash the rom. I haven't tried it, so if you feel like taking a risk go for it.
CollinsB said:
Hello!
So I have become a crazy cat collector with Nougat. But I recently switched roms so I dont have my beautiful cats anymore. :crying: What files can I copy from my old rom to get them back into my new one?
I found this article:
https://www.reddit.com/r/Android/comments/4tualq/what_i_know_about_cats_the_android_nougat_easter/
It didn't specifically say that cats can be restored but i tried copying the xml file from directory below. But it was a no-go
/root/data/data/com.android.egg/shared_prefs/mprefs.xml
Is there anyway I can be reunited with my cats. Please let me know.
God Bless
-The Cat Lady
Click to expand...
Click to collapse
This might work but it also might crash your phone. Proceed at your own risk.
I was wondering if you ever figured out a way. I'm using a Nexus 5X so it's only a matter of time before the bootloops plague my device. Was hoping to back them up before then.
EDIT:
Would using ADB work?
Code:
adb backup -f "C:\CatsBackup20161229.ab" -apk com.android.egg
EDIT 2:
I was so close. Thanks to this Reddit post, I have used the following in a Windows Batch File to backup my Cats with a timestamp. Hope this helps any Googlers.
Code:
adb root
adb backup -f C:\CatsBackup_%date:~-4,4%%date:~-10,2%%date:~-7,2%.ab com.android.egg -system
What I'd done was long press the cat when one came up then just shared it to my Drive folder. I've also found duplicates will most likely come up (number of the cat) but the cat will be different color.
I've personally flashed numerous different nougat ROMs and different versions (7.0, 7.1, 7.1.1) in no particular order, and the Easter egg cat collection got backed up and restored on each and every ROM I've tried and used.
The way I go about this is, before I decide to switch ROMs or update using clean flash, I use titanium backup to backup the Easter egg app. Once I clean install an update or a different nougat ROM, I first unlock the nougat Easter egg in settings (tap the Android version a bunch and long press on the N animation to find the cat icon). Then head over to quick toggles, hit edit, find the cat toggle and add it to a desired slot. Finally, in titanium backup, find the Easter egg app, hit restore. It will ask what to restore, make sure you select "data only," do NOT restore "app + data," this may or may not cause system UI issues.
Requirements: Nougat ROM of your choice (any version) and root access.
This method works for restoring chrome tabs and possibly a few other system apps' data. Restoring system app(s) + data, however, will usually break things, so make sure to only restore the respective system apps' data only.
okay so i got the easteregg.ab file to back up onto my local disk, but i cannot get my phone to restore the .ab file through ADB.
ADB will say that i must unlock my device and allow the restore to complete however the phone is completely unresponsive to the request to restore, it as if nothing is happening.
what am i missing here :
adb backup -f easteregg.ab com.android.egg -system
(that puts an easteregg.ab file into c\users\xxxx)
then : adb restore c\users\xxxx
(adb then tells me "Now unlock your device and confirm the restore operation)
.....but nothing has happened and it asks for nothing on my phone and the cats are not loaded =(
Permissions. Were they set on the file when you restored it?
Strephon Alkhalikoi said:
Permissions. Were they set on the file when you restored it?
Click to expand...
Click to collapse
im not sure if i know which permissions your refering too, but the easteregg.ab file permissions are currently set to allow full control for the System, Administrator and the User.
How do i ensure the permissions are correct ?>
The permissions were likely completely stripped from the file when it was sent via ADB. You'll need to root and do one of the following.
*Use a terminal app to set permissions.
*Use a file manager with root access, navigate to the file's location, and set permissions manually.
The correct permissions are likely rw-r--r--, which uses the number 644.
Strephon Alkhalikoi said:
The permissions were likely completely stripped from the file when it was sent via ADB. You'll need to root and do one of the following.
*Use a terminal app to set permissions.
*Use a file manager with root access, navigate to the file's location, and set permissions manually.
The correct permissions are likely rw-r--r--, which uses the number 644.
Click to expand...
Click to collapse
My s7 edge is not rooted.
Is there anyway to restore the easteregg kitties with out root ? i thought that was possible.
Did you downgrade from a Nexus 6 to a S7? Sorry to hear that if true, because the S7 has a locked bootloader. The file likely never transferred to where you wanted it to go, as the locked bootloader would prevent that. Thus you need to unlock the bootloader to even transfer the file. ADB may have commands to set file permissions, but my recollection on that is hazy. It would also be irrelevant if the bootloader cannot be unlocked.
Strephon Alkhalikoi said:
Did you downgrade from a Nexus 6 to a S7? Sorry to hear that if true, because the S7 has a locked bootloader. The file likely never transferred to where you wanted it to go, as the locked bootloader would prevent that. Thus you need to unlock the bootloader to even transfer the file. ADB may have commands to set file permissions, but my recollection on that is hazy. It would also be irrelevant if the bootloader cannot be unlocked.
Click to expand...
Click to collapse
oh wow! i pulled up this thread last night and didn't even realize i was on the nexus 6 groups forums haha, boooooo on me =(
no i didnt down grade lol, i never had the nexus, i am just a s7 edge owner who doesn't want to loose their kitties in a phone swap =(
and yeah i had some real difficulties getting the .ab file to even save to my computer after messing around with a bunch of variations on commands through adb.
now im getting depressed again
..hey i REALLY appreciate all this help btw =\
Sorry to hear that. But unfortunately, unless you can unlock the bootloader, you're not going to be able to use ADB to transfer the file back. With a locked bootloader you can pull files, but not push them.
I shoulda realized that cause im not new to the rooting process at all and i hate having a phone with a locked bootloader but i really do like the s7 edge, it grew on me,....... alas my kittens will have to wait till the bootloader becomes available.....
Check the S7 Edge forums. I'm sure they have something that may help.