• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Moto e root problem: stuck on warning screen

P

pooksahib

Member
Hi. Rooting is new to me so please be gentle. I have the Moto e 2nd Gen LTE 4G. I was following this video:
http://www.xda-developers.com/how-to...loader-xda-tv/
and thought I was doing well but came unstuck after completing the 'unlock'.
I then followed this page:
http://www.howtogeek.com/115297/how-...might-want-to/
Flashing the SuperSU zip went OK. "Wipe cache/Dalvik" went OK. However, "Reboot System" has left me on the 'WARNING BOOTLOADER UNLOCKED" screen. It's now been 45 minutes. Surely that's too long? If so, can you tell me the cause and cure?

Update: The only usable screen I can get is TWRP. I've transferred 3 zip files onto the phones' storage – logo, squid-kernel and SuperSU. TWRP gave me 'success' messages for flashing the latter two but 'logo' failed. A pity, as that's the one that's supposed to remove the 'warning bootloader unlocked' screen.

I just can't find a way to get the phone to a screen where I can check the installed apps etc etc. Any help offered would be really appreciated.
 
Hi Bg260. Bad news – things are worse. Inside my 'Minimal ADB and Fastboot' folder, I also have the extracted files from 'mfastboot-v2.zip' and 'XT1524_RETEUALL_MOTOE2(4G-LTE)_5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml.zip' (stock firmware).

I then executed these commands (with a view to flashing stock firmware):

mfastboot devices
mfastboot erase boot boot.img
mfastboot erase recovery recovery.img
mfastboot erase system system.img_sparsechunk.0
mfastboot erase system system.img_sparsechunk.1
mfastboot erase system system.img_sparsechunk.2
mfastboot erase modem NON-HLOS.bin
mfastboot erase fsg fsg.mbn

mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot reboot system

Most went fine but a couple of commands gave me a 'not enough memory' message. At the end of it, nothing on the phone had changed. However, selecting 'Recovery' no longer takes me to TWRP. Instead, I get a picture of the android on his back with a red exclamation mark triangle over his guts. Doesn't look good...
 
These are the latest mfastboot commands I could find.
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash boot boot.img
mfastboot flash logo logo.bin
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot oem fb_mode_clear
mfastboot reboot

Some of the commands you may not need depending on what is in you firmware download.
 
Last edited:
Jfalls63 said:
At the screen with the Android on his back, press and hold power and tap the volume up and see if it takes you to the recovery screen.
Click to expand...
I'm on a screen not seen before. I'm being given the option of 'reboot system now', 'apply update from SD card (I have no card)', 'apply update from adb', 'wipe data/factory reset', 'wipe cache partition', reboot to bootloader', 'power down' or 'view recovery logs'.
Foot of screen (in yellow) says 'qe 0/0'. What to do?
 
Just a second after choosing 'reboot system' I'm back in the screen where you have all those options in the pale green box (barcodes, BP tools etc). A reboot can't have been that quick, can it? Choosing 'Recovery' still gives me the dead android/red triangle.
 
Last edited:
Yes (in the screen with barcodes/BP tools etc). (Is that what's known as fastboot?) Choosing 'start' showed me the 'warning bootloader unlocked' screen for a few seconds and then back to the screen where I chose 'start' in the first place. Seems I'm in a loop. Some other options in this screen are Restart Bootloader or Factory Mode.
 
I think you will either have to try flashing the stock firmware again in fastboot or flash TWRP recovery image then a custom rom in TWRP.

Does the firmware download you have contain a XML or service file?
 
Thanks. I now have RSDLite6.2.4.msi. But - and I'm sorry - could you tell me exactly what to do with it?
IGNORE, think I have it sussed. Tried to flash both xml files - both failed.
 
Last edited:
Also on your firmware, make sure that you have the latest released version. Sometimes trying to downgrade to a early version causes problems.
 
pooksahib said:
Thanks. I now have RSDLite6.2.4.msi. But - and I'm sorry - could you tell me exactly what to do with it?
Click to expand...
Open RSDlite and connect phone to pc in fastboot mode and see if your device is detected. If yes, choose file and see if you can locate one of the XML files and hit start.
 
Thanks but see above. Firmware I'm trying is "XT1524_RETEUALL_MOTOE2(4G-LTE)_5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml". Best way/place to find latest version?
 
Actually, I don't think RSDLite IS seeing my phone (I just saw the word 'connected' but no actual phone details are shown). How to fix this?
rsd.jpg
 
You must log in or register to reply here.
Back
Top Bottom