[GUIDE] XPOSED on FIRE STICK - Fire TV Android Development

For those who use Xposed framework and would like to use it on the Fire stick ive managed to find a way how to install xposed v85 on Fire stick without a recovery.
Ive successfully installed it onto my own Fire Stick and a friends Fire stick.
Before you go on im not responsible for any bricking you might encounter.
Your more than welcome to wait for Rbox to release a custom recovery for the stick.
Please note, im only passing on what i found and tried, i did not make the tool.
Be very careful on what modules you install, again im not responsible for any bricks that might arise.
This obviously requires root. Im rooted with kingoroot.
The Fire sticks i tested where on 5.0.5 and 5.2.1.0
If your on a higher firmware version and are rooted use this guide and come back:
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298
Im explaining the guide from a windows pc and using the program ADBlink to transfer files, if your going to do this a different way please modify instructions to suit.
First download this:
http://s000.tinyupload.com/index.php?file_id=13649473132596741692
Next extract the folder to your desktop.
Open up ADBlink and connect to your Fire stick.
Upload the entire contents to your Fire sticks internal sd card, (make sure the files are going to /sdcard).
Head over to your Fire stick and install busybox, open busybox up and click install and wait till its finished.
Very important to click install inside of the Busybox app, if it wont let you exit the app and try again. You will have problems trying to run the script further in the guide
Install Terminal (not sure if this step is necessary as you will be using ADBlink's ADB Shell, but it was used when i found this info). Finally install Xposed installer, make sure you DO NOT open the Xposed apk yet, just click done.
Now if you used a different way to do this and the files are not in the /sdcard directory now is the time to move them to the /sdcard directory.
Back over to windows pc.
Click ADB Shell in ADBlink (you should have it still open and connected to your Fire stick).
Type the following commands:
su then hit enter.
sh /sdcard/installer.bin then hit enter.
Choose option 1 hit enter.
You will see alot of errors, ignore these and restart your Fire Stick.
It will take a while to boot and go to the optimizing apps screen and take about 10 minutes to boot up.
After its booted go ahead and check Xposed is installed !
Again im not responsible for anyone's Fire Stick and/or any modules you may try.
Again im not responsible for anyone's Fire Stick and/or any modules you may try.
Would be a good idea to list working modules you guys might try, give the community a heads up on whats working.
I will update the guide with modules i test and/or you guys report work.
*edit***
This also works on 5.2.1.0, was informed by user @metallica this worked on 5.2.1.0
Ive just got the time to test this on a brand new Fire Stick and can confirm it also.
Thanks @metallica
*edit
*Ive now successfully installed xposed v85 on 6 Fire Sticks*
Working Modules: (not limited to, just ones ive tried or been told work)
AdBlocker
Lucky Patcher
RootCloak
SpotifySkip
YouTube AdAway
RboxFireTvMods v1.4 *This mod will hide stock launcher without disabling settings* (finally got amazon screen launcher gone)
*update*
I should of included this information when I made the guide but in order to be able to select and activate any xposed mod in xposed menu after you have installed it using the fire stick remote alone will not allow you to navigate to the checkbox and put a tick into it.
In order to do this you must have an app to turn the remote into a mouse or some other way to manoeuvre the pointer.
The 3 ways I know of doing this are:
1/ Mouse toggle for fire tv. This is the easiest way but its a paid app. Download it from Google play and send it to your Fire TV.
2/ Droidmote server, agaim another paid app from Google play store but this must have Google play store/services installed as to allow for license check. There is a guide to follow to have this installed on here somewhere.
3/ Use Bluetooth mouse if you have one.
4/ Use an USB mouse with an OTG connector, the commands to start OTG are on AFTVnews.com, I have this command autorun at boot to enable otg after a restart (very handy).
There may be other ways but these are the omes ive had experience with and use myself.

As per usual I recommend that you wait for a working recovery system, if you install something from an Xposed Module & it bricks your Stick you will have no way back! Rbox is working on the recovery & a prerooted rom for the stick. Use at your own risk I would say.... this is just a helping hand & I'm not trolling your thread, just some newer users may not know the risks.

deanr1977 said:
As per usual I recommend that you wait for a working recovery system, if you install something from an Xposed Module & it bricks your Stick you will have no way back! Rbox is working on the recovery & a prerooted rom for the stick. Use at your own risk I would say.... this is just a helping hand & I'm not trolling your thread, just some newer users may not know the risks.
Click to expand...
Click to collapse
I think I have made my point already about the risks involved and im almost certain that anyone wanting xposed on the fire stick will already know the risks, as with anything involving root/xposed etc.
I have tested this myself and know it works and have listed some modules I have installed that work fine. As long as people stay away from modules that are definitely no use to fire stick and heavily moddify /system (im sure when reading the description of modules it will say in the write up about them) I cant see there being any problems.
I will continue to list any modules that I find are of any use to fire stick and list them here. If people want to wait for a custom recovery that is there choice, as ive pointed out in the guide. In my eyes everything you have said is already pointed out in the first post.
Also I will add as long as your Rooted and have a working adb connection either through WiFi or USB there is a chance you can come back from a bricked state with my other guide I put together.

sconnyuk said:
For those who use Xposed framework and would like to use it on the Fire stick ive managed to find a way how to install xposed v85 on Fire stick without a recovery.
Ive successfully installed it onto my own Fire Stick and a friends Fire stick.
Before you go on as i stated ive installed it onto 2 fire sticks i am not responsible for anyone's Fire stick bricking.
Your more than welcome to wait for Rbox to release a custom recovery for the stick.
Please note, im only passing on what i found and tried, i did not make the tool.
Be very careful on what modules you install, again im not responsible for any bricks that might arise.
This obviously requires root. Im rooted with kingoroot.
The Fire sticks i tested where on 5.0.5, i do not recommend this to be tried on 5.0.5.1 or 5.2.1.0.
AGAIN, this is for 5.0.5, ive not tested on any other firmware version !!!
If your on a higher firmware version and as the Fire sticks are still rootable you can hop over to my other guide on how to downgrade the Fire stick then come back afterwards:
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298
Im explaining the guide from a windows pc and using the program ADBlink to transfer files, if your going to do this a different way please modify instructions to suit.
First download this:
http://www.filedropper.com/xposedfirestick
or
http://www.megafileupload.com/76x5/Xposed_Fire_Stick.rar
Next extract the folder to your desktop.
Open up ADBlink and connect to your Fire stick.
Upload the entire contents to your Fire sticks internal sd card, (make sure the files are going to /sdcard).
Head over to your Fire stick and install busybox, open busybox up and click install and wait till its finished.
Very important to click install inside of the Busybox app, if it wont let you exit the app and try again. You will have problems trying to run the script further in the guide
Install Terminal (not sure if this step is necessary as you will be using ADBlink's ADB Shell, but it was used when i found this info). Finally install Xposed installer, make sure you DO NOT open the Xposed apk yet, just click done.
Now if you used a different way to do this and the files are not in the /sdcard directory now is the time to move them to the /sdcard directory.
Back over to windows pc.
Click ADB Shell in ADBlink (you should have it still open and connected to your Fire stick).
Type the following commands:
su then hit enter.
sh /sdcard/installer.bin then hit enter.
Choose option 1 hit enter.
You will see alot of errors, ignore these and restart your Fire Stick.
It will take a while to boot and go to the optimizing apps screen and take about 10 minutes to boot up.
After its booted go ahead and check Xposed is installed !
Again im not responsible for anyone's Fire Stick and/or any modules you may try.
Again im not responsible for anyone's Fire Stick and/or any modules you may try.
Would be a good idea to list working modules you guys might try, give the community a heads up on whats working.
I will update the guide with modules i test and/or you guys report work.
*edit
*Ive now successfully installed xposed v85 on 6 Fire Sticks*
Working Modules:
AdBlocker
Lucky Patcher
RootCloak
SpotifySkip
YouTube AdAway
RboxFireTvMods v1.4 (finally got amazon screen launcher gone)
Click to expand...
Click to collapse
Assume this will work on gen 1 AFTV box w OS5? (feel late to the game)
I have/still have xposed installed from when it was running OS3. Do I need to flash the uninstaller?
Also what version youtube are you using to get Youtube adaway to work? Thanks

KLit75 said:
Assume this will work on gen 1 AFTV box w OS5? (feel late to the game)
I have/still have xposed installed from when it was running OS3. Do I need to flash the uninstaller?
Also what version youtube are you using to get Youtube adaway to work? Thanks
Click to expand...
Click to collapse
Ive no idea if this works with gen 1 FTV. With the gen 1 FTV now having custom recovery you could flash the zip the normal way to have xposed on (Im sure you would flash the same version, arm 22?) please double check that first.
I put this guide together for use with the fire stick, as it has not got a custom recovery and we cant use the tool flashify.
I use the latest version of youtube downloaded directly from within the fire sticks interface.

sconnyuk said:
Ive no idea if this works with gen 1 FTV. With the gen 1 FTV now having custom recovery you could flash the zip the normal way to have xposed on (Im sure you would flash the same version, arm 22?) please double check that first.
I put this guide together for use with the fire stick, as it has not got a custom recovery and we cant use the tool flashify.
I use the latest version of youtube downloaded directly from within the fire sticks interface.
Click to expand...
Click to collapse
Well it's gen 1 but running OS5 so I'm pretty confident it'll work but was just hoping for confirmation (if not from you then anyone who may've tried it).
That's interesting that the adaway is working with amazon stock youtube. I used to sideload one from playstore and it had it's glitches because it was designed for tablets. Even the android tv version wasn't perfect but the ads got blocked at least.

KLit75 said:
Well it's gen 1 but running OS5 so I'm pretty confident it'll work but was just hoping for confirmation (if not from you then anyone who may've tried it).
That's interesting that the adaway is working with amazon stock youtube. I used to sideload one from playstore and it had it's glitches because it was designed for tablets. Even the android tv version wasn't perfect but the ads got blocked at least.
Click to expand...
Click to collapse
Since theres a custom recovery in place for fire tv 1 if I was you too minimise any risk id follow the guides on AFTVnews on installing TWRP recovery. Then at least if you run into problems you can restore it.
I have xposed on my gen 2 fire tv and im sure its 64bit version, but the gen 1 and fire stick are just normal arm version(sdk22 for 5.1)
Yes, the stock amazon youtube, whole better experience when ads are removed.

