Database Info

whatsapp problem on CM9

Hello!
I flashed CM9 RC2 recently and now whatsapp doesn't work. I get warning after installing it saying that custom rom might cause whatsapp not to work properly. After starting whatsapp it simply closes down.
Before CM9 RC2 i used HyperSensation Rom (2.9 i think), and it worked normally without any problems.
Is there anything i can do to get this to work besides reflashing ROM?
Thank you.

Delete the data of the app.. Un-install it and install it again that might help
Sent from my pyramid using blazing fast sonic waves

Tried that several times. Problem still persists.
EDIT: Just to report. Eventually i installed latest AOKP rom from their site (Milestone 6), and it works fine now.

ive had this same problem. I am usuing the CM9 RC2 right from the cyanogen mod website for samsung captivate ATT. if i install the AOKP rom you think it will work. and if i do whats the difference between AOKP build 40 and milestone 6.
edit: ok i installed milestone 6 and still did not work. what the hell

hshaikh said:
ive had this same problem. I am usuing the CM9 RC2 right from the cyanogen mod website for samsung captivate ATT. if i install the AOKP rom you think it will work. and if i do whats the difference between AOKP build 40 and milestone 6.
edit: ok i installed milestone 6 and still did not work. what the hell
Click to expand...
Click to collapse
AOKP builds marked with number (for example: build 40) are something like beta builds and are more likely to have bugs. Milestone builds are more stable releases.
Regarding problem with whatsapp. Seriously i dont know why is this happening. I tried searching net and found couple guys with same problem but nobody offered solution. As i said in my first post, i used hypersensation which was build on one of earlier CM9 releases and it worked fine. So i would suggest to try some earlier releases of AOKP or CM9 or some rom from XDA based on them.

could you please provide me with a link to the rom you used. i will try that one

Here is hypersensation. However i used 2.9 version based on CM9, current version is 3.1. Download is in post 2. In post 3 you can find AOKP roms, but i haven't tried these.

I am using a samsung Captivate. will this rom work for me

My guess is no. You should probably go to Samsung Captivate forum and check there. I don't know anything about Captivate.

[OFFICIAL]CM10 Official Nightlies for D2VZW GSIII

