Hard bricked device. MiFlash 'hello packet' error - Xiaomi Redmi Note 5 Pro Questions & Answers

I recently unlocked bootloader, so I installed Red Wolf Team Recovery. After that, I flashed MIUI 10 zip update via recovery and after restarting my phone, it got hard brick. I'm trying to flash 9.5.19 and 8.8.6 using Mi Flash but I get 'Can not receive hello packet' error and then 'timed out' error.
Drivers are installed. Tried with different ports but I get the same error. Also tried touching power on button but nothing changes.
Any way to solve it?
EDIT: Now I receive this error:
Only nop and sig tag can be recevied before authentication.
It seems that I need an authorized account for using MiFlash. Any alternative?
I don't have any type of Xiaomi Service Center in my country, only can contact to my reseller for guarantee but I don't know if its covered.

Search, read.. You have to hold power button for like 10s, not just touch it

Incogn said:
Search, read.. You have to hold power button for like 10s, not just touch it
Click to expand...
Click to collapse
Now I receive this error:
Only nop and sig tag can be received before authentication.
Edit: It seems that I need an authorized account to flash (tried with other version of Mi Flash). Where do I get it?

Literally half of this forum is filled with topics about this exact issue. Read around. Looks like you have ARB brick.

Which miui was there before you installed twrp?

UtkuAblak said:
Which miui was there before you installed twrp?
Click to expand...
Click to collapse
MIUI 9.5.17

Letrix said:
MIUI 9.5.17
Click to expand...
Click to collapse
long press power button fro 10-20 seconds . it will reboot. now hold down volume button during reboot to enter fastboot. if you can enter fastboot, your device is not arb bricked.

arunmohan16 said:
long press power button fro 10-20 seconds . it will reboot. now hold down volume button during reboot to enter fastboot. if you can enter fastboot, your device is not arb bricked.
Click to expand...
Click to collapse
It's hard brick. It doesn't do nothing. Only is recognized by PC as Qualcoom 9008 but now it's asking for authentication in my account. Is there any way to authorize my account?

Letrix said:
It's hard brick. It doesn't do nothing. Only is recognized by PC as Qualcoom 9008 but now it's asking for authentication in my account. Is there any way to authorize my account?
Click to expand...
Click to collapse
Mi authorized account is hard to get. check mi russian and english forums. sometimes they will open forum for collecting Mi account number for authorization. If you are in warranty, check service center and they will replace the motherboard.

arunmohan16 said:
Mi authorized account is hard to get. check mi russian and english forums. sometimes they will open forum for collecting Mi account number for authorization. If you are in warranty, check service center and they will replace the motherboard.
Click to expand...
Click to collapse
It's covered by guarantee? I'm from Argentina and the guarantee that I have received is a mandatory one for six months.

Install app ver. 2018.5.28 and try again , asks for user and pass.
You can ask for authorization in Russian forum miui.
Good luck

I wonder why did you installed redwolf recovery to flash miui10. Don't you know, you can flash miui10 using mi recovery??

SunilSuni said:
I wonder why did you installed redwolf recovery to flash miui10. Don't you know, you can flash miui10 using mi recovery??
Click to expand...
Click to collapse
Agreed: normally you flash/update your device via miflash (or OTA). Then you can flash RedWolf (for root) and enable an option for getting MIUI OTA updates.
What I wanted to say is, it's interesting how you got the hardbrick: reversing from ARB v.4 to v.4 or vice versa (v.3 to v.3) shouldn't be a problem whatsoever. Even if your firmware is on version v.4 (use fastboot getvar anti for your version) you shouldn't have any problems (at least with custom roms).
I'm still wondering how you got the hardbrick. I red pretty much every post here, maybe I have overlooked something.

SunilSuni said:
I wonder why did you installed redwolf recovery to flash miui10. Don't you know, you can flash miui10 using mi recovery??
Click to expand...
Click to collapse
I didn't know it in that moment.

the thing is you were on 9.5.17 which has arb version 3 and u were trying to install miui 10 dev rom which got arb version 4....so u shouldnt get arb brick at the first place...there is something wrong...were you flashing global dev over china stable?

sayedquadir said:
the thing is you were on 9.5.17 which has arb version 3 and u were trying to install miui 10 dev rom which got arb version 4....so u shouldnt get arb brick at the first place...there is something wrong...were you flashing global dev over china stable?
Click to expand...
Click to collapse
They never post what they did exactly all they post is their phone got bricked because of ARB and start bashing Xiaomi.
Thing is it's highly impossible to brick a device while switching from ARB 3 ROM to ARB 4 ROM and most of the people thinking as developers after watching some freaking useless YouTube video

