Database Develop

[tutorial][updating TWRP for 4.4 compatibility]

Ive noticed many people with older TWRP versions having problems with the updater script when installing 4.4 roms you need to be on the latest version of twrp (CWM may also need to be on a recent version). This tutorial will cover TWRP. Goo manager will not work for installing the latest TWRP recovery version on grouper. The following will give you the basics on how to use fastboot to flash a recovery.img (In this case twrp)
Things you will need:
A PC
Android SDK http://developer.android.com/sdk/index.html
TWRP recovery.img for grouper http://techerrata.com/browse/twrp2/grouper
A basic understanding of terminal/command prompt
You will need a PC and the android SDK (SDK http://developer.android.com/sdk/index.html) for fastboot to push the recovery file. TWRP can be found here (http://techerrata.com/browse/twrp2/grouper) you need the 2.6.3.0 version. Extract your android sdk and move your twrp image file (openrecovery-twrp-2.6.3.0-grouper.img) to the platform-tools folder in the sdk (This is where fastboot/adb are). For simplicity's sake rename your twrp file to recovery.img Enter command prompt or terminal depending on what OS you are using (windows/linux) and navigate to to your platform-tools folder in the SDK folder (where you should have moved your recovery.img) using the cd command. (plug device in) Once there check to see if you device is connected and seen with the adb devices command hopefully you will see a wonky alpha numeric code with "device" after it. If you dont you need to enter developer setting to enable adb. You do that by going into settings/about tablet and tapping build number 7 times. That should give you a developer options in settings check to make sure USB debugging is enabled. If all is well reboot your device into the boot loader with the adb reboot bootloader command once your device is at the bootloader check fastboot with fastboot devices you should see another wonky output with "fastboot" after it. The final command to push your new twrp image will be fastboot flash recovery recovery.img You should see some output saying how long it took to push the file it should not take that long. That should cover it! Now you should be good to go with the 4.4 rom's floating around.
There are many tutorials online explaining this process I just thought customizing it to the grouper would help those less comfortable with adb/fastboot. It's always a good idea to know how to use these tools you never know when you might need to use them. Anyone with question's feel free to ask.

Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app

blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That will work. But knowing your way around adb/fastboot can't hurt. There won't always be a GUI to do everything for you.

blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't know of flashify, awesome. Thx, really fast and easy method. Best thing is I didn't even need my pc for it

Thanks for the tutorial but surely this belongs in q&a, help etc not android development ;p
Sent from my Nexus 4 using XDA Premium 4 mobile app

Actually it's suited to the General section (guides and all). I appreciate you advising the fastboot method (I use it too), but it can b a pain for people who don't have their devices configured (configuring it can be a pain sometimes too). Flashify, as one member said, is a great alternative. BUT you *may* brick your device if you flash something to the wrong block device (possibility of that happening to an expert user: 0.0001%; possibility of that happening to a new user: 1%). Just my two cents.

I agree guys this should be in general. I've never posted anything but a build and didn't even think about it. Do I need to get a mod to move it? As for flashify sounds like a great tool. I've never had the pleasure of using it but if it works and people are comfortable with it more power to it. Personally fastboot is what I'm comfortable with it might seem a little in depth but really its quite simple especially if you use adb for logcats and are setup.

OP No worries, moved and thank you.

To flash 4.4 ROMs one could follow this tutorial, or one could simply flash this .zip of the latest version of CWM:
http://forum.xda-developers.com/showpost.php?p=46053223

So, i've bricked it already.
Hello experts and knowledgeable persons!
First, i'm a noob.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery, copied to PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated.
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
So now what do I do, as I don't want to make things worse. I am doing a factory reset before installing. The error i'm getting is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"

ziffius said:
Hello experts and knowledgeable persons!
First, i'm a noob.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery, copied to PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated.
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
So now what do I do, as I don't want to make things worse. I am doing a factory reset before installing. The error i'm getting is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"
Click to expand...
Click to collapse
I'm sure this is not what you want to hear but if all else fails push the factory.IMG you will be starting from square one. You can try pulling your backups off but might as well start over for 4.4

blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much for this recommendation. Really nice. Simple and took out all the nervousness of using the computer to push these files etc.
REally truly best for flashaholics.

question
Won't it work too if you just flash the zip from twrp itself? I'm running 2.6.3.2 and I read somewhere that i can simply install the new version (2.7.0.0.) zip from the recovery itself..Is it right??

Ergina95 said:
Won't it work too if you just flash the zip from twrp itself? I'm running 2.6.3.2 and I read somewhere that i can simply install the new version (2.7.0.0.) zip from the recovery itself..Is it right??
Click to expand...
Click to collapse
Did you ever try just flashing it and if so, did it work?

for some reason i cannot download the twrp ..it stuck at 99%
tried 2 version of twrp..hurm

Mookie2014 said:
Did you ever try just flashing it and if so, did it work?
Click to expand...
Click to collapse
yeap! did it! worked perfectly :good: just flash zip updates through the recovery

[Q&A] [RECOVERY][victara] TWRP 2.8.0.1 touch recovery [2014-10-20]

Q&A for [RECOVERY][victara] TWRP 2.8.0.1 touch recovery [2014-10-20]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][victara] TWRP 2.8.0.1 touch recovery [2014-10-20]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

