yashsingh1/xdaforums huggingface dataset:
[Galaxy Note5 Q&A, Help & Troubleshooting] PRADEEPHONDA:
Galaxy apps never lists the Message app & I have the original default apk extracted & restored but somehow it's not working. So even have Flashed Stock firmware still no go but I know I have to wipe everything that will work but any mods who are having experience in making ROMs definitely know where the solution lies.

My storage is almost full & backing up definitely seems an difficult task at the moment as I'm running around with other things.

I'm no dumb to take your time mods so please help.
[Galaxy Note5 Q&A, Help & Troubleshooting] grxgen:
So While Replacing New Messaging App May Be For Eg.S9 Messaging App With Blue Icon Did You Replce It In priv-app/Messaging_SEP81 Or MessagingCommon Folder By Renaming The Target Apk With The Same Name? As Per My View This Issue Looks To Be Complicated..Flashing The Latest Stock Build Should Solve The Issue Itself But Unfortunately It Didn't So You Can Either Try To Replace Another Version Of Apk According To API Level On ApkMirror Or Try To Figure Out If App Shows In Settings/apps/show system app/clear data n cache if present there OR Try To Flash Any Custom Rom For Your Device And See If It Works On Custom Flawlessly Instead Of Stock
[Galaxy Note5 Q&A, Help & Troubleshooting] PRADEEPHONDA:
Hear is what I did, back up my existing data & wiping it in twrp gets back default app but again after restoring data gets me the same issue so gonna modify the backed up data & see where it goes.

I had gone almost full on storage so was trying to simple avoid the time to back up & restore but anyways it's the only Ultimatum now. As all mods prefer to remain in silent-no offense.

I have already fixed it but I would like to know if there are any who could help it out to resolve the issue in simplest manner. I have been working on it. May be it works or may be it doesn't to modify backed up data bcoz I definitely know the issue is in data but not system. So if someone gets into same issue as I'm then I just something left out for them to get their issue resolved by this post that's all. Cheers to all.

Thank you for your reply.
[Android Head-Units] Stivipg:
I have a problem with my unit , after change battery in car and five times cut energy , my unit stop work ok. Turn on and stuck on android logo . Revers camera work ok, but unit no sturtup android .

I try to enter recovery mode but no luck, only i found update mode (reset button and hold power on).

I try to find a firmwire for this unit but no firmwire on net.

How find firmwire , or enter some custom fw ? Or any solution to wipe data and factory reset ?

Sory for my bad english
[Android Head-Units] Stivipg:
maybe some recommendation to install custom rom ???
[Magisk] MasterSheea:
Hello.

Unable to flash magisk modules.

! /data/adb/magisk_merge.img mount failed.

Even via twrp recovery is no possible to flash magisk modules, says something like error 1.

The device is a doogee mix 2.

I was forced to install the normal xposed framework just to use it.

Root works; only modules have problems.

Can some expert find a solution, please?

Thank you in advance to everyone gives good news!
[Magisk] Jaymin.0.1910:
Hi, Can you attach logs while flashing ?? from both MM and recovery
[Magisk] Didgeridoohan:
Known issue on some MTK devices. Loop mounting doesn't work.

There are lots of reports like this for Doogee... There's been some investigating into it in the beta thread, but as of yet there's no solution, I believe.
[Magisk] MasterSheea:
Hello!

Yes, of course!

Logs of magisk installer and TWRP recovery here:

https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk

Ignore the crittografy error; I have tried to disable the crittografy and all is the same. Same problem.

In more, yesterday I had another annoying problem with magisk: before the options of the magisk app disappeared (there is the pic in the folder I attached. Then magisk is totally disappeared: magisk is not installed anymore in your device.

Tried to re-install magisk: nothing happens.

I have re-flashed the ROM and re- installed magisk: at moment is working.

Root files and SuperSU are not working.

I will open a new forum discussion for this problem.

Thank you in advance.

Greetings
[Magisk] Jaymin.0.1910:
The file is not accessible
[Magisk] MasterSheea:
Sorry.

Try now, please.

https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
[Magisk] Didgeridoohan:
Looks like recovery can't decrypt /data, so that's likely an issue there. But it'd be easier to tell if you had provided the recovery log rather than a screenshot (Advanced - Copy log after trying to flash).

And, it would also be very useful if you had provided a Magisk log rather than only installation logs.

But, it's probably a moot point anyway. Like I said earlier, this is a known issue with loop mounting on Doogee devices (and other devices using Mediatek). No solution as of yet...
[Magisk] Jaymin.0.1910:
Same here, provide good logs
[Magisk] MasterSheea:
Ok, thanks.

I will try to send you good logs.

About encryption, I have tried to disable encryption and to install all without encryption: nothing changes.

Before I must understand why magisk disappears from system, then I will collect logs about modules installation. Magisk is the only way to root this damned phone, SuperSU does not works.

Thank you in advance :)
[Magisk] Didgeridoohan:
There was no need to start a new thread about that... You've already got this one going.

