Database Users

[RECOVERY] Unofficial TWRP

This is an unofficial port of TWRP for the OnePlus 3
Downloads:
https://basketbuild.com/filedl/devs?dev=Grarak&dl=Grarak/oneplus3/recovery.img
Sources:
https://github.com/Grarak/android_device_oneplus_oneplus3
https://github.com/Grarak/android_kernel_oneplus_msm8996
Installation:
Download the recovery image and make sure your bootloader is unlocked
reboot into fastboot and execute
Code:
fastboot flash recovery recovery.img
Known issues:
Mouse pointer is hovering in the middle of the screen all the time, doesn't affect usability.
I am not sure if OTG works right now, last time I tried it didn't.
Everything else is working including decryption!
XDA:DevDB Information
TWRP OnePlus 3, Tool/Utility for the OnePlus 3
Contributors
Grarak
Version Information
Status: Beta
Created 2016-06-18
Last Updated 2016-06-18

hello, i have problems copying my old files to my new OP3 and i think it might have something to do with the encrypted storage on the new phone. (when i copy my files to the phone, the last modified date changes to the current date and i want to keep the correct timestamps)
how can i decrypt the data partition in twrp?

~MaX~ said:
hello, i have problems copying my old files to my new OP3 and i think it might have something to do with the encrypted storage on the new phone. (when i copy my files to the phone, the last modified date changes to the current date and i want to keep the correct timestamps)
how can i decrypt the data partition in twrp?
Click to expand...
Click to collapse
TWRP will either automatically decrypt your data or ask for your password.

OTG doesn't work.

How does this differ from the other twrp thread thats already posted?

This ones handles device encryption (which is on by default)
Therefore you can see/use internal storage

Vitriol_Drinker said:
This ones handles device encryption (which is on by default)
Therefore you can see/use internal storage
Click to expand...
Click to collapse
I can see and access my internal. Even made a stock backup.

Awesome! I hope OTG can be sorted soon Thanks for all your efforts Grarak
Sent from my ONE A2003 using Tapatalk

Awesome work man, now I'll get to enjoy Broken OS when I get my OP3.

fix-this! said:
I can see and access my internal. Even made a stock backup.
Click to expand...
Click to collapse
Can you upload the stock recovery somewhere?
If you did back it up, before installing TWRP?
Gesendet von meinem OnePlus One

jamesn2k said:
Awesome work man, now I'll get to enjoy Broken OS when I get my OP3.
Click to expand...
Click to collapse
Where did you see BrokenOs for OP3?? I'm very intrested! Thanks.

After flashing SuperSU in TWRP and doing a factory reset/wipe, how long should it take the OP3 to boot?
I feel like I've been stuck on the 1+ Powered by Android screen for far too long.

Grarak said:
This is an unofficial port of TWRP for the OnePlus 3
I have a problem with that recovery. Every time after I restore a backup I have made with that recovery my phone starts up and the unlock pattern is not valid anymore.
I have that now for the third time. Do you have a fix for that?
Edit: Fixed the pattern. But there is something wrong with that recovery. Please fix that
Click to expand...
Click to collapse

Planet X said:
I have a problem with that recovery. Every time after I restore a backup I have made with that recovery my phone starts up and the unlock pattern is not valid anymore.
I have that now for the third time. Do you have a fix for that?
Edit: Fixed the pattern. But there is something wrong with that recovery. Please fix that
Click to expand...
Click to collapse
i have the same issue^^ after restoring any rom, my pin / my pattern isn't valid anymore.

