Email or username:

Password:

Forgot your password?
Top-level
caleb

@penguin42 all do yeah, the trick is to run "fastboot set_active a" on every boot, this resets the boot counter.

worth noting that i currently just have the op6/6t hooked up (pic related, details in alt text), and I'm only really confident that i could get the op7, fairphone, and Pixel devices up, the others I'm not quite so sure.

the new home for my device farm, a desk with the control PC to the right (pulling double duty as a gitlab runner). The phones are on the desk attached to a barebones PPPS USB hub, each one has a pi pico and a 4.4v buck regulator for control and power.
7 comments
penguin42

@cas Oh, that's nice. Yeh I found out that qcom problem on my Find7 (main phone) the hard way when playing with kernels. What's the 4.4v for? Seems an odd value.

caleb

@penguin42 to replace the battery, both for safety and because it makes power cycling a sub 1 second process instead of a 15 second one

caleb

@penguin42 you might be interested in qbootctl if you're running some Linux userspace, it's a port of the Android bootctl HAL to handle slot switching and resetting the retry count from userspace

gitlab.com/sdm845-mainline/qbo

penguin42

@cas Does that let you recover if you've already got it into the worst recovery mode?

penguin42

@cas Actually; let me more precise - I mean the qcom boot mode that happens before fastboot.

caleb

@penguin42 ohh, EDL mode? There's a tool you can find on GitHub, but it requires having some vendor signed "loader" binary, many of these get leaked so you might get lucky..

It can be quite hard to figure out what's causing that, especially without serial access.

penguin42

@cas Yeh I think that's the scary one; I ended up having to reflash via a windows vm running a dodgy chinese reflashing tool; if I can already get to Fastboot I'm not too scared, it's when it doesn't get that far I worry.

Go Up