yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
If you want root without BL unlock, but it will not work yet since you will have miss-match between boot and system

thats why we need B20(pre BL OTA) images. Currnet boot.img is made from post BL boot

In case you were asking what is boot.img, it is the kernel and ramdisk part of the OS
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dennis96411:
Can I flash the stock recovery image I made directly in TWRP or do I need to use tenfar's tool again?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdgillihan:
This is the reason wifi (and probably nfc) won't work, because of the mismatch. Not sure about your other question. I would say yes but I don't want to steer you wrong. I'll defer to [MENTION=1340661]peramikic[/MENTION] on this.

Always thank those who are helpful...and just ignore those who aren't.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
I would think either should work. TWRP can flash img files directly now. And tenfar's tool should do it as well just like it falshes TWRP in the forst place
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rczrider:
Alright, done :)

Stock boot and recovery are already uploaded and I'm in the process of uploading my system dump (locked B20).

EDIT: files can be found at http://xdaforums.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
The B20_Boot OTA affects fastboot, boot, recovery, and system. As [MENTION=1340661]peramikic[/MENTION] clarified, we know yet if the ACTUAL "fastboot oem unlock" changes anything else while running. We'd probably need to compare all the partitions after B20_Boot OTA and after the actual unlock to make sure of that one.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Jose-MXL:
Thanks for the clarification, I wasn't sure which partitions so I limited myself to point system image only.

The fact that all of these partitions and probably something else gets modified with B20_boot, makes imperative to backup any partition possible with tool development (tenfar did for us), and to continue doing so until ZTE provides stock images, which I doubt will happen in the short term.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HonestOtter:
Every time I go to TWRP I get the "Mount Decrypt Data" "enter password".

I have spent 4 days on the XDA forum trying to get rid of this.

I have not started using my phone because I can't do a back up so why bother changing things.

PLEASE anyone who actually know what this is Please tell me how to get rid of it. I have formatted my data every way from sunday. Tried every boot image I can find. Nothing on the site has worked.

I am using Rcriders System image, not sure if that matters. I have no idea if I was b20 when I started using the tool 4 days ago. Any backups I have made of my origninal system or boot or recovery are gone.

I have the latest version of ADB and every file anyone has ever linked. I am using twrp 3.0.2-0 Root would be nice but the only thing I care about right now is being able to make a twrp backup of my data.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] raber111:
Flash TWTP from the post with decryption support. Or format data and you will loose all of your data

Отправлено с моего HTC One M8 через Tapatalk
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HonestOtter:
I have no data to care about. I have wipped and formated the data at least 100 times so far, yet any time I go back into twrp I get the stupid password and I can't backup my data

PLEASE I am desperate I have spent 60+ hours on this phone since i go got it friday. PLEASE anyoene who actually knows what this is and how to get rid of it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dennis96411:
Wait, did you use tenfar's tool? If so, did you also flash boot.img along with recovery.img?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HonestOtter:
Yes I followed every guide and comment anyone has made in any of the axon posts.

I used tenfar first tool which killed the wifi

I used tenfar second tool (modified boot image from Rcrider)

through the hundreds of times I have used the tool, wiped the data with twrp, the stock recovery and even inside system settings, I have never been able to mount the data after running system. Once I go into system the data partition gets encrypted again and twrp can't mount it. I have seen others have that issue with short replies but none of them seem to resolve the issue.

I am sure I am doing something wrong and willing to try anything, even if I've done it a dozen times already.

ultimately what I want is root, and the ability to make backups, and load custom roms in TWRP. I don't care about OTA or any of that stuff.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dennis96411:
Did you make a backup of your original boot image before you modified it?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HonestOtter:
I did but in all the renaming of files I believe it is lost forever.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] 37_:
I have the same problem, I have been able to mount the data in TWRP after a factory reset in original recovery

steps: flash boot without flashing TWRP -> then enter default recovery and wipe data -> then turn off phone and flash TWRP

BUT!!! Once I go into android system the data partition gets encrypted again and twrp can't mount it anymore :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Taconut:
I'm in the same boat as you here. I could personally care less about the backups ATM, but I'd like this issue resolved as well. If you figure it out, please let me know and I'll do the same for you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
It's too late for your situation, but for others in your situation, if all you want is something similar, it'd be better and safer to just ask for the official unlock, rather than flashing all these sideloading versions.

And to be really safe, it shouldn't be done until we actually get those precious factory images.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HonestOtter:
Are you suggesting that if I buy another phone and go through the official channel that some how I will be able to use twrp?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dennis96411:
I'm not sure if this matters, but I also flashed this after allowing system modifications in TWRP: http://cloud.tapatalk.com/s/57bf4e0a26b02/no-verity-opt-encrypt-2.1.zip

Maybe it will solve the encryption problem? Try wiping your data partition and flashing this if you have the problem.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
People have been having troubles with various things being odd when flashing the unofficial locks. The people that used TWRP early on had done the official unlocking AFAIK, which pushes all the correct bits to the phone. I also think there are 2-3 versions of TWRP running around, and I'm not sure which ones are the working one(s).

I think people are running into trouble because they are flashing each other's images, and they haven't all been verified as actually being identical to other phone's yet.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HonestOtter:
Ive tried that before, I just get a black screen I think. So are you able to mount the data partition in twrp?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dennis96411:
Yeah, it seems to work completely fine for me. Data mounts fine for me, and I can backup every partition. I see the following console log:

Data successfully decrypted, new block device: '/dev/block/dm-0'
Successfully decrypted with default password.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] XblackdemonX:
But you have the official bootloader unlocked right?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gcharma:
[MENTION=4376211]dennis96411[/MENTION] Can you confirm if you still have avoided the password prompt? I'm finding that I can get into TWRP after flash, but once I set up my phone the password prompt appears. I'll be trying your ZIP file in a sec to see if that changes anything.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dennis96411:
My phone has been completely setup, and I can reboot right into TWRP and do everything with no password prompt.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gcharma:
Argh... so interestingly, I flashed your ZIP and the device crashed (powered down) every time I tried to boot to System. I re-flashed the modded boot.img that came with the locked bootloader root tools and I'm back in. I'm going to set up the phone now and see whether or not anything changes for me this time around.

---------- Post added at 06:40 PM ---------- Previous post was at 06:11 PM ----------

K, so looks like first reboot after setting up the phone resulted in the password prompt. Reflashing the recovery didn't help, so I guess I'm stuck again. For the record, I:

1. Flashed my stock boot.img and recovery.img images using tenfar's tool.

2. Flashed the modded boot.img using the tool.

3. Booted into recovery (stock, at this point), did factory reset.

4. Flashed the modded recovery.img.

5. Booted into recovery (TWRP), no problems. All mounts accessible.

6. Went through initial phone setup (did not encrypt any volumes or set up a password/PIN/fingerprint), ran adb reboot disemmcwp to unlock /system (this last step I only ran this most recent time - previous times I haven't and the TWRP password issue still cropped up).

7. Boot into recovery, password prompt.

Any ideas?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dennis96411:
I left my boot image completely stock the entire time I had my phone. This is what I did:

1. Used tenfar's tool to backup my boot and recovery images (I didn't flash anything)

2. Flashed OTA unlock package in stock recovery

3. Unlocked bootloader

4. Used fastboot to flash TWRP image

5. Booted into TWRP and allowed system modifications

6. Flashed that ZIP file and SuperSU

I also did the disemmcwp step, but I don't think that mattered.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gcharma:
Interesting... so the difference between our scenarios is the unlocked bootloader. Not sure I'm comfortable enough yet to unlock it for full TWRP functionality, but good to know that if I really need it there's still a step for me to try. Thanks for the detailed information!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HonestOtter:
well that is sad, might have to send my phone back, I made a back up of my boot image but when I tried to put it back my WIFI didn't work. somewhere between that and when Tenfar released the second tool, I lost my original boot image. Hopefully needing the original boot image is not key. Maybe someone with the Decrypt issue can try your method and see if it fixes the decryption issue. I am just to burnt out to try anything at this point.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Flapjack:
I followed the same steps as you, minus step 1. The guide I followed never mentioned tenfar's tool, so I didn't even know about it. All seemed fine until I flashed the SuperSU zip from TWRP, and now my phone will not boot. It just sits at the ZTE logo.

I've tried flashing the unmodified boot, as well as stock system, but the closest I can get it the Axon logo, where it also hangs.

I'm not sure what to do to recover the phone at this point. Any help would be GREATLY appreciated.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
Do you have boot and system backups from TWRP after unlocking? You should flash those and see if it get's you up and running. If not, wipe data, cache, dalvik, Format data and factory reset just to make sure and then reboot

If you don't have system, check this post but the dropbox account has a daily limit on it i think (thank you [MENTION=2782065]swehes[/MENTION])

http://xdaforums.com/showpost.php?p=68248798&postcount=53

for B20_boot image maybe [MENTION=2782065]swehes[/MENTION] or [MENTION=3044858]DrakenFX[/MENTION] has a dump of one already
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dennis96411:
The logo might sit for a good 3 to 5 minutes on the first boot, so I'm assuming you allowed it to sit at least that long.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] R800x_user:
Hey since your axon isn't having problems and twrp is funtional why not backup and upload for someone to try to restore that backup but I'm pretty sure the password thing might be a hurdle til then

:eek:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Barsky:
Decided I wanted to redo my phone today. I went into twrp and formated data and also did an advanced and formated all but system. Now, for some reason my phone thinks it only has 4gb of Internal/Phone Storage. Obviously, this is a big problem.

Any idea how to fix this? Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Flapjack:
Yeah.... I let it sits for 20-30 minutes. :(

What boot file should I be running right now, considering I've already restored the system partition to stock, and still have TWRP installed?

**EDIT**

I can now get into my phone, following the "How to restore" thread. After that, I have no wifi. I can then flash the original tenfar modified boot (the one that is now crossed out), and I can get wifi. But as soon as I flash SuperSU version 2.76, my phone is bricked and I have to restore

How is everyone else getting root??
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gcharma:
Via this SU binary: https://play.google.com/store/apps/details?id=me.phh.superuser
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dennis96411:
I flashed the 2.65 zip file and then updated the binary once booted into the phone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Flapjack:
I wish I had seen that before I tried SuperSU 2.67. Now I can't get wifi back. I'm not even going to worry about root until I can get wifi working again.

I would try that, but since 2.67 softbricked it, the wifi doesn't want to work again... no matter how many times I restore it.

How can I follow those same restore steps and not have the same outcome. What exactly does flashing the SuperSU zip affect? I can't imagine it's anything more than the system and/or boot partitions.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
The boot partition contains the kernel and initial ram images though. If it's being patched incorrectly due to incompatibility, it wouldn't be surprising to have some odd issues crop up.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] cdeister:
I think this version of TWRP contains the fatal EFS bug that has been reported in 3.0.2-1

http://xdaforums.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119

Or something about it interacts with the axon in the same manner. Alternatively, I screwed something else up. But I have been reading a number of radio brick axon 7 posts so I strongly suspect it is this efs bug. I had made and restored an efs backup with this version and radio bricked my phone. I tried everything and nothing worked. So, I chalked it up to my stupidity for flashing anything without factory images (I had a complete backup) and was moving on. Then I read the bug post and it seemed like my problem. Their fix is easy and rational, you will need different paths for the axon though:

adb shell dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/modemst1 bs=16384

adb shell dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/modemst2 bs=16384
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] manu7irl:
People with no wifi/no service, this is a TWRP issue.

http://xdaforums.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119

Check if it is a good solution.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Flapjack:
To be honest, I don't know if I ever did total backup and restore, but I am going to guess that is probably the issue. I always select the EFS partition when backing up, so I bet that's what it is.

Does anyone know what the proper command would be with the Axon 7 US?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] manu7irl:
You can backup the modem partition

dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Flapjack:
Thanks, but I was referring to the command in the thread I linked, which someone theorized that a restored EFS partition in TWRP 3.0.2.x might be causing the dead modem issue. Version 3.0.2.1 has a fatal bug that causes some phones not to boot until the EFS command is fixed with a command, so the hope is that someone can come up with a similar command for our phones that fixes the EFS partition, and the modem issue as well.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] manu7irl:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384

adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384

Add these two to the restore script.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Flapjack:
These are exactly the same commands as the page I linked. I was under the impression it was not the same for our phones. That path doesn't even exist on our phones, as it was crafted for a Nexus device. That command would not even run.

Here is what our folder structure looks like. If it's as simple as putting the correct path between "/platform" and "/by-name", that would be great, but I'm not going to assume anything at this point.

/dev/block/platform/soc/624000.ufshc/by-name # ls
aboot cmnlib64 dsp keymaster modemst2 sec xbl
apdp cryptkey echarge keystore msadp splash xblbak
bluetooth ddr fbop lksecapp persist ssd ztecfg
boot devcfg frp mdtp pmic sti
cache devinfo fsc misc recovery system
cdt dip fsg modem reserve tz
cmnlib dpo hyp modemst1 rpm userdata
/dev/block/platform/soc/624000.ufshc/by-name # pwd
/dev/block/platform/soc/624000.ufshc/by-name
/dev/block/platform/soc/624000.ufshc/by-name #
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Flapjack:
[MENTION=3809901]manu7irl[/MENTION]

That worked!!!! You are a life (and a phone) saver!!!

Anyone who is having the no wifi/two sim icon issue, the following two commands after restore worked perfect. I'm not sure how to add them to the restore script, but you don't really need to, as long as you have a computer you can access the phone with adb on.

For me, the steps I took were to:

1) Restore using DrakenFX's uploaded TWRP backup (I also had to wipe system, otherwise it would not boot fully):

B20_Boot TWRP Backup Xposed+Root Edition Provided by DrakenFX

http://xdaforums.com/showpost.php?p=68206051&postcount=4

2) Enable USB debugging and boot into recovery

3) Type: "adb shell" and enter the following commands:

dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384

adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384

3) Wipe cache and dalvik, then reboot into system.

If all goes well, the output from the two commands should look like this:

/dev/block/platform/soc/624000.ufshc/by-name # dd if=/dev/zero of=/dev/block/boo
tdevice/by-name/modemst1 bs=16384
dd: writing '/dev/block/bootdevice/by-name/modemst1': No space left on device
129+0 records in
128+0 records out
2097152 bytes (2.0MB) copied, 0.001917 seconds, 1.0GB/s
/dev/block/platform/soc/624000.ufshc/by-name # dd if=/dev/zero of=/dev/block/boo
tdevice/by-name/modemst2 bs=16384
dd: writing '/dev/block/bootdevice/by-name/modemst2': No space left on device
129+0 records in
128+0 records out
2097152 bytes (2.0MB) copied, 0.001829 seconds, 1.1GB/s
/dev/block/platform/soc/624000.ufshc/by-name #
c:\Users\chris\Desktop\Chris Phone\Axon\modem_a2017u>

Hope this helps! Thanks to DrakenFX for the TWRP dump, and manu7irl for the idea that TWRP 3.0.2.0 was to blame for a corrupted EFS backup/restore. I could not have fixed my phone without either of them! I'm off to post this in the missing wifi thread!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I think the main developer addressed this issue but it's merged on the android 7.0 twrp. I'll backport it and run a build. The issue in the commit addresses restoration of subpartition which the efs is.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] manu7irl:
I'm glad it worked!

Do not forget to hit the thank button....

And also you could buy me a beer,

http://goo.gl/1BEqCQ
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Flapjack:
Thanks given.

Tried to buy you a beer, but page returned: "Sorry — your last action could not be completed"

---------- Post added at 11:21 PM ---------- Previous post was at 11:08 PM ----------

It would be good to see it fixed. So far, I've only read of it affecting the Nexus 6P, and the Axon 7.... with very different symptoms. Who knows what it might do on other phones.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] emudojo:
this is not working for me, I can live without WIFI for a few days, but I'm definitely looking forward for the backport, I can then recover the original boot and recovery re-install TWRP and see if that fixes both the wifi and the encrypted storage.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
Awesome.

[MENTION=3044858]DrakenFX[/MENTION], you should probably take down your mirror of the TWRP download so that other people don't download a bad one and potentially mess up their phones.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
Current TWRP works, i have restore many times DATA , CACHE, BOOT, RECOVERY, SYSTEM (EVEN SYSTEM_IMAGE 6gb) , thrust me been flashing CM13 a lot :D ,i just haven't try restoring EFS cuz i have NOT had any problems that require that partition .... i did add a NOTE about not restoring EFS Partition thou.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
New build has been uploaded TWRP 3.0.2-2

I've backported the following fixes for the subpartition restore bug (Tested by [MENTION=3044858]DrakenFX[/MENTION])

https://gerrit.omnirom.org/18939

https://gerrit.omnirom.org/18973

Download:

https://www.androidfilehost.com/?fid=24686680535467611
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] stl-soldier:
Thank you for all of your great work.

I do have an issue installing this latest version, however. I am unable to boot to Recovery when installing 3.0.2-2. I tried several times. I can go back to 3.0.2-0 successfully. I noticed that the file size is significantly smaller with the latest release (17.5 MB vs 48.1 MB). Is the build/upload corrupted or am I just the unlucky one who can't get it working?

Thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Could you do this from the previous twrp build adb shell dmesg > dmesg.txt and upload it please.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] stl-soldier:
Hopefully the attached is what you're looking for. If not, let me know. Thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Didn't seem to capture it could you do adb shell cat /proc/kmsg > kmsg.txt as soon as adb is available
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] stl-soldier:
Sorry for the delay.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I was expecting your hardware to be different, but it's the same as DrakenFx. I removed compiling of some of the unsupported device tree boards which significantly brought down the size.

adb shell cat /proc/cpuinfo