Develop Bugs

Unable to mount partitions after flashing TWRP on Nexus 7 (2013, WiFi, flo)

I just bought this device a week and I haven't even rooted I wanted to install Cyanogenmode and follow through the instructions and flashed TWRP through fastboot commands from Windows7 using Minimal ADB and Fastboot [8-28-15].
I got the TWRP recovery but I am not sure what have I done wrong, when I am in the TWRP recovery, it does not show any partitions so I am unable to install any ROM on it.
I have also tried to use this thread: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562 when I flash the given recovery from fastboot commands from this thread, the recovery get stuck with bootloop. So then I restored it back to the original TWRP 2.8.7.0.
So at this point now I can only access bootloader and the recovery which does not show partitions.
At this point Is it possible for me to go back to the stock ROM somehow? Please advice. Otherwise I might be able to return it because I have only bought it few days ago.
SOLVED: To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/androi...s/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/dev...o_20150630.img
This allowed TWRP to work.
Thanks to Batfink33 and lynnux

You can follow this guide to flash the newest factory image: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/. You should just download the latest factory image from: https://developers.google.com/android/nexus/images?hl=en the one in the guide is outdated.

Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.

lynnux said:
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
Click to expand...
Click to collapse
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.

Batfink33 said:
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Click to expand...
Click to collapse
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).

lynnux said:
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
Click to expand...
Click to collapse
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!

Batfink33 said:
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Click to expand...
Click to collapse
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice

a4abbas said:
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
Click to expand...
Click to collapse
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.

Batfink33 said:
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Click to expand...
Click to collapse
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice

a4abbas said:
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
Click to expand...
Click to collapse
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.

theminikiller said:
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
Click to expand...
Click to collapse
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?

a4abbas said:
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
Click to expand...
Click to collapse
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.

theminikiller said:
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
Click to expand...
Click to collapse
You must be right, it make sense.

DM verity

In the Oneplus 3T forum it is reported that flashing the bootloader resets the dm verity. Can we get the bootloader for Oneplus 3 to try the fix?

wrong forum body...
there's a specific forums for questions & requests.

Hi,
I had also this problem on my OP3 (not T version).
Solved with this :
1- on Freedom OS 1.7 (any rom should work), rebooted to TWRP (Official)
2- wiped everything including internal storage. (if already on .28 TWRP wiping data to f2fs and wiping internal storage normally may save you some steps later on)
3- fastbooted the official recovery (v1 downloaded from OP site)
4- rebooted to official recovery and started install from ADB.
5- sideloaded beta 9
6- rebooted to beta 9 ( booted perfectly with no issues)
7- reboot back to official recovery (now it will be v2)
8- wipe cahce (and data if available)
9- reboot to fastboot and fast boot mod TWRP .28
10 - on TWRP the password issue might appear but it';; be fixed after this step
11- on TWRP wipe Data to f2fs (even if it was f2fs) and wipe internal storage (it may show it as 0 size)
12- reboot to system
13- reboot back to TWRP and now it can access internal storage , flash SuperSU (sr5)
finaly reboot to system.
Regards,
Ted

Stop with this thread there are already specific threads for dm.

I Made an Backup with flashfire (fastboot flashable). And then restored it. After that the warning was away.

i still not get it, what the big problem is with this warning?
Have it since it came out, and cant find any issue with it?! Or do i miss something?

MultiCulti said:
i still not get it, what the big problem is with this warning?
Have it since it came out, and cant find any issue with it?! Or do i miss something?
Click to expand...
Click to collapse
There's technically no problem other than the annoyance of seeing the warning and using an extra 5 secs

I asked this issue on OnePlus online chat. They said that flashing open beta 7 firmware can solve this issue. I've tryed this and dm-verity error has been gone.

qhsusb_bulk said:
I asked this issue on OnePlus online chat. They said that flashing open beta 7 firmware can solve this issue. I've tryed this and dm-verity error has been gone.
Click to expand...
Click to collapse
And then flashed back OOS 4.02?? It is still gone

panther124 said:
I Made an Backup with flashfire (fastboot flashable). And then restored it. After that the warning was away.
Click to expand...
Click to collapse
Worked like a charm! Thanks for the tip

fuarkgl3 said:
Worked like a charm! Thanks for the tip
Click to expand...
Click to collapse
can u tell me how to restore backup file from flashfire.

phanipk said:
can u tell me how to restore backup file from flashfire.
Click to expand...
Click to collapse
Transfer your backup to your computer and extract the zip, then put your phone in fastbooot mode and click flash-all.bat

there have been so many threads on how to remove DM V. just use the search function dude...

There is no need to flash or erase anything.
Just use these two fastboot commands and the dm-verity notification is gone:
fastboot oem disable_dm_verity (this command is not needed)
fastboot oem enable_dm_verity

