My Redmi Note 3 Kenzo is bricked, it doesn't go past MI Logo.
I have tried flashing multiple stock ROMs in edl and fastboot mode, mi flash tool says success but device doesn't go past MI Logo.
This happened when I was trying to repair my lost IMEI, I found this thread on XDA:
https://forum.xda-developers.com/redmi-note-3/how-to/recover-redmi-note-3-sd-imei-baseband-t3744385
My device was bricked after I wrote the following commands:
fastboot flash modemst1 modemst1
fastboot flash modemst2 modemst2
fastboot flash fsg fsg
I can still access fastboot, please help.
Samip12 said:
My Redmi Note 3 Kenzo is bricked, it doesn't go past MI Logo.
I have tried flashing multiple stock ROMs in edl and fastboot mode, mi flash tool says success but device doesn't go past MI Logo.
This happened when I was trying to repair my lost IMEI, I found this thread on XDA:
https://forum.xda-developers.com/redmi-note-3/how-to/recover-redmi-note-3-sd-imei-baseband-t3744385
My device was bricked after I wrote the following commands:
fastboot flash modemst1 modemst1
fastboot flash modemst2 modemst2
fastboot flash fsg fsg
I can still access fastboot, please help.
Click to expand...
Click to collapse
THREE threads about the same issue AND in the wrong forum?
Samip12 said:
My Redmi Note 3 Kenzo is bricked, it doesn't go past MI Logo.
I have tried flashing multiple stock ROMs in edl and fastboot mode, mi flash tool says success but device doesn't go past MI Logo.
This happened when I was trying to repair my lost IMEI, I found this thread on XDA:
https://forum.xda-developers.com/redmi-note-3/how-to/recover-redmi-note-3-sd-imei-baseband-t3744385
My device was bricked after I wrote the following commands:
fastboot flash modemst1 modemst1
fastboot flash modemst2 modemst2
fastboot flash fsg fsg
I can still access fastboot, please help.
Click to expand...
Click to collapse
Are u sure phone is kenzo and not kate?
Many users lost thier baseband coz of flashing wrong miui rom on wrong device.
If above is not the cause then may be its due to replacing of duplicate incompatible parts. Never go to local unauthorized shops.
Black_Stark said:
Are u sure phone is kenzo and not kate?
Many users lost thier baseband coz of flashing wrong miui rom on wrong device.
If above is not the cause then may be its due to replacing of duplicate incompatible parts. Never go to local unauthorized shops.
Click to expand...
Click to collapse
oh ****, looks like its kate, the model number in my box is 2015161, https://forum.xda-developers.com/redmi-note-3/help/guys-how-tell-kate-kenzo-t3479255
i rememebr trying to flash a kate image and mi flash said mismatching image and device and i thought my device was kenzo.
What should I do now?
Samip12 said:
oh ****, looks like its kate, the model number in my box is 2015161, https://forum.xda-developers.com/redmi-note-3/help/guys-how-tell-kate-kenzo-t3479255
i rememebr trying to flash a kate image and mi flash said mismatching image and device and i thought my device was kenzo.
What should I do now?
Click to expand...
Click to collapse
I just flashed kate image in edl mode, but the device did not boot. I have found this new tool called mi flash pro, now i'm trying to flash via recovery .Previously, i had to enter my IMEI number as the fields were blank, but now my IMEI was already there. Looks like I have my IMEI in the device now but the device is not booting.
Samip12 said:
I just flashed kate image in edl mode, but the device did not boot. I have found this new tool called mi flash pro, now i'm trying to flash via recovery .Previously, i had to enter my IMEI number as the fields were blank, but now my IMEI was already there. Looks like I have my IMEI in the device now but the device is not booting.
Click to expand...
Click to collapse
Kate is redmi note 3 special edition. Its not written on box ?
Kenzo is 15.0 cm
Kate is 15.2 cm.
Black_Stark said:
Kate is redmi note 3 special edition. Its not written on box ?
Kenzo is 15.0 cm
Kate is 15.2 cm.
Click to expand...
Click to collapse
Its just written Redmi Note 3 in box.
Looks like it's 15cm, but .. 15 and 15.2, too close to be determined.
I had a similar issue in my friend's phone. Now you need to keep a few things in mind.
1) is the device rebooting back to mi logo again and again - the reason for this is a faulty battery.
2) is the device kenzo or kate??? Kenzo was sold in 2+16 and 3+32 configuration. Kindly check on the box for the network band support and compare with gsmarena.
3)you need to flash miui 7 rom if you need to recover your device. My volte was completely broken and that's the only way i could fix it.
Good luck
tejasvi001 said:
I had a similar issue in my friend's phone. Now you need to keep a few things in mind.
1) is the device rebooting back to mi logo again and again - the reason for this is a faulty battery.
2) is the device kenzo or kate??? Kenzo was sold in 2+16 and 3+32 configuration. Kindly check on the box for the network band support and compare with gsmarena.
3)you need to flash miui 7 rom if you need to recover your device. My volte was completely broken and that's the only way i could fix it.
Good luck
Click to expand...
Click to collapse
My device appears to be kate.
The mi logo doesn't reappear. It appears then the device turns off.
I'll try with MIUI 7.
tejasvi001 said:
I had a similar issue in my friend's phone. Now you need to keep a few things in mind.
1) is the device rebooting back to mi logo again and again - the reason for this is a faulty battery.
2) is the device kenzo or kate??? Kenzo was sold in 2+16 and 3+32 configuration. Kindly check on the box for the network band support and compare with gsmarena.
3)you need to flash miui 7 rom if you need to recover your device. My volte was completely broken and that's the only way i could fix it.
Good luck
Click to expand...
Click to collapse
flashed MIUI 7 ROM , device didn't boot as usual. The mi logo appears and the device shuts off itself.
What might be the problem?
Muhammad Haris
Your wrong in flash modemts1, modemts2, and fsg. So make your device stuck at mi logo. Not like that solution for write imei back to your device.
I give recommend, you try open cmd(minimal adb fastboot). You can search in google about minimal adb fastboot. And you type command like that:
Fastboot modemst1 erase
Fastboot modemst2 erase
Fastboot fsg erase
That's will make your phone lose imei. But your phone Will normal booting. To write imei, maybe I can help other time. Now, you must try it. Can or not to make your phone normal. Oke. Thank you
is it a faulty battery? I have been using this device since 2016 and the battery didn't last good the last time the device worked. I can boot into fastboot, I can boot into recovery, everytime I flash ROM it says success, I can flash and use TWRP. I can do everything except using the system. I just tried installing lineage OS 14.1. Sometimes after MI logo, the lineage OS animation appears a little bit and the device shuts off again.
Mharis0799 said:
Your wrong in flash modemts1, modemts2, and fsg. So make your device stuck at mi logo. Not like that solution for write imei back to your device.
I give recommend, you try open cmd(minimal adb fastboot). You can search in google about minimal adb fastboot. And you type command like that:
fastboot modemst1 erase
fastboot modemst2 erase
fastboot erase fsg
That's will make your phone lose imei. But your phone Will normal booting. To write imei, maybe I can help other time. Now, you must try it. Can or not to make your phone normal. Oke. Thank you
Click to expand...
Click to collapse
Thank you so muchh man , my phone is booting again I can't thank you enough mate.
Mharis0799 said:
Your wrong in flash modemts1, modemts2, and fsg. So make your device stuck at mi logo. Not like that solution for write imei back to your device.
I give recommend, you try open cmd(minimal adb fastboot). You can search in google about minimal adb fastboot. And you type command like that:
Fastboot modemst1 erase
Fastboot modemst2 erase
Fastboot fsg erase
That's will make your phone lose imei. But your phone Will normal booting. To write imei, maybe I can help other time. Now, you must try it. Can or not to make your phone normal. Oke. Thank you
Click to expand...
Click to collapse
I wrote the above command and flashed kate ROM through edl mode,now my device is booting and everything is working except sim card and loudspeaker. The IMEI is unknown.
Samip12 said:
I wrote the above command and flashed kate ROM through edl mode,now my device is booting and everything is working except sim card and loudspeaker. The IMEI is unknown.
Click to expand...
Click to collapse
I also remember flashing a kenzo persist.img file on my device, does that have anything to do with loudspeaker?
Black_Stark said:
Are u sure phone is kenzo and not kate?
Many users lost thier baseband coz of flashing wrong miui rom on wrong device.
If above is not the cause then may be its due to replacing of duplicate incompatible parts. Never go to local unauthorized shops.
Click to expand...
Click to collapse
if I'm not mistaken only the rom changes between kenzo and kate so this shouldn't be the problem.
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
Samip12 said:
flashed MIUI 7 ROM , device didn't boot as usual. The mi logo appears and the device shuts off itself.
What might be the problem?
Click to expand...
Click to collapse
Try with flashing a custom rom via twrp, now android 6 is an outdated system.
MatteoGemma said:
if I'm not mistaken only the rom changes between kenzo and kate so this shouldn't be the problem.
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
Try with flashing a custom rom via twrp, now android 6 is an outdated system.
Click to expand...
Click to collapse
my phone boots now, everything works except loudspeaker and SIM is not detected due to unknown IMEI, also tried lineage OS 14.1 same problem.
Samip12 said:
my phone boots now, everything works except loudspeaker and SIM is not detected due to unknown IMEI, also tried lineage OS 14.1 same problem.
Click to expand...
Click to collapse
Try with an android 9/10 official custom rom
Samip12 said:
I wrote the above command and flashed kate ROM through edl mode,now my device is booting and everything is working except sim card and loudspeaker. The IMEI is unknown.
Click to expand...
Click to collapse
With those commands, its already mentioned it will make you LOSE imei but help in booting... & That worked for you...
He then said to guide you how to write back imei. So you should now look for the procedure to restore imei infos., Or wait for him to tell you...
Related
Moto G5s Plus Xt1802 does not work!
My most Moto G5s had a loop problem. It would call itself, switch off and restart itself. It had a own life.
1
Then I got the bootloader after tried several methods. I got the code with a Motorola support.
2
I cannot root! Keep trying, but no success.
3
I already tried to use GZOSP, Liquid Remix, Pixel, Zero, and even return to Original Stock, but I can not. I tried via TWRP or via Prompt ADB.
4
If any ROM is installed, in the first start, this message appears: the password is correct, but unfortunately your data is corrupted. The message is the same, if I type correct password or not.
5.
If an installation is successful, the IMEIs disappear and I cant use the simcard.
The file system is as ext4, but sometimes it appears as e2fs. Could this be wrong? How do I setup this, can you install one of these cost roms? How to mount it correctly?
How should I proceed?
So, I ask for the help of these master experts, because I still can not solve it. Since then I cant use the device, cant enjoy anything of it.
Best Regards, guys!
Always take a backup using twrp before doing anything, keep it safe.
First Make sure that you are using latest TWRP 64 bit recovery.
Download latest Custom ROM and flash it..
For password problem..Wipe Data.
Now check that your IMEI number is OK..and you are getting signal.(if there is no 4G signal.. reply here)
Caution: While flashing Stock Don't use modem erase Commands , otherwise IMEI will be Null..skip these.
If possible take a backup of efs and persist partition..will be helpful in case of emergency.
Avoid volte fix.
crazytech2 said:
Always take a backup using twrp before doing anything, keep it safe.
First Make sure that you are using latest TWRP 64 bit recovery.
Download latest Custom ROM and flash it..
For password problem..Wipe Data.
Now check that your IMEI number is OK..and you are getting signal.(if there is no 4G signal.. reply here)
Caution: While flashing Stock Don't use modem erase Commands , otherwise IMEI will be Null..skip these.
If possible take a backup of efs and persist partition..will be helpful in case of emergency.
Avoid volte fix.
Click to expand...
Click to collapse
Ok, Crazytech,
Your tips have helped a lot.
I installed and am testing Frankenrom.
I noticed that the LTE 4G is not operating, only the 3G +
mdr1982 said:
Ok, Crazytech,
Your tips have helped a lot.
I installed and am testing Frankenrom.
I noticed that the LTE 4G is not operating, only the 3G +
Click to expand...
Click to collapse
Is your IMEI number is visible..*#06#
If yes..Do one more thing..
Restart your phone into Bootloader mode..
Pass these two Commands..
fastboot erase modemst1
fastboot erase modemst2
Reboot Now..and Check 4G signal..!
crazytech2 said:
Is your IMEI number is visible..*#06#
If yes..Do one more thing..
Restart your phone into Bootloader mode..
Pass these two Commands..
fastboot erase modemst1
fastboot erase modemst2
Reboot Now..and Check 4G signal..!
Click to expand...
Click to collapse
Great !!!!
Now LTE 4G works as well.
Sincere thanks.
Someone can remove the message: Your device has been unlocked and can not be trusted. To learn more, visit: motorola.com/unlockbootloader?
mdr1982 said:
Great !!!!
Now LTE 4G works as well.
Sincere thanks.
Someone can remove the message: Your device has been unlocked and can not be trusted. To learn more, visit: motorola.com/unlockbootloader?
Click to expand...
Click to collapse
Now...if you want to flash stock again skip modem erase Commands.. always..!!
Otherswise Null IMEI will be there..!!
What about volte..right now..??
crazytech2 said:
Now...if you want to flash stock again skip modem erase Commands.. always..!!
Otherswise Null IMEI will be there..!!
What about volte..right now..??
Click to expand...
Click to collapse
Well,
I think this Frankenrom ROM has not, I have not seen it yet.
I am paying attention to Motorola's message , to remove this.
mdr1982 said:
Well,
I think this Frankenrom ROM has not, I have not seen it yet.
I am paying attention to Motorola's message , to remove this.
Click to expand...
Click to collapse
Flash a Custom logo.bin..this message will be hidden..no more visibility..!!
crazytech2 said:
Flash a Custom logo.bin..this message will be hidden..no more visibility..!!
Click to expand...
Click to collapse
Im Trying, but no success:
"flashboot flash logo logo.bin"
dont work
mdr1982 said:
Im Trying, but no success:
"flashboot flash logo logo.bin"
dont work
Click to expand...
Click to collapse
Right now..on which rom are you trying this. ?
Check this may be helpful..
https://forum.xda-developers.com/moto-g5s-plus/themes/logo-bin-nice-bootloader-images-t3692228
https://forum.xda-developers.com/mo...ove-unlocked-bootloader-message-moto-t3672419
crazytech2 said:
Right now..on which rom are you trying this. ?
Check this may be helpful..
https://forum.xda-developers.com/moto-g5s-plus/themes/logo-bin-nice-bootloader-images-t3692228
https://forum.xda-developers.com/mo...ove-unlocked-bootloader-message-moto-t3672419
Click to expand...
Click to collapse
Solved logo problem.
I used Motorola Logo Maker and created my own logo
And then flash with fastboot.
https://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667
mdr1982 said:
Solved logo problem.
I used Motorola Logo Maker and created my own logo
And then flash with fastboot.
https://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667
Click to expand...
Click to collapse
Fantastic..!
Enjoy..!!
Some custom ROMs have some password even if u don't put them ..... So flash the lock fixer zip from twrp
Hello all, i unlocked the bootloader on the xiaomi mi A2 , and i was trying to follow this guide :https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475 to install the gmcam, but after the point 5. i just rebooted the phone from the recovery, just cause i wanted to try it, after that is stucked in android 8.1 animation, but i have access to the recovery (even if the tool shouldnt have installed it), but dunno what can i do from the recovery, and the device can go in fastboot mode but is not recognized by adb, what can i do?
What version of software was your Mi A2, if it was V9.6.13.0.ODIMIFE, then download the full stock ROM from here
http://en.miui.com/download-353.html
In fastboot mode, adb is not working, fastboot commands works there.
Extract boot.img from images of downloaded ROM.
Put the boot.img in adb folder.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
it should start normally
If not, then flash every image like in this post.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
minnuss said:
What version of software was your Mi A2, if it was V9.6.13.0.ODIMIFE, then download the full stock ROM from here
http://en.miui.com/download-353.html
In fastboot mode, adb is not working, fastboot commands works there.
Extract boot.img from images of downloaded ROM.
Put the boot.img in adb folder.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
it should start normally
If not, then flash every image like in this post.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
Thanks for the help, but, I don't know why, ADB driver were not working properly, didnt recognize the phone so I couldnt follow this guide, and i couldnt switch off the phone either, it was stuck in bootloop, the only thing I was able to do is to put the device in fastboot mode using the button combination..
Luckly the Mi Flash tool was able to recognize the device so I flashed the stock rom with that and now everything is back to normal, I've just a question, the phone sais that the bootloader is still unlocked, is that true? Even if I've flashed from zero the stock rom?
fuffy841 said:
Thanks for the help, but, I don't know why, ADB driver were not working properly, didnt recognize the phone so I couldnt follow this guide, and i couldnt switch off the phone either, it was stuck in bootloop, the only thing I was able to do is to put the device in fastboot mode using the button combination..
Luckly the Mi Flash tool was able to recognize the device so I flashed the stock rom with that and now everything is back to normal, I've just a question, the phone sais that the bootloader is still unlocked, is that true? Even if I've flashed from zero the stock rom?
Click to expand...
Click to collapse
Yep, it's true. You have to relock the bootloader, but this cause full wipe. IMO there's no need to relock the bootloader if you not enable the usb dev mode.
Also, theres an option in mi flash tool to lock the bootloader after flash. Something like flash_all_lock
DO NOT use flash_all_lock_crc. This will cause dead wifi and Bluetooth modem.
I am stuck on the exact same issue. Can you explain in detail all the steps you followed.
Mine was updated to September patch and it is Indian variant.
---------- Post added at 06:16 PM ---------- Previous post was at 05:31 PM ----------
rt1279_isBITW said:
I am stuck on the exact same issue. Can you explain in detail all the steps you followed.
Mine was updated to September patch and it is Indian variant.
Click to expand...
Click to collapse
Nvm I was able to flash that rom but now after the phone locks once the touch is gone until I reboot the device.
Are there any hardware differences in my indian variant or did I just flash it wrong?
I used flash_all.bat and clean all option.
Daniesz said:
Yep, it's true. You have to relock the bootloader, but this cause full wipe. IMO there's no need to relock the bootloader if you not enable the usb dev mode.
Also, theres an option in mi flash tool to lock the bootloader after flash. Something like flash_all_lock
DO NOT use flash_all_lock_crc. This will cause dead wifi and Bluetooth modem.
Click to expand...
Click to collapse
Nono i want to keep the bootloader unlocked, that's why I asked ! Thanks man.
Nvm I was able to flash that rom but now after the phone locks once the touch is gone until I reboot the device.
Are there any hardware differences in my indian variant or did I just flash it wrong?
I used flash_all.bat and clean all option
Click to expand...
Click to collapse
I used the same option, cause it didnt work with the other ones.. I didnt have any issue so far tho, and I dont know about hardware differences, but I dont think a bad flash can cause this kind of problem, not sure tho. Maybe now that everything is working try to flash again a stock rom.
I need help can't access adb only stuck in fastboot please help
tried xiaomi tool and didnt work, need to enable usb debugging please help
Flash stock rom with miflash.
Have you tried flashing TWRP then MIUI in TWRP?
Kollachi said:
Flash stock rom with miflash.
Click to expand...
Click to collapse
I'm getting an error "couldn't find flash script"
_MartyMan_ said:
Have you tried flashing TWRP then MIUI in TWRP?
Click to expand...
Click to collapse
I flashed twrp using the fastboot command many times but it doesn't install
I also tried the fastboot boot twrp.img but im getting an error
zydalili said:
I'm getting an error "couldn't find flash script"
Click to expand...
Click to collapse
did you download the correct file? did you download stock fastboot rom or stock flash rom?
It's okay now
I used miflash pro and downloaded the rom directly from the app. Now it's fully working again. Thanks for the help guys.
"Flash crclist error" in MI 9 cepheus
Hello, I deleted everything in my MI 9 cepheus, already tried with mi flash, with mi flash pro, with mi suite with xiaomi tools and I can not reset anything.
This happened after installing twrp with adb and within twrp do wipe cache / dalvik, the files were all coded and from there it was in fastboot mode and I can not do anything else.
In mi flash gives the error "Flash crclist error", and died ... peace to your soul :crying:
mavimendes said:
Hello, I deleted everything in my MI 9 cepheus, already tried with mi flash, with mi flash pro, with mi suite with xiaomi tools and I can not reset anything.
This happened after installing twrp with adb and within twrp do wipe cache / dalvik, the files were all coded and from there it was in fastboot mode and I can not do anything else.
In mi flash gives the error "Flash crclist error", and died ... peace to your soul :crying:
Click to expand...
Click to collapse
You have to lock bootloader again "fastboot oem lock" and that Will give you the error system hás been destroyed. Then put him um fastboot mode and flash with miflash tool. Last time that happend me i was in a fastboot loop it took me 5 days to discover.
Flashing Guide - Fastboot Update
Try fastboot ROM to flash new ROM by fastboot tool.
1.Fastboot tool: http://api.en.miui.com/url/MiFlashTool
2.Fastboot ROM download: http://en.miui.com/a-234.html (Find correct one for your device )
zydalili said:
I need help can't access adb only stuck in fastboot please help
tried xiaomi tool and didnt work, need to enable usb debugging please help
Click to expand...
Click to collapse
mavimendes said:
Hello, I deleted everything in my MI 9 cepheus, already tried with mi flash, with mi flash pro, with mi suite with xiaomi tools and I can not reset anything.
This happened after installing twrp with adb and within twrp do wipe cache / dalvik, the files were all coded and from there it was in fastboot mode and I can not do anything else.
In mi flash gives the error "Flash crclist error", and died ... peace to your soul :crying:
Click to expand...
Click to collapse
I had same thing happen to me. You need to force flash firmware. Another XDA member suggested to use miuiflashpro. And flash your phone's firmware back. Part of your phone's recovery has been erased I think. Choose keep data or flash all in settings an your cell will work again
Hello, thanks for the tips, Miflashpro nor detects the equipment... I've exhausted the ideas and options. I think I got a paperweight to put in the Office ?
mavimendes said:
Hello, thanks for the tips, Miflashpro nor detects the equipment... I've exhausted the ideas and options. I think I got a paperweight to put in the Office ?
Click to expand...
Click to collapse
You put him in fastboot mode? Because you only can flash in Miflash pro with fastboot mode
PRolo said:
You put him in fastboot mode? Because you only can flash in Miflash pro with fastboot mode
Click to expand...
Click to collapse
Yes, is in fasboot Mode.
Sent from my MI 9 using Tapatalk
Can you reflash twrp?
Then ADB sideload ROM?
Goto advanced twrp file manager and move ROM to internal storage?
Then flash ROM?
Follow first post in this thread:
https://forum.xda-developers.com/Mi-9/how-to/guide-how-flashed-twrp-xiaomi-eu-rom-t3912952
After all this was easier to solve than apparently it seemed. Just installed a new version of TWRP (3.3.1-34), the previous one although it indicated that it was nominated for the MI9, was not the best choice. After installing a new one, I uploaded the ROM(MIUI 10.5 by xiaomi.eu 9.6.20) to the root of the phone and installed it. It's all working again.
mavimendes said:
After all this was easier to solve than apparently it seemed. Just installed a new version of TWRP (3.3.1-34), the previous one although it indicated that it was nominated for the MI9, was not the best choice. After installing a new one, I uploaded the ROM(MIUI 10.5 by xiaomi.eu 9.6.20) to the root of the phone and installed it. It's all working again.
Click to expand...
Click to collapse
can you link me the one you downloaded? i installed twrp multiple times and it still wont go to recovery.
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?
Hey guys.. just updating you all
in all of my (previous ) test to get my patched boot.img
i've got this initial msg on my boot :
dm-verity corruption
your device is corrupt.
it can't be trusted and my not work properly.
press enter button to continue.
Or, device will power off in 5s.
(written in white)
NOW i tell that it didn't happen after bootloader unlock (so it was unlocked and all good no problem )
but honestly i don't remember if that happened when i tried to upload official rom through Miflash !
Anyway is there any way to remove this? I re installed ( clean install ) official Rom and it's still there, locked bootloader back and it's still there tried some
fastboot oem enable_dm_verity
i'm also warning new user that you might get this msg at boot !
thanks
forget this..i've got ROOT check the other thread !
How do you fix it?
simika said:
forget this..i've got ROOT check the other thread !
Click to expand...
Click to collapse
How did you managed to fix this?
by reading lol.. check the other thread all written
For reference to whoever that are confused about where to look for the solution.
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
Download the vbmeta and flash it via fastboot to get rid of the dm-verify.
simika said:
by reading lol.. check the other thread all written
Click to expand...
Click to collapse
Could you reference a link or give me a little how to?
I tried a lot now:
- Installed a new Firmware trough Fastboot
- Using MsmDownload Tool
nothing helped so far.
So it would be great if you could assist in any way.
simika said:
Hey guys.. just updating you all
in all of my (previous ) test to get my patched boot.img
i've got this initial msg on my boot :
dm-verity corruption
your device is corrupt.
it can't be trusted and my not work properly.
press enter button to continue.
Or, device will power off in 5s.
(written in white)
NOW i tell that it didn't happen after bootloader unlock (so it was unlocked and all good no problem )
but honestly i don't remember if that happened when i tried to upload official rom through Miflash !
Anyway is there any way to remove this? I re installed ( clean install ) official Rom and it's still there, locked bootloader back and it's still there tried some
fastboot oem enable_dm_verity
i'm also warning new user that you might get this msg at boot !
thanks
Click to expand...
Click to collapse
I done everything but my phone doesn't unlock so now I have the dm-verity warning and I can't do a clean flash with Miflash. Also Miflash Unlock doesn't work. What I can do now?
if you can enter in fastboot mode, reflash stock boot and vbmeta
wetito said:
if you can enter in fastboot mode, reflash stock boot and vbmeta
Click to expand...
Click to collapse
How can I do? Miflash says:
error:Writing 'crclist' FAILED (remote: 'not allowed in locked state')
bro you have relock bootloader, this is a fatal error. the only way is try to unlock with an mtk tool that do this via pc. you can find on internet. search unlock all mtk devices. i think there a link also on xda
Just realized that the M3 thread, my phone is a M4.
.
@simika how are you sending this question?
1. Hello friends, there are two ways to fix this problem, first you need Root, I read your Root tutorial, your tutorial is very good, and after using Root, you need to download any file manager, give Root Permissions, you need to backup your baseband, nvram nvdata nvcfg backup and save, you also need an MTK Bypass, you can search for MTK Auth Bypass Tool through Google, you also need to use SP Flash to flash the machine, you need to download the official firmware package, which can be downloaded from xiaomirom.com , download the corresponding version, use SP Flash to read your firmware package, after the reading is completed, choose to format all and download, wait for completion, press the power button after completion, you will find that the error has disappeared, but the baseband is lost, But you have backed up. Boot through fastboot to unlock the BL lock, perform fastboot flash nvram ....... fastboot flash nvdata ....... fastboot flash nvcfg ....... Fastboot reboot reboot. Congratulations The baseband is back, I'm a novice, my instructions are not comprehensive, such as where is the baseband location, but I have too many characters, I will list the baseband location. 2. Replace a new motherboard, all mobile phone problems are all solve.
Hope to help you.
wetito said:
if you can enter in fastboot mode, reflash stock boot and vbmeta
Click to expand...
Click to collapse
Thanks. This worked on my Umidigi A11 phone.
xdadev_user11 said:
Thanks. This worked on my Umidigi A11 phone.
Click to expand...
Click to collapse
nice!
hello i got the same problem today, my phone is redmi9a can some help me regarding to this error ?
i had this problem even though i never unlocked my bootloader so i couldnt flash anything to fix it. but when i got the miui 13 update it fixed it for me
wetito said:
if you can enter in fastboot mode, reflash stock boot and vbmeta
Click to expand...
Click to collapse
What if you cant enter fastboot?