I modified the first Skyrocket TWRP for the t989, i mean all it really needed was a ram disk edit for the props to identify as a hercules instead of a skyrocket.

Now, i used the old skyrocket recovery, and it has not caused any bricks i have been doing what ever in it. I've used every format option, ive clicked on reboot into recovery which users initially reported were bricking the device. I pretty must tried to abuse my phone, and all is well.

I have a feeling that it was the roms people were flashing causing bricks and i'd hate to see the dev waste his time. i mean with these leaks, hell a t989 user bricked just rebooting from the leaked rom, that i made and flashed about 20 (other users are flashing it and still on it fine as well) times for logging and testing. I have no idea what happened with that user, but user error is always a factor to consider, given the circumstances that my self and many others are fine.

What we have to consider here is if the recovery were to be bricking, it would be because it was formatting the partition table or important bits on the emmc like the sbl's and what not. this would not be a selective proses, it would either brick every one or no one.

I was also informed by a Samsung coder that the leaked skyrocket kernel had a huge bug that could be triggered by certain user actions that could potentially cause bricks. it has been fixed and that's why there was a second leak. it was a fixed kernel.

anyways, wanted to say thanks for the recovery its great, i'm one of the CM9 devs for the skyrocket and hercules. and if you'd like to support the t989 (hercules) officially i am sure that would make a lot of people happy. people have been flashing my "modded" skyrocket version of twrp with no issues. And like i said we have been using the "device bricking" version.

Jeff

Thanks for posting that. I, too, had a feeling it was those bad kernels that was causing the bricks, since they were rather random.

I thought the bad kernels were only exynos variants?

Sent from my SAMSUNG-SGH-I727 using xda premium

I want to use this bad boy so bad lol half tempted

Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Originally Posted by nrm5110

I want to use this bad boy so bad lol half tempted

Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

I stress tested this extensively over the weekend with different roms, different wiping, different flashing methods and I had no problems at all. It's a safe bet that the bricks were due to the bad kernel from one of the leaks.

Originally Posted by orlandoxpolice

I thought the bad kernels were only exynos variants?

Sent from my SAMSUNG-SGH-I727 using xda premium

The bad kernels affected the Note, too, which is Qualcomm based; so it's not just Exynos.

Originally Posted by SolsticeZero

I stress tested this extensively over the weekend with different roms, different wiping, different flashing methods and I had no problems at all. It's a safe bet that the bricks were due to the bad kernel from one of the leaks.




The bad kernels affected the Note, too, which is Qualcomm based; so it's not just Exynos.

It was any device with capacitive buttons that were effected

been using this recovery on my t989 since Mr.X edited the ram disk.. it is working really good and i have no issues. Thanks TeamWin and Mr.X

So it should in NO WAY brick (as in even reboot recovery) the T-Mobile UVLC8 Leak? Since it doesn't have the kernel bug. does it?

I've flashed this recovery twice with zero problems yet I believe I read within the AOKP thread that twrp is (was?) not compatible. Anyone using twrp with AOKP?

Sent from my SAMSUNG-SGH-I727 using xda premium

Originally Posted by bacheezy

I've flashed this recovery twice with zero problems yet I believe I read within the AOKP thread that twrp is (was?) not compatible. Anyone using twrp with AOKP?

Sent from my SAMSUNG-SGH-I727 using xda premium

I flashed aokp using twrp didnt have any issues other than the ones posted.

PS i used both non-touch and touch cwm to flash ics roms but they were all buggy but when i flashed using twrp the recovery solved all the issues.