Related
Hello to anyone who decides to read this, and thank you for taking the time to haha.
I'm new here, and I'm relatively new to the whole rooting and modding scene, although I'm pretty confident in using Odin and various software involved in this, so, hopefully this won't be too complicated.
I have a question about my Note 10.1 2014. I have the WiFi model (P6000), which was bought in China since I was a student there for a year. Now I'm back in England. I flashed my ROM to a UK version so I could use Google Play services and Facebook integration, along with several other features and services which are blocked in China for various reasons. Now, my problem is, I have no real reason to have a rooted device other than for this. I also know I didn't need to root my device to flash the ROM, but I had some problems with my keyboard in China, but I have since solved them and have no use for the root. I want to take advantage of OTA updates since apparently my device should have one, but I can't because I'm rooted. Is it at all possible to unroot and lock the bootloader so I can update, without losing the ROM flash that is making my device run the UK firmware? If so, how would I go about doing this on my device? If it's not possible, is there are method in which I can update my firmware?
Sorry if I'm a little clueless about this stuff, and thanks in advance.
haofeng93 said:
Hello to anyone who decides to read this, and thank you for taking the time to haha.
I'm new here, and I'm relatively new to the whole rooting and modding scene, although I'm pretty confident in using Odin and various software involved in this, so, hopefully this won't be too complicated.
I have a question about my Note 10.1 2014. I have the WiFi model (P6000), which was bought in China since I was a student there for a year. Now I'm back in England. I flashed my ROM to a UK version so I could use Google Play services and Facebook integration, along with several other features and services which are blocked in China for various reasons. Now, my problem is, I have no real reason to have a rooted device other than for this. I also know I didn't need to root my device to flash the ROM, but I had some problems with my keyboard in China, but I have since solved them and have no use for the root. I want to take advantage of OTA updates since apparently my device should have one, but I can't because I'm rooted. Is it at all possible to unroot and lock the bootloader so I can update, without losing the ROM flash that is making my device run the UK firmware? If so, how would I go about doing this on my device? If it's not possible, is there are method in which I can update my firmware?
Sorry if I'm a little clueless about this stuff, and thanks in advance.
Click to expand...
Click to collapse
What rom version you're running right now? Do you have a full UK factory firmware 4.4 available?
buhohitr said:
What rom version you're running right now? Do you have a full UK factory firmware 4.4 available?
Click to expand...
Click to collapse
Sorry for the late response, I was travelling.
I'm not entirely sure haha. Here's my device info, does this explain my situation?
As for the second question, I'm not entirely sure what you mean? I looked for the firmware for flashing but couldn't find a Android 4.4 version, despite my device telling me I have an available update and the internet saying my device should be updated to 4.4?
haofeng93 said:
Sorry for the late response, I was travelling.
I'm not entirely sure haha. Here's my device info, does this explain my situation?
As for the second question, I'm not entirely sure what you mean? I looked for the firmware for flashing but couldn't find a Android 4.4 version, despite my device telling me I have an available update and the internet saying my device should be updated to 4.4?
Click to expand...
Click to collapse
OK, you have 4.3 and waiting for 4.4 OTA update. If you open your SuperSU app, then go to settings, scroll down to "Full unroot", select that and it should unroot. After done reboot your device and verify that the SuperSU is no longer in your app draw. I don't know if you modify anything else on your device like build.props or installed any rooted apps, if you do you need to remove them ALL, unfreeze any system apps using Titanium backup and revert build.props back to factory original, BEFORE YOU UNROOT. Once everything done you should be ok to take the OTA update. The OTA update will not erase your data so you should be fine there.
buhohitr said:
OK, you have 4.3 and waiting for 4.4 OTA update. If you open your SuperSU app, then go to settings, scroll down to "Full unroot", select that and it should unroot. After done reboot your device and verify that the SuperSU is no longer in your app draw. I don't know if you modify anything else on your device like build.props or installed any rooted apps, if you do you need to remove them ALL, unfreeze any system apps using Titanium backup and revert build.props back to factory original, BEFORE YOU UNROOT. Once everything done you should be ok to take the OTA update. The OTA update will not erase your data so you should be fine there.
Click to expand...
Click to collapse
Thanks for the speedy reply. I tried to option within SuperSU, but it seems to have been uninstalling for about 15 minutes with no result. I realised that I froze the stock Samsung keyboard since it overtakes the Google Chinese Pinyin Input when using a keyboard, and I work primarily in Chinese. Could this be the reason why the uninstall seems to have failed or got stuck? Not sure what to do now, oops.
haofeng93 said:
Thanks for the speedy reply. I tried to option within SuperSU, but it seems to have been uninstalling for about 15 minutes with no result. I realised that I froze the stock Samsung keyboard since it overtakes the Google Chinese Pinyin Input when using a keyboard, and I work primarily in Chinese. Could this be the reason why the uninstall seems to have failed or got stuck? Not sure what to do now, oops.
Click to expand...
Click to collapse
Did you read my instructions?? you must un-freeze all the system apps first before unroot otherwise the OTA may failed. Let it sits for another 10 min then reboot your phone and check to see root has been removed.
buhohitr said:
Did you read my instructions?? you must un-freeze all the system apps first before unroot otherwise the OTA may failed. Let it sits for another 10 min then reboot your phone and check to see root has been removed.
Click to expand...
Click to collapse
Yeah, I did read the instructions. It was just a moment of stupidity on my behalf, completely forgot I'd frozen the stock keyboard. I'll leave a little longer and then reboot.
buhohitr said:
Did you read my instructions?? you must un-freeze all the system apps first before unroot otherwise the OTA may failed. Let it sits for another 10 min then reboot your phone and check to see root has been removed.
Click to expand...
Click to collapse
Well, it seems to have gone a little weird. I have no root access anymore but SuperSU is still installed and my device status is still custom, so the OTA update won't run. I'm guessing I ought to reroot and properly clear out/unfreeze stuff, right? Sorry for being a pain haha...
haofeng93 said:
Well, it seems to have gone a little weird. I have no root access anymore but SuperSU is still installed and my device status is still custom, so the OTA update won't run. I'm guessing I ought to reroot and properly clear out/unfreeze stuff, right? Sorry for being a pain haha...
Click to expand...
Click to collapse
You need to remove the SuperSu app by go to playstore search for Supersu then you should see the uninstall option. The OTA failed probably because it detected that you have modified the system. You need to think what you did to your system and revert back before try again. I would just use towelroot app and reroot then unfreeze any frozen apps, then uninstall then try again. If you can't remembered what you did and the OTA stills failing, then the next step is use Odin and flash factory firmware either 4.3 or 4.4. Remember to read my instructions before and ask if in doubt before taken any action. After you re-root, make sure you use Titanium to run a full backup of all your userapps. if you don't want to be bother, then just use Odin to flash either 4.3 or 4.4 but you need to re setup and re-download all your apps.
I have tried to follow the instructions for the Kindle Fire but that is not working and I have not found a thread that specifically gives directions on how to install and make the google play store work on this device.
I have downgraded my software and rooted my phone so that step is done.
I have attempted to follow the directions in downloading and using ES File.
I have downloaded many versions of the play store and play services but all seem to crash or give errors at some point. Please help!!!
I need google play!!
Did you install xposed framework and hdxposed? (You have to open xposed, install itself and activate hdxposed)
Installed HDXPOSED
Ok i installed xposed and activated hd xposed now what?
Follow this guide, it works. (it is in this forum)
[GUIDE] Make FireOS looks and feel like normal android
Normally all things should work now when you follow my guide.
http://forum.xda-developers.com/showthread.php?t=2898921
If you have questions you can ask me directly
So if I have version 3.6.5 (AT&T) will this work?
You Need Root first
gino23 said:
So if I have version 3.6.5 (AT&T) will this work?
Click to expand...
Click to collapse
You gotta downgrade to 3.5.0 first then factory reset, then download towel root and root the phone, install SU, disable OTA, then Xposed...
Disable OTA is not necessary when installing xposed with hdxposed
Kevinreid1 said:
You gotta downgrade to 3.5.0 first then factory reset, then download towel root and root the phone, install SU, disable OTA, then Xposed...
Click to expand...
Click to collapse
Would you happen to know where to get specific directions for the above? I've done the UNLOCKED fire phones (that was easy to install Google Apps), but I bought 1 used Fire Phone that was locked to AT&T and has 3.6.5 and the procedure I'm used to just doesn't work (constant gapps crashing).
Also, I did SIM unlock this phone...can i update it to 3.6.8 or is it stuck on 3.6.5 regardless?
Thanks!
lancorp said:
Would you happen to know where to get specific directions for the above? I've done the UNLOCKED fire phones (that was easy to install Google Apps), but I bought 1 used Fire Phone that was locked to AT&T and has 3.6.5 and the procedure I'm used to just doesn't work (constant gapps crashing).
Also, I did SIM unlock this phone...can i update it to 3.6.8 or is it stuck on 3.6.5 regardless?
Thanks!
Click to expand...
Click to collapse
After I downgraded I had apps crashing to, to fix that you will have to do a factory reset, since the reset I have had no crashes. Every thing I have read says do not upgrade if you want root access, but you can downgrade and root anything up to 3.6.8, my even include 3.6.8 but to a search to make sure, root is on 3.5.0 and after root you can not upgrade and keep root..
Kevinreid1 said:
After I downgraded I had apps crashing to, to fix that you will have to do a factory reset, since the reset I have had no crashes. Every thing I have read says do not upgrade if you want root access, but you can downgrade and root anything up to 3.6.8, my even include 3.6.8 but to a search to make sure, root is on 3.5.0 and after root you can not upgrade and keep root..
Click to expand...
Click to collapse
I didn't downgrade. It was my understanding the AT&T locked phones are at 3.6.5 and unlocked are at 3.6.8 and the two are not compatible (you can't upgrade a locked phone to 3.6.8).
I'm not interested in rooting, but just want the simple GAPPS install experience I had with my unlocked 3.6.8 phone.
By factory reset, you mean wipe it?
Hi all, I've had Fire TV 1's and rooted them since the day they got rooted, the main thing I use them for is Kodi and as a launcher.
I followed zeroepoch's thread and attempted root in windows but it stopped midway through, not bricked or anything, the only thing I noticed is I could not check for updates anymore (I did not disable the ota service or block in router or anything) since no root access at that point. Well I decided to spin up an Ubuntu VM and use linux to root (MUCH faster/easier btw!) I followed the video guide posted here (Thanks!) and it was a breeze.
Here's my question now though, I want to update to 5.0.4. @AFTVnews.com posted a topic about 5.0.4 but had suggessted unrooting first, then upgrading officially, then re-rooting. I"m good with doing this, I'm sure it will take some time to complete but that's fine. I'm just not sure how to go about doing this. I have kept my linux box VM, is there a guide I missed or anything? I'm sure it's similar to the rooting process I just want to make sure I do it right, don't want a brick.
Also with FTV1, xposed was working and rbox module to override launcher and this is what I used a lot of, as well as modified Kodi Confluence skin from @elmerhueso. I know xposed is not yet up and running on ftv2 but for those running Kodi, is Firestarter the best launcher replacement, even with root? Last question is, I noticed team Kodi dropped libstagefright in Jarvis, this was a major problem for the FTV1 as is was a regression in some video playback as mediacodec is not quite as mature. Is this still the case with FTV2? Or what is the reccomended version of Kodi everyone is using?
Thanks for everyones help, without your work the fire tv would be nowhere compared to what it is now!
P.S. - Any other Root programs/tips&tricks for the FTV2 now that I've successfully rooted, I'd love to hear what others are using root for on their FTV2.
I use the latest stable version of Kodi 15.2, running Konfluence skin (modded confluence), get yourself a Logitech K400 plus keyboard their great & have also a mouse touch pad (make sure you unable us debugging or your usb socket won't work). Their isn't a proper guide yet I've looked! We will have to wait I'm sure it won't be long? Their is a quick upgrade in the forums but also some have reported bricks with the "quick upgrade" , so for me I'm not taking the risk just yet, I'd rather do a longer flash of my AFTV2 than a super quick flash & end up with a "brick".
Skater4599 said:
Here's my question now though, I want to update to 5.0.4. @AFTVnews.com posted a topic about 5.0.4 but had suggessted unrooting first, then upgrading officially, then re-rooting. I"m good with doing this, I'm sure it will take some time to complete but that's fine.
Click to expand...
Click to collapse
Just enable OTA via package manager then install the 5.0.4 update. It will unroot your device and you have a stock 5.0.4. Then just root as you did for 5.0.3. There is no reason/need to go to stock 5.0.4 and then rerooting. I've done 3 devices with exactly this method, no issues.
I'm sure it's safe but I would rather wait for an official guide than take a risk
Sent from my SM-G900F using Tapatalk
Thanks everyone!
Good info here, I'm glad to hear that re-enabling the OTA is "safe" to just go ahead and update and re-root, I thought there might be something else needed but I aired on the side of caution as I'm pretty new to the FTV2 and the rooting method used for it.
Your tips/input is much appreciated!
Skater4599 said:
Thanks everyone!
Good info here, I'm glad to hear that re-enabling the OTA is "safe" to just go ahead and update and re-root, I thought there might be something else needed but I aired on the side of caution as I'm pretty new to the FTV2 and the rooting method used for it.
Your tips/input is much appreciated!
Click to expand...
Click to collapse
I don't know about OTA'ing from 5.0.3 to 5.0.4 being "safe". It SEEMS to work... but I still have some reservations about it.
rbox said:
I don't know about OTA'ing from 5.0.3 to 5.0.4 being "safe". It SEEMS to work... but I still have some reservations about it.
Click to expand...
Click to collapse
Same here, I recall from previous experiences in the past with many rooted devices (mainly phones or consoles) that in most cases that you don't install OTA updates straight from a rooted device because 9/10 times It leads to Bricks! Now I don't know if this would be the same with the AFTV2 but I'd unroot then install the OTA & then reroot.
Sent from my SM-G900F using Tapatalk
deanr1977 said:
Same here, I recall from previous experiences in the past with many rooted devices (mainly phones or consoles) that in most cases that you don't install OTA updates straight from a rooted device because 9/10 times It leads to Bricks! Now I don't know if this would be the same with the AFTV2 but I'd unroot then install the OTA & then reroot.
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
There any instructions to do this? I would rather do it the safer method, dont care if it takes longer thats ok. Im not sure how to full unroot, use an app or reflash stock image or something? Thanks again
Skater4599 said:
There any instructions to do this? I would rather do it the safer method, dont care if it takes longer thats ok. Im not sure how to full unroot, use an app or reflash stock image or something? Thanks again
Click to expand...
Click to collapse
Hopefully someone will provide a full working guide very soon, it is almost Xmas so I can't see anyone putting a guide up anytime this week? Or Amazon doing another update until at least the end of January? So we will have to just wait. Ask in the main Root thread for AFTV2 if you like?
Sent from my SM-G900F using Tapatalk
http://forum.xda-developers.com/fire-tv/general/root-update-5-3-0-1-to-5-0-4-3-min-t3277997 @aboshi posted this 5.0.3.1 to 5.0.4 guide. It's not an official OTA update but a few people have used it with success.
gen3benz said:
http://forum.xda-developers.com/fire-tv/general/root-update-5-3-0-1-to-5-0-4-3-min-t3277997 @aboshi posted this 5.0.3.1 to 5.0.4 guide. It's not an official OTA update but a few people have used it with success.
Click to expand...
Click to collapse
Cheers mate I've seen this already & as tempting as a 3-5min flash upgrade I think I'd rather be safer with the longer root process than the quicker one, I'm not gonna jump in feet first when rooting (especially when we have no recovery yet).
Sent from my SM-G900F using Tapatalk
I hear ya man. I havent tried it either. Im happy with my flawless kodi streaming from my pc to my ftv and phone. Dont really see a need for the 5.0.4 update myself, since i use Firestarter anyways. Cheers bud and merry xmas.
I have a 4k fire TV box and have kodi installed etc,what's the benefits of rooting them
More features, mod the look of stuff, have more control over everything, if in the future Amazon blocks kodi, if your on an earlier update (custom firmware) you maybe able to still use (because we block the ota updates with root), get rid of ads in apps, more accessories options/mods, the list goes on.
Sent from my SM-G900F using Tapatalk
Hi all,
I'd previously rooted, installed recovery, etc on my FireTV version 1. Everything was working great, and I thought I'd disabled updates. I turned it on recently and It somehow lost root. Everything is still installed, but can't open SuperSU, towelroot says the device isn't supported. Still says that Xposed is installed with the framework though.
The system says I'm now on 51.1.4.1_user_514013920 for some reason. Checking for system update still gives an error. What went wrong, and is there any way to fix it?
@AFTVNews, I'm mainly looking at you
Does anyone know?
If you disabled updates its probably the fact that the fire tv has updated its self, im afraid thats why su (root) isnt working & your device isn't supported because your firmware has upgraded. You have no way to root at the moment in time unless a os5 root for AFTV gen1 is created sometime in the near future? It is possible because Rbox is making a Os5 root for Gen 1.... But i think you need root already for that? My advice would be if you still want root, get a AFTV 2 while root is still possible & root/block updates & wait for the new recovery & rom being developed by Rbox which fingers crossed should be very near to be released. I still cant get over why you would want to unblock updates for when you had root & exposed framework? oh well whats done is done now.
If this helps press that thanks button
If he install clockword mod and if he can still get into it, couldn't he flash the latest rom and get root back?
That's very confusing?
Disabling updates should've been the first thing you did after rooting (presumably a long time ago if you have gen 1.)
Disabling updates, successfully or not, shouldn't've caused you to lose root. If you have CWM, your aftv should not be able to receive a stock update. Of course towel root won't work because your firmware is based on stock software that is not rootable. Are you certain you did nothing else other than disable updates?
I'm basing all of this off the assumption you have CWM. If so then just push the same firmware you currently have installed to /sdcard and flash it again. Install busybox and I'd think you'd be ok. You probably already know this but aftvnews has all rbox's prerooted roms.
Maybe you only disabled ota on your router? Have you taken it anywhere else? Or got a new router?
Sent from my SM-G900F using Tapatalk
Yes, I disabled updates when I first rooted. I did this on the firetv, not my router. I followed @aftvnews guide to do it, and it worked perfectly. I'm not looking to get another device, but to restore this one. I still have cwm, busybox, supersu all installed (I think I still have cwm, don't remember how to boot to it). I still don't believe you can just flash a rooted rom over top...
ldeveraux said:
Yes, I disabled updates when I first rooted. I did this on the firetv, not my router. I followed @aftvnews guide to do it, and it worked perfectly. I'm not looking to get another device, but to restore this one. I still have cwm, busybox, supersu all installed (I think I still have cwm, don't remember how to boot to it). I still don't believe you can just flash a rooted rom over top...
Click to expand...
Click to collapse
If the firmware has gone to an updated latest unrootable firmware I'm sure what ever you flash onto it will brick your device even if you do have cwm?
Sent from my SM-G900F using Tapatalk
deanr1977 said:
If the firmware has gone to an updated latest unrootable firmware I'm sure what ever you flash onto it will brick your device even if you do have cwm?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Yeah that's what I assumed. I thought it might be too far gone. Was hoping AFTVnews might see this and offer advice.
ldeveraux said:
Yeah that's what I assumed. I thought it might be too far gone. Was hoping AFTVnews might see this and offer advice.
Click to expand...
Click to collapse
You're not understanding. First, the firmware you have MUST have boot menu installed. Therefore you can choose to boot recovery from there. OR connect adb and reboot recovery. Adbfire simplifies this...
You should be fine to flash a prerooted rom and it should fix whatever got messed up.
Again, theres NO way youre running stock because im fairly certain rbox's recovery wont allow the installation. Theres an issue with you su no doubt but im thinking youre still rooted.
Sorry I missed this thread until now. Do you know what version pre-rooted ROM you had installed last? You say it's on 51.1.4.1, but are you positive that is not the version it was always on? If by some strange way it did install a stock update, there's no way it would have updated to 51.1.4.1 since Amazon is pushing 51.1.6.3 to all devices now. Just because you can't open SuperSU doesn't mean you lost root. What happens when you connect via ADB and enter the "su" command? Is your bootloader unlocked? Here's how to check.
AFTVnews.com said:
Sorry I missed this thread until now. Do you know what version pre-rooted ROM you had installed last? You say it's on 51.1.4.1, but are you positive that is not the version it was always on? If by some strange way it did install a stock update, there's no way it would have updated to 51.1.4.1 since Amazon is pushing 51.1.6.3 to all devices now. Just because you can't open SuperSU doesn't mean you lost root. What happens when you connect via ADB and enter the "su" command? Is your bootloader unlocked? Here's how to check.
Click to expand...
Click to collapse
Huh, looks like everything is still good. I ADB in and "su" still shows [email protected] I guess I still have root and unlocked bootloader. I disabled automatic updates again just in case, it says "Package com.android.dcp new state: disabled". I feel like I should update the the ROM though as my install is feeling a bit awkward. Is there a guide on AFTVnews?
EDIT: I just checked and I don't have RBOX's Boot Menu installed. Does that mean I should downgrade to 51.1.4.0, install the boot menu, then upgrade the ROM in that order?
ldeveraux said:
Huh, looks like everything is still good. I ADB in and "su" still shows [email protected] I guess I still have root and unlocked bootloader. I disabled automatic updates again just in case, it says "Package com.android.dcp new state: disabled". I feel like I should update the the ROM though as my install is feeling a bit awkward. Is there a guide on AFTVnews?
EDIT: I just checked and I don't have RBOX's Boot Menu installed. Does that mean I should downgrade to 51.1.4.0, install the boot menu, then upgrade the ROM in that order?
Click to expand...
Click to collapse
Yes, install 51.1.4.0, then install the boot menu, then install 51.1.6.3
AFTVnews.com said:
Yes, install 51.1.4.0, then install the boot menu, then install 51.1.6.3
Click to expand...
Click to collapse
Hey cool everything works.
Only issue right now is the google play store. I installed it as in your guide, but it keeps updating and won't work at all on version 6.0.5. I saw this user UnderXP (http://forum.xda-developers.com/fire-tv/help/how-to-disable-google-play-store-auto-t3135642/page2) who used XPrivacy to stop the storee/services from auto updating. I've had no luck at it.
What do you recommend?
ldeveraux said:
Hey cool everything works.
Only issue right now is the google play store. I installed it as in your guide, but it keeps updating and won't work at all on version 6.0.5. I saw this user UnderXP (http://forum.xda-developers.com/fire-tv/help/how-to-disable-google-play-store-auto-t3135642/page2) who used XPrivacy to stop the storee/services from auto updating. I've had no luck at it.
What do you recommend?
Click to expand...
Click to collapse
I haven't looked into the Google Play Store in a while. I plan to update my guide once Fire OS 5 is released to older devices, since any changes I make now likely won't work after the update.
Hi all,
I know this may seem like a n00b question, but I hope you can point me in the right direction. I have a A320FL with Android 6.0.1 - build june 28 2017, and I blocked the auto update feature, because back then I read about the advanced locking technique and want to root my phone. Since then I looked at these forums, but found it quite difficult to gather all the information to get confident enough to flash/root my phone. In the past I rooted/flashed my Sony Z1c regularly and that was easy. But for some reason flashing the A320 seems much more difficult, with more chances for it to go wrong.
I'd like to have the following:
- Android Oreo stock, twrp, rooted and Xposed (optional if possible)
I found this thread about rooting and twrp and xposed, but it's an older manual for Android 7 and I don't know if it will also work with Oreo.
Other threads talk about unlock and the security path, but I'm not sure if it applies to my situation, or not? (since I have an older installation, perhaps the advanced locking technique isn't implemented)
Any help is appreciated. Thanks.
hatsikidee said:
Hi all,
I know this may seem like a n00b question, but I hope you can point me in the right direction. I have a A320FL with Android 6.0.1 - build june 28 2017, and I blocked the auto update feature, because back then I read about the advanced locking technique and want to root my phone. Since then I looked at these forums, but found it quite difficult to gather all the information to get confident enough to flash/root my phone. In the past I rooted/flashed my Sony Z1c regularly and that was easy. But for some reason flashing the A320 seems much more difficult, with more chances for it to go wrong.
I'd like to have the following:
- Android Oreo stock, twrp, rooted and Xposed (optional if possible)
I found this thread about rooting and twrp and xposed, but it's an older manual for Android 7 and I don't know if it will also work with Oreo.
Other threads talk about unlock and the security path, but I'm not sure if it applies to my situation, or not? (since I have an older installation, perhaps the advanced locking technique isn't implemented)
Any help is appreciated. Thanks.
Click to expand...
Click to collapse
You should just be able to enable OEM unlock, flash TWRP, format data in TWRP, flash no-verity- noencrypt zip, and you should be fine I think.
Okay, and then flash the last stock rom and then Magisk for root?
hatsikidee said:
Okay, and then flash the last stock rom and then Magisk for root?
Click to expand...
Click to collapse
If you want to be on the latest update, then do it before you root. But yes, then you flash magisk after the rom after you got TWRP.. Make sure you boot up once or more before you flash magisk.