yashsingh1/xdaforums huggingface dataset:
[Xposed General] moejay90:
Did you try flashing root zip file after updating in fastboot mood?

---------- Post added at 01:56 PM ---------- Previous post was at 01:56 PM ----------

Did you try flashing root zip file after updating in fastboot mood
[Xposed General] scarline:
Not yet.

Will this make a difference? I start with stock. Flash Root. Flash Exposed. Update Rom. Both Lost. Than again flash Root? Does this make sense? Feels like turning circles...
[Xposed General] moejay90:
Ok you can try to update rom in fast boot, and then boot into recovery the flash root, then boot up, then back again and flash xposed.
[Xposed General] scarline:
I did this. NFC Loop like before!

Only thing that worked was flashing xposed ---> factory reset. But I am loosing root due to this process. When I flash afterwards with superSU AGAIN NFC loop....
[Xposed General] moejay90:
Just a double check, once you are in recovery go to mount and make sure system isn't ticked.

---------- Post added at 02:15 PM ---------- Previous post was at 02:11 PM ----------

Ok, so you are only losing root, can you check where is xposed zip file located and your root zip file located at? Also make sure your system partition isn't ticked on Mount options.
[Xposed General] scarline:
superSu is automaticly mounting /system during the flash process. Does this setting in mount-options have an effect? Should it be disabled for flashing xposed and supersu?

---------- Post added at 03:20 PM ---------- Previous post was at 03:18 PM ----------

They are located in the same directory on internal space. Is this relevant for the effect of the re flashing of system.img?
[Xposed General] moejay90:
It needs to be off so that you don't lose root, superSu automatically mounting can be your obstacle, do it manually and disable it.
[Xposed General] scarline:
The mounting is shown in the shell promt. No sure if one can influence that? Currently Iam re flashing the xposed..... Now I got 57 apps optimized. This is an indicator for things working..... But I dont understand whats the reason that it does not work in the first run but in the second/third,,,, it di not work again, multiple FC...
[Xposed General] moejay90:
Let's wait for optimization to finish and see what happens, please keep captures for any errors you encounter so we are on the same lane throughout this issue.

---------- Post added at 03:01 PM ---------- Previous post was at 02:54 PM ----------

Btw which zip are you flashing first? Root.zip or xposed.zip? Flash root.zip first then wipe cache dalvik, then xposed.zip again wipe cache dalvik then restart system.

---------- Post added at 03:06 PM ---------- Previous post was at 03:01 PM ----------

Let's wait for optimization to finish and see what happens, please keep captures for any errors you encounter so we are on the same lane throughout this issue.

---------- Post added at 03:01 PM ---------- Previous post was at 02:54 PM ----------

Btw which zip are you flashing first? Root.zip or xposed.zip? Flash root.zip, wipe cache dalvik then restart system, then flash xposed.zip, then wipe cache dalvik then restart system.
[Xposed General] scarline:
I flashed normally this way. I also tried to wipe before and afterwards.
[Xposed General] moejay90:
And when you install each separately and wipe, what happens?
[Xposed General] grep_i:
I think I do not understand what you are trying to say why would you reflash it after factory reset, reflashing the complete rom is the same as factory reset.

Factory reset or stock rom firmware reflashing is the same and with both methods you loose Supersu and custom recovery.

So yes after this methods you must always reflash custom recovery and Supersu.

I really do not understand this. It does not matter if your root is systembased or systemless a factory reset wipes everything except "/sdcard" so basically what you say about this is a litte bit ridiculous.

A rom that has Supersu included has it in the rom pre placed in the right location so what does this have to do with what you are saying this ain't factory resetting because it is a custom rom in the first place.

Phones usually does not come from the factory with custom roms from independent developers but with stock roms that are built by the manufacturer. Resetting your phone to the rom from the manufacturer is called factory resetting not installing flashing custom rom.
[Xposed General] zelendel:
That is because you are not understanding just what a factory reset does. It does not reset the device to the factory rom. IT also doesnt completely wipe those partitions either.

And installing an OEM rom after using a custom rom is not factory resetting either. It is flashing Stock.
[Xposed General] Fen-X:
I died laughing reading this. you'r more crazy than me.
[Xposed General] grep_i:
Maybe following makes you understand better. This is specifically about Nexus devices:

Maybe your claim is true for other devices, on Nexus devices doing factory reset your device will go back to the defaults from the factory rom it came with, except ofcourse if you upgraded your android version I am specifically talking about when you installed factory rom images since than it will not go back to the older version I guess. don't know for sure what happens if you update via OTA my guess would be factory resetting would still reset your phone to old version but this I never tested because I never update via OTA always though factory images. So yes every factory reset brings me back to the latest installed factory rom on my device.

If in any case the data is not wiped as intended I guess that something went wrong than(wipe all partitions). I've read an article on AndroidPIT about 2 or 1 months ago about this issue that it wouldn't wipe all partitions. But that was only tested with devices prior to Android 4.4 KitKat, so I don't know if it even affects Android 6.0 devices and especially if Google Nexus devices are vulnerable at all.

If you know more about this matter I really like to hear about this from you in detail.

Quote from the site of Google developers

https://developers.google.com/android/nexus/images

From the Google support site:

https://support.google.com/nexus/answer/4596836

Quote Wikihow

http://www.wikihow.com/Reset-Your-Android-Phone
[Xposed General] mielletseed:
You are really wrong! A "factory reset" just wipes /data and /cache, never /boot or /system. If it would do so you was "bricked". This is because without root this would be (almost) the "factory state". A "normal" root is installed in /system and will therefor survive every factory reset.
[Xposed General] moejay90:
You are absolutely correct, thanks for educating him.

---------- Post added at 06:23 PM ---------- Previous post was at 06:20 PM ----------

factory reset in case you have a custom rom doesn't make you lose custom recovery or root, cuz what we are talking about here is Custom Roms and not not stock roms. And btw even if you lose root with custom recovery installed, then in fact if you boot into recovery it would still boot into custom recovery, please Educate yourself before you offend people , we are not talking about stock roms here this is all about development, custom roms, root and custom recoveries. [MENTION=6952047]grep_i[/MENTION]
[Xposed General] grep_i:
Last time I checked this thread was about installing Xposed on Android marshmallow and as far as I know Xposed works the best on Android stock roms, cause with custom roms the variety is too big to code against as every developer can change every aspect of its rom at any time which is good if you like custom roms and having all kind of new gizmos in it. I think it's nice a lot of people here love custom roms and such, but not me. I love the stock Android and use Xposed to enable options that are not available in stock rom. While using stock rom I do not have issues with installing and using Xposed when I used custom roms in the past it was always troublesome. Although Xposed can work with a lot of custom roms a lot of developers of those custom roms will not support issues when they know you have Xposed installed. So I guess Xposed works the best on stock roms as they are the least moderated. Don't know why you're so overheated I was talking about Nexus 5 and stock rom and than you feel somehow the need to tell me I'm totally wrong and stays taking about something else and puts me out the equation although you're reacting on my post. So excuse me for saying that I was not talking about custom ROM but about stock rom in this thread. I really don't see how that is bad I guess we can talk about custom and stock rom in this thread don't you agree on that ?

---------- Post added at 07:44 PM ---------- Previous post was at 07:30 PM ----------

You really do know that /system is a subfolder of data so it is quite possible you can loose data in system it is not unthinkable
[Xposed General] scarline:
Hey guys, its kind of frustrating.... I am still not able to get a clean installation of exposed. It would be perfect when someone with real experience on this would give me some advice...
[Xposed General] moejay90:
You are right and I apologize if somehow I offended the matter was I was talking about custom ROM but you came along talking about stock ROM which caused the conflict.

---------- Post added at 08:32 PM ---------- Previous post was at 08:30 PM ----------

I understand your frustration, but please just provide a screenshot for me to look at it... Is it a code error if so then screenshot the code error you recieve cuz there is no way twrp would successfully flash your xposed or root successfully and then end up having an inactive xposed or unroot.
[Xposed General] scarline:
No, this is not correct. Factory reset in TWRP wipes data, dalvik, and cache partition. In case you 've got a systembased root it would not kill SU. But in marshmallow systemless is the "normal" way to go. SO whipping /data obviously takes your root away. Otherwise one needs a costumized boot.img on MM if I got in right to get it systembased.

Nevertheless I believe meanwhile that you 're right regarding the 2. flash-run. In the case the NFC error appears (evertime untill now), it is actually necessary to reflash system.img because this seems to trigger a full initialization of 60+ apps. Otherwise you'll get 20 apps initialized with will lead to FCs. After the reflash you will to have reflash supersup and exposed. But as mentioned now you get a full imitation. So I would conclude, You flash clean stock, flash recovery, flash supersu, flash xposed. Update rom -> Lose Xposes und super su > reflash both and finally got a working setup. Annyone else that can confirm that process?

