• 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

There is a way to do ADB side load in TWRP but I have never tried nor familiar with the steps to do it
I'm almost 100% positive the last firmware you tried is correct but can't figure out why it's not flashing.

It might be best to get @scary alien or another moderator to move this thread to the forum for your device.
Hopefully there someone with your device and more experience with Motorola than I will be able to get you sorted.
 
OK. I did have access to TWRP at one point but since my first attempt to flash firmware with mfastboot I've been unable to get to TWRP. Whether or not it's still on the phone, I don't know. Got to log off now. My sincere thanks to you.
 
Evidently you were able to get the stock recovery image to flash in your first attempt or the stock recovery did a overwrite on reboot.
Sorry I haven't been much help.
If I come across something that might help, I'll post.
 
Jfalls63 said:
There is a way to do ADB side load in TWRP but I have never tried nor familiar with the steps to do it
I'm almost 100% positive the last firmware you tried is correct but can't figure out why it's not flashing.

It might be best to get @scary alien or another moderator to move this thread to the forum for your device.
Hopefully there someone with your device and more experience with Motorola than I will be able to get you sorted.
Click to expand...
Adb sideload is like this. Go to advanced in TWRP then choose ADB sideload, swipe to start. In cmd type adb devices it should return sideload. Then type sideload then drag the file into CMD and press enter.
 
pooksahib said:
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?
Click to expand...
Where did you get this file? Have you tried the Flash all bat? Something isn't right... Try booting into fastboot then run fastboot getvar all and post what returns in CMD.
 
Last edited:
Sounds an awful lot like the issue I linked in post #24. Minus the relocking of the Bootloader. The solution is presented there.


Excerpt from solution:


However, I have now found a copy of the original Motorola signed firmware for my phone: http://forum.xda-developers.com/showpost.php?p=60448421&postcount=27



I flashed the original system image as described here: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936 (I only needed to re-flash the system image, and I skipped all of the other mfastboot commands listed in that post.)



And I am now able to boot my phone again! Yay!
Click to expand...
 
