Bootloop fix - EFS filesystem corruption (Mods please sticky)

themichael

Senior Member

Jul 15, 2011

523

152

New York

• Jan 3, 2014

• #1

Myself and many other people in the note 3 forums have encountered a boot looping issue and the solution has not been documented on the T-Mobile forums. It seems to be a problem with the EFS filesystem getting corrupted for various reasons (kernel flash, twrp restore, etc).

Below is a link to the fix from the 9005N forum. It wipes the EFS partition so it can be rebuilt uncorrupted. It does not affect any data, etc.

I take no credit for the fix and am simply reposting so T-Mobile users can find it easily.

Link: http://xdaforums.com/showthread.php?t=2507403

 

Last edited: Jan 3, 2014

• 

Reactions: Persianhawkes

slick4mitch

Senior Member

Oct 11, 2009

955

316

• Jan 3, 2014

• #2

Does a same fix exists for the Tmobile Note 2? I have this problem on my Note 2, anyone? Thanks!

 

themichael

Senior Member

Jul 15, 2011

523

152

New York

• Jan 3, 2014

• #3

I am not aware of that issue on the note 2 but if it is the same issue then the above could work. It may not but it will most likely not cause further harm.

 

Persianhawkes

Senior Member

Sep 24, 2012

518

183

Virginia Beach

OnePlus 9 Pro

OnePlus 11

• Jan 3, 2014

• #4

Thanks for posting this. I encountered this 2 days ago and had to wipe it manually. It seems as its happens when restoring a backup via TWRP not sure about CWM.

Sent from my SM-N900T using Tapatalk

 

themichael

Senior Member

Jul 15, 2011

523

152

New York

• Jan 3, 2014

• #5

yeah I have heard the twrp causes an error with restores. I have personally encountered it when flashing a new kernel and sometimes even change kernel settings and rebooting. seems to be a little different for everyone but almost always the same issue/fix in the end.

 

kabuk1

Senior Member

Jan 17, 2007

1,402

490

Wisconsin

Samsung Galaxy Note 4

Samsung Galaxy Note 5

• Jan 3, 2014

• #6

My EFS got borked after flashing a new kernel too. I had to manually fix it in TWRP with the terminal, but it'll be nice to have a flashable file to fix it next time it happens.

 

chuko303

Senior Member

Dec 24, 2011

2,155

399

colorado

• Jan 3, 2014

• #7

Sucks when it happens out of nowhere what could be the main cause of this?

Sent from my SM-N900T using xda app-developers app

 

themichael

Senior Member

Jul 15, 2011

523

152

New York

• Jan 9, 2014

• #8

note sure, my guesses its a something Samsung can fix with a firmware update. the fix works for me but sometimes the problem comes back and I have to re-flash the fix.

 

chuko303

Senior Member

Dec 24, 2011

2,155

399

colorado

• Jan 9, 2014

• #9

True has only happened to me once but I can see how sensitive the note 3 is

Sent from my SM-N900T using Tapatalk