Develop Bugs

MiFlash - Trying to Unlock Bootloader

I'm starting to lose all hope in this device...
I bought my phone from, what I thought, was an official Xiaomi online store, my mistake, buyer beware, lesson learned. However. I have the phone, I like the form factor and all that, and the thought of trying to get a return from a Chinese company sounds like the kind of hassle I don't want to deal with. I'm well experienced in rooting/flashing devices (Nexus 5, OnePlus 2, OnePlus X, Xperia Z5c). I've done it a thousand times on these devices.
My new Mi5S came with "MIUI Global 8.6 | Stable 8.6.10.0(RM1100)" preinstalled.
I only found out after I bought it that the reseller installed this version. They apparently did this so they can make it a global rom. They installed Google play services, Play Store, removed chinese apps and made English the default language. That's great and all, but they also have the Locale setting locked in as China. It's unchangeable. And installing Google Launcher from the Play Store doesn't work (yet Pixel Launcher, downloaded from the web, works fine). Not a huge deal I guess.
Anyway, long story longer, I'm trying to unlock the bootloader.
I got permission, downloaded the Unlocker, VolDown+Power into Fastboot and ran the MiFlash unlocker.
It goes to 50% and then says "Couldn't verify device". That's where I'm stuck.
I've tried everything I can think of, and I just can't unlock the Bootloader.
Is anyone else having this same issue? Has anyone found a way to get TWRP on here?