The screenshot of the Manager you provided simply showed a Manager without internet access. Completely normal.

About losing root completely, make sure you don't have any aggressive battery optimisation on the Manager. More here:

https://www.didgeridoohan.com/magisk/Magisk#hn_Randomly_losing_root
[Magisk] MasterSheea:
Ok, good, I close the other thread :)

Yes true, that is a normal screenshot of magisk offline. Yesterday I did formatted data to disable encryption and I lost all the other screenshots, but was like this: before all options disappeared, then magisk disappeared.

No, no aggressive battery optimization running, but I have installed greenify and amplify... Perhaps one of this app makes problem?
[Magisk] MasterSheea:
I wish to close the other thread, but I do not know how to do it.

How to do it, please? :)
[Magisk] Didgeridoohan:
Make sure the Manager is removed from Battery optimisation and that it isn't selected I'm Greenify. It's not certain that this is the issue, but it's worth ruling out.

Other than that, a logcat of it happening, or even just a screenshot of the Manager when things aren't working. A Magisk log is also useful, of course.

Just let it be... :)
[Magisk] MasterSheea:
Oki.

I removed magisk from battery optimization.

I hope that at least the root will work.

But I seen in another thread that there is a solution known as f2fs workaround bug fixer. But is still not working. I hope that someone will fix it soon.

Anyhow, thank you for all :)
[Magisk] Pragnan Saha:
Move to thread https://xdaforums.com/apps/magisk/guide-magisk-official-version-including-t3577875. Flash last zip. Move to magisk manager, install updated (2018.3.6) version. All modules should now install fine.
[Magisk] MasterSheea:
Hello.

Thank you for the answer.

I have tried to flash the zip without success.

No magisk installation found or installed version is not supported.

Error process 1.

The magisk version I have installed is v16. - 5.6.4(112).

The last one, suppose.

Any suggestions, please?

Thank you in advance ?
[Magisk] MasterSheea:
I made also the this attempt: I have flashed a magisk module using flashify.

The flashing was successful, but the module is not in the magisk list.

Can be a permission problem? Someone knows where is the folder of installed magisk modules, please? Perhaps is a permission problem and changing permissions will work...
[Magisk] Pragnan Saha:
Download f2fs-loopback-bug-workaround-2018.1.31.zip from the thread. Place it in Download folder of internal storage. Reboot to recovery. Flash zip in twrp. Reboot. Open magisk manager. F2FS Loopback Bug Workaround should be installed in modules. I hope any module can be installed from now on.
[Magisk] MasterSheea:
Dear Pragnan Saha,

Thank you for your answer.

I have tried to flash f2fs-loopback-bug-workaround-2018.1.31.zip, but without success.

TWRP says: No magisk installation found or installed version is not supported. Error process 1.

Some suggestions, please?

Thank you in advance
[Magisk] basmeuter:
What thread? And is it about exact the same error ! /data/adb/magisk_merge.img ... What this thread is about?

Do you know if there's a fix already? I'm on ext4 so f2fs loopback makes no sense for me

And [MENTION=7870033]MasterSheea[/MENTION] do you have a fix?

I've got exactly the same error with flashing modules, after clean flask is possible to install modules but after 1 reboot it fails
[Magisk] MasterSheea:
Dear basmeuter,

No, sorry... I do not have found any fix.

And I do not will re-flash the ROM just for install some modules.

The normal Xposed framework works very good.

There will are no new OTA updates for this device in future, so even the normal SuperSu and Xposed are ok.

Of course, there are interesting magisk modules to try... a fix would be welcome :)
[Magisk] mhyr:
Same problem for me I have xposed installed with gravity box, I tried last update of magistrates and downgraded to version 15, non of them working, my bootloader is unlocked but I have stock recovery, is that the problem? Do I have to install twrp?

My safety net also fails

F2fs not working
[Magisk] h3sh11:
Same problem here in Moto G5
[Magisk] MasterSheea:
Please, could some genius Android programmist to find a solution?