dmbfan13 said:
Has anyone been able to install via TWRP Manager? every time i select "select device", it crashes. Anyone else?
Click to expand...
Click to collapse
I was unable to install via adb, so i tried using the app, it worked perfect.

Question
Hi, first at all: sorry my english, i'm a little rust; i have an Moto X 2014 (xt1097), with Android Lollipop (22.21.17.victara_retbr.retbr.en.BR amxcl), does this version of TWRP works 100%? O almost? i'm most interested to get Root and instal a recovery, my (sold) Moto x 2013, have TWRP and root. honestly, i want root to use Power Toogles, should i have to change the recovery? Or only with root can use it?

Twrp is good except time and date

Question
michyall said:
Twrp is good except time and date
Click to expand...
Click to collapse
Hi, sorry but what do you mean about time and date? It changes time and date on cellphone? Thanks

Yup. Every time i go into twrp date is wrong. Usually 6 days before and time wrong too.
When booting phone i get whatsapp time and date error: no trouble, when radio signal is up android is synchronizing and everything return right. Except twrp.
Have read about a bug

Cant make a backup TWRP
I get the error:
Backup complete. Failed.
unable to create backup folder errno=13
Using either twrp-2.8.6.0-victara or twrp-2.8.5.0-victara
Before trying to use 2.8.6 I could.
Thanks

Revert back to stock recovery on xt1092?
So I flashed TWRP on my xt1092 but I want to revert back to stock recovery. How to do it? My Moto X came with lollipop 5.0 with build no. LXE22.46-19