I followed the guide and successfully installed xposed and a few modules (AdBlocker, YouTube AdAway, and RboxFireTvMods).
Unfortunately, somewhere along the way I lost the stock launcher. My firestick is on OS v5.0.5 as per the guide and I also have FireStarter V.3.2.3 installed and running fine, so my firestick isn't useless. I can still launch FireTV Settings from the apps menu but FireTV Home is no longer there. I also made sure that it wasn't just hidden and oddly enough it is still listed under the hidden apps menu, although I have it unchecked so that it should be visible.
Is there some way that you are aware of to get the Stock launcher back without factory resetting?

skwirmy444 said:
I followed the guide and successfully installed xposed and a few modules (AdBlocker, YouTube AdAway, and RboxFireTvMods).
Unfortunately, somewhere along the way I lost the stock launcher. My firestick is on OS v5.0.5 as per the guide and I also have FireStarter V.3.2.3 installed and running fine, so my firestick isn't useless. I can still launch FireTV Settings from the apps menu but FireTV Home is no longer there. I also made sure that it wasn't just hidden and oddly enough it is still listed under the hidden apps menu, although I have it unchecked so that it should be visible.
Is there some way that you are aware of to get the Stock launcher back without factory resetting?
Click to expand...
Click to collapse
Rboxfiretv mods disables it.
You can still access the settings by the fire tv settings icon but if you want to see fire tv stock launcher you cant have Rboxfiretv xposed mod running.
Also very glad to see another user benefiting from this guide

sconnyuk said:
Rboxfiretv mods disables it.
You can still access the settings by the fire tv settings icon but if you want to see fire tv stock launcher you cant have Rboxfiretv xposed mod running.
Also very glad to see another user benefiting from this guide
Click to expand...
Click to collapse
Ahh, that was the problem. Thank you very much for the quick and informative reply!
I need to do some more research into that module. It appears from the reading that I should be able to use the stock launcher with it enabled since it has options for modifying what is displayed in the stock launcher. Of course this all should be addressed in that post. Its good to highlight that this may occur for other people though. Thanks again!

skwirmy444 said:
Ahh, that was the problem. Thank you very much for the quick and informative reply!
I need to do some more research into that module. It appears from the reading that I should be able to use the stock launcher with it enabled since it has options for modifying what is displayed in the stock launcher. Of course this all should be addressed in that post. Its good to highlight that this may occur for other people though. Thanks again!
Click to expand...
Click to collapse
Your welcome.
The mod is quite old and has not been updated in a while.
It is useful to disable the stock launcher, that is what I use it for, disabling certain things from the Amazon launcher is broke, im not sure if and when Rbox is updating it.
There is a guide I followed to remove some menu features before (photos, music etc) through adb commands.
The same thing can be accomplished by using Titanium backups freeze feature as long as you know which ones to disable.
Here are the ones I disabled on my fire stick:
package:com.amazon.precog
package:com.amazon.recess
package:com.amazon.whisperplay.contracts
package:com.amazon.bueller.photos
package:com.amazon.kindle.cms
package:com.amazon.client.metrics
package:com.amazon.device.software.ota
package:com.amazon.whisperlink.core.android
package:com.amazon.application.compatibility.enforcer
package:com.amazon.whisperplay.service.install
package:com.amazon.device.software.ota.override
package:com.amazon.bueller.music
This is info found at:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
Thanks to @Ludacrisvp

Well xposed is working on aftv1 box but youtube adaway (probably the only mod I care about) is not.
Which version of youtube is working? I have 1.2.0

KLit75 said:
Well xposed is working on aftv1 box but youtube adaway (probably the only mod I care about) is not.
Which version of youtube is working? I have 1.2.0
Click to expand...
Click to collapse
The latest one downloaded directly from Amazon.
I have the same set up on my fire tv 4k box with latest youtube and xposed youtube adaway and it works on that also.
I might add also make sure you have the latest xposed framework installed.

I can confirm, this Xposed installation work with 5.2.1.0 too, have successfull installed on my rooted Firestick in my Kitchen xD experimental tested *fg*
damn good work. @sconnyuk can you build a installer for fully working google play? Just a idea.
Gesendet von meinem LG-H850
EDIT: Adaway and Rbox Tools working without issue

MetaIIica said:
I can confirm, thisXposed installation work with 5.2.1.0 too, have successfull installed on my rooted Firestick in my Kitchen xD experimentsl tested *fg*
damn good work. @sconnyuk can you build a installer for fully working google play? Just a idea.
Gesendet von meinem LG-H850
Click to expand...
Click to collapse
Thats good news. I will test this myself and update the guide tomorrow.
As for Google playstore, that would be the icing on the cake, its what im trying to find an answer for at the moment.
The closest and next best thing I have is my Google account and Google services setup so im able to use my paid apps that do a license check.
Also using DroidMote on firestick is excellent.

morning, i install it on my firestick (same config) in the living room to see it will work again...
but i'm sure it will work
Gesendet von meinem LG-H850

Only way I can think of Google play store installation would be with flashify:
https://play.google.com/store/apps/...ery&pcampaignid=APPU_1_kWqFV-OkMevCgAa28oSIAg
With gapps version arm-5.1-pico from this page:
http://opengapps.org
BUT IVE NOT TESTED THIS.......
As im unsure if flashing this would brick the device.?

