yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BrianFX:
So just to recap here, brand new A2017U, updated OTA to B25, followed the toolkit FAQ, and I'm stuck with an error screen upon booting that states: "Your device software can't be checked for corruption. Please lock the bootloader. If no key pressed: Your device will boot in 5 seconds"

I'm given the options: Power Off, Restart, Recovery (TWRP), and Fastboot.

I successfully flashed SuperSU from TWRP per that link, but that didn't fix the above issue, I'm still getting that same error message upon booting..

I'm not sure what to do now - should I re-lock the bootloader from TWRP? Or flash stock and try to start over from scratch? (is that even possible without re-locking the bootloader?) Any help is appreciated, thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
That text is normal and intended (by Google)

It is because you unlocked your bootloader.

You can only get rid of it when locking the bootloader. (Which forces you to be a sheep of the stock software.)

---------- Post added at 09:32 AM ---------- Previous post was at 09:29 AM ----------

If you get unable to mount storage. Perform the task (whichever it was that was required to mount storage) by keeping TWRP in read only mode.

You probably have it in read/write mode therefore storage is mounted and in use (busy). Hence the error message.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BrianFX:
So I just need to load fastboot, connect via USB, and run the re-lock command? (just confirming as I don't want to accidentally brick)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
Only if you use the axon 7 with pure stock software and no modifications at all. If you relock with modifications your system won't boot.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BrianFX:
I presume having both TWRP and SuperSU installed would be considered modifications?

(sorry for the noob questions, I've rooted every Android phone I've ever owned, but none were ever this complicated..)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
For one you can't even boot into TWRP with a locked bootloader. The other is self explanatory.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BrianFX:
So we need TWRP and SuperSU for root, but we can't boot without a locked bootloader, and we can't re-lock the bootloader without removing TWRP and SuperSU...

I'm obviously quite lost and should probably just give up and live with vanilla stock w/o root. I presume steps 1-7 from here will get me back there. Last noob question, at what point do I re-lock the bootloader, immediately after flashing both zips?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Hangoverr:
Sounds like a twrp installation issue to me. Use EDL and flash B19. Then use toolkit and flash twrp. Don't, click anything until twrp installation completes and it says click to return to options.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
Why would you want to relock the bootloader anyway? Just to hide the 5 sec message?!

A cell phone is running in the boot system literally 24/7. That message is seen for only 5 seconds and only when you reboot...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BrianFX:
Right now upon booting, my phone currently freezes after 5 seconds on that screen, unless I select Recovery/TWRP or fastboot within 5 seconds, those are my only two options.. Thus I assumed I had to re-lock to proceed any further..
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
No you missed a step.

Read back a few more posts.

I posted the solution for that to others and myself coming across that problem.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BrianFX:
I did see your posts and I greatly appreciate your help. Just for the sake of specifics (and so I don't shoot myself in the foot by bricking) - 1) Downgrade/flash TWRP to version 3.0.4-1, and 2) wipe data and switch to EXT4? (do both steps in that sequence?)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
Yes just make sure you use the toolkit to flash TWRP it will do the proper steps for the boot.img.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BrianFX:
The toolkit's TWRP version is 3.1.1.-0 (twrp-3.1.1-0-ailsa_ii.img). Do I overwrite that img file in the toolkit's TWRP directory with the 3.0.4-1 img file prior to running the toolkit? (so that it installs 3.0.4-1 instead of 3.1.1-0?)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
No?! Why would you do that??

The toolkit already provides the best steps and versions necessary.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BrianFX:
When you said go back a few posts, I assumed you meant your post #498 which quoted Hannover's link to the Official TWRP 3.0.4-1 thread. That's why I specifically asked about version 3.0.4-1 in my post 513 just now, partially to clarify that exact version number.. (which you initially confirmed in your reply, hence my confusion)

So if I simply re-run the toolkit, re-flash TWRP 3.1.1.-0, wipe data, switch to EXT4, reboot, I should be able to boot on B25?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ifunny:
Hi,

When i try to unlock bootloader. I flashed successfully but it can not boot up to anything and stuck at the black screen (when I hit power it has a really weak vibration). The only thing I can do is flashed back up B19 and I can boot up into system. I went and check bootloader and it is still saying LOCKED.

Is there anything I can do? Thank you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mechashef:
have the same problem right now. seems like its bricked...

downloading the b13 edl to try the unbrick option. I'll update you as soon as i know if it works

Edit : I reflashed the files and its working and unlocked
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] brack11:
Strange thing, I tried all mirrors for downloading Axon7Toolkit v1.2 from the first post but it keeps not finishing download, shows miraculos "failed networking error" and file is not saved. Any advise?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Mulle01:
You deserve a big Thankalisaurus. Be careful though, he has big teeth.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Mulle01:
Is it risky to use this to unlock BL and get Lineage on 2017G 7.1.1 B04? I've seen here that it's easy to brick the G model?

Also, am I supposed to use the toolkit when already in EDL mode? Heck it'd be awesome if someone could just give all the steps to unlock BL + install TWRP on 2017G 7.1.1 B04 lol
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] robertaramar:
If you're on Windows, Defender reports a false positive on Axon7Toolkit.exe. That may cancel the download.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] :
Does it work for A2017G with Nougat?

Does it work for Axon 7 A2017G running android N?:confused:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
The millennials nowadays don't read...

What does it say on post #3 right after information for V1.1.1?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LoidSemus:
Full support doesn't mean it's safe or hard to brick...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ttkian:
That is true. All these things (unlock bootloader, root, custom ROM etc) have risks. That's why they all have disclaimer.

If the OP said it supports a device, he/she must have tested it somehow.

If you don't trust OP, then don't do it. It's your choice really. As simple as that.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LoidSemus:
I'm not the guy who asked, I'm already on Lineage :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Mulle01:
So I flashed the bootloader unlock zip, but it says device state- LOCKED, and when I try to flash TWRP it days Flash failed!, should I be warned?

Edit: And apparently I can boot up the device normally, no harm made. But why didn't it work? It said success in MiFlash.

Edit2: Umm, can't use my pin?

Edit3: If I'm in the bootloader, on miflash my device shows up as "a66dd290" is it a good idea to try to flash the unlock zip from there?

Edit4: "fastboot oem unlock" I'm so dumb... Sry (:

Edit5: Bootloader unlocked, twrp installed, can't flash zips, not by TWRP or the toolkit, where am I supposed to "be" when flashing them? EDL? Bootloader?

Edit6: Getting Error 7, updater process ended when trying to flash from twrp, device not found in toolkit when in TWRP.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mark1003:
Can't flash recovery

First: Unlock was successful.

Then:

I have verrified the correct developer options and started to flash twrp with the toolkit.

The toolkit reboots my Axon7 to bootloader (i can see it is unlocked). then an error ist shown:

"fastboot device is not connected"

I can't see the QUSB_BULK driver, instead i see "Android" as driver desciption.

Manually rebooting with adb (adb reboot edl) i see in my device manager the QUSB_BULK driver.

Any idea? Help would be very wellcome.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] brack11:
Unfortunately this is not the case. Defender is disabled on my computer. Tried today again, same result. Is there any alternative link I could try?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcus.linkenbach:
Just do it the old fashioned way:

rename the twrp.img into recovery.img

adb reboot bootloader

fastboot flash recovery recovery.img

(You even don't have to rename the file)

Hope you know where to enter these commands ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] benhollio:
Zte a2017g jpv1.1.0b01

Does this work with the Japanese version of the Axon 7 (ZTE A2017G JPV1.1.0B01)? I see that A2017G *is* supported but I don't know if there is more than 1 version of the G.

Furthermore, here in Japan we just got our 7.1.1 upgrade yesterday, but for some incompetent reason Daydream still considers it an incompatible phone, which is why I want to root and force the phone to be daydream compatible. Will our version of 7.1.1 muck this root up?

Any advice would be appreciated.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Fonecord:
Really hoping someone can help me out.

I unlocked my bootloader & successfully rooted last night using the OP's instructions & program. For some reason my snapchat app would not let me login when I was setting everything up again. I googled it and found that snapchat dosnt work if you're rooted. I followed instructions to remove the root from within the SuperSU app. When it finished and rebooted, my phone is now stuck on a screen showing "Your device software can't be checked for corruption, please lock the bootloader. If no key pressed, your device will boot in 5 seconds"

My phone is stuck on this screen and will not boot up. When this screen first appears, i have the option to get into fastboot & recovery with the volume buttons, but if i wait too long the volume buttons dont work and I have to restart the phone again. Only boots up into this menu though and will not boot up fully.

This screen was coming on when i first unlocked the boot loader & rooted, but it did go away after the 5 seconds and boot up normally. Now its stuck and I think my phone is toast.

Can anybody help me out?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ttkian:
I believe the problem is that you removed the root. Yet, I am not sure why you want to unlock your bootloader if you don't have root. Anyway, the bootloader on this phone is a bit funny. If you unlock the bootloader, in most likelihood you need to root. If not, then you are stuck.

So, try reinstalling root and see what happens. If you install Supersu and you need to hide it for some apps, I think you can install hidesu. If you install Magisk, you can hide the root from inside the app.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] robertaramar:
I have an unlocked bootloader because I am running Los. However, I have not installed any root software as two of my apps will ceize function if I do so. So unlocked bootloader without root absolutely makes sense and does work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
sounds to me dm-verity is enabled.

depending on the unroot app/software. some unroot not only "unroot" but also re-enable dm-verity.

simply use the toolkit to install TWRP it will run the dm-verity-disable and encryption-optional script and boot your phone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Fonecord:
I fixed it!

Using the method above...I had to boot into FTM mode (Factory Test Mode = Volume Down + Power) in order to obtain an ABD & Fastboot connection to my PC, then flashed TWRP again. I didnt see this post at the time so I sort of gave it my best guess, and it worked!

From here I booted up, and setup my system before rooting again (ie; Logged into snapchat first)

Now I'm fully rooted, properly working TWRP...all is good.

There are 2 minor issues i am having though, maybe someone can help on these topics;

1 - When booting up, I have the screen that pops up temporarily saying my system cant be checked and to lock the bootloader, if no keys are pressed it will boot in 5 seconds - is there a way to remove this screen so I can boot as normal?

2 - My google Now or Google Assistant widget does not load anymore...it just shows a blank widget ..Im thinking this has something to do with the root too but not sure... any ideas?

Thanks everyone!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MagicSeeker:
WTF? After flashing bootloader unlock with MiFlash it asks me for a password to start Android. And it does not accept my password!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcus.linkenbach:
Same happend to me.

Had to do a factory reset.

But when unlocking the phone, itself resets into factory state. So it doesn't really matter.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jdgesmlls:
You need to format /data to ext4 from f2fs. It has been discussed many times in the past 10 pages of this forum.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] witchcraftz:
I have reset my phone to factory I believe by following this guide. I have to send it in for RMA.

https://xdaforums.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484

I was rooted and unlocked, so following the guide I flashed :

- A2017UV1.0.0B29_RollBackModded.zip (then put twrp back on)

- A2017UV1.1.0B25_bootstack_by_DrakenFX.zip

- A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip

Everything installed without a hitch. Am I safe to use this tool to relock the bootloader now?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcus.linkenbach:
At the time I did it it was formatted to ext4. My paritions never have been formatted to f2fs. ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kranoner:
thanks bkores for the toolkit my new axon7 rooted in 5 min awsome work bro :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jdgesmlls:
Back to stock

If I EDL flash N B19, the only other step needed to return to 100% stock is to lock the bootloader?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jman1234:
Right now I have a 7.1.2 custom rom installed, how do I use this tool to go back to stock Axon 7?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Just use the restore stock option
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Yes although I advise you not to until I release an update as the there is a chance the bootloader lock option can brick your phone which has happened to some people.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jman1234:
Oh, that's it? I thought I had to do something special for this tool since the manual thread exists and people are still doing it that way. So I should I pick the B29 option?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] wielluk:
Trojan:Win32/Fuery.B!cl found by Defender...

Umm... Anyone wish to comment on the Virus found by WinDef in the ToolKit ??? :mad:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
This has been mentioned before: false positive. It's because of the compiler that I use.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TetraFlash:
Backup Issue

I am having an issue where the backup seems to run fine, but no file is created on my system. Any ideas?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
It's in bin/backup.ab and is a known bug. Seriously can none of you read the bugs/issues post?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
bkores, unfortunately that's the new generation... they no longer read. they simply post questions even though everything has been explained perfectly well in the opening thread's.

I gave up on my threads about it. it's not worth the nerves/time. I simply ignore it and let it(them) die in stupidity. what bothers me more is that XDA isn't doing anything about it...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] brack11:
I tried to download this tool with PC without ANY antivirus, but ut keeps failing on last bite, I downloaded it with the phone but now cannot copy it to PC, neither copy nor transfer via bluetooth nor Dropbox nor wifi works. Whatever this file is it is NOT normal exe.

---------- Post added at 08:46 PM ---------- Previous post was at 08:30 PM ----------

Never mind, downloaded it with linux running then placed it on hard drive with windows, then run installation from within windows
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ralphodog:
Attempted this on a new replacement device. Flashed B19, then attempted unlock bootloader. After flashing the bootloader unlock it appears to be hard bricked in DFU mode. Not sure what the deal is, but this tool is not safe.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jdgesmlls:
It is a sad state of affairs that most people will come to this thread and read this comment and go the other way. I have a 2017U model and read over these forums for a few weeks while trying out stock etc. I knew exactly what I should (and shouldn't) do with this device because I educated myself by reading... I unlocked my bootloader, flashed customer recovery and moved around to different bootloaders all with this tool. Never once did I have a brick and if I did, it was 99.9% likely my fault.

[MENTION=2820578]ralphodog[/MENTION] - If you are going to make a statement about a problem with the tool, you best back it up with some evidence that the tool caused the issue. Right now, from experience the only problem I see is user error. Go troll on another forum.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ralphodog:
I read every single post in this thread and followed the directions exactly. Flashing B19, rebooting, then attempting the bootloader unlock flash caused an unrecoverable hard brick on the device. Maybe it's a problem with new devices, but it is definitely a problem and people should be warned against attempting this given how easy it is to do a hard brick that requires sending the phone back to ZTE.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jdgesmlls:
How about you provide some details so the community can understand your problem better? I have been reading Axon 7 forums for months and rarely have I come across a hard brick that cannot be recovered. Details or it didn't happen... :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ralphodog:
It's a DFU brick. Cannot access EDL mode or FTM mode. Attempting to power on just causes it to vibrate and flash the red LED, can't even get to a ZTE logo. It appears that if you at least get the ZTE logo, it's recoverable, but those who get nothing have a permanent hard brick.

https://xdaforums.com/axon-7/help/a2017g-totally-bricked-t3537990
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Obviously you didn't as I made it very clear in the first post:

WARNING: Some A2017G devices may be PERMANENTLY bricked when flashing packages through EDL mode due to slightly different partition tables. USE AT YOUR OWN RISK.

And you can see that the last time I edited the post was the 14th of July.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ralphodog:
Device was A2017U.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jdgesmlls:
This link is for a A2017G variant.... https://xdaforums.com/axon-7/help/a2017g-totally-bricked-t3537990

It sounds like there is likely a few things that caused this issue for you. Sorry you are in a pinch but I would check the IMEI and see which model comes back. If you were supposed to get a A2017U variant, possibly ZTE sent you the wrong replacement?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
A2017U doesn't have a DFU mode, only A2017G does which means there is no way your phone is permanently bricked.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ralphodog:
The back very distinctly says "Model: ZTE A2017U". And under device manager it comes up as "Handset Diagnostic Interface (DFU) (COM4)." If anyone has a solution it would be greatly appreciated.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jdgesmlls:
And the tool shows that you chose the "A2017U" model?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] wroclaw.17:
Axon 7 A2017 - chinese version with multilanguage

Hello

i'm new

I read 2 times whole the tread and I wonder if it is possible upgrade to nugat without losing multilanguage using the tool
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcus.linkenbach:
You won't find anything 'cause there's nothing to say about it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] witchcraftz:
Still hoping for a confirmation on this? I don't want to lock it and find I missed something...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] robertaramar:
I did it recently on my A2017G ,though with a different ROM. Worked perfectly. The repair team at ZTE did not mention anything about the phone having been unlocked.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] witchcraftz:
Fantastic. Thanks for the confirmation.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] RMSmoorenburg:
Need help with bootloader and TWRP

I think i unlocked the bootloader however i was still on the B25 and it does not let me lock the bootloader and when i try and unlock it with the right files theres an error
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] witchcraftz:
I've tried to relock the bootloader but I keep getting this message when it boots to lock:

The volume buttons don't do anything. EDIT: have to hold up&down fro 2 seconds. Then I can reboot, go to fastboot (same error), or go to recovery (opens TWRP)

Not only that but even though I flashed

- A2017UV1.1.0B25_bootstack_by_DrakenFX.zip

- A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip

I have been able to boot into TWRP..... I thought it was supposed to be gone?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tentereten:
Avira complains

Hi,

I dloaded the axonToolkit-v1.2.0. Installed it but when executing Avira free antivirus (W10) kicked in saying it had a detection of pattern 'TR/Agent.aexir [trojan]'

in 'C:\Axon7Development\Updater.exe. What is this?

Thanks,

Marc
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jdgesmlls:
[MENTION=7658623]bkores[/MENTION] - I seem to be hitting the in-call audio bug on all ROMs that I install now. I don't really want to go back to stock but I know you mentioned there is an issue re-locking the bootloader.

If I EDL flash back to B19, reboot to fastboot and issue a 'fastbook oem lock' would this be susceptible to the possibility of bricking the device? I know you said you were going to release a fix but I wasn't sure if this issue was just with using the toolkit bootloader re-lock.

---------- Post added at 10:16 AM ---------- Previous post was at 10:15 AM ----------

Read back through the thread, known false positive.