Database Users

Zenfone 501CG hard bricked, nothing visible only detected as 'CLOVERVIEW'

Hi, I recently tried to unbrick my phone from corrupted bootloader by using xFSTK and basically following this tutorial http://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911. However, the steps given there weren't working well for me, because xFSTK was giving me this error: "XFSTK-STATUS--USBSN:629391F5E045705C--Softfuses Binary absent. Please provide binary.". I fixed it by using softfuse binary (whatever it does) found under this video https://www.youtube.com/watch?v=o-b1sPy8SlI. Apparently, it wasn't the best idea and flashing that messed up my phone so bad that now nothing is even displayed. The only thing that is still working is that it is detected as 'CLOVERVIEW' device when I connect it to my pc and I can flash it using xFSTK. No fastboot, no recovery. Is it still possible to fix this or do I just have a stylish paperweight?

try look there http://23pin.logdown.com/ just search

The tutorial on that blog is exactly the same as here on xda (just translated). Still no luck.

see this post its written by asus guys:
http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800

@quad muffin.........I had this issue several times. It's nothing serious and you just need to make sure you turn off your device. Long press the power button will turn off the device but honestly, it's difficult to understand it's on/off at this situation. Please follow the below instructions:
1. TURN OFF the device
2. Press and hold Volume Up+Power to enter to fastboot/droidboot. When the ASUS logo shows up, release the power button and keep on pressed the Volume UP button. This will take you to droidboot mode.
3. check whether your PC detects the fastboot...
Code:
fastboot devices
if not, go to device manager and install the fastboot driver(by online). if fails, install from the PC by selecting the android device from the list.
4. download this image UL-ASUS_T00F-WW-2.21.40.30-user.zip: http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.61130092.1708615694.1457697474
5. extract fastboot.img, boot.img, recovery.img from the zip file and copy to ADB folder to flash. Copy UL-ASUS_T00F-WW-2.21.40.30-user.zip to ADB folder as well.
6. run the below commands:
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot.....
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. then go to recovery by selecting from the menu
8. in the recovery, select wipe data/factory reset
9. select wipe cache partition
10. select apply update over adb sideload
11. Now check whether your PC detects the ADB over USB. if not, go to your PC's device manager and install the ADB driver online. if fails, install from the PC by selecting the android device from the list.
12. after successful detection, run below command
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
let me know if it works or not. Good luck.

Thanks a lot for the reply, but unfortunatelly a few days ago I sent my phone to asus service and they fixed it by replacing mainboard. But I'm sure the steps will be usefull for people trying to fix their phones in the future.

quad muffin said:
Thanks a lot for the reply, but unfortunatelly a few days ago I sent my phone to asus service and they fixed it by replacing mainboard. But I'm sure the steps will be usefull for people trying to fix their phones in the future.
Click to expand...
Click to collapse
I will post my instruction with debrick soon.

I guess it will help you...
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455/

When "adb sideload <filename>" finished...
"Finding update package...
Opening update package...
Verifying update package...
Installing update...
Device image SKU:
TW
OTA image SKU: TW
Please update to newest 4.3 image first...
Erasing old dictionary...
Updating splash image...
Updating IFWI image...
(SKIP) Updating 3g Module firmware image...
(SKIP) Updating 3G module nvm...
Install from ADB complete."
But still stuck at Asus logo

wernico said:
When "adb sideload <filename>" finished...
"Finding update package...
Opening update package...
Verifying update package...
Installing update...
Device image SKU:
TW
OTA image SKU: TW
Please update to newest 4.3 image first...
Erasing old dictionary...
Updating splash image...
Updating IFWI image...
(SKIP) Updating 3g Module firmware image...
(SKIP) Updating 3G module nvm...
Install from ADB complete."
But still stuck at Asus logo
Click to expand...
Click to collapse
Reboot to bootloader, flash the fastboot, boot, and recovery images from the firmware zip file. Then go to recovery and sideload the firmware again.
Sent from my ASUS_T00J using XDA-Developers mobile app

