[Recovery](KENZO)TWRP-COFFACE (3.0.0) No patched boot.img required to flash MIUI roms - Xiaomi Redmi Note 3 [Snapdragon] ROMs, Kernels, Re

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

Related

[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

[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.

Tutorial(downgrade8.1.0=>7.1.1)use nougat stok/custom-roms on Oreo BC-12 bootloader

Tutorial(downgrade8.1.0=>7.1.1)use nougat stok/custom-roms on Oreo BC-12 bootloader
This tutorial is for the users wich are not satisfied by Oreo 8.1.1 rom
Also can be used by users wich changed the touchscreen from some reazons
and on Oreo 8.1.1 this new touchscreen not work​
First got to Settings/System/Developer option and chec OEM-unlockin to be ENABLED!
for flashing twrp-recovery may be need to unlock the bootloader by code but it should work only with OEM-unlocking enabled
Downgrading with FASTBOOT!
1) Charge youre phone to at least 50-70%, better is 100%
2) Download the FILES necessary for downgrading
3) Reboot the phone in bootloader and connect to the pc
4) Opend the terminal and write "fastboot" or "mfastboot" depends by your instaled fastboot
5) Copy/Paste in terminal the lines writed in "fastboot-mfastboot.txt" atached to files
or write them one by one and press ENTER
WAIT 'till it finish
6) In bootloader screen, from buttons vol-up & vol-down navigate and set to "reboot recovery" and press Power
Phone should boot in TWRP-recovery!
Now you have to install a custom-rom or a stok-rom TWRP flashable with Install option
""for this use the instruction to install posted by the developer of each rom""
Also you can RESTORE an older 7.1.1 backup made before update to OREO
Reboot and enjoy by nougat-7.1.1 rom on oreo-8.1.0 bootloader
Downgrading with TWRP
Files to be flashed with TWRP for the users wich have olready the TWRP-recovery instaled!
1) Download the files
2) Copy the zip archive on the sdcard
3) Reboot the phone in TWRP-recovery
4) Search and install the zip
5) Install nougat 7.1.1 rom or restore an older backup made before update to OREO
Enjoy!
reserved
Thank You very much
---------- Post added at 06:02 PM ---------- Previous post was at 05:38 PM ----------
vaserbanix said:
This tutorial is for the users wich are not satisfied by Oreo 8.1.1 rom
Also can be used by users wich changed the touchscreen from some reazons
and on Oreo 8.1.1 this new touchscreen not work​
First got to Settings/System/Developer option and chec OEM-unlockin to be ENABLED!
for flashing twrp-recovery may be need to unlock the bootloader by code but it should work only with OEM-unlocking enabled
Downgrading with FASTBOOT!
1) Charge youre phone to at least 50-70%, better is 100%
2) Download the FILES necessary for downgrading
3) Reboot the phone in bootloader and connect to the pc
4) Opend the terminal and write "fastboot" or "mfastboot" depends by your instaled fastboot
5) Copy/Paste in terminal the lines writed in "fastboot-mfastboot.txt" atached to files
or write them one by one and press ENTER
WAIT 'till it finish
6) In bootloader screen, from buttons vol-up & vol-down navigate and set to "reboot recovery" and press Power
Phone should boot in TWRP-recovery!
Now you have to install a custom-rom or a stok-rom TWRP flashable with Install option
""for this use the instruction to install posted by the developer of each rom""
Also you can RESTORE an older 7.1.1 backup made before update to OREO
Reboot and enjoy by nougat-7.1.1 rom on oreo-8.1.0 bootloader
Downgrading with TWRP
Files to be flashed with TWRP for the users wich have olready the TWRP-recovery instaled!
1) Download the files
2) Copy the zip archive on the sdcard
3) Reboot the phone in TWRP-recovery
4) Search and install the zip
5) Install nougat 7.1.1 rom or restore an older backup made before update to OREO
Enjoy!
Click to expand...
Click to collapse
Also, can I flash Stock Nougat (using fastboot) after this? And is there any chance of my device being hardbricked?
ShattrdChain said:
Thank You very much
---------- Post added at 06:02 PM ---------- Previous post was at 05:38 PM ----------
Also, can I flash Stock Nougat (using fastboot) after this? And is there any chance of my device being hardbricked?
Click to expand...
Click to collapse
No! you cant flash a full nougat rom with fastboot.
Bootloader cant be downgraded!
for hardbricked phones you have first to boot it using the sdcard img.
then when you get bootloader working without sdcard, can use this tutorial
Sent from my Moto G (5S) using Tapatalk
vaserbanix said:
No! you cant flash a full nougat rom with fastboot.
Bootloader cant be downgraded!
for hardbricked phones you have first to boot it using the sdcard img.
then when you get bootloader working without sdcard, can use this tutorial
Sent from my Moto G (5S) using Tapatalk
Click to expand...
Click to collapse
Oh ok. Thank You very much
I successfully rolled back to 7.1 using this method. No errors or issues. Everything worked flawlessly. A big thank you @vaserbanix
What are the problems with 8.1? I'm still on Android 7 (RETEU)
Argon007 said:
What are the problems with 8.1? I'm still on Android 7 (RETEU)
Click to expand...
Click to collapse
1. Oreo Battery drains considerably faster than 7.1. (But charges faster too)
2. Fingerprint unlocks slower than 7.1
3. Lags slightly when doing intensive tasks.
Now we need a maintainer for (a) Nougat rom(s)..
Ænimal said:
Now we need a maintainer for (a) Nougat rom(s)..
Click to expand...
Click to collapse
YES indeed!
Im in 8.1.1 stock rom. Can i install a custom 7.1.2 (ViperOS) with this method? Tks.
mysticauls said:
Im in 8.1.1 stock rom. Can i install a custom 7.1.2 (ViperOS) with this method? Tks.
Click to expand...
Click to collapse
lineage 14.1 work so it should work ViperOS too!
to be sure ask in ViperOS thread.
Thankyou!
Hello!
Do you lose biometrics by installing twrp?
vaserbanix said:
YES indeed!
Click to expand...
Click to collapse
LOS14.1 has been updated:
NEW BUILD: https://www.androidfilehost.com/?fid...63190603848665
Change log: November 18 Security Update
NOTE: Like so many other users, I too updated my device with OREO and stuck with that. I haven't tried downgrading it because I don't want to end up with a hard-bricked device once again. Point here is the new build is not tested. So please take a TWRP backup before using this build. Don't forget to post me even if works fine.
Thanks,
KS
Click to expand...
Click to collapse
EDIT: When I try to quote properly I get logged out for some reason, so see this thread obviously (and don't forget to thank @kalyansundhar ):
https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-14-1-t3727918
Fantastic tutorial, vaserbanix. Thank you!
Does anybody know where can I get a nougat stock rom TWRP flashable? There is a thread with stock roms but all of them are only flashable via Fastboot...
I would like to get this in particular: [MONTANA_NPP26.102-49-14]
---------- Post added at 08:38 PM ---------- Previous post was at 08:13 PM ----------
ShattrdChain said:
I successfully rolled back to 7.1 using this method. No errors or issues. Everything worked flawlessly. A big thank you @vaserbanix
Click to expand...
Click to collapse
Thank you so much for your feedback, ShattrdChain! :good:
May I know what rom did you use for flashing with this method?
And do you know if bootloader needs to be unlocked in order to downgrade with this guide?
TWRP method doesn't work (bootloop), pls fix or delete.
FanderWasTaken said:
TWRP method doesn't work (bootloop), pls fix or delete.
Click to expand...
Click to collapse
i understand it work!
just chek the twrp version!
is posible the twrp to dont read some partitons.
this can make the differences betwen work or not
ask eric rutgers ( @GoldeneyeS2), he instaled sucesful that downgrade.zip
Thankyou!
vaserbanix said:
i understand it work!
just chek the twrp version!
is posible the twrp to dont read some partitons.
this can make the differences betwen work or not
ask eric rutgers ( @GoldeneyeS2), he instaled sucesful that downgrade.zip
Thankyou!
Click to expand...
Click to collapse
Its works great.
You can also use fastboot to downgrade!
can the downgrade be done without the bootloader unlocked?
the methods don't work for xt1799-2!

Xiaomi Mi 9 Brick!

I have a xiaomi mi 9 but it does not pass the logo of home, it stays there, I do not have the bootloader unlocked so I wanted to know another way to flash it
If flashing is no option for you, you might have to send it in for warranty.
Try XiaoMiTool v2
Same problem here; and this tool says fastboot unbrick is not supported yet ... So even though I can flash different twrp builds, it wont get out of reboot to fastboot and no recovery works
futiless said:
Same problem here; and this tool says fastboot unbrick is not supported yet ... So even though I can flash different twrp builds, it wont get out of reboot to fastboot and no recovery works
Click to expand...
Click to collapse
Did you've tried this lr team twrp:
http://files.mi-room.ru/files/twrp/cepheus/3.3.1-0601/recovery.img
And after flashing twrp, directly with volume up and power reboot in twrp?
Search for vbmeta.img file for mi 9 and flash it
What worked is cepheus_global_images_9.6.27_20190627.0000.00_9.0_global_d1aa19c208 ; then MANUAL usage of flash_all.bat ; then I was able to boot... I think (and don't take my word for it !!) what this is, is encryption lockout. Most XiaomiFlash offical tools were practically useless for the Mi 9 and only finding that exact build (which I figured out wasn't an upgrade like the others with no flash_all.bat, actually ran and it flashed stock and booted me to pincode decryption. After than I was able to use twrp-3.3.1-35-cepheus.img, and get TWRP ... granted it wiped everything. But I booting twrp-3.3.1-35-cepheus also asked for my decrypt key. I think the other TWRP's that don't ask for this while I am encrypted actually corrupted this data... (again maybe i'm wrong) but all in all ... I had a couple hours of slowly building up stress.. cause every recovery I flashed rebooted direct to fastboot. And i'm still not sure why..
Everyone needs to make sure that you can see your full file directory tree before utilizing TWRP commands as if the TWRP install doesn't detect decryption it doesn't discriminate and just overwright and corrupts files... THIS IS WHAT IT SEEMS AT LEAST ...
ALSO big word of warning Global users have to play it safe as it seems our variants is not the one the devs are releasing for ATM. and most things you attempt to flash will cause problems. (AGAIN just my 2 cents not to be taken as fact.) Just a warning... that is it...
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
emprazol said:
Search for vbmeta.img file for mi 9 and flash it
Click to expand...
Click to collapse
OK what is that file updating over ?
link to the rom you used to fix fastboot brick?? please
I have 9008, can you help me?

[RECOVERY] Unofficial TWRP 3.3.1-0 recovery for Xiaomi Redmi (olive)

There is now an official version available (xda post). Go use that.
Thanks for your work
---------- Post added at 10:43 PM ---------- Previous post was at 10:37 PM ----------
seprode said:
I compiled TWRP for my own Redmi 8 (olive) and thought I would share. Based on the devicetree for the Redmi 8a (olivelite) by milankragujevic.
I have the global variant with a Tianma display. I can't test if it works on any other variant, use with precaution.
I used it successfully to flash the xiaomi.eu rom and magisk.
You can find the device tree on my GitHub: here
And the image in the release section: here
Installation:
Unlock Bootloader if not already done (Official Tool)
Boot in to fastboot (Powerbutton + volume down)
Run fastboot flash recovery recovery.img (for Windows use Minimal ADB and Fastboot)
Boot in to recovery (Powerbutton + volume up)
If something breaks you can use MiFlash and the stock fastboot rom to go back to reset your phone (phone will also be locked again) or use fastboot to flash the stock recovery (can also be found in the stock fastboot rom).
You can download the fastboot rom here.
Click to expand...
Click to collapse
How can I know if my device Tianma display or not?
yamabokra1 said:
How can I know if my device Tianma display or not?
Click to expand...
Click to collapse
Go in to the phone app and dial *#*#6484#*#*. Under 1 and then LCD you can then find the manufacturer.
I don't know if it actually matters. I read here that it affects devices when using the Redmi 8a recovery. Since I forked the code and have a Tianma display I can't really look in to the problem.
Have you got MTP working while at TWRP? I can't seem to get it right, Windows don't see my phone (adb and fastboot are working). While using adb-sideload I've got error that my mi-globe.zip rom cannot be installed through that method
------ EDIT -----
So, I flashed fastboot stock ROM and recovery. Then flashed this recovery. Booted into stock ROM, copied my custom ROM, rebooted into recovery and still couldn't install - after half of the installation process TWRP shouted that it couldn't mount /system partition. How did you get it to work? And thanks for work!
pulka103 said:
Have you got MTP working while at TWRP? I can't seem to get it right, Windows don't see my phone (adb and fastboot are working). While using adb-sideload I've got error that my mi-globe.zip rom cannot be installed through that method
------ EDIT -----
So, I flashed fastboot stock ROM and recovery. Then flashed this recovery. Booted into stock ROM, copied my custom ROM, rebooted into recovery and still couldn't install - after half of the installation process TWRP shouted that it couldn't mount /system partition. How did you get it to work? And thanks for work!
Click to expand...
Click to collapse
Can you check your LCD is it Tianma display?
"Go in to the phone app and dial *#*#6484#*#*. Under 1 and then LCD you can then find the manufacturer."
pulka103 said:
Have you got MTP working while at TWRP?
Click to expand...
Click to collapse
I recompiled TWRP with MTP enabled and it seems to show up as a device but i can't access data from the device.
I installed the image via a sd-card, but usb-otg or adb push should also work.
pulka103 said:
TWRP shouted that it couldn't mount /system partition.
Click to expand...
Click to collapse
Okay I changed the default mounting point of the system partition. Try again with the new image.
yamabokra1 said:
Can you check your LCD is it Tianma display?
"Go in to the phone app and dial *#*#6484#*#*. Under 1 and then LCD you can then find the manufacturer."
Click to expand...
Click to collapse
I do have a Tianma display. Problem isn't with controls but with the TWRP itself in my case.
Just tried new image, same problem "Checking /system. /system is not mounted! Trying to mount /system RW. /system cannot be mounted. [...] Installation will be aborted."
I am using Mi-Globe right now, gonna try with "clean" Xiaomi.eu.
And still can't access storage through Windows Explorer (but device itself is seen, tested with adb).
So Xiaomi.eu installed kinda. No errors and stuff but won't boot up. After one try it just goes back into TWRP. Using V11.0.3.0 for HM8 (as described by Xiaomi.eu)
luckily, mine has TIANMA display, I'll try while my rm8 is unlocked, thanks bro
@seprode, Reading your post and seen your work, I decided and today I ordered a Redmi 8 (olive) for my self , too.
I am very thankful that there are people like you, pioneers, who open the path, for all of us to follow.
Thank you again for what you are doing for us.
I hope, soon enough, some developer will pay attention to our new phone and , maybe , we will be also able to see new Android (Q ?) roms for it.
I am active involving so far in Samsung NOTE 2(exynos) and Note 4 (snapdragon) and also Xiaomi Redmi 5 plus community
I will do my best and see, if any of these groups will be able , in the future, to do something for our little brother here.
But the path you have open, is the very important first step to it.
KUDOS
:good::good:
@pulka103 You want to try again? I made some changes and got MTP working.
seprode said:
I compiled TWRP for my own Redmi 8 (olive) and thought I would share. Based on the devicetree for the Redmi 8a (olivelite) by milankragujevic.
I have the global variant with a Tianma display. I can't test if it works on any other variant, use with precaution.
I used it successfully to flash the xiaomi.eu rom and magisk.
You can find the device tree on my GitHub: here
And the image in the release section: here
Installation:
Unlock Bootloader if not already done (Official Tool)
Boot in to fastboot (Powerbutton + volume down)
Run fastboot flash recovery recovery.img (for Windows use Minimal ADB and Fastboot)
Boot in to recovery (Powerbutton + volume up)
.
Click to expand...
Click to collapse
Thank for your work !
What about vbmeta as mentioned at milankragujevic ?
And do we need something against dm_verity ?
Edit:
I did the described "simple" way and it works !!!
No need to flash anything else !!!
Great job, Thanks again :good:
seprode said:
I compiled TWRP for my own Redmi 8 (olive) and thought I would share. Based on the devicetree for the Redmi 8a (olivelite) by milankragujevic.
I have the global variant with a Tianma display. I can't test if it works on any other variant, use with precaution.
I used it successfully to flash the xiaomi.eu rom and magisk.
You can find the device tree on my GitHub: here
And the image in the release section: here
Installation:
Unlock Bootloader if not already done (Official Tool)
Boot in to fastboot (Powerbutton + volume down)
Run fastboot flash recovery recovery.img (for Windows use Minimal ADB and Fastboot)
Boot in to recovery (Powerbutton + volume up)
If something breaks you can use MiFlash and the stock fastboot rom to go back to reset your phone (phone will also be locked again) or use fastboot to flash the stock recovery (can also be found in the stock fastboot rom).
You can download the fastboot rom here.
Click to expand...
Click to collapse
I have a problem and maybe some of you can help me. I flashed last recovery.img. After flashing phone reboot itself and boot to system. Next, perform reboot to recovery and it boot to mi-recovery, not twrp. Then I cant boot to system. I have to flash again and then it boot to system.
===EDIT====
Ok, I managed this. After "fastboot flash recovery recovery.img" you have to type "fastboot reboot"
Great Great work I hope you continue updating. Thank you ?
good afternoon, this twrp this worked on redmi 8 olive, if it worked I will for now, obg and thank you already.: D
Ok, so ive tried to install latest xiaomi.eu rom for the redmi olive after flashing twrp, following all the steps from here and other posts, and all I get was reboot everytime. how do i go back to stock? miflash is not working and i dont find any .img to flash back
seprode said:
@pulka103 You want to try again? I made some changes and got MTP working.
Click to expand...
Click to collapse
hey man i fixed up novatek touchscreens on a repack version of your twrp i will include here
Download also i did a PR on your github with the needed changes so your next version will have this fix
Thank for twrp i hope it works on my device but what about custom rom wee need to custom rom ..miui contains lots of ads so that we need some good custom room..and brother replay me as soon as possible.
[email protected] said:
Thank for twrp i hope it works on my device but what about custom rom wee need to custom rom ..miui contains lots of ads so that we need some good custom room..and brother replay me as soon as possible.
Click to expand...
Click to collapse
you should try miui eu
unlock Bootloader
how can i unlock Bootloader for Redmi 8 with out Official Tool

Categories

Resources