Database Develop

hd atrix att help not to flash

Hello I could help .. I have a problem with RS flash lite. I get an error in the RS lite, this error: FLAILET 15/21 FASTH BOOT "BOOT.IMG"
and the phone says this: Preflash FAILET VALIDATION FOR BOOT
help .. I have this fireware MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-AHD MX.xml.zip q is the only pole came 15/21

ANGELOCHITE said:
Hello I could help .. I have a problem with RS flash lite. I get an error in the RS lite, this error: FLAILET 15/21 FASTH BOOT "BOOT.IMG"
and the phone says this: Preflash FAILET VALIDATION FOR BOOT
help .. I have this fireware MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-AHD MX.xml.zip q is the only pole came 15/21
Click to expand...
Click to collapse
Do you have an unlocked bootloader? Do you have safestrap or cwm installed? Rooted?

1) Make sure you have an unlocked bootloader.
2) Replace the .xml file inside of the .zip you are trying to flash with this one: https://www.box.com/s/num1eshkf0c2or2h4160
If RSD Lite will not work after confirming these 2 things have been done, then you will have to consult this guide to do it manually: http://forum.xda-developers.com/showthread.php?t=2259661
All you need to do is go into command prompt and redirect to the folder that contains your zip using the "cd C:/pathtofile" command and enter the proper command lines one at a time for flashing. Do this while in fastboot and make sure your xml file is properly modified.

audit13 said:
Do you have an unlocked bootloader? Do you have safestrap or cwm installed? Rooted?
Click to expand...
Click to collapse
noc como saber si lo tengo bloqueado.. como se eso y como lo desbloqueo.. y no tengo nada instalado xq no prende el cel solo se queda en la pantalla de FASTBOOT MODE S

ANGELOCHITE said:
noc como saber si lo tengo bloqueado.. como se eso y como lo desbloqueo.. y no tengo nada instalado xq no prende el cel solo se queda en la pantalla de FASTBOOT MODE S
Click to expand...
Click to collapse
In english please thats the only way i can help

I used Google Translate and got this:
how to tell if I have it locked .. as that and as unlocking .. I have not installed anything it not turn the cell just stays on the screen of FASTBOOT MODE S.
Did you ever use a program called Myth Tools? Motochopper?

[Tutorial] How to Flash Different Official Firmware

Para la guia en español, ve al final del post y haz click en el spoiler para verla.
THIS IS NOT FOR DROID TURBO I REPEAT DONT DO THIS FOR DROID TURBO
Hello guys, given the unlocked bootloader nature of our moto maxx's and moto turbos
and that some of us like to try and test firmware from different countries, i present you:
How to Flash Different Official Firmware on Moto Maxx/Turbo
Lets say you have the mexico, puerto rico or brasil firmware and want to try India Firmware
you have to get this on your PC:
Requisites:
RSD LITE
Android Studio or Minimal ADB and Fasboot (i personally recommend Minimal Adb and Fastboot because thats all we gonna need and its lighter than Android Studio 2 Mb vs 800Mb)
Official Firmware you want to flash
mFastboot (motorola Fastboot) i uploaded it for you: https://mega.co.nz/#!MVtz1DLb!CZTh_-wCl-qyta4Q0yZuPk_TB6Wq7Z4zElk6eArXrXk
RSD LITE only Works if you are going back to your Original Firmware
Installation:
1.- Install MAaF
Install Minimal ADB and Fastboot
2.- Install mFastboot
Copy the contents of mfastboot.zip and put them on Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot)
Now you have working Fastboot AND mFastboot
3.- Copy Firmware
Copy the contents of your desired firmware to Minimal ADB and Fastboot Folder like this:
Now you are ready to flash!
First turn off your device and Put it on fastboot mode (Power and volume down for 2 seconds with your phone off)
4.- Get Detected
type
Code:
fastboot devices
on minimal adb to see if your pc detects your phone on fastboot mode
if you get some numbers and letters like the picture you are ready to go.
if not, you are missing drivers, looks for Motorola Device Manager
5.- Install
Copy and Paste these commands on Minimal ADB and Fastboot:
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
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 system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot erase cache
mfastboot erase userdata
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
and thats all, as easy as copy from here and paste on cmd.
when your phone finishes flashing just press enter to execute mfastboot reboot and you will boot the new firmware.
Tip:
you can remove/skip the line
Code:
mfastboot flash recovery recovery.img
if you want to keep your custom recovery like TWRP of CyanogenRecovery
remember:
Flashing another firmware will erase all your information
i know that you can flash without erasing anything but that causes many many errors and inestability i've seen it a lot of times so i encourage to erase everything every time you flash a different firmware, better start fresh.
FAQ
i have a Moto Maxx/Turbo and i want to flash Verizon (or another Firmware) will it work???
Flashing different quark phones firmware will work and boot, however getting signal its another history, all moto maxx are unlocked and there is no problem with them but if you flash droid turbo firmware on moto maxx you likely wont get any signal, see my thread for [Guide] Droid Turbo & Moto Maxx Carrier and Bootloader Compatibility
Why i can't just flash it using RSD LITE?
Because somehow it detects the firmware you are on, so you can only flash your original firmware
Why did you not include gpt.bin in the flashing???
Because if you were on kitkat, installed brasil or another firmware and take a OTA to lollipop your gpt.bin version will be greater than the one you'll try to flash and it will FAIL TO FLASH, dont worry just skip that line.
Why If i flashed India/Mexico/Brasil Firmware it says the name of my original Firmware???? did it failed??
Motorola Somehow stores in a partition your original firmware name, even if you flash another from another country it will say the name of the original firmware you had, dont worry it doesnt affect anything.
Can i go back to kitkat if i flashed the Mexico or Brasil Lollipop OTA???
Yes you can flash back to kitkat without risk of brick if you flashed the mexican or brasil OTA using the method of this thread.
Where i can get my official firmware???
you can get it in another thread i have: [All Quark][Official] Stock Firmware Moto Maxx Droid Turbo Moto Turbo
Im in mexico or brasil Lollipop how can i get root?
Just boot or flash TWRP and flash Super SU for android 5.0 by chainfire.
Protip: (my view on flashing soak test on locked devices)
DONT YOU EVER EVER EVER FLASH A SOAK TEST IF YOU HAVE LOCKED BOOTLOADER OR DONT WANT TO UNLOCK, GPT.BIN AND SOME OTHER BOOTLOADER FILES WILL BE UPDATED AND WILL FAIL IF YOU TRY TO FLASH BACK TO OLDER VERSIONS YOU'LL HAVE TO WAIT FOR THE FIRMWARE TO GET OFFICIALLY RELEASED AS A FULL (NOT OTA) AND EVEN THAT ITS NOT A GUARANTEE THAT YOU'LL HAVE YOUR PHONE BACK WORKING, BE CAREFUL WHAT YOU DO TO YOUR PHONE, UNLOCKED BOOTLOADER ITS BEST TO TRY FIRMWARE.
this is a Q&A thread, so if you have any questions just post them here!
i took my time to upload and write this guide for you, so...
If this was useful Press Thanks and if you have $1.00 spare on paypal, i can always take it
Click Donate to me below my name
Guia En español, como instalar diferente FIrmware en tu Moto Maxx o Moto Turbo
NO HAGAS ESTO SI TIENES UN DROID TURBO REPITO NO HAGAS ESTO SI TIENES UN DROID TURBO
Hola amigos, teniendo en cuenta que nuestro telefono se puede desbloquear el bootloader
y que a algunos de nosotros nos gusta tener y probar firmware de otros paises les presento:
Como Instalar Otros Firmwares Oficiales en Moto Maxx/Turbo
Digamos que tienes tu moto maxx Mexico, puerto rico o brasil y quisieras probar el firmware de India
Tienes que tener esto en tu PC:
Requisitos:
RSD LITE
Android Studio or Minimal ADB and Fasboot (yo recomiendo Minimal Adb and Fastboot porque es todo lo que vamos a necesitar y es mas pesado que Android Studio 2 Mb vs 800Mb)
El Firmware Oficial que quieres Instalar (se le dice flashear)
mFastboot (motorola Fastboot) Lo subi para que lo descarguen de aqui: https://mega.co.nz/#!MVtz1DLb!CZTh_-wCl-qyta4Q0yZuPk_TB6Wq7Z4zElk6eArXrXk
RSD LITE Nada mas sirve para volver a tu firmware original, no para instalar otros, OJO
Instalacion:
1.- Instala MAaF
Instala Minimal ADB and Fastboot
2.- Install mFastboot
Copia los contenidos de mfastboot.zip y ponlos en la carpeta de Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot)
Es todo lo que se necesita, ya tienes fastboot y mFastboot
3.- Copiar el Firmware
Copia el contenido del firmware que quieres instalar en la carpeta de Minimal ADB and Fastboot así:
Ya estas listo para Flashear!
Primero apaga tu telefono y ponlo en modo fastboot (presiona boton de encendido y volumen para abajo 2 segundos con el telefono apagado)
4.- Que se Detecte el Telefono
Escribe
Code:
fastboot devices
en minimal adb para ver si tu PC detecta el telefono en modo fastboot
si te salen algunos numeros y letras como la foto ya estas listo para flashear.
si no te salen, te faltan drivers, instala el Motorola Device Manager
5.- Instalar
Copia y pega estos comandos en Minimal ADB and Fastboot:
mfastboot flash partition gpt.bin
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
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 system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot erase cache
mfastboot erase userdata
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
y eso es todo, copia de aqui y pega en la consola de comandos
cuando tu telefono termine de flashear solo presiona enter para ejecutar mfastboot reboot y se reiniciara con el nuevo firmware.
Tip:
puedes quitar la linea
Code:
mfastboot flash recovery recovery.img
si te quieres quedar con TWRP Recovery o la que tengas.
Recuerda:
Flashear otra información va a borrar toda tu información
se que se puede flashear sin borrar nada pero eso causa muchos errores e inestabilidad, lo he visto muchas veces, asi que yo recomiendo borrar todo cada vez que flasheas un firmware diferente, siempre es mejor empezar limpio
PREGUNTAS FRECUENTES
si tengo un moto maxx o moto turbo y quiero flashear el firmware de Verizon (o cualquier otro) funcionara?
Mira flashear diferentes firmwares de los moto maxx funcionaran y encenderan, pero tener señal es otra historia, todos los moto maxx estan desbloqueados y no hay problemas en poner otro firmware de otro pais de otro moto maxx pero si instalas el firmware del droid turbo en el moto maxx es probable que no tengas señal, para ver un cuadro de compatibilidad mira mi tema: [Guia] Droid Turbo & Moto Maxx compatibilidad de señal y desbloqueo de firmware
Porque no puedo flashear directo usando RSD LITE?
Porque de alguna forma RSD LITE detecta el firmware que estas o estabas, asi que solo puedes flashear tu firmware original usando rsd lite.
Por que no incluiste la parte gpt.bin en el flasheo???
Porque si estas en kitkat e instalaste brasil u otro firmware y tomaste la OTA para lollipop tu version de gpt.bin es mas nueva que la que intentas flashear y si incluyes esa version, fallara de flashear y te fallara tu telefono., no te preocupes solo borra esa linea.
Si Flashie el firmware de India/Mexico/Brasil sigue diciendo el nombre de mi Firmware original???? fallo??
Motorola de alguna forma guarda en una particion el nombre de tu firmware original, incluso si flasheas otra de otro pais, seguira diciendo el nombre del firmware original que tenias, no te preocupes, no afecta en nada.
Me puedo regresar a kitkat si flashie la OTA de Mexico o Brasil???
Si, puedes usar el método de este tema si te puedes regresar a kitkat sin el riesgo de brickeo si flasheaste la ota de mexico o brasil
Donde puedo sacar el firmware original de mi telefono???
Lo puedes obtener en este tema que tengo: [All Quark][Official] Stock Firmware Moto Maxx Droid Turbo Moto Turbo
Estoy en el firmware de mexico/brasil/india en lollipop, como puedo tener root??
solo inicia el recovery TWRP y descarga e instala Super SU para android 5.0 por chainfire.
tip: (mi punto de vista en flashear un soak test en un telefono con el bootloader bloqueado)
NUNCA NUNCA NUNCA NUNCA FLASHEES UN SOAK TEST SI TIENES EL BOOTLOADER BLOQUEADO O NO QUIERES DESBLOQUEAR EL BOOTLOADER, GPT.BIN Y OTROS ARCHIVOS DEL BOOTLOADER SE ACTUALIZAN Y FALLAN SI TRATAS DE FLASHEAR A VERSIONES MAS VIEJAS, TU TELEFONO SE JODERA Y TENDRAS QUE ESPERAR QUE EL FIRMWARE SALGA OFICIALMENTE COMPLETO (NO OTA) Y AUN ASI NO ES GARANTIA DE QUE TU TELEFONO VUELVA A FUNCIONAR, TEN CUIDADO CON LO QUE LE HACES A TU TELEFONO, ES MEJOR PROBAR FIRMWARE CON EL BOOTLOADER DESBLOQUEADO.
RECUERDA QUE ESTO ES XDA, SI TIENES PREGUNTAS HAZLO EN INGLES EN ESTE TEMA
yo me tome mi tiempo para subir y escribir esta guia para ti, asi que...
Si esto fue util presiona el boton gracias y si tienes $1.00 de sobra en paypal, siempre lo puedo aceptar
haz click en donate debajo de mi nombre.

