As quick as these are being dropped we aren't far from ota.
I'll give it by the middle of June.


Sent from my SPH-D710 using Tapatalk 2

NICE!
These builds have quickly become my go to! Thanks so much for your work on this! Can't wait for the plus repack!

Originally Posted by humdrum2009

As quick as these are being dropped we aren't far from ota.
I'll give it by the middle of June.


Sent from my SPH-D710 using Tapatalk 2

As someone already said its not much of a sign. We have been getting them this quick for most of the leaks. Many many times they have been 2 days a part we even had 4 in a row?

Am I correct in understanding that at this time there is no way to get CWM Recovery onto any of these ICS builds?

Originally Posted by steindog99

Am I correct in understanding that at this time there is no way to get CWM Recovery onto any of these ICS builds?

There is an FD02 kernel with the Rogue version of CWM. Factory Reset can insta brick the phone permanently. Flashing roms was considered dangerous not sure if it was narrowed down yet. I have not kept up.

Best thing to do is mobile odin the el26 cwm kernel when you need to do things. The stock CWM, even stock recovery will have the issue since its a Samsung kernel issue.

Originally Posted by RainMotorsports

There is an FD02 kernel with the Rogue version of CWM. Factory Reset can insta brick the phone permanently. Flashing roms was considered dangerous not sure if it was narrowed down yet. I have not kept up.

Best thing to do is mobile odin the el26 cwm kernel when you need to do things. The stock CWM, even stock recovery will have the issue since its a Samsung kernel issue.

We've actually duplicated the problem with the stock Samsung ICS kernel repacked with just the unlocked recovery.

Our best guess as to the cause of the issue is a change in the ICS kernel, regarding how it handles wipes, is triggering a latent EMMC firmware bug which then renders blocks of EMMC unwritable.

We think the reason GB kernels don't exhibit the issue is they handle wipes differently and thus don't trigger the latent EMMC firmware bug.

The EMMC firmware is basically the internal controller for the EMMC and not something that can be updated with a flash.

There may be some versions of the EMMC more susceptible to this problem and the bug could lie in sections of the EMMC firmware designed to make sure flashes don't keep flashing the same blocks to reduce "wear".

This could explain the behavior where you do the same operation 4 times with no issue, then on the 5th it bricks.

Originally Posted by sfhub

There may be some versions of the EMMC more susceptible to this problem and the bug could lie in sections of the EMMC firmware designed to make sure flashes don't keep flashing the same blocks to reduce "wear".

I am familiar with wear leveling as well as the basics on the interface controller. I would actually be curious to see if there is anything in the area of storage the controller has access to internally that is not presented outside of vendor specific queries and commands. I assume they are able to see and write that area with jtag so there is probably nothing there. But would be interesting to see a dump before and after brick on the same phone. That is unless the combined package prevents direct access to the flash itself, unlike what I am used to.

I haven't bothered keeping up because I know you guys are on it and there is nothing I can do. I don't even have the time in the day. Keep it up guys, much better than anything I can do.

Originally Posted by robbyr

Can't wait for the plus repack!

repack done uploading now.

I have been flashing the NODATA versions of these leaks and all data settings seem preserved except for Juice Defender which I need to re-configure each time...is that normal?

thanks sfhub . cant wait to get home

Sent from space shuttle gs-2