[Nexus 6P Android Development] Z3R0L1F3:
DISCLAIMER: TO ACKNOWLEDGE THE NEAR-PERFECT USELESSNESS OF THIS SUBMISSION, YOU ARE INVITED TO SKIP TO THE MONEY SHOT:

"MAIN QUERIES FOUND DIRECTLY BELOW DIVIDER LINE AFTER THIS DIVIDER LINE"

v

v

v

==*==*==*==*==*==*==**==*==

@yesimxev longtime lurker/fan. Nothing I can say you don't already know. Extraordinary work..

Ahem. Picked up a $27 Angler ("parts"!) on eBay due to a laughable Oreo FRP + fictitious Vzn lock. This is only my 2nd NH endpoint- pls b gentle 💩

Success booting ur los17.1-based image. Idk was getting the BS vendor error. Lol "fixed" it by rebooting straight back to recovery after 17.1 but before NH. No system. Then again, always thought FDE was /data? I think this is the fix though because all the FW images being alike tested as secondary to stock vendor NEVER booting system, instead re-rebooting to recovery to clean flash fstab/squashfs/NH.. Can't encrypt what it never mounted/parsed 😎

Unfortunately, the battery is bat**** FUBAR. Completely fails as suddenly as 87%. You know the drill.

Anyway, she died when copying your 699Mb android_kernel_huawei_angler_pixel folder (over 39,800 files- wow) via usb-otg. So clearly, that's bad it broke stuff. I got tired of xbin error. And I know that would have been fixed easily with cp here and an mkdir there.. but I said to hell with all of it scorched Earth. Was just going in to take it from the top, when it occurred to me:

If there was a single Android version I found myself on that just absolutely HAD to (if possible) be one version up? For me- Android 10, shrug.. But it seems as tho 17.1 is apparently the last version with published nethunter integration. This is accurate?

Second, I am pretty bummed out for no USB Gadget Tool support. The conspicuous absence of USB Arsenal from the app. kernel_support=false, duh..

The problem I've identified is that there's no support for 3.*.* kernels. Any work around or solution that exists whatsoever, has eluded my search. I've lost the forest for the tree.

Forgive me my stupidness, but if we can update literally any and everything else in this phone's contingent tree, can we not get it to a kernel version 4.*.*? This now bleeds over into the scope of I suppose all things Linux. Maybe I need to get the kernel talk from someone Everything's a file, and arguably just exists for the sake of update. EXCEPT kernel?! 4.0 is older than Angler- it's the only reasonable deduction by its absence..

I DID find a far newer kernel (May'22). It worked. BUT. If it's still same 3.10, & has no bearing on Android or Vendor patch, this really amounts to an update in name only- right? No real sec benefit..

Kernel x.y.z-def_2022 against kernel x.y.z-abc_2020- both having verysame Android+Sec patch means NOTHING(?)

Or am I oversimplifying again? I actually think your older kernel would be preferred in this context- having been vetted by the community at least..

Just regurgitating my crapshoot determinations out loud in hopes that any inaccuracy gets a light shined..

Knowing that will help me move forward with reflashing. Meanwhile, knowing this will help me select a battery. Found a "new" battery at haha I think 57mo (I promise we're still talking about Angler- generally). But Lithium-ion batteries, I *believe*, have quite a lot of shelf life IF stored naked/unattached to their host. Chillin in their climate-controlled packaging, I think they'd lose a percentile a month. If starting with 60%, (big if) they'd still be a few percentiles shy of 0%. So I've no idea whether to select "new" 5yo original stock battery for ~$8

OR

dicey generic clone for >$16 (but with benefit of actually being new).

<<OLD_AF versus FAKE_AF>>

..which of these is the LESSER sin?

If anyone responds to any of this, they have my gratitude. I'm sure you've way more relevant stuff working on in 2024. Shrug maybe I'll write you another book in another 18mo..

==*==*==*==*==*==*==*==*==

<<<To recap:>>>

•any known issues w 2023.4?

•kernel 3.10.* highest stable?

•los17.1 highest stable?

•BATTERY- 'Barnacle' or 'Bootleg'?

==*==*==*==*==*==*==*==*

Thanks again!