snippem said:
And then flashed back OOS 4.02?? It is still gone
Click to expand...
Click to collapse
Sorry for late reply. Yes now i am using OOS 4.0.2 with open beta 7 firmware. Firstly flashed full OOS zip with twrp, secondly i flashed OB7 firmware.

Thanks Sniperle
sniperle said:
There is no need to flash or erase anything.
Just use these two fastboot commands and the dm-verity notification is gone:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Click to expand...
Click to collapse
This was just the right trick
No more DM verity mumbo-jumbo.
THANKS!!!

So those two commands can also be used instead of the dm-verify.zip for those that want to make changes to their system partition (by mounting it in twrp) WITHOUT root?

Rastko said:
This was just the right trick
No more DM verity mumbo-jumbo.
THANKS!!!
Click to expand...
Click to collapse
sniperle said:
There is no need to flash or erase anything.
Just use these two fastboot commands and the dm-verity notification is gone:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Click to expand...
Click to collapse
Can i use this with TWRP, Custom ROM and Root activated? Or is this only possible with original bootloader and recovery?

bensen from hell said:
Can i use this with TWRP, Custom ROM and Root activated? Or is this only possible with original bootloader and recovery?
Click to expand...
Click to collapse
I'm using TWRP, LineageOS, phh root and it works
---------- Post added at 11:13 ---------- Previous post was at 10:59 ----------
sjaak1234 said:
So those two commands can also be used instead of the dm-verify.zip for those that want to make changes to their system partition (by mounting it in twrp) WITHOUT root?
Click to expand...
Click to collapse
The ZIP is for the previous use to not trigger dm-verity at all.
The fastboot commands should disable the message if you have already triggered dm-verity.

Ahhh nice, thanks. I thought that is only work with original bootloader and recovery because the OEM in the command. I'll try it at Weekend.

TWRP 3.2.3-1 for Pixel 2 XL

Note: Do not use if you have multiple users (including a guest user)
Lots more information here: https://plus.google.com/u/1/+DeesTroy/posts/i33ygUi7tiu
I strongly recommend that kernel developers start building the touch drivers into the kernel instead of depending on modules to ensure a fully functional TWRP since recovery is now part of the boot partition.
Be careful about what you install on your device as far as kernels and ROMs go. I think there is a high potential for losing the ability to decrypt because of the OS and patch level tags that are included in the boot image and the anti-rollback features that Google has implemented.
MTP does not work in TWRP on the Pixel 2 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, you will need to reflash root.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
Pixel 2:
https://twrp.me/google/googlepixel2.html
https://dl.twrp.me/walleye/
Pixel 2 XL:
https://twrp.me/google/googlepixel2xl.html
https://dl.twrp.me/taimen/

Reserved!

Awesome to see the progress here, thank you for working on it and dealing with all the impatient requests. Will definitely be keeping an eye on this thread ?

Hurray for progress!

fastboot boot /path/to/twrp.img reboots into TWRP, but it never goes past the teamwin splash screen. I am able to reboot the phone normally after that, so no biggie.
I don't have time now to mess with figuring out how to get you logs, but I'll do that later this evening. Just wanted to give you a quick "what happened when I tried it."
And THANK YOU for working on this for us so quickly!
Edit: The logs are posted here:
https://forum.xda-developers.com/pixel-2-xl/development/twrp-alpha-pixel-2-xl-t3698148/post74363478

This makes me smile. Thanks Troy and TeamWin!

Thanks Dees_Troy and Team for getting this started!

Things are looking up, thanks guys!

Awesome to see action with this phone! Thanks!!

You da man

sharkie405 said:
fastboot boot /path/to/twrp.img reboots into TWRP, but it never goes past the teamwin splash screen. I am able to reboot the phone normally after that, so no biggie.
I don't have time now to mess with figuring out how to get you logs, but I'll do that later this evening. Just wanted to give you a quick "what happened when I tried it."
And THANK YOU for working on this for us so quickly!
Click to expand...
Click to collapse
Here are those logs.

Nice! Great to see the progress

Thanks for the progress guys. Has anyone tried flashing root from TWRP yet? I wonder if this process would work, if we used this modded TWRP... https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324

sharkie405 said:
Here are those logs.
Click to expand...
Click to collapse
Did you try unlocking critical?

cwalker0906 said:
Did you try unlocking critical?
Click to expand...
Click to collapse
Yes, I've already unlocked critical.
Sent from my Pixel 2 XL using XDA Labs

Great to see...this is the start!

I unlocked the bootloader without critical and was able to bootloader into twrp. No just figuring out a way to get root.

