Question CRC Error on flashing via Fastboot - Redmi Note 10 Pro

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...

Related

phone bricked

Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
oudric said:
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
Click to expand...
Click to collapse
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
internetpilot said:
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
Click to expand...
Click to collapse
can you please tell me steps i am so afraid to do anything to my phone now and i think my problem is same as yours
i downloaded 6.0.0 (MRA58R) and i used option in toolkit flash stock it gave me an error
"failed (data transfer failure (unknown error))
Its not so easy to brick nexus, but make sure you don't lock bootloader before your phone is working right. You can find the guide how to flash it on XDA.
You will need to flash the missing files by hand.
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
oudric said:
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
Click to expand...
Click to collapse
You don't need to move the files to the platform-tools folder.
Go to Nexus 6 General > Sticky rol-up thread > Adb and fastboot. What is it?
This will tell you how to set up and use adb or fastboot properly.

Big problems after bootloop

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

Mi 9 won't boot into Android

Alright lets start... I bought Mi 9 about 2 months. I just like to work with phones and mess up with Roms, recoverys, etc. I started it about 4-5 years ago with Samsung Galaxy Trend Plus. When i lost that phone i bought HTC M8 and also do the same (mess up with software). With Mi 9 i couldnt wait for Miui11 and tried to install it via Twrp. Unlocked bootloader installed Twrp via Fastboot, and every time when i restarted phone Miui stock recovery would overwrite Twrp. I searched everywhere and found some "solution". It was when you install Twrp via fastboot you need to write Fastboot boot Twrp.img, something like that im not really sure. Well that worked, kindof. Twrp would always appear but it cant boot into Android. And like always i tried to to solve it myself but i cant for two days of working without stopping i cant solve this. I tried to install different Rom (Miui 11 all versions) and it would install but wont boot. I tried Stock Miui Rom, i tried Factory img almost everything. Tried with adb, Miflash tool, All in one tool for Mi 9. I really love this phone i worked every day on summer for this phone. Thanks. If someone read this and want to help for more information just ask.
MadTractorist said:
Alright lets start... I bought Mi 9 about 2 months. I just like to work with phones and mess up with Roms, recoverys, etc. I started it about 4-5 years ago with Samsung Galaxy Trend Plus. When i lost that phone i bought HTC M8 and also do the same (mess up with software). With Mi 9 i couldnt wait for Miui11 and tried to install it via Twrp. Unlocked bootloader installed Twrp via Fastboot, and every time when i restarted phone Miui stock recovery would overwrite Twrp. I searched everywhere and found some "solution". It was when you install Twrp via fastboot you need to write Fastboot boot Twrp.img, something like that im not really sure. Well that worked, kindof. Twrp would always appear but it cant boot into Android. And like always i tried to to solve it myself but i cant for two days of working without stopping i cant solve this. I tried to install different Rom (Miui 11 all versions) and it would install but wont boot. I tried Stock Miui Rom, i tried Factory img almost everything. Tried with adb, Miflash tool, All in one tool for Mi 9. I really love this phone i worked every day on summer for this phone. Thanks. If someone read this and want to help for more information just ask.
Click to expand...
Click to collapse
First of all
It's wrong froum
Format data always needed after to flashed new rom
And you did try to flash vbmeta.img ?
MadTractorist said:
Alright lets start... I bought Mi 9 about 2 months. I just like to work with phones and mess up with Roms, recoverys, etc. I started it about 4-5 years ago with Samsung Galaxy Trend Plus. When i lost that phone i bought HTC M8 and also do the same (mess up with software). With Mi 9 i couldnt wait for Miui11 and tried to install it via Twrp. Unlocked bootloader installed Twrp via Fastboot, and every time when i restarted phone Miui stock recovery would overwrite Twrp. I searched everywhere and found some "solution". It was when you install Twrp via fastboot you need to write Fastboot boot Twrp.img, something like that im not really sure. Well that worked, kindof. Twrp would always appear but it cant boot into Android. And like always i tried to to solve it myself but i cant for two days of working without stopping i cant solve this. I tried to install different Rom (Miui 11 all versions) and it would install but wont boot. I tried Stock Miui Rom, i tried Factory img almost everything. Tried with adb, Miflash tool, All in one tool for Mi 9. I really love this phone i worked every day on summer for this phone. Thanks. If someone read this and want to help for more information just ask.
Click to expand...
Click to collapse
You need Miflash pro. Search for it. Sounds like you have some kind of recovery bootloop. If you can get your Mi9 to the fastboot (bootloader) screen then you can fix your cell an get it to boot . Trust me on this. I must of made flashing errors with my Mi9 maybe 20 times an got stuck in a fastboot loop.
Heres a link https://androidmtk.com/use-mi-flash-pro-download-xiaomi-firmware
Follow the guides an you should have a working Mi9 in under 20 minutes.
Sometimes there can be trouble getting the latest version of Miflash pro an it requires a bit of tinkering to flash with it.
Not sure that this would help but here is what I did to install Xiaomi.EU ROM in my Mi 9. I followed the guide from this forum here.
Prerequisite:
Download TWRP 3.3.1-42 for Cepheus from Mauronofrio here
Download Xiaomi.EU ROM here
Rename both files to twrp.img & rom.zip respectively (for easy typing later)
Steps:
Power off phone
Boot phone to fastboot - Vol Down + Power
type "fastboot flash recovery twrp.img" without the double quotes
Power off phone
Boot phone to recovery - Vol Up + Power
Type "adb push rom.zip /tmp/" without the double quotes
In TWRP, go to Wipe-Format Data-type yes in TWRP
Then perform a Factory Reset in TWRP
Then flash ROM located in tmp
And finally reboot to system
I hope this helps.
fereidooni said:
First of all
It's wrong froum
Format data always needed after to flashed new rom
And you did try to flash vbmeta.img ?
Click to expand...
Click to collapse
Maybe this guys new man?