5.1 Support
Just upgraded to the 5.1 soak test (23.1.28) from a clean 22.46-11 installation and can no longer flash twrp (I tried 2.8.0.3, 2.8.0.5, 2.8.0.6, and crpalmer's unofficial build). They all complain about mismatched partition size, and if the flash is successful the recovery partition must be overwritten immediately by the stock recovery. I'm hoping someone comes up with a workaround or new build soon.

kevind23 said:
Just upgraded to the 5.1 soak test (23.1.28) from a clean 22.46-11 installation and can no longer flash twrp (I tried 2.8.0.3, 2.8.0.5, 2.8.0.6, and crpalmer's unofficial build). They all complain about mismatched partition size, and if the flash is successful the recovery partition must be overwritten immediately by the stock recovery. I'm hoping someone comes up with a workaround or new build soon.
Click to expand...
Click to collapse
Flash from within Android and it will stick.

korockinout13 said:
Flash from within Android and it will stick.
Click to expand...
Click to collapse
How can I do that? Thanks!
EDIT - I'm an idiot, I didn't boot into recovery straight away after flashing the image, so it was overwritten on boot up.

kevind23 said:
How can I do that? Thanks!
EDIT - I'm an idiot, I didn't boot into recovery straight away after flashing the image, so it was overwritten on boot up.
Click to expand...
Click to collapse
Sent from my XT1095 using XDA Free mobile app

Guys, fast question. I've flash stock firmware, flash twrp latest version, then cm and start setting up, deleted some apps wipe Cache and dalvik and when I tried to reboot into recovery to flash a kernel it just boot loops into recovery boot image.... Phone is working great, but can't get into recovery.... Any idea? Already tried flashing previous version and same result
Enviado desde mi XT1095 mediante Tapatalk

I installed this recovery 1 month ago, but now i am trying to boot into recovery but it stucks on TWRP screen, there are no menus like backup, install etc, it just stucks on twrp blue screen. Even i flashed older twrp 2.8.x.x by fastboot mode but same thing happens only twrp blue screen...?
Could someone help me?
P.S: it was working fine 1 month ago when i flashed RR.

I have the exact same issue on my Xt1060. It has flashed several Roms fine, but hangs up on the TWRP blue screen too! I also reflashed 2.8.7.1 with no difference. Any ideas?

I uninstalled twrp and rebooted the phone. I then reinstalled twrp using 2.8.6.0 version. I rebooted and tried opening the recovery. It now works fine. I have since installed the cyanpop nightly and updated happy. Phone works!!!! Not sure why but it does. I will stay with the older version. Thanks.

Guys, I'm having this problem, I'm on 3.0.0.0 and every time I wipe Cache and dalvik/art Cache (I'm on stock marshmallow only tip root and krait kernel) it doesn't wipe anything..... Any idea? Or what do I have to do?
Enviado desde mi XT1097 mediante Tapatalk

On version 3.0.2-2 I get a corrupt zip file error every time I try to flash. This has happened 5 times since encrypting the phone with two different ZIP files.
Is this due to TWRP not supporting Nougat encryption?
Is this resolved in 3.1.0?
Sent from my 2014818 using Tapatalk

No further update of CM13 via TWRP possible

Hey folks,
after hours of reading around I have almost no idea left how to update my CM13 (13.0-20151213_nightly-titan) currently installed to a newer version. I tried with TWRP 2.8.6.0 and even 2.8.7.0, but it's all the same: I choose the zip file to install, the filesystem is detected correctly - but the installation just won't continue (usually the detection is followed by "patching the system unconditionally"). TWRP doesn't freeze, but just nothing happens . When I brake up after some time (usually an installation is done very quickly) with pressing the power button, my phone boots in the old version normally.
I tried another TWRP, wiped cache and dalvik, fixed permissions, set root in phone options, tried several CM13 builds... But I'm afraid of wiping data and system as it's a lot of work to get everything right again afterwards :crying:. Do you have any idea why TWRP doesn't want to install the new build?
Thanks a lot!

First always take a nandroid backup before you make any changes.
Even thought TWRP 2.8.7.0 is released, For Moto G 2014(titan)
only 2.8.6.0 is official https://dl.twrp.me/titan/
Try doing a clean installation(Wipe the data & System). That should do the trick.
just for the record the recovery is stopping you from installing a new build

Seems to be an issue with TWRP. You could give a try using CWM PhilZ Touch recovery. I have flashed using this recovery numerous times without any problem.

Thank you two for your replies !
Maddy, I know that 2.8.7.0 is unofficial for titan, but nevertheless it's working (for others). I want to avoid a complete reset, but in the end this could be a solution. But as I reflashed twrp (and tried another version also) I'm really wondering why twrp could be the problem ...
pank, I will take a look on CWM PhilZ, but until now I was really happy with twrp (and of course with its backup function). I hope it's possible to flash CWM using twrp and vice versa .

Unfortunately CWM PhilZ Touch Recovery shows the same behaviour than twrp - installation of new zip file just doesn't work (without any error) . If someone has an idea (except of a full wipe) please give me input !

Update the bootloader to the latest version. Had a similar problem a few months back that resulted in lots of hair tearing This solved it.
http://forum.xda-developers.com/moto-g-2014/general/bootloader-update-t3060007

Great hint - just checked your link already this morning and everything seemed to make sense... But I figured out that bootloader 4883 (newest version) was installed at my phone . Downgrade to 4882 should not be possible, and I'm also afraid of that .
I think I have something to do around Christmas - full wipe and a clean install! Damn...

Try installing this app called "CyanDelta" from playstore. What it does is it downloads the necessary files to upgrade from cm latest build (not the hole file) it's could be around 30 mb only. Totally legit!!... And it would dirty flash after download....
Do let us know how it turns out ?

I already tried CyanDelta, great tool! But as it's just creating a script for TWRP it has the same behavior . Oh, and I discovered that the nightly I'm using is no more available on cyanogenmod's official website ^^.
By now I think I've spend more time on searching for a solution than a full wipe including everything would need :laugh: ...

For me TWRP gives this behaviour only when Downloaded zip has some problem in it.
when it's not downloaded correctly it stuck at patching System
Have you tried latest zip?
also check SHA1 after download, doing that will confirm zip is downloaded correctly

Yes, I've tried the newest zip (several days respectively the newest) and I've checked the SHA value every time . The zip verification of twrp itself also doesn't report an error.
Maybe the reason is that I've used CM 12.1 before and made a "dirty" flash. Full wipe is getting closer to me...

No_Future said:
Yes, I've tried the newest zip (several days respectively the newest) and I've checked the SHA value every time . The zip verification of twrp itself also doesn't report an error.
Maybe the reason is that I've used CM 12.1 before and made a "dirty" flash. Full wipe is getting closer to me...
Click to expand...
Click to collapse
Just to say that I am having the same problem. Does the problem exist with Cyanogen Recovery? Can I replace TWRP with Cyanogen Recovery without touching everything else?
Thanks in advance.

mwalma said:
Just to say that I am having the same problem. Does the problem exist with Cyanogen Recovery? Can I replace TWRP with Cyanogen Recovery without touching everything else?
Thanks in advance.
Click to expand...
Click to collapse
Yes, you can try Cyanogen Recovery
download it and from fastboot
you can either just boot once and try it or flash the recovery replacing TWRP
Code:
fastboot boot recovery.img
Code:
fastboot flash recovery recovery.img

Great, I didn't know that it's possible just to boot once with a special recovery image. I'll try cyanogenmod recovery today !

Great news: With use of Cyanogenmod Recovery I was able to flash the newest build :victory:! I'm looking forward to try one day with TWRP, but for now I'm totally up to date . Thank you all again and have some nice days !
Edit: A full wipe and clean install solved this problem completely . Now the flashing with TWRP works again.

Zuk Z2Pro Android 7 Version

Hi All,
Was finally able to get a hold of the Android 7 version for Zuk Z2pro, at this point it's in the development phase, looks pretty stable as of now, it's just been an hour since I installed it, Got it from the Chinese site ( Landlord ) a little tough to figure out the content on the site, but the ROM is in English.
I tried flashing it with the Stock Recovery but didn't work , went back to 2.3.044 and then flashed the TWRP ( Chinese Version ) Did a dirty flash, and all the sensors {Heart Rate, UV Sensor, Pedometer, Proximity, etc } seem to be working fine. The file is available in a Baidu link, and it takes a lot of time to download.
The ROM now supports themes but as of now i see only 4 inbuilt themes and no black themes. But inbuilt themes uses nice icons to make it look simple and neat. I shall post pics of the screens. Settings now show the lab features directly to play around with fake location( never got it working though ). As of now calls and Volte working fine. Haven't been successful in making video calls over LTE with Zui Roms.
Need some help in getting a cloud storage to upload the file.
If someone could help me, would be happy to upload it for the benefit of the community. Again ***** Please do install it at your own risk, make sure you backup in TWRP before you flash this ROM , the size is 1.6 GB. ***** All thanks to the Chinese forums BBS.lenovomobiles.

Screenshots
These are the screenshots
And you can download the file from :
https://drive.google.com/file/d/0B6GiX9_gwfCqVXVhRHcyVEdfbkU/view?usp=sharing
Make sure you backup in TWRP, Please use the Chinese version of the TWRP to flash this file,

More screenshots please ??

Some bugs ? Any way to go back to Android 6? After flashing this ROM TWRP still working?
Отправлено с моего Z2 Pro через Tapatalk

Bugs
raber111 said:
Some bugs ? Any way to go back to Android 6? After flashing this ROM TWRP still working?
Отправлено с моего Z2 Pro через Tapatalk
Click to expand...
Click to collapse
Following are the bugs I have noticed
1. Vibration stops working, a reboot will be needed
2. Manual mode in the Camera gives a red tint in faster shutter speeds
3. No Root, haven't been able to root it, maybe I am doing it wrong. Flashing the Superuser in TWRP makes the sim card go an undetected state.
4. No options to set a live wallpaper ( Google Pixel wallpaper with animation ). Figured out a way to fix it by using the app shortcut maker to set a shortcut for the live wallpaper picker.
5. Battery seems to be draining faster.
Will keep adding can't complain as it is a dev version.

anupsnair said:
Following are the bugs I have noticed
1. Vibration stops working, a reboot will be needed
2. Manual mode in the Camera gives a red tint in faster shutter speeds
3. No Root, haven't been able to root it, maybe I am doing it wrong. Flashing the Superuser in TWRP makes the sim card go an undetected state.
4. No options to set a live wallpaper ( Google Pixel wallpaper with animation ). Figured out a way to fix it by using the app shortcut maker to set a shortcut for the live wallpaper picker.
5. Battery seems to be draining faster.
Will keep adding can't complain as it is a dev version.
Click to expand...
Click to collapse
So TWRP still working after flashing?
Gapps working?
Отправлено с моего Z2 Pro через Tapatalk

I'm not able to flash it via chinese TWRP. I've also tried TWRP from Emmaus. If someone can share a working recovery with this ROM I'll tell you my opinion about it. (Error 7 is the problem).

raber111 said:
So TWRP still working after flashing?
Gapps working?
Отправлено с моего Z2 Pro через Tapatalk
Click to expand...
Click to collapse
TWRP works fine, just that I wasn't able to root it, Gapps not required, as I installed the Google sync app and the Google contacts previously on the 2.3.044 build since I did a dirty update, got the play store and the Google contacts in tact

cyBeRdUdE-9 said:
More screenshots please ??
Click to expand...
Click to collapse
Hi Cyberdude,
Is there any specific screen that u are looking for?

anupsnair said:
Hi Cyberdude,
Is there any specific screen that u are looking for?
Click to expand...
Click to collapse
Screens of any major UI changes ??

Hey I was on CM13 By Emmaus, did a TWRP backup.
Flashed the Chinese TWRP.
Wipe -> Flashed the Android 7 ZUI -> Used it for a day and wanted to go back to CM13.
I flashed the TWRP By Emmaus-> Restore-> Now the phone doesnt go past the ZUK logo with the blue LED light.
What do you think needs to be done to restore the TWRP backup and go back to CM13?
Edit: Solution: I had QFIL to 1.9 then flash Emmaus Recovery and restore.

Root Zuk Z2pro Android 7
Hi All,
For those who need to root this ROM, you can flash the following file from twrp it's a modified version of SU,

anupsnair said:
Hi All,
For those who need to root this ROM, you can flash the following file from twrp it's a modified version of SU,
Click to expand...
Click to collapse
I've flashed just the last version of SuperSu beta, no modify version needed in my option because is working like a charm!
Sent from my Z2 Pro using Tapatalk

lucaam said:
I've flashed just the last version of SuperSu beta, no modify version needed in my option because is working like a charm!
Sent from my Z2 Pro using Tapatalk
Click to expand...
Click to collapse
Thank you Lucaam, for the benefit of the forum can you please post a link, when I flashed SU, the sim in my phone stopped working.

Here's to you the link https://download.chainfire.eu/750/SuperSU/BETA-SuperSU-v2.64-20151220185127.zip?retrieve_file=1 of to the file that I've downloaded. I flashed it after the first full boot.
Sent from my Z2 Pro using Tapatalk

syedtahir16 said:
Hey I was on CM13 By Emmaus, did a TWRP backup.
Flashed the Chinese TWRP.
Wipe -> Flashed the Android 7 ZUI -> Used it for a day and wanted to go back to CM13.
I flashed the TWRP By Emmaus-> Restore-> Now the phone doesnt go past the ZUK logo with the blue LED light.
What do you think needs to be done to restore the TWRP backup and go back to CM13?
Edit: Solution: I had QFIL to 1.9 then flash Emmaus Recovery and restore.
Click to expand...
Click to collapse
hey dude, i had same problem, i couldn flash any rom through twrp, nor could i recover any backup.. then i saw your post, i could hardly flash 1.9 firmware, but even then, and even with locked or unlocked bootloader, i could neither update through official firmware update process (OTA) nor could i flash anything through any recovery, it stucks on updating/flashing system image unconditionaly.. so something strange happens when flashing 7.0, so you cannot go back anyway. May you could help. Its just so anoying that i cant restore my backups, cant install any custom rom, official rom, only qfil works but dont solves any problem.
thanks in advance
Ikram

ikram.senguen said:
hey dude, i had same problem, i couldn flash any rom through twrp, nor could i recover any backup.. then i saw your post, i could hardly flash 1.9 firmware, but even then, and even with locked or unlocked bootloader, i could neither update through official firmware update process (OTA) nor could i flash anything through any recovery, it stucks on updating/flashing system image unconditionaly.. so something strange happens when flashing 7.0, so you cannot go back anyway. May you could help. Its just so anoying that i cant restore my backups, cant install any custom rom, official rom, only qfil works but dont solves any problem.
thanks in advance
Ikram
Click to expand...
Click to collapse
I"m not certain about other backups. But I had a CM13 TWRP backup.
What I did was:
QFIL to 1.9. This should work irrespective of what recovery you have. This is like an absolute reset. Once this is done, let your phone reboot and load once.
Then adb reboot bootloader
In the bootloader mode -> Flash the recovery ( You will need to flash Emmaus recovery if you are going back to CM13).
Once flashed. You can wipe the data,system and cache. Install CM13 and you should be all set.
You could also wipe and restore any old CM13 Backup too. Hope this helps.

SOLVED
SOLVED: HOW? STRANGE!
i did everything exact same as at home, but somehow ..just somehow ..it didnt ****ed itself and didnt stuck on everywhere and indeed succeeded flashing every f****** rom!
so here a step-by-step (if some ever expirience same) thanks to you all which i can confirm:
1. flash 1.9.104 rom through qfil (let it boot..)
2. enable usb debuging through enabled developer settings
3. boot in fastboot (adb reboot bootloader) unlock bootloader with your unlock_bootloader.img (fastboot -i 0x2b4c flash unlock unlock_bootloader.img) right after that unlock it (fastboot -i 0x2b4c oem unlock-go) forreal
4. reboot, then enable usb debuging again and boot in fastboot again (adb reboot bootloader)
5. flash emmaus TWRP (fastboot flash recovery recovery.img) DO !NOT! USE ---> [fastboot -i 0x2b4c boot recovery.img] <--- CODE!
6. boot to TWRP, wipe data/cache/dalvik-cache (system not needed, better dont wipe system to be sure)
7. flash AICP, RR or CM13 .zip, NOT ANY OTHER (https://emmaus.pro/?dir=Zuk Z2 Pro & http://forum.xda-developers.com/zuk-z2-pro/development/rom-aicp-11-0-mm-6-0-1-unofficials-t3499283) those work for sure on emmaus TWRP
8. reboot, DONE
to every single zuk z2 pro user out there, please make sure your PC, USB PORT, USB-CABLE is working right, because even if everything seems right, under the hook its sometimes not. In my case, i knew it, but could not believe it since qfil showed me SUCCSESS in every section, the connection betweet cable and usb port was faulty, thats the only possibility. THANK YOU ALL VERY MUCH, this was one of the most HARD-BRIKS ive ever experienced, and ive been through S2, S3, S4, S5, S6, HTC ONE M7 hard-bricks.. so.. yeah!!! THANK YOU VERY MUCH :')

i try this zip on my twrp , but my phone are dead don't run anybody else
what i can do ?

Many thanks to you ! the flash worked very well. i had same issues here . best description ever many many thanks !!

Does anyone hava a guide to installing custom rom on MI 9 2020?

Hi,
I bought a new phone and thought I would get in to custom ROMs again. Mostly to get rid of bloatware. However, after following multiple guides I'm still no where closer to achieving my goals. The phone is a MI 9.
I found there's a lot of different steps depending on guide but most of the once I've tried does the following:
* Unlock bootloader, working
* Installing twrp via fastboot, working
* Deleting data in twrp, working
* Transfering a rom.zip file (depending on rom), working via usb cable
* Some guides recommends to install disable force Encryption via another zip file transferred from the computer, however, that seems to not be necessary, tried i few times
* Installing rom via twrp, seems to work
* In some guides you then need to remove cache, working
* Rebooting from twrp, working
After these steps I find myself in one of three different cases,
1. Phone is stuck in fastboot, have to reflash it with MIflash and global MIUI rom to get phone to work again
2. Phone in boot loop, logo shows up, phone waits for awhile, phone reboots, logo shows up
3. Phone boots up, logo is shown, phone reboots into twrp
I've also tried both XiaoMiTool and XiaoMiTool V2,
XiaoMiTool seems to write the global ROM to the phone whatever I choose (Have tried Xiaomi.eu and LineageOS 17)
XiaoMiTool V2, fails in second to last step, it wants to remove some cache before the installation in twrp is done.
Things I've not tried:
* Moving file to twrp with adb instead, should not make a difference
* Installing magisk
Now, I'm a bit afraid my phone will get hard bricked, have reinstalled the OS 20 times the last day to test different approaches and steps. Nothing seem to work. Does anyone have a proven method working in 2020?
Another way to go might be to just get rid of the commercials, run a different launcher to get app list and get rid of the bloatware. This is not really what I want but I can live with it.
As you can hear I'm about to just throw in the towel and give up. But I've heard a lot good about the xda forums so I thought it might be worth a try even though I do understand if no one has time or energy to help out a newbie.
Help please!
Edit: I do realize I've accidentally put this under Guides and not Q&A. I find no way of moving it nor deleting the thread so I guess some moderator will have to come help. Sorry for this.

Do you use latest TWRP for Mi9? TWRP from Mauronofrio works fine for me.
When you say "Deleting data in twrp", does this mean you did Format Data (confirm by typing "yes")? Or just wipe?
Poslano z mojega MI 9 z uporabo Tapatalk

mxxt01 is right. You have to format the data partition or else you will run into a bootloop.
I followed the guide here but I did not flash magisk since I don't need root.
Basically what I did was;
1. Unlock bootloader
2. Reboot to load the OS but skip the initial setup
3. Reboot to fastboot/bootloader
4. Flash TWRP (use the latest beta from Mauronofrio)
5. Immediatly press Vol Up + Power button to boot TWRP
6. Sideload the firmware to /tmp/
7. Format the data partition and type yes to continue
8. Factory reset
9. Flash firmware from within TWRP
10. Factory reset again (you can skip this if you don't want to)
11. Reboot
And that is how I did it.

mxxt01 said:
Do you use latest TWRP for Mi9? TWRP from Mauronofrio works fine for me.
When you say "Deleting data in twrp", does this mean you did Format Data (confirm by typing "yes")? Or just wipe?
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
I have tried both Formatting data, this generally makes all folders have gibberish names and by going to advanced wipe, choosing data, some guides also wants you to delete Dalvik, Cache and System. I have tried both in the same go and one or the other. Does not seem to make a difference. But from the response below I get that it's formatting the data and typing yes that is the way to go(?)
TWRP version 3.3.1-0
sangbuana said:
mxxt01 is right. You have to format the data partition or else you will run into a bootloop.
I followed the guide here but I did not flash magisk since I don't need root.
Basically what I did was;
1. Unlock bootloader
2. Reboot to load the OS but skip the initial setup
3. Reboot to fastboot/bootloader
4. Flash TWRP (use the latest beta from Mauronofrio)
5. Immediatly press Vol Up + Power button to boot TWRP
6. Sideload the firmware to /tmp/
7. Format the data partition and type yes to continue
8. Factory reset
9. Flash firmware from within TWRP
10. Factory reset again (you can skip this if you don't want to)
11. Reboot
And that is how I did it.
Click to expand...
Click to collapse
Could you describe step 6 in more detail please?
This is what I get if I try sideloading my phone:
adb push xiaomi.eu_multi_MI9_V11.0.5.0.QFACNXM_v11-10.zip /tmp/
adb server is out of date. killing...
* daemon started successfully *
I guess it's important to not get the firmware in the SD-card folder since that will be wiped if I format the data, this might be where I fail.

Step 6 is to type adb push rom.zip /tmp/
I renamed the zip file to rom.zip so that I don't typo when typing.
Sent from my MI 9 using Tapatalk

In any case you should flash a current (11.0.6.0 or younger) fastboot ROM (.tgz extention). Recovery ROMs (.zip extention) don't reset the phone as deep as fastboot ROMs do.
After that you'd best flash vbmeta.img before TWRP, see #1 for more details.
Cheers
Toscha

From personal experience of using xiaomi.eu's ROM, I never did install vbmeta.img or dmverity, since that particular rom is based on the official beta Chinese MIUI ROMs, and the latest TWRP from Mauronofrio supports decryption. Not sure about other ROMs though.
Just to be safe, just download the stock fastboot ROM as a backup just in case anything goes wrong. Always remember to NOT lock your bootloader when flashing back to stock, in case your persist partition gets corrupted, you can flash it to recover.

ZevSwe said:
I have tried both Formatting data, this generally makes all folders have gibberish names and by going to advanced wipe, choosing data, some guides also wants you to delete Dalvik, Cache and System. I have tried both in the same go and one or the other. Does not seem to make a difference. But from the response below I get that it's formatting the data and typing yes that is the way to go(?)
TWRP version 3.3.1-0
Could you describe step 6 in more detail please?
This is what I get if I try sideloading my phone:
adb push xiaomi.eu_multi_MI9_V11.0.5.0.QFACNXM_v11-10.zip /tmp/
adb server is out of date. killing...
* daemon started successfully *
I guess it's important to not get the firmware in the SD-card folder since that will be wiped if I format the data, this might be where I fail.
Click to expand...
Click to collapse
Like written by toscha42 you should flash the latest fastboot stock rom (tgz) for your phone first, as after all the attempts you have made your phone is probably kind of ****ed up... Do not lock bootloader.
What I do and it works for me, starting from stock ROM.
1. Unlock bootloader (you already done that)
2. Flash in fastboot latest TWRP for your device (I use Mauronofrio)
3. After flashing disconnect the phone and push VOLUME UP + POWER to enter from fastboot directly to TWRP recovery
4. Format data with yes
5. Reboot to recovery
6. Flash xiaomi.eu custom rom for your device with USB OTG (usb otg is the easiest way I guess as you don't need to move the rom to internal storage)
7. Reboot to recovery
8. Wipe cache and dalvik cache
8. Reboot to system
And that's all.
Poslano z mojega MI 9 z uporabo Tapatalk

toscha42 said:
In any case you should flash a current (11.0.6.0 or younger) fastboot ROM (.tgz extention). Recovery ROMs (.zip extention) don't reset the phone as deep as fastboot ROMs do.
After that you'd best flash vbmeta.img before TWRP, see #1 for more details.
Cheers
Toscha
Click to expand...
Click to collapse
Can't seem to find any fastboot ROMS, neither of xiaomi.eu or LineageOs 17. Where can I find this? https://xiaomi.eu/community/threads/20-1-16.54300/
If I understood correctly vbmeta.img unlockes secure boot. Not sure why that is needed or what problems it might create. Did some googling but found nothing. What is this used for? If it's important, why is it not in any guides I found?

ZevSwe said:
Can't seem to find any fastboot ROMS, neither of xiaomi.eu or LineageOs 17. Where can I find this? https://xiaomi.eu/community/threads/20-1-16.54300/
If I understood correctly vbmeta.img unlockes secure boot. Not sure why that is needed or what problems it might create. Did some googling but found nothing. What is this used for? If it's important, why is it not in any guides I found?
Click to expand...
Click to collapse
Fastboot STOCK Xiaomi ROM.
To be flashed with MiFlash. Do not lock bootloader.
http://c.mi.com/oc/miuidownload/detail?device=1700361
Poslano z mojega MI 9 z uporabo Tapatalk

Fastoot ROMs are only available for official MIUI ROMs and has tgz as their filename extensions. They are flashable only using Mi Flash tools or equivalent. Custom ROMs has zip and they are flashable using recovery.
Correct me if I'm wrong, vbmeta.img is for verified boot. I was running on official MIUI ROM and I wanted to have TWRP recovery, but stock recovery would come back after every reboot. So I flashed a modified version of vbmeta.img available on the web, to disable verified boot, and TWRP would persist in the recovery partition. Have a read on Verified Boot here.

mxxt01 said:
Fastboot STOCK Xiaomi ROM.
To be flashed with MiFlash. Do not lock bootloader.
http://c.mi.com/oc/miuidownload/detail?device=1700361
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
Hmm okay, but the phone is already working with the stock ROM, my whole idea is to switch to something else. What do you mean with do not lock bootloader?
sangbuana said:
Fastoot ROMs are only available for official MIUI ROMs and has tgz as their filename extensions. They are flashable only using Mi Flash tools or equivalent. Custom ROMs has zip and they are flashable using recovery.
Correct me if I'm wrong, vbmeta.img is for verified boot. I was running on official MIUI ROM and I wanted to have TWRP recovery, but stock recovery would come back after every reboot. So I flashed a modified version of vbmeta.img available on the web, to disable verified boot, and TWRP would persist in the recovery partition. Have a read on Verified Boot here.
Click to expand...
Click to collapse
Right, well I wish to switch to another ROM so installing MIUI Global ROm will not help.
I'm able to install TWRP without touching verfiedboot at all and get it to work even after reboot so that is not a problem. If that is what verifiedboot does I believe I can skip that?

ZevSwe said:
Hmm okay, but the phone is already working with the stock ROM, my whole idea is to switch to something else. What do you mean with do not lock bootloader?
Click to expand...
Click to collapse
than try once again by following my steps in post #8

You can skip flashing vbmeta and just follow mxxt01's steps.
Sent from my MI 9 using Tapatalk

sangbuana said:
You can skip flashing vbmeta and just follow mxxt01's steps.
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
That seems to have made the trick! Thanks so much!

I've been following this thread because I was having the same problems as ZevSwe, multiple attempts at installing roms with no success. I've been using phones/tablets with custom roms for years so I have some experience but not with this device.
I'll be trying the steps in post #8 later today but I have a question about twrp that's buggin me. I have been taking full twrp backups to a usb stick before installing and just reinstalling when the custom rom didn't work but the last few times the reinstall failed at about 98% complete and I've had to reinstall stock from scratch.
Any idea why a twrp backup would fail on reinstall? Is there something I could have inadvertantly done to cause this issue? Playing with roms is fun and easy when you've got a twrp backup to fall back on but a pain in the $#^ when it doesn't restore. Any thoughts would be appreciated before I give it another go.

thecdn said:
I've been following this thread because I was having the same problems as ZevSwe, multiple attempts at installing roms with no success. I've been using phones/tablets with custom roms for years so I have some experience but not with this device.
I'll be trying the steps in post #8 later today but I have a question about twrp that's buggin me. I have been taking full twrp backups to a usb stick before installing and just reinstalling when the custom rom didn't work but the last few times the reinstall failed at about 98% complete and I've had to reinstall stock from scratch.
Any idea why a twrp backup would fail on reinstall? Is there something I could have inadvertantly done to cause this issue? Playing with roms is fun and easy when you've got a twrp backup to fall back on but a pain in the $#^ when it doesn't restore. Any thoughts would be appreciated before I give it another go.
Click to expand...
Click to collapse
Since you noted that you have been doing a backup to a USB stick, it could be the USB stick is failing.

Honestly, all the installation guides for custom Roms i came across on XDA in the recent years are complete garbage. It fills like copy pasted from a guide that has been copypasted from a copypasted thread which has been copypasted and never worked.
For me, this guide works just fine. I just had to find the files for my Mi 9 instead of the k20 Pro. I would upload them for you but my upload speed is garbage.
https://www.youtube.com/watch?v=w_u_w6SrTDY&t=249s

I have flashed a lot of ROMs custom and official, fastboot and recovery. Never had any problems, the steps is here in thread.
Just remember 2 thing:
1. If you have ROM which using encryption, you must format data, because wipe will not remove encryption and you will see gibberish names
2. If you wipe system (which is mean less, because every ROM flash will do that, when you flash it, but many people insist in wiping it) then you must flash a ROM without reboot or you will stuck in fastboot and only option to repair is to flash official fastboot ROM (Non official fastboot ROMs, don't exist).