adb sideload "Zip signature verification failed!"

I'm on a Nexus 6p with resurrection remix (for android 6.0.1) trying to flash back to stock 6.0.1. I've been attempting to sideload angler-ota-mtc20l-095e81f7.zip on TWRP (After wiping Dalvik, system, data, and cache) but it keeps saying "Zip signature verification failed!" in my phone and "total xfer: 1.00x" on cmd. I had a backup which I attempted to restore after this failed several times but this left me in a bootloop. Any solution would be appreciated. If you need more information just ask.

Hskom said:
I'm on a Nexus 6p with resurrection remix (for android 6.0.1) trying to flash back to stock 6.0.1. I've been attempting to sideload angler-ota-mtc20l-095e81f7.zip on TWRP (After wiping Dalvik, system, data, and cache) but it keeps saying "Zip signature verification failed!" in my phone and "total xfer: 1.00x" on cmd. I had a backup which I attempted to restore after this failed several times but this left me in a bootloop. Any solution would be appreciated. If you need more information just ask.
Click to expand...
Click to collapse
You'll have to flash the full factory image, not an OTA. You won't be able to side load or flash from recovery. You can either use ADB to flash the full image with the included flash-all.bat, or a toolkit like NRT.

v12xke said:
You'll have to flash the full factory image, not an OTA. You won't be able to side load or flash from recovery. You can either use ADB to flash the full image with the included flash-all.bat, or a toolkit like NRT.
Click to expand...
Click to collapse
I exactly have the same issue but, if I understand correctly, because my device is locked I'm unable to flash the factory image. My phone got bricked during a system update. I had this issue once and I was able to recover it with OTA sideload. But this time it doesn't work: when I do the OTA sideload it gives me the signature verification error.
How could I overcome it?

D4rkFloors said:
I exactly have the same issue but, if I understand correctly, because my device is locked I'm unable to flash the factory image. My phone got bricked during a system update. I had this issue once and I was able to recover it with OTA sideload. But this time it doesn't work: when I do the OTA sideload it gives me the signature verification error.
How could I overcome it?
Click to expand...
Click to collapse
Hi... More infos would help troubleshooting the issue more efficiently.
What was the initial build before the device got bricked?
What was the build "system update" that bricked your phone? Did you update manually or through a pushed OTA? If manually, how did you flash it /bricked your phone?
Finally, which build did you try to Sideload?

5.1 said:
Hi... More infos would help troubleshooting the issue more efficiently.
What was the initial build before the device got bricked?
What was the build "system update" that bricked your phone? Did you update manually or through a pushed OTA? If manually, how did you flash it /bricked your phone?
Finally, which build did you try to Sideload?
Click to expand...
Click to collapse
Thanks for your help.
My current build before the phone got bricked is N4F26I .
I think the update that bricked my phone was N4F26O.
I applied the OTA from the recovery system by selecting "Apply update from ADB" and then doing an adb sideload.
More info:
– I have tried to sideload the OTA images for N4F26I, N4F26J, N4F26O but for all of them I get the error above (I downloaded the OTA image files from Google page)
– Re-downloaded the files, but no joy.
– Phone is not rooted. It had the stock image
- Device shows as LOCKED. If I understand correctly, when device is locked it's not possible to flash the factory image
- USB debugging is enabled
this is the error which happens when I reach 47% of the sideload:
E: failed to verify whole file signature
E: signature verification failed
E: error 21
Installation aborted.

