Hi firmware experts! I have been working on getting a Turbo 2 working after water damage for the last couple of weeks. I am not an expert on any of this, so learning is where most of the time has gone.
After the rice drying, etc, the phone was in bootloop. I tried reflashing firmware, and I finally was able to successfully flash stock 6.0.1, but the phone remained in bootloop. I took the phone apart, removed a bunch of EMI shields, and scrubbed the components with 91% isopropyl, put it back together, and it booted right up. All tested components worked perfectly, ..... that is until I tried to activate the phone on a network. That's when I realized the cellular radio isn't working (wifi and bluetooth radios are intact).
Indications that cellular radio is non-functional:
*after activation attempt, phone call attempts result in the phone telling me to turn airplane mode off when it is off already
*sim card is being read but network signal not showing in notification bar or other such places
*under sim status in the settings the 'Service state' reads "Voice: Radio off / Data: Radio off" with an active sim card in the phone, rather than "Voice: In service..." or "Voice: Out of service..." as a Turbo I used for comparison displays
I'm not ruling out that there could be water induced damage to the cellular circuitry, but it seems strange and unfortunate that that would be the only issue that would remain. I'm wondering if I messed up the modem firmware during flashing.
Here is my most recent flash sequence with 6.0.1 (I believe I downloaded from mirrors.lolinet.com):
Code:
fastboot getvar max-sparse-size
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 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 system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash modem NON-HLOS.bin
fastboot flash bluetooth BTFM.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
I didn't have any errors.
Is there a chance that I flashed a firmware from another region (I'm US) and that is the prob? I've tried flashing earlier stock firmwares I can find, ie. 5.1.1 but I get 'preflash validation failed',presumably because by bootloader won't let me downgrade.
XT1585_KINZIE_VERIZON_6.0.1_MCK24.183-22_cid2_subsidy-DEFAULT_CFC.xml
Would it be a good idea to try 'fastboot flash modem NON-HLOS.bin' or fsg by itself? Maybe I could try to just flash the modem and fsg from another package, which I think the bootloader might let me do.
I've read that you want to have a backup of the EFS, but it doesn't seem like you can without root, which I don't think I can do with my locked bootloader? I do still have an IMEI.
I am trying everything I can to get this working, any help is greatly appreciated. If you guys say it's no chance of a software fix then I'll go back into the phone and check the antenna connector and remove the rest of the EMI shields and scrub what's underneath, but I don't want to do this until I am more sure it isn't a software issue because I don't want to take the chance of breaking things in there when it wasn't necessary.
Thanks a ton!
No Radio
implausibleg said:
Hi firmware experts! I have been working on getting a Turbo 2 working after water damage for the last couple of weeks. I am not an expert on any of this, so learning is where most of the time has gone.
After the rice drying, etc, the phone was in bootloop. I tried reflashing firmware, and I finally was able to successfully flash stock 6.0.1, but the phone remained in bootloop. I took the phone apart, removed a bunch of EMI shields, and scrubbed the components with 91% isopropyl, put it back together, and it booted right up. All tested components worked perfectly, ..... that is until I tried to activate the phone on a network. That's when I realized the cellular radio isn't working (wifi and bluetooth radios are intact).
Indications that cellular radio is non-functional:
*after activation attempt, phone call attempts result in the phone telling me to turn airplane mode off when it is off already
*sim card is being read but network signal not showing in notification bar or other such places
*under sim status in the settings the 'Service state' reads "Voice: Radio off / Data: Radio off" with an active sim card in the phone, rather than "Voice: In service..." or "Voice: Out of service..." as a Turbo I used for comparison displays
I'm not ruling out that there could be water induced damage to the cellular circuitry, but it seems strange and unfortunate that that would be the only issue that would remain. I'm wondering if I messed up the modem firmware during flashing.
Here is my most recent flash sequence with 6.0.1 (I believe I downloaded from mirrors.lolinet.com):
Code:
fastboot getvar max-sparse-size
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 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 system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash modem NON-HLOS.bin
fastboot flash bluetooth BTFM.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
I didn't have any errors.
Is there a chance that I flashed a firmware from another region (I'm US) and that is the prob? I've tried flashing earlier stock firmwares I can find, ie. 5.1.1 but I get 'preflash validation failed',presumably because by bootloader won't let me downgrade.
XT1585_KINZIE_VERIZON_6.0.1_MCK24.183-22_cid2_subsidy-DEFAULT_CFC.xml
Would it be a good idea to try 'fastboot flash modem NON-HLOS.bin' or fsg by itself? Maybe I could try to just flash the modem and fsg from another package, which I think the bootloader might let me do.
I've read that you want to have a backup of the EFS, but it doesn't seem like you can without root, which I don't think I can do with my locked bootloader? I do still have an IMEI.
I am trying everything I can to get this working, any help is greatly appreciated. If you guys say it's no chance of a software fix then I'll go back into the phone and check the antenna connector and remove the rest of the EMI shields and scrub what's underneath, but I don't want to do this until I am more sure it isn't a software issue because I don't want to take the chance of breaking things in there when it wasn't necessary.
Thanks a ton!
Click to expand...
Click to collapse
I have the same problem, water damage, replaced the screen and now no radio. Not sure on what Rom i orginaly was before. The sim works but no signal
Had the same thing.
You're using file XT1585_KINZIE_VERIZON_6.0.1_MCK24.183-22_cid2_subsidy-DEFAULT_CFC.xml
There is a different version, for the model with an "S" in it.
Try file name: XT1585_KINZIE_VERIZON_6.0.1_MCKS24.183-22_cid2_subsidy-DEFAULT_CFC.xml
This worked for me for XT1580
i need help, same exact issue. anyone?
Related
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
Hello folks. I need help getting back to stock firmware on my Moto G4 Plus Indian Variant (xt1643). I have flashed resurrection remix that's on android 7.1.2. I tried to flash the stock firmware (november 1, 2016 security build) through fastboot. As soon as I entered the command to flash the stock boot image, I get a pre-flash validation error message and had to abort the flashing procedure immediately. I was on the latest march build before flashing resurrection remix. I don't know how to go about with it and need to get back to stock firmware asap. Any help is always appreciated.
Thanks in advance,
Krishna16
I am running resurrection remix (7.1.2) on my moto g4 plus currently and have an unlocked bootloader and twrp recovery installed.
Krishna16 said:
I am running resurrection remix (7.1.2) on my moto g4 plus currently and have an unlocked bootloader and twrp recovery installed.
Click to expand...
Click to collapse
If you previously were on the March 2017 security build (should be NPJS25.93-14.4), you may wish to download this stock ROM, which is the latest build that we have available (NPJS25.93-14.4, March 2017 security patch). https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 This stock ROM thread also has scripts to help you flash, though you may wish to edit them to match the commands below. You may also verify if you're on the latest firmware previously by booting to your bootloader - I recall the March 2017 bootloader version is B1.05.
Regardless, you're likely getting that pre-flash validation error due to an attempt of flashing an older bootloader and/or attempting to relock your bootloader with an older firmware. You can only relock your bootloader with firmware of the same build you had previously or newer.
I'd suggest using the latest stock firmware, and provided you were on the March 2017 update previously, omit flashing the GPT and bootloader partitions (whether you're using the latest stock build or your November build - just keep those partitions as they are):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
You may also wish to omit the locking commands if you don't wish to lock your bootloader. Your commands should look therefore like:
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 erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
If you wish to relock your bootloader, use the commands as follows (if the commands complain of needing a signed image, try booting into your flashed stock system, toggle OEM Unlock in Developer Settings and re-flash the stock ROM with the re-locking commands)
Code:
fastboot oem lock begin
fastboot oem lock begin
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 (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
I've used the 1st list of flashing commands - the non-locking version - to revert from RR 5.8.3 27/05/2017 to the stock NPJS25.93-14.4 ROM on my XT1642 without issue (apart from the unlocked bootloader warning). Be aware that re-flashing a stock ROM will wipe your device clean (including internal storage) and may result in your SD card being non-functional until wiped. Back up your important data accordingly (you may wish to use Titanium Backup to preserve your app data), and transfer backups off your device until you have flashed.
EDIT - tweaked a couple of sentences for clarity.
echo92 said:
If you previously were on the March 2017 security build (should be NPJS25.93-14.4), you may wish to download this stock ROM, which is the latest build that we have available (NPJS25.93-14.4, March 2017 security patch). https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 This stock ROM thread also has scripts to help you flash, though you may wish to edit them to match the commands below. You may also verify if you're on the latest firmware previously by booting to your bootloader - I recall the March 2017 bootloader version is B1.05.
Regardless, you're likely getting that pre-flash validation error due to an attempt of flashing an older bootloader and/or attempting to relock your bootloader with an older firmware. You can only relock your bootloader with firmware of the same build you had previously or newer.
I'd suggest using the latest stock firmware, and provided you were on the March 2017 update previously, omit flashing the GPT and bootloader partitions (whether you're using the latest stock build or your November build - just keep those partitions as they are):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
You may also wish to omit the locking commands if you don't wish to lock your bootloader. Your commands should look therefore like:
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 erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
If you wish to relock your bootloader, use the commands as follows (if the commands complain of needing a signed image, try booting into your flashed stock system, toggle OEM Unlock in Developer Settings and re-flash the stock ROM with the re-locking commands)
Code:
fastboot oem lock begin
fastboot oem lock begin
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 (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
I've used the 1st list of flashing commands - the non-locking version - to revert from RR 5.8.3 27/05/2017 to the stock NPJS25.93-14.4 ROM on my XT1642 without issue (apart from the unlocked bootloader warning). Be aware that re-flashing a stock ROM will wipe your device clean (including internal storage) and may result in your SD card being non-functional until wiped. Back up your important data accordingly (you may wish to use Titanium Backup to preserve your app data), and transfer backups off your device until you have flashed.
EDIT - tweaked a couple of sentences for clarity.
Click to expand...
Click to collapse
I am out of words to thank you??. Thanks a lot for your efforts and time echo92. I still have a perpetual problem and that is my speaker volume is too low while playing YouTube videos. Is there a way to fix that??
now should i update from marshmello to nougat???
after reverting back to stock?
sarang25 said:
now should i update from marshmello to nougat???
after reverting back to stock?
Click to expand...
Click to collapse
No. You must flash nougat with latest security patch
sarang25 said:
now should i update from marshmello to nougat???
after reverting back to stock?
Click to expand...
Click to collapse
If you previously had stock Nougat (doesn't matter about custom ROM Nougat) before reverting back to Marshmallow stock, I too would recommend you flash the latest stock Nougat via fastboot. For India, Brazil, EU and UK devices, that stock ROM is the NPJS25.93-14-18 firmware ( https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 )
We've seen previously that attempting to use OTA updates on a device with downgraded stock firmware (again, does not matter what custom ROM you had, what matters is what stock ROM builds you had flashed previously and now) can hard brick your device. Thus, if you want to update, using OTA updates can be potentially risky. Safest way is to use fastboot flashes to update.
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
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.
As per title, after doing some custom rom flashes of android 10 I wanted to return to stock. I did the usual procedure for the moto g6 plus but the end result is buggy and can't read sim or wifi. Bootloader works, i can flash stuff and return to stock but the end result is that sim and wifi don't work.
I'm using stock rom EVERT_PPW29.116-20 and this command list to flash it (i tried a lot of combinations with a, b and nothing):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_b system_other.img
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Also, I have a EFS backup done before the problem, but it does nothing when restored. I also tried blank flash method but it won't flash, it says <waiting for device> indefinitely.
EDIT: After flashing the latest stock rom Wifi works. Sim is detected but IMEI is 0. I can't find a way to repair it on the forum, there's a nice guide about it but it's for the g5 plus.
Possible Solution
VincentVG93 said:
As per title, after doing some custom rom flashes of android 10 I wanted to return to stock. I did the usual procedure for the moto g6 plus but the end result is buggy and can't read sim or wifi. Bootloader works, i can flash stuff and return to stock but the end result is that sim and wifi don't work.
I'm using stock rom EVERT_PPW29.116-20 and this command list to flash it (i tried a lot of combinations with a, b and nothing):
Also, I have a EFS backup done before the problem, but it does nothing when restored. I also tried blank flash method but it won't flash, it says <waiting for device> indefinitely.
EDIT: After flashing the latest stock rom Wifi works. Sim is detected but IMEI is 0. I can't find a way to repair it on the forum, there's a nice guide about it but it's for the g5 plus.
Click to expand...
Click to collapse
If you have a backup of IMEI, Persist, EFS, try to recover it, that is why many dev suggest to make a backup first, if you dont have it, to install many custom roms, it should recover sim and Wifi, its not Hardware problem, is flashing problems, i can suggest to:
1. Install a custom Rom with ADB Sideload (Lineage OS, Xtasis, Resurrection, etc) after the first boot, go to twrp and wipe/Format Data, in this case literally idk why, but fixes al Rom problems, after it, boot your phone, check if custom Rom detects Sim at least, if it works, install your stock Rom with Fastboot. Also sorry if my english sounds weird but is not my native language, i try to help people!