Develop Bugs

[Q] Rooting the Creative Zio

Hi there!
I'm trying to root Ziio 7 unit I got for a review for PurePC.pl, and so far so good I installed SuperUser app and su and busybox binaries. Now using terminal I can su without any problems. But the thing is, SU only seems to be working in terminal emulator. I've tried using some apps that should use root like ShootMe and ScreenshotIt, SetCPU and they just doesn't work.
ShootMe says "Starting Server failed", plus info that i need to have root access and enabled access to lower graphics (whatever it is).
ScreenshotIt just doesn't work without any information why, and SetCPU FC's after selecting profile. Although it gets me a nice SuperUser dialog, but that's as far as it goes, cause it crashes right after that.
Am I missing something to have a complete root? Interesting thing is that on this device, preferred PATH for executable binaries is /data/busybox/, and not a usual /system/bin. Interestingly, my su binaries refused to work from /data/busybox directory, so I moved them to /system/bin. Rest of the utilities and such are still in /data/busybox, but I don't know if this information is important in any way Have I missed something along the way? Please help. Cheers.

OK, I know why su gave me permission denied when running from /data/busybox. The /data partition was mounted with nosuid. But still the applications such as ShootMe won't work.

I waiting for. If who has a good new. Please tell me to private message.

Have you made any progress on this bagienny?

[Q] unrevoked worked but phone still not rooted?

It took me 4 hours to get unrevoked root my phone (turned out that the actual version is buggy) but somehow it seems not "really" rooted.
I want to install titanium backup, so when I start it I get this popup to grant root access but titanium still says it is not ok.
I can do a "su" in the shell but not a whoami. - I don't understand why.
If I go into the recovery menu it says ClockworkMod Recovery v.3.0.0.5
Bravo PVT1 SHIP S-ON
HBOOT 0.93.0001
Microp-031d
Radio-5.10.05.23

If you bothered to check the Titanium website you'd see you need to click the 'Problems' box to install BusyBox. Without this TB won't work
http://matrixrewriter.com/wiki/tiki-index.php?page=TB+-+User's+guide

EddyOS said:
If you bothered to check the Titanium website you'd see you need to click the 'Problems' box to install BusyBox. Without this TB won't work
http://matrixrewriter.com/wiki/tiki-index.php?page=TB+-+User's+guide
Click to expand...
Click to collapse
It even says on first Titanium Backup launch!

Yep...pops up a message. Click "Problems?" at the bottom for a reliable busybox.

Believe me I bothered a lot to look around and I tried for hours and hours.
Titanium complained about not having root privileges not about busybox. And in the help on their homepage there was this guide "how to check if your phone is rooted properly" by issuing the su command followed by whoami which is obviously misleading.
However, thank you for pointing me in the right direction. It seems to work now.

OK. Now I am convinced - this was completely not my fault. Not only is the documentation missleading, the software is buggy as well.
Going to the Problems? Menu suggests it would fix your issues with busybox by installing it and such...
Well, it does download it to your device but it is not usable until you install it manually via the android sdk in recovery mode. Until then you will not get an app listing. I wonder where to find this little detail in the docu (talking about laziness)

No one else seems to have this issue so not sure what you're doing differently
I just went to running a custom ROM so once rooted didn't have any issues

When you flash your phone with unrEVOked, try using Clockwork 2.5.0.7 as I used this version and it worked 1st time.

