Related
So, we all just got the fresh root. Now that I'm rooted and I want to install CWM, do we have the ability to downgrade like the older updates?
lowridincrew said:
So, we all just got the fresh root. Now that I'm rooted and I want to install CWM, do we have the ability to downgrade like the older updates?
Click to expand...
Click to collapse
No. You can not not use CWM if you are on FireOS5 and I would strongly recommend not attempting to downgrade.
rbox said:
No. You can not not use CWM if you are on FireOS5 and I would strongly recommend not attempting to downgrade.
Click to expand...
Click to collapse
Thanks for the reply. What could I do from here? Playstore? Leanback Launcher?
lowridincrew said:
Thanks for the reply. What could I do from here? Playstore? Leanback Launcher?
Click to expand...
Click to collapse
Wait for me to release TWRP and prerooted roms.
rbox said:
Wait for me to release TWRP and prerooted roms.
Click to expand...
Click to collapse
Oooh ok. Waiting lol
rbox said:
Wait for me to release TWRP and prerooted roms.
Click to expand...
Click to collapse
Hi rbox,
would you be supporting 1st gen FireStick as well? - if TWRP is even possible to be install on these units. Thank you
bula1ca said:
Hi rbox,
would you be supporting 1st gen FireStick as well? - if TWRP is even possible to be install on these units. Thank you
Click to expand...
Click to collapse
That is the plan. Thanks to @AFTVnews.com and some wonderful people on the website, I picked up a stick last night. After some preliminary examination, I'm pretty sure it will work. I am still waiting on the update url for 3.x to 5.0.5 or beta to 5.0.5 though.
rbox said:
That is the plan. Thanks to @AFTVnews.com and some wonderful people on the website, I picked up a stick last night. After some preliminary examination, I'm pretty sure it will work. I am still waiting on the update url for 3.x to 5.0.5 or beta to 5.0.5 though.
Click to expand...
Click to collapse
I know I ask a lot (so feel free to not awnser), but do you have any idea how long until release? my actual install is partially broken and I'd like to know if it's worth resetting now or just wait for your releases
EDIT : I mean for the Fire TV 1 box, not the stick.
rbox said:
That is the plan. Thanks to @AFTVnews.com and some wonderful people on the website, I picked up a stick last night. After some preliminary examination, I'm pretty sure it will work. I am still waiting on the update url for 3.x to 5.0.5 or beta to 5.0.5 though.
Click to expand...
Click to collapse
has your stick already come with the update to 5.0.5?
if not, you can capture it via adb logcat?
El_Nino9 said:
has your stick already come with the update to 5.0.5?
if not, you can capture it via adb logcat?
Click to expand...
Click to collapse
Mine update 4 hours after I un-blocked router. Unfortunately I did not think about it at the moment
desmopro said:
I know I ask a lot (so feel free to not awnser), but do you have any idea how long until release? my actual install is partially broken and I'd like to know if it's worth resetting now or just wait for your releases
EDIT : I mean for the Fire TV 1 box, not the stick.
Click to expand...
Click to collapse
I was doing some testing on Sunday and it all looked good, but that was for unlocked boxes only. I need to fix some things to work with the locked bootloader. I plan on releasing both at the same time.
El_Nino9 said:
has your stick already come with the update to 5.0.5?
if not, you can capture it via adb logcat?
Click to expand...
Click to collapse
I got the newer one that already had 5.0.3 or something on it. I have all the 5 to 5 URLs. I need 3 to 5 or beta to 5.
bula1ca said:
Mine update 4 hours after I un-blocked router. Unfortunately I did not think about it at the moment
Click to expand...
Click to collapse
similar situation as you, it came to mind afterwards that too when i was already rooted.
to be honest i like the new UI better than the old. especially seeing my apps that i've side loaded there on the main page
I do as well however unfortunately broke some apps as well....hopefully these will be fixed sooner or later.
desmopro said:
I know I ask a lot (so feel free to not awnser), but do you have any idea how long until release? my actual install is partially broken and I'd like to know if it's worth resetting now or just wait for your releases
EDIT : I mean for the Fire TV 1 box, not the stick.
Click to expand...
Click to collapse
Dude, faux pas
rbox said:
I was doing some testing on Sunday and it all looked good, but that was for unlocked boxes only. I need to fix some things to work with the locked bootloader. I plan on releasing both at the same time.
I got the newer one that already had 5.0.3 or something on it. I have all the 5 to 5 URLs. I need 3 to 5 or beta to 5.
Click to expand...
Click to collapse
1) firetv 1, what will the consequences be if you were to dd the bootloader and other partitions of an unlocked system to one of a locked device fire tv1
2)firetv stick, if i do a system dump using dd, would that be useful? i have kingroot and busybox from playstore only installed on system partition.
El_Nino9 said:
1) firetv 1, what will the consequences be if you were to dd the bootloader and other partitions of an unlocked system to one of a locked device fire tv1
2)firetv stick, if i do a system dump using dd, would that be useful? i have kingroot and busybox from playstore only installed on system partition.
Click to expand...
Click to collapse
1) you'll brick it hard
2) I actually have gotten all the URLs I need. Thanks though.
my first gen fire tv box, I root it by kingroot, everything works fine. but after I use super me to get super su, resatart. then the box stacks at amazon splash start screen. Anybody can give any idea how to hardware reset? help :crying:
I do not want to give you a hard time but why you guys do not read before doing it. There are few post here mentioning that boxes get bricked if you use supersu-me. Can you connect to it through adb? The only way to get it back if somehow rbox will release an unbrick image as he did for firetv 2
sardiswolf said:
my first gen fire tv box, I root it by kingroot, everything works fine. but after I use super me to get super su, resatart. then the box stacks at amazon splash start screen. Anybody can give any idea how to hardware reset? help :crying:
Click to expand...
Click to collapse
Same thing happened to me with fire stick but not stuck on amazon logo but fire TV stick logo.
Sent from my iPhone using Tapatalk
READ ME!
If you read the Kingroot thread on this forum, located here. You will find that the authors of Kingroot have taken exception to the author of SuperSu and anyone else who uses it in their programs to replace Kinguser, because of the claims of conflicting programs and/or malicious coding. Kingroot authors counter claim that programs like Super-Sume improperly remove Kingroot leaving orphaned files which may cause problems. But the author of Super-Sume says his program will not brick your device.
Most people have had no luck installing SuperSu on their devices after being rooted by Kingroot even though Kingroot authors claim they could co-exist on the same device, because Kingroot has added a restriction regarding SuperSu. So consequently those who have gotten SuperSu installed on their Kingroot rooted devices have ended up with problems.
Don't install random stuff via root without custom recovery! Its just as effective as a pull and pray people. You need some protection.
Just be patient!!
hope rbox will bring out some unbrick rom. is any other way to do the hardware reset. open the box and short somewhere? Please give me a hint.
sardiswolf said:
hope rbox will bring out some unbrick rom. is any other way to do the hardware reset. open the box and short somewhere? Please give me a hint.
Click to expand...
Click to collapse
There's really nothing you can do if you have a locked firetv1 box that is bricked.
rbox said:
There's really nothing you can do if you have a locked firetv1 box that is bricked.
Click to expand...
Click to collapse
even it was rooted and I put super su there. I remenber can short the the chip somewhere to get the recovery mode.
sardiswolf said:
even it was rooted and I put super su there. I remenber can short the the chip somewhere to get the recovery mode.
Click to expand...
Click to collapse
There's many ways to force it into recovery, but there's not much you can do from there.
You could follow the hardware rooting instructions to get access to the flash chip, and then rewrite the system.img... but that's about it.
rbox said:
There's many ways to force it into recovery, but there's not much you can do from there.
You could follow the hardware rooting instructions to get access to the flash chip, and then rewrite the system.img... but that's about it.
Click to expand...
Click to collapse
do you have thr 5.0.5 system.img ? since it is bricked, may try, otherwise throw in the garbage.
sardiswolf said:
do you have thr 5.0.5 system.img ? since it is bricked, may try, otherwise throw in the garbage.
Click to expand...
Click to collapse
@AFTVnews.com has posted the update url for 5.0.5 for firetv1. You just need to run sdat2img on it to get the full system.img.
rbox said:
@AFTVnews.com has posted the update url for 5.0.5 for firetv1. You just need to run sdat2img on it to get the full system.img.
Click to expand...
Click to collapse
good to hear that, but where is the link, and after I get that img file, what do I need to do. Thanks
sardiswolf said:
good to hear that, but where is the link, and after I get that img file, what do I need to do. Thanks
Click to expand...
Click to collapse
Can't really walk you through this. But you could wait until I post the prerooted rom for firetv1. And extract the system.img from that.
rbox said:
Can't really walk you through this. But you could wait until I post the prerooted rom for firetv1. And extract the system.img from that.
Click to expand...
Click to collapse
Thanks, I will wait for your rom and use aftvnew post the unbrick way to do factory reset.
looks like the usb keyboard could not make it get into factory reset area.
Same problem here. used SuperSU me and now the box is stuck on Firetv logo.. It looks like emmc soldering is the only way which is pretty scary and possibly not worth the hassle... Did you get any further with recovering?
mrchrister said:
Same problem here. used SuperSU me and now the box is stuck on Firetv logo.. It looks like emmc soldering is the only way which is pretty scary and possibly not worth the hassle... Did you get any further with recovering?
Click to expand...
Click to collapse
no way to solve it. bought another brand tv box.
I will try a emmc hardware root to revive the box. I hope rbox will release a bootloader for firetv gen 1 soon
Sent from my X98 Air III(M5C5) using Tapatalk
mrchrister said:
I will try a emmc hardware root to revive the box. I hope rbox will release a bootloader for firetv gen 1 soon
Sent from my X98 Air III(M5C5) using Tapatalk
Click to expand...
Click to collapse
If your bootloader isn't already unlocked and you bricked a FireTV 1, there isn't anything that can be done from a software perspective.
i was hoping to dd system.img through hardware emmc soldering. do you think this could work to revive it?
Sent from my iPhone using Tapatalk
Has anyone else that has their bootloader unlocked been able to download netflix from the play store? I tried but just said device not compatible. I was able to download the apk somewhere else but just wondering it that happened because of the bootloader
Yes it's because of the bootloader
ErickF said:
Has anyone else that has their bootloader unlocked been able to download netflix from the play store? I tried but just said device not compatible. I was able to download the apk somewhere else but just wondering it that happened because of the bootloader
Click to expand...
Click to collapse
It's been that way since Android 4.0 or something like that.
Sent from my Moto Z (2) using Tapatalk
Na just recently actually
Just download the apk from apkmirror
Though apk mirror works, I'm getting sick of this sort of thing. Kodi doesn't block unlocked bootloaders... I've been a Netflix customer for years... This is really annoying...
-RioT- said:
Though apk mirror works, I'm getting sick of this sort of thing. Kodi doesn't block unlocked bootloaders... I've been a Netflix customer for years... This is really annoying...
Click to expand...
Click to collapse
Kodi also has nothing to do with movie and television studios and is mostly used for pirating
Sent from my Moto Z (2) using Tapatalk
altimax98 said:
Kodi also has nothing to do with movie and television studios and is mostly used for pirating
Click to expand...
Click to collapse
Sure.
-RioT- said:
Though apk mirror works, I'm getting sick of this sort of thing. Kodi doesn't block unlocked bootloaders... I've been a Netflix customer for years... This is really annoying...
Click to expand...
Click to collapse
Can you guys link to the Netflix APK that works for you?
I also just have my bootloader unlocked running factory Sprint 8.0.0 July patch and when I launch Netflix it shown the Netflix logo and just hangs there. No error just hangs on the Netflix logo.
Thanks!
jeffritz1 said:
Can you guys link to the Netflix APK that works for you?
I also just have my bootloader unlocked running factory Sprint 8.0.0 July patch and when I launch Netflix it shown the Netflix logo and just hangs there. No error just hangs on the Netflix logo.
Thanks!
Click to expand...
Click to collapse
Do you have magisk installed?
Marcowe said:
Do you have magisk installed?
Click to expand...
Click to collapse
I do not. I was trying to make it happen without breaking OTAability
jeffritz1 said:
I do not. I was trying to make it happen without breaking OTAability
Click to expand...
Click to collapse
So there isn't a solution for you, every solution breaks OTA.
The only solution without breaking OTA is relocking bootloader.
Netflix fix:
must be rooted.
go to the root directory with a file manager that will let you like Root Explorer
Go to: /system/vendor/lib
Find the file "liboemcrypto.so" and delete it.
Reboot
go to play store and download Netflix, Hulu and or Vudu
I just bought this tablet on black Friday recently and I was wondering if the rapid root method noted on this other thread would work? I don't like amazon's bloatware on it.
Rapid Temporary Root for HD 8 & HD 10
Software root method for Mediatek MT816x, MT817x and MT67xx! A tool that gives you a temporary root shell with Selinux permissive to do with as you please STATUS Confirmed Working Fire HD 8 8th gen (2018) (thanks xyz`) -- up to Fire OS 6.3.0.1...
forum.xda-developers.com
dizzymon said:
I just bought this tablet on black Friday recently and I was wondering if the rapid root method noted on this other thread would work? I don't like amazon's bloatware on it.
Rapid Temporary Root for HD 8 & HD 10
Software root method for Mediatek MT816x, MT817x and MT67xx! A tool that gives you a temporary root shell with Selinux permissive to do with as you please STATUS Confirmed Working Fire HD 8 8th gen (2018) (thanks xyz`) -- up to Fire OS 6.3.0.1...
forum.xda-developers.com
Click to expand...
Click to collapse
Your own post says "up to ... 6.3.0.1". Any recentl tablet is going to be above that, so, no it won't work. The best way to debloat is with the "Toolbox"
I used toolbox but I can't seem to get other web browsers to install. Any ideas?
I got one when amazon was doing there amazon day for cheap, too bad it comes with newestest firmware. I haven't used it yet since it can't be rooted or roms yet. I hope someone comes up with something soon
Toolbox got rid of all the amazon things from the UI but the browser remains an issue.
dizzymon said:
Toolbox got rid of all the amazon things from the UI but the browser remains an issue.
Click to expand...
Click to collapse
I don't have an issue. Chrome is working fine on my HD 10 2019. OS ver 7.3.1.6
dizzymon said:
Toolbox got rid of all the amazon things from the UI but the browser remains an issue.
Click to expand...
Click to collapse
I was able to install Vivaldi, from the Google Play Store.
Droid4200 said:
I got one when amazon was doing there amazon day for cheap, too bad it comes with newestest firmware. I haven't used it yet since it can't be rooted or roms yet. I hope someone comes up with something soon
Click to expand...
Click to collapse
I was just thinking , has anyone tried to open one of these and serial/UART flash to downgrade firmware to a rootable firmware?
Droid4200 said:
I was just thinking , has anyone tried to open one of these and serial/UART flash to downgrade firmware to a rootable firmware?
Click to expand...
Click to collapse
I am able to boot into the bootrom through the other exploits on fire devices, the bootrom is how every fire device has been unlocked in the last 2years. No one really has put much effort into unlocking it though. Running the exploit and plugging in to PC during the "waiting for bootrom" would boot it right into the bootrom (lsusb detects mediatek phone), but that is as far as i got as the exploit would have to be set up i believe similar to the firestick4k exploit. I have 2 rooted and one that is not rooted. The mtk-su exploit was blocked on first update. But the mtk-su is a temp root and you can not change the system folder. i havent checked any device higher than 6.3.1.2, I am not sure if you can still boot into it. Either way, it seems that the bootrom for this device was not blocked on the firmware. I believe there is a unlock option here, but i am not the one to figure it out...
Michajin said:
... i havent checked any device higher than 6.3.1.2, I am not sure if you can still boot into it. Either way, it seems that the bootrom for this device was not blocked on the firmware. I believe there is a unlock option here, but i am not the one to figure it out...
Click to expand...
Click to collapse
That says it all. The current OS version are all higher than that and that no longer works. So far, no one has succeeded in rooting the current OS and you can't downgrade.
lewmur said:
That says it all. The current OS version are all higher than that and that no longer works. So far, no one has succeeded in rooting the current OS and you can't downgrade.
Click to expand...
Click to collapse
i dont know if anyone has tried to check to see if the bootrom is available on newer OS. But no one has written code to unlock if there is a bootrom exploit. I will update one this week and see if it will still boot into the bootrom. The mtk-su was just a temp root. The bootrom exploit has potential for full unlock, root, and TWRP... Has anyone try to access it on 7.3.1.6?
lewmur said:
That says it all. The current OS version are all higher than that and that no longer works. So far, no one has succeeded in rooting the current OS and you can't downgrade.
Click to expand...
Click to collapse
Looks like they killed the bootrom access since.. i don't know what version killed it.. I am on 6.3.1.7 now. I can only see the preloader now...
lewmur said:
That says it all. The current OS version are all higher than that and that no longer works. So far, no one has succeeded in rooting the current OS and you can't downgrade.
Click to expand...
Click to collapse
@k4y0z has done it again! come join the party @ https://forum.xda-developers.com/t/...k-brainstorming.3979343/page-28#post-84499719
Michajin said:
Looks like they killed the bootrom access since.. i don't know what version killed it.. I am on 6.3.1.7 now. I can only see the preloader now...
Click to expand...
Click to collapse
7.3.1.1 -> 7.3.1.0 confirmed. need more ppl 2 test out other fw rev.
newnewcomputer said:
@k4y0z has done it again! come join the party @ https://forum.xda-developers.com/t/...k-brainstorming.3979343/page-28#post-84499719
7.3.1.1 -> 7.3.1.0 confirmed. need more ppl 2 test out other fw rev.
Click to expand...
Click to collapse
i can give it a shot this weekend if i have a device that is on 7.3.1.1. But so few people got access to root or 7.3.1.1, unlocking may be moot if no developers have a want to make a rom. On that note, there should be a shorting method to access the bootrom. Amazon disabled the volume/power on trick somewhere between 7.3.1.2 and 7.3.1.7, not sure what version disabled the easy way. so what all does this do? just downgrade for accessibility to root? What do i need to do this, do i need access to bootrom to downgrade? Trying to read through the posts i got a little lost. I have 3 Mavericks and one is rooted. What would you like me to try, can you give me a step by step. Guess i am asking what rom are you looking for to attempt a downgrade from ? Let me know i will give it a shot, i just have my mavericks in a drawer right now...
Michajin said:
... so what all does this do? just downgrade for accessibility to root? What do i need to do this, do i need access to bootrom to downgrade? Trying to read through the posts i got a little lost. I have 3 Mavericks and one is rooted. What would you like me to try, can you give me a step by step. Guess i am asking what rom are you looking for to attempt a downgrade from ? Let me know i will give it a shot, i just have my mavericks in a drawer right now...
Click to expand...
Click to collapse
all mine are on 7.3.1.0 so i havent gone thro' the procedure myself. its early n only got 1 confirmed successful case so far (the hack was just put together n tested last few days).
@k4y0z thinks it should work on fw rev. newer than 7.3.1.1. first is to run the bypass utility; then the rollback. if it works out, ur tab will now be running 7.3.1.0 which allows the mtk-su root.
looks like someone has just tried n run into a problem...will need to see how it works out in that thread. good luck!
newnewcomputer said:
all mine are on 7.3.1.0 so i havent gone thro' the procedure myself. its early n only got 1 confirmed successful case so far (the hack was just put together n tested last few days).
@k4y0z thinks it should work on fw rev. newer than 7.3.1.1. first is to run the bypass utility; then the rollback. if it works out, ur tab will now be running 7.3.1.0 which allows the mtk-su root.
looks like someone has just tried n run into a problem...will need to see how it works out in that thread. good luck!
Click to expand...
Click to collapse
Do you need access to the bootrom to use this? If someone can find access to the bootrom on a updated rom this exploit has a further chance to develop into a custom rom. I suspect the old shorting method should be possible, but i have no idea where to look on the board. I have had it apart before but didn't see anything standing out... but anyways i am charging up my mavericks to see what i have, i know i have a 7.3.1.0, a 7.3.1.1 and a 7.3.1.7. So to be clear, boot into bootrom (volume down and plug in) then run the bypass and rollback? I will test the 7.3.1.1 since i know this one is more likely to succeed
Michajin said:
Do you need access to the bootrom to use this? If someone can find access to the bootrom on a updated rom this exploit has a further chance to develop into a custom rom. I suspect the old shorting method should be possible, but i have no idea where to look on the board. I have had it apart before but didn't see anything standing out... but anyways i am charging up my mavericks to see what i have, i know i have a 7.3.1.0, a 7.3.1.1 and a 7.3.1.7. So to be clear, boot into bootrom (volume down and plug in) then run the bypass and rollback? I will test the 7.3.1.1 since i know this one is more likely to succeed
Click to expand...
Click to collapse
Yeah there was a successful downgrade from 7.3.1.1 already, it has the same lk/pl as 7.3.1.0 but I haven't been able to get into the bootrom on 7.3.1.2, might need to look into shorting a pin.
I think bootrom through the volume button was killed before 7.3.1.7 though
I can confirm bootrom through the volume button on v7.3.1.7 is not working.
newnewcomputer said:
all mine are on 7.3.1.0 so i havent gone thro' the procedure myself. its early n only got 1 confirmed successful case so far (the hack was just put together n tested last few days).
@k4y0z thinks it should work on fw rev. newer than 7.3.1.1. first is to run the bypass utility; then the rollback. if it works out, ur tab will now be running 7.3.1.0 which allows the mtk-su root.
looks like someone has just tried n run into a problem...will need to see how it works out in that thread. good luck!
Click to expand...
Click to collapse
Do i need to run the bypass utility in linux? I am not familiar with this tool... Have any step by step instructions? i will do my 7311 then i will open my other on 7317 and start looking for a short option (i dont care if i destroy one of these testing, lol). I am going to go deep into it in the morning...
Michajin said:
Do i need to run the bypass utility in linux? I am not familiar with this tool... Have any step by step instructions? i will do my 7311 then i will open my other on 7317 and start looking for a short option (i dont care if i destroy one of these testing, lol). I am going to go deep into it in the morning...
Click to expand...
Click to collapse
@Michajin The bypass-utility will run fine on windows, check the README how to set up python and libusb on windows.
I'm not sure if the kamakiri-RPMB Downgrade will work on windows though.
You can use FireISO for both, it should have everything included.
Steps would be:
Run bypass-utility to disable authentication.
Use SP Flash Tool to flash 7.3.1.0
If it doesn't boot due to anti-rollback, run the kamakiri RPMB-downgrade
As for the shorting, there are some options on the back of the board.
Compare with suez (Fire HD 10 - 2017)
Note: Systemless root is not an option on this box due to locked bootloader, do not tell me that root is not an option, because I am rooted right now.
I rooted my Fire TV 2 (FireOS 5.2.7.1) with the hardware method using SuperSU in system mode, although whenever I open SuperSU it immediately crashes. It still comes up with root prompts and I can still accept them, but I can't actually open the app and change settings because it just instantly crashes. Is there a fix for this?
If there isn't a fix for this issue, are there any other SYSTEM MODE superusers that do the same thing as SuperSU.
(Magisk is systemless root, so it doesn't meet the criteria above.)
It's just what amaz. does with apps they don't like^^
But you can edit the supersu config file if you like, in order to access all supersu settings...
The fix is to flash the amonet zip with twrp (aka. unlock the BL), then use magisk... but I guess you know that already, isn't it!?
Sus_i said:
It's just what amaz. does with apps they don't like^^
But you can edit the supersu config file if you like, in order to access all supersu settings...
Click to expand...
Click to collapse
So an Amazon service force closes the package name eu.chainfire.supersu in an attempt to make root Unusable? If that's the case Couldn't I just edit the package name to something else, like what I did with FireStarter Launcher?
Sus_i said:
The fix is to flash the amonet zip with twrp (aka. unlock the BL), then use magisk... but I guess you know that already, isn't it!?
Click to expand...
Click to collapse
Well unless Magisk Devs release a System mode Root that can't happen, for reasons I stated above:
"Systemless root is not an option on this box due to locked bootloader"
Having TWRP doesn't mean it's an unlocked bootloader, I know because I recently tried Magisk out of desperation, the result was that It ended up being stuck on the Amazon Logo and I had to do the unbrick process again.
Toothless_NEO said:
So an Amazon service force closes the package name eu.chainfire.supersu in an attempt to make root Unusable? If that's the case Couldn't I just edit the package name to something else, like what I did with FireStarter Launcher?
Well unless Magisk Devs release a System mode Root that can't happen, for reasons I stated above:
"Systemless root is not an option on this box due to locked bootloader"
Having TWRP doesn't mean it's an unlocked bootloader, I know because I recently tried Magisk out of desperation, the result was that It ended up being stuck on the Amazon Logo and I had to do the unbrick process again.
Click to expand...
Click to collapse
No, it isn't the package name. Most likely it's because an incompatible app theme (missing theme on all fireTV OS versions). If you want to know details, somewhere on xda is a guide, on how to use root/xposed together with xposed modules, as a workarround in order to open up the supersu app on fireTVs. A working theme was material dark, if I remember correct.
Idk why you state magisk isn't an option on 'this' box, since the BL unlock is out and really easy.
Anyway, have fun.
Toothless_NEO said:
So an Amazon service force closes the package name eu.chainfire.supersu in an attempt to make root Unusable? If that's the case Couldn't I just edit the package name to something else, like what I did with FireStarter Launcher?
Well unless Magisk Devs release a System mode Root that can't happen, for reasons I stated above:
"Systemless root is not an option on this box due to locked bootloader"
Having TWRP doesn't mean it's an unlocked bootloader, I know because I recently tried Magisk out of desperation, the result was that It ended up being stuck on the Amazon Logo and I had to do the unbrick process again.
Click to expand...
Click to collapse
He never said or implied having twrp means you have a unlocked bl.
He (as well as I) are wondering why you haven't simply flashed Rortiz2 amonet zip (the unlock) from within your current locked twrp.
This will ultimately unlock the bl of your Sloane.
And solve your issue in minutes + enable you to flash magisk etc.
Regards
Bertonumber1 said:
He never said or implied having twrp means you have a unlocked bl.
He (as well as I) are wondering why you haven't simply flashed Rortiz2 amonet zip (the unlock) from within your current locked twrp.
This will ultimately unlock the bl of your Sloane.
And solve your issue in minutes + enable you to flash magisk etc.
Regards
Click to expand...
Click to collapse
WAIT....
I can unlock the bootloader of my AFTV 2 box- sloane?
Last year i did hardware method to get root/twrp because i was under the impression that one CAN NOT unlock bootloader on this device....
If you can now unlock bootloader on sloane box, when did this happen?
When was this "Rortiz2 amonet" released?
Lastly, since im already rooted and twrp, what do i further need to do to unlock the bootloader?
Thanks many
dovedescent7 said:
WAIT....
I can unlock the bootloader of my AFTV 2 box- sloane?
Last year i did hardware method to get root/twrp because i was under the impression that one CAN NOT unlock bootloader on this device....
If you can now unlock bootloader on sloane box, when did this happen?
When was this "Rortiz2 amonet" released?
Lastly, since im already rooted and twrp, what do i further need to do to unlock the bootloader?
Thanks many
Click to expand...
Click to collapse
I'll answer your pm and your post here...
Yes you can, the boys have presented the full unlock of the Sloane Firetv 2 and Rortiz2 has headlined the thread in "Original Android TV development" section within the Amazon Firetv forum.
All you need to do is follow the OP there, download and flash the zip in current twrp.
If you need any assistance just ask.
Good hearing from you again
Regards
Bertonumber1 said:
I'll answer your pm and your post here...
Yes you can, the boys have presented the full unlock of the Sloane Firetv 2 and Rortiz2 has headlined the thread in "Original Android TV development" section within the Amazon Firetv forum.
All you need to do is follow the OP there, download and flash the zip in current twrp.
If you need any assistance just ask.
Good hearing from you again
Regards
Click to expand...
Click to collapse
I was told that you have to update to the latest version of FireOS and those versions are extremely broken. I can't use that unlock method unless someone finds a way to do it without updating to the latest firmware.
Sus_i said:
No, it isn't the package name. Most likely it's because an incompatible app theme (missing theme on all fireTV OS versions). If you want to know details, somewhere on xda is a guide, on how to use root/xposed together with xposed modules, as a workarround in order to open up the supersu app on fireTVs. A working theme was material dark, if I remember correct.
Idk why you state magisk isn't an option on 'this' box, since the BL unlock is out and really easy.
Anyway, have fun.
Click to expand...
Click to collapse
It's not an option because the unlock requires an update to the latest firmware (stock firmware) or so I was told.
If it's just the theme that is the issue could I just use Preferences editor to change it to a working theme?
Toothless_NEO said:
If it's just the theme that is the issue could I just use Preferences editor to change it to a working theme?
Click to expand...
Click to collapse
Probably not.
This is the old guide, mentioned above:
[PROTIP] How to get SuperSu, Xposed App Settings and other apps that dont open to run
Some apps like supersu or xposed app settings dont open on firetv. Apparently this is caused by the app theme which the firetv is missing. So its unable to open those apps with incompatible themes. To fix those apps and make em run, you need...
forum.xda-developers.com
Sus_i said:
Probably not.
This is the old guide, mentioned above:
[PROTIP] How to get SuperSu, Xposed App Settings and other apps that dont open to run
Some apps like supersu or xposed app settings dont open on firetv. Apparently this is caused by the app theme which the firetv is missing. So its unable to open those apps with incompatible themes. To fix those apps and make em run, you need...
forum.xda-developers.com
Click to expand...
Click to collapse
Interesting, Why does It work to change the theme in Xposed and not through preferences and/or modding the app?