Develop Bugs

[Q] Reinstall HTC Sense stock apps

Hello,
I've removed the Gallery app (com.htc.album.apk) using the Titanium backup 'cause I wanted to replace it with another one. I do have the backup, but when I do a restore it just does the circle with restore in progress forever. Is there a way to restore the Gallery?
The only reason why I want to restore is that when I use the HTC Sense apps which cooperate with Gallery (for example the Camera), when I want to see the photos the apps crash - I thought it would be possible to choose another app like QuickPic for this photo browsing, but apparently not. Therefore I would be very grateful if somebody knows how to restore the app.
The phone has s-off and is rooted.
Thank you very much.

SOLUTION
OK, I've found a way how to do it, so just want to share with others, in case anybody gets into the same kinda trouble as I did ;-)
The steps:
1. Download the zipped RUU of the stock ROM and extract the APK and ODEX files of the app you want to restore (HTCAlbum.apk and HTCAlbum.odex in my case)
2. Using Root Explorer (or some other tool that can write into /system/app) copy the apk and odex files into it.
3. Again using the same tool set the permissions of the 2 files to rw-r--r-- and set the owner and group to 0 - root (both user and group)
4. What I did now was try to Install the apk in the /system/app, but it failed, so probably this step is not needed - just put it here in order to reproduce exactly all steps.
5. Reboot the phone -> after the reboot the app should appear in the app drawer and all HTC stock apps now work with using the Gallery.
Please if you try this method, write down your comment, whether you succeeded or not.
Cheers and good luck...

Didn't work for me. Tried apk and odex gallery from newest ruu.

I also accidentally removed the Gallery (com.htc.album.apk), and I've found a way out to do it.
First to do :
> Install the latest Java JDK.
> Install HTC Sync & drivers.
> Install the Android SDK.
> Open SDK Manager after installing the Android SDK successfully.
> Install every 'Available Packages' in SDK Manager.
> Edit 'Path' in Environmental Variables and put this behind the line
Code:
;C:\android-sdk-windows\platform-tools
> Enable USB Debugging on your HTC.
And after all this above..
1 -Connect your Wildfire to the PC.
2 -Reboot into CWM Recovery.
3 -Go to Mounts and Storage.
4 -Select Mount /system.
Then use adb :
Oh and make sure the HTCAlbum.apk is in the same map as adb.exe
Code:
adb push HTCAlbum.apk /system/app
-MAKE SURE YOUR DEVICE IS S-OFF- Otherwise it won't work.

Solar_ said:
MAKE SURE YOUR DEVICE IS S-OFF- Otherwise it won't work.
Click to expand...
Click to collapse
This doesn't need S-OFF. Just a Custom Recovery like Clockworkmod.

rocky7x said:
OK, I've found a way how to do it, so just want to share with others, in case anybody gets into the same kinda trouble as I did
The steps:
1. Download the zipped RUU of the stock ROM and extract the APK and ODEX files of the app you want to restore (HTCAlbum.apk and HTCAlbum.odex in my case)
2. Using Root Explorer (or some other tool that can write into /system/app) copy the apk and odex files into it.
3. Again using the same tool set the permissions of the 2 files to rw-r--r-- and set the owner and group to 0 - root (both user and group)
4. What I did now was try to Install the apk in the /system/app, but it failed, so probably this step is not needed - just put it here in order to reproduce exactly all steps.
5. Reboot the phone -> after the reboot the app should appear in the app drawer and all HTC stock apps now work with using the Gallery.
Please if you try this method, write down your comment, whether you succeeded or not.
Cheers and good luck...
Click to expand...
Click to collapse
It worked! Thank you:good:

[Q] BenQ B50 Can Root it ?

sorry , My english is poor
The Phone Can Root it?
i won't use 1 key root , because 1 key root APP , too many have virus and Crash APP
my phone is BenQ B50 LTE , 1G ram / 8G rom .
dual sim
dump two IMG Files
Boot.IMG And Recovery.IMG
here:
Recovery
https://mega.co.nz/#!Q8t02Y4R!ZsDU9OqNotu0jETJ3VmscgNeC8wHnFPWEoBu5ygvZck
Boot
https://mega.co.nz/#!U01TGbbC!Z14cU91HyGNRpKQ53x6mDiXx2Rq8q7zqKfCKujp8ON8
Two Image
if need dump more IMG , i'll upload files

Use iRoot/VRoot then change to SuperSU . No virus if use Vroot except it install a china app store but after downloading SuperSU it will uninstall the Vroot Superuser and also the china app store. We use this with 98% success rate on phones in Asia.

cracktech said:
Use iRoot/VRoot then change to SuperSU . No virus if use Vroot except it install a china app store but after downloading SuperSU it will uninstall the Vroot Superuser and also the china app store. We use this with 98% success rate on phones in Asia.
Click to expand...
Click to collapse
Thanks,
I Use VRoot , can root it
but supersu binary out of date in other SuperUser App
else only Default VRoot SuperUser APP ?

