yashsingh1/xdaforums huggingface dataset:
[One (M9) General] Myrmeko:
So, before you install anything be sure you have a way to restore your phone if anything goes wrong.

I do NOT know if those require a certain variant of the M9.

And i also havent tested any of those because i dont have the patience to download anything from Baidu. It takes way too much time. Or i simply dunno where the download link is because i dont speak chinese.

So, install them at your own risk.

And have fun. :)

Future Interactive UI (5.1.1/6.0.1):

http://www.fiui.org/download.html

Moonlight OS (7.1.2):

http://m.romjd.com/Rom/Detail/141020

Moonlight OS (6.0.1):

http://m.romjd.com/Rom/Detail/129985

FlymeOS (6.0.1):

http://m.romzj.com/rom/68480.htm

FlymeOS (5.1.1):

http://m.romzj.com/rom/41056.htm

Modern Lagoon (6.0.1):

http://bbs.zhiyoo.com/forum.php?mod...age=2&filter=typeid&typeid=16470&typeid=16470
[Samsung Galaxy S8 Themes, Apps, and Mods] sp1312:
Today I got an update where Bixby vision got changed to Note 9 version. Got all the Bixby features live translation, image recognition etc.

Anyone got it yet?
[Samsung Galaxy S8 Themes, Apps, and Mods] eXPerience1983:
Yes, yesterday on a S8+ with Spanish ROM

Enviado desde mi SM-G955F mediante Tapatalk
[LG V30 Questions & Answers] scytalemk:
Hello, a week or two ago I have Android Pay on my LG V30 and LG Watch Urbane 2, and now seems it dissapeared. I can't find Android Pay app neather on phone or watch? Someone help?
[LG V30 Questions & Answers] ChazzMatt:
Try reinstalling it?
[Xiaomi Mi A1 Questions & Answers] KronozFX:
Hi,

I am personally very satisfied with this GCAM, and I don't feel the need to mess up with the below more-than-simply-advanced settings, however if someone with the right skills is able to push further the quality of A1's photos, then why not?

So I'd like to know if someone is interested in experimenting with these settings or if just anyone has some suggestion about this.

The thing is that probably the settings are optimized for a specific SENSOR and DEVICE, and our A1 is kinda different from the Pixel bloodline... so thanks in advance to anyone who looks up into this.

[IMG="Settings location"]https://i.imgur.com/41ZtSt3.jpg[/IMG]

[IMG="First part"]https://i.imgur.com/NiRs4AB.jpg[/IMG]

[IMG="Second part"]https://i.imgur.com/yOwRv76.jpg[/IMG]
[Samsung Galaxy S9  Questions & Answers] kjplasma:
Just switched back to Android from iOS and apparently it seems like Android\S9 does not allow answering calls via Bluetooth Headsets at all? Is there a fix or mod for this?

I'd like to answer Whatsapp, Viber, Skype type calls via the answer key on the car steering wheel same as what iOS allowed me to.

To clarify - once I answer the call on the phone, I can then talk via Bluetooth no issues. The problem is using the answer button on the car or headset to pick the call. Normal calls are not affected.

All my google-fu has returned futile as it seems this is not possible with Android yet.

I have also tried another Jabra Bluetooth headset and it is no different.

Thoughts?
[Samsung Galaxy S9  Questions & Answers] Docmjldds:
No problems answering on my Malibu 2016 using connect button. Not to mention Android Auto also works fine, but of course USB chord connected. But even when NOT using AA, I can answer or disconnect with car controls just fine.
[Samsung Galaxy S9  Questions & Answers] kjplasma:
What VOIP app are you using when you mentioned that you can answer calls? Have you tired answering a Whatapp or FB call?
[ZTE Axon 7 Guides, News, & Discussion] rzarectha:
Updated OP since this thread became useful to track if magisk works with our stock ROM.

The most recent version you can use at the moment is magisk 16.7 and magisk manager 5.8.3.

