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
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
I rooted my G4 on 6.0 Now just flash back to stock rom and upgrade to 7.0 Build NPJ25.93-14. I also did "fastboot oem lock" to lock the bootloader. But it still comes up when I restart my phone.
Anyone has any idea how I can remove that unlocked bootloader. Now I can not use android pay for my Amex offer now.
What i had to do to get the bootloader to relock was to reinstall the stock firmware again. the worst part is, that the one that was from the Moto factory image site didnt work for me, so i had to use this https://androidfilehost.com/?fid=312978532265364350
Keep in mind that this will erase everything on the device, so make sure to backup your data.
just do this manually
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot oem lock
fastboot oem lock
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunck.0
fastboot flash system system.img_sparsechunck.1
fastboot flash system system.img_sparsechunck.2
fastboot flash system system.img_sparsechunck.3
fastboot flash system system.img_sparsechunck.4
fastboot flash system system.img_sparsechunck.5
fastboot flash system system.img_sparsechunck.6
fastboot flash system system.img_sparsechunck.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot oem lock
fastboot reboot
zonggestsu said:
i had to use this https://androidfilehost.com/?fid=312978532265364350
Keep in mind that this will erase everything on the device, so make sure to backup your data.
Click to expand...
Click to collapse
Can I use this image on model XT1622 (16gb DUAL-sim)
HTCZ715E said:
Can I use this image on model XT1622 (16gb DUAL-sim)
Click to expand...
Click to collapse
Im not certain, but would assume no. that being said however, it looks like Moto made all G4 and G4+ varients use the same software, with the exception of the G4 Play. If you do decide to try this, dont flash the bootloader, gpt, NON-HLOS, and fsg, so that going back wont be too painful.
I have unlocked bootloader. Now I need to unlock the tethering. Apparently it is done by editing the build prop. Instructions will be appreciated.
BTW I had rooted the phone with the Tool kit, the camera had stopped working, so I reinstalled the OEM ROM November update, now the root and TWRP are gone and the camera is working again..
TIA
goodjuju said:
I have unlocked bootloader. Now I need to unlock the tethering. Apparently it is done by editing the build prop. Instructions will be appreciated.
BTW I had rooted the phone with the Tool kit, the camera had stopped working, so I reinstalled the OEM ROM November update, now the root and TWRP are gone and the camera is working again..
TIA
Click to expand...
Click to collapse
Tethering is down to your carrier, some allow it others block it, the phone itself allows tethering natively, or have I misunderstood your question.
It depends entirely on how the carrier is restricting tethering... if they doing by MAC/traffic analysis there is nothing you can do. If they are doing it by just the provisioning flag, you can edit your build.prop and change "net.tethering.noprovisioning" to true. Then may need to change make a change from a su terminal shell, "settings put global tether_dun_required 0". But again, this all depends on how your carrier is blocking tethering.
Thanks Acejavelin. That's exactly the info I was looking for.
I don't see a "net.tethering.noprovisioning" line in the build prop. Should I insert the line? Any specific location in the build prop? Should the line read "net.tethering.noprovisioning=true"
TIA
goodjuju said:
Thanks Acejavelin. That's exactly the info I was looking for.
I don't see a "net.tethering.noprovisioning" line in the build prop. Should I insert the line? Any specific location in the build prop? Should the line read "net.tethering.noprovisioning=true"
TIA
Click to expand...
Click to collapse
Yes, just add it at the bottom, the order isnt important.
Got the tethering to work. But it reverted back when I tried to relock the bootloader and installed the stock ROM. Checked the build.prop sure enough the added line vanished. Is there a way to make it stick?
goodjuju said:
Got the tethering to work. But it reverted back when I tried to relock the bootloader and installed the stock ROM. Checked the build.prop sure enough the added line vanished. Is there a way to make it stick?
Click to expand...
Click to collapse
You mean to relock with a modified system file? No. Even if you found a way to lock the bootloader with a modified file, it would then fail to boot due to other security measures in Linux.
Thanks Ace. Not savvy enough to understand what you mean. But this is what I did -
1. Use the following relock commands -
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 boot boot.img
fastboot oem lock
2. Then reflashed the stock ROM using -
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 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
Both processes are from other posts here in XDA.
goodjuju said:
Thanks Ace. Not savvy enough to understand what you mean. But this is what I did -
1. Use the following relock commands -
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 boot boot.img
fastboot oem lock
2. Then reflashed the stock ROM using -
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 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
Both processes are from other posts here in XDA.
Click to expand...
Click to collapse
The process of writing system sparce chunks over-write your changes... You can't have a modified build.prop and a locked bootloader. I don't know how to be more clear.
Thanks again Ace! Now I got it. Only reason to relock was to get the OTA updates. I can live without it. I have a question - Since the sparce chuncks overwrite the changes wouldn't installing updates via TWRP or fastboot also overwrite the build.prop changes? Sorry to be a pain but I am learning.
goodjuju said:
Thanks again Ace! Now I got it. Only reason to relock was to get the OTA updates. I can live without it. I have a question - Since the sparce chuncks overwrite the changes wouldn't installing updates via TWRP or fastboot also overwrite the build.prop changes? Sorry to be a pain but I am learning.
Click to expand...
Click to collapse
Having an unlocked bootloader only does not stop OTA updates, but the OTA scrupt makes several checks and I know one of them if build.prop file, the OTA will fail even if that is the only change you have made.
OTA's can only be installed in a PURELY stock device, stock recovery and stock /system partition, other than that the bootloader locked/unlocked status is not relevant. Your only real choice here is to return to stock, accept the OTA, then make the change again.
acejavelin said:
Having an unlocked bootloader only does not stop OTA updates, but the OTA scrupt makes several checks and I know one of them if build.prop file, the OTA will fail even if that is the only change you have made.
OTA's can only be installed in a PURELY stock device, stock recovery and stock /system partition, other than that the bootloader locked/unlocked status is not relevant. Your only real choice here is to return to stock, accept the OTA, then make the change again.
Click to expand...
Click to collapse
Thanks again Ace! I think instead of returning to stock every time for OTA update it will be simpler to do ZIP updates when they are made available here at XDA. Having the modified build.prop is more useful to me.
Hi, Adding this line will work for at&t blocker in G5S plus ?
Thx in advance.
alejomj said:
Hi, Adding this line will work for at&t blocker in G5S plus ?
Thx in advance.
Click to expand...
Click to collapse
What do you mean "AT&T blocker"? Don't most AT&T plans include tethering?
And will it work? Maybe, depends how they are enforcing it.
I have buyed a straight talk sim, it has 3 options att/virgin/tmobile and i choose att but when i went to use tehering it said "account not setup for mobile hotspot". But problem solved rooting the g5s plus and editing the file system/build.prop it works perfect. Thx a lot
Someone managed to get the RSD Secure link for the FASTBOOT files of the final Oreo 8.1 release for RETAIL Moto G5/cedric.
With these files you'll be able to update to official oreo, relock your bootloader or simply go back to stock.
Using the guide I'll write below you'll be able to flash it from Linux, Windows and MacOS.
The new firmware is named OPP28.85-16 and Blur Version listed within the firmware package is:
Code:
Blur_Version.28.41.15.cedric.retail.en.US
whereas the OTA file for the corresponding Firmware lists it as:
Code:
Blur_Version.25.361.10.cedric.retail.en.US
I dont know which is "correct", but anyways, this should not alter your results when flashing this with fastboot.
DOWNLOAD
Gdrive: https://drive.google.com/file/d/1gNB7vNM8xH5ueTPKh5Qwev87gJpSpyyK/view?usp=sharing
RSD Secure: https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
FLASHING IT
If your seeing this post long after Setember 2018 it may be the case you have updated your firmware past this one and got a different bootloader version, in that case, make sure to check you bootloader version is BELOW B8.31. Flashing bootloader of equal or minor version will hardbrick your device
UPDATING FROM PREVIOUS ANDROID VERSION
1. If you're on Windows/Mac, download motorola USB drivers here. (You shouldn't need these on Linux)
2. Download Android Platform Tools (ADB & Fastboot ) for Windows/Mac/ Linux here (if you're on Linux, get these from your distro's repo instead).
3. Extract the platform tools somewhere
4. Extract the firmware's ZIP too (I recommend extracting it to the same directory as platform tools, this will make your life easier).
5.Open a command prompt/terminal where you extracted platform tools (To do that on windows, Hold SHIFT + right Click some blank area within platform-tools directory, then click "Open Command Prompt Here".
6. Reboot into fastboot (power off and connect USB while holding Vol Down) and Execute the following commands
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
7. Reboot your phone by typing fastboot reboot or by selecting the "START" option in phone's screen and then pressing the power button
PS: Do not execute commands related to erasing the modemst1 and modemst2 partitions. This has been related to people losing their IMEI's.
RELOCKING YOUR BOOTLOADER
edit
Seems like my instructions on how to relock didn't work, but I want to thank Andrej_SK, who managed to do it and posted instructions on how to do it. Just remember that you should Not flash bootloader if you're already on B8.31 or past it. Flashing gpt.bin can also hardbrick your phone and there have been reports of it happening here on XDA and on telegram. I personally didn't flash it when moving from NPPS25.137-93-2-5 and had no problem at all, and I think you shouldn't too, unless you know you absolutely need it (which I think is unlikely, since the partition scheme looks the same on both nougat and Oreo)
Andrej_SK said:
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
Try this (on your own risk only): input "fastboot oem lock" twice (first time for starting the whole process of locking, second time for confirmation). Then, execute commands below, one by one
Code:
fastboot flash oem oem.img
fastboot flash boot boot.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
Then, input "fastboot oem lock" for the last time. Your phone should immediately reboot, as mine did. If there will be problem with booting into OS, just reflash the whole system with commands below:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img (do not flash this if you're on B8.31 or further, so as not to hardbrick the device)
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 system system.img_sparsechunk.8
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
Click to expand...
Click to collapse
DOWNGRADING FROM A FIRMWARE NEWER THAN OPP28.85-16
1. Follow steps one 1 up to five described in the first section UPDATING FROM PREVIOUS ANDROID VERSION
2. Omit these lines from step 6:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Notice that omitting these two lines is VERY IMPORTANT if you're downgrading, otherwise you'll hardbrick your device.
3.7. Reboot your phone by typing fastboot reboot or by selecting the "START" option in phone's screen and then pressing the power button
That's it. If you liked, press thanks
Ps: some of my friends have reported phone is rebooting right after flashing sparsechunk.5.
phone will apparently boot normally and show the setup wizard screen, but in actuality there will be missing files on the system partition.
in that case, reboot into fastboot and finish flashing the system normally, then boot your phone
Thank you very much! Excuse me if I'm wrong but with this file it's safe to install Oreo from stock Nuggat right? I just need to unlock the bootloader and flash normally?
Thank, you to provide the firmware.
On another thread (https://forum.xda-developers.com/g5...eo-8-1-0-release-opp28-t3849273/post77771786) you wrote it's necessary to be on firmware NPPS25.137-93-2-5. Maybe you forgot to mention that!?
I believe the two threads are separate updates. One being OTA and this thread being fastboot firmware. I was wondering if this would work on my Moto g5 xt1670 (137-93-8)?
Woooow
Thanks
Ahasverus said:
Thank you very much! Excuse me if I'm wrong but with this file it's safe to install Oreo from stock Nuggat right? I just need to unlock the bootloader and flash normally?
Click to expand...
Click to collapse
no need to unlock BL to flash this. If you're on stock Nougat just make sure you're on NPPS25.137-93-2-5 (July security patch), then grab the ota here and sideload or flash it using the stock recovery
if you're not on NPPS25.137-93-2-5 then you'll need to flash it before flashing the ota.
AndroidenKalle said:
Thank, you to provide the firmware.
On another thread (https://forum.xda-developers.com/g5...eo-8-1-0-release-opp28-t3849273/post77771786) you wrote it's necessary to be on firmware NPPS25.137-93-2-5. Maybe you forgot to mention that!?
Click to expand...
Click to collapse
if you're going to install it from fastboot there's no need to be on NPPS25.137-93-2-5
TWRP v3.2.3.0 for Cedric: works
Magisk v17.1: works (don't use safetynet)
Thank you very much for this! I've been using the soak Oreo and could not be happier until this thread, time for the final Oreo for my beloved G5.
Blur_Version.28.41.15 for OPP28.85-16 is correct!
I'm on the 2nd soak test update OPP28.85-13 and tried the OTA update from your other post. This failed due to wrong version (E3002) since it expects the last NPPS25.137-93-2-5 version.
How can I update from OPP28.85-13 to the latest OPP28.85-16 via fastboot flash without losing my current data and settings?
Can I flash without "erase userdata"?
The thing I don't like in your instructions is lack of DDR errase command.
Please explain your point. Also please compare with flashfile.xml from Oreo firmware.
PsyClip-R said:
The thing I don't like in your instructions is lack of DDR errase command.
Please explain your point. Also please compare with flashfile.xml from Oreo firmware.
Click to expand...
Click to collapse
So "fastboot erase ddr" command should be included while flashing stock Oreo through fastboot? What does that command do?
I am on amzin software channel and my build number is NPPS25.137-93-14 (July Security Patch). Will this fastboot method work for me?
Hello,
the bootloader locking seems not to be working. At the last "fastboot oem lock" it says that it needs a signed boot.img. Has anyone else experienced this issue ?
achintyakv said:
I am on amzin software channel and my build number is NPPS25.137-93-14 (July Security Patch). Will this fastboot method work for me?
Click to expand...
Click to collapse
I don't think so since this is definitely a retail version.
BUILD REQUEST INFO:
SW Version: cedric-user 8.1.0 OPP28.85-16 0400 release-keysM8937_22.29.02.70R
MBM Version: B8.31
Modem Version: M8937_22.29.02.70R
FSG Version: FSG-8937-02.65.33
Build Fingerprint: motorola/cedric/cedric:8.1.0/OPP28.85-16/0400:user/release-keys
CQATest App Version: 6.0.6
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 28.41.15.cedric.retail.en.US
Model Number: Moto G (5)
Android Version: 8.1.0
Baseband Version: M8937_22.29.02.70R
Build Id: OPP28.85-16
SW Display Build ID: OPP28.85-16
Build Date: Wed Sep 5 09:46:09 CDT 2018
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.28.41.15.cedric.retail.en.US
Version when read from CPV: cedric-user 8.1.0 OPP28.85-16 0400 release-keys
slsmaster said:
Hello,
the bootloader locking seems not to be working. At the last "fastboot oem lock" it says that it needs a signed boot.img. Has anyone else experienced this issue ?
Click to expand...
Click to collapse
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
Try this (on your own risk only): input "fastboot oem lock" twice (first time for starting the whole process of locking, second time for confirmation). Then, execute commands below, one by one
Code:
fastboot flash oem oem.img
fastboot flash boot boot.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
Then, input "fastboot oem lock" for the last time. Your phone should immediately reboot, as mine did. If there will be problem with booting into OS, just reflash the whole system with commands below:
Code:
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 system system.img_sparsechunk.8
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
Edit: as you can see at the screenshots in the attachment, I'm able to lock bootloader with this firmware. First, I reflashed the whole Oreo firmware, then rebooted into bootloader using "fastboot reboot-bootloader" command and at last I tried to relock bootloader which was (once again) successful.
Phone specs: XT1676 (3/16), DualSIM, reteu soft. channel
Andrej_SK said:
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
......
......
Click to expand...
Click to collapse
Thank you very much, worked like a charm.
need cedric amzin oreo update before was on soak oreo ,after upate this phone stay in fastboot mode
PsyClip-R said:
The thing I don't like in your instructions is lack of DDR errase command.
Please explain your point. Also please compare with flashfile.xml from Oreo firmware.
Click to expand...
Click to collapse
never heard about this command before, I have never used it ever and I flashed this firmware without any problem so far
Andrej_SK said:
So "fastboot erase ddr" command should be included while flashing stock Oreo through fastboot? What does that command do?
Click to expand...
Click to collapse
As I said above, I and other people I know who flashed this didn't have any problem by flashing without typing "fastboot erase DDR" and in fact I'm curious to know what does this command do.
JoeDoe0 said:
Blur_Version.28.41.15 for OPP28.85-16 is correct!
I'm on the 2nd soak test update OPP28.85-13 and tried the OTA update from your other post. This failed due to wrong version (E3002) since it expects the last NPPS25.137-93-2-5 version.
How can I update from OPP28.85-13 to the latest OPP28.85-16 via fastboot flash without losing my current data and settings?
Can I flash without "erase userdata"?
Click to expand...
Click to collapse
I think it's very unlikely anyone has this OPP25.85-16, otherwise it would've already surfaced somewhere.
(edit)
seems like I was wrong, I just reflashed the firmware and managed to keep my data by not using fastboot erase user data.
(/edit)
regarding the "fastboot erase user data" it doesn't matter if you use it or not, since once you flash all sparse chunks you'll lose your data partition anyways.
what I'd suggest you to do is
1.backup your data partition using twrp and your internal storage to a pc/sdcard/whatever (twrp doesn't backup your internal storage)
2. flash the firmware just as described on the main thread
3 fastboot boot twrp.img PRIOR to the first boot
4. restore your data
5. connect your phone to USB cable with twrp still open and copy back your internal storage through TWRP's MTP(or use twrp's file manager/aroma FM in case you backed internal storage to sd card)
5. boot your phone.
I never tried backing up internal storage but I already did this when fastbooting and managed to keep my data (settings, apps, etc) .
I just advice you to remove any screen lock prior to backing up your data since your previous pattern/pin/password generally won't work after restoring a twrp backup, but in case you forget it use twrp and go to /data/system and delete locksettings.db and your
lock screen protection will be gone
achintyakv said:
I am on amzin software channel and my build number is NPPS25.137-93-14 (July Security Patch). Will this fastboot method work for me?
Click to expand...
Click to collapse
I don't know, this could brick your phone, but I'm not sure
tapan8914 said:
need cedric amzin oreo update before was on soak oreo ,after upate this phone stay in fastboot mode
Click to expand...
Click to collapse
as I said idk what'd happen if someone did this. the best you can do now is to find some old amzin firmware and fastboot it (do not flash gpt.bin or bootloader.bin, so as not to hard brick your device)
Andrej_SK said:
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
Try this (on your own risk only): input "fastboot oem lock" twice (first time for starting the whole process of locking, second time for confirmation). Then, execute commands below, one by one
Code:
fastboot flash oem oem.img
fastboot flash boot boot.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
Then, input "fastboot oem lock" for the last time. Your phone should immediately reboot, as mine did. If there will be problem with booting into OS, just reflash the whole system with commands below:
Code:
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 system system.img_sparsechunk.8
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
Edit: as you can see at the screenshots in the attachment, I'm able to lock bootloader with this firmware. First, I reflashed the whole Oreo firmware, then rebooted into bootloader using "fastboot reboot-bootloader" command and at last I tried to relock bootloader which was (once again) successful.
Phone specs: XT1676 (3/16), DualSIM, reteu soft. channel
Click to expand...
Click to collapse
many a thanks, I'll put this on the main thread
Currently on OPP28.85-3
Currect me if I'm wrong, but by what I have been reading,
I cant go from OPP28.85-3 to OPP28.85-16
What I've read, I can't be on bootloader B8.31 (which I am) and since this isn't a "full system" image, just a "patch" for official Nougat to upgrade to offical Oreo, I need to be on Nougat.
If this is the case, could I go back to nougat through a TWRP Zip, or would this need to be done through fastboot commands. I know I need a downgraded Bootloader and I don't think ROM flashing affects anything else but /system
PLEASE correct me if I'm wrong. Just a curious guy who loves learning.