Database Users

TWRP prevents Marshmallow?

I may be doing something stupid, but I've tried various options...
I had an original 5.1.1 build that I let OTA to 6.0. Everything was working fine. I wanted to root, so I installed TWRP... and then the machine wouldn't reboot; it stuck at the "powered by Android" screen and never went into the standard animation screens. I could reboot into TWRP recovery easily enough and using that I could see the filesystem data, but the OS wouldn't boot.
So I reflashed back to 5.1.1 (using http://www.andromods.com/download-files/xt1575-stock-firmware-moto-x-2015-pure-edition.html ), let that OTA to 6.0, installed TWRP... same result.
Third attempt; started at 5.1.1 then installed TWRP (which worked) and then did OTA to 6.0... but this went into a reboot loop.
(Of course during all this I've lost my configs, but I can rebuild that)
Has anyone been able to install TWRP onto an X-Pure 2015 that's running 6.0 ?

What TWRP version are you installing? Make sure it's 2.8.7.1 https://dl.twrp.me/clark/
Sent from my XT1575 using Tapatalk

Sorry, yes, I should have mentioned that; twrp-2.8.7.1-clark.img

Did you install TWRP as read only? I did this and now system recovery is overwriting TWRP and I have no idea how to get out of it.

I had the same problem a couple days ago and posted about it in the 'Android 6.0 Update rolling out! Pure Edition' thread:
"I keep running into a problem after doing the MM update when I flash TWRP (either 2.8.7.0 or 2.8.7.1) where it won't boot into system, just sits there where the animation part should start. Booted/rebooted fine a few times after finishing the MM update, even after flashing the unlocked bootloader logo fix, but as soon as I flash recovery it won't boot system. "
Tried it several times with both TWRP 2.8.7.0 and 2.8.7.1 with no success. Also tried sideloading the OTA per the manual steps in this thread but still couldn't boot to system. Only by already having TWRP installed on 5.1.1 am I able to flash a custom 6.0 ROM successfully. Haven't seen a really clear statement yet that someone has flashed TWRP on fully stock MM with no problem..

EVR_PR said:
Did you install TWRP as read only? I did this and now system recovery is overwriting TWRP and I have no idea how to get out of it.
Click to expand...
Click to collapse
First time I let /system be read-write and second time I let /system be RO. However this likely isn't related to recovery overwriting TWRP; it's documented that on first boot the OS may rewrite the recovery data meaning you'd need to install TWRP again.

Dahenjo said:
I had the same problem a couple days ago and posted about it in the 'Android 6.0 Update rolling out! Pure Edition' thread
...
Haven't seen a really clear statement yet that someone has flashed TWRP on fully stock MM with no problem..
Click to expand...
Click to collapse
Thanks; at least I know it's not me being stupid then (or if I am, then I'm not alone ).

sweh said:
First time I let /system be read-write and second time I let /system be RO. However this likely isn't related to recovery overwriting TWRP; it's documented that on first boot the OS may rewrite the recovery data meaning you'd need to install TWRP again.
Click to expand...
Click to collapse
I have flashed TWRP twice and even rebooted to recovery from recovery and system recovery still overwrites TWRP after booting to system.
Only way I can access TWRP is either flashing it or booting into from the fastboot folder using the fastboot boot command.
Doesn't matter what I do, the option for changing TWRP from read-write to read only doesn't show up anymore.

sweh said:
Thanks; at least I know it's not me being stupid then (or if I am, then I'm not alone ).
Click to expand...
Click to collapse
Well, at age 65 I do put my socks on backwards sometimes..... :silly:

Read on a fairly-detailed post that using adb to flash recovery and rebooting into it should actually work fine!
Could anyone confirm? Is it even possible?
P.S. I'm on XT1572 Indian stock 6.0, and very eager for twrp

I had the exact same problem. I used adb. Stuck on loading screen and then suddenly black. Not able to boot the phone. I'd like to make a nandroid and after that I'd like to use systemless root. If I'm correct, I'll still receive ota's while using systemless root.

