Database Info

Read-Only Filesystem?

Hello, all!
I'm trying edit a file in /etc/ and adb says 'Failed to copy: Read-only filesystem'
Now, is this actually true? Or is this simply a permissions issue? I'm doing this on a non-rooted phone, so I can't 'touch' anything without permission errors, but is it a futile task if the filesystem is read only anyway?
I'm trying to do this from a non-rooted environment as I had intended on making this into an application, but I imagine that if I can't touch or push these files from an adb shell then I won't be able to from the application space either.
It's frustrating not to be able to edit the filesystem of my own phone, I'll be rooting if this is just a permissions problem and not an issue of a non-writable filesystem. Perhaps I could still make an application for rooted-only phones.. hrm..
Any thoughts on this?

/etc is an alias for /system/etc, and /system is a partition mounted as ro (you can confirm this yourself by running mount)

Ah, bugger. So this is hopeless (without modifying and then reflashing)?
Thanks very much.

you need to mount it read write,
mount -oremount,rw /dev/block/mtdblock3 /system
then it will be read/write

try adb remount. if it failes you need root sorry.

Hello, i have the same error and I have root. i have tried adb remount and the mount -oremount,rw /dev/block/mtdblock3 /system
still dotn work. I want to move a script to /
so i only have to type sh debian.sh
nvm I figured it out. i just put it on system and then just type sh debian.sh on the terminal and it works

Rafase282 said:
Hello, i have the same error and I have root. i have tried adb remount and the mount -oremount,rw /dev/block/mtdblock3 /system
still dotn work. I want to move a script to /
so i only have to type sh debian.sh
Click to expand...
Click to collapse
what is the error message? saying it dont work doesnt provide enough info for us to help....

it says sh: cant open aw.sh
so i still have to put the path or cd to where the file is. Is there a way to make /system my home?

no you cant make system your home, system is system, home is home. you can make a symlink if you are familiar with linux - might want to read up about shell commands

korndub said:
you need to mount it read write,
mount -oremount,rw /dev/block/mtdblock3 /system
then it will be read/write
Click to expand...
Click to collapse
Thanks it really worked!! for me i had the same problem as the other guy.

Rafase282 said:
Hello, i have the same error and I have root. i have tried adb remount and the mount -oremount,rw /dev/block/mtdblock3 /system
still dotn work. I want to move a script to /
so i only have to type sh debian.sh
nvm I figured it out. i just put it on system and then just type sh debian.sh on the terminal and it works
Click to expand...
Click to collapse
You *CAN'T* modify the / filesystem. It is part of your BOOT partition, which CANNOT be remounted rw. You would have to read, modify, and write the boot partition.

Rafase282 said:
Hello, i have the same error and I have root. i have tried adb remount and the mount -oremount,rw /dev/block/mtdblock3 /system
still dotn work. I want to move a script to /
so i only have to type sh debian.sh
nvm I figured it out. i just put it on system and then just type sh debian.sh on the terminal and it works
Click to expand...
Click to collapse
Maybe you're typing it in too literally. It should actually read like this:
mount -o remount,rw /dev/block/mtdblock3 /system
There was a typo with -oremount, there should be a space after -o.
Hope that helps.
PS. That command worked for me on a device where everything else failed.

dhkr123 said:
You *CAN'T* modify the / filesystem. It is part of your BOOT partition, which CANNOT be remounted rw. You would have to read, modify, and write the boot partition.
Click to expand...
Click to collapse
actually, / can be mounted rw, but changes are lost on reboot

new user
Firerat said:
actually, / can be mounted rw, but changes are lost on reboot
Click to expand...
Click to collapse
Hi I have my Asus Prime rooted and installed a virtuous Rom and I tried to put a fonts on the System/ fonts folder using root explorer using a instructions to fix some error on some games that need that tis fonts exist on the tablet but it said it cant because file system is read only I'm new and I don't know how to do this commands any help on how to do in a easy (explained) form.

egalpr said:
Hi I have my Asus Prime rooted and installed a virtuous Rom and I tried to put a fonts on the System/ fonts folder using root explorer using a instructions to fix some error on some games that need that tis fonts exist on the tablet but it said it cant because file system is read only I'm new and I don't know how to do this commands any help on how to do in a easy (explained) form.
Click to expand...
Click to collapse
I would recommended not posting in the g1 section. The Asus forums would be a lot more helpful.

