yashsingh1/xdaforums huggingface dataset:
[Magisk] ipdev:
I bork my 6T every now and then. 🙃

Most of the time I can get back up and running with my backup files.

It would be a lot easier if OnePlus supported Fastboot. 🤬

When I go too far in breaking it.

I boot into Windows, use the msm tool to flash it back to stock.

It always takes me a minute to figure out how to connect.​

- Start the msm tool.​

- Put the device in edl mode.​

- Then connect it to the computer.​

You will probably have better help in one of the OnePlus 7 Pro threads. ;)

I miss read your post originally but, one of these threads might help to get back on track.

[GUIDE] How to convert TMobile OP7 to International. - xdaThread - Link

[GUIDE] T-Mobile One Plus 7 Pro MSM Tool (revert back to TMO stock) - xdaThread - Link

msm download tool - xdaTags - Link

Good luck. 👍

Cheers. :cowboy:

PS.

The move away from fastboot support is what turned me off of OnePlus.

Love my 5T and I like my 6T but, I doubt I will decide to buy a newer OnePlus device any time soon. :(
[Magisk] pndwal:
Actually, I think he's joking... He only keeps /warning himself after his own posts in English. 😜 ...

Don't know who added copying / forwarding restriction (like in LSPosed group)... may have been to curb habitual forwarding of identical messages in consecutive posts (Chinese 'roasting' practice?)... Could have been vvb2060 too!

Yup, can't in Telegram app, but Nekogram works fine as mentioned...

Side benefit (for me): I couldn't read LSPosed and other groups Chinese posts before this due to same policy... Now I know about Nekogram I can catch up on development... If I can find time... 😝 PW
[Magisk] krosselegance:
So after going through this page, my phone now only have 8GB instead of 32GB. I don't know how this happened, but I'm so confused. Also, I installed Magisk App again and no Additional Setup dialogue comes up.

I'm using a Galaxy A10s (SM-107M ZTO), and usedSamFirm 0.5.0 to download the FirmWare. Can someone help me? Did I lost my storage forever?

Edit: I was dumb, forgot the factory reset lol. Now it's fine.
[Magisk] koala86:
Thank you for your response, I have been able to connect it to the MSM tool; however, this is what is showing up. Could it be that I am using the wrong version of the MSM tool because from what I have watched/read there are various MSM tools such as guacamole and enchilada...
[Magisk] koala86:
Thank you for your response, I have been able to connect it to the MSM tool; however, this is what is showing up. Could it be that I am using the wrong version of the MSM tool because from what I have watched/read there are various MSM tools such as guacamole and enchilada.

I believe that this is the ROM, which I have used:

OnePlus7ProOxygen_21.O.20_OTA_020_all_1909172051_db7a3f61.zip

Sorry for the noob questions/being annoying, I am new to this...
[Magisk] midgo12:
I have had luck flashing back to Android 10 and then updating to Android 11 via OTA from there.

I used the files in this link.

https://xdaforums.com/t/op7pro-late...0-gm21ba-collection-of-unbrick-tools.3956595/
[Magisk] m0han:
i did direct install with -2 and -3. had issues with -3. showed zygisk 'no' for a long time. later became 'yes' (maybe after a reboot; don't remember). also, both sims had network icons missing and media in whatsapp chats were blurred. but, all good after a couple of reboots. strange!
[Magisk] m0han:
@zgfg, i notice you're running ofox recovery [on your surya(?)]. please ignore if not surya.

Spoiler content hidden.
[Magisk] m0han:
is this where you downloaded Nekogram from? any special configuring needed?
[Magisk] Stephen589:
I'm Already Using It. It's Great
[Magisk] pndwal:
Sounds strange... Quick search indicated device in question supports fastboot flashing...

https://www.hardreset.info/devices/oneplus/oneplus-7-pro/fastboot-mode/

https://droidrecovery.com/oneplus-7-pro-recovery-mode/

Seems 6 / 6T does too:

https://www.thecustomdroid.com/boot-oneplus-6t-bootloader-recovery-mode/

Are you sure they've done this? - EDL is basically for hardbrick recovery AIUI... Why allow EDL but not fastboot???

Some OEMs have restricted EDL however since penetration testing proved it's a security issue, eg. with some fiddling data wipe on ROM installation can actually be bypassed in EDL even w/ locked bootloader enabling thieves etc to gain access to your encrypted / protected data...

This, of course, presents serious issues for modders. Eg I use MIUI*, but it's fraught due to hardbrick potential which requires being logged into 'Authorised Service Account' at Xiaomi service dept. or w/ TeamViewer connected session with Authorized Account holding agent, and these are now like hens teeth as Xiaomi has now revoked accounts for most and now requires per-session payments from agent... (Due to same security abuse potential?)

*Nb. MIUI hardbrick issue is largely confined to MediaTek devices which are infamously easy to hardbrick, and even Devs have become tired of going to 3rd party agents to pay / unbrick, so many custom projects for MediaTek Xiaomi devices have ceased... On the other hand it seems you need to do something dumb to hardbrick Qualcomm Xiaomi...

PSA: Xiaomi Modders - BUY ONLY QUALCOMM SOC Devices! You have been warned!

I twice hardbricked a Redmi 6 just by flashing faulty TWRPs (made for device!!) - yes, this CAN do it... on MediaTek! Both times used an agent in Vietnam and fixed in 15 minutes w/ TeamViewer session for $20; no fuss fix... Since had numerous requests for details from XDA users in same bind, and got into trouble with XDA for passing on details (paid services break rules) even after confining this to Private Messages! Was told PMs are part of XDA forums under same rules...

Interesting discussion with Mods followed, but the staunch position (and they did say they'd review it) that there are NO exceptions remains. Ironically, XDA members with knowledge of any remaining Authorised Account holders (quite necessary for many users as there is simply NO Xiaomi service center in their city or county! ... and these don't do TeamViewer etc anyway) are thus BARRED from giving details / reviews to help users find honest / avoid unscrupulous agents... 😕 - I told Mods that this effectively means XDA would rather you have an expensive paperweight after being rewarded with a hard brick for following instructions posted here to the letter, than allow members to part with $20 and get their beautiful phone / device back on the strength of any XDA members personal experience! ... (RULES XDA! - why not PRINCIPLES?)

Thanks for opening an old wound doc.

🙃 PW
[Magisk] pndwal:
Nekogram X from Play Store. 😛

I think it just worked; can't recall configuring... PW
[Magisk] koala86:
Thank you, I will try this.
[Magisk] pndwal:
No experience with OnePlus, but experience shows that flashtools are very finicky and often only certain versions work with a specific ROM. Even newest often fails...

Many (most?) fastboot ROMs package correct flashtool in the archive. Doesn't OnePlus do this?... OnePlus users may help you better...

Despite what's been said, it seems you can simply flash boot.img only from fastboot on OnePlus 7 Pro. May need to search how to extract boot image from ROM if it's not visible in archive... I think I saw instructions mentioned... I'd be trying this first if possible; flash complete ROM only if needed. 😬 PW
[Magisk] midgo12:
The MSM tool and files in this link are for the Android 10 OOS both global and EU rom files are included and I have used them on my Oneplus 7pro GM 1910.

It worked for me so good luck...
[Magisk] pndwal:
Curious, is it possible to simply fastboot flash boot.img on OnePlus 7 / 7 Pro (as search seems to indicate)? And any special knowledge needed to extract from OnePlus ROM archive? Ta, PW
[Magisk] m0han:
i think you need to tap on the foreign language post and choose 'translate' from the pop-up. or, does it auto-translate for you?
[Magisk] midgo12:
I have only ever used these files to recover from a bricked device.

They worked in this situation and restored my phone to vanilla 10.3.8 and then I was able to update to the latest OOS Android 11 using OTA through Oxygen Updater.

I have never tried any other way so cannot comment on that aspect...
[Magisk] pndwal:
Haha, copy / forward restriction removed! 😝...

Par for the course I guess! 🤪 PW
[Magisk] pndwal:
I mean can fastboot be used at all? eg to flash Magisk patched boot image as per Magisk Installation Instruction? - Asking since @ipdev suggests OnePlus supports EDL but not Fastboot. 🤔 PW
[Magisk] pndwal:
Yup, tapping for each post here. PW
[Magisk] zgfg:
Cannot judge for Poco X3, mine is Mi 9T

Generally I use official TWRP but sometimes switch to alternative recoveries

In OFox, few more partitions can be backed up, like DTBO (although, so far I didn't need to pull restore)
[Magisk] J.Michael:
There is a warning that only filling the AP slot in Odin (not providing BL, CP, and CSC) can result in the data partition being shrunk. Could you have done this?
[Magisk] midgo12:
Yes I have flashed magisk patched images as well as stock boot images on the current Derpfest 12 custom Android 12 rom I am running on my Oneplus 7Pro GM 1910 using fastboot.

When I was on OOS 11 I used the latest TWRP 11as my recovery and was able to flash anything including magisk through TWRP recovery.

That was convenient so I am looking forward to a TWRP 12 hopefully soon...
[Magisk] koala86:
I decided to try to go into fastboot mode and flash boot.img, but now my phone is in a loop. It keeps repeating "The boot loader is unlocked and software integrity cannot be guaranteed..."
[Magisk] pndwal:
So did you already have boot restored? I've lost track... And are you sure boot.img matches current ROM and is stock (not parched)? PW
[Magisk] pndwal:
Hiding

Latest Hide My Applist:

V2.3.2 Final Version

Changelog:

Add syscall interception

Remove maps interception (Because it is meaningless. Though I am lazy to remove it from UI)

Support Zygisk (Be sure to remove the old Magisk module first, then install it by command!)

It has been a long time since the last version was released. Due to various trivial matters, HMA will stop updating. This means that V2.3.2 will probably be the last version of this project, but there are still a lot of known bugs (If the Magisk module is enabled with the Xposed module disabled, it will cause bootloop; After switching on file interception, some banks are not functioning properly).

Note: Uninstall old Magisk extension before updating to V2.3.2, then install the new one via the install button in the app. If you encounter unable to get root access, please manually extract the installer from the apk and rename it to Riru-HideMyApplist.zip or Zygisk-HideMyApplist.zip and install it manually with the magisk --install-module zippath command.

Although HMA is suspended, you are still welcome to submit translations or fix PRs, and if you want to join the discussion group, please check the first pinned message in the channel. My new app is still on development, but it's not clear when the first preview version will be released. Thank you all for your support along the way, and I look forward to seeing you all on the new journey as we part for the better.

https://github.com/Dr-TSNG/Hide-My-Applist

... Seems app is suspended, but a new one is on the horizon... somewhere... and we now have app syscall hiding. 😀

Thanks Nullptr. 👍 PW
[Magisk] koala86:
I was finally able to figure it out. I watched this YouTube video, and all I needed was the t-mobile firmware, and the t-mobile to global firmware.

Thank you.
[Magisk] pndwal:
👍 .... As far as I can see, if you do intend install magisk again (I'd wait for merged fix for 7 / 7 Pro if using Android 12) you should be able to do so by fastboot patching boot.img extracted from that ROM. I suspect you may have been flashing a different or patched boot image before... (Only thing I'm hazy on are flash instructions for A/B devices w/o recovery partition).

Also, recovery in the event of bootloops w/ magisk should be as simple as flashing unpatched boot image... Let us know if you do restore Magisk... All best with it, PW
[Magisk] zgfg:
Putting simple, I updated HMA LSPosed module from 2.2.4 to 2.3.2 and rebooted

Upon reboot, I had one soft reboot and when I opened Playstore (I hide/detach some apps from Playstore) one Force Close for Playstore

I tried more reboots, opening Playstore, seems it's all stabilized now and HMA continued working fine

And Idid not need the remark about renaming and flashing Zygisk-HideMyApplist.zip...
[Magisk] traversone:
dear,

do you know why this issue #5185 has been closed ?
[Magisk] GauchoTche:
There's a:

Assign to @yujincheng08

and then the thread is closed. What does this means please?
[Magisk] pndwal:
Nb. Caveats:

• Uncheck the last two interception methods, filedetection and mapscan.

• If the Magisk module is enabled with the Xposed module disabled it will cause bootloop. 😬 PW
[Magisk] pndwal:
I've asked... May get ignored... Hopefully LoveSy's still on it... PW
[Magisk] traversone:
much appreciated!

and, from my side (only?), I would also care the "unpack error" on some boot.img....
[Magisk] pndwal:
Bit further; there was this:

https://t.me/c/1414270883/25563

So while Android 8.1 / 9 is supported in theory, it may not be in fact... (Guessing 'Broken Magisk' error itself may in fact be in error at this stage, or Magisk may not be broken at all).

If it is this it should be handled in closed source Shamiko and I anticipate we'll see a new build or minimum requirement / compatibility note appear soon...

Hoping for further comments...

*** Does anyone have working Shamiko on Android 8.1 / 9 ? ***

😶 PW
[Magisk] GauchoTche:
I cannot access the message, it says I'm not allowed, is there a way I can get into the group so I can follow those messages?

About this magisk alpha telegram group. Is the ZIP fie a file to flash with TWRP to patch the boot image? the APK file the Android magisk app?
[Magisk] traversone:
nope...you have to use APK both as Manager and flashable installer in TWRP.
[Magisk] zgfg:
Zip file is source

Apk is for patch/flash

If you need zip for TWRP, rename apk to install.zip (details in Magisk Installation instructions) - in case of TWRP 3.6.0+, you even don't need to rename, use as apk for TWRP

Have you ever been into that Telegram channel and were blocked by admins? If not, you should be able to subscribe to

If blocked, you would need e.g. TG as dual app, with an alter-ego account
[Magisk] GauchoTche:
No, I've not been blocked. Could you please send a link to the group itself, not the message?
[Magisk] pndwal:
Re. https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86233863

Ok, so vvb2060 responded.

https://github.com/topjohnwu/Magisk/issues/5185#issuecomment-1008896945

Issue is with"flock"... Does he mean Google FLoC??... Still baffled... I posted questions:

https://github.com/topjohnwu/Magisk/issues/5185#issuecomment-1008908777

🤔 PW
[Magisk] traversone:
just tried, always on S4 but flashed with LOS 16 (PIE): same error in Shamiko execution so I would say it is (generally?) not working before Q as on same S4 but flashed with LOS 17.1 it works well
[Magisk] zgfg:
I had an invitation link:

Join group chat on Telegram

t.me

but it shows now it's expired. It's kind of a secret society 🤪

Maybe @pndwal can help you
[Magisk] traversone:
...@pndwal please help me too for same subject
[Magisk] GauchoTche:
this is what I get. I need to get into the group first, then I can see the message. Can anyone help?
[Magisk] zgfg:
You need to open from Telegram, not a browser
[Magisk] GauchoTche:
Any chance Alpha 3 could fix the issue? it was posted in the telegram group
[Magisk] GauchoTche:
it doesn't matter opening from windows telegram or phone telegram, both say the same, must be in the group to access that message.
[Magisk] zgfg:
Check the PM
[Magisk] pndwal:
Try this?

https://t.me/c/1414270883/

Just truncated from message...

No... @martyfender is on Alpha3...

Seems issue is w/ Android 8.1 / 9 as I suspected... Works fine on 10+...

Try custom ROM? Move to Android 11? Many choices:

https://xdaforums.com/f/lenovo-zuk-z2-plus-roms-kernels-recoveries.6267/

👀 PW
[Magisk] martyfender:
No, if you are talking about the shamiko issue, I am on alpha-3.

I have reverted back by turning off zygisk, turning on Magiskhide and reinstalling riru, momo-hider and the riru safetynet-fix module until this is resolved.
[Magisk] GauchoTche:
What is RIRU? does it makes bank apps that refuse to run work?
[Magisk] rodken:
More in-depth explanation.
[Magisk] GauchoTche:
Thanks. I've noticed that my bank app refuses to play even with magisk completely uninstalled. Could it be detecting unlocked bootloader? What else could it be detecting?
[Magisk] rodken:
Utilize the 'Search This Thread" feature.

input the term "banking app".
[Magisk] zgfg:
Riru is an older 'technology'. Not compatible with Zygisk (hence you cannot use if you already opted for Zygisk+DenyList, only if you stay with the old MagiskHide)

E.g., you can install Riru and Riru-LSposed Magisk modules, or enable Zygisk and then use Zygisk-LSposed Magisk module
[Magisk] GauchoTche:
so I did the search and checked many posts, but I cannot find something specific about bank app detecting unlocked bootloader and how to prevent that. I've completely wiped data, uninstalled the bank app, completely uninstalled magisk, installed bank app (no magisk or root) and it still refused to run. I'm also not sure if there's a way to find out what kind of data the app is checking to prevent run.
[Magisk] zgfg:
Almost every bank could have their own app, developed by different developers, utilizing different methods to (mostly) guess if your phone is rooted

There is no such thing as a generic method, used by all banking apps to find root.

Hence there is also not a single method to hide root from all banking apps

They usually combine various methods to find or better to say, guess if your phone is rooted.

Attesting SafetyNet is usually just one, 'trivial' part

Did you google for your particular banking app, under the app name. And search the same also here on XDA

For starting, Wiki on Magisk Github (there is a section with various honts to try)
[Magisk] HippoMan:
Some banking apps look for the existence of a TWRP folder. Do you have one on your sdcard? If so, you might try renaming it to some random name and rebooting.

Some banks also look for the existence of the "Titanium Backup" app.

There are other tests that various banking programs perform. These just happen to be two that I know about.
[Magisk] pndwal:
I think you need to understand the basics.

Hiding Broken TEE (aka hiding 'root') Basics:

As a minimum, bank / other security centric apps look for Play Protect Device is certified result (see Play Store settings) which requires full SafetyNet pass.

Device will be uncertified with unlocked bootloader (so bank apps know TEE - Trusted Execution Environment - is broken before ever checking if bootloader is unlocked.

To counter this, Magisk modules (Universal Safety Net Fix, MagiskHide Props Config etc).and some custom ROMs provide spoofing (Compatibility Test Suite - CTS - certified fingerprint etc) / hiding (traces, signals...) etc needed to pass SafetyNet and, in turn, Play Protect certification.

If you have Play Protect 'Device is certified' result and 'root' (modified execution environment) is hidden from app (ie. it's in denylist / hidelist), then app is employing its own custom checks since SafetyNet is well known to be unreliable / easily subverted. (Probably the reason Google is renaming upcoming SafetyNet replacement API, rather than just strengthening it, to Google Play Integrity API. 👀) Sometimes the app is doing a simple check for Magisk app, and just using Magisk's Hide the Magisk App feature is enough to subvert this check.

If not, it may be using complex app detection, looking for other root apps, twrp etc, or even isolated process mount leaks etc... You will need to research / test on a per-app basis... there are module and other solutions (Riru-Momohider, Shamiko (Zygisk), LSPosed-Hide My Applist, etc) + various methods... Start here for understanding:

https://www.didgeridoohan.com/magisk/MagiskHide

See especially 'Hiding root from apps'.

🤠 PW
[Magisk] pndwal:
So canyie confirmed it's not a Magisk issue; Shamiko problem:

https://github.com/topjohnwu/Magisk/issues/5185#issuecomment-1009000522... PW
[Magisk] m0han:
late with this: have seen that feature (and more) in 'plus messenger' from long back.
[Magisk] pndwal:
I was using that when it stopped working... Works better than official Telegram, yes, but neither app translates when group disallows copying / forwarding... Nekogram does...

Alpha group turned copying / forwarding back on; policy changes with the weather there. So any app works now... Try it in LSPosed group though! 😉 PW
[Magisk] m0han:
after installing Hide My Applist v2.3.2, Applist Detector v1.3.2 reports abnormal environment 'found'. how can i resolve the issue? (i've done everything as with HMA v2.2.4, where i had everything not found.)
[Magisk] GauchoTche:
Man, thanks very much, that did the trick! I have:

- Renamed TWRP folder

- Renamed TitaniumBackup folder

- Activated magisk hide for the app

- Hide magisk with its incognito feature

This solved the problem with the bank app. I'm so glad, cause Shamiko doesn't work with my phone.
[Magisk] zgfg:
Since Lsposed Manager supports what they call Parasitic app (read on the Guthub LSPosed page), you can uninstall the Lsposed Manager apk (you can create the shortcut or dial a secret code when you need to change something in LSPosed)
[Magisk] m0han:
lsposed manager not present in apps/drawer. only the shortcut remains
[Magisk] zgfg:
Hmm strange, not showing for me (complaining only for Magisk app since I did not hide/repackage the app)

Actually I think (it was long ago) I configured in HMA to hide Lsposed mngr from Applist Detector before I removed Lsposed mngr (and HMA shows me there are 6 'effective' configuref apps, but when I open it lists only five - I think that LSPosed mngr is the sixth, 'lost')
[Magisk] CitizenSmith:
Still new to using roms and could really do with some help.

Got a problem I had rooted my samsung s7 a while back and used ALEXNDR custom rom it all went well and still is but I wanted to try a more up to date rom so started looking at the phone again and forgot whats what!.

i have managed to update Magisk with version23.0 and it seemed to update fine it saw the previous version and stalled using an apk however when I now open magisk all looks ok and saftynet shows Sucess but when I go to settings/ customization I only get list from Themes to Download Path there is nothing after that. after watching www.youtube.com/watch?v=g1bDfDjtUsY.

I can't see Clear repo cashe and any thing else there after is missing!!! that's including magisk hide which I know I enabled when i installed my last rom.

I have rootchecker pro installed and it shows not rooted but I know I had magisk fool the phone so it thinks it's not rooted so I can get certain apps to run not sure if this is part of my problem!

I have completely forget what and how I flashed and rooted my phone and can't figure out how to proceed from here any help here would seriously be appreciated. can't find way to revert back to old magisk as I don't seem to have any apks for that old version only files! again forgot how I did this now just confused to hell!.

Don't want to uninstall anything yet incase I loose ability to edit rooted phone or the apps.
[Magisk] lolvatveo:
canyie's custom version didn't work, so I chose to uninstall magisk and restore boot.img didn't work it said no stock boot exists. almost no root privileges.
[Magisk] c3k:
I'm going to update my Samsung S21 from Android 11 One UI 3.1 to Android 12 One UI 4, can someone confirm that the standard firmware update procedure (patched system image + home_csc) will work?

Thank you!
[Magisk] zgfg:
Is this really a question for Magisk support (discussion about Magisk on all kinds of Android smartphones and versions) or something you should check/ask on the XDA subforums for particular Samsung device (users knowing and interested in your particular phone, update procedures, etc)?