Related
In several places in the forums I see DSP manager mentioned as a way to change the sound output from the phone.
It is possible to use the .apk file or flash the .zip file to a stock firmware that is rooted (no other changes), or does it have to be applied to a custom rom?
Ta.
Here you go...
http://www.multiupload.com/7VS5O9KKQ0
Flash as you would a ROM
Hmm, I flashed it and the settings appeared, but they seem to make no difference to the sound output!
Trying via headphones? As I doubt you'd notice from the internal speaker
Other than that I can't help, have no issues personally
Yep, trying via headphones. Seems to make no difference at all. I am running a stock rooted HTC Rom.
Hi, I flashed the DSP from recovery and rebooted. Installation was successful but I can't find the app anywhere in my phone? where do I see it?
SOLUTION
ilya.glants said:
Hi, I flashed the DSP from recovery and rebooted. Installation was successful but I can't find the app anywhere in my phone? where do I see it?
Click to expand...
Click to collapse
For anyone else having this problem:
I didn't find the app I installed so I searched the net for other installation files, and found this:
h ttp://androidforums.com/1446319-post107.html
after I flashed this and rebooted, I got a 'force close' notification for the app. Than I went to /system/app/DSPManager.apk and installed it.
DSP Manager now working great ^^
I did as u said but it gives me a force close and when i try to install it i cant cause its already installed, cant uninstall it either, what should i do ? BTW I'm using AuraxTSense v7.4
did you install the one in the second post as well?
I'm using AuraxTSense 7.0
Yes, first I installed that one, it didn't work, then I installed the other. Is that the problem ? I thought so... so how should I fix it ?
good question..I'm not sure.. try installing the first again
Ok I did it, it removed the app from the app list. What now ? If I try installing it from /system/app it gives an error.
I don't know.. i just rebooted my device and it gave me the force close again. so I did what I did the previous time and ran that app from the location I wrote.. worked like a charm.. again..
ilya.glants said:
I don't know.. i just rebooted my device and it gave me the force close again. so I did what I did the previous time and ran that app from the location I wrote.. worked like a charm.. again..
Click to expand...
Click to collapse
I installed the other zip again, gave me a force close so went to system/app and tried to install it but I can't, only have the options uninstall and launch... No idea why is it working for you and not for me...
EDIT: Ok it works now, had to remove first the odex file and install the other zip again
Update DSP Manager
You can remove the DSPManager.apk file using the terminal emulator.
NOTE: You need to have a rooted phone, Superuser & Terminal emulator.
STEPS
1. Change to root user it is granted super-user permissions.
su -2. Then change to the system app directory.
cd /system/app3. Then move the DSPManager.apk to the tmp directory.
mv DSPManager.apk /tmp4. Move the new apk file to the system app directory.
NOTE: Change to the directory where the DSPManager_1.0.apk is.
cp DSPManager_1.0.apk /system/app5. Reboot the phone.
6. Check in the apps list and the new DSP Manager should be in there.
NOTE: If it all worked you can remove the DSPManager.apk from /tmp
rm /tmp/DSPManager.apk
Attached is the version I use on my rooted HTC Desire.
In order to work, DSP Manager also needs a file called libaudioflinger.so in the /system/lib directory in addition to the apk.
The easy way to get this done is to use an update zip for DSP Manager. Get it from one of these links (all links from this page):
FileServ
MultiUpload
My FTP
doesnt get android to work on my hd 2... i managed it once but since i updated my android build i dont get it anymore...
i think it because i dont have an root folder in the android folder where i can put the files in ????????
if i just install it from the zip via astro explorer it appears in the menue but there is no change in audio ?!?!?!
what can i do ???
B-Man2005 said:
doesnt get android to work on my hd 2... i managed it once but since i updated my android build i dont get it anymore...
i think it because i dont have an root folder in the android folder where i can put the files in ????????
if i just install it from the zip via astro explorer it appears in the menue but there is no change in audio ?!?!?!
what can i do ???
Click to expand...
Click to collapse
I don't think you can install the zip from Astro Explorer because it needs to copy files to the /system partition which is read-only when the phone is booted up. In other words, you must have a rooted phone to do this.
If you do have a rooted phone, then reboot into recovery mode and install the update.zip the usual way.
If you don't have a rooted phone, well that's a whole different story.
i , please help me.
I've installed it via recovery and I made backup with my original needly files: libaudioflinger and libaudio. Then i copied my files back (deleted new files and moved old files) . I restarted my phone and it didn't boot. Just show me the White window (T-mobile)... Can i repair my phone by myself? Please help me and sorry for my english.
maximus rus said:
i , please help me.
I've installed it via recovery and I made backup with my original needly files: libaudioflinger and libaudio. Then i copied my files back (deleted new files and moved old files) . I restarted my phone and it didn't boot. Just show me the White window (T-mobile)... Can i repair my phone by myself? Please help me and sorry for my english.
Click to expand...
Click to collapse
I'm sorry I don't really understand the problem. Normally, installing the update.zip should be all that you need to do. I don't understand why you copied the old files back and were those two files the only files that you backed up?
My phone is rooted, Super User is running for ROM manager. I get an error every time i click "Flash ClockwordMod Recovery" HTC G2 is clicked, then i get the error "An error occured while flashing your recovery"
Help please, Im rooted and SU is running fine. I also have busybox.. not that it has anything to do with it. I just want to install a custom rom. thanks
i am having the exact same problem as well. could it be a problem with the server side?
Could be the download.
You could always use the manual method.
I all ready have CWM 3.0.0.5 installed i've just gone in to rom manager and tried to flash and older recovery and I'm getting the same error. There is a manual method, trying to find it now and will post here when I do
Sent from my HTC Vision using XDA App
Same issue, if someone can post the latest recovery file. It lives somewhere in the clockworkmod directory on the sd card. If you can also tell us what the directory is, we should be able to place the recovery in the same directory. That way rom manager will not try to download. thanks.
OK download recovery image from here http://mrcellphoneunlocker.com/recovery.img you will need to do this from your pc not your phone then transfer to your sdcard don't put in a file though and rename to recovery.img
I then open termianl emulator and type in
su
flash_image recovery /sdcard/recovery.img
I don't think this version of CWM is up todays though
Sent from my HTC Vision using XDA App
Quoted my self instead of editing
Thanks, but to get latest recovery image, can you do as I suggest and get the recovery image from the clockword mod directory on the sd card? If can also tell us what the full directory path is, we can 'trick' rom manager into not needing to download. Thanks.
I
saquib said:
Thanks, but to get latest recovery image, can you do as I suggest and get the recovery image from the clockword mod directory on the sd card? If can also tell us what the full directory path is, we can 'trick' rom manager into not needing to download. Thanks.
Click to expand...
Click to collapse
I've looked but I can't find it. I've searched the forums and I can't find a direct download for the latest recovery ill keep looking though. If not I'm sure I have a copy on my pc.
Sent from my HTC Vision using XDA App
Recoveries are here:
http://mirror.kanged.net/recoveries/
Anyone got the flash_image script?
saquib said:
Anyone got the flash_image script?
Click to expand...
Click to collapse
flash_image is a binary not a script, in any case you can get it here:
http://forum.xda-developers.com/showthread.php?t=902493
Hi,
I'm following the tutorial here: http://forum.xda-developers.com/showthread.php?t=1739426
I am on the 3rd option and am trying to load the latest clockworkmod on my GS3, I have it downloaded, but it is an .img file.
The tutorial says:
if you download this recovery you will need to extract this file (if you have issues extracting try removing the .md5 extension first) to get a recovery.img file and copy to your phone's internal /sdcard
connect your phone to computer and use adb
type adb shell
once in the shell run su
then
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Can someone please explain this in more detail? I am looking for links to the ADB program I need as-well as how to use it to apply those commands.
Also I am having a hit-or-miss issues with Windows reading my phone as an external device, the phone reads as an established MTP connection but Windows sometimes reads it, or does not. What am I doing wrong here?
Thank you.
Info:
Phone: Samsung-SGH-I747
Carrier: AT&T
Andriod Version: 4.1.1
OS: Windows 8 64Bit
Samsung Software: Kies 2.5.0.12114_1
Here is how I done it. It's in a zip file if you already have the non-touch version installed. All you need to do with this is install from SD from CWM recovery. None of the adb stuff has to be messed with. 7th post.
http://forum.xda-developers.com/showthread.php?t=1877761
Edit: This was on down in the post you quoted. If you don't have any CWM recovery installed, then do the below, then install the above touch version zip from sd in CWM recovery.
Third, alternate #3 if unfamiliar with adb commands and uncomfortable using any command line
Decide if you want to use TWRP or CWM.
If you would like to install ClockworkMod recovery then grab Rom Manager from the Play store and in the menu select to install ClockworkMod Recovery.
I am no expert by any means but you have to run those commands in the command prompt (DOS) system. Hit the start menu and find the run and type in cmd and that will open up command line or it should be in the Accessories folder as well.
If Windows sometimes doesn't recognize your phone I would uninstall and re install the drivers to see if that helps.
I have a heck of a time to get ADB and everything working when I first started so I know how you feel. Just keep reading the forums and everything and you will get it to work.
bo.benson said:
Here is how I done it. It's in a zip file if you already have the non-touch version installed. All you need to do with this is install from SD from CWM recovery. None of the adb stuff has to be messed with. 7th post.
http://forum.xda-developers.com/showthread.php?t=1877761
Edit: This was on down in the post you quoted. If you don't have any CWM recovery installed, then do the below, then install the above touch version zip from sd in CWM recovery.
Third, alternate #3 if unfamiliar with adb commands and uncomfortable using any command line
Decide if you want to use TWRP or CWM.
If you would like to install ClockworkMod recovery then grab Rom Manager from the Play store and in the menu select to install ClockworkMod Recovery.
Click to expand...
Click to collapse
Currently my phone has NO clockwork Mod installed, I am wanting to install the latest version ( recovery-clockwork-6.0.1.2-d2att ) I have this file in .img format, I am trying to figure out how to install it on my phone -- the tutorial says add it to your sdcard, I have done that, then it says connect to your phone and use ADB commands, that is the part where I need more information, also do I wipe cache/reset settings/dalvick cache during any of this process? Should my phone be in download mode when doing ADB commands or what specifically is where I do not understand.
I would like to understand the process more in-depth and ADB as well - opposed to going the RomManager route, from my research it seems that updates/versions are available first with that method.
Thanks
Kweli87 said:
Currently my phone has NO clockwork Mod installed, I am wanting to install the latest version ( recovery-clockwork-6.0.1.2-d2att ) I have this file in .img format, I am trying to figure out how to install it on my phone -- the tutorial says add it to your sdcard, I have done that, then it says connect to your phone and use ADB commands, that is the part where I need more information, also do I wipe cache/reset settings/dalvick cache during any of this process? Should my phone be in download mode when doing ADB commands or what specifically is where I do not understand.
Thanks
Click to expand...
Click to collapse
He gave you the link to the play store app in the post. It's android terminal emulator..type terminal emulator in play store its the top app.
I just merely gave you a second option which I did and functioned flawlessly. Grab Rom Manager from the play store and select the top option to flash CWM Recovery. It will ask you your phone type and carrier and then will give you the option to install it. Easier than the whole adb thing.
Ok that route did work, thanks.
Now I installed the latest CM10 Nightly - cm-10-20121206-NIGHTLY-d2att
And then rebooted and installed the latest Gapps - gapps-jb-20121011-signed
It does not seem that any of the google apps are in my apps
Also the Play Store no longer works....just "Connection Timed Out"
Specifically I am looking to use Google Now/G-Mail/Drive/Voice/etc...
Did I do something wrong? CWM said the Gapps installed successfully. Was I supposed to wipe cache somewhere?
Thanks for the help.
bo.benson said:
He gave you the link to the play store app in the post. It's android terminal emulator..type terminal emulator in play store its the top app.
I just merely gave you a second option which I did and functioned flawlessly. Grab Rom Manager from the play store and select the top option to flash CWM Recovery. It will ask you your phone type and carrier and then will give you the option to install it. Easier than the whole adb thing.
Click to expand...
Click to collapse
Kweli87 said:
Ok that route did work, thanks.
Now I installed the latest CM10 Nightly - cm-10-20121206-NIGHTLY-d2att
And then rebooted and installed the latest Gapps - gapps-jb-20121011-signed
It does not seem that any of the google apps are in my apps
Also the Play Store no longer works....just "Connection Timed Out"
Specifically I am looking to use Google Now/G-Mail/Drive/Voice/etc...
Did I do something wrong? CWM said the Gapps installed successfully. Was I supposed to wipe cache somewhere?
Thanks for the help.
Click to expand...
Click to collapse
I have not noticed that. I used the same Gapps file to do mine and everything worked fine on I believe the 11-30 NIGHTLY, no wiping that I remember. Now this was before I got on Official JB, was still back on stock ICS. Haven't flashed CM since upgrading. I will after today as battery life sucks on the Official, if it does the same to me I will let you know.
Touch version of CWM is pretty sweet, no accidental clicks too far with the volume keys, works right from your screen. That was the link in the first post I gave you. Download it to your SD, go into recovery and install it from SD.
Looks like mine had no problems with the gapps 11-30 nightly coming from LK3. Haven't got around to downloading the latest nightly yet. Will do today. Let me know if you got it resolved.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
This being my first post a HI EVERYBODY is in order.
On with the show.
So, I managed to unlock my bootloader via htcdev website, i slapped on the cwm recovery and managed to put a custom rom on my cell.
The rom in question is the jellyking, works fine, everything is great.
PROBLEM:
although ive tried several cm10 roms i liked jellyking the most but on all of them i had troubles getting root.
what happens is that i download es file manager, set it to give me root and mount system as RW, popup says that the preinstalled (with rom) superuser app granted those rights and that everything should be superb, but I couldnt copy files from my sd to lets say /system/media (wanted to change my bootanim) it says file copy failed, only once i did manage to copy a file but i dont know how.
The question:
when i put a custom rom, do i need to reapply the famous root.zip or maybe install busybox as my first app or maybe flash over the existing superuser app the superSU app which seems to update the root binaries sucessfully.
BOTTOM LINE:
What is the exact (if any) procedure that I need to follow to get perm root access (copy rights) to my own phone, each and every reboot.
Thanks in advance for all Your insights,
Humbly,
egr2lrn
I'm having a problem with es file explorer and root explorer. Last night my fire tv kept booting to home screen and rebooting, so I had to re-install 5.0.5.1 prerooted rom thru recovery. I reinstalled all my apps, and when trying to enable root explorer, I get the superuser request as usual, I grant and get the notification that it's been granted. Root explorer access is enabled for about 6 seconds before disabling with the message "Sorry, test failed. This feature cannot run on your device". Adaway works fine when asking for su permission. Only thing I did differently this time around with installation of the rom is I installed Es file explorer and tried to enable root explorer before doing the SU command from adb shell. I've since uninstalled and reinstalled ES file explorer and reacquiring SU permission but it does the same thing. I went and installed a much older version and it does the exact same thing. Anyone else come across this problem?
The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.
deanr1977 said:
The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.
Click to expand...
Click to collapse
Thanks for your reply. I'll do what another user suggested and use Total Commander instead as I have it installed and granted root access for it, and it does the same functions. I haven't had any issues with es file explorer on my ftv 2 at all, but another user reported the exact same problem in a different thread on this forum so I'm not alone.
Ok mate no worries, just a note I have both manager apps working on 2 sticks (1 rooted & 1 not, both updates blocked but on different firmware) & also on my prerooted AFTV2 so dunno what happened with yours & the other forum member?
Sent from my SM-G900F using Tapatalk
i have this same issue on 2 firebox's after a full conversion from os3, running rbox latest 5.2.x
both give the identical error, yet other apps are getting su control just fine?
any idea's? @rbox
I am having this problem on my first FTV1 I upgraded from PreRooted FireOS 3 to latest PreRooted FireOS 5. It is a fully rooted with fully unlocked bootloader FTV1. ES File Explorer is giving me this error when trying to turn on its Root Explorer option and all though Total Commander & Root Explorer are not giving me this error. They are not letting me copy files from a Root folder into regular storage. I can view them & choose them but it errors out when trying to copy over. I had to copy them thru TWRP.
I plan to do a Factory Reset thru TWRP & reinstall the latest PreRooted Rom again. But this time after doing the TWRP special build number update blocking tweak. I plan to run the SU command before installing any apps. Will see if that helps at all or not. If not I will post more detail info in case someone can help. This is the last bug I've encounter since doing the move from FireOS 3 to FireOS 5.
@d3adpool , @deanr1977 , @LittleBill21
Where you guys ever able to come up with an answer or fix for this issue ??
Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.
Y314K said:
I am having this problem on my first FTV1
Click to expand...
Click to collapse
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?
d3adpool said:
Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.
Click to expand...
Click to collapse
Sorry to hear that, thanks for responding. I had already done a few reinstalling of the latest PreRooted Rom via TWRP without that fixing it. Will keep at it, though.
phresch said:
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?
Click to expand...
Click to collapse
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
---------- Post added at 01:07 AM ---------- Previous post was at 12:17 AM ----------
@RBox ; @AFTVnews.com
Decided to upgrade my first TowlRoot Rooted Bueller FTV1 on the last FireOS 3 PreRooted Rom (v51.1.6.3) to the latest FireOS 5 PreRooted Rom (v5.2.1.1_r1). I verified that I meet all the requirements. My bootloader was FULLY unlocked & I was on the latest CWM (v6.0.5.1.4a) with BootMenu (v1.0). I decided I wanted from the start the upgrade on as a clean as possible FTV1. So I uninstalled all programs except for SuperSU. Then I went into CWM & did a Factory Reset (Wipe Dalvik, Cache, Factory Reset) from within CWM & Reinstalled the last FireOS 3 PreRooted Rom (v51.1.6.3). All that was left after the Factory Reset was SuperSU.
Then I pushed over the TWRP bueller-twrp_3.0.0-7.img to the /SDCard & verified it's hash to make sure it was not a corrupt upload. Then I ran the command to switch to the TWRP recovery & everything installed perfectly.
I had ready a USB stick (Fat32) so I could install & md5 verify the FireOS 5 PreRooted Rom (v5.2.1.1_r1) on installation. Booted into TWRP & first did a wipe from within TWRP of Dalvik, Cache, Data & Internal Storage. Then installed the FireOS 5 PreRooted Rom (v5.2.1.1_r1) without any errors. Then I rebooted into system & it went thru it's paces. I did hit a road block when it came to check updates. This was because I was blocking the HTTPS update address from both my router & thru OpenDNS. I did a few re-flashes of the FireOS 5 PreRooted Rom (v5.2.1.1_r1) until I figure out that since this was the latest Rom version I should just let it talk to the update servers or do the PropBuild mod. So finally I got past the update nag. I first turned on ADB Debuging & I first did the SU command & chose to GRANT SuperUser rights. Then I did the update block command from SU. I installed my apps & the only bug I found after that was that ES File Explorer, even after it has been granted SuperUSer rights. It will error out "Sorry, test failed. This feature cannot run on your device". I thought this problem was just with ES file Explorer. But it seems to happen to a lesser degree on Total Commander & Root Explorer too. On those I can see the Root directories. But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
I tried flashing the bueller-fixsusdcard.zip thru TWRP on that install but nothing changed on the test response. Then I tried to do a full reinstall of the PreRooted Rom with the bueller-fixsusdcard.zip as a secondary .zip to flash during the installation. And same... Then I re-verified that I do have a unlocked bootloader. And that I am rooted. Passed on both. I was able to verified I am rooted by using an SDCard app while trying to see what size my MBCache.db file was. I was able to find it in /Data/Data/ without any problem.
So this is where I am at. I wonder if the bueller-fixsusdcard.zip file needs an update for FireOS 5 PreRooted Rom (v5.2.1.1_r1). Or should we try to install SuperSU as a secondary .zip file in TWRP or what can possibly be the answer to getting SU & Root working properly.
I would appreciate any ideas to try.
Y314K said:
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
Click to expand...
Click to collapse
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
Click to expand...
Click to collapse
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
phresch said:
...
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
I searched for a download of v2.05 and could only fine sources that I did not trust. Do you have a link to that version?
phresch said:
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
Click to expand...
Click to collapse
I haven't tried to change or flash to a different SuperSU then the one that comes stock with the PreRooted Roms. Which is v2.46. Trying my best not to loose having a Fully unlocked bootloader. Are you flashing/testing the different versions of SuperSU thru TWRP or are you just flashing APK's just to try to see which one's GUI might still work ?
I notice the SU /SDCard bug only after trying out Total Commander & Root Explorer. Others said those where working fine for them. But for me it looked like they where gonna work fine. But as soon as any of those went to Root mode. I started to see bugs in those programs too. Although in those programs I can at least view Root files. And this last time Root Explorer is letting me copy files over from Root to /SDCard. Total Commander is still hanging when trying to copy files from Root to /SDCard. Like I said this last time I installed the /SDCard SU .zip fix right after I flashed the PreRooted Rom. So it did changed something. But from ADB I still get the same response from the SU List command.
phresch said:
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
Click to expand...
Click to collapse
I have not swapped SuperSU from what comes with the PreRooted Rom. Trying other SuperSU versions might be something I do after getting some feedback from @rbox since I really do not want to accidentally loose my Fully unlocked bootloader.
phresch said:
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Click to expand...
Click to collapse
Are you doing the SuperSU changing thru APK flashing or thru TWRP zip flashing ? Do you know a link to where we can find most versions of SuperSU from v2.16 (used when we towelrooted) to v2.78 ? I see v2.79 is the latest version. Have you tried v2.79 on your FTV1 ? Is there a version of SuperSU we shouldn't go beyond ?
phresch said:
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
Please post v2.05. I wonder if we can go down to v2.05 for that option. And then when things are working right go back to v2.46.
Either way ES File Explorer / Root Setting will not work for your right. Not matter what?
Hope I can get past this bug before updating my other 3 FTV1's.
Just ran into something else that is very odd. I've been using Amazon FireTV Utility App v0.66 to access ADB non-Root & Root Shell. Decided to switch to the stand-alone "adb-setup-1.4.3" to see if that would help with the SU commands. But I found that as soon as I give it the "adb shell su" command. Even if SuperSU has been granted full access on a fresh install of the PreRooted Rom on the FTV1. The "[email protected]:/ # _" line gives me a blinking _ & it won't let me input anything else. On the FTV1's screen it says "ADB Shell (2000)" was granted root access each time. But I can't get past that. Is like ADB never receives the granted access response. Then I have to CTRL+C to be able to input anything & exit. This happens whether I opened the CMD with & without Admin rights on my Windows 8.1 PC.
Gonna try downgrading to adb-setup-1.4.2 but I doubt it will make a difference. So the bugs are bunching up. Seems SuperSU is not being installed or allowed to work properly. Any help would be appreciated.
Forgot that on FireOS 5 you have to break the command.
First "adb shell" to get "[email protected]:/ $" & then just "su" to get to "[email protected]:/ #" without it freezing.
The /SDCard list still had the same response though.
"lrwxrwxrwx root root 1970-01-07 19:45 sdcard -> /storage/emulated/legacy"
Solution:
First let me start by Thanking @rbox , @AFTVnews.com , @zroice , @phresch for all their work & feedback.
Was finally able to test multiple options & found a reproducible solution to this problem. The key was in @zroice post about Holo Themer.
https://forum.xda-developers.com/fi...w-to-supersu-xposed-app-t3552590#post71703744
Basically you got to make sure you install or have installed the latest version of BusyBox & XPosed & HDXPosed Module. And to have activated Holo Themer from within XPosed so you can run the SuperSU APK that comes with the PreRooted Rom. SuperSU should ask you to update. Once you have done a "Normal" update like we did when we first rooted our FTV1's then that should fix the Root Option fail that ES File Explorer & other apps have had. I am guessing the problem comes when we uninstall or wipe our FTV1's during our FireOS 3 to FireOS 5 update. Some of us thought BusyBox & Xposed would not be as important to functionality on FireOS 5 as it was on FireOS 3.
Make sure you only activate Holo Themer on a per needed basis. Since it will make your FTV reboot randomly if you leave it on all the time.
And like always. As long as you installed TWRP correctly. You can always start anew with a wipe (NEVER WIPE SYSTEM) & install of the latest PreRooted ROM. I would also recommend having all the files you know you will need in a USB drive or SDCard in FTV2's case ready to go & in separate folders before you start flashing away. Makes things much easier.
If you forgot how to install BusyBox or XPosed you can always find how in the many guides over @ AFTVNews.com . For me even the old FireOS 3 guides & FTV2 guides help as a good refresher or visual confirmation.