Related
For all Condor Owners if you wish to restore your Moto E back to stock then follow the guide, Ask any doubts in the comments!
Droid-Developers Website is down, I don't have any locally stored copy. Please wait until the link is updated or better sources are found. If any of you are having the original firmwares in your Hard-drives, Please, upload them and share their links, this would help the community in general. For now I am helpless and this post will not make sense.
I did find some firmwares for moto E here
DISCLAIMER:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research! YOU are choosing to follow this method to restore, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Pre-Requisite:
Installed Motorola Drivers.
Instructions:
Go to This This link, and download the firmware for your model! If you are unsure which one is yours please see Appendix 1
Download mfastboot-v2 and Extract it into the same folder
Reboot the phone into Bootloader using VolumeDown+Power Button
If you prefer an automatic one click process please go to step 5
Shift+RightClick in empty space in the extracted folder and choose open a command window here.
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
OR
If you just did 4th step, You can skip this
Download Restore.bat/Restore+lock.bat from Attachments, Extract it to the same folder and just run
And the phone is as good as new.
So now experiment all you want, flash different firmwares.
Appendix:
How to choose Correct Firmware for your phone
If you are unsure which one is your firmware, go to Settings>About Phone>System Version the text written there will be similar to the version you want to choose!
If You cannot access your phone or have changed ROM, then please go to bootloader mode using step 2 and 3 from instructions, Open command window like in step 4. Enter
Code:
fastboot getvar ro.build.version.full
. You will see the version to choose in output.
Still cant find, then wait the list at droid-developers is still expanding, your firmware version will be soon up
If you don't like the bootloader unlock logo then here is a method by @cschmitt originally posted here
Download this file, copy it to your fastboot location
Reboot to bootloader using Power+VolumeDown
Do following command from command prompt
Code:
fastboot flash logo logo.bin
Reboot and enjoy
If flashing is failed in any of the commands
Thanks @sw33ty4ppu for asking this question.
Critical Commands (Absolutely Necessary Commands, which if failed will hard brick)
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash boot boot.img
Non-Critical (If these failed, It will still allow you to go to bootloader and start flashing again)
Code:
mfastboot.exe flash logo logo.bin
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
First check which command gave you an error in flashing.
Any of the non-critical command fails to flash, You can start flashing again and hope it might work, you can also check if the downloaded files are proper or their extraction from zip is proper. You can ask for help here on XDA in Q&A section as well.
Any of the critical command fails to flash, it is absolutely necessary that you do not exit bootloader. Because when device is in bootloader mode, bootloader is loaded into RAM and is still the original copy, you can still take the phone which is already in bootloader mode to a friend's place and get the flashing done there. But if you reboot bootloader somehow(knowingly/unknowingly). Man, You're screwed. Morale of the story, don't turn off/ reboot your phone until correct flashing is performed.
This also is another reason that experienced users prefer to enter commands manually than rely on an automated .bat or .sh script.
If it helped, Hit thanks
Reserved!
Thanks for the guide!!:laugh::good:
Maybe a noob question but want to know how different is the mfastboot.exe from the normal fastboot commands?
Edit: I checked with the files in the directory linked for mfastboot and found the files are from android sdk. correct me if im wrong. Thanks in advance
phanitej said:
Maybe a noob question but want to know how different is the mfastboot.exe from the normal fastboot commands?
Edit: I checked with the files in the directory linked for mfastboot and found the files are from android sdk. correct me if im wrong. Thanks in advance
Click to expand...
Click to collapse
What mfastboot is basically a set of extended commands for normal fastboot, what Motorola has done is taken the fastboot protocol that is integrated into the bootloader code and added additional features and operations to fit with how there devices partition schemes are laid out and how they have designed the devices. In summary think of it as fastboot from the Android Open Source Project (Which is what is found in the Android SDK) with extra features for Motorola devices. The files in the directory you saw do come from the Android SDK however mfastboot and fastboot included in the Android SDK are not the same, mfasboot and the files from the Android SDK were bundled together for the convenience of downloading them. Let me know if you still have question's I'll be happy to answer them.
shimp208 said:
What mfastboot is basically a set of extended commands for normal fastboot, what Motorola has done is taken the fastboot protocol that is integrated into the bootloader code and added additional features and operations to fit with how there devices partition schemes are laid out and how they have designed the devices. In summary think of it as fastboot from the Android Open Source Project (Which is what is found in the Android SDK) with extra features for Motorola devices. The files in the directory you saw do come from the Android SDK however mfastboot and fastboot included in the Android SDK are not the same, mfasboot and the files from the Android SDK were bundled together for the convenience of downloading them. Let me know if you still have question's I'll be happy to answer them.
Click to expand...
Click to collapse
Thanks for the explanation
The reason why i wanted to know is, i use lubuntu and don have any windows PC i cud use. Was able to root and flash the device using fastboot, so in case i wish to lock it back, dint want to go through the hassle of searching for a windows PC
How to restore Moto logo instead of bootloader unlocked logo?? thanks
gaurav2009 said:
How to restore Moto logo instead of bootloader unlocked logo?? thanks
Click to expand...
Click to collapse
You could try the bootlogo restore method for moto G, it is unconfirmed weather it works or not!
Otherwise you will have to wait for someone to modify the logo!
deej_roamer said:
You could try the bootlogo restore method for moto G, it is unconfirmed weather it works or not!
Otherwise you will have to wait for someone to modify the logo!
Click to expand...
Click to collapse
Actually i tried it though the warning is removed but the M logo doesnot show up it is all black for some seconds then the bootanimation starts up
gaurav2009 said:
Actually i tried it though the warning is removed but the M logo doesnot show up it is all black for some seconds then the bootanimation starts up
Click to expand...
Click to collapse
Better than the pathetic white unlocked warning!
deej_roamer said:
Better than the pathetic white unlocked warning!
Click to expand...
Click to collapse
Yeah lol
Here is modified logo.bin for bootloader unlocked Moto E (shows normal boot splash instead of dire warning.)
1. Download and unzip logo.zip.
2. Reboot to fastboot mode (power + vol down)
3. fastboot flash logo logo.bin
4. Reboot, enjoy!
cschmitt said:
Here is modified logo.bin for bootloader unlocked Moto E (shows normal boot splash instead of dire warning.)
1. Download and unzip logo.zip.
2. Reboot to fastboot mode (power + vol down)
3. fastboot flash logo logo.bin
4. Reboot, enjoy!
Click to expand...
Click to collapse
Added to main thread!
cschmitt said:
Here is modified logo.bin for bootloader unlocked Moto E (shows normal boot splash instead of dire warning.)
1. Download and unzip logo.zip.
2. Reboot to fastboot mode (power + vol down)
3. fastboot flash logo logo.bin
4. Reboot, enjoy!
Click to expand...
Click to collapse
Thanks it works perfectly
Nice guide
Sent from my XT1022 using XDA Free mobile app
lock bootloader
can the bootloader be locked without flashing whole firmware?
and will it wipe or erase all data like unlocking?
please tell me..
indrasen00 said:
can the bootloader be locked without flashing whole firmware?
and will it wipe or erase all data like unlocking?
please tell me..
Click to expand...
Click to collapse
No Locking bootloader needs a fresh firmware! you will need to wipe your device with its internal memory completely,
Thanks ! Worked Perfectly !
cschmitt said:
Here is modified logo.bin for bootloader unlocked Moto E (shows normal boot splash instead of dire warning.)
1. Download and unzip logo.zip.
2. Reboot to fastboot mode (power + vol down)
3. fastboot flash logo logo.bin
4. Reboot, enjoy!
Click to expand...
Click to collapse
Thanks ! Worked Perfectly !
How to edit/create log.bin file in linux for moto E ?
cschmitt said:
Here is modified logo.bin for bootloader unlocked Moto E (shows normal boot splash instead of dire warning.)
1. Download and unzip logo.zip.
2. Reboot to fastboot mode (power + vol down)
3. fastboot flash logo logo.bin
4. Reboot, enjoy!
Click to expand...
Click to collapse
How to edit/create log.bin file in linux for moto E? How did u edit the original logo.bin file. pls give the steps to do the same.
paultsr said:
How to edit/create log.bin file in linux for moto E? How did u edit the original logo.bin file. pls give the steps to do the same.
Click to expand...
Click to collapse
I would recommend taking a look at this guide , it steps are essentially the same for the Moto E and since part of the guide involves GIMP you will be able to follow along on Linux.
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.
This method are originally made by the member ffosilva, I just made a step-by-step tutorial.
Works on the XT1068 (Dual-SIM) and XT1069 (DSTV)
What you need:
XT1068 or XT1069 stock ROM.
Unlocked Bootloader.
Necessary Files:
ADB
mfastboot
ROMS:
XT1064 Firmware
Lollipop modified to work dual SIM
Recovery:
CWM Philz Touch
OPTIONAL:
If something goes wrong...
XT1068 (Dual-Sim variant)
XT1069 (DSTV variant)
BUGS:
If use only 1 SIM: Nothing
If use 2 SIM's: Dialer fc when try to call or accept a call. You can use 2 SIMs, but you has to choice manually the SIM that you makes call. To solve this problem: Open the Dialer, Dialer setting (three dots) Call settings >phone account settings>Makes call with> Select the SIM that you use for make calls. (Correct-me if the names of options are wrong, cause I use another language.)
DSTV: function lost on XT1069.
Lets install Lollipop 5.0:
1. Download the necessary files.
2. Extract the adb tools, mfastboot, XT1064 firmware, CWM Philz Touchin a folder.
3. Put the Moto G on Bootloader Mode (Power on and Volume down)
4. Press and hold the Shift key, press the right button of mouse and select the option "Open a prompt".
5. Follow the commands below:
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 erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
6. Wait the system start, move the file "update_nofsg.zip" to the Moto G internal storage's. You lost the signal, don't worry, cause you will recover when you do the next step.
7. Go to bootloader screen (power on and volume down) and install the CWM Philz Touch Recovery using the command "mfastboot.exe flash recovery CWM_Touch_Titan_V2.img".
7. Acess the recovery mode, just select "Recovery" in bootloader screen.
8. Select "Install" in the CWM Philz Touch, select the "update_nofsg.zip" file and wait the process finish (It takes a while, but it will work).
9. Reboot, wait the system boot and update the apps.
Well done, Android 5.0 Lollipop installed!
Thanks for you tutorial. Lollipop is not so smooth as Kitkat was..
delete
Or just wait a little bit longer for lollipop to hit. Be any time soon for the dual sim version.
chamadas off
Vithalvess said:
This method are originally made by the member ffosilva, I just made a step-by-step tutorial.
Works on the XT1068 (Dual-SIM) and XT1069 (DSTV)
What you need:
XT1068 or XT1069 stock ROM.
Unlocked Bootloader.
Necessary Files:
ADB
mfastboot
ROMS:
XT1064 Firmware
Lollipop modified to work dual SIM
Recovery:
CWM Philz Touch
OPTIONAL:
If something goes wrong...
XT1068 (Dual-Sim variant)
XT1069 (DSTV variant)
BUGS:
If use only 1 SIM: Nothing
If use 2 SIM's: Dialer fc when try to call or accept a call. You can use 2 SIMs, but you has to choice manually the SIM that you makes call. To solve this problem: Open the Dialer, Dialer setting (three dots) Call settings >phone account settings>Makes call with> Select the SIM that you use for make calls. (Correct-me if the names of options are wrong, cause I use another language.)
DSTV: function lost on XT1069.
Lets install Lollipop 5.0:
1. Download the necessary files.
2. Extract the adb tools, mfastboot, XT1064 firmware, CWM Philz Touchin a folder.
3. Put the Moto G on Bootloader Mode (Power on and Volume down)
4. Press and hold the Shift key, press the right button of mouse and select the option "Open a prompt".
5. Follow the commands below:
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 erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
6. Wait the system start, move the file "update_nofsg.zip" to the Moto G internal storage's. You lost the signal, don't worry, cause you will recover when you do the next step.
7. Go to bootloader screen (power on and volume down) and install the CWM Philz Touch Recovery using the command "mfastboot.exe flash recovery CWM_Touch_Titan_V2.img".
7. Acess the recovery mode, just select "Recovery" in bootloader screen.
8. Select "Install" in the CWM Philz Touch, select the "update_nofsg.zip" file and wait the process finish (It takes a while, but it will work).
9. Reboot, wait the system boot and update the apps.
Well done, Android 5.0 Lollipop installed!
Click to expand...
Click to collapse
ola amigo fiz todo o processo mas nao consigo fazer ligaçoes somente envio de sms, rede e receber chamadas. alguma dica? obrigado.
Works fine
please mirror this files to some other site coz mega host not opening
mrstabs said:
Or just wait a little bit longer for lollipop to hit. Be any time soon for the dual sim version.
Click to expand...
Click to collapse
Then what are u doing on XDA buddy...
U should not be reading this post..if u r waiting for the Lollipop update.
---------- Post added at 10:07 PM ---------- Previous post was at 10:06 PM ----------
pradeepmaddy said:
please mirror this files to some other site coz mega host not opening
Click to expand...
Click to collapse
Install the mega app from playstore.
Then click on the mega link..& transfer the file to ur Mega account & download it.
This works. Done it with two phones so far.
if I want to move back to Kitkat what are the steps I should follow?
For in the Spanish XT1068 dialer FC continues. To continue waiting for the officer if that product or method works
It could not be done as follows: Flash the rom without flash the baseband files (either in exchange for American rom as the update for the lollipop)?
Like this:
Flash this:
Code:
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 erase cache
fastboot erase userdata
fastboot reboot
Don't flash this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
djixon said:
For in the Spanish XT1068 dialer FC continues. To continue waiting for the officer if that product or method works
Click to expand...
Click to collapse
It works, I have an XT1068 too
You must to set a SIM as default, because it crash when prompt is selected
Sent from my XT1063 using XDA Free mobile app
Good work!!!
How i know if the xt1068 have the bootloader unlocked?
Thanks in advance!!!
luisjoseb said:
It works, I have an XT1068 too
You must to set a SIM as default, because it crash when prompt is selected
Sent from my XT1063 using XDA Free mobile app
Click to expand...
Click to collapse
Your sing is xt1063
djixon said:
Your sing is xt1063
Click to expand...
Click to collapse
Yes, because I install the LOLLIPOP XT1063 firmware on my XT1068
Sent from my XT1063 using XDA Free mobile app
I used xt1063 firmware on my xt1068 and flashed lollipop .... Now hw can I root my device ?
thomstrack said:
It could not be done as follows: Flash the rom without flash the baseband files (either in exchange for American rom as the update for the lollipop)?
Like this:
Flash this:
Code:
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 erase cache
fastboot erase userdata
fastboot reboot
Don't flash this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
what do mean ... what shouldnt i flash this ????
---------- Post added at 07:26 PM ---------- Previous post was at 07:17 PM ----------
what should i do if i dont want the dual sim version ???? i am from india ... us rom dosnt recieve signal here ... but i use only one sim ... and i dont want those dual sim symbol thats on the lock screen ... what should i do to get us rom have signal
Vappali!
Vithalvess said:
This method are originally made by the member ffosilva, I just made a step-by-step tutorial.
Works on the XT1068 (Dual-SIM) and XT1069 (DSTV)
What you need:
XT1068 or XT1069 stock ROM.
Unlocked Bootloader.
Necessary Files:
ADB
mfastboot
ROMS:
XT1064 Firmware
Lollipop modified to work dual SIM
Recovery:
CWM Philz Touch
OPTIONAL:
If something goes wrong...
XT1068 (Dual-Sim variant)
XT1069 (DSTV variant)
BUGS:
If use only 1 SIM: Nothing
If use 2 SIM's: Dialer fc when try to call or accept a call. You can use 2 SIMs, but you has to choice manually the SIM that you makes call. To solve this problem: Open the Dialer, Dialer setting (three dots) Call settings >phone account settings>Makes call with> Select the SIM that you use for make calls. (Correct-me if the names of options are wrong, cause I use another language.)
DSTV: function lost on XT1069.
Lets install Lollipop 5.0:
1. Download the necessary files.
2. Extract the adb tools, mfastboot, XT1064 firmware, CWM Philz Touchin a folder.
3. Put the Moto G on Bootloader Mode (Power on and Volume down)
4. Press and hold the Shift key, press the right button of mouse and select the option "Open a prompt".
5. Follow the commands below:
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 erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
6. Wait the system start, move the file "update_nofsg.zip" to the Moto G internal storage's. You lost the signal, don't worry, cause you will recover when you do the next step.
7. Go to bootloader screen (power on and volume down) and install the CWM Philz Touch Recovery using the command "mfastboot.exe flash recovery CWM_Touch_Titan_V2.img".
7. Acess the recovery mode, just select "Recovery" in bootloader screen.
8. Select "Install" in the CWM Philz Touch, select the "update_nofsg.zip" file and wait the process finish (It takes a while, but it will work).
9. Reboot, wait the system boot and update the apps.
Well done, Android 5.0 Lollipop installed!
Click to expand...
Click to collapse
Hi!
Thank you! Hungarian language is it?
Root
Now how do I root it on my xt1069?
Hii !! How long will it take for the fastboot rom to arrive for Moto g4 plus Indian retail xt1643 ... With 1st Feb 2018 security patch ???
Vs1607 said:
Hii !! How long will it take for the fastboot rom to arrive for Moto g4 plus Indian retail xt1643 ... With 1st Feb 2018 security patch ???
Click to expand...
Click to collapse
https://drive.google.com/file/d/1qR9MUUQCNUQ6sAivz2OTkc4TW88vmszv/edit
Already available since a month.
smog2699 said:
https://drive.google.com/file/d/1qR9MUUQCNUQ6sAivz2OTkc4TW88vmszv/edit
Already available since a month.
Click to expand...
Click to collapse
Where'd you find it ?? I mean I've been searching this whole time and couldn't find it ?
.
.
.
Just curious ! ?
Vs1607 said:
Where'd you find it ?? I mean I've been searching this whole time and couldn't find it Just curious ! ?
Click to expand...
Click to collapse
It was posted in the forum at least three times.
thorin0815 said:
It was posted in the forum at least three times.
Click to expand...
Click to collapse
Hi thorin0815, Vs1607,
Just a off thread question. If a flash this image it will wipe the data? My issue is described on below link. Please help me.
https://forum.xda-developers.com/moto-g4-plus/help/stock-moto-g4-plus-getting-rebooted-t3781480
hardythaker said:
Hi thorin0815, Vs1607,
Just a off thread question. If a flash this image it will wipe the data? My issue is described on below link. Please help me.
https://forum.xda-developers.com/moto-g4-plus/help/stock-moto-g4-plus-getting-rebooted-t3781480
Click to expand...
Click to collapse
If you want to avoid wiping your data whilst flashing the fastboot stock ROM, you can omit the 'fastboot erase userdata' command and you do not have to re-lock your bootloader (re-locking will wipe your data).
However, if you are experiencing instabilities as you mentioned, a data wipe is a useful troubleshooting step, and may help you determine if your data is corrupted or whether you may have a more serious hardware/firmware issue.
echo92 said:
If you want to avoid wiping your data whilst flashing the fastboot stock ROM, you can omit the 'fastboot erase userdata' command and you do not have to re-lock your bootloader (re-locking will wipe your data).
However, if you are experiencing instabilities as you mentioned, a data wipe is a useful troubleshooting step, and may help you determine if your data is corrupted or whether you may have a more serious hardware/firmware issue.
Click to expand...
Click to collapse
Okay thanks for your comments. I will give it a try. Just one question is that the latest firmware. Because I had recently updated the ROM.
hardythaker said:
Okay thanks for your comments. I will give it a try. Just one question is that the latest firmware. Because I had recently updated the ROM.
Click to expand...
Click to collapse
NPJS25.93-14-15 as of writing is the latest firmware, Feb 2018 security patch. What ROM did you update to?
echo92 said:
NPJS25.93-14-15 as of writing is the latest firmware, Feb 2018 security patch. What ROM did you update to?
Click to expand...
Click to collapse
April ota is the last , but no one have it
leap_ahead said:
April ota is the last , but no one have it
Click to expand...
Click to collapse
Yeah the update note appears to be up but as you mentioned it's not been released yet to any channel. So for now the latest firmware we have is the Feb 2018 build.
echo92 said:
If you want to avoid wiping your data whilst flashing the fastboot stock ROM, you can omit the 'fastboot erase userdata' command and you do not have to re-lock your bootloader (re-locking will wipe your data).
However, if you are experiencing instabilities as you mentioned, a data wipe is a useful troubleshooting step, and may help you determine if your data is corrupted or whether you may have a more serious hardware/firmware issue.
Click to expand...
Click to collapse
Can i use this below commands. Also my bootloader is already locked, I have not unlocked the bootloader. Should I have to add any addtional command to above script like fastboot oem lock begin command.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
[STRIKE]fastboot erase userdata[/STRIKE]
fastboot erase customize
fastboot erase clogo
fastboot reboot
hardythaker said:
Can i use this below commands. Also my bootloader is already locked, I have not unlocked the bootloader. Should I have to add any addtional command to above script like fastboot oem lock begin command.
<Snip>
Click to expand...
Click to collapse
Okay, as your bootloader is locked, there's no need for the OEM lock commands. Using them, regardless of if your bootloader is locked or not, will erase your data.
Those commands look okay, just ensure in your flashing script that you have that erase userdata command removed (not just struck out). Your command list a look like:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
If this flash doesn't get your device going, you may have to wipe your data or consider a service repair as a locked bootloader gives us limited options for rescue.
echo92 said:
Okay, as your bootloader is locked, there's no need for the OEM lock commands. Using them, regardless of if your bootloader is locked or not, will erase your data.
Those commands look okay, just ensure in your flashing script that you have that erase userdata command removed (not just struck out). Your command list a look like:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
If this flash doesn't get your device going, you may have to wipe your data or consider a service repair as a locked bootloader gives us limited options for rescue.
Click to expand...
Click to collapse
Thanks mate. Am going to flash this tomorrow. Will surely let you know the outcome. Anyway if all this allow me to use my phone at least for an hour, I will take the backup of the necessary data and then will proceed with wipe data/factory reset.
echo92 said:
Okay, as your bootloader is locked, there's no need for the OEM lock commands. Using them, regardless of if your bootloader is locked or not, will erase your data.
Those commands look okay, just ensure in your flashing script that you have that erase userdata command removed (not just struck out). Your command list a look like:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
If this flash doesn't get your device going, you may have to wipe your data or consider a service repair as a locked bootloader gives us limited options for rescue.
Click to expand...
Click to collapse
Okay so I have flash the phone using above commands, but no luck, exact same issue is persists and even nothing has been changed on the phone, not even lock screen wallpaper.
So now do you have any more suggestion please let me know if not will proceed with Data Wipe. Also Even if I wipe user data and after that can I recover files using some Andrioid File Recovery Tools out there.
Waiting for your reply and will proceed as you will suggest. Thanks.
hardythaker said:
Okay so I have flash the phone using above commands, but no luck, exact same issue is persists and even nothing has been changed on the phone, not even lock screen wallpaper.
So now do you have any more suggestion please let me know if not will proceed with Data Wipe. Also Even if I wipe user data and after that can I recover files using some Andrioid File Recovery Tools out there.
Waiting for your reply and will proceed as you will suggest. Thanks.
Click to expand...
Click to collapse
That's not good, if a flash doesn't fix things.
1)Try to wipe your data via a factory reset. I think you can try to keep your internal storage by selecting to only wipe userdata in the stock recovery (boot to recovery, hold the power key then press the volume up key to get past the 'No Command screen', then under wipe data/factory reset, there should be an option to wipe userdata only). Then wipe cache/Dalvik in that same menu, and see if your device boots. I do not know if file recovery tools will work on non-rooted devices (due to restrictions on reading the data partition).
2)If that doesn't work, your device may have a serious hardware fault that only a service centre can resolve.
echo92 said:
That's not good, if a flash doesn't fix things.
1)Try to wipe your data via a factory reset. I think you can try to keep your internal storage by selecting to only wipe userdata in the stock recovery (boot to recovery, hold the power key then press the volume up key to get past the 'No Command screen', then under wipe data/factory reset, there should be an option to wipe userdata only). Then wipe cache/Dalvik in that same menu, and see if your device boots. I do not know if file recovery tools will work on non-rooted devices (due to restrictions on reading the data partition).
2)If that doesn't work, your device may have a serious hardware fault that only a service centre can resolve.
Click to expand...
Click to collapse
Okay so seems like am in serious trouble.
1) Done wipe data (user data only) with no luck.
2) Done wipe data with userdata and personalized content, still...
3) Flash stock ROM along with "Fastboot Erase userdata", but no joy.
Should I unlock the bootloader now and try to install TWRP and from there if I can go some where
And now I have kept the phone on Welcome Screen, its not getting rebooted, Am able to go till Select WIFI, even am able to connect to WIFI. Then on next screen it is asking me to "Accept Moto T&C", after that it will show me Checking Connectivity > Checking For Update > Checking Info.......and this is the point where it get restarted. Can you guess what is the issue, seems like its some network or connectivity hardware issue.
hardythaker said:
Okay so seems like am in serious trouble.
1) Done wipe data (user data only) with no luck.
2) Done wipe data with userdata and personalized content, still...
3) Flash stock ROM along with "Fastboot Erase userdata", but no joy.
Should I unlock the bootloader now and try to install TWRP and from there if I can go some where
And now I have kept the phone on Welcome Screen, its not getting rebooted, Am able to go till Select WIFI, even am able to connect to WIFI. Then on next screen it is asking me to "Accept Moto T&C", after that it will show me Checking Connectivity > Checking For Update > Checking Info.......and this is the point where it get restarted. Can you guess what is the issue, seems like its some network or connectivity hardware issue.
Click to expand...
Click to collapse
You'd only be able to unlock your bootloader if you enabled OEM unlocking in Settings>Developer Options, and you can only get to Developer Options if you can properly boot into the system (as a security measure)....
Hmm, if it's holding on the Setup Assistant now, can you use mobile data to set up instead of Wi-Fi? If it is an issue with the Wi-Fi, maybe using the mobile signal could get around that.
echo92 said:
You'd only be able to unlock your bootloader if you enabled OEM unlocking in Settings>Developer Options, and you can only get to Developer Options if you can properly boot into the system (as a security measure)....
Hmm, if it's holding on the Setup Assistant now, can you use mobile data to set up instead of Wi-Fi? If it is an issue with the Wi-Fi, maybe using the mobile signal could get around that.
Click to expand...
Click to collapse
Tried with mobile data too, but still same issue. Anyway am in service center now let's see what they say.
echo92 said:
You'd only be able to unlock your bootloader if you enabled OEM unlocking in Settings>Developer Options, and you can only get to Developer Options if you can properly boot into the system (as a security measure)....
Hmm, if it's holding on the Setup Assistant now, can you use mobile data to set up instead of Wi-Fi? If it is an issue with the Wi-Fi, maybe using the mobile signal could get around that.
Click to expand...
Click to collapse
Okay so after one-month of stupidity from service center and some other guys finally I myself resolved the issue.
1) Service center tried to flash the rom but didn't resolved the issue.
2) They changed the battery, but still the same issue.
3) They said that this is motherboard issue and it will cost 5200 INR.
Then gave my phone on yaantra .com to repair it they kept the phone for 5 days and said the same thing that it is a motherboard issue as network circuit is not working properly.
( In between this I end up buying OnePlus 6 :victory: :victory: )
Then I bought one new damaged phone in which motherboard was working fine. I replaced that motherboard with mine and still the same issue. After this I started disconnecting parts one by one which are there on display pannel. After checking speaker, vibrator, flash, when I disconnected the fingerprint sensor and rebooted the phone it was totally fine and no more reboots.
I never thought that a corrupted/damaged fingerprint scanner can do this kind of wired issue to a phone. .Now this will be a spare phone without fingerprint scanner. Thanks for your help @echo92