[ROM][OFFICIAL][RACER]Lineage OS 17.1

[Heat84]

When I go to my phone status IMS is not registered. And when I get a call or receive a call the phone disables data and says it using 2g for voice. When the call ends it goes back to LTE data and Voice. Either the phone is messed up or something wrong with the sim or LOS 20 is severely messed up. I ordered a new Sim from Ting to see what happens.

I have Timg. I don't know anything about IMS. I didn't know about it until you mentioned it. Someone else will have to help you with that.

 

[Heat84]

So I just upgraded to 20. I think it was the smoothest LineageOS upgrade ever.

1. Bluetooth connects automatically(and instantly) everytime now instead of 1% of the time.

2. 5G still crashes the phone.

3. The phone still makes 1 call successfully, then immediately hangs up on all subsequent attempts until I reboot.

4. On the screen you get to after you reboot after the battery dies, the battery level stays stuck at 0%, but after waiting 10 or 15 minutes and rebooting, the battery level was at 42%. I had a similar issue before I upgraded: Where the battery level was stuck at 0% in 20, it was it wasn't stuck at 0% in 19.1, but it was 5 or 10% behind what the battery level was after you booted back
into the OS. Why aren't the two in sync?

 

[SyberHexen]

So I just upgraded to 20. I think it was the smoothest LineageOS upgrade ever.

1. Bluetooth connects automatically(and instantly) everytime now instead of 1% of the time.

2. 5G still crashes the phone.

3. The phone still makes 1 call successfully, then immediately hangs up on all subsequent attempts until I reboot.

4. On the screen you get to after you reboot after the battery dies, the battery level stays stuck at 0%, but after waiting 10 or 15 minutes and rebooting, the battery level was at 42%. I had a similar issue before I upgraded: Where the battery level was stuck at 0% in 20, it was it wasn't stuck at 0% in 19.1, but it was 5 or 10% behind what the battery level was after you booted back
into the OS. Why aren't the two in sync?

Can I ask what stock firmware tag you have installed or the last time you restock?

Please send fastboot getvar all but omit your imei

 

[Heat84]

Can I ask what stock firmware tag you have installed or the last time you restock?

Where can I get that information?

Please send fastboot getvar all but omit your imei

See attached file.

Why did you want me to omit my IMEI? Its not there anyway. At the end of the log you see: getvar:all failed (unknown status code). Do you know what that's about? Maybe thats why I don't see the IMEI. Hopefully the information you're looking for isn't also missing.

By the way, I ran the command a few times and it had the same result. Do you know why I had to unplug and replug my phone into the USB port everytime I ran the command or else the command would output no data?

Also, I had to switch USB ports to get Fastboot to work but ADB worked in the first port. Both ports(the 2 ports on the front of the computer) are the same USB type.

 

[SyberHexen]

Where can I get that information?

See attached file.

Why did you want me to omit my IMEI? Its not there anyway. At the end of the log you see: getvar:all failed (unknown status code). Do you know what that's about? Maybe thats why I don't see the IMEI. Hopefully the information you're looking for isn't also missing.

By the way, I ran the command a few times and it had the same result. Do you know why I had to unplug and replug my phone into the USB port everytime I ran the command or else the command would output no data?

Also, I had to switch USB ports to get Fastboot to work but ADB worked in the first port. Both ports(the 2 ports on the front of the computer) are the same USB type.

From bootloader screen with Android guy.
fastboot getvar all

It's going to have firmware information and other identifiers

 

[Heat84]

From bootloader screen with Android guy.
fastboot getvar all

It's going to have firmware information and other identifiers

See attached picture.

Why are you wanting me to do getvar again?

 

[SyberHexen]

See attached picture.

Why are you wanting me to do getvar again?

Well this isn't the full information i wanted but was enough to determine needed information.
Your bootloader / firmware is 2yrs out of date from the final android 11 official firmware from Motorola.
MBM Version: MBM-3.0-racer_retail-d0a492fa0b-200825
where 200825 is the date 2020-08-25 (Android 10 firmware?)

From the last stock ota for your specific device you should be on this:
BUILD REQUEST INFO: SW Version: racer_retail-user 11 RPDS31.Q4U-39-26-14-13 17601e release-keysM7250_HI20_06.18.02.74.05R Modem Version: M7250_HI20_06.18.02.74.05R FSG Version: FSG-7250-06.68.01 MBM Version: MBM-3.0-racer_retail-b1aecf973-220729

I'm actually surprised any roms even boot at this point considering the major changes moto rolled out from then to final.

Your options are:
1) Use Motorola RSA to restock (which erases userdata) then preform a fresh installation of LineageOS following the wiki.
2) Use provided link below to flash just the device firmware from the bootloader screen with pc fastboot. (this will flash bootloader, modem, fsg, bluetooth and dsp images to both a/b slots without erasing or disturbing current installation.

Firmware Only zip: Download

**Notes**
1) Current Stable and updated Roms will not work correctly if you don't update firmware.
2) Older unsupported roms like lineage-17.1/18.1 era will no longer boot after updating firmware
3) You will not be able to downgrade device firmware after updating.

 

[Heat84]

Well this isn't the full information i wanted but was enough to determine needed information.
Your bootloader / firmware is 2yrs out of date from the final android 11 official firmware from Motorola.
MBM Version: MBM-3.0-racer_retail-d0a492fa0b-200825
where 200825 is the date 2020-08-25 (Android 10 firmware?)

From the last stock ota for your specific device you should be on this:
BUILD REQUEST INFO: SW Version: racer_retail-user 11 RPDS31.Q4U-39-26-14-13 17601e release-keysM7250_HI20_06.18.02.74.05R Modem Version: M7250_HI20_06.18.02.74.05R FSG Version: FSG-7250-06.68.01 MBM Version: MBM-3.0-racer_retail-b1aecf973-220729

