Develop Bugs

Updating AT&T OTA issues; need help sideloading

Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
{
"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"
}

If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.

This is exactly what I needed; not necessarily a hand-holding or step by step, but a path forward to investigate. Thanks!

So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
41rw4lk said:
If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.
Click to expand...
Click to collapse

westec2 said:
So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
Click to expand...
Click to collapse
With a locked bootloader you can flash an official firmware that is the same revision or newer. So in short, yes.

Hello! I ended up using the smart tool; it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool; it was the easiest way without root to get updated. Once I had the right drivers installed and it recognized bootloader mode, LMSA was really easy to use.

despree said:
it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool.
Click to expand...
Click to collapse
How did you get the "right drivers" and how did you install them? Does the PC download them automatically when you attach the phone or did you need to find them and manually install them?

Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.

New to updating here
despree said:
Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.
Click to expand...
Click to collapse
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot

omiCar said:
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot
Click to expand...
Click to collapse
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.

despree said:
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.
Click to expand...
Click to collapse
Hi, thank you for your quick response, I will be attempting to do this tonight or tomorrow, I will circle back with an update, again thank you !

Backup phone first with LMSA
That's what I had to do so it would stop hanging at 51%. Use LMSA backup feature first then upgrade

I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.

Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...

bdizzle1686 said:
Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...
Click to expand...
Click to collapse
You can take any flashing all, use a tool to merge the sparsed system images and mount the system img and pull it that way if you really need it

wrenhal said:
I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.
Click to expand...
Click to collapse
Answered my own question. The flash worked fine. I switched over to the log at 51% and watched it copying files and eventually it finished up and the phone rebooted to Oreo. All in all, if say it took only fifteen to twenty minutes.
Sent from my KIW-L24 using Tapatalk

despree said:
Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/help/how-to-manually-update-att-motorola-z2-t3879143

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.

Redmi 6 Pro (Faked Mi A2 Lite) bricked - How to solve this: "device is locked."

Redmi 6 Pro (Faked Mi A2 Lite) bricked - How to solve this: "device is locked."
First of all, I tried to install MIUI on my mi a2 lite, but apparently this phone is redmi 6 pro with the rom a mi a2 lite android one, my phone won't turn on anymore. Fake Mi AQ2 Lite
{
"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"
}
My phone does not turn on, only the logo of xiaomi appears
I can put in the bootloader, but when using the command it gives the error of the image.
I try to install xiaomi's current rom by mi flash, but the error appears below:
rom: jasmine_global_images_V10.0.9.0.PDIMIXM_20190513.0000.00_9.0_bbaa8993fe
-----------------
Attempts with rom Sakura, product name version
How to solve this: "device is locked. cannot erase?"

CCSJava said:
First of all, I tried to install MIUI on my mi a2 lite, but apparently this phone is redmi 6 pro with
the rom a mi a2 lite android one, my phone won't turn on anymore. Fake Mi AQ2 Lite
My phone does not turn on, only the logo of xiaomi appears
I can put in the bootloader, but when using the command it gives the error of the image.
I try to install xiaomi's current rom by mi flash, but the error appears below:
rom: jasmine_global_images_V10.0.9.0.PDIMIXM_20190513.0000.00_9.0_bbaa8993fe
-----------------
Attempts with rom Sakura, product name version
How to solve this: "device is locked. cannot erase?"
Click to expand...
Click to collapse
Take a look here, it seems to be the very same issue https://forum.xda-developers.com/redmi-6-pro/how-to/redmi-6-pro-faked-mi-a2-lite-bricked-t3956142 just a thing, don´t try to flash any other rom or you´ll completely leave it bricked.
Edit: I recommend; read the OP to better understanding and then you can jump directly to the post #21 where solution is.

