Database Develop

Hard brick never seen! Mia2 -> mi6x System has been destroyed

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

Help! Got bootloop after flashing permissiver_v5 in Evo X Rom (A2)

Hello! Hoping someone can help and guide me in fixing my A2's bootloop. I already searched many forums online, but still no luck.
I flashed a permissiver_v5.zip in Evolution X Rom hoping that it will solve the random reboots, and I got bootloop. I successfully flashed the July stock rom through Miflash, hoping to boot into system, but still bootloop. I flashed the stock firmware and persist zip too in TWRP, but I also got mount persist error. I also need to use fastboot boot twrp.img to get into Twrp since it will disappear after clicking reboot recovery. I tried EDL, but then I got not enough storage error in Miflash.
Hopefully somebody can help me with steps!
LATEST UPDATE:
With the help of KevMetal, I can now use my phone after a week of being hardbricked. At first, my device can't boot to the bootloader or recovery, so what I did was to press the volume down and power button for some time and my phone was detected by the PC. So my device booted to EDL by itself, no need to open the phone. Then I used the 2018 version of MiFlash Tool and flashed the V.10.0.17 of stock Pie ROM from here: https://forum.xda-developers.com/mi-...-t3824849/amp/
After that, I flashed the persist.zip provided by KevMetal (browse in this thread) in recovery since I can't sideload the zip, and it worked fine. I then booted to system and finally there was no bootloop.
I then noticed that the IMEI was gone, so I tried to fix through some guides online but this one worked for me. https://medium.com/@shekhawatkoki/fi...1-2ed533548d32

Ronaldendoma said:
Hello! Hoping someone can help and guide me in fixing my A2's bootloop. I already searched many forums online, but still no luck.
I flashed a permissiver_v5.zip in Evolution X Rom hoping that it will solve the random reboots, and I got bootloop. I successfully flashed the July stock rom through Miflash, hoping to boot into system, but still bootloop. I flashed the stock firmware and persist zip too in TWRP, but I also got mount persist error. I also need to use fastboot boot twrp.img to get into Twrp since it will disappear after clicking reboot recovery. I tried EDL, but then I got not enough storage error in Miflash.
Hopefully somebody can help me with steps!
Click to expand...
Click to collapse
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs

KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you so much for your reply. I really appreciate it. I admit that I am really wrong in flashing that permissiver zip. I just hoped that it will solve my random reboot issue, from this tutorial: https://www.google.com/url?sa=t&sou...BMAB6BAgCEAE&usg=AOvVaw2suOu9rYeTps71AvKuZbrA
So now, I already downloaded OrangeFox-R10.1_1-Stable-jasmine_sprout.zip for recovery and persist_restorer_6x.zip from the Telegram group, which is universal persist according to them.
But I just have some questions:
1. Do I need to wipe both a and b in recovery or use command fastboot -w before flashing the stock ROM?
2. After flashing stocK ROM in Miflash tool, it will start to boot to system, but in this case, bootloop, so am I right to press buttons to forcibly go to bootloader?
3. For #7 (boot to recovery), this means fastboot boot recovery.img?
4. For #9, if adb sideload doesn't work, can I flash persist in recovery instead?

Ronaldendoma said:
Thank you so much for your reply. I really appreciate it. I admit that I am really wrong in flashing that permissiver zip. I just hoped that it will solve my random reboot issue, from this tutorial: https://www.google.com/url?sa=t&sou...BMAB6BAgCEAE&usg=AOvVaw2suOu9rYeTps71AvKuZbrA
So now, I already downloaded OrangeFox-R10.1_1-Stable-jasmine_sprout.zip for recovery and persist_restorer_6x.zip from the Telegram group, which is universal persist according to them.
But I just have some questions:
1. Do I need to wipe both a and b in recovery or use command fastboot -w before flashing the stock ROM?
2. After flashing stocK ROM in Miflash tool, it will start to boot to system, but in this case, bootloop, so am I right to press buttons to forcibly go to bootloader?
3. For #7 (boot to recovery), this means fastboot boot recovery.img?
4. For #9, if adb sideload doesn't work, can I flash persist in recovery instead?
Click to expand...
Click to collapse
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs

KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
KevMetal said:
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you again.
I tried adb sideload before but was stuck at 0%, I missed something. I'll update here for the result once I can be back to PC.

KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
KevMetal said:
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you again.
I tried adb sideload before but was stuck at 0%, I maybe missed something. I'll update here for the result once I can be back to PC.

Ronaldendoma said:
Thank you again.
I tried adb sideload before but was stuck at 0%, I maybe missed something. I'll update here for the result once I can be back to PC.
Click to expand...
Click to collapse
ok yeah must be a mistake ..
do you understand that first you enter fastboot and boot the orange fox recovery ..only then you start the adb ..
BUT REMember first you need to toggle or activate adb from orange fox recovery (maybe you forgot this ? )
another thing it is very slow so wait very long
another thing the zip you want to flash must be in the adb folder and have the name you use
so
rename persist to persist.zip and put it in adb folder ..then put magisk zip and rename to magisk.zip :
adb sideload persist.zip
adb sideload magisk.zip
Sent from my wayne using XDA Labs

here is a photo where you need to activate adb
Sent from my wayne using XDA Labs

KevMetal said:
ok yeah must be a mistake ..
do you understand that first you enter fastboot and boot the orange fox recovery ..only then you start the adb ..
BUT REMember first you need to toggle or activate adb from orange fox recovery (maybe you forgot this ? )
another thing it is very slow so wait very long
another thing the zip you want to flash must be in the adb folder and have the name you use
so
rename persist to persist.zip and put it in adb folder ..then put magisk zip and rename to magisk.zip :
adb sideload persist.zip
adb sideload magisk.zip
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
I need to wait more, I think. Before this thread, I tried to adb sideload in TWRP but it took somewhat long and still 0%, so I just cancelled since I ran out of time.

KevMetal said:
here is a photo where you need to activate adb
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Regarding persist.zip, I am now confused because I asked in the group if the file persist_restorer_6x.zip is universal (either pie or 10, wayne or jasmine), they said yes, and another one said no. I searched in the group and found persist_restorer_a2.zip. I checked both files and they have the same filesize and contents.
So is there a thing like a universal persist for a2/6x, either for pie or 10? Or like what you said, only relevant persist depending on the os and device?

techieboy2020 said:
Regarding persist.zip, I am now confused because I asked in the group if the file persist_restorer_6x.zip is universal (either pie or 10, wayne or jasmine), they said yes, and another one said no. I searched in the group and found persist_restorer_a2.zip. I checked both files and they have the same filesize and contents.
So is there a thing like a universal persist for a2/6x, either for pie or 10? Or like what you said, only relevant persist depending on the os and device?
Click to expand...
Click to collapse
it is the same device.. so it is cross compatible ..it might just give an error if it checks the build prop ..obviously flash the A2..pie or q will just maybe be updated version or not but bettrr to flash corresponding if it exists
Sent from my wayne using XDA Labs

KevMetal said:
it is the same device.. so it is cross compatible ..it might just give an error if it checks the build prop ..obviously flash the A2..pie or q will just maybe be updated version or not but bettrr to flash corresponding if it exists
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
I see. I can't access my PC yet, but what if I still got bootloop after trying those steps, what must I do next? I'm worried for step #10.
Regarding the persist.zip, can you please check the zips below? The two have the same filesize and files inside, so maybe the two are just the same.

techieboy2020 said:
I see. I can't access my PC yet, but what if I still got bootloop after trying those steps, what must I do next? I'm worried for step #10.
Regarding the persist.zip, can you please check the zips below? The two have the same filesize and files inside, so maybe the two are just the same.
Click to expand...
Click to collapse
those are empty and won't work ..use this
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
Sent from my wayne using XDA Labs

KevMetal said:
those are empty and won't work ..use this
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Ok thank you so much. Will try this tomorrow.
Regarding the state of my device, I can't boot to system because of bootloop. If I press power and volume +, I got no command. If I press power and volume -, fastboot mode. My device's bootloader is already unlocked, and can be detected through fastboot.

techieboy2020 said:
Ok thank you so much. Will try this tomorrow.
Regarding the state of my device, I can't boot to system because of bootloop. If I press power and volume +, I got no command. If I press power and volume -, fastboot mode. My device's bootloader is already unlocked, and can be detected through fastboot.
Click to expand...
Click to collapse
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs

KevMetal said:
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Got it. So the zip is compatible for either Pie or Android 10?
What's the best version for Miflash tool? I tried the newer version but it can't detect my device, and only the older version can detect. But it seems that the older version can't be trusted also since I still got persist error before.
For #10, my device will bootloop 4 to 5 times. So will it automatically turn off and on again until it will successfully boot? How long does it normally boot?

UPDATE:
KevMetal said:
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
UPDATE:
So I flashed the Pie Rom (V.10.0.17.0) in the MiFlash Tool (v. 2016.04.01.0) and the flashing was successful. The device turned on and only remained at the Android One logo and turned off again. This repeated for another time and I then forced my device to fastboot mode through the buttons. I then flashed the latest Orange Fox Recovery and it was successful. Now, I checked the recovery and persist can't be mounted (can't put a check on the box), but I still continued to adb sideload mode. The sideloading for persist.zip started, but was stuck at 10%. I waited more and decided to disconnect and try to flash the zip on the device instead. I checked the active slot and it was b, so I thought changing to a will be able to mount persist. I thought that if I remain at b, I will still get mount persist error. I clicked "boot to recovery" and the screen turned off. After a while, the screen remained off and I tried to use the button combinations, and the screen was totally black (no fastboot, logo, animation, or even some light, etc). It's completely black, but I noticed that the device was still hot after a few minutes. I connected my device to the PC again and the MiFlash tool detected my device as Com10. I flashed the rom again but the flashing was not successful. I tried to uninstall the drivers and still, there is no hope for reflashing the rom (it's now detected as com4). If I try to use power combinations, the PC will make sounds like when you connect/ disconnect a device, meaning, my phone can still be detected by my PC. So is there still a hope for my phone?

techieboy2020 said:
UPDATE:
So I flashed the Pie Rom (V.10.0.17.0) in the MiFlash Tool (v. 2016.04.01.0) and the flashing was successful. The device turned on and only remained at the Android One logo and turned off again. This repeated for another time and I then forced my device to fastboot mode through the buttons. I then flashed the latest Orange Fox Recovery and it was successful. Now, I checked the recovery and persist can't be mounted (can't put a check on the box), but I still continued to adb sideload mode. The sideloading for persist.zip started, but was stuck at 10%. I waited more and decided to disconnect and try to flash the zip on the device instead. I checked the active slot and it was b, so I thought changing to a will be able to mount persist. I thought that if I remain at b, I will still get mount persist error. I clicked "boot to recovery" and the screen turned off. After a while, the screen remained off and I tried to use the button combinations, and the screen was totally black (no fastboot, logo, animation, or even some light, etc). It's completely black, but I noticed that the device was still hot after a few minutes. I connected my device to the PC again and the MiFlash tool detected my device as Com10. I flashed the rom again but the flashing was not successful. I tried to uninstall the drivers and still, there is no hope for reflashing the rom (it's now detected as com4). If I try to use power combinations, the PC will make sounds like when you connect/ disconnect a device, meaning, my phone can still be detected by my PC. So is there still a hope for my phone?
Click to expand...
Click to collapse
all of this couldn't happen if you only flashed permissiver ..what rom did you previously flash in slot b
anyway doesn't matter ..boot to fastboot with buttons ..boot ..NOT FLASH orange fox recovery
do all wipes
format data
install custom rom
install magisk
install persist
reboot to other standby slot ..
do all wipes
format data
install custom rom
install magisk
install persist
then reboot and phone will boot
use a latest custom rom Q with gapps included ....
follow all the instructions ..not only some ..don change them ..if it fails message me with screenshot
but the 10% problem over usb is a hardware , computer or most likely cable problem ..get a new cable ..or maybe you changed or damaged your screen improperly ..
anyway try the above
also download the most newest copy of miflash and use that to install drivers and flash if you want to flash stock and flash the latest stock amdroid ..
if your phone doesn't go into fastboot it is cos it is bricked in edl mode ..so flash latest stock with latest miflash ..
THEN FLASH PERSIST BY ONLY BOOTINGBrecovery
did you try to convert this A2 to Wayne amd triggered arb ? that could be why flashing stock pie goes to edl mode
Sent from my wayne using XDA Labs

