[Q] Busybox install, after rooting - Motorola Droid 3

Has anyone been able to successfully install Busybox after rooting? I grabbed it from the market but the install FCs.
For the install I picked v1.19.0 installing to /system/xbin.
The requirements page states the following are necessary:
A fully rooted device
A device that is nand unlocked
A device that does NOT have any sort of write protection on the file system
A ROM that supports installing Busybox to partitions that are NOT re-written on every boot
At least 1600KB free in your chosen installation path
Are we missing #2 on req. list even though we can fully root the device?

Yes busybox does work. Im wondering if that app is not remounting /system as writabe.
Try this, from adb or a terminal emulator. Type su . Then mount -o remount,rw /system
then try to run the app again.

eww245 said:
Try this, from adb or a terminal emulator. Type su . Then mount -o remount,rw /system
then try to run the app again.
Click to expand...
Click to collapse
Thanks but this command does not seem to have complete syntax. In Terminal, after elevating to su, I run that and am prompted with "Usage: mount....etc".

g3m1n1 said:
Thanks but this command does not seem to have complete syntax. In Terminal, after elevating to su, I run that and am prompted with "Usage: mount....etc".
Click to expand...
Click to collapse
Well that was the busybox way. lol
mount -o remount,rw /dev/block/system /system

Thanks, I think that did the trick.

Related

[FIXED] Remount failed: operation not permitted

Ok, I'm not a total noob. I've been trying to return to 1.5 as cleanly as possible, but now I'm having an error when trying to remount my phone.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
This is what I did:
Flashed the 1.5 RUU that Flipz has had out for months. No errors
Ran the Avalaunch PRI fix to get rid of the flipz_01 PRI name
updated my profile
updated my PRL (which is now 65000??)
rooted through the normal sequence without error, I can boot to the recovery just fine, but when I adb shell into the phone I end up at $ instead of #. I have to su to get to # and at the c:\windows-sdk-windows\tools\adb remount fails with "remount failed: operation not permitted"
Is it possible that the PRI update has foiled the root exploit? I even restored a nand backup that I know had a working root and I still have the same results. This is too weird.
Anyone else have this issue? I searched the forum but I came up empty.
Try adb remount before adb shell. I'm pretty sure anythig with adb should be ran at just the command prompt.
Someone feel free to correct me if I'm wrong.
right, this is at the c:\android-sdk-windows\tools\ prompt. I guess I need to re-word that last bullet point to be more clear.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
Yeah the wording got me. I was hoping it was as simple as that for you tho. Defiantly Strange. Believe me I've had plenty of those moments where hours would have been saved if someone could have just said "no your just doing it wrong".
Maybe try rerunning the RUU and start from scratch the PRI fix should hold thru the RUU but if it did affect something else running the RUU again may correct it.
I RUU'd about 4 times so far on two different laptops, one with XP and one with Win7, running both versions of the HTC Sync drivers.
Something is definitely different. I'm thinking of doing the PRI fix again to see if that helps. The PRL being 65000 instead of the normal 60664 is another anomaly I'm curious about.
looks as if the 65000 PRL is a new one. I can't confirm (not with Sprint) but there is a thread over in General talking about it.
http://forum.xda-developers.com/showthread.php?t=684873
YEAH! I fixed it....well....actually Flipz fixed it for me. I created a custom ROM in the kitchen and flashed it. Now the remount miraculously works. I'm back to being happy...though I don't know why. Its not like I was using root for anything
Nextelian said:
right, this is at the c:\android-sdk-windows\tools\ prompt. I guess I need to re-word that last bullet point to be more clear.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
Click to expand...
Click to collapse
Can someone splain how to fix this issue w/o flashing? Like maybe from command prompt/shell? Pleeeeease?
mrsato said:
Can someone splain how to fix this issue w/o flashing? Like maybe from command prompt/shell? Pleeeeease?
Click to expand...
Click to collapse
I found something that help me and you. it properly works!!
I can't spell out instructions for the above mentioned suggestion, since I
don't know which file editor comes on the shipped device, but I have an
alternative solution.From the SDK's tools directory, run adb shell. In the
prompt run the following:
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system (Or any subdirectory you want to push to inside system)
# exit
adb push <local file> <device location>
and eventually you should restore the original directory permissions by:
# chmod 755 /system (Or any subdirectory you modified permissions to)
Hope this helps,
Yoav
Click to expand...
Click to collapse
still no Read/Write on /system
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
mojotexas said:
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
Click to expand...
Click to collapse
I'm not at my computer but I think the command is off... check to make sure its exactly how it should be... maybe the coma after the rw
Sent from my HERO200 using XDA App
mojotexas said:
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
Click to expand...
Click to collapse
Just cd to your tools directory and adb remount
huedawg said:
Just cd to your tools directory and adb remount
Click to expand...
Click to collapse
Is there a solution for this?
I have a rooted HTC Desire.
When I type adb remount I get permission denied.
When I type adb shell and then su , i get permission denied!
This was a stock 2.2 rooted with unrevoked 3.
Any idea?
[edit]
i noticed root permissions pop-up on the phone and allowed so su worked.
[/edit]
Hi,
I have a Desire with stock froyo rooted with unrevocked 3 too and cannot use adb remount:
D:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
D:\android-sdk-windows\tools>adb shell
$ remount
remount
remount: permission denied
$
Click to expand...
Click to collapse
I have allowed ADB via the Super user app popup.
Any idea?
EDIT: I have set S-OFF using AlphaRev's recovery fastboot and I am now able to remount in rw (well no access denied anymore)
still missing some access as I fail to remove the Google Maps app (want to use Brut maps only)
ghost_boy1412 said:
I found something that help me and you. it properly works!!
Click to expand...
Click to collapse
This worked perfectly! Thank you!
Good freakin lord why the heck did you feel the need to bump this thread thats almost a year old just to say that!!!!!!!! I rarly shout like this, but this crap is starting to drive me crazy!!!!!!!!!!!!
Grrrrrrrrrrrrrrr
same thing for me. i get permission denied
DannyMichel said:
same thing for me. i get permission denied
Click to expand...
Click to collapse
thank you for letting us all know, and in such detail, and with new valuable information no less
/me shakes fists in rage.
Post deleted.
Don't mean to bring up this dead thread but a more simple solution would be this
adb shell
$ su
# busybox mount -o remount,rw /system (or another desired directory)
# chmod 777 (or another desired permission set) /system (or another desired directory)
# exit
$ exit

