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

[Q] At a Standstill

So I've decided I want 2.2 at least on my CDMA Hero. I am following this guide.
wiki.cyanogenmod[DOT]com/index.php?title=HTC_Hero_%28CDMA%29:_Full_Update_Guide
Well Here are the problems I am running into.
I can get Temporary root access to my phone. (Meaning I get # in the shell and my id check gives me a 0) However on restart i loose that root access. I have pushed the flash_image, su, Superuser.apk, and the recovery rom (using amon_ra) to their respective folders (flash_image goes to /sdcard/) and from what I can tell my su isn't working properly.
Essentially heres what happens
Shell opens up fine
#su
su
#cd /sdcard/
cd /sdcard/
#
My number sign after cd is still JUST a number sign. I was expecting #/sdcard/ but didn't get that, should I?
The reason I ask is because when I hit flash_image <image> it gives me
flash_image: not found.
I've personally checked that flash_image is on the root directory and it is, it is also named exactly that. So I can think of no reason flash_image isn't working except my su is bad. However just afterword I do an id check and I'm still root...
ugh...
*frusterated*
halp?

What ROM are you running right now? What version?
http://forum.xda-developers.com/wik..._CDMA.png#Rooting_.2F_Un-rooting_.2F_Flashing - has all links you might need to root and flash a ROM. Try and report back...

why dont you flash clockwork....it is easier (i think) and is very straight forward...
get rom manager from the market and flash CW recovery and then boot from it and flash the rom you want....

[Q] Rooting TELUS Optimus Black

Anyone figured out how to do it? I've tried following the guides with no success (gingerbreak). Model is P970g and software is 10a. Country code is TLS.
Anyone have a Telus OB and been able to root it? How did you do it?

I've rooted a couple of them, both 10a on Telus, one of them was pretty easy using z4root. Another one wouldn't work with z4root, latest superoneclick, gingerbreak or manually using adb shell to gingerbreak, rageaggainstthecage & psneuter. I did finally get the stubborn one to root wither an older superoneclick; version 1.6.5. Attached it below as it doesn't seem available in CLShortFuse's thread anymore.
Goodluck

alexredford said:
I've rooted a couple of them, both 10a on Telus, one of them was pretty easy using z4root. Another one wouldn't work with z4root, latest superoneclick, gingerbreak or manually using adb shell to gingerbreak, rageaggainstthecage & psneuter. I did finally get the stubborn one to root wither an older superoneclick; version 1.6.5. Attached it below as it doesn't seem available in CLShortFuse's thread anymore.
Goodluck
Click to expand...
Click to collapse
I tried both z4 and the superoneclick you suggested to no avail.
Do you think it's safe to try flashing another vulnerable rom? 10b or 10c? I'm worried the basebands may be different and the phone will have no voice/data connection.
Running out of ideas.

Attempted to root another one, same model, same version and none of the previous methods worked, was able to root this one as well using a combination of SOC 2.1.1 and the attached ADB Shell.
1. Download and run SuperOneClick 2.1.1, choose psneuter and click Shell Root
2. It should get stuck on step #4, run task manager, end superoneclick and terminate any adb.exe processes. (You should have Shell Root now)
3. Extract ADB.zip and open a command prompt to where you extracted it.
4. Enter the following commands
Code:
adb push su /tmp/
adb push Superuser.apk /tmp/
adb shell
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
cat /tmp/su > /system/bin/su
cat /tmp/superuser.apk > /system/app/Superuser.apk
chown root.root /system/bin/su
chmod 06755 /system/bin/su
chown root.root /system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
reboot
The permissions on /system/bin/su didn't stick the first time for me, and the phone rebooted a couple times, but eventually it all went through. To verify permissions on su, type "adb shell", then "ls -l /system/bin/su". The permission should read -rwsr-sr-x, if it doesn't repeat the shell root process and type
Code:
adb shell
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
chmod 06755 /system/bin/su
ls -l /system/bin/su

Ok, i've figured out what the problem is. As soon as the adb process from SOC is shut down, the phone soft reboots and I lose temporary root. I've tried the psneuter exploit in the same adb command shell, but it hangs just like SOC. I've tried to be "quick" and get the commands in before the reboot, but it isn't possible.
Suggestions on how I may bypass that? Otherwise i'll wait for the official 2.3 update in september and try again then.

One of the phones I tried it on, did the same thing, ended the adb process and phone would reboot, pushed a file, phone would reboot, set permissions, phone would reboot. Occasionally the phone would appear to hang, buttons flash at the bottom for awhile, phone becomes unresponsive. Just wait a minute or 2 and it should return to normal. I also tried creating a script to do all of the above before the device had time to reboot and it didn't help.
Persistence was the key.

Did you try that ? If following the instructions don't work for you, I let you know how it works for me.
EDIT : Sorry, forget link's thread : http://forum.xda-developers.com/showthread.php?p=14458927
Sent from my LG-P970 using xda premium

Hey i am having the same problem and am fearing bricking my phone from making a mistake. is there an easier method than those above mentioned?
Android 2.2.2
software: v10a

Sobralobo said:
Did you try that ? If following the instructions don't work for you, I let you know how it works for me.
EDIT : Sorry, forget link's thread : http://forum.xda-developers.com/showthread.php?p=14458927
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
This method worked when rooting my wife's P970g.

KDZ file
hey does anyone have the Telus firmware KDZ file? i will need it to restore my phone back to original state to cash in on a waranty (ended up bricking it, had to install a german 1&1 firmware to get it back)

s0dhi said:
This method worked when rooting my wife's P970g.
Click to expand...
Click to collapse
...which ROM did you use, the v10a EEU from the thread?
I'm worried cause on Telus 970g as well.

The_non_rootable said:
hey does anyone have the Telus firmware KDZ file? i will need it to restore my phone back to original state to cash in on a waranty (ended up bricking it, had to install a german 1&1 firmware to get it back)
Click to expand...
Click to collapse
http://lg-phone-firmware.com/index.php?id_mod=1

[Q] Recovery not sticking - adb help

Hi guys, I would really appreciate some help. I am able to root my gear and transfer the TWRP via odin. But when I reboot into recovery it just goes back to the stock launcher. I read this in the developer thread:
IF YOU FIND THE RECOVERY IS NOT STICKING & YOUR GEAR WIPES WHEN ATTEMPTING TO ACCESS RECOVERY AFTER FLASHING.
YOU MUST ROOT YOUR GEAR PRIOR TO INSTALLING TWRP AGIAN & RUN THE FOLLOWING COMMANDS IN ADB.
*NOTE* YOU WILL HAVE TO ACCEPT A SUPERUSER REQUEST POPUP WHEN EXECUTING "SU" COMMAND.
*NOTE 2* PROBABLY A GOOD IDEA TO RUN THIS PRIOR TO FIRST INSTALLATION, TO SAVE TIME.
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
IF YOU DELETE THE "RECOVERY-FROM-BOOT.P" FILE YOU MUST RELFASH TWRP RECOVERY.
I have rooted and installed roms on phone before but working in the developer tools is new to me. Can anyone explain exactly how and when to do this during the TWRP recovery install process? Or possibly just point me to a how to or youtube on basic adb commands? I have searched and it looks super complicated. Just need to know how to run these 3 commands.
THANKS!

i have the exact same issue, is there any answer for this??
Wettpassat said:
Hi guys, I would really appreciate some help. I am able to root my gear and transfer the TWRP via odin. But when I reboot into recovery it just goes back to the stock launcher. I read this in the developer thread:
IF YOU FIND THE RECOVERY IS NOT STICKING & YOUR GEAR WIPES WHEN ATTEMPTING TO ACCESS RECOVERY AFTER FLASHING.
YOU MUST ROOT YOUR GEAR PRIOR TO INSTALLING TWRP AGIAN & RUN THE FOLLOWING COMMANDS IN ADB.
*NOTE* YOU WILL HAVE TO ACCEPT A SUPERUSER REQUEST POPUP WHEN EXECUTING "SU" COMMAND.
*NOTE 2* PROBABLY A GOOD IDEA TO RUN THIS PRIOR TO FIRST INSTALLATION, TO SAVE TIME.
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
IF YOU DELETE THE "RECOVERY-FROM-BOOT.P" FILE YOU MUST RELFASH TWRP RECOVERY.
I have rooted and installed roms on phone before but working in the developer tools is new to me. Can anyone explain exactly how and when to do this during the TWRP recovery install process? Or possibly just point me to a how to or youtube on basic adb commands? I have searched and it looks super complicated. Just need to know how to run these 3 commands.
THANKS!
Click to expand...
Click to collapse
i have the exact same issue, is there any answer for this??

Well it's been well over a year since I did that but let's see if I can help..... Before I start I'm hoping you've already enabled adb debugging on the gear and downloaded adb onto your computer. I believe you run the commands after you've run cygnia but before you flash twrp. You run the task from a command prompt from your pc. I'm pretty sure you don't include the $ or #. Before you start try the adb command- adb devices from the command prompt on your pc. That'll let you know if the gear is connected. I remember being a bit intimidated by it all as it was different to any other flash I'd done. In reflection it's very easy, type the line in a command prompt, press enter, wait for the cursor to come up again, type the next line. As for guides..... I can't remember which one I used but there's plenty out there.

[HOW TO] Debrand boot animations without flashing new ROM

** Requires ROOT+Busybox and either Terminal or a capable File Manager
So you don't feel like flashing a new ROM and losing all your data, but your carrier's boot up and shutdown branding is getting on your nerves? Here is what you do, the basic idea is the same as putting on a new boot animation
I'll assume you're using a Terminal and bootsamsung.qmg for the rest of this, the other files follow the same method
Copy stock boot and shutdown animations onto your SD card, I'll call the path to this location %sd%. A copy of the stock files in the attached archive.
Open terminal and become root
Code:
su
You may need to remount your /system partition as writable, if you're connecting via ADB, adb.exe may crash here - that's fine, just re-connect the USB cable and you shouldn't need to repeat this step again
Code:
mount -o remount,rw [COLOR="RoyalBlue"]/system[/COLOR]
Copy bootsamsung.qmg from %sd% to /system/media/,
Code:
busybox cp -f "[COLOR="RoyalBlue"]%sd%[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]" "[COLOR="RoyalBlue"]/system/media/[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Set the permissions of the file to 644,
Code:
chmod [COLOR="red"]644[/COLOR] "[COLOR="RoyalBlue"]/system/media/[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Get rid of the SD card copy if you don't want it anymore,
Code:
rm -f "[COLOR="RoyalBlue"]%sd%[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Clean up any overriding animations, I had this happen for my shutdown animation where my carrier had a shutdown directory in /system/media/video/ which contained another copy of shutdown.qmg, so check for the existence of these and remove them, e.g.
Code:
if [ -f [COLOR="RoyalBlue"]/system/media/video/[/COLOR][B][COLOR="Purple"]bootsamsung[/COLOR]/[COLOR="Green"]bootsamsung.qmg[/COLOR][/B] ]; then
rm -f [COLOR="RoyalBlue"]/system/media/video/[/COLOR][B][COLOR="Purple"]bootsamsung[/COLOR]/[COLOR="Green"]bootsamsung.qmg[/COLOR][/B]
fi
Reboot and see what happens!
Extra notes: Always keep backups of original files. If you can't get past the boot animation, restore the backups.

paulie-uk said:
** Requires ROOT+Busybox and either Terminal or a capable File Manager
So you don't feel like flashing a new ROM and losing all your data, but your carrier's boot up and shutdown branding is getting on your nerves? Here is what you do, the basic idea is the same as putting on a new boot animation
I'll assume you're using a Terminal and bootsamsung.qmg for the rest of this, the other files follow the same method
Copy stock boot and shutdown animations onto your SD card, I'll call the path to this location %sd%. A copy of the stock files in the attached archive.
Open terminal and become root
Code:
su
You may need to remount your /system partition as writable, if you're connecting via ADB, adb.exe may crash here - that's fine, just re-connect the USB cable and you shouldn't need to repeat this step again
Code:
mount -o remount,rw [COLOR="RoyalBlue"]/system[/COLOR]
Copy bootsamsung.qmg from %sd% to /system/media/,
Code:
busybox cp -f "[COLOR="RoyalBlue"]%sd%[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]" "[COLOR="RoyalBlue"]/system/media/[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Set the permissions of the file to 644,
Code:
chmod [COLOR="red"]644[/COLOR] "[COLOR="RoyalBlue"]/system/media/[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Get rid of the SD card copy if you don't want it anymore,
Code:
rm -f "[COLOR="RoyalBlue"]%sd%[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Clean up any overriding animations, I had this happen for my shutdown animation where my carrier had a shutdown directory in /system/media/video/ which contained another copy of shutdown.qmg, so check for the existence of these and remove them, e.g.
Code:
if [ -f [COLOR="RoyalBlue"]/system/media/video/[/COLOR][B][COLOR="Purple"]bootsamsung[/COLOR]/[COLOR="Green"]bootsamsung.qmg[/COLOR][/B] ]; then
rm -f [COLOR="RoyalBlue"]/system/media/video/[/COLOR][B][COLOR="Purple"]bootsamsung[/COLOR]/[COLOR="Green"]bootsamsung.qmg[/COLOR][/B]
fi
Reboot and see what happens!
Extra notes: Always keep backups of original files. If you can't get past the boot animation, restore the backups.
Click to expand...
Click to collapse
Hello, I'm interested in debranding my verizon s5. I'd love to get rid of the Verizon screen at bootup. I read through your directions and it seems that you are suggesting overwriting the animation with the stock that you provided. All good. It is the use of the terminal that I am completely unfamiliar with. I tried using adb.exe in a command window inside of windows 7 and it didn't even like the first command 'su' My phone is rooted with a custom rom and busybox in developer mode. Could you help me out with what terminal to use and how to connect etc. to enter the commands? I have a decent filemanager installed but It doesn't let me write to system. Thanks for this post.

Eaglebiker said:
Hello, I'm interested in debranding my verizon s5. I'd love to get rid of the Verizon screen at bootup.
Click to expand...
Click to collapse
My first comment must be to say I have a G900F, the international version of the phone and it's using a stock ROM with a few tweaks, e.g. root. A custom ROM will have changed the system partition already so this method shouldn't be applicable there - if it shows a carrier logo on a custom ROM then it's in another partition, not system
Eaglebiker said:
I read through your directions and it seems that you are suggesting overwriting the animation with the stock that you provided. All good. It is the use of the terminal that I am completely unfamiliar with.
Click to expand...
Click to collapse
I gave terminal instructions so people could do it only using their phone but as you've noticed, it's not the only option
Eaglebiker said:
I tried using adb.exe in a command window inside of windows 7 and it didn't even like the first command 'su'
Click to expand...
Click to collapse
If you are using adb, make sure that adb can gain root - the flag should be somewhere in your superuser's settings - then with your USB connected launch adb into shell mode from your computer. This makes adb act as a terminal
Code:
adb shell
If you see a $ then you are not root and will need to gain root, i.e. run su
If you see a # then you are root and don't need to do that
Eaglebiker said:
My phone is rooted with a custom rom and busybox in developer mode.
Click to expand...
Click to collapse
All good things!
Eaglebiker said:
Could you help me out with what terminal to use and how to connect etc. to enter the commands?
Click to expand...
Click to collapse
The terminal I use is can be found here (though I used v1.0.65). Most custom ROMs already include it so you may find it in your apps already. It's all on your phone so you'd type on your phone's keyboard as normal. You shouldn't have to use this if you want to use ADB.
Every time I wrote a %path% you will need to enter the real path for what you have on your device, e.g. %sd% may be /extSdCard/
Eaglebiker said:
I have a decent filemanager installed but It doesn't let me write to system.
Click to expand...
Click to collapse
What doesn't let you do this? If it's "read only" then you may need to remount the /system partition (my step 3). File managers like the one you get with CM do let you do root things but it needs to be in root mode or prompt mode (see it's settings). To find /system in a file manager, the easiest way is to keep going up until you're at /, then you should be able to go down through [/B]/system[/B]
Eaglebiker said:
Thanks for this post.
Click to expand...
Click to collapse
Thank you for letting me give some meaningful answers in post 3!

The Rom I'm using would be better described as a stock lollipop rom for the 900v with a few tweaks.
I now understand that you can have a terminal on the s5. I've installed the terminal and greatly prefer it. Using a terminal on the s5 hadn't even occurred to me and it sounds much easier then hooking to a computer needlessly. Awesome.
I manage to get su access #. in step 2.
in step 3 I type in the mount command and nothing seems to happen. no errors
in step 4 it tells me the folder or file doesn't exist. I'm certain it does. I can see it in my file manager. in the folder /extSdCard/bootsamsung.qmg and the destination folder is /system/media as well. I've tried it with and without quotes and no joy. Any clue what is going on?