Database Users

[XT1063] downgrade to 21.11.17 4.4.4 then update to 22.21.28 5.0.2

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

Moto Z official firmware downloads

Rogers Canada
http://www.filefactory.com/file/386..._subsidy-RGRCA_regulatory-DEFAULT_CFC.xml.zip
Telus Canada
http://www.filefactory.com/file/3pe..._subsidy-TELUS_regulatory-DEFAULT_CFC.xml.zip
Retail Mexico
http://www.filefactory.com/file/50m...d50_subsidy-DEFAULT_regulatory-03_CFC.xml.zip
Retail Europe
http://www.filefactory.com/file/6ht...ubsidy-DEFAULT_regulatory-03_CFC_EMEA.xml.zip
Retail Canada
http://www.filefactory.com/file/3vz...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
? (Colombia)
http://www.filefactory.com/file/102...ubsidy-MOVSTLA_regulatory-DEFAULT_CFC.xml.zip
At&t Mexico
http://www.filefactory.com/file/3qf...sidy-IUSMXLA_regulatory-03_CFC_ATT_MX.xml.zip
Bell Canada
http://www.filefactory.com/file/57c...subsidy-BELLCA_regulatory-DEFAULT_CFC.xml.zip
Verizon
http://www.filefactory.com/file/662...MCL24.203-22_cid2_subsidy-DEFAULT_CFC.xml.zip
http://www.filefactory.com/file/1iq...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Retail China
http://www.filefactory.com/file/1ar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

great! You have the folder link in FileFactory?

Hello.
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25

Thank you.

Hello,
How to install the rom?
Thank you.

tonime said:
Hello,
How to install the rom?
Thank you.
Click to expand...
Click to collapse
Flash it manually using mfastboot command.

I have a doubt, i purchased a moto z with at&t México and flashed the retail firmware of this thread for my country and works fine, but when i enter in bootloader mode the info of the Phone shows that my Phone is a sheridan version, so i'm confused, what version i have? ��

nesgcmx said:
I have a doubt, i purchased a moto z with at&t México and flashed the retail firmware of this thread for my country and works fine, but when i enter in bootloader mode the info of the Phone shows that my iPhone is a sheridan version, so i'm confused, what version i have? ��
Click to expand...
Click to collapse
Probably Griffin. As others already reported, on bootloader mode all reports to be Sheridans... :fingers-crossed:

enetec said:
Probably Griffin. As others already reported, on bootloader mode all reports to be Sheridans... :fingers-crossed:
Click to expand...
Click to collapse
Moto Z has two product name.

alphaeva said:
Moto Z has two product name.
Click to expand...
Click to collapse
Yeah, just to make things more... confused!
We have Z, Force, Play, single sim, dual sim, Verizon's, unlocked, etc... we *really* need confused codename and product codes to help us on this...
Anyway @motorola they are surely fans of The Griffin's series..... Sheridan is the surname of the series' director...

Located the US firmware and uploaded it to Mega if anyone needs it https://mega.nz/#!vtVmgAoI!J1cZtlRi0FjRHbxIJGA5U8CLx6RwUWQjwrCbjzf_Naw

How do you "Flash it manually using mfastboot command."?

<redacted>
<How do you delete a post?>

SolusCado said:
How do you "Flash it manually using mfastboot command."?
Click to expand...
Click to collapse
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Keep in mind depending on the region you're flashing you may have a different number of sparse chunks (I think VZW has like 16, where as stock has like 13) You just enter the amount of sparse chunks you need to flash.

Prfndhatrdofman said:
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Keep in mind depending on the region you're flashing you may have a different number of sparse chunks (I think VZW has like 16, where as stock has like 13) You just enter the amount of sparse chunks you need to flash.
Click to expand...
Click to collapse
Thanks; that worked - though now I find that the pre-Rooted EU ROM I was using doesn't seem to work with my Hasselblad Camera Mod.

SolusCado said:
Thanks; that worked - though now I find that the pre-Rooted EU ROM I was using doesn't seem to work with my Hasselblad Camera Mod.
Click to expand...
Click to collapse
I would just root yourself then. I couldn't get systemless root to work with the current TWRP available so I just flashed a forced System ROOT instead.
http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Download from there and flash it in TWRP. But say goodbye to Android pay obviously

:/ Ok; try as I might I cannot seem to get my Moto Z to boot if I have SuperSU installed. My bootloader is unlocked, and I've been able to flash different ROMS with no problem. But if I try to install SuperSU (v2.78-SR1) to a working ROM, or install JanJan's pre-rooted US ROM, then Android simply never boots. I just downloaded the three more recent versions of SuperSU to give them a try, but does anyone have any suggestions of what I might be doing wrong here?

SolusCado said:
:/ Ok; try as I might I cannot seem to get my Moto Z to boot if I have SuperSU installed. My bootloader is unlocked, and I've been able to flash different ROMS with no problem. But if I try to install SuperSU (v2.78-SR1) to a working ROM, or install JanJan's pre-rooted US ROM, then Android simply never boots. I just downloaded the three more recent versions of SuperSU to give them a try, but does anyone have any suggestions of what I might be doing wrong here?
Click to expand...
Click to collapse
Sounds to me like you need a different Boot image then. I flashed the boot.img that was disabled force encryption, then flashed the System mode SuperSU. No issues at all. US Moto Z 64 GB model.