Planet X said:
I have a problem with that recovery. Every time after I restore a backup I have made with that recovery my phone starts up and the unlock pattern is not valid anymore.
I have that now for the third time. Do you have a fix for that?
Edit: Fixed the pattern. But there is something wrong with that recovery. Please fix that
Click to expand...
Click to collapse
From Nexus 6P guide - 4. How To Make A Nandroid Backup With TWRP Recovery:
Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Fingerprint) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue. Boot into TWRP and use the built in file manager to delete /data/sytem/locksettings.db. This should be enough to get you into your OS again. If it isn't you can also try deleting /data/system/locksettings.db-shm and /data/system/locksettings.db-wal. If this still doesn't fix your issue you can delete /data/system/gatekeeper.password.key and /data/system/gatekeeper.pattern.key.
Click to expand...
Click to collapse
I had to do it few times when I was restoring nandroid with pattern secured lock screen.

Natakranta said:
From Nexus 6P guide - 4. How To Make A Nandroid Backup With TWRP Recovery:
I had to do it few times when I was restoring nandroid with pattern secured lock screen.
Click to expand...
Click to collapse
That was what I had to do: delete /data/system/gatekeeper.pattern.key from Filmmanager. But still, that shouldn't be necessary.

why are there 3 different twrp threads? which one is recommended to use?

Did anybody try to
fastboot boot recovery.img
it?
It's not booting this way. I wanted to just boot it from PC and make a nandroid of all partitions including stock recovery.

i had the pattern issues too, luckily when i made the 1st initial back up of 3.1.0 i didn't have a key, b/c when i flashed 3.1.3 full zip xposed does not work, so i had restore my 3.1.0 nandroid and dirty flash the 3.1.3 after i installed xposed.
so in other words if u clean flash the 3.1.3 zip via TWRP i cannot get xposed to work

After updating to full OxygenOS 3.1.3 I can no longer flash this recovery does anyone have any suggestion ?
I try just like before but when I want to reboot into recovery from the OS it says "Factory device reset....rebooting"
And then it boots into OnePlus recovery
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (17776 KB)...
OKAY [ 0.398s]
writing 'recovery'...
OKAY [ 0.136s]
finished. total time: 0.536s
Click to expand...
Click to collapse
---------- Post added at 23:12 ---------- Previous post was at 22:35 ----------
I was finally able to boot into recovery using "fastboot boot" and flash SuperSU like this but now I am still on stock recovery.
Good thing is that this way i hope to receive the next OTA so till then I will probably try and stay this way.

Mi Note 2 bricked! Request for solution