Nobody is able to fix this damned problem?
[Magisk] Didgeridoohan:
You could try the f2fs loopback workaround module (that's linked earlier in the thread). It'll not install on Magisk v16.6+ though, not without an update and since it seems like [MENTION=5228676]VR25[/MENTION] is missing in action, you'll likely have to do that yourself. Or, install on v16.0 and then update if you want a newer Magisk version.

MTK devices are quite hopeless... If there's a solution, it'll likely be found eventually. No ETAs though...
[Magisk] JuliB.:
Ich hab das gleiche Problem, aber ich habe es gelöst indem ich einfach in den Recovery Mode gehe und da die zip flashe dauert zwar länger und du musst das handy immer Neustarten aber es funktionert. Sie werden dann trotzdem Normal in magisk angezeigt.
[Magisk] Didgeridoohan:
Hello and welcome to XDA. Thanks for your input, but you should know that you're required to post in English on XDA... Check out the rules for more info (specifically rule #4): https://xdaforums.com/announcement.php?f=5903
[Magisk] JuliB.:
Sry for the German xD I forgot that this thread was English.(dont know how I deleted it)What I want to tell u is I fixed the problem by simple download the app I want via magisk then put the zip in intern go in recovery and flashed it in the manager and start the phone
[Magisk] MasterSheea:
Dear JuliB,

Can you be more specific about the procedure, please?

I did tried to do it a lot of times, but always gives me the same error.

Which version of magisk are you using, please?

And which version of twrp.

Thank you in advance for your answer :)
[Magisk] Morris001:
I was getting the same error you mentioned originally in the post trying to download & install modules from Magisk on a Moto G5 Plus with a stock ROM. I tried the newest 'f2fs work-around' by flashing it via TWRP, which returned a success, but ultimately didn't work. After flashing it modules would say they installed, but after a reboot they disappeared from the Magisk Manager. Taking from what Didgeridoohan and JuliB. mentioned (thank you guys!) this is what worked for me:

1. Boot to recovery (TWRP 3.2.3 here)

2. Flash MagiskUninstall.zip

3. Wipe Davilk cache

4. Flash Magisk v16.0.zip (was v16.7 before)

5. Wipe Davlik cache

6. Reboot (mine took awhile to come back up)

7. Launch Magisk and download the .apk's when prompted for the newest Magisk Manager (5.8.3), but DON'T upgrade to the newest Magisk version.

8. Launch Magisk Manager and open Modules.

