Database Info

adb root: Permission denied but OK in recovery mode.

Dear Sirs,
I have HTC Desire Z with CM 7.0.3 (superuser installed) and s-off. Posting here since the issue seems relevant to android in general rather than specific hardware...
I have already seen the following threads before opening this one but they do not help since I cannot issue any of the commands that they mention:
:http://forum.xda-developers.com/showthread.php?t=1364521
:http://forum.xda-developers.com/showthread.php?t=1087350
:http://forum.xda-developers.com/showthread.php?t=837102 (it says to use mount command but thats exactly where I get the permission denied)
When I boot the phone normally and "adb shell", I can get a root prompt (id command shows root user, "cd" shows "/"). But ANY command I run brings permission denied (even ls, chmod, mount). I literally can't do anything. Same whether I boot with/without S D card. I CAN however issue commands such as "adb pull /init.rc" if I exit and go back to DOS.
If I open a terminal session (with Superuser full permissions), I can SU as root, but again cannot issue any commands without getting "permission denied"/
However if I boot into clockworkmod recovery and mount /data and /system, and then open an adb shell via USB, I can connect as root and browse everything, everything is fine and all commands work OK. /etc/fstab shows all partitions would be mounted as rw.
So it looks like some application during boot, is resetting the permission for /system to be ro, and also removing root's privileges.
Please could you let us know if there is a method to determine what app is doing this during boot. I cannot see anywhere in init.rc where I can catch this application that is doing this and prevent it from making /system inaccessible after boot.
Preferably if someone could point me to the complete log of the boot process that shows each command that is run, I might have a clue as to where in the boot up process, the /system partition suddenly becomes ro and root loses all permissions.
The problem prevents busybox updating and other root apps that need to write to /system.
This was not a problem for months after installing and rooting CM 703, only recently it has become an issue, perhaps following some hidden Google update???
Thanks

[Q] [OUYA] SuperUser Access Help

