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?
My gf wants mm so badly, but she does not want to do all the flash work again, plus wiping. Lazy.
She has unlocked bootloader and root. Version B140.
She just received the OTA B181 and I was wondering if a normal update would work, just removing the root before. I know that in Samsung phones that does the trick.
Also: will the recovery be overwritten? Will the bootloader remain unlocked (i think so)?
(Also i just read something about that bug that block the update at 4%, is it the B171 or it affects the B181 aswell?)
Thank you guys, I know theese may sound noob questions.
Bootloader remains unlocked, maybe not necessary unroot if you do a local update
Inviato dal mio ALE-L21 utilizzando Tapatalk
I recently bought a P8 GRA-UL10 and next thing i did was to update to MM but it turns out it's "beta" in Europe, i think only in Asia there's a stable version so far.
So i tried to rollback with the, only, two firmware i found either on XDA or Google and nothing successful, it just don't downgrade poping always the same error.
I tried VIA hardware combination and with DIAL-PAD code, it turns the same error.
Anyone with an idea what can be done?
I recently have the same problem!
I just got my phone recently from //Buymobilebd I am facing the same problem, I ask them for help so they took my phone into their service center for fixing this.
They fixed it for free?
Enviado do meu HUAWEI GRA-UL10 através de Tapatalk
migueli2 said:
I recently bought a P8 GRA-UL10 and next thing i did was to update to MM but it turns out it's "beta" in Europe, i think only in Asia there's a stable version so far.
So i tried to rollback with the, only, two firmware i found either on XDA or Google and nothing successful, it just don't downgrade poping always the same error.
I tried VIA hardware combination and with DIAL-PAD code, it turns the same error.
Anyone with an idea what can be done?
Click to expand...
Click to collapse
I also have that version, and yes it is in beta, but it is pretty much stable and ready for the public, you can use it with no problem, unless you are facing some bugs I don't understand why do you want to downgrade. If your model is from china I can maybe help you find the solution if you still want to downgrade.
fede011 said:
I also have that version, and yes it is in beta, but it is pretty much stable and ready for the public, you can use it with no problem, unless you are facing some bugs I don't understand why do you want to downgrade. If your model is from china I can maybe help you find the solution if you still want to downgrade.
Click to expand...
Click to collapse
Only the thing that camera lost to many quality...
Rest is fine with some improvements.
Enviado do meu HUAWEI GRA-UL10 através de Tapatalk
Hi There! I had a problem with the update.
I received the update to nougat, downloaded it, and the donwload freeze at% 52 and proceeded to cancel it. Then when I wanted to download the update again it appears that the device is already updated, but I'm still in marshmallow. I already tried several times in these 3 or 4 days that pass already and I did not succeed. Someone to help me try to know what happened so I can upgrade to nougat.
By the way, my device it's pure stock.
Please anyone can help me?
Enviado desde mi XT1635-02 mediante Tapatalk
Maybe worth looking into installing Nougat 93-11 or 93-14 via fastboot, so that your device can be fully updated. https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
These images may overwrite your partial flash and allow you to properly boot into nougat.
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: