I guess, Rc dosen't get updated as quickly as nightlies, so if i were to flash back to nightly do i need to wipe anything?
Or can i just flash and go
Not really - unless it is not needed for some new major changes in the update
I've been using CM and updating nightlys about once per week. Yesterday I updated to 10.1 but when I did Gapp didn't work (of course) I thought. No big deal, I'll just revert back to a 10.0 build... then something went horribly wrong. The phone stuck on the CM splash/boot screen.
I've tried deleteing cache and dalvik cache, Flashing the stable 10.0 build, flashing the 10.1 nightly and gapps... nothing has worked. I'm at a loss as to what to do now.
I should note that i'm using CWM.
Currently i've restored to the last stock build which ate battery like it was candy (ironic since it's jelly bean... carnivore) and this works... but it still won't boot if I try to flash CM. Any help explaining what has happened or how to fix it would be appreciated.
Athanasius said:
I've been using CM and updating nightlys about once per week. Yesterday I updated to 10.1 but when I did Gapp didn't work (of course) I thought. No big deal, I'll just revert back to a 10.0 build... then something went horribly wrong. The phone stuck on the CM splash/boot screen.
I've tried deleteing cache and dalvik cache, Flashing the stable 10.0 build, flashing the 10.1 nightly and gapps... nothing has worked. I'm at a loss as to what to do now.
I should note that i'm using CWM.
Currently i've restored to the last stock build which ate battery like it was candy (ironic since it's jelly bean... carnivore) and this works... but it still won't boot if I try to flash CM. Any help explaining what has happened or how to fix it would be appreciated.
Click to expand...
Click to collapse
Don't flash 10.1 over 10.0 if you do so.
Wipe data factory reset / format boot also format system with cwm later make fresh install. flash gapps right after you flash the rom don't let it boot without it
mypat said:
Don't flash 10.1 over 10.0 if you do so.
Wipe data factory reset / format boot also format system with cwm later make fresh install. flash gapps right after you flash the rom don't let it boot without it
Click to expand...
Click to collapse
I can't tell you exactly what I did but it seems to be working... somehow a factory reset resulted in CM10.0 and gapps installed correctly... i'm still scratching my head but i'm happy enough.
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?
So guys, I've been at this for days.
I was originally using AK's kernel, TWRP Recovery and the official 44S ROM, but had issues with logging being disabled, so I fugured I'd go for the cm12 nightlies. I installed the latest AK kernel (102), updated TWRP to 2.8.4.1 and tried to dirty flash the 20150130 nightly, just to find that I'm stuck on the boot screen. I then on found about a firmware update that I installed after I wiped everything clean. Installed cm12 again and I was stuck in the same bootloop. I've even tried cm11 with the intention to OTA to cm12, but that had the same issue. That went through many different ROM's I've tried. I am kind of fed up by now and I would appreciate any input.
Thanks.
So you initially tried to dirty flash CM12 over CM11S? And you did that after flashing the AK kernel? If so you've got one major problem there: never dirty flash when switching ROMs or Android versions, you did both in one hit. And the minor problem: you're meant to flash a kernel after flashing a ROM, if you do it the other way around the stock kernel from the ROM zip just overwrites the custom kernel.
Anyway, I think your best bet is to flash the stock images with fastboot, see section 8 of my guide thread .
Transmitted via Bacon
I can flash any 11S rom, but the problem is installing and booting into cm12. But I think I'll just wait for 12S as it should come up soon. Would be cool if I had access to nightlies though.
Well' you can't win them all.
There's no reason why you shouldn't be able to flash the nightlies? Did you update your firmware appropriately before flashing CM12?
Transmitted via Bacon
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
tetakpatak said:
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
It's definitely possible, the firmware is the most likely culprit at this stage though.
Transmitted via Bacon
I have updated the firmware properly before that. Also no other custom ROM runs - not only cm12. I've tried cm11, OmniROM, TGM, BlissPop and temarek.
I have also tried CWM, but not PhilZ. I made sure to format everything - even internal storage. I've tried both F2FS and EXT4 as filesystems for /system.
I will try PhilZ though.
Cheers.
Hey guys,
I am thinking of giving f2fs a shot due to some rumors. As I am sticking to the CM12.1 nightlies, I am flashing new builds every now and then. So modifying the fstab everytime after flashing is time consuming. Is there some way to flash a zip for f2fs support and be done?
Rei