Had the same issue when unlocking mine - two things worth checking: firstly, make sure the phone is signed in to the same Mi account that you have permission on (you can check it's "properly" linked by going to i.mi.com and clicking Find Device - if it shows as online, you're good). You don't need to use the Mi account at all after this, so once it's unlocked you can unlink and delete the account if you like.
Secondly, make sure the PC you're using has compatible ADB drivers on it - when it's linked by USB in FastBoot mode, make sure that it shows correctly in device manager. I had some weirdness with the previous global driver (still don't know why) and only ended up succeeding when I reinstalled straight from device manager.

MoonBuggy said:
Had the same issue when unlocking mine - two things worth checking: firstly, make sure the phone is signed in to the same Mi account that you have permission on (you can check it's "properly" linked by going to i.mi.com and clicking Find Device - if it shows as online, you're good). You don't need to use the Mi account at all after this, so once it's unlocked you can unlink and delete the account if you like.
Secondly, make sure the PC you're using has compatible ADB drivers on it - when it's linked by USB in FastBoot mode, make sure that it shows correctly in device manager. I had some weirdness with the previous global driver (still don't know why) and only ended up succeeding when I reinstalled straight from device manager.
Click to expand...
Click to collapse
I have verified that I'm using the proper account and that Mi Cloud sees my device as online.
Could you clarify which driver you ended up using?

You cannot unlock bootlader that easy. (Ive own mi5)... my english is not very good so i cannot describe all steps. Just find how to unlock mi5 bootloader. You have to request from xiaomi to let you unlock it. !!! AND I SEE NO PROBLEM HERE.

lummujaj said:
You cannot unlock bootlader that easy. (Ive own mi5)... my english is not very good so i cannot describe all steps. Just find how to unlock mi5 bootloader. You have to request from xiaomi to let you unlock it. !!! AND I SEE NO PROBLEM HERE.
Click to expand...
Click to collapse
I already have permission. Still doesn't work.

I used the driver from here: http://www.xiaomi.cn/content-19-6735-1.html - direct file link is http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar

So, check this out. I loaded up the Mi PC software and instead of just clicking on R.Flash, I held shift then clicked R.Flash. It popped up a file select box and I was able to choose the official chinese ROM. It then installed it! No issues or anything. Once it was finished and it booted, I did a factory reset. The initial setup screen ran and I got in to the phone. I installed the Google Play Installer from the Mi Store and that was that.
I now have 8.0.10.0.
Didn't need to unlock the bootloader or anything.
*phew*

dgrasley said:
So, check this out. I loaded up the Mi PC software and instead of just clicking on R.Flash, I held shift then clicked R.Flash. It popped up a file select box and I was able to choose the official chinese ROM. It then installed it! No issues or anything. Once it was finished and it booted, I did a factory reset. The initial setup screen ran and I got in to the phone. I installed the Google Play Installer from the Mi Store and that was that.
I now have 8.0.10.0.
Didn't need to unlock the bootloader or anything.
*phew*
Click to expand...
Click to collapse
You've actually completed the first step in unlocking your bootloader - you need to make sure you are using an official ROM and not a so called "Vendor ROM".
I am still waiting patiently for my Mi5s to get here...

If "fastboot devices" shows your mi5s in fastboot mode right before unlocking - then you have the right driver and the 50% problem should be solved.

CL0SeY said:
You've actually completed the first step in unlocking your bootloader - you need to make sure you are using an official ROM and not a so called "Vendor ROM".
You can unlock in vendor rom..
Without unlocking you should be able to flash official rom using miflash/fastboot
Vendor rom updater/recovery may not word (did not work for me) to update to official chinese rom..
Click to expand...
Click to collapse

MoonBuggy said:
I used the driver from here: http://www.xiaomi.cn/content-19-6735-1.html - direct file link is http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Click to expand...
Click to collapse
any funky method you have to install the driver? i am struggling here. adb is fine, but fastboot shows no devices. have tried every driver i can find including above!
edit - for the record i disabled driver signature verification in win10 and installed the above drivers, and still no luck. here is my cmd output
{
"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"
}
when it reboot into fastboot a new driver installed on windows and i can see the android bootloader interface in device manager but still no fastboot. weird? also miflash is showing the device when the phone is in fastboot.
---------- Post added 28th October 2016 at 00:33 ---------- Previous post was 27th October 2016 at 23:37 ----------
ok fixed the driver problem. for anyone else stumbling across this:
reboot to fastboot mode, then in device manager update the bootloader interface driver with the google driver that comes inside the C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Driver folder. (you need to have miflash installed obviously)
note that windows10 you may have to disable driver signature verification for this.
:good:

I got my phone today and had the same problem but i solved it at last, i installed the chinese dev rom and then it worked to unlock the bootloader and i have installed xiaomi.eu rom and works great.

I had the same issue, for me it was indeed the fastboot driver.
The solution for me was to put phone in fastboot, connected usb.
In device manager you have to look android bootloader interface, deinstall, and let windows install driver itself.
For me that was the solution...
From what i have read everywhere, using a windows 7 machine instead off windows 10 will solve the issue for sure

marcel112 said:
I had the same issue, for me it was indeed the fastboot driver.
The solution for me was to put phone in fastboot, connected usb.
In device manager you have to look android bootloader interface, deinstall, and let windows install driver itself.
For me that was the solution...
From what i have read everywhere, using a windows 7 machine instead off windows 10 will solve the issue for sure
Click to expand...
Click to collapse
What OS did you use when you successfully did this? Windows 10 or Windows 7 or other?

dgrasley said:
What OS did you use when you successfully did this? Windows 10 or Windows 7 or other?
Click to expand...
Click to collapse
I was using a windows 10 machine, but i didnt succeed severall times.
The thing i did was trying to unlock, 50% error, then boot the phone, turned off find Mi phone, rebooted, tried again still no go, rebooted again, tunred on find Mi phone again, then tried unlocking again...: Eureka!!
That was the solution, so i tried that on a different machine with no drives installed at all!!

How to full backup any qualcomm phone (no root)

Hi every body, I had reviced a lot of question about how to backup qualcomm devices. So today I will show you how! (test in Obi SF1)
Because if your phone is not root, you can't back up your rom in case brick when you play with the phone. So you will need this!!!
1: Download all necessary files (in my video description) put all of them in the same folder and extract out!
2: in stall the right driver (make sure your usb connect type is MTP)
When your phone and computer are connected and in devices manager you see some thing with a yellow triangle and the QFIL software show “no port available” that mean you need driver!
To install the driver, run qualcomm_Setup as administrator! Restart your computer. If success, no more yellow triangle in devices manager.
3: now put your phone into download mode by: install QPST.2.7.437 to your computer. Then run eMMC Software Download, chose switch device to DLOAD…> chose your phone >ok, now you will see several new hard disks in your computer , and in device manager you will see something like qualcomm emmc or qualcom mmc... in hard disk field! now close the eMMC Software Download software.
4: Run HDDRawCopy1.10Portable, chose Qualcomm MMC Storage USB Device (your phone flash) then click continue > double click on file > browse to pale you want to save the backup file > name the file, in file type field, chose raw img file > save > click continue and wait to complete (it may took along time depend on your memory size)
To wake up the phone out of download mode, just press all three hard buttons same time in 2 minutes !!! (for Obi phone, may different in other phones).
Link to this document in description too!
Attention: this method no need root, and you will have the full rom back up. But be careful if you chose wrong field you may miss your hard disk’s data, and when you apply the back up again to your phone your phone will really hard brick if you break the process. So if you had rooted the phone, use another method for better!!!
Guide video and tool links here:

If read back gets interrupted in between will it brick ?
Demon_king18 said:
Hi every body, I had reviced a lot of question about how to backup qualcomm devices. So today I will show you how! (test in Obi SF1)
Because if your phone is not root, you can't back up your rom in case brick when you play with the phone. So you will need this!!!
1: Download all necessary files (in my video description) put all of them in the same folder and extract out!
2: in stall the right driver (make sure your usb connect type is MTP)
When your phone and computer are connected and in devices manager you see some thing with a yellow triangle and the QFIL software show “no port available” that mean you need driver!
To install the driver, run qualcomm_Setup as administrator! Restart your computer. If success, no more yellow triangle in devices manager.
3: now put your phone into download mode by: install QPST.2.7.437 to your computer. Then run eMMC Software Download, chose switch device to DLOAD…> chose your phone >ok, now you will see several new hard disks in your computer , and in device manager you will see something like qualcomm emmc or qualcom mmc... in hard disk field! now close the eMMC Software Download software.
4: Run HDDRawCopy1.10Portable, chose Qualcomm MMC Storage USB Device (your phone flash) then click continue > double click on file > browse to pale you want to save the backup file > name the file, in file type field, chose raw img file > save > click continue and wait to complete (it may took along time depend on your memory size)
To wake up the phone out of download mode, just press all three hard buttons same time in 2 minutes !!! (for Obi phone, may different in other phones).
Link to this document in description too!
Attention: this method no need root, and you will have the full rom back up. But be careful if you chose wrong field you may miss your hard disk’s data, and when you apply the back up again to your phone your phone will really hard brick if you break the process. So if you had rooted the phone, use another method for better!!!
Guide video and tool links here:
Click to expand...
Click to collapse
Hi ,
Thanks for the video link. I want to use this so that I can get boot image and recovery image so that it can be ported . My phone is Gionee M6S plus Snapdragon chipset with locked boot loader. I would like to ask while In reading mode ,if by unforseen reason the readback gets interrupted ;is there any chance of hard bricking ?
Thanks

Suhi02 said:
Hi ,
Thanks for the video link. I want to use this so that I can get boot image and recovery image so that it can be ported . My phone is Gionee M6S plus Snapdragon chipset with locked boot loader. I would like to ask while In reading mode ,if by unforseen reason the readback gets interrupted ;is there any chance of hard bricking ?
Thanks
Click to expand...
Click to collapse
Nope, in backup process just don't format or delete any any thing in your phone's internal memory, your phone will be ok. But when you restore the phone, if the process broke, your phone maybe brick depen on how many percen had complete!

how to restore?

Hi,
thanks for this tutorial but i have a question, my device is Asus Zenfone 4 Selfie Lite ZB553KL (Sd425), i want to know how to wake my device from download mode before i start this tutorial as i dont want to brick my device

Can we backup full boot.img and system.img with that?
Or does it only backup data partition?

skeleton1911 said:
Can we backup full boot.img and system.img with that?
Or does it only backup data partition?
Click to expand...
Click to collapse
When you using this method, it will backup all of your partition: boot, recovery, efs, system, and user data too!

Rempoiiii said:
Hi,
thanks for this tutorial but i have a question, my device is Asus Zenfone 4 Selfie Lite ZB553KL (Sd425), i want to know how to wake my device from download mode before i start this tutorial as i dont want to brick my device
Click to expand...
Click to collapse
For my device (Obi Sf1) just long press (may up to 3 minutes) all of my 3 hard buttons to wake him up!

irwan_dcp said:
how to restore?
Click to expand...
Click to collapse
Sorry, my phone had lost, so i can't made a guide video for you. But there is a guide here: https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Hope usefull!

Nice tutorial but eroor 0x80004005 when pressing download mode
Nice tutorial thanks, but I'm getting error code 0x80004005 after pressing download mode, trying to backup huawei scl-l01 in QC 9008 mode port is visible drivers are ok

Hi @Demon_king18, sorry for bringing this old thread back up but I am having the same problem as @Provokuoji is.
When I open emmc software download app, and I try to switch to DLOAD, I get this message
{
"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"
}
This is the only thing stopping me for now. Might you know what is happening? :crying:

Hi @Demon_king18, sorry for bringing this old thread back up but I am having the same problem as @Provokuoji is.
When I open emmc software download app, and I try to switch to DLOAD, I get this message
This is the only thing stopping me for now. Might you know what is happening? :crying:

Getting the 0x80004005 error also. Any suggestion? The phone shows up as qualcomm device just fine.

find another way to boot into EDL mode. usually you have a timeout ~30 sec

Can we restore userdata with qfil ?

aIecxs said:
find another way to boot into EDL mode. usually you have a timeout ~30 sec
Click to expand...
Click to collapse
There is no other way to boot into EDL if your screen is completely blacked out and all what the computer recognises is a Qualcomm device in Device Manager.

deep flash cable? test point method?

aIecxs said:
deep flash cable? test point method?
Click to expand...
Click to collapse
I have a cable and it doesn't work.
I took my phone apart and did the test point shorting, that doesn't work either.
I have also been told that the phone is already in EDL mode but the problem is me getting that error message!

if it is already in EDL mode, just install Qualcomm HS-USB QDLoader 9008 Driver

aIecxs said:
if it is already in EDL mode, just install Qualcomm HS-USB QDLoader 9008 Driver
Click to expand...
Click to collapse
Done that from the start.

Possible Brick - Flashing Unlock Not Allowed

I've been reading through dozens of "bricked" threads for the last day, trying to figure this out, as I've been rooting/flashing android since the Hero and have managed not to brick anything in all those years. This is an unlocked Pixel 2XL bought from Google Store.
I unlocked the bootloader probably a year ago. I'd been rooted at one point, but after installing a security update around September I ended up leaving it stock.
Picked up a Pixel 3 and wanted to sell the Pixel 2. Confirmed I was all stock everything, and locked the bootloader. When trying to reboot after locking, I now get the "Can't find valid operating system. The device will not start" error.
I can access the fastboot menu, and my device is detected with fastboot devices. However, when I try "fastboot flashing unlock" or "unlock_critical" I get:
"FAILED (remote: 'Flashing Unlock is not allowed')"
I've tried Deuce's script, same errors.
Saw a suggestion regarding switching to the other partition, this errors out as well due to device being locked.
Tried booting into recovery from the Fastboot screen; it just goes to the "Can't find valid operating system" error screen with the only option being press power to power off so apparently my recovery partition is wiped as well. Also tried booting from the TWRP recovery image, this errors out due to device being in Lock State.
I have tried multiple PC's, USB cables, and USB slots. All have the same issue. Confirmed that I was using latest Platform Tools from Google as well.
My assumption is that I missed something and my device was not fully stock when I re-locked the bootloader. Before I give up hope and throw myself at the mercy of Google, I just thought I'd throw this up here to see if I missed something in one of the threads or if someone has any other ideas. Thanks!

So many cases from relocking the bootloader, guess i just leave it unlock then., care to share with us the method you use to return to stock ? did you use the Deuce script ?

Unfortunately I did not use the Deuce script. I just factory reset, flashed the December factory image with ADB, and then locked the bootloader (also with ADB).

I have exactly the same problem; have you found any solution? And will Google accept the device if it's under warranty knowing that the device was once unlocked?

ASMstudent said:
...will Google accept the device if it's under warranty knowing that the device was once unlocked?
Click to expand...
Click to collapse
Yes. Google is rather lenient in that regard.

That's good news!
Do they require a proof of purchase or a warranty card because I don't have either of them.
Sent from my PLK using Tapatalk

ASMstudent said:
That's good news!
Do they require a proof of purchase or a warranty card because I don't have either of them.
Click to expand...
Click to collapse
No proof of purchase means Google is not obligated to help you. You'll need to talk to them. On a side note, run the IMEI through imeipro.net's LG IMEI search engine so you know when the phone was manufactured, as that may be useful information in dealing with Google.

I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.
{
"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"
}
Sent from my PLK using Tapatalk

ASMstudent said:
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.
Click to expand...
Click to collapse
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else?

Badger50 said:
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else?
Click to expand...
Click to collapse
I was playing around hoping for some thing to change. I searched around and found out that LG ( the original ODM of pixel 2 xl) has a way to unbrick using download mode ( accessed by pressing and holding power button+ volume up) which is similar to what is happening to me. The problem is that you can only flash KDZ updates with LG flash tool. This works for hard bricked devices when nothing else worked. I was thinking to connect the device in this way and update drivers using LG drivers instead of pixel's but still I can't get an update in kdz format.

ASMstudent said:
...but still I can't get an update in kdz format.
Click to expand...
Click to collapse
And you won't either. Google doesn't offer them, so you'll have to hope a developer creates one or one gets leaked by someone at Google.

Just installed LG mobile drivers and connected my device in download mode. In manage devices, it's now shown as an LG mobile connected, so theoretically it could work.
Sent from my PLK using Tapatalk

I downloaded a patched LGUP flash tool from LG v30 forums that could allow cross flashing between different variants and it detected my pixel 2 XL. Still it needs a kdz or tot file to flash, but when I chose boot.img from Google factory image, it gave me an error on the LGUP but also on my device which means there is a connection between my PC and my device which means this might actually work .View attachment 4719702
Sent from my PLK using Tapatalk

ASMstudent said:
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.View attachment 4718679View attachment 4718680
Sent from my PLK using Tapatalk
Click to expand...
Click to collapse
were you able to find a good solution to your problem, am in the same situation.?

Nope
I found out that this is EDL or Qualcomm emergency download mode and you need Google proprietary programmer firehouse file, blank flash files and rawprogram0.xml file; last two can be extracted from a working device. I contacted Google support forum and they told me that they wouldn't release these files to anyone as they may be used to find software vulnerabilities in the device. I contacted software repair center known for dealing with these problems, he told me that they have the programmer firehouse for the pixel 2xl ( not sure if they actually do or it's just a scam) but they would need time to extract the other needed files. I paid a sponsorship fee ( only 21$ ) and gave them 2-3 months, but they provided no updates so I requested a refund and sold the device as spare parts. EDL mode is theoretically your best bet to fix the device, but without the appropriate files ( which may never be available) it's useless.
You can look up EDL mode, QFIL, QPST tools and the store's name is aryktech.

ASMstudent said:
Nope
I found out that this is EDL or Qualcomm emergency download mode and you need Google proprietary programmer firehouse file, blank flash files and rawprogram0.xml file; last two can be extracted from a working device. I contacted Google support forum and they told me that they wouldn't release these files to anyone as they may be used to find software vulnerabilities in the device. I contacted software repair center known for dealing with these problems, he told me that they have the programmer firehouse for the pixel 2xl ( not sure if they actually do or it's just a scam) but they would need time to extract the other needed files. I paid a sponsorship fee ( only 21$ ) and gave them 2-3 months, but they provided no updates so I requested a refund and sold the device as spare parts. EDL mode is theoretically your best bet to fix the device, but without the appropriate files ( which may never be available) it's useless.
You can look up EDL mode, QFIL, QPST tools and the store's name is aryktech.
Click to expand...
Click to collapse
How sure its not your device that i bought of ebay?:laugh:

