yashsingh1/xdaforums huggingface dataset:
[Xposed General] metal.satan:
hi bro

It's very simple

1.open xposed menu / open xposed hide (black) then Find and mark app cloner

2.open lucky patcher menu / open exposed setting and mark all and enable exposed module.

3.restart phone END
[Xposed General] yuminhao:
The most efficient way is to complie xposed source code and change some string names
[Xposed General] olik2000:
Use momo, try to hide root and xposed from it, if you succeed, app cloner shouldn't detect anything.

You can download it from here

Magisk alpha

检测设备修改情况 更新日志： 修复zygisk的假阳性 修复包管理异常的检测

t.me
[Xposed General] christantoan:
Thank you but I already use Momo and I don't think it's possible to fully hide Xposed from it if Xposed is still enabled (AFAIK ART parameters are abnormal)
[Xposed General] olik2000:
I had the same problem with lsposed, I solved it by going to data/adb/modules/lsposed and open system.prop using text editor and add # before the first line. Save the file and reboot then check exposed.

Lsposed shows me system prop incorrect but everything works normally and momo doesn't detect it anymore.
[Xposed General] christantoan:
I had heard about that method as well though I haven't tried it yet with App Cloner. I was afraid it would cause unseen problems.
[Xposed General] christantoan:
I just tried but it still doesn't work with App Cloner. However, my Momo still doesn't show clean results though. Just the ART parameters... is removed now (see attached screenshot).

Can you help?

Thank you in advance!
[Xposed General] olik2000:
I didn't have any of these two problems, could it be that you're using a custom rom? For the traces, I had the twrp/magisk files trace, I just changed the name of the twrp folder and it was solved. Anyway, if I find anything regarding the two problems you have under "details" I'll let you know.
[Xposed General] christantoan:
Thank you very much for your help as I've been also searching for the solution. For the partition mounted abnormally I've read somewhere it's because of unlocked bootloader though I haven't verified it as I need to stay unlocked.
[Xposed General] olik2000:
By the way, I have magisk and lsposed. I downloaded app cloner, went to magisk and hid it in the configure denylist with

"Enforce denylist" disabled

I have the shamiko module activated

My magisk app is hidden

The way lsposed works is that it is only injected in the app you select, so if xposed is applied on all apps, that means all the apps can know if xposed is installed. Make sure to configure that in xposed settings. I've read there's an option called globally or something like that, so disable it if it's there if possible or just switch to lsposed

App cloner works fine for me
[Xposed General] olik2000:
Mine is unlocked too, so I don't think that's the problem
[Xposed General] christantoan:
Turns out I've enabled App Cloner in one of my LSPosed module (Minminguard). I've disabled it now and it's working.

Woah, nice knowing that!

I always thought it was due to my settings.
[Xposed General] olik2000:
Happy to hear that, no reboots anymore! :D
[Xposed General] christantoan:
Yep! And it even still works when LSPosed system.prop is restored.
[Xposed General] IngwiePhoenix:
I am currently trying to get a banking app to work, "VR SecureGo Plus". There is also "VR SecureGo", but my bank wants to switch to the new Plus version...

So I have Magisk 24.3, LSPosed 1.8.0, MicroG and FakeGApps as well as Shamiko and Hide My Applist. The Applist Detector shows that nothing can be found - except the LSPosed modules, and specifically the HMA one.

As I got everything working as it should, all I want to do is hide the XPosed modules from the app (both Applist Detector to verify and VR SecureGo Plus to actually use it).

Any idea? Been trying to figure this out for hours now and I have run into several walls - both in terms of finding just about nothing and in terms of text; Google Translate doesn't seem to like Taiwanese a lot :/

Thank you in advance and kind regards,

Ingwie

Spoiler content hidden.
[Xposed General] Ace_Cole:
So in a short term xposed can't be hidden from apps enabled in xposed modules.

I wish there is a way to solve this.. 🤔
[Xposed General] EuRen:
Maybe it checks for root?

For my banking app I used:

Magisk Hide

Sudo Hide

Root Cloak

I enabled it on all just to be sure.

*Edit: Sorry my fault, you are already using Shamiko to hide root.
[Xposed General] andybones:
The post linked to the Apps website which describes exactly what it does. :-)

