axon 7 rootjunkie 5 steps to bootloader unlocking and rooting issue - ZTE Axon 7 Questions & Answers

Hi I have a chinese a2017 which gives an error when i upload via SDcard the first file from root junkie's 5 step walk-through for bootloader unlocking etc. Oddly, the file uploads to 25% (from SDcard) and then aborts the installation due to an issue verifying the "entire" file iirc. More strange is that when the phone boots up fully, it reports that the system has been changed to the firmware that is uploaded and nothing seems wrong except for the error that was previously reported.
My question is is it safe to continue on with the other steps after this error? I would think not but it almost seems as if the error might be a fluke. Thanks in advance!

Related

[Q] 4.2.2 Update Error Help

So My Nexus 7 is simple Stock android 4.2.1 with root and i go to update to 4.2.2 and i get a error (The red triangle one)
Can anybody help i hear there are others with this same problem but yet to find somebody with a solution, do you think i should unroot and relock the nexus and try and update again or just reflash back to stock image
That screen sounds a bit like the stock recovery, not a custom recovery as one would expect with a rooted device. Please explain.
The error that occurred is given in the recovery log file - /cache/recovery/recovery.log
Please report what the error was. If you actually have root in the ROM you should be able to view this file.
No need to relock your boot loader - that is unrelated and relocking it only complicates things.
One more thing - OTAs are not designed to be robust in the face of and arbitrarily reconfigured ROM. It is unreasonable to expect that they will work correctly on a rooted device. They are meant for 100% stock devices, PERIOD. While you may not remember explicitly changing something, if you gave root privilege to an app, that app might have changed things which cause the problem that occurs. On this forum, there have been claims that Stickmount, Beats Audio, and even Titanium Backup can cause these sorts of problems.
bftb0 said:
That screen sounds a bit like the stock recovery, not a custom recovery as one would expect with a rooted device. Please explain.
The error that occurred is given in the recovery log file - /cache/recovery/recovery.log
Please report what the error was. If you actually have root in the ROM you should be able to view this file.
No need to relock your boot loader - that is unrelated and relocking it only complicates things.
One more thing - OTAs are not designed to be robust in the face of and arbitrarily reconfigured ROM. It is unreasonable to expect that they will work correctly on a rooted device. They are meant for 100% stock devices, PERIOD. While you may not remember explicitly changing something, if you gave root privilege to an app, that app might have changed things which cause the problem that occurs. On this forum, there have been claims that Stickmount, Beats Audio, and even Titanium Backup can cause these sorts of problems.
Click to expand...
Click to collapse
And how do you fix this? I have the same problem. I guess you need a different file then the OTA one. Where do you get this file?
Thanks!
MatthiasSchuetze said:
And how do you fix this? I have the same problem. I guess you need a different file then the OTA one. Where do you get this file?
Click to expand...
Click to collapse
Ummm... you are forcing me to guess about your situation. You are rooted, but also do not have a custom recovery installed?
What error message do you find in the /cache/recovery/recovery.log file? Please do not simply say "Status 7", report the FULL ERROR message.
As I said, the OTAs are meant to be used with pure stock ROMs, not customized/rooted ROMs. There do not exist an infinite array of OTA file variations corresponding to a fix for the exact problem you are experiencing, unless you were to create one for yourself by unpacking the OTA zip file and hand-editing the META-INF/com/google/android/updater-script file to skip over the problem you are experiencing.
And if you did that, you would certainly need to use a custom recovery to install it, as doing the operation described above would break the signing of the OTA package, so the stock recovery would refuse to install it.
The other alternative which allows you to use the unmodified OTA is to "fix up" a customized ROM by manually replacing all files that were removed or altered with their original stock versions. This process seems almost as ridiculous as the scenario described above, as now you are purposely breaking the modifications performed by root-aware apps (Stickmount? Beats Audio? Titanium Backup?)
The amount of effort this whole process will take is variable depending on how much stuff has been changed since you rooted. When the OTA performs it's checks prior to beginning it's patching operations, it halts on the first check which fails. Which might mean that you will need to iterate several to many times the process of:
- run the OTA, look at the error in /recovery/log/recovery.log
- hand patch the file involved
- re-run the OTA.
Doing the above can be problematic if you have changed multiple framework files - if you replace stuff one file at a time it is possible to wedge the OS because of dependency issues.
The only good news here is that because the OTA runs all it's checks before it patches anything, it is safe to run it as many times as you can tolerate. (On tilapia devices, though there is evidence that using custom recoveries is almost never a good idea if you want the radio firmware to be updated correctly).
A wholly better idea is to simply start over. Make a full Nandroid backup of your current ROM. If you want, you can also experiment with backup/restore apps like Titanium Backup and/or Carbon.. Then you install a pure stock ROM from the Google Factory images, and begin re-customizing all over again, as if you had just bought the tablet.
If you don't like the result, restore your Nandroid backup. That's what backups are for.**
good luck
** its a good idea to get copies of your Nandroid backups off of the device, as there are various ways that the entire /data partition can get wiped - including the psuedo-SD card containing all your precious backups. You've been warned.
First of all. Thanks for the quick response. Secondly, I get this error on both my nexus devices. The Galaxy Nexus and the Nexus 7. Though I don't know if it is exactly the same error - it is very similar (with the android guy on its back and the red triangle). I have a picture of the error message that comes up on the Galaxy Nexus. Both devices have an unlocked bootloader and a custom recovery. The Nexus 7 is deffinitely rooted with the Galaxy Nexus I'm not sure - I thought so but Titanium Backup doesn't let me backup anything and I don't have a custom ROM running on the phone.
So if I understood you correctly I should go back to the stock recovery and unroot it as well and then try it again?!
Why is the picture that I attached not showing?
This is the error message:
ClockworkMod Recovery v6.0.1.9
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation update...
Verifying current system...
assert failed: apply_patch_check("/system/build.
prop". "THEN A WHOLE LOT OF NUMBERS AND LETTERS")
E: Error in /cache/07501b11ad3b.signed-yakyu-JDQ3
9-from-JOP40D.07501b11.zip
(Status 7)
Installation aborted.
I rechecked it for the Nexus 7. The message is slightly different:
assert failed: apply_patch_check ("/system/lib/libSR_A
udioIn.so", "THEN THE NUMBERS AND LETTERS AGAIN")
E: Error in /cache/6ece895ecb23.signed-nakasi-JDQ39-fr
om-JOP40D. 6ece895e.zip
(Status 7)
Installation aborted.
Now, it does show (the picture). Nice.
MatthiasSchuetze said:
First of all. Thanks for the quick response. Secondly, I get this error on both my nexus devices. The Galaxy Nexus and the Nexus 7. Though I don't know if it is exactly the same error - it is very similar (with the android guy on its back and the red triangle). I have a picture of the error message that comes up on the Galaxy Nexus. Both devices have an unlocked bootloader and a custom recovery. The Nexus 7 is deffinitely rooted with the Galaxy Nexus I'm not sure - I thought so but Titanium Backup doesn't let me backup anything and I don't have a custom ROM running on the phone.
So if I understood you correctly I should go back to the stock recovery and unroot it as well and then try it again?!
Why is the picture that I attached not showing?
This is the error message:
ClockworkMod Recovery v6.0.1.9
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation update...
Verifying current system...
assert failed: apply_patch_check("/system/build.
prop". "THEN A WHOLE LOT OF NUMBERS AND LETTERS")
E: Error in /cache/07501b11ad3b.signed-yakyu-JDQ3
9-from-JOP40D.07501b11.zip
(Status 7)
Installation aborted.
I rechecked it for the Nexus 7. The message is slightly different:
assert failed: apply_patch_check ("/system/lib/libSR_A
udioIn.so", "THEN THE NUMBERS AND LETTERS AGAIN")
E: Error in /cache/6ece895ecb23.signed-nakasi-JDQ39-fr
om-JOP40D. 6ece895e.zip
(Status 7)
Installation aborted.
Now, it does show (the picture). Nice.
Click to expand...
Click to collapse
On both devices the files do not match the expectations (assert failed), i.e those files are not the original ones the OTA is expecting -> You need to re-apply the original files to your ROM before you can apply the OTA or you need to do flash the 4.2.2 system manually, which probably might be the easier solution.

Post Your Current or Last Boot Issues here (READ BEFORE POSTING PLEASE)

Hi A7 users,
Let's start this off be saying, bare with me English is not my primary language.....
OK now, the reason for this Thread is to find a definite solution for current users and future users who have run into boot issues cuz they were trying to :
A- Go back to Un-rooted and lock bootloader state.
B- Started Playing with root tools and make a huge mistake
C- Started playing with twrp not knowing what they were doing
D- All the above + started flashing images files and got worts.
E- Any other type of situation.
I Know we make mistakes and we learn from them and well here today we are going to try or rather say Find a permanent /define solution to all this issues with your help, so PLEASE ONLY POST IF YOU HAVE RUN INTO ANY OF THIS ISSUES AND HOW YOU GOT INTO THE ENCHILADA ( MESS ) .
If you have the solution to your previous boot problems send me a PM and I'll keep this Thread updated for everyone to see with your solution and of course credit to the user/s.​
NOTE : Please mention which Axon 7 you are using e.g. :
- A2017 (Chinese Variant)
- A2017U (USA Variant)
-A2017G (UK/Europe/International Variant)
reserve 1
reserve 2
reserve 3
reserve solution 4
reserve solution 5
Anyone this issues please post you issue, how to got into the problem, device model and if you got it fix let us know.
https://www.youtube.com/shared?ci=05LD4Ja-h3k
You'd think with all the other posts about problems there'd be something here by now.
Always thank those who are helpful...and just ignore those who aren't.
Mine happened when I wiped Internal storage from twrp. This caused the phone to only see 4gb of internal storage. Came to xda and it was suggested to flash back original boot.img. once that was done 4gb issue was fixed and the radio was gone.
I did indeed try every solution offered (thanks again for all the effort, DrakenFX and others). But, I've come to the conclusion that this is not going to get fixed until XTE releases US images. For other people's sake I hope I am wrong, but I myself decided to proceed with the exchange where I bought it, as I was right at the end of my 14 days (newegg doesn't seem to give the 30 days that xte does). I may be out of an Axon 7 for a while, so for now I am on my amazon ads, Blu R1 HD (with ads defeated
Is there a guide to go back to stock for the A2017G?
i'm on B02 with root and the bootloader still locked.
Like to go back to stock now that ZTE is working on an update to give the A2017G an unlocked bootloader.
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
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");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
aPexalpha said:
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
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");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
Click to expand...
Click to collapse
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
I am was rooting my axon a2017 on b10 chinnese version without any backup after rooting got password screen after boot then i was do factory reset and format data and all looking good but after that i saw that i dont have google play app so i installed macro gapps 6.0 after flashing phone stuck on axon screen (after zte logo) for long time i been wait up to 30 minutes and nothing was done..also i have the message on twrp about the modification(dont understand why i have this message all the time) i saw in xda forum that need to install supersu so i search on internet and was flash super su 2.65 and then when i am was boot device go to zte logo screen and then turning off when i connect the device as mtp device named as a2017u (whats worng with it??? I was flashed b10 root boot.img)
I regret about this root and want to back all to stock without any problems need help from someone
I need stock b10 boot.img if someone can upload
Many thanks!
---------- Post added at 04:23 AM ---------- Previous post was at 04:11 AM ----------
DrakenFX said:
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
Click to expand...
Click to collapse
Its will help me too i think
Dear All,
ZTE Axon 7 A2017 (Chinese version) Stuck on Bootloader mode.
Device after power on will Stuck on ZTE logo even power button press longer also will Off and came back to square one and the only way to power off is via selection on bootloader page via volume button which consists of Recovery mode, Power Off, Bootloader and some other mode which I can't recall.
History of this issue. Please bear with long story.
Manage to install MM ROM with B13 via sd card installation via update software in phone setting. follow by Unlocked bootloader and Install TWRP 3.1.1.0 then try few different ROM until one day when I use Xiaomi flashtool my PC crash half way through during flashing resulting in device with Pure Chinese ROM and TWRP also got corrupted, when I said corrupted because I install TWRP 3.1.1.0 but when I go to Recovery mode it shows TWRP 3.0 something. with this corrupted TWRP when I try to install ROM it will show loading but end result is NIL meaning same ROM nothing change.
Until this stage I never did a TWRP backup because all this while the ROM is Not my type of ROM from this junction when I boot back to TWRP and I did Advance Wipe most of it except external sd card thinking that I may be able to install fresh TWRP but my Recovery TWRP is residing in phone storage resulting in No more TWRP recovery software. next thing I did was I connect phone to PC and ran adb fastboot tool to detect device and managed to detect device in recovery mode and I make decision to Locked back the bootloader and did just that and Locked bootloader is Succes and it also Erased everything during the process.
To cut short the story after Locked back bootloader only Bootloader mode is accessible and when I connect to PC and enable Recovery mode (Black screen) and EDL mode (Black screen) from Windows PC Device Manager COM port able to see Qualcomm 9008 for this 2 mode.
I must admit after few days of trying to resolve this Stuck Bootloader issue I almost give up.
Then I remember this Woodo magic by jcadduno which recommends XM flashtool version 2016.08.30.0 but unable to flash after trying few version Xiaomi flashtool and the very latest and I mean from Xiaomi Flashtool webpage http://xiaomiflashtool.com/
version 20170425 that break the ice and finally able to load A2017U ROM because this US ROM my phone No Network detected.
From here onwards I unlocked bootloader and install back TWRP (Installation of TWRP via Axon7toolkit) because of Network issue since I got TWRP I install back A2017 ROM but still Not satisfied because Chinese ROM certain Apps having issue because of Google services and I chance upon this Conversion A2017 to A2017U ROM (Hybrid ROM caused ROM is US and Modem from Chinese Modem)
that I'm stay put right now and my phone now is A2017U model.
I hope this experience can help others with similar Stuck bootloader and those who wish to convert A2017 to A2017U ROM.
below is the link that I described Woodo magic.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Straight forward Axon7toolkit, please don't use Chrome browser cause Chrome will Automatically Delete it after complete download for my case I used Microsoft Edge.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
below is the link to Hybrid ROM for A2017U
https://androidfilehost.com/?fid=457095661767154458 by Michael Warner After flash install No verity patch for the bootloader.
Cheers.
I am stuck in a position where I can restore my nandroid backups but get Error 7
when trying to reinstall any Rom on a2017u I was able to fix the unlocked bootloop
by the EDL method. The Rom's are the same as the backups. I think I tried to role back to B29 Causing the bootloop) and have had problems ever since.
Should I try flashing A2017Uv1.1.0B32_Bootstack_by_DrakenFX since the Rooms are all B32?
The B15 and B19 Nandroid's still Restore fine.
Hello all,
i don't get onto forums very often but i thought this was a nice one to add to. i've rooted a few motorolas, a few ztes, a cat; i've also bricked those ztes, cat & a few samsungs. i'm dealing with two Axon7U's; one is factory MM-b29, the other is N-b35.
while screwing around with TWRP, i bricked the b35 (the b29 has been bricked for a month at this time) after i had it almost perfected. by perfected i mean a custom recovery & root user access fully acquired. with DrakenFX's {YOURS; thanks so much. i'm learning to get along with linux} extensive files created to save people from themselves i was able to unbrick the b35. albeit its CELLULAR DATA became unhinged; that's something i could've lived with except it was a loaner and had NO CAMERA! it's camera (along with the ability to push both volume buttons at once for say EDL mode...) was damaged having been beaten across a steering wheel several times. so with my newfound unbricking superpowers i decided to take another crack at the b29. managed to get it unbricked but couldn't get it setup with both TWRP & SuperSU without losing one, the other or, both. at times it didn't even boot up. i was doing pretty much everything cited above for reasons 'why'. best way to learn is by trial & error (if one can afford it).
the b29 is rooted right at this moment; i'm working on it as soon as i leave this posting. i used Axon7_EDL_Tool. i used Axon7root. i used MiFlash. i used Fastboot. I used ADB App Controller software too. back & forth i fought for three days mostly due to downloading glitches and i prevailed. i manipulated a stock OTA full system update.zip by happenstance and it Auto_Updated over itself. in other words it already had the same ROM installed. i don't know what it tested to realize it needed to update to what it already had. it didn't have CELLULAR DATA either. just like the b35, it broke somehow while flashing TWRP or SuperSU. funny thing is it still wanted to update that same ROM after it did. while perusing the system update setting(s) i noticed it had downloaded N-b15 and it wanted to update b29 AGAIN! i opted for the Nougat update. it did alright and appears to have fixed it's CELLULAR DATA too. i haven't looked at it since but i'm confident i can gain root user access with a minimal amount of effort.
The main problem i've had with dealing with bricked devices is the age of the file downloads. most of them are simply GONE!, expired links and whatnot. if i'd had a clear path say from a custom recovery and rooted boot image of my factory version or the path that leads to it, i'd have been fixed up long ago. i've found partial 'paths' if you will that almost get me there but no quite all the way. flashing images & zips through fastboot are different from their counterparts entered through TWRP or Emergency Download Mode which of course are both different too. three different ways to get into one's phone makes it almost impossible to keep them perfected.
i'm not sure i did what i'm supposed to regarding this thread. Thank you DrakenFX for your time & knowledge; you've saved my old Axon7!
Hello all update;
b35 Nougat phone is retired. b29 managed to update itself to b35 7.1.1. however, its CELLULAR DATA is still broken. i haven't managed to figure out how or where it's broken so i cannot fix it.
what i'm trying to do now is flash Magisk instead of SuperSU and using a TWRP version 3.0.3-1. heck i've used all of TWRP's versions in my efforts to reacquire CELLULAR DATA.
crazy part is the phone knows its CELLULAR DATA carrier and freely displays all of its hookup info. this is very frustrating.

How do I update to Android 7.0 on the Axon 7 (USA Model) with TWRP Recovery installed

I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29
Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Only use ota if you don't want twrp/root anymore.
Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2

Asus Zenfone Selfie ZD551KL cannot flash any ROMs or restore recovery. TWRP installed

Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?
Did you fix your problem cause I fix mine my device can boot to fast boot mode if you
Did you fix your problem cause I fix mine my device can boot to fast boot mode if yours can I will send you the original recovery boot manger then download the latest firmware from the official webpage the go to bootloader and update the file it will work for sure but now have a software touch problems I tried to change theme and enable gloves mode it worked fine for a little time
Same issue..
Hey Lobstercat,
I am having the same problem as you..
I have tried TWRP (format /cache, /dalvik, /system and /data) with an unlock bootloader from an Asus Selfie. I have made a backup of it before trying the above. TWRP was able to restore the UL-Z00T-WW-1.12.40.382 OS fine.
But when install through TWRP, on UL-Z00T-WW-1.13.40.661-user.zip, it gives up on authentication, of which I also turned off with the same result.
In sideload mode it failed with the following message;
sudo adb sideload UL-Z00T-WW-1.13.40.661-user.zip serving: 'UL-Z00T-WW-1.13.40.661-user.zip' (~79%) E: fota_return_code 408
I have also tried "sudo fastboot flash system system.img" it failed, with the message "system.img was too large" this rendered my device unbootable and TWRP cannot restore the backup grrr..
I have the latest fastboot and adb from google went through the same above procedure with the same result, TWRP terminal shows files which I cannot be deleted with rm -rf command
I need to update with the OTA updates to UL-Z00T-WW-1.15 from Asus first before moving over to LOS.
Lobstercat said:
Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?
Click to expand...
Click to collapse
Resolved..
I was able to sort it out through this link.
https://forum.xda-developers.com/zenfone-2-laser/orig-development/rom-cyanogenmod-13-0-t3317515
"In order to update your firmware to MM one you can either flash ASUS MM rom in stock recovery or flash a package that will update your fw which you can download right here"
Download that link, sideload it with no issues and lineage OS 14 with no issues.
Now running Lineage OS 14. Damn its quick!
Getting failed to mount'/persist'(invalid argument) while flashing custom rom lineage
Lobstercat said:
Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?
Click to expand...
Click to collapse
I am on latest version of TWRP have done all the process
unlocked bootloader
Rooted my phone
On latest version of TWRP
Official lineage os 14.1
But all time getting failed to mount'/persist'(invalid argument)
Even not able to go back to stock recovery through back2stock.zip process
currently operating my phone through restoring backup
What I need to do please anybody have any solution of this please reply thanks in advance
Jayants susner said:
I am on latest version of TWRP have done all the process
unlocked bootloader
Rooted my phone
On latest version of TWRP
Official lineage os 14.1
But all time getting failed to mount'/persist'(invalid argument)
Even not able to go back to stock recovery through back2stock.zip process
currently operating my phone through restoring backup
What I need to do please anybody have any solution of this please reply thanks in advance
Click to expand...
Click to collapse
Excuses excuses, but bottom line just don't get around to things very fast very often. Did you ever figure it out? It was a long time ago now so I assume you did....

massive problems with ERROR:7

Hello,
I'm having big problems flashing any ROM on my Oneplus 5 atm.
At the beginning of this month, I wanted to unroot my rooted Android 8.0 or 8.1 (One of them, it was OxygenOS, but not the newest version)+ Xposed Oneplus 5.
I got a couple of errors, most of the time error 7.
After hours, old and new recoverys (TWRP) from blu_spark, codeworkx and some xda user recoverys and diffrent OxygenOS versions i finally managed it to install a Oxygen version with Android 7.1.1 on the phone. The Problem was: I always got errors (Installation failed) when I wanted to intall Software Updates no matter if I tryed it by myself or with the official system update in android.
So and today the official beta build of OxygenOS for 9.0 released and I was so stupid and thought I can make this an easy one.
Now I'm sitting here since 9:30am and try to flash Android 9, or any Android except 7.1.1 (only Oxygen Versions). Most of the Time i'm getting ERROR:7, it doesnt matter with which Recovery or Build.
When I got this problem at the first Time, my Phone was shown as "" (The error was something like: This Package is for a "Oneplus 5" this is a "").
When I get this scentence now (not every Recovery is showing it) it says my Phone is a "OnePlus5T", but i have a Oneplus 5.
Also (maybe partly) important things are:
- I tryed to edit the updater-script and delete the assets lines but there were no asset lines. Tryed it anyways and it didnt work. (and i really dont want to try this again)
I tryed to google this error for hours and many people meant that this is the way to go but I dont belive it. Isn't there any way to rename my phone, if yes: what do I have to do? I have TWRP and access to the command prompt aswell. If anyone can successfully create the 9.0 beta without the assets I would be happy but i dont think that is the solution for my problem, just a workaround.
- I think the problem is just something about my devices name. The strange part is that it accepted 7.1.1. And this was 100% a Oneplus 5 ROM.
- 7.1.1 isnt the way to go for me anymore. I dont like android 7 and it has so old security patches..
- Fingerprint sensor and screen got replaced
thank you for reading this and maybe helping me. I dont have the best language skills, if you need more Information about my Phone, please ask
EDIT1: As I said, 7.1.1 is still successfull, i tryed it a couple of mins ago. no error 7 or sth
maybe you can try revert to fully stock setup{without TWRP) and update to pie?
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
petryrety said:
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
Click to expand...
Click to collapse
Make sure the download isn't corrupt or if you extract the compatibility.zip use a recommended tool.
I had this problem couple of months ago. I solved it by flashing an old os version then flashing stock recovery(I don't remember if I locked the bootloader). boot in to the phone and download and update through ota( I did 3 updates this way). Then install twrp and root. Now I can flash any oos update without error 7.
May work
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
iwantademo123 said:
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
Click to expand...
Click to collapse
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
strongst said:
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
Click to expand...
Click to collapse
That's good, It's good advice. I am just stressing to everyone in this thread, how important it is to follow that and use a recommended tool to remove compatibility.zip because removing compatibility.zip sounds very trivial thing, but it's actually really important to use a tool like 7-Zip that doesn't break the firmware in the process.
Also, the link to my other post ( https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13 ) should be detailed and comprehensive enough to help people with error 7 in other scenarios or that are trying to update to oreo or other stock firmwares too. This method restores the phone back to factory condition, including all the partitioning. Updating with a locked bootloader can fix a lot of update errors. I've found that after 5.1.5 it is safe to unlock the bootloader and take updates. But as you mentioned, for an unlocked bootloader, compatibility.zip needs to be removed from the firmware archive, and a tool such as 7-Zip must be used to do so as other archive managers break the update entirely (with error 7).
Good luck everyone trying to update, hope our advice helps :good:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
TurtleSandals said:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
Click to expand...
Click to collapse
The unlocking process of the bootloader is the same!
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
mathgerm said:
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
Click to expand...
Click to collapse
Please see here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post79938097

Categories

Resources