Hello people!
I have a Moto G4 Plus XT640-DS stuck on 6.1.0 stock and it's not getting the OTA update in any way. The ROM version is MPJ24.139-23.1 and I wanna know if anyone has a Blur Version update for this ROM or an idea to force the OTA on the system.
gabrielbrondon said:
Hello people!
I have a Moto G4 Plus XT640-DS stuck on 6.1.0 stock and it's not getting the OTA update in any way. The ROM version is MPJ24.139-23.1 and I wanna know if anyone has a Blur Version update for this ROM or an idea to force the OTA on the system.
Click to expand...
Click to collapse
You can install the stock fastboot rom for nougat for example if it's that what you want?
strongst said:
You can install the stock fastboot rom for nougat for example if it's that what you want?
Click to expand...
Click to collapse
I tried some Blur ROMs I found here, but all of them come back with a error because the stock ROM installed isn't on the version the blue version requires
gabrielbrondon said:
I tried some Blur ROMs I found here, but all of them come back with a error because the stock ROM installed isn't on the version the blue version requires
Click to expand...
Click to collapse
Without knowing what version was previously on your device, I'm not comfortable with suggesting OTA updates. If your device was downgraded with Marshmallow, then using blur OTA updates might be risky.
Did you install the Motorola usb drivers, minimal ADB /fastboot and if you're running Windows 10, to ensure you have disabled driver signature enforcement? Just to check you've mentioned it's working for your other device.
If so, and you have fastboot working, then we can try to flash the stock fastboot ROM as suggested by strongst above.
echo92 said:
Without knowing what version was previously on your device, I'm not comfortable with suggesting OTA updates.
Click to expand...
Click to collapse
Sorry, here is the phone specifications:
Device XT-1640-DS
Android: 6.0.1
M8952_7000.04.03.32R
ATHENE_BRAZIL_DSDS_CUST
Kernel: 3.10.84-GCF01273
[email protected] #1
MPJ23.139-23.1
echo92 said:
if you're running Windows 10, to ensure you have disabled driver signature enforcement?
Click to expand...
Click to collapse
How do I disabled that?
gabrielbrondon said:
Sorry, here is the phone specifications:
Device XT-1640-DS
Android: 6.0.1
M8952_7000.04.03.32R
ATHENE_BRAZIL_DSDS_CUST
Kernel: 3.10.84-GCF01273
[email protected] #1
MPJ23.139-23.1
How do I disabled that?
Click to expand...
Click to collapse
Thanks, that's one of the first builds of Marshmallow for our device - seems that the buyer tried to revert back to original condition. However, the problem is that if your bootloader is newer than your stock firmware, attempting to use OTA updates may well corrupt your bootloader and hard brick the device. If you boot to the fastboot screen, what bootloader version (E.g. B1.03, B1.06) listed below the AP secure flash line?
I think you've already got the driver signature enforcement disabled as you mentioned fastboot was working for your own device, but if you want to check, here's a tutorial: www.howtogeek.com/167723/how-to-dis...8.1-so-that-you-can-install-unsigned-drivers/
echo92 said:
If you boot to the fastboot screen, what bootloader version (E.g. B1.03, B1.06) listed below the AP secure flash line?
Click to expand...
Click to collapse
It is B1.06 (sha-0edfb0d, 2017-06-01)
gabrielbrondon said:
It is B1.06 (sha-0edfb0d, 2017-06-01)
Click to expand...
Click to collapse
Thanks, so someone did appear to flash a really old firmware on top of a newer bootloader. By the way, do you mean MPJ24.139-23.1? I'm having difficulty finding MPJ23.139-23.1.
Regardless, you've got a June 2017 Nougat bootloader on a device running Marshmallow, so OTA updates even if you could get them, would hard brick your device, likely.
Any luck on getting the device recognised in fastboot? What happens if you boot the device to the bootloader, connect to your computer, and then in a minimal ADB terminal on your computer, type 'fastboot devices' without quotes? Does that device's serial number appear when you press enter?
Related
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
This one
http://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Tried flashing it. No success. Also the fiingerprint reader is also missing.
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
GeeteshKhatavkar said:
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
Click to expand...
Click to collapse
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
sabithmk said:
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
Click to expand...
Click to collapse
Which city ?I think you should go for the replacement and then update it via OTA when you get a notification.
Any Solutions Yet ?
Has anyone found any solutions yet !?
It is surely a Software issue
Service Center people are asking Rs.6500/- to replace the motherboard
Can't even relock the bootloader as i flashed the Nougat OTA and thus i can't downgrade the bootloader and lock it either !!
Please Help !
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
You found any solution?? I am facing the same problem...
bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
I sent it for service and got a free replacement.
bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
Yes I found it..
I created a thread. Check this.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
---------- Post added at 11:38 AM ---------- Previous post was at 11:36 AM ----------
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
Check this link friend. I did it. Was having same problem as you.
Check the thread I created.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
echo92 said:
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
Click to expand...
Click to collapse
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
gioyocho said:
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
Click to expand...
Click to collapse
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
Check my link.
You can even OTA update in future if you installed the latest firmware.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
echo92 said:
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
Click to expand...
Click to collapse
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
gioyocho said:
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
Click to expand...
Click to collapse
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
echo92 said:
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
Click to expand...
Click to collapse
well i tried and did not work those run commands
My Phone Info:
Single sim 2gb ram + 16gb rom
Hello folks I've been searching for a nougat update for XT-1644, but unable to find over the xda if anyone of you havs upgraded your xt-1644 then kindly tell the procedure here, Thanks.
Here is my About Phone Info.
http://cloud.tapatalk.com/s/589c8f61b2eab/Screenshot_20170209-203359.png
http://cloud.tapatalk.com/s/589c8f48b01b2/Screenshot_20170209-203401.png
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
echo92 said:
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
Click to expand...
Click to collapse
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
waseemmayaa said:
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
Click to expand...
Click to collapse
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
echo92 said:
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
waseemmayaa said:
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
Click to expand...
Click to collapse
I see you've received a response in the other thread regarding if XT1644 will accept the update; given you've flashed TWRP, if you wish to be very safe, I would suggest re-installing your Marshmallow ROM so you have a stock install before proceeding to Nougat. There's nothing stopping you from directly flashing Nougat, and the fastboot method for either Nougat build may correctly overwrite the relevant files, the only way is to try the procedure. Don't use the TWRP backup images of Nougat - they don't contain updates to your baseband modem and other core parts of your device - they are only meant to be used once your entire phone is updated to Nougat.
If you wish to restore back to stock MM before flashing Nougat, here's links to stock firmware for XT1644: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980
But either way, read all the instructions first, ensure you've got all the firmware and tools you need installed/downloaded, your phone has at least 50 % battery and plenty of time, and you should be okay.
My phone has its bootloader unlocked and ive had customs ROMs in the past - I ended up loosing my IEMI and the EFS files, so I went back to stock and got the IEMI and EFS back.
Iam currently on NPNS25.137-93-4, has any one else had this issue were the OTA update will not work? it will start the update process and ends up with a droid laying down with an error " ! " coming out of it. In addition when I boot my phone the "unlocked bootloader warning" says "ID: bad key" were before it said "ID: N/A" with the lineage ROM - Not sure if it matters. Should I relock my bootloader?
or does anyone have a link for the newest update XT1687 north america?
I am also on NPNS25.137-93-4. I tried installing with adb sideload but installation was aborted. I also tried installing with stock recovery but the my phone can not mount internal or external storage
jgmmjg said:
I am also on NPNS25.137-93-4. I tried installing with adb sideload but installation was aborted. I also tried installing with stock recovery but the my phone can not mount internal or external storage
Click to expand...
Click to collapse
You think its the version thats the issue?
vonwap said:
My phone has its bootloader unlocked and ive had customs ROMs in the past - I ended up loosing my IEMI and the EFS files, so I went back to stock and got the IEMI and EFS back.
Iam currently on NPNS25.137-93-4, has any one else had this issue were the OTA update will not work? it will start the update process and ends up with a droid laying down with an error " ! " coming out of it. In addition when I boot my phone the "unlocked bootloader warning" says "ID: bad key" were before it said "ID: N/A" with the lineage ROM - Not sure if it matters. Should I relock my bootloader?
or does anyone have a link for the newest update XT1687 north america?
Click to expand...
Click to collapse
When I tried unlocking my phone and installing 64-bit TWRP incorrectly, I ran into an issue similar to you. Now, my phone was on an older software version so I was able to fully install a firmware the fixed my device. (It had an 83 in it, can't remember what it was fully.) I'd look for a NPS25.137-93-14 build and flash all the files. That's the latest XT1687 build.
reCoded said:
When I tried unlocking my phone and installing 64-bit TWRP incorrectly, I ran into an issue similar to you. Now, my phone was on an older software version so I was able to fully install a firmware the fixed my device. (It had an 83 in it, can't remember what it was fully.) I'd look for a NPS25.137-93-14 build and flash all the files. That's the latest XT1687 build.
Click to expand...
Click to collapse
As far as I know there's no 93-14 version available, the last build uploaded is 93-10. There's a 92-14 firmware but that one is for India/Brazil only.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
As far as I know there's no 93-14 version available, the last build uploaded is 93-10. There's a 92-14 firmware but that one is for India/Brazil only.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
damn thats my problem i guess
I've just captured the Official OPP28.85-16 OTA for retail cedric and I'm posting it here. I'm on retbr channel but this will work on any retail device. If you're on another updated channel, I don't know what would happen if you installed this.
Notice that to install this YOU MUST be on NPPS25.137-93-2-5 to install these, since OTA's are not full firmwares like fastboot files, but instead they're patchings tailored to be applied upon a specific firmare - NPPS25.137-93-2-5 in this case.
Another particular detail is that the OTA file (gotten directly from my credric) lists the Blur Version as Blur_Version.25.361.10.cedric.retail.en.US, but curiously, the fastboot version for the same firmware ( which you can download here) lists it as Blur_Version.28.41.15.cedric.retail.en.US
Someone also reported in another thread that they just sideloaded this upon the Second Soak test. I wouldn't doubt it since this is what should happen to regular soak testers, but if you do it, DO IT AT YOUR OWN RISK
I also won't post instructions on how to install this since they're already available here
Download
Gdrive: https://drive.google.com/file/d/149hrGFpuWUgAvJr02McYNwJVaqSvllYO/view?usp=sharing
That's it.
changelog?
Has anyone already tried it?
Since this is a (Delta) OTA Update that expects NPPS25.137-93-2-5 (Blur_Version.25.361.10) it should be correctly named "block_delta-ota-Blur_Version.25.361.10-28.41.15.cedric.retail.en.US" in my view.
Someone also reported in another thread that they just sideloaded this upon the Second Soak test.
Click to expand...
Click to collapse
I'm on the 2nd soak test update OPP28.85-13.
Just tried to flash the update from SD card and ADB sideload.
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
JoeDoe0 said:
Since this is a (Delta) OTA Update that expects NPPS25.137-93-2-5 (Blur_Version.25.361.10) it should be correctly named "block_delta-ota-Blur_Version.25.361.10-28.41.15.cedric.retail.en.US" in my view.
I'm on the 2nd soak test update OPP28.85-13.
Just tried to flash the update from SD card and ADB sideload.
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
Click to expand...
Click to collapse
seems like it can be updated. from. soak test then, but I never heard nor did I find anything about OPP25. 85-16 build. maybe there was a third soak test and we don't know about it
Works perfect
Hi,
i used the above Image in Germany and i am now on Oreo 8.1
Everything works perfect. First i had a little bit trouble due to an old Version of ADB Tools, but after Update ADB to current Version the Update to Oreo took something around 30min.
Build 28.85-16
Oreo 8.1
Software Channel reteu
Patch Level 01.08.2018
bori321 said:
Hi,
i used the above Image in Germany and i am now on Oreo 8.1
Everything works perfect. First i had a little bit trouble due to an old Version of ADB Tools, but after Update ADB to current Version the Update to Oreo took something around 30min.
Build 28.85-16
Oreo 8.1
Software Channel reteu
Patch Level 01.08.2018
Click to expand...
Click to collapse
On which version you were before update?
Firmware
Hi,
before update to Oreo i flashed NPPS25.137-93-2-5 Firmware and after that the Image from this thread.
Worked perfect.
Alex
I tried to post a Screenshot but it was not possible because i am a new member...
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
Click to expand...
Click to collapse
freeZbies said:
seems like it can be updated. from. soak test then, but I never heard nor did I find anything about OPP25. 85-16 build. maybe there was a third soak test and we don't know about it
Click to expand...
Click to collapse
Update fails from OPP28.85-13 since it expects either OPP28.85-16 which is the latest Oreo build (that I want to update to) or the latest Nougat NPPS25.137-93-2-5.
There is no OPP25. 85-16 build! I think you misread the error message.
BTW I updated from OPP28.85-13 to -16 using the full fastboot version and it worked out perfectly.
JoeDoe0 said:
Update fails from OPP28.85-13 since it expects either OPP28.85-16 which is the latest Oreo build (that I want to update to) or the latest Nougat NPPS25.137-93-2-5.
There is no OPP25. 85-16 build! I think you misread the error message.
BTW I updated from OPP28.85-13 to -16 using the full fastboot version and it worked out perfectly.
Click to expand...
Click to collapse
yeah, I actually misread it, now I see it.
Anyways, flashing it from fastboot doesn't prove anything. but seems like Cedric can be upgraded from the soak test to final version using this ota. Idk because I used fastboot myself too, since I had already modified my system partition.
AsusZenFone3Deluxe said:
changelog?
Click to expand...
Click to collapse
seriously?
stop joking, Motorola doesn't release changelogs.
but I'll try:
updated from nougat to oreo?
duhhh
how is speaker quality in this build ?
because there is some issues in previous oreo builds
Speaker
Hi,
i would say that for my ears the speaker sounds better than it was with Nougat.
After a few days of testing everything works really good and i have not found anything not working or any problems.
Alex
bori321 said:
Hi,
before update to Oreo i flashed NPPS25.137-93-2-5 Firmware and after that the Image from this thread.
Worked perfect.
Alex
I tried to post a Screenshot but it was not possible because i am a new member...
Click to expand...
Click to collapse
how do you get back to NPPS25.137-93-2-5
I followed the steps from this Thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
- Unlocked bootloader (don't know of this is necessary)
- back to NPPS25.137-93-2-5 via the commands from the thread i linked (without the lines:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
)
- via ADB sideload with the Oreo download from this thread to Oreo.
Alex
ahmedAZ said:
how is speaker quality in this build ?
because there is some issues in previous oreo builds
Click to expand...
Click to collapse
In my experience the quality is better than on previous oreo builds.
ahmedAZ said:
how do you get back to NPPS25.137-93-2-5
Click to expand...
Click to collapse
if you have an unlocked bootloader download NPPS25.137-93-2-5 Flashable Zip here and flash it with twrp
bori321 said:
I followed the steps from this Thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
- Unlocked bootloader (don't know of this is necessary)
Alex
Click to expand...
Click to collapse
to flash official Motorola files there's no need to unlock the bootloader.
you've just unnecessarily voided your warranty
@freeZbies
Hey is that twrp stock rom (137-93-2-5) the only thing we need to flash before going for the ota ? Cause I've been told that we needed to be on a completely unmodified system partition in order to receive the ota. In that case just flashing twrp stock wouldn't be sufficient right?
https://forum.xda-developers.com/g5...o-official-stock-oreo-8-t3823598/post77713117
Chekm8Qc said:
@freeZbies
Hey is that twrp stock rom (137-93-2-5) the only thing we need to flash before going for the ota ? Cause I've been told that we needed to be on a completely unmodified system partition in order to receive the ota. In that case just flashing twrp stock wouldn't be sufficient right?
https://forum.xda-developers.com/g5...o-official-stock-oreo-8-t3823598/post77713117
Click to expand...
Click to collapse
I dont know if the twrp version would be valid. To apply an OTA, your system must matchbit by bit, so the most guaranteed way is to flash that firmware via fastboot, but you could try flashing the twrp version, and in case it works, you could post the results here.
just dont forget that if the ota fails youll soft brick ur phonr and will only be able to recover it via fastboot
freeZbies said:
I dont know if the twrp version would be valid. To apply an OTA, your system must match stick bit by bit, so the most guaranteed way is to flash that firmware via fastboot, but. you could try flashing the twrp version, and in case it. woeks you could post the results here.
just dont forget that if the ota fails youll soft brick ur phonr and will only be able to recover it via fastboot
Click to expand...
Click to collapse
Thanks I'll keep that in mind
Being soft bricked,, wouldn't I be able to use twrp still? Like to flash a valid rom or one of my backups?
Anyways I can't really try it that way since the update hasn't come to me yet I'm on software channel Retca.
Edit : right I forgot that I could just use the official ota available here if I would like to test it.
Chekm8Qc said:
Thanks I'll keep that in mind
Being soft bricked,, wouldn't I be able to use twrp still? Like to flash a valid rom or one of my backups?
Anyways I can't really try it that way since the update hasn't come to me yet I'm on software channel Retca.
Edit : right I forgot that I could just use the official ota available here if I would like to test it.
Click to expand...
Click to collapse
being soft bricked doesnt necessarily mean you can recover it through twrp. OTA's are different of twrp flashables in that it modifies things beyond system partition. I've seen reports from people with other motorola devices who applied an OTA while having a modified system partition, and even though they were able to boot to twrp, flashing a custom Rom or restore a backup wouldn't make the phone boot. Their phones weren't hard bricked, but still they had to fastboot to recover their phones. Anyways, why don't you flash the Twrp flashable if, it's already available (considering you have an unlocked bootloader).
I'm case you have a locked bootloader you may fastboot without executing "fastboot erase userdata" in case you want to try. I did it without losing my data (although I was already in Opp 28.85-16)
but after all I really advice you to flash the twrp zip if u can
Hello Everyone!
I am a total noob. I have rooted many phone but never once reversed the process. Plus with stock moto being 32bit and customs being 64 it is even more complicated for me. And plus all this post about lost IMIE numbers and lost GPT makes me scared.
If i may, can I get step by step guide to relock my bootloader and get OTAs.
I have read most of the tutorials here but couldnt get the confidence to move forward(they all sound a little different)
I have moto G5 plus XT1686 indian version 4Gb/32GB currently running PE 9.0 (GTRCraft). I dont remember which version I had when I unlocked the bootloader. I do have a backup of my persist/efs.
I did see one tutorial but it is for 8.1.0 to stock and IDK if that works for me.
Thanks in advance.
reganEZ said:
Hello Everyone!
I am a total noob. I have rooted many phone but never once reversed the process. Plus with stock moto being 32bit and customs being 64 it is even more complicated for me. And plus all this post about lost IMIE numbers and lost GPT makes me scared.
If i may, can I get step by step guide to relock my bootloader and get OTAs.
I have read most of the tutorials here but couldnt get the confidence to move forward(they all sound a little different)
I have moto G5 plus XT1686 indian version 4Gb/32GB currently running PE 9.0 (GTRCraft). I dont remember which version I had when I unlocked the bootloader. I do have a backup of my persist/efs.
I did see one tutorial but it is for 8.1.0 to stock and IDK if that works for me.
Thanks in advance.
Click to expand...
Click to collapse
Just wipe everything from twrp and then use LMSA OR manually flash the stock ROM and then go for bootloader lock procedure. Then you are done. And you won't lose any IMEI or Persist, so you will be safe.
riyan65 said:
Just wipe everything from twrp and then use LMSA OR manually flash the stock ROM and then go for bootloader lock procedure. Then you are done. And you won't lose any IMEI or Persist, so you will be safe.
Click to expand...
Click to collapse
So just download a TWRP flashable 8.1.0 rom and i m good?
reganEZ said:
So just download a TWRP flashable 8.1.0 rom and i m good?
Click to expand...
Click to collapse
No, download a fastboot flashable ROM, with a TWRP flashable you won't be able to apply OTAs:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Use OPSS28.85-17-4 if you're in the US or OPSS28.85-13-3 for the rest of the world.
Follow the available tutorials for flashing that firmware and after that for relocking the BL (almost the same commands). Make sure you have Minimal ADB & Fastboot
https://androidfilehost.com/?fid=746010030569952951
and Motorola drivers
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view
installed on your PC.
For the fastboot commands you can use this flashall.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
Wolfcity said:
No, download a fastboot flashable ROM, with a TWRP flashable you won't be able to apply OTAs:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Use OPSS28.85-17-4 if you're in the US or OPSS28.85-13-3 for the rest of the world.
Follow the available tutorials for flashing that firmware and after that for relocking the BL (almost the same commands). Make sure you have Minimal ADB & Fastboot
https://androidfilehost.com/?fid=746010030569952951
and Motorola drivers
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view
installed on your PC.
For the fastboot commands you can use this flashall.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
Click to expand...
Click to collapse
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
This is a part of the bootloader locking tutorial here on XDA. Does this make a difference?
reganEZ said:
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
This is a part of the bootloader locking tutorial here on XDA. Does this make a difference?
Click to expand...
Click to collapse
+ i tried the method and it says "slot not found" error
reganEZ said:
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
This is a part of the bootloader locking tutorial here on XDA. Does this make a difference?
Click to expand...
Click to collapse
You have to use the firmware you were on before you changed to a custom ROM or a newer one.
Never use an older one, downgrading can brick your device.
reganEZ said:
+ i tried the method and it says "slot not found" error
Click to expand...
Click to collapse
The "slot not found" error is normal, it's related to A/B devices with more than one recovery slot like Pixel phones. The commands should work nevertheless. Ignore the message.
I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damned thing.
Everything works fine, excpet for Netflix that can't be installed no more and my bank software who keeps complaining.
I just dunno what to do to relock, any advice ?
Wolfcity said:
You have to use the firmware you were on before you changed to a custom ROM or a newer one.
Never use an older one, downgrading can brick your device.
The "slot not found" error is normal, it's related to A/B devices with more than one recovery slot like Pixel phones. The commands should work nevertheless. Ignore the message.
Click to expand...
Click to collapse
Hello, Thank you for your reply.
I understand I cannot use an older firmware. I remember I unlocked my BL when I was in 7.0 itself, but when I installed the Arrow 9.0, I flashed the 8.1 firmware zip to get the NFC and Fingerprint working. So now my ro.build fingerprint doesnt tell me which firmware build i am on it just says "8.1"
I am confused what to do. Should I download the latest 8.1 moto rom and flash it? I tried the TWRP flashable rom but the phone just goes upto Hello Moto bootscreen and then bootloops.
I erased everything and flashed PE 9.0 again.
reganEZ said:
Hello, Thank you for your reply.
.....Should I download the latest 8.1 moto rom and flash it?.......
Click to expand...
Click to collapse
That's what I would do. If you flash the latest firmware it can't be older as the one you're originally coming from.
Follow my previous post:
Wolfcity said:
No, download a fastboot flashable ROM, with a TWRP flashable you won't be able to apply OTAs:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Use OPSS28.85-17-4 if you're in the US or OPSS28.85-13-3 for the rest of the world.
Follow the available tutorials for flashing that firmware and after that for relocking the BL (almost the same commands). Make sure you have Minimal ADB & Fastboot
https://androidfilehost.com/?fid=746010030569952951
and Motorola drivers
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view
installed on your PC.
For the fastboot commands you can use this flashall.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.batflashallO.bat?dl=0
Click to expand...
Click to collapse
Wolfcity said:
That's what I would do. If you flash the latest firmware it can't be older as the one you're originally coming from.
Follow my previous post:
Click to expand...
Click to collapse
Hello Sir, i was on OPSS28.85-13-5 when i flashed custom rom. The link you provided lists OPSS28.85-13-3 as the latest firmware. Should i install that? I am from India if that helps. Help please.
MrAshuBrar said:
Hello Sir, i was on OPSS28.85-13-5 when i flashed custom rom. The link you provided lists OPSS28.85-13-3 as the latest firmware. Should i install that? I am from India if that helps. Help please.
Click to expand...
Click to collapse
Take this one:
85-13-5
https://forum.xda-developers.com/g5-plus/how-to/official-oreo-coming-soon-t3779098/post78844908
CanadianGixxerman said:
I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damned thing.
Everything works fine, excpet for Netflix that can't be installed no more and my bank software who keeps complaining.
I just dunno what to do to relock, any advice ?
Click to expand...
Click to collapse
Flash all the system files while locking. (0-8). Older locking guides have only 0-4. Newer firmware has 9 system files.
Wolfcity said:
Take this one:
85-13-5
https://forum.xda-developers.com/g5-plus/how-to/official-oreo-coming-soon-t3779098/post78844908
Click to expand...
Click to collapse
Thank you so much ?