yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Watch 4] frea:
It really is a shame what poor quality samsung dares to ship out to customers!

But what makes me even more angry are all the fanboys that defend samsung no matter what and always try to blame users for their hardware and software issues even though it´s clear that it´s just a faulty/unfinished product...

In the other thread there really have been people blaming the user for their burn-in issues for "setting the brightness wrong"... On a finished device there should never be a user setting that could damage a device permanently....
[Samsung Galaxy Watch 4] sesnut:
like 5 people got a bad watch while everyone elses is fine dood
[Samsung Galaxy Watch 4] frea:
So you would really dare to set your watch to max brightness with AOD on for a week?
[Samsung Galaxy Watch 4] Denska:
In my case it was auto brightness and screen burn in for about one day
[Samsung Galaxy Watch 4] y2kbadbug:
Yeah. I love how these guys are trying to blame us. My watch was set to the default display settings with AOD on. My GW and GW3 had the same settings and never had this problem. This is my 4th smart watch, first being that LG one that came out in like 2016
[Samsung Galaxy Watch 4] y2kbadbug:
Samsung just sent me an email saying they are shipping my device back unrepaired. I'm trying to find out what the hell is going on.

EDIT: Samsung sent that email automated because they determined to just send me a brand new replacement.
[Samsung Galaxy Watch 4] y2kbadbug:
I have a status update. Samsung will not replace the watch, they are only offering me a refund. I'm livid at this.
[Samsung Galaxy Watch 4] kodiak799:
Ummm, so you take the refund and buy a new watch. What's the difference?
[Samsung Galaxy Watch 4] emreLP61:
My watchface of my gw4 classic literally burn in in 5 hours with AOD and automatic brightness. I also got called from 1000000

But I contacted Samsung and they told that I can send the watch back and receive a brand new one
[Samsung Galaxy Core.] jayabandara:
After I installed CM 11 ROM; I wanted to install stock apps. But I couldn't. Then I downloaded SM-G318H firmware file and extracted it's apks and install them. But they didn't installed. When I searched on web, I couldn't find answer either. So I tried to deodex and install it.

But also couldn't. So can anyone tell me what to do (I wanted to install stock apps; Including TouchWiz and other important apps)

(The thing is I want to make firmware file like an original KitKat firmware)
[Samsung Galaxy S8+ Questions & Answers] Elohim-Brown:
Hello, please my phone says SM-G955FXXU1AQH3 and it's android 7.0, and it's region BTU, that is United Kingdom. So please do I just need to download any latest firmware as in 9 Pie ROM firmwares of any BTU version?

Because I have tried to fine any update that match it as in something like " SM-G955F8AQH8 or something since binary 8 is the latest?.Because I have tried to fine any update that match it as in something like " SM-G955F8AQH8 or something since binary 8 is the latest?.
[Android Q&A, Help & Troubleshooting] gfrank227:
Hi all, I noticed today that safetynet is suddenly failing. I don't think I made any changes to the system today that would have an affect on SafetyNet. I was playing around yesterday with an exposed module and while doing so, was switching between xposed frameworks to compare them (Edxposed was NOT one of them, because that always trips SN for me).

So I am wondering...did Google make any recent changes to SN that would affect the CTS profile passing?

Is it possible that the experimenting with different xposed frameworks changed the system in such a way that the only way to get SN back is to start from scratch?

Thanks for any insights you might have.
[Android Q&A, Help & Troubleshooting] Deleted member 1890170:
Yes, SafetyNet API got changed: it no longer looks for a phone's CTS profile locally stored on phone but externally stored on Google server - uploaded there by phone's manufacturer.
[Android Q&A, Help & Troubleshooting] Deleted member 1890170:
The cat-and-mouse game has ended. :)
[Android Q&A, Help & Troubleshooting] devaponnadsm:
Where did you get this info from?

Pls send link
[Android Q&A, Help & Troubleshooting] Deleted member 1890170:
SafetyNet Attestation API | App quality | Android Developers

The SafetyNet Attestation API provides services for determining whether a device running your app satisfies Android compatibility tests.

developer.android.com
[Android Q&A, Help & Troubleshooting] gfrank227:
People have said that before.....i said just two days ago that if google suddenly finds a way to bypass magiskhide for good, then i'd be inclined to blame topjohnwu.

