Related
Hey Guys, bought my phone in Australia at retail. It's running 4.3 JB. I've already unlocked the bootloader and installed a recovery. Now I want to run KitKat. I checked and there's no OTA, it says I'm already up to date. I don't care about the dual sim at all as I only have one sim (it's actually quite annoying having two icons in the statusbar).
Can I just go and install any Moto G KitKat ROM onto the phone and it will work? Is it better to have the official OTA so that it updates the radios before installing a custom KitKat ROM? Do the radios matter? Will I brick my XT1033 if I install a ROM for XT1031, XT1032 etc. ?
Just asking before I kill the phone.
Thanks guys
Single SIM ROMs are not compatible with dual chip XT1033.
From what I have read there is only 2 options:
1. unlock the phone and load en.GB 4.3 ROM and wait for the 4.4 kitkat update on it
2. CM11 by dhacker29 - Read first post about the details about how to flash to XT1033 where you need to flash a modem as well. http://forum.xda-developers.com/showthread.php?t=2608377
Whatever you do, make sure you do a backup of the stock ROM as I don't see Australian ROM in the stock images thread yet. So if you need to go back you can safely restore. To Restore from CM11 you need to flash the old modem as well that is in the same thread.
There are no cases of bricking so far that I am aware of. Also you could try fastboot flashing* the en.GB 4.4.2 firmware.
http://forum.xda-developers.com/showpost.php?p=49861244&postcount=101
*mfastboot may be required.
EDIT: You should be aware that flashing the GB firmware also includes the GB Modem/Radio firmware. If you notice data/wifi/coverage issues after flashing, this may be the reason. There is currently on AU firmware image you can restore with.
Excluding the following commands should allow you to retain the AU Modem/Radio firmware:
flash modem NON-HLOS.bin
erase modemst1
erase modemst2
flash fsg fsg.mbn
syl0n said:
Single SIM ROMs are not compatible with dual chip XT1033.
From what I have read there is only 2 options:
1. unlock the phone and load en.GB 4.3 ROM and wait for the 4.4 kitkat update on it
2. CM11 by dhacker29 - Read first post about the details about how to flash to XT1033 where you need to flash a modem as well. http://forum.xda-developers.com/showthread.php?t=2608377
Whatever you do, make sure you do a backup of the stock ROM as I don't see Australian ROM in the stock images thread yet. So if you need to go back you can safely restore. To Restore from CM11 you need to flash the old modem as well that is in the same thread.
Click to expand...
Click to collapse
thats true, I flased cm11 and both sim signal not work,
then I flash modem xt1033 same not work again,
finally I restored my stock room and sit like a boss for waiting 4.4 officiall update,
my moto g from malaysia retailer. :angel:
invictussevenfold said:
thats true, I flased cm11 and both sim signal not work,
then I flash modem xt1033 same not work again,
finally I restored my stock room and sit like a boss for waiting 4.4 officiall update,
my moto g from malaysia retailer. :angel:
Click to expand...
Click to collapse
hi, do you manage to flash kitkat and get single sim to work?
devalian said:
hi, do you manage to flash kitkat and get single sim to work?
Click to expand...
Click to collapse
i did, with the following update OTA GB 4.4.2, but something wrong when flash using sideload or put zip file to sdcar, so it cant be done.
n today I want to change my moto to single sim, because I dont need dual sim acctually. keep calm developer
invictussevenfold said:
i did, with the following update OTA GB 4.4.2, but something wrong when flash using sideload or put zip file to sdcar, so it cant be done.
n today I want to change my moto to single sim, because I dont need dual sim acctually. keep calm developer
Click to expand...
Click to collapse
cool. i did tried a several methods, but i couldnt get the radio signal at all. so was wondering what did i did wrongly.
mind to elaborate more on your steps?
juzza87 said:
Hey Guys, bought my phone in Australia at retail. It's running 4.3 JB. I've already unlocked the bootloader and installed a recovery. Now I want to run KitKat. I checked and there's no OTA, it says I'm already up to date. I don't care about the dual sim at all as I only have one sim (it's actually quite annoying having two icons in the statusbar).
Can I just go and install any Moto G KitKat ROM onto the phone and it will work? Is it better to have the official OTA so that it updates the radios before installing a custom KitKat ROM? Do the radios matter? Will I brick my XT1033 if I install a ROM for XT1031, XT1032 etc. ?
Just asking before I kill the phone.
Thanks guys
Click to expand...
Click to collapse
I downloaded and uncompressed android 4.3 firmware - Blur_Version.14.71.8.falcon_umts.Retail.en.GB from http://sbf.droid-developers.org/phone.php?device=14
then ran the "flash-all.bat" script. Rebooted and then did the OTA update. A single (primary) sim works no issues, and my model number now says XT1032 instead of XT1033.
I'm sure you'd get the same result by just flashing straight Android 4.4.2 for Great Britain - Blur_Version.174.44.9.falcon_umts.Retail.en.GB
I only need one sim anyway, so it works well for me. then I make lots of modifications with Xposed.
gregneal said:
I downloaded and uncompressed android 4.3 firmware - Blur_Version.14.71.8.falcon_umts.Retail.en.GB from http://sbf.droid-developers.org/phone.php?device=14
then ran the "flash-all.bat" script. Rebooted and then did the OTA update. A single (primary) sim works no issues, and my model number now says XT1032 instead of XT1033.
I'm sure you'd get the same result by just flashing straight Android 4.4.2 for Great Britain - Blur_Version.174.44.9.falcon_umts.Retail.en.GB
I only need one sim anyway, so it works well for me. then I make lots of modifications with Xposed.
Click to expand...
Click to collapse
I am really curious so I'll try this. Downloading "Blur_Version.174.44.9.falcon_umts.Retail.en.GB" and will report back, worst case I just run the stock flash all again (Blur_Version.14.85.4.falcon_umtsds.AsiaRetail.en.03) now that I know there's no risk
juzza87 said:
I am really curious so I'll try this. Downloading "Blur_Version.174.44.9.falcon_umts.Retail.en.GB" and will report back, worst case I just run the stock flash all again (Blur_Version.14.85.4.falcon_umtsds.AsiaRetail.en.03) now that I know there's no risk
Click to expand...
Click to collapse
I used this guide http://forum.xda-developers.com/showthread.php?t=2542219
Changed the filenames for these commands to reflect the files in the folder:
mfastboot flash system system.img_sparsechunk1
to
mfastboot flash system system.img_sparsechunk.0
It is rebooting now.
Boot animations works [OK]
"Preparing Device - Please Wait..." [OK]
Choose Language (KK style!) [OK]
So far I only have one SIM card working with only one set of icons at the top and it has successfully connected to Vodafone AU (YES!)
Wifi network detected [OK]
OK everything is running! WiFi is working, phone is now running 4.4.2 KitKat! Just called myself and it worked!
THANKS GUYS
I will follow up later on. First thing I'll try is recovery, root, xposed framework and see if I can change the battery icon to show percentage (this wasn't possible on the JB ROM but I suspected because of the dual sim and likely a different SystemUI.apk
I had trouble rooting but then just used this flashable zip http://forum.xda-developers.com/showthread.php?t=2585755 and it got there.
I installed Xposed and everything worked as expected, using gravity box I changed the battery to one with a percentage and reduced the navigation bars to 70% (gives more screen real estate). Using the Google Experience Launcher, Google Keyboard and enabling ART has made this device a bit closer to my Nexus 4 which the screen broke on, so I'm very happy with this device.
Now I just need to work out how to get rid of the carrier name in the status bar (VODAFONE AU takes up a lot of room :silly
EDIT: Thanks Moto X community http://repo.xposed.info/module/com.penree.android.xposed.hidecarriermotox now it's gone
devalian said:
cool. i did tried a several methods, but i couldnt get the radio signal at all. so was wondering what did i did wrongly.
mind to elaborate more on your steps?
Click to expand...
Click to collapse
I think you should be waiting for general thread for moto G dual sim, and also they will create another rom for it.
I use Q10 now, bored with android :victory:
I flashed Google Play edition 4.4.2 ROM on my XT1033 + added Xposed GravityMod. Gives me 90% of what Cyanogenmod does so I am pretty happy.
syl0n said:
I flashed Google Play edition 4.4.2 ROM on my XT1033 + added Xposed GravityMod. Gives me 90% of what Cyanogenmod does so I am pretty happy.
Click to expand...
Click to collapse
Can you share some step by step instructions and links please?
Sent from my XT1033 using Tapatalk
occtec said:
Can you share some step by step instructions and links please?
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
try this.
http://forum.xda-developers.com/showthread.php?t=2635706
it works for me, changing XT1033 to single sim and kitkat.
1) download the file in the link
2) run the program and flash image with outside usa
3) flash cwm recovery
4) push superSU
5) install xposed framework with framework installer.
devalian said:
try this.
http://forum.xda-developers.com/showthread.php?t=2635706
it works for me, changing XT1033 to single sim and kitkat.
1) download the file in the link
2) run the program and flash image with outside usa
3) flash cwm recovery
4) push superSU
5) install xposed framework with framework installer.
Click to expand...
Click to collapse
Will give it a shot later, cheers mate. Just flat out with work atm. :banghead:
Sent from my XT1033 using Tapatalk
occtec said:
Can you share some step by step instructions and links please?
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
I used this: http://forum.xda-developers.com/showthread.php?t=2633272
Follow step by step instructions for International. Flash it all using fastboot. After the last step, before reboot, flash this GPE recovery: http://forum.xda-developers.com/showthread.php?t=2634008 (unzip it and run this command: fastboot flash recovery CWM6046-falcon_gpe.img)
Then I rebooted into the CWM recovery and used adb sideload to load to root it - follow this post exactly: http://forum.xda-developers.com/showpost.php?p=49996027&postcount=19
Once rooted installed Xposed and customise
syl0n said:
I used this: http://forum.xda-developers.com/showthread.php?t=2633272
Follow step by step instructions for International. Flash it all using fastboot. After the last step, before reboot, flash this GPE recovery: http://forum.xda-developers.com/showthread.php?t=2634008 (unzip it and run this command: fastboot flash recovery CWM6046-falcon_gpe.img)
Then I rebooted into the CWM recovery and used adb sideload to load to root it - follow this post exactly: http://forum.xda-developers.com/showpost.php?p=49996027&postcount=19
Once rooted installed Xposed and customise
Click to expand...
Click to collapse
How do you find the Play Edition compared to the Motorola version of KitKat? Pretty much the same thing just without the Motorola apps, settings, sounds and wallpaper?
I'm really happy with the Motorola software but wouldn't mind putting the Play edition on if it's much better
juzza87 said:
How do you find the Play Edition compared to the Motorola version of KitKat? Pretty much the same thing just without the Motorola apps, settings, sounds and wallpaper?
I'm really happy with the Motorola software but wouldn't mind putting the Play edition on if it's much better
Click to expand...
Click to collapse
Its not that much different.
The main issues i have with moto edition is that there is no internet calling in dialer (This is for VOIP accounts - Moto removed it from the Moto G for some reason and most 3rd party apps suck compared to native VOIP calling)
Minor issues (Nothing that can't be fixed with root)
- hidious career label in status bar (in en.GB 4.2.2)
- ugly dual SIM 2 signal bars wasting space on the status bar + 3G/H+ icon
- No useless Motorola apps that I don't need
Whats better in Moto ROM
- Camera App (GPE has no HDR)
- FM Radio (not in GPE)
- Faster file system (but this is barely noticable, GPE feels the same speed for me)
Is it ok to update to kitkat from 4.3? Ive only just tried it and says update available
i had the latest COS12 stock rom (rooted)
few days ago my battery ran out and after charging, the device got into bootloop.
i tried the onplus fix (https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/) which indeed fixed my bootloop and flashed KTU84Q (4.4.4), however, my wifi doesn't turn on now:
https://youtu.be/xchjcNl3pPk
i've tried clean flash again (with lolipop i get bootloop again)
i've also tried flashing color os (kitkat) and also no wifi
so far my problem seems to be:
on lolipop - bootloop
on kitkat - no wifi
any one has any idea?
matanp said:
i had the latest COS12 stock rom (rooted)
few days ago my battery ran out and after charging, the device got into bootloop.
i tried the onplus fix (https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/) which indeed fixed my bootloop and flashed KTU84Q (4.4.4), however, my wifi doesn't turn on now:
https://youtu.be/xchjcNl3pPk
i've tried clean flash again (with lolipop i get bootloop again)
i've also tried flashing color os (kitkat) and also no wifi
so far my problem seems to be:
on lolipop - bootloop
on kitkat - no wifi
any one has any idea?
Click to expand...
Click to collapse
A few questions:
What method are you using to switch between KK and LP? Fastboot (flashing stock images) or recovery?
If it's recovery, are you flashing the correct firmware/modem?
Are you still able to see your baseband and IMEI in About Phone?
IF you haven't flashed the stock images with fastboot that's the first thing you should try. I have detailed instructions in my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
first, thanks for your reply
second:
at first i did a clean flash from fastboot like this: https://forums.oneplus.net/threads/tutorial-flashing-a-factory-image-from-scratch.142870/
i also tried the oneplus one fix for bootloops that also use fastboot from here: https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/
later, i tried flashing from recovery, also the colorOS rom
the common for all is LP = bootloop \ KK = no wifi
when i'm on KK the phone works got, getting calls in and out
when i've flashed from recovery i've flashed only one zip file. didn't flash firmware nor modem
matanp said:
first, thanks for your reply
second:
at first i did a clean flash from fastboot like this: https://forums.oneplus.net/threads/tutorial-flashing-a-factory-image-from-scratch.142870/
i also tried the oneplus one fix for bootloops that also use fastboot from here: https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/
later, i tried flashing from recovery, also the colorOS rom
the common for all is LP = bootloop \ KK = no wifi
when i'm on KK the phone works got, getting calls in and out
when i've flashed from recovery i've flashed only one zip file. didn't flash firmware nor modem
Click to expand...
Click to collapse
Have you flashed the latest Lollipop build with fastboot as outlined in my guide?
not with your guide but with the guide in the link in my last post
also i don't remember seeing a userdata 64GB file in the lolipop image i had
matanp said:
not with your guide but with the guide in the link in my last post
also i don't remember seeing a userdata 64GB file in the lolipop image i had
Click to expand...
Click to collapse
That's because the LP images don't usually contain it, but the ones I link to do.
i'll try and report
thanks
i just got a message from oneplus support:
Hi Matan,
Thank you for reaching out. Sorry for the inconvenience that has caused to you. Rest assured that we will be providing you solutions in solving the issue.
You can also try to flash the device to the latest Oxygen OS, it is designed to fix common bugs that causes the issue.
To install OxygenOS on your OnePlus One, you need to flash the device. You may follow the guidance here:
https://forums.oneplus.net/threads/oxygenos-is-here-installation-guide.289398/
Please also note that since OxygenOS is a product from OnePlus therefore it is currently only available for OnePlus One.
Please don't hesitate to contact us for any update and feedback.
Thank you and have a good day.
Regards,
Jefflee
Click to expand...
Click to collapse
can i flash oxyOS (to check if it solve the problem) and after that flash your COS12 img with the fastboot commands or is there anything else i should know about?
flashed the latest COS12 version with your guide and i still have bootloops
Having this exact problem.... No wifi in CM11 and when updating tot CM12 getting boot looped.
Found a solution to your problem?
It's because of the modem files.. When u downgrade or upgrade from/to lollipop/kitkat u must flash the appropriate files!! Pm me if u want more info
Sent from my A0001 using Tapatalk
yes, i've open a ticket with oneplus one and their tech guy installed oxygenOS and it works well
This is only for devices currently on 4.4 or rooted 5.1 w/ moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Note 12/2/2015:
Development on this has been discontinued with the release of the SunShine bootloader unlock.
To use SunShine without having to deal with KingRoot, you can flash the Rooted v3 system img and then use SunShine to unlock. This is the most stable method if you can use mofo.
After unlocking using SunShine, please flash the latest bootloader/radio images from here. This will bring your phone completely up to date and provide a more stable experience with custom ROMs.
These images are still flashable after unlocking your bootloader if you'd like a stable, closest-to-stock ROM possible.
Instead of using mofo to flash the system image, you can just use
Code:
fastboot flash system filename-goes-here.img
You can then flash your own tweaks like Xposed.
I'd recommend making a back up of the stock ROM in TWRP so you have a stable base to go back to if anything goes wrong.
Note 10/10/2015:
Updated all images to the latest OTA update (SU4TL-44) and included the latest official Xposed version (v75) in extras v5.
Follow the instructions with 5.1_images_v4.zip to flash the updated firmware images.
Note 9/5/2015:
Updated extras (v4) to include the latest official Xposed version (v73). Read the previous note for more information.
Note 8/31/2015:
Updated extras to the latest official Xposed version (v72). Reflashing all of the images is not required, only the extras system.img using mofo.
You can download the full extras image (1.5gb), or if you already have the rooted v2 image, use the extras v3 patch (8mb) with the instructions below.
Using the rooted v2 image + patch will allow you to update in the future without redownloading the entire image (as long as you keep the original after patching).
Note 7/23/2015:
Updated to the latest OTA (23.11.39). Make sure to follow instructions and reflash all images from the latest zip.
Unfortunately, I couldn't provide a patch to go from rooted image v1->v2, so a redownload is needed.
When applying the latest extras, make sure you're applying it to the rooted image v2.
Files (updated 10/10/2015 w/ latest OTA & extras v5)
5.1 firmware images (v4)
SHA1: 8be8a19664e6ba5aa556838bb3f744cdbf41f2ef
Stock 5.1 system image (v3)
SHA1: 1e67fc22331f035e9f3bd6c28d81fb173dd86a3e
Rooted 5.1 system image (v3)
SHA1: b8ff04d7f6ad9de31292cf62da94a3d80d3e373c
Extras 5.1 system image (rooted v3 + extras v5) (see below for details)
SHA1: 126744919f86132c05d15e79373ea759f74e37cf
Instructions
A data wipe is not required, but please back up any important data beforehand in case something goes wrong.
After extracting 5.1_images_v4.zip, reboot into bootloader and run the following commands to prepare your phone for the latest 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem modem.img
fastboot flash mdm1m9kefs3 fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs2
fastboot flash recovery recovery.img
fastboot erase ddr
fastboot reboot-bootloader
Then use mofo to flash the system image of your choice and reboot.
After flashing a system image, the first boot will stay on the Motorola logo for an extra 30 seconds to 1 minute. This is rebuilding the cache partition (erased by moforoot after every flash).
If your phone doesn't boot after 5 minutes (and isn't showing the "Upgrading apps" dialog), try formatting the cache in recovery by doing the following:
While phone is off, hold the volume down button and turn it on to boot into bootloader. Use the volume keys to find the recovery option and press power to confirm.
Once you see the dead Android (it may also say "No Command", this is normal), pull up the recovery menu by holding power and pressing volume up (5.1 recovery is different than 4.4) and use the wipe cache option.
If the screen is blank in recovery with a periodically flashing Android icon, try booting the phone normally and trying again. This happened to me a few times, and I theorize it's because of the cache partition not being formatted after erased.
Extras (updated 10/10/2015 w/ latest OTA & Xposed official v75)
Download patch (v5)
SHA1: 451be2eef3df509facf16b807c6fc665c8fac090
If you don't want to deal with patching the image using xdelta3, you can download the full extras image in the Files section above.
This will prevent you from updating without redownloading the whole image in the future, but is easier for less experienced users.
Current extras:
Xposed official v75 (download APK from here)
(optional) ad blocking
busybox/sqlite3
tethering enabled
To apply the patch, use the rooted v3 image (not an already patched image) as a base, and follow the patching instructions (using xdelta3) in this post.
After patching the system.img with the extras, you'll use mofo to flash the patched image.
To use ad blocking, download AdAway (available in F-Droid) and enable it. Make sure the "Target hosts file" is set to "/data/hosts" in settings.
shouldnt we also be updating the radio?
diabl0w said:
shouldnt we also be updating the radio?
Click to expand...
Click to collapse
I haven't personally tested upgrading the radio, and whether that affects downgrading at all. If someone confirms it's without risk, I'll add the radio.img to the zip and instructions.
firstEncounter said:
I haven't personally tested upgrading the radio, and whether that affects downgrading at all. If someone confirms it's without risk, I'll add the radio.img to the zip and instructions.
Click to expand...
Click to collapse
ive downgraded radio from 4.4 to 4.2 in the past, but it messed up wifi somehow... isnt wifi part of the modem image? anyways, nothing else bad happened so idk if this is useful info
edit: when i did the downgrade (4.4.4 to 4.4.2 radio) it disabled the ability to turn on wifi and log messages gave the error wifistatemachine: failed to load wifi driver
diabl0w said:
ive downgraded radio from 4.4 to 4.2 in the past, but it messed up wifi somehow... isnt wifi part of the modem image? anyways, nothing else bad happened so idk if this is useful info
Click to expand...
Click to collapse
It looks like radio is just a collection of the modem images, so that should eliminate some of the commands. I'll update the OP.
firstEncounter said:
It looks like radio is just a collection of the modem images, so that should eliminate some of the commands. I'll update the OP.
Click to expand...
Click to collapse
check my edit
diabl0w said:
check my edit
Click to expand...
Click to collapse
Radios won't be compatible across ROM versions. You would flash the 4.4.4 radio if downgrading to a 4.4.4 image, not while running 5.1.
Ummmmm. Is this a dream? Someone pinch me...... There's no one around....... Can this really be true!? I'm afraid to try it and bork everything.
firstEncounter said:
This is only for devices currently on 4.4, requires moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Files:
5.1 upgrade images
Stock 5.1 system image
Rooted 5.1 system image
After extracting the 5.1_images_v2.zip, run the following commands to prepare your phone for a 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot erase ddr
(Commands based on this post. Thanks @mikeoswego and @JulesJam!)
Then use mofo to flash the system image of your choice.
Xposed and Adblock images coming soon.
Click to expand...
Click to collapse
Why aren't you flashing 5.1 recovery?
JulesJam said:
Why aren't you flashing 5.1 recovery?
Click to expand...
Click to collapse
Missed that command in the OP. Thanks!
Is the rooted image debloated
Sent from my XT1254 using Tapatalk
JulesJam said:
Why aren't you flashing 5.1 recovery?
Click to expand...
Click to collapse
So we should do that command as well?
janitorjohnson said:
So we should do that command as well?
Click to expand...
Click to collapse
I had trouble when I tried to stay on 5.0 recovery after I flashed 5.1 system image on my MX14.
JulesJam said:
I has trouble when I tried to stay on 5.0 recovery after I flashed 5.1 system image on my MX14.
Click to expand...
Click to collapse
Is that the final command?
trikotret said:
Is the rooted image debloated
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
No, it's completely stock with SuperSU installed.
janitorjohnson said:
Is that the final command?
Click to expand...
Click to collapse
I do
logo
boot
recovery
radios
But I do that b/c that is the way they are usually written in the scripts that come with the images. I think the only 2 where the order really matters is the bootloader and partition table and you aren't flashing those.
---------- Post added at 05:18 AM ---------- Previous post was at 05:16 AM ----------
firstEncounter said:
No, it's completely stock with SuperSU installed.
Click to expand...
Click to collapse
I went ahead and made one too just in case there were any issues with FirstEncounter's since I already have a device set up to do this anyhow.
https://www.dropbox.com/s/rmuev8agm5wl2lh/XT1254_5.1_root_system_ext4.zip?dl=0
PLMK if there are any issues with my image. I will take it down once people have started to modify the images, test them and are sure there are no issues.
It should be easy for someone to modify the buildprop so you can have free tether.
works like a charm
firstEncounter said:
This is only for devices currently on 4.4, requires moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Files:
5.1 upgrade images
Stock 5.1 system image
Rooted 5.1 system image
After extracting the 5.1_images_v2.zip, run the following commands to prepare your phone for a 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot erase ddr
Then use mofo to flash the system image of your choice.
Xposed and Adblock images coming soon.
Click to expand...
Click to collapse
Followed instructions to a T and used OP's files... Everything works like a charm and is buttery smooth: http://imgur.com/ZwIRB8X
Bootloader acted a little weird, got a couple screen flickers... not sure if related or not. It worked itself out after one or two reboots. Thanks for the awesome instructions!
Just updated the OP with a patch for Xposed, ad blocking, busybox and tethering. Let me know if it works for everyone.
firstEncounter said:
Just updated the OP with a patch for Xposed, ad blocking, busybox and tethering. Let me know if it works for everyone.
Click to expand...
Click to collapse
Thank you! You are working mighty quickly I must say. We all really appreciate it!
I can not seem to boot it to recovery after doing the steps in OP. Little man blinks and says "no command" under him. Wanted to do a factory reset after the steps in OP. Any ideas? I am letting it boot into LP for the first time and then will try to get into recovery to do the reset.
After I let LP boot up, I could enter into recovery and factory reset without a problem.
I take no credit for this, thank the Motorola-Firmware-Team on Android File Host, and you can follow any leaked firmware on their Twitter feed.
I no longer have a Moto X Pure Edition, so I can't personally vouch for this firmware, but it seems like it is a totally legit full factory firmware image of Nougat NPH25.200-22 for flashing in fastboot.
This is the "official" full factory image of Nougat NPH25.200-22 and NOT the OTA file. It can be used for a clean flash and to relock the bootloader which is recommended to pass SafetyNet API checks if you are planning on staying stock and not rooting.
Flashfile.xml shows: version="clark_retus-user 7.0 NPH25.200-22 21 release-keysM8992_1255331.29.01.88.09R", MD5 matches, and all dates are correct.
This is ONLY for the Moto X Pure Edition, Retail US (RETUS) variant. I have no information on any other firmware or device.
Tested and verified as official Nougat factory ROM image by @Andromendous
This image is NOT flashable in TWRP, like all factory images it is flashed with fastboot in the bootloader... How to flash:
Code:
fastboot oem lock begin (if wanting to re-lock bootloader, othewise use `fastboot oem fb_mode_set`)
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 system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
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 lock (only if you used `fastboot oem lock begin`, otherwise end with `fastboot oem fb_mode_clear`)
fastboot reboot
See https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 for detailed instructions
Downloads
Original source: https://androidfilehost.com/?fid=889964283620765304
Google Drive mirror: [removed]
@acejavelin: Since you have been one of the guru's on this phone, can this file be flashed in fastboot directly if I am on stock MM android December update rooted with Magisk and TWRP installed? I just want to make sure that when I am ready to take the plunge, I can take the minimal work procedure since I factory wipe after all major updates anyway.
Does this mean people who haven't received 7.0 OTA can flash this ROM and get Nougat without any complications such as corrupted bootloader and stuff? Also read multiple times that downgrading to 6.0 and again upgrading to 7.0 via OTA corrupts the bootloader leading to hard brick (which is now solver using external SD), will flashing this would solve this too?
Yes... This is the pure stock factory image for Nougat, it can be flashed, used to lock the bootloader, fix the "preflash validation" issues, etc. like any factory image.
There should be no issue applying it over a downgraded version, as long as you flash the entire image.
acejavelin said:
Yes... This is the pure stock factory image for Nougat, it can be flashed, used to lock the bootloader, fix the "preflash validation" issues, etc. like any factory image.
There should be no issue applying it over a downgraded version, as long as you flash the entire image.
Click to expand...
Click to collapse
Great! I plan on holding on to this phone for about another 6 months or so and might as well get the update. Will probably go over to stock nougat in December. Custom ROMs just always seem to have at best some minor issue(s) that prevents me from sticking with them.
Dude Ace you are the f-ing man. Thanks for the find.
I flashed it manually while on Hashbangs LOS rom. I was stuck on 6.0 modem and tried to just flash the modem, which made me lose sim service. I then flashed the entire imagine manually and booted just fine.
Now I'm back to LOS with 7.0 modem and so far so good. Hashbang is doing a great job, he's already cleaned multiple bugs just today.
i am already on 7.0 but putting this away for the future. Can you flash the zipped XML or do you need to unzip and flash each piece individually? Thanks.
schneid said:
i am already on 7.0 but putting this away for the future. Can you flash the zipped XML or do you need to unzip and flash each piece individually? Thanks.
Click to expand...
Click to collapse
It's a factory image... Have to flash each piece manually with fastboot, this is not a flashable TWRP or other recovery image
So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.
andromobilogy said:
So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.
Click to expand...
Click to collapse
We don't know that for sure... NPH25.200-22 is what has been rolling out to Sprint, T-Mobile, and AT&T devices, but it seems that Verizon users are getting NPH25.200-23 according to one verified (via screen shot) report on Lenovo's official forum.
The issue is we know the Moto OTA server keeps track of what device get's what version, if you flash this it won't know you have it so if a future OTA update comes out, you might be offered it via push and will have to wait until it's available by pull.
andromobilogy said:
So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.
Click to expand...
Click to collapse
Yes. There's a huge difference. With this you wont brick your phone.
Can we Re-lock bootloader with this version?
AND...
If you flash this version NPH25.200-23, will you still be able to install a SIM from another carrier, say Sprint, T-Mobile, or AT&T, and not be pigeon holed into a specific wireless Plan from VZW with their own Propietary APPs like VZW Cloud?
CLETjB said:
Can we Re-lock bootloader with this version?
AND...
If you flash this version NPH25.200-23, will you still be able to install a SIM from another carrier, say Sprint, T-Mobile, or AT&T, and not be pigeon holed into a specific wireless Plan from VZW with their own Propietary APPs like VZW Cloud?
Click to expand...
Click to collapse
Yes, you can relock... unless you have already applied NPH25.200-23, otherwise you should be able to relock from ANY version out there currently.
We don't know what's up with NPH25.200-23 for sure though... recently Moto has been doing "different" versions for Verizon users that don't seem to get to anyone else, we also see it in the Moto G5+, and we don't know the differences either. Most likely it's just a minor VZW specific change and can be ignored. If the update does get pushed later, you should have no issues taking the OTA update when on this firmware, it is the official factory image.
@ acejavelin
I know that I'm a bit OT, but I think that this thread is the most suitable for my request: do you know if there is a nougat factory image available also for the xt1572?
Thanks in advance,
Gaetano.
Inviato dal mio XT1572 utilizzando Tapatalk
ghitus said:
@ acejavelin
I know that I'm a bit OT, but I think that this thread is the most suitable for my request: do you know if there is a nougat factory image available also for the xt1572?
Thanks in advance,
Gaetano.
Inviato dal mio XT1572 utilizzando Tapatalk
Click to expand...
Click to collapse
As I stated in the first post... no, I have idea or information about any other images for other variants and I suggest following MotoFirmware123 on Twitter as that is the best place to find leaked firmware. Motonovo has gotten very tight on letting firmware get out, but if it becomes available this is likely where it will come from, IF it ever gets leaked.
Just curious. I recently moved on to a Note 8 and want to give my son my Moto X Pure. Does this file put default recovery on the phone as well? I tried to factory reset it last night (had it rooted with TWRP installed) and now it will only boot into TWRP. I just want it all stock for him.
Thanks
Oaklands said:
Just curious. I recently moved on to a Note 8 and want to give my son my Moto X Pure. Does this file put default recovery on the phone as well? I tried to factory reset it last night (had it rooted with TWRP installed) and now it will only boot into TWRP. I just want it all stock for him.
Thanks
Click to expand...
Click to collapse
Yes, it is an official stock firmware image... if properly flashed with fastboot it will restore the device to 100% factory conditions, including recovery.
acejavelin said:
Yes, it is an official stock firmware image... if properly flashed with fastboot it will restore the device to 100% factory conditions, including recovery.
Click to expand...
Click to collapse
Thank you. His phone is now ready.
Finally !Thanks, man!
Now I just flash via fastboot and avoid all the OTA updates process.
you are the man!
So I flashed lineage os 14.1 (20180105 nightly) on my moto g3(osprey) and now whenever someone calls me or I call them, they hear their own voice as an echo while I have no problem hearing anything.
Can anyone tell me what the problem might be and how I can fix it please ?
Yes same thing is happening with me ,eco on caller side on latest nightlies
Well, my friends can hear 'double' sounds, kind of reverberation I think, but only when on Loudspeaker mode.
I am using a modified mixer_paths.xml for stereo output (but I didn't touch mic values) from 5/6th jan build. At first I thought I had messed up, but now it seems it's something in ROM/kernel.
Have you tried flashing squid kernel and then testing? The custom kernel had a fix for low call & media volume, so maybe it fixes up the current issue ?
Sent from my MotoG3 using Tapatalk
Gravemind2015 said:
Well, my friends can hear 'double' sounds, kind of reverberation I think, but only when on Loudspeaker mode.
I am using a modified mixer_paths.xml for stereo output (but I didn't touch mic values) from 5/6th jan build. At first I thought I had messed up, but now it seems it's something in ROM/kernel.
Have you tried flashing squid kernel and then testing? The custom kernel had a fix for low call & media volume, so maybe it fixes up the current issue ?
Click to expand...
Click to collapse
I tried the squid kernel but the issue still exists. Any ideas how to fix this ?
Marzipan Outlaw said:
I tried the squid kernel but the issue still exists. Any ideas how to fix this ?
Click to expand...
Click to collapse
Currently I'm on 19th Jan build (dirty flashed over 5th Jan) with Ultradevs 7.0 kernel. The sound appears fine now. Hope it helps.
Sent from my MotoG3 using Tapatalk
Gravemind2015 said:
Currently I'm on 19th Jan build (dirty flashed over 5th Jan) with Ultradevs 7.0 kernel. The sound appears fine now. Hope it helps.
Click to expand...
Click to collapse
Still doesn't work. I'm now on 26th Jan build and with Ultradevs 7.0 kernel. Help !!!
Marzipan Outlaw said:
Still doesn't work. I'm now on 26th Jan build and with Ultradevs 7.0 kernel. Help !!!
Click to expand...
Click to collapse
Try replacing your mixer_paths.xml with the one attached in TWRP. You can backup your current setup and try with a clean install to ensure that it's used correctly. I had modified this file to enable stereo output so please bear with that
Sent from my MotoG3 using Tapatalk
Gravemind2015 said:
Try replacing your mixer_paths.xml with the one attached in TWRP. You can backup your current setup and try with a clean install to ensure that it's used correctly. I had modified this file to enable stereo output so please bear with that
Click to expand...
Click to collapse
Tried this, still doesn't work.
Is there any chance that this might be a hardware error ?
Marzipan Outlaw said:
Tried this, still doesn't work.
Is there any chance that this might be a hardware error ?
Click to expand...
Click to collapse
It could be. If the same happens with the stock rom, then it's either your carrier or the phone hardware.
Sent from my MotoG3 using Tapatalk
I have the same problem 19/1/18 update even in 26/1/18 update.
I tried the 02/02/18 build and everything seems to be working fine now. Hope it helps
Thanks
help
Marzipan Outlaw said:
I tried the 02/02/18 build and everything seems to be working fine now. Hope it helps
Thanks
Click to expand...
Click to collapse
Where I can get 02/02/18 build? can you please provide a link?
I have same problem. This issue is not in stock 5.1 ROM. but in stock 6.0 and stock 6.0.1 ROM, this echo problem is present. Any solution for this?
stock 5.1 ROM didn't have echo problem. But I can't get volte working in stock ROM 5.1 anymore on my XT1550. Any help please?
Finally I solved the echo problem in my XT1550 2GB phone.
------------------------------
FINALLY WORKING (echo problem SOLVED):
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Download XT1550 5.1.1 stock firmwares
5.1.1 (build 47 ) = Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA-INDIA_DS_2GB_5.1.1_LPI23.72-47_cid7 (Mirror #1)
5.1.1 (build 47.4 )= Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-47.4_cid7
5.1.1 (build 65 ) = Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7 (Newer Build)
Steps I followed:
wipe/reset
install 5.1.1 (build 65)
install 5.1.1 (build 47)
Wipe/reset
modem firmware alone from OS5.1.1 (build 47.4)
Wipe/reset
modem firmware alone from OS5.1.1 (build 65), all other commands below in https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
(my guess is probably wipe/reset before modem firmware alone from OS5.1.1 (build 65) is the solution!)
Hope it helps someone.