bggold said:
I unlocked the bootloader without critical and was able to bootloader into twrp. No just figuring out a way to get root.
Click to expand...
Click to collapse
From here we should be able to push ADB shell comands to edit build.prop right?

I just fastboot booted your .img. All functioning as expected except for the issues that you indicated.
Rebooted back to system without any issues.
Thank You Great Job!

chazall1 said:
I just fastboot booted your .img. All functioning as expected except for the issues that you indicated.
Rebooted back to system without any issues.
Thank You Great Job!
Click to expand...
Click to collapse
Have you unlocked critical?
Sent from my Pixel 2 XL using XDA Labs

Haven't flashed in over 2 years. Missing anything?

I went to the dark side in April 2016, and haven't flashed anything in about 2 years. Wife's tablet (flo) needs an update, MM is getting laggy though the tablet has always been good to us.
Titanium was getting to be crap around the last time I used it, with problems mostly restoring, does that still hold true? Might just use it to back up a couple apps she uses a lot and just use Play Store to restore the rest. It's not really important, just curious.
Downloading the TWRP app, I know TWRP is installed but willing to bet it needs to be updated and the app can do that.
Tablet is near its EOL, not planning on rooting it if the ROM doesn't come pre-rooted. I have no idea what Magisk is.
So I'm gonna go into TWRP, wipe system, wipe data, wipe cache, wipe dalvik. Flash ROM (going with Lineage 15.1). Now at one point 2-3 years ago the common wisdom was starting to become "flash ROM, boot ROM, reboot to recovery and then flash Gapps." Y'all still doing that? Or can I just flash Gapps right after flashing ROM and reboot then?
Bit nervous as I haven't flashed in a while, but also kind of exciting.

We've got Android 8.1 Oreo now... Working perfectly on our Nexus 7... You should check it out...

Any suggestions for which are the most stable roms to try? I'm in the same boat. I'm on android 6.0.1, stopped flashing things a while ago and it might even be official! But mine's running like a dog so think I wanna try something to jazz it up!

You should try pure Nexus rom based on 7.1.2 for ultimate good battery life. Oreo is Good but battery isn't the greatest.

Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING

ganggreen777 said:
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
Click to expand...
Click to collapse
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:

k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
Thanks so much for responding back!!!!
Tonight I will follow the steps. I trust it will go fine.
Excited to do this. ......yep I waited this long to root this device

k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
I did the 'install lineageOS on flo and installed TWRP latest. Seem like fastboot went into a slew of commands
and finished. I followed the steps to reboot into recovery and twrp is not there. Android dude opened with red triangle.
I have no clue whats up. I leave it sit, and it reboots into android splash screen and bootsup so i can use the tablet. I guess this is why I am soo perplexed. "Am i missing something?"

ganggreen777 said:
....twrp is not there. Android dude opened with red triangle.
...."Am i missing something?"
Click to expand...
Click to collapse
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html

k23m said:
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html
Click to expand...
Click to collapse
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device

Kevin_McLaughlin said:
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Click to expand...
Click to collapse
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.