Dear all,
I stupidly bricked my Mi Note 2 by doing OTA with TWRP installed (at least I think that is the reason) - although I have done this once with success, but at the second time, the phone won't boot anymore.
- In TWRP, it says that the internal storage is encrypted and prompts me for code
- In TWRP the storage cannot be mounted (none of the partitions can be mounted)
- Tried to flash stock ROM or stock recovery in fastboot mode, seems like the internal storage cannot be accessed either
- With Mi Assistant, still no lock
It seems that the internal storage is totally corrupted...
What can I do without going to service (luckily I'm in China right now...)? Perhaps ADB sideload stock ROM would work?
Thanks!

Delete data partition an try reboot

Can't. Got some error message - see attached.
Sense like that the internal storage can't be found at all...

Also tried to side load DEV rom via adb, but got the attached error.
No clue how to proceed...

1. Format your data partition, and then reboot TWRP. This will decrypt your phone.
2.After entering TWRP, wipe all partition and then reboot TWRP
3.Copy your ROM file into your phone, and then flash ROM

Kris Chen said:
1. Format your data partition, and then reboot TWRP. This will decrypt your phone.
2.After entering TWRP, wipe all partition and then reboot TWRP
3.Copy your ROM file into your phone, and then flash ROM
Click to expand...
Click to collapse
Hi, I have assumed this as well, however didn't figure out a way to format the data partition. In my previous screenshot I showed the error ("unable to mount" or "no such device") when trying to delete the data partition.
Do you have a more detailed instruction?
Thanks!

Here you are.
See that "Format Data" ?
CrisperNeO said:
Hi, I have assumed this as well, however didn't figure out a way to format the data partition. In my previous screenshot I showed the error ("unable to mount" or "no such device") when trying to delete the data partition.
Do you have a more detailed instruction?
Thanks!
Click to expand...
Click to collapse

Kris Chen said:
Here you are.
See that "Format Data" ?
Click to expand...
Click to collapse
That's exactly what I have done... However: "unable to mound" or "no such device", it did not work

Which one of TWRP version do you use now ?
---------- Post added at 09:51 PM ---------- Previous post was at 09:46 PM ----------
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
I use this version !

Kris Chen said:
Which one of TWRP version do you use now ?
---------- Post added at 09:51 PM ---------- Previous post was at 09:46 PM ----------
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
I use this version !
Click to expand...
Click to collapse
3.0.2-X by BY~XM

Do you want to switch mostly updated one and try again?
Sometime it may come from outdated version of TWRP.
CrisperNeO said:
3.0.2-X by BY~XM
Click to expand...
Click to collapse

Kris Chen said:
Do you want to switch mostly updated one and try again?
Sometime it may come from outdated version of TWRP.
Click to expand...
Click to collapse
Actually I cannot flash any recovery now: FAILED (remote: flash write failure)

Download fastboot rom and flash it with miflash tool.

Can you enter fastboot mode ? If yes, then you can do (1)as dtsun said that; (2)flash the new version of TWRP(fastboot flash recovery xxxx.img ===> "XXXX.img" means the whole file name of TWRP image file), rebooting to TWRP again and then flash your recovery ROM.

dtosun said:
Download fastboot rom and flash it with miflash tool.
Click to expand...
Click to collapse
tried and also no luck, internal storage seems like not accessible

Kris Chen said:
Can you enter fastboot mode ? If yes, then you can do (1)as dtsun said that; (2)flash the new version of TWRP(fastboot flash recovery xxxx.img ===> "XXXX.img" means the whole file name of TWRP image file), rebooting to TWRP again and then flash your recovery ROM.
Click to expand...
Click to collapse
I can enter fastboot, but like said before, cannot flash any recovery

Sorry for that. It's indeed that you have bricked your phone
Now you need to find local mobile store to repair it, or prepare for another phone - Mi 6 ~

dtosun said:
Download fastboot rom and flash it with miflash tool.
Click to expand...
Click to collapse
Do this.

What error are you getting when trying to flash MIUI fastboot rom?
I have had this problem before on my redmi note 3, although the cause was from flashing TWRP not OTA.
I tried everything I could think of to try fix it, in the end flashing fastboot rom and clean all and lock with mi flash tool was the only way.
You'll need to use mi unlock to unlock the phone again but that is easy if you have done it before.
Did you use official way to unlock bootloader?

Reply to all above:
I unlocked the phone in the official way;
Miflash didn't work, because the internal storage is not accessible.
So lessons learned: never do OTA update if you have a custom recovery installed.
But:
Latest report:
Sent back to Xiaomi (luckily I'm in China right now) and Xiaomi was awesome, the engineer replaced the main board and it costed me nothing...

Create Stock Recovery.img from FTF File

Hi, I am in the process of preparing for upgrading from 7.0 to 7.1.1
I know I need to replace the Custom Kernel with the Stock Kernel. And I have to replace TWRP with Stock Recovery.
Can anybody tell me, which file inside the FTF is the stock recovery? I already found the kernel. Need help to find the stock recovery, thank you!

tempurastyle said:
Need help to find the stock recovery, thank you!
Click to expand...
Click to collapse
We don't have one which is why we have to use TWRP.

So my only way is to flash via Flashtool without wipe?

tempurastyle said:
So my only way is to flash via Flashtool without wipe?
Click to expand...
Click to collapse
Do that then mod your own kernel. [How To] make your own XPERIA DRM-fix kernel.
And flash a TWRP.img to the recovery partition.

fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.

realtuxen said:
fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.
Click to expand...
Click to collapse
this is real knowledge, thanks! so just to be sure, this is what i will do in flashtool:
1) wipe: nothing selected
2) exclude: fotakernel.sin selected
can anybody confirm this is correct?
then after this, i will flash a custom kernel via fastboot and magisk via twrp.
one question regarding magisk: will it be deleted during the flashtool update?

