General [Download] P11(TB-J606) Android 11 Global ROM - Lenovo P11

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?

Related

Still didn't get nougat...

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

Official sm-g930t TWRP missing?

Hello all,
My goal is to image my phone with TWRP(which I have used when I had a rooted EVO2,) I am not after root. My goal is to test different NON-ROOT backup programs and restore if something is missing. So I have to ask the experts here, I see NO official TWRP rom for sm-g930t, whats the deal?
Here is what I find at TWRP website for Samsung Galaxy S7 (Exynos) (herolte)
{
"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"
}
imgur.com/ABMYYc9
The alternative is the Chinese variant. Also why does it say herolte in the first place? This is not to be confused with the hero phone?
This concerns me as I find guides to install TWRP for the sm-g930t from places like androidinfotech.com/2017/03/root-samsung-galaxy-s7-t-mobile-sm-g930t-nougat.html and Youtube.com using ENG-Root-USA.zip as the TWRP rom.
Thanks in advance for any help,
XDAGuy
G930T is Snapdragon SoC which has a locked bootloader, you aren't getting TWRP onto it, it's not possible.
herolte is the codename for the Exynos SoC S7's, which is the SoC you need for TWRP.
Beanvee7 said:
G930T is Snapdragon SoC which has a locked bootloader, you aren't getting TWRP onto it, it's not possible.
herolte is the codename for the Exynos SoC S7's, which is the SoC you need for TWRP.
Click to expand...
Click to collapse
Thanks @Beanvee7. So am I able to image my emmc partitions with adb for my cloning purposes atleast? Can they ever be returned? And finally you are saying if I have G930T, I cannot install TWRP on it period (even with Odin)---then what are some tutorials and success for... trololol? And is this lock thx to T-Mobile?
Thanks,
XDAGuy
emmc partitions I believe fall under boot partitions, which are locked by the bootloader.
Yes I am saying the G930T cannot install TWRP on it period even with Odin.
Odin can only flash what the device permits, and a locked device won't permit boot modifications.
If you can find me a tutorial where they successfully flashed TWRP onto a G930T I'd like to see it.
The lock applies to all USA models, it's not specifically T-Mobile. It was likely AT&T and/or Verizon that forced the requirement onto Samsung.
Smaller carriers would be prevented from allowing an unlock method, because it could then be used on AT&T and Verizon models since they have the same SoC.
Beanvee7 said:
emmc partitions I believe fall under boot partitions, which are locked by the bootloader.
If you can find me a tutorial where they successfully flashed TWRP onto a G930T I'd like to see it.
Click to expand...
Click to collapse
I linked one in the first thread(without the protocol +www for anyones imagination,) they limit new posters on links. I also found one on you tube with people saying in comments worked on G930T, however cant find it since I cant search comments and its annoying.
androidinfotech.com/2017/03/root-samsung-galaxy-s7-t-mobile-sm-g930t-nougat.html
or
fastunlocker.in/root-samsung-s7-sm-g930t.html
Finally, whats this @ 1:49 youtube.com/watch?v=3yJY9RSpV0c, for custom OS? Cant change boot but can OS?
Those guides are both nonsense tbh, first one is full of errors without any photo or video, second one under the TWRP says 'we can't provide the files, find them yourself', so where's TWRP?
The video they show is also for a different model.
As for your youtube video, that's just standard recovery and download mode. All Samsung phones display the same warning, even models that can't actually flash custom firmware.
TWRP looks like this
Standard recovery looks like this
After some more digging, there is this:
https://forum.xda-developers.com/tmobile-galaxy-s7/development
https://forum.xda-developers.com/verizon-galaxy-s7/development
You still don't get full custom ROM's, but you can run some modded zips.
Beanvee7 said:
After some more digging, there is this:
https://forum.xda-developers.com/tmobile-galaxy-s7/development
https://forum.xda-developers.com/verizon-galaxy-s7/development
You still don't get full custom ROM's, but you can run some modded zips.
Click to expand...
Click to collapse
You da man, very much appreciated for your time. I checked out the piece by Kevin, looks like he spent alot of time on it. Thanks for helping, but again, I was just looking to get TWRP installed so I could image my phone and test non-root backup solutions. I do not want ROOT atm. From what I am gathering I cannot change the boot parition to put TWRP, correct? And via ADB I cannot image my phone? And if I could image my phone, I couldnt restore the images to my phone, correct?
Thanks again,
XDAGuy357

Question IMEI & Baseband are gone in latest firmware version

