Hi, guys. I have a terrible issue with my phone. I tried to flash stock ROM and phone get bricked. After that, i used a tool to flash without MiFlash but i miss the tool is for Redmi 3S, so i guess i mess up, HardBrick. The thing is that my phone is stuck in EDL mode, if i connect to laptop, that recognize QD Loader 9008 port. But if i flash again, i getting the error "writing exceeded wait time" and in times "only nop and sig tag...."
Any advices folks??
Edit: I used newest MiFlash and all good untill i get "No authorized Xiaomi Account can't Flash" message... Help please
Miflash Beta 2016: "cannot find port"
Miflash 2015: "catastrophic failure 0x8000ffff "
Can you boot into recovery?
THE USER said:
Can you boot into recovery?
Click to expand...
Click to collapse
Im stuck in EDL, i dont tried point test yet because dont want to loose warranty. None of the button combinations can send my out of EDL
kathsfernan said:
Im stuck in EDL, i dont tried point test yet because dont want to loose warranty. None of the button combinations can send my out of EDL
Click to expand...
Click to collapse
Did you solve it?
I have the same problem
venezolano69 said:
Did you solve it?
I have the same problem
Click to expand...
Click to collapse
Dont worked any of the advices. The only method i have seen is to pay a s- unlock account (20-30 $) but i certainly need a china rom, and dont exist any for the RN 6 Pro, so i guess i have a paperweight instead :crying:
Hi guys, i need to tell you that i could flash via MiFlash with succeed. The problem i have right now that the phone is in Bootloop, even if i Flash again with newest MiFlash version. I have to say that im unlocked bootloader, what you recomend?
Had the same issue. Went to the service center and they flashed it and gave it back within 15 mins
As i have read in the article from the link below, even for EDL you have to have account approval from Xiaomy (which is paid i assume)...
https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
Sent from my Redmi Note 6 Pro using Tapatalk
Well.... after thousand of tries, i could bring back to life my device, only flashing Beta Pie Official rom via MiFlash 2018528. Only thing is that i missed IMEI
I have also watched before (maybe a year ago) some clips on YouTube how to bring back IMEI number (procedure for entering number, you have it on the box of the phone if you still have it).
Hope you will resolve it soon.
I will download MiFlash 2018528 and try to flash MIUI 9 to mine phone... I have read that MIUI 9.6.10.0 have ARB level 4, same as MIUI 10.2.2.0 so it should be safe to flash back to MIUI 9 (really hope it is safe [emoji53])
Sent from my Redmi Note 6 Pro using Tapatalk
Well...i was.flashing 9.6.10.0 through MinFlash tool, and after some 130 seconds, some error has been reported (Failed to write - somerhing like that) and I'm stuck on Fastboot... Same thing is happening when i want to flash 10.0.5.0 or even 10.2.2.0 which was there in the first place...
Since it's stuck in Fastboot, i hope i didn't brick it... I have sent it to a guy which is an expert in these things, hoping to resolve ot successfully [emoji53]
Sent from my Redmi Note 4 using Tapatalk
davorterzin said:
Well...i was.flashing 9.6.10.0 through MinFlash tool, and after some 130 seconds, some error has been reported (Failed to write - somerhing like that) and I'm stuck on Fastboot... Same thing is happening when i want to flash 10.0.5.0 or even 10.2.2.0 which was there in the first place...
Since it's stuck in Fastboot, i hope i didn't brick it... I have sent it to a guy which is an expert in these things, hoping to resolve ot successfully [emoji53]
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
You could flash back Beta Pie from newest fastboot without any problem
My problem right now is that i restore IMEI, but no signal for me. None of the sim card, even if the phone recognize that
How did u get the authorized ID?
could someone solve it?
Related
Hello everyone, currently after my bad decision to flash keymaster file form Note 7, my Note 7 Pro is dead and don't have heart beat.
After a while I see only EDL working via testpoint on back cover. Now am stuck between two option to pay 30$ for auth. account or find emmc file.
I know nothing is free but i will try to find emmc firehose mbn file. If anyone have idea where can find be kind to share with me. Thanks in advance!
I think the name of the file will be prog_emmc_firehose_Sdm675_ddr.mbn or prog_emmc_firehose_Sdm6150_ddr.mbn
b0nb0n3v said:
Hello everyone, currently after my bad desiciot to flash keymaster file form Note 7, my Note 7 Pro is dead and don't have heart beat.
After a while I see only EDL woriking via testping on backcover. Now am stuck between two option to pay 30$ for auth. account or find emmc file.
I know nothing is free but i will try to find emmc firehose mbn file. If anyone have idea where can find be kind to share with me. Thanks in advance!
I think the name of the file will be prog_emmc_firehose_Sdm675_ddr.mbn or prog_emmc_firehose_Sdm6150_ddr.mbn
Click to expand...
Click to collapse
It will available in fastboot rom right ? ?
urstrulynaveen said:
It will available in fastboot rom right ? ?
Click to expand...
Click to collapse
No, no light, no vibration - nothing. Only EDL via testpins work, but need auth. account for flash. I think have another way to revive. I will wait some guru to see this thread.
I don't know did available to switch from EDL to fastboot?
b0nb0n3v said:
No, no light, no vibration - nothing. Only EDL via testpins work, but need auth. account for flash. I think have another way to revive. I will wait some guru to see this thread.
I don't know did available to switch from EDL to fastboot?
Click to expand...
Click to collapse
This happend to me also i searched whole internet but sadly their is no firehose file for our violet available to bypass edl auth. I suggest the best way to reach nearest service center they flash it with mi flash via testpoints and its cheap not so coastly. Dont try to flash by your side alone u may trash ur partition tables situations may get worse.
Same here I don’t have any hope for this trash. Never gonna by a Xiaomi again. I remember in old redmi phones you didn’t need auth to flash edl
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
There was a Russian selling me auth account for 10$ but I bet he’s gonna scam so I didn’t try.
Anyway. Let me know if you find the firehose file or anything.
DeveloperOne said:
Same here I don’t have any hope for this trash. Never gonna by a Xiaomi again. I remember in old redmi phones you didn’t need auth to flash edl
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
There was a Russian selling me auth account for 10$ but I bet he’s gonna scam so I didn’t try.
Anyway. Let me know if you find the firehose file or anything.
Click to expand...
Click to collapse
Yes they are scamers and they use TeamViewer which may lead to hack your computer. So better is to rush on service center. Those good old days of redmi phones will never come back they are imposing more and more restrictions to devices.
my violet is dead !
my phones is also dead ....was trying to get back to miui 11 (android 9)from covrvus 6.5(android 10) because no sensors were working in corvus !
i got miui 11 but wifi was not working and sensors too ! tried flaashing many fastboot roms from offical miui sites but non of them fixed senors and wifi ! ...then tried flashing with old miflashtool probably 2014 version ... then flash system error came while flashing fastboot rom violet ....
then phone got switched off automaticaly ! and never started since then !
i looked up everything flashing with edl mode !
in miflashtool
earlier when bootloader it was showing "ceeee0ccc0" device name
now in miflashtool it is showing "COM20" or"COM10"
when i am flashing fastboot rom latest one with latest flashtool
it is showing "packet receive something something..." call paket ...etc
some time it shows "edl auth " then it ask to sign in my account after login ..
"Your Acount is bined to this system " but later ""Your account is not authorised for this operation !"
and hence the flashing stops with error !
if someone is seriously readying this you can reply and ask for screenshots
please ! i have lost all hopes ! i need some guidence and lil help !
I looked a way to bypass edl auth ...
but the video was of Redmi note 7 ! not pro
in there he used
some file "prog_emmc_firehose_Sdm610_ddr.mbn" somehing like that ...
he placed this file in images folder !
it skipped the edl auth ...and flashing continued !
maybe if i can get file
prog_emmc_firehose_Sdm675_ddr.mbn something like that of my phone
violet version for my chipset
maybe i can skip too auth edl ....
dont know ! just help please !
kankurcool said:
my phones is also dead ....was trying to get back to miui 11 (android 9)from covrvus 6.5(android 10) because no sensors were working in corvus !
i got miui 11 but wifi was not working and sensors too ! tried flaashing many fastboot roms from offical miui sites but non of them fixed senors and wifi ! ...then tried flashing with old miflashtool probably 2014 version ... then flash system error came while flashing fastboot rom violet ....
then phone got switched off automaticaly ! and never started since then !
i looked up everything flashing with edl mode !
in miflashtool
earlier when bootloader it was showing "ceeee0ccc0" device name
now in miflashtool it is showing "COM20" or"COM10"
when i am flashing fastboot rom latest one with latest flashtool
it is showing "packet receive something something..." call paket ...etc
some time it shows "edl auth " then it ask to sign in my account after login ..
"Your Acount is bined to this system " but later ""Your account is not authorised for this operation !"
and hence the flashing stops with error !
if someone is seriously readying this you can reply and ask for screenshots
please ! i have lost all hopes ! i need some guidence and lil help !
I looked a way to bypass edl auth ...
but the video was of Redmi note 7 ! not pro
in there he used
some file "prog_emmc_firehose_Sdm610_ddr.mbn" somehing like that ...
he placed this file in images folder !
it skipped the edl auth ...and flashing continued !
maybe if i can get file
prog_emmc_firehose_Sdm675_ddr.mbn something like that of my phone
violet version for my chipset
maybe i can skip too auth edl ....
dont know ! just help please !
Click to expand...
Click to collapse
Bro sadly there is no firehose file for violet. I had same issue earlier only solution is to go service center. They flash in edl takes just 10 mins charge around 180 rupees. U may try flashing via umt dongle or miracle thunder but i never recommendes that.
My RN7pro got also dead, I had to pay 1200rs to revive this phone by local mobile repairer. They flash it with UFI box. I made mistake no to go authorised service center. That technician looted me.
b0nb0n3v said:
No, no light, no vibration - nothing. Only EDL via testpins work, but need auth. account for flash. I think have another way to revive. I will wait some guru to see this thread.
I don't know did available to switch from EDL to fastboot?
Click to expand...
Click to collapse
hey dude can u pls help me? im on the same boat which u were on. i dont find that patched up emmc file of note 7 pro. flashing with the stock rom showing error in quolcomn softwares as well in mi flasher tool. pls help what to do now
Can anyone point me to a guide to do a rollback from 12.5.1 CN ROM to any 12.0.x official CN ROM?
The upgrade to Android 11 was a bad mistake, a lot of things are broken and my notifications (Whatsapp, etc) are no longer working properly.
Is there anti-rollback protection in 12.5.1?
I figured out it's as simple as request Bootloader unlock, then using miflash fastboot to flash the official 12.0.15 fastboot rom with the clean all and lock option?
That's all right? nothing special?
Hi Phibersg, where do I find official rom? - ok found!
However what about ARB Anti rollback
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
Thanks
kiwiindo said:
Hi Phibersg, where do I find official rom? - ok found!
However what about ARB Anti rollback
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
Thanks
Click to expand...
Click to collapse
I just checked there is no ARB for mi 10 ultra on the 12.0.15..
on my mi 10 ultra:
C:\adb>fastboot getvar anti
anti: 1
finished. total time: 0.009s
anti = 1
which is the same as the number is anti_version.txt in
cas_images_V12.0.15.0.QJJCNXM_20201209.0000.00_10.0_cn\images
phibersg said:
I just checked there is no ARB for mi 10 ultra on the 12.0.15..
on my mi 10 ultra:
C:\adb>fastboot getvar anti
anti: 1
finished. total time: 0.009s
anti = 1
which is the same as the number is anti_version.txt in
cas_images_V12.0.15.0.QJJCNXM_20201209.0000.00_10.0_cn\images
Click to expand...
Click to collapse
I am in the same situation and tried rolling back before getting unlocked (still 5 days to go!) however my big issue is to get GAPPS working - contact syncing and WhatsApp changing from phone numbers to contact names at random. Error was AntiRoll Back Error
kiwiindo said:
I am in the same situation and tried rolling back before getting unlocked (still 5 days to go!) however my big issue is to get GAPPS working - contact syncing and WhatsApp changing from phone numbers to contact names at random. Error was AntiRoll Back Error
Click to expand...
Click to collapse
How are you getting anti rollback error when you are still locked and not able to flash?
For the contacts to numbers issue, just set permission for whatsapp to access Contacts to ALWAYS, don't use Allow only when using app.
that will fix the issue.
phibersg said:
How are you getting anti rollback error when you are still locked and not able to flash?
For the contacts to numbers issue, just set permission for whatsapp to access Contacts to ALWAYS, don't use Allow only when using app.
that will fix the issue.
Click to expand...
Click to collapse
I used the Xaiomi MiFlash which works only on Xaiomi ROM So since not changing the boot record I thought it should be ok! I tried to flash back to this ROM cas_images_V12.0.15.0.QJJCNXM_20201209.0000.00_10.0_cn_77d730d8ca.tgz from XaiomiROM.Com. A Flashrom I understand is like an OTA upgrade - but error!
kiwiindo said:
I used the Xaiomi MiFlash which works only on Xaiomi ROM So since not changing the boot record I thought it should be ok! I tried to flash back to this ROM cas_images_V12.0.15.0.QJJCNXM_20201209.0000.00_10.0_cn_77d730d8ca.tgz from XaiomiROM.Com. A Flashrom I understand is like an OTA upgrade - but error!
Click to expand...
Click to collapse
try again when your bootloader is unlocked! Use the full recovery rom instead of the OTA flashrom.
Ya.. cas_images_V12.0.15.0.QJJCNXM_20201209.0000.00_10.0_cn_77d730d8ca.tgz should be the fastboot rom to use.
If you really need to go back, I think you will need an authorised ESL flash from one of the Russian guys.
Managed to rollback to 12.0.15 using miflash last night when my BL got unlocked. just by flashing the 12.0.15 fastboot rom over the 12.5.1 rom in the mi 10 ultra.
nothing extra or special was needed..
i did get a error flashing sparsecrclist.txt error, so i just commented out that line in the BAT and it worked.. LOL
One time affair.. all good now!
i am never touching the 12.5 firmware ever again!
phibersg said:
Managed to rollback to 12.0.15 using miflash last night when my BL got unlocked. just by flashing the 12.0.15 fastboot rom over the 12.5.1 rom in the mi 10 ultra.
nothing extra or special was needed..
i did get a error flashing sparsecrclist.txt error, so i just commented out that line in the BAT and it worked.. LOL
One time affair.. all good now!
i am never touching the 12.5 firmware ever again!
Click to expand...
Click to collapse
If you were bootloader unlocked with twrp installed I'm sure it was possible flashing the 12.0 on 12.5 and than format data (which requires typing "yes") and all would have been good, but that's just my thought based on my android experience and knowledge, cheers
Hello Android-Wizzards,
i am stuck in a Bootloop to stock recovery mode since i tried to downgrade my mi note 10 pro from MIUI 12 V12.1.4.0.RFDEUXM to MIUI 12 V12.1.3.0.RFDEUXM via the update app .
After the OTA update to 12.1.4. i could not make any calls anymore so i searched for a way to downgrade to 12.1.3, where the problem was not present. I did it with the internal update app and followed this instruction: https://www.world-today-news.com/th...evert-your-xiaomi-a-buggy-update-xiaomi-news/
Sadly i didnt make a backup before anf after the rom finished installing it only boots to stock recovery anymore. If i try to connect the device via "Connect with MIAssistant" it does not work.
I searched the forums but i cant find a way to install MIUI 12 V12.1.4.0.RFDEUXM again.
The tutorials mention that if i want to recover my phone i have to use MIflash or fastboot flash which both need a unlocked bootloader according to the tutorials.
Sadly i did NOT unlock the bootloader when the phone was working normal and i dont see a method to umlock the bootloader an a bricked / bottloped mi note 10 pro.
Its bad enough that cause i didnt make a backup befor i tried to downgrad i must assume that all my pbhotos i took this year with my note 10 pro are lost forever, Mi cloud backup is full since last year and i didnt bother to pay for more space, another bad decicion in hindsight but is there a way i can restore my phone?
Please help, i dunno what else to do to get my phone booting up agian.
Had a simmilar problem with an older mi phone of mine a few years ago and then it wasnt a problem cause i could easyli flash it with MIflash, but dunno since when you have to unlock bootloader first and since i didnt know that my phone has a locked bootloader, never minded to unlock it.
Nautzzz said:
Hello Android-Wizzards,
i am stuck in a Bootloop to stock recovery mode since i tried to downgrade my mi note 10 pro from MIUI 12 V12.1.4.0.RFDEUXM to MIUI 12 V12.1.3.0.RFDEUXM via the update app .
After the OTA update to 12.1.4. i could not make any calls anymore so i searched for a way to downgrade to 12.1.3, where the problem was not present. I did it with the internal update app and followed this instruction: https://www.world-today-news.com/th...evert-your-xiaomi-a-buggy-update-xiaomi-news/
Sadly i didnt make a backup before anf after the rom finished installing it only boots to stock recovery anymore. If i try to connect the device via "Connect with MIAssistant" it does not work.
I searched the forums but i cant find a way to install MIUI 12 V12.1.4.0.RFDEUXM again.
The tutorials mention that if i want to recover my phone i have to use MIflash or fastboot flash which both need a unlocked bootloader according to the tutorials.
Sadly i did NOT unlock the bootloader when the phone was working normal and i dont see a method to umlock the bootloader an a bricked / bottloped mi note 10 pro.
Its bad enough that cause i didnt make a backup befor i tried to downgrad i must assume that all my pbhotos i took this year with my note 10 pro are lost forever, Mi cloud backup is full since last year and i didnt bother to pay for more space, another bad decicion in hindsight but is there a way i can restore my phone?
Please help, i dunno what else to do to get my phone booting up agian.
Had a simmilar problem with an older mi phone of mine a few years ago and then it wasnt a problem cause i could easyli flash it with MIflash, but dunno since when you have to unlock bootloader first and since i didnt know that my phone has a locked bootloader, never minded to unlock it.
Click to expand...
Click to collapse
Did you try wipe data with the recovery?
or try this old method.
Did you try to flash the rom in recovery again?
Hey!
Soooooo, I tried to update my OS to the most recent while rooted, but I accidentally locked my boot loader, bricked the software, tried to unbrick it, then later got hard bricked in EDL mode. I have tried using the MSM tool for the global version of the Oneplus 9 but it always ended up saying that the image didn't match or something (IDK the thing was in F’ing Chinese). This hard brick has gotten so bad that I cant even hold Vol up + Power to hard restart it. The screen just doesn't come on any more but is still recognized by my computer as a Qualcomm device. Does anyone know of a fix that doesn't include installing the Indian loader?
Model # LE2115 (OP9 Global)
I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for you.
chinbags said:
I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for you.
Click to expand...
Click to collapse
I had to do the same thing. I am using a LE2113 and managed to brick my phone in a way where only EDL could save it. I came from the latest OOS (colorOS) firmware and tried to flash LineageOS when everything went south. I tried to use the Oneplus 9 EU MSM tool but this one did not work for me. Since there is no official EU MSM for the LE2113 the only way I could repair it was by using the EU OnePlus 9 pro msm firmware. It only worked with the "use lite firehose" option for me. After that was done I unlocked the bootloader once again and flashed OOS (Android 11) for OnePlus 9 again. This was the way I got the original firmware back on my device although I do not think it would've been possible to relock the bootloader at this point.
Straight after that I once again flashed lineage and everything is working fine now. Certainly a shady approach but it is the end result that counts I'd say.
Nullifii said:
Hey!
Soooooo, I tried to update my OS to the most recent while rooted, but I accidentally locked my boot loader, bricked the software, tried to unbrick it, then later got hard bricked in EDL mode. I have tried using the MSM tool for the global version of the Oneplus 9 but it always ended up saying that the image didn't match or something (IDK the thing was in F’ing Chinese). This hard brick has gotten so bad that I cant even hold Vol up + Power to hard restart it. The screen just doesn't come on any more but is still recognized by my computer as a Qualcomm device. Does anyone know of a fix that doesn't include installing the Indian loader?
Model # LE2115 (OP9 Global)
Click to expand...
Click to collapse
That's not Chinese version m8 le2110 is, I bricked mine , I flashed it with global version , now it says it le2115 lol after OTA update to android 12 ??
jab5555 said:
That's not Chinese version m8 le2110 is, I bricked mine , I flashed it with global version , now it says it le2115 lol after OTA update to android 12 ??
Click to expand...
Click to collapse
That's the thing though. I had the LE2115 MSM tool but it was in Chinese for some reason I have a LE2115 phone as well but it said that the files didn't match up. Maybe they uploaded the wrong variant to the website? None of the tools that I had downloaded were in English, all in Chinese.
chinbags said:
I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for y
Click to expand...
Click to collapse
File folder on MEGA
mega.nz
This what I used m8, got it off OP when they tried to remote flash my phone , couldn't do it on AMD Ryzen, done on my old pc, driver issue lol, good luck m8
I tried to flash Global ROM to Chinese Redmi Note 11E Pro 5G, but when flashing unintentionally ticked "flash and lock" option. Now my phone is stuck in Fastboot mode, and it doesn't allow me to neither flash other ROMs nor unlock using MiFlashUnlock.
I searched how to fix this in Internet, but unfortunately didn't find any solution - every option requires me to unlock bootloader with a functioning phone, but unfortunately that seems not possible in my case.
Is my phone bricked?
Any way to bring it back to life?
Basriy, if you are going to use this route, could you please report whether it was a success?
astanlofter said:
Basriy, if you are going to use this route, could you please report whether it was a success?
Click to expand...
Click to collapse
I would love to. In fact, I have contacted that guy from Telegram and I genuinely believe he is capable of solving my issue. The problem is I couldn't make a payment to his account to finish his job because of financial restrictions at place.
So I think I have a fancy looking brick now.
i have the same problem , on my Note 11E pro , stuck on fastboot , any luck ?
viruskn said:
i have the same problem , on my Note 11E pro , stuck on fastboot , any luck ?
Click to expand...
Click to collapse
The guys who repair phones in my town found to be able to fix this kind of a problem as well, but that required physically opening the phone and doing some programming.
And I am still waiting to get help from them. 3 months have passed. Pinged them ~20 times. Each time there's either no answer or a single Yes, but when I give them the connection details, they go completely silent.