Hi,
I have a Nexus 7 which won't boot past the colored X.
I have tried to use ADB Sideload to restore the image but get the following error
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/nakasi/grouper:4.1.1/JROO3D/402395:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/nakasi/grouper:4.1.2/JZo54K/485486::user/release-keys"
Installation Aborted
Can anyone tell me where I am going wrong?
I can't get in to the developers options to turn on USB Debugging mode so think this may be the cause? Is there any way I can rebuild my Nexus 7 when I can't get it in to USB debug mode? If so, can anyone give me clear instructions on how to do this.
I also can't find any ROM images for 4.1.1? which is what the error is indicating is the version I had installed?
Any help here would be most welcome
Many thanks in advance
Aquitaine404
You do not need USB Debugging to use ADB while in recovery - that for only when booted into the ROM. You can use fastboot to flash stock image package to restore the stock 4.1.2 ROM.
Sorted!
Many thanks for the reply. I took another look at the fastboot processes and have now managed to restore the Nexus 7 to a working condition!!! :good:
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
[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
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.