[Q] MOTO E (condor) not booting after installing cm12 nightly ???? - Moto E Q&A, Help & Troubleshooting
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
Related
[Q] Cant install recovery or boot in recovery anymore..
I workerd some days before and i dont know what happend. I unlocked my bootloader and did pretty much everything. Ive installed cm12 and everything worked perfectly. Only thing that annoys me was the Cyanogenrecovery that forced me to flash twrp manually after every update. The TWRP App says i got 2.8.4.0 installed. But i cant boot into it. The Led blinks pink and then it goes off and cm starts booting like nothing happend. I tried to reflash the recovery but it did not work. Please help, i just want to update cm and install xposed
xan_asmodi said: To gain a persistent recovery, one needs to flash a recovery to the fota partition as explained here: cant post twrp sirius link here bc xda spam prevent... I figured that it was an error with Infected's CM12 nightlies. I flashed the latest boot.img and I was sorted. Click to expand... Click to collapse this fixed it for me ^^
Can't install stock rom with twrp recovery
So here is my issue. I am unable to install any stock rom on my moto e first gen I have twrp recovery and whenever I put a stock rom on my sd card and try to flash it it shows failed. Currently I have cm 12.1 condor nightly on my moto e and I wanted to install the stock 5.1 rom which has been extracted from the ota updates. I have tried everything I have tried wiping cache and dalvik with data and everything but it still shows field whenever I try to flash stock rom 4.4. 4 Also my phone's usb port is messed up so I cant connect my phone to the computer via usb cable there is no option of using adb unfortunately. Kindly help
kinkymonk said: So here is my issue. I am unable to install any stock rom on my moto e first gen I have twrp recovery and whenever I put a stock rom on my sd card and try to flash it it shows failed. Currently I have cm 12.1 condor nightly on my moto e and I wanted to install the stock 5.1 rom which has been extracted from the ota updates. I have tried everything I have tried wiping cache and dalvik with data and everything but it still shows field whenever I try to flash stock rom 4.4. 4 Also my phone's usb port is messed up so I cant connect my phone to the computer via usb cable there is no option of using adb unfortunately. Kindly help Click to expand... Click to collapse bro are you using the twrp backup files or the files which started with 'blur.condor.....'.zip. you can only flash twrp backup files via twrp . download appropriate twrp backups which are present in general forum/Android development forum and flash it. Good luck.
zeshan94 said: bro are you using the twrp backup files or the files which started with 'blur.condor.....'.zip. you can only flash twrp backup files via twrp . download appropriate twrp backups which are present in general forum/Android development forum and flash it. Good luck. Click to expand... Click to collapse Thanks a lot bro .. you're awesome ..
CM 14 won't Boot. Tried Flashing it multiple times!
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14. Please, if anyone can then PLEASE HELP!
amritanshu.sikdar said: 1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14. Please, if anyone can then PLEASE HELP! Click to expand... Click to collapse Check the bootloader compatibilty of these roms, if they r for the mm bootloader it ll not boot untill u upgrade ur bootloader, check the threads from wer u hv downloaded this...
amritanshu.sikdar said: 1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14. Please, if anyone can then PLEASE HELP! Click to expand... Click to collapse Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Exodusche said: Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue. Click to expand... Click to collapse I already flash the OOS 3, but still this problem continues. File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff Is there any other way how I can manually upgrade my bootloader? That would really help.
amritanshu.sikdar said: I already flash the OOS 3, but still this problem continues. File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff Is there any other way how I can manually upgrade my bootloader? That would really help. Click to expand... Click to collapse check out this thread http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
amritanshu.sikdar said: I already flash the OOS 3, but still this problem continues. File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff Is there any other way how I can manually upgrade my bootloader? That would really help. Click to expand... Click to collapse I use Oxygen_14_OTA_18_all but there's a couple files posted on the bootloader upgrade threads that allow you not too flash the whole firmware just the partions you need to upgrade.
i am having same issue i was on oxygenos 3.1.3 firmware when i started to flash nogut roms every nogut rom works except cm. i flashed official cynogenmod 14.1 thinking that problem must have been solved but it wont boot it just shows oneplus logo. i have waited for 30 minutes but nothing happened if something worked out for you please tell me.
Well I've looked around XDA for soultion and this is it. CM 14 has some Kernel problems, so only what you have to do is just install new kernel as Arsenic or Black Reactor kernel
I was running the new bootloader on cm13 nightlies and couldn't get it to boot either. Even after a full wipe and reflash with v7 gapps Gave up in the end and went back to the last cm13 Nightly
flash arsenic kernel after flashing rom and gapps it will boot. Read the posts in ashwin's official cm 14.1 thread.
Flash Black Reactor (recommended) or Arsenic Kernel.
The zip files that you have for CM are the unofficial ones. So I guess they're from Sarthak Narang. Or at least one of them. Those ROMs require the older bootloader to function. So if you have the newer bootloader, it won't work.
Installing any new cynogenmod/mokee ROM always fails
Hi, I am trying to install cynogenmod or mokee rom and the device always gets stuck at cyno/mokee logo. it never goes beyond that. tried to wait for half an hour(waited for one hour twice). Here is what I am doing: I used TWRP but it wasnt working so i installed CWM, in both the recoveries I was wiping everything except sd card storage as my zip files were in the card. after that i flashed zip files(ROM & GAPPS). after that i rebooted to system. Am I doing it wrong? I am currently on 4.4.4 stock rom. Need help. Thank you.
No one to help?
How can TWRP not work on your device? Install again TWRP via adb.
Flash latest twrp 3.0.2 and try
rian_tama said: How can TWRP not work on your device? Install again TWRP via adb. Click to expand... Click to collapse Rajendran Rasa said: Flash latest twrp 3.0.2 and try Click to expand... Click to collapse The problem wasn't with the recovery and I wasn't doing anything wrong. It was really too bad to know that the rom version I was installing had a bootloop bug in it. So I had tried two previous versions but they too had the same bug. And unfortunately I tried CONTINUOUSLY for two long days to install those same bugged ROMS as if God has put me in frustration mode. Tech fooled me right, lol.
Grab the November 8 version of Cyanogemod. There are issues with the newer updates.
phone not starting after nightly update
i had cm 13 installed in my moto e condor. i did a OTA update of a nightly ( i do not remember the version ) about a month ago but since then it is not booting. it just shows the cyanogen logo on the screen and it goes on and on. i tried the recovery through adb but it is not able to access my sd card where the recovery is installed. am i doing something wrong ??? i am not a technical person but i find rooting and installing custom roms thrilling. it is not my main phone. just a side kick. so not worried too much. but if someone can help may be it will help me in understanding this rooting and installing custom roms process more.
rajesh.rajkot said: i had cm 13 installed in my moto e condor. i did a OTA update of a nightly ( i do not remember the version ) about a month ago but since then it is not booting. it just shows the cyanogen logo on the screen and it goes on and on. i tried the recovery through adb but it is not able to access my sd card where the recovery is installed. am i doing something wrong ??? i am not a technical person but i find rooting and installing custom roms thrilling. it is not my main phone. just a side kick. so not worried too much. but if someone can help may be it will help me in understanding this rooting and installing custom roms process more. Click to expand... Click to collapse CM13 had bootloop bug in last few nightlies. So u better install other ROM or try cm14.1
Ujwal Agrawal said: CM13 had bootloop bug in last few nightlies. So u better install other ROM or try cm14.1 Click to expand... Click to collapse Thanks Ujwal. appreciate your help. but at present it is not accessing my sdcard because of this bug. so nothing happens after i select recovery option in boot loader screen. so i may not be able to flash or clear cache or anything. can you please guide me how to install any newer rom or i might even install the stock cm13 which is still with me and was working fine till i installed the nightly update. please explain me how to install back cm 13 or any newer rom, please.
Could you go to twrp? Have you tried to flash twrp using fastboot?