I've run into a problem flashing the VANIR & COMMOTIO rom for the e970. I was originally on slimkat beta 3.0, then I went to TWRP and wiped data, system, chache, and dalvik. Then I flashed B64-Commotio-geeb (the latest nightly) and finally I flashed standard Banks gapps 4.4.2. Now I rebooted, and my phone has been stuck on the bootup screen saying "COMMOTIO" for the last 2 hours.
I am pretty sure everything I did was right, but I'd appreciate it if someone pointed out a mistake or fix. I don't want to restore from nandroid if I don't have to.
1. commotio has had issues since 20th nightly
2. Use up to 22nd for vanir
3. Try march 01 of vanir without the kernel b64. Then try the kernel afterwards
Sent from my LG-E970
Solved
bokilenator said:
I've run into a problem flashing the VANIR & COMMOTIO rom for the e970. I was originally on slimkat beta 3.0, then I went to TWRP and wiped data, system, chache, and dalvik. Then I flashed B64-Commotio-geeb (the latest nightly) and finally I flashed standard Banks gapps 4.4.2. Now I rebooted, and my phone has been stuck on the bootup screen saying "COMMOTIO" for the last 2 hours.
I am pretty sure everything I did was right, but I'd appreciate it if someone pointed out a mistake or fix. I don't want to restore from nandroid if I don't have to.
Click to expand...
Click to collapse
I ended up having to restore via Nandroid, then download an older nightly and flashing that. It worked, and now I can flash the new nightly with no problems. Weird that the newest nightly was unable to boot up alone.
Off topic, how was ur experience with SlimKat?
awesome
CarvellW said:
Off topic, how was ur experience with SlimKat?
Click to expand...
Click to collapse
Very good. Barely any bugs and the customization was awesome. However battery sometimes felt short, theres no theme support and no halo.
Related
Hey guys,
I (was) on jokers CM9 (before recent update). I backed up and then attempted to install the new version... So here's the problem, I can't install Gapps PERIOD. It failed for jokers CM9, as well as MIUI v4. I'm not new to installing ROMs, I know I did all the wipes properly etc and fixed permissions just in case. I have tried the last 3 releases of Gapps as well. The ROM is good, boots fine and all (MIUI and CM9) but no Gapps in any situation. The only time I've been able to get it to stick is using the Options Chooser MIUI Installer, worked great. Ive downloaded the files mutiple times with no problems... no idea what I could be missing! Anyone else had this problem/fix?
did you update your CWM recovery to 6.0.x.x? That's what i did before flashing jokers CM10 alpha build and it wouldn't let me install GAPPS either. I just reverted back to an earlier version and it worked fine.
R2DeeTard said:
did you update your CWM recovery to 6.0.x.x? That's what i did before flashing jokers CM10 alpha build and it wouldn't let me install GAPPS either. I just reverted back to an earlier version and it worked fine.
Click to expand...
Click to collapse
Yes! I actually did right before I started flashing the new stuff... thanks!
Still having trouble ... downgraded back to 5.x. (joker v3). Now it seems like data/cache arent wiping. When trying to flash clean, after doing all wipes I still end up with the same install.
fabe0334 said:
Still having trouble ... downgraded back to 5.x. (joker v3). Now it seems like data/cache arent wiping. When trying to flash clean, after doing all wipes I still end up with the same install.
Click to expand...
Click to collapse
I use photon3 recovery. Works great. Be sure to flash twice if gapps don't show up. If still nothing then you must have a bad download of gapps.
If this works let me know.
Sent from my SGH-I777 using XDA
Ok, I got a question what to do now.
The following happened.
I updated the nightly CM10.1 from the settings menu. Normally this works fine. I forgot to make a backup (DUMB). When CM10.1 restarted it never came further than the boot screen (Samsung logo). After waiting for more than 30 minutes I decided to restart the device (get rid of battery). Now CM10.1 won't start again.
Luckily I had a backup, but it was from CM9 (at least I can call). I already tried to install CM10.1 again, but whit no result (bootlooping again).
How to install CM10.1 again? From CM9. What did I forget?
Hope someone can help.
Cm10.1 is no good. Unreliable I think. Try aokp milestone 2 for a solid Rom. If you really want it
Mounts and storage
Format
Data
system
Cache
Wipe dalv cache in advanced
Flash Rom
flash gapps
wipe cache
wipe dalv
Reboot
Enjoy.
or read op first post on first page
I've only just installed CM10.1 on my S2 today. I encountered the same problem with cm-10.1-20130722-NIGHTLY-i9100
However, 0723 worked fine for me. Give that (the latest at time of writing) a go perhaps?
andrewwright said:
Cm10.1 is no good. Unreliable I think. Try aokp milestone 2 for a solid Rom. If you really want it
Click to expand...
Click to collapse
I did, and it works now, luckaly I made a backup on my google account so all apps are downloaded
Thanks for your solution!
ps. Is there an overview what the big differences are between CM10.1 and aokp m2?
baszer said:
I did, and it works now, luckaly I made a backup on my google account so all apps are downloaded
Thanks for your solution!
ps. Is there an overview what the big differences are between CM10.1 and aokp m2?
Click to expand...
Click to collapse
Easy way to put it is cm 10.1 unstable aokp milestone 2 stable. Simple as that. Also more changeable things in aokp. Cm fanboys wont like what I put but they no its the truth :thumbup: glad you sorted your problem :thumbup:
I just installed PM 4.3 and from what i read it should be compatible with newest UBER 3.0 kernal but it just stays stuck in splash (pacman roms, game over, instert coin etc.) I tried downgrading to previous twrp, reflashing rom and gapps, and also tried factory reset. Any help of info would be appreciated, sorry if this is wrong section.
l330n said:
I just installed PM 4.3 and from what i read it should be compatible with newest UBER 3.0 kernal but it just stays stuck in splash (pacman roms, game over, instert coin etc.) I tried downgrading to previous twrp, reflashing rom and gapps, and also tried factory reset. Any help of info would be appreciated, sorry if this is wrong section.
Click to expand...
Click to collapse
there is a compatible Uber for that. most developers will suggest at least 24 hours with kernel included in rom. you don't have to just suggested.
you mentioned a previous TWRP, but you didn't mention any specific versions.
2.6.0.1 is working great for me
2.6.0.3 seemed to have some issues, hence the reason I am still on 0.1
2.6.1.0 is most recent, but until I have problem with 0.1 im sticking with it.
you should always factory reset and it suggested to repeat 3-4 times to clear out any remaining leftover goop.
my routine an also used by others is...........
3 wipes, cleanliness is next to godliness
flash rom alone
flash rom again w/ gapps
wipe davlik and cache
boot up and let settle the 10 mins
reboot and set up
maybe overkill but has not failed me
captemo said:
there is a compatible Uber for that. most developers will suggest at least 24 hours with kernel included in rom. you don't have to just suggested.
you mentioned a previous TWRP, but you didn't mention any specific versions.
2.6.0.1 is working great for me
2.6.0.3 seemed to have some issues, hence the reason I am still on 0.1
2.6.1.0 is most recent, but until I have problem with 0.1 im sticking with it.
you should always factory reset and it suggested to repeat 3-4 times to clear out any remaining leftover goop.
my routine an also used by others is...........
3 wipes, cleanliness is next to godliness
flash rom alone
flash rom again w/ gapps
wipe davlik and cache
boot up and let settle the 10 mins
reboot and set up
maybe overkill but has not failed me
Click to expand...
Click to collapse
Cool, thanks for the tips, ill try them once i get home in the morning from work.
I saw someone recommend twrp 2.6.1.0 (still hangs), at first I had 2.6.3.0 (newest i believe) and still kept hanging on splash
Do you know which uber kernal is the correct one for that rom or is it just the one included in newest pacman rom 4.3?
I may just try out carbon and revolt, seems like more people running those roms. I was messing with some of the color setting in PA and phone locked up on me and it was weird, had like a greenish screen that got brighter and brighter and brighter eventually i just shut it off, it was fine when i restarted. Im not too worried about changing the colors really, i was just tryin it out.
Hello people!
Since I had this Galaxy Nexus I always clean flashed my ROM whenever even a major version (4.1 -> 4.2) update was done. Dirty flashed Nightlies. When I clean flashed, I wiped everything except /sdcard/ and everything went fine. However, lately some AOKP things started giving trouble so I restored, wiped and flashed a lot of times. Now this is what happened:
Flash kernel, AOKP 4.3 stopped booting.
Restore from backup, AOKP 4.3 still not booting.
Forget to wipe, install XP + PA 4.4 Gapps (it's a 4.4 CM based ROM), boot. Everything works! All my apps work, even SuperUser works, which normally asks for permissions after a new flash.
Don't like XP, install CM11 + PA 4.4 Gapps. It works fine!
So what's the matter with no dirty flashing? I just flashed a 4.4 ROM over a 4.3 ROM based on completely different things and it still works great, then I flashed another ROM on top of that and no issues have occurred yet. All works fine - E-mail accounts, Google accounts, YouTube, even my alarms are still kept in one place. The custom toggles I set in XP still are there and everything is just dandy.
Do you guys always clean flash, or did you also decide to say "who gives a hell, let's go dirty"? Did any dirty flashing result in bad things for you?
tl;dr
Why exactly is dirty flashing bad? I dirty flashed AOKP 4.3.1 -> CM11 (4.4) and all's fine.
RainbowSwag said:
Hello people!
Since I had this Galaxy Nexus I always clean flashed my ROM whenever even a major version (4.1 -> 4.2) update was done. Dirty flashed Nightlies. When I clean flashed, I wiped everything except /sdcard/ and everything went fine. However, lately some AOKP things started giving trouble so I restored, wiped and flashed a lot of times. Now this is what happened:
Flash kernel, AOKP 4.3 stopped booting.
Restore from backup, AOKP 4.3 still not booting.
Forget to wipe, install XP + PA 4.4 Gapps (it's a 4.4 CM based ROM), boot. Everything works! All my apps work, even SuperUser works, which normally asks for permissions after a new flash.
Don't like XP, install CM11 + PA 4.4 Gapps. It works fine!
So what's the matter with no dirty flashing? I just flashed a 4.4 ROM over a 4.3 ROM based on completely different things and it still works great, then I flashed another ROM on top of that and no issues have occurred yet. All works fine - E-mail accounts, Google accounts, YouTube, even my alarms are still kept in one place. The custom toggles I set in XP still are there and everything is just dandy.
Do you guys always clean flash, or did you also decide to say "who gives a hell, let's go dirty"? Did any dirty flashing result in bad things for you?
tl;dr
Why exactly is dirty flashing bad? I dirty flashed AOKP 4.3.1 -> CM11 (4.4) and all's fine.
Click to expand...
Click to collapse
This is because roms dont always format the proper partitions and can cause corruption and data loss. This can also lead to ghost issues. I personally set my script to clean flash my roms. This way I dont have to do it manually and when I was releasing it prevented ghost issues and the normal questions about clean or dirty flashing.
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
What is CyanogenMod ? It is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors of these cell phones.
CyanogenMod 13.0 : Download
Changelog : Changelog
Open GApps : Download ( arm, 6.0, nano )
TWRP : Download​
CM13 Nightlies, ROM for the Sprint Galaxy S5
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Nightly, now moved to 14.1
UPDATE 6/14: Looks like there's an issue that 5ghz network doesn't work on higher bands, but it works on 36-48 and bluetooth. Hopefully it will be fixed soon.
UPDATE 6/23: There's a fix attempt on boot image. Link. Thanks to @haggertk
UPDATE 6/27: Looks like Bluetooth and Wifi issue have been fixed since 6/25 nightly.
Thanks to @haggertk
Created 2016-05-12
Last Updated 2016-11-29
Reserved
Works great!
Is there a version of SuperSU that works with CM13? All trash the ROM and have to do full restore.
I just needed confirmation on something. I'm currently running CM12.1 on a SM-G900P with firmware G900PVPU3BOK4. Does the update to CM 13.0 require a firmware update to G900PVPU3CPCA (the MM level of firmware from the stock Sprint download) or can I stay on G900PVPU3BOK4 with CM13.0?
btw: Sorry for the double post. I'm new to XDA and having trouble figuring out which forum is correct for me to ask my questions in.
Thanks!
alexclang said:
I just needed confirmation on something. I'm currently running CM12.1 on a SM-G900P with firmware G900PVPU3BOK4. Does the update to CM 13.0 require a firmware update to G900PVPU3CPCA (the MM level of firmware from the stock Sprint download) or can I stay on G900PVPU3BOK4 with CM13.0?
btw: Sorry for the double post. I'm new to XDA and having trouble figuring out which forum is correct for me to ask my questions in.
Thanks!
Click to expand...
Click to collapse
From my limited experience, it does not appear to run on CPCA. CM13 on OK4 worked for me.
e-j said:
From my limited experience, it does not appear to run on CPCA. CM13 on OK4 worked for me.
Click to expand...
Click to collapse
Excellent!! I'll just install the latest nightly for CM13 just like I was going for 12.1 and hopefully things will go smoothly!
I'm having difficulty with CM13 and Open GApps. If I flash CM13 alone everything is fine. When I install CM13 and then the ARM 6.0 pico Open GApps through the same TWRP 3.0.2-1 session (as directed here: https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0), I either get constant force close errors after boot (with 5/19 CM & GApps zips) or an endless blue android boot screen (with 5/20 CM & GApps zips). I've tried re-downloading the zips and reinstalling after wiping (dalvik, system, data, cache) multiple times.
Any ideas?
UPDATE/PSA: USE THE NANO GAPPS AS STATED IN THE OP. NANOGAPPS INFINITY OPENS THE DOOR.
e-j said:
I'm having difficulty with CM13 and Open GApps. If I flash CM13 alone everything is fine. When I install CM13 and then the ARM 6.0 pico Open GApps through the same TWRP 3.0.2-1 session (as directed here: https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0), I either get constant force close errors after boot (with 5/19 CM & GApps zips) or an endless blue android boot screen (with 5/20 CM & GApps zips). I've tried re-downloading the zips and reinstalling after wiping (dalvik, system, data, cache) multiple times.
Any ideas?
Click to expand...
Click to collapse
I've had similar issues; all with Google apps. When I see it, I delete the Google app in question and then immediately re-install from the App store. Once I've done that, I haven't had the Google app force quit again.
alexclang said:
I've had similar issues; all with Google apps. When I see it, I delete the Google app in question and then immediately re-install from the App store. Once I've done that, I haven't had the Google app force quit again.
Click to expand...
Click to collapse
Got it working after I realized the OP specifically mentioned the "nano" GApps variant; booted fine after a clean install of CM13 & the nano zip.
Issues w. CM13 flash
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
smspenc said:
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
Click to expand...
Click to collapse
Would boot loop on the latest firmware for me as well; had to Odin back to OK4.
smspenc said:
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
Click to expand...
Click to collapse
You had the official MM installed from Samsung, correct?
As far as I know, the current CM13 needs LP bootloader installed.
I have no issue with LP bootloader.
lentm said:
You had the official MM installed from Samsung, correct?
As far as I know, the current CM13 needs LP bootloader installed.
I have no issue with LP bootloader.
Click to expand...
Click to collapse
Yeah that was exactly the issue. Reflashed 5.0 then made the jump and it worked perfectly. So much wasted time...
---------- Post added at 05:28 AM ---------- Previous post was at 05:25 AM ----------
e-j said:
Would boot loop on the latest firmware for me as well; had to Odin back to OK4.
Click to expand...
Click to collapse
Yeah reflashing lollipop then installing cm13 did the trick.
Does this Rom fix Bluetooth issues?
Sent from my SM-G900P using XDA-Developers mobile app
has anyone got themes to work ine keeps crashing
manolze said:
has anyone got themes to work ine keeps crashing
Click to expand...
Click to collapse
Mine works fine with Puzzled UI - CM Theme from Play Store on 5/20 build.
I have no working theme chooser on this releaese
xenokc said:
Works great!
Is there a version of SuperSU that works with CM13? All trash the ROM and have to do full restore.
Click to expand...
Click to collapse
no need just go into developer and turn on root access
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
anyone have a solution to theme chooser yet? i have already fixed phone dial problem and time out of sync problem
xpm69420 said:
no need just go into developer and turn on root access
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
anyone have a solution to theme chooser yet? i have already fixed phone dial problem and time out of sync problem
Click to expand...
Click to collapse
Theme chooser works great for me, not having any issues with it. I am having an issue with the time being or of sync when set to automatic... How'd you fix it? Also, what's wrong with the dialer... can't say I'm having any issues there either.
unclejuju said:
Does this Rom fix Bluetooth issues?
Sent from my SM-G900P using XDA-Developers mobile app
Click to expand...
Click to collapse
I little late here, but CM 13.0 did NOT fix the S5 bluetooth issues. Still have the skipping and studdering.