"The app i want to run. but can't because I don't want to deactive xposed, is called App Cloner 2.12.5 (google banned them from playstore but their app is still elsewhere https://appcloner.app/)"
[OnePlus 8T Questions & Answers] kinkoff85:
Bricked my phone... Can only boot into fastboot, and cannot connect to msm tool. Please help. This is the first time in 12 years of tinkering I have ever turned a phone into a paperweight
[OnePlus 8T Questions & Answers] BillGoss:
The MSM tool thread has everything you need and the instructions in the OP are very good.

[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...

xdaforums.com

PS: if you can get into bootloader, then your phone is obviously not bricked.
[OnePlus 8T Questions & Answers] kinkoff85:
It won't go

It won't load anything but fastboot
[OnePlus 8T Questions & Answers] kjslabber:
If phone won't connect in EDL try using different usb port on your pc. Works a lot of the time.
[OnePlus 8T Questions & Answers] GraveDigger176:
Have you disabled the driver signature, are you have the latest Qualcomm drivers and the latest OnePlus drivers ?
[OnePlus 8T Questions & Answers] BillGoss:
We can't see your phone or what you've done unless you tell us. Why don't you describe in detail what you did and what happened.
[OnePlus 8T Questions & Answers] kinkoff85:
I tried flashing a custom ROM based off Pixel and android 12... It rebooted and went straight to fastboot and that's the only place it will go is fastboot. I later read that rom was not compatible with the 8t only the 8 and 8pro. Whenever I try to connect it with MSM TOOL it simply reboots right back into fastboot. I do have TWRP recovery installed but cannot figure how to flash or side load from there either. I've tried over and over.
[OnePlus 8T Questions & Answers] BillGoss:
When you're in fastboot, flash TWRP and then boot into recovery.
[OnePlus 8T Questions & Answers] kinkoff85:
There is nothing to flash once in recovery.
[OnePlus 8T Questions & Answers] BillGoss:
You'll have to format data (wipe>format data: type 'yes') and then sideloaded what you want to flash.
[OnePlus 8T Questions & Answers] TanakaX5:
Try these fixes mentioned in these videos

and

especially the tips from the second video, helped me once I couldn't get into edl mode.
[Non-Touchscreen Windows Mobile Other] frskies:
Hi, i bought a chinese iphone clone which runs windows mobile 6.0, it came with S2U2 and S2V by A_C installed to make it look like a iphone:) I would like to uninstall them before i install the newest versions, but they aren`t in the "Remove programs" menu, so how do i uninstall them?

And one more question: From time to time a dialog box pops up with the title "power off hint" and asks me if i want to power off my device; i don`t know why, and it messes up the GUI, is it possible to disable this?
[Non-Touchscreen Windows Mobile Other] brad-sylvester:
Same Problem

I have the same problem. See no one has answered in a year. Hope someone know the answer now.
[General Questions and Answers] dorkxperience:
Well I bought this Calypso U318AA from a friend for cheap. It was his sons he got new phone. I bought it to root it. I was just going to do the magical root.. I've rooted several other phones in past. The world wide web has very little info well, no info on this thing. It's a Android 10. I'm not sure of even the best way to unlock the bootloader. I know it doesn't have nothing in developers options. On recovery reboot you can do a recovery boot and a fastboot as well as normal boot. Can't find anything but factory at&t stuff. So any info would be great. Thank you
[General Questions and Answers] mrmazak:
I just received this phone from at&t. Found out mtk_client will unlock bootloader. so magisk root "should be" available after this unlock. I have not tried yet , i only unlocked bootloader earlier today. will keep looking for anyone else trying this and update as i find any info.
[General Questions and Answers] mrmazak:
Twrp is working (mostly) for TINNO U318AA. (ATT&T Calypso)

still need to work out data decryption, and FatsbootD mode.

Device Tree: https://github.com/mrmazakblu/twrp-device-att_u318aa/tree/twrp-11

Device Dump: https://github.com/mrmazakblu/att_u318aa_dump
[General Questions and Answers] mrmazak:
Phh aoap gsi a11 installs and runs good
[General Questions and Answers] mrmazak:
To clarify, let me tel you all which build version i have installed and outline the steps to get it loaded.

