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

Root [Boost Mobile] Official CyanogenMod 11 Nightlies!

I just delete all the assert lines...
But can you fash any other rom? Say a tw rom like moar?

Yeah I have sucessfully done the following:

Flashed MK5 jdsingle rom (TW)

Flashed VanirAOSP nightly (AOSP) [ROM][4.4.2]VanirAOSP & Commotio[OFFICIAL] - xda-developers

Flashed to get MG2 bootloader http://androidforums.com/boost-mobile-galaxy-s3-all-things-root/758586-odin-backup-sph-l710_mg2.html

as well as modems and such, without any issues I can boot right into the roms just fine.

With Cm11 latest nightly and beanstalk 4.4, I flash the rom only just fine, without gapps or anything else, JUTS the rom, fresh/clean install, reboot and see the samsung logo flash real fast and then it goes to a black screen, and just sits there......I've let it set for 15 mins, up to around 2 hrs even, and nothign ever happens. Battery doesn't get hot, just nothing ever happens.

I can reboot to recovery just fine.

I have also use CM touch, Cm regular, and Philz recovery, and all three have the same effect of the black screen.

Removing assert lines or assert lines in makes no change either.


I've been talking closely with struckn, and he's out of ideas as ell......so now it's like a twilight zone episode.
 
Maybe try flashing the boot.img found in the roms zip via adb after flashing from recovery. ..
Maybe after that flash the system folder via adb

Just a thought. It sounds like it is one of those that might be the problem.

*** check md5 sum *** maybe your download is getting corrupt!???
 
Maybe try flashing the boot.img found in the roms zip via adb after flashing from recovery. ..
Maybe after that flash the system folder via adb

Just a thought. It sounds like it is one of those that might be the problem.

*** check md5 sum *** maybe your download is getting corrupt!???

Good call, maybe there is some kind of kernel issue going on. Possibly try flashing the 12/26 build of the dkp kernel for AOSP 4.4 in the same session as the ROM flash before booting back into system as well.
 
Maybe try flashing the boot.img found in the roms zip via adb after flashing from recovery. ..
Maybe after that flash the system folder via adb

Just a thought. It sounds like it is one of those that might be the problem.

*** check md5 sum *** maybe your download is getting corrupt!???

That's kinda what I thought at first to, and was under suspicion, but after thinking about it.....the install goes fine without any issues, it's the booting to the os that's the issue, it flashes and installs fine, no errors, no stalls no hangups, after a reboot, into the system, that's where it stalls or hangs or whatever it's doing...I can't tell because it's a black screen so even if it is bootlooping or something I couldn't tell anyways.

So I doubt it's a bad download or anything, just a fluke thing happening.

If it was an MD5 or a bad download or corrupted d/l it probably wouldn't install and say it installed ok.
Probably something that's getting overlooked, kinda like the asset lines...I just installed a cm10.1 rom and got a status 7 error. Thought perhaps it was due to the assert lines, and removed them, and sure enough it installed fine without any status 7 error.
 
Definitely not the assert lines... All it does is check the baseband. I just delete the whole section. ..

You would not be able to tell if the bootloop was due to kernel or system. ..

Bad download is possible and still be able to do a full flash... just one character mess up in the right location can cause a bootloop. .. think of just changing one character badly in your build.prop could put your phone in a bootloop. .. There are many other places just one bit off would stop your phone.
 
True, but this is happening with multiple roms though, not just a few, so far I have cm10.1, cm10.2.0, cm11, and beanstalk that all have the issue.

Cm11, I have downloaded at least 3 times thinking it was perhaps a bad d/l, cm10.1 I only downloaded once, and cm10.2.0 I have downloaded twice.

My carrier is gonna freek out when they see the d/l amount.

I'm not exactly sure but I bet I've hit like 6GB so far in an 8 hour span with all the downloads I've done. Probalby way more, but still a ton more than I normally do.

I'm kinda leaning towards another issue as apposed to the bad download, but not ruling out the d/l part although if 4 times of a download doesn't get it downloaded in full, I may as well write it off then because it's more than likely not ever gonna download good that being the case.
 
To eliminate thoughts and possibilities. ..

Does your phone work right now?

Can you restore your saved backups in recovery?

Can you get any other aosp roms to run?

Any other touchwiz roms that is highly modded work? Not stock based.

When did you buy your phone?... they have made a couple different s3's and the new ones have extra prevention to stop us from rooting and hacking the phone... maybe there is yet another new phone that's just getting released.
 
Boy howdy, that'd be awesomeness........I'm all for videos.

I thought I had remembered how and I did delete the assert lines in the cm11 file, then saved it but it still isn't working, I still have the dreaded black screen right after the Samsung logo.
Probably missing something along the line somewhere.

Update:
@wetbiker7 thanks for the video, it reassured me that I was doing the correct procedure for removing asserts.

So now that I have confirmed I am doign that, I'm just completely out of ideas why in the world cm11 will not install right, or why am I getting just a black screen :(.

No problem and glad it helped. You timed it just right too because I just remade that video. I pulled the original video a few weeks ago and just got it reposted.

As for the issue with the ROM not flashing, I'm doing some serious head scratching right now. I would definitely start with downloading and reflashing your recovery. I would then start with a stock rooted version and get it flashed. I would make sure all of this is new too because there is a possibility that one of the original installs was corrupt and that's what's causing your trouble now.

