Related
I just installed a custom rom onto my AT&T Thrive/P506 for the first time, and everything is coming up with weird graphical glitches/colors.
I've tried both the CM7 and devoid ROMs, but both are doing the same thing. The initial LG screen looks fine, but once the ROM loads I only get a weird blue/green screen. I followed the directions as stated. It appears as though a graphics driver or something is not being installed properly.
Has anyone seen this before? Any help is greatly appreciated.
I am in the same boat. Can anyone help please !!!
Btw Dangelone, what does your phone model say in About Phone.
I have the same problem to. I kept the stock rom and flashed the kernel and i got the same thing too. Im starting to think it's just the kernel that messes up the screen.
Anyone got a rom that works for the LG thrive P506? Most roms give messed up color display but functions all work.
I hope someone at least tries to make one, I can't because I have no idea where to start. I'm starting to think that the devs wouldn't even want to try since this is a lower-end Android phone and that they higher-end ones are more exciting. But for the goodwill of the community maybe there will be one good person who will attempt to make a fully functional custom rom for us LGP506 owners.
backup ur stock kernel, flash custom rom, then restore stock kernel?
Hello everyone, I'm trying to do a buddy of mine a favor by upgrading his Vibrant to something a lot better (he's on stock) but I'm a bit unclear on a few things. First of all let me get out of the way that I'm a Fascinate (Verizon) owner that recently modded my own phone to run AOKP ICS Milestone 6 with great results, so I figured since he pretty much had the exact same phone I could do it for him. The problem I'm running into is the procedure I used to flash my phone doesn't seem to apply to the Vibrant (or at least what I was searching for) so I just wanted to clear up a few steps before I try to flash his phone.
He's not a very tech savvy guy, so he won't be updating ROMs on the bleeding edge or anything, he just wants his phone to run better so I figure ICZen is the way to go right, considering it's based off of what I'm using now (AOKP M6)? Everything needs to work, so that pretty much rules out any JB right now because of the GPS issues. Okay now onto the specific flashing questions:
1) This thread seems to be the go to thread for flashing the Vibrant, but it hasn't been updated since Dec '11, so would I just follow the same procedure for the newer ICS roms?
2) Here is the guide I used for my Fascinate (see section 4), which has a few extra steps that I notice are lacking for the Vibrant... namely installing cwm4 fixed for cm7 first, then installing THS Build 2, then flash over that with whatever ICS Rom you need.
3) Devil Kernel is what's considered best on my phone running AOKP M6... is that true as well for ICZen?
4) Since the Vibrant never got 2.3, what is the best modem to be using? On the Fascinate the EH03 (GB) stock modem is best, but I'm unsure what the deal is for the Vibrant since they never got an official GB update. Also along the same topic, Verizon has a code you can input that updates your PRL and improves reception... does T-Mobile have such a code or not?
I appreciate any and all input, as I want this to go as smoothly as possible. Thanks
You seem to have a pretty good grasp on what your doing.
From stock, install gingerbread bootloaders then go to recovery via volume rocker down and hold power button, until the logo. Might have to practice it a couple times.
Once in recovery click reinstall packages, might have to do it s couple of times. This installs your update.zip
From here I always perform wipes and flash a custom Froyo ROM. Maybe overkill but, only takes a second and I don't mind.
From here I flashed the latest CM9 nightly and on to Helly Bean.
Do your wipes in between flashes, and you should be fine.
I haven't ever heard about a T-Mobile code for tower updates, I think its automatic.
Well I didn't have to worry about bootloaders on my Fascinate since I was already on GB, so that's a bit new to me... but doing a quick google search I found this guide. Is that an accurate guide to follow? Alright so basically what you're saying is before I root at all I need to do this?
Also like I was saying earlier, he wants everything to work so I think Helly Bean is out of the question because of GPS, right? I was thinking ICZen looks the cleanest, with everything working nicely, and it's based on what I'm currently using on mine.
Can you clarify on why you're flashing a custom froyo rom? I won't mind to do that either, if it has any benefit.
Also, I checked his phone last night and it's on stock 2.2, not 2.1 if that makes any sort of difference. Thanks again
First root and get cwm recovery then flash bootloaders. The vibe never got an official GB, so that's why boot loaders are recommended. The guide you have is fine. Second the GPS on the vibrant has been notoriously hit or miss. I have a captivate, the GPS works great but my vibe couldn't get a lock to save my life.
Now as far as iczen or hellybean, you have to weigh the options:
Iczen is a great ROM and might have a better chance getting a GPS lock. IMO if you can get a lock with ICS you will probably get a lock with JB. But with ICS you have to be concerned with the EU bug. What's that you ask:
There has been an issue with people randomly looking at phone and a message saying encryption unsuccessful press to reset. If you press the button you have basically just locked up your internal SD card. If you don't press you MIGHT be able to recover it. There is a workaround if this happens, to use ext SD only but your friend will not like that.
I'm currently running hellybean on both of my devices and I love it. Like I said, cappy gps works great and my vibrant not so much. If you really want stable go with bionix as toast recommended or one of moped Ryder's ROMs . If you want to be wowed, go with hellybean.
There are some things you can try with it to get a GPS lock. The general consensus is turn on GPS, reboot, wait it out till you get an initial lock. After that locks will be quicker. I hope this helped in some way, if so hit thanks. As far as the guides etc you are good to go.
its peanut butter jelly(bean) time
That did help quite a bit, thank you. I have never even heard of that bug, do you know if that's Vibrant specific or can that happen on any of the others? I have been wanting to try Helly Bean on my Fascinate, but unfortunately my sdcard isn't very stable and I don't trust to flash anything until I can buy a new one. Honestly, I don't even think he cares much about the GPS, my original point was more along the lines of that I wanted to give him as much of a glitch-free experience as possible, so my fault for not being more specific. If Helly Bean is as stable as you're saying, then maybe I'll just do that instead then, especially after you explained that glitch. Also, since I don't have any Helly Bean experience myself, does it offer as much customization as AOKP? I've grown quite fond of all the little tweaks they include
Hellybean is pretty stable. When I did my vibrant I didn't have to use a boot loader I went straight to ICS then jellybean. If you want ICS then you may want to try aokp for his vibe its nice. If you end up trying aokp milestone 6 and have unknown baseband let me know and I'll link you to a linario build that should fix that
Sent from my SGH-T959 using xda app-developers app
I have a complete guide to install ICS ROMs in my signature if you feel so inclined. PM me if you need any of the files or I may just host them on my Dev-Host account. I'll be out most of the day, but I can upload them later on tonight.
When I need to go back to stock and root and flash cwm I use the AIO toolbox. I just put the rom on the internal flash and then use AIO to get cwm on it from the flash custom rom option. Then cancel the file and the phone will reboot into recovery where you install packages twice and should end up in cwm.
The EU bug has hit vibrant and captivates that I know of. It seems rare though, if you think about the number of users compared to the reported number of cases of the EU bug, its a small percentage.Hellybean doesn't have nearly as much customization but it does offer theming and some launcher/lock screen tweaks. You could always use a custom launcher. There are a few other jellybean ROMs you could try. Honestly any way you go will be better than stock!
*I forgot to tell you, you will need to Odin back to stock 2.1!
its peanut butter jelly(bean) time
Yeah.. I don't think root is actually necessary to do any of this. You'll be rooted when the process is complete however. The custom ROMs come with root access.
But to elaborate on Samsgun357's last post, if you are currently on Froyo 2.2 stock, you'll need to Odin back to stock 2.1 prior to starting, because Samsung fixed the bug that allows installation of custom recovery when they released 2.2
It's simple to do, search the forums and you'll find a guide on Odining back to JFD. That's stock Eclair. If I have time in a few I'll locate it for you and post it.
There are YouTube videos about it with links to the files as well. I think djeddie1west posted a good one with links to all files needed, if they are still working links.
Edit: http://forum.xda-developers.com/showthread.php?t=1117990
There's the link for installing GB bootloader.
Also, I am on my phone and haven't tested links, but as long as they work, near the bottom of the post you'll find the files needed to Odin the JFD files.
Eh, I just gave up and told him to go get an iPhone instead, to increase his hipster status.
Or... that's right, I'd rather be dead than own one of those ugly bricks.
You have all been extremely helpful, and I think I have more than enough to go on. I think for now I'll just throw ICZen on his phone since it's based on the rom I'm most familiar with... and when I have more experience with Helly Bean (I finally ordered a new sdcard that's on the way, so I can play with it on my own phone soon enough :good I'll just flash his again. He'll be okay with the risks mentioned so far in this post, and honestly his upgrade is coming up soon so I'm sure I'll be drooling over his S3 when that time comes.
@Woodrube That guide you made to install ICS was exactly what I was looking for, and I wish I had found it earlier so thank you for making such an excellent post.
I'll post back here with the results, thanks for all the help once again
I have a Galaxy S2, I9100, original, I had the LoS Kernel from early on, and I have had recent troubles upgrading. I've upgraded to Dream Kernal, Siyah Kernal, and several other kernals. The phone boots when I load each individual rom, however, several services fails to load.
Am I missing something? I haven't updated this phone since it first came out, and after months of "update messages" from Sprint, I've decided to update it and I'm having difficulty. I've got CWM downloaded and I've used CWM to update each rom and kernel. If I could get some direction that'd be great. I just want the latest Android version and some type of superficial visual ROM ontop. I am generally very okay with each ROM, just upset that the current kernal leaves me with a failure of signal, causing me to reboot.
Update
I currently have Kernel version 3.043-rc1-Siyah-Dorimanx-V5.78-SGII-PWR-CORE and AOKP Version ThunderBolt Rom JB by ALHuessein Mohammed and Android version 4.1.1. . My Build is ThundrBolt by ALHussein Mohammed and I can't get any of my active services to work. Wifi doesn't work, sending texts doesnt work, surfing the internet doesn't work. Nothing. I get the phone to boot, but nothing comes of my boot. I have tried several different kernels, and different ROMs, but none of them seem to fix the issue of standard services working. I'd appreciate some help with the issues. My CWM version is 6.0.1.2-Siyah. I'm pretty confused on the whole matter.
As far as my knowledge goes, the Kernel is like the underlying infrastructure, and the ROM is like the OS. I don't really know what I've done to **** this **** up, but it's no longer functioning as a regular phone. I've used ODIN before, but seeing how I have CWM, I figured it wasn't required. Any help would be appreciated. Even setting my phone back to stock, since backing up my phone through CWM didn't actually do anything, since I can't restore back to my previous version.
I'm in dire need. Please assist.
--Zach
So no one has any idea why my phone boots, but every active service fails to load? I guess I'll have to call this one a loss.
zdavidi said:
So no one has any idea why my phone boots, but every active service fails to load? I guess I'll have to call this one a loss.
Click to expand...
Click to collapse
hey ma8 first and foremost u should have patience here on XDA.
bumping Post like this will lead u knowhere and people will simply ignore the same for sure
now coming back to ur issue what i would suggest u is this before jumping into kernel flashing thing have u checked in the ROM thread of the one ur using for what kernel people r using there r any kernel related post in that thread.
if not do the same first (search that thread for post that r similar to ur issues).
also u can try the latest Siyah kernel v4.1.5 and see
zdavidi said:
I have a Galaxy S2, I9100, original, I had the LoS Kernel from early on, and I have had recent troubles upgrading. I've upgraded to Dream Kernal, Siyah Kernal, and several other kernals. The phone boots when I load each individual rom, however, several services fails to load.
Am I missing something? I haven't updated this phone since it first came out, and after months of "update messages" from Sprint, I've decided to update it and I'm having difficulty. I've got CWM downloaded and I've used CWM to update each rom and kernel. If I could get some direction that'd be great. I just want the latest Android version and some type of superficial visual ROM ontop. I am generally very okay with each ROM, just upset that the current kernal leaves me with a failure of signal, causing me to reboot.
Click to expand...
Click to collapse
Several contradicting pieces of information here that I've bolded.
The I9100 is a GSM phone. Sprint is a CDMA network. The I9100 won't even work on Sprint's network.
When I google for "LoS kernel site:forum.xda-developers.com", the first result I get is for this, which is an Epic 4G Touch kernel.
These things tell me you are not in the correct forum for your device.
The Sprint variant for the Galaxy S2 is the Epic 4G Touch, and that forum is located at http://forum.xda-developers.com/forumdisplay.php?f=1281
ctomgee said:
Several contradicting pieces of information here that I've bolded.
The I9100 is a GSM phone. Sprint is a CDMA network. The I9100 won't even work on Sprint's network.
When I google for "LoS kernel site:forum.xda-developers.com", the first result I get is for this, which is an Epic 4G Touch kernel.
These things tell me you are not in the correct forum for your device.
The Sprint variant for the Galaxy S2 is the Epic 4G Touch, and that forum is located at http://forum.xda-developers.com/forumdisplay.php?f=1281
Click to expand...
Click to collapse
Yeeeahh. I had searched Samsung Galaxy SII, and I was led here. I had forgotten that my particular phone was an Epic 4G Touch. Thanks for the direction.
So, I have been reasonably experienced in the Android world with terms to Nexus devices and Samsung but HTC still confounds me. I have an S-Off Rezound, it is on GB Firmware and everytime I flash a ROM I have to flash a fix for old firmware or else is random reboots. I have searched and searched on different occasions for the answer to this but I have yet to find a straight answer. Feel free to flame me, be rude, etc., but can someone please point me in the right direction. My Fiancee loves her Rez, has been running sense 4.1 since we got it (it was s-off when we got it, a happy surprise from the seller we bought it from on eBay.) But she is weary of the extra steps she needs to take to update a ROM. Can anyone point us in the right direction?
[/COLOR]
loveableterrorepic4g said:
So, I have been reasonably experienced in the Android world with terms to Nexus devices and Samsung but HTC still confounds me. I have an S-Off Rezound, it is on GB Firmware and everytime I flash a ROM I have to flash a fix for old firmware or else is random reboots. I have searched and searched on different occasions for the answer to this but I have yet to find a straight answer. Feel free to flame me, be rude, etc., but can someone please point me in the right direction. My Fiancee loves her Rez, has been running sense 4.1 since we got it (it was s-off when we got it, a happy surprise from the seller we bought it from on eBay.) But she is weary of the extra steps she needs to take to update a ROM. Can anyone point us in the right direction?
Click to expand...
Click to collapse
RUU http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
1st flash RUU(it will give you new firmware permanently)
2nd flash any rom with new firmware
Or ....
Download this
http://old.androidfilehost.com/main/-Support_Files-/SuperChilPil/[ICS][2.27][STOCK][8-12]PH98IMG.zip
but don't run it as a PH98IMG just yet, replace the hboot in it from this
http://old.androidfilehost.com/main/-Support_Files-/SuperChilPil/[ICS][2.25][STOCK][5-7]PH98IMG.zip
You will be soft-bricked until you flash a new rom/re-flash your current one.
Thanks guys, appreciate the info. She is going to run the RUU today and probably just go back to newts one xxx for global. She was getting tired fo forgetting to flash the "fix" everytime she updated.
You don't need to RUU if you're s-off, you can flash just the firmware, keep in mind you'll need to reverse the old firmware patch, that's available in the link below too..
http://forum.xda-developers.com/showthread.php?t=1614366
Global would be - [ICS][2.27][STOCK][8-12]PH98IMG.zip, follow the directions in the post to install it.
Back up your rom just to be safe but you should be ok just flashing the combo you want along with the "new" firmware patch.
EDIT - Just realized Snuzzo posted the same thing, it's linked from the XDA post above which has directions in it.
******** First off, let me say, that I'm not sure where to post this, so I'm taking a stab here, but it might be better suited for the "Sprint HTC EVO 4G LTE > HTC EVO 4G LTE Android Development" threads, that being said, let me know. ********
Feeling really lost, and could really use a friend *sniff*
I keep running into pitfalls, and I think it's because I just have bad timing. I know that the Evo LTE is getting close to EOL, and a lot of dev's have either moved onto to new hardware, lost interest in this device, or are now playing around with the new 4.3 RUU or KitKat builds for this device....
I've been heavily modded on many of my older devices, but with my Evo lte I've been stock (rooted, but still S-On) for over a year now, and I'm just starting to want to get more out of this device.
I did a ton of Google searches for ROM's and finally homed in on one, Beanstalk (the older 4.3 stable builds), but I'm just running into issues at every turn.
Currently I'm on Viper4G 3.1.7, purely because it saved my ass, when I tried going to Beanstalk while still S-On (whoops).
I'm currently S-Off with moonshine
HBOOT 2.09.4444
RADIO 1.12.11.1210
while I can now get Beanstalk to install, and boot, and GApps (jb-20130813), I CAN NOT get my phone to activate, I spent probably 4 hours and MANY reboots and re-flashes trying to get it to let me activate. I've tried both the "Stable (8/27)" and the "Latest Stable (9/17)" builds, both do the exact same thing.
So, needing a working phone, I'm back on Viper4G, and wondering, what is the best ROM to look at for this device?
I would post in the Beanstalk thread, but the dev has already said
I just don't feel the excitement for this phone anymore. Last Saturday I was ready to give this phone up...
Click to expand...
Click to collapse
and until I posted something in that thread, it hadn't been touched since Dec of 2013...annnnd then a senior member even said
This is probably the wrong thread to post in since it's been dead since Dec.
Click to expand...
Click to collapse
so, I just don't know what ROM I should be looking at, and where to get help on these older ROMs when they have hiccups on install. Can anyone suggest a ROM?
Personally it seems like KitKat needs a little more time in the bakery before I feel ready to put it on my daily use phone.
I even thought about going with the 4.3 RUU right from HTC, but then I started reading all the bugs people where running to, and the fact that you can't downgrade has me worried, and so, like I said about KitKat, I think I just wanted to give that a bit more time as well.
So in a round-about way, I guess I'm asking, what ROM should I be looking at? Is Beanstalk currently the best for this device (I know that's heavily subjective) or is there another ROM I should be looking at that still has active members to bounce issues off of if I run into installation issues?
EvilRSA said:
******** First off, let me say, that I'm not sure where to post this, so I'm taking a stab here, but it might be better suited for the "Sprint HTC EVO 4G LTE > HTC EVO 4G LTE Android Development" threads, that being said, let me know. ********
Feeling really lost, and could really use a friend *sniff*
I keep running into pitfalls, and I think it's because I just have bad timing. I know that the Evo LTE is getting close to EOL, and a lot of dev's have either moved onto to new hardware, lost interest in this device, or are now playing around with the new 4.3 RUU or KitKat builds for this device....
I've been heavily modded on many of my older devices, but with my Evo lte I've been stock (rooted, but still S-On) for over a year now, and I'm just starting to want to get more out of this device.
I did a ton of Google searches for ROM's and finally homed in on one, Beanstalk (the older 4.3 stable builds), but I'm just running into issues at every turn.
Currently I'm on Viper4G 3.1.7, purely because it saved my ass, when I tried going to Beanstalk while still S-On (whoops).
I'm currently S-Off with moonshine
HBOOT 2.09.4444
RADIO 1.12.11.1210
while I can now get Beanstalk to install, and boot, and GApps (jb-20130813), I CAN NOT get my phone to activate, I spent probably 4 hours and MANY reboots and re-flashes trying to get it to let me activate. I've tried both the "Stable (8/27)" and the "Latest Stable (9/17)" builds, both do the exact same thing.
So, needing a working phone, I'm back on Viper4G, and wondering, what is the best ROM to look at for this device?
I would post in the Beanstalk thread, but the dev has already said and until I posted something in that thread, it hadn't been touched since Dec of 2013...annnnd then a senior member even said
so, I just don't know what ROM I should be looking at, and where to get help on these older ROMs when they have hiccups on install. Can anyone suggest a ROM?
Personally it seems like KitKat needs a little more time in the bakery before I feel ready to put it on my daily use phone.
I even thought about going with the 4.3 RUU right from HTC, but then I started reading all the bugs people where running to, and the fact that you can't downgrade has me worried, and so, like I said about KitKat, I think I just wanted to give that a bit more time as well.
So in a round-about way, I guess I'm asking, what ROM should I be looking at? Is Beanstalk currently the best for this device (I know that's heavily subjective) or is there another ROM I should be looking at that still has active members to bounce issues off of if I run into installation issues?
Click to expand...
Click to collapse
If s-off you can downgrade via older ruu, viperruu I believe but don't quote me on it. As for me I haven't had any issues on the new update. me personally I'm not a fan of aosp roms. My personal favorite is the 4.3 sense 5.5 from sin and chubbz. I've tried some of the aosp for the new format and those are the ones that I had data problems with. Viper does have a rom for the new layout as well as Yankees. But then again it's all user preference. Personally I would strongly recommend running the new ruu. Captain has a thread listing aosp roms built for the new layout if that is what you are interested in.
http://forum.xda-developers.com/showthread.php?t=2654590
[ROM][AOSP] CM11 & other AOSP-based ROMs that support updated partition layout
HTC Jewel
HBOOT 2.10 S-OFF (rumrunner)
Android 4.3 Sense 5.5 V3
EvilRSA said:
******** First off, let me say, that I'm not sure where to post this, so I'm taking a stab here, but it might be better suited for the "Sprint HTC EVO 4G LTE > HTC EVO 4G LTE Android Development" threads, that being said, let me know. ********
Feeling really lost, and could really use a friend *sniff*
I keep running into pitfalls, and I think it's because I just have bad timing. I know that the Evo LTE is getting close to EOL, and a lot of dev's have either moved onto to new hardware, lost interest in this device, or are now playing around with the new 4.3 RUU or KitKat builds for this device....
I've been heavily modded on many of my older devices, but with my Evo lte I've been stock (rooted, but still S-On) for over a year now, and I'm just starting to want to get more out of this device.
I did a ton of Google searches for ROM's and finally homed in on one, Beanstalk (the older 4.3 stable builds), but I'm just running into issues at every turn.
Currently I'm on Viper4G 3.1.7, purely because it saved my ass, when I tried going to Beanstalk while still S-On (whoops).
I'm currently S-Off with moonshine
HBOOT 2.09.4444
RADIO 1.12.11.1210
while I can now get Beanstalk to install, and boot, and GApps (jb-20130813), I CAN NOT get my phone to activate, I spent probably 4 hours and MANY reboots and re-flashes trying to get it to let me activate. I've tried both the "Stable (8/27)" and the "Latest Stable (9/17)" builds, both do the exact same thing.
So, needing a working phone, I'm back on Viper4G, and wondering, what is the best ROM to look at for this device?
I would post in the Beanstalk thread, but the dev has already said and until I posted something in that thread, it hadn't been touched since Dec of 2013...annnnd then a senior member even said
so, I just don't know what ROM I should be looking at, and where to get help on these older ROMs when they have hiccups on install. Can anyone suggest a ROM?
Personally it seems like KitKat needs a little more time in the bakery before I feel ready to put it on my daily use phone.
I even thought about going with the 4.3 RUU right from HTC, but then I started reading all the bugs people where running to, and the fact that you can't downgrade has me worried, and so, like I said about KitKat, I think I just wanted to give that a bit more time as well.
So in a round-about way, I guess I'm asking, what ROM should I be looking at? Is Beanstalk currently the best for this device (I know that's heavily subjective) or is there another ROM I should be looking at that still has active members to bounce issues off of if I run into installation issues?
Click to expand...
Click to collapse
Being that you're S-off, it is possible to downgrade after running the 4.3 RUU. Also you can try updating your firmware. I haven't been on any of the older partition layout ROMs for quite a long time but I do recommend running the RUU. You will remain S-off and your bootloader may even remain unlocked. (Mine did) If not, it's not a big deal to unlock it again. Most of the limited development remaining for this device is based around the new partition layout. There is even a new Viper build. Just my ยข2.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Greeting,
I moved your thread to Q&A, please post questions in Q&A in the future
Thank You,
BD619
BD619 said:
Greeting,
I moved your thread to Q&A, please post questions in Q&A in the future
Thank You,
BD619
Click to expand...
Click to collapse
Congrats on the moderator status!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Here's a tip for the OP. Flash the rom, then reboot into Android without flashing Gapps. THEN reboot into recovery again and flash Gapps. You won't encounter the Welcome screen, so you'll have to add your account through the settings. The same problem happens to me, no matter which AOSP rom.
aarsyl said:
Here's a tip for the OP. Flash the rom, then reboot into Android without flashing Gapps. THEN reboot into recovery again and flash Gapps. You won't encounter the Welcome screen, so you'll have to add your account through the settings. The same problem happens to me, no matter which AOSP rom.
Click to expand...
Click to collapse
You know, I did notice that. I didn't post that permutation of installation steps, but I did find that if I flashed either of the "stable" or "latest stable" builds of beanstalk WITHOUT GApps, I could get around the welcome screen, but I still couldn't place a call. Also I noticed that my PRL version was sky high for what I should have. Currently have 16018, but when I checked it while on Beanstalk it was something like 65002 (if my memory is correct) could this be causing issues too?
I never checked the PRL version whole on AOSP, so I truly couldn't tell you.