yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] slainer68:
Hi there. Maybe I'm not the only one with the problem, I was wondering why the auto-update feature of LOS is not working on my phone?

I'm using TWRP 3.0.4-1, when I'm using the auto-updater, the phone reboots in the recovery, the recovery asks me for the partition password. I enter the good password, it decrypts the partition succesfully, then directly goes back in the main menu. And the logs does not display any error message...

So I don't know what is wrong, is that a problem with LOS or TWRP?

Thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] h0LLe:
hey guys, i unlocked bootloader successfully and then pushed the twrp 3.1.1.0 over fastboot. i already flashed lineage os and resurrection os without much problems. but i cant make a backup of my phone within twrp on micro sd. error message is:

Backing up System Image

Backup Failed. Cleaning Backup Folder.

now i tried on internal storage and it does work. i used the micro sd in other phones, too. should i format it inside the axon 7?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dnlilas:
[MENTION=1846546]h0LLe[/MENTION]

Did you check microSD for available space? Your microSD is FAT32 or exFAT?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] h0LLe:
yeah, the free space is shown when choosing internal or external sd, external had about 16gb free, backup showed 11gb of needed space.

micro sd is in fat32 ... might that be the problem?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dnlilas:
FAT32 should be OK. Maybe you can try to check the TWRP recovery.log for detailed information: in TWRP, button Advanced etc...

I would suggest to mount the microSD under Windows (Mount button inside TWRP) and do a checkdisk command : "chkdsk g: /f" (assuming g: is your microSD).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] h0LLe:
did that and checkdisk didnt find any disk errors. i did a format on pc with exfat but the backup onto sd failed also. then i did a format inside android, same result twrp backup failed writing onto sd card after around 7,8gb.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Smedslund:
I have read and searched but i just can't get it.

Im on RR whit open bootloader and twrp 3.0.4.

I can flash SuperSU but i cant see my internal storage so every flash is giving me nothing.

What do i need to do to pass encryption?

It is not the first time i flash and root devices but first time on AXON 7.

Any suggestions please?

Best regards

Smedslund
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
[MENTION=1846546]h0LLe[/MENTION] I having the same issuses as you.... I can create a full backup on the internal storage but it fails at the same point on my sd card as you...

I running the lineage with opengapps on my a2017u with TWRP 3.1.1.0 recovery as well... Can someone take a look at this log for me. It's failing on the system backup and talks about a directory not existing but I'm stumped....
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dnlilas:
[MENTION=1846546]h0LLe[/MENTION] [MENTION=1504428]Young Gunna[/MENTION]

From log:

Backing up System Image...

I:Reading '/dev/block/sde13', writing '/external_sd/TWRP/BACKUPS/aaec9f4b/2017-06-01--06-31-40_lineage_axon7-userdebug_7.1.2_N2G47O_be8ece/system_image.emmc.win'

I:Error writing destination fd (No such file or directory)

Backup Failed. Cleaning Backup Folder.

I suspect a lack of free space problem (although estimated at start of backup).

When you take backup on internal SD, what are the size of system image backup? And what is the free space on external SD?

By the way, you can try to backup System instead of System image, since with RR or LOS the dm-verity is disabled so there is no need to back system image (sectors backup). System backup (files backup) would be sufficient and will take less space.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
[MENTION=3393704]dnlilas[/MENTION] I have plenty of space on my external SD card ~80GB... (120GB Sd Card) internal disk i have ~50GB. When I make a backup using the same settings to my internal drive it all backups successfully and that has less free storage than my extSD...

I guess i could just backup the system instead of the system image to my extSD since it looks to make it past that point without problems.... I just hate when things dont "work" and want to help find bugs when i can...

Could it be that my exSD card is formated as vfat????

Display_Name: Micro SDCard

Storage_Name: Micro SDCard

Backup_Path: /external_sd

Backup_Name: external_sd

Backup_Display_Name: Micro SDCard

Storage_Path: /external_sd

Current_File_System: vfat

Fstab_File_System: vfat
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dnlilas:
[MENTION=1504428]Young Gunna[/MENTION]

I agree with you that we must understand the problem. So disk space is not the problem.

When backup with internal SD, what is the size of the file system_image.emmc.win?

FAT32 has limit of 4GB, vFAT and exFAT should be OK. Now since vFAT did not work, could you try to use exFAT (this would mean reformat your external microSD so it could be not possible for you)?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
[MENTION=3393704]dnlilas[/MENTION]

I already deleted the backup that was on my internalsd card (accidents happen lol) so i cant get you that information.

I can reformat my SD card tonight when i get home tonight, thats not a problem.... ill format it to ext4 to match what android has my internal SD card set as and also can support way larger file sizes than i have ever seen....

