[ROOT] Rooting the Moto E

Search This thread

sunny4691

Senior Member
Nov 11, 2012
85
35
Well your friend has flashed TWRP successfully...
You can ignore that "mismatched partition size" error...
It occurs due to the TWRP recovery file size being less than 10mb...
You can either ignore this or buffer the recovery size to 10mb...

Hope this helps... :good:
Ok, will see tomorrow if he has got TWRP as his recovery :)

Thanks for your reply.
 

shamps

Senior Member
Jan 25, 2011
978
155
Yup, don't worry he has got TWRP installed...
Browse through this thread (http://xdaforums.com/showthread.php?t=2754486) to know more about this error and see what the OP has posted...
:good:



No probs... Happy to help... :eek:
Hi
I am having problems with flashing twrp or Cwm on my dual sim Moto e.
I have an unlocked bootloader and on 4.4.4 out of the box.
The recovery just doesnt load though it flashes fine.
I have read around and seen people talking about downgrading to 4.4.2 for the recovery to work. But a couple of people have successfully flashed with 4.4.4 as well.
I have followed those threads as well but no success.
Could you please help me with this.
Is it necessary to downgrade?
Thanks in advance.
Btw I have asked this in couple of other threads as well so please dont bash me for asking this at multiple places.

Cheers!!

sent from my Nexus 5
 
G

g33kparineeti

Guest
Hi
I am having problems with flashing twrp or Cwm on my dual sim Moto e.
I have an unlocked bootloader and on 4.4.4 out of the box.
The recovery just doesnt load though it flashes fine.
I have read around and seen people talking about downgrading to 4.4.2 for the recovery to work. But a couple of people have successfully flashed with 4.4.4 as well.
I have followed those threads as well but no success.
Could you please help me with this.
Is it necessary to downgrade?
Thanks in advance.
Btw I have asked this in couple of other threads as well so please dont bash me for asking this at multiple places.

Cheers!!

sent from my Nexus 5


Before flashing TWRP on 4.4.4 firmware, place the SuperSU zip file in your droid's internal storage...
After that flash TWRP and disconnect your device from PC....
Don't boot up your device yet and let it remain in bootloader screen....
After you've successfully disconnected the device from PC, enter TWRP recovery from bootloader and flash the SuperSU zip file...
After that reboot your device and voila, TWRP sticks!!! :cool:

The secret here is to not rebooting the device after flashing TWRP...
You've got to remain in the bootloader screen and only after flashing SuperSU through recovery you may boot the device...

PS: You don't need to downgrade to 4.4.2 at all...

Hope this helps and click the Thanks button if I helped ya... :good:
 

csetera

Senior Member
Feb 27, 2010
197
16
Does anyone have a flashable version of the original recovery? I didn't think that I'd installed TWRP when I rooted. I went ahead and accepted the OTA update, but can't apply it with TWRP. When I reboot, the device then reboots back to recovery again. I figure the easiest solution at this point is to flash original recovery and get the OTA update installed. From there I can re-root if necessary.

---------- Post added at 01:23 PM ---------- Previous post was at 12:25 PM ----------

Never mind... I found it in the FAQ thread and have successfully broken out of my boot loop.

Does anyone have a flashable version of the original recovery? I didn't think that I'd installed TWRP when I rooted. I went ahead and accepted the OTA update, but can't apply it with TWRP. When I reboot, the device then reboots back to recovery again. I figure the easiest solution at this point is to flash original recovery and get the OTA update installed. From there I can re-root if necessary.
 

nilanko

Senior Member
Jun 2, 2014
954
270
New Delhi
I tried booting into TWRP 2.8.5.0 on Moto E condor using:

fastboot boot recovery.img

But it was stuck at the Motorola blue boot logo. What went wrong?
 

smith44

Senior Member
Nov 21, 2011
219
40
Guwahati
to the @op and the moderators I think this thread should not be here as it is not related to development. Its a thread related to guide for rooting the device so I request to move this thread to general section
 

x@n|]er

New member
Jun 25, 2016
1
0
If you first unlock your bootloader, then flash the TWRP recovery image in the original post of this thread, and then flash the SuperSU.zip included in the original post, in that order then you will have root access. If you have any questions feel free to ask.

bootloader unlocked but cannot root says"error cannot load recovery.img" please help

---------- Post added at 05:33 AM ---------- Previous post was at 05:27 AM ----------

bootloader unlocked but cannot root says"error cannot load recovery.img" please help
 

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    Flash TWRP From here

    Flash Chainfire's SuperSu updater from here

    If you don't want to flash the recovery, then you can do these commands instead

    Code:
    adb reboot bootloader
    fastboot boot recovery.img

    This will preserve the original recovery, and root your system
    7
    So what we need now is someone to work on cyanogen mod right

    Sent from my XT1022 using XDA Free mobile app

    I have Slim building atm
    6
    Old root method

    This is purely for historical records

    Note: This method is long winded, and could result in no more booting if done incorrectly

    This method will be replaced with a cleaner, faster method, and is only here as a reference for people who can't wait, or to see how it was initially done

    Note:
    I am not supplying any links to the tools I used (excluding make_ext4fs). This is because this is not a guide for the faint hearted, and if you don't know how to locate the tools yourself, you shouldn't be here.
    This is only for Linux.

    required:
    • The Phone
    • A USB Cable for the Phone
    • ADB
    • Fastboot
    • make_ext4fs (remove .zip off the end)
    • SuperSU update pack

    make a working directory
    Code:
    WORK_DIR="~/moto_e_hacking"
    cd $WORK_DIR

    Fetch the system contents from the phone
    Code:
    adb pull /system system/

    apply the SuperSU pack to the fetched system
    for reference, follow the update-binary contents
    You need to apply all the permissions the same way the update binary does as well

    create a system.img
    Code:
    ./make_ext4fs -a system system.img system/ -l 800M

    flash the system image
    Code:
    adb reboot bootloader
    sudo fastboot flash system system.img

    This should take a few minutes. Ignore the sparse warning.

    once this is done, reboot the phone. You should now have root

    I'm currently building a recovery, so once that is done, we can just flash the update package.
    4
    Is it likely that condor will have an official slim release at some stage?
    Thank you for your work.

    There will be official slim. Working on it as and when I get chance.

    Sent from my Nexus 7 using Tapatalk
    2
    Successfully Rooted! No issues at all.