Method for avoiding emmc brick: rootgalaxynote.com

[Neuralgia]

At www.rootgalaxynote.com they recommend flashing first Abyss kernel.

Is this true? Just wanted to make sure.

 

[Whiskeyjack4855]

Yes it's true... Read dr ketan's thread in Android development to root your note

Sent from my GT-N7000 using free xda app-developers app for poor people

 

[jonpaslim]

And flash safe ics kernel like speedmod, goku, notecore, and cf root 5.6.

 

[msedek]

And flash safe ics kernel like speedmod, goku, notecore, and cf root 5.6.

Hey cf root its not safe.... That's a stock repack with root but it does not have MMC_CAP_ERASE disabled.. Be careful with what you write

Enviado desde mi GT-N7000 usando Tapatalk 2

 

[jeetu1981]

Hey cf root its not safe.... That's a stock repack with root but it does not have MMC_CAP_ERASE disabled.. Be careful with what you write

Enviado desde mi GT-N7000 usando Tapatalk 2

CF Root Kernel from v5.6 is said to be possibly safe, here is the note from Chainfire's thread.
v5.6 and newer
- Possible brickbug fix.

But then it still have risk,

Quote:
Originally Posted by chasmodo
I wouldn't flash another Rom from ICS CF-Root kernels, because there is a possibility of a brick. Not a very high risk, but still a risk:

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

You are better off doing it from Notecore kernel which has a double-safety net against erase commands.

Another note by Entropy512-
"If you run a custom kernel with MMC_CAP_ERASE disabled - you will be safe.

If you run CF-Root 5.6 (with erase disabled in recovery) - You will be safe to wipe and factory reset, but you are NOT guaranteed safety when flashing other firmwares - they can use a dangerous update-binary."

 

[jonpaslim]

Hey cf root its not safe.... That's a stock repack with root but it does not have MMC_CAP_ERASE disabled.. Be careful with what you write

Enviado desde mi GT-N7000 usando Tapatalk 2

It is mmc cap erase disabled. Thats why the devs include the 5.6 in their custom rom. The only time the devs stop including the 5.6 because chainfire is in vacation and chainfire last 5.6 is lrg.

 

[dr.ketan]

Here some clearance what i know
CF root kernel have Emmc erase cap disable in his recovery, not in kernel.
So it is safe to perform wipe, nandroid backup/restore. But not safe to flash other stuff which can have dangerous update binarry, in such case still such command goes direct to kernel and can lead to Brick.
Now this will make sense why recovery is used by other custom kernel. e.g. Notecore, that contains safe recovery from CF, and kernel also have disabled emmc erase cap command.

 

[jonpaslim]

Here some clearance what i know
CF root kernel have Emmc erase cap disable in his recovery, not in kernel.
So it is safe to perform wipe, nandroid backup/restore. But not safe to flash other stuff which can have dangerous update binarry, in such case still such command goes direct to kernel and can lead to Brick.
Now this will make sense why recovery is used by other custom kernel. e.g. Notecore, that contains safe recovery from CF, and kernel also have disabled emmc erase cap command.

Thank you Dr. Ketan for making it so clear.

Thus goku and speedmod have the same safety as notecore, safe in CWM and also the kernel?

 

[dr.ketan]

That really i am not aware of speedmod and goku have this or not, as i never used that and didn't studied deeply. I have read OP of speedmod kernel, which clearly mentioned about kernel, but i am not knowing about recovery. But If kernel is safe then i think thats safe, b'coz if any recovery pass any bad script ultimately it will be block by kernel.
Though if i am wrong someone can correct me.