I'm actually surprised any roms even boot at this point considering the major changes moto rolled out from then to final.

Your options are:
1) Use Motorola RSA to restock (which erases userdata) then preform a fresh installation of LineageOS following the wiki.
2) Use provided link below to flash just the device firmware from the bootloader screen with pc fastboot. (this will flash bootloader, modem, fsg, bluetooth and dsp images to both a/b slots without erasing or disturbing current installation.

Firmware Only zip: Download

**Notes**
1) Current Stable and updated Roms will not work correctly if you don't update firmware.
2) Older unsupported roms like lineage-17.1/18.1 era will no longer boot after updating firmware
3) You will not be able to downgrade device firmware after updating.

You haven't told me which problem you're helping me fix(none of which are worth doing a factory reset to fix). I was about to ask you if you were helping me or just collecting beta testing data.

What missing information did you want?

 

[SyberHexen]

Please re-read my reply carefully.

Your modem / firmware is so outdated that it's not compatible.

See solution 2 to avoid having to factory reset.

Should at the very lease solve the battery data and device restarting.

 

[Heat84]

Please re-read my reply carefully.

Your modem / firmware is so outdated that it's not compatible.

See solution 2 to avoid having to factory reset.

Should at the very lease solve the battery data and device restarting.

Oh, ok. I see.

Also, maybe I should've mentioned that my phone is rooted and the bootloader unlocked. Maybe that explains the incomplete getvar output? And other things?

 

[SyberHexen]

No, root / bootloader unlock should have no adverse results by itself.

most issues are likely related to not keeping device firmware up to date.

fastboot looked like you got it from recovery / fastbootd rather than bootloader mode.

 

[Heat84]

Please re-read my reply carefully.

Your modem / firmware is so outdated that it's not compatible.

See solution 2 to avoid having to factory reset.

Should at the very lease solve the battery data and device restarting.

Oh, ok. I see.

Also, maybe I should've mentioned that my phone is rooted and the bootloader unlocked. Maybe that explains the incomplete getvar output? And other things

No, root / bootloader unlock should have no adverse results by itself.

most issues are likely related to not keeping device firmware up to date.

fastboot looked like you got it from recovery / fastbootd rather than bootloader mode.

I did getvar in bootloader mode . I didn't realize you can do a fastboot command in bootloader mode. I haven't done the firmware fix yet.

 

[Heat84]

Please re-read my reply carefully.

Your modem / firmware is so outdated that it's not compatible.

See solution 2 to avoid having to factory reset.

Should at the very lease solve the battery data and device restarting.

How do I flash the firmware? Flashing the zip file doesn't work. I guess I'm supposed to extract the zip file and flash everything separately? Or execute the bach file that's inside the zip file somehow?

 

[SyberHexen]

Extract zip.

Run bat file assuming you're on windows with fastboot binary or execute commands inside by hand.

 

[Heat84]

Extract zip.

Run bat file assuming you're on windows with fastboot binary or execute commands inside by hand.

I ran the batch file and the flash was successful except for radio.img. The error message is: FAILED <remote: No such file or directory>.

 

[SyberHexen]

I ran the batch file and the flash was successful except for radio.img. The error message is: FAILED <remote: No such file or directory>.

hmm i checked for typo and didn't see any but I've extracted radio.img to respective partitions.

FW_ONLY_MODEM-RACER_RPDS31.Q4U-39-26-14-13.zip

drive.google.com

 

[Heat84]

hmm i checked for typo and didn't see any but I've extracted radio.img to respective partitions.

FW_ONLY_MODEM-RACER_RPDS31.Q4U-39-26-14-13.zip

drive.google.com

The phone is bricked. I don't know what happened. It rebooted into the OS just fine after I did the flash. But I couldn't tell if the flash took because the window closed when it was finished and it wouldn't flash again after I put the pause command at the end of the batch file(so the window wouldn't close). I did that when I flashed the first zip you gave me but I forgot to do it this time. I wanted to reboot the phone into the bootloader screen to see what it said and to do getvar all,, but it never got there. ADB isn't seeing the phone.

I'm not worried about the data since did a thorough backup before flashing the first zip file. I hope this isn't the type of brick that's unrecoverable.

 

[Heat84]

I downloaded this and the instructions told me to install a Quallcomm or MTK driver. I installed this. My phone now appears in Device Manager as an unknown device with a yellow exclamation point(which disappears when I unplug the phone) with the error message: Windows has stopped this device because it has reported problems. (Code 43). And that's as far as I've gotten.

I read something about shorting 2 pins together to put it in EDL mode: https://android.stackexchange.com/questions/221973/enter-edl-mode-in-motorola-devices

 

[SyberHexen]

The phone is bricked. I don't know what happened. It rebooted into the OS just fine after I did the flash. But I couldn't tell if the flash took because the window closed when it was finished and it wouldn't flash again after I put the pause command at the end of the batch file(so the window wouldn't close). I did that when I flashed the first zip you gave me but I forgot to do it this time. I wanted to reboot the phone into the bootloader screen to see what it said and to do getvar all,, but it never got there. ADB isn't seeing the phone.

I'm not worried about the data since did a thorough backup before flashing the first zip file. I hope this isn't the type of brick that's unrecoverable.

This is certainly odd, by chance did you still have lineage 20 installed or did u return to a older version?

When I return from work I'll put together a blankflash / edl reply.

 

[Heat84]

This is certainly odd, by chance did you still have lineage 20 installed or did u return to a older version?

When I return from work I'll put together a blankflash / edl reply.

I still have 20 installed.