Last edited:
Hi James L, thanks for helping out. I'm truly amazed by the level of support here. You asked where I got a firmware file – from here:
https://firmware.center/firmware/Motorola/Moto%20E%20%282nd%20gen-2015%29/Stock/XT1524/
'Flash all bat'? No, I haven't tried (not sure what that is). Here's the 'getvar' result:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
flashall Flash boot, system, vendor, and -- if found -- recovery.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing any partition except bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related partitions.
flashing unlock_critical Enables flashing bootloader-related partitions.
flashing get_unlock_ability Queries bootloader to see if the device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can override the fs type and/or size the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <suffix> Sets the active slot. If slots are not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.
options:
-w Erase userdata and cache (and format if supported by partition type).
-u Do not erase partition before formatting.
-s <specific device> Specify a device. For USB, provide either a serial number or path to device port.
or ethernet, provide an address in the form <protocol>:<hostname>[port] where <protocol> is either tcp or udp.
-p <product> Specify product name.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b, --base <base_addr> Specify a custom kernel base address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset. (default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset. (default: 0x01000000)
--tags-offset Specify a custom tags offset. (default: 0x00000100)
-n, --page-size <page size> Specify the nand page size (default: 2048).
-S <size>[K|M|G] Automatically sparse files greater than 'size'. 0 to disable.
--slot <suffix> Specify slot suffix to be used if the device supports slots. This will be added to all partition names that use slots. 'all' can be given to refer to all slots. 'other' can be given to refer to a non-current slot. If this flag is not used, slotted partitions will default to the current active slot.
-a, --set-active[=<suffix>] Sets the active slot. If no suffix is provided, this will default to the value given by --slot. If slots are not supported, this does nothing. This will run after all non-reboot commands.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message.

Hello again Bg260. I've just tried that solution using the firmware suggested by Jfalls63. Two of the commands failed: flash partition gpt.bin and flash bootloader (remote failure). But I kept going and there was one more failure – 'erase customize' (invalid partition name customize). Point of (potential) interest: on this page -
http://techylab.com/1576/fix-bricked-moto-e/
it says 'you will see that there is scrolling text on Device in yellow color'. My phone's screen didn't move at all when I was doing all these cmd entries.

I found this on the web: “the bootloader will not accept firmware that came from a different device model, region, or carrier than the firmware that was originally installed on your phone.” I bought my phone via Amazon. It was posted from within the UK but the seller is registered in Hong Kong. What are my chances of finding the correct firmware? Would the serial number help?

(Are 'firmware', 'ROM' and 'kernel' all the same thing?)
 
Last edited:
You missed a part in your command you typed fastboot getvar it should have been "fastboot getvar all" on my way to work I'll look when i get home.
 
My apologies. Here is the result:
E:\stock + fbootV2>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-80.20
(bootloader) product: surnia (bootloader) board: surnia (bootloader) secure: yes
(bootloader) hwrev: 0x8300 (bootloader) radio: 0x4
(bootloader) emmc: 8GB Micron REV=06 PRV=12 TYPE=17
(bootloader) ram: 1024MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8916 (bootloader) serialno: TA395018X1
(bootloader) cid: 0x0007 (bootloader) channelid: 0x46
(bootloader) uid: 908B1B0F00000000000000000000
(bootloader) unlocked: yes (bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes (bootloader) mot_sst: 3
(bootloader) max-download-size: 268435456
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 353339065301199
(bootloader) meid: (bootloader) date: 12-14-2015
(bootloader) sku: XT1524 (bootloader) battid: SNN5955A
(bootloader) iccid: (bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 30 10:48:44 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/surnia_vfeu/surnia_umts:6
(bootloader) ro.build.fingerprint[1]: .0/MPI24.65-39/23:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.51.39.surnia_vfeu
(bootloader) ro.build.version.full[1]: .vfeuall.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
(bootloader) version-baseband: <not available>
(bootloader) kernel.version[0]: Linux version 3.10.102-r17-g15931b7-0319
(bootloader) kernel.version[1]: 6-g2d22955 (sultan@sprocket) (gcc versio
(bootloader) kernel.version[2]: n 5.3.1 20160113 (Linaro GCC 5.3-2016.02
(bootloader) kernel.version[3]: ) ) #3 SMP PREEMPT Tue Aug 16 23:35:39 E
(bootloader) kernel.version[4]: DT 2016
(bootloader) sbl1.git: git=MBM-NG-V80.20-0-g3812770
(bootloader) rpm.git: git=MBM-NG-V80.20-0-g932f716
(bootloader) tz.git: git=MBM-NG-V80.20-0-ga1c5ae6
(bootloader) hyp.git: git=MBM-NG-V80.20-0-ga1c5ae6
(bootloader) aboot.git: git=MBM-NG-V80.20-0-g76fb222
(bootloader) partition-type:modem: raw (bootloader) partition-type:sbl1: raw
(bootloader) partition-type:DDR: raw (bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw (bootloader) partition-type:tz: raw
(bootloader) partition-type:hyp: raw (bootloader) partition-type:utags: raw
(bootloader) partition-type:logs: raw (bootloader) partition-type:sec: raw
(bootloader) partition-type:factorytune1: raw (bootloader) partition-type:padA: raw
(bootloader) partition-type:metadata: raw (bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw (bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:utagsBackup: raw (bootloader) partition-type:hypBackup: raw
(bootloader) partition-type:padB: raw (bootloader) partition-type:frp: raw
(bootloader) partition-type:modemst1: raw (bootloader) partition-type:modemst2: raw
(bootloader) partition-type:hob: raw (bootloader) partition-type:dhob: raw
(bootloader) partition-type:fsg: raw (bootloader) partition-type:fsc: raw
(bootloader) partition-type:ssd: raw (bootloader) partition-type:cid: raw
(bootloader) partition-type:logo: raw (bootloader) partition-type:clogo: raw
(bootloader) partition-type:persist: raw (bootloader) partition-type:misc: raw
(bootloader) partition-type:boot: raw (bootloader) partition-type:recovery: raw
(bootloader) partition-type:factorytune2: raw (bootloader) partition-type:kpan: raw
(bootloader) partition-type:padC: raw (bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw (bootloader) partition-type:oem: raw
(bootloader) partition-type:carrier: ext4 (bootloader) partition-type:system: raw
(bootloader) partition-type:cache: raw (bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x0000000004000000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-size:DDR: 0x0000000000008000
(bootloader) partition-size:aboot: 0x0000000000100000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000007d000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:sec: 0x0000000000004000
(bootloader) partition-size:factorytune1: 0x0000000000371000
(bootloader) partition-size:padA: 0x00000000001af000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:abootBackup: 0x0000000000100000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000007d000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-size:padB: 0x000000000048f000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000180000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:logo: 0x0000000000400000
(bootloader) partition-size:clogo: 0x0000000000400000
(bootloader) partition-size:persist: 0x0000000000800000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-size:boot: 0x0000000002000000
(bootloader) partition-size:recovery: 0x0000000001ffc000
(bootloader) partition-size:factorytune2: 0x0000000000a0e000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:padC: 0x0000000000380000
(bootloader) partition-size:sp: 0x0000000001000000
(bootloader) partition-size:keystore: 0x0000000001000000
(bootloader) partition-size:oem: 0x0000000001000000
(bootloader) partition-size:carrier: 0x0000000001000000
(bootloader) partition-size:system: 0x0000000071000000
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-size:userdata: 0x000000013ffe0000
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (75)
(bootloader) ro.carrier: vfgb
all: listed above
 
That's the one I took. Commands went OK bar one ('invalid partition name customize' - don't think it's a problem) and phone is now doing that 'hand stitched by Peter Crawley' thing. Let's see how long this takes...
 
Success! I'm chuffed.. My sincere thanks to all of you, I really can't believe how helpful you are. I'm not done asking questions, though - I take it the phone is still unlocked but how do I check? And what about 'rooted' (the object of the exercise in the first place) - I take it I need to begin that process again?
 
The web tells me to run 'fastboot oem device-info' but, now that the phone's in working mode, it no longer shows up in 'fastboot devices'. Why would that be?
 
Yes, you are still both Sim and bootloader unlocked.
Glad it worked!
You are on Android 6.0 so different root method may be needed.
You can go systemless root or probably traditional.
The main thing to do, once you flash TWRP recovery and before you do anything else, is to make a stock backup. Copy it to your pc for safe keeping.
I'll have a look at what root methods are available.
 
FYI:

E:\stock + fbootV2>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-80.20
(bootloader) product: surnia (bootloader) board: surnia (bootloader) secure: yes
(bootloader) hwrev: 0x8300 (bootloader) radio: 0x4
(bootloader) emmc: 8GB Micron REV=06 PRV=12 TYPE=17
(bootloader) ram: 1024MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8916 (bootloader) serialno: TA395018X1
(bootloader) cid: 0x0007 (bootloader) channelid: 0x46
(bootloader) uid: 908B1B0F00000000000000000000
(bootloader) unlocked: yes (bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes (bootloader) mot_sst: 3
:
:​

You should also be able to do:

fastboot getvar unlocked​

to just display the status/value of the unlocked variable

(don't forget fastboot only works when your device is in fastboot/bootloader mode)

:)
 
You must log in or register to reply here.
Back
Top Bottom