Database Develop

I accidentaly deleted the ROM on my Zuk Z2 pro

Hello there !
I'm not sure to be in the right section for looking for help, redirect me if needed.
I was trying to flash my device with TWRP recovery to get Mokee on my phone. I had a lot of trouble but finally everything was ok and I just had to press "flash". But after that, the process remained stuck at the "Patching system image unconditionally..." step. I did serval whipe, backup and install, with serval ROM (CyanogenMod and ResurrectionRemix as well) but I couldn't go farther. But once, I lost my backup and I had no ROM installed, and no way to install a custom one.
At this point, the phone can't boot, can't access flashboot mod or recovery mod. The display remain black and there is nothing I can do, like if it was dead. It is just detected by QFIL and MiFlash (port COM3).
The only thing I could do is try to install the ROM stock with QFIL. But QFIL won't work, it is stuck at "13: H\abc\prog_ufs_firehose_8996_ddr.elf" step for some times, then returns "Download fail:SaharaFail:QSaharaServer Failrocess Fail". So I was looking for an other way and I heard of a flash method through Miflash (as a new member, I can't post any link here). I followed the guide, step by step, but wether the flash ends correctly with no error and the phone still doesn't boot, or it says "Reached the end of the file.(0x80070026: Receiving hello packet)". In both case, it doesn't work.
So this is where I am now, an empty phone, with no ROM, just detected by the computer to flash. But some one told me a Qualcomm SOC can't be totally bricked, so I still have hope.
Could you please help me ? I've been working on it for so long, trying all sort of stuff, downloading every single driver from all over the web. I can't do any better.
Ask me some questions, ask for screenshots, I'm at your service !

I also tried this guide : w w w . droidviews .c o m /how-to-bo...astboot-download-bootloader-or-recovery-mode
But each adb reboot command returns "error : no device/emulator found"
Yet, it seems to be the very last thing I could do and it should work, do you think the issue is about drivers ? Or is that possible that even adb reboot commands fail ?

This is what I have in my devices manager : h t t p : / / hpics . li/da67572

I found out that when I press volume- and power for a long time, it activates the bootmod (which means I can flash with QFIL). But if I hold it two more seconds, the bootmod is desactivated, and that's why I was stuck until now.
I have now the ZUI ROM STOCK.
But still trying to get Mokee ^^

cannot access TWRP after successful flashing

Hi guys
today was my waiting time over and so i opend the bootloader and flashed:
Twrp_3.3.0_Cepheusv11
xiaomi.eu_multi_MI9_9.5.23_v10-9
Magisk-v19.2
all with success.
The phone (Global version, 6gb+128gb) boots normal and everything works fine up to the point where i want to boot in TWRP. After starting the phone with power+Vol up i get the mi unlocked screen and then for 1 second a black screen, then its reboot and i'm on the mi unlock screen again. Fastboot and normal system boot works fine, i have root over magisk and everything.
Any ideas how to get into twrp again?
Longer version:
After unlocking the bottloader i followed this guide-how-flashed-twrp-xiaomi-eu-rom but with newer files. For TWRP i used the Twrp_3.3.0_Cepheusv11 version from here. The eu rom came from sourceforge and the magisk version from here.
I flashed twrp over terminal from my pc with "fastboot flash recovery twrp.img" and uploaded the rom and magisk with "adb push rom.zip /tmp/" + "adb push magisk.zip /tmp/" to the ram. After disconnection the usb cable i hold down power+vol up while still in the fastboot mode and the phone reboots into twrp. from there it was strait following the guid eg. wipe menu, format data, confirmed with "yes", wipe menu again, factory reset. Install rom.zip, install magaisk.zip both without any errors. Reboot menu and select "do not install" for the twrp app.
From now on the eu rom started up, i connected to my wlan and connected the phone to my mi account and after that to my google account. The rest was normal installation.
After installing everything i debloated the phone with this list. Instead of pasting the full list i chose just the follwing parts:
Android Stuff: none
Google Stuff: none
Xiaomi Stuff: all
Xiaomi Apps: all
Extra Stuff: none
To be Tested yet (try at your own risk):
com.miui.compass
com.miui.calculator
com.miui.cloudservice.sysbase
com.miui.gallery
com.miui.screenrecorder
com.mi.webkit.core
com.miui.providers.weather
Unfortunately is the android.providers.calendar app in the xiaomi app list and my calender didn't sync to google without it. So i read a bit about the com.android.providers.calendar app and learned that it is a specific app for every version of android and i cannot simply use the version from my other phone.
Okay, i thougt, my system is just about 2 hours old i reflash the eu rom and magisk and be done with it. So said, i wanted to boot into twrp, powerd the phone off, hold down power+vol up and got the miui unlocked screen, after that 1 second of black screen and than the miui unlock screen again with is followed by the normal system boot.
First i thought i missed the right moment for holding the buttons down so i installed apps which allowed me to directly reboot into recovery.
But with ervery app it was the same: miui unlocked screen, after that 1 second of black screen and than the miui unlock screen again with is followed by the normal system boot.
So i reflashed twrp over the terminal "fastboot flash recovery twrp.img" and it was stated a success. But again only: miui unlocked screen, after that 1 second of black screen and than the miui unlock screen again with is followed by the normal system boot.
Next i tried to reboot into recovery from adb but it was the same result.
Next i tried to just boot twrp from terminal with "fastboot boot twrp.img" but again, same result.
Next i tried to install different versions of twrp. From beta8 to beta11 i flashed every version but again, same result.
Now i'm sitting here happy with a new eu rom and fully rooted but unhappy with the knowing i cannot update anymore. Any ideas how to get into twrp again?
Edit: i reinstalled my android.providers.calendar after i read the "How to Re-Install an Uninstalled App" section again ^^