---------- Post added at 09:38 PM ---------- Previous post was at 09:34 PM ----------

It says "Unfortunately, Nfc service has stopped" as described here https://www.reddit.com/r/xposed/comments/3yxn3k/help_unfortunately_nfc_service_has_stopped/ and here https://github.com/rovo89/Xposed/issues/128.
[Xposed General] moejay90:
Ok you are running nexus 6p stock Rom? If am correct did you to flash v80 instead of v79?

---------- Post added at 09:09 PM ---------- Previous post was at 09:09 PM ----------

Ok you are running nexus 6p stock Rom if am not wrong, you tried v79, have you tried v80?
[Xposed General] scarline:
Tried both.
[Xposed General] moejay90:
Ok, have you tried the same process in a custom rom since you are on stock?
[Xposed General] scarline:
No, but finally I made it. The trick is to do a factory reset after flashing xposed. Afterwards direct flash of super su again. Works like a charm.
[Xposed General] moejay90:
Great! Really happy for you man!
[Xposed General] scarline:
Thank you! It took a lot of trial and error. But I hope I can help someone a little bit on the way to get things working.
[Xposed General] cognitivedissonance:
Can someone please confirm that my thinking is correct in terms of appropriate framework versions? I'm particularly interested in verifying the proper selections for 6.x.x

I'm using a Verizon Galaxy S4 (which is ARMv7)

AOSP 5.0.x based ROM - Rovo89's ARM (SDK21) version

AOSP 5.1.x based ROM - Rovo89's ARM (SDK22) version

AOSP 6.x.x based ROM - Rovo89's ARM (SDK22) version EDITED - this one was incorrect -- I corrected it in my commment, below.

TouchWiz 5.0.x based ROM - Arter97's ARM (SDK21) version

TouchWiz 5.1.x based ROM - wanam's ARM (SDK22) version

TouchWiz 6.x.x based ROM - wanam's ARM (SDK22) version EDITED - this one was incorrect -- I corrected it in my commment, below.

Thanks!
[Xposed General] Nergal di Cuthah:
Any 6.x.x (as of this date those that have been thus far released which are 6.0 and 6.0.1) is SDK 23
[Xposed General] cognitivedissonance:
Thanks for the correction. I've updated the list, below (just a reminder for anyone who stumbles on this list: this list pertains to ARMv7 devices)

AOSP 5.0.x based ROM - Rovo89's ARM (SDK21) version

AOSP 5.1.x based ROM - Rovo89's ARM (SDK22) version

AOSP 6.x.x based ROM - Rovo89's ARM (SDK23) version

TouchWiz 5.0.x based ROM - Arter97's ARM (SDK21) version

TouchWiz 5.1.x based ROM - wanam's ARM (SDK22) version

TouchWiz 6.x.x based ROM - wanam's ARM (SDK23) version
[Xposed General] grep_i:
Wonderful, this is great news I'm so happy for you it finally works. Now you can fiddle around with some modules.
[Xposed General] grep_i:
Ok maybe you are right on a level of technicality bit still the intention of factory reset as the word says it all is bring the device back to the state as when it was just leaving the factory. (ready to make its journey to a reseller and from there to a customer).

If it does not do a good job through the options in settings app to factory reset, than I'm happy that I don't use that option.

I always do it by flashing

Factory Images for Nexus Devices

Because I am a noob I also call this factory reset. Maybe my way is more factory reset than doing it from within the settings app on your phone I guess but I don't know that for sure though.

So yeah to me factory resetting my way does wipe all except /sdcard or is this still not true ?

If I'm incorrect can you please provide me with information why this is not true and what does not get wiped when doing it my way, thanks in advance.

Does this still stands when flashing it as described above ?
[Xposed General] moejay90:
Guys a question which isn't Xposed Related, however am soo used to this forum and the people in it, here is the thing, am trying to change my boot animation, i downloaded the bootanimation that I want, named it as bootanimation.zip then renamed the stock bootanimation into bootanimation.zip1 and then I copied my custom bootanimation.zip into system/media and once I reboot no animation shows just a blank screen, any idea whats happening, am trying this on a rooted nexus 4 with custom rom (nitrogen OS) thanks!
[Xposed General] TNSMANI:
Let me also wade into this.

Warning! I am not technically sound. I am giving below what I have learnt from fiddling with the phone and from reading in XDA. If I am wrong please correct me so that I learn further.