SOLVED
Thanks guys. I already solved all problems. It was horribly difficult to get over all these pit falls but finally I reached my goal (a Titanium Backup).
What caused me most trouble was the unclear description of Titanium Backup, especially the part in which they state "if whoami does not respond so and so you are not root"... BULL****!!!
"Short" list of how I got my Desire with HBOOT 0.98 rooted and installed Titanium Backup:
Unrevoked root, but not the latest version 3.32. This one will stop with an Error: Cannot get root. Is your firmware too new? or something similar. Instead use version 3.2
Install Titanium and start it. Superuser will popup and ask for permissions - grant.
Make the changes in the application settings that Titanium asks for (I think usb debugging and allow applications that are not from market) and forget about the message telling you you have no sufficient root privileges, that is not true - I guess what they really mean is that busybox is not installed on your system (would be nice if they'd said what they mean).
Go to the "Problems?" button and let Titanium install Busybox.
... not over yet!
Titanium will now not complain about root privileges any longer but you will still not see any application listings in the software. So maybe there is still something wrong. But what could that be? The root priviliges? WRONG!. Titanium downloaded busybox but did not bother to also install it, although it said it did ;-)
Get the android SDK from Google and install it. (you will also need the Java JDK). You can uncheck most of the packages during installation, probably all. We are only interested in the adb tool that is included in the base installation (I think it is, I also installed the Android SDK Platform tools, SDK Tools and SDK Platform Android 2.2 - just because I was not sure about it).
Boot phone into recovery and connect with the adb shell. (this is a little tool that you will find in the tools subdirectory in the android sdk. You need to start it from the command prompt)
Once connected you need to install busybox manually. Titanium did download the data but did not install! How to do this is described by Loccy here:
Code:
Actually, what I did was use Titanium's busybox:
* install Titanium
* run Titanium
* click the "problems" button and install Busybox
* boot into recovery
* adb shell from my Mac
* mount /system
* cp /data/data/com.keramidas.TitaniumBackup/files/busybox /system/bin
* cd /system/bin
* ./busybox --install -s .
Instead of using the mount commands, listed above I mounted the mentioned directories with the mount option in the ClockworkMod recovery menu, that comes with the unrevoked rooting, because the mount commands did not work properly for me. Also, I had to cd into the /data/data/com.keramidas.TitaniumBackup/files/busybox directory and copy busybox to /system/bin/. from there.
Code:
cd /data/data/com.keramidas.TitaniumBackup/files
cp busybox /system/bin/.
cd /system/bin
./busybox --install -s .
But I might have had a typo.
reboot the device and enjoy.
I should mention, if you NOW issue the suggested "su" and "whoami" commands in a shell that according to Titaniums super HOWTO should tell you if you have root privileges, THEN you will get the right response.
In Conclusion:
Forget about the Titanium howto. If Unrevoked finished with no error you HAVE root privileges, no matter what Titanium tells you. Another indicator: If the superuser popup appears, you should be rooted as well.
Install Busybox either completely manually or with the above described method via Titanium. The busybox setup has worked if you can issue the "su" and "whoami" command in a shell.
@EddyOS: "Noone" might not be entirely true - If Titanium was so clear you would not find tons of "how do I install it" questions in the forum. If it works on some *or most* devices but on others not, this is just an indication for sloppy coding. And a user should not have to spend hours over hours to surf some forums for solutions that should have been provided by the developers in the first place. Some people have a life...

[Q] Nexus 4 - SU not working anymore but binary present

Hi all,
I come with what is probably a silly question after I did not manage to stumble upon someone with the exact same situation while doing some googling around.
I have a Nexus 4, running the older Android 4.2.2 (did not update as I have some custom patches in there).
My phone has also been rooted for quite a while and working perfectly until recently something broke it (did not manage to find out when I broke it).
I have CWM installed and that is working fine.
I have SuperSu installed, now the latest version.
If I boot my phone into Recovery Mode and then I access it with the shell commands:
a) I mount the sdcard partition
b) I run
$ ./adb shell
~ # /system/xbin/su -
[email protected]:/ #
All works fine.
If I boot my phone normally and I run SuperSU, then I get: "no su binary installed" and the app kicks me out.
If I connect with ADB to it .. then I see that the binary is indeed in /system/xbin/su but trying to run it just doesn't do anything.
The process "freezes" and I don't get a command prompt anymore.
I can cancel it with CTRL+C and try to run it again but still ...nothing happens
This is one point where I am missing the Linux strace which I did not think of having here but would have enabled me to at least see what the SU binary is doing when it is not returning control to the command prompt or at least giving an error
Any idea what might be happening ?
Also..why is "su" working fine when called from the bootloader/CWM and why freezing when calling from the normal running system (aside from that funky error that no su binary is installed).
I tried so far flashing also an older version of SuperSU...same result, then went back to v1.94
Sorry if my problem is stupid but I don't seem to get my way around it...

