Develop Bugs

Guide to restoring factory Image that works?

There isn't much on restoring this device at all. I'm really disappointed. I had high hopes. Anyway, the root situation is a mess, and after looking on here, I couldn't find a single set of instructions for properly flashing root. After digging around for a couple of hours, the only instructions I can find to revert to stock is:
1) Extract folder on PC.
2) Hold POWER and VOL DOWN on the phone to access the fastboot mode. Try to release the power button first before the VOL DOWN in case you trigger the system boot accidentally.
3) Connect USB cable to PC.
4) Flash in the following order:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
Complete restore
WARNING: May wipe device, and has not been personally tested.
Before flashing the above, flash these first:
Code:
fastboot flash gpt.bin partition
fastboot flash bootloader.img bootloader
fastboot flash NON-HLOS.bin modem
fastboot flash fsg.bin fsg
fastboot flash adspso.bin dsp
fastboot flash logo.bin logo
BUT I cannot get this to work because I keep getting a "Image not signed or corrupt" error. I've confirmed I have the US retail single sim version (Addison).
I also cannot find a working version of RSD Lite that detects my phone. I've tried version 6.2.4.
Would anyone be able to help? I'd really appreciate it. I can get the bootloader up, but I cannot do anything else.

I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.

uberano26 said:
I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.
Click to expand...
Click to collapse
I appreciate the reply. RSD doesn't detect, but ADB can. I can send fastboot commands via the bootloader, so I think drivers are OK. What got me in this mess was flashing the Chinese TWRP posted on the root guide here on XDA so I think the drivers are installed ok. I think it's a Windows thing.
I found that page you're referring to last night and read up on it. I found the retail US stock firmware image posted by another here on XDA and proceeded to go through the steps. After looking, the batch file immediately closed and did nothing. Then I went into the XML file and removed the m in mfastboot. After runnng manually, I found that it kept saying mfastboot.exe is not found. Then it went through every step as I've seen before, but every time a command was finished it would say "Image not signed or corrupt". I believe if I could somehow get RSD lite to work that I would be OK. I'd love to get this thing booting again.

uberano26 said:
I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.
Click to expand...
Click to collapse
OK, I found mfastboot.exe located here (http://forum.xda-developers.com/gen...ng-mfastboot-exe-to-unbrick-motorola-t3203518) and had NO idea there was such a thing as mfastboot !
Unfortunately when running this, on all of these lines of mfastboot:
mfastboot flash gpt.bin partition
mfastboot flash bootloader.img bootloader
mfastoot flash NON-HLOS.bin modem
mfastboot flash fsg.bin fsg
mfastboot flash adspso.bin dsp
mfastboot flash logo.bin logo
I get "Image not signed or corrupt"
When I flash all of these, they go through OK:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
So I'm hoping this helps someone figure out what I'm doing wrong. Again, I'm just trying to get back to stock.

- You are restoring the firmware without wiping the device, i'd try fastboot erase userdata first before flashing the rest, could be worth a try.
- I get "Image not signed or corrupt" when flashing a modified kernel too, but it is flashed regardless.
- I got root with the chinese twrp, the others gave me bootloop.
Good luck.

I too have a freshly-bricked EU dual-SIM Z Play that gives "Image not signed or corrupt" errors when I try to flash recovery and boot. Seen by fastboot, but not by RSD.
edit: more of my saga is here http://forum.xda-developers.com/moto-z-play/help/identifying-firmware-required-phone-t3517360/

yeahhh, i manage to flash my moto z play back to stock, the rom was bad or something i downloaded from here.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETLA/
so happy

joesee said:
There isn't much on restoring this device at all. I'm really disappointed. I had high hopes. Anyway, the root situation is a mess, and after looking on here, I couldn't find a single set of instructions for properly flashing root. After digging around for a couple of hours, the only instructions I can find to revert to stock is:
1) Extract folder on PC.
2) Hold POWER and VOL DOWN on the phone to access the fastboot mode. Try to release the power button first before the VOL DOWN in case you trigger the system boot accidentally.
3) Connect USB cable to PC.
4) Flash in the following order:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
Complete restore
WARNING: May wipe device, and has not been personally tested.
Before flashing the above, flash these first:
Code:
fastboot flash gpt.bin partition
fastboot flash bootloader.img bootloader
fastboot flash NON-HLOS.bin modem
fastboot flash fsg.bin fsg
fastboot flash adspso.bin dsp
fastboot flash logo.bin logo
BUT I cannot get this to work because I keep getting a "Image not signed or corrupt" error. I've confirmed I have the US retail single sim version (Addison).
I also cannot find a working version of RSD Lite that detects my phone. I've tried version 6.2.4.
Would anyone be able to help? I'd really appreciate it. I can get the bootloader up, but I cannot do anything else.
Click to expand...
Click to collapse
joesee said:
OK, I found mfastboot.exe located here (http://forum.xda-developers.com/gen...g-mfastboot-exe-to-unbrick-motorola-t3203518) and had NO idea there was such a thing as mfastboot !
Unfortunately when running this, on all of these lines of mfastboot:
mfastboot flash gpt.bin partition
mfastboot flash bootloader.img bootloader
mfastoot flash NON-HLOS.bin modem
mfastboot flash fsg.bin fsg
mfastboot flash adspso.bin dsp
mfastboot flash logo.bin logo
I get "Image not signed or corrupt"
When I flash all of these, they go through OK:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
So I'm hoping this helps someone figure out what I'm doing wrong. Again, I'm just trying to get back to stock.
Click to expand...
Click to collapse
The commands that aren't working aren't being given correctly. Should be like this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin

Milly7 said:
The commands that aren't working aren't being given correctly. Should be like this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
Click to expand...
Click to collapse
You just saved my phone. Can I buy you a beer or something?

theodric said:
You just saved my phone. Can I buy you a beer or something?
Click to expand...
Click to collapse
It's all good. Just helping out. Glad it helped.

joesee said:
There isn't much on restoring this device at all. I'm really disappointed. I had high hopes. Anyway, the root situation is a mess, and after looking on here, I couldn't find a single set of instructions for properly flashing root. After digging around for a couple of hours, the only instructions I can find to revert to stock is:
1) Extract folder on PC.
2) Hold POWER and VOL DOWN on the phone to access the fastboot mode. Try to release the power button first before the VOL DOWN in case you trigger the system boot accidentally.
3) Connect USB cable to PC.
4) Flash in the following order:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
Complete restore
WARNING: May wipe device, and has not been personally tested.
Before flashing the above, flash these first:
Code:
fastboot flash gpt.bin partition
fastboot flash bootloader.img bootloader
fastboot flash NON-HLOS.bin modem
fastboot flash fsg.bin fsg
fastboot flash adspso.bin dsp
fastboot flash logo.bin logo
BUT I cannot get this to work because I keep getting a "Image not signed or corrupt" error. I've confirmed I have the US retail single sim version (Addison).
I also cannot find a working version of RSD Lite that detects my phone. I've tried version 6.2.4.
Would anyone be able to help? I'd really appreciate it. I can get the bootloader up, but I cannot do anything else.
Click to expand...
Click to collapse
I had the complete restore section reversed when you saw it on my thread, someone pointed it out and it's been fixed now.
Edit: I see someone's done it here too.
You also don't need to restore fully, just do the restore for ota and it should be enough if you've not flashed over the other stuff.

well i forgot to boot and set up a pin before installing TWRP, soft bricked myself for hours, this thread helped me return to stock so i could set a pin so TWRP would work, THANK YOU!
also if anyone else ends up here, and is having trouble finding the US retail stock image, i used the one from https://mirrors.lolinet.com/firmware/moto/addison/official/RETUS/

Is that an official signed image?
Can i use it to relock bootloader?
Thanks!

dyonissos said:
Is that an official signed image?
Can i use it to relock bootloader?
Thanks!
Click to expand...
Click to collapse
None of the images are signed and won't relock the bootloader.

Would this allow me to return to Marshmallow after sideloading a Nougat OTA, given I unlock my bootloader? I flashed a build from a different region (I think retbr or something) onto my Canadian Z Play, but the build number doesn't match what everyone else is getting from. Just looking to revert to Marshmallow to perform a proper update instead of impatiently sideloading an OTA.

IncendiaryPyro said:
Would this allow me to return to Marshmallow after sideloading a Nougat OTA, given I unlock my bootloader? I flashed a build from a different region (I think retbr or something) onto my Canadian Z Play, but the build number doesn't match what everyone else is getting from. Just looking to revert to Marshmallow to perform a proper update instead of impatiently sideloading an OTA.
Click to expand...
Click to collapse
Yep if you have the right factory image for your device.

Leraeniesh said:
Yep if you have the right factory image for your device.
Click to expand...
Click to collapse
Thank you. I've never had issues doing stuff like this before, but for some reason it scares the hell out of me with this phone. Maybe because I haven't had it for very long, lol. Downgraded to Marshmallow successfully. Hopefully I don't run into any issues in the future that would require an RMA, but out of all the phones I've had over the years, I've only had to RMA a Nexus 5 due to a problem with the screen.

Hi everyone. Is this guide is okay for reteu dual sim? And please point me if there is a firmware for reteu nougat. I softbrick my device and my imei is 0. I want to restore it please guide me as i am a noob in fastboot commands and steps. Thanks in advance

Vitxlss said:
yeahhh, i manage to flash my moto z play back to stock, the rom was bad or something i downloaded from here.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETLA/
so happy
Click to expand...
Click to collapse
do you have rooted device with twrp (maybe) ?
also, is the boot.img you got from Android 7 or 6.xx ?
Thanks

I use the DOWNGRADE script found here :
https://drive.google.com/file/d/0B134drJ4-Ed0MHQ5aE1wUmp5eFk/view
The original discussion here :
https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118
Note that the original script is not ideal. The actual script came from @-=MoRpH=- on comment #4