And where the RDS flash point?

hi
thanks for the great work! congratz!
i have a moto maxx br version. im using cm12 with twrp. i can downgrade to OTA 4.4.4 using this tutorial? and if yes, its safe? i'm asking because i see a lot of post of bricked mmaxx owners. thanks in advance!

fillonov said:
And where the RDS flash point?
Click to expand...
Click to collapse
It's on the official firmware thread
colthars said:
hi
thanks for the great work! congratz!
i have a moto maxx br version. im using cm12 with twrp. i can downgrade to OTA 4.4.4 using this tutorial? and if yes, its safe? i'm asking because i see a lot of post of bricked mmaxx owners. thanks in advance!
Click to expand...
Click to collapse
As long as you have unlocked bootloader and only took the ota for lollipop it's ok

[Q] Not in FAQ - mind puzzler
After cable got unplugged while flashing moforoot. I have tried to put stock ROM back on through boot loader.
I get stuck on your step #4. Says devices not found.
I am able to see my phone though usb deview as fastbook quark S... or while in recovery mode as xt1254. (see attached)
I have uninstalled/reinstalled drivers mulitple times but it will not take to my phone/computer.
I have used USBDeview.
I have done partition clean.
I have wiped/factory reset
I have tried RSD Lite - which will not find the device
I have tried connecting it to PC through recovery mode.
I have tried everything. Still at a stand still. Help would be greatly appreciated. I would much rather donate someone on here than to pay 200$ to insurance a new phone.