SunilSuni said:
They never post what they did exactly all they post is their phone got bricked because of ARB and start bashing Xiaomi.
Thing is it's highly impossible to brick a device while switching from ARB 3 ROM to ARB 4 ROM and most of the people thinking as developers after watching some freaking useless YouTube video
Click to expand...
Click to collapse
It's called a mistake? and if it was any other phone then he could probably quite easily recover his phone in minutes. But no, the REASON why he is in this position is because of Xiaomi's stupid ass restrictions so yes. That's why we all bash Xiaomi because this bs they've done to our phones is they're fault. It's like trying to upgrade your cars radio, but you make a mistake so the car turns into a massive brick and you can't use it unless the manufacturer approves of it. But that could be weeks or never because the manufacturer is now poo'n all over its community that put them there in the first place

So, the summary is, if you followed a ROM update guide, which does not mention the issue, flashed the linked and wrong ROM version and bricked the phone, it is gone, unless a "service center" replaces the motherboard? That's beyond ridiculous, really.
And yeah, there are a million threads about the issue, and not a single coherent guide.

Related

i guess i somewhat kinda bricked my nitrogen, please help out

So, somebody please help me. I had the chinese rom. fully updated.
I have no idea wich version it was but i belive most likely it was the last one since i got the telephone last week and updated it.
so, coming from mi max 1 and then mi max 2 i installed TWRP and booted into recovery
and tried to flash eu global rom but it came out as an error and i downloaded a few roms and tried but no sucess in flashing them and then suddenly the screen went black and i can hear it connect and it will show up in miflash but as for now i dont have the recovery files
and am downloading them at the moment.
I remember running into a similar issue on my mimax 2 or 1 and then i needed to flash it using adb and running the flash system commandoes.
But i forgot them and im sure some of you have done this so can anyone help me finding a recovery fastboot files and give me a either miflash supported file to use or adb files and then the commandoes to flash it all back?
it was something like
system flash
recovery flash
boot flash
etc
But i dont have the files for recovery fastboot
and the commandoes are lost for me.
It was like flashing in EDL mode i belive, if i can remember,
I really screwed up and since the telephone is so new its hard to find the files needed.
Thank you and please excuse my bad English.
The one getting me back ill paypal you a beer.
veralynn said:
i downloaded a few roms and tried but no sucess in flashing them and then suddenly the screen went black
Click to expand...
Click to collapse
Which other roms did you try to install?
Latest china official roms have Anti-rollback enabled, so you have to be careful about what rom you trying to install otherwise your device will be hard bricked (if not bricked already).
If your device has bricked by anti-rollback, you need to flash in EDL mode, but EDL mode is blocked on Mi Max 3, so you need a Xiaomi EDL authorized account to flash with it.
Anyway, here is the link of the latest fastboot china stable rom http://bigota.d.miui.com/V9.6.12.0....EDCNFD_20180820.0000.00_8.1_cn_5e8d0ddf88.tgz
You can give it a try with MiFlash Tool.
My max 3 was bricked as well on Sat, no boot, no recovery, no fastboot.
You just need to download the fastboot of 8.9.20 china dev, install Qualcomm driver, then use Miflash to flash ur phone again in EDL mode. That's all.
dinhvtai said:
My max 3 was bricked as well on Sat, no boot, no recovery, no fastboot.
You just need to download the fastboot of 8.9.20 china dev, install Qualcomm driver, then use Miflash to flash ur phone again in EDL mode. That's all.
Click to expand...
Click to collapse
Can you help me findig the link to dev rom?
I am really really lost..
Been at this things for 24 hours now, and i was working on my fiancees phone at the same time so after twrp my own i did his, and then of course we both have black screens now in download mode, and there is nothing i have done that
will get me back to fastboot or to twrp.
If i hold in power it just kinda restarts download mode i can hear on my computer as it make the Plug in plug out sound from the Usb.
I have already gotten a lot of ugly stare downs from my fiancee now and i really cannot afford buying two new phones and of course i shouldnt need to either as since they are in black screen download mode they can be flashed, but i need the file you sir are talking about and also if you can say wich kind of miflash you used and etc i would be very happy and im seriuous about that paypal buying you a beer and what not thing.
I am going on vacation in few days also so i desperately need the phones to work or its not gonna be any happy vacation and definetly not any "happy times" either. so please help out!!
I am also equipped with teamwiewer if necessary,
Also, i opened up my own telephone and tried shorting out the two connectors inside, "testpoint" but it didnt give any difference at all, and i am out of ideas.
And of course now it seems i have searched so long for the correct files i cant find anything any longer as im stuck.
so .- yeah. Please get me out of this mess.
this is the link of 8.9.20 (latest) dev fastboot: http://bigota.d.miui.com/8.9.20/nitrogen_images_8.9.20_20180920.0000.00_8.1_cn_7c2f993484.tgz
For MiFlash, just google "MiFlash 2018" and download the Portable version, that's enough.
For Qualcomm driver, google "QDLoader HS-USB Driver" and download/install it.
Make sure that you can enter the EDL mode, if you do it right, you will see the device as "Qualcomm 9008" (cannot remember exactly the name) and Miflash will recognize the COM port then you are good to move forward.
dinhvtai said:
this is the link of 8.9.20 (latest) dev fastboot: http://bigota.d.miui.com/8.9.20/nitrogen_images_8.9.20_20180920.0000.00_8.1_cn_7c2f993484.tgz
For MiFlash, just google "MiFlash 2018" and download the Portable version, that's enough.
For Qualcomm driver, google "QDLoader HS-USB Driver" and download/install it.
Make sure that you can enter the EDL mode, if you do it right, you will see the device as "Qualcomm 9008" (cannot remember exactly the name) and Miflash will recognize the COM port then you are good to move forward.
Click to expand...
Click to collapse
you just earned urself a beer.
i flashed my telephone sucessfully.
seems forgetting to log out of miaccount is a really dumb thing to do as i now cant flash my fiancees as his telephone is not binded to my laptop, and his is not been used before.
the miflash asked me to log in, wich was succesful but its stuck in edl autitenctation and has been now for a while.
but can i flash global rom now??
and if so, how can i do it and not brick it again?
im guessing you want more than one beer??
Fashing the other it says unautoriszed xiaomiaccount..
Solutions??
veralynn said:
you just earned urself a beer.
i flashed my telephone sucessfully.
seems forgetting to log out of miaccount is a really dumb thing to do as i now cant flash my fiancees as his telephone is not binded to my laptop, and his is not been used before.
the miflash asked me to log in, wich was succesful but its stuck in edl autitenctation and has been now for a while.
but can i flash global rom now??
and if so, how can i do it and not brick it again?
im guessing you want more than one beer??
Fashing the other it says unautoriszed xiaomiaccount..
Solutions??
Click to expand...
Click to collapse
Xiaomi has locked the account of the other phone, you need a Mi Authorized Account, which is not easy to find and is paid of course. Don't flash Global Stable over your China Dev, unless you unlocked bootloader officially. But you have the option to flash Xiaomi.eu rom, if your bootloader is unlocked. If not - don't.
veralynn said:
you just earned urself a beer.
i flashed my telephone sucessfully.
seems forgetting to log out of miaccount is a really dumb thing to do as i now cant flash my fiancees as his telephone is not binded to my laptop, and his is not been used before.
the miflash asked me to log in, wich was succesful but its stuck in edl autitenctation and has been now for a while.
but can i flash global rom now??
and if so, how can i do it and not brick it again?
im guessing you want more than one beer??
Fashing the other it says unautoriszed xiaomiaccount..
Solutions??
Click to expand...
Click to collapse
I do not really understand your current issue. A picture will be better? In case if you forgot to logout, it's ok, you just need to input the password of that account.
Anyway, you cannot flash Global stable 9.6.6 (MIUI 9) over the 8.9.20 (MIUI 10 - antirollback activated), it will brick again.
martin.burgas said:
Xiaomi has locked the account of the other phone, you need a Mi Authorized Account, which is not easy to find and is paid of course. Don't flash Global Stable over your China Dev, unless you unlocked bootloader officially. But you have the option to flash Xiaomi.eu rom, if your bootloader is unlocked. If not - don't.
Click to expand...
Click to collapse
Both telephones are unlocked by the belonging miaccounts.
I have run the unlock tool on them both of course before doing the TWRP and then someplace something got messed up, not sure yet and made me in this mess.
What i have done in difference on my phone and the other is that i have opened up mine and short circuited lol almost all check points inside it and after the last link mentioned here with the rom it worked.
but im not sure if it was the testpoint trick at all as that really didnt give any information about anything changed or not.
What im trying to do here now is to somehow flash this edl phone left back to china dev without me opening it up and do the testpoint wich i have no idea helped me or not.
I can try the unlock tool again see if it recognize any phones.
all help appreciated.
Try flashing China 8.8.30 of the other phone, maybe it will skip asking for Mi authorized acc. I have red somewhere it worked .
OK-
So i can hereby confirm that TESTPOINT is working.
So if you have bricked your phone into edl mode download mode and there is NO WAY you can flash it using miflash or twrp or anything, you can open it up and unplug the battery, short cut the testpoints wich in my case was my fumbling around everyone with a wire and then
retry connecting the battery and reflash.
I also tried testpoint with battery connected. I have NO IDEA if that was the case or not.
But i managed to get back my phones, but of course i nicked one screen so im guessing im gonna need to sell this and rebuy a new one with global as to keep the housepeace intact.
So- i will try and rewrite this into something that can be sticked to the front. Including pictures.
So, if I understand correctly, without the testpoint method, MiFlash was asking you for an authorized xiaomi account but with the testpoint there is no need for authorization?
panospc said:
So, if I understand correctly, without the testpoint method, MiFlash was asking you for an authorized xiaomi account but with the testpoint there is no need for authorization?
Click to expand...
Click to collapse
Well. Good question.
Seems like it doesn't need something else than unlock.
But verified account, its really not a big deal.
Just create a miaccount beforehand and wait the 500 or so hours to unlock.
If you screw up something just testpoint it.
But i was logged into the account on the telephone on miflash. But wasnt verified the laptop i used so i couldn't flash.
But with testpoint Wich was kinda nervewrecking i fixed them both. Again.
I will wait for global official rom before doing this again.
My mi Max 3 is unlocked and bricked. Computer detects it as 9008 and mi flash. When i flash 8.9.2 cn dev rom, it is stuck on dummy.img. It is stuck on dummy.img in other firmware versions as well. How can i fix it ?
Edit : solved by Flashing with QFIL.
Flashed mine to stock global rom.
I was so nervous as hell.
Downloaded the official global and didnt even have the nerves to twrp it.
Do i Flashed it using xiaomi mi flasher and it worked.
Dont feel like messing more with it now...
You didn't take a pic of the test points you shorted by any chance did you? I'm sure that will hep out some people.
Thanks
seti007 said:
You didn't take a pic of the test points you shorted by any chance did you? I'm sure that will hep out some people.
Thanks
Click to expand...
Click to collapse
Try my method before trying to open up your phone with test point method: https://forum.xda-developers.com/mi-max-3/how-to/to-youre-stuck-edl-mode-black-screen-t3837846/page2

