So, some days ago I've purchased a Mi A2 Lite. Right after starting it and testing it's basic functions, I headed right away to the computer to change ROMs. When I booted TWRP through fastboot, I wiped system to install another ROM, but the roms i'd downloaded wouldn't flash. Then, suddenly, TWRP touch stops working. I found then that it was a normal thing, and a guy posted in a thread that locking and unlocking his bootloader made TWRP work again (I did try to boot it again and didn't work). So I locked the device through a simple tool. Now, I can't unlock the bootloader in anyway. MiUnlock requires binding the device to an account (my device doesn't have an OS anymore since I wiped it), can't unlock it through fastboot (token verification failed), can't enter adb through commands because it is locked. MiFlash requires an authorized account to flash. QFIL doesn't flash because by entering in EDL Mode through test points, you have to start flashing fast, otherwise it won't be able to read hello packet, but the QFIL app takes too long to start flashing, I click it, it loads and loads, and just says it couldn't read packet. I'm trying to unbrick this device for 4 days long.
Now, the reason I say it is a faked Mi A2 Lite (can't know it for sure, actually) are these:
-Although the device came new from fabric, all the box and acessories had their plastics and stickers, the device came unlocked.
-The device came with Android One (which is right, as I bought a Mi A2 Lite), but has a Mi-Recovery 3.0, which is from MIUI systems, and Redmi 6 Pro has MIUI.
-When trying to unlock it through fastboot, I entered some commands to get info of the device, the interesting ones were these:
imei: (blank)
product: sakura (which is Redmi 6 Pro)
version-bootloader:MSM8953_DAISY1.0_20181019193735
I am from Brazil, and I am mostly sure that it is original and came this way from Xiaomi because the seller gave me the receipt and says he buys from authorized seller. And everything came with it's plastics on, the box was sealed-new, so I don't believe the seller did this, I believe Xiaomi did this mi a2 lite/redmi 6 pro confusion.
EDIT: I'm now sure it's Xiaomi's fault as I've found another identical cases where they had "sakura" devices with "daisy" bootloaders (exactly same versions), they probably chose to do this, which is worse than this being a mistake.
Could you guys help me, don't know what to do anymore. If you need more info to solve this problem, please ask, I'll post them right away.
@GNDawg
Well, I search around and it seems to be most likely a Xiaomi fault. they flashed a wrong firmware but it also could be that some seller in the chain took a bricked device, changed back over and flashed a rom that it had available either changing or not motherboard from the original but this is just a theory hard to proof.
Anyway now your best bet would be try to flash through an unnoficial tool like QPST download drivers and follow carefully instructions to update then onto your pc http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/ and here is a tutorial how to use it https://c.mi.com/thread-226346-1-1.html this tool gives error on several cases so you have to search probably a modded sahara file for other MSM8953 to fix it.
And here a thread with a different method, the idea is try to boot from the sdcard, you could need some files to do it like a part of the system dumped for other user with the same device, this thread is just a reference for other model https://forum.xda-developers.com/g4/general/guide-unbrick-via-external-sdcard-qfil-t3748946
I did in the past the file to be flashed onto TWRP and dump it, I´ll try to search for it
SubwayChamp said:
@GNDawg
Well, I search around and it seems to be most likely a Xiaomi fault. they flashed a wrong firmware but it also could be that some seller in the chain took a bricked device, changed back over and flashed a rom that it had available either changing or not motherboard from the original but this is just a theory hard to proof.
Anyway now your best bet would be try to flash through an unnoficial tool like QPST download drivers and follow carefully instructions to update then onto your pc http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/ and here is a tutorial how to use it https://c.mi.com/thread-226346-1-1.html this tool gives error on several cases so you have to search probably a modded sahara file for other MSM8953 to fix it.
And here a thread with a different method, the idea is try to boot from the sdcard, you could need some files to do it like a part of the system dumped for other user with the same device, this thread is just a reference for other model https://forum.xda-developers.com/g4/general/guide-unbrick-via-external-sdcard-qfil-t3748946
I did in the past the file to be flashed onto TWRP and dump it, I´ll try to search for it
Click to expand...
Click to collapse
Hey man, I didn't quite understand the tutorial you passed me, because it just says to build a EDL Cable and then flash it through MiFlash, as far as I understood. I'm so tired I think I'm gonna pay s-unlock to unbrick this damn phone, are they trustworthy? The service doesn't need TeamViewer anymore, they've built a tool which needs an account with credits (you pay for them), and then you can flash using these credits, I wonder if the process fails, will the credits be gone? hahaha man, look at the level we're at, thank you Xiaomi!
GNDawg said:
Hey man, I didn't quite understand the tutorial you passed me, because it just says to build a EDL Cable and then flash it through MiFlash, as far as I understood. I'm so tired I think I'm gonna pay s-unlock to unbrick this damn phone, are they trustworthy? The service doesn't need TeamViewer anymore, they've built a tool which needs an account with credits (you pay for them), and then you can flash using these credits, I wonder if the process fails, will the credits be gone? hahaha man, look at the level we're at, thank you Xiaomi!
Click to expand...
Click to collapse
In the post in spanish there are some useful links like Qualcomm 9008-USB drivers and other to explain how to avoid drivers verification on Windows, this could be necessary to get a perfect connection among your device and pc although I´m begin to suspect that motherboard is damaged at some level, I say you this cause I had similar problem in different circumstances with a Xiaomi device in the past; briefly explained an user uploaded incorrect files to some site and I flashed onto my device and some of the files were for other model; result: totally bricked, I tried a lot of guides and method but I didn´t give out till I was absolutely sure that there was nothing more to do with. Finally I had to buy other motherboard and that device now is working fine.
I commented about a method to "burn" a part of the image in an external SDcard, a part of the system image means just about 100 or 200 MB sized of the image, I shared year/s ago a zip to obtain it (I didn´t find now) so some user that have same device can flash it through TWRP and so dump this "part/fraction" of system, then they can share with you, you burn it using the disc image utility inbuilt on Windows and then apply to your device and this way your device do an attempt to boot from this SDcard, then you can flash normally all the whole rom through XiaoMi flash. But your case is slightly different, it seems like not a totally brick, in my case I didn´t have any partition working like fastboot, recovery, nothing at all. The third link refers to something similar to the exposed above.
Referent to this service, you have to be sure that they can do something with a device that can´t communicate correctly with XiaoMi flash and you said me first that the tool needs an account authorized but then you said that the tool began but finally failed to flash that mean that the tool can work without an authorization, if this is true you only have to refine the method to use it correctly.
Probably you can upload an image while you´re attempting in XiaoMi flash to see how is detecting it.
SubwayChamp said:
In the post in spanish there are some useful links like Qualcomm 9008-USB drivers and other to explain how to avoid drivers verification on Windows, this could be necessary to get a perfect connection among your device and pc although I´m begin to suspect that motherboard is damaged at some level, I say you this cause I had similar problem in different circumstances with a Xiaomi device in the past; briefly explained an user uploaded incorrect files to some site and I flashed onto my device and some of the files were for other model; result: totally bricked, I tried a lot of guides and method but I didn´t give out till I was absolutely sure that there was nothing more to do with. Finally I had to buy other motherboard and that device now is working fine.
I commented about a method to "burn" a part of the image in an external SDcard, a part of the system image means just about 100 or 200 MB sized of the image, I shared year/s ago a zip to obtain it (I didn´t find now) so some user that have same device can flash it through TWRP and so dump this "part/fraction" of system, then they can share with you, you burn it using the disc image utility inbuilt on Windows and then apply to your device and this way your device do an attempt to boot from this SDcard, then you can flash normally all the whole rom through XiaoMi flash. But your case is slightly different, it seems like not a totally brick, in my case I didn´t have any partition working like fastboot, recovery, nothing at all. The third link refers to something similar to the exposed above.
Referent to this service, you have to be sure that they can do something with a device that can´t communicate correctly with XiaoMi flash and you said me first that the tool needs an account authorized but then you said that the tool began but finally failed to flash that mean that the tool can work without an authorization, if this is true you only have to refine the method to use it correctly.
Probably you can upload an image while you´re attempting in XiaoMi flash to see how is detecting it.
Click to expand...
Click to collapse
So, there's this problem that happens when the software can't connect to the device if I take too long to flash after entering EDL Mode, I've seen a lot of other cases of this "problem" too. I have to test point and flash right after, which is no problem in MiFlash, but in QFIL and QPST it looks like it takes too long to connect with the device and then it fails. But I've seen that S-Unlock uses
their own tool called XiaomiTool, where they create an account for you which has credits. Then the tool uses the credits to flash. It's quite confusing... but you don't need to grant them TeamViewer access, which if way more safer than the previous method. Man... I had a ZUK device before, there was no AntiRollback ****, I didn't even had to unlock a bootloader in the first place you would just wipe and flash all day long for as long as you'd want, I was in heaven and didn't know it.
Also, I'm pretty sure the softwares detect the device just fine, the device connects through 9008 port, and they detect it right after connecting it.
GNDawg said:
So, there's this problem that happens when the software can't connect to the device if I take too long to flash after entering EDL Mode, I've seen a lot of other cases of this "problem" too. I have to test point and flash right after, which is no problem in MiFlash, but in QFIL and QPST it looks like it takes too long to connect with the device and then it fails. But I've seen that S-Unlock uses
their own tool called XiaomiTool, where they create an account for you which has credits. Then the tool uses the credits to flash. It's quite confusing... but you don't need to grant them TeamViewer access, which if way more safer than the previous method. Man... I had a ZUK device before, there was no AntiRollback ****, I didn't even had to unlock a bootloader in the first place you would just wipe and flash all day long for as long as you'd want, I was in heaven and didn't know it.
Also, I'm pretty sure the softwares detect the device just fine, the device connects through 9008 port, and they detect it right after connecting it.
Click to expand...
Click to collapse
You say that through XiaoMi Flash (also usually called MiFlash tool) the flash process begins then no need to an authorized account, right? if this is right then now the only challenge is get the tool to work fine and in this case I guess that the best would be to try with some tricks like:
- Uninstall all the drivers (I know you say that pc detects it but it seems that in the way it is disconnecting).
- Before to reinstall them again disable signature verification from Windows to avoid that some firewall/antivirus cut the drivers to be installed properly.
- Check that the folder where the images and the scripts are, be in the last directory/path in the tool an short the name where it contained for "6mipro" for example without spaces.
- Move all the files of the rom to the same drive and folder where XiaoMi flash is installed usually C drive.
- Prepare previously all the tool and the path and just to the end put device in download mode, with battery disconnected and fingerprint is also recommendable to get out.
- Try with firmware for 6 Pro and also for A2 Lite.
Regarding this service is extrange how they can take control over device, no remote service, nor IMEI required or IP digits, How they can put a firmware onto your device this way!. There are other services that you can consult before to accept this unless you find some positive reference about it.
SubwayChamp said:
You say that through XiaoMi Flash (also usually called MiFlash tool) the flash process begins then no need to an authorized account, right? if this is right then now the only challenge is get the tool to work fine and in this case I guess that the best would be to try with some tricks like:
- Uninstall all the drivers (I know you say that pc detects it but it seems that in the way it is disconnecting).
- Before to reinstall them again disable signature verification from Windows to avoid that some firewall/antivirus cut the drivers to be installed properly.
- Check that the folder where the images and the scripts are, be in the last directory/path in the tool an short the name where it contained for "6mipro" for example without spaces.
- Move all the files of the rom to the same drive and folder where XiaoMi flash is installed usually C drive.
- Prepare previously all the tool and the path and just to the end put device in download mode, with battery disconnected and fingerprint is also recommendable to get out.
- Try with firmware for 6 Pro and also for A2 Lite.
Regarding this service is extrange how they can take control over device, no remote service, nor IMEI required or IP digits, How they can put a firmware onto your device this way!. There are other services that you can consult before to accept this unless you find some positive reference about it.
Click to expand...
Click to collapse
No, it does need an authorized account, but first it has to connect to the device, after it suceeds, it then asks for the account. I don't think that it "disconnecting" is a big issue, only if the Xiaomi Tool that the S-Unlock guys use also takes a long time to connect to the device.
To explain the problem more precisely, the software tells me "cannot read hello packet if I press the button too long after connecting EDL, it fails seconds after clicking to flash. If I connect the device and flash right away, it suceeds and then proceeds to ask the authorized account.
And about the service, they don't actually take control over the device, I would do the flashing myself, the only thing they do is provide the account necessary to flash, but it isn't in the MiFlash tool, it's the XiaomiTool (they give the link to the app), where it first asks for an account, then only after logging in it can start the flashing process. One of those cases I've talked about that were just like mine were solved with these guys.
GNDawg said:
No, it does need an authorized account, but first it has to connect to the device, after it suceeds, it then asks for the account. I don't think that it "disconnecting" is a big issue, only if the Xiaomi Tool that the S-Unlock guys use also takes a long time to connect to the device.
To explain the problem more precisely, the software tells me "cannot read hello packet if I press the button too long after connecting EDL, it fails seconds after clicking to flash. If I connect the device and flash right away, it suceeds and then proceeds to ask the authorized account.
And about the service, they don't actually take control over the device, I would do the flashing myself, the only thing they do is provide the account necessary to flash, but it isn't in the MiFlash tool, it's the XiaomiTool (they give the link to the app), where it first asks for an account, then only after logging in it can start the flashing process. One of those cases I've talked about that were just like mine were solved with these guys.
Click to expand...
Click to collapse
Ok, now the things are most clear, I never need an authorized account (by fortune) I´m not sure and I expect that my actual doesn´t need it just in case.
When you connect for first time to the tool and try to flash then the tool allows you continue but of course then it prompts for an authorization, from here you can´t try a second attempt in the same time that it remains connected this will lead you then of a few minutes to a fail like "sahara fail" or "cannot read packet".
In my experience the second attempt didn´t work at all so you have to disconnect device and restart the tool to can try it again.
As far I understand this is similar to a patched Odin for Samsung devices to bypass some security controls but in this case they provide you a patched XiaoMi tool which is controlled remotely to get authorized. It has sense and it seems trustworthy.
I don´t know if actually Xiaomi authorizes new account users https://miui.blog/any-devices/mi-account-authorization-tips/
And Probably you can try first an older version of MiPhone, previous than XiaoMi flash https://www.xiaomiflash.com/download/
SubwayChamp said:
Ok, now the things are most clear, I never need an authorized account (by fortune) I´m not sure and I expect that my actual doesn´t need it just in case.
When you connect for first time to the tool and try to flash then the tool allows you continue but of course then it prompts for an authorization, from here you can´t try a second attempt in the same time that it remains connected this will lead you then of a few minutes to a fail like "sahara fail" or "cannot read packet".
In my experience the second attempt didn´t work at all so you have to disconnect device and restart the tool to can try it again.
As far I understand this is similar to a patched Odin for Samsung devices to bypass some security controls but in this case they provide you a patched XiaoMi tool which is controlled remotely to get authorized. It has sense and it seems trustworthy.
I don´t know if actually Xiaomi authorizes new account users https://miui.blog/any-devices/mi-account-authorization-tips/
And Probably you can try first an older version of MiPhone, previous than XiaoMi flash https://www.xiaomiflash.com/download/
Click to expand...
Click to collapse
Hey man, I bought the S-Unlock service, I tried to flash the daisy ROM but it wouldn't send the "firehose_emmc_something" succesfully, so I tried the Redmi 6 Pro ROM i'd downloaded (Xiaomi_Redmi_6_Pro_V9.6.4.0.ODMMIFD_20180730.0000.00_8.1_Global_XFT) and it succesfully flashed!!!!!
BUT, it doesn't boot. "This version of MIUI can't be installed on this device."
Any ideas? In the support group of S-Unlock they say this happens when you flash a global rom into a chinese device, which can only receive global roms with unlocked bootloaders. An admin from the group told me to flash chinese ROM.
EDIT: sent the command fastboot getvar all:
product: sakura_india
it ****ing changed hahaha, now I'll probably have to flash an indian ROM, but I'll have to pay again, I really want to give up this device...
GNDawg said:
Hey man, I bought the S-Unlock service, I tried to flash the daisy ROM but it wouldn't send the "firehose_emmc_something" succesfully, so I tried the Redmi 6 Pro ROM i'd downloaded (Xiaomi_Redmi_6_Pro_V9.6.4.0.ODMMIFD_20180730.0000.00_8.1_Global_XFT) and it succesfully flashed!!!!!
BUT, it doesn't boot. "This version of MIUI can't be installed on this device."
Any ideas? In the support group of S-Unlock they say this happens when you flash a global rom into a chinese device, which can only receive global roms with unlocked bootloaders. An admin from the group told me to flash chinese ROM.
EDIT: sent the command fastboot getvar all:
product: sakura_india
it ****ing changed hahaha, now I'll probably have to flash an indian ROM, but I'll have to pay again, I really want to give up this device...
Click to expand...
Click to collapse
The service is very limited, they had to guide you to a final success, it´s a shame.
It was hard to know exactly what firmware is the proper for this "hybrid" phone. The theory is right, this might be an indian version but I guess that you didn´t receive at first the getvar product as sakura_india.
It might be great if they can unlock bootloader and this way you can do anything on it.
Did you see bootloader status or if you can flash something now through fastboot?
Try with other tool for Qualcomm from here https://androidmtk.com/category/tools maybe some of them work.
SubwayChamp said:
The service is very limited, they had to guide you to a final success, it´s a shame.
It was hard to know exactly what firmware is the proper for this "hybrid" phone. The theory is right, this might be an indian version but I guess that you didn´t receive at first the getvar product as sakura_india.
It might be great if they can unlock bootloader and this way you can do anything on it.
Did you see bootloader status or if you can flash something now through fastboot?
Try with other tool for Qualcomm from here https://androidmtk.com/category/tools maybe some of them work.
Click to expand...
Click to collapse
The service is only to give me the EDL Authorization, they don't care if what I flash, they just grant me this permission to flash in EDL, which ****ing xiaomi requires. They have a bootloader unlocking service, but for MIUI v9 only, and there isn't an option for my phone (neither mi a2 lite nor redmi 6 pro). I'm willing to try again, it would cost me 10 dollars more, but I need to know what Rom works for this thing. I don't think these tools will work because the phone continues the same, but now with a ROM which the device doesn't accept because of locked bootloader which I can't unlock.
EDIT: I've read in an article from XDA that booting MIUI Roms in the Redmi 6 pro can brick it. I'll have to flash a custom rom?
GNDawg said:
The service is only to give me the EDL Authorization, they don't care if what I flash, they just grant me this permission to flash in EDL, which ****ing xiaomi requires. They have a bootloader unlocking service, but for MIUI v9 only, and there isn't an option for my phone (neither mi a2 lite nor redmi 6 pro). I'm willing to try again, it would cost me 10 dollars more, but I need to know what Rom works for this thing.
Click to expand...
Click to collapse
If the limit is according a certain time and not number of flashing sessions I think you have to follow these simple rules:
- Flash first an Indian version of 6 Pro http://en.miui.com/download-349.html#545 (choose stable not developer rom)
- Prepare/download if it exists a chinese version, I´m not sure it does so device was release for India but some guys are talking that they bought with a chinese firmware although in the official site there is only an Indian firmware.
- Keep in mind that this device has ARB so don´t try with a lower build number version.
I don't think these tools will work because the phone continues the same, but now with a ROM which the device doesn't accept because of locked bootloader which I can't unlock.
Click to expand...
Click to collapse
No, this tool can work as the same way that XiaoMi flash can, the same thing that both can´t achieve is that a wrong firmware can work/boot up on your device due to regional locking security. Maybe you can try this simple tool before https://androidmtk.com/download-emmc-dl-tool anyway if doesn´t result probably the best would be go for a second chance with that service.
SubwayChamp said:
If the limit is according a certain time and not number of flashing sessions I think you have to follow these simple rules:
- Flash first an Indian version of 6 Pro http://en.miui.com/download-349.html#545 (choose stable not developer rom)
- Prepare/download if it exists a chinese version, I´m not sure it does so device was release for India but some guys are talking that they bought with a chinese firmware although in the official site there is only an Indian firmware.
- Keep in mind that this device has ARB so don´t try with a lower build number version.
No, this tool can work as the same way that XiaoMi flash can, the same thing that both can´t achieve is that a wrong firmware can work/boot up on your device due to regional locking security. Maybe you can try this simple tool before https://androidmtk.com/download-emmc-dl-tool anyway if doesn´t result probably the best would be go for a second chance with that service.
Click to expand...
Click to collapse
No, every flash costs 10 credits, which costs 10 dollars. If I get it wrong, I have to pay again.
What I meant by the tools not working is that just like Xiaomi flash, they require the EDL authorization.
I tried with emmc tool, but I couldn't get it to work, it gives me "Failed to connect to phone"
Adding the edit I put in the previous reply, I read an article here in XDA saying that flashing MIUI Rom in Redmi6 pro (along with other devices) may brick the device just like my device is bricked right now (https://www.xda-developers.com/flash-miui-global-locked-bootloader-xiaomi-brick/
So, will I have to flash custom rom?
GNDawg said:
No, every flash costs 10 credits, which costs 10 dollars. If I get it wrong, I have to pay again.
Click to expand...
Click to collapse
Ah ok, then the best is go direct to the safest zone flashing the rom linked in my previous post.
What I meant by the tools not working is that just like Xiaomi flash, they require the EDL authorization.
I tried with emmc tool, but I couldn't get it to work, it gives me "Failed to connect to phone"
Adding the edit I put in the previous reply, I read an article here in XDA saying that flashing MIUI Rom in Redmi6 pro (along with other devices) may brick the device just like my device is bricked right now (https://www.xda-developers.com/flash-miui-global-locked-bootloader-xiaomi-brick/
Click to expand...
Click to collapse
Yes, this is now the scenario, to be honest your device is now "double" bricked, first time was bricked due to relock bootloader while a non-proper firmware was shipped with i.e. a Mi A2 Lite firmware on a different device. And the second time now when you flashed a a Global rom over a device that supposedly was (it had to be) shipped with an indian/chinese firmware.
But don´t worry about it, device at this way won´t boot due to a locked bootloader, if you still can enter to fastboot and recovery no signals of serious damages.
So, will I have to flash custom rom?
Click to expand...
Click to collapse
No, never try it yet with locked bootloader untill you unlocket it, this won´t result as same as try to modify any partition or file you can´t by now, your device simply won´t boot at all.
SubwayChamp said:
Ah ok, then the best is go direct to the safest zone flashing the rom linked in my previous post.
Yes, this is now the scenario, to be honest your device is now "double" bricked, first time was bricked due to relock bootloader while a non-proper firmware was shipped with i.e. a Mi A2 Lite firmware on a different device. And the second time now when you flashed a a Global rom over a device that supposedly was (it had to be) shipped with an indian/chinese firmware.
But don´t worry about it, device at this way won´t boot due to a locked bootloader, if you still can enter to fastboot and recovery no signals of serious damages.
No, never try it yet with locked bootloader untill you unlocket it, this won´t result as same as try to modify any partition or file you can´t by now, your device simply won´t boot at all.
Click to expand...
Click to collapse
Hey, so I downloaded the ROM you linked, but it is in .zip format, and the files inside are different from the other ROMs I downloaded, which are in .tgz (I think these are fastboot ROM files, dunno, but they are all in the same format and arrangement), I searched and found a ROM in MIUI site (http://en.miui.com/a-234.html).
The file name is sakura_india_global_images_V10.3.3.0.PDMMIXM_20190711.0000.00_9.0_global_400152c914.tgz
Looks like the same as the one you sent, but in tgz, since it is sakura india global image, 10.3.3.0 and 9.0.
GNDawg said:
Hey, so I downloaded the ROM you linked, but it is in .zip format, and the files inside are different from the other ROMs I downloaded, which are in .tgz (I think these are fastboot ROM files, dunno, but they are all in the same format and arrangement), I searched and found a ROM in MIUI site (http://en.miui.com/a-234.html).
The file name is sakura_india_global_images_V10.3.3.0.PDMMIXM_20190711.0000.00_9.0_global_400152c914.tgz
Looks like the same as the one you sent, but in tgz, since it is sakura india global image, 10.3.3.0 and 9.0.
Click to expand...
Click to collapse
Oh my bad, I linked the rom that is for recovery, the link that you have this is the right firmware to flash through fastboot.
SubwayChamp said:
Oh my bad, I linked the rom that is for recovery, the link that you have this is the right firmware to flash through fastboot.
Click to expand...
Click to collapse
**** man, I'm so frustrared, flashed this ROM and got the same ****ing thing. "This MIUI version can't be installed on this device."
fastboot getvar all
version-bootloader:MSM8953_DAISY2.0_20190711190946
(bootloader) hw-revision:10001
(bootloader) rollback_ver:2
(bootloader) serialno:09d58bc30805
(bootloader) kernel:lk
(bootloader) product:sakura_india
I found that if you send fastboot getvar anti you get if your phone has got antiroll or something like this
fastboot getvar anti
anti:
it gives me blank...
I think I may have another chance to flash, I have some credits, don't know if they are enough, what ROM should I try next if I can? I was thinking maybe chinese ROM?
GNDawg said:
**** man, I'm so frustrared, flashed this ROM and got the same ****ing thing. "This MIUI version can't be installed on this device."
fastboot getvar all
version-bootloader:MSM8953_DAISY2.0_20190711190946
(bootloader) hw-revision:10001
(bootloader) rollback_ver:2
(bootloader) serialno:09d58bc30805
(bootloader) kernel:lk
(bootloader) product:sakura_india
I found that if you send fastboot getvar anti you get if your phone has got antiroll or something like this
fastboot getvar anti
anti:
it gives me blank...
I think I may have another chance to flash, I have some credits, don't know if they are enough, what ROM should I try next if I can? I was thinking maybe chinese ROM?
Click to expand...
Click to collapse
Redmi 6Pro as same as Mi A2 Lite have ARB but actually bootloader revisions are not implementing it so it stays as blank (a kind of zero), when your device reach value 5 then you can´t downgrade anymore on locked bootloaders.
There is something very strange that unfortunately marked your device as practically unusable. The system partition seems to be wrong from the fabric.
It´s hard to know which firmware it´s the correct. Did you see those users with the same problem? maybe you can ask them in some forum for sure.
If exists a chinese version as stated in my previous post this would be the next chosing and the next if exists a chinese version of Mi A2 Lite so I wonder how they installed Android One previously.
SubwayChamp said:
Redmi 6Pro as same as Mi A2 Lite have ARB but actually bootloader revisions are not implementing it so it stays as blank (a kind of zero), when your device reach value 5 then you can´t downgrade anymore on locked bootloaders.
There is something very strange that unfortunately marked your device as practically unusable. The system partition seems to be wrong from the fabric.
It´s hard to know which firmware it´s the correct. Did you see those users with the same problem? maybe you can ask them in some forum for sure.
If exists a chinese version as stated in my previous post this would be the next chosing and the next if exists a chinese version of Mi A2 Lite so I wonder how they installed Android One previously.
Click to expand...
Click to collapse
I think the main problem is the locked bootloader, the device came unlocked so they must've installed android one easily.
I was searching for those similar cases I'd said and found at least 4 more, where they had Mi A2 Lite with sakura product name. Some of them said they had LineageOS installed... I don't remember seeing any Lineage symbols when I booted the device and I know it because I used on my previous device, I only know it was Android One.
In one of the cases, the buyer talked to the seller who showed him all of the other A2 Lite he had were just like his, with LineageOS installed. That's so bad man...
Another useful info, in the back of the phone there's a Model Number, and it matches the box model number, so it isn't counterfeit or scammed, I'm sure this came from Xiaomi.
And one of the cases were solved flashing MIUI China version, I believe that the only way these are not from Xiaomi is everybody having bought from the same chinese seller who did this, so it would make sense that only MIUI Chinese version works, I'll try it, since it's the only option.
I think I'll not be able to flash daisy ROMs, when I tried two daisy ROMs, in both cases the firehose thingy wouldn't send correctly and the flash would fail, sakura ones work fine.
GNDawg said:
I think the main problem is the locked bootloader, the device came unlocked so they must've installed android one easily.
Click to expand...
Click to collapse
Well, here is where my theory that some reseller had to do the whole mistake so the device come locked by default and if Xiaomi flashed Android One also they have to make an A/B partition scheme and this didn´t happen, anyway this is just for the record BUT this could be useful to claim your rights to the seller so if they didn´t do by itself then they had the obligation to buy from a reseller a good device to can sell it to a client in a well form and this is achieve without any technical skill just comparing the IMEIs declared from the box with device itself. Also atleast in my country R6Pro is cheaper than Mi A2 Lite so has sense that they bucked some dollars with it.
I was searching for those similar cases I'd said and found at least 4 more, where they had Mi A2 Lite with sakura product name. Some of them said they had LineageOS installed... I don't remember seeing any Lineage symbols when I booted the device and I know it because I used on my previous device, I only know it was Android One.
In one of the cases, the buyer talked to the seller who showed him all of the other A2 Lite he had were just like his, with LineageOS installed. That's so bad man...
Another useful info, in the back of the phone there's a Model Number, and it matches the box model number, so it isn't counterfeit or scammed, I'm sure this came from Xiaomi.
Click to expand...
Click to collapse
I guess they confussed LineageOs with Android One, in Pie there is not many differences at a quick view,
And one of the cases were solved flashing MIUI China version, I believe that the only way these are not from Xiaomi is everybody having bought from the same chinese seller who did this, so it would make sense that only MIUI Chinese version works, I'll try it, since it's the only option.
I think I'll not be able to flash daisy ROMs, when I tried two daisy ROMs, in both cases the firehose thingy wouldn't send correctly and the flash would fail, sakura ones work fine.
Click to expand...
Click to collapse
In this site there are many firmware versions https://xiaomifirmware.com/roms/download-official-roms-for-redmi-6-pro/ probably you have to choose the chinese version that came first with device and not try to upgrade it to the latest contrarily as we think before. I read that Redmi 6 Pro did come with Oreo 8.1 and although it had a Pie firmware was from other device and it won´t be considered as a downgrade in this case so never had Pie firmware based on Miui.
I did find this but I don´t know if it´s reliable, if unlocking bootloader can be done device will free for any rom http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=5997528&pid=35773053
I think I finally destroyed my cell phone. I tried to install the Chinese version firmware on my Mi 9T Pro Global and it's on a Hard Brick: It doesn't turn on fastboot or recovery. Opening the phone, I managed to connect to EDL to try to recover by Mi Flash and only the error "Can not read from port com" appears and I've tried everything! I tried several different ROMS, changed the Firehose file that prevents unauthorized accounts by MI Auth, changed Mi Flash versions, installed all necessary drivers several times, changed the USB port to 2.0 and 3.0 and nothing happened. I also tried alternative programs like Qualcomm's QPST/QFIL, and also a Virtual Box. I just found a thread that taught a method where I would have to pay 15 dollars to recover the phone, but what if I hard brick it again , I'll always have to pay 15 dollars to retrieve the cell phone, and I can't do that, not to mention that I don't even know if this method would work. Holy s*** I don't think I've ever been so desperate hahahaha has anyone retrieved any Mi 9T Pro through EDL, or at least knows how to solve this port COM problem?
XxGardenXx said:
I think I finally destroyed my cell phone. I tried to install the Chinese version firmware on my Mi 9T Pro Global and it's on a Hard Brick: It doesn't turn on fastboot or recovery. Opening the phone, I managed to connect to EDL to try to recover by Mi Flash and only the error "Can not read from port com" appears and I've tried everything! I tried several different ROMS, changed the Firehose file that prevents unauthorized accounts by MI Auth, changed Mi Flash versions, installed all necessary drivers several times, changed the USB port to 2.0 and 3.0 and nothing happened. I also tried alternative programs like Qualcomm's QPST/QFIL, and also a Virtual Box. I just found a thread that taught a method where I would have to pay 15 dollars to recover the phone, but what if I hard brick it again , I'll always have to pay 15 dollars to retrieve the cell phone, and I can't do that, not to mention that I don't even know if this method would work. Holy s*** I don't think I've ever been so desperate hahahaha has anyone retrieved any Mi 9T Pro through EDL, or at least knows how to solve this port COM problem?
Click to expand...
Click to collapse
Paying someone is the only way to make EDL work these days.
Also ensure your cable works. My port didn't seem to work with any Xiaomi cables for data, however it fortunately worked with a magnetic end charging cable as my port is presumably a tad damaged.
You will get your money back with the guy I did it with if it doesn't work.
So touching those pins are the only way you can get any sort of output to the screen?
[Edit]
The price of a new motherboard is really expensive. I'd probably rule that out.
Also if you can get to download mode in any way, I'd use Linux. I've not managered to get ADB working on Windows this year. However Linux has been fine. EDL flashing worked in Windows for me.
Turbine1991 said:
Paying someone is the only way to make EDL work these days.
Also ensure your cable works. My port didn't seem to work with any Xiaomi cables for data, however it fortunately worked with a magnetic end charging cable as my port is presumably a tad damaged.
You will get your money back with the guy I did it with if it doesn't work.
So touching those pins are the only way you can get any sort of output to the screen?
[Edit]
The price of a new motherboard is really expensive. I'd probably rule that out.
Also if you can get to download mode in any way, I'd use Linux. I've not managered to get ADB working on Windows this year. However Linux has been fine. EDL flashing worked in Windows for me.
Click to expand...
Click to collapse
My cable seems to be working as it charges my mom's cell phone, and the PC also recognizes the EDL, though I haven't tried using other cables.
Yes, Test Point is the only answer the phone gives me that it's still alive, as the PC recognizes the EDL, even though the phone doesn't turn on the screen (it doesn't even vibrate when I hold the power button or try to turn it on on the fastboot/recovery)
If it's a motherboard problem, I'll follow your advice and buy another cell phone, it wouldn't be worth it to just send it for assistance and pay a fortune
Finally, I don't have access to any linux unfortunately, but I was also having problems with ADB, and that's exactly why I accidentally installed Chinese Firmware lol
Mine got all the way up to the flashing point and it failed until I changed cable. Just because it charges, doesn't mean it'll work for data.
And you've tried vol up + hold power? And try detach the battery so it's definitely off of EDL.
I mean a motherboard will fix it, but that's just to replace your emmc memory. But you're better off trying the EDL pay service regardless.
What do you mean you don't have access to Linux? It's free and one doesn't need to install it to boot into it.
After you recover to an ancient Chinese rom through EDL, one still needs to unlock the bootloader to go back to something better like Miui.eu.
Turbine1991 said:
Mine got all the way up to the flashing point and it failed until I changed cable. Just because it charges, doesn't mean it'll work for data.
And you've tried vol up + hold power? And try detach the battery so it's definitely off of EDL.
I mean a motherboard will fix it, but that's just to replace your emmc memory. But you're better off trying the EDL pay service regardless.
What do you mean you don't have access to Linux? It's free and one doesn't need to install it to boot into it.
After you recover to an ancient Chinese rom through EDL, one still needs to unlock the bootloader to go back to something better like Miui.eu.
Click to expand...
Click to collapse
About the cable I didn't know it could be detected by the pc and at the same time not being able to transfer data, thanks! I will try to change the cable in the next attempts
Yes, I tried to hold the volume and power, but nothing happened. I also tried it with the battery ribbon cable plugged in and unplugged, but both didn't work either.
I don't know anything about PC OS hahaha mb, for me installing linux in my pc, would be like installing IOS on a Samsung. So I think I have access to Linux
About the bootloader I don't think I'll have any problems, I've already unlocked the phone, rooted it and changed the ROM to an AOSP-based one
Oh, and forgot to say: a friend also hard bricked his Mi 8 Lite and retrieved it via EDL. He said that the problem I'm having, he was also, and he only managed to solve it after downloading the rom and files of a guy here in Brazil, but unfortunately on the site he didn't have the Mi 9T Pro files He said he changed firehose, persist, patch0 and rawprogram0 (all files present in the images folder of ROM) and it worked! Mi Auth was bypassed and the system came out of the brick.
Hi All,
I received an update notification yesterday on my China Market device with Global ROM and I immediately downloaded the update to MIUI13. I had 60% battery when the download finished and after downloading it did an app optimization. After that, I hit the reboot button with 58% battery. The device turned off and since then the device is literally not showing any sign of life. it doesn't charge or show up in the ADB devices list. My MBP doesn't recognize USB in the devices list. What is the best option I have? From threads, it doesn't sound like a brick or EDL mode to me but should I still contact the EDL guy?
Just an update. I was using Macbook to test if the device is alive. MacBook Pro doesn't show any updates when you connect a new device. I plugged USB into a Windows machine installed on my Bootcamp, Windows recognized the device as Qualcomm 9008. Which is effectively in EDL mode. I have no idea how the device got into that mode but my assumption is that I had TWRP installed with BL open and when going from Android 11 to Android 12 via MIUI13, something called anti-rollback protection which was implemented by Xiaomi put the phone into EDL mode. Luckily, I am in the UK and got in touch with Xiaomi after sales, they agreed to repair it because the issue was caused by a software update.
Lesson Learned: Never update your phone via OTA to a newer android version without taking a proper backup. A really bad experience with Xiaomi. it cost me one day to try to fix and will be costing me some time to install everything back after the repair. I am seriously thinking to buy an iPhone now.
lord219 said:
Just an update. I was using Macbook to test if the device is alive. MacBook Pro doesn't show any updates when you connect a new device. I plugged USB into a Windows machine installed on my Bootcamp, Windows recognized the device as Qualcomm 9008. Which is effectively in EDL mode. I have no idea how the device got into that mode but my assumption is that I had TWRP installed with BL open and when going from Android 11 to Android 12 via MIUI13, something called anti-rollback protection which was implemented by Xiaomi put the phone into EDL mode. Luckily, I am in the UK and got in touch with Xiaomi after sales, they agreed to repair it because the issue was caused by a software update.
Lesson Learned: Never update your phone via OTA to a newer android version without taking a proper backup. A really bad experience with Xiaomi. it cost me one day to try to fix and will be costing me some time to install everything back after the repair. I am seriously thinking to buy an iPhone now.
Click to expand...
Click to collapse
I dont think its about anti-rollback function
That function only affect when u try to flash from higher miui version back to lower version. It will not allow u to do that
In your case, it 's all about xiaomi software problem :| and it is unacceptable problem
hungragezone said:
I dont think its about anti-rollback function
That function only affect when u try to flash from higher miui version back to lower version. It will not allow u to do that
In your case, it 's all about xiaomi software problem :| and it is unacceptable problem
Click to expand...
Click to collapse
Well, finally I got in touch with the EDL guy and he fixed it smoothly. I literally had to go through a lot of documents and websites to understand the problem but he fixed it in 10 minutes. I think he is using some sort of cracked miFlashTool where he interferes with the communication between the phone and Xiaomi servers and bypasses authorization issues. I think many people are having problems at that point when following the EDL operation explained on the internet. Anyways, fixed it fairly easily and cheaply.
lord219 said:
Well, finally I got in touch with the EDL guy and he fixed it smoothly. I literally had to go through a lot of documents and websites to understand the problem but he fixed it in 10 minutes. I think he is using some sort of cracked miFlashTool where he interferes with the communication between the phone and Xiaomi servers and bypasses authorization issues. I think many people are having problems at that point when following the EDL operation explained on the internet. Anyways, fixed it fairly easily and cheaply.
Click to expand...
Click to collapse
For edl, did he install MIUI 12 or MIUI 13?
i thing they have installed the new Miui 13
chiposh said:
For edl, did he install MIUI 12 or MIUI 13?
Click to expand...
Click to collapse
For EDL, Miui 12.5-global eu rom. I later on updated to miui13 with no issue.
lord219 said:
For EDL, Miui 12.5-global eu rom. I later on updated to miui13 with no issue.
Click to expand...
Click to collapse
That's very strange. Why first update led to brick
By Global eu rom you mean EEA or Xiaomi.eu ROM?
p.s. I know at least one Mi 11 ultra and one Mi 11 faced the same issue
chiposh said:
That's very strange. Why first update led to brick
By Global eu rom you mean EEA or Xiaomi.eu ROM?
p.s. I know at least one Mi 11 ultra and one Mi 11 faced the same issue
Click to expand...
Click to collapse
lord219 said:
Well, finally I got in touch with the EDL guy and he fixed it smoothly. I literally had to go through a lot of documents and websites to understand the problem but he fixed it in 10 minutes. I think he is using some sort of cracked miFlashTool where he interferes with the communication between the phone and Xiaomi servers and bypasses authorization issues. I think many people are having problems at that point when following the EDL operation explained on the internet. Anyways, fixed it fairly easily and cheaply
Click to expand...
Click to collapse
hi how can i get in contact with that EDL
my mi ultra its rebooting on fastboot mode only
i think i lost my phone i cant use it just bought it yesterday and it only goes on fastboot after restart
i had to buy a cheap phone today i called costumer service they keep hanging up each time while i talk to them
my fastboot is locked and my brain 2 is locked dont know hat to do anymore
If you can get to fastboot, you can flash the original stock ROM. Plenty of instructions here and on the Xiaomi EU forums. You only need edl if you cannot get to fastboot.
Sathelp said:
If you can get to fastboot, you can flash the original stock ROM. Plenty of instructions here and on the Xiaomi EU forums. You only need edl if you cannot get to fastboot.
Click to expand...
Click to collapse
You cannot flash anything in fastboot if bootloader is locked
In that case, you will need an edl flash to recover. But be careful that he doesn't leave it with an edl account permission or you won't be able to unlock without that edl account. Although I thought you could flash the original stock firmware that it came with back on with it locked.
Hi, i have same problem after try to flash Miui 13. But The MIflash tool shows error:sw path is not valid, have not found solution for this error message. How can I Get in contact with the EDl Guy.. I have a Mi 11 Pro
Reminds my about the new released Samsung galaxy S22 series, lots of problems for some weeks now_
It´s so frustrating that the update caused this. It´s now the first time for me to solve this problem. But I have so many other issues that I don´t have the time for this. I´ve read some threads where some persons have written about people who can unbrick it online. This would be right now my first choice. Could somebody help me where I can contact someone for help please.
locdogyuga said:
It´s so frustrating that the update caused this. It´s now the first time for me to solve this problem. But I have so many other issues that I don´t have the time for this. I´ve read some threads where some persons have written about people who can unbrick it online. This would be right now my first choice. Could somebody help me where I can contact someone for help please.
Click to expand...
Click to collapse
im sending you link now who to contact and this is not spam
Hello same here - I guess flashed wrong version from EEA instead of EU of Android 11 - all went good but then I allowed OTA updates and finally update to MUI13 I had a brick.
Now I am in contact with one EDL guy but not certain he is legit. Can you send me PM for your contact?
I'm planning on purchasing this phone but things like this one makes me worried. Is there a risk to update the eu stable firmwares from fastboot with bootloader unlocked?
If you know how to do it, no risk.