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.
Related
My OPO is rooted and I have TWRP installed. I think I now may have a file or two that has been corrupted and I would like to reflash the CM11s rom. I ran the CM11 nightlies on my LG G2 and that was always a fix to get the files back where they should be.
Is there any reason why I can't dirty flash this http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH25R-bacon-signed.zip with TWRP?
kevinga said:
My OPO is rooted and I have TWRP installed. I think I now may have a file or two that has been corrupted and I would like to reflash the CM11s rom. I ran the CM11 nightlies on my LG G2 and that was always a fix to get the files back where they should be.
Is there any reason why I can't dirty flash this http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH25R-bacon-signed.zip with TWRP?
Click to expand...
Click to collapse
So just to make sure I understand this correctly you just want to know why you cant dirty flash CM11s rom over itself. First off you can dirty flash all you want but the issues you may or may not get are on you. Now may I suggest your wipe system when dirty flashing with TWRP. I check off dalvilk, cache and system whenever I upgrade or dirty flash.
Also this is still android and most if not all of the flashing rules still apply
The problem I have is with wifi. This developed a couple of days ago where I have to toggle airplane mode on/off before wifi will reconnect. I actually did a factory reset last night and it did not fix it. I am now thinking that I will need to do more. I suppose the wifi is monitored by the kernel? baseband? I am not sure that a factory reset would reset those things. I could be wrong.
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
I_HAVE_NO_IDEA said:
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
Click to expand...
Click to collapse
Well if you can boot into the recovery and if its custom (TWRP) wipe all the data on your phone. Second I would try to flash a ROM onto your device such as Resurrection Remix and see if that works. Update on your progress.
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
I_HAVE_NO_IDEA said:
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
Click to expand...
Click to collapse
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
vtails said:
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
Click to expand...
Click to collapse
Thank you. But I can't flash a cm12.1 atm (see my post below). I can only flash through fastboot. I'm not sure I properly understood you, what do you call 4 22 ?
FYI I managed to boot again. Here's what I did:
Flash a 5.x ROM, try to boot to let the system make partitions and stuff (I think)
Boot in TWRP and saw that system and cache were not mountable, so I wiped them.
Flash a cm12.1 (+ Gapps) and here we go!
Thank you for your help!
I'm testing CM 12.1 and came from the official Kitkat rom. I had to flash CWM via fastboot (thread here) in order to install CM 12.1. It worked, but I was stuck with that Cyanogen recovery that comes with CM 12.1. I tried flashing CWM and TWRP, but my phone went into a boot loop. I was forced to reflash 12.1. I also tried installing a newer version of TWRP via XZRecovery, but it got stuck and never installed anything. Here are my problems:
Can't make nandroid backups
Unable to flash Xposed zip for Lollipop 5.1
Is it possible to run CM 12.1 and have a regular recovery like CWM/TWRP?
I do, so yeah definitely possible. But I don't use a "regular" recovery, but the FOTA Recovery version of TWRP. This recovery is installed in a partition of the system which won't get overwritten by the CM Recovery when upgrading. Just search for "FOTA TWRP Z3" via google or XDA and you should be good to go.
Omario-242 said:
I do, so yeah definitely possible. But I don't use a "regular" recovery, but the FOTA Recovery version of TWRP. This recovery is installed in a partition of the system which won't get overwritten by the CM Recovery when upgrading. Just search for "FOTA TWRP Z3" via google or XDA and you should be good to go.
Click to expand...
Click to collapse
I've been on Kitkat for about 4 months and have no idea how I missed that. I installed it and it works perfectly. Thank you!
Hey guys I'm new to owning this device and just wanted to know if I have to reflash my firmware after clean flash?
This is what I do
Wipe System/Data/Art/Cache
From there I Flash Firmware/ROM/gapps
Is the firmware step required? Or can I just skip that step once I alreday flashed it previously?
I'm asking this question because I've been having some major issues flashing roms where they flash successfully but frankly just don't boot. I'm just not sure if I'm doing this correctly.
ChainFires Son said:
Hey guys I'm new to owning this device and just wanted to know if I have to reflash my firmware after clean flash?
This is what I do
Wipe System/Data/Art/Cache
From there I Flash Firmware/ROM/gapps
Is the firmware step required? Or can I just skip that step once I alreday flashed it previously?
I'm asking this question because I've been having some major issues flashing roms where they flash successfully but frankly just don't boot. I'm just not sure if I'm doing this correctly.
Click to expand...
Click to collapse
Clean flash involves wiping
/system /data /dalvik /cache
Then flash ROM + gapps
If you flash current firmware it should show 241 baseband in About Phone. Only need to do it once. No need to do every time you flash. CM nightlies do include firmware in their zips so by default will flash the firmware or at least check if its updated every nightly.
Use TWRP 2.8.6.0 or 3.0.0-1 which are versions known to flash firmware correctly.
If you flashed COS12.1.1 fastboot zip at any point in time your data and cache partitions will be F2FS and only certain ROMs will work with that. AOSP based ROMs most likely won't boot.
Sent from my A0001 using Tapatalk
Renosh said:
Clean flash involves wiping
/system /data /dalvik /cache
Then flash ROM + gapps
If you flash current firmware it should show 241 baseband in About Phone. Only need to do it once. No need to do every time you flash. CM nightlies do include firmware in their zips so by default will flash the firmware or at least check if its updated every nightly.
Use TWRP 2.8.6.0 or 3.0.0-1 which are versions known to flash firmware correctly.
If you flashed COS12.1.1 fastboot zip at any point in time your data and cache partitions will be F2FS and only certain ROMs will work with that. AOSP based ROMs most likely won't boot.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Appreciate the the reply! I'm going to restore to stock, and do it all over and update the baseband/firmware from there. Just to be safe ?
It's been a while since I've touched my OPO since I've been using my OPT as my daily. I'm still on YNG1TAS2I3 on my OPO running stock everything. At the moment it is not rooted, with no custom recovery, but the bootloader IS unlocked. I also had xposed installed with some modules but I ran the xposed uninstaller arm.zip version in TWRP and removed the modules.
Is it possible to dirty flash YNG4PAS1N0 which is CM12.1 onto my OPO? I've tried installing TWRP and then fastbooting CM12.1 but it causes a bootloop. I had to re-fastboot flash CM12.0 to get out of it. I've tried it with TWRP 3.0.2.0 and TWRP 2.8.6.0. I also tried sideloading it but again-- bootloop. Reflashing CM12.0 causes CM recovery to rewrite TWRP even though I don't flash the recovery partition. So it took me a LONG time to get TWRP installed again for all these trials.
At this point is my only option to do a complete wipe and then flash? Even trying to run the OTA update for YNG4PAS1N0 causes a bootloop.
I think fastboot wipe the partition then flash it, else upgrade incrementally (I know it'd suck)
Transmitted via BACON
MZO said:
I think fastboot wipe the partition then flash it, else upgrade incrementally (I know it'd suck)
Transmitted via BACON
Click to expand...
Click to collapse
Well the problem is even incrementally updating it is kicking it into bootloop like I said.
crazykidguy said:
Well the problem is even incrementally updating it is kicking it into bootloop like I said.
Click to expand...
Click to collapse
Then
Instead of normal flashing you should fastboot erase <partition> and then flash it.
Transmitted via BACON