[IMG][5.0.2][Lollipop]RETCN XT1085 LXE22.92-18 - X 2014 General

The IMG is made for Moto X 2nd Gen sold in China mainland aka " XT1085" which was released a week ago. Major retailers in China have started to sell since Feb 5.
I can confirm the system also works well on my XT1095 pure edition,however Moto engineers have removed almost all of the google apps and services and implemented some key features with native chinese apps,like Moto Voice. Most of the bloatwares can be easily removed except a security app of lenovo and a voice assistant named Linxi.
You can get the full IMG from a mirror server in china or file factory
Mega
md5sum: 95306D8D80B1F60285E14D2A6FD7F4F0
XT1095 pure edition users can flash the boot.img and system.img via Fastboot utility.(1.Please backup your data before doing this!
2. Just flash the boot.IMG and all system image chunk files. Don't flash other partitions especially GPT and Bootloader,otherwise you would upgrade BL to 0x6012.)
As the Google apps, we can find many flashable zips in the forum,like @TKruzze's PA Gapps packages.

This work in xt1097? And how about root?

xarcom said:
This work in xt1097? And how about root?
Click to expand...
Click to collapse
It should work since there is almost no big difference in android system between 1095 and 1097. However, you should unlock BL first.
As the ROOT, chainfire's CF-Auto-ROOT image still works or you can flash TWRP recovery to your device via fastboot, and flash the root binaries from within TWRP.

I downloaded but how install? Sorry i'm noob , i have unlock bl

xarcom said:
I downloaded but how install? Sorry i'm noob , i have unlock bl
Click to expand...
Click to collapse
0.Backup your personal data.
1.Unzip the image.
2.Put your phone in AP fastboot mode.
3.fastboot flash boot boot.img
4.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
5.fastboot -w
6.fastboot reboot

Does the Moto Voice works in other languages? Also the system is all in Chinese or we can change it to English or in my case Spanish.? Thanks.
Auto reply
Nop, the moto voice is not working with any language besides chinese, what I did was to uninstall via Titanium the moto voice, reboot and install the normal apk and everything is great now

No google stuff so battery life must be better than the stock rom we use
About 5.0.2, maybe a fix for the memory leak bug is included?

alexfiorani said:
No google stuff so battery life must be better than the stock rom we use
About 5.0.2, maybe a fix for the memory leak bug is included?
Click to expand...
Click to collapse
5.0.1 has fixed the memory leak bug.

purejoy said:
5.0.1 has fixed the memory leak bug.
Click to expand...
Click to collapse
Memory bug is still present
And Google knows about it
They are set to fix it in 5.1.

I noticed the same thing. Memory leak bug still present, though things did seem better (maybe placebo). Eventually background apps started closing out on me as often happens when using stock 5.0.
---------- Post added at 01:02 AM ---------- Previous post was at 12:48 AM ----------
@purejoy I'm curious how you knew flagging this to our pure edition phones was safe. Someone just posted images for 5.0.2 on US Cellular, and I was thinking of giving it a try. Thoughts?
http://forum.xda-developers.com/showthread.php?t=3032735

mercado79 said:
I noticed the same thing. Memory leak bug still present, though things did seem better (maybe placebo). Eventually background apps started closing out on me as often happens when using stock 5.0.
---------- Post added at 01:02 AM ---------- Previous post was at 12:48 AM ----------
@purejoy I'm curious how you knew flagging this to our pure edition phones was safe. Someone just posted images for 5.0.2 on US Cellular, and I was thinking of giving it a try. Thoughts?
http://forum.xda-developers.com/showthread.php?t=3032735
Click to expand...
Click to collapse
The hardware architecture is almost the same except communication modules and many 1095 users in China have been testing it since the IMG was released.
As the 1093's firmware, we can just flash the kernel and system partitions. The android system should work.

purejoy said:
The hardware architecture is almost the same except communication modules and many 1095 users in China have been testing it since the IMG was released.
As the 1093's firmware, we can just flash the kernel and system partitions. The android system should work.
Click to expand...
Click to collapse
After I flash this version, I cannot go back to the official 5.0 because i think the firmware is not good at all. When I trying to restore it to the original one, I found that I cannot boot. I've tried every firmware that I can find for XT1095.

zhangyang_haha said:
After I flash this version, I cannot go back to the official 5.0 because i think the firmware is not good at all. When I trying to restore it to the original one, I found that I cannot boot. I've tried every firmware that I can find for XT1095.
Click to expand...
Click to collapse
check if the system is flashing good, sometimes the fastboot commands says system ok, but your phone will prompt a message error

juliospinoza said:
check if the system is flashing good, sometimes the fastboot commands says system ok, but your phone will prompt a message error
Click to expand...
Click to collapse
each time i flash, it says that the image is too large. I tried different times but it doesnt work

zhangyang_haha said:
each time i flash, it says that the image is too large. I tried different times but it doesnt work
Click to expand...
Click to collapse
Same is happening to me, I dont know if is my computer or something, but one question, when you are trying to flash the new version are you flashing all the files or only the system.img? because In my case the (partial) solution was to flash motoboot.img, wich is the bootloader version, and then all the other files... I said partial because I am in one ROM I dont want. Maybe later at home will check with other PC, this is 8.1 and the one at home is 7.

juliospinoza said:
Same is happening to me, I dont know if is my computer or something, but one question, when you are trying to flash the new version are you flashing all the files or only the system.img? because In my case the (partial) solution was to flash motoboot.img, wich is the bootloader version, and then all the other files... I said partial because I am in one ROM I dont want. Maybe later at home will check with other PC, this is 8.1 and the one at home is 7.
Click to expand...
Click to collapse
OK, I've found the problem. We can never flash back to the official 5.0 again because Motorola update the bootloader in the chinese version. It is impossible to downgrade the bootloader version. It happened the same thing when I used Milestone 2.

zhangyang_haha said:
OK, I've found the problem. We can never flash back to the official 5.0 again because Motorola update the bootloader in the chinese version. It is impossible to downgrade the bootloader version. It happened the same thing when I used Milestone 2.
Click to expand...
Click to collapse
Flashing back to the original is no problem. Flash all files except for the bootloader and you'll be fine.

zhangyang_haha said:
OK, I've found the problem. We can never flash back to the official 5.0 again because Motorola update the bootloader in the chinese version. It is impossible to downgrade the bootloader version. It happened the same thing when I used Milestone 2.
Click to expand...
Click to collapse
we have to wait till some 5.0.2 version is released, in the meanwhile the OP should warn all the users about upgrading the bootloader
thanks

Steve-x said:
Flashing back to the original is no problem. Flash all files except for the bootloader and you'll be fine.
Click to expand...
Click to collapse
except for the boot loader? Do you mean that motoboot.img?

zhangyang_haha said:
except for the boot loader? Do you mean that motoboot.img?
Click to expand...
Click to collapse
Don't flash the bootloader partition otherwise you would upgrade BL to 0x6012. Just flash the boot.IMG and all system image chunks.

Related

[ROM]KITKAT][4.4.4][XT1068] Stock Android 4.4.4 Easy Installer

