I'm affraid that i have some bad news people... First hardbrick on Franco's V3 kernel - confirmed. Even with MMC_CAP_ERASE disabled.

Here is full post of user eRode, looks like man knows what he's talking about.

Originally Posted by eRode
R3 installed using Mobile Odin. Read the OP, the ROM carries recoveries (R1 didnt).

What's the point of implementing the "MMC_CAP_ERASE" fix if it still doesnt allow safe flashing/wipe/restore? I'm very keen to hear your logic on that.

As an update, brought the bricked phone to the local (HK) Sammy service centre and they had it fixed within an hour by replacing the main board....230 euros later i'm back in business, with the knowledge from the engineer that it was indeed a hard brick.

I paid for my mistake, and am not complaining, I'm not sharing my grief with others on bricking given it was my own decision.

But what I'm sharing is that this MMC_CAP_ERASE fix is not golden. Those that repeatedly post "how do I flash this" should stay away for your own good if you have to ask that level of question.

---------- Post added at 11:54 AM ---------- Previous post was at 11:49 AM ----------



If you read a little more closely PC Odin wasnt able to write to the device like I said.

Same result with a manual adb push (InitialCFRootFlasher) method.

I've been using linux for almost 20 years now since i was a high school student and hold a doctorate in CS, not saying that earns me the right to report a brick but crying wolf and discrediting the alert doesnt really do the community a favour other than to give false confidence to others.

Than we will stay away from ICS ROMs for a while Do you think Samsung gonna find a solution for this or the kernel devs gonna fix it?

MY queation exactly..i mean where do we go from here now. .especially for the few.of us who are not willing to root as yet and want Ics,has samsung released any sort of a press release about this bug other than releasing the kernel?

Sent from my GT-N7000 using xda premium

Originally Posted by GocaS6

I'm affraid that i have some bad news people... First hardbrick on Franco's V3 kernel - confirmed. Even with MMC_CAP_ERASE disabled.

Here is full post of user eRode, looks like man knows what he's talking about.

Originally Posted by eRode
R3 installed using Mobile Odin. Read the OP, the ROM carries recoveries (R1 didnt).

What's the point of implementing the "MMC_CAP_ERASE" fix if it still doesnt allow safe flashing/wipe/restore? I'm very keen to hear your logic on that.

As an update, brought the bricked phone to the local (HK) Sammy service centre and they had it fixed within an hour by replacing the main board....230 euros later i'm back in business, with the knowledge from the engineer that it was indeed a hard brick.

I paid for my mistake, and am not complaining, I'm not sharing my grief with others on bricking given it was my own decision.

But what I'm sharing is that this MMC_CAP_ERASE fix is not golden. Those that repeatedly post "how do I flash this" should stay away for your own good if you have to ask that level of question.

---------- Post added at 11:54 AM ---------- Previous post was at 11:49 AM ----------



If you read a little more closely PC Odin wasnt able to write to the device like I said.

Same result with a manual adb push (InitialCFRootFlasher) method.

I've been using linux for almost 20 years now since i was a high school student and hold a doctorate in CS, not saying that earns me the right to report a brick but crying wolf and discrediting the alert doesnt really do the community a favour other than to give false confidence to others.

There's no confirmation whatsoever he was actually ON Franco R3 - He was on CF-Root and claims he flashed R3 with Mobile Odin - but I can speak from personal experience that when extracting a zImage from a ZIP I've OFTEN accidentally put it in the wrong place and then flashed a zImage from somewhere else.

If he was confirmed to ACTUALLY be on R3 by going into CPUSpy and checking the build host/user before entering CWM, I'd be worried - but he was on a known affected kernel, claims he flashed R3 in MO, and then immediately went into recovery without confirming that the kernel actually flashed properly.

Sent from my GT-P7510 using Tapatalk 2

Originally Posted by GocaS6

Hm first problems in paradise ?!

"eRode
Today, 11:19 AM
# 2729
**BRICK ALERT**

I'm sad to report that restoring a nandroid backup using R3 bricked my Note.

I was running on TMT1.3 with CF5.3 kernal and have developed a habit of flashing abyss4.2 before doing any data wipe or restore work. Out of faith and some reading up of the EMMC bug I skipped my usual abyss step and did a restore of another instance of TMT1.3 directly using the R3 kernal. Nothing was amiss until I reboot and was hung indefinitely at the boot screen. Pulling battery etc did not help.

Last resort, PC Odin flashing stock GB and as soon as the write part began Odin reported an error and failed. The phone is now stuck at the "firmware recovery failed please connect Kies and try again" message.

This is my 7th day of owning the phone so hopefully vendor will replace the unit for me.

You've been warned."

It is not so clear did he was on CF or R3 when he made a restore. Waitin for a update...

That could be something else reboot in downloadmode and try again also check with another rom first that its not corrupt download

Sent from my GT-N7000 using Tapatalk 2

There were a lot of people who flashed franco kernel with mobile odin, and then rebooted only to find that they still were on their previous kernel. The solution was to flash with odin. I bet he was still on brick kernel when he wiped.

False alert for me.

Sent from my GT-N7000 using XDA

if that's the case (he wiped on cfroot), we can assume that the bricking bug is squashed,,,

Re: What an expert said about eMMc bug!

---

Sorry bad post