Develop Bugs

Towel Root [NE6] - Knox 0x0

So geohot announced last night that he has rooted 4.4.2, its specifically tailored to the S5's with locked bootloaders, but he states it should work on all devices with a kernel older than June 5th (Our latest update, NE6, is dated May 19th).
He also states it shouldnt trigger knox, but he makes no guarantees.
Its also just an apk which is awesome.
Im feeling bold today, so if nobody else gets around to testing it on the tmobile note 3, ill be testing it in a few hours on my lunch.
http://towelroot.com/
http://forum.xda-developers.com/showthread.php?t=2783157
RESTATING OBVIOUS: this isn't my work, all credit goes to geohot, I'm merely linking to it as our phone meets the criteria and should theoretically work works.
UPDATE
Worked without a hitch... Just make sure to install the latest SuperSU (download the zip from chainfires website, and extract SuperSU.apk from common)... It's newer than the play store version.
SuperSU zip:
http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
The play store version of SuperSU has been updated and should work fine now.
1) run towel root ("make it rain"), it will reboot automatically
2) immediatly after reboot, install latest SuperSU (before you run it)
3) run SuperSU, let it update binaries, it will freeze on disabling knox
4) reboot again, run again, disable knox will be successful.
IT DID NOT TRIP KNOX
Just to clarify, this device is a virgin (never been rooted before) running the latest NE6 update...
Restoring to stock (/w nothing tripped) should be as easy as flashing the stock NE6 tar via odin.
UPDATE 2
I can confirm by reply's here, as well as actually trying it on a friends phone that is is not working for NB4, but works perfectly fine on NE6
{
"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"
}
Sent from my SM-N900T using Tapatalk

starnostar said:
So geohot announced last night that he has rooted 4.4.2, its specifically tailored to the S5's with locked bootloaders, but he states it should work on all devices with a kernel older than June 5th (Our latest update, NE6, is dated May 19th).
He also states it shouldnt trigger knox, but he makes no guarantees.
Its also just an apk which is awesome.
Im feeling bold today, so if nobody else gets around to testing it on the tmobile note 3, ill be testing it in a few hours on my lunch.
http://towelroot.com/
http://forum.xda-developers.com/showthread.php?t=2783157
RESTATING OBVIOUS: this isn't my work, all credit goes to geohot, I'm merely linking to it as our phone meets the criteria and should theoretically work.
Click to expand...
Click to collapse
Let me know if it works for you I've got the galaxy s5 for T-Mobile but I'm not sure I want to try it until I've got proof on T-Mobile devices

Worst case scenario if I were to try and right now what would happen
Sent from my SM-N900T using xda premium

Pajar0913 said:
Worst case scenario if I were to try and right now what would happen
Click to expand...
Click to collapse
you would trip knox and/or have to flash a stock tar... ill be testing it in about 30 min.

Keep us updated

There might be bugs since it was intended for the S5. It's not tailored for our devices. Geohot says the same thing. And he didn't say it shouldn't trip knox. Just threw it out there that it didn't trip it for him.
Sent from my SM-N900T using XDA Premium 4 mobile app

Moved to OP

I can confirm that it works following starnostar's instructions.
Sent from my SM-P600 using Tapatalk

So I can go install a custom recovery thereafter
Hello and this is kind of newbee-ish I am an ATT customer looking (actually getting delivery tomorrow) for an N900T - i.e. Tmo Note - which needs to be sim ulocked after it is rooted and then a custom recovery - and then to my fav - an CM ROM.
I think if I do flash a custom recovery - it will trip knox - Just asking here to see if that's true or get some more insights into my plans for the device.
Thanks for reading so far.

Not working 4.4.2 / first time root
I tried rooting following starnostar instructions and it didn't work. The binaries that SuperSU need wouldn't download after the towelroot initial reboot. Tried installing SuperSU (entire directory in file provided) from the phone/SD card with the same result. Did an uninstall of everything a few times. Reboot -> install tr -> reboot -> install SuperSU provided from phone/SD card (either) -> run SuperSU or reboot and run SuperSU. Tried with other super user apps (ChainsDD and ClockworkMod). Same result.
The only things I can think to do are disable Lookout, factory restart the phone or start then stop KNOX (I disabled it a little while back). Any ideas?