SubwayChamp said:
Take a look here, it seems to be the very same issue https://forum.xda-developers.com/redmi-6-pro/how-to/redmi-6-pro-faked-mi-a2-lite-bricked-t3956142 just a thing, don´t try to flash any other rom or you´ll completely leave it bricked.
Edit: I recommend; read the OP to better understanding and then you can jump directly to the post #21 where solution is.
Click to expand...
Click to collapse
try 1
try 2
ROM: sakura_images_V9.6.18.0.ODICNFD_20180817.0000.00_8.1_cn_eee51da93d

CCSJava said:
try 1
try 2
ROM: sakura_images_V9.6.18.0.ODICNFD_20180817.0000.00_8.1_cn_eee51da93d
Click to expand...
Click to collapse
Be sure to use EDL, not fastboot.

SubwayChamp said:
Be sure to use EDL, not fastboot.
Click to expand...
Click to collapse
so, I put the testpoint, it recognizes in device manager, but in mi flash no

SubwayChamp said:
Be sure to use EDL, not fastboot.
Click to expand...
Click to collapse
is it normal to take long?

CCSJava said:
is it normal to take long?
Click to expand...
Click to collapse
No, is not normal, it has to take around 8 minutes. But the times (several) that I flashed through EDL using Miflash tool you have not to see your ID but simply COM 10 for example or the port where is detected device, probably you have to go throw back your steps to sure that this first of all be fixed, otherwise no way to flash correctly. Remember that your device has to be detected like qualcomm-HSUSB-9008download or something similar.

SubwayChamp said:
No, is not normal, it has to take around 8 minutes. But the times (several) that I flashed through EDL using Miflash tool you have not to see your ID but simply COM 10 for example or the port where is detected device, probably you have to go throw back your steps to sure that this first of all be fixed, otherwise no way to flash correctly. Remember that your device has to be detected like qualcomm-HSUSB-9008download or something similar.
View attachment 4850439
Click to expand...
Click to collapse
I think I'm doing something wrong
Is EDL the test point? I opened the phone, put a metal part in the two points, then connected the usb cable.
QUalcomm Appears, But MiFlash Does Not Appear
Am I doing something wrong?

CCSJava said:
I think I'm doing something wrong
Is EDL the test point? I opened the phone, put a metal part in the two points, then connected the usb cable.
QUalcomm Appears, But MiFlash Does Not Appear
Am I doing something wrong?
Click to expand...
Click to collapse
You did reach EDL mode apparently, in unkocked devices you can get it through commands but in locked (like yours) the unique way is using testpoint method so it´s fine with it.
NO, it´s incorrect, your device must not be detected like Qualcomm Diagnostics but this is the exact name that has to appear: "Qualcomm HS-USB QDLoader 9008", download drivers from here https://www.google.com/url?sa=t&rct...bit-windows/&usg=AOvVaw1aDI5aquv8QiX3bzyxrZtp, then update them locating the path and then probably you need to restart pc, and try it again.
Edit: And don´t try to use "save user data" ever do a clean flash all.

SubwayChamp said:
You did reach EDL mode apparently, in unkocked devices you can get it through commands but in locked (like yours) the unique way is using testpoint method so it´s fine with it.
NO, it´s incorrect, your device must not be detected like Qualcomm Diagnostics but this is the exact name that has to appear: "Qualcomm HS-USB QDLoader 9008", download drivers from here https://www.google.com/url?sa=t&rct...bit-windows/&usg=AOvVaw1aDI5aquv8QiX3bzyxrZtp, then update them locating the path and then probably you need to restart pc, and try it again.
Edit: And don´t try to use "save user data" ever do a clean flash all.
Click to expand...
Click to collapse
everything is going wrong, i will cryy

Try this tutorial https://boycracked.com/flashing
Sent from my Infinix NOTE 3 Pro using Tapatalk

