Database Users

[Q] How to copy file to system\app with Build shubCRAFT CM6/Froyo/V1.3

Can not use Root Explorer to copy files to system\app with Build shubCRAFT CM6/Froyo/V1.3.
I tried mount R/W, but it did not change r/o to r/w.
Anybody can help? Thanks!
Need to copy Jbed.apk to that folder.
Thanks again.

copy apk
Hi zchf,
Try Android Commander "http://forum.xda-developers.com/showthread.php?t=628138" it works for me
sparkie_1

Here you go:
- open Terminal emulator:
$ su
# mount -o remount,rw /system
- open Root Explorer \system folder and press r/w
- voila
Thx to doberman

Thank you very much!
I copied the file, while the Java doesn't work yet.
Anybody uses this and suggest?

[recovery hack] How to get back recovery 2e

Helo
I found a way to return to the recovery 2e
recovery 2e
Copying a file using the Root Explorer
# unzip and put archive contents in a folder called recovery2e on /sdcard/
# first mount -o remount,rw /system (important options in Root Explorer for do this)
# file recovery copy to /system/bin (and replace)
# xbi folder contents copy to /system/xbin/ (and replace)
Click to expand...
Click to collapse
Method by captive thanks buddy
# put archive contents in a folder called recovery2e on /sdcard/
# open a shell and get root (ADB or Terminal on Phone, type su and pres enter / accept )
# remount /system rw (busybox mount -o remount,rw /system)
# rename recovery in /system/bin to recovery3e (for backup purposes)
# copy "recovery" from /sdcard/recovery2e/ to /system/bin/ (cp /sdcard/recovery2e/recovery /system/bin/)
# copy the folder /sdcard/recovery2e/xbin/recovery to /system/xbin/ (cp -rr /sdcard/recovery2e/xbin/recovery /system/xbin/)
# enjoy!
Click to expand...
Click to collapse
Restart your phone

Isn't anyone going to comment on this?
Gurus: does it really work? That simple?
Thanks

Didn't work for me - used root explorer method. Now just hangs when I try to get recovery mode. Can get download mode ok still, and phone boots ok of course. Running JPM with root and voodoo5 3. Anything else to try?

Does not work on JPM....

it no works.
Phone: Doc's JP6 + voodoo pre3 + rooted
Method: Root explorer.
1, during copy the xbin folder to system, it shows "replace files" but after i check inside the system/xbin, the files are disappared??!! I did manually copy everything one after one from xbin to system/xbin, but i can't see where they are after copy.
2, anyway, i reboot the phone with 3b combo, the recovery mode still showing 3e.
so i say it no works. anyone tried the cable methed?

this thing work but it needs a little workaround as discussed by danzel. follow here: http://forum.xda-developers.com/showthread.php?t=774500&page=188

