yashsingh1/xdaforums huggingface dataset:
[Magisk] TraderJack:
Hey all. Not sure if this was brought up in any form before. I have been using for quite a few months Magisk 81658d45 (27002). I believe this was a debug build(?).

I had been using some of the non-TJW Magisk (like Alpha) due to some of the other fixes that allowed some of my apps to run, but when 27002 was released, it seemed to have some merges that allowed my apps to function, so I went back to it as I prefer to be on official Magisk.

I just upgraded to 27004 and I notice that my Starbucks App no longer will log me in (it gives an "unable to log you in" error message). With 27002 and HMA it logs me in without an issue, but as soon as I go to 27004 it fails.

Does anyone know (or know where I can find) what the changes were in 27004 that might have led to this?
[Magisk] Matheus-TestUser1:
i try to flash, on a14 5g the magisk , and it always asks to format but it seems even formatting gives this error again A146MUBS2AWH7 ,already this one i got normal patecheando init boot A146MUBS2AWG6_ZTO
[Magisk] pndwal:
Not familiar with Starbucks detection, but had you taken 'hide the Magisk app' for 27002 and/or hidden Magisk App from Starbucks using HMA?... If you restored the app and hid again or simply restored, Magisk is probably no longer hidden in HMA lists... You generally need to re-add Magisk in HMA template after updating Magisk as random signing keys and package name will change...

Hope it helps. 👍 PW
[Magisk] pndwal:
This is not clear...

So what is the device?

Format what?... Where?... 🤔

Where is the error shown?

What's 'patecheando'!??

So another error code?... Other? 🤔 🤷 PW
[Magisk] wugga3:
Sometimes after an app update... I find that if I've now have an app that's not functioning correctly - I uninstall them reinstall that app and reconfigure it all goes well then I'm set... May or may not help you as I dont use that specific app you requested assistance with.
[Magisk] TraderJack:
I'm not sure it's Magisk now actually. I had done several tests which seemed to indicate it was the upgrade, but now I am getting wonky results on 2 similar phones. I'm pretty sure that Starbucks is doing something but I just can't narrow it down to what is blocking it from logging on. It is so intermittent and wonky.

For instance if I am able to get it to a state where it works: and by that I mean I can login, clear storage, and login again without issue, but then I try to login with my wife's account (I'm troubleshooting on both identical phones) it gives her the issue. So it can't possibly be the app alone if I can login with one account but not another. Then, on top of that the state that I had everything setup where it worked could be recreated several times, but then on say the 4th try it doesn't do it anymore. I'm not sure there is an answer - but if anyone else is struggling with the Starbucks app it seems to just be a PIA and I'm not sure the issues aren't also on their end. I suspect they might also be employing some sort of security mechanisms that is blocking/locking logins...but I just don't know.
[Magisk] Untitled_neo:
Sorry for the offtop, I consider buying a new phone. What device is easiest to root? I have Redmi Note 9 with Mediatek chipset and it was pain to root it and then update Magisk.
[Magisk] zgfg:
If staying with Xiaomi, choose Qualcomm models. But consider the troubles with unlocking - new models, with China ROMs will cost you to unlock
[Magisk] casouzaj:
Sony is very developers friendly. Very easy to root.
[Magisk] BillGoss:
Pixels are a breeze to root. And software support is brilliant.
[Magisk] rogers11:
Don't forget the hassle with RCS, Wallet, etc. I will not continue to support Google with device purchases because of this. And I've had almost every Google device, starting with a Nexus 4.
[Magisk] Nergal di Cuthah:
That's true for all brands, with pixel's you get guaranteed adb and fastboot thus @badabing2003's pixel flasher (which works with all adb fastboot devices) makes the hassle pretty painless.
[Magisk] badabing2003:
Although rare, until they get into serial mode and are deemed hard bricked due to lack of tools.

Those issues are not limited to just Google devices, they are any Android issues, and if you're going to tell me that iPhones are better than why are you in modding forums?
[Magisk] BillGoss:
Ah, yes. I've not really gotten into serious problems on my Pixel. I do miss not having something like the MSM Tool that's available for the OnePlus 8T which saved my phone countless times.

I'm a LOT more careful on my P8P for that reason.
[Magisk] rogers11:
Sure it's Android things, but it's Google playing the stupid RCS game, not Nokia or others. And it has nothing to do with iPhones at all.
[Magisk] J.Michael:
Google may have started it, but the manufacturers are all too happy to pile on. Which makes some manufacturers appear friendlier than others.

It has to do with iPhones in the sense that, since the Pope divided the world between Google and Apple, if you are anti-Google, then you are stuck with Apple.
[Magisk] HippoMan:
That's just a schism between mainstream religions. There are also a comparatively low number of people who reject the mainstream and congregate in small, independent churches.

As for me, I'm now starting to investigate Linux phones ... the ones which don't offer any Googlefrinchian libraries or services. Given the way that I use my device, I think that there's at least a chance that I could indeed get the features and capabilities that I want by going down this road.

If so ... then ...

Sayonara, Android!!!
[Magisk] sawdoctor:
There's plenty of manufacturers far worse. Samsung once disabled the camera if you just unlocked the bootloader and once knox is tripped s health s pay etc will never work again. Google could just patch the loop hole we're using for device integrity anytime they want but haven't
[Magisk] RandomPooka:
IIRC, all the rooted device issues with apps can frequently be boiled down to the device being compromised by an unknown source. Your bank doesn't know if YOU rooted or if you were infected with a rootkit/malware. That's not Google. Google may have had a hand in devising a way to certify integrity, but Google isn't to blame for financial institutions not wanting to have their software running on a compromised device.
[Magisk] Untitled_neo:
Thanks for the recommendations. I still didn't get it how Google phones can be the root friendly if Google policy is always to control everything and get money from nothing. They are opposite to freedom. I can not even imagine how much bloatware there are in modern Google devices
[Magisk] pndwal:
Have you tried to understand 'the RCS game?'...

It's a GSM Association's initiative for 'next generation cross platform messaging technology' proposed in 2007, but no players responded at all until Google finally announced it's intention to 'lead a charge into an RCS future' in early 2016.

This occurred soon after they had acquired Jibe Mobile for it's end-to-end encryption (E2EE) technology, and since then there's been RCS misadventures with Google partnering with Sprint to bring that carrier RCS only the have other big carriers AT&T, T-Mobile, and Verizon form their own 'Cross Carrier Messaging Initiative' (CCMI) which sought to create an RCS implementation that wouldn’t risk another iMessage-like service being created without them getting a piece of the pie... These collaborations ultimately fell apart including Spirit's involvement after that was acquired by T-Mobile, and Google was basically left leading the 'RCS charge' solo again...

By this time, Google had integrated RCS into its Google Messages app however, and support for RCS messaging referred to as "chat features" in December 2019 were followed by a wider global rollout throughout 2020 with end-to-end encryption (E2EE) protocols obtained from Jibe Mobile also being adopted for one-to-one RCS-based conversations from June 2021 and for all group chats by August 2023... Google also made their Jibe based E2EE available to carriers to help them quickly adopt RCS on their networks (unlike Apple’s proprietary iMessage E2EE protocol).

Slowly, with these Google advances/initiatives, many carriers and manufacturers have adopted Google Messages as the default messaging app, and even Samsung (with its own RCS-compatible Samsung Messages app) made Google Messages the default on new smartphones...

While compatible E2EE is an essential selling point, Apple finally made the surprise announcement that it will also adopt RCS by the end of 2024 subject to Google making changes to meet Apple's required standards for cross-platform security and anti-abuse protections, so the Google changes related to security and protocol compliance assurances almost certainly have everything 'to do with iPhones' and Apples take-up slated for iOS18 (around September) and already working in Beta releases...

These changes may be of more importance for proper cross-platform adoption of RCS than many modders here realise and, of course, such adoption was the whole goal of the GSMA originally... Nb. There have also recently been further developments in adopting a mutually acceptable E2EE standard, but it seems that all the issues are not yet fully resolved.

So while the RCS messaging protocol has been in the making for some 17 years already, it's clearly largely thanks to Google's efforts to develop and open up secure technologies to carriers that RCS has been made available to most Android users and, what's more, it's Google's willingness and efforts to adopt further security standards to get the likes of Apple on board etc that's gotten RCS to the verge of actually becoming the cross platform rich communication messaging technology that was first envisioned...

And it's about time. 🙂 PW
[Magisk] rogers11:
So they are doing everything they can to adapt their security standard to Apple's conditions in order to enforce a common protocol for messages. And that is more secure than Threema, Signal, etc. or is it just about metadata and chat control again?

