V2056A | PD2056 | 5G China variant
- PD2056B_A_1.11.13 HERE Android 11
thats good!
and how can i flash it?
My device is last week broken . is the rom flashable with fastboot? thx mike
How did you broken the device?
You can simply upload zip on device with adb command and flash by using stock recovery mode
adb push .....
I tried to flash my patched boot.img (via_magisk) with the MTKROOT V2.5.5 tool. -https://www.ayudaroot.com/root/vivo/como-rotear-los-telefonos-vivo-x60-pro-plus . The first problem was unlocking the bootloader. That did not make the tool. The tool failed .. I unlocked that manually in fastboot mode. After the bootloader was open, I tried the tool for the second time.
That was probably the serious mistake! The tool has transferred the patched boot img. So far everything was o. K. Then I booted to the Recovery Menu to clean the data and cache partition. (Factory Reset). Then restart system. Since then I have a bootloop and it was not possible to boot into recovery mode.
Then I flashed from the Indian Rom the boot and the recovery image.
Now the device booted again in Indian Recovery Mode (English). Then I tried to execute the recovery WLAN update. Unfortunately, the system has found no access points when searched.
!! F *** K !!
The next day I tried to flash the original CN-ROM with the QPST flashtool from https://www.needrom.com/download/vivo-x60-pro-plus/ ..
Here I had problems installing the Qualcomm driver for the EDL download mode or to boot the device in the EDL mode.
Without success!
Finally, I tried to flash all the items of the CN-ROM from Needrom via Fastboot. The Flash order of the items I had from the partition.xml file on the CN-ROM.
But I still have a bootloop ..
No access to the recovery WLAN Update-No networks are displayed ..
Do you have an idea for the EDL download mode?
88user88 said:
I tried to flash my patched boot.img (via_magisk) with the MTKROOT V2.5.5 tool. -https://www.ayudaroot.com/root/vivo/como-rotear-los-telefonos-vivo-x60-pro-plus . The first problem was unlocking the bootloader. That did not make the tool. The tool failed .. I unlocked that manually in fastboot mode. After the bootloader was open, I tried the tool for the second time.
That was probably the serious mistake! The tool has transferred the patched boot img. So far everything was o. K. Then I booted to the Recovery Menu to clean the data and cache partition. (Factory Reset). Then restart system. Since then I have a bootloop and it was not possible to boot into recovery mode.
Then I flashed from the Indian Rom the boot and the recovery image.
Now the device booted again in Indian Recovery Mode (English). Then I tried to execute the recovery WLAN update. Unfortunately, the system has found no access points when searched.
!! F *** K !!
The next day I tried to flash the original CN-ROM with the QPST flashtool from https://www.needrom.com/download/vivo-x60-pro-plus/ ..
Here I had problems installing the Qualcomm driver for the EDL download mode or to boot the device in the EDL mode.
Without success!
Finally, I tried to flash all the items of the CN-ROM from Needrom via Fastboot. The Flash order of the items I had from the partition.xml file on the CN-ROM.
But I still have a bootloop ..
No access to the recovery WLAN Update-No networks are displayed ..
Do you have an idea for the EDL download mode?
Click to expand...
Click to collapse
My PC is over adb unautorized, after the Factory reset...
I managed to get this full rom from Recovery, there is a option to download the full last rom and burn. I use another phone with photo google translator to navegate in the menu.
I know this option with the update from the WLAN - but this option is no longer available to me - after the search for a network is completed, no further networks are displayed. He doesn't find any networks.
And the second problem was - I cannot import this Update.zip into the main directory because the PC is unauthorized.
It wasn't just the MTK tool that was wrong.
I think our mistake was you mixed recovery and boot of another Rom. I did that many years ago with Huawei but for me it was a hard brick. Better not mix!
yes i think thatat too. first step now- i try to put the phone in EDL download mode. Then I could try the Qualcomm Flash Tool -. .. But thank you anyway.
with which command did you unlocked the bootloader? I can't find a way.
@88user88 : i wish you the best.
Do you see a way to flash the indian ROM?
Question was not for me but:
I think i have a way that works. But for that I need the command to unlock the bootloader. Because none of the normal ones works.
DPMDP said:
with which command did you unlocked the bootloader? I can't find a way.
Click to expand...
Click to collapse
+1
wolfgart said:
V2056A | PĐ2056 | Biến thể 5G Trung Quốc
- PD2056B_A_1.11.13 TẠI ĐÂY Android 11
Click to expand...
Click to collapse
hello i am a new user in vietnam, can you guide me in detail how to install . Thank you very much
I spent almost 5 hrs yesterday tried to flash from CN ROM, Origin OS to Global ROM, FunTouch OS. I used several methods including AFTool, QFIL, and QPST tool. None of them succeed.
AFTool - failed to flash because missing Fastboot batch file in the global firmware.
QFIL - failed to flash because, Qualcomm Driver 9808 not detected.
QPTS - failed to flash because, Qualcomm Driver 9808 not detected.
I like Origin OS but the reason I want to change to FunTouch OS is because Origin OS didn't come with Google Mobile Seevice package. In fact, 'Hey Google' also didn't worked out.
DPMDP said:
Question was not for me but:
I think i have a way that works. But for that I need the command to unlock the bootloader. Because none of the normal ones works.
Click to expand...
Click to collapse
OK, if we manage to restore my device, I'll give you instructions on how you can unlock your bootloader. then at least I know that in an emergency you also have the option to restore your device.
otherwise it would be too unsafe for me ...
ok?-now you come!
astrofahim said:
I spent almost 5 hrs yesterday tried to flash from CN ROM, Origin OS to Global ROM, FunTouch OS. I used several methods including AFTool, QFIL, and QPST tool. None of them succeed.
AFTool - failed to flash because missing Fastboot batch file in the global firmware.
QFIL - failed to flash because, Qualcomm Driver 9808 not detected.
QPTS - failed to flash because, Qualcomm Driver 9808 not detected.
I like Origin OS but the reason I want to change to FunTouch OS is because Origin OS didn't come with Google Mobile Seevice package. In fact, 'Hey Google' also didn't worked out. YouTube Vanced also always failed to open.
Click to expand...
Click to collapse
same here, my device is iqoo 7 cn origin os i downloaded from android 12 website, failed to upgrade in recovery mode when in hardware check.
both on funtouch os and android 12
Hi, does anyone know where it is I can find this PD2056C_A_1.14.1 firmware
the command menu of the recovery mode of the Chinese version and in Chinese or English
Related
Hi all
Unfortunately, I'm having serious problems with my new Mi8, which arrived yesterday. It arrived with Global ROM and opened Bootloader.
Switch On, set up, data from the Mi6 pulled by NFC, all tutti. the Mi account I have connected here too.
Then I wanted to play the xiaomi.eu. TWRP installed via "Minimal adb and fastboot", installed via TWRP then the xiaomi.eu-ROM (newest). Has also worked. When setting up the point that I can play back via NFC what was not displayed, or I have overlooked him. Okay, again from the beginning, I thought. Have then reset the phone to factory settings to repeat the device.
Then the phone stuck in the bootloop. Again and again the Mi logo appeared and "unlocked", disappeared and came back, disappeared and came back. I did not get into the TWRP anymore, just into the fastboot.
On advice of different users on FB and another forum I should flash the Global ROM again over the MiFlash tool, which I did then also. Unfortunately I carelessly chose "Flash-and-Lock" and closed the boot loader. Unfortunately, this flash did not work and the phone now only starts in recovery mode 3.0
Due to the closed boot loader, it is not possible for me to install TWRP again, to flash another ROM with MiFlashTool. Also, the Unlock tool does not work, because I get the error message that the device is not linked to my account. I have also tried to install a recovery mod on the Xiaomi PC suite, as the bar remains on the PC but at 0%, on the phone remains the image with the pictured Mi8, after I in the recovery menu "Connect with MiAssistent "selected. Otherwise nothing happens.
With the latest version of the PC suite flashing works, but still boots the box in the recovery mode and the red font remains. Another user in the other forum said that I need the CN version, because on the CN device no EU-Rome is allowed. The CN version is rejected by the PC suite not get verified.
What else can I do. Do you have an idea that helps me getting the phone back on track?
This, for me, is the biggest joke of Xiaomi! Many users are getting stuck in this new policy! That does not exist! A total lack of respect for brand lovers. Let the developers figure out how to reverse this.
try CN Dev version, is latest and best,
forget xiaomi.eu rom lol, almost all they do you can do by yourself within minutes, uninstalling few chinese apps and get google works with googleinstaller_v3. and dev rom have root. just suggestion.
I tried the last cn-version, but the pc-suite dont verify this ROM and dont flash it.
Rantanplan12345 said:
I tried the last cn-version, but the pc-suite dont verify this ROM and dont flash it.
Click to expand...
Click to collapse
use mi flasher
This is Mi 8 thread not Mi 6.
altvolt74 said:
use mi flasher
Click to expand...
Click to collapse
Miflasher dont work, because the bootloader is locked.
To OP and the issue at hand, have you tried the fastboot image to install chinese stable or developer rom? That should flash and allow you to unlock bootloader again.
To the people whining about this policy of Xiaomi, you are buying a product for a different market. There is nothing wrong with their policy and you should wait for global version of the phone if you want global image with locked bootloader. It's a little like complaining that the chinese MMO you play over vpn doesn't have english menus. Well no, it's not for that market.
Superbia said:
To OP and the issue at hand, have you tried the fastboot image to install chinese stable or developer rom? That should flash and allow you to unlock bootloader again.
Click to expand...
Click to collapse
I tried only the chinese recovery rom for flashing with the pc-suite. The fastboot image, I can only flash with twrp or miflashtool, right? TWRP dont work, I cant boot in it. And miflashtool says, as I tried to flash the global rom, that it isnt allowed to erase a locked device.
Rantanplan12345 said:
I tried only the chinese recovery rom for flashing with the pc-suite. The fastboot image, I can only flash with twrp or miflashtool, right? TWRP dont work, I cant boot in it. And miflashtool says, as I tried to flash the global rom, that it isnt allowed to erase a locked device.
Click to expand...
Click to collapse
Nah, the fastboot image flashes best in my experience if you unpack it, all the way. You will get some folders and .bat files. make sure you have fastboot in either PATH or same directory make sure fastboot detects the image and after that run the flash_all.bat and it should flash it.
Superbia said:
Nah, the fastboot image flashes best in my experience if you unpack it, all the way. You will get some folders and .bat files. make sure you have fastboot in either PATH or same directory make sure fastboot detects the image and after that run the flash_all.bat and it should flash it.
Click to expand...
Click to collapse
That dont work, because the bootloader is locked. Fastboot says too, that it isnt allowed because the lock, same when I try to install twrp on the locked phone.
Rantanplan12345 said:
That dont work, because the bootloader is locked. Fastboot says too, that it isnt allowed because the lock, same when I try to install twrp on the locked phone.
Click to expand...
Click to collapse
Hmm you tried "fastboot oem unlock" also right?
Yes, I tried. Result in a failef, I remember.
Token verify failed
Hi. Well I speak Spanish and I used the Google translator.
Well here is my dilemma. I had my Mi A2 with Miui 10, root and twrp. I download from xiaomi.eu la rom 10.3.14 for Mi6x and the i try to falsh but i didn't delete the folder firmware update. (I do not know if it matters) when I power on the phone remains in boot loop. I did not have access to the recovery or twrp. (vol + + pwr) only to fastboot mode. The Mi Flash program error with the original rom of Mia2 (android one) and the rom mi6x (miui 10). And touching blocking the bootloader. From there I see "the system has been destroyed ...". from that moment I did everything. Test point edl and Mi flash recognize as COM# but the flash error. I tried with the screen in fastboot also skips error. flash rom Mi a2 and mi6x. I try directly from the .bat but close immediately. xiaomi my unlock does not work. I do not know what else to do. I have installed all the usb drivers and nothing. I try with 3 pc's. really the one with the solution is a God.
Have you tried flashing the ROM manually (not with Miflash) from fastboot?
willy899 said:
Hi. Well I speak Spanish and I used the Google translator.
Well here is my dilemma. I had my Mi A2 with Miui 10, root and twrp. I download from xiaomi.eu la rom 10.3.14 for Mi6x and the i try to falsh but i didn't delete the folder firmware update. (I do not know if it matters) when I power on the phone remains in boot loop. I did not have access to the recovery or twrp. (vol + + pwr) only to fastboot mode. The Mi Flash program error with the original rom of Mia2 (android one) and the rom mi6x (miui 10). And touching blocking the bootloader. From there I see "the system has been destroyed ...". from that moment I did everything. Test point edl and Mi flash recognize as COM# but the flash error. I tried with the screen in fastboot also skips error. flash rom Mi a2 and mi6x. I try directly from the .bat but close immediately. xiaomi my unlock does not work. I do not know what else to do. I have installed all the usb drivers and nothing. I try with 3 pc's. really the one with the solution is a God.
Click to expand...
Click to collapse
did you know that this latest beta version of miui 9.3.14 needs to install the hex ne kernel as well? because the default kernel of the loop at boot
cmarcom said:
Have you tried flashing the ROM manually (not with Miflash) from fastboot?
Click to expand...
Click to collapse
Yes. With the .bat but didn't work. The cad Windows close quickly.
Rickk18244001 said:
did you know that this latest beta version of miui 9.3.14 needs to install the hex ne kernel as well? because the default kernel of the loop at boot
Click to expand...
Click to collapse
I really do not know. I followed the steps. and flash the .zip with twrp. zero error and on the turn on was left in boot loop and does not enter recovery or twrp.
this the link the rom: xiaomi.eu/community/threads/9-3-14.49609
willy899 said:
I really do not know. I followed the steps. and flash the .zip with twrp. zero error and on the turn on was left in boot loop and does not enter recovery or twrp.
this the link the rom: xiaomi.eu/community/threads/9-3-14.49609
Click to expand...
Click to collapse
Flash Hex or RA kernel.
willy899 said:
Yes. With the .bat but didn't work. The cad Windows close quickly.
Click to expand...
Click to collapse
thats because the fastboot is not in the same folder as the .bat, and you hast to flash hex v288 for wayne in order to 9.3.14 to boot.
I used Havoc rom
Connect phone to pc in fastboot
In cmd:
Fastboot -w
Fastboot set_active b
And boot twrp
Flash rom, flash twrp and switch partition to A
Forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Hi, today I tried using the Realme Flash tool for X2 Pro but it bricked my phone. Based on the flash tools error logs it shows this
"~~Medium~~ UnZipFloHelper Delete temp file exception:The process cannot access the file 'C:\Users\Michael\AppData\Roaming\realmeFlashTools\temp\system.img' because it is being used by another process."
seems like a windows problem but I cant find any reference on the web. I tried restarting my PC but it didn't solve my problem.Any suggestions how to fix this? thank you!
Realme flash tool decrypt and extract the ofp to C:\Users\Michael\AppData\Roaming\realmeFlashTools \temp .This seem to be windows permission issue .
Try to run as administer the realme flash tool and try again. Also you can flash unpacked ozip trough fastboot manually, It will be very similar to flashing with realme flash tool .
or965 said:
Realme flash tool decrypt and extract the ofp to C:\Users\Michael\AppData\Roaming\realmeFlashTools \temp .This seem to be windows permission issue .
Try to run as administer the realme flash tool and try again. Also you can flash unpacked ozip trough fastboot manually, It will be very similar to flashing with realme flash tool .
Click to expand...
Click to collapse
Thank you it worked! I tried run as admin the flash tool and deleted .IMG file it also seems that an Virtual image program is holding to it so I disabled it.
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Rinku390 said:
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Click to expand...
Click to collapse
Hi, ( if your problem is not resolved at this time )
If you want you can try this procedure
Enter fastboot
- don't know if a fastboot erase " boot + system + vendor" can help
Flash stock recovery
Enter recovery and format data
Reboot bootloader
Flash full stock rom ~5Gb ( not the OTA ~3GB) with the realme flash tool
LoVerMaKi said:
Hi, ( if your problem is not resolved at this time )
If you want you can try this procedure
Enter fastboot
- don't know if a fastboot erase " boot + system + vendor" can help
Flash stock recovery
Enter recovery and format data
Reboot bootloader
Flash full stock rom ~5Gb ( not the OTA ~3GB) with the realme flash tool
Click to expand...
Click to collapse
i have a same problem here. but i cant flash stock rom on fastboot flashing img files will loop back into bootloader and realme flash tool says "CANNOT FIND CENTRAL DIRECTORY" PLEASE HELP ME
Rinku390 said:
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Click to expand...
Click to collapse
i have a same problem here. but i cant flash stock rom on fastboot flashing img files will loop back into bootloader and realme flash tool says "CANNOT FIND CENTRAL DIRECTORY" PLEASE HELP ME
Rinku390 said:
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Click to expand...
Click to collapse
did you fix your phone?
i am at same problem here please please please answer me.
please share the procedur to fix if you have fixed
PETER.PARKER said:
i have a same problem here. but i cant flash stock rom on fastboot flashing img files will loop back into bootloader and realme flash tool says "CANNOT FIND CENTRAL DIRECTORY" PLEASE HELP ME
Click to expand...
Click to collapse
Hi,
Flashtool says some error that not relevant. If the rom is not adaptable for the phone, the error msg is not really clear.
Here is some link. I cant help you more.
You need to dl the c27.ofc (full stock rom).
rom and flash tool
ofc extractor
Option 1 try flash the c27 with flashtool.
Option 2
. Extract the ofc with MCT OFP Extractor .boot in flashboot and flash the boot/recovery (maybe try all img one by one if it pass) i use google for the correct syntax for each img file
. try boot in recovery et format data
. Reboot in fastboot and reflash the ofc with flashtool
You need to experiment to find the correct proces for your problem.
Hf gl
LoVerMaKi said:
Hi,
Flashtool says some error that not relevant. If the rom is not adaptable for the phone, the error msg is not really clear.
Here is some link. I cant help you more.
You need to dl the c27.ofc (full stock rom).
rom and flash tool
ofc extractor
Option 1 try flash the c27 with flashtool.
Option 2
. Extract the ofc with MCT OFP Extractor .boot in flashboot and flash the boot/recovery (maybe try all img one by one if it pass) i use google for the correct syntax for each img file
. try boot in recovery et format data
. Reboot in fastboot and reflash the ofc with flashtool
You need to experiment to find the correct proces for your problem.
Hf gl
Click to expand...
Click to collapse
I downloaded and flashed that c27 rom with realme flash tool it successfully completed the flashing process but nothing new it loops back into bootloader im literally pissed rigt now
Detail info about my problem "https://forum.xda-developers.com/t/...evice-state-unlocked-secure-boot-yes.4330817/"
Rinku390 said:
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Click to expand...
Click to collapse
i am facing same problem,is your problem resolved ,please help
JKD23 said:
Thank you it worked! I tried run as admin the flash tool and deleted .IMG file it also seems that an Virtual image program is holding to it so I disabled it.
Click to expand...
Click to collapse
Please tell me how you did?
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...