[Announcement] TWRP 3.0.2-1 has a fatal bug! Do not backup or restore EFS on 3.0.2-1

bogomil4e

Member
Oct 18, 2012
35
77
0
Haskovo
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!

If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:

ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384

and

ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384


This should fix it for ANY Nexus 6P users.

Users on other phones with the same problem await instructions!
 
Last edited:

Ericarthurc

Senior Member
Jul 28, 2013
324
120
0
Fastboot flash (or use Flashfire?) a Marshmallow vendor.img to get older versions of TWRP working on encrypted Nougat.

Sent from my Nexus 5X using Tapatalk
So I can flash MTC20F vendor through fastboot and Nougat will still run fine??

My phone isn't in boot loop btw; I am running stock Nougat. Just saw that 3.0.2-1 had issues
 
Last edited:

ultyrunner

Senior Member
Dec 31, 2010
816
255
0
604
No. TWRP team is not made of hundreds of people! You can count them on one hand AND they have other jobs and families.
Sadly that means that they cant work on it 24/7 and well just have to wait and see. All the devs told me was that a fix has been made and pushed soon.
Yeah, I know. A "no idea" would have been sufficient, instead of the unnecessary lecture about devs volunteering their time, which I understand very well.
 

joeyddr

Senior Member
May 4, 2011
1,991
329
103
Yeah, I know. A "no idea" would have been sufficient, instead of the unnecessary lecture about devs volunteering their time, which I understand very well.
I agree but, i think maybe they should of tested a MM backup and restore before releasing? cause thats what caused mine and of course now that the fix is out my phone is sitting with huawei right now for up to 14 days.... the phone in which i flashed stock MM and locked. So if they decide not to fix my phone for whatever reason i get a locked bootlooping phone back. Hopefully I can fastboot boot twrp and run the DD commands if thats what they decide to do.
 

musashiken

Senior Member
Feb 22, 2010
1,354
152
93
That will work too and its basically the same thing. Our idea was to let the phone generate them again just to be safe for extra security as brand new perfect EFS partitions is better than old ones.
Oh so that means I don't need any EFS backup for this method?

I don't have one anyway.
 

defcondev

Senior Member
Jul 19, 2013
193
197
83
TX
I agree but, i think maybe they should of tested a MM backup and restore before releasing? cause thats what caused mine and of course now that the fix is out my phone is sitting with huawei right now for up to 14 days.... the phone in which i flashed stock MM and locked. So if they decide not to fix my phone for whatever reason i get a locked bootlooping phone back. Hopefully I can fastboot boot twrp and run the DD commands if thats what they decide to do.
Mine shipped off to Huawei as well.

But with you flashing stock and re-locking the bootloader, I don't think that's possible.

Due to California's "Smartphone Kill-Switch Law" (SB-962), you have to enable the "Allow OEM Unlocking" in developer settings to unlock the bootloader.

And an unlocked bootloader is required to "fastboot flash", as well as "fastboot boot" if I remember correctly.

Perhaps someone can clarify...
 

joeyddr

Senior Member
May 4, 2011
1,991
329
103
Mine shipped off to Huawei as well.

But with you flashing stock and re-locking the bootloader, I don't think that's possible.

Due to California's "Smartphone Kill-Switch Law" (SB-962), you have to enable the "Allow OEM Unlocking" in developer settings to unlock the bootloader.

And an unlocked bootloader is required to "fastboot flash", as well as "fastboot boot" if I remember correctly.

Perhaps someone can clarify...
Thing is if it was unlocked but then I locked it via fb command but it never booted Android to read that you checked off allow unlock it might be possible to fastboot OEM unlock again. Just a thought.