jerney307 said:
After cable got unplugged while flashing moforoot. I have tried to put stock ROM back on through boot loader.
I get stuck on your step #4. Says devices not found.
I am able to see my phone though usb deview as fastbook quark S... or while in recovery mode as xt1254. (see attached)
I have uninstalled/reinstalled drivers mulitple times but it will not take to my phone/computer.
I have used USBDeview.
I have done partition clean.
I have wiped/factory reset
I have tried RSD Lite - which will not find the device
I have tried connecting it to PC through recovery mode.
I have tried everything. Still at a stand still. Help would be greatly appreciated. I would much rather donate someone on here than to pay 200$ to insurance a new phone.
Click to expand...
Click to collapse
You have a droid turbo you have to flash back using rsd lite, I believe the rsd version you have doesn't detect your phone, uninstall it and use the one on my thread http://forum.xda-developers.com/showthread.php?t=3063470, also download your phones firmware (verizon) and your phone will be detected and it will flash

If I am on 4.4.4 and I wish to flash the Indian 5.0.2 firmware, I need to include the following line:
mfastboot flash partition gpt.bin
Click to expand...
Click to collapse
but if I later want to go back to 4.4.4, I will need to skip flashing gpt.bin, correct?
I guess I want to verify that 1) flashing gpt.bin is necessary for Lollipop and 2) running an upgraded partition doesn't cause any problems for KitKat
Thanks!

Jaocagomez said:
It's on the official firmware thread
As long as you have unlocked bootloader and only took the ota for lollipop it's ok
Click to expand...
Click to collapse
About the RDS -> In the instraction i cant find the point where i have to flash it with RDS. Only adb. So I asked where have i to run RDS, what file to put there and flash?
So, if i have Br 5.0.2 i jast flash with RDS the file with Mex 5.0.2???

dreyln said:
If I am on 4.4.4 and I wish to flash the Indian 5.0.2 firmware, I need to include the following line:
but if I later want to go back to 4.4.4, I will need to skip flashing gpt.bin, correct?
I guess I want to verify that 1) flashing gpt.bin is necessary for Lollipop and 2) running an upgraded partition doesn't cause any problems for KitKat
Thanks!
Click to expand...
Click to collapse
That's exactly how it works

fillonov said:
About the RDS -> In the instraction i cant find the point where i have to flash it with RDS. Only adb. So I asked where have i to run RDS, what file to put there and flash?
So, if i have Br 5.0.2 i jast flash with RDS the file with Mex 5.0.2???
Click to expand...
Click to collapse
No, don't flash OTA just full firmware

problem
OK, I decided to flash the India Lollipop 5.02 to my Mexico Moto Maxx which still has 4.4.4. Bootloader unlocked, rooted, has TWRP recovery installed.
I started by copying and pasting the first command while in Fastboot. I get this error message. What am I doing wrong?
{
"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"
}

Grab the mfastboot.exe from the link in the first post and put it in the same directory as fastboot.exe.

ChazzMatt said:
OK, I decided to flash the India Lollipop 5.02 to my Mexico Moto Maxx which still has 4.4.4. Bootloader unlocked, rooted, has TWRP recovery installed.
I started by copying and pasting the first command while in Fastboot. I get this error message. What am I doing wrong?
Click to expand...
Click to collapse
OK, solved the problem. I copied and pasted all the India files to my regular ADB Android/SDK2/Platform Tools folder and did everything from there. I just removed the "m" from the front of all the fastboot commands as I was no longer using "Minimal" version.
I purposefully left out the recovery image command as I want to retain TWRP...
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash boot boot.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 erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Phone is rebooting now. Wish me luck! :good:
___________
Hmmmmm... seems stuck on the boot logo for a LONG time! How long until I get worried?
---------- Post added at 04:13 PM ---------- Previous post was at 04:05 PM ----------
Steve-x said:
Grab the mfastboot.exe from the link in the first post and put it in the same directory as fastboot.exe.
Click to expand...
Click to collapse
I downloaded and installed Minimal Fastboot from the first post. I don't see an mfastboot.exe.