Is it even possible to unbrick a locked bootloader Redmi note 5 pro in 2020?

i have literally searched everywhere and tried the methods but to no avail. There are some old methods but they dont work anymore.
i cant access recovery but i can access fastboot but since my bootloader is locked, i guess thats no use.
1. Official flash wont work because not a authorised mi account (if someone have this, please for love of god help a brother out).
2.Tried the famous anti test https://www.youtube.com/watch?v=Pf_pPCGkldI&app=desktop but stuck at "ACK count dont match" and i guess others have this issue too. Do anyone know what this error mean in first place?
service center guys is waiting to rip off money with new motherboard but there must be someone somewhere who have good knowledge about and tweak something to make it work.
tl;dr: please provide a working unbricking method for RN5pro (working in 2020)
Hey bro as u can access fastboot mode, can u unlock ur bootloader via unlock tool?
binarygod1299 said:
i have literally searched everywhere and tried the methods but to no avail. There are some old methods but they dont work anymore.
i cant access recovery but i can access fastboot but since my bootloader is locked, i guess thats no use.
1. Official flash wont work because not a authorised mi account (if someone have this, please for love of god help a brother out).
2.Tried the famous anti test
&app=desktop but stuck at "ACK count dont match" and i guess others have this issue too. Do anyone know what this error mean in first place?
service center guys is waiting to rip off money with new motherboard but there must be someone somewhere who have good knowledge about and tweak something to make it work.
tl;dr: please provide a working unbricking method for RN5pro (working in 2020)
Click to expand...
Click to collapse
Bro i also need this solution , please help me ??
---------- Post added at 09:07 AM ---------- Previous post was at 09:06 AM ----------
Sidgup1998 said:
Hey bro as u can access fastboot mode, can u unlock ur bootloader via unlock tool?
Click to expand...
Click to collapse
I can't because for this we should enable usb debugging and oem unlock from the settings , but how we can do that if mobile is stuck at mi logo ??
udaymaurya said:
Bro i also need this solution , please help me ??
---------- Post added at 09:07 AM ---------- Previous post was at 09:06 AM ----------
I can't because for this we should enable usb debugging and oem unlock from the settings , but how we can do that if mobile is stuck at mi logo ??
Click to expand...
Click to collapse
Actually i didn't do anything u mentioned to unlock my bootloader, u can give it a try
Sidgup1998 said:
Hey bro as u can access fastboot mode, can u unlock ur bootloader via unlock tool?
Click to expand...
Click to collapse
No, you cant do that. You need to set in developler settings first but since the phone is stuck, you can't do it which means you can't unlock bootloader now using miunlock. if this was possible, we wont be whacking brains in edl n stuffs.
source: i have tried it already n didnt work.
binarygod1299 said:
No, you cant do that. You need to set in developler settings first but since the phone is stuck, you can't do it which means you can't unlock bootloader now using miunlock. if this was possible, we wont be whacking brains in edl n stuffs.
source: i have tried it already n didnt work.
Click to expand...
Click to collapse
Good luck
Download latest MIUI fastboot ROM and flash it
simple.. and use anti test patch.. search on xda.
Good luck.
drnightshadow said:
Download latest MIUI fastboot ROM and flash it
simple.. and use anti test patch.. search on xda.
Good luck.
Click to expand...
Click to collapse
neither the anti test rom nor the anti test patch is working now. it used to work before. ppl getting the "ack count dnt match error" or simply other error. maybe xiaomi patched something .
binarygod1299 said:
neither the anti test rom nor the anti test patch is working now. it used to work before. ppl getting the "ack count dnt match error" or simply other error. maybe xiaomi patched something .
Click to expand...
Click to collapse
No no, if you get ack error you just need to power cycle the phone (hold power button for 20-30 sec).
Really easy just need to be patient and retry.
Trust me I done it last week on my friends phone.
Just don't give up.. take a break and try it again. I done it in 3rd try. And use patched firehouse file on original MIUI fastboot rom.
Good luck!
drnightshadow said:
No no, if you get ack error you just need to power cycle the phone (hold power button for 20-30 sec).
Really easy just need to be patient and retry.
Trust me I done it last week on my friends phone.
Just don't give up.. take a break and try it again. I done it in 3rd try. And use patched firehouse file on original MIUI fastboot rom.
Good luck!
Click to expand...
Click to collapse
may i ask which ph model did u fix?
also which version of mi flash di you use? di you open case n did test point method?
binarygod1299 said:
may i ask which ph model did u fix?
also which version of mi flash di you use? di you open case n did test point method?
Click to expand...
Click to collapse
1. It was global model
2. mi flash 2018
3. Not needed, as i could access to fastboot.
binarygod1299 said:
may i ask which ph model did u fix?
also which version of mi flash di you use? di you open case n did test point method?
Click to expand...
Click to collapse
I don't know if this help, I unlocked many Xiaomi devices and it usually takes a lot of wait time but I bought a RN5 Pro from second hand and when I tried to unlock it through Mi-Unlock Tool it did it instantly so it looks like Xiaomi don't care anymore for bothering on old devices, just in case you didn't try it previously.
Also it may help some screenshot as possible of your issue from the Mi Flash tool, I always used the Mi Flash tool Pro for unbrick purposes https://xiaomifirmware.com/downloads/miflashpro/ Have present that a device in this state is highly unresponsive so you have to try it a lot of times to get it working again changing always some things around.
Unlocked a Note 3 bricked like that back in the day using the EDL mode with MiFlash. Just a tip, don't know whether that'll work here.
Another tip: Don't buy any more Xiaomi devices.
Limetak said:
Unlocked a Note 3 bricked like that back in the day using the EDL mode with MiFlash. Just a tip, don't know whether that'll work here.
Another tip: Don't buy any more Xiaomi devices.
Click to expand...
Click to collapse
Yeahh Xiaomi's edl authentication is bull****.
Locked edl flashing (which they thought was a security measure) but they bundle miui with full of crap and data miners.
binarygod1299 said:
neither the anti test rom nor the anti test patch is working now. it used to work before. ppl getting the "ack count dnt match error" or simply other error. maybe xiaomi patched something .
Click to expand...
Click to collapse
did you manage to solve it? I am in your same condition! I can go to fastboot mode, edl but cannot flash anything neither with QFIL or MIFLASH same error ACK COUNT DONT MATCH Or Sahara Server connection! I am really desperate and disappointed!
supermike23 said:
did you manage to solve it? I am in your same condition! I can go to fastboot mode, edl but cannot flash anything neither with QFIL or MIFLASH same error ACK COUNT DONT MATCH Or Sahara Server connection! I am really desperate and disappointed!
Click to expand...
Click to collapse
Did you disconnect battery?? If not, do it and try again.
And try even with disconnect battery and try EDL.
Good luck!
drnightshadow said:
Did you disconnect battery?? If not, do it and try again.
And try even with disconnect battery and try EDL.
Good luck!
Click to expand...
Click to collapse
Yes I tried everything even miflash pro and miflash 2018, miflash 2017 and flashing old rom both global or china mode with or without the new ssd660.elf files or patchprogram etc. I tried with connected battery and no battery in EDL mode and nothing is working just error of ACK COUNT COULDN'T MATCH cannot flash anything even with QFIL di qualcomm such a shame for Xiaomi! I think EMMC is corrupted then. Can't think of any other reason!
How did you solve the issue now in 2021?
What did you do?
Was the phone only able to go to fastboot and edl mode or also recovery? Cause mine only MI LOGO, fastboot and EDL mode with locked bootloader and EDL mode only via test point with open back cover!
Thanks
ACK COUNT COULDN'T MATCH this warning is linked to a synchronization attempt between programming Computer and interface controller the data transfer rate needs to be HIGHER than normal USB serial link transfer rate it seems.
arpit.exe said:
ACK COUNT COULDN'T MATCH this warning is linked to a synchronization attempt between programming Computer and interface controller the data transfer rate needs to be HIGHER than normal USB serial link transfer rate it seems.
Click to expand...
Click to collapse
the bootloader needs to be unlocked first remember the WHYRED is an android device all android devices are based on linux kernel the flashing computer OS must have a core ADB support and linux terminal and a linux kernel to complete the job
I need help i tried flashing fastboot ROM with MIUI tool and now its stuck in bootloop also cant access bootloader

