• 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

GreyCelt

Well-Known Member
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.
 
How are you installing them . do you perform any wipe or update through the CyanogenMod update in the settings .
 
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.
 
BRAINZ2013 said:
But try with out that you maybe removing something it needs to boot up if problems continue post back
Click to expand...

Nahhhh just checked its true may want to wait a while cause they combined and the problems been going on since Feb 20 2014. Give ma a second I post the problems
 
BRAINZ2013 said:
But try with out that you maybe removing something it needs to boot up if problems continue post back
Click to expand...

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?
 
GreyCelt said:
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?
Click to expand...

Yes running a bionic and s3 with kk o my bad d2lte :eek::D:what:
 
struckn said:
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.
Click to expand...

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.
 
Micaallin said:
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.
Click to expand...

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.
 
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?
 
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.
 
mattstout404 said:
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.
Click to expand...

Or just wipe dalvik & cache? xP
 
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?
 
Tokens210 said:
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?
Click to expand...

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.
 
upconvert said:
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.
Click to expand...

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
 
Tokens210 said:
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
Click to expand...

It will cause a bootloop whenever you flash it.
 
You must log in or register to reply here.
Back
Top Bottom