Awesome news!!! Being new to rooting in general I'll wait until I see a bit more feedback, but very excited there is a new Knox friendly root available. Thanks for posting!
Sent from my SM-N900T using xda app-developers app

gitofgits said:
I tried rooting following starnostar instructions and it didn't work. The binaries that SuperSU need wouldn't download after the towelroot initial reboot. Tried installing SuperSU (entire directory in file provided) from the phone/SD card with the same result. Did an uninstall of everything a few times. Reboot -> install tr -> reboot -> install SuperSU provided from phone/SD card (either) -> run SuperSU or reboot and run SuperSU. Tried with other super user apps (ChainsDD and ClockworkMod). Same result.
The only things I can think to do are disable Lookout, factory restart the phone or start then stop KNOX (I disabled it a little while back). Any ideas?
Click to expand...
Click to collapse
How did you disable knox without root? if you rooted in the past, maybe residual files left over are causing issues. If this is the case (that you had rooted in the past), maybe a fresh "never-rooted" odin flash is in order.
Another possibility is I used root checker to verify root before installing supersu (i never opened the app, just accepted the prompt), maybe a root prompt must be triggered and granted to complete the process.

starnostar said:
How did you disable knox without root? if you rooted in the past, maybe residual files left over are causing issues. If this is the case (that you had rooted in the past), maybe a fresh "never-rooted" odin flash is in order.
Another possibility is I used root checker to verify root before installing supersu (i never opened the app, just accepted the prompt), maybe a root prompt must be triggered and granted to complete the process.
Click to expand...
Click to collapse
Yeah, I was thinking that I needed a prompt too. I've never attempted root with this phone.
As to KNOX, I just turned it off/disabled it after I did a reset as I did with a handful of things. I was one of the unfortunate few who had to reset after the 4.4.2 upgrade. I did reinstall KNOX, but there was no change. reboot -> install tr - make it ra1n -> reboot -> check - no root access -> install SU - no SU binary to install. Or little variations on that. I'll just wait around a few weeks to see if anyone figures out a solution or factory reset and try again.
Bummer too, I was really looking forward to getting Call Master back. :/

On ne6. Rooted fine and knox 0x0.

Worked for me, Almost forgot the step to (download the zip from chainfires website, and extract SuperSU.apk from common) got errors updating the SuperSU files but its working now!

Help!! Getting error on SuperSU
On Note 3 Tmobile NB4, never rooted, installed Towelroot, rebooted, and installed superSU, when tried to load Super User I get this message,
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Please help!!
zemaj800 said:
Worked for me, Almost forgot the step to (download the zip from chainfires website, and extract SuperSU.apk from common) got errors updating the SuperSU files but its working now!
Click to expand...
Click to collapse

shijocj said:
On Note 3 Tmobile NB4, never rooted, installed Towelroot, rebooted, and installed superSU, when tried to load Super User I get this message,
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Please help!!
Click to expand...
Click to collapse
I initially tried on NB4 but had the same issue, updated to NE6 with Samsung's Kies app and then tried again and it worked fine.

stpinc said:
I initially tried on NB4 but had the same issue, updated to NE6 with Samsung's Kies app and then tried again and it worked fine.
Click to expand...
Click to collapse
I was on NB4 and getting Kies and updating the firmware fixed it for me. Thanks!

Wow, finally a working root solution for our Note 3!
Kies is installed and as soon as I charge my phone, I will update to NE6 and give this a shot!

So u got it working did it trip Knox for u
Sent from my SM-N900T using XDA Free mobile app

How to unroot a Fire TV completely?

I can't seem to find a definitive answer to this. For a variety of reasons I would like to uproot my Fire TV. It currently has Busybox, Clockwork Mod, Su, Towelroot installed. It also has Amazon updates blocked. Is the process as simple as installing the latest firmware, after unlocking Amazon updates. That is, will the update take care of removing anything added to the unit by me ( Busybox for example)?
Thanks...philip
Sent from my Fire HDX.

AFTVnews has a guide on returning to stock:
http://www.aftvnews.com/how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software/