I solved the first part by myself
Seems Xprivacy suddenly lost my preferences and was not allowing the running of su...
Now from the Terminal App on my Android, I can do: /system/xbin/su - and I get root.
But both SuperSU and SuperUser report that there's no SU binary....
Are they searching for it in some other path ?
I don't get it...
How can the binary not exist but if I run it by hand from the terminal app, everything works perfectly and I get to be root.
skyraven83 said:
Hi all,
I come with what is probably a silly question after I did not manage to stumble upon someone with the exact same situation while doing some googling around.
I have a Nexus 4, running the older Android 4.2.2 (did not update as I have some custom patches in there).
My phone has also been rooted for quite a while and working perfectly until recently something broke it (did not manage to find out when I broke it).
I have CWM installed and that is working fine.
I have SuperSu installed, now the latest version.
If I boot my phone into Recovery Mode and then I access it with the shell commands:
a) I mount the sdcard partition
b) I run
$ ./adb shell
~ # /system/xbin/su -
[email protected]:/ #
All works fine.
If I boot my phone normally and I run SuperSU, then I get: "no su binary installed" and the app kicks me out.
If I connect with ADB to it .. then I see that the binary is indeed in /system/xbin/su but trying to run it just doesn't do anything.
The process "freezes" and I don't get a command prompt anymore.
I can cancel it with CTRL+C and try to run it again but still ...nothing happens
This is one point where I am missing the Linux strace which I did not think of having here but would have enabled me to at least see what the SU binary is doing when it is not returning control to the command prompt or at least giving an error
Any idea what might be happening ?
Also..why is "su" working fine when called from the bootloader/CWM and why freezing when calling from the normal running system (aside from that funky error that no su binary is installed).
I tried so far flashing also an older version of SuperSU...same result, then went back to v1.94
Sorry if my problem is stupid but I don't seem to get my way around it...
Click to expand...
Click to collapse

it seems in the end that it was all in xprivacy problem....
solved and now it is functional
skyraven83 said:
I solved the first part by myself
Seems Xprivacy suddenly lost my preferences and was not allowing the running of su...
Now from the Terminal App on my Android, I can do: /system/xbin/su - and I get root.
But both SuperSU and SuperUser report that there's no SU binary....
Are they searching for it in some other path ?
I don't get it...
How can the binary not exist but if I run it by hand from the terminal app, everything works perfectly and I get to be root.
Click to expand...
Click to collapse

Just so you know
The reason you probably did not get responses to this is because you posted it in Galaxy Nexus section and not Nexus 4 forums

need help system is read only

Hi,
im trying to install twrp and having a tough time trying to find a solution to my problem, ive rooted using zeroepochs guide, when i run the command to extract and install the recovery.zip i get a read only error as below
[email protected]:/ $ sh /sdcard/firetv2_recovery_v5.zip
Extracting unzip...
Remounting /system read-write...
mount: Invalid argument
Extracting...
checkdir: cannot create extraction directory: /system/recovery
Read-only file system
ln: /system/bin/ext4_resize: Read-only file system
Remounting /system read-only...
any help is appreciated.

You need to go into root admin.
Use the command "Su" to get into root shell

Hi, thanks I've tried that and get the same issues?

skirocket said:
Hi, thanks I've tried that and get the same issues?
Click to expand...
Click to collapse
After su command was sent through ADB, have you granted access on the pop up screen that appears at first use?
- Reset (unplug and plug back in) unit
- let it boot into main menue
- connect through ABD
- at adb shell prompt type su
- enter
- A pop up screen should appear on your TV asking you to grant access for su
- using your FireTV remote select yes and press OK.
- see if issue is solved