Has anyone tried using Flashfire?
http://flashfireapk.com
I'm just curious. It works on Fire Tablet running OS5 and I've ONLY used it on that. I'm not looking to possibly contribute to a bricked device, just wondering if it's been tried...
Feels like I'm beating a dead horse, but I can't understand why Youtube Adaway isn't working with Youtube 1.2.0 on my device. Pretty sure that's the latest version because there's no update available. According to others it works.
***What would be cool is to get Awesome Popup video to work fully with xposed. I was able to use it on OS3 but never could get it working right--open youtube video, have option of playing in a smaller window while I go to another app.
All I could do was get it to work with videos from within the awesome popup UI, which is no where near as good (much smaller selection, can't access your subscriptions, playlists, etc.)

KLit75 said:
Has anyone tried using Flashfire?
http://flashfireapk.com
I'm just curious. It works on Fire Tablet running OS5 and I've ONLY used it on that. I'm not looking to possibly contribute to a bricked device, just wondering if it's been tried...
Feels like I'm beating a dead horse, but I can't understand why Youtube Adaway isn't working with Youtube 1.2.0 on my device. Pretty sure that's the latest version because there's no update available. According to others it works.
***What would be cool is to get Awesome Popup video to work fully with xposed. I was able to use it on OS3 but never could get it working right--open youtube video, have option of playing in a smaller window while I go to another app.
All I could do was get it to work with videos from within the awesome popup UI, which is no where near as good (much smaller selection, can't access your subscriptions, playlists, etc.)
Click to expand...
Click to collapse
You could try the obvious, uninstall youtube disable xposed mod reboot, reinstall youtube from Amazon and re enable xposed mod.
As for flashfire, it won't work as it requires chainfires supersu.
Until a way tp swap kingoroot for supersu comes along then we can only wait for custom recovery.

second firestick running 5.2.1.0 in living room successfull xposed installed after small issue (newest kingo root from homepage must be installed)
think this with Kingo Root is a important information!
after rbox tools, stick start faster *fg*
Gesendet von meinem LG-H850

Related

Dell Venue 8 7840 - Here is a working Xposed framework

Credit for this goes to another user in another discussion forum. I just wanted to put it in a proper forum to help folks.
Please discuss your victories and defeats with your modules.
I currently use two modules: YouTube Ad Blocker and Greenify Experimental Settings. Test your Greenify settings one at a time. I have found that allowing hibernation of system processes causes an occasional bootloop. I think it's related to just one or two apps, so I'm trying to isolate those.
Xposed APK will be attached momentarily. I have to switch to a desktop.
Thanks!
jumpup said:
Credit for this goes to another user in another discussion forum. I just wanted to put it in a proper forum to help folks.
Please discuss your victories and defeats with your modules.
I currently use two modules: YouTube Ad Blocker and Greenify Experimental Settings. Test your Greenify settings one at a time. I have found that allowing hibernation of system processes causes an occasional bootloop. I think it's related to just one or two apps, so I'm trying to isolate those.
Xposed APK will be attached momentarily. I have to switch to a desktop.
Click to expand...
Click to collapse
I've been having issues with apps not staying hibernated (Greenify), and when I tried Xposed, my Venue 8 became unstable. I've installed your version; and so far, so good! I'm using Greenify Experimental and Amplify.
urquiagal said:
I've been having issues with apps not staying hibernated (Greenify), and when I tried Xposed, my Venue 8 became unstable. I've installed your version; and so far, so good! I'm using Greenify Experimental and Amplify.
Click to expand...
Click to collapse
@urquiagal same here. Glad to hear you are having success with Xposed as well.
I hope more interest in the Venue 8 7840 comes our way. This is an amazing system.
I spoke too soon ...
{sigh}
A couple of nights ago my Venue started bootlooping again, and it wouldn't stop until I uninstalled XPosed. I wanted so badly for this to work.
Is the xposed bootloop issue just a problem with the stock ROM, or does it happen with custom ROMs too? I've never flashed a non-stock ROM on any of my devices, but I think I'd be willing to try with the Venue if that would let me use Greenify's full functionality.
Slightly OT: is it possible to put a Venue 3830 into "safe mode"? Not wanting to do another factory reset (still a pain even with Titanium restore), it took me a LOT of bootloop cycles trying to uninstall xposed in 10-15 second intervals. (And why does the Venue app list only scroll one way?) I finally managed to put the StatsOf icon on the primary home screen, change my settings to open the app list first, sort the app list so that xposed was on the first "page", and long-press the xposed entry long enough to get the delete prompt before it looped again. Did a hard reboot at that point and the loop was gone.
urquiagal said:
{sigh}
A couple of nights ago my Venue started bootlooping again, and it wouldn't stop until I uninstalled XPosed. I wanted so badly for this to work.
Is the xposed bootloop issue just a problem with the stock ROM, or does it happen with custom ROMs too? I've never flashed a non-stock ROM on any of my devices, but I think I'd be willing to try with the Venue if that would let me use Greenify's full functionality.
Slightly OT: is it possible to put a Venue 3830 into "safe mode"? Not wanting to do another factory reset (still a pain even with Titanium restore), it took me a LOT of bootloop cycles trying to uninstall xposed in 10-15 second intervals. (And why does the Venue app list only scroll one way?) I finally managed to put the StatsOf icon on the primary home screen, change my settings to open the app list first, sort the app list so that xposed was on the first "page", and long-press the xposed entry long enough to get the delete prompt before it looped again. Did a hard reboot at that point and the loop was gone.
Click to expand...
Click to collapse
No custom Roms or development at all for this tablet yet.
urquiagal said:
{sigh}
A couple of nights ago my Venue started bootlooping again, and it wouldn't stop until I uninstalled XPosed. I wanted so badly for this to work.
Is the xposed bootloop issue just a problem with the stock ROM, or does it happen with custom ROMs too? I've never flashed a non-stock ROM on any of my devices, but I think I'd be willing to try with the Venue if that would let me use Greenify's full functionality.
Slightly OT: is it possible to put a Venue 3830 into "safe mode"? Not wanting to do another factory reset (still a pain even with Titanium restore), it took me a LOT of bootloop cycles trying to uninstall xposed in 10-15 second intervals. (And why does the Venue app list only scroll one way?) I finally managed to put the StatsOf icon on the primary home screen, change my settings to open the app list first, sort the app list so that xposed was on the first "page", and long-press the xposed entry long enough to get the delete prompt before it looped again. Did a hard reboot at that point and the loop was gone.
Click to expand...
Click to collapse
Leave the Xposed installed, but disable the Greenify module. That will likely solve it.
No custom ROMs are out yet. If you need it, the Dell 4.4.4 factory ROM is posted in Venue General (7840 ROM, that is)
What is the best root method you guys have used?
Venue 8 7840 only supports tethered CWM at this time
spotdog14 said:
What is the best root method you guys have used?
Click to expand...
Click to collapse
@spotdog14 - The only way to access a recovery and install SuperSU is through a tethered CWM recovery session made for Intel x86 Android tablets - Check this thread - http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
On another note: What do you folks think about creating a generic Venue 7840 "Tips and Tricks/What-We-Know-So-Far" thread and compile this info? I would be glad to lead this.
Thanks!
J.
spotdog14 said:
What is the best root method you guys have used?
Click to expand...
Click to collapse
@spotdog14 - BTW, your signature is beyond awesome
jumpup said:
On another note: What do you folks think about creating a generic Venue 7840 "Tips and Tricks/What-We-Know-So-Far" thread and compile this info? I would be glad to lead this.
Click to expand...
Click to collapse
That would probably be a good idea - it's all dotted around at the moment and mixed in with the other venue tablets.
anggusss said:
That would probably be a good idea - it's all dotted around at the moment and mixed in with the other venue tablets.
Click to expand...
Click to collapse
A couple of weeks ago, I put in a request for a dedicated Venue 7840 forum. Here is what I'm thinking:
Intro
Guides
[**]Tethered CWM Recovery + SuperSU
[**]Xposed module install
[**]Format microSD for support up to 512GB
Resources
[**]Dell 4.4.4 CWM Nandroid rooted image
[**]APKs of Dell-specific apps (Camera, Gallery, etc. - whatever will work as such)
Anything else?
jumpup said:
@spotdog14 - The only way to access a recovery and install SuperSU is through a tethered CWM recovery session made for Intel x86 Android tablets - Check this thread - http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
On another note: What do you folks think about creating a generic Venue 7840 "Tips and Tricks/What-We-Know-So-Far" thread and compile this info? I would be glad to lead this.
Thanks!
J.
Click to expand...
Click to collapse
Awesome, thanks! I had some problems finding the right ADB driver but it all worked out. I ended up using option 3 and got an error about too many links but it still booted fine into recovery and I was able to flash SU just fine. The first two apps to install here Adaway and xposed.
**Edit**
I have a question, this is obviously an older version of xposed and one of the modules I use is App Settings and it is saying it requires XposedBridge Version 52. Is it safe to update Xposed from inside the app or should I try downloading an older version of App Settings?
I would not recommend updating Xposed just yet. One of the modules that I use is YouTube adblock, and it complained about not having the latest framework. It still worked, though.
The reason I posted this Xposed (found on another Android x86 forum) was that when I tried the latest framework, I got an immediate bootloop.
Fortunately, though, if you have a problem, you can boot to Android Safe Mode and have enough time to remove Xposed. Boot the system while holding down both VolUp+VolDn, and it'll boot to Safe Mode.
RE: Adblock -> That's my first order of business. Install FDroid+Adblock. It is night-and-day performance boost on Android.
spotdog14 said:
Awesome, thanks! I had some problems finding the right ADB driver but it all worked out. I ended up using option 3 and got an error about too many links but it still booted fine into recovery and I was able to flash SU just fine. The first two apps to install here Adaway and xposed.
**Edit**
I have a question, this is obviously an older version of xposed and one of the modules I use is App Settings and it is saying it requires XposedBridge Version 52. Is it safe to update Xposed from inside the app or should I try downloading an older version of App Settings?
Click to expand...
Click to collapse
jumpup said:
I would not recommend updating Xposed just yet. One of the modules that I use is YouTube adblock, and it complained about not having the latest framework. It still worked, though.
The reason I posted this Xposed (found on another Android x86 forum) was that when I tried the latest framework, I got an immediate bootloop.
Fortunately, though, if you have a problem, you can boot to Android Safe Mode and have enough time to remove Xposed. Boot the system while holding down both VolUp+VolDn, and it'll boot to Safe Mode.
RE: Adblock -> That's my first order of business. Install FDroid+Adblock. It is night-and-day performance boost on Android.
Click to expand...
Click to collapse
That is kind of what I figured. I just wish I could get App Settings to work.
Also it appears I cannot get Xposed GEL Settings to work correctly either. I'm going to try to uninstall it and reinstall it later today to see if that makes any difference.
I haven't tried Xposed GEL yet. Let me know how that goes. What I figure we could do in the compiled 7840 info thread is include what's been tried and a "Yes/No/Kinda" section of how apps/modules are performing.
spotdog14 said:
That is kind of what I figured. I just wish I could get App Settings to work.
Also it appears I cannot get Xposed GEL Settings to work correctly either. I'm going to try to uninstall it and reinstall it later today to see if that makes any difference.
Click to expand...
Click to collapse
jumpup said:
I haven't tried Xposed GEL yet. Let me know how that goes. What I figure we could do in the compiled 7840 info thread is include what's been tried and a "Yes/No/Kinda" section of how apps/modules are performing.
Click to expand...
Click to collapse
Sounds good to me. After reinstalling GEL settings worked fine. I'm thinking about applying gravity box next. I miss my customizable quick toggles.
Update, Gravity Box KK works, but you cannot disable or move the quick access settings for:
My Dell
Sound
Dell Cast
But from my brief test everything else seems to be working fine.
@spotdog14 - Thank you for posting your findings. I will roll this into the general thread.
Som sad news, though. I traded in my Venue 7840 for a Galaxy Note 10.1 2014 Edition. I really needed the pen capability. Nonetheless, I have the info I need to set up the 7840 general forum.
I am currently uploading Dell's factory 4.4.4 image as Nandroid. It should be pre-rooted, but if not, use the tethered CWM to install the latest SuperSU.
spotdog14 said:
Update, Gravity Box KK works, but you cannot disable or move the quick access settings for:
My Dell
Sound
Dell Cast
But from my brief test everything else seems to be working fine.
Click to expand...
Click to collapse
I used this tool to install xposed from day one and has worked great for me the past couple months. It's 2.6.1
http://forum.xda-developers.com/xposed/modules/tool-installer-xposed-installer-zenfones-t2983589
Worked like a charm.

Kindle Fire HDx 7" OS 4.5.3 root?

I am reading the site the last couple of hours, and I can't find a step by step for Root. I can't Enable ADB because it is not there! So I guess the method for HD is not working? Please help me and sorry if it was asked, but I can't find it,
You can't root 4.5.3, you have to roll back to 3.2.8 (and root it, plus you can install Safestrap on that build and use the Nexus 1.0.1 ROM which is Jelly Bean but that's as far as you go) and then upgrade to 4.5.2 which is still rootable with the CVE exploit.
But with 4.5.3 you're stuck, and with 4.5.4 around the corner there's a chance that update could totally block all rooting period so, be aware of this - stay away from 4.5.4 (when it becomes available) if there's even a potential update or as long as you can, and within reason roll back to 3.2.8 then bump it to 4.5.2, root that build then disable the OTA capability and go from there.
To get ADB, go into Settings, Device, Serial Number - Tap Serial Number 7 times which gives you the Developer Options (just like tapping the build number in normal Android does). Once you have them (go back a menu) you can then enable ADB from there.
But again, the recommendation is to get off 4.5.3 (at least it's my recommendation if you want any possible root at all) as soon as possible.
The instructions are here, I just got an HDX on Wednesday and I've learned quite a bit in the past 48 hours or so (no that doesn't mean I've been lurking/reading/posting for the past 48 hours, of course). It's not that tough, but it does require actual reading with comprehension and not just skimming topics or barely reading the posts in threads.
atti_mac said:
I am reading the site the last couple of hours, and I can't find a step by step for Root. I can't Enable ADB because it is not there! So I guess the method for HD is not working? Please help me and sorry if it was asked, but I can't find it,
Click to expand...
Click to collapse
In addition to the comments from br0adband be aware adding gapps (Google Play Services, Store, etc) to Fire OS can be problematic as you can not completely purge the device of Amazon equivalents. It works but not without some annoyances. At present there is a broader issue with the current release of Google Play Services (v7.3)that is impacting a wide swath of devices including many rooted Kindles. Google will likely issue a fix but they do not seem in any hurry to do so.
A rooted HDX running Fire OS 4.x isn't like other Android devices. Root helps you get around some Amazon annoyances and add addition capabilities but it's nothing like pure Android. Even simple things like changing wallpaper can be a hassle.
If you want to move forward w/root see this post for further instructions.
Davey126 said:
In addition to the comments from br0adband be aware adding gapps (Google Play Services, Store, etc) to Fire OS can be problematic as you can not completely purge the device of Amazon equivalents. It works but not without some annoyances. At present there is a broader issue with the current release of Google Play Services (v7.3)that is impacting a wide swath of devices including many rooted Kindles. Google will likely issue a fix but they do not seem in any hurry to do so.
A rooted HDX running Fire OS 4.x isn't like other Android devices. Root helps you get around some Amazon annoyances and add addition capabilities but it's nothing like pure Android. Even simple things like changing wallpaper can be a hassle.
If you want to move forward w/root see this post for further instructions.
Click to expand...
Click to collapse
It said : "Put roolback file into the Internal storage folder of your Kindle." !
I downloaded a "mod-update-kindle-thor-13.3.2.8_user_713328020" folder and i have no idea where I have to copy it. I just did it to a main folder put it between the "Kindle" and "Movies" but it doesn't do anything when I want to do an update. Without wifi, didn't even start.
UPDATE, just realized i had to copy a "bin" file not a folder version. So now is downgrading. How to root 3.2.8? should i update to 4.5.2 first and root or root the 3.2.8?
update
I was able to downgrade , and upgrade to 4.5.2, rooted, and I was able to follow the other guides to disable OTA updates.
But when I try to install the Google play apps, it said at step 1 "aquire the GApps.."http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550
So when I followed the link , it takes me here :http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
And Step 2 Boot into recovery to able to install Zip file....
I can't boot in recovery, the step by step guide said power on, and when i will see the "kindle fire" hold the power till turns blue and let it go. Mine newer turns blue just orange and if I let the power go nothing happen.
Will you guys help? I am so close!
Do not do the recovery instructions. Grab the file from the link and follow the instructions from this forum. If you are rooted, be very careful with stock recovery.
The spoiler is instead of installing the zip, unzip it and copy many of the files to their respective folders. Skip priv/app/ setupwizard.apk and priv/app/prebuiltgmscore.apk. install the gms core as a normal app and you are good to go... almost. Look around the HDX general threads for a fix to prevent google play services updating themselves.
Good luck
Sent from my KFTHWI using Tapatalk
a chinese root toolkit named Kingroot seems able to support Fire OS 4.5.3 now. Several guys tested it and succeeded.
but it contians a su manager named KingUser from the same company. if anybody can install SuperSU instead, you can have a try.
some one dont understand chinese? PM me, i can help.
BTW. Personally, I never recommend Chinese APPs from chinese companies. They use the APPs/Softwares to play a role as thief to steal your information, contacts, maybe more. And they always ask for more permissions.
For economic benefits, they can do anything.
FotixChiang said:
a chinese root toolkit named Kingroot seems able to support Fire OS 4.5.3 now. Several guys tested it and succeeded.
but it contians a su manager named KingUser from the same company. if anybody can install SuperSU instead, you can have a try.
some one dont understand chinese? PM me, i can help.
BTW. Personally, I never recommend Chinese APPs from chinese companies. They use the APPs/Softwares to play a role as thief to steal your information, contacts, maybe more. And they always ask for more permissions.
For economic benefits, they can do anything.
Click to expand...
Click to collapse
FYI recieved OTA 4.5.4 and it breaks root. Kingroot 4.1 no longer works.
koda1789 said:
FYI recieved OTA 4.5.4 and it breaks root. Kingroot 4.1 no longer works.
Click to expand...
Click to collapse
Must be a lucky day that I've just rooted 4.5.3 with Kingroot and disabled OTA today :fingers-crossed:
koda1789 said:
FYI recieved OTA 4.5.4 and it breaks root. Kingroot 4.1 no longer works.
Click to expand...
Click to collapse
Unbelievable. Had an HDX 7" with 13.3.1.0, rooted, was ready to unlock bootloader and install CM12. Received a surprise visit, and when I got back to my desk I was on 4.5.4...
Bad day...
Well, it could be worse, you could have gotten bricked during the update.
Davey126 said:
In addition to the comments from br0adband be aware adding gapps (Google Play Services, Store, etc) to Fire OS can be problematic as you can not completely purge the device of Amazon equivalents. It works but not without some annoyances. At present there is a broader issue with the current release of Google Play Services (v7.3)that is impacting a wide swath of devices including many rooted Kindles. Google will likely issue a fix but they do not seem in any hurry to do so.
A rooted HDX running Fire OS 4.x isn't like other Android devices. Root helps you get around some Amazon annoyances and add addition capabilities but it's nothing like pure Android. Even simple things like changing wallpaper can be a hassle.
If you want to move forward w/root see this post for further instructions.
Click to expand...
Click to collapse
Watch this video to fix that issue with Google Play Services...
[Fix] - Play store and COC not Working on Kindle …: https://youtu.be/7RxuP9X3Mgo
Ali Ejea Mc said:
Watch this video to fix that issue with Google Play Services...
[Fix] - Play store and COC not Working on Kindle …: https://youtu.be/7RxuP9X3Mgo
Click to expand...
Click to collapse
Thanks.
Another option now exists for locked devices that involves replacing FireOS with Nexus which natively supports the Play store. See: http://forum.xda-developers.com/showthread.php?t=3137840

I think I have a playground.

I now have a second Thor, and it's on 3.0.5. What kind of things can I do to this?
fdigl said:
I now have a second Thor, and it's on 3.0.5. What kind of things can I do to this?
Click to expand...
Click to collapse
Some suggestions:
-root and block OTA with HDX toolkit (link)
-install TWRP
-update bootloader to 3.2.3 (link)
-ROMS: Nexus 2.0.5 or CM11
-optional: unlock bootloader (thread)
-ROMS: as above plus CM12
Unlocking the bootloader is the most involved but opens additional options and (more importantly) offers a more robust recovery capability should things go wrong.
Most important thing you can do now is 1) stay off WiFi until OTA is effectively blocked; and 2) read, read and read some more. You've likely seen numerous 'brick' posts. Most were the result of rushed actions and/or incomplete research. Do your homework and ask questions along the way. Good luck.
Davey126 said:
Some suggestions:
-root and block OTA with HDX toolkit (link)
-install TWRP
-update bootloader to 3.2.3 (link)
-ROMS: Nexus 2.0.5 or CM11
-optional: unlock bootloader (thread)
-ROMS: as above plus CM12
Unlocking the bootloader is the most involved but opens additional options and (more importantly) offers a more robust recovery capability should things go wrong.
Most important thing you can do now is 1) stay off WiFi until OTA is effectively blocked; and 2) read, read and read some more. You've likely seen numerous 'brick' posts. Most were the result of rushed actions and/or incomplete research. Do your homework and ask questions along the way. Good luck.
Click to expand...
Click to collapse
Thanks! In Xposed Installer, the framework section is just blank white. No buttons or dropdowns, just white. Everything else in the app appears normal. I can't install the framework for HDXposed.
fdigl said:
Thanks! In Xposed Installer, the framework section is just blank white. No buttons or dropdowns, just white. Everything else in the app appears normal. I can't install the framework for HDXposed.
Click to expand...
Click to collapse
HDXposed is not on the list. There is no need for this module as it has long been depreciated and of questionable value given more current alternatives. Strongly suggest not installing stuff or traveling your own path. Also recommend uninstalling Xposed framework and any other 'system' level hacks/utilities until your devices is otherwise upgraded and stable. Just asking for trouble ...
While I have the pulpit don't mess with build.prop or any system file other than OTAcerts (even that can be avoided). If you are following a guide that indicates one/both should be modified you're in the wrong place. Post a question; someone will help you get back on track.
Davey126 said:
HDXposed is not on the list. There is no need for this module as it has long been depreciated and of questionable value given more current alternatives. Strongly suggest not installing stuff or traveling your own path. Also recommend uninstalling Xposed framework and any other 'system' level hacks/utilities until your devices is otherwise upgraded and stable. Just asking for trouble ...
While I have the pulpit don't mess with build.prop or any system file other than OTAcerts (even that can be avoided). If you are following a guide that indicates one/both should be modified you're in the wrong place. Post a question; someone will help you get back on track.
Click to expand...
Click to collapse
Oh, thanks for the info!
Anyways, I have Android Market working but Play Store just crashes while opening. I have the same version of Play Store running on the older Thor, but not this one. It just stops working, but behind the dialogue I can see another one under it, likely the Play Store agreement, but it closes when I close the stopped working dialogue. This makes Play Store unusable.
fdigl said:
Oh, thanks for the info!
Anyways, I have Android Market working but Play Store just crashes while opening. I have the same version of Play Store running on the older Thor, but not this one. It just stops working, but behind the dialogue I can see another one under it, likely the Play Store agreement, but it closes when I close the stopped working dialogue. This makes Play Store unusable.
Click to expand...
Click to collapse
Play Store works great on the three roms previously mentioned while various issues keep cropping up using it with Fire OS. I suggest you flash TWRP, the 3.2.3 bootloader update and Nexus 2.05. Each is relatively low risk (given your favorable starting point; many would love to have that device!) if you follow directions. In the end I think you will be much happier with the overall experience. Perhaps someone else can help if you want to continue with Fire OS 3.x and sideload gapps.
Davey126 said:
Play Store works great on the three roms previously mentioned while various issues keep cropping up using it with Fire OS. I suggest you flash TWRP, the 3.2.3 bootloader update and Nexus 2.05. Each is relatively low risk (given your favorable starting point; many would love to have that device!) if you follow directions. In the end I think you will be much happier with the overall experience. Perhaps someone else can help if you want to continue with Fire OS 3.x and sideload gapps.
Click to expand...
Click to collapse
I have Safestrap 3.72 on there, does that count as TWRP? Despite this, I'd prefer to keep Fire OS on here.
To get gapps working on fire is, look at the version of google play services. Some people have no problems. I am running 7.0.99 I think.
fdigl said:
I have Safestrap 3.72 on there, does that count as TWRP? Despite this, I'd prefer to keep Fire OS on here.
Click to expand...
Click to collapse
Nope. TWRP in Safestrap does not operate in 'native' mode. If you prefer Fire OS then your options are limited:
- create another slot in Safestrap and install Nexus 1.0.5 (note different version number) which offers full Play Store support. Make sure you preserve your existing copy of Fire OS in the base slot; bad things happen if it gets trashed. You can then toggle between Fire OS and Nexus although the two roms can not share applications (they operate independently)
- continue wrestling Play Store (and other Google components) on Fire OS 3.x.
- permit your device to upgrade to the version 4.x of Fire OS which is a modest improvement over 3.x. You will be faced with the same headaches getting Google Components to play nice with Fire OS but you will likely receive better community support. Please note this is a one way trip. Once you go beyond 3.2.6 you can not make the modifications required to run most non-Amazon roms like CM11/12.
Davey126 said:
Nope. TWRP in Safestrap does not operate in 'native' mode. If you prefer Fire OS then your options are limited:
- create another slot in Safestrap and install Nexus 1.0.5 (note different version number) which offers full Play Store support. Make sure you preserve your existing copy of Fire OS in the base slot; bad things happen if it gets trashed. You can then toggle between Fire OS and Nexus although the two roms can not share applications (they operate independently)
- continue wrestling Play Store (and other Google components) on Fire OS 3.x.
- permit your device to upgrade to the version 4.x of Fire OS which is a modest improvement over 3.x. You will be faced with the same headaches getting Google Components to play nice with Fire OS but you will likely receive better community support. Please note this is a one way trip. Once you go beyond 3.2.6 you can not make the modifications required to run most non-Amazon roms like CM11/12.
Click to expand...
Click to collapse
It seems that I got Play Store 4.6.17 to work, but I'm unable to download anything (will spam ANRs). In HDXposed, did the content provider fix have to do with any of this? I have it on the older Thor, but not on the new one. If it does, what would be the alternative way of applying that fix?
EDIT: Any version of Play Store is working, just unable to download/install from the store.
lekofraggle said:
To get gapps working on fire is, look at the version of google play services. Some people have no problems. I am running 7.0.99 I think.
Click to expand...
Click to collapse
I know how to get GApps working, it's just Play Store that's acting up.
fdigl said:
I know how to get GApps working, it's just Play Store that's acting up.
Click to expand...
Click to collapse
I meant play store. That is the problem most people are having. Take a look at the two threads in the general section.
Sent from my KFTHWI using Tapatalk
fdigl said:
Thanks! In Xposed Installer, the framework section is just blank white. No buttons or dropdowns, just white. Everything else in the app appears normal. I can't install the framework for HDXposed.
Click to expand...
Click to collapse
What version of Xposed Installer are you using?
Davey126 said:
HDXposed is not on the list. There is no need for this module as it has long been depreciated and of questionable value given more current alternatives. Strongly suggest not installing stuff or traveling your own path. Also recommend uninstalling Xposed framework and any other 'system' level hacks/utilities until your devices is otherwise upgraded and stable. Just asking for trouble ...
While I have the pulpit don't mess with build.prop or any system file other than OTAcerts (even that can be avoided). If you are following a guide that indicates one/both should be modified you're in the wrong place. Post a question; someone will help you get back on track.
Click to expand...
Click to collapse
EncryptedCurse said:
What version of Xposed Installer are you using?
Click to expand...
Click to collapse
I tried the latest, and v32 - the one that worked on my Thor on 3.2.5. The tablet in question is on 3.0.5, but installed TWRP and the 3.2.3 boot loader zip was flashed.

Confused: from partially working Fire OS to 'proper' ROM ... ?

Hi there. I'm really confused about how to proceed and would appreciate some help.
I have a Kindle Fire HDX 7 (3rd Gen) on which I would like to wipe the Fire OS, and replace it with a working, functional Android ROM. I have some basic competence with installing software, flashing phones, etc., but am by no means an expert. I have both Windows & Linux PCs with which to connect.
A year or so ago I tried to get the tablet working with Google Apps, etc.. I can't remember precisiely what I did (!), but I think I used TWRP, I rolled back the operating system to 4.5.2, turned off the updates, and installed a Google Apps piece of software. The tablet then worked reasonably well, but not great. By that I mean I could web browse, and download and use some apps from the Play Store, but lots of stuff didn't work preoperly. At some time since then, the tablet decided it no longer wanted to install/update from the Play Store, and more of the apps have stopped working. I can still web browse.
TBH, I've got to the point where if I can't completely replace the OS then I think I'm just going to stop using it.
What steps should I take to get a 'proper' ROM working on the tablet?
Thanks very much in advance for any help,
Aaron
alhroot said:
Hi there. I'm really confused about how to proceed and would appreciate some help.
I have a Kindle Fire HDX 7 (3rd Gen) on which I would like to wipe the Fire OS, and replace it with a working, functional Android ROM. I have some basic competence with installing software, flashing phones, etc., but am by no means an expert. I have both Windows & Linux PCs with which to connect.
A year or so ago I tried to get the tablet working with Google Apps, etc.. I can't remember precisiely what I did (!), but I think I used TWRP, I rolled back the operating system to 4.5.2, turned off the updates, and installed a Google Apps piece of software. The tablet then worked reasonably well, but not great. By that I mean I could web browse, and download and use some apps from the Play Store, but lots of stuff didn't work preoperly. At some time since then, the tablet decided it no longer wanted to install/update from the Play Store, and more of the apps have stopped working. I can still web browse.
TBH, I've got to the point where if I can't completely replace the OS then I think I'm just going to stop using it.
What steps should I take to get a 'proper' ROM working on the tablet?
Thanks very much in advance for any help,
Aaron
Click to expand...
Click to collapse
There's a good chance you can replace FireOS with CM11 or Nexus, two popular ROMs that are well suited to this device. First order of business is to assess the current status of your device. What version of FireOS is currently installed? It it reasonably stable? Many times laying Google components over FireOS creates other issues that can interfere with components needed to support an alternative rom.
Davey126 said:
There's a good chance you can replace FireOS with CM11 or Nexus, two popular ROMs that are well suited to this device. First order of business is to assess the current status of your device. What version of FireOS is currently installed? It it reasonably stable? Many times laying Google components over FireOS creates other issues that can interfere with components needed to support an alternative rom.
Click to expand...
Click to collapse
Davey, thanks for the reply.
I've just checked, and the Fire OS version running on the tablet is 4.5.2.
The device is stable.
alhroot said:
Davey, thanks for the reply.
I've just checked, and the Fire OS version running on the tablet is 4.5.2.
The device is stable.
Click to expand...
Click to collapse
Next step is to allow the device to update to FireOS 4.5.5.1. While you could get by with 4.5.2 the newest rom builds require low level (kernel) components that get installed with 4.5.5.1. Replacing FireOS is the only way to get these pups on an HDX; there is no way to install them separately.
To obtain 4.5.5.1 you need to unblock OTA updates which typically involves renaming a file back to its original ID using a tool such as ES File Explorer. Search for a file starting with 'DeviceSoftwareOTA' which is typically located in /system/priv-app/. It will probably be called 'DeviceSoftwareOTA.bak' or something similar. Rename that to 'DeviceSoftwareOTA.apk', reboot and check for updates. You will loose root if 4.5.5.1 is successfully found/installed but you can get it back fairly easily.
FWiW - There are other methods of blocking OTA updates such as renaming the otacerts.zip file. That approach is less common on this device.
Davey126 said:
Next step is to allow the device to update to FireOS 4.5.5.1. While you could get by with 4.5.2 the newest rom builds require low level (kernel) components that get installed with 4.5.5.1. Replacing FireOS is the only way to get these pups on an HDX; there is no way to install them separately.
To obtain 4.5.5.1 you need to unblock OTA updates which typically involves renaming a file back to its original ID using a tool such as ES File Explorer. Search for a file starting with 'DeviceSoftwareOTA' which is typically located in /system/priv-app/. It will probably be called 'DeviceSoftwareOTA.bak' or something similar. Rename that to 'DeviceSoftwareOTA.apk', reboot and check for updates. You will loose root if 4.5.5.1 is successfully found/installed but you can get it back fairly easily.
FWiW - There are other methods of blocking OTA updates such as renaming the otacerts.zip file. That approach is less common on this device.
Click to expand...
Click to collapse
Bang on.
I renamed the file from '.bak' to '.apk', rebooted, and did a couple of updates cycles.
I'm now on FireOS 4.5.5.1 ...
alhroot said:
Bang on.
I renamed the file from '.bak' to '.apk', rebooted, and did a couple of updates cycles.
I'm now on FireOS 4.5.5.1 ...
Click to expand...
Click to collapse
Fantastic! Next step is to root with KingRoot (apk or tethered version). After that the good stuff starts happening. Sorry for piecemealing out details; I find it works better in the absence of an A to Z guide.
Be out-of-pocket for a few hours; will look for your response later.
Davey126 said:
Fantastic! Next step is to root with KingRoot (apk or tethered version). After that the good stuff starts happening. Sorry for piecemealing out details; I find it works better in the absence of an A to Z guide.
Be out-of-pocket for a few hours; will look for your response later.
Click to expand...
Click to collapse
Okay, I think that's all good ... Kingroot apk downloaded & installed, device rooted, turned on root explorer in ES File Explorer as a test: prompted for permission.
Davey, thanks again for your help.
So now for the good stuff ... ??? :good:
alhroot said:
Okay, I think that's all good ... Kingroot apk downloaded & installed, device rooted, turned on root explorer in ES File Explorer as a test: prompted for permission.
Davey, thanks again for your help.
So now for the good stuff ... ??? :good:
Click to expand...
Click to collapse
Excellent. Next step is to install Safestrap 4.0.1 which provides a pseudo recovery environment that supports the installation of custom roms. It looks a lot like TWRP (but isn't). You can snag the app from here; be sure to select the appropriate format. Once installed launch the app and install Safestrap recovery which is the component that does the heavy lifting.
Important: Once Safestrap recovery is installed never (never!) attempt a 'factory reset' - either from the stock recovery menu or from within FireOS. Doing so will brick the device with no possible recovery.
Now reboot. You'll notice a new screen that has a couple options at the bottom. Select the option that launches Safestrap recovery. Take a look around but don't change anything. When ready return to the home screen and then go into the backup section. Take a backup of your current FireOS installation (selection all partitions). You will want this should you every want to restore you device to it's current configuration. The resulting files will be quite large and should be copied to another device for safe keeping. Exit Safestrap and reboot into FireOS. Tether your device and copy the files to a suitable host. You seem to be familiar with ES File Explorer so should have no problem finding them. Should be in the TWRP directory located within sdcard (or just browse internal storage from the host machine).
Next step is to decide which rom to flash. Two are available/compatible with Safestrap 4.0.1: CM11 and Fire Nexus which are both KitKat based. Both are solid, feature complete and regularly updated with security patches. My daily driver on this device is Nexus as I prefer to build upon a pure Android foundation. That said, CM11 is a fine choice and my preferred rom on secondary devices as it contains a suite of nice UI enhancements minimizing post flash tweaks. FWIW - Lollipop+ roms are not an option as they require an unlocked bootloader which is not possible on your device.
Once you decide upon a rom I'll provide the final set of instructions (really best practices) for installing the rom and related components such as Google Play Services/Store. Feel free to read through the linked threads which contain numerous 'how-to' posts, especially the first couple posts in the rom threads. If all goes well you'll be running a custom rom by this time tomorrow.
Another step complete ...
I downloaded the Safestrap apk from the link contained in the thread, choosing THOR (HDX 7"), installed the app, then installed the recovery software. After a reboot I backed up, and then copied the resultant folder to a PC.
Question: The back up folder is really big (4GB) ... is it okay if I now delete the back up on the tablet? To do this, can I just delete with ESFE?
Duly noted about not doing a factory reset.
After having a read, I think I'm happy to go with the Nexus ROM - keeping things as clean as possible. It sounds like it's very solid with no real issues.
Davey, thanks once again for your precise and excellent help.
Cheers,
Aaron
alhroot said:
Another step complete ...
I downloaded the Safestrap apk from the link contained in the thread, choosing THOR (HDX 7"), installed the app, then installed the recovery software. After a reboot I backed up, and then copied the resultant folder to a PC.
Question: The back up folder is really big (4GB) ... is it okay if I now delete the back up on the tablet? To do this, can I just delete with ESFE?
Duly noted about not doing a factory reset.
After having a read, I think I'm happy to go with the Nexus ROM - keeping things as clean as possible. It sounds like it's very solid with no real issues.
Davey, thanks once again for your precise and excellent help.
Cheers,
Aaron
Click to expand...
Click to collapse
Super! Final step is to install Nexus. Grab the Thor (nickname for 3rd gen HDX 7) installation zip from here. GAaps and SuperSU are built in so it's the only file you will need. Transfer that to a safe location on your device, preferably in a folder you create directly under sdcard. It is important this file (or it's successors) remain on your device at all times for emergency recovery. Putting it in the suggested location reduces the chance of accidental removal when wiping the (user) data partition. You can also place the folder directly under root (/) but be aware some file managers and tethers restrict access to high level directories.
Important: Unlike TWRP Safestrap v4.0.1 recovery has no ability to communicate with the outside world. Not by tether, wifi, bluetooth, adb, etc. It is fully isolated environment. If your rom becomes unstable (rare...but it does happen) your only recovery is using a previously created backup or a flashable rom image (as discussed above) resident on the device.
Boot into Safestrap recovery. Use the File Manager (under advanced) to confirm the existence/location of the Nexus rom zip. Return to the home screen and then access the wipe menu. Use the slider at the bottom to perform a factory reset which wipes the data, cache and dalvik partitions. Note this is different that a stock 'factory reset' which was discussed in a previous post. Also note it is impossible to wipe the system partition in Safestrap v4 even if selected in the advanced section. I won't get into the reasons; just know it isn't necessary for the upcoming operation.
Return to the home screen and select install. Navigate to the folder containing the Nexus rom, select it and then and then swipe the slider at the bottom to install (flash) the zip which will overwrite FireOS. When complete (assuming no errors) reboot your tablet and select continue to fire up Nexus. First boot make take some time as caches are populated. However, anything over 5 min indicates a problem. Once Nexus starts I assume you know where to go from there. You can safely enable WiFi, register with Google and perform all other requested initialization steps.
A few final footnotes:
- Nexus is pretty bare bones; not even a browser in included in the base build. Head over to the Play Store to grab what you need
- While Google's stock launcher is nice I suggest replacing it with Nova which offers a superior AOSP experience along with robust customization
- Xposed Framework and associated modules offers some excellent additions to this rom if you wish to customize further (advanced topic)
- Once you are confident Nexus is stable you can delete the huge FireOS backup created in an earlier step. Either via ESFE or from Safestrap
You may be aware Safestrap supports multi-boot through the use of user created slots. Unfortunately, they do not work with this device and can lead to unrecoverable bricks. You'll see various cautions in the Safestrap, Nexus and CM threads. Short version: do not create or use secondary slots.
Aaron - Feel free to post any questions/concerns/comments. Someone from the HDX community will likely respond within 24-48 hours. On a personal note it's been awhile since I did a long hand 'step-by-step' which is a refreshing change of pace from the usual bullets. I appreciate your patience as I dusted off various cob webs and hope you make the most out of your newly liberated device.
Nice!
Nexus installed, and I'm using it right now ?
Absolutely superb help Davey. I was totally confused trying to work out how to go from where I was to where am now, and you've completely sorted me out. A massive thanks from me.
Everything seems to be working well (!) ... I'm going to test things out a bit more before deleting the FireOS back up folder. I think I messed around with the xposed framework before... I'll definitely take another look.
Seriously, thank you.
Cheers,
Aaron
alhroot said:
Nice!
Nexus installed, and I'm using it right now ?
Absolutely superb help Davey. I was totally confused trying to work out how to go from where I was to where am now, and you've completely sorted me out. A massive thanks from me.
Everything seems to be working well (!) ... I'm going to test things out a bit more before deleting the FireOS back up folder. I think I messed around with the xposed framework before... I'll definitely take another look.
Seriously, thank you.
Cheers,
Aaron
Click to expand...
Click to collapse
Great to hear! As an aside (not for me) don't forget to click the 'Thanks' button on XDA posts when appropriate, especially for newer members trying to build a reputation. Great working with you and gratified by the positive outcome.
Davey126 said:
Super! Final step is to install Nexus. Grab the Thor (nickname for 3rd gen HDX 7) installation zip from here. GAaps and SuperSU are built in so it's the only file you will need. Transfer that to a safe location on your device, preferably in a folder you create directly under sdcard. It is important this file (or it's successors) remain on your device at all times for emergency recovery. Putting it in the suggested location reduces the chance of accidental removal when wiping the (user) data partition. You can also place the folder directly under root (/) but be aware some file managers and tethers restrict access to high level directories.
Important: Unlike TWRP Safestrap v4.0.1 recovery has no ability to communicate with the outside world. Not by tether, wifi, bluetooth, adb, etc. It is fully isolated environment. If your rom becomes unstable (rare...but it does happen) your only recovery is using a previously created backup or a flashable rom image (as discussed above) resident on the device.
Boot into Safestrap recovery. Use the File Manager (under advanced) to confirm the existence/location of the Nexus rom zip. Return to the home screen and then access the wipe menu. Use the slider at the bottom to perform a factory reset which wipes the data, cache and dalvik partitions. Note this is different that a stock 'factory reset' which was discussed in a previous post. Also note it is impossible to wipe the system partition in Safestrap v4 even if selected in the advanced section. I won't get into the reasons; just know it isn't necessary for the upcoming operation.
Return to the home screen and select install. Navigate to the folder containing the Nexus rom, select it and then and then swipe the slider at the bottom to install (flash) the zip which will overwrite FireOS. When complete (assuming no errors) reboot your tablet and select continue to fire up Nexus. First boot make take some time as caches are populated. However, anything over 5 min indicates a problem. Once Nexus starts I assume you know where to go from there. You can safely enable WiFi, register with Google and perform all other requested initialization steps.
A few final footnotes:
- Nexus is pretty bare bones; not even a browser in included in the base build. Head over to the Play Store to grab what you need
- While Google's stock launcher is nice I suggest replacing it with Nova which offers a superior AOSP experience along with robust customization
- Xposed Framework and associated modules offers some excellent additions to this rom if you wish to customize further (advanced topic)
- Once you are confident Nexus is stable you can delete the huge FireOS backup created in an earlier step. Either via ESFE or from Safestrap
You may be aware Safestrap supports multi-boot through the use of user created slots. Unfortunately, they do not work with this device and can lead to unrecoverable bricks. You'll see various cautions in the Safestrap, Nexus and CM threads. Short version: do not create or use secondary slots.
Aaron - Feel free to post any questions/concerns/comments. Someone from the HDX community will likely respond within 24-48 hours. On a personal note it's been awhile since I did a long hand 'step-by-step' which is a refreshing change of pace from the usual bullets. I appreciate your patience as I dusted off various cob webs and hope you make the most out of your newly liberated device.
Click to expand...
Click to collapse
Hey Davey,
Thanks for reaching out to my thread and directing me to your conversation here. I followed all your steps and was able to successfully install the Nexus ROM and have everything running smoothly!!! Very happy! I had been hunting for a while to find a step by step instruction like yours!.
Thanks a lot!
P.S. Wasn't sure whether I should post this here or in my own thread but figured you were actively following this
One week on and I've been using my 'new' tablet quite a bit. It's been really solid with no crashes or problems whatsoever. Fantastic. I've now deleted the 4GB back up on the device, freeing up loads of space again.
I've had another good look at the Xposed framework, but frankly I'm so pleased to have the tablet running smoothly I think I'm just going to keep things nice and standard for now.
Davey, thanks (I found the button now!) again for sharing your knowledge, and giving your time and help. Very much appreciated.
Cheers,
Aaron
alhroot said:
One week on and I've been using my 'new' tablet quite a bit. It's been really solid with no crashes or problems whatsoever. Fantastic. I've now deleted the 4GB back up on the device, freeing up loads of space again.
I've had another good look at the Xposed framework, but frankly I'm so pleased to have the tablet running smoothly I think I'm just going to keep things nice and standard for now.
Davey, thanks (I found the button now!) again for sharing your knowledge, and giving your time and help. Very much appreciated.
Cheers,
Aaron
Click to expand...
Click to collapse
Hey Aaron, thanks for the follow-up. If you are happy with native rom/app capabilities there is no need to complicate matters. That said, if you every have a need for additional core functionality Fire Nexus, an AOSP clone, has proven to be an ideal platform for Xposed Framework and associated KitKat modules.
A tip of the hat to @ggow for his outstanding adaptation and ongoing support of this rom that is cornerstone of the post FireOS experience.
Enjoy your rejuvenated HDX!
Hi there. Thanks for this tutorial - I used it to install the Nexus ROM on my device. One weird thing; everything works, but I have NO sound? Any ideas why that might be?
skoop99 said:
Hi there. Thanks for this tutorial - I used it to install the Nexus ROM on my device. One weird thing; everything works, but I have NO sound? Any ideas why that might be?
Click to expand...
Click to collapse
Thoughts:
- a full power off/on (vs reboot) sometimes solves weird HW issues
- what version of FireOS was on the device prior to Nexus? 4.5.5.1 is recommended for the proper binaries
- might try a simple (dirty) reflash of Nexus in case something didn't 'take' on the first attempt (stranger things have happened)
Davey126 said:
Thoughts:
- a full power off/on (vs reboot) sometimes solves weird HW issues
- what version of FireOS was on the device prior to Nexus? 4.5.5.1 is recommended for the proper binaries
- might try a simple (dirty) reflash of Nexus in case something didn't 'take' on the first attempt (stranger things have happened)
Click to expand...
Click to collapse
Rebooted. I was on 4.5.5.1...
Will try a quick re-flash. ? Thanks!
Update, I have sound over headphones, but not over the speakers... :-S
skoop99 said:
Update, I have sound over headphones, but not over the speakers... :-S
Click to expand...
Click to collapse
Suggest you backup your current Nexus build from within Safestrap, then flash the Safestrap compatible version of cm11 to see if the problem persists. Yep, a bit of trial-and-error but not sure how else to diagnose. You could also try the Safestrap compatible build of FireOS (4.5.2; be sure it's the Safestrap build as a standard FireOs build will brick the device). Another option is to flash the Dolby enhancements which use a different suite of binaries. Post back if you need links to any of the above.

[ROM][S905X2] A95X Max - atvXperience v3 - The Ultimate AndroidTV OS Experience!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We're back, boys!
This time with with Oreo 8.1.0 atvXperience v3 for S905X2 and specifically A95X Max!
THE FIRST EVER CUSTOM ROM FOR A95X MAX!!
• Android OS version: 8.1.0
• For devices: A95X MAX
• Recovery: AOSP
Those who don't have it, you can buy from this link. Probably the most popular S905X2 TV box with HDD and SSD Support and really fast and stable!
https://www.gearbest.com/tv-box/pp_009379639442.html?wid=1433363&lkid=39289238
Attention:
I don't force you to use the ROM. It's stable and can be used as daily driver except for a few things.
If you don't like something, please ask me on how to remove/add it.
atvXperience and nobody from the team nor the forum moderators are responsible for bricked devices. But we always try to help as much as we can
Click to expand...
Click to collapse
Based on AndroidTV OS. Has all the features of an AndroidTV but since atvXperienceOS provides a different experience, we combine the best of AOSP and ATV.
Credit: SrWladimir
* Nayam Amarshe
* Carmine Rovito
* Taylor Stephen Hadden
* Vadim Mussin
v3A
NOTE
The first boot will take a lot of time! Screen will be glitchy, bootvideo will be laggy and you may not even see anything except for black screen but this is normal and doesn't affect the device in any way. This only happens on the first boot because the encrypted kernel and bootloader try to reject the device but it boots anyway and everything will be OK in the second boot.
v3A
• Based on latest AndroidTV OS, latest Security patches.
• Google Play Works
• All Google Apps Work!
• Recommendations work great! To turn off go to Settings - Home
• Casting Works with Airscreen
• Fully Compatible with A95X Max!
• atvXed up with Multiple USB drivers!
v3B To-Do:
Add USB drivers
Add Navbar and Status Bar
Change Settings shortcut to TVSettings
Change App Drawer Wallpaper
Add some more preinstall apps
DO THE ATVX THING
PLEASE WATCH THE YOUTUBE VIDEO:
https://m.youtube.com/watch?feature=youtu.be&v=hnliXmly7WY
Please consider donating if you like our work
PAYPAL LINK
or
PAYPAL EMAIL
[email protected]
Known Problems:
None my boi
Credits:
Fabio Ciani
Ricky Divjakovski
Superceleron
eric
A95X Max developers
XDA-Developers Members
forumXperience members
My team
atvXperience followers
and the one reading this
Special Thanks to my boi Nitin for making this when I was busy
Rom is *meh*, as it completely throws away the stock android Oreo layout and switches to a straight up TV Box setup like a Roku. Most apk's refuse to work with this setup. The included Youtube app sucks and needs to be REMOVED FROM THE ROM as a system app or at least replaced with YT Vanced. Also, Chrome is simply gone...and you cant find it in the "store" either. The apk can be manually installed with a USB/SD card. Netflix app installed within the store does not work with this rom so its like what are we doing here?... but there is a work around. There is no option to boot straight to recovery either, if there even is one. We need TWRP for this to let us do what we want...Get rid of the Android TV BS and let people install their own launcher and you will profit more than just re-skinning the stock OS with this.
Then don't use it... I use it because of the Android TV layout. He was very up front in the beginning as to what this was and what would and would not work. No 3rd party box is going to work with Netflix or Amazon Apps at this time due to widevine DRM.
If what you have described is what you want, then by all means make your own ROM.
Rumsfield said:
Rom is *meh*, as it completely throws away the stock android Oreo layout and switches to a straight up TV Box setup like a Roku. Most apk's refuse to work with this setup. The included Youtube app sucks and needs to be REMOVED FROM THE ROM as a system app or at least replaced with YT Vanced. Also, Chrome is simply gone...and you cant find it in the "store" either. The apk can be manually installed with a USB/SD card. Netflix app installed within the store does not work with this rom so its like what are we doing here?... but there is a work around. There is no option to boot straight to recovery either, if there even is one. We need TWRP for this to let us do what we want...Get rid of the Android TV BS and let people install their own launcher and you will profit more than just re-skinning the stock OS with this.
Click to expand...
Click to collapse
Parsival1973 said:
Then don't use it... I use it because of the Android TV layout. He was very up front in the beginning as to what this was and what would and would not work. No 3rd party box is going to work with Netflix or Amazon Apps at this time due to widevine DRM.
If what you have described is what you want, then by all means make your own ROM.
Click to expand...
Click to collapse
I'll get right on it.
Rumsfield said:
Rom is *meh*, as it completely throws away the stock android Oreo layout and switches to a straight up TV Box setup like a Roku. Most apk's refuse to work with this setup. The included Youtube app sucks and needs to be REMOVED FROM THE ROM as a system app or at least replaced with YT Vanced. Also, Chrome is simply gone...and you cant find it in the "store" either. The apk can be manually installed with a USB/SD card. Netflix app installed within the store does not work with this rom so its like what are we doing here?... but there is a work around. There is no option to boot straight to recovery either, if there even is one. We need TWRP for this to let us do what we want...Get rid of the Android TV BS and let people install their own launcher and you will profit more than just re-skinning the stock OS with this.
Click to expand...
Click to collapse
Read the title again maybe?
This is an AndroidTV OS and no it's not BS. Maybe it's only you who likes to use a mouse and keyboard on a tv. This is meant for those who don't want the airmouse BS and want a clean look, to have the real AndroidTV Box and not just a phone-UI Android Box and not the *meh* launchers that are meant for phone screens.
All apks work, if it works in the phone rom, it works in ATV. 'Maybe' you're doing something wrong or lack the knowledge of apps installation.
The google play store is meant for AndroidTV, it shows apps which are compatible with your remote, not mouse or keyboard.
Also, Netflix thing, everybody knows you need a Netflix certified box for it, it's even mentioned on their website.
And everybody knows you can use Aptoide Store for other apps that aren't on play store.
If you want your own launcher, go ahead make a ROM but please don't call my work a 'simple reskin' because I am working my ass off for a box that's totally encrypted to the core and has a 'meh' phone UI.
So, please don't think I'm playing copy and paste here, I've worked hard on this and if my work is *meh*, please use another ROM (if it exists).
Thank you for the feedback on v3A
Sent from my Spaceship using Tapatalk
Links Updated!
Please don't forget to watch the tutorial video first.
Thank you for the support.
Sent from my F3116 using Tapatalk
Good... Then you can ***** and complain to yourself rather than crap on someone elses hard work.
Rumsfield said:
I'll get right on it.
Click to expand...
Click to collapse
Parsival1973 said:
Good... Then you can ***** and complain to yourself rather than crap on someone elses hard work.
Click to expand...
Click to collapse
Did I ***** and complain? I simply stated some of this rom's caveats and giving a heads up to people who might prospectively install this not realizing its going to completely change the OS to a dedicated Kodi box.
No browser at all? Youtube that you cant get rid of? If you dont like my opinion you can straight up not listen to it. I doubt you even installed it in the first place or you wouldn't be responding with your sh*t posts.
Rumsfield said:
Did I ***** and complain? I simply stated some of this rom's caveats and giving a heads up to people who might prospectively install this not realizing its going to completely change the OS to a dedicated Kodi box.
No browser at all? Youtube that you cant get rid of? If you dont like my opinion you can straight up not listen to it. I doubt you even installed it in the first place or you wouldn't be responding with your sh*t posts.
Click to expand...
Click to collapse
You can install Puffin Browser from Google Play. It's the best TV Browser out there, 100% remote compatibility.
It's pre-rooted, you can easily uninstall YouTube if you know what root means. AptoideTV Store is there to help.
I thought I included webXperience, It's our own browser. If I didn't, I'll do it in the next release which is going to shut everybody up because as I mentioned, this is the first release and the next will be address all the issues you mentioned and the features that I mentioned.
If you want a phone rom on a tv box, please go elsewhere because this is an AndroidTV thread, please don't argue here, the mods take notice of everything.
Thank you for understanding.
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
You can install Puffin Browser from Google Play. It's the best TV Browser out there, 100% remote compatibility.
It's pre-rooted, you can easily uninstall YouTube if you know what root means. AptoideTV Store is there to help.
I thought I included webXperience, It's our own browser. If I didn't, I'll do it in the next release which is going to shut everybody up because as I mentioned, this is the first release and the next will be address all the issues you mentioned and the features that I mentioned.
If you want a phone rom on a tv box, please go elsewhere because this is an AndroidTV thread, please don't argue here, the mods take notice of everything.
Thank you for understanding.
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
I am familiar with rooting aka administrative privileges over apps/os and have had many phones/tablets/matricom boxes all eventually rooted with either magisk or super su, some I actually paid for. This rom doesnt allow me to uninstall anything, just disable which is not the same. How can I grant root access to any app, such as bloatware removal tools? There is no root management on this thing. (that I am aware of?) and there is no recovery I can see to get into to flash anything besides the temp TWRP method with an sd card + paper clip which has not worked with anything on this rom.
Rumsfield said:
I am familiar with rooting aka administrative privileges over apps/os and have had many phones/tablets/matricom boxes all eventually rooted with either magisk or super su, some I actually paid for. This rom doesnt allow me to uninstall anything, just disable which is not the same. How can I grant root access to any app, such as bloatware removal tools? There is no root management on this thing. (that I am aware of?) and there is no recovery I can see to get into to flash anything besides the temp TWRP method with an sd card + paper clip which has not worked with anything on this rom.
Click to expand...
Click to collapse
Try switching on the root switch from settings and reboot.
Another tip, install SuperSU 2.79 and it will fix your root management issues.
The recovery is stock, just like the original ROM. Use quick reboot app to reboot to recovery.
If it still doesn't work, I'll double check and fix anything if wrong. As I said, this is the first release so expect issues unless you know how to fix things but don't worry, the v2B or v2F (whatever I name it) is going to fix all the issues. Trust me, you'll never feel the need to use Navbar and Statusbar again with the new build.
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
Try switching on the root switch from settings and reboot.
Another tip, install SuperSU 2.79 and it will fix your root management issues.
The recovery is stock, just like the original ROM. Use quick reboot app to reboot to recovery.
If it still doesn't work, I'll double check and fix anything if wrong. As I said, this is the first release so expect issues unless you know how to fix things but don't worry, the v2B or v2F (whatever I name it) is going to fix all the issues. Trust me, you'll never feel the need to use Navbar and Statusbar again with the new build.
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
Switching off/on root switch doesn't do anything even with restarting.
SuperSu 2.79 does not successfully flash in temp TWRP with paperclip method or with stock recovery (see pic).
Since there is no root management, quick reboot and other root required apps install but dont work.
Ad-Away also will not save host files either, and I prefer to use that in combination with chrome over Puffin.
If I pissed you off with my earlier post, I apologize and that was not my intent. I understand this rom is pretty much in beta at this point but its very frustrating when nothing works for me, pretty much at all except for what worked with the stock OS.
FYI I have the v81 board.
Rumsfield said:
Switching off/on root switch doesn't do anything even with restarting.
SuperSu 2.79 does not successfully flash in temp TWRP with paperclip method or with stock recovery (see pic).
Since there is no root management, quick reboot and other root required apps install but dont work.
Ad-Away also will not save host files either, and I prefer to use that in combination with chrome over Puffin.
If I pissed you off with my earlier post, I apologize and that was not my intent. I understand this rom is pretty much in beta at this point but its very frustrating when nothing works for me, pretty much at all except for what worked with the stock OS.
FYI I have the v81 board.
Click to expand...
Click to collapse
You are not supposed to flash super su. Just install it.
See here:
https://forum.atvxperience.com/viewtopic.php?f=16&t=814
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
You are not supposed to flash super su. Just install it.
See here:
https://forum.atvxperience.com/viewtopic.php?f=16&t=814
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
It doesn't matter, it doesn't install either way (flashing vs apk).
All I can think of is to completely re-flash the new link firmware over my version I installed when you made it first available, maybe there is a difference?
Rumsfield said:
It doesn't matter, it doesn't install either way (flashing vs apk).
All I can think of is to completely re-flash the new link firmware over my version I installed when you made it first available, maybe there is a difference?
Click to expand...
Click to collapse
Thanks for letting me know, it's strange it's not working for you. My friend reported it working. I'll fix the su in the new version. Meanwhile, you can flash stock rom because I don't want you to get any issues.
New build will be ready in a week or so and it's going to be great!
Thanks for all the feedback.
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
Thanks for letting me know, it's strange it's not working for you. My friend reported it working. I'll fix the su in the new version. Meanwhile, you can flash stock rom because I don't want you to get any issues.
New build will be ready in a week or so and it's going to be great!
Thanks for all the feedback.
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
Thats fine, so now we know why I was a bit brash in my original post.
It still needs a bit of polish. Thanks for you work.
Rumsfield said:
Thats fine, so now we know why I was a bit brash in my original post.
It still needs a bit of polish. Thanks for you work.
Click to expand...
Click to collapse
If you watch this video, you can see that Nicholas tested that the ROM is rooted. That's why I said, I don't know why it's not working for you.
https://youtu.be/hnliXmly7WY
Maybe you can try switching root switch off, reboot, then on and reboot.
I'll update the su anyway, nobody should be getting any problems but this box is one hell of a fighter. They've encrypted everything! I could only get access to system because kernel, recovery and everything else was encrypted.
Sent from my Spaceship using Tapatalk
N'ayam Amarsh'e said:
If you watch this video, you can see that Nicholas tested that the ROM is rooted. That's why I said, I don't know why it's not working for you.
https://youtu.be/hnliXmly7WY
Maybe you can try switching root switch off, reboot, then on and reboot.
I'll update the su anyway, nobody should be getting any problems but this box is one hell of a fighter. They've encrypted everything! I could only get access to system because kernel, recovery and everything else was encrypted.
Sent from my Spaceship using Tapatalk
Click to expand...
Click to collapse
Re-flashing the newer firmware link over last weeks firmware link allowed SuperSu apk to install successfully. Apparently we are good to go now...
Rumsfield said:
Re-flashing the newer firmware link over last weeks firmware link allowed SuperSu apk to install successfully. Apparently we are good to go now...
Click to expand...
Click to collapse
Sweet!
Do lookout for new version as it will include these features:
1. Replace settings shortcut with TV Settings
2. Include pre-install apps like Web browser, Netflix and other apps.
3. Double tap home button for Recent Apps and use arrow keys to clear the apps.
4. Hold Power button for quick shutdown.
5. Add Init.d tweaks for more performance.
6. Add Back-Panic Button.
7. Hold Back button for assistant.
8. Add Navbar and Status bar functionality (if possible)
9. Add Gamepad drivers
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
Sweet!
Do lookout for new version as it will include these features:
1. Replace settings shortcut with TV Settings
2. Include pre-install apps like Web browser, Netflix and other apps.
3. Double tap home button for Recent Apps and use arrow keys to clear the apps.
4. Hold Power button for quick shutdown.
5. Add Init.d tweaks for more performance.
6. Add Back-Panic Button.
7. Hold Back button for assistant.
8. Add Navbar and Status bar functionality (if possible)
9. Add Gamepad drivers
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
I spoke too soon lol. SuperSu 2.79 installs after a fresh firmware flash but bootloops (waiting 20 minutes and still stuck on logo screen). Re-flashing and installing SuperSu 2.82 does the same thing. Oh well.
Re-flashing the image brings its back but just beware root doesnt work. I give up, good luck to everyone getting root.

Categories

Resources