okie, gonna try it now. So I'll restart my com, run mi flash beta, boot up my phone, power it down, edl mode it, then plug it in, right?
Xiaomi Mi Max - Part 2
- Thread starter amazingone
- Start date
okie, gonna try it now. So I'll restart my com, run mi flash beta, boot up my phone, power it down, edl mode it, then plug it in, right?
No need restart computer, but if you want to restart also can.
Yes, start the miflash beta first.
Unplug your mi max first from computer, simply press and hold the vol +, vol - and power button again to restart it as edl mode (vibrate let it go). then connect.
Update: feedback after you manage to see the COM:xx on miflash beta (click on refresh button of course)
Last edited:
yupp just tried that. Miflash beta on, restarted mi max, put it to EDL mode, plugged in, clicked refresh, nothing happened. unplugged, plug back in, error - unable to detect
yupp just tried that. Miflash beta on, restarted mi max, put it to EDL mode, plugged in, clicked refresh, nothing happened. unplugged, plug back in, error - unable to detect
You mean you replugged in 2 times?
Update: sorry bro, I mean you plug in le refresh no luck and then you replugged in again??
Last edited:
yes, but i got the point about having to do a fresh EDL cycle when i want to plug it in. However, when I try to plug it in 'for the first time', nothing happens, even after I click on the refresh button on MiFlash Beta.
So what happens is, I hear the computer detect the plug in, but it's not recognised on the computer at all - like nothing happened.
You know to set up remote assistance on win8? I very eager to see what is really happening on your screen.
anyway try again. close the miflash beta. unplug your mi max, restart to edl mode. plug in only first time and wait for it (just wait a while). Check on your device manager and you should have like the below picture.
after you got this, open miflash beta, then refresh on miflash beta.
Update: If don't have then, follow up on bro kelvinti on the adb again, since you like did halfway thru.
Update 2: if the device manager shows "QHSUSB_BULK" means driver not install. just install the driver by pointing it to download qualcomm folder.
after you got this, open miflash beta, then refresh on miflash beta.
Update: If don't have then, follow up on bro kelvinti on the adb again, since you like did halfway thru.
Update 2: if the device manager shows "QHSUSB_BULK" means driver not install. just install the driver by pointing it to download qualcomm folder.
Last edited:
1982-1994
Great Supremacy Member
- Joined
- Oct 10, 2016
- Messages
- 59,386
- Reaction score
- 30,601
just look for it on carousell.
got one shop at TPY central selling it.
still waiting for his reply on price and availability.
UPDATE!
I uninstalled miflash, and reinstalled in in another location - now I CAN DETECT THE PHONE! (omg its like i got a promotion) but tried flashing, there was an error - "can not found programmer file". So I am now trying to re extract the MIUI files into another location as well. Lets see if that works.
lol ic, good for you, so unexpected. try to extract at the C: or D: HDD root directory.
Update: wait! did miflash shows something like "COM:10" under id? just to double check, because it won't work if it doesn't shows COM:xx
Last edited:
hmmmm try to rename the rom folder without spaces. the flashing programs doesn't like it. try then let me know
mmm. changed the usb port, renamed the master folder, but it still says: Can not read from com port 4.
To be sure, do you point the miflash beta to the master folder, or one of the folders inside? There are 3 inside: "Cust", "firmware-update" and "META-INF".
Point to the master folder.
OK some tricky part about this mi flash. you change to another USB port (assume you restart edl mode) you need to refresh again as the COM:xx changes with another diff usb port. If refresh that time error, you need to relaunch the miflash.
refresh ar, not reflash ar.
Wow! At least can see COMXX on the miflash now... Getting closer....
Ya in the end, miflash installed location issue, plus he did not restart edl mode when replugged.
Pretty lame to see that though, least expected.
Edit: i mean the installation location issue. As for the edl restart every replug, i think i did came across just that never really bother to look at it, since is like always work on first try.
Last edited:
tried that - still same error. "Can not read from port COM4".
OK. now before you do anything for flashing again. Restart your computer and try again. If cannot, please continue on the adb thingy that you tried earlier on, it seems like halfway didn't finished.
kelvinti
Arch-Supremacy Member
- Joined
- Jan 5, 2009
- Messages
- 23,268
- Reaction score
- 2,433
Ya in the end, miflash installed location issue, plus he did not restart edl mode when replugged.
Pretty lame to see that though, least expected.
Haha!
For myself, the lame incident was that the official miFlash worked with my previous Win10 pc flashing the Mi Max.
Now, I have a new Win10 pc, and strangely, only the MiFLash beta works . The official miFlash version doesn't work with my new Win10 PC now!
So, could it be the miFlash version issue now since he is able to see the COMxx but flashing failed right at the start?
>> Cokiee,
What is the name and version of your MiFlash?
Last edited:
Haha!
For myself, the lame incident was that the official miFlash worked with my previous Win10 pc flashing the Mi Max.
Now, I have a new Win10 pc, and strangely, only the MiFLash beta works . The official miFlash version doesn't work with my new Win10 PC now!
So, could it be the miFlash version issue now since he is able to see the COMxx but flashing failed right at the start?
>> Cokiee,
What is your name and version of MiFlash?
Oooooo lol. That time still recall you keep saying official works. Hahaha
Hmmmmm wait. Maybe he using official miflash as of now?
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ Forums. Forum members and moderators are responsible for their own posts.
Please refer to our Community Guidelines and Standards and Terms and Conditions for more information.