0x0null said:
How sure its not your device that i bought of ebay?[emoji23]
Click to expand...
Click to collapse
Lol
Actually I sold it locally in my country.
You can contact aryktech if they made any progress just don't pay upfront
Sent from my PLK using Tapatalk

Aiit.tnx

@ASMstudent or @0x0null - any other progress? Exact same situation with Taimen (Pixel 2 XL). Dunno if I should make this my month-long side project, or just chuck the phone.

SimFox3 said:
@ASMstudent or @0x0null - any other progress? Exact same situation with Taimen (Pixel 2 XL). Dunno if I should make this my month-long side project, or just chuck the phone.
Click to expand...
Click to collapse
Nah, i got a new board.

Android tablet, how to disable kiosk mode or install new firmware

I am new to the android programming world. I own an iQR70 device from MLS that is using -if I read well- the kiosk mode for its own application called MAIC (something like Amazon's Alexa virtual assistant).
{
"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"
}
The real pain with this device is that the application is buggy does not get any updates and overall does not work properly.
So, my questions are, a) is there any way to disable the kiosk mode and work with it as a normal tablet? or desperately b) Can I install a compatible firmware? I don't care for the data inside.

You can check for update. Look for android version of tablet. You can check their site for any upgrade of software.
You can flash other firmware. Find compatible firmware as per your model.
You can disable apps same as you do on android mobile.