I rooted my Samsung device previously, but has since done a clean flash and locked the bootloader so it's back to how it originally was. But now, if I update my phone, the IMEI & baseband are gone. I discovered that clean flashing the firmware A125FXXU1BUG1 seems to fix the issue for me.
So my question is, is it possible to update my phone without loosing my IMEI and baseband? And is this an issue caused by Samsung or me rooting my phone?
The same thing for me, I rooted, then go back to stock like you did but can't update to the latest version A125FXXU1BUI3. I'm currently on version A125FXXU1BUF9.
Edit.
I tried multiple times and couldn't upgrade. I updated it from the first available firmware Android 10 to the latest Android 11 in my region (A125FXXU1BUI3 XTC) with no luck. I tried every existing firmware on my device without success in updating to the current version, and I'm still stuck on version A125FXXU1BUF9. A125FXXU1BUI3 is only 710 MB in size, but no dice. I believe we are to blame for rooting our phones.
No luck means invalid IMEI and invalid baseband.
The issue isn't because you rooted your phones. Since the update A125FXXU1BUG6 I have also experienced IMEI and Baseband errors and I've never rooted my phone. I think the updates have a bug in them or something. Same goes with the latest A125FXXU1BUI3 update. I thought the latest one would fix it but it didn't. Waiting to see if the November security update will fix it
These are fimware issues made by samsung, they are not happending because you rooted your phone or triped knox or other... It's a ordinary fimware bug I thought they would fix in BUI3 which relased after BUG6(where the issue started happending) I thought then someone would allready report that, I don't actualy know if samsung knows this is happending or they just don't care to fix it.
And it's like as if anything over BUF9 is good... it really isn't. Some people say thay get bootloops and other weired issues on GSIs with fimware over BUF9 version. I haven't tested that my self yet, so I'm going of others people words. I dindn't test it because when I first saw the IMEI issues I didn't care to test.
Anyway, going to send a modem.tar file which could fix the issues, haven't tested....
I've flashed the new A125FXXU1BUJ4 November security update and the bug is still there but I was able to flash this IMEI/Baseband repair file and it fixed it. I actually reported to samsung but their response was to visit a help center. I guess they don't know it a bug in their firmware. Just flash the file using Odin and add it in CP.
The fix was posted on this forum:
https://forum.xda-developers.com/t/sim-baseband-imei-errors-since-tuesday-17th.4322143/post-85875843
Allehandro said:
I've flashed the new A125FXXU1BUJ4 November security update and the bug is still there but I was able to flash this IMEI/Baseband repair file and it fixed it. I actually reported to samsung but their response was to visit a help center. I guess they don't know it a bug in their firmware. Just flash the file using Odin and add it in CP.
The fix was posted on this forum:
https://forum.xda-developers.com/t/sim-baseband-imei-errors-since-tuesday-17th.4322143/post-85875843
Click to expand...
Click to collapse
sorry i frgot to send it, anway you can find in that other post as you linked it. glad it worked. Sorry for inconvenience to anyone.
Thank you so much, if it wasn't for you guys until now I'm still waiting for Samsung to fix it.
I can't download this file and I had this bug any other solution?
{
"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"
}
Anyway I using this phone only for some games but without imei some games don't work
Forgot it I solved flashing Android 10 Baseband if someone has the same problem try to flash the last android 10 baseband this a palliative solution (If Samsung upgrades their binary to 2 I think the bug cannot be fixed)

moto g pure fastboot magisk_patched image error

i have a moto g pure from xfinity mobile i found a stock zip file using the lenovo rsa i then copied the boot image then ran it through the magisk app i then fast boot it and this is the error i get i did oem unlock in settings and also fastboot oem unlock it sends to phone then starts to write and this is the error can someone smarter please help
{
"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"
}
moderater sorry im new please foward to appropiate forum thank you
My guess is you've a driver problem.
Use the driver offered here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
motorola-global-portal.custhelp.com
jwoegerbauer said:
My guess is you've a driver problem.
Use the driver offered here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
motorola-global-portal.custhelp.com
Click to expand...
Click to collapse
not a driver problem its a failed verification on the stock patched.img through magisk diferent verifiction key for the two images
OK
So did you ever get it figured out? I have the moto g pure as well. I have it bootloader unlocked but have been unable to find a boot.img to try to use Magisk on. The stock file I tried to get from the Motorola tool keeps giving me an error saying the file failed to decompress....
Agent_Orange1488 said:
So did you ever get it figured out? I have the moto g pure as well. I have it bootloader unlocked but have been unable to find a boot.img to try to use Magisk on. The stock file I tried to get from the Motorola tool keeps giving me an error saying the file failed to decompress....
Click to expand...
Click to collapse
No I never did how did you get your bootloader unlocked?
Agent_Orange1488 said:
So did you ever get it figured out? I have the moto g pure as well. I have it bootloader unlocked but have been unable to find a boot.img to try to use Magisk on. The stock file I tried to get from the Motorola tool keeps giving me an error saying the file failed to decompress....
Click to expand...
Click to collapse
Newportswag74 said:
No I never did how did you get your bootloader unlocked?
Click to expand...
Click to collapse
There is your boot img
Newportswag74 said:
There is your boot img
Click to expand...
Click to collapse
Thanks a ton!!! Bootloader unlock was simple for me (T-Mobile). https://androidbiits.com/unlock-bootloader-motorola-moto-g-pure-xt2163-4-easily/
The guide at this link worked perfectly for me!! I will let you know how Magisk root goes
Agent_Orange1488 said:
Thanks a ton!!! Bootloader unlock was simple for me (T-Mobile). https://androidbiits.com/unlock-bootloader-motorola-moto-g-pure-xt2163-4-easily/
The guide at this link worked perfectly for me!! I will let you know how Magisk root goes
Click to expand...
Click to collapse
Really when I tried that at the Lenovo website it said my pure wasn't eligible
did patching that boot work?
i managed to patch the latest firmware with march security update, and root the stock rom, now i need to mess with gsis

Untouched Poco F2 Pro (SJKEUXM) Unknown baseband after latest update (13.0.8.0 SJKEUXM)

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.

Categories

Resources