Solution to flash stock rom(factory image) via fastboot and locking the bootloader..

Hey Guys,
I recently had hardbricked my potter device.. Was unable to flash any rom, not even stock rom and I didnt find any thread in this forum which could have helped me.
I unbricked my device, flashed the stock rom and locked the bootloader,
The following steps will also get you unbrick your device... So, I would like to share the steps with all of you.
Note that this isnt only for unbricking, this can be done by any user who wants to flash stock rom and lock their bootloader.
Step 1: Download your potter rom from the following link: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
"POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" download the following zip file.
Step 2: Download Minimal adb and fastboot from the following link: https://androidfilehost.com/?fid=745425885120698566
Step 3: Install Minimal adb and fastboot and extract the downloaded rom to the same folder where you have installed Minimal And fastboot package.
Step 4: After extracting open command prompt in that folder (where you have extracted the rom/ the adb and fastboot folder)
Step 5: Now boot your phone into your bootloader by pressing volume down+ power button at the same time.
Step 6: Type the following in your command prompt: fastboot devices
If it detects your device move to the next step, if it does not then you will have to install drivers for your device.
Step 7: Now Copy the following code and paste it to your command prompt:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Step 8: This will completely wipe your data and install stock 7.0 OS on your potter device. Note that this does not lock your bootloader.
Step 9: Boot your device to check if it boots and if it works.... now if you want to lock your bootloader move to the next step.
Step 10: Reboot again into your bootloader.
Step 11: Again follow the step 4, step 5 and step 6.
Step 12: Now paste the following commands in the command prompt:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Step 13: Reboot your device...
In this way you will be able to move to stock rom and lock your bootloader..
Please do comment if this works for you too and if you find any issues...
Thank you!!
All the Best!!:fingers-crossed::fingers-crossed::good::good:

rishivg said:
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
Click to expand...
Click to collapse
The quoted lines are redundant (surely they gave you an error since they don't exist in the G5+ firmware)
Otherwise, pretty standard Moto stuff... interesting that in 5th gen stuff you can lock after only flashing system sparsechunks, almost all previous devices required a complete flash with wipe to relock. https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ is another good source for stock factory ROM's (it is the official repo of FirmwareTeam), and Minimal ADB and Fastboot has a lots of "hacks" out there, so it is best to only reference the original source: https://forum.xda-developers.com/showthread.php?t=2317790
I am extremely familiar with previous Moto device, but am curious on this device what is the bootloader status number after relocking with this method and do you still get the unlocked warning screen after relocking like on previous Moto devices?

Hi,
Great if this guide works (not tested by me). However, it sounds viable. :good:
In any case, I suggest to put the original device and retail versions witht the link of the firmware. For example:
- XT1680 & retus: "POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
This is necessary. For example my is XT1685 and RETEU, then this file is not for me!

Not working. Its says cant be downgrade.

No does not work with the XT 1685 and reteu

surjeet.vishwas said:
Not working. Its says cant be downgrade.
Click to expand...
Click to collapse
what is your model number?

rishivg said:
what is your model number?
Click to expand...
Click to collapse
Xt1686 but i download another stock rom

surjeet.vishwas said:
Xt1686 but i download another stock rom
Click to expand...
Click to collapse
okay that is why it gave you error, try with the file that is mentioned in the post

This only works if you are on a previous or the exact same build. If you have already installed the August ota atm you can't relock the bootloader.

Gingernut78 said:
This only works if you are on a previous or the exact same build. If you have already installed the August ota atm you can't relock the bootloader.
Click to expand...
Click to collapse
yes exactly! you ll need to flash the whole previous build again...

rishivg said:
yes exactly! you ll need to flash the whole previous build again...
Click to expand...
Click to collapse
You can flash a previous build but it won't lock the bootloader that is the problem.

Gingernut78 said:
You can flash a previous build but it won't lock the bootloader that is the problem.
Click to expand...
Click to collapse
it will

rishivg said:
it will
Click to expand...
Click to collapse
The firmware will only re-lock your bootloader in that case if it's of the same or newer patch level as your bootloader. Older firmwares, as Gingernut78 pointed out, will get you back to stock, but if you're on the August 2017 patch level (and your bootloader is at the August 2017 patch level as well), you need a August 2017 or later stock ROM to re-lock your bootloader.

rishivg said:
Hey Guys,
I recently had hardbricked my potter device.. Was unable to flash any rom, not even stock rom and I didnt find any thread in this forum which could have helped me.
I unbricked my device, flashed the stock rom and locked the bootloader,
The following steps will also get you unbrick your device... So, I would like to share the steps with all of you.
Note that this isnt only for unbricking, this can be done by any user who wants to flash stock rom and lock their bootloader.
Step 1: Download your potter rom from the following link: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
"POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" download the following zip file.
Step 2: Download Minimal adb and fastboot from the following link: https://androidfilehost.com/?fid=745425885120698566
Step 3: Install Minimal adb and fastboot and extract the downloaded rom to the same folder where you have installed Minimal And fastboot package.
Step 4: After extracting open command prompt in that folder (where you have extracted the rom/ the adb and fastboot folder)
Step 5: Now boot your phone into your bootloader by pressing volume down+ power button at the same time.
Step 6: Type the following in your command prompt: fastboot devices
If it detects your device move to the next step, if it does not then you will have to install drivers for your device.
Step 7: Now Copy the following code and paste it to your command prompt:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Step 8: This will completely wipe your data and install stock 7.0 OS on your potter device. Note that this does not lock your bootloader.
Step 9: Boot your device to check if it boots and if it works.... now if you want to lock your bootloader move to the next step.
Step 10: Reboot again into your bootloader.
Step 11: Again follow the step 4, step 5 and step 6.
Step 12: Now paste the following commands in the command prompt:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Step 13: Reboot your device...
In this way you will be able to move to stock rom and lock your bootloader..
Please do comment if this works for you too and if you find any issues...
Thank you!!
All the Best!!:fingers-crossed::fingers-crossed::good::good:
Click to expand...
Click to collapse
thank you so much you safe my life:good

rishivg said:
yes exactly! you ll need to flash the whole previous build again...
Click to expand...
Click to collapse
Please let me know how. I'm on August security patch. Xt1686 67 5 build indian version. I can flash only 67 5 build stock rom. When i try flashing older stock roms, it says bootloader version downgrade. Please please tell me how i can fully go back to stock.

ksvirdi105 said:
Please let me know how. I'm on August security patch. Xt1686 67 5 build indian version. I can flash only 67 5 build stock rom. When i try flashing older stock roms, it says bootloader version downgrade. Please please tell me how i can fully go back to stock.
Click to expand...
Click to collapse
dont flash the bootloader! ignore that command and report!:fingers-crossed:

rishivg said:
dont flash the bootloader! ignore that command and report!:fingers-crossed:
Click to expand...
Click to collapse
Are you sure it will work perfectly. No bricking and stuff?? which commands should i skip.
And once i flash it will i be able to get ota to august patch and relock?

ksvirdi105 said:
Are you sure it will work perfectly. No bricking and stuff??
Click to expand...
Click to collapse
it wont brick your device.. try it out:good:

rishivg said:
it wont brick your device.. try it out:good:
Click to expand...
Click to collapse
Once i flash it will i be able to get ota updates.

ksvirdi105 said:
Once i flash it will i be able to get ota updates.
Click to expand...
Click to collapse
lock your bootloader, you ll get updates but not security updates.. I dont know why? Need some help from developers

Help Z2 PLAY XT1710-11 + Testing

Hi everyone I have some questions if here in the forum we can solve them together
Without offending or underestimating the work of forum members and the people I have quoted, I only try to find solutions​
I have the Chinese version of the Motorola Z2 Play Model XT1710-11, so I wanted to remove the default firmware with ZUI!. by 7.1.1_NZS26.71-36
First try Unlocking the bootloader to work clean following the steps of many sites who recommend working with the unlocked bootloader But unfortunately when I tried to unlock it, it told me a message "BAD KEY", Look for this type of problems in the forum and other sites, according to the problem is because the supplier who I buy it in China, should give me the key, since it is likely that the seller has changed it. Unfortunately the seller does not answer me and I do not think he does.
1. So the first question is: Is it possible to do the flash even if you have this kind of problem?
First I use this command as the flash comes, blocked from the factory by the supplier:
fastboot flashing unlock
Click to expand...
Click to collapse
First of all make a backup of the firmware, and all the elements with the TWRP here: https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Thanks to @Junior Passos , for his post, who helped me to do it, and in case someone has this phone model with the same "BAD KEY" problem. and be afraid of damaging it, it was tested and it worked normally.
The first problem in my head was that I did not like the operating system that brought by default my Z2-XT1710-11, because even if it was in Spanish or English there were places in the Chinese system
So, what I wanted was a clean and operable nougat.
I started looking for this exact model on the Internet and in the forum, I did not find a specific topic of this model, but in the comments of someone who had it, its name is: @LunaTheLuminous Who had a problem with their modems, https://forum.xda-developers.com/z2-play/help/fastboot-xt1710-11-china-mobile-modem-t3801969.
I did not have a modem problem because I had done backup, but I wanted to try to get to a clean rom and try to flash with comments from @KirMit from here: https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3. Unfortunately there were not the exact commands that he use, for avoid some kind of brick in my device.
Then I continued looking for the same model, and I found something similar that I decided to try : https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668. The original idea is to try to get a clean Nougat, According to @KirMit he managed to get a Clean nougat by using Two ROM, which I do not know From Here: https://forum.xda-developers.com/showpost.php?p=74833568&postcount=17.
I tried to find a clearer solution, because I had doubts about the exact commands that I use and roms, below in the comments, KirMit explains: that "the best manual is in the post" . I decided to use the @lexie90 tutorial https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668 Thanks with this ROM: "ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml"
and These commands:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
NOTE: The commands that are In red do not use them, I put them to see, the commands that I use and the ones that you do not have to use
Here I found a problem, because the bootloader has "BAD KEY" I can not close the OEM LOCK, and in the stage of flash recovery and flash boot it showed this message:
"Image signed with key bad key"
Click to expand...
Click to collapse
The flash of the firmware was made, I could go to the Nougat, Stock Running the modem, fingerprint reader, but when I turned on the phone I got a "bad key error message", looking for this type of problem is that the "logo.bin" file was necessary flash it, Unfortunately I could not find the original, but in the forum there are several people who have made their own logo.bin as: https://forum.xda-developers.com/moto-z/themes/logo-bin-to-remove-unlocked-warning-n-t3757030, and https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153 Thanks to @TobiPeter and @flashallthetime .
But when trying to flash it, and since they were from z play, the screen did not look good, therefore after several tests to eliminate this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To delete the message, from the motorola z2 play MODEL: XT1710-11, I did a flash with the logo that I made in the backup of the twrp.
https://drive.google.com/open?id=1OjPxy5k02MrH73SXZoXjI1sZCp83uFAr
With this command:
fastboot flash logo logo.emmc.win
Click to expand...
Click to collapse
2. My question is is there any way to make a flash clean and to install normal without any error with this type of BAD KEY problem?
But I did not just try that Rom, try several Stock Roms which I present to you in this list:
ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_RETAIL_7.1.1_NPSS26.118-19-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_NPSS26.118-19-1-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
CHINESE VERSION XT1710-08
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-36_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-97-41-9_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Click to expand...
Click to collapse
Also try to change the command to try to see if there was the error, and use these: https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479, Thanks to @Kacike27 , Always avoiding:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
In the ROM of China I decided to make a full flash using all the commands, as @KirMit said in one of his comments.
https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3
Hi. Use this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
I flashed all using standard set of fastboot commands including modem flashing and erasing. You will boot in Chinese version, but still able to change a language to English in preferences menu (try to find a right menu by logos). It is still Android Nougat 7.1.1 with CH/EN only languages.
After that I flashed this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
But skip modem flashing and erasing. You will have multi language Android Oreo.
Enjoy.
Click to expand...
Click to collapse
Unfortunately I did not succeed the result was the same "bad key" errors and commands ("Image signed with key bad key", FAILED) Etc.
But as you will understand, I was not satisfied with the fact of all these mistakes, which were presented to me along the way, so I decided to do an update to OREO of both version ZUI!!!, and Stock of rom 7.1.1 ALBUS_NPSS26.118-19-4.
Then I followed the instructions in this post by @HTCDevil https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 Thanks!!!
I followed the following commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Following the advice of KirMit, I do not use the commands that are in red
By @KirMit
I confirm, that all is working after update on XT1710-11 (China Mobile), BUT! do not flash all - skip:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
If you want your modems and fingerprint sensor are still working!
Click to expand...
Click to collapse
The process that I did for fastboot, it did not work for me, unfortunately the same mistakes appeared in the previous roms, I have to add that when updating to Oreo, in both versions, ZUI and 7.1.1 (Stock ALBUS_NPSS26.118-19-4.), the fingerprint reader stopped working.
The device, started to "encrypt", when I wanted to downgrade to 7.1.1 ALBUS_NPSS26.118-19-4 or ZUI!!. In the command stage:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
The commands were throwing error, (failed), now the question is:
3.It is possible that I can not flash the Bootloader, nor do the gpt partition, because the device is encrypted or has the oreo bootloader
?
To finish I try to flash with RSD Lite, without any result, due to the error when it goes in :"fastboot flash partition gpt.bin", it can not execute the flash in the gpt, it stays stuck in that stage.
The testing of RSD lite was with the help of the following post:
https://forum.xda-developers.com/showpost.php?p=76454434&postcount=29 by @St.Nogiel
https://forum.xda-developers.com/moto-z-play/how-to/mini-guide-bricked-special-case-attempt-t3812530 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/addison-factory-stock-images-t3736767/post75236696#post75236696 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194 by @KrisM22
Click to expand...
Click to collapse
end of the tests,
sorry for my English. greetings friends

I got a z2 play in secondhand.
This phone is from china mobile and the previous owner has flashed 7.1.1 .
Now the phone is stuck in 7.1.1 and it does not get get updated to 9.0.
Is there any way this can be done.
I contacted Lenovo and they say that the build number is not in the database .

(Bootloader) Permission denied [SOLVED]

Hi, I used Carbon ROM on XT1670, when I wanted to change ROM I ran:
Code:
fastboot -w
And i got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also tried to remove them:
In TWRP I tried to do something but all I get is something similar to this:
Am I missing something? Thanks for your help.

I've been reading the question and answer forum, apparently it's a problem with the encryption.
I don't have the Moto G5 right now, I can try it in a couple of hours, what other solution could I have anyway?

In twrp go to wipe
Then press the option on the right to format data
Reboot to recovery
Note this is different from wipe data from the advanced wipe menu.
The fastboot command would be
fastboot erase userdata

TheFixItMan said:
In twrp go to wipe
Then press the option on the right to format data
Reboot to recovery
Note this is different from wipe data from the advanced wipe menu.
The fastboot command would be
fastboot erase userdata
Click to expand...
Click to collapse
Hello, good (and bad) news
I did and now I have MTP for TWRP.
But still CMD says "Bootloader is logical @@@ not found"
"@@@" is depending on what you are trying to flash, be it system or recovery.
I was also able to change the filesystem I did it for DATA / CACHE / SYSTEM I went from FAT and then to EXT4 again.
Insert a ROM and it flashed without problems but it starts again in fastboot, the same if I do it with ADB Sideload.
I also tried flashing Stock ROM, everything seems to be written without problem but with the first line of "Bootloader logical ... not found" and again start in fastboot.
It makes me believe that something is still encrypted.
I mean this.

I also tried
Code:
fastboot format:ext4 userdata
But I have this:

Bootloader is logical not found - this is normal output
Why are you trying to change formats? You are going to have issues especially with encryption. Use twrp to format not fastboot if you are messing with formatting but make sure you know what you are doing!

TheFixItMan said:
Bootloader is logical not found - this is normal output
Why are you trying to change formats? You are going to have issues especially with encryption. Use twrp to format not fastboot if you are messing with formatting but make sure you know what you are doing!
Click to expand...
Click to collapse
I flash a rom (no apparent problem, even Stock ROM) but it only boots to fastboot or the robot with an open belly.
What exactly should I do, I will follow step by step, I really need to get it back. Thank you very much for your help.

Hello again, I saw you in another post that apparently has the same problem as me, it is this:
Decryption unsuccessfull
Hi guys, I have a problem with my motorola moto g5. It turns out that I upgraded to android oreo and at the time of associating the fingerprint I asked for a pin for security which I put. En el twrp me pide el pin, el cual ingresa y ya podia...
forum.xda-developers.com

I have the same bugs, do you think I should run the command to decrypt?

Dislekzi4 said:
Ok, I'll get to the point.
I flash a rom (no apparent problem, even Stock ROM) but it only boots to fastboot or the robot with an open belly.
What exactly should I do, I will follow step by step, I really need to get it back. Thank you very much for your help.
Click to expand...
Click to collapse
In twrp format data
That is by selecting wipe
Then the option on the right to format data
Reboot to recovery
Everything should now be mountable
Make sure you are flashing stock rom correctly
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Making sure you are flashing the same or newer firmware version than already on your phone
If your phone keeps booting to recovery (android with an open stomach or twrp) then do this
Boot into twrp then connect phone to PC and in cmd/terminal type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Reboot and your device will boot normally (assuming you have a working rom)

Hi, it work!
Thank you very much for your time and help, I am very grateful, for a moment I thought it was really a hardware problem.

I get device unauthorized. Please check the confirmation dialog on your device. and it won't let me do anything

Rod_Ems said:
I get device unauthorized. Please check the confirmation dialog on your device. and it won't let me do anything
Click to expand...
Click to collapse
Enable adb debugging on your device in dev options
Make sure you are using the latest platform tools
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip
Navigate your cmd window to to the platform tools directory
In cmd type
adb devices
Look on your phone and a window will pop up asking you to confirm authorisation - tick the box to allow always if you want to
Then type
adb devices
And your device is authorised

TheFixItMan said:
In twrp format data
That is by selecting wipe
Then the option on the right to format data
Reboot to recovery
Everything should now be mountable
Make sure you are flashing stock rom correctly
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Making sure you are flashing the same or newer firmware version than already on your phone
If your phone keeps booting to recovery (android with an open stomach or twrp) then do this
Boot into twrp then connect phone to PC and in cmd/terminal type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Reboot and your device will boot normally (assuming you have a working rom)
Click to expand...
Click to collapse
mine show the following error message: device '(null)' not found

danniel_sx said:
mine show the following error message: device '(null)' not found
Click to expand...
Click to collapse
Either
Your phone is not connected to pc
Faulty cable
You haven't installed Motorola USB drivers
You are using the wrong commands
If in fastboot mode type
fastboot devices
If in recovery mode type
adb devices
Your device should be listed if correctly connected

I found a solution, i'm argentinian so sorry if my english is bad
the fastboot menu of the combination power + volume down have no permissions to all modifications
You have to acces to the recovery fastboot menu, to do this, move to "recovery mode" enter here with power
Now if in the screen appears "No command" you have to press power + volume down for 3 sec and press vol up without press the another 2, then release the 3 buttons
Now go to "fastboot" in the recobery mode, and ta daaa. You have permissions

[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12

As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this!
ANSWER - THE BOOTLOADER!
Massive Update! Someone found a way to recover the phone using EDL Deep Flash Cable.
XDA Thread Link
(Even though I tried it when it happened to me all this time ago and it didn't work, but it does seem to work for few people who used a Black & White cable from AliExpress (maybe there's some hidden tech inside) so give it a try and report, there's also a chance that maybe some devices don't get burned out but simply refuse to boot because voltage is too high, and others might be fried forever, we will see with time I guess. Nonetheless, Good Luck!)
While OxygenOS OTA is mostly safe, it can still accidentally flash the wrong bootloader on Your phone! Examples are having Magisk Props Module installed which will lead to OxygenOS flashing the wrong image or TWRP telling payload to flash DDR4 bootloader onto DDR5 device.
But wait.. how can an official bootloader kill the motherboard beyond MSM?! Well.. Here's the thing, OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one You flash.
But wait.. isn't there any protection to stop this from happening? Well.. there should be. In fact previously OnePlus 8 and 8 Pro firmwares both shipped with single bootloader that was either designed for DDR4 or DDR5. Now since OxygenOS 12 they started shipping DDR4 and DDR5 in the same package. And the reason why the phone dies is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
How can we tell which one we should flash if we end up flashing OOS OTA manually through fastboot?
Update: Double check Your RAM just in case!
Post #3
If You have OnePlus 8 (DDR4) You're supposed to flash xbl.img & xbl_config.img
If You have OnePlus 8 Pro / 8T / 9R (DDR5) You're supposed to flash xbl_lp5.img & xbl_config_lp5.img
I recommend everyone who makes fastboot flashers to include that change or make separate flashers for each codename!
Previously LP5 was only available in 9R firmware but it seems that OnePlus after joining OPPO has changed things a little and made things quite dangerous for many people.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Images above show that there are some checks but unfortunately they don't seem to work correctly and voltage is being set too high anyway.
So, Dear OnePlus, please stop adding non DDR5 bootloader to 8 Pro firmware builds! Or at least add protection to fail boot if DDR5 is detected.

ProtoDeVNan0 said:
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this!
ANSWER - THE BOOTLOADER!
While OxygenOS OTA is mostly safe, it can still accidentally flash the wrong bootloader on Your phone! Examples are having Magisk Props Module installed which will lead to OxygenOS flashing the wrong image or TWRP telling payload to flash DDR4 bootloader onto DDR5 device.
But wait.. how can an official bootloader kill the motherboard beyond MSM?! Well.. Here's the thing, OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one You flash.
But wait.. isn't there any protection to stop this from happening? Well.. there should be. In fact previously OnePlus 8 and 8 Pro firmwares both shipped with single bootloader that was either designed for DDR4 or DDR5. Now since OxygenOS 12 they started shipping DDR4 and DDR5 in the same package. And the reason why the phone dies is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
How can we tell which one we should flash if we end up flashing OOS OTA manually through fastboot?
If You have OnePlus 8 (DDR4) You're supposed to flash xbl.img & xbl_config.img
If You have OnePlus 8 Pro / 8T / 9R (DDR5) You're supposed to flash xbl_lp5.img & xbl_config_lp5.img
I recommend everyone who makes fastboot flashers to include that change or make separate flashers for each codename!
Previously LP5 was only available in 9R firmware but it seems that OnePlus after joining OPPO has changed things a little and made things quite dangerous for many people.
View attachment 5578875
View attachment 5578877
Images above show that there are some checks but unfortunately they don't seem to work correctly and voltage is being set too high anyway.
So, Dear OnePlus, please stop adding non DDR5 bootloader to 8 Pro firmware builds! Or at least add protection to fail boot if DDR5 is detected.
Click to expand...
Click to collapse
This is so F'ing insane

Some extra warnings:
1. OnePlus 8T/9R also has LPDDR4x variant, make sure the variants before flashing.
2. The DDR detection process was artificially killed, stay away from the Magisk modules to keep safe.
3. TWRP is no longer recommended, use OxygenOS modified recovery or other ROM's recovery instead.
4. Flash/Root has huge risks, all operations need to be careful.
OnePlus 8 - LPDDR4x
OnePlus 8 Pro - LPDDR5
OnePlus 8T - LPDDR4x/LPDDR5
OnePlus 9R - LPDDR4x/LPDDR5

Thank you

Looks as if I need to just bite the bullet and roll back to 11 until 12 gets sorted. I won't hold my breath though with the rollout of the new "flagship" I doubt fixing 12 is a high priority.

Holy ****...
These are the images of IN2025_11_C_OTA_1100
Code:
abl.img
aop.img
bluetooth.img
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dsp.img
dtbo.img
featenabler.img
hyp.img
imagefv.img
keymaster.img
logo.img
mdm_oem_stanvbk.img
modem.img
multiimgoem.img
my_bigball.img
my_carrier.img
my_company.img
my_engineering.img
my_heytap.img
my_manifest.img
my_preload.img
my_product.img
my_region.img
my_stock.img
odm.img
product.img
qupfw.img
recovery.img
spunvm.img
storsec.img
system.img
system_ext.img
tz.img
uefisecapp.img
vbmeta.img
vbmeta_system.img
vendor.img
xbl.img
xbl_config.img
xbl_config_lp5.img
xbl_lp5.img
And these are the images of 11.0.11.11
Code:
abl.img
aop.img
bluetooth.img
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dsp.img
dtbo.img
featenabler.img
hyp.img
imagefv.img
keymaster.img
logo.img
mdm_oem_stanvbk.img
modem.img
multiimgoem.img
odm.img
product.img
qupfw.img
recovery.img
reserve.img
spunvm.img
storsec.img
system.img
system_ext.img
tz.img
uefisecapp.img
vbmeta.img
vbmeta_system.img
vendor.img
xbl.img
xbl_config.img
Usually i use this script after changing a rom and after using MSM tool.
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot fastboot
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
fastboot reboot-bootloader
If i would have used this with OOS12 i would have bricked my phone on both slots instantly.....
Im so glad that i was sceptical because OOS12 had more .img files compared to OOS11 and i did not use the script.
People need to know this...
Am i right that as long as we stay on OOS11 and dont use anything from OOS12 we are good to go like before?

FYI. This is what I did to kill my phone, link below
"Warning" Total Brick After Flashing Android 12 Beta
My phone is totally bricked, and it will not respond to anything, a totally black screen, after flashing Android 12 Beta using Fastboot. I was on A12 Beta, I hated it, I wanted to flash AOSP, it did not work, so I decided to flash OOS 11 from...
forum.xda-developers.com

ProfEngr said:
Looks as if I need to just bite the bullet and roll back to 11 until 12 gets sorted. I won't hold my breath though with the rollout of the new "flagship" I doubt fixing 12 is a high priority.
Click to expand...
Click to collapse
Don't go to 12, it's LAME, Stay on 11, might even consider Samsung over OOS12

Hi, i wanted twrp on my oneplus 8 pro IN2021 India and now i can't exit fastboot mode... when i press recovery mode then it boot into fastboot mode again.. and when i boot other rom's it stay the same (sorry bad english i am dutch lol)

Niekdeg said:
Hi, i wanted twrp on my oneplus 8 pro IN2021 India and now i can't exit fastboot mode... when i press recovery mode then it boot into fastboot mode again.. and when i boot other rom's it stay the same (sorry bad english i am dutch lol)
Click to expand...
Click to collapse
Are you on Android 12 or 11?

nkhater said:
Are you on Android 12 or 11?
Click to expand...
Click to collapse
android 12

Niekdeg said:
android 12
Click to expand...
Click to collapse
Dude, be very careful, any wrong move you can lose your phone. I am not sure if MSMTool can help take you back to OOS 11.
download this https://androidfilehost.com/?fid=2188818919693750622
from here:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
have you ever used MSMTool?

Niekdeg said:
android 12
Click to expand...
Click to collapse
Twrp is not ready for OOS 12. Next time you have a TWRP question, you should ask in the appropriate thread, and there's really no need to ask in multiple threads as you did. Keep threads on topic.

nkhater said:
Dude, be very careful, any wrong move you can lose your phone. I am not sure if MSMTool can help take you back to OOS 11.
download this https://androidfilehost.com/?fid=2188818919693750622
from here:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
have you ever used MSMTool?
Click to expand...
Click to collapse
i have that but my device isn't there... i have install the driver but noting..

FreshlyBaked 420 said:
Twrp is not ready for OOS 12. Next time you have a TWRP question, you should ask in the appropriate thread, and there's really no need to ask in multiple threads as you did. Keep threads on topic.
Click to expand...
Click to collapse
okay i do next time, i don't want this again.
but i flash roms all day but noting help and try other recovery image but still the same

Niekdeg said:
okay i do next time, i don't want this again.
but i flash roms all day but noting help and try other recovery image but still the same
Click to expand...
Click to collapse
yes it is
IN11DA tools (indian firmware):
ANDROID 11:
OOS 11.0
OOS 11.0.1.1
OOS 11.0.2.2
OOS 11.0.3.3
OOS 11.0.4.4

nkhater said:
yes it is
IN11DA tools (indian firmware):
ANDROID 11:
OOS 11.0
OOS 11.0.1.1
OOS 11.0.2.2
OOS 11.0.3.3
OOS 11.0.4.4
Click to expand...
Click to collapse
thank you, so i try them al, so just flash boot.img only or ? i don't want lose my phone so

Niekdeg said:
thank you, so i try them al, so just flash boot.img only or ? i don't want lose my phone so
Click to expand...
Click to collapse
This is the MSMTool, there is no boot,img here, boot int EDL mode and restore your phone, watch couple of video on how to use MSMTool

nkhater said:
This is the MSMTool, there is no boot,img here, boot int EDL mode and restore your phone, watch couple of video on how to use MSMTool
Click to expand...
Click to collapse
here

nkhater said:
This is the MSMTool, there is no boot,img here, boot int EDL mode and restore your phone, watch couple of video on how to use MSMTool
Click to expand...
Click to collapse
i do but problem is my phone don't boot to edl mode