A factory reset is only done by using the option in Settings. When it is done whatever ROM you are using is restored to the state when you/the OEM initially flashed it. That is if you are running the OEM ROM, then whatever version you are running at that moment is restored. If you are running a custom ROM, then the version which you are running at that moment is restored.

If you have flashed a custom ROM, by factory reset, the OEM ROM will not be restored.

Any other method of restoring a ROM, whether OEM or custom, is called flashing. This is the universal understanding of this process.

I am clear on this. The question is whether my understanding is correct.
[Xposed General] magnamentis:
you have to change permissions to 0644 like shown in the picture

[IMG="permissions"]http://xdaforums.com/attachment.php?attachmentid=3669831&stc=1&d=1457091620[/IMG]
[Xposed General] moejay90:
Thanks! However am using ES file explorer pro, is there a way to do it on that app if not then which app did you just show me the picture in?? Thanks alot!

---------- Post added at 12:03 PM ---------- Previous post was at 11:44 AM ----------

Found it and done it, but it's a no go! I tried 720 p and 1080 p but still not working? Any idea should I flash the file in custom recovery or what's going wrong?
[Xposed General] grep_i:
You could try and download an app in the Google Playstore and see if you can feed your bootanimation to the app and see if the app approves it.

Maybe you do not have the right dimension or color depth for an bootanimation ?

Is you picture a 5 part .png ?

Have you compared the original file with your file ?

What about your desc.txt if you have any ?
[Xposed General] moejay90:
Am not sure about that bro, its a zip that I downloaded, I haven't worked on the bootanimation myself, any idea what's the name of the app that I should try?
[Xposed General] grep_i:
Boot animation from JRummy or any other you can find
[Xposed General] moejay90:
Thanks man this helped! Actually the zip file itself can't be pushed to the app which means the problem is in the zip file itself. Thanks man
[Xposed General] pialletti:
Hello. I have a motorola moto x force. marshmallow 6.0 root. rom stock. selinux (permissive). Which version should I install? someone has already tested on motoxforce? thank you
[Xposed General] Fen-X:
You have to install xposed v80-sdk23 arm x64.

V80 is the lastest release of xposed framework, sdk 23 is dedicated to marshmallow and i think but not sure that s810 processor is a 64 bit arm
[Xposed General] xdvs23:
Qualcomm Snapdragon 810 is 64 bit (arm64 / armv8).
[Xposed General] grep_i:
You are almost right I guess.

A factory reset is also possible by booting to custom recovery and choose the option wipe, "Advanced Wipe" gives you the option to wipe even more partitions/volumes, option "Format Data" let you format partitions/volumes and let you even change filesystems if your rom supports it, see screenshot.

As the terminology is not very correct or clear to what it supposed to I created a third option which in my eyes is far more factory reset than the option in Settings.
[Xposed General] coconutxyz:
are you using the factory reset in recovery mode or the settings? so basically the step is flash stock>custom recovery>su>xposed>factory reset>xposed>su?
[Xposed General] zizon65:
hi guys,

i own a samsung galaxy S6E+ rooted and running Marshmallow 6.0.1, then i flashed xposed-v80-sdk23-arm64.zip with TWRP recovery booted and get stuck in a bootloop, any clue??????

Chers.
[Xposed General] grep_i:
Did you got wanam version from developer arter97 that one is the one made for Samsung devices, you can find it somewhere on this forum.
[Xposed General] zizon65:
am not sure bro, maybe thats why I got into bootloop! Now what to do for to recover normal as I haven't made any backup? Do I have to reflash a stock marshmallow rom, rooted and so one???

Regards.
[Xposed General] moejay90:
First try to wipe cache dalvik if it doesn't work then you need to wipe everything and start from scratch by flashing stock or any rooted custom rom, but with no back up made you lost all your data, but still you can recover from the bootloop :)
[Xposed General] grep_i:
It had an uninstaller try that it will fix you from boot looping but you won't have Xposed anymore
[Xposed General] bagarwa:
Could you please tell me the process of removing the systemless root and flashing the legacy root for Nexus 6P?
[Xposed General] DRatJr:
Thanks a bunch. I googled what architecture nexus 6 was and couldn't find this answer.
[Xposed General] ruuster13:
It's working on mine :D
[Xposed General] Nergal di Cuthah:
No worries, so did I two weeks ago when I got my phone. I used DuckDuckGo, with slightly better results (found an answer about half way down my search).
[Xposed General] phangu:
I didn't install it. Because I didn't flash framework successfully!
[Xposed General] Face_Plant:
On my Nexus 6 I did the following:

1. Uninstall SuperSU

2. Download SuperSU v2.52

3. Boot into TWRP

4. Flash SuperSU v2.52

5. Reboot

You will have to grant all of your apps root access again.
[Xposed General] kradkovich:
I

installed Xposed

on my

Nexus 6p

today and it all went fine until i needed to reboot to activate my modules. Thats when i bootlooped, any one know what might be the issue?
[Xposed General] TugBoatTed:
Certain modules cause bootloops. You have to install them one by one until you find the bad ones
[Xposed General] dark_knight_95:
Is the uninstaller zip working?
[Xposed General] Nergal di Cuthah:
Yes
[Xposed General] Face_Plant:
The systemless root isn't pointless. Say someone wants to use Android Pay, but they can't because the app detects SU binaries in /system. If they use the systemless root method the app won't detect the SU binaries and the user will be able to use Android Pay.

If you don't care about Android Pay THEN there's no point and you're better off using the tried and true method.
[Xposed General] Fuzzy13:
Working good on Chroma 6.0 Shamu. 77arm

Make sure you have all your modules uninstalled as they can cause the bootloop. Once Xposed is flashed, install your modules one by one to weed out the ones that don't work. If one bootloops, reboot into Twrp and remove the apk instead of reflashing the rom.

Modules that work for me.

Swype Tweaks

Clarity

Just weather

Lolistat

Hope this helps someone
[Xposed General] ldiomedi:
00:40:28.818 I/Xposed (11820): Found Xposed class de/robv/android/xposed/XposedBridge, now initializing 11-15 00:40:29.112 I/Xposed (11820): Errors during Xposed initialization 11-15 00:40:29.112 E/Xposed (11820): java.io.IOException: Permission denied while reading /data/data/de.robv.android.xposed.installer/conf/modules.list 11-15 00:40:29.112 E/Xposed (11820): at de.robv.android.xposed.services.ZygoteService.readFile(Native Method) 11-15 00:40:29.112 E/Xposed (11820): at de.robv.android.xposed.services.BaseService.getFileInputStream(BaseService.java:116) 11-15 00:40:29.112 E/Xposed (11820): at de.robv.android.xposed.XposedBridge.loadModules(XposedBridge.java:428) 11-15 00:40:29.112 E/Xposed (11820): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:102)

I'm having the error of permission denied while reading modules.conf. The Xposed Bridget is installed but it can't activated because that error. Any idea? Cm13 for Moto g 2013 (falcon)..
[Xposed General] bagarwa:
What about the angler-mdb08k-boot-systemless.zip that I had flashed earlier? Do I need to flash stock boot.img or angler-mdb08k-boot.zip or that doesn't matter?
[Xposed General] ddimple4:
Will v77 work on MRA58N for Nexus 5 or just MRA58K?
[Xposed General] tssphysicsboi:
Works for cm 13.
[Xposed General] nimkip:
Forewarning for anyone who wants to install on a Nexus Player, v77 causes a bootloop.
[Xposed General] tonyafc:
All good
[Xposed General] Face_Plant:
The systemless root kernel would probably still work, but I would flash the other modified kernel by Chainfire just in case. It's at the bottom of the first post of the following link:

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
[Xposed General] ijustwantaname:
Is systemless root a problem for xposed? (N6 here)
[Xposed General] siealex:
Can anyone get Xposed running on Nexus 5X? It throws errors in almost all apps both on stock and Omni.
[Xposed General] netinetinet:
xposed v78-arm64 work with Nexus 5X
[Xposed General] siealex:
Only v78?
[Xposed General] netinetinet:
I tried v80, v79 don't work.. v78 for me with 5X work
[Xposed General] siealex:
On pure stock ROM or on custom ROMs?

PS, where can I get v78? I don't see it in the official thread.
[Xposed General] netinetinet:
I am on Chroma rom
[Xposed General] siealex:
Is your data partition encrypted or not?
[Xposed General] netinetinet:
encrypted ....I sent you a link in private message..
[Xposed General] siealex:
Trying it on full stock...

PS, v80 works on non-encrypted partition.
[Xposed General] moejay90:
What are the errors you are getting? And is xposed active?
[Xposed General] siealex:
NFC service has stopped... Print spooler has stopped... etc. And I can't even reach the desktop.