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
i am having problem while flashing gapps with latest cm13 via cyanogenmod ... i have downloaded latest open gapps and even the latest custom os ... problem arises when i flash gapps .. after the installation of gapps when i reboot my phone .. it shows installing 101 files .. thats okay .. but when it finishes installing them .. it installs google framework ... suddenly it restarts the installation of 101 apps .. this process repeats on till i switch off my phone manually
help me with it .. urgently
Thanks
vjstar7 said:
i am having problem while flashing gapps with latest cm13 via cyanogenmod ... i have downloaded latest open gapps and even the latest custom os ... problem arises when i flash gapps .. after the installation of gapps when i reboot my phone .. it shows installing 101 files .. thats okay .. but when it finishes installing them .. it installs google framework ... suddenly it restarts the installation of 101 apps .. this process repeats on till i switch off my phone manually
help me with it .. urgently
Thanks
Click to expand...
Click to collapse
Yep, I got the same problem, anyone????
Instructions
Hello and thank you for using Q/A,
Download:
cm-13.0-20160210-NIGHTLY-i9300.zip
Slim_zero_gapps.BETA.6.0.build.0.x-20160210-1513.zip
Move both files to you S3. Wipe:
Code:
[LIST]
[*]data
[*]cache
[*]dalvik-cache
[*]system
[/LIST]
Then flash both files.
It didnt work, but I found out what was wrong, my custom recovery, changed it and it worked.
custom recovery ?? cm 12.1 is working fine ... this problem is with cm13 only
mousemeat said:
It didnt work, but I found out what was wrong, my custom recovery, changed it and it worked.
Click to expand...
Click to collapse
custom recovery ?? cm 12.1 is working fine ... this problem is with cm13 only
vjstar7 said:
i am having problem while flashing gapps with latest cm13 via cyanogenmod ... i have downloaded latest open gapps and even the latest custom os ... problem arises when i flash gapps .. after the installation of gapps when i reboot my phone .. it shows installing 101 files .. thats okay .. but when it finishes installing them .. it installs google framework ... suddenly it restarts the installation of 101 apps .. this process repeats on till i switch off my phone manually
help me with it .. urgently
Thanks
Click to expand...
Click to collapse
I used here the Benzo Gapps and work perfectly.
do u tried installing open gapps ??
Leojrk said:
I used here the Benzo Gapps and work perfectly.
Click to expand...
Click to collapse
do u tried installing open gapps and got same problem ??????
vjstar7 said:
do u tried installing open gapps and got same problem ??????
Click to expand...
Click to collapse
Yes, then I did a full wipe, flash the cm and flash the benzo gapps, now its work normally.
OBS: I tried the Pico, Nano and Stock Open gapps.
Today I managed to install the Open GAPPS, I found that was the CWM which was not compatible.
Instalaei the TWRP installed and normally without errors.
can u specify .. do u got the same error .. like i got
i will try to install the latest cm 13 and benzo gapps ... lets see what happens
Worked ... I tried with gapps and twrp ............... Thanks a lot
I had this problem: After flashing cm13 and gapps, the device booted until attempting to start GoogleServicesFramework, then it crashed, rebooted, but got stuck for ever at the cm boot animation.
After upgrading from the ancient clockworkmod recovery I had on the device to latest twrp, I could flash cm13 and gapps (opengapps nano), and the device booted fine.
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.
Hey, I have that trouble. I was using CyanogenMod 14.1 and now I tried to update for LineageOS 7.1 and after boot the device it don't initialize. Stay on the loader screen and nothing happens. What could be the problem? One thing I've notice is that I can't click on Do Not Install when it says to me install the SuperSu. I use TeamWin . Sorry if I've make some mistake or make a question which was already done, I look for but don't found it.
roscfi said:
Hey, I have that trouble. I was using CyanogenMod 14.1 and now I tried to update for LineageOS 7.1 and after boot the device it don't initialize. Stay on the loader screen and nothing happens. What could be the problem? One thing I've notice is that I can't click on Do Not Install when it says to me install the SuperSu. I use TeamWin . Sorry if I've make some mistake or make a question which was already done, I look for but don't found it.
Click to expand...
Click to collapse
Wipe system,data,cache, and flash the ROM again
DO NOT INSTALL THE SUPERSU OFFERED BY TWRP. WHEN TWTP ASKS CONFIRMATION TO INSTALL SUPERSU HOLD POWER BUTTON AND IT WILL RESTART
oppodi said:
Wipe system,data,cache, and flash the ROM again
DO NOT INSTALL THE SUPERSU OFFERED BY TWRP. WHEN TWTP ASKS CONFIRMATION TO INSTALL SUPERSU HOLD POWER BUTTON AND IT WILL RESTART
Click to expand...
Click to collapse
Thaks for the answer, I haven't tried it yet because when I tried I've got a error from the TWRP and now I'm trying to fix the recovery mode which gives me other error.
But thanks anyway, when I fix it and try what you told I make a post here.
You go Mount setting and unclick system mount after flash any rom
My phone is Galaxy S4 Mini (i9195i). I've installed TWRP 3.3.1 and flashed using this ROM ( https://forum.xda-developers.com/galaxy-s4-mini/development/rom-aospextended-rom-v7-2-t4107397 ).
The ROM works fine but whenever I try to install GApps (open_gapps-arm64-10.0-pico-20200715) it fails with "Error 64".
I've tried wiping the caches after installing the ROM, rebooting into recovery after installing the ROM, mounting /system before I try to install GApps, downgrading the recovery to TWRP 3.0.2, downgrading the GApps to earlier versions and I've just rooted. The only thing that let me install GApps was installing an arm version instead of arm64. My device is 100% arm64. This resulted in the OS not booting. I left it with a spinning wheel for over 2.5hrs. Reflashed without the arm GApps and it booted in 90s.
Please can someone help me!?
Thank you!
DevaVictrix said:
My phone is Galaxy S4 Mini (i9195i). I've installed TWRP 3.3.1 and flashed using this ROM ( https://forum.xda-developers.com/galaxy-s4-mini/development/rom-aospextended-rom-v7-2-t4107397 ).
...
Please can someone help me!?
Thank you!
Click to expand...
Click to collapse
Hi, apparently from what I read here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-463335444
And here:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-562900489
This is a TWRP issue that can be solved by updating TWRP to its latest version or by using a non official build that have been patched. So I advice you to contact the dev who built TWRP for your device, or keep installing arm Gapps to your phone (if it works).
Have a good day
Also, you can try that : https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-531326172
Or you can try boot TWRP from fastboot :
https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/