SubwayChamp said:
You did reach EDL mode apparently, in unkocked devices you can get it through commands but in locked (like yours) the unique way is using testpoint method so it´s fine with it.
NO, it´s incorrect, your device must not be detected like Qualcomm Diagnostics but this is the exact name that has to appear: "Qualcomm HS-USB QDLoader 9008", download drivers from here https://www.google.com/url?sa=t&rct...bit-windows/&usg=AOvVaw1aDI5aquv8QiX3bzyxrZtp, then update them locating the path and then probably you need to restart pc, and try it again.
Edit: And don´t try to use "save user data" ever do a clean flash all.
Click to expand...
Click to collapse

CCSJava said:
Click to expand...
Click to collapse
Now is detected like 9008qdloader? It seems that the path to your folder is empty, I don´t see files there.

SubwayChamp said:
Now is detected like 9008qdloader? It seems that the path to your folder is empty, I don´t see files there.
Click to expand...
Click to collapse
the universe is not plotting for me, I think I'll give up.
Did my cell phone die?

CCSJava said:
the universe is not plotting for me, I think I'll give up.
Did my cell phone die?
Click to expand...
Click to collapse
What about the picture that you uploaded, I don´t see nothing here or is edited?
and what about why I asked before about if it´s detected now?
Mostly unbrick a device is not a simple thing, you just have to refine the way that you are doing, double check how you are connecting with pc and pay attention if device is vibrating or blinking led, you have to put some effort on this and you could solve it. You tried to flash a wrong firmware on it not even with the same processor (jasmine) it´s normal that now your device is an abnormal state.

SubwayChamp said:
What about the picture that you uploaded, I don´t see nothing here or is edited?
View attachment 4850799 and what about why I asked before about if it´s detected now?
Mostly unbrick a device is not a simple thing, you just have to refine the way that you are doing, double check how you are connecting with pc and pay attention if device is vibrating or blinking led, you have to put some effort on this and you could solve it. You tried to flash a wrong firmware on it not even with the same processor (jasmine) it´s normal that now your device is an abnormal state.
Click to expand...
Click to collapse
I downloaded two sakura roms, one v10 and the other v9, this image was v9, renamed it to 1, the other was in the successor post, it didn't work.
About connecting, every time I connect the usb cable to the computer it vibrates and the xiaomi logo appears.
Should I install any specific rom?

CCSJava said:
I downloaded two sakura roms, one v10 and the other v9, this image was v9, renamed it to 1, the other was in the successor post, it didn't work.
Click to expand...
Click to collapse
Well, I thought that short name was the name for.
About connecting, every time I connect the usb cable to the computer it vibrates and the xiaomi logo appears.
Click to expand...
Click to collapse
In Device Manager of PC you have to see that is detected like qualcomm-HS 9008qdloader and doesn´t have to vibrate nor appears no screen otherwise is not connecting well, you have to repeat the process: when you connect your device then just have to made a sound.
Should I install any specific rom?
Click to expand...
Click to collapse
Your case is the same that wich I linked before, the user has a Sakura with a fake rom for Daisy and the member flashed a chinese rom, this solved the issue and has sense cause apparently the device comes from the chinese market and is not intended like a global one. In the post that I linked you can find also a link to some chinese roms that I provided for him in the past.
Just strange is that the member needed an authorized account and you don´t?

SubwayChamp said:
Well, I thought that short name was the name for.
In Device Manager of PC you have to see that is detected like qualcomm-HS 9008qdloader and doesn´t have to vibrate nor appears no screen otherwise is not connecting well, you have to repeat the process: when you connect your device then just have to made a sound.
Your case is the same that wich I linked before, the user has a Sakura with a fake rom for Daisy and the member flashed a chinese rom, this solved the issue and has sense cause apparently the device comes from the chinese market and is not intended like a global one. In the post that I linked you can find also a link to some chinese roms that I provided for him in the past.
Just strange is that the member needed an authorized account and you don´t?
Click to expand...
Click to collapse
So always made the windows whistle when a usb is inserted
The vibration and xiaomi logo, if I'm not mistaken, 100% of the time appeared when entering EDL mode.
About the account, did not ask no, I click flash and each time appears a different error, as can not read port COM10.
Should I try the chinese rom developer edition?