I suggest that you change the update channel to custom and set the address to 127.0.0.1

For the most recent Magisk version:

Thanks for checking [MENTION=5059016]mickey36736[/MENTION]
[ZTE Axon 7 Guides, News, & Discussion] raystef66:
I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:

Open Manager and update. Download latest stable one and flash it. Reboot.
[ZTE Axon 7 Guides, News, & Discussion] rzarectha:
mine bootlooped on stock. I'm naive enough to wait for the big update ;) also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build

update: it bootloops on stock no matter what channel (stable/beta) you get it from.

I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.
[ZTE Axon 7 Guides, News, & Discussion] Oki:
You can change the OP tittle by pressing Go Advanced button next to the Save button when editing the OP post.
[ZTE Axon 7 Guides, News, & Discussion] Prophet 5:
Not only on stock...

I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...

I installed the zip of an earlier version to no avail.
[ZTE Axon 7 Guides, News, & Discussion] rzarectha:
use the uninstaller zip first
[ZTE Axon 7 Guides, News, & Discussion] koftheworld:
Try 17.1. supposedly solves the bootloops.
[ZTE Axon 7 Guides, News, & Discussion] trevor68:
bootloops are easily fixed by using the uninstaller first.
[ZTE Axon 7 Guides, News, & Discussion] KwesiJnr:
Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7
[ZTE Axon 7 Guides, News, & Discussion] koftheworld:
You have to use the uninstaller first and then flash 17.1.
[ZTE Axon 7 Guides, News, & Discussion] pnin:
Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:
[ZTE Axon 7 Guides, News, & Discussion] koftheworld:
Did you use the magisk uninstaller? If not, just reflash your bootloader
[ZTE Axon 7 Guides, News, & Discussion] marcdw:
Excuse my ignorance but how would reflashing the bootloader help. Doesn't Magisk modify the boot image?

I figure that if flashing the uninstaller and then flashing v17.1 still results in a bootloop I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image). Flash Magisk 17.x afterward.

That said, I am a non-Magisk kind of guy (not present on any ROMs or devices) so I might not know what I'm talking about. [emoji16]

Dark ROM. FTW. [emoji41]

ZTE Axon 7 A2017U, AospExtended v4.6 ROM, LlamaSweet 0.5 Kernel, microG (NoGapps), Multiboot, XDA Legacy
[ZTE Axon 7 Guides, News, & Discussion] pnin:
Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again... :(

I have even had to restore recovery through fastboot mode now. :silly:
[ZTE Axon 7 Guides, News, & Discussion] amphi66:
I did not flash Magisk 17.x on Stock B35 (stayed with v16.4), but installing the latest Magisk Manager (v5.9.1) resolved the previous SafetyNet Check errors
[ZTE Axon 7 Guides, News, & Discussion] DrakenFX:
Using stock anything above and v17.0 will bootloop using stock,

Just my 2cents, if that your issue just do the following:

-Download v16.7 first in case you don't have it yet, and move it to the SDCard.

* Head back to TWRP

* Flash v16.7 or your preferred release.

* You're good to go.
[ZTE Axon 7 Guides, News, & Discussion] marcdw:
Not sure to be honest. Last time I had Magisk was around v15.x. When I initially rooted my Moto Magisk was part of the process. Even though the stock ROM is using SuperSU it seems I didn't fully remove Magisk. I have the following remnants visible in TWRP...

/data/magisk

/data/magisk.img

and files in /data/adb/

Not sure why everything is failing so badly on your end. I can't test things on my Axon 7 since I use DualBoot Patcher where Magisk is a no go.

Moto G5S Plus XT1806, MSM-Xtended v2.5 ROM, MultiROM, XDA Legacy
[ZTE Axon 7 Guides, News, & Discussion] pnin:
So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).

Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).

I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.
[ZTE Axon 7 Guides, News, & Discussion] christoophat:
I'm not currently having Magisk issues, but Google Messages, after the recent update, does the same here. Gave up on it & switched to Textra.
[ZTE Axon 7 Guides, News, & Discussion] rzarectha:
New beta version released. Still bootloop
[ZTE Axon 7 Guides, News, & Discussion] SkaboXD:
Thanks for warning us, i was close to flash it.
[ZTE Axon 7 Guides, News, & Discussion] greyhamism:
Any updates to this?

Currently on 16.6, and most of my modules need 17+ to update. On the Oreo B12 Beta.

Cheers :)
[ZTE Axon 7 Guides, News, & Discussion] kraljan66:
Hi all....today I made update of MAGIS(probably to 17...i´m not sure nr of version) and now has a bootloop...problem is I can not get to TWRP!....I see only boot logo, then restart and boot logo again = after that 3x red led....

I was on Nugat b12 this rom: https://xdaforums.com/axon-7/development/rom-slm-dfnr-t3842931

any idea?

hehe it looks like DFU brick....fck brick after magisk update....fck fck.
[ZTE Axon 7 Guides, News, & Discussion] Predatorhaze:
i dont even understand why you update magiks on that rom.Ray even mentioned only 1 magisk works.

Maybe you should try instal twrp again trough EDL or something (edltool)

