Database Develop

Incredible S file explorer

Hello
I'm waiting for my new Incredible S to arrive shortly and in the meantime I'm reading the user manual, I'm new to Android coming from Windows Mobile world.
Question: if I have backupped my applications to the memory card, in case of an hard reset, is there a way to reinstall them without passing through AppMarket? I have not found any File Explorer or Application Manager included in the ROM... are you obliged to connect to internet and download them?
Thanks

You can use Titanium Backup to back up and restore your apps.
They are not passed through the Android Market.
I do recall the app requires root, but that will be possible soon and is easy to do.

stefanospizzica said:
Hello
I'm waiting for my new Incredible S to arrive shortly and in the meantime I'm reading the user manual, I'm new to Android coming from Windows Mobile world.
Question: if I have backupped my applications to the memory card, in case of an hard reset, is there a way to reinstall them without passing through AppMarket? I have not found any File Explorer or Application Manager included in the ROM... are you obliged to connect to internet and download them?
Thanks
Click to expand...
Click to collapse
Hi there, I hope you will enjoy android!
There is indeed no file explorer installed on the Incredible S.
And yes, you will have to register your google account to access the market to download a file explorer (Astro File Manager for example)

TimMun said:
Hi there, I hope you will enjoy android!
There is indeed no file explorer installed on the Incredible S.
And yes, you will have to register your google account to access the market to download a file explorer (Astro File Manager for example)
Click to expand...
Click to collapse
Hi!
Thanks for your prompt answer! I suspected that after reading many threads on this matter. It seems a sort of limitation, I mean, having an SD card with your backup data and needs to connect to internet to download a file manager to install them..
But ok, this is the way it works

please use the ES File Manager .GO Android Market search "ES"

If you really wan't to avoid android market, you could usb adb (android debug bridge) to install titanium backup and then restore your apps. Or you could use adb to install certain apk's (apps are always .apk) you stored on your pc.
simple commands like
adb install C:\bla\bla\*.apk work like a charm
so if you download a filemanager, say "filemanager.apk".
you can give the command
adb install C:\bla\downloads\filemanager.apk
and it will install it on you phone after which you can acces all your files directly on your device.
You will need the SDK and some more info
If you want to use the adb, cd to \platform-tools\
But all this will be clear after a few hours of reading, trial and error
Welcome to Android.

DaanJordaan said:
If you really wan't to avoid android market, you could usb adb (android debug bridge) to install titanium backup and then restore your apps. Or you could use adb to install certain apk's (apps are always .apk) you stored on your pc.
simple commands like
adb install C:\bla\bla\*.apk work like a charm
so if you download a filemanager, say "filemanager.apk".
you can give the command
adb install C:\bla\downloads\filemanager.apk
and it will install it on you phone after which you can acces all your files directly on your device.
You will need the SDK and some more info
If you want to use the adb, cd to \platform-tools\
But all this will be clear after a few hours of reading, trial and error
Welcome to Android.
Click to expand...
Click to collapse
Hello!
thanks for your info. I was actually playing with adb and see it is very powerful. But you need the pc connected to your phone of course and again it seems not a so comfortable solution. I find a little bit curious not having an application installer or file explorer embedded in the system.
About the backup, I know that Tytanium need root privileges, correct? As far as I know no root procedure are still available on Incredible S. But, will tytanium allow to select what you want to restore? Maybe root is not necessary is you want to restore your application and not system files
Thanks

stefanospizzica said:
Hello!
thanks for your info. I was actually playing with adb and see it is very powerful. But you need the pc connected to your phone of course and again it seems not a so comfortable solution. I find a little bit curious not having an application installer or file explorer embedded in the system.
About the backup, I know that Tytanium need root privileges, correct? As far as I know no root procedure are still available on Incredible S. But, will tytanium allow to select what you want to restore? Maybe root is not necessary is you want to restore your application and not system files
Thanks
Click to expand...
Click to collapse
Yes, with titanium backup it is possible to select only certain apps that you wan't to restore.
It is indeed strange that HTC doesn't ship their android devices with a file manager, I recall my Hero didn't have one too. My Galaxy S does, although it's extremely basic.
I think after a few weeks when the first custom roms come out they will probably have a file manager installed in them. Until then I would recommend Linda Filemanager or OI Filemanager from the market, they are both free and quite powerful.
Cheers,
DaanJordaan

Regarding Titanium Root requirements. It does allow you to select between applications to restore, but the root check at start-up means you can't even access the backup/restore screen if your device isn't rooted.
It would be interested to see if a temproot is sufficient to restore certain apps. Something for me to try when i get home
As for the file manager... i think it was a concious decision to keep the device consumer focused. HTC has changed much in the last 2 years and definitely closed a lot of doors/windows they had open to devs and geeky consumers.

Bantu85 said:
Regarding Titanium Root requirements. It does allow you to select between applications to restore, but the root check at start-up means you can't even access the backup/restore screen if your device isn't rooted.
It would be interested to see if a temproot is sufficient to restore certain apps. Something for me to try when i get home
As for the file manager... i think it was a concious decision to keep the device consumer focused. HTC has changed much in the last 2 years and definitely closed a lot of doors/windows they had open to devs and geeky consumers.
Click to expand...
Click to collapse
Hello
what does temproot means? How do you log on as temproot?
Let me know about your trial...
Thanks

Unroot?

Is it possible to unroot after using the 1 Click Root? I'm coming from a rooted Droid Eris and I remember the first few people who rooted their Erises had lots of problems and I just wanna make sure we can go back and re-root if a better root process comes along later on...

magicelf said:
Is it possible to unroot after using the 1 Click Root? I'm coming from a rooted Droid Eris and I remember the first few people who rooted their Erises had lots of problems and I just wanna make sure we can go back and re-root if a better root process comes along later on...
Click to expand...
Click to collapse
Yes, but you'd have to do it manually at this point.
You'd delete busybox and su, uninstall superuser.apk, and there may be a symlink you need to undo, but I think the latest one-click cleans that up. I'd have to go back and check.
And any bloat you froze needs to be unfrozen, or bloat removed needs to be restored.

Okay, first version of this tool, be kind and let me know if there are any problems with it.
Also: NO GUARANTEES. If it does something that breaks your phone, I am not liable. Use at your own risk. Etc., etc.
http://www.psouza4.com/Droid3/PetesMotorolaRootTools_v1.03.zip
UPDATE 9/1/2011: version 1.03

I'm trying the one touch unroot and keep getting an error about the /sdcard/d3unroot folder missing files.
I extracted all of the APKs from your link to my /sdcard/d3unroot directory, but for some reason one touch unroot will not work.
The root worked great

same error here...

Get that error as well

Same here.
Why does it even need that to un-root @ that point?

I'm getting the same error.

Is it really a one-click method?
I'm a dummy so I think I'm gonna wait for some clarity.
Thanks for doing this, man!

Fully re-written and should un-root and restore /system/app for both v5.5.959 and v5.6.890. Enjoy!
http://www.psouza4.com/Droid3/PetesMotorolaRootTools_v1.03.zip
This program is for Windows only and can:
root your device (most Motorola Gingerbread devices)
unroot your device
restore your /system/app, even if you deleted files
And a bit more, such as un-freezing apps if you un-root just like Titanium Backup can.

So how do I do this. Is it the same as the one click root meaning unzip the file and put my phone into charging mode and let it do its thing
Sent from my DROID3 using XDA App

spacecasespiff said:
So how do I do this. Is it the same as the one click root meaning unzip the file and put my phone into charging mode and let it do its thing
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Pretty much -- this is an all-in-one. It'll tell you where to download files and where to put them when you begin.

I guess I'm just retarded I can't get this to work. I give up. Looks like I'm gonna have to get VZ to mail me a new D3

Yonnor said:
I guess I'm just retarded I can't get this to work. I give up. Looks like I'm gonna have to get VZ to mail me a new D3
Click to expand...
Click to collapse
Why can't you? More than willing to help, but have to tell me what the problem is. And bear in mind that I put out a new version less than 2 hours ago that fixes a LOT (it's a full rewrite).

ok ive downloaded the file to my computer.

Keep getting the error for the Restore data not being in the right place. I've extracted the files to the right spot (I think)
is the restore folder supposed to be located in the Root Tools folder, and then all the apk's placed that Restore folder?

Yonnor said:
Keep getting the error for the Restore data not being in the right place. I've extracted the files to the right spot (I think)
is the restore folder supposed to be located in the Root Tools folder, and then all the apk's placed that Restore folder?
Click to expand...
Click to collapse
Basically, yes.
I'll use your desktop as an example, so if you have:
Desktop\New Folder\Pete's Motorola Root Tools.exe
Then you'll want to extract all the files for the /system/app fix to:
Desktop\New Folder\restore
So that you have:
Desktop\New Folder\restore\AccountAndSyncSettings.apk
Desktop\New Folder\restore\AccountAndSyncSettings.odex
Desktop\New Folder\restore\AdminFeedNotifier.apk
etc.
This assumes you are using my new version 1.03.

psouza4 said:
Basically, yes.
I'll use your desktop as an example, so if you have:
Desktop\New Folder\Pete's Motorola Root Tools.exe
Then you'll want to extract all the files for the /system/app fix to:
Desktop\New Folder\restore
So that you have:
Desktop\New Folder\restore\AccountAndSyncSettings.apk
Desktop\New Folder\restore\AccountAndSyncSettings.odex
Desktop\New Folder\restore\AdminFeedNotifier.apk
etc.
This assumes you are using my new version 1.03.
Click to expand...
Click to collapse
Ok thank you, I'll give this a shot again.
EDIT: I have it set up as:
Desktop/PetesMotorolaRootTools_v1.03/restore/(all the apk's)
And I'm still getting the:
ERROR: /restore/ backup doesn't exist or is incomplete! etc etc

ok i just unrooted and all is good now im rooting agian. so thank you for this on click unroot meathod. its good to know that if i want to unroot i can. You should put this on every forum that you can. I will aslo tell people about it. You did a good thing for the people on this one. I think a lot of new people will whant to root now that they have a way to undo it.

Lol well like 8th try and I got it to work. Sorry for pestering you so much.

[Q] Another root ?

Fellas, I come to here, humble and contribed. I, as all others, have the dreaded gps bug. I know there are a few posts concerning it, however, those are starting to get confusing to me. I ask for some simple instructions as to simply root my device, and procedure to replacing the files that are to make it functional again. No debloating, flashing of ROMs, or etc. DL links would be nice too.
Phone specs:
At&t n900a
4.3 stock
baseband n900aucubnb4
build number jss15j.n900aucubnb4
Have rooted other samsung devices, so not totally an idiot...
Any help will be much appreciated

Kingo
Sent from my SAMSUNG-SM-N900A using Tapatalk

zinupe14 said:
Kingo
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
As well as other posts to many threads here, someone posts partial answers, or simply something they read. Thanks . People wonder why they brick their devices....SMH

You asked how to root p. Kingo app is as simple as it gets. And it doesn't trip your Knox counter. If you want 4.4.2 then I would suggest downloading the urdroid rom and following the detailed instructions. I'm running the stock kitkat rom rooted with no Knox counter trip. Not trying to be a prick but the kingo root method was as simple as pi
Sent from my SAMSUNG-SM-N900A using Tapatalk

I'm not interested in kitkat, honestly, I dont care about custom ROMs. I just need to root, and the procedure for replacing the gps files that are to make the AT&T GN3 gps actually work. And possibly stop the updates.

if you're on the latest nb4 baseband than you'll need to google Kingo v.1.15 and find a download of that version. if you're still on mj5 than just google kingo app, download and install to a windows pc. open the app and follow the instructions. its easy. kingo should install the correct drivers. kingo doesn't always succeed the first time. if that's the case try again until kingo says success. once done update su superuser app via google play and restart your phone. now you have root. i don't have gps problems so hopefully someone else can help you with. good luck. sry i can't post any download links but if you use google you should have no problems

Honestly I'd just wait if I were you....
Rogers and tellus note 3 have gotten kitkat the s4 has gotten kitkat for att in looking for kitkat in the next few weeks to month.
Sent from my XT907 using xda app-developers app

Would some explain how to "flash" the gps files to fix the friggen thing. I have root with kingo, and downloaded the gpsfix from drakeymcmb, but 2 folders are extracted and only one is told what to do with, as well as how to change permissions for the files...thanks in advance

crazysgt said:
Would some explain how to "flash" the gps files to fix the friggen thing. I have root with kingo, and downloaded the gpsfix rom drakeymcmb, but 2 folders are extracted and only one is told what to do with, as well as how to change permissions for the files...thanks in advance
Click to expand...
Click to collapse
Ignore the meta folder. You're not "flashing" these files, you're copying them to your phone's system folder. Open the zip and open the system folder, then open the etc folder. Now copy the gps.conf file to your phone's system/etc directory. Now go back to the gpsfix.zip and open system then open lib. Copy the 3 libloc files to your phone's system/lib directory. Go back to the zip. Open system, open lib, open hw. Now copy the 2 GPS files to the phones system/lib/hw directory. Change each files properties to rw-r-r(Fix permissions). Now reboot. Warning if you don't know what you are doing i don't recommend doing this as messing with system files can lead to very expensive paperweight

The Basilisk said:
Ignore the meta folder. You're not "flashing" these files, you're copying them to your phone's system folder. Open the zip and open the system folder, then open the etc folder. Now copy the gps.conf file to your phone's system/etc directory. Now go back to the gpsfix.zip and open system then open lib. Copy the 3 libloc files to your phone's system/lib directory. Go back to the zip. Open system, open lib, open hw. Now copy the 2 GPS files to the phones system/lib/hw directory. Change each files properties to rw-r-r(Fix permissions). Now reboot. Warning if you don't know what you are doing i don't recommend doing this as messing with system files can lead to very expensive paperweight
Click to expand...
Click to collapse
Thanks! This is what I needed, I understand the risks, but also know the reward is a functioning gps, the meta folder and how to change the permissions is what was holding me back.

So on permissions, just rw, r,r no execute on any right? Now how to disable att updates? Thank goodness for yall smart fellas

crazysgt said:
So on permissions, just rw, r,r no execute on any right? Now how to disable att updates? Thank goodness for yall smart fellas
Click to expand...
Click to collapse
Sry for the late reply. Owner=read write, group=read, other=read. No execute

To disable AT&T updates, freeze the at&t update app. (Sorry, I can't get the name right now, I'm on a ROM that had it removed, but it's at&t <something to do with updates>, with little red and green lines on the icon.) Link2SD or TiB will freeze it.

One more quick ?, When I open Super SU, a popup appears, Samsung KNOX has been detected. This might limit root capabilities and cause annoying popups. Try to disable KNOX? I have always cancelled the popup. Is that correct? or should I ok it? Again, thanks guys for all the help. I used my gps without fail all weekend long. Not a single problem, gps or phone wise. Wonder if I was to unroot using Kingo app, and leave the gps patch alone, if it would still get OTA?

[Q] Android 4.4.2 - ADB - Shell Commands - Root

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

[Q] Problems Backing Up EFS info

Hi. I'm new to rooting and flashing ROM's. I have had a Samsung Captivate (Gingerbread) that I haven't been using for quite some time and I thought I might try to update it to KitKat. I have read that it would be important to back up the EFS file so that I can keep my IMEI info. I rooted my phone using the tutorial on these forums and tried to use EFS Pro, but was not able to get past "the device is not perm rooted". Various threads suggested changing adb status, but I could not find that information (though I was able to find the USB debugging selection). I know that the phone is rooted so I looked for an older copy of EFS Pro in case the newer versions had dropped support for the Captivate. I couldn't find one so I looked at other ways to back up the files, but most information was for other (newer) Samsung phones. I could not install Samsung Tools. I really don't want to proceed with installing KitKat before backing up the EFS information. How do I go about doing this? I have tried the search function on the forum for this device and couldn't find what I was looking for (or maybe I didn't understand the information). Any thoughts?
I hope flashing KitKat will be easier than this issue...
Thanks.

Curious D said:
Hi. I'm new to rooting and flashing ROM's. I have had a Samsung Captivate (Gingerbread) that I haven't been using for quite some time and I thought I might try to update it to KitKat. I have read that it would be important to back up the EFS file so that I can keep my IMEI info. I rooted my phone using the tutorial on these forums and tried to use EFS Pro, but was not able to get past "the device is not perm rooted". Various threads suggested changing adb status, but I could not find that information (though I was able to find the USB debugging selection). I know that the phone is rooted so I looked for an older copy of EFS Pro in case the newer versions had dropped support for the Captivate. I couldn't find one so I looked at other ways to back up the files, but most information was for other (newer) Samsung phones. I could not install Samsung Tools. I really don't want to proceed with installing KitKat before backing up the EFS information. How do I go about doing this? I have tried the search function on the forum for this device and couldn't find what I was looking for (or maybe I didn't understand the information). Any thoughts?
I hope flashing KitKat will be easier than this issue...
Thanks.
Click to expand...
Click to collapse
You could just manually backup your efs folder using a root explorer or through adb. Have that backup on your pc in case you lose your IMEI.
That being said, when it happens (which is fairly rare), a flash back to stock (KK4) usually fixes it and then you're fine to update/flash again.

Other EFS backup options would include:
1) EFS☆IMEI☆Backup by wanam >> his xda thread, his playstore listing.
2) [HOWTO]Comprehensive IMEI/EFS Backup lists two simple ways to permanently backup up IMEI on your phone. One is with adb, the other is with Terminal Emulator for those with rooted devices. The commands used are said to be based on "Samsung's built in backup." The thread is in the SGS3 forum, if nothing else is an excellent source of background information for backing up and restoring nvdata.

I tried to copy the efs folder using Root Browser because the adb method looked very involved. When I started Root Browser, it was able to see a Titanium backup that I had placed into the SD card even though I had formatted the SD card. I figured that the format didn't wipe the information so I proceeded to copy the efs folder over. However, after copying the folder, I stuck the card into my computer and did not see the folder and could not copy the folder over to my computer. Is it because the card is formatted differently than my computer or is it that the file is not compatible with Windows given that it is an Android folder?
Will copying the folder be enough for backing up? If it is this easy to restore the efs, why use EFS Pro? Is there something else with the folder that needs to be present in order to restore a phone that loses IMEI information?

Curious D said:
I tried to copy the efs folder using Root Browser because the adb method looked very involved. When I started Root Browser, it was able to see a Titanium backup that I had placed into the SD card even though I had formatted the SD card. I figured that the format didn't wipe the information so I proceeded to copy the efs folder over. However, after copying the folder, I stuck the card into my computer and did not see the folder and could not copy the folder over to my computer. Is it because the card is formatted differently than my computer or is it that the file is not compatible with Windows given that it is an Android folder?
Will copying the folder be enough for backing up? If it is this easy to restore the efs, why use EFS Pro? Is there something else with the folder that needs to be present in order to restore a phone that loses IMEI information?
Click to expand...
Click to collapse
If you have it on your SD card, it should be fine. The idea is to have it on something else than your device's internal memory in case something goes wrong and can't get it there.
As for efs pro, some devices can't manually backup like the Cappy or is not enough. But once again, it doesn't happen very often that you lose your IMEI.

Okay. That's great. I guess I can try my first ROM flashing to KitKat. Thanks.