-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [Boost Mobile] Working ROMS/MODS/KERNELS/MODEMS/ECT for the Boost S3
- Thread starter wetbiker7
- Start date
-
- Tags
- samsung galaxy s3
codezer0
Android Expert
Well, so far this is turning out to be the worst advice I've received yet, because so far everything I've tried to run has turned out crap.If you want to try something and don't know what just try them all!As long as you keep a backup of your current setup there's nothing to lose. Hell I've flashed roms that haven't been supported or updated in a year just to try something new. Hi my name is Dustin and I'm a flashaholic.
All the *OKP ROMs all crash on android.systemui and android.phone, even when just peeking through the available settings, much less when actually using the phone. Some more frequently than others.
SOKP won't let me update Xposed at all and won't let me update any of the programs that require it.
SlimKat wouldn't even let me use a camera app at all, much less let one actually write/save any pictures I try to take.
And I've yet to be able to get a single version of MOAR (as much as I detest what a battery hog it is) to actually flash since going from TWRP to PhilzTouch Recovery.
Guys, I can't stress enough that I can't have a phone that keeps crashing on me like this. And so far it seems like each build I try just gets worse than the last. So what am I supposed to do here?
mydian
Android Expert
That's weird. I've flashed every moar version (I think) with Philz and aside from every 4.3 TW rom having unusable call quality for me the rest of the rom seemed to work fine.
Also some of your posts seem confusing like your mixing up AOSP with AOKP. AOKP, like CM, is based off of AOSP.
Also some of your posts seem confusing like your mixing up AOSP with AOKP. AOKP, like CM, is based off of AOSP.
mydian
Android Expert
Also I was just thinking since I have been researching and reading and reading about AOSP, AOKP, CM11, etc and I'm wondering if some of these force closes you guys are getting could possibly be coming from the Google Apps package you're using? I saw AOKP has their own. I don't know what the difference is since I'm a noob but I thought I would throw that out there.
cwhatever
Life Goes On
That is what I have heard too. I do not run any of those roms. But they say you have to use the gapps that come with those roms
I use a modified version of the PA 0 Day GAPPS on AOKP. I've taken out the apps of the zip that i will end up uninstalling anyways.
on L.S. I never get to the GAPPS flash before FCs start happening.
I always flash:
1. ROM
2. sit for 5 min, then setup
3. Flash GAPPS
4. set up apps and ROM
5. Flash Boost AOSP APN fix. Since i use Wifi to setup anyways.
(always clear cache and davlick when leaving recovery)
on L.S. I never get to the GAPPS flash before FCs start happening.
I always flash:
1. ROM
2. sit for 5 min, then setup
3. Flash GAPPS
4. set up apps and ROM
5. Flash Boost AOSP APN fix. Since i use Wifi to setup anyways.
(always clear cache and davlick when leaving recovery)
codezer0
Android Expert
Doesn't matter. with every build I've used the associated gapps whatever it comes with. the problem is that it doesn't seem to fix anything, and in many cases seems to make it worse.
I'm beginning to wonder if there's even an OKP or OSP that even works, or what the point of such a ROM is if they're never stable...?
cwhatever
Life Goes On
I think you're supposed to flash the gapps before you even boot the system up for the first time then you let it sit 5 minutes to do all the other stuff
was just throwing it out there that in just my personal case, it wasn't the GAPPS. But, yes, it shouldn't matter whether the GAPPS are flashed at the same time directly after the ROM or not.
That's just how I personally get the best results from flashing from my phone. Everyone's is different.
wyelkins
Android Expert
The system UI crash thing started happening to me with the final version of LiquidSmooth. I rarely got that on prior builds. Apparently some other Roms are getting it too. I am sure this will be fixed. In my case, while it is annoying, it does not seem to really screw anything up. Usually it goes back to the lock screen. If it really bothered me, I would switch back to in older build.
That being said, while I was typing that my phone froze up and I had to reboot. Poetic Justice, I guess. Lol.
I think it is important to state the obvious in that if you are a Rom flasher you are by your very nature a beta tester. These Roms won't be perfect. If you expect that, it is probably better for your stress level to stay with stock.
I think we have a great bunch of people on this forum, who will help anyone any way they can. Nice place to hang out.
I can honestly say that these recent UI crashes are by far the worst I have had on Kit Kat roms. I am going to switch back to AICP and see what happens.
I have not run much TW since MOAR 8.0 and Wicked Sensations, so I don't know about the newer versions, but those ran great for me.
That being said, while I was typing that my phone froze up and I had to reboot. Poetic Justice, I guess. Lol.
I think it is important to state the obvious in that if you are a Rom flasher you are by your very nature a beta tester. These Roms won't be perfect. If you expect that, it is probably better for your stress level to stay with stock.
I think we have a great bunch of people on this forum, who will help anyone any way they can. Nice place to hang out.
I can honestly say that these recent UI crashes are by far the worst I have had on Kit Kat roms. I am going to switch back to AICP and see what happens.
I have not run much TW since MOAR 8.0 and Wicked Sensations, so I don't know about the newer versions, but those ran great for me.
wyelkins
Android Expert
I have done that, but in my case I almost always flash the Rom and boot first. I do this because I don't have Wi-Fi and I want to get data working first, whatever that entails.
Then I flash the gapps and set up the Google stuff so that I can sync
codezer0
Android Expert
Well, short of making yet another thread, I will ask again.
I can't go back to stock because it will then incessantly nag me into getting knox'd up. And I don't appreciate the idea of Samsung basically making my warranty void because I do happen to run a few apps that require root just to work at all.
I was Happy With StaticPower v2... but the incessant nagging to update to a knox'd rom is the big reason that pushed me to start looking elsewhere. But so far every single one of these AOSP ROMs has been an absolute mess.
Without fail, every time I go into settings->more (regarding mobile data)->mobile networks and even tap to view the settings below the preferred network type (such as mobile plan, etc), android.phone crashes. Intermittently while doing anything with the phone - which has mostly now been just trying to get the apps back that I want/need - I would get the android.systemui crashing and kicks me back out to the lock screen, which completely interrupts what I was doing, and that's really *expletive* annoying. And despite all the apparent included power management stuff that seems to have been added to most of these ROMs, all of them have been definitely eating more power per day than what I was running. Even on a busy day I could at least get three full days of battery with StaticPower. Every single one of these AOSP roms seem to want to drain the battery dry in 1.5 even when I'm just doing basic stuff.
I can't go back to stock because it will then incessantly nag me into getting knox'd up. And I don't appreciate the idea of Samsung basically making my warranty void because I do happen to run a few apps that require root just to work at all.
I was Happy With StaticPower v2... but the incessant nagging to update to a knox'd rom is the big reason that pushed me to start looking elsewhere. But so far every single one of these AOSP ROMs has been an absolute mess.
Without fail, every time I go into settings->more (regarding mobile data)->mobile networks and even tap to view the settings below the preferred network type (such as mobile plan, etc), android.phone crashes. Intermittently while doing anything with the phone - which has mostly now been just trying to get the apps back that I want/need - I would get the android.systemui crashing and kicks me back out to the lock screen, which completely interrupts what I was doing, and that's really *expletive* annoying. And despite all the apparent included power management stuff that seems to have been added to most of these ROMs, all of them have been definitely eating more power per day than what I was running. Even on a busy day I could at least get three full days of battery with StaticPower. Every single one of these AOSP roms seem to want to drain the battery dry in 1.5 even when I'm just doing basic stuff.
- SOKP
- Would not let me update Xposed - at all. It refused to install any updates to Xposed or any other apps or updates that use it.
- What good is the GPS optimizer when it basically broke the GPS to begin with?
- Despite enabling the dolby digital driver, it certainly didn't seem to improve audio quality at all.
- Why is there no officail release of CM11 for these phones?
- AOKP
- Um, it went into a crash loop with android.keyboard, and thus I couldn't even finish the initial setup. I had to yank the battery out because the notification of it crashing wouldn't let me do anything else
- LiquidSmooth
- How about the fact that it kept nagging that it wants me to update that inspire launcher but then refuses to let me see what was updated about it.
- SlimKat
- Specifically, the fact that this one constantly made it so that no camera app could access the camera in the first place, even from a fresh boot.
- Or for that matter, the fact that i had since lost many shots that I would have wanted to keep, because SlimKat decided that it didn't need to save the pictures in the first place
Codezero, for the Ota nag I use an app file called for fotakill.apk that you just place the app file in system/root and reboot. I've used it multiple times when I had to flash back to TW 4.3 from aokp or cyanagen roms and the nag always stayed at bay, I never got the nag after, except one time maybe, and I just clicked update later, it never did show after that though.
If you can't find the apk file let me know I'll see if I can't get it uploaded to download for ya.
HiiiPowers
Android Enthusiast
AOKP? Yes, I just finished flashing that... and right out of the gate, the keyboard process stops working. So I can't even finish the initial setup.
... *expletive* seriously!? Why are there so many roms that don't *expletive* work?! Does anyone ever actually test any of these roms before shoving them on us?
I'm taking about aokp sokp is something different
You flashed the newest build of aokp from the 15th and the keyboard crashed wow
That's extremely weird are you wiping everything before you install I personally use go into mounts and SD and format my sdcard (which is the internal one, not sdcard 1)the making sure I get a good install
codezer0
Android Expert
Yea, see, the OTA updates don't even give you the option to try and deal with it later... it's either restart and install or press the home key to get it out of the w ay. but it won't clear from the notification drawer and it puts itself right in the way to force you to accept the update.
HiiiPowers
Android Enthusiast
I think your right about that I use to use the full module pa gapps and every time I installed a rom I had to update the Google play services before anything Google ran so that may be a issues I use now the small gapps package with barely nothing in it and download what I need
wyelkins
Android Expert
I haven't had to tackle the TW nag for 4.4, but I remember that the 4.3 nag was a bitch to get rid of. I think that Moar for 4.1.2 had a fix that finally killed it. Obviously, in ROM time that is ancient history, but it sounds like there is a fix for that problem now too.
As everyone says YMMV.
As everyone says YMMV.
HiiiPowers
Android Enthusiast
If the key board fcs why didn't you just let it boot back up once you pulled the battery? May have just been a one time thing
I think you really need to give aokp another try I recommend if you have a sdcard that you put in the back of the phone put the rom on that boot into recovery wipe data /factory reset then once that's complete if your using philz go to mounts and storage go to the option format sdcard and then install the rom
It would take me forever to address every bullet point you have but overall your having issues with everything so since you want stability run cm10.2 official release which is a 4.3 rom if you get any fcs with that it's not the rom somethings going wrong in the installation process
wyelkins
Android Expert
That is a very good point. All new Roms take a few minutes to settle. Running on slow data, it sometimes takes a while for Google Services to update. Even on a fast connection, sometimes Google waits until it is good and ready to start.
codezer0
Android Expert
... Could you please explain what the heck you mean by "fcs" ? I have no idea what you are talking about with that. And frankly hearing these weirdo acronyms is starting to make this situation worse and getting me stressed out.
I use the option to clean for installing a new rom from Philz, install the rom, then install gapps, and then the boost APN fix before starting a fresh boot. Far as I understood it, that's all I had to do.
Also, why would I format the sd card now? it has the sms backup, which is the only thing I can't actually restore if I end up having to wipe the phone again. I'm not sure I understand what it is you're trying to get me to do here, other than basically delete everything I have.
mydian
Android Expert
It's very easy to stop the OTA nag for 4.4. You just need to edit the build.prop file and replace the old MK3 build# with the new ND8 build# everywhere you see it. Some custom roms, like Moar and Wicked Sensations have zips to do it for you but it's really not that hard. You could have done that in a few minutes instead of playing with other roms.
jdsingle76
Android Enthusiast
... Could you please explain what the heck you mean by "fcs" ? I have no idea what you are talking about with that. And frankly hearing these weirdo acronyms is starting to make this situation worse and getting me stressed out.
I use the option to clean for installing a new rom from Philz, install the rom, then install gapps, and then the boost APN fix before starting a fresh boot. Far as I understood it, that's all I had to do.
Also, why would I format the sd card now? it has the sms backup, which is the only thing I can't actually restore if I end up having to wipe the phone again. I'm not sure I understand what it is you're trying to get me to do here, other than basically delete everything I have.
FC means force close, meaning it stops working and is normally accompanied with some sort of error message. We all get frustrated, but you must remember, the people on here are helping and building things for free, and the best mod you can put on your device is patience, because the more you flash, the more risk you run of having issues, which can normally be worked through by the folks on here and XDA, who do it...for free...
HiiiPowers
Android Enthusiast
... Could you please explain what the heck you mean by "fcs" ? I have no idea what you are talking about with that. And frankly hearing these weirdo acronyms is starting to make this situation worse and getting me stressed out.
I use the option to clean for installing a new rom from Philz, install the rom, then install gapps, and then the boost APN fix before starting a fresh boot. Far as I understood it, that's all I had to do.
Also, why would I format the sd card now? it has the sms backup, which is the only thing I can't actually restore if I end up having to wipe the phone again. I'm not sure I understand what it is you're trying to get me to do here, other than basically delete everything I have.
Formatting the internal sdcard cleans everything off it yeah "clean for install a new roms" wipes everything but tw places some folders on your sdcard(internal storage one) that can only be removed by formatting
Alright now as far as having your sms backup folder on your SD card you have it on your internal one because that's what I'm saying format? Not your external one which you can remove
If you have a external sdcard you can copy and paste the sms backup folder or move if you want to your external sdcard and you'll be fine
I'm trying to give you a clean phone with nothing on it so when you install the rom it might help with the fcs(force closes)
If you don't want to disregard the whole first section of this but its your choice I'm just trying to help
Overall
You really could just try to install the rom first then the boost apn zip to get data then let it boot don't install the gapps because I'm sure that's probably what's making it fcs once the rom boots let it sit for about 10 seconds reboot back into recovery then install the gapps and if you get fcs then it's the version of pa gapps your using
wetbiker7
Extreme Android User
UPDATE
Wicked-X has just released version 6.5.
_________________
As for the previous posts. I always try to use the newest version of Philz. As far as flashing AOSP based ROMS (any of them) , I do the factory reset (install new ROM) , wipe dalvik, wipe cache and then flash the ROM. I then flash the NEWEST version of PA 0-Day Mini-Modular GAPPS, and then flash the APN fix. In that order, all at once. I have never had any issue flashing ROMs this way. NEVER.
As for the member who who's complaining about the advice he was given, go and READ. If you take the freaking time, you can find your own answers! The information is out there. Don't criticize someone for trying to help you. That's just down right RUDE! The member took the time to answer your questions. Respect that dude.
Wicked-X has just released version 6.5.
_________________
As for the previous posts. I always try to use the newest version of Philz. As far as flashing AOSP based ROMS (any of them) , I do the factory reset (install new ROM) , wipe dalvik, wipe cache and then flash the ROM. I then flash the NEWEST version of PA 0-Day Mini-Modular GAPPS, and then flash the APN fix. In that order, all at once. I have never had any issue flashing ROMs this way. NEVER.
As for the member who who's complaining about the advice he was given, go and READ. If you take the freaking time, you can find your own answers! The information is out there. Don't criticize someone for trying to help you. That's just down right RUDE! The member took the time to answer your questions. Respect that dude.