Hi,
Long story short. I had TWRP 2.5.0.2 with my SGH-I377 (Galaxy S4 AT&T). I used it to flash this GE ROM by Maddog (http://forum.xda-developers.com/showthread.php?t=2340783)
After flashing, the ROM works just fine without issue. The Model Number in the about phone section however showed to be GT-I9505G, but I didn't mind too much since it works flawlessly in everyway. When I tried to update TWRP to 2.6.3.0, GooManager downloaded the wrong img due to this (it was my fault for not looking at the version before clicking yes). But now after reboot, i can't get into TWRP recovery anymore, it keeps saying "System software not authorized by ATT has been found on your phone". I was able to bypass by going to download mode and cancel to boot back into my old GE ROM. But now I can't seem to find away to get the correct TWRP version back on the phone.
I can download the correct img from this site, put it on my internal/ext SD, but I can't find a way to install it from within GooManager or from a File Manager.
http://techerrata.com/browse/twrp2/jflteatt
I need some assistance with instructions on how to install TWRP manually from an img file. Or from a tar file using ODIN if anyone has the link to necessary files and instructions on how to do it. At this point, it doesn't even have to be 2.6.3.0, I'll be just happy to get 2.5.2.0 back.
thinking21 said:
Hi,
Long story short. I had TWRP 2.5.0.2 with my SGH-I377 (Galaxy S4 AT&T). I used it to flash this GE ROM by Maddog (http://forum.xda-developers.com/showthread.php?t=2340783)
After flashing, the ROM works just fine without issue. The Model Number in the about phone section however showed to be GT-I9505G, but I didn't mind too much since it works flawlessly in everyway. When I tried to update TWRP to 2.6.3.0, GooManager downloaded the wrong img due to this (it was my fault for not looking at the version before clicking yes). But now after reboot, i can't get into TWRP recovery anymore, it keeps saying "System software not authorized by ATT has been found on your phone". I was able to bypass by going to download mode and cancel to boot back into my old GE ROM. But now I can't seem to find away to get the correct TWRP version back on the phone.
I can download the correct img from this site, put it on my internal/ext SD, but I can't find a way to install it from within GooManager or from a File Manager.
http://techerrata.com/browse/twrp2/jflteatt
I need some assistance with instructions on how to install TWRP manually from an img file. Or from a tar file using ODIN if anyone has the link to necessary files and instructions on how to do it. At this point, it doesn't even have to be 2.6.3.0, I'll be just happy to get 2.5.2.0 back.
Click to expand...
Click to collapse
You won't be able to install it with Goo Manager. Head over the the TWRP website and find your phone that way, and grab the flashing zip file and just flash it in recovery. I had the same issue a few weeks ago.
After some more digging, I was able to find a solution.
For anyone who runs into this problem...I was able to use Quick Flasher from this thread http://forum.xda-developers.com/showthread.php?t=1694617 , then choose the flash a new recovery using the correct TWRP img
Everything is good now, I am able to get into TWRP recovery 2.6.3.0
thinking21 said:
Hi,
Long story short. I had TWRP 2.5.0.2 with my SGH-I377 (Galaxy S4 AT&T). I used it to flash this GE ROM by Maddog (http://forum.xda-developers.com/showthread.php?t=2340783)
After flashing, the ROM works just fine without issue. The Model Number in the about phone section however showed to be GT-I9505G, but I didn't mind too much since it works flawlessly in everyway. When I tried to update TWRP to 2.6.3.0, GooManager downloaded the wrong img due to this (it was my fault for not looking at the version before clicking yes). But now after reboot, i can't get into TWRP recovery anymore, it keeps saying "System software not authorized by ATT has been found on your phone". I was able to bypass by going to download mode and cancel to boot back into my old GE ROM. But now I can't seem to find away to get the correct TWRP version back on the phone.
I can download the correct img from this site, put it on my internal/ext SD, but I can't find a way to install it from within GooManager or from a File Manager.
http://techerrata.com/browse/twrp2/jflteatt
I need some assistance with instructions on how to install TWRP manually from an img file. Or from a tar file using ODIN if anyone has the link to necessary files and instructions on how to do it. At this point, it doesn't even have to be 2.6.3.0, I'll be just happy to get 2.5.2.0 back.
Click to expand...
Click to collapse
You can get it right here
http://www.teamw.in/project/twrp2/182
That's straight from the horses mouth there. I didn't read much into it, but it looks like they have a odin flashable version. Also make sure that the newest version of TWRP doesn't conflict with the ROM your using. I have read quite a few where the latest version causes issues.
Can someone please post here stock recovery.img for OPT im now on TWRP but i want to install H2OS OTA normally.
Thank you so much
You may have chosen to keep the twrp recovery on your device from beeing overwritten by the stock recovery. This is done in twrp by renameing the "/bin/recovery.sh" (afaik).
Before installation OTA update checks for all checksums of files it will patch. So you will not only need the stock recover but at least to replace the recovery.sh with the original one.
Much easier way is to flash 2.0.2 full (not the OTA!), flash 2.1 OTA, flash SU and reboot in one session from twrp . I have done this and it worked without a problem.
Just make sure your battery is fully charged before
I'm getting an updated binary error. Started getting it in TWRP after flashing a custom kernel. Could you post your stock recovery? Or the stock kernel? (preferably the latter I suppose)
I've tried digging into the full 2.0.1 and 2.1 ROMs to find them, but I can't track them down...
Yes,i need the stock recovery
Well I need stock recovery because of hydrogen OS hope someone have it..
All you need is recovery paparapapa ahahahah
I managed somehow to have back stock recovery
When i flashed TWRP and then Gapps for Hydrogen OS it asked me to stop stock recovery to flash or something so i press dont stop, and voila im back on stock recovery
OnePlus 2 stock recovery -> http://forum.xda-developers.com/oneplus-2/general/oneplus-2-stock-recovery-t3217848
Phone: Samsung Galaxy Core Prime
MetroPCS
Model: SM-G360T1
ROM and Kernal: Stock
Issue: Touchscreen doesn't work in TWRP.
Links:
Where I got TWRP: https://dl.twrp.me/coreprimelte/
The guide I followed: http://www.android.gs/install-twrp-recovery-v3-0-0-on-samsung-galaxy-core-prime/
I got this phone from a friend. I tried to install TWRP via ODIN, but I've had some trouble. Initially, when I installed TWRP it didn't appear after I rebooted the phone. After doing some research, I found that this is normal for stock ROM's, and that they tend to replace any custom recovery with the stock one. I learned that in order to access TWRP, I need to remove the batter before rebooting, and then reboot directly into TWRP without letting the OS see the light of day. But when I get to TWRP, the touchscreen breaks. I can't interact with anything. I can still boot into the operating system just fine, but doing so removes the recovery, and I can't interact with TWRP outside of locking it by using the power button. I think this issue could be solved by installing a custom ROM, but I don't know if that's even possible without TWRP. This seems to be a loop of nothing, never going anywhere.
All I need is for the touchscreen to work in TWRP, I can handle the rest from there. Thank you for any help, and Happy Holidays!
Edit: After further research, I've discovered that the problem could lay in the recovery I'm using. I'm trying to install the latest TWRP version found in the link above, but I've tried almost all of them. Is there any information on any specific version of TWRP I should use?
OK, so I totally ****ed up somewhere while trying to wipe and flash stock while I could only see half my screen. I now have a fully working screen but no system.
Current situation is if trying to boot phone normally I get stuck on ZTE logo.
If I press volume keys during boot I get to here; https://puu.sh/z7YQa/8de2adc04e.jpg
Selecting recovery takes me to TWRP which immediately asks for a password (that I never set up).
If I attempt to flash RR (which was previously installed) I get error 7. (Lineage OS has the same response) https://puu.sh/z81cA/6371d882cc.jpg
I can successfully flash the latest TWRP (twrp-3.2.1-0-ailsa_ii.img).
I've also tried flashing A2017_N_Modem.zip and ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip which appear to complete successfully.
TWRP ADB Sideload seems to work and my PC can see the phone (adb devices but I've not tried anything with that yet for fear of ****ing up further.
Code:
C:\Users\Fish\Downloads\ADB>adb devices
List of devices attached
e33edd51 sideload
MrGodMan said:
OK, so I totally ****ed up somewhere while trying to wipe and flash stock while I could only see half my screen. I now have a fully working screen but no system.
Current situation is if trying to boot phone normally I get stuck on ZTE logo.
If I press volume keys during boot I get to here; https://puu.sh/z7YQa/8de2adc04e.jpg
Selecting recovery takes me to TWRP which immediately asks for a password (that I never set up).
If I attempt to flash RR (which was previously installed) I get error 7. (Lineage OS has the same response) https://puu.sh/z81cA/6371d882cc.jpg
I can successfully flash the latest TWRP (twrp-3.2.1-0-ailsa_ii.img).
I've also tried flashing A2017_N_Modem.zip and ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip which appear to complete successfully.
TWRP ADB Sideload seems to work and my PC can see the phone (adb devices but I've not tried anything with that yet for fear of ****ing up further.
Click to expand...
Click to collapse
Look, you have an A2017G, right? Error 7 is caused by not flashing the universal bootloader. The password is because you forgot to flash magisk or supersu on the last rom's first boot.
Download 3 things: raystef66's TWRP flashable B09 bootstack and stocksystem zips (from the download center or the dedicated thread, but make sure that it's the TWRP flashable ones) and Magisk 15.2. Install the BOOTSTACK, then the ROM, then Magisk. After that go to Wipe, and FORMAT DATA (not wipe!). You'll lose your internal storage.
Choose an username... said:
Look, you have an A2017G, right? Error 7 is caused by not flashing the universal bootloader. The password is because you forgot to flash magisk or supersu on the last rom's first boot.
Download 3 things: raystef66's TWRP flashable B09 bootstack and stocksystem zips (from the download center or the dedicated thread, but make sure that it's the TWRP flashable ones) and Magisk 15.2. Install the BOOTSTACK, then the ROM, then Magisk. After that go to Wipe, and FORMAT DATA (not wipe!). You'll lose your internal storage.
Click to expand...
Click to collapse
Thank you so much. Got that all done nicely and have a working stock ROM.
How would I now get from here back to RR?
MrGodMan said:
Thank you so much. Got that all done nicely and have a working stock ROM.
How would I now get from here back to RR?
Click to expand...
Click to collapse
Reading instructions is a start :laugh:
For real now: Get the ROM, the B15 universal bootloader (from the Lineage thread), get the latest modem file from the download center (B09 now for example), Magisk 15.2, GApps zip (unless you'll go microG) and be sure that you are on the latest TWRP or update to it.
Flash the bootloader and modem file (you'll have to install the modem as image i think). After you flash the bootloader your phone model becomes 'axon7' instead of 'ailsa_ii'; most custom roms use this to know whether you flashed it or not; and the region will be A2017U which is normal (it is based off of B15 for the U, don't panic). After that, flash the ROM and Magisk and GApps.
Choose an username... said:
Reading instructions is a start :laugh:
For real now: Get the ROM, the B15 universal bootloader (from the Lineage thread), get the latest modem file from the download center (B09 now for example), Magisk 15.2, GApps zip (unless you'll go microG) and be sure that you are on the latest TWRP or update to it.
Flash the bootloader and modem file (you'll have to install the modem as image i think). After you flash the bootloader your phone model becomes 'axon7' instead of 'ailsa_ii'; most custom roms use this to know whether you flashed it or not; and the region will be A2017U which is normal (it is based off of B15 for the U, don't panic). After that, flash the ROM and Magisk and GApps.
Click to expand...
Click to collapse
Perfection.
Everything works!
Hi guys,
I got the ASUS Zenfone 3 Zoom and started playing with it. Unfortunately I managed to soft brick it and somehow I can't go back to stock. Here are all the things I did. I would be happy to get any ideas what to try next:
1. unlocked the bootloader - using asus's official unlock tool
2. flashed twrp recovery - twrp-3.2.1-0-Z01H-20180304.img, using:
adb reboot bootloader
fastboot flash recovery twrp.img
3. updated asus's firmware to the latest official one:
copying UL-Z01H-WW-71.60.139.30.zip onto internal memory
android detects the update and applying it using android
4. Enabling lock pattern at boot (from android settings). Correct pattern required even when booting into recovery
5. Installing supersu via twrp:
adb reboot recovery
installing supersu
wiping caches (the cache partition cannot be wiped)
6. SuperSu working (tested via android)
7. Reading about Magisk. Trying to install magisk via twrp. Magisk's installer complained that the system is not vanilla (due to SuperSu modifications). Have to uninstall SuperSu to return to previous state.
8. Tried uninstalling SuperSu from the program itself (in android). The uninstaller got stuck. The phone become unresponsive and had to reboot.
9. Found a script packaged as an executable zip (to be installed via twrp) that will uninstall SuperSu and return system to pristine state (SuperSu makes a backup of the files it changes before installation) - UPDATE-unSU-signed.zip. Uninstallation worked.
10. Magisk installation still complained about the bootloader. Then things started to go wrong. I unpacked the latest firware UL-Z01H-WW-71.60.139.30.zip, took out boot.img and tried to flash just the bootloader
fastboot flash boot boot.img
11. Upon reboot the phone got stuck at the ASUS logo. Reboot into recovery and into fastboot still works (soft brick). Still shows unlock pattern at boot.
12. I tried flashing the original firmware using TWRP (install a zip). However the installation threw some errors. Unsuccessful.
13. I've tried flashing the system.img from the original firware using fastboot but still it's stuck at the ASUS logo at boot.
fastboot flash system system.img
Here I am stuck. I've read that TWRP cannot install properly the ASUS official firmware but if you flash the original recovery, it can probably flash it properly. Another thing that I think might explain why I cannot get out of the soft brick is that I've enabled the lock pattern at boot, which effectively encrypted some parts of the phone and I have a strong feeling this interferes with the boot process. I will look for a script/installable zip (via twrp) that can remove the lock.
I really need ideas/suggestions before I make something that will turn my phone into a hard brick. Thanks.
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Thanks
+)KEV1N(+ said:
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Click to expand...
Click to collapse
Thanks,
I tried to find a stock recovery images but unsuccessful. Can you tell me where to get it from?
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
-- [link] removed due to XDA regulations
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
mollonado said:
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
Click to expand...
Click to collapse
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
It came preloaded with Nougat? Interesting.
+)KEV1N(+ said:
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
It came preloaded with Nougat? Interesting.
Click to expand...
Click to collapse
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
mollonado said:
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
Click to expand...
Click to collapse
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
+)KEV1N(+ said:
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
Click to expand...
Click to collapse
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
mollonado said:
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
Click to expand...
Click to collapse
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
mollonado said:
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
Click to expand...
Click to collapse
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
+)KEV1N(+ said:
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
Click to expand...
Click to collapse
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
mollonado said:
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
Click to expand...
Click to collapse
First off, my apologies for this late reply (Been superbusy with school and internship assignments)
Secondly, and that is why I only use magisk. Because once you mess with the host file, depending on what module you install, it can range from tripping safetynet to bootlooping.
So quick question, is it still in this state right now since 9 days ago?
Greetings,
Kevin
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
I made a mistake and could not install recovery stock, I followed what you wrote in the beginning install MM recovery and so I did a hard reset and I was able to install the most current recovery stock and installed ROM Oreo, Thanks. Sorry, I'm on google translator.