[GUIDE] Restore to stock after soft BRICKED | Install TWRP, Root, Kernel --March 2017

[CZ Eddie]

Oh how I remember the good ol days of clockworkmod where things seemed so simple LOL.

Hahah, CWM FTW.
I almost miss having to press the down arrow 50 times to get the option I wanted to select.
I felt so much in control. lol

In RC1 I checked off system, data, boot, and vendor (all partitions no images) and the back up and restore went fine but it kept rebooting back into recovery?

That happened to me also on my first try. Which led to confusion about needing to back up the IMG's instead of partitions.
But after I restored to stock and then got RC1 running again, I tried the exact same backup and it restored/booted fine.

I'm not sure where you're at right now in your issues.
But it may be a good time to..

TWRP wipe the everythings!
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img (why not, can't hurt)
flash-all.bat the latest full factory image from Google
fastboot boot twrprc1.img
Install RC1 from within TWRP
Delete the fstab
Install RS5 superuser (or wait for RS6 to drop later today and not mess with fstab?)
Boot up & setup OS
TWRP nandroid your ish and back it up to PC.
TWRP nandroid your ish a second time and back it up to PC.
TWRP wipe the everythings.
Reboot to TWRP.
Restore one of the backups.
Test.

 

[CZ Eddie]

Just remembered something.
I think I had the bootloop back into TWRP on another occasion after screwing stuff up.
And then I flashed ElementalX kernel and suddenly I was booting into the OS again.
Not 100% sure. I break a lot of stuff on purpose.
I work from home and have a few minutes here and there to do what I want.

 

[cam30era]

At any rate, the ONLY thing that fixed my damn phone was reflashing the stock factory image with the Unified Toolkit. I think a guide on using that would be a lot easier than dealing with bull**** adb/fastboot issues by trying to do it yourself with those methods.

Was your ADB and fastboot up to date?

 

[Nitemare3219]

Was your ADB and fastboot up to date?

Don't know and don't care. I've never had any notable issues because of ADB/fastboot versions since I've been flashing stuff since 2009. I've updated periodically for other reasons (like getting a new PC), but not because something wasn't working. I downloaded the latest minimal ADB/fastboot and that didn't fix anything either (was doing this at work, not at home where I know ADB was updated since I was trying to block Note7 packages). Point is, the Toolkit worked the 1st time with no issues. Half the instructions for things on the web are either dated/incorrect, or don't consider when **** goes wrong (like in my case of having insufficient storage for the flash-all.bat).

 

[jp712]

Don't know and don't care. I've never had any notable issues because of ADB/fastboot versions since I've been flashing stuff since 2009. I've updated periodically for other reasons (like getting a new PC), but not because something wasn't working. I downloaded the latest minimal ADB/fastboot and that didn't fix anything either (was doing this at work, not at home where I know ADB was updated since I was trying to block Note7 packages). Point is, the Toolkit worked the 1st time with no issues. Half the instructions for things on the web are either dated/incorrect, or don't consider when **** goes wrong (like in my case of having insufficient storage for the flash-all.bat).

I too had the insufficient storage error when it was trying to update the image.
Turning off USB Debugging seems to have fixed it for me. Then just run the last step it failed on again.

fastboot update image-marlin-nmf26q.zip

Hope that helps...

 

[Nitemare3219]

Was your ADB and fastboot up to date?

I too had the insufficient storage error when it was trying to update the image.
Turning off USB Debugging seems to have fixed it for me. Then just run the last step it failed on again.

fastboot update image-marlin-nmf26q.zip

Hope that helps...

I had a soft brick and even did a factory reset in the midst of all the issues. ADB/fastboot still never worked for flashing the entire 7.1.1 factory image.

 

[jp712]

I keep getting stuck at not enough space to flash image zip. Any suggestions?

Sent from my SM-G935W8 using XDA-Developers mobile app

Boot it back up and turn off USB Debugging, fixed the issue for me.

 

[MrMeek]

What exactly does fastboot continue do?

If you get in a soft brick like I was in,check Jcases PSA thread, you can run that to get out of it so you can actually get in your phone and turn on usb debugging to flash a stock rom.

 

[aholeinthewor1d]

If you get in a soft brick like I was in,check Jcases PSA thread, you can run that to get out of it so you can actually get in your phone and turn on usb debugging to flash a stock rom.

Where is this thread idk why I don't see it

Edit: I'm retarded

 

[virtyx]

is it normal for fstab.marlin to appear again after installing supersu from zip?

 

[CZ Eddie]

is it normal for fstab.marlin to appear again after installing supersu from zip?

yep

 

[virtyx]

yep

thank you

 

[virtyx]

anyone know to to enter "service mode" on the pixel xl to view fast dormancy and to disable it. i remember my s6 had a dialler code.

 

[cam30era]

anyone know to to enter "service mode" on the pixel xl to view fast dormancy and to disable it. i remember my s6 had a dialler code.

*#*#4636#*#*

 

[virtyx]

*#*#4636#*#*

nothing about fast dormancy in there.

 

[CZ Eddie]

Updated OP for new SuperSU 2.79 and ElementalX 1.02 and also cleaned up the OP with

 wraps.
Please let me know of any mistakes.
It's hard trying to keep such a long OP maintained without errors.  :eek:

2.79 SuperSU does not require deleting fstab like 2.78 did.  
Thanks, Chainfire & DeesTroy!  :good:

Also added a link to download a modified flash-all.bat script with the "[B]-w[/B]" removed so it doesn't wipe your data.
http://www.filedropper.com/flash-all

 

[CZ Eddie]

Updated OP for new superuser, kernel and January android image.
Cleaned a few things up.

 

[cam30era]

@CZ Eddie,
Maybe update the OP with links to Google's ADB and fastboot instead of minimal?

 

[557953]

Thanks for this guide, I just have a question, I have an EE Pixel XL so BL was unlockable originally (cheers Root Ninja) in the new Jan V update I downloaded (I'm in UK) when I unpacked "image-marlin-nmf26v.zip" I noticed there is a "bootloader-marlin-8996-012001-1611091517 .img" file which I don't see in the U update thats in the pictures of the guide, should I remove that before running the flash-all.bat? I don't wanna end up with a locked BL again, and if I remove it and need it I want a paperweight even less.

Thanks in advance people

 

[cam30era]

Thanks for this guide, I just have a question, I have an EE Pixel XL so BL was unlockable originally (cheers Root Ninja) in the new Jan V update I downloaded (I'm in UK) when I unpacked "image-marlin-nmf26v.zip" I noticed there is a "bootloader-marlin-8996-012001-1611091517 .img" file which I don't see in the U update thats in the pictures of the guide, should I remove that before running the flash-all.bat? I don't wanna end up with a locked BL again, and if I remove it and need it I want a paperweight even less.

Thanks in advance people

If your bootloader is already unlocked, it'll stay unlocked.