Related
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?
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
I'm trying to delete a default application from my droid (WriteandGo) by deleting both the .apk and .odex file from /system/app using root explorer.
The phone is rooted, in Root Explorer and the partition appears mounted as r/w. When I delete both files it works fine and they disappear, but when I go back and then return to the app folder the files are there again. The application never gets uninstalled.
Any ideas?
Thanks!
Use titanium backup to uninstall sytem apps..
Thanks, it does work, but I'm curious as to why root explorer is failing to delete the files..
Neojag said:
I'm trying to delete a default application from my droid (WriteandGo) by deleting both the .apk and .odex file from /system/app using root explorer.
The phone is rooted, in Root Explorer and the partition appears mounted as r/w. When I delete both files it works fine and they disappear, but when I go back and then return to the app folder the files are there again. The application never gets uninstalled.
Any ideas?
Thanks!
Click to expand...
Click to collapse
That is because the /system partition is mounted read only.
To mount read-write, install ADB.
Set phone to USB debug.
Then:
> adb shell
$ su
# mount -o remount,rw /dev/block/stl6 /system
Then go the the appropriate directory and remove the files with "rm".
So the info Root Explorer is supplying (that the partition is mounted as r/w) is wrong? That's odd, because I've managed to copy a file to /system/etc/.
Hey
I've tried to install xrecovery, and done what this video says: http://www.youtube.com/watch?v=O6eRfqs8TVs but when i reboot, it won't work. Nothing happends when i press the bkac button alot.
If it is some files, causing this, then please send me yours, so i don't have to ask for them, when you have answered
SimonXiDk said:
Hey
I've tried to install xrecovery, and done what this video says: http://www.youtube.com/watch?v=O6eRfqs8TVs but when i reboot, it won't work. Nothing happends when i press the bkac button alot.
If it is some files, causing this, then please send me yours, so i don't have to ask for them, when you have answered
Click to expand...
Click to collapse
It happens to me to at the first time, all you have to do is delete the files and paste them again.. xD if still didn't work, i'll post my files here so you can tried..
I have tried now, but it won't work. I would be glad if you posted your files :b
Have you set the right permissions for the files?
All files needs to be writeable. The easiest way to set the write permissions is to use root explorer.
Or if using terminal emulator: Chmod each file to: 777
After a lot of trying this worked for me:
1. Download xRecovery from here.
2. Copy three files to sdcard - xrecovery.tar, busybox, chargemon
3. Just in case, get Busybox from Market and install it.
4. Copy three files from sdcard to /system/bin - don't forget to mount system as r/w (you can do it with Root Explorer by simply clicking "mount r/w" button)
5. Chmod all three files to 777 - with Root Explorer, open context menu for file and select "Permissions" and make sure all 9 boxes are ticked. Or, use adb shell.
6. Turn off your phone normally.
7. Turn on and keep pressing back button, now you should enter xRecovery.
blagus said:
5. Chmod all three files to 777 - with Root Explorer, open context menu for file and select "Permissions" and make sure all 9 boxes are ticked. Or, use adb shell.
Click to expand...
Click to collapse
Can i give permission, when the files are in the bin? Will it work then?
blagus, i did what you said, but still, with no luck .. :s
SimonXiDk said:
blagus, i did what you said, but still, with no luck .. :s
Click to expand...
Click to collapse
It is important to install xRecovery 0.1!!!
I have tried to install 0.3 first but it is not work on X8.
So use this only: http://forum.xda-developers.com/showthread.php?t=878426
qsmyle said:
It is important to install xRecovery 0.1!!!
I have tried to install 0.3 first but it is not work on X8.
So use this only: http://forum.xda-developers.com/showthread.php?t=878426
Click to expand...
Click to collapse
If you read the whole thread, then you would know, that it is the same that blagus said. And as i said, i did all that he said.
Use this files.. If didn't work, I don't know what to say, can't understand your problem..
Now i got to know that i should download these same three files three times. again - it do not work.
SimonXiDk said:
Now i got to know that i should download these same three files three times. again - it do not work.
Click to expand...
Click to collapse
Here did you pasted those files? Didn't you already having xrecovery running well, before you reflash your phone?
Now you get the story:
First of all, i tried in hours to get xRecovery work on my phone. Then succesfully, in some unknown way, i made it work.
Then i screwed up, and deleted the bin, so my phone wouldn't turn on.
Then i had to use SEUS to get my phone work, and I did that succesfully. But it was only 2.1 now.
Now i want 2.2 again, but can't make xRecovery work.
Weee it works now D I have no idea what I did diffrent this time, but it works now D thank you all for taking time, to help me ;b
And you're using 2.1 android, right? Is it rooted? If yes, all you have too do (and before that, delete the old files that you already pasted, except busybox..):
-put the files on your sdcard root;
-go to root explorer and to the sdcard folder;
- forget it busybox, just copy the other files;
- go to system/bin and then select the W/R option;
- then just paste them e restart your phone..
Then press a few times the back key, right after SE logo apears.. If you did't get anything, go again to the bin folder with root explorer and see if was created a folder with the xrecovery name.. If yes, just try again pressing back key until you get xrecovery menu..
" adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push "D:\Manu\Android\xrecovery/chargemon" "/sdcard/tmp/chargemon"
failed to copy 'D:\Manu\Android\xrecovery/chargemon' to '/sdcard/tmp/chargemon': Permission denied
adb push "D:\Manu\Android\xrecovery/xrecovery.tar" "/sdcard/tmp/xrecovery.tar"
failed to copy 'D:\Manu\Android\xrecovery/xrecovery.tar' to '/sdcard/tmp/xrecovery.tar': Permission denied
adb shell dd if="/sdcard/tmp/chargemon" of="/system/bin/chargemon"
/sdcard/tmp/chargemon: cannot open for read: Permission denied
adb shell dd if="/sdcard/tmp/xrecovery.tar" of="/system/bin/xrecovery.tar"
/sdcard/tmp/xrecovery.tar: cannot open for read: Permission denied "
what should i do?
crazyboy05 said:
" adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push "D:\Manu\Android\xrecovery/chargemon" "/sdcard/tmp/chargemon"
failed to copy 'D:\Manu\Android\xrecovery/chargemon' to '/sdcard/tmp/chargemon': Permission denied
adb push "D:\Manu\Android\xrecovery/xrecovery.tar" "/sdcard/tmp/xrecovery.tar"
failed to copy 'D:\Manu\Android\xrecovery/xrecovery.tar' to '/sdcard/tmp/xrecovery.tar': Permission denied
adb shell dd if="/sdcard/tmp/chargemon" of="/system/bin/chargemon"
/sdcard/tmp/chargemon: cannot open for read: Permission denied
adb shell dd if="/sdcard/tmp/xrecovery.tar" of="/system/bin/xrecovery.tar"
/sdcard/tmp/xrecovery.tar: cannot open for read: Permission denied "
what should i do?
Click to expand...
Click to collapse
you're going to need to mount the system first. I believe it's adb shell -> su -> then something. Can't remember now.
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.