egalpr said:
Hi I have my Asus Prime rooted and installed a virtuous Rom and I tried to put a fonts on the System/ fonts folder using root explorer using a instructions to fix some error on some games that need that tis fonts exist on the tablet but it said it cant because file system is read only I'm new and I don't know how to do this commands any help on how to do in a easy (explained) form.
Click to expand...
Click to collapse
Download EStrong File Manager and within the settings of it, enable mounting of the system as read/write.
Or, download Terminal Emulator and type this in:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
Or, try typing this in terminal/cmd:
Code:
adb remount
Or, if you plan on doing it all from recovery you could do:
Code:
adb shell "mount system"
and then you could do it all from there.
Next time, please post in the proper forum.

Read-Only /system... i just deleted the file, tich push should update/replace and then it worked... only had this bug when i was trying to modify Trebuchet.apk (homescreen)

Hi guys
Not being a linux expert, i'm stuck with the following problem..
i'm using a program who uses low level adb commands to write on the phone extSdCard...
problem: this extSdcard is seen as a readonly filesystem.
What has to be done to make this FS RW instaed of RO ?
This does not happen under windows where I can write to the extSd without problems
thks in advance for the tip

[Q] how to edit GPS.conf in system folder ?

I would like to set my phone to europe.pool.ntp.org becouse it's default northamerica.pool.ntp.org
How can I edit this file ? When I try to type adb shell to terminal it gives me an error message.
Thanks
Not development related moved to General

At first U must root R phone and then install Root Explorer. After that go to SYSTEM/ETC/
Here u need to edit GPS.CONF file and change NTP Server from northamerica.pool.ntp.org to europe.pool.ntp.org.
I hope that I help U m8.

Get write acces in system folder
I used the post I've quoted down here. After you have gained write acces in the system folder you can edit gps.conf!
octy said:
By default the /system is mounted in read-only mode.
With 'root' access you can change this.
First 'root' your phone with tutorial 'slumpolo' has provided at
the begining of this thread.
Then open a shell on your phone with adb
Code:
adb shell
Grant 'root' access with 'su' command and have a look of memory partitions
Code:
su
mount
In 'mount' command output, identify the partition on which /system was mounted.
In my phone it was '/dev/block/stl6'
Finally you can remount it to get read-write permissions on it.
But before be sure to be outside /system in the shell (by typing 'cd /' for example).
Code:
mount -o remount,rw /dev/block/stl6 /system
Do the modification you want..... BECAREFUL of want you do, you can damage your phone.
Set read-only mode again
Code:
mount -o remount,ro /dev/block/stl6 /system
Sorry I cannot made any snapshot for the moment, I can't use my phone.
Hope it can help you.
Click to expand...
Click to collapse

By the way, for Slovakia I think you can better change to sk.pool.ntp.org
Complete list of European NTP servers:
http://www.pool.ntp.org/zone/europe
Other area's:
http://support.ntp.org/bin/view/Servers/NTPPoolServers

LeoApollo said:
By the way, for Slovakia I think you can better change to sk.pool.ntp.org
Complete list of European NTP servers:
http://www.pool.ntp.org/zone/europe
Other area's:
http://support.ntp.org/bin/view/Servers/NTPPoolServers
Click to expand...
Click to collapse
I see, probably I can use also CZ, HU, AT, DE or SK or EU .. I've red that the best is with more sites.
"After you have gained write acces " How can I gain write access ? I have rooted - but Adb shell doesn't work, did I missed something ? Thaks

nastyba said:
"After you have gained write acces " How can I gain write access ? I have rooted - but Adb shell doesn't work, did I missed something ? Thaks
Click to expand...
Click to collapse
i think yes adb is for the PC. it is part of the android sdk tools.

i did that on my desire (it should be same) but i have problem i edit and save file and now i cant see it
i can see that backup file but how do i restore it?
i tried create new file it wont work i cant see it (it says file created sucessfuly)

aantdesign said:
At first U must root R phone and then install Root Explorer. After that go to SYSTEM/ETC/
Here u need to edit GPS.CONF file and change NTP Server from northamerica.pool.ntp.org to europe.pool.ntp.org.
I hope that I help U m8.
Click to expand...
Click to collapse
U can use adb on Win or linux or qtadb.
Give these commands on adb shell..
su
mount -o remount,rw /dev/block/stl6 /system
exit
exit
adb pull /system/etc/gps.conf
Edit the gps.conf the way u like.
Then mount again in rw mode.
adb push gps.conf /system/etc/gps.conf
adb reboot
Done.

moved
new post @sgs2

nastyba said:
I would like to set my phone to europe.pool.ntp.org becouse it's default northamerica.pool.ntp.org
How can I edit this file ? When I try to type adb shell to terminal it gives me an error message.
Thanks
Not development related moved to General
Click to expand...
Click to collapse
U can use the apo "FasterFix" from market.

