Related
Hey guys,
Just wanted to know how many of you ditched the Xposed on marshmallow for the latest 7.1.1 Android based oxygenos?
Since we don't know when nougat will be supported by xposed, is staying on marshmallow worth it?
Even though most of the modules I use are more or less esthetical, there's one thing I can't live without - youtube background playback and ad block.
Share your thoughts!
Xposed over any OS without Xposed. I have never even flashed Nouget because I know its just a waste of time for me. Ive been on cm13 since the day it came out. DEC 11 2016.
If all you need is the youtube modules, there's modded youtube apps out now with adblock and background playback. Check it out here.
I've also packaged the app in a convenient Magisk module, which you can find here.
It works exactly like the xposed-modified YouTube app, but it works on Nougat.
Anova's Origin said:
If all you need is the youtube modules, there's modded youtube apps out now with adblock and background playback. Check it out here.
I've also packaged the app in a convenient Magisk module, which you can find here.
It works exactly like the xposed-modified YouTube app, but it works on Nougat.
Click to expand...
Click to collapse
Hey Anova, what is this Magisk thingy you're talking about?
Also... For me The most important is gravitybox then come youtube modules and mock mock locations.
You think it's worth the upgrade? I personally never had a phone that would get updates so quickly or even at all. So I have no idea what to expect.. Would I have to reroot, reinstall recovery or it's all a piece of cake and only the exposed won't affect anything? Lemme know.
Crishien said:
Hey Anova, what is this Magisk thingy you're talking about?
Also... For me The most important is gravitybox then come youtube modules and mock mock locations.
You think it's worth the upgrade? I personally never had a phone that would get updates so quickly or even at all. So I have no idea what to expect.. Would I have to reroot, reinstall recovery or it's all a piece of cake and only the exposed won't affect anything? Lemme know.
Click to expand...
Click to collapse
Magisk is a framework that allows you to make temporary changes to your /system partition at boot, without actually modifying the partition. It works by superimposing user-defined changes to files in /system during boot; changes are reverted to their stock state afterwards. These user-defined changes are loaded into Magisk through Magisk modules. While a lot of people may think it's similar to Xposed, they're really nothing alike. I mentioned Magisk for the YouTube app because it is merely convenient. You could manually replace the YouTube APK in system without any additional software, but Magisk will do it for you while applying all the correct permissions, etc. As a bonus, Magisk also includes its own rooting method that works, for the most part, as well as SuperSU. This means that you can flash only Magisk to root your phone (flashing SuperSU is optional and is really based on personal preference, Magisk will work with SuperSU if you flash that first).
Because of what Magisk is and how it works, it is not able to modify your device in the same way that Xposed can. This means that mods like gravitybox and mock mock locations cannot be implemented with Magisk. Technically, all Magisk modules can be installed without Magisk by manually editing/replacing things in the /system partition. What is special about it is that Magisk does these things systemlessly, meaning that (with the proper configurations), you can modify /system without triggering safetynet.
For the modified YouTube app I was talking about, that was actually modded and compiled as a stand-alone APK by someone on XDA. It does not alter your current YouTube app, but rather outright replaces it.
As for upgrading to Nougat, it's really up to personal choice. I personally never used Xposed for anything other than YouTube Adaway and Background Playback, and to top it off I rarely use YouTube on my phone anyways so upgrading was an easy choice for me. If you do end up wanting to upgrade, do the following:
1) Download the full ROM of whatever version of OOS you want to use (4.1.0 is the latest, on Android 7.1.1). Do not use the "Upgrade Phone" option in settings if you are already rooted or have modified anything in your /system partition, as it will cause problems.
2) Flash the full zip in TWRP, wipe cache/Dalvik, then immediately flash the latest Magisk.zip (from the main Magisk thread on XDA)
3) Boot, then download Magisk Manager from the Play Store
At this point, Magisk will have been fully installed and your phone should be rooted. You can confirm through the Magisk Manager app
Anova's Origin said:
Magisk is a framework that allows you to make temporary changes to your /system partition at boot, without actually modifying the partition. It works by superimposing user-defined changes to files in /system during boot; changes are reverted to their stock state afterwards. These user-defined changes are loaded into Magisk through Magisk modules. While a lot of people may think it's similar to Xposed, they're really nothing alike. I mentioned Magisk for the YouTube app because it is merely convenient. You could manually replace the YouTube APK in system without any additional software, but Magisk will do it for you while applying all the correct permissions, etc. As a bonus, Magisk also includes its own rooting method that works, for the most part, as well as SuperSU. This means that you can flash only Magisk to root your phone (flashing SuperSU is optional and is really based on personal preference, Magisk will work with SuperSU if you flash that first).
Because of what Magisk is and how it works, it is not able to modify your device in the same way that Xposed can. This means that mods like gravitybox and mock mock locations cannot be implemented with Magisk. Technically, all Magisk modules can be installed without Magisk by manually editing/replacing things in the /system partition. What is special about it is that Magisk does these things systemlessly, meaning that (with the proper configurations), you can modify /system without triggering safetynet.
For the modified YouTube app I was talking about, that was actually modded and compiled as a stand-alone APK by someone on XDA. It does not alter your current YouTube app, but rather outright replaces it.
As for upgrading to Nougat, it's really up to personal choice. I personally never used Xposed for anything other than YouTube Adaway and Background Playback, and to top it off I rarely use YouTube on my phone anyways so upgrading was an easy choice for me. If you do end up wanting to upgrade, do the following:
1) Download the full ROM of whatever version of OOS you want to use (4.1.0 is the latest, on Android 7.1.1). Do not use the "Upgrade Phone" option in settings if you are already rooted or have modified anything in your /system partition, as it will cause problems.
2) Flash the full zip in TWRP, wipe cache/Dalvik, then immediately flash the latest Magisk.zip (from the main Magisk thread on XDA)
3) Boot, then download Magisk Manager from the Play Store
At this point, Magisk will have been fully installed and your phone should be rooted. You can confirm through the Magisk Manager app
Click to expand...
Click to collapse
Thanks for such a detailed description of everything! You're the best! I seriously decided to upgrade tomorrow.
Just last couple questions before I do... Should I delete anything? Like xposed itself with it's modules, or does the system upgrade wipe everything itself? Should I perform any backups other than usual titanium ones?
Thanks in advance
Crishien said:
Thanks for such a detailed description of everything! You're the best! I seriously decided to upgrade tomorrow.
Just last couple questions before I do... Should I delete anything? Like xposed itself with it's modules, or does the system upgrade wipe everything itself? Should I perform any backups other than usual titanium ones?
Thanks in advance
Click to expand...
Click to collapse
You should delete the Xposed modules prior to updating, as they are saved as user apps and will not be wiped with an upgrade. Delete the Xposed framework app as well for the same reason. Updating should erase all of the background stuff that the Xposed originally installed in /system. Take a nandroid prior to updating just in case.
Anova's Origin said:
You should delete the Xposed modules prior to updating, as they are saved as user apps and will not be wiped with an upgrade. Delete the Xposed framework app as well for the same reason. Updating should erase all of the background stuff that the Xposed originally installed in /system. Take a nandroid prior to updating just in case.
Click to expand...
Click to collapse
Thanks again, mate!
Is this the one I should download? https://forum.xda-developers.com/oneplus-3t/how-to/rom-oos4-0-nougat-op3t-leaked-t3523482
Crishien said:
Thanks again, mate!
Is this the one I should download? https://forum.xda-developers.com/oneplus-3t/how-to/rom-oos4-0-nougat-op3t-leaked-t3523482
Click to expand...
Click to collapse
Yes, that will work. OnePlus has not yet released the official zip through their website at this time, otherwise I would advise you to use the official zip.
Anova's Origin said:
Yes, that will work. OnePlus has not yet released the official zip through their website at this time, otherwise I would advise you to use the official zip.
Click to expand...
Click to collapse
Great, thank you. Imma let you know how it goes later today.
Anova's Origin said:
Yes, that will work. OnePlus has not yet released the official zip through their website at this time, otherwise I would advise you to use the official zip.
Click to expand...
Click to collapse
Not sure if I did anything wrong or I'm just impatient... But I flashed the update successfully and deleted dalvik. But got stuck at boot logo. Been hanging like this for 15 minutes, phone got hot and drained half its juice. So I reverted for now.... I'll try again at home with a charger... ?
954wrecker said:
Xposed over any OS without Xposed. I have never even flashed Nouget because I know its just a waste of time for me. Ive been on cm13 since the day it came out. DEC 11 2016.
Click to expand...
Click to collapse
what can xposed do that you actually need that you can't do with magisk?
EuEra said:
what can xposed do that you actually need that you can't do with magisk?
Click to expand...
Click to collapse
I don't think magisk can handle what xposed can handle.
954wrecker said:
I don't think magisk can handle what xposed can handle.
Click to expand...
Click to collapse
Indeed I will miss gravitybox. But if there is any other way to make my buttons do what I like which is (on the left - menu button with double tap for previous app/ home is home and recents on long press / right is back.)
Other than that it's all purely visual enhancement such as perfect color bar, media visualizer, and ****.
On the other hand I've just encountered a slight difficulty... Magisk won't work properly if I had Supersu previously installed, right?
Crishien said:
Indeed I will miss gravitybox. But if there is any other way to make my buttons do what I like which is (on the left - menu button with double tap for previous app/ home is home and recents on long press / right is back.)
Other than that it's all purely visual enhancement such as perfect color bar, media visualizer, and ****.
On the other hand I've just encountered a slight difficulty... Magisk won't work properly if I had Supersu previously installed, right?
Click to expand...
Click to collapse
What are you gaining if I may ask? I have never tried 7.0 or magisk because I see ZERO benefit and Id lose all my favorite modules.
954wrecker said:
What are you gaining if I may ask? I have never tried 7.0 or magisk because I see ZERO benefit and Id lose all my favorite modules.
Click to expand...
Click to collapse
That's what I wanna find out. I wanna see what's the new Android about. And I'm sure rovo will find a solution soon. And we will see xposed for nougat.
GravityBox is terrible and has slowed down every phone it's ever been put on (from my experience).
Xposed is a hack and it's shameful how it's holding back advancement.
Nougat > any hack
MattBooth said:
GravityBox is terrible and has slowed down every phone it's ever been put on (from my experience).
Xposed is a hack and it's shameful how it's holding back advancement.
Nougat > any hack
Click to expand...
Click to collapse
My phone is just as fast with xposed as it is without. All my apps work perfectly so I say any OS with Xposed is > Nougat
954wrecker said:
I don't think magisk can handle what xposed can handle.
Click to expand...
Click to collapse
Most of that is either completely unnessecary, pointless, or magisk can do it if people start developing for it. I have none of it (except no ads on youtube and the ability to turn off the screen) and i am completely fine. I think you tell yourself you need all that stuff but you actually don't, staying versions behind on the OS for it seems stupid.
954wrecker said:
My phone is just as fast with xposed as it is without. All my apps work perfectly so I say any OS with Xposed is > Nougat
Click to expand...
Click to collapse
Well that's your opinion and you're entitled to it, but I've noticed the total opposite across several devices. I always try Xposed on a new phone and I always massively dislike the way it works. Intercepting code that was not supposed to be intercepted just adds overhead. There's a good reason AOSP devs will refuse to look at any bug report that has Xposed in the logs.
EDIT:
Anyway, the battery savings from Nougat are too good to pass over. The only thing I need to customise on my phone is having the Google Dialer, and AdAway, whilst still keeping SafetyNet as passing, which Magisk does perfectly.
EuEra said:
Most of that is either completely unnessecary, pointless, or magisk can do it if people start developing for it. I have none of it (except no ads on youtube and the ability to turn off the screen) and i am completely fine. I think you tell yourself you need all that stuff but you actually don't, staying versions behind on the OS for it seems stupid.
Click to expand...
Click to collapse
Exactly, unless you use every setting on GravityBox then it's not entirely necessary, yet even if those functions are off or there are features of GravityBox you don't use, their code is still run. The bigger it gets the more the overhead there is. If you don't use, say, the network speed monitor, it's hook is still active. I could be wrong, but last time I dabbled with Xposed, this was the case.
If anything, smaller more granular modules would be better for GB. One module for network speed. One module for changing the on-screen buttons, etc. That way you only install modules that you use, rather than a whole library of them where you might only use 2-3 of the actual features.
@topjohnwu
I'm sure you've read the google+ message or the post on the front page in regards to Chainfire stopping development on all current root-related apps. This includes thus SuperSU (which was sold to CCMT a long time ago and they did absolutely nothing with) and FlashFire (which i use to flash an OTA and keep root intact.
Now with that in mind, magisk is pretty much the only root solution now and i'm starting to look into it. I've already installed the manager and will flash the stock rom at a later point. First a question.
What would be the proper way to flash an OTA (on my 6P, for as long as it will get them) and keep magisk root intact? (i know my way around ADB a bit and twrp, usually i ADB BOOT the latter, not install it). Has anyone tried the latest magisk with flashfire on a 6?
I'll appreciate your input.
Regards,
Ch3vr0n
I'm also interested in getting OTAs installed while preserving root and magisk, on my Pixel XL. I can't get it working properly using the suggested method from @topjohnwu
May i suggest you make your own topic then? It will do neither of us any good of replies to our issue get lost in replies to the other
I did already.
I just showed that I am interested in a proper solution as well. I have not asked specifically about my issue, but wanted to tell you that the "official" way (which is well documented) doesn't work for some users (it's not only me).
yeah but you have a completely different device. So what's not working for you, isn't even relevant in case. Thanks for the interest though
and a quick bump.
Ch3vr0n said:
Has anyone tried the latest magisk with flashfire on a 6?
Click to expand...
Click to collapse
Hopefully you're aware that you can no longer even purchase FlashFire on the Google Play Store, so it's not a solution going forward...
Who said that was a problem. I've been using pro since day 1. Pro users don't have the time issue and it works just fine.
Sent from my Nexus 6P with Tapatalk
OTA installation tips (from the official Magisk docs):
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
I know that A/B device users have been reporting negative results with the documented method, but fortunately it's not applicable in this case.
Have seen a bunch of reports of Flashfire not working properly with later release of Magisk, but can't confirm since I've never used it.
That leaves the last described method. Should always work, but by then I usually feel it's a lot easier to just use fastboot to flash the latest factory image...
I have some phones with Magisk, and are not A/B devices. Magisk gets lost after the OTA, I just reflash it, reinstall the 4 Magisk modules I use, and open each app that requires root so I can grant root access to them again. Of course, add to Hide the banking and other apps that need it. Not too much trouble for me, even if I usually receive weekly OTAs. Wish I could save the Superuser and module settings of Magisk before flashing, then I can just restore it.
At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.
Use Magisk I guess? Use it to hide root from that app.
Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.
ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs
Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?
I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).
ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...
Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid
Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?
After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...
probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.
Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.
So I got my pixel 4XL a month after it came out I instantly unlocked the bootloader but only until last night when I was going to re-lock it I decided to give Magisk a whirl.
So I downloaded the May update and I patched it with the Magisk Manager and finally have room Can someone of you tell me what I can do if my phone's rooted A long time ago what I would do if I had root was just get a customer recovery and make backups and flash new ROMs.
So when I'm in the Magisk Manager and in the top left corner there's a hamburger menu and one of the options is downloads Can I download any one of those or are those for every phone and some of them at some of them might not work for the Pixel 4 XL?
I want Magisk Hide to hide me and allow me to use Google pay and possibly Netflix.
Last thing that I can think of off without my head is is there any way that I can make backups like I could in TWRP so that if I've installed a module that sends me into a blue loop etc I can just reload my recovery because I'm assuming some modules and exposed units will break a blue my device and I don't want to start from scratch
GokuSSJgod said:
So I got my pixel 4XL a month after it came out I instantly unlocked the bootloader but only until last night when I was going to re-lock it I decided to give Magisk a whirl.
So I downloaded the May update and I patched it with the Magisk Manager and finally have room Can someone of you tell me what I can do if my phone's rooted A long time ago what I would do if I had root was just get a customer recovery and make backups and flash new ROMs.
So when I'm in the Magisk Manager and in the top left corner there's a hamburger menu and one of the options is downloads Can I download any one of those or are those for every phone and some of them at some of them might not work for the Pixel 4 XL?
I want Magisk Hide to hide me and allow me to use Google pay and possibly Netflix.
Last thing that I can think of off without my head is is there any way that I can make backups like I could in TWRP so that if I've installed a module that sends me into a blue loop etc I can just reload my recovery because I'm assuming some modules and exposed units will break a blue my device and I don't want to start from scratch
Click to expand...
Click to collapse
No custom recovery at the moment and don't hold your breathe. If a module sends you into a boot loop you can disable all modules in ADB with "uninmod -d" just make sure you have USB debugging always enabled with a trusted computer when using Magisk modules.
GokuSSJgod said:
So I got my pixel 4XL a month after it came out I instantly unlocked the bootloader but only until last night when I was going to re-lock it I decided to give Magisk a whirl.
So I downloaded the May update and I patched it with the Magisk Manager and finally have room Can someone of you tell me what I can do if my phone's rooted A long time ago what I would do if I had root was just get a customer recovery and make backups and flash new ROMs.
So when I'm in the Magisk Manager and in the top left corner there's a hamburger menu and one of the options is downloads Can I download any one of those or are those for every phone and some of them at some of them might not work for the Pixel 4 XL?
I want Magisk Hide to hide me and allow me to use Google pay and possibly Netflix.
Last thing that I can think of off without my head is is there any way that I can make backups like I could in TWRP so that if I've installed a module that sends me into a blue loop etc I can just reload my recovery because I'm assuming some modules and exposed units will break a blue my device and I don't want to start from scratch
Click to expand...
Click to collapse
Many modules in that section are universal (fit for any device) but some are device-specific. It's best to do research/reading on what you're thinking of installing, before doing so.
If you run into issues, there's a core-only boot image you can flash (found in themes/apps/mods section of this forum) to boot your device with all modules disabled, so you can delete the offending module.
There also may be a way to remove modules via adb, but again, you're going to have to do some research.
For flashing ROMs, you don't necessarily need Magisk. ROMs are flashed through adb sideload in normal recovery since we don't have TWRP.
I personally use Magisk for custom fonts, dozing Google Play Services, BusyBox, Viper4Android and ad blocking.
For making backups, I use an app called Swift Backup, available on the Play Store. It backs up all your apps + app data, and SMS texts, and call logs. It can also backup WiFi networks.
Hope this helped.
dave5777 said:
No custom recovery at the moment and don't hold your breathe. If a module sends you into a boot loop you can disable all modules in ADB with "uninmod -d" just make sure you have USB debugging always enabled with a trusted computer when using Magisk modules.
Click to expand...
Click to collapse
Thanks
rickysidhu_ said:
Many modules in that section are universal (fit for any device) but some are device-specific. It's best to do research/reading on what you're thinking of installing, before doing so.
If you run into issues, there's a core-only boot image you can flash (found in themes/apps/mods section of this forum) to boot your device with all modules disabled, so you can delete the offending module.
There also may be a way to remove modules via adb, but again, you're going to have to do some research.
For flashing ROMs, you don't necessarily need Magisk. ROMs are flashed through adb sideload in normal recovery since we don't have TWRP.
I personally use Magisk for custom fonts, dozing Google Play Services, BusyBox, Viper4Android and ad blocking.
For making backups, I use an app called Swift Backup, available on the Play Store. It backs up all your apps + app data, and SMS texts, and call logs. It can also backup WiFi networks.
Hope this helped.
Click to expand...
Click to collapse
I know I could search for the answer but I like you now than the search bar lol.
But where do you find the custom fonts exactly
And the mods for dozing Google play services how much extra battery do you get and is that in thevMagisk Manager? If so what's it called and how do you do it and if it's not there where you find it? What's the point of busy box and viper for Android is something to do with sound and we assume
If you don't want safety net surprises don't use exposed, it's red more than times than it's green
GokuSSJgod said:
I know I could search for the answer but I like you now than the search bar lol.
But where do you find the custom fonts exactly
And the mods for dozing Google play services how much extra battery do you get and is that in thevMagisk Manager? If so what's it called and how do you do it and if it's not there where you find it? What's the point of busy box and viper for Android is something to do with sound and we assume
Click to expand...
Click to collapse
Fonts are from the user Tulsadiver in the Themes and apps section.
How much extra battery is subjective, depends on so many other things as well which can be different from me (i.e. screen brightness, how many apps you have installed, different apps from me, cellular network strength, what features are enabled/disabled, etc.)
But overall I'd say it's just a small increase in battery, not anything drastic.
BusyBox is required for some other root apps. If you don't run into any apps asking for BusyBox, you may not need it.
Yes Viper is to increase sound quality, a guide to install it can be found in this forum as well!
I apologize if this is a noob question. I haven't rooted since Pixel 2, so it has been close to 6 years and I am not very aware anymore about Magisk. I can probably find videos regarding how to install Magisk and root, but my question was with its use of LSposed and Pixelfy Google photos.
The Pixel 5 and older have free photo storage, and I assume this module spoofs the type of phone and makes it think it is a Pixel and gives free photo storage.
I have a phone I am not using but it is not rooted yet and something I am considering.
I have been also checking various threads and there is mixed feedback on this particular module.
Does anyone use the Pixelfy free photo storage ? It looks like it needs to be used with Magisk and LSposed to get it to work ? Some threads it looks like it works, others have been commenting that it is bricking and causing problems. If it is unreliable or bricking, then I'll just see if I can buy and older pixel but thought I'd ask here first. Thanks.
mikeprius said:
I apologize if this is a noob question. I haven't rooted since Pixel 2, so it has been close to 6 years and I am not very aware anymore about Magisk. I can probably find videos regarding how to install Magisk and root, but my question was with its use of LSposed and Pixelfy Google photos.
The Pixel 5 and older have free photo storage, and I assume this module spoofs the type of phone and makes it think it is a Pixel and gives free photo storage.
I have a phone I am not using but it is not rooted yet and something I am considering.
I have been also checking various threads and there is mixed feedback on this particular module.
Does anyone use the Pixelfy free photo storage ? It looks like it needs to be used with Magisk and LSposed to get it to work ? Some threads it looks like it works, others have been commenting that it is bricking and causing problems. If it is unreliable or bricking, then I'll just see if I can buy and older pixel but thought I'd ask here first. Thanks.
Click to expand...
Click to collapse
If you mean this LSPosed module, then yes, I use it on 3 of my devices and it works perfectly.
And yes, it requires to be rooted with Magisk and to have LSPosed framework installed.
Lord Sithek said:
If you mean this LSPosed module, then yes, I use it on 3 of my devices and it works perfectly.
And yes, it requires to be rooted with Magisk and to have LSPosed framework installed.
Click to expand...
Click to collapse
Hi yes I believe this is it. So in order to have unlimited Google photo uploads, I need to first root, have magisk, download lsposed, then download this module separately?
I have a pixel 6a. Has there been any issues with Google halting or finding out about the spoof and blocking it?
mikeprius said:
Hi yes I believe this is it. So in order to have unlimited Google photo uploads, I need to first root, have magisk, download lsposed, then download this module separately?
I have a pixel 6a. Has there been any issues with Google halting or finding out about the spoof and blocking it?
Click to expand...
Click to collapse
Yes...there is actually two methods Pixelify goes about this; they either spoof the Pixel 5 (which is the latest Pixel Google will allow unlimited uploads but at "Storage Saver" lowered quality on the photos and videos) or the original Pixel(1) [which is the original and only Google Pixel left that Google allows unlimited uploads in original quality]. So you would need to decide which method you are willing to try and do...
But yes, you'd have to unlock the bootloader (which wipes the device), root with Magisk, install the LSPosed Magisk module, then run that Unlimited Google Photo app (or Baltiapps Pixelify GPhotos as it's officially named) which will then install the LSPosed module "separately".
I've already spoken a bit on this, so I will just quote what I said before (things to consider and risks involved) as well as you can click on the quote to go to the post/thread and see how the discussion developed there;
simplepinoi177 said:
I wouldn't make this claim with such certainty. Spoofing a Pixel phone is definitely against Google's Terms and Conditions. Doing this for years may have worked out since Google was offering it from Pixel 2-5 in Storage Saver capacity, but it's been 2 years since the Pixel 5 was released, and as time goes on, it's less realistic that Pixel's before 6 would still be in use, yet there would be all these accounts still backing up using the unlimited storage feature. ESPECIALLY if (like me, to be guilty of) there are many who are spoofing the Pixel 1 to get it unlimited WITH original quality -- being the first Pixel is 7 years old; highly unrealistic that so many people should still be using the phone to be taking photos and videos off of.
My point is that, no one using this "trick" should completely rely on it and expect Google to "play along" indefinitely about it. Like I've been saying, at best, Google will just plug in the loophole and close the feature down; at worst, they remove any photo or video that were taken under a particular Pixel model when your google account shows it being connected to another device altogether and/or they suspend a google account outright using the exploit -- this is highly unlikely, but is still in the realm of possibility and is as I said worst case.
I, myself, back my photos and videos from my Pixel 7 Pro using this spoofing trick, but I will also back all my media up (when my device is full) on a physical medium just in case.
Click to expand...
Click to collapse
P.S. Also, since you are out of practice in rooting, there is an excellent tool that streamlines most anything to do outside of stock experience on the Pixels (bootloader unlocking, rooting, flashing and/or updating Full Factory images or OTAs [to either both or inactive slots], flashing custom ROMs, other recovery checks and protocols, advanced apk install or apk/app disabling [system, stock], it might even be able to flash custom kernels but I can't be too sure) which would be able to accomplish what your aims are pretty much with a single click (outside of clicking where your factory images are and what not)....
simplepinoi177 said:
Yes...there is actually two methods Pixelify goes about this; they either spoof the Pixel 5 (which is the latest Pixel Google will allow unlimited uploads but at "Storage Saver" lowered quality on the photos and videos) or the original Pixel(1) [which is the original and only Google Pixel left that Google allows unlimited uploads in original quality]. So you would need to decide which method you are willing to try and do...
But yes, you'd have to unlock the bootloader (which wipes the device), root with Magisk, install the LSPosed Magisk module, then run that Unlimited Google Photo app (or Baltiapps Pixelify GPhotos as it's officially named) which will then install the LSPosed module "separately".
I've already spoken a bit on this, so I will just quote what I said before (things to consider and risks involved) as well as you can click on the quote to go to the post/thread and see how the discussion developed there;
P.S. Also, since you are out of practice in rooting, there is an excellent tool that streamlines most anything to do outside of stock experience on the Pixels (bootloader unlocking, rooting, flashing and/or updating Full Factory images or OTAs [to either both or inactive slots], flashing custom ROMs, other recovery checks and protocols, advanced apk install or apk/app disabling [system, stock], it might even be able to flash custom kernels but I can't be too sure) which would be able to accomplish what your aims are pretty much with a single click (outside of clicking where your factory images are and what not)....
Click to expand...
Click to collapse
Thank you for the information. So before the way I used to root was I would use adb then type fastboot img then the TWRP file.
Then reboot and now I have custom recovery TWRP. This is of course after I have unlocked the bootloader which wiped.
I assume this is still the case where oem unlock is checked in developer options then sdb fastboot flashing unlock?
I briefly used magisk by topjohnwu but it was new back then and I sort of didn't keep up with it.
If there is a program or different method is it possible to point me to it? I honestly can remember what to do after booting TWRP.
Regarding the spoofing, the standard upload of the pixel 5 is fine for me and you mentioned some good points regarding Google potentially catching on. At the time banking apps didn't care if you were rooted but I think they do not work anymore if you are.
Also I thought I read somewhere, lets say I just flash a custom rom instead and don't use the pixel OS, will this be automatically for this module without having to do anything extra? It reminds me of when all custom roms had free Hotspot tethering built in so you didn't need to do anything extra.
I also don't mind flashing a custom rom and using it as a dedicated backup device either. Just exploring options
Thanks for the starter info. I just realized how long it has been and I don't recognize anything anymore.
mikeprius said:
Thank you for the information. So before the way I used to root was I would use adb then type fastboot img then the TWRP file.
Then reboot and now I have custom recovery TWRP. This is of course after I have unlocked the bootloader which wiped.
I assume this is still the case where oem unlock is checked in developer options then sdb fastboot flashing unlock?
I briefly used magisk by topjohnwu but it was new back then and I sort of didn't keep up with it.
If there is a program or different method is it possible to point me to it? I honestly can remember what to do after booting TWRP.
Regarding the spoofing, the standard upload of the pixel 5 is fine for me and you mentioned some good points regarding Google potentially catching on. At the time banking apps didn't care if you were rooted but I think they do not work anymore if you are.
Also I thought I read somewhere, lets say I just flash a custom rom instead and don't use the pixel OS, will this be automatically for this module without having to do anything extra? It reminds me of when all custom roms had free Hotspot tethering built in so you didn't need to do anything extra.
I also don't mind flashing a custom rom and using it as a dedicated backup device either. Just exploring options
Thanks for the starter info. I just realized how long it has been and I don't recognize anything anymore.
Click to expand...
Click to collapse
I also had a Pixel 2 XL (taimen) for 3 years -- upgraded to the Pixel 5 -- so I am familiar with the method you are familiar with.
Unfortunately, that is no longer how it works. It sucks, but TWRP could never catch up after Android 10 -- it would take so long for them to develop that once they finally got TWRP to work with Android 10, Android 11 was released and became the new established version; then once they finally got it compatible with Android 11, Android 12 released and the same thing. So, as I understand it, TWRP does work in a limited capacity for Android 12, but it will not work for Android 13 (yet); and it seems if history repeats itself, it might not get there by the time Android 14 releases...
So still using magisk, but you can't "install" magisk from a .zip like you could with TWRP.
It's not that much more complicated than flashing Full Factory images or temp booting from a recovery image -- you simply extract the init_boot.img from the Full Factory image, "run it through" the Magisk app and get it patched that way, then flash the patched image the same way you flash the recovery partition (from the TWRP image) to permanently install/flash the custom recovery.
But, if you are still wary about going about all of this and/or if you are out of practice and unsure, please consider badabing2003's PixelFlasher. It basically does all of that stuff, but puts a GUI and automates it all for you -- as well as doing certain checks and protocols to make sure things aren't done wrong or buggy/incompatibly. It's as close to "one-click" as anyone's gonna get for the Pixels...
PixelFlasher will guide you to downloading the Full Factory image (or OTA if you wish that way), Magisk, the right platform-tools version (the least buggy version), i believe it can unlock the bootloader (but I could be wrong), and root or Full Factory update for you.
Hope this helps!
Lord Sithek said:
If you mean this LSPosed module, then yes, I use it on 3 of my devices and it works perfectly.
And yes, it requires to be rooted with Magisk and to have LSPosed framework installed.
Click to expand...
Click to collapse
Please, after installing how can be used?
Thanks!
amplatfus said:
Please, after installing how can be used?
Thanks!
Click to expand...
Click to collapse
after installing the module, the module actually installs an app (which can be found in the app drawer) under "Pixelify GPhotos". Running the app should give you all the settings and options you need to get it to work/"be used" -- it even has a button to force-close Google Photos to reset it to detect the spoofing. Just be sure you have all modules enabled (LSPosed[within Magisk], Pixelify GPhotos[within LSPosed]).
I've assisted a bunch of users/members where they had to play around with the configurations a bunch to finally get it to work for them; for whatever reason, one configuration works for one user but not the other -- my configuration did not work for some of them and they had to enable certain settings to get it to work for them (even though we are using the same device).
simplepinoi177 said:
after installing the module, the module actually installs an app (which can be found in the app drawer) under "Pixelify GPhotos". Running the app should give you all the settings and options you need to get it to work/"be used" -- it even has a button to force-close Google Photos to reset it to detect the spoofing. Just be sure you have all modules enabled (LSPosed[within Magisk], Pixelify GPhotos[within LSPosed]).
I've assisted a bunch of users/members where they had to play around with the configurations a bunch to finally get it to work for them; for whatever reason, one configuration works for one user but not the other -- my configuration did not work for some of them and they had to enable certain settings to get it to work for them (even though we are using the same device).
Click to expand...
Click to collapse
Hi thank you for all your help. I currently have the pixel 6a now and will get the 7a but probably keep the 6a as a dev device. Once I unlock the bootloader, I will try the pixel flasher and go from there. Good to know about TWRP but if there is a newer and better way I am all about experimenting with that as well. I may give it a run over the summer.
Once I download pixel flasher and install magisk, so I go to gitgub and download lsposed then install pixelfy as a module separately?
Unlock bootloader -> pixel flasher->magisk->Lsposed-> Pixelfy?
Thanks and salamat po
mikeprius said:
Hi thank you for all your help. I currently have the pixel 6a now and will get the 7a but probably keep the 6a as a dev device. Once I unlock the bootloader, I will try the pixel flasher and go from there. Good to know about TWRP but if there is a newer and better way I am all about experimenting with that as well. I may give it a run over the summer.
Once I download pixel flasher and install magisk, so I go to gitgub and download lsposed then install pixelfy as a module separately?
Unlock bootloader -> pixel flasher->magisk->Lsposed-> Pixelfy?
Thanks and salamat po
Click to expand...
Click to collapse
Once [you] download pixel flasher and install magisk,...go to [github] and download LSPosed (zygisk version), then install Pixelify GPhotos (Baltiapps version, not original kingsman44) LSPosed module as a module separately (in LSPosed).
It will then install a companion app which you can set the settings and options....
But yes, "Unlock bootloader -> pixel flasher->magisk->Lsposed-> Pixelfy?" looks right; just keep in mind that unlocking bootloader wipes device, and use Pixelify Baltiapps and not kingsman44's.
Glad to help!