Develop Bugs

0 IMEI after Pie on XT-1789-03 Sprint

I have lost IMEI number after flashing Pie. On my Sprint Moto Z2 Force. Signal bar has turned grey and IMEI is showing as zero.
Wifi is working
Bluetooth is working
Barcodes in bootloader mode is showing some different IMEI no.
Downgrade to Stock Oreo or Naugat
If I downgrade to stock Oreo then I lost all wifi, sim and Bluetooth. Also no baseband found in bootloader.
Will appreciate if someone can help.
Thanks in advance.

If you have already flashed Pie Rom (including bl、 baseband), you will not be able to return to Oreo

Hello.
I am trying to research the imei bricks on Sprint models after Verizon pie update. In short, everything we understand says this should not be happening, and yet it is.
Can you, for research purposes, describe the state of your device when you applied the update? Was it running full verizon firmware down to the bl, modem, and gpt? I may have an experimental fix but I need to gather more info about the bricks.
Also, it is impetative that you don't flash any further modems for my fix to have a good chance to work. Thanks.

Thanks for the message,
The device working fine, very super smooth and I can feel the difference.
The only think which is not working is cell phone and it's because of 0 IMEI number, currently I am on pie retail version (NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml) downloaded from mirrors lolinet com / firmware / Moto / Nash / retail
Pls let me know if you want more info.
Thanks in advance.

hqureshi said:
Thanks for the message,
The device working fine, very super smooth and I can feel the difference.
The only think which is not working is cell phone and it's because of 0 IMEI number, currently I am on pie retail version (NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml) downloaded from mirrors lolinet com / firmware / Moto / Nash / retail
Pls let me know if you want more info.
Thanks in advance.
Click to expand...
Click to collapse
What firmware did you flash from? Stock? Do you have an unlocked bootloader?
If yes to all the above, I can give you some experimental things to try.

Yes to all and bootloader is unlocked.
btw i have flashed firmware in this order
1. i flashed NASH_PPX29.159_19_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
then
2. XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and now on
3. NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml

That's not ideal (the additional flashes) but what I have is still worth a try and you have nothing to lose.
The first thing we need is to boot twrp on the device using fastboot (get the latest .img here and fastboot boot twrp.img it). Once in twrp, immediately reboot to "EDL."
https://dl.twrp.me/nash/
Get drivers for qualcomm 9008 mode device if needed (should show in Windows device manager under "ports"):
https://androidfilehost.com/?fid=11410963190603862036
Then get the nougat blankflash here:
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/blankflash_from_NDX26.183-15_17.zip
Extract and run the cmd inside. You may need to try a few times, on different usb ports. I heard usb 2.0 works best.
If it succeeeds, try flashing your stock firmware and see if imei is back.
Good luck. This is a real stretch but it just might work...
PS: This does have potential to completely brick your device. Please keep that in mind and weigh your options.

I have tried as per instruction but still getting the "baseband not found" status on all stock oreo & nougat firmwares. So when I flash Pie retail I get wifi and Bluetooth back with 0 IMEI status. so the situation is the same.
BTW I have read somewhere the 0 IMEI issue is related persist file/folder/. I may be able to share reference link of that discussion in a while. (Link of discussion)
Let me know if you want me to test anything else. Thanks again for your time. best

hqureshi said:
I have tried as per instruction but still getting the "baseband not found" status on all stock oreo & nougat firmwares. So when I flash Pie retail I get wifi and Bluetooth back with 0 IMEI status. so the situation is the same.
BTW I have read somewhere the 0 IMEI issue is related persist file/folder/. I may be able to share reference link of that discussion in a while. (Link of discussion)
Let me know if you want me to test anything else. Thanks again for your time. best
Click to expand...
Click to collapse
That's really odd. Sorry, I have nothing right now for you but will look into this as best I can.

Thanks, btw whenever i flash stock nougat i am getting verification failed error during flashing of bootloader.img

EDL
R-T-B said:
That's not ideal (the additional flashes) but what I have is still worth a try and you have nothing to lose.
The first thing we need is to boot twrp on the device using fastboot (get the latest .img here and fastboot boot twrp.img it). Once in twrp, immediately reboot to "EDL."
https://dl.twrp.me/nash/
Get drivers for qualcomm 9008 mode device if needed (should show in Windows device manager under "ports"):
https://androidfilehost.com/?fid=11410963190603862036
Then get the nougat blankflash here:
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/blankflash_from_NDX26.183-15_17.zip
Extract and run the cmd inside. You may need to try a few times, on different usb ports. I heard usb 2.0 works best.
If it succeeeds, try flashing your stock firmware and see if imei is back.
Good luck. This is a real stretch but it just might work...
PS: This does have potential to completely brick your device. Please keep that in mind and weigh your options.
Click to expand...
Click to collapse
I can see the qualcomm device in twrp on my device manager. how to i get to edl mode. there is no reboot edl option in twrp. do i command fastboot reboot edl when device in twrp screen? when i run the qboot blank-flash it says wating for device

Please use latest TWRP from here https://dl.twrp.me/nash/ load it using fastboot and the in TWRP click reboot and select EDL.
Let me know if you face any issue.

i'm on the same boat
no celluler, no IMEI
wifi and bluetooth working

Everyone keeps trying to flash pie firmware that isn't for their variant and this is the result, no baseband. Plus once you upgrade to a pie modem, you can't go back to an oreo modem. Maybe something will come along and remedy that, that's a big maybe too. The devs are trying to find a solution, but there just might not be one. You can't blankflash your way out of it, and if you're not careful you can brick your phone for real. Not 9008 brick, paperweight. Not trying to be an ass, just trying to warn others. If it isn't pie for your phone, don't flash it.

Blankflash doesn't work anyways.
Stand by we are working on another fix.

R-T-B said:
Blankflash doesn't work anyways.
Stand by we are working on another fix.
Click to expand...
Click to collapse
Let me know if you need this fastboot_nash_verizon_oem_vzw_user_9_PCX29.159-21_10d9a_release-keys-cid2_vzw.tar.gz. I have got it from @oslov a member of discord.
I have tried this in this sequence but still zero IMEI.
1. Nougat Blank flash
2. Flashed Stock Verizon Oreo and then staying in bootloader mode I flashed above Pie Update using Flash-All batch file.
Phone successfully booted with Verizon sim activation warning but IMEI was 0.
I thought I should update you guys.
Thanks

Oslov is my discord nick.
Confusing I know, lol.
Be careful with that file, we don't fully understand it yet. I gave it to you because, how much worse off can you be really?

R-T-B said:
Oslov is my discord nick.
Confusing I know, lol.
Be careful with that file, we don't fully understand it yet. I gave it to you because, how much worse off can you be really?
Click to expand...
Click to collapse
Lol. Wow!
Thanks again for doing this. Best

un1ocked said:
i'm on the same boat
no celluler, no IMEI
wifi and bluetooth working
Click to expand...
Click to collapse
Have restored IMEI # with the help of @oslov, We will share the solution in a while.

hqureshi said:
I have lost IMEI number after flashing Pie. On my Sprint Moto Z2 Force. Signal bar has turned grey and IMEI is showing as zero.
Wifi is working
Bluetooth is working
Barcodes in bootloader mode is showing some different IMEI no.
Downgrade to Stock Oreo or Naugat
If I downgrade to stock Oreo then I lost all wifi, sim and Bluetooth. Also no baseband found in bootloader.
Will appreciate if someone can help.
Thanks in advance.
Click to expand...
Click to collapse
I have resolved the 0 IMEI issue with the help of R-T-B, by doing undo Sim/network Unlock. changing CHMOD of id_00 to 0770
so now I am facing sim/network locked,
So whenever i unlock the sim/network lock i get 0 IMEI issue.
I will appreciate if someone now can help me to unlock SIM/network lock while keeping IMEI
I am currently on Retail pie with Sim/Network Locked. Phone Model is Sprint XT1789-03, dual sim enabled

Possible brick or semi brick

Well let me explain this question, i bought this device in aliexpress cause i live in mexico, so, my device version is the chinese (this for the network compatibility).
when the new software version roll out i downloaded in the realme web i tried to install it. But i was not able to, so i unlocked the bootloader to try some custom roms, i install the recovery TWRP , and then i downloaded the pixwel experience, before installing i checked and the realme ui update was released, so i tried to install it, but i couldn't cause i had the bootloader unlocked and the custom recovery.
Next thing i did was install the stock recovery, and then i locked again the bootloader, but now the cellphone dont start, it only shows the screen of "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it" .
The problem here is, the recovery dont start and the fastboot its locked and i can't bypass that.
I'm looking for a solution, but i want to know if anyone have solve this before or have any idea to do it. Thanks guys!

well it happened to me same the only way is to take it to realme service center or finde some one who have the oppo realme server to flash it like i did ifound a guy who have an official server the flash my device am from algeria

