yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] raystef66:
[MENTION=9339252]Hellsbend[/MENTION]

Thnx but I think you underestimate [MENTION=319057]Oki[/MENTION] ;) This is his field right now and I just made the Q&A to let

him

answer all of that as this is

his

own project. And these questions (as others) WILL come sooner or later and therefore, let the Q&A group them together for new member-starters. Not more no less ;).

And btw, he'll be happy to do so. All credits to his work :good:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] docentore:
Jaysus, I have (had) right version installed, I had downloaded file correctly. Stop patronising me folks. Why are you so convinced that, especialy with new development, one user is fine other has to be as well.

It's like no one wants to hear that software might have bugs (every software has bugs)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Thanks for the log. Now I know what you were doing, how it failed, and how to fix it. In fact, it was very easy to fix and it is already fixed in the next release.

There is a bug in the back button of the confirmation actions under Advanced > Oki Labs functions. All the scripts, the functions, work fine but, if you press the back button instead of swipe to confirm, then the user interface crashes. It was easy to detect and fix. I haven't tried that button and this is why I didn't catch it. Thanks!

WORKAROUND: Until the next release, you can cancel the action by pressing the central navigation instead of the back button. That will bring you directly to the main menu and the UI won't crash.

Could you please confirm this workaround?

EDIT: New release v1.1 is now available and this bug has been fixed.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Druboo666:
[MENTION=319057]Oki[/MENTION]

any plan of releasing the source??
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] docentore:
I'm testing something else now, so little time so many things to try :) might come back to this tomorrow evening
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Well, the sources are at glance. You just have to unzip the zip files in the okilabs folder and you will find the shell script code. The UI part is under the twres also available for inspection in raw xml text files. The rest of the binaries are standard TWRP 3.2.3-0 so just go to the TeamWin repository for their sources.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
New TWRP LABS MOD v1.1 released:​

TWRP_3.2.3-0L_v1.1-Axon7-Labs_Mod.img

(Quick boot even when using F2FS, full ADB support, NO B12 Oreo encryption).

TWRP_3.2.3-0L_v1.1(B12)-Axon7-Labs_Mod.img

(Long boot when using F2FS, NO ADB support, B12 Oreo encryption).

CHANGE LOG:

* Added free space check in the Storage Backup function.

* Fixed back button UI crash in the confirmation page of the Oki Labs tools.

* Fixed EDL ZIP restore issue affecting the sets MINIMAL, EMERGENCY, FULL and ALL. Key detection is now working properly and backups created with this version can now be restored in TWRP as well as the rest of the sets. Please note that the affected sets created with the initial version can be restored only using MiFlash so update your EDL backups to have full functionality.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mjgspr95:
Does remove msg work yet? Nothing happened when I select it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] samo_lego:
Great recovery, thanks [MENTION=319057]Oki[/MENTION]!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] achilles912:
[MENTION=319057]Oki[/MENTION] I have problem with v1

I wiped everything

I flashed project treble v1.1

my phone restarted and i have this.

I don't know what i supposed to do

I can't flash phone through MiFlash because i getting can not read from port COM3

---------- Post added at 03:45 PM ---------- Previous post was at 03:22 PM ----------

PROBLEM SOLVED

i flash system through MiFlash using deep flash cable made by myself :angel:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Maybe you still need to enabled Device Mapper Verity enforcing, depending on the bootstack it is required.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
WoW!!! that looks like a hardware corruption. The flash of the Treble ROM shouldn't affect to the bootstack and recovery.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] billjim24:
I have the same thing happening. Thank you for the tip
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Any common factors here? Do you both have 'G' version phones? Are you both flashing from the same version of TWRP (whatever that might be)? etc?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] billjim24:
I have a U version and I picked option 1 from the OP. Other than that it seems like the same chain of event as previous poster. Its like recovery has completely crashed
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] skdubg:
what can we do here?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mjgspr95:
I'm on LOS 16 with your bootstack. Do I enable that with majisk or some adb command?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Two users with the same issue is not a coincidence. [MENTION=8300628]achilles912[/MENTION], you or any other who could duplicate this issue, could provide the recovery.log so I could see if it was a problem with the recovery? I have been using it for a month and I never saw this happening. I use an A2017U 4/64, and I tested the recovery with many different bootstacks/roms and partition tables.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Go to the reboot menu and reboot using the DM-Verity option.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] roadworker:
Same problem here on Nfound's B12 Oreo beta.

Removing password and/or pin doesn't solve this issue....
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] billjim24:
I would love to help if it happens again I will defiantly try to get you a recovery.log. But I will be honest I hope is doesn't lol. My homemade EDL cable was fun to make but is rather questionable. ( Although I did just order a more professional one on EBay... just in case ) . Would you be able to tell me how to get that log. I'm guessing I would have to do it after forcing EDL as there is no access to ADB .
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] alwynjoshy:
Could anybody explain why 2 version of twrp, i am noob about encryption and decryption on twrp, now i am on NFound's Treble Twrp (3.2.1-8). So would i get anything by flashing this?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DerSammler:
I also had the same problem as achilles912 and billjim24

