Develop Bugs

[ROOT] N5206 v150108 - v150312 root method with working wireless

Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2.
Note: A more detailed and user-friendly version of these instructions can be found at: http://www.oppoforums.com/threads/n5206-international-root-instructions.24159
Download http://lum.uk/n3/files/recmodn3.img and http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
Copy the rooter onto your SD card.
Boot into fastboot by holding volume up while powering on the phone.
fastboot oem unlock
fastboot flash recovery recmodn3.img
fastboot boot recmodn3.img
Flash the root coloros zip file, reboot and you're rooted.
Note: This is a modified stock recovery that can flash OTAs as well as zips not signed by Oppo. If you prefer TWRP then that is available here: https://dl.twrp.me/n3/. Note that at the time of writing TWRP is unable to flash OTAs.
Thanks to [email protected] for the original root method, Arvin A. [email protected] for the fixing SuperSU to work on ColorOS, and [email protected] for providing the modified N3 recovery.

Restoring stock firmware
Download your chosen firmware and recovery from this thread
Copy the firmware to the root of the internal storage
Take a nandroid backup using TWRP
Reboot to bootloader from within TWRP
Code:
fastboot flash recovery recovery_N3.img
fastboot reboot
adb reboot recovery
Use the stock recovery to flash your chosen firmware
If you are downgrading then wipe data and cache (you did remember to take a nandroid, right?)
Reboot
You are now on stock fimware. Follow the rooting instructions in post #1, and if you wiped you may optionally restore only the data partition from your nandroid backup.

Will memory be erased?
Hi,
So i'm looking forward to root my beautiful Oppo N3.
On my last Phones memory (data and so on) was erased alongside with unlocking the phone.
Will it be the same on this phone so that I have to backup all my data?

Your data will not be erased when rooting or unlocking. Also your warranty will not be invalidated like it is with other manufacturers.
It is, however, always wise to take a backup before anything like this, just in case something does go wrong.

Hi,
I tried rooting my N3 now but i made a mistake by not executing the commands after falshing SuperSU.
That's why my phone is always booting into TWRP. There i tried executing your commands, but apparently the shell refuses to su by throwing exception: "command not found"
Going on with mount-command, it is also giving back an error: "can't find /system in /proc/mounts"
Hope sb could help me now...
EDIT: Solved by installing stock recovery, booting system, and the reflash twrp.

Lum_UK said:
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2
Download http://teamw.in/project/twrp2/282 and http://download.chainfire.eu/supersu
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.8.4.0-n3.img
fastboot reboot
adb reboot recovery
Flash Super SU from within TWRP. Then boot the OS
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and you're rooted.
By default ColorOS doesn't let apps auto-start themselves, so go into security centre and allow SuperSU to auto-start, otherwise you won't get prompts for root when other apps need it.
Thanks to invisiblek for the original root method and babelmonk for the fix. I have shamelessly copied these and adapted them for the new firmware.
Click to expand...
Click to collapse
Quoted from your post in oppo forum
Wait for the phone to boot:
adb reboot recovery
It should boot into TWRP recovery flash the SuperSU zip you downloaded but do not reboot as we need to fix a small bug in SuperSU due to Oppo not using the expected startup scripts.
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and congratulations. You are now rooted.
Sorry , quite new in fastboot command so i apologize if I misunderstood you but I'm running on N5206_EX_23_150208 , which should i follow ? to boot up after flashing SuperSU or not to boot up ?

It doesn't matter which way around you do it, just that root won't work outside of ADB until it's done.
I assume that XDA folk are more familiar with ADB etc. than on the Oppo forums so the instructions skip over more detail here.

Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.

Lum_UK said:
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Click to expand...
Click to collapse
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?

Anilexis said:
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Click to expand...
Click to collapse
Fixed it by flashing boot.img from 150208, root still there due to script edit.

