Database Develop

SU - Reboot - not permitted!

Hi all,
Didn't find anything on this, hoping for some clarification.
Shell snippet(terminal on phone):
$su
#reboot
not permitted!
in short - reboot and reboot recovery commands do not work via terminal. want this ability for GScript.
i installed the super boot image from modaco, i've re-installed the superuser.apk and also ran the commands manually from /superboot/superboot.sh on the phone...is any one else having this problem or has anyone found a solution to the issue? please also note that i have in fact reflashed the superboot image twice now, still no resolve. halp!

Same issue
I still have the same issue... I can't do it

check permissions in SuperUSER.apk and see if you have it enable to do so

Hi all,
i get the same issue on my EVO 4G. not permited! when i type reboot or reboot recovery and i know for a fact that supersuer allowed root access to TU. this used to work before on superuser 2.1 now i have SU 2.3.5. anyone ?

i have the same problem -.-

Do you have the toolbox binary in /system/bin as well as a symlink named reboot pointing to it? 'reboot' is not a native command and you'll find that most (if not all) "shell commands" are actually binaries and shell scripts. Even something as simple as 'mv' (move) is a binary, not built into the shell. Ensure that you have a reboot symlink that points to toolbox. It's quite possible that your rom (or superboot) doesn't include it.
You can also download Quick Boot by Sirius Applications Ltd. From the market. It lets you reboot, reboot into recovery and reboot into fastboot, plus you can make shortcuts to each different reboot on your home screen. (market link)

Have busybox installed..(think thats what Chains jus said)
if you do.. try this
Busybox reboot

ilostchild said:
Have busybox installed..(think thats what Chains jus said)
if you do.. try this
Busybox reboot
Click to expand...
Click to collapse
I was using the extended controls widget but that stopped working.
running su, reboot, gives not permitted!
running su, busybox reboot, gives no error but doesn't reboot the phone.
trying the quickboot app now ...
*** quickboot works great ... I don't know what the problem is though ..

this command work well!
command : busybox restart -f
i can use this command to restart samsung and htc phone

here's the latest--
http://dl.dropbox.com/u/28338566/Superuser-3.0.7-efghi-signed.zip
Had same issue till I flashed this
I forget if I just flashed or extracted the apk and pushed--sorry--just had sugery and not remembering all that well
I flash different roms so hope someone can ok this for any rom--not sure why not

Anything new on this? I am having the same issue with my HTC one. With busy box installed there is a reboot bin in /system/bin that gives the "Not permitted!" Message when ran from the phone.
Busy box installs reboot in /system/xbin and when you disable or remove the reboot binary in /system/bin it executes the one in /system/xbin however it does nothing unless you add a -f to the command' and all you can do is regular reboot (no bootloader or recovery)
Works:
/system/xbin/reboot -f
Reboot recovery command using adb shell on computer
Does not work:
/system/bin/reboot [anything]
/system/xbin/reboot -f recovery (boot loader,etc)
This stinks because rebooting to recovery from apps won't work
There must be a way to hack this into a working reboot recovery command

Ok
Sent from my SGH-M919G using xda premium

orthonovum said:
Anything new on this? I am having the same issue with my HTC one. With busy box installed there is a reboot bin in /system/bin that gives the "Not permitted!" Message when ran from the phone.
Busy box installs reboot in /system/xbin and when you disable or remove the reboot binary in /system/bin it executes the one in /system/xbin however it does nothing unless you add a -f to the command' and all you can do is regular reboot (no bootloader or recovery)
Works:
/system/xbin/reboot -f
Reboot recovery command using adb shell on computer
Does not work:
/system/bin/reboot [anything]
/system/xbin/reboot -f recovery (boot loader,etc)
This stinks because rebooting to recovery from apps won't work
There must be a way to hack this into a working reboot recovery command
Click to expand...
Click to collapse
I'm having the same problem. I did notice that my system/xbin folder is missing quite a bit of the files as the system/bin folder, including the reboot file. I assume it doesn't need to mirror it exactly, but should it have the reboot file also? If not, should there be a symbolic link in the xbin folder to link the reboot file in the bin folder? Thanks in advance for any and all help.
By the way, I am rooted, boot unlocked, and s-off running the Android Revolution HD rom.

I had this issue now reboot works (in a way)
This might be naughty of me to bring up an old thread but others have done and its only a few weeks sincle last post...
Anyways I had this issue from what I have read it only happens to people to certain people on certain phones.
I was able to reboot though a mobile terminal emulator, ssh, and though the shell while in usb.
I noticed that only though ADB would it accept reboot (security reasons?) so I read a nifty article on using ADB though tcp and to make it more secure I used it though localhost since only I can use it.
here is the commands that I used:
Code:
stop adbd && stop adb && setprop service.adb.tcp.port 5555 && start adbd && sleep 4 && adb connect localhost && adb reboot
It feels more like a work around but my personal goal was reboot my phone though a remote sms (remote terminal) and it worked within a shell so wohoo. I hope it helps someone and setting ADB to listen on usb is
Code:
setprop service.adb.tcp.port -1
I had to use sleep to make sure ADB started before I tried to connect... you can add reboot bootloader...etc..adb commands....
I guess you can make this into a file called myReboot.sh and link it to make it a "command"

My solution
To root, updated version of Android Gingerbread, from there, I downloaded the same version, but Japanese, walked into the boot, and updated to version japonsa from there to root nexus one and go.

Download quick reboot form the play store
Sent from my Nexus 7 using XDA Premium 4 mobile app

SU - Reboot - not permitted! solved
SOLVED:
Not all linux commands r available on andriod(depends upon rooting how u did that), to do that just install BUSYBOX.
After installing busybox u have every command. Enjoy

Custom Recovery without Root?

I had previously unlocked my bootloader and was running CM6.1, but I had to go back to stock because my company's email app (Good for Enterprise) refuses access on rooted devices.
I would like to monkey around with different configurations to see if I can find a way to run Good on CM6.1. I don't want to do this if I have to reinstall everything if it doesn't work however.
So my question is this. I just want to get the Clockwork recovery on my N1 so I can back up the non-rooted OS and monkey around a little. Can this be done with ABD on a non-rooted device?

Gave it a shot, worked fine.
"fastboot flash recovery clockwork-image-name.img"
Good for Enterprise still runs, so it isn't looking at the recovery to determine rooted status.
Nevermind, clockwork didn't survive a reboot. Good news is I was able to get a backup first.

After installing recovery via fastboot, try removing the following files via adb:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Nexus One using XDA App

danger-rat said:
After installing recovery via fastboot, try removing the following files via adb:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
When I try to do this from the recovery, these files are not found, and adb can't see the device from the bootloader. If I boot into the OS, it will be too late - the recovery would be wiped by then and I am back to square one. I must be missing something.
Is there any way to pull the System partition and mount the .img file on my PC to do this? That sounds a little dangerous though

Just thought, you need root to delete the files.
You'd probably have to root, install recovery, then install a non-rooted ROM, but keep custom recovery...
Sent from my Nexus One using XDA App

This is what you need to do:
1) boot your device into the OS
2) download the rageagainstthecage binary and save it as rageagainstthecage in the /tools folder (in the android SDK)
3) plug your device to your computer
4) open a command prompt in the /tools directory
5) type adb devices to make sure your computer sees your device
6) push the rageagainstthecage binary to /data/local/tmp/ by typing adb push rageagainstthecage /data/local/tmp/rageagainstthecage
7) type adb shell to open a shell
8) change the permissions on the binary to allow it to run by typing chmod 700 /data/local/tmp/rageagainstthecage
9) navigate to the directory (cd /data/local/tmp) and execute the binary by typing ./rageagainstthecage
10) wait for it to run, and it will exit the shell
enter the following command at the prompt: adb kill-server
11) enter the following command at the prompt: adb start-server
12) open an adb shell again: adb shell
13) now you should have a temporary root shell. You should see a # instead of a $. if you still see the $, go back to step 9. You may have to do this a few times (I had to do it 3 times before I got root access)
14) now, mount the /system partition as r/w by typing mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
15) delete the two files: rm /system/etc/install-recovery.sh and rm /system/recovery-from-boot.p
16) mount the partition as r/o by typing mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
17) exit the shell
18) now flash your custom recovery

Awesome, thanks. I'll give it a shot later!

This worked flawlessly, thanks for the great writeup!

Santoro said:
This worked flawlessly, thanks for the great writeup!
Click to expand...
Click to collapse
Two things: First, don't forget that any update from Google always has those two files in it, so they will reappear after every update.
Second, I just reread your first post again. I think you should still be able to kepp root and have your company's email working. I think the problem was that you were using an AOSP-based ROM instead of a stock-based one. Follow the directions for rooting in my signature (the first part is essentially the same as what you just did to gain r/w access to the system partition via adb, the second part is copying su and Superuser.apk to the right directories). Root is essentially one additional file copied to your /system directory, so I believe your company's email will still work with root.

efrant said:
This is what you need to do:
1) boot your device into the OS
2) download the rageagainstthecage binary and save it as rageagainstthecage in the /tools folder (in the android SDK)
3) plug your device to your computer
4) open a command prompt in the /tools directory
5) type adb devices to make sure your computer sees your device
6) push the rageagainstthecage binary to /data/local/tmp/ by typing adb push rageagainstthecage /data/local/tmp/rageagainstthecage
7) type adb shell to open a shell
8) change the permissions on the binary to allow it to run by typing chmod 700 /data/local/tmp/rageagainstthecage
9) navigate to the directory (cd /data/local/tmp) and execute the binary by typing ./rageagainstthecage
10) wait for it to run, and it will exit the shell
enter the following command at the prompt: adb kill-server
11) enter the following command at the prompt: adb start-server
12) open an adb shell again: adb shell
13) now you should have a temporary root shell. You should see a # instead of a $. if you still see the $, go back to step 9. You may have to do this a few times (I had to do it 3 times before I got root access)
14) now, mount the /system partition as r/w by typing mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
15) delete the two files: rm /system/etc/install-recovery.sh and rm /system/recovery-from-boot.p
16) mount the partition as r/o by typing mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
17) exit the shell
18) now flash your custom recovery
Click to expand...
Click to collapse
Without unlock recovery i can install Amon RA?(‘fastboot oem unlock‘)In this way as u typed.

W3ber said:
Without unlock recovery i can install Amon RA?(‘fastboot oem unlock‘)In this way as u typed.
Click to expand...
Click to collapse
Not sure what you are asking.
If your bootloader is unlocked, you can use fastboot. Download the recovery image you want into the /tools directory of your SDK and rename it recovery.img. Open a command prompt in the same directory. Type fastboot devices to make sure fastboot sees you device. Then type fastboot flash recovery recovery.img and you are done.
If your bootloader is not unlocked, you can use flash_image, but you need root access. See attachments on how to get root if your bootloader is locked, and how to flash a custom recovery with a locked bootloader.

efrant said:
Two things: First, don't forget that any update from Google always has those two files in it, so they will reappear after every update.
Second, I just reread your first post again. I think you should still be able to kepp root and have your company's email working. I think the problem was that you were using an AOSP-based ROM instead of a stock-based one. Follow the directions for rooting in my signature (the first part is essentially the same as what you just did to gain r/w access to the system partition via adb, the second part is copying su and Superuser.apk to the right directories). Root is essentially one additional file copied to your /system directory, so I believe your company's email will still work with root.
Click to expand...
Click to collapse
I was using the Nexus One 2.2.1 stock image directly from Google. My problem is that the Good for Enterprise actively checks for root. Specifically if the Superuser.apk exists, it refuses to let me in and cites corporate policy.
Since getting my stock backup, I was free to experiment and I had some success getting Good running on CM 6.1. Taking clues from your earlier instructions, I used adb shell to rename su to su.bak and Superuser.apk to Superuserapk.bak on the phone, then rebooted. After the reboot, I don't have root anymore.
This is a compromise, but at least I don't have to give up that CM6 goodness just to use my corporate email. So far I have not seen any issues in CM6 resulting from not having root. In an emergency I can rename them the superuser files back using rageagainsthecage as you outlined but I probably won't do it often.
Thanks for the help!

Santoro said:
I was using the Nexus One 2.2.1 stock image directly from Google. My problem is that the Good for Enterprise actively checks for root. Specifically if the Superuser.apk exists, it refuses to let me in and cites corporate policy.
Since getting my stock backup, I was free to experiment and I had some success getting Good running on CM 6.1. Taking clues from your earlier instructions, I used adb shell to rename su to su.bak and Superuser.apk to Superuserapk.bak on the phone, then rebooted. After the reboot, I don't have root anymore.
This is a compromise, but at least I don't have to give up that CM6 goodness just to use my corporate email. So far I have not seen any issues in CM6 resulting from not having root. In an emergency I can rename them the superuser files back using rageagainsthecage as you outlined but I probably won't do it often.
Thanks for the help!
Click to expand...
Click to collapse
Just for your info, Superuser.apk does not give you root, it only manages the root permissions. If your corporate email application checks only for Superuser.apk, you could technically delete Superuser.apk and keep the su binary. Your would still have root, and your corporate email app would work. The su binary is what actually gives you root access. All that the Superuser.apk file does is manages the permissions for root access, i.e., it allows or denies applications from using the su binary. Everything would work fine (including all apps that require root) without Superuser.apk. HOWEVER, just as a warning, without Superuser.apk, you would have no control over which apps have root access...

I will have to put su back and see what happens. I may be recalling wrong, maybe it checks for su also...

I experimented a bit more and it looks for both files. Sorry for the confusion.

Manually Push CWM to Zv8 With Cmd Prompt.

I realize that these threads are every where but re posting in hopes of helping someone out. Every bit of mt's AIO worked for me, but AIO 2 for Zv8 would not.
You could always do this manually using adb. Here's how.
Push CWM Recovery image to your phone manually once in rooted zv8.
1. Open the ZV8CWMRecovery folder on your PC.
2. Double click the 'Files' folder to go into that directory.
3. Highlight/select and copy the address of your current folder location on your PC. It will look something like this:
Code:
C:\Documents and Settings\username\My Documents\Downloads\ZV8CWMRecovery\Files
4. Click Start>Run>type 'cmd' and hit enter/return to open your command prompt.
5. Type 'cd', hit your spacebar, then paste your address which you copied in step 3 into your command prompt, hit enter/return.
6. You should now be positioned in the folder containing the adb and CWMRecovery files.
7. Type the following to copy the CWMRecovery image to your phone:
Code:
adb devices
adb remount
adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img
adb shell dd if=/data/local/tmp/cwmrecovery.img of=/dev/block/mmcblk0p14 bs=4096
adb shell "rm /data/local/tmp/* 2>/dev/null"
adb shell rm /system/etc/install-recovery.sh
adb shell rm /system/recovery-from-boot.p
adb shell rm /data/local.prop
adb reboot
Phone should reboot. Try and boot into CWMRecovery after it reboots.
you can do that by typing: adb reboot recovery
all thanks go to brad 6360 for lending a hand and general lack of DoucheBaggery!

You're welcome. Glad I could help.

I'm stuck on adb remount cmd. Here's the output I get:
adb remount
remount failed: Operation not permitted
Any ideas? This is the same place I had issues running the AIO .bat file. Any help would be greatly appreciated!

JMink said:
I'm stuck on adb remount cmd. Here's the output I get:
adb remount
remount failed: Operation not permitted
Any ideas? This is the same place I had issues running the AIO .bat file. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Make sure you have internet connection and usb debugging enabled.

JMink said:
I'm stuck on adb remount cmd. Here's the output I get:
adb remount
remount failed: Operation not permitted
Any ideas? This is the same place I had issues running the AIO .bat file. Any help would be greatly appreciated!
Click to expand...
Click to collapse
I was having the same problems. No matter what I tried, AIO, this method, etc, nothing worked when I was using my computer to get CWM back after ZV8. I found this thread that uses terminal emulator on the phone and it worked perfectly.
http://forum.xda-developers.com/showthread.php?t=1594885

I never could get cwm working but a friend recommended QuickBoot, gives you the boot into recovery mode. Works great.
Sent from my VS910 4G using xda premium

This is the same thing as terminal emulater on your phone
with this you can open a shell inside your phone running on your pc
Same commands

Thanks for the suggestions. I ended up getting it to work. I just skipped the adb remount cmd and started with pushing the img. Then I used the su cmd in shell to get a # prompt and ran the rest of the cmds as written including reboot recovery. CWM popped up on boot!
Sent from my Revo 4g using XDA Premium App

Hoping someone can help
Hey all. Last night I was helping a friend keep root through the V8 update. Everything went fine until I thought that I had manually pushed clockwork, but when I tried to reboot into recovery I got stuck on the LG logo forever. How I'm having trouble getting the phone to do anything. When in emergency mode it won't connect to the computer and it's not even my phone so I feel like a real #$%^^. Any advice would be appreciated.
Edit: http://forum.xda-developers.com/showthread.php?t=1564941 allow me to answer my own question

4X HD hangs after updating busybox or something..

Hi guys,
I really need your help. I don't know what it caused, but my device now hangs after boot at the "Android führt ein Upgrade aus..." "Starten von Andwendungen..." Screen. I don't know how this is named in the english android, maybe something like "android does perform an upgrad..." "starting applications...". Normally this screen comes every boot for 1-3 seconds, but now it is stuck in it.
What I did before that?
- Upgraded Busybox (first time since a long time ago)
- Set hosts file back to normal via adfree
I updated to the new firmware "h" a few days ago. I do not often reboot, so maybe something else caused this, I wrote down the last things I remember above.
But I can connect to the device via adb, so please give me advice how to fix this without wiping or losing data.
If I could make it to the recovery, I think a wipe of the dalvik cache would help - but unfortunately it I cant get there (or at least I don't know how as I can not access the LG 4X Recovery App).
Please Help!
Thx!
Ps.: Is this the right Section? Sorry if not
Edit: I also tried http://forum.xda-developers.com/showthread.php?t=2006168 .. but that did not work!

keep it as it is
Use it as normal phone for two days. same happened to me for v10e update. But fixed automatically.

Subhajitdas298 said:
Use it as normal phone for two days. same happened to me for v10e update. But fixed automatically.
Click to expand...
Click to collapse
I can't use it. IT IS STUCK at this screen. Even after 10 times reboot...
I deleted busybox via adb and pushed the old one. The Main problem was that /system/xbin/busybox was gone. Fixed that -> bootes fine.
But one question remains: Why does it show this screen at every boot?
I know the mistake: I chose /system/bin as install location of busybox. It has to be /system/xbin!

Mhh, it happened again after installing busybox again

Evilandi666 said:
Mhh, it happened again after installing busybox again
Click to expand...
Click to collapse
so dont ?

Evilandi666 said:
Hi guys,
I really need your help. I don't know what it caused, but my device now hangs after boot at the "Android führt ein Upgrade aus..." "Starten von Andwendungen..." Screen. I don't know how this is named in the english android, maybe something like "android does perform an upgrad..." "starting applications...". Normally this screen comes every boot for 1-3 seconds, but now it is stuck in it.
What I did before that?
- Upgraded Busybox (first time since a long time ago)
- Set hosts file back to normal via adfree
I updated to the new firmware "h" a few days ago. I do not often reboot, so maybe something else caused this, I wrote down the last things I remember above.
But I can connect to the device via adb, so please give me advice how to fix this without wiping or losing data.
If I could make it to the recovery, I think a wipe of the dalvik cache would help - but unfortunately it I cant get there (or at least I don't know how as I can not access the LG 4X Recovery App).
Please Help!
Thx!
Ps.: Is this the right Section? Sorry if not
Edit: I also tried http://forum.xda-developers.com/showthread.php?t=2006168 .. but that did not work!
Click to expand...
Click to collapse
Just re-flash it...
By the way, it was rooted before you install or update busybox?

Tomaat said:
so dont ?
Click to expand...
Click to collapse
Yes, I can't update Busybox anymore via Stericson's app. When I do, my device hangs as described, even when correctly installed to /system/xbin/.
RuedasLocas said:
Just re-flash it...
By the way, it was rooted before you install or update busybox?
Click to expand...
Click to collapse
I just pushed the original busybox from the rooting package to /system/xbin and /data/local, that fixed it. Don't know why that happens.
Yes it was/is rooted.
As you can see here (http://forum.xda-developers.com/showpost.php?p=34498340&postcount=3), the stericson busybox seems to be the problem.

I try to update busy box (my backup pro does'n work properly without higher busy box version) and I have a boot screen stuck O4X now Flash rom again
Sent from my LG-P880 using xda premium

Root process already contains busybox, probably version conflict...
I'll try to upgrade mine

dracula3020 said:
Flash rom again
Click to expand...
Click to collapse
You don't need to do that. Just connect via usb and download o4xr.zip from the "How to Root" thread.
Then do the following:
- extract o4xr.zip and switch to that folder
- adb shell "su -c 'mount -o remount,rw -t ext4 /dev/block/mmcblk0p33 /system'"
- adb push busybox /sdcard/
- adb shell "su -c 'cat /sdcard/busybox > /data/local/busybox'"
- adb shell "su -c 'chmod 777 /data/local/busybox'"
- adb shell "su -c 'cat /sdcard/busybox > /system/xbin/busybox'"
- adb shell "su -c 'chmod 777 /system/xbin/busybox'"
- At this point the device will reboot itself automatically (Don't know why?), if not: adb shell 'su -c reboot'
- Delete /sdcard/busybox
- Done
RuedasLocas said:
Root process already contains busybox, probably version conflict...
I'll try to upgrade mine
Click to expand...
Click to collapse
The version in o4xr.zip is 1.19.3 (that does work), I tried every version in stericson's free busybox app (1.19.4, 2.0.x), none worked.
I think this problem didn't exist before v10H?

Evilandi666 said:
You don't need to do that. Just connect via usb and download o4xr.zip from the "How to Root" thread.
Then do the following:
- extract o4xr.zip and switch to that folder
- adb shell "su -c 'mount -o remount,rw -t ext4 /dev/block/mmcblk0p33 /system'"
- adb push busybox /sdcard/
- adb shell "su -c 'cat /sdcard/busybox > /data/local/busybox'"
- adb shell "su -c 'chmod 777 /data/local/busybox'"
- adb shell "su -c 'cat /sdcard/busybox > /system/xbin/busybox'"
- adb shell "su -c 'chmod 777 /system/xbin/busybox'"
- At this point the device will reboot itself automatically (Don't know why?), if not: adb shell 'su -c reboot'
- Delete /sdcard/busybox
- Done
The version in o4xr.zip is 1.19.3 (that does work), I tried every version in stericson's free busybox app (1.19.4, 2.0.x), none worked.
I think this problem didn't exist before v10H?
Click to expand...
Click to collapse
Can you please do a more detailed guide?

[SOLVED][Q] 4.4.3 after restart restores previous values

Hi!
I have problem with my HTC One m7 (ViperOne 7.0.1).
While I changed something in /system/app folder (eg. deleted a "DriveActivator.apk" - successfully accomplished) and restart phone, I see again that deleted app!!!
Do you know why? I'm using RootExplorer, I have root and granted permissions to r/w.
It seems like system restores some kind of backup - I don't know why, and I don't know how to fix it (I mean do some permanent changes in /system/app).

dry3333 said:
Hi!
I have problem with my HTC One m7 (ViperOne 7.0.1).
While I changed something in /system/app folder (eg. deleted a "DriveActivator.apk" - successfully accomplished) and restart phone, I see again that deleted app!!!
Do you know why? I'm using RootExplorer, I have root and granted permissions to r/w.
It seems like system restores some kind of backup - I don't know why, and I don't know how to fix it (I mean do some permanent changes in /system/app).
Click to expand...
Click to collapse
It appears that the System isn't booted with RW capabilities
There's a nice long command that I'll give you later that will fix it
If you wanna get it sooner and aren't afraid of adb shell (make sure you have root access enabled for adb AND apps, not just apps) you can Google remount Linux system read/write and you should find it
You'll need to modify that command to reflect the One, but the name of the partition should be something like by-name-system or something
I'll get it later if you need it when I wake up

ajbiz11 said:
It appears that the System isn't booted with RW capabilities
There's a nice long command that I'll give you later that will fix it
If you wanna get it sooner and aren't afraid of adb shell (make sure you have root access enabled for adb AND apps, not just apps) you can Google remount Linux system read/write and you should find it
You'll need to modify that command to reflect the One, but the name of the partition should be something like by-name-system or something
I'll get it later if you need it when I wake up
Click to expand...
Click to collapse
Thanks mate!
Stupid question - how I can check whether I have root access enabled for adb and apps? I have superuser app, and in settings I can see: "Superuser Access: Apps and ADB" - is this what you are wrote about?

dry3333 said:
Thanks mate!
Stupid question - how I can check whether I have root access enabled for adb and apps? I have superuser app, and in settings I can see: "Superuser Access: Apps and ADB" - is this what you are wrote about?
Click to expand...
Click to collapse
That's exactly what I'm referring to (The settings thing)
Lemme go find that command for you
---------- Post added at 06:00 AM ---------- Previous post was at 05:56 AM ----------
Wish I knew this existed when I was working on the L port
There's an app to do exactly what you need without looking up partitions
https://play.google.com/store/apps/details?id=com.beansoft.mount_system
Although if you want to go through terminal, here's a tutorial
http://ckirbach.wordpress.com/2012/11/27/how-to-remount-system-as-read-write-in-android/
Basically, you use grep to find the name of the system partition, then run the mount command to remount the partition you found in that precious step

I have this app: Mount /system (rw / ro), also I have this option in superuser and it works fine - I mean that I can change /system/app or for eg. edit /etc/hosts (I get message that ES explorer granted superuser access), but after restart I see previous files (before changes)... I have no idea how make this work - maybe I need custom kernel or something? I want to make permanent changes in system files...
I have reinstalled system (clean option with wipe all data), but still no results...

dry3333 said:
I have this app: Mount /system (rw / ro), also I have this option in superuser and it works fine - I mean that I can change /system/app or for eg. edit /etc/hosts (I get message that ES explorer granted superuser access), but after restart I see previous files (before changes)... I have no idea how make this work - maybe I need custom kernel or something? I want to make permanent changes in system files...
I have reinstalled system (clean option with wipe all data), but still no results...
Click to expand...
Click to collapse
The remount app should do exactly that
Try the command option and make your changes then reboot

ajbiz11 said:
The remount app should do exactly that
Try the command option and make your changes then reboot
Click to expand...
Click to collapse
I have tried - still no results. My system already has RW permissions. Problem is that after restart my files are "restored".
Analogously like in Cisco IOS - commit but without write memory.
Maybe I should go to recovery and do something (but I don't know what)?

dry3333 said:
I have tried - still no results. My system already has RW permissions. Problem is that after restart my files are "restored".
Analogously like in Cisco IOS - commit but without write memory.
Maybe I should go to recovery and do something (but I don't know what)?
Click to expand...
Click to collapse
Check the Viper forum and maybe post there
I only run CM-base so I'm not too experienced with Sense issues

ajbiz11 said:
Check the Viper forum and maybe post there
I only run CM-base so I'm not too experienced with Sense issues
Click to expand...
Click to collapse
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?

dry3333 said:
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?
Click to expand...
Click to collapse
You can remove it from the ViperROM zip and format ONLY system and reflash
That SHOULD work
That's like...the be all end all

dry3333 said:
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?
Click to expand...
Click to collapse
Make life simple: erase the apk while in custom recovery, TWRP has a file manager, or you can use Aroma File Manager
even adb commands while booted in custom recovery are better than booted up ROM.

nkk71 said:
Make life simple: erase the apk while in custom recovery, TWRP has a file manager, or you can use Aroma File Manager
even adb commands while booted in custom recovery are better than booted up ROM.
Click to expand...
Click to collapse
Thanks for advice. Is it possible via TWRP not only remove file, but also replace it? Where shoul I place new file for replace original one?

dry3333 said:
Thanks for advice. Is it possible via TWRP not only remove file, but also replace it? Where shoul I place new file for replace original one?
Click to expand...
Click to collapse
I would recommend using the Aroma File Manager instead of TWRP's, just place all the files you'll need on your internal storage (including Aroma File Manager), then reboot to select "Install" to run the Aroma File Manager and remove/replace whatever you need to.
You may need to also check if the permissions are right, I can't remember if Aroma File Manager has that built in.
remember that once you are in recovery to mount /system (in the Mount menu)
and you can even use adb shell, and adb push commands to replace the .apk.... i'm just guessing it's easier with a GUI interface.

nkk71 said:
I would recommend using the Aroma File Manager instead of TWRP's, just place all the files you'll need on your internal storage (including Aroma File Manager), then reboot to select "Install" to run the Aroma File Manager and remove/replace whatever you need to.
You may need to also check if the permissions are right, I can't remember if Aroma File Manager has that built in.
remember that once you are in recovery to mount /system (in the Mount menu)
and you can even use adb shell, and adb push commands to replace the .apk.... i'm just guessing it's easier with a GUI interface.
Click to expand...
Click to collapse
The windows drivers don't work with recovery mode (usually)

ajbiz11 said:
The windows drivers don't work with recovery mode (usually)
Click to expand...
Click to collapse
they do for me, but sometimes (after flashing a new/different version) i have to manually select the drivers, check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

I would like to thank you for advice. I did this via TWRP (after I had mounted /system). It works fine for me

dry3333 said:
I would like to thank you for advice. I did this via TWRP (after I had mounted /system). It works fine for me
Click to expand...
Click to collapse
sure, no problem :good: :good:
if all is good now, can you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title