Related
Question:
I have used AAHK to downgrade my DHD and root it, but apparently I don't have write access on the system partition. I have succesfully installed AOSPX BR6 and 7 and am now running Nik 's Project X. Tried installing AdAway last night, but when it attempts to change the 'hosts' file (/system/etc/hosts), it fails. I have granted permissions with Superuser when asked for it and I can see it attempt twice before it fails on 'applying hosts file' ('copying of hosts file failed!').
When I try and create a folder or file in the root using ES Explorer, it also fails ('sorry, operartion failed').
HBOOT states 'S-OFF RL'.
What am I doing wrong?
Thx
Largamelion said:
Question:
I have used AAHK to downgrade my DHD and root it, but apparently I don't have write access on the system partition. I have succesfully installed AOSPX BR6 and 7 and am now running Nik 's Project X. Tried installing AdAway last night, but when it attempts to change the 'hosts' file (/system/etc/hosts), it fails. I have granted permissions with Superuser when asked for it and I can see it attempt twice before it fails on 'applying hosts file' ('copying of hosts file failed!').
When I try and create a folder or file in the root using ES Explorer, it also fails ('sorry, operartion failed').
HBOOT states 'S-OFF RL'.
What am I doing wrong?
Thx
Click to expand...
Click to collapse
Adaway seems to act funny with ICS roms sometimes it works other times it wont. Try wiping data on it in menu>manage apps. If that dont help try Adfree from the play store.
That rom has a r/w problem. Have you done the fix to solve it? It's stated in the OP. Use the backup fix. After that, when trying to update it may fail the firsr time, run it again.
Sent from a dream.
Wiping cache did not work. Adfree seems to work fine but doesn't block all ads.
I will look for the fix tomorrow and give it a go.
Thx
Found it, it was in the second OP under patches & mods, must 've missed it. Thx for pointing me in the right direction. Will try tomorrow.
Pfff ... can't even quote another post without 10 post of my own (and I hate image verification ... so hard to decipher).
Flashing busybox zip didn't work, but the backup/restore of the ROM did fix it. SU is updated now and AdAway works perfectly, seems to block all ads.
Thx again.
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
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.
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.
Hello ! And thanks to anybody who could possibly help me !
So, I installed magisk on my new oneplus 9 pro EU version. I got root and everything worked just fine...
But then I installed Viper4Android (drivers installation didn't work), so I moved on to james dsp audio drivers, which didn't work either.
I tried installing busybox as suggested in a forum (plus, I know that those can come handy at some point anyway), so I downloaded the busybox installer etc. Then I proceeded to a smart installation of busybox ! Didn't work and suggested to change directory from /system/xbin to /system/bin. I did that and it worked !
But steel issues with James Jsp audio drivers. Well, I open fx file explorer and went to the root folder > system `/system` and tried to create a 'xbin' folder (which didn't see to exist). It asked me to mount the system partition in read-write, thus I did.
Well... I rebooted my phone, and now it won't boot !...
Even TWRP won't do much as it says that there is 0 mb storage on the phone and cannot mount nor wipe anything.
Well, I booted on magisk image through fastboot and the phone boots this way, I get every app and config I did install on the phone ! Tried flashing the image again throughout magisk app... But when I restart the phone, it only boots on recovery mod !...
Tried going through the adb shell, and mounting the system partition in rw mode, but it fails and outputs :
mount: can't find /system in /proc/mounts
Feel free to ask for any additional information which I could share.
Thank you to anyone who could hand in some help !
Boot into the ROM with Magisk boot img and remove Viper and James. Are you on A11 or A12? I have a feeling BusyBox is causing the problem... I couldn't help much with that since I don't use it though.
Hey ! I actually just solved the issue like 10s ago ^^
Well first thank you soooo much for your help ! =D
I actually removed everything Viper or James related in a first time, but it didn't work...I tried reinstalling busybox in /system/xbin, but it failed haha
At some point, I just flashed the magisk image (the one I used to root the phone) with `fastboot flash boot magisk_C64_BA_Boot.img`
Now everything seems to work fine for me
I don't know how "dirty" it is what I've done tho ^^ probably some real Android developers are furious at me (*sorry ^^*)
Anyway, I let it here in case some other noobyas me faces the same issue.
Thank you again @luckylui
Maurpheus said:
Hey ! I actually just solved the issue like 10s ago ^^
Well first thank you soooo much for your help ! =D
I actually removed everything Viper or James related in a first time, but it didn't work...I tried reinstalling busybox in /system/xbin, but it failed haha
At some point, I just flashed the magisk image (the one I used to root the phone) with `fastboot flash boot magisk_C64_BA_Boot.img`
Now everything seems to work fine for me
I don't know how "dirty" it is what I've done tho ^^ probably some real Android developers are furious at me (*sorry ^^*)
Anyway, I let it here in case some other noobyas me faces the same issue.
Thank you again @luckylui
Click to expand...
Click to collapse
I'm glad you got it all figured out and didn't have to use MSM