I ran "fastboot flash recovery C:\Users\user\Desktop\fixtwrp.img" but it just has main stock recovery with the green robot, red warning icon, and "no command."Your TWRP recovery is brain-dead. I've tried to fix it. Give this a shot.
I can access adb. I just want to put TWRP on it and figure out why non-stock keeps being overwritten. Currently cannot get the super.img extracted at all with anything. Using dynamic but not A/B.Yeah, I missed something there. I was just going to tell you not to bother.
You mean like the bootloader screen, right, not really a recovery screen? It doesn't say Recovery 123.456?
The original recoverytest.img is totally half-baked. It's missing init. I wasn't quite sure if there was a copy in system or what was happening.
I put in all the symlinks that were in the stock recovery.
What's your complaint with the stock recovery? That it doesn't have ADB? We can fix that easier than beating our heads against the TWRP.
Yes, I know that you have ADB when the regular system is booted. But does the stock recovery give you that? What is it about TWRP that you want/need?
I actually did that this morning, haha
you could also request user release source code in compliance to GPL. You can probably pick up in person between 9-5 in Shenzhen office![]()
The EDL HWID tells us that this is a "QM215". Despite hints otherwise, it is no MSM8937.
Qualcomm Technologies, Inc. MSM8953 + PMI632 SOC
Qualcomm Technologies, Inc. MSM8953 + PMI632 SOC
Qualcomm Technologies, Inc. QCM2150
Qualcomm Technologies, Inc. QM215
Qualcomm Technologies, Inc. SDA429 CDP
Qualcomm Technologies, Inc. SDA439
Qualcomm Technologies, Inc. SDM429 MTP
Qualcomm Technologies, Inc. SDM439 MTP
Will this allow TWRP? I'm not sure what "18d1/4ee7" is or means.Well, here's a shot in the dark, a proof of concept (or not). It's a custom recovery.
If it works you should get a white screen, hopefully with text, but I'll accept diagonal whizzes.
If you are lucky you might have ADB on 18d1/4ee7
You can try it fastboot boot or fastboot flash.
No.Well, do you get ADB? Does it bong when you connect/disconnect.
No, this is not TWRP.
Nope. Just sits on UMX boot logo screen for a bit then keeps resetting. No ADB.
Sure is, haha.This stuff is tootoughtedious to do by remote control without even an operating console.
The fix was re-flashing super.img (thank you, PizzaG).
sorry but the files pulled are just garbage. you probably did from windows, right? please remember exec-out is only working from linux. I did not find a way to pull files from windows, yet. please upload to mediafire it's free. also please provide checksums
phhgsi_a64_ab:/ # sha256sum /dev/block/*/*/*/by-name/*
I did it from Linuxsorry but the files pulled are just garbage. you probably did from windows, right? please remember exec-out is only working from linux. I did not find a way to pull files from windows, yet. please upload to mediafire it's free. also please provide checksums
Code:phhgsi_a64_ab:/ # sha256sum /dev/block/*/*/*/by-name/*
phhgsi_a64_ab:/ # cd /storage/????-????
phhgsi_a64_ab:/storage/0815-4711 # mkdir u696cl
phhgsi_a64_ab:/storage/0815-4711 # cd u696cl
phhgsi_a64_ab:/storage/0815-4711/u696cl # for b in $(ls /dev/block/*/*/*/by-name/!(userdata)); do dd if=$b of=${b##*/}; done
phhgsi_a64_ab:/storage/0815-4711/u696cl # sha256sum /dev/block/*/*/*/by-name/* | tee sha2.txt
UMX-U693CL-FireHose_Programmer.mbn
from UMX_U693CL-A-Team-Root_Recovery_Package.zip and see if it works for your device.lsusb
edl --loader='/path/to/UMX-U693CL-FireHose_Programmer.mbn' rl dumps
sudo apt update
once then follow install instructions as descripted here)Factory Loader = Firehose programmer. the Loaders repo is a collection for other devices. "Install EDL Loaders" is for adding own firehose file to collection. you don't need this. just add the--loader
flag to each command pointing to your own loader.
"Device is in Sahara error state, please reboot device" is most likely caused by timeout. some devices only accept initiation during first 30 sec
I installed Xubuntu with my Windows so I can boot into either..bin .mbn .elf file whatever name it has is irrelevant as it will be renamed. dirname doesn't matter you can name it tmp, newstuff, examples just put your file(s) somewhere.
usage is (where~/tmp
is any directory with your own files andLoaders
is existing target dir insideedl
)
Code:cd edl git submodule update --init --recursive fhloaderparse ~/tmp Loaders
your linux is live distro from pendrive? you don't need this as you have to re-install everything on each boot anyway, its temporary linux like DVD so it's pointless.
the only command needed is that from post #2 it's fine to test loaders. it seems like the loader is crashing your phone...
cd edl
git submodule update --init --recursive
fhloaderparse /home/name/edl/newstuff/ Loaders