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
Related
My son wanted to root his brand new phone. i have rooted 8 phones from different phones before with success..... but this time i f***d up...
Accedently installed this on his phone.
http://wccftech.com/flash-and-root-nexus-5-on-android-6-0-1-mmb29k/
executed flash-all.bat and it flashed the bootloader.
For the wrong phone...
It should have been this one..
http://wccftech.com/flash-and-root-nexus-5x-android-6-0-1/
Missed the X......
Now the phone will not even boot any more at all....cant enter bootloader.......does not power up at all.!!!
Jesus...what have i done.......
It here any chance at all to fix this somehow?
Hello and thank you for using Q/A,
because you can't enter bootloader, you can't do anything. You can try to send the phone to Google. Say: It didn't boot after OTA Update.
Kind regards
Trafalgar Square
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
well
hopesrequiem said:
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
Click to expand...
Click to collapse
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Only thing I know to use is a riff box to jtag it. Not sure if they have one for 5x.
crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Your use of the period seems rather condescending. And no, you as the end user cannot fix that. You did one of the few things that is unrecoverable unless you manage to get the bootloader to accept adb commands somehow.
crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Didn't you say the phone won't turn on? The above scenario is not possible.
Well
bobby janow said:
Didn't you say the phone won't turn on? The above scenario is not possible.
Click to expand...
Click to collapse
Well. the bootloader is flashed into the phone from the beginning aswell during manufacturing. I work with electronics and software and i know there is always a way to reflash the bootloader. All the electronics comes in the beginning with no software at all, one only needs the proper software/hardware. Most probably by jtag....or if they have some other special tool for snapdragon 808.
Stupid of me not to see that the version i flashed was not for nexus 5X...and only for nexus 5
sight...
Good luck. Will Google not rma it?
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
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
Just as a reminder: the MSM tool resets your device and locks the bootloader. If for whatever reason, you modified partitions that are not touched by the MSM tool (like param, persist, etc), there is a chance your device will fail the integrity check and will not boot with the red message "Your device is corrupt". If you're at this stage, there is no good way to get you back. Maybe someone knows how to toggle "enable oem unlock" without being able to boot to OS, but without that ability, your device is essentially hard bricked.
Is it what happen to your device ? Hopefully you could recover ?
Steve0007 said:
Is it what happen to your device ? Hopefully you could recover ?
Click to expand...
Click to collapse
No, someone else's, we're trying to see if there's anything we can do via edl currently
craznazn said:
No, someone else's, we're trying to see if there's anything we can do via edl currently
Click to expand...
Click to collapse
Hope it's not a one way street...
craznazn said:
Just as a reminder: the MSM tool resets your device and locks the bootloader. If for whatever reason, you modified partitions that are not touched by the MSM tool (like param, persist, etc), there is a chance your device will fail the integrity check and will not boot with the red message "Your device is corrupt". If you're at this stage, there is no good way to get you back. Maybe someone knows how to toggle "enable oem unlock" without being able to boot to OS, but without that ability, your device is essentially hard bricked.
Click to expand...
Click to collapse
I came across the corrupt message twice during my rooting mission hold down pwr+vol up+vol down until it shut off, then held down all three buttons til it turns on and it went into bootloader mode. It did take several tries but it got there. Then I could oem lock/unlock and reboot to a fresh system. Now I didn't mess with my partitions so maybe that is something deeper but it's worth a try.
hllywd said:
I came across the corrupt message twice during my rooting mission hold down pwr+vol up+vol down until it shut off, then held down all three buttons til it turns on and it went into bootloader mode. It did take several tries but it got there. Then I could oem lock/unlock and reboot to a fresh system. Now I didn't mess with my partitions so maybe that is something deeper but it's worth a try.
Click to expand...
Click to collapse
Yeah, we can get to the bootloader and EDL mode. However, we can't fastboot oem lock/unlock because OEM lock/unlock option is not togged in the System -> Dev options -> OEM Unlocking. This is a T-Mobile device, so not only that, we need to flash cust-unlock first which is not possible with OEM unlocking disabled in dev options.
avid_droid said:
Looks like I won't be doing the Tmo to EU. Looks like root will suffice until MSM for 2127 is released. I'm just wanting my camera updated to the latest and couldn't get it on unrooted. Waiting for my token, will use your magusk patch and update my camera. Thanks for the warning
Click to expand...
Click to collapse
The MSM for the 2127 is actually available now via remote support, just nobody has posted it online yet. That's where this warning comes from. Another user was able to run the 2127 MSM on his phone, and now it's bricked
I thought there was a command for the oem tick switch?
This is essentially what happened to my device! I ended up just returning it as I was in The 15day return window. Waiting on a refund now
ssjucrono said:
This is essentially what happened to my device! I ended up just returning it as I was in The 15day return window. Waiting on a refund now
Click to expand...
Click to collapse
When did this happen? What device did you have?
craznazn said:
When did this happen? What device did you have?
Click to expand...
Click to collapse
Oneplus 9 pro green 256gb. Happened last Wednesday
craznazn said:
Just as a reminder: the MSM tool resets your device and locks the bootloader. If for whatever reason, you modified partitions that are not touched by the MSM tool (like param, persist, etc), there is a chance your device will fail the integrity check and will not boot with the red message "Your device is corrupt". If you're at this stage, there is no good way to get you back. Maybe someone knows how to toggle "enable oem unlock" without being able to boot to OS, but without that ability, your device is essentially hard bricked.
Click to expand...
Click to collapse
Might be a good idea to update the thread title as it's misleading. Makes it look like the normal MSM tool is going F someone's normal variant device. Most people don't have the crappy T-Mobile variant. I understand saving a quick Buck is important though.
avid_droid said:
Looks like I won't be doing the Tmo to EU. Looks like root will suffice until MSM for 2127 is released. I'm just wanting my camera updated to the latest and couldn't get it on unrooted. Waiting for my token, will use your magusk patch and update my camera. Thanks for the warning
Click to expand...
Click to collapse
Is this the Camera app from APKmirror? The one that you'd have to move to... privapp, I think? Because they failed to sign it correctly?
avid_droid said:
Don't understand when people say "save a quick buck on Tmo," when it's exactly the same $1069 right across. It's about getting it in hand instead of waiting for shipping. And the thread is not misleading as it is for the 2127 which is the Tmo variant but it doesn't say that haha
Click to expand...
Click to collapse
Clearly is misleading because he doesn't put T-Mobile in the thread title.
I'd gladly wait up to 2 weeks to get a device that has timely updates and easily has up-to-date development..
avid_droid said:
Yes. Root is needed.
Click to expand...
Click to collapse
How is it so far? Is it worth trying out?
Burt Squirtz said:
Clearly is misleading because he doesn't put T-Mobile in the thread title.
I'd gladly wait up to 2 weeks to get a device that has timely updates and easily has up-to-date development..
Click to expand...
Click to collapse
It's not misleading, because ANY device where you modify a partition that is not usually touched my the MSM tool can result in a hard brick if it's checked by avb
avid_droid said:
@craznazn , it's only if you edit partitions correct? My unlock token should be here in a few days and plan on only rooting for a couple apps. This won't affect my re-locking would it?
Click to expand...
Click to collapse
Rooting only touches the boot partition and that's fine. Even flashing AA/BA/DA is fine because all of those partitions will just get overwritten by the MSM. Things only start to get dicey when you start messing with param, persist, and the likes.
craznazn said:
Rooting only touches the boot partition and that's fine. Even flashing AA/BA/DA is fine because all of those partitions will just get overwritten by the MSM. Things only start to get dicey when you start messing with param, persist, and the likes.
Click to expand...
Click to collapse
Just theoretical question: would flashing the device to something else like LineageOS (if there was working version) help? Or is the partitions check on HW/FW level?
drozd128 said:
Just theoretical question: would flashing the device to something else like LineageOS (if there was working version) help? Or is the partitions check on HW/FW level?
Click to expand...
Click to collapse
Once the bl is locked due to msm, you can't flash anything again.
craznazn said:
Once the bl is locked due to msm, you can't flash anything again.
Click to expand...
Click to collapse
I see. Thank you.
Follow and complain here.
Let ASUS know their bootloader implementation is VERY NOT FRIENDLY to us. I've been modding my Android devices since the Android 2 era and this is the first time I encountered an UNOFFICIALLY UNRECOVERABLE state which is a HORRIBLE experience.
Me? Have played with
Samsung(S5 to S9 and Tab/Odin is a good thing)
XiaomiRedmiPoco(Main device for me today, very modder friendly and robust)
Huawei(Remember when they allow applying for BL unlock?)
Apple(LOL jailbreak from A4 SoC until iPhone X(meantime Samsung S8 looks gorgeous) lost my interest)
And various small brands or exited market big brands(honorable mention Lenovo LePhone C101. My first smart device/Android and received big community support at the good old time)
ASUS. Fix your buggy BL. Fix your policy. Release everything we need to fix OUR DEVICES of OURSELVES. Just ONE step closer to perfect.
Just imagine how stupid is this:
Everytime you want to update you operating system, your UEFI/BIOS firmware might break.
And worse, that you don't have free official resources to fix it?
And can it be worse? Yes! Your Warranty is maybe void because you may unlocked bootloader, now supposedly only ASUS service center have the file to fix it.
Ha now it's interesting. That's the era of ANTITRUST. Even Apple won't do it(Worst case DFU, easily fixable using OFFICIAL iTunes).
WT*?
yeah dude i'm bricked up rn
Paid here, paid there.
Yeah sure.
Exploit people.
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
EDIT: quoted content removed.
Never use this firmware, because it has not been modified, 100% of fingerprints and IMEI will be lost after use. You need to modify the firmware before you can flash it.
mahdibassam said:
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
Click to expand...
Click to collapse
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
iMoc said:
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
Click to expand...
Click to collapse
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
mahdibassam said:
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
Click to expand...
Click to collapse
1\ The fastboot code in their bootloader have bugs, any CORRECT command you type can easily break bootloader then stuck you in 9008.
2\ The normal update method failed because THEIR UPDATER did do things wrong.
3\ They refuse to provide official ROM to let yourself fix it. SEND IT TO ME TO FIX IT, AND I MIGHT CHARGE YOU SOME.
....\
N\ You go talk to Apple about it because they are experts about saying YOU USED IT WRONG.
Anyone asked for help gets it for free so far.
All devs on my chat group agree at least fastboot flashable should be available on the official download page.
MOD EDIT: off topic content removed
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
insideoft said:
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
Click to expand...
Click to collapse
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Moderator Information
Hello everyone,
I have cleaned the thread from off topic contents and posts. Please focus on problem solving related discussion, not finger pointing or flaming each other. We all come here to solve the issues and learn some new stuffs.
Thanks.
iMoc said:
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Click to expand...
Click to collapse
Sorry long time ago since I was into this stuff previosly.
That fixed it, thanks for the help!
same here