hmm thinking more... i believe that the vFat might be the issue... im not sure how TWRP backs up large files but if its making a 1for1 copy of my system image that would make the final file size ~6GB which would clearly break things lol... All other backups a much lower than the 4GB limitation.

/system_image | /dev/block/sde13 | Size: 6144MB

Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img

Primary_Block_Device: /dev/block/sde13

Display_Name: System Image

Storage_Name: system_image

Backup_Path: /system_image

Backup_Name: system_image

Backup_Display_Name: System Image

Storage_Path: /system_image

Current_File_System: emmc

Fstab_File_System: emmc

Backup_Method: dd
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dnlilas:
[MENTION=1504428]Young Gunna[/MENTION]

I think you point out the problem. exFAT is recommended over FAT32 and vFAT since it should support file size > 4GB.

My 64GB microSD card comes pre-formatted with exFAT.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
*sigh*.... i wont be able to test this out until about 9pm EST.... i should have know this was this issue, just wasn't thinking when i reformatted my sdcard using a Windows machine. My old galaxy S5's backups didnt have the option for the entire image so i never saw this issue of file sizes being too large for the last 2 years....
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
[MENTION=3393704]dnlilas[/MENTION] I was able to use TWRP recovery to change my exSD card to ext4 from vFAT and the successfully make a complete backup to the exSD Card it was definitely a file size limitation as the system image isn't broken up during a backup and was a 6GB file! I failed because i should have know that was the issue as FAT can only handle file sizes of <4GB...

[MENTION=1846546]h0LLe[/MENTION] check to see if your SD card is formatted as vFat or FAT... If soo you will need to reformat it to ext4... just a reminder once you do this you will lose data on the sd card so make sure you back everything up... and secondly you will not be able to use this card on a windows machine without installing additional software as windows doesn't support ext4 natively.

[MENTION=5672995]jcadduono[/MENTION] Can you add this info to the first post so that others can see it? Basically to do full system image backups SD card need to be formatted as ext4 due to 4GB file size limitations. This will mainly affect Windows users as by default we format our SD card as vFat/Fat32 so we can still use them with windows machines.

Edited: Fixed typos...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimbo77:
What about exFat? I have my 128gb card formatted as exFat and I was able to do backups with no problems...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dnlilas:
vFAT (aka FAT32) has limit of 4GB for max file size. exFAT does not have such limit.

https://www.howtogeek.com/235596/whats-the-difference-between-fat32-exfat-and-ntfs/
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
Correct! exFat does not have that file size limitation, however, [MENTION=3130027]jimbo77[/MENTION] some android devices might not be able to read exFAT formatted cards. If the Axon 7 is working fine with it then you should be good to go.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ArgonautPollux:
If all I do is unlock the bootloader and install TWRP/SuperSu, will I still be able to download and flash official updates from ZTE without any problems?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
I have a little problem, I'm using the build 3.0.4-1 and when I make a backup, it won't restore when I try to restore the backup. I'm on B19 complete stock unlocked bootloader
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
If you checked "make system read only" in TWRP when you flashed your ROM, you must uncheck it when restoring a backup. Goodluck
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
Thank you very much for telling me.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ariy11:
Hello I am unable to boot into any nandroid backups I make any advice is appreciated
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mark1003:
Hello,

rebooting my system i have a problem with encryption.

During the system reboot the encryption seems to be active and i am asked to type in a password, although i have installed no-verity-opt-encrypt-5.1 and formated data to get rid of encryption.

So my LineageOS can't boot.

I do need a tricky hint :o

Thanks for help
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jdgesmlls:
What format is data? Is it f2fs or ext4? It needs to be ext4 based on several users experience.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mark1003:
It is f2fs.

I can change the format in "wipe>change file system" for the data partition.

But if i then choose "format data" (in order to get rid of encryption) it is again formated as f2fs.

Is there another way to remove encryption?

By the way: why is encryption not removed using "format data"??

I have never seen this.

Edit: Meanwhile i am not really sure if encription is the problem. During boot (Lineage) the booting sequence

is interrupted, because the device can't be checked for corruption. It is confusing, since i have

formated data and install no-verity-opt-encrypt-5.1.zip before installing Lineage.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JenniferDylan:
I might have goofed, I updated from an earlier version of TWRP to a newer version since the ROM I tried to install prompted me to update, problem is that I did not have an OS installed already. So now I can't get into recovery, it either get stuck on ZTE boot logo or I can boot into EDL but windows do not detect it. Am I screwed?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] seko85:
Turn off Your phone. Then press Vol Up and Power button and keep pressed them for a while. Then release only Power button and keep pressing Vol Up. You should see ZTE logo and then TWRP menu.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
Updated the thread - it's been some time. Sorry, life's been full of surprises lately.

