yashsingh1/xdaforums huggingface dataset:
[Xposed General] Skittles9823:
Okay so I've been trying to install the magisk version for about an hour now and its definitely broken. So first I flashed the module, booted up and all was fine, then I installed closed installer but it wouldn't open and kept crashing. So I uninstalled the module rebooted and tried to install it again (I installed through the latest TWRP) and I booted up to System UI, com.android.phone and another app crashing that I didn't recognise bit I have a substratum theme so I thought that was the problem, so I uninstalled magisk, reflashed my ROM then magisk again to get xposed uninstalled and I proceeded to uninstall all overlays in substratum. After that I reflashed closed again and the same apps crash. Every time I flashed xposed I got an error 1 in twrp. The first instance makes me believe that it isn't compatible with xposed installer 3.1.1 my ROM is Dirty Unicorns 11.6, magisk is 13.3 and magisk manager is 5.1.1 I have more then enough system space BTW (over 1gb free in root storage) anybody have any help?
[Xposed General] BlackSoulxxx:
Using topjohnwu template so its not that old
[Xposed General] Skittles9823:
-deleted- didn't merge.
[Xposed General] Didgeridoohan:
He's updated the template quite a few times... The current template is v4 (not compatible with a Magisk versions below v13.1). Use template v3 if you wan't to support older Magisk versions (unsupported, of course).
[Xposed General] theandroidguy:
Ohhh I see thankyou for the help.mate
[Xposed General] BlackSoulxxx:
To be clarify Im actually using the Xposed systemless template by topjohnwu, not building it from scratch.
[Xposed General] lover:
[MENTION=5733862]BlackSoulxxx[/MENTION] [MENTION=4667597]Didgeridoohan[/MENTION]

the user [MENTION=3694505]Telperion[/MENTION] found a work around this, here is his post maybe you find it helpfull

https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268/post72551212#post72551212

he also made a working xposed to pass SN but it needed SuHide: https://xdaforums.com/showpost.php?p=72548221&postcount=3932
[Xposed General] theandroidguy:
Hey which modules are u using, will you please tell me
[Xposed General] Didgeridoohan:
Again... Not the latest one. The latest Magisk Xposed module uses template v3 (that's not what you're using).

That's a workaround to use Xposed and pass SafetyNet. It requires a quite specific setup... Magisk v12 with the Universal SafetyNet fix module, a modified version of the Xposed module, SuperSU, suhide and an Android security patch no later than October 2016. Even then it's nowhere near guaranteed to work.

I'm not sure what that has to do with the current conversation though... :confused:
[Xposed General] BlackSoulxxx:
Again. Seriously im using the v87 systemless version on nov 28 by topjohnwu as my main template.
[Xposed General] Skittles9823:
He means the template for magisk modules in general. Not the xposed modules.
[Xposed General] Didgeridoohan:
Yeah, I know... I should probably have been clearer... The one attached to his systemless Xposed thread is not the latest one. It's here: https://github.com/Magisk-Modules-Repo/xposed_23

And by the way (from the man himself): https://github.com/rovo89/Xposed/issues/230#issuecomment-316560803
[Xposed General] lover:
regardless of security patch Telperion found out by comparing 86.6/87.0 and 86.2/86.5.

It's not the newer Xposed versions that are preventing it from passing SafetyNet, it's something about the flash script that's changed.

maybe we can solve SN by using TopJohnWu's older template and also new v13.3 has solved SN check
[Xposed General] P650SE:
Can anyone clarify the differences between this build and the one by PurifyOS Team in the other thread? I'm a little confused as to which one to choose, despite reading through several pages of each discussion. :confused:
[Xposed General] Skittles9823:
Might want to read this before using it at all. https://github.com/rovo89/Xposed/issues/230#issuecomment-316560803
[Xposed General] superdragonpt:
This "build" is a prebuilt.zip

Likely the other guys are doing on the "right way" (if we can call that) and patched their ROM source and built...

Taking a guess here, with all current limitations( and please do check rovo89's comments on this.)

flashing a prebuilt stuff that was made in an specific src ain't the way at all

this "release" is still great in my point of view , since there's way more people now to debug and check stuff, hence , time saving

For people that do build roms, just patch your ROM source (and for the moment switch to se permissive ) and test that for better results & compatibility on your "a" device..

Modules that do change resources handling will fail miserably

This is by no means * an stable xposed fw handling *

And don't expect modules to work , this is intended @ testers and developing ONLY .

( yup I did it, its all on red, so that you can see )

Bb
[Xposed General] BlackSoulxxx:
New Magisk version now alive with template v3. OP updated.
[Xposed General] Diaze:
how to clear magisk img? im new to this
[Xposed General] SKULSHADY:
Magisk module isn't installing. I get Error 1. I checked the above link for the fix but I have lots of space left on system partition. I an on OP3T running OOS OB11
[Xposed General] CappyT:
Still getting error 1, magisk img is 128mb with almost 80mbs of free space. /system is around 300mb of free space.

Tried flashing it multiple times.
[Xposed General] Harshatxda:
Nougat support - xposed.

Numbers are less to thank you all.

Xposed is so needy that everyone was waiting to release version for nougat. We understand that it may not be stable version but no one will complain. We know how much hard work you all have paid to.

Thanks a ton for releasing
[Xposed General] NightMean:
Using latest magisk v3 version and I have yellow error in xposed saying is installed but not active
[Xposed General] Base2:
Magisk Versions > 13.0

[MENTION=5733862]BlackSoulxxx[/MENTION],

Still a little behind the times, Magisk version is currently at 13.3, and the MagiskManager version is 5.1.1, with the template updated to v4. Topjohnwu has requested that modules be updated to the new template, and stated that versions > 13.0 may not be compatible with earlier templates.

http://xdaforums.com/showpost.php?p=73017774&postcount=24

http://github.com/topjohnwu/magisk-module-template
[Xposed General] YHNdnzj:
Does it support Google Pixel?
[Xposed General] Diaze:
So are the modules working ? Like youtube ad away and amplify ?
[Xposed General] robertogl:
This works only if install at first boot.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed General] MrCreel:
Nexus 6P

Carbon & RR 7.1

Magisk 13.3

Non versions work, error 1 with magisk version with alot of free space on system, tried clean flash also.

Normal version of Xposed cause bootloop
[Xposed General] amuzavali:
Without functional modules is zero
[Xposed General] ak0ztik:
I needed to reinstall my vpn app because i can't open it anymore it crash, and google play is randomly crashing.

Also at boot every boot i get this random crashing of apps.

System Android also crashes at first, and at 2nd crash it restarts my phone.
[Xposed General] fjsferreira:
There's just too many crashes for this to be used daily. The modules I tested worked (minmin guard, always predict, double tap statusbar to sleep) but I ended up restoring my system due to the instability. Still, a great start.

Using oneplus 5 OOS 4.5.5 stock with supersu and permissive stock kernel.

Sent from my OnePlus 5
[Xposed General] Aguys:
Magisk version gave me error 1. So, I tested non-magisk on Nexus 5X running RR rom 5.8.3. Seems working good with Lollistat module active(but still unstable). Some apps crash, especially apps with webview on it.
[Xposed General] :
[MENTION=5733862]BlackSoulxxx[/MENTION] you should really really write in big letters that this is unstable
[Xposed General] unknown:
Really great work [MENTION=5733862]BlackSoulxxx[/MENTION]

I will test soon

VIetnamese dev are proud of you :o:o:o:o:o

I have a question : What is the different between your version and [MENTION=6992457]ErnyTech[/MENTION] version ??? :confused:
[Xposed General] rafaelbrunner:
No success here... Running ViperOS, latest version:

https://xdaforums.com/redmi-note-3/development/rom-viperos-t3613688

I tried the Magisk v3 version:
[Xposed General] unknown:
As he said in first post , It is not working for LOS and AOSP based ROM

Be unique and he will add support for it soon ;);):o:o:o
[Xposed General] rafaelbrunner:
Nope... It's said: "Tested on Sony Xperia XZ F8332 and should be working on AOSP/Lineage/Lineage-based ROM"

So, as ViperOS is based on Lineage, it should work, right? :p
[Xposed General] ErnyTech:
I did not see its source so I can not know it

In my opinion, the best thing is to bring everything together into a single project
[Xposed General] robertogl:
It works only if integrated into the rom, or if it is installed at first boot...

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed General] SHAdowLOL:
How to clean Magisk img?
[Xposed General] shawnsnyderseedb:
Mine is working, and i dodnt install and forst boot nor is it integrated into my ROM.
[Xposed General] BlackSoulxxx:
New Magisk version with template v4 is coming and x86_64 build.
[Xposed General] alukarulz:
Wouldn't suggest to flash anything not coming from Rovo89. You will experience a lot of bugs. Flashing this will cause boot loop and you will lose data on unsupported devices, which is a lot. Rovo89's builds come stable right away. Wait. Be Paitent.
[Xposed General] robertogl:
It can work like that, depends on when android optimize the app. For 100% security you have to include this in the rom.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed General] nomisunrider:
Please read the details behind this by reading here: https://github.com/rovo89/Xposed/issues/230#issuecomment-315959127
[Xposed General] bigjackw:
hello ll group

after flash zip and clean dalvik-cache i get bootloop at boot system

i have RR-NG 5.8.3 nougat 7.1.2 (ARM)

can someone help me plz !!
[Xposed General] krishu_s:
Error
[Xposed General] EagleSoldier:
Waiting for uninstaller.

To many system bugs :(

Thank you anyway....

LOS 14.1 (7.1.2)
[Xposed General] BlackSoulxxx:
New Magisk version with error 1 fixed. No new template v4 yet, have to fix SDK detection.
[Xposed General] zenosteam:
Hi. Is it working on s'7 edge samsung rom

Envoyé de mon SM-G935F en utilisant Tapatalk
[Xposed General] just a bird xo:
Didn't get the error message but it says framework is not installed.

I confirmed it is enabled in Magisk (13.3).

Attempted to disable/enable but still the same results.
[Xposed General] rafaelbrunner:
I also got the exact same results here...

Magisk Module is enabled, and Xposed app says framework is not installed... :(
[Xposed General] Aldideos:
Not working... The module doesn't mount system.... Enabling auto-mount in the module folder the screen turn yellow, so there is something wrong...
[Xposed General] m_a_omar:
Any Solution for SDK 24 Please ?
[Xposed General] Xceeder:
Slightly off topic but I need this question answered - hey buddy I'm using the latest resurrection remix on oneplus 3 and I was told to always use the latest twrp by bluspark to avoid problems but with multirom the twrp is a few versions behind what I'm using does it not matter which twrp you use or would using the twrp for multirom be fine ??
[Xposed General] weigeloveu:
ye me too

通过我的 LEX820 上的 Tapatalk发言
[Xposed General] SacredDeviL666:
+1

first the OP claims/states that Xposed is a work of others contribution which isn't, its clearly a one man contribution by rovo89 then he says he will give his name as credit just to be happy where in it should have been only his name.

then this race of releasing WIP stuff to public without even checking the basics and it took almost 3 to 4 post of yours to understand he is messing with an outdated template.

https://www.xda-developers.com/xposed-android-nougat-support/

worst part is that he/she has done nothing but to compile someone else's work and not even acknowledge it correctly!
[Xposed General] alsys:
PMP module crashing and making others apps to crash
[Xposed General] teddy0209:
As suggested, it's better to use the latest twrp... You can always flash multirom twrp back if you need it to manage roms...
[Xposed General] unknown:
Here is some review of me on this xposed version :

+ Not stable like [MENTION=6992457]ErnyTech[/MENTION] ( although build from same source ( as two guys credit to same github link in first post ) )

+ After flash , install apk , it is show not installed xposed in xposed apk .

---------- Post added at 02:10 AM ---------- Previous post was at 02:07 AM ----------

It is same to you ( as first post of you and him credit to same github link )

But your version is more stable and working fine .

So i think we should make your project as the main project :D:D:D
[Xposed General] andreMusers:
working on rr or based rom aosp, not for based stock
[Xposed General] EagleSoldier:
When u like to uninstall the framework:

Uninstaller for LP/MM worked perfect for me.

Android 7.1.2 - ARM 64 - LOS 14.1

I had bad issus with some system apps after install this framework :/

Will wait for Rovos Version :)

Best regards
[Xposed General] Didgeridoohan:
+1 :D

It's not about the community for some, just the "fame".

Now I'm mainly browsing these new threads and eating popcorn...
[Huawei P9 Lite Questions & Answers] ut0mt8:
So I finaly soft bricked my p9 lite trying to dual sim it.

I think the situation is not that bad.

Quick recap :

- My phone is VNS-L31 (europe)

- I have access to twrp (venus version)

- My phone is unlocked and FRP unlock

- I have access to Fastboot rescue mode (and fasboot devices -l show it)

So what the best way ? I'm a bit lost with terminology.

I suppose I have to download a full stock firmware (but from where and what version ??)

I suppose I also have to complety wipe my old system ? (twrp make error on this ?)

Should I try an update.app with erecovery or flash directly partition by partition ?
[Huawei P9 Lite Questions & Answers] k1ll3r8e:
Heyho,

if u have a system which can boot into the TWRP recovery:

1) make sure which Android version u currently run (MM / N)

2) get u a oeminfo matching to the version u want end in (for example: L31C432B130_DS)

3) flash the oeminfo via TWRP u can use my toolkit to do so

4) boot into the bootloader (fastboot mode)

5) flash the stock recovery matching to ur current kernel (MM / N)

(the recovery is included in my toolkit packages, otherwise u need to get u the "Huawei Update Extractor" here on XDA and extract the recovery from the update.app)