My tablet currently Is dead boot and I am trying to find the test points. Anyway, I have no access to the android os to disable apps. The virtual assistant is the only app I can use, all others are forbidden.

Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?

zeetotheuno said:
Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?
Click to expand...
Click to collapse
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.

sdancer said:
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.
Click to expand...
Click to collapse
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.

zeetotheuno said:
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.
Click to expand...
Click to collapse
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.

sdancer said:
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
Click to expand...
Click to collapse
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
sdancer said:
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
Click to expand...
Click to collapse
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
sdancer said:
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.
Click to expand...
Click to collapse
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.

zeetotheuno said:
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.
Click to expand...
Click to collapse
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.

sdancer said:
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.
Click to expand...
Click to collapse
That's awesome! Thank you in advance.
Yeah, I guess the hardware reset really takes some time and a lot of trial and error.
But if you manage to do it, let me know, I'm just curious in general, if that's possible with this device.

To Flash your device,
1) Install the drivers
2) Press Download from SP Flash Tool
2) Connect USB
3) Connect the power outlet from your device (in this case) or connect the battery
****WARNING: DONT FORMAT THE PRELOAD or you will get a DEAD BOOT device, use ONLY DOWNLOAD and not download+format
AutoInstall
=================
MediaTek_Preloader_USB_VCOM_drivers.exe
File on MEGA
mega.nz
Manual Install
=================
MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed.zip
File on MEGA
mega.nz
MediaTek_Preloader_USB_VCOM_Drivers.zip
File on MEGA
mega.nz