Could you please update the instruction for jp6 + voodoo pre4?
abd remount (don't know why) isn't working and /system is always ro so adb push and shell (adb shell works) cmd aren't working.
It is correct to remove su and busybox int the extracted folder since i have both already installed?

I was on JPM, followed the instructions.
Phone couldn't boot, lost ability to enter recovery. Luckily I could still enter Download mode, flashed to JPM, but being on voodoo kernel before that, didn't managed to disable lagfix before getting into this trouble - Couldn't revert back to RFS, and without ability to enter recovery to format.
Finally reverted back to Eclair firmware, could see my beloved recovery again. No way I'm going through the above again.
The above is just my own experience, for reference just in case someone is as unlucky as me.

This is the clear step on recovering the recovery2e
Recover recovery2 e
1. uncompress the downloaded file recovery 2e and copy the direcotry to sdcard and rename it to recovery2e
2. Using root explorer copy File recovery from recovery2e on sdcard to /system/bin
3. Using root explorer copy Folder recovery in xbin to /system/xbin
4. If did not work try copy xbin folder over /system/xbin folder

Ok, confirmed working for me on JPM+Voodoo.
I installed Rom Manager too, and CWM Recovery is fully working too!! TNX

xtrememorph said:
This is the clear step on recovering the recovery2e
Recover recovery2 e
1. uncompress the downloaded file recovery 2e and copy the direcotry to sdcard and rename it to recovery2e
2. Using root explorer copy File recovery from recovery2e on sdcard to /system/bin
3. Using root explorer Folder recovery in xbin to /system/xbin
Click to expand...
Click to collapse
Your method DO NOT work at all. I cannot enter recovery mode.
Fortunately download mode is still available.
JPM+Voodoo5 pre6

lagigia, what didn't work for you?
Here's what I did:
put archive contents in a folder called recovery2e on /sdcard/
open a shell and get root
remount /system rw (busybox mount -o remount,rw /system)
rename recovery in /system/bin to recovery3e (for backup purposes)
copy "recovery" from /sdcard/recovery2e/ to /system/bin/ (cp /sdcard/recovery2e/recovery /system/bin/)
copy the folder /sdcard/recovery2e/xbin/recovery to /system/xbin/ (cp -rr /sdcard/recovery2e/xbin/recovery /system/xbin/)
enjoy!

if using the root explorer method, copy xbin folder content, do not try to overwrite the entire dir on top.

mike.sw said:
if using the root explorer method, copy xbin folder content, do not try to overwrite the entire dir on top.
Click to expand...
Click to collapse
too late is there a way to solve it or get a step back?
thx!

i think u can just flash only the old kernel back and it will be fixed (only zimage).

captive said:
lagigia, what didn't work for you?
Here's what I did:
put archive contents in a folder called recovery2e on /sdcard/
open a shell and get root
remount /system rw (busybox mount -o remount,rw /system)
rename recovery in /system/bin to recovery3e (for backup purposes)
copy "recovery" from /sdcard/recovery2e/ to /system/bin/ (cp /sdcard/recovery2e/recovery /system/bin/)
copy the folder /sdcard/recovery2e/xbin/recovery to /system/xbin/ (cp -rr /sdcard/recovery2e/xbin/recovery /system/xbin/)
enjoy!
Click to expand...
Click to collapse
Thanks, works fine on JPM/JP6

Could we get a newbie friendly guide please. Get root. What does that mean and should i just type what you quoted. Thanks
Sent from my GT-I9000 using XDA App

Edited the first post and put the new, easy tutorial

Could i get some background on this, please?
Is it correct that:
1) recovery2e is the default samsung recovery?
2) new versions of recovery2e can't apply all the update.zip we were able to apply with the older versions? (unsigned, signed??)
3) This is why we need the old recovery2e to replace the new one?
4) Where did the issue started? Since Froyo releases?
5) Is this why we can't root Froyo FWs with an update.zip anymore like it was the case with Eclair?
I'm really sorry if this is kinda obvious but i never really saw any clear explanation about this. Hope someone could clear it up for me

1) Yes
2) Correct on recovery 2e you can't apply all the update.zip
4) Yes, New tutorial on fist post
4) The JPM ROM brings new recovery 3e
5) You can root phone by flash kernel with root by odni

[Q] How to mount R/W in...

