Database Users

New N release 4/7/16

Is there a way to root NCP91K version of N
I believe we need a special image or boot loader file. Please point me in the right direction.

pospower said:
Is there a way to root NCP91K version of N
I believe we need a special image or boot loader file. Please point me in the right direction.
Click to expand...
Click to collapse
Hello pospower,
I hope you are new to the community, so first of all, welcome to the Nexus 6P section.
I advise you to read the sticky threads here at the section. First in the list would be: http://forum.xda-developers.com/nexus-6p/general/questions-section-t3214020
Over to your query now. Bootloader has no relation to rooting, except one, that it should be unlocked. Unlocking the bootloader will enable you to flash TWRP recovery, which in turn would be used to flash SuperSU v2.71 flash-able zip.
For detailed instructions, please refer to section #1, #2, and #6 in the following thread: [GUIDE] Unlock/Root/Flash for Nexus 6P
I hope this helps. Best regards.
DJBhardwaj

boot.img my bad i was refering to this below
Download the latest TWRP Recovery. Please note: if you're on MHC19I or above you must use TWRP 3.0.0-1 or above, otherwise TWRP won't be able to decrypt. Also, if you want to use TWRP with the Android N Developer Preview you must use TWRP 3.0.0-1 or above, and you must also flash the modified boot.img found here.

ok got twrp installed 3.0.2.0
flashed the boot.img from above post
flashed twrp.img
rebooted bootloader
rebooted into recocery but freezws on teamwin screen

pospower said:
ok got twrp installed 3.0.2.0
flashed the boot.img from above post
flashed twrp.img
rebooted bootloader
rebooted into recocery but freezws on teamwin screen
Click to expand...
Click to collapse
TWRP is having issues with encrypted filesystems right now. You can either flash TWRP v3.0.0 or decrypt your 6P.
The decryption process should be carried out just after you flash the modified boot.img.
To decrypt, you will need to connect your device in bootloader mode and enter the following command:
Code:
fastboot format userdata
(Please note that this will wipe your complete internal storage).

OK got twrp working 3.0.0
Now it's asking for a password to get to decrypted files.
Any suggestions?

pospower said:
OK got twrp working 3.0.0
Now it's asking for a password to get to decrypted files.
Any suggestions?
Click to expand...
Click to collapse
Did you decrypt your device? Check under Settings > Security > Encrypt phone. Is it showing "encrypted"?

DJBhardwaj said:
Did you decrypt your device? Check under Settings > Security > Encrypt phone. Is it showing "encrypted"?
Click to expand...
Click to collapse
I must have

pospower said:
I must have
Click to expand...
Click to collapse
Please confirm.
And by decryption, i mean that you first flashed the modified boot.img and then formatted the userdata.

DJBhardwaj said:
Please confirm.
And by decryption, i mean that you first flashed the modified boot.img and then formatted the userdata.
Click to expand...
Click to collapse
Yes this is what I did. Followed the steps exactly.

pospower said:
Yes this is what I did. Followed the steps exactly.
Click to expand...
Click to collapse
Give a try to v3.0.0-1, and let me know.

DJBhardwaj said:
Give a try to v3.0.0-1, and let me know.
Click to expand...
Click to collapse
tried 3.0.0-1 woudnt start froze on twrp screen
do i need to decryp data again?

pospower said:
tried 3.0.0-1 woudnt start froze on twrp screen
do i need to decryp data again?
Click to expand...
Click to collapse
If you don't mind doing it, I would say Yes!

reflshed boot.img
decrpted
rebooted
copied su to download folder
reflashe boot then twrp 3.0.0 rebooted boot then to recovery againg asking for password to decriped data
ugggg

pospower said:
reflshed boot.img
decrpted
rebooted
copied su to download folder
reflashe boot then twrp 3.0.0 rebooted boot then to recovery againg asking for password to decriped data
ugggg
Click to expand...
Click to collapse
That is weird. I have done the same thing like twice or thrice since the last two days, and it has worked like a charm.
If you're decrypted, TWRP v3.0.0-1 should work fine.
Are you sure you wiped complete storage using fastboot format userdata command?

Yes

