Database Users

DOWNGRADE Danger of hard brick

Danger of hard brick
Mind you, the you that you have installed the version 5.1 and you please do downgrade.
If possible downgrade and works CORRECTLY, but does not drop the bootloader version. (Motorola apparently not contemplated back the bootloader)
Well, if after downgrade accept an OTA, OTA is flash the bootloader and, being superior version, fails, result: this just corrupt. The phone turns off and no more lights. If the computer connect this is recognized as QHUSB_BULK. That while you have battery, since neither charge.
There are many moto g afflicted with the same problem, and have been waiting to release the BLANKFLASHFILES files needed to revive the phone. Unfortunately it seems that Motorola only thing it does is send to the affected to a technical service, with subsequent payment of repair, as it seems to those files could change the IMEI, etc.
So you know, maybe not downgrade, but if ye do not accept any OTA, the cell dies.
I speak from experience,The announcement is made

I downgrade from 5.1 to 5.0.2 thanks for the info bro
Enviado desde mi MotoE2(4G-LTE) mediante Tapatalk

i downgrade my moto e XT1524 and he's hard brick
moto G solution does not work for the moto e
is the a solution ???

can someone explain this with some better english?

In short, please never install any OTA update if you have downgraded from 5.1 stock rom to 5.0.2 stock rom. Otherwise your moto e will be dead permanently as motorola will never release the files to recover it.
If you have hardbricked in this way, only solution is to sell all parts individually except the motherboard like me. I have recovered 50% of its cost (Moto E 1st Gen).

Would flashing 5.0.2 bootloader along with downgrading prevent this issue ?

pollazht said:
Would flashing 5.0.2 bootloader along with downgrading prevent this issue ?
Click to expand...
Click to collapse
Excluding the flash bootloader probably would avoid the brick

iks8 said:
can someone explain this with some better english?
Click to expand...
Click to collapse
LOL yeah no kidding..
I've done it but...
Like none of these guys mention.. Most use custom roms and god knows what else.
Most people here use CM and then assume everyone else does too
I have done it a few times and had no problems.

ENRIQUEMM said:
Excluding the flash bootloader probably would avoid the brick
Click to expand...
Click to collapse
Sorry, I don't understand.
If I downgrade to be safe from brick I should:
a) Leave the the 5.1 bootloader
or
b) Flash the 5.0.2 bootloader and then flash Lollipop 5.0.2
?
Thanks in advance.

pollazht said:
Sorry, I don't understand.
If I downgrade to be safe from brick I should:
a) Leave the the 5.1 bootloader
or
b) Flash the 5.0.2 bootloader and then flash Lollipop 5.0.2
?
Thanks in advance.
Click to expand...
Click to collapse
A
If you already have version 5.1 bootloader CAN NOT DOWNGRADE, that's what causes the brick.
The flash fails and nothing happens, do not touch it.
The OTA is that if it tries to update and how it can not be corrupted. No more lights.

Need to downgrade
Hi there I updated moto E2(4G-LTE) to marshmallow..
After update it started heating up and battery drains more quickly..
I have tried all the solutions but nothing fixed it So I need to downgrade
It to lollipop 5.1.1 from marshmallow 6.0.. Will the service center people will downgrade it for me.. Or is there any solution for it

Shepherd22 said:
Hi there I updated moto E2(4G-LTE) to marshmallow..
After update it started heating up and battery drains more quickly..
I have tried all the solutions but nothing fixed it So I need to downgrade
It to lollipop 5.1.1 from marshmallow 6.0.. Will the service center people will downgrade it for me.. Or is there any solution for it
Click to expand...
Click to collapse
you can make flash version 5.1.1 , will fail to flash the bootloader , but ignores and continues .
for safety otas not accept , but if the ota update the bootloader by which you should not miss anything .
Enviado desde mi MotoE2(4G-LTE) mediante Tapatalk

ducatman said:
i downgrade my moto e XT1524 and he's hard brick
moto G solution does not work for the moto e
is the a solution ???
Click to expand...
Click to collapse
Hi, I have the same problem, did you manage to solve it?
Thank you"

Hi, thanks for warning. Can DOWNGRADE from 6.0 to 5.1 except BOOTLOADER ???

kaotd99 said:
Hi, thanks for warning. Can DOWNGRADE from 6.0 to 5.1 except BOOTLOADER ???
Click to expand...
Click to collapse
Even if you would want, you couldn't downgrade INCLUDING bootloader )))
If the phone is unlocked, then any kernel, system, modem, and recovery can be flashed. Feel free to experiment, but don't receive any OTA after that. Receiving OTA on unlocked Motorola phone is prohibited, generally speaking. OTA mechanism isn't aware of every of your modification inside the phone, so kills what's not right to him.

m_loaiza said:
I downgrade from 5.1 to 5.0.2 thanks for the info bro
Enviado desde mi MotoE2(4G-LTE) mediante Tapatalk
Click to expand...
Click to collapse
how did u do that...plz tell me tge process

heeeeeeelp
m_loaiza said:
I downgrade from 5.1 to 5.0.2 thanks for the info bro
Enviado desde mi MotoE2(4G-LTE) mediante Tapatalk
Click to expand...
Click to collapse
bro plz tell me how to downgrade moto e lte from MM 6.0 to LP 5.0

I have a problem. I had the stock rom 5.1 or 5.0 can not remember which, actulice to version 6.0 OTA that firware I have to download?

Error Update OTA moto XPlay...

Hi There,
Yesterday i've received the notification of update 24.211.11.en.EU for my moto Xplay. Problem i had a TWRP Recovery, so i made the manip to come back to a stock recovery... with success, i think, fastboot tell me "okay". But the install stop with message "error" ... help ...

you can install by RDS Lite firmware factory.
Enviado desde mi XT1635-02 mediante Tapatalk

