Problem
I am running lineage nightlies on my Moto G 2015 (XT1541 with 2GB) since several month. Since some weeks i get "Unknown baseband" if i flash a current nightly.
Question
Is that a known issue? How can i workaround that?
Should i flash back to the latest Factory Firmware Images (from here: https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639) and then try reinstalling Lineage?
dddufte said:
Problem
I am running lineage nightlies on my Moto G 2015 (XT1541 with 2GB) since several month. Since some weeks i get "Unknown baseband" if i flash a current nightly.
Question
Is that a known issue? How can i workaround that?
Should i flash back to the latest Factory Firmware Images (from here: https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639) and then try reinstalling Lineage?
Click to expand...
Click to collapse
You can reflash the radio firmware, that should fix the unknown baseband error.Here is the link to the guide, it's in the FAQ:
How to flash Radio Firmware only?
Use the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
Broadcasted from Zeta Reticuli
Gravemind2015 said:
You can reflash the radio firmware, that should fix the unknown baseband error.Here is the link to the guide, it's in the FAQ:
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Let's see if i understood:
- Download & extract firmware for XT1541 here https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
- Install fastbook on my linux host ( i would prefer using my package mananger pacman)
- Reboot phone to Bootloader mode
- Execute the following fastbook commands
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1*
fastboot erase modemst2*
fastboot flash fsg fsg.mbn
- Reboot phone
I hope thats correct so far.
As i am interested: why is that baseband now outdated or not longer supported for current lineage nightlies? And how can i be sure that the ones contained in the firmware archive are newer?
dddufte said:
Let's see if i understood:
- Download & extract firmware for XT1541 here https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
- Install fastbook on my linux host ( i would prefer using my package mananger pacman)
- Reboot phone to Bootloader mode
- Execute the following fastbook commands
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1*
fastboot erase modemst2*
fastboot flash fsg fsg.mbn
- Reboot phone
I hope thats correct so far.
As i am interested: why is that baseband now outdated or not longer supported for current lineage nightlies? And how can i be sure that the ones contained in the firmware archive are newer?
Click to expand...
Click to collapse
Sorry, there was a typo. Instead of modemst1*, it would be modemst1, same for modemst2
So the resulting set of commands would be:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
.
As for the rest of the procedure, it's fine, I am a mint and arch user
Maybe the firmware isn't outdated but 'corrupted' in some way. Newer firmware doesn't always include core-level changes, so there is a chance that the firmware being flashed is the same version. The bootloader screen does show some info, but I'm not sure
Broadcasted from Zeta Reticuli
Related
Someone can help me downgrading my MOTO G with unlocked bootloader from GPE to stock 4.3.
I've been trying but I get "Image is too large" when I try to flash "system.img".
I want to downgrade to stock 4.3 Claro Argentina firmware.
Please, I really need your help!
cocoralladoo said:
Someone can help me downgrading my MOTO G with unlocked bootloader from GPE to stock 4.3.
I've been trying but I get "Image is too large" when I try to flash "system.img".
I want to downgrade to stock 4.3 Claro Argentina firmware.
Please, I really need your help!
Click to expand...
Click to collapse
Could be two things:
1. You may need to flash gpt.bin from 4.3 (included in official 4.3 download) as this will create a new correctly sized partition table.
2. Make sure you use motorola fastboot to flash (known as mfastboot) and not the Google fastboot.
Not a problem. Download http://sbf.droid-developers.org/download.php?device=14&file=124
And follow:
Code:
fastboot flash partition gpt.bin #if this fails, ignore it and carry on
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I have same problem too...any firmware I flash I get those " image is too big " errors and when I restart I am stuck at bootloader? any ideas?
gd91 said:
I have same problem too...any firmware I flash I get those " image is too big " errors and when I restart I am stuck at bootloader? any ideas?
Click to expand...
Click to collapse
Unfortunately i'm in the same boat, stuck at boot. Flashing different zips doenst seem to help. I think the partition has changed since the 4.4.4 OTA from 4.4.2 on the GPE. It's impossible to flash a different rom at the moment. Hopefully there will be a fix soon.
Yes ...I read the same thing in several places...it has to do something with that gpe firmwares partition.....anyone have any idea how to fix this please?
same problem here. I was able to fix my phone partially with
1, factory reset in recovery (twrp)
2, adb Cyanogen rom
3, fixing reception with
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
using gpe 4,4 fsg
Can you explain that in "noob language " please ? ...did you managed to flash official firmware after that?
Is fastboot mode available? If yes then you could just either 'dd' them or flash via fastboot, starting with sys partition. Don't touch the efs.
Hey,
i had found a solution for this in the moto 4g forum:
Quote:
Originally Posted by swicago
I just update via CM downloader and it update fine, however again my Radios are gone.
I tried to following to recover them, but to no avail
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
I am going to try a full wipe and install
EDIT: After doing full wipe and fresh install, my radios were still gone.
Had to run the above fastboot commands after fresh install..... Would be nice if we didn't need to do this each time on a new version.
Click to expand...
Click to collapse
Can anybody help me with finding those "NON-HLOS.bin" " fsg.mbn" files ? Im am Noob.
Thanks!!
Search for radio firmware for your device model.
_that said:
Search for radio firmware for your device model.
Click to expand...
Click to collapse
Perfect thanks! i take "Lollipop Radio Firmware:"?
E: Ok worked thanks a lot!
I was long time at MM sources.
Yesterday, Luis Gonzales created Resurrection Remix 5.8.5 working on Nougat baseband.
https://forum.xda-developers.com/mo...mix-v5-8-3-t3637204/post74686456#post74686456
So I updated my MXS to last N: 25.200-15-3
Before flashing custom I made DD backup of all needed partitions. I didn't try it but I think they are safe.
All can be flashed with fastboot.
System, boot, recovery with twrp too(flash from image).
All without root.
Kernel(boot) is untouched - without root - extracted from supersu backup.
https://mega.nz/#F!814XxZQK!g_INQT-O8ClpNttPc-wg6w
Flashing method:
fastboot oem fb_mode_set
fastboot flash logo logo.bin (unlocked BL warning!!!)
fastboot flash boot boot.img (rename downloaded file)
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Only for phones with unlocked BL and N version of BL & gpt.
Fastboot should sparse system.img itself.
Modems only(MM&N):
https://mega.nz/#F!FlxxUZxQ!M9kqWei99LXatwc4LgJORw
Mirror and instructions with comments - post #25
https://forum.xda-developers.com/showpost.php?p=74993383&postcount=25
MM recovery tool post #28
https://forum.xda-developers.com/showpost.php?p=75001459&postcount=28
Big thanks to @Prazaar
valerio32 said:
Modem is EU?
Click to expand...
Click to collapse
"Stock xt 1572, RetEu, 7.0 DDumped files."
valerio32 said:
you can do the ota updates and the recovery is original or is twrp?
---------- Post added at 03:34 PM ---------- Previous post was at 03:16 PM ----------
is normal "Invalid sparse file format at header magi"?
:crying::crying::crying::crying:
Click to expand...
Click to collapse
I don't understand. Upload screenshots somewhere.
valerio32 said:
the phone works, but how can I block the bootloader?
thank you
:crying::crying::crying::crying:
Click to expand...
Click to collapse
You can't untill will be flashable original stock for fastboot.
The same version or upper.
OTA - I don't think will be any more. But If you have last BL version shouldn't be any problems.
Btw
Did you flashed all partitions I uploaded? Only modem, fsg?
CAN NOT.
Hi,brother.could you please backup the bootloader file?
zi_mo said:
Hi,brother.could you please backup the bootloader file?
Click to expand...
Click to collapse
Only with flashfire app(rpm, sbl1, aboot, utags).
Flashfire says - restoring is most dangerous.
Thanks for replying.
My friend has a broken xs_EU with blocked BL by flashing stock_7.0BR,I thought that it would be rescued by flashing you files with gpt of the ota_patches if we got the file bl.
so, we must wait for the stock_7.0EU.
Will this work if I flash these files on my recently debricked (from downgrade) XS on MM 6.01?
Bootloader is still unlocked from the initial install of a custom ROM. But then I bricked it after downgrading from N to stock MM and installing OTA updates.
So just flash these files in fastboot and it should be on Nougat again unbricked?
I don't know.
There isn't bootloader & gpt into these files.
If your BL & gpt are Nougat you can flash it and later install ota updates @Murugan78
BL and GPT should still be N after the downgrade no? It went from MM to N with OTA when I bought it. Last month I installed Lineage ROM but decided to go stock again (and got bricked due to the N bootloader and gpt?). I get the prevalidation error when flashing BL and GPT from the official MM ROM so these must still be N if I am correct. This is my first moto device and I have done some custom things in the past with my S1, S2 and my OPO but never had these issues.
The sparsechunks are not necessary for trying to upgrade?
BL, gpt should be N. @Murugan78
And I can flash the system.img as 1 file instead of all the chunks?
Yes
fastboot flash system system.img
Flashed the files and so far so good! Got an OTA update without problems. Tomorrow I'm gonna test if my SIM works and maybe remove the unlocked bootloader message.
Thanks a LOT!
dzidexx said:
I was long time at MM sources.
Yesterday, Luis Gonzales created Resurrection Remix 5.8.5 working on Nougat baseband.
https://forum.xda-developers.com/mo...mix-v5-8-3-t3637204/post74686456#post74686456
So I updated my MXS to last N: 25.200-15-3
Before flashing custom I made DD backup of all needed partitions. I didn't try it but I think they are safe.
All can be flashed with fastboot.
System, boot, recovery with twrp too(flash from image).
All without root.
Kernel(boot) is untouched - without root - extracted from supersu backup.
https://mega.nz/#F!814XxZQK!g_INQT-O8ClpNttPc-wg6w
Flashing method:
fastboot oem fb_mode_set
fastboot flash logo logo.bin (unlocked BL warning!!!)
fastboot flash boot boot.img (rename downloaded file)
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Only for phones with unlocked BL and N version of BL & gpt.
Fastboot should sparse system.img itself.
Modems only(MM&N):
https://mega.nz/#F!FlxxUZxQ!M9kqWei99LXatwc4LgJORw
Click to expand...
Click to collapse
If i flash all with fastboot, i turn back my phone to the lastest N stock version.
I guess that it format internal storage too.
thi3um said:
If i flash all with fastboot, i turn back my phone to the lastest N stock version.
I guess that it format internal storage too.
Click to expand...
Click to collapse
This will format:
fastboot erase cache
fastboot erase userdata
You need it if you was on another version - 6.x or 7.1.2.
mirror online: https://dl.prazaar.de/?dir=Android/Motorola/XT1572/Dumped_Files
edit: The gpt.bin can be easily pulled from an OTA file
and the single bootloader files in: Blur_Version.24.231.13.clark_reteu.reteu.en.EU.zip:
tz.mbn, sdi.mbn, sbl1.mbn, pmic.mbn, rpm.mbn, hyp.mbn, fsg.mbn (but it "about.mbn" is missing)
I working on a Recovery Tool for Moto X Style (EU) XT1572 from 7.0 back to 6.0.1 with working OTAs
No other factory img is needed anymore. you want to be up to date? only OTAs needet for this
bootloader after this up to date!
The Recovery Tool bring you up to 6.0.1 without restriction.
https://dl.prazaar.de/?dir=Android/Motorola/XT1572/Factory/Recovery-Tool / for news prazaar.de
Just a question, I already have my xt 1572 reteu with the build version NPHS 25.200-15-3 like this dumped files, but I miss the October update, can I just flash recovery and boot.img from the dumped files in order to install the security patch? Thanks!!
I am trying to lock the bootloader while restoring all the stock images.
These are the commands I used:
fastboot devices
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
"fastboot flash partition gpt.bin" failed giving me "preflash validation failed".
After some research I found out that it was because I was trying to flash older firmware, and downgrading of firmware wasn't possible.
So, what's the solution here? How do I lock the bootloader and restore the stock images and firmware, and downgrade properly?
I was previously on Lineage OS Nougat 7.1.2.
I downloaded the correct stock images from https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639.
Specifically XT1541_OSPREY_RETEU_2GB_6.0.1_MPIS24.107-55-2-5_cid7.
I'm afraid you'll have to wait till a newer stock firmware is released. The bootloader cannot be locked if the system is not 100% stock.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
I'm afraid you'll have to wait till a newer stock firmware is released. The bootloader cannot be locked if the system is not 100% stock.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I had Nougat 7.1.2 with Lineage OS. I don't think Motorola is ever going to update the firmware of the Moto G 2015 to anything above 6.0.1. Does that mean that there is nothing I can do?
Is there any other way I can downgrade and lock?
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
"I get a 'Preflash validation' error when flashing a Firmware Image
The Firmware Image you are trying to flash is too old. You can only flash a firmware image that matches, or is newer than the most recent system version you have had on your phone. However the former scenario can also sometimes return the error. In which case, your options are to wait for an even newer firmware image or unlock Bootloader and flash a ROM zip."
Can anyone explain the parts in bold? I have an unlocked bootloader. If I flash a ROM zip will it downgrade? Can I flash the stock images and lock afterwards?
nomuzephyr said:
I had Nougat 7.1.2 with Lineage OS. I don't think Motorola is ever going to update the firmware of the Moto G 2015 to anything above 6.0.1. Does that mean that there is nothing I can do?
Is there any other way I can downgrade and lock?
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
"I get a 'Preflash validation' error when flashing a Firmware Image
The Firmware Image you are trying to flash is too old. You can only flash a firmware image that matches, or is newer than the most recent system version you have had on your phone. However the former scenario can also sometimes return the error. In which case, your options are to wait for an even newer firmware image or unlock Bootloader and flash a ROM zip."
Can anyone explain the parts in bold? I have an unlocked bootloader. If I flash a ROM zip will it downgrade? Can I flash the stock images and lock afterwards?
Click to expand...
Click to collapse
Well, there are some TWRP flashable stock rom available in a separate post. I think lost101 was referring to them. Still, I can't say for sure if they would work for locking.
You can still downgrade safely, just ignore the preflash validation for gpt.bin and bootloader.img. But you can't lock it that way.
Broadcasted from Zeta Reticuli
bump
Anyone else have more info?
nomuzephyr said:
bump
Anyone else have more info?
Click to expand...
Click to collapse
1st
Relocking bootloader will not restore the warranty.
2nd
Flash as you wrote without oem lock... commands, repeat any command if error. Don't reboot.
3rd
Flash as... with oem commands.
It works for some Moto models.
Hey, I just installed June security patch on my Moto G6 and I gotta say this build is super smooth.
I’m getting more than 5-6hrs of SOT and yes DIGITAL WELLBEING IS A SYSTEM APP NOW.
I downloaded the latest firmware from here : https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
And flashed it via RSD Lite.
Don’t forget to hit thanks
aaryan1596 said:
Hey, I just installed June security patch on my Moto G6 and I gotta say this build is super smooth.
I’m getting more than 5-6hrs of SOT and yes DIGITAL WELLBEING IS A SYSTEM APP NOW.
I downloaded the latest firmware from here : https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
And flashed it via RSD Lite.
Don’t forget to hit thanks
Click to expand...
Click to collapse
Can I install this patch with Android 9 OTA with Root?
bradz28 said:
Can I install this patch with Android 9 OTA with Root?
Click to expand...
Click to collapse
No, unfortunately not. This is a full wipe/fresh install only. The same rooting method works, but it will have to be a fresh install.
xfrobex said:
No, unfortunately not. This is a full wipe/fresh install only. The same rooting method works, but it will have to be a fresh install.
Click to expand...
Click to collapse
Ok, thanks
Hello, I upgraded my phone through CMD commands in fastboot folder, but now I can't hear nor be heard in calls. I tried already intalling the NON-HLOS.bin from Stock ROM RETAIL OPSS27.104-92-4 and tried with the NON-HLOS.bin from the Sotck ROM from my region OPENMX OPSS27.82-87-8 too, but it didn't work.
Tried turning the phone on Secure Mode to see if it was a problem related with an app but it wasn't the case, also tried couple of times doing factory reset, but it gave the same result.
I was on the RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8 and the calls were fine. Could someone help me, please?
I did all of above with locked bootloader.
Edit:
Now I unlocked bootloader to downgrading to RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8, and it didn't work so I relock bootloader.
mariconojoda said:
Hello, I upgraded my phone through CMD commands in a fastboot folder, but now I can't hear and can't be heard in calls. I tried already intalling the NON-HLOS.bin from Stock ROM RETAIL OPSS27.104-92-4 and tried with the NON-HLOS.bin from the Sotck ROM from my region OPENMX OPSS27.82-87-8, but it didn't work.
Also tried turning the phone on Secure Mode to see if it was a problem related with an app but it wasn't the case, also tried couple of times doing factory reset, but it gave the same result.
I was on the RETAIL PPSS29.55-34-1 and the calls were fine. Could someone help me, please?
All of above with locked bootloader.
Edit:
Now I unlocked bootloader to downgrading, I donwgrade to RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8, it didn't work so I relock bootloader.
Click to expand...
Click to collapse
As you unlocked the bootloader your warranty is gone, plus I didn’t try with CMD commands, I used RSD Lite, so maybe try a fresh install again if problem persists.
aaryan1596 said:
As you unlocked the bootloader your warranty is gone, plus I didn’t try with CMD commands, I used RSD Lite, so maybe try a fresh install again if problem persists.
Click to expand...
Click to collapse
It don't recognize the device
Nevermind I just needed to connect the device in another port, also now the calls work thank you @aaryan1596
How do I install this without RSDLite? The program doesn't work for me at all (v5.7 on Win10), and I do not fully understand how to use fastboot/batch files to install the unpacked .zip file. Thank you for your help.
Edit: I was able to easily install this using Minimal ADB and Fastboot. Simply extract the contents of your .xml.zip file to your Minimal ADB and Fastboot installation folder. Boot your phone into fastboot mode (volume+power down) and copy and paste these commands (you can copy and paste the entire block and they will run sequentially):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Using this method I was able to easily install to latest version onto my XT1925-6, which shipped with Oreo.
Is there any different between ROM with february security patch and this one (june security patch)?
Has anyone in the UK been able to download this update via system updates yet?
um.z said:
Has anyone in the UK been able to download this update via system updates yet?
Click to expand...
Click to collapse
Just downloading via system updates, channel: retgb.
Well, I received the June 1, PPS29.55-37-4 OTA (retgb channel) at around 9:40pm (Mon 5th Aug, UK time). It took 12 minutes to download the 818.6Mb package over a 4G connection, and a further 26 minutes to install it.
Everything went without a hitch, and all seemed perfectly fine afterwards...
...however, having previously read about the problems reported here on XDA and on the Lenovo/Motorola community support forum regarding recent Pie updates, I decided to perform a factory wipe/reset immediately after the update. A tiresome chore to be sure, having to set everything up again aftwards, but it just seemed the prudent thing to do.
So now, some 19 hours later, my G6 is still working perfectly, with no obvious problems, and it does certainly feel smoother and more responsive than it's predecessor, PPS29.55-24, which I received at the end of March. And, yep, this new 'build' includes Google's Digital Wellbeing app integrated at the system level, so I guess that's something new to tinker around with.
Anyhow, just some thoughts regarding my experience of updating to this latest version of Pie.
Rgrds,
Ged.
test