yashsingh1/xdaforums huggingface dataset:
[ZTE Axon Pro] demenicis:
EDIT.

My phone was bent a bit. The frame with the screen is bent, but the back is not, so there it's a gap that allows the SD card to randomly disconnect. Doing this about 10 times a day cannot be healthy to the card. Now I factory reset the phone, removed SD card and will only use the internal memory. The phone is now retired and serving as a fix landline. I got a grade A axon 7 mini for £99......which by the way is utterly amazing. All the good stuff of the axon mini, but with NFC, better camera, battery well healthier, sound still amazing, android nugget and the OS is so fluid. I even tried lineage on it.......although ZTE, as usual, does what they can to complicate their system like no other company. I lost the IMEI during the upgrade process and it took me a month to get the phone going again.....and I actually killed it (I have a 1 day old irreversibly dead brick)....... and I bought a second one.......which I bricked again but I managed to fix it.......anyway it was worth it. The phone has what would make the axon mini perfect.

So the message is that I'll now very rarely check this forum, but will sometimes just because it is really nice to be able to help people if I can.

Cheers

-------------

guys, after more than 2 years of good use, my phone started destroying SD cards.

I thought it was a China one so I got a proper £25 Kingston one, class 10 and my pictures are turning all grey.

today I took about 10 pictures, whatsapped them fine. went back to the gallery and every single one was grey, corrupted.

anyone facing the same?
[ZTE Axon Pro] learn31:
Roor 963vl
[ZTE Axon Pro] ronthekiller:
Will axon 7 mini ROMs work on this device?

Hey guys I'm a noob here and was wondering if axon 7 mini ROMs will work on Axon mini... There are literally no ROMs for this phone and it's making me go nuts lol. :D
[ZTE Axon Pro] devasishsaikia:
Any Custom ROM for ZTE Axon Mini (Snapdragon 616) not ZTE Axon 7 mini

Hello, I am bit confused is this post is about ZTE Axon Mini (Snapdragon 616) with forced touch released in 2015 or is about ZTE Axon 7 Mini (Snapdragon 617) released in 2016.

Post says ZTE Axon Mini but also talks about Android 6, but ZTE Axon Mini was never updated to Android 6, on the other hand ZTE Axon 7 Mini was updated to Android 6. So I am confused, post is for which device.

Also is there any Custom Rom for ZTE Axon Mini - SD616 version ?
[ZTE Axon Pro] demenicis:
Lol. Totally lost......

Ok axon mini is a phone, with 2 variants, Chinese 22015, and international 2016.

They are identical, but the 2015 only got android 6 update and doesnt have force touch.

The 2016 has force touch, but stuck in lollipop forever, AND THAT IS THE WHOLE POINT OF THIS THREAD, i.e. adapting the Chinese Rom for the 2016 phone.

Don't even talk axon 7 mini, it is another completely different phone (similar looking though) and the ROM will not work on this one. I have the 7 mini now btw. But the axon mini is now with grandpa, still strong after nearly 4 year!

Cheers
[ZTE Axon Pro] Luba0609:
Does the axon mini (not axon 7 mini) have "custom binary blocked by FRP" if rooted or twrp flashed, when used along with Google account... ?

