I just updated from an old cm 10.2 unofficial build from sometime in september to the latest nightly of cm 10.2. I used the update feature in cm to get the latest nightly and install it. I am running twrp recovery and wipe data cache and delvik after flashing then reboot. this all works fine and the rom boots up and starts re installing my apps. however after I reboot the device it just sits at the tab boot logo and I end up having to wipe data again to boot up and start all over. how can I fix this? I am just not having the best of luck with roms these days. Soon I want to update to kitkat but I am having trouble with that as well. (see other thread)
Edit: it's now having the same issue with my restored backup of my previous rom. Basically my backup is now doing the exact same thing where it just freezes up at the galaxy tab logo after first reboot.
mikee286 said:
I just updated from an old cm 10.2 unofficial build from sometime in september to the latest nightly of cm 10.2. I used the update feature in cm to get the latest nightly and install it. I am running twrp recovery and wipe data cache and delvik after flashing then reboot. this all works fine and the rom boots up and starts re installing my apps. however after I reboot the device it just sits at the tab boot logo and I end up having to wipe data again to boot up and start all over. how can I fix this? I am just not having the best of luck with roms these days. Soon I want to update to kitkat but I am having trouble with that as well. (see other thread)
Edit: it's now having the same issue with my restored backup of my previous rom. Basically my backup is now doing the exact same thing where it just freezes up at the galaxy tab logo after first reboot.
Click to expand...
Click to collapse
Maybe it´s a problem with your emmc. We have a MAG2GA type with a known bug called "MAG2GA TRIM bug" and like i know cm 10.2 runs the trim command once a day. There is a possible patch for this problem, but i think it´s not merged to our device.
Please can you check the emmc memory with the tool eMMC Brickbug Check from Market?
Hello.
Recently I returned my HTC Sensation XE arranged, and seeing that it had no guarantee I decided to root it. After two days in which I almost lost the mobile after having bricked, I finally managed to unlock the bootloader (although I'm still S-ON), install the latest version of 4ext Recovery Touch and give root permissions.
What happens is that looking for an Android Lollipop ROM I saw there was only one type of ROMs developed by Ivanich, and others called UnoROMs but at the end also belonged to Ivanich. Both unofficial version of CyanogenMod 12.1.
Overall, I started to download and install CM12.1 ROM with GApps and entering in recovery, but nothing was installed. I deleted cache, dalvik, data and reset to factory, but all attempts were in vain. Or almost.
When I realized that something was wrong, I looked in the ZIP of the ROM, I entered in the "/system" folder and presto!: no sign of apps, data, or other things that I think should be to make it work, only was the 'build.prop'.
Finally I gave up and tried to install Ivanich's CM11 with the corresponding GApps, and everything was great (although WIFI, that is unusable). It turns out that this ROM itself had all the appropriate files in the '/system' folder.
I thought then that Ivanich's CM12.1 ROM would be an update of his CM11 ROM and I tried to install it with CM11 as the system at that time, and I got it, but it starts out a sign saying that I had no data on the phone and to make it work I need to reset to factory. I did it and nothing happened. The recovery remained caught in the process of reseting to factory. And so over and over again. At the end I reinstalled CM11 and tried to repeat the installation process of CM12 this time making an erased of dalvik, data, cache and factory reset (which I not did at the previous), but it didn't installed, and 5.1 GApps either. As usual.
Currently I have CM11 by Ivanich (KitKat 4.4.4) with GApps, but I can't use the phone because WIFI practically doesn't work. There is a ZIP to fix WIFI that I flashed and that was fine, but it didn't fix anything.
Please can someone explain to me why I can't install CM12.1 and 5.1 GApps and why this ROM has the '/system' folder empty. There are people that have been able to install this ROM, and I can't understand how they have succeeded.
Thanks to all who help me in advance.
Hey there,
i've got a problem, don't know how serious it is. i recently installed cm12.1 for the p900 wifi, then decided to test cm11 for there were several bugs and i needed a stable rom. bein in cm12.1 still i encrypted the device. unfortunately i didn't set a password before flashing cm11. now, after flashing the older rom (cm11) i receive a password prompt before i can enter the OS. well, that password has never been set and i seem to be stuck.
my question: how can i reset everything (format partition) to a "blank state" and make a fresh install of cm11?
thanks in advance,
andi
I posted this over on the CM forums, but wanted to post here as well for visibility.
I have multiple (read as 30+) 1st Gen Boost Moto Gs (XT1031) and this has been a problem on every.... single.... one...
Stock OS Info
Android Version: 4.4.2
Baseband version: MSM8626BP_1032.355.66.00R
Kernel version: 3.4.0-gc6fc9e1-00001-gf3bf628
System version: 175.44.1.falcon_cdma.Boost.en.US
Build number: KXB20.9-1.10-1.18-1.1
Bootloader: 41.1A
Recovery: twrp-2.8.7.0.-falcon_STOCK_NOTHEME
I've also tested with the Stock 4.4.4 and 5.1 Soak Test OS versions, both have the same results as well.
Additionally, this happens regardless of whether GAPPS is flashed or not.
I've tried the following, and ALWAYS results in an endless boot that just constantly stays on the CM Android head boot animation unless I flash & boot to CM11 first:
(Note: A TWRP Factory Reset is performed before flashing each new ROM)
CM11 - cm-11-20140504-SNAPSHOT-M6-falcon.zip
Stock -> CM11 = Boots and works fine
CM12.1 - cm-12.1-20151115-NIGHTLY-falcon.zip
Stock -> CM12.1 = Endless Boot
Stock -> CM11 (without booting to OS) -> CM12.1 = Endless Boot
Stock -> CM11 (Booted once) -> CM12.1 = Boots and works fine
CM13 (all nightly versions)
Stock -> CM13 = Endless Boot
Stock -> CM11 (without booting to OS) -> CM13 = Endless boot
Stock -> CM11 (Booted once) -> CM13 = Boots and works fine
So...The only way that I can get these to boot, is if I flash CM11 AND boot into it once and THEN flash CM12.1/CM13.
What is it about the first boot of CM11 that makes CM12.1 and CM13 work? any why doesn't direct from Stock -> CM12.1/CM13 work??? Is there a Kernel or something that gets installed when CM11 boots or something?
This is driving me insane. Please help me figure this out so that I can flash directly from Stock -> CM12.1/CM13.
---
Here is an example of exactly how to reproduce this problem. From the Stock ROM, do the following:
{Unlock Bootloader}
{Enable USB Debugging}
adb reboot bootloader
fastboot flash motoboot motoboot_41.1A.img
fastboot flash logo logo.bin
fastboot flash recovery twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img
fastboot reboot
adb reboot recovery
adb shell twrp wipe factoryreset
adb push cm-12.1-20151115-NIGHTLY-falcon.zip /sdcard/
adb shell twrp install /sdcard/cm-12.1-20151115-NIGHTLY-falcon.zip
adb reboot
Click to expand...
Click to collapse
...Device never boots, and only stays on the CM logo animation.
I've just finished updating from Stock 5.1 (XT1033) to CM 13
Here's what I've done
1. Updated to the latest TWRP recovery
2. Copied the latest CM 13 nightly and Gapps (Pico) to internal storage
3. Reboot to recovery
4. Performed an advanced wipe. Wiping /system, /cache and /dalvik-cache
5. Performed a Factory Reset
6. Flashed both CM 13 and Gapps
7. Reboot
Wait for a few minutes.
mardobloom said:
I've just finished updating from Stock 5.1 (XT1033) to CM 13
Here's what I've done
1. Updated to the latest TWRP recovery
2. Copied the latest CM 13 nightly and Gapps (Pico) to internal storage
3. Reboot to recovery
4. Performed an advanced wipe. Wiping /system, /cache and /dalvik-cache
5. Performed a Factory Reset
6. Flashed both CM 13 and Gapps
7. Reboot
Wait for a few minutes.
Click to expand...
Click to collapse
Exact same steps on my XT1031, waited 6 hours, still didn't boot.
But if I flash CM11, boot to it once, then factory reset and install CM13... it will boot just fine. What magic does CM11 do that CM12.1/CM13 aren't doing?!
As a side note, the TRWP Factory Reset option wipes /system /cache and /dalvik-cache... so step #4 is redundant.... but I did it anyways.
Edit: I guess I skipped step #1 ... didn't realize that TWRP 3.0.2.0 was available for "falcon". I'll try this later tonight and see if it fixes the issue or not.
https://dl.twrp.me/falcon/
twig123 said:
As a side note, the TRWP Factory Reset option wipes /system /cache and /dalvik-cache... so step #4 is redundant.... but I did it anyways.
Click to expand...
Click to collapse
I followed the steps to perform a clean update from the official thread of CM 13 but when I tried to install the zip file it says that the data is incompatible and I needed to perform a factory reset. So that's why I've added that additional step so that there won't be any problems while installing CM 13. :laugh:
twig123 said:
Edit: I guess I skipped step #1 ... didn't realize that TWRP 3.0.2.0 was available for "falcon". I'll try this later tonight and see if it fixes the issue or not.
https://dl.twrp.me/falcon/
Click to expand...
Click to collapse
Okay try first with that one i.e. TWRP 3.02.0. If that doesn't work then maybe you can try this one from here :- http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621 <------- This one worked fine for me i.e twrp-3.0.0.0_2-falcon following the above steps which I've mentioned.
P.S. I'm currently on baseband 1032.3116.98.00R - Retail Asia
mardobloom said:
I followed the steps to perform a clean update from the official thread of CM 13 but when I tried to install the zip file it says that the data is incompatible and I needed to perform a factory reset. So that's why I've added that additional step so that there won't be any problems while installing CM 13. :laugh:
Okay try first with that one i.e. TWRP 3.02.0. If that doesn't work then maybe you can try this one from here :- http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621 <------- This one worked fine for me i.e twrp-3.0.0.0_2-falcon following the above steps which I've mentioned.
P.S. I'm currently on baseband 1032.3116.98.00R - Retail Asia
Click to expand...
Click to collapse
Nope. Flashed back to stock to test, updated to TWRP 3.0.2.0, attempted to flash to the latest CM13 nightly... still endless boot (waited 30min and it just stayed on the boot animation).
I'll try the recovery you mentioned later.... although, I also tried CM's own Nightly recovery... and the same thing happens with that as well.
I tried with the recovery you mentioned, and the same thing happens.
However, the story unfolds...
Recovery log when flashing from Stock-to-CM11:
http://pastebin.com/M0EGdLwu
Recovery log when flashing from Stock-to-CM12.1:
http://pastebin.com/HaderDW2
In the Stock-to-CM12.1 log.... it doesn't appear that anything is copied! if you look at the Stock-to-CM11 log, after the "Installing zip file '/sdcard/cm-11-20140504-SNAPSHOT-M6-falcon.zip'" line, it has a bunch of "minzip: Extracted file" lines. Comparing that to the Stock-to-CM12.1 long, none of those such lines exist in the log! I see the CM12.1 ROM file has a "system.new.dat" file, instead of all of the files extracted in the "system" folder, like the CM11 ROM has... not sure if that is causing the problem or not.
If none of the files are getting copied, that would explain why it never boots.... but this doesn't tell me how to fix it... or why CM11 doesn't have a problem, but CM12.1 and CM13 DO have a problem.
twig123 said:
I tried with the recovery you mentioned, and the same thing happens.
However, the story unfolds...
Recovery log when flashing from Stock-to-CM11:
http://pastebin.com/M0EGdLwu
Recovery log when flashing from Stock-to-CM12.1:
http://pastebin.com/HaderDW2
In the Stock-to-CM12.1 log.... it doesn't appear that anything is copied! if you look at the Stock-to-CM11 log, after the "Installing zip file '/sdcard/cm-11-20140504-SNAPSHOT-M6-falcon.zip'" line, it has a bunch of "minzip: Extracted file" lines. Comparing that to the Stock-to-CM12.1 long, none of those such lines exist in the log! I see the CM12.1 ROM file has a "system.new.dat" file, instead of all of the files extracted in the "system" folder, like the CM11 ROM has... not sure if that is causing the problem or not.
If none of the files are getting copied, that would explain why it never boots.... but this doesn't tell me how to fix it... or why CM11 doesn't have a problem, but CM12.1 and CM13 DO have a problem.
Click to expand...
Click to collapse
Backup first and try to restore your phone to stock firmware using the instructions over here. ----------> http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
And choose the firmware version which is related to your phone. They will be something like this:-
XT1031_FALCON_BOOST_5.1_LPB23.13-56_cid9_CFC.xml.zip
XT1031_FALCON_REPW_5.1_LPB23.13-51-R.10_cid6_CFC.xml.zip
XT1031_FALCON_USC_5.1_LPB23.13-33.6_cid9_CFC.xml.zip
XT1031_FALCON_USC_5.1_LPBS23.13-33.6-2_cid9_CFC.xml.zip
mardobloom said:
Backup first and try to restore your phone to stock firmware using the instructions over here. ----------> http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
And choose the firmware version which is related to your phone. They will be something like this:-
XT1031_FALCON_BOOST_5.1_LPB23.13-56_cid9_CFC.xml.zip
XT1031_FALCON_REPW_5.1_LPB23.13-51-R.10_cid6_CFC.xml.zip
XT1031_FALCON_USC_5.1_LPB23.13-33.6_cid9_CFC.xml.zip
XT1031_FALCON_USC_5.1_LPBS23.13-33.6-2_cid9_CFC.xml.zip
Click to expand...
Click to collapse
Thanks for the suggestion, but I've already flashed to stock (XT1031_FALCON_BOOST_5.1 in this case).
The issue is coming FROM stock to CM12.1 or CM13 that is the problem, but Stock->CM11->CM12.1/CM13 works fine.
I don't want to have to install CM11 every time just to get a bootable rom... :-\
twig123 said:
Thanks for the suggestion, but I've already flashed to stock (XT1031_FALCON_BOOST_5.1 in this case).
The issue is coming FROM stock to CM12.1 or CM13 that is the problem, but Stock->CM11->CM12.1/CM13 works fine.
I don't want to have to install CM11 every time just to get a bootable rom... :-\
Click to expand...
Click to collapse
Save the recovery log while upgrading from CM11 to CM 12.1 to see what's the difference between that one which works and Stock to CM12.1/13
After playing with trying to flash CM13 directly for quite a long time.... I've come to the conclusions that something with the partition wipes don't actually work within the CM13 setup script, nor from Custom Recovery!
However, I found a workaround! Wiping the partitions from the Bootloader, instead of from Custom Recovery, allows a flash of CM13 to boot properly!
(The question still stands as to why CM11 doesn't have this issue, but CM12.1 and CM13 do...... but I have a workaround, so I'm not too worried about it)
I made a Windows Batch script to automate this flashing process, which I posted over on the CM Forum:
https://forum.cyanogenmod.org/topic...-to-cm121-or-cm13-never-boots/#comment-601380
Newbie here.
Background: I have my Samsung Note 10.1 GT-N8000 since 2012, but I haven't touched it for 2+ years because it was still on Android 4.1. (Last week Netflix announced that we could watch it offline with Android 4.4 up, so I eventually had the courage to do sth about my 10.1)
My problems:
I was using TWRP 2.4, flashed CM13 ROM and Gapps pico. It went well except all Google apps weren't installed properly:
- If I just flashed the CM13 ROM without Gapps, upon reboot it kept popping "Unfortunately Google Play etc stopped"
- If I flashed both, it was the same, plus all Google apps were labelled "com.Android" instead.
I searched for and tried all possible solutions, and in one old threat someone suggested TWRP version matters too. So I updated it to TWRP 2.8 (also tried 3.0). Now, I have a different set of problems. I can't flash in TWRP 2.8 the same ROM that I could flash with TWRP 2.4, and it keeps giving the "error executing updater binary in zip" I've tried it million times (literally fighting it for the past 18 hours...)
I've tried the followings: wiping system/ cache before flashing new ROM, starting the entire process, rooting it again etc.
Could anyone kindly chip in? Any suggestions are appreciated!!!
Try Philz Recovery .
Nonono...don't try Philz recovery. Use the recovery explicitly stated in the CM13 instructions (TWRP 2.8.7.0) or newer (I'm using 3.0.2.0). Do not use any recovery that the instructions say is not supported, which is everything else.
rudycreat said:
My problems:
I was using TWRP 2.4, flashed CM13 ROM and Gapps pico. It went well except all Google apps weren't installed properly:
...
I've tried the followings: wiping system/ cache before flashing new ROM, starting the entire process, rooting it again etc.
Click to expand...
Click to collapse
Given this and the apparent lack of following CM13 installation instructions (you didn't wipe everything), I'd suggest starting over with downloading/flashing the TWRP version on the CM13 downloads page and re-downloading CM13 and and Open GApps check MD5s. Maybe a standard Open GApps install would be a good idea; you can always uninstall what you don't want.
Not meaning to sound harsh but preferable to spending another 18 hours in Einstellung. (pun not intended)