Question OTA without data loss custom kernel?

[Stoowyguy]

Please post the method utilized for to KEEP data when new OTA available and have a custom kernel such as Eng.stk's Blu_spark.
The problem I ran into today was an unstable recovery experience, no desktop connection as ADB sideload was going to be my method to retain data. This eventually led me to an android laying on back black screen "error!" or "No Command".
I got back to fastboot, and did a flash_all.bat procedure via Windows.
OR ,can't we restore stock kernel and update system on settings page? I tried last time for JAN when I tried reflashing the same boot.img from the update I was on using fastboot flash boot (boot.img) didn't work I couldn't post. SO I flash_all.bat in fastboot.

How can we take the OTA.zip and apply it.

 

[Druboo666]

use pixel flasher to flash the full image and then flash then custom kernel

 

[96carboard]

Edit the flash-all.sh to replace the "-w" parameter with "--skip-reboot" on the last real line to prevent it from wiping userdata and remain in fastboot. Then install your custom images like "fastboot flash boot boot.img". Then finally "fastboot reboot".

 

[kingpeppermint]

Isn't removing the -w parameter the way to let it not ''wipe'' everything? Had something similar this week in the end recovered via the android flash tool and ticked off the wipe data parameters then when it booted again applied root again after that the costum rom(in my case kikura which can't be flashed using fastboot)

 

[Stoowyguy]

Edit the flash-all.sh to replace the "-w" parameter with "--skip-reboot" on the last real line to prevent it from wiping userdata and remain in fastboot. Then install your custom images like "fastboot flash boot boot.img". Then finally "fastboot reboot".

I wouldn't mess with that lol Thats my last resort of flashing do you know anything about applying an OTA.zip not the flash_all.bat

 

[Stoowyguy]

You know Google hoping things wont be derped after they bring up a second fastboot fastboot'd. XD

 

[96carboard]

Isn't removing the -w parameter the way to let it not ''wipe'' everything? Had something similar this week in the end recovered via the android flash tool and ticked off the wipe data parameters then when it booted again applied root again after that the costum rom(in my case kikura which can't be flashed using fastboot)

Why do you think I said to replace it with the parameter to prevent it from rebooting?

 

[96carboard]

I wouldn't mess with that lol Thats my last resort of flashing do you know anything about applying an OTA.zip not the flash_all.bat

I guess you like doing things the dangerous way, huh?