Same for me. Returned to stock EU 5.1.1, got update, installed it. Later unlocked bootloader and installed latest TWRP. And now I am stuck on booting up image.
So stock Marshmallow cant be used with TWRP?

BooBzi said:
Same for me. Returned to stock EU 5.1.1, got update, installed it. Later unlocked bootloader and installed latest TWRP. And now I am stuck on booting up image.
So stock Marshmallow cant be used with TWRP?
Click to expand...
Click to collapse
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.

Dahenjo said:
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Click to expand...
Click to collapse
Thanks for reply, I did listen to you and post on TWRP thread.

Dahenjo said:
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Click to expand...
Click to collapse
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.

ccic2491 said:
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
Click to expand...
Click to collapse
Hello, is it possible to get step by step tutorial?
Later will try on Style with stock MM.
Thanks!

ccic2491 said:
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
Click to expand...
Click to collapse
Did you not use the Fastboot Install Method on the TWRP site? We are unable to reboot back into system after using this on stock MM, which always worked fine on stock LP. If you used a different method that worked could you please share what that was?

I am using twrp 2.8.7.1 on my Moto X Style XT1572 Asia retail without any trouble for past two weeks.
I normally flashed it using the fastboot and never ran into trouble.

gulshanstrider said:
I am using twrp 2.8.7.1 on my Moto X Style XT1572 Asia retail without any trouble for past two weeks.
I normally flashed it using the fastboot and never ran into trouble.
Click to expand...
Click to collapse
Just to confirm - when you flashed TWRP you were completely stock after installing the 6.0 OTA (not still on 5.1.1 before taking the OTA), correct?

Dahenjo said:
Just to confirm - when you flashed TWRP you were completely stock after installing the 6.0 OTA (not still on 5.1.1 before taking the OTA), correct?
Click to expand...
Click to collapse
Here is what I did:-
1) I was in Stock 5.1.1 (had unlocked bootloader)
2) I took the OTA.
3) Flashed the twrp 2.8.7.1 using fastboot
So yes I was completely stock 6.0 when I flashed the TWRP for MM

N910TUVS2EPG2 - Caution & Info

Be cautious with the latest N910TUVS2EPG2.
You might not be able to downgrade the bootloader once its updated.
If you look back at the history of builds for the N910T you will see the following:
N910TUV U2 EPE3 = 6.0.1
N910TUV U2 DOK2 = 5.1.1
N910TUV U1 COG2 = 5.0.2
Pay attention to the U1 & U2 numbers.
Notice that you can upgrade and downgrade between 6.0.1 and 5.1.1 but cannot downgrade to 5.0.1
Both 6.0.1 and 5.1.1 have U2 in their build. In the past (at least on some devices) once these numbers change is when you cannot downgrade to a different number.
So whats my point? Look at the latest build. N910TUV S2 EPG2.
"S2" This very well could mean you can not downgrade to 5.1.1 and or PE3 6.0.1.
It also could mean that there have been some other bootloader changes.
There have been some reports that some on the latest N910TUVS2EPG2 have had trouble flashing TWRP.
Disclaimer: This info is not to be taken as golden fact. I'm just providing it so people can look out and be aware this has been the case in the past.
Since a lot of this information has not been confirmed and will not be confirmed by Samsung we can only go by past situations.
This has been indeed the case on both the Note 4 and the Galaxy Tab S2
To everyone that has indeed updated to this new Firmware version (N910TUVS2EPG2) please post any experiences from it.
Any problems? Any confirmed known changes. Anything.
Thanks!

I updated, and I was able to install twrp, root, and xposed. However, I have heard reports that twrp doesn't work for some people.

I updated yesterday. Took a couple of tries, but I got it to install twrp & supersu. Currently rooted on epg2
Can anyone point me in the direction of installing xposed on 6.0.1?

N910T here. Updated to EPG2 and I was able flash twrp, supersu v2.76 and custom ROM. I haven't tried rolling back to 5.1.1 bootloader yet.
Sent from my SM-N910T3 using Tapatalk