arunmcops said:
U can use the apo "FasterFix" from market.
Click to expand...
Click to collapse
Thanks for the tip much easier to change with this application done in seconds

[Q] [i9020a] Nexus S - can't remove / rename install-recovery.sh

Hello,
I have a Nexus S which I am trying to root and flash CWM recovery on. I've followed "The Unlockr's Guide" which was a tremendous help as well as kursk's "Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9023 and i9020A)".
I am having issues however, renaming / removing the "install-recovery.sh" script. I've tried to rename it using Android Mate. I get the error message "failed to rename to install-recovery-no.sh".
I've also tried to use ADB Shell by trying:
"mount -o rw,remount /dev/block/mtdblock3 /system" which go the following error:
mount: operation not permitted
so I couldn't perform the rename using the mv command.
I really don't know what else to try... Any help would be appreciated.
Thanks.

Just start from begin again and use this guide. I have also i9020a and I was done in 15 minutes, newer did it before with Nexus S. good lack

Wrong thread sir!!!
However, back on subjkect,
type adb shell
cd to /
the cd to system/etc
from there, # mv install-recovery.sh install-recovery.sh.bak
if you are still having problems, i have a zip file removing this recovery-install.sh script. forgot who was the author though.( just saying so that you know merit goes to someone else) . just fflash from recovery.
http://db.tt/ooDaCnU

I just renamed it using root explorer. Worked fine for me

Thanks deeren,
That worked. It removed the recovery-install.sh script altogether. One question, if I ever want to go back to the stock recovery, is there a script I can use to bring it back?
deeren said:
Wrong thread sir!!!
However, back on subjkect,
type adb shell
cd to /
the cd to system/etc
from there, # mv install-recovery.sh install-recovery.sh.bak
if you are still having problems, i have a zip file removing this recovery-install.sh script. forgot who was the author though.( just saying so that you know merit goes to someone else) . just fflash from recovery.
Click to expand...
Click to collapse

AnalogTrail said:
Thanks deeren,
That worked. It removed the recovery-install.sh script altogether. One question, if I ever want to go back to the stock recovery, is there a script I can use to bring it back?
Click to expand...
Click to collapse
If you are on stock rom, then you can just reflash any stock rom (without wiping , so that you do not loose your data) and it will put back the script back.
you could also pull the script from any stock rom and push it back to your phone using adb.

move along, empty post, nothing to see here

I think..just flash any Stock ROM..
and your Stock Recovery will be back...
cmiiw

deeren said:
Wrong thread sir!!!
However, back on subjkect,
type adb shell
cd to /
the cd to system/etc
from there, # mv install-recovery.sh install-recovery.sh.bak
if you are still having problems, i have a zip file removing this recovery-install.sh script. forgot who was the author though.( just saying so that you know merit goes to someone else) . just fflash from recovery.
http://db.tt/ooDaCnU
Click to expand...
Click to collapse
Can You tell me how to use that script ., I mean I am a noob . Can you tell me what exactly to do with that file. Coz I have been trying to remove that .sh file for 6 hours now. No matter what i do ., whenever i run the android recovery it creates a new file again and shows that triangle with exclamation screen ., :'(

Rooting 2.3.6 Samsung Replenish!!! Success!!!