Is there absolutely no way around this?
[Android Q&A, Help & Troubleshooting] Deleted member 1890170:
Magisk no longer can't prevent this, because it can't intercept this server-side query.

Take note that the developer of Magisk has already adnitted that!

MagiskHide became obsolete.
[Android Q&A, Help & Troubleshooting] gfrank227:
And all this happened yesterday?
[Android Q&A, Help & Troubleshooting] Deleted member 1890170:
Depends on when Google Play Services Framework got updated on your phone: SafetyNet is integral part of Google Play Services Framework.
[Android Q&A, Help & Troubleshooting] gfrank227:
OK. I set up the XPrivacyLua with the assistance of this youtube video.

I only watched the video once and set it up using the google play store app. but after reading your response, I set it up using the "google play services" process, and now my phone passes safetynet again.

Hope this helps someone. :-)
[Android Q&A, Help & Troubleshooting] p2pteam:
Its work for me is poco x3 pro , thanks
[Android Q&A, Help & Troubleshooting] jaccydan:
Hi @gfrank227 et all.

My Safetynet was working due to the instructions in the video you posted above. This could be a classic case of 'If it ain't broke don't try and fix it'.

I got a Magisk update message, and 'perhaps stupidly' I installed it in Magisk. I then lost my 'Check SafetyNet' option in the main screen of Magisk, and in Magisk Settings I lost the 'MagiskHide' option.

I also got a message to update LSposed, so I downloaded the zip, and decided to re-follow the youtube video above again this time installing the new LSposed zip.

Nothing's changed, I still have those missing options in Magisk, and also now in Google Play Store my device is now showing as 'Not Certified'.

SafetyNet Test App states 'Failed'.

However, LSposed & XPrivacyLua are actually set up correctly as per the youtube video.

Not sure how to proceed to fix this. :unsure: Could really do with my Google Pay back.
[Android Q&A, Help & Troubleshooting] gfrank227:
You must have installed the latest magisk canary. Have you tried the magisk module universal safety net fix?
[Android Q&A, Help & Troubleshooting] jaccydan:
Thanks for the reply, sorry it took so long to get back to you - (for some reason I didn't get an email notification, but never mind).

Anyway, yes I was looking at those very 2 things. I actually went into Magisk and 'installed from storage' the latest safety net fix, but nothing's changed.

With Canary, I have gone into the Magisk App tab in settings, and clicked on 'Update Channel', then clicked on Canary, but nothing happens. What am I doing wrong here?

I think this Canary build thing could be the answer.

I am also unsure if I need to download a latest canary apk and install it via Odin or something. Not sure how to proceed.

Thanks in advance.

Here's my Magisk Home Screen:

View attachment 5441241

Some additional information:

View attachment 5441249
[Android Q&A, Help & Troubleshooting] gfrank227:
Also install magiskhide props config. they added some props to the default module that magisk is removing.

If this also doesn't work, then go back to 23.0 and don't update until someone fully replaces magiskhide with an working module.
[Android Q&A, Help & Troubleshooting] jaccydan:
This might sound stupid but when I go into modules there seems to be no way now of searching for modules online through Magisk - it only seems to be an option to install from storage, so I can see if I need to update magiskhide props config.

Btw, I already have a version of magiskhide props config activated, so I probably don't need to do anything with that.

This page states ( I think) that yesterday this v.23.0 build of Magisk has been updated with a new Canary build:

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

I think therefore I need to install this Magisk version and then activate Canary in it.

I'm a newbie, so if you could advise me which method to install this, it would be much appreciated. Am i going back to Twrp or Odin or can I do it more easily via the Magisk app? I came across this page explaining various installation methods, but I'm not sure which one to follow in my circumstance:

Installation

The Magic Mask for Android

topjohnwu.github.io

Thanks.
[Android Q&A, Help & Troubleshooting] gfrank227:
Yeah, so it's not stupid. You're right. Topjohnwu, the developer of magisk recently joined the Google security team. As a result, magisk development was put on hold pending approval. Due to conflicts of interest, it was determined that he would not be creating software intended to get around Google's security checks. This is the reason why Magiskhide is gone in the newest canary build.

The other change he made was to remove the built-in modules. You will have to therefore download the zip file for magiskhide props config from github. The props in magiskhide props config were only added in the past couple of months. so you should make sure you are downloading the latest version, or at least the one right before the latest.

If you have both modules I reference and are still failing, then this is because these modules were not intended to fully replace magiskhide. I am confident that eventually they will be able to fully replace it; but until then, you should simply uninstall the magisk manager and then install the apk from the github site that you reference above. That's the correct latest stable version. Then, forget about the canary version.

After the canary version goes as a full update, I recommend that you don't update magisk right away but wait until there's a suitable replacement module that works.

Additionally, if you patched boot.img with the latest canary version, simply repatch using the magisk app after replacing the manager. In theory, you should then have magiskhide back and pass safety-net.

Eventually, of course, google will find a way to bypass this so eventually, we will certainly need to hope for a fix. But this is the best solution for the short term.
[Android Q&A, Help & Troubleshooting] gfrank227:
If you look at the change-log from the three or four most recent releases, you'll be able to see if magiskhide props config you are running has the magiskhide props.

GitHub - Magisk-Modules-Repo/MagiskHidePropsConf: This tool is now dead...

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com
[Android Q&A, Help & Troubleshooting] jaccydan:
Thanks for that info @gfrank227 that is very helpful.

When you said the above (see quote), do I need to rename that Magisk .apk to .img before using Magisk Install to 'Select and Patch a File' from out of my downloads folder?

It's the 2nd part of your reply that I'm stuck on:

"Additionally, if you patched boot.img with the latest canary version, simply repatch using the magisk app after replacing the manager."

Can you run me through this process, I'm not familiar with patching images?
[Android Q&A, Help & Troubleshooting] jaccydan:
I'm likely to follow this instruction.

Once I've used the Magisk app to uninstall the current Magisk, should I use TWRP to install the Magisk apk as you advised?

I've noticed when I click on 'Uninstall Magisk' a warning pops up telling me root will be removed, etc. I'm a bit concerned about that.

Thanks.
[Android Q&A, Help & Troubleshooting] gfrank227:
You should be able to simply replace the magisk manager app with the older version. After the older version is installed you can repatch the boot.img from within the magisk app without a need for twrp.
[Android Q&A, Help & Troubleshooting] jaccydan:
Ok, so how do I do this?

I saw this, but it confused me:

​

Patching Images​

If your device has boot ramdisk, you need a copy of the boot.img

If your device does NOT have boot ramdisk, you need a copy of the recovery.img.

You should be able to extract the file you need from official firmware packages or your custom ROM zip (if using one). If you are still having trouble, go to XDA-Developers and look for resources, guides, discussions, or ask for help in your device’s forum.

Copy the boot/recovery image to your device

Press the Install button in the Magisk card

If you are patching a recovery image, make sure “Recovery Mode” is checked in options.

In most cases it should already be automatically checked.

Choose “Select and Patch a File” in method, and select the stock boot/recovery image

The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.

Copy the patched image to your PC with ADB:

adb pull /sdcard/Download/magisk_patched_[random_strings].img

Flash the patched boot/recovery image to your device.

For most devices, reboot into fastboot mode and flash with command:

fastboot flash boot /path/to/magisk_patched.img or

fastboot flash recovery /path/to/magisk_patched.img if flashing a recovery image

Reboot and voila!

Are you saying there's a simpler way? If so, how? I've never used ADB btw.

What I'd simply like to do is press 'Install' on the Magisk card and have the aforementioned Magisk apk renamed to Magisk.img, and just install/patch it simply like that. Will that work?

Thanks.
[Android Q&A, Help & Troubleshooting] gfrank227:
Install the magisk 23.0 apk. Then simply press install from within the magisk app. See attached. The instructions for the initial rooting of the phone and patching the ramdisk shouldn't be necessary on a device that is already rooted.
[Android Q&A, Help & Troubleshooting] jaccydan:
I just followed this..

..to try to downgrade to v.23, but it seems that it hasn't fully worked and remnants that new version has remained.

Safetynet still failing, and SafetyNet button still not present in Magisk.
[Android Q&A, Help & Troubleshooting] gfrank227:
According to your screenshot you are still using the canary version.
[Android Q&A, Help & Troubleshooting] jaccydan:
The problem seems to be lying in that when I try to install the 'old' magisk apk, the message is 'app not installed'. It only wants to install that latest version that I'm trying to get rid of.
[Android Q&A, Help & Troubleshooting] jaccydan:
I thought that Canary had gone and I was on a custom channel
[Android Q&A, Help & Troubleshooting] gfrank227:
First uninstall the currently installed magisk manager app the same way you uninstall any app. then when you install the old apk it should work.
[Android Q&A, Help & Troubleshooting] jaccydan:
If I click on the Uninstall Magisk button this screen pops up. Can I proceed if I choose 'Restore Images'. Then perhaps the apk install will work?
[Android Q&A, Help & Troubleshooting] gfrank227:
No, don't do that. that uninstalls root completely. I mean, go into your device settings and uninstall the magisk manager app only. The same way you'd uninstall any other app.
[Android Q&A, Help & Troubleshooting] jaccydan:
Ok will try.
[Android Q&A, Help & Troubleshooting] borisSweden:
You can still spoof Safety Net on Pie but later Android version you need, Gapps, GPlayServices, Universal Safety Net fix, manual fingerprinting change with MagiskHideprop, no MicroG, Riru, Riru Hide and of course Magisk. for now it fixes the server side Safety Net test.

On the other hand, JohnW is actively trying to make Android stop not security based apps stop using Safety Net. Pokemon and McDonalds shouldnt use that API.
[Android Q&A, Help & Troubleshooting] jaccydan:
Ok, so if I click on Install it gives me 2 options: 1. Select and Patch a File & 2. Direct Install (Recommended)

Don't know which one to choose.

Also, Update channel has defaulted to Canary. Do I choose 'Stable' or something else?

I didn't do that last thing and I'm still rooted.

re. ⬇
[Android Q&A, Help & Troubleshooting] gfrank227:
i disagree with the entire concept of SafetyNet. If I can log into a banking website on my Windows PC from an administrator account, then I should be able to log into the same system from my phone as an administrator. I don't blame John for taking a job at google, but if google suddenly succeeds in causing every single rooted device to permanently fail safetynet, then I will most definitely blame him.

Can you be more specific regarding the steps to pass safetynet with the latest canary version as you described? Thanks.
[Android Q&A, Help & Troubleshooting] jaccydan:
I want to get rid of that d7e7df3b (23010)
[Android Q&A, Help & Troubleshooting] gfrank227:
after you have magisk manager 23.0 back on, and it says 23.0 under manager, you should "install magisk" in the top box from my screenshot above. that should get rid of the 23010 code and go back to 23001.
[Android Q&A, Help & Troubleshooting] jaccydan:
I did that and I've unfortunately lost root. I might need to recap over my previous posts to see how to get it back. Maybe that is the only way to revert back to old Magisk?

The weird thing is that as soon as i clicked on install, and chose recommended install then rebooted, the phone did a system update before i lost root.
[Android Q&A, Help & Troubleshooting] jaccydan:
@gfrank227 I am stuck trying to re-root my device. I was wondering if you know a way for me to do this. I have tried flashing magisk.zip in TWRP and also flashing safetynet fix and magiskhide props config.

I need to find a way where I don't end up losing all the data on my phone.
[Android Q&A, Help & Troubleshooting] gfrank227:
That is strange. If you lost root, it's likely because of the system update, not because of a magisk installation.

I just tried to upgrade to the Canary version. I was able to continue to pass safetynet - UNTIL I activated Zygisk to use the new app hiding feature. Then I failed safety net. This is actually an exception - I would expect that most people would fail. On newer phones, with hardware attestation, I'm pretty sure that magiskhide is still necessary.

I'm not sure you should listen to me because I may have messed you up. But you can try the following. I'm not 100% sure if it'll work.

enable developer settings and enable usb debugging. Connect the phone to the computer. Download minimal adb from here. run the following commands:

adb devices (this checks to see that the device is properly connected for adb debugging)

adb reboot fastboot (this reboots the device in fastboot mode)

fastboot flash --slot a boot {path and filename of magiskpatched boot.img file)

i don't know if this will work. but it might be worth a try to specify the specific slot you want it reinstalled to.
[Android Q&A, Help & Troubleshooting] borisSweden:
I don't have that problem as our bank,ID and payment app doesn't care about ROOT. Its all encryption and passwords. I don't remember where I got the tutorial but it'd either on XDA or Github. I use MicroG so it wouldn't work for me.
[Android Q&A, Help & Troubleshooting] jaccydan:
Hi @gfrank227. Yes I was just about to do an adb fastboot installation of say, Magisk v.22, but I've never used adb before just TWRP, so am doing a bit of reading.

I have tried to simply flash Magisk.zip via TWRP, but I am not getting any resulting app on my phone to complete the installation once I reboot. Then I have tried installing the apk first then flashing the zip, but nothing is showing in the app.

So I assume I need to use the boot.img adb method.

The problem I have is that I don't know where to obtain the "boot.img" from??

I will be working from either of these 2 methods:

re. 'Patching Images'

Installation

The Magic Mask for Android

topjohnwu.github.io

OR

'Method 2'

Root Android Phone with ADB, Magisk & TWRP

Here are 2 different methods to root your Android phone or tablet using ADB and Fastboot commands, Magisk and install TWRP Recovery.

technastic.com

Which do you think would be the best guide for me to follow?

Thanks.

Thank you for the adb tools link, I was wondering where I could get something like that from. :)