Fortunately everything appears to be working just fine on B32, let me know if any issues show up. I'll probably be updating TWRP for ailsa_ii to the Android 7.1 branch sometime later. (it's currently built off Android 6.0)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
[MENTION=5672995]jcadduono[/MENTION]

With Chinese Oreo leak images, any news about trying to update to support O?

There's no way to know if will get any type/kind of source code.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
Well I certainly hope to support Oreo once NA images are released. Right now I'm a little pissed that B32 kernel sources don't boot (removing vendor_log/sdlog mentions to even compile, thanks ZTE for providing half assed sources)

I might just rebase my Android M driver cleanups onto a new CAF branch and go from there. I don't really see any major ZTE code changes.

The issue I'm having with B32 is...

Unhandled fault: alignment fault (0x96000061) at 0xwhatever

PC at smp2p_init_header

LC at smp2p_(can't remember)

I figured it was a toolchain issue. On GCC-7 (ignoring many warnings) the result is that.

On GCC-5 (ignoring a few warnings) I can't even convince it to boot far enough to get pstore.

I still have yet to try GCC-4.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MrGodMan:
What order are the wipe options listed in? I can't see half my screen (but it still responds fine) and I want to flash stock and lock bootloader before returning it for repair.

This is all I can currently see.

If there's an option in TWRP for screen rotation that would also be very helpful.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
The B32 kernel isn't public. That one you can find from ZTE Open Source is B25. Or are you in contact with ZTE? Anyways if you want B32 working you can find the source from Udev and me here: https://github.com/OrdenKrieger/android_kernel_zte_msm8996/commits/oreo-mr1?after=5b2b3bf6579e0b314cb82188b2048c4167d50284+209
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] :
Speaking of witch, the latest version 3.2.1-0 won't decrypt an encrypted partition on Android O.

I use this ROM : https://xdaforums.com/axon-7/development/rom-project-world-t3728221 with B32 bootstack, like the post suggest.

Thank you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] foggydew88:
I've tried one month long to compile the source kernel (Nougath B08), after the usual corrections of a planty of headers, the compilation goes well, but no way to boot.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xdataibai:
Deleted
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Devendra kove:
Change my ZTE nx597j Recovery mode in twrp recovery
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BaamAlex:
I think this is the wrong forum for you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
TWRP - treble + encryption

With 3.2.3-1 out for certain phones, which supports encryption, what is the chance a TWRP that supports treble + encryption will come out? NFound's TWRP has a number of limitations (adb is one of them).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] juniorjpdj:
I'm also waiting for this.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] teji007:
Sir/Ma'am,

I have A2017U Model with Stock Oreo B20 non rooted. I want to install custom rom and need to install TWRP first. Can you guide me how to unlock the bootloader and install TWRP, step by step?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] juniorD:
Does anyone know how to fix Error 255 or what it is?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mrrocketdog:
this might help :

https://xdaforums.com/oneplus-5/help/error-255-twrp-t3739468

good luck [emoji106]

err on the side of kindness
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] juniorD:
Thanks for the reply. But my issues isnt during backup/restore its during installation. Trying to install the July update to AEX ROM for my Axon7U. The earlier update installs fine but not this one. The TWRP team told me my logs point to a problem in the updater script and to contact the developer. I did but havent gotten a response as yet. Is there a workaround to bypass the updater script?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcdw:
After attempting to flash and getting error 255, go to TWRP's Advanced section and save the recovery log. Either look through it and see if you find anything or let us have a look. Attach it here or post it online and provide a link. Just don't paste it in a post.

If you had an error 7 then I would suggest removing the assert lines from the ROM's updater-script. For error 255 I'm not sure so a log should give an idea what's going on. Might be assert lines, might be something related to what mrocketdog linked to (even though not doing a backup/restore), or something else. Logs are key. Better than head scratching. [emoji16]

ZTE Axon 7 A2017U, Project New World, Multiboot, XDA Legacy
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] juniorD:
Thanks again. I do have the recovery log. Thats what I sent to the TWRP team and they looked at it and said the error seemed to be with the updater script. I'll attach it to this message. If you can take a look it would be greatly appreciated. The maintainer for the AEX GSI is in this forum and has yet to answer my message so any other help would be awesome :good:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcdw:
Heh, ran out of battery while reading the log on the Axon. Oops.

[MENTION=4901196]juniorD[/MENTION], ah, I forgot you were dealing with a GSI. I don't do GSI, Pie, Treble, and vendor stuff so I'm out of my element.

The ERROR 255 is caused by this though...

"Failed to read sparse file"

So there may be an issue with that AEX img. Hopefully the provider/dev will get back to you on that.

Essential PH-1, /e/OS 0.7-n ROM, microG (NoGapps), XDA Legacy
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BlazingBullets:
Works on my A2017 (Chinese 4/128) running ZAD Mix 3, xposed, supersu 2.78.