CCSJava said:
So always made the windows whistle when a usb is inserted
Click to expand...
Click to collapse
As I said your device doesn´t have to be detected like qualcomm 900E Diagnostics
View attachment 4851309
But like qualcomm 9008qdloader
View attachment 4851311
Open and check device manager before to start any attempt, you have to fix first this wrong connection otherwise you CAN´T do nothing, see some tutorial like this to install correctly the drivers https://www.google.com/url?sa=t&rct...=IstIV85WEmk&usg=AOvVaw2gTeL5OSfkQxi0jND9N7zw
The vibration and xiaomi logo, if I'm not mistaken, 100% of the time appeared when entering EDL mode.
Click to expand...
Click to collapse
Are you using test point method? otherwise how you think to do it? just connecting with device on or off won´t work.
About the account, did not ask no, I click flash and each time appears a different error, as can not read port COM10.
Click to expand...
Click to collapse
The same, fix first qualcomm drivers.
Should I try the chinese rom developer edition?
Click to expand...
Click to collapse
If you type fastboot oem unlock what happened?

I have a bricked one too.. you need a xiaomi special account to flash with the rom. With other apps with dos log you will se is that the "error" only adms users can flash... Even the old versions ddn work. Cant see all the post now but think the "rom link" is ok. Is just the flash software the problem. Some sites sell the account to flash 1 time. Like 13 dollar idkn

Realme UI 2.0 update issue

Hello everyone. Hope you all are doing well.
I had updated my Realme 6 Pro from Android 10, version RMX2061_11.A.49 to the Android 11 update i.e. Realme UI 2.0, version RMX2061_11.C.15. The thing is, after optimizing apps during the first boot, the phone is stuck at the lock screen and the touchscreen is not responding.
Video of the issue is here: Realme 6 pro UI 2.0 issue
Kindly do help on what to do next. Doing a reset is the last step I want to undertake, since I forgot to take a backup.. Will flashing the Realme UI 2.0 update via stock recovery help? Any help and suggestions would be much appreciated.
Thank you.

soham93 said:
Hello everyone. Hope you all are doing well.
I had updated my Realme 6 Pro from Android 10, version RMX2061_11.A.49 to the Android 11 update i.e. Realme UI 2.0, version RMX2061_11.C.15. The thing is, after optimizing apps during the first boot, the phone is stuck at the lock screen and the touchscreen is not responding.
Video of the issue is here: Realme 6 pro UI 2.0 issue
Kindly do help on what to do next. Doing a reset is the last step I want to undertake, since I forgot to take a backup.. Will flashing the Realme UI 2.0 update via stock recovery help? Any help and suggestions would be much appreciated.
Thank you.
Click to expand...
Click to collapse

Hello soham,
I have the exactly same problem since the yesterday update with my Realme X2 Pro.
If you find a solution please let me know
...at the moment i have no idea.

yeah bro same with mine,
but we have another choice,
drain the battery and let the mobile turn off
after that go to the recovery mode and wipe your data.
or else we need to update the software in the recovery mode which is not arrived yet.

Press the power off and volume up button for about 7 sec and it should power off. when u turn it on press the power off and volume down button for 10 sec and you will boot to recovery mode. After that, u will have to format your data which will cause ur data to be removed.

I dont think there is any other way to fix this. Unless you have your data back up in the cloud. Maybe you can also take out the storage card from your phone which is difficult and then back up your data from a pc or something.

I thought of flashing the ROM, but it was not available anywhere. So I ended up performing a factory reset to boot the phone. There seems to be no other solution for this.

I have no backup..so i wait for the next update..
Wipe data doesnt work for me and i do not format the device.

I have the exact same issue. This problem generally applies to all Realme devices upgraded to Realme UI 2.0. The root cause is the disabling of com.coloros.weather.service package, usually done during debloating through adb. Further analysis I have done is explained on my thread.
Quick fixes you have now:
If you have adb enabled and ticked "Always allow from this computer" on the prompt below when your phone is still working, you can connect your phone in the blinking state and issue the following command: adb shell cmd pm enable com.coloros.weather.service. Then, reboot your phone. It will work normally on Realme UI 2.0.
{
"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"
}
Click to expand...
Click to collapse
[DATA LOSS] Download this ozip and put it on an SD card. A used SD card works fine as long as it isn't encrypted and has enough free space. Make sure the file name matches your device model. Enter realme UI Recovery (on Realme 7, you press VolumeDown + Power, which might differ for each device) and choose 'Install from Storage'. Enter your device password, select 'SD Card', and pick the ozip you have downloaded. The phone will wipe itself, and you end up with a working phone on Realme UI 1.0.
[DATA LOSS] If your phone is still on warranty period, go to any Realme Service Centre, and use the following statement; the service centre will either replace your phone free of charge or if they don't have any replacements in stock, put you on a waitlist and calls you back once the replacement device is available.
I am updating my device to Realme UI 2.0 when suddenly the device turns off and reboot itself. Now, this device won't allow me to unlock it.
Click to expand...
Click to collapse
Other possible, longer-term solutions are:
Wait for Realme to realize this problem and issue an OTA update. The fix is easy on their side; just add a simple one line on the after-flash script of the next OTA/ozip to enable the weather services package:
Code:
pm enable com.coloros.weather.service
The command pm enable would do nothing if a package is already enabled. However, Realme might not realise this problem. Even if they recognise it, Realme might think it is not their own problem (debloating = user's fault?). If they release this fix, we can just boot into recovery and install it. Realme has support for OTA updates on their recovery. Just enter the device password and then the WiFi password.
I have tried exploring the Realme forums, albeit not directly filing a bug report. I found many, many users experiencing a similar issue as ourselves. Most of it was responded to by Realme representatives in this fashion: "enter recovery mode by pressing this and this, and then choose to wipe data. This will reset your phone to its working state." This is not acceptable for me since a functioning phone is lower on my priority than keeping my data (albeit in limbo).
Suppose your device has MediaTek SoC, and you have not set up any password/PIN/pattern on your device. In that case, you could possibly extract the userdata partition, exploiting the Boot ROM (BROM) exploit by Dinolek and k4y0z with the SP Flash Tool. You first need to find a specific scatter file for your device; however, if none is available, you could generate one from a preloader dump using a tool named Wwr MTK.
If you have set up a password, then this would be infeasible, apparently, since not only the device password is needed to decrypt it, but also some salt stored on the SoC itself; hence this thread highly suggests swapping SoC and eMMC to another working exact same phone (cannibalize another phone).
However, even after you swapped the SoC to a new phone and write your userdata partition on it, you faced a new dilemma:
previously on the old phone, you have a non-working software config, but the decryption key to the userdata is the same as the decryption key to the other partitions
now on the new phone, you have a working software config. The decryption key is available on SoC, but the other partitions are unreadable to the bootloader. They are either unencrypted or encrypted with a different key.
I have not been able to solve the above dilemma.
Hence, my current objective is to nag Realme and invite others to also nag them to implement that simple one line on their OTA update.

any updates? today i update realme 6 to realme ui 2.0 it broke my phone... because of this weather crap usb debugging not working for me...

I too ran into this issue just now. Thanks @said1219 for your suggestion. A single change in my case. I haven't disabled the app, I have uninstalled it. So I ran
adb shell cmd package install-existing com.coloros.weather.service
This fixed the issue. This didn't require restart.
I use Realme C3. After this update again there is a new update of 280MB released on Dec 9, 2021, specifies system optimization.
It doesn't make any issue after this.

vigneshrajarr said:
I too ran into this issue just now. Thanks @said1219 for your suggestion. A single change in my case. I haven't disabled the app, I have uninstalled it. So I ran
adb shell cmd package install-existing com.coloros.weather.service
This fixed the issue. This didn't require restart.
I use Realme C3. After this update again there is a new update of 280MB released on Dec 9, 2021, specifies system optimization.
It doesn't make any issue after this.
Click to expand...
Click to collapse
I have a question, how did you reinstall the weathersystem even if your phone is flickering? Did you do it on power on or in recovery mode? That is an adb fastboot right?? Does your phone prompt you and asks to "file transfer" and "charging only"? Because that's the only last thing I have to do, let my pc run adb fastboot to turn it on

Quasar.Illumia said:
I have a question, how did you reinstall the weathersystem even if your phone is flickering? Did you do it on power on or in recovery mode? That is an adb fastboot right?? Does your phone prompt you and asks to "file transfer" and "charging only"? Because that's the only last thing I have to do, let my pc run adb fastboot to turn it on
Click to expand...
Click to collapse
You let the phone complete boot and enter the flicker-state. Then run "adb devices" as per your photo in my thread.
The following step can be done either on normal boot, fastboot, or recovery mode:
If no device is found, it is likely that USB debugging is disabled on your device.
If your device is found, but it says 'unauthorized', it means that you didn't tick "Always allow connections from this device" or a long time has lapsed since you've connected your PC's ADB to your phone.
If your device is found and it says 'device' on the right of the serial number, you're good to go.
Except for the last scenario, you're possibly getting back to square one.
The following step must be done after the phone completed normal boot, recognized your PC, and enter the flicker-state:
If you disabled the weather package, run
Code:
adb shell cmd pm enable com.coloros.weather.service
If you uninstalled the weather package, run
Code:
adb shell cmd package install-existing com.coloros.weather.service
Your phone will immediately stop flickering and you can enter your password normally. And, as per my reply in my thread, "Allow charging only" could prevent you from accessing ADB.

I thought it wasn't working when I entered adb shell yesterday. Thank you UwU it is working now
said1219 said:
You let the phone complete boot and enter the flicker-state. Then run "adb devices" as per your photo in my thread.
The following step can be done either on normal boot, fastboot, or recovery mode:
If no device is found, it is likely that USB debugging is disabled on your device.
If your device is found, but it says 'unauthorized', it means that you didn't tick "Always allow connections from this device" or a long time has lapsed since you've connected your PC's ADB to your phone.
If your device is found and it says 'device' on the right of the serial number, you're good to go.
Except for the last scenario, you're possibly getting back to square one.
The following step must be done after the phone completed normal boot, recognized your PC, and enter the flicker-state:
If you disabled the weather package, run
Code:
adb shell cmd pm enable com.coloros.weather.service
If you uninstalled the weather package, run
Code:
adb shell cmd package install-existing com.coloros.weather.service
Your phone will immediately stop flickering and you can enter your password normally. And, as per my reply in my thread, "Allow charging only" could prevent you from accessing ADB.
Click to expand...
Click to collapse

Well then, another year has gone by
No changes so far? I noticed new Realme UI updates have been launched in the meantime. Has anyone tried them out yet on the blocked phones?
As you've recommended @said1219 , I've kept my battery in good condition and still hope that this problem can get solved in the future...
However, since this issue started, by principle I've refused to buy any new Realme product...

Question Can't unlock my Poco f3 bootloader with mi tool

Hi there
It's been two days that I want to unlock my Poco f3 bootloader with mi tool but i can't, i've been very frustrated, i am worried if i'm stuck with official rom! could you please help me, I've searched google and the forums and tried a lot of workarounds but nothing works.
So first issue is that i do not receive the sms verefication when i log in to MI tool.
Then I tried the QR code method, i scanned it, openned the URL and allowed sign in. MI tool says local verefication is done, and wants me to relogin, I click on the login button and the tool starts loading but won't load anything!
After that, i tried loging in with facebook, it showed me an error and i clicked on not now, and it showed me a login page, i tried loging in and it logged in successfully!
however, once i connect my phone in fastboot mode to my computer, the tool shows "checking phone status" then says "unknown error 1004, try again later)
Is the mi tool service down or i'm doing something wrong. I tried with two accounts so far.

I've had a similar problem if the if you can't sign in while you're in fast Boot and you have the mi tool open use another phone to try to get the verification that's what I had to do and then you can sign in with the mi tool , I just used Google voice so there was no need for another phone but that's what I did

jefffrom said:
I've had a similar problem if the if you can't sign in while you're in fast Boot and you have the mi tool open use another phone to try to get the verification that's what I had to do and then you can sign in with the mi tool , I just used Google voice so there was no need for another phone but that's what I did
Click to expand...
Click to collapse
Sorry I got confused a bit, do you mean that i have to go to fast boot on my phone and it needs to be connected to the pc, and then try to sign in with mi tool?
because the way i do it, i have the phone on, i try to sign in first, so i can scan the QR code or get the SMS code.

maybe it is a problem with the drivers, try to download the ones from that guide and connect the phone in normal mode (allow usb debug when the message appears) and also connect it in fastboot mode so that it recognizes the drivers
https://www.getdroidtips.com/unlock-bootloader-poco-f3/

viroxnet said:
maybe it is a problem with the drivers, try to download the ones from that guide and connect the phone in normal mode (allow usb debug when the message appears) and also connect it in fastboot mode so that it recognizes the drivers
https://www.getdroidtips.com/unlock-bootloader-poco-f3/
Click to expand...
Click to collapse
no luck.
mi unlock tool does not send me my sms verefication and when i login with qr code it just gets stuck in loading screen

oasis1701 said:
no luck.
mi unlock tool does not send me my sms verefication and when i login with qr code it just gets stuck in loading screen
Click to expand...
Click to collapse
Send image

Rstment ^m^ said:
Send image
Click to expand...
Click to collapse
so first i open mi unlock tool on pc and then click i agree, and then on the button that shows the qr code.
then i go to my phone, settings, mi account, scan qr code, and i scan the code on the screen, and click sign in when it prompts me to. then this screen appears: https://www.dropbox.com/s/1zthjiod03fotwd/Screenshot 2022-05-12 20.33.30.png?dl=0
then i click on the text that says login and this shows up: https://www.dropbox.com/s/5kyepva0zdc6m34/Screenshot 2022-05-12 20.33.47.png?dl=0
and just stays there forever

maybe version? in the images it is different from the current one.
Sometimes is windows permission, use the app in your desktop and execute as administrator
https://miuirom.xiaomi.com/rom/u1106245679/6.5.224.28/miflash_unlock-en-6.5.224.28.zip

viroxnet said:
maybe version? in the images it is different from the current one.
Sometimes is windows permission, use the app in your desktop and execute as administrator
https://miuirom.xiaomi.com/rom/u1106245679/6.5.224.28/miflash_unlock-en-6.5.224.28.zip
Click to expand...
Click to collapse
tried with this version too, still no luck. in fact when i use this version it wants me to update to another latest version.
IS the message "relogin to your account" normal? does it happen for all QR logins?

oasis1701 said:
tried with this version too, still no luck. in fact when i use this version it wants me to update to another latest version.
IS the message "relogin to your account" normal? does it happen for all QR logins?
Click to expand...
Click to collapse
maybe the problem is the account on the phone, try to delete the account and add it again.
On the phone and in the app you must log in with the same method (hopefully with the phone number)

viroxnet said:
maybe the problem is the account on the phone, try to delete the account and add it again.
On the phone and in the app you must log in with the same method (hopefully with the phone number)
Click to expand...
Click to collapse
thanks for helping
I signed out from mi account in the phone, rebooted, then signed back in. though interestingly enough, it did not ask me for my password but signed in without it. i had to turn on find my device and that one asked for the password though.
But again it didn't work for me same things keep happening

Hi there. A couple of days ago I was dealing with the same issues you're dealing with now. Here is some input which might help you and others who are currently stuck at the loading screen:
First, notice that there's a log file created by Mi Unlock on your computer which, at any rate, may help you mitigatating any issues. The file is located at:
C:\Users\YourUserName\AppData\Roaming\Xiaomi\miflash_unlock\Log\miflash_unlock.log
The error 1004 is, as far as I know, related to the unlockAPI being unreachable. Specifically, the QR login method results in an 401 error and for this reason, the loading page gets stuck.
Ditch the QR login method and instead log in with your password (the default method). If the SMS verification screen appears, wait for 60 seconds (there should be a timer indicating that) and click on RESEND. In my case, it was the second attempt that worked and the SMS transmitted successfully.
Now, as everybody else, I assumed this login method wouldn't work, as previously there were reCAPTCHA issues. That's probably why everyone recommended the QR method. In any event, as of today, this method should work again and might get you logged in successfully, without receiving the 1004 error.
I'm afraid there is the possibility that you'll need to wait for another 168 hours as you logged out of your account on the POCO F3. If that's the case, try next week the same aforementioned method again. If that doesn't work, try the QR method.
Good luck!
EDIT: Clarifications and formatting.

I also face the same problem earlier this month! I think I try a different version and the older version is working for me with the QR code solution. Good luck!

I have a similar problem. I tried different versions of the unlock tool (5.5.224.24, 6.5.224.28, 6.5.406.31) and I get the same error (Local verification has been completed please re-login your account) when checking the authentication with a barcode. Clicking on Login button doesn't do anything.
However, I can log in with an email address or phone number and SMS verification works. If I try to unlock the device i get an error Couldn't unlock. Please rebind and try again.
{
"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"
}
Also the driver for the Fastboot connection is the original Xiaomi.
If it helps anyone, there is a log file of the unlock tool on https://www.miamit.si/miflash_unlock.log

i got same issue, i got error 1004. i was try every method and got 1 solution and maybe can help. first to know i only one laptop running windows 10 and already have miunlock tool and has been install all driver. first try to Disable Driver Signature (you can find how to do on google) and restart. after boot reinstall driver you have, if you have miflash you can reinstall driver from that, make sure windows ask you to have permission to install driver. and last step try to open miunlock (my miunlock is latest version) and login to your account for unlocking, recommend to login using email or facebook to avoid SMS verification. if you can login you can see your error status at miunlock homescreen,if status error is not showing now you can unlock your bootloader. i hope my method can help everybody. good luck

185F8DB3227 said:
Hi there. A couple of days ago I was dealing with the same issues you're dealing with now. Here is some input which might help you and others who are currently stuck at the loading screen:
First, notice that there's a log file created by Mi Unlock on your computer which, at any rate, may help you mitigatating any issues. The file is located at:
C:\Users\YourUserName\AppData\Roaming\Xiaomi\miflash_unlock\Log\miflash_unlock.log
The error 1004 is, as far as I know, related to the unlockAPI being unreachable. Specifically, the QR login method results in an 401 error and for this reason, the loading page gets stuck.
Ditch the QR login method and instead log in with your password (the default method). If the SMS verification screen appears, wait for 60 seconds (there should be a timer indicating that) and click on RESEND. In my case, it was the second attempt that worked and the SMS transmitted successfully.
Now, as everybody else, I assumed this login method wouldn't work, as previously there were reCAPTCHA issues. That's probably why everyone recommended the QR method. In any event, as of today, this method should work again and might get you logged in successfully, without receiving the 1004 error.
I'm afraid there is the possibility that you'll need to wait for another 168 hours as you logged out of your account on the POCO F3. If that's the case, try next week the same aforementioned method again. If that doesn't work, try the QR method.
Good luck!
EDIT: Clarifications and formatting.
Click to expand...
Click to collapse
Thank you, this helped me quite a lot. I waited another day and the sms verefication works now.
The fact that the sms and QR method didn't work for 24 hours throw me off, now i know that the QR method is broken.