Updated the OP to use the modified stock recovery (Wmjan's recovery for the N5207) as this will be friendlier to noobs and also make it easier to install OTAs.

Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/

cowabunga said:
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
Click to expand...
Click to collapse
Sorry for the delay in replying. I've re-hosted the file for you.
http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip

You could also try this. It worked on my girlfriend's R5 running a similar version of ColorOS. Didn't need modified recovery or anything, install it, run, click the root button, and it'll reboot to recovery and root for you.
http://lum.uk/n3/files/ForceRoot.apk

can this root work with Chines n5207

Hello,
I'm from Malaysia,
I got problem with my N3 / N5206 after update the newest version of software...now it cannot detect any line signal and open a wifi...what the problem,can u help me...

I can't make the WiFi to work again. Installed all versions of firmware and no luck....
Update: I was using the wrong tool to flash the firmware.
Don't update the phone with Msm8974DownloadTool !!!!
You have to download and install QPST_2.7.460 and place the phone in download mode by pressing volume + and power button and then in QPST load the firmware N5206EX_11_A.11_150528_SVN6225 or Oppo_N3_N5206_EX_11_A.13_151230 or N5206EX_11_A.10_150519_SVN6196
After flashing the wifi is working but you gonna loose the NV ram backup for the IMEI numbers..
Then you have to open dealpad with *#801# and anable Full-port ON
In QFIL(QPST) click on Tools then click QCN Backup Restore
Choose the qcn file and press restore.
Everything will work again after reboot the phone...

failed to flash ob 10 and can only boot into recovery now

Tried to flash flash ob 10, but twrp said the zip was corrupted. I could not boot into the system anymore.
The problem is the system partition is ok ( verified from twrp file manager), but every time I choose reboot system, it will go back to twrp. I tried to re-flash ob 9, but twrp again reported another error. Log is attached. How should I solve the problem?
By the way, I wipe all data, including storage in twrp by mistake. Is there any way to recover the data? I am traveling now, just got several hundred pictures.:crying::crying: It seems to be impossible to do it on a computer in MTP mode, but I could not boot into the system neither.

Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.

You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?

zTweaked said:
Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.
Click to expand...
Click to collapse
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Update: flashing stock recovery seems to be effective ( of course, twrp does not exist anymore ).

SoybeanYoung said:
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Click to expand...
Click to collapse
Unknown command is a known and harmless issue on all 7.x.x roms. Just ignore it and go ahead.
And I think I saw 3.0.2-1 twrp version in your log.
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
pmbabu said:
You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?
Click to expand...
Click to collapse
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.

After you flash any rom, reflash recovery. Reboot to RECOVERY & then to system.
The red message it's on almoust every Nugat rom. And it's about some log .

zTweaked said:
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.
Click to expand...
Click to collapse
He said he could only boot into twrp. That occurs (reboot to system will take it back to twrp over and over) only if someone tried an OTA update with twrp.

I don't think this is the case for you, but if you tried the other suggestions don't work try the below. I had a similar issue and found that my recovery partition was corrupted. However, an additional symptom I had was that my TWRP would hang completely when selecting reboot after any successful flash. I think modded TWRP does not like internal storage wipe from within TWRP (rather than through fastboot format userdata).
Boot to fastboot
Fastboot erase recovery
Fastboot flash recovery filename.img
Boot to recovery and flash your desired ROM+supersu which you can sideload via MTP (drag and drop from Windows) or adb push C:\SourceLocation\filename.zip /sdcard
I recommend ADB push over MTP.

Had the exact same problem as op, after some issues i was forced to use the unbrick method to get phone back as it wasn't even booting. Now im using beta 10 perfectly.

Did you manage to fix it? I have the same probem.

Can't install anything in TWRP

i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?

Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file

SubwayChamp said:
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file
Click to expand...
Click to collapse
it's not only with the roms, it's with everything
i've tried to flash new firmware, gapps and nothing works :/

well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery

SubwayChamp said:
well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery
Click to expand...
Click to collapse
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything

Citroon said:
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything
Click to expand...
Click to collapse
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again

SubwayChamp said:
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again
Click to expand...
Click to collapse
Tried that, still having the error:crying:

Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!

StonebridgeGr said:
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!
Click to expand...
Click to collapse
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this

Citroon said:
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this
Click to expand...
Click to collapse
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )

StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
i've tried about every RoM available.
I also want to note that i have flashed with this version of TWRP before (3.0.2.0)

StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
tried about every rom available, and other things just to see what would work and what wouldn't (nothing can flash)
im currently running 3.0.2.0 and have flashed with this version of TWRP before, but suddenly it stopped working

Citroon said:
Tried that, still having the error:crying:
Click to expand...
Click to collapse
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79

SubwayChamp said:
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79
Click to expand...
Click to collapse
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare

Citroon said:
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare
Click to expand...
Click to collapse
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/

SubwayChamp said:
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/
Click to expand...
Click to collapse
I finally got it working
I was so stubborn that I decided to install Windows Bootcamp on my mac
it was as simple as reinstalling TWRP and do a clean wipe, now i can install roms and all the other things as i please again.
-Thank you for your help!

root problem after update to beta 19

hi,
my oneplus 3 has been rote since i got it (i bought it on launch day) but since i updated it to the beta 19, my phone is no longer rooted : when i put the phone in fastboot it says that my bootloader it unlocked but all the apps who requier root are saying that the phne is not rooted and i cant get twrp to work. i tryied with the official app on my phone and with a program called "tool all in one" (https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993) and when i flash twrp from the program, i can boot into twrp but then i can't access my files and after i boot the phone, i can no longer boot to twrp
does anyone have a solution that doesn't involve me wiping the phone?

You loose root after updating. Try installing twrp again and then rooting it. Use the toolkit for oneplus 3. Simplifies the process

what do you mean by "then rooting it" ?
the program i use does the same thing as the toolkit and when i install twrp, as i said, it can boot on twrp one time and in twrp i can't access my files and after i boot the phone i can't get back to twrp ,i get the stock recovery

Unless your ROM has built-in root, after flashing TWRP, you have to flash SuperSU or Magisk to obtain root. Mere flashing of TWRP will not give you root.

I know but i can't get to the folder when the magisk file is : when in boot into twrp i cant see my files

Few details... it's quite difficult to help you.
What's the root method? Magisk, SuperSU or Kingroot? Which version?
Ps TWRP recovery is not depending by root, you just need to unlock bootloader (surely it's already unlocked) and flash the same recovery, from PC, via the command "fastboot flash recovery filename.img".
Now enter in TWRP:
1) Wipe /system and /cache;
2) Flash another time Open Beta 19;
3) Flash Magisk or SuperSU (be sure to have latest release);
4) Move TWRP img file from computer to device, then flash it another time (because firmware provides the OOS stock recovery);
5) Reboot and wait 5-10 minutes, because of cache rebuilding.
Tell me if you solve

I am using magisk
Yes my bootloader is unlocked
My problem is that when i flash twrp i cant access my files so i don't want to wipe system if i cant reflash something after
I think that I'll wait for the next update, maybe then it will work
But thank you for your help

Which version of TWRP do you have? Try eng.stk's latest version.

I tryied 3.1.1-2
The eng.stk is not available anymore

Your phone is encrypted, so you have to format data ( but your internal storage wiped by formating data, so back it up ,then only twrp read files in your storage)and flash custom kernel then boot restore backup .

how do you know that my phone is encrypted? i never encrypted it
i use titanium backup so i can't back my phone up until i get rot back

Whenever you flash stock ROM it encrypt if you boot into system directly . So twrp could not read internal storage. Whenever you flash stock ROM you must flash custom kernel or any other method to avoid encryption. This is happened to me and what I'd done is flash custom kernel before boot into rom
To save your data try this
https://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228

Who said that? Check this: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Edit: If you want to save items in internal storage, you can use ADB commands instead of TWRP. You can also simply copy and paste if your PC recognises the internal storage of your phone.

I succeeded but i had to clean everything and use the last backup i made a week ago
Thank you all for your help

[SOLVED] TWRP doesn’t let browse /sdcard files

I am having a problem it happened after I finally got to flash latest CosmicOS and set up a new password on my OP3. So, here’s what basically happened;
Once I got it up and running I noticed that home button and fingerprint sensor was completely disabled, then I tried to set up a new password (completely same password I used to decrypt my storage in TWRP 3.0.2-0) and fingerprint just in case but it didn’t react to me calibrating the fingerprint so I was like, ”alright, gladly I got a backup in TWRP”.
Once I rebooted to recovery it asked for a password as usually, once I typed that exact same password as before it just said wrong password, I tried it twice in case if I made a typo but still invalid password. And then I was panicing and pressed cancel and just rebooted back to OS.
I then removed all passwords there and booted back to recovery again, TWRP doesn’t ask for a password anymore but there’s a slider which says allow modifications or something similar and also there’s read only mode. When I slided the modification thing it just doesn’t show any of my files in sdcard folder when I go to ’Install’ tab but (0mb) instead. I even was able to browse and add files from my pc while phone was plugged in and in recovery mode, not anymore though.
Can anyone give me advice or help to get my oneplus 3 back in use? I have all the important files moved to my pc so I don’t mind losing files I have left in internal storage that much. Not if it’s necessary or easier workaround. thanks for reading this long-ass text :fingers-crossed:
EDIT: Issue SOLVED thanks to @AkR2014. I switched data partition from EXT4 to F2FS and then one more time back to EXT4 in TWRP's Wipe tab. (I was using latest blue_spark's TWRP-3.2.1-x version) and I was able to wipe data, system and both caches afterwards. After that I managed to flash new rom via USB-C to A with mounted USB flash drive on the other end and you know rest of the story. Do note that it WILL clear your internal storage so back up all the necessary files you need. And if you want to stay on F2FS data partition be sure to flash a ROM which supports it
EDIT2: There might be another way to mount your storage in TWRP but this is probably fail-proof method and worked for me

Oh and I couldn’t flash the Gapps in recovery after flashing the CosmicOs and nor I can’t now because of this haha. I can use my email though and send files through it from my another email if that helps

Vaahtopahvi said:
Oh and I couldn’t flash the Gapps in recovery after flashing the CosmicOs and nor I can’t now because of this haha. I can use my email though and send files through it from my another email if that helps
Click to expand...
Click to collapse
Try eng.stk's TWRP and clean flash ROM and Gapps.

tnsmani said:
Try eng.stk's TWRP and clean flash ROM and Gapps.
Click to expand...
Click to collapse
I couldnt find link for eng.stk TWRP, only people talking of it it. and what am I supposed to do with it once I get if you could explain? sorry for nooby questions

tnsmani said:
Try eng.stk's TWRP and clean flash ROM and Gapps.
Click to expand...
Click to collapse
Wait, I think I found it. But the question is can and do I need to update the latest eng.stk’s TWRP through fastboot? And if so, is there instructions topic somewhere?

So here's the latest update: I flashed twrp-3.1.1-2 via fastboot but once I go to recovery it still doesn't let me browse files in /sdcard and if I put new password in OS it doesn't match in TWRP. I have a OS where I can boot to but no Gapps installed.
People say formatting data in TWRP would work, I'm just scared if that doesn't work and won't let me boot to OS anymore (even though I have a TWRP back up which I made before wiping my OxygenOS system data and caches in my pc as well in my phone's storage atm) and I can't flash anything in recovery mode, is there anything I could do? I'm in desperate need of help right now.
In this CosmicOS i am using Android 8.1.0 and I'm afraid something isn't supporting it or so.

Vaahtopahvi said:
So here's the latest update: I flashed twrp-3.1.1-2 via fastboot but once I go to recovery it still doesn't let me browse files in /sdcard and if I put new password in OS it doesn't match in TWRP. I have a OS where I can boot to but no Gapps installed.
People say formatting data in TWRP would work, I'm just scared if that doesn't work and won't let me boot to OS anymore (even though I have a TWRP back up which I made before wiping my OxygenOS system data and caches in my pc as well in my phone's storage atm) and I can't flash anything in recovery mode, is there anything I could do? I'm in desperate need of help right now.
In this CosmicOS i am using Android 8.1.0 and I'm afraid something isn't supporting it or so.
Click to expand...
Click to collapse
As I said, flash eng.stk's TWRP. Simply flash the image to Recovery partition using the TWRP you already have. After that, wipe everything and clean flash the ROM. If anything goes wrong, you can use the Mega Unbrick guide method 2.
Here's the link to TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads

tnsmani said:
As I said, flash eng.stk's TWRP. Simply flash the image to Recovery partition using the TWRP you already have. After that, wipe everything and clean flash the ROM. If anything goes wrong, you can use the Mega Unbrick guide method 2.
Here's the link to TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Thanks for the reply and link. I understood most of the parts except flashing the image to Recovery partition. Am I supposed to find the eng.stk’s TWRP from my Install tab in my current TWRP? Because it doesn’t show any files there. Also do I download the latest 3.2.1-x TWRP from the link you provided?

Vaahtopahvi said:
Thanks for the reply and link. I understood most of the parts except flashing the image to Recovery partition. Am I supposed to find the eng.stk’s TWRP from my Install tab in my current TWRP? Because it doesn’t show any files there. Also do I download the latest 3.2.1-x TWRP from the link you provided?
Click to expand...
Click to collapse
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.

tnsmani said:
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
Click to expand...
Click to collapse
he is unable to mount storage via twrp , i have the sol but it will format your whole data / internal storage if your wiling to .
1 ) Go to twrp
2 ) wipe - > Advance wipe > change system file partation
3) if your on F2FS change to ext 4 or vice versa .
4 ) you will be able to mount sdcard
and dont flash this rom again , faceed same issue while flashing some oreo rom .
P.S : do it at your own risk .

AkR2014 said:
he is unable to mount storage via twrp , i have the sol but it will format your whole data / internal storage if your wiling to .
1 ) Go to twrp
2 ) wipe - > Advance wipe > change system file partation
3) if your on F2FS change to ext 4 or vice versa .
4 ) you will be able to mount sdcard
and dont flash this rom again , faceed same issue while flashing some oreo rom .
P.S : do it at your own risk .
Click to expand...
Click to collapse
Thanks man :highfive: I have really nothing to lose anyways so I gotta try that lol. How can I know whether I am on F2FS or EXT 4 though? And once it’s done can I access to my phone storage while it’s in recovery mode and just paste new rom to internal storage? Or do I need to push the rom via adb while in fastboot mode? Thinking to try out Paranoid rom which is based on Nougat, right?

tnsmani said:
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
Click to expand...
Click to collapse
Thanks for clarification tnsmani, appreciate the time you put into it. But as the person who replied to your text, I cannot mount the storage in TWRP which would prevent me of flashing pretty much anything on phone in TWRP.

Vaahtopahvi said:
Thanks man :highfive: I have really nothing to lose anyways so I gotta try that lol. How can I know whether I am on F2FS or EXT 4 though? And once it’s done can I access to my phone storage while it’s in recovery mode and just paste new rom to internal storage? Or do I need to push the rom via adb while in fastboot mode? Thinking to try out Paranoid rom which is based on Nougat, right?
Click to expand...
Click to collapse
yap you will be able to access your internal storage as well flash any thing you want from internal storage , no need to push via adb , use deskinfo app from playstore to check
the format of your data partition. yah try Omni 8.1.0 really awsome rom i am currently using. :laugh:

Vaahtopahvi said:
Thanks for clarification tnsmani, appreciate the time you put into it. But as the person who replied to your text, I cannot mount the storage in TWRP which would prevent me of flashing pretty much anything on phone in TWRP.
Click to expand...
Click to collapse
If you are able to boot into fastboot mode, you can install TWRP through ADB.
But you can not copy, paste in TWRP.

AkR2014 said:
yap you will be able to access your internal storage as well flash any thing you want from internal storage , no need to push via adb , use deskinfo app from playstore to check
the format of your data partition. yah try Omni 8.1.0 really awsome rom i am currently using. :laugh:
Click to expand...
Click to collapse
Great to hear that. Though I don’t have Gapps installed. Accidentally tried to flash the wrong one before the mounting problem occurred and now you know rest of the story :laugh:
I’ll try to find another way to check it though. Oh and as well as the ROM