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

Root [Virgin Mobile] [ROM][4.4.2]CyanogenMod 11 w/DKP

If your using the actual cwm and not philz recovery you may wanna switch

As for the md5, its also called the checksum, usually a long string of numbers

Where you downloaded the file most likely has it posted then u can usually choose check/verify checksum in WinZip or something similar

Just don't unpack the zip, never unpack a Roms zip file cause its not really a zip, a ROM is put threw a compiler which happens to spit out a zip, once unpacked unless you compile it as well it'll never zip up correctly "not saying you've done this just a tip I'm tossing out there"
 
If you dont wanna switch its fine, its ur decision

But I will say you'll probly be limited on what you can flash, so far you'll be the 2nd or 3rd person I've seen who is having issues flashing a ROM that most have had no issues with while using cwm compared to philz, which is cwm, just adjusted to be better lol
 
theres no difference between this and the d2vmu one right(question mark, because that one booted nicely in one shot no probs and the rom is nice the only thing different should be the kernel, which I can flash if I want from xda right
 
mudflap2020 said:
theres no difference between this and the d2vmu one right(question mark, because that one booted nicely in one shot no probs and the rom is nice the only thing different should be the kernel, which I can flash if I want from xda right
Click to expand...

Yes I believe that currently the only difference between this one and the cm11 thread by elb is this one has the dkp kernel built in

Both I believe have mopedryders fixs pre added

And yes you can flash the kernel separate, just be sure its the one for this device
 
Speaking of dkp kernel, new test build is out. CM has unified their kernel, which means that there are no more carrier differences. Therefore, decimalman has created a new folder called just "d2" for his new build, which is flashable for Sprint (and by default VM/Boost), TMobile, Verizon, and AT&T.

Just a thought for @ajnycguy, I don't know how hard it is to incorporate Aroma installer, but it would be very cool to be able to do so and then give the user the option while flashing a ROM to go with stock, dkp, BMS, or LeanKernel. Just throwing that out there.
 
struckn said:
Speaking of dkp kernel, new test build is out. CM has unified their kernel, which means that there are no more carrier differences. Therefore, decimalman has created a new folder called just "d2" for his new build, which is flashable for Sprint (and by default VM/Boost), TMobile, Verizon, and AT&T.

Just a thought for @ajnycguy, I don't know how hard it is to incorporate Aroma installer, but it would be very cool to be able to do so and then give the user the option while flashing a ROM to go with stock, dkp, BMS, or LeanKernel. Just throwing that out there.
Click to expand...

New dkp kernel is running beautifully.
 
Currently waiting on Android File Host to upload v03!

v03 comes with a newer! CM11 nightly & DKP's new! kernel!
I will be uploading to AFH for now on, for me at least the downloads seem faster (Feel free to tell me if you would like me to post on DevHost as well as AFH). Faster = Better. I'll post here as an "update" to let you know when it's finished. Hope you guys enjoy!

:party:


Update:
AFH seems to be having problems with uploads, I'll have to try tomorrow then :(. Sorry guys.
 
struckn said:
Speaking of dkp kernel, new test build is out. CM has unified their kernel, which means that there are no more carrier differences. Therefore, decimalman has created a new folder called just "d2" for his new build, which is flashable for Sprint (and by default VM/Boost), TMobile, Verizon, and AT&T.

Just a thought for @ajnycguy, I don't know how hard it is to incorporate Aroma installer, but it would be very cool to be able to do so and then give the user the option while flashing a ROM to go with stock, dkp, BMS, or LeanKernel. Just throwing that out there.
Click to expand...

I'm going to eventually try and do this, the only thing is that I don't know how hard it is either, haha. I'm trying to learn how it works and how to set it up maybe, I could ask the created of MOAR. I believe it's @rompnit. Maybe he could guide me along the way, that would be cool ;).
 
ajnycguy said:
I'm going to eventually try and do this, the only thing is that, I don't know how hard it is either haha. I'm trying to learn how it works and how to set it up maybe, I could ask the created of MOAR. I believe it's @rompnit. Maybe he could guide me along the way, that would be cool ;).
Click to expand...

Yeah forgot to suggest who to get in touch with, since MOAR does have that option. Just FYI, thread for dkp kernel had a lot of users reporting issues with the new unified kernel build. Nothing too major except for a couple of people with WiFi issues that I am not entirely sure can be attributed to the kernel.
 
struckn said:
Yeah forgot to suggest who to get in touch with, since MOAR does have that option. Just FYI, thread for dkp kernel had a lot of users reporting issues with the new unified kernel build. Nothing too major except for a couple of people with WiFi issues that I am not entirely sure can be attributed to the kernel.
Click to expand...

I had this Wifi issue as well. If i remember correctly you said it runs with the newer versions of CM that don't care about the carrier when flashing a kernel. I was on the Snapshot Build when this happened. When I updated CM11 and flashed the new build it worked fine. So far i can say that I have had 0 issues. Maybe it has something to do with that?
 
ajnycguy said:
I had this Wifi issue as well. If i remember correctly you said it runs with the newer versions of CM that don't care about the carrier when flashing a kernel. I was on the Snapshot Build when this happened. When I updated CM11 and flashed the new build it worked fine. So far i can say that I have had 0 issues. Maybe it has something to do with that?
Click to expand...

Quite likely, in my opinion. If there really is an issue, decimalman is very responsive and fixes things ASAP. Would assume that CM has done a bunch of commits since the Snapshot that work with the unified kernel source, but that's just an educated guess. Also, I hear that a lot of Bluetooth issues were fixed on 1/21 nightly but borked again on 1/22, for what it's worth.
 
struckn said:
Quite likely, in my opinion. If there really is an issue, decimalman is very responsive and fixes things ASAP. Would assume that CM has done a bunch of commits since the Snapshot that work with the unified kernel source, but that's just an educated guess. Also, I hear that a lot of Bluetooth issues were fixed on 1/21 nightly but borked again on 1/22, for what it's worth.
Click to expand...

Good to know about those fixes... Since I have to wait to upload anyway, I can try to see if I can do the 1/21 build tomorrow as well. Thanks :thumbup:
 
ajnycguy said:
Good to know about those fixes... Since I have to wait to upload anyway, I can try to see if I can do the 1/21 build tomorrow as well. Thanks :thumbup:
Click to expand...

Cool! One final thing, looks like, from the CM changelogs, that they might be looking to implement double tap to wake into their own kernel, this is from a couple of nights ago. Would be a cool feature for sure, Elemental X, which I use on my Motorola Xoom, has it and I like it. Funny how LG makes it sound like they invented it, when really they are just the first OEM to really implement it without the need for root.
 
You must log in or register to reply here.
Back
Top Bottom