THIS IS NOT INTENDED TO BE STEP BY STEP GUIDE ONLY AN OVERVIEW

WHATEVER YOU DO ON YOUR DEVICE IS AT YOUR OWN RISK

system-squeak-arm32_binder64-ab-vndklite-vanilla

downloaded from :

Releases · phhusson/treble_experimentations

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com

!. Bootloader must be unlocked.

AT&T removed the enable OEM unlock from developer menu, but there is an excellent work around 'tool' to get around this.

MTK CLIENT will allow you to read (pull) stock firmware off from phone, much like spflash tool does, except with this phone and many other newer phones the manufacture has enabled security and authorization files to block sp flash tool , SOOOO, tools like mtk client try to stay a step ahead.

I only used the GUI options with the client, it was very user friendly , the tool has way more options than i needed to mess with.

GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool

MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.

github.com

2. Before flashing gsi, make sure you have pulled firmware from phone, so you have stock super.img. If you don't you will not be able to restore device when / if you mess up the vendor partition.

3. I disabled vbmeta verification .

will need stock vbmeta from pulled firmware.

boot into bootloader, (adb reboot bootloader , or reboot while holding the volume up button. You should get a boot menu)

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

(the last part need to point to you file location where ever it is)

4. Now we need to move from bootloader to fastboot. fastboot reboot command didn't work for me so needed to boot recovery first, then fastboot.

fastboot reboot

hold volume up button to get boot menu, select recovery

from recovery select reboot fastboot

in the fastbootd connection you will be able to flash gsi

the system area is not large enough to fit gsi , so you will need to remove the /product partition.

fastboot delete-logical-partition product
fastboot flash system system-squeak-arm32_binder64-ab-vndklite-vanilla.img

once completed use the screen menu to reboot back to recovery and perform factory reset.

With the exception of needing to use mtk client, the rest of these steps are standard android process. documented in many locations. I go to the android source first for information. \

Moving Fastboot to Userspace | Android Open Source Project

source.android.com
[General Questions and Answers] inglele:
Thanks a lot mrmazak, I'm working on a step by step guide for newbies like me to expand on your steps to unblock and reflash the phone.

I was able to use MRK Client, unlock bootloader and put the phone in fastboot.

The problem I have is to find the right MediaTek driver for the device USB\VID_0E8D&PID_201C

Where did you find them? I tried Google USB driver from ADP but they use different Device ID and all MediaTek driver with same VendorID 08ED have old ProductID instead of 201C.

Any help on MediaTek driver so I can finish the guide and post the link here?

Specifically, I was able to connect via ADB but Fastboot requires a different driver which I'm not able to find :(

Thanks a lot for your help!
[General Questions and Answers] dorkxperience:
Thats awesome thanks
[General Questions and Answers] mrmazak:
Did not have to install any drivers special.
[General Questions and Answers] inglele:
Yes, I had Other \ Android device listed in Device Manager, so I tried disable signed driver and force install of these drivers: https://xdaforums.com/t/windows-10-...32-64-bit-driver-install-tutorial-m2.3267033/

Now, I have it visible as MediaTek PreLoader USB VCOM Port but if I type "fastboot devices" is not listed.

ADB is able to see it correctly:

adb devices
List of devices attached
AYMB5PKZCUEUUOSC device

When I restart in fastboot with "adb reboot bootloader" the phone restart correctly in fastboot.

I'm not able to unblock the connection between fastboot tool and phone in fastboot mode, I suspect due to missing / wrong driver.

If you have any idea, it would be great! :)
[General Questions and Answers] inglele:
Found the correct driver. I needed to force Google ADB Driver -> "Android Bootloader Interface" and it works!

They are available here: https://developer.android.com/studio/run/win-usb

Thanks for the help and sorry for confusion, newbie questions :)
[General Questions and Answers] mrmazak:
Mod Edit: Quote removed since post deleted.

I received 'not enough space" error when flashed gsi, this is why i delete product partition.

I recall there are fastboot commands to list super.img size, but not sure for super sub-partiton size. there are tools to extract the sub-partitons and it will show individual size.