i believe this is not really a brick,can be solved trough edl.But maybe im wrong
[ZTE Axon 7 Guides, News, & Discussion] kraljan66:
At the moment have only win10 or linux...and have a problem with qualcom driver...so will taste it with my old PC WIN7....so we will see...
[ZTE Axon 7 Guides, News, & Discussion] GodOfPsychos:
I just remembered, this bootloop issue also happened for some pixel devices on magisk v17 (or higher). It was once in the xda news (sadly i can't seem to find the article). In the news it stated that topjohnwu fixed that issue in the canary builds. Maybe you can try out those. Just beware that they can be unstable.

Here is the official thread to the canary channel:

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

How to add the canary channel to magisk:

In the official thread click on release channel and copy the browser browser url (https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/release.json)

Now go into magisk settings and go to update channel. Change it to custom and paste the copied url there.

Idk if it works or not. But in case something happens, there is also a canary uninstaller linked in the canary channel thread
[ZTE Axon 7 Guides, News, & Discussion] rzarectha:
Thanks a lot for the tip.

I flashed it on B02, unfortunately it has the same behavior. Boots up to the "your software is corrupted" screen then reboots. Over and over.

It's good it's being looked into though, let's hope!
[ZTE Axon 7 Guides, News, & Discussion] Dodgexander:
Guys please take the time to note you also have the issue to try and get it fixed:

https://github.com/topjohnwu/Magisk/issues/729

https://github.com/topjohnwu/Magisk/issues/758
[ZTE Axon 7 Guides, News, & Discussion] bluenote73:
18.x is out, have you tried it? I'm lazy and hoping to save myself the trouble of finding out it doesn't work.
[ZTE Axon 7 Guides, News, & Discussion] jeboo:
Magisk 18.0 still bootloops with stock B20 kernel. However, it works fine with the custom asder kernel.
[ZTE Axon 7 Guides, News, & Discussion] dodo34:
Magisk 18.0 does not work with A2017G Stock Rom Oreo. Any solution ?
[ZTE Axon 7 Guides, News, & Discussion] klałn:
To use Magisk 17.0+, use modified kernel by asderdd.

It works on latest B19(A2017) and B03(A2017G) ROMs.
[ZTE Axon 7 Guides, News, & Discussion] dodo34:
That is for US Modell and stability is questionable.
[ZTE Axon 7 Guides, News, & Discussion] Dodgexander:
It doesn't work and the issue remains open on GitHub.
[ZTE Axon 7 Guides, News, & Discussion] garryb:
hey how are you? sorry guys to bump up this post [MENTION=2471504]jeboo[/MENTION]

please do you use discord i need your help with aboot on a samsung j415fn if you can message me back here i would really appreciate the help.
[ZTE Axon 7 Guides, News, & Discussion] rzarectha:
Hello guys! Magisk 19.1 Stable is out now.

Anyone had the chance to test it on stock? I would but I'm at work and I don't have access to a PC with adb
[ZTE Axon 7 Guides, News, & Discussion] Predatorhaze:
not true
[ZTE Axon 7 Guides, News, & Discussion] rzarectha:
I revived the thread because it's relevant for us to discuss if Magisk 17+ is now viable on our stock ROMs.

Thanks for your contribution. You started to argue with a post 228 days old.
[ZTE Axon 7 Guides, News, & Discussion] rzarectha:
I will answer my own question. Unfortunately, the latest stable magisk is causing a bootloop for oreo b03
[ZTE Axon 7 Guides, News, & Discussion] joaocandeias:
Thanks for the feedback! I was about to update magisk
[ZTE Axon 7 Guides, News, & Discussion] mickey36736:
Same for me as well.

Even I tried the custom version of magisk from here. (19.2)

https://github.com/ianmacd/MagiskBuilds

It's still bootloop after the penguin sign.

Flash the magisk 16.7 back and it boots just fine.
[ZTE Axon 7 Guides, News, & Discussion] GodOfPsychos:
Yeah. Its because of the stock kernel and something about zte-policy stuff inside it.

Idk if it works on b03 (im still on b02) but im using the kernel from asderdd which fixes the bootloop issue (and of course the modem modules in the same post of his to have wifi working). And it works. Even though it states its for A2017U oreo, it works flawlessly for me on my G.

https://xdaforums.com/axon-7/development/kernel-magisk-17-stock-roms-t3856809
[ZTE Axon 7 Guides, News, & Discussion] rzarectha:
If someone is willing to try again:

- [General] Fix bootloops on some devices with tmpfs mounting to /data

I can't test it because I'm on the Slim stock so it works by default
[ZTE Axon 7 Guides, News, & Discussion] mickey36736:
I tested 19.2 on B01 oreo and it still bootloops.

Flash 16.7 back and it's working again.
[ZTE Axon 7 Guides, News, & Discussion] mickey36736:
I tested 19.3 on B01 oreo and it still bootloop.
[ZTE Axon 7 Guides, News, & Discussion] rzarectha:
I will update OP to make it easier to find the info
[ZTE Axon 7 Guides, News, & Discussion] roadworker:
I got 19.3 working on an Axon 2017G with raystef66's Slim B03 ....

Steps :

Install Nfound' s TWRP 3.2.1.8 Axon 7 Oreo.

From within TWRP,install raystef66's B03 bootstack.

Install Slim B03.

Run Raystef66's A2017G_O_system_permission_enable patch.

Install Magisk 19.3.

reboot (don't clear cache and dalvik)

After the reboot,you'll get an error about a damaged sdcard,if there's 1 installed .....ATM,I didn't found a way to format it as removable storage,because the format doesn't work,no matter what filesystem is used for the refreshing.

However,formatting the sdcard as extra internal storage works,and is recognised by the systm,so I can live with that... ;)

Reboot,go to TWRP ,clear cache and Dalvik and you're good to go.......@ least,I got so far with this approach.... ;)
[ZTE Axon 7 Guides, News, & Discussion] joaocandeias:
Oh so that's why i got that sd card errror. I had to format the card to fat32 and it started working fine again as removable storage
[ZTE Axon 7 Guides, News, & Discussion] mickey36736:
It's been a while and today it's the end for stock rom user.

Today, Safetynet has some new update that finally broke magisk hide for old version of magisk.

For stock user now require to use custom rom instead that support magisk 17+ and higher.

And yes, I tried magisk 20.3 and it bootloop back to recovery screen.
[ZTE Axon 7 Guides, News, & Discussion] pOOBAH1973:
Damn.. I'll see how long my Banking TAN app keeps working.

I don't want to be forced to reinstall everything.

I'm just using magisk because of GCam.
[ZTE Axon 7 Guides, News, & Discussion] bluenote73:
My magisk manager from 16.7 crashes constantly, is it just me?
[ZTE Axon 7 Guides, News, & Discussion] gecata93:
Hi, im completely lost now what to do next.

I followed a guide enable twrp rooting magisk

And now i have A2017UV1.1.0B35 nougat (7.1.1) with twrp. I want to install the latest version of magisk but phone end in bootloop as written here in this thread. Last working magisk version is 16.7 but it is too old magisk manager crashes and cant install modules( smali patcher module) on it.

I see that there is kernel solution for Oreo, but i cant find bootstacks for my model (A2017U) to try this solution, i think i saw only for A2017G model.

Second choice is custom rom and this is like deep ocean for me, i have no idea what to do. Which custom rom would work okay with latest magisk version and my phone model?

I would be very happy if someone point me to a guide or a solution, all i want to is to make latest magisk work.
[ZTE Axon 7 Guides, News, & Discussion] amphi66:
On Stock B35 you should have TWRP 3.2.1. Magisk 16.7 w/ Magisk Mgr 6.1 work just fine. Try flashing the Magisk uninstaller to insure you are working from a clean start & you should have no issues. Good luck.
[ZTE Axon 7 Guides, News, & Discussion] jawz101:
Why do you need a specific version of twrp? It's just a recovery partition. Can't you just go to twrp.me and get the latest official version?

I've absolutely hated the custom ROM scene on this phone since day 1. Everyone made a "here's how to do it" guide and they all recommend specific versions of things made by specific users. As if they all fix some certain issue. Every time I tinkered with this phone I was compelled to review 10 threads to ensure I had the most ironclad instructions.

In the end I returned to stock a couple of years ago because it was just too much confusion on here.
[ZTE Axon 7 Guides, News, & Discussion] amphi66:
Unfortunately not. TWRP revisions are tied into bootloader code & if theTWRP rev is not compatible you will not boot w/ solid red light or bootloop.
[ZTE Axon 7 Guides, News, & Discussion] klałn:
Nougat B12 kernel, patched with Magisk 22.1, doesn't cause bootloop.

Some of you may try and move from Magisk 16.7.

N B12 kernel, no dm verity with forced encryption below.

Sadly, no change on Oreo B02 and B04 kernels.
[Samsung Galaxy S7 Questions and Answers] gotroot64:
I don't know how this happened but this problem randomly appeared where /system in the mounting option keeps being unchecked after rebooting and I can't edit the files.

I've tried formatting, flashing the firmware and flashing TWRP but it still gets unchecked. It's also strange that internal storage can still be used with no problems and flashing zips it's just /system stays read only no matter what i do.
[Samsung Galaxy S7 Questions and Answers] gotroot64:
bump
[Samsung Galaxy S7 Questions and Answers] gotroot64:
b2
[Moto X4 Questions & Answers] Ermes.mt/brasil:
I saw in several websites. And in several places that performance adreno 508 maxima @ 850mhz. But in the moto X4 She is @ 700mhz. Someone who made root knows whether to say if this is a variation of the SDN630 or if it is the same chip but did a decrease of the power for some reason. If it has been a decrease, if you have to reach the @ 850MHz with root and with auditor kernel
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] attitude12:
Hey, recently i've been having issues with the proximity sensor on my vince. This started a couple of days ago when i decided i wanna go back to miui from custom roms and i did a full fastboot reflash. So basically i flashed everything clean without locking the bootloader.

