Originally Posted by l0rd_almighty

Well sorry If i misunderstood you mr smarty pants. Weird that it will load a gb kernel, flash and then load lpy afterwards. I mean why would it have to do that? What's the logic? Enlighten me techwhiz

Sent from my GT-N7000 using Tapatalk 2

Better ask Chainfire directly, from what i hear he's a very smart dude . It's a feature he implemented (I guess for safety reasons) and now it comes in handy with this hard brick bug going on. From my point of view I don't have any clear confirmation that this is all true, I only know of chasmodo's confirmation some posts back, and the presence of that kernel file under /sdcard which is also on my device.

BTW, I also flashed ICS from GB with MOP with both wipe data and cache ticked and had no problems. I even did a wipe from the device's stock options because some FC's. I guess I was lucky this time. Anyway I reverted to GB later due to battery drain problems.

Cheers

Here is what Chainfire has to say about MO safety:

http://forum.xda-developers.com/show...postcount=1730

He thinks it is safe, but is not entirely sure.

Originally Posted by l0rd_almighty

Well sorry If i misunderstood you mr smarty pants. Weird that it will load a gb kernel, flash and then load lpy afterwards. I mean why would it have to do that? What's the logic? Enlighten me techwhiz

Sent from my GT-N7000 using Tapatalk 2

Is that the normal way for you to talk to those trying to help you. You are obviously not that smart otherwise he would not have needed to dumb down his explanation to you.

If you act like a spoilt brat, expect to be treated like one. Now get your home work done and get to bed before I tell your mum.

Something more from CF:

http://forum.xda-developers.com/show...postcount=1361

Originally Posted by l0rd_almighty

Well sorry If i misunderstood you mr smarty pants. Weird that it will load a gb kernel, flash and then load lpy afterwards. I mean why would it have to do that? What's the logic? Enlighten me techwhiz

Sent from my GT-N7000 using Tapatalk 2

Just being independent from whatever kernel you are running.....
and therefore being sure it will do what it was intended for......

Maybe you didn't like my tone, but you are being stubborn for days with several
ppl just answering the question you posted yourself, and just not listen.

So instead of calling other ppl smartasses, go get a mirror

Why is the case that 'Mobile Odin' is deemed safe , whereas 'CWM recovery and App' are deemed unsafe and brickable while flashing ICS , although they come from the same great 'MAN' 'Chainfire"

One reason may be that CWM recovery uses the kernel which the User has flashed , while MO uses Stock GB as Chainfire said.

Hence the conclusion is that the E_mmc bug is related to compilation of kernel and its chain of commands. Meaning they have to be compiled in a certain manner , like arrangement of 'Pinballs'

Did full wipe on LP1 3 or 4 times with CWM and 3 times with MobileOdin. At LP5 2 times CWM and 1 time MobileOdin. LPY - 5 times with CWM and 2 times with MobileOdin. LPF 1 time with CWM and 1 time MobileOdin.
Never got any problems. Many people here got bricks only because they are not carefully follow flashing instructions!

Originally Posted by anonymous572

Did full wipe on LP1 3 or 4 times with CWM and 3 times with MobileOdin. At LP5 2 times CWM and 1 time MobileOdin. LPY - 5 times with CWM and 2 times with MobileOdin. LPF 1 time with CWM and 1 time MobileOdin.
Never got any problems. Many people here got bricks only because they are not carefully follow flashing instructions!

Sure........Don't come crying afterwards then

Oh Yeah!

---

Here is another confirmation, since I asked him the very same question before finding this thread:

Originally Posted by Dan_Aykroyd
@Chainfire:

Thanks for your great work and continuous support to the (Samsung) community! I just got a Note and I'm rooting it and going to buy this app as a token of gratitude towards you (I just did! Order Number: XXXXXXXXXXX13514 ). I previously came from a Galaxy S and I've used countless solutions from you so far.

Just a couple of questions that came to mind and didn't find here:

1) Is it safe to use the "Wipe data" function when flashing new ROM, in devices such as SII and mostly Note with the 0x19 eMMC bug?

2) When using the EverRoot in new ICS stock leaks, aren't you be adding an "old" (the currently present) SuperSU / BusyBox (and also if injecting CWM) to the new firmware? Wouldn't it be better to go and download your newly, custom made CF-Root for that new leak, in order to have the last available version for those apps?

Thanks, I hope to have some clarifications on this from you or if someone else knows, since you must be a really busy guy!
(1) Mobile ODIN's wipe data function should be safe from the brick bug. It doesn't use a format command, it just recursively deletes files (which as far as I know is safe)

(2) EverRoot only injects SuperSU, no busybox or CWM. I update the included SuperSU to the latest version with every Mobile ODIN update, so it's usually pretty up to date. Flashing the latest CF-Root for a particular firmware/device may have a slightly newer, or sometimes slightly older SuperSU included. It doesn't really matter, as you can update SuperSU from Market/Play as soon as you're rooted If you wan't CWM and BB and all that, use a CF-Root (which isn't available for most devices that Mobile ODIN supports).