Also is it possible to root it with Magisk... ?
[ZTE Axon Pro] Luba0609:
Any one? Show me some light... Please... :(
[ZTE Axon Pro] smartlinux:
Axon Mini EDL Tool

Axon Mini EDL Tool​

The program for flashing the phone in EDL mode​

Qualcomm HS-USB QDLoader 9008 (COM ...)​

!!! Whatever you do, you do at your own risk !!!

!!! If you are not sure of yourself do not use this program !!!​

I just redid this utility for ZTE Axon Mini device. Author utility djkuz for which he thanks a lot.

How to start:

Unpack the downloaded archive with the program;

It is advisable to unpack the program on drive C: \ or D: \;

Run the Axon_Mini_EDL_Tool_0001.exe file as Administrator;

Features of the program:

Language interface selection (English, Russian);

Automatically puts the phone in EDL mode;

Finds the connected phone and forcibly sets the com-port speed to 115200;

Able to flash the phone, makes backups, restores from backups;

Flash partitions Boot, Bootloader, Modem, Recovery (original and TWRP) files from the program;

Analyzes folders for missing files;

Download: from Yandex.Disk
[ZTE Axon Pro] Nick0-72:
Great thanks, I will try this out!
[ZTE Axon Pro] lelmiral:
I have the B2016, I was messing around and got the custom ROM working but after I wiped the system I am unable to do anything TWRP recovery is still there but I can't flash the 5.0.1 zip and any thing it just shuts off automatically. Help!
[ZTE Axon Pro] gouthamram:
thank you for all zte axon mini developers...iam already take a edl backup for my zte b2016...

now iam using B14 M clean rom its work super smooth & fluid.it gives a new life of my poor laggy device...
[ZTE Axon Pro] gouthamram:
first your flash Aboot5 file then you flash B14 clean rom...
[ZTE Axon Pro] lelmiral:
I know it's been a long time, but does the same thing automatically turns off automatically while flashing aboot5 you mean aboot 5.1.1 this or any other aboot?
[ZTE Axon Pro] jmbenevise:
Has anyone been able to get a look at this firmware ZTE B2016 FTV1.0.0.B06 ?

Is it legit, international, working?
[ZTE Axon Pro] Crisvendetta:
it omly works with the thumb finger
[ZTE Axon Pro] scoobydoos:
Yes I install the apk. What's the log-mode ? adb status : root ? How you set the app on default ?

Thanks a lot

bye
[ZTE Axon Pro] Bruce_999:
Thanks! I confirm It works with the thumb finger or covering well with any fingertip
[ZTE Axon Pro] Crisvendetta:
I deactivated the live wallpaper with the fish but cannot find where to reactivate it, anyone knows?
[ZTE Axon Pro] Heze85:
the enable-log-mode will be ask the first time you open up the tool, and you have to set it after this to default and not the root status
[ZTE Axon Pro] scoobydoos:
Ok I do that and I click on "OK" or I leave the app open ?

Thanks a lot

bye
[ZTE Axon Pro] aga75:
Обновился с В03 до В04. Прошивка на сайте ZTE.

Заработал голосовой помощник на английском. Root слетел, но ставится назад по способу выше. Извиняюсь, что пишу не на английском...
[ZTE Axon Pro] Heze85:
it doesnt matter if open or not, but sometimes it takes more then one try on the pc - tool

---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------

---------- Post added at 05:15 PM ---------- Previous post was at 05:14 PM ----------

Updated from B03 to B04 . Firmware Online ZTE.

Earned voice assistant in English . Root flew off , but put back by the method above. I apologize that I am not writing in English ... translation

---------- Post added at 05:20 PM ---------- Previous post was at 05:15 PM ----------

some link for the b04-firmware !? thanks
[ZTE Axon Pro] ryaniano:
Axon elite Mi Assistant

Hi.

I am new to the ZTE Axon elite . It has the the latest version of Mi Assistant running on it.

I am at my wits end trying to sort out a problem.:

I have automatic call recorder Pro on the phone. What I'm trying to do is to get it working. It is 100% blocked.

I have allowed every permission known on Mi to no avail.

Mi keeps blocking it. Even when I turn it off (I Think) Automatic Call Recorder refuses to work.

I need to use this programme for references with my work.

I would be eternally grateful for any help.

You possibly might need to download Automatic Call Recorder Pro from the play store. It's free...

Best Regards.

Ian Ryan. SLIGO. Ireland.

ryanian@iol.ie :(
[ZTE Axon Pro] aga75:
http://myzte.ru/disk/o…AxonMini_V1.0.0B04.zip
[ZTE Axon Pro] aga75:
Это всё этот mi assistant блокирует все записывающие звонки программы. Отключал, замораживал, удалял( titanium), всё одно- не работает. Писал в поддержку, попросили список прог с которыми не работает, сказали, что разберутся. Уже два месяца разбираются. По ходу только кастомная прошивка с вырезанным mi assistant или антивирусов. Но для нашего тела даже рекавери кастомного нет. Тел хорош, но нет умельцев довести прошивку
[ZTE Axon Pro] Crisvendetta:
disable mi assistant in settings
[ZTE Axon Pro] Nerd777:
Succesful update of russian B04 firmware. The system seems a little bit more smooth, notification led bug in charging (sometimes work sometimes not) seems fixed.

ITALIAN language present!

Dolby digital bug (when you plug headphones goes off everytime) not fixed.

Succesful rooted with files at page 4, B2016. I'm going to install adaway, finally...

Thank you guys
[ZTE Axon Pro] Crisvendetta:
the download always fails at 90% any link for software other than that?
[ZTE Axon Pro] Nerd777:
http://zte.ru/smartphones/axon/axon-mini-/

Translate and go at the bottom of the page, there you find the direct link
[ZTE Axon Pro] aga75:
А он сам включается при попытке записи и отключает программу rec.
[ZTE Axon Pro] Heze85:
cant download the update , site give me error 404
[ZTE Axon Pro] Crisvendetta:
You must doenload it from the phone.

Go to myzte.ru select support/axon mini/ and there you can find the software to download. I have noticed the system to be slightly smoother and more fluid but cannot confir lm this 100% still.
[ZTE Axon Pro] Wurstwa55er:
No problems downloading the B04 from the russian site (with pc).

(Can someone please make a md5-sum of his working update-zip, so I can proof my dl first?)

thx

I wonder, that on the HK-site of zte the B03 is still the actual one ....
[ZTE Axon Pro] Crisvendetta:
The china version is on B08 now
[G4 Q&A, Help & Troubleshooting] Rosa Elefant:
I'm lost.

I updated to 20A, finally unlocked my bootloader and reinstalled all apps. Worked quite OK. Then I decided to root my phone again so I can use texdroider. (Yes, that is an important app for me.) I used fastboot boot to boot into TWRP (latest 2.8.7.0) and chose "Install SuperSU". Then I let it reboot.

Now it's stuck at the LG logo. No adb connection available.

Help!!11! *screams hysterically*

(Please.)

edit:

Turns out SuperSU was too old. Flashing the 2.66 build instead of the built-on one fixed it.
[Samsung Galaxy Ace 4] BrenoBR:
exist?
[Samsung Galaxy Ace 4] zenug:
No one being interested to do it
[Samsung Galaxy Ace 4] David Masa:
I'm on a WIP regarding this -> https://xdaforums.com/ace-4/development/wip-porting-galaxy-ace-4-neo-sm-g316ml-t3805962
[MTCB Android Head Units Q&A] lotherius:
OK, so I got everything working on my unit back in November. Bluetooth worked fine and connected with my phone and OBD device (OBDLink LX).

Suddenly within the last couple of weeks, it's stopped connecting. I have tried rebooting the radio, unplugging/replugging my bluetooth OBD, unpairing the phone, repairing, etc... Nothing seems to work for more than a few minutes. Sometimes it will work for one trip, but then the next trip it's back to REFUSING to connect to either bluetooth device. Remember - BOTH worked before, and I didn't change anything.

Since it's happening with both my Phone and my OBD device, it appears like it is a fault in the stereo. I really don't want to do a full factory reset as that would entail many hours sitting in the car wasting gas idling while I reinstall/reconfigure EVERYTHING only to not even be sure it won't do this again.

Anybody have any tips on something I can do to fix this? There does not appear to be any kind of "unpair" option in the bluetooth settings on the radio itself. I'm wondering if there's a way I can manually reset just all of the bluetooth settings - blow them away and start over without resetting the whole device.

This is a pretty big deal - one of the #1 reasons I bought this device was for OBD datalogging. If that feature does not work, I will rip it out of my dashboard and ebay it. PERIOD...

Adcice?
[MTCB Android Head Units Q&A] lotherius:
Nobody?

I tried changing the bluetooth device name, changing the PIN and re-pairing my devices. They work intermittently, but 90% of the time won't connect, or if they do, they won't stay connected.

This is turning my radio into an expensive piece of garbage... :(
[MTCB Android Head Units Q&A] themissionimpossible:
Try keeping wifi on all the time (even if not actually connected to any network).
[MTCB Android Head Units Q&A] lotherius:
I do have Wifi on all the time. I have an LTE Hotspot I keep in the glovebox of my car that powers up as soon as the car powers on. So there's 100% wifi coverage for my stereo no matter where I'm at.

I can randomly get it to connect, but it won't stay connected. When I'm in the bluetooth menu, the devices will actually disappear from the paired devices list. Both paired and available will go blank just suddenly as the devices drop off. Then they'll reappear on their own. So it appears to be the bluetooth stack is crashing - but I'm not sure why.

It is a KLD RK3188 unit. Running latest MCU (came preloaded, just bought it in November - I haven't put a new MCU) and recent firmware, which is a stock firmware, not MalaySK (MalaySK doesn't support the digital display below the screen on my unit)...
[MTCB Android Head Units Q&A] lotherius:
At this point this unit is trash if I can't keep Bluetooth working more than 10% of the time.

Sent from my OnePlus One.
[MTCB Android Head Units Q&A] themissionimpossible:
Some smartphones might show an incompatibility with the radio's BT stack. To be sure try with another smartphone.
[MTCB Android Head Units Q&A] dakkara303:
I would see if it pairs reliably with just one device at a time. My phone has issues connecting with the HU if I first connect my BT headset to the phone but works fine if I do it after. Also the construction of these seems to be sub-par and it could be the bt device or antenna in yours was not connectec/mounted well and you hit a pothole and now its not attached/broken/loose. It may be worth opening and looking inside for something that broke off or is loose. Finally, I have had (well still have) my factory settings change randomly and have to go in and reset. There are settings in the for BT module and it may be worth looking to see if yours are correct.
[MTCB Android Head Units Q&A] stormlabs:
I also have problems with mine but I'm running Marshmallow in my OPO. As soon as i go back to Lollipop (CM 12.1) it works again.
[MTCB Android Head Units Q&A] lotherius:
Turns out I think it's the OPO. Mine has issues even with 12.1. I think it's based on Modem version not firmware version. Your modem may have been changed when you went back to 12.1.

For me changing modem versions is something I really want to avoid. I hunted forever for a modem version that didn't constantly drop WiFi and LTE, finally found one, and I think that's when the Bluetooth issues started. Every time I flash a modem to the OPO it becomes a nightmare. That phone really does not want you messing with the firmware which is not what I expected when I bought it.

For now I'm back on my old Nexus 5. No problems. I may just sell the OPO and never stray from Nexus again.
[MTCB Android Head Units Q&A] stormlabs:
Hmmm.

My OPO doesn't connect to the headset but my chinese BT OBD dongle connects fine and works.
[MTCB Android Head Units Q&A] maximosm:
I have the same problem with my unit but phone working.Only obd2 adapter some times not connecting.Have you find any solution?
[MTCB Android Head Units Q&A] noodlemctwoodle:
I have a similar issue with the Pixel XL.

Previous I was on a Nexus 5 Bluetooth worked perfectly every time without fail, could make calls, listen to music and sync address book no issue.

Now since moving to the Pixel XL I have an issue connecting to the head unit. The head unit shows as a connected device, but then flashes green then grey, green, grey showing connected, disconnected... I can still stream music from my phone over Bluetooth, but voice is not achievable.

Like suggested it's likely to be the BT stack in the handset rather than the head unit as works fine with Nexus 5. Highly frustrating and likely no fix unless it can be patched by software update :@
[MTCB Android Head Units Q&A] Syphe:
I'm also having the same problem as you noodlemctwoodle on a Nexus 6P with 7.1 developer preview.

I've un-enrolled from the beta program this morning, waiting for the ota to come down, as soon as it does will re-test and let you know if it's working, as I suspect it is a problem with the bluetooth stack in 7.1
[MTCB Android Head Units Q&A] mr.hackerly:
MTCD MLT (Xtrons TD618AS) Bluetooth and OBD Reader

I have had issues with the Bluetooth on the MTCD MLT V1.76_1 (Xtrons TD618AS).

I found a work around which allows me to use the OBD reader successfully. I downloaded an Android Bluetooth App and toggled off the Bluetooth. Once the Bluetooth was toggled off I was able to access the OBD reader by using the "Piston" OBD app. I tapped on the car picture and waited for the app to think about things. Once the app finished thinking I was able to start capturing the live OBD data by pressing the play picture. I am only speculating, but I feel as though perhaps the firmware engineers goofed. This is even the OBD reader that Xtrons promoted as compatible with the TD618AS stereo I bought with it at the same time. Not to mention that I continually lose FM radio even though the stereo was professionally installed and no wires were cut. I was very excited, and now only depressed.
[MTCB Android Head Units Q&A] CARRisma:
Which Bluetooth app did you download?
[One (M9) Q&A, Help & Troubleshooting] sishirbaid:
After android 6.0 many users have been facing issues with rooting their htc one m9, here's a simple way to do so.

prior knowledge required- how to use adb , fastboot to flash recovery and if in case any thing goes wrong , head over to this thread of mine for some help ( http://xdaforums.com/one-m9/general/best-unlocking-bootloader-rooting-guide-t3087354 )

I) ROOTING :

1> flash twrp-2.8.7.1_beta 1 as your custom recovery it can be found here (http://xdaforums.com/devdb/project/dl/?id=13383) - this is the system-less root

2>use superSU 2.64 (beta) to gain root and not the classic swipe to root when you reboot system . it can be found here (https://download.chainfire.eu/750/Su...1220185127.zip)

3>You are good to go :) your phone might boot-loop a few times , let it do its work , give it ten mins. if nothing happens in 10-15 mins , redo the entire process.
[One (M9) Q&A, Help & Troubleshooting] freighter2298:
this worked for me
[One (M9) Q&A, Help & Troubleshooting] billgates420:
Thanks a lot man, this worked for me. I had been trying a few different guides for the last couple of days and none of them had worked for me. I never got past the bootloops.
[One (M9) Q&A, Help & Troubleshooting] Cube144:
Hello, I do not know anything about rooting. Do you have any links on how to learn the basics of rooting so I could follow this guide? I have an HTC One m9
[One (M9) Q&A, Help & Troubleshooting] Hungos:
sprint htc m9 is root or not it
[One (M9) Q&A, Help & Troubleshooting] computerslayer:
Create a new thread rather than resurrecting a months-old discussion. When you do, a complete question will help us understand what you are asking.

See you in your new thread

- Computerslayer
[Android Q&A, Help & Troubleshooting] stephanepi:
I want to flash my cube i7.

I achieved to set ro.secure=0 ; ro.adb.secure=0 and ro.debuggable=1 by splitting the boot image i use to boot with fastboot.

ADB allow me to enter in root mode (adb root) but when i want to mount the system in rw, permission denied.

No way neither to push a file.

I can enter in some folder, according the permissions specifics to each one of them, but since i'm a normal user, i can't write anythinx in order to push supersu.

Well, I think the cause is selinux policy preventing adb (or adbd) to gain administrator privilège.

So here the questions ?

Is there a way to mount system at boot time (what i did already with fstab) to allow me to modify it ???

Is there a way to disable selinux for just a boot ???

Can i split the file system at cold state, modify file system, and flash it again in memory with proper permission ???
[Sony Cross-Device General] RyTekk:
[TWEAK][S800/801] Tunable interactive & VM optimized - performance, battery, coolness

This is a small tweak to optimize the interactive governor that will makes your phone to be more smoother and cooler, also CPU clock won't gain aggressive like Sony's setting. I edit some VM (Virtual Memory) as well, maybe it'll increase some performance and battery life.

Feature:

Interactive governor optimized: based-on CM 12.1 kernel settings
VM optimized: based-on Kickasskernelizer by @[URL="https://xdaforums.com/member.php?u=3357461"]zeppelinrox[/URL]
Core control thermal manage

Changelog:

**********************

[B][COLOR=Green]10 Jan 2016[/COLOR][/B]: Initial

**********************

[B][COLOR=Green]07 May 2016[/COLOR][/B]: update to MM file, set 1 to minimum core online all time,
separate to two versions:
Normal: with core control enabled (default)
Perf: without core control

**********************

[B][COLOR=green]15 May 2016[/COLOR][/B]: add more two versions with each cores governor profiles:
Balance: [COLOR=Red]core0,3[/COLOR] [COLOR=Blue]interactive[/COLOR] | [COLOR=red]core1,2[/COLOR] [COLOR=blue]conservative[/COLOR]
Battery: [COLOR=red]core0[/COLOR] [COLOR=blue]interactive[/COLOR] | [COLOR=red]core1,2,3[/COLOR] [COLOR=blue]conservative[/COLOR]
[I]perf and non-perf (normal) are same as 07 May update desciption above[/I]
[B]Thanks to @dontbelive and @PDesire gave me suggestion for this update[/B]

**********************

[STRIKE][B][COLOR=green]30 May 2016[/COLOR][/B]: force enable Core Control (main msm thermal part) and
VDD Restriction, hope it would reduce temperature from restriction of VDD
(cpu voltage), from that point will gain a little performance even S801 is really
good at keep the stable in heavy loads.[/STRIKE]
It seems that there's a problem with VDD on shinano, removed.

**********************

Dowload:

Requirement:

Lollipop 5.1.1 (23.4.A.1.264)

Marshmallow 6.0.1 (23.5.A.0.570)

It might work on other firmwares as long as Lollipop and upper.

Recovery (TWRP is recommend)

Stock kernel is highly recommend, it also works on other kernels.

P/s: MM versions should work on LP, there's just a very small change in files that I editted from stock.

I've test on Z2 (LP only), it should works on Z1, Z1c, Z3, Z3c (S800/801).

Install: Flash via recovery and all done.

If you wanna back to old setting, go to /system/etc, delete two files init.qcom.post_boot.sh, set_governor.sh and rename those one with *_bak OR flash the revert zip in the attachment.
[Sony Cross-Device General] ryandxter:
Some simple question:

1. What's this mod requires? (eg. Root, Recovery, etc) It seems for UBL or somewhat?

2. Determined to question #1 does this works under LBL?

Thanks for advance
[Sony Cross-Device General] RyTekk:
1. Root & recovery is required, of course.

2. It works on both UB/LB, but I didn't test with custom kernel because I'm using LB.
[Sony Cross-Device General] FalleN_lMaster:
Awesome bro

Good work lml
[Sony Cross-Device General] heineken78:
Testing it on Infocus m810!

Good gob so far!
[Sony Cross-Device General] heineken78:
After night of battery test, I have got the same battery life but with extra 30 % performance.

SD801-AC, 2gb

AMAZING!!!!

Much better than of performance, same battery life as on demand!

Made installation as init.d script. Initiated from init.qcom.post_boot. easy-to-remove.
[Sony Cross-Device General] The Bankshooter:
For those who has tried, Is this safe for Z1? There a battery change?
[Sony Cross-Device General] semder:
xperia z locked 5.1.1 existenz rom here. anyone tried?? is it usefell and/or safe? thanks.
[Sony Cross-Device General] RyTekk:
It should work on Z1 because it uses msm8974 board too, but my aim is improve performance, not improve battery.

I've just edited values which are in msm8974, Xperia Z used apq8064 board so it won't be effect.

init.qcom.post_boot.sh will run before init.d scripts, and maybe someone don't have init.d support, but that's your choice :)
[Sony Cross-Device General] The Bankshooter:
Your processor ir Snapdragon S4 Pro, this mods allow only Snapdragon 800 and 801 series
[Sony Cross-Device General] hoangpro1234:
Hi pro. I want to use it for AOSP rom ?