Hello everyone,
I bricked my Z2 Pro and after hours of searching and trying to fix it by flashing stock ROM via EDL I'm desperate so I would be grateful for any help.
My Z2 came with some custom ROM from shop with 1.9 version on it without OTA so I decided to flash it with different ROM. I unlocked the bootloader, flashed TWRP and SU, but flashing Gedeon ROM via TWRP ended with an error (error code 7 or 11 if I remember correctly). So I decided to flash stock ROM following
this guide.
QFIL recognized the device correctly as Qualcomm HS-USB QDLoader 9008, but I kept receiving this error:
02:20:14: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
02:20:14: ERROR: function: sahara_main:854 Sahara protocol error
02:20:14: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
So I followed this guide that recommends to use MiFlash instead of QFIL.
After few unsuccessful updates (it wasn't able to open the port) it finally finished downloading the ROM (2.0.057 ST) with this message at the end: The operation completed successfully.(0x00000000: ApplyPatch sector NUM_DISK_SECTORS-1., offset 16, value CRC32(NUM_DISK_SECTORS-1.,92), size 4)
It took about 55s.
However after I unplugged Z2 from the USB cable and hit the power button, nothing happened. Since the update the screen is off, the LED light is off. Even if I hold the power off button for one minute.
When I plugged the phone back, it was still recognized as QDloader 9008, so it is apparently stuck in the EDL mode.
I tried all stock ROMs from here multiple times with the same result. Multiple times with the "successful update" message, but nothing happens.
EDIT: Now, after few tries the of the same process it is not even updating the ROM at all. It says "Open serial port failed" and afterwards "Missing hello packet, try to recover" (I waited about 5 min, but the message didn't change).
Please help
I hope for a solution without the need to unplug the battery, but if it will be necessary, I will do it.
Thank you!
Creshaw said:
Hello everyone,
I bricked my Z2 Pro and after hours of searching and trying to fix it by flashing stock ROM via EDL I'm desperate so I would be grateful for any help.
My Z2 came with some custom ROM from shop with 1.9 version on it without OTA so I decided to flash it with different ROM. I unlocked the bootloader, flashed TWRP and SU, but flashing Gedeon ROM via TWRP ended with an error (error code 7 or 11 if I remember correctly). So I decided to flash stock ROM following
this guide.
After few unsuccessful updates (although it recognized the device correctly as Qualcomm HS-USB QDLoader 9008, it wasn't able to access it via the relevant port) it finally updated the ROM (2.0.057 ST) with successful message at the end (the flash itself took about 55s). However after I unplugged Z2 from the USB cable and hit the power button, nothing happened. The screen is off, the LED light is off. Even if I hold the power off button for one minute.
When I plugged the phone back, it was still recognized as QDloader 9008, so it is apparently stuck in the EDL mode.
I tried all stock ROMs from here multiple times with the same result. Still successful update, but nothing happens.
Please help
I hope for a solution without the need to unplug the battery, but if it will be necessary, I would do it.
Thank you!
Click to expand...
Click to collapse
Can you verify if you followed step 1.1.2.
1.1.2 If you opend QFIL swich to the FireHoseConfiguration and enter the following settings:
syedtahir16 said:
Can you verify if you followed step 1.1.2.
1.1.2 If you opend QFIL swich to the FireHoseConfiguration and enter the following settings:
Click to expand...
Click to collapse
Yes, everything step by step. I even have the same version of QFIL (QPST is build 437 instead of suggested 434 - I suppose that won't be causing any problem). I tried to reboot my PC, different USB ports, reinstall drivers (as I previously had Lenovo USB driver and before the flash I installed the ZUK driver as well as without the ZUK drivers it wasn't recognized as QDLoader).
Zukfans.eu
Btw I'm unable to sign up to zukfans.eu to place my question there as well as. It asks for CAPTCHA verification, however there is no CAPTCHA shown, only the verification question "what zuk have you ?". I filled in there 'ZUK Z2 Pro', copied the question in there etc., used 4 different broswers on 2 devices and networks, no luck. And it is not possible to log in via FB as well.
I was working on it until 4AM last night and today I completely forgot to describe the important part about MiFlash
Please see in the original post.
Thanks for your your reply!
Creshaw said:
I was working on it until 4AM last night and today I completely forgot to describe the important part about MiFlash
Please see in the original post.
Thanks for your your reply!
Click to expand...
Click to collapse
I'm not sure about Miflash. I used QFIL.
Also, I wrote a small tutorial. See if that helps:
http://zukfans.eu/community/threads...rom-zuk-z2-pro-z2121-only.57/page-8#post-7282
If you are unable to use that link. Below is an extract:
"The QFIL zip contained the ROM twice. so you can load the contents.xml from the parent folder or the other folder within the zip too.
Make sure you extract the ROM in a short part i.e. "C:\Z2Pro\
1) Firstly, the tricky part having the tool recognize the qualcomm port.
Solution: Uninstall the tool, USB drivers (i.e. Zuk drivers), any existing qualcomm drivers.
Reboot.
Install Zuk drivers.
Install the tool. (According to the guide, the tool will also install the drivers for qualcomm, but for some reason it did not)
Install the qualcomm drivers.
2) Fortunately, my phone was not bricked. So I could easily get into edl mode using "adb reboot edl"
3) While trying to get this to work, some RELINK driver was installed instead of qualcomm. Uninstall that if you see that.
4) Anyway, back to our troubleshooting. So you would think that you are all set and your qualcomm port should be recognized, but no. It failed to recognize. So try this:
Reboot PC.
Reboot Phone.
5) Now Proceed. Hopefully by now you have see your qualcomm port. Great.
6) This is the trickiest part. You need to click on the "Download Content" "IMMEDIATELY" "AS SOON AS" you hit enter on "adb reboot edl".
[Image]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7) Yay. You see very nice progress in the little progress section on QFIL. You think you'ved nailed it.. But no, you could again end up getting another error. (Unfortunately I forgot to get a screenshot). Anyway, you would see this multiple times, that the "File access is very slow"; I'm not sure if only I received that error or if it is generic.
8) When you get an error at this point. Try a different port. Luckily, I got it to work on my second attempt on another attempt.
My review on the stock ROM:
Honestly, the custom ROM installed by the seller worked way better for me. This stock ROM had a lot of chinese apps (which of course I can uninstall). But somehow, the custom ROM from the seller felt better. Luckily I had a nandroid backup and I went back to it. The only drawback apart from OTA, being on the latest etc etc is that I cannot use the heartrate sensor (which is no big deal for me).
I guess I'll wait for another AOSP or another custom ROM or probably something with Android N before I upgrade again.
Hope this helps."
Thanks for getting back to me. I remember reading this before, however I cannot apply it to the current situation (but I tried anyway).
However there is an update to share. After some time I was able to go through the full download via MiFlash as before (with the 'successful' message) and moreover, flashing via QFIL finally started to produce something promising, however at the end it showed this message (no change to the state of the phone):
View attachment 131237287087498319.log
Next try showed the same error message as before:
View attachment 131237297946525488.log
SOLVED!
Hallelujah! After many many many tries (just doing the same over and over and over) the stock ROM (2.0.048) was finally uploaded (using QFIL)!
I was trying to hold power off and/or volume buttons while and after connecting to PC just to try different things and maybe that helped as well.
If someone will experience the same issue as me, I have one advice - don't loose your faith, don't give up!
And if you are thinking about flashing via MiFlash, simply just don't.
Creshaw said:
Hallelujah! After many many many tries (just doing the same over and over and over) the stock ROM (2.0.048) was finally uploaded (using QFIL)!
I was trying to hold power off and/or volume buttons while and after connecting to PC just to try different things and maybe that helped as well.
If someone will experience the same issue as me, I have one advice - don't loose your faith, don't give up!
And if you are thinking about flashing via MiFlash, simply just don't.
Click to expand...
Click to collapse
Glad you got it figured out! Enjoy your Z2 Pro
Hello there, I'm having a similar problem that the owner of this thread had, but the difference is that the adb doesn't detects my device.
I've tried to reinstall all the drivers, and downloaded the Android SDK tools, but still doesn't works...
Any idea about what to do? The device is with the screen in black, no led blinks or anything like that, and when connected to the PC, only detrects the Qualcomm 9008 port...
Thank you in advance.
Now after some research, I found out that the "ADB interface" is not showing in Windows device manager
I tried to install it manually, but can't find a way to get it working, and after the flash, USB debugging was set on, so can't figure out what could be happening...
Is it possible it's completely dead?
Any idea?
--
Thanks to valuable help from Emmaus and DanRO from zukfans.eu I managed to render my phone operable once more and now it runs flawlessly. This recovery is a life-saver for anyone experiencing bricking or malfunction issues:
https://yadi.sk/d/DfTYl-jz3Cxg76
_The first thing to do is to enter fastboot menu (pressing vol rockers will help)
_Then you will need to unlock bootloader with the dedicated commands:
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
fastboot -i 0x2b4c oem unlock-go
For noobs or newcomers: Be informed that you will need the OEM bootloader image from ZUK website through giving your credential and phone's serial number for unlocking, you can see the instructions on the forum or by googling it.
_After unlocking your bootloader you should flash the aforementioned and link-given recovery with the following commands:
fastboot -i 0x2b4c flash recovery twrp_name.img
(Replace "twrp_name" with the name of the downloaded image and without quotes)
_Once you successfully enter TWRP Recovery menu, you can either flash a TWRP-flashable file or else, by tapping reboot button you can select EDL (9008) option to open 9008 port on QPST for being able to flash any official firmware.
_Check your internal storage on flashing TWRP-flashable ROMs. In my case, after I flashed recovery and then a CM-based ROM (AICP), I saw that the phone had only a 9GB-size as internal storage. If you happen to face the same issue, just flash an official firmware on QPST, as this problem occurs due to bad partitioning, at least that is what it seems.
Ask anything for any further details.
Thanks.
Can't power off....help!
Hi all.
My Z2 Plus is old 4 day! Buyed from Gearbest, i flashed the latest stock CN Firmware with QFIL, unlocked bootloader, installed CN TWRP and flashed GizRom 1.1 from Franck076,
After this, i backupped all from TWRP and flashed Francko76 Global v7 and Mokee Official 7.1.1 for test. To return to normal use, i restored the backup GizChina Rom 1.1 and i rebooted.
DISASTER!
My Zuk Z2 screen is black, no flashing led, it's vibrate every 25/30 seconds andt there's no way that i can power off! I read so many guides to unbrick, but all say that the phone is switched off. In every tested so it continues to vibrate...
Please, help me!
Also I am Now Bricked
When Z2Pro was hung up during QFIL connection with EDL mode, It cannot but wait until battery empty because it does not reaction to the reboot with the VOL PowerBtn's switch either.
if Disassemble the Z2pro then remove buttery,maybe re-QFIL.
Anyone,want you to tell me if you know the method for reboot z2pro.whthout Disassemble it.
maofedeli said:
Hi all.
My Z2 Plus is old 4 day! Buyed from Gearbest, i flashed the latest stock CN Firmware with QFIL, unlocked bootloader, installed CN TWRP and flashed GizRom 1.1 from Franck076,
After this, i backupped all from TWRP and flashed Francko76 Global v7 and Mokee Official 7.1.1 for test. To return to normal use, i restored the backup GizChina Rom 1.1 and i rebooted.
DISASTER!
My Zuk Z2 screen is black, no flashing led, it's vibrate every 25/30 seconds andt there's no way that i can power off! I read so many guides to unbrick, but all say that the phone is switched off. In every tested so it continues to vibrate...
Please, help me!
Click to expand...
Click to collapse
Have you figured out a way?
Hi all,
received a Z2 pro, flashed with multi language rom, without OTA upgrades. When sim inserted, there was no connection to the network. After several attempts, i decided to send it back.
Ordered from another shop a new 2 ro, ( i know, very stupid to try twice) and this time, when tried to flash it from multi language rom, with an official one, it was bricked. Deep flash trick and.....
Tried several times to open HS-USB QDloader 9008 and once every 20 times it was a success. But, Sahara error all the time in qfil and hallo packet error in miflash. I'm out of ideas,.... Do you hve any?
Guys,
My ZUK Z2 Pro (bootloader unlocked) after finish loading the entire system (android) and appear the home screen, it reboots itself. When its boot it connected to PC, it does not reboot and after 5s I can remove cable and use it without problems. If the cable is in charge adapter, it also has the same problem.
Summary: I always need to turn on it connected in PC (with drivers installed) and wait 5s after finished loading all OS + startup APPs to not reboot alone. I install TWRP for good but no change to install custom ROM as it comes in loop after loading bootloader. Only ROMs that are stock, installed using QFIL works.
Do you have any idea?
Btw: I was using Mokee Rom without problems but after starting somes Frameworks apps te rom bricked out.
No 9008
Hello, i am new here and posted a reply in a different place. I think the wrong thread, so i will write here too.
I have a Zuk Z2 Pro. Unlocked bootloader, TWRP (twrp-3.2.1-0-z2_row.img) and installed several roms to try out. Then i read about a new ZUI and wanted to flash it. But, i made a mistake and now my phone is bricked. I read all about unbricking and flashing wit QFIL, but (and like others) my pc does not recognize my phone anymore. I can not work with adb (windows commands) and in QFIL i can not get the needed 9008 port. I installed all the needed stuff, but nothing.
Can someone help me out please. I already followed all the stept in some tutorials, but i get stuck with this 9008, which will not appear.
Phone does not start up. Recovery is gone, only menu with fastboot, recovery etc. is there. And the ZUI screen (from the rom i wanted to install) but the screen does not respond anymore, so i can not begin with setting the phone.
Is there a solution so i can flash with QFIL?
Or another solution?
Thanks,
Alex
Update 18-03-2018
This worked for me to get the needed 9008 port for flashing with QFIL:
- Open QFIL
- Phone must be off
- Connect usb cable to pc (not to phone yet)
- press volume up + power button and immediately connect usb cable to phone
- phone will vibrate 3 time (screen stays black/off)
- pc recognizes phone (there is this familiar sound of your pc)
- In QFIL you wil see port 9008
- just flash and wait till it's done
Off course you must have drivers etc installed on your pc, all the needed stuff for flashing. Don't forget to charge you phone.
I bricked my lenovo z2 plus, it is not booting to ROM or fastboot, it only vibrates after I hold the power button, and keeps vibrating every 10 sec, can anybody help me??
Thread Closed
tell what you did, to brick phone.
what android version was before, what android wersion you tried to instal, what recovery you used. ?
oh, but if fastboot isnt working, you more or less are done. if im correct, even dc phoenix use fastboot..
"Step 1
Write compatible UPDATE.APP file in fastboot with DC Phoenix"
Arnys said:
tell what you did, to brick phone.
what android version was before, what android wersion you tried to instal, what recovery you used. ?
oh, but if fastboot isnt working, you more or less are done. if im correct, even dc phoenix use fastboot..
"Step 1
Write compatible UPDATE.APP file in fastboot with DC Phoenix"
Click to expand...
Click to collapse
i just use the SRKTool Lod Chan and try to unlocked the bootloader
and it success , after that i proceed to replace recovery with TWRP
but doesn't work . afterwards i bring back to re-lock bootloader
then the phone reboot . the phone stuck at android boot logo
no recovery no fastboot cannot identify even in PC
but when the phone gets drain and i plugged the charger on it
the phone reboots directly into the system or its OS
but when i try to power it off again ( reboot )
the same thing happen it will stuck in the boot logo
until the battery dries again ,.
i never upgrade to Nougat so my phone still in Marshmallow version
thank you .
vinfrix said:
i just use the SRKTool Lod Chan and try to unlocked the bootloader
and it success , after that i proceed to replace recovery with TWRP
but doesn't work . afterwards i bring back to re-lock bootloader
then the phone reboot . the phone stuck at android boot logo
no recovery no fastboot cannot identify even in PC
but when the phone gets drain and i plugged the charger on it
the phone reboots directly into the system or its OS
but when i try to power it off again ( reboot )
the same thing happen it will stuck in the boot logo
until the battery dries again ,.
i never upgrade to Nougat so my phone still in Marshmallow version
thank you .
Click to expand...
Click to collapse
what wersion of twrp ? link. there are MM and N versions, and, if you on MM put N version twrp, you will brick phone.. and, even with dead battery i was able to enter fastboot, when i instaled wrong twrp. but for me solution was simple, instal right twrp and all was good (ofcorse if you didnt delete system)
i can't remember the version but im sure it all arounds in 2.1...something
no i wasn't load the Nougat version because i know i am MM the only thing i remember is the TWRP i load is from SRKTool Lod Chong there was an option there to install twrp recovery
can i be able to enter the fastboot ?
if i can go over to fastboot i can repair this
but i can't go fastboot
volume rocker technique doesn't work
even using adb reboot bootloader too
when i am doing volume down ( hold )
the phone only vibrates then stuck at logo
even when its connected to adb command
when the phone reboot it stuck at the logo
can't go to fastboot ?
is there any way of forced
reflash the boot.img & recovery.img?
Hi, i have P9 L19 with C432 B210 i want to update do Android 7, but mistakely put wrong UPDATE to phone memory. Now I'm stucked at Huawei logo and cant turn off device.
Only I can get to Fastboot&Rescue Mode. After press all three buttons nothing happened, phone juest restarts and stuck at logo. I tried put right UPDATE to SD card but no luck
Bootloader: locked
FRP: locked
debbuging: off
Please help me.
no one knows how to fix our problem so sad
Please close the thread
problem issue solved!
please help me same problem as you...
JCB117 said:
please help me same problem as you...
Click to expand...
Click to collapse
Easily Unbrick Your Phone via this method
https://forum.xda-developers.com/p9/help/huawei-p9-brick-easiest-to-unbrick-t3662350
Hello Xda community,
I need help badly , I bricked my phone one week after receiving it !! My goal was to install Clarity kernel for better battery performance.
I try to tell you all the steps and informations you will need to help me :
1 - I unloacked bootloader using Mi unlock.
2 - I installed TWRP 3.1.1-0 and root my device this way : LINK (method 2)
3 - I flash in recovery mode last MIUI rom 9.5.5.0, phone still running well after that
4 - I boot in recovery and flash this firmware in order to flash Clarity Kernel after
5 - After flashing the firmware I reboot and Im stuck at MIUI logo. I can go to fastboot mode though. But unable to reach recovery mode neither switch off the phone.
6 - I install MiFlash and tried to flash different version of rom MIUI santoni from official website (9.5.5.0 / 8.2.10.0) neither work SEE IMAGE I tried with mi flash 2016.08.30 same result
I get different status on mi flash, one is (image not matching device), even though I think I did everything well.
7 - Since last try of flashing my computer does not even recognise my phone in fastboot mode like before :/ and MiFlash doesn't see my phone :/
Please give me some advice/clue to revive my phone :crying:
In advance I thank you so much :good:
I use Windows 10 - 64 bits
try booting recovery from fastboot "fastboot boot *twrp image*.img"
Niaph said:
Hello Xda community,
I need help badly , I bricked my phone one week after receiving it !! My goal was to install..........
In advance I thank you so much :good:
I use Windows 10 - 64 bits
Click to expand...
Click to collapse
Well i am not at all an expert in miui, infact this is my first mi phone. But i think this tool called xiaomi adb/fastboot tool can help u. Google it.... It is available in reddit. One piece of general advice : before any kind of experiment always keep a preparation for the worst case scenario. I think ur phone is stuck at boot. U can try to hold the power button for about 10-15 seconds to turn off. Also just relax and have patience... It will b solved. Let me know how it goes.
Niaph said:
Hello Xda community,
I need help badly , I bricked my phone one week after receiving it !! My goal was to install Clarity kernel for better battery performance.
I try to tell you all the steps and informations you will need to help me :
1 - I unloacked bootloader using Mi unlock.
2 - I installed TWRP 3.1.1-0 and root my device this way : LINK (method 2)
3 - I flash in recovery mode last MIUI rom 9.5.5.0, phone still running well after that
4 - I boot in recovery and flash this firmware in order to flash Clarity Kernel after
5 - After flashing the firmware I reboot and Im stuck at MIUI logo. I can go to fastboot mode though. But unable to reach recovery mode neither switch off the phone.
6 - I install MiFlash and tried to flash different version of rom MIUI santoni from official website (9.5.5.0 / 8.2.10.0) neither work SEE IMAGE I tried with mi flash 2016.08.30 same result
I get different status on mi flash, one is (image not matching device), even though I think I did everything well.
7 - Since last try of flashing my computer does not even recognise my phone in fastboot mode like before :/ and MiFlash doesn't see my phone :/
Please give me some advice/clue to revive my phone :crying:
In advance I thank you so much :good:
I use Windows 10 - 64 bits
Click to expand...
Click to collapse
Nevermind I misread... If you think clarity or the firmware messed up your phone I could give you my kernel and firmware for you to restore it
Though if you're desperate for a solution, I'd transfer a ROM into your phone and start over with it, you can flash MIUI also by flashing https://drive.google.com/file/d/0ByWEieei-0nyMTR4R0dxWk9BTms/view after it
Your version of miflash is a little bit outdated! The last One is from may, last year if my memory doesnt fail. Install latest version of miflash and try to flash again stock ROM.
You can try also flashing stock ROM with miflash but in edl mode (emergency download mode) , instead of fastboot mode, but to do that you have to acess stock recovery, and then use this command " adb reboot edl", connect your phone to PC, and then see of detects, then flash then stock ROM. To acess stock recovery, press volume up + Power, if that not works, press volume up + volume down+ Power. Hope i helped
Ok I solved the problem using this method.
So I removed back cover, disconnected battery, connected the 2 points with a twizzer then flashed STOCK rom and it worked!! So relieved!
Thank you for the help anyway.
Speaker87 said:
Your version of miflash is a little bit outdated! The last One is from may, last year if my memory doesnt fail. Install latest version of miflash and try to flash again stock ROM.
You can try also flashing stock ROM with miflash but in edl mode (emergency download mode) , instead of fastboot mode, but to do that you have to acess stock recovery, and then use this command " adb reboot edl", connect your phone to PC, and then see of detects, then flash then stock ROM. To acess stock recovery, press volume up + Power, if that not works, press volume up + volume down+ Power. Hope i helped
Click to expand...
Click to collapse
Dear sir,
flashing redmi4 with miflash tool in edl shows me "object reference is not set to an instance of the object". Any solution please. This was second time i try flashing soft bricked redmi4 , first time few days ago flashed successfully and was using it properly in edl with miflash tool. Then During downloading update shown in setting by ota and rebooting it, and again got stuck on mi logo, means softbricked again.but try edl this time gives an error mentioned.
Speaker87 said:
Your version of miflash is a little bit outdated! The last One is from may, last year if my memory doesnt fail. Install latest version of miflash and try to flash again stock ROM.
You can try also flashing stock ROM with miflash but in edl mode (emergency download mode) , instead of fastboot mode, but to do that you have to acess stock recovery, and then use this command " adb reboot edl", connect your phone to PC, and then see of detects, then flash then stock ROM. To acess stock recovery, press volume up + Power, if that not works, press volume up + volume down+ Power. Hope i helped
Click to expand...
Click to collapse
chandan shah said:
Dear sir,
flashing redmi4 with miflash tool in edl shows me "object reference is not set to an instance of the object". Any solution please. This was second time i try flashing soft bricked redmi4 , first time few days ago flashed successfully and was using it properly in edl with miflash tool. Then During downloading update shown in setting by ota and rebooting it, and again got stuck on mi logo, means softbricked again.but try edl this time gives an error mentioned.
Click to expand...
Click to collapse
Problem solved.
I got revived my redmi 4 again from softbricked locked bootloader,
By trying an older rom
santoni_global_images_V8.2.12.0.MAMMIEA_20170629.0000.00_6.0_global_751410291c.tgz​With miflash-20220218 in edl mode .
Hello guys, so, today i was trying to install miui 9 in my mi a2, then later going to update to miui 10. I was trying to install by flash mode (XiaoMiFlash) Everything was going fine, until my windows accidently turned off for updates (RIP). When my pc turned on, i was desperately opening miflash as fast that i could, but then when i try to install again it was saying "cannot recieve hello packet". I tried to restart it thinking that would fix it, but its just stuck in a MI logo with mi.com screen(Bootloop). I was trying to unplug usb cable and then putting again trying to fix it, clicking refresh to see if it appears, but it doesn't. Same with fastboot mode, doesn't get recognized. I really need help to fix it and sorry if i wrote something wrong, english is not my native language.
Same problem happened with me today. Any Solution?
Are you able to boot into fastboot?
Something similar happened to me once with the A2.
I somehow too managed to interrupt some update process and got stuck in the same scenario.
I could resolve it by getting one of these now superseded fastboot stock files with some installer scripts in them.
The scripts also wouldn't work, but I could install the firmware files one by one manually, following the script's content.
First off though, you could try to get into fastboot mode (as mentioned before), boot the official twrp img and flash the latest firmware zip file from here
Then you could go ahead and flash miui for the A2 like any other custom ROM (or did you just post in the wrong section and actually got an 6X? - seeing that you used miflash, it really seems like it..
Just in case here is the right thread for downloading miui for the A2: A2 miui port)
Yaroray said:
Are you able to boot into fastboot?
Click to expand...
Click to collapse
Hey, sorry for not awnsering for a long time. Yes, i can enter in fastboot, but the problem is that my MI A2 doesn't get recognized. (nothing happens if i try to flash it in fastboot mode).
i same that trouble, i can try to bootloader but when i connect usb to my pc it not recognized, i don't run anycommand from my PC,
I think if i change to second slot i will boot my phone, and i want to change slot without command "fastboot set active-slot "