Just FYI:
Since 10.0.2.0 till now I thought that persist.img is version-insensitive, as I flashed persist.img taken from 8.1 ROM into couple of versions of 9.0 without any problems (via my method published in "Guides...").
Last week I noticed that compass is "showing south", and tried to flash various versions of persist.img into active 11.0.12.0 - and was surprised to encounter "white screen of eternal booting" with non-native version of persist.img. So finally had to flash persist.img taken from 11.0.12.0 fastboot ROM image.
(Btw, my problem with compass seems to have 2 sides -1st is somewhat very big deviation at homeplace, and 2nd is that only 1st magnetic sensor is being calibrated while second magnetic sensor is not being calibrated by means I used).

KevMetal said:
all of this couldn't happen if you only flashed permissiver ..what rom did you previously flash in slot b
anyway doesn't matter ..boot to fastboot with buttons ..boot ..NOT FLASH orange fox recovery
do all wipes
format data
install custom rom
install magisk
install persist
reboot to other standby slot ..
do all wipes
format data
install custom rom
install magisk
install persist
then reboot and phone will boot
use a latest custom rom Q with gapps included ....
follow all the instructions ..not only some ..don change them ..if it fails message me with screenshot
but the 10% problem over usb is a hardware , computer or most likely cable problem ..get a new cable ..or maybe you changed or damaged your screen improperly ..
anyway try the above
also download the most newest copy of miflash and use that to install drivers and flash if you want to flash stock and flash the latest stock amdroid ..
if your phone doesn't go into fastboot it is cos it is bricked in edl mode ..so flash latest stock with latest miflash ..
THEN FLASH PERSIST BY ONLY BOOTINGBrecovery
did you try to convert this A2 to Wayne amd triggered arb ? that could be why flashing stock pie goes to edl mode
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
So I was able to use another laptop, and I managed to install adb, drivers, and MiFlash Tool. The 2018 version can now detect my phone, and I can now at least boot into fastboot. But my flashing is still not successful because I got stuck at system.img. The laptop freezes and I already tried to free up space in C: drive.

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

Merlin , bricked , cant enter fastboot or recovery, cant turn device off , bootloop

Hello, i have a redmi note 9,
I was using lineage OS from here https://t.me/HelioG85_Updates/265
Custom firmware, custom opensource vendor
I wasnt able to boot into the recovery today for some reason, i was using the recovery from here https://t.me/HelioG85_Updates/268
In a moment of genius, i decided to get this app https://play.google.com/store/apps/details?id=net.mxbi.reboot and used it to boot to the recovery , now my device is bricked, doesnt enter fastboot or the recovery , and i cant turn the device of meaning i cant flash with sp flash tool
My bootloader is unlocked. i do not have a xiaomi account anymore
I have my imei and nvdata backed up, so i should be fine on that regard
Please do help me, This is the only phone i have and i cannot get a another one . If you help me i will be forever greatfull to you, Please help me i am desperate

Ifuckinghatemyselfandall said:
Hello, i have a redmi note 9,
I was using lineage OS from here https://t.me/HelioG85_Updates/265
Custom firmware, custom opensource vendor
I wasnt able to boot into the recovery today for some reason, i was using the recovery from here https://t.me/HelioG85_Updates/268
In a moment of genius, i decided to get this app https://play.google.com/store/apps/details?id=net.mxbi.reboot and used it to boot to the recovery , now my device is bricked, doesnt enter fastboot or the recovery , and i cant turn the device of meaning i cant flash with sp flash tool
My bootloader is unlocked. i do not have a xiaomi account anymore
I have my imei and nvdata backed up, so i should be fine on that regard
Please do help me, This is the only phone i have and i cannot get a another one . If you help me i will be forever greatfull to you, Please help me i am desperate
Click to expand...
Click to collapse
So sp flash tool will lock your phone to engineer mode if it turns off follow this instruction:
prepare sp flash tools to only flash recovery (the one you want to boot into)
then click the download button to start flash
then wait for phone to get to boot( when image appears, before it gets to reboot plugin your phone to pc)
sp flash tools will flash then when done make sure you reboot to the custom recovery
then if you can access your system from recovery , look next to build.rop for recovery or rebootfromrecovery.p
copy the file somewhere
edit in notepad to clear everything, save it then use the edited one to overwrite

