Hi all,
Recently I did the following:
1 - unlock device
2 - flash rom (clean all and lock)
3 - erro message appears "This MIUI version can't be installed on this device"
I am stuck
I can repeat the process, to unlock device I have to go to MIUI settings and to do that I need a rom.
Miui pc suite doesn't detect the device no matter what.
{
"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"
}
flash rom (clean all and lock) is wrong. You should not choose this option as it will brick your phone.
Try to use MiFlash to flash a fastboot rom and see if it helps.
HKShooter said:
flash rom (clean all and lock) is wrong. You should not choose this option as it will brick your phone.
Try to use MiFlash to flash a fastboot rom and see if it helps.
Click to expand...
Click to collapse
I know, but I miss that point and I recognized the mistake late after.
I try what you said with different roms (EEA, GLOBAL and Chinese) I doesn't start the flash process due to an error. The error is because the phone is locked and is not possible to rewrite.
Try this to see if it works for you
http://c.mi.com/thread-238808-1-0.html
Or try that like in the video: https://www.youtube.com/watch?v=5o2WJZ5nTnY
HKShooter said:
Or try that like in the video:
Click to expand...
Click to collapse
I am not able to flash or do any fastboot commands because the device is locked
Jester646 said:
I am not able to flash or do any fastboot commands because the device is locked
Click to expand...
Click to collapse
MiFlash Tool cannot recognize your phone?
HKShooter said:
MiFlash Tool cannot recognize your phone?
Click to expand...
Click to collapse
MiFlash tool recognize the device but gives me an error "erase boot error" when I try to flash it
Flashing via MiFlash tool I need to unlock bootloader
To unlock bootloader I need to add the miui account in Mi Unlock status under developer options...to do that I need a rom. Rom doesn't work because "can't be installed on this device"
HKShooter said:
Or try that like in the video:
Click to expand...
Click to collapse
EDL method is a great option unfortunately doesn't work on CC9PRO/NOTE10
Jester646 said:
EDL method is a great option unfortunately doesn't work on CC9PRO/NOTE10
Click to expand...
Click to collapse
If it still doesn't work, you need to go to the Xiaomi service center.
Since its locked with no ROM, i dont think i can help you . Last thing i can suggest is using test point method, which means you need to pry open your backglass cover.
HKShooter said:
If it still doesn't work, you need to go to the Xiaomi service center.
Click to expand...
Click to collapse
Xiaomi service center message "I would like to inform you that we won't be able to assist in this regard as your device has been bricked. However, I would request you kindly get in touch with the respective point of purchase." I bought this device during a China trip, I live in Germany.
I am able to use MiFlash PRO and flash the same ROM trough the option Recovery Flash, however, I don't solve the issue.
I am not able to use other rom: "current ROMs network carrier type is different from that in the recovery package."
Any suggestions?
Jester646 said:
I am able to use MiFlash PRO and flash the same ROM trough the option Recovery Flash, however, I don't solve the issue.
I am not able to use other rom: "current ROMs network carrier type is different from that in the recovery package."
Any suggestions?
Click to expand...
Click to collapse
if you really desperate, try the test point method.
Jester646 said:
Xiaomi service center message "I would like to inform you that we won't be able to assist in this regard as your device has been bricked. However, I would request you kindly get in touch with the respective point of purchase." I bought this device during a China trip, I live in Germany.
Click to expand...
Click to collapse
The service center must be able to help. Did you tell them honestly that you flashed the international Rom and bricked it? If you were in China, there should be shops in Shenzhen who can help you.
HKShooter said:
The service center must be able to help. Did you tell them honestly that you flashed the international Rom and bricked it? If you were in China, there should be shops in Shenzhen who can help you.
Click to expand...
Click to collapse
He live in germany. And his phone is china model, thus i doubt the xiaomi representative in germany would like to help. Since its uncovered by eu warranty. I guess he gonna have to spend some amount of money to get it fixed. Or experimenting with test point himself.
otonieru said:
He live in germany. And his phone is china model, thus i doubt the xiaomi representative in germany would like to help. Since its uncovered by eu warranty. I guess he gonna have to spend some amount of money to get it fixed. Or experimenting with test point himself.
Click to expand...
Click to collapse
In Hongkong, the people can take the phone to the service centers in China to repair it. Xiaomi sells international version only in HK. I think there is no need to tell whether it's a China version or EU version as it's bricked and the phone looks the same. Maybe there are some shops in Germany who can help.
otonieru said:
He live in germany. And his phone is china model, thus i doubt the xiaomi representative in germany would like to help. Since its uncovered by eu warranty. I guess he gonna have to spend some amount of money to get it fixed. Or experimenting with test point himself.
Click to expand...
Click to collapse
I ordered a Deep flash cable, that may help, it is expected to be delivered on Saturday. I will share the results after... I didn't find enough information about the testing points to open the device yet.
HKShooter said:
In Hongkong, the people can take the phone to the service centers in China to repair it. Xiaomi sells international version only in HK. I think there is no need to tell whether it's a China version or EU version as it's bricked and the phone looks the same. Maybe there are some shops in Germany who can help.
Click to expand...
Click to collapse
I am sure people more flexible than others but if by email they said no after being honest. There is no point for me to go door by door. In last scenario I may have a business trip to CN after CNY, if yes, I take the phone with me and I am sure that in there I solve it (from past experience).
Jester646 said:
I ordered a Deep flash cable, that may help, it is expected to be delivered on Saturday. I will share the results after... I didn't find enough information about the testing points to open the device yet.
Click to expand...
Click to collapse
as far as i know, deep flash cable is no longer working since miui 10. i might be wrong though
Related
(First of all sorry for my English, I'm from Mexico)
Hello Friends, this is my first post, however, I have always used this forum as a guide along the phones I have had.
A few days ago I made a Hard Brick to my Mi Note 10 Pro, this while trying to load the Xiaomi EU Rom. I have seen many tutorials where they indicate how to revive it, without success since most are focused on the phone turning on in Fastboot mode, mine does not turn on in any way
I managed to make the phone recognize the PC in EDL mode but when flashing in Mi Tools it asks for a My account, when entering it the software tells me that my account is not authorized to carry out that transaction.
{
"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"
}
Someone here managed to solve this or know of some method in which you do not need that authorized account and finally retrieve the phone?
I would greatly appreciate your help
dbaesteban said:
(First of all sorry for my English, I'm from Mexico)
Hello Friends, this is my first post, however, I have always used this forum as a guide along the phones I have had.
A few days ago I made a Hard Brick to my Mi Note 10 Pro, this while trying to load the Xiaomi EU Rom. I have seen many tutorials where they indicate how to revive it, without success since most are focused on the phone turning on in Fastboot mode, mine does not turn on in any way
I managed to make the phone recognize the PC in EDL mode but when flashing in Mi Tools it asks for a My account, when entering it the software tells me that my account is not authorized to carry out that transaction.
Someone here managed to solve this or know of some method in which you do not need that authorized account and finally retrieve the phone?
I would greatly appreciate your help
Click to expand...
Click to collapse
do fastboot mode work?
albo.ma said:
do fastboot mode work?
Click to expand...
Click to collapse
Fastboot is an Android protocol that allows you to modify the filesystem through a USB connection to the smartphone, however, in my case it does not enter that mode, only EDL
i'm sorry but never happened to me... did u tried mi flash to flash something? does mi flash recognize your mi note 10 in edl mode?
albo.ma said:
i'm sorry but never happened to me... did u tried mi flash to flash something? does mi flash recognize your mi note 10 in edl mode?
Click to expand...
Click to collapse
Yes, I already tried Mi Flash, but it seems that you need an authorized account, here is the image of the software:
You could try QFIL (Qualcomm Flash Image Loader). I personally haven't needed to use it but it's designed to work with all Qualcomm Android devices.
Some info links
https://androidmtk.com/use-qualcomm-flash-image-loader-qfil
https://androidmtk.com/download-qpst-flash-tool
https://www.google.co.nz/url?sa=t&s...jAEegQIDBAO&usg=AOvVaw2g_XEnwfWA5Aj-IyquRhN2p
did a quick research and found these:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
patched version of mi flash to bypass authorization, but for redmi note 5 - check the thread if it works for other models too
https://in.c.mi.com/thread-1571278-1-1.html
people are requesting authorization there, do not know if they ever succeed but maybe it is worth to try
grandma_p said:
did a quick research and found these:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
patched version of mi flash to bypass authorization, but for redmi note 5 - check the thread if it works for other models too
https://in.c.mi.com/thread-1571278-1-1.html
people are requesting authorization there, do not know if they ever succeed but maybe it is worth to try
Click to expand...
Click to collapse
It seems to work, I have been trying for several hours to find the right .mbl for the MI CC9 Pro without success, I will continue searching and inform you.
Thank you for the support!
It looks like Mi Tools need to bind your computer to your device in order to give you authorization, i think you need to ask for authorization in the Official Xiaomi Support Forums.
tadad1 said:
You could try QFIL (Qualcomm Flash Image Loader). I personally haven't needed to use it but it's designed to work with all Qualcomm Android devices.
Some info links
https://androidmtk.com/use-qualcomm-flash-image-loader-qfil
https://androidmtk.com/download-qpst-flash-tool
https://www.google.co.nz/url?sa=t&s...jAEegQIDBAO&usg=AOvVaw2g_XEnwfWA5Aj-IyquRhN2p
Click to expand...
Click to collapse
Thanks, I'm still looking for the correct files for Mi Note 10 Pro, it seems they are limited
CescVicious said:
It looks like Mi Tools need to bind your computer to your device in order to give you authorization, i think you need to ask for authorization in the Official Xiaomi Support Forums.
Click to expand...
Click to collapse
Thank you !, I already tried and posted to see if they hopefully give me authorization :good:
dbaesteban said:
Thanks, I'm still looking for the correct files for Mi Note 10 Pro, it seems they are limited
Click to expand...
Click to collapse
You need to download a fastboot ROM, I checked and they were all there although in the video there is only one XML file but in the MIUI fastboot ROM there are 5 but I was able to load them into QFIL so I think it would not be a problem.
Have a look here you will find all the tucana ROMs
https://t.me/s/MIUIUpdatesTracker?q=#tucana
The last fastboot ROM was 11.0.9.0. you will need to extract the .tgz file which will give you a .tar file which you need to then extract again to get the files needed.
tadad1 said:
You need to download a fastboot ROM, I checked and they were all there although in the video there is only one XML file but in the MIUI fastboot ROM there are 5 but I was able to load them into QFIL so I think it would not be a problem.
Have a look here you will find all the tucana ROMs
https://t.me/s/MIUIUpdatesTracker?q=#tucana
The last fastboot ROM was 11.0.9.0. you will need to extract the .tgz file which will give you a .tar file which you need to then extract again to get the files needed.
Click to expand...
Click to collapse
Yes, in fact I tried all the xml files and their possible combinations without success.
The file "programmer patch", in this case comes in extension .elf and in the videos that I have seen is extension .mbn, Additional the first xml that is loaded is also called rawprogram.xml in the firmware for my Note 10 there are none file named like that.
I will keep searching and if I find something, I will post it for users who have this problem in the future
this is the error that gives me in all cases
.elf and .mbl are both supported by QFIL so should be fine. I have 6 .XML, rawprogram0.xml to rawprogram5.xml. When I press the load XML button I can click and drag and select them all at once. It then prompts me to load the patch.xml once again patch0.xml to patch5.xml and drag and select all. They should now all appear in the Rawprogram and Patch window. Unfortunately I can't get into EDL mode to try flashing but it looks like you are already in EDL. All the best.
Well, after many days of searching without solution, I decided to take it to the technical service, who flashed it in EDL mode with the UFT box.
The cell phone is walking and without any anomaly.
Thank you all for your valuable help.
dbaesteban said:
Well, after many days of searching without solution, I decided to take it to the technical service, who flashed it in EDL mode with the UFT box.
The cell phone is walking and without any anomaly.
Thank you all for your valuable help.
Click to expand...
Click to collapse
is there any way other than UFT box to unbrick the phone mine have working EDL, fastboot , offical recovery but relock bootloader ..:crying:
I am having the exact issue in attempt to update the rom through fastboot. My tucana is no more responding to charging, pwr + Vol combination, detection to laptop etc. I have tried making my own EDL cable and its working with K20 but not with Tucana. Can you please brief how you managed to get phone into EDL mode?
As title.
Thanks.
gords78 said:
As title.
Thanks.
Click to expand...
Click to collapse
Hope this link helps
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
Good luck!
orb3000 said:
Hope this link helps
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
Good luck!
Click to expand...
Click to collapse
Thanks, my device is a Redmi 6 with locked bootloader and I'm pretty sure there are no workarounds.
gords78 said:
Thanks, my device is a Redmi 6 with locked bootloader and I'm pretty sure there are no workarounds.
Click to expand...
Click to collapse
I've bricked my friend's redmi note 7 about a month ago and encountered the same issue as I flashed miui global rom into a chinese version via miflash tool with option 'flash all and lock'. She said she bought the device not from an official mi store but instead from a distributor which I think had flashed some modified chinese rom to appear as global one. So the device was in locked bootloader state, and after turning it on it always boots up into mi recovery. After done so many hours researching on the internet about how to bypass this lock bootloader and flash the right version of firmware in edl mode without authorized account, I've successfully unbrick the phone after flashing the firmware with a patched firehose file for redmi note 7. Try it mate. Hope it helps u. Cheers.
Prodai said:
I've bricked my friend's redmi note 7 about a month ago and encountered the same issue as I flashed miui global rom into a chinese version via miflash tool with option 'flash all and lock'. She said she bought the device not from an official mi store but instead from a distributor which I think had flashed some modified chinese rom to appear as global one. So the device was in locked bootloader state, and after turning it on it always boots up into mi recovery. After done so many hours researching on the internet about how to bypass this lock bootloader and flash the right version of firmware in edl mode without authorized account, I've successfully unbrick the phone after flashing the firmware with a patched firehose file for redmi note 7. Try it mate. Hope it helps u. Cheers.
Click to expand...
Click to collapse
Thanks. This is my exact situation too. Bought as global version on eBay but after locking the bootloader found out its Chinese. Was going to give the firehose method a go tonight but read id still need an authorised account. Will give it a go.
Solved to a certain degree. My handset doesn't support EDL as its a Mediatek chipset.
Prodai said:
I've bricked my friend's redmi note 7 about a month ago and encountered the same issue as I flashed miui global rom into a chinese version via miflash tool with option 'flash all and lock'. She said she bought the device not from an official mi store but instead from a distributor which I think had flashed some modified chinese rom to appear as global one. So the device was in locked bootloader state, and after turning it on it always boots up into mi recovery. After done so many hours researching on the internet about how to bypass this lock bootloader and flash the right version of firmware in edl mode without authorized account, I've successfully unbrick the phone after flashing the firmware with a patched firehose file for redmi note 7. Try it mate. Hope it helps u. Cheers.
Click to expand...
Click to collapse
I've bricked my poco f3. samen issue. tried Qfil an QPST. no luck. did you use a stock rom?
Try w
Prodai said:
I've bricked my friend's redmi note 7 about a month ago and encountered the same issue as I flashed miui global rom into a chinese version via miflash tool with option 'flash all and lock'. She said she bought the device not from an official mi store but instead from a distributor which I think had flashed some modified chinese rom to appear as global one. So the device was in locked bootloader state, and after turning it on it always boots up into mi recovery. After done so many hours researching on the internet about how to bypass this lock bootloader and flash the right version of firmware in edl mode without authorized account, I've successfully unbrick the phone after flashing the firmware with a patched firehose file for redmi note 7. Try it mate. Hope it helps u. Cheers.
Click to expand...
Click to collapse
Prodai said:
I've bricked my friend's redmi note 7 about a month ago and encountered the same issue as I flashed miui global rom into a chinese version via miflash tool with option 'flash all and lock'. She said she bought the device not from an official mi store but instead from a distributor which I think had flashed some modified chinese rom to appear as global one. So the device was in locked bootloader state, and after turning it on it always boots up into mi recovery. After done so many hours researching on the internet about how to bypass this lock bootloader and flash the right version of firmware in edl mode without authorized account, I've successfully unbrick the phone after flashing the firmware with a patched firehose file for redmi note 7. Try it mate. Hope it helps u. Cheers.
Click to expand...
Click to collapse
Try what, will please explain what you just suggested to try?
i have a redmi 5 rosy hard brick but i can enter edl without problem by using test point , flash stock rom and it worrking again
Guan Yu said:
i have a redmi 5 rosy hard brick but i can enter edl without problem by using test point , flash stock rom and it worrking again
Click to expand...
Click to collapse
Will you please share how you flashed?
Because with the MiFlash, you need Mi authorised account (about which I don't know how get one), so which tool you used?
True ayush Kushwaha said:
Will you please share how you flashed?
Because with the MiFlash, you need Mi authorised account (about which I don't know how get one), so which tool you used?
Click to expand...
Click to collapse
well you just need to check if your devices entered edl or not . you can check in device manager and make sure it named " Qualcoom Qloader 9008 " , then download stock firmware and click flashall.bat , dont use miflash
True ayush Kushwaha said:
Try w
Try what, will please explain what you just suggested to try?
Click to expand...
Click to collapse
Try flashing the right version firmware with a patched firehose file in EDL mode. You won't need authorized account anymore using these file. I was using the latest miflash tool at that time. So just give it a try first mate, hope it works for you too.
aaflan88 said:
I've bricked my poco f3. samen issue. tried Qfil an QPST. no luck. did you use a stock rom?
Click to expand...
Click to collapse
Yes i did. Qfil and QPST didn't work for me either as it still asked for an authorized account. So after researching more I found the solution; just flash the stock rom with a patched firehose file in edl mode. The latest miflash tool will do, and it won't ask for an authorized account anymore.
Guan Yu said:
i have a redmi 5 rosy hard brick but i can enter edl without problem by using test point , flash stock rom and it worrking again
Click to expand...
Click to collapse
How do you use the "test point" to access this mode. The truthful answer will allow me to fix my Note8, S6 edge, and my 1+.
Please explain
Delgoth said:
How do you use the "test point" to access this mode. The truthful answer will allow me to fix my Note8, S6 edge, and my 1+.
Please explain
Click to expand...
Click to collapse
search youtube usb edl cable or "your device name " + test point , make sure your device is recognized as Qloader 9008 not Diagnostics 900E then flash stock rom using miflash or cmd
{
"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"
}
Guan Yu said:
search youtube usb edl cable or "your device name " + test point , make sure your device is recognized as Qloader 9008 not Diagnostics 900E then flash stock rom using miflash or cmdView attachment 5556141
Click to expand...
Click to collapse
I kinda know that part already. I've dealt with 9008 and 9006 mode before on multiple devices.
But when you use a test point what equipment are you using outside just a USB cable?
Delgoth said:
I kinda know that part already. I've dealt with 9008 and 9006 mode before on multiple devices.
But when you use a test point what equipment are you using outside just a USB cable?
Click to expand...
Click to collapse
i use this lol (no joking i dont have a tweezers and i dont want to buy a new usb cable )
Prodai said:
Try flashing the right version firmware with a patched firehose file in EDL mode. You won't need authorized account anymore using these file. I was using the latest miflash tool at that time. So just give it a try first mate, hope it works for you too.
Click to expand...
Click to collapse
Thank you very much, but please tell me where I can get the patched files?
Have a xiaomi mi 11 lite 5g ne I just need an authorized mi account for flashing the edl firehose and I’m set I have no idea about how to become authorized or what to do to even find the information to gain authorization so I’m stuck. Does anyone have the information to help me become authorized or is someone authorized who can help
edl authorized for qualcomm.my device is redmi 7 onclite
thanks
hi forum,
i open a new discussion with the hope that someone (more expert than me) with a bit of patience can try to understand the situation of my 5 II (model XQAS52).
Since i've purchased this device, a couple of months ago, i' ve noticed different bugs in the daily use... Various bugs reported in another thread here on XDA. A bit annoying, if you ask me.
The firmware version is 58.1.A.3.87 and i think that OTA updates are... off.
It is possible? There is a way to understand if i'm right or not?
In case, and i don't know why, my device will not receive any kind of updates, what can i do to solve this?
I've tried to repair it with Xperia Companion but every time my device shutdown during the process, and of course it doesn't complete the repair.
My build # is 58.1.A.5.330. I would probably ask Sony why I wasn't getting updates? I might go to Sony Xperia Support and try manually downloading updates.
patrickt said:
My build # is 58.1.A.5.330. I would probably ask Sony why I wasn't getting updates? I might go to Sony Xperia Support and try manually downloading updates.
Click to expand...
Click to collapse
manual updates in the app are useless: the app indicates me that the system is already updated. Same for Xperia Companion on pc.
I've spent 700euro for this device (new, of course) only to find it in this situation... it's shameful.
KnockOut^9 said:
manual updates in the app are useless: the app indicates me that the system is already updated. Same for Xperia Companion on pc.
I've spent 700euro for this device (new, of course) only to find it in this situation... it's shameful.
Click to expand...
Click to collapse
All variants of XQ-AS52 are currently having 58.1.A.5.395 build: https://xpericheck.com/XQ-AS52
If you have bought it via official channel you can definitely raise this concern with Sony support.
You can alternately check Software Info from Service Menu to check the exact region of your device. I can't think of why but I vaguely remember that if you device is cross flashed or not in the region it initially supported then you sometime don't get OTA updates(I may be wrong too). But first step is to check with Sony support as Patrickt mentioned.
PPGX5II said:
All variants of XQ-AS52 are currently having 58.1.A.5.395 build: https://xpericheck.com/XQ-AS52
If you have bought it via official channel you can definitely raise this concern with Sony support.
You can alternately check Software Info from Service Menu to check the exact region of your device. I can't think of why but I vaguely remember that if you device is cross flashed or not in the region it initially supported then you sometime don't get OTA updates(I may be wrong too). But first step is to check with Sony support as Patrickt mentioned.
Click to expand...
Click to collapse
in fact, if i launch Xperifirm, my model on the left pane has that firmware .395 (Customized EEA).
I've bought the phone via Amazon.it (i'm from Italy), but the store is situated in London.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
when i open that link on LTA version, some info appears to me, and at the bottom, russian language is present. Is this normal? I think that my model was intended for russian market, but that store in London imported from Russia and flash the Customized EEA firmware. Is this possible?
Anyway, me too think OTA services are deactivated, at this point.
KnockOut^9 said:
in fact, if i launch Xperifirm, my model on the left pane has that firmware .395 (Customized EEA).
I've bought the phone via Amazon.it (i'm from Italy), but the store is situated in London.
View attachment 5414701
when i open that link on LTA version, some info appears to me, and at the bottom, russian language is present. Is this normal? I think that my model was intended for russian market, but that store in London imported from Russia and flash the Customized EEA firmware. Is this possible?
Anyway, me too think OTA services are deactivated, at this point.
Click to expand...
Click to collapse
Hmm, looks like it. Create a support topic on Sony mobile forum or chat with support(if available in your region) to check if this device is official under warranty and then follow-up with them to solve the issue.
There can be alternate solution if your device is not officially supported by Sony(use Xperifirm or something like that) but first check if it's under warranty.
PPGX5II said:
Hmm, looks like it. Create a support topic on Sony mobile forum or chat with support(if available in your region) to check if this device is official under warranty and then follow-up with them to solve the issue.
There can be alternate solution if your device is not officially supported by Sony(use Xperifirm or something like that) but first check if it's under warranty.
Click to expand...
Click to collapse
the truth is... i only want my device works properly. I really like Xperia devices (SP, M5, X, XZ, XZ2 and now this), and i'm really disappointed this time, sorry.
I'm seriously thinking to flashing it with and old firmware with Android 10. Maybe i'm wrong? I don't care, later with future updates, i can always flash it again with updated firmware (hoping for the best). My personal problem is that i'm totally noob in this kind of things, i don't wank risk to ruins my phone.
So, if someone with a bit of patience can help me to flashing and old firmware (i have it already: Android 10 Customized EEA) would do make me a favor. It doesn't matter if my OTA Services would continue to stay deactivated. But, at least, my Xperia should be works great with A10.
i contacted SONY with email, but is not very helpful to me. They say, of course, to send the phone to the original Store in London, or to send it in Verona city (here in Italy) for assistance and repair.
The problem is i have no other spare phone to use, at the moment when my XPeria 5 II will be in Assistency.
Xperifirm show me the different firmwares available for my model (XQ-AS52).
I suppose to download the first, perhaps (?) and flash it.
Every updated firmware there in the list have italian language?
I would try first factory reset. power button and volume down and factory reset. If that doesnt work you can try and flash the newest europe firmware for your 52 model
Cptnfruitloops said:
I would try first factory reset. power button and volume down and factory reset. If that doesnt work you can try and flash the newest europe firmware for your 52 model
Click to expand...
Click to collapse
hi Cptmfruitloops and thanks for your reply.
I will try your suggestion: if i push power button+volume down will appear to me some sort of... recovery with various options, i understand right?
yeah power down and then hold power button and volume down until it vibrates then let go and you will be greeted with recovery and from there you can factory reset your phone. Before you do though log out of google on the phone and remove the device from your account (not required but recomended)
Cptnfruitloops said:
yeah power down and then hold power button and volume down until it vibrates then let go and you will be greeted with recovery and from there you can factory reset your phone. Before you do though log out of google on the phone and remove the device from your account (not required but recomended)
Click to expand...
Click to collapse
Done, but for now with the smartphone connected on Wifi, no system-updates yet.
No Google account logged in, nothing of nothing, no sim-card inside (i use my number and my account on another phone at the moment), but i don't think all of that is a problem.
I will wait a few hours, 1/2 days perhaps, if the updates don't arrive, i will try again a software-repair with Xperia Companion.
Thanks Cptnfruitloops. If you have other suggetions, i'm all ears.
KnockOut^9 said:
Done, but for now with the smartphone connected on Wifi, no system-updates yet.
No Google account logged in, nothing of nothing, no sim-card inside (i use my number and my account on another phone at the moment), but i don't think all of that is a problem.
I will wait a few hours, 1/2 days perhaps, if the updates don't arrive, i will try again a software-repair with Xperia Companion.
Thanks Cptnfruitloops. If you have other suggetions, i'm all ears.
Click to expand...
Click to collapse
Perhaps you have the sony update servers somehow blocked on your network. You can contact sony or perhaps try flashing newest firmware
Cptnfruitloops said:
Perhaps you have the sony update servers somehow blocked on your network. You can contact sony or perhaps try flashing newest firmware
Click to expand...
Click to collapse
yeah, i've used Newflasher (by munjeni) and everything's ok. The problem is that OTA are always blocked. I think this is the situation, basing myself on other users experiences in the Newflasher official thread.
Every new firmware i should flash it manually with Newflasher. This is... a little annoying of course, so i think to flash my phone again in the future, maybe 1 year, when Android 12 is available and perhaps with future updates firmwares, more stable.
Hi I'm in the same situation, I buy my xperia 5 ii on Amazon.de from Italy and it doesn't update. I will make the return.
xire68 said:
Hi I'm in the same situation, I buy my xperia 5 ii on Amazon.de from Italy and it doesn't update. I will make the return.
Click to expand...
Click to collapse
hi xire68, i'm sorry to read this. From what i've read on the past months, many users here and on the web, are encounters our problem, the same problem: no OTA updates on their devices.
I don't know yet why this happens: the only way to update our smartphones is to use Newflasher (by munjeni), download the firmware you want and flash it. The method is very very simple, but i understand this is not a good way to updates our phones. We've paid for this Xperia, in my case 699euro and i expect updates like should be. And not to solve the problem with alternative methods.
Anyway, i understand your move.
This was a Untested MSM .OPS file for the EU Variant use at your own risk.
This was tested by @lockmunk and verified to be working for the EU varient of the device check post 4 if you want to see proof.
This will fail verification when pressing verify because the msm tools used was originally global msm,i just swapped the ops files so it could be flashed.
This was made using the files linked here : https://forum.xda-developers.com/t/...oneplus-9-le2113-with-msm-tool.4320461/page-2
ANY AND ALL DAMAGE DONE TO YOUR DEVICE AFTER THIS IS NOT MY RESPONSIBILITY.....
I take no responsibility for you hardbricking your device or it becoming nonworking after this......
This is OxygenOS_11.2.7.7.LE25BA firmware as shown in the screenshot in post #4
https://www.mediafire.com/file/gyv5gza7t4ibn7j/OnePlus_9_EU_lemonade_22_E.10_210609.zip/file
PREREQUISITES
MUST HAVE QUALCOMM DRIVER'S INSTALLED (FOR EDL TO WORK!!)
CLICK LINK DOWNLOAD MSM TOOL
UNZIP
CLICK ON MSM TOOL
RUN AS OTHER!!
REBOOT TO EDL.
(POWER OFF)
HOLD BOTH VOLUME UP AND DOWN CONNECT TO PC
WHEN YOU SEE CONNECTED CLICK START AND LET IT RUN DEVICE WILL REBOOT ONCE & DONE!!!
wow this is nice. can someone test it?
dear @allenjthomsen a
Found that MD5 checksum failed
{
"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"
}
ok I risk myself to tried it out.
and the results is...it REALLY WORKS!!
below is my settings in MSM and about phone
lockmunk said:
dear @allenjthomsen a
Found that MD5 checksum failed
View attachment 5479725
Click to expand...
Click to collapse
It will fail md5 verification because msm tools in this file were originally global i just swapped the ops file.
lockmunk said:
ok I risk myself to tried it out.
and the results is...it REALLY WORKS!!
below is my settings in MSM and about phone
Click to expand...
Click to collapse
this is good im glad it was able to restore your phone to EU
My model is le2110 and a bit afraid of bricking. Anyone tested on 2110?
azizolmez said:
My model is le2110 and a bit afraid of bricking. Anyone tested on 2110?
Click to expand...
Click to collapse
LE2110 is CN and normally comes with Colour OS unless converted to IN firmware. LE2113 is EU. LE2115 is NA/Global.
This info was taken from OP9 community forum.
allenjthomsen said:
LE2110 is CN and normally comes with Colour OS unless converted to IN firmware. LE2113 is EU. LE2115 is NA/Global.
This info was taken from OP9 community forum.
Click to expand...
Click to collapse
Converted oos11 then flashed havoc. Now I want to go back to stock.
Thanks you a lot for making this. Sorry cause i m asking but, can it be done with last 11.2.10.10 too? Thanks xDD
azizolmez said:
Converted oos11 then flashed havoc. Now I want to go back to stock.
Click to expand...
Click to collapse
you can use it with no problem, i have LE2110 too, but i live in Europe. Until now i was using GLOBAL MSM to get OOS and flashing Europe by local update.
Sheldd said:
Thanks you a lot for making this. Sorry cause i m asking but, can it be done with last 11.2.10.10 too? Thanks xDD
Click to expand...
Click to collapse
I'm not sure thats possible unless the msm files could be found like the ones provided in the thread that i linked, best i can say for now is just use the provided msm i made and update via settings to latest firmware.
Sheldd said:
Thanks you a lot for making this. Sorry cause i m asking but, can it be done with last 11.2.10.10 too? Thanks xDD
Click to expand...
Click to collapse
When I try this files, I also on this version. Should be no problem. Then now I updated to 11.2.10.10 without any problem.
allenjthomsen said:
This was a Untested MSM .OPS file for the EU Variant use at your own risk.
This was tested by @lockmunk and verified to be working for the EU varient of the device check post 4 if you want to see proof.
This will fail verification when pressing verify because the msm tools used was originally global msm,i just swapped the ops files so it could be flashed.
This was made using the files linked here : https://forum.xda-developers.com/t/...oneplus-9-le2113-with-msm-tool.4320461/page-2
ANY AND ALL DAMAGE DONE TO YOUR DEVICE AFTER THIS IS NOT MY RESPONSIBILITY.....
I take no responsibility for you hardbricking your device or it becoming nonworking after this......
This is OxygenOS_11.2.7.7.LE25BA firmware as shown in the screenshot in post #4
OnePlus_9_EU_lemonade_22_E.10_210609.zip
drive.google.com
PREREQUISITES
MUST HAVE QUALCOMM DRIVER'S INSTALLED (FOR EDL TO WORK!!)
CLICK LINK DOWNLOAD MSM TOOL
UNZIP
CLICK ON MSM TOOL
RUN AS OTHER!!
REBOOT TO EDL.
(POWER OFF)
HOLD BOTH VOLUME UP AND DOWN CONNECT TO PC
WHEN YOU SEE CONNECTED CLICK START AND LET IT RUN DEVICE WILL REBOOT ONCE & DONE!!!
Click to expand...
Click to collapse
Work fine on my OnePlus 9, thank you for saving my phone
I flashed with MSM Tool to my LE2110 but Model Number doesn't change
isson said:
I flashed with MSM Tool to my LE2110 but Model Number doesn't change
Click to expand...
Click to collapse
based on my experience with OP devices the model number will not change on your device even if you flash a different msm.
isson said:
I flashed with MSM Tool to my LE2110 but Model Number doesn't change
Click to expand...
Click to collapse
The model number wont change by flashing a diferent region rom. Only if you flash the weirdo OOS12 update you will see LE2115 xDD
I flashed with MSM Tool to my LE2110 works very well , but im unchecked all
the model name remain the same too, but no problem finally we have a tool to re-alive our op9
thanks boss
Would this work with the T-Mobile op9? I went that whole India 9pro direction and now my phone can't use the fingerprint sensor or proximity sensor. Any feedback would be great thanks.
I have one question, since supported LTE frequencies is a software limitation, flashing the EU version when we come from global rom change something one le2110 model?
akboy7015 said:
I have one question, since supported LTE frequencies is a software limitation, flashing the EU version when we come from global rom change something one le2110 model?
Click to expand...
Click to collapse
no changement, no change name model remain all perfect as a new model
Hello,
I dunno if this thread is still active but I have the EU variant Poco F2 Pro and this has been untouched since 2020(no I regret not unlocking the bootloader). And just last week, (I think) after receiving the latest patch update, I suddenly lost my baseband. Hence I now have no signal. I have raken my ohone to a technician for consultation and checkup and he was the one who noticed the "unknown baseband", Suffice to say my IMEI is also gone. He told me that rhe only way to solve this is to reflash OS. Unfortunately, my bootloader is still locked because I said this is still untouched (I regret it now).
So I did some research and came across this DFT Pro Tool for mobile maintenance which works on multiple brands and claims it can fix the IMEI/baseband issue even with bootloader locked. PROBLEM IS, you have to buy it for $70 and for something you'll gonna be using just once, that is a huge sum.
Now I have sent Fredback to Poco about this and requested for a rollback update (idk if they reply to such cases) just to see if the current update is the issue. I have also tried redownloading and reflashing the full latest firmware via the update menu but it did not solve anything.
The last thing on my mind is to reflash an older version (maybe 13.0.5.0, 4.0, or 3.0) via recovery but I know xiaomi and Poco implemented an anti rollback feature (which I now think is kinda selfish and stupid of them).
I also have this crazy idea of extracting the baseband zip from a previous version of the rom, renaming it 'update.zip" and flashing but I doubt that it's as simple as that.
Anyone encountered a similar issue?
{
"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"
}
ichigo_kurosaki said:
Hello,
I dunno if this thread is still active but I have the EU variant Poco F2 Pro and this has been untouched since 2020(no I regret not unlocking the bootloader). And just last week, (I think) after receiving the latest patch update, I suddenly lost my baseband. Hence I now have no signal. I have raken my ohone to a technician for consultation and checkup and he was the one who noticed the "unknown baseband", Suffice to say my IMEI is also gone. He told me that rhe only way to solve this is to reflash OS. Unfortunately, my bootloader is still locked because I said this is still untouched (I regret it now).
Click to expand...
Click to collapse
V13.0.8.0.SJKEUXM is a stable beta, and yes Xiaomi is updating with Beta versions on the stable channel and this is nothing new, many like you have found themselves with bricked phones.
At first tried with https://www.xiaomitool.com/V2/ if no result reposted.
Will it work even with locked bootloader? Thanks for the reply anyway.
ichigo_kurosaki said:
Will it work even with locked bootloader? Thanks for the reply anyway.
Click to expand...
Click to collapse
First try to reinstall the same version with the OTA.
NOSS8 said:
First try to reinstall the same version with the OTA.
Click to expand...
Click to collapse
Already did that. Tried the ota and the full rom (download full package).
ichigo_kurosaki said:
Already did that. Tried the ota and the full rom (download full package).
Click to expand...
Click to collapse
So;use https://www.xiaomitool.com/V2/,select bricked device.(Not 100% guaranteed that it will work)
NOSS8 said:
So;use https://www.xiaomitool.com/V2/,select bricked device.(Not 100% guaranteed that it will work)
Click to expand...
Click to collapse
Yes you are right. This method is not guaranteed. I tried to trick the tool into thinking my Poco F2 Pro was bricked. I got as far as to the firmware selwction for my device (there was IMI and IMI-new) but I thinkini represents redmi k30 pro because when i tried to proceed it was searching for china rom (when in fact I have F2 eu variant). Idk what imi new is. Maybe that is my device/global and eu f2. But when i tried to proceed i get this error i was lucky to cime uo upon doing google search.
Try with the same rom or update.
This tool is able to detect the rom.
NOSS8 said:
Try with the same rom or update.
This tool is able to detect the rom.
Click to expand...
Click to collapse
So i gotta use "my device is working" then "i want to mod ot" then select my rom file?
ichigo_kurosaki said:
So i gotta use "my device is working" then "i want to mod ot" then select my rom file?
Click to expand...
Click to collapse
try what is possible.
NOSS8 said:
try what is possible.
Click to expand...
Click to collapse
Almost succeeded. Lol. I went in to Mi Assistant in recovery so just to make the device appear in pcsuite mode. All was qell .a rom was found for my device. Almost done flashing then $hit happens and i was booted back (thankfully) to my current system.
NOSS8 said:
try what is possible.
Click to expand...
Click to collapse
Almost succeeded. Lol. I went in to Mi Assistant in recovery so just to make the device appear in pcsuite mode. All was qell .a rom was found for my device. Almost done flashing then $hit happens and i was booted back (thankfully) to my current
Hi, i have the global version (POCO F2 PRO) in the last month i had this problem. I dont know the reason, never did something whith software , only one day the phone freezen and when i do the reboot los this information. You have good news?? pd: sorry for my english no is my principal lenguage
Hello..
Please any solution yet? I also have Poco f2 pro global with same issue (bootloader is locked).. and currently the phone is not recognised by any pc(only charging) all settings are okay. The phone is not even reading USB otg flash storage again.