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
Related
This may be a noob question but i am concerned that i may have bricked my phone.
I followed this guide
http://forum.xda-developers.com/showthread.php?t=878446
with the exception that i downloaded recovery-clockwork-3.0.2.4-crespo.img
and used that instead of the 3.0.0.0 the guide says to use...
unfortunately when i finish doing the steps in the guide, when i reboot the phone, it's stuck on the google with the open padlock image. I have been waiting 30 minutes and no change.
my phone is a rogers nexus s running 2.3.3.
can anyone help me?
mm144 said:
This may be a noob question but i am concerned that i may have bricked my phone.
I followed this guide
http://forum.xda-developers.com/showthread.php?t=878446
with the exception that i downloaded recovery-clockwork-3.0.2.4-crespo.img
and used that instead of the 3.0.0.0 the guide says to use...
unfortunately when i finish doing the steps in the guide, when i reboot the phone, it's stuck on the google with the open padlock image. I have been waiting 30 minutes and no change.
my phone is a rogers nexus s running 2.3.3.
can anyone help me?
Click to expand...
Click to collapse
If your phone powers on, it isn't bricked...
power up the phone holding the power button and volume up and tell me what happens.
it goes into the bootloader.
saying it is in fastboot mode, and is unlocked.
mm144 said:
it goes into the bootloader.
saying it is in fastboot mode, and is unlocked.
Click to expand...
Click to collapse
Yeah you're fine. Just flash recovery again.
Open terminal
cd to the directory where fastboot is
./fastboot devices (to verify your phone is connected)
./fastboot flash recovery recovery.img (the recovery image needs to be in the same folder you cd to, where fastboot is)
ok then. I downloaded a new recovery file 3025-i9020.img based on this forum:
http://forum.xda-developers.com/showthread.php?t=1031760
and installed the su-2.3.6.1-ef-signed.zip
and it still doesn't go beyond the google and the padlock screen.
in fact, now, my carrier info is wrong. the bootloader detects my phone carrier as att...
mm144 said:
ok then. I downloaded a new recovery file 3025-i9020.img based on this forum:
http://forum.xda-developers.com/showthread.php?t=1031760
and installed the su-2.3.6.1-ef-signed.zip
and it still doesn't go beyond the google and the padlock screen.
in fact, now, my carrier info is wrong. the bootloader detects my phone carrier as att...
Click to expand...
Click to collapse
Okay, so the recovery image is flashing fine.
What model is your phone? Is it i9020?
Flash a stock ROM for your model.
I've been trying to, however, whenever i try to install a rom (any rom) from the recovery...
i get this:
E:connot find misc
finding update package...
opening update package...
installing update...
assert failed: write_raw_image("/tmp/boot.img". "boot")
E: Error in /sdcard/rom.zip (status 7)
installation aborted.
I should also note that i now get errors popping up every time i use a menu item in recovery.
the error stems from can't mount /cache/recovery/last_log
Also i am 100% certain i have a GT-I9020A as i found my manual.
mm144 said:
I've been trying to, however, whenever i try to install a rom (any rom) from the recovery...
i get this:
E:connot find misc
finding update package...
opening update package...
installing update...
assert failed: write_raw_image("/tmp/boot.img". "boot")
E: Error in /sdcard/rom.zip (status 7)
installation aborted.
I should also note that i now get errors popping up every time i use a menu item in recovery.
the error stems from can't mount /cache/recovery/last_log
Also i am 100% certain i have a GT-I9020A as i found my manual.
Click to expand...
Click to collapse
Hmm, that's a weird issue. Go to mounts and storage and make sure everything is mounted. If it still doesn't work, try redownloading the recovery and flash again.
I just wanted to post that i redownloaded recovery and su and did it all over again and it worked. must have had corrupted files. thanks.
mm144 said:
I just wanted to post that i redownloaded recovery and su and did it all over again and it worked. must have had corrupted files. thanks.
Click to expand...
Click to collapse
Great to hear. Make sure to check md5
mm144 said:
in fact, now, my carrier info is wrong. the bootloader detects my phone carrier as att...
Click to expand...
Click to collapse
FYI, it's supposed to say ATT if you have a Rogers phone. It just means the phone is using the AT&T band (same as Telus, Fido, Koodo, Bell, etc). If you have a Wind or Mobilicity Nexus S it will say something like TMO for the T-Mobile band.
Hello all, this is my first post as I've just discovered this site. Loving it so far!
I'm new to Android, as I sold my iPhone 4 for an Xperia Play (couldn't resist the controller)
Anyway, I'm trying to install a custom rom, I rooted the phone no problem but I keep encountering errors when trying to install the rom here: http://forum.xda-developers.com/showthread.php?t=1128216
Where I get confused is in the tutorial:
to flash cm7 rom you have to take 3 steps (after unpacking the 7z archive)
step 1 - copy update.zip to sdcard
step 2 - flash new kernel (always use the kernel provided in CM7 / it is incompatible with stock ROM)
ON PC - run flash_kernel.cmd (an black window will open and will stay open untill kernel is flashed)
ON PHONE - put phone in fastboot mode (power off then press lower right key and plug usb cable) and phone LED will light BLUE
step 3 - when phone is booting (first 5 seconds) press volume key several times to enter recovery and choose apply update from sdcard
WARNING - if you used another rom (stock or custom) you have to wipe data or device will not boot
Click to expand...
Click to collapse
I'm happy to admit I'm a complete noob with android, so could someone with more experience please go into more depth with the instructions?
For example:
ON PC - run flash_kernel.cmd
Click to expand...
Click to collapse
When I unzip the 7z file there's no file called that there, just update.zip and boot.img.
step 3 - when phone is booting (first 5 seconds) press volume key several times to enter recovery and choose apply update from sdcard
Click to expand...
Click to collapse
Does this mean that a recovery mode is installed when the kernel is installed or would I need to install a recovery mode beforehand?
Any help is appreciated, I really want to install this custom rom!!
Thanks in advance!
Boot into fastboot, type fastboot flash boot boot.img then boot into recovery and install from sd the update.zip
Okay, I've tried that and I get the error:
assert failed: getprop("ro.product.device") == "zeus"
getprop("ro.build.product") == "zeus"
etc...
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
Any ideas whats causing it?
when it checks device compatability it fails, a lot of us are having htat problem, don't worry, ver 14 should fix it
Awesome, glad to know it wasn't something I did. Any idea when v.14 might come out? I've literally only discovered the site so I have no concept how often it gets updated
Many thanks!
Edit: new problem, I'm trying to flash the old boot.img but keep getting this error:
(bootloader) S1 partID 0x00000003, block 0x00000280-0x0
FAILED (remote: Image won't fit, partition too small!)
The only reason I want to revert is because my wifi has stopped working, so if anyone knows how to fix that instead please let me know!
This thread has a fix for wi-fi: http://forum.xda-developers.com/showthread.php?t=1128272
Thanks, but for some strange reason my sms isn't working either, it keeps hanging on "sending" for ages. Any way of reverting back to the the way the phone shipped, basically just reset it back ti defaults?
And no, im an idiot and didn't make a backup
Use the 2.3.3 FTF with Flashtool, it will bring your phone back to the standard UK version.
Quick update, successfully flashed the generic firmware back and everything's working fine, however I'm having problems with the built-in games (Bruce Lee, Star Battalion etc)
I'm thinking it might have something to do with the modified boot.img I flashed, if so would anyone know where I could find a generic version I could flash?
If not, does anyone know what might be causing it?
Thanks again, and sorry for the noobish questions!
Edit: Just flashed the boot.img from here: http://forum.xda-developers.com/showthread.php?t=1073624 but still have the problem with Gameloft games... Any suggestions?
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
SuperDizor said:
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
Click to expand...
Click to collapse
I used to be difficult to use TWRP menu, then the menu advanced Wipe Wipe then select all topics except the MicroSD and then manage Otg Wipe it !! Flash Stock Recovery to be done to make Flash official rom first official rom files onto the MicroSD example, I was. UL-ASUS_Z012D-WW-13.20.10.79-user. To change its name Then insert the MicroSD MOFD_SDUPDATE Recovry Mode, then select update to zip and then choose File. "MOFD_SDUPDATE.zip" I will wait a little longer for the update firmware and set up virtually everything is not lost through the OTA.
ผมเคยเป็นแก้ไม่ยากใช้ TWRP แล้วเข้าเมนู Wipe แล้วเข้าเมนู advanced Wipe ทำการเลือกทุกหัวข้อ ยกเว้น MicroSD และ Otg แล้วจัดการ Wipe ครับ!! เสร็จแล้วให้ทำการ Flash Stock Recovery เพื่อที่จะใช้ Flash official rom ก่อนอื่นทำไฟล์ official rom ลงไปยัง MicroSD ผมยกตัวอย่างเป็น UL-ASUS_Z012D-WW-13.20.10.79-user ให้เปลี่ยนชื่อเป็น MOFD_SDUPDATE แล้วนำใส่ MicroSD แล้วเข้า Recovry Mode แล้วเลือก update to zip แล้วทำการเลือกไฟล์ "MOFD_SDUPDATE.zip" แล้วรอสักพักอาจจะนานหน่อยเพราะเป็นการ update firmware ข้อมูลและการตั้งค่าทุกอย่างจะไม่หายเสมือนอัพผ ่าน OTA
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
SuperDizor said:
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
Click to expand...
Click to collapse
I got the same issue, where did you get these files?
roosevelt84 said:
I got the same issue, where did you get these files?
Click to expand...
Click to collapse
I have the exact same error. Same here. Please someone can post download link.
SuperDizor said:
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
Click to expand...
Click to collapse
I found a solution, and now my ZF3 is working but its showing a second screen with a error when it boots.
1 - download a zip file rom from asus site
2 - open it with winrar or another of your choice
3 - go to \META-INF\com\google\android
4 - open the updater-script with a text editor
5 - search for all the words WW_Phone and replace it for omni_ze552kl
6 - save the change and close, update the file inside the compressed zip
7 - put the zip rom inside your phone and flash it through twrp, done!
*sorry about english, its not my native lang.
Hi SuperDizor,
The issues you are having are both caused by the installation of TWRP 3.0.2. that was compiled for the Zenfone 3 using omni_ze55kl as the device type instead of WW_ZE552KL or CN_ZE552KL. I assume that the person that compiled it tried to make TWRP as universal as possible (instead of making two different versions, one for each device type - the TWRP code would have been the same except for this string...). However, the updater checks for this device type string and fails (unless you modify the updater config file as described in the post above). This is also why flashing stock recovery solved your issue.
The second error message you have, the one with dm-verity not being in enforcing mode was caused by having you install TWRP and allowing it to modify the system partition. This was necessary in the past but not anymore. When you flash TWRP, the first time you start it, it ask for your permission the make the system read-write, and you should refuse, as TWRP will function anyway and you will not get the dm-verity error. The dm-verity thingy is a software module in the bootloader (aboot to be precise) that checks the integrity of the system partition. TWRP has to force it in non-enforcing mode since it modifies the system partition and your device would not boot if it left dm-verity in enforcing mode. When you don't let TWRP modify the system partition (ie staying read-only), it does not change the dm-verity mode and you don't get warning messages. Don't worry, TWRP will still enable you to root your device and do whatever it does even if it is in "read only" mode.
Hope this helps !
I just got this error seemingly out of the blue on my ZenFone 3 Laser. I didn't do anything, just walked up and it was showing this screen
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
Haven't rooted, unlocked bootloader, or tried to install any rom manually.
Same happened with my device too. How did you fix it? Can you please let me know the procedure for same.
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
Niemer said:
I just got this error seemingly out of the blue on my ZenFone 3 Laser. I didn't do anything, just walked up and it was showing this screen
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
Haven't rooted, unlocked bootloader, or tried to install any rom manually.
Click to expand...
Click to collapse
Same happened with my device too. How did you fix it? Can you please let me know the procedure for same. Thanks
SuperDizor said:
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
Click to expand...
Click to collapse
but how to flash? its not booting in recovery mode.
Hello, I am in bad shape, this never happened to me before,
I own a A2017G and I tried to go to Nugart. But every thing went south and FUBAR.
I do not know how to fix it. The problem is that I cannot do a adb reboot edl and option 2 pushing +- does not get me into EDL either.
Therefore I cannot instal TWRP and I have the stock and I get the linux pinguin.
1. I tried to upload into the sd card a update.zip with a stock 09 but the Stock TWRP tells me that I cannot install from SDcard
2. I go to install through ADB , and that gets me into sideload.... however every file I try to update which is large 2.5gig fails and the small ones (recovery.img in a zip) tells mes that I have the wrong header.
What can I do?
Is there a way of sideload twrp???
Thanks for any support!!!
The error I get when uploading a Zip through TWRP from ADB:
Finding update package...
Opening update package....
Verifingy update package....
E: footer is wrong
Update package verification took 0.0 s (result 1)
E: Signature verification failed
Instalation Aborted
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
marcus.linkenbach said:
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
Click to expand...
Click to collapse
I new te risks.. I am willing to brick... Done it 1000 of times in my first xperia x10, xperia Z2 and ZTE axon 7...just the first time I do not know if to fix it...
If I just get into edl.... No pain no gain
Let me know if it worked for you.
marcus.linkenbach said:
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
Click to expand...
Click to collapse
Like always there is away, knowledge is the power to do things that others cannot
j77moduss said:
Like always there is away, knowledge is the power to do things that others cannot
Click to expand...
Click to collapse
The magic words... Usb modified cable.. Deep flash cable...
This will allow me to get into Edl and re flash TWRP and flash a zip and be safe...
Knowledge is blitz!!!
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.