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

[rvarma8282]

Hi I'm Ravi

Sent from my A0001 using Tapatalk

 

[cam30era]

7.1, because before all this I restored to factory,so I got the sailfish and even tried Marlin, mines just a pixel, not XL, and when I run fastboot flash file.zip i get unknown partition, error:cant determine image filename.
I can seem to find any factory images that are .img,just zipped ones,that have like the one OP shows.

Don't do this > fastboot flash file.zip

You have to type the actual name of the .bat file.

Here's the Google page for factory images. Go to "Sailfish". Click the download link for November for the same version ("V" or "X") that you were on. > https://developers.google.com/android/images

 

[MrMeek]

Don't do this > fastboot flash file.zip

You have to type the actual name of the .bat file.

Here's the Google page for factory images. Go to "Sailfish". Click the download link for November for the same version ("V" or "X") that you were on. > https://developers.google.com/android/images

ok I got those,Im verizon so I was using the X . And in the command I have tried typing just "Flash-all.bat".and get command write failed (no error).

 

[cam30era]

ok I got those,Im verizon so I was using the X . And in the command I have tried typing just "Flash-all.bat".and get command write failed (no error).

Just double click the flash-all.bat file

 

[MrMeek]

Just double click the flash-all.bat file

I get the same thing.
target didn't report max-download-size
sending 'bootloader' (32820 KB)...
FAILED (command write failed (No error))
finished. total time: 0.005s
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.005s
target didn't report max-download-size
sending 'radio' (57048 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.005s
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
error: cannot load system.img from flash
Press any key to exit...

 

[cam30era]

@MrMeek,

What does it say at the bottom of your fastboot screen? Locked or unlocked?

 

[MrMeek]

@MrMeek,

What does it say at the bottom of your fastboot screen? Locked or unlocked?

Device is locked
secure boot roduction
Console: Disabled

 

[cam30era]

Device is locked
secure boot roduction
Console: Disabled

Not good. You can't use fastboot because your bootloader is locked. You can't enable USB debugging because it throws errors and reboots. What happened when you booted to stock recovery and tried to ADB sideload?

 

[MrMeek]

Not good. You can't use fastboot because your bootloader is locked. You can't enable USB debugging because it throws errors and reboots. What happened when you booted to stock recovery and tried to ADB sideload?

I cant get into recovery,just goes straight to the error ,then shuts off. I did try to sideload it but didnt work but not sure if the commands were correct.

 

[cam30era]

I cant get into recovery,just goes straight to the error ,then shuts off. I did try to sideload it but didnt work but not sure if the commands were correct.

From bootloader, if you select "Recovery" your device shuts off? Or do you get the android on his back?

 

[MrMeek]

From bootloader, if you select "Recovery" your device shuts off? Or do you get the android on his back?

no from bootloader, I choose recovery and then goes to the "Your device is corrupted" ,then powers off after a few seconds.

 

[cam30era]

no from bootloader, I choose recovery and then goes to the "Your device is corrupted" ,then powers off after a few seconds.

I'm out of ideas. Sorry.

 

[MrMeek]

I'm out of ideas. Sorry.

Ok I found a very simple solution it seems, for anyone else getting a softbrick. From Bootloader,type "fastboot continue" Thanks for the help though @jcase you are awesome man,glad you posted that save

 

[CZ Eddie]

OP updated for December's second update, "Q".
And also for new root install method suggested by DeesTroy/TWRP.

 

[Archangel]

What exactly does fastboot continue do?

Ok I found a very simple solution it seems, for anyone else getting a softbrick. From Bootloader,type "fastboot continue" Thanks for the help though @jcase you are awesome man,glad you posted that save

 

[CZ Eddie]

I cant make it past the error "Device is corrupted", it just shuts down after that, If I go to Recovery, it does the same thing. I am able to get into the bootloader though. My phone is unusable right now. On the error screen it shows an address to go to for more information, and its a pixel/nexus page detailing the errors then instructions on how to flash to stock, but it wont work becasue bootloader is locked and the fastboot oem unlock command isnt working.

Sorry, I haven't read all your posts yet.
Have you tried flashing the stock boot.img to both partition A and B yet?
Then flash the flash-all.bat to restore the OS afterwards?


EDIT: N/M I was looking at an older version of this thread and you have since gotten your issue fixed?

 

[Archangel]

I was trying to update to TWRP RC1 from alpha 2 and I fastboot flashed the stock boot.img to both a and b then installed RC1, deleted the fstab-sailfish and then installed SU sr5 but it kept bootlooping back to recovery? Do you have to flash the flash-all right after fasbooting the stock boot image?

Sorry, I haven't read all your posts yet.
Have you tried flashing the stock boot.img to both partition A and B yet?
Then flash the flash-all.bat to restore the OS afterwards?


EDIT: N/M I was looking at an older version of this thread and you have since gotten your issue fixed?

 

[CZ Eddie]

I was trying to update to TWRP RC1 from alpha 2 and I fastboot flashed the stock boot.img to both a and b then installed RC1, deleted the fstab-sailfish and then installed SU sr5 but it kept bootlooping back to recovery? Do you have to flash the flash-all right after fasbooting the stock boot image?

To update to RC1 from Alpha 2, you simply install RC1's EXE from within TWRP.

Flashing the stock boot.IMG's was an unecessary step unless you're missing something from your description of what you're doing.
I've never ever flashed the stock boot.img for any reason other than to un-fook something I fooked up.
The same goes for flashing it to A & B. Never once done that either.

Did you reboot back to TWRP after you installed it?
And then installed SR5 root?
Shouldn't really need to. But it doesn't make sense that you're bootlooping.

 

[Archangel]

Oh how I remember the good ol days of clockworkmod where things seemed so simple LOL. I read back in dee's troy explanation of TWRP and flashing the boot.img to both a and b partitions to avoid it booting back into recovery all the time. Well I had to restore a back up and thats exactly what happened. 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? Now I am back on TWRP Alpha 2 cause RC1 is really wierd for me,,,I am trying to figure out what I am not doing that others are when they are saying they have backed up and restored so many times and I cant even get one to work?

To update to RC1 from Alpha 2, you simply install RC1's EXE from within TWRP.

Flashing the stock boot.IMG's was an unecessary step unless you're missing something from your description of what you're doing.
I've never ever flashed the stock boot.img for any reason other than to un-fook something I fooked up.
The same goes for flashing it to A & B. Never once done that either.

Did you reboot back to TWRP after you installed it?
And then installed SR5 root?
Shouldn't really need to. But it doesn't make sense that you're bootlooping.

 

[Nitemare3219]

I had a bootloop issue where my phone was going to stock recovery and showing "no command." I tried the flash-all.bat and it kept telling me the device had insufficient storage to transfer the .zip with all the main .img files (e.g. system, system_other) and would fail. I tried flashing the relevant .img's myself but failed that as well because there are no good instructions on what needs flashed (e.g. one website said to use "fastboot flash system system.img" when in reality the correct command seemed to be "fastboot flash system_a system.img").

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.