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

Root [Virgin Mobile] Bootloops CM11 d2lte

GreyCelt

Well-Known Member
Nov 11, 2011
211
46
Portland, OR
Is anyone getting bootloops after flashing the two latest nightlies from CM11 (20140221 & 20140222)?

I've done nothing different from previous flashes and the first boot immediately after flashing results in bootloops. It never does boot-up fully and I have to do a battery pull and go back into recovery to restore my Nandroid Backup of the 20140220 build.

Prior to the 20140221 build I never had problems even with the couple of new d2lte unified builds that were put out.
 
I download through Settings-->About Phone-->CyanogenMod Updates

Then I unzip the file, remove asserts and debloat to my liking. I then re-zip and move the file to my Flash file where I keep all of my current zips that I flash when updating.

Reboot to Philz recovery. Wipe cache and dalvik cache (I know some say it's unnecessary but I've always done it).

Flash ROM, then GAPPS, then kernel, then dalvik optimization. Wipe cache and dalvik cache.

Reboot.... Bootloop!

I've been doing this same routine since I started flashing CM11 2-3 months ago or whenever it was. No changes. No problems...until the last 2 nightlies.
 
Upvote 0
But try with out that you maybe removing something it needs to boot up if problems continue post back

Yeah, my next step is to troubleshoot. I'm gonna flash each zip separately and try to reboot after each flash. I'll also forgo the wiping to see if that changes anything.

BRAINZ2013, Are you on CM11 d2lte nightlies?
 
Upvote 0
I think it is a d2lte issue in general, Carbon has had similar issues after 2/18. Build from 2/21 for Carbon bootlooped on me in similar fashion.

I am on Carbon d2lte, and not CM 11, but I had similar bootloop issues with Carbon d2lte 2/21 and 2/22. After fiddling around with different flash scenarios to see if something would work, I discovered that I avoided bootloops if I didn't flash the optimized Dalvik zip.

Flash as you normally do, but skip the optimized Dalvik zip and see if that works.
 
Upvote 0
I am on Carbon d2lte, and not CM 11, but I had similar bootloop issues with Carbon d2lte 2/21 and 2/22. After fiddling around with different flash scenarios to see if something would work, I discovered that I avoided bootloops if I didn't flash the optimized Dalvik zip.

Flash as you normally do, but skip the optimized Dalvik zip and see if that works.

Thanks for the heads up! From what I have been reading as well, looks like ART is causing a lot of issues on the newer builds too.
 
Upvote 0
Well, I thought I was gonna have some news because I haven't checked this thread since my last post. (I was busy curling... Yes, I said curling!) It looks like others have discovered what I just figured out on my own.

Anyway, when I got home I flashed the 20140222 ROM & rebooted...no problems. Flashed dkp kernel & rebooted...no problems. Flashed dalvik optimization...BOOTLOOPS!

Restored Nandroid Backup.
Flashed ROM/kernel & rebooted...no problems.

I wonder what they changed? Does this mean that they're getting closer to making ART the default runtime?
 
Upvote 0
I had an issue where whenever I tried to simply upgrade straight from a dalvik optimized instance of CM11.
If you have a dalvik optimized backup that you want to continue upgrading (without doing a full wipe) you should do this, worked for me:

1. make a new backup with CWM
2. do a full wipe
3. install the new d2lte cm zip and whatever kernel
4. boot and skip the setup (we're wiping it anyway)
5. boot to recovery
6. advanced restore JUST the data
7. reboot
8. profit

Not sure if it helps or not but I figured I'd throw it out there.
 
Upvote 0
I had an issue where whenever I tried to simply upgrade straight from a dalvik optimized instance of CM11.
If you have a dalvik optimized backup that you want to continue upgrading (without doing a full wipe) you should do this, worked for me:

1. make a new backup with CWM
2. do a full wipe
3. install the new d2lte cm zip and whatever kernel
4. boot and skip the setup (we're wiping it anyway)
5. boot to recovery
6. advanced restore JUST the data
7. reboot
8. profit

Not sure if it helps or not but I figured I'd throw it out there.

Or just wipe dalvik & cache? xP
 
Upvote 0
Just so I'm clear here lol

I'm running the like feb 28th cm11 or something, thinking about upgrading to the newest version this weekend

I usually always do a full wipe/clean install

I am using the dalvik optimization


So my question is, is this bootloop issue ppl are encountering only when dirty flash/ or upgrading??

So if I do my typical full wipe/ clean install should I run into any issues?


Also I see a few saying the optimization is what's causing the issue so is it stopping the ROM install causing the bootloops?

Or is it after our running the ROM trying to install it causes bootloops?
 
Upvote 0
Just so I'm clear here lol

I'm running the like feb 28th cm11 or something, thinking about upgrading to the newest version this weekend

I usually always do a full wipe/clean install

I am using the dalvik optimization


So my question is, is this bootloop issue ppl are encountering only when dirty flash/ or upgrading??

So if I do my typical full wipe/ clean install should I run into any issues?


Also I see a few saying the optimization is what's causing the issue so is it stopping the ROM install causing the bootloops?

Or is it after our running the ROM trying to install it causes bootloops?

You will be fine as long as you don't flash the dalvik optimization.zip. When you flash it, the ROM will no longer boot. Your full wipe will take care of that fine.
 
  • Like
Reactions: Tokens210
Upvote 0
You will be fine as long as you don't flash the dalvik optimization.zip. When you flash it, the ROM will no longer boot. Your full wipe will take care of that fine.

Thanks, just didn't wanna fly in blind

Secondary, does the optimization work later, like if I fully set the ROM up then flash it ?

I'm cool if the optimiztion doesn't work anymore, just gotten used to it in my typical flash process.


Thx again
 
Upvote 0
Just a quick update - the Optimized Dalvik flash has been updated to work with CM11.

[4.4/4.4.x][PATCH] Qualcomm-optimized Dalvik & Bionic libraries - xda-developers

From the XDA thread:


"If you're running CM11 released after 1 March 2014 or any other ROM that includes fixes to DVM, please flash 4.4_qc-optimized_dalvik-cm11.zip. This is the only file you need, don't flash anything else from this thread!"


 
  • Like
Reactions: upconvert
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones