Hi there,
Is there a way to temporary root my Nexus S [I9020XXKD1] or alternatively a non-root way to access /data so that I can copy a file in and out? Essentially I want to be able to backup and restore some game saves
Most posts I've read basically have folks saying "Just root it", which is good advice to most but isn't right for me - I really don't want to have to wipe my phone and I'd also like to be able to dip my toe into rooting before taking a full leap. That, and aside from needing this one file in /data my phone works exactly as I'd like it to
I only need "su" access for a brief moment to copy off a file to and from /data. I set up the android sdk but ADB didn't work because of the protection of "production builds".
VISIONary seemed like the right kind of thing, but I don't believe it works for the Nexus S or recent firmware, so while temp rooting would be nice so would any solution that allows me to backup and restore some files in /data.
At the moment I am wondering if writing an apk of my own that copies/replaces this one file is the way to go - but that seems perversely long way around!
So any help/suggestions most appreciated
There is no temporary root for the Nexus S. You're either rooted, or you're not. However, if, perchance, you are on Android 2.3.2 or earlier, you might be able to root without wiping.
Without root, you cannot see the files in /data, but you can read/write the files directly if they have the proper permissions and you know the exact path/filenames. After poking around a bit, it seems that read & write permissions vary among apps. Most apps have full permissions reserved for the parent app. Some allow other apps/user to read some files, and read+write others. (The permissions being app-specific, if it can't be done by command line, I doubt it could be done by creating an app, either.)
So, what is the game? Perhaps I can do some exploring.
If you have the old bootloader (2.3.2 i think) you can boot a recovery without flashing. From you computer use "adb boot recovery.img" and boot clockwork recovery. From there you can mount and access the filysystems.
Sent from my Nexus S using XDA App
Maximilian Mary said:
There is no temporary root for the Nexus S. You're either rooted, or you're not. However, if, perchance, you are on Android 2.3.2 or earlier, you might be able to root without wiping.
Without root, you cannot see the files in /data, but you can read/write the files directly if they have the proper permissions and you know the exact path/filenames. After poking around a bit, it seems that read & write permissions vary among apps. Most apps have full permissions reserved for the parent app. Some allow other apps/user to read some files, and read+write others. (The permissions being app-specific, if it can't be done by command line, I doubt it could be done by creating an app, either.)
So, what is the game? Perhaps I can do some exploring.
Click to expand...
Click to collapse
Thanks I figured as much. The game is Dungeon Hunter 2 and essentially I am trying to implement a simple fix to make my save game work again (the fix is here: http://forum.xda-developers.com/showthread.php?t=1042675 a few posts down) but it requires root. So I do know the exact paths and filename.
Thank you for your helpful answer
Ok, I'm not having any luck here, and it's pissing me off. FYI, I don't have that game, so I'm testing it with Angry Birds. I can read and copy the file just fine, but I can't modify it without using root. The data file itself has read/write access, but the containing folder (files/) is read-only, so I can't overwrite the file after I've modified it. Since the file itself has r/w access, I wonder if it would work to modify the file directly, instead of using an outside program to modify it then overwriting it. (I'm a bit ignorant of the finer points of linux permissions.) This would require an app that would allow you to open and modify a file by typing the full path & filename, instead of just browsing the directory tree. You could also try < adb pull /data/data/com.gameloft.android.TBFV.GloftD2HP.ML/files/dh2_000.savegame dh2_000.savegame > (using the correct path, if that's not it). Then see if < adb push dh2_000.savegame /data/data/com.gameloft.android.TBFV.GloftD2HP.ML/files/dh2_000.savegame > works. The fact that you can copy the file out is promising, anyway. So even if you had to root, you could backup the file before rooting wipes everything, then fix it & back it up after you had root.
Btw, what version of Android are you on?
Edit: I think I'm getting somewhere. While you can't modify the file itself, you can modify the file contents. So something like this might work: < adb shell >
< more /sdcard/dh2_000.savegame > /data/data/com.gameloft.android.TBFV.GloftD2HP.ML/files/dh2_000.savegame >
So the next step is to get some help from someone who has the game and is rooted as to the exact path to the savegame file. Once we have that, I think we're golden. (Or, let me know if adb pull works with the path I guessed at.)
wow! Thank you for your help
In answer to your questions: my Nexus s is running 2.3.4 and you are correct about the file path (many other kind xda users died to bring us those paths ) is /data/data/com.gameloft.android.TB with the filename being dh2_000.savegame
I don't want to drive you to distraction! If I could back it up I probably would go ahead then and root the phone given how complexplaying with a non-rooted phone is!
I will try the adb pull method and let you know how I get on.
Thank you again for your help and for showing me why I probably do want to root!
Related
If you want to delete an app, change a file or whatever when you get root, please be smart about it. Think before you delete something. Have a plan B (a failback plan). If you don't know how you will fix whatever you're about to potentially break, DON'T DO IT.
Try to learn ADB. I know it's not for everyone, but it may pull you out of the fire later. Think before you do anything.
No matter what Android device it is, someone always has a post saying "Help! I deleted <insert app here> and I need it back!" Here are some tips:
Don't freeze or delete an app using Titanium Backup without knowing if it will crash your phone or not
If you're using ADB, rename a file instead of deleting it if you're not sure if it will crash your phone or not
Your /system folder is like the base operating system folder (think C:\Windows); before you change something BACK IT UP!
Code:
adb pull /system <destination_folder>
Since we only have temp root for now, if you're disabling packages, back up the packages.xml file
Code:
adb pull /data/system/packages.xml <destination_folder>
Learn from others' mistakes; if someone bricks their phone, read the thread and figure out how NOT to screw yourself and your phone
Heard of measure twice, cut once? Read three times, execute once. Listen to the Devs. Be nice to them. Don't piss them off. They do this on their own time.
Please be smart about whatever you do to your phone. We can't be dumb smart phone users. If you don't know something, ask in the appropriate section or thread. If you know something, don't tease others for not knowing. The occasional flame is funny and all, but at some point someone has to learn whatever they don't know - someone is going to have to step up and help them.
Thanks dawg...
I think and SD backup and Nandroid recovery backup on root will be good enough? <not condascending...just asking from your adb opinion?>
ROM_Guest said:
Thanks dawg...
I think and SD backup and Nandroid recovery backup on root will be good enough? <not condascending...just asking from your adb opinion?>
Click to expand...
Click to collapse
I think of that as another layer. We're not there with the Sensation yet, but I always think it's a good idea to use any and all methods best suited for what you're doing.
For example, if you're flashing a theme someone customized which could change multiple apk and jar files, a Nandroid backup is best.
When someone goes to remove an apk or freeze an app, they usually don't think to take a Nandroid backup (because deleting or freezing takes only a second - Nandroid backups take longer).
1) we don't have that functionality yet and 2) it's very common for someone to try to freeze a critical app which can cause a boot loop, which can easily be fixed by adb (if a Nandroid is not available).
i tried:
adb pull / backup/
it started building a file list and then started the copy. after a time (dont know excatly when because i let it run beside) it stoped working at:
pull: /sys/devices/platform/msm_adc/batt_id -> backup/sys/devices/platform/msm_adc/batt_id
nothing more happend. now i got 4883 files, a total of 3.1 GB, backup directory. but it seems not all files are in. when i browse through the phone dir i see much more files in the dirs.
is there any other way of getting a complete backup? when i rerun the command will it skip the files it allready dumped to disk? any other command?
thx!!!
daSn00p said:
i tried:
adb pull / backup/
it started building a file list and then started the copy. after a time (dont know excatly when because i let it run beside) it stoped working at:
pull: /sys/devices/platform/msm_adc/batt_id -> backup/sys/devices/platform/msm_adc/batt_id
nothing more happend. now i got 4883 files, a total of 3.1 GB, backup directory. but it seems not all files are in. when i browse through the phone dir i see much more files in the dirs.
is there any other way of getting a complete backup? when i rerun the command will it skip the files it allready dumped to disk? any other command?
thx!!!
Click to expand...
Click to collapse
All you really need is /system and /data if you want a complete backup. I know you see other files+folders, but those are mounted by the OS and kernel... or whatever. Someone with more Linux experience can explain better than I can. But if you want a complete backup, just get /system and /data.
The /system folder is like getting the base OS. The /data is all your user/personal data.
dumping /system worked fine: 1366 files pulled. 0 files skipped.
when trying to dump /data it freezes again and allways again at:
pull: /data/d/smem_log/dump_cont -> ../backup2/data/d/smem_log/dump_cont
so i dumped every dir in data manually only /data/d is missing now. but there are so many dirs in it, i dont want to dump every dir on its own
any idea?
daSn00p said:
dumping /system worked fine: 1366 files pulled. 0 files skipped.
when trying to dump /data it freezes again and allways again at:
pull: /data/d/smem_log/dump_cont -> ../backup2/data/d/smem_log/dump_cont
so i dumped every dir in data manually only /data/d is missing now. but there are so many dirs in it, i dont want to dump every dir on its own
any idea?
Click to expand...
Click to collapse
That should be good enough for now. No one else is doing this manually, so until we get an official root this is all you can do to backup. Once we get permanent root, titanium backup will do most of this for us.
I would only make backups of anything you change or delete at this point, but that's just me.
Sent from my HTC Sensation 4G using XDA App
Noob question here, how do i make a backup on this phone? do i need to unlock bootloader? it was so easy on the hero lol
I am also wondering this. I have a new stock NS4G with 2.3.4. I would like to root it, but my understanding is that is only possible on 2.3.4 if I unlock the bootloader also... right? Which will wipe my data.
Is there ANY option I have to backup data while not rooted? Specifically some saved games I have... Plants vs Zombies and Cut the Rope... I've spent (wasted) way too much time on those games to lose my saves!
I think game data saves are stored in/data/data/
I'm not 100% on this. See if you can back that folder up. Again, I'm not 100% on this. Do your research and come back to confirm but im about 75% certain it's /data/data/ but don't take my word.
Hmm... using androzip on phone, I browse to /data and I see no contents. :-( But there are some other directories outside of SDcard that I can see contents. Weird.
You do have permissions to access the data files themselves, but you do not have permissions to see the folder contents. So you need someone rooted who has those games installed to give you the path and filenames for the save files. Then download terminal emulator and
cat /data/data/com.happy.gamex/subfolder/gamesave1.poo > /sdcard/backup/com.happy.gamex/subfolder/gamesave1.poo
Make sure the file copied correctly (the new one is not empty). Then backup the sdcard, as that will get wiped, too. After you root, play a couple levels so the game will recreate the save files. Then to put your info back:
cat /sdcard/backup/com.happy.gamex/subfolder/gamesave1.poo > /data/data/com.happy.gamex/subfolder/gamesave1.poo
Thanks for the info Max, that sounds promising. Very strange to have access permissions but not "see" permissions... never heard of that in my other computing experience. Now to find somebody to help me. I wonder if I can use SDK to install games there and see some directory structure in the emulated device to answer the question? I did a google search for Plants vs Zombies and found one guy saying it's impossible with that game, rooted or not... but I still want to find out for myself.
The111 said:
Thanks for the info Max, that sounds promising. Very strange to have access permissions but not "see" permissions... never heard of that in my other computing experience. Now to find somebody to help me. I wonder if I can use SDK to install games there and see some directory structure in the emulated device to answer the question? I did a google search for Plants vs Zombies and found one guy saying it's impossible with that game, rooted or not... but I still want to find out for myself.
Click to expand...
Click to collapse
Well, I'm having trouble installing PvZ on my virtual device, but I have some other things installed and would like to browse my device directories, but I think they are all buried in .img files in my virtual device on my Windows machine. Any tips on getting inside these .img files to look around?
The111 said:
Thanks for the info Max, that sounds promising. Very strange to have access permissions but not "see" permissions... never heard of that in my other computing experience. Now to find somebody to help me. I wonder if I can use SDK to install games there and see some directory structure in the emulated device to answer the question? I did a google search for Plants vs Zombies and found one guy saying it's impossible with that game, rooted or not... but I still want to find out for myself.
Click to expand...
Click to collapse
It's the way linux permissions work. If a folder has execute but not read permissions, you can access subfolders and files, but cannot read the folder contents. If one of the files in it has read access, you can copy it, even though you can't see the actual file listing.
Maximilian Mary said:
You do have permissions to access the data files themselves, but you do not have permissions to see the folder contents. So you need someone rooted who has those games installed to give you the path and filenames for the save files. Then download terminal emulator and
cat /data/data/com.happy.gamex/subfolder/gamesave1.poo > /sdcard/backup/com.happy.gamex/subfolder/gamesave1.poo
Make sure the file copied correctly (the new one is not empty). Then backup the sdcard, as that will get wiped, too. After you root, play a couple levels so the game will recreate the save files. Then to put your info back:
cat /sdcard/backup/com.happy.gamex/subfolder/gamesave1.poo > /data/data/com.happy.gamex/subfolder/gamesave1.poo
Click to expand...
Click to collapse
This appears to be untrue.
I finally found (via another forum) the complete path to one of the saved game files I was interested in:
/data/data/com.zeptolab.ctr/shared_prefs/CtrApp.xml
So I tried in terminal: "cat /data/data/com.zeptolab.ctr/shared_prefs/CtrApp.xml > /sdcard/test.xml"
result: "/data/data/com.zeptolab.ctr/shared_prefs/CtrApp.xml: Permission denied"
The111 said:
This appears to be untrue.
I finally found (via another forum) the complete path to one of the saved game files I was interested in:
/data/data/com.zeptolab.ctr/shared_prefs/CtrApp.xml
So I tried in terminal: "cat /data/data/com.zeptolab.ctr/shared_prefs/CtrApp.xml > /sdcard/test.xml"
result: "/data/data/com.zeptolab.ctr/shared_prefs/CtrApp.xml: Permission denied"
Click to expand...
Click to collapse
Ahh... so frustrating. I want to upgrade to 2.3.5 rooted, and if I know for sure I have to lose these files, then I guess I'll lose them. But if there is any way at all to save them obviously I want to figure that out before I cross the point of no return...
I'm posting this information because 1 I was asked to and 2 I feel it could be helpful for the "MORE ADVANCED" users.
Do Not try any of my methods, None of them. Unless you WANT to brick your phone.
With that said, here to the best of my memory is what I have done.
I pulled my framework-res file as well as the other 3 that relate to it and tried to theme them. It worked a few times and after tweaking I eventually broke the permission of the files.. Hence putting me in a bootloop.
What I did..
Thankfully I had the Bionic Safestrap installed. (DO NOT INSTALL THE SAFESTRAP) So, I was able to boot into the safestrap and use adb commands. This took some toying around. For the sake of saving people from bricking i'm not going to list all of the adb commands. But I had to mount both the /sdcard and /systemorig. Now simple enough, I just went through and rm every file from inside the folders. (Do not rm the folder, You will not be able to recover the folder and no you can not push the folder) rm all files from /systemorig /apps /osh etc.. then push all my restore files (backup made with safestrap) to the /sdcard. (For some reason they have to be placed on the sdcard before being copied to the root directory otherwise it breaks the permission of the files, idk y?) A few times in order to mount /systemorig as full rw I had to quick toggle safe mode. Now cp all files from the sdcard to their places on the phone turn safe mode off if you had to enable it and reboot. Bam, You just recovered from a soft brick. I have also used this method to restore webtop after breaking that also. Yes it does take a long time to restore and it is cumbersome but at least you can do it. I was also able to mount /emmc to /sdcard and flash a rom from the razr (yes i knew at this point it wouldn't work, this was a test) although it did not boot it did unpack and fully install the rom in the correct locations and it looked as though it would with a little more code boot from the sdcard. What i'm playing with now is trying to use the overclock method from the razr on my a2 but seems how I don't know exactly what files are being changed i'm being cautious. Sorry guys I'm not exactly a linux guy, I do what I can and I am always learning.
I'll edit this post as more info comes to mind. But to let you know I have been able to play with most files w/o fear of bricking so long as you don't mess up the .rc files in /systemorig you will always be able to boot into safestrap.
***MUNKY-TOOL***
IS AN ONBOARD ANDROID UTILITY
FEATURES
[*]Copy system.img
[*]Copy boot.img
[*]Backup efs
[*]Logcat
[*]Backup and Restore Contacts
[*]Out For A Rip
Munky-tool will locate and copy most partitions without you having to track down paths. This is convenient if you use a ROM kitchen, or just want to make a backup of your system without using custom recovery. Some devices do have weird partition names, and munky-tool will not find them. If this happens to you, run the following command in terminal emulator
Code:
ls /dev/block/platform/*/by-name
Paste the output and your device name in the comments, and I will work your device in if possible.
INSTRUCTIONS
Download zip or clone git
Place extracted munky-tool folder in system partition (must be able to set permissions)
Set permissions of munky-tool script (not the directory) to at least 775 (rwx rwx rw)
Open terminal emulator and key in 'su' for root permissions
cd to the munky-tool directory
Type ./munky-tool to execute the script and start the utility
DOWNLOAD
github
Dude once again you're creativity and hard work is paying off. Great job man
Style point for the rip bud!
Sounds very helpfull and as markbencze already replyed I gues it's working on the O+O too. Have to try it in the next days.
thx markbencze for sharing.
SaschaKH said:
Sounds very helpfull and as markbencze already replyed I gues it's working on the O+O too. Have to try it in the next days.
thx markbencze for sharing.
Click to expand...
Click to collapse
Yes. I tested it on my OPO. It went out for a rip. It will run on any device, and it will find the partitions on most.
Where's the download link dude, i'm not find download link from github ?
itsnie said:
Where's the download link dude, i'm not find download link from github ?
Click to expand...
Click to collapse
On the right side of page near the clone url, there should be a button that says download as zip.
Just realized you have to be in desktop view to see the download as zip button. I will post an additional link a little later.
Just added backup and restore contacts.
N-i-c-e!
Thank you.
I've been working on the same sort of thing, and trying to figure out how to get adb connected to the phone with debugging off, for those people (I won't use the word I'm thinking of) who don't make backups, then break the screen, or bootloop the phone. Your script makes finding the data partition trivial, but I'm still working on the "force debugging on from outside" part.
But munky is going to be part of my phone from now on.
Rukbat said:
N-i-c-e!
Thank you.
I've been working on the same sort of thing, and trying to figure out how to get adb connected to the phone with debugging off, for those people (I won't use the word I'm thinking of) who don't make backups, then break the screen, or bootloop the phone. Your script makes finding the data partition trivial, but I'm still working on the "force debugging on from outside" part.
But munky is going to be part of my phone from now on.
Click to expand...
Click to collapse
Thanks, man. Glad to hear you like it.
mike the inkman said:
***MUNKY-TOOL***
IS AN ONBOARD ANDROID UTILITY
FEATURES
[*]Copy system.img
[*]Copy boot.img
[*]Backup efs
[*]Logcat
[*]Backup and Restore Contacts
[*]Out For A Rip
Munky-tool will locate and copy most partitions without you having to track down paths. This is convenient if you use a ROM kitchen, or just want to make a backup of your system without using custom recovery. Some devices do have weird partition names, and munky-tool will not find them. If this happens to you, run the following command in terminal emulator
Code:
ls /dev/block/platform/*/by-name
Paste the output and your device name in the comments, and I will work your device in if possible.
INSTRUCTIONS
Download zip or clone git
Place extracted munky-tool folder in system partition (must be able to set permissions)
Set permissions of munky-tool script (not the directory) to at least 775 (rwx rwx rw)
Open terminal emulator and key in 'su' for root permissions
cd to the munky-tool directory
Type ./munky-tool to execute the script and start the utility
DOWNLOAD
github
Click to expand...
Click to collapse
Good Tool, do you already plan to support restore EFS? which make a full loop of running time change the EFS setting without a PC,
this can help to me to control the modem band preset selections for network testing purpose.
Azlun said:
Good Tool, do you already plan to support restore EFS? which make a full loop of running time change the EFS setting without a PC,
this can help to me to control the modem band preset selections for network testing purpose.
Click to expand...
Click to collapse
It is usually done in bootloader, but I am pretty sure I can make it work. Just need to test it before I release it. I am also going to release this as an apk soon. (Don't know how soon, but I probably won't have time for a few weeks)
An app that we can point new users to that will back up their userdata partition? Fantastic!
Rukbat said:
An app that we can point new users to that will back up their userdata partition? Fantastic!
Click to expand...
Click to collapse
Yeah, I think it will fill a need. I am going to do an APK to do the things from this script, and a corresponding GUI Linux package for APK modding, and maybe do something for Windows as I get time. In the process of moving somewhat unexpectedly, so it is taking longer than I would have liked.
I think this is a universal issue that would apply to any android system. But in case it makes a difference, I've got some Samsung devices. I've got an original Tab S (10.5 inches) and a Note 4 (8 inches). The first is running Resurrection Remix (based on Nougat) and the second is running LineageOS 16.
WHAT I WANT TO DO:
I want to modify some files that live in subdirectories of sys and system. Basic text files, whether XML or anything else. I want to change the configuration settings within the files. I'm rooted and all that. I can edit the files, but after I do, the system puts them back the way they were.
I can only draw one conclusion from this: THE SYSTEM THINKS IT'S BETTER THAN ME, AND IT WANTS TO FIGHT.
I need help. How can I modify the files and have them stay modified? How do I put on my digital boxing gloves and show the system who's boss?
FailSafeNow said:
I think this is a universal issue that would apply to any android system. But in case it makes a difference, I've got some Samsung devices. I've got an original Tab S (10.5 inches) and a Note 4 (8 inches). The first is running Resurrection Remix (based on Nougat) and the second is running LineageOS 16.
WHAT I WANT TO DO:
I want to modify some files that live in subdirectories of sys and system. Basic text files, whether XML or anything else. I want to change the configuration settings within the files. I'm rooted and all that. I can edit the files, but after I do, the system puts them back the way they were.
I can only draw one conclusion from this: THE SYSTEM THINKS IT'S BETTER THAN ME, AND IT WANTS TO FIGHT.
I need help. How can I modify the files and have them stay modified? How do I put on my digital boxing gloves and show the system who's boss?
Click to expand...
Click to collapse
Well it looks like the app's data you want to modify is kept by the app itself and gets restored everytime. It's a security precautions and I don't think you can do much about it. Is it a game or something ?
But if you saw someone modify successfully the XML file without it being constantly restored I can't help you much, maybe uninstall/reinstall will do the trick but tbh it would be kinda weird.
Hope this help, good luck with your fight.
It's not an app. These are system files. They belong to the system itself.
FailSafeNow said:
It's not an app. These are system files. They belong to the system itself.
Click to expand...
Click to collapse
Can you precise the path to the file, it may come handy
FailSafeNow said:
I think this is a universal issue that would apply to any android system. But in case it makes a difference, I've got some Samsung devices. I've got an original Tab S (10.5 inches) and a Note 4 (8 inches). The first is running Resurrection Remix (based on Nougat) and the second is running LineageOS 16.
WHAT I WANT TO DO:
I want to modify some files that live in subdirectories of sys and system. Basic text files, whether XML or anything else. I want to change the configuration settings within the files. I'm rooted and all that. I can edit the files, but after I do, the system puts them back the way they were.
I can only draw one conclusion from this: THE SYSTEM THINKS IT'S BETTER THAN ME, AND IT WANTS TO FIGHT.
I need help. How can I modify the files and have them stay modified? How do I put on my digital boxing gloves and show the system who's boss?
Click to expand...
Click to collapse
Ok, you're rooted, that's only part of what you need in order to modify system files. The next step is, are you using an app that has a "root explorer" built-in and do you have your read/write permissions set to r/w? If you haven't set your read/write permissions to r/w, you won't be able make changes and have those changes persist.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Ok, you're rooted, that's only part of what you need in order to modify system files. The next step is, are you using an app that has a "root explorer" built-in and do you have your read/write permissions set to r/w? If you haven't set your read/write permissions to r/w, you won't be able make changes and have those changes persist.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Yes, I'm using FX, with the root explorer, and the system is mounted read-write.
Let's go with the example I'm most concerned with currently. My Note 4 has sound coming out of the wrong channels. Right and left are switched. I've tried modifying mixer_paths.xml in system/vendor/etc, which is supposed to be a way of fixing this. But the system just changes the file right back.
Edit: The permissions for the System directory are thus: All can read, but only Owner Root can write. Can I change this somehow?
Further update: I rooted my device even more than it was before. I installed the root binary for Lineage OS and set the built-in root to ADB and Apps. I used chmod from a terminal to change permissions for /system, /system/vendor, and /system/vendor/etc to 775. Those permission changes are sticking. But I can't seem to change the xml file so that it stays changed. I even used FX to modify its permission, but it just doesn't work. Nothing doing.