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
Sorry everyone. I can't post this on the original forum.
I need to know how I can remove this rom and go back to a older rom I installed and backed up via TRMP.
Unfortunately I am having problems with this rom as I have had it installed for over a month now and really can't be used as a daily.
Have changed the kernel to trmp but it only gives / directory with 0 bytes. Cannot mount any other system etc to restore a working rom.
Have tried installing a rooted rom via Flashtool but keep getting errors.
I am trying to avoid wiping the whole phone and start afresh. Any ideas or help would be greatly appreciated.
You can restore your back up via twrp.
fnldstntn said:
You can restore your back up via twrp.
Click to expand...
Click to collapse
I have tried but trwp when in recovery will not recognize any of the other partitions. It can only see / partition. I have also used trwp app. When I reboot into system from trwp it says no system available but will boot into RR rom.
Help me please, I have my Le Max 2 bricked, I got it already with twrp and rom cuoco installed, everything working perfectly when I decided to change the rom and put the small eui, so that during the configuration of the aroma I ended up selecting to clean everything I installed the flashback 1.9, I did the procedures and everything was happening without problems, after installing the twrp of the cuoco I tried to flash the small eui Again and again without success and then things got worse because the device started to stay in bootloop then with the blue led on, so I started to search here in the forum a solution, and I saw the recovery twrp 5.8 teamspain, and I did The installation by fastboot (since it is the only thing I have access to at the moment), and I managed to flash the twrp, I did the reinstall procedure of the cuoco rom, everything was going well and nothing from bootloop until when i I started the system in the part of choosing the language I took a while to make the settings and when I came back it was already the device with the screen erased and with blue led again, already tried to reinstall the rom by flashone and without success, already tried to install the Twrp again and nothing too, I do not know what to do being that I only have the fastboot to try something, can anyone help me? I do not know what to do here in a topic that could extract a rec.img from the zip of eui.58.014s but I do not find this rom for download nor the zip file, if anyone can help me I'll be grateful. Well, I'm giving up hope and sorry for English.
RaphaBraga23 said:
Help me please, I have my Le Max 2 bricked, I got it already with twrp and rom cuoco installed, everything working perfectly when I decided to change the rom and put the small eui, so that during the configuration of the aroma I ended up selecting to clean everything I installed the flashback 1.9, I did the procedures and everything was happening without problems, after installing the twrp of the cuoco I tried to flash the small eui Again and again without success and then things got worse because the device started to stay in bootloop then with the blue led on, so I started to search here in the forum a solution, and I saw the recovery twrp 5.8 teamspain, and I did The installation by fastboot (since it is the only thing I have access to at the moment), and I managed to flash the twrp, I did the reinstall procedure of the cuoco rom, everything was going well and nothing from bootloop until when i I started the system in the part of choosing the language I took a while to make the settings and when I came back it was already the device with the screen erased and with blue led again, already tried to reinstall the rom by flashone and without success, already tried to install the Twrp again and nothing too, I do not know what to do being that I only have the fastboot to try something, can anyone help me? I do not know what to do here in a topic that could extract a rec.img from the zip of eui.58.014s but I do not find this rom for download nor the zip file, if anyone can help me I'll be grateful. Well, I'm giving up hope and sorry for English.
Click to expand...
Click to collapse
Are you able to boot into TWRP recovery again? When you were in TWRP, did you do wipes first before tryin to install a ROM?
Yes I did the wipes, so now I do the twrp flash only that nothing happens, type appears until the installation all right but at the moment of starting the twrp it erases the screen and the blue led
Try EUI or LineageOS that I have linked below. Both are for the x829:
https://drive.google.com/drive/folders/0B_jI7m27ljxhVmtQWmx5NVF3NzA?usp=sharing
It might be helpful if you make of video showing what you are attempting, and what is happening on the screen of your phone too.
You might want to reinstall coco twrp. Also make sure the rom you flash has downloaded fully(that happened to me a few times, corrupt downloads). If rom file is OK it should flash correctly, otherwise you get the blue led
Sent from my Le X829 using Tapatalk
luisoman2000 said:
You might want to reinstall coco twrp. Also make sure the rom you flash has downloaded fully(that happened to me a few times, corrupt downloads). If rom file is OK it should flash correctly, otherwise you get the blue led
Sent from my Le X829 using Tapatalk
Click to expand...
Click to collapse
I have the official version twrp running on my X829. It works flawlessly.
https://twrp.me/devices/leecolemax2.html
Specifically ----------> https://dl.twrp.me/x2/twrp-3.1.1-0-x2.img.html
Hello,
I tried to install FuntouchOS on V30 but after restart I can't access TWRP i tried to reinstall in on PC but sometimes it's not recognizing the phone. After fighting I was able to reinstall TWRP but it's not loading still. I'm thinking also that LG partition is different than default but I'm not sure about that. I don't need original ROM i can get any custom ROM just to use it.
Hopefully someone can help me ?
Thanks for help ?
Snip3rPolska said:
Hello,
I tried to install FuntouchOS on V30 but after restart I can't access TWRP i tried to reinstall in on PC but sometimes it's not recognizing the phone. After fighting I was able to reinstall TWRP but it's not loading still. I'm thinking also that LG partition is different than default but I'm not sure about that. I don't need original ROM i can get any custom ROM just to use it.
Hopefully someone can help me
Thanks for help
Click to expand...
Click to collapse
You should ask this in the FunTouch OS ROM thread.
Yes, you had to create a vendor partition to even install that ROM. If you didn't, then you didn't read the instructions. If you did, then yes now your "LG partition" is definitely different from "default".
Both Funtouch and MUI ROMS are not "regular" ROMs you just install with TWRP, like AOSP or stock-based ROMs. They need vendor partition creation. That means you are willing to experiment with your phone.
ChazzMatt said:
You should ask this in the FunTouch OS ROM thread.
Yes, you had to create a vendor partition to even install that ROM. If you didn't, then you didn't read the instructions. If you did, then yes now your "LG partition" is definitely different from "default".
Both Funtouch and MUI ROMS are not "regular" ROMs you just install with TWRP, like AOSP or stock-based ROMs. They need vendor partition creation. That means you are willing to experiment with your phone.
Click to expand...
Click to collapse
It stuck in TWRP splash and doesn't matter which version I'll install it's not working. Is there any way to fix it ?
Snip3rPolska said:
It stuck in TWRP splash and doesn't matter which version I'll install it's not working. Is there any way to fix it ?
Click to expand...
Click to collapse
I'm going to answer you in the right place.
https://forum.xda-developers.com/showpost.php?p=81521981&postcount=43
I Was on the latest ArrowOS build and I wanted to flash he new DoT OS 5.2. I wanted to switch back but when i installed the new rom the device was stuck in boot animation and it was like that for other 2 roms so i tried to flash stock firmware and the devices boots but if i try to flash any rom the problem reoccurs. What am i doing wrong? I have never had this kind of problem. I use
TWRP 5.2.9.0. Sorry if i didn't give enough information, thnaks for the answer
xBinyWolf said:
I Was on the latest ArrowOS build and I wanted to flash he new DoT OS 5.2. I wanted to switch back but when i installed the new rom the device was stuck in boot animation and it was like that for other 2 roms so i tried to flash stock firmware and the devices boots but if i try to flash any rom the problem reoccurs. What am i doing wrong? I have never had this kind of problem. I use
TWRP 5.2.9.0. Sorry if i didn't give enough information, thnaks for the answer
Click to expand...
Click to collapse
Hello,
You need to format data (not just wipe).
Follow the clean installation guide at my POCO F1 Ultimate Collection & Guides.
Retrial said:
Hello,
You need to format data (not just wipe).
Follow the clean installation guide at my POCO F1 Ultimate Collection & Guides.
Click to expand...
Click to collapse
I already did and found no success, even repaired file system and did that thing of chaning in exfat2 then 4 again. Changing to Orange fox recovery solved my problem. Thank you for the reply.