Can u confirm this is your model? http://www.benq.com.tw/product/smartphones/b50/specifications/ . If it is MTK SoC it is very easy for me to help you.
First -Dont worry about the "su" binary needs to be updated. YOu do this first 1- install Mobile UncleTools (from Playstore) 2. download the CWM recovery (from the link I give you and copy to sdcard , 3- Select "Update recovery from MobileUncleTool - search for the CWM Recovery and answer "yes". 4- Check recovery has been installed (Vol+/Vol- plus Power button OR from within MobileUncleTool you can select "reboot into recovery") 5. Download and copy "ROOT_MTK.zip" to sdcard and from CWM select "install" . F I N I S H!!
Your phone is now rooted with SuperSU 2.46 plus busybox and no future problems with "su" binary update.
Please go to this link to select all the files necessary to do this : CWM recovery/ ROOT_MTK/ : :removed link

cracktech said:
First -Dont worry about the "su" binary needs to be updated. YOu do this first 1- install Mobile UncleTools (from Playstore) 2. download the CWM recovery (from the link I give you and copy to sdcard , 3- Select "Update recovery from MobileUncleTool - search for the CWM Recovery and answer "yes". 4- Check recovery has been installed (Vol+/Vol- plus Power button OR from within MobileUncleTool you can select "reboot into recovery") 5. Download and copy "ROOT_MTK.zip" to sdcard and from CWM select "install" . F I N I S H!!
Your phone is now rooted with SuperSU 2.46 plus busybox and no future problems with "su" binary update.
Please go to this link to select all the files necessary to do this : CWM recovery/ ROOT_MTK/ :
Click to expand...
Click to collapse
Yes , My Phone is model.
First , Very Thank You To Help me
Because of My phone was returned for repair.
The main reason for failure camera options
I am waiting for the phone to come back
I will do it
Very thanks you , Again .

cracktech said:
Can u confirm this is your model? ]
Click to expand...
Click to collapse
My phone has return
I Try it. it can Root ,thank you!
I use MTK_ROOT.zip File , But this File was install some app ?

Yes MTK_ROOt installs additional apps for MTK users only!
jackyui said:
My phone has return
I Try it. it can Root ,thank you!
I use MTK_ROOT.zip File , But this File was install some app ?
Click to expand...
Click to collapse
Yes it does but not SPYWARES! NTPSync is for you to get very fast GPS satellites lock (please add the 2 digit "XX.pool.ntp.org" XX= your current country e.g. "cn" =China , "tw"=Taiwan, "de"=Germany. MTK Suite is for you to do backup of IMEI process and Download of "ETO.db" also for GPS. just press download "eto" only 3-4 seconds and then "install" . "QuickExit" is for you to use when an app is frozen and you cannot exit the app , just swipe down from top task bar tap on QuicExit. It will exit the app.
If you dont want them since you have already "Rooted" you can "uninstall" them by using any "root uninstaller". Goodbye.

cracktech said:
Yes it does but not SPYWARES! NTPSync is for you to get very fast GPS satellites lock (please add the 2 digit "XX.pool.ntp.org" XX= your current country e.g. "cn" =China , "tw"=Taiwan, "de"=Germany. MTK Suite is for you to do backup of IMEI process and Download of "ETO.db" also for GPS. just press download "eto" only 3-4 seconds and then "install" . "QuickExit" is for you to use when an app is frozen and you cannot exit the app , just swipe down from top task bar tap on QuicExit. It will exit the app.
If you dont want them since you have already "Rooted" you can "uninstall" them by using any "root uninstaller". Goodbye.
Click to expand...
Click to collapse
BenQ B50 , Never backup ROM And Reboot Option Select "Yes" in CWM
Because it will only front camera lens :crying:

Can root Sony M5?

Hi,all
Anyone had try root Sony M5 successfully?
Thanks

Not ure, but it seems that there is no unlock bootloader yet....
You may have to check the talk .sony forums. I'm sorry that XDA doesn't let me post links yet.

i want to get sony m5 root . how to root m5 ?.plz teach me. my email adress is [email protected]

Ydnb said:
i want to get sony m5 root . how to root m5 ?.plz teach me. my email adress is [email protected]
Click to expand...
Click to collapse
You're going to have to wait for quite sometime. Firstly Mediatek is something new for Sony. Previously it was Qualcomm so the steps are more or less the same. Secondly this is a mid range phone by Sony so there won't be much waves about this phone because most people will be getting Z5.
But nonetheless i think this phone is pretty decent that's why i get M5 instead of Z5.
So we got to be patient. Very very patient.

RootMaster (Chinese products)it works finely
http://www.romjd.com/jiaocheng/content/12500 -the link to the page
download link- http://soft.mgyun.com/files/product...350976/VRoot_1.8.5.15285_cid2040_44c47ecb.exe (skip it-click more information and click browse unsafe )
First install driver and tick USB debug in dev option, security unknown sources,screen sleep set to 10min and last install the root master u downloaded
Second start the program and tick i agree the terms beside the green button (green button-mean connect device )connect your M5 before click the button after u clicked the button it will try to connect your M5 and a green button also tick the i agree beside the green button and click the button
一键ROOT and sit on your chair and wait til done.
How you know your phone is rooted or not, first check did your device reboot by the program and after it check superuser aplication app is installed or no.If the App (permission manager)not suit to you ,download ES file manager from playstore and install SuperSU from playstore and use es file manager to backup SuperSU apk with the tool include in ES file manager next rename SuperSU apk in backup folder and hold it and move to system with right R/W permission (before move the apk go to ES file manager sidebar and find Root Explorer in Tools tab click the on off Root Explorer and grant root permission and click it again click Mount R/W label and make all paths to RW )and all done
the SuperSU apk rw permission in the system folder hold the supersu apk and click properties and click change permission with
rw-r-r
x=tick and o =untick
(xxo)
(xoo)
(xoo)
and after it reboot phone and open ES file manager go to system/app and delete the App (superuser came from the root program) and now u have the chainfire's Super SU installed in system/app and now open SuperSU update the su bin install busybox installer from playstore and optional
install xposed (Lollipop version) and install Xperia Xposed and others modules by yrself and tick xperia xposed module in xposed Modules section and next reboot phone and now you can choose new power menu with reboot option in xperia xposed app and now use the root to do the things u want such as browse page with orbot or Hola better internet apps or play cheat with game cheater apps .XD dont mind my reply are too ugly and peace,and if you think this is helpful for you or friends please give a Thanks Button.

E5633 m5 dual
this method it seems to be not working

Alex Tan Hao Nam said:
RootMaster (Chinese products)it works finely
http://www.romjd.com/jiaocheng/content/12500 -the link to the page
download link- http://soft.mgyun.com/files/product...350976/VRoot_1.8.5.15285_cid2040_44c47ecb.exe (skip it-click more information and click browse unsafe )
First install driver and tick USB debug in dev option, security unknown sources,screen sleep set to 10min and last install the root master u downloaded
Second start the program and tick i agree the terms beside the green button (green button-mean connect device )connect your M5 before click the button after u clicked the button it will try to connect your M5 and a green button also tick the i agree beside the green button and click the button
一键ROOT and sit on your chair and wait til done.
How you know your phone is rooted or not, first check did your device reboot by the program and after it check superuser aplication app is installed or no.If the App (permission manager)not suit to you ,download ES file manager from playstore and install SuperSU from playstore and use es file manager to backup SuperSU apk with the tool include in ES file manager next rename SuperSU apk in backup folder and hold it and move to system with right R/W permission (before move the apk go to ES file manager sidebar and find Root Explorer in Tools tab click the on off Root Explorer and grant root permission and click it again click Mount R/W label and make all paths to RW )and all done
the SuperSU apk rw permission in the system folder hold the supersu apk and click properties and click change permission with
rw-r-r
x=tick and o =untick
(xxo)
(xoo)
(xoo)
and after it reboot phone and open ES file manager go to system/app and delete the App (superuser came from the root program) and now u have the chainfire's Super SU installed in system/app and now open SuperSU update the su bin install busybox installer from playstore and optional
install xposed (Lollipop version) and install Xperia Xposed and others modules by yrself and tick xperia xposed module in xposed Modules section and next reboot phone and now you can choose new power menu with reboot option in xperia xposed app and now use the root to do the things u want such as browse page with orbot or Hola better internet apps or play cheat with game cheater apps .XD dont mind my reply are too ugly and peace,and if you think this is helpful for you or friends please give a Thanks Button.
Click to expand...
Click to collapse
I download the software(rootmaster) ,but it not work . I tryed many times....

http://forum.xda-developers.com/xperia-m5/general/unlock-bootloader-t3220927
Unlock bootloader is now possible.

Did anybody, other then the poster have success with this rootmaster?
And does this require the boot loader to be unlocked?

Doing a Google search for MT6795 (our chipset) shows that Mediatek has at some point released the sources of the kernel and baseband, but all the links to their github are dead.
If we can find someone who has pulled these sources before they were taken off and a developer who knows how to put them to use we might get custom recoveries, root and custom ROMs.

JudgeDread11 said:
Doing a Google search for MT6795 (our chipset) shows that Mediatek has at some point released the sources of the kernel and baseband, but all the links to their github are dead.
If we can find someone who has pulled these sources before they were taken off and a developer who knows how to put them to use we might get custom recoveries, root and custom ROMs.
Click to expand...
Click to collapse
I found this , is it what you were looking for?

Unfortunately I found some other info saying it e wasn't actually released but leaked. Which explains why it has been taken off again. These posts also said that those sources were incomplete and only applies to a xiuomi (or something like that) model and not to other phones.
And on top of that I am not a developer so I can't do anything with the sources myself. I just read the blogs and these sources seem to be the reason why we still don't have root.
So maybe a developer could have a look at the sources you found and verify if they are real and complete. If they are this might get us one step closer to open development for our device.

Try KingRoot

kingsasha said:
Try KingRoot
Click to expand...
Click to collapse
I did but it doesn't support our device. I put in a research request, but there aren't enough for them to research or device.
More requests might help, but I don't know how many they need.

I think our hopes of rooting M5 is definitely not going to happen....

firdyRAY said:
I think our hopes of rooting M5 is definitely not going to happen....
Click to expand...
Click to collapse
Why definitely?

JudgeDread11 said:
Why definitely?
Click to expand...
Click to collapse
Seems like no developer is working on it and the reception have been pretty poor.

http://forum.xda-developers.com/showthread.php?t=3309313
This works

Can anyone confirm a successfull root on this device?

kermanp said:
Can anyone confirm a successfull root on this device?
Click to expand...
Click to collapse
Kingroot can successfully root our device, but it requires a couple of tries. I had to run it 5 times before it was successful.

[TUT]How To Obtain A Little Freedom

[Tut]How To Systemless Root+Root+More!
This was fully tested on SM-G928A;Baseband:UCU2AOJ1 on 5.1.1
Just in case needed //SM-G928A\\ **Full Odin Restore G928AATT2AOJ1**
$<Download Mode & Odin Systemless Root Flash>
Requirements:
1.A Windows Computer
2.Your Phone Device SM-G92-0/5/8A
3.Odin 3.10.7
4.Kernel_Root_Android_5.1.1_AT&T_SamFirm.NET
5.USB Drivers(Most of the time if connect the phone to the computer using the usb cord that comes with the device it will install all of the drivers if your computer is connected to the internet.
____________________
Okay now assuming that everything has been required, we can begin.
Turn off your phone and open Odin with admin rights on the computer & connect your phone to the computer using the usb cable that comes with the phone.
On the phone now hold all of these following buttons down, Volume Down+Home Key+Power Soon after once you see the blue screen release those buttons and press the Volume Up key to enter Downloading Mode.
Now in Odin on the computer, it should have recognized your device now press the "AP" button and open up for example, "G928A_Kernel_Root_5.1.1_SamFirm.NET.tar.MD5" now just press start and sit back and relax and soon you will have Systemless Root!(Note your phone will reboot which is normal after the flash.
--------------------
#<Obtaining Root Access>
Requirements:
1.A Windows Computer
2.Your Phone Device SM-G92-0/5/8A
3.USB Drivers(Most of the time if connect the phone to the computer using the usb cord that comes with the device it will install all of the drivers if your computer is connected to the internet.
4.Flashed The Systemless Root
5.Kingo Root
6.Root Checker Cost $FREE
7.SuperSU Cost $FREE
8.BusyBox Cost $FREE
9.Developer Options (USB Debug)
____________________
Okay now assuming that everything has been required, we can begin.
Go into Settings>System>About Device & Enable Developer Options.(Keep tapping the "Build Number" category until it says Developer options have been enabled.
Connect your device with your usb that which comes with the phone on the computer. Open "Kingo ROOT" on your computer with admin rights, and once the program asks you to turn USB Debug on, go on your phone into Settings>System>Developer options and make sure it is enabled as well as usb debugging. Wait for kingo root to find your device and once found, it will ask you to either "Reroot,Root, or Remove Root, click "Reroot" then wait for it to start.(After it starts you should see on your phone the kingo root usb app pop-up and show the same thing you see on your computer)
After it is done it should confirm you have been rooted and will ask to donate.
Now you may exit out of the program on the computer and the phone and once out of the app and back on your phone, you will want to look in your app drawer for the kingo root "Superuser" and uninstall this. Then head on over to the playstore if haven't all ready and install "SuperSU" & "Busybox" if want to. Once have the SuperSU app open it and install the su binary updates with the "Normal" option not the recovery one since we don't have that.... & once done just press OK DO NOT REBOOT or you will bootloop and will have to use Odin to reflash your system of your phone to get it back working out of the box "state"
UPDATE Have a pc around and can still boot with root:
Yamaha169 said:
You can restart the device while rooted... but you have to have ADB to do so...
When you reboot ... you will get stuck at the ATT logo... at this point... plug your phone in to your pc...
Open up ADB (COMMAND WINDOW)
type in
ADB devices
until your device # appears in adb... (this can take a minute for your pc to find your phone) so don't panic
This means the phone is found...
From this point... type
ADB ROOT
ADB SHELL
YOU will now be inside the shell of the device with root permissions
Now type
setenforce 0
(MAKE SURE LOWERCASE just like seen. "setenforce 0" if do Setenforce 0 it won't be found.....)
This will set selinux to permissive ... allowing the phone to boot...
Someone with enough experience could probably create a selinux permissive stock kernel ... but I've contacted several developers with no response ...
Click to expand...
Click to collapse
Now open up the root checker app & click verify to see if you truly do have root.(You must grant root access so allow once it pops up.) Enjoy your root but never ever reboot.
UPDATE: How to Root If Possibly not allowing you to root!!!
Step one you will need to of downloaded "Android Studio
Step two you will now need to install all of the updates(Well that's what I did) inside the studio program.
Step three now locate 'program tools" which for me was located here: C:\Users\NameofComputer\AppData\Local\Android\android-sdk\platform-tools
Step four make a cmd.exe file to go in the platform-tools simply just clicking on the "start button" on windows and searching "cmd" then dragging the cmd file to the folder.(Rename it to something like ADB Root or something different than just cmd)
Step FIVE download the su binary which can be located HERE and place it in the "platform-tools" folder.
Step SIX now almost there. Open the cmd file(ADB Root.exe) and once opened, plug the phone into the computer with the cable that came with your phone.
Step Seven:^.^ now with the phone plugged in and the program start, type this command to make sure your device is found:
Code:
adb devices
and if found you will see your attached devices and if more than one or can't see your device, you can do
Code:
adb kill-server
command and it will restart adb.
Step Eight: MAGIC time lol now that your phone is connected and you can see it is indeed listed, type these commands as followed:
Code:
adb root
adb remount
adb push su /system/bin/su
adb shell
chown 0:0 /system/bin/su
chmod 6755 /system/bin/su
You don't really have to do the other commands after pushing su it's just for pre-caution.
Step Nine: Now do the following at the top and try to use the Kingo root once more and click root or reroot.
If this doesn't work try to press unroot and restart phone then try this again.
Also like down below I talk about if you did reboot before you unrooted, you can still unroot but sometimes it's tricky and it needs you to do the adb remount before will work so just remember that...
--------------------
$#$<UnRooting & Keeping Systemless Root So You Can Reboot & Reroot>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights)
3.SuperSU Cost $FREE
4.Root Checker Cost $FREE
____________________
This is very simple and easy to do, all you must do after every root and before every reboot is to go into "SuperSU" and go into the settings and scroll down until you see "Fully Unroot" and click that and once done verify with the root checker that you are indeed unrooted but still have adb shell and once done that you may freely reboot with no bootloop and then if want root once more just use "Kingo Root" on the computer to reroot once more.(I'm hoping someone will come out with an app that does the same thing and works so we don't need the computer anymore which would make it much easier..)
Edit/Update:
I found that if you maybe forgot to unroot before a reboot that you can still unroot without the need of going into odin and reflashing stock system just by connecting your phone to the computer via the usb that which comes with your phone and opening up Kingo Root and waiting for it to find your phone then click unroot and wait for it after you have unrooted and you will hear a sound which means it's fixed! So just force shutdown the device with pressing both: Volume Down+Home Button+Power then it will boot back up as normal!
-------------------- ____________________ -------------------- ____________________
~My Findings Through Long Research & Errors~:
<How to Fix Wifi Bug That Comes With Flashing Systemless Root>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights)
3.SuperSU Cost $FREE
4.BuildProp Editor Cost $FREE
____________________
On your phone open up the "BuildProp Editor".
click on the search button and search for "ro.securestorage.support=true" now once found change the =true to =false and save. Now you must reboot for it to take place but remember to UNROOT before you reboot.
Now doing this your wifi will stay connected and you no longer have to enter your password millions of times so it will be nicer to keep systemless root.
--------------------
<How to Enable AT&T Hotspot System FULLYApp>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Root Explorer Cost $3.99
4.NEW Modded TetheringProvision .apk Cost $FREE(Also can be found in this thread in attachments.
5.ADB Root cmd knowledge or Download SQLite Editor Cost $2.99
6.BuildProp Editor Cost $FREE
____________________
Okay my fellow members that stayed on 5.1.1 with me, this tut did once work but then at&t blocked me and it stopped working but now rejoice becase there is a bypass once more!!!
NEW WAY:
I'm not sure which worked so I'm gonna just tell you everything that I did...
1.I first rooted obviously
2.I found a new TetheringProvision.apk which I have uploaded down in the attachment and at the top.
3.I used adb root for this but this can also be done with sqlite editior so I'll explain both ways, first way will be the easy way the adb root...>>>
Step 1: Ensure you have the correct OEM drivers installed for your handset on the computer
Step 2: Download and install the necessary ADB drivers (v1.4.2)
Step 3: Enable USB debugging on your Android handset:
Go to Settings > About Device, and tap the build number 7 times or until you see 'You're now a developer' message.
Return to Settings > Developer options and use the toggle button to turn on USB debugging. Then tap OK button to accept the warning and continue.
Step 4:Connect your device to PC with original USB cable.
Step 5: Launch a command window on your Windows PC.
Step 6: Access ADB shell and run the following command:
adb shell now just type " settings put global tether_dun_required 0 " and enter.
________----------Now the sqlite way
Step 1:Go into sqlite editor and allow root rights...
Step 2: Locate "Settings Storage" and click on "Settings.db then click on "global"
Step 3:Locate tether_dun_required 0 and if not there add by clicking on the +
then fill out name as " tether_dun_required " >>And value as " 0 " and then save file and unroot then reboot.
Now then after all of that I downloaded the build.prop which I know you don't have to but it makes it easier for me to do so and probably for you too...
Step 1:Get build.prop editor from the playstore and open it to grant root rights.
Step 2:Click on the pencil icon on the top right where the search icon is.
Step 3: Scroll all the way down to an open line.(If not one make one.)
and put this in the line....>>> " net.tethering.noprovisioning=true " and then click the save button at the top right and then save it and unroot then reboot.
Then replacing the Tetherprovision.apk . >>>
Step 1: Download the NEW modded TetherProvision.apk at top or at bottom.
Step 2: get a root explorer and go to System/App/TetheringProvision
Step 3: Rename the actual TetheringProvision.apk to TetheringProvision.apk.bak
Step 4: in the same location, go into "arm64" and rename the TetheringProvision.odex to TetheringProvision.odex.bak
Step 5: Now locate the modded TetheringProvision.apk you've just downloaded and place it in System/App/TetheringProvision/ now should be two TetheringProvision, the TetheringProvision.apk.bak and the modded one, TetheringProvision.apk.
Step 6: change the property promissions of the tetheringprovision.apk to give it root rights by changing the promissions to look just like the actual one which is " rw-r--r-- "
Step 7: save and unroot then reboot!
Now youre wifi tether and usb should work!!! enjoy!
--------------------
<How to disable OTA & Security Notification>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Titanium Backup & Titanium Backup Pro License Cost $Free | $5.99
____________________
Open up titanium back with pro license and freeze these following apps:
1.SecurityLogAgent(This is that annoying notification that which comes with the systemless flash root that keeps annoying you to reboot and undo what you done.)
AT&T Software Update(This will make it so AT&T won't push any updates to your device anymore so no need to worry about installing an update ota and losing your root or something else like bootlooping.
And again, all of this sticks after you unroot and reboot!
___________________________________________
<How to Get Youtube RED (Sort of) FREE!>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.OGYoutube Cost $Free
Basically all you do here is download the modded sort of youtube app(OGYoutube) and install it then done! You now can download videos/music on the app and have access to run audio in the background plus NO ADS!!! (if there are I haven't seen any yet...)
Best part of this too since can't be used fttb, no need for XPOSED apk!
_____________________________
<How To Install Viper4android>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Fast Reboot
4.Soft Reboot
5.Viper4Android V2.3.4.0
6.Audio_Effect.Config
7.Titanium Backup & Titanium Backup Pro License Cost $Free | $5.99
8.IRS Impulse Response Sample files
9.Root Explorer Cost $3.99
~~~~~~~~~~~~~
To Read the tuts yourself than rather follow my tut, you may do so by following This Link & This Link
~~~~~~~~~~~~~~~~~~
Alright, I decided to do my own detail tut to make it much easier so follow me and you'll have viper4android in no time : )
So let's get begin, download if not already, the busybox,SuperSU,TitaniumBackup,Fast reboot,Soft Reboot, & Root explorer. Now having all that done open up Busybox and allow it root rights and you may wait for it to research for a smart intall, or just press install. Once you installed it in the default location System/xbin, click on the will be installed to location and choose System/bin and install it there too.(Not sure why but that's what the tut called for.)
Now let's download the folders for viper4android, go ahead and download Audio_Effect.Config.zip file,IRS Impulse Response Sample files, & the Viper4Android V2.3.4.0 folder.
Now open up the root explorer and unzip all that which is zipped up.(Which is all of the files;Audio_Effect.Config.zip file,IRS Impulse Response Sample files.zip, & the Viper4Android V2.3.4.0 folder.zip
)
Now once all are extracted, we will begin putting what is needed where.
Let's start off with the ViPER4Android_FX_A4.x (The actual name of the folder) you're gonna want to long press it and copy this folder. Once done, you're gonna want to paste this folder in System>Priv-app and make sure to change the permission of the .apk to 0644 rw-r--r-- & the FOLDER to 0755 rwxr-xr-x(The folder should have the same permissions as the other folders in that location.) which is inside the folder to give it root access which is 0644;rw-r--r-- and if not sure what root permission should look like, refer to this link Or Google what it looks like, then save/press ok.
Now go back to where you extracted your folders, and this time copy the "audio_effects.conf and go to System>etc and find and rename the actual audio_effects.conf to audio_effects.conf.bak and then paste the copied modded audio_effects.conf here & DONT FORGET change the permissions to give it root rights.
Now after all is done, open the app "Titanium Backup Pro" and look for and freeze these following applications: 1.Adapt Sound 4.0 & SoundAlive 3.0 now open the app "Soft Reboot (Root) and click yes you want to do a soft reboot. Then once back up(If want you can click the "Fast reboot app" to quickly refresh the system) and running you should see the viper app inside your app drawer. Open it and install the update/software when ask you to and once done it should ask for you to reboot just click on ok and then go out and back to the "Soft Reboot (Root) then do another soft reboot.
Now almost DONE!!! Once back up and running again, go to your root explorer again where you extracted the folders and grab the folder of "ViPER4Android and move it to your device storage ex; Storage/emulated/0 (It's where the download folder is and dcim folder is.. Then finally, go toSettings>Device>Sounds and notifications>Sound quality and effects and toggle on all of the listings[NOTE YOU MUST PUT EARPHONES IN FOR THESE TOGGLES TO SHOW]; UHQ Upscaler|SoundAlive+|Tube Amp Pro now you're done enjoy viper4android via editing the settings in the app.
Edit
You need to download SELinux Mode Changer and give root rights and just click on permissive mode and all done. Also might need to use compatible mode in the Viper4Android settings.
I found that this mod works with Pandora and Youtube app but not with google music or the default music app and not sure how to fix that....
__________________________________0
This is some more quick finds which you don't need a tut for just information I'd like to share so you all know.
I found out that you can use Titanium Backup Pro Cost $5.99 and freeze anything you want such as bloatware and that annoying notification that appears every time you reboot if have systemless root installed "SecurityLogAgent" and as long as you UNROOT before you reboot, it is safe and everything you froze stays frozen.
Now I haven't tried uninstalling any system apps so I wouldn't advise doing that unless you wanted to but I don't see the point except to free space up since you can just freeze anything and does the same thing except for freeing space....
I haven't been able to unlock the bootloader in my research and errors which probably never gonna happen anytime soon....
I also never found an app that could root the device yet without a computer....
And yeah that's it! I just was so happy to find out all of this and just had to share it with xda members which are on the same boat as me that has been wanting some "freedom" which now can have a piece of it. : )
If found these tuts to be helpful, feel free to hit thanks button and if want donate.

AngelRyu said:
Just gonna get right to it and be fast.
Odin Flash Kernel for systemless root.
obtain root
Download SuperSU
After rooted download some sort of buildprop editor and search for " ro.securestorage.support=true" Now change =true to =false. and save!
Now go into the superSU app and fully unroot then reboot and also keep adb shell root!
So you fix the wifi bug plus keep the adb shell so you can obtain root once more! Now we just need some app that can give root access with 1 click without needing a pc and this would work for me until we can actually reboot with root without it bootlooping anyways.... I still can't find a wifi tether app or a method that works for the at&t hotspot app though...
Click to expand...
Click to collapse
Question for clarification.
So current method for rooting g928a is this systemless root.
Question 1, will it brick my phone with this root if i reboot, because i read somewhere on here that the phone will just keep on rebooting.
You mention using superSU app to unroot to reboot. So basically I have to unroot with superSU whenever I want to reboot then reflash again to get root?

fuzmik said:
Question for clarification.
So current method for rooting g928a is this systemless root.
Question 1, will it brick my phone with this root if i reboot, because i read somewhere on here that the phone will just keep on rebooting.
You mention using superSU app to unroot to reboot. So basically I have to unroot with superSU whenever I want to reboot then reflash again to get root?
Click to expand...
Click to collapse
Yes you must unroot to remove the su binary so the system acts like nothing has happen. I use kingo root for windows and it works every time with root all you need to do is hit "root" or it may say "reroot" and works every time. I have been playing with this a lot trying to do things to get it to reboot with root but have failed so far.... I wish someone with more experience would approach this so we could have an app to use at least so we not have to use pc every time to reroot until we get the ability to keep root and reboot.
Kingo root can be found here : https://www.kingoapp.com/android-root.htm
and this works after flashing the kernel from odin. This was the only way I actually found to be able to get root was with this because manually pushing su just didn't work for me....

Thanks for being much clearer on the instructions and idoit proof. I was worried about the bootloop and I thought there was no exit strategy on this expensive phone until you mention reflash. With your extensive tinkering on this, did your knox security trip up?
If this is the only possible way, maybe the community could make some sort of app that if we have to shutdown or reboot the phone specifically for g928a, it will safely unroot it for us.
TASKER?!

Anyone know if this still works after taking the latest OTA a few days ago?

The problem is this isn't root. I restart my phone several times a day. There is no point especially if I can't get a custom OS. However, thanks for making the instructions clear. And for anyone who doesn't understand systemless root, it's temp root. When you reboot dmverity sees the false file structure and tries to rewrite and reverse the changes, effectively removing root. On the Note 5 AT&T for temp root you didn't have to unroot before reboot as it wouldn't boot loop, it would just remove root and let you continue on. So something in this version must be getting farther in breaking past dmverity if it's causing the OS to bootloop.

tonys.94 said:
The problem is this isn't root. I restart my phone several times a day. There is no point especially if I can't get a custom OS. However, thanks for making the instructions clear. And for anyone who doesn't understand systemless root, it's temp root. When you reboot dmverity sees the false file structure and tries to rewrite and reverse the changes, effectively removing root. On the Note 5 AT&T for temp root you didn't have to unroot before reboot as it wouldn't boot loop, it would just remove root and let you continue on. So something in this version must be getting farther in breaking past dmverity if it's causing the OS to bootloop.
Click to expand...
Click to collapse
I was wondering if maybe we could place SU somewhere else so we might could trick it to reboot with root but haven't done it yet and or maybe keep SU on the sdcard/storage and use the terminal on the phone to push su to xbin every reboot but just hoping maybe can get root working without making the stupid thing bootloop.... Like I said I been doing a lot of dumb stuff with my phone because I have been so disappointed in this phone with not having wifi tether at the most really but now that got that I'm much happier but I'm still on the research of keeping root and being able to reboot.
I won't be updating until something maybe for sure comes along with 6.0 I can wait because my galaxy s4 I had stayed on stock version forever because was able to do everything so was no need to update really.... Anyways yeah lol maybe someone greater or maybe my playing around will work. WE can only hope...
Oh yeah, to the other guy NO it did not trip knox doing any of the things I've done. which I wouldn't care if could unlock the bootloader lol...
Edit:
I've done all I can think of and didn't work to keep root on a reboot except it did keep root without bootloop with a soft reboot...
I found out to maybe later will add tut up top but for now I'd like to tell you or whoever, if you do bootloop due to not being able to access the su unroot in time, you can still connect your device with Kingo Root in that bootloop and can unroot to save you from having to reflash every time... Might have to reboot as soon as you hear the found from the unroot though.
Oh and on a factory reset everything sticks excepts what was frozen becomes unfrozen just fyi...
Yeah, that's all I can find so I'm done with it hope someone can help later on but I'm just happy with wifi tether so much : )

So what all can we do with this root
Thank you for your hard work. it's very much appreciated!!!
Will pay part of my bounty which is 50 dollars pay day!!
But, please reply. what all can we do with this root!?

O0Gjulian said:
So what all can we do with this root
Thank you for your hard work. it's very much appreciated!!!
Will pay part of my bounty which is 50 dollars pay day!!
But, please reply. what all can we do with this root!?
Click to expand...
Click to collapse
Hi, I didn't come up with anything but the fix for wifi bug and hotspot app.
I just made a very detail tut to help others, but thanks.
I would wait on the bounty to be paid to someone who can make it possible to keep root on and still be able to reboot.

So in theory with this method I can root, install a modified tetheringprovisions, unroot (as hotspot is the only feature I actually desire), and go about my business without worrying about bootlooping or knox being tripped? Feels too good to be true, but I want to believe.

Just a reminder that Android 6.0.1 is right around the corner. If you don't fully go back to stock before the upgrade it will not flash and could possibly wipe the data partition. Both the system and boot images need to be 100% stock.

antizombie said:
So in theory with this method I can root, install a modified tetheringprovisions, unroot (as hotspot is the only feature I actually desire), and go about my business without worrying about bootlooping or knox being tripped? Feels too good to be true, but I want to believe.
Click to expand...
Click to collapse
It's true, that's how my phone is rolling with frozen apps and the modded hotspot without root, but still the systemless root remains in the system but doesn't do anything with out a computer or applying the kingo root to true root it.
I haven't tested the adaway yet so idk if will work or not.... and I been wanting xpose to work to disable youtube ads but haven't tried that either. . I might root tonight and try out adway tho.
But yeah to your question you are 100% safe and will not change anything or trip anything; phone can reboot all it wants with no bootloops with the modded tether is what I'm trying to say lol .. .
Edit:
Yeah adaway works after unroot and reboot. . . But I decided not to use it because a lot of people us adfly and it wouldn't let me access the link so yeah.....
On another note I froze a lot of stuff and done a lot of things not sure which part caused it but it doesn't bother me because I don't use samsung pay but in the end I had to freeze samsung framework for samsung pay because it kept saying force closed but which again Idc about that app so no biggy to me : )

Was Samsung Pay crashing before you started freezing apps? I have yet to use Pay but I'd prefer to keep my options open if possible.

antizombie said:
Was Samsung Pay crashing before you started freezing apps? I have yet to use Pay but I'd prefer to keep my options open if possible.
Click to expand...
Click to collapse
Honestly, I'm not sure but it had to be either the freezing at&t update or securityagent because it seemed to happen after that... Or could be the hotspot mod but I didn't get any crashes until i froze those 2 apps so idk...

Package Disabler in play store freezes apps so what's the point?
Can you fully remove with TiBu and be safe unrooted?
---------- Post added at 03:55 PM ---------- Previous post was at 03:40 PM ----------
navalynt said:
Just a reminder that Android 6.0.1 is right around the corner. If you don't fully go back to stock before the upgrade it will not flash and could possibly wipe the data partition. Both the system and boot images need to be 100% stock.
Click to expand...
Click to collapse
Yeah and from what I've seen of the nightmares people have been having with their Note 5's on Marshmallow, I'm staying FAR away from it!

I can confirm this works. Sorta a pain to have to reroot but hey, It's progress. We may never have a custom ROM option or recovery, But this is the next big thing. If we can find a app that'll just reroot us. it's perfect. (somewhat) Just rooted a few minutes ago. Going to play around. More than likely I'll re flash stock and make a youtube video for anyone needing questions or wanting to see it be done.
And I lied.. So, My experience was weird. Lagging constantly and weird download issues with a fresh wipe.
I'm sadly gonna have to unroot and hope that a better method would come out.
):

O0Gjulian said:
I can confirm this works. Sorta a pain to have to reroot but hey, It's progress. We may never have a custom ROM option or recovery, But this is the next big thing. If we can find a app that'll just reroot us. it's perfect. (somewhat) Just rooted a few minutes ago. Going to play around. More than likely I'll re flash stock and make a youtube video for anyone needing questions or wanting to see it be done.
And I lied.. So, My experience was weird. Lagging constantly and weird download issues with a fresh wipe.
I'm sadly gonna have to unroot and hope that a better method would come out.
):
Click to expand...
Click to collapse
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Also @
joe3681 said:
Package Disabler in play store freezes apps so what's the point?
Can you fully remove with TiBu and be safe unrooted?
---------- Post added at 03:55 PM ---------- Previous post was at 03:40 PM ----------
Yeah and from what I've seen of the nightmares people have been having with their Note 5's on Marshmallow, I'm staying FAR away from it!
Click to expand...
Click to collapse
I can confirm freezing anything won't harm the system on a reboot after unrooting but not sure about removing the apps would be safe. I have however remove the youtube app and reinstalled it in play store and it didn't harm anything.

AngelRyu said:
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Thanks for helping me! I went ahead and flashed stock and followed your steps!
Working great now!
NOW, My next question... What difference would it make if I used package disabler pro VS TBU?
Wouldn't both of these apps freeze the processes? Or would it make a difference with root and SU access?
Click to expand...
Click to collapse

O0Gjulian said:
AngelRyu said:
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Thanks for helping me! I went ahead and flashed stock and followed your steps!
Working great now!
NOW, My next question... What difference would it make if I used package disabler pro VS TBU?
Wouldn't both of these apps freeze the processes? Or would it make a difference with root and SU access?
Click to expand...
Click to collapse
I'm not sure because I've never heard of that program, but I did buy it just now for about $1.89 and the activation keeps failing so I can't test it to see the difference but with titanium you can do everything not just freeze stuff but back up apps and their data and much more.
Titanium backup has been around for ages which is why I recommend it.
Click to expand...
Click to collapse

I use package Disabler. Works like TiBu without root. Only reason to root would be to fully remove apps but would it boot okay after?

Es File Explorer issue

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.