flairepathos.info said:
So sp flash tool will lock your phone to engineer mode if it turns off follow this instruction:
prepare sp flash tools to only flash recovery (the one you want to boot into)
then click the download button to start flash
then wait for phone to get to boot( when image appears, before it gets to reboot plugin your phone to pc)
sp flash tools will flash then when done make sure you reboot to the custom recovery
then if you can access your system from recovery , look next to build.rop for recovery or rebootfromrecovery.p
copy the file somewhere
edit in notepad to clear everything, save it then use the edited one to overwrite
Click to expand...
Click to collapse
I am going to try the mtk bypass tool, is that going to work? if not i am going to try your instructions, however it did not boot into the recovery even after reflashing , i have tried that before with the twrp app
It cannot detect the device, it isnt in device manager either, i am getting scared
edit: actually it gets detected in device manager as "usb serial device (com4)" when i hold the power button, volume up and volume down at the same time, when i do that, the device stays with a black screen
SP flash tool still does not detect it
it seems to be disconnecting while in this state
Please help, i cant turn the device off
sp flash tool says STATUS_EXT_RAM_EXCEPTION i was trying to flash miui 12.5 R i will try flashing 12.0.5 q since thats what people are using

Ifuckinghatemyselfandall said:
sp flash tool says STATUS_EXT_RAM_EXCEPTION i was trying to flash miui 12.5 R i will try flashing 12.0.5 q since thats what people are using
Click to expand...
Click to collapse
You need to flash the SAME miui version present on the device first.

VD171 said:
You need to flash the SAME miui version present on the device first.
Click to expand...
Click to collapse
But i do not know which version was present before, i was using a custom rom when it bricked...
I do think it was running 12.0.6 EEA Q
i am trying to flash miui 12.0.5 global, will that be okay?
It is now giving me "error status error" please help

Ifuckinghatemyselfandall said:
But i do not know which version was present before, i was using a custom rom when it bricked...
I do think it was running 12.0.6 EEA Q
i am trying to flash miui 12.0.5 global, will that be okay?
Click to expand...
Click to collapse
Certainly, mixing files from different miui versions, bricked your device.
You need to flash the correct miui version to fix the partition table.
And then, you can flash another miui version using fastboot.

VD171 said:
Certainly, mixing files from different miui versions, bricked your device.
You need to flash the correct miui version to fix the partition table.
And then, you can flash another miui version using fastboot.
Click to expand...
Click to collapse
No, this is not waht bricked my device, i rebooted to a custom recovery while on a custom rom and thats when it happened

Ifuckinghatemyselfandall said:
No, this is not waht bricked my device, i rebooted to a custom recovery while on a custom rom and thats when it happened
Click to expand...
Click to collapse
Custom recovery will never brick a device.

VD171 said:
Custom recovery will never brick a device.
Click to expand...
Click to collapse
You dont seem to understand what i am saying, It does not if you disable boot verification, which i did , please reread the post

Ilovethewholeworldbutme said:
You dont seem to understand what i am saying, It does not if you disable boot verification, which i did , please reread the post
Click to expand...
Click to collapse
Just flash the full stock miui again.

Ozip links for Realme 6 (RMX2001)

OZIP's FOR RMX2001​​«Android 10»​ㅤㅤ ㅤㅤㅤㅤ ㅤㅤㅤㅤㅤㅤㅤ Click Here
«Android 11»​*Team Drive Gone Will Find And Update
​Need Help?
Contact Me On Telegram
-GROUP LINK-

Awesome!! Can I dirty flash ui2?

Android 11 update (C12 Global) failed, why?

Not flashing ui 2

Ferbir88 said:
Android 11 update (C12 Global) failed, why?
Click to expand...
Click to collapse
it cant be flashed directly u should flash ozip using custom recovery but after flash , flash patched vbmeta too otherwise u got brick for more info ask in ofiicial realme 6 main telegram group