If your XT1068 is the later version (came from factory with 5.0.2 -it has toshiba front cam) Kitkat will work BUT you will LOSE use of front cam as kitkat has no drivers for this
4.4.4 KITKAT XT1068 Easy Installer
Simple quick Installer of firmware via fastboot
the 4.4.4 Retaildsdsall (GLOBAL) firmware
YES IT CONVERTS UK (GB) PHONES
this is STOCK firmware with no mods,
So Will receive ALL Future OTA updates
and installs over ANY version of 4.4.4 /5.0.x / Custom Rom
(does not check - just flashes regardless of version)
by Auto Restore Script​
Requires Windows 7/8/10 to run script
WARNING READ THIS!​
MAKE A FULL BACKUP OF PHONE
via play and TWRP or your favorite method. DO NOT SAVE TO PHONE save to pc and a flash drive
(2 copies - cover yourself)
Try to have Battery over 70% charged - 50% OK under 30% DANGER
This flashes back STOCK UNTOUCHED files inc, GPT, modem, boot, recovery, bootloader, system etc etc (basically only your external SD card is left alone!!)
CLEAN FLASH ONLY, so do a
Full factory Reset / wipe required before installation
from phone backup & reset in settings
YOU can HANG / KILL your phone if IGNORED
-- USE @ OWN RISK --
DOWNLOAD
Kitkat 4.4.4
.14 .23 .27 versions (global) + UK (GB) .23 + DE (German) .14
stock firmware + installer AIO
+ INSTRUCTIONS​
Download and save to PC / laptop / desktop - DO NOT save the Download to phone or SD Card​
A) Firmware KXB21.85.14 (earliest version) https://mega.co.nz/#!mo8wnRJI!APkjY2f_bk-HB2JFBCoWh5rmPvltqCzgTQjQf1t-MHQ
B) Firmware KXB21.85.23 (DSDS ALL) https://mega.co.nz/#!Kkc31L4A!JLtksSioP_xnOZ6m3CR570o9Dxm7LbPgEF2gnkDF_TI
C) Firmware KXB21.85.27 (latest version) https://mega.co.nz/#!CltVzboY!etSjBHqKdMrQTYsh1LcsdMj9S3McG7gkfXRMI7WYPJQ
D) Firmware KXB21.85.23 - GB Region (UK) https://mega.nz/#!yotQhYjK!w0FcxKw1s6w4Ro125mwAvxcoPywnVso8Fa5BihW2Z3k
E) Firmware KXB21.85.14 - DE Region (Germany) https://mega.co.nz/#!T10zkTrR!yBTSeScMh2FLbi9GXjf34VRIBHtBsZoKv_XYqdBj9yU​
.
.
V 1.0 Retired
V2.0
Simplified Install method, zip now includes instructions, drivers and all required ADB files
no longer needs USB debugging as done via AP Fastboot flash mode
​
FAQ's
Q1): What exactly is this?
STOCK motorola firmware files, with a added auto restore script, Adb and fastboot, to allow a easy installation.
Q2): What model phone does this work for?
XT1068 , Various Retaildsds firmware, confirmed working on UK (GB), Indian and EU phones NOT for Brazilian XT1068
Q3): What version is this ?
4.4.4 KITKAT version .14 .23 .27 and UK (GB) .23
Q4): Why Must I factory reset /wipe phone?
Simply because your phone will Hang if downgrading, be sluggish and other problems..... if you can flash firmware - you can make back up 1st and reload all you apps and data - Do it right 1st time
thanks for this.....i'll try your tools later, now i'm not able to use pc!!!
Will this restore the Indian Version to stock as well?
If so can I use the all earliest firmware that you have provided or should I download one specific to my region?
arjunpaliath said:
Will this restore the Indian Version to stock as well?
If so can I use the all earliest firmware that you have provided or should I download one specific to my region?
Click to expand...
Click to collapse
A and B should work on ANY XT1068 as it's a Retail for ALL Dual sim, (it may or may not have certain languages) but if you can find your original firmware it's a easy job to add the automated script
My fone came with KXB21.85-23 installed. Noticed big battery drain. Should switch to ART instead of Dalvik?
reefuge said:
A and B should work on ANY XT1068 as it's a Retail for ALL Dual sim, (it may or may not have certain languages) but if you can find your original firmware it's a easy job to add the automated script
Click to expand...
Click to collapse
Thank you. Was able to find my original firmware and restore to stock.
Rexton270 said:
My fone came with KXB21.85-23 installed. Noticed big battery drain. Should switch to ART instead of Dalvik?
Click to expand...
Click to collapse
I'm just leaving mine as is till lollipop comes out as OTA for XT1068
Wait, wouldn't the boot loader message modified prevent this roms from getting otas since it's a change to a file system?
Nagass said:
Wait, wouldn't the boot loader message modified prevent this roms from getting otas since it's a change to a file system?
Click to expand...
Click to collapse
I dont think so as you can still download OTA with modified Roms, but you need Stock recovery to install - but if it worries you edit the .bat script to remove the line with logo2.bin in it near end of script.
if we cant OTA install, but have a OTA zip of Lollipop we can modify it and just flash it via mfastboot method anyway
reefuge said:
I dont think so as you can still download OTA with modified Roms, but you need Stock recovery to install - but if it worries you edit the .bat script to remove the line with logo2.bin in it near end of script.
if we cant OTA install, but have a OTA zip of Lollipop we can modify it and just flash it via mfastboot method anyway
Click to expand...
Click to collapse
I don't know, I'm quite new to Motorola phones but I read in this forum more than once that for OTA updates (atleast for the lollipop one) you must have a completely stock rom, even a frozen system app would make the update fail to install.
Nagass said:
I don't know, I'm quite new to Motorola phones but I read in this forum more than once that for OTA updates (atleast for the lollipop one) you must have a completely stock rom, even a frozen system app would make the update fail to install.
Click to expand...
Click to collapse
I have run 4.4.4 versions .14 .23 and .27 on my xt1068 as well as modded xt1064 5.0 and modded xt1069 5.0.1 , so worst case is All I will be able to run is modded roms, but i'm 99.99% sure that if you have the correct OTA for you Android version on phone there will be a way to upgrade.
reefuge said:
I have run 4.4.4 versions .14 .23 and .27 on my xt1068 as well as modded xt1064 5.0 and modded xt1069 5.0.1 , so worst case is All I will be able to run is modded roms, but i'm 99.99% sure that if you have the correct OTA for you Android version on phone there will be a way to upgrade.
Click to expand...
Click to collapse
Well anyway I just saved all of your packages just in case I'll ever need to restore my UK XT1068 back to stock.
I still have bootloader locked and everything as it came out of the box waiting for 5.0 OTA (of course I'll try to get the link and post it on XDA )
Nagass said:
Well anyway I just saved all of your packages just in case I'll ever need to restore my UK XT1068 back to stock.
I still have bootloader locked and everything as it came out of the box waiting for 5.0 OTA (of course I'll try to get the link and post it on XDA )
Click to expand...
Click to collapse
Lol sometimes wished I had waited for OTA 5.0
hi ,
when I tried to return to stock through bat file , when was the time to writing partition , it says <bootloader>Preflash validation failed .
Has anyone idea why?
nitsos said:
hi ,
when I tried to return to stock through bat file , when was the time to writing partition , it says <bootloader>Preflash validation failed .
Has anyone idea why?
Click to expand...
Click to collapse
is your bootloader unlocked? this method requires UNLOCKED bootloader
Yes,I have bootloader already locked
as of 14/01/2015 firmware B is Accepting OTA zip update (copy to internal memory AND SDCARD ) to Lollipop 5.0.2 from india
bro can you please upload Firmware KXB21.85.23 (DSDS ALL) to google drive as some people are not able to access mediafire??!!

[GPe Lollipop 5.1] 1click Installer - rom, root, twrp [AIO][XT1032]

Google Play Edition Lollipop 5.1
1 Click Installer
Root, Custom Recovery and change Boot Logo All-in-One Pack
Created for personal usage, just share it now for those
who want to upgrade to Lollipop 5.1 from 5.0.1, stock motorola 5.0.2
or custom roms like CM12, ResurrectionRemix, BlissPop, Euphoria OS, etc
The easiest way how to install rom, root, recovery
CONTAINS
GPe 5.1 Lollipop
15 sec Adb Setup for install ADB, Fastboot and Drivers
TWRP recovery 2.8.6.0
SuperSU 2.46
Dark Moto Logo
&
Restore to Default (stock recovery, logo)
USAGE
Download the archive and extract
From "TOOLS" folder run (install) "adb-setup-1.4.2.exe
Reboot your phone to the download mode (power+volume down)
Connect via usb cable to pc
From GPe_5.1_OneClick run (double click on) Flash_GPe_5.1.bat
Wait until it finish, than reboot your phone
ROOT & TWRP
Copy the "UPDATE-SuperSU-v2.46.zip" from ROOT-RECOVERY folder to your virtual sd card
Reboot to the download mode (power+volume down) and connect via usb cable to pc
From ROOT-RECOVERY folder run "flash_recovery.bat"
than select recovery and from installed twrp install "UPDATE-SuperSU-v2.46.zip"
CHANGE BOOT LOGO
Download mode + connected usb cable and from folder Dark_MotoLogo run "flash_logo.bat"
RESTORE BOOT LOGO & STOCK RECOVERY
From "Default" folder run "flash_logo.bat" or "flash_recovery.bat"
DOWNLOAD
GPe_5.1.rar
And as always:
I am not responsible for any trouble that may occure by using this guide, such as your phone exploding, your cat dying... you know.
If you're a noob, ask before doing anything you don't know!
That's what XDA threads are for.
I will do my best to give any support needed.
CREDIT AND THANKS
Google for rom
@qd42 for FileFactory link of GPe 5.1
@Chainfire for SuperSU
TeamWin for TWRP recovery
@caitsith2 for Motorola Boot Logo Maker
@Snoop05 for 15 seconds ADB Installer
​
-reserved- just in case
Good job!
Can I use this installer when my XT1032 is running Blisspop 2.1 (5.0.2) with TWRP already? Or this can be used only on stock non-rooted device.
thx
pnuda said:
Good job!
Can I use this installer when my XT1032 is running Blisspop 2.1 (5.0.2) with TWRP already? Or this can be used only on stock non-rooted device.
thx
Click to expand...
Click to collapse
Yep, you can use it but make a backup from your personal files (videos, pictures, music, etc.) because it'll wipe your data and internal storage.
Do you have UPDATE-SuperSU-v2.46.zip on it's own? I have installed GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip and TWRP as well seperatly but just need to root it. So just need that file not complete ROM
---------- Post added at 11:35 PM ---------- Previous post was at 10:56 PM ----------
error in rom batch file, it's pointing to windows\system32 and failing
also read should use mfastboot not fastboot?
also your mfastboot flash recovery twrp-2.8.6.0-falcon.img is non GPE version when I flash with yours I get vsync like tearing. Flash to twrp-2.8.6.0-falcon_GPE.img and stable screen
Superuser works
Will I have any problem if after flashing this I'll try to flash the stock motorola 5.1 fw when it wii be out?
Hello,
Thanks for taking your time to create this.
I have already updated my moto G 1032 to lollipop 5.1 using a method as shown in the attachment.
Do i need to do the entire process again?
Maybe it's a stupid question but, will this work for the xt1034 version?
To be more specific and avoid future questions like this, does every rom for the xt1032 work for xt1034?
Thank you
Berties123 said:
Do you have UPDATE-SuperSU-v2.46.zip on it's own? I have installed GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip and TWRP as well seperatly but just need to root it. So just need that file not complete ROM
---------- Post added at 11:35 PM ---------- Previous post was at 10:56 PM ----------
error in rom batch file, it's pointing to windows\system32 and failing
also read should use mfastboot not fastboot?
also your mfastboot flash recovery twrp-2.8.6.0-falcon.img is non GPE version when I flash with yours I get vsync like tearing. Flash to twrp-2.8.6.0-falcon_GPE.img and stable screen
Superuser works
Click to expand...
Click to collapse
Ahh buddy, about your errors please read the op carefully. Under thanks you can find links, click on it please and about twrp also. I'm using only official releases not unofficials
BurningKoala said:
Will I have any problem if after flashing this I'll try to flash the stock motorola 5.1 fw when it wii be out?
Click to expand...
Click to collapse
No, you can flash moto 5.1 directly whet it will be out.
reganEZ said:
Hello,
Thanks for taking your time to create this.
I have already updated my moto G 1032 to lollipop 5.1 using a method as shown in the attachment.
Do i need to do the entire process again?
Click to expand...
Click to collapse
Nope, this is only easiest way how to upgrade to 5.1 and contains the whole 5.1 firmware not only the updates.
Hello,
My Moto is XT1032 From Tesco GB retail. Can I use this guide to take 5.1 ? Thanks
Same question. There is no word about bootloader. Does it have to be unlocked?
BlackBoneBla said:
Hello,
My Moto is XT1032 From Tesco GB retail. Can I use this guide to take 5.1 ? Thanks
Click to expand...
Click to collapse
Yes.
Rendoqoz said:
Same question. There is no word about bootloader. Does it have to be unlocked?
Click to expand...
Click to collapse
Of course.
▪◼ Tapatalk ♦ Moto G ◼▪
@ronin790 i have a new Moto G X1032 16GB 4.4.4
what i need do first to apply this?
1.- open bootloader
what's next?
zero995 said:
@ronin790 i have a new Moto G X1032 16GB 4.4.4
what i need do first to apply this?
1.- open bootloader
what's next?
Click to expand...
Click to collapse
Just follow mentioned instructions from op.
▪◼ Tapatalk ♦ Moto G ◼▪
Difference between stock Motorola rom and GPE In battery life and performance?
fer2503 said:
Difference between stock Motorola rom and GPE In battery life and performance?
Click to expand...
Click to collapse
Noone can know that when there is no Moto 5.1 firmware yet.
But i assume that the battery life as well as performance should be almost equal. (If they don't screw it up ...I hope they won't)
Flash_GPE_5.1.bat errors
I'm on Motorola stock 5.02 firmware and I'm getting errors when running Flash_GPE_5.1.bat process. It seems I'm getting error for the following command line:-
fastboot.exe flash partition gpt.bin
fastboot.exe erase cache
fastboot.exe oem fb_mode_clear
Are these errors critical or can I just ignore them.
Factory Reset?
Hi, I'm currently on 5.1 GPe with 41.19 stock Bootloader, no Root, just unlocked BL . I followed a Youtube video and everything runs great BUT.. i can't do factory reset on the device (must be done via fastboot).
Is it possible to Factory Reset with your guide/rom?, if yes... Can I reinstall your ROM over the one I currently have?
Thanks in advance mate. Great Job.
Tomazon said:
Hi, I'm currently on 5.1 GPe with 41.19 stock Bootloader, no Root, just unlocked BL . I followed a Youtube video and everything runs great BUT.. i can't do factory reset on the device (must be done via fastboot).
Is it possible to Factory Reset with your guide/rom?, if yes... Can I reinstall your ROM over the one I currently have?
Thanks in advance mate. Great Job.
Click to expand...
Click to collapse
Don't know the answer but mine does the same having upgraded using this method.
Tomazon said:
Hi, I'm currently on 5.1 GPe with 41.19 stock Bootloader, no Root, just unlocked BL . I followed a Youtube video and everything runs great BUT.. i can't do factory reset on the device (must be done via fastboot).
Is it possible to Factory Reset with your guide/rom?, if yes... Can I reinstall your ROM over the one I currently have?
Thanks in advance mate. Great Job.
Click to expand...
Click to collapse
Sorry, i don't know. You can try it, but maybe something wrong with partitions after 5.0.2.
spikey_w said:
I'm on Motorola stock 5.02 firmware and I'm getting errors when running Flash_GPE_5.1.bat process. It seems I'm getting error for the following command line:-
fastboot.exe flash partition gpt.bin
fastboot.exe erase cache
fastboot.exe oem fb_mode_clear
Are these errors critical or can I just ignore them.
Click to expand...
Click to collapse
Just ignore and reboot. If everything works fine don't care about it.
▪◼ Tapatalk ♦ Moto G ◼▪

Nougat Fastboot flash error with system image [Solved]

Marshmallow factory images never a problem flashing. Ever sense Nougat came along I can not flash the system.img in fastboot without getting the dreaded "error: cannot load 'system.img' ". I've tried the trick by adding the extension to flash smaller chucks of data with the command line.
I used flashfire to update with no problem but this takes all the joy of doing it manually.
I know other users have had this problem also. Did anyone come up with a solution for this problem yet? Thanks.
Solved:
Seems that my Platform-Tools program was not updated as I had thought. I had thought it was a "One Button" update type of program but apparently certain parts or updates need to be updated first then other parts can be updated. So long story short for anyone else having this problem make sure the all updates are applied to Platform-Tools.
Thanks for all the help!
Yes this has happened to me and I was stuck almost. I had to load the system image to a otg and flash it in twrp and that's when it would go.
Have you tried flashing using LxMultiTool
Leeum said:
Have you tried flashing using LxMultiTool
Click to expand...
Click to collapse
I have not tried. I will on next update if I can't find any other fix. I also forgot to mention that I updated all the libs and what not in the Google adb program installed on my PC. Also I used Winrar to decompress the factory image if that makes a difference, it hasn't been a issue in the past with marshmallow.
I suspect you are not running the latest version of platform tools/adb/fastboot. Find the latest version of platform tools and you should be good.
Pig Vomit said:
I suspect you are not running the latest version of platform tools/adb/fastboot. Find the latest version of platform tools and you should be good.
Click to expand...
Click to collapse
Thanks for the info. I did update to platform tools when nougat was released last month, but will check again. I had the same issue then also. I even installed the 7.0 files. Maybe I'm missing something.
As i said, Download LxMultiTool. It has adb and everything. I flashed latest NRD90U 7.0.0 Stock rom without issues. It also lets you lock/unlock bootloader, sideload files, install recovery
How do you load the system image to otg.?
Sent from my HUAWEI MT7-TL10 using XDA Free mobile app
Solved, thanks guys.

After flashing phone changed from G4 Plus to G4

I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
This one
http://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Tried flashing it. No success. Also the fiingerprint reader is also missing.
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
GeeteshKhatavkar said:
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
Click to expand...
Click to collapse
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
sabithmk said:
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
Click to expand...
Click to collapse
Which city ?I think you should go for the replacement and then update it via OTA when you get a notification.
Any Solutions Yet ?
Has anyone found any solutions yet !?
It is surely a Software issue
Service Center people are asking Rs.6500/- to replace the motherboard
Can't even relock the bootloader as i flashed the Nougat OTA and thus i can't downgrade the bootloader and lock it either !!
Please Help !
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
You found any solution?? I am facing the same problem...
bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
I sent it for service and got a free replacement.
bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
Yes I found it..
I created a thread. Check this.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
---------- Post added at 11:38 AM ---------- Previous post was at 11:36 AM ----------
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
Check this link friend. I did it. Was having same problem as you.
Check the thread I created.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
echo92 said:
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
Click to expand...
Click to collapse
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
gioyocho said:
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
Click to expand...
Click to collapse
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
Check my link.
You can even OTA update in future if you installed the latest firmware.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
echo92 said:
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
Click to expand...
Click to collapse
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
gioyocho said:
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
Click to expand...
Click to collapse
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
echo92 said:
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
Click to expand...
Click to collapse
well i tried and did not work those run commands

Final Official Oreo 8.1.0 Release - OPP28.85-16 OTA

I've just captured the Official OPP28.85-16 OTA for retail cedric and I'm posting it here. I'm on retbr channel but this will work on any retail device. If you're on another updated channel, I don't know what would happen if you installed this.
Notice that to install this YOU MUST be on NPPS25.137-93-2-5 to install these, since OTA's are not full firmwares like fastboot files, but instead they're patchings tailored to be applied upon a specific firmare - NPPS25.137-93-2-5 in this case.
Another particular detail is that the OTA file (gotten directly from my credric) lists the Blur Version as Blur_Version.25.361.10.cedric.retail.en.US, but curiously, the fastboot version for the same firmware ( which you can download here) lists it as Blur_Version.28.41.15.cedric.retail.en.US
Someone also reported in another thread that they just sideloaded this upon the Second Soak test. I wouldn't doubt it since this is what should happen to regular soak testers, but if you do it, DO IT AT YOUR OWN RISK
I also won't post instructions on how to install this since they're already available here
Download
Gdrive: https://drive.google.com/file/d/149hrGFpuWUgAvJr02McYNwJVaqSvllYO/view?usp=sharing
That's it.
changelog?
Has anyone already tried it?
Since this is a (Delta) OTA Update that expects NPPS25.137-93-2-5 (Blur_Version.25.361.10) it should be correctly named "block_delta-ota-Blur_Version.25.361.10-28.41.15.cedric.retail.en.US" in my view.
Someone also reported in another thread that they just sideloaded this upon the Second Soak test.
Click to expand...
Click to collapse
I'm on the 2nd soak test update OPP28.85-13.
Just tried to flash the update from SD card and ADB sideload.
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
JoeDoe0 said:
Since this is a (Delta) OTA Update that expects NPPS25.137-93-2-5 (Blur_Version.25.361.10) it should be correctly named "block_delta-ota-Blur_Version.25.361.10-28.41.15.cedric.retail.en.US" in my view.
I'm on the 2nd soak test update OPP28.85-13.
Just tried to flash the update from SD card and ADB sideload.
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
Click to expand...
Click to collapse
seems like it can be updated. from. soak test then, but I never heard nor did I find anything about OPP25. 85-16 build. maybe there was a third soak test and we don't know about it
Works perfect
Hi,
i used the above Image in Germany and i am now on Oreo 8.1
Everything works perfect. First i had a little bit trouble due to an old Version of ADB Tools, but after Update ADB to current Version the Update to Oreo took something around 30min.
Build 28.85-16
Oreo 8.1
Software Channel reteu
Patch Level 01.08.2018
bori321 said:
Hi,
i used the above Image in Germany and i am now on Oreo 8.1
Everything works perfect. First i had a little bit trouble due to an old Version of ADB Tools, but after Update ADB to current Version the Update to Oreo took something around 30min.
Build 28.85-16
Oreo 8.1
Software Channel reteu
Patch Level 01.08.2018
Click to expand...
Click to collapse
On which version you were before update?
Firmware
Hi,
before update to Oreo i flashed NPPS25.137-93-2-5 Firmware and after that the Image from this thread.
Worked perfect.
Alex
I tried to post a Screenshot but it was not possible because i am a new member...
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
Click to expand...
Click to collapse
freeZbies said:
seems like it can be updated. from. soak test then, but I never heard nor did I find anything about OPP25. 85-16 build. maybe there was a third soak test and we don't know about it
Click to expand...
Click to collapse
Update fails from OPP28.85-13 since it expects either OPP28.85-16 which is the latest Oreo build (that I want to update to) or the latest Nougat NPPS25.137-93-2-5.
There is no OPP25. 85-16 build! I think you misread the error message.
BTW I updated from OPP28.85-13 to -16 using the full fastboot version and it worked out perfectly.
JoeDoe0 said:
Update fails from OPP28.85-13 since it expects either OPP28.85-16 which is the latest Oreo build (that I want to update to) or the latest Nougat NPPS25.137-93-2-5.
There is no OPP25. 85-16 build! I think you misread the error message.
BTW I updated from OPP28.85-13 to -16 using the full fastboot version and it worked out perfectly.
Click to expand...
Click to collapse
yeah, I actually misread it, now I see it.
Anyways, flashing it from fastboot doesn't prove anything. but seems like Cedric can be upgraded from the soak test to final version using this ota. Idk because I used fastboot myself too, since I had already modified my system partition.
AsusZenFone3Deluxe said:
changelog?
Click to expand...
Click to collapse
seriously?
stop joking, Motorola doesn't release changelogs.
but I'll try:
updated from nougat to oreo?
duhhh
how is speaker quality in this build ?
because there is some issues in previous oreo builds
Speaker
Hi,
i would say that for my ears the speaker sounds better than it was with Nougat.
After a few days of testing everything works really good and i have not found anything not working or any problems.
Alex
bori321 said:
Hi,
before update to Oreo i flashed NPPS25.137-93-2-5 Firmware and after that the Image from this thread.
Worked perfect.
Alex
I tried to post a Screenshot but it was not possible because i am a new member...
Click to expand...
Click to collapse
how do you get back to NPPS25.137-93-2-5
I followed the steps from this Thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
- Unlocked bootloader (don't know of this is necessary)
- back to NPPS25.137-93-2-5 via the commands from the thread i linked (without the lines:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
)
- via ADB sideload with the Oreo download from this thread to Oreo.
Alex
ahmedAZ said:
how is speaker quality in this build ?
because there is some issues in previous oreo builds
Click to expand...
Click to collapse
In my experience the quality is better than on previous oreo builds.
ahmedAZ said:
how do you get back to NPPS25.137-93-2-5
Click to expand...
Click to collapse
if you have an unlocked bootloader download NPPS25.137-93-2-5 Flashable Zip here and flash it with twrp
bori321 said:
I followed the steps from this Thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
- Unlocked bootloader (don't know of this is necessary)
Alex
Click to expand...
Click to collapse
to flash official Motorola files there's no need to unlock the bootloader.
you've just unnecessarily voided your warranty
@freeZbies
Hey is that twrp stock rom (137-93-2-5) the only thing we need to flash before going for the ota ? Cause I've been told that we needed to be on a completely unmodified system partition in order to receive the ota. In that case just flashing twrp stock wouldn't be sufficient right?
https://forum.xda-developers.com/g5...o-official-stock-oreo-8-t3823598/post77713117
Chekm8Qc said:
@freeZbies
Hey is that twrp stock rom (137-93-2-5) the only thing we need to flash before going for the ota ? Cause I've been told that we needed to be on a completely unmodified system partition in order to receive the ota. In that case just flashing twrp stock wouldn't be sufficient right?
https://forum.xda-developers.com/g5...o-official-stock-oreo-8-t3823598/post77713117
Click to expand...
Click to collapse
I dont know if the twrp version would be valid. To apply an OTA, your system must matchbit by bit, so the most guaranteed way is to flash that firmware via fastboot, but you could try flashing the twrp version, and in case it works, you could post the results here.
just dont forget that if the ota fails youll soft brick ur phonr and will only be able to recover it via fastboot
freeZbies said:
I dont know if the twrp version would be valid. To apply an OTA, your system must match stick bit by bit, so the most guaranteed way is to flash that firmware via fastboot, but. you could try flashing the twrp version, and in case it. woeks you could post the results here.
just dont forget that if the ota fails youll soft brick ur phonr and will only be able to recover it via fastboot
Click to expand...
Click to collapse
Thanks I'll keep that in mind
Being soft bricked,, wouldn't I be able to use twrp still? Like to flash a valid rom or one of my backups?
Anyways I can't really try it that way since the update hasn't come to me yet I'm on software channel Retca.
Edit : right I forgot that I could just use the official ota available here if I would like to test it.
Chekm8Qc said:
Thanks I'll keep that in mind
Being soft bricked,, wouldn't I be able to use twrp still? Like to flash a valid rom or one of my backups?
Anyways I can't really try it that way since the update hasn't come to me yet I'm on software channel Retca.
Edit : right I forgot that I could just use the official ota available here if I would like to test it.
Click to expand...
Click to collapse
being soft bricked doesnt necessarily mean you can recover it through twrp. OTA's are different of twrp flashables in that it modifies things beyond system partition. I've seen reports from people with other motorola devices who applied an OTA while having a modified system partition, and even though they were able to boot to twrp, flashing a custom Rom or restore a backup wouldn't make the phone boot. Their phones weren't hard bricked, but still they had to fastboot to recover their phones. Anyways, why don't you flash the Twrp flashable if, it's already available (considering you have an unlocked bootloader).
I'm case you have a locked bootloader you may fastboot without executing "fastboot erase userdata" in case you want to try. I did it without losing my data (although I was already in Opp 28.85-16)
but after all I really advice you to flash the twrp zip if u can

Categories

Resources