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
I have a Zenfone 5 - T00J and i lost the bootloader on the phone.
This is what happened:
I installed the TWRP2870.
I tried to install a custom rom and it didn't work.
I then tried to unlock bootloader and the phone turned off and never turned on by it self.
So i powered it on and i have lost the boot loader.
If i try to reboot into bootloader i will get a battery with a question mark.
I am unable to get ADB access.
I can only boot into TWRP but i am unable to update the firmware.
If i try to install the original firmware i get this
Code:
error: assert failed: getprop("ro.build.asus.sku") == "TW" return code 8
If i try to install a custom firmware i get this
Code:
This pacage is for device: T00F, T00F1, T00J, T00J1, a501cg ; this device is .
Can anyone help me please.
Thanks.
cjulio said:
I have a Zenfone 5 - T00J and i lost the bootloader on the phone.
This is what happened:
I installed the TWRP2870.
I tried to install a custom rom and it didn't work.
I then tried to unlock bootloader and the phone turned off and never turned on by it self.
So i powered it on and i have lost the boot loader.
If i try to reboot into bootloader i will get a battery with a question mark.
I am unable to get ADB access.
I can only boot into TWRP but i am unable to update the firmware.
If i try to install the original firmware i get this
Code:
error: assert failed: getprop("ro.build.asus.sku") == "TW" return code 8
If i try to install a custom firmware i get this
Code:
This pacage is for device: T00F, T00F1, T00J, T00J1, a501cg ; this device is .
Can anyone help me please.
Thanks.
Click to expand...
Click to collapse
Are you able to flash anything from twrp ?
If yes then get latest twrp by xanwar . And flash it .
Link: https://forum.xda-developers.com/zenfone-5/development/recovery-twrp-3-0-2-0-asus-zenfone-5-t3355749
It is working.
followed this:
https://forum.xda-developers.com/showpost.php?p=67473764&postcount=10
I still don't have the fast boot menu option i get a battery with a question mark
How can i fix this?
cjulio said:
I still don't have the fast boot menu option i get a battery with a question mark
How can i fix this?
Click to expand...
Click to collapse
Charge your phone. You should also try one of ASUS flashtools.
e: unknown volume "/spare"
I have gone trough everything i could find.
but everything hits the same problem.
i run the "Debrick Asus Zenfoen 5" post options
and on the sec_offline_update_image.cmd it does not create the partition spare.
erasing 'spare'...
FAILED (remote: unable to format)
finished. total time: 0.790s
what can i do?
thanks.
Hi! I'm currently trying to revive an LG G6 that I had lying around and was pleasantly suprised that there are recent builds of LineageOS available for the device.
Steps I took:
Download latest build (lineage-19.1-20230529-nightly-h870-signed.zip), boot.img and recovery.img
Installed boot image via `fastboot flash boot boot.img`
Installed recovery via `fastboot flash recovery recovery.img`
Reboot via `fastboot reboot`
Boot into recovery (via Vol Down + Power, Release Power, press power againg)
In Lineage Recovery, choose Apply update and Apply from ADB
Sideload image via `adb sideload .\lineage-19.1-20230529-nightly-h870-signed.zip`
Upload starts but stops at ~47%
Error message shown on phone:
Code:
Supported API: 3
Finding update package...
Verifying update package...
Update package verification took 39,4 s (result 0):
Installing update...
Comparing TZ versions:
Max TZ version: TZ.BF.4.0.1-1865684
assert failed: msm8996.verify_max_trustzone("TZ.BF.4.0.1-176180") == "1"
E:Error in /sideload/package.zip (status 1)
Does anybody have an idea what could be the problem here? I had an older version of LineageOS installed on the device (bootloader is still unlocked), but I completely wiped the device prior to trying to install the latest version.
Thanks!
Hackysack said:
Hi! I'm currently trying to revive an LG G6 that I had lying around and was pleasantly suprised that there are recent builds of LineageOS available for the device.
Steps I took:
Download latest build (lineage-19.1-20230529-nightly-h870-signed.zip), boot.img and recovery.img
Installed boot image via `fastboot flash boot boot.img`
Installed recovery via `fastboot flash recovery recovery.img`
Reboot via `fastboot reboot`
Boot into recovery (via Vol Down + Power, Release Power, press power againg)
In Lineage Recovery, choose Apply update and Apply from ADB
Sideload image via `adb sideload .\lineage-19.1-20230529-nightly-h870-signed.zip`
Upload starts but stops at ~47%
Error message shown on phone:
Code:
Supported API: 3
Finding update package...
Verifying update package...
Update package verification took 39,4 s (result 0):
Installing update...
Comparing TZ versions:
Max TZ version: TZ.BF.4.0.1-1865684
assert failed: msm8996.verify_max_trustzone("TZ.BF.4.0.1-176180") == "1"
E:Error in /sideload/package.zip (status 1)
Does anybody have an idea what could be the problem here? I had an older version of LineageOS installed on the device (bootloader is still unlocked), but I completely wiped the device prior to trying to install the latest version.
Thanks!
Click to expand...
Click to collapse
Look's like someone else had the same exact problem: link, and the corresponding solution: link. Hope this helps!
(I found this solution by searching: "assert failed: msm8996.verify_max_trustzone("TZ.BF.4.0.1-176180") == "1" ")
ethical_haquer said:
Look's like someone else had the same exact problem: link, and the corresponding solution: link. Hope this helps!
(I found this solution by searching: "assert failed: msm8996.verify_max_trustzone("TZ.BF.4.0.1-176180") == "1" ")
Click to expand...
Click to collapse
Hi,
thanks for you reply.
I'm not 100% sure about the terminology: Does bootstack mean kdz file?
If that is the case, I already tried to apply it to the device, but neither LGUP or LGFlashTool did work for me... On top there are so many versions floating around that I'm unsure which of the flashing tools is the right one to use on Windows 11. Do you happen to know where I should look for the latest version of one of these tools? (Besides googling, which as mentioned I already tried )
Hackysack said:
Hi,
thanks for you reply.
I'm not 100% sure about the terminology: Does bootstack mean kdz file?
If that is the case, I already tried to apply it to the device, but neither LGUP or LGFlashTool did work for me... On top there are so many versions floating around that I'm unsure which of the flashing tools is the right one to use on Windows 11. Do you happen to know where I should look for the latest version of one of these tools? (Besides googling, which as mentioned I already tried )
Click to expand...
Click to collapse
I honestly don't know, as I only have a Samsung. If you search for the same thing I did in that thread I linked to there were a few more results, you could check those: link.