ayeitschris said:
N910T here. Updated to EPG2 and I was able flash twrp, supersu v2.76 and custom ROM. I haven't tried rolling back to 5.1.1 bootloader yet.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Chocu1a said:
I updated yesterday. Took a couple of tries, but I got it to install twrp & supersu. Currently rooted on epg2
Can anyone point me in the direction of installing xposed on 6.0.1?
Click to expand...
Click to collapse
Any chance one of you could try rolling back to 5.1.1 or even PE3?
Regarding Xposed it should be the same one as PE3.
http://forum.xda-developers.com/note-4-tmobile/general/pe3-xposed-n910t-t3-marshmallow-t3406950
Also, How is PG2 running for you both? Anything worth mentioning?

DeeXii said:
Any chance one of you could try rolling back to 5.1.1 or even PE3?
Regarding Xposed it should be the same one as PE3.
http://forum.xda-developers.com/note-4-tmobile/general/pe3-xposed-n910t-t3-marshmallow-t3406950
Also, How is PG2 running for you both? Anything worth mentioning?
Click to expand...
Click to collapse
I upgraded to the new MM and everything its ok, twrp, (your root systemless) is ok and all is ok! let me rolling back to LP now, gime a 20 or 30 min...:good:

wilsonmd said:
I upgraded to the new MM and everything its ok, twrp, (your root systemless) is ok and all is ok! let me rolling back to LP now, gime a 20 or 30 min...:good:
Click to expand...
Click to collapse
Any update to this?

DeeXii said:
Any update to this?
Click to expand...
Click to collapse
Odined stock EPG2 tar, SuperSu systemmode, Xposed alt 86 wanam, TWRP 3.0.2-0, no issues. Great battery, runs smoother, no hiccups. :good:

DeeXii said:
Any update to this?
Click to expand...
Click to collapse
via Odin and i could not let me try flashing the LP bootloader and flash any room ......

How Downgrade your T-Mobile Note 4 (N910t) from MM (any version) to DOK2 Lollipop!
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
IM NOT RESPONSABLE IF A HEART ATTACK OCCUR OR YOUR PHONE BLOW UP WITH ALL THE ROOF :silly:
IF YOU HAVE YOUR PHONE IN MM PG2 STOCK rooted with super SU systemless and last TWRP instaled (like me) YOU CAN DOWNGRADE TO D0K2 LOLLIPOP :
******REMEMBER Disable Reactivation lock (see picture below) and activate USB debuggin, Before DO this procedure!!*******
1-Download the DOK2 BOOTLOADER HERE https://www.androidfilehost.com/?fid=24269982087008410 and the D0K2 modem here: https://www.androidfilehost.com/?fid=24269982087008409 ( i did use 3.0.9 Odin) >>>>>>>>>thanks to @xoxo_xdagirl91 for post the links!
2- Download The 5.1.1 rom here: http://forum.xda-developers.com/note-4-tmobile/development/rom-maximum-ovrdrive-v15-1-1-t3196653 its an awsome rom by @OvrDriVE and so Thanks for that!
3-Put the ovrDrive 5.1.1 rom into the external sd card together with the upgrade. (because need erase all in the internal memory, remember, make a back up of your data in the phone or in the internal memory if you want).
4-now GO to your TWRP and wipe cache-dalvik-system-data-INTERNALmemory x3 ..........DONT TOUCH YOUR EXTERNAL SD, REMEMBER THE OVRDRIVE 5.1.1 ROM IS THERE!
******REMEMBER WHEN YOU ERASE YOUR INTERNAL MEMORY JUST REBOOT AGAIN IN RECOVERY, each time you erase yor internal memory, when reboot in TWRP you see the warning and said that you need to click in "never show this screen during boot again" just click there and swipe to allow Modifications or the stock recovery will rewrite again. TURN OF YOUR PHONE!
5-GO TO DOWNLOAD MODE TO USE Odin and flash the 5.1.1 bootloader FIRST, WHEN FINISH, Flash the modem ..... REMEMBER: put the bootloader in the BL section FIRST AND FLASH & FOLLOWING THE modem in the CP section of odin
6- When finish the step 5, go to your recovery TWRP>install>go to ext sd>flash the ROM first, when finish, wipe dalvik, cache and reboot again in TWRP
7- Just flash the othe part of the rom........the upgrade zip file, when finish just reboot the system aaaaaaaand
WALAAAAAHHHHHH!!!!!!
I DID IT EXACTLY AS DIRECTED AND I HAVE A CLEAN OVRdrive
rooted rom in 5.1.1. Now you can flash via ODIN the original firmware on 5.1.1:good::good:

Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.