Root Issue FRF91

I have...
Nexus one
FRF91, android 2.2
Radio: 4.06.00.12_7
Recovery: Recovery-RA-nexus-v1.7.0.1
I fallowed all the steps on unlockr.com to root my N1. I see the Superuser Permissions installed, but I still don't have root access. I attempted to delete the amazon mp3 app from my phone with the fallowing command:
adb remount
adb shell rm /system/app/*amaz*
and I'm replied with a Read-only error. Also, when I installed Titanium Backup, i was not able to gain root access after SU prompted me for permission (i allowed).
I have tried to re-root the device, but I'm told by superboot (updated FRF91 version) that the device has been rooted.
you gotta remount the /system to make big changes like that..
so you would go
mount -o remount,rw /dev/block/mtdblock3 /system
rm /system/app/amazon.apk
and should remove it from there.. you can also get terminal emu from market and use that with in terminal
ilostchild said:
you gotta remount the /system to make big changes like that..
so you would go
mount -o remount,rw /dev/block/mtdblock3 /system
rm /system/app/amazon.apk
and should remove it from there.. you can also get terminal emu from market and use that with in terminal
Click to expand...
Click to collapse
I just got the N1 yesterday, was on the MT3G before it. Another little step I need to remember.
Thank you, it worked perfectly.
np and welcome

[Q] Mounting /system partition under adb shell

Hi,
I want to deodex stock rom myself, so...
what variables in mount command I should use to properly mount /system partition in rw under adb shell?
Cheers
masi0 said:
Hi,
I want to deodex stock rom myself, so...
what variables in mount command I should use to properly mount /system partition in rw under adb shell?
Cheers
Click to expand...
Click to collapse
try: adb shell mount -o remount,rw system
Code:
adb remount
It should do the trick too
gromez said:
Code:
adb remount
It should do the trick too
Click to expand...
Click to collapse
lol, that's shorter indeed
adb remount will only remount an existing mount, it won't create one.
It's not clear what the OP wants.
You don't need rw to deodex a ROM because you certainly don't want to write to system whilst you're doing it.
Also, I thought the stock ROM was deodexed?
To mount system in recovery, which will give you rw access and allow you to pull the files you need you just type:
Code:
mount /system
or
Code:
adb shell mount /system
Because system is included in /proc/mtd
to all: the answer is:
mount -o rw,remount /dev/block/mmcblk0p1 /system
Click to expand...
Click to collapse
masi0 said:
to all: the answer is:
Click to expand...
Click to collapse
Hello
in my case, what it worked:
mount -o rw,remount /system
Why is this thread in development section, are you that stupid?
Sent from my LG-P990 using xda app-developers app
Micronuub said:
Why is this thread in development section, are you that stupid?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
I already reported it
In my case except adb nothing is working as i cannot access system folder.
In my case except adb nothing is working as i cannot access system folder.
Can anyone suggest me what to do or what i should do as no flash tool or anything other option is working except adb.
also $ SU is not working please help me its driving crazy.
TheSSJ said:
I already reported it
Click to expand...
Click to collapse
Here's a solution
masi0 said:
Hi,
I want to deodex stock rom myself, so...
what variables in mount command I should use to properly mount /system partition in rw under adb shell?
Cheers
Click to expand...
Click to collapse
Hi, this seems to work for me:
Open a terminal (Command Prompt).
type adb shell
type su
You should see a # in your prompt.
type mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
and Bingo! Your /system is now mounted as r/w. [NOTE: There will be no confirmation message. Your command will simply be printed again, and that means its a success)
The possible error might be that you forgot the su part. I'm making a wild guess that it stands for superuser. The first time I tried this, I didn't know about the 'su' and I wasted a little time because of that.
Hope this helped.
helllpppp
rktcool said:
Hi, this seems to work for me:
Open a terminal (Command Prompt).
type adb shell
type su
You should see a # in your prompt.
type mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
and Bingo! Your /system is now mounted as r/w. [NOTE: There will be no confirmation message. Your command will simply be printed again, and that means its a success)
The possible error might be that you forgot the su part. I'm making a wild guess that it stands for superuser. The first time I tried this, I didn't know about the 'su' and I wasted a little time because of that.
Hope this helped.
Click to expand...
Click to collapse
i used an app ldc dpi modder n its bricked with black screen n im on cm10 now it want to change chmod to 644 for my lww but i dont know how to do that please help me with step by step guide im new to this things
this worked for me:
mount -o rw,remount /system

Busybox/System RW/Metamorph

Right,
I have been trying to mount system as RW so i can install busybox - ( as busybox install is failing saying "device is not nand unlocked or unable to remount")
I have s-off and root (the superuser app is there and rootchecker says so)
so first i ran command
mount -o rw,remount /dev/block/mmcblk0p2 /system
Click to expand...
Click to collapse
and this was failing saying
mount: Permission denied
Click to expand...
Click to collapse
so i tried
adb remount
Click to expand...
Click to collapse
then i check cat /proc/mounts and got
/dev/block/mmcblk0p25 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
Click to expand...
Click to collapse
so i assumed all was ok ...
however ... in terminal emulator on the phone i try simple command "ls" or "mount" and i get permission denied again (from su)
terminal emulator has root privileges
but still busybox wont install saying the SAME error.
all this stemmed from trying to install MetaMorph and it saying "some files could not be installed. Check /system for space"
i have 300mb of space in /system - after some research i found it could be because system isnt RW ... and thats where im at now ..
So, any help would be appreciated
Have you tried
adb shell
su
Did su from terminal change cursor and request super user permission?
Sent from my HTC Desire S using XDA Premium App
In terminal emulator on phone it changed from a
$ to # after su
In terminal on my desktop its always a #

[TEMPORAL-FIX] Remount RW /system reboot

Hello guys, i know that maybe some people have the same issue, i was able to bypass this using a not very beautiful solution but it works perfect lol.
Check this:
Code:
1. Connect your phone with adb, then type adb shell
2. Type su, to get root access
3. Type stop ric
4. Type busybox pkill -f /sbin/ric
5. Type this "mount -ro remount,rw /" without the quotes to remount / as rw
6. Type this "chmod 0440 /sbin/ric" without the quotes
6. Copy the file build.prop from /system to /
7. Open this file using a root text editor, in my case i used Root Explorer
8. Add this "ro.secure=0" without the quotes below "ro.build.host"
9. Save the changes to the file
10. Type stop ric
11. Type busybox pkill -f /sbin/ric
12. Type "mount -ro remount,rw /system" without the quotes to remount /system as rw, after you do this, please continue to other steps as fast you can.
12. Type busybox cp -af /build.prop /system/build.prop
13. rm /build.prop
14. Done. Now you should be able to mount /system as rw too.
I tested this because i was trying to get ubuntu to run on my system but the bootscript was trying to mount my /system as rw, it was rebooting my tablet but now i've ubuntu perfect and running.
See my attachments
UPDATE: Links to the Full HD images
1. http://cl.ly/image/42210t2X3B1r
2. http://cl.ly/image/2P2S3T1S0k3v
3. http://cl.ly/image/04120x0r1B0B
4. http://cl.ly/image/1f0N310P1O0c
juanyunis said:
Hello guys, i know that maybe some people have the same issue, i was able to bypass this using a not very beautiful solution but it works perfect lol.
Check this:
Code:
1. Connect your phone with adb, then type adb shell
2. Type su, to get root access
3. Type stop ric
4. Type busybox pkill -f /sbin/ric
5. Type this "mount -ro remount,rw /" without the quotes to remount / as rw
6. Type this "chmod 0440 /sbin/ric" without the quotes
6. Copy the file build.prop from /system to /
7. Open this file using a root text editor, in my case i used Root Explorer
8. Add this "ro.secure=0" without the quotes below "ro.build.host"
9. Save the changes to the file
10. Type stop ric
11. Type busybox pkill -f /sbin/ric
12. Type "mount -ro remount,rw /system" without the quotes to remount /system as rw, after you do this, please continue to other steps as fast you can.
12. Type busybox cp -af /build.prop /system/build.prop
13. rm /build.prop
14. Done. Now you should be able to mount /system as rw too.
I tested this because i was trying to get ubuntu to run on my system but the bootscript was trying to mount my /system as rw, it was rebooting my tablet but now i've ubuntu perfect and running.
See my attachments
Click to expand...
Click to collapse
Also i've my bootloader locked, so i believe this could work for both (unlocked and locked).
juanyunis said:
Also i've my bootloader locked, so i believe this could work for both (unlocked and locked).
Click to expand...
Click to collapse
unlocked bootloader users don´t have the reboot problem :silly: o i think sony want´s to stop the people from rooting without having an unlocked bootloader.
mine is unlocked, had no reboot problems on .370 rooted but i´m on cm10.1 now tough i had no probs with stock. i love the stock android interface and top statusbar.
om22 said:
unlocked bootloader users don´t have the reboot problem :silly: o i think sony want´s to stop the people from rooting without having an unlocked bootloader.
mine is unlocked, had no reboot problems on .370 rooted but i´m on cm10.1 now tough i had no probs with stock. i love the stock android interface and top statusbar.
Click to expand...
Click to collapse
That's nice to hear, but it makes sense because with a customer recovery that would be very easy to fix lol.
I do love CM 10.1, but i don't want to loose BE2. In my case i love how it works making my colors more vibrant but well i'm use to AMOLED displays so you can imagine.
I hope to see a way to bypass this or maybe a new stock firmware from Sony with the new status bar.
Thanks for reporting that you don't have this issue!
juanyunis,
Could you please share or write a manual for installation of Ubuntu on Tablet Z?
theZest said:
juanyunis,
Could you please share or write a manual for installation of Ubuntu on Tablet Z?
Click to expand...
Click to collapse
Sure I'll write one tomorrow. It's very easy once you have root with remount system fixed. Have a good day.
Sent from my Samsung Galaxy S4
This fix didn't work for me. To be more precise, it worked until I turned off the tablet. After I started the tablet, remouting caused reboots again. :crying:
---------- Post added at 10:11 PM ---------- Previous post was at 10:07 PM ----------
Oh, just to add,. I verified that the /system/build.prop file was saved correctly. The line is added.
fness said:
This fix didn't work for me. To be more precise, it worked until I turned off the tablet. After I started the tablet, remouting caused reboots again. :crying:
---------- Post added at 10:11 PM ---------- Previous post was at 10:07 PM ----------
Oh, just to add,. I verified that the /system/build.prop file was saved correctly. The line is added.
Click to expand...
Click to collapse
It's a temporal fix lol, but you can use Fisherman ROM with that fixed, i just don't need to use this fix all the time. But once you did this, you can open a terminal on your tablet and run this:
1. su
2. chmod 0444 /sbin/ric
3. stop ric
4. busybox pkill -f /sbin/ric
If you want this to be a permanent solution you can create a sh script with those commands and then user a init.d app like CPD Adjuster to run that script on boot. I'll try to do this for you.
Thanks, now I understand. Stupid of me really. It says temporal in the title.
juanyunis said:
Hello guys, i know that maybe some people have the same issue, i was able to bypass this using a not very beautiful solution but it works perfect lol.
Check this:
Code:
1. Connect your phone with adb, then type adb shell
2. Type su, to get root access
3. Type stop ric
4. Type busybox pkill -f /sbin/ric
5. Type this "mount -ro remount,rw /" without the quotes to remount / as rw
6. Type this "chmod 0440 /sbin/ric" without the quotes
6. Copy the file build.prop from /system to /
7. Open this file using a root text editor, in my case i used Root Explorer
8. Add this "ro.secure=0" without the quotes below "ro.build.host"
9. Save the changes to the file
10. Type stop ric
11. Type busybox pkill -f /sbin/ric
12. Type "mount -ro remount,rw /system" without the quotes to remount /system as rw, after you do this, please continue to other steps as fast you can.
12. Type busybox cp -af /build.prop /system/build.prop
13. rm /build.prop
14. Done. Now you should be able to mount /system as rw too.
I tested this because i was trying to get ubuntu to run on my system but the bootscript was trying to mount my /system as rw, it was rebooting my tablet but now i've ubuntu perfect and running.
See my attachments
UPDATE: Links to the Full HD images
1. http://cl.ly/image/42210t2X3B1r
2. http://cl.ly/image/2P2S3T1S0k3v
3. http://cl.ly/image/04120x0r1B0B
4. http://cl.ly/image/1f0N310P1O0c
Click to expand...
Click to collapse
Hi!
When i edit the build.prop file i have bootloop issue!
So i'm traying the bellow
su
mount -ro remount,rw /
chmod 0440 /sbin/ric
stop ric
busybox pkill -f /sbin/ric
Then you can mount /system as rw from a file explorer (estrong)
The attached file (unzip first) you can use it with ROM toolbox (add as new script) and execute as root and on boot option (if you want a permanent solution)
It's very useful when I deodex my ZULTRA without CWM.
Just to say thanks.
And.....can I use your method in my post?
http://forum.xda-developers.com/showthread.php?t=2468109
Easy Method Linux Install...
There is an app on the play store called "Complete Linux Installer" it works perfectly fine and you can pick from different distros, I tried Ubuntu and Debian. If you can find the full version somewhere for "free" you can customize your screen rez. There is a free version that has some restrictions. You also need androidVNC to mount. This runs on top of android so when you are done with linux you just shut it down to go back to android.
juanyunis said:
Hello guys, i know that maybe some people have the same issue, i was able to bypass this using a not very beautiful solution but it works perfect lol.
Check this:
Code:
1. Connect your phone with adb, then type adb shell
2. Type su, to get root access
3. Type stop ric
4. Type busybox pkill -f /sbin/ric
5. Type this "mount -ro remount,rw /" without the quotes to remount / as rw
6. Type this "chmod 0440 /sbin/ric" without the quotes
6. Copy the file build.prop from /system to /
7. Open this file using a root text editor, in my case i used Root Explorer
8. Add this "ro.secure=0" without the quotes below "ro.build.host"
9. Save the changes to the file
10. Type stop ric
11. Type busybox pkill -f /sbin/ric
12. Type "mount -ro remount,rw /system" without the quotes to remount /system as rw, after you do this, please continue to other steps as fast you can.
12. Type busybox cp -af /build.prop /system/build.prop
13. rm /build.prop
14. Done. Now you should be able to mount /system as rw too.
I tested this because i was trying to get ubuntu to run on my system but the bootscript was trying to mount my /system as rw, it was rebooting my tablet but now i've ubuntu perfect and running.
See my attachments
UPDATE: Links to the Full HD images
1. http://cl.ly/image/42210t2X3B1r
2. http://cl.ly/image/2P2S3T1S0k3v
3. http://cl.ly/image/04120x0r1B0B
4. http://cl.ly/image/1f0N310P1O0c
Click to expand...
Click to collapse
it will be better to execute the commands like this in a row (one single line) as to execute them asap:
mount -o remount,rw /system; mv /build.prop /system/; chmod 644 /system/build.prop; mount -o remount,ro /system
Bootloop!
I followed the instructions on the first page and successfully mounted /system as RW. Then I rebooted (by typing reboot in ADB), and now my tablet is in a bootloop.
I didn't touch anything other than build.prop and media_codecs.xml. What should I do?
Edit: Solved by flashing FTF.
is there any save way to run it on a 16GB wifi only model ? I have root, but my BL is locked.
did try the script form page 1 but this did not work. I am not sure about edeting the build.prop witht the bootloop problems :/
greetings
edit: it would be fine if i can edit the host file from the pc just once, without rw access from the tab itself, i just wanna get rid of those annoying ads everywhere
very usefull on xperia z1 thanks man :good:

Categories

Resources