yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Guides, News, & Discussion] r00l3z:
So i unlocked the bootloader, but i am stuck in the fastboot mode menu, how to exit? i did all steps up until step 12, the phone restarted to fastboot mode, and there is a message that serial number: efdea614, secure boot: enabled, device state: unlocked. there are 4 options i can press start, restart bootloader, recovery mode, and power off. Start and restart bootloader gets me back here in fastboot mode. Anyone know how to exit it?

Edit: i managed to flash twrp from fastboot
[ZTE Axon 7 Guides, News, & Discussion] schueyisking:
struggling through with this guide so far.... fortunately just noticed people have asked some of the questions i had.

---------- Post added at 10:07 PM ---------- Previous post was at 10:01 PM ----------

PLEASE PLEASE HELP WTF......

So i get to step 10, wait for device to turn on - And I go to unlock the screen AND MY PATTERN ISNT WORKING!!!!!!!!!!

NOW WHAT???? PLEASE PLEASE HELP. WHY Is My unlock pattern not working??!!!!

---------- Post added at 10:28 PM ---------- Previous post was at 10:07 PM ----------

hiya, i'm having this exact problem.

Please help me.

I didn't see the options you say in step 2, It booted to 'android recover' . I then selected 'reboot to bootloader' and that did nothing, just took me to another screen where i could either start, enter recovery screen again, or reboot.

I then went back to recovery screen, tried to select 'apply update from ADB', then connected phone to PC.

The phone is now stuck on this 'now send the package you want to apply to the device with 'adb sideload ,filename;

What do i do!!!!!!! The phone is stuck here!

What do i send to it, and how??? I can't use my phone!

OK after a very long press, I'm now back to square 1 - stuck on this screen pattern thing.

What do i do when i reboot back into 'android recovery' screen??

The original posters guide is honestly ...The worst guide., ever made.

EDIT. i've given up. done a factory reset. i'm going to follow another guide on youtube. christ.
[ZTE Axon 7 Guides, News, & Discussion] WesTD:
There are some people who can unlock, some can't.

i'll close thread.

Try format data or flash full edl rom to recover your phone.
[ZTE Axon 7 Guides, News, & Discussion] bibiii79:
Thanks a lot, worked perfectly !!!

:good:

Cheers!
[ZTE Axon 7 Guides, News, & Discussion] muzzz33:
Many thanks , worked a charm , installed latest TWRP AND Magisk once unlocked . I thought this would be a night mare but no issues so far. I was on 7.1.1 2017G 1.20B08
[ZTE Axon 7 Guides, News, & Discussion] sebv_n:
Hi,i followed the steps in the guide to root my Axon 7 A2017, but I forgot to make a backup of the EFS folder before.

Now I have the device without a signal and if I write on the numeric keyboard * # 06 # to see my imei, it says this:

imei1: unknown

imei2: unknown

meid: unknown

But if I go to settings, in the phone information if I see the 2 imei.

I recently tried to go back to the original ROM of the a2017 b13 that I installed on the sd card, I made a wipe data, wipe cache, dalvik cache and a full reset.

After this I made a backup from TWRP of several things like the system, boot, bluetooth and I also had the option to backup the folder efs.

I did that and I just installed the original rom but I still have the device without signal and imei unknown

Can someone help me or give me an idea about what can be done?

Thanks
[ZTE Axon 7 Guides, News, & Discussion] iitywygms:
Got to this step.

8. Go MiFlash and Refresh. Your device will be there. Select from top Unlock Images folder which you've extracted.

9. Flash and wait until it is done.

10. Long press power button and let your device is on.

Then got the dreaded enter your android password.

Had to do a complete reset.

What did I do wrong?
[ZTE Axon 7 Guides, News, & Discussion] stinka318:
Just reflash EDL......
[ZTE Axon 7 Guides, News, & Discussion] Oki:
I suspect that flashing these weird Turkish files with a green and uncentered ZTE logo, intead of the blue one, in a 2017U removes the capability to enter EDL by pressing VolUp+VolDn while rebooting the device. This behavior persists even after flashing the Oreo B12 or Universal BootStacks.

Are you experiencing this problem? Any clue on how to recover the original behavior of that key combination?
[ZTE Axon 7 Guides, News, & Discussion] KH_Lionheart:
Does the file included in the OP just flash fastboot functionality back to devices that have had it stripped by OTA?
[ZTE Axon 7 Guides, News, & Discussion] Kiddles:
Am I missing something here? I have my ADB drivers installed, and am able to get into the bootloader menu just fine, but anytime I use this command, it says the 'fastboot' command is unrecognized. Also, I can not longer use my PIN to get into my phone.
[ZTE Axon 7 Guides, News, & Discussion] Tekoj:
Does it work on A2017V3.0 B11 (Chinese beta Oreo) ?
[ZTE Axon 7 Guides, News, & Discussion] Kimmoth:
It didn't work for me either. I think it should say "fastboot oem unlock /go"

That worked.
[ZTE Axon 7 Guides, News, & Discussion] bigmarkusch:
I have closely followed the instructions and was able to unlock the bootloader. However since then, I haven't been able to see my device appear again in MiFlash, I can only go in recovery mode or back to the bootloader.

My phone shows up under Device Manager > Android Device but despite trying different drivers (Android ADB Interface, ZTE Handset ADB Interface) I've never been able to see it when typing adb devices in the command line. I've tried adb kill-server without success.

Also the device appears under Ports (COM & LPT) > Qualcomm HS USB when I manually turn ELM on (Vol up + down) but with a broken-driver-yellow-icon "This device cannot start. (Code 10)" and again not in MiFlash.

Any clue how I can move on from here? My goal is to flash this ROM . I'm running Windows 10 on a VirtualBox.

Thanks guys!
[ZTE Axon 7 Guides, News, & Discussion] bigmarkusch:
I realized my VirtualBox USB Ports was not properly setup (has to be USB 2). So now I can install any driver I want but still, I haven't been able to communicate through adb or while manually running EDL. Have tried different USB ports and different cables and I cannot boot the system, only bootloader / recovery mode.

Anyone?
[ZTE Axon 7 Guides, News, & Discussion] bigmarkusch:
I solved my issue: I was able to flash TWRP directly using the fastboot command line! Not sure how, why or if EDL mode was even necessary after all… got a fantastic new phone! Yaaay. Advice to beginners like me: keep trying with different versions and approaches, read carefully different threads including comments… good luck!

Thanks guys for all your efforts making these tools for everyone to use!
[ZTE Axon 7 Guides, News, & Discussion] redhou:
hi

by mistak i flash my A2017G with this file : ZTE_AXON_7_BOOTLOADER_UNLOCK_IMAGES_BY_TURKDEVS using miflash and now my phone don't start.

i was on oreo b02 , any solution to make it working again
[ZTE Axon 7 Guides, News, & Discussion] eeyan:
I got the password prompt after doing this, as in, when I power it on normally, it boots up and asks me for a password. I don't seem to have a useful bootloader anymore, when I do volume up + power, the red light turns on briefly then nothing happens. Other people with the password prompt issue have solved it by a factory reset or TWRP functions but I can't get to either. When I do volume up + down + power to get into EDL mode, when I plug it into my computer I get the DFU device in my ports list in device manager and MiFlash can't do anything with that. I got an EDL cable but it doesn't do anything but get me into DFU also, I've tried for hours with combinations of the cable button and device buttons offered online, no luck. When I fire up DFU_MultiDL Tool, I can't flash anything in it because it causes the device to go out of DFU and then shows up as a QDLoader 2008 device. While in that mode I can flash stuff, so I tried flashing the unbrick option in Axon7Toolkit, and now it gives me the password prompt in Russian. There is no fastboot capability. Any stuff I should try?
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
It shouldn't be that hard to get out of that mess - Just don't use axon7toolkit, you'll bury yourself even more. The unbrick option probably flashed an EDL package, I assume

First of all, you were getting a red light when trying to enter the recovery because the recovery was not compatible. There are some TWRP versions that might start when you get to this state - one of them is 3.0.2-2 Tenfar, which is signed. DO NOT BACKUP with this version as it will erase your EFS partition if you attempt to back it up. But you can format data all right with it.

MultiDL works just like you described it lol, it simply gets you out of DFU. you just have to close it and get to EDL Tool or miflash or whatever. To flash tenfa's TWRP you ca simply use EDL Tool's flash recovery option

Or you can just flash a full EDL package? I can't see why you wouldn't after trying axon7toolkit's unbrick option, whatever it does, it probably already replaced whatever you had before (vendor?)
[ZTE Axon 7 Guides, News, & Discussion] eeyan:
Thanks for your reply and the info. I got the Tenfar TWRP package but my phone wasn't having it when I tried flashing it. My bootloader didn't get unlocked, not sure why, I had the OEM Unlock option on when I ran this guide. Should the Tenfar TWRP flash even if the bootloader isn't unlocked because it's signed? I've been trying the full EDL packages. One of them gets me the ZTE boot screen with Chinese characters on it and the Russian password prompt and the others give me the regular ZTE boot screen with the Russian password prompt.
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
How do you know your bootloader is not unlocked? Do you have the warming screen?

Tenfar's TWRP is made for flashing before unlocking the bootloader, so that you can replace the aboot and fbop images and regain Fastboot, and then issue the unlock command from there

You're not bricked anymore though. you just need to format your data partition. Try flashing Tenfar twrp and entering it right away, by holding Volume UP before the ZTE boot logo appears. then format data from inside of it if you manage to get there. if it throws an error about data being encrypted, just reboot - reboot recovery and try formatting data again
[ZTE Axon 7 Guides, News, & Discussion] adeki:
is this method working 8.0.0 B022 stock ?
[ZTE Axon 7 Guides, News, & Discussion] kay07-:
does this work on oreo 8.0.0 2017g 0B02 stock?
[ZTE Axon 7 Guides, News, & Discussion] OleKohle:
How does step 11 work?

How do I do these steps (11,12) ? I got there but the instruction just says "Enter" but not where I should enter or how. I really need help!

Btw. the phone is in normal lockscreen now but I cannot unlock it via my pin.

11. Enter "adb reboot bootloader" after your device is on.

12. Enter "fastboot oem unlock-go" when you are on bootloader interface.
[ZTE Axon 7 Guides, News, & Discussion] WesTD:
sorry for late reply. you should cmd screen for this commands.
[ZTE Axon 7 Guides, News, & Discussion] OleKohle:
It's alright

No problem, I just wiped it and now use it in its stock form. I just wanted it to be a bit smoother like when it was new anyways.
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
well, tbh you should probably unlock it anyways, Pie is much better in terms of battery, and is much more updated. especially if you are on Nougat, that's two versions old
[ZTE Axon 7 Guides, News, & Discussion] Athiril:
Others have asked but havent gotten answer yet.

Does this work with stock Oreo roms?
[ZTE Axon 7 Guides, News, & Discussion] pkmsuhail:
hi please anyone can tell me did this method work with "zte axon 7 a2017g , stock rom version oreo b02"
[ZTE Axon 7 Guides, News, & Discussion] kaczychuj:
Hi, sorry for my english. I have a problem with Axon 7 A2017G. It works correctly. But i need to make root. Bootloader is locked, so i have:

- win10 x64;

- Disable Driver Signature Verification

- ROM is 7.1.1 v1.2 B10

- "USB Debugging" and "Unlock OEM" - on

Driver install from this post.

Any idea ?
[ZTE Axon 7 Guides, News, & Discussion] klałn:
Are you using linux and trying to enter edl on windows virtual machine?

The thing is, dfu/edl mode works as serial port, not as usb device.

Your host OS doesn't switch to serial mode on usb, but the guest OS did so. Probably, because of that, you got descriptor error on usb.

I would play with virtualbox and usb/serial port settings.
[ZTE Axon 7 Guides, News, & Discussion] kaczychuj:
no it's normal Windows 10 x64 with latest update. Interesting is on DFU mode PC recognize phone
[ZTE Axon 7 Guides, News, & Discussion] klałn:
I had descriptor errors few days ago on EDL mode. It is a cable in my case. Specifically, microusb fails when used with usb-c adapter.

You are on Win10 with usb 3.0, on the other hand. You will have to try more things like installing usb intel drivers, changing usb settings or playing with regedit..

Yet, try to clean up charging port and usb cable first.

Also, phone in EDL Mode on Oreo B03/B04 may hang on (or crash), reporting descriptor error - rare, but possible. Cooling down or disconnecting battery will help.
[ZTE Axon 7 Guides, News, & Discussion] kaczychuj:
I have already tried with the battery. Should every cable work? I checked the cable from Xiaomi Mi9t does not see the phone. Only the original works. Kurwa wykończe się zaraz z tym angielskim. On a different charging port, it doesn't work either
[ZTE Axon 7 Guides, News, & Discussion] klałn:
Any usb-c cable should work. Have you tried cleaning ports with toothbrush soaked in denaturated/isopropyle alcohol or benzyną ekstrakcyjną (white gas?)?

Try uninstalling driver from device manager when phone is in edl mode.

Maybe disabling usb 3.0 in uefi/bios will help..

Descriptor 43 error can make you mad..
[ZTE Axon 7 Guides, News, & Discussion] kaczychuj:
Interesting is that, only oryginal cable works. I check many port, many PC. cable even checked another usb board. I'll try to clean it but first i try now windows 7 on sd card.

Edit:

-nothing works - registry, oblivion usb, change cabel, change port, change pc, change usb board, change system, driver, setting in Bios

- everything clean

- pc recognize phone only with oryginal cable :(

Maybe the flex cable between mainboard and usb board is broken ? (main u84A)
[ZTE Axon 7 Guides, News, & Discussion] flich47:
I Tried on Oreo B03 and works!!!

Thanks
[Moto Z2 Force  Guides, News, & Discussion] enetec:
Reserved #1.
[Moto Z2 Force  Guides, News, & Discussion] enetec:
Reserved #2.
[Moto Z2 Force  Guides, News, & Discussion] TheKnux:
Awesome guide! One of the most intricate guides that goes over every last detail that I've read on XDA in a long time. Thank you. ?
[Moto Z2 Force  Guides, News, & Discussion] 3's&7's:
Great guide, thanks for the notes re: Xposed...I kept trying to install from TWRP (habit)
[Moto Z2 Force  Guides, News, & Discussion] enetec:
Our device still needs some cautions & tips...;)
[Moto Z2 Force  Guides, News, & Discussion] Deester4x4jr:
Issue with Modem/Radio

After following your guide to the letter, my phone would not connect to a mobile network and would say "Error while searching for networks" when I tried to force it to find one. I ended up following this guide to try and get back to a working setup:

https://xdaforums.com/z2-force/development/rom-stock-november-hybrid-rom-t-mobile-t3712795

Unfortunately, nothing is working. Any help would be greatly appreciated.

Thanks!

-Josh-
[Moto Z2 Force  Guides, News, & Discussion] Deester4x4jr:
I figured it out. Had to use the Flash ALL Package from that other post. The modem firmware is very specific.
[Moto Z2 Force  Guides, News, & Discussion] ilovemeow:
might be this is the reason i loose 4G+ (4G instead) signal after flashing lmfao
[Moto Z2 Force  Guides, News, & Discussion] turbojetjs:
just Wow!! What a great post!!
[Moto Z2 Force  Guides, News, & Discussion] hashnon:
Damn! Why did follow this guide!? I knew I didn't need to flash anything but boot/boot_a and stay on stock FW with only TWRP from Pantheon kernel!

Now I have a Moto Z2 Force (Dual SIM, UK, retail) without wifi, mac 02:00:00:00:00:00:00:00 and it cannot switch it on!

Any one have full stock image, at least of the boot partition from Dual SIM, UK?

PS: No need to link to Factory Image Moto Z2 Force (NASH) RETAIL. both of them aren't fixing anything for me.
[Moto Z2 Force  Guides, News, & Discussion] basdriver62:
Bitdefender blocked it for me for the longest time, then after reinstalling minimal ADB and Fastboot, Motorola Manager, and allowing access to Windows File Explore through Bitdefender, it worked for me; check your antivirus, hope that helps.
[Moto Z2 Force  Guides, News, & Discussion] hashnon:
Blocked what? And anyway, I don't have any antivirus. There is brain and Linux for that!
[Moto Z2 Force  Guides, News, & Discussion] basdriver62:
Oh my bad, lol
[Moto Z2 Force  Guides, News, & Discussion] hashnon:
Ok, fixed it my self, this: https://xdaforums.com/nexus-6/help/wifi-mac-address-200000000000-t3257465/post65960082#post65960082 gave me general idea what to do and what to check.
[Moto Z2 Force  Guides, News, & Discussion] basdriver62:
Good to hear that, I got so mad when I went in and tried rooting my Z2F without reading this guide first on the very first day that I got it. ??
[Moto Z2 Force  Guides, News, & Discussion] enetec:
This is intended/tested only on EU/intl. XT1789-06... on what version did you applied all this?
[Moto Z2 Force  Guides, News, & Discussion] enetec:
This is intended/tested only on EU/intl. XT1789-06... on what version did you applied all this?

How do you fix your wifi issue exactly?
[Moto Z2 Force  Guides, News, & Discussion] ilovemeow:
reteu, xt1789-06

---------- Post added at 10:09 PM ---------- Previous post was at 10:09 PM ----------

lol i found this post and fixed too
[Moto Z2 Force  Guides, News, & Discussion] aamszia:
any idea how to convert single sim edition to dual sim ?
[Moto Z2 Force  Guides, News, & Discussion] nishthecooldude:
Is it advisable to unlock bootloader first on international model v7.1.1 and then update to oreo?

Should i root first on 7.1.1 or after updating to 8.0.0?
[Moto Z2 Force  Guides, News, & Discussion] HACK3DANDR0ID:
WoW, a lot of info... Thanks for the post. My Moto Z2 Force just got dropped off within the last couple hours. So far i've unlocked the boot loader, i was going to do the Oreo sideload update but for some reason i cannot get my device into Stock Recovery Mode...so i guess i'm going to add TWRP and Magisk until a TWRP flashable version comes out. I'm coming from the Note8 and LG V30. Loved the Note8, just not the fact of being LOCKED down and unable to do anything to my device...the V30 really feels cheap and out of about 60 Android Devices, this was my 1st and last LG. Just doesnt feel like what it costs, at all...

Anyway, I didnt think any other devices had a/b partitions except Pixels. I had a Pixel XL, working with 2 partitions has a little getting use too, but unfortunately a/b partitions lack development, at least in the Google Pixel XL community, of all communities. Thats why i kinda got rid of my Pixel XL, lack of development....i hope the same thing doesnt happen with the Moto Z2 Force :( Cause thats what we all want, development!
[Moto Z2 Force  Guides, News, & Discussion] gburas:
Hi, Moto site states that my xt1789-06 reteu(official pie) from amazon.de is not intended to bootloader unlock, is there any other method?

Wysłane z mojego Moto Z (2) przy użyciu Tapatalka
[Moto Z2 Force  Guides, News, & Discussion] gburas:
Anyone? I tried multiple times (somebody wrote that finally work out) but unlucky. I have this extremely annoying WiFi problem and I wanted to try other ROMs but if I don't unlock bootloader it will be so pice of junk. Motorola lost all my respect, I had Moto phones since RAZR Maxx but I will drop them soon if I can't install custom ROM.

Wysłane z mojego Moto Z (2) przy użyciu Tapatalka
[Moto Z2 Force  Guides, News, & Discussion] Kiohard:
Is it possible downgrade pie to nougat?
[Nook HD, HD+ Q&A, Help & Troubleshooting] theleagueofstream:
I recently switched over from CM10.1 to LN14.1 and have been getting misreported battery (it worked fine previously) Specifically, it will drop 15-20% every 10 minutes or so, and stay at 1% for several hours (I've recorded up to ten hours).

What I've tried to fix the issue:

Draining to 0% and recharging to 100% (i.e. manual calibration listed on XDA) on LN14 builds

Battery Calibration Apps recommended on XDA

Flashing down to stock ROM, factory resetting, and re-flashing 14.1 (I read this could restore a battery file that has been affected by repeated flashing of ROMs.)

Flashing back down to CM10.1 and CM10.2 (also tried CM11 and CM12 builds) that I used previously

Wiping DALVIK/Cache between each install

Battery Monitoring Apps (Rooted)

Battery saving/hibernation apps

Adjusting nearly every power consumption option (screen brightness, WiFi, etc.)

The behavior has been the same switching between any ROM of CM, LN, Stock/Factory Reset from the point that I first upgraded from CM10 to LN14.

I don't think it's a lack a capacity and it has to do with misreporting.

I haven't tried recalibrating/draining on CM10 or stock, but I don't know if that would be pointless since I've attempted it three times on LN14 with no success. Also, I don't know if the process causes battery issues long-term. Right now, I'm looking to see if TWRP reports the same battery level as LN14. Last night, I was at 1% for 10 hours or so, including ~3 hours of video trying to discharge.

Anyone have any tips on where to look next? Is this just an issue with LN on HD+ in general? Thanks in advance for any help.
[Nook HD, HD+ Q&A, Help & Troubleshooting] nmyshkin:
Probably one of your sources of information is this post: https://xdaforums.com/nook-hd/help/nook-hd-battery-issue-custom-rom-fixes-t3389721

We suffered through this issue with an HD for quite awhile and tried all the stuff you mention. It may be that the return to stock/factory reset actually worked but it may also be that we discovered that somehow the SD card we were using for flashing (and which we had remade at some point) had not been properly configured as 0x0c and was instead 0x0b. This eventually led to a tablet that would only boot when plugged in and allowed to sit for a minute before being unplugged. We never got to the battery misbehaving issue at that point because of the panic that ensued over what the %#W% was going on!

Anyway.....once the card was made properly, we started from stock/factory reset (including actually re-registering the tablet with B&N, etc.) and then flashed the CM ROMs. Everything is now fine.

Whew.
[Nook HD, HD+ Q&A, Help & Troubleshooting] theleagueofstream:
I checked my SD card and the Partition ID is 0x0b. However, my tablet doesn't have the behavior you described regarding the need to be plugged in to boot.

Are you indicating that it would be worth flashing back down to 2.1.0 Stock ROM/Factory Reset with a 0x0c card, and Registering to attempt to resolve the issue? Would I be required to remain on stock for a period of time or can I re-flash to LN immediately? Thanks in advance for you help, the Partition ID type is news to me.