mykos said:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
Click to expand...
Click to collapse
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.

xdapowerapps said:
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
Click to expand...
Click to collapse
Thanks for the response! I gave it another shot this morning.
Used CF Auto Root, installed TWRP, no issues. I was having random restarts on non-stock roms, but none on this one even with rigorous testing.

xdapowerapps said:
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
Click to expand...
Click to collapse
They say that this compilation can not Downgrade "N910TUVS2EPG2" to 5.1.1 o another 6.0.1 compilation
IS TRUE..!!

mykos said:
Thanks for the response! I gave it another shot this morning.
Used CF Auto Root, installed TWRP, no issues. I was having random restarts on non-stock roms, but none on this one even with rigorous testing.
Click to expand...
Click to collapse
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
kiikez said:
They say that this compilation can not Downgrade "N910TUVS2EPG2" to 5.1.1 o another 6.0.1 compilation
IS TRUE..!!
Click to expand...
Click to collapse
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:

xdapowerapps said:
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
Click to expand...
Click to collapse
Conflicting reports on here. I haven't tried this myself yet but THIS post states a successful downgrade. YMMV.

mykos said:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
Click to expand...
Click to collapse
how did you flashed the super su systemless?

Cannot root or odin twrp after latest (pg2) update. Odin to pe2 and everything is back to normal.

xdapowerapps said:
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
Click to expand...
Click to collapse
Could you list the exact steps. I would like to try that ROM as well, considering we don't have any MM ports for our T-Mo Note 4. How is it working so far?
Thanks

krishelnino said:
Could you list the exact steps. I would like to try that ROM as well, considering we don't have any MM ports for our T-Mo Note 4. How is it working so far?
Thanks
Click to expand...
Click to collapse
Sure bud.
1) Download the M6 ROM from Dev-Host or from MediaFire.
Put this file in your external SD card.
2) Download the BeastMode kernel.
Put this file in your external SD card.
3) Download the Data Fix - MM_DataFixs7rebootmenu.zip.
Put this file in your external SD card.
4) Boot into recovery. Make a backup of your current ROM just in case. :fingers-crossed:
5) Go into Advanced Wipe (if you're using TWRP) and wipe dalvik, system, data, cache, internal storage (or whichever options are available in the recovery you are using).
6) Flash M6 Rom from Step 1. Do not restart.
7) Flash kernel from Step 2. Do not restart.
8) Flash data fix from Step 3.
9) Now wipe cache and dalvik cahe. Restart.
Once you restart, it will look like your phone crashed or is stuck in a bootloop, it's not. Let it sit there for about 10-15 minutes and it will boot into the setup screen. Good luck. :good:

Having problem rooting my Axon 7 A2017U

Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!

What version of TWRP did you flash first?

I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.

Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.

I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.

Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.

Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.

[How-To] Applying Monthly Security Patches if you're Rooted (Magisk)