The link is in the first post but here it is again:
https://mega.co.nz/#!MVtz1DLb!CZTh_-wCl-qyta4Q0yZuPk_TB6Wq7Z4zElk6eArXrXk

Steve-x said:
The link is in the first post but here it is again:
https://mega.co.nz/#!MVtz1DLb!CZTh_-wCl-qyta4Q0yZuPk_TB6Wq7Z4zElk6eArXrXk
Click to expand...
Click to collapse
Thanks. I thought it was the same program as in the links above, just a different place to download it. Then Chrome blocked it twice, so I had to use IE to download it.
Flashing everything again using mfastboot. Let's see if it works this time!
At least I'm doing it on my "spare" Moto Maxx first. Not that I want to ruin it, because I still want to sell it...
---------- Post added at 04:36 PM ---------- Previous post was at 04:33 PM ----------
___________________
Still stuck on the Motorola logo like before. NOT good.
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
________
@Jaocagomez,
You say this:
Q: Why did you not include gpt.bin in the flashing???
A: Because if you were on kitkat, installed brasil or another firmware and take a OTA to lollipop your gpt.bin version will be greater than the one you'll try to flash and it will FAIL TO FLASH, dont worry just skip that line.
Click to expand...
Click to collapse
Yet I see flash gpt.bin as your first command.
5.- Install
Copy and Paste these commands on Minimal ADB and Fastboot:
Quote:
mfastboot flash partition gpt.bin
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
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 system system.img_sparsechunk.4
mfastboot erase cache
mfastboot erase userdata
mfastboot oem fb_mode_clear
mfastboot reboot
and thats all, as easy as copy from here and paste on cmd.
Click to expand...
Click to collapse
Is that a mistake? And how do I fix my phone now?

Did you flash all 8 of the system chunks?
With your bootloader unlocked there should be almost no way to mess up the phone, so no need to panic at all.

Steve-x said:
Did you flash all 8 of the system chunks?
With your bootloader unlocked there should be almost no way to mess up the phone, so no need to panic at all.
Click to expand...
Click to collapse
Yeah, figured it out. I was taking the list too literally. There are 8 sparse chunks in the India image, and I only flashed 0-4. I feel stupid. :crying:
Rebooted and everything is fine. Now on India Lollipop 5.02!
Woo hoo! I now have a Moto Turob XT1225. But for some reason TWRP didn't get saved? when I go to "recovery" I get the Android with the open chest. Hmmm... guess I can reflash TWRP, right?
Now just have to do it with my main phone -- my Puerto Rico Moto Maxx -- I mean Moto Turbo.
Need to back up everything with Titanium Backup -- again -- and transfer off to my PC so I can restore all my apps...

The phone OS is restoring the factory recovery image each boot up because it detected the recovery image wasn't the factory image. If you flash TWRP and then root the phone it will no longer get overwritten as the rooting process disables this "feature".

Steve-x said:
The phone OS is restoring the factory recovery image each boot up because it detected the recovery image wasn't the factory image. If you flash TWRP and then root the phone it will no longer get overwritten as the rooting process disables this "feature".
Click to expand...
Click to collapse
OK, flashed TWRP and rooted.
I even made a TWRP backup with root, but for some reason I can't see the TWRP folder on my Mexico Moto Maxx/Moto Turbo with Lollipop. Even when I use TWRP file manager to copy the backup file to the Download folder, I can't see it there either. Very strange. I want to upload the TWRP folder with India Lollipop for others to use.
In my Puerto Rico 4.4.4 Moto Maxx I see ALL my folders, including TWRP.

ChazzMatt said:
OK, flashed TWRP and rooted.
I even made a TWRP backup with root, but for some reason I can't see the TWRP folder on my Mexico Moto Maxx/Moto Turbo with Lollipop. Even when I use TWRP file manager to copy the backup file to the Download folder, I can't see it there either. Very strange. I want to upload the TWRP folder with India Lollipop for others to use.
In my Puerto Rico 4.4.4 Moto Maxx I see ALL my folders, including TWRP.
Click to expand...
Click to collapse
i dont know if thats a twrp bug or lollipop one.

Soft Bricked - "Fall-through from normal boot mode"