ADB works and everything else works fine afaik.

Looks good so far. Now we wait for CM official...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gpz1100:
You're referring to the fbop partition? I don't see a fbop.img file in the b20 firmware file. Can you post it?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimbo77:
Any instruction as to how to revert to B20 bootloader? I'm on B29 bootloader (due to a update via twrp) but hate the 5 seconds warning too ;/
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
I meant emmc_appsboot.mbn which is flashed to aboot, that's what's displaying the warning. (it's located in the full OTA B20 zip)

I don't want to post it as I don't know which negative implications it could have yet.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimbo77:
I understand the risk. Thanks anyways, whenever you confirm it's safe please do let us know :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gpz1100:
I actually find the 5 second delay useful. Easier than trying to remember which key combination is correct to get into recovery. Motorola's are power and vol down iirc, this one is vol up + power (or the other way around). With the splash screen, just press either and then choose fastboot or recovery.

Edit: I really need to proof read what I type!@# Apparently what I was thinking never got written.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hjjiang:
same here, as the stock rom, we cant edit the power menu to reboot to recovery/bootloader via GravityBox
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
just be glad zte made it so damn easy compared to other vendors, I really like that you can just hit restart from power menu and then hold volume up until you see zte logo to get into recovery, then enter bootloader/fastboot from recovery
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Narada2XK:
If you are already on B29, must you still go through the OTA procedures in the instructions or can you simply unlock the bootloader, flash TWRP and install SuperSU?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xtermmin:
A little off topic, but is there a way to clear modemst1 and modemst2 via TWRP? I tried doing it via fastboot a couple of months ago but it appears that ZTE is blocking the erase command.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimbo77:
I was on B27. So my recommendation install the B20 update via stock recovery unlock the Bootloader and then install the B29 bootstack and B29 system zips :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
Yeah just dd if=/dev/zero bs=16384 of=/dev/block/bootdevice/by-name/modemst1

From twrp terminal or adb shell (change modemst1 to modemst2 for modemst2 obviously)

Thinking about adding wipeingui support for emmc labeled partitions to do that

As for people asking about unlocking BL... You have to flash the B20 full ota and then B20 unlock. I did add full instructions for it in a link on the first post.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xtermmin:
Didn't know that worked. Thanks a bunch! :D
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
& because "enquiring minds want to know". . . . . what will you use that for -- & why? :p
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xtermmin:
It's because of something myself and a couple others have experienced on the Axon 7, and I've also experienced on other (mostly Motorola) devices. What happens is that sometimes after removing and re-inserting a Verizon SIM card (which seems to be the commonality) in a phone a few times without powering off, the phone will no longer be able to connect to LTE, just CDMA 1x/EVDO. Setting the phone connectivity method to "LTE-only" doesn't fix it, rebooting the phone doesn't fix it, removing and reinserting the SIM doesn't fix it, inserting the SIM into another phone (which connects to LTE fine) and sticking it back into the first phone doesn't fix it. To fix it, there are a few options, but they're kinda clunky:

1. Power off, swap in a GSM SIM, power on, phone will detect the different kind of SIM and re-generate the modemst1 and modemst2 partitions, power off again, stick Verizon SIM back in. (clunky)

2. Power off, boot into bootloader, connect to computer (clunky), fastboot erase modemst1 & modemst2, power on phone and wait a minute for the phone to re-generate those partitions. This is the method that I used on other phones, but ZTE has blocked the erase command in the bootloader, so it can't be used on the Axon 7.

3. Something I've only done with the Axon 7, but if I go into the Phone Info testing menu (where you can set the connection type), and switch between "LTE/GSM/CDMA auto", "LTE/CDMA auto", and "LTE-only" multiple times while also turning on and off the radio, at some point the phone will re-generate the modemst partitions and re-connect to Verizon LTE. (random & clunky)

I didn't realize that TWRP's terminal had access to those partitions, so being able to quickly boot into TWRP and erase those two partitions would be a much more straight-forward way of re-generating them. Sure, it'll only help those of us who have TWRP installed, but at least it wouldn't be as clunky for those of us who do.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
Never tried it myself but maybe you can create 2 files that are 16384 null bytes on your PC and fastboot flash that file to modemst1 or modemst2 lol

Busybox for Windows: https://frippery.org/busybox/

busybox dd if=/dev/zero bs=16384 count=1 of=erase_modemst.bin
fastboot flash modemst1 erase_modemst.bin
fastboot flash modemst2 erase_modemst.bin

As always, busybox for Windows is almost as cool as me
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kgptzac:
I suppose this is a bit off-topic question... when making a backup, does it matter if I have pattern/PIN/password protection? I read in somewhere that having such security would make things not working afterwards.