So, since once a month I find myself having to click a bunch of links and read how to do a bunch of commands, I wanted to create a thread that (rather generically) explains how to manually flash the OTA monthly updates if you're rooted with Magisk. So, minimally, here's a thread for me to review every month... if it helps you all out, all the better!
Pre-requisites:
Download Latest OTA zip file from Google.
Obtain the STOCK boot.img (required) and dtbo.img (optional) of the System ROM you are currently running. This can be done if you already have the full System Image file downloaded, downloading it currently, or just obtaining the stock boot and dtbo image files elsewhere. (NOTE: This can be skipped if you successfully uninstall Magisk BEFORE you start the process and choose to restore the Stock images in the uninstall process.)
Download Latest Magisk Zip file
Download latest TWRP recovery image
If applicable, have latest USB drivers, adb/fastboot/ files etc.
Preparation:
1) Extract or open the Full Image file and locate the boot.img and dtbo.img files. You will want these on your PC in the platform-tools folder (I usually put the Month name at the beginning, ex. - Jan_boot.img). Again, you can skip if you successfully uninstall Magisk prior to all of this.
2) Copy your OTA zip file to the platform-tools folder, again naming it after the month helps (ex. - Feb_Pixel2XL_OTA.zip)
3) Put your TWRP recovery in platform-tools folder.
4) Place the latest Magisk zip on your Pixel's internal storage (what used to be the SDCard on phones so equipped).
Commands:
1) From PC, open command prompt and change directory to your platform-tools folder.
2) If your phone is on, "adb reboot bootloader" If powered off, press power and Vol Down button to get to Bootloader. Plug your phone into your PC.
3) [If Magisk is not uninstalled first] Command: fastboot flash boot {Name_of_boot.img File}
4) [If Magisk is not uninstalled first] Command: fastboot flash dtbo {Name_of_dtbo.img File}
5) On your phone, hit Vol Down until you see Recovery, then press power button.
6) Once in recovery mode, press power and Vol Up to bring up menu
7) Scroll to item: "Apply update from ADB" and press power
8) Command: adb sideload {Name_of_OTA.zip file}
9) After the OTA finishes flashing, exit recovery back into the Bootloader
10) Command: fastboot boot {twrp_filename.img}
11) Install Magisk Zip file (and any other Zip files you want installed... Kernels, etc.) within TWRP
Then after flashing your zip files, reboot to system and you should be all set.
I believe everything above is correct, but if I've made a glaring mistake, please let me know. I also realize there may be other methods to this madness, but this is what works for me.

With this method do you have to worry about removing your password from your phone before you try to go into twrp?

uofirob said:
With this method do you have to worry about removing your password from your phone before you try to go into twrp?
Click to expand...
Click to collapse
Yes. Mine is set to pin, which I had to put in and it let me finish.

Sweet. I'll give this method a try tonight!
WorldOfJohnboy said:
Yes. Mine is set to pin, which I had to put in and it let me finish.
Click to expand...
Click to collapse

Thank you for this. Just to be clear in step 2 under prerequisites you say more on this later. Then in step 1 for preparation you prefix your boot and dtbo with Jan xx.img. I get what your saying, but for the newer noobs they may get confused. Maybe reword to say, extract or open the factory image your currently using or the previous months image. Obviously you do this first so that you can sideload the ota. I don't mean any disrespect.

I believe you also need remove the -w from the end of the .bat file after you extract the OTA; otherwise, all of your data will be wiped.
But great job of getting all this info in one place!