Hey @sdancer, thank you for the drivers. But I must do something wrong, because it's still not detected. It's not showing in my device manager and nothing happens in SP Flashtool.
I tried the automatic install and the manual install, but still nothing :/
Could you maybe explain how exactly you installed them? Maybe I'm making a mistake there.

1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at

sdancer said:
1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at
Click to expand...
Click to collapse
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.

zeetotheuno said:
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.
Click to expand...
Click to collapse
Hi
I suppose that this is a driver's problem, you should try to fix it someway.

Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko

Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
Any idea, Any fix?

paulos2951 said:
Any idea, Any fix?
Click to expand...
Click to collapse
I have no idea bro :/ Hoping that someone will help me

Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
I have the same problem with you
If you find a solution please send me a message !

Jim-Kyritsis said:
I have the same problem with you
If you find a solution please send me a message !
Click to expand...
Click to collapse
Hi friend! Are you Greek? Is there a way to contact MLS in Greece?

Question RM6/6Pro Unbrick Tool - EDL Flash / Switch from CN to EU

Hello guys,
I received the following unbrick tool from my supplier in Shenzhen - China and wanted to share it with you since I noticed that many people are desperate to fix their RM6 and swap it to EU.
The process is super easy:
1) Download & extract the following .zip
https://mega.nz/file/ntBSxDKa#h9vUPGoWVyqtyDYWYmSgz8bE1_vNimBMAqTp9csvv-w
2) Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)
3) Open the MiTool application
4) in MiTool, select the folder images
5) Put your phone in EDL mode
6) Once connected, Click flash - the brushing process will start automatically.
7) Once done, force reset and Voilà!
There's an alternative as well: MultiportQLoader
I haven't tried it myself, feel free to try it and share the steps.
Im sorry if any details aren't clear, but I'm typing this while driving xD
Good luck and would appreciate a shout-out on insta @Out.Geeked ^^

