Need help going back to stock Oreo (but keeping bootloader unlocked) - Moto Z Play Questions & Answers

Long story short, I got pissed at Moto and decided to unlock my bootloader, flash TWRP, and flash a custom ROM (Alberto97's AOSP 8.1). While the ROM is working fine, eventually, I kind of missed the stock ROM, and decided I want to go back (Oreo). Keep in mind, though, I don't want to relock my bootloader as I will flash TWRP and root my device after going back to stock. How do I do this? I do have the Oreo OTA zip with me (Build no. OPN27.76-12-22), if that matters.

When you never were on stock oreo, you can easily flash stock firmware with February security patch (it's 7.1) and then update with the Oreo update zip you find in the forums. Then you can flash TWRP again.

jonas210678 said:
When you never were on stock oreo, you can easily flash stock firmware with February security patch (it's 7.1) and then update with the Oreo update zip you find in the forums. Then you can flash TWRP again.
Click to expand...
Click to collapse
Well, I was on official Oreo :/

djdelarosa25 said:
Well, I was on official Oreo :/
Click to expand...
Click to collapse
Bro, you and I are on same page. I also rooted my device when I was on stock Oreo and forgot to make a backup of stock Oreo (cuz I'm stupid). I talked a lot to other members and only option that is available for now to get back to stock with boot unlocked and OTA support is wait for Fastboot flash files for stock Oreo. Stock flash files will return your device to original state. I hope Oreo frimware would be available soon (about couple of months). I also want to get back to stock and guess what? I am also using AOSP by Alberto and it's working just like stock, no problem and bugs (there is some data connection bug but I use wifi all the time so it doesn't bother me) so far. Only problem with this ROM is safety net but I don't even use apps that requires safety net certification so I'm good with that too. Basically, it is a perfect ROM for me.
And don't try to back flash if you want to get back to original state, it is true you can still flash 7.1.1 but no guarantee, I just heard from someone but I never tried because I don't want to take risks and even if you got it running 7.1.1, a single OTA will brick your phone for sure. So wait for Oreo frimware, that's the only way and by the time enjoy AOSP.

Manish355 said:
Bro, you and I are on same page. I also rooted my device when I was on stock Oreo and forgot to make a backup of stock Oreo (cuz I'm stupid). I talked a lot to other members and only option that is available for now to get back to stock with boot unlocked and OTA support is wait for Fastboot flash files for stock Oreo. Stock flash files will return your device to original state. I hope Oreo frimware would be available soon (about couple of months). I also want to get back to stock and guess what? I am also using AOSP by Alberto and it's working just like stock, no problem and bugs (there is some data connection bug but I use wifi all the time so it doesn't bother me) so far. Only problem with this ROM is safety net but I don't even use apps that requires safety net certification so I'm good with that too. Basically, it is a perfect ROM for me.
And don't try to back flash if you want to get back to original state, it is true you can still flash 7.1.1 but no guarantee, I just heard from someone but I never tried because I don't want to take risks and even if you got it running 7.1.1, a single OTA will brick your phone for sure. So wait for Oreo frimware, that's the only way and by the time enjoy AOSP.
Click to expand...
Click to collapse
I definitely will. Thanks a lot, man . Lesson learned, always make backups

Manish355 said:
Bro, you and I are on same page. I also rooted my device when I was on stock Oreo and forgot to make a backup of stock Oreo (cuz I'm stupid). I talked a lot to other members and only option that is available for now to get back to stock with boot unlocked and OTA support is wait for Fastboot flash files for stock Oreo. Stock flash files will return your device to original state. I hope Oreo frimware would be available soon (about couple of months). I also want to get back to stock and guess what? I am also using AOSP by Alberto and it's working just like stock, no problem and bugs (there is some data connection bug but I use wifi all the time so it doesn't bother me) so far. Only problem with this ROM is safety net but I don't even use apps that requires safety net certification so I'm good with that too. Basically, it is a perfect ROM for me.
And don't try to back flash if you want to get back to original state, it is true you can still flash 7.1.1 but no guarantee, I just heard from someone but I never tried because I don't want to take risks and even if you got it running 7.1.1, a single OTA will brick your phone for sure. So wait for Oreo frimware, that's the only way and by the time enjoy AOSP.
Click to expand...
Click to collapse
Hey, so if someone can upload a TWRP flashable Nandroid backup of stock Oreo, are we saved?

djdelarosa25 said:
Hey, so if someone can upload a TWRP flashable Nandroid backup of stock Oreo, are we saved?
Click to expand...
Click to collapse
You'll get back to stock for sure but bootloader will still be unlocked, the only way to lock bootloader is through fastboot flashing of stock ROM. Moreover, TWRP backup contains personal information so not many want to share it but if someone kind enough to make a backup after doing factory reset so it will not contain any personal information then it will work.

Manish355 said:
You'll get back to stock for sure but bootloader will still be unlocked, the only way to lock bootloader is through fastboot flashing of stock ROM. Moreover, TWRP backup contains personal information so not many want to share it but if someone kind enough to make a backup after doing factory reset so it will not contain any personal information then it will work.
Click to expand...
Click to collapse
Why would one still want to relock the bootloader? It's to my understanding that unlocking it voids your warranty, and I've also read somewhere that even after relocking it, the warning persists.

By the way, have you checked my PM?

Hi guys, in my case I updated from Android Nougat 7.1.1 to AOSP 8.1. now I want to go back to stock rom 7.11 and after that update to Oreo by OTA. Should I only apply Stock Rom 7.11 by RSD Lite??
Thanks in advance

soadcma said:
Hi guys, in my case I updated from Android Nougat 7.1.1 to AOSP 8.1. now I want to go back to stock rom 7.11 and after that update to Oreo by OTA. Should I only apply Stock Rom 7.11 by RSD Lite??
Thanks in advance
Click to expand...
Click to collapse
You can directly flash the Oreo firmware via fastboot

Yeah, just flash the Oreo firmware

jonas210678 said:
You can directly flash the Oreo firmware via fastboot
Click to expand...
Click to collapse
But where can I find it to download ?
Thanks
---------- Post added at 04:39 PM ---------- Previous post was at 04:37 PM ----------
djdelarosa25 said:
Yeah, just flash the Oreo firmware
Click to expand...
Click to collapse
But where can I find it to download ?
Thanks

soadcma said:
But where can I find it to download ?
Thanks
---------- Post added at 04:39 PM ---------- Previous post was at 04:37 PM ----------
But where can I find it to download ?
Thanks
Click to expand...
Click to collapse
Link for the topic with the Oreo stock fastboot ROM. https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-oreo-bootloader-to-stock-t3784621
1.67 GB in size.

Related

Downgrade to Marshmallow with S-On?

I'm wondering if anyone has attempted to install a Marshmallow custom ROM or stock RUU over the Nougat firmware with any success.
I'm doubtful, but perhaps it's possible with S-On. Thanks!
the nougat firmware is not downcompatible with marshmallow roms.
only way would be to s-off, downgrade firmware then, flash the marshmallow rom.
be aware to pick a full firmware though and no incremental one...we've seen a handful people doing this and that ends in a hardbrick.
j to the 4n said:
the nougat firmware is not downcompatible with marshmallow roms.
only way would be to s-off, downgrade firmware then, flash the marshmallow rom.
be aware to pick a full firmware though and no incremental one...we've seen a handful people doing this and that ends in a hardbrick.
Click to expand...
Click to collapse
When I then eventually update ViperROM from Marshmallow to Nougat, will I have to perform a full wipe - or can the update be directly applied?
Trying to plan ahead, thanks a bunch j4n.
fullydeveloped said:
When I then eventually update ViperROM from Marshmallow to Nougat, will I have to perform a full wipe - or can the update be directly applied?
Trying to plan ahead, thanks a bunch j4n.
Click to expand...
Click to collapse
well, that sounds like that you are still on marshmallow firmware + rom.
That would mean, you could flash the nougat rom and revert back to the marshmallow one anytime. Just ensure you flash latets TWRP before and backup your data, including sdcard..in case something goes wrong with encryption.
the nougat rom can be dirty flashed.
you know what the difference between firmware and rom is, right?
j to the 4n said:
well, that sounds like that you are still on marshmallow firmware + rom.
That would mean, you could flash the nougat rom and revert back to the marshmallow one anytime. Just ensure you flash latets TWRP before and backup your data, including sdcard..in case something goes wrong with encryption.
the nougat rom can be dirty flashed.
you know what the difference between firmware and rom is, right?
Click to expand...
Click to collapse
Thanks, apologies for the confusion. I'm on Nougat, but am planning to downgrade for xposed - then eventually update back up to Nougat once there's a stable release. I asked about dirty flashing since I'm less likely to full wipe for 7.0 after many months of customizing
j to the 4n said:
the nougat firmware is not downcompatible with marshmallow roms.
only way would be to s-off, downgrade firmware then, flash the marshmallow rom.
be aware to pick a full firmware though and no incremental one...we've seen a handful people doing this and that ends in a hardbrick.
Click to expand...
Click to collapse
Has anyone downgraded the Firmware and succeeded? I hard bricked mine twice, first was trying to downgrade it with a full stock firmware from OTA and 2nd time it died when i accidentally picked and flashed a wrong Marshmallow aboot trying to get rid of Hidden Red text which made me believe flashing a Marshmallow aboot while on Nougat hardbricks the Phone. It died at the stage where it should restart so we can run fastboot flash zip Firmware_xx.zip command the 2nd time. It goes black, doesn't turn on, a PC doesn't recognize it, doesn't show if charging. Was lucky HTC took care of the problem.
emrug said:
Has anyone downgraded the Firmware and succeeded? I hard bricked mine twice, first was trying to downgrade it with a full stock firmware from OTA and 2nd time it died when i accidentally picked and flashed a wrong Marshmallow aboot trying to get rid of Hidden Red text which made me believe flashing a Marshmallow aboot while on Nougat hardbricks the Phone. It died at the stage where it should restart so we can run fastboot flash zip Firmware_xx.zip command the 2nd time. It goes black, doesn't turn on, a PC doesn't recognize it, doesn't show if charging. Was lucky HTC took care of the problem.
Click to expand...
Click to collapse
thats what I said. The firmware in an ota is NOT a full firmware, its a incremental one.
You need a full firmware package like its provided in @Sneakyghost 's threads, with those lots of downgraded already.
j to the 4n said:
thats what I said. The firmware in an ota is NOT a full firmware, its a incremental one.
You need a full firmware package like its provided in @Sneakyghost 's threads, with those lots of downgraded already.
Click to expand...
Click to collapse
Great!! Now i get it, well explained. Thanks :highfive:

Jio4GVoice App Oreo Problem

This is my first post here so please ignore any novice mistakes.
I have been running AICP 7.1.2 from a long time and in fact after i flashed a custom rom, i lost volte altogether, which has been an issue for most of the people. So now i have to use Jio4GVoice app for calling.
I tried 2-3 Oreo based roms but even after whitelisting the app and providing complete data access to the app, unfortunately it doesn't run in background. It definitely shows up status as Online but i don't receive any calls unless i open up the app in foreground. I tried every possible fix for this but somehow Oreo has a hard background killing scheme. All Nougat roms worked fine though. Can somebody help please?
Same problem here in oneplus one
Flash Stock ZUI through TWRP first and boot till you see HD or enable it in settings if you don't see it enabled. After this, flash any custom ROM you like, Volte should be enabled by default at this stage. I had this problem and this method solved it. Try it.
Shinichi Kudo said:
Flash Stock ZUI through TWRP first and boot till you see HD or enable it in settings if you don't see it enabled. After this, flash any custom ROM you like, Volte should be enabled by default at this stage. I had this problem and this method solved it. Try it.
Click to expand...
Click to collapse
Could you please help me on how to backup the entire custom rom before flashing stock rom ?
I want to backup all data so that I can restore everything
Can you help me on this?
Or can I get volte working on custom rom itself without having to go back to stock rom?
akash2018 said:
Could you please help me on how to backup the entire custom rom before flashing stock rom ?
I want to backup all data so that I can restore everything
Can you help me on this?
Or can I get volte working on custom rom itself without having to go back to stock rom?
Click to expand...
Click to collapse
You can make a full backup of your system through TWRP.
Then flash stock rom.
Boot into it and wait till you get HD.
Reboot and restore.
This should do the trick.
But BEWARE, you should take the backup and restore with the SAME recovery.
The deodexed stock rom will flash an older recovery and hence replace the new one.
You have to FLASH THE NEW (SAME) RECOVERY that you used for backup BEFORE RESTORING your data.
If you fail to keep an eye on this step, you are most likely going to HARD BRICK your device.
Shinichi Kudo said:
You can make a full backup of your system through TWRP.
Then flash stock rom.
Boot into it and wait till you get HD.
Reboot and restore.
This should do the trick.
But BEWARE, you should take the backup and restore with the SAME recovery.
The deodexed stock rom will flash an older recovery and hence replace the new one.
You have to FLASH THE NEW (SAME) RECOVERY that you used for backup BEFORE RESTORING your data.
If you fail to keep an eye on this step, you are most likely going to HARD BRICK your device.
Click to expand...
Click to collapse
Thank you so much
But right now my device is rooted do I have to unroot it and relock the bootloader in order to flash the stock ROM ?
akash2018 said:
Thank you so much
But right now my device is rooted do I have to unroot it and relock the bootloader in order to flash the stock ROM ?
Click to expand...
Click to collapse
Nope. Just go ahead and follow the steps carefully.
By the way, the deodexed rom is pre-rooted.
You just need it to see the HD symbol to appear on boot that's all.
---------- Post added at 12:00 PM ---------- Previous post was at 11:59 AM ----------
Here is the link to deodexed stock if you need it.
https://forum.xda-developers.com/lenovo-zuk-z2/development/deodexed-z2-plus-nougat-2-5-334-st-t3594483
I guess you are an Indian user, use the Indian ROM 2.5.104
Shinichi Kudo said:
Nope. Just go ahead and follow the steps carefully.
By the way, the deodexed rom is pre-rooted.
You just need it to see the HD symbol to appear on boot that's all.
---------- Post added at 12:00 PM ---------- Previous post was at 11:59 AM ----------
Here is the link to deodexed stock if you need it.
https://forum.xda-developers.com/le...t/deodexed-z2-plus-nougat-2-5-334-st-t3594483
I guess you are an Indian user, use the Indian ROM 2.5.104
Click to expand...
Click to collapse
Thank you so much for your help
So after doing all steps and restoring the custom rom through the twrp recovery will I have all data back including xposed modules and media, contacts, apps, app data etc?
I mean will everything on my device present right now will be there after this process or something will be missing?
Also one more important thing I forgot to tell you is that after flashing custom ROM I flashed custom kernel also so is it okay if I flash stock ROM along with the custom kernel?
And twrp recovery version can be a different one (i mean can it be on latest version?) while restoring custom ROM or should be the same version on which I back up custom ROM?
Sorry for asking too many questions
Don't know why u r facing this problem, but I've tried almost every Oreo really roms here and all of them have stable volte! My jio works flawlessly on all of them. Just make sure u r on baseband version 1.7. Naming a few stable volte Oreo roms:
Bootleggers
DotOs
Havos Os(my currenr favourite)
Pixel experience (old rom without updates)
AospExtended
RR
CAF
etc etc...volte works everywhere!
---------- Post added at 08:03 PM ---------- Previous post was at 07:58 PM ----------
Try this:
https://forum.xda-developers.com/le...oreo-firmwarebaseband-twrp-flashable-t3776254
Then again, u r flashing at ur own risk. I'll accept no blames!
ghostranger047 said:
Don't know why u r facing this problem, but I've tried almost every Oreo really roms here and all of them have stable volte! My jio works flawlessly on all of them. Just make sure u r on baseband version 1.7. Naming a few stable volte Oreo roms:
Bootleggers
DotOs
Havos Os(my currenr favourite)
Pixel experience (old rom without updates)
AospExtended
RR
CAF
etc etc...volte works everywhere!
---------- Post added at 08:03 PM ---------- Previous post was at 07:58 PM ----------
Try this:
https://forum.xda-developers.com/le...oreo-firmwarebaseband-twrp-flashable-t3776254
Then again, u r flashing at ur own risk. I'll accept no blames!
Click to expand...
Click to collapse
Thanks for your reply but the problem is I had to enable volte in stock ROM before flashing custom ROM but I didn't enable volte on stock rom.
So if I update my baseband on custom rom without flashing stock rom again will jio volte work ?
akash2018 said:
Thanks for your reply but the problem is I had to enable volte in stock ROM before flashing custom ROM but I didn't enable volte on stock rom.
So if I update my baseband on custom rom without flashing stock rom again will jio volte work ?
Click to expand...
Click to collapse
No. I tried it. It won't work. I had VoLTE working in stock rom and after rooting and unlocking the bootloader, i didn't have VoLTE enabled in any of the custom roms. I updated my baseband. I've had 1.6, 1.7 and 2.0. But none of them is a workaround for VoLTE. So as already suggested, install stock rom and then check for HD symbol on the same. (I'm yet to try this. I'll soon do it myself and may be post the result here).
And for that custom kernel question on stock rom, well you have to install stock for just few minutes or hours just to get HD symbol so that you can proceed with installing custom roms with VoLTE enabled. So, better clean install stock rom and wait for HD symbol. Then as stated before, use the same custom recovery version, you will be able to restore data back.
Guys i finally had this problem sorted out. Steps which worked for me:
1. Flash stock rom via mi flash tool - Zui 2.5
2. Wait for HD symbol and then do a test call
3. Clean install custom rom which supports VoLTE
4. Before first start, install baseband version 1.7
VoLTE worked for me like this only
I'm using AospExtended Oreo based

[DISCONTINUED]Stock ROM VER:WW-15.0410.1803.51_ROM 4/12 Update TWRP Flashable!

Hey guys since i dint see any stock roms here, i decided to make one thats possible to flash from twrp, its 100% stock nothing added nothing taken from original rom, no firmaware files in rom zip.
I have the the US Asus Zenfone 4 pro , tested ONLY ON THIS DEVICE DO NOT FLASH IT ON ANY OTHER ZENFONE YOU HAVE BEEN WARN!!
How to Flash:
1.Unlock Bootloader Via Official App
2.Flash TWRP
3:Swipe to allow modifications to system VERY IMPORTANT! flash noverity.zip just incase you get stuck in a bootlooop.
4lace zip on your sdcard/internal Storage
5:Wipe Data/System
6:Flash rom zip (Ignore "unknow command error" after flashing, i need to cleanup the update script )
7.Reboot to system
I followed these step and rom flashed fine.
I might try and do some other things with this phone, be advised i haven't tinker with android in a very very long time.
ROM Download LINKS:
OREO-WW-15.0410.1803.51.zip
Change log:
1.Security patch update
2.Improve touch sensitivity
3.Fix launcher home page folder cannot be changed
4.Fix play to/MI Box porject not full screen issue
5.Fix randomly auto reboot issue
6.Fix status bar icon to show more obviously
7.Fix audio issue in 3rd party APPs
OREO-WW-15.0410.1802.34 If you flash this you will need to flash 15.0410.1803.51 right after or you wont have audio and videos will lag.
WW-14.2610.1801.51_ROM
Change Log: January Security Updates
WW-14.2610.1712.45_ROM
Thanks Dude! Now I cant root it safe, without worrying about not having a recovery
No problem!, This will also allow people that unlocked bootloader before getting the latest ota, to be on the latest software update, il keep making these as asus releases future updates for our phones.
Added Latest WW-14.2610.1801.51 update enjoy guys.
rafyvitto said:
Added Latest WW-14.2610.1801.51 update enjoy guys.
Click to expand...
Click to collapse
Thanks dude...and sorry to ask...but can you do one with the oreo update? Thank
As soon as someone posts the oreo ota zip i will, haven't gotten the update on my phone yet ;/.
ok guys i have a working flashable OREO! but videos are lagging because i havent been able to flash the firmware files need to dig deeper into this, before releasing it, give me some time guys, also twrp is unable to decrypt OREO internal data so thats another issue, but this one si out of my league shakalaca will need to update our recovery to decryot oreo data, il upload the current rom if anyone is willinf to flash it with the current issues, let me know.
Here's a screenshot of about screen.
Proof of root on oreo
Hi.Can I update my firmware if bootloader is unlocked and root is installed?If so, how?
You want to upgrade to oreo? Or just update your current firmware?
Just wondering.Are phones updated when the bootloader is unlocked?
Yes you can update phones with unlock bootloader's, if you want official updates you need the stock recovery, the twrp flashable roms i made will give you stock recovery.
Where is the stock recovery to take?
Flash any of the twrp stock roms i made and it will give you stock recovery.
Download firmware from the official website of asus, install it via twrp
and I get stock recovery with the new firmware???You don't know when to do an unofficial unlock of the bootloader?
rafyvitto said:
ok guys i have a working flashable OREO! but videos are lagging because i havent been able to flash the firmware files need to dig deeper into this, before releasing it, give me some time guys, also twrp is unable to decrypt OREO internal data so thats another issue, but this one si out of my league shakalaca will need to update our recovery to decryot oreo data, il upload the current rom if anyone is willinf to flash it with the current issues, let me know.
Click to expand...
Click to collapse
Hi. I flashed the stock rom you uploaded because I accidentally lost mine... aside from audio/video lag issues, audio from calls were also unable to hear. Will patiently wait for your stock rom with firmware files. thaaaaanks
Go into recovery and flash the official oreo zip this will flash firmware files and fix no audio/video lag issues.
rafyvitto said:
Go into recovery and flash the official oreo zip this will flash firmware files and fix no audio/video lag issues.
Click to expand...
Click to collapse
:'(
Groundz said:
:'(
Click to expand...
Click to collapse
If you flash my oreo zip with no firmware and boot it up, this will give you stock recovery, which you will need to flash the stock oreo zip , and ofcourse you will need to reflash twrp after.

Help! My phone is stuck on bootloader warning screen

I tried to root my MZP but instead it's stuck on bootloader warning screen with ID:N/A. I know i did something wrong but how to fix this now?
It says "Your device will boot in 5 sec" but it never boots. I just updated my phone with oreo yesterday and wanted to root it but now I'm stuck with it. Please help. My device is on official oreo update launched yesterday.
can anyone upload the images for Oreo 27.76 official OTA for flashing. if i flash the older build, my phone might get bricked.
Do you have a TWRP back up to revert back to? I'm hoping you backed up your device before trying to root... Which root manager did you use?
I've not seen an Oreo fastboot ROM yet to flash.
echo92 said:
Do you have a TWRP back up to revert back to? I'm hoping you backed up your device before trying to root... Which root manager did you use?
I've not seen an Oreo fastboot ROM yet to flash.
Click to expand...
Click to collapse
It should be available soon on one of the links below:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
rafikowy said:
It should be available soon on one of the links below:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hopefully someone can then capture and upload the firmware to Android file host or somewhere reliable. The RSD server seems to reject my connection for security/authenticating reasons.
echo92 said:
Hopefully someone can then capture and upload the firmware to Android file host or somewhere reliable. The RSD server seems to reject my connection for security/authenticating reasons.
Click to expand...
Click to collapse
Ha! There is a trick I discovered few days ago.
To be "authenticated" you only need to be logged as a normal member of Lenovo Forums (https://forums.lenovo.com). While you logged in there, all data can be downloaded from https://rsdsecure-cloud.motorola.com But first of course you need to have a correct URL of .zip factory image file. They do not provide any page where all files are listed, so you can only prepare URL basing of software versions and models (as I did for the latest February fastboot image).
Sadly i didn't took the twrp backup and i was trying to install magisk :'(
I am stupid, i Should have took the backup but now it's late, i need help
rafikowy said:
Ha! There is a trick I discovered few days ago.
To be "authenticated" you only need to be logged as a normal member of Lenovo Forums (https://forums.lenovo.com). While you logged in there, all data can be downloaded from https://rsdsecure-cloud.motorola.com But first of course you need to have a correct URL of .zip factory image file. They do not provide any page where all files are listed, so you can only prepare URL basing of software versions and models (as I did for the latest February fastboot image).
Click to expand...
Click to collapse
Unfortunately, the server still reports access denied:
1)Logged into the Lenovo forums via Google account authentication.
2)Attempted to access either https://rsdsecure-cloud.motorola.com or https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (the Dec 2017 Moto Z Play stock firmware) and both times the server replied with access denied. Attempting to download the zip produced a 243 byte file.
I think that certain members or IP addresses are authorised by Motorola/their service centres to access the resources, which are otherwise restricted to the general public.
---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------
Manish355 said:
Sadly i didn't took the twrp backup and i was trying to install magisk :'(
I am stupid, i Should have took the backup but now it's late, i need help
Click to expand...
Click to collapse
Are you still able to boot into the bootloader and boot into TWRP? If so, did you/can you apply the f2fs kernel patch and the forced encryption and dm-verity settings in magisk as per the guide?
If i restore anyone elses twrp backup, will it work?
echo92 said:
Unfortunately, the server still reports access denied:
1)Logged into the Lenovo forums via Google account authentication.
2)Attempted to access either https://rsdsecure-cloud.motorola.com or https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (the Dec 2017 Moto Z Play stock firmware) and both times the server replied with access denied. Attempting to download the zip produced a 243 byte file.
I think that certain members or IP addresses are authorised by Motorola/their service centres to access the resources, which are otherwise restricted to the general public.
---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------
Are you still able to boot into the bootloader and boot into TWRP? If so, did you/can you apply the f2fs kernel patch and the forced encryption and dm-verity settings in magisk as per the guide?
Click to expand...
Click to collapse
It was happening before but now there is a mount error in twrp when flashing anything. It may be because i had wiped the system
echo92 said:
Unfortunately, the server still reports access denied:
1)Logged into the Lenovo forums via Google account authentication.
2)Attempted to access either https://rsdsecure-cloud.motorola.com or https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (the Dec 2017 Moto Z Play stock firmware) and both times the server replied with access denied. Attempting to download the zip produced a 243 byte file.
I think that certain members or IP addresses are authorised by Motorola/their service centres to access the resources, which are otherwise restricted to the general public.
Click to expand...
Click to collapse
Hmm... let's try this one:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Manish355 said:
It was happening before but now there is a mount error in twrp when flashing anything. It may be because i had wiped the system
Click to expand...
Click to collapse
Ah, that's a problem if you wiped the system. In theory, you could apply someone else's TWRP backup (but only their system and kernel partitions ideally, attempting to apply other partitions may cause even more headaches).
You may wish to flash a custom ROM to get your device working and wait for a TWRP flashable or the official Oreo stock ROM to be leaked.
echo92 said:
Ah, that's a problem if you wiped the system. In theory, you could apply someone else's TWRP backup (but only their system and kernel partitions ideally, attempting to apply other partitions may cause even more headaches).
You may wish to flash a custom ROM to get your device working and wait for a TWRP flashable or the official Oreo stock ROM to be leaked.
Click to expand...
Click to collapse
So i can flash a oreo custom rom ? But i like the stock rom because its stable and secured, Nothing against custom roms.
I wish official rom leaks soon or if you have a twrp backup, plz let me know.
Manish355 said:
So i can flash a oreo custom rom ? But i like the stock rom because its stable and secured, Nothing against custom roms.
I wish official rom leaks soon or if you have a twrp backup, plz let me know.
Click to expand...
Click to collapse
As far as I can see, that's an option if you want a working device at the moment.
I don't have a Moto Z Play, so I hope someone else can help you with the TWRP backup. If you do get your device working, please back up in future before attempting anything that affects your system.
---------- Post added at 02:17 PM ---------- Previous post was at 02:14 PM ----------
rafikowy said:
Hmm... let's try this one:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hmm, still gives the access denied error and directly linking the download produces a 0 byte file
Oh well, just trying it out of curiosity (though it would be a useful resource in general!) Thanks for the links, hope they work for others!
echo92 said:
As far as I can see, that's an option if you want a working device at the moment.
I don't have a Moto Z Play, so I hope someone else can help you with the TWRP backup. If you do get your device working, please back up in future before attempting anything that affects your system.
Click to expand...
Click to collapse
Thanks for your support, i will backup my device before flashing. I think i need to make another thread for the TWRP backup, but I'll try flashing a custom rom. But what would i do when the official leak is out? How to Uninstall the rom?
Manish355 said:
Thanks for your support, i will backup my device before flashing. I think i need to make another thread for the TWRP backup, but I'll try flashing a custom rom. But what would i do when the official leak is out? How to Uninstall the rom?
Click to expand...
Click to collapse
For flashing the official Oreo stock ROM, you'd need to flash it in fastboot/bootloader mode - you cannot flash it in TWRP. Flashing the stock ROM will remove TWRP/root/any custom ROM (and if you had a custom ROM, you will likely require a data wipe).
As you've formally updated to Oreo, I would not recommend downgrading to stock Nougat and attempting to update to Oreo via OTA. In theory, you could try flashing the Feb 2018 7.1.1 stock firmware if it's available and update (as that's the firmware directly preceding the Oreo patch), but I cannot guarantee it's safe as I've not tested it.
echo92 said:
For flashing the official Oreo stock ROM, you'd need to flash it in fastboot/bootloader mode - you cannot flash it in TWRP. Flashing the stock ROM will remove TWRP/root/any custom ROM (and if you had a custom ROM, you will likely require a data wipe).
As you've formally updated to Oreo, I would not recommend downgrading to stock Nougat and attempting to update to Oreo via OTA. In theory, you could try flashing the Feb 2018 7.1.1 stock firmware if it's available and update (as that's the firmware directly preceding the Oreo patch), but I cannot guarantee it's safe as I've not tested it.
Click to expand...
Click to collapse
Ok, I'm downloding AOSP 8.1.0, will it work ? I need ti give up using banking apps though.
Manish355 said:
Ok, I'm downloding AOSP 8.1.0, will it work ? I need ti give up using banking apps though.
Click to expand...
Click to collapse
Ok, it seems like i can't even flash a rom please help.
Manish355 said:
Ok, it seems like i can't even flash a rom please help.
Click to expand...
Click to collapse
Scroll it down, picture and share once again.
rafikowy said:
Scroll it down, picture and share once again.
Click to expand...
Click to collapse
Ok, somehow i have flashed a rom and it's working now, but is there any rom which is close to moto stock rom because i am use to it. Just installed AOSP but it's too bare bones.

Update to oreo PROBLEM

my build number is NPPS25.137-93-14
I want to update to oreo but read some posts says that i can not because of build number
HELP
ahmedAZ said:
my build number is NPPS25.137-93-14
I want to update to oreo but read some posts says that i can not because of build number
HELP
Click to expand...
Click to collapse
You must be running NPPS25.137-93-2-5 to be able to update through OTA. However, you can still update to Oreo using fastboot method (link here: https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244), but most probably, you will loose all of the data stored in the phone.
Andrej_SK said:
You must be running NPPS25.137-93-2-5 to be able to update through OTA. However, you can still update to Oreo using fastboot method (link here: https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244), but most probably, you will loose all of the data stored in the phone.
Click to expand...
Click to collapse
Is it safe to downgrade?
Some people say you may hard brick
Using adb don't need to downgrade?
ahmedAZ said:
Is it safe to downgrade?
Some people say you may hard brick
Click to expand...
Click to collapse
It's safe as long as you don't try to flash gpt and bootloader. Downgrading one (or both) of these partition results in hardbrick.
Andrej_SK said:
It's safe as long as you don't try to flash gpt and bootloader. Downgrading one (or both) of these partition results in hardbrick.
Click to expand...
Click to collapse
But if i install oreo custom rom fingerprint may not work because it needs updated bootloader
I have read something like that on forum
ahmedAZ said:
But if i install oreo custom rom fingerprint may not work because it needs updated bootloader
I have read something like that on forum
Click to expand...
Click to collapse
If you update to official Oreo but then decide, you want to install CustomROM, you have to downgrade to Nougat first. Otherwise, your fingerprint won't simply work with any CustomROM. I have already mentioned it in this thread https://forum.xda-developers.com/g5/help/finger-print-sensor-issue-oreo-roms-t3853491.
Btw, bootloader version is not related to fingerprint working or not with CustomROM. There's another partition that makes difference in it.
Andrej_SK said:
If you update to official Oreo and decide later, you want to install CustomROM, you have to downgrade to Nougat first. Otherwise, fingerprint won't work with any CustomROM. I have already mentioned it in this thread https://forum.xda-developers.com/g5/help/finger-print-sensor-issue-oreo-roms-t3853491.
Click to expand...
Click to collapse
So it is better to be on nougat if i want custom roms in future?
Treble project needs stock nougat or oreo?
ahmedAZ said:
So it is better to be on nougat if i want custom roms in future?
Click to expand...
Click to collapse
In my opininon yes, but your opininon might be different. Downgrading from official Oreo to official Nougat isn't difficult at all. You just have to remember, you can't flash gpt and bootloader. It's also recommended to avoid erase modem commands to prevent loss of IMEI.
ahmedAZ said:
Treble project needs stock nougat or oreo?
Click to expand...
Click to collapse
None of them. Treble project needs Treble TWRP and Treble LineageOS installed firstly for correct functionality of other Treble CustomROMs. More info in this thread https://forum.xda-developers.com/g5/development/treble-project-treble-cedric-t3820451.
ahmedAZ said:
my build number is NPPS25.137-93-14
I want to update to oreo but read some posts says that i can not because of build number
HELP
Click to expand...
Click to collapse
Hi everyone , I have not yet received update for Oreo ? Indian region, having same build no , my bootloader is unlocked as well
Same problem here. I have also the same build number on amzin software channel. Didn't receive the update till now. It says there is no update available.
akshayshirkar10 said:
Hi everyone , I have not yet received update for Oreo ? Indian region, having same build no , my bootloader is unlocked as well
Click to expand...
Click to collapse
achintyakv said:
Same problem here. I have also the same build number on amzin software channel. Didn't receive the update till now. It says there is no update available.
Click to expand...
Click to collapse
I was on 137-93-14 too. I flashed the fastboot firmware 137-93-2-5 to go back full stock and official. No need to re lock bootloader..then I downloaded the latest OTA update 28.85-16 and installed it via ADB sideload.
My phone is xt1670 on channel retca..though I can't say for sure what difference it makes if your on amzin. Wish I could help more.
No problem bro Yesterday I flashed the fastboot files and successfully updated to oreo which I found on this thread.
https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244
Btw you have taken the long step bro. No need to get back to 137-93-2-5.
Cheers!
Chekm8Qc said:
I was on 137-93-14 too. I flashed the fastboot firmware 137-93-2-5 to go back full stock and official. No need to re lock bootloader..then I downloaded the latest OTA update 28.85-16 and installed it via ADB sideload.
My phone is xt1670 on channel retca..though I can't say for sure what difference it makes if your on amzin. Wish I could help more.
Click to expand...
Click to collapse
achintyakv said:
No problem bro Yesterday I flashed the fastboot files and successfully updated to oreo which I found on this thread.
https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244
Btw you have taken the long step bro. No need to get back to 137-93-2-5.
Cheers!
Click to expand...
Click to collapse
i updated through twrp
@achintyakv
Yeah your right that was definitely the long way hehe. It's cause I wasn't sure that th oreo fastboot method would have worked for me. I had tried the TWRP version and it kept boot looping so I thought the other way would be safer

Categories

Resources