So I ran into a problem...
The Upgrade to 7.1.1 via flashtool was smooth. Then, i flashed twrp via fastboot as usual. When I tried to enter twrp, i get a password prompt to decrypt the phone. So i don't know which password i need to type in. I tried the unlock PIN, doesnt work. Any suggestions?

tempurastyle said:
Any suggestions?
Click to expand...
Click to collapse
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.

XperienceD said:
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.
Click to expand...
Click to collapse
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.

tempurastyle said:
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.
Click to expand...
Click to collapse
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)

Also if you do the above fastboot format commands suggested in post#8 without disabling 'forceencrypt' for /data (fstab in the kernel image or with a tool) the phone will encrypt itself again as soon as you turn it on.
If forceencrypt is disabled the same can be achieved (clearing encryption) with a factory reset btw.
So if you did not bump into the password in twrp before you likely did a factory reset with a kernel with encryption disabled. Then, maybe after updating you rebooted stock and the phone encrypted itself again, then now you can not access /data in twrp. Thats also because we have no version of it that supports encryption on the X-compact though. Again do not worry, I have not meet a zip I could not flash, supersu, magisk, etc because they do not access /data anyway.

realtuxen said:
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)
Click to expand...
Click to collapse
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!

tempurastyle said:
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!
Click to expand...
Click to collapse
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
The 1. ssue is really odd! I use the second twrp you posted, for some wierd reason the first one does not boot for me (twrp does not start). But I talked with another guy for him it was the other way around. It was really strange. I think most can use both though without problems
There is one more twrp 3.1 from bambamx, but I really do not get this, twrp boots from its own partition with its own kernel. They should be separated unless twrp does something to system ofcause which it very well shouldn't unless you ask it to, deleting a important file or flashing something. I have never heard of this sorry. One thing is certain our device sure could use a stable nougat encryption compatible twrp!
I will let you know if I find something, you can try the last available version, I have no idea if it will exhibit the same strange behaviour. But maybe its worth a shot although it seems something else is at play.
A couple of stupid questions sorry; You disabled dm verity and sony ric in ta poc right, and it does not happen if you boot your phone normal a couple of times.
Edit: sorry Mr. Sandman had not left so I did not read properly here from the morning. I will edit my post to actually answer as best as I can lol.

Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
2. You do not need write access to /data partition to install Magisk. It was explained in another thread that Magisk can use /cache temporary when access to /data is not available. It will write to /data on first boot instead.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.

realtuxen said:
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
Click to expand...
Click to collapse
I did, but the SD card can't be selected, and the size shows as 0kb. I did a workaround though: i formatted a spare sd card and copied magisk on it. it was instantly recognized and selectable.
ypnos42 said:
Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.
Click to expand...
Click to collapse
GREAT advice! I launched TWRP from ADB and successfully flashed Magisk using ADB sideload. Thanks, my phone is rooted again!

[Guide] How to decrypt data on Mate 9 (hi3660) [2018-11-01]

Hi .
I'm tired with Huawei's encryption. It's ok with Emui Rom but for AOSP (or other based on it) it's annoying :crying:
So use this guide for remove it definitively
WARNING !!
ALL YOUR DATA WILL BE DELETED ,SO BACKUP ALL YOUR PICTURES,VIDEO ETC ... TO YOUR PC OR IN EXT SDCARD
Download and copy in sdcard,not internal ,in attached files my :
- Huawei_remove_encyption_data
- Custom TWRP 3.2.3 recovery
rename my twrp_recovery.img.zip to twrp_recovery.img (remove .zip at the end, it's for upload this files into xda (size files))
or
in Android File Host
Download
HERE
PROGRESS :
Boot into fastboot, and Run
"fastboot -w", to wipe crypto
without rebooting flash included patched TWRP (fastboot flash recovery_ramdisk twrp_recovery.img)
Boot into TWRP, then Wipe internal storage, Wipe > Format Data then write "Yes"
Then flash my Huawei_remove_encyption_data script
reboot into TWRP recovery
Now you could continue to flash AOSP/LOS/CUSTOMS ROMs
And we're Done
Changelogs
2018-11-01
* Add new Android File Host Download link
* Add new MINADBD
* Fix selinux denial with stock kernel
Click to expand...
Click to collapse
Note:
If you want to come back to stock EMUI/Encryption data ,reboot into erecovery and use "download last firmware and recovery" and follow the steps
Enjoy :good:
Creadits:
@AL_IRAQI for the inspiration of this guide

Updated 2018-10-24
* Update script with busybox mount program , more stable as previous script
* Update TWRP with Static Busybox ,last teamwin stuff and some other fix

This is on a good path, thank you brother for your work ...:good:

I tried on my VTR-L29C432 (P10) and it worked!
Now I can flash files from my internal storage.
It works on EMUI and custom roms, even android 9. @micky387 Thank you so much for this tool bro

It just isnt working for me.
it installs twrp, but it fails with the wiping
when i try to format data it says cannot mount storage
acant install any rom either.
also refuses to download latest update in emui recovery
man, does huawei suck!

caniranges said:
It just isnt working for me.
it installs twrp, but it fails with the wiping
when i try to format data it says cannot mount storage
acant install any rom either.
also refuses to download latest update in emui recovery
man, does huawei suck!
Click to expand...
Click to collapse
Which device ,mate 9 ?
download again and try the new files. I have updated my twrp and script for more support

After flashing custom ROM, my data partition was encrypted.

Need some help here.
I have a mate 9 US variant. I was directed here from [Recovery][10-09-2018][3.2.3-0] TWRP for the Huawei Mate 9 (hi3660) (https://forum.xda-developers.com/mate-9/development/recovery-twrp-huawei-mate-9-hi3660-t3834796).
1) Successfully installed TWRP 3.2.3.
2) Backed up my /system partiton using TWRP to my ext SD card.
3) Boot into fastboot and run "fastboot -w". It shows
"
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.078s]
finished. total time: 0.078s
"
Not sure it is successful or not.
4) No rebooting and flash TWRP 3.2.3 again.
5) reboot to TWRP successfully, but not able to format data. It shows "failed to mount '/data'"
---------------------------------------------------------------------------------------------------------------------------------------------
Just found these two post have different TWRP files. The version numbers are the same, but file sizes are not. Is successful with the TWRP posted in this page.

@micky387 Hi!
One Question, the fstab file was taken from Honor View 10 forum or you modded that? Because I the one that I'm using was taken from there.
First I did the wipes on Twrp but my internal storage wasn't recognized when the phone booted, so I had to wipe using stock recovery and it worked, now I can use my internal memory on Twrp.

Hi guys.
OP updated
* Update script with busybox mount program , more stable as previous script
* Update TWRP with Static Busybox ,last teamwin stuff and some other fix
Click to expand...
Click to collapse