D4rkFloors said:
Thanks for your help.
My current build before the phone got bricked is N4F26I .
I think the update that bricked my phone was N4F26O.
I applied the OTA from the recovery system by selecting "Apply update from ADB" and then doing an adb sideload.
More info:
– I have tried to sideload the OTA images for N4F26I, N4F26J, N4F26O but for all of them I get the error above (I downloaded the OTA image files from Google page)
– Re-downloaded the files, but no joy.
– Phone is not rooted. It had the stock image
- Device shows as LOCKED. If I understand correctly, when device is locked it's not possible to flash the factory image
- USB debugging is enabled
this is the error which happens when I reach 47% of the sideload:
E: failed to verify whole file signature
E: signature verification failed
E: error 21
Installation aborted.
Click to expand...
Click to collapse
Did anyone ever figure out this situation. I'm in exactly same situation. Can't sideload full ota image, quits in middle with signature verification. Bootloader is locked and device wont boot up to enable oem unlocking.

How to get past
adb sideload "Zip signature verification failed!"​Disable signature verification

xinulhacker said:
Come superare
adb sideload "Verifica firma zip fallita!"​Disabilita la verifica della firma
Click to expand...
Click to collapse
How?

White Signal Bar on ZTE Axon 7 A2017

Hi everyone,
My brother bought an Axon 7 (A2017) from China and because it came without Google package he installed them manually. However, he start having some malfunctioning issue while importing his contacts from his google account. So, I advise him to switch to EU or US firmware and from there our nightmare started!
First we switched to US firmware (A2017U) and for some unknown reason the phone stopped recognizing our SIM. Basically, the phone sees the SIM but we cannot make a call. The signal bar showing ZERO bars at all time.
Moved to EU firmware (A2017G) without a success.
Tried to go back to A2017 without a success.
What do you think has happened?
Currently, we are on A2017-B08 and we have no issue with it but how can we make to SIM to work again?
Regards,
Nawaf

I would install the latest Chinese build, therefore b013. Easy to do, look back in general questions thread. Use a contacts transfer app to transfer contacts. I've got mine fully up and running on Chinese axon 7 b013.

hajjinm said:
Hi everyone,
My brother bought an Axon 7 (A2017) from China and because it came without Google package he installed them manually. However, he start having some malfunctioning issue while importing his contacts from his google account. So, I advise him to switch to EU or US firmware and from there our nightmare started!
First we switched to US firmware (A2017U) and for some unknown reason the phone stopped recognizing our SIM. Basically, the phone sees the SIM but we cannot make a call. The signal bar showing ZERO bars at all time.
Moved to EU firmware (A2017G) without a success.
Tried to go back to A2017 without a success.
What do you think has happened?
Currently, we are on A2017-B08 and we have no issue with it but how can we make to SIM to work again?
Regards,
Nawaf
Click to expand...
Click to collapse
I think you guys installed full US firmware which overwrited CN bootloader and it leads to lost signal. CN device only works with CN bootloader so you have to install full CN firmware.
Download CN B13 full firmware from here
Unzip it to get update.zip file. If you install via "SD upgrade" put this file into root of SD card. You also can install via TWRP.
Let me know if you get this error message :assert failed getprop( ro.product.name) == "P996A03" during installation process.
To sync Google Contact into CN firmware following these steps:
Enable Google Play Service in Apps setting
Install Google Play Store/Gmail in ZTE Market
Run Google Play Store/Gmail it will asks you update Google Play Service
Install Google Contacts Sync from here. It must be 6.0.1 version.
After this you can add Google account and see Google account option in Contact settings.

Greetings all,
Thanks for your prompt responds. I am on the process of downloading the CH firmware (B13) and I will update you with my outputs.
Appreciate your support and kindness.
Regards,
Nawaf

Greetings All,
I just download the CN firmware and upload it into my SD card. When I tried to "Apply update from SD card" and after reaching 25% progress, I end up with the following error message:
Eackage is not for this device AB - g
Installation aborted.
I rebooted the device and did (1) Wipe data/factory reset and (2) Wipe cache partition and tried again, the screen went black after reaching 25% progress. I re-performed Wipe cache partition again and tried it one more, and I end up with above message!
Any suggestions?
When I go to recovery mode, the following data are presented:
Android Recovery
ZTE/P996A04/ailsa_ii
6.0.1/MMB29M/20161124.233247
user/release-keys
One more thing, when I unzip the update file to the check the updater-script, I found this product no. mentioned there: assert(getprop("ro.product.name") == "P996A03");. As you can see the device showing P996A04 and the update file showing P996A03? Do you think this is the reason for the error and how to overcome it?
Regards,
Nawaf

