Related
I have a Motorola Cliq, Also a G1. I was wondering. Is there a way to pull an APK from an unrooted phone? I can "adb shell" into the phone and look at it's contents. I see the APK i want to copy but since i don't have root, it says "CP Permission Denied"... Is there a way of pulling or copying an APK if the phone is not rooted???
Did you try adb remount first?
Karolis said:
Did you try adb remount first?
Click to expand...
Click to collapse
yes, I tried ADB remount but it doesn't work... I can do adb devices and it'll show but it won't mount it as rw... it just lists the contents but can't copy,move,pull or push.
Where is the apk located? If it's in /system and it's read-only in theory you should still be able to pull it. Don't know why you're using 'cp' rather than adb pull.. If it's in data/app-private then no you won't be able to pull it. Hence the ADP1 has root but can't download paid apps (to prevent piracy)..
Solved
I tried CP, MV, PULL, PUSH... nothing worked because the phone is not rooted... BUT I SOLVED THE PROBLEM!
Here's what my goal was. My wife got a Motorola Cliq. It came with the TeleNav program and i wanted to put it on my G1... I couldn't get it out because the phone's not rooted....
I fixed the problem though...
I installed ASTRO File Manager on the Motorola Cliq, located the APK and used the e-mail option to e-mail it to myself... that actually worked... woot woot!
Installed it on the G1 and it works like a charm... so now I have Turn by Turn directions on my G1.
follow up question because i'm attempting to do the same thing, just trying to extract the apk. where exactly did you find that file using astro, i've been looking but haven't seen it
jbearamus said:
follow up question because i'm attempting to do the same thing, just trying to extract the apk. where exactly did you find that file using astro, i've been looking but haven't seen it
Click to expand...
Click to collapse
Apps should be in /data/app.
Also, you could have used ADB
Code:
adb pull /data/app/app.to.pull.apk C:\apps
Ooglez said:
Apps should be in /data/app.
Also, you could have used ADB
Code:
adb pull /data/app/app.to.pull.apk C:\apps
Click to expand...
Click to collapse
now i understand the fact that i have a different device may screw things up, but when i look in the data file it says "directory is empty" and when i executed that command via cmd prompt it says remote object...does not exist
the new google maps in market hs turn by turns as well...
Problem solved through other means, thanks for the help!
hey boys
so I finally gave it and did the whole adb rooting thing... lots of command lines and so on but finally it works so I got rid of Universal Androot..
so now my problem is still there though...
I run the update.zip and I get this:
assert failed: apply_patch_check(“system/app/GenieWidget.apk”,”(insert tons of digits here″,”(insert tons of digits here)″)
“E: Error /sdcard/update.zip
(Status 7)
Installation aborted.”
Anybody got a solution?
My phone and its changes:
Stock Nexus One 2.2
Rooted word-per-word via http://forum.xda-developers.com/showthread.php?t=736271
Uninstalled Amazon MP3 and "News & Weather" (genie widget?)
I figure maybe reinstalling News & Weather would fix it ... but Titanium backup does not recover it even if I did back it up first... (useless??)
I downloaded the APK and instaled it, but still the same thing.
What else what else...
thanks
I'm only posting this here because I, too, have an error and am in no way trying to thread-jack. I got the 2.2.1 OTA the other day and went ahead to update. Unfortunately, I use AndRoot also and when I got halfway through the OTA, I got an error during installation. I pulled the battery, rebooted, and I was still 2.2 rooted. I unrooted with AndRoot and now seemingly have no way of acquiring the update OTA. Any advice, OP?
OTA seems absolutely random to me ... so I would download the update (found in this very forum) and rename it to update.zip and put it in the root of your sd card and run the update as prescribed on many sites...
as for my problem... damnit damnit damnit is all I can say. I know 2.2.1 is generally useless, but I want to be sure I can install Gingerbread when it comes out!!
damn so I tried 2 different versions of GenieWidget installations (it's news and weather)
seems I get the same error everytime.
I know the "simplest" thing is to run a full reinstall of my phone (recover console?) but I don't want to redo all my apps/settings... can't there be a way to recover 1 or 2 components only? in this case, amazon mp3 and geniewidget, just so that the 2.2.1 update works...?
I had the same issue with com.amazon.mp3.apk not being found (I remember deleting it as soon as I got root)... well I had to put it back under /system/app/ (meaning you can't do it via the market - only manually)
Note: the exact version that was shipped with froyo has to be installed. You can check that you have the right apk by computing its sha1 sum (that's the second "insert tons of digits here" MitchRapp refers to)
*UPDATE*
oh snap.
my friend has the same nexus one as me ... so I copied his GenieWidget.apk and .odex into my /system/app and so far so good... i got another error (com.amazon.mp3) so I'm going to copy that too
update to follow...
hey it worked!
after a (seemingly) endless "X" animation bootup... 2.2.1 is there.
now I lost the root access I just made with adb shell something something.... that's normal I guess, so I'll redo it
Uh oh, I removed amazon mp3 too...;(
toss the .apk back in /system/app and reboot and update... it worked!
now for re-rooting... that wont work damnit.
I'm doing the rageagainstthecage thing word-for-word and the thing is, when I try
./busybox cp busybox etc...
it says file already exists
and the chmod commands only give me a "read-only" error
cuz I already rooted earlier using the .freenexus style .......
what can I do for this?
Anyone happen to have the2.2 Amazon apk and willing to share?
Sent from my Nexus One using XDA App
I do, what's your email
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...
bennettm89 said:
Anyone happen to have the2.2 Amazon apk and willing to share?
Click to expand...
Click to collapse
Sure.
sha1sum is c3b285c13db4b7f8fcfb72372d77b388157bf6cd
MitchRapp said:
I do, what's your email
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...
Click to expand...
Click to collapse
I used superboot (1.1-FRF91-nexusone-superboot) - worked like a charm.
I had an issue with settings.apk , had used universal androot and metamorph to make changes to the battery meter.
After getting the ota , the installation was aborted due to changes in settings.apk . i downgraded to android 2.1 erd79 ( had the passimg.zip file from few months ago).
Once downgraded never got OTA for further updates ( eg ere27 , frf91 etc).
had to manually update to frg83.
Jony, Thank you.
OP, thank you anyway, I got it from Jony. Now to find the update.zip...
God bless it. Went to go install from SD, I don't have twitter. I hate twitter. Anyone have it...
MitchRapp said:
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...
Click to expand...
Click to collapse
The rageagainstthecage step-by-step is missing a couple steps that will cause it to give the errors you're seeing. I ran into this and posted the solution, with follow-up and confirmation by others, later in the thread. Check out
http://forum.xda-developers.com/showthread.php?t=792016
In a nutshell, the /system partition needs to be mounted for both read and write in order to set permissions on the Superuser.apk and su files. Also, if you already were rooted and have Superuser.apk, su, and busybox installed, you don't have to copy them back to the phone--you can just set the permissions on the existing files.
Ohhhh jony! Can you post the twitter APK pl0x
bennettm89 said:
Now to find the update.zip...
Click to expand...
Click to collapse
There it is: http :// android.clients.google.com/packages/passion/signed-passion-FRG83-from-FRF91.c8847c98.zip
bennettm89 said:
Ohhhh jony! Can you post the twitter APK pl0x
Click to expand...
Click to collapse
Hre you go - sha1sum is 2acade940a14e65abcb93ff7fc68b0a95b733113
jony22 said:
There it is: http :// android.clients.google.com/packages/passion/signed-passion-FRG83-from-FRF91.c8847c98.zip
Hre you go - sha1sum is 2acade940a14e65abcb93ff7fc68b0a95b733113
Click to expand...
Click to collapse
Thanks buddy, I appreciate it.
I'm not really happy with the update. Lost root ( I knew I would ) but the most upsetting thing is that I removed my work email from my phone. I had to update security settings to authorize the remote administration of my device through my exchange server at our HQ which is not happening. I know it doesn't have to be done but I was getting increasingly angry just looking at it in the notification bar 24/7.
Hey all -- so i flashed back to JH6 with ODIN, got the JH7 update through Kies Mini, and then rooted. I also decided to use Launcher Pro as my default homescreen launcher.
Now i'm trying to use SWM to sideload some apps, but I always get the error (something like this) FAILED INSTALL PARSE UNKNOWN EXCEPTION ... the program recognizes my device just fine and loads up the .apk just fine but fails on trying to install it onto my phone.
anyone have an idea of what might be going on
SWM is unnecessary after root isn't it
Sent from my SAMSUNG-SGH-I897 using XDA App
Tchem said:
SWM is unnecessary after root isn't it
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The 2 are not related. You do NOT need to root to use Sideload. The SWM just uses the ADB command from the SDK. You can do this all day long without root.
If you want to install apps from your phone (not your PC) then you need to root and then you need to edit the settings.db file to allow sideload on the phone. You can't get to settings.db without rooting your phone.
Does that help?
alphadog00 said:
The 2 are not related. You do NOT need to root to use Sideload. The SWM just uses the ADB command from the SDK. You can do this all day long without root.
If you want to install apps from your phone (not your PC) then you need to root and then you need to edit the settings.db file to allow sideload on the phone. You can't get to settings.db without rooting your phone.
Does that help?
Click to expand...
Click to collapse
sort of not really, as i'm trying to upload apps/widgets from my pc. i want to hold off buying Root Explorer, and apparently Droid Explorer doesnt work on win7 64-bit systems yet ... just kind of odd that SWM can't load to my phone. i either get the INSTALL PARSE FAILURE UNKNOWN EXCEPTION or INSUFFICIENT SPACE or OLDER SDK errors. doesn't make sense to me...
turn debugging on ,
don't put the .apk files in the sideloader folder at all. caused the whole no space avaliable for me when i did that
try that... works for me.
updated with the ota an i'm rooted.
yeah i had debugging on, left the apks in a completely separate folder (didnt put them in the payload folder). the main failure i get is the install parse unknown exception one
im thinking it might actually be the apks i'm trying to upload. i got one apk to upload successfully, so maybe the other ones have some bad code in them. *shrug*
specifically i've been trying to upload the REVOlution transparent apps. all of them fail for me. then i uploaded minimal icons apk just fine.
Simple Thread to show how to root 1.5.7 & 1.8.3 using GingerBreak
Requirements: SD Card(real sd card not internal)
WARNING: THIS WILL DELETE YOUR INTERAL SD-CARD, BACKUP FIRST!!!
First if you don't have adb you need to get it. Easiest way is by downloading SuperOneClick. DO NOT run superoneclick, you only want adb from it.
Next download GingerBreak.apk made by Chainfire, it can be found here
Next launch from command prompt move to where adb is c:/path/to/adb/ and then run the following command
adb install /path/to/apk/GingerBreak.apk
It will install it, next on your phone in your app menu browse to and click on GingerBreak. Click root. Your phone will reboot and you will have root .
I have personally tested on a stock 1.5.7 and it works!
I have not personally tested on 1.83, but it has been confirmed by many. Same procedure applies
If you want side loading use Gladenable.
So to follow up.
Code:
1. Get ADB
2. adb install GingerBreak.apk
3. Run GingerBreak
4. Root
5. If needed run Gladenable to enable sideloading if needed.
6. Done!
All credit goes to the GingerBreak team & Chainfire, all did was apply there work.
Or you could do this, Thanks kennethpen .
kennethpenn said:
Hey everyone, I made a little tool that does all of this stuff for you.
Go ahead and download then run.
http://bandbinnovations.com/xda/GingerBreak.exe
Click to expand...
Click to collapse
nice.....thanks
thats great news for now and for the future xD
Nice.. Very Very Thanks..
This works at Korea Atrix MB860(SK Telecom).
Does this work for phones that were never rooted/have sideloading disabled still?
You can always sideload using Android Sideload Wonder Machine.
Oh, nice. That tool is way better than the other one I have...
Also, the OP doesn't mention needing an SD card installed but the other thread mentioned needing one. So do I need an sd card in?
Sir_Brizz said:
Oh, nice. That tool is way better than the other one I have...
Also, the OP doesn't mention needing an SD card installed but the other thread mentioned needing one. So do I need an sd card in?
Click to expand...
Click to collapse
Yes, you need an SD card (not the internal one). As best I've been able to tell so far, vold can only be exploited with an external SD card mounted.
Because of the risk of formatting the card, its recommended you either back yours up first, or use some old 2GB junker. You can get these in the impulse buy isle at your local grocery store.
Sir_Brizz said:
Does this work for phones that were never rooted/have sideloading disabled still?
Click to expand...
Click to collapse
Yes this is a full rooting method, afterwards you would need to enable sideloading through say GladiRoot.
Hey everyone, I made a little tool that does all of this stuff for you.
Go ahead and download then run.
http://bandbinnovations.com/xda/GingerBreak.exe
romracer said:
Yes, you need an SD card (not the internal one). As best I've been able to tell so far, vold can only be exploited with an external SD card mounted.
Because of the risk of formatting the card, its recommended you either back yours up first, or use some old 2GB junker. You can get these in the impulse buy isle at your local grocery store.
Click to expand...
Click to collapse
I can do one better, I have a 512mb junker Hopefully that will work.
Would anyone happen to have a mirror to superoneclick? the link that they have is to a corrupt file, it wont open.
drock212 said:
Would anyone happen to have a mirror to superoneclick? the link that they have is to a corrupt file, it wont open.
Click to expand...
Click to collapse
Just download the .exe that I made (it is in the OP).
So we don't need to flash the SBF in order to root now???
I have a completely unmodded Stock Atrix running 1.5.7, and this will allow me to root and do all the cool root type things that cool kids do these days?
thebeardedchild said:
So we don't need to flash the SBF in order to root now???
I have a completely unmodded Stock Atrix running 1.5.7, and this will allow me to root and do all the cool root type things that cool kids do these days?
Click to expand...
Click to collapse
that is correct.
thebeardedchild said:
So we don't need to flash the SBF in order to root now???
I have a completely unmodded Stock Atrix running 1.5.7, and this will allow me to root and do all the cool root type things that cool kids do these days?
Click to expand...
Click to collapse
correct
Nice! Just a suggestion to make it clear in the title that this roots system version 4.1.57 and does not require any sort of SBF flash. Maybe even update the Gladroot original post to link to this one?
Good . I have MB861. It's success. Thanks jug6ernaut
Do you download to the phone, then run the exe.?
Atrix rooted 1.5.7
GingerBlurr 1.3
katinatez said:
Do you download to the phone, then run the exe.?
Atrix rooted 1.5.7
GingerBlurr 1.3
Click to expand...
Click to collapse
Exe runs on your computer not phone.
Sent from my MB860 using Tapatalk
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