So I did this, and now I'm bootlooping. I guess I'll re-flash the Jan factory image and wait a little longer... **UPDATE** I fixed the bootloop by re-trying the process again (after re-verifying the MD5 hash on the update.zip. I rebooted after installing the update,
but before the TWRP flash to install MAGISK. Maybe this allowed the "update"
to finish processing. I also had to remove the pin from my lock screen in order to allow me to get into twrp. After rebooting into the system and removing the pin, I adb reboot bootloader and then flashed twrp. Thanks for the guide!
---------- Post added at 07:58 AM ---------- Previous post was at 07:50 AM ----------
PuffDaddy_d said:
I believe you also need remove the -w from the end of the .bat file after you extract the OTA; otherwise, all of your data will be wiped.
But great job of getting all this info in one place!
Click to expand...
Click to collapse
You don't need to remove the -w from the .bat file since you aren't using it at all to do the update. That is only if you're flashing your factory image.

Fe Mike said:
Thank you for this. Just to be clear in step 2 under prerequisites you say more on this later. Then in step 1 for preparation you prefix your boot and dtbo with Jan xx.img. I get what your saying, but for the newer noobs they may get confused. Maybe reword to say, extract or open the factory image your currently using or the previous months image. Obviously you do this first so that you can sideload the ota. I don't mean any disrespect.
Click to expand...
Click to collapse
I changed some wording under prerequisite...

I agree with everything on this guide...
just teasing...
I'm actually glad you created this thread...I wanted to create one also and try and help out as much as I could, but I don't have the cahones and didn' t think I had experience enough to start a "guide" thread :silly:

I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!

CyberpodS2 said:
I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!
Click to expand...
Click to collapse
Well...I can't speak for the OP, but I wrote my extremely similar identical one because, for whatever reason, many users would choose OTAs over flashing full factory images. I/me & you understand the benefits of the factory images over the OTAs; especially understanding the process you must go through to install the OTAs as-of-current is almost the same as flashing the factory images anyways...
But if I were to give a possible explanation to their reasoning is that, like many of them, I come from a non-Google phone (S5 for me), and OTA's were simpler, takes less bandwidth (which still remains true today), they were significantly simpler to install vs. factory images, and with a lot of popular phones you only flash factory images to recover your phone; i.e. muniz_ri's OTA's for the S5 and FlashFire were loads simpler than flashing a whole factory image. But, again, understanding the difference for Pixel 2 and Oreo's OTA & factory images (or the small difference thereof), it's probably better to do a few extra steps and/or downloads to do the whole image than sideloading an OTA.
In the end, this is for people who insist for OTA updates most likely because that's how they are familiar (and therefore more comfortable) with; whether it being explained to them or not...
Cheers!:good:

Fair enough, thanks for the input!

CyberpodS2 said:
I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!
Click to expand...
Click to collapse
It may seem awful complicated, but to be honest, to me is less complicated than having to edit a script file (which if you forget to do, will lose all of your data). Also, though the steps I wrote out seem like a lot more if you were to write out a process using the full image, it actually works out to be almost the same number of steps.
Lastly, as someone else hinted at, the OTA file size is smaller. The only full image you need is what you are currently running (which in most cases I have on my phone in case the sh__ hits the fan with my phone), not the new full image. (To be even more precise, you only need the boot.img and dtbo.img from the full image file--there may be places to get just those two files out there.)
As I put in the last sentence, I realize there are other methods to this madness, this is basically what works for me. I wanted to get it in writing so I wouldn't forget this down the road, and if it helps anyone here, just icing on the cake. Clearly I'm no Dev and not forcing anyone to perform the updates this way!

WorldOfJohnboy said:
It may seem awful complicated, but to be honest, to me is less complicated than having to edit a script file (which if you forget to do, will lose all of your data). Also, though the steps I wrote out seem like a lot more if you were to write out a process using the full image, it actually works out to be almost the same number of steps.
Lastly, as someone else hinted at, the OTA file size is smaller. The only full image you need is what you are currently running (which in most cases I have on my phone in case the sh__ hits the fan with my phone), not the new full image. (To be even more precise, you only need the boot.img and dtbo.img from the full image file--there may be places to get just those two files out there.)
As I put in the last sentence, I realize there are other methods to this madness, this is basically what works for me. I wanted to get it in writing so I wouldn't forget this down the road, and if it helps anyone here, just icing on the cake. Clearly I'm no Dev and not forcing anyone to perform the updates this way!
Click to expand...
Click to collapse
Hey bud, wonder I I could pick your brain just a little. When doing monthly Google updates, are most of their proprietary files located in the boot, dtbo, and vendor images?? Your posts have intrigued me a little, and are very well written BTW. My reasoning is this. On my old 6p, about all we needed to do was flash the new vendor, and of course the bootloader and radio if there were any worthwhile improvements. Would the same possibly apply to the P2XL?? I'm just wondering because, now that we're starting to see custom roms, if this would be a viable option, and simplify the updating process. Thank again for your great write up ??

Badger50 said:
Hey bud, wonder I I could pick your brain just a little. When doing monthly Google updates, are most of their proprietary files located in the boot, dtbo, and vendor images?? Your posts have intrigued me a little, and are very well written BTW. My reasoning is this. On my old 6p, about all we needed to do was flash the new vendor, and of course the bootloader and radio if there were any worthwhile improvements. Would the same possibly apply to the P2XL?? I'm just wondering because, now that we're starting to see custom roms, if this would be a viable option, and simplify the updating process. Thank again for your great write up
Click to expand...
Click to collapse
I'll be perfectly honest with you, I haven't taken a dive to see what is in the OTA files and would imagine that it varies depending on the monthly updates.... that said, the only reason why I have stated to re-flash the stock boot.img is because if you are rooted with Magisk, it takes the stock boot.img and modifies it. In order to take an OTA sideload, you need to be on stock boot.img and stock recovery. dtbo is only in my process because there was one time when I tried to sideload and my dtbo wasn't stock (or corrupt). You may not need to flash the stock dtbo.img, but it doesn't hurt to do so.

WorldOfJohnboy said:
I'll be perfectly honest with you, I haven't taken a dive to see what is in the OTA files and would imagine that it varies depending on the monthly updates.... that said, the only reason why I have stated to re-flash the stock boot.img is because if you are rooted with Magisk, it takes the stock boot.img and modifies it. In order to take an OTA sideload, you need to be on stock boot.img and stock recovery. dtbo is only in my process because there was one time when I tried to sideload and my dtbo wasn't stock (or corrupt). You may not need to flash the stock dtbo.img, but it doesn't hurt to do so.
Click to expand...
Click to collapse
I'm really happy to see our device has graduated to this level of discussion, instead of the random guessing and 14 different "possible" routes to a solution. Lol
Custom roms abound, once TWRP gets squared away and someone master's the art of turning monthly updates into zip installs we'll pretty much be there!
Btw OP, great write up... Clear and precise!

I do not understand the purpose for downloading the full system image and then flashing only the OTA zip - what am I missing? There is a widely distributed method for performing monthly OTA updates by uninstalling Magisk, updating OTA normally, then flashing Magisk again - seems much simpler, any reason why it would not work?

Brenneke said:
I do not understand the purpose for downloading the full system image and then flashing only the OTA zip - what am I missing? There is a widely distributed method for performing monthly OTA updates by uninstalling Magisk, updating OTA normally, then flashing Magisk again - seems much simpler, any reason why it would not work?
Click to expand...
Click to collapse
Downloading the full system image is not required. You only need the Stock versions of boot.img (required) and dtbo.img (optional) of the ROM version your phone is currently running. I actually keep a full system image on my phone in case something goes awry.
I'm going to update the OP to more clearly state that you only need the stock boot.img file--how you obtain it is up to you. Uninstalling Magisk will do the same exact thing, however I tried to do that a couple of months ago and it created more issues for me than if I had just flashed the stock boot.img in the first place.

WorldOfJohnboy said:
Downloading the full system image is not required. You only need the Stock versions of boot.img (required) and dtbo.img (optional) of the ROM version your phone is currently running. I actually keep a full system image on my phone in case something goes awry.
I'm going to update the OP to more clearly state that you only need the stock boot.img file--how you obtain it is up to you. Uninstalling Magisk will do the same exact thing, however I tried to do that a couple of months ago and it created more issues for me than if I had just flashed the stock boot.img in the first place.
Click to expand...
Click to collapse
I have not tried the uninstall Magisk method but plan to do so at next update. What kind of issues did it create for you?
Thanks.

Brenneke said:
I have not tried the uninstall Magisk method but plan to do so at next update. What kind of issues did it create for you?
Thanks.
Click to expand...
Click to collapse
For some reason, I don't think it restored the correct (or not corrupted) boot.img version. Then, there were remnants of the Magisk APK and other files so I ended up having to do a full TiBu of my apps and flashed (with wipe) a full System image. It may have been something I did or just my bad luck, but I prefer not to chance it and instead manually flash the Stock image as my "guide" here states.

Help with soft brick

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.