Root [Virgin Mobile] Warning about flashing kernels

[xthedakmanx]

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!

 

[oner14]

Any idea why the kernel that came with this ROM didn't brick my phone

 

[xthedakmanx]

Any idea why the kernel that came with this ROM didn't brick my phone

Did you flash it separately from the actual rom?

 

[oner14]

Did you flash it separately from the actual rom?

No it came with the rom

 

[rbheromax]

Any idea why the kernel that came with this ROM didn't brick my phone

Because the developer used by-name to flash, thus correctly flashing the rom for your phone. It installed system to system and boot to boot. And since its the same hardware it boots

 

[craig71200]

I have flashed every Sprint Kernel with no issues except no 4g..... Is this a particular recovery issue?

 

[punkmaxx]

/dev/block/mmcblk0p5 = aboot (this is part of our boot loader partitons, if you try to write a kernel to mmcblk0p5 it will definitely brick your phone...)

Check Here for mount point and partition name reference.

 

[rbheromax]

Even with aboot gone you should still get to odin mode. You should worry about tz(mmcblk0p8) which is right before aboot in the boot sequence.

 

[lordmage]

is there a recovery that will work correctly or is it more a case of the script. could someone simply edit and flash it.

 

[xthedakmanx]

Even with aboot gone you should still get to odin mode. You should worry about tz(mmcblk0p8) which is right before aboot in the boot sequence.

You'd think so, but nope >_< TOTALLY locks up the phone.

What was happening was I was flashing for the wrong kind of GS3 (derp), but still, like you said, it STILL should of booted up....but I couldn't even get into download mode

 

[peter counias]

What kernel did you flash?

 

[peter counias]

Don't you still have a recovery system?

 

[xthedakmanx]

I stupidly flashed the Yoda Kernel for the Verizon GS3. It shouldn't of totally broke the phone, but for some reason I couldn't even get into Odin mode or recovery

 

[Shabbypenguin]

only results i can find are for the gtab 10.1, and the i9300, which is the international sgs3

 

[spacepanda]

solution : TWRP.

 

[rbheromax]

XD Twrp is what ppl are using to flash the kernels that are bricking them lol

 

[spacepanda]

XD Twrp is what ppl are using to flash the kernels that are bricking them lol

definitely said cwm...no mention of twrp. not the first problem people have had with cwm either...

 

[Shabbypenguin]

it wouldnt have mattered which recovery that was used