Database Develop

[Q] broken recovery on stock 4.2.2

Dear all,
I've a tf701 with stock 4.2.2 build JDQ39.WW_epad-10.14.1.2820130827
I've been able to root it through adb/fastboot.
I tried to use the same way to flash the recovery and adb says "ok"
Problem is that when I launch RCK on fastboot; it starts normaly, not in recovery.
I'd tried to update the tf701 but update process tried to restart in recovery and it is the same thing I describe above.
I tried also rom manager to flash the recovery but the device is not superted yet.
If somebody could help me providing a recovery.img that work with JDQ39.WW_epad-10.14.1.2820130827 it would be great
Thanks in advance for tips and comments

guerito73 said:
Dear all,
I've a tf701 with stock 4.2.2 build JDQ39.WW_epad-10.14.1.2820130827
I've been able to root it through adb/fastboot.
I tried to use the same way to flash the recovery and adb says "ok"
Problem is that when I launch RCK on fastboot; it starts normaly, not in recovery.
I'd tried to update the tf701 but update process tried to restart in recovery and it is the same thing I describe above.
I tried also rom manager to flash the recovery but the device is not superted yet.
If somebody could help me providing a recovery.img that work with JDQ39.WW_epad-10.14.1.2820130827 it would be great
Thanks in advance for tips and comments
Click to expand...
Click to collapse
DO NOT USE ROM MANAGER! Fastest way to brick a transformer. Lucky you didn't.
Which recovery are you trying to flash?
Have you tried upgrading to 4.3 from Asus?

sbdags said:
DO NOT USE ROM MANAGER! Fastest way to brick a transformer. Lucky you didn't.
Which recovery are you trying to flash?
Have you tried upgrading to 4.3 from Asus?
Click to expand...
Click to collapse
I tried to flash CWM recovery, on adb it was a file called recovery.img but to my understanding it works with the asus stock 4.3 not the 4.2.2
OTA asus update dosn't work
I tried to update placing a SD card with the asus update, got a notification that my device will be updated but.... nothing the device restart (guess try to boot on recovery so fails and start normaly
still stuck there

Any ideas?
Somebody known if it is possible to flash CROMI X from a PC thanks to adb for instance?

guerito73 said:
Any ideas?
Somebody known if it is possible to flash CROMI X from a PC thanks to adb for instance?
Click to expand...
Click to collapse
See the recovery for 4.2.2 here:
http://forum.xda-developers.com/showthread.php?t=2622594
then you can upgrade to 4.3 from below:
http://forum.xda-developers.com/showpost.php?p=49969993&postcount=21

Many thanks, I restored the CWM recovery
May I upgrade from stock 4.2.2 with CWM recovery to CROMI X stable?
Thanks again

guerito73 said:
Many thanks, I restored the CWM recovery
May I upgrade from stock 4.2.2 with CWM recovery to CROMI X stable?
Thanks again
Click to expand...
Click to collapse
No you must go to JB 4.3 10.26.1.18 first.

ok i've tried to install jb-4.3_ota-full_t701t_macallan.zip trought CWM recovery for 4.2.2
it failed
says assert failed getprop ("ro.product.device") == "tf701t" || getprop ("ro.build.product") "tf701t"
error in /emmc/10/jb-4.3-ota_full_tf701t_macallan.zip
any idea?

guerito73 said:
ok i've tried to install jb-4.3_ota-full_t701t_macallan.zip trought CWM recovery for 4.2.2
it failed
says assert failed getprop ("ro.product.device") == "tf701t" || getprop ("ro.build.product") "tf701t"
error in /emmc/10/jb-4.3-ota_full_tf701t_macallan.zip
any idea?
Click to expand...
Click to collapse
Easier if you install the stock 4.2.2 recovery from that url and then put the zip inside the asus firmware zip in the root of internal or micro sd and reboot. It should update to 4.2.2 that way. I don't think you can flash asus stock roms from CWM yet.

Ok,
I flashed the recovery found at this url: http://droidbasement.com/asus/tf701t/stock/
It won't start, I boot android normaly instead of the recovery I think it is a recovery only for 4.3
The only recovery I've found for 4.2.2 id CWM

guerito73 said:
Ok,
I flashed the recovery found at this url: http://droidbasement.com/asus/tf701t/stock/
It won't start, I boot android normaly instead of the recovery I think it is a recovery only for 4.3
The only recovery I've found for 4.2.2 id CWM
Click to expand...
Click to collapse
Some news; flashed several times the recovey, adb flash without errors but trying to update asus update (WW_10_26_1_18_SDupdate.zip or WW_epaduser_10_26_1_18_UpdateLauncher.zip) my tf701t restart and that's it, no do anything more and I still stuck to 4.2.2 JDQ39.WW_epad-10.14.1.28
I've contacted asus; I hope they will be able to help me to restore the recovery.

just to be sure, it is not possible to flash the stock firmware from adb console?

guerito73 said:
Some news; flashed several times the recovey, adb flash without errors but trying to update asus update (WW_10_26_1_18_SDupdate.zip or WW_epaduser_10_26_1_18_UpdateLauncher.zip) my tf701t restart and that's it, no do anything more and I still stuck to 4.2.2 JDQ39.WW_epad-10.14.1.28
I've contacted asus; I hope they will be able to help me to restore the recovery.
Click to expand...
Click to collapse
You have to unzip the ....UpdateLauncher.zip once which will give you a .....user.zip. That's the file you need to flash.

Yes I know, I've do that, it has detect a firmware and starts the update process but only restart the tab.
After that, when I plug again the SD card with user.zip nothing...
Firmware is no longer detected on SD card.
Still with recovery issue that's why I wonder if it is possible to flash stock ROM through adb.

guerito73 said:
Yes I know, I've do that, it has detect a firmware and starts the update process but only restart the tab.
After that, when I plug again the SD card with user.zip nothing...
Firmware is no longer detected on SD card.
Still with recovery issue that's why I wonder if it is possible to flash stock ROM through adb.
Click to expand...
Click to collapse
Not in ADB - Android can't be running when you flash the system partition but you can flash the system blob in fastboot.
Check this out: http://forum.xda-developers.com/showthread.php?t=2179759&page=2

berndblb said:
Not in ADB - Android can't be running when you flash the system partition but you can flash the system blob in fastboot.
Check this out: http://forum.xda-developers.com/showthread.php?t=2179759&page=2
Click to expand...
Click to collapse
Ok thanks for the info.
I no response from asus support concerning a way to restore the 4.2.2 recovery I'll do that.
Just to be sure, I erease ell partitions (system, recovery, user data, boot, misc, cache and only flashing system (blob file) will re write every partitions?

guerito73 said:
Ok thanks for the info.
I no response from asus support concerning a way to restore the 4.2.2 recovery I'll do that.
Just to be sure, I erease ell partitions (system, recovery, user data, boot, misc, cache and only flashing system (blob file) will re write every partitions?
Click to expand...
Click to collapse
.
The system blob contains everything: kernel, recovery and system files. It does not re-write user data naturally, and I don't think you have to wipe that partition. Doesn't sound as if your trouble is related to user data.... So you should erase system, boot and recovery. I would also erase misc and cache - can't hurt...
Here's a link with a very good step-by-step guide: http://forum.xda-developers.com/showthread.php?t=2195883

Ok, thank you for your interest.
I confirm that with recovery CWM for stock 4.2.2 it is not possible to flash the firmware provided by Droidbasement.
got the error message:
assert failed getprop ("ro.product.device") == "tf701t" || getprop ("ro.build.product") "tf701t"
error in /emmc/10/jb-4.3-ota_full_tf701t_macallan.zip
Click to expand...
Click to collapse
I tried to go back to stock recovery but the one provided on droidbasement doesn't work; when "RCK" selected on fastboot mode, it says "booting recovery kernel" and restart the tab; that's all.
Same thing when tried to update asus stock firmware placing the update on SD card it's only reboot the tab.
To my understanding the stock recovery image provided by droidbasement works only with 4.3 stock not 4.2.2 stock.
So I'm able to flash a recovery CWM for 4.2.2 but can do nothing with it and not able to go back to a workable stock recovery
When I try to flash the stock recovery on droidbasement, it just restart the tab, still stuck at this step since 1 week.
I'm waiting a response from asus support I asked them a recovery image for stock 4.2.2
If they are not able to help me, I'll considere to flash the blob in fastboot.
Obviously if someone get tips to help me I'll reconsidere my plans

guerito73 said:
Ok, thank you for your interest.
I confirm that with recovery CWM for stock 4.2.2 it is not possible to flash the firmware provided by Droidbasement.
got the error message:
I tried to go back to stock recovery but the one provided on droidbasement doesn't work; when "RCK" selected on fastboot mode, it says "booting recovery kernel" and restart the tab; that's all.
Same thing when tried to update asus stock firmware placing the update on SD card it's only reboot the tab.
To my understanding the stock recovery image provided by droidbasement works only with 4.3 stock not 4.2.2 stock.
So I'm able to flash a recovery CWM for 4.2.2 but can do nothing with it and not able to go back to a workable stock recovery
When I try to flash the stock recovery on droidbasement, it just restart the tab, still stuck at this step since 1 week.
I'm waiting a response from asus support I asked them a recovery image for stock 4.2.2
If they are not able to help me, I'll considere to flash the blob in fastboot.
Obviously if someone get tips to help me I'll reconsidere my plans
Click to expand...
Click to collapse
I think you are wasting your time waiting for a response from Asus. They do not provide support for our flashing shenanigans

berndblb said:
I think you are wasting your time waiting for a response from Asus. They do not provide support for our flashing shenanigans
Click to expand...
Click to collapse
Yes, you are right, asus support just tell me a kind of **** you...
As asus blob file get everything including the recovery, I've downloaded the 4.2.2 update from asus and unpack the blob to get the recovery.img
unpacking blob file I've got:
blob.BC1
blob.BCT
blob.EBT
blob.PT
Anybody knows where is the recovery file and how can I do to make it flashable?
EDIT: I guess recovery is not in the blob file but in a recovery folder containing recovery-from-boot.p

[Q] PLEASE POST full STOCK HTC ONE ROM exe for AT&T new kitkat Vers: 4.18.502.7

ISSUE RESOLVED: keeping post since active since I still need the rom exe. But boot looping fixed.
My AT&T HTC One is stuck in boot loop, probably to do with the KK OTA update. I have looked everywhere, read posts all night, and tried all of the various reboots and reflashings of recovery files and firmware, erased caches, locked and unlocked bootloaders. Can anyone post the executable RUU for the stock ROM KK version 4.18.502.7? I'd really appreciate it. I can't sideload a zip (it stalls). I'm aware of the other post asking for the same thing and the response in it with a link to the file, but that link actually is only to a recovery zip with darkbootloader, which seems also to require S-OFF, even if I did have some way to sideload it.
The firmware updated before it began looping, so I can't just reinstall a prior stock ROM exe file, as far as I can tell. I tried anyway!
I hesitate to install the .1540. Dev. Ed. version of the ROM that's available because it says in the notes that it's "compatible" with my cid and PN, etc, but I think they mean for recovery file purposes and not for a full ROM install. So I think I just need the ROM exe, if anyone has it? Thanks!

more info
by the way, when it crashed i had installed the ota update and then restarted play around with it, then rebooted in bootloader and unlocked, reinstalled twrp and AndRev HD 51. I've noticed two problems there. The first is that the Xposed module's latest update totally defeats my internet wifi and especially crashes vpn sevice. prior versions did not and I could not down-install to prior version (is preinstalled in HD 51). The other problem is that in looking around for this boot loop probably, turns out that TWRP apparently doesn't get along well with the encryption. don't know why. this stuff may or may not be part of the problem, but at this point i have no OS, an erased cache and can't even get into recovery (tried flashing twrp, older twrps and CWM. thanks.

You are screwed if you have no recovery, and the phone is s-on. You need to find a way to get in recovery. Alternatively try to flash the firmware only from OTA to get stock recovery.
sent from my mobile device

randomOne1111 said:
My AT&T HTC One is stuck in boot loop, probably to do with the KK OTA update. I have looked everywhere, read posts all night, and tried all of the various reboots and reflashings of recovery files and firmware, erased caches, locked and unlocked bootloaders. Can anyone post the executable RUU for the stock ROM KK version 4.18.502.7? I'd really appreciate it. I can't sideload a zip (it stalls). I'm aware of the other post asking for the same thing and the response in it with a link to the file, but that link actually is only to a recovery zip with darkbootloader, which seems also to require S-OFF, even if I did have some way to sideload it.
The firmware updated before it began looping, so I can't just reinstall a prior stock ROM exe file, as far as I can tell. I tried anyway!
I hesitate to install the .1540. Dev. Ed. version of the ROM that's available because it says in the notes that it's "compatible" with my cid and PN, etc, but I think they mean for recovery file purposes and not for a full ROM install. So I think I just need the ROM exe, if anyone has it? Thanks!
Click to expand...
Click to collapse
This RUU does not exist yet, only the FOTA version - I've been in talks with HTC about this very thing. They do not have an ETA for the RUU, unfortunately.

SaHiLzZ said:
You are screwed if you have no recovery, and the phone is s-on. You need to find a way to get in recovery. Alternatively try to flash the firmware only from OTA to get stock recovery.
sent from my mobile device
Click to expand...
Click to collapse
Hm. I did flash the firmware from an OTA. But couldn't actually boot into recovery after that. I can flash custom recoveries but can sideload without the intall stalling about a third of the way through (just hangs, no error messages). Then after that if I restart it loops. I can maybe fix the "tampered" warning and swap it out somewhere. I think it's the encryption while using twrp maybe resulted in some hiccup. But I thought the firmware flash would fix that. And I'm not sure how you can actually tell whether the flashed firmware is successful. (it says it is in the command prompt, but the phone doesn't really do anything all that different and i already updated with the OTA so the numbers won't change).
Looking at the board today and reading through the posts I see many people reporting basically being in the same boot loop boat after the OTA update, though with diff versions maybe there's some FW problem. weird so many posts of similar boot looping.
Thanks for responding.
This issue is temporarily resolved, was able to push ARHD in TWRP (would not sideload without erroring out during install, but was able to push zip to sdcard and then install from there) after much wiping using both twrp and cwm. Did notice when using CWM recovery would not install ARHD off sdcard push, and would flag unknown files .... android..security during wipes, so i am guessing that encrypting a custom ROM at least with TWRP as recovery was a bad idea. hopefully this will stay stable until the KK OEM RUU EXE is available. Thanks for the help.

[Q] Help crash after flash

First of all sorry for my English...
Yesterday I was trying to install vanir room to my p880 after 10 hours I rooted the phone and unlock the bootloader then installed cwm but after reboot I get stuck on logo so I used kdz and load LGP880AT-00-V20a-262-000-MAR-26-2013+0 with (after 4 hours ) then i try using twrp and finally load the room (vanir_p880_4.4.4.112414.zip) and Gapps after rebooting I started getting crashes ( aosp keyboard, com.google, home and back buttons etc didn't work)
so again kdz then i try other room Paranoid but the same thing..
What I'm doing wrong? I used factory reset, wipe etc but same results

what gapps you flashed?

blansh heretics
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.

G0ll0 said:
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
Click to expand...
Click to collapse
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942

LGaljo said:
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?

G0ll0 said:
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
Click to expand...
Click to collapse
I think you should try with CWM first, get it: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.5-p880.img
you can flash it with this app if you are rooted: https://play.google.com/store/apps/details?id=com.cgollner.flashify
then you can download CM11 from here: http://download.cyanogenmod.org/?device=p880
and gapps from last mine post
and then boot to recovery, do factory reset and wipe /system, then flash rom and gapps.
Hope it helps

Crash After Flash OTA Vanir 5.0
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!

BermiePT said:
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
Click to expand...
Click to collapse
Have you tried to flash a recovery using fastboot? You won't need to root (if you are going to use a custom ROM) and/or it will be easier with a custom recovery

Soft brick after last update.
Hello,
I seem to have a similar problem. I updated a few days ago using Vanir updater. There were no warnings re updating the recovery, just a warning regarding losing root. I checked restore root. The phone rebooted to the bootloader logo, then to a black screen. Now, I can access Cyanogen recovery, SW update mode, abd fastboot mode using buttons and the recovery options. ADB can see the phone only in recovery mode, but not in fastboot or SW update mode. CM recovery has no option to mount USB storage, so my PC cannot see the phone, and I cannot side load a new recovery and flash a new ROM.
Is there any way to use ADB if it cannot see your phone in fastboot or SW mode? Perhaps modify the settings.secure string to enable ADB? ADB can see the phone in recovery mode.
Otherwise I will try flashing a stock ROM via KDZ or LG firmware update tool, the re-root and proceed - but rooting was a major ordeal the first time, so I would like to avoid doing that again.
Thanks in advance.

[Q] [RESOLVED] Lollipop OTA update aborted

Hi all.
This is a moment that I'm disconnected hacks because I am in stock (6.0.401.11) and satisfied. I had OTA updates without problems until this kitkat version but today after receiving and downloading 2 times the OTA lollipop I can not install it because installation starts well and some moments later, the screen is stuck on the phone with red triangle and I have this in the recovery:
Verifying current system ...
"/ System / bin / reboot" has unexpected content
Installation aborted
Even when I do it manually, it's the same. Yet I have just manually switch successfully 6.0.401.12 that I missed somehow.
What's the trouble?

kamso said:
Hi all.
This is a moment that I'm disconnected hacks because I am in stock (6.0.401.11) and satisfied. I had OTA updates without problems until this kitkat version but today after receiving and downloading 2 times the OTA lollipop I can not install it because installation starts well and some moments later, the screen is stuck on the phone with red triangle and I have this in the recovery:
Verifying current system ...
"/ System / bin / reboot" has unexpected content
Installation aborted
Even when I do it manually, it's the same. Yet I have just manually switch successfully 6.0.401.12 that I missed somehow.
What's the trouble?
Click to expand...
Click to collapse
this says to me, in system/bin you have modified files, you must be 100% stock so flash TWRP recovery then use this: https://www.androidfilehost.com/?fid=95864024717072880 to retore full stock rom.
DO NOT try and root or anything, 100% pure stock required.
Full Reboot into android
boot back to recovery and flash this pre-load data here: https://www.androidfilehost.com/?fid=95864024717072879
Full reboot into android
You will need TWRP recovery for both of the above files, but you will also need to flash stock recovery afterwards to update which is here: https://www.androidfilehost.com/?fid=95864024717072472
fastboot flash recovery
fastboot erase cache
fastboot reboot-bootloader
full reboot into android, then update.
DO NOT try and root or anything, 100% pure stock required.

Seanie280672 said:
this says to me, in system/bin you have modified files, you must be 100% stock so flash TWRP recovery then use this: https://www.androidfilehost.com/?fid=95864024717072880 to retore full stock rom.
DO NOT try and root or anything, 100% pure stock required.
Full Reboot into android
boot back to recovery and flash this pre-load data here: https://www.androidfilehost.com/?fid=95864024717072879
Full reboot into android
You will need TWRP recovery for both of the above files, but you will also need to flash stock recovery afterwards to update which is here: https://www.androidfilehost.com/?fid=95864024717072472
fastboot flash recovery
fastboot erase cache
fastboot reboot-bootloader
full reboot into android, then update.
DO NOT try and root or anything, 100% pure stock required.
Click to expand...
Click to collapse
Ok, thank you. But what I don't understand is that there's a long time I'm no more root, I'm full stock (Rom, recovery...), only S-off and Unlocked. So Why for previous OTA updates I have not had this problem? Why I have to manually update successfully from 6.09.401.11 version to 6.09.401.12 one? Why it is only the upgrade to the Lollipop which has problem?
What is the preload data? I already have this: https://www.androidfilehost.com/?w=...0f40a2a319761577a4c3f1e723594b05669cb009e9d00
Can I flash it and the stock recovery only?

Your problem is the lack or corruption of the file /bin/reboot
2 solutions:
Flash a custom recovery and reflash the rom
Flash a custom recovery and replace the file

migascalp said:
Your problem is the lack or corruption of the file /bin/reboot
2 solutions:
Flash a custom recovery and reflash the rom
Flash a custom recovery and replace the file
Click to expand...
Click to collapse
Ok thanks. I'm downloading the Rom and I have to flash it through TWRP, flash stock recovery and try OTA update again.

kamso said:
Ok thanks. I'm downloading the Rom and I have to flash it through TWRP, flash stock recovery and try OTA update again.
Click to expand...
Click to collapse
preload data is HTC's little hidden way of stopping you getting OTA's if you unlock your bootloader, and yes it is required to update, without it, updates will fail.

Seanie280672 said:
preload data is HTC's little hidden way of stopping you getting OTA's if you unlock your bootloader, and yes it is required to update, without it, updates will fail.
Click to expand...
Click to collapse
Ah Ok I understand. These are applications that disappear when we unlock the bootloader. I had already installed them there's a long time. As I said my OTA updates passed without problem.

Problem flashing stock Rom in TWRP:
"- Zip signature verification failed
- Error flashing zip"
I don't understand anything, what's happen?

Problem solved and phone updated. Thank you!!!

Haven't been able to update since LMY48I. Trying to get on Marshmallow now.

Okay, I haven't been able to update since LMY48I. Back then I was on stock recovery. Re-locking bootloader and all but still was not able to take OTA (always came up with dead android guy with "Error"). I'll skip the (probably) irrelevant stuff since then and give you the current situation:
Currently unlocked, rooted, with custom recovery. Still on LMY48I. I can't take OTAs obviously, and have tried flashing OTA updates manually with no luck and have tried flashing the entire Marshmallow image and that will not work either (sideload or flashing from internal storage in recovery). Sideload comes up with Closed error (device DOES show up in device list and I can do other things). Flashing from within recovery just says "Failed".
Please help me get to Marshamallow!
Edit: On Project Fi by the way.
Edit 2: Also, I've tried the flash-all script.

Now it says the device is corrupted when I boot up. I can still access recovery. Any help walking me through getting all of the correct firmware and latest build on would be much appreciated.
Thank you.
Edit: Looks like i'm good. I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.

altvisionx said:
......./I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.
Click to expand...
Click to collapse
Flashall.bat stops; only m-bootloader and m-radio are flash. Google's fault. You did the right thing by extracting the images and fasbiot flash them.

You cannot sideload the full factory image or flash from storage. Only fastboot

And just to clarify, you can't take an OTA (sideloading or otherwise) if your phone is rooted, have a custom recovery or a custom kernel (or any other modification to the system). The state of the bootloader (locked or unlocked) does not affect the ability to take an OTA update.