When I have problems like you're describing with a phone, I start from scratch and reinstall EVERYTHING. I mean EVERYTHING. I've found that this is the best way to troubleshoot a pesky problem like you're having.

Good luck and I hope you get it fixed up.
 
So I'm really New to this phone and CM. I tried installing both of the Kernels and My phone just bootlooped. Also I am having trouble with my 4G (It's not showing up). Please help! I'm having difficulties following your guys guides. Thanks!!

Edit: I'm on 20140102
 
So I'm really New to this phone and CM. I tried installing both of the Kernels and My phone just bootlooped. Also I am having trouble with my 4G (It's not showing up). Please help! I'm having difficulties following your guys guides. Thanks!!

Clarify please on the kernel issue. All ROM's contain their own kernel, flashing a custom kernel (if that is what you are trying) is not necessary, it is just personal preference. More specifics in a "Help" post are a good idea in general, just FYI. You should be able to just restore a backup to eliminate the bootloops and then start over.
 
To eliminate thoughts and possibilities. ..

Does your phone work right now?

Can you restore your saved backups in recovery?

Can you get any other aosp roms to run?

Any other touchwiz roms that is highly modded work? Not stock based.

When did you buy your phone?... they have made a couple different s3's and the new ones have extra prevention to stop us from rooting and hacking the phone... maybe there is yet another new phone that's just getting released.

I recently bought this phone at best buy, and I think you are correct, I heard that they have some newer s3's that dn't like the roms like your saying.

I can save backups
The phone works fine, as I have had touchwiz roms installed and a couple of aosp roms on, although they seem to give issues.


This is my compiled list so far of roms that I have tried:

Roms with a black screen after samsung logo:

-CM11 nightly latest build - blank screen after
samsung logo
-Beanstalk 4.4 nightly build - black screen after
samsung logo
-Cm10.2.0 - bails out on install
-CM10.1 - bails out on install
-Carbon Rom 4.4.2 - black screen after samsung logo

Roms that have worked fine:

jdsingle MK5 Tw rom
-ODIN Backup for --> BOOST MOBILE SPH-L710_MG2 (tw)
- no isues at all
-stock rooted MD7 rom (tw) - no issues at all
-stock rooted MG2 rom (tw) - no issues at all
-VanirAOSP nightly - had a few issues and glitches
-Fox - Installed fine but had no wifi or 3g/data
-Bam Android - no data/3g
-Carbon rom 4.3.1 but has a few glitches

Conclusion, every touchwiz rom I have tried just works without issues.

Most if not all that I can recall of the aosp roms have the APN issue, so I don't have data on those.....and a few other quirks, but I can worry about those later, need an APN fix first.

Since I have never had to do an APN fix before I am nt sure what steps to take to do it.....so does anyone know a way on aosp roms to fix the apn?


In the mean time I am going to try one last ditch effort at this as a work around, in hopes they didn't bypass the MG2 update and go directly to MK5......I am going to flash back stock un-rooted, except the firmware updated, and as I said hope it will do incremental updates and not go directly to mk5.
If it does indeed go directly to MK5, then I will be holding off and put on pause, JUST to make sure there are no hardware issues before I void warranty......I figure a good month will do the trick, although I realize there are n guarantees it won't happen down the road, but still, better to be safer than sorry.
 
Clarify please on the kernel issue. All ROM's contain their own kernel, flashing a custom kernel (if that is what you are trying) is not necessary, it is just personal preference. More specifics in a "Help" post are a good idea in general, just FYI. You should be able to just restore a backup to eliminate the bootloops and then start over.

It would just sit there loading. I decided I didn't need a different kernel so that's no problem. But mainly I want 4g back how can I so this?
 
......I am going to flash back stock un-rooted, except the firmware updated, and as I said hope it will do incremental updates and not go directly to mk5.

Do not take the ota update, it will go directly to mk5. ..

As for apn fix, find and install piggyback zip
 
So i have installed the Snapshot. The Ptimized dalvik library, the 12-14GApps Core, and CM-AOSP D2BST APN FIX.ZIP. And I still have no Mobile Data. Everything else works though. Please help. as for the PRL that involves ##3282# I can't get that to work.
 
So i have installed the Snapshot. The Ptimized dalvik library, the 12-14GApps Core, and CM-AOSP D2BST APN FIX.ZIP. And I still have no Mobile Data. Everything else works though. Please help. as for the PRL that involves ##3282# I can't get that to work.

Go into your data settings and take it off LTE and set it to CDMA, reboot and you should have data.
 
If the boost APN fix is not working for you, idk if you can get 4g on the ROM you are running.

Try wiping dalvik and reflashing the fix...
 
Here is a link to Alpineman's tutorial on how to switch back to the Boost APN after flashing a AOSP Sprint ROM. Look at the 2nd post and choose Boost.


Alpineman's tut-
FIXED: Can't send MMS? Sprint / Boost / Virgin Mobile APN Settings Problem! - xda-developers

So I'm trying to do this. I moved it to system/apps and it still won't work and titanium just sits on processing for hours with no result when I command it to convert it.

On a side note in regards top titanium. How do I enable USB debugging?
 
I am on cm11 as well now, and I tried both listed on that same web site linked, and cannot get them to work.....is there another way to get to change the apn settings with cm11?
 
Back
Top Bottom