(HELP!!!) Accidentaly Locked Boot Loader on wiped and bricked phone

Hello,
The Xiaomi 9 SE Global Unlocked of my girlfriend was restarting a lot (restart loop) and I tried to flash a ROM but I accidentaly flashed and locked the mobile on a "MIUI version that can´t be installed on this device" (grus_global_images_V12.0.2.0.QFBMIXM_20200910.0000.00_10.0_global)
The problem is the phone was wiped and I cant unlock the phone now. What to do? I can´t flash another ROM or unlock it and I just have access to Recovery Mode and Fastboot mode.
Please any help would be greatly appreciated.
It´s 4 am where I live and I´ll go to bed... But Will read here as soon as I´m awake. Thanks a lot in advance.
Let me continue my story... I still need help.
I contacted an authorized and he helped me to EDL a flashed version and I reinstalled the MIUI 12.0.2 Global stable on the phone.
But the phone is still TURNING OFF BY ITSELF (this was the reason because I tried flashing it on the first place). I don´t know the cause but it does not seems to be a faulty battery. I heard the phone has Anti RollBack protection. Is it right?
So I need help on how to procced. I would like to RollBack it to MIUI 11 where I didn´t had this problems...
Unfortunately you can NEVER go back once you flash a ROM on Xiaomi devices. However that doesn't prevent you from flashing custom ROMs.
Though you still need to be careful, because once flashed there is no going back.
I recommend testing the ROM on an emulator before flashing it. Here is how.
Also don't forget to check for your rollback protection index and the ROM's index before flashing.
Follow this post and scroll down to "How to find rollback index of images".
XDHx86 said:
Unfortunately you can NEVER go back once you flash a ROM on Xiaomi devices. However that doesn't prevent you from flashing custom ROMs.
Though you still need to be careful, because once flashed there is no going back.
I recommend testing the ROM on an emulator before flashing it. Here is how.
Also don't forget to check for your rollback protection index and the ROM's index before flashing.
Follow this post and scroll down to "How to find rollback index of images".
Click to expand...
Click to collapse
what do you mean never? you can flash miui with miflash
giorgarasgr said:
what do you mean never? you can flash miui with miflash
Click to expand...
Click to collapse
You can read more about xiaomi anti-rollback here.