How to check if MIUI flashed by MiFlash is legit?

Hi, yesterday I unlocked bootloader in my phone and flashed a custom ROM but I decided that I want to go back to stock and have locked bootloader. I downloaded MiFlash tool and 10.0.3.0 image from here: http//)c(.)mi(.)com/oc/miuidownload/detail?guide=2
First thing that struck me was that the tool isn't signed, the producer is unknown in the UAC popup. The ROM was suspicious as well, its MD5 hash (only part of it) was in the filename, which is just stupid. I decided that I want to use this tool and flash the ROM anyway. I connected my phone (which was in fastboot mode) to USB 3.0 port in my PC and ran the tool. It got up to flashing system image, but then I got an error "Failed system flash". I noticed that the bootloader got locked, but the MiFlash Unlock tool told me that the device is already unlocked. I tried to boot to TWRP but, well, the bootloader was locked. I thought I hard bricked my phone, but then I decided to connect it to USB 2.0 port. To my surprise, the whole flashing progress was successful and I got no errors. It was suspicious for me, I thought that the first error was on purpose, to replace boot image to allow installation of rogue ROMs with locked bootloader. I know it's kinda paranoic, but I don't trust these Chinese tools at all. Also, I compared old boot image (backed up with TWRP) with new one, and their hashes were different. When the phone booted, I successfully updated MIUI to version 11.0.4.0 (it's the latest MIUI available in Poland), so it seems for me that it's legit. I'm attaching some screenshots from settings: https//)imgur(.)com/a/894o9qU. So, what's the best way to determine if the system is 100% legit and I'm not running some fake ROM with hidden malware?
knur2172 said:
Hi, yesterday I unlocked bootloader in my phone and flashed a custom ROM but I decided that I want to go back to stock and have locked bootloader. I downloaded MiFlash tool and 10.0.3.0 image from here: http//)c(.)mi(.)com/oc/miuidownload/detail?guide=2
First thing that struck me was that the tool isn't signed, the producer is unknown in the UAC popup. The ROM was suspicious as well, its MD5 hash (only part of it) was in the filename, which is just stupid. I decided that I want to use this tool and flash the ROM anyway. I connected my phone (which was in fastboot mode) to USB 3.0 port in my PC and ran the tool. It got up to flashing system image, but then I got an error "Failed system flash". I noticed that the bootloader got locked, but the MiFlash Unlock tool told me that the device is already unlocked. I tried to boot to TWRP but, well, the bootloader was locked. I thought I hard bricked my phone, but then I decided to connect it to USB 2.0 port. To my surprise, the whole flashing progress was successful and I got no errors. It was suspicious for me, I thought that the first error was on purpose, to replace boot image to allow installation of rogue ROMs with locked bootloader. I know it's kinda paranoic, but I don't trust these Chinese tools at all. Also, I compared old boot image (backed up with TWRP) with new one, and their hashes were different. When the phone booted, I successfully updated MIUI to version 11.0.4.0 (it's the latest MIUI available in Poland), so it seems for me that it's legit. I'm attaching some screenshots from settings: https//)imgur(.)com/a/894o9qU. So, what's the best way to determine if the system is 100% legit and I'm not running some fake ROM with hidden malware?
Click to expand...
Click to collapse
That site is the official MIUI forums and the list of fastboot ROMs listed in that page are the official ROMs. As far as I know, that page is the only official page that has fastboot ROM links.
A boot partition backup from TWRP will not give the same hash, it copies the data from the boot partition into a new .img file, it does not do a bit perfect copy of the partition.
Robbo.5000 said:
That site is the official MIUI forums and the list of fastboot ROMs listed in that page are the official ROMs. As far as I know, that page is the only official page that has fastboot ROM links.
A boot partition backup from TWRP will not give the same hash, it copies the data from the boot partition into a new .img file, it does not do a bit perfect copy of the partition.
Click to expand...
Click to collapse
Thank you for your response! So it seems that I've done everything properly and there's no need to worry about anything

General [X60 PRO+] Chinese variant - Official Stock ROM Collection

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

Categories

Resources