bula1ca said:
After su command was sent through ADB, have you granted access on the pop up screen that appears at first use?
- Reset (unplug and plug back in) unit
- let it boot into main menue
- connect through ABD
- at adb shell prompt type su
- enter
- A pop up screen should appear on your TV asking you to grant access for su
- using your FireTV remote select yes and press OK.
- see if issue is solved
Click to expand...
Click to collapse
hi thanks for the reply, i have done that and it says that i have been granted SU but i get this message
[email protected]:/ # sh /sdcard/firetv2_recovery_v5.zip
Extracting unzip...
Remounting /system read-write...
mount: Invalid argument
Extracting...
checkdir: cannot create extraction directory: /system/recovery
Read-only file system
ln: /system/bin/ext4_resize: Read-only file system
Remounting /system read-only...

Sorry to pick this up again. But i have the same Issue. How have you installed TWRP?
Thanks

I used King root, then installed a custom rom, had too many problems trying to install twrp previously.

skirocket said:
I used King root, then installed a custom rom, had too many problems trying to install twrp previously.
Click to expand...
Click to collapse
Thank you
so you used this guide http://www.aftvnews.com/how-to-root...covery-and-a-pre-rooted-rom-all-without-a-pc/ with your rooted Fire Tv2?

i used this guide http://www.aftvnews.com/how-to-root-the-fire-tv-2-using-kingroot-no-usb-cable-required/. but at the time if i remember i updated my box to stock update 5.0.5 from 5.0.4 then rooted again.

Hi, the trick is to use this Guide http://www.aftvnews.com/how-to-root-the-amazon-fire-tv-2/
Worked perfectly

I know this is an old thread but I'll post what worked for me just in case...
On ADBLink, select Root → Mount /system RW. This will make /system writable.
Not sure if this is necessary, but I switch back to RO (read only) once I was done with my changes.

There's a SU binary on my phone but i didn't root it

Hello Forum,
Sorry if this post isn't in the right place; i'm not very good at posting on forums.
My question: does a stock phone already have a SU binary installed?
My situation specifically:
Sony Xperia XZ2 Compact (H8324)
It seems there's a SU binary in /sbin
Trying to execute it results in Error: java.io.IOException: Cannot run program "su": error=13, Permission denied
It seems there's also a busybox installed but I can't get any details about it
I checked my phone with Root Checker Pro by Joey Krim because an app (CoronaCheck) by the Dutch government used to identify yourself and state your corona status (for entry to concerts, festivals, restaurants etc) gave me a warning that my details were not safe because my phone was rooted.
I did not root my phone. I bought it as a brand new phone that was stock in every way.
Does a stock rom have a su binary and busybox installed?
Any help would be welcome! Thanks.

bombastique said:
Hello Forum,
Sorry if this post isn't in the right place; i'm not very good at posting on forums.
My question: does a stock phone already have a SU binary installed?
My situation specifically:
Sony Xperia XZ2 Compact (H8324)
It seems there's a SU binary in /sbin
Trying to execute it results in Error: java.io.IOException: Cannot run program "su": error=13, Permission denied
It seems there's also a busybox installed but I can't get any details about it
I checked my phone with Root Checker Pro by Joey Krim because an app (CoronaCheck) by the Dutch government used to identify yourself and state your corona status (for entry to concerts, festivals, restaurants etc) gave me a warning that my details were not safe because my phone was rooted.
I did not root my phone. I bought it as a brand new phone that was stock in every way.
Does a stock rom have a su binary and busybox installed?
Any help would be welcome! Thanks.
Click to expand...
Click to collapse
Since i believe, on all stock android firmware, since android 6 ( Marshmallow ) it comes with Toybox installed.
Toybox is similar Busybox. Except for the latest version ( i believe ) of toybox these versions don't have ' root ' like functionality, which is why ' su ' command will fail. This is why you will see the commands in directories like /bin etc.
As for apps, the detection methods have changed to more then looking for ' just if your phone is rooted ( SU Binaries )' or not. ie: unlocked bootloader etc, and maybe playstore certification/safetynet. Blame Google for that.
Toybox - Wikipedia
en.wikipedia.org