Question Bricked poco f3. I Need Help :(

Hello i recently bricked my phone (poco f3) and there is no firmware on the phone. when i boot up it shows the poco logo and instalntly opne fastboot, fastboot works but the mi recovery not., i tried to flash the global img and there is a error.it says failed reading sparse file , i researched what this means but i found nothing in the internet. so i want to ask you guys if you can help me with this problem. i have another question: what is the super.img?
michits said:
Hello i recently bricked my phone (poco f3) and there is no firmware on the phone. when i boot up it shows the poco logo and instalntly opne fastboot, fastboot works but the mi recovery not., i tried to flash the global img and there is a error.it says failed reading sparse file , i researched what this means but i found nothing in the internet. so i want to ask you guys if you can help me with this problem. i have another question: what is the super.img?
Click to expand...
Click to collapse
If Fastboot works, this means your phone is not bricked.
Just make sure your bootloader isn't relocked.
Then flash stock rom 12.5.1 using MiFlash, better than CMD command. You get to see errors in Miflash.
If it fails, then change USB port in your PC. ( USB ports on the back are recommended)
Good luck.
laid1995 said:
If Fastboot works, this means your phone is not bricked.
Just make sure your bootloader isn't relocked.
Then flash stock rom 12.5.1 using MiFlash, better than CMD command. You get to see errors in Miflash.
If it fails, then change USB port in your PC. ( USB ports on the back are recommended)
Good luck.
Click to expand...
Click to collapse
(i am a german) when i use the new mi flash then it says this:
michits said:
(i am a german) when i use the new mi flash then it says this:
Click to expand...
Click to collapse
I don't really know the exact fix for that.
Try using a newer/different version of MiFlash
this version works for me
laid1995 said:
I don't really know the exact fix for that.
Try using a newer/different version of MiFlash
Click to expand...
Click to collapse
michits said:
this version works for me
Click to expand...
Click to collapse
I'd suggest using a newer version. That could work though. Still, I highly recommend newer version. For the safety of your phone.
2015 version, that is so old
what if i flash all exept storage? and my main problem is it wont flash super.img
michits said:
(i am a german) when i use the new mi flash then it says this:
Click to expand...
Click to collapse
Dude we don't speak German you would have to use Google translate to tell us what it says in English. What did you do to your Poco f3 that bricked it? Do you have an unlocked bootloader? Because it looks to me like 20 threads a day are created for this phone by people who aren't actually into development but just want help, which is fine but it's not what xda is for.
Techguy777 said:
Dude we don't speak German you would have to use Google translate to tell us what it says in English. What did you do to your Poco f3 that bricked it? Do you have an unlocked bootloader? Because it looks to me like 20 threads a day are created for this phone by people who aren't actually into development but just want help, which is fine but it's not what xda is for.
Click to expand...
Click to collapse
Ok maybe make a "poco F3 bricked megathread" as to compress all threads into one?
michits said:
what if i flash all exept storage? and my main problem is it wont flash super.img
Click to expand...
Click to collapse
I haven't tried it dude. And I wouldn't. That could actually brick the phone. Older peograms may not agree with our A/B POCOF3 partitions.
michits said:
(i am a german) when i use the new mi flash then it says this:
Click to expand...
Click to collapse
This is super easy to fix. Take a look at this video.
never use clean all and lock option to avoid brick

Question Blackscreen after flashing FW

hello people, I have a black screen after flashing the FW and can't get out of it.
Battery is fully charged
Pressing key combinations doesn't help.
when the mobile phone is connected to the pc, there is a brief message that a device has been connected to the pc.
please urgently for help
thx
neroes said:
Pressing key combinations doesn't help.
Click to expand...
Click to collapse
Fastboot mode not working?
NOSS8 said:
Fastboot mode not working?
Click to expand...
Click to collapse
No ... pressing VOL+down dosnt work
fastboot devices
negativ
neroes said:
No ... pressing VOL+down dosnt work
fastboot devices
negativ
Click to expand...
Click to collapse
I sent you a PM
So just a Black Screen? No Recovery or Fastboot?
You might have to flash a ROM via EDL Mode... The unfortunate thing though is that it will cost you money, unless you still have Warranty...
You said your PC briefly says that your phone got connected. In Device Manager, does it say "Qualcomm 9008" ? That would indicate that your phones' SOC detected that the Bootloader isn't working, and so, instead booted into the EDL Mode (Emergency DownLoad Mode), which is a read-only Mode inside the SOC itself.
cyanGalaxy said:
So just a Black Screen? No Recovery or Fastboot?
You might have to flash a ROM via EDL Mode... The unfortunate thing though is that it will cost you money, unless you still have Warranty...
You said your PC briefly says that your phone got connected. In Device Manager, does it say "Qualcomm 9008" ? That would indicate that your phones' SOC detected that the Bootloader isn't working, and so, instead booted into the EDL Mode (Emergency DownLoad Mode), which is a read-only Mode inside the SOC itself.
Click to expand...
Click to collapse
is now fixed, yes was in EDL mode.
it's a shame that I didn't know about the guarantee... the phone is only 6 months old... now I've paid $25 to "unlock" it
neroes said:
is now fixed, yes was in EDL mode.
it's a shame that I didn't know about the guarantee... the phone is only 6 months old... now I've paid $25 to "unlock" it
Click to expand...
Click to collapse
Sorry about that.
What did you do to make that happen? From which FW to which FW did you upgrade to?
cyanGalaxy said:
Sorry about that.
What did you do to make that happen? From which FW to which FW did you upgrade to?
Click to expand...
Click to collapse
My mistake was to listen to someone else and downgrade the firmware
neroes said:
My mistake was to listen to someone else and downgrade the firmware
Click to expand...
Click to collapse
that is weird because noting shoould happen when you change firmware.did you use twrp or adb sideload via recovery?
neroes said:
My mistake was to listen to someone else and downgrade the firmware
Click to expand...
Click to collapse
Downgrading is not a problem if the instructions are followed correctly.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
This is why it is important to give as much detail as possible when asking a question.
If you had specified that the phone was less than 6 months old, I would have directed you to the warranty as suggested by CyanGalaxie.
Currently the guarantees are under contracted by Xiaomi and the returns are very bad (loss of the phone, broken screen, long delays, etc.).
In your case you got your phone back in 15 minutes, maybe it's better that way.
So I'm satisfied that it really worked within half an hour to "unlock" my cell phone again instead of sending it in etc.
I just tried to downgrade via sideload. that led to the EDL
All in all I'm glad that my cell phone is working again ... I'm just annoyed because I've been playing around with all sorts of cell phones for over 10 years and I couldn't figure it out myself
neroes said:
So I'm satisfied that it really worked within half an hour to "unlock" my cell phone again instead of sending it in etc.
I just tried to downgrade via sideload. that led to the EDL
All in all I'm glad that my cell phone is working again ... I'm just annoyed because I've been playing around with all sorts of cell phones for over 10 years and I couldn't figure it out myself
Click to expand...
Click to collapse
The best way to downgrade is to use Miflash or the bat file (Fastboot rom)included in the rom folder to avoid ARB.
Phones have since changed, notably with dynamic and A/B partitions.
If you were trying to downgrade/upgrade the FW due to requirement/recommendation by your Custom ROM, you can simply flash the FW inside TWRP/OrangeFox.
cyanGalaxy said:
If you were trying to downgrade/upgrade the FW due to requirement/recommendation by your Custom ROM, you can simply flash the FW inside TWRP/OrangeFox.
Click to expand...
Click to collapse
This method to have the right firmware for for example an aosp rom does not always work sometimes it is necessary to flash the full rom.
For a version change on a stock rom use fastboot roms which contain all the imgs.
Yeah, stupid anti-rollback thing. Threads like these make me wish someone already unlocks the EDL flashing. I heard developers need some source code or something for it, I'm not sure. But that needs to happen ASAP.
It's totally evil to keep EDL restricted.
user0u said:
Yeah, stupid anti-rollback thing. Threads like these makes me wish someone already unlocks the EDL flashing. I heard developers need some source code or something for it, I'm not sure. But that needs to happen ASAP.
It's totally evil to keep EDL restricted.
Click to expand...
Click to collapse
For ARB okay but for EDL mode it's just a matter of security, you lose or your phone is stolen and just flash in edl mode and the phone is yours, no.
Then the guy will only be able to flash AOSP roms as he will be blocked by the Xiaomi account.
Note that this only concerns Qualcomm Socs,Mediatek are more less secure.
@NOSS8 We are modders and tinkerers here man. We were doing just fine before these restrictions. These restrictions have been added less for "security" and more to take control away from the end users anyway.
user0u said:
@NOSS8 We are modders and tinkerers here man. We were doing just fine before these restrictions. These restrictions have been added less for "security" and more to take control away from the end users anyway.
Click to expand...
Click to collapse
Not everyone is like you or me, there are thieves and crooks,otherwise we would be in a perfect world.
user0u said:
Yeah, stupid anti-rollback thing. Threads like these make me wish someone already unlocks the EDL flashing. I heard developers need some source code or something for it, I'm not sure. But that needs to happen ASAP.
It's totally evil to keep EDL restricted.
Click to expand...
Click to collapse
There are patched Firehose files (for QPST) on the internet (apparently circumvents the required Account authorisation). I can't provide a link, but you can google it.
But I'm not sure if those work, because I couldn't find one for Poco F3, and so I too had to pay 25$
It's very annoying that people buy into these pseudo-security lies we're getting fed so often (especially Apple Users). People don't realise this is not about protecting consumers, but simply for lé money. It has always been about the money.
Xiaomi locked the EDL Mode, because people kept buying their phones from China and import them to EU/USA, flash software with GMS and sell them here.
And locking EDL Mode causes more people to pay for Xiaomi Service Centres. xddd
I wish people would just have a healthy amount of criticism and not fanboy for any company, except for Valve. Valve is cool. Valve is love

Categories

Resources