kraqh3d said:
AFTVnews has a guide on returning to stock:
Click to expand...
Click to collapse
Thanks. I had read that excellent guide before. It requires ClockworkMod and retains root if you select an appropriate firmware. This doesn't seem to restore a Fire TV to the state it was bought. For instance, ClockworkMod would still be there and perhaps even Amazon update blocking.
I should have been clearer with my intent. I would like to know how to restore a Fire TV to the state that it came when purchased. That is, I want to know how to remove any traces of me having touched it!
Sent from my Fire HDX.

If you want to unroot it, Id sell the one you have rooted ( since they are becoming like ghosts now ) and buy one with the money profited.

pmcdunnough said:
I can't seem to find a definitive answer to this. For a variety of reasons I would like to uproot my Fire TV. It currently has Busybox, Clockwork Mod, Su, Towelroot installed. It also has Amazon updates blocked. Is the process as simple as installing the latest firmware, after unlocking Amazon updates. That is, will the update take care of removing anything added to the unit by me ( Busybox for example)?
Thanks...philip
Sent from my Fire HDX.
Click to expand...
Click to collapse
It's very easy to unroot & get it back to stock with the AFTV Utility app. You don't need CWM. But I feel like a traitor telling you how... :crying: Sell or exchange the unit with someone stuck with a unrootable one. Make them pay for shipping for both units. Don't kill the root...
Let me know if you still want me to give you the step-by-step...

Y314K said:
It's very easy to unroot & get it back to stock with the AFTV Utility app. You don't need CWM. But I feel like a traitor telling you how... :crying: Sell or exchange the unit with someone stuck with a unrootable one. Make them pay for shipping for both units. Don't kill the root...
Let me know if you still want me to give you the step-by-step...
Click to expand...
Click to collapse
Sorry to make you feel bad, but it it's any consolation I sold a rooted Chromecast to someone who would make better use of it ( at the same price as an unrootable Chromecast). So, although I understand that this is a bit difficult, I would really appreciate the step-by-step process. I am currently running CWM, latest rooted firmware, busybox free, su, Amazon updates blocked. I would like them all gone via the process and the unit back to stock.
Thank you,
Philip

mroneeyedboh said:
If you want to unroot it, Id sell the one you have rooted ( since they are becoming like ghosts now ) and buy one with the money profited.
Click to expand...
Click to collapse
Not in it for any profit. Just like trying out different media players. They kind of come and go on a regular basis. But I do get the logic behind your suggestion.
The ability to return something to stock is important for everyone even if it were just a warranty issue ( not the case here though). I've seen quite a few threads on the subject for tablets and phones, just not the Fire TV.
The current Fire TV is pretty open as shipped. This is very different than the Apple TV situation or Chromecast where rooted units became priced at unbelievable levels. The main advantage of rooted FTV's seems to be centered around the USB port or turning it into an XBMC box with the Amazon GUI hidden.
Philip

pmcdunnough said:
Sorry to make you feel bad, but it it's any consolation I sold a rooted Chromecast to someone who would make better use of it ( at the same price as an unrootable Chromecast). So, although I understand that this is a bit difficult, I would really appreciate the step-by-step process. I am currently running CWM, latest rooted firmware, busybox free, su, Amazon updates blocked. I would like them all gone via the process and the unit back to stock.
Thank you,
Philip
Click to expand...
Click to collapse
NP... Also Linux sideloading is coming too... Along with custom kernels, overclocking, Rom's, etc... But they will all need rooot...
So what you do with the APP is...
Make sure you keep the update IP's blocked in your router if you want to root in the future.
Using the latest AFTV Utility Change Recovery to "recovery-stock-51.1.0.img"
This will kill root & it should restart the FTV to Stock Recovery. If not you can hit "Reboot to Recovery" in the app.
From the Stock Recovery do a Factory Reset & also a "clear cache" only. Then reboot the FTV & enjoy the startup video again.
You can do the Factory Reset from the Menu/System too. But you won't be able to clean the cache from there. The Factory Reset is what actually gets rid of any installed apps.
Then you should now have a back to stock AFTV. And you can choose to update to a non-rootable FW. Once you stop blocking the IP's...
You can find how to manually tell it to update in the System Menu.
I"ve never actually booted in the stock recovery so not sure what it looks like and if it has the same options as CWM. But if it doesn't you can go into Menu/System and do the Factory Reset from there.
You can clear cache & do Factory Reset from stock recovery..
{
"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"
}
Also to correctly close command promps with this app you sometimes need to hit CTRL+C to be able to input EXIT to close it.
NOTE: Since you mention you had CWM already... Here is a post that would help you wipe stuff thru CWM & Factory reset before unrooting thru the recovery shot.. WIll come out with an alternative way to fully clear cache's & format stuff in the future... ( http://forum.xda-developers.com/fire-tv/help/q-cwm-factory-reset-leaves-stuff-t2928521 ) The jest of it is you never format system unless you are ready to flash FW again before any reboot thru CWM.

pmcdunnough said:
Thanks. I had read that excellent guide before. It requires ClockworkMod and retains root if you select an appropriate firmware. This doesn't seem to restore a Fire TV to the state it was bought. For instance, ClockworkMod would still be there and perhaps even Amazon update blocking.
I should have been clearer with my intent. I would like to know how to restore a Fire TV to the state that it came when purchased. That is, I want to know how to remove any traces of me having touched it!
Sent from my Fire HDX.
Click to expand...
Click to collapse
As stated in the first sentence of that guide, it will "revert back to the stock recovery and stock software". In other words, ClockworkMod would be gone. Following that guide and doing a factory reset afterwards would leave the Fire TV in a fully stock state without root and without the update blocking.

AFTVnews.com said:
As stated in the first sentence of that guide, it will "revert back to the stock recovery and stock software". In other words, ClockworkMod would be gone. Following that guide and doing a factory reset afterwards would leave the Fire TV in a fully stock state without root and without the update blocking.
Click to expand...
Click to collapse
I had read the guide. I think I was confused by the meaning of stock recovery. I kept thinking that CWM would still be there as well as my modifications. My misunderstanding. Sorry about that.
Well now I have two ways to proceed. I guess applying both will guarantee I will never again be root
Philip
Sent from my Fire HDX.

pmcdunnough said:
I had read the guide. I think I was confused by the meaning of stock recovery. I kept thinking that CWM would still be there as well as my modifications. My misunderstanding. Sorry about that.
Well now I have two ways to proceed. I guess applying both will guarantee I will never again be root
Philip
Sent from my Fire HDX.
Click to expand...
Click to collapse
Both AFTVNews great guide & the AFTV Utility method are doing the exact same thing... You only need to choose one that you are most comfortable with. Specially since you can't unroot twice. All you would be doing by doing it twice is installing stock recovery on top of stock recovery...
Edited the instructions for your specific purpose.

kraqh3d said:
AFTVnews has a guide on returning to stock:
http://www.aftvnews.com/how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software/
Click to expand...
Click to collapse
Since XBMC/KODI is now an official app and the icon shows up on the home screen I don't feel the need to be rooted and have all the extra stuff installed. I followed this guide on both of my FTV's, worked great I'm back to stock like I wanted to be with the latest software installed. Netflix is updated and working great, it was stuck on an older version before. Best of all the 5ghz band stays connected now (2.4ghz was strong but 5ghz would not stay connected) and buffering on 1080p files is non existent.
My only issue now is that on one of my FTV boxes when I check for updates it throws an update error, I think I may have forgotten to "enable OTA updates" in the fire tv utility app before I removed SU, xposed, towel root, clockworkmod etc.. All router level update DNS blocks have been removed and my other FTV can scan for updates with no problem (I did remember to enable OTA updates in the fire tv utility app for this box). I can install apps, I'm just getting that error message when I scan for an update to the FTV software.
Am I screwed now? Will I not be able to get OTA updates in the future? Perhaps I need to do a factory reset to enable them?
Both are on:
51.1.4.3_user_514020320 stock software
51.1.3.0_user_513011520 stock recovery
Thanks in advance!

