yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
[MENTION=5672995]jcadduono[/MENTION]

Can you or anyone else test this for me, use an USB-OTG with your TWRP 3.0.3?

i was trying some stuff and seems like TWRP 3.0.3 doesn't read / let me select OTG's, Tested with 2 different drivers and can you PM have a personal question for future ZTE Updates, thanks man
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] borijess:
Why does TWRP take so long too load?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimbo77:
Did you change your data partition to F2FS? I'm assuming you did, jccaduono has explained that it is because of the chkdsk process that is done in every boot and unfortunately it does not play good with F2FS, i guess that's the trade to have an 'improved' data partition.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] borijess:
I don't think I ever changed anything. How can I check if I did?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lafester:
You would know if you did. How long is it taking to load?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
yeah I've had OTG fixed for a while now I'll put up a new build soon
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] borijess:
Like a minute or over that.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] djfred:
I have A2017 Chinese version 128/4 G model, currently have B07 and can upgrade to B13

anyone try this method successfully on my build and Chinese version?

Need to root and install Xposed .
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
Looking for input on https://build.nethunter.com/test-builds/twrp/zte/twrp-3.0.3-1-ailsa_ii.img before posting it on twrp.me

I'd like to know first of all if it is working correctly to decrypt on the Nougat test builds (ZTE is unwilling to provide me with a copy :))

Also if there are any bugs.

I made some pretty big changes to the kernel, and it's actually running on a configuration that is the absolute minimal to get a bootable TWRP environment in hopes it would reduce boot time a little bit. OTG is also fixed.

It will pull decryption libraries from system and prioritize them over the built in ones (from B29) using a script I developed for the OnePlus 3 and 3T.

The kernel itself is only 4.5 MB after gzip! I managed to reduce the dtb to only 300 KB :)

(it was a fun task!)

For those using ext4, I've included a zip in the first post of the thread that will switch the default partition type of TWRP to ext4, allowing it to decrypt ext4 partitions should they be encrypted. Flashing the zip again will default it back to f2fs.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tasar:
OTG is working again :good:

Is it secure now to save/restore EFS because older version overwrite efs2.emmc.win with efs1.emmc.win?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
I have seen your new approach for getting the decryption blobs straight from /system and I love it! No need to include them with the recovery anymore!

I have seen the script at the OP3T repo.

I wonder would that approach work on all Snapdragon arm64 based system's despite their SoC series (obviously same generation).

Like it probably works on the 821/820/625/etc series but might not work on 810/615/etc.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
Should work all the way down to Snapdragon 800.

Some devices might have an additional library needed that you would need to include in the script, and of course you would need to change lib64 to lib on 32-bit.

I always include a set anyways in case user boots recovery without ROM installed.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Everything seems to be working fine here. F2FS data boots a little faster. Only a little.

Instead of flashing the swap zip to commute between F2FS and ext4, you could integrate this option as a check box under the settings menu. Just an idea.

Currently F2FS mounts do not use optimized options in twrp. Inline xattr and data, noatime and nodiratime would increase not just the boot time, it would help on creating optimized F2FS partitions when restoring them.

One final thought on the F2FS implementation, it is very outdated. Current Android Linux kernel includes the inline_dentry as a default option, while the F2FS code in the TWRP kernel doesn't even support this option. It would increase the free space and reduce the reads, access time, battery usage, etc... The latest version is included in the 4.10 kernel. There is only one problem of backporting those drivers to TWRP, but there is a simple solution. If the new drivers are included, the default behavior will have inline directories into the inode (a lot better) but it is unsupported by the current kernel. Another checkbox option in the TWRP settings could set inline_dentry mount option or not to make it backwards compatible.

Another point to finally integrate the 4.10 drivers could be the decision of freeza, willing to integrate the latest f2fs drivers in his BeastMode ROM. So at some point we would need a TWRP with support for the latest F2FS implementation for the Axon 7.

Thanks for your time on investigating on the F2FS issue. :good:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
I can make a build with the f2fs-stable backport f2fs drivers but be aware that using it will restructure your f2fs partitions making them incapable of booting any kernel which is using the Android/Linux stable f2fs drivers from 2014. (this means no ZTE stock)

I did the same for OnePlus 3/3T since many were using these drivers. Unfortunately it brings up lots of problems due to the incompatibility between 2014 and 2016 f2fs and the amount of people reporting issues about it is driving me mad.

Should I upload a build with these drivers, I will ignore any and all bug reports related to it.

Update: Included in a section on the first post.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
BIG FAT Thanks!!!!

Yes, the data partition won't be compatible, however if TWRP could switch between using inline directory or not, just activating inline_dentry or noinline_dentry mount options. Setting noinline_dentry makes the F2FS implementation backported from 4.10 fully compatible with stock kernels.

Could you test setting the mentioned options to the fstab of the recovery kernel in order to reduce the boot time? noatime and nodiratime mount options should help a lot on that by removing the atime update for files and directories.

I am waiting for [MENTION=309990]freeza[/MENTION] to release the next BeastMode Kernel with backported 4.10 F2FS drivers to benchmark this new implementation.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
I will test this today and report back.

Update:

TWRP mount options: /dev/block/sda9 on /data type f2fs (rw,seclabel,noatime,nodiratime,background_gc=on,user_xattr,noinline_data,noinline_dentry,flush_merge,noextent_cache,mode=adaptive,active_logs=6)

TWRP boot times:

atime,diratime: 2m24s

noatime,nodiratime: 2m23s

Operating system.....

BOOTS!

I'll let you guys test it out and report back if it breaks things as well.

https://build.nethunter.com/test-builds/twrp/zte/twrp-3.0.3-f2fs-test2-ailsa_ii.img
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Looks nice. The surprise was the reduction of only 1 s between atime and noatime. I sincerely was expecting a significant gain, about 30% less. I was wrong about that but right about backward compatibility when using noinline_dentry.

I will test it ASAP. As default you can also activate inline_data and inline_xattr since the old 2014 implementation already supports those mount options. Only inline_dentry is the difference. The directory structure inside inodes in 4.10 F2FS drivers is not supported in 3.18. So to maintain backward compatibility while ensuring the best compatible performance, I'd set noinline_dentry, inline_data and inline_xattr along with nodiratime, noatime and nobarrier. Backups could be faster that way. These settings will restore a data backup with almost fully optimized F2FS structure.

I'll test it tonight at home.

Thanks again!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
[MENTION=5672995]jcadduono[/MENTION], I have done extensive testing with all the versions. I have recreated the structure of /data and /sdcard with the new drivers and everything is working fine. My findings:

Boot to recovery time in my case:

3.0.3-1 (3.18 f2fs drivers): it takes 52 s to boot to recovery.

3.0.3-f2fs test1 (4.10 f2fs drivers with atime and diratime) it takes 47 s to boot to recovery.

3.0.3-f2fs test2 (4.10 f2fs drivers with noatime and nodiratime) it takes 45 s to boot to recovery. This is 13% reduction in time respect to older drivers without nodiratime and noatime but no much difference from atime and diratime.

The default options still require some optimization:

noextend_cache should be switch to extend_cache to increase cache hit ratio (compatible with 3.18 drivers).

noinline_data should be switched to inline_data providing extra performance when restoring a backup (compatible with 3.18 drivers).

noinline_xattr should be switched to inline_xattr providing extra performance when restoring a backup (compatible with 3.18 drivers).

Maintain noinline_dentry to keep compatibility with 3.18 drivers. However placing a checkbox in the settings to switch this on would be nice since future kernels will use 4.10 drivers.

Maintain nobarrier, noatime and nodiratime. It is a small improvement, but everything adds to a final number.

The final options string for the backported drivers validated in my tests is:

nosuid,nodev,noatime,nodiratime,discard,user_xattr,inline_xattr,inline_data,noinline_dentry,flush_merge,nobarrier,extent_cache,mode=adaptive

Could you create a new version with this set for /data and /sdcard?

By the way, If you have time, probably experimenting with fastboot mount option could reduce the boot time to recovery. It affects performance, but performance within twrp won't be noticeable. Boot time could be more important. So, if you prepare a couple of versions, with and without fastboot mount option, along the rest of the previous options set, then I could do all the testing.

Thanks again!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gpz1100:
I'm on the latest stable twrp (3.0.3-1).

Have a strange issue after factory reset, it seems stuck indefinitely on the axon 7 logo. After some period of time, forcing a reboot, it boots right up in ~30-45 seconds.

More details in this thread: https://xdaforums.com/axon-7/help/stuck-axon-7-logo-factory-reset-t3542715

Seems as though something weird happens with /data.

Thoughts?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Have been using TWRP 3.0.3-0 since release on A2017U.

Downloaded & flashed TWRP 3.0.3-1 via the Official TWRP app, but rebooting to Recovery leads to a black screen.

Used the app to download and reflash TWRP 3.0.3-0, but have same results.

Is this an app issue? Can you offer a suggestion to regain TWRP?

Phone boots OK to system (Rooted & bootloader unlocked)

Thanks.

Edit: I should note that I had converted /data partition to F2FS prior to this, but had been in & out of TWRP 3.0.3-0 several times before the attempted upgrade and black screen issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
please let me know if it changes with https://build.nethunter.com/test-builds/twrp/zte/twrp-3.0.3-2-ailsa_ii.img

if it does not, you will need to gather logs for me, you can do this by booting to system and running:

adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar

you will need to make sure adb works before doing this, so enable USB debugging.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
With TWRP not available, do you have a recommended method to flash the 3.0.3-2 image? Terminal emulator?

Flashify crashes. Interesting the -2 file size is about twice the size of the -0 or -1.

Edit: I should note that I had converted /data partition to F2FS prior to this, but had been in & out of TWRP 3.0.3-0 several times, made & restored backups, before the attempted upgrade and black screen issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
on pc in fastboot:

fastboot flash recovery twrp.img

on phone terminal, from internal storage:

su 0 dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery

on pc using adb booted into rom:

adb exec-in su 0 dd of=/dev/block/bootdevice/by-name/recovery < twrp.img

so many ways to do it...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Yes, so many ways. Didn't know if there might be an "approved solution" since this was a test build.

I flashed the -2 via Terminal Emulator and now can boot back into TWRP.

FYI: quite long on TWRP Splash screen (a measured 71 seconds).

Thank you!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Just curiosity, What is the change in this release?

Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
f2fs optimized mount options on backport, k3.18.47, LA.HB.1.3.1.c1-20600 that's all, not really a release i just didn't add the -test suffix when i was building

i wouldn't say it is ready for release as i am still in the middle of debugging an issue in the kernel where the screen locks up, doesn't seem to be showing up in twrp though

oh. and the changes since twrp 3.0.3 which includes slight theme code changes (so 3.0.3 and older themes are actually incompatible, sorry)

power key now turns screen off instead of just locks

twrp backup tar format changed, now backs up linux capabilities too (fixes nougat backup/restore)

as well as the rare commit by me https://github.com/omnirom/android_bootable_recovery/commit/c51bd35 which makes both ext4 and f2fs decrypt work on the same build :)

theres quite a few more commits, Dees_Troy just merged like 20 of them sitting in gerrit which fixes a lot of longstanding issues!

all of this is mentioned in the first post btw....
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Hmmmm.... I see, the best mount options, and compatible with Android kernel 3.18 up to 4.10. This should work now for everyone with f2fs data partition. I miss discard and nobarrier mount options, but performance is not a problem in TWRP. Good choice. By the way, it works perfectly.

Nice way of decrypt ext4 and f2fs without the need of a patch. It looks like it will soon become 3.0.4.

By the way, could you try the mount option "fastboot" for f2fs? It should speed up the boot.

Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
i don't think you know what fastboot mount option does, and if anything it will slow boot speed even more (0.3 second mount time -> 0.1 second mount time, /data scan 75 seconds -> 85 seconds)

almost all of TWRP's boot time is scanning /data

if i turn off the /data scan, the loading screen only lasts 1 second

hmmm it looks like i can't boot old f2fs drivers now again, yikes, maybe more modifications needed...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
I see, the problem is not the mount but the file scan. In such case fastboot option must be slower.

Have you considered the use of sync mount option to ensure the f2fs partition is synced in an event of a reboot? However if sync is executed before reboot or shutdown it would be enough.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
In Linux, at least as early as 2.4, a sync always occurs before power down, including after kernel panics and whatever else. The only time a sync would not succeed is in immediate power loss (very unlikely to happen with non-removable battery), most kernels should have triggered safe shutdowns at 0% or low voltage battery.

sync && reboot is just a habit from the old days.

Of course, when using OTG storage, always remember to unmount (also triggers sync) it before removing it!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
So nothing to worry about in Android. That was my only concern about F2FS, but in this case I see it is completely safe.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nujackk:
[MENTION=5672995]jcadduono[/MENTION]

Can i just flash back to 3.03, seems that 3.0.4 has borked my wifi.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
You can...But it's not TWRP that broke your wifi. You must have flashed a custom kernel at some point. You need to restore both system and boot to go back to stock.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nujackk:
Thank you,
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] yunowork:
So i guess i'll have to be the noob and ask how these instructions apply for A2017G?

I do not understand these instructions because it's not clear (at least not for me) what is needed and what not. From my naive understanding of android i would assume that, if i were to use the unlockkit, which is for the U, the U firmware would brick G or at least reduce capabilities such as LTE bands, etc. Can you possibly clear this up for me, because i really don't want to trash 400€.

Since ZTE ships the devices with the same stock rom, my understanding of unlocked bootloader is as soon as you activate it in your developer option, it's unlocked. What is different with ZTE?

Also, this is the first time that any android device manufacturer had such a fu**ed up and annoying procedure to unlock your device. Not even Samsung was that bad, and they were the worst out of all brands i had until now.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
I'm guessing A2017G users can flash that signed TWRP somewhere in the forums then flash the unlockable fastboot from that. Can someone confirm? If so, that's a hell of a lot less work... :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MrWilsonxD:
I can't answer all you posted about, but here's some.

Simply ticking the option for allow bootloader unlock does NOT unlock your bootloader.

The process of unlocking bootloader for this device for me was relatively simple, and informative. There's a nice thread about it, here.. https://xdaforums.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165/page36
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
[MENTION=5672995]jcadduono[/MENTION]

Say I wanted to create an openrecoveryscript and one of the commands would be wiping the system would it be

mount system
cmd make_ext4fs /dev/block/bootdevice/by-name/system
unmount system

or would it be

mount system
cmd twrp make_ext4fs /dev/block/bootdevice/by-name/system
umount system

Or would neither of those commands work and I would have to do "adb shell twrp make_ext4fs /dev/block/bootdevice/by-name/system" from Windows commandline?

Also in general would any regular shell command be cmd [command] and any twrp specific command would be cmd twrp [command]?

It's because I'm making a tool for someone on Z-Community that will unlock the bootloader, flash twrp, and flash lineage
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] chas123:
Try:

format("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "0", "/system")
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Isn't that for an updater-script inside a flashable zip? I'm talking about the openrecoveryscript in /cache/recovery/ that is executed when TWRP boots.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nupi:
There is a bug in twrp 3.0.3-1: it fails to mount lineage encrypted /data once a password different from screen lock has been set for it.

Upon a clean flash, the following seems to reproduce:

1. Setup phone

2. Set password

3. Encrypt phone

So far so good, twrp can mount the encrypted /data with the previously set password.

4. Change encryption password

twrp is now unable to decrypt the volume, using either the old or the new password.

I have attached recovery.log
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
only accepting bug reports for 3.0.4, is it an issue in 3.0.4?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nupi:
Now that you mention it, it indeed works in 3.0.4:rolleyes:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JP_93:
I tried to flash lineage from stock B10 but now my phone keeps rebooting into twrp. I'm using twrp 3.0.4-0, any advice?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
In TWRP settings page disable ask app install

It causes TWRP to crash when it asks
[Google Pixel Questions & Answers] Blues fan:
I was wondering does the Pixel have expedited and free shipping like most of the carriers do like second day or overnight, or do you have to pay extra for that? Google has free shipping but says only for lowest cost
[Galaxy S 5 Q&A, Help & Troubleshooting] olrakizz:
My samsung s5 sm-g900l .. When my s5 is connected to pc. It will not bootloop. But when i disconnected in the pc 2 mins it will bootloop.. What should i do? Im done reinstalling stock rom. But still it bootloop.

Help please.
[Android Q&A, Help & Troubleshooting] Mohanasundaramrebel:
I have stock recovery of coolpad note 5.i need help how to compile custom recovery using stock recovery
[Android Q&A, Help & Troubleshooting] milkyway3:
If you have root, download the flashify app from play store and just browse and flash the .img file

If you dont have root, reply me back I will give you detailed information about flashing through your pc

Regards milkyway3
[Android Q&A, Help & Troubleshooting] ViperZ31:
i have coolpad note 5.

Can you help me root my coolpad note 5
[Android Q&A, Help & Troubleshooting] Kareppa Pujeri:
My device void Warranty....????
[Android Q&A, Help & Troubleshooting] Ashwinrg:
Yes. Rooting voids your warranty.
[Android Q&A, Help & Troubleshooting] D.L.Tejas:
Hey bro are you having Coolpad note 5 recovery? ?
[Android Q&A, Help & Troubleshooting] debs_newbie:
coolpad note 5 Custom ROM

Can anyone help me with a good custom ROM and rooting for CoolPad Note 5. Even with such high specs the phone is really slow. I'm unable to use the phone.
[Android Q&A, Help & Troubleshooting] chandra 007:
How to root cool pad note 5 replay fast guysss plzzz
[Android Q&A, Help & Troubleshooting] krisshna sai:
how can i get twrp in cool pad 3600i

bro i nead solution for this can any one help me about thie
[Android Q&A, Help & Troubleshooting] IMTHI:
Dude pls help me I need custom recovery for Coolpad 3600i.i tried to root my device with and without pc but I failed pls pls help me to root my device and custom recovery

---------- Post added at 07:29 PM ---------- Previous post was at 07:25 PM ----------

Can we flash Moto x style 3.10.84(prefs)TWRP recovery to coolpad note 5 3.10.84(prefs)
[Android Q&A, Help & Troubleshooting] IMTHI:
I can help you

If u have stock recovery of coolpad note 5 upload the link i can compile twrp for your device

Regards

Imthiyas
[Android Q&A, Help & Troubleshooting] GuestD2274:
Need for stock recovery

Can anyone give me the stock recovery? I need that.
[Android Q&A, Help & Troubleshooting] Pratyakshchaudhary99:
can you please help me to get that.
[Android Q&A, Help & Troubleshooting] Stark_Inc:
Hi all,

I was wondering if perhaps someone might be able to provide the stock firmware for Lemfo's Lem5? Really like the look and functionality of this Rom and would like to try to port it to another watch.

Thanks
[Android Q&A, Help & Troubleshooting] Timeku:
i just got this watch. Amazing piece of hardware. I can do this. in what format you need it?
[Android Q&A, Help & Troubleshooting] Stark_Inc:
Oh. That would be great!

I think if you are able to provide a SPTOOLS flashable package that would be most flexible for me, however if your only able to do TWRP backup that would be fine too.

Thanks a lot. I'll let you know how it goes.
[Android Q&A, Help & Troubleshooting] Stark_Inc:
Lem5 Firmware

Hi there,

Hope your holidays were enjoyable!

Just wanted to touch base to see if you are still able to provide the firmware for the Lem5?

Thanks
[Android Q&A, Help & Troubleshooting] Timeku:
Sorry i Dint have the time busy day's christmas etc :) but i will look into it tonight. I let you know.