pospower said:
Yes
Click to expand...
Click to collapse
Try switching to a different version of TWRP, and see if any one of them works for you.
v3.0.0-1, v3.0.1-0, or v3.0.2-0.

{Guide} How to Root ONEPLUS 3T (Unlock bootloader, TWRP Recovery, SuperSu)

Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting.
1. Download the ADB For Windows from here :-
https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k/view
2. TWRP: https://mega.nz/#!v9MmGQ5C!i5VroRopCVz2_Uoc6Mi2U6N4oDa0HK1SxCrkDrc4mwQ
3. SuperSu: https://mega.nz/#!eh13yLiC!3tkx_RkLg-D8T6mi35zDUB8AYEPLliBsL8yO1dmZbI8
Steps:
1.Backup Data
2.Unlock boot loader
3.Flash Recovery
4.Flash SuperSU
ENJOY
Video:
https://youtu.be/wwd31NU7VC0
Rooting OOS 4.0.3 ONEPLUS 3T
https://youtu.be/0QYp5tkBaao

Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?

Midomad said:
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Click to expand...
Click to collapse
Simply flash the full ROM.zip manually in recovery, typically 1.4GB.
That means not installing the incremental mini zips. And not installing from the settings menu.
It's up to you whether you want to wipe data or cache.

Midomad said:
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Click to expand...
Click to collapse
Download complete zip file n flash using two.

Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.

uttam.ace said:
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
Click to expand...
Click to collapse
yes if u follow the steps you wont have DM verity issuse.

uttam.ace said:
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
Click to expand...
Click to collapse
Dm verity zip is not needed when you flash SuperSu.

*winces* Ooh, all the files on file hosts? Why not just link to the legit sites?

Very easy to download the required files. Very simple step-by-step video guide. A+
Thanks for putting this together you made my night!

Thanks, I have unlocked bootloader, Installed TWRP, and Super Su.
one question though, when after setting my account going for nandroid backup there I found SYSTEM as well SYSTEM IMAGE.
what is difference between them, What thing should I backup.
Also there is showing your system is Unmounted, so when I should have to mount it.
Thanks to all Once again.

Hello guys, thanks for the guide!
I was wondering if anyone has faced the same problem as me - while trying to root the Oneplus 3T I constantly get a bootloop after flashing SuperSU. The latest TWRP (3.0.4.0) is installed without any problems in fastboot, the system is mounted as r/w, and I don't see any problems during flashing SuperSU package...
I've tried it before and after OOS 4.0.2, I've tried old and new, stable and beta versions of SuperSU, but either way the phone is stuck on bootscreen after flashing.
P. S. If I flash the official ROM after that - it boots up instantly without any errors... And with no root :/

I'm having the same problem

respectableafrican said:
I'm having the same problem
Click to expand...
Click to collapse
So nice to know I'm not alone!
Did you find a way to root your phone?

Try this SuperSU

I heard only SuperSU SR3 works

Just tried both versions (2.79 and the SR3 beta) - unfortunately, the same bootloop happens.

I flash twrp 3.0.4 then flashed RR N rom but twrp is not booting to system it boot again to twrp please help

nishant.roy24 said:
I flash twrp 3.0.4 then flashed RR N rom but twrp is not booting to system it boot again to twrp please help
Click to expand...
Click to collapse
Power off and boot instead of selecting reboot from twrp

hrsa said:
So nice to know I'm not alone!
Did you find a way to root your phone?
Click to expand...
Click to collapse
Oh yeah actually I did, just use the systemless root guide on r/oneplus (cant link because im new)

respectableafrican said:
Oh yeah actually I did, just use the systemless root guide on r/oneplus (cant link because im new)
Click to expand...
Click to collapse
Oh, finally - thank you so much!
Followed the guide on reddit page, and got the Magisk root, with Android Pay compatibility!
I wonder why it was so hard to find

Correct Way Of Rooting A Moto Z Play As Of Feb/ 17