I read somewhere the Chinese recovery should work with latest Xiaomi.eu. TWRP is still in early stages.

Re-flash the recovery in fastboot mode. After flashing don't reboot recovery with a command but reboot recovery by pressing vol+ and power, keep both pressed untill you see twrp booting. Happened with me as well but than got sorted by flashing again after setting up the rom, enabling usb debugging and going back into fastboot and flash. And can I ask why did you use version 11 when the latest on that recovery is v17 beta and a final version but v17 is good and decrypts as well, hope this helps, cheers.
version 17 is on this page: click on the mega link
https://forum.xda-developers.com/Mi-9/how-to/recovery-unofficial-twrp-recovery-3-2-3-t3912118/page10
Also try this recovery,
https://forum.xda-developers.com/Mi-9/development/twrp-3-3-0-arm64-gapps-support-t3925728

Xiaomi.eu
k4win said:
Hi guys
today was my waiting time over and so i opend the bootloader and flashed:
Twrp_3.3.0_Cepheusv11
xiaomi.eu_multi_MI9_9.5.23_v10-9
Magisk-v19.2
all with success.
The phone (Global version, 6gb+128gb) boots normal and everything works fine up to the point where i want to boot in TWRP. After starting the phone with power+Vol up i get the mi unlocked screen and then for 1 second a black screen, then its reboot and i'm on the mi unlock screen again. Fastboot and normal system boot works fine, i have root over magisk and everything.
Any ideas how to get into twrp again?
[...]
Click to expand...
Click to collapse
Hello, i had the same pb, try this recovery: https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825 it's ok for me.
@++

NEM-L21: Stucked with wrong version of boot.img, no more possibility of flashing

Hello everyone, it's my first time writing here, but I’ve tried everything, searched everywhere, and am desperate for help.
I screwed up big time while trying to flash a custom rom on my nem-l21, as I successfully did before with my xiaomi... So what I did:
I managed to unlock bootloader with dc unlocker. Then I got stucked flashing twrp with adb tools. Everything was looking to be fine, no error messages, “flashing successful”… But, I was never able to boot into flashed twrp. Always got stuck on “your phone has been unlocked blah blah. Your device is booting.” It never booted, not in twrp, nor in stock recovery. I tried different versions of twrp from different sources, always same result (flashing successful, booting into recovery not). Booting into the system was fine. And then I made that horrible mistake. Oh, how I wish I didn’t!!
I read on some website, that you are supposed to flash the twrp as boot.img, not as recovery.img. Seemed illogical and stupid to me, but in the end I tried it. Of course, this just bricked my phone, with no possibility to boot. After hours of googling, installing, trying and crying, I managed in the end to flash back stock boot.img. But at that time, I didn’t know my build number (b359), and I flashed boot.img b351. So now I have a phone which boots into the system b359 with boot.img b351, but with lot of errors.
- developer options, security options, display and factory reset option doesn’t work and just crashes. Therefore I am not able to flash the correct boot.img b359 or anything else at all from pc, no way to enable usb debugging and oem unlocking. Adb devices → nothing. I am able to use fastboot (fastboot devices sees the phone), but when try to flash something, I get error “command not allowed”. Also I can’t enable unknown sources installation, which bothers me a lot. And I can’t make factory reset to restore the crashing settings. Also I can’t change display timeout, and original 30 secs is super annoying.
- I am not able to uninstall even apps installed by me, always just restarts system UI and app stays.
What I tried so far:
- flashing correct boot.img from pc, not working because of dev options crashing
- go into recovery, but stock one is overwritten with unfunctioning twrp, always just get stuck on “your phone was unlocked blah blah… your device is booting now”, but it never does, have to hard reboot
- go into huawei erecovery, which is working, but when I try to resolve problem from there, always ends up with errors and crashes
- connect to pc and use HiSuite, system recovery tool here always says “no problem detected”
- updating to b361 through system update settings, always crashes on 5% and sends phone into “your phone was unlocked blah blah… your device is booting now” error
- downloading the proper b359 as and update.app file, put it in dload internal storage → same error during update, put it in dload sdcard → same error, no matter which way I use to start the update
- boot into twrp or stock recovery.img through fastboot without actually flashing it, anyway error “command not allowed”
- do factory reset or update through dial codes (i.e. *#*#123456#*#* …), nothing worked
My pc is windows 10, all drivers up to date. Using powershell as an admin. Am an idiot for not making backup of the phone before I started...
So, now I have more or less functioning phone, but I can’t uninstall any apps at all, can’t install from unknown sources, can’t do nothing from pc, can’t make any update, and lot of important settings keep crashing.
I can use the phone like this, but if somebody could think about some solution for this ****ed up situation I got myself into, I would be grateful to him/her for the rest of my life.
Sorry for a long post.
Thank you in advance and have a nice day

I think using Hisuit will help. Enter Fastboot and connect ur phone to ur computer and use system recovery toll

Mi 9 bricked - Locked bootloader & MiUI version can't be installed on this device

Hi all,
I have searched for a solution to this but haven't come across anyone witht the same issue.
I bought a Mi 9 from China which came with the Global rom loaded. I found out that I couldn't use Google Pay unless I rooted with Magisk.
So I went through the process of trying to flash Magisk through fast boot (didn't work - boot loop to recovery) then with TWRP (didn't work - boot to TWRP and freeze).
I then used Miflash to flash the latest global stable version. Unfortunately I didn't notice it was defaulted to "clean all and lock" when I flashed. When the device restarted, it loaded into recovery and was no longer unlocked. The message is "This MIUI version can't be installed on this device". But I can't flash again, because its locked.
I downloaded the MiUnlock app and after running it get the message "Current account is not bound to this device" with instructions to change settings in developer options. But I can't access the developer options because the MIUI isn't loading.
So, yeah. I think I'm in trouble. Any suggestions?

If your device was global version i would say flash fastboot ROM with Mi flash tool or using script flash_all.bat. Then bound your account to your device, then try to unlock recovery. But i red that in some cases Chines version is not so simple, so search, how to flash fastboot ROM on Chines device and if there is some problems with this.
You will need adb and fastboot installed on your pc.
Upd. Man it's all over the internet, just search "This miui version can't be installed on this device". There is a fix with opening the device and so on... but if i was you i would try to contact the seller of the device and ask him to use his account to unlock recovery. My be using teamviewer or similar software.

you bought in china with global rom and it was unlocked already ? because if you tried twrp then the device must be unlocked (bootloader)
then it was a China Version with unlocked bootloader and global rom. you used then the miflash and locked the bootloader again and flashed the global rom...
so you bricked your device....
if found this in an other forum:
"Dear customers, our service provides services in a remote format, if you are from another country .
If you need Mi Authorized EDL Account or you need my services for the restoration of the brick phones and the account is deleted, mi, if you forgot , contact me on my contacts : WhatsApp +7967 777 15 98"

g_seva said:
If your device was global version i would say flash fastboot ROM with Mi flash tool or using script flash_all.bat. Then bound your account to your device, then try to unlock recovery. But i red that in some cases Chines version is not so simple, so search, how to flash fastboot ROM on Chines device and if there is some problems with this.
You will need adb and fastboot installed on your pc.
Upd. Man it's all over the internet, just search "This miui version can't be installed on this device". There is a fix with opening the device and so on... but if i was you i would try to contact the seller of the device and ask him to use his account to unlock recovery. My be using teamviewer or similar software.
Click to expand...
Click to collapse
Thanks! I searched as suggested and am trying a fix from the MIUI forum "[FIX] unbrick your BL LOCKED phone without xiaomi id authorization!!!". If that doesn' work I'll go with the team viewer option. Cheers!

minnnism said:
Hi all,
I have searched for a solution to this but haven't come across anyone witht the same issue.
I bought a Mi 9 from China which came with the Global rom loaded. I found out that I couldn't use Google Pay unless I rooted with Magisk.
So I went through the process of trying to flash Magisk through fast boot (didn't work - boot loop to recovery) then with TWRP (didn't work - boot to TWRP and freeze).
I then used Miflash to flash the latest global stable version. Unfortunately I didn't notice it was defaulted to "clean all and lock" when I flashed. When the device restarted, it loaded into recovery and was no longer unlocked. The message is "This MIUI version can't be installed on this device". But I can't flash again, because its locked.
I downloaded the MiUnlock app and after running it get the message "Current account is not bound to this device" with instructions to change settings in developer options. But I can't access the developer options because the MIUI isn't loading.
So, yeah. I think I'm in trouble. Any suggestions?
Click to expand...
Click to collapse
https://forum.xda-developers.com/Mi-9/help/soldthis-miui-version-installed-device-t3975421
Read carefully and report
1. Try to hold down the buttons vol down and power, see if : fastboot devices sees it. If so XiaoMi Tool will restore it. If not do the same try recovery vol up + power. Do adb devices and see if anything shows up. Worst case you'll have to open the phone up and connect the EDL pins together and it will flash anything. I use minimal ADB and Fastboot phone plugged via USB cable into the computer and run those commands.
2. Fully bricks their device here is the unbrick factory method
https://c.mi.com/thread-1479882-1-0.html
that's connecting EDL pins with the phone case removed for a phone that doesn't boot at all
3. https://youtu.be/8mW0JzKow7E
here's the exact EDL test point required on Mi9
if you can't boot or recognize the device at all via fastboot or ADB. If this doesn't work nothing will...
But it will work, that's what the factory does. Obviously the last resort.

any success?

Xiaomi MI A2, is stuck in bootloop

Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.

Is it a Guide?
Oh, now, its a Great News!
Please delete this post from this forum.
As I have already wrote to you, questions should go to "Questions and Answers" forum.
And as I have already wrote to you, Search works here, and if you've used it, you'd get answers (in mentioned above forum):
1. MiA2 having A/B slots architecture, - is supposed to recover to the other slot X when OTA corrupts ROM is slot Y, - after numerous boot attempts.
2. In case you have tampered phone with try-and-see operations without knowing what you were doing - the only way to recover phone is: TEST Point / EDL. Search these keywords in this forum for appropriate Guide.

try the "fastboot continue" command

dillu12 said:
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Click to expand...
Click to collapse
you need to flash the phone in edl mode
**just be careful there is a timeout ..when you put it into edl you need miflash and rom.loaded
*** download a stock fastboot stable pie for jasmine
**** unzip amd select revelant xml from within miflash
*****on phone manually boot to fastboot mode with buttons
****** run command "fastboot oem.edl"
*******device will boot to black screen ... immediately go to miflash and press the button to start flashing
___BE CAREFUL__ select clear all tick box at bottom of miflash screen
this should be enough to rescue your device regardless of what you've done or whether you unlocked bootloader or not