Hi everyone,
I bought axon 7 (A2017) Chinese version from aliexpress. It's on B07 version, when trying to check OTA updates - it says no updates. If I understood correctly, that's because seller flashed gapps. No problems, I thought, I can do this myself... After 2 days of reading, downloading malware and even trying to register on chinese zte forums I give up.
-Tried simply putting update files on sd card and updating - no luck. Most probably because I can't find b08/b09 updates for straight A2017 (without U or G), have the last two only.
-Installed drivers, tried unlocking bootloader -failed. Adb works, detects device, however after rebooting to edl - adb does not detect any devices (enabled usb debugging and oem unlocking.
-tried flashing with MiFlash - errors "[2,07 COM6]:cannot receive hello packet,MiFlash is trying to reset status!"
-tried rebooting to edl manually (up/down+power) - boots, but adb does not detect devices (MiFlash sees it as com6 though)
-tried using axon7tool and minimal_adb_fastboot_v1.4 - same, detects while on, reboots to edl and nothing
-tried sideloading twrp through the adb sideload - says signatures are bad...
Oh, as a bonus, recovery is in Chinese, so I have to guess what's what
What could be the issue? Drivers, device itself? Owner? I don't want to be on the damn 6.0.1 - my nexus 5 was on that. plus zte skin is awful, I would want to flash cyanogenmod or at least a newer version that does not have the damn bell icon, or permanently stuck sms that I can't delete or mark as read
Is there a way to flash US or EU firmware? Any ideas would be welcome. And sorry for writing here - as a new user I'm unable to reply on the dev posts
Hi I have the same problem can anyone help on this issue to resolve
My unit is from aliexpress also but it was B11 when i received it. What i did was enabled usb debugging and oem unlock from dev options. Then boot in stock recovery and format the phone. I think it was the option above the choices where there is 'sd' written. Then installed the update via sd for b13.
otaconremo said:
My unit is from aliexpress also but it was B11 when i received it. What i did was enabled usb debugging and oem unlock from dev options. Then boot in stock recovery and format the phone. I think it was the option above the choices where there is 'sd' written. Then installed the update via sd for b13.
Click to expand...
Click to collapse
I finally managed to do this via this method
https://forum.xda-developers.com/axon-7/how-to/guide-b13-chinese-a2017-root-unlock-t3549873
and now I run lineageOS
you will need a laptop that you have admin access to, which allows you to disable your antivirus though.. which was my main problem
Moderators, if any, you can lock the thread
Hi man I hope you're OK. Today I was on A2017V2.1.1B07(MM) and I just downloaded B11(third one) from this link (http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78]) and put it on SD card and updated and installed it from settings(although I downloaded and put B11 on sd card, it showed B13 ROM update in settings). Then when It was finished , I got B15 Nougat OTA in settings and downloaded and installed it then again I've got B16 OTA in settings and installed it and now everything is okay. But I wanna ask you if I did it all correctly???(because I downloaded B11 Rom(not b13 rom from that link above) but I got B13 when I put that B11 on sd card and went to the setting)and Did you do the same???
Hi,
To be honest, I don't remember the actual steps. I followed this threadhttps://forum.xda-developers.com/axon-7/how-to/guide-b13-chinese-a2017-root-unlock-t3549873 and finally did it =)But I don't think I was able to get and instal OTA updates =) I'm on US B25 version now, and every time I update I basically use DrakenFX's builds. How do you like your axon mate?
build 16 is latest so you are up to date
I had custom roms installed on my device but decided to go back to stock rom. I was able to restore the stock rom, updated and installed twrp and root on my device. I noticed that after I did this, my headphone jack stopped working and my PC doesn't detect my phone for USB file transfer or MTP configuration anymore (on stock, rooted). I wanted to know if I have the same problem on custom rom so I flashed a custom rom and both issues are resolved. Although I liked the Custom roms I tried (Havoc OS and Arrow OS Pie), I decided to go back to stock again this morning because one particular game that I'm playing (Mobile Legends) isn't working properly on custom roms (screen would sometimes flicker or go into black screen, I didn't experience this on stock). This time I decided to forget about root and relock my bootloader. After updating, I ran into the same problem with my headphone jack and usb file transfer. Does anyone have the same problem? If so, how did you get the headphone jack and usb file transfer to pc working again? Please help. Thanks.
I am facing the same problem ! anyhow installed lesser and switching between speakers and headphones ! Usb still isn't working !
romi7 said:
I am facing the same problem ! anyhow installed lesser and switching between speakers and headphones ! Usb still isn't working !
Click to expand...
Click to collapse
The only way I could use usb file transfer is when I boot into a custom recovery. I went back custom rom for now, until I find a permanent solution for both. I tried searching for answers at the Zentak forums but couldn't any help there.
Have you tried flashing the raw firmware first than update? It's here somewhere on unofficial unlock/re-lock post, I went back to stock ROM after re-lock without any issues. I did have an issue flashing using AFT after re-lock, but flashing corresponding recovery.img than flash firmware using recovery solved that.
sanctitude888 said:
Have you tried flashing the raw firmware first than update? It's here somewhere on unofficial unlock/re-lock post, I went back to stock ROM after re-lock without any issues. I did have an issue flashing using AFT after re-lock, but flashing corresponding recovery.img than flash firmware using recovery solved that.
Click to expand...
Click to collapse
'
Hi! Thank you! My problem is now fixed, both headphone jack and USB file transfer, although I'm not really sure if it will work for others. What I did was I flashed (while device is unlocked) the Nougat raw firmware (WW_ZE552KL_14.2020.1712.85_M3.10.47.15), tested it and both were functioning. I decided to update to Oreo using the system update feature and it is still now working after I installed all the Oreo updates. I'm not planning to re-lock anytime soon as I installed root and found it beneficial.
I did follow the unofficial unlock/ re-lock prior to doing the previous steps, although I first flashed the factory raw rom (CSC_ZE552KL_13_13_1_36_M2_6_7_P7_userdebug.zip), unlocked and the flashed the Oreo raw firmware (WW_ZE552KL_15.0410.1806.68_M3.10.47.19) . Maybe skipping to flash the Nougat Raw firmware caused the problem? I'm not really sure, sorry I'm relatively new to all these.
Glad to know it's all ok on your part
borutosdad said:
'
Hi! Thank you! My problem is now fixed, both headphone jack and USB file transfer, although I'm not really sure if it will work for others. What I did was I flashed (while device is unlocked) the Nougat raw firmware (WW_ZE552KL_14.2020.1712.85_M3.10.47.15), tested it and both were functioning. I decided to update to Oreo using the system update feature and it is still now working after I installed all the Oreo updates. I'm not planning to re-lock anytime soon as I installed root and found it beneficial.
I did follow the unofficial unlock/ re-lock prior to doing the previous steps, although I first flashed the factory raw rom (CSC_ZE552KL_13_13_1_36_M2_6_7_P7_userdebug.zip), unlocked and the flashed the Oreo raw firmware (WW_ZE552KL_15.0410.1806.68_M3.10.47.19) . Maybe skipping to flash the Nougat Raw firmware caused the problem? I'm not really sure, sorry I'm relatively new to all these.
Click to expand...
Click to collapse
Yup you should flash Oreo RAW as custom ROMs (Android 8 and above) needs latest modem.
Okay, so I've been trying to get some answers regarding custom ROMs for the past few days but I haven't even got one...and it seems I'm not the only one looking for them. So...lay it in this thread maybe we can start something up.
I am on stock OREO B04, phone's software has never been tampered with anything, TWRP, BL unlock and so on.
This is the premise of the thread, not only for me but for other users who find themselves in the same situation.
Oreo seems to be a bit of a hassle right now for migrating to custom ROMs, and this is not helped by the fact guides in the A7 section are all over the place as well, some may be outdated and there's no clear "Don't use this on x.x version" warning.
I am not even going to attempt to unlock the BL until I clear answer on wether it's possible or not. So let's start with this:
-Is it possible to unlock the BL on OREO?
-If not, what stock official ROM should we install in order to successfuly attempt to unlock the bl?
-Which guide or method is the best for doing so? I've found 2, one from 2016 on MM ROMs and one provided by TurkDevs that seems to work on some Nougat ROMs.
Then comes the recovery section:
-What TWRP should we install on a freshly unlocked device, the official releases, or the Nfound custom ones?
-Also, what are the prerequisites for installing TWRP...I hear that fastboot commands are gone since Nougat and that some flashing methods don't work, then I hear somehow you can do it by bringing back fastboot. How? There's only replies saying "type that command in fastboot" but nobody says if they had it or reinstalled it somehow.
Then comes the ROMs section:
-All custom ROMs seem to require a vendor partition as most if not all of them are Treble based. How do we get that to work?
- I am aware of the fact that the ROM threads have a prerequisites section, but none of them redirect you to a guide on how to get those prerequisites working. I understand that it's not the dev's responsability, I am not bashing anyone here, but a little bit of info cleaning and structuring should be in order in this section.
What I want for me and others in my situation is a clear answer on how to proceed, not a "flash this flash that". There's no secret that the A7 still has life in it especially with the new PIE ROMs.
I've recently seen a reply in one of the threads, encouraging the dev of one of this ROMs to not be disappointed by the seemingly low interest in PIE ROMs. I don't think there's a low interest in them, I think there are users that don't want to risk a bricked phone because of outdated guides and unlcear steps.
There's a lot of confusion going around here so I hope this thread will become a source of updated info on what's possible and what not. Thanks in advance!
Hi, I'm not the best person to help you with this since i've unlocked my Axon 7 a long time ago and I can't remember everything but I will try to help you based on my experience and on what I can remember.
Let's go
Starting with the bootloader, I unlocked mine on stock Nougat B09 using EDL Tool (Oreo wasn't even out when I unlocked my bootloader so I don't know if you can do it while running Oreo but just to be safe you should downgrade to Nougat)
It should be quite easy to unlock the bootloader, here's a simple step by step (please anyone correct me if I'm wrong)
- Download the EDL tool from the link above
- Downgrade your phone to Nougat (Using the updater on the phone itself or an EDL Package with EDL Tool or MiFlash - you can find the stock ROMs on @raystef66 's Download Center
- Once running Stock Nougat, turn on USB Debugging and Allow OEM Unlocking on Developer Settings
- Plug the phone to your computer and open EDL Tool (that should reboot the phone into EDL mode automatically)
- Navigate through the EDL Tool using the number keys on the keyboard, and it should be easy to find the Unlock Bootloader option. Unlock it and you should be done.
Once again that's the way I did it, I don't know if this is the easiest one available. You have more methods available like this one
Now onto the recovery situation, I think each developer recommends a specific TWRP version for their ROM's, like for example
@raystef66 likes NFound's TWRP 3.2.1-8 as you can see on his ROM's posts (check the first line in the installation guide)
@OrdenKrieger likes the official TWRP as you can see on Lineage OS 16.0 post
Generally, official TWRP should work just fine with any ROM.
On a recently unlocked Nougat Stock ROM, I recommend maybe an older version of TWRP, like 3.2.1 for example and you can flash it also using EDL Tool.
But when moving to Pie I recommend you use the latest TWRP version or the version that the ROM developer recommends. You probably know this but you can update your TWRP version by flashing it over the current version you have.
Now about the ROM's, the new ones have a Vendor partition so you have to create it when you're coming from Stock (because our Axon 7 doesn't support Project Treble) and to do that you can use @Oki 's PARTY Tool and after that you can flash the ROM normally, using the proper Bootstack and Modem files.
You could also try GSI's but I can't help you with that because I never tried them.
And this should be all.
I tried to keep it simple for now but i can help you further
I'm not the best person to guide you but at least I tried Feel free to ask me something and good luck!
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
TorqueSsS said:
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
Click to expand...
Click to collapse
I'm glad I could help
Since you're not the only person with questions on how to migrate from stock to custom, I'm thinking about writing a full post so more people can see it.
Btw what method did you use to downgrade to nougat?
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
TorqueSsS said:
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
Click to expand...
Click to collapse
Thanks! That will help me a lot to write a full guide. You'll be credited, don't worry
And yeah, when you migrate to custom roms you'll have to sacrifice camera quality and functionality and also a bit of speakers sound quality (all dolby atmos ports I tried are quite buggy and don't work well ; i only use atmos with the speakers). Headphones sound quality is great though.
If you don't use camera that much (not my case) and you're okay with the speakers sound quality then custom roms are probably the best option out there.
@joaocandeias
I was fully aware of the camera issues I might encounter, this has been the case with my old Mediatek devices when going to custom as well, same camera issues, but at least...it works here. Yeah, I lost some functionality, but to me it's a good trade-off. It can still take snaps and film properly so it's enough for me.
I am kind of going to miss Dolby on speakers (never liked it on headphones though), as it did a really good job for podcast style videos on YT, but it still sounds way better than a lot of phones without it so it's fine. I just need to crank the volume up a little more than usual.
I've heard that treble Pie Roms require a oreo bootloader, is this true? I am still confused how to install on my A2017G. In which order would I install bootloader and vendor partition?
Edit 3: TL;DR: This is appears to be an S8 exclusive error, it's shown in the recovery:
"Product device tree not found, couldn't verify firmware" or something like that. For solutions, please look that up.
So, I bought a bootlooping S8 in the hopes of fixing it.
Since OEM and FRP lock are on, I went with installing Samsung firmware on it, as installing a custom recovery at this point is not possible.
The default recovery wouldn't work, so I wasn't able to know which firmware exactly to flash, because I couldn't find out which model exactly I have bought.
I do not know the carrier of the device either, but it should be from some german provider.
All of the firmwares I tried just bootlooped, but the recovery works again, except for ADB, which is quite unfortunate, and I have no idea why it fails, the device shows up when I'm in the recovery menu, but as soon as I activate ADB, it's gone from the list of connected devices.
Combination firmwares sometimes show some turning gears animations, but then crash with some, thought often memory related, pretty random crash issue.
Another problem I am now facing is that in the process of trying to find a working firmware I now upgraded the devices "binary level"? (forgot what exactly it was called) to 6, so I can't flash any older firmware or combination firmware than 6, since downgrading isn't allowed.
I received the device with either binary level 1 oder 2.
My theory is that I don't have the right firmware, since I keep seeing dm-verity and license errors...
I am happy to provide logs if necessary.
The goal is to have an unlocked bootloader/ custom recovery.
I literally am going INSANE over this FRP blocking me from flashing TWRP and being done with this in under 10 minutes, please help :c
PS: Some random info attached
Edit 1: With the IMEI code i found while opening the phone I now know my model number: SM-G950FZKADBT.
Any tips for finding the PDA code of the originally installed system? Or finding a matching firmware?
Is this even neccesary? Why do official firmwares not work for me? :c
Edit 2: Somewhat solution: I think the only way to recover this device would be to find it's firmware, which is just NOT to be found...
So, until a miracle happens I'm gonna keep reading "Firmware is not valid" errors in the log
Did you look in samfrew.com ? ? ? I just grabbed a fw from there.
The dnld was loooong so I purchased a privilege for faster speed . . .