Ok folks you're here because you have the need to root​MM 6 or Nougat 7.0 Only
As of February 2017 you need 3 things
Unlocked Bootloader
Motorola Device Manger (drivers):Download
1) TWRP ( Recovery)
2) Modified kernel (F2FS fixes)
3) SuperSu 2.79 R3 systemless root
TWRP can be found Here: TWRP
Modified Kernel can be found here:TWRP & Modified kernel
Download both the modified kernel, either the MM one Or Nougat 7.0, depending on which OS you are using and download the modified kernel to your internal sd card ( Our external sdcard can't be read by TWRP, so all flashable zips must be in your internal sdcard)
Flash recovery through fastboot Code: fastboot flash recovery (name of recovery).img
Do not reboot but use the volume buttons on the phone to select recovery from the menu on the fastboot screen.
Now we can flash the Modified Kernel which you have previously downloaded to your internal sd card.
Flash the Kernel.
Now download SuperSu
SuperSu:SuperSu 2.79 R3
NEW FOR NOUGAT 7.1.1 ONLY
Unlocked bootloader
Motorola device manager Download:Download["]Moto Device Manager
Twrp recovery downloaded into the same folder as fastboot
Gaining root differs from 7.0 or 6.0, you can only root with magisks 13 or above if you are running any stock based rom or custom based rom that doesn't have built in root, you no longer need to flash the F2FS fixed kernel on 7.1.1
Magisks Thread :Magisks Thread
You need to flash Magisks to disable dm-verity otherwise your phone will not boot this is because the stock kernel checks for any modifications to the system
That's it
Thanks to @Alberto97 & @tomparr

Will be useful for noobies
Enviado desde mi XT1635-02 mediante Tapatalk

Do you suggest disabling force encryption. I'm rooted but encrypted currently. If disabling would make significant speed boost I'm willing to take the pain of setting-up apps and stuff from scratch and format userdata

Nil253259 said:
Do you suggest disabling force encryption. I'm rooted but encrypted currently. If disabling would make significant speed boost I'm willing to take the pain of setting-up apps and stuff from scratch and format userdata
Click to expand...
Click to collapse
I'm unecrytped and see real no gain, I think it's more of a placebo effect.

is that superSU better than Magisk?

Do you still need official bootloader unlocking ? aka no more warranty ? Thanks

razorsbk said:
Do you still need official bootloader unlocking ? aka no more warranty ? Thanks
Click to expand...
Click to collapse
Yes

Thank you.
Sent from my XT1635-02 using Tapatalk

Will all this work with Windows 10?

shawnsac2000 said:
Will all this work with Windows 10?
Click to expand...
Click to collapse
It will if you have the right drivers installed

punkerEVO said:
is that superSU better than Magisk?
Click to expand...
Click to collapse
It's confirmed that you'll have root with SuperSu 2.79 R3, Magisk's may cause Issues under certain circumstances.
I'ver tried to keep as simple as possible because there's 2 other threads with root method's that are not up to date.

Thanks

dedraks said:
Thanks
Click to expand...
Click to collapse
Lol OK I can see where this could get confusing now.

Thanks flashallthetime.
I misread your instructions though and I am in trouble. I misread the bit about copying the modified kernel to internal SD card; instead I copied to external SD card (as I have always done with previous devices). I now can't flash the modified kernel because the newly flashed TWRP 3.0.2 doesn't have access to the external SD card.
The current state of the device is that it is stuck at the unlocked warning screen. It says "ID: bad key", but after flashing a recovery, it says "ID: N/A".
Is this consistent with the kernel not being flashed, or do I have another issue?
If I get an OTG cable, can I flash the modified kernel that way with TWRP? Can this version of TWRP access an OTG USB device on Moto Z Play?
Anyone? Thanks so much!!

You can use fastboot to flash boot.img.
---------- Post added at 02:28 PM ---------- Previous post was at 02:25 PM ----------
punkerEVO said:
Lol OK I can see where this could get confusing now.
Click to expand...
Click to collapse
How?

dedraks said:
You can use fastboot to flash boot.img.
Click to expand...
Click to collapse
Is that to me? Which boot.img, where do I find it? Thanks!

raymosaurus said:
Is that to me? Which boot.img, where do I find it? Thanks!
Click to expand...
Click to collapse
Yes.
Extract from the ROM in this post:
https://forum.xda-developers.com/moto-z-play/development/rom-stock-7-0-t3553213

raymosaurus said:
If I get an OTG cable, can I flash the modified kernel that way with TWRP? Can this version of TWRP access an OTG USB device on Moto Z Play?
Click to expand...
Click to collapse
Should do fine. Did not test with this version, but using Chinese twrp I could mount and afterwards access OTG partition. Don't see a reason why this one should behave differently.
If you want to use fastboot, the command should be (from memory): fastboot flash boot boot.img

tag68 said:
Should do fine. Did not test with this version, but using Chinese twrp I could mount and afterwards access OTG partition. Don't see a reason why this one should behave differently.
If you want to use fastboot, the command should be (from memory): fastboot flash boot boot.img
Click to expand...
Click to collapse
For God's sake people , don't use the Chinese TWRP. 2 people that I know have mistakenly wiped their IMEI with that junk.

dedraks said:
You can use fastboot to flash boot.img.
---------- Post added at 02:28 PM ---------- Previous post was at 02:25 PM ----------
How?
Click to expand...
Click to collapse
I have a flashable zip of the Nougat stock boot.img
Here https://www.androidfilehost.com/?fid=457095661767138793

Baseband file for XT1643 (ATHENE_INDIA) needed

No network on any ROM (stock & LOS-based ROMs). I might have flashed the wrong baseband file, can someone please give me the baseband specifically for India? Baseband required - M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST

meraj99 said:
I'm on RR Remix N and have TWRP 3.1.1 shreps for the recovery. I can flash RR without any issues but whenever I try flashing either a JX series ROM or a fully stock ROM, TWRP says 'Invalid Zip File Format'. I have access to both bootloader and recovery, everything else works fine. Can someone please guide me on what to do? Do I have to sideload the ROM via ADB? If so, please enlighten me about the procedure
Click to expand...
Click to collapse
Why not trying to reflash the twrp(may try another one from official website or of silesh nair on his thread).
I think you might have turn on md5 checksum or another this which keeps verifying the zip and no signature is found.
Reflashing is a good course as it do not erase any data of yours.

DgnrtnX said:
Why not trying to reflash the twrp(may try another one from official website or of silesh nair on his thread).
I think you might have turn on md5 checksum or another this which keeps verifying the zip and no signature is found.
Reflashing is a good course as it do not erase any data of yours.
Click to expand...
Click to collapse
I used 3 different versions of TWRP Still didn't help. And the MD5 checksums matched, zip signature verification has been disabled too

meraj99 said:
I used 3 different versions of TWRP [emoji14] Still didn't help. And the MD5 checksums matched, zip signature verification has been disabled too
Click to expand...
Click to collapse
Try this and report. After installing wipe cache, dalvik.
If flashing recovery is problem, reflash stock rom w/ stock recovery n boot ans try again to flash twrp, might sovle the issue
Link : https://drive.google.com/file/d/1EGS-uU1QBDbrP3G4lFUSVqDSHC_ZGpMR/view?usp=sharing
Sent from my Moto G4 Plus using Tapatalk

DgnrtnX said:
Try this and report. After installing wipe cache, dalvik.
If flashing recovery is problem, reflash stock rom w/ stock recovery n boot ans try again to flash twrp, might sovle the issue
Link : https://drive.google.com/file/d/1EGS-uU1QBDbrP3G4lFUSVqDSHC_ZGpMR/view?usp=sharing
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
can you please tell me how to use the stock recovery? It just says 'No Command' everytime I boot into it

meraj99 said:
can you please tell me how to use the stock recovery? It just says 'No Command' everytime I boot into it
Click to expand...
Click to collapse
Its power button followed by vol up, but hey that recovery ain't gonna help you. Im just saying you to reflash it as it will erase all the data of current twrp recovery which might interfere with another recovery(changes are negligible, but then too).
I gave you link to a 64-bit twrp made by dreamester and silesh nair. Try it and see if it works.

You can not flash stock ROM from TWRP or other custom recovery. You need a PC with Moto Drivers and fastboot tools installed. Then you have to flash the stock rom from fastboot (generally instructions are given inside rom zip in a file called 'flashfile.xml'). I can't say about flashing JX series ROM (maybe it needs you to be on stock first or something like that) but here are the files needed to install Motorola ADB and FASTBOOT drivers and ADB & FASTBOOT tools on windows pc:
https://firmware.center/software/Android/platform-tools/win/ and https://firmware.center/software/Motorola/
---------- Post added at 10:15 PM ---------- Previous post was at 10:11 PM ----------
meraj99 said:
can you please tell me how to use the stock recovery? It just says 'No Command' everytime I boot into it
Click to expand...
Click to collapse
To get into stock recovery press VOLUME UP while pressing and holding POWER button but you can't flash custom ROM or wipe SYSTEM from there. For that purpose use Official latest TWRP recovery from their website.

JackFrost said:
You can not flash stock ROM from TWRP or other custom recovery. You need a PC with Moto Drivers and fastboot tools installed. Then you have to flash the stock rom from fastboot (generally instructions are given inside rom zip in a file called 'flashfile.xml'). I can't say about flashing JX series ROM (maybe it needs you to be on stock first or something like that) but here are the files needed to install Motorola ADB and FASTBOOT drivers and ADB & FASTBOOT tools on windows pc:
https://firmware.center/software/Android/platform-tools/win/ and https://firmware.center/software/Motorola/
---------- Post added at 10:15 PM ---------- Previous post was at 10:11 PM ----------
To get into stock recovery press VOLUME UP while pressing and holding POWER button but you can't flash custom ROM or wipe SYSTEM from there. For that purpose use Official latest TWRP recovery from their website.
Click to expand...
Click to collapse
I already have these installed! But when I run RDS and connect my phone in fastboot mode to the computer, RDS doesn't detect it in the program. I mean, the device doesn't show up in the boxes below. But when I run 'fastboot devices' in CMD I can see my device connected. And can you pleeease tell me how to flash ROMs through the stock recovery?

meraj99 said:
I already have these installed! But when I run RDS and connect my phone in fastboot mode to the computer, RDS doesn't detect it in the program. I mean, the device doesn't show up in the boxes below. But when I run 'fastboot devices' in CMD I can see my device connected. And can you pleeease tell me how to flash ROMs through the stock recovery?
Click to expand...
Click to collapse
Stock recovery don't flash roms, thats why we use customs recovery. As he mentioned just flash the stock rom, enable usb debugging and oem unlocked. Just flash the files and again flash the recovery which ever suits you and thats it.
Note : take backup first as it wipes your internal storage.

DgnrtnX said:
Stock recovery don't flash roms, thats why we use customs recovery. As he mentioned just flash the stock rom, enable usb debugging and oem unlocked. Just flash the files and again flash the recovery which ever suits you and thats it.
Note : take backup first as it wipes your internal storage.
Click to expand...
Click to collapse
well, how do I flash...? When I try to flash using TWRP it gives the error. I've tried almost all available TWRP v3+ recoveries

meraj99 said:
well, how do I flash...? When I try to flash using TWRP it gives the error. I've tried almost all available TWRP v3+ recoveries
Click to expand...
Click to collapse
Go into bootloader and then flash the file linked below from computer.
Note : usb debugging is must.
Link : https://www.google.co.in/amp/s/foru...tock-rom-npjs25-93-14-4-march-1-t3608138/amp/

DgnrtnX said:
Go into bootloader and then flash the file linked below from computer.
Note : usb debugging is must.
Link : https://www.google.co.in/amp/s/foru...tock-rom-npjs25-93-14-4-march-1-t3608138/amp/
Click to expand...
Click to collapse
yoooo!!! IT worked! Thank you so much! ^_^

DgnrtnX said:
Go into bootloader and then flash the file linked below from computer.
Note : usb debugging is must.
Link : https://www.google.co.in/amp/s/foru...tock-rom-npjs25-93-14-4-march-1-t3608138/amp/
Click to expand...
Click to collapse
erm, my SIM isn't being detected... WiFi works fine

meraj99 said:
erm, my SIM isn't being detected... WiFi works fine
Click to expand...
Click to collapse
Just flash twrp and which ever rom you like, and see if they are working or not.

DgnrtnX said:
Just flash twrp and which ever rom you like, and see if they are working or not.
Click to expand...
Click to collapse
Not working

meraj99 said:
Not working
Click to expand...
Click to collapse
I think reflashing the stock rom is the only thing to do. Read carefully whatever is written in that thread. And see if all the commands are properly exicuted.
I dont know any work around for sim as i have never had that issue. Tell me if its solved or not for just a bit of knowledge.
Edit : just for reference you are not using moto g4 play device, are you?

Standard ROM and recovery cannot be flashed by TWRP, only in fastboot mode.

DgnrtnX said:
I think reflashing the stock rom is the only thing to do. Read carefully whatever is written in that thread. And see if all the commands are properly exicuted.
I dont know any work around for sim as i have never had that issue. Tell me if its solved or not for just a bit of knowledge.
Edit : just for reference you are not using moto g4 play device, are you?
Click to expand...
Click to collapse
nah, G4+. Problem is with the baseband

meraj99 said:
nah, G4+. Problem is with the baseband
Click to expand...
Click to collapse
I flashed that firmware 2 days ago and is working fine for me, try flashing baseband then. Idk link for it search in Google for it

DgnrtnX said:
I flashed that firmware 2 days ago and is working fine for me, try flashing baseband then. Idk link for it search in Google for it
Click to expand...
Click to collapse
that's what I'm looking for. I need the Indian baseband file, do you know where i can get it

Couldn't update Installation problem with august update

So this week i hadn't time enough to install the august update since my phone is rooted so i decided to do it now. What i did before trying to download the update :
1.Deleted all magisk modules that i had then rebooted
2.Unistalled magisk using restore image then rebooted
3.Went to sys update downloaded and it says installation failed
What do to? I'm not rooted now and i don't have twrp installed.
PS. don't want to install it via fastboot/miflash

Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.

emiljano539 said:
PS. don't want to install it via fastboot/miflash
Click to expand...
Click to collapse
If you don't want to use Miflash (Why ?) you can boot temporary TWRP and flash .zip here:
https://forum.xda-developers.com/showpost.php?p=77353883&postcount=542

sipollo said:
If you don't want to use Miflash (Why ?) you can boot temporary TWRP and flash .zip here:
https://forum.xda-developers.com/showpost.php?p=77353883&postcount=542
Click to expand...
Click to collapse
Do i lose my data if i flash this via twrp?
Idk i don't really trust miflash

emiljano539 said:
Do i lose my data if i flash this via twrp?
Idk i don't really trust miflash
Click to expand...
Click to collapse
You won't lose your data.

ludditefornow said:
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
Click to expand...
Click to collapse
flashed the stock boot image tried to install it but again it shows that error , i guess the only thing i can do is to flash it manually via fastboot/miflash

sipollo said:
You won't lose your data.
Click to expand...
Click to collapse
Okay thanks, do i have to remove the magisk and flash the stock boot.img or it doesn't matter?

emiljano539 said:
Okay thanks, do i have to remove the magisk and flash the stock boot.img or it doesn't matter?
Click to expand...
Click to collapse
It doesn't matter. You'll have to reinstall Magisk (if you want to).

sipollo said:
It doesn't matter. You'll have to reinstall Magisk (if you want to).
Click to expand...
Click to collapse
which one should i install from them because there are 2 tissot-T files ( for twrp)
"tissot-T-OPM1.171019.026.8.8.23.zip" or "tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip" ?

emiljano539 said:
which one should i install from them because there are 2 tissot-T files ( for twrp)
"tissot-T-OPM1.171019.026.8.8.23.zip" or "tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip" ?
Click to expand...
Click to collapse
tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip
The other file is the latest beta.

sipollo said:
tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip
The other file is the latest beta.
Click to expand...
Click to collapse
I installed the zip from twrp and now after reboot i am stucked in bootloop now i can't even boot into twrp. What to do?
After i flashed it in the end says:
Failed to mount /system Invalid argument

Which TWRP did you use?

sipollo said:
Which TWRP did you use?
Click to expand...
Click to collapse
the official one. what version should i use?
its funny now that i flashed the stock rom via mi flash tool and now again the installation shows error..

ludditefornow said:
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
Click to expand...
Click to collapse
I'm facing same issue and I was following the guide.

Same here, can't install set Ota, even after remove magisk.
Other thing, cell won't show screen to put pin to boot, previous pin of sim so I think encryption is disable!? Any idea?