Hi all.
Today, after rebooting my X4, I got greeted by a black bootloader screen, saying the following (attached photo for more details):
Code:
AP Flastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Flastboot Reason: Fall-through from normal boot mode
Choosing to enter recovery mode does nothing. I have a "Factory" option, which probably does factory reset?
It may have something to do with Magisk uptade that gave a error and couldn't get installed a week ago. It's been at least a month since I last rebooted the phone, so it's hard to know.
my question is: As the system seems ok (I was using it normally before rebooting) could I fix it without flashing stock or factory resetting and losing my data? Like booting TWRP and restoring just the boot partition from a backup?
I would rather not have to set up the whole thing again if I don't need to

Twski said:
Hi all.
Today, after rebooting my X4, I got greeted by a black bootloader screen, saying the following (attached photo for more details):
Code:
AP Flastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Flastboot Reason: Fall-through from normal boot mode
Choosing to enter recovery mode does nothing. I have a "Factory" option, which probably does factory reset?
It may have something to do with Magisk uptade that gave a error and couldn't get installed a week ago. It's been at least a month since I last rebooted the phone, so it's hard to know.
my question is: As the system seems ok (I was using it normally before rebooting) could I fix it without flashing stock or factory resetting and losing my data? Like booting TWRP and restoring just the boot partition from a backup?
I would rather not have to set up the whole thing again if I don't need to
Click to expand...
Click to collapse
I suppose you have bootloader unlocked. Extract boot.img from fastboot ROM (https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/) and flash it using this command: fastboot flash boot boot.img.

Comby_sk said:
I suppose you have bootloader unlocked. Extract boot.img from fastboot ROM (https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/) and flash it using this command: fastboot flash boot boot.img.
Click to expand...
Click to collapse
I get this:
Code:
c:\adb\platform-tools>fastboot flash boot boot.img
error: Failed to identify current slot
Can I specify a slot for it to flash?
Tried to boot twrp aswell, it gives me "(bootloader) Failed to load/authenticate boot image: Not Found"
EDIT: fastboot -set-active-slot=a / -set-active-slot=b was what I needed. Changed it to B (I knew it was lastly using B), flashed stock boot.img, booted TWRP and restored my rooted boot.img from a backup.

Twski said:
I get this:
Code:
c:\adb\platform-tools>fastboot flash boot boot.img
error: Failed to identify current slot
Can I specify a slot for it to flash?
Tried to boot twrp aswell, it gives me "(bootloader) Failed to load/authenticate boot image: Not Found"
EDIT: fastboot -set-active-slot=a / -set-active-slot=b was what I needed. Changed it to B (I knew it was lastly using B), flashed stock boot.img, booted TWRP and restored my rooted boot.img from a backup.
Click to expand...
Click to collapse
I know this thread is old, but I have the same exact problem and can't find any solution. What brought mine about was I restored my stock boot image from within Magisk and then I tried reinstalling Magisk afterwards without a reboot, but got an error. When I rebooted, the problem started. I can't possibly think of what is wrong. I tried switching slots, but it says my device doesn't support slots. Any idea what else I can try?

Twski said:
I get this:
Code:
c:\adb\platform-tools>fastboot flash boot boot.img
error: Failed to identify current slot
Can I specify a slot for it to flash?
Tried to boot twrp aswell, it gives me "(bootloader) Failed to load/authenticate boot image: Not Found"
EDIT: fastboot -set-active-slot=a / -set-active-slot=b was what I needed. Changed it to B (I knew it was lastly using B), flashed stock boot.img, booted TWRP and restored my rooted boot.img from a backup.
Click to expand...
Click to collapse
Thanx very much, man! U saved me!

no meu moto g8 plus eu tinha perdido o root e tentei reinstalar a imagem pelo maginsk e ele não começou e depois apaguei várias coisas do sistema com o twrp e agora ele só dá as mesmas mensagens e não sei o que fazer sim, eu tentei de tudo, e ao ter que instalar uma rom aparece "destino relatado tamanho máximo de download de 805273600 bytes
enviando 'boot' (65536 KB) ...
OK [2.168s]
escrevendo 'boot' ...
(bootloader) Nome de partição inválido boot
FAILED (falha remota)
concluído. tempo total: 2.319s " para todos os comunicadores

MarttinsBR01 said:
no meu moto g8 plus eu tinha perdido o root e tentei reinstalar a imagem pelo maginsk e ele não começou e depois apaguei várias coisas do sistema com o twrp e agora ele só dá as mesmas mensagens e não sei o que fazer sim, eu tentei de tudo, e ao ter que instalar uma rom aparece "destino relatado tamanho máximo de download de 805273600 bytes
enviando 'boot' (65536 KB) ...
OK [2.168s]
escrevendo 'boot' ...
(bootloader) Nome de partição inválido boot
FAILED (falha remota)
concluído. tempo total: 2.319s " para todos os comunicadores
Click to expand...
Click to collapse
Try this solution:
No bootable A/B Slot and OEM locked device, not able to revert to stock.
Hello everybody! My brother got a Moto One (XT 1941-3) last year and tried to flash it, but somehow he got the wrong Rom and bricked it. I'm trying to recover the phone to its stock rom, but the device says that it is OEM_locked, so I can't...
forum.xda-developers.com