Moto g4 plus is not responding..bootloader not opening :(

hi friends,
i just flashed Marshmallow rom and downloaded the nougat from system update.. after installing the update Suddenly the device got switched off ...it is not responding at all... bootloader is also not opening ...just blinking the LED light While connecting with charger...pls help me...!

Did you downgrade from nougat to marshmallow and take the OTA? If yes, think u have bricked the phone.
Enviado desde mi Moto G (4) mediante Tapatalk

As Fede79 has mentioned, if you downgraded from the March 2017 or June 2017 stock firmware with an older firmware update (e.g Marshmallow), then accepted the OTA, you'd have likely hard bricked with a corrupted bootloader.
You can try rescuing your device with the blank flash from this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
If it works, then afterwards do not accept any OTA updates if you choose to downgrade. If you think you'll forget this, then do not downgrade.

Fede79 said:
Did you downgrade from nougat to marshmallow and take the OTA? If yes, think u have bricked the phone.
Enviado desde mi Moto G (4) mediante Tapatalk
Click to expand...
Click to collapse
Yes...by mistake i have done like that

echo92 said:
As Fede79 has mentioned, if you downgraded from the March 2017 or June 2017 stock firmware with an older firmware update (e.g Marshmallow), then accepted the OTA, you'd have likely hard bricked with a corrupted bootloader.
You can try rescuing your device with the blank flash from this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
If it works, then afterwards do not accept any OTA updates if you choose to downgrade. If you think you'll forget this, then do not downgrade.
Click to expand...
Click to collapse
Thank you :highfive: echo92 ...it worked...thanks a lot...:good:

[warning][hardbrick] dont flash ota updates blindly !!!

Hello everyone,
I am here to tell you guys. If you ever updated/flashed stock nougat soak test/ official updates on your moto x play. And if you reverted back to marshmallow. Then don't flash any ota updates you've recieved . Because it will result in a hardbrick (no fastboot/recovery mode).
As of now, there are no proper blank flash files to rescue device from hardbrick .blank flash files are present in leaked nougat soak test fastboot firmware. But they aren't working on these hardbricked devices
And I have seen almost 5-7 guys in past few days hard bricking their device by flashing ota updates
Motorola already mentioned that once updated you cannot rollback to previous android versions.
NOTE: You cannot downgrade to a previous software version after installing this update.
Click to expand...
Click to collapse
READ IT HERE !!
Note: if you ever wanted to rollback to previous android version then fastboot flash boot,system,userdata partitions only

Innfinite4evr said:
Hello everyone,
I am here to tell you guys. If you ever updated/flashed stock nougat soak test/ official updates on your moto x play. And if you reverted back to marshmallow. Then don't flash any ota updates you've recieved . Because it will result in a hardbrick (no fastboot/recovery mode).
As of now, there are no proper blank flash files to rescue device from hardbrick .blank flash files are present in leaked nougat soak test fastboot firmware. But they aren't working on these hardbricked devices
And I have seen almost 5-7 guys in past few days hard bricking their device by flashing ota updates
Motorola already mentioned that once updated you cannot rollback to previous android versions.
READ IT HERE !!
Note: if you ever wanted to rollback to previous android version then fastboot flash boot,system,userdata partitions only
Click to expand...
Click to collapse
I applied a guy's Twrp recovery n now m on Sept. 1 security path along with 7.1.1 . Will it brick my phone if I flash 6.0.1 again through adb. ?? And please suggest a way to root Moto x play on 7.1.1 the old version of super su isn't working.
---------- Post added at 10:31 AM ---------- Previous post was at 10:28 AM ----------
Plus suggest a Valid way to get back to 6.0.1 . Bettery life is terrible on 7.1.1 . It was bit better on 6.0.1...even after clearing dalvic cache n all the stuff from Twrp..device can be hard bricked??? ..

my devices is bricked ****

Once you have decided to use custom rom and unlocked your bootloader, you no longer use stock rom. even if you use stock rom, you shall not accept or install OTA updates.

Many guys got their devices hard bricked including me and there is no fix till date.. Gave to various service centers and all are saying to change Mother Board, which may cost around 8k approximately.. Emmc can be flashed via Jtag box.. But guys using Jtag box are very rare.. As of now my MXP is kinda paper weight !!!

same here waiting for blank files

gilbertoperezx1 said:
same here waiting for blank files
Click to expand...
Click to collapse
Ídem..
Enviado desde mi XT1635-02 mediante Tapatalk

Blank repair firmware needed .
help ...............

aamszia said:
Blank repair firmware needed .
help ...............
Click to expand...
Click to collapse
There is no working blank flash files available.. You can get the MB Jtag Flashed or get the MB replaced.

Oh man, I wish I had this information before. Now my Moto X Play is also bricked
Well, I guess I'll wait to see if a method to unbrick comes along in the near future.

Moto G4 Amz Version

Hello, i would like to ask here if someone has the same issue, i had a fully working Moto G4 AMZ Version Running Nougat, however after waiting too much and the oreo version never was released, i wanted to try to flash the firmware and update it via rsd lite with oreo version, however this resulted in my phone bricked, i tried some ways to downgrade again to nougat however i was not able since it is not possible to downgrade to stock amz firmware once i had updated it with wrong version of 8.0, so may i ask if after maybe 1 year is there any advance or release for the 8.0 amz version firmware? i think the only solution for this is to send the device back to motorola, but i will ask first here any other ideas?
Thank you in Advance
Henser.

Use lenovo save and rescue to unbrick your phone.
I’ve tried installing stock moto G4 Android 8.1 and no luck. This is with boot loader unlocked, custom kernel and root. No luck.

same issue, i try from time to time to recover the device with no luck, still waiting for a solution with bootloader locked