yashsingh1/xdaforums huggingface dataset:
[Magisk] theduke7:
Hello Everyone,

This is a collection of modules and a 1 flashable zip to enable aptX and aptx-HD on Oreo ROMs that doesn't have them...

the original files are taken from OnePlus OOS Oreo ROM, this should work (one of the options) on any OReo ROM, it may also work on N Roms but that's is not tested.

all modules flash the lib files to different places (or to all places), please the options, and select what is appropriate to you.

Bug reporting.

if you're going to report any issue please attach a log (the log should be taken before enabling Bluetooth and should record it being enabled and then being connected to an aptX enabled device)

Updated on January 6th 2018:

- 3 Magisk Modules added Description bellow for each.

- all 3 modules are based on the latest 1500 (15.0) Magisk template.

- APTX-enabler.zip is not a Magisk Module it's a recovery flashable zip, Description bellow.

should Works On All Oreo Roms.

Requirement:

-Root

-Root file manager

-Recovery (TWRP) for flashable Zip

A- Manual Installation:

1- download & extract the zip attached. ( APTX-enabler)

2- copy the files from System/vendor/lib64 folder to same place on your device, 0644 permission to both.

2- copy the files from System/lib and System/lib64/ folders to same place on your device, 0644 permission to both.

3- open build.prob in a text editor (or through the file manager) and add the following line at the end of it.

persist.bt.enableAptXHD=true
persist.service.btui.use_aptx=1
persistent.bt.a2dp_offload_cap=sbc-aptx-aptXHD

5- reboot

B- Flashable Zip Installation

1- reboot to TWRP

2- flash APTX-enabler.zip

3- reboot

C-Magisk Module

1- Download one of the 3 modules (discretion bellow)

2- install through Magisk manager

3- reboot

Modules Description:

A- aptX-HD_OreoEnablerOOS.zip , add the lib files only to System/vendor/lib64/ , some Roms like OOS Oreo Roms only require that for aptX to be enabled, it's not only for OOS other Roms use that too, if you don't know Use option C.

B- aptX-HD_OreoEnabler2.zip , add the lib files to system/lib and system/lib64 only... some roms like Nitrogen doesn't require to add any Libs on the vender folder, if not sure also use Option C.

C- aptX-HD_OreoEnabler.zip, this will add the lib files to ALL possible places, insuring that no matter what ROM you have aptX works...if you don't know which folder your ROM uses either ask the Rom Dev or use this option.

Old lib Files and modules can still be found on the following folder

https://drive.google.com/open?id=1aJQiFlzFgQmDJb08QZ_NMLUc0eKqBPry

Credits to

[MENTION=5671576]Riku Azhurlar[/MENTION] for initial flashable zip

[MENTION=7141309]simonsmh[/MENTION] for the Initial Magisk Module

[MENTION=4550123]bmg1001[/MENTION] & [MENTION=4460126]ossito2012[/MENTION] for initial aptx files

OnePlus for Current aptX lib files
[Magisk] Riku Azhurlar:
No problem mate. We're you able to fix my installer with the new lib files okay? Or do you need me to touch up on itt
[Magisk] theduke7:
to be honest mate i just updated the libs and permission, i personally use the module and they work, but the flashable file was reported by several people on my other thread on OP3 forums to be working... i wouldn't mind if you took a little look at the script :D :P
[Magisk] matrixios01:
I have the nexus 6p with nitrogen 8.1 wich one Can not do without to use;;;;

Στάλθηκε από το Nexus 6P μου χρησιμοποιώντας Tapatalk
[Magisk] JohnFawkes:
instead of doing resetprop just put the props in system.prop file
[Magisk] Didgeridoohan:
Apart from what [MENTION=6815443]JohnFawkes[/MENTION] mentions above, you also need to configure the config.sh file to actually run the post-fs-data.sh script (POSTFSDATA=true) or the system.prop file if you decide to use that (PROPFILE=true).

Also, since you're providing these files for manual install you should remove the placeholder file from /system. This file may cause bootloops since some devices can't take adding new files or folder directly to the root of /system.
[Magisk] theduke7:
I used to have the flags in as described but the new OOS update responds only to the post-fs-data.sh, I forgot to enable it and remove the place holder file... I will remedy that and update them
[Magisk] theduke7:
Modules updated according to above suggestions.

it depends on your rom, you can ask your rom dev which folder to place the lib files at at download the one corresponding to that... the aptX-HD_OreoEnabler.zip file should work for all roms cause it adds the libs to all possible places, but at least in my opinion this should be the last thing to try,

If Nitrogen in Nexus works the same way it does on OP3 the file aptX-HD_OreoEnabler2.zip should work for you...
[Magisk] Riku Azhurlar:
Sure I'll take a look here in a few when I get home. Also I didn't keep up on it. Did the magisk modules get updated to the newer template for magisk 15? Never know if the magisk dev will enforce it eventually if not I can do that too I've got nothing else to do lol
[Magisk] theduke7:
yes my friend it's updated to 15 template, i had it on the older template on the other thread on OP3 forums, but decided to download and update to the new one when creating this thread.
[Magisk] Riku Azhurlar:
Cool just checking my luck always seems to be they release new templates and then stop allowing them eventually.
[Magisk] joseph0042:
Does the manual install work without Magisk? I have an S8+ with locked bootloader (no custom recovery), but rooted, so was just wondering.
[Magisk] initguru:
Thanks for the module.

I installed Magisk module type c but the codecs were not enabled.

logcat said I have aptx and aptx hd in local capability but not in selectable capability.. only SBC and AAC there.

My phone is Essential ph-1 and I found another module in ph-1 forom but it is basically same.

I thought I need special codec config file but nothing contained a sort of config.

EDIT: nvm, my device just does not support aptX, so tried another one and it worked!
[Magisk] fl0wfr:
Could this work on any Oreo smartphone? For example on a Honor 9 running RR-OS Oreo? I read that the CPU was not compatible with Apt-X.
[Magisk] JBolho:
If the CPU isn't compatible... why are all the AptX libs in their place in stock rom? (At least in EMUI 8)
[Magisk] ecotycoon:
Thanks for the hard work on this port. Wasn't able to get the Magisk module working on Magisk 16. But was able to get the standalone systemless flash package working just fine on a LineageOS 15.1 port to my Nexus 5 which has been really awesome.
[Magisk] OGNinjaDon:
Just installed via Magisk and says enabled, but when I go to developer options under Bluetooth it still only says Aptx, i had this before. How do I know if aptx-hd is enabled?
[Magisk] jhobc:
Your device support the aptx-hd codec?
[Magisk] 00111101:
Dev can you include compatibility with AML?
[Magisk] rafaelrmoreira:
Does nexus 6p only support Aptx? Because I tried to enable the other Aptx HD codec and not active. Only Aptx.
[ZTE Axon 7 Guides, News, & Discussion] WesTD:
actually you don't need to open your phone. I was same situation and made a deepflash cable. it needs a little electronic ability and passion. you can enter edl mode with this method but it is too hard and you must be very patient.

I got edl mode one time but miflash didn't install correctly stock rom and couldn't again. [MENTION=6062859]asderdd[/MENTION] helped me and my device is okay now.
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
The deep flash cable works only sometimes. I didn't try but most people bought a bunch of normal ones and they didn't work
[ZTE Axon 7 Guides, News, & Discussion] andrizmitnick:
[MENTION=7799420]Choose an username...[/MENTION] bro should I take out the daughter board (which held usb c port) too? what should I do about the usb c module u've mentioned above?
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
It's not necessary, just taking out the board and the battery is usually enough. Be careful with the USB-C flex cable though, those are fragile
[ZTE Axon 7 Guides, News, & Discussion] DrakenFX:
just my 2 cents here, better off getting cable like this

https://www.amazon.com/gp/product/B06XXCLMGM

bought one just to have one in any sort of emergency and even tested and works like a charm and is not just for ZTE devices but any snapdragon device out there....
[ZTE Axon 7 Guides, News, & Discussion] andrizmitnick:
I ended up taking out the daughter board, I got it working on my 2nd try. my axon is working fine now, thank u so much for the guide, really helpful for urgent situation like I had atm ?

edit: I forgot to ask, do u know any solution on how I can recovery my bootloader mode back? I already try flashing official rom from stock recovery but no luck.

i'm too lazy to wait, so today i'm following this guide and it's a success. thanks btw for the link, gonna order it next week for future needs
[ZTE Axon 7 Guides, News, & Discussion] Miustone:
Will try this, my Axon 7 is still bricked af. Can't boot into Recovery, Bootloader, System or anything else without Reboots. Hope this Guide does the Trick...
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
And? Did you manage to pull it back together?
[ZTE Axon 7 Guides, News, & Discussion] bornlivedie:
I have my Axon 7 since March 2017. After a month of owning it, when Android 7.0 was released, I rushed to flash a chinese rom. The result, a nice brick.

I tried with 3 EDL cables and shorting that pin, many many times. No luck. So back then I decided to put the phone back in its box, forget about it and move on. So eventually I purchased a new phone, wich I hated so much because it was more expensive than the Axon 7 and lacked in every aspect. So I sold it as well, and bought another phone, which I loved, but again, lacked in comparison to the Axon 7, until I was mugged. So I remembered that I had an Axon 7 lying around in its box, and decided to search XDA for a solution. That's when I found this thread and I decided to try and revive the phone.

All can I say is thank you. You brought my beloved Axon 7 back to me.

Thank you so much.
[ZTE Axon 7 Guides, News, & Discussion] Harmtan2:
Thanks for the Guide! Annoyed at myself for my bonehead move that got me here in the first place, no biggie though as I used to repair phones for a living. If was any good with solder, I'd contemplate sticking a dab on that pin and never worry about not getting into EDL Mode again. I really like this phone, but the crap they've pulled in making it a nightmare to tinker with has me not desiring to get another one ever. OnePlus will probably get my next dollar set cuz of how open they are currently.
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
i don't think that would be a good idea. your phone would probably ONLY enter EDL mode. But I thought seriously about soldering a pushbutton on it. thing is that if you somehow rip the pad off, your mobo is dead.
[ZTE Axon 7 Guides, News, & Discussion] Reyad_W_K:
Thank you for this guide my phone is working on chinese rom now but the big problem is

i cant flash any thing now .

vol up + pwr then the fastboot keep restart

vol up + vol down + pwr send me to dfu mode

vol down + pwr send me to ftm mode and when i send (( adb reboot edl )) i get qualcomm usb but mi flash keep say (( can't receive hello packet )) i tried many many times with 3 versions of mi flash but nothing works

please help me i cant live with chinese rom .
[ZTE Axon 7 Guides, News, & Discussion] Oki:
Try Flashing with the Axon 7 EDL Tool. The problem can also be the EDL package you are trying to flash. Try now a different one. If you can get to EDL mode, then it should work.
[ZTE Axon 7 Guides, News, & Discussion] Hylex:
Woke up today to see my phone not turning on. Having troubles booting up and when I choose to go to recovery or fastboot through the unlocked bootloader warning menu it just bootloops. I connect my phone to my PC and it is already showing the "Qualcomm HS-USB QDLoader 9008" in device manager. Do I still need to open my phone and do the paper clip test in Step 4? Or can I continue on with the rest of the guide?
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
You should be able to just connect and do the final part. As long as your emmc is all right, of course
[ZTE Axon 7 Guides, News, & Discussion] Hylex:
Thanks for the quick reply. Heh, how often is flash storage failing a problem with other users? =X
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Maybe I've seen it once, but i'm on the q&a section all the time, so it's extremely rare. If it tries to boot then maybe it's just something much simpler
[ZTE Axon 7 Guides, News, & Discussion] TysonBeall:
From FTM mode ( hold volume + and plug in USB cable) adb should be enabled. If the phone has a Qualcomm chip and Qualcomm drivers have been installed on your computer. Use "adb reboot edl" to reboot the phone into edl / Qualcomm 9008 mode. No need for cables or tearing the phone apart. This does not work on every phone.
[ZTE Axon 7 Guides, News, & Discussion] Hylex:
Successfully flashed B35 EDL. Phone is unresponsive to any power or volume key presses. MicroSD card is removed. Still no cigar. Can't get the phone to be recognized as EDL mode anymore either. Phone detected with different USB port for EDL. Flashed again. Still nothing. Any suggestions? I still have the option of taking the phone apart, but that is a last resort if that makes the ability to RMA void.

I can feel the phone warming up when I plug it into a charger. That's the only sign of life I see in the phone.
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
You'll have to claim warranty... that sounds like dead storage. try another package maybe, marshmallow even. but i don't think it'll help too much
[ZTE Axon 7 Guides, News, & Discussion] bornlivedie:
You have to press power for like 10 seconds after you flash via EDL for the phone to turn on.

Maybe a button is stuck? Something similar happened to me with a galaxy s3.
[ZTE Axon 7 Guides, News, & Discussion] djprez:
I'm at this stage now trying to get my DFU'd Axom back. I have successfully got it to be recognized as a Qualcomm 9008 in device manager and miflash sees it. After several attempts to flash miflash gets to the 3s mark under the "Time" column and then a red message appears saying "Catastrophic failure.........."

I can't seem to get past this part.
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Damn, I never heard of a catastrophic failure ?

Do this, as soon as you get into EDL (You know, Qualcomm 9008) use EDL tool instead of MiFlash. Maybe it'll do its job
[ZTE Axon 7 Guides, News, & Discussion] djprez:
Well, I tried it again with a different MiFlash and EDL package and it worked. Now, my issue is the screen does not respond to touch. I'm going to open it up again and mak certain everything is in it's place which I thought I did prior to putting it back.

UPDATE:

Yeah, I've taken it apart again all the way to removing the motherboard and reassembling and the touch screen is not responding at all. DAMN. Could it be the software? Now that I am able to boot to the welcome [inital] screen and I have placed it in EDL mode and do have the other options after pressing the Vol up + Power key, is there a way I can flash something else?

UPDATE #2:

Took it apart again and I can not see any damage to anything inside so I am at a loss. Can't believe I got this far to have this happen.

UPDATE #3 (the saga continues):

I was able to flash TWRP and get into recovery and guess what...... the screen works! So, I'm thinking it may have something to do with the EDL rom I flashed.

Well, I've been trying to flash some roms and it gets stuck at the warning screen (software can't be checked for corruption..........). Tried the DrakenFX bootstack 35 and stocksystem 35 tried the boostack 19, sysyetm 19 and even BadBoys rom (I used to use a long time ago) and still stuck at that screen. Hope someone can shed some light on this, I'm so close..lol

WELP, I just may give up. got a bootstack/rom to work and I'm back at the Welcome screen but the screen is not responding to touch. WTH could be going on?
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Yeah, this happened to someone else. Just try custom ROMs and then go back to stock if you feel like it. Install LineageOS 15 or 14.1 just like the guides say, and see what happens
[ZTE Axon 7 Guides, News, & Discussion] Hylex:
May I ask which Miflash and EDL package you used to get a success?
[ZTE Axon 7 Guides, News, & Discussion] kitcostantino:
Me, possibly? lol I have a gold a2017u board stuck on MM. it is stuck simply because when i update to Nougat via OTA, EDL, or sd card update, touch functionality is gone. no other board i have had has had this issue. it is my oldest board.

Yes, it is the software. try flashing MM EDL and see if it brings touch back.

your guess is as good as mine. it makes no sense. the hardware is fine on mine, just cant upgrade beyond MM B29 (a2017u) and have touch functionality. That being said, there has to be a logical reason the touchscreen driver is borking on Nougat.
[ZTE Axon 7 Guides, News, & Discussion] le011:
greattt...

ty for the exellent guide...wow..its saved the phone...ty very much.....:cowboy::cowboy::svetius:
[ZTE Axon 7 Guides, News, & Discussion] Matthieu42:
Just saved my brother's Axon 7, thanks a lot !

I still can't believe that a simple brick can involve hardware work ...

We just need ZTE DFU Software to make this a lot easier
[ZTE Axon 7 Guides, News, & Discussion] janthe6th:
so after I flashed, I will need to put the phone back together and press volup+power to try to enter recovery right? at the moment I have successfully flashed a couple times but I'm still not able to turn on phone or enter recovery... I tried holding volup+power, volup+voldown+power, voldown+power but the screen won't turn on, only red light and sometimes green light flashing
[ZTE Axon 7 Guides, News, & Discussion] Syberclone:
Press and hold the power button till the phone boots (to make sure its working)
[ZTE Axon 7 Guides, News, & Discussion] janthe6th:
hi have tried multiple times with different edl packages and still can't get the phone to turn on. The flashing takes around 200 seconds and they all says successful. But when I try to turn the phone on, the LED flash red twice then green once in a split second then go off. Not sure that to do from here
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
i thanked you accidentally lmao

Did you brick the phone, or did it die by itself? If it was you, how did you brick it? What EDL files did you try? What model is your phone? Check on the back. It can be A2017, A2017U or A2017G. You have to install a package that works for your own device, otherwise it won't boot if it is locked (another question: is it locked?)

DO NOT flash a package that is not meant for your model as you will lose your IMEIs and you'll be in even deeper
[ZTE Axon 7 Guides, News, & Discussion] MicahDeWitt:
I've been trying to flash my phone for the past 4 hours, I am still googling but I cant find out why my phone is listed as Handset Diagnostic interface(DFU) (COM3) and I tried uninstalling the drivers and reinstalling qualcom but no luck, I can only boot up my phone in edl mode and if I try to do a regular boot up it just shuts off, I'm guessing I soft bricked it but I don't really know. Any help would be greatly appreciated and sorry for taking up your time.
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
lol, no problem. This guide is still useful for some very specific use cases but there are ways to fix a DFU brick (i.e. what you have) without even taking the phone apart.

Btw swapping the drivers is not gonna do anything... Your Fiat with a paint job is never gonna be a Ferrari. Just uninstall whatever driver you installed and check "delete driver software" so that it goes back to what it was.

Download MultiDL from this forum and also the latest MiFlash, those two are probably the best combination right now. Or also you could download EDL Tool and attempt to flash an EDL package with it instead of MiFlash.

There are a couple guides on how to unbrick with that stuff, all I can tell you is you are NOT on EDL, but rather on DFU. Getting out of DFU requires a) taking the phone apart and shorting a pin as described in this guide, or b) using MultiDL (which wasn't present a year ago, that's why this even exists) which simply gets you to EDL as soon as you connect it to the phone.