Security patch October 2018

Hi, see if someone can help me !!! I arrived by the October 2018 patch via OTA for Android 8.1. I have unlocked bootloader, TWRP and Magisk root, for MO that installing this license, I would leave a brick! There is some method to install the OTA or some way to make UK Zip flash for TWRP or some form of meter by ADB? Ota_Package_ops28.65-36.zip Poch Upload the Zip to Google Drive and share it if necessary !!
------------------
Hola, a ver si alguien me puede ayudar!!! me llego el parche de octubre 2018 via OTA para android 8.1. Tengo bootloader desbloqueado, twrp y magisk root, por mo que instalar este ñarche me dejaría un ladrillo! Hay algún metodo para instalar la OTA o alguna forma de hacer uk zip flashable por twrp o alguna forma de meter por adb?OTA_Package_OPS28.65-36.zip piedo subir el zip a google drive y compartirlo si es necesario!!

I have my phone with unlocked bootloader, TWRP and Magisk Root. I have the same question than u have, in case I get the OTA October Patch Security, how can I install it?

Did you get October security patch update? Where are you from guys?

amritmalviya said:
Did you get October security patch update? Where are you from guys?
Click to expand...
Click to collapse
I'm from Argentina, I have the channel retar, my phone is XT-1800, and I installed the firmware 8.1 of adb. I have the boot unlocked and root with magisk, I download the patch from October 1, 2018. The question now would be, if we reset the firmware again and we did not modify it, only having the boot unlocked to be able to install the patch without problems?

I confirm, reinstalling the stock firmware, and without modifying anything, just having the bootloader unlocked, I got the message of the patch, I downloaded it and installed the cell phone is working wonderfully now with the October patch!
----------------------------------
Confirmo, reinstalando el firmware stock, y sin modificar nada, solo teniendo el bootloader desbloqueado, me llego el mensaje del parche, lo descargue le di instalar y el celular esta funcionando de maravilla ahora con el parche de octubre!!!

how did you installed the stock firmware?
did you used files from: https://androidfilehost.com/?w=files&flid=214680
or where did you get the original image?

DavidXanatos said:
how did you installed the stock firmware?
did you used files from: https://androidfilehost.com/?w=files&flid=214680
or where did you get the original image?
Click to expand...
Click to collapse
Here is the link to the original.
Installation instructions:
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
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

Its strange, on a new phone after oreo update I have unlocked the bootloader and started twrp via fastboot (without flashing it to the phone) to backup the partitions.
Now I got the update notification and it cant install the OTA update.
I have compared boot, recovery and system from the twrp backup with the files in the original firmware archive and they are identical.
Now ncandroid84 confirms that just the unlocked bootloader should be fine.
So the question is why it fails, and which partition has the problem?

DavidXanatos said:
Its strange, on a new phone after oreo update I have unlocked the bootloader and started twrp via fastboot (without flashing it to the phone) to backup the partitions.
Now I got the update notification and it cant install the OTA update.
I have compared boot, recovery and system from the twrp backup with the files in the original firmware archive and they are identical.
Now ncandroid84 confirms that just the unlocked bootloader should be fine.
So the question is why it fails, and which partition has the problem?
Click to expand...
Click to collapse
Remember. You cannot update the system by OTA if the bootloader is unlocked, TWRP is installed, and ROOT is installed. The consequences can be sad.
And also, it is impossible to make a rollback to the previous version of firmware.

[OP7P] [Final update: H33] Android 11/12 Firmware collection

The OnePlus 7 Pro is now officially EOL, which means going forward new vulnerabilities found in the firmware stay unpatched.
I present to you Android 11/12 firmware collection, to be flashed within fastbootd mode. For that you need a compatible recovery and your device needs to be unlocked.
For example the official Lineage OS recovery supports fastbootd.
Instructions using Lineage OS recovery (copied from the official Lineage OS Wiki)
1. Boot up LineageOS recovery (fastboot boot recovery.img)
2. Go to “Advanced” -> “Enter fastboot” (you will notice that the recovery switches to an orange color)
3. Connect your phone with your pc and execute the following commands:
Code:
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 hyp hyp.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all LOGO LOGO.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all oem_stanvbk oem_stanvbk.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
fastboot reboot
Downloads (Global and Europe versions):
Dropbox
Mega
Happy flashing!​

11.0.1.1 global firmware added
Edit: Europe firmware now uploaded.

hi there,
hopefully u can help. i started this in windows powershell in the order where the .img files are
fastboot flash --slot=all abl abl.img
but get always error. unknow option -- slot=all
any idea what do i wrong??
thanks