link to indian firmware...not able to download it as filefactory.com is restricted... tried via apn also still a no go...can anyone download it and upload it to other server??
http://www.filefactory.com/file/20s..._subsidy-DEFAULT_regulatory-XT1650-03.xml.zip

Prfndhatrdofman said:
Located the US firmware and uploaded it to Mega if anyone needs it https://mega.nz/#!vtVmgAoI!J1cZtlRi0FjRHbxIJGA5U8CLx6RwUWQjwrCbjzf_Naw
Click to expand...
Click to collapse
Do this have the modem (baseband) included?.. I need to completely put everything back to factory.
---------- Post added at 04:29 PM ---------- Previous post was at 04:21 PM ----------
dallas90733 said:
Do this have the modem (baseband) included?.. I need to completely put everything back to factory.
Click to expand...
Click to collapse
Nevermind- I didn't read

Any Wifi and data fixes on xt1625

I have a second Moto G4 and I was curious if anyone got a fix for these issues? it happened a while back when I was trying to go back to factory image. there was a lot of errors. I cant seem ti find the screenshots of the errors that I got at the time. This was around January or so.There is no Mac Address in settings and theres no ip no way to turn data on and when I try wifi. it automatically shuts off. Doesn't detect my Sim Card or Service. says Emergency calls only

I have the same problem, I have got the sim working but no wifi or bluetooth yet.
When I load adb shell and grep the wireless module it says "WCNSS DRIVER NOT FOUND" even though it is there.

I found fix. Delete the old os completely and have the right stock os ready to adb flash. Id say google ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml .. then put it in your minimal adb and fastboot file. go to bootloader and then back to computer to do the shift right click in the file on pc and get terminal up and copy and paste this
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash 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 userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Fastboot flash logo logo.bin
The fastboot restart the device and you should be back with the wifi and data. I bought a new phone in feb or march because of this issue and couldn't find a fix till I googled constantly.
I had to delete the os completely and then flash the factory boot image with
AArnold2 said:
I have the same problem, I have got the sim working but no wifi or bluetooth yet.
When I load adb shell and grep the wireless module it says "WCNSS DRIVER NOT FOUND" even though it is there.
Click to expand...
Click to collapse

NeroCZA said:
I found fix. Delete the old os completely and have the right stock os ready to adb flash. Id say google ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml .. then put it in your minimal adb and fastboot file. go to bootloader and then back to computer to do the shift right click in the file on pc and get terminal up and copy and paste this
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash 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 userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Fastboot flash logo logo.bin
The fastboot restart the device and you should be back with the wifi and data. I bought a new phone in feb or march because of this issue and couldn't find a fix till I googled constantly.
I had to delete the os completely and then flash the factory boot image with
Click to expand...
Click to collapse
What are the proper steps to completely remove your entire OS safely? Do you mean to just overwrite the current one?

This procedure overwrites your current or completely. You will lose the contents of the internal SD card
Sent from my LG-LS980 using Tapatalk

dayne.rhoades said:
What are the proper steps to completely remove your entire OS safely? Do you mean to just overwrite the current one?
Click to expand...
Click to collapse
Save what you want and it should be safe to just completely wipe your phone cache and all no overwrite.. Then have the stock ready to flash in the file on computer and do the the above steps. Ive done it on both my moto g4's because on my main one which I'm sending off to Motorola for screen repairs, I wiped my phone without thinking about the stock os. panicked but remembered the back to stock steps and attempted them. Ive always gotten errors or wifi and data wipe from over writing with the codes. So I just flashed on the one I deleted OS off of and it worked.

tekweezle said:
This procedure overwrites your current or completely. You will lose the contents of the internal SD card
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Yeah sadly you will lose everything unless you have it all saved. I was mad about losing a lot of things but I was having screen issues and data wifi issues to try to fix. I do have data and wifi now. I just wish I saved what I could.
Would the android data recovery program recover anything? Ive been searching how to recover wiped data. Internet is full of info on how wiped data can be recovered. I just want the text messages and stuff. I had important things in some the text messages I lost

You should save to the external SD card.
Sent from my LG-LS980 using Tapatalk

Delete the old OS via twrp?

You should have made a backup with twrp. Then you could restore your os as it was.
Sent from my Moto G (4) using Tapatalk

Nope the firmware linked above caused the phone to go in to a boot loop.

AArnold2 said:
Delete the old OS via twrp?
Click to expand...
Click to collapse
Yeah that's what I did. Then I flashed the stock rom I googled. Ive been trying to update to nougat for past 2 days since I got back to proper stock rom.

you can;t flash any of the official firmwares via TWRP. You can flash a custom rom or restore a backup of your OS though.
to flash/reload an official firmware, you need ADB and fastboot running from a computer.

Exactly. Don't try with TWRP.
tekweezle said:
you can;t flash any of the official firmwares via TWRP. You can flash a custom rom or restore a backup of your OS though.
to flash/reload an official firmware, you need ADB and fastboot running from a computer.
Click to expand...
Click to collapse

Fastboot rom for Moto G4 PLUS XT1643 NPJS25.93-14-15

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

[Getting Error while installing OTA]

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.