Bricked? phone: Moto E 2nd gen

dden4012 said:

Last time I used Odin was with the Samsung note 2. I thought it was ONLY for Samsung platform. What am I missing here? Odin works with Motorola as well? I've only seen Odin in reference to Samsung phones.

Click to expand...

You'd be right in that Odin is a Samsung specific app, but it CAN be used to flash ROMs. It can't be used to unlock the bootloader on a non-samsung device.

There are a few other things to try.

1. Bootloader must be unlocked. KingoRoot Android

(a). Download the CWM 6.0.4.9 recovery For MOTO E. this recovery is required temporary for flashing "SuperSU".

(b). So download UPDATE-SuperSU-v2.01.zip

(c). Download the latest TWRP Recovery TWRP 2.7.2.0 V2.2. this will be your new default recovery.

I've tried it for a bit, so far no luck.

I connected the phone via usb to a pc that has all the required drivers in place, and also adb, fastboot etc.

The phone does seem to make a data connection after a while (battery is drained as it keeps boot-looping as long as there is power). As it powers up and starts to boot there is the typical windows sound of usb device connecting, and after a while also disconnecting.

Powering the phone pressing volume-down + power etc does not seem to make a difference at all.

At this point i don't see i can do anything further: there is no way to boot into recovery mode, no way to do a factory reset of any kind, no way to somehow get it to respond to going into any different mode using the usb connection.

Also it does make the windows usb-connected sound at times, but it does not appear as any device after that (not as the phone like it should, not as mass storage or anything at all).

Given how old the phone is there is no warrantee option either, though that probably was not available anymore after rooting the thing using the motorola website in the first place.

Still wondering what caused it all though, the phone worked fine as a rooted device for at least a year, i didn't install any odd new apps or did anything strange to it, but it just went into a coma for no apparent reason after a reboot.

I guess random memory corruption could be an option here, but no way to verify that.