I have an unlocked bootloader, and am rooted. I've flashed TWRP before previously to root and have since reverted back to stock recovery. I've been trying to update the firmware to 4.4.4 as I have class 10 microsds that I can't currently use. Unfortunately when I try to update via the OTA it shows
installing
Click to expand...
Click to collapse
until I get an error code of just
error!
Click to expand...
Click to collapse
.
I've looked, and haven't seen the 4.4.4 firmware online anywhere that I can download and push. Is there anything I'm missing or any workarounds that are known? Are there any ROMs that have these fixes integrated?
Thanks
kdbrown5 said:
I have an unlocked bootloader, and am rooted. I've flashed TWRP before previously to root and have since reverted back to stock recovery. I've been trying to update the firmware to 4.4.4 as I have class 10 microsds that I can't currently use. Unfortunately when I try to update via the OTA it shows until I get an error code of just .
I've looked, and haven't seen the 4.4.4 firmware online anywhere that I can download and push. Is there anything I'm missing or any workarounds that are known? Are there any ROMs that have these fixes integrated?
Thanks
Click to expand...
Click to collapse
Just choose the one you like more:good::
link1
link2
Thanks! It failed flashing with TWRP so I'm assuming I have to use fastboot to push it similar to http://forum.xda-developers.com/showthread.php?t=2542219
I'll be doing it tomorrow as I want to back up a few thing before this wipes my data. Do you know what the difference in those 2 files are? I was going to use the (link 1) RETAIL-CA-SS instead of the (link 2) AMX-PE-SS as it was a few days newer.
edit:
The ones you linked are cid 12 and cid 14. According to this, I would be wanting cid9 for USA
http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
[Q] [help] Trying to flash a custom ROM to moto g, getting "bootloader not supported"
My moto g is XT1031, the Boost Mobile version.
I've tried to flash CM, BlissPop ROM, flexOS, and others. I always get "Bootleader not supported. Operation Aborted".
I want to flash a custom ROM because Boost Mobile never pushed out lollipop, and I want to try it out. This is not my primary phone, and is only used on Wi-Fi.
My Moto G is Rooted (I have the SuperSU app) and the bootloader is unlocked (Get the warning message on boot).
I'm flashing via Clockwork mod revocery 6.0.4.7
Any help is strongly appreciated.
Thanks.
By the way, this is the exact message:
This package supports bootloader(s): 0x4118, 0x4119, 0x411A; this device has bootloader 0x4113.
(Status 7)
Operation Aborted.
I was able to flash Cyanogenmod 11 Snapshot M6 Falcon, but not sure what to do after that. It seems that the bootloader is not compatible with Lollipop?
SuperCana said:
My moto g is XT1031, the Boost Mobile version.
I've tried to flash CM, BlissPop ROM, flexOS, and others. I always get "Bootleader not supported. Operation Aborted".
I want to flash a custom ROM because Boost Mobile never pushed out lollipop, and I want to try it out. This is not my primary phone, and is only used on Wi-Fi.
My Moto G is Rooted (I have the SuperSU app) and the bootloader is unlocked (Get the warning message on boot).
I'm flashing via Clockwork mod revocery 6.0.4.7
Any help is strongly appreciated.
Thanks.
Click to expand...
Click to collapse
SuperCana said:
By the way, this is the exact message:
This package supports bootloader(s): 0x4118, 0x4119, 0x411A; this device has bootloader 0x4113.
(Status 7)
Operation Aborted.
I was able to flash Cyanogenmod 11 Snapshot M6 Falcon, but not sure what to do after that. It seems that the bootloader is not compatible with Lollipop?
Click to expand...
Click to collapse
You have two options
1- Either update your bootloader to lollipop one which is 41.19 for cdma variants
2-Edit the updater script and metadata file of rom to allow you to flash the rom
First method is risky but better because you dont have to edit the updater scrip of every rom you wanna flash
sent from falcon
PRESS THANKS IF HELPED?????
sjandroiddeveloper said:
You have two options
1- Either update your bootloader to lollipop one which is 41.19 for cdma variants
2-Edit the updater script and metadata file of rom to allow you to flash the rom
First method is risky but better because you dont have to edit the updater scrip of every rom you wanna flash
sent from falcon
PRESS THANKS IF HELPED
Click to expand...
Click to collapse
Thanks. How do I update the bootloader to 41.19?
SuperCana said:
Thanks. How do I update the bootloader to 41.19?
Click to expand...
Click to collapse
I have the links to bootloader for gsm variants but not CDMA
I am asking someone experienced that is @matmutant, so please wait for a day
Till then I will tell you how to edit the updater script and metadata (credits to @wskelly )
Extract the zip and go to
META-INF/com/google/android/updater-script
META-INF/com/android/metadata
Alter the files as shown in the screenshots.
You will see the flickering/jumping of the screen on the first boot, but this will go away after you turn the screen off and then on once.
Screenshots are here
sjandroiddeveloper said:
I have the links to bootloader for gsm variants but not CDMA
I am asking someone experienced that is @matmutant, so please wait for a day
Till then I will tell you how to edit the updater script and metadata (credits to @wskelly )
Extract the zip and go to
META-INF/com/google/android/updater-script
META-INF/com/android/metadata
Alter the files as shown in the screenshots.
You will see the flickering/jumping of the screen on the first boot, but this will go away after you turn the screen off and then on once.
Click to expand...
Click to collapse
I found the download for bootloader 41.19 CDMA. Found here: https://www.androidfilehost.com/?fid=95916177934538145
I then flashed it via clockwork mod and then was able to flash BlissPop 5.1.1. All is working fine now, except the screen in clockwork mod has a flashing line. No big deal though, this doesn't impact the actual OS.
Thanks again for your help.
SuperCana said:
I found the download for bootloader 41.19 CDMA. Found here: https://www.androidfilehost.com/?fid=95916177934538145
I then flashed it via clockwork mod and then was able to flash BlissPop 5.1.1. All is working fine now, except the screen in clockwork mod has a flashing line. No big deal though, this doesn't impact the actual OS.
Thanks again for your help.
Click to expand...
Click to collapse
You have flickering screen in CWM recovery because it is based on kitkat bootloader
To remove
Just flash the latest TWRP by @h2o64 from xda ( not from official site )
Or try this unofficial Philz
https://docs.google.com/file/d/0B7lxW9DP17gNalk2Y3EtcU9JZTA/edit?usp=docslist_api
Sent from falcon
PRESS THANKS IF HELPED?????
I came across this site while searching for a solution to my problem which I thought can help you
They've mentioned instructions to Unlock Bootloader for different models :
https://forums.motorola.com/posts/35e4d3be5c
ravibhat said:
I came across this site while searching for a solution to my problem :
https://forums.motorola.com/posts/35e4d3be5c
Click to expand...
Click to collapse
You posted on a wrong thread
Updated my post for more clarity
Hope it helps OP or someone who is looking for a solution.
sjandroiddeveloper said:
You posted on a wrong thread
Click to expand...
Click to collapse
Hi,
I got my Moto G 2015 XT1541 running with Android 5.1.1 official rom and TWRP Osprey 3.0.0 R2. I just got the official message to upgrade to Marshmallow, but when I to upgrade TWRP comes with the following error: Updater process ended with ERROR: 7
I've placed a full log here: recovery.log
I also tried installing an other OTA file - (2GB Retail EU OTA): Download - thanks to @Osid - from here, but got the same error.
Also, the official update is version 24.41.33.en.EU, and the above file 23.41.47 and is already on my phone, according to "About Phone".
Anyway: Can someone please help me to get past this error and update to the official 24.41.33.en.EU? I've read about changing an updater-script file in the zip if you have one, but this is a block.map.
Thanks allot!
robert1010 said:
Hi,
I got my Moto G 2015 XT1541 running with Android 5.1.1 official rom and TWRP Osprey 3.0.0 R2. I just got the official message to upgrade to Marshmallow, but when I to upgrade TWRP comes with the following error: Updater process ended with ERROR: 7
I've placed a full log here: recovery.log
I also tried installing an other OTA file - (2GB Retail EU OTA): Download - thanks to @Osid - from here, but got the same error.
Also, the official update is version 24.41.33.en.EU, and the above file 23.41.47 and is already on my phone, according to "About Phone".
Anyway: Can someone please help me to get past this error and update to the official 24.41.33.en.EU? I've read about changing an updater-script file in the zip if you have one, but this is a block.map.
Thanks allot!
Click to expand...
Click to collapse
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
nobreak1970 said:
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
Click to expand...
Click to collapse
Both update methods, as described above, fail. Method 1: using the phone's system updater, method 2: using the official(?) OTA upgrade files provided on this site.
But it looks like the OTA file is of a version I already have. See attachment.
Sorry, I misread your reply. I am looking for the stock recovery now keep you posted.
nobreak1970 said:
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
Click to expand...
Click to collapse
Ok, I took the recovery.img from "XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7_subsidy-DEFAULT_CFC.xml", my version was 23.72-47. Hope that doesn't really matter. But is was the only 2GB European ROM I could find here.
So I used fastboot to flash that and tried the system update again. At the beginning it looked hopeful; It was showing the Installing System Update with the progress bar, but then briefly the error icon and rebooted without making any changes.
If I need to re-lock and/or un-root to fix this, can it be don without wiping everything?
Thanks again!
robert1010 said:
Ok, I took the recovery.img from "XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7_subsidy-DEFAULT_CFC.xml", my version was 23.72-47. Hope that doesn't really matter. But is was the only 2GB European ROM I could find here.
So I used fastboot to flash that and tried the system update again. At the beginning it looked hopeful; It was showing the Installing System Update with the progress bar, but then briefly the error icon and rebooted without making any changes.
If I need to re-lock and/or un-root to fix this, can it be don without wiping everything?
Thanks again!
Click to expand...
Click to collapse
Anyone who can help me with this please?
I was using cm 12.1 and wanted to update it to newer version, but after flashing it stuck in bootloop.
Now i can only flash cm 12.1 and don't know why ?
I've tried many types of different rom's but all end up in bootloop, only version 12.1 works.#
Thanks for help.
Fastboot doesn't work for me, when im trying start it, screen flashes and goes back to bootloader.
I dont care about any files so i've tried wiping everything mounting unmounting, factory resets etc. but still it boots only cm 12.1
Will someone be able to help me please ?
It's really important.
eskejpmi said:
Will someone be able to help me please ?
It's really important.
Click to expand...
Click to collapse
well you can only flash lollipop roms until you update your bootloader as far as I know. I haven't messed with any custom rom though, but I at least read the threads.
lafester said:
well you can only flash lollipop roms until you update your bootloader as far as I know. I haven't messed with any custom rom though, but I at least read the threads.
Click to expand...
Click to collapse
When I search for " bootloader update nvidia shield " there is no such thing on the internet.
I read a lot of threads and still haven't found a solution to my problem.
Still thanks for the reply.
So basically i can only boot CyanogenMod 12.1 on mine device. No other ROM boots.
You can find the Marshmallow bootloader (4.2.0) under Firmware Update of the OP of the CM13 thread. First, make sure you're using the latest official TWRP 3.0.2-2 before flashing the bootloader.
*PROBLEM RESOLVED*
Firstly i had to unlock bootloader through fastboot - I haven't checked it at first.
After that I flashed updated firmware from upper post.
Had a lot of problems making fastboot working on my pc, but after few hours spent on searching I finally got it running.
Then I flashed CM13 and it worked !
Thanks for help !
Moto G4 Plus US Variant XT1644
Build# MPJ24.139-64 Android 6.0.1
Stock Unmodified TWRP Backup
Stock Recovery.img & Logo.bin
Description:
I could not find ANY stock images for the US XT1644 variant so I made my own for others that have modified their system partition and wish to restore to a factory state and take the 7.0 update. Backup created on a factory reset unmodified stock build (not previously rooted/xposed/modified in any way) via fastboot booting TWRP w/system write disabled. Stock recovery and logo extracted via DD from stock rooted rom after TWRP backup was made. I pulled the recovery and logo images as these are the most commonly modified partitions (other than the system). This backup will work if you stayed on 6.0.1 and rooted/exposed/changed boot logo/etc. If you played with the 7.0 updates made for other variants, I honestly don't know if this will work for you to take the OTA as the bootloader/modem were likely modified - Test and let us know.
Directions:
-Have ADB working on your PC (google it, not getting into that here)
-Download TWRP backup here: https://mega.nz/#F!vBgU3QJB!R5J5RgZkvUiWHwmIfN6BkA
-Move backup to your proper TWRP backup location on your sd or external sd
-Restore backup via TWRP and reboot
-Download stock recovery & logo images here: https://mega.nz/#F!eBpB3Z5C!J6hoLKdfcObSLavWCsLnyw
-Power off device/plug into pc/hold volume down for 5 seconds/press and hold power & volume down until fastboot appears
-Move files to adb location (Windows) or open terminal where you downloaded the files (Linux) on your pc
-Verify connection
Code:
fastboot devices
-Restore stock recovery:
Code:
fastboot flash recovery recovery.img
-Restore stock logo (if you changed it previously to get rid of warning):
Code:
fastboot flash logo logo.bin
-Reboot and enjoy stock 6.0.1 and be able to take OTA
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Click to expand...
Click to collapse
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Sent from my XT1575 using Tapatalk
annoyingduck said:
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Click to expand...
Click to collapse
I Will flash stock xt1644 firmware 64, then i restore your backup
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
pupamonkey said:
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
Click to expand...
Click to collapse
It's not available, we're still waiting for it, that's why we flashing stock firmware again
Thanks for doing this! It's essentially what I did to get the marshmallow update (restore stock system & boot via TWRP, then recovery & logo via fastboot).
Please let us know when you see moto/Lenovo push out the nougat update via OTA!
Sent from my Moto G4 Plus using Tapatalk
you are the champ!! i have exact same model but i am yet to update to 64 release as i just got the phone today. Just doing some research before i grease my hands! thanks man!
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
bmeek said:
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
Click to expand...
Click to collapse
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
where to check?
i have the us variant from best buy as well , but i twicked it a lot .
How can i know when a nougat release is available? where can i check .
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
Click to expand...
Click to collapse
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Hymizzle said:
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Click to expand...
Click to collapse
If you flash a XT1625-XT1644 firmware and you use it "normally" on a XT1644, at some point you will have ghost touch even with low brightness, but...
For upgrading, I'll recommend flashing XT1625-XT1644, (cause there's no
...139-64 XT1644 firmware, just a firmware for both)
Flash it via fastboot, boot it up, flash TWRP recovery, wipe the full system with it, download the TWRP backup that was posted here, restore it, then via fastboot flash the stock recovery (for removing TWRP) and stock logo, then you will have MPJ24.139-64 with no problems, just waiting for nougat OTA for retus version.
Here's the link for retus firmwares: https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
TheDude1998 said:
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
Click to expand...
Click to collapse
Yeah I wouldn't think so, but thanks for letting us know.
Sent from my XT1575 using Tapatalk
getting the Nougat OTA
annoyingduck said:
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
Click to expand...
Click to collapse
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Click to expand...
Click to collapse
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
dedik46 said:
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
Click to expand...
Click to collapse
Yes your bootloader will still be unlocked unless you specifically enter the oem lock command. Read the tutorials, they all explain how to keep your bootloader unlocked.
Sent from my XT1575 using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
vishnureddy17 said:
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
Click to expand...
Click to collapse
Which of these 5 download? .