Once you are in EDL mode (Qualcomm HS-USB QDLoader 9008) just use MiFlash to flash a full EDL file. Or EDL Tool, too. I usually have more success with MiFlash but try both
[ZTE Axon 7 Guides, News, & Discussion] MicahDeWitt:
Thanks for the help got it working!
[ZTE Axon 7 Guides, News, & Discussion] h.whitty.99:
Thank you so much!!!
[ZTE Axon 7 Guides, News, & Discussion] dodo34:
i connect the phone to the PC by short circuit the point and i get "Qualcomm HS-USB QDLoader 9008" in the device manager.

i short circuit again and press refresh on miflash but miflash cannot find the phone. Why ?

Can someone help me pelase.

Kind regards
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Right click on the Qualcomm QDLoader stuff and uninstall device, tick uninstall driver software too. After that try again.

Did you try using MultiDL before? If you were on DFU, it isn't needed to take the phone apart anymore in most cases because MultiDL takes you out of it.

Also try EDL Tool and the latest miflash version (or older versions) and it may work
[ZTE Axon 7 Guides, News, & Discussion] dodo34:
Removed the driver and installed again and it worked. Strange.

Thank you so much !
[ZTE Axon 7 Guides, News, & Discussion] Prez1:
Has anyone figured out how to upgrade from Marshmallow B29 after getting the Axon back using this technique? For those who have issue below.

I still am unable to upgrade to anything above this release AND have the touch screen responsive. It upgrades fine but there is no response on the screen at all at the welcome screen (touch works in recovery menu).

Thanks!!!
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
I think [MENTION=3836686]kitcostantino[/MENTION] had the same problem... There doesn't seem to be any known fix for this. As for trying random stuff, maybe try backing up your persist partition and flashing someone else's backup? Honestly nothing tells me that it can work, but it won't do any harm as you would have to stay in MM anyways if this doesn't work
[ZTE Axon 7 Guides, News, & Discussion] Prez1:
Thank you for the reply.

I guess I'll stay as-is because it's such a pain to get back to MM B29 after I try different loads.
[ZTE Axon 7 Guides, News, & Discussion] kitcostantino:
well, i do have a theory, but it doesnt contain a solution. my board that was affected in this way i just kept on MM. Anything higher, and it would lose touch. i did figure out that where i effed up was manually flashing partitions. and config files. to fix that board, id have to be able to have the factory image and flash it using ztes method if initial programming. EDL cannot touch the partitions i borked. i never found a solution bc i never found the proper factory files. edl files exist all over the place, but what i flashed manually was marshmallow. and the only way i know to undo it is to reflash every partition. edl doesnt do that. i had read a bunch about the initial programming files but never could obtain any. zte could fix the board, but where i live, there are no shops with that sort of flashing capabilities. the best hint i can give is you need a config file and the proper software to repartition the entire memory. but i have no clue there. i wish you better luck thani had. :)