And now the proximity sensor went nuts. (it was working fine until i flashed the fastboot rom)

It works, but barely. I gotta put my finger really close to the screen for it to actually work. So if i'm in a call it's annoying, screen is staying on since my ear can't get that close to turn off the screen, unless i press it hard against my head.

I've tried recalibrating it from miui, i've tried flashing different version of miui rom (both in fastboot and recovery) with no avail.

Also, i've removed the tempered glass i had on it and i cleaned its surface.

Anyone had this issue? Can anyone give me some pointers?
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] takke8:
Try flashing the custom rom which you used before flashing the miui roms...it may work...
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] attitude12:
Did that, i flashed a plethora of custom roms and nothing changed. I've read some stuff and maybe it's related to the persist partition, but i can't erase that in fastboot (something about image not being allowed to download), tho i can flash it. I've flashed the persist.img twice now, once with a developer stable rom and once with a simple stable rom. Still the same issue.
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] takke8:
Have you tried wiping the cache after the first boot of the rom (custom / miui)..?

If above doesn't work, try to turn off auto brightness(if enabled) and then check if the sensor works on call....
[Android Q&A, Help & Troubleshooting] BackCare:
So i bought a new battery for my S3 and its not switching on or showing any indication of being charged. i left on charge for a whole day and still no reaction.But my phone works on my old battery which is a little swollen . Oh and btw my phone is rooted with CM13 unofficial ROM. Please help me.
[ZTE Axon 7 Mini Questions & Answers] GotoDengo:
Does anyone else have a problem with video recording? No matter which app I use the camera hunts for focus occasionally resulting in the frame zooming in and out, or out and in, slightly. I can't manage to get more than 3/5 seconds of rock solid framing?
[ZTE Axon 7 Mini Questions & Answers] SGH-i200:
I have the same issue (LineageOS 14.1) and came here to ask which app I should use to avoid this problem! :(

This video shows the refocusing really well: https://www.youtube.com/watch?v=ZCcEp3oD4aY

Do you use the stock ROM or a custom ROM like I do?

Maybe ZTE will repair your phone?
[ZTE Axon 7 Mini Questions & Answers] GotoDengo:
It looks like your camera is refocussing a lot more frequently than mine! :(

I'm running the Stock ROM and camera app at the moment. I don't think it's a hardware problem as the camera does not refocuss when taking a still photo.

I can't have ZTE look at it as there's no service center in the UK (and I bought it from Gearbest).
[ZTE Axon 7 Mini Questions & Answers] SGH-i200:
You are right! :good: I changed the 'touch focus duration' in the LOS camera app from '0s' to 'infinite' and now the focus does only change if I click elsewhere! :)

There should a similar setting in the stock camera app!
[ZTE Axon 7 Mini Questions & Answers] GotoDengo:
I can't find such a setting in the stock camera app! :(

But I did find it in the Open Camera app! :)
[ZTE Axon 7 Mini Questions & Answers] SGH-i200:
Can you upload a screenshot of the video settings?

You mean 'Open Camera' (Camera App) - https://f-droid.org/app/net.sourceforge.opencamera? Which setting you changed? I had no refocussing without changing any setting.
[ZTE Axon 7 Mini Questions & Answers] GotoDengo:
Using Open Camera has fixed the problem for me!

The stock camera app only seems to have fixed focus settings for the stills camera! :(
[ZTE Axon 7 Mini Questions & Answers] SGH-i200:
To answer myself: The small icons in the menu represent the different focus modes! :good:
[ZTE Axon 7 Mini Questions & Answers] GotoDengo:
Yes it took a while to find the settings! The continuous autofocus setting ("c") causes my Mini to hunt for focus every 2/3 seconds. All the other settings work as expected with no hunting.
[ZTE Axon 7 Mini Questions & Answers] GotoDengo:
Doh! I've just found that you can lock focus and exposure using the Stock camera app! You just need to long press on the target circle after you have selected the object you want to focus on.

https://youtu.be/Un0FJCYKTcM?t=216

Once locked you can choose another object to focus another and it will lock focus on that without having to long press again.