1

I have an old Zte Blade Apex 2 with stock rom TIM-IT and stock recovery that can't start because of Encryption unsuccessfull error.

It can boot in recovery with power + volume+ so as a first step I tried to wipe data and cache but the issue persists.

The original rom is not available anywhere online, but some other provider's ROMs are available (movistar or Micro P UK), I tried to use one of those updates but the updater script will fail because of an assert on getprop("ro.build.product") which differs only by the network operator name. Clearly changing the updater script inside the zip causes "failed to verify whole-file signature" error.

For this device there is a TWRP recovery available but currently it's not installed.

I can run adb sideload (in recovery mode) and adb shell without root (from FTM mode, power + volume-), but trying adb restart bootloader will start the device normally with the encryption error. By booting power with volume+ and volume- together (that should be fastboot mode) the red led is on and the device won't be recognized by Windows 10 (USB device not recognized) while on ubuntu with lsusb I can see the usb device id (which is different from the one in FTM mode allowing adb commands) but the command fastboot devices won't show any device and also trying to manually provide the device id won't work.

Any suggestion to recover this phone?

UPDATE: I started the phone with power+both volume keys, lsusb gives ID 19D2:0112 ZTE WCDMA Technologies MSM QHUSB__BULK. while ./edl.py r recovery r.img keeps printing dots "Waiting for the device". In FTM mode ID 19D2:0500 ZTE WCDMA Technologies MSM Android I could run abd reboot edl but edl.py will return Library.sahara - couldn't find a loader for given hwid and pkhash :( Now lsusb gives 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode) On windows it is recognized by MiFlash so it should be correctly in EDL mode, but how can I flash the TWRP recovery now?

13
  • fastboot mode is not helpful on locked bootloader. you can dump userdata + metadata in EDL mode github.com/bkerler/edl
    – alecxs
    Commented Apr 24, 2020 at 7:25
  • @alecxs I updated the question with the attempt with edl.py, do you know any other tool?
    – David
    Commented Apr 24, 2020 at 13:42
  • forum.xda-developers.com/general/rooting-roms/…
    – alecxs
    Commented Apr 24, 2020 at 13:49
  • 1
    Thank you, but I am a bit lost.. How do I write an xml file for the firehorse programmer? I don't have the actual offsets of the partition table for my phone, can I extract something with the original rom update.zip or with non root shell access? I have seen the Axon7 tool forum.xda-developers.com/axon-7/development/… that probably can be customized with other mbn loaders
    – David
    Commented Apr 24, 2020 at 23:22
  • 1
    Tried other usb ports win and linux,other pc but same result, unable to get this phone in download mode. I have a xiaomi that works with fastboot. I tried some mbn from here github.com/programmer-collection/zte in QFIL with no success. in the meantime I realized that sahara protocol works only in the first 1 minute the phone is in EDL, after it will give sistematic errors and I also learned that QFIL will put the phone from FTM mode to EDL mode automatically. I think I will throw away this old phone, not worth it to invest so much time despite learning interesting things about Qualcomm
    – David
    Commented Apr 26, 2020 at 0:22

0

You must log in to answer this question.

Browse other questions tagged .