hajjinm said:
Greetings All,
I just download the CN firmware and upload it into my SD card. When I tried to "Apply update from SD card" and after reaching 25% progress, I end up with the following error message:
Eackage is not for this device AB - g
Installation aborted.
I rebooted the device and did (1) Wipe data/factory reset and (2) Wipe cache partition and tried again, the screen went black after reaching 25% progress. I re-performed Wipe cache partition again and tried it one more, and I end up with above message!
Any suggestions?
When I go to recovery mode, the following data are presented:
Android Recovery
ZTE/P996A04/ailsa_ii
6.0.1/MMB29M/20161124.233247
user/release-keys
One more thing, when I unzip the update file to the check the updater-script, I found this product no. mentioned there: assert(getprop("ro.product.name") == "P996A03");. As you can see the device showing P996A04 and the update file showing P996A03? Do you think this is the reason for the error and how to overcome it?
Regards,
Nawaf
Click to expand...
Click to collapse
Don't worry the following trick should fix this issue:
Unzip update.zip
Use Notepad to open \META-INF\com\google\android\update-script
Delete the first and second line:
getprop ( "ro.product.device") == "ailsa_ii" || abort ( "This package is for " ailsa_ii \ "devices; this is a " "+ getprop (" ro.product.device ") +" \ ".");
assert (getprop ( "ro.product.name") == "P996A03");
Save the update-script and zip everything to update.zip rom file. The reason to do this is to remove the safety checks.

Greetings all,
Thalias, thank you again for everything. Unfortuenately, after I did all what you recommend I end up with the following while installing:
E:footer is wrong
E:Signature verification failed
Installation aborted
Did I miss something here?
Regards,
Nawaf

