• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [MetroPCS/CDMA] [ROM][OFFICIAL] CyanogenMod 11 Nightly Builds for d2mtr

First of all, thanks for all the hard work you guys are putting into this. I have been using cyanogenmod 10.1, latest and greatest. for the most part everything has been working, until today. Tried to use the voice function in messagaing and now I can't type a message, keyboard starts to come up and then it closes and a message flashes on the screen (way too fast for these old eyes to catch). Tried going back one nightly and still same problem. Also ran Apollo after it was fixed, (froze the phone while on previous nightlies) and it worked except the screen did the flickering. Also noticed the camera is getting better, at least so far it has stopped flickering. gonna try and d/l a differnt keyboard, and see if that fixes the problem.
 
Ok, well that didn't work, using a different keyboard. was finally able to see the "flash popup" on the screen, "Unfortunitly Google Search has stopped working." going to uninstall google search and reinstall, see if that works
 
said th' heck with it and just did a re-install of the gapps-jn-20121212-signed
all better now.

Update; just tried the "Google Search" wigdet and same thing happend. appears to be a issue with Google Search.

Update#2; just performed a update to "Google Search" from the play store and it is working now.
 
Well the newest build 20130102 is pretty smooth, GPS doesn't seem to work properly and then it force closes and Bluetooth also is not working properly, but it doesnt freeze the phone anymore and if you call voicemail or any call and hang up right away it plays for a few seconds.

Sent from my SCH-R530M
 
Get@Me said:
Try editing these two lines in the built prop to look like this and reboot
debug.composition.type=gpu
debug.mdpcomp.maxlayer=0
Click to expand...


Well that didn't quite work, phone tries to boot, get the Samsung splash screen for a brief second, then goes blank. tried even pulling the battery and doing a cold boot... nothing. Able to get to the "Download" function tho. :confused:guess it is back to the drawing board and back to trying to reinstall from ODIN and downloading 4.0.4 and re-rooting my phone... unless you guys got any other ideas on how to recover my phone.
I am on the 20130102 nightly.
 
jconstable007 said:
Well that didn't quite work, phone tries to boot, get the Samsung splash screen for a brief second, then goes blank. tried even pulling the battery and doing a cold boot... nothing. Able to get to the "Download" function tho. :confused:guess it is back to the drawing board and back to trying to reinstall from ODIN and downloading 4.0.4 and re-rooting my phone... unless you guys got any other ideas on how to recover my phone.
I am on the 20130102 nightly.
Click to expand...


Don't know why it would cause your phone to do that those are the same edits I did on BB6 to stop flickering and it work. Did you make or have a backup of your previous rom? If so just boot into recovery and restore or flash the rom again
 
Get@Me said:
Don't know why it would cause your phone to do that those are the same edits I did on BB6 to stop flickering and it work. Did you make or have a backup of your previous rom? If so just boot into recovery and restore or flash the rom again
Click to expand...


will try do a flash the rom again when i get home. so far the only thing I can do is get to the download function....can't even get to the recovery.... she is really locked up...:confused:
 
jconstable007 said:
will try do a flash the rom again when i get home. so far the only thing I can do is get to the download function....can't even get to the recovery.... she is really locked up...:confused:
Click to expand...


To get in recovery hold power, vol+, home button you should be able to get into recovery.
 
michel5891 said:
Any ideas as to why the low in-call volume levels?
Click to expand...


It's been a known problem and has shown in various builds. When you find a build that works for you, stick with it. People are constantly updating to the new nightly and then they wonder why something doesn't work. It's because it's a nightly! Find a build that works for you, read changelogs before trying a newer one, report your issues with the way described by the developer and always make a backup.
 
I flashed it and it was working perfectly but then realized I had no google apps. I went back to flash gapps and now the rom doesn't work. How do u properly install gapps for this rom?
 
Get@Me said:
To get in recovery hold power, vol+, home button you should be able to get into recovery.
Click to expand...


Tried that, and no go.:confused:.. was able to get it to go one step further after d/l and trying to re-flash Clockworkmod... it flashes fine through ODIN but upon reboot it goes back to the blank screen after the second splash screen, the "Samsung Galaxy SIII" splash screen. went to the store and they tried a hard reset and still no good. end result they are ordering a new phone for me :D. now I just have to wait 3 - 5 business days... sometime between monday and wednesday next week.:( oh well at least i get a new one. thanks for the help, but she got bricked bad
 
jconstable007 said:
Tried that, and no go.:confused:.. was able to get it to go one step further after d/l and trying to re-flash Clockworkmod... it flashes fine through ODIN but upon reboot it goes back to the blank screen after the second splash screen, the "Samsung Galaxy SIII" splash screen. went to the store and they tried a hard reset and still no good. end result they are ordering a new phone for me :D. now I just have to wait 3 - 5 business days... sometime between monday and wednesday next week.:( oh well at least i get a new one. thanks for the help, but she got bricked bad
Click to expand...


Did you try flashing the stock firmware through ODIN?
 
THE W said:
so is the general consensus that this thing still needs work?
Click to expand...


Depends. Cm10 had a stable release. A nightly always needs work and that had been discussed numerous times in this large thread. Most stable 10.2 for me is the nightly from 12-26.
 
twistedriku said:
Did you try flashing the stock firmware through ODIN?
Click to expand...

Been trying just about everything that I can think of, was able to get it to go to the "Android system recovery <3e>". I had a copy of the cyanogenmod 10.0 on the internal memory, tried to do a install, and it doesn't pass the signature verification process. so far been unable to access the internal rom to upload a "signed" rom to see if that helps. if you know of where i can get a copy of the stock firmware for this thing, I will try that.
 
jconstable007 said:
Been trying just about everything that I can think of, was able to get it to go to the "Android system recovery <3e>". I had a copy of the cyanogenmod 10.0 on the internal memory, tried to do a install, and it doesn't pass the signature verification process. so far been unable to access the internal rom to upload a "signed" rom to see if that helps. if you know of where i can get a copy of the stock firmware for this thing, I will try that.
Click to expand...

if its just signature verification, turn it off
 
confed said:
if its just signature verification, turn it off
Click to expand...

there is no way to turn it off in the official Android system recovery.. not running twrp or cwm. this is the recovery that comes with the phone.
tried using various tar files with ODIN and everything fails at the NAND write... I think the phone died of the NAND failure that has been hitting the galaxy s3's. thanks again for your help
 
You must log in or register to reply here.
Back
Top Bottom