THANK YOU SIR

To ask a dumb question, but is this only the 6 or for the pro as well?

Works for both

Thank you so much, it work after someone help me erase flash

Outgeeked.net said:
Works for both
Click to expand...
Click to collapse
Yeah I checked the model number against the box it came in and gave it a shot, now it shows the RM logo and then reboots to the bootloader lmao this phone legit hates me
*edit*
So I think either I'm doing something wrong or this phone is actually messed up. Checked the drivers, tried 2 other cables, all my USB ports and still all it does is briefly show the white "System Rebooting" screen and then the RM logo for about 20 seconds and then reboots to fastboot/bootloader.
MiFlash shows "couldn't find flash script" but otherwise looks like it goes through the reflash process completely but QLoader always fails with an error "Unknown chunk type cac2"
Does this unbrick method require the bl to be unlocked?

anyone lost their imei after doing this? hahahha
i did lost my imei, but manage to repair it but... it still doesnt detect mobile network idk what to do now lol

Nocturne Seigneur said:
anyone lost their imei after doing this? hahahha
i did lost my imei, but manage to repair it but... it still doesnt detect mobile network idk what to do now lol
Click to expand...
Click to collapse
Did you ever find a way to recover your IMEI? Turns out that I'm in the same situation as you with a lost IMEI

