Most adb and fastboot commands are marked as unknown. Fastboot is easily accessible. Adb is accessible through Rescue mode.
Graphene webinstaller also did not work.
Graphene webinstaller also did not work.
Last edited:
Looking at the build date, looks like a new netwerk/device. Can't find anything on the internet about this device.i recently bought this pixel 4a with "matrix OS "
very similar to anom
Are you able to enter EDL mode? I can try to help you if you can.Most adb and fastboot commands are marked as unknown. Fastboot is easily accessible. Adb is accessible through Rescue mode.
Graphene webinstaller also did not work.
Adb reboot edl? Or a different way?Are you able to enter EDL mode? I can try to help you if you can.
any way of entering it, doesn't matter. at least on mtk, you can use mtkclient to backup, im still trying to find a firehorse for you. sprd requires a manifest to backup but on qcom i dont know
you can try these files here if you would like, it is from a different device, but same soc, gpu, and cpu as sunfish pixel 4a. i removed the img files as they were large. it comes from https://droidfilehost.com/download/realme-x2-rmx1992-firmware-flash-file-stock-rom/ and was decryptedany way of entering it, doesn't matter. at least on mtk, you can use mtkclient to backup, im still trying to find a firehorse for you. sprd requires a manifest to backup but on qcom i dont know
Nope, just giving me command closed. So another command which is either removed or protected.any way of entering it, doesn't matter. at least on mtk, you can use mtkclient to backup, im still trying to find a firehorse for you. sprd requires a manifest to backup but on qcom i dont know
you might need to short something to get it into that mode then, idk what, i dont own a pixelNope, just giving me command closed. So another command which is either removed or protected.
Short is not an option. Don't want to brick the device. Took a while to find one.you might need to short something to get it into that mode then, idk what, i dont own a pixel
Key-shortcut wat? What's that, you mean holding down Vol - and pluging in the usb when turned off? And why is short not an option, you should be able to exit it anyways. And what about those usb things online where you plug in something and it works (altho idk about it or if its a scam or not)Short is not an option. Don't want to brick the device. Took a while to find one.
I tried the ADB and Fastboot way, no success. I tried the key-shortcut wat, no success.
With "you might need to short something" you are reffering to circuit board right?Key-shortcut wat? What's that, you mean holding down Vol - and pluging in the usb when turned off? And why is short not an option, you should be able to exit it anyways. And what about those usb things online where you plug in something and it works (altho idk about it or if its a scam or not)
1. YesWith "you might need to short something" you are reffering to circuit board right?
Key-shortcut I am indeed reffering to key combination to get the phone into EDL mode.
"And what about those usb things online where you plug in something and it works (altho idk about it or if its a scam or not)" I have no idea what you are reffering to. Any video or link?
Update: Don't use the ZIP I uploaded earlier, I am trying to dump it from the bootloader img file right now, which half of prog_firehose_ddr.elf is actually in the bootloader (bootloader-sunfish-s5-0.2-6281315.img)1. Yes
2. So it doesn't work, I thought so because Pixel's are the hardest to get to EDL unless you flash the wrong FW, which you cant even flash anything. Even Stock Pixel is hard on EDL, Google relies too much on 2nd stage Fastboot which isn't a good if they auto update that.
3. I'm talking about this https://www.ebay.com/itm/322476443357
Try 000e60e10066000a_3ef72a02fb931be1_fhprg.bin I even searched the name up and found 1 result of someone looking for the same file name I generated (hopefully its valid tho)Update: Don't use the ZIP I uploaded earlier, I am trying to dump it from the bootloader img file right now, which half of prog_firehose_ddr.elf is actually in the bootloader (bootloader-sunfish-s5-0.2-6281315.img)
So booting this over fastboot you mean?Try 000e60e10066000a_3ef72a02fb931be1_fhprg.bin I even searched the name up and found 1 result of someone looking for the same file name I generated (hopefully its valid tho)
No, over EDL, if you can get there, using this tool is recommeded if you can handle the command line http://github.com/CE1CECL/edl and doing a complete backup of flash, not just partitions.
If you are using windows use this template if you dont know how to use it (I cant figure out how to embed text so it will be like this for now until i figure it out later)No, over EDL, if you can get there, using this tool is recommeded if you can handle the command line http://github.com/CE1CECL/edl and doing a complete backup of flash, not just partitions.
if you can can you debug where the network for the update api is sending to? Maybe i can debug that while i wait finding a device on ebay, since i cant find anything.If you are using windows use this template if you dont know how to use it (I cant figure out how to embed text so it will be like this for now until i figure it out later)
Command to Run:
git clone https://github.com/CE1CECL/edl
cd edl
git submodule update --init --recursive
pip3 install -r requirements.txt
----------------------
Copy 000e60e10066000a_3ef72a02fb931be1_fhprg.bin to the EDL folder where you cloned it to and then run something like this
python .\edl.py rf arcaneos.bak --loader=000e60e10066000a_3ef72a02fb931be1_fhprg.bin
Just make sure you have python 3.9, git and usbdk from the README of the repo.
If its too large let me know if you need something to upload it with (if you get what i mean), Once i get it i will compress it later.
>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