6) copy the FULL-L31C432Bxxx update.app on ur sdcard/internal storage (dload folder)

(!IMPORTANT! - The oeminfo must match to the update! This means, u can flash a B130 oeminfo and a B160 rom. But, u can't flash a B130 rom over an B160 oeminfo!)

7) turn the device off and disconnect it from any USB connection

8) turn the device on with the following combination:

Press and hold [Vol+ Vol- Power] until u see the huawei recovery

9) wait until the update is done

If u can't boot into TWRP:

1) turn ur device off - plug the USB cable in

2) press and hold [Vol- Power]

3) unlock ur device with my toolkit, the code can be requested by huawei (a link is in my toolkit)

4) flash the TWRP recovery matching to ur current kernel (MM / N)

5) follow the previous steps above from (1)

Hope i could help u ;)

Regards,

Sebastian
[Huawei P9 Lite Questions & Answers] ut0mt8:
So I flash the oeminfo with dd found on your google drive.

It seems it relock my phone. So I suppose I have to unlock it again with ./fastboot oem unlock xxxxx ?

I put a stock B160 on root on the sdcard (/sdcard/dload/UPDATE.APP). VNS-L31C432B160.zip.

In fact I cannot go to huawei recovery (hold power +UP+Down) nor Twrp ; I always finish on erecovey (which it not very helpful)
[Huawei P9 Lite Questions & Answers] k1ll3r8e:
Heyho,

Np ;)

-

About the recovery, u should use the TWRP from [MENTION=4960686]OldDroid[/MENTION] from my signature, i can confirm that this recovery will work as it should.

Hehe, u "only" wiped the system, data not the boot partition, the boot.img contains the kernel and ram-disk. But, an N kernel can't boot an MM recovery, also the MM kernel can't boot an N recovery.

Yes and no, the oeminfo is 64 mb not 32 mb!

Just use:

adb shell su -c "dd if=/sdcard/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"

Because, each oeminfo dump will be exactly 64 mb so there is no need to set the size.

To flash the recovery u should use fastboot...

fastboot flash recovery /path/to/the/recovery/image

As described in the preparation, this is only to get the device back to work, that u can boot into the TWRP and do all the stuff i just tell u...

I don't use the TWRP u mentioned, maybe there is an issue... I had a look on my device with the TWRP from OldDroid, there are those block-devices... But i had a look under "/dev/block/platform/hi_mci.0/by-name". I think, if u have a look at this path, u'll find the block-devices also on ur device.

Yup, if u saw a PW-prompt where u entered a random or ur last known PW, the device will normally do a factory-reset.

As u mentioned, u can unlock it with

fastboot oem unlock UR_UNLOCK_CODE

again.

About the recovery, which recovery u flashed? (The L31C432B130? it's MM and can't boot with an N kernel...)

Just download the "pkg.L31C432B380.zip" from my g-drive and flash the stock recovery from this package, it's an N recovery.

Hope everything is now working for u ;)

Regards,

Sebastian
[Huawei P9 Lite Questions & Answers] ut0mt8:
OK so I ve re unlock my phone, and flash the recovery with your twrp version. Still have the problem with

mount: mounting /vendor on ext4 failed: No such file or directory
mount: mounting /product on ext4 failed: No such file or directory
mount: mounting /usbotg on auto failed: No such file or directory

but let's move on.

If I understand correctly I have now a good oeminfo, a boot with nougat kernel and initramfs/initrd.

I have to flash the recovery with stock recovery nougat in order to flash an old B130 update.app.

Let's try.

PS : bs paramater in dd mean how much data your write at each pass (it's an optimisation parameter don't needed here)
[Huawei P9 Lite Questions & Answers] k1ll3r8e:
Heyho,

hmm, maybe the partitions are not formatted... - Just proceed with the update, normally it will flash those partitions. I had a similar issue a while ago.

About the "bs", it's meant as "block-size"? If so, the normal block-size for the oeminfo will be "4096" :p

Regards,

Sebastian
[Huawei P9 Lite Questions & Answers] ut0mt8:
Yep It means blocksize but in fact it is just pass to the read/write system call ; so you can virtually pass every value (even a size greater than the image file; in that case dd/system will try to read it in one pass). This is no alignement related.

Another quick question : did you know a method to break the boot loop and enter fastboot mode ?

Normally you have to shutdown your device but in that configuration I have no option (unless draining the battery).

I think I succeed one time with a precise timing but not sure.
[Huawei P9 Lite Questions & Answers] k1ll3r8e:
Heyho,

thx for the info ;)

-

About the boot-loop, u can try to long press Power until it turn off and on again.

