yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xtermmin:
You can flash 2.65 without mounting system, as 2.65 flashes in systemless mode by default.

Mounting system seems to cause issues with the phone and/or TWRP asking for a password on boot, so it's best to not mount system if you don't need to. Making changes to system also breaks OTA. The systemless root that 2.65 uses makes changes to the boot image, which does break OTA too, but it's a much smaller image to restore from backup, and it doesn't cause any password on boot issues.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nsane:
Link in first post appears to be down.

Could someone please reupload TWRP 3.0.2-2 touch for Axon 7?

Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nsane:
Apologies for not noticing this.

Thank you
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
Considering TWRP is community driven, why can't this be included in their official builds? I'm all for modding but, coming from devices with "official" ROMs and recoveries, I only have suspicion of unofficial builds.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dennis96411:
I think "unofficial" means it's not built by the TWRP team, but rather someone who forked the sources over. There's no reason not to trust it if the source code is available.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
It could be included officially but there wouldn't be any difference since I would still be the device maintainer.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
It would speak to its legitimacy and integrity. Why not be an "official" maintainer? If anything I'd say you deserve the recognition and it would aid in the device getting more interest in ROM development. Instead of "someone got TWRP to work on the Axon 7" the conversation changes to "TWRP officially supports the Axon 7."

Plus, people have gotten jobs through their hobbies on here. Paranoid Android devs all got hired by one phone company, for example (can't remember which.) It's a good way to think about it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tasar:
Is it possible to "flash" twrp temporary as i do it on my Moto G4 with : fastboot boot twrp.img ? Have an A2017G and i see no fastboot screen on phone like Moto.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Unfortunately ZTE doesn't allow fastboot boot or fastboot flash with locked bootloader. And even if you unlocked your bootloader fastboot boot is something ZTE did not add it returns unknown command I believe.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tasar:
Ok, thanx . I have test it myself and yes, the command give me an "return unknown command " :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Loader009:
how about "fastboot sideload twrp.img"?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
I'm getting "Enter Password" upon boot of TWRP when I simply cancel out try to backup partitions I receive decryption failed?

What's the cause of this and what to do to fix that issue?

Edit: Solved it by formatting data.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Antistar:
Hi all

Need a help

I did twrp backup of my system and data and boot. When i want to restore all of them , after reboot system asking for a password. What`s goin on .??
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ntrambitas12:
noob question here, will this work for the mini model?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Controllerboy:
No, don't try this or it'll probably brick your device.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Tibedabeeto:
Download link seems to be broken in OP. I found another link here..... https://www.androidfilehost.com/?fid=24723757092307091

Not sure if this is the right one, but the name seems to be correct.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Locklear308:
So, everything is working on my device but I wanted to try out Cm13. I'm a bit nervous to backup anything or do anything in TWRP because last time it broke my wifi. O.O

Am I missing something here?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hjjiang:
just got this phone rooted and unlocked, i want to back up my current setup, do i need to backup the system image (6gb) with everything else but cache?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tasar:
Dont backup the great system, you cant restore It.

Gesendet von meinem ZTE A2017U mit Tapatalk
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hjjiang:
thanks for the info, the backup just got smaller =)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gpz1100:
Is this on a bootloader locked version or unlocked? Why not?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hjjiang:
i actually have my bootloader unlocked, is it still useless?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kgptzac:
I'm having issue with touch screen not working while in the recovery... only way to get touch screen to work is to do power off then power on then to the recovery directly.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gpz1100:
A2017U, bootloader unlocked, twrp 3.0.2-2.

Strange behavior with twrp. If I select to back up boot/system/data, upon restore, it just sits at the zte logo indefinitely.

If I select to back up system image (rather than system), then it boots properly.

What am i missing here? Past phones (even on MM) required just /system to be backed up for a successful restore/boot.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Loader009:
Does it actually booting into your Backup?

I had the problem that it was booting into this system image with ~4GB of storage space.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tasar:
I have an unlocked 2017U and for me, the restore break with the big System backup
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Loader009:
Does anyone have issues with an encrypted Backup?

I am not able to make an encrypted Backup.

After setting the encryption password two times, I start the backup.

2 1/2 minutes later it stops, with the following message:

createTarFork() process ended with ERROR: 255

It stops after about 1700MB.

After it stopped, I go back, set the encryption password again and start the backup... still stops with that error.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gpz1100:
It appears to. I created the large backup, then restored it. Rebooted successfully.

Question is, why doesn't just backing up "system" work?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gpz1100:
Small update, selecting in twrp options rm -fs rather than formating seems to allow booting after restoring.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xtermmin:
I have no issue backing up and restoring system/data/boot/cache in TWRP. I'm able to switch between my B29 backup (not the hueg system image) and CM13. I don't do straight Restore though, I do the Advanced Wipe first, and then restore my TWRP backup.

A2017U, bootloader unlocked, using UnjustifiedDev's TWRP.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
There are user-defined settings stored under Data that help control system parameters. Dependent upon how different the System and Data levels vary, restoring a backup of just one (or the other) may cause a failure to boot or even with boot may cause FCs in any of several System apps.

Good luck.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tasar:
[MENTION=3867776]xtermmin[/MENTION], the problem is not an normal backup/restore, the problem is when you want to decrypt yout TWRP backup, that doenst work. Backup breaks at Data with error 255.

And dont forget, to disable pin/pattern before backup. When you restore a backup where pin/pattern was set, pin/pattern is break after restore and you must manualy delete some files in system/data:

password.key

pattern.key

locksettings.db

locksettings.db-shm

locksettings.db-wal

password.key

pattern.key

not all of them are present on every device, the last time for me it was enough to delete the locksettings.xxx files and i have full acess again and can make new pin/pattern entry.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gpz1100:
Don't think this plays much of a role. After wiping data, I tried restoring just boot/system with similar results.

Being stuck at the zte logo is some indicator of where the failure is occurring. It's not even getting to the point where the axon logo/boot animation is being displayed.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
First command is :

adb reboot bootloader

Once there you follow the rest of the commands "fastboot ones"
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimmydee62:
Thanks I appreciate the quick response now I can do the thing.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Updated link to latest build which fixes the external sdcard. Keep in mind the image name has not changed. Thanks [MENTION=3044858]DrakenFX[/MENTION] for testing and uploading the file.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
Just adding little more info.

Just download the new TWRP image and Flash using your Current TWRP, there is NO NEEN to use fastboot,
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
Are you going to submit the Axon 7 for official TWRP builds?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Sure am once we iron out the remaining issues.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tele_jas:
Thank you! Backing up now to my External SD card!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Barsky:
Smoooooth and backing up before rooting.

Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ciko84xp:
Hi guys, i whould know if this TWRP Recovery works on Chinese Axon 7 6GB/128GB FT version.

Thanx
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdgillihan:
Hey, did you backup the stock recovery before flashing twrp? If so would you mind uploading it for me if that's possible? Tia.

Always thank those who are helpful...and just ignore those who aren't.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tele_jas:
No, I didn't
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdgillihan:
Bummer. Ok thanks.

Always thank those who are helpful...and just ignore those who aren't.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] allan1229:
From what I've read I don't think theirs a way to backup stock recovery before flashing TWRP
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rczrider:
I think [MENTION=540283]tenfar[/MENTION]'s tool does it and [MENTION=2530247]KyJelly69[/MENTION] just did it: http://xdaforums.com/showpost.php?p=68262032&postcount=106
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] XblackdemonX:
When I try to restore the system.img it says extractTarFork() process ended with ERROR: 255.

Now my phone cannot boot anymore.

What can I do?

Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
Which system.img are you restoring and which TWRP are you using. Just asking since I say that you flashed tenfar's recovery and his TWRP is quite smaller then this one. I have see this happen with corrupted images though.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] XblackdemonX:
I'm using the TWRP 3.0.2.0-b10 with the system image I took from here.

If I try to flash the TWRP from this thread it will only boot recovery to a black screen.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
Try the one that is posted in the OP, that was done by Unjustified Dev (08162016), it fixes SD card support and such. The same image worked for warofhero, but he was already BL unlocked and that image is for B20_boot. Here is how he did it.

http://xdaforums.com/showpost.php?p=68233963&postcount=34

Are you running of the internal sd and external. It might be that the img file got corrupted during transfer

EDIT - just saw that this one is not working for you, not sure why though, how are you flashing the OP TWRP [MENTION=4911249]Unjustified Dev[/MENTION] - could you chime in on why this might be happening
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] XblackdemonX:
If I try to flash the TWRP from this thread it will only boot recovery to a black screen.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warofhero:
So you are saying you have a problem with flashing TWRP not the system restore file. If you have Chinese edition Axon 7 , don't try to flash the TWRP in this thread because it might create problem for you. Use the one that support Chinese version.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] XblackdemonX:
If I try to restore the system image via TWRP I get extractTarFork() process ended with ERROR: 255.

If I try to update the TWRP with the one from OP, it will say SUCCESS but when I reboot to recovery I just end up on a black screen.

(I have the US version and my bootloader is LOCKED)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warofhero:
Bro I don't know what you did but it sound like something is wrong with TWRP since you can't even boot into it. I recommend you to start everything fresh from the beginning especially unlock your bootloader first because it is already proven to work.

Follow the steps here with unlocked bootloader method
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] XblackdemonX:
The problem is if I unlock the bootloader and it doesn't work, then i'm stuck with a brick and I can't return it on warranty :crying:

I am able to boot into TWRP 3.0.2.0-B10 fine it's just the one in OP that I am unable to boot into.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warofhero:
Well I think you already can't return the phone because you no longer have stock recovery. As long as bootloader work, you can always unbrick your phone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
OK, so to keep it clear...

You can boot into twrp but is not OP recovery?

Meaning you are using a whole different custom recovery twrp? Which brings me to the point of system images posted in my Thread (thanks [MENTION=2782065]swehes[/MENTION] for it) give you such error when you try to flashed over the one you are running right now?

That image was back up using twrp from OP.

TRY THE FOLLOWING.

1- Assuming you have the file already, add " .iso " at the end of ".win "

2- Now try flashing it using INSTALL > SELECT image.

---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------

He didn't flash TWRP he just boot into it.

fastboot boot TWRP. Img

The OP twrp CAN'T boot that way.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] XblackdemonX:
I have the stock recovery and I am able to flash it no problems.

That is correct.

TWRP doesn't see the ISO image.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warofhero:
Oh I didn't know you can do that.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
Doesn't see the file cuz is not an .iso , you need to change the extension of the file.

Right now is what : system_image.emmc.win

Change it to : system_image.emmc.iso or system.iso

EDIT:

Are you B20 or B20_boot?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] XblackdemonX:
Yes that is exactly what I did but it doesn't see it. It is only able to see .img files.

Edit: I'm B20 (no boot)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
Sorry my mistake change to. Img LoL :silly:

Friday little nuts around here....

Mmmmm how is it possible???? I thought B20_boot is required use TWRP and Flash stuff.

If that is the and you can't get working you may need to UPDATE to 20B_boot and do unlock bootloader and all that.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] XblackdemonX:
No problems. thanks for your help btw.

Now if I rename it to .img I can only select to flash it to boot partition or recovery, I cannot select system.

If I select Boot it will say the target partition is not big enough.

EDIT: If I unlock the bootloader using jkuczera's method I guess there is no way to re-lock it right?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
Has to be system, is a system image
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] XblackdemonX:
That is exactly what I thought but I don't have this option.

Maybe what I'll try is to use a different boot.img with Unjustified Dev's TWRP
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
What are you talking about?

YOU DON'T NEED boot.Img :rolleyes:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] XblackdemonX:
Well... when you use Tenfar's method it flashes a modified boot.img and his version of TWRP.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdgillihan:
I haven't been back in there to check today (and no offense to him, it's a wip), but so far I haven't seen his program actually fully work yet. Seen two semi bricked devices in there trying. Probably was user error, but I'd wait until it's perfected and proven myself.

EDIT: I guess maybe it's the root part that I haven't seen be provable as working yet. Maybe what you are trying to do will.

Always thank those who are helpful...and just ignore those who aren't.

---------- Post added at 02:42 PM ---------- Previous post was at 02:22 PM ----------

Wouldn't the fastboot command to relock it work? I can't remember [MENTION=3044858]DrakenFX[/MENTION], has anyone tried to relock yet?

What is it, fastboot oem lock?

Always thank those who are helpful...and just ignore those who aren't.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
I think [MENTION=540283]tenfar[/MENTION] is using the [MENTION=5672995]jcadduono[/MENTION]'s TWRP from idlekernel, he modifies it to load past the locked bootloader. We have not seen the it confirmed on US phone yet since source for img's was from B20_Boot. I looked at the boot and recovery that was dumped from a B20, looks legit but is padded to 64MB file. It's probably why the TWRP from here will not boot, it's not modified(signed) to get past the locked BL. And the other TWRP might not be fully functional, i know jcadduono pulled the file from his post. So we probably need tenfar to mod the TWRP from op to make it run on locked BL. Even then the boot and system will mismatch (wifi won't work) so we need a system pulled from B20(non _Boot one) but it should get the phone bootable and possibly with root. I still have the B20_Boot boot.img that tenfar modded to match that system image at least if needed
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rczrider:
My gray came today, stock with B20. I can pull system if someone can tell me how to do it.

Or is that the issue? [MENTION=540283]tenfar[/MENTION]'s script will only pull boot and recovery, correct? System could be pulled from TWRP, but we can't currently install TWRP without an unlocked bootloader, which requires B20_Boot?

There are a lot of threads and discussions within to keep track of. If there's something someone would like for me to do, just let me know. I'll keep it B20 stock for the moment.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
You could pull the stock boot and recovery, then flash [MENTION=540283]tenfar[/MENTION]'s TWRP to dump the system and the hopefully flash back the stock recovery image to put you back to full stock. It's just unclear if the TWRP that tenfar modified is working properly, waiting on clarification hopefully he, Udev and jcadduono see my post and respond. I agree, we have a lot of parallel development going on, not much collaboration though.

---------- Post added at 04:05 PM ---------- Previous post was at 03:45 PM ----------

This seems to be confusing quite a few people but flashing the OTA it self will not unlock the BL. it will however change the software version to B20_Boot and alter the phones finger print. This can be changed later on by flashing the matching boot/system of B20 and hopefully we get a full image for ZTE.

When you run the fastboot oem unlock, that is when you actualy unlock the BL. and while no one tried it, it should be doable, the oem lock is enabled in the aboot. IT will still leave your version as B20_Boot however, so no normal OTA from ZTE unless they throw the bone to us. We will have to make our own OTAs
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
as [MENTION=1340661]peramikic[/MENTION] mention " stock boot and recovery " and Untouch System_Image (yeah i know is huge 6gb )

thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rczrider:
Is the only way to do that (pull stock boot and recovery) using [MENTION=540283]tenfar[/MENTION]'s tool? I don't mind doing it, but didn't [MENTION=2530247]KyJelly69[/MENTION] already do it?

Recovery: https://www.dropbox.com/s/h929mct86lrkum0/stock_recovery_backup.img?dl=0

Boot: https://www.dropbox.com/s/7bj0py7r7zywyd1/stock_boot_backup.img?dl=0

If so, then it's just flashing TWRP via [MENTION=540283]tenfar[/MENTION]'s tool, which (may have) soft-bricked someone's phone? [MENTION=1001089]XblackdemonX[/MENTION], maybe?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Jose-MXL:
Pull boot and recovery before tampering, please :) do it, and then we can compare. It is always a very good sanity check to verify the checksum of two phones to see if the images are identical, if they are not, we have to go to the drawing board to see what the hell is going on.

When you do bootloader unlock the ZTE way (whether using the B20_boot or via offical OTA), the system partition is also affected so you have to rely on someone else's backup (I don't recall which other partition but it affects other stuff).

When using tenfar's tool you are only messing with the boot.img and recovery.img, you have the opportunity to also backup your stock B20 system image, and whatever other image that TWRP allows you to retrieve. Please note that I'm still not sure why you need to flash boot.img with tenfar's tool.

Pros and cons to whichever method you follow, just please please please backup whatever you can while you can...

So my recommended steps:

1.- backup stock B20 recovery.img and boot.img (via tenfar's)

2.- Use tenfar's tool to get you TWRP.

3.- backup the sh** out of the phone through TWRP, whatever you can (system.img and whatever other partition available)

4.- You should have a full phone image right? So let's get the party started.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dennis96411:
Okay, I backed up my boot and recovery partitions using tenfar's tool. Should I backup the system before I unlock the bootloader using the OTA update package or just go right ahead?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdgillihan:
Yes. Backup any and everything you can.

Always thank those who are helpful...and just ignore those who aren't.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dennis96411:
So I assume I just flash the included boot and recovery (is it TWRP?) images in tenfar's tool? What's the purpose of flashing the boot image alone?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
You can flash his TWRP, when it runs, run it in read only mode so it changes nothing in /system.

Then dump whatever you can off other partitions except /data. Take system image if you can as well.

Then move those to your PC via ADB or MTP, not sure this TWRP version works with SD cards

Then flash back the stock recovery.

You can than flash the OTA the normal way and unlock the BL

As long as you have all the partitions you can technically lock back the phone and then flash back to B20

---------- Post added at 09:19 PM ---------- Previous post was at 09:18 PM ----------

don't flash boot, no need just the recovery

so that would be -r option
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dennis96411:
What's the purpose of the boot image?

Okay I backed up system and data (so I don't have to resetup everything if I do flash it back to stock). What was this problem I'm hearing about an invalid password and needing to wipe data?