Hello everyone, I have been lurking for a long time and I just want to say what a great community this is and thank you to everyone who develops and/or contributes. I have learned everything I know about android dev from reading these forums and I am confident enough now to start posting and trying to offer whatever I can from my experiences. Now for my question
What is the general opinion about flashing nightly builds? Is it generally only for people who are testing/debugging? I am running cm-11-20140805-NIGHTLY-moto_msm8960_jbbl on my Atrix HD right now and I am very happy with it - in fact I am ecstatic to have found a 4.4.4 rom that works smooth, fast, and stable for me (I got tired of waiting for AT&T to release their OTA update!). Consider this a positive endorsement of it. However, I see that new builds were released on 8/9 and 8/10 (as I would expect for nightly builds to be updated often, of course). I looked at the changelogs and I don't fully understand every last thing I see there, but I have not encountered any issues with the build I am running, so should I bother to flash the newest nightly releases when they come out? Is there a way to update without resetting everything or should I just restore my apps with Titanium Backup after flashing a new nightly? Finally, what is the best way for me to contribute to development (short of submitting code myself, as I do not feel confident enough to do so just yet)?
Since it seems I am not allowed to have a sig until I reach a certain number of posts(?) I will post my current devices below:
AT&T Motorola Atrix HD MB886
ClockworkMod Recovery v6.0.4.4
CyanogenMod 11 cm-11-20140805-NIGHTLY-moto_msm8960_jbbl (KK 4.4.4)
pa_gapps-stock-4.4.4-20140804-signed
Acer Iconia A500
Skrilax_CZ's Bootloader v8
ClockworkMod Recovery Thor v1.7.3
CyanogenMod 10.2 cm-10.2-20131004-UNOFFICIAL-a500 (JB 4.3)
P.S. - special thanks to the Myth Team, Djrbliss, skeevydude, leanix, osm0sis, chainfaire, PhilZ for making it super easy to root and unlock my phone :good:
Fanarkle said:
Hello everyone, I have been lurking for a long time and I just want to say what a great community this is and thank you to everyone who develops and/or contributes. I have learned everything I know about android dev from reading these forums and I am confident enough now to start posting and trying to offer whatever I can from my experiences. Now for my question
What is the general opinion about flashing nightly builds? Is it generally only for people who are testing/debugging? I am running cm-11-20140805-NIGHTLY-moto_msm8960_jbbl on my Atrix HD right now and I am very happy with it - in fact I am ecstatic to have found a 4.4.4 rom that works smooth, fast, and stable for me (I got tired of waiting for AT&T to release their OTA update!). Consider this a positive endorsement of it. However, I see that new builds were released on 8/9 and 8/10 (as I would expect for nightly builds to be updated often, of course). I looked at the changelogs and I don't fully understand every last thing I see there, but I have not encountered any issues with the build I am running, so should I bother to flash the newest nightly releases when they come out? Is there a way to update without resetting everything or should I just restore my apps with Titanium Backup after flashing a new nightly? Finally, what is the best way for me to contribute to development (short of submitting code myself, as I do not feel confident enough to do so just yet)?
Since it seems I am not allowed to have a sig until I reach a certain number of posts(?) I will post my current devices below:
AT&T Motorola Atrix HD MB886
ClockworkMod Recovery v6.0.4.4
CyanogenMod 11 cm-11-20140805-NIGHTLY-moto_msm8960_jbbl (KK 4.4.4)
pa_gapps-stock-4.4.4-20140804-signed
Acer Iconia A500
Skrilax_CZ's Bootloader v8
ClockworkMod Recovery Thor v1.7.3
CyanogenMod 10.2 cm-10.2-20131004-UNOFFICIAL-a500 (JB 4.3)
P.S. - special thanks to the Myth Team, Djrbliss, skeevydude, leanix, osm0sis, chainfaire, PhilZ for making it super easy to root and unlock my phone :good:
Click to expand...
Click to collapse
Nightly builds are just that, builds that are made nightly. They are the most up to date. Snapshots/M(*insert number here*) releases are generally more stable, but we got knocked out of being eligible for them after the release of M8 (thanks kk bootloader). CM has made a msm8960 jb bl section, which you did find. This might get us up and running for a M10 next month if they choose to do that, but then again, msm8960 did not get a M9. Nightly's are for everyone. CM makes a few tweaks to their code and pushes it to each nightly. Some tweaks make it better, some tweaks make it worse. If you are satisfied with the release that you currently are running, you don't need to flash the update if you don't want to. Since you would be flashing an update, you just flash it, no backups of apps. Now if you were going from CM11 down to CM10, 10.1, or 10.2, then yes, back them up b/c you'd wipe those partitions before flashing the ROM.
Sent from my MB886 using XDA Free mobile app
palmbeach05 said:
Since you would be flashing an update, you just flash it, no backups of apps. Now if you were going from CM11 down to CM10, 10.1, or 10.2, then yes, back them up b/c you'd wipe those partitions before flashing the ROM.
Click to expand...
Click to collapse
How would I go about updating without losing anything? Do I just boot into recovery, wipe only delvik cache, and flash cm-11-20140810-NIGHTLY-moto_msm8960_jbbl.zip? Or is there a separate file just for updating? If I don't have to set everything up all over again after each nightly then I will gladly keep updating and providing feedback.
Fanarkle said:
How would I go about updating without losing anything? Do I just boot into recovery, wipe only delvik cache, and flash cm-11-20140810-NIGHTLY-moto_msm8960_jbbl.zip? Or is there a separate file just for updating? If I don't have to set everything up all over again after each nightly then I will gladly keep updating and providing feedback.
Click to expand...
Click to collapse
You can just clear cache in recovery then flash the update and it would keep all of your settings, data, everything the same. It is not recommended. If you have enough space, you can nand backup your current version and that eliminates the risk of losing everything if updating doesn't work, but it's recommended that you wipe cache and wipe data before flashing a new nightly. I've rarely had a problem flashing a nightly on top of my existing build without wiping data, but to each his own.
Just make sure you're flashing the jbbl nightlies and you should be fine.
Dr. Orange said:
You can just clear cache in recovery then flash the update and it would keep all of your settings, data, everything the same. It is not recommended. If you have enough space, you can nand backup your current version and that eliminates the risk of losing everything if updating doesn't work, but it's recommended that you wipe cache and wipe data before flashing a new nightly. I've rarely had a problem flashing a nightly on top of my existing build without wiping data, but to each his own.
Just make sure you're flashing the jbbl nightlies and you should be fine.
Click to expand...
Click to collapse
When you say "clear cache", do you mean "wipe cache partition," "format /cache," or "wipe delvik cache?" So basically what you are saying is that it is possible to flash a nightly on top of an existing build without losing anything but it is generally not recommended? I always create a backup image before I flash anything so no problem there.
Yes. Wipe cache. It will format automagically. You can wipe dalvik cache as well. Usually I just select the first "wipe cache" option in clockworkmod recovery then start flashing. Works 99% of the time.
Some say they develop problems doing it that way, but I've never had an issue with it. Maybe my phones (I had a moto bravo before the atrix hd) just like me.
Fanarkle said:
So basically what you are saying is that it is possible to flash a nightly on top of an existing build without losing anything but it is generally not recommended? I always create a backup image before I flash anything so no problem there.
Click to expand...
Click to collapse
Dr. Orange said:
You can wipe dalvik cache as well. Usually I just select the first "wipe cache" option in clockworkmod recovery then start flashing. Works 99% of the time.
Some say they develop problems doing it that way, but I've never had an issue with it. Maybe my phones (I had a moto bravo before the atrix hd) just like me.
Click to expand...
Click to collapse
The method of flashing over-top of an existing ROM is referred to as "dirty flashing". The issue isn't so much that it's not recommended or that it develops problems, but it could potentially develop problems, because there's always a chance that the new build relies on some random file that should have been deleted, changed, etc.
So, in summary, it's perfectly fine to dirty flash a CM nightly over your existing version, especially if it works fine for you. HOWEVER, if you develop problems, then you should refrain from reporting them until you have done a CLEAN wipe of everything and installed clean from scratch. If you still have an issue after a clean install, then feel free to report any issues as "bugs."
quasihellfish said:
if you develop problems, then you should refrain from reporting them until you have done a CLEAN wipe of everything and installed clean from scratch. If you still have an issue after a clean install, then feel free to report any issues as "bugs."
Click to expand...
Click to collapse
OK, thanks. What is the best avenue and method of reporting bugs if I do find any after a clean install? xda-forums? Cyanogenmod.org? Directly from the phone?
Fanarkle said:
OK, thanks. What is the best avenue and method of reporting bugs if I do find any after a clean install? xda-forums? Cyanogenmod.org? Directly from the phone?
Click to expand...
Click to collapse
Depends on how confident you are
I usually just ask/report in the appropriate XDA thread and look for feedback. There is a thread for the Atrix HD, but the thread for the RazrHD is much more active. You'll get a lot more activity and responses in the RazrHD thread because it's essentially the same device, just be sure to note that you're on the JB bootloader.
I suppose if you're really sure of a "bug", you could always report it at cyanogenmod.org, but I've never felt to be in the right position to do that.
quasihellfish said:
Depends on how confident you are
I usually just ask/report in the appropriate XDA thread and look for feedback. There is a thread for the Atrix HD, but the thread for the RazrHD is much more active. You'll get a lot more activity and responses in the RazrHD thread because it's essentially the same device, just be sure to note that you're on the JB bootloader.
I suppose if you're really sure of a "bug", you could always report it at cyanogenmod.org, but I've never felt to be in the right position to do that.
Click to expand...
Click to collapse
Thanks, I will stick with XDA then :good: I was looking at jira.cyanogenmod.org and I can't figure out how to report anything specific to a nighly build anyway What is the useful/relevant information that I should post (besides what build I am running) to be the most helpful? i.e. How do I generate a log/report with all the relevant info?
Fanarkle said:
Thanks, I will stick with XDA then :good: I was looking at jira.cyanogenmod.org and I can't figure out how to report anything specific to a nighly build anyway What is the useful/relevant information that I should post (besides what build I am running) to be the most helpful? i.e. How do I generate a log/report with all the relevant info?
Click to expand...
Click to collapse
Well, then I just recommend sticking with XDA. If one of the real CM devs/maintainers then recognizes a bug, someone will report it. Or re-ask this question over there, and they can help you.
Why this topic is still open?
Where are the forum admins?
Sent from my GT-I9505 using XDA Free mobile app
RatusNatus said:
Why this topic is still open?
Where are the forum admins?
Click to expand...
Click to collapse
Did I do something wrong? I am creating a backup and "dirty" flashing the latest nightly right now. I was going to post how it went after I finished just so other people would have the info if they were looking for it.
Success! I rebooted into recovery and, after creating a backup, performed "wipe cache partition" and "wipe delvik cache" before installing cm-11-20140811-NIGHTLY-moto_msm8960_jbbl.zip on top of the build I was running. I rebooted and everything is as it was, except that my custom boot animation was reverted back to CM default (which was expected, no big deal) and the new version I flashed is correctly shown on the "About phone" screen. If I encounter any issues going forward, I will post in the appropriate thread.
Fanarkle said:
Did I do something wrong?
Click to expand...
Click to collapse
No.
RatusNatus said:
Why this topic is still open?
Where are the forum admins?
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
Why did you post here if you had nothing constructive to say?
I'm glad you got it to work fanarkle[emoji4]
Related
Please use this thread for all your discussion about the Nightly builds for CM7 for the Atrix.It is important to note that Nightly Builds are not for most Users
Things to know about Nightly Builds:
Not Stable releases
Will have bugs / issues
Not intended to be used as main everyday ROM
Are not Fully Supported like Stable Releases
Should not be used by people that are not Masters of ADB
You Should be comfortable enough to recover from soft bricks On your OWN
90% chance you will be wipping your data (factory reset) at some point and time
DO NOT REPORT ISSUES ON NIGHTLIES ON THE BUG TRACKERFAQ FOR ATRIX NIGHTLY'sNightly builds can be found here:
http://download.cyanogenmod.com/?device=olympus
Also would like to add that BACKUPS are your friend if you are not comfortable with t0dbld's sugestions. Thanks for starting this thread and for the teams dedication.
Is or are the Dev team also creating different tweaks/builds seperate from Cyanogenmod or will the teams work just be incorporated into the nightly builds?
Excellent! Allrighty, lets kick off this party with a bang. First off, thanks to all the Devs and others who made this a reality. Nightly builds = awesome. After installing this with the latest version of Gapps, everything is working beautifully. Very excited to see where this is going. Faux123's stopgap kernels WILL work with this build so far and I have tested them. Only thing I've noticed so far is that, for the first time for some reason, I am unable to buy an app from Market and bill it to my AT&T account. Option seems to have disappeared. I've heard of others discuss this, and I'm assuming that the change language to English fix will work with this, but haven't tried it yet. Umm...ring lock screen seems to be working with less lag than before. Other than that, have nothing else to report at this time. Thanks again all, and happy flashing!
Phalanx7621 said:
Excellent! Allrighty, lets kick off this party with a bang. First off, thanks to all the Devs and others who made this a reality. Nightly builds = awesome. After installing this with the latest version of Gapps, everything is working beautifully. Very excited to see where this is going. Faux123's stopgap kernels WILL work with this build so far and I have tested them. Only thing I've noticed so far is that, for the first time for some reason, I am unable to buy an app from Market and bill it to my AT&T account. Option seems to have disappeared. I've heard of others discuss this, and I'm assuming that the change language to English fix will work with this, but haven't tried it yet. Umm...ring lock screen seems to be working with less lag than before. Other than that, have nothing else to report at this time. Thanks again all, and happy flashing!
Click to expand...
Click to collapse
Hi, May i know this rom can support the Fingerprint and the webtop?
what the different with another CM7 (non nightly ver) , quite blur here.
thanks.
You might find it being offered by someone willing to make a workaround to get it to work. Being that "Android" didn't put the fingerprint scanner in the phone and no other phone has one, you'll have to wait for someone to actually make a script that can be added to CM7.
NP...
Does Cyanogenmod or Dev Team post changelogs about each update/nightly?
Phoneguy589 said:
NP...
Does Cyanogenmod or Dev Team post changelogs about each update/nightly?
Click to expand...
Click to collapse
https://cm-nightlies.appspot.com/?device=olympus
Are we going to see nightlies on Rom manager?
-CM7.1 -B^-N Over Clocked via Faux123 1.45ghz V2.1 THANKS XDA DEV!
I'm already seeing the Nightlies on ROM Manager. In fact, just downloaded Nightly 3 and I'm installing as we speak.
I'm seeing things about "FM Radio" on the nightly change log. Does the atrix have FM Radio capabilities?
CancerJesus said:
I'm seeing things about "FM Radio" on the nightly change log. Does the atrix have FM Radio capabilities?
Click to expand...
Click to collapse
No it does not have capability
I've been running full #2 today, full wipe. Only problem I've had is battery life. I could get 24+ hours with the previous betas...I'll be lucky to get 10 at this rate. Nothing in the stats stands out. Guess I'll wipe and install #3 tonight and see how it goes.
Anyone getting Market FC all the time as soon as they try to download an application? Should I reboot my phone and see if that fixes the problem?
crea78 said:
Anyone getting Market FC all the time as soon as they try to download an application? Should I reboot my phone and see if that fixes the problem?
Click to expand...
Click to collapse
Change Language to "English"
Usually the fix...
crea78 said:
Anyone getting Market FC all the time as soon as they try to download an application? Should I reboot my phone and see if that fixes the problem?
Click to expand...
Click to collapse
I got that when I updated to the stopgap version. Just use Titanium Backup to backup your market apk and then uninstall it. Restore it and use the "App Only" option and do not restore data. After its done simply open Market and add your account.
You're good to go after that.
I wasn't sure if I'd run into any challenges with the latest nightly, but nope! Running smooth as butter. Using faux's latest 1.45ghz OC kernel too. Didn't wipe from scratch, just cleared Dalvik cache and hoped for the best lol (and did a backup of course)
I'm running nightly #2 should upgrade to #3?
sent from cm7 atrix 1.3ghz
michaelatrix said:
I'm running nightly #2 should upgrade to #3?
sent from cm7 atrix 1.3ghz
Click to expand...
Click to collapse
Not worth it
XAviierG said:
Dudes he didn't ask if the finger print scanner works he just said he didn't STOP FLAMING
Click to expand...
Click to collapse
sublimejosh2000 said:
I hope this thread doesn't turn into what the other one did,who gives a rats @$$ about the stupid Finger Print Sensor? When it is working, it will be added, not anytime sooner. I threw up in my mouth when I saw that post ...
Click to expand...
Click to collapse
Not looking to start a war here but lets do some Math:
XAviierG= March 2011 join date ; # of posts 2624 or aprox 403.69 a Month
sublimejosh2000 = Dec 2010 join Date : # of posts 351 or aprox 35.1 a month
I think its safe to say that at least one user is not spending his life "flaming" others or making a lot of pointless posts, etc. Lets watch who plays police in these forums because as you can see not so many are doing it right them selves
I'm running #3 and its smooth as butter, thanks for the hard work y'all put into the atrix! Y'all rock
Sent from my MB860 using xda premium
Please note! Due to certain issues, as of 08/26 I have moved on to the official CM10. If time permits, I'll update this OP, but not making promises.
WARNING: This ROM probably still has intermittent emergency dialing issues. Do not use it for a daily driver when you're out or could need 911 or any emergency number. If you STILL choose to use it at those times, it's your own fault!
Let's get this out of the way:
This thread is for DEVELOPMENT! If you have non-development questions...which is just about everything that seems to show up anymore.....go to the following thread:
http://forum.xda-developers.com/showthread.php?p=28730705
From DerTeufel1980:
I want to present to you the Helly_Bean ROM. The following description is taken from the original thread over in the i9000 section. You can find his thread here:
http://forum.xda-developers.com/showthread.php?t=1775169
This ROM is not the official built of CM10 by Teamhacksung.
It is based on their source code, but with some modifications, to allow the use of /datadata partition
Click to expand...
Click to collapse
Many many thanks, to pawitp, FaultExeption, Jt1134 and all the other people who commit to gerrit. without these, this ROM wouldn't be possible
What's not working or known bugs?
[FIXED]- toggling the GPS repeatedly will reboot phone.
[FIXED]- mounting of external sd to pc (you can switch to mtp mode in recovery to "fix" this).
Click to expand...
Click to collapse
******************
Build 08/20 is showing as available. I don't recommend dl'ing it as its caused many to have baseband issues. I've contacted Der to look into this, which I'm sure he will when time permits.
(08/17)New build available.
This is md5 sum:
cd703c25d560ce4c3d33cbfcab724427
Changes:
- compiled from latest sources, but still using /datadata (going to be change probably soon)
- renamed the two navbar menus
- added Facebook sync (you have to install Facebook app before)
- added i9000b to supported devices
- (hopefully) fixed modem/baseband issue
- added possibility to install devil kernel apps to installer
- fixed mms for showcase
http://rootaxbox.no-ip.org/derteufel/Helly_Bean/rom/
Wipe not needed if flashing from a previous version, but is highly recommended. Be sure to flash the add-on also.
TF here.....I found, as often is the case, I had to flash the ROM and let it boot up, then go back in and flash the add-on. After that.....golden!
(08/15)New test build up now.
Why test build?
- Because I have added two new devices, for which I don't know if it is working well for them
- I have fixed the navbar not appearing, but now there a two menus in system which both are named the same. One is for enabling, the other for customization. I am working at integrating the two into one menu, but I did not get it yet.
- ffc support for Vibrant
Install process has not changed, but if you are coming from another ROM/kernel than mine, you should create a folder devil at your sdcard, place a file named device into it, and write your device name in it, valid names are:
i9000
cappy
vibrant
fascinate
mesmerize
showcase
users of mesmerize and showcase have to do this!
Other changes:
If devil app(s) are not installed, the menu is not displayed under system settings (many thanks to phillbring for coding me this).
md5sum is: 3b11a106529f10236d2e6139416bc346
http://rootaxbox.no-ip.org/derteufel/test/
Wipe not needed if flashing from a previous version, but is highly recommended. Be sure to flash the add-on also.
From TF: I love the Cid theme from Annex, but flashing his most recent version sent me into bootloops. I'm assuming he will update as soon as he has a chance.
(08/13) New instructions for flashing. Wipe not needed if flashing from a previous version, but is recommended. Be sure to flash the add-on also.
The files can be found at:
http://rootaxbox.no-ip.org/derteufel/Helly_Bean/
Install instructions:[/SIZE]
Coming from any other rom:
- make sure to have gingerbread bootloaders. (Remember, Google is your friend)
- wipe data/factory reset
- flash allinone.zip
- reboot recovery
- flash allinone.zip again
- flash Helly_Bean_AddOn or Helly_Bean inverted AddOn
coming from previous version:
- flash allinone.zip
- flash Helly_Bean_AddOn or Helly_Bean inverted AddOn
Attention: this is still a test. Don't flash it if you don't know what you are doing/how to get back!
For a new feature cherry-picked last night, go to settings --> system
*************************
You can find the official website for this project here (I don't maintain the site myself, if there is anything website related to ask, please use the contact info from the web site):
http://hellybean.site11.com/download.html
You'll find download links and faq on this site.
The usual back-up, complete wipe (if this is the first time flashing this ROM), flashing of files and fix permissions applies.
***********
One thing I noticed is that if you follow the normal flash procedure, it can bootloop, or at least appears as though it is. One way to fix that is to flash the ROM only and boot up you phone. Then go back into recovery and flash the add-on. That has worked every time it happened to me.
You can find the changelog here:
http://hellybean.site11.com/changelogg.html
For mirrors, please take a look at the thread. if you don't find any, just ask in the thread.
I really didn't want to mention this, but lack of experience by some members seems to require it:
If you are unsure of ANYTHING that goes with flashing a ROM, do research first. If you honestly can't find the answer, ask questions. We are not responsible for any action that happens to your phone.
Many thanks to:
- be18
- mkalter, who got the first running JB ROM
- elitemovil (who was the first who got gsm working)
- stratosk (from who's initramfs I could start build my first JB booting kernel)
- teamhacksung/pawitp for the ROM sources
- team nyx who always have good tips for me, if i get problems with my kernel
- SysTem-X for hosting
- Rootax for hosting
- RolluS for hosting
- many thanks also to the other people who have created mirrors
- if i have forgotten you, please PM me
If you consider a donation for this ROM and kernel, please follow this link:
donate to DerTeufel1980
________________________________
Now, from TFordham (you can just call me TF):
I've been using this ROM for some time now, and really happy with it. Personally, I think this is the best JB ROM out there. I find it very smooth, and for an early release, quite stable.
I do want to point out that I'm not a dev at all. The Helly Bean ROM is from DerTeufel1980 and his team. I put this up since his ROM is being mentioned in another ROM forum, but figured it might as well have its own home
Something else I want to be clear about is that I have no technical knowledge on creating ROMs, kernels or other things of this nature. I simply wanted to let other Vibrant owners know this ROM is out there. This fantastic XDA community is the place to ask, as there are plenty who know FAR more than I. In addition, DerTeufel1980 is active in this forum, ago if there are issues, he will help address them. While I appreciate the "thanks" button being hit, it is his comments in this thread that should be thanked.
Sent from my SGH-T959 using xda app-developers app
HellyBean 0801 is definitely the fastest JB ROM for the Vibrant because of the included Devil 1.1.0 kernel and the use of the faster datadata partition. All Vibrant users should donate to Derteufel1980 for his amazing kernel and now ROM support. He is the only ICS/JB kernel developer we have right now so we must treat him right.
How does this differ from the CM10 v8? Other than the kernel of course.
gunks said:
How does this differ from the CM10 v8? Other than the kernel of course.
Click to expand...
Click to collapse
Keeping in mind I'm far from the most tech savvy flasher out there, like I mentioned, I don't see a huge difference in most of the JB ROMs. I just happen to like this one a lot. Others may be able to get into far more detail on why it's good compared to other (or vice versa, for that matter, if they feel that's the case).
Sent from my SGH-T959 using xda app-developers app
More info here http://hellybean.site11.com/
hurtz777 said:
HellyBean 0801 is definitely the fastest JB ROM for the Vibrant because of the included Devil 1.1.0 kernel and the use of the faster datadata partition. All Vibrant users should donate to Derteufel1980 for his amazing kernel and now ROM support. He is the only ICS/JB kernel developer we have right now so we must treat him right.
Click to expand...
Click to collapse
There is no link to Devil 1.1.0. I can see a folder, but it is empty. I do see and know that Devil 1.0.4 works.
chadhoard said:
There is no link to Devil 1.1.0. I can see a folder, but it is empty. I do see and know that Devil 1.0.4 works.
Click to expand...
Click to collapse
The kernel is in the ROM...you don't need to flash it separately.
Sent from my SGH-T959 using xda app-developers app
TFordham said:
The kernel is in the ROM...you don't need to flash it separately.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Good to know!! Now, I flashed the ROM, Kernel 1.0.4, and add-ons yesterday. Can I just flash the ROM without wiping?
chadhoard said:
Good to know!! Now, I flashed the ROM, Kernel 1.0.4, and add-ons yesterday. Can I just flash the ROM without wiping?
Click to expand...
Click to collapse
Again, not a techy. Give it a try, just do a back-up first. I tend to always do a full wipe. Seems like ROMs just run better that way, IMO.
Sent from my SGH-T959 using xda app-developers app
TFordham said:
Again, not a techy. Give it a try, just do a back-up first. I tend to always do a full wipe. Seems like ROMs just run better that way, IMO.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Thanks!
Its nice too see an official home/thread for helly bean. Thanks to everyone involved!
Der Teufel nennt mich bruder.
drool on my chin from a mouth full of jellybeans....
Nice
So far so good. No problems at all. Just waiting 15 mins b4 I reboot and play with it. Why 15 mins cause files are still installing. Stay thirsty my friends.
shownuff said:
So far so good. No problems at all. Just wa 15 mins b4 I reboot and play with it. Why 15 mins cause files are still installing. Stay thirsty my friends.
Click to expand...
Click to collapse
Delete...I misunderstood what you were saying.
I think that DerTeufel has to be the OP.
Did you ask him before put this?
Are you able to answer questions about Kernel, ROM, Modems, UV, NL etc?
Update the proper content of our device?
This is why the "leader team" or the Dev has to be the OP.
Not trolling, just saying: If we want a better Topic it has to be created by DerTeufel.
Waldos said:
I think that DerTeufel has to be the OP.
Did you ask him before put this?
Are you able to answer questions about Kernel, ROM, Modems, UV, NL etc?
Update the proper content of our device?
This is why the "leader team" or the Dev has to be the OP.
Not trolling, just saying: If we want a better Topic it has to be created by DerTeufel.
Click to expand...
Click to collapse
Thanks for your concern. I've contacted him. If he wants anything changed, or even to have it closed, I'm sure he'll let me know.
Sent from my SGH-T959 using xda app-developers app
hurtz777 said:
HellyBean 0801 is definitely the fastest JB ROM for the Vibrant because of the included Devil 1.1.0 kernel and the use of the faster datadata partition. All Vibrant users should donate to Derteufel1980 for his amazing kernel and now ROM support. He is the only ICS/JB kernel developer we have right now so we must treat him right.
Click to expand...
Click to collapse
We have like 3 other devs with functional jb ROMs.
Sent from my SGH-T959 using xda app-developers app
This download. Is FRICKING SLOW.
Sent from my SGH-T959 using xda app-developers app
How's the battery life on this rom? Im getting amazing battery on CM10 Alpha Preview by FE with Devil 1.0.4 test3 JB kernel. I wanna know if this battery's any good before I switch.
Can someone quickly summarize how to get here from Stock? I had done it a long time ago to the ics roms and can't do it again... I"m missing some major step.
So far:
heimdall to stock
root update.zip
install rommanager and then cwm install and re-boot to flash update.zip -> cwm recovery.
Flash this rom
-> results in boot loop.
What am I missing?
spybld said:
Can someone quickly summarize how to get here from Stock? I had done it a long time ago to the ics roms and can't do it again... I"m missing some major step.
So far:
heimdall to stock
root update.zip
install rommanager and then cwm install and re-boot to flash update.zip -> cwm recovery.
Flash this rom
-> results in boot loop.
What am I missing?
Click to expand...
Click to collapse
My experience from going all the way back to stock is that I had to flash a Gingerbread ROM first, then wipe that and install a later ROM (ICS, JB).
Sent from my SGH-T959 using xda app-developers app
Hi all,
I am currently using CM10.2. I am happy with it, but I might need MHL for somehow. Can I flash back and fore between CM10.2 to Stock without wipe my cache and data and I get
1, stable enough to run on both ROM
2, Personal data still good(still keeping like whatsapp history, contact data etc)
I am not brave enough to test by myself, hope anyone can help. Thanks
Mike
ekimkam said:
Hi all,
I am currently using CM10.2. I am happy with it, but I might need MHL for somehow. Can I flash back and fore between CM10.2 to Stock without wipe my cache and data and I get
1, stable enough to run on both ROM
2, Personal data still good(still keeping like whatsapp history, contact data etc)
I am not brave enough to test by myself, hope anyone can help. Thanks
Mike
Click to expand...
Click to collapse
You can try it but you will for sure get a bootloop, especially with stock and custom rom. This way you are maybe able to change between custom ROMs with same android version, but stock is older than CM 10.2.
Sent from my LG-P880
Omario-242 said:
You can try it but you will for sure get a bootloop, especially with stock and custom rom. This way you are maybe able to change between custom ROMs with same android version, but stock is older than CM 10.2.
Sent from my LG-P880
Click to expand...
Click to collapse
What you mean of bootloop is that you can't even make the device running without wipe?? Hey man, If I have the guts to try I will not ask. Haha..=)
Thanks anyways..
Mike
ekimkam said:
What you mean of bootloop is that you can't even make the device running without wipe?? Hey man, If I have the guts to try I will not ask. Haha..=)
Thanks anyways..
Mike
Click to expand...
Click to collapse
That's what I meant the differences between android version are to big and especially if you have a stock and a custom rom. Too many files/file paths are different and your system will screw up. It will boot, show the LG logo and reboot. That's why every single custom rom thread has the wipe part in it's instructions.
Like I said you can try it but I see no chance. I did it once between two custom ROMs (both CM 10.1) and even that didn't work out good.
It booted but every single app and system itself force closed repeatedly.
Sent from my LG-P880
Im running an mb886 using the CM11 and Carbon nightlys. ive been using the CM11 JBBL nightlys and was wondering if there is any reason to jump up to a KKBL. and if so is there a guide. alas the search feature did nothing for me.
disregard i found it.
disappointing that i cant move to the KKBL.
currently I have carbonrom on my phone. do the CM11 nightlys for JBBL mirror the other ones or are they behind?
oscar the grouch said:
currently I have carbonrom on my phone. do the CM11 nightlys for JBBL mirror the other ones or are they behind?
Click to expand...
Click to collapse
CM11 nightlies are based on the same build for both JBBL and KKBL bootloaders. The build server runs every night and uses the same code base for both of them.
p.s. If you're ever in doubt, you can always check the changelogs for both the JBBL and KKBL builds.
Thank you.
I tired the aospb build rom earlier. For some reason it kept giving me unfortunately blah blah quit. Apparently my itialian input method. (Not Italian) kept shutting off. And everything I tried from my titanium backup and the playstore crashed every time I opened it. Can't ask inthe rom thread so I sent back to carbon. Any thoughts
oscar the grouch said:
Thank you.
I tired the aospb build rom earlier. For some reason it kept giving me unfortunately blah blah quit. Apparently my itialian input method. (Not Italian) kept shutting off. And everything I tried from my titanium backup and the playstore crashed every time I opened it. Can't ask inthe rom thread so I sent back to carbon. Any thoughts
Click to expand...
Click to collapse
Sorry, but I have no idea what you're trying to say. I've used both Carbon and CM11 on my phone without issue (currently on CM11 nightly).
If I had to take a wild guess about your issue with Playstore crashing, you probably need a newer/more compatible version of the Google Apps installed. Not sure what you installed, but the PA Gapps are always up to date. Start with the Mini or Micro packages and work from there.
Or ask a new question in the Q&A forum.
I was using the pa micro. Still am. Something about the aospb rom didn't like me. I flashed it with out gapps and it still.crashed every non system app. It was better when not running the app data on a partition but still not good. Currentlyrunning the carbon nightly with zero issues
oscar the grouch said:
I was using the pa micro. Still am. Something about the aospb rom didn't like me. I flashed it with out gapps and it still.crashed every non system app. It was better when not running the app data on a partition but still not good. Currentlyrunning the carbon nightly with zero issues
Click to expand...
Click to collapse
With some ROMs, I was having an issue with the dialler whereby I would need to press the # key three times in a row to get the keypad to appear. Have you ever experienced this issue?
audit13 said:
With some ROMs, I was having an issue with the dialler whereby I would need to press the # key three times in a row to get the keypad to appear. Have you ever experienced this issue?
Click to expand...
Click to collapse
have not. that is weird. how do you get a #key with out a dial pad tho?
Q&A for CM11 based on 4.4.2 OTA
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Thanks!
JackpotClavin said:
K I'm back on my CM11 builds. New build will be released tomorrow if I have time!
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
This is a really nice ROM. I bought a VS980 (for cash, even) and was disappointed that Cyanogenmod didn't seem to be maintaining the build for it anymore. Battery life is so good I thought the battery meter was broken at first. I'm seeing 75% full at the end of a typical day of calls and texts and apps.
Thanks a lot for making this!
Is the OCT 13th build using 26a binaries, drivers and kernel?
Sent from my VS980 4G
I'm on 24a on paranoid android. Can I just go ahead and flash this like I do any other ROM or do I need to follow all the steps on the front page?
Sent from my LG-VS980 using XDA Free mobile app
babygetoboy said:
I'm on 24a on paranoid android. Can I just go ahead and flash this like I do any other ROM or do I need to follow all the steps on the front page?
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
Just flash it is fine.
Curious what those on CM and CM based Roms are using for SMS..the stock app only sends compressed pictures that look like garbage. How are you all sending uncompressed? Personally I've been using Textra, but would prefer to mod stock SMS if possible...anyone?
What's the point of this thread? I don't understand what to ask here instead of in the original thread.
CaptainElwood said:
What's the point of this thread? I don't understand what to ask here instead of in the original thread.
Click to expand...
Click to collapse
Kinda wondering the same thing. I guess it's good for people who don't have enough posts to use the development thread, on the other hand it splits conversations about the rom to two different places. I could understand if the developer specifically asked for all Q & A to go here but I don't think that's the case is it?
CaptainElwood said:
What's the point of this thread? I don't understand what to ask here instead of in the original thread.
Click to expand...
Click to collapse
Based on the OP and the name of the poster, I'm guessing this is automated by XDA.
I think threads like these could be useful. For instance the question I posed above in no way contributes to the development of a ROM, it's features, or is a bug that needs sorting out.
Lately I've noticed mods pointing those who ask questions in a development thread to Q&A threads like this..I can only guess that XDA prefers things in this direction now.
Hope this isn't too dumb a question.
So I've been reading a LOT of this thread and I just need to clarify a few things.
First, I have the 26A build and cannot flash the regular CM11 (I get stuck in the LG boot loop) so this is how I found this thread. Now, is this thread specifically for a special build of CM that gets around this problem? The last 20 pages or so are more about bugs and things within this build so I'm getting a little confused on if this is actually the thread and build I need.
Second thing: If this IS the zip I need for my boot loop problem, can I simply flash it in recovery or do I need to go through the steps in the OP? I saw someone ask this question a few pages back but didn't really understand the answer. If it's as simple as a flash of the zip, whey would the long string of instructions still be in the OP? Thank you for clarifying.
Third thing is: If I flash this build and the official CM builds later somehow work with the 26A firmware, can I simply flash the new, official CM build(s) or will I need to wipe and install the official build clean?
Thank you for answering these annoying questions. I've literally spend the last 3 days trying to root and boot and finally found this thread and spent the last day reading up on it.
blue duck butter said:
So I've been reading a LOT of this thread and I just need to clarify a few things.
First, I have the 26A build and cannot flash the regular CM11 (I get stuck in the LG boot loop) so this is how I found this thread. Now, is this thread specifically for a special build of CM that gets around this problem? The last 20 pages or so are more about bugs and things within this build so I'm getting a little confused on if this is actually the thread and build I need.
Second thing: If this IS the zip I need for my boot loop problem, can I simply flash it in recovery or do I need to go through the steps in the OP? I saw someone ask this question a few pages back but didn't really understand the answer. If it's as simple as a flash of the zip, whey would the long string of instructions still be in the OP? Thank you for clarifying.
Third thing is: If I flash this build and the official CM builds later somehow work with the 26A firmware, can I simply flash the new, official CM build(s) or will I need to wipe and install the official build clean?
Thank you for answering these annoying questions. I've literally spend the last 3 days trying to root and boot and finally found this thread and spent the last day reading up on it.
Click to expand...
Click to collapse
1.Official CM is still using 4.2 sources.
2. Yes, just wipe and flash this then gapps. Ignore all the complicated instructions, they're outdated.
3. I'd recommend a clean flash, but, yes, when/if CM finally updates to true kitkat sources.
jesssiii said:
1.Official CM is still using 4.2 sources.
2. Yes, just wipe and flash this then gapps. Ignore all the complicated instructions, they're outdated.
3. I'd recommend a clean flash, but, yes, when/if CM finally updates to true kitkat sources.
Click to expand...
Click to collapse
Great! Thanks for clarifying. Is the CM team slow at updating the sources? I was under the impression that CM worked fairly quickly. From what I gather, the VS98026A build has been around for about a month, correct? Also, does that mean 26A is the first firmware from LG built on 4.4?
blue duck butter said:
Great! Thanks for clarifying. Is the CM team slow at updating the sources? I was under the impression that CM worked fairly quickly. From what I gather, the VS98026A build has been around for about a month, correct? Also, does that mean 26A is the first firmware from LG built on 4.4?
Click to expand...
Click to collapse
24A was first, then 2nd, then 26A. Not all were official. As far as CM goes, I don't know.
Getting same error message as other user
I have fewer than 10 posts so I can't post in the forum but I'm getting the same error message that user AO4EVER was getting. Here is his post:
"Same error message with the new build
Can't install this package on top of incompatible data. Please try another package or run a factory reset. E: Error executing updater binary in zip's '/data/media/0/sideload.zip'
Anyone else is getting this? [Don't think it is due to build, something is off the device itself]" - AO4EVER
He was confused because nobody else was getting that error message. Well, that's the message I get when I try to flash JPC's build of CM11. I am rooted on stock 26A.
Does anyone know why this is happening? The user said he ended up deleting some of the verification code to get it to finally work. Can anyone explain how I would go about doing this? I don't know a ton but I feel comfortable enough in terminal/command prompt to make changes if I know what changes to make.
*EDIT* I deleted the part of the verification code that was preventing me from flashing JPC's CM11 build and have successfully flashed it now.
Just updated to 20141026, GPS is broke (was broke on an earlier Oct build). I see others confirming GPS working, how do I test to make sure I don't have bad hardware?
laf gets overwritten
The aboot and boot replacement works fine. The md5sums match over many reboots. However, something keeps overwriting the laf file. I tried replacing mmcblk0p24 directly, and the md5sum for that and the laf symlink in by-name are correct, but when the phone reboots something has overwritten it. I also made a copy of mmcblk0p24 in the block folder, and strangely that gets deleted on reboot as well. But aboot and boot keep the changes. Weird. Do you know what could be causing this?
updating
If i followed this guide to install the cm 11 m11 build and i want to update to m12 how do i do that
boggsmicah said:
If i followed this guide to install the cm 11 m11 build and i want to update to m12 how do i do that
Click to expand...
Click to collapse
Wipe and flash rom and gapps as usual.
LG G2 VS980
I have the same problem with screen off during call after screen timeout has elapsed, did u manage to get it fixed? im on 26A and im using 2014 11 02 nightly build, M12 gave me call drop so i opted for the nightly
CM 11 (M12) vs980 Camera w Flash problem
Hello all,
So, i've been running the latest builds of CM 11 4.4.4 through the help of JackpotCalvin's write up and kernel exploit.
I figure I should ask if anyone else has had some issues with the camera and taking pictures with flash enabled?
for whatever reason the white balance is faulty with flash enabled and the pictures come out whitewashed. It didn't used to do this with previous updates (before the M12 stapshot).
maybe something is bogging down performance and i dont realize it. Anyway, thanks for any feedback.
-Mike M