Database Develop

[Recovery](KENZO)TWRP-COFFACE (3.0.0) No patched boot.img required to flash MIUI roms

Hi All,
You guys must be thinking why i'm sharing this recovery when we already have Official TWRP Recovery
actually this Recovery is Lil bit modified (One of my friend Found it somewhere)
via this Recovery you guys will able to Flash any MIUI Rom without Modifying/Patching Boot.img (I tested it my self)(i flashed miui global stable 7.2.3 and global dev 6.4.28)no patched boot.img required
Note:- I'm Not responsible for any kind Of damage caused to your device
Orignal Link => https://drive.google.com/file/d/0B6zD6Bewl4FmQVJGVVBOdzRmT2M/view
Password to the zip :- www.cofface.com
Instructions to flash
download the zip file (link provided)
extract The TWRP recovery.img (password given)
and flash it via flashify or Fastboot
Fastboot Command "Fastboot flash recovery "image-name.img"
yoo done
BUG:- Its not a major bug its not even a bug(i'm just considering it as a bug) but kinda annoying once you flash this recovery this recovery will change your device name from KENZO to CM_KENZO(this not gonna affect anything) but if you will try flash AOSP v4 or anyother AOSP build that verifies the Product name will give some errors
that "This build is for kenzo devices not for Cm_kenzo device"
Solution :- Open the zip in winrar and edit the updater script just change the Kenzo word with CM_Kenzo and it will work (alot of work to do right)
Another solution (this one is better i guess)
when ever you wanna flash MIUi official firmware flash this reocvery via Flashify.
flash the miui rom...
boot it up again flash the official TWRP recovery(so that you will able to flash other roms)
WARNING:- Dont flash miui rom via official TWRP recovery it will not boot untill you flash the Modify boot.img
Update
Bug fixed ===> "This build is for kenzo devices not for Cm_kenzo device"==>No Error now
Link(bug fixed) => https://drive.google.com/open?id=0B5bSNUUrjm6JQjFhUEkzZXZ2bkk
Credits
Developer :- Cofface
Source :- http://www.miui.com/thread-3941604-1-1.html (orignal thread)
Special Thanks to @Rajdip for solving the bug
pls hit thanks if you guys found it helpful

what about the emmc_appsboot file ? should be remove from official rom ?

What is the zip password?? Can you share some screen shot

Anands3 said:
What is the zip password?? Can you share some screen shot
Click to expand...
Click to collapse
read my post zip password is already provided

wawan20 said:
what about the emmc_appsboot file ? should be remove from official rom ?
Click to expand...
Click to collapse
if your device is unlocked officially then No need to remove EMMC_appsboot file
but if your device is unlocked unofficially then yeah you have to dlt that file otherwise it will relock

Please add credits and source links

Rajdip said:
Please add credits and source links
Click to expand...
Click to collapse
I should have added the credit and sources link
But the thing is Idk who developed this recovery.
one of my friend provided me the link and he just found it randomly
i have only this info

Ashish0077 said:
I should have added the credit and sources link
But the thing is Idk who developed this recovery.
one of my friend provided me the link and he just found it randomly
i have only this info
Click to expand...
Click to collapse
Here's the source http://www.miui.com/thread-3941604-1-1.html
and those who are wondering, It works I tested.
---------- Post added at 05:07 PM ---------- Previous post was at 04:43 PM ----------
Okay I edited cafface TWRP, no more "This build is for kenzo devices not for Cm_kenzo device" error here it is https://drive.google.com/open?id=0B5bSNUUrjm6JQjFhUEkzZXZ2bkk

Rajdip said:
Here's the source http://www.miui.com/thread-3941604-1-1.html
and those who are wondering, It works I tested.
---------- Post added at 05:07 PM ---------- Previous post was at 04:43 PM ----------
Okay I edited cafface TWRP, no more "This build is for kenzo devices not for Cm_kenzo device" error here it is https://drive.google.com/open?id=0B5bSNUUrjm6JQjFhUEkzZXZ2bkk
Click to expand...
Click to collapse
Thanx Alot Bro.....and dude its "COFFACE" not "Cafface" and did you tested your build?? if yes i will add your link in the post and will give you credits
Credits Gives

Ashish0077 said:
Thanx Alot Bro.....and dude its "COFFACE" not "Cafface" and did you tested your build?? if yes i will add your link in the post and will give you credits
Credits Gives
Click to expand...
Click to collapse
Yeah I tested my build.. thanks

will this fix the unofficial bootloader unlock hard brick scenario? since now the phone should boot even if the bootloader gets relocked

Nice work, i will test it. Thx.
Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka

Seems to work, but TWRP is in Chinese?
I used Cofface's abd + fastboot files and replaced cofface_recovery_twrp_kenzo.img with the fixed TWRP.img provided by Rajdip. I get some prompt from what I can tell, but since everything is in Chinese I don't know what to click. I'll try to find a solution and post it here.
Update (Solved):
I still don't know what the first screen message was about, but you can get into the normal TWRP menu by swiping the slider to the right. After that click the second from the bottom button on the right to get into settings. Press the globe-symbol on the upper tab bar. From there you can choose the language you want TWRP to be in.
Update #2:
Works like a charm for me. Just installed SuperSU as well. I'm on Redmi Note 3 SnapDragon with Global Developer ROM 6.4.14 (MIUI7), officially unlocked bootloader. Thank you very much for posting OP!

Immortal68 said:
Seems to work, but TWRP is in Chinese?
I used Cofface's abd + fastboot files and replaced cofface_recovery_twrp_kenzo.img with the fixed TWRP.img provided by Rajdip. I get some prompt from what I can tell, but since everything is in Chinese I don't know what to click. I'll try to find a solution and post it here.
Update (Solved):
I still don't know what the first screen message was about, but you can get into the normal TWRP menu by swiping the slider to the right. After that click the second from the bottom button on the right to get into settings. Press the globe-symbol on the upper tab bar. From there you can choose the language you want TWRP to be in.
Update #2:
Works like a charm for me. Just installed SuperSU as well. I'm on Redmi Note 3 SnapDragon with Global Developer ROM 6.4.14 (MIUI7), officially unlocked bootloader. Thank you very much for posting OP!
Click to expand...
Click to collapse
The first prompt that appears is whether you would like to make TWRP modify system files or keep it read only. In simple words, if you swiping to the right Mi recovery wont replace TWRP when MIUI roms are flashed. If anyone didnt swipe right on the first prompt, just goto mount and unselect the read-only option.

Rajdip said:
The first prompt that appears is whether you would like to make TWRP modify system files or keep it read only. In simple words, if you swiping to the right Mi recovery wont replace TWRP when MIUI roms are flashed. If anyone didnt swipe right on the first prompt, just goto mount and unselect the read-only option.
Click to expand...
Click to collapse
Nice to know. TWRP asked the same thing (again apparently) when I rebooted from menu to system. It also provided the option to install SuperSU (or rather install the SuperSU Installer - whatever that was worth). I'm confirmed rooted now and recovery is still TWRP after many reboots. :good:

But is 3.0.0.0
I don't understand that

meangreenie said:
will this fix the unofficial bootloader unlock hard brick scenario? since now the phone should boot even if the bootloader gets relocked
Click to expand...
Click to collapse
No it will not fix that.... actually the thing Is When we unlock Bootloader with Official method it will not get relock while flashing any rom(via recovery)(miflash can still do that) in unofficial Method we replaces the emmc file with the modified one(and when we flash any official rom this file get replaced as this one is modified and (update. Zip/miuirom.zip) does not verify that emmc and relocks the boot loader....
What This recovery does is...
Miui roms inculde some recovery verification On The first boot
Which means it will replace twrp with the stock miui recovery which will cause bootloop...
For this we need to flash the patched/modified boot.img
But This recovery is Lil modified (it auto patches the boot.img and and our recovery does not get replaced and yoo thats how this recovery successfully flashes miui without a patched boot.img

Immortal68 said:
Seems to work, but TWRP is in Chinese?
I used Cofface's abd + fastboot files and replaced cofface_recovery_twrp_kenzo.img with the fixed TWRP.img provided by Rajdip. I get some prompt from what I can tell, but since everything is in Chinese I don't know what to click. I'll try to find a solution and post it here.
Update (Solved):
I still don't know what the first screen message was about, but you can get into the normal TWRP menu by swiping the slider to the right. After that click the second from the bottom button on the right to get into settings. Press the globe-symbol on the upper tab bar. From there you can choose the language you want TWRP to be in.
Update #2:
Works like a charm for me. Just installed SuperSU as well. I'm on Redmi Note 3 SnapDragon with Global Developer ROM 6.4.14 (MIUI7), officially unlocked bootloader. Thank you very much for posting OP!
Click to expand...
Click to collapse
Mine was in english Only on first Boot too?? But yeah i didnt use fastboot to flash was not in mood to turn on my pc.... I flashed it vai flashify and it the recoverg was in english by default and ymyou can flash it via twrp itself..
Anyways Thnx For Reporting This and giving solution

jujusito said:
But is 3.0.0.0
I don't understand that
Click to expand...
Click to collapse
Does that really matter?? Actually i dint face any problem with this recovery and atleast we can flash Miui roms without patching Boot?? And what you dont uderstand??
Its just an old version of twrp as iwas unablefound any updated one
As soon as i get it i will update here...

can I flash this recovery in current TWRP?
Sent from my kenzo using Tapatalk

Moto G probably bricked.?

OK guys hi... I somehow managed to wipe everything from the phone.I mean everything.The phone boots au to the screen with the ''unlocked bootloader'' warning.Then nothing.if i press power button and hold volume down i can use the recovery menu and i can go to the TWRP menu.From there i cannot use the MOUNT>USB OTG option so the phone is not recognized from my windows.
The only option i see available is installing something from my SD card.But i have no idea what or how or if there's a way i can install again the original android files.When i try booting it says there is no OS.
Is there a chance fellas.?

The fact you have somehow wiped your phone I dont think you can recover any lost files but you can at least still use the phone. Try flashing stock, if you are unable to do this put a custom rom on the sd card and try flashing that.

stonedpsycho said:
The fact you have somehow wiped your phone I dont think you can recover any lost files but you can at least still use the phone. Try flashing stock, if you are unable to do this put a custom rom on the sd card and try flashing that.
Click to expand...
Click to collapse
Yes i definitely cant recover anything i've wiped out.I will try anything you say i just don't know where i can find a custom rom or a stock one.Can you please give me a link.? i have the 2014 moto G XT1072.

Albilosha said:
Yes i definitely cant recover anything i've wiped out.I will try anything you say i just don't know where i can find a custom rom or a stock one.Can you please give me a link.? i have the 2014 moto G XT1072.
Click to expand...
Click to collapse
I would recommend trying to flash the stock image first. I am unsure of what country you are in, the link below is for the UK filmware:
http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-firmware-uk-gb-t3337916
This also has the steps needed to flash the stock image.
You can flash a custom rom though if you wish. I have only flashed Cyanogenmod13 so I can not recommend a different rom although CM13 is brilliant.
to download CM13- http://download.cyanogenmod.org/?device=thea
for Gapps (choose ARM/6.0/ then I choose the pico but you can choose what you want- http://opengapps.org/
Once you have put them on the sd card flash cm13 then gapps straight after then just reboot, done.

Take your Sd card out to an other phone or card reader then copy the ROM and flash it

stonedpsycho said:
I would recommend trying to flash the stock image first. I am unsure of what country you are in, the link below is for the UK filmware:
http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-firmware-uk-gb-t3337916
This also has the steps needed to flash the stock image.
You can flash a custom rom though if you wish. I have only flashed Cyanogenmod13 so I can not recommend a different rom although CM13 is brilliant.
to download CM13- http://download.cyanogenmod.org/?device=thea
for Gapps (choose ARM/6.0/ then I choose the pico but you can choose what you want- http://opengapps.org/
Once you have put them on the sd card flash cm13 then gapps straight after then just reboot, done.
Click to expand...
Click to collapse
Tried flashing both stock and CM and it failed.How can i check what version Moto G do i have since the UK firmware doesn't seem to work..
here are some pictures of the message i get while flashing
http://s33.postimg.org/h374o1x0v/DSC0760.jpg the stock one.
http://s33.postimg.org/lmx5esj1r/DSC0764.jpg CM.

Albilosha said:
Tried flashing both stock and CM and it failed.How can i check what version Moto G do i have since the UK firmware doesn't seem to work..
here are some pictures of the message i get while flashing
http://s33.postimg.org/h374o1x0v/DSC0760.jpg the stock one.
http://s33.postimg.org/lmx5esj1r/DSC0764.jpg CM.
Click to expand...
Click to collapse
The stock image is not for flashing in recovery, you need to flash it with "mfastboot" on a pc using command prompt.
It seems CM13 will not flash as I take it you were still on Lollipop?
I will PM you steps on how to use mfastboot.

stonedpsycho said:
The stock image is not for flashing in recovery, you need to flash it with "mfastboot" on a pc using command prompt.
It seems CM13 will not flash as I take it you were still on Lollipop?
I will PM you steps on how to use mfastboot.
Click to expand...
Click to collapse
ok thank you.the problem is that PC does not recognize the device.Even in Device manager the device appears as a MTP usb device.So i wonder how will i use fastboot damn i thing im doomed

Albilosha said:
ok thank you.the problem is that PC does not recognize the device.Even in Device manager the device appears as a MTP usb device.So i wonder how will i use fastboot damn i thing im doomed
Click to expand...
Click to collapse
Just sent you a PM

Albilosha said:
OK guys hi... I somehow managed to wipe everything from the phone.I mean everything.The phone boots au to the screen with the ''unlocked bootloader'' warning.Then nothing.if i press power button and hold volume down i can use the recovery menu and i can go to the TWRP menu.From there i cannot use the MOUNT>USB OTG option so the phone is not recognized from my windows.
The only option i see available is installing something from my SD card.But i have no idea what or how or if there's a way i can install again the original android files.When i try booting it says there is no OS.
Is there a chance fellas.?
Click to expand...
Click to collapse
If you can already enter TWRP then just download a Thea CyanogenMod firmware and Pico Gapps for Android 6.0. Then flash the CM ZIP and then the Gapps ZIP and then restart in normal mode.
---------- Post added at 06:47 PM ---------- Previous post was at 06:45 PM ----------
And one thing more. If you flashed TWRP for titan (XT106X) flash it for thea if your phone is XT107X. Then try to flash a XT107X Cyanogenmod firmware.

benjausen said:
If you can already enter TWRP then just download a Thea CyanogenMod firmware and Pico Gapps for Android 6.0. Then flash the CM ZIP and then the Gapps ZIP and then restart in normal mode.
---------- Post added at 06:47 PM ---------- Previous post was at 06:45 PM ----------
And one thing more. If you flashed TWRP for titan (XT106X) flash it for thea if your phone is XT107X. Then try to flash a XT107X Cyanogenmod firmware.
Click to expand...
Click to collapse
With help i managed to restore the phone to default android and then flashed the latest twrp and cyanogenmod 13.Thank you all guys

[RECOVERY] [UNOFFICIAL] TWRP_3.0_m86_patched_st0rm77

** BRICK WARNING/Disclaimer/Requirements **
>> Only flash with unlocked bootloader <<
>> Scripts are released under GPlv2 license <<
>> Run at own risk <<
Hi,
I patched the TWRP 3.0 recovery from faust93 to include important partitions
that make switching between different versions of Android/Ubuntu very simple.
All partitions are properly added to the fstab, but out of fear that some of
you will brick your device i disabled most of them.
Next version will contain a backup of all unique partitions, but i will have
to test this thoroughly.
Steps to install:
1. Download the zip file from attachments below
2. Unpack the zip file
3. Check checksum with md5sum -c *.md5
4. Put phone into fastboot mode (boot device with [vol-] and [power] button)
5. Flash recovery with:
# fastboot flash recovery TWRP_3.0_m86_patched_st0rm77.img
# fastboot reboot
then boot the device with [vol+] and [power] button, to enter recovery
[Requested by @p82maarj]
Already on an older TWRP version ?
- Flash "update_TWRP_3.0_m86_patched_st0rm77.zip" from TWRP
or
- Unpack the zip and flash the recovery manually in TWRP by selecting "install image"
Enjoy
Warning:
** If you flash an official update.zip from Flyme, remove bootloader, ldfw & recovery from ZIP**
** Otherwise you'll find yourself with a locked bootloader **

Hi @st0rm77
Thanks for your contrubution!
It will be good if you create a flashable zip of your new recovery. It can be flashed directly from the stock recovery or from the other twrp recovery without entering in fastboot.
Furthermore to have a flashable zip is usefull to flash a new rom update. For updating the new rom version I enter in TWRP, flash rom zip, flash unlocked bootloader zip and flash TWRP zip.
I attach the other flashable TWRP zip you can based on (only replace recovery.img by your recovery.img).

Hi @p82maarj,
Thanks, as per your request, i added an update_TWRP_3.0_m86_patched_st0rm77.zip . This is directly flashable from an older TWRP.
I added some extra verification so people dont end up with a corrupt recovery.
Enjoy
(in order not to confuse people to much, can you remove your download)

Personally I like android as OS, I don't wish to try Ubuntu, in my case it's useful to update my "old" TWRP by Faust93 with this one ?

PYCON said:
Personally I like android as OS, I don't wish to try Ubuntu, in my case it's useful to update my "old" TWRP by Faust93 with this one ?
Click to expand...
Click to collapse
Yeah, you get some extra abilities:
- Backup of Boot Logo
- Backup of Device Tree
Now you can backup/restore in TWRP without manually flashing dtb (device tree) in order to switch between Flyme, AICP, ResurrectionRemix or Ubuntu.

Thanks for everything you've been releasing, great work!

st0rm77 said:
Hi @p82maarj,
Thanks, as per your request, i added an update_TWRP_3.0_m86_patched_st0rm77.zip . This is directly flashable from an older TWRP.
I added some extra verification so people dont end up with a corrupt recovery.
Enjoy
(in order not to confuse people to much, can you remove your download)
Click to expand...
Click to collapse
Done Thanks!

st0rm77 said:
** If you flash an official update.zip from Flyme, remove bootloader, ldfw & recovery from ZIP**
** Otherwise you'll find yourself with a locked bootloader **
Click to expand...
Click to collapse
Sorry for the stupid question but it's just to be sure. I should remove the file named "bootloader" or the one named "boot.img"? Or both of them?
Thank you very much!

Another little question... What's the difference from 2 ZIP files ? Older one and updated ZIP ?

PYCON said:
Another little question... What's the difference from 2 ZIP files ? Older one and updated ZIP ?
Click to expand...
Click to collapse
I know the answer to this one!
The first zip contains the img file that you can flash using fastboot.
The second (update) zip is the one you need if you already have (an older) TWRP and you wish to update to this version (use it from inside TWRP).

abePdIta said:
Sorry for the stupid question but it's just to be sure. I should remove the file named "bootloader" or the one named "boot.img"? Or both of them?
Thank you very much!
Click to expand...
Click to collapse
boot.img is your boot partition, you need this one :good: (NEEDED)
bootloader is the locked bootloader from meizu, avoid this one as the plague (AVOID)
Dont brick your device, check everything carefully :fingers-crossed:

st0rm77 said:
Dont brick your device, check everything carefully :fingers-crossed:
Click to expand...
Click to collapse
Thank you very much! I will be careful in the future, I promise!

i follow the a to I tutorial
then unlock bootloader
then this
now when i conect meizu to pc i try to pass custom rom to internal memory and the phone restart
what is the problem
---------- Post added at 10:35 PM ---------- Previous post was at 09:56 PM ----------
managed to download the rom in phone browser now i have RR and all it´s ok

I flash stock recovery ( use update 5.1.10.0g) but not success, híc híc, help me restore stock recovery, many thanks!!!!

st0rm77 said:
Now you can backup/restore in TWRP without manually flashing dtb (device tree) in order to switch between Flyme, AICP, ResurrectionRemix or Ubuntu.
Click to expand...
Click to collapse
Just to be sure I understood :
Going from Flyme to CM :
-Backup Flyme (system+data+dtd)
-Flash CM archive
Going back to Flyme
-(optional) Backup CM (system+data+dtd)
-Restore Flyme (system+data+dtd)
Is there is a quikier way ?

TWRP 3.1.0.0 is out... It's possible to port it for our PRO5 ?! :silly:

help
hi .i change meizu pro 5 from china to national (5.6.1.19 daily )and unlock it and flash recover TWRP 3.0 but not login it the recovery .
i want updated

PYCON said:
TWRP 3.1.0.0 is out... It's possible to port it for our PRO5 ?! :silly:
Click to expand...
Click to collapse
I too vote for a port!

3.1.1 was released

munky-head said:
3.1.1 was released
Click to expand...
Click to collapse
Not for PRO5

Stuck in Fastboot Mode / TWRP without OS

Hello people,
I have an OnePlus 3T, which does not start the OS. I can open Fastboot Mode or TWRP. I do not even know which OS is installed (I think stock rom, but do not know). When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted". When I boot into system, it stops at the black "Powered by android" Screen (very first screen).
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
So what Information do I have so far (with my amateur knowledge):
adb shell getprop ...
ro.build.version.release: 6.0.1
ro.build.version.sdk: 23
ro.build.display.id: omni_oneplus3-eng 6.0.1 MOB31K eng.jc.20170208.012427 test-keys
ro.modversion: OmniROM-6.0.1-20170208-oneplus3-HOMEMADE
ro.twrp.version: 3.0.4-1
When I start the bootloader:
Product_Name - msm8996
Variant - MTP UFS
Bootloader Version -
Baseband Version -
Serial Number - *****
Secure Boot - enabled
Device State - unlocked
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
I tried to flash the stock ROM => did not work (with this Error 7)
So my first question: Which OS do I have? Really Marshmallow 6.0.1?
Second: Do you need more infos?
Third and most important: How to repair this mess?
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Thank you very much for your help.

Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.

thes3usa said:
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
Click to expand...
Click to collapse
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous

elchico92 said:
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
Click to expand...
Click to collapse
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.

thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.

elchico92 said:
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
Click to expand...
Click to collapse
Nope, that's the complete stock Zip. Unless you want to install OOS, that's not the one to Sideload.
Download the FW only from here: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166
And then Sideload it, reboot back to recovery, and then Sideload the ROM.

elchico92 said:
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
Click to expand...
Click to collapse
What is in the TWRP folder, anything? The TWRP folder would normally only be created, if a backup was created. You can possibly just boot TWRP, select the RESTORE option, select the backup from the TWRP folder, and get the phone up and running again.
Another possibility, if you aren't that up on adb commands (sideload, etc.), since you can access the internal storage, just download a ROM or fill stock ROM zip onto your PC, then just drag/copy to internal storage. Then boot TWRP, select INSTALL, pick the file, and flash it.
What is the background of the device, how do you not know the OS version? Did you receive it this way, or fixing it for a friend or something?
---------- Post added at 09:19 AM ---------- Previous post was at 09:12 AM ----------
elchico92 said:
When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted".
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Click to expand...
Click to collapse
That isn't the dm-verity notification. The dm-verity notification screen is similar, but says "dm-verity is not started in enforcing mode".
What you described is the bootloader unlocked warning screen. The bootloader unlocked warning screen is expected and normal (in fact, unavoidable) if the bootloader is unlocked. And unlocked bootloader is required for TWRP, flashing custom ROMs, etc.
dm-verity warning screen is in fact normal, as well, if you have TWRP installed. That one can be disabled by a couple different methods. But it's only purpose is to notify a "average" user that the system has been modified. For XDA users that are intentionally modifying their phones (TWRP, root, etc.) the warning is pretty meaningless. Under certain conditions, dm-verity will prevent the phone from booting. But TWRP and root in themselves, will normally not do that.
Neither warning means you have the wrong kernel, necessarily. And unless you (or someone else) tried to flash a kernel, there really isn't any reason to believe that.
---------- Post added at 09:29 AM ---------- Previous post was at 09:19 AM ----------
elchico92 said:
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
Click to expand...
Click to collapse
Flashing stock recovery will (by definition) replace TWRP with stock recovery. You probably have recovery, just the stock one (not TWRP) which is fairly useless in your case (can't flash custom ROMs, root, etc.).
elchico92 said:
I tried to flash the stock ROM => did not work (with this Error 7)
Click to expand...
Click to collapse
Can't really troubleshoot this, unless you tell us what file exactly (file name) and where you got it from. "Stock ROM" is far too vague, and can literally mean a dozen or more different things.
Also, what version TWRP?
Using a TWRP version which does not support Oreo is one reason for Error 7. Or you may have tried a file intended for the 3, not the 3T. So these details need to be provided, before we can figure out what went wrong.
elchico92 said:
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
Click to expand...
Click to collapse
You kind of need to decide which of those you want. Otherwise, there are just too many options for us to give.
Yet another option (in addition to those given) would be to flash the full stock OOS zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Then before rebooting, flash Magisk to root, and you should be all set. The full zip will put you on a fully stock baseline (including firmware). Which, if you aren't sure if you want stock, beta or custom ROM, is not a bad place to be; you can see what the "stock" condition is, before messing with things like custom ROMs. But again, it's totally subjective and a matter of personal preference, and you really do need to decide for yourself what is best for you (as an individual) at this time.

thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
Why not just sideload stock ROM which includes the firmware? Make life easier

przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Yeah, that is a good option, among many. As I mentioned, there are just too many options since the original poster hasn't even decided stock or custom ROM.

przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Since OP hasn't mentioned whether he wants to use a stock or custom ROM. So I gave him the link for the latest FW, in case he wants to use a recently updated custom ROM without needing to download the whole Stock zip.

Done!
Thanks a lot. The phone is working again.
I have flashed with adb sideload the firmware and the ResurrectionRemix-Rom (Nougat) and then via TWRP the gapps.
So I hope, everthing will be fine now.
answers:
- TWRP-folder: yeah I created one because I thought, maybe to restore will fix anything
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
- background: it was the phone of a friend of mine => he never heard anything about ROMs etc
The thread can be closed.

elchico92 said:
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
Click to expand...
Click to collapse
I already offered to troubleshoot this error for your, but you never supplied the requested info. Don't assume it is the "right one" next time, but rather, give exact file names, version numbers, and let us verify. Mistakes happen, and it always is good to have another set of eyes look at the specifics.
---------- Post added at 09:58 AM ---------- Previous post was at 09:56 AM ----------
elchico92 said:
The thread can be closed.
Click to expand...
Click to collapse
Threads on xda don't get closed, just because you solved your current issue. Others may have a similar problem, and may want to ask questions, etc.

I'm stuck in Fastboot Mode & TWRP without OS
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's

slykereven said:
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
Click to expand...
Click to collapse
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs

Resolved
OK, that's a little crazy but it's working, i've got a one plus 3T A3003, but i had to install Stable9.0.3+Firmware+Modem_OnePlus3.zip and not the one for the 3T ..... then install the last lineage os 17, and everything seems to work for now !!!
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
BillGoss said:
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Hi, thank's for your help, i didn't see your answer before and i have resolved the issue with other method

[ROM] [STOCK] [08-Mar] TWRP flashable Stock ROM [v340]

Code:
[B]NOTE : [/B]PROCEED AT YOUR OWN RISK. Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from AOSP extended (22/06 build) on primary device. Also I will try to help out in case of issues.
If already on Stock Rom then visit THIS THREAD for OTA updates.
This thread is useful for those who want to return to stock ROM from custom ROM while keeping TWRP & unlocked bootloader.
How to ,
Backup all your important app data.
Do a TWRP backup of current ROM. (precautionary step)
Download modified full recovery stock rom - TWRP_Stock_v340.zip from this post.
Download decrypt.zip from HERE.
Reboot to TWRP.
Go to wipe and select swipe to Factory reset.
Flash the ROM file.
Flash decrypt.zip file.
Reboot & Enjoy.
Users coming from Android Pie reported microphone issues - in case you face it then flash DolbyPlus-Oreo_8.1.zip from THIS post via Magisk which might resolve the issue.
(optional) If you want to boost up by debloating then use this MOD.
(optional) If you want to boost up BATTERY then use this GUIDE.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
NOTE : ROM works independant of RAM i.e. applicable for 3/4/6 GB variants.
Recommended TWRP : https://androidfilehost.com/?fid=3700668719832241089 by @SagarMakhar.

To ROOT the ROM
Flash Magisk from TWRP and you will have root access

Well I am trying to flash this ROM coming from RR but somehow its taking half an hour to encrypt so is it necessary to encrypt can't we just skip it ???
also it did erased TWRP as when I am trying to get in TWRP using volume up + power button its get back to default bootloader that came with mobile .....
also do I have to flash again TWRP again after this to get back root via magisk......

piku2008 said:
Well I am trying to flash this ROM coming from RR but somehow its taking half an hour to encrypt so is it necessary to encrypt can't we just skip it ???
also it did erased TWRP as when I am trying to get in TWRP using volume up + power button its get back to default bootloader that came with mobile .....
also do I have to flash again TWRP again after this to get back root via magisk......
Click to expand...
Click to collapse
Did you performed factory reset and flashed ROM & decrypt.zip
The TWRP survives the flash and Magisk can be flashed to Root the ROM but after above two files are flashed.

Well I successfully flashed ROM after complete factory reset with internal memory tooo ......
But some how TWRP got replaced with factory default (the one with root checker) with bootloader unlocked screen

Thank you. Just updated to latest version from old stock rom. Please update new versions also whenever available

Aftab_khatri said:
Thank you. Just updated to latest version from old stock rom. Please update new versions also whenever available
Click to expand...
Click to collapse
Will do

Thank You bro.. Your Guide has tested successfully from AOSiP build to stock ROM 309.. [emoji16]
Sent from my [device_name] using XDA-Developers Legacy app

AOSP to Stock
Good day, Can I use this method to go back in Stock Rom? Currently using AEX but I can't use my mobile data here in the Philippines, your answer would be a great help, Thank you...
[Update]
Good day mate, just flashed this, and I'm back to stock with root, Thanks Mate for this...

jroviel18 said:
Good day, Can I use this method to go back in Stock Rom? Currently using AEX but I can't use my mobile data here in the Philippines, your answer would be a great help, Thank you...
[Update]
Good day mate, just flashed this, and I'm back to stock with root, Thanks Mate for this...
Click to expand...
Click to collapse
Great .. Sorry could not reply earlier but you got the resolution of the query.
For subseqeunt update with TWRP intact .. please follow this guide in future .. https://forum.xda-developers.com/as...to/rom-update-stock-firmware-keeping-t3808269

Update - WW-15.2016.1805.311
Updated Stock ROM file - TWRP_Stock_v311.zip now avaliable.
For those who are already on stock ROM,
The instructions to flash are in THIS POST.
For those who are on custom ROM,
The instruction to flash are in THIS POST

Do these zips format internal storage or not ??

aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
No

aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
I believe this is the exact same firmware as the official one. It is just modified to work with TWRP. Nothing more, nothing less.

aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
You will have to format data (i.e. factory reset) but the Internal Storage will be safe.

aaa
Work For Max Pro M1 ?
This rom XOOT not XOOTD
---------- Post added at 11:26 AM ---------- Previous post was at 11:07 AM ----------
.A.V.i.n.a.S.h. said:
Code:
[B]NOTE : [/B]Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from AOSP extended (22/06 build) on primary device. Also I will try to help out in case of issues. BUT still proceed at your own risk.
This thread is useful for those who want to return to stock ROM from custom ROM while keeping TWRP & unlocked bootloader.
How to ,
Backup all your important app data.
Do a TWRP backup of current ROM. (precautionary step)
Download modified full recovery stock rom - Stock_X00T_Patch_May_Version_311_TWRP.zip.
Download decrypt.zip from HERE.
Reboot to TWRP.
Go to wipe and select swipe to Factory reset.
Flash the ROM file.
Flash decrypt.zip file.
Reboot & Enjoy.
(optional) If you want to boost up by debloating then use this MOD.
This will update your firmware to WW-15.2016.1805.311 to have updates after this follow THIS THREAD.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
Click to expand...
Click to collapse
My Devices Zenfone Max Pro M1 X00TD
This your Rom Not WORKING X00T
Flash to TWRP error TWRP Has Restarting
sory bad english

arielrizuly said:
My Devices Zenfone Max Pro M1 X00TD
This your Rom Not WORKING X00T
Flash to TWRP error TWRP Has Restarting
sory bad english
Click to expand...
Click to collapse
This ROM should work on X00T and X00TD both. Can you please validated checksum again for the downloaded file.

.A.V.i.n.a.S.h. said:
This ROM should work on X00T and X00TD both. Can you please validated checksum again for the downloaded file.
Click to expand...
Click to collapse
I am on stock build 311 and Rom X00TD , i am unable to root or even unlock bootloader on my device.
Tried all methods , on YouTube and xda but all wasted.
Though , i debloated my phone using one of the methods mention in a thread in xda and even installed xda navbar using adb.
Please help.

Abby 244 said:
I am on stock build 311 and Rom X00TD , i am unable to root or even unlock bootloader on my device.
Tried all methods , on YouTube and xda but all wasted.
Though , i debloated my phone using one of the methods mention in a thread in xda and even installed xda navbar using adb.
Please help.
Click to expand...
Click to collapse
Have you checked the drivers if they are installed.
Do one thing .. see if in fastboot .. if you get any responce for fastboot devices command from pc.

.A.V.i.n.a.S.h. said:
Have you checked the drivers if they are installed.
Do one thing .. see if in fastboot .. if you get any responce for fastboot devices command from pc.
Click to expand...
Click to collapse
No response even in fastboot.