Related
Currently running CM9 on my Photon, would like to go back to stock, have searched and havent really found to much.
Is there a guide for the simple minded among us (namely me) to go back to stock???
I have a feeling it's really simple and I am gonna feel silly for asking....heh
Boot into recovery,
hard reset X3
Reboot into rsd mode
Sbf back to stock
(you will have t to re root and unlock if you choose to after)
Sent from my MB855 using Tapatalk 2
Cm9 isn't as cracked up as they making out to be?
Sent from my MB855 using xda premium
It was pretty nice, but not all it's cracked up to be. A few things didnt work.
But the most annoying thing was it didnt seem to know it was on Sprint network.
It was nice, and I dont wanna crap on the hard work put into it..
It's acting kind of flakey, I wonder if re-flashing it would help, I might try that first then maybe go back to stock.....
Ive had very few issues with CM9 and ive followed it from the beginning Alpha stages.. Try a different version if you have issues. To each his own for sure some people will like others won't. I personally cant be taken away from it. Ive had VERY few network issues where it wouldn't connect and the not working items list gets smaller each day, its basically down to video camera in stock app and few other minor things. As for going back to stock if you need super detail check out QBKing77 on youtube, he has a video of exactly what to do.
I am currently running beta-0.1.0-2d-cm-9.0.0-RC0-Sunfire-KANG-signed, maybe I should just upgrade to beta-0.5.0-cm-9.0.0-RC0-sunfire-UNOFFICIAL-signed. If I do that, I pretty much follow the directions I did to flash the original correct??
Basically from about 3 minutes in on QB's tut video??
Cant post the link, but this one:
How to Install the Beta CyanogenMod 9 ICS Rom on the Motorola:
H0a3rySyJZA
Slagathor01 said:
I am currently running beta-0.1.0-2d-cm-9.0.0-RC0-Sunfire-KANG-signed, maybe I should just upgrade to beta-0.5.0-cm-9.0.0-RC0-sunfire-UNOFFICIAL-signed. If I do that, I pretty much follow the directions I did to flash the original correct??
Basically from about 3 minutes in on QB's tut video??
Cant post the link, but this one:
How to Install the Beta CyanogenMod 9 ICS Rom on the Motorola:
H0a3rySyJZA
Click to expand...
Click to collapse
When coming from previous cm9 build just wipe system in mounts and storage and flash thr newer build onto it via clockworkmod recovery.
Sent not from your device!
I will give that a try, I tried 3 or 4 times yesterday but it would get stuck on the M duel core screen.
Restored the back up I had and it was ok then.
EDIT:
No love yet again, I am using CWM 5.0.2.7.
It stops at the M duel core tech screen and just sits there.
Did you flash twice? If you don't, it bootloops.
Sent from my MB855 using XDA
ryan8r said:
When coming from previous cm9 build just wipe system in mounts and storage and flash thr newer build onto it via clockworkmod recovery.
Sent not from your device!
Click to expand...
Click to collapse
Do not wipe system when coming from a previous build. Wipe caches and fix permissions after you flash twice.
Sent from my MB855 using XDA
ICS Rom
The way i got that rom to work on my photon was to run the original rom, then go back and flash the most recent version, that worked perfectly for me!
I will give that a whirl after after work, thanks....
Finally, got it going, further reading figured out to flash the rom twice in a row, currently running 0.5.0, had to flash the CDMA fix to get the signal, running great, much smoother then the 0.1.0......
Thanks for all the help guys.....
braindeadracefan said:
Did you flash twice? If you don't, it bootloops.
Sent from my MB855 using XDA
Click to expand...
Click to collapse
I realise now what you meant by flash twice......
I've been running AOSP 4.2 on my S4 for quite a while with no issues. Upon trying to upgrade to 4.3 though, boots take upwards of 5 minutes and the baseband isn't recognized (it literally shows "Baseband Version: Unknown"). I then tried to revert to one of the various 4.2 ROMs still out there, and am encountering quite a bit of general instability (lots of FCs), however, the baseband works fine. Any idea what is going on?
I should add that though I am using the ME7 modem, everything else is MDK and that these symptoms are pervasive through several different ROMs.
Update:
When trying to switch to RUIM/SIM in the Radio Settings, I get the following logcat:
Code:
/CdmaSubscriptionListPreference( 1762): Setting Cdma subscription source failed
I/Use2GOnlyCheckBoxPreference( 1762): get preferred network type, exception=com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
have you gone into network settings and verified that your subscription is set to RUIM/SIM instead of NV?
Did you compile the AOSP yourself? What build are you using? Project Elite's baseband and network all work out of the box no problems. I'm not sure if they posted it yet though.
Dubbsy said:
have you gone into network settings and verified that your subscription is set to RUIM/SIM instead of NV?
Click to expand...
Click to collapse
Yes; Whenever I do that I get the logcat I mentioned above and the setting doesn't stick (ie it immediately changes back to NV).
Edit:
When I retried, I got:
Code:
E/CdmaSubscriptionListPreference( 1618): Setting Cdma subscription source failed
Dubbsy said:
Did you compile the AOSP yourself? What build are you using? Project Elite's baseband and network all work out of the box no problems. I'm not sure if they posted it yet though.
Click to expand...
Click to collapse
No; this is with several 4.3 based ROMs including CM and Pacman.
Edit 2:
I'm downloading the Darkslide ROM to try to get that baseband installed and will keep this thread up to date with the result.
murphycr said:
Yes; Whenever I do that I get the logcat I mentioned above and the setting doesn't stick (ie it immediately changes back to NV).
Edit:
When I retried, I got:
Code:
E/CdmaSubscriptionListPreference( 1618): Setting Cdma subscription source failed
No; this is with several 4.3 based ROMs including CM and Pacman.
Edit 2:
I'm downloading the Darkslide ROM to try to get that baseband installed and will keep this thread up to date with the result.
Click to expand...
Click to collapse
Oh you aren't running pure aosp. Gotcha.
I was able to hold subscription on PAC, Slim, and CM10.2
Did you edit anything prior to install? Was your phone's data working just before switching to 4.3?
Dubbsy said:
Oh you aren't running pure aosp. Gotcha.
I was able to hold subscription on PAC, Slim, and CM10.2
Did you edit anything prior to install? Was your phone's data working just before switching to 4.3?
Click to expand...
Click to collapse
Yes. It also works if I switch back to 4.2, but then other things break. Anyway, I'm about to flash the baseband you referred to, so I'll see where that gets me.
Thanks!
murphycr said:
Yes. It also works if I switch back to 4.2, but then other things break. Anyway, I'm about to flash the baseband you referred to, so I'll see where that gets me.
Thanks!
Click to expand...
Click to collapse
the baseband used in all 4.3 builds I've used was MDK.
Me7 baseband is not as good as some people like to claim. It is buggy, and in my opinion it was rushed to release because Verizon wanted to quick kick everyone in the nuts. I tried me7 a few times and everytime I had worse spottier service.
The project elite aosp I was talking about is actually full aosp. And I haven't seen a post for it yet.
Another thing I've noticed in general... What recovery are you using? I don't trust CWM(any variation) at all anymore. I've seen too many installs act up and just not work right at all with CWM and after trying it on twrp 2.5.0.2 the same exact installer worked fine. :silly: I don't know why, but regardless the layout of CWM is piss poor anyway. If you are using CWM, click the link in my sig to go to my GE build. In the second post I have flashable recoveries posted. You can try one out just to see and if you get the same results just flash back to your desired/current recovery:good:
I was having the same problem with my own cm10.2 builds. I blew out my device and vendor repos several times and finally decided that there had to be something in frameworks that doesn't like the dev edition radios. The nightlies wouldn't even work. I ultimately wound up using the official cwm (non-loki only) and was finally able to change from nv to ruim/sim.
Sent from my SCH-I545 Dev Edition using xda app-developers app
So you used the non-loki'd CWM to do what fixed it? (I presume simply having it installed didn't fix it automatically)
On the dev edition, the general consensus in the beginning was that philz touch(cwm based) was the recovery to use probably because he offered a non-loki version. We don't need loki fortunately because of our unlocked bootloader. I later found out that official cwm was also not lokified. If you have the retail version, unfortunately you are stuck with the loki recovery. I was just suggesting that you might try a different cwm since they are not all created equal.
Edit: I guess what I was really trying to say is just try another recovery. Not necessarily one over the other (cwm vs. twrp). It's not the non-loki part that will make the difference. Hopefully you'll find one that works for you. But who would have known that would cause it.
Sent from my SCH-I545 using xda app-developers app
OLD&SLOW said:
On the dev edition, the general consensus in the beginning was that philz touch(cwm based) was the recovery to use probably because he offered a non-loki version. We don't need loki fortunately because of our unlocked bootloader. I later found out that official cwm was also not lokified. If you have the retail version, unfortunately you are stuck with the loki recovery. I was just suggesting that you might try a different cwm since they are not all created equal.
Edit: I guess what I was really trying to say is just try another recovery. Not necessarily one over the other (cwm vs. twrp). It's not the non-loki part that will make the difference. Hopefully you'll find one that works for you. But who would have known that would cause it.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I've tried both TWRP and PhilZ. Neither seemed to do it. At this point I'm just going to do a full ODIN.
Thanks for all the help though!
No problem, I just hope you figure it out. There are too many people using aosp 4.3 roms with no problems for this to be impossible. :thumbup:
Sent from my SCH-I545 using xda app-developers app
murphycr said:
I've tried both TWRP and PhilZ. Neither seemed to do it. At this point I'm just going to do a full ODIN.
Thanks for all the help though!
Click to expand...
Click to collapse
I have an already Loki patched cwm touch posted in my list if you wanted to try it too.
I've found Odin helps clean all the garbage out though. So either way
Good luck!
sent from my Verizon Galaxy sIV
Not responsible for damaged phones, use at your own risk!
I installed the Stock rooted T Mobile rom by Scrosler posted here:
http://forum.xda-developers.com/showthread.php?t=2459677
After flashing that rom from recovery, I used Scrosler Stock loki'd ATT boot img found here:
http://forum.xda-developers.com/showpost.php?p=45755689&postcount=3
After booting, you have to setup an ATT APN. I used this one found here:
http://forum.xda-developers.com/showpost.php?p=41717915&postcount=9
APN settings are found under System settings / tethering & networks / mobile networks / access point names / "menu soft key" new apn. Be sure to save when done.
After this you have a completely functioning T Mobile rom with theming for the home launcher on your ATT D800
Of course build prop will need to be changed to ATT settings, but will work as is.
Thanks to Scrosler for all the need files and his time to do this!
Edit, you can load the build prop from clean Rom 1.1 to get it back to ATT.
Screenshots
Sent from my LG-D801 using Tapatalk 4
Note Att in drop down shade.
Sent from my LG-D801 using Tapatalk 4
the S3 were interchangeable rom between ATT and tmobile, this doesnt suprise me but good post.
Does this also Enable tmobile aws hspa bands?
Not sure what issues Scrosler was having porting it over then. I think I'll wait for his port though, CleanROM is just running too well for me to make a change.
supersain08 said:
Does this also Enable tmobile aws hspa bands?
Click to expand...
Click to collapse
i might try this out myself. don't know what it does for the bands, but i unlocked my at&t G2 when i first got it and i've been able to get T-Mobile 4G and 4G LTE service with my T-Mobile SIM. coverage and speeds are not as good as at&t in a few spots.
@op - what other benefits (if any) have you seen with the T-Mobile ROM? thanks.
The roms are basically the same, however the T-Mobile Rom has launcher theming built in. Hopefully in the future this will help developers build for more than one carrier.
Sent from my LG-D800 using Tapatalk 4
Any adverse affects of running this ROM? You have me tempted just to have themes and the option to opt out of carrieriq.
Sent from my LG-D800 using xda app-developers app
Is there anything you can change specifically to get themes working on the at&t variant without flashing a whole new rom?
Sent from my LG-D800 using XDA Premium 4 mobile app
None that I noticed!
Sent from my LG-D800 using Tapatalk 4
I tried flash T Mobile ROM to my at&t g2 but after TWRP did its thing it then went straight into fastboot mode on its own and now I am stuck with no way out and you please help me
willdogg78 said:
I tried flash T Mobile ROM to my at&t g2 but after TWRP did its thing it then went straight into fastboot mode on its own and now I am stuck with no way out and you please help me
Click to expand...
Click to collapse
looks like you forgot step 2 in the original post (flash the att loki'd boot image). reboot to recovery using the hard keys (see this post for steps, copy the att loki'd boot image to your phone and flash with TWRP and you'll be good to go. or, you can restore your backup from TWRP (assuming you made a backup).
thank you so much I am back in to recovery and flashing my nandroid backup. I am going to give this another try but want to just clarify that I am doing it correctly. If I understand properly I need to flash the T Mobile firmware. where I need the clarification is do I just simply put the boot image as the second file to flash so that they flash one after another, instead of what I tried the first time which was to flash the firmware first then go back into recovery and then flash the boot image which is what screwed me up first time. Does this sound like I have it under control this time
Why did you do this? The only plus so far I see is you got rid of the att on the left top corner?
willdogg78 said:
thank you so much I am back in to recovery and flashing my nandroid backup. I am going to give this another try but want to just clarify that I am doing it correctly. If I understand properly I need to flash the T Mobile firmware. where I need the clarification is do I just simply put the boot image as the second file to flash so that they flash one after another, instead of what I tried the first time which was to flash the firmware first then go back into recovery and then flash the boot image which is what screwed me up first time. Does this sound like I have it under control this time
Click to expand...
Click to collapse
yes, that's what i did. flashed the ROM and the boot image one after the other.
good news!! I have the ROM up and running the only thing left to do is the new APN setting for AT&T but the file you indicate to use is the same exact file for step 2 am I missing something? Also if that is the right file do I just simply flash it like normal, or is there a different method to apply it? thanks again for all of your help sorry to be a pain in the butt
jordant2 said:
Not sure what issues Scrosler was having porting it over then. I think I'll wait for his port though, CleanROM is just running too well for me to make a change.
Click to expand...
Click to collapse
IM porting. This is not a porting. What I am doing is a but more complex than flashing another ROM and changing the boot image.
colbyfink said:
Is there anything you can change specifically to get themes working on the at&t variant without flashing a whole new rom?
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope, I can post a launcher later, I have them working fine on my AT&T G2 running CR 1.1
Also, just an FYI, you can use the Korean version and the Verizon version as well...
But on the Verizon version the kernel is built to read the sensors different and you will need to swap the kernel modules because of this.
Also, you can swap the APN file too before you flash and yo wont have to worry about APN's.
Just sayin....
Oh and one other thing...
I accidentally deleted the boot.img so maybe OP can upload it please?
Otherwise I will make a new version when I get home.
I've spent the weekend trying to make a safestrap rom out the newest update from T-mobile. As far as I can tell everything is working the particular steps I did were
Disabled Wi-Fi in stock ROM before flashing
I'm not sure if this does anything but someone suggested this for fixing wifi not always coming up. I'm not sure if it matters but if you don't disable WiFi in the stock slot and WiFi in the SafeStrap slot doesn't work then mention it in the comments.
Create new rom slot of at least the default size
Flash vzwupdat.zip
Flash root, whatever other mods you may want
The kernel is still the old one, I just added the wifi drivers to the original rom to try and alleviate the issues that kept people from being able to turn on WiFi. I also added the build.prop and eri.xml from the stock Verizon ROM to fix T-CDMA64 showing as the Mobile Network.
Will you update now that the OTA for Verizon has been released?
The short answer is no. The Verizon update is the same software wise as this version. The modems were updated and some of the security binaries are updated. If you use this you are essentially using the newest software you could possibly use. Trying to modify Verizon's OTA to work with safestrap is going to be counterproductive because there is so much carrier specific branding and dependencies. This does include all the same camera updates, but to alleviate some of the problems that people have with call quality I will look into a flashable radio if someone else doesn't do it 25/10/13
Mega Link
https://mega.co.nz/#!0c9WRRSB!MkyN-wah-qD-lxrNXBLSOTwwb84o9AfE7UvhOW02AUg
Drive Link
https://docs.google.com/file/d/0B3Kv8-wueihjVnhWb2tQQXd2TDA/edit?usp=sharing
SuperSU by chainfire
http://download.chainfire.eu/supersu
HOW TO VIDEO!!!!!
http://www.youtube.com/watch?v=JsvUxEqNu-A&feature=youtu.be
Excellent, thanks!
What does the eri.xml file do? I'm just wondering if i need it for anything. I have a vzw dev edition and am running the T-Mobile rom. I just added the vzw build.prop and made sure to switch to the right network type lte/cmda auto(prl) every time I boot the phone. No issues so far. Is the eri.xml just for people with safestrap?
Working great. No issues so far.
Sent from my XT1060 using XDA Premium 4 mobile app
How is this different from stock? I'm about to pickup a Moto X and am excited to start modding it!
Edit: wait nevermind, I should have searched first...
Thanks so much. Can't wait until I have time to figure out how to flash this..
Sent from my XT1060 using Tapatalk
jimmypop13 said:
What does the eri.xml file do? I'm just wondering if i need it for anything. I have a vzw dev edition and am running the T-Mobile rom. I just added the vzw build.prop and made sure to switch to the right network type lte/cmda auto(prl) every time I boot the phone. No issues so far. Is the eri.xml just for people with safestrap?
Click to expand...
Click to collapse
On most ports from GSM to CDMA the eri is missing an entry to tell the phone "Hey, this network is called 'Verizon Wireless'." It keeps users from seeing the T-CDMA64 as their network provider. If you do flash it on your dev edition I just warn you that this was designed for being used as a SafeStrap ROM. It doesn't contain a boot.img and may not boot on the dev editions.
Does this have a wifi tether enable override so that VZW doesn't get checked?
htowngator said:
Does this have a wifi tether enable override so that VZW doesn't get checked?
Click to expand...
Click to collapse
This is essentially like using an carrier-less moto x. No bloat. No subscription checks.
Awesome work man!
Only one question before I flash this gem.
Does this cause any problems with safestrap??
I only ask because I flashed the tmo ROM the other day with no issues. Had data and WiFi working great. When I rebooted to get into ss I bootlooped like a son of a beotch. Had to fxz back to stock. Saw a few other users with the same problem flashing the same tmo ROM.
Can anyone comment on this??
Sent from my XT1060 using Tapatalk
doobie711 said:
This is essentially like using an carrier-less moto x. No bloat. No subscription checks.
Click to expand...
Click to collapse
So basically you create a rom slot, backup to new rom slot, install your update, install su update, and boot to new slot?
Sent from my Nexus 7 using Tapatalk 4
How can this be used on AT&T safestrap?
Sent from my XT1058 using XDA Premium 4 mobile app
codygs83 said:
Awesome work man!
Only one question before I flash this gem.
Does this cause any problems with safestrap??
I only ask because I flashed the tmo ROM the other day with no issues. Had data and WiFi working great. When I rebooted to get into ss I bootlooped like a son of a beotch. Had to fxz back to stock. Saw a few other users with the same problem flashing the same tmo ROM.
Can anyone comment on this??
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I've had no issues with reboots. I've turned off and on, rebooted to recovery and regular reboots and working great.
My only thing, and I'm new to SS so I know it's something I'm doing, is when I switch to stock slot and then back to where this ROM is, I've lost data on the custom slot. Like I clean flashed. Is there a way to maintain all my user data on slot 1 while switching to stock?
Sent from my XT1060 using XDA Premium 4 mobile app
Ok, I have it installed and running great so far...but as far as root, which Pwn version would I use? The Verizon one, the TMobile one, or none?
Thanks for developing for us. Stupid Verizon and their late updates!
SubliminalME said:
Ok, I have it installed and running great so far...but as far as root, which Pwn version would I use? The Verizon one, the TMobile one, or none?
Thanks for developing for us. Stupid Verizon and their late updates!
Click to expand...
Click to collapse
Didn't you unlock your bootloader?
Sent from my Moto X.
htowngator said:
So basically you create a rom slot, backup to new rom slot, install your update, install su update, and boot to new slot?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Backing up to a new rom slot is really just to have your stock rom on that rom slot. All that is needed is to create the rom slot and then flash this zip.
SubliminalME said:
Ok, I have it installed and running great so far...but as far as root, which Pwn version would I use? The Verizon one, the TMobile one, or none?
Thanks for developing for us. Stupid Verizon and their late updates!
Click to expand...
Click to collapse
Just about to post a link for the zip that I flash in safestrap for root.
codygs83 said:
Awesome work man!
Only one question before I flash this gem.
Does this cause any problems with safestrap??
I only ask because I flashed the tmo ROM the other day with no issues. Had data and WiFi working great. When I rebooted to get into ss I bootlooped like a son of a beotch. Had to fxz back to stock. Saw a few other users with the same problem flashing the same tmo ROM.
Can anyone comment on this??
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
If you have no issues then I wouldn't recommend changing a thing.
BREAK THE CRACKFLASHING HABIT, BROTHER
mj0528 said:
How can this be used on AT&T safestrap?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Theoretically you should be able to use it the same way on AT&T but it may just cause your network to say "Verizon Wireless" in the notification shade and the quick settings tile.
Crooke356 said:
I've had no issues with reboots. I've turned off and on, rebooted to recovery and regular reboots and working great.
My only thing, and I'm new to SS so I know it's something I'm doing, is when I switch to stock slot and then back to where this ROM is, I've lost data on the custom slot. Like I clean flashed. Is there a way to maintain all my user data on slot 1 while switching to stock?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I do not believe this should occur. I would post over on the rootzwiki forum on the SS page because it is probably an issue with SS. Certain user data is getting stored differently because of how the Moto X is set up from what I have gathered. I know Hashcode just change in the new SS where he was storing certain things so that might be part of the problem. Make sure you are on the newest SS and post what occurred over there so hashcode can look into it.
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v363-2013-10-14/
I just installed Cynogenmod 10.2.1 and now have no mobile network, radio in bootloader says 1.01.04.0300, I am s-off. In setting>about phone>status>mobile network state, it says disconnected.
I've done fresh installs of roms before, I'm not new to this, but I'm not sure what happened here.
Any help please?
I'm guessing your phone number is listed as 000-000-0000? Your status bar shows LTE and you have data connectivity but oddly cannot call or text? Strangely multiple people are running into this condition this week.
Check recent posts in this forum - one mentions "000-000-0000" in the subject, another is "SMS and phone issues" or similar. Simple process - they saved my ass last night.
Edit: Subject is "DNA texting and calling issue", "No signal, phone number, SIM problem? Number 000-000-0000"
Sent from my HTC6435LVW using xda app-developers app
Phibernaut said:
I'm guessing your phone number is listed as 000-000-0000? Your status bar shows LTE and you have data connectivity but oddly cannot call or text? Strangely multiple people are running into this condition this week.
Check recent posts in this forum - one mentions "000-000-0000" in the subject, another is "SMS and phone issues" or similar. Simple process - they saved my ass last night.
Edit: Subject is "DNA texting and calling issue", "No signal, phone number, SIM problem? Number 000-000-0000"
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
no my phone number is listed as normal
mobile net work type is LTE
service state is in service
roaming is not roaming
mike17855 said:
I just installed Cynogenmod 10.2.1 and now have no mobile network, radio in bootloader says 1.01.04.0300, I am s-off. In setting>about phone>status>mobile network state, it says disconnected.
I've done fresh installs of roms before, I'm not new to this, but I'm not sure what happened here.
Any help please?
Click to expand...
Click to collapse
Are you GSM? That doesn't work without a patch on 10.2. Either way, go with CM 11 instead of CM 10.2...
crpalmer said:
Are you GSM? That doesn't work without a patch on 10.2. Either way, go with CM 11 instead of CM 10.2...
Click to expand...
Click to collapse
I'm waiting for stable cm 11, I got the radio working but note I have the 000-000-0000 phone number issue
mike17855 said:
I'm waiting for stable cm 11, I got the radio working but note I have the 000-000-0000 phone number issue
Click to expand...
Click to collapse
I can't help with the 000-000-0000 but in general CM 11 is much more stable than CM 10.2.
Try Carbonrom 4.3, it's stable and Ive been running it troublefree for 3+ months. Otherrwise try a Google Edition ROM for the stability and similarity to AOSP. You can supplement any missing things with xposed framework.
All the rom listed above are pretty much stable. I don't believe its a rom error. I believe he/she needs to reflash a radio to fix the partition.
thayl0 said:
All the rom listed above are pretty much stable. I don't believe its a rom error. I believe he/she needs to reflash a radio to fix the partition.
Click to expand...
Click to collapse
I had to reflash stock rom and stock recovery then do a factory reset to fix the radio partition. Once that was done I was able to reflash CWM and a custom rom, I just went with CM 11 and it seems to be stable from what I've seen so far.
TY for yalls help, it took some research and effort.
http://forum.xda-developers.com/showthread.php?t=2568696
mike17855 said:
I had to reflash stock rom and stock recovery then do a factory reset to fix the radio partition. Once that was done I was able to reflash CWM and a custom rom, I just went with CM 11 and it seems to be stable from what I've seen so far.
TY for yalls help, it took some research and effort.
Click to expand...
Click to collapse
Your welcome.
Thanks
mike17855 said:
http://forum.xda-developers.com/showthread.php?t=2568696
Click to expand...
Click to collapse
This helped.. Thanks