Sirloc said:
hi there,
hopefully u can help. i started this in windows powershell in the order where the .img files are
fastboot flash --slot=all abl abl.img
but get always error. unknow option -- slot=all
any idea what do i wrong??
thanks
Click to expand...
Click to collapse
make sure you use the latest fastboot, which can be downloaded here: https://developer.android.com/studio/releases/platform-tools
And make sure you are in fastbootd mode.

11.0.2.1 global and europe firmware added

Using locked BL with Pixel Experience. Cannot flash from fastboot because "Download is not allowed on locked devices", but that's the way to upgrade firmware so.... Any suggestions?
Maybe a flashable zip just for flashing this from recovery?

jknvv13 said:
Using locked BL with Pixel Experience. Cannot flash from fastboot because "Download is not allowed on locked devices", but that's the way to upgrade firmware so.... Any suggestions?
Maybe a flashable zip just for flashing this from recovery?
Click to expand...
Click to collapse
sorry, you can't flash firmware from regular fastboot. you need to be in fastbootd mode. the official lineage os recovery supports it for example

hellcat50 said:
sorry, you can't flash firmware from regular fastboot. you need to be in fastbootd mode. the official lineage os recovery supports it for example
Click to expand...
Click to collapse
Actually using fastbootd with Pixel Recovery. But locked BL is the issue.

jknvv13 said:
Actually using fastbootd with Pixel Recovery. But locked BL is the issue.
Click to expand...
Click to collapse
oh sorry my bad. i'll update my thread accordingly and gl with fixing your problem

hellcat50 said:
oh sorry my bad. i'll update my thread accordingly and gl with fixing your problem
Click to expand...
Click to collapse
Correct me if I'm wrong but...
A flashable zip would work under Pixel/Lineage/Modified recovery.
Because AFAIK the problem is when you modify system files, but not the other partitions that store the fw parts.

jknvv13 said:
Correct me if I'm wrong but...
A flashable zip would work under Pixel/Lineage/Modified recovery.
Because AFAIK the problem is when you modify system files, but not the other partitions that store the fw parts.
Click to expand...
Click to collapse
i suggest you ask the rom developer on how to update the firmware with a locked bootloader

11.0.3.1 global firmware added

11.0.3.1 europe firmware added

This is the 4th option I have tried and it doesn't work. I'm on unlocked OP 7Pro; it was already on Android 11 when I got it so I can't install TWRP. I was able to root and install LOS 18.1. I haven't been able to install any other ROMs. I can't even go back to stock now.... What am I missing?
I have already installed the latest drivers, software, etc. Most guides are for Android 10 which makes this more difficult but even the more recent guides fail to do anything except cause an occasional bootloop if they even do anything at all.

MrAwesome75 said:
This is the 4th option I have tried and it doesn't work. I'm on unlocked OP 7Pro; it was already on Android 11 when I got it so I can't install TWRP. I was able to root and install LOS 18.1. I haven't been able to install any other ROMs. I can't even go back to stock now.... What am I missing?
I have already installed the latest drivers, software, etc. Most guides are for Android 10 which makes this more difficult but even the more recent guides fail to do anything except cause an occasional bootloop if they even do anything at all.
Click to expand...
Click to collapse
Hi, I have only had my op7p for a little over a week and mine was a11 but I as able to install twrp many many times , There are several good xda posts that helped me tremendously including a functional msm tool
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
[MSM Tool] Guac for All
To everyone who donated, I love y'all. This took a really long time to get lol but it's straight from support and I did not make any modifications to it; I hope it helps a lot of people. The revision is listed in the archive, I believe it's...
forum.xda-developers.com
Just trying to help, Sorry if you tried both of these before.

Eu estava com a OOS 11.0.3.1 no meu OP7P porém resolvi instalar a custom ROM dotos. Infelizmente não gostei muito do resultado e gostaria de voltar a stock. Já tentei esse tutorial entre outros que voltam para a oxygen 10 mas nenhum deu certo. Poderia me ajudar

11.0.4.1 europe and global firmware added

Sir Hopefull For Reply
I'm a little confuse here
- Theres no system img file in the zip file
- what if I am on custom rom and have fastbootd recovery can I direct flash 11.0.4.1 these files?
- or is it for only update
Thanks

Tnbh9 said:
Sir Hopefull For Reply
I'm a little confuse here
- Theres no system img file in the zip file
- what if I am on custom rom and have fastbootd recovery can I direct flash 11.0.4.1 these files?
- or is it for only update
Thanks
Click to expand...
Click to collapse
it's intented to be used to update your firmware while you are running custom roms like lineage os

11.0.5.1 global and europe firmware added