Hey everyone! I am back with a new question / challenge for everyone. I apologize if this sounds too N00B! I searched in the forum and cannot find a solution.
I am trying to make my Galaxy S4 TOTALLY R/W permanently. Rooting only makes the system directory r/w but there are other directories and locations that also need to be accessible as well. When I was back on the MDL firmware I used a linux command to make the entire drive and phone (everything) R/W using the Terminal ... and for the life of me I cannot remember how I did it.
Can anyone help me out with this? I sure would appreciate it. I am tired of copying files and pasting and tricking it to do what I want when I assign permissions or modify a file. If I remember correctly I ran some linux command that made the ENTIRE phone read / write accessible permanently.
Thanks to anyone who can help!
TheDogman said:
Hey everyone! I am back with a new question / challenge for everyone. I apologize if this sounds too N00B! I searched in the forum and cannot find a solution.
I am trying to make my Galaxy S4 TOTALLY R/W permanently. Rooting only makes the system directory r/w but there are other directories and locations that also need to be accessible as well. When I was back on the MDL firmware I used a linux command to make the entire drive and phone (everything) R/W using the Terminal ... and for the life of me I cannot remember how I did it.
Can anyone help me out with this? I sure would appreciate it. I am tired of copying files and pasting and tricking it to do what I want when I assign permissions or modify a file. If I remember correctly I ran some linux command that made the ENTIRE phone read / write accessible permanently.
Thanks to anyone who can help!
Click to expand...
Click to collapse
Still no replies. Holy smokes. Looks like this one stumped everybody. -smiles-
I have the same issue. I have also been searching around for this.
TheDogman said:
Still no replies. Holy smokes. Looks like this one stumped everybody. -smiles-
Click to expand...
Click to collapse
u talking about a simple chmod 666 ?
What would the reason be in doing so ? I only ask to see the reason behind why you would need to do so
hednik said:
What would the reason be in doing so ? I only ask to see the reason behind why you would need to do so
Click to expand...
Click to collapse
+1. Sounds like a disaster waiting to happen.
jd1639 said:
+1. Sounds like a disaster waiting to happen.
Click to expand...
Click to collapse
No disaster. I am just sick and tired of constantly using work arounds when I'm sure there is a way to make the entire file system read / write. I had it this way using the MDL firmware. The only way this would turn into a disaster is if a user got plain stupid with it and deliberately messed with files that he knew weren't to be messed with. Also the comment earlier about a "simple chmod 666" is kind of funny because not all of us are guru's with linux such as some of you are. Please be easy on the guys trying to learn and give back to the community also. Everyone was a N00B once. Don't forget that! -smiles- Anyway thanks for the replies. I will continue my search for the fix!
TheDogman said:
No disaster. I am just sick and tired of constantly using work arounds when I'm sure there is a way to make the entire file system read / write. I had it this way using the MDL firmware. The only way this would turn into a disaster is if a user got plain stupid with it and deliberately messed with files that he knew weren't to be messed with. Also the comment earlier about a "simple chmod 666" is kind of funny because not all of us are guru's with linux such as some of you are. Please be easy on the guys trying to learn and give back to the community also. Everyone was a N00B once. Don't forget that! -smiles- Anyway thanks for the replies. I will continue my search for the fix!
Click to expand...
Click to collapse
I still wonder what it is you are trying to do. Honestly I can't see much of a reason because most things I do are done in Root Explorer (hands down the best file explorer and worth the price) and it's merely clicking the button to make R/W and then altering what it is I need to do. What firmware are you on by the way ? You stated you were on MDL but not now. I might only assume you are on one of the more locked down firmwares like MK2 or MF3 and maybe it is not possible.
The chmod comment was not a dig at anyone and he was asking if that is what you are trying to do as in linux cdmod 666 makes the file system R/W.
What other directories are you trying to make R/W ?
TheDogman said:
No disaster. I am just sick and tired of constantly using work arounds when I'm sure there is a way to make the entire file system read / write. I had it this way using the MDL firmware. The only way this would turn into a disaster is if a user got plain stupid with it and deliberately messed with files that he knew weren't to be messed with. Also the comment earlier about a "simple chmod 666" is kind of funny because not all of us are guru's with linux such as some of you are. Please be easy on the guys trying to learn and give back to the community also. Everyone was a N00B once. Don't forget that! -smiles- Anyway thanks for the replies. I will continue my search for the fix!
Click to expand...
Click to collapse
Wasnt trying to be cute. Open terminal, type su chmod 666 /path/to/folder. As others have said, be very careful what you're setting to rw. Chmod is command to change user perms and 666 is rw.
Sent from my SGH-I337M
Related
Ran across this thread in the evo section, seeing how we also have htc's flash lite. It made me hopeful of attaining root. Ive tried every card mentioned as being successful on three different systems:-(
http://forum.xda-developers.com/showthread.php?t=718889
bowtieduece said:
Ran across this thread in the evo section, seeing how we also have htc's flash lite. It made me hopeful of attaining root. Ive tried every card mentioned as being successful on three different systems:-(
http://forum.xda-developers.com/showthread.php?t=718889
Click to expand...
Click to collapse
Even though I didn't really think it would work, I gave it a shot anyway. Naturally, it was unsuccessful. The Eris take FOREVER to load that website, and it never triggers the shell script to ask for a reload, therefore permission is denied for the second part when you reboot with adb shell.
Interesting exploit, though. I wonder if there is some way to modify it for the Eris. Maybe you could contact the devs.
Really, nobody else is interested in this?
MyFixofAndroid said:
Yep that's what I expected. Yea there's gotta be someone here that can do the changes to the EVO files so they work with Eris, and upload the proper files to file sites and have us downloading in no time, so we can get root finally. Yes please anyone here up and willing
Click to expand...
Click to collapse
Toastcfh used to do some work for the Eris someone may want to start there since he provided what looks to be a pretty main part of the EVO root.
sickbox said:
Toastcfh used to do some work for the Eris someone may want to start there since he provided what looks to be a pretty main part of the EVO root.
Click to expand...
Click to collapse
Thanks for the tip. I sent him a PM. Will report back when I find something.
Anyone with an Eris can help out - rooted or unrooted.
I looked at those scripts last night - what seems like the necessary conditions for the beginning of the exploit (part1) are:
(1) there is a directory read/write/traversal permission security flaw in the data area for flash-lite;
(2) apparently, when flash-lite is running it must have root privilege at a moment when it performs a file "chmod" operation
So, an unprivileged user goes in, and makes a symlink (at the correct moment in time) in flash-lite's data area that points to a mtd partition - moments later, flash-lite "chmods" what it thinks is a file in it's data area, but instead, it is chmod'ing the target of a symlink - the normally protected mtd partition.
This allows use of flash_image to write whatever is wanted to that partition - even as an unprivileged user.
It should be easy enough for someone with Linux/Unix command line scripting experience to test to see if these conditions prevail on the Eris. You don't even need to be root - make your symlink point to something in /data/local if you are worried about something bad happening to a mtd partition. Chmod it initially to 600, and see if it get's changed by flash-lite when (and if) you drop the symlink into place.
I would do it, but I've got to go buy all the parts for ( & build) a new computer (no dev station as of last night ).
bftb0
bftb0 said:
Anyone with an Eris can help out - rooted or unrooted.
bftb0
Click to expand...
Click to collapse
Thank you for the detailed explanation. I'll have a look at the scripts, though it's more about learning new things for me, as this exceeds the current state of my unix knowledge. Hope others with more immediate knowledge of the subject will take a crack at it.
The shell script points to sharedobjects within /data/data/com.android.browser/flashlite, but sharedobjects, nor any folder for that matter, exists within that directory on the Eris. Is there a different place this could point; does the Eris have the same objects stored in a different location?
UPDATE: I'm searching my filesystem on my Eris right now to find it. I will report back later with results.
Also If we find a sharedobjects folder (and the right one) then we can point the script in the proper direction and have root very soon.
MyFixofAndroid said:
Maybe the "sharedobjects" folder and other missing folders are really on the Eris, one of you should look for them. Use ASTRO or a different file manager and search most of the whole filesystem and see if you can find "sharedobjects" on your Erises.
In the meantime I'll try the same thing. Maybe there's a search engine for the file system of the Eris that you can get in the Android Market, that would do the trick. A file and/or folder search engine.
If we find a sharedobjects folder (and the right one) then we can point the script in the proper direction and have root very soon.
Click to expand...
Click to collapse
From what I see (and this may just be my eris), the directory probably does exist but we can't touch it:
ls -l
...
drwxrwx--x system system 2010-04-15 02:23 data
...
No read or write permissions to the directory using adb or Astro.
I do have permissions for /sdcard/data on my Eris:
d---rwxr-x system sdcard_rw 2010-06-26 13:26 data
but it doesn't contain the referenced folders and I don't think the browser downloads temporary files to the SD card.
I checked on my other Eris which is rooted. It seems that these may be the directories that we are looking for. However I don't find anything in an app-cache directory.
# find / -name *flashlite
find / -name *flashlite
/data/data/com.android.browser/flashlite
find: /proc/851: No such file or directory
# find / -name com.android.browser
find / -name com.android.browser
/data/data/com.android.browser
Well this appears to be the deal breaker then. Because non-root users of Eris cannot access /data as non-root, they cannot see anything in app-cache, and therefore cannot root yet, at least with this particular method unless there's another way to do it.
We should think of a way to still exploit Flash Lite on Eris, but use a different folder/folders in the Part? scripts that they point to for the operations of the script. This may be possible to do, however, still unlikely to work, and it is still going to be hard at this point.
But does anyone want to give my modified EVO method but for Eris a try? One of you should, so that we can root this thing and get it over with.
jimbonj said:
From what I see (and this may just be my eris), the directory probably does exist but we can't touch it:
ls -l
...
drwxrwx--x system system 2010-04-15 02:23 data
...
No read or write permissions to the directory using adb or Astro.
I do have permissions for /sdcard/data on my Eris:
d---rwxr-x system sdcard_rw 2010-06-26 13:26 data
but it doesn't contain the referenced folders and I don't think the browser downloads temporary files to the SD card.
Click to expand...
Click to collapse
I dont think we would need read write permissions to begin with to use this root, if we had them to start we would be rooted
Because is he using a exploit in flash lite to write to a restricted folder, hes not just found a folder where the permissions aren't set correctly.
If flash lite can invoke admin access and we can exploit it there should be a way to root this.
I am going to the bar going to get some beers for my friends birthday, when I get home I am going to see if I can modify this into an eris root
Yeah JVWARD!
On your rooting effort, all the better, try modifying it for Eris and let all of us know if you succeed, hope you can, so we can get root too. Keep trying it with different changes until you get it to work.
Thanks.
You are able to cd directly into /data/data/com.android.browser/ and then ls, so all hope may not be lost yet. The flashlite directory does not show up, I'm guessing because I haven't used my browser yet so I need to try and get to a flash site and see if it is created. I'm having some problems with the touch screen my leak Eris right now that I'm trying to fix right now if anyone else wants to give it a shot.
You are able to cd directly into /data/data/com.android.browser/ and then ls, so all hope may not be lost yet. The flashlite directory does not show up, I'm guessing because I haven't used my browser yet so I need to try and get to a flash site and see if it is created. I'm having some problems with the touch screen my leak Eris right now that I'm trying to fix right now if anyone else wants to give it a shot.
Click to expand...
Click to collapse
Yes sickbox, by all means, keep trying stuff, and finding that "flashlite" directory etc. till you get it to root. Hope your touchscreen returns to normal, and that you can create the directory that you mentioned in your previous post by using a flash site.
Hey guys, I know this is a tall order, but I want to help. Any chance you could do a "step by step" set of instructions, or at least copy & paste the Evo instructions with the appropriate changes to try this on the Eris? I'm still not rooted, and the SD card Timing root method isn't working for me. I'd like to try something different.
hey can someone with a rooted Eris using a an almost 100% stock Rom setup dump there file system and post it. Anyone using a highly customized Rom don't bother.
Sent from my Eris using Tapatalk
lostpilot28 said:
Hey guys, I know this is a tall order, but I want to help. Any chance you could do a "step by step" set of instructions, or at least copy & paste the Evo instructions with the appropriate changes to try this on the Eris? I'm still not rooted, and the SD card Timing root method isn't working for me. I'd like to try something different.
Click to expand...
Click to collapse
Link to the Evo instructions is in the OP. Currently working to see if it's possible on the Eris, so that's a no-go for now.
Stay tuned.
Team,
I've been working with the scripts with the awesome folks on IRC and have currently gotten thus far:
Part1 - http://pastebin.com/FUJWM3zW
Part2 - http://pastebin.com/6h07zrdm
I believe at this point I've screwed up my FlashLite plugin with my testing, so I'm going to try to recover that and keep moving along.
LR
OK, I made a zip. Who wants to be my guinea pig? It's at the bottom of the post. (erase -signed and put it on the internal sd)
blackjackboy said:
I guess my idea would be to take the settings.apk from either the Vibrant dump or cyanogenmod 5.0 and push it to /system/app or wherever the settings.apk is located. Does anyone think that this would work or be willing to try it? I'm just worried that this will brick the touchwiz, and without an "original ROM" or RUU and custom recovery, I'm afraid to try it. Is there anyone braver than me?
Click to expand...
Click to collapse
Did you check this thread?
http://forum.xda-developers.com/showthread.php?t=728121
tbae2 said:
Did you check this thread?
http://forum.xda-developers.com/showthread.php?t=728121
Click to expand...
Click to collapse
The thing is, root explorer isn't free. I want to give people an easy, free solution (maybe flashing something from recovery?). For now, ADB will work for me, but in the future I want to provide something flashable from recovery.
Well, the best thing to do, simply run a sql command along with the rooting update.zip.
I will work on this today and get back to you guys soon.
http://androidforums.com/samsung-ca...e-sideloading-apps-captivate.html#post1178618
Been done.
blackjackboy said:
The thing is, root explorer isn't free. I want to give people an easy, free solution (maybe flashing something from recovery?). For now, ADB will work for me, but in the future I want to provide something flashable from recovery.
Click to expand...
Click to collapse
It isn't free but it isn't expensive either. You just dropped a large wad of cash for the phone, seems like another $3 to get it the way you want it wouldn't be such a big deal.
blackjackboy said:
The thing is, root explorer isn't free. I want to give people an easy, free solution (maybe flashing something from recovery?). For now, ADB will work for me, but in the future I want to provide something flashable from recovery.
Click to expand...
Click to collapse
Droid Explorer is.
I'm an android noob but experienced linux user, so I came up with my own free solution: download a terminal emulator app (the one i got was free, and called, simply, Terminal Emulator, I think).
Then (in the terminal emulator):
Copy the settings.db file to the SD card:
To get superuser access so you can get to the settings.db file (need a rooted phone, obv):
Code:
$su
And confirm the popup allowing access.
Code:
#busybox cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
Then hook up your phone via USB (mass storage method) and use your window manager to copy that from the phone to the computer, edit with an SQL database browser, save it, verify it's still good, move it back to the SD card, then, back on the phone in the terminal emulator:
To get superuser access again:
Code:
$su
Shouldn't have to confirm the popup allowing access again, as the first time appears to do it.
Move the original file to a backup name (just to be safe):
Code:
#busybox mv /dbdata/databases/com.android.providers.settings/settings.db /dbdata/databases/com.android.providers.settings/settings.db.old
Copy the new (edited) file into place:
Code:
#busybox cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings/settings.db
Then reboot, and enjoy the ability to install non-market apps. My first install was Flash 10.1. Works fine on the Captivate.
blackjackboy said:
The thing is, root explorer isn't free. I want to give people an easy, free solution (maybe flashing something from recovery?). For now, ADB will work for me, but in the future I want to provide something flashable from recovery.
Click to expand...
Click to collapse
Grab Android Mate from the market, it is free and has root level exploration
blackjackboy said:
OK, I made a zip. Who wants to be my guinea pig? It's at the bottom of the post. (erase -signed and put it on the internal sd)
Click to expand...
Click to collapse
This might also work, I have used it, pretty simple
http://m.androidcentral.com/sideload-android-apps-all-you-want-sideload-wonder-machine
Superoneclickroot has a one click enable non market apps next to the root button, fyi.
terrymc said:
This might also work, I have used it, pretty simple
http://m.androidcentral.com/sideload-android-apps-all-you-want-sideload-wonder-machine
Click to expand...
Click to collapse
Smasher816 said:
Superoneclickroot has a one click enable non market apps next to the root button, fyi.
Click to expand...
Click to collapse
:faceplam:
bump a year old thread? with these no less....
whats wrong with bumping a (insert # here) old thread? it hasnt been closed or deleted. as long as info pertaining to the OP is being posted shouldnt it be a non-issue? now if it was bumped with something like 'why bump this fossil thread?' then that would be a pointless bump. i gained info from the 1 year late post about superoneclick and thanked the guy for posting it.
EDIT: you spelled 'facepalm' wrong.
Well first it shouldn't even be here in development. And second thread closed.
Okay unfortunately 5 mins after rooting my phone I noticed my replacement Vibrant has a bad screen. I used the one-click program to root, so I did the same thing to unroot. I downloaded ROM Manager after I unrooted to confirm the phone was unrooted and ROM Manager seems to think so (it told me to root my phone).
However, I am wondering if there is any way to *confirm* my phone has been unrooted (i.e. manually look for the root files and make sure they are not there)? I ask because I reset my phone to factory settings after unrooting, but updated.zip and chromemod folder were still present when I looked under files, which sort of scared me into thinking T-Mobile may be able to detect I had rooted.
Thanks for all the help and wish me luck for my *third* Vibrant.
DarkAgent said:
Okay unfortunately 5 mins after rooting my phone I noticed my replacement Vibrant has a bad screen. I used the one-click program to root, so I did the same thing to unroot. I downloaded ROM Manager after I unrooted to confirm the phone was unrooted and ROM Manager seems to think so (it told me to root my phone).
However, I am wondering if there is any way to *confirm* my phone has been unrooted (i.e. manually look for the root files and make sure they are not there)? I ask because I reset my phone to factory settings after unrooting, but updated.zip and chromemod folder were still present when I looked under files, which sort of scared me into thinking T-Mobile may be able to detect I had rooted.
Thanks for all the help and wish me luck for my *third* Vibrant.
Click to expand...
Click to collapse
You can test this to un-root.
https://www.dropbox.com/s/pyg5sypm9qto7rw/Galaxysroot.apk
I wrote it today. with help.
its posted on another thread.
Erm.. couldn't you just download Terminal Emulator (if it already isn't installed) and type in: "su" (without quotations)
zephiK said:
Erm.. couldn't you just download Terminal Emulator (if it already isn't installed) and type in: "su" (without quotations)
Click to expand...
Click to collapse
^^I second this, if you are not rooted, you will get a "su not found" type of error.
Also in this thread http://forum.xda-developers.com/showthread.php?t=728471 you will find
How to unroot
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
you could also do it from adb.
rhcp0112345 thanks for the app but I think the su way sounds easier.
Thanks zephiK and d_bot! I did the su thing and got a "su not found" error so I guess I am good.
Lakjin said:
rhcp0112345 thanks for the app but I think the su way sounds easier.
Thanks zephiK and d_bot! I did the su thing and got a "su not found" error so I guess I am good.
Click to expand...
Click to collapse
Yep, no su, no root
New to Andriod, sry for noob question, What are the benefits to Root, What changes on your phone??
30Glock said:
New to Andriod, sry for noob question, What are the benefits to Root, What changes on your phone??
Click to expand...
Click to collapse
Well, I know there will probably be a lot of people freaking out on me, but from how I use my phone the only use I've had so far is using cachemate to clear cache, and possibly modding the look of the os. I personally used to it to remove the annoying tmo boot and shutdown sounds/video.
30Glock said:
New to Andriod, sry for noob question, What are the benefits to Root, What changes on your phone??
Click to expand...
Click to collapse
Welcome to Android 30Glock
the main benefit of rooting is to be able to remove bloat-ware. Bloatware plagues the vibrant. Besides that there are other things you can do like custom roms(not many for the vibrant but they will come), with custom roms comes custom themes, also you can increase you cpu frequency. There are a few awesome apps out there that require root (Titanium Backup).
Basically think of it as you have just been given a new windows machine at work, and the admin gave you User permissions, so yeah you can do some cool stuff, but to really get in and have some fun you need admin permissions. To root/unroot this phone it is jaw dropping easy! Thank you samsung. Thank you DEVS!
Install Root Explorer and try to navigate to your system folder.
Moved to general section.
I am picking up a Fascinate today and have been looking here and other forums but can not find anything. I want to put it back to stock then root at some point but I do not see anything about doing so with Ubuntu. Anyu way to do it?
rllong1 said:
I am picking up a Fascinate today and have been looking here and other forums but can not find anything. I want to put it back to stock then root at some point but I do not see anything about doing so with Ubuntu. Anyu way to do it?
Click to expand...
Click to collapse
As good as it'll get...for now
http://androidforums.com/fascinate-a...ng-ubuntu.html
Thanks for the link. It was broken but I found it.
rllong1 said:
Thanks for the link. It was broken but I found it.
Click to expand...
Click to collapse
huh...sorry bout that. But at least you know it's out there lol
Just in case any one is looking...
http://androidforums.com/fascinate-all-things-root/236081-how-root-using-ubuntu.html
Corrected the link ^^
Do you have any experience with Ubuntu, when I try putting in a few commands, I am getting some errors. I figure it would be helpful to talk to someone who knows.
rllong1 said:
Do you have any experience with Ubuntu, when I try putting in a few commands, I am getting some errors. I figure it would be helpful to talk to someone who knows.
Click to expand...
Click to collapse
Yeah, I was using 10.1 I believe however found it incredibly difficult which forced me to load a windows partition. What error are you getting?
Yeah its easier to partition then use odin youll get that done quicket
Blue Super Froyo
I do not have a copy of windows or I would do that. I put this command, just the second one.
mv ~/Desktop/tools/adb ~/bin/
Then I get no such file or directory.
rllong1 said:
I do not have a copy of windows or I would do that. I put this command, just the second one.
mv ~/Desktop/tools/adb ~/bin/
Then I get no such file or directory.
Click to expand...
Click to collapse
Did you download SDK, create the bin file and drag the adb into it?
Yes I did, I am just so lost with Ubuntu
How hard would it be to create a script that runs on boot that formats /system if su is detected?
And could it be made into a flashable zip to be used on any phone?
Very happy to throw a nice donation your way if it can be done.
Thank you.
iBowToAndroid said:
How hard would it be to create a script that runs on boot that formats /system if su is detected?
And could it be made into a flashable zip to be used on any phone?
Very happy to throw a nice donation your way if it can be done.
Thank you.
Click to expand...
Click to collapse
It's not hard at all, but why would you want to do this?
abnormalreply said:
It's not hard at all, but why would you want to do this?
Click to expand...
Click to collapse
Ha. I spose that sounds a little suspicious. It's a long story, but basically I just want a script that I can run on a few of my devices so I can test out a few things, mainly via recovery and adb, really just making sure I can recover if something like that happens. Yeah I could wipe from recovery but I'd rather simulate the real thing, or if I have stock recovery, etc. I know a tiny bit about init but not enough to know how to write the script so I just figured it would be easier and quicker for someone to do it who actually has experience. I also realized that there's no need for a zip since I can just copy the script to any device I need. Basically "if /system/bin/su or /system/xbin/su exists, then format /system" - something like that, although I know the formatting is different. Yes I understand what I'm doing and the risks and have the restoration tools ready lol
iBowToAndroid said:
Ha. I spose that sounds a little suspicious. It's a long story, but basically I just want a script that I can run on a few of my devices so I can test out a few things, mainly via recovery and adb, really just making sure I can recover if something like that happens. Yeah I could wipe from recovery but I'd rather simulate the real thing, or if I have stock recovery, etc. I know a tiny bit about init but not enough to know how to write the script so I just figured it would be easier and quicker for someone to do it who actually has experience. I also realized that there's no need for a zip since I can just copy the script to any device I need. Basically "if /system/bin/su or /system/xbin/su exists, then format /system" - something like that, although I know the formatting is different. Yes I understand what I'm doing and the risks and have the restoration tools ready lol
Click to expand...
Click to collapse
I'm surprised you're able to test recovery/ADB scripts on your devices but don't know how to write the script you're describing.