with your first TWRP version.

Could the mobile phone but with a Deep Flash cable and MiFlash

and restore it to its former glory.

A2017G

Translate with DeepL
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
New TWRP LABS MOD v1.2 released:​

TWRP_3.2.3-0L_v1.2-Axon7-Labs_Mod.img

(Quick boot even when using F2FS, full ADB support, NO B12 Oreo encryption).

TWRP_3.2.3-0L_v1.2(B12)-Axon7-Labs_Mod.img

(Long boot when using F2FS, NO ADB support, B12 Oreo encryption).

CHANGE LOG:

* New Function: Expand OS. It resizes the filesystem of the system and vendor partitions to fit all the space available in the partition. Useful when flashing GSI and the user wants to add GApps, systemize apps or add any other module to the system or vendor partitions.

* Fixed the error at TWRP boot script. The log shouldn't show any error except the warnings appearing when the vendor partition is not present.

* Fixed EDL ZIP restore script issue affecting some configurations. In some cases the script was not able to restore the partitions in the zip file. Please note that the affected sets created with the initial version can be restored using MiFlash. If your device is affected by this issue and has problems restoring backups, please restore your backups using MiFlash and create them again using the new restore script.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Device encryption can't be disable. Once enabled the only way to remove it is to create a TWRP Backup of the data partition, an intSD backup and reformat the filesystem changing the type, switch ext4 by f2fs or viceversa. Use the trick twice if you do not want to modify the filesystem type. This is a TWRP limitation not related to the Labs Mod.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
I hope you enjoy the new Expand OS function. I know it was annoying not having enough space in the /system filesystem after installing a GSI when we have 5.5-6.0GiB for that partition.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
[MENTION=8300628]achilles912[/MENTION] [MENTION=4264354]DerSammler[/MENTION] [MENTION=4896987]billjim24[/MENTION] You three had the same issue. It can be probably related to the boot script instructions generating the errors in the log. I don't know if those instructions were causing your problem. I have solved those warnings but I can't check if they were the cause of your issue. It would be nice if you could retest the new version or provide the recovery log files under /cache or giving some information about your system such as:

- Vendor partition location and size

- Bootstack, ROM and TWRP version you had before this happened.

- What operation in TWRP were you using when that happened?

- Did it happened at the first boot or did it happened after the first session?

- Were you using device encryption?

- Can you provide the steps to duplicate the issue?

I have tried to duplicate it and I couldn't so it must be a very specific configuration triggering your issue. Sorry, I can't solve something I cant duplicate, and I can't check if it was solved in v1.2 as I hope, because I can't check.

Regarding the EDL mode, the EDL cable makes things easier. Have you tried to access EDL mode using the vol key combo? There are several ways when the device is bricked:

Op A: Pressing VolUp+VolDn+power, and keep them pressed until the led flashes. Then plug your device to the computer.

Op B: When the phone is off, Press VolUp+VolDn. While keeing them pressed, turn your phone on by pressing the power key, and keep the VolUp+VolDn pressed until the led flashes briefly.

Op C: Turning your phone off, press VolUp+VolDn and connect the device to the computer while you keep the vol key pressed.

By the way, any backup generated with the EDLBackup tool since the initial version can be restored using MiFlash in EDL mode.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] billjim24:
I honestly wasn't being very scientific this morning and was going a little flash happy exploring your tool and different GSI's so it is possible I am forgetting something.

But i believe I had just wiped system/data/vendor/cache. Then I decided to try the party tool and deleted my vendor ( the original MiFlash 800mb one Nfound introduced us to ) . Then I rebooted to recovery and made a new vendor which I know was on data (800 mb) but I cant recall beginning or end ( which ever one does not warn about erasing data ) I rebooted and flashed NFound's Treble v1.1 and then rebooted again but this time it was like recovery had crashed.

A few other details

I was still on Nfounds B12

Not encrypted.

I was just coming off of Arrow Rom but I had already wiped everything

Using your TWRP option 1 and I had used it probably 3 or 4 times to switch GSI's ( Its a pretty slick tool by the way. Well done )

While TWRP was frozen and unusable I was able to access the phones storage thru my PC.

As far as getting into EDL I tried all of the options you listed several times and while it looked as if the phone was going into EDL mode my computer was not seeing it. The EDL cable was truly a last resort for me.

I am sorry I cant really give more details. I really was in explore mode this morning and not taking measured steps like I should lol there is so much happening so fast for our device I just kinda want to see it all.

Also thank you for all the work you have put into this tool it truly is very nice and I can imagine only going to get better
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DerSammler:
[MENTION=319057]Oki[/MENTION]

I was on Stock Android 1.2 B12 Nougat with Supersu and TWRP-3.2.1.7.blackdeutsch.

Then I used the A2017X BootStack O B12 from NFound and your TWRP Laps.

So the OmniP-GSI-Vanilla flashed 9 Pie and everything worked fine, then I flashed PixelExperience P -9 Pie GSI- UNOFFICIAL for testing and the bootloader warning stopped. The TWRP looked the same with me as with achilles912. The PC only recognized my phone as Axon7 and as Handset Diagnostic Interface (DFU).

The only thing that could save my phone was the Deep Flash cable.

Translated with www.DeepL.com/Translator
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jomadeto:
Another with same problem that [MENTION=8300628]achilles912[/MENTION] [MENTION=4264354]DerSammler[/MENTION] [MENTION=4896987]billjim24[/MENTION], and as say [MENTION=4264354]DerSammler[/MENTION] only Deep Flash Cable can recover my phone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Guido83:
I got the same issue. Could you please explain how to fix that or point to a guid?

thank you
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anildzs:
Great TWRP development

Hi Oki - This is great development. Thanks for your development to the ZTE Axon 7 software enhancement and giving back to the ZTE Axon 7 community. I will try it out. Installation was without any problems.

---------- Post added at 05:22 PM ---------- Previous post was at 04:29 PM ----------

The EDL tool backup will be a great addon. Will this backup Boot, Bootstack, Modem, System and Data for MiFlash. That would be really wonderful to return from brick.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Could you please report also what were you doing and your configuration? What version of TWRP Labs Mod were you using? What language are you using in TWRP? what bootstack? what ROM? what vendor partition configuration?

Returning to a working status is easy. just follow the unbrick guide. You can use any EDL package, even those created by the EDLbackup as MINIMAL, EMERGENCY, FULL or ALL. For these situations Minimal should be enough to recover TWRP access (pressing vol up while rebooting).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Boot is backup along with vendor and system, as it is always part of an OS package. if you just want the boot partition image, you can extract it from the created ZIP, rename it to boot.img and then you can flash it alone. I understand it is nice if you want to revert to the original boot image after testing another kernel or unlock method.

BOOTSTACK is already an option in the EDbackup tool.

Modem is present in the MINIMAL, EMERGENCY, FULL and ALL sets. if you need it, you can extract it from any of those backups. adding extension .img will allow you to flash it using the standard install button in any TWRP.

System is also included in the OS package, and it is useless without the other partitions, this is why there isn't an option to backup only that partition.

____________________________________

I am planning on creating a "Bleach" function to zero the eMMC bytes of a partition, either for security reasons or to empty the unused sections of the partitions so they could be compressed even more for the backups. Do you feel this is interesting for you guys? I do it very often with the corresponding shell command but maybe it is interesting for you to have a button for this deep wipe function.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anildzs:
Bleach would be helpful

I think bleach would be helpful. This entire revamped TWRP is very helpful to try various rom's especially when nowadays there are so many GSI's to test.

---------- Post added at 08:17 PM ---------- Previous post was at 07:28 PM ----------

Hi Oki - Tested EDL Backup creation. Works great. Does the full also back up data. Looks like it is creating System Image, so I am guessing backing up data too.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
New TWRP LABS MOD v1.3 released:​

TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod.img

(Quick boot even when using F2FS, full ADB support, NO B12 Oreo encryption).

TWRP_3.2.3-0L_v1.3.B12-Axon7-Labs_Mod.img

(Long boot when using F2FS, NO ADB support, B12 Oreo encryption).

CHANGE LOG:

* Added Deep Wipe function. Performs a low level erasing of the user selected partitions.

* EDLbackup injected install script has been completely revamped to solve latest issues with big system files when they grow bigger than 2GB. The file created now ends in iEDL.zip (TWRP Installable+EDL zip file). Please remember that the EDL files created by this util can be installed in TWRP like any other ROM file in addition to standard EDL flashing mode.

* Re-arranged options in two pages.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
The deep wipe functionality is now integrated into the TWRP Labs Mod.

Regarding your second point, the program is fully ready to do it, and It can create a huge zip file containing the backups. The problem is the filesystem compatibility with files bigger than 2GiB and the busybox unzip integrated in TWRP. It doesn't support multipart zips so I cant create zip files bigger than 2GB. I have to find a static binary of the unzip aplication for ARM and solve some other issues before adding the huge userdata partition to the iEDL backup. It is not a critical factor since the data and Internal Storage can be backup using other tools inside the TWRP Labs.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] samo_lego:
Thanks so much for such an active development [MENTION=319057]Oki[/MENTION]!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Guido83:
So it happend now the second time while trying to flash a GSI (a few times flashing GSI worked though).

It starts flashing the system Image and then the phone is going to DFU mode before finishing the progress. After this, TWRP is broken
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
If you guys did a clean wipe,first reboot to twrp if u want flash something new!!!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ??evan:
Help me

Im trying to start using the axon 7 and it won't take Google account info what do i do
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Sorry guys, with that information I can only think on a bad download of the TWRP, flashing a GSI doesn't even used my scripts but the standard TWRP code. I can't help more if you do not answer my questions.

In order to avoid the DFU mode, use the proper bootstack with EDL hw key combo.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
You can use the unlock Google function to remove the Google account lock of your phone. It is under Advanced > Oki Labs > Unlock menu.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Guido83:
Sorry for not answering your questions. Here we go:

What language are you using in TWRP? - english

what bootstack? - DrakenFX's ZTE_A7LOSv1_UniversalBootStack

what ROM? - Benzo ROM GSI - latest

what vendor partition configuration? - 500MB at end of System (Vendor Creation tool from LOS16 thread)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Not really required. Alternatively you can unmount and remount the partitions from the Main > Mount menu.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JTruj1ll0923:
Hey Oki thanks for the development of this! One bug I have to offer that I don't believe I've seen is with the vendor partition. I took the vendor.img from LOS 15 and tried flashing that to vendor but I always get an error saying "cannot flash images to file systems." This TWRP can flash to other partitions with img files, just not vendor. Also I tried the TWRP from LOS 16 and it flashes the img just fine, so it's not the img. Thanks again!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Everything seems to be fine except for the bootstack you are using. I've seen some problems not being able to enter into EDL mode when using that B12 bootstack, judt test the button combo to see if you are affected too. This is the B12 bootstack I use: AXON7-Oki_REMIX-B12_BOOTSTACK-iEDL.zip flashing using MiFlash for better compatibility. Regarding the GSI, I have tested it a lot since it is huge. I have been testing the image splitting with it many, many times when developing the EDLbackup tool. I haven't tested the Vendor creation tool from LOS16, maybe it was doing something weird, but many other people have use it without any issue.

Have you checked the MD5 of the file before flashing? Download problems happen more often that we all would like. I am thinking in release them not as an IMG file but as an installable ZIP file instead. just to avoid these issues.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] achilles912:
If somebody want help with Deep Flash Cable just type google.

(Phone must be off. You must cross green cable with black(ground) cable, plug cable into phone for 10 sec with crossed cable, after 10 sec or more untwist this cables and done. YOU ARE IN EDL MODE)

I tired with VolD+VolU and plug in cable but is doesn't work for me. IDK why.

https://www.youtube.com/watch?v=yI8XSFi5vpQ

After that download ABD, unzip, Hold SHIFT in folder with ABD, type open console here.

Download last recovery, rename it to recovery.img and type in console

fastboot flash recovery recovery.img

What language are you using in TWRP? - english

what bootstack? - AXON7-Oki_REMIX_B12_BOOTSTACK-Flashable_EDL

what ROM? - Pixel Experience 9 GSI

what vendor partition configuration? - 500MB at end of System (capacity from data)

FTW didn't work for me. My computer didn't see ADB. My phone was broken for 2 days and I found solution to the problem.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] joaste:
Hello Oki,

I tried to install your bootstack file, but only get options to backup various items (os, bootstack, etc.). None of the options mention flashing a bootstack. Am i missing something?

Thanks for your help and the work you're doing!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Flash using MiFlash.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Aviver:
Hey Oki, i know this is picky but please can you change that booting image? This is a amoled screen and booting with a full screen yellow page :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
5 seconds of a full screen image don't drain a lot of battery compared to the drain of the kernel booting. Nonetheless, I am open to any other splash. Any suggestion other than the bland original one?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Aviver:
The original is perfect, you can just change the logo color? And add it too to your twrp. That would be perfect :D

Anything with black background is perfect, it contrasts and our eyes thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
[MENTION=319057]Oki[/MENTION] whilst trying to restore a FULL backup of my havoc rom, via twrp, I get 'Error flashing xbl partition' and then get stuck on 'Restoring xblbak partition'. Waited 20+ minutes to no avail. It was stuck.

any idea why this is? I even deep wiped the system after normal wiping, just to ensure that nothing has any problems.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Anon1mus:
Any recommendations for somebody with the issue of not getting to EDL mode after having the LOS bootstack? I intend to use yours if I can get this thing working again.. I was using your twrp but didn't see the stack until after bricking
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] alwynjoshy:
currently i am on NFound's Treble 3.2.1-8, so flashing

TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod.img would cause any issues like loss all data , i am not using any encryption
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
No problem, it will work fine.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Some units have some locks. Use MiFlash, that will overwrite everything.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Alright, will try when I get home. Thanks!