-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
See the 9-11-12 Cyanogenmod Announcement at bottom of post! There are now regular Nightlies you are used to and now the M-Series Roms, I will let the CM Team speak for it themselves as to what it is, see quote and link at bottom of post.
As of 8-18-12, the Verizon Galaxy S III, yes the one with the formerly locked bootloader that everyone loved to hate, has now been accepted into the Official CM10 Jelly Bean Nightly builds. Bookmark THIS PAGE to check for the latest nightlies. Many thanks to everyone involved in getting the d2vzw this far including you, African Canadian Sock Monkey!
Official Announcement from Cyanogenmod 8-18-12
Today we kick off the nightly builds of the CM10 JellyBean code branch, builds will show up later this evening.
CM9 nightly builds for devices that don't receive a CM10 nightly will continue (for the meantime) but we are changing the timing on them to be once a week instead (aka weeklies). This will allow a means for us to test bug fixes and the like as they get merged into the ICS branch - as stated before, the CM9 branch is in an otherwise perpetual code-freeze.
The devices receiving CM10 nightlies this evening include (but aren't limited to):
# The US SGS3 variants
# The Galaxy Nexus variants
# The Nexus S varaints
# The Nexus 7
# The Transformer and Transformer Prime
# The SGS1 variants (Vibrant, Captivate, International, and i9000b)
# The SGS2 i9100g
# P3 and P5 tablets
Other devices will join the roster as they become ready and gain their maintainers blessing for nightlies.
Edit d2vzw nightlies will require the insecure bootloader. See http://goo.gl/CST0K
Click to expand...
Click to collapse
Source
I didn't see a thread for this so I figured I would go ahead and create this thread for the discussion and following of the d2vzw Official CM10 Jelly Bean Nightlies. Our maintainer cvpcs has stated that the initial official nightlies may not have all of the fixes such as MMS fix in them until those fixes are merged into the official tree.
YOU MUST BE ROOTED:
I recommend using the Casual app from Adam in THIS THREAD.
YOU MUST BE UNLOCKED:
As stated the official version of CM10 nightlies for d2vzw requires you be on an unlocked Verizon GSIII. As an alternative to the Casual method Adam posted up, you can now unlock your device using a simple one-click app made by fellow dev mmmeff called VZW GS3 EZ-Unlock on the play store.
YOU MUST BE RUNNING A CUSTOM RECOVERY:
Also see his EZ-Recovery for VZW Galaxy S3 app for the easiest way to load any custom recovery you want. Please note the Touch CWM 5.8.4.9 available in the app doesn't play nice with CM10. Don't use it. I personally recommend using the CWM (non-touch) versions such as 6.0.1.2. If you prefer 6.0.1.2 Touch and want to flash it using the EZ-Recovery app using the "custom" option, simply flash this file using the app.
If you would rather not use that app, see THIS THREAD for CWM 6.0.1.2 files and install instructions.
blade7840 said:
Can I use TWRP recovery to flash this Rom?
Click to expand...
Click to collapse
Don't see why not. As usual, make sure you have a nandroid just in case. I previously stated TWRP Data Wipe was broken. Which is only partially true, because it FAILS for a REASON. If it worked it would format our internal sdcard! Proper use of TWRP would be to use the Factory Reset option which should take care of things. The Format Data option would be rather dangerous if it worked. So there you go.. It should work as well as CWM. More of a preference thing. You can find TWRP 2.2.2.0 in THIS THREAD. If you like using mmmeff's EZ-Recovery app and want to flash TWRP 2.2.2.0 using the custom option, use this file.
BECAUSE WE ARE NOW UNLOCKED, WE NO LONGER REQUIRE OR USE ANYTHING KEXEC
* In case anyone is still running CWM 6.0.1.0 from the kexec kernel days it is fine to use still. It functions as a standard custom recovery but had the additional ability to run kexec enabled kernels. So you can continue to use it or upgrade to another version. Because we are unlocked you are free to use any recovery now and Kexec is no longer applied.
So now all you need to do is root your phone, load up those two apps, load the recovery (i recommend the newest TWRP 2.2.2.0), unlock the device, and download and install the latest nightly in recovery.
GOOGLE APPS (including Play Store) ARE NOT INCLUDED IN OFFICIAL CM:
Make sure you also have a copy of the CWM flashable Google Apps on your ext sdcard which can be found HERE thanks to our friends at goo.im because CM doesn't come with Google Apps by default.
If you do a complete wipe and install an official CM10 build clean and you still have gapps remaining without having ever installed a gapps package, you likely didn't get a clean wipe. Recommend rebooting and wiping again and re-install.
WILL I LOSE MY IMEI IF I FLASH THIS?:
WizeGuyDezignz said:
Is there still a chance to lose your imei with these?
Click to expand...
Click to collapse
There is a chance you will lose your IMEI on these devices any time you flash anything. If you are not willing to accept the risk inherent in flashing your device, regardless of what you are flashing or what you are worried about, then DONT FLASH ANYTHING, remain stock, and locked. If you want to read more on the "how to" for IMEI backup and restore, see THIS THREAD for latest IMEI discussions and detailed methods for backup and restore.
CM OFFICIAL NIGHTLIES DO INCLUDE A KERNEL:
tombepa said:
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Click to expand...
Click to collapse
Yes. If you want to try custom kernels on CM10, it is of course at your own risk.
Flash, MMS, NFC or Native Tethering work on these builds?
Let's put it this way. They have all worked at some point or another. Then you have the fact that so many people posting here are contaminating the results with comments about unofficial builds and people that are flashing using different methods, etc......There's no good way for me to track and update this portion accurately. If you rely on any single feature to work properly, you are using the wrong ROM. Go back to stock. If you are flashing Nightlies of anykind you should expect things that have worked all along, some days will be broken. So the best thing to do is try it yourself and report here for others to see. These might be official nightlies but it's still very BETA and WIP (Work In Progress) and should be treated as such.
MMS WORKS
I can confirm personally as of the 8-20 build MMS is working and persistent after a reboot!
NFC WORKS
NFC fix found here.
WPA/WPA2 Native Tethering WORKS
You can flash the file in THIS POST to fix native tethering with WPA/WPA2 security intact.
FLASH WORKS
Sideload the newest Adobe Flash app found in THIS THREAD to get Flash on Jelly Bean. Of course you must have "Unknown Sources" enabled in Settings->Security to sideload any apk
If things change, let me know via PM, I'll try to update the OP.
UNOFFICIAL ALPHA BUILD THREAD IS OVER HERE.
In that thread you can find discussion and info on the unofficial alpha builds by people such as cvpcs, invisiblek, dhacker and others who have been part of the efforts to get us to where we are today. Their contributions are invaluable. Those builds right now may actually run smoother and have less bugs because they are UNOFFICIAL which means they can do what's called "cherry picking" and include code that has not been committed into the OFFICIAL builds yet. The official build may or may not have all those features. They are sometimes different ROMs functionally.
Now that we have an Official Nightly build in order to not confuse people please take Alpha Unofficial talk to that thread. Please keep posts here on topic and relevant to the Official Nightly builds. Things that work on those doesn't work on these and vice-versa.
CHANGELOG IS HERE and UnOfficial CM10 Bugtracker is HERE
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
UPDATE, Official Announcement from Cyanogen Mod, M-Series Roms Announcement 9-11-12
Something we have learned over the past few months is that if you don’t release, someone else will do it for you. Since we are open-source, we absolutely encourage it! Unfortunately, the quality of unofficial builds can vary, and we are serious about quality. Of course nightlies are always available, but we realized that having something that is a bit more stable on a more frequent basis is important. Starting now, we are rolling out our M-Series releases. M-Series builds will be done at the beginning of every month. We did a soft freeze of the codebase for the last week, blocking new features in order to stabilize. Our plan is to continue this (assuming that the response is good) up until stable release, and onward.
We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
M-Series builds will be available under the EXPERIMENTAL tag. The filename will include the date stamp as well as the M version. These builds should be stable enough for daily use, and we encourage feedback and bug reports.
Tonight’s M1 build is available for these devices:
Galaxy Nexus GSM (maguro)
Galaxy Nexus VZW (toro)
Galaxy Nexus Sprint (toroplus)
Galaxy S2 GT-I9100G (i9100g)
Galaxy S (galaxysmtd)
Galaxy S B (galaxysbmtd)
Captivate (captivatemtd)
Galaxy S3 Sprint (d2spr)
Galaxy S3 VZW (d2vzw)
Galaxy S3 AT&T (d2att)
Galaxy S3 TMO (d2tmo)
Galaxy S3 US Cellular (d2usc)
Nexus S (crespo)
Nexus S 4G (crespo4g)
Galaxy Note AT&T (quincyatt)
Google Nexus 7 (grouper)
Sony Xperia Acro S (hikari)
Sony Xperia S (nozomi)
In standard CM style, we will continue to add devices as time goes on up until our stable release.
Head over to Get.CM to grab the latest build for your device. Installation instructions and other documentation can always be found at the CM Wiki and help is always close at hand over on our official forums.
Happy flashing!
Click to expand...
Click to collapse
Source
If you need a more general "all things GSIII guide" to bail out of a problem, or to do other things that aren't necessarily CM10 specific, I highly recommend THIS THREAD

So to start it off I'd like to know if anyone is running the cm-10-20120818-NIGHTLY-d2vzw.zip build from early this morning? Does it have the MMS fix? Is it significantly different from the alpha builds we have been running for a couple weeks?

Flashed this directly over my Synergy 1.7 a few hours ago and it's working great.
Make sure you've unlocked your bootloader. I understand there is a one-click in the play store for those who can't bear the horrors of one-clicking on Casual.
Did a factory wipe/cache/dalvik.
I haven't found anything yet that's not working.
I'm running CM on my tenderloin so I'm used to some of the conventions.

Do these include google now, if not where can I get it?

ilogik said:
Do these include google now, if not where can I get it?
Click to expand...
Click to collapse
Please read the OP. CM never has and never will come with Google Apps, per Cyanogenmod.
Make sure you also have a copy of the CWM flashable Google Apps on your ext sdcard which can be found HERE thanks to our friends at goo.im because CM doesn't come with Play Store by default.
Click to expand...
Click to collapse

Is there still a chance to lose your imei with these?
Sent from my SCH-I535 using xda premium

Immolate said:
Flashed this directly over my Synergy 1.7 a few hours ago and it's working great.
Make sure you've disabled your bootloader. I understand there is a one-click in the play store for those who can't bear the horrors of one-clicking on Casual.
Did a factory wipe/cache/dalvik.
I haven't found anything yet that's not working.
I'm running CM on my tenderloin so I'm used to some of the conventions.
Click to expand...
Click to collapse
Lol. I'm pretty sure you don't want to disable your bootloader. Now, you do need to unlock your bootloader. The difference is kind of a big deal. Just sayin
Sent from my SGS3 on Synergy Nightlies

WizeGuyDezignz said:
Is there still a chance to lose your imei with these?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
YES. Op updated.

Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Sent from my SCH-I535 using Tapatalk 2

Schaweet said:
Lol. I'm pretty sure you don't want to disable your bootloader. Now, you do need to unlock your bootloader. The difference is kind of a big deal. Just sayin
Sent from my SGS3 on Synergy Nightlies
Click to expand...
Click to collapse
Yeah yeah, acknowledged. I'm sure if you can disable your bootloader, I'll figure out a way.

ive had one random reboot hopefully it was just a once time thing cause im loving this rom..much better than touchwiz
hopefully that flickering thing when texting gets fixed soon cause it gets a bit annoying..(ive also noticed that my widgets flicker)

neyenlives said:
Please read the OP. CM never has and never will come with Google Apps, per Cyanogenmod.
Click to expand...
Click to collapse
I think he's talking about Google now(voice search assistant), Not Google apps. It should be built into the ROM but you should still flash gapps anyways
Sent from my SCH-I535 using Tapatalk

Can we update the OP with important commits like the MMS fix when they go through?
Sent from my Galaxy S III
---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------
tombepa said:
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The ROM comes with a kernel, but you can flash any non-kexec kernel for AOSP ROMs that you want. I'm currently running an AT&T kernel.
Sent from my Galaxy S III

TheBiles said:
Can we update the OP with important commits like the MMS fix when they go through?
Sent from my Galaxy S III
Click to expand...
Click to collapse
mms is working for me with the latest build:good:

XTRoRDiNAiRE said:
mms is working for me with the latest build:good:
Click to expand...
Click to collapse
Does your phone number stick after a reboot? CVPCS said that the commit wouldn't be in the first build.
Sent from my Galaxy S III

Can I use TWRP recovery to flash this Rom?

TheBiles said:
Does your phone number stick after a reboot? CVPCS said that the commit wouldn't be in the first build.
Sent from my Galaxy S III
Click to expand...
Click to collapse
Phone number and MIN are blank for me (after a few reboots). Also, the LTE toggle doesn't seem to function properly. Everything else is working flawlessly; this ROM is definitely a daily-driver. Enjoy!
EDIT: I just realized that MMS isn't working for me....I can live without it for now but those that need it, may want to wait for another build.

neyenlives said:
YES. Op updated.
Click to expand...
Click to collapse
Thanks. Will this issue ever be fixed?
Sent from my SCH-I535 using xda premium

Nice. I was just thinking about flashing this
Sent from my Verizon Samsung Galaxy S 3 running SynergyROM v1.6

WizeGuyDezignz said:
Thanks. Will this issue ever be fixed?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The IMEI issue from my personal standpoint and based off of the opinions of the smart guys in IRC, is that it is very possibly a hardware design issue. Samsung could have put the EFS data which contains the IMEI in a non-volatile un-changable part of the memory but it looks as though they left it writable. This means we can try to write it back if we lose it but it also means bad data could be written to it thus erasing it.......that's what I have gotten out of it so far. So every time you flash you take the risk. I seriously doubt any fix will ever officially come because as long as you buy the phone and use it in stock form, you would never see the issue. It's an issue that only affects custom flashers, so don't expect to see a fix.

Running stock 4.1.2.. What is most stable to flash?

Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?

DatacomGuy said:
Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?
Click to expand...
Click to collapse
For TW 4.1.2 is the most current, but developers are working on 4.3. Otherwise, I would flash an AOSP ROM & I've had good luck on those too.

DatacomGuy said:
Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?
Click to expand...
Click to collapse
Gummy and SlimKay have full GPS and Bluetooth capabilities. The unofficial CM builds are FAR more stable than the official ones, so if you must use CM, go with an unofficial like Mastamoon or KitKang.
HOWEVER... every custom rom has issues with a 'kill signal' with Bluetooth, so if you use BT, you need to make sure you power down the other device, before you try to turn off BT on your phone; that will send the signal to your device and unpair the two. Otherwise, your phone won't be able to reconnect to BT on that device and you'll have to reboot. It's a known bug and people are working on it.
I used Gummy all December and now I'm running SlimKat... they're stable for daily use. I'd recommend a custom kernel with Slim, though... I'm using Lean Kernel.

DatacomGuy said:
Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?
Click to expand...
Click to collapse
Take a look at this it was just released
http://forum.xda-developers.com/showthread.php?t=2591895

beepea206 said:
Gummy and SlimKay have full GPS and Bluetooth capabilities. The unofficial CM builds are FAR more stable than the official ones, so if you must use CM, go with an unofficial like Mastamoon or KitKang.
Click to expand...
Click to collapse
Why would an unofficial cm be more stable? From reading the descriptions, it's just cm with a couple of visual tweaks, no?

lexluthor said:
Why would an unofficial cm be more stable? From reading the descriptions, it's just cm with a couple of visual tweaks, no?
Click to expand...
Click to collapse
Recent CM nightlies are highly unstable and there's often they'll put out a build with a commit they later revert. The unofficial builds vary... some don't release every night (avoiding those bad commits), others cherry-pick and are able to avoid commits they don't think are necessary (and are what often wonk up a build). Basically, they're more fine-tuned for our specific device (the CM builds are just pushed out auto-build) and tend to perform better.
If you look at the feedback in the 'official' thread, then compare that to the unofficial threads, you'll see far more issues in the official one. Could be more noobs going to CM's official builds because it's considered safer, but I've seen some veteran flashers have the same issues, so I'm inclined to believe it's due to how they push out nightlies.
... but that's just my observation. Take it for what it's worth.

beepea206 said:
Recent CM nightlies are highly unstable and there's often they'll put out a build with a commit they later revert. The unofficial builds vary... some don't release every night (avoiding those bad commits), others cherry-pick and are able to avoid commits they don't think are necessary (and are what often wonk up a build). Basically, they're more fine-tuned for our specific device (the CM builds are just pushed out auto-build) and tend to perform better.
If you look at the feedback in the 'official' thread, then compare that to the unofficial threads, you'll see far more issues in the official one. Could be more noobs going to CM's official builds because it's considered safer, but I've seen some veteran flashers have the same issues, so I'm inclined to believe it's due to how they push out nightlies.
... but that's just my observation. Take it for what it's worth.
Click to expand...
Click to collapse
That's a reasonable explanation. I'm on CM11 official nightly. I usually read the changelog before I update. I did do a full wipe before updating originally and I've been running very well. I've had 1 random boot in about a week and the camera froze the system once. I had many more random reboots on TW. It's incredibly fast and I've got no lag (that was a bad problem for me on 4.1.2).

Nice one... checking the changelog and/or Gerrit commits is a good practice, IMO. I only flash a nightlie if I find some commits I think would make the rom run better for me... most are small things like language tweaks and updates to other device repos, so flashing the newest version isn't always necessary.
Regarding the random reboots, you probably have the same modem issue I do. There was a recent update to the device RILs that completely resolved the modem 'freakout' i kept having; I believe they used the updated device files from the 4.3 stock builds pushed out, so it made the device more compatible with the 4.3 and 4.4 roms.

DatacomGuy said:
Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?
Click to expand...
Click to collapse
if you like touchwiz, MOAR and Wicked Sensations roms (4.1.2) are pretty good. I'm on cm10.2 (4.3.1) with xposed framework and it's running perfectly. I'm staying away from kitkat cause of all the bluetooth issues.

[Q] Which CM version works best?

So I'm trying to prolong the use of this tablet but keep it stable and quick, and I think CyanogenMod is the way to go. There are a number of versions available for it, with 10.0 being the last stable build that I can find. I flashed 10.0 and it was quick and stable, except for one major problem: the Google+ app just would not load no matter what, and by searching I found others had the same issues with no fix.
So I'm back to stock 4.1.2 JB now, which is fine but I'd rather move to CM if I can. I flashed the latest nightly, but was having major issues with Gapps closing and the Play Store wasn't even available (even though I flashed the correct Gapps package).
For those that are using CM, which version is the best to use? Any help would be much appreciated, thanks!

Honestly, I use the CM11 builds and they are working great.
XOOM XOOM!

slinky317 said:
So I'm trying to prolong the use of this tablet but keep it stable and quick, and I think CyanogenMod is the way to go. There are a number of versions available for it, with 10.0 being the last stable build that I can find. I flashed 10.0 and it was quick and stable, except for one major problem: the Google+ app just would not load no matter what, and by searching I found others had the same issues with no fix.
So I'm back to stock 4.1.2 JB now, which is fine but I'd rather move to CM if I can. I flashed the latest nightly, but was having major issues with Gapps closing and the Play Store wasn't even available (even though I flashed the correct Gapps package).
For those that are using CM, which version is the best to use? Any help would be much appreciated, thanks!
Click to expand...
Click to collapse
CM10.1 (based on 4.2.x) really great. I used it for the past few months.
Never give me problem. Of course you must install 2/20/13 JB Unified GApps.
Looking forward to try CM11 but having hard time with TWRP (big part) at the moment.

TheMan0790 said:
Honestly, I use the CM11 builds and they are working great.
Click to expand...
Click to collapse
Another vote for CM11, but you do have to install BigPart. That isn't a big deal if you read carefully through the resource thread before proceeding. I'm certainly not a tech wizard (color TV and phones without dials were big deals when I was a kid, VCRs didn't come out until I was in college, and I was in my mid twenties when home computers just started to become widespread) and was able to run BigPart without trouble.

I got BigPart working successfully with no problems on the first go. Merely requires some reading and should work fine.
Break me off a piece of that Kit-Kat ROM!

[Q] lets make a list of ROMS for TeamWin Recovery Project 2.7.1.0(kitkat Bootloader))

Can we start a list of sorts with Roms that work with the new bootloader?? so far i read that Dhacker29 has a few test builds of cm11 . i have one installed right now and it has some bugs but works and is faster than my hd has ever been . i can run this game i like and before it couldnt play without lagging now it runs crazy fast . anyway thank you Dhacker29 for the recovery and rom. i was reading another site and someone mentioned another dev that had a test build out for the new recovery but i cant for the life of me find or remember who it was. also how can i tell if a rom will work without trying to install it. i read that the kernel had to be 3.5 and newer or some shshhsh. anyway thanks in advance to anyone that responds

I second this. Was actually thinking of suggesting the same thing. Might help keep people from flashing the JB kernel Roms and asking what they did wrong. Least maybe a bit more.
>.>

almost forgot
heres a link to Dhackers Test rom that im using . it has a few minor bugs but all the hardware works soo
http://androidhosting.org/Devs/Dhacker29/msm8960/cm-11-20140619-UNOFFICIAL-RAZR-HD_M-KITKAT-TEST.zip
i hope its ok to do this anyway Thanks Dhacker29!!!!

http://androidhosting.org/Devs/Dhacker29/msm8960/
here's the whole directory with all his builds and where I think he adds them

I believe there is a PACMan Alpha out as well. Has the same bugs as CM11

cmh714 said:
I believe there is a PACMan Alpha out as well. Has the same bugs as CM11
Click to expand...
Click to collapse
i would love to have pacman rom on here!! i read that you cant downgrade your bootloader is this true or is that only apply to locked bootloaders?

JohnnyMcG said:
Can we start a list of sorts with Roms that work with the new bootloader?? so far i read that Dhacker29 has a few test builds of cm11 . i have one installed right now and it has some bugs but works and is faster than my hd has ever been . i can run this game i like and before it couldnt play without lagging now it runs crazy fast . anyway thank you Dhacker29 for the recovery and rom. i was reading another site and someone mentioned another dev that had a test build out for the new recovery but i cant for the life of me find or remember who it was. also how can i tell if a rom will work without trying to install it. i read that the kernel had to be 3.5 and newer or some shshhsh. anyway thanks in advance to anyone that responds
Click to expand...
Click to collapse
Any stable builds? Maybe some that use stock and then tweak it out.

i think you can install the stock files and then root and use a root app manager to remove all the bloatware from your phone. there is even a thread that tells you all the apps you can get rid of without jacking anything up. here you can check it out
http://forum.xda-developers.com/showthread.php?t=2756195

spapesh said:
Any stable builds? Maybe some that use stock and then tweak it out.
Click to expand...
Click to collapse
after root you can download xposed installer and then download one of the customizing modules and you can then change your icons in the status bar. nav bar, even alter the way your toast messages come in . anything you can think change the color of your wifi and 4g icons or change them to something entirely diff . here check that out too . you probably already know all this already but just in case.
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053

JohnnyMcG said:
i think you can install the stock files and then root and use a root app manager to remove all the bloatware from your phone. there is even a thread that tells you all the apps you can get rid of without jacking anything up. here you can check it out
http://forum.xda-developers.com/showthread.php?t=2756195
Click to expand...
Click to collapse
This is what I did. I was already running stock KK before rooting/unlocking. Still running it now but I removed a lot of crap. I'm looking forward to at least a few stable ROMs to try out on this phone, but I'm cool with this for now.
Sent from my DROID RAZR HD using Tapatalk

Does anyone know if the available KK-bootloader roms work on xt925? I know the ROM unification for a lot of devices have taken place. I am not sure this also happens with the new KK-bootlader, or if we are back on the old xt925 vs xt926 compatability devide...
Thanks in advance.

idless said:
Does anyone know if the available KK-bootloader roms work on xt925? I know the ROM unification for a lot of devices have taken place. I am not sure this also happens with the new KK-bootlader, or if we are back on the old xt925 vs xt926 compatability devide...
Thanks in advance.
Click to expand...
Click to collapse
not sure . you can ask Dhacker29 he is the one that made the recovery I think. or you can post your question in this thread and you might get a better response
http://forum.xda-developers.com/showthread.php?t=2776515

Here is a Gummy rom that supports the 3.4 kernel.
https://mobile.twitter.com/dhacker29/status/480220911225036800
Source: http://forum.xda-developers.com/showpost.php?p=53609374&postcount=2913
So far I know of these Roms that are being developed to run on 3.4 kernel
CM11 Unofficial: http://androidhosting.org/Devs/Dhacker29/msm8960/
PAC-man Alpha 1: http://forum.xda-developers.com/showthread.php?t=2683962&page=3 I read mention that this works but I've not tested it myself
Gummy Rom Nightly: https://mobile.twitter.com/dhacker29/status/480220911225036800 <-- using this right now. Seems pretty good.
full list like CM11 unofficial http://androidhosting.org/Devs/Gummy/moto_msm8960/NIGHTLY/
NexesqueKK 0.01: http://www.droidrzr.com/index.php/t...2-droid-nexesque-for-razr-hd-beta-442-builds/ I saw on DroidRZR.com that there was a test for the 3.4 kernel but my attempts to flash it failed
Beanstalk Nightly (Kitstalk): http://www.droidrzr.com/index.php/topic/35880-rom442kit-katunofficalxt926-beanstalk/ flashed the 6-23 one on my phone.. Seems to be working

wow
I thought I was decent at finding info online but i couldn't find any of those threads except for the pacman alpha but for the life of me I can't find where to download the alpha build I can find the nightly n the 4.3 but alas no alpha maybe its under one of the devs tabs instead of the pacman tab idk anyway thanks a lot for all the great info

Jaysp656 said:
Here is a Gummy rom that supports the 3.4 kernel.
https://mobile.twitter.com/dhacker29/status/480220911225036800
Source: http://forum.xda-developers.com/showpost.php?p=53609374&postcount=2913
So far I know of these Roms that are being developed to run on 3.4 kernel
CM11 Unofficial: http://androidhosting.org/Devs/Dhacker29/msm8960/
PAC-man Alpha 1: http://forum.xda-developers.com/showthread.php?t=2683962&page=3 I read mention that this works but I've not tested it myself
Gummy Rom Nightly: https://mobile.twitter.com/dhacker29/status/480220911225036800 <-- using this right now. Seems pretty good.
full list like CM11 unofficial http://androidhosting.org/Devs/Gummy/moto_msm8960/NIGHTLY/
NexesqueKK 0.01: http://www.droidrzr.com/index.php/t...2-droid-nexesque-for-razr-hd-beta-442-builds/ I saw on DroidRZR.com that there was a test for the 3.4 kernel but my attempts to flash it failed
Beanstalk Nightly (Kitstalk): http://www.droidrzr.com/index.php/topic/35880-rom442kit-katunofficalxt926-beanstalk/ flashed the 6-23 one on my phone.. Seems to be working
Click to expand...
Click to collapse
Gummy rom tested on my xt925. Stuck at unlocked bootloader sign. I don't think xt925 is supported yet.

Yeah I don't know if any have xt925 support or not. Hopefully they will include them eventually.

Gummy Rom
I recently tried Gummy Rom for 3.4 kernel. It was pretty good, but had trouble with bluetooth freezing the phone and wifi dropout at times. It has great progress, and appreciate those who are working on it. :good:

I have installed dhacker's 4.4 cm build from 24/6. Happy to report that it boots - and so far, at least - works great. This is on an xt925! It's the first 4.4 bootloader rom other than moto that I have got to actually boot up on this phone.

I installed gummy and have been using the auto updater running nightlies right now I'm running 6-24 build . it seems like the the previous ver. had fixed the screen dimming issue but it seemed to come back on this ver. but rarely happens I haven't tied Bluetooth yet and the popping/static sound issue is still there but other than that I like the rom . thanks for
Sent from my DROID RAZR HD using Tapatalk

In droidrzr forums there is an Unofficial Omni Rom for kitkat bootloader..
btw, for xt925, dhacker says that we only need the new bootloader (maybe installing the leaked soak test from France we can use the newest roms)