alt link: http://forums.androidcentral.com/sa...-guide-stock-2-3-6-replenish.html#post1651482
REVISED TUTORIAL IN ROOTING 2.3.6 SAMSUNG REPLENISH
warning for experienced adb users!: this was made with noobs in mind. you may learn something (from me! a noob! XD) but anyways, enjoy!
this does not affect anything on the phone except for adding the ability to access root permissions. CWM is not permanent, it disappears after you use it, and nothing on the phone is affected, as far as i know, but i had just factory reset the phone, so use at your own risk...
you may need to know:
root of a drive- drives are designated C:\ or D:\ or whatever letter in windows. Just go to "computer" and double click the first item. That location is the "root" of a drive.
Note: make sure you have at least 400 mb of memory (i know, thats alot, but just in case) on your sd card so you can back up your entire phone! i reccomend doing every optional step!!! It'll save you hassle if you have problems. If you can't make room for some reason, and you still wanna try, you should skip step 8. I don't suggest it though.
1. download "odin.zip" and "su" here: https://www.box.com/shared/620b03e95cc0814fefc8 and unzip to your desktop. if you dont have the android sdk, simply copy the "adb.exe" file from "odin.zip" to the root of your primary drive for later. Just go to "computer" and double click the top icon/item. It should say something about C:/. If you're on Mac, sorry. Idk much about it. As for Linux, I have no clue how you'd even try to do this. I love Linux but, sadly, can't experiment with this in it. WINE has its limits....... And I don't think adb or Odin would work.
2. download the "su" file and put into into "platform-tools" where you installed the android sdk, if you have it, or put onto the root of your primary drive if you havent.
3. start phone while holding "spacebar" and "p". "downloading..." should appear on the screen in yellow text
4. plug into the computer and run "Odin_Multi_Downloader_v4.42.exe"
5. select SPHM580.ops for "OPS" and Replenish-CWM5.tar for "One Package" (they should be the only options) DO NOT CHANGE ANYTHING ELSE!!!!!
6. hit "Start" and DO NOT REMOVE PHONE FROM USB.
7. as the phone reboots, hold "u" until CWM opens and set the phone down. you should close Odin now.
8. use the volume keys to navigate to the backup and restore option and use enter to select backup. wait for it to finish completely and take you back to the the CWM main UI. backing up here creates a pure recovery, untouched by anything. CWM is NOT installed into this recovery. continue with the guide.
9. open the command prompt (type cmd.exe in search or run in the start menu, depending on your version of windows) or use some form of terminal emulator on your operating system of choice. command prompt is preferred due to the fact i know it can get the job done, but do what you will.
10. navigate to the drive your sdk is on and into "platform-tools" or to the folder you put the adb.exe and su files on. the default should be [name of drive]:\Users\[username]\. use the "cd.." command til youre at the root of the drive, and if you installed the sdk, type "cd android-sdk-windows/platform-tools" or just go to the root of the drive and go to the next step if you havent. just be sure adb.exe and su are there.
11. type this in line for line, with enters in between. the blue "~#" in the later lines is the prompt you should have. do not type this. it will be in blue. (clockworkmod should still be open on your phone at this point)
adb shell
~#mount -o remount,rw -t rfs /dev/block/stl12 /system
~#exit
adb push su /system/bin/
adb shell
~#chmod 777 /system/bin/su
~#reboot
DO NOT CLOSE THE COMMAND PROMPT YET FOR THE SAKE OF CONVENIENCE
If you have problems with that, try using CWM to mount "/system". Some friendly people over at androidcentral pointed that out. I personally didn't have that problem, but I'm glad it's fixed.
12. when your phone has rebooted, go back to the open command prompt, which should be where it was before you typed "adb shell"
13. type "adb shell". you will see a prompt of "$." type "su." if you have a prompt of "#" rejoice! you have permanent root! now you can go on the Play Store and find "Superuser" and "Busybox" (they should be free. if you cant find it, get ahold of me and ill try to supply the newest updates) if not, and you have a backup from optional step 2, you should go through til you hit CWM and restore the backup. if not, make one now and reattempt everything aside from downloads and the moving the files around on your computer. Also, someone said something about "chmod 06755 /system/bin/su", so if you might try using that instead of "chmod 777 /system/bin/su". 777 worked for me, but maybe this works better for you.
OPTIONAL FINISH STEP: I dont know how you install CWM permanently, but you should do this so you can make backups of your rom and store them somewhere like on a box.com or mediafire.com account if you decide to mess with something on your phone. (use hjsplit to break it into pieces for uploading and reassemble after download for flashing if its too big). to use a recovery, enter CWM (either the way i have here or if you have permanently installed, just reboot and hold "u") and navigate to "backup and restore," "restore," and select the recovery you wish to use on your sd card (make sure when you take out a backup for storage, you zip up the entire folder with the name that contains the date and time of your backup.) it will overwrite everything on your phone to be exactly like it was when you backed it up.
good luck! have fun!
Note: if you rename the CWM backup file, make sure it DOESN'T HAVE A SPACE or it'll give you something about md5 or something not matching. If it says this, remove any spaces in the name and try again. I had it happen on my xperia play and freaked, thinking it was soft-bricked permanently one time, til I found out about cwm's glitch with that.
Also, I uploaded pretty much everything needed for rooting the phone, with comments pertaining to each file. This includes current (as of July 31, 2012) copies of Superuser.apk, a busybox installer, and the busybox and su binaries, as well the Odin package containing the tools to temp flash CWM.
the odin.zip file and the process of achieving CWM temp-flashing was found at http://forums.androidcentral.com/sa...method-samsung-replenish-android-2-3-6-a.html and credit for that part is given to joshua.worth, although I took it a different path than he did.
Update to above info: to simplify things, I uploaded all relevant files to box so people can get them easier. The su file went missing from xda, most importantly, so I fixed that, and added an updated binary in case someone has trouble with the other one.
contact me at [email protected] if you cant pm me.
Sorry if it takes a while to respond. Life's been kinda crazy for me lately, and I am using my new phone (no service) to do this over wifi.