getprop("ro.product.device") == "ailsa_ii" || abort("This package is for "ailsa_ii" devices; this is a "" + getprop("ro.product.device") + "".");
assert(getprop("ro.product.name") == "P996A03");
ui_print("Target: ZTE/P996A03/ailsa_ii:6.0.1/MMB29M/20161027.021856:user/release-keys");
show_progress(0.950000, 180);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("Failed to update system image.");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
package_extract_file("ddr.img", "/dev/block/bootdevice/by-name/ddr");
package_extract_file("echarge.img", "/dev/block/bootdevice/by-name/echarge");
package_extract_file("lksecapp.mbn", "/dev/block/bootdevice/by-name/lksecapp");
package_extract_file("rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("xbl.elf", "/dev/block/bootdevice/by-name/xblbak");
package_extract_file("mdtp.img", "/dev/block/bootdevice/by-name/mdtp");
package_extract_file("xbl.elf", "/dev/block/bootdevice/by-name/xbl");
package_extract_file("cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("adspso.bin", "/dev/block/bootdevice/by-name/dsp");
package_extract_file("recovery.img", "/dev/block/bootdevice/by-name/recovery");
package_extract_file("sec.dat", "/dev/block/bootdevice/by-name/sec");
package_extract_file("NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("pmic.elf", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
package_extract_file("splash.img", "/dev/block/bootdevice/by-name/splash");
package_extract_file("hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");
package_extract_file("cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_dir("cache", "/cache");
set_progress(1.000000);
I remove the two bold lines from the script.

Thalias,
I am still getting the same error message regardless of all my attempts:
E:footer is wrong
E:Signature verification failed
Installation aborted
Regards,
Nawaf

hajjinm said:
Thalias,
I am still getting the same error message regardless of all my attempts:
E:footer is wrong
E:Signature verification failed
Installation aborted
Regards,
Nawaf
Click to expand...
Click to collapse
Are you flashing with TWRP or SD Upgrade?

Thalias,
I am using SD Upgrade.
Regards,
Nawaf

hajjinm said:
Thalias,
I am using SD Upgrade.
Regards,
Nawaf
Click to expand...
Click to collapse
You could try to use TWRP and let me know.

You could try to use TWRP and let me know.
Click to expand...
Click to collapse
Thalias,
The problem I cannot go into EDL mode to install TWRP into A2017G!? I made to many attempts but unfortunately no success.
After confirming that the PC seeing the device with "adb devices" and after sending the command "adb reboot edl", the screen of A2017G went dark BUT the "RED LIGHT" is OFF. Any command I sent I end up with error that the device cannot be seen.
Have you ever experienced this?
Regards,
Nawaf

hajjinm said:
Thalias,
The problem I cannot go into EDL mode to install TWRP into A2017G!? I made to many attempts but unfortunately no success.
After confirming that the PC seeing the device with "adb devices" and after sending the command "adb reboot edl", the screen of A2017G went dark BUT the "RED LIGHT" is OFF. Any command I sent I end up with error that the device cannot be seen.
Have you ever experienced this?
Regards,
Nawaf
Click to expand...
Click to collapse
even if it is dark it is in edl mode, i finished the steps and when i tried to go to recovery mode i failed it will give a black screen like the one with edl mode. and I suffered to bring the mi recovery back. i have the same problem dude "NO SIGNAL!"

You will turn your phone to brick if you keep messing around with locked bootloader.
1. Unlock bootloader
2. Flash twrp
3. Flash right bootstack for your country (A2017U for US, A2017G for world and A2017 for china) - (warning: "Your country" - not "Your phone's country)

Thalias said:
Are you flashing with TWRP or SD Upgrade?
Click to expand...
Click to collapse
I have just removed the two lines, pack into a zip and flash by TWRP but TWRP called "corrupt zip". When I go back the OS, I try to open the .zip file by ES explorer, it can be opened normally, not corrupt!
---------- Post added at 02:25 PM ---------- Previous post was at 02:11 PM ----------
I have solution for this:
1-Copy ORIGINAL .zip file (no removing 2 line like above)
2-Flash Stock recovery by fastboot (you can extract stock recovery: recovery.img from ORIGINAL.zip file)
3-Use updater app from Settings to choose and install the zip file => your OS will be updated
4-Flash back to TWRP

TWRP won't boot

I am attempting to put lineageos on my new Mi A1, following the installation guide here https://wiki.lineageos.org/devices/tissot/install
I have previously installed lineage on my old Moto G LTE and a Samsung Galaxy S4 and have not run into issues.
I have unlocked the bootloader and all that but I can't get twrp to boot.
I boot into fastboot with
Code:
adb reboot bootloader
that works fine, then I
Code:
fastboot boot twrp-3.2.2-0-tissot.img
This seems to have no effect, other than my phone 'disconnecting' from the PC.
I get the following terminal output
Code:
./fastboot boot .\twrp-3.2.2-0-tissot.img
Downloading 'boot.img' OKAY [ 0.682s]
booting OKAY [ 0.623s]
Finished. Total time: 1.336s
However nothing happens on the phone, it still just has the fastboot logo on it.
At this point if I manually reboot (long-press power) it will reboot into stock rom.
If I manually reboot into recovery (long-press power+volume up) it will reboot into stock recovery
I have ensured my sytem tools are up to date, and tried the previous version of twrp, and there is no change.
I WAS able to get twrp to boot using the "Mi A1 Tool" i found here https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857
However I was not able to install lineage due to an error.
I did not copy the exact output but it was something along the lines of
error 7, kInstallDeviceOpenError
After this attempt, I reflashed the stock rom using Xiaomi tools, and am back to the beginning.
The phone is fully up-to-date with stock updates, Android 8.1, July security update.
Once again went through the bootloader unlocking, and everything, but have arrived at the same result.
Anyone have any ideas?
any help would be greatly appreciated!
Thanks!

Hey, could you try this TWRP made for Oreo? https://www.androidfilehost.com/?fid=818070582850498337 (thread: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472)
I've also had some issues booting TWRP, but running
Code:
fastboot oem unlock
was enough to boot it successfully (
Code:
fastboot boot recovery-3.2.1-2-oreo.img
)

Thank you!
dgadelha said:
Hey, could you try this TWRP made for Oreo? https://www.androidfilehost.com/?fid=818070582850498337 (thread: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472)
I've also had some issues booting TWRP, but running
Code:
fastboot oem unlock
was enough to boot it successfully (
Code:
fastboot boot recovery-3.2.1-2-oreo.img
)
Click to expand...
Click to collapse
This recovery image worked great, AND installed lineage, thank you very much.
However, I am now unable to get gapps working.
I was pointed to this changelog here https://lineageos.org/Changelog-19/ by a user in the lineage subreddit.
I rebooted from twrp into the lineage recovery, chose Apply Update -> Apply from ADB
On my PC I run
Code:
./adb sideload .\MindTheGapps-8.1.0-arm64-20180610_024023
.zip
and after a pause I get the output
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: No error
and sometimes I get
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: Connection reset by peer
What happens on the phone has been a little different each time I have attempted this.
It either pops up on screen that it is unable to verify the file, install anyway?, doing so doesn't work.
OR it is hung up on a progress bar screen, with the following log output, or a slight variation of it
Code:
Stopping adbd...
Now send the package you want to apply to the device with "adb sideload <filename>"...
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
E:error: 21 Restarting dbd... Installation aborted.
After many attempts of this, reflashing lineage, and trying again, it did miraculously start doing the transfer at one point. It got to 47% then failed again.

Can't you just install from recovery?
https://forum.xda-developers.com/mi-a1/development/rom-lineageos-15-1-t3757938

pidermin said:
This recovery image worked great, AND installed lineage, thank you very much.
However, I am now unable to get gapps working.
I was pointed to this changelog here https://lineageos.org/Changelog-19/ by a user in the lineage subreddit.
I rebooted from twrp into the lineage recovery, chose Apply Update -> Apply from ADB
On my PC I run
Code:
./adb sideload .\MindTheGapps-8.1.0-arm64-20180610_024023
.zip
and after a pause I get the output
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: No error
and sometimes I get
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: Connection reset by peer
What happens on the phone has been a little different each time I have attempted this.
It either pops up on screen that it is unable to verify the file, install anyway?, doing so doesn't work.
OR it is hung up on a progress bar screen, with the following log output, or a slight variation of it
Code:
Stopping adbd...
Now send the package you want to apply to the device with "adb sideload <filename>"...
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
E:error: 21 Restarting dbd... Installation aborted.
After many attempts of this, reflashing lineage, and trying again, it did miraculously start doing the transfer at one point. It got to 47% then failed again.
Click to expand...
Click to collapse
Hey,
Install GApps also at TWRP. Signature verification is failing most probably because the Lineage Recovery should be accepting only Lineage-signed ZIP files.
You can install TWRP in your current boot image (so you don't need to boot TWRP everytime through fastboot) with this ZIP: https://www.androidfilehost.com/?fid=746010030569959456 (yet, you need to boot to TWRP through fastboot so you can flash it, but no need to boot it manually after installing it). Notice that after every system update you may need to install TWRP again (same for Magisk), as boot images get replaced.
Also, if sideload fails, you can just do a
Code:
adb push filename.zip /sdcard/
then install the ZIP directly from the "Install" section on TWRP.
Thanks!

Thanks a lot!
I found and was able to follow this guide
https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
instead of the one on the lineageOS website, and I am up and running.
Thank you very much for your time!

Can't boot to recovery or fastboot
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt it just reboots normally. Any suggestions on what should I do Please?

Azan Qazi said:
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt. Any suggestions on what should I do.
Click to expand...
Click to collapse
Have you tried doing reboot in the OS and choosing Recovery option?

Azan Qazi said:
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt it just reboots normally. Any suggestions on what should I do Please?
Click to expand...
Click to collapse
TrueMS said:
Have you tried doing reboot in the OS and choosing Recovery option?
Click to expand...
Click to collapse
yes sir I did tried several times. But as I said above it simply reboots the system.

[solved] axon7 A2017G assert failed: axon7.verify_trustzone("TZ.BF.4.0.1-00315") == 1

[solved] axon7 A2017G assert failed: axon7.verify_trustzone("TZ.BF.4.0.1-00315") == 1
Hello,
I’m trying to flash the official LineageOS 15.1 on a Axon7 A2017G phone but I can’t get rid of this error :
Code:
assert failed: axon7.verify_trustzone("TZ.BF.4.0.1-00315") == 1
According to another topic I should “flash the right bootstack” but I don’t get exactly what it is.
I tried to install different versions of TWRP : the one recommended in LineageOS documentation and the latest I could find on the official TWRP website with no success.
https://androidfilehost.com/?w=files&flid=274875
https://dl.twrp.me/ailsa_ii/
Any idea ?
Thank you !

krodelabestiole said:
Hello,
I’m trying to flash the official LineageOS 15.1 on a Axon7 A2017G phone but I can’t get rid of this error :
According to another topic I should “flash the right bootstack” but I don’t get exactly what it is.
I tried to install different versions of TWRP : the one recommended in LineageOS documentation and the latest I could find on the official TWRP website with no success.
https://androidfilehost.com/?w=files&flid=274875
https://dl.twrp.me/ailsa_ii/
Any idea ?
Thank you !
Click to expand...
Click to collapse
You should be using this bootstack:
https://androidfilehost.com/?fid=11410932744536985259
And the TWRP in the LOS original post.

thank you !
here is the official LOS post for who might be interested : https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214
I've put this file on my microSD card and flashed it from TWRP but I probably should have the A2017G modem as well.
https://androidfilehost.com/?w=files&flid=270519
Unfortunately I can't access the recovery anymore. I just can access fastboot, no adb. Flashing TWRP again doesn't change a thing.

I've tried this command :
fastboot flash radio A2017G_OreoModem.zip
though I don't think it's a good idea since it is not an img file... anyway it has returned : FAILED (remote: partition table doesn't exist)
I don't know how I can get back to TWRP, or flash this modem from fastboot...
// EDIT : I'm mistaken : i can boot to recovery / TWRP ... I'm working on it...

argh I have a new error : Create /vendor partition failed.
unfortunately at some point I have used this script and it's probably related : https://forum.xda-developers.com/axon-7/development/tool-party-v0-1-vendor-partition-t3831517
// edit ok nothing to do with this, and this tool works fine btw, I just had to launch the install of LineageOS twice.

krodelabestiole said:
argh I have a new error : Create /vendor partition failed.
unfortunately at some point I have used this script and it's probably related : https://forum.xda-developers.com/axon-7/development/tool-party-v0-1-vendor-partition-t3831517
// edit ok nothing to do with this, and this tool works fine btw, I just had to launch the install of LineageOS twice.
Click to expand...
Click to collapse
The LOS script will create the vendor partition if a vendor partition is not found. Using the party tool might have caused it some confusion, as even using the tool can be flakey sometimes, needing to be flashed a few times to get the proper result.
So are you up and running on LOS 15 now?

yes it's solved ! thank you

krodelabestiole said:
I've tried this command :
fastboot flash radio A2017G_OreoModem.zip
though I don't think it's a good idea since it is not an img file... anyway it has returned : FAILED (remote: partition table doesn't exist)
I don't know how I can get back to TWRP, or flash this modem from fastboot...
// EDIT : I'm mistaken : i can boot to recovery / TWRP ... I'm working on it...
Click to expand...
Click to collapse
that modem file is a flashable, also there isn't a radio partition anyways, it's called modem
Just flash it in TWRP