First off, I have a Nexus S 4g from Sprint (d720) rooted using the method as posted in the thread titled "[GUIDE] Nexus S 4G Simple Root/Unroot" by kpkimmel back a few weeks ago when that was the ONLY method available.
I am trying to edit an XML file located in my /root/data/data/ directory but I can't access it from adb shell nor the app "Root Explorer", I can however see and 'cd' to the directory but it shows up empty on both "Root Explorer" and through adb . As it seems, I don't have the proper permissions to be able to view/edit the files/folders in the root folder.
SuperUser permissions have been granted for both adb shell and Root Explorer as well so I know that part is in order. I guess I could just be missing an obvious step in accessing the /root/data folder but any help would be greatly appreciated.
Should I just unroot my device and re-root using a different method? Anybody with adb and permissions issues experiences please help. I'm more than frustrated at this point.
Thanks in advance.
try mounting it as rw
Would you be able to list the steps please?
Top right of the page, hit read write
Sent from my Nexus S 4G using Tapatalk
My /root contains nothing either. What is it exactly you want to edit?
its a empty folder.
Related
With certain files, SteelH describes using Root Explorer as "like trying to swap the engine of a car while it's running"
I experienced this as I tried to copy back a modified services.jar file with Root Explorer. I ended up using ADB and it worked fine.
Question 1: I did this while the phone was running/OS loaded, but ADB copy method worked while Root Explorer didn't. Why? Does ADB have higher authority in some way?
Question 2: How about using a terminal window on the phone to copy/replace files (if a computer is not handy)? Does it yield the same function/result as Root Explorer or ADB?
Question 3: If I simply want to back up the file, say services.jar or framework.apk, to be copied to SD, can I use Root Explorer for that?
Thanks.
snovvman said:
With certain files, SteelH describes using Root Explorer as "like trying to swap the engine of a car while it's running"
I experienced this as I tried to copy back a modified services.jar file with Root Explorer. I ended up using ADB and it worked fine.
Question 1: I did this while the phone was running/OS loaded, but ADB copy method worked while Root Explorer didn't. Why? Does ADB have higher authority in some way?
Question 2: How about using a terminal window on the phone to copy/replace files (if a computer is not handy)? Does it yield the same function/result as Root Explorer or ADB?
Question 3: If I simply want to back up the file, say services.jar or framework.apk, to be copied to SD, can I use Root Explorer for that?
Thanks.
Click to expand...
Click to collapse
i can't answer all of these authoritatively, but i will say
-i find adb to be the easiest way to do ANY modifications, as long as you know just a handful of commands and remember to remount. also remember to pull anything you are getting ready to mess with, just in case you bork it up. takes a lot less time to push an unmodified file than it does to do a complete restore. especially if you forgot to backup, lol
-if you have a terminal app mounted with rw privileges, you can move whatever you want wherever you want. however, referring back to my last point, adb is easier. i find that trying to type type type things out on a dinky little keyboard is a bigger pain in my butt than using my full size one, especially when i can use cut/paste from the intertubes.
-i think rooted explorere shouldn't have a problem copying a file from /system/ or /data/ to some folder on your sdcard
Thank you for the information. I just copied a file with terminal (on phone) and Root Explorer. Interesting thing: using the CP command, the file that was copied onto the SD showed the current date. The file that was copied using RE has the original date.
i tried the search and google but find nothing on this. Im not new to rooting, i rooted my OG droid, but now im trying to root my Mt4g and having trouble. I have the .86 boot loader and im trying to do the gfree method of rooting. Only problem is when i go to transfer my gfree files to data/local, i cant find data local. Im using astro file manager and i hit the up button to get as far as i can go. Once i do that i select the data folder, and it just says empty directory. so i can find /data, but not /data local. Thanks for taking the time to read my question.
Astro file manager will not show the /data/local folder. If you don't have root you have to push gfree using adb.
i'm on a 4g slide with this same problem, i need to move a file to the /data/local, and my file managers cannot find 'local', and do not let me create one.
i am already rooted.
leoilios said:
i'm on a 4g slide with this same problem, i need to move a file to the /data/local, and my file managers cannot find 'local', and do not let me create one.
i am already rooted.
Click to expand...
Click to collapse
you need to use a root explorer.
or use the line command
Code:
adb push <file_name> /data/local
Another thing you could do is download visionary, temp root, use a root required file manager to move the file to data/local. Then un temp your phone an run gfree
From my fist to your face, enjoy.
Please forgive me if this is covered in an earlier thread. I searched several different ways and found nothing.
I've been temp rooted with Visionary for a several months now with no real problems. Recently I decided to perma-root and try some other ROMs. I double checked all my settings and downloaded the appropriate root files and loaded them to the root directory of my sd card. When I open the Terminal Emulator and start going through the commands:
su
cd/sdcard/root
I get a "cd/sdcard/root: not found" response...?
I've double checked the location of the Root folder both using a file explorer and connecting to my computer. Is it my sd card? I haven't had any problems that I know of...?
Any help would be appreciated...
What bootloader do you have
pedaler said:
Please forgive me if this is covered in an earlier thread. I searched several different ways and found nothing.
I've been temp rooted with Visionary for a several months now with no real problems. Recently I decided to perma-root and try some other ROMs. I double checked all my settings and downloaded the appropriate root files and loaded them to the root directory of my sd card. When I open the Terminal Emulator and start going through the commands:
su
cd/sdcard/root
I get a "cd/sdcard/root: not found" response...?
I've double checked the location of the Root folder both using a file explorer and connecting to my computer. Is it my sd card? I haven't had any problems that I know of...?
Any help would be appreciated...
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA Premium App
You're missing the spaces.
And "root directory" means - NO directory. You should have copied the files to your SD card without putting them into any directory on it.
The command looks like that/:
cd /sdcard/
Make sure you didn't unzip the files...
Edit: sorry, don't unzip roms! But you haven't gotten that far! Sorry about that, my mistake.
Sent from my HTC Glacier using XDA App
pedaler said:
Please forgive me if this is covered in an earlier thread. I searched several different ways and found nothing.
I've been temp rooted with Visionary for a several months now with no real problems. Recently I decided to perma-root and try some other ROMs. I double checked all my settings and downloaded the appropriate root files and loaded them to the root directory of my sd card. When I open the Terminal Emulator and start going through the commands:
su
cd/sdcard/root
I get a "cd/sdcard/root: not found" response...?
I've double checked the location of the Root folder both using a file explorer and connecting to my computer. Is it my sd card? I haven't had any problems that I know of...?
Any help would be appreciated...
Click to expand...
Click to collapse
If i remember correctly its cd /data/local not cd/data/local make sure you hit the space bar between cd and /
This was the culprit....I didn't have a space in the correct place. I can't believe I over looked that one...Thanks
Hi everyone. As a new Kindle Fire user, I bought mine AFTER the recent Kindle 6.2 update. After following step-by-step the instructions posted on this forum to root KF, I seemed to have succeeded at my first attempt. However, when trying to copy and paste either vending.apk or amarket.apk to system/app folder using File Expert which I got from Amazon store, I couldn't get it to work. This means I don't see either apps in the system app folder after I paste them there. I followed the instructions to the T and rebooted KF, still no show. I then tried to install it via adb, I was able to "adb install" googleservice frameworks on KF. But when trying to "adb push" the market app to system/app, I keep getting "adb access denied". I tried re-rooting with superoneclick, still can't "adb push".
I really don't know what went wrong. BTW, I could hard install the market app on to KF and gained access to the market. (I thought KF blocked it.) But all my download from android market seem unsuccessful. I need help. Thanks.
Problem solved. And here's what I found out and how I made it work. Thanks for everyone who posted to help.
After trying what everyone suggested here, I still couldn't get r/w perssion to the system folder. I reset my KF to factory setting and started all over again. This time I realized it was the File Expert app that's causing this problem. Although it seems like File Expert could gain full access to the system, it doesn't allow you to make any modification to the system folder. I know someone claimed it worked on theirs. But if your File Expert comes from Amazon app store, it DOES NOT work when you try to paste anything into the system. When I realized that ROOT EXPLORER is no longer available on Amazon, I figured that could be the reason. After downloading Root Explorer to my PC and installed it onto KF, everything worked like a charm! So for those of you who encounter similar problems, it's not you. It could be the File Expert app that you got from Amazon.
You need to mount system as writable
Thanks Felnarion. But I did that. It didn't help. I followed the instructions step by step. Don't where the problem is. I find it hard to believe that KF allows me to do regular install of android market(the market icon even shows on the carousel) but I can't do it the "sneaky" way? Anyone else tried installing market app directly from the sd card?
In that case I think it's your app. I just downloaded file expert and had problems copying to /system as well.
Try root explorer, haven't had any problems with it.
File Expert is broken in regards to mounting folders RW/RO. Even though it claims it has successfully changed permissions, it never does or they don't stick. I suffered the exact same issue, regarding mounting folders RW/RO, and had to install Root Explorer to get the job done.
Code:
mount -o rw,remount -t ext4 /dev/block/platform/mmci-omap-hs.1/by-name/system /system
is the adb command
nycrare said:
However, when trying to copy and paste either vending.apk or amarket.apk to system/app folder using File Expert which I got from Amazon store, I couldn't get it to work. This means I don't see either apps in the system app folder after I paste them there. I followed the instructions to the T and rebooted KF, still no show. I then tried to install it via adb, I was able to "adb install" googleservice frameworks on KF. But when trying to "adb push" the market app to system/app, I keep getting "adb access denied". I tried re-rooting with superoneclick, still can't "adb push".
Click to expand...
Click to collapse
This might be a dumb question, but did you
Code:
su
and click OK on the Superuser prompt on the KF screen prior to the adb push attempts? Were you able to mount /system rw through adb? If adb can't get root access there's no way File Expert will be able to.
devilot said:
File Expert is broken in regards to mounting folders RW/RO. Even though it claims it has successfully changed permissions, it never does or they don't stick. I suffered the exact same issue, regarding mounting folders RW/RO, and had to install Root Explorer to get the job done.
Click to expand...
Click to collapse
File Expert works fine. I've used it to do all my root related installs. You just have to make sure you check the 'Root Explorer' box under Settings>File Explorer Settings before trying to do any /system mounts, it's off by default.
Thank you everyone for your help. If I remember correctly, I did try "su" in adb. but not sure if entered the code correctly. I also heard about File Expert could be the cause when it comes to gaining permissions. I checked root explorer on File expert settings as well. I'm beginning to wonder if my hard install of market app ,which worked to my surprise, messed things up. I will try to reset my KF to factory setting and start over again. I will report back with the result. Once again, I really appreciate everyone's help.
death2all110 said:
Code:
mount -o rw,remount -t ext4 /dev/block/platform/mmci-omap-hs.1/by-name/system /system
is the adb command
Click to expand...
Click to collapse
i have to admit this is the first time I see this code. I tried something similar based on an instruction from another site. But not this exact code. I will try it later.
that command line was a life saver
Saved me a future headache
nycrare said:
After trying what everyone suggested here, I still couldn't get r/w perssion to the system folder. I reset my KF to factory setting and started all over again. This time I realized it was the File Expert app that's causing this problem. Although it seems like File Expert could gain full access to the system, it doesn't allow you to make any modification to the system folder. I know someone claimed it worked on theirs. But if your File Expert comes from Amazon app store, it DOES NOT work when you try to paste anything into the system. When I realized that ROOT EXPLORER is no longer available on Amazon, I figured that could be the reason. After downloading Root Explorer to my PC and installed it onto KF, everything worked like a charm! So for those of you who encounter similar problems, it's not you. It could be the File Expert app that you got from Amazon.
Click to expand...
Click to collapse
Interesting. I was the one it worked for and I'm pretty sure I got mine from the Market, not Amazon. Good thing I haven't clicked that update button from within Amazon App Store.
Thank you for following up. Perfect example of how it can help others.
Glad you got everything sorted.
This may amount to a n00b question, but here goes: After rooting my Kindle(7.2.3), my GF decided she loved the new look and functionality of it so she wanted me to do the same. Hers was on 7.3, which made the process different, but I was able to do it successfully. I've already installed Market and Google Play, and am now trying to remove the ads by changing Dtcp_apk.apk to Dtcp_apk.bat. However, I keep getting an Operation Failed message. I realize this has to do with changing the permissions, but I can't for the life of me remember how to do it, or where exactly I read it when I rooted my personal Kindle. Any help would be greatly appreciated.
So...
Code:
adb shell su -c "mount -o remount,rw ext4 /system"
adb shell su -c "mv /system/app/dtcp_apk.apk /system/app/dtcp_apk.bak"
...doesn't work?
And now, my n00bness shall shine through. Haha. After I rooted the first Kindle(7.2.3), I only had to change the dtcp_apk.apk file to dtcp_apk.bat and it worked like a charm. The method you are describing, I am not familiar with. Is that something I do within a cmd window? I apologize for not knowing, I just didn't have to do it before...
Yes, those are entered from the command line. The first one remounts the system partition as read/write, allowing changes to be made to that partition. The second one simply renames the file so the system can't find it. The "su -c" part tells the shell to run the commands as the root user, needed on stock systems.
I'm guessing your file manager your using doesn't have full root access I use es file explorer and you go into settings root settings and check them all then you can rename that file you don't have to learn to use adb to do this...
Sent from my GT-P3110 using xda app-developers app
mrkhigh said:
I'm guessing your file manager your using doesn't have full root access I use es file explorer and you go into settings root settings and check them all then you can rename that file you don't have to learn to use adb to do this...
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
AHA!!!! This was exactly what I did the last time, but couldn't remember this time around. Worked like a charm. Thank you both for the responses and the help. :victory: