Its almost October and I'm still stuck on EMUI 4.1. My model is BLN-L21, middle east variant, not rooted. Updater still says no update available
{
"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"
}
Any help would be greatly appreciated.
You're on latest update, as you can check here http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=bln-l21c185b140&firmware_page=0 without a model debranding, at the moment you cannot receive other updates.
So I wont be getting emui 5 or 6 for that matter?
BELIEVER PK said:
So I wont be getting emui 5 or 6 for that matter?
Click to expand...
Click to collapse
Exactly, not for now at least without a device rebranding. Oh yes, EMUI 6 will be on Oreo, and we still don't know for sure if our device will finally get it or not.
BELIEVER PK said:
Its almost October and I'm still stuck on EMUI 4.1. My model is BLN-L21, middle east variant, not rooted. Updater still says no update available
Any help would be greatly appreciated.
Click to expand...
Click to collapse
i have BLN-L21 and I am on emui 5.1 with B371 update officially through the system update in settings. Also middle east variant
---------- Post added at 01:32 AM ---------- Previous post was at 01:30 AM ----------
RedSkull23 said:
You're on latest update, as you can check here http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=bln-l21c185b140&firmware_page=0 without a model debranding, at the moment you cannot receive other updates.
Click to expand...
Click to collapse
That's definitely not true. I am on BLN-L21C185B371 middle east variant
So what is wrong with mine?
oae08 said:
That's definitely not true. I am on BLN-L21C185B371 middle east variant
Click to expand...
Click to collapse
Ok sorry my bad, i put the B140 at the end and obviously MT site found only matching build firmwares.
BELIEVER PK said:
So what is wrong with mine?
Click to expand...
Click to collapse
You could try to force the update by going on system update -> clicking on the 3 dots on upper right corner -> choose 1st option, "download latest update". If nothing is found, you could flash latest update by dload method.
BELIEVER PK said:
So what is wrong with mine?
Click to expand...
Click to collapse
Flash these files via dload. it should update you to the BLN-L21C185B361 version.
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v84689/f2/full/update.zip
http://update.hicloud.com:8180/TDS/...89/f2/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_BLN-L21_hw_meafnaf.zip
Good luck
You sure its safe right? Because I've seen a lot of posts about manual updating where people are facing missing themes/fm radio/updater app and lots of bugs...
And will this void my warranty?
BELIEVER PK said:
You sure its safe right? Because I've seen a lot of posts about manual updating where people are facing missing themes/fm radio/updater app and lots of bugs...
Click to expand...
Click to collapse
This happens the most when wrong firmwares for your build number are downloaded, but with the 3 packages that shashank linked to you yes, you are safe. They're official packages that matches your build
Thanks. Will flashing these void my warranty.
And if you don't mind, could you give me instructions on how to flash via dload...
BELIEVER PK said:
Thanks. Will flashing these void my warranty.
And if you don't mind, could you give me instructions on how to flash via dload...
Click to expand...
Click to collapse
These are absolutely stock version and no warranty loss.
For dload, check my signature below for dload guide. It is quick steps for all requirements and you can flash files easily.
Call customer care or chat with their online support they will ask for IMEI and few other things and updated will be there within 48 hours they have that hi care app where u can get online support or from there website or twitter or simply by calling customer care number
Thanks
Hey guys, sorry for the necrobump. I successfully flashed update.zip using dload (had to move it to internal storage to flash successfully).
But whenever I try to flash the 2nd file "update_full_BLN-L21_hw_meafnaf.zip" it goes upto 5% and fails. Also while booting it says "Your device has failed verification and may not work properly". On top of that, I lost file manager and update option in the settings (probably because the 2nd file did not flash). And for some reason, my build no. is "NRD90M test-keys" now...
Please help.
FYI, I'm still not rooted nor unlocked Bootloader.
I had the same problem: recovery stuck at 5 % until timed-out. Please make sure that your device is not connected to your computer via USB and then reboot into recovery mode. I unplugged the cable from both devices to be very sure.
See this thread on Huawei P9: p9/help/forced-recovery-stuck-5-t3594840
Related
After updating to MM When I try to configure the screen lock I get this error, and does not recognize my sim card
Does anyone know how I can repair this?
{
"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"
}
Have you tried factory reset? Also dial *#06# and check whether the IMEI is displayed correctly or as 0/null.
Affangta said:
Have you tried factory reset? Also dial *#06# and check whether the IMEI is displayed correctly or as 0/null.
Click to expand...
Click to collapse
i already did factory reset, and the EMI it's incorrect, exist someway to fix it?
yulianov25 said:
After updating to MM When I try to configure the screen lock I get this error, and does not recognize my sim card
Does anyone know how I can repair this?
View attachment 4102748
View attachment 4102750
View attachment 4102772
Click to expand...
Click to collapse
I have exactly the same problem
It seems that one of the users (another threath LG H900 5.1 > 6.0 problem) is right and I upload software h900 6.0 via KDZ via TOT even via octopus and nothing, even the same error is possible that the main card is not h900 but another variant?, He says he solved the problem by loading vs900 software because the main card was not h900 but refurbished vs900.
I opened the phone and I was right, now i am going to load the correct software and tell you.
I am facing same problem
I don't know what i can do i brought from in dubizzle for second hand...att h900 and for me mobile hostpot not working...
Everyone getting same problem who update has phone by LGUP. Who update from FOTA like who living in US so they don't have any problem.
I brick my phone in reupdating my mobile in LGUP then I install again lollipop root version .
I face error many times but I try again and again and now I downgrade finely.
Anti roll is 2.0 that's why u can't go back to lollipop from marshmallow. But there is a way
Everything is possible if u use ur mind because it's made by human not God.
khalilrehman17 said:
Everyone getting same problem who update has phone by LGUP. Who update from FOTA like who living in US so they don't have any problem.
I brick my phone in reupdating my mobile in LGUP then I install again lollipop root version .
I face error many times but I try again and again and now I downgrade finely.
Anti roll is 2.0 that's why u can't go back to lollipop from marshmallow. But there is a way
Everything is possible if u use ur mind because it's made by human not God.
Click to expand...
Click to collapse
Please make a more detailed description, I have managed to skip antirollback protection with octopus but I leave the dead phone completely brick, another way is to force the rom but also end up killing the phone, phone no logo no load, no update mode or anything if Have you been able to bypass the protection without killing your LG could you share your method?
Any suggestion how to repair that type of problem, or how to go back to 5.1.1
thanks
I TRIED
jesemazari said:
i have exactly the same problem
it seems that one of the users (another threath lg h900 5.1 > 6.0 problem) is right and i upload software h900 6.0 via kdz via tot even via octopus and nothing, even the same error is possible that the main card is not h900 but another variant?, he says he solved the problem by loading vs900 software because the main card was not h900 but refurbished vs900.
I opened the phone and i was right, now i am going to load the correct software and tell you.
Click to expand...
Click to collapse
i tried but i can not install error coming..
If you have solution let me know...
tmdmoosa said:
i tried but i can not install error coming..
If you have solution let me know...
Click to expand...
Click to collapse
same probleme... And there no updates anymore for this lg v10 h900 at&t ???
Hellow Guys
I have a Problem With My LG V10 H900 At&t Android 5.1.1 . I cant Repair My IMEI Number ..Can some one guide me.
[email protected]
Greetings from Brazil.
There's a new update available to our loved and hated phone.
May security update on OPLS27.76.51-5.
I've downloaded using @erfanoabdi tool.
Sideload via ADB and works fine up to now.
https://erfanoabdi.000webhostapp.com/index.php?model=XT1650&sv=Blur_Version.27.11.58.griffin.retail.en.US&carrier=retbr&sn=SERIAL_NUMBER_NOT_AVAILABLE
I received it OTA. Reteu
Verstuurd vanaf mijn XT1650 met Tapatalk
Got it too, reteu. But not installed yet.
OTA
This morning, i received OTA update notification.
Just download and install.
Retapac - UBL - Stock US Oreo
In Poland ,also a news ota
Same here, received it via ota. Reteu. It's a security update to may 1st.
Anyone can share a screenshot with the bug-fixes of this version (if there are any)? Thanks in advance!
No need. Found the details on Motorola's website: https://support.motorola.com/uk/en/solution/MS129117
ENHANCEMENTS
This update introduces changes including the following:
- Android security: Includes the updates of Android security patches through May 1st, 2018.
Click to expand...
Click to collapse
I think I got a little bit better batterylife with this update. But only had it it for a day so perhaps to early to say.
Bro, please try playing pubg under stock oreo does it still lags after 3 minutes?
Thanks
bijixda said:
Bro, please try playing pubg under stock oreo does it still lags after 3 minutes?
Thanks
Click to expand...
Click to collapse
It is probably throttling due to heat. Get a Custom Kernel (or ROM), which allows you to deactivate thermal throttling.
kirkx10 said:
I think I got a little bit better batterylife with this update. But only had it it for a day so perhaps to early to say.
Click to expand...
Click to collapse
battery was bad on my phone after oreo update and with this one its gotten worse
going back to RROreo as i cant trust the official software anymore.
works on xt1650-03 reteu ?
can someone build partition gpt.bin from this ota ? i need that, please
full OTA available
The full OTA can be found here:
https://forum.xda-developers.com/moto-z/how-to/how-to-relock-bootloader-moto-z-xt-1650-t3821817
(including the gpt and any other relevant files to actually oem-lock the phone again :heart_eyes: )
Version OPLS27.76.51-7
My Phone have the July security pack. I upgraded it automatically, with the bootloader locked.
{
"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"
}
July security update - bricked phone!
Beware!
The last OTA update (OPLS27.76-51-7, July security update) bricked my Moto Z! I had no root, battery was at about 60% - now every time I try to turn it on it displays "your phone has failed verification and may not work properly" and reboots to bootloader with no way to force boot into system.
Do at least a full backup before applying!
I'll post an update as soon as I hear back from the support.
just update the july update via OTA, working just fine
- moto z 8.0 RETAPAC non root, locked bootloader
- upgrade to 8.0 from 7.1 via sideload
Updated today to july security version without problems, retmx without root.
This bricked my phone too. Can't unlock the bootloader, and Moto Support says I can't do anything but send my phone to the seller and hope for a repair. As I never flashed anything on this phone, does anyone know how to flash the right factory image and make my brick actually work again? Thank you all for your help!
stuntr38 said:
This bricked my phone too. Can't unlock the bootloader, and Moto Support says I can't do anything but send my phone to the seller and hope for a repair. As I never flashed anything on this phone, does anyone know how to flash the right factory image and make my brick actually work again? Thank you all for your help!
Click to expand...
Click to collapse
akkenoth said:
Beware!
The last OTA update (OPLS27.76-51-7, July security update) bricked my Moto Z! I had no root, battery was at about 60% - now every time I try to turn it on it displays "your phone has failed verification and may not work properly" and reboots to bootloader with no way to force boot into system.
Do at least a full backup before applying!
I'll post an update as soon as I hear back from the support.
Click to expand...
Click to collapse
and these are the exact reasons why i switched to custom rom since i no longer trust the official updates since the initial oreo release
If this this update upgrades the bootloader from 92.03 to newer in the process you cant even fix it yourself by flashing the official oreo image , even with a locked bootloader you should still be able to do that
I have an honor 6x here that has the FRP locked, bootloader unlocked and under developer options, OEM unlocking is disabled and greyed out.
I changed my oeminfo to Chinese to use oreo, and decided I wanted to go back to BLN-24 because I had tons of problems so I reflashed bln-24 oeminfo and then the latest update package on Firmware Finder for bln24 via HURU & TWRP.
I'm now on build # NRD90M test-keys, android 7.0 with emui 5.0.4.
I have stock recovery and I'm unable to do any fastboot commands since frp is locked.
I've tried the DLOAD method once, but it failed. (I only see one FULL-OTA firmware for the bln-24 on firmware finder :silly:..)
I'm also unable to relock the bootloader via fastboot, I get
FAILED (remote: root type is risk)
Any suggestions? Thanks!
I'm in the same boat, except that my bootloader is also locked.
Help please.
erecovery with firmware finder's dns will solve it in no time, and works every time.
galapagos said:
erecovery with firmware finder's dns will solve it in no time, and works every time.
Click to expand...
Click to collapse
Don't I need the correct OEM info on my phone to use that?
{
"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"
}
I don't know which Firmware erecovery would use
I'm stuck at "Getting Package Info failed", even if i try the changelog.xml from the directory where I got the update.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3196/g1699/v147280/f1/full/changelog.xml
galapagos said:
erecovery with firmware finder's dns will solve it in no time, and works every time.
Click to expand...
Click to collapse
I tried but this fails for me too
zenixa said:
I tried but this fails for me too
Click to expand...
Click to collapse
You did change the dns in your router to the one provided by FF, right?
Use dload method
galapagos said:
You did change the dns in your router to the one provided by FF, right?
Click to expand...
Click to collapse
yeah, the update gets detected and everything goes fine on hiSuite, it'll finish downloading and then when my phone restarts to recovery for it to install it'll fail. I've only tried it with one firmware though(the one that's already installed on the device, so that could be why it fails) but I only see one BLN-L24 in firmware finder.
zenixa said:
yeah, the update gets detected and everything goes fine on hiSuite, it'll finish downloading and then when my phone restarts to recovery for it to install it'll fail. I've only tried it with one firmware though(the one that's already installed on the device, so that could be why it fails) but I only see one BLN-L24 in firmware finder.
Click to expand...
Click to collapse
got it!
I managed to find more firmware via the mobile updater finder and was able to successfully flash one using the DNS method.
I'm not sure why the pc version don't show as many BLN-24's as the mobile version does, but I'm so glad it's fixed now.
Thanks everyone <3
I tried three different firmwares, even the one it had when I got it, still no luck
HiSuite is detecting the update and the install fails on the phone
Chest3r said:
I tried three different firmwares, even the one it had when I got it, still no luck
HiSuite is detecting the update and the install fails on the phone
Click to expand...
Click to collapse
What's your original firmware version?
BLN-L21C432B375
I even tried B360, no luck, did you flash via HiSuite or did you use the updater on the cellphone with the DNS method? Till now I've only tried HiSuite, because erecovery didn't find any packages with the DNS method.
I also checked and the firmware is installable for my imei, I'm kinda lost here
don't use hisuite. just change the dns and use the erecovery.
galapagos said:
don't use hisuite. just change the dns and use the erecovery.
Click to expand...
Click to collapse
Yea, i tried that, it says "Getting package information failed".
I created a Wlan network with the FF DNS Server, if i try HiSuite it finds updates, erecovery doesnt.
Please explain the process
zenixa said:
got it!
I managed to find more firmware via the mobile updater finder and was able to successfully flash one using the DNS method.
I'm not sure why the pc version don't show as many BLN-24's as the mobile version does, but I'm so glad it's fixed now.
Thanks everyone <3
Click to expand...
Click to collapse
Bro I am stuck with the same problem can you please elaborate the process ?
Android 11 Global ROM
WIFI:
https://rsdsecure-cloud.motorola.com/download/TB-J606F_S320029_210923_ROW.zip
LTE:
https://rsdsecure-cloud.motorola.com/download/TB-J606L_S320030_210923_ROW.zip
{
"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"
}
@qwer1335 I've changed the prefix of your thread from "Development" to "General" as the thread didn't qualify for the first one. Please review the sticked guidances of the responsible moderators' team prior to your next posting and do not change the prefix back! Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
Updated with LMSA with no issues, only be warned that everything is deleted and you start from scratch. I had my bootloader unlocked, this was kept. But I am unable to root it as I did with Android 10. Patching boot.img with Magisk and I get bootloop to fastboot after flashing it. Only way to continue as of now was to flash the boot.img that came with the new firmware.
Hallux_ said:
Updated with LMSA with no issues, only be warned that everything is deleted and you start from scratch. I had my bootloader unlocked, this was kept. But I am unable to root it as I did with Android 10. Patching boot.img with Magisk and I get bootloop to fastboot after flashing it. Only way to continue as of now was to flash the boot.img that came with the new firmware.
Click to expand...
Click to collapse
So may I ask if you bought your 606f from China or abroad?
Since mine is a Chinese one, everytime I flash 0805/0906 it ends with *system and hardware not compatible* error. (the same both BL locked and unlocked)
I wonder if this new ROW rom fixes this issue.
Thanks.
i tried but the link doesn't work
EDIT: i tried from rescue and smartaassistant, and i found the update
asukav said:
So may I ask if you bought your 606f from China or abroad?
Since mine is a Chinese one, everytime I flash 0805/0906 it ends with *system and hardware not compatible* error. (the same both BL locked and unlocked)
I wonder if this new ROW rom fixes this issue.
Thanks.
Click to expand...
Click to collapse
I have the global version.
Hallux_ said:
I have the global version.
Click to expand...
Click to collapse
Then that's not a problem.
Can you guide me how to unpack the img files? I tried several but none of those works correctly.
I just want to do some research on what kind of restrictions lenovo does to the rom files.
Thank you.
asukav said:
Then that's not a problem.
Can you guide me how to unpack the img files? I tried several but none of those works correctly.
I just want to do some research on what kind of restrictions lenovo does to the rom files.
Thank you.
Click to expand...
Click to collapse
Sorry, I am not sure if it is what you are looking for, but I downloaded the new ROM with LMSA and I do have all the IMG files in the download directory. I do not know if you can do the same not having the exact same tablet model.
asukav said:
So may I ask if you bought your 606f from China or abroad?
Since mine is a Chinese one, everytime I flash 0805/0906 it ends with *system and hardware not compatible* error. (the same both BL locked and unlocked)
I wonder if this new ROW rom fixes this issue.
Thanks.
Click to expand...
Click to collapse
i recently install this rom but have "system and hardware not compatible, can you intsall android 11 on chinese lenovo p11 tablet?
famicom9x said:
i recently install this rom but have "system and hardware not compatible, can you intsall android 11 on chinese lenovo p11 tablet?
Click to expand...
Click to collapse
Still a "NO". It's the same: "system and hardware not compatible".
So I flash back to 0520.
I do hope I could spare some time to unpack those imgs to have a check on some specific files next week.
Just be busy all the time with my work...
Engineers from Lenovo China give me no useful answers. I think I can only count on myself.
I tried update to 210923 via LMSA, but not boot.
Then I tried again with qpst 2.7.496, it boot up and get a minor update to 0925.
Still lost serial number.
Que??
Have a new ROM in https://mirrors.lolinet.com/firmware/lenovo/Tab_P11/TB-J606F/TB-J606F_S320109_211207_ROW.zip but after i flash with QPST 2.7.496 still "system and hardware not compatible". Need someone fix it.
tnt1212 said:
Have a new ROM in https://mirrors.lolinet.com/firmware/lenovo/Tab_P11/TB-J606F/TB-J606F_S320109_211207_ROW.zip but after i flash with QPST 2.7.496 still "system and hardware not compatible". Need someone fix it.
Click to expand...
Click to collapse
It's because your device is Region locked. Within this XDA there is a forum on how to region unlock ur device. You have to use QCN file to change it.
Mine won't update because of region lock and now it's working perfectly
Hey guys, do you know if we still have widevine L1 after updating this ROM with locked bootloader?
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.