ahh... well, turns out unrooting cannot be done with a CWM backup... you probably have to find a nandroid or a clean version of kernel with rom. the su file dissapears, although root is still there. ill keep playing with it, i have an idea why root stays although su disappears from the system files. anyways, i will still supply a backup thats pre-rooted for anyone who is willing to have a fresh start on their replenish. it will have superuser.apk preinstalled along with busybox, and everything else will be wiped. this will be a sprint backup, so if anyone has the boost version and is willing to back up with CWM and factory reset, then follow my guide, install busybox and superuser.apk, then back it up again, id be eternally grateful to have a copy
by the way, if anyone has problems with restoring a backup due to "md5" tags or whatever it is, make sure the name of the backup has no spaces. i was freaking out til i found that tip on an obscure forum (well, to me. i dont have a Motorola. lol. just a Sony Ericsson and 2 Samsungs)
update: sorry i havent uploaded the backup. i realized it would give whoever used it the number on this phone and i have to fix that. havent had time to anyways, plus it would only work on a sprint phone. it would convert any boost mobile to sprint, so thats a no-go. sorry...

does this work for the boost mobile replenish that is 2.3.6 if so how long does it take to odin

It should work. And Odin just flashes cwm (really fast) for the duration of the next boot cycle, which it automatically initiates, so hold the recovery button (I think it's u) as it goes into it and you'll have temp root. Make sure it's in download mode before you start. Remember, it cannot be unrooted, so if you value your warranty, plz think twice before doing it. I'm just here to supply the how-to if you decide to, not to say you have to. If you do, enjoy root access!

isavegas said:
It should work. And Odin just flashes cwm (really fast) for the duration of the next boot cycle, which it automatically initiates, so hold up (I think it's u) as it goes into it and you'll have temp root. Make sure it's in download mode before you start. Remember, it cannot be unrooted, so if you value your warranty, plz think twice before doing it. I'm just here to supply the how-to if you decide to, not to say you have to. If you do, enjoy root access!
Click to expand...
Click to collapse
Thanks. I did not know if there is a fail safe if something went wrong. so I was second guessing. Very simple to do thank you assuming with odin I made a back up. if I where to mess my system up I can use odin and restore my backup and I be back up and running again no need to sbf

i keep getting : ~ # mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument

bscabl said:
i keep getting : ~ # mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
Click to expand...
Click to collapse
hmm... i am familiar with the error (ive gotten it with 3 different phones in my attempt to root it, but i have succeeded each time regardless) but are you sure you actually have clockworkmod OPEN on your phone when the error shows up? i cant actually do anything from my end, because i no longer have a computer i can use to test anything, or the replenish i rooted with the method... but i opened the cwm several times before thinking to test the adb and seeing the "~#". i actually restarted the phone and did it again before actually rooting it, seeing if i had rooted it or what, and tho i got the same prompt every time it was booted in cwm, it wouldnt show up if i allowed the phone to boot normally after using odin, i HAD to ACTUALLY boot into the cwm menu, which is completely seperate from the OS itself, although it has access to the system files.
by the way, copy and paste this directly into the command prompt when you get to the step to avoid human error. mount -t rfs -o remount,rw /dev/block/stl9 /system
or, if it wont work, try this mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
sorry bout the babbling XD. anyways, cwm should be circumnavigating the root permissions. hmm.... if you still have problems after that, try skipping to the adb push for the "su" file.
sorry i havent been on top of the thread. ill set up an email notification.
and by the way, something i found very useful on my xperia play when it went into infinite reboot, you can always just restore the system files in the advanced restore option, allowing you to keep all of your app data if, later down the line, your phone needs to be restored. hope this helps. it helped me XD thought id lose all of my messages, but nope. i decided to explore the advanced restore and yay! i got to keep them XD
UPDATE
I don't know if it matters to you anymore, but apparently, some people have trouble with this and fix it by going to the mount menu in CWM and mounting /system

Couple of corrections:
chmod 777 /system/bin/su
should be chmod 06755 /system/bin/su
and then following that command should be
ln -s /system/bin/su /system/xbin/su
and I saw someone say this is unrootable. Thats not correct. Simply running the unroot script would unroot. Doomlord made a nice one.
To use it do the following:
Code:
adb push unroot /data/local/
adb shell chmod 777 /data/local/unroot
adb shell su -c "/data/local/unroot"
adb reboot
[code]
The above will unroot almost any android device.

halfcab123 said:
Couple of corrections:
chmod 777 /system/bin/su
should be chmod 06755 /system/bin/su
and then following that command should be
ln -s /system/bin/su /system/xbin/su
and I saw someone say this is unrootable. Thats not correct. Simply running the unroot script would unroot. Doomlord made a nice one.
To use it do the following:
Code:
adb push unroot /data/local/
adb shell chmod 777 /data/local/unroot
adb shell su -c "/data/local/unroot"
adb reboot
[code]
The above will unroot almost any android device.[/QUOTE]
Unfortunately, Doomlord's method didn't work on it. I tried all manner of one clicks and manual versions and only this got even temporary root. It's a workaround based on forcing the phone to boot into a custom recovery. (I call it custom bc its not an "official" recovery.) And I chose the chmod by looking through many manual ways to root, and that one was popular, and it works. I had full root access afterwards. I tried to unroot afterwards, however, so I could take screenshots and stuff, but the su file would reappear, even after manual deletion or restoring to an unrooted backup. Anyways, point is, this is the only method I could get to work at all, and it does work.
But the "chmod" night help other people, so ill make note of it in the post just in case. Thanks for the info.
Sent from my rooted R800at using xda app-developers app
Click to expand...
Click to collapse

Important fix----
If step 11 doesn't work, go to the "mount" menu in cwm and mount /system. Some people on androidcentral were kind enough to mention that this fixed their problem with mounting /system as rewritable
Sent from my R800at using xda app-developers app

isavegas said:
Important fix----
If step 11 doesn't work, go to the "mount" menu in cwm and mount /system. Some people on androidcentral were kind enough to mention that this fixed their problem with mounting /system as rewritable
Sent from my R800at using xda app-developers app
Click to expand...
Click to collapse
thats because your command is wrong

shabbypenguin said:
thats because your command is wrong
Click to expand...
Click to collapse
How? Throughout my own rooting of one of the phones, I had this working perfectly. Every time I hit a snag, I found a way around it and documented it. A few other people had errors show up because the phone itself hadn't mounted the system, but the problem was resolved, and only a couple people had any other problems, and they were unrelated to that. I assure you, every command works properly, as far as I know.

exactly my point. your command to mount system is wrong.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
lets break it down shall we?
mount - this is teh command
-o remount,rw - this is where you tell it what option you want, in this case remounting as rw.
-t yaffs2 - here you are telling mount that it should expect a yaffs2 formatted device, which is not what the samsung replenish is. the replenish uses RFS (robust file system), the best way i can describe it is like telling your windows computer that your hard drive is fat32 when its actually ntfs.
/dev/block/mtdblock3 - this is where you tell mount what you are looking to mount, the issue here is that the replenish doesnt use MTD blocks, it uses STL's and BML's.
/system here is where you are trying to mount the said device to..
out of 5 parts you did get 3 correct tho. you might wish to modify your guide to reflect the actual mount command, for your device it is the following:
mount -o remount,rw -t rfs /dev/block/stl12 /system
and that will kick out system as r/w

shabbypenguin said:
exactly my point. your command to mount system is wrong.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
lets break it down shall we?
mount - this is teh command
-o remount,rw - this is where you tell it what option you want, in this case remounting as rw.
-t yaffs2 - here you are telling mount that it should expect a yaffs2 formatted device, which is not what the samsung replenish is. the replenish uses RFS (robust file system), the best way i can describe it is like telling your windows computer that your hard drive is fat32 when its actually ntfs.
/dev/block/mtdblock3 - this is where you tell mount what you are looking to mount, the issue here is that the replenish doesnt use MTD blocks, it uses STL's and BML's.
/system here is where you are trying to mount the said device to..
out of 5 parts you did get 3 correct tho. you might wish to modify your guide to reflect the actual mount command, for your device it is the following:
mount -o remount,rw -t rfs /dev/block/stl12 /system
and that will kick out system as r/w
Click to expand...
Click to collapse
Hmmmm.... Odd..... *shrugs* I had no problem with the command, but I guess other ppl had pickier computers or phones. Hell, Vista's buginess might have worked in my favor that time XD. Thanks for the pointer. I didn't really understand the exact way the replenish was built. I just found a lil guide for making it boot into cwm and found it allowed for me to use that as an exploit to root the device. In fact, I've done the same kind of stuff to root the samsung Intercept, except I made their own software flash a pre-rooted kernel. anyways, I'll update the guide on xda and androidcentral. Thanks!

isavegas said:
Hmmmm.... Odd..... *shrugs* I had no problem with the command, but I guess other ppl had pickier computers or phones. Hell, Vista's buginess might have worked in my favor that time XD. Thanks for the pointer. I didn't really understand the exact way the replenish was built. I just found a lil guide for making it boot into cwm and found it allowed for me to use that as an exploit to root the device. In fact, I've done the same kind of stuff to root the samsung Intercept, except I made their own software flash a pre-rooted kernel. anyways, I'll update the guide on xda and androidcentral. Thanks!
Click to expand...
Click to collapse
chances are you had system mounted in cwm without knowing it.
for future knowledge always check the devices fstab for where to mount and filesystem type
https://github.com/Shabbypenguin/android_device_replenish/blob/master/recovery/recovery.fstab
as you can see the proper mounts from the files i used to make CWM for the replenish

shabbypenguin said:
chances are you had system mounted in cwm without knowing it.
for future knowledge always check the devices fstab for where to mount and filesystem type
https://github.com/Shabbypenguin/android_device_replenish/blob/master/recovery/recovery.fstab
as you can see from the files i used to make CWM for the replenish the proper mounts
Click to expand...
Click to collapse
Eh, maybe. For all I know the first thing I did was mount everything with cwm. I DID do this several months ago. I don't even have the phone anymore. The owner of the phone was gonna give it to me after upgrading, but she sold it, so I kept her 500gb laptop hard drive instead. Popped it out of the external hdd casing and stuck it in a laptop. XD. It now has Linux on it.
Anyways, I've updated the guide to have the right command and note that if it doesn't work to use cwm to mount /system. And how do you find the fstab? Just Google it? Or is it somewhere on the device?
Btw, do you know anything about cwm? It refuses to properly back up my xperia play anymore. The .android_secure folder keeps giving it errors.

isavegas said:
Eh, maybe. For all I know the first thing I did was mount everything with cwm. I DID do this several months ago. I don't even have the phone anymore. The owner of the phone was gonna give it to me after upgrading, but she sold it, so I kept her 500gb laptop hard drive instead. Popped it out of the external hdd casing and stuck it in a laptop. XD. It now has Linux on it.
Anyways, I've updated the guide to have the right command and note that if it doesn't work to use cwm to mount /system. And how do you find the fstab? Just Google it? Or is it somewhere on the device?
Btw, do you know anything about cwm? It refuses to properly back up my xperia play anymore. The .android_secure folder keeps giving it errors.
Click to expand...
Click to collapse
its where the recovery is on the device. each device has their own fstab. as for your error sounds like a conflict, either with cwm itself or that folder

shabbypenguin said:
its where the recovery is on the device. each device has their own fstab. as for your error sounds like a conflict, either with cwm itself or that folder
Click to expand...
Click to collapse
It HAS to he cwm, because the folder is regarded as super hidden by the device. The folder itself can be seen, but the contents can ONLY be edited by the rom or a pc, and I haven't touched it with a pc before. It's where your apps go when you move them to the sd card. I've been trying to back my phone up with cwm because I wanted to test the jelly bean alpha release for it. its the xperia play 4g. Stupid backup crashes every time I try and it ends up eating up what room is left in my sdcard.

i followed your guide and have root in shell. however i cant get root permission on any apps, the window doesnt pop up asking me for permission. i also get a toast notification saying superuser access denied for whatever app im trying to open. any ideas?

arodey said:
i followed your guide and have root in shell. however i cant get root permission on any apps, the window doesnt pop up asking me for permission. i also get a toast notification saying superuser access denied for whatever app im trying to open. any ideas?
Click to expand...
Click to collapse
What does your Superuser log show?
Sent from my PC36100

GT-n8010 (Wifi) Factory Mode

Hi,
Hope someone can figure this as its wrecking my brain.
I got an 8010 (wifi only version) a few days ago.
Did the clockwork and rooting and it was all working fine, until..
Booted it up this morning and it flashed a message 'Unfortunately, Factory Test has stopped. Factory Mode is ON!!' and gave me the 'calculator' program for putting in service codes.
I've checked the efs folder and its blank, no files. (I do not have a backup, yes I know I'm an idiot)
I've since tried flashing a number of roms, including stock. None of which have resolved the issue.
When using the stock recovery it gives me an error about being unable to mount /efs
From google it appears that the efs folder is to do with the imei and other areas. As mine is wifi only version should I even have this folder?
The note appears to work fine with the exception of having a lock screen, power off options etc.
thanks
BB

Have you tried to flash it over the PC with Odin and the Files from sammobile.com ??
Have you tried to repair the EFS with this Tool: http://forum.xda-developers.com/showthread.php?t=1308546 ?

update
Darkman_RS said:
Have you tried to flash it over the PC with Odin and the Files from sammobile.com ??
Have you tried to repair the EFS with this Tool: http://forum.xda-developers.com/showthread.php?t=1308546 ?
Click to expand...
Click to collapse
Hi,
I have tried with the N8010XWALG4_N8010XSAALG3_XSA from sammobile but am currently running the N8010-XXALH2-XAALH2-DBT-deodexed
Strangely enough I have just tried to connect with Kies, and it wont connect gives an error of 'No Sim Card inserted unable to continue communication'
I'm wondering if I've somehow confused my device into think its a 8000, when it is in fact an 8010.
I've tried the EFS Repair, it states that Locate /efs partition failed and can't locate any backups ;-((
I've just tried reflashing a stock rom via odin, selecting the re-partition and format efs section (got nothing to lose at this stage I guess)
I've also removed clockwork mod and gone back to stock recovery, which reads E:failed to mount /efs (Invalid arument)
would anyone have the .pit file / bootloader files? or are they built into the the pda rom?
thanks
BB

Pit file
Further testing has shown that the /efs partition does not exist or has become corrupt.
Would anyone have / or could make a pit file for a 32gb gt-8010?
Failing that would anyone know the terminal commands and dev location for making the /efs partition (make2fs ??)

Did you fixed the issue?
blue_bear said:
Further testing has shown that the /efs partition does not exist or has become corrupt.
Would anyone have / or could make a pit file for a 32gb gt-8010?
Failing that would anyone know the terminal commands and dev location for making the /efs partition (make2fs ??)
Click to expand...
Click to collapse
I have the same problem please advise?

Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013

Hello
I am getting the same problem.
Odin can not find partition. But I cant go to CWM, only download mode is possible. Any other way to start, it goes to a white screen...

BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
You made my day bro a lot of thanks its works for me thank u

ques
BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
hi, I sent u a msg, if u dont read msgs on private, qoute me her so i can ask ya her.
bless

BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
perfect
thx a lot

thank you sir, good job.

BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
Hi,
how is the zip to be used?

YOSEFE said:
Hi,
how is the zip to be used?
Click to expand...
Click to collapse
it is just factorymode file set to on
use root enabled file manager and copy to /efs over writing current one. but it's just as easy or easer to just edit current file and change OFF to ON

BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
@YOSEFE and @carl1961
hello
where I find this CWM and ANDROIDSDK ,,,??? ...she said " Assuming you have CWM installed on device and have androidsdk store on computer C: drive "
CWM what exactly is and where to find it ?
same for androidsdk where I find it ??
can you give me the real or good link plz ?? thanks

Hello,
CWM Recovery is found on www.clockworkmod.com
You need the one for your device.
You can Google search this and other file too. Be sure to read about CWM Recovery. It will trip knox on Samsung phones.
Sent from my SM-N910F using XDA Free mobile app

YOSEFE said:
Hello,
CWM Recovery is found on www.clockworkmod.com
You need the one for your device.
You can Google search this and other file too. Be sure to read about CWM Recovery. It will trip knox on Samsung phones.
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
@YOSEFE
I'm sorry but what this i don't understand where is the link plz direct links for download ?? thanks
I can not go and install apps because the tablet does not open
my device is GT-8010 WIFI ONL
edits
i have downloaded this "recovery-clockwork-6.0.4.6-n8000 ' and "recovery-clockwork-6.0.4.6-n8013" it's ok or no ?? here http://www.clockworkmod.com/rommanager
if yes how to install ??

joan62 said:
@YOSEFE
I'm sorry but what this i don't understand where is the link plz direct links for download ?? thanks
I can not go and install apps because the tablet does not open
my device is GT-8010 WIFI ONL
edits
i have downloaded this "recovery-clockwork-6.0.4.6-n8000 ' and "recovery-clockwork-6.0.4.6-n8013" it's ok or no ?? here http://www.clockworkmod.com/rommanager
if yes how to install ??
Click to expand...
Click to collapse
your best using one for 8013
https://goo.im/devs/Darkman/Recoverys/N8013-CWM-noTouch-6.0.3.6-ODIN.zip/

carl1961 said:
your best using one for 8013
https://goo.im/devs/Darkman/Recoverys/N8013-CWM-noTouch-6.0.3.6-ODIN.zip/
Click to expand...
Click to collapse
+1...
Sent from my SM-N910F using XDA Free mobile app

@YOSEFE @carl1961
please help with the screnns is possible I'm sorry but i don't understand
I enter the ligne but the command not working
he said not find
the ANROIDSDK IN c : drive /android /android-sdk.... it's ok the intallation ?

Install on C:\. Use ODIN to install Recovery. Make sure your device is in download mode.
Sent from my SM-N910F using XDA Free mobile app