I also believe that the ship has long since sailed, at least in Europe. Almost everyone uses WhatsApp, no matter what you think of it. SMS/MMS are dead.

That's just my personal opinion, of course. I wouldn't want my messages to go through Google's servers either. But that's a completely different story.
[Magisk] pndwal:
The Forbes article cited way back here:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89378516

with it's Reddit article link established that spammers are already abusing modded Android devices and made the connection between automated spamming (automation allowed by modding along with all the extended multimedia and more capabilities of RCS) and how Android mod abuse would/could affect all mobile users incl. iOS with RCS... So the likelihood is that Apple wants all RCS content to originate from "walled garden elements of [the] ecosystem" like their own.

So limitations on RCS per device are no real concern then! 😜 PW
[Magisk] HippoMan:
Yes. Modders avoiding a complicatedly problematic feature of Android and using non-Android software in its place is definitely a "plus" for them.
[Magisk] Wolfcity:
It's your device and I think I'm getting your point but shouldn't one be careful in every case when fumbling around with it? Again, I get your point, I had some Motorola devices and there is a very useful tool called LenovoMotoSmartAssistant and I used it not very often. Just when the Moto gets old...:cool:

In the end it's a matter of money, what are you willing to spend? I'm somewhere in the middle, Qualcomm driven Xiaomis. Good price-performance ratio and if you know what to do it's a good device for the money.

Just my 2 cents.

Yes, I never heard about RCS here in Europe before the play integrity stuff appeared. Here Whatsapp or Telegram are the apps to go with. One problem less for me....;)

But the US is a big market so I think it will be important also in the future.

5000​
[Magisk] rodken:
[Off-topic] You're absolutely right about the key role Google has played in pushing RCS forward.

While Google has been a major advocate for RCS, especially for Android users. They've developed features and integrated RCS into their messaging app, Google Messages.

Moreover, a big hurdle for RCS adoption is getting different platforms like iMessage to work seamlessly. Google's willingness to adopt stronger security measures is a big step towards making RCS more attractive and potentially attracting holdouts.

Overall, Google's efforts have been instrumental in getting RCS to where it is today. With continued focus on security and collaboration, RCS has the potential to become the universal messaging standard, but I'm not holding my breath.
[Magisk] HippoMan:
... which worries me, because of the problems that have been encountered so far in using RCS on many modded phones. I'm hoping and praying that a totally reliable and universal way of enabling RCS on all modded phones will come into existence.
[Magisk] rodken:
Makes me wonder if someone already has developed a method without full disclosure.
[Magisk] Lughnasadh:
New Canary Release:

Magisk (7b81e2d) (27005)​

[Zygisk] Update internal JNI hooking implementation

[MagiskInit] Update preinit partition detection

Diffs to v27.0​

[General] Support 16k page size

[General] Add support for RISC-V

[General] Use a minimal libc to build static executables (magiskinit and magiskboot) for smaller sizes

[Core] Remove unnecessary mirror for magic mount

[MagiskInit] Rewrite 2SI logic for injecting magiskinit as init

[MagiskPolicy] Preserve sepolicy config flag after patching

[MagiskPolicy] Optimize patching rules to reduce the amount of new rules being injected

[DenyList] Support enforcing denylist when Zygisk is disabled

[Resetprop] Improve implementation to workaround several property modification detections

[Resetprop] Update to properly work with property overlays

[App] Major internal code refactoring

[App] Support patching Samsung firmware with images larger than 8GiB

[App] Use user-initiated job instead of foreground services on Android 14

[App] Support Android 13+ built-in per-app language preferences

[MagiskBoot] Support spliting kernel images without decompression
[Magisk] HippoMan:
I updated to this latest TJW Magisk 27005 on my fossilized stone-age Pixel 5 running antediluvian A11 and TJW Magisk 27004. Everything worked well.

Here are the steps I followed:

(1) I launched my hidden 27004 version of Magisk.

(2) I un-hid Magisk.

(3) I exited from Magisk and re-launched Magisk, just in case.

(4) I selected "Update" in the "App" section of the Magisk home screen where 27005 was listed. The app indeed got updated properly.

(5) I exited from Magisk and re-launched Magisk, just in case.

(6) Version 27005 then indeed showed in the "App" section of the Magisk home screen. I then selected "Install" in the "Magisk" section of the Magisk home screen where 27005 was listed.

(7) In the dialog that popped up, I selected "Direct Install".

(8) After the installation tasks were shown as being complete, I selected "Reboot", and my device indeed rebooted.

(9) After reboot completed, I launched Magisk, and it indeed showed 27005 both in the "App" and "Magisk" sections of the Magisk home screen.

(10 I exited Magisk and tested Magisk functionality, and everything worked properly.

(11) I then re-launched Magisk and re-hid it.

(12) I exited from Magisk and rebooted again, just in case.

(13) After reboot completed, I tested the now hidden Magisk, and everything continued to work properly.

Some of my re-launchings of Magisk and one of the reboots might not actually have been necessary. But I did those things just out of extra caution.

So ...

Excelsior!
[Magisk] pndwal:
Wow: Update README...

Debug build link disappears from Magisk main page... Turns up in Releases link in Assets... (Wonder if these will remain there, especially as current Canary and Debug builds are not yet found in https://github.com/topjohnwu/magisk-files/tree/canary !) 👀
[Magisk] jcrompton:
Someone had asked about this working on a 7.1 ROM ( I have been using on SIX ROM - 7.0 .... on my Nexus6)

Today I flashed cDroid latest , today's, release

I posted in that thread results.

Here is what gave success for that ROM:

Also just as a report. I flashed as instructed.

Then installed SuperSU and did full unroot.

Went to recovery and mounted system and the with file manager deleted system/bin and system/xbin su files (not sure why SuperSU unroot didn't do it)

Flashed Magisk 9

Flashed the magisk phh superuser 266 module

Booted

Installed phh superuser app

Confirmed root

Installed Magisk 2.5 app

Opened, gave root permission, then opened settings and checked Hide Magisk

Rebooted - got blue SafetyNet

Rebooted again - got green / pass SafetyNet

PoGo as well
[Magisk] dark_knight_95:
What ROM are u on and how to get it to work .could u briefly tell. I have d855 on nougat ROM.
[Magisk] hokiealumnus:
I'm on crDroid right now. You have to enable root, use the magisk app to install v9, boot into recovery, bump, rename su to s_u in both system/bin and system/xbin, flash phh superuser magisk version, boot up, enable magisk hide, reboot, profit.
[Magisk] dark_knight_95:
What do u mean by reboot to recovery,bump. Do I have to flash mrbump.zip. sorry for noobish question.
[Magisk] hokiealumnus:
Yes. You will need to go into recovery manually after installing magisk with the app, because the boot IMG will no longer be bumped. When it tries to restart, it will hang with a blinking LED. Pull battery and boot into recovery to bump it.

If you don't know how to recover from this type of thing, you may not want to try. There is a risk of bricking, however small, as there is with all of the things we do.
[Magisk] yochananmarqos:
IIRC, the D855 bootloader can be unlocked without bumping it like the carrier models.

If you didn't need to bump your bootloader to root to begin with, you certainly don't now.
[Magisk] 3mutts:
Hi, Im having an issue installing magisk v9 on my Samsung Galaxy Tab Pro 10.1 (its running CyanogenMod 13). For some reason, if I try to flash it I get error 1 (Can not extract ZIP) in TWRP (it is version 3 btw). It didnt do this on my Nexus 6 running 7.0 and I tried downloading the file multiple times to makes sure I didn't get unlucky with a corrupt file. I'm lost and if anyone could help it would be great.
[Magisk] Portgas D. Ace:
You can simply boot into recovery and flash the latest Magisk.zip. No wipe is required as the system partition isn't touched at all. If you aren't sure, make a backup before flashing.
[Magisk] devilloki:
v9'issue

Boot partition size still too small...

my device is huawei honor7
[Magisk] stifuco:
Samsung s6 support

Hi everybody! I'll explain the situation: I have a galaxy s6, have rooted with the unikernel (which I think is the only way to root it), and then installed TWRP and xposed. Now I would like to install magisk.

The first question is... is it feasible?

If I understood well, I should first unroot it. But if I go to superuser and tap "unroot", and then restart my phone, it comes back with root again.

Can someone please tell me the steps I have to do? Thank you in advance.
[Magisk] Didgeridoohan:
If it is a problem you've encountered before (sounds like it), have you provided any details to help solve it? What you've tried, recovery log, logcat, your boot image (as described in the official anouncement thread) and so on...
[Magisk] devilloki:
how update file,in android client?
[Magisk] Didgeridoohan:
I'm sorry, but I have no idea what you mean.
[Magisk] cl0g:
Cant find any information about Magisk working on latest November security patch causing bootloops with modules on official xposed.

Somebody has more information?
[Magisk] SDMU:
Using the xda app , you can upload the log in a .zip or a .txt format
[Magisk] ss4rob:
I did a complete uninstall using the uninstaller and removing all magisk directories and files, and reinstalled v9 clean, and I'm back to passing SafetyNet. Whew, I was planning on paying for Pokémon Sun/Moon with Android Pay, heh. Thanks devs!
[Magisk] egonet:
SuperSU 2.78SR3 -> Magisk v9 -> Flashing ZIPs using FF is impossible!

Hello

I'm new here :)

I just flashed SuperSU 2.78SR3 in my new device (S7 edge G935F), then Magisk v9 (using FlashFire 0.53). Magisk worked great but I have one major problem - flashing another ZIP using FF is impossible - only black screen for 30 second, then reboot. No changes at all..

100% stock firmware, only boot.img patched by SuperSU, then by Magisk...

It is not FF problem, because after removing Magisk FlashFire started working again as it should :confused:

IMHO it is real problem for "systemless" users (including me) who do not like to use custom recovery (also - FlashFire is great tool because it is the only tool I know with access to /data during flash process in case of encrypted /data partition).
[Magisk] Didgeridoohan:
It's not Magisk that's the problem, it's Xposed. The november patch breaks Xposed and it's gonna take a while for Rovo89 to fix... If you really need Xposed you have to roll back to an earlier security patch (or find a rom with a fix).

Magisk works like a charm...
[Magisk] dimm0k:
curious, are you able to flash Magisk modules in Magisk Manager? wondering if this is a similar issue to mine since I can't flash either...
[Magisk] TopperBG:
Huawei P8 (GRA-L09 C432B370) flashing by TWRP latest Magisk v9 lead me to broken boot. Start to fastboot screen with two erros (no boot and no somethnig else)

Restore original boot.img from ROM B370 with fastboot restore boot system.

Latest installed Magisk was v8 + Phh SuperUser.

What can couses the problem ?

Edit: BTW v8 reflashed works just fine ?
[Magisk] devilloki:
upload recovery.log

pls help me .ths.

---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------

ths.

i had uploaded recovery.log from PC.

---------- Post added at 10:33 AM ---------- Previous post was at 10:31 AM ----------

boot partition is too small?

my honor 7 show me that.
[Magisk] Eddie_Brock:
Has there been any progress in getting magisk to work fully with FlashFire? I'd really like to go back to magisk and phh, however FF is essential for me.
[Magisk] TopperBG:
Here with v8, phh and SeperSU modules installed app like Flashify works flawlessly. Give it a try.

Изпратено от моят HUAWEI GRA-L09 с помощта на Tapatalk
[Magisk] jimbomodder:
V1 uninstaller has updater error in recover, how can I manually remove magisk please
[Magisk] Artim_96:
I doubt it will ever run with FlashFire. At least not as long as Chainfire doesn't allow it. And he has his SuperSU as dependency, because he knows that everything necessary is in it. And it makes debugging way easier.

But even with SuperSU FlashFire won't run for me. It will show me the black screen but nothing else even if I wait for minutes. I don't know if it got better because I think the last time I tried was when Magisk first really supported SuperSU... Which was v6 or so. Maybe it works better now

---------- Post added at 01:59 AM ---------- Previous post was at 01:57 AM ----------

Remove Magisk.img from /data and restore your stock boot.img. I don't know if there would be any leftovers, but that's basically it
[Magisk] jimbomodder:
Yeah restored stock and then boeffla and magisk still present
[Magisk] Artim_96:
Well, if you really flashed your stock boot.img there is no easy Magisk still can be running. So you must have done something wrong summer point
[Magisk] jimbomodder:
Restored the stock from an untouched backup
[Magisk] Artim_96:
Well, then use the backed up one in /data. Of it went right Magisk can't be running anymore since it needs to make changes to the boot.img to run
[Magisk] jimbomodder:
That's after deleting from data
[Magisk] jimbomodder:
Well doing a search I found all magisk and removed and that worked
[Magisk] Eddie_Brock:
No, that's exactly the problem. With magisk installed, FF loads fine, however just goes to a black screen as you described when you attempt to flash.

I've tried with both SuperSU and PHH, with the same result. It's definitely magisk, and chainfire has basically said to ask here.