Related
Disclaimer
What's posted here is tested before sharing
but if something bad happens, it's not my problem.Originally posted @MotoModTR by »CanERYVZ« to restore the stock firmware of any XT1033 converted to XT1032 GPE 4.4.2 with deej_roamer's instructions posted here,then OTA'd to GPE 4.4.4. I'm just sharing, all credits to »CanERYVZ« :good:
Your device will be restored to XT1033 Asia.retail 4.4.2 successfully
TESTED and WORKS for XT1033 Asia Retail Dual-Sim version.
1- Download 4.4.2 stock version for your device RETAIL-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml.zip
1a- Extract firmware to c:\retail
2- Download stock OTA 4.4.4 file for XT1033 Blur_Version.171.44.31.falcon_umtsds.AsiaRetail.en.03.zip
2a- Extract just the 3 files "gpt.bin", "logo.bin" and "emmc_appsboot.mbn" to c:\retail and overwrite the old ones.
3- Download mfastboot-adb.rar
3a- Extract mfastboot-adb.rar to c:\retail
4- Open CMD (command prompt) and go to C:\retail (type cd c:\retail in cmd)
Note: you need to run command prompt as administrator.
4a- Type the following commands one by one:
Code:
mfastboot flash aboot emmc_appsboot.mbn
mfastboot flash partition gpt.bin
mfastboot reboot-bootloader
mfastboot getvar max-sparse-size
mfastboot oem fb_mode_set
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot oem fb_mode_clear
mfastboot reboot
5- Go to stock recovery. Wipe data / factory reset and wipe cache for a clean start.
ps : motoboot partition will result error because we don't have it in the moto 4.4.4 ota file, just don't worry and continue. :good:
Greetings. :highfive::good:
So, this will restore the mobile from GPE to Stock 4.4.4 with dual sim capability ?
When does the android s friends
No,
This will restore XT1033 from GPE 4.4.4 to Moto 4.4.2 , but if you like you can OTA to Moto 4.4.4.
When does the android l friends
Awesome, but i have a question.
Some people just take the gpt.bin, replace it to 4.4.2 firmware pakage and flash without flashing motoboot.img.then ok.
Some people take logo.bin too.
But i did not see anyone take the emmc_appsboot.mbn. can u explain what is emmc_appsboot.mbn
Sorry for being noob.
Btw, how many devices did u test?
Sent from my SM-G900F using Tapatalk
@windylawyer.1712,
Hi,
i need to say that i'm a noob when it comes to qualcomm platform but after a little research in google, i got some results and to my understanding ;
emmc_appsboot.mbn which is flashed into aboot partition keeps information about the emmc file system structure. So what's aboot partition ? I'll quote from Master Dan Rosenberg here.
aboot loads the kernel and ramdisk into memory at the addresses requested by the boot image header, and then signature validation is performed after this loading is complete. Because the boot image header is read straight from eMMC flash prior to any signature validation, it contains essentially untrusted data. As a result, it's possible to flash a maliciously crafted boot image whose header values cause aboot to read the kernel or ramdisk into physical memory directly on top of aboot itself!
Click to expand...
Click to collapse
Other methods that i've seen without the " emmc_appsboot.mbn " flashing step, seems to halt the phone on startup and returns to bootloader menu, then you need to press Normal Powerup to boot the device.
However the method in OP, the phone just boots fine. Hope this helps and if there's something to be corrected, i'd be more than happy to learn something new.
fatihtpr said:
When does the android l friends
Click to expand...
Click to collapse
Hello fatih,
I think XT1032 GPE will get Android L after a month for the Nexus Line. XT1033 or XT1032 moto editions might get it about 3 months...
Semseddin said:
Hello fatih,
I think XT1032 GPE will get Android L after a month for the Nexus Line. XT1033 or XT1032 moto editions might get it about 3 months...
Click to expand...
Click to collapse
Hello şemseddin thank for as ne.
What is the difference between xt 1033 xt1032 and wonder?
fatihtpr said:
Hello şemseddin thank for as ne.
What is the difference between xt 1033 xt1032 and wonder?
Click to expand...
Click to collapse
Xt1032 is one sim version.
Xt1033 is dual sim version
Gửi từ GT-N7105 của tôi bằng cách sử dụng Tapatalk
Thanks windylawyer
Thanks OP...
THANKS!!!
thank youuu good sir! this is total life saver!!
Preflash validation failed
I have got a 1032. Used to have GPE, installed as 4.4.2, OTA upgraded to 4.4.4.
I want to get back the Motorola ROM, 4.4.2, or 4.4.4.
When I tried, I got a few "Preflash validation failed" errors, bootloader complains: "version downgraded for xxx". After the "downgrade" I have got just bootloader and recovery. No sstem can be booted/installed.
I have also tried this script (first few steps), but I have got the same errors for the first 2 commands
Tried with 4.4.2 and 4.4.4 xml.zip versions as well.
Code:
mfastboot flash aboot emmc_appsboot.mbn
mfastboot flash partition gpt.bin
mfastboot reboot-bootloader
mfastboot getvar max-sparse-size
mfastboot oem fb_mode_set
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot oem fb_mode_clear
mfastboot reboot
... and after the whole thing ran, boot process stops in logo (bootloader is open blahblahblah...)
bootloader / recovery can be started, nothing more.
is this method working successfully??
jbanti said:
is this method working successfully??
Click to expand...
Click to collapse
Yes
can i ota after following this procedure to restore to xt1033 firmware?
pfufle said:
can i ota after following this procedure to restore to xt1033 firmware?
Click to expand...
Click to collapse
YES... u can its fully Stock
Sent from my XT1033
Bootloader unlocked flashing and stuck
Semseddin said:
@windylawyer.1712,
Hi,
i need to say that i'm a noob when it comes to qualcomm platform but after a little research in google, i got some results and to my understanding ;
emmc_appsboot.mbn which is flashed into aboot partition keeps information about the emmc file system structure. So what's aboot partition ? I'll quote from Master Dan Rosenberg here.
Other methods that i've seen without the " emmc_appsboot.mbn " flashing step, seems to halt the phone on startup and returns to bootloader menu, then you need to press Normal Powerup to boot the device.
However the method in OP, the phone just boots fine. Hope this helps and if there's something to be corrected, i'd be more than happy to learn something new.
Click to expand...
Click to collapse
please somebody help.....after doing all this my screens blink with logo of BOOTLOADER UNLOCKED........and when i go to the fastbootboot and connect usb it now doesnt recognize it........plz help me save my moto g....plzzzzzzzzzzzzzzzz
I am Starting this with a very simple reason that the filefactory link for the Firmware which is the only link currently available right now is a crapy link. The download failed six times before i could finally download it. :highfive:
Downloads:
1.http://goo.gl/5aVzPE [Dev-Host]
2.http://goo.gl/JsWtVE [Mirror]
Pre-Requisite:
1.http://goo.gl/Wl50A3
Instructions 4.4.4:
1. Download 4.4.4 and Extract it to a folder
2. Download mfastboot-v2 and Extract it into the same folder [mfastboot Download: http://goo.gl/lTYq4F]
3. Reboot the phone into Bootloader
4. Run Following commands from the Command Prompt after cd-ing to the folder, one by one
If you do not wish to lock bootloader skip 4.1 and 4.3
4.1
Code:
mfastboot.exe oem lock begin
4.2
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
4.3
Code:
mfastboot.exe oem lock
4.4
Code:
mfastboot.exe reboot
New 4.4.4 Software Update Is Available [Build KXB21.85.23]
Code:
Model number: Moto G (2nd Generation)
Android version: 4.4.4
Baseband version: MSM8626BP_1032.394.88.00R,EMEA_DSDS_CUST
Kernel version: 3.4.42-g668a77b [email protected] #1 Tue Aug 26 20:30:04 CDT 2014
System version: 21.11.23.titan_retaildsds.retaildsdsall.en.03 retin
Build number: KXB21.85-23
Instructions New 4.4.4 Update:
IF you are restoring to complete stock prefer the above method to go 4.4.4 method below is obsolete
1. Download The Firmware Package: http://goo.gl/NoKvOu
2. Copy this file into the root of directory of Internal SD (i.e Internal SD itself, no subfolders)
3. Reboot to Stock Recovery using Holding down VolumeDown+Power button to go to Bootloader, Then VolumeDown=>VolumeUp to recovery
or using ADB
Code:
adb reboot recovery
4. Apply update from SD and choose the downloaded package.
5. TaDa, Stock 4.4.4.
4.4.4 Update Doesn't wipe Internal Memory
And the Phone is as good as new.
Many thanks!!:good:
katobest said:
Many thanks!!:good:
Click to expand...
Click to collapse
Press Thanks Button. :good:
I'm new to motorola phones,
Can we unlock the moto g bootloader without getting the unlock code from motorola? and does that have any effect on warranty?
Is this mfastboot tool from motorola?
littleromeo said:
I'm new to motorola phones,
Can we unlock the moto g bootloader without getting the unlock code from motorola? and does that have any effect on warranty?
Is this mfastboot tool from motorola?
Click to expand...
Click to collapse
Without Unlock code u cant unlock booloader. your warrenty void after unlock.mfastboot tool from devlopers (google)
Failed to Validate System Image
Hi,
I have Moto G 2014 XT1068 model with locked bootloader. I have followed steps in 4.2 section, now the phone is not booting up with error message "Failed to validate system image boot uo failed" Please help revive my moto g 2014.
Thanks
Dhamukanna said:
Hi,
I have Moto G 2014 XT1068 model with locked bootloader. I have followed steps in 4.2 section, now the phone is not booting up with error message "Failed to validate system image boot uo failed" Please help revive my moto g 2014.
Thanks
Click to expand...
Click to collapse
Bro,
Never flash stock Firmware with a locked bootloader. -_-
Solution: Unlock Bootloader and reflash Stock Firmware with same steps.
Unlock Bootloader From Here: http://forum.xda-developers.com/mot...wip-unlock-bootloader-moto-g-2nd-gen-t2875728
SST Lock Failure
archies20 said:
Bro,
Never flash stock Firmware with a locked bootloader. -_-
Solution: Unlock Bootloader and reflash Stock Firmware with same steps.
Unlock Bootloader From Here: http://forum.xda-developers.com/mot...wip-unlock-bootloader-moto-g-2nd-gen-t2875728
Click to expand...
Click to collapse
Thanks Bro.. I unlocked bootloader.. followed steps in 4.2 section.. once I perform 4.4 step, phone reboots with a bootloader unlocked warning message and vibrates and then screen blinks with bootloader unlocked warning message and not booting into system.. Please help Bro
Dhamukanna said:
Thanks Bro.. I unlocked bootloader.. followed steps in 4.2 section.. once I perform 4.4 step, phone reboots with a bootloader unlocked warning message and vibrates and then screen blinks with bootloader unlocked warning message and not booting into system.. Please help Bro
Click to expand...
Click to collapse
I had the same issue. What I did was, in code 4.2, before this line:
"mfastboot.exe flash modem NON-HLOS.bin",
i added
"mfastboot.exe flash system system.img_sparsechunk.3",
as in the archive, there are three sprsechunk files.. Then the device booted up fine. Pls try and do let me know if I am wrong.
Is it necessary to flash all modules if we just want to return to stock recovery and remove root? Can we remove root and lock the bootloader without flashing all modules?
Thank you very much bro.. Issue resolved
deepaklunked said:
I had the same issue. What I did was, in code 4.2, before this line:
"mfastboot.exe flash modem NON-HLOS.bin",
i added
"mfastboot.exe flash system system.img_sparsechunk.3",
as in the archive, there are three sprsechunk files.. Then the device booted up fine. Pls try and do let me know if I am wrong.
Click to expand...
Click to collapse
Thanks bro.. I noticed system.img_sparsechunk.3 in the firmware folder and reflashed it as you have suggested.. worked like a charm now I am able to boot my moto g 2014 into system. Thanks again bro. I am going to post a new thread for properly reflashing stock rom on moto g 2014...
Update Steps else phone won't boot into system
archies20 said:
I am Starting this with a very simple reason that the filefactory link for the Firmware which is the only link currently available right now is a crapy link. The download failed six times before i could finally download it
Downloads:
1.http://goo.gl/5aVzPE [Dev-Host]
2.http://goo.gl/JsWtVE [Mirror]
Pre-Requisite:
1.http://goo.gl/Wl50A3
Instructions 4.4.4:
1. Download 4.4.4and Extract it to a folder
2. Download mfastboot-v2 and Extract it into the same folder [mfastboot Download: http://goo.gl/lTYq4F]
3. Reboot the phone into Bootloader
4. Run Following commands from the Command Prompt after cd-ing to the folder, one by one
If you do not wish to lock bootloader skip 4.1 and 4.3
4.1
Code:
mfastboot.exe oem lock begin
4.2
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
4.3
Code:
mfastboot.exe oem lock
4.4
Code:
mfastboot.exe reboot
And the Phone is as good as new.
Click to expand...
Click to collapse
Please add mfastboot.exe flash system system.img_sparsechunk.3 after mfastboot.exe flash system system.img_sparsechunk.2 (I have XT1068 model). Users need to flash all system files (sparsechunk.0, 1, 2, 3) to reflash stock firmware on Moto G 2014 else phone won't boot into system saying Failed to Validate System Image".
Dhamukanna said:
Please add mfastboot.exe flash system system.img_sparsechunk.3 after mfastboot.exe flash system system.img_sparsechunk.2 (I have XT1068 model). Users need to flash all system files (sparsechunk.0, 1, 2, 3) to reflash stock firmware on Moto G 2014 else phone won't boot into system saying Failed to Validate System Image".
Click to expand...
Click to collapse
Oh my god sorry guys for issue. mfastboot.exe flash system system.img_sparsechunk.3 added thanks.
Help..!!!
I ve messed up with one of the system apk and now want to flash stock firmware. I followed the steps but at first command it says "waiting for device".. It stays forever. pls help
I am not able to relock the bootloader nor able to flash stock rom
i simply followed OP's guide but still
Any help would be appreciated
haytham.kenway said:
I am not able to relock the bootloader nor able to flash stock rom
i simply followed OP's guide but still
Any help would be appreciated
Click to expand...
Click to collapse
And in phone i Get "Failed to Vaildate System Image":crying::crying::crying::crying::crying:
in Phone "Invalid PIV signed image file"
http://imgur.com/xCCr3IZ
Anyone please help me
haytham.kenway said:
Anyone please help me
Click to expand...
Click to collapse
Follow the steps provided below:
1. Install Motorola Device Drivers
2. Get Unlock Code from Motorola Website
3. Download firmware for your phone model
4. Follow the instructions provided in this thread
Dhamukanna said:
Follow the steps provided below:
1. Install Motorola Device Drivers
2. Get Unlock Code from Motorola Website
3. Download firmware for your phone model
4. Follow the instructions provided in this thread
Click to expand...
Click to collapse
Bro i have succesfully flashed the rom but i'm not able to lock the bootloader
it says failed to lock bootloader sst failure
help please
Im not able to flash the rom. Extrcted fastboot and rom in the same folder. shift and fight click, run cmd here. i entered the command but it says ' waiting for device' im rooted , bootloader is unlocked and usb debugging is on
Hi , guys after been long time i jumped from my old Galaxy Ace to these MOTO G2 , the concept of rooting and flashing on the Ace was very different from these new devices , we used to have one click flash got ROOT and again with one flash we got UNROOT , tada !
But in these devices for rooting we need to first unlock the boot loader and then we are free to root it or flash or any modding , but what if have to unroot and lock the boot loader ? , though unrooting is a quite a just one click we got unrooted phone but at the time of locking Bootloader we face errors .But why to lock it again ? though every one has different thinking but these is for those who want to lock . But at the time of locking ERRORS What are they ? how to solve them ? searching over the whole Internet but didn't found a proper solution ! So these type of situation is very critical for new users who are new to these like me ( jokes apart) . So below i have explained a little bit & a fail safe process , I am not taking about tools and download links for them just a process .
Click to expand...
Click to collapse
Various ERRORS which we face like
Code:
(bootloader) sst lock failure!
OKAY [ 0.011s]
finished. total time: 0.012s
Code:
failed to validate system image
Code:
Executing ".\Windows\fastboot.exe flash boot boot.img"
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.505s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.090s
Click to expand...
Click to collapse
These type of error we face while locking boot loader , now do note these things first of check out the build number of your phone & download the same build number firmware , or if there is updated version then you can download that . Because OEM doesn't allow you to downgrade the system it will give you error like system downgrade started & then failed to validate system image so flash the same build version firmware or higher one . By doing these follow the same steps as stated here @archies20 in his thread
Click to expand...
Click to collapse
Code:
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
Click to expand...
Click to collapse
Now by following the above procedure in the between watch out in your phone the screen will be black , and you will get to see the Locked status will be written after that the last error will be like
Code:
C:\MOTOROLA\mfastboot-v2>mfastboot.exe oem lock
...
FAILED (status read failed (Too many links))
finished. total time: 20.117s
But don't get panic the boot loader will be locked still the Unlock warning logo will be there so just flash the logo.bin .
Click to expand...
Click to collapse
Note : Don't try to lock the boot loader after flashing the firmware it will give you error like
Code:
(bootloader) sst lock failure!
OKAY [ 0.011s]
finished. total time: 0.012s
so follow the above procedure only , if you checked out the whole thing then there will be 0% chances of failing .
I hope you will found these thread very helpful ,
Thankyou
Click to expand...
Click to collapse
.
EDIT : You can downgrade via Fastboot not mFastboot.
Bootloader warning
I followed the steps exactly , and the only error occurred was the one you mentioned ,
but the "bootloader unlocked warning " still remains after i flashed the logo
what is the soulution ?
thankyou,
Good job hitesh :good:
If i relock the bootloader will miss the root?
Sebastian94 said:
If i relock the bootloader will miss the root?
Click to expand...
Click to collapse
Yes.
archies20 said:
Good job hitesh :good:
Click to expand...
Click to collapse
Thanks buddy , just i cleared all doubt's and errors .
ghostcoder said:
I followed the steps exactly , and the only error occurred was the one you mentioned ,
but the "bootloader unlocked warning " still remains after i flashed the logo
what is the soulution ?
thankyou,
Click to expand...
Click to collapse
First just check the Bootloader status in bootloader menu , if it is locked then just flash the logo.bin that's it .
OK, first you are giving instructions to flash the firmware and then to send command "lock oem" (the last line).
Later in your post:
Note : Don't try to lock the boot loader after flashing the firmware it will give you error like
sst lock failed.
This is exact error everyone gets, even following your steps (lock begin -> flash firmware -> oem lock).
This guide is misleading.
linasmit said:
OK, first you are giving instructions to flash the firmware and then to send command "lock oem" (the last line).
Later in your post:
Note : Don't try to lock the boot loader after flashing the firmware it will give you error like
sst lock failed.
This is exact error everyone gets, even following your steps (lock begin -> flash firmware -> oem lock).
This guide is misleading.
Click to expand...
Click to collapse
You are not getting properly , i told that after flashing firmware and after booting it , then taking back into boot loader now in these state if you will give command then it wont work !!
That's the point i have explained in that Note .
And above what ever i have written it is 100% working not only tested by but also some other users .
Cannot relock bootloader
Hitesh2626 said:
.
Click to expand...
Click to collapse
I have Global version. then flashed US version and upgrade to lollipop. Later decided to go back to Global version for using CF-autoroot. SO I downgraded to KitKaT US first. I again then changed to global version.
The problem is, now, I cannot relock bootloader. I can chage to us and also in us version i cannot relock.
While I flash Fastboot flash boot boot.img it says downgrading; same for Fastboot flash system system.img_sparsechunk.0; downgrading error as well as invalid piv signed system image error.
Thus after mfastboot.exe oem lock command, it gives SST lock failure ! failed to validate system image in device display.
Applied flash according to :
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
Click to expand...
Click to collapse
my mobile version info is attached
Anonymous 360 said:
I have Global version. then flashed US version and upgrade to lollipop. Later decided to go back to Global version for using CF-autoroot. SO I downgraded to KitKaT US first. I again then changed to global version.
The problem is, now, I cannot relock bootloader. I can chage to us and also in us version i cannot relock.
While I flash Fastboot flash boot boot.img it says downgrading; same for Fastboot flash system system.img_sparsechunk.0; downgrading error as well as invalid piv signed system image error.
Thus after mfastboot.exe oem lock command, it gives SST lock failure ! failed to validate system image in device display.
Applied flash according to :
my mobile version info is attached
Click to expand...
Click to collapse
+1 i cant flash the stock rom with mfastboot.exe oem lock begin if i use tht command .. am facing failed to validate system image plz help me to get out of here plz:crying:
pradeepmaddy said:
+1 i cant flash the stock rom with mfastboot.exe oem lock begin if i use tht command .. am facing failed to validate system image plz help me to get out of here plz:crying:
Click to expand...
Click to collapse
You can try this, for the first time with US version, as far as i can remember, it worked for me. But now, after downgrading and changing back to the global version, it is not working.....
Fastboot oem lock begin
Fastboot flash partition gpt.bin
Fastboot flash motoboot motoboot.img
Fastboot flash logo logo.bin
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Fastboot flash system system.img_sparsechunk.2
Fastboot flash system system.img_sparsechunk.3
Fastboot flash modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot erase cache
Fastboot erase userdata
Fastboot oem lock
Fastboot reboot
Click to expand...
Click to collapse
please, inform me, if it works
Anonymous 360 said:
You can try this, for the first time with US version, as far as i can remember, it worked for me. But now, after downgrading and changing back to the global version, it is not working.....
please, inform me, if it works
Click to expand...
Click to collapse
The user u have quoted is trying to lock the bootloader for Global version retaildsds.en03
If it works then its well & good..
Solved! Solved! Solved!
YEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE!!!!
After lots of flashing, at last ::fingers-crossed:
followed these steps:
after downgrading, go to bootloader, install twrp 2801 and flash supersu2.16 (that means, root your device ! ))
reboot and copy your lollipop update file (same variant) to the internal storage
now, again go to bootloader and flash the recovery: Fastboot flash recovery recovery.img
Now go to recovery and select your lollipop update... ta-da.... explanation:
After entering recovery node, Press the Volume Up and Volume Down buttons for around 5 seconds. Now while holding those two, press and release the Power button.
Your device will now be booted into stock recovery mode, displaying Android System Recovery <3e> text at the top of the screen.
apply adb trougt sdcard.... select file AND WAIT TO THE PROCess to finish
You dont need to lock the bootloader at all :good: :good:
Hit thanks if it helps
Anonymous 360 said:
YEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE!!!!
After lots of flashing, at last ::fingers-crossed:
followed these steps:
after downgrading, go to bootloader, install twrp 2801 and flash supersu2.16 (that means, root your device ! ))
reboot and copy your lollipop update file (same variant) to the internal storage
now, again go to bootloader and flash the recovery: Fastboot flash recovery recovery.img
Now go to recovery and select your lollipop update... ta-da.... explanation:
After entering recovery node, Press the Volume Up and Volume Down buttons for around 5 seconds. Now while holding those two, press and release the Power button.
Your device will now be booted into stock recovery mode, displaying Android System Recovery <3e> text at the top of the screen.
apply adb trougt sdcard.... select file AND WAIT TO THE PROCess to finish
You dont need to lock the bootloader at all :good: :good:
Hit thanks if it helps
Click to expand...
Click to collapse
Do you still have your device rooted after lollipop update?
Anonymous 360 said:
I have Global version. then flashed US version and upgrade to lollipop. Later decided to go back to Global version for using CF-autoroot. SO I downgraded to KitKaT US first. I again then changed to global version.
The problem is, now, I cannot relock bootloader. I can chage to us and also in us version i cannot relock.
While I flash Fastboot flash boot boot.img it says downgrading; same for Fastboot flash system system.img_sparsechunk.0; downgrading error as well as invalid piv signed system image error.
Thus after mfastboot.exe oem lock command, it gives SST lock failure ! failed to validate system image in device display.
Applied flash according to :
my mobile version info is attached
Click to expand...
Click to collapse
Anonymous 360 said:
YEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE!!!!
After lots of flashing, at last ::fingers-crossed:
followed these steps:
after downgrading, go to bootloader, install twrp 2801 and flash supersu2.16 (that means, root your device ! ))
reboot and copy your lollipop update file (same variant) to the internal storage
now, again go to bootloader and flash the recovery: Fastboot flash recovery recovery.img
Now go to recovery and select your lollipop update... ta-da.... explanation:
After entering recovery node, Press the Volume Up and Volume Down buttons for around 5 seconds. Now while holding those two, press and release the Power button.
Your device will now be booted into stock recovery mode, displaying Android System Recovery <3e> text at the top of the screen.
apply adb trougt sdcard.... select file AND WAIT TO THE PROCess to finish
You dont need to lock the bootloader at all :good: :good:
Hit thanks if it helps
Click to expand...
Click to collapse
bro am in kitkat now... i dont want to go with us variants again but i want to lock boot loader in kitkat itself please give me the solution for tht
I afraid I do not have a solution......
---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------
You still have SU app, but you will not have the binary, so you have to appy CF auto root : http://forum.xda-developers.com/moto-g-2014/help/solved-cf-chainfire-autoroot-problem-t2942154
Help please
pradeepmaddy said:
+1 i cant flash the stock rom with mfastboot.exe oem lock begin if i use tht command .. am facing failed to validate system image plz help me to get out of here plz:crying:
Click to expand...
Click to collapse
I've got an XT1068 bought in UK.......and stuck with the same problem after upgrading to lollipop (xt1063 way) and downgrade.
I cant' lock the bootloader and if I install a stock firmware trying to locking it i receive a lot of FAILED messaged (in partition,motoboot,boot, system system.img_sparsechunk1-2-3....) And can't lock with "SST lock failure ! failed to validate system image" error.
What I have to do? T_T Can someone help me please? I want to bring back everything as before...clean!
If I try to install a stock rom and i don't try to lock the bootloader i receive FAILED error only in the first 2 strings
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
and this never happen. What I have to do for locking the bootloader again? :\ I try with fastboot instead of mfastboot commands too..but...same results.
Thanks.... :crying:
After reading numerous threads about relocking the bootloader, I came to the conclusion that after a downgrade it's simply impossible to relock the bootloader.
So, if you have, for instrance, an XT1068 and you have flashed the US build of Lollipop on it, the only way to make it 'stock' is to downgrade to KitKat, since there is no official Lollipop build for the XT1068 yet. This means that you will be unable to lock the bootloader. You'll have to wait for an official Lollipop build, install that manually, and then relock the bootloader.
So in short: after a downgrade (as from Lollipop to Kitkat) it's impossible to lock the bootloader!
Please correct me if I'm wrong!
smitharro said:
After reading numerous threads about relocking the bootloader, I came to the conclusion that after a downgrade it's simply impossible to relock the bootloader.
So, if you have an XT1068 and you have flashed the US build of Lollipop on it, the only way to make it 'stock' is to downgrade to KitKat, since there is no official Lollipop build for the XT1068 yet. This means that you will be unable to lock the bootloader. You'll have to wait for an official Lollipop build, install that manually, and then relock the bootloader.
Please correct me if I'm wrong!
Click to expand...
Click to collapse
According Motorola downgrading from lolipop to kitkat is not possible
Moto G (2nd Generation) - Android™ 5.0 Lollipop - Release Notes
INTRODUCTION
We are excited to announce a new software update for Moto G (2nd Generation) by Motorola. This update brings Android™ 5.0 Lollipop to your phone along with other improvements.
For more information on Motorola updates and repairs, visit us at www.motorola.com/mymotog.
NOTE: You cannot downgrade to a previous software version after installing this update.
Bootloader unlock required to avoid downgrade PIV Signature errors in fastboot.
Download firmware for XT1063 21.11.17 here
http://motofirmware.com/files/download/950-retuglb-xt1063-444-kxb2185-17-cid9-cfcxmlzip/
I flashed firmware using @Shawn5162's scrpt, but replaced the 21.11.23 files with the ones from the link above.
http://forum.xda-developers.com/showthread.php?t=2957167
or you can do it manually via fastboot:
adb reboot bootloader
Fastboot flash partition gpt.bin
Fastboot flash motoboot motoboot.img
Fastboot flash logo logo.bin
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Fastboot flash system system.img_sparsechunk.2
Fastboot flash system system.img_sparsechunk.3
Fastboot flash modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot flash erase cache
Fastboot flash erase userdata
fastboot reboot
Then I applied all the following OTAs successfully:
Note: download and copy all OTAs to SD card downloads folder then install via STOCK Recovery apply update from SD Card
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-11-6-android-t2939881
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-16-t2965161
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-25-t2978658
http://forum.xda-developers.com/showthread.php?p=58136321
Please hit the thanks if it worked and report back.
P.S.
Still unable to lock bootloader until 5.0 firmware released.
Android The Greek said:
First my bootloader is unlocked as I would always get PIV Signature errors in fastboot when downgrading.
Second, I have not be able to look the bootloader at all since I have been on Lollipop before.
Download firmware for XT1063 21.11.17 here
http://motofirmware.com/files/download/950-retuglb-xt1063-444-kxb2185-17-cid9-cfcxmlzip/
I then flashed firmware using Shawn152's scrpt, but replacing the 21.11.23 files with the ones from the link above.
or you can do it manually:
adb reboot bootloader
Fastboot flash partition gpt.bin
Fastboot flash motoboot motoboot.img
Fastboot flash logo logo.bin
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Fastboot flash system system.img_sparsechunk.2
Fastboot flash system system.img_sparsechunk.3
Fastboot flash modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot flash erase cache
Fastboot flash erase userdata
fastboot reboot
Then I applied all the following OTAs successfully:
Note: download and copy all OTAs to SD card downloads folder then install via STOCK Recovery apply update from SD Card
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-11-6-android-t2939881
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-16-t2965161
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-25-t2978658
Please hit the thanks if it worked and report back. This should help all those stuck on 22.11.6. Please make sure you go all the way back to 21.11.17 first before reporting back.
Click to expand...
Click to collapse
I presume that you MAY NOT have to flash whole rom, if you 'JUST' flashed the needed version of recovery then you can upgrade with a OTA zip (can't test as only got xt1068) maybe someone can test this - but obviously some OTA's rely on being updated in order.
This is for XT1063 Only!
Android The Greek said:
Bootloader unlock required to avoid downgrade PIV Signature errors in fastboot.
Download firmware for XT1063 21.11.17 here
http://motofirmware.com/files/download/950-retuglb-xt1063-444-kxb2185-17-cid9-cfcxmlzip/
I flashed firmware using @Shawn5162's scrpt, but replaced the 21.11.23 files with the ones from the link above.
http://forum.xda-developers.com/showthread.php?t=2957167
or you can do it manually via fastboot:
adb reboot bootloader
Fastboot flash partition gpt.bin
Fastboot flash motoboot motoboot.img
Fastboot flash logo logo.bin
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Fastboot flash system system.img_sparsechunk.2
Fastboot flash system system.img_sparsechunk.3
Fastboot flash modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot flash erase cache
Fastboot flash erase userdata
fastboot reboot
Then I applied all the following OTAs successfully:
Note: download and copy all OTAs to SD card downloads folder then install via STOCK Recovery apply update from SD Card
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-11-6-android-t2939881
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-16-t2965161
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-25-t2978658
Please hit the thanks if it worked and report back. This should help all those stuck on 22.11.6. Please make sure you go all the way back to 21.11.17 first before reporting back.
P.S.
Still unable to lock bootloader.
Click to expand...
Click to collapse
Bootloader can easily be locked. I've done it & even made a one click to do it as well. However I was able to update to 5.0 without the bootloader being locked. I'm back on KitKat for the third time. I'm not willing to give up root & deal with all the bugs of L.
There is also a custom ROM in these forms that run smoother than the stock & easier to install but still has the root bug.
kingmt01 said:
Bootloader can easily be locked. I've done it & even made a one click to do it as well. However I was able to update to 5.0 without the bootloader being locked. I'm back on KitKat for the third time. I'm not willing to give up root & deal with all the bugs of L.
There is also a custom ROM in these forms that run smoother than the stock & easier to install but still has the root bug.
Click to expand...
Click to collapse
What model do you have?
I can assure you I am not new at this, I bought my phone from Amazon with 21.11.23 and there was an addition added at some point that prevents a downgrade and in turn does not allow the system to be flashed with a locked or unlocked bootloader if you start with the command Fastboot oem lock begin.
if you have an XT1063 please tell me how you locked your bootloader without modifying anything that will then be unreversable.
Don't take it the wrong way, but I have seen people create tools that edit the hex to show bootloader locked then they can no longer unlock it or corrupt the phone and brick.
Android The Greek said:
What model do you have?
I can assure you I am not new at this, I bought my phone from Amazon with 21.11.23 and there was an addition added at some point that prevents a downgrade and in turn does not allow the system to be flashed with a locked or unlocked bootloader if you start with the command Fastboot oem lock begin.
if you have an XT1063 please tell me how you locked your bootloader without modifying anything that will then be unreversable.
Don't take it the wrong way, but I have seen people create tools that edit the hex to show bootloader locked then they can no longer unlock it or corrupt the phone and brick.
Click to expand...
Click to collapse
ETA: I'm not going to get upset over anything in a forum. I just post info to the best of my knowledge in hope to be helpful to someone else. Sometimes that changes as more knowledge is gained.
I have a xt1063 .17 & I did use "fastboot oem lock begin" I don't remember every command but the one click also restored the stock firmware at the same time. I'll have to look at my files in a few. I only made about 20 one clicks & was writing & rewriting a how to guide all at the same time as I was trying to figure it out & get on 5.0 all at the same time. Like I said tho my bootloader is unlocked again & it doesn't seem to affect the ability to flash OTA.
---------- Post added at 12:43 PM ---------- Previous post was at 11:55 AM ----------
OK. I used mfastboot to lock it.
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot oem lock
kingmt01 said:
ETA: I'm not going to get upset over anything in a forum. I just post info to the best of my knowledge in hope to be helpful to someone else. Sometimes that changes as more knowledge is gained.
I have a xt1063 .17 & I did use "fastboot oem lock begin" I don't remember every command but the one click also restored the stock firmware at the same time. I'll have to look at my files in a few. I only made about 20 one clicks & was writing & rewriting a how to guide all at the same time as I was trying to figure it out & get on 5.0 all at the same time. Like I said tho my bootloader is unlocked again & it doesn't seem to affect the ability to flash OTA.
---------- Post added at 12:43 PM ---------- Previous post was at 11:55 AM ----------
OK. I used mfastboot to lock it.
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot oem lock
Click to expand...
Click to collapse
I never said anything about needing to relock it. I just said I have not been able to for those of us that want 5.0.1 and want to lock the bootloader. If you are able to price steps on how you downgraded from 5.0 and locked the boot loader I sure would want to try it myself.
Ideally I would add in the commands above fastboot OEM lock begin and fastboot OEM unlock for those who want a relocked boot loader before flashing the otas. Its just not possible if you are not on 21.11.17 to begin with because of the signed zip downgrade verification
Android The Greek said:
I never said anything about needing to relock it. I just said I have not been able to for those of us that want 5.0.1 and want to lock the bootloader. If you are able to price steps on how you downgraded from 5.0 and locked the boot loader I sure would want to try it myself.
Ideally I would add in the commands above fastboot OEM lock begin and fastboot OEM unlock for those who want a relocked boot loader before flashing the otas. Its just not possible if you are not on 21.11.17 to begin with because of the signed zip downgrade verification
Click to expand...
Click to collapse
Stating that it didn't need locked to flash 5.0 is just added info for anyone fallowing the thread & based on my experience. That may change for flashing 5.0.1.
These commands was ran from a modified 21.11.17 build to lock the bootloader. I thought I read ether in this thread or another thread that you already found a way to flash back to the stock firmware 21.11.17 without the downgrade error. If your on stock 21.11.17 now then you could give the lock command a try from mfastboot. I restored a Nandroid to get back to KitKat from Lollipop.
The one click I made was for those that had tampered with their stock 21.11.17 & wanted to be back to stock & locked. I didn't even know there was a 21.11.23 build at the time.
kingmt01 said:
Stating that it didn't need locked to flash 5.0 is just added info for anyone fallowing the thread & based on my experience. That may change for flashing 5.0.1.
These commands was ran from a modified 21.11.17 build to lock the bootloader. I thought I read ether in this thread or another thread that you already found a way to flash back to the stock firmware 21.11.17 without the downgrade error. If your on stock 21.11.17 now then you could give the lock command a try from mfastboot. I restored a Nandroid to get back to KitKat from Lollipop.
The one click I made was for those that had tampered with their stock 21.11.17 & wanted to be back to stock & locked. I didn't even know there was a 21.11.23 build at the time.
Click to expand...
Click to collapse
Correct!
Android The Greek said:
Bootloader unlock required to avoid downgrade PIV Signature errors in fastboot.
Download firmware for XT1063 21.11.17 here
http://motofirmware.com/files/download/950-retuglb-xt1063-444-kxb2185-17-cid9-cfcxmlzip/
I flashed firmware using @Shawn5162's scrpt, but replaced the 21.11.23 files with the ones from the link above.
http://forum.xda-developers.com/showthread.php?t=2957167
or you can do it manually via fastboot:
adb reboot bootloader
Fastboot flash partition gpt.bin
Fastboot flash motoboot motoboot.img
Fastboot flash logo logo.bin
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Fastboot flash system system.img_sparsechunk.2
Fastboot flash system system.img_sparsechunk.3
Fastboot flash modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot flash erase cache
Fastboot flash erase userdata
fastboot reboot
Then I applied all the following OTAs successfully:
Note: download and copy all OTAs to SD card downloads folder then install via STOCK Recovery apply update from SD Card
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-11-6-android-t2939881
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-16-t2965161
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-25-t2978658
Please hit the thanks if it worked and report back. This should help all those stuck on 22.11.6. Please make sure you go all the way back to 21.11.17 first before reporting back.
P.S.
Still unable to lock bootloader.
Click to expand...
Click to collapse
Worked like a charm! Thank you so much, Updated my moto g 2014 xt1063 21.11.23 KitKat 4.4.4 Amazon unocked global using this method. :good:
Thank you for reporting in appreciate it
help
hello,i am somewhat new to these things but surely i can do it with detailed steps(thanks for those)
so here is the thing,i bought Moto G2 from amazon last month and my mobile has these details
System Version:-
21.11.23.titan_retuglb.retuglb.en.US retus
Build Number- KXB21.85-23
i am bored with KitKat ..
a few ques:-
After this tricky update will i be eligible for future updates too?
Can i root after the Lolipop update?
WIl this method format my mobile?
Thanks.
(sry for newbie type ques )
kkriop said:
hello,i am somewhat new to these things but surely i can do it with detailed steps(thanks for those)
so here is the thing,i bought Moto G2 from amazon last month and my mobile has these details
System Version:-
21.11.23.titan_retuglb.retuglb.en.US retus
Build Number- KXB21.85-23
i am bored with KitKat ..
a few ques:-
After this tricky update will i be eligible for future updates too?
Can i root after the Lolipop update?
WIl this method format my mobile?
Thanks.
(sry for newbie type ques )
Click to expand...
Click to collapse
You will get updates. You can Root, however I do not think there is a stable root yet. If you unlock your boot loader it will format, if you already unlocked your boot loader then you will not loose your data.
Android The Greek said:
You will get updates. You can Root, however I do not think there is a stable root yet. If you unlock your boot loader it will format, if you already unlocked your boot loader then you will not loose your data.
Click to expand...
Click to collapse
Its fine w/o root..as far as i am getiing lollipop experience.. My bootloader is unlcoked..will do the thing and post ..thanks again
kkriop said:
Its fine w/o root..as far as i am getiing lollipop experience.. My bootloader is unlcoked..will do the thing and post ..thanks again
Click to expand...
Click to collapse
No problem
Android The Greek said:
No problem
Click to expand...
Click to collapse
downgrade complete now the issue is when i check System Updates it doesnt pick up Lollipop update
and these manual update links doesnt open is there any mirror link?? :crying:
Do you mean you cannot download from mega?
Which one you need I'll put it in my Dropbox and pm you
Android The Greek said:
Do you mean you cannot download from mega?
Which one you need I'll put it in my Dropbox and pm you
Click to expand...
Click to collapse
The two from mega (first two) third one is already on dropbox so not a prob for that..
Thank u very much
so is safe to install ota updates with bootloader unlocked?
CrazyGenio said:
so is safe to install ota updates with bootloader unlocked?
Click to expand...
Click to collapse
Yes an unlocked boot loader has no effect on anything except the abity to flash a custom recovery. If your unlocked and have it all stock, then you should be good
I have found that the new update is not a newer Android version but a security patch according to identifications made in July 2016.
Total size of update is 508.4 MB.
Some people have reported problems with notification sounds.
Do we have any more news about this update.?
Please upload stock rom for indian variant moto g4plus xt1643
i have installed a stock rom and it was US but now my phone is unable to connect to any wifi or mobile network plz upload anywhere else than filefactory
I have installed the update and everything is working fine for me.
help
jack_04 said:
I have installed the update and everything is working fine for me.
Click to expand...
Click to collapse
can u backup ur rom nd upload
navi74644 said:
can u backup ur rom nd upload
Click to expand...
Click to collapse
My phone is not rooted. So I guess I can not take ROM backup.
no need to be rooted
jack_04 said:
My phone is not rooted. So I guess I can not take ROM backup.
Click to expand...
Click to collapse
just put it in fastboot mode and pull the rom
navi74644 said:
just put it in fastboot mode and pull the rom
Click to expand...
Click to collapse
Can You Tell Me How To pull the rom In fastboot mode?
I hv installed updates..
There is a problem after that..
Sim 1 is automatically Off after sm time..
How is your phone working now?
jack_04 said:
I have installed the update and everything is working fine for me.
Click to expand...
Click to collapse
Motorola claims that they have solved all the reported issues except heating because of its board.
Many people have found that notification volume is decreased to 30%.
Could you share detailed information about what is included in update?
Have you reported this with Motorola?
Milan Samani said:
I hv installed updates..
There is a problem after that..
Sim 1 is automatically Off after sm time..
Click to expand...
Click to collapse
If you are using unrooted phone the I would suggest you to report this with Motorola. Let us know how do they respond and if they are willing to offer any quick solution to this issue.
first thing first: I have rooted using systemless root method. so if I update to this latest patch will I have to root it again? and will it be a complete factory reset or I can expect my apps persisting after update?
Sent from my Moto G (4) using Tapatalk
is there any way to update my unlocked bootloader phone ? I tried everything.. Flashed stock recovery... Unroot my phone.. Flash fire etc. nothing works.. Any suggestion will be appriciate.
navi74644 said:
i have installed a stock rom and it was US but now my phone is unable to connect to any wifi or mobile network plz upload anywhere else than filefactory
Click to expand...
Click to collapse
Same thing happened to me ! What I did is I just gave my mobile to service centre they flashed original firmware( don't forget to remove warning image )
I got this update and after updating, I am facing low notification sound.
Sent from my Moto G (4) using Tapatalk
By my ear notification sound is about 60% what it was before (this is sitting two devices next to each other and comparing the updated device at max volume with the non-updated device, when the nud's volume bar was at ~60℅ they sounded equal). Incidentally 100℅ on the non-updated device was probably a bit too loud.
I've contacted Moto and requested they acknowledge the issue and provide a timeframe for a solution; I have threatened to return both devices to my supplier. I'll share the reply.
The US unlocked XT1644 didnt get any updates. Anybody expecting android 7.0 before the holidays is going to be disappointed.
Pranav Kumar said:
Same thing happened to me ! What I did is I just gave my mobile to service centre they flashed original firmware( don't forget to remove warning image )
Click to expand...
Click to collapse
how to remove warning nd here did get it flashed again i mean which service centre
navi74644 said:
how to remove warning nd here did get it flashed again i mean which service centre
Click to expand...
Click to collapse
relock the bootloader and flash the stock rom again.
steps:
Flashing Stock Firmware:
1) Download firmware for XT1643 from https://drive.google.com/file/d/0B1N...tsRU1RTVk/view
2) Download mfastboot from https://drive.google.com/file/d/0B5j...ew?usp=sharing
3) Extract the firmware into the folder containing mfastboot.
4) Reboot the phone into Bootloader (power off, then press the power and volume down buttons simultaneously).
5) Execute these commands and make sure you receive an 'OKAY' after each command.
Code: just type first mfastboot oem lock,then enter this commands
mfastboot oem lock
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem lock
mfastboot reboot
anhoxhrs said:
relock the bootloader and flash the stock rom again.
steps:
Flashing Stock Firmware:
1) Download firmware for XT1643 from https://drive.google.com/file/d/0B1N...tsRU1RTVk/view
2) Download mfastboot from https://drive.google.com/file/d/0B5j...ew?usp=sharing
3) Extract the firmware into the folder containing mfastboot.
4) Reboot the phone into Bootloader (power off, then press the power and volume down buttons simultaneously).
5) Execute these commands and make sure you receive an 'OKAY' after each command.
Code: just type first mfastboot oem lock,then enter this commands
mfastboot oem lock
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem lock
mfastboot reboot
Click to expand...
Click to collapse
brother the given link doest not exist plz update ur drive download link it will be highly thankful to u
navi74644 said:
brother the given link doest not exist plz update ur drive download link it will be highly thankful to u
Click to expand...
Click to collapse
Lol this guy who mentioned the stepd just did a copy paste.the url he provided is incomplete.the complete url is - https://drive.google.com/file/d/0B1N6dGU7FEXsSjR3QUtsRU1RTVk/view