soft-touch said:
After flashing custom ROM, my data partition was encrypted.
Click to expand...
Click to collapse
Try with new stuff.
swith to busybox for more device variant support
huhtan said:
Need some help here.
I have a mate 9 US variant. I was directed here from [Recovery][10-09-2018][3.2.3-0] TWRP for the Huawei Mate 9 (hi3660) (https://forum.xda-developers.com/mate-9/development/recovery-twrp-huawei-mate-9-hi3660-t3834796).
1) Successfully installed TWRP 3.2.3.
2) Backed up my /system partiton using TWRP to my ext SD card.
3) Boot into fastboot and run "fastboot -w". It shows
"
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.078s]
finished. total time: 0.078s
"
Not sure it is successful or not.
4) No rebooting and flash TWRP 3.2.3 again.
5) reboot to TWRP successfully, but not able to format data. It shows "failed to mount '/data'"
---------------------------------------------------------------------------------------------------------------------------------------------
Just found these two post have different TWRP files. The version numbers are the same, but file sizes are not. Is successful with the TWRP posted in this page.
Click to expand...
Click to collapse
Same, use new script and twrp in OP and report
sfoot13 said:
@micky387 Hi!
One Question, the fstab file was taken from Honor View 10 forum or you modded that? Because I the one that I'm using was taken from there.
First I did the wipes on Twrp but my internal storage wasn't recognized when the phone booted, so I had to wipe using stock recovery and it worked, now I can use my internal memory on Twrp.
Click to expand...
Click to collapse
Hi,
first, fstab is from Mate 9. The only diff with View 10 is this line.
Code:
/devices/platform/e7f00000.hifi_usb/* auto auto defaults voldmanaged=usbotg:auto
you can add it in my fstab if you want for your device
for the second question ,I have already noted that for me, just restart in recovery mode to fix this
With TWRP do you use ?

micky387 said:
Hi,
first, fstab is from Mate 9. The only diff with View 10 is this line.
you can add it in my fstab if you want for your device
for the second question ,I have already noted that for me, just restart in recovery mode to fix this
With TWRP do you use ?
Click to expand...
Click to collapse
Thanks for the answer
On my last testing, I flashed your fstab without problems and wiped using stock.
To flash your zip, first I need to use this twrp https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 it boots even if the phone is encrypted but you need a sdcard, after the decrypt is done, I replace it with this twrp https://marijuana.ddo.jp/cm/recovery

sfoot13 said:
Thanks for the answer
On my last testing, I flashed your fstab without problems and wiped using stock.
To flash your zip, first I need to use this twrp https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 it boots even if the phone is encrypted but you need a sdcard, after the decrypt is done, I replace it with this twrp https://marijuana.ddo.jp/cm/recovery
Click to expand...
Click to collapse
Thanks do you have a xda link of the second TWRP ?
It's just to see if it use too a symlinks script for our partitions

micky387 said:
Thanks do you have a xda link of the second TWRP ?
It's just to see if it use too a symlinks script for our partitions
Click to expand...
Click to collapse
No, I saw the link on this post https://forum.xda-developers.com/showpost.php?p=77262856&postcount=166 but I think @love_marijuana is the dev, because of the splash screen of the twrp :silly: talk to him bro.

OP Updated
2018-11-01
* Add new Android File Host Download link
* Add new MINADBD
* Fix selinux denial with stock kernel
Click to expand...
Click to collapse
We can use all TWRP feature now in Stock kernel.
Because Huawei has removed setenforce permission into kernel , the recovery script (setenforce 0) dont work , so "use" adb and other stuff was blocked by selinux
Fix all selinux denial by this commits

Return to stock emui/encryption
Hello!
I have a mate 9 c432 b370 with LineageOS 16 by micky (but due to stopped development i want to go back, the other treble roms just aren't working that well as rhis one, and I'm having a bit of bad battery life right now)
My question is:
"If you want to come back to stock EMUI/Encryption data ,reboot into erecovery and use "download last firmware and recovery" and follow the steps"
Is this the only way to go back to stock/encryption?
A wipe data or factory reset on emui stock recovery wouldn't work?
I'm asking because i have decrypted a while ago.
The last time i tried to use erecovery it said "no packages available" with an exclamation mark.
I have flashed stock system, kernel, ramdisk and recovery to boot back several times, but this time i have decrypted the internal storage...
Just need confirmation and/or possible solution to this. @micky387
Thanks in advance

hello @micky387
noob question. is it possible to work on a mate 8 debrand(AL10C00) atm im running openkirin omnirom 5.2,
would like to try other gsi roms. to check the most compatible rom..
your reply is very much appriciated
thank you

P10 Lite / WAS-LX1
Works on P10 Lite (WAS-LX1) with a fitting TWRP (I used Darkjokers 3.3.1). Used the zip over ADB sideload, so no external SD needed. Thanks for showing us da wae pal :good:

Hey dudes will this work on mate 8 Oreo ? If soon could you mod it for it ? Thanks

c|nder said:
Hey dudes will this work on mate 8 Oreo ? If soon could you mod it for it ? Thanks
Click to expand...
Click to collapse
If you check by the dates, it was all discussed at the time of EMUI 8/Oreo.
Earlier with Nougat, there was no such problem (TWRP was able to access internal storage).
To the other side, with current EMUI 9.1, Vendor is read-only and proposed modifications will not work

[HELP OXYGEN OS] Can´t install 5.1.5 update or flash in original recovery!!

Hello, I have an OP 5 with unlocked bootloader and i was rooted. So, I'm in 4.5.13, and i'm trying to install 5.1.5 but i need to be unrooted for this.
Somehow when i removed root (magisk) my phone entered in bootloop mode (i think that magisk lost the original boot img). I flashed the stock boot img and the phone booted normally and without root. However i think that some "crumbs" of the magisk or adway stayed in my system or phone partitions and my phone continues to say that he can´t install the OTA. I've already wiped cache and data in the recovery and tried to install with adb sideload but it fails.
I still have my OOS and is working fine, but I can't update... Any ideas?
Do you think that if I do the normal settings > restore factory settings will it work? Or that option will be also damaged?
Should i boot TWRP in fastboot, and try to do a factory reset and then flash 5.1.5?
For your information, i've never flashed anything besides magisk and the attempts to update. The rom is the original as also the recovery. To flash the magisk i always booted twrp connected by usb to my PC.
I apreciate all the help!!

pdalvares said:
I apreciate all the help!!
Click to expand...
Click to collapse
https://downloads.oneplus.com/oneplus-5/oneplus_5_oxygenos_5.1.5/
This is the full OOS ROM Zip with instructions to flash with either stock Recovery, or TWRP.

Dirk said:
This is the full OOS ROM Zip with instructions to flash with either stock Recovery, or TWRP.
Click to expand...
Click to collapse
Yo, i already tried it different ways, but thank you :/

pdalvares said:
Yo, i already tried it different ways, but thank you :/
Click to expand...
Click to collapse
Fastboot flash TWRP, format partitions and flash full OOS ROM and Magisk. What's the difficulty?
https://www.xda-developers.com/how-to-install-twrp/

Dirk said:
Fastboot flash TWRP, format partitions and flash full OOS ROM and Magisk. What's the difficulty?
https://www.xda-developers.com/how-to-install-twrp/
Click to expand...
Click to collapse
Ok i'm gonna try it i'm sorry for my noobish but you know the smartphone was expensive and i'm afraid to brick it someway :/
Just one question: when you say formating partitions you mean wipe data, cache, system and dalvik / ART cache right?
thanks alot for your help and im sorry for being noob xD
I've my nexus 7 with root and PureNexus rom and had an moto g with custom rom, twrp and root but somehow I'm afraid with the OP5 because it was very expensive to my pocket xD :silly:

pdalvares said:
Ok i'm gonna try it i'm sorry for my noobish but you know the smartphone was expensive and i'm afraid to brick it someway :/
Just one question: when you say formating partitions you mean wipe data, cache, system and dalvik / ART cache right?
thanks alot for your help and im sorry for being noob xD
I've my nexus 7 with root and PureNexus rom and had an moto g with custom rom, twrp and root but somehow I'm afraid with the OP5 because it was very expensive to my pocket xD :silly:
Click to expand...
Click to collapse
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.

Dirk said:
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Click to expand...
Click to collapse
I've made what you said but it gives me the error "Updater process ended with error: 7"

pdalvares said:
I've made what you said but it gives me the error "Updater process ended with error: 7"
Click to expand...
Click to collapse
Which TWRP are you using? It should be the latest Official version, or you could try the latest codeworkx from here:
https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Error 7 is a generic error code. The useful information about the error is usually in the body of text.
If you can't get TWRP to play nicely you can use it to format partitions as mentioned before, and then use it to install the stock OOS recovery from the bottom of this page:
https://downloads.oneplus.com/oneplus-5/oneplus_5_oxygenos_5.1.5/
The stock recovery is an .img, so in the TWRP 'Install' menu you need to select Image instead of Zip at the bottom of the screen. Move the stock recovery .img to Internal Storage and flash it. Reboot into Stock Recovery and flash full OOS zip.

Dirk said:
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Click to expand...
Click to collapse
YO BRO i've made it. I installed other version of the OS and it's working! Now im gonna see if i can update it to the newest version
Thank you for encouraging me!

pdalvares said:
YO BRO i've made it. I installed other version of the OS and it's working! Now im gonna see if i can update it to the newest version
Thank you for encouraging me!
Click to expand...
Click to collapse
Let me know how you get on. :good:

Dirk said:
Let me know how you get on. :good:
Click to expand...
Click to collapse
It all works fine but when doing the OTA in the OOS to 5.1.4 the device reboots, enters in oxygenos recovery but it fails...
EDIT:
Could it be because the bootloader is unlocked?? Is it safe to lock it like i unlocked it? No problem?

pdalvares said:
It all works fine but when doing the OTA in the OOS to 5.1.4 the device reboots, enters in oxygenos recovery but it fails...
Click to expand...
Click to collapse
Work through the steps in post #8. Begin with the latest codeworkx TWRP and go from there.
Check this guide if you think you might be missing something:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877

Dirk said:
Work through the steps in post #8. Begin with the latest codeworkx TWRP and go from there.
Check this guide if you think you might be missing something:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Click to expand...
Click to collapse
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "

pdalvares said:
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
Click to expand...
Click to collapse
Are you trying to OTA or full ROM? OTA is not going to work. Only full ROM .zip will get the job done.
Have you considered giving up on OOS for now and just try flashing a Custom ROM from TWRP? I'd recommend Dirty Unicorns Oreo for now until Pie ROMs mature. You can get their ROM from their website.. Should be no issue at all flashing it. Opengapps ARM64, 8.1 Nano is the Gapps i'd recommend.
Wipe in TWRP, Flash Firmware/ROM/Gapps/Magisk. Job done.

pdalvares said:
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
Click to expand...
Click to collapse
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/

pdalvares said:
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
Click to expand...
Click to collapse
Initial boot can take some time.
I'm at a loss why your phone hates OOS, but it might love Custom ROMs. Give it some thought.

pdalvares said:
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
Click to expand...
Click to collapse
MY BROTHER, i really needed to lock the bootloader, wiped everything and adb sideloaded 5.1.1. It booted at android 8 and then i ran the OTA's until the newest one and now i have my phone fully functional, with the latest update, and running all stock. Thank's alot for all the help. I don´t know how to thank you! Peace and see you one day!
EDIT:
Maybe one day I will try some custom ROM, like lineage or other best than that. For now im gonna stay like this for a while, just because yes

pdalvares said:
MY BROTHER, i really needed to lock the bootloader, wiped everything and adb sideloaded 5.1.1. It booted at android 8 and then i ran the OTA's until the newest one and now i have my phone fully functional, with the latest update, and running all stock. Thank's alot for all the help. I don´t know how to thank you! Peace and see you one day!
EDIT:
Maybe one day I will try some custom ROM, like lineage or other best than that. For now im gonna stay like this for a while, just because yes
Click to expand...
Click to collapse
Good news! :good:
You can see how resilient OP phones are. You can pretty much always get them back to a working condition. I can only guess but it sounds like you were right. Something was wrong with your Bootloader after the initial problems. Glad you got it sorted.