k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this ordecr or else TWRP will be gone again.
Click to expand...
Click to collapse
Why u asking???? Have we chatted b4?¿?
I will do as stated above (I swear I am (thinking) I am doing it as above all the other times. (when you say copy output...is that from the fastboot dialogue? ) ...is it as easy as copy paste ...I dont remember how to copy via adb fastboot...
(Makes me wonder if twrp is really being fastbooted into the n7 2013
Thanks for helping.

k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
Click to expand...
Click to collapse
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.

ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs

ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:

beachfl said:
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
Click to expand...
Click to collapse
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS

ganggreen777 said:
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
Click to expand...
Click to collapse
BTW
I am great to go.....thanks very much for helping me thru
---------- Post added at 01:06 AM ---------- Previous post was at 01:04 AM ----------
k23m said:
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
Click to expand...
Click to collapse
BTW I am great to go... Thanks for sticking thru with me

Instructions to install twrp and root not wifi error on all rom

Resources:
1. TWRP img: https://drive.google.com/open?id=1M04t6uspBLDJfHXFfJQeOzqDRSk56UMF
2. TWRP zip: https://drive.google.com/open?id=16IbNJJspaqqimqdLeNGBnkRoj3rZ0zcR
Copy all into adb folder
Proceed:
1. Connect the device in fastboot mode, enter the command cmd: fastboot boot TWRP-3.3.1-1004-ASUS_ROG2-CN-wzsx150.img (boot, not flash boot, I do not write missing)
The machine will automatically boot into twrp
2. In Twrp choose Advanced => ADB sideload, enter the command: adb sideload TWRP-3.3.1-1004-ASUS_ROG2-CN-wzsx150.zip
3. Reboot into Twrp, select Advanced => Install root
Done, start and enjoy!
My telegram
https://t.me/rogphonevietnam2

That's work only on CN rom or also on WW?

dracoolia said:
That's work only on CN rom or also on WW?
Click to expand...
Click to collapse
All

Any other tested this method? Could someone else confirm this. Ty

iampatricktan said:
Any other tested this method? Could someone else confirm this. Ty
Click to expand...
Click to collapse
Working well

This works great! Thanks!

You install root or flash zip magisk 20?

dungnghien said:
You install root or flash zip magisk 20?
Click to expand...
Click to collapse
You just helped me on Telgram...Im rich...LOL. Im thinking magisk 20 should work. What do i know though?

suzook said:
You just helped me on Telgram...Im rich...LOL. Im thinking magisk 20 should work. What do i know though?
Click to expand...
Click to collapse
Oh. You can try 20!
suzook said:
I tried this...it booted fine with root, and wifi working, but the next reboot, slot was corrupt. I will try again
Click to expand...
Click to collapse

I think i will let someone else try 1st....LOL
dungnghien said:
Oh. You can try 20!
suzook said:
I tried this...it booted fine with root, and wifi working, but the next reboot, slot was corrupt. I will try again
Click to expand...
Click to collapse
Click to expand...
Click to collapse

my pc dont find fastboot mode
i try connect my rog phone 2 to pc and tell me waiting a device, anyone know how fix? thks

I have same pronlem, when I connect my phone on my laptop in adb that's work but when I'm in fastboot mode that's not find my phone any one can hepl, thx a lot

thermaldude said:
i try connect my rog phone 2 to pc and tell me waiting a device, anyone know how fix? thks
Click to expand...
Click to collapse
dracoolia said:
I have same pronlem, when I connect my phone on my laptop in adb that's work but when I'm in fastboot mode that's not find my phone any one can hepl, thx a lot
Click to expand...
Click to collapse
You guys using the side usb port?

suzook said:
You guys using the side usb port?
Click to expand...
Click to collapse
For me that's work well now I forget to edit PATH??, but I have a question when I install TWRP I dont active SU in advanced in TWRP, I install magisk zip to root my phone, but... because of that I lost TWRP, if I install again TWRP in fastboot I loose my root or not? Because both are boot image

dracoolia said:
For me that's work well now I forget to edit PATH??, but I have a question when I install TWRP I dont active SU in advanced in TWRP, I install magisk zip to root my phone, but... because of that I lost TWRP, if I install again TWRP in fastboot I loose my root or not? Because both are boot image
Click to expand...
Click to collapse
You lost twrp after flashing magisk.zip? That doesnt make sense

suzook said:
You lost twrp after flashing magisk.zip? That doesnt make sense
Click to expand...
Click to collapse
I was on ww 1908.12 with twrp installed. I then updated to magisk 20.0 by flashing the zip through twrp. This caused me to lose twrp and I get an error unbootable slot when trying to enter into recovery now. Since there is no dev support I figure I'm not missing much without it. I was able to update to the latest firmware ww1908.25 by downloading the file from the op gdrive link. Moving it to root then apply update. Go to magisk install to inactive slot and reboot.

sesz said:
I was on ww 1908.12 with twrp installed. I then updated to magisk 20.0 by flashing the zip through twrp. This caused me to lose twrp and I get an error unbootable slot when trying to enter into recovery now. Since there is no dev support I figure I'm not missing much without it. I was able to update to the latest firmware ww1908.25 by downloading the file from the op gdrive link. Moving it to root then apply update. Go to magisk install to inactive slot and reboot.
Click to expand...
Click to collapse
What you did is something different....you absolutely will lose twrp with an ota

Yeah same message, when I have installed zip of magisk with TWRP everything work well with magisk, but now when I want to boot on recovery I have big message in red
ERROR UNBOOTABLE SLOT

dracoolia said:
Yeah same message, when I have installed zip of magisk with TWRP everything work well with magisk, but now when I want to boot on recovery I have big message in red
ERROR UNBOOTABLE SLOT
Click to expand...
Click to collapse
Get back to Fastboot and run this command
fastboot set_active other
^ Then hit enter.
You can go back to recovery by
fastboot reboot recovery

sesz said:
I was on ww 1908.12 with twrp installed. I then updated to magisk 20.0 by flashing the zip through twrp. This caused me to lose twrp and I get an error unbootable slot when trying to enter into recovery now. Since there is no dev support I figure I'm not missing much without it. I was able to update to the latest firmware ww1908.25 by downloading the file from the op gdrive link. Moving it to root then apply update. Go to magisk install to inactive slot and reboot.
Click to expand...
Click to collapse
can you provide me with a link for the version 25 for ww?
and also i tried the method given in the first post but i still cannot connect wifi on my phone. I am on verion 21