When I turn my Moto E on it automatically goes into the Fastboot Flash Mode. It says it is unlocked status code 3.
I tried to go to recovery mode it just flashes the "warning bootloader unlocked" screen.
The Bootloader logs say:
"Fastboot Reason: Fall-through from recovery boot mode
Boot up failed"
I don't know why this is happening but my phone is unusable.
Please look into this
Well the good news is that it still boots into fastboot mode right:fingers-crossed:
Did it just suddenly start behaving this way or did a flash go bad? Also, what rom/kernel were you using on what phone? xt1527?
I'd try flashing or booting a compatible recovery in fastboot and work from there, it seems your recovery is broken anyway.
The phones bootloader was unlocked and I reset my phone and tried to downloaded the system update on the phone. When the phone restarted from the update it got stuck on the "no command" screen. Then i tried to install the TWRP_2.8.0.1_Titan_v2.img. From there it got stuck on the fastboot mode.
battle_hardened said:
Well the good news is that it still boots into fastboot mode right:fingers-crossed:
Did it just suddenly start behaving this way or did a flash go bad? Also, what rom/kernel were you using on what phone? xt1527?
I'd try flashing or booting a compatible recovery in fastboot and work from there, it seems your recovery is broken anyway.
Click to expand...
Click to collapse
I got TWRP recovery working but what rom can I flash?
Dominikk7 said:
I got TWRP recovery working but what rom can I flash?
Click to expand...
Click to collapse
I personally like cm13 with squid kernel
http://forum.xda-developers.com/moto-e-2015/orig-development/rom-cyanogenmod-13-moto-e-lte-t3329100
Hey guys,
I agree the Squid Kernel runs smooth on the XT1527. I've had this device unlocked and rooted for 6 months. In that time I have probably tested every compatible ROM, Kernel, Gapp package, framework MOD etc. that Google can find which has helped me discover my xt1527's 'Habitable' zone so to speak.
I've got a few personal favorites and reliable standbys but its all dictated by how the device responds to the changes I force on it. And (mine anyway) seems to respond better to the Surnia Specific Roms, Kernels and Recoveries.
Viva la Moto E!
XT1527 unlocked and rooted.
Recovery = Squid's TWRP 3.0.2 r1
Rom = ResurrectionRemix v5.7.2 (now maintained by vatsal with weeklies and nightlys)
Gapp pack. = Banks Dynamic Gapps
Kernel = (switched almost daily as per required effect. I.e. longer battery life or straight performance)
Sent from my XT1527 using XDA-Developers mobile app
Related
I Unlocked the bootloader 3 days ago and flashed Cyanogenmod 12.1 with exact gapps and was able to use the phone perfectly ,today I searched for xposed and found that it could be only installed by manual flashing for android lollipop , so I downloaded the zip file and rebooted my phone in Recovery Mode [ TWRP ] and flashed the zip file just after that the phone stuck at bootloop. Restarted the phone 3 time's but no luck so finally I got into bootloader by pressing the volume down button and the power button and opened recovery mode to factory reset the phone and reflashed the CM 12.1 with gapps , now the problem begin's when I restarted the phone it is stuck at "Warning Bootloader Unlocked" and even the recovery mode is stuck at beginning screen of twrp , Im only able to use the bootloader . Even tried to reflash TWRP Recovery from computer but thier's no change it is still stuck at the recovery screen .
Any help would be really appreciated
try reflashing and then wiping cache's before rebooting ?
like the regular cache and dalvik cache.
also don't expect the first boot to work quick.. leave it for a long time...
good luck.
Actully the problem is , when i try to open recovery mode it stucks at teamwin logo (twrp)
"I searched for xposed and found that it could be only installed by manual flashing for android lollipop"
Click to expand...
Click to collapse
that quote is confusing.. what did you mean exactly.
What TWRP ? From Where + what version # ?
If i were you i would re-download it then MD5 hash it.. verify it !
I always check the md5 hashes on any phone roms or firmware etc.
I have had tons of incomplete downloads and there is nothing wrong with my internet connection either.
The more detailed you can be the more likely someone can help.
Once you are positive your TWRP is downloaded properly if i were you
i would re-flash it with fastboot. (if you can)
Can you power off the phone and put it in bootloader mode then connect to pc ?
power it off then hold volume down + power then plug in USB
then right click the empty space in the windows folder (assuming no Linux)
select open command prompt here then type:
adb devices
Is it listed ?
I also assumed you have "Minimal ADB and Fastboot" installed.
Sounds like you flashed a 5.1 firmware package ?
yes ? which one ?
And watch out many sites have cut off my download on me while downloading them.
and if you then flashed a half completed download you could prob damage the phone.
for checking hashes on windows i use HashSlash.. it's clean / free and has a GUI ..google it
Basically , first I flashed Android 5.1.1 AOSP for my device and then Cyanogenmod 12.1 Nightly Surnia . and yes I tried to reflash TWRP Recovery but it is stuck at the same Teamwin Logo screen , and i flashed the latest version of twrp which was available on xda . Can you provide me worth some kind of image file which I can flash to Factory reset my device from computer or anything else which can help.
And by the way Thanks for the quick reply
sabungolfer0011 said:
Basically , first I flashed Android 5.1.1 AOSP for my device and then Cyanogenmod 12.1 Nightly Surnia . and yes I tried to reflash TWRP Recovery but it is stuck at the same Teamwin Logo screen , and i flashed the latest version of twrp which was available on xda . Can you provide me worth some kind of image file which I can flash to Factory reset my device from computer or anything else which can help.
And by the way Thanks for the quick reply
Click to expand...
Click to collapse
https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
i used that.. but didn't flash my phone yet.
that is all firmware packages stock for Moto-2015
You still have not mentioned a lot like where did you get TWRP and what version ?
What carrier is your phone ?
I take it you unlocked the bootloader or did you get it like that ?
I'm guessing the bootloader loads TWRP
so either of those is probably damaged i bet.
I would try and get it stock then work from there getting TWRP back on and rooting etc.
What i was trying to ask you is..
Was your phone on 5.02 and you tried to update it to v5.1 ?
Because i have seen other people here who had problems with that.
Relocking the bootloader can cause problems and so can reverting to an old ver from 5.1 to 5.02
I used a custom kernel and TWRP from Squid here on the forum and rooted
and his kernel is only good for me up to version 5 but he has way newer versions out..
but they are only for users who updated to 5.1
So you have to be VERY careful what your doing.
I might have screwed up my phone if i didn't notice the fine print.
Also just search the forum for some guides on flashing firmware
and verify the downloads
My Bootloader is unlocked , TWRP Recovery Version 2.8.6.0 . My phone was on Android 5.0.2 [ Official Non Rooted ] , so I thought of updating it to 5.1.1 which was available as custom rom So I unlocked the bootloader flashed TWRP version 2.8.6.0 by copying Recovery.img in minimal adb folder and oped CMD and flashed the custom recory and it was no problem , then 2 days ago I flashed Cyanogenmod.12.1.Surnia.20150829.zip and it worked fine no issues then I flashed Xposed Modular in recovery mode , now when I tried to restart the system it stuck at bootloop so I entered Bootloader and again restarted 2, 3 times but no luck so I again entered bootloader and entered Recovery Mode ( TWRP 2.8.6.0) and wiped all my data , But unfortunately I was outside so I dint had the firmware and gapps so I switched the phone off in hope that ill flash the firmware and gapps when i reach back home . So when I vame back home and pasted the firmware and gapps in memory card and inserted it baxk in the phone and tried to enter recovery mode , that was the first time when I experied That teamwork logo stuck at recover mode and the further story you laready know
so.. i have an Lg d618 rooted and running official L 5.0.2
i wanted to flash a custom recovery so i started with patching bootloader using this thread
http://forum.xda-developers.com/g2-mini/development/bootloader-d620-d618-t3127819
then i installed TWRP using this thread
http://forum.xda-developers.com/g2-mini/development/recovery-lg-g2-mini-d618-v10c-t2854493
by flashing the img file with Flashify
the the phone rebooted and i got the TWRP interface
http://img.wonderhowto.com/img/39/2...only-custom-recovery-youll-ever-need.w654.jpg
and when i press reboot i got this
http://img.wonderhowto.com/img/38/1...only-custom-recovery-youll-ever-need.w654.jpg
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I got that android logo like i have no recovery installed
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
i tried this solution http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/ and it didn't help
dibik said:
so.. i have an Lg d618 rooted and running official L 5.0.2
i wanted to flash a custom recovery so i started with patching bootloader using this thread
http://forum.xda-developers.com/g2-mini/development/bootloader-d620-d618-t3127819
then i installed TWRP using this thread
http://forum.xda-developers.com/g2-mini/development/recovery-lg-g2-mini-d618-v10c-t2854493
by flashing the img file with Flashify
the the phone rebooted and i got the TWRP interface
http://img.wonderhowto.com/img/39/2...only-custom-recovery-youll-ever-need.w654.jpg
and when i press reboot i got this
http://img.wonderhowto.com/img/38/1...only-custom-recovery-youll-ever-need.w654.jpg
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I got that android logo like i have no recovery installed
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
i tried this solution http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/ and it didn't help
Click to expand...
Click to collapse
Followed you from the other spot...
It sounds like Flashify plunked recovery on your boot/kernel partition (assuming your recovery you described is still stock - that is - Andy laying down with the front panel open). So, I would suggest to ADB push your official L 5.0.2 boot.img while in TWRP and flash that (to boot), and you should be golden.
Also, from my perspective it's hard for me to say your bootloader is acting up, as I have a different LG device and it's bootloader does not have fastboot. It's front-end is only a shim that makes you factory reset to get into recovery mode (it's only function).
Hope this helps.
OfficerJimLahey said:
Followed you from the other spot...
It sounds like Flashify plunked recovery on your boot/kernel partition (assuming your recovery you described is still stock - that is - Andy laying down with the front panel open). So, I would suggest to ADB push your official L 5.0.2 boot.img while in TWRP and flash that (to boot), and you should be golden.
Also, from my perspective it's hard for me to say your bootloader is acting up, as I have a different LG device and it's bootloader does not have fastboot. It's front-end is only a shim that makes you factory reset to get into recovery mode (it's only function).
Hope this helps.
Click to expand...
Click to collapse
thank you Jim for the reply
well my problem is solved.. i just flashed my device with the Official KDZ file using LG flash tool in "normal flash mode not CSE"
my phone turned on normally and everything (apps, pictures, files, messages.... ) and all my data were still there so i did'nt loose a thing
i just lost the root acces and that won't be a prblm cause i can root it all over again
thanks again Jim ^^
dibik said:
thank you Jim for the reply
well my problem is solved.. i just flashed my device with the Official KDZ file using LG flash tool in "normal flash mode not CSE"
my phone turned on normally and everything (apps, pictures, files, messages.... ) and all my data were still there so i did'nt loose a thing
i just lost the root acces and that won't be a prblm cause i can root it all over again
thanks again Jim ^^
Click to expand...
Click to collapse
Did you still have TWRP installed after flashing the KDZ file normal mode? Is your bootloader still unlocked?
ShadowBlade_20 said:
Did you still have TWRP installed after flashing the KDZ file normal mode? Is your bootloader still unlocked?
Click to expand...
Click to collapse
no i didn't
i re-unlocked the bootloader and installed TWRP 2.8.7.0 and it worked like a charm and now i'm on CM 13
Having sanw problem. Been stuck here on att lg gflex for 3 months. Can u help me please? [email protected]
Sent from my C6740N using Tapatalk
i have moto e2 xt1506 ...i tried to update it manually but instead i think i downgraded it....lol
now my device wont boot up its just showing boot menu....i clicked everything Normal powerup, Recovery, Factory but still its showing that menu again...
version downgraded for boot..
failed to validate boot image
fastboot reason : fall-through from normal boot mode
i think my ROM is busted...any solution to this? anyone?
rootedmind said:
i have moto e2 xt1506 ...i tried to update it manually but instead i think i downgraded it....lol
now my device wont boot up its just showing boot menu....i clicked everything Normal powerup, Recovery, Factory but still its showing that menu again...
version downgraded for boot..
failed to validate boot image
fastboot reason : fall-through from normal boot mode
i think my ROM is busted...any solution to this? anyone?
Click to expand...
Click to collapse
Idk why are you on 5.0
Anyways, get minimal fastboot and adb.
Flash twrp recovery built for Otus (Don't flash for surnia!)
That's it! Now you have an arsenal of ROMs! I use resurrection remix. Provides immence customization. But that's your choice. If you want simple and stock, AOSP is there. Resurrection for customization... Use CyanogenMod for having something in between customization and simple . all links can be found in the Original Android development section.
Happy Flashing!
PseudoDev said:
Idk why are you on 5.0
Anyways, get minimal fastboot and adb.
Flash twrp recovery built for Otus (Don't flash for surnia!)
That's it! Now you have an arsenal of ROMs! I use resurrection remix. Provides immence customization. But that's your choice. If you want simple and stock, AOSP is there. Resurrection for customization... Use CyanogenMod for having something in between customization and simple . all links can be found in the Original Android development section.
Happy Flashing!
Click to expand...
Click to collapse
thnx for reply some how i manged to make it to stock os...but as you suggested i will try to flash with others ROMs as well...:good:
Unfortunately Google Play Services Has Stopped Error
rootedmind said:
thnx for reply some how i manged to make it to stock os...but as you suggested i will try to flash with others ROMs as well...:good:
Click to expand...
Click to collapse
hey hi i flashed moto otus with cm-13.0-20160621-NIGHTLY-otus.zip ( 2016-06-21 ) and gapps after that.
after update i got Unfortunately Setup wizard Has Stopped Error...i managed to stop it but now i am getting Unfortunately Google Play Services Has Stopped Error this.
have you got any such error?
any solution? anyone?
hiiii alll..
Recently my moto E 1st generation mobile android os has crashed. I have given in mobile repair shop and they are telling that its not accepting software. always showing moto symbol itself when it restarted. could anyone tell me how to recover the os or reinstall
note: my mobile is not rooted.
even can i install android version.... please respond
Yes definately you can install android
Just root your phone and install custom recovey like twrp and then install any custom rom which can be downloaded from xda
It's easy
I repaired a non-rooted moto e with the same problem. you have to check your phone goes into fastboot mode (switch off the phone, press volume down + power button for 10 secs). Then you have to unlock the bootloader, install twrp and flash whichever os u want . For unlocking bootloader and installing twrp there are so many threads in xda
vinithv said:
I repaired a non-rooted moto e with the same problem. you have to check your phone goes into fastboot mode (switch off the phone, press volume down + power button for 10 secs). Then you have to unlock the bootloader, install twrp and flash whichever os u want . For unlocking bootloader and installing twrp there are so many threads in xda
Click to expand...
Click to collapse
brother i can boot the image (recovery file) but it boots in a endless showing MOTO logo and nothing happens , unable to flash anything can you help ??
Harry_00s.HS said:
brother i can boot the image (recovery file) but it boots in a endless showing MOTO logo and nothing happens , unable to flash anything can you help ??
Click to expand...
Click to collapse
Try flashing stock rom from this thread http://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
vinithv said:
Try flashing stock rom from this thread http://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
Click to expand...
Click to collapse
how can i flash when i am not able to boot to twrp .... i get lot's of errors in stock recovery , also i am not able to flash stock rom via cmd
Harry_00s.HS said:
how can i flash when i am not able to boot to twrp .... i get lot's of errors in stock recovery , also i am not able to flash stock rom via cmd
Click to expand...
Click to collapse
have you unlocked your bootloader ?was it successful ?
vinithv said:
have you unlocked your bootloader ?was it successful ?
Click to expand...
Click to collapse
Bootloader was unlocked i guess , yes bootloader is unlocked cuz last time when i saw my phone turning on it said that bootloader unlock warning means the Bootloader is unlocked
it started with calyxOS then i tried Paranoid Andriod and now i am trying RiceDriod.
Specifically it happens trying to go into recovery mode to install updates via adb sideloading but it just takes me to the google screen then the "your devices bootloader is unlocked" warning.
I just flashed stock using andriod flash tools and it worked fine. not sure why it wont work for the others.
catcatjpg said:
it started with calyxOS then i tried Paranoid Andriod and now i am trying RiceDriod.
Specifically it happens trying to go into recovery mode to install updates via adb sideloading but it just takes me to the google screen then the "your devices bootloader is unlocked" warning.
I just flashed stock using andriod flash tools and it worked fine. not sure why it wont work for the others.
Click to expand...
Click to collapse
You have to flash a custom recovery so that you can flash custom ROMs.
Lineage OS has a up to date collection for device specific recoveries. However, you have to check the compatibility of them with the ROM you are intended to flash.
You should read the OP of that ROM more carefully regarding the compatibility issue.
aimsjahan said:
You have to flash a custom recovery so that you can flash custom ROMs.
Lineage OS has a up to date collection for device specific recoveries. However, you have to check the compatibility of them with the ROM you are intended to flash.
You should read the OP of that ROM more carefully regarding the compatibility issue.
Click to expand...
Click to collapse
I do flash the custom recovery so I can flash the ROM. I never had an issue before but now I do even though I have done everything correctly.
How do I clear cashe partition and dalvik cashe? The rest of the steps I have done but have not worked unfortunately. even with the different roms.
Do you have a visual of this? Pixel 6 does not have a physical home button when powered off haha. It would also help just for better understanding what to do
nothings working so far guess ill stick with graphene until i get a new phone or a solution pops up
catcatjpg said:
Do you have a visual of this? Pixel 6 does not have a physical home button when powered off haha. It would also help just for better understanding what to do
Click to expand...
Click to collapse
To manually boot recovery on a custom rom just hold power button down , keep holding it down and once your screen goes black hold volume down till you are in bootloader/fastboot mode, then use volume to select recovery and hit power. That should get you in recovery on custom roms. Or you can plug in to a PC with adb and enable USB debugging and dev options on device, disable screen lock and type: sudo adb devices (for Linux ) and when the box pops up on your phone check mark it really quick. Now your device can have commands sent to it. If on a custom rom from cli type: sudo adb reboot recovery or sudo adb reboot bootloader then use volume keys to go to recovery and power to select it.
The best way to get out of a bootloop is hold power and volume down until you are in bootloader/aka fastboot mode then execute the ./flash-all.sh script that's in factory image and let it flash and wipe your device. You can always sideload a rom again but the factory image script will get everything to normal. There are tons of videos on YouTube about flashing device's. Everything changed a few years ago when Google started making android A/B partition devices but if you check out YouTube just do a quick search for whatever it is and more than likely you'll find what you're looking for there. Lots of pixel 6 videos!!!
Please explain your "exact " installation technique step by step. The more details the better the answers you'll get. What rom are you installing and exact steps you are doing to get in a boot loop.. While there are some highly intelligent people here nobody can read minds. Every detail helps to get a solution that works. Must be specific.. For me I rarely have issues but i don't flash nearly as often as I used to but when I have had a loop I hold power and volume down then from bootloader screen plug up to PC and I flash factory image using the flash-all.sh script that comes in factory image. Check out YouTube for visuals. Lots of good videos there.
This will hopefully provide more information on my situation
Currently I am trying to install RiceDroid for the pixel 6.
How I am in stalling it is I extract the images from the payload bin using a guide. Get the vendor boot image. Flash it with 'fastboot flash vendor_boot 'path/to/vendor_boot.img' then I try to boot into recovery which doesn't work it loads into the the warning screen then to the Google boot up screen but I never get to the Andriod 'no command' screen I only get taken back to the warning screen then back to the boot screen again untill I manually boot into bootloader again (power button and volume down) and flash my stock firmware.
Other Roms are not working for me either and it started happening after I tried to flash calyxOS and that failed. Now I can't even flash lineageOS or Evolution X rom only web flashing with GrapheneOS and Android Flash Tool can successfully flash my device.
im not sure what i did but things are working again