[GUIDE] How to restore stock firmware

[chico_salvador]

Didn't work.

 

[Repepino]

I have this issue

PS C:\Users\paco_\Desktop\Moto z rom> fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (142 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.178s
PS C:\Users\paco_\Desktop\Moto z rom>

Can you help me? pls

 

[Sb_SharK]

IMEI 0, No signal, panic!

I followed all steps. What can I do?

Same happened to me! If you found a solution please reply!?

 

[techlogik]

Coworker had the buttons stop working on the phone. ADB reboot, phone went to bootloader, buttons still didn't work.

Now, fastboot devices waiting for device screen. No commands work. Think phone just is toast. Told her to take it back to the store and see what they say, phone must be toast if fastboot and buttons won't work.

Then, after disconnecting from the bootloader/usb cable, phone just shut off. Plug the phone in, shows charging symbol..but buttons still don't work. Guess it is dead.

 

[KOOLjeet]

I tried restoring using your guide.

restored from 8.1 to 7.1.1, successfully
everything worked
but i lost the signals i.e IMEI is 0 now

I have TWRP backup of my 8.1 official system, restoring the backup solves my problem.

please help, how to restore without losing IMEI no. , should I skip flashing any file from the stock firmware through ADB.

 

[tag68]

...
please help, how to restore without losing IMEI no. ,

I have no idea how to revert the changes Oreo does to the efs partition. Maybe restoring a backup of the efs partition you did before installing Oreo the first time would help. But I can give you a warning: The things you try have a high risk of causing hard brick. I hope you are aware of that danger?

 

[KOOLjeet]

I have no idea how to revert the changes Oreo does to the efs partition. Maybe restoring a backup of the efs partition you did before installing Oreo the first time would help. But I can give you a warning: The things you try have a high risk of causing hard brick. I hope you are aware of that danger?

I dont know what danger you are awaring about here? please elaborate what could possibly go wrong, beacause restroing the backup solves all the problems.
I read somewhere that i should skip executing the following commands, this will not alter my IMEI data, maybe i should give it a try. Do you have any idea about it?

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier

 

[tag68]

I dont know what danger you are awaring about here? please elaborate what could possibly go wrong, beacause restroing the backup solves all the problems.

In case of hard brick it is impossible to flash. How do you want to restore the backup if you are not able to run twrp? Just have a look at the corresponding threads about hard brick, Oreo versus Nougat etc.

I read somewhere that i should skip executing the following commands, this will not alter my IMEI data, ...

Why do you think that should help?

In regards to this question my advice is that you wait with flashing until you learned more about the basics of Android. But better flash than doing OTA. Be glad while your mobile is working fine.

Your IMEI data has Oreo structure. Nougat won't be able to read it. I doubt there is a way back. That's the hard brick risk: if the installer of Oreo bootloader tries to convert efs (which contains IMEI) again and is not aware that it already has Oreo structure, you will probably get a hard brick.

 

[KOOLjeet]

In regards to this question my advice is that you wait with flashing until you learned more about the basics of Android. But better flash than doing OTA. Be glad while your mobile is working fine.

Your IMEI data has Oreo structure. Nougat won't be able to read it. I doubt there is a way back. That's the hard brick risk: if the installer of Oreo bootloader tries to convert efs (which contains IMEI) again and is not aware that it already has Oreo structure, you will probably get a hard brick.

so is there any way around to restore to nougat without losing IMEI.

 

[bryanisimo]

Worked!

I try it with a Moto Z2 Play just downloading "albus" version, I just uploaded to Android 8.0, thank you so much!

 

[silgreyn]

Hi, i have a Moto Z, each time i want to send the commands via adb, i get the feedback from the phone that '' installation aborted'' I am trying to flash the stock rom. After a number of research, i came to see that there is rooting process on the other hand, but there am not ready to brick the phone. The bootloader is unlocked already and the usb debugging is turned on.

Now my question is; is there any way to deal with that ''installation aborted'' apart from rooting the phone?
Is it a must that i need to root the phone to flash stock room, of course not to overlook the ''installation aborted issue?
Help please.

 

[tag68]

Is it a must that i need to root the phone to flash stock room, of course not to overlook the ''installation aborted issue?

It seems you do not understand what root means. Root is the possibility to execute "su" to get extended rights (log in as superuser). This means you have a ROM installed. If your ROM is not working, it is not possible to successfully root the phone.

Which part of the installation aborts? Which action fails? Where did you get the ROM from? Is it fine? Do you know of any hardware problems your phone has? Is your device recognized via USB cable, or is the installation aborted because no device is recognized?

The Moto Z has (like some similar Motos) a higher probability of getting bricked than other devices: if you downgrade the ROM to an earlier version, where the bootloader does not (fully, correctly) gets downgraded and the next try to update will cause the brick. Try to root usually is not that dangerous even if it fails - while a successful flash of ROM can cause a brick after OTA. According to your questions, you may want to look if you can ask some friend who has more knowledge about computer and Android to help you.