CyberWolf92 said:
Did you ever find a way to recover your IMEI? Turns out that I'm in the same situation as you with a lost IMEI
Click to expand...
Click to collapse
loool welcome to the club xD, I didn't found any solution yet, i will tell u once confirmed, for now i can write imei but mobile network still not functioning

Does it actually work?
According to the file name, it's EU V3.10.
I thought we should apply the NA/Asia version.

cannon3025 said:
Does it actually work?
According to the file name, it's EU V3.10.
I thought we should apply the NA/Asia version.
Click to expand...
Click to collapse
yes it does work, some ppl lose imei some not idk why, mine lose imei and cant connect to any mobile network right now T^T
after u unbrick it, u can flash via local update to v4.13 i did that working fine

Nocturne Seigneur said:
yes it does work, some ppl lose imei some not idk why, mine lose imei and cant connect to any mobile network right now T^T
after u unbrick it, u can flash via local update to v4.13 i did that working fine
Click to expand...
Click to collapse
After you update to V4.13, your phone still no IMEI right?
How about flashing it again?

cannon3025 said:
After you update to V4.13, your phone still no IMEI right?
How about flashing it again?
Click to expand...
Click to collapse
its gone, forever lol
i just gave my phone to someone else to fix this, if he can.
[Guide] Restore Lost IMEIs / Repair Network or Radio Issues
I accidentally restored TWRP backup of another Zuk Z2 phone on my new pgone and in this process over-wrote the EFS partition. This left me with a phone having no IMEI, no mac for Wifi and Bluetooth. Effectively No Network on phone. Worried, I...
forum.xda-developers.com
this maybe work, havent test it out

Since we have the partition layout & the correct firehose, it should actually be a good practice by anyone wanting to play with their phone (BL unlock, root, dev, etc) to first dump the critical partitions.
That way, you can always restore. Example: EFS, misc, persist, etc.

Thanks for your help
When I use MiFlash shows "couldn't find flash script"
Can you please help
My RM6pro restarting all time to fastboot mode after I tried to relock bootloader and oem
Now I need to solve this issue by using this tools
I am beginner
Thanks

Same issue for @CyberWolf92

Alaryani said:
Thanks for your help
When I use MiFlash shows "couldn't find flash script"
Can you please help
My RM6pro restarting all time to fastboot mode after I tried to relock bootloader and oem
Now I need to solve this issue by using this tools
I am beginner
Thanks
Click to expand...
Click to collapse
Select the images folder and then hit flash.

Mine is alive again, no more problems.
I think I know why a lot of people have probably bricked their device after flash from CN to Global. If you do a local update, let the device REboot until the end. After the restart it uses the update.zip again. I think a lot of people did a factory reset immediately after the reboot (like me in Recovery) and the system can no longer find the update.zip.
Therefore, let the update run through, reboot until you are back in the system. Then you can do a factory reset.

Outgeeked.net said:
Select the images folder and then hit flash.
Click to expand...
Click to collapse
When I selected images folder shows "couldn't find flash script"
{
"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"
}
And when I go to edl mode my phone disappeard from list devices in MiFlash.
but still showing in driver manger
What driver needs for this issue "Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)" what else I need?
also when i did it on fastboot mode i face this massge

Alaryani said:
When I selected images folder shows "couldn't find flash script"
View attachment 5329645
And when I go to edl mode my phone disappeard from list devices in MiFlash.
View attachment 5329643
but still showing in driver manger
View attachment 5329647
What driver needs for this issue "Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)" what else I need?
also when i did it on fastboot mode i face this massge
View attachment 5329661
Click to expand...
Click to collapse
you must be in edload mode not fastboot