Related
Hello,
my Pixel XL came from T-Mobile Germany.
I am in TWRP alpha2 and SR4-SuperSU-v2.78-SR4.
My Pixel XL is on NDE63H.
I logged the OTA download process used the link in there and got now the 68MB small OTA.zip.
Can I use TWRP and this small update OTA to update to NDE63U,
or do I need to use the large 850MB OTA file from the google develope site to do so -> marlin-ota-nde63u-56d5b07a.zip?
I think I will loose root by using the large one, but will I loose TWRP as well?
My preference would be to use the small one, but will it work via TWRP and will I loose root as well or will this only update the necessary files?
Any help is highly appreciated.
mancman
I haven't tried it on the pixel, but on my previous Nexus device (N6), the small OTA would fail if the devices was rooted or had any changes to the system partition - that's because the small OTA was an incremental update, and was checking to see if the system partition was modified in any way before applying the OTA.
The full OTA would work - but you would lose the root/TWRP. Reinstalling TWRP is just a fastboot command away, so why is that a big deal?
Hello jj14,
I tried it.
First within TWRP and then by sideload and both failed with the same error.
I first needed to get a newer version of adb, but it failed as said above as well via sideload.
See error message here in the attached picture.
Any hint?
As far as that error, it means the binary update files are missing. That could be because the structure of OTA's changed. Without seeing the OTA I cannot say for sure. I would post that screenshot in the twrp thread and ask @Dees_Troy what he thinks.
Hello Scott,
thanks for your answer.
I wrote Dess a message.
Attached 2 screenshots which show what is in the zip from the OTA file and one for the comparison to a Nexus 10 zip,
you see that the update-binary is missing, so Goggle has changed things here as you postulated.
Thanks,
mancman
I assume you are trying to sideload the full OTA file. If so, what error did you get using the ADB sideload? (yes, you will need the newest version of ADB - download from the Google developers site). TWRP is still very new, so there may still be some bugs to address - Dees is pretty good about quick updates/fixes though.
I may be wrong here but shouldn't you flash back stock recovery before applying stock ota ??
Dear all
There are so many people looking for exactly samething that iam looking for but unfortunately there is not any proper tutorial available.
Could you confirm if there is anyway to install any other ROM on chinese moto z play ? i don't mind if i have to install each OTA manually.
If so could you please guide step by step guide how to perform this?
If there so no any ROM that can work with chinese variant is there any custom ROM that would and support Moto Mods?
You can read my thread: https://forum.xda-developers.com/moto-z-play/help/problem-reteu-firmwares-chinese-t3619235
Briefly:
1) If you unlock your bootloader you will be able to flash full image of any firmware throug fastboot (with ordinary instruction)
2) OTA at the moment can't be installed even manually due to different device name (addison_retcn vs addison)
I'm looking through different ways to fix device name with no luck at the moment (but I am sure it is possible)
freeman_g said:
You can read my thread: https://forum.xda-developers.com/moto-z-play/help/problem-reteu-firmwares-chinese-t3619235
Briefly:
1) If you unlock your bootloader you will be able to flash full image of any firmware throug fastboot (with ordinary instruction)
2) OTA at the moment can't be installed even manually due to different device name (addison_retcn vs addison)
I'm looking through different ways to fix device name with no luck at the moment (but I am sure it is possible)
Click to expand...
Click to collapse
Did you try editing build.prop?
jameelmemon said:
Did you try editing build.prop?
Click to expand...
Click to collapse
I see that you has not even tried to look through my thread (link was provided in previous post). Suggest to do that (espesially the very end) before further questions / discussion
I have gone through almost all threads including your befiore posting or asking you that question
you are referring to
2) target script is probably /device/company_name/device_name/init.device_name.usb.rc
3) there is a string in that script: write /sys/class/android_usb/android0/iProduct ${ro.product.model}
aactualy {ro.product.model} is variable in build.prop so that script (/device/company_name/device_name/init.device_name.usb.rc) from build.prop
Actually, not there. I have pushed build.prop with adb and has not found any signs of "addison_retcn" there
Hovewer AIDA64 (as well as adb once you try to sideload OTA) will display "addison_retcn" so it is somewhere else
I do not thing that script take the name from build.prop as, for example, it also obtains serial number with the same way and it is the first recommendation on recovering serial (in case it is lost during the some flashing procedure) to manually set it in that script
Finally i manage to install 7.1.1
My phone is addison after installing RETAIL version (7.0)
I installed RETAIL version then downloaded ota then installed 7.1.1 OTA from this thread https://forum.xda-developers.com/moto-z-play/how-to/official-android-7-1-1-download-how-to-t3616352
phone should not be locked/encrypted or protected at least i bricked it and it was not booting up.
Now need to change two things those are in bootloader (SKU and ro.carrier) fastboot getvar all
So just install retail version and sideload OTA through ADB?
I see that my phone is encrypted, shall I decrypt it first?
In any case any news on how you managed to boot 7.1.1 are appreciated
Just found ro.carrier comes from kernel and will be taken from kernel each time devices boots up. so we need someone to customize the kernel and add retru or retus to kernel as ro.carrier.
sku i can not change as i am getting error of command is not allowed
can anyone help regarding this?
So what is the result? You have managed to sideload 7.1.1 аnd it is not booting?
Or everything works fine and you tried to change SKU/channel for further updates?
freeman_g said:
Actually, not there. I have pushed build.prop with adb and has not found any signs of "addison_retcn" there
Hovewer AIDA64 (as well as adb once you try to sideload OTA) will display "addison_retcn" so it is somewhere else
I do not thing that script take the name from build.prop as, for example, it also obtains serial number with the same way and it is the first recommendation on recovering serial (in case it is lost during the some flashing procedure) to manually set it in that script
Click to expand...
Click to collapse
freeman_g said:
So just install retail version and sideload OTA through ADB?
I see that my phone is encrypted, shall I decrypt it first?
In any case any news on how you managed to boot 7.1.1 are appreciated
Click to expand...
Click to collapse
Just install fresh retail version then sideload first ota via adb then boot your phone do not complete setup.
then install 7.1.1 then do factory restore then you are good to go
and it have so many great features you can view them here specially camera app
freeman_g said:
So what is the result? You have managed to sideload 7.1.1 аnd it is not booting?
Or everything works fine and you tried to change SKU/channel for further updates?
Click to expand...
Click to collapse
Initally it didn't work and stuck on bootloader unlock warning but later it worked perfect and iam using 7.1.1 and now trying to figure out how we can change sku and channel to get official OTA.
Sku (XT1635-03) is in bootloader but i can't write is with Fastboot, channel (retcn) is in kernel.
Lucky you I still have the same problem
Yesterday I tried to start with flashing stock retail 7.0 (the link you have provided earlier) but due to fact I had already flashed image with April security patch I didn't manage to downgrade bootloader and gpt (security downgrade issue)
Despite this fact phone boots but small OTA with April security patch did not agree to flash for the same reason: wrong name "addison_retcn"
So I believe the problem is in bootliader and I will probably manage to fix it only with full 7.1.1 retail image.
Glad to see you guys are making some progress. I'll try flashing the retail version on my Chinese Z Play. I'm currently on Epsilon rom (stock rooted 7.0) with January patch. Can I flash retail and then the ota?
I woulf suggest the following:
1) At your current firmware install Aida64 and check if you have addison or addison_cn product name in System section. If you see only addison - then you may install retail firmware and OTAs
2) If you still have addison_cn here then try to install retail firmware provided above (bootloader can be upgraded) and then check product name in Aida64 again. If it changed to addison - you can sideload OTAs. If still addison_cn - then you can't
Thanks @freeman_g
Here is a screenshot of AIDA64 on my device: https://imgur.com/gallery/Or2JF
I guess I should be good to go, right?
Yes, should work
What I can't understand why I still with addison_retcn. Probably, will have to wait for full 7.1.1 retail image
Sorry for the noobie question, but how did you guys with XT1635-03 flash the XT1635-02 firmware? Did you use this script? Did you flash the full rom, including partition, fsg, and modem, no restrictions? I bought my device at Banggood. I know it will come with a shop rom and I would like to install the stock firmware. I want to be prepared when it arrives. Don't want to take the risk of brick it and would like to leave the custom roms for later.
Ok, I have finally found why some people (and myself) have problems with 7.1.1 OTA on xt1635-03
As I mentioned before, OTA just refuses to install mentioning wrong device name (addison_retcn vs addison)
The problem is standard instuction for flashing any firmware with fastboot missing these lines:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
After flashing these files I saw correct "addison" name in Aida64 and managed to install 7.1.1 OTA on my XT1635-03
People who use RSD Lite did not have such problem as this program use xml file contained both commands (oem and dsp)
It is better to have unlocked bootloader as at first attempt OTA was flashed with some mistake and the phone did not boot. After restoring full image (7.0) with fastboot I managed to sucessfully sideload OTA and now have 7.1.1 on my Chineese device.
Hope this helps
freeman_g said:
Ok, I have finally found why some people (and myself) have problems with 7.1.1 OTA on xt1635-03
As I mentioned before, OTA just refuses to install mentioning wrong device name (addison_retcn vs addison)
The problem is standard instuction for flashing any firmware with fastboot missing these lines:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
After flashing these files I saw correct "addison" name in Aida64 and managed to install 7.1.1 OTA on my XT1635-03
People who use RSD Lite did not have such problem as this program use xml file contained both commands (oem and dsp)
It is better to have unlocked bootloader as at first attempt OTA was flashed with some mistake and the phone did not boot. After restoring full image (7.0) with fastboot I managed to sucessfully sideload OTA and now have 7.1.1 on my Chineese device.
Hope this helps
Click to expand...
Click to collapse
Awesome, many thanks for sharing. Does this mean you'll receive future OTAs?
Hello all,
Follow my guide at your own risk. Read everything SUPER carefully to fix your Verizon LTE network connectivity on your US Retail unlocked Motorola G5 Plus.
I am here to save you all from flashing your phone countless times to try to bring back LTE with no EFS backup and no persist backup.
Here is a guide for XT1687 U.S. version of Moto G5+ (potter) that brings back Verizon LTE on STOCK Firmware/Rom and gives you OTA updates after downgrading from custom 8.1 Oreo roms.
I have not been able to relock bootloader, but that is okay. I am on stock firmware with OTA updates working and LTE working again.
Here is what I did:
I went ahead and flashed POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml to bring my phone back to stock from OMNI Rom 8.1 Oreo custom rom.
Obviously there is a bug that makes your IMEI 0 and loses all network connectivity after you flash back to stock from Oreo 8.1 64 bit roms on this phone.
1) Download the STOCK firmware/rom for XT1687 I used and extract the files: POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2.) Install ADB
https://forum.xda-developers.com/showthread.php?t=2588979
3)Extract the firmware to a folder using 7zip or right-click and extract all to folder in windows, then
4.) boot into your Moto G5+ bootloader by holding: Volume Down + Power button
Open a command prompt, copy and paste the following commands after installing ADB & Fastboot, make sure you launch command prompt or change directory to the same directory as the extracted rom files (cd C:/rom files):
You can type in CMD: fastboot devices to see if your device serial number shows up and you are ready to flash, make sure you are in bootloader mode first.
Paste the following commands in cmd prompt:
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 modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
Boot into your new stock rom now and use WIFI to update OTAs:
Make sure USB debugging is enabled > goto settings > click on build number 5 times then go back and goto developer options > usb debugging checked on
Your network connectivity will still be broken until we patch persist file but continue through the whole bootup for stock rom, set it up from new, and install all the OTA updates available through WIFI first.
5.) Install OTA updates over WIFI even though your network connectivity still doesn't work yet. Your IMEI will be 0 and you will have no network access.
Install all OTA updates with WIFI until your phone is on Build number: NPNS25.137-93-10, there is no firmware file to download this build, so it must be updated through OTA on wifi (all OTAs together should be ~300-500mb total).
6.)Download TWRP 3.2.1.0 and flash it using the following command: fastboot flash recovery twrp-3.2.1-0-potter.img:
https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html
7.) Go into TWRP > backup > check EFS so it creates a folder in your phone storage TWRP folder, and then copy it into to a folder on your computer for future backups.
8.) Download Persist file linked here and boot phone in bootloader mode, use PC to copy persist file into TWRP folder > Newly created EFS backup folder > Persist file in your phone storage:
Code:
[url="https://nofile.io/f/RuxbqZAQayH/persist.ext4.win"]https://nofile.io/f/RuxbqZAQayH/persist.ext4.win[/url]
9.) TWRP > restore > check EFS backup folder you made earlier with your new persist file in it (should be 193kb for persist file). > restore the backup for EFS & Persist > reboot phone once its done.
10.) Ta-dah! The Verizon LTE network signal should be instantly back after you rebooted your phone into android OS.
Let me know if it worked for you on other versions as well. Everything is at your own risk. It worked for me and I just flashed it today 06/20/2018.
Also, files are from other devs on XDA, just made the guide to highlight the process steps that worked for me.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
vwfan511 said:
Hello all,
Follow my guide at your own risk. Read everything SUPER carefully to fix your Verizon LTE network connectivity on your US Retail unlocked Motorola G5 Plus.
I am here to save you all from flashing your phone countless times to try to bring back LTE with no EFS backup and no persist backup.
Here is a guide for XT1687 U.S. version of Moto G5+ (potter) that brings back Verizon LTE on STOCK Firmware/Rom and gives you OTA updates after downgrading from custom 8.1 Oreo roms.
I have not been able to relock bootloader, but that is okay. I am on stock firmware with OTA updates working and LTE working again.
........
5.) Install OTA updates over WIFI even though your network connectivity still doesn't work yet. Your IMEI will be 0 and you will have no network access.
Install all OTA updates with WIFI until your phone is on Build number: NPNS25.137-93-10, there is no firmware file to download this build, so it must be updated through OTA on wifi (all OTAs together should be ~300-500mb total).
Click to expand...
Click to collapse
Nice guide, just a little correction: There is in fact a fastboot flashable NPNS25.137-93-10 stock firmware, here's a mirror, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud (the one where customer service get the firmware) but not everyone was able to download it from there.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Nice guide, just a little correction: There is in fact a fastboot flashable NPNS25.137-93-10 stock firmware, here's a mirror, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud (the one where customer service get the firmware) but not everyone was able to download it from there.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
thanks but the link is dead there, know anywhere else to get it? and there the same for ATT and verizon right?
vonwap said:
thanks but the link is dead there, know anywhere else to get it? and there the same for ATT and verizon right?
Click to expand...
Click to collapse
Hmm, I've just tried the link and it works - I'm downloading the NPNS25.137-93-10 stock ROM as I write this from that provided Google Drive link.
As for the AT&T or Verizon versions, I'm not sure (though I think that retus devices on Verizon may have NPNS25.137-93-10, someone with a US device would be better suited to comment). Also, if I recall, devices on Verizon were on a different update path, from NPN25.137-33 to NPN25.137-35 (March 2017 security patch), then to NPN25.137.43-5 (May 2017 security patch), then to NPN25.137-83 (Aug 2017 security patch) before NPN25.137-93 (Nov 2017 security patch), then you should also get NPNS25.137-93-4 (Jan 2018 security patch), NPNS25.137-93-8 (March 2018 security patch), then NPNS25.137-93-10 (April 2018 security patch).
I would also caution against downgrading to NPNS25-137-33-5 (May 2017 security patch), as described in the guide, if your stock firmware was updated to a version newer than the May 2017 security patch. The reason being that if you have a device with a newer stock firmware previously flashed to it, downgrading to the May 2017 firmware may go okay, but you run the risk of hard bricking your device (as installing old OTA updates overwrites your bootloader, which is still present from the newer stock firmware). If your device was previously on the May 2017 stock security patch or older, you may not risk a hard brick but downgrading comes with risks.
Thus, it's probably best to attempt to flash NPNS25.137-93-10 for EU, US and Asia devices or NPNS25.137-92-10 for Brazil and Indian devices to avoid a downgrade.
vonwap said:
thanks but the link is dead there, know anywhere else to get it? and there the same for ATT and verizon right?
Click to expand...
Click to collapse
The link should be working as you see above in the post of @echo92 who has also answered your question as good as I could, maybe better.
I'm also not sure about the firmware path. 33-5 was May security patch here too but as you can see on the screenshot below August 2017 security patch was 33-11, at least here in Europe.
I'm pretty sure that there's no difference in the latest Verizon or AT&T firmwares but as @echo92 said, maybe a US user knows more about that (if you want to be 100% sure about that).
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific, they should work but you won't receive any OTA updates as the updates pushed in the US an Europe search for 93-x firmwares.
Try the link again, maybe in a different browser.
If you can't download it at all I will mirror it on another hoster. Just send me a PM.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
The link should be working as you see above in the post of @echo92 who has also answered your question as good as I could, maybe better.
I'm also not sure about the firmware path. 33-5 was May security patch here too but as you can see on the screenshot below August 2017 security patch was 33-11, at least here in Europe.
I'm pretty sure that there's no difference in the latest Verizon or AT&T firmwares but as @echo92 said, maybe a US user knows more about that (if you want to be 100% sure about that).
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific, they should work but you won't receive any OTA updates as the updates pushed in the US an Europe search for 93-x firmwares.
Try the link again, maybe in a different browser.
If you can't download it at all I will mirror it on another hoster. Just send me a PM.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
thanks worked with firefox, Ima try and get my VoLTe back on x1687? flashed to pixle 4g works but just left b/c scared to mess it up again. backed up my efs though. what is the persist ?
Wolfcity said:
The link should be working as you see above in the post of @echo92 who has also answered your question as good as I could, maybe better.
I'm also not sure about the firmware path. 33-5 was May security patch here too but as you can see on the screenshot below August 2017 security patch was 33-11, at least here in Europe.
I'm pretty sure that there's no difference in the latest Verizon or AT&T firmwares but as @echo92 said, maybe a US user knows more about that (if you want to be 100% sure about that).
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific, they should work but you won't receive any OTA updates as the updates pushed in the US an Europe search for 93-x firmwares.
Try the link again, maybe in a different browser.
If you can't download it at all I will mirror it on another hoster. Just send me a PM.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Confusingly, the US series of firmwares seemed to be on different update paths until recently, when Motorola wisely appeared to unify them. The US equivalent of the 33-11 Aug 2017 update for EU/Brazil (and India?), as you posted, was NPN25.137-83, which was a follow on from either NPNS25.137-33-5 (May 2017) or NPNS25.137-35-5 or NPN25.137.43-5 (depending on which US network you were on). Needless to say, it got messy with regards to firmware updates...
But yes, I concur with you that the NPNS25.137-93-10 firmware should be a safe bet (especially as it's currently the latest firmware we have available anyway).
vonwap said:
thanks worked with firefox, Ima try and get my VoLTe back on x1687? flashed to pixle 4g works but just left b/c scared to mess it up again. backed up my efs though. what is the persist ?
Click to expand...
Click to collapse
It's a part of the nandroid backup.
persist.img is "persist" which contains data which shouldn't be changed after the device shipped, for example: calibration data of chips(wifi, bt, camera, etc.), certificates and other security related files. I heard it should contain the IMEI too but I'm not sure about that. You can't back it up with the official TWRP but with some unofficial versions, take a look here: https://forum.xda-developers.com/g5-plus/how-to/psa-efs-persist-t3807240
There are persist files uploaded here on XDA but it's a very hacky way as you have to use a file from the Moto G4 with side effects like yellowish photos.
Check the related threads.
Sent from my Moto G5 Plus using XDA Labs
Hmm sort of worried b/c im on att not sure if it makes a difference. Ill try and report back.
Wolfcity said:
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific
Click to expand...
Click to collapse
Just a correction to the above, Asia Pacific (retapac) uses the 93 series as well.
NZedPred said:
Just a correction to the above, Asia Pacific (retapac) uses the 93 series as well.
Click to expand...
Click to collapse
Ok, thx for the info. So the 92-x firmware is only for India and Brazil.
Sent from my Moto G5 Plus using XDA Labs
Dont use if on any other carrier than verizon
Don't use this if you are not on verizon, I flashed this thinking it would fix some issues I was having with camera on my XT1687 and cricket wireless but now my imei is 0 and unrecoverable. If some on has a presist file and using cricket or att please share so I can see if that will help get LTE and IMEI back.
What firmware rom did you flash?
Did you follow guide and flash persist in TWRP that I linked to? Are you coming from custom Oreo rom?
When you flash back to stock from Oreo roms you will automatically lose IMEI and network connectivity.
Persist file is linked in first post :good::
Code:
https://www23.zippyshare.com/v/13MfpRhg/file.html
TWRP recovery needs to be flashed again after you flash the stock firmware.
You need to make an EFS backup in TWRP Recovery to create the EFS folder in your phone storage, after you finish flashing stock rom.
The persist.img backup needs to be restored in TWRP after you place it in your newly created EFS folder in your TWRP folder on phone storage.
Restore persist.img in TWRP after flashing stock firmware, you should not be flashing firmware only. Persist.img is what gives you your LTE network signal and IMEI back.
Let me know if you have further issues.
vwfan511 said:
Did you follow guide and flash persist in TWRP that I linked to? Are you coming from custom Oreo rom?
When you flash back to stock from Oreo roms you will automatically lose IMEI and network connectivity.
Persist file is linked in first post :good::
Code:
https://www23.zippyshare.com/v/13MfpRhg/file.html
TWRP recovery needs to be flashed again after you flash the stock firmware.
You need to make an EFS backup in TWRP Recovery to create the EFS folder in your phone storage, after you finish flashing stock rom.
The persist.img backup needs to be restored in TWRP after you place it in your newly created EFS folder in your TWRP folder on phone storage.
Restore persist.img in TWRP after flashing stock firmware, you should not be flashing firmware only. Persist.img is what gives you your LTE network signal and IMEI back.
Let me know if you have further issues.
Click to expand...
Click to collapse
Yep flashed presist file in link along with efs after rolling back to the firmware version you recommend, even went back to the the one prior to that after losing IMEI. Whatever I did screwed me up big time. Was able to get 3G back on stock but still no IMEI number. Really not sure what changed or went differently this time compared to other times that I've followed similar steps with no problems but whatever it was has caused me to lose 4G and IMEI completely without being able to recover it by flashing Oreo ROMs. Ohhh well I'll be keeping my eye out on deals at best buy now lol.
Wolfcity said:
Nice guide, just a little correction: There is in fact a fastboot flashable NPNS25.137-93-10 stock firmware, here's a mirror, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud (the one where customer service get the firmware) but not everyone was able to download it from there.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
tuxattack80 said:
Yep flashed presist file in link along with efs after rolling back to the firmware version you recommend, even went back to the the one prior to that after losing IMEI. Whatever I did screwed me up big time. Was able to get 3G back on stock but still no IMEI number. Really not sure what changed or went differently this time compared to other times that I've followed similar steps with no problems but whatever it was has caused me to lose 4G and IMEI completely without being able to recover it by flashing Oreo ROMs. Ohhh well I'll be keeping my eye out on deals at best buy now lol.
Click to expand...
Click to collapse
Try flashing Omni rom.. when I lost mine it wasn't working on other Oreo roms and PixelExperience was forceclosing nonstop, couldn't even get it to boot.
Code:
[URL="http://dl.omnirom.org/potter/"]http://dl.omnirom.org/potter/[/URL]
. My IMEI and 3g came back on Omni, then went back to stock and flashed persist..
Also make sure your TWRP is fully updated to 3.2.1.0, wipe cache dalvik...etc
vwfan511 said:
Try flashing Omni rom.. when I lost mine it wasn't working on other Oreo roms and PixelExperience was forceclosing nonstop, couldn't even get it to boot.
Code:
[URL="http://dl.omnirom.org/potter/"]http://dl.omnirom.org/potter/[/URL]
. My IMEI and 3g came back on Omni, then went back to stock and flashed persist..
Also make sure your TWRP is fully updated to 3.2.1.0, wipe cache dalvik...etc
Click to expand...
Click to collapse
okay thanks i'll give it a shot
Does anyone have a different way to get the persist file. The little zippy thing wants to have me downloading other crap that i dont want??
this worked fine for me on att, coming from google pixle oreo with working efs, restored my efs and this persists,
but my bootloader still says "ID: bad key" not sure if it matters. should i relock my boot loader? or not worry
Archangel said:
Does anyone have a different way to get the persist file. The little zippy thing wants to have me downloading other crap that i dont want??
Click to expand...
Click to collapse
Here's a mirror link for you:
https://nofile.io/f/RuxbqZAQayH/persist.ext4.win
https://nofile.io/g/ZH3emEjoBxxnId89k5DfprKEpe4Ikpis5p85S8edrSibxiLtMzbfYNS0tAx9qE4Q/persist.ext4.win/
Click to expand...
Click to collapse
Reuploaded for you on a different mirror as zippyshare has ads/bs now.
vonwap said:
this worked fine for me on att, coming from google pixle oreo with working efs, restored my efs and this persists,
but my bootloader still says "ID: bad key" not sure if it matters. should i relock my boot loader? or not worry
Click to expand...
Click to collapse
Relocking bootloader may not be possible unless you're on the latest firmware, I haven't relocked mine yet.
I am waiting for official Oreo update to go ahead and try... you can try the relock commands with the latest OTA firmware file.. but I can't guarantee it will work.
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Iam uploading my special Bricked moto Z Loader Stock Oreo TWRP Moto G5+ for those who may need it, ciao!!!
Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!
SowilM said:
Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!
Click to expand...
Click to collapse
Happy to help brother!
So this will work for european users who did not break their persist?
Fabiuz99 said:
So this will work for european users who did not break their persist?
Click to expand...
Click to collapse
As far as i Know only for retail americas but you can try on your own and let us know
Battery performance is for fully happy and satisfied OVERWHELMING
will it work for indian version
will it work for indian version
---------- Post added at 06:48 PM ---------- Previous post was at 06:00 PM ----------
prnv1312 said:
will it work for indian version
Click to expand...
Click to collapse
thnks alot man
can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this?
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this? june security update
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
I am friom mexico and my phone is working perfect...is your question anserred alwearu...can not go back to nouhat
will it work for indian version XT1686
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
Click to expand...
Click to collapse
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?
carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
nvrpayretail said:
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?
Click to expand...
Click to collapse
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome
LLegion said:
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome
Click to expand...
Click to collapse
Sorry, I still a bit confused. The text I quoted says "bootloader stays MotoZ". If I install this update, as is, will my bootloader be MotoZ or remain Moto G5+?
Thanks...
I have the US version (retus), bootloader unlocked, nougat 7.0 with August patch (NPNS25. 137-93-18). Can I use this method safely? Thanks
I do not know what else to say...just flash as edpalined if phone breaks then unbrick it reading other tutos sorry pals but seems you are not reading enough
No risk no Win buddies
Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1
JohnSmith8786 said:
Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1
Click to expand...
Click to collapse
Do no flash from twrp but from runnimg the batch file oreo desde cero and it will flash the recobery as well to the oreo stock and thats it.buddie
I have LG G8 Alexa variant. Model LM-G820QM.
I think ts on latest firmware "qm21e". Right now I live in India so the VoLTE is not working. I tried to cross-flash it to Open firmware but LGUP gave error "Cant change the device(AMZ_US > OPEN_US)".
I have three questions.
Can I cross flash Korean firmware ?
And if so, will i get VoLTE working ?
And my G8 has 2 cams while the Korean varient has 3 cams. Will my cams work with Korean firmware ?
Thank you.
Do you by any chance still have the OPEN_US Firmware?
I've been looking everywhere for it but I can't find it.
Download LG Firmware for LG G8 ThinQ LMG820QM Android 10 Q kdz stock BPT Rom
Download Android 10 Q KDZ stock firmware for download with direct link
lg-roms.com
--------
| Firmware Update Android 10 Q kdz stock AMZ Rom
Download Android 10 Q KDZ stock firmware for download with direct link
lg-firmware.net
I think any of this 2 are OPEN. If not then reply me back I will deep search on google. I happend to found it somewhere but can't remember where exactly.
Thanks for your reply
Unfortunately, neither one worked.
I tried the first one, however the flash tool didn't work because (OPEN_US_>NAO_US)
The second one would not download at all. I don't think it would have worked anyway since my phone is not the Alexa version. It's factory unlocked, purchased from Best Buy.
Hey man, I was able to figure out my problem! Not only that, I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root!
I appreciate your help, and I want to help you if I can.
As for the cross-flashing, you can't do it via LGUP. The only possible way is to download the firehose for your phone and to use the Qualcomm Image Flash Loader(QIFL) tool. You can extract the firmware you want to flash, and load all the images into the QIFL partition manager. There is no guarantee your phone will boot from it, but you can try it. NOTE: Do NOT modify the OP partitions! This will cause your phone to throw an OPID mismatch error and it won't boot!
As for the cameras, you may be able to extract the current Camera APK from your phone and install that on the Korean firmware so that you are still able to use them. No guarantee this will work, and they might work fine with the Korean camera APK, but it's worth doing before you flash.
awgybop1 said:
Hey man, I was able to figure out my problem! Not only that, I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root!
I appreciate your help, and I want to help you if I can.
As for the cross-flashing, you can't do it via LGUP. The only possible way is to download the firehose for your phone and to use the Qualcomm Image Flash Loader(QIFL) tool. You can extract the firmware you want to flash, and load all the images into the QIFL partition manager. There is no guarantee your phone will boot from it, but you can try it. NOTE: Do NOT modify the OP partitions! This will cause your phone to throw an OPID mismatch error and it won't boot!
As for the cameras, you may be able to extract the current Camera APK from your phone and install that on the Korean firmware so that you are still able to use them. No guarantee this will work, and they might work fine with the Korean camera APK, but it's worth doing before you flash.
Click to expand...
Click to collapse
I see, but I just want VoLTE to work. I don't mind using stock rom or custom rom too. So keeping that in mind what do you suggest? And also, Do you think that your solution " I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root! " could work for me too ? If so do let me know how did you figured that NAO_US was actually OPEN_US. Maybe I can find out one for AMZ_US.
On the box Model : G820QM
SKU : G820QM8 (QM8 stands for AMZ)
Thank you.
I'm really not sure how VoLTE works internally, so I couldn't tell you if using another firmware would actually work for you - but the way I found out one of the firmwares was actually OPEN_US was by extracting it using the KMZ extractor tool someone made. This is how I was able to reflash the partition on my phone that I screwed up on in the first place and created a brick with. Like I said, you could manually reflash all those partitions one-by-one in QFIL, but i don't recommend it as it may not even work and could potentially brick your device. It's really up to you in this case, if you'd like to try though:
Download the firmware you want to try, search for KZM extractor on Google, download QFIL and all of it's prerequisites, and finally the firehose.
Use the KZM extractor and place the firmware inside of it.
Once it is done extracting all the files, put your phone into download mode and open QFIL
NOTE: DO NOT FLASH THE PARTITIONS WITH 'OP' IN THEM! Your phone won't boot for sure!
From QFIL use the firehose file and manually, one by one, sort through the output files of the KZM extractor and find the partitions that match their name and flash them with the file.
Zero guarantees this will work, and you may end up with a brick for a phone at the end of the day, but if you're that desperate it just might work.
Hi there.
I am still looking for solutions for VoLTE to work. I googled a lot and came on this post " https://piunikaweb.com/2021/06/07/unlocked-lg-g8-thinq-now-supports-att-volte-after-april-update/ "
Mine is Amazon version "QM8". Yet I did received april update via OTA. But still no VoLTE. I can OEM unlock from devs. Can I flash AT&T "QM7" on Amazon "QM8" ?
What do you think of this please let me know.
Thank you
VoLTE seems to depend on files in the OP partition, so crossflashing other partitions but not OP will not get VoLTE to work. LGUP will not allow crossflashing.
See my experience to get working VoLTE and Wifi Calling: https://forum.xda-developers.com/t/lg-g8-volte-fix.4113291/post-85455109
You will need to be bootloader unlocked and rooted.
awgybop1 said:
Hey man, I was able to figure out my problem! Not only that, I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root!
I appreciate your help, and I want to help you if I can.
As for the cross-flashing, you can't do it via LGUP. The only possible way is to download the firehose for your phone and to use the Qualcomm Image Flash Loader(QIFL) tool. You can extract the firmware you want to flash, and load all the images into the QIFL partition manager. There is no guarantee your phone will boot from it, but you can try it. NOTE: Do NOT modify the OP partitions! This will cause your phone to throw an OPID mismatch error and it won't boot!
As for the cameras, you may be able to extract the current Camera APK from your phone and install that on the Korean firmware so that you are still able to use them. No guarantee this will work, and they might work fine with the Korean camera APK, but it's worth doing before you flash.
Click to expand...
Click to collapse
Pls how to extract kdz,mine get error bad header