Hi.
I accidentally bricked my Moto Z2 Play and after flashing 2018 ROM boot stuck at bootloader warning with error "Bad ID". I hope it's just because this ROM is too old and somehow flashing the one that was there before will fix it.
So I'm looking for a latest, I don't remember exactly, 2019 February or March ROM, preferably fastboot flash-able.
Many thanks in advance!
Related
So, I just installed the May 2017 security update on my Pixel XL. Now, when I go to re-root it after applying the update, I get a boot loop.
I have to reflash both boot slots with stock and boot back in to android without rooting/installing the root files.
Is anyone else having trouble rooting with the May 2017 security update? If not, how'd you do it?
NWolf said:
So, I just installed the May 2017 security update on my Pixel XL. Now, when I go to re-root it after applying the update, I get a boot loop.
I have to reflash both boot slots with stock and boot back in to android without rooting/installing the root files.
Is anyone else having trouble rooting with the May 2017 security update? If not, how'd you do it?
Click to expand...
Click to collapse
Lots of us, its all blown up. Thread in the news and guide section. You can reflash the April boot image and it will work.
Oops, Toni beat me to it.
oh i am not alone...
glad that i see this post before looping for 100 times more...
Hi,
I have moto z play , reteu software channel and it seems that I'm stuck on npns26.118-22-1 with security patch stuck on august 1, 2017.
When I go to system updates I get system up to date.
I got my moto z play from a friend so I dont know if I have the latest updates but it seems that i dont as some poeple have newer security patch level. My friend didnt fiddle with the phone in any way and I can confirm that everything is stock(BL locked - OEM locked, not rooted)
Thanks for your help
Im also stuck on that version. Somehow i cant receive updates.
G4liant said:
Im also stuck on that version. Somehow i cant receive updates.
Click to expand...
Click to collapse
I managed to get the latest update(OTA) (december patch) when I reinstalled my android by following this guide
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
Hi
I have updated my stock naugat to feb 2018 but now i want to sideload 8.0 so i have to go back to dec patch how can i do that?
Use caution if you do this, it's my understanding that a couple of users have done this, and were subsequently hard bricked.
In addition to dandrumheller's reply, I would not recommend downgrading and then try to apply the OTA Oreo update. This appears to be a nasty hardbrick and the blankflashes we have do not seem to work.
Safest way would be to wait for the official Oreo OTA or the official Oreo fastboot ROM, as I mentioned previously to you.
I just got a second hand Moto Z2 Play which is a XT1710-09 on android 7.1.1 with security patch level February 1, 2018 and reteu Software Channel with build number NPSS26.118-19-22.
It was already reset when I got it and after I done my initial setup I got a prompt to update to android 8.0, April 1, 2018, OPS27.76-12-25 but after I wait for the download to finish (tried on both wifi and mobile data) it says the update couldn't be validated and to try again.
I went ahead in the recovery and deleted cache and factory reset once again and I get the same issue. The bootloader also shows the software as being modified and not official.
Any tips ? I really wouldn't want to return the phone because I love it so far but if there's no solution I'll just have to go ahead and get my money back
Ich guess your bootloader ist unlocked? Well then you cant make ota Updates anymore, but you can Install a full rom via Fastboot.
It says oem_locked when I boot into fastboot mode :/ I was able to update to February 2019 security patch and Android 8.0.0 by using fastboot tho. Is this the latest security patch available ?
Hir0xM said:
It says oem_locked when I boot into fastboot mode :/ I was able to update to February 2019 security patch and Android 8.0.0 by using fastboot tho. Is this the latest security patch available ?
Click to expand...
Click to collapse
Yep, that's indeed the last one.
That's the one I have.
I've not been having a good experience with Q and now that TWRP has been released, it gives me more reason then ever to go back to pie.
I've successfully unlocked the bootloader, but it refuses to even start flashing the old image because of a bootloader version mismatch (3a has a newer version). I've tried both 9.0.0 (PQ3B.190801.002, Aug 2019) and 9.0.0 (PD2A.190115.029, Mar 2019) to no avail.
I'm sure I'm not the only one to experience this, and any help will be appreciated.
Not sure but in my experience with 3a Xl, I just unlocked bootloader and fastboot flashall from the stock 9.0 factory rom. Then boot twrp and install custom 9 rom. I got issues until I decided to flash the Google factory 1st release 9 rom. Just my 2 cents.
Yeah, you will definitely need to flash all to downgrade. I think the radio is the same but the bootloader isnt.
Solved, turns out that it was outdated device drivers that kept flash-all from flashing an older bootloader image.