-
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
cwhatever
Life Goes On
I just noticed on Moar, I started with stock kernel, then switched to the other dkp kernel and noticed it used 2 gig more of the internal storage. I was like oh well and couldn't see why I had 2 gig more used. I switched back to the stock and now have gained that 2 back again. That explains that, seems like alot for a kernel. But didn't know if anyone else noticed that too.
wyelkins
Android Expert
Does seem like a lot. Not sure about that. You are used to worrying about storage from the Prevail. That is a good thing. I guess when you get an S3 you get a little lazy about that.
I have never had a storage problem on the S3. But I don't understand why a kernel would use that much space.
cwhatever
Life Goes On
I know, and yes look from time to time and no problem at all! I tried it again for the heck of it and sure enough it is 2 gig and switched back and then 2 gig back! Strange
I seem to be having some issue with call quality on moar. It's hard to understand them at times. It's not the modem because it works fine in stock tw roms. It's more a kind garbled or muffled in a way, it's hard to explain really.
I've seen some mention the call quality but never saw anything really in depth.
I'd really hate to stop using it, but it's almost to the point of not being usable at this point.
I don't get a lot of calls normally but today I did and it was noticeably bad and I had to keep saying stuff like "huh?" And "repeat that" quite a bit.
So is there a way to clear the call quality up at all?
Forgot to mention, this also does not happen in aosp roms either
I've seen some mention the call quality but never saw anything really in depth.
I'd really hate to stop using it, but it's almost to the point of not being usable at this point.
I don't get a lot of calls normally but today I did and it was noticeably bad and I had to keep saying stuff like "huh?" And "repeat that" quite a bit.
So is there a way to clear the call quality up at all?
Forgot to mention, this also does not happen in aosp roms either
kevindroid
Android Expert
you are right there is an issue with moar sound. ive noticed it since 4.3. ihave very little problem with it until i turn the sound up past 2/3 of the way. thats been my little work around. i really like moar but carbon and cm11 are starting to look good. ill find something i like and run with it. i try out roms on the tablet to get an opinion
wetbiker7
Extreme Android User
Guys. Get rid of MOAR if you're having issues. There are too many ROMs out there that run great.
If you want TouchWiz then go with Wicked Sensations.
If you want AOSP then go with CM11 or Carbon.
I suggest any of the above because I've ran them. The only issue I had was with Carbon and it looks like Struckn has a camera fix in the Carbon thread.
If you want TouchWiz then go with Wicked Sensations.
If you want AOSP then go with CM11 or Carbon.
I suggest any of the above because I've ran them. The only issue I had was with Carbon and it looks like Struckn has a camera fix in the Carbon thread.
kevindroid
Android Expert
yes ive been watching cm 11 and carbon i have them and ws on a thumb drive
Guys. Get rid of MOAR if you're having issues. There are too many ROMs out there that run great.
If you want TouchWiz then go with Wicked Sensations.
If you want AOSP then go with CM11 or Carbon.
I suggest any of the above because I've ran them. The only issue I had was with Carbon and it looks like Struckn has a camera fix in the Carbon thread.
Only reason right now I'm going with tw is a game I'm currently into, subway surfer.
So quick question about wicked, the color scheme, can that be changed?
I in no way am saying it's a bad rom, just not a huge fan of the color schemes they currently have out for these tw roms, as well as the fancy different icons they use ie: toggle icons.....I prefer the stock look.
mydian
Android Expert
I had the same problem with both Moar 7 and Jdsingles 4.3 update. Call quality is so bad it's unusable. I haven't tried any other 4.3 TW roms and don't plan to. I went with Moar 6 for now and call quality is just fine. As soon as I can have LTE and MMS at the same time with 100% stability I'll try an AOSP rom out.
scootmcdoot
Well-Known Member
I didn't care much for the all blue with wicked, so I went with the Eredicate theme. Much better in my opinion. Also, gurple is being worked on, so that might be another option in the future.
Up in Smoke and the USA theme are also available for Wicked now, to add a couple of other options. Check the Apps and Themes thread on XDA for the Sprint SGS3.
wetbiker7
Extreme Android User
Yes. There are 3 or 4 themes right now and more being worked on.
Wicked also has Xposed Framework installed with the Wanam app. A lot of stuff can be done to it to theme it up. 
Hopefully Gurple will be done soon.
Yes. There are 3 or 4 themes right now and more being worked on.
Hopefully Gurple will be done soon.
Left ya a PM
kevindroid
Android Expert
snow storm hit here pretty good. i flashed the wicked sensations rom and must admit its a very good rom. hey biker can it see me lol. so far im loving it. its quite snappy without any overclocking. all that i tested worked. i new it would from your reports. i can only add that otg works fine. i believe this will be a daily driver.
wetbiker7
Extreme Android User
I'm really glad that you like it Kevin. Now you know why I stuck with that ROM all this time. LOL Not only is it a great ROM, the thread for it is amazing and has an awesome group of people in it. Members are always making mods for it and sharing them. :thumbup:
Gotcha and replied.
wyelkins
Android Expert
All I can say is Wow! This could be a huge update for us, guys!
Philz just updated his recovery for the d2spr to fix most of the status 7 problems that we have.
If this works, we won't have to remove the asserts anymore. We can flash the zip right after download.
He just posted this and I can't get the download to work yet. Let me know if anyone does.
http://forum.xda-developers.com/showthread.php?t=2446393
Edit
Got it installed. Did not work for me. Still get the status 7.
But, at least Phil is working on it. Maybe someone else will have better luck.
It had been a while since I updated my recovery. Looks like Phil has added some things...
Philz just updated his recovery for the d2spr to fix most of the status 7 problems that we have.
If this works, we won't have to remove the asserts anymore. We can flash the zip right after download.
He just posted this and I can't get the download to work yet. Let me know if anyone does.
http://forum.xda-developers.com/showthread.php?t=2446393
Edit
Got it installed. Did not work for me. Still get the status 7.
But, at least Phil is working on it. Maybe someone else will have better luck.
It had been a while since I updated my recovery. Looks like Phil has added some things...
The assert override Phil included only bypasses the bootloader asserts, it doesn't bypass the device check, which is the first line in the current updater-script.
wyelkins
Android Expert
Ahhhh! What would devs have to do in their asserts to fix this for Boost and Virgin Mobile?
If you look at the first line in the updater-script it looks for "d2spr" so it would need "d2vmu" to be allowable for VM, I don't know what designation Boost uses.
wyelkins
Android Expert
Why can't we modify something like build.prop to make our phone have d2spr?
Edit
I suppose build.prop isn't loaded during recovery, But...
Maybe Phil could somehow spoof the script processing so that it somehow knows that Boost and VM S3 are equivalent to d2spr.
He could have a checkbox on his, d2spr recovery to signify that this device is Boost or VM.
mydian
Android Expert
Boost is d2vmu also. I just checked with Quadrant and then double checked in the stock build.prop.
wetbiker7
Extreme Android User
All they would have to do to get it to flash on our Boost phone is to add our Baseband. That's what I was originally doing before I started removing all the asserts altogether. I've added my Boost Baseband to several of the AOSP updater-scripts and flashed the ROM.
wyelkins
Android Expert
All they would have to do to get it to flash on our Boost phone is to add our Baseband. That's what I was originally doing before I started removing all the asserts altogether. I've added my Boost Baseband to several of the AOSP updater-scripts and flashed the ROM.
Maybe I am wrong, but I feel like we deserve a little love. Add our baseband to the script.
I think that it was not SlimKat that I noticed did not have that assert. I was in able to download to the phone and flash it. Just like God intended.