Just hold the device connected to USB, that's important to enter fastboot!

Just try to:

1) power off

2) and when it's off, hold Vol-

that should be enough to enter fastboot.

Regards,

Sebastian
[Huawei P9 Lite Questions & Answers] ut0mt8:
Effectively with phone connected to usb it work much better ;)

So I correctly install the stock recovery , and push an UPDATE.APP, the recovery launch and found the package but it hold at 5% and does nothing more.

I think I had to flash all partition more violently. Let's try.

What really help was if something can look at a correct partition scheme for /vendor an /product; coz I think my problem came from here.

Thks.
[Huawei P9 Lite Questions & Answers] k1ll3r8e:
Heyho,

just disconnect the device while the update... This is normal and mentioned a lot of times... That when the device is connected to USB the update will fail at 5%, why ever.^^

-

I wiped my device yesterday ~20++ times and flashed all the time back to B130 so i can promise u that this will work...

oeminfo + stock recovery + update = 100% B130

Regards,

Sebastian
[Huawei P9 Lite Questions & Answers] ut0mt8:
OMG it's finally working ! and dual simed !!

Big thks for your patiente with noob like me.

There still a lot of things I had to dig/understand (I will try to flash twrp again and check for my partition issue)

I will now try to make a quick howto with my notes.
[T-Mobile LG G3] weirdzombie_21:
Hi there everyone!

There is a service called "com.google.provision".This service is always running in background.Should I remove this service.How can i remove that service?

Device:

G3 D851 (4.4.2 Rooted)
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] AWESOME1092387456:
As quoted from this thread: https://xdaforums.com/verizon-galaxy-s5/development/toshiba-11-series-bootloader-unlock-t3349346

"Our chip is the THGBMHG7C1LBAIL I believe" I begun searching for some sd cards that might use it and my guess is that these sd cards might have the same eMMC chip on them:

http://www.toshiba-memory.com/cms/en/products/microsd-cards/hs-standard/

~and~

http://www.toshiba-memory.com/cms/en/products/sd-cards/hs-standard/

This is what i found on Toshiba's documantation of the emmc controller:

https://toshiba.semicon-storage.com/info/docget.jsp?did=12587
[Google Pixel Accessories] mikeprius:
I'm on my second skin for the Pixel from dbrand. I was wondering if anyone else had issues with the corners ? The fitment I'd say for the skin is about 95% accurate. Once you start from the bottom and roll it over slowly it fits for the most part. There are some half millimeter offsets around the sim card tray and buttons, but that's not a huge deal. The issue I have had twice are the corners. My last skin, the top corners had issues. This most recent one, it was one bottom and one top. Some areas almost seem like the skin has to even be stretched ever so slightly to fit. For example, the bottom where you start fits fine, but I had to tug it several times to stretch it to fit the camera 100% perfectly. If I did not it would have been slightly off. The sides are also ever so slightly off and I could not tug it b/c I'd have to set one side down to pull. I speculate the skins are cut 100% accurate, but since it goes on top of the phone, there is some slight shortage. For example, if you made a case for a phone, it may give a bit to fit snug, but when the skin if you just roll it over you'll see it.

Overall it looks fine, I think the first skin I had fit better due to the fabric being more pliable and I'd say both skins came out about 95% and quite frankly its not noticeable unless I point it out., but I was wondering if others ran into the same issue.
[Google Pixel Accessories] Onknight:
I can't even get any now shipped to canada
[Google Pixel Accessories] ebbbz:
Yeah I bought one....great stuff but its like you said the corners and around the sim area it's not a perfect fit but its manageable and not too bad...but I also switch between covers and the constant pulling in and out of the phone made the sim area of the skin to peel off and now it just sits there like loose skin.
[Android Q&A, Help & Troubleshooting] _Edward_:
Please can we get twrp recovery for c5000zhu1aqc5.I don't install xposed I need twrp recovery.
[Android Q&A, Help & Troubleshooting] AACH:
I was unable to find any working custom recovery for the current C5000ZHU1BRA1 or any reliable method to root this version. Please, anybody, post a reliable root method.
[Android Q&A, Help & Troubleshooting] kalicyh:
I have a twrp that can use for samsung galaxy c5000

I have a twrp that can use

I'm a chinese

my QQ is：1353859364

Email：1353859364@qq.com

my English isn't very good
[Android Q&A, Help & Troubleshooting] _Edward_:
https://youtu.be/t_PvSxLE4-8

It is working
[Samsung Galaxy S8 Questions and Answers] Snowby123:
Do you think making Xposed compatible with this device will be as difficult or more difficult than it was for the S6?