Related
my device is rooted and I want to backup all my apps before flashing a new ROM
but titanium backup wont start saying that im not rooted although I am and it stated that I need busybox installed. But when installing busybox it says failed to copy over /system/xbin and my device suddenly reboot. please help
will thank every useful post
Please help
From recovery:
mount /system
mount /sdcard
cp /sdcard/busybox /system/xbin/busybox
chmod 755 /system/xbin/busybox
cd /system/xbin
./busybox --install
TouchPal-d from my Desire running Starburst Classic Rom - 450 apps and counting. .
Obviously you have to put a good busybox binary within /sdcard/
Sibere's Data2sd thread had one attached
TouchPal-d from my Desire running Starburst Classic Rom - 450 apps and counting. .
Droidzone said:
From recovery:
mount /system
mount /sdcard
cp /sdcard/busybox /system/xbin/busybox
chmod 755 /system/xbin/busybox
cd /system/xbin
./busybox --install
TouchPal-d from my Desire running Starburst Classic Rom - 450 apps and counting. .
Click to expand...
Click to collapse
I'm sorry but I don't understand what ur trying to say
im really a new to the desire. I dont understand what cp, chmod 755, cd is
Droidzone said:
Obviously you have to put a good busybox binary within /sdcard/
Sibere's Data2sd thread had one attached
TouchPal-d from my Desire running Starburst Classic Rom - 450 apps and counting. .
Click to expand...
Click to collapse
it's busybox.zip attached to this thread rite? http://forum.xda-developers.com/showthread.php?t=852219. If so Ive downloaded.
and I can't do nandroid backup please help me.
thanks for the respond btw I really appreciate it
You're a newbie...why didnt you say so at first?
Never mind, just flash this..
Well, did it work?
TouchPal-d from my Desire running Starburst Classic Rom - 450 apps and counting. .
Droidzone said:
You're a newbie...why didnt you say so at first?
Never mind, just flash this..
Click to expand...
Click to collapse
thank you so much! I'll try and report back later cos the phone is not currently in my hand
thank you!!
Droidzone said:
Well, did it work?
TouchPal-d from my Desire running Starburst Classic Rom - 450 apps and counting. .
Click to expand...
Click to collapse
Umm... Sorry for the long reply n not being really active. I flashed succesfully but after i go to busybox installer it says that i dont have busybox installed. I think i may have done something wrong with rooting....
When i go to the recovery it says:
E: cant find misc
E: cant mount cache: recovery/ command
E: cant find misc
E: cant mount cache: recovery/ log
E: cant find misc
And when i want to do a nand backup it says
Error while dumping boot image!
E: cant mount cache: recovery/ log
E: cant find misc
What did i do wrong?
Troble Installing Could Do With Some Help Thanks .
* NEED HELP INSTALLING BUSYBOX *
I have joined this form as i have finally came to my wits with trying to get Busybox installed but i am getting nowhere with it. I found and old HTC desire 620 phone lying around and i thought i would use it as a project phone its running on Android Kitkat 4.4.4 i unblocked it first for any sim and its network is BT it use to be with O2 then i paid One Click Root to Root my phone (PROBS A STUPID THING TO DO AS THERE IS LOADS OF WAYS TO DO IT BUT I JUST WANTED IT DONE THERE AND THEN ) and i dont no much about the android system but would like to get familiar with it tho at somepoint. Once the phone was rooted my boot menu is with TWRP But i think i can change that to Clockwork or would it matter what one i have.
I have watched lots of vids and read a good few forms aswell but still cant get this app to install. If i download anymore apps to try helping me install this app i wont have any more room at all and this is the part is where you are probs going to see how stupid i am with android below are a list of apps i have downloaded to try help me :-
I paid for SuperSu Pro, Paid for Busybox Pro, ROM Installer, ROM Toolbox Lite, ROM Manager, Busybox on Rails, ES File Explorer, Mount /system RO/RW App, ASTRO, Hack App Data, SU Update Fixer, SU Root Tools, Total Commander, Terminal Emulator and i even downloaded Titanium Backup as someone said it could help with the install of Busybox but hasnt got me anywhere. I also have dsploit and Lucky Patcher both apps that i would like to work but both require Busybox to be installed.
Now i have downloaded a few Busybox apks and even the free vrsion from the app store Stephen (stericson) version and nothing happend then i paid to get the full version thinking it should work straight away as i have now paid for it but still wont install. This is my situation when i open up the app i am on the install page i select the box in the top right hand corner (Auto Update Busybox), the version is Busybox 1.26.2 and the install path to /system/xbin and when i hit the install button the message i get back says :- ( It looks like the installation of Busybox was not successful, try installing to a differant location, that may resolve the issue) the i hit the red X button and the app cuts of back to the home page. When i reopen the app i change the path to /system/bin the i get the same message and a split 2 seconds l8r my phone just cuts of then reboots only happens everytime i press the install button and the location selected is /system/bin. When i even tryed the other to paths :- /su/xbin and /su/bin at the bottom of my screen a quick message flashes up saying :- (Systemless root is not configured, please choose another install location)
I do apologize for this very long message but it would be appreciated if there is anything someone could do for me or point me in the right direction as every where else i have looked it has been unsuccessfull or its been far to confussing to even understand. I guess there would be most of use saying if i dont no what i am doing i shouldnt be playing around i do no that i could brick the phone or end up in a constant bootloop but as i said i found a spare phone that was still working and though i would give it a go and you can always learn along the way from help by others. If you need more info just message me and i will give u as much info u need but i hope with what i have said so far will give you a chance to see where i have went wrong as i have said its prob been something so basic that is right under my nose but i just havnt noticed it lol.
I hope there is something you can do for me and i hope to hear back soon thanks for your time if you even get to read this.
Kind Regards
Davie
davie6098 said:
* NEED HELP INSTALLING BUSYBOX *
I have joined this form as i have finally came to my wits with trying to get Busybox installed but i am getting nowhere with it. I found and old HTC desire 620 phone lying around and i thought i would use it as a project phone its running on Android Kitkat 4.4.4 i unblocked it first for any sim and its network is BT it use to be with O2 then i paid One Click Root to Root my phone (PROBS A STUPID THING TO DO AS THERE IS LOADS OF WAYS TO DO IT BUT I JUST WANTED IT DONE THERE AND THEN ) and i dont no much about the android system but would like to get familiar with it tho at somepoint. Once the phone was rooted my boot menu is with TWRP But i think i can change that to Clockwork or would it matter what one i have.
I have watched lots of vids and read a good few forms aswell but still cant get this app to install. If i download anymore apps to try helping me install this app i wont have any more room at all and this is the part is where you are probs going to see how stupid i am with android below are a list of apps i have downloaded to try help me :-
I paid for SuperSu Pro, Paid for Busybox Pro, ROM Installer, ROM Toolbox Lite, ROM Manager, Busybox on Rails, ES File Explorer, Mount /system RO/RW App, ASTRO, Hack App Data, SU Update Fixer, SU Root Tools, Total Commander, Terminal Emulator and i even downloaded Titanium Backup as someone said it could help with the install of Busybox but hasnt got me anywhere. I also have dsploit and Lucky Patcher both apps that i would like to work but both require Busybox to be installed.
Now i have downloaded a few Busybox apks and even the free vrsion from the app store Stephen (stericson) version and nothing happend then i paid to get the full version thinking it should work straight away as i have now paid for it but still wont install. This is my situation when i open up the app i am on the install page i select the box in the top right hand corner (Auto Update Busybox), the version is Busybox 1.26.2 and the install path to /system/xbin and when i hit the install button the message i get back says :- ( It looks like the installation of Busybox was not successful, try installing to a differant location, that may resolve the issue) the i hit the red X button and the app cuts of back to the home page. When i reopen the app i change the path to /system/bin the i get the same message and a split 2 seconds l8r my phone just cuts of then reboots only happens everytime i press the install button and the location selected is /system/bin. When i even tryed the other to paths :- /su/xbin and /su/bin at the bottom of my screen a quick message flashes up saying :- (Systemless root is not configured, please choose another install location)
I do apologize for this very long message but it would be appreciated if there is anything someone could do for me or point me in the right direction as every where else i have looked it has been unsuccessfull or its been far to confussing to even understand. I guess there would be most of use saying if i dont no what i am doing i shouldnt be playing around i do no that i could brick the phone or end up in a constant bootloop but as i said i found a spare phone that was still working and though i would give it a go and you can always learn along the way from help by others. If you need more info just message me and i will give u as much info u need but i hope with what i have said so far will give you a chance to see where i have went wrong as i have said its prob been something so basic that is right under my nose but i just havnt noticed it lol.
I hope there is something you can do for me and i hope to hear back soon thanks for your time if you even get to read this.
Kind Regards
Davie
Click to expand...
Click to collapse
First of all, the topic chosen for Desire Bravo A8181, which means that you have chosen badly.
If you want to be sure to busybox from the root, then first check that you have the root with a root checker.
For busybox you do not need to have root, however.
Check the Install BusyBox (No Root).
It works for me. I have Android 4.3 on Samsung.
This is an exploit, I take NO RESPONSIBILITY if this does ANYTHING bad, your fault not mine, it was only tested on the firmware mentioned below. If you redistribute it, republish, work it into a all in one click, please link back and PROPERLY credit me.
Tested on the
ro.build.date=Mon Jan 30 10:42:53 KST 2012
ro.build.version.incremental=ZV9.479A6632
Update for the VirginMobile LG Optimus V
Your phone needs to be updated to the above build, and potentially needs a factory reset before this works, but it works fine. This will allow you to flash recovery without being root. After flashing recovery, flash this zip http://dl.dropbox.com/u/8699733/rootme.zip to install su, superuser and disable re-flashing of the stock re covery
LinuxMac Script + files:
https://github.com/CunningLogic/GorditaRoot
Flash_image:
https://github.com/CunningLogic/GorditaRoot/blob/master/flash_image
Recovery:
http://www.mediafire.com/?vzc5k8taj9smmll (Credit BobZhome)
Windows users run the commands manually
GNU nano 2.2.2 File: Gordita.sh
Code:
#!/bin/sh
echo "GorditaRoot 1.0 by jcase / TeamAndIRC"
echo "for the VM670 Optimus V"
echo "March 21st 2012"
echo "Follow me! http://www.twitter.com/TeamAndIRC"
echo "Donations are optional http://forum.xda-developers.com/donatetome.php?u=2376614"
echo "-"
echo "Recovery taken from http://forum.xda-developers.com/showthread.php?t=1197991"
echo "-"
echo "Pushing recovery to /data/local/"
adb push VM670NH_recovery.img /data/local/recovery.img
adb push flash_image /data/local/
adb shell "chmod 755 /data/local/flash_image"
echo "Removing old sensor config, setting up symlink attack"
adb shell "rm /data/amit/*"
adb shell "ln -s /dev/mtd/mtd2 /data/amit/AMI304_Config.ini"
adb shell "ln -s /dev/mtd/mtd2 /data/amit/AMI304_Config2.ini"
echo "Rebooting to execute symlink attack, to chmod 666 the recovery block device"
adb reboot
adb wait-for-device
sleep 10
adb shell "rm /data/amit/*"
adb shell "/data/local/flash_image recovery /data/local/recovery.img"
echo "Recovery flashed! Enjoy"
Having trouble identifying whether or not you completed the root process? Quickly test for root access with Root Checker Basic
Confirmed working on a phone donated just for this purpose!
Started with stock firmware, Android 2.2.1, baseband VM670ZV4_60401001, generic android recovery
Flashed the VirginMobile Security Update from their website, became VM670ZV9_60401001 ZV9.479A6632
Manually walked through above script by jcase via gtalk, and using the exploit, was able to flash BobZhome's CWM for the VM670, reboot into it and made a backup.
Flashed the su zip, and all is well in Optimus V land again.
HUGE THANKS TO JCASE FOR TAKING THE TIME TO RE-ROOT THE VM670!!!
I only wish I understood what it all meant--so I could be excited, too!
wilberfan said:
I only wish I understood what it all meant--so I could be excited, too!
Click to expand...
Click to collapse
Means ppl who couldnt root before, now can
wilberfan said:
I only wish I understood what it all meant--so I could be excited, too!
Click to expand...
Click to collapse
i was gonna ask the same thing LOL
Hey! Sorry, I'm a ET4G user, just trying to put ICS on my girl's phone so she stops whining
Anyways, I presume there's an update being pushed to all optimus v's? If so would you happen to know how I could update hers? Or would it be easier to stay on the current version ( i belive v5???) and root a different way??
Also, great work on an exploit so soon after a release! Happy to join (kinda) the Optimus family!
jlear3 said:
Hey! Sorry, I'm a ET4G user, just trying to put ICS on my girl's phone so she stops whining
Anyways, I presume there's an update being pushed to all optimus v's? If so would you happen to know how I could update hers? Or would it be easier to stay on the current version ( i belive v5???) and root a different way??
Also, great work on an exploit so soon after a release! Happy to join (kinda) the Optimus family!
Click to expand...
Click to collapse
The update is not being pushed, because the OTA mechanism doesn't work on the OV. You have to go to the VM website and download the update from the phone FAQ.
The only advantage is a new radio, which give slightly improved performance.
Thank you very much!
I installed the update to my (unmodded) backup phone without thinking about whether or not I'd be able to root the handset after applying it. DOH!
I have just been using this phone as a WiFi device so far. I have run the battery down and recharged it once and installed a few apps on it. So I will run it down, recharge it again and then do a factory reset before I try rooting it just to make sure that I don't hose it.
It's a good idea to check all the steps before you start ...
Finally ran my battery down for the second time. So, I recharged, ran a factory re-set and ran the shell script on my Linux box to root the phone.
Oops!
The file VM670NH_recovery.img downloaded as VM670NH_recovery.bin and the system can't find/stat it! Hit ^C and bailed!
Hoping, hoping, hoping ...
Good! It's not bricked!
Renamed the recovery file, re-ran the script. Success!!
Rebooted into recovery, flashed rootme.zip
==> Did a nandroid backup.
Downloaded root check basic app and confirmed that it has worked.
So, for other modders trying this out:
Check your files and file names before you start! When I looked at Gordita.sh the first time I found that what I had downloaded was an HTML file with the script embedded in it. Copied and pasted from the OP and then checked again to make sure I had the right content.
Of course if you are running the adb commands manually then this won't happen to you.
But, as I noted above, I didn't cross-check that the recovery file that the script would be looking for had the right file name extension (.img, not .bin), so don't be me.
That said, jcase: Thank You Very Much!! Not only for developing this root exploit but also for making one that is robust enough for someone like me to goober it up and still come out unburnt!
After all of this , can you make it a hotspot in quick settings?
The setting dialog is there ..
H0daddy said:
After all of this , can you make it a hotspot in quick settings?
Click to expand...
Click to collapse
Once I rooted my phone I installed a modified ROM. And then another one, and then ...
I saw your question a bit ago and since I no longer had the stock ROM installed (and had never used Quick Settings to enable the hotspot feature before) I didn't know. I still don't. Here is the story on that ...
I just restored the ZV9 ROM from backup today and then installed the Quick Settings app. I can say that the app still has the option to enable the hotspot available and that it tries to set it up. However the phone I am using hasn't been activated yet and the 3G network isn't provisioned on it. So all I get is a message saying the network isn't available.
So, it looks somewhat promising. Maybe someone who has an activated phone with the ZV9 ROM can test it out and let you know.
And if I activate this phone before you get a useful reply I'll test it to see if it works.
So happy to see this
Please assist
Got up to step adb shell "chmod 755 /data/local/flash_image"
But got back "no such file."
CWM
Got up to CWM but it won't let me select install zip from sd card. Any suggestions?
knicks791 said:
Got up to CWM but it won't let me select install zip from sd card. Any suggestions?
Click to expand...
Click to collapse
so you have bobz recovery installed?... i assume youve tried rebooting to recovery form the powered off state via the key combo (HOLD home+vol down+power, RELEASE after the LG logo), and tried instal zip from sd again?...
try:
http://forums.projectopencannibal.net/beta-releases-11/lg-optimus-v-v2-1dev1-(10-09-2012)/
http://forums.projectopencannibal.n...1-universal-installer-for-lg-optimus-devices/
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
Sorry if the answer is somewhere in here but I have been looking for over a day.
This is what I have done:
I have a stock Verizon HTC One
Installed weak sauce gained root access.
Installed Firewater S-Off and HBoot worked Beautiful work thank you after hours of research. - For a Noob it went smooth.
Also flashed PhilZ Touch Advance and when I try to reboot it says: Root access is missing or broken.
Ran Root Checker: You have root access!
Super User Application Status:
SuperSU application - version 1.93 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 113036 2014-03-30 12:15 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
I'm sure the answer is in here I just dont want to F it up and my eyes are crossed from looking for answer.
Thanks Again.
How about just flashing a rooted ROM in your recovery and seeing if it's all good?
That easy?
orangekid said:
How about just flashing a rooted ROM in your recovery and seeing if it's all good?
Click to expand...
Click to collapse
Ok I will try that. Do you think the error is because I installed supersu incorrectly, or wrong method. I believe I dropped and dragged it to my download file then opened it with my file browser and installed. As long as that wont be an issue I will give it a shot. Thank You for responding to my noob question.
habatchaNow said:
Ok I will try that. Do you think the error is because I installed supersu incorrectly, or wrong method. I believe I dropped and dragged it to my download file then opened it with my file browser and installed. As long as that wont be an issue I will give it a shot. Thank You for responding to my noob question.
Click to expand...
Click to collapse
It could be a number of things, but you were going to flash a custom ROM at some point anyways, right?
@PonsAsinorem might be able to help on this.
ROM .... Check
orangekid said:
It could be a number of things, but you were going to flash a custom ROM at some point anyways, right?
Click to expand...
Click to collapse
I took your advice and flashed the NuSenceSix. It went off without a hitch, holding breath eh entire time. Thank you for the push.
I went back to the firewater threads and one thing I didn't do was remove weaksause. Is that something I need to do if I want the root to be permanent? I don't need to go to the android development and go though that process emailing system info or whatever its called do I?
Also I was about to read up on radios and kernals for this ROM as well as try and figure out why I am getting that message in Rootchecker.
Thanks Again for your help.
Please
synisterwolf said:
@PonsAsinorem might be able to help on this.
Click to expand...
Click to collapse
That would be awesome. Any suggestions would be greatly appreciated. As I was telling the Room Moderator I flashed the NuSense6 and it went off without a hitch. however it is Still showing the same messages with rootchecker.
Thank You
synisterwolf said:
@PonsAsinorem might be able to help on this.
Click to expand...
Click to collapse
Sorry for the late response; was at work.
habatchaNow said:
That would be awesome. Any suggestions would be greatly appreciated. As I was telling the Room Moderator I flashed the NuSense6 and it went off without a hitch. however it is Still showing the same messages with rootchecker.
Click to expand...
Click to collapse
If you're S-OFF, you're golden. Most anything after that is going to be a ROM issue. It's been a minute since I ran that ROM, but the early batches had issues with su being configured improperly. The easiest way to fix this would be to flash the update SuperSU zip in recovery.
I miss read the OP-
I thought he was saying that Philz recovery was showing Super User not installed on reboot when the rom is Rooted.
OP-
As for weaksauce, once you have s-off you will no long need the app. you can root any rom by flashing SU.zip if you have an S-off device running a custom recovery.
habatchaNow, what version of PhilZ are you running? There was a bug that misdetecting CM, but that's been fixed, and I don't think this rom ever had the false positive, because root actually wasn't configured properly at the time.
Custom Recovery Version
PonsAsinorem said:
habatchaNow, what version of PhilZ are you running? There was a bug that misdetecting CM, but that's been fixed, and I don't think this rom ever had the false positive, because root actually wasn't configured properly at the time.
Click to expand...
Click to collapse
Let me see, it looks like my custom recovery is PhilZ 6.40.4 Cyogen Mod V6.0.4.8. I think the problem started when I installed and ran super su. I side loaded it( that's moving it onto my device via explorer right?) Do you guys recommend another ROM for my phone? I like the NuSence it just seems like a minor upgrade to the stock ROM. I don't know if this matters but when I open my files on the phone the "root" folder and "sbin" folder are both empty.
One of my challenges is that I don't even know what I don't know so, I really appreciate the help. If you ever need help or advice with health/life/investments I'm your guy.
If you like that ROM, then stick with it. I try not to steer people away from any ROM. To fix your su problem, try flashing this from recovery.
http://download.chainfire.eu/supersu
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