Thanks, appreciated.
[Android Q&A, Help & Troubleshooting] gfrank227:
Are these specific to your phone model?

You get the boot.img from a stock rom image. If you have a Motorola device I can give you specific instructions. But I'm not sure about other devices.
[Android Q&A, Help & Troubleshooting] jaccydan:
Yes I thought the boot.img might be a phone specific thing. I have a Samsung S20 Ultra 5G SM-G9880 Hong Kong Variant, and I've done a search but not finding anything. I will have to look harder.
[Android Q&A, Help & Troubleshooting] monsiu:
lol you saw how he rant when everyone called him a traitor and threatened to side with google and actively f everyone using "hide"
[Android Q&A, Help & Troubleshooting] gfrank227:
yes, I saw that. Honestly. He has to make a living, so I can't blame him for taking the job. But he should have passed the project along to someone who could do it properly.

Can you recommend a forked magisk version that maintains hide but is going to be actively maintained an developed?
[Android Q&A, Help & Troubleshooting] jaccydan:
Well I downloaded the stock files compatible to my device, and I got a load of Odin type files?? No file labelled boot.img.

Does this assume I have to use Odin? Won't that wipe all my phone data?

Wouldn't know how to proceed with this in terms of what I want to do with rooting with Magisk..although i have used Odin before so that in itself wouldn't be an issue if it can safely be done that way. Which one of these files to use, who knows??

This all seems to be going off on a tangent from just using adb.

UPDATE: Found this ~

https://xdaforums.com/t/get-boot-img-from-stock-samsung-fw.1929222/post-32597420

"Rename file.tar.md5 to file.tar and unzip" (in order to get boot.img).

I'm assuming that would be the HOME.tar.md5??
[Android Q&A, Help & Troubleshooting] monsiu:
his true origin story......hahaha but yea i mean if i was as smart as the guy i would definately work for a company as google. it honestly can not get better than that.

He should have just step down from the project and handed it to someone else with whom he worked on the project with cause now he works for security at google and this magisk hide actively messes with his line of work and he is frustrated as f as google has been on his back for it.

He should just have hung up the towel the moment he went for his first day at work.

cant you just uninstall and revert to the previous version....the man hinted on a way to bypass the safetynet and even said something about denylist which some newly made modules can be used to "hide"

But i do not think development has begun....and its just confusing on why he is developing for magisk but still removing things
[Android Q&A, Help & Troubleshooting] jaccydan:
UPDATE:

Downloaded LZ4 program and used the context menu to 'decode' i.e. unzip the boot.img.lz4.

It appears I have produced a boot.img file. I have highlighted where it says it's 0 KB tho. I have other unrelated iso files and they don't show as 0 KB! I did a search and this can be an issue, but don't know how to fix it if it needs fixing.

The same 0 KB thing happens if I try opening boot.img.lz4 with LZ4.exe using the context menu.

UPDATE:

Just clicked on Install in Magisk and then 'Select and Patch a File', then selected that boot.img and it came back as 'Installation Failed, Invalid Input File'. Most likely because it has 0 KB's.

Got to try to find a way to unzip the boot.img.lz4 file correctly. Was looking at a Git lz4 program instead to unzip but haven't yet worked out the cmd commands for it. As soon as I get a valid boot.img file I think I can root the phone again.