[ROM][PEREGRINE][5.1][STOCK] Stock Motorola 4G Lollipop ROM Collection

[lost101]

Now we are getting somewhere. There are issues cropping into the device and maybe you are correct. But I think that maybe a larger warning on the 1st post that these issues are beginning to appear might deter someone from doing this update and then not being happy. I have since downgraded my XT1045 back to the original version, however there is still the issue of the flicker. Yes, there is a work around, but a work around is not a solution. Right now, there does not seem to be a solution.

Again, I am not pointing fingers nor accusing anyone of wrong doing. Just that these issues are appearing and it is disheartening to have a perfectly fine phone stop being perfectly fine. The phone still works, data work, wifi works, I can make and receive calls. So other than kicking myself in the behind for not letting sleeping dogs lie, I kicked the dang dog and now regret it.

Please stop compressing together different issues just to support your own world-view. The vast majority of people greatly benefit from customization of Stock and AOSP ROMs, that is why this forum exists.

You are incorrect in your previous assertion that running any version of Android other than pure OEM Stock will be problematic. I have many years of experience with Motorola handsets and personally always run optimized Stock with no issues.

Regarding the 'optimizing apps' message; You could try deleting the following file in the optimized ROMs:

system/etc/init.d/darky_zipalign​

Secondly, downgrading of Bootloader is extremely dangerous and usually impossible. You have correctly identified the Bootloader is causing your screen to flicker with certain Kernels. This is something that can be permanently resolved with a Kernel created to address the problem.

 

[Brian D]

Wow, you are taking this way too personal.

 

[IronTechmonkey]

Wow, you are taking this way too personal.

Huh? The replies to you were analytical, descriptive, offered a workaround/solution, and did not seem personal at all.

You seem to expect that your passage through this software universe be guaranteed from the start to have no future issues. Little in life is like that, no less software development. If you don't like the meal, then don't pull up to the table, or even better, pull up to the stove and cook us up something that you think is better .

 

[lost101]

Wow, you are taking this way too personal.

Apologies if my tone was too strong. My only intention was to try to help.

 

[Brian D]

And it was my intent to only advise what issues were now visible, not to point fingers at anyone. We must now agree to disagree. But so you know, the ROM did work other than the issues I reported and they were not caused by your work.

 

[IronTechmonkey]

Apologies if my tone was too strong. My only intention was to try to help.... incorrect in your previous assertion that running any version of Android other than pure OEM Stock will be problematic. I have many years of experience with Motorola handsets and personally always run optimized Stock with no issues.

IMO Your tone was just fine and in particular that point had to be made. I've been using custom ROMs on 2 Peregrine devices for years to better effect than stock firmware, as has been the case for 5 years across 6 other Moto devices as well. Now I'll get out of here before I continue typing and make this worse. Thanks for giving us this firmware option.

 

[Shaileshkr]

Thanks,
Shailesh Kr.

 

[lost101]

Please find a mail sent at your [/QUOTE]
Please remove that email address from your post. It's best to create a thread if you want help in future. Use [user=1006674]@lost101[/user] to get my attention.

Flash the latest available factory firmware image for your model.

Firmware Images: [url]https://xdaforums.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639[/url]
Firmware Image flashing Tutorial: [url]http://xdaforums.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750[/url]

[B]Note: You must perform a 'Factory data reset' in Stock Recovery before flashing any Firmware Image - [URL="http://xdaforums.com/showpost.php?p=66521508&postcount=590"]instructions here[/URL].[/B]

 

[Brian D]

I have since reloaded the 5.1 firmware and and have figured out the problem with the "optimizing..." issue. As long as I do not upgrade SuperSU from 2.46 (the version found in the ROM) then my XT1045 works as advertised. It seems that every time I did any kind of SuperSU upgrade, or tried to back out of the upgrade the phone would do the "Optimizing..." every time after a reboot.

So, for ME, the answer was to not allow SuperSU to upgrade. Took me many times loading and testing before I narrowed it down. This was tested with SD card in and out and the results were the same.

This is just an FYI if anyone is having the "Optimizing..." issue at boot.

Summary: For my XT1045, "Optimizing..." at boot was being caused by an upgrade of SuperSU 2.46 to any version.

Again, thanks for the 5.1 ROM.

added: I tried to upgrade SuperSU via the TWRP method and the normal method. The results were the same. I am wondering if flashing SuperSU img file might result in a different outcome?

 

[Adilshah055]

please give me moto xt1090 flash file

please give me moto xt1090 flash file

 

[90Ninety9]

EU Radio Firmware not updating on penegrine

OK . I picked out my old Moto G X 1039 Penegrine . It has been sitting in a box for years since I had stopped using it after a flash went wrong .

Basically the phone has an unlocked bootloader and has TWRP 2.7.1.0 installed .

I have since installed the 5.1 official untouched EU rom using the ADB sideload method . ( TWRP would not read/detect my external SD ) .

Now I am back to my original problem , the radios on the phone don't work . I have tried flashing the radio firmware multiple times but this gives me the same error every time

Erasing modemst1...
assert failed: format ("raw" "EMMC", "modemst1", "0", "/modemst1")
E:Error executing updater binary in zip '/data/media/0/sideload.zip'
Updating partition detals...

I would really like to use this phone , can anyone advise me , please post or send PM
[EDIT]

Despite the error , I just restarted the phone and it works !

Now im getting a weird random 'boot into recovery mode ' on its own !

 

[Rob...]

OK . I picked out my old Moto G X 1039 Penegrine . It has been sitting in a box for years since I had stopped using it after a flash went wrong .

Basically the phone has an unlocked bootloader and has TWRP 2.7.1.0 installed .

I have since installed the 5.1 official untouched EU rom using the ADB sideload method . ( TWRP would not read/detect my external SD ) .

Now I am back to my original problem , the radios on the phone don't work . I have tried flashing the radio firmware multiple times but this gives me the same error every time



I would really like to use this phone , can anyone advise me , please post or send PM
[EDIT]

Despite the error , I just restarted the phone and it works !

Now im getting a weird random 'boot into recovery mode ' on its own !

from which android version do you come.

 

[90Ninety9]

OK . I picked out my old Moto G X 1039 Penegrine . It has been sitting in a box for years since I had stopped using it after a flash went wrong .

Basically the phone has an unlocked bootloader and has TWRP 2.7.1.0 installed .

I have since installed the 5.1 official untouched EU rom using the ADB sideload method . ( TWRP would not read/detect my external SD ) .

Now I am back to my original problem , the radios on the phone don't work . I have tried flashing the radio firmware multiple times but this gives me the same error every time



I would really like to use this phone , can anyone advise me , please post or send PM
[EDIT]

Despite the error , I just restarted the phone and it works !

Now im getting a weird random 'boot into recovery mode ' on its own !

from which android version do you come.

I think it was 4.4 but , the phone was stuck on "unlocked bootloader" screen, so am not 100%.
I think the SU application is forcing restart , so may have to reflash without the SU app , I guess . Ideally I want to lock the bootloader , as the atm/banking apps wont work . I am guessing the bootloader locking is done separately ?

 

[Rob...]

I think it was 4.4 but , the phone was stuck on "unlocked bootloader" screen, so am not 100%.
I think the SU application is forcing restart , so may have to reflash without the SU app , I guess . Ideally I want to lock the bootloader , as the atm/banking apps wont work . I am guessing the bootloader locking is done separately ?

if you come from android 4, you have to upgrade the bootloader. flash stock android 5.1 for your device, should upgrade the bootloader. maybe someone knows how to flash only the bootloader.

forget everything, my mistake

 

[Sofiane omega]

what dose it mean (Partially 'Stagefright' Patched) in the xt-1039 untouched ROM

 

[J0hnick]

Is it no longer possible to do an OTA update from official stock Kitkat to Lolipop ?. My wife's old Moto G 4G is still on 4.4.4, I was gonna root it and put lineage on it but wanted to update it first so the radio firmware is OK, but it keeps telling me the phone is already up to date (when it obviously isn't).

 

[roton]

I have a problem with the radio, signal loss problem. I tried many roms (like 5), it won't work with any.
Tried to flash the radio firmware here, it's impossible with TWRP (no modemst1 error 7), but without errors with mfastboot (however it's very quick doing it).

Any solution?

I just solved my error 7 (on Peregrine) using this - https://xdaforums.com/moto-g/general/falcon-bootloader-upgrader-tool-t3093793/
It seemed to be the only way to make it work.

 

[joey000]

I have a peregrine phone which can make phone calls and send & receive texts, and connect to wifi, but which does not seem to do anything with cellular data.

A few weeks ago I tried upgrading this phone from an "unbloated" version of Android 6 to a LineageOS version of Android 7.1.12. And immediately this problem began, even though I've been told that upgrading a ROM has no bearing on the radio partitions.

Does anyone have any tips or suggestions? I can't remember what all I tried to do to fix this situation, but nothing seemed to work. I think I tried flashing the radio firmware that is mentioned at the beginning of this thread, but if I did I did not take notes on what exactly I did and what exactly happened.

I've also got TWRP v.3.2.3-0 and Fastboot v.41.1a on this phone.

Thank you for your time and compassion.

 

[nachogl1]

Lollipop update stopped

Hello,
I have an XT1039 (MotoG) which I have previously updated to lollipop from kitkat using Motorola update services. However I came back to this today after a few months and when I try to update an XT1039 the Motorola update scheduler states 'All Software Up To Date'. Does anyone know if Motorola have pulled lollipop for the XT1039 and if so is there an alternative service

Thank you.

 

[IronTechmonkey]

Hello,
I have an XT1039 (MotoG) which I have previously updated to lollipop from kitkat using Motorola update services. However I came back to this today after a few months and when I try to update an XT1039 the Motorola update scheduler states 'All Software Up To Date'. Does anyone know if Motorola have pulled lollipop for the XT1039 and if so is there an alternative service

Thank you.

As this thread is specifically about a particular custom ROM called Lineage OS 14 and your question seems to be about stock ROM updates this is not the most appropriate or productive place for your question. That being said, here is some information which may help.

It sounds like you are still on the stock ROM in which case it is normal to reach a point where there are no more updates, especially for a device and Android version this old. Motorola, in cooperation with the various service providers, will keep the device updated for some time but that is not endless, usually just a year or two. First the major updates stop and the security updates continue then the security updates stop as well.

You should be able to learn more by searching the internet about stock updates to the device.