Until now i got 4 of ArcaneOS Pixels 4a and can confirm that 2/4 successfully unlocked by (fastboot flashing unlock) command. After that I flash stock Android, than relock bootloader and those two phones works perfect. But last two exactly same as previous do not accept command which i mentioned. So I think i was lucky with first two, 'cause maybe they forgot to disable oem unlock
Thanks for the information, useful. Does anyone know where I might find the correct Qualcomm firehose for the SM7150, or my best approach to extract the firmware from a functioning Pixel4a?It's possible that some have a custom bootloader installed that disables oem unlock and flashing commands by fastboot. If these are regular off-the-shelf 4a's (ie, they don't have some kind of hardware lock on the firmware or EDL mode, and I'm guessing they don't since after all "someone" already got this far with custom firmware), it should be possible to use the qualcomm developer tools (QFIL or QPST) to overwrite the firmware with stock and re-enable flashing and unlock from EDL mode. (Fair Warning: also possible to hard brick it entirely so that it won't power on at all, so be very careful and don't do this on any devices you can't afford to lose entirely, though frankly considering who created this particular ROM you're probably better off with a hard brick than this ROM anyway)
For that you'd need the firehose programmer binary and a stock firmware image to flash. If they are the same hardware you should be able to use the tool to dump the firmware from a working one and download it to the rest once you have the firehose programmer. Unfortunately I'm not sure which one you need for the Pixel 4a, but, it may be the same one as for other 730g chipset devices (SM7150 is the product sku so something like prog_xxxx_firehose_sm7150.bin). See for example, this guide or maybe this, or a lot of other guides on this forum. Those aren't specifically for the 4a, and I'm not sure one exists, but it's probably very similar to the process for other Pixels and especially HTC Pixels (I have successfully done it on a LG-made pixel 2 xl, if I had a 4a I'd give it a shot, mayb I can get one of these on a discount Though again, not sure I want one considering whence they came!
Fortunately I'm currently not in the situation where I need to revive my phone, but I was wandering the same when reading tutorials about this topic. In those tutorials they always use 3 files (as you have stated): the
patchfile. In one of the links you have posted the question about the last 2 files is raised:
Zuke Beug said:
patchfiles not needed since an mbn file is used? Then why do the tutorials always require the triplet?
I have three of these in my possession now.If anyone else gets a phone running ArcaneOS, send me a message
Also, you're famous, OP: https://www.vice.com/en/article/n7b4gg/anom-phone-arcaneos-fbi-backdoor
The FBI reportedly sold backdoored Pixel phones to criminals, and one of those phones found its way to an XDA member.www.xda-developers.com
I think if you use the GrapheneOS installer tool you mentioned here to unlock the bootloader, you should be able to do it. I would suggest trying to use the GrapheneOS tool to unlock the bootloader (don't do anything else with it though). After that, I would suggest live booting TWRP using `fastboot boot YourTwrpImage.img` (don't flash it to the phone's recovery partition since you won't be able to get the ArcaneOS recovery back if you do!).
Have you tried this?
>adb devices List of devices attached 09241JEC228869 sideload >adb shell error: closed >adb sideload open_gapps-arm64-10.0-stock-20210518.zip adb: sideload connection failed: no devices/emulators found adb: trying pre-KitKat sideload method... adb: pre-KitKat sideload connection failed: no devices/emulators found >adb sideload "by4a.setedit22_2018.10.31-18_minAPI11(arm64-v8a,armeabi-v7a,x86,x86_64)(nodpi)_apkmirror.com.apk" serving: 'by4a.setedit22_2018.10.31-18_minAPI11(arm64-v8a,armeabi-v7a,x86,x86_64)(nodpi)_apkmirror.com.apk' (~47%) adb: failed to read command: No error >adb shell settings put global development_settings_enabled 1 error: closed >adb root adb: unable to connect for root: closed >adb shell error: closed
>fastboot --version fastboot version 31.0.2-7242960 >fastboot devices 09241JEC228869 fastboot >fastboot flash bootloader sunfish-rq2a.210505.002\bootloader-sunfish-s5-0.3-7062598.img Sending 'bootloader' (8357 KB) FAILED (remote: 'Download is not allowed on locked devices') fastboot: error: Command failed >fastboot flashing unlock FAILED (remote: 'Unrecognized command flashing unlock') fastboot: error: Command failed