As of 7/29/2013...Will update when there is progress on this issue.
This is a notice to EVERYONE who has CWM on their phone as of right now.
(Atleast the version in this thread)
Be EXTREMELY careful flashing ANY kernels in recovery at this moment unless they SPECIFICALLY say they are for the Virgin Mobile varient! It will 100% BRICK YOUR PHONE! AKA, no turning on, nothing. The only thing you will be able to get will be QHSUSB_DLOAD in your device manager when plugging your phone into your computer, and there has not been a workaround yet for this specific phone.
The issue seems to be how third party kernel zip's flash
In the install script, it goes through and tries to write the boot.img to /dev/block/mmcblk0p5, when it should actually be at dev/block/mmcblk0p7. Until a fix/workaround has been figured out, be VERY careful on what you flash on your phone!
This is a notice to EVERYONE who has CWM on their phone as of right now.
(Atleast the version in this thread)
Be EXTREMELY careful flashing ANY kernels in recovery at this moment unless they SPECIFICALLY say they are for the Virgin Mobile varient! It will 100% BRICK YOUR PHONE! AKA, no turning on, nothing. The only thing you will be able to get will be QHSUSB_DLOAD in your device manager when plugging your phone into your computer, and there has not been a workaround yet for this specific phone.
The issue seems to be how third party kernel zip's flash
In the install script, it goes through and tries to write the boot.img to /dev/block/mmcblk0p5, when it should actually be at dev/block/mmcblk0p7. Until a fix/workaround has been figured out, be VERY careful on what you flash on your phone!