Related
So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse
Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse
Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse
Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.
So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?
Let's make this quick. Received nougat update, decided to root device, nougat version is nrd90r, twrp recovery version is 3.0.2-2, superSU tells me that I properly have root, root apps ask for root, the root apps never end up working and now I just want lollipop back. Tried cm 13 nightly but the zip file errors every time and I've downloaded it many times. Can someone give me some help. All I need is a rooted phone that works with Xposed. Thanks in advance for the help
randallrbaker said:
Let's make this quick. Received nougat update, decided to root device, nougat version is nrd90r, twrp recovery version is 3.0.2-2, superSU tells me that I properly have root, root apps ask for root, the root apps never end up working and now I just want lollipop back. Tried cm 13 nightly but the zip file errors every time and I've downloaded it many times. Can someone give me some help. All I need is a rooted phone that works with Xposed. Thanks in advance for the help
Click to expand...
Click to collapse
right now xposed isn't compatible with nougat anyway.
to got back to M or L follow section 11 of this guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
after that you can install twrp, supersu and xposed again.
I kNow nougat doesn't have Xposed yet and I was content with waiting it out but root doesn't even work. And I have some Google app that need to be removed lol. Thanks for the help I'll get back to you on the process!
randallrbaker said:
Let's make this quick. Received nougat update, decided to root device, nougat version is nrd90r, twrp recovery version is 3.0.2-2, superSU tells me that I properly have root, root apps ask for root, the root apps never end up working and now I just want lollipop back. Tried cm 13 nightly but the zip file errors every time and I've downloaded it many times. Can someone give me some help. All I need is a rooted phone that works with Xposed. Thanks in advance for the help
Click to expand...
Click to collapse
It isn't that root isn't working, is that the apps your using need an update on how they call su. Su has changed with Android n and some things need updates to support it
Sent from my SHIELD Tablet K1 using Tapatalk
@rbox Hey I keep getting notices that Su binary needs updating. Should I flash latest update via recovery?
I thought i saw mention of a fix for this but I can't seem to locate it again.
nujackk said:
@rbox Hey I keep getting notices that Su binary needs updating. Should I flash latest update via recovery?
I thought i saw mention of a fix for this but I can't seem to locate it again.
Click to expand...
Click to collapse
Just dismiss the notification.
rbox said:
Just dismiss the notification.
Click to expand...
Click to collapse
I've been doing that, just wondering if i can/should update ? Will It cause problems if i flash latest version?
got the same idea: just flash super su 2.79 sr3 should work?
That's what I'm thinking, just wanting rbox to confirm it shouldn't hose anything. I know some roms on phones don't work with latest versions. And since he is using such an old version, I'm think that might be the case here
Hmm i think i will try it next time. Create a backup and flash supersu.
Spillunke said:
Hmm i think i will try it next time. Create a backup and flash supersu.
Click to expand...
Click to collapse
flashing/updating SuperSU is not working and you will lose root
Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.
Y314K said:
Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.
Click to expand...
Click to collapse
Good luck! I always ended up with non-root after trying to replace/update SuperSU on my FireTVs
rainman74 said:
Good luck! I always ended up with non-root after trying to replace/update SuperSU on my FireTVs
Click to expand...
Click to collapse
What FW where you on & what method did u try using ?
- manual clean up of apk installation first (system/apps & /data/app, but left /system/xbin/su)
- adb install eu.chainfire.supersu.vX.xx.apk (1.94, 1.97, 2.00, 2.4x,...)
- TWRP flash of UPDATE-SuperSU-vX.xx.zip (1.94, 1.97, 2.00, 2.4x,...)
- ...
rainman74 said:
- manual clean up of apk installation first (system/apps & /data/app, but left /system/xbin/su)
- adb install eu.chainfire.supersu.vX.xx.apk (1.94, 1.97, 2.00, 2.4x,...)
- TWRP flash of UPDATE-SuperSU-vX.xx.zip (1.94, 1.97, 2.00, 2.4x,...)
- ...
Click to expand...
Click to collapse
Although it is much more of a pain to do fresh installs. I think when dealing with root it should be more stable to mess with it that way.
One can also do the build.prop mod to stop updates if one wants to test older FW versions.
Y314K said:
Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.
Click to expand...
Click to collapse
First thanks for the link to the xposed fix:good: And now that you mention it I don't know why i didn't think of that sooner, should be relatively easy to just replace the files in the zip with 7zip DUH. Only problem is I have everything all setup perfect.
Anyone have any luck getting Magisk 11.1 working on Nougat? Have done a ton of searching and a bunch of experimenting and nothing seems to work. I've always used traditional root, so if there's some obvious trick to getting it working, sorry in advance!
xxBrun0xx said:
Anyone have any luck getting Magisk 11.1 working on Nougat? Have done a ton of searching and a bunch of experimenting and nothing seems to work. I've always used traditional root, so if there's some obvious trick to getting it working, sorry in advance!
Click to expand...
Click to collapse
First flash the kernel with f2fs fixes v2 by tomparr than magisk 11.1 via twrp.
But safety net is not working didn't try it with magisk su instead of supersu.
prins29 said:
First flash the kernel with f2fs fixes v2 by tomparr than magisk 11.1 via twrp.
But safety net is not working didn't try it with magisk su instead of supersu.
Click to expand...
Click to collapse
Not OP, but last I checked that resulted in a kernel not found error at boot and that was like two days ago with the same exact versions you've mentioned. Has anything changed since then or I'm missing something?
lpchaim said:
Not OP, but last I checked that resulted in a kernel not found error at boot and that was like two days ago with the same exact versions you've mentioned. Has anything changed since then or I'm missing something?
Click to expand...
Click to collapse
He updated the file with changes .. and there is new update of TWRP by Alberto which is released today .With f2fs fixes. so u can check it out too.
prins29 said:
He updated the file with changes .. and there is new update of TWRP by Alberto which is released today .With f2fs fixes. so u can check it out too.
Click to expand...
Click to collapse
I've just tried again with the new TWRP and redownloaded files on my phone to be doubly sure, result is the same error others are reporting. Mind detailing how you managed to get Magisk running exactly? I've been looking around for a few days and never found consistent reports of it working on Nougat specifically, so it'd come in pretty handy.
Bump. Anybody succeed yet?
Try the Magisk 12 Snapshot. For me it works.
-=MoRpH=- said:
Try the Magisk 12 Snapshot. For me it works.
Click to expand...
Click to collapse
Can you write a guide please?
Here is how i got it working:
1. Make sure u have a clean unrooted Nougat Installation
2. Flash the TWRP from Alberto and make a full Backup
3. Flash magisk 12 (From here )
4. Reboot and Install the Magisch Manager 5.0
5. If no root there boot into recovery and flash the f2s Kernel
6. Flash magisk again and reboot...
7. Magisch should work now.
If not idk what if done right. My Setup is working fine.
-=MoRpH=- said:
Here is how i got it working:
1. Make sure u have a clean unrooted Nougat Installation
2. Flash the TWRP from Alberto and make a full Backup
3. Flash magisk 12 (From here )
4. Reboot and Install the Magisch Manager 5.0
5. If no root there boot into recovery and flash the f2s Kernel
6. Flash magisk again and reboot...
7. Magisch should work now.
If not idk what if done right. My Setup is working fine.
Click to expand...
Click to collapse
V12 definitely doesn't have an error when flashing like v11.1 did, but still doesn't pass safety check even after clean flashing flashallthetime's retbr build. Anyone get this to work with any other roms? One thing I noticed that was odd after clean flashing was viper and Dolby were installed but Dolby crashed and viper said drivers weren't installed. Weird.
Edit: Reflashed several different roms without zip. Tried using unSU zip + epsilon. No way to safetynet to pass, I give up. No androidpay/pokemongo is a small price to pay for working notification sounds, adblock, and greenify.
Hello not working for me ROM stock Nougat Épsilon
Regards
Enviado desde mi XT1635-02 mediante Tapatalk
iron maiden said:
Hello not working for me ROM stock Nougat Épsilon
Regards
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
I'm pretty sure Epsilon is pre-rooted, as it says in his OP.
xxBrun0xx said:
I'm pretty sure Epsilon is pre-rooted, as it says in his OP.
Click to expand...
Click to collapse
yep, but i delete de supersu zip from the rom
So i did it again, and it works
1. Flash the f2fs Kernel
2. Flash SuperSU R3
3. Flash Magisk v12
4. Clear Cache
5. Reboot
-=MoRpH=- said:
So i did it again, and it works
1. Flash the f2fs Kernel
2. Flash SuperSU R3
3. Flash Magisk v12
4. Clear Cache
5. Reboot
Click to expand...
Click to collapse
How do you pass safetynet with SuperSU? Magisk v11.1 and up has SuperSU built in, why flash it?
Not trying to give you a hard time, just trying to understand. Really appreciate the help!
Dont aks xD
Without that it won't work. Magisch patch the SuperSU away and replace it with MagiskSU and pass SaftyNet fine.
-=MoRpH=- said:
Dont aks xD
Without that it won't work. Magisch patch the SuperSU away and replace it with MagiskSU and pass SaftyNet fine.
Click to expand...
Click to collapse
Did you take a nougat OTA? I didn't, so I wonder if my problem is that I'm still on the marshmallow bootloader/modem?
Yes im on the Stock Nougat. But the bootloader or modem shouldn't make a difference.
But there could be a problem with the Custom roms.
-=MoRpH=- said:
Yes im on the Stock Nougat. But the bootloader or modem shouldn't make a difference.
But there could be a problem with the Custom roms.
Click to expand...
Click to collapse
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.
xxBrun0xx said:
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.[/QUOTE
I'll pm you with the right one
---------- Post added at 10:00 PM ---------- Previous post was at 09:56 PM ----------
xxBrun0xx said:
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.
Click to expand...
Click to collapse
Here https://www.androidfilehost.com/?fid=529152257862701536
Click to expand...
Click to collapse
Hi at all,
I own this device for two months now and I have read a lot about rooting and flashing. It seems to be quite difficult compared to my former Samsung and Xiaomi devices...
To avoid any kind of bricking my phone I wanted to ask if there's a way to root it. I (still) have a locked bootloader and I installed the latest update to 7.1.1 with 1st July security patch.
Is there any safe way to root and install TWRP (and afterwards some ROMs of course)?
Thank you. :fingers-crossed:
I have root on my moto z play with stock 7.1.1. if you don't downgrade you don't get bricked
To unlock and install twrp :
https://forum.xda-developers.com/moto-z-play/how-to/guide-root-xposed-flashing-stock-rom-t3529637
And to root use this:
https://forum.xda-developers.com/moto-z-play/how-to/how-to-safetynet-7-1-1-update-stock-rom-t3669086
To root is better with magisk ( second link)because don't break SafetyNet and the link is a tutorial made by me so if have any questions you can ask in the thread.
jst98 said:
I have root on my moto z play with stock 7.1.1. if you don't downgrade you don't get bricked
To unlock and install twrp :
https://forum.xda-developers.com/moto-z-play/how-to/guide-root-xposed-flashing-stock-rom-t3529637
And to root use this:
https://forum.xda-developers.com/moto-z-play/how-to/how-to-safetynet-7-1-1-update-stock-rom-t3669086
To root is better with magisk ( second link)because don't break SafetyNet and the link is a tutorial made by me so if have any questions you can ask in the thread.
Click to expand...
Click to collapse
Thank you so much! This is exactly what I needed and what I wasn't able to find :angel:
I will try this in the next few days and tell how far I will have come
f_ries said:
Thank you so much! This is exactly what I needed and what I wasn't able to find :angel:
I will try this in the next few days and tell how far I will have come
Click to expand...
Click to collapse
Sorry, but how was it? I'm in the same situation and I want to know. Any recommendation? Do you have any issue?
Thanks!
Martin-cai said:
Sorry, but how was it? I'm in the same situation and I want to know. Any recommendation? Do you have any issue?
Thanks!
Click to expand...
Click to collapse
If you are in 7.1.1, unlock your bootloader, download TWRP of @Alberto97 version 3.1.1-0(https://dc4.androidfilehost.com/dl/...673368273298955814/twrp-3.1.1-0-addison.img), flash it, download this kernel( https://drive.google.com/file/d/1i8PfTQ1e-WQkZ5-zD52HzWO3LZ5luaq_/view?usp=drivesdk) and the attached Magisk.zip.
Now, after you flashed the TWRP through Fastaboot, enter into recovery mode, select INSTALL, select the kernel and swipe to flash it. Then go back, select the Magisk.zip file to flash and swipe to flash it. After you do it, just reboot you device and check if the Magisk Manager app is installed, if it is, then open it, click on "check safety net", tap OK and wait until it tests the root hiding, if it says everything is okay, then everything is okay.
Congratulations, you are rooted now with Magisk and the Hiding Feature, you can play Pokemon go as well and the same for Snapchat and that stuffs that blocks rooted users from using their apps.
xdaVTU said:
Now, after you flashed the TWRP through Fastaboot, enter into recovery mode, select INSTALL, select the kernel and swipe to flash it. Then go back, select the Magisk.zip file to flash and swipe to flash it. After you do it, just reboot you device and check if the Magisk Manager app is installed, if it is, then open it, click on "check safety net", tap OK and wait until it tests the root hiding, if it says everything is okay, then everything is okay.
Congratulations, you are rooted now with Magisk and the Hiding Feature, you can play Pokemon go as well and the same for Snapchat and that stuffs that blocks rooted users from using their apps.
Click to expand...
Click to collapse
Thanks for your response!
I've read that flashing a kernel when you're in 7.1.1 might cause problems. Did you try this steps being in 7.1.1 or they're just general steps?
In case you were in 7.1.1, did you install xposed after those steps?
Sorry if I ask many questions, but I want to be sure that I'll not brick my phone
Martin-cai said:
Thanks for your response!
I've read that flashing a kernel when you're in 7.1.1 might cause problems. Did you try this steps being in 7.1.1 or they're just general steps?
In case you were in 7.1.1, did you install xposed after those steps?
Sorry if I ask many questions, but I want to be sure that I'll not brick my phone
Click to expand...
Click to collapse
no problem dude, i understand your concern, i'm just like this. Actually I was asking for help until last night and got all the answers.
flashing a kernel won't cause any problem since you do not flash any kernel but for your android version. The link i shared with you is a @logotoy73 kernel, he updated it last night and i used it. It's working properly and with no issues.
Today i've tried to install xposed, but due to the forced encryption in 7.1.1 it wasn't possible, even trying with the systemless xposed(magisk feature), maybe later i'll try again then i give you a feedback.
In magisk there are some xposed modules to be able to use it in nougat, but it caused me a bootloop.
If you follow exactly what i've said, you will be rooted in 7.1.1 in a few minutes!
Any problem you have, pm me so i could help you haha
good lucky
xdaVTU said:
no problem dude, i understand your concern, i'm just like this. Actually I was asking for help until last night and got all the answers.
flashing a kernel won't cause any problem since you do not flash any kernel but for your android version. The link i shared with you is a @logotoy73 kernel, he updated it last night and i used it. It's working properly and with no issues.
Today i've tried to install xposed, but due to the forced encryption in 7.1.1 it wasn't possible, even trying with the systemless xposed(magisk feature), maybe later i'll try again then i give you a feedback.
In magisk there are some xposed modules to be able to use it in nougat, but it caused me a bootloop.
If you follow exactly what i've said, you will be rooted in 7.1.1 in a few minutes!
Any problem you have, pm me so i could help you haha
good lucky
Click to expand...
Click to collapse
I just tried it and it worked perfectly. Thank you so much! You should make a post with those steps, I think it might help someone else.
Please, tell me if you manage to install xposed properly
Martin-cai said:
I just tried it and it worked perfectly. Thank you so much! You should make a post with those steps, I think it might help someone else.
Please, tell me if you manage to install xposed properly
Click to expand...
Click to collapse
I think creating a new post won't be necessary because kernel is already in @tomparr post, but in the last page of it, the twrp you cam download from Alberto's post, and magisk from the official thread(it's actually one of the most famous threads for now hahaha), but maybe if someone else have any issue with 7.1.1 i can create the post!
Edit. If i plan to try xposed again I tell you!
I have systemless xposed running on 7.1.1 with my kernel. After installing module xposed via twrp if a long start, helps reboot.
logotoy73 said:
I have systemless xposed running on 7.1.1 with my kernel. After installing module xposed via twrp if a long start, helps reboot.
Click to expand...
Click to collapse
Could you help with a little step by step?
Which xposed module? Magisk?
What did u mean with long start? Helps reboot?
Bug camera help me
I have root z play 7.1.1 with supersu, but problem bug camera ...using kernel post ...anything solution? I'm sorry my English...
xdaVTU said:
Could you help with a little step by step?
Which xposed module? Magisk?
What did u mean with long start? Helps reboot?
Click to expand...
Click to collapse
Only Magisk module. Normal XPosed would modify /system which would brick your device. And I don't know if that could be fixed
---------- Post added at 23:24 ---------- Previous post was at 23:18 ----------
Gean Teixeira said:
I have root z play 7.1.1 with supersu, but problem bug camera ...using kernel post ...anything solution? I'm sorry my English...
Click to expand...
Click to collapse
On the first site there is a tutorial linked, just follow it. Basically get rid of supersu first. Then the tutorial probably says that you have to install a custom kernel in order to just Magisk modules because the stock one is faulty. If you ask me that's shooting with guns on pidgins. The easiest way is to get the Magisk module F2FS loopback bug workaround. Google for it. When you have it and latest Magisk zip, go to TWRP, flash Magisk and the module, then reboot. Works perfectly, though you shouldn't ever wipe or format /cache because that's where Magisk is installed now, you'd loose it.
Artim_96 said:
Only Magisk module. Normal XPosed would modify /system which would brick your device. And I don't know if that could be fixed
---------- Post added at 23:24 ---------- Previous post was at 23:18 ----------
On the first site there is a tutorial linked, just follow it. Basically get rid of supersu first. Then the tutorial probably says that you have to install a custom kernel in order to just Magisk modules because the stock one is faulty. If you ask me that's shooting with guns on pidgins. The easiest way is to get the Magisk module F2FS loopback bug workaround. Google for it. When you have it and latest Magisk zip, go to TWRP, flash Magisk and the module, then reboot. Works perfectly, though you shouldn't ever wipe or format /cache because that's where Magisk is installed now, you'd loose it.
Click to expand...
Click to collapse
Thanks attention ...no work...i'll installed ROM 7.1.1 pre rooted in other post.
Gean Teixeira said:
Thanks attention ...no work...i'll installed ROM 7.1.1 pre rooted in other post.
Click to expand...
Click to collapse
Well then go back to stock first
Artim_96 said:
Well then go back to stock first
Click to expand...
Click to collapse
Stock Addison rooted magisk e december patch ZIP ...flash a few moments
I'M using stock...
Gean Teixeira said:
Stock Addison rooted magisk e december patch ZIP ...flash a few moments
I'M using stock...
Click to expand...
Click to collapse
Well, in the last post you said you are running a pre-rooted version. So what are you actually running and what are you trying to do and what doesn't work?
Artim_96 said:
Well, in the last post you said you are running a pre-rooted version. So what are you actually running and what are you trying to do and what doesn't work?
Click to expand...
Click to collapse
I'm enganed...ZIP is rooted with magisk ,flashed , It,s ok...no insue
Gean Teixeira said:
Stock Addison rooted magisk e december patch ZIP ...flash a few moments
I'M using stock...
Click to expand...
Click to collapse
Is that a new ROM or the Stock Plus?
Enviado desde mi XT1635-02 mediante Tapatalk
sergiomc22 said:
Is that a new ROM or the Stock Plus?
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
Stock post shamu17...dez patch, root magisk