Database Info

[Q] How to unbrick xt1040 (failed downgrade)

Hi everyone
(Sorry mi English, I want to be the more clear possible, I'll be gratefull if answers are equal clear , please)
My actual escenario:
Moto G LTE xt1040 in fastboot 41.16(*), no ROM stock, no custom ROM, the only thing I can do is flash TWRP and it works, but in TWRP I can't flash anything, because I think my partitions are corrupted or gone, If I try to flash CM12 I get an this error :
Code:
E:unable to mount '/data'
E:unable to mount '/cache'
E:unable to mount '/system'
...done
E:unable to mount storage
By the other way If I try to flash stock roms like 4.4.3 or 4.4.4 , the command :
Code:
mfastboot flash partition gpt.bin
Send me the error:
(bootloader) Preflash validation failed FAILED (remote failure)
Click to expand...
Click to collapse
Ok, now where I was :
My xt1040 has 4.4.4 stock Latinoamerica, then I unlocked the bootloader, then flash TWRP, then go to CM11, and then to CM12.1 (5.1) ,
I was using CM12.1 for two or three weeks, everything works fine, this week Motorola release the official 5.1 rom for this terminal, and the way to get this official rom was downgrade to 4.4.3, then update to 4.4.4 by OTA, and then flash the 5.1 Rom through stock recovery.
The problem begins when I try to downgrade to 4.4.3, I read the tutorials, download the right ROM, open fastboot and begin to write the commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
The think is that the first command : mfastboot flash partition gpt.bin sends me the error previously mentioned.
What I did?? I found a gptSTOCK.bin file in other forum, that supossed to be right for the downgrade, I flashed it by fastboot, now the command works fine, I can complete all the commands without error, but the phone restarts and freezes in WARNING BOOTLOADER UNLOCKED screen.
I try to flash TWRP and it works, I can enter recovery but can't flash anything by the UNMOUNT error. Seems like my internal SD is not partitioned correctly or corrupted.
At this point I want to know what makes this gpt.bin file and I don't wanna flash, flash, flash without not know what I'm doing, May be my xt1040 was bricked, I don't know, I think than while fastboot and recovery works, must to be any escape to this situation.
Please If any can help me, I see several people has similar problema with the gpt.bin and unmounted partitions.
I try to do with 4.4.3 rom and 4.4.4 without results.
My problem is to MOUNT the disc partitions (data, system, cache) , I think with that I can flash cm12 or another custom ROM.
Thanks
Martin

Hi there!
I have the same problem since February... Mi Moto G XT1040 still bricekd until now.
Yesterday I tried to revive it again, but I couldn't. I'll still trying to taking it back to life again. I'll stay in touch with you and if you can revive your phone, notify me, please!
Regards!
---------------------------------------------------------------------------------------------------------
Hola ahí!
Tengo el mismo problema desde Febrero... Mi Moto G XT1040 sigue brikeado hasta ahora.
Ayer trate de revivirlo de nuevo, pero no pude. Voy a seguir tratando de traerlo a la vida de nuevo. Me mantengo en contacto con vos y si podes revivirlo, por favor avisame!
Saludos!

Hey man! I just relive it a few minutes ago! It's perefectly running Android Lollipop 5.1 (AOSP)... The main problem there is when it try to mount "/data", "/system" and "/cache", but I solve it and the phone start like if nothing happened.
I'll make a tutorial, right now I cant, but stay quiet 'couse I already find the solution to the problem!
----------------------------------------------------------------------------
Hey! Acabo de revivirlo hace apenas unos minutos! Esta corriendo perfectamente Android Lollipop 5.1 (AOSP)... El problema principal era cuando trataba de montar "/data", "/system" y "/cache", pero lo solucione y el telefono arranco como si nada hubiera pasado.
Ya voy a hacer un tutorial, ahora mismo no puedo, pero quedate tranquilo que ya le encontre la vuelta al problema!

it works? funcionó?
iyurcic95 said:
Hey man! I just relive it a few minutes ago! It's perefectly running Android Lollipop 5.1 (AOSP)... The main problem there is when it try to mount "/data", "/system" and "/cache", but I solve it and the phone start like if nothing happened.
I'll make a tutorial, right now I cant, but stay quiet 'couse I already find the solution to the problem!
----------------------------------------------------------------------------
Hey! Acabo de revivirlo hace apenas unos minutos! Esta corriendo perfectamente Android Lollipop 5.1 (AOSP)... El problema principal era cuando trataba de montar "/data", "/system" y "/cache", pero lo solucione y el telefono arranco como si nada hubiera pasado.
Ya voy a hacer un tutorial, ahora mismo no puedo, pero quedate tranquilo que ya le encontre la vuelta al problema!
Click to expand...
Click to collapse
Great, how you did? Did you write the tutotial?
------------------------------------------------------------
Genial bro, pero ¿cómo lo hiciste? escribiste el tuto?

Sorry in advance for repeating the question, but this thread is sooooooo loooong ... So here's how I messed up: I had CM12.1 on my xt1039, I downgraded to stock 4.4.4, and then updated to 5.1 (OTA). It worked fine until the battery died and the phone powered off. After that I tried to turn it on, it loaded the fastboot screen for a moment saying sth about partition table and then went blank. I can't get back into fastboot any more. If I plug connect it to my PC and run "lsusb" I can't see anything. Any hope?

G6 U251 Brick

Hola a todos soy de Colombia y me sucede lo siguiente:
Es la primera vez que me llega un Huawei a mis manos con este problema y no se como solucionarlo, se queda en el logo de Huawei Ascend y no pasa de ahí, puedo entrar al Recovery y hacer Wipe cache pero al darle Wipe data se queda en Wiping Data... He tratado con el ADB y me sale "failed (remote command not allowed)" luego de ejecutar cada comando.
¿Como puedo solucionar esto?
Google Traductor:
Hello everyone I am from Colombia and the following happens:
It is the first time I get Huawei my hands with this problem and do not know how to fix it , it stays in the logo of Huawei Ascend and it's not there, I can enter the Recovery and make Wipe cache but give Wipe data stays Wiping Data on ... I have tried with ADB and I get "failed (remote command not allowed ) " after executing each command.
How can i fix this?

make a backup, flash slimstock, if slimstock also doesn't boot force update to your original update (download original firmware, format sd, place update.app or update.zip on sd like this: SD:/dload/update.zip or SD:/HwOUC/update.app)

Flash
How to flash SlimStock for Huawei Ascend G6 u-10? Do you have some tutorial?

http://forum.xda-developers.com/asc...m-slimstock-kk-g6-u10-based-b360-pre-t3280631
Slimstock works only if you have an unlocked bootloader, if you don't have that you can try my #1 comments (download update.zip / update.app)

[SOLVED] Cannot flash TWRP: partition table doesn't exist

UPDATE: I was trying to flash this port of TWRP to the recovery partition, but it turns out, it needs to be flashed to the boot, not the recovery partition. So I did that, and it's working now. This also solved the root issue I was trying to solve by installing Cyanogenmod, which is that I cannot mount /system writable. So, issue solved, ignore this post.
I want to install Cyanogenmod. I know that without a recovery this is a very bad idea, so I want to install TWRP. But I get this:
Code:
[email protected]$ sudo fastboot flash recovery boot.img
sending 'recovery' (19144 KB)...
OKAY [ 0.629s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.633s
What does this mean and how do I fix it?
The ROM is the stock ROM with Android 4.4.4, I have no custom recovery, USB debugging is enabled, my bootloader is unlocked, and I am rooted. It may be important to note that I cannot mount /system writable in the current situation; which is the reason why I want to install Cyanogenmod.

Please tell me what you did.i have the same issue

Rajatc said:
Please tell me what you did.i have the same issue
Click to expand...
Click to collapse
If you read the update, you would have known, but I'll repeat it anyway: I had this problem because I was flashing to the recovery partition. This sounds correct, but you actually need to flash it to the boot partition. (Or at least, my port had me do that. Please make sure you are using the same port as mine. I have a link to it in the OP.) So instead of doing this:
Code:
sudo fastboot flash recovery boot.img
You need to do this:
Code:
sudo fastboot flash boot boot.img
Again, the tutorial I was following stated that you had to flash it to recovery, but the port I was using, which is for the Sony Xperia E3 and not for any other device, needs to be flashed to the boot partition.

Stock kernel
Can you please provide me stocks Kernel if you have taken backup.Thankyou

If you flashed the wrong kernel, and your phone doesn't boot anymore, you can still try to flash the correct kernel. I won't provide you with the stock kernel because A) I haven't made a backup before that, and B) I don't think I'm allowed to do that by the EULA. If all else fails, you might have luck with Sony's Emma, but I don't guarantee it. I've been told that it will reject phones with any non-stock kernel, but I haven't tried it.

Are you using nitrogen.My nitrogen rom lags a bit.Do you have any solution
---------- Post added at 03:24 PM ---------- Previous post was at 03:03 PM ----------
Are you using nitrogen .My nitrogen lags a bit.Do you have any solution

No problem to not boot
foxite said:
If you flashed the wrong kernel, and your phone doesn't boot anymore, you can still try to flash the correct kernel. I won't provide you with the stock kernel because A) I haven't made a backup before that, and B) I don't think I'm allowed to do that by the EULA. If all else fails, you might have luck with Sony's Emma, but I don't guarantee it. I've been told that it will reject phones with any non-stock kernel, but I haven't tried it.
Click to expand...
Click to collapse
No se puede instalar equivocamente el kernel, ya que el paquete ADB no te permite instalar el gestor de arranque (boot) en una particion de recuperación (recovery)
Code:
FAILED <remote: image is not a boot image>
Aun asi, yo aun tengo el problema en mi Sony Xperia T3, donde la partición de recuepacion menciona que no existe :crying: :crying:

zature said:
No se puede instalar equivocamente el kernel, ya que el paquete ADB no te permite instalar el gestor de arranque (boot) en una particion de recuperación (recovery)
Aun asi, yo aun tengo el problema en mi Sony Xperia T3, donde la partición de recuepacion menciona que no existe :crying: :crying:
Click to expand...
Click to collapse
??????
This is an English forum. Speak English.

foxite said:
UPDATE: I was trying to flash this port of TWRP to the recovery partition, but it turns out, it needs to be flashed to the boot, not the recovery partition. So I did that, and it's working now. This also solved the root issue I was trying to solve by installing Cyanogenmod, which is that I cannot mount /system writable. So, issue solved, ignore this post.
I want to install Cyanogenmod. I know that without a recovery this is a very bad idea, so I want to install TWRP. But I get this:
Code:
[email protected]$ sudo fastboot flash recovery boot.img
sending 'recovery' (19144 KB)...
OKAY [ 0.629s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.633s
What does this mean and how do I fix it?
The ROM is the stock ROM with Android 4.4.4, I have no custom recovery, USB debugging is enabled, my bootloader is unlocked, and I am rooted. It may be important to note that I cannot mount /system writable in the current situation; which is the reason why I want to install Cyanogenmod.
Click to expand...
Click to collapse
how to fix it please:crying:

otakuyasser1 said:
how to fix it please:crying:
Click to expand...
Click to collapse
Please read the existing replies before asking for another solution.

foxite said:
If you read the update, you would have known, but I'll repeat it anyway: I had this problem because I was flashing to the recovery partition. This sounds correct, but you actually need to flash it to the boot partition. (Or at least, my port had me do that. Please make sure you are using the same port as mine. I have a link to it in the OP.) So instead of doing this:
Code:
sudo fastboot flash recovery boot.img
You need to do this:
Code:
sudo fastboot flash boot boot.img
Again, the tutorial I was following stated that you had to flash it to recovery, but the port I was using, which is for the Sony Xperia E3 and not for any other device, needs to be flashed to the boot partition.
Click to expand...
Click to collapse
Thanks, i doing this and the problem sovled.
Code:
sudo fastboot flash boot boot.img

warpaper said:
Thanks, i doing this and the problem sovled.
Code:
sudo fastboot flash boot boot.img
Click to expand...
Click to collapse
Bootloop.

Cannot flash recovery in fastboot

Hi,
my device is rooted, bootloader unlocked. But I am currently on stock recovery. MHA-L09 8.0.0.321 (C432log) is my current EMUI Rom (Android O beta) and I want to install ne released version 361.
To do so, I need TWRP recovery.
So I wanted to do fastboot flash recovery ... like I always did and what always worked.
But now it didnt. I got always "Failed :Command not allowed". I had a check on google and yes, USB Debugging is turned on, as well as OEM-Unlock.
Fastboot showed me this, just to be sure:
PHONE Unlocked
FRP Unlock
However, I made fastboot oem unlock again and unlocked bootloader again.
Then, with enabled OEM Unloock and USB-Debugging I tried again fastboot flash recovery command, but now I get another error:
target reported max download size of 471859200 bytes
sending 'recovery' (26982 KB)...
OKAY [ 0.579s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.600s
So I checked on google again and found that thread, same error message, same device (MAte 9): https://forum.xda-developers.com/mate-9/help/failed-remote-partition-length-error-t3686583
But the linked TWRP did not worked for me, still getting the same error.
Does anyone have an idea what I could do? Never hat such issues when trying to flash recovery image
Thanks!

OK, I managed it by myself, haha.
For anyone else with same issue.
Since Oreo: Partition names have changed.
Use this command: fastboot flash recovery_ramdisk RECOVERY.img
"recovery" changed to "recovery_ramdisk" now.
Mod can close this thread.

tobyffm said:
OK, I managed it by myself, haha.
For anyone else with same issue.
Since Oreo: Partition names have changed.
Use this command: fastboot flash recovery_ramdisk RECOVERY.img
"recovery" changed to "recovery_ramdisk" now.
Mod can close this thread.
Click to expand...
Click to collapse
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
Just in case you need to restore stock boot you need to flash ramdisk/kernel

ante0 said:
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
Just in case you need to restore stock boot you need to flash ramdisk/kernel
Click to expand...
Click to collapse
@ ANTE0 : could you please let us know the complete list of command lines if we wanted to flash the Oreo entiere data extracted files ?...
hope to hear from you, thanks for sharing knowledge

Oh thx mate, that was the solve for my problem :good::good:

hi ante0, i have US version bla a09 8.0.0.104(c567), i am trying to flash back to stock and was able to download the ota update 8.0.0.109 and extracted update.app and have several .img and .header files, so if i want to flash this update what do i need to do, thank you.

FuM8 said:
@ ANTE0 : could you please let us know the complete list of command lines if we wanted to flash the Oreo entiere data extracted files ?...
hope to hear from you, thanks for sharing knowledge
Click to expand...
Click to collapse
@ante0

tobyffm said:
OK, I managed it by myself, haha.
For anyone else with same issue.
Since Oreo: Partition names have changed.
Use this command: fastboot flash recovery_ramdisk RECOVERY.img
"recovery" changed to "recovery_ramdisk" now.
Mod can close this thread.
Click to expand...
Click to collapse
Great. Trying this now.
Although how do I flash the system and make it boot?

I need help with this method
ante0 said:
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
Just in case you need to restore stock boot you need to flash ramdisk/kernel
Click to expand...
Click to collapse
Hi i need help with this method, i can flash a new version oreo for e.g. i have 368 and stuck Error Mode 11 and 2, if extract all files from update.app oreo 370 and flash one per one my phone is booth again ? because try to flash with the version 368 and doesnt work maybe i forgot flash a file.
thks

I stuck with my Mate 9 Error mode numbers 11 and 2
hybrid09 said:
Hi i need help with this method, i can flash a new version oreo for e.g. i have 368 and stuck Error Mode 11 and 2, if extract all files from update.app oreo 370 and flash one per one my phone is booth again ? because try to flash with the version 368 and doesnt work maybe i forgot flash a file.
thks
Click to expand...
Click to collapse
cher81 said:
Great. Trying this now.
Although how do I flash the system and make it boot?
Click to expand...
Click to collapse
I would like to tell you my problem, I have a Mate 9 MHA-L09C605B111 which I did a rebrand a while ago and I'm with CUST 432 and installed the version of Oreo 8.0.0.368, a few weeks ago I received the update 369 via OTA. It was interesting to try; the problem is that I had open bootloader, TWRP Pretorian 3.2.0 and Root, take a terrible decision to do a relock of the bootloader.
After several attempts and letting the battery drain I could enter Fastboot mode, I have the FRP unlocked and I could unlock the bootloader again, the problem is that I can not enter either the TWRP, or to recovery mode, try flashing again the same TWRP I had installed it well but still when I want to enter after passing the Huawei logo it remains on the white screen of ERROR MODE, Func NO: 11 (recovery image) Error NO: (image Failed!) Reading other forums and looking I have been told a lot by Internet that it is necessary to make the Dload method try it but it did not work, I understand that it does not work in this model but I still try it.
I also did a flash with all the files as I found in XDA
"When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img "
I'm still stuck on the same screen with error 11 and 2 I made the flash of the recovery that I used when I put version 368 are two MHA_RECOVERY_NoCheck.img and MHA_RECOVERY2_NoCheck.img both give Failed using the command Fastboot flash recovery_ramdisk RECOVERY_XXXX with both the same without using the _ramdisk command is equal I'm still stuck in the same state.
Does anyone have an idea that another method I can try?
I will thank you very much.
You can flash all * .img through ADB and in this case there is a specific order to do it, check several threads but I did not get an answer and search but I could not find anything, it is worth noting that when I flash files I mentioned before all OKAY but on power up it goes back to error 11 and 2 I have been told that it is a partition problem but I could not find something to recover them, there is some method that is missing or maybe an error in the steps I am doing ? I still can not access the TWRP but I can access without problems by ADB.

hybrid09 said:
I would like to tell you my problem, I have a Mate 9 MHA-L09C605B111 which I did a rebrand a while ago and I'm with CUST 432 and installed the version of Oreo 8.0.0.368, a few weeks ago I received the update 369 via OTA. It was interesting to try; the problem is that I had open bootloader, TWRP Pretorian 3.2.0 and Root, take a terrible decision to do a relock of the bootloader.
After several attempts and letting the battery drain I could enter Fastboot mode, I have the FRP unlocked and I could unlock the bootloader again, the problem is that I can not enter either the TWRP, or to recovery mode, try flashing again the same TWRP I had installed it well but still when I want to enter after passing the Huawei logo it remains on the white screen of ERROR MODE, Func NO: 11 (recovery image) Error NO: (image Failed!) Reading other forums and looking I have been told a lot by Internet that it is necessary to make the Dload method try it but it did not work, I understand that it does not work in this model but I still try it.
I also did a flash with all the files as I found in XDA
"When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img "
I'm still stuck on the same screen with error 11 and 2 I made the flash of the recovery that I used when I put version 368 are two MHA_RECOVERY_NoCheck.img and MHA_RECOVERY2_NoCheck.img both give Failed using the command Fastboot flash recovery_ramdisk RECOVERY_XXXX with both the same without using the _ramdisk command is equal I'm still stuck in the same state.
Does anyone have an idea that another method I can try?
I will thank you very much.
You can flash all * .img through ADB and in this case there is a specific order to do it, check several threads but I did not get an answer and search but I could not find anything, it is worth noting that when I flash files I mentioned before all OKAY but on power up it goes back to error 11 and 2 I have been told that it is a partition problem but I could not find something to recover them, there is some method that is missing or maybe an error in the steps I am doing ? I still can not access the TWRP but I can access without problems by ADB.
Click to expand...
Click to collapse
I am exactly in your same situation. Were you able to find a solution?

Solved
cococchio said:
I am exactly in your same situation. Were you able to find a solution?
Click to expand...
Click to collapse
Hola si pude arreglar el celular de la siguiente forma, usando la herramienta DC Phoenix te recomiendo comprar el pack de 21 euros,
Pasos para poder comprar los créditos en DC Phoenix:
1. Crea una cuenta tu usuario y contraseña.
2. Comprate el pack de 21 euros
3. Te llegara por mail una confirmación de compra de forma casi inmediata con una nueva contraseña con esta nueva contraseña y el mismo usuario que creaste en la pagina de DC Phoenix ingresas al programa.
Pasos cuando ya tengas los créditos del DC Phoenix:
1. Baja la ROM oficial que tenias instalada en el celular antes de que tuvieses ese error por ejemplo la 368 de oreo que fue mi caso, baje el archivo solo el update.zip
2. Descomprimí el archivo Update.app que esta dentro del zip que bajaste en el paso 1.
3. Dentro del programa DC Phoenix en la sección de examinar buscas el archivo Update.app que descomprimiste y lo seleccionas.
4. Pone tu teléfono en modo Fastboot tener en cuenta que debes tener el Bootloader tanto como el FRP desbloqueados.
5. Pones start y dejas que haga todo el proceso.
6. Una vez que finalice te va a quedar en la pantalla de Fastboot lo reinicias a mano
7. Entrara en modo Recovery de fabrica, haces un erase cache y luego un wipe data partition.
8. Se va a reiniciar y hará el Wipe Data partition.
9. Lo reinicias nuevamente y conecta el celular al cargador ya que la batería esta totalmente vacía.
10. Ya inicia el sistema operativo de forma normal y lo configuras a tu gusto.
Cualquier cosa avísame.
Saludos

hybrid09 said:
Hola si pude arreglar el celular de la siguiente forma, usando la herramienta DC Phoenix te recomiendo comprar el pack de 21 euros,
Pasos para poder comprar los créditos en DC Phoenix:
1. Crea una cuenta tu usuario y contraseña.
2. Comprate el pack de 21 euros
3. Te llegara por mail una confirmación de compra de forma casi inmediata con una nueva contraseña con esta nueva contraseña y el mismo usuario que creaste en la pagina de DC Phoenix ingresas al programa.
Pasos cuando ya tengas los créditos del DC Phoenix:
1. Baja la ROM oficial que tenias instalada en el celular antes de que tuvieses ese error por ejemplo la 368 de oreo que fue mi caso, baje el archivo solo el update.zip
2. Descomprimí el archivo Update.app que esta dentro del zip que bajaste en el paso 1.
3. Dentro del programa DC Phoenix en la sección de examinar buscas el archivo Update.app que descomprimiste y lo seleccionas.
4. Pone tu teléfono en modo Fastboot tener en cuenta que debes tener el Bootloader tanto como el FRP desbloqueados.
5. Pones start y dejas que haga todo el proceso.
6. Una vez que finalice te va a quedar en la pantalla de Fastboot lo reinicias a mano
7. Entrara en modo Recovery de fabrica, haces un erase cache y luego un wipe data partition.
8. Se va a reiniciar y hará el Wipe Data partition.
9. Lo reinicias nuevamente y conecta el celular al cargador ya que la batería esta totalmente vacía.
10. Ya inicia el sistema operativo de forma normal y lo configuras a tu gusto.
Cualquier cosa avísame.
Saludos
Click to expand...
Click to collapse
I'm sorry to bother you and any of you guys but I'm in a similar situation than OP and I have some questions.
DC Phoenix isn't actually needed, right? All the flashing could have been done with fastboot commands, isn't it? Or there was another reason for why you needed that software? I think I can access fastboot so I wont need that, am I right?
I'm asking because I've never dealt with this update.app package and upon examining its contents I saw that all the images have different names so flashing them should be relatively easy?
There are some imgs that I don't know if it should be flashed, like reserved[1 to 10].img, should I flash this with a command like: fastboot flash reserved1 reserved1.img?
Sorry if this is confusing because I'm not talking about this phone but the P8 Lite 2017, partitions with the name reserved does exists?

Same problem here.
On the P8 Lite 2017 - like @Jhon_Locke
Block in bootloop, TWRP or eRecovery don't work, I only have access to the fastboot.
Flash a new TWRP or Recovery don't work too
If someone find a solution

naced said:
Same problem here.
On the P8 Lite 2017 - like @Jhon_Locke
Block in bootloop, TWRP or eRecovery don't work, I only have access to the fastboot.
Flash a new TWRP or Recovery don't work too
If someone find a solution
Click to expand...
Click to collapse
I've got the same issue like you. Did you find any solution?

AP fastboot flash Mode (not secure)

I have a problem with my moto g7 power xt1955-2, I cannot unlock the bootloader because when entering Fastboot mode this appears in red AP fastboot flash Mode (not secure) and below where it should say oem_locked it says (engineering)

Héctor.M1999 said:
Tengo un problema con mi moto g7 power xt1955-2, no puedo desbloquear el bootloader debido a que al entrar en modo Fastboot sale esto en rojo AP fastboot flash Mode (not secure) y abajo donde debe decir oem_locked dice (engineering)
Click to expand...
Click to collapse
Please use English on XDA
I have a problem with my moto g7 power xt1955-2, I cannot unlock the bootloader because when entering Fastboot mode this appears in red AP fastboot flash Mode (not secure) and below where it should say oem_locked it says (engineering)
Click to expand...
Click to collapse
engineering is unlocked

Héctor.M1999 said:
I have a problem with my moto g7 power xt1955-2, I cannot unlock the bootloader because when entering Fastboot mode this appears in red AP fastboot flash Mode (not secure) and below where it should say oem_locked it says (engineering)
Click to expand...
Click to collapse
Help!

Héctor.M1999 said:
Help!
Click to expand...
Click to collapse
It's already unlocked