xdriv3r said:
Not flashing ui 2
Click to expand...
Click to collapse
u cant flash it by stock recovery read other comment reply

unique_sandesh said:
it cant be flashed directly u should flash ozip using custom recovery but after flash , flash patched vbmeta too otherwise u got brick for more info ask in ofiicial realme 6 main telegram group
Click to expand...
Click to collapse
I tried not working (bootloop). I lfashed patched vbmeta. I installed it with custom recovery

Ferbir88 said:
I tried not working (bootloop). I lfashed patched vbmeta. I installed it with custom recovery
Click to expand...
Click to collapse
tell meyour all process sir , and they also need format

unique_sandesh said:
unique_sandesh said:
tell meyour all process sir , and they also need format
First, I flashed stock b.53 firmware with SP flashtool and I update with stock recovery to b.65. For the second time I need root the firmware and patch vbmeta, because missing the custom recovery without this step.( orange fox recovery)For the third Time I flash the c.12 firmware with custom recovery, and reboot to bootloader from recovery than I patch c.12 vbmeta. For the last Time I reboot and the end result bootloop.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

unique_sandesh said:
tell meyour all process sir , and they also need format
Click to expand...
Click to collapse
First, I flashed stock b.53 firmware with SP flashtool and I update with stock recovery to b.65. For the second time I need root the firmware and patch vbmeta, because missing the custom recovery without this step.( orange fox recovery)For the third Time I flash the c.12 firmware with custom recovery, and reboot to bootloader from recovery than I patch c.12 vbmeta. For the last Time I reboot and the end result bootloop

ofc it will not boot untill u format data , u need to format data . give these cmd fastboot -w , fastboot erase userdata

unique_sandesh said:
ofc it will not boot untill u format data , u need to format data . give these cmd fastboot -w , fastboot erase userdata
Click to expand...
Click to collapse
Thank you very much now It works, but I want to ask you: Why can not i enter in recovery Mode? I tried the power on and volume down combination, but the phone enter only fastboot mode with "oplus verification failed" message. If I do a factory reset under the Android, the phone load the recovery, until resetting.

Ferbir88 said:
Thank you very much now It works, but I want to ask you: Why can not i enter in recovery Mode? I tried the power on and volume down combination, but the phone enter only fastboot mode with "oplus verification failed" message. If I do a factory reset under the Android, the phone load the recovery, until resetting.
Click to expand...
Click to collapse
from rmui 2.o we only get in fastboot mode. for recovery give this cmd fastboot reboot recovery, , and ignore that oppo verify failed msg

unique_sandesh said:
from rmui 2.o we only get in fastboot mode. for recovery give this cmd fastboot reboot recovery, , and ignore that oppo verify failed msg
Click to expand...
Click to collapse
Thank you very much!

Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply

Jegwaar said:
Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply
Click to expand...
Click to collapse
were the same situation and i dont know what to do. Please help us.

which is the process 4 install? im on rui 1.0

Kodize said:
which is the process 4 install? im on rui 1.0
Click to expand...
Click to collapse
using custom recovery
Rollback With Custom Recovery
This Method Only For Realme 6/6i(indian)/6s _____________________ RMUI2.0 TO RMUI 1.0____________________________________________ This Method For Downgrading From F2Fs Based Custom Roms ⓿ Flash Latest TWRP (Gofaraway One) ❶ Go to manage partitions And Select...
telegra.ph

Jegwaar said:
Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply
Click to expand...
Click to collapse
keep unlockd your bl and use spft for flashing rui 2 make sure you selected download only in spft while flashing here is the latest decrypted firmware link https://t.me/rmx2001_clouds/7

unique_sandesh said:
keep unlockd your bl and use spft for flashing rui 2 make sure you selected download only in spft while flashing here is the latest decrypted firmware link https://t.me/rmx2001_clouds/7
Click to expand...
Click to collapse
Hi guys, did someone do this ? i'm in the same situation after rolling back to B55 using stock recovery, now stuck on B65, no update coming.
Bootloader is unlocked, when i flash a C18 firmware with SPF phone bootloop in fastboot mode.
Only flashing a B65 firmware with SPF to get phone boot corretly.
I just need to known if this method is tested with the given C19 firmware ?
Many thx.