Hi everyone, I'm trying to Install busybox,SuperUser and SU Binaries on my OUYA ...
I Have:
-ADB set up and working(wired)
-Downloded and unzipped the needed files
-Placed unzipped files in /android-sdk/platform-tools
Then i run the following commands to make sure my console is connected:
-adb kill-server
-echo 0x2836
-adb start-server
-adb devices
After 'adb devices' I see a number(My console #), which signifies my connected console...
Then i run the following commands to put SU in the proper place:
-adb shell
-su
-mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
-exit
-exit
-adb push su /sdcard/su<-----here is where i get an error (cannot stat 'su': No Such Files Or Directory :crying What am i doing wrong here/ i don't get it!...Can anyone please help me?

cronikman84 said:
Hi everyone, I'm trying to Install busybox,SuperUser and SU Binaries on my OUYA ...
I Have:
-ADB set up and working(wired)
-Downloded and unzipped the needed files
-Placed unzipped files in /android-sdk/platform-tools
Then i run the following commands to make sure my console is connected:
-adb kill-server
-echo 0x2836
-adb start-server
-adb devices
After 'adb devices' I see a number(My console #), which signifies my connected console...
Then i run the following commands to put SU in the proper place:
-adb shell
-su
-mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
-exit
-exit
-adb push su /sdcard/su<-----here is where i get an error (cannot stat 'su': No Such Files Or Directory :crying What am i doing wrong here/ i don't get it!...Can anyone please help me?
Click to expand...
Click to collapse
:good:never mind i figured it out...but when i go to Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update, it gives me an error saying---->there was an error installing superuser. please send a log of the error to the developer. what now?

cronikman84 said:
:good:never mind i figured it out...but when i go to Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update, it gives me an error saying---->there was an error installing superuser. please send a log of the error to the developer. what now?
Click to expand...
Click to collapse
Never mind LMAO...i got it :victory:

cronikman84 said:
Never mind LMAO...i got it :victory:
Click to expand...
Click to collapse
How'd you get it?! I'm stuck here too, thanks!

thanamesjames said:
How'd you get it?! I'm stuck here too, thanks!
Click to expand...
Click to collapse
Are you stuck at the error saying---->"there was an error installing superuser" still? cause if you are i think i can help you..., just on your ouya head over to MANAGE-SYSTEM-ADVANCED and scroll down to apps and delete the BUSYBOX FREE and SUPERUSER APPS...after that's done just repeat the commands again and reboot the system, then go click on MAKE>SOFTWARE>SUPERUSER and allow it to UPDATE but not from recovery and if that doesn't work let me know and ill tell you what to do next...BUT if your stuck at "adb push su /sdcard/su cannot stat 'su': No Such Files Or Directory" error then i can also help you...let me know, it's very simple, less than a minute

cronikman84 said:
Are you stuck at the error saying---->"there was an error installing superuser" still? cause if you are i think i can help you..., just on your ouya head over to MANAGE-SYSTEM-ADVANCED and scroll down to apps and delete the BUSYBOX FREE and SUPERUSER APPS...after that's done just repeat the commands again and reboot the system, then go click on MAKE>SOFTWARE>SUPERUSER and allow it to UPDATE but not from recovery and if that doesn't work let me know and ill tell you what to do next...BUT if your stuck at "adb push su /sdcard/su cannot stat 'su': No Such Files Or Directory" error then i can also help you...let me know, it's very simple, less than a minute
Click to expand...
Click to collapse
Hi,
I'm at the point where I've installed 'superuser' apk via adb. I've rebooted the console, gone to MAKE>SOFTWARE>SUPERUSER but when I click on 'install', I just get the error message: "There was an error installing Superuser. Please send a log to the error to the developer" but there are no logs.
Any ideas?

diazamet said:
Hi,
I'm at the point where I've installed 'superuser' apk via adb. I've rebooted the console, gone to MAKE>SOFTWARE>SUPERUSER but when I click on 'install', I just get the error message: "There was an error installing Superuser. Please send a log to the error to the developer" but there are no logs.
Any ideas?
Click to expand...
Click to collapse
yes, the best way to do it is with this tool OUYA toolbox and you can find it over here-----> http://forum.xda-developers.com/showthread.php?t=2350900 follow the instructions plug in your OUYA to your pc and download the test version of the tool, open it, click on install superuser and install it, then istall busybox and install it...then go to make- software-superuser and Update but not from recovery, then plug you OUYA back on to the pc and run the ouya toolbox program again and root(if you want to), you will be all set with SuperUser apk and busybox apk and root working perfect with no errors...

cronikman84 said:
yes, the best way to do it is with this tool OUYA toolbox and you can find it over here-----> http://forum.xda-developers.com/showthread.php?t=2350900 follow the instructions plug in your OUYA to your pc and download the test version of the tool, open it, click on install superuser and install it, then istall busybox and install it...then go to make- software-superuser and Update but not from recovery, then plug you OUYA back on to the pc and run the ouya toolbox program again and root(if you want to), you will be all set with SuperUser apk and busybox apk and root working perfect with no errors...
Click to expand...
Click to collapse
I think I might have found the issue. I think I forgot to copy the 'su' executable from /sdcard to /system/xbin. I've copied the correct 'su' executable to /system/xbin now. I'll have to test it later, I'm connected remotely at the moment so I can only do the shell stuff, I can't run Superuser.
What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?

diazamet said:
I think I might have found the issue. I think I forgot to copy the 'su' executable from /sdcard to /system/xbin. I've copied the correct 'su' executable to /system/xbin now. I'll have to test it later, I'm connected remotely at the moment so I can only do the shell stuff, I can't run Superuser.
What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?
Click to expand...
Click to collapse
:good: i hope you found the issue...i was having the same issue as you "There was an error installing Superuser. Please send a log to the error to the developer" and no matter what i tried it wouldn't work, so i just downloaded the OUYA toolbox test version and it took me less then 1 minutes to have superuser apk and busybox apk running and rooted, i didn't know you were connected remotely, i had mines connected straight up with the usb cable and it makes it easier for me..."What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?" <----yes, i'm 90% sure that the native SU is crippled in some type of way, and i've heard other people confirm this.

cronikman84 said:
:good: i hope you found the issue...i was having the same issue as you "There was an error installing Superuser. Please send a log to the error to the developer" and no matter what i tried it wouldn't work, so i just downloaded the OUYA toolbox test version and it took me less then 1 minutes to have superuser apk and busybox apk running and rooted, i didn't know you were connected remotely, i had mines connected straight up with the usb cable and it makes it easier for me..."What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?" <----yes, i'm 90% sure that the native SU is crippled in some type of way, and i've heard other people confirm this.
Click to expand...
Click to collapse
Yep. That was the problem. I guess I thought I'd copied the correct version of 'su' across without checking properly.

diazamet said:
Yep. That was the problem. I guess I thought I'd copied the correct version of 'su' across without checking properly.
Click to expand...
Click to collapse
Sweet!!...glad you got it fixed... I knew that the native SU was crippled the first time i tried it...that's why i tried the OUYA toolbox cause i knew people had success with SU on that toolbox, so i gave it a try and SU was workin...tha's how i knew something was wrong with the native SU...

[ROOT] $99 Walmart Nextbook 8 (NX008HD8G)

The Nextbook 8 (NX008HD8G) is a $99 tablet available from Walmart. It sports a AMLogic AML8726-MX SoC (1.5Ghz dualcore Cortex-A9 w/400mhz dualcore Malli400 GPU), 1 Gb of DDR3 RAM, 8" display, and 8Gb internal storage. Its a nice little budget tablet for those who don't need a Nexus 7 or greater performance rated tablet. Not too long ago I discovered how to root it and apparently I'm the first to do it as far as I can tell. Now here's how.
What you will need is Bin4ary's One Touch Root App. This app will get you only partial root via the ADB Shell. My guess is the ADB exploit he uses does work to get basic root access for ADB, but some incompatibility prevents proper installation of su & SuperUser.apk. What we're going to do is finish the job manually.
First run Bin4ary's app and use the Normal Method. Be sure to ignore all errors. After your tablet reboots move su and Superuser.apk from Bin4ry's app folder to the root of the Internal SDCard. Next you will need ADB. If you don't have it you can get it either from Bin4ary's app folder you found su & superuser.apk in or you can install the Android SDK. At the command prompt enter the following:
Code:
adb shell
su
At this point you should see a # sign indicating root privileges. If you do enter the following commands.
Code:
mv /system/xbin/su /system/xbin/osu
cp /sdcard/su /system/xbin
chmod 6755 /system/xbin/su
The use Astro or your favorite file manager to navigate to /sdcard and install SuperUser.apk then reboot your tablet. From here on you should have full root on your tablet. Credit should definitely goto Bin4ry for his work on his One Touch Root App for getting us half way there.

Confirmed Working
Confirmed. Works as described.
Nice work!

Thank you for this information, works excellent.

Ron Overdrive said:
The Nextbook 8 (NX008HD8G) is a $99 tablet available from Walmart. It sports a AMLogic AML8726-MX SoC (1.5Ghz dualcore Cortex-A9 w/400mhz dualcore Malli400 GPU), 1 Gb of DDR3 RAM, 8" display, and 8Gb internal storage. Its a nice little budget tablet for those who don't need a Nexus 7 or greater performance rated tablet. Not too long ago I discovered how to root it and apparently I'm the first to do it as far as I can tell. Now here's how.
What you will need is Bin4ary's One Touch Root App. This app will get you only partial root via the ADB Shell. My guess is the ADB exploit he uses does work to get basic root access for ADB, but some incompatibility prevents proper installation of su & SuperUser.apk. What we're going to do is finish the job manually.
First run Bin4ary's app and use the Normal Method. Be sure to ignore all errors. After your tablet reboots move su and Superuser.apk from Bin4ry's app folder to the root of the Internal SDCard. Next you will need ADB. If you don't have it you can get it either from Bin4ary's app folder you found su & superuser.apk in or you can install the Android SDK. At the command prompt enter the following:
Code:
adb shell
su
At this point you should see a # sign indicating root privileges. If you do enter the following commands.
Code:
mv /system/xbin/su /system/xbin/osu
cp /sdcard/su /system/xbin
chmod 6755 /system/xbin/su
The use Astro or your favorite file manager to navigate to /sdcard and install SuperUser.apk then reboot your tablet. From here on you should have full root on your tablet. Credit should definitely goto Bin4ry for his work on his One Touch Root App for getting us half way there.
Click to expand...
Click to collapse
Did NOT work for me.
1-On first attempt, got pound sign....tried to push code resulting in cant find SD
2-On second attempts, would not let me be superuser su
3-Did a factory reset....same results as (2)
Im stomped!....please help

Amlogic Next8HD8G (NX008HD8G) Modified Recovery - Stock Rom - Root & Gapps
Modified recovery, stock rom, flashable root and flashable Gapps here: http://www.freaktab.com/showthread.php?7010-Amlogic-Next8HD8G-%28NX008HD8G%29-Modified-Recovery-Stock-Rom-amp-Flashable-Root
ShaunMT

Confirmed as well..
Ty... no fusses at all..

zenkillizen said:
Ty... no fusses at all..
Click to expand...
Click to collapse
I need someone to be more clear on rooting this device because I already bricked one using the method from tab freaks instructions aren't that clear and I don't want to brick another one ! Please thanks

andrew09 said:
I need someone to be more clear on rooting this device because I already bricked one using the method from tab freaks instructions aren't that clear and I don't want to brick another one ! Please thanks
Click to expand...
Click to collapse
this guide is like the clearest root guide I've seen Just sit down and read it, take your time Rooting my seem hard at first, but you catch on

Aiko0923 said:
this guide is like the clearest root guide I've seen Just sit down and read it, take your time Rooting my seem hard at first, but you catch on
Click to expand...
Click to collapse
Parts are missing from the guide like how to install the adb drivers the computer needs to recognise the tablet first before u try and root it I have read through it and I've already bricked one also I noticed if you go to recovery on this tablet it erases the system and factory reset doesn't fix anything there's no factory ROMs or anything to fix it if it messes up. If someone can't a sure me that the method is correct I'll do it I'll try it.

Does this method work on the newer models say model number starting with YFG12 and up?

I bought this today.
I am having problems here:
I did what you said to do:
Normal Mode enabled!
Pushing busybox....
4806 KB/s (1165484 bytes in 0.236s)
Pushing su binary ....
7134 KB/s (104576 bytes in 0.014s)
Pushing Superuser app
6792 KB/s (2139595 bytes in 0.307s)
Making busybox runable ...
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful I will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
RunMe.sh: line 222: wait: pid 10 is not a child of this shell
Waiting for device to show up again....
RunMe.sh: line 225: wait: pid 10 is not a child of this shell
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
---
And then I copied the files su and the .apk to /sdcard
Then I try to run su, and it says:
su
/system/bin/sh: su: not found
so I do
[email protected]:/sdcard $ ./su
/system/bin/sh: ./su: can't execute: Permission denied
---
Other times, it just does this:
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful I will tell you, if not this shell will run forever.
Running ...
and it runs forever
what do I do?

http://www.cydiaimpactor.com/
Worked for me.

YES! use cydia impactor
H0wdy said:
http://www.cydiaimpactor.com/
Worked for me.
Click to expand...
Click to collapse
Yes, I used it also. worked for me too (my serial for the tablet is YF07... in case there is a problem with the newer versions)
Thanks, H0wdy
Steps to do it:
Download Cydia Impactor
Turn on USB debug in settings-> Developer options
Plug in tablet into PC (I used a 32 bit Windows 8.1)
Wait a while... a long while for me... for windows to download drivers, disconnect tablet, wait a few seconds, then reconnect.
you should see in the device manager (on the top) android phone and underneath Android Composite ADB interface
Unzip Cydia, run impactor.exe and just choose start for # drop SuperSU su to /system/xbin/su
Wait a bit, then you're done. (no reboot or anything else necessary).
Install supersu (or I guess any other superuser app) from the android market. It will tell you that you can update the su binary... your choice, I updated without a problem.
I had supersu installed beforehand, but I guess it has nothing to do with it, it wasn't working anyway)
Ranting, but maybe someone has this issue also:
One ( -- BIG --) problem I had was getting the connection between the tablet and my computer, and Not because I can't plug-in a cable
the tablet said it was connected, but on the computer, nothing showed up in device manager and the list of devices kept refreshing.
The PC was beep-ing just like it found a device. the device list would refresh once or twice, then again beep, all this till the end of my patience.
At first I thought it was the USB 3.0 port, then the cable, then the ESXi USB redirection (my desktop is actually a VM), then the windows version, then the architecture,
Then I switched to a laptop, nothing.. same story.
I can BET it's Sony's F***ed up drivers
So, I used a clean system (no other adb or phone drivers installed) and worked as a charm
I think I hat this much trouble because I had a lot of other drivers (for sony, samsung, universal adb, etc etc.)
So on the computer I had all this stuff installed, it looked like the tablet was connected, then disconnected in the space of 10-15 seconds, then repeat forever.
If this happens to you, use a clean windows.

Can"t access sdcard after root permission.

Hi guys ! i was trying to run a script on my micromax unite 2 by terminal emulator but it always gives a error "permission denied" . so, i searched on google there i found that it requires root access.
So, i rooted my phone and type "su" at the starting to gain supersu access. But after getting root access i cant get access to my sdcard through terminal emulator. it always give me error "no such file or directory". please help me with a solution.
Thanks in Advance and sorry for my english .

rathors1998 said:
Hi guys ! i was trying to run a script on my micromax unite 2 by terminal emulator but it always gives a error "permission denied" . so, i searched on google there i found that it requires root access.
So, i rooted my phone and type "su" at the starting to gain supersu access. But after getting root access i cant get access to my sdcard through terminal emulator. it always give me error "no such file or directory". please help me with a solution.
Thanks in Advance and sorry for my english .
Click to expand...
Click to collapse
Are you sure you're entering the correct directory for the sdcard into the shell (terminal with a #)?

yes I typed right path and even checked it 3-4 times.
you can see it in the screenshot. I'm trying to run complete linux installer script to install ubuntu on my phone. my phone supports loop devices.

Root access on adb shell but not for apps

Hello,
i am working on chinese android tablet called "MID-U705B". The device came half rooted i guess. I am getting an # in the adb shell, even without running "su", right from the start of adb shell. Nevertheless i am not able to run any root apps. When i am trying to call a root shell command from my app i am getting: [java.io.IOException] : write failed: EPIPE (Broken pipe).
There is a su file inside my /system/xbin folder and i also created a symbolic link to it in /system/bin.
Does someone know how to get full root access on this devices? Whats missing?
Thanks for your help and advice!
Best regards,
Hans

skatehans said:
Hello,
i am working on chinese android tablet called "MID-U705B". The device came half rooted i guess. I am getting an # in the adb shell, even without running "su", right from the start of adb shell. Nevertheless i am not able to run any root apps. When i am trying to call a root shell command from my app i am getting: [java.io.IOException] : write failed: EPIPE (Broken pipe).
There is a su file inside my /system/xbin folder and i also created a symbolic link to it in /system/bin.
Does someone know how to get full root access on this devices? Whats missing?
Thanks for your help and advice!
Best regards,
Hans
Click to expand...
Click to collapse
If you can get root on ADB then just install SuperSU app and its binaries and you are good to go.
Flashing the attached ZIP will install SuperSU app and everything it requires to function.
NOTE: You probably need a custom recovery because the zip isn't signed.

Thanks for your reply!
Unfortunately i dont have a custom recovery because its a no name device an there does not exist a custom recovery for this device. Is there any way to install this without a custom recovery? What happens when i try to flash it from a (chinese) stock-recovery?

skatehans said:
Thanks for your reply!
Unfortunately i dont have a custom recovery because its a no name device an there does not exist a custom recovery for this device. Is there any way to install this without a custom recovery? What happens when i try to flash it from a (chinese) stock-recovery?
Click to expand...
Click to collapse
You should be able to flash it via fastboot.

Thats the next Problem. I cant boot into fastboot mode. When i execute "adb reboot bootloader" or "adb reboot download" the device boots up like normal, so i guess fastboot is not available on this device.
Do you know any other way?