Update
Irvinukis said:
Well let me explain this question, i bought this device in aliexpress cause i live in mexico, so, my device version is the chinese (this for the network compatibility).
when the new software version roll out i downloaded in the realme web i tried to install it. But i was not able to, so i unlocked the bootloader to try some custom roms, i install the recovery TWRP , and then i downloaded the pixwel experience, before installing i checked and the realme ui update was released, so i tried to install it, but i couldn't cause i had the bootloader unlocked and the custom recovery.
Next thing i did was install the stock recovery, and then i locked again the bootloader, but now the cellphone dont start, it only shows the screen of "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it" .
The problem here is, the recovery dont start and the fastboot its locked and i can't bypass that.
I'm looking for a solution, but i want to know if anyone have solve this before or have any idea to do it. Thanks guys!
Click to expand...
Click to collapse
i´ve been "searching" (not too much to be honest) a way to flash my device, or even easier, to unlock the bootloader, once that is done, i will be able to do the next thing.
There are ways to "force" flashing modifying the hardware (i really don't want to that), other places suggest flashing a vbmeta.img, but i get back to the same, i need the bootloader
im actualy downloading UFI android tool, any update i will post it

Irvinukis said:
i´ve been "searching" (not too much to be honest) a way to flash my device, or even easier, to unlock the bootloader, once that is done, i will be able to do the next thing.
There are ways to "force" flashing modifying the hardware (i really don't want to that), other places suggest flashing a vbmeta.img, but i get back to the same, i need the bootloader
im actualy downloading UFI android tool, any update i will post it
Click to expand...
Click to collapse
well, my research and asking lead me to teh JIG usb to force the download mode, but i need to build it, does anyone have experience with this?

Firstly u need to flash twrp with adb and then use twrp to flash the rom. Then wipe and clean cache and you are done

eni_pog said:
Firstly u need to flash twrp with adb and then use twrp to flash the rom. Then wipe and clean cache and you are done
Click to expand...
Click to collapse
How can i do that with the bootloader blocked?
Can u explain me please?

The solution may be QFI and EMMC download tool, if unbrick the device i'll post a guide

i made a EDL cable that i'm gonna use to try, i don't even know if the device have that mode, i'm actually searching a micro usb to type c usb to try

Irvinukis said:
Well let me explain this question, i bought this device in aliexpress cause i live in mexico, so, my device version is the chinese (this for the network compatibility).
when the new software version roll out i downloaded in the realme web i tried to install it. But i was not able to, so i unlocked the bootloader to try some custom roms, i install the recovery TWRP , and then i downloaded the pixwel experience, before installing i checked and the realme ui update was released, so i tried to install it, but i couldn't cause i had the bootloader unlocked and the custom recovery.
Next thing i did was install the stock recovery, and then i locked again the bootloader, but now the cellphone dont start, it only shows the screen of "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it" .
The problem here is, the recovery dont start and the fastboot its locked and i can't bypass that.
I'm looking for a solution, but i want to know if anyone have solve this before or have any idea to do it. Thanks guys!
Click to expand...
Click to collapse
I think EDL mode flashing stock ROM is a good way, but is there compatible download tool or image? I have ever used Miflash to downgrade my bootloader locked Xiaomi 4c for unlocking bootloader in EDL mode (maybe "fasboot oem edl" ,"fastboot reboot-edl", or "fastboot reboot edl" command).
Unlocking the Mi4c Bootloader: https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
Miflash guide: https://xiaomi.eu/community/threads/miui-10-developer-rom-8-9-13-with-miflash.47542/

Did you get the solution same problem
Well let me explain this question, i bought this device in aliexpress cause i live in mexico, so, my device version is the chinese (this for the network compatibility).
when the new software version roll out i downloaded in the realme web i tried to install it. But i was not able to, so i unlocked the bootloader to try some custom roms, i install the recovery TWRP , and then i downloaded the pixwel experience, before installing i checked and the realme ui update was released, so i tried to install it, but i couldn't cause i had the bootloader unlocked and the custom recovery.
Next thing i did was install the stock recovery, and then i locked again the bootloader, but now the cellphone dont start, it only shows the screen of "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it" .
The problem here is, the recovery dont start and the fastboot its locked and i can't bypass that.
I'm looking for a solution, but i want to know if anyone have solve this before or have any idea to do it. Thanks guys!
did u get the solution bro

Not yet, i have some steps to do it, but now im facing the last step, the file don´t get recognized by the tool, this tool ask for a scatter file, and the one with QFIL, i need a xml firehose fle, and i havent found it

did u get the solution bro[/QUOTE]
What i got is this:
Emergency download: press vol + and vol - then connect it to the pc, the pc will recognize it as port 9008 com in the device manager of your pc, if yor phone reboots u have to disconnect the battery cause the battery forces the reboot of the EDL mode, maybe if you put the phone on EDL mode an then quickly flash would work with out tearing appart the device
Files: you need to install qualcomm drivers (https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/), download the .ofp file of your device (i get if from here https://oppostockrom.com/oppo-realme-x-rmx1901 ), then you need to download the tool you will use
here is where things are gonna get a bit harder
MSMDownload: this is the official tool, it came withe ofp file from the link i put before, the proble is you need a user and password, i haven't found where to get one official, its from oppo workers i guess
There is a cracked version, but don't recognizes the file
QFIL: its for qualcom devices (found it here https://androidmtk.com/download-qualcomm-flash-image-loader-qfil), this will let you flash every qualcomm device (or thats what they tell you), it shows the port, but ask for a xml file and a programer path (thing that i haven't found it yet)
Cracked MSMDownload: i found this https://www.techoxygen.com/msm-download-tool/ , https://romprovider.com/2020/02/flash-qualcomm-devices-using-msm-download-tools/, or this https://www.youtube.com/watch?v=0CKsEOfGGaQ
now, in my case the file its not recognized, it says incorrect scatter file, from here you can start diggin around, if you solve this please let me know

What i got is this:
Emergency download: press vol + and vol - then connect it to the pc said:
https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/),[/url] download the .ofp file of your device (i get if from here https://oppostockrom.com/oppo-realme-x-rmx1901 ), then you need to download the tool you will use
here is where things are gonna get a bit harder
MSMDownload: this is the official tool, it came withe ofp file from the link i put before, the proble is you need a user and password, i haven't found where to get one official, its from oppo workers i guess
There is a cracked version, but don't recognizes the file
QFIL: its for qualcom devices (found it here https://androidmtk.com/download-qualcomm-flash-image-loader-qfil), this will let you flash every qualcomm device (or thats what they tell you), it shows the port, but ask for a xml file and a programer path (thing that i haven't found it yet)
Cracked MSMDownload: i found this https://www.techoxygen.com/msm-download-tool/ , https://romprovider.com/2020/02/flash-qualcomm-devices-using-msm-download-tools/, or this
now, in my case the file its not recognized, it says incorrect scatter file, from here you can start diggin around, if you solve this please let me know
Click to expand...
Click to collapse
Hi man , did you try this method?

devilkar said:
Hi man , did you try this method?
Click to expand...
Click to collapse
yeah, i tried, but my bootloader its blocked

zaki789 said:
well it happened to me same the only way is to take it to realme service center or finde some one who have the oppo realme server to flash it like i did ifound a guy who have an official server the flash my device am from algeria
Click to expand...
Click to collapse
Hi bro i from algeria too can you tell where you flashed your phone, please adresse phone number any help, thank you

all about official firmware and where to find it

This wil be a list of firmware sources and a bit of explanation in different firmware versions and builds. This information has been gathered over the past few weeks, mainly by helping others to find the proper stock roms.
First of all, there seem to be multiple regions that have different firmware’s, and there seem to be different software channels per region or per region per provider. ( for instance vfeu vs reteu )
The phone model is XT2041-X where the X can stand for 1 to 4
The development name / moto name is called: Sofiar ( XT2041-1/3)
the development name for the US name is: Sofia ( xt2041-4 )
The easiest way to find the proper firmware would be via the Lenovo rescue and smart assistant ( LMSA)
you can download it from here: https://download.lenovo.com/consumer/mobiles/rescue_and_smart_v5.0.0.25_setup.exe
Since a few days support has been added to rescue the g8 power
you can download the current firmware for your device via the rescue page.
Manual selection of firmware sources:
So far, every source on the internet points to the lolinet mirror
see https://mirrors.lolinet.com/firmware/moto/sofiar/official/
US version: https://mirrors.lolinet.com/firmware/moto/sofia/official/
a 2nd source would be the moto updates tracker, but I expect that everything you find here Will appear on lolinet
US: https://t.me/s/MotoUpdatesTracker?q=#sofia
The rest of the world: https://t.me/s/MotoUpdatesTracker?q=#sofiar
so far I have not been able to find any other sources. I hope this helps a bit in downloading / finding the stock firmware for your phone.
If you find any other / better source, please let me know, I'll add it to this first post.

Thanks
I successfully updated mine and regained root.
I will post manual update guide later.
A side note: the following must be flashed in fastbootd (fastboot reboot fastbootd or adb reboot fastboot)
boot.img, recovery.img, vbmeta.img, super, dtbo.img

@mingkee Pls can you share manual update guide? THX

endva3 said:
@mingkee Pls can you share manual update guide? THX
Click to expand...
Click to collapse
There's a simple method using LMSA rescue method, but make sure you backup your phone because your phone will be wiped during the process.

Hi, I'm running into a little problem. I used the lolinet link to download the factory ROM for my Moto G Power (Best Buy unlocked, on Verizon). I downloaded the sofia VZW factory ROM first (thinking because I'm on Verizon). I used Magisk to patch the boot.img and fastbooted it. After reboot, I lost the touch screen and cell service -- could not unlock the phone. So I thought no big deal, I'll just reflash the unpatched boot.img from the sofia retus ROM this time. However, I still do not have touch screen. Does anyone have the factory boot.img for QPM30.80.50-1 that originally came with this G Power? Thanks in advance.

quangtran1 said:
Hi, I'm running into a little problem. I used the lolinet link to download the factory ROM for my Moto G Power (Best Buy unlocked, on Verizon). I downloaded the sofia VZW factory ROM first (thinking because I'm on Verizon). I used Magisk to patch the boot.img and fastbooted it. After reboot, I lost the touch screen and cell service -- could not unlock the phone. So I thought no big deal, I'll just reflash the unpatched boot.img from the sofia retus ROM this time. However, I still do not have touch screen. Does anyone have the factory boot.img for QPM30.80.50-1 that originally came with this G Power? Thanks in advance.
Click to expand...
Click to collapse
You may have patched unmatched build number.
Solution: flash full ROM
LMSA rescue is the simplest method but it will wipe the phone

Thanks! That was what I ended up doing.

Is it possible to change fw xt2041-3 (PAHF0004PL) to XT2041-3 (PAHF0006GB)? I'm on the PL version (andoid security January 2020) and the GB version is May 2020. If possible, the bootloader must be unlocked? Can it be changed via any tool (mototool) or via adb commands?

Anyone have the boot.img for QPMS30.80-51-3?
I cant download the latest May update from their server. Some reason the link to download expired a few days after. So if anyone has another link or can just hook it up with the boot.img please
I couldnt get it with the rescue app either it was a lower version.
EDIT
Found it here
https://forum.xda-developers.com/showpost.php?p=82865201&postcount=73

Some lessons learned
pjottrr said:
The easiest way to find the proper firmware would be via the Lenovo rescue and smart assistant ( LMSA)
you can download it from here: https://download.lenovo.com/consumer/mobiles/rescue_and_smart_v5.0.0.25_setup.exe
Since a few days support has been added to rescue the g8 power
you can download the current firmware for your device via the rescue page.
Click to expand...
Click to collapse
In my case, you in fact cannot exactly download the "current" firmware via the rescue page - the phone's updater app thinks QPM30.80-51-3 is the latest version, but the rescue app installs the newer QPM30.80-109. Both are 5/1/2020 security patch level, but the boot.img files are most certainly not interchangeable.
I ended up in a bootloop which I had to rescue the phone to escape. I'd advise anyone wanting to root this phone to just rescue it first.
Also it's essential that you install the Motorola Device Manager/USB drivers in addition to LRSA, otherwise LRSA will incorrectly insist your phone is not in fastboot flash mode if you have to resort to rescuing from fastboot mode.
Finally, the rescue process will not work from a Windows VM under KVM, whether you have the USB device redirected or shared with the host. You need Windows running on bare metal.
Hope this saves someone the hours of annoyance I just went through trying to unbrick the damn thing.

Can jump from a carrier Rom to a unlocked version? And if yes, what's the unlocked phone rom? Cause I only see carrier versions.

Mikael1013 said:
Can jump from a carrier Rom to a unlocked version? And if yes, what's the unlocked phone rom? Cause I only see carrier versions.
Click to expand...
Click to collapse
Switching from a carrier rom to an unlocked version won't SIM unlock a phone (at least not to my knowledge), if that's your objective. But if you're looking to switch the retail flavor rom, try RETUS, specifically XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.

rlrevell said:
In my case, you in fact cannot exactly download the "current" firmware via the rescue page - the phone's updater app thinks QPM30.80-51-3 is the latest version, but the rescue app installs the newer QPM30.80-109. Both are 5/1/2020 security patch level, but the boot.img files are most certainly not interchangeable.
I ended up in a bootloop which I had to rescue the phone to escape. I'd advise anyone wanting to root this phone to just rescue it first.
Also it's essential that you install the Motorola Device Manager/USB drivers in addition to LRSA, otherwise LRSA will incorrectly insist your phone is not in fastboot flash mode if you have to resort to rescuing from fastboot mode.
Finally, the rescue process will not work from a Windows VM under KVM, whether you have the USB device redirected or shared with the host. You need Windows running on bare metal.
Hope this saves someone the hours of annoyance I just went through trying to unbrick the damn thing.
Click to expand...
Click to collapse
Also a good word of advice before flashing a boot.bin
run the command
fastboot boot boot.bin
or whatever your boot.bin is called
Then you can test your patched file before patching it. Also even better once you get into Android you can open MAGISK and use direct install

TNS201 said:
Also a good word of advice before flashing a boot.bin
run the command
fastboot boot boot.bin
or whatever your boot.bin is called
Then you can test your patched file before patching it. Also even better once you get into Android you can open MAGISK and use direct install
Click to expand...
Click to collapse
I've never actually had this work on any device I've tried to root. Command not implemented or some such error was always the result. Does it work for you on this device?

The download link for the latest Google Fi firmware works again if anyone wants to grab it before it expires...again heh.
SOFIA_RETAIL_QPMS30.80-51-3

CodyF86 said:
The download link for the latest Google Fi firmware works again if anyone wants to grab it before it expires...again heh.
SOFIA_RETAIL_QPMS30.80-51-3
Click to expand...
Click to collapse
Do you have stock boot IMG by any chance? Thx in advance

freddienuxx said:
Do you have stock boot IMG by any chance? Thx in advance
Click to expand...
Click to collapse
sofia_80-51-3boot.img

CodyF86 said:
sofia_80-51-3boot.img
Click to expand...
Click to collapse
Thx man

rlrevell said:
I've never actually had this work on any device I've tried to root. Command not implemented or some such error was always the result. Does it work for you on this device?
Click to expand...
Click to collapse
yea when you are in bootloader with phone attached to the PC it should work
It worked on my pixel 2 xl and this phone

Does anybody have this file available? (Sorry for the spaces, I can't post a link...). The download link has expired.
t.me /motoupdatestracker/ 2752
filename: SOFIA_RETAIL_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
What's the difference between that and RETUS on lolinet? Is there any? Reason I'm asking is that I don't have any radios after that OTA (Google Fi) and flashing the boot.img from RETUS QPMS-30.80-51-5.

Sony Xperia XA1 - Bootloop after twrp misuse

Hello, i'm writing this post because i'm a noob on mobiles and i need some assistence in this scenario.
I have a xa1 that was stopped at home because it had terrible calibration problems. This year i remembered to root and flash this mobile, maybe it was the build that was having some compatibility issues.
For now i have successfully unlocked the bootloader but when doing an instructon installing the twrp program on the device, i may have done something wrong.
From what i understand, twrp is a backup/recovery user gui to make some actions easier.
i think i ****ed up and now the phone is on bootloop and i cant even go into recovery mode.
i did not move the twrp.img to the folder i was working on and still pressed enter on the "fastboot boot twrp.img" step.
I understand that i may have told the phone "hey use this img that doesnt exist" and now its standarized to launch from that img i told him? is that it?
I have adb and fastboot installed. I had them both recognizing the device, no problem until i did that step earlier, and now adb doesnt recognize the device anymore. I thought i could maybe get the standart boot.img(if that even exists) from some forum but this is getting waaay hairier that i thought.

Don't worry, it normal that the phone has bootloop after unlocked. You should flash stock rom again via Flashtool, for the firmware you could still download it from xperiafirm I guess, after reflash the stock rom your device will work just fine and you could download my twrp here which I build for XA1 Plus but a friend of mine have it working on XA1 Ultra just fine, if you need any more help on TWRP just DM me or ask in my thread

Hari Nguyen said:
Don't worry, it normal that the phone has bootloop after unlocked. You should flash stock rom again via Flashtool, for the firmware you could still download it from xperiafirm I guess, after reflash the stock rom your device will work just fine and you could download my twrp here which I build for XA1 Plus but a friend of mine have it working on XA1 Ultra just fine, if you need any more help on TWRP just DM me or ask in my thread
Click to expand...
Click to collapse
which firmware do i select and download? i bought the phone via amazon, from the uk, should i use the firmware of the language i want or the original from the fabric? does that even make a difference? im sorry, im a noob at android systems xD

Learn it at Xperia Firm thread, my country might vary from your (like network operator or what not) for that you need to do your own research to know which one to download, in my country all I need it go and download firmware that made for vietnam and done, it already come with multiple languages

H8314 firmware on an SO-05K model possible?

Question:
Is there any way to install a different firmware on my XZ2 Compact (SO-05K)? Preferably the one for H8314 as they are both single SIM.
Story:
Recently, I got my (used) XZ2 Compact and what I immediately tried to do was to unlock the bootloader so I could install LineageOS. What I didn't know was that the device was the Japanese model (SO-05K) so I nearly gave up on unlocking its bootloader and just live with it as it is. At least it was SIM unlocked so it wasn't totally useless.
Not until I found this post. So I followed that post and to my surprise, the bootloader indeed got unlocked.
Now, my problem is that I can't successfully install LineageOS 17.1 because the stock firmware is different from what was required in order to flash it. So I tried changing the firmware (flashtool and newflasher) but never had luck. Hence, the question.
Thank you!

Did you get any luck in installing h8314 on do-05k? When I tried using newflasher, I got "Error, didn't got signature OKAY reply! Got reply: FAILFailed to verify cms"

Not sure about Android images. But, I was able to flash Sailfish OS, a Linux based OS (https://forum.xda-developers.com/t/gnu-linux-sailfish-os-for-xperia-tama-devices.4008699/) on my unlocked SO-05K. It uses the firmware files for H8314 from Sony's Open Devices website. I guess both the devices (H8314 nad SO-05K) are the same, but with different model numbers hardcoded.
Could be that the flasher checks for a connected H8314, but finds no such device and fails. I experienced similar problem initially that the fastboot flasher script was looking for H8314, but was finding SO-05K and hence was failing. Modifying the script to look for SO-05K allowed me to use the script. In any case, I believe one could manually flash each file to the right partition using fastboot only. That said, I am no expert.

I've got a SO-05K with unlocked bootloader and I'd love to flash LineageOS or any other custom andriod rom but I'm not sure if its compatible and I'd hate to brick my device.
Does anyone have an idea if its possible?
Is there a program that will allow scan a rom and tell me to if it supports SO-05K?

I have same problem

Hi,
My device: Sony Xperia XZ2 Compact, version SO-05K, NTT DoCoMo, Android 10 > working well.
.
I tried to install LineageOS 17.1 on the Xperia XZ2c.
I followed the page https://wiki.lineageos.org/devices/xz2c/install
- Performed the basic requirements.
- The latest recovery file 'lineage-17.1-20210514-recovery-xz2c.img' has been installed.
Recovery installed in 'Active slot: a'.
- 'Factory reset', then 'Format data / factory reset' was done.
- Sideload package using: 'adb sideload copy-partitions-20210323_1922.zip'
Everything went well, but when installing the update 'lineage-17.1-20210514-nightly-xz2c-signed.zip' an error occurred and does not allow to proceed:
.
"Installing update ..."
"Step 1/2"
"Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)"
.
EDIT:
70%
[0127/031946.016998:ERROR:cached_file_descriptor.cc (89)] Failed to flush cached data: no space left on devive (28)
[0127/031946.017290:ERROR:extend_writer.cc(53)] utils:WriteA11(fd_, c_bytes + bytes_written,bytes_to_write) failed.
Leaving there, I tried official firmware SO-05K, FlashTool, Newflasher, but they all went wrong.
I also tried the Unofficial TWRP, and it gave an error: 'error: cannot load 'boot_a': No such file or directory´.
The error may be in the access to Slot-a, is it?
Right now I only have 'Lineage Recovery 17.1' in slot-a. The device locks on the Sony Logo, obviously.
That said, I am not an expert.
Someone can help me?
Sorry for the bad English.

anjomale said:
Hi,
My device: Sony Xperia XZ2 Compact, version SO-05K, NTT DoCoMo, Android 10 > working well.
.
I tried to install LineageOS 17.1 on the Xperia XZ2c.
I followed the page https://wiki.lineageos.org/devices/xz2c/install
- Performed the basic requirements.
- The latest recovery file 'lineage-17.1-20210514-recovery-xz2c.img' has been installed.
Recovery installed in 'Active slot: a'.
- 'Factory reset', then 'Format data / factory reset' was done.
- Sideload package using: 'adb sideload copy-partitions-20210323_1922.zip'
Everything went well, but when installing the update 'lineage-17.1-20210514-nightly-xz2c-signed.zip' an error occurred and does not allow to proceed:
.
"Installing update ..."
"Step 1/2"
"Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)"
.
EDIT:
70%
[0127/031946.016998:ERROR:cached_file_descriptor.cc (89)] Failed to flush cached data: no space left on devive (28)
[0127/031946.017290:ERROR:extend_writer.cc(53)] utils:WriteA11(fd_, c_bytes + bytes_written,bytes_to_write) failed.
Leaving there, I tried official firmware SO-05K, FlashTool, Newflasher, but they all went wrong.
I also tried the Unofficial TWRP, and it gave an error: 'error: cannot load 'boot_a': No such file or directory´.
The error may be in the access to Slot-a, is it?
Right now I only have 'Lineage Recovery 17.1' in slot-a. The device locks on the Sony Logo, obviously.
That said, I am not an expert.
Someone can help me?
Sorry for the bad English.
Click to expand...
Click to collapse
I'm no expert, but I had a similar issue with the Z3 D6683 Hong Kong variant to work with LineageOS for D6633.
I remember having to first install a stock D6633 firmware but I needed to remove fwinfo.xml so that FlashTool would allow flashing the firmware.
Perhaps a similar trick could work for the So-05K XZ2 Compact?
The link is to the D6683 story: https://forum.xda-developers.com/t/sony-xperia-z3-dual-d6683-flash-to-d6633-marshmallow.3404448/

lal883 said:
Not sure about Android images. But, I was able to flash Sailfish OS, a Linux based OS (https://forum.xda-developers.com/t/gnu-linux-sailfish-os-for-xperia-tama-devices.4008699/) on my unlocked SO-05K. [...]
Click to expand...
Click to collapse
wait... you installed sailfish on an xz2c? I thought these aren't supported?
I would almost prefer that over lineage os tbh... haven't checked your link yet, but I hope it contains proper instructions on how to do it -_-
anjomale said:
[...]
"Installing update ..."
"Step 1/2"
"Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)"
.
EDIT:
70%
[0127/031946.016998:ERROR:cached_file_descriptor.cc (89)] Failed to flush cached data: no space left on devive (28)
[0127/031946.017290:ERROR:extend_writer.cc(53)] utils:WriteA11(fd_, c_bytes + bytes_written,bytes_to_write) failed.
Leaving there, I tried official firmware SO-05K, FlashTool, Newflasher, but they all went wrong.
I also tried the Unofficial TWRP, and it gave an error: 'error: cannot load 'boot_a': No such file or directory´.
The error may be in the access to Slot-a, is it?
Right now I only have 'Lineage Recovery 17.1' in slot-a. The device locks on the Sony Logo, obviously.
[...]
Click to expand...
Click to collapse
I am having exactly the same issues atm! did you ever solve them? how did you make it to 70%? I never managed to get past the error 28..

I was also able to flash Sailfish, see https://forum.xda-developers.com/t/...ish-os-for-xperia-tama-devices.4008681/page-5
Sadly Sailfish doesn't quite support one essential app and also no japanese text so I went back again.
Still so using the wrong firmware on the device is definitely possible, question is now how to get it onto it...

Z0rnica said:
I was also able to flash Sailfish, see https://forum.xda-developers.com/t/...ish-os-for-xperia-tama-devices.4008681/page-5
Sadly Sailfish doesn't quite support one essential app and also no japanese text so I went back again.
Still so using the wrong firmware on the device is definitely possible, question is now how to get it onto it...
Click to expand...
Click to collapse
Sounds like it's worth downloading the H8314 firmware fileset from Sony with the Xperifirm client then delete the fwinfo.xml file before starting up the FlashTool client and building an .ftf package to flash to the device. Then your device will pretend it's an H8314 model assuming it boots up. From there you can follow the instructions on the LineageOS official guide.

yes, currently downloading flashtool to try to create the ftf package - simply flashing the firmware (as is) with new flasher did not work... the other thread also said, that flashing the ftf with flashtool wont work (https://forum.xda-developers.com/t/need-help-flashing-xz2-ftf-flash-fails.3873024/), so I am hoping that flashing the ftf with newflasher will work...
I am not quite sure which H8314 firmware to pick though, most seem to be branded. there is one designated "internal" and "storefront", I assume that is for over the shelf phones without contracts? there is also one called internal "commercial and journalists", I assume that contains the nsa spyware?

lal883 said:
Not sure about Android images. But, I was able to flash Sailfish OS, a Linux based OS (https://forum.xda-developers.com/t/gnu-linux-sailfish-os-for-xperia-tama-devices.4008699/) on my unlocked SO-05K. It uses the firmware files for H8314 from Sony's Open Devices website. I guess both the devices (H8314 nad SO-05K) are the same, but with different model numbers hardcoded.
Could be that the flasher checks for a connected H8314, but finds no such device and fails. I experienced similar problem initially that the fastboot flasher script was looking for H8314, but was finding SO-05K and hence was failing. Modifying the script to look for SO-05K allowed me to use the script. In any case, I believe one could manually flash each file to the right partition using fastboot only. That said, I am no expert.
Click to expand...
Click to collapse
Do you know if your H8314-sailfish flashed SO-O5K supports the same LTE bands as a "real" H8314? I'm having trouble getting trustworthy info on what bands the SO-O5K supports but some sources e.g. kimovil imply the Docomo version has fewer bands.

chaphal3 said:
Do you know if your H8314-sailfish flashed SO-O5K supports the same LTE bands as a "real" H8314? I'm having trouble getting trustworthy info on what bands the SO-O5K supports but some sources e.g. kimovil imply the Docomo version has fewer bands.
Click to expand...
Click to collapse
I cannot be certain about that. All I could confirm is that I havn't had trouble so far connecting to 4G network of my operator (not Docomo).

Does anyone know if you can downgrade on the SO-05K running Android 10 to the presumably Docomo Android 9 firmware on xperifirm, without breaking anything?4
I've flashed H8314 from 10 back to 9 before with newsflasher, I just need to know if I can do the same thing with Docomo firmware on SO-05K...

Hi guys, I'm planning to buy a so-05k to make a comparison with the old so-02k (xz1c) but I'm wondering if I can put the "global" firmware or not and if there is a working guide to unlock the LTE bands
Thanks for the clarification.

I've kept trying to flash global firmware to no avail, even modifying the source code of newflasher to stop it from returning after facing any error just results in another error:
Code:
Error, didn't got flash OKAY reply! Got reply: FAILCommand not authenticated
This error isn't actually part of newflasher and I'm assuming is from the phone itself.
I've also tried mix-matching the files from the Japanese and the Global roms, because at this point I don't really care if the phone bricks itself lol. But yeah, still no luck, either it just flashes as the regular Japanese firmware with no noticeable changes, or it just straight up fails.
Very disappointing!
The closest thing I have achieved is installing a treble ROM on the device, however the camera is non-functioning which is a dealbreaker for me.

drychemical said:
I've kept trying to flash global firmware to no avail, even modifying the source code of newflasher to stop it from returning after facing any error just results in another error:
Code:
Error, didn't got flash OKAY reply! Got reply: FAILCommand not authenticated
This error isn't actually part of newflasher and I'm assuming is from the phone itself.
I've also tried mix-matching the files from the Japanese and the Global roms, because at this point I don't really care if the phone bricks itself lol. But yeah, still no luck, either it just flashes as the regular Japanese firmware with no noticeable changes, or it just straight up fails.
Very disappointing!
The closest thing I have achieved is installing a treble ROM on the device, however the camera is non-functioning which is a dealbreaker for me.
Click to expand...
Click to collapse
Hi, what do you mean with a treble rom ?

bob1791 said:
Hi, what do you mean with a treble rom ?
Click to expand...
Click to collapse
Treble ROMs are ROMs that can work on any device shipped with Android 8.0 or later, to keep the explanation simple.
You can see them all here: https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/

drychemical said:
Treble ROMs are ROMs that can work on any device shipped with Android 8.0 or later, to keep the explanation simple.
You can see them all here: https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
Click to expand...
Click to collapse
Oh right... So you put and android rom on SO-05K and it worked well ?

bob1791 said:
Oh right... So you put and android rom on SO-05K and it worked well ?
Click to expand...
Click to collapse
Yep, apart from the camera, from my brief test everything worked as it should.