Related
Hi guys
Sorry for my bad English
My device was running Android 10
miui 11
After I accidentally used an application to raise the screen frequency to 84Hz
The devics did a reboot and then stopped on the fastboot logo
I tried to enter recovery mode but was back to fastboot mode
I tried to flash twrp via adb and fastboot but the method did not work and the device returned to fastboot mode
Finally I downloaded the ROM file global Version Android 9
miui 11 and when i flashed the system via "xiaomi flash tool " the operation was successful until it reached the end of the process it showed me an error and the flash failed
I restarted the process and noticed that the flashing process gives me the error when the download arrives at "flashing boot"
I searched a lot for the version of Android 10 miui 11 but I did not find
What is the problem!
Can anyone explain what the problem is?
Thank you very much
Edit : solved With the help of my friend and brother @tsongming thanks bro
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
tsongming said:
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
Click to expand...
Click to collapse
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
ahmadbasher said:
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
Click to expand...
Click to collapse
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
tsongming said:
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
Click to expand...
Click to collapse
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
ahmadbasher said:
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
Click to expand...
Click to collapse
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
thanks for replay bro i will tri it
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
I tri it and no change
Again reboot to fastboot
ahmadbasher said:
I tri it and no change
Again reboot to fastboot
Click to expand...
Click to collapse
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
tsongming said:
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
Click to expand...
Click to collapse
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me ? But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Is it possible that this is part of the problem..!
I can't check it
@tsongming
ahmadbasher said:
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Click to expand...
Click to collapse
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
ahmadbasher said:
Is it possible that this is part of the problem..!
I can't check it
@tsongming
Click to expand...
Click to collapse
No that is just encryption, if the issue was related to encryption the flashall.bat method would have resolved it.
If you had a persist issue, you would see specific messages about not being able to mount the persist partition.
tsongming said:
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
Click to expand...
Click to collapse
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
ahmadbasher said:
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
Click to expand...
Click to collapse
Hey sorry for the delay in getting back to you, I sent you the link for the file via PM.
Also, I would strongly suggest using the stock miui initially. Just until you know it's resolved. Also while Miui is installed make a full TWRP backup and save it to your desktop. This way you always have a full backup to resolve any serious issues.
Then once you know everything is working as it should then go back to what you prefer..
For the record this issue was solved. Anyone reading this, make sure that you have a full working TWRP backup of your working device, it will save you a lot of headaches. The solution for the refresh rate is issue is restoring stock DTBO, and then flashing Miui Stock.
My first post, after some modding (and soft bricking too:silly My recovery doesn't work anymore (Touch not working, twrp 3.1.1-1) I want to flash stock miui 11 global with miFlash but it gives me the Flash vendor_ab error. What I have to do? or maybe u have a method to solve my recovery. Fastboot works, bootloader unlocked. Let me know if u need logs. Thanks, at the moment I have no working phone.
xD_Lol said:
My first post, after some modding (and soft bricking too:silly My recovery doesn't work anymore (Touch not working, twrp 3.1.1-1) I want to flash stock miui 11 global with miFlash but it gives me the Flash vendor_ab error. What I have to do? or maybe u have a method to solve my recovery. Fastboot works, bootloader unlocked. Let me know if u need logs. Thanks, at the moment I have no working phone.
Click to expand...
Click to collapse
Hey brother @tsongming May be you can help him
[emoji1191]
xD_Lol said:
My first post, after some modding (and soft bricking too:silly My recovery doesn't work anymore (Touch not working, twrp 3.1.1-1) I want to flash stock miui 11 global with miFlash but it gives me the Flash vendor_ab error. What I have to do? or maybe u have a method to solve my recovery. Fastboot works, bootloader unlocked. Let me know if u need logs. Thanks, at the moment I have no working phone.
Click to expand...
Click to collapse
Be sure that you are using Fastboot rom , and not a recovery rom.
Make sure that your ADB and drivers are up to date, and finally you may be experiencing the driver issue issue that a lot of people with Ryzen processors experience. I had the same issue on my Intel neon processors. This can be fixed by flash the batch file from here : https://forum.xda-developers.com/showpost.php?p=82607121&postcount=25
Unpack the fastboot file twice on your desktop and then combined with the batch file it should flash.
I saw this was out and was curious if anyone had tried installing and flashing their ROM. Didn't want to start the process of it's not awesome like their other rom builds or buggy... Didn't see any other posts on it. thoughts?
I have. I download the ROM and ran the windows update script. Everything installs fine with no error. However, when it reboots, it boots back up to fastboot. Waiting to see if there's a solution to it. I'm about to try and flash using linux to see it that works. Maybe the windows script has some errors or typos? Who knows
Edit: Just intalled in Linux using the included linux script. Installed and booted up to Android just fine. I believe the windows script has some errors. I'll be testing the EU Rom to see how it runs.
hectordc5 said:
I have. I download the ROM and ran the windows update script. Everything installs fine with no error. However, when it reboots, it boots back up to fastboot. Waiting to see if there's a solution to it. I'm about to try and flash using linux to see it that works. Maybe the windows script has some errors or typos? Who knows
Edit: Just intalled in Linux using the included linux script. Installed and booted up to Android just fine. I believe the windows script has some errors. I'll be testing the EU Rom to see how it runs.
Click to expand...
Click to collapse
Hello,anny issues you found till now? Is there b20? All Google services working? And all language support?
Thank you and sorry for all these questions
Jinthegodstyle said:
Hello,anny issues you found till now? Is there b20? All Google services working? And all language support?
Thank you and sorry for all these questions
Click to expand...
Click to collapse
No issues so far. Everything is running smooth.
I live in the U.S. and it works fine on 5G bands over here. There's no way to check which bands are available on Qualcomm devices, unless QPST or QXDM is used, even then it's tricky since the values shown are bit-based.
All google services are working.
All languages supported that are stated in the Xiaomi EU Rom
hectordc5 said:
No issues so far. Everything is running smooth.
I live in the U.S. and it works fine on 5G bands over here. There's no way to check which bands are available on Qualcomm devices, unless QPST or QXDM is used, even then it's tricky since the values shown are bit-based.
All google services are working.
All languages supported that are stated in the Xiaomi EU Rom
Click to expand...
Click to collapse
Many thanks for your feedback! Tomorrow I'll give a try to flash threw windows hope I'll be lucky to don't have same issues like you had..
Mine failed to fastboot too but not having any linux PCs, I've not managed to try it. I gave it a go with Linux on windows and even Ubuntu on windows but everytime i tried with the Linux script it only got to the y/n part and went no further. May be someone with more linux experience could assist here?
The windows install fails at one part of the flash saying there is no destination folder or partition ( i think) at storsec.mbm.
Currently flashing stock again and hoping the error is fixed soon.
Sathelp said:
Mine failed to fastboot too but not having any linux PCs, I've not managed to try it. I gave it a go with Linux on windows and even Ubuntu on windows but everytime i tried with the Linux script it only got to the y/n part and went no further. May be someone with more linux experience could assist here?
The windows install fails at one part of the flash saying there is no destination folder or partition ( i think) at storsec.mbm.
Currently flashing stock again and hoping the error is fixed soon.
Click to expand...
Click to collapse
You most likely have to install ADB and fastboot drivers.
Open up terminal.
run
Code:
sudo apt-get update
Then, run
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Once installed, run
Code:
sudo adb start-server
After, connect your phone to your PC. Make sure your phone is in fastboot mode.
Then, run
Code:
adb devices
to verify your device shows up.
After, go to your directory in terminal using
Code:
cd
Example:
Code:
cd Downloads/<folder name> (without <>)
and run the script.
Does anyone have a working instant boot loader unlock for the mi 10 ultra, or have u guys all waited your time period?
pcxnet said:
Does anyone have a working instant boot loader unlock for the mi 10 ultra, or have u guys all waited your time period?
Click to expand...
Click to collapse
It's only a week. I've seen no way to cheat it. Maybe something obscure back when I got my Mi 9. But do start the process, it will only help you
Did it work for anyone using windows, what are the implications of unlocking the bootloader?
ToneLa said:
It's only a week. I've seen no way to cheat it. Maybe something obscure back when I got my Mi 9. But do start the process, it will only help you
Click to expand...
Click to collapse
so just real quick: Unlocking the bootloader is use the miflash_unlock right? Do I need to toggle on "OEM unlocking" in developers mode? I don't wanna wait a week just to realize I need to have that already checked beforehand.
ultimatepichu said:
so just real quick: Unlocking the bootloader is use the miflash_unlock right? Do I need to toggle on "OEM unlocking" in developers mode? I don't wanna wait a week just to realize I need to have that already checked beforehand.
Click to expand...
Click to collapse
The countdown only starts from when the Mi Unlock app on your computer has had the Unlock button pressed. It even warns you you're going to wipe your device but it'll stop short and tell you how long is left.
In a nutshell yes you'll want to enable dev options and switch on OEM unlocking. Two down from that is Mi Unlock Status which gives you the link to download the unlock tool.
As i understand there is a problem with formating data on the script for windows?
If i will format data from recovery with twrp and then boot to fastboot and run the script,may that work?
Here's a neat guide:
https://xiaomi.eu/community/threads/guide-how-to-install-xiaomi-eu-rom-for-xiaomi-mi10-ultra.57259/
I've only JUST unlocked so not done anything myself yet. The Windows script seems broke, I might wait...
I tried Windows and it didn't work
However there is a fix!... you flash the super.img on its own when it's at the second, post-flash stuck flashboot stage
Easier way perhaps? just copied then edited the batch file, and removed anything that wasn't the line for super.img (er, do keep the header and footer if you do this), so a batch file of just:
Code:
@echo off
cd %~dp0
platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *cas" || echo Missmatching image and device
platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *cas" || exit /B 1
platform-tools-windows\fastboot %* flash super firmware-update/super.img
platform-tools-windows\fastboot %* reboot
Which will flash the super.img and reboot at the end of it and here I am in a nice new ROM
The guy who found this on the Xiaomi.eu forums mentioned using "another fastboot.exe", I asked him what he means. I did use one left behind from my Mi9 tinkering but honestly not sure if required?
Cannot do anything with this flash!
I tried also this fix new fastboot file but nothing..
Tried to install with linux by ubuntu and virtual box but having the message that no images and device (even if its reading the device on adb command)
Any idea,need to format data,to repair data,cache to f2fs?Dunno what else to do with this!
If you cant get it flashed, what I did yesterday was to download this stable ROM from here: http://bigota.d.miui.com/V12.0.8.0.QJJCNXM/cas_images_V12.0.8.0.QJJCNXM_20200823.0000.00_10.0_cn_8c57a38882.tgz and use the all in one tool from here: https://sourceforge.net/projects/tool-all-in-one/
You can then flash that downloaded ROM using the Flash Factory Images tool to recover. then download the latest update once back in use. But by changing the fastboot tool from another package, and moving the super image to the last flash within the bat file I managed to get it loaded OK. Took a few attempts, it should never be this hard to flash a phone.
Sathelp said:
If you cant get it flashed, what I did yesterday was to download this stable ROM from here: http://bigota.d.miui.com/V12.0.8.0.QJJCNXM/cas_images_V12.0.8.0.QJJCNXM_20200823.0000.00_10.0_cn_8c57a38882.tgz and use the all in one tool from here: https://sourceforge.net/projects/tool-all-in-one/
You can then flash that downloaded ROM using the Flash Factory Images tool to recover. then download the latest update once back in use. But by changing the fastboot tool from another package, and moving the super image to the last flash within the bat file I managed to get it loaded OK. Took a few attempts, it should never be this hard to flash a phone.
Click to expand...
Click to collapse
So as i understand i flash the rom,i boot,then i reboot on fastboot mode and there i choose flash factory image and choose the zip file that miui eu rom has provided?
Jinthegodstyle said:
So as i understand i flash the rom,i boot,then i reboot on fastboot mode and there i choose flash factory image and choose the zip file that miui eu rom has provided?
Click to expand...
Click to collapse
If you just want to give up flashing to the EU Rom until it is a bit more stable, the follow my link to download a Stable stock ROM and when in Fastboot, flash using the flashing tool in the all-in-one-tool. This will recover you to where you were when you bought the phone. There is one update that has the August security patches in, not much else to down load later.
If you want to try the EU ROM flashing for a while, then what I did was to edit the bat file and put the super.img line at the bottom of the list. I also used another version of Fastboot and copied it in to the platform_tools folder (only as someone has already said that another Fastboot version seemed to fix it) and then flash again. It then worked for me, so there is hope but if you just get fed up today and want to go back to using your phone, Flash the stock ROM using the tool from Phone in Fastboot mode.
Sathelp said:
If you just want to give up flashing to the EU Rom until it is a bit more stable, the follow my link to download a Stable stock ROM and when in Fastboot, flash using the flashing tool in the all-in-one-tool. This will recover you to where you were when you bought the phone. There is one update that has the August security patches in, not much else to down load later.
If you want to try the EU ROM flashing for a while, then what I did was to edit the bat file and put the super.img line at the bottom of the list. I also used another version of Fastboot and copied it in to the platform_tools folder (only as someone has already said that another Fastboot version seemed to fix it) and then flash again. It then worked for me, so there is hope but if you just get fed up today and want to go back to using your phone, Flash the stock ROM using the tool from Phone in Fastboot mode.
Click to expand...
Click to collapse
i managed finally to bring phone back to life installng threw twrp,twrp recovery rom. I want to try and install the eu rom again.
Can you share the fastboot you used? I will edit the bat file,the super.img need to be before the -w line right?
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?
Ayo,
i got a new N10Pro EEA and tried to update it to the latest official ROM to play a bit with it.
Bootloader is unlocked since yesterday, and i tried to download the 13.0.15 and 13.0.16 from different sites. Checked CRCs and all are good.
Unpacked the TGZ file and added the necessary fastboot.exe and files. (Did it this way a lot of Redmi Note 8T times... )
Got the device in fastboot mode, connected it and started the flash_all.bat
It goes through until it tries to flash part 7 of the super image, then it fails with a CRC error.
It does this on either the EEA version (13.0.16) and the global (13.0.15), and i've checked repeatedly that my files are ok and i'm positive they are.
I edited the super line out of the file and all the others go through flawlessly, but now my device just bootloops because the most of data is corrupt of course.
What did i do wrong?
I just had a SIM in there, registered the Mi account (i used it for all my RN8Ts), unlocked it with a week wait and nothing more.
No Wifi, no other accounts, just the minimum necessary to unlock it, then tried to flash....
flashernoob said:
Ayo,
i got a new N10Pro EEA and tried to update it to the latest official ROM to play a bit with it.
Bootloader is unlocked since yesterday, and i tried to download the 13.0.15 and 13.0.16 from different sites. Checked CRCs and all are good.
Unpacked the TGZ file and added the necessary fastboot.exe and files. (Did it this way a lot of Redmi Note 8T times... )
Got the device in fastboot mode, connected it and started the flash_all.bat
It goes through until it tries to flash part 7 of the super image, then it fails with a CRC error.
It does this on either the EEA version (13.0.16) and the global (13.0.15), and i've checked repeatedly that my files are ok and i'm positive they are.
I edited the super line out of the file and all the others go through flawlessly, but now my device just bootloops because the most of data is corrupt of course.
What did i do wrong?
I just had a SIM in there, registered the Mi account (i used it for all my RN8Ts), unlocked it with a week wait and nothing more.
No Wifi, no other accounts, just the minimum necessary to unlock it, then tried to flash....
Click to expand...
Click to collapse
Developer options USB debugging is activated?
Search for flashing instructions in this forum for your preferred ROM and it's easier to flash Roms, in my opinion, with orange fox recovery (or TWRP)
Can't and won't activate USB debugging as phone is softbrick now. Didn't need to on my RN8Ts, either.
The ROM is Xiaomi stock, flashing instructions are "unpack tgz, connect phone in fastboot mode, start flash_all.bat", which is what i did (as with all the RN8Ts i have)
TWRP it is the next step, but first i need it to work with the latest official ROM...
I'd prefer OFox but i think there is no version for Android 12/MIUI 13. The beta has V11 in the name so it's for Android11, not?
flashernoob said:
Can't and won't activate USB debugging as phone is softbrick now. Didn't need to on my RN8Ts, either.
The ROM is Xiaomi stock, flashing instructions are "unpack tgz, connect phone in fastboot mode, start flash_all.bat", which is what i did (as with all the RN8Ts i have)
TWRP it is the next step, but first i need it to work with the latest official ROM...
I'd prefer OFox but i think there is no version for Android 12/MIUI 13. The beta has V11 in the name so it's for Android11, not?
Click to expand...
Click to collapse
Perhaps you find here ideas
[Solved] Fastboot flash super error - FAILED (remote: 'failed to check sparse crc')
Hi, I'm getting an error trying to install stock rom from xiaomirom.com via fastboot. D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea>fastboot flash super...
forum.xda-developers.com
The Complete Guide to Flashing Factory Images on Android Using Fastboot
If your phone has an unlocked bootloader, you can use Fastboot commands to flash factory images. That may sound like a bunch of technical jargon, but when it comes down to it, this is the best method for updating a rooted device, fixing a bricked phone, reverting to stock, or even getting new...
android.gadgethacks.com
Thank you very much, your first link had a hint on the solution, thanks a lot!
I used the latest google/android fastboot 33.0.3, but tried another as to the thread posted, and the years old fastboot 1.4.3 from https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/#post-42407269 did the trick!
Never would i have thought that a 4 year old hack would work better than the latest official google file....
flashernoob said:
Ayo,
i got a new N10Pro EEA and tried to update it to the latest official ROM to play a bit with it.
Bootloader is unlocked since yesterday, and i tried to download the 13.0.15 and 13.0.16 from different sites. Checked CRCs and all are good.
Unpacked the TGZ file and added the necessary fastboot.exe and files. (Did it this way a lot of Redmi Note 8T times... )
Got the device in fastboot mode, connected it and started the flash_all.bat
It goes through until it tries to flash part 7 of the super image, then it fails with a CRC error.
It does this on either the EEA version (13.0.16) and the global (13.0.15), and i've checked repeatedly that my files are ok and i'm positive they are.
I edited the super line out of the file and all the others go through flawlessly, but now my device just bootloops because the most of data is corrupt of course.
What did i do wrong?
I just had a SIM in there, registered the Mi account (i used it for all my RN8Ts), unlocked it with a week wait and nothing more.
No Wifi, no other accounts, just the minimum necessary to unlock it, then tried to flash....
Click to expand...
Click to collapse
I solved my soft brick using the 13 image files on my RN11. This got me out of a perpetual fastboot loop. (It should also work on the RN10P)
i.e. fastboot flash boot boot.img, fastboot flash super super.img etc for all 13 images.
I tried the flash_all.bat several times but it just kept borking at different spots and I needed to get out of that fastboot loop hell.
The flash_all bat works like a charm for me, there's no sense in typing all the lines one for one.
The exe seems to bork at the size of the super image, the RN8 hadn't such a thing, the RN10 has a 7G file the exe couldn't stand, obviously.
At least it did CRC error repeatedly, with different ROMs, all at the 7 of 10 or 7 of 11 stage...