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

Root [5.1.1][UNOFFICIAL] Paranoid Android 5.1 [12.30.2015]

Ive been saying for months now that there will not be a fix for CDMA. They will leave us all behind. Boost Mobile will never get the 5.0 update for any CDMA phone. There is no fix people.
 
Ive been saying for months now that there will not be a fix for CDMA. They will leave us all behind. Boost Mobile will never get the 5.0 update for any CDMA phone. There is no fix people.
Don't be so pessimistic! Im not sure how reliable this is, but someone on XDA claims to have asked a Boost Mobile rep about an update and was told they knew nothing. They then asked a Motorola rep and were told rest assured we will eventually get the update. A Motorola dev made a post on Google+ reassuring everyone the update was coming because theres so much negative talk. I keep telling people it hasn't been that long since we got 4.4.4, and there are very few phones with lollipop still. We should all stop cluttering Seraph's thread with this stuff when there's plenty others to discuss this stuff.
 
To say there will be no CDMA lollipop fix is just preposterous.. There are literally millions of CDMA devices that are to be updated. I can't believe this notion would even be entertained. All moto g will be updated I'm willing to bet on it.
 
I haven't noticed any major bugs with this ROM. Nothing that isn't a problem with CM12 anyway, but you can only test just so much with no data, etc. I can't go long without these either so I don't miss an important phone call or something.
 
I haven't noticed any major bugs with this ROM. Nothing that isn't a problem with CM12 anyway, but you can only test just so much with no data, etc. I can't go long without these either so I don't miss an important phone call or something.
Looks like one of the devs on XDA is working on submitting a patch to CM regarding the setupwizard...apparently that's part of the problem as the device is "preparing" after boot its looking for a Sim card not a CDMA device...may be s step in the right direction.
 
Looks like one of the devs on XDA is working on submitting a patch to CM regarding the setupwizard...apparently that's part of the problem as the device is "preparing" after boot its looking for a Sim card not a CDMA device...may be s step in the right direction.
The problem was brought to the attention of Recognized Developer Somcom3X on the Officially CM12 Nightly thread, who says he wants to help fix it. This should have happened weeks ago. I guess from what I heard CM was denying CDMA was broken. This is definitely a very good step in the right direction.
 
The problem was brought to the attention of Recognized Developer Somcom3X on the Officially CM12 Nightly thread, who says he wants to help fix it. This should have happened weeks ago. I guess from what I heard CM was denying CDMA was broken. This is definitely a very good step in the right direction.

Yeah its been brought up since the first nightly, but the CM Team/falcon maintainer doesn't acknowledge a problem with CDMA so there is a problem with reporting a regression to the CM branch...the new thought process being tossed around is a XT1028/31 specific build sans all the GSM stuff. So unless there's a patch in AOSP or a CM maintainer for falcon takes notice and makes an effort...the fix will likely come from a independent developer in our community(like usual). I'm not sure what percentage of users have the xt1028/31 but hopefully someone will figure it out for us.
 
This was used in Aurora to get cdma radios working back in 4.4.X can't vouch for it as I've just never used that rom, may be worth a look though...

"in the init.mmi.rc to set ro.hw.radio based on the ro.boot.radio value, from there I use init.mmi.radio.sh to set the appropriate build.prop values based on the radio detected to be stock for the device."
 
This was used in Aurora to get cdma radios working back in 4.4.X can't vouch for it as I've just never used that rom, may be worth a look though...

"in the init.mmi.rc to set ro.hw.radio based on the ro.boot.radio value, from there I use init.mmi.radio.sh to set the appropriate build.prop values based on the radio detected to be stock for the device."
There'll be a better way soon! I was just informed by a Boost user on XDA, that they received an email for an early update. I instructed them on how to prepare for it and to copy the zip so it can be used to make a flashable rom zip, and hopefully fixing CM12 data.
 
There'll be a better way soon! I was just informed by a Boost user on XDA, that they received an email for an early update. I instructed them on how to prepare for it and to copy the zip so it can be used to make a flashable rom zip, and hopefully fixing CM12 data.

Better not be screwing with us bruh
 
Hey guys just reflashed the sock recovery...all I get is a dead android with an exclamation triangle... Is this normal or do I need to flash the recovery by another means?
 
nah nothing yet that im aware of, thanks for the nod at xda also.
No problem man you built a great version... Its by and far the most stable source built ROM for this phone imo. Smoother than CM and CM based and none of the issues that AOSP builds have. Granted there's not as many bells and whistles but for me stability wins out over flash any day. Function before form.
 
ok so I tried the last pa5.0 build (the one with the wierd name and ota written) It didn't flash and the phone is stuck at bootlogo. I tried with philz it was stuck at installing update and the same thing happened on twrp. I am on lollipop bootloader on xt1031
 
Last edited:
for some reason my FTP client didn't upload the last build correctly. I'm doing it now with the latest one. I apologize, this was my mistake.
 
Back
Top Bottom