there must be commands for it in fastboot i think, But i do not know them.\
[General Questions and Answers] ltk6260:
hi! hope i can get some help. this is my first time using mtkclient but i can't seem to get it to detect the phone. i'm making sure to follow the steps listed of having the phone off first, then press both volume buttons and plug in the usb. on the phone it eventually pulls up a "select boot mode" where i can use the volume buttons to select recovery mode fastboot mode or normal mode boot. i've tried recovery and fast boot modes as well as just leaving it on that select screen but nothing is detected in mtkclient

thanks!
[General Questions and Answers] chucklesb8080:
New to the world of droid but am familiar with modding stuff so I'm a semi-noob I suppose. Found myself getting one of these things from the local dollar general and followed this guide to get rid of all the google crap and hopefully speed it up a bit. Bootloader is unlocked, .img posted above is flashed, and it boots up and seemingly works. Can't figure out how to sideload apps nor can I find any type of write up explaining what to do with the tree and dump file posted above. Any help and/or clarification, greatly appreciated. MTKClient, ADB, and Fastboot are all installed and functional. Using Linux Manjaro.

--chuckles b
[General Questions and Answers] veryspecialagent:
Run mtkclient. With the phone already off, hold down both volume buttons and connect the phone to your computer. You should hear the "usb connected" notification sound on your computer and mtkclient will pick up it. As soon as you hear that chime, release the buttons, set the phone down, and don't touch it. The screen shouldn't come on during this step.

Make sure you're ONLY holding down the volume buttons and plugging it in. Don't touch the power button.

If you're still having issues with it not picking up your phone, go through the standard troubleshooting steps: Recheck you followed every step, restart your computer, try other USB ports, try other cables.

*********

FYI this isn't applicable to this process, but should be noted: This phone has a weird way to get into the recovery menu. You have to hold Vol+ and Power, then select Recovery from the menu, THEN immediately press and hold the Vol+ (or Vol- I don't recall at the moment) and Power buttons again until the recovery menu comes up
[General Questions and Answers] ltk6260:
Thanks! that did help.

i was able to get all the way through up to flashing the new rom. I'm getting this error:

fastboot flash system system-squeak-arm32_binder64-ab-vndklite-vanilla.img

Invalid sparse file format at header magic

Resizing 'system' OKAY [ 0.013s]

error: write_sparse_skip_chunk: don't care size 201668900 is not a multiple of the block size 4096

Sending sparse 'system' 1/2 (262140 KB) error: write_sparse_skip_chunk: don't care size 201668900 is not a multiple of the block size 4096

error: write_sparse_skip_chunk: don't care size 201668900 is not a multiple of the block size 4096

OKAY [ 12.568s]

Writing 'system' FAILED (remote: 'No such file or directory')

fastboot: error: Command failed

still can't get past this error. i've confirmed my filename, file extensions, and file location. even checked file permissions. the img file is in the same folder as the fastboot command itself.

i also tried the command using the full c:\ path to the img file but it fails the same.

i then restored the phone to the original super.bin and the phone worked like normal. so i went all the way back through the steps starting from the top but failed at the same final step flashing the system.
[General Questions and Answers] veryspecialagent:
What are you trying to do? What is the purpose or end result you're hoping to achieve?

I ask because this thread is a bit convoluted and "noobs" looking to just root and tinker might come in thinking they have to do all the steps in this thread to get there.

Like someone wanting an oil change overhearing two mechanics rebuilding a transmission, taking notes, especially where they mentioned "oil," then walking away thinking that's what they need to do.

The tools linked above are great. The mtk one, once I was able to get it running, was how I got past the FRP. For anyone wondering, there's an FRP partition that you can just delete with the tool.

If you're just wanting root, see above for unlocking the bootloader, then stop. I'm 90% certain I achieved root by just following the process outlined the official Magisk page on GitHub.

Can I get some OP/MOD thoughts on breaking this thread up into specific guides with the purpose clearly written in the title?
[General Questions and Answers] ltk6260:
I understand your questioning. I'm trying to unlock and load aosp firmware, or frankly, anything other than what this device is loaded with since it's horribly bloated, slow and periodically unstable. this is a play phone, i have two of these phones actually.
[General Questions and Answers] veryspecialagent:
So is mine. I agree with the bloat, which I thought was weird considering the Android 10 version it comes with (Go) is supposed to be a more streamlined version for lower end phones that lack the processing power.

I tend to not do new ROMs unless it's something with a track record and support like Lineage, but after playing around with it and testing some of the functions with things like WIGL, Termux, LSposed, etc, I'm thinking it might be a good Nethunter phone.
[General Questions and Answers] veryspecialagent:
After some extensive Googling, and since I doubt this falls under the "you're flashing the wrong build/version" because there's only one variant of this phone, I'd say it might be possible you're not running the right SDK platform package.

Start Android Studio, go to Settings > Appearance & Behavior > System Settings > Android SDK and make sure you have the right platform packages installed (i.e. Android 10, API 29) and updated.
[General Questions and Answers] ltk6260:
I don't have the full android studio installed, just downloaded the platform tools (as per this page). I can install the full studio and check again though
[General Questions and Answers] aragats:
I got this phone yesterday.

Unlocked bootloader, but there is no system partition.

I tried writing both A11 and A12 to super, but it reboots into fastboot after flashing.

I don't have much experience in such things, maybe just missing something?
[General Questions and Answers] aragats:
Okay, I got it: super must be unpacked with lpunpack and repacked with lpmake using the new system.img.
[General Questions and Answers] ltk6260:
oh man you're way ahead of me when it comes to this stuff. were you able flash aosp from this guide? or what were you trying to accomplish with your phone
[General Questions and Answers] ltk6260:
trying my way through the tools and was able to use lpunpack, i'm assuming i swap in the old system.img with the new one and then use lpmake to pack it back up. but what parameters and flags did you use on lpmake? i'm looking at the arguments for the command and don' t know the answers to things like device size, metadata slots etc
[General Questions and Answers] aragats:
@ltk6260

I started from the directions described in this this thread.

As was suggested above, I ignored product.img when repacked since we need more space. My command line for the gapps version of A12 was:

lpmake --metadata-size 65536 --super-name super --metadata-slots 1 --device super:2457862144 --group main:2066169856 --partition system:readonly:1853341696:main --image system=system-squeak-arm32_binder64-ab-vndklite-gogapps.img --partition vendor:readonly:212828160:main --image vendor=vendor.img --sparse --output super-new.img

(just ignore sparse file warnings).

Basically, the numbers correspond to the file sizes in bytes. For --device super I used the size of the current super minus the size of metadata (65536).
[General Questions and Answers] ltk6260:
thanks very much that's very helpful. I'll take a closer look and see if this will help me. did you then write the new packed super back to the phone using mtk gui that this thread mentions? ('m a noob still learning)
[General Questions and Answers] aragats:
It can be done with mtkclient, although I prefer the plain fastboot:

fastboot flash super super-new.img
[General Questions and Answers] ltk6260:
thanks! I wonder why the guide posted in this thread earlier references to fastboot flash the system img file but it doesn't seem to be able to do it directly if the system img is packed into the super bin.

Just wondering what that means, is it something specific with this phone? can you normally flash the system img directly via fastboot flash? it didn't work for me so that's why i'm trying to go this route of lpunpack/lpmake but this is new territory for me.
[General Questions and Answers] aragats:
In all Android devices I've ever dealt with, system was a separate partition. Here we have super partition, which, in its turn, contains 3 other partitions: vendor, product and system. So, those "sub-partitions" are not visible to fastboot. I think, maybe earlier revisions of that phone had a "flat" partitioning scheme, thus the written above perfectly worked.
[General Questions and Answers] ltk6260:
ah makes sense.

Well i'm hitting my next roadblock attempting to use the lpmake command shared above:

./lpmake --metadata-size 65536 --super-name super --metadata-slots 1 --device super:2457862144 --group main:2066169856 --partition system:readonly:1853341696:main --image system=system-squeak-arm32_binder64-ab-vndklite-gogapps.img --partition vendor:readonly:212828160:main --image vendor=vendor.img --sparse --output super-new.img

lpmake I 07-19 14:13:16 51660 51660 builder.cpp:1012] [liblp]Partition system will resize from 0 bytes to 1853341696 bytes

lpmake I 07-19 14:13:16 51660 51660 builder.cpp:1012] [liblp]Partition vendor will resize from 0 bytes to 212828160 bytes

Invalid sparse file format at header magic

lpmake E 07-19 14:13:16 51660 51660 images.cpp:384] [liblp]read failed: Success