Hi I have a little question to make, and I haven't find anything about it...
My cellphone has root and i'm able to mount R/W in a most folders with root explorer, but I can't mount R/W in "cust" folder. Inside is a folder called "entel" and there are the modified boot animations and stuff.
There is the Swype.apk too, but it hasn't any dictionaries and I'm not able to install them too (I don't know why)... So when I try to change the apk for another one, i can't mount R/W.
And when i try to install normally i can't.
Is there a way to mount r/w in that folder or change the swype?

Why you don't just copy the files you need on another folder on sdcard and try to manipulated there?
Also this folder sould be in /cust_backup/custom_data. Did you tried from there?

I try to manipulate them in another place but then I can't replace the new files...
And i don't know why... but the folder is "cust", i know there is another one ".cust_backup" but inside is only the image folder with amss.mbn, boot.img, cust.img, emmcboot.mbn and recovery.img.
My cust folder includes a lot of subfolders, first one called "entel", then another subfolder "cl" and then i have folder called "app" (inside is only the Swype.apk"), lib, logo, media, nv, ons, prop, wallpaper and xml.
I Can't mount R/W in any of the cust folders, but I can do it in ".cust_backup"
:S

I don't know If you can mount this folder as rw.
Try to open command prompt on pc(and give the command adb shell) or a terminal emulator(in this case give the command su to take root rights)
and then give the command
cat/proc/mounts
to see which partitions have and where they mounted
Then, if the custom partition exist give the command
mount -o rw,remount /dev/block/
followed with the mmc...(something that I dont rember) number of partition
e.g mount -o rw,remount /dev/block/mmwhateveris12
to mount it.

It didn't worked...
What if change something in the apk to make the system think that isn't swype?

[Q] Trouble installing 19mountsdboot script

The instructions for installing 19mountsdboot are found here: http://forum.xda-developers.com/showthread.php?p=22858059#post22858059
I unrared 19mountsdboot-rev2.rar, and 19mountsdboot is in /sdcard/Download.
My problem is when I try to copy that file to /etc/init.d. Using Terminal Emulator,
cd /etc/init.d
cp /sdcard/Download/19mountsdboot .
cp: can't create './19mountsdboot': Read-only file system
Using ES File Explorer, I also get a "Read-only file system" error.
What am I missing?
Thanks

OrionNav said:
The instructions for installing 19mountsdboot are found here: http://forum.xda-developers.com/showthread.php?p=22858059#post22858059
I unrared 19mountsdboot-rev2.rar, and 19mountsdboot is in /sdcard/Download.
My problem is when I try to copy that file to /etc/init.d. Using Terminal Emulator,
cd /etc/init.d
cp /sdcard/Download/19mountsdboot .
cp: can't create './19mountsdboot': Read-only file system
Using ES File Explorer, I also get a "Read-only file system" error.
What am I missing?
Thanks
Click to expand...
Click to collapse
/etc/init.d is a root location. You must have root access and /system set to r/w.
So set terminal emulator in su (root) mode. Type su enter and the prompt will change to a #. Then you can try it. Set /system to r/w.
Also ES File Explorer must also be put in root mode and set /system to r/w before you can do it.
Edit: if you use the flashable zip, it does everything for you. Just put that zip into the boot partition of the SD and boot to SD recovery. It will install automatically. And it puts it in /data so it survives the update to a new ROM. I highly recommend you use that method.
Sent from my Nook HD+ running CM10.1 on emmc.

[Solved] Link2sd "mount warning" fix for all samsungs and android 5.1.1+ stock ROM

[Solved] Link2sd "mount warning" fix for all samsungs and android 5.1.1+ stock ROM
Hi.
I suppose many samsung and some sony devices have the problem "mount warning" displayed by Link2sd after installing it for manage second partition on external sd card. You do not have to generate mounting scripts again and again and restart system by Link2sd's own menu option to fix this. This solution lets to mount second partition automatic in boot phase.
Thank you to Warre101 for the idea.
If you want to use Link2sd you have to have rooted device. I did it on samsung galaxy tab 4 with stock ROM 5.1.1..
The best application for make all operations is Total Commander (TC).
1. Create subdirectory su.d in directory /system where you store your script, do it in left window of TC.
/system/su.d
2. Set 700 (RWX) permision for new created directory in Propertis TC's menu option . (Long tap directory name)
3. In the right window of TC open directory : /data/data/com.buak.Link2SD/files/
4. Copy the file init-link2sd.sh from right to left window. (If this file does not exist , create your own text file and paste the content from the example)
5. Change name of this file in the left window (/system/su.d directory) to 11link2sd
6. Copy renamed file back to right window and open it in Totalcmd-Editor (installed with TC)
7. Remove not needed text , the result should be:
Code:
#!/system/bin/sh
sleep 4
mount -t ext2 -o rw /dev/block/mmcblk1p2 /data/sdext2
8. Write changes and leave editor.
9. Copy changed file back to /system/su.d (left window). Overwrite existing file.
10. Set 700 (RWX) permision for this file . /system/su.d/11link2sd
11. Restart the device.
The new created script will mount partition needed by Link2sd for manage second partition on your external sd card during the booting phase of device/system .
This is not 100% sure if /su.d solution will work in every ROM. If you will find one not working, please comment here.

Help
Tomek0000 said:
Hi.
I suppose many samsung and some sony devices have the problem "mount warning" displayed by Link2sd after installing it for manage second partition on external sd card. You do not have to generate mounting scripts again and again and restart system by Link2sd's own menu option to fix this. This solution lets to mount second partition automatic in boot phase.
Thank you to Warre101 for the idea.
If you want to use Link2sd you have to have rooted device. I did it on samsung galaxy tab 4 with stock ROM 5.1.1..
The best application for make all operation is Total Commander (TC).
1. Create subdirectory su.d in directory /system where you store your script, do it in left window of TC.
/system/su.d
2. Set 700 (RWX) permision for new created directory in Propertis TC's menu option . (Long tap directory name)
3. In the right window of TC open directory : /data/data/com.buak.Link2SD/files/
4. Copy the file init-link2sd.sh from right to left window.
5. Change name of this file in the left window (/system/su.d directory) to 11link2sd
6. Copy renamed file back to right window and open it in Totalcmd-Editor (installed with TC)
7. Remove not needed text , the result should be:
Code:
#!/system/bin/sh
sleep 4
mount -t ext2 -o rw /dev/block/mmcblk1p2 /data/sdext2
8. Write changes and leave editor.
9. Copy changed file back to /system/su.d (left window). Overwrite existing file.
10. Set 700 (RWX) permision for this file . /system/su.d/11link2sd
The new created script will mount partition needed be Link2sd for manage second partition on your external sd card during the booting phase of device/system .
This is not 100% sure if /su.d solution will work in every ROM. If you will find one not working, please comment here.
Click to expand...
Click to collapse
in the directory : /data/data/com.buak.Link2SD/files/ , i cannot find the file init-link2sd.sh, only 2 files "link2sd_b and link2sd.log" and link2sd_b cannot be edited. My account haven't post 10 posts yet, so i cannot upload image for you to check.
can i creat the new init-link2sd.sh and continue your intructions ?
My device: Samsung galaxy A7 2016 (android 6.0.1 Rusia)

Hi _DoomD_ .
You should see this file if you installed current version of link2sd. If this file does not exist, you can use other text file or create new and copy the content from the example. If you use windows, do not use copy/paste. Linux uses different end line char. You does not do it on Tab 4 I suppose ... no mater , it will work on others if only your system will support new created /system/su.d/ .
Please let us know if it will work in android 6.0.1 .
Bye

Tomek0000 said:
Hi _DoomD_ .
You should see this file if you installed current version of link2sd. If this file does not exist, you can use other text file or create new and copy the content from the example. If you use windows, do not use copy/paste. Linux uses different end line char. You does not do it on Tab 4 I suppose ... no mater , it will work on others if only your system will support new created /system/su.d/ .
Please let us know if it will work in android 6.0.1 .
Bye
Click to expand...
Click to collapse
At step 8, i couldnot save changes. It gived me a writing error. I tried to change permission but it didnot work. I couldnot finish your intruction using totalcommand. I tried to use root explorer to edit and finished your intruction. But mount warning didnot fix.
I think your solution cannot work on android 6.0.1. Now i use apps2sd instead. Anyway, thanks for your help.

The problem with saveing exists in /system/... location. This is a reason i write abot coping renamed file back to link2sd's subdirectory and do all changes here. If your TC has root permision, it saves changes here. If this is not working, I do not know where is a source of problem.
File permision 700 lets the root do anything with file. TC with root permission uses root priv. for this operation. Maybe wrong owner of file, should be root...

A nifty thing one can do on a setup without built-in init.d, but recent SuperSU root with su.d, is to create and bind system/etc/init.d. I use a script in su.d to do this:
00000mounts:
Code:
mount -o bind,rw /su/su.d /system/etc/init.d;
In my case, I'm using systemless root, thus the '/su/su.d' location. Change it to your su.d folder location if it differs. This one line gives what amounts to standard init.d support, and any apps that create init.d scripts will see the /system/etc/init.d folder, use it, and their scripts end up in su.d and get executed on boot by SuperSU.
(And yes, this makes link2sd mounting work out of the box. Well, YMMV, but it worked for me.)

Filesystem for the second partition.
Code:
#!/system/bin/sh
sleep 4
mount -t ext2 -o rw /dev/block/mmcblk1p2 /data/sdext2
The important thing is that if you are using different filesystem for the second partition you should change `ext2` after `mount -t` to whatever filesystem you use. Maybe someone has posted it already but I do not have a time to check it. In my case I use `ext4` so it looks like this:
Code:
#!/system/bin/sh
sleep 4
mount -t ext4 -o rw /dev/block/mmcblk1p2 /data/sdext2
After this change Link2SD works perfectly on my Samsung Galaxy J3 (2016) aka SM-J320FN with stock Samsung ROM. Thanx.

@HostisSupremus
it has sense. I am always format it to ext2 on all my devices because of undelete support for ext2 and a lack of this support for ext4.
I found interesting fact on some of my devices . When you install link2sd, it wants to create initial script when you have to select your filesystem of second partition. I have always ext2, but some my devices works if I select ext2 and some do not. If do not, it works if I select ext4 , and it works with realy ext2 phisical partition. I do not know why .

dosent work for me, samsung galaxy tab a6 2016 android 5.1 rooted with magisk

This is what finally worked for me after three days of trying everything, thank you OP, you are my saviour
Difficult to believe after all these years of development link2sd does not verify init.d support.

I am using LOS 14.1 (Android 7.1) on my LG L70 and encounter the same mounting-failed problem.
I pull the file init-link2sd.sh out and it reads:
set +e
echo "$(date) mounting..." > $LOG
sleep 2
mount -t vfat -o rw,uid=1000,gid=1000,umask=133,dmask=0002 /dev/block/vold/public:179_66 /data/sdext2 1>>$LOG 2>>$LOG
mount -t vfat -o rw,uid=1000,gid=1000,umask=133,dmask=0002 /dev/block/mmcblk1p2 /data/sdext2 1>>$LOG 2>>$LOG
mount >> $LOG
echo "$(date) mount finished" >> $LOG
chmod 773 /data/dalvik-cache
Is there anything wrong? Why the 2nd partition can be mounted automatically at boot?
Also if there is a problem can I edit the file then push back directly?

I tried to edit the file init-link2sd.sh and pushed it back to phone. Not working...

thanks.
perfect..
my DEVICE J320G:good:

As a magisk user, I created a mount .sh script at /sbin/.magisk/img/.core/post-fs-data.d which seems to execute at boot time but not solve the issue