[Q]Hard bricked Moto E - Moto E Q&A, Help & Troubleshooting

I have hard bricked my device XT1022. I have no other phone now.
All I wanna ask is.. can anybody provide me the blankflash files for XT1022 Moto E?
Or is my device gone forever?
Please help :'(
I'm dying :'(
Life is impossible without a phone and I'm a student and I dont earn so I cant buy a new one either :'(

---

nilanko said:
I have hard bricked my device XT1022. I have no other phone now.
All I wanna ask is.. can anybody provide me the blankflash files for XT1022 Moto E?
Or is my device gone forever?
Please help :'(
I'm dying :'(
Life is impossible without a phone and I'm a student and I dont earn so I cant buy a new one either :'(
Click to expand...
Click to collapse
Flash stock ROM using fastboot

---

nilanko said:
I have hard bricked my device XT1022. I have no other phone now.
All I wanna ask is.. can anybody provide me the blankflash files for XT1022 Moto E?
Or is my device gone forever?
Please help :'(
I'm dying :'(
Life is impossible without a phone and I'm a student and I dont earn so I cant buy a new one either :'(
Click to expand...
Click to collapse
LOL..........Same here...........Ur best bet is to take ur phone to a service centre.......Most probably, they won't check if u have voided ur warranty (Based on the experiences of a few Moto G owners who did the same with their phones and got them bricked)......Tell them that ur phone became like this after an update and they'll fix it for u, I guess.........Try and tell me .....I'm planning on doing the same Missing my phone :crying::crying::crying:
---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------
Adarsh1998 said:
Flash stock ROM using fastboot
Click to expand...
Click to collapse
The phone won't turn on.

---

Thankyou for the suggestions dem0nicbl00d. I have talked to the service center owner and he asked me to come on Monday as tomorrow is a holiday.
Another thing is that, I followed http://forum.xda-developers.com/moto-e/development/unbrick-hard-bricked-moto-e-t2974093 this guide and after doing this, the computer doesn't even detect the phone as qhsusb_bulk anymore. It just shows that an "unknown USB device" is connected. I tried re-following the same guide and re-ran blankflash but now all it shows is "waiting for device" which means that even if I get the required blank flash files, it'll be impossible to flash them as the phone is completely dead.
Is the phone really dead now? I mean can't it ever be switched on again? Can the android phones die forever this easily? I mean is it really *impossible* to do anything and get it running ever again? It's unbelievable that there's no other way. And I dont think the service center guy would magically turn it on some or the other way as I am 99.99% sure he's not that awesome of a geek.

---

nilanko said:
Thankyou for the suggestions dem0nicbl00d. I have talked to the service center owner and he asked me to come on Monday as tomorrow is a holiday.
Another thing is that, I followed http://forum.xda-developers.com/moto-e/development/unbrick-hard-bricked-moto-e-t2974093 this guide and after doing this, the computer doesn't even detect the phone as qhsusb_bulk anymore. It just shows that an "unknown USB device" is connected. I tried re-following the same guide and re-ran blankflash but now all it shows is "waiting for device" which means that even if I get the required blank flash files, it'll be impossible to flash it as the phone is completely dead.
Is the phone really dead now? I mean can't it ever be switched on again? Can the android phones die forever this easily? I mean is it really *impossible* to do anything and get it running ever again? It's unbelievable that there's no other way. And I dont think the service center guy would magically turn it on some or the other way as I am 99.99% sure he's not that awesome of a geek.
Click to expand...
Click to collapse
Exactly my situation......I don't think they'll try fixing it.........They'll most probably just give u a replacement
And FYI, that guide links to tools that are supposed to be used for Moto G and are also so outdated that they don't work on Lollipop->KitKat downgrade bricks anymore............
Also, if anyone can point me in the direction of the FileFactory folder for Moto E, that would be helpful
---------- Post added at 04:15 PM ---------- Previous post was at 04:08 PM ----------
And @nilanko, it would b awesome if u cud share ur experiences with the service centre guys..............Situations says I won't b able to get the nearest service centre till Friday............

---

Can you go to boot loader???

---

If they provide a replacement, I would say I am the luckiest guy alive-- but alas, I hardly have any hopes.. I don't think that if they send it to the company for replacement, they'd replace it just like that. I don't regret rooting as Moto E is pretty much useless without rooting with its mere 2.1 GB free space it offers.
And by the way, if they do send it to the company, where are they gonna send it? To flipkart? And how long will it take.. I mean how long do I have to forget that I used to have a Moto E before the company says anything? Any idea from your mates who have done the same?

---

nilanko said:
If they provide a replacement, I would say I am the luckiest guy alive-- but alas, I hardly have any hopes.. I don't think that if they send it to the company for replacement, they'd replace it just like that. I don't regret rooting as Moto E is pretty much useless without rooting with its mere 2.1 GB free space it offers.
And by the way, if they do send it to the company, where are they gonna send it? To flipkart? And how long will it take.. I mean how long do I have to forget that I used to have a Moto E before the company says anything? Any idea from your mates who have done the same?
Click to expand...
Click to collapse
No idea but,
faraaz_1998 said:
hey guys
after 2 weeks of struggle of waiting
i finally got my moto g fully working
they replaced the motherboard
free of cost
i would recommend all of u, if u have a moto service center in ur city, state or whatever
go and give ur mobile to them and tell them it wont turn on
if u r in warranty, they will replace ur motherboard
Click to expand...
Click to collapse
(not my buddy....just a random lucky guy)
---------- Post added at 04:27 PM ---------- Previous post was at 04:26 PM ----------
dhruvmu said:
Can you go to boot loader???
Click to expand...
Click to collapse
Nope...........Well, warn whoever u know who owns a Moto E not to downgrade from Lollipop to 4.4.2 and then update to 4.4.4

---

dem0nicbl00d said:
No idea but,
(not my buddy....just a random lucky guy)
---------- Post added at 04:27 PM ---------- Previous post was at 04:26 PM ----------
Nope...........Well, warn whoever u know who owns a Moto E not to downgrade from Lollipop to 4.4.2 and then update to 4.4.4
Click to expand...
Click to collapse
Haha
Well I just did
Was on lollipop
Installed twrp (may be did some mistake) and then my phone stuck at boot animation. No further progress.
Went to boot loader and flashed the stock 4.4.4 firmware and again updated to lollipop.

---

dhruvmu said:
Haha
Well I just did
Was on lollipop
Installed twrp (may be did some mistake) and then my phone stuck at boot animation. No further progress.
Went to boot loader and flashed the stock 4.4.4 firmware and again updated to lollipop.
Click to expand...
Click to collapse
I mean downgrade to stock 4.4.2 factory image and update via 4.4.4 OTA
And can u link me Moto E's FileFactory folder ??

---

dem0nicbl00d, yeah I would tell ya but I am gonna be dead if they return my dead phone back to me. I don't have money neither are my parents going to gimme 1 buck for another phone. Now using Nokia 6030.. I am telling in advance that I'm gonna be actually dead.
dhruvmu, no nothing. Phone does not turn on any more in anyway. I tried all possible combinations of key-pressing-- nothing works. It's totally dead. Not even the computer detects it as qhsusb_bulk anymore. It's just a dead unknown device which even the computer cant communicate with anymore.

---

dem0nicbl00d said:
I mean downgrade to stock 4.4.2 factory image and update via 4.4.4 OTA
And can u link me Moto E's FileFactory folder ??
Click to expand...
Click to collapse
I used this.
http://forum.xda-developers.com/showthread.php?p=56871696
Its stock 4.4.4 Asia retail xt 1022
I think if u can go to boot loader then reverting to KitKat is possible. I just did.

---

dhruvmu said:
I used this.
http://forum.xda-developers.com/showthread.php?p=56871696
Its stock 4.4.4 Asia retail xt 1022
I think if u can go to boot loader then reverting to KitKat is possible. I just did.
Click to expand...
Click to collapse
Wish I'd found this image earlier...............Thanks anyway

---

dem0nicbl00d said:
Wish I'd found this image earlier...............Thanks anyway
Click to expand...
Click to collapse
I think the battery might be down.
Charging it might let u go to boot loader.
I have hard bricked my xperia ion a no of times and recovering it a tough job. Requires full charged battery to go to fastboot which takes 36 to 48 hrs. Notification led helps.
But dont know whether with charging the moto e you will be able to go to boot loader. Never faced anything like this.

---

dhruvmu said:
Can you go to boot loader???
Click to expand...
Click to collapse
dem0nicbl00d said:
I mean downgrade to stock 4.4.2 factory image and update via 4.4.4 OTA
And can u link me Moto E's FileFactory folder ??
Click to expand...
Click to collapse
dem0nicbl00d said:
No idea but,
(not my buddy....just a random lucky guy)
---------- Post added at 04:27 PM ---------- Previous post was at 04:26 PM ----------
Nope...........Well, warn whoever u know who owns a Moto E not to downgrade from Lollipop to 4.4.2 and then update to 4.4.4
Click to expand...
Click to collapse
Thanks for all this. You gave me some hope. But I know I am unlucky. I hope they replace the mobo or something.
I never knew 5.0.2 -> 4.4.2 -> 4.4.4 would lead to the phone's death and would require the hardware to be replaced. This is really weird.

---

nilanko said:
Thanks for all this. You gave me some hope. But I know I am unlucky. I hope they replace the mobo or something.
I never know 5.0.2 -> 4.4.2 -> 4.4.4 will lead to the phone's death and would require the hardware to be replaced. This is really weird.
Click to expand...
Click to collapse
Nothing is wrong with the hardware actually.......If we just had the necessary tools, the fix is just a few clicks away...........Like flash the bootloader, the flash the stock ROM n then voila.........But unfortunately for us, the tools are unavailable
And I'm pretty sure u'd b able to get it replaced for free..............Like that guy.......

---

nilanko said:
Thanks for all this. You gave me some hope. But I know I am unlucky. I hope they replace the mobo or something.
I never know 5.0.2 -> 4.4.2 -> 4.4.4 will lead to the phone's death and would require the hardware to be replaced. This is really weird.
Click to expand...
Click to collapse
Basically it was not 5.0.2 -> 4.4.2 -> 4.4.4 that bricked your device. I remember reading on XDA forums (i don't remember the exact posts) that once you upgrade from 4.4.2 to 4.4.4 you should never try to go back to 4.4.2.

---

wait
One thing can only help u
Waiting till mbm ci 5.0 for moto e is not released
When u downgraded to 4.4.2 I hope u did it without flashimg gptand motoboot
Were there screwn flickering issues
Many moto g owners also bricked their precious while applying ota from 4.4.2 to 4.4.4
So we are waiting for singleimage.mbn
Press thank if I helped

---

panart said:
Basically it was not 5.0.2 -> 4.4.2 -> 4.4.4 that bricked your device. I remember reading on XDA forums (i don't remember the exact posts) that once you upgrade from 4.4.2 to 4.4.4 you should never try to go back to 4.4.2.
Click to expand...
Click to collapse
I did'nt have issues with 4.4.4->4.4.2 except that gpt n motoboot failed to flash..........AFAIK the updated bootloader in Lollipop does not allow the KitKat kernel to boot and like during 4.4.4->4.4.2, does not allow being replaced by an older bootloader version and typically, the phone's bricked...................
---------- Post added at 05:04 PM ---------- Previous post was at 05:01 PM ----------
Brawn_Sg said:
One thing can only help u
Waiting till mbm ci 5.0 for moto e is not released
When u downgraded to 4.4.2 I hope u did it without flashimg gptand motoboot
Were there screwn flickering issues
Many moto g owners also bricked their precious while applying ota from 4.4.2 to 4.4.4
So we are waiting for singleimage.mbn
Press thank if I helped
Click to expand...
Click to collapse
During factory image flashing, I was able to cancel flashing those two........But the 4.4.4 OTA went ahead and did that, typically screwing my phone................I'm just gonna get to the service centre , say my phone just went poof n get a mobo replacement or something
---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------
Brawn_Sg said:
So we are waiting for singleimage.mbn
Click to expand...
Click to collapse
I recall someone telling singleimage can be dumped easily from another phone..........It's the programmer.bin that's missing

---

dem0nicbl00d said:
I did'nt have issues with 4.4.4->4.4.2 except that gpt n motoboot failed to flash..........AFAIK the updated bootloader in Lollipop does not allow the KitKat kernel to boot and like during 4.4.4->4.4.2, does not allow being replaced by an older bootloader version and typically, the phone's bricked...................
Click to expand...
Click to collapse
When i downgraded 5.0.2 (XT1022) to 4.4.4 (XT1021) i got the gpt and motoboot fail but all the rest of commands succeeded and i was back to 4.4.4 without any issues.