MxChris said:
Since XBMC/KODI is now an official app and the icon shows up on the home screen I don't feel the need to be rooted and have all the extra stuff installed. I followed this guide on both of my FTV's, worked great I'm back to stock like I wanted to be with the latest software installed. Netflix is updated and working great, it was stuck on an older version before. Best of all the 5ghz band stays connected now (2.4ghz was strong but 5ghz would not stay connected) and buffering on 1080p files is non existent.
My only issue now is that on one of my FTV boxes when I check for updates it throws an update error, I think I may have forgotten to "enable OTA updates" in the fire tv utility app before I removed SU, xposed, towel root, clockworkmod etc.. All router level update DNS blocks have been removed and my other FTV can scan for updates with no problem (I did remember to enable OTA updates in the fire tv utility app for this box). I can install apps, I'm just getting that error message when I scan for an update to the FTV software.
Am I screwed now? Will I not be able to get OTA updates in the future? Perhaps I need to do a factory reset to enable them?
Both are on:
51.1.4.3_user_514020320 stock software
51.1.3.0_user_513011520 stock recovery
Thanks in advance!
Click to expand...
Click to collapse
If you left updates disabled, a factory reset will clear it.

Both of my FTVs are crashing with Kodi

I have two FTVs both running old 51.1.1.0. Both of them have Kodi 14.2 and both crash shortly after I launch Kodi. They were both working fine and then both stopped working the same day. I thought there may have been an update, but that didn't happen. I can't figure it out and I'm really frustrated with these boxes. I'm ready to sell them and get something better. I can't even update them. Every way I try to update fails.
Any suggestions?

madtork said:
I have two FTVs both running old 51.1.1.0. Both of them have Kodi 14.2 and both crash shortly after I launch Kodi. They were both working fine and then both stopped working the same day. I thought there may have been an update, but that didn't happen. I can't figure it out and I'm really frustrated with these boxes. I'm ready to sell them and get something better. I can't even update them. Every way I try to update fails.
Any suggestions?
Click to expand...
Click to collapse
You have to provide a lot more info regarding your boxes. I am assuming your boxes are rooted or you blocked updates in your router because this is a very old firmware and if so you will not be able to update them over the air without enabling OTA updates.
Start here and read before you do anything (you can still keep root and update to latest OS3 s/w): http://www.aftvnews.com/start/

bula1ca said:
You have to provide a lot more info regarding your boxes. I am assuming your boxes are rooted or you blocked updates in your router because this is a very old firmware and if so you will not be able to update them over the air without enabling OTA updates.
Start here and read before you do anything (you can still keep root and update to latest OS3 s/w): http://www.aftvnews.com/start/
Click to expand...
Click to collapse
They both are rooted. I'm just trying to update Kodi. I thought it would be best to keep the old firmware. I've used the Windows utility app to try and install the new version of Kodi as well as the fire installer on an android phone. Nothing seems to work. This is the way I've always done it. Let me know what other information I can provide.

Not sure why you want to keep an older firmware (newer versions bring fixes and improvements) but that is up to you. Have you installed something on both units that lead to the system crash? It is very weird that both units stopped working at the same time. Have you try to clean cache (not data) and run kodi again? If this does not work do a back up, uninstall kodi, reset firetv, reinstall whatever version of kodi you like and run it (do not restore you back up yet) if all is good (opens up) exit kodi and restore your back up. If it still does not open then something got corrupted in your data files and you will have to reinstall everything from scratch.

bula1ca said:
Not sure why you want to keep an older firmware (newer versions bring fixes and improvements) but that is up to you. Have you installed something on both units that lead to the system crash? It is very weird that both units stopped working at the same time. Have you try to clean cache (not data) and run kodi again? If this does not work do a back up, uninstall kodi, reset firetv, reinstall whatever version of kodi you like and run it (do not restore you back up yet) if all is good (opens up) exit kodi and restore your back up. If it still does not open then something got corrupted in your data files and you will have to reinstall everything from scratch.
Click to expand...
Click to collapse
I've tried clearing cash. The reason I didn't take an OTA update for firmware is because I thought I couldn't root the newer versions.

madtork said:
I've tried clearing cash. The reason I didn't take an OTA update for firmware is because I thought I couldn't root the newer versions.
Click to expand...
Click to collapse
You can still update to latest firmware (using rbox prerooted images). Follow link I posted above and read, read, read before you do anything.

I think the same as bula1ca write down here.
First update to the last availible prerooted rom. Read it here how to do: http://www.aftvnews.com/start/
Another question from my side is: Why did you use kodi 14.2.
kodi 16 jarvis is availible and you can use it as launcher too with a pythin script here from the board.
Feel free to ask your question but please read enough before
Greetings by Idijt

Update to latest firmware OTA Update Without Losing Magisk (Root Permissions)

Hello,
Only Few days ago, we received the new OTA Update for our OnePlus 8 Pro devices,
notifying us to upgrade to the latest available stable version (11.0.4.4) from the older version 11.0.3.3.
with such great expectations based on update log.
{
"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"
}
As we're testing whether there are enough improvements in the latest update or not..
Let me share with you, how to update to the latest OTA update on a rooted OnePlus device..
Using magisk manager .. for magisk-rooted devices (without custom recovery of course) ..
First we check the new update notification in notification bar, and go to download the new update ..
if you didn't get that notification.. go to settings and check for updates manually
start to Download the update - the device will tell you that because of having a rooted device.. the software version will be downloaded as a full package from the start.. not just the update package ..
that's why it will be around 4.00 Gbs.
while waiting for the update to finish .. make sure your magisk manager is uptodate
and now return to ur update progress bar..
SOFTWARE Update Download finishes. Click on Install NOW to install the newest OTA update...
Make Sure ur device is charged at least 20% - Click Install
After Installation is Complete, DONT REBOOT ur device as it offers in the bottom of the screen
Now Go to magisk manager application once more..
choose install or update (as depicted).
choose the last option (install to inactive slot (after OTA) )
Agree to the warning that appears by clicking OK
Now it finishes flashing the new patched_boot to the inactive slot which will be master one after reboot.
Now click reboot .. and voila you have the new update without losing magisk..
Thanks for reading.
until we meet in another tutorial.. goodbye..
​

appreciate it

Thanks for your tutorial

Have had this tutorial up for over a year.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
Maybe read next time before putting so much effort in.

Doesn't work for me - in Android 11 OnePlus Updater doesn't offer downloading full update - it just instantly fails on rooted devices.

okgnew said:
Doesn't work for me - in Android 11 OnePlus Updater doesn't offer downloading full update - it just instantly fails on rooted devices.View attachment 5227685
Click to expand...
Click to collapse
You should just use oxygen updater bud

Deleted.

How has this process changed with Magisk 22.0 Since I can choose Install to Inactive Slot (After OTA) but hitting Let's Go does nothing?

update instantly fails for me too....I would use oxygen updater but...it's not available on there.

cali310 said:
update instantly fails for me too....I would use oxygen updater but...it's not available on there.
Click to expand...
Click to collapse
Same problem here, I have the OTA notification for 11.0.5.5 but I can't install it, not on Oxygen Updater either. Wish there was a way to get the file off my phone that failed to install so I could try a local upgrade myself.

I installed the update via local update, but I forgot to uninstall Magisk first, what should I do now? Should I continue with install to inactive slot or I pretty much lose the root and after start from scratch? Thanks!

marvyzoro said:
I installed the update via local update, but I forgot to uninstall Magisk first, what should I do now? Should I continue with install to inactive slot or I pretty much lose the root and after start from scratch? Thanks!
Click to expand...
Click to collapse
You shouldn't have uninstalled magisk, just disabled modules.
Yes install to active slot, provided you didn't reboot after the update.
If you rebooted then you'll need to boot (via fastboot) the patched image then install directly via magisk.
Let me know if you get stuck.

Thank you dladz. I went ahead and select the Install to inactive slot after OTA. It flashed and rebooted and it came back, but even after I locally installed beta 8, it came back as beta 7.
dladz said:
You shouldn't have uninstalled magisk, just disabled modules.
Yes install to active slot, provided you didn't reboot after the update.
If you rebooted then you'll need to boot (via fastboot) the patched image then install directly via magisk.
Let me know if you get stuck.
Click to expand...
Click to collapse

OK, I did the step one more time, installed the update follow with Magisk install to active slot. This time it came back updated to Beta 8 with root. Thanks!

The part that I am confused is that I didn't uninstall or disable the Magisk module before install the oneplus update as some other posts suggested that needs to be done first.

marvyzoro said:
The part that I am confused is that I didn't uninstall or disable the Magisk module before install the oneplus update as some other posts suggested that needs to be done first.
Click to expand...
Click to collapse
You don't have to but if a module requires a specific part of an OS like OPSystemUI.apk in my center clock mod's case, then you'll enter a bootloop.
However depending on the module you may be absolutely fine, so it's more of a fail-safe rather than anything else..

Can someone post the entire update file?

Hi! So today I got a notice of an update for 11.0.5.5.IN11AA on my IN2025 (8 Pro) which is rooted (I did mine by doing the download boot.img, patch with magisk, then flash with adb/fastboot on unlocked phone).
Looks like there's something different about the new update? I tried the process above and here's what happens:
Click "Download and install" button in update screen
Almost immediately you get a "Installation will continue when device isn't being used. To install now, tap Resume" error at the top.
Click "Resume" button in update screen.
Again almost immediately, get "Installation problem" error at top and button is now "Try again"
Try again just repeats the scenario. I have noticed a lot of OnePlus website pages, even my trade in page where I'm supposed to accept my trade in value, are throwing errors too. Maybe it's just a OnePlus server issue?

wesblake said:
Hi! So today I got a notice of an update for 11.0.5.5.IN11AA on my IN2025 (8 Pro) which is rooted (I did mine by doing the download boot.img, patch with magisk, then flash with adb/fastboot on unlocked phone).
Looks like there's something different about the new update? I tried the process above and here's what happens:
Click "Download and install" button in update screen
Almost immediately you get a "Installation will continue when device isn't being used. To install now, tap Resume" error at the top.
Click "Resume" button in update screen.
Again almost immediately, get "Installation problem" error at top and button is now "Try again"
Try again just repeats the scenario. I have noticed a lot of OnePlus website pages, even my trade in page where I'm supposed to accept my trade in value, are throwing errors too. Maybe it's just a OnePlus server issue?
Click to expand...
Click to collapse
If its incremental then it won't work that way..
It needs to be a full update.
If it is a full update, then just take the update locally, then run the OTA install on magisk

Thanks. Was able to follow the guide to update my phone today.

Rooted Firestick 4K reboots after opening Prime Video

My 4k firestick is attached to my Sony Android TV and I haven't tried using Prime Video on the Firestick for quite some time as I usually watch Prime Video via Android TV on the Sony. When I recently tried Amazon Prime on the Firestick I had audio for about 10 seconds but no video and the the Firestick rebooted. On a second try there was 10 seconds or so of audio and no video and then the firestick froze. There was no response to any button on the controller and I had to physically disconnect power to get it to reboot. I'm on the latest version 6.2.8.1 of the OS.
My firestick is rooted and I've extended the internal memory onto a USB. I have also installed the Launcher Manager and the Wolf launcher.
Oddly, Amazon Prime will play trailers but not the main video ?? Other streaming sources such as the BBC iPlayer work fine.
Has anyone else experienced this or can offer an explanation/fix for this ?

This is discussed in other forum post also,
Just update TZ via twrp.
Download TWRP flash package from
Fire TV Stick 4K 6.2.8.1 r3_4054 Fully Patched Rom
Here's the latest release 6.2.8.1_r3_4054 of the pre-rooted rom I've combined into one patched ota removed zip which packs the downgraded older interface with accessibility settings working again. After flashing, clear data in...
forum.xda-developers.com

Thank you for your prompt response. In the meantime I installed mantis-6.2.8.1-rooted_r2.zip but it has led to the disappearance of TWRP so I can't try your solution. Thank you all the same.

fourlans said:
Thank you for your prompt response. In the meantime I installed mantis-6.2.8.1-rooted_r2.zip but it has led to the disappearance of TWRP so I can't try your solution. Thank you all the same.
Click to expand...
Click to collapse
Flashing rbox's prerooted rom in no was can remove your TWRP.
If you flashed his rom on top of older roms (i.e <8.0) then your efuse should be intact. By judging that you are able to boot your stick means you haven't performed any modifications. Also means you haven't disabled OTA on your stick.
I think you should try to unlock once again, after that disable OTA.

SweenWolf said:
Flashing rbox's prerooted rom in no was can remove your TWRP.
If you flashed his rom on top of older roms (i.e <8.0) then your efuse should be intact. By judging that you are able to boot your stick means you haven't performed any modifications. Also means you haven't disabled OTA on your stick.
I think you should try to unlock once again, after that disable OTA.
Click to expand...
Click to collapse
I'll try the unlock again. Thanks again for your advice