Dear Team, I have MotoG4 Plus (Model XT1643).
Post selecting the data migration from internal storage to SD card, the phone stopped booting.
[[ Upon pressing the vol + power key ]] __
Restart bootloader screen shows
*oem_locked
*Software status: Modified (in yellow) __
Navigating to Bootloader logs screen, it shows
*failed to validate boot image
*ERROR: failed to pass validation, backup to fastboot Fastboot Reason: Fall-through from charger boot mode
Kindly suggest
Hmm, what were you trying to do prior to the soft boot? You mentioned data migration, how were you transferring data?
Given your bootloader is locked (OEM_locked), then something's corrupted your boot kernel and thus the bootloader isn't letting your device boot, as it can't verify your stock kernel signatures.
You may have to re-flash your stock ROM - can you remember which stock ROM build you had on your device?
chetana22 said:
Dear Team, I have MotoG4 Plus (Model XT1643).
Post selecting the data migration from internal storage to SD card, the phone stopped booting.
[[ Upon pressing the vol + power key ]] __
Restart bootloader screen shows
*oem_locked
*Software status: Modified (in yellow) __
Navigating to Bootloader logs screen, it shows
*failed to validate boot image
*ERROR: failed to pass validation, backup to fastboot Fastboot Reason: Fall-through from charger boot mode
Kindly suggest
Click to expand...
Click to collapse
Are u using dummy bootloader I guess not orginal
---------- Post added at 07:32 PM ---------- Previous post was at 07:26 PM ----------
No need to reflash u have to upgrade the bootloader then u have to flash the stock rom
@ Echo
Hmm, what were you trying to do prior to the soft boot? You mentioned data migration, how were you transferring data?
<<<< I was transferring data from phone memory to memory card via an option which says move media to SD card >>>>
Given your bootloader is locked (OEM_locked), then something's corrupted your boot kernel and thus the bootloader isn't letting your device boot, as it can't verify your stock kernel signatures.
You may have to re-flash your stock ROM - can you remember which stock ROM build you had on your device?
<<<< I have no idea about stock ROM build. If you can help, how would I know since my device is not starting? >>>>
@ usha55
Are u using dummy bootloader I guess not orginal
<<<< I do not know >>>>
---------- Post added at 07:32 PM ---------- Previous post was at 07:26 PM ----------
No need to reflash u have to upgrade the bootloader then u have to flash the stock rom
<<<< How do I upgrade? Please guide >>>>
@chetana22 thas makes confusion if you write post like that.
You just need to reflash boot.img only not whole ROM. To know the correct version of ROM and boot.img, post your phone's baseband/bootloader version, which is visible on bootloader screen.
____Mdd said:
@chetana22 thas makes confusion if you write post like that.
You just need to reflash boot.img only not whole ROM. To know the correct version of ROM and boot.img, post your phone's baseband/bootloader version, which is visible on bootloader screen.
Click to expand...
Click to collapse
Hi.
Im not able to upload the image. Pl. find baseband details below.
Baseband: M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST
Pls let me know steps to reflash boot.img
chetana22 said:
Hi.
Im not able to upload the image. Pl. find baseband details below.
Baseband: M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST
Pls let me know steps to reflash boot.img
Click to expand...
Click to collapse
If you have locked bootloader, flashing of older boot.img may not work. You need to flash whole firmware.
See here,
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138/page8
Download it and flash it, instructions are given there.
If you have important data on your phone, say photos/videos/or any file, then skip "erase userdata" command.. when you get device working, copy your data and then wipe your device.
Tried the method as given.
At the end ..it is repeatedly showing
FAILED (remote failure)
chetana22 said:
Tried the method as given.
At the end ..it is repeatedly showing
FAILED (remote failure)
Click to expand...
Click to collapse
Which stock firmware are you flashing that gives you this error? Please mention the build number.
You may have to try flashing with the NPJS25.93-14-10 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash as per below commands if you want to save your data (no need to re-lock your bootloader).
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 reboot
It does not work
echo92 said:
Which stock firmware are you flashing that gives you this error? Please mention the build number.
You may have to try flashing with the NPJS25.93-14-10 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash as per below commands if you want to save your data (no need to re-lock your bootloader).
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 reboot
Click to expand...
Click to collapse
It does not work
al3al3al3jandr0 said:
It does not work
Click to expand...
Click to collapse
What didn't work, please describe more about what happened?
From your other post, I saw that gpt and bootloader worked. Did you ensure that all the firmware files in your ADB folder are from the same patch? Some of them appear to have different dates. I would delete all the firmware files in your ADB folder (except your minimal ADB filled) and extract a fresh copy of the stock ROM to your ADB folder and try again. Double check you're extracting the NPJS25.93-14-10 ROM.
Now the error sends it to me in the boot.img
echo92 said:
What didn't work, please describe more about what happened?
From your other post, I saw that gpt and bootloader worked. Did you ensure that all the firmware files in your ADB folder are from the same patch? Some of them appear to have different dates. I would delete all the firmware files in your ADB folder (except your minimal ADB filled) and extract a fresh copy of the stock ROM to your ADB folder and try again. Double check you're extracting the NPJS25.93-14-10 ROM.
Click to expand...
Click to collapse
Now organize the original firmware and download the December OTA, replace the gpt.bin file with the OTA one. Now the error sends it to me in the boot.img
al3al3al3jandr0 said:
Now organize the original firmware and download the December OTA, replace the gpt.bin file with the OTA one. Now the error sends it to me in the boot.img
Click to expand...
Click to collapse
1) Why are you adding the December 2017 GPT.bin to the NPJS25.93-14-10 flash files? Mixing and matching patch levels especially with you re-locking the bootloader can be very risky, and could result in you bricking your device.
2)Are you getting the same error with flashing the boot.img? Can you confirm with an md5 checksum tool (http://www.winmd5.com/ ) that your boot.img (the kernel) has the md5 checksum: 61473507904cc98b5dcc508a1a35e657 If the checksum is different, I urge you again to doublecheck you've copied the right files from the stock ROM. If you're re-locking, you generally must have only the flash files from the same stock ROM patch level, you cannot mix and match old and new stock ROMs.
Again, if you're not sure, delete all the stock ROM files from your folder and re-extract clean, fresh copies from the stock ROM zip.
3)If you've updated to NPJS25.93-14-13 previously via OTA update (the December 2017 stock ROM), then you cannot use this method to re-lock your bootloader and flash the stock ROM. The stock ROM used to re-lock a Motorola device must be of the same build/newer than what you had on your device. You'd have to wait for the NPJS25.93-14-13 stock ROM.
thank you
echo92 said:
1) Why are you adding the December 2017 GPT.bin to the NPJS25.93-14-10 flash files? Mixing and matching patch levels especially with you re-locking the bootloader can be very risky, and could result in you bricking your device.
2)Are you getting the same error with flashing the boot.img? Can you confirm with an md5 checksum tool (http://www.winmd5.com/ ) that your boot.img (the kernel) has the md5 checksum: 61473507904cc98b5dcc508a1a35e657 If the checksum is different, I urge you again to doublecheck you've copied the right files from the stock ROM. If you're re-locking, you generally must have only the flash files from the same stock ROM patch level, you cannot mix and match old and new stock ROMs.
Again, if you're not sure, delete all the stock ROM files from your folder and re-extract clean, fresh copies from the stock ROM zip.
3)If you've updated to NPJS25.93-14-13 previously via OTA update (the December 2017 stock ROM), then you cannot use this method to re-lock your bootloader and flash the stock ROM. The stock ROM used to re-lock a Motorola device must be of the same build/newer than what you had on your device. You'd have to wait for the NPJS25.93-14-13 stock ROM.
Click to expand...
Click to collapse
ok thank you very much, you're right I'll have to wait
Sir, how to fix no found bootimage in m0t0 g4plus XT1643
Adityashankar said:
Sir, how to fix no found bootimage in m0t0 g4plus XT1643
Click to expand...
Click to collapse
Did this happen suddenly, and is this with the stock firmware or using a custom ROM?
You could try flashing the Oreo stock firmware: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Hello team, I have the same problem like chetana22 but with motorola one xt-1941-4. When i was transfering (probably) virus file from internal storage to usb flash memory, the phone stopped booting.
I have inportant and private files on internal storage, phone have quarantee... What can i do? Pls help
flash latest stock rom and skip the following instruction while flashing
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
MOTOROLA G5S PLUS - Start up failed
My phone is G5s PLUS ... Sorry
Hi All,
Moto G4 Plus XT1643 is my phone model.
Was not being used for past 6 months, and it got stuck the boot screen .
Tried the factory reset, it got stuck in the fast boot.
Then tried the tool given by Lenovo, no luck. The "fast boot" option in the software fails.
Anyway, came to our good old XDA.
tried the options in the forum https://forum.xda-developers.com/t/...c-01-security-patch-fastboot-7-0-8-1.3608138/
Now, i am stuck with the below screens, i have attached them
Allso, do i need to start a separate thread?
Kindly help me out.
Related
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 a Moto G4 (XT1625) Unlocked with 32GB of storage. Bootloader Unlocked and TWRP Bootloader or Recovery, IDK how to word it, but I attempt to update from Android 6.0.1 to Android 7 and the update fails. When the device reboots it reboots into the TWRP Recovery Menu. How do I proceed. Please help.
Haven't used adb, drivers, or anything and cannot seem to remember the process. Any pointers in the right direction are appreciated. Thank you.
Update 1: I am able to boot into TWRP 3.0.2-0 and see files on my MicroSD. However I downloaded a .ZIP file that was suppose to be the Nougat factory image and when I went to flash it, it says "Installing zip file.... could not find 'META-INF/COM/GOOGLE/ANDROID/UPDATE-BINARY' in the zip file. Error installing zip file."
Update 2: Can someone confirm that I would need to first somehow remove TWRP in order to update? How do I remove TWRP and get phone back to FULL STOCK.
Okay, accepting OTA updates requires a stock recovery (as you've discovered), stock kernel and unmodified system. Furthermore, the stock Nougat zip that you've downloaded needs to be extracted on your computer and flashed via fastboot, it's not flashable in TWRP.
If you're wanting to update and update to the latest Nougat build (which for US devices - XT1625 and XT1644 - appears to be NPJ25.93-14.5, June 2017), the easiest way is to download the stock Nougat ROM from here: https://www.androidfilehost.com/?fid=673368273298984458 . Download to your computer and extract the files. This build is for retail US (non-Amazon devices), with a retus software channel as listed in Settings>About Phone.
Then follow the instructions here, but using the above NPJ25.93-14.5 stock ROM instead. https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Beware that this process may erase your data in the process, so back up as necessary. If you do not wish to erase your data, then you can use the following fastboot commands instead of the commands in the guide. Back up anyway and you may have to factory reset (thus losing your data) if your device is not stable. Also, either process will remove TWRP, root and any other modifications. Xposed is still not officially released for Nougat. It is up to you if you choose to re-lock your bootloader or not (of course, re-locking the bootloader will prevent you from flashing TWRP/root/any other modifications).
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 reboot
pause
One word of warning, once you have formally updated to June 2017 (B1:06 bootloader), do not attempt to downgrade and accept OTA updates. You may wish to downgrade, but I don't recommend it - if you forget to not accept OTA updates, you may hard brick your device. If you think you'll forget, do not downgrade.
My moto g4 plus, model XT1643 was hardbricked, i installed blank flash on it, it has rebooted into bootloader mode of blankflash with no android logo, and has locked oem of my phone. I cannot install a stock rom now as the oem is locked and when unlocking oem from cmd prompt its asking me to enable oem from from developer options, which i cannot do as my mobile is not booting. Please help as to how can i install stock rom into it as my bootloader and oem is locked now. Any help would be appreciated, thanks.
tried to pass the last stock if I am not mistaken version that is or updated passes without being with bootloader unlocked.
Pranav_dp said:
My moto g4 plus, model XT1643 was hardbricked, i installed blank flash on it, it has rebooted into bootloader mode of blankflash with no android logo, and has locked oem of my phone. I cannot install a stock rom now as the oem is locked and when unlocking oem from cmd prompt its asking me to enable oem from from developer options, which i cannot do as my mobile is not booting. Please help as to how can i install stock rom into it as my bootloader and oem is locked now. Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Following a blankflash, you can only boot into the bootloader, which is normal. It seems that using a blankflash sets your bootloader to be locked, regardless of if it was previously unlocked in the first place. Provided you can flash a stock ROM, your bootloader should become unlocked again.
Have you tried flashing the April 2018 fastboot stock ROM from https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ? The guide there should be useful in how to reflash stock firmware to your device, and as it's the newest firmware that has been leaked, should rescue your device.
If you want to keep your bootloader unlocked and try to save your data, then try the following flashing commands instead of the ones in the guide. Be aware that you may have to factory reset your device should it boot but be unstable.
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 reboot
These commands should flash the April 2018 GPT, bootloader, system and modem to your device. Please try to avoid hardbricks in the future by only flashing stock firmware as new or newer than your bootloader, and please do not use old OTA updates.
echo92 said:
Following a blankflash, you can only boot into the bootloader, which is normal. It seems that using a blankflash sets your bootloader to be locked, regardless of if it was previously unlocked in the first place. Provided you can flash a stock ROM, your bootloader should become unlocked again.
Have you tried flashing the April 2018 fastboot stock ROM from https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ? The guide there should be useful in how to reflash stock firmware to your device, and as it's the newest firmware that has been leaked, should rescue your device.
If you want to keep your bootloader unlocked and try to save your data, then try the following flashing commands instead of the ones in the guide. Be aware that you may have to factory reset your device should it boot but be unstable.
These commands should flash the April 2018 GPT, bootloader, system and modem to your device. Please try to avoid hardbricks in the future by only flashing stock firmware as new or newer than your bootloader, and please do not use old OTA updates.
Click to expand...
Click to collapse
Thank you so much, I've restored the stock rom following your guidelines, my phone is working fine but im not able to install any OTA updates after that. Should i just skip any OTA updates from now on, please advice. Thank you.
Pranav_dp said:
Thank you so much, I've restored the stock rom following your guidelines, my phone is working fine but im not able to install any OTA updates after that. Should i just skip any OTA updates from now on, please advice. Thank you.
Click to expand...
Click to collapse
If you flashed the April 2018 security patch stock firmware, there are currently no OTA updates, the April 2018 security patch is the latest available.
If you fully flashed the latest firmware as I mentioned, you should be okay to use OTA updates. Just in future please remember to not use OTA updates if you downgraded your device by flashing old stock firmware.
i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?
Daroas said:
i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?
Click to expand...
Click to collapse
Without a blankflash new enough to flash to the device, I don't think so. You'd have to consider a JTAG repair, a motherboard replacement or buy a new device.
Hi! I currently have NPNS25.137-92 running thanks to a TWRP backup I did before going custom Pie on my G5+. I'd like to go back to stock so that TWRP is removed, bootloader locked and I can take official OTAs up to Oreo or whatever it is. What is the best way to achieve this? I could flash the latest Oreo TWRP flashable build, but that way it won't accept OTAs right?
Any help will be greatly appreciated.
Cheers
guillermohs9 said:
Hi! I currently have NPNS25.137-92 running thanks to a TWRP backup I did before going custom Pie on my G5+. I'd like to go back to stock so that TWRP is removed, bootloader locked and I can take official OTAs up to Oreo or whatever it is. What is the best way to achieve this? I could flash the latest Oreo TWRP flashable build, but that way it won't accept OTAs right?
Any help will be greatly appreciated.
Cheers
Click to expand...
Click to collapse
First thing: You don't have to lock the bootloader to receive and install OTA, this is a widespread fallacy.
And yes, with a TWRP flashable build you won't be able to apply OTA updates.
To get back on track you will have to flash a full fastboot ROM, best would be the latest one available for your region.
Firmwares can be found here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Oreo builds for the US are ending on 85-17-x (where 17-4 is the latest), for other regions it's 85-13-x , here the latest one is 85-13-5 (December security patch).
You will lose your data so backup your stuff.
Wolfcity said:
First thing: You don't have to lock the bootloader to receive and install OTA, this is a widespread fallacy.
And yes, a TWRP flashable build won't be able to apply OTA updates.
To get back on track you will have to flash a full fastboot ROM, best would be the latest one available for your region.
Firmwares can be found here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Oreo builds for the US are ending on 85-17-x (where 17-4 is the latest), for other regions it's 85-13-x , here the latest one is 85-13-5 (December security patch).
Click to expand...
Click to collapse
Thanks for your answer, I'm looking but I guess firmwares for my region (retar) are difficult to find. Flashing retus won't affect the usage? Finally, to flash that image you must unzip it and paste that long chunk of fastboot commands I've seen around here right?
guillermohs9 said:
Thanks for your answer, I'm looking but I guess firmwares for my region (retar) are difficult to find. Flashing retus won't affect the usage? Finally, to flash that image you must unzip it and paste that long chunk of fastboot commands I've seen around here right?
Click to expand...
Click to collapse
No, flashing the US variant won't affect usage. It's possible that you don't receive OTA updates in the future anymore because the ones pushed in your region may be for the other update channel. Would be good to find out which Oreo build has been pushed to your region, maybe you can elaborate it via Google.
Yes, you have to unzip the firmware in your adb/fastboot folder on your PC and enter all fastboot commands, you can also use a flashall.bat with all commands in it. You have to copy that bat into your adb/fastboot folder too and just click it.
Here's one:https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
There are some tutorials around how to do it all but some are a bit outdated. I'm about to write an actual one.
You need Motorola drivers on your PC:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=sharing
and something like Minimal Adb & Fastboot:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=sharing
If you're not familiar with this procedure you can also give Lenovo Motorola Smart Assistant a shot:
https://support.lenovo.com/de/de/downloads/ds101291
Wolfcity said:
No, flashing the US variant won't affect usage. It's possible that you don't receive OTA updates in the future anymore because the ones pushed in your region may be for the other update channel. Would be good to find out which Oreo build has been pushed to your region, maybe you can elaborate it via Google.
Click to expand...
Click to collapse
I'm searching for images for retar channel but with no luck. Having flashed retus image, won't I be getting OTA updates pushed on retus?
You should write that tutorial, there is no such thing as too many well written tutorials!
I'm comfortable using fastboot and adb, I just never used them to go back to stock and finding the right firmware for potter seems hard for what I'm reading.
guillermohs9 said:
I'm searching for images for retar channel but with no luck. Having flashed retus image, won't I be getting OTA updates pushed on retus?
You should write that tutorial, there is no such thing as too many well written tutorials!
I'm comfortable using fastboot and adb, I just never used them to go back to stock and finding the right firmware for potter seems hard for what I'm reading.
Click to expand...
Click to collapse
I'll take a look what firmware has been pushed to your region. If you're on the wrong update channel you won't receive OTA updates because Motorola/Lenovo only pushes one update for every location, either the US version (17-x) or the other one (13-x).
I'm writing on that guide but it will be a bit extensive because it should cover unlocking/flashing/rooting/decrypting/locking, the whole thing.
Sorry for interrupting but I would like you have your advise.
I returned from custom pie to 8.1 stock flashed through fastboot. I'm from Belgium, I took the build OPS28.85-17. Reteu channel. This is sept 18 security patch.
I don't receive an ota for an updated security patch.
How can I flash OPS28.85-17-4 without losing data? With some fastboot commands? Wich ones? Tnx for help:good:
BartKey said:
Sorry for interrupting but I would like you have your advise.
I returned from custom pie to 8.1 stock flashed through fastboot. I'm from Belgium, I took the build OPS28.85-17. Reteu channel. This is sept 18 security patch.
I don't receive an ota for an updated security patch.
How can I flash OPS28.85-17-4 without losing data? With some fastboot commands? Wich ones? Tnx for help:good:
Click to expand...
Click to collapse
No need to apologize for interrupting, this is not a private chat. 17-4 is the US firmware, you'll have to change to OPS28.85-13-x to receive OTA updates here in Europe. Even when your "about phone" setting tells you you're on reteu, the firmware number is what makes the difference.
If your main goal is not to lose your data you can flash the 17-4 firmware by fastboot and omit the line "erase userdata". But you still won't receive future OTA updates as you're on the wrong firmware. You can try to flash the latest available fastboot firmware for Europe which is OPS28.85-13-3 and omit the "erase userdata" line too. The source for the firmwares is posted above, it's https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
As written above, a guide how to do it will follow.
The fastboot commands are the same as in the flashall.bat also posted above:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I flashed the retus Oreo firmware you suggested with the commands you uploaded to Dropbox but upon rebooting I get a "No command" screen and it's stuck there.
Edit: flashed Twrp now it says "bad key" on the unlocked device screen but it boots into stock Oreo.
I get the thing about the region. The device still says it's on retar so with retus firmware it will not take OTAs if I understood correctly.
guillermohs9 said:
I flashed the retus Oreo firmware you suggested with the commands you uploaded to Dropbox but upon rebooting I get a "No command" screen and it's stuck there.
Click to expand...
Click to collapse
Have you omitted the "erase userdata" line?
If that screen appears the device seems to be waiting for a reboot.
Edit: Ok, good to hear it's booting now.
The " bad key" screen is normal, you should have seen it after unlocking the bootloader.
Wolfcity said:
Have you omitted the "erase userdata" line?
If that screen appears the device seems to be waiting for a reboot.
Edit: Ok, good to hear it's booting now.
The " bad key" screen is normal, you should have seen it after unlocking the bootloader.
Click to expand...
Click to collapse
It used to say N/A instead. I don't mind. The problem now is that it always tries to boot into recovery.
guillermohs9 said:
....
I get the thing about the region. The device still says it's on retar so with retus firmware it will not take OTAs if I understood correctly.
Click to expand...
Click to collapse
As I said, depends on which firmware has been rolled out in your country.
What's your actual firmware number?
wolfcity said:
as i said, depends on which firmware has been rolled out in your country.
What's your actual firmware number?
Click to expand...
Click to collapse
opss28.85-17-4
guillermohs9 said:
opss28.85-17-4
Click to expand...
Click to collapse
Ok, that's the latest US build, so it can't find OTA now. Btw I don't think that we will see too many updates as the Moto G5+ isn't that new anymore so it's not such a big thing.
I haven't found out which firmware is the right one for your country, if I find out something I'll let you know.
As you said, no need to care about the bad key screen, I just flashed a custom bootlogo to get rid of it.
About booting into recovery, here's a thread about it: https://forum.xda-developers.com/showthread.php?p=74109609#post74109609
First try to wipe cache/dalvik in TWRP.
Than try enter "fastboot oem fb_mode_clear" from PC.
If that doesn't help try the mentioned dd commands from the thread in TWRP terminal.
It's a known problem.
Wolfcity said:
Ok, that's the latest US build, so it can't find OTA now. Btw I don't think that we will see too many updates as the Moto G5+ isn't that new anymore so it's not such a big thing.
I haven't found out which firmware is the right one for your country, if I find out something I'll let you know.
As you said, no need to care about the bad key screen, I just flashed a custom bootlogo to get rid of it.
About booting into recovery, here's a thread about it: https://forum.xda-developers.com/showthread.php?p=74109609#post74109609
First try to wipe cache/dalvik in TWRP.
Than try enter "fastboot oem fb_mode_clear" from PC.
If that doesn't help try the mentioned dd commands from the thread in TWRP terminal.
It's a known problem.
Click to expand...
Click to collapse
Thanks! I figured the same about the future updates, now Motorola is focused on newer devices so december security patch is enough.
I am on stock, unrooted, relocked bootloader now. I used the commands you provided (included erase userdata) then had to flash TWRP, flash magisk, use adb shell and dd to clear that misc partition (so it boots into system), and finally did
fastboot oem lock
fastboot oem lock
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 system system.img_sparsechunk.8
fastboot flash boot boot.img
fastboot oem lock
to relock bootloader. It works as expected now and it's ready to be used by anyone.
Thanks a lot
Wolfcity said:
No need to apologize for interrupting, this is not a private chat. 17-4 is the US firmware, you'll have to change to OPS28.85-13-x to receive OTA updates here in Europe. Even when your "about phone" setting tells you you're on reteu, the firmware number is what makes the difference.
If your main goal is not to lose your data you can flash the 17-4 firmware by fastboot and omit the line "erase userdata". But you still won't receive future OTA updates as you're on the wrong firmware. You can try to flash the latest available fastboot firmware for Europe which is OPS28.85-13-3 and omit the "erase userdata" line too. The source for the firmwares is posted above, it's https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
As written above, a guide how to do it will follow.
The fastboot commands are the same as in the flashall.bat also posted above:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thanks a lot @Wolfcity
I came from OPS28.85-17, without updates available.
Now I flashed OPS28.85-13 with your instructions not to erase userdata.
Checking for updates: 13.3 available -> installed
13.5 available -> installed and "up to date" security patch dec 2018
:good:
@guillermohs9 @BartKey: Great to hear everything is working! I will add your experiences to the upcoming tutorial.
I received an update Oreo, when I tried to install it failed and displayed a message "Error" and restarted. Help me to update my mobile to latest version. I cleared cache partition, still no luck.
I have unlocked bootloader and on latest stock ROM.
Screenshot attached !!!
ksamm97 said:
I received an update Oreo, when I tried to install it failed and displayed a message "Error" and restarted. Help me to update my mobile to latest version. I cleared cache partition, still no luck.
I have unlocked bootloader and on latest stock ROM.
Screenshot attached !!!
Click to expand...
Click to collapse
Flash the complete stock rom using fastboot and lock the bootloader and then update the device through OTA.
ksamm97 said:
I received an update Oreo, when I tried to install it failed and displayed a message "Error" and restarted. Help me to update my mobile to latest version. I cleared cache partition, still no luck.
I have unlocked bootloader and on latest stock ROM.
Screenshot attached !!!
Click to expand...
Click to collapse
Facing the exact same issue here.I think the latest stock oreo needs locked bootloader to flash
No need to relock the bootloader, but you must revert back to unmodified stock firmware on your device before updating. Without seeing what error it is, it's difficult to say. A locked bootloader strictly enforces having the unmodified stock furnace, which is why an OTA update is more likely to work.
Try this:
1) download the NPJS25.93-14-18 firmware from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Only use this if you have not updated to Oreo and you are still on NPJS25.93-14-18.
2)unzip the fastboot ROM, delete any old stock ROMs from your ADB folder and copy the stock ROM over.
3) assuming you had NPJS25.93-14-18 already on your device, flash the firmware with the following instructions - no need for the GPT/bootloader. Ensure you have your data backed up, as you may have to factory reset if you encounter instability.
Code:
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 reboot
That should get your device into an OTA friendly state without erasing your data. If that doesn't work, I suggest waiting for the Oreo fastboot ROM.
I've custom Oreo installed on my phone. Which firmware package should I install?
echo92 said:
No need to relock the bootloader, but you must revert back to unmodified stock firmware on your device before updating. Without seeing what error it is, it's difficult to say. A locked bootloader strictly enforces having the unmodified stock furnace, which is why an OTA update is more likely to work.
Try this:
1) download the NPJS25.93-14-18 firmware from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Only use this if you have not updated to Oreo and you are still on NPJS25.93-14-18.
2)unzip the fastboot ROM, delete any old stock ROMs from your ADB folder and copy the stock ROM over.
3) assuming you had NPJS25.93-14-18 already on your device, flash the firmware with the following instructions - no need for the GPT/bootloader. Ensure you have your data backed up, as you may have to factory reset if you encounter instability.
Code:
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 reboot
That should get your device into an OTA friendly state without erasing your data. If that doesn't work, I suggest waiting for the Oreo fastboot ROM.
Click to expand...
Click to collapse
tobey_onk said:
I've custom Oreo installed on my phone. Which firmware package should I install?
Click to expand...
Click to collapse
At the moment, we only have the stock Nougat firmware to revert to - Oreo firmware doesn't seem to be out yet. However, flashing stock Nougat over custom Oreo may appear to come with some risk of losing IMEI, so be careful. You could try the TWRP flashables, be aware the stock ROM is only 32 bit.