moto e condor not booting after installing cm12 on the device. i have followed all the correct procedure but the device is stuck at the cm symbol while bootings. It blinks and blinks. I have waited for almost 2 days but no result. Please help!!!
i have not installed gapps in the process could it be the problem?? :crying::crying:
thanks in advance..:good:
pravardhan96 said:
moto e condor not booting after installing cm12 on the device. i have followed all the correct procedure but the device is stuck at the cm symbol while bootings. It blinks and blinks. I have waited for almost 2 days but no result. Please help!!!
i have not installed gapps in the process could it be the problem?? :crying::crying:
thanks in advance..:good:
Click to expand...
Click to collapse
may be that is the problm,again go to recovery format factory reset and then install cm12 and install gapps and then reboot,make sure gapps for lollipop u install
I don't think so. I installed cm12 without gapps worked fine. But still. Try every option u can to restore your phone. Maybe u need to flash gapps for newer version of cm12. Let us know if anything worked for you. Your info coold help others. Good luck mate.
pravardhan96 said:
moto e condor not booting after installing cm12 on the device. i have followed all the correct procedure but the device is stuck at the cm symbol while bootings. It blinks and blinks. I have waited for almost 2 days but no result. Please help!!!
i have not installed gapps in the process could it be the problem?? :crying::crying:
thanks in advance..:good:
Click to expand...
Click to collapse
may be the downloaded file is corrupted while it was downloaded, happened to me also. download the file again and do a 'clean' installation.
flashing gapps have no connection whatsoever with rom installation. :good:
Install CM11, boot it up once, then install CM12+gapps without wiping.
pravardhan96 said:
moto e condor not booting after installing cm12 on the device. i have followed all the correct procedure but the device is stuck at the cm symbol while bootings. It blinks and blinks. I have waited for almost 2 days but no result. Please help!!!
i have not installed gapps in the process could it be the problem?? :crying::crying:
thanks in advance..:good:
Click to expand...
Click to collapse
Flashing a ROM without gapps will not cause any bootloop issue
how ever you can try these two :
1. If you are using the 27th March build, don't use that, there's some problem with that, if you clean flash that zip, it ll result into a bootloop, use the 28th March build instead
2. If you are still facing a bootloop, make sure that you are using the TWRP 2.8.5 version
Sent from my Moto E using XDA Free mobile app
pravardhan96 said:
moto e condor not booting after installing cm12 on the device. i have followed all the correct procedure but the device is stuck at the cm symbol while bootings. It blinks and blinks. I have waited for almost 2 days but no result. Please help!!!
i have not installed gapps in the process could it be the problem?? :crying::crying:
thanks in advance..:good:
Click to expand...
Click to collapse
Hi, first of all, download the latest build, do a clean flash of all partitions, data, system, cache & dalvik, if you don't wanna loose your data make a backup and restore it only when you have booted your device at least once to make sure it boots, and as recommendation flash a custom kernel after verifying the boot, tell us how it goes Luck!
I tried all the options. I installed the latest build. I cleared cache, dalvik cache, factory reset, etc. But no use its always gets the same situation. Due to the bootloop the device was not detected in Pc so I transferred the cm12 zip to external so card and tried installing it from their. Could dis be a problem?? ? This time I also installed gapps. Please help I want my device back:crying:
pravardhan96 said:
I tried all the options. I installed the latest build. I cleared cache, dalvik cache, factory reset, etc. But no use its always gets the same situation. Due to the bootloop the device was not detected in Pc so I transferred the cm12 zip to external so card and tried installing it from their. Could dis be a problem?? ? This time I also installed gapps. Please help I want my device back:crying:
Click to expand...
Click to collapse
re store back to stock rom 4.4.4. do not flash stock 4.4.2
Where can I find the stock rom 4.4.4?? What if I flashed into 4.4.2??
pravardhan96 said:
Where can I find the stock rom 4.4.4?? What if I flashed into 4.4.2??
Click to expand...
Click to collapse
find stock rom 4.4.4 somewhere on xda developer site or google u will get it, if u flash android 4.4.2 and then update to android 4.4.4 through sofware update. ur moto e get potentially bricked because u have unlocked the bootloader, when u update stock rom replace the bootlaoder. then u cannot recover ur loving moto e,,then u have only one option to change the motherboard
pravardhan96 said:
Where can I find the stock rom 4.4.4?? What if I flashed into 4.4.2??[/QU
Click to expand...
Click to collapse
pravardhan96 said:
Where can I find the stock rom 4.4.4?? What if I flashed into 4.4.2??
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-e/development/downgrade-5-0-x-to-4-4-4-stock-firmware-t3031073
This you can do if you have installed soak test via putting it in your sd card or installed via OTA(ie if you have updated your bootloader) and make sure drivers are installed
Hope it helped
I believe I have the same problem. I tried going from stock 4.4.4 to cm12. Tested april 1st and april 2nd builds and I always get stuck in boot screen animation for nearly one hour.
Whenever I install the rom I get the following message "detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system". I used sideload and the external SD.
Will it brick if I try installing CM11 now after a wipe? Will it be considered a downgrade (even if I never properly booted)?
Sorry if it seems I'm hijacking this thread, but I believe we both have the same problem. I necessary I'll create another topic.
Thanks
Sarmatios said:
I believe I have the same problem. I tried going from stock 4.4.4 to cm12. Tested april 1st and april 2nd builds and I always get stuck in boot screen animation for nearly one hour.
Whenever I install the rom I get the following message "detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system". I used sideload and the external SD.
Will it brick if I try installing CM11 now after a wipe? Will it be considered a downgrade (even if I never properly booted)?
Sorry if it seems I'm hijacking this thread, but I believe we both have the same problem. I necessary I'll create another topic.
Thanks
Click to expand...
Click to collapse
no, you can flash cm11, provided you have never flashed the soak test zip anytime before
and about the bootloop, try using the previous version of TWRP, many people have stated that when they tried flashing with the previous version of TWRP it didn't result into bootloop
Hit Thanks if that was helpful
Quick update, with a solution.
Indeed I changed the recovery for TWRP and chose to clean the system in addition to cache, data and dalvik. After that I installed CM12 through sideload and this time it worked fine. Even if I still got the message "detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system".
Hope this helps OP as well!
Hi
Hi Guys, I am facing this problem too and not able to boot and stuck on CM bootlogo. I am using TWRP 2.8.5.0, if any previous version of TWRP solves this issue then please let me know which version of TWRP to be flashed and where to download it from. My device is not is usable condition right now.
MrJukeHardbane said:
Hi Guys, I am facing this problem too and not able to boot and stuck on CM bootlogo. I am using TWRP 2.8.5.0, if any previous version of TWRP solves this issue then please let me know which version of TWRP to be flashed and where to download it from. My device is not is usable condition right now.
Click to expand...
Click to collapse
Try to flash twrp 2.7 version
suresh.anthati said:
Try to flash twrp 2.7 version
Click to expand...
Click to collapse
Flashing 2.7.1.0 is not helping too and still stuck on bootlogo after flashing 03 April cm12 nightly
Sent from my HTCSensation using XDA Premium 4 mobile app
Hi,
I facing the same issue. Roms tested:
cm-12.1-20150411-UNOFFICIAL-condor.zip
cm-12.1-20150412-ROBBIEL811-UBER4.8-condor.zip
cm-12-20150411-NIGHTLY-condor.zip
with recoveries:
twrp2.8.5.0-condor.img
cwm_6051_condor.img
cwm_6050_condor.img
All combinations fail to boot. Tested in CWM with sideload and SD, format all, and nothing.
After all test, still can't boot.
BTW, Bootloader xt1021 5009. Is there any newer version ?
(My MotoG bootloader has to be upgraded to run latest versions)
---------- Post added at 08:12 PM ---------- Previous post was at 07:22 PM ----------
The last option is recover it from paperweight; downgrade to 4.4.4 (RETESALL_XT1021_4.4.4_KXC21.5-40_cid7_CFC.xml.zip)
In fastboot:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot erase cache
fastboot erase userdata
fastboot reboot
After all, is working again, in stock rom.
glococo said:
Hi,
I facing the same issue. Roms tested:
cm-12.1-20150411-UNOFFICIAL-condor.zip
cm-12.1-20150412-ROBBIEL811-UBER4.8-condor.zip
cm-12-20150411-NIGHTLY-condor.zip
...
Click to expand...
Click to collapse
Guys here is my condition
My friend had Xt1022 on stock KK(4.4) so I just unlocked BL and went ahead flashing PA5+,Blisspop,Euporia etc and all were stuck at boot loop. whatever ways i tried It ended up in bootloop for over 20 mins.
I tested on twrp 2.8.5,2.8.6 and always got bootloop.
I fixed it by flashing stock LP and then flashing PA
wipe everything..system,data,cache,dalvik and internal storage also....and before flashing check the md5 of the rom.
Already knew and tried it but all in vain
It Helped
Thanks it Helped to sort my issue to ...atleast now on stock LP would check custom ROMS Further...
hi ..i have a Moto E XT1022 Dual Sim Indian Phone(4.4.4 Kitkat STOCK)
REcently I had unlocked and even rooted my phone by Flashing CWM 6.0.5.0 and Super User 2.46
Later when i tried flashing 5.1 Lollipop! Tried Blisspop then Minimal OS
It seems to Bootloop
I mean that it Stays in Boot Animation and when i press power off it reboots automatically
can some one tell me where i went wrong?OR what i can do to Come out of this Mess!?
POOSIBLE ERRORS I FEEL:
1.)Not installed SDK
2.)not installed Busy Box
benishere said:
hi ..i have a Moto E XT1022 Dual Sim Indian Phone(4.4.4 Kitkat STOCK)
REcently I had unlocked and even rooted my phone by Flashing CWM 6.0.5.0 and Super User 2.46
Later when i tried flashing 5.1 Lollipop! Tried Blisspop then Minimal OS
It seems to Bootloop
I mean that it Stays in Boot Animation and when i press power off it reboots automatically
can some one tell me where i went wrong?OR what i can do to Come out of this Mess!?
POOSIBLE ERRORS I FEEL:
1.)Not installed SDK
2.)not installed Busy Box
Click to expand...
Click to collapse
Well by I know you can't install a Lollipop rom using kitkat on motorola..try flash cm11 or some based rom on KitKat and see if it works Or update your device to soak before change the rom to some lollipop/cm12(.1) based rom.
The first time I launched cyanogenmod after Flashing it, It loaded up fun but when I tried to open browser it would just crashed so I restarted it and now it just keeps restarting over and over, I have tried wiping it and to no avail. Can someone help me please?
Please link to which recovery, which version of the rom and which Gapps you are using.
es0tericcha0s said:
Please link to which recovery, which version of the rom and which Gapps you are using.
Click to expand...
Click to collapse
Alright, Also now it doesn't even boot then reset it just stays at cyanogenmod loading screen.
Recover:
downloadandroidrom . com/file/GalaxyS5/TWRP/openrecovery-twrp-2.7.0.0-klte.tar
Rom:
get . cm/?device=kltespr
I don't have a Gapps flashed.
It's the recovery. It's too old. Doesn't support newer roms. You need 3.2. X I believe.