9. Download (don't install) the 'f2fs work-around' and whatever modules you want to internal storage (I did YouTube Vanced)

10. Boot back into recovery

11. Flash the 'f2fs work-around' immediately followed by your modules

12. Reboot

13. Open Magisk Manager and check your Modules. Hopefully they'll show as installed and function correctly.

After doing this I rebooted and verified everything still showed as installed and worked. I also installed another module directly from Magisk with no issues. The app still appeared as installed within modules and worked.
[Magisk] nicche:
I was getting the same error, after I flashed a new version ( the latest) of ROM called Havoc. I tried also too the newest 'f2fs work-around' by flashing it via TWRP, but at the first attempt didn't work. Finally I found this post and I tryed,with just one change, and it work! :), So Thanks to: Didgeridoohan, JuliB and Morris001 of course!

Morris001's version

My way with this specs:

- Device: Oneplus 3T

- ROM: HavocOs v2.0 Official Pie build

Steps:

1. Boot to recovery (TWRP 3.2.1-x_blu_spark_v8.61 )

2. Flash MagiskUninstall.zip

3. Wipe Davilk cache

4. Flash Magisk beta, last one version 16.7.zip ( I tried to flash v16.0 but when I reboot I didn't find magisk app, probably because it's a pie build)

5. Wipe Davlik cache

6. Reboot

7. Launch Magisk Manager and open Modules

8. Download (don't install) the 'f2fs work-around' and whatever modules you want ( I tried with Magic Charging Switch)

9. I personally moved the modules from magisk manager folder to Download folder

10. Boot back into recovery

11. Flash the 'f2fs work-around' immediately followed by your modules

12. Reboot

13. Open Magisk Manager and check your Modules. Hopefully they'll show as installed and function correctly.

Afert the boot I checked for the properly operation of MCS ( Magic Charging Switch) and it work.

So I installed another two modules directly from magisk witout any problems
[Magisk] Didgeridoohan:
So the ROM broke f2fs on a device that on a stock system has no issues? Might want to let the ROM creator know about that.
[Magisk] lolifer:
I also have been battling with this problem on my Huawei H1711(Ascend XT2) which does come with an encrypted data partition. It was my understanding once /data is formatted in twrp the encryption no longer lives. How can this be? I have tried all kinds of things but to no avail. I switched over to phhs sesuperuser 351 beta along with its manager and ran a system root like the old days...hehe.

I really would like to enjoy Magisk and when I try to flash the workaround f2fs zip, that fails as well. Im simply at a loss and could use some of you more experienced gurus help. :( It would be greatly appreciated I can tell you that much. My wife would thank you too since I would stop obsessing over it. haha :silly:

The only zips that work for me are osmosis' busybox, nano binary, and adb/fastboot, but as soon as I reboot they dissapear from the manager's "Installed" section.
[Magisk] Phoenixx2837:
MTK is the issue

I can state that this is a mediatek mtk issue. I have a Blackview BV8000 Magisk 17.1 I am having same issues..any options?
[Magisk] akki40112:
Getting same error while installing magic charging switch on magisk.other modules from magisk works fine for me.plz help
[Magisk] fadestyle:
i am having the same problem with a moto e4 xt1766. magisk and busybox will uninstall and magisk modules fail to install. i am going to try and unoptimize them in battery. above instructions seemed to have worked so far,
[Magisk] The_unknown_DF:
I solved this problem on my Huawei Nova (CAN-L11) like this - I changed /data partition file system from F2FS to EXT4, because workaround worked not like I expected, all modules would disappear upon 2nd reboot
[Magisk] Wandresjr64:
I solved it by installing a new kernel.
[Magisk] os_man:
Use latest 19.0 beta to fix
[Magisk] MAOQ:
Hello. I have such a problem.

In the firmware eRobot v1.2 (port from Galaxy Note 7) this was not before.

This is either due to the new TWRP v3.2 or Magisk v20.4 (this is my opinion).

In general, when I returned a clean backup, there Magisk v16.0 and a problem. When launched, it crashes with an error if Magisk is not updated to the last.

In short, the AM3D Zirene(link version 1.9.2) mod was installed while Magisk v16.0 was installed, and when it updated Magisk v20.4, the mod disappeared.

I wanted to remove the mod and install again, it did not work.

After installing the mod through Magisk, it appears in Magisk, but not in the application menu.

BusyBox from YDS(v1.29.2) is not yet installed.

Please help me, what should I do?

Phone Samsung Galaxy Note 4 (N910C), Exynos.
[Magisk] Didgeridoohan:
It's not a TWRP or Magisk issue, but a module issue. The installer for those modules simply haven't been updated to work with current Magisk releases. I believe Magisk v18.1 would be the latest release that would work (and that information is even stated in the AM3D Zirene link you posted). The installers would have to be updated if you want to install those modules now...

Edit: What should you do? Update the installers yourself (check the Magisk docs for how Magisk installers now work) or use other mods that have been updated.
[Magisk] MAOQ:
Ok, thanks for the info, but I thought something serious happened with Magisk or with TWRP. Even because of this mod, I changed TWRP (versions) several times and reinstalled Magisk. :)

Well, I’m not very good at it, maybe in a nutshell you can tell what exactly to do(update installers)?)))

I have been using this mod for a long time and some time after using my native amplifier Samsung (SoundAlive) decided to return to the AM3D Zirene.

But this dependency modules already got Magisk. :(

They gave us some kind of binary in the subject, and nothing happened after the replacement. Just installing and hanging Magisk.
[Magisk] Didgeridoohan:
The attached update-binary is compatible with current Magisk releases (although it isn't the latest one). The AM3D module is a bit complicated though (since it's using an old Unity template) and it's very unlikely that you can just drop it into the zip and things will work. More work is required (and I'm not the one that will do it). See the previously linked docs for what's needed.
[Magisk] MAOQ:
No, it has already happened, thank you. :)

I created a binary from your link and added it to the AM3D Zirene archive and after setting the rules worked.)))

But YDS BusyBox is not.

I think it is connected with the firmware.

For example, I have custom firmware and it is always installed in system/xbin, but for some reason it shows through the terminal that it is installed in /sbin.

Where it is not clear from there.

The Manager looked through the File, indeed BusyBox v1.27.1 is installed in /sbin and I did not install it.)))

And other installers show that BusyBox is installed in system/xbin if you install BusyBox through the Magisk repository.

What kind of magic I don’t know. :)

Here is the new binary for legacy modules.
[One (M7) Q&A, Help & Troubleshooting] anshulroy:
Hi,

Suddenly my HTC M7 went on loop restart. I tried to use Power and Vol Down button options but nothing worked. Getting message of S-On, Security-On etc. Tried to flash the Mobile using bootloader and all available stuffs on google, but did not work.

Please let me know, if there is a way to fix this problem. The only thing I can access is the Memory card that I can insert in other phone and do something.

desperately looking for a guidance on this.
[One (M7) Q&A, Help & Troubleshooting] lucyr03:
First you need to grab a fastboot getvar all to be able to help you, we need to know more about your device.

You need to boot in fastboot and run "fastboot getvar all" (you need htc drivers and adb installed).
[One (M7) Q&A, Help & Troubleshooting] Zyren2016:
You will need to flash the latest stock ROM you can find. That is what worked for me. If you don't know how, there are plenty of YouTube videos that explain how.

Download fastboot and start from there. (I don't haven't made enough posts to post links, so hopefully someone else can)

Also, you will need to use htc_flashboot (attached here) since the normal flashboot seems to have issues with HTC devices.

Try that and report back here.
[Magisk] liamolua:
Hi, I don't know if this is common knowledge but I have the latest version of Magisk Stable (16.0) running on Stock Android Oreo on a Nexus 6P.

I tried using Android Pay in store and it said "You can no longer use this card. Please lock your bootloader". I went and started SafteyNet check on the main page of MagiskManager and it came up with red crosses. I assume that means SafteyNet has patcher has patched itself to find MagiskHide, is that correct?

If so, is there a way around this? Does Beta version of MagiskManager fix this?
[Magisk] liamolua:
I think I might havr found the solution. Apparently Xposed Framework breaks SafteyNet. I've uninstalled it and now only getting green ticks in MagiskManager. Will try Google Pay latter and see if it works. I'll post here to let anyone else having this issue know ?.
[Android General] bc320:
I may be getting a micro-pc with no OS on it at all. I was thinking I would like to install Android on it as the operating system. I want to run Kodi to manage my media and then some emulators and Arcbrowser. I will also need to run something like file x-plore.

Is this possible or should I look at installing Linux first then Andriod?
[General Topics] jifop:
hey all, i am running WM6 on my HTC excaliber and i want to set up my email, basically i don't want the phone to download any mail from my pop3 server but i want to be able to send mail out marked as being from my pop3 account. how can i do this?
[Moto Z2 Force  Questions & Answers] Radick_11:
What's up! How are you? I am nuvo here if I miss one of your rules I ask you please let me know ... I have a problem with the motor z2 force .. xt1789-05 when flashing via ota to oreo android 8.0 lost base band again lower the NASH_AMX_NPX26.122-69_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

but I realized that the version I need is NPX26.122-69-74 and this NASH_AMX_NPX26.122-69_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml is

NPX26.122-69-14 how can I recover the bandbase? since it does not let me see the imei nor serves the wifi nor the bluetoth I already did flash by several commands NON-HLOS.bin and I do not find the indicated .. someone to help me ??
[Moto Z2 Force  Questions & Answers] j@cks:
Hi,

Have you tried flashing complete (no OTA) Oreo retail FW?? that may help you. Here in the forum, there is tread where you can download Oreo retail and try.

Good luck!

Regards

J@cks
[Moto Z2 Force  Questions & Answers] Radick_11:
how about first of all thanks for answering and install it and leave me baseband in the same way. I already downloaded several sw and leave the same without wifi any other idea? I restart it from the factory and return the baseband but it marks another baseband that is not giving me this NASH TMO OCX27.109 I found it here in the forums but checking another team of a friend the one I need is this m8998_20207.117.02.41R NRS
[Moto Z2 Force  Questions & Answers] j@cks:
Hi Radick_11

Go to this thread: https://xdaforums.com/z2-force/how-to/android-o-variants-t3746862

go to post #9, use the FW recomended and flash using that instructions, I have m8998_20207.117.02.41R NRS baseband, that is in the FW mentioned in that threat.

Ve a ese ling al post #9, usa el FW que te recomienda bajar, y flashealo con las intrucciones que ahi indica, yo tengo la base band m8998_20207.117.02.41R NRS que biene en ese firmware de ese post.

Saludos

J@cks
[Moto Z2 Force  Questions & Answers] Radick_11:
how can I thank you for replying that I'm desperate and I've done everything and I can not find the modem I need to download NASH_RETAIL_8.0.0_OPX27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip hoping it would work for me but now since I'm on android 8 I realize that now I need opx27.109-49 that is the compilation that Telcel Mexico manages