Have a FTV rooted version 1 with old firmware (51.1.4.0) I updated TWRP to the latest version then used a pre-rooted rom to upgrade to 5.5.2.1.1
I now have some problems with a file (mbcache.db) increasing in size so I would get Memory full delet apps.
I wanted to use TWRP to change rom to a later one. Hoping the problem would go away.
When I booted into TWRP i found that it reverted to old version screen is huge can only see button to install and cant scroll around
So I tried to update TWRP again but when I use adb and just after I run adb shell I try to run su but I get this
/system/bin/sh: us: not found
So
I cant do anything because everything requires the su command
I also checked and my bootloader is locked but wasn't when I did the first rom but now its locked
Any idea whats going on
Rick
Ok I think I got it figured out was able to downgrade to 5.0.5.1
I am having a similar issue with SU permission. My rom is 5.2.1.1, and boot loader unlocked. I was wondering if you can help me out. I am able to access FireTv with Teamviewer Quicksupport and SU grants permission, but when I select remote control however it grants permission, and then quickly denies it. What exactly am I doing wrong?
Does the Xposed framework and Module have to be installed again? If so what version should I use or does that not make a difference with this working? I have busybox updated and working fine, but I can't get my head around this. I had it working before on OS 3, but on OS 5 no luck, I know it works, but something is changing the permissions quickly. If you can please help me with this it would be greatly appreciated.
Don't know if this helps but I found FACTORY RESET kills removes the SU functionality. I just reinstalled my routed rom and SU worked again
Related
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?
Sorry to bother everyone.
In preparation for the 4.04 update, I flashed the stock 4.02 ROM and then was prompted to install the VZW OTA update. This flashed OK. I went ahead via adb and flashed cwm-recovery and then installed the su.zip file via the recovery console.
Once rebooting, I'm able to pop open an adb shell and type su and become the superuser, however none of the apps that require root no longer work -- root explorer, busybox installer, etc.
I'm guessing its a problem with my su file (possibly). Does anyone have any suggestions to troubleshoot? Thanks.
The problem I'm having specifically is gaining root access....fail (within su app).
I had unlocked my bootloader and had switch user unlocked then i changed roms from custom to image version
Acer_ac041_a100_rv16rc02-ww_gen1
build Acer_av041_a100_1.037.00_ww_gen1
kernal version 2.6.39.4+ (i have no idea what kernals do)
i wanted to go back to stock completely and then root so i could remove the bloat but i cannot root for some reason..
when i try to apply busybox it fails..
super user wont update the su binary cause it isnt installed
i ran the terminal but the su file stays at 0.0 kb and later disappears
ive tried several different root techniques none worked.. 1 side note when i run the terminal
sh /mnt/sdcard/root.sh itll run and say making your tab super but it says
/system/xbin/su: no such file or directory... i dont remember it being xbin.. and when i go into busy box its install location is /bin/ with no x.. it has an option for the /xbin/ which ive tried of course.. no cigar.. any help would be much appreciated but please be specific i am not on the same level as some of you guys here, i just recently learned how to cd in command prompt! lolol
kungfaux17 said:
I had unlocked my bootloader and had switch user unlocked then i changed roms from custom to image version
Acer_ac041_a100_rv16rc02-ww_gen1
build Acer_av041_a100_1.037.00_ww_gen1
kernal version 2.6.39.4+ (i have no idea what kernals do)
i wanted to go back to stock completely and then root so i could remove the bloat but i cannot root for some reason..
when i try to apply busybox it fails..
super user wont update the su binary cause it isnt installed
i ran the terminal but the su file stays at 0.0 kb and later disappears
ive tried several different root techniques none worked.. 1 side note when i run the terminal
sh /mnt/sdcard/root.sh itll run and say making your tab super but it says
/system/xbin/su: no such file or directory... i dont remember it being xbin.. and when i go into busy box its install location is /bin/ with no x.. it has an option for the /xbin/ which ive tried of course.. no cigar.. any help would be much appreciated but please be specific i am not on the same level as some of you guys here, i just recently learned how to cd in command prompt! lolol
Click to expand...
Click to collapse
Did you try the new version root script? I know it works with 015 not sure about 037 though.
Su binary in /system/xbin is normal.
Tapatalked from my A100 - Kuroikaze B3
what new version? do you have a link or a name i can persue?
http://forum.xda-developers.com/showthread.php?p=23285307
New and old versions there, try the new version.
Tapatalked from my Galaxy S II.
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
Hi,
I've successfully rooted my FireTV Gen2 and have Kodi installed.
I want to install Xposed but the official version does not support SDK 22 or Arm64.
There is an unofficial version of xposed which works on SDK22 and Arm64 but it is a zip file flashed via recovery.
I am currently on version 5.0.4 and have tried installing CWM but could only find one guide.
I run into an issue immediately when i try chmod the cache folder:
"Unable to open /cache: Is a directory"
No **** it's a directory lol.
I've power cycled several times which hasn't helped. I can't downgrade either because SU isn't working properly.
The device is actually functioning fine and the first time I ran SU in shell the FireTV prompted me to grant.
So can anyone please tell me what the **** is going on?
joncy92 said:
Hi,
I've successfully rooted my FireTV Gen2 and have Kodi installed.
I want to install Xposed but the official version does not support SDK 22 or Arm64.
There is an unofficial version of xposed which works on SDK22 and Arm64 but it is a zip file flashed via recovery.
I am currently on version 5.0.4 and have tried installing CWM but could only find one guide.
I run into an issue immediately when i try chmod the cache folder:
"Unable to open /cache: Is a directory"
No **** it's a directory lol.
I've power cycled several times which hasn't helped. I can't downgrade either because SU isn't working properly.
The device is actually functioning fine and the first time I ran SU in shell the FireTV prompted me to grant.
So can anyone please tell me what the **** is going on?
Click to expand...
Click to collapse
Well there is no CWM for the firetv2... so there's that problem. And there is also nothing to downgrade to...
I am currently working on recovery for the firetv2 and will release it soon.