Related
Hello, just looking for some clarification if possible before I destroy my device!
So I currently have a T-Mobile Galaxy Note 3 (SM-N900T) that has been towel rooted on kitkat 4.4.2 and then flashfire'd to the latest stock Lollipop 5.0 firmware available for my device to keep root.
I have also FlashFire'd the latest unofficial xposed framework for samsung lollipop 5.0.x by dkcldark and I do not have TRWP, or any custom recovery.
As far as I understand xposed is not compatible, or at least probably not the one im using. I'm willing to sacrifice it and go with Magisk for its ability to hide root from apps if at all possible.
I believe the root I have is not systemless. I also believe the t-mobile note 3 has an unlocked bootloader. Though I'm not 100% positive.
Edit: Final note, within Magisk Manager ... it says I am "Properly Rooted, with 2.82:SUPERSU"
So now on to the questions:
1. If I uninstall my current xposed framework and download Magisk Manager, can I successfully install Magisk and accomplish "hiding root/by passing safetynet" from apps on my device that is currently rooted probably via system without a custom recovery?
2. Will Knox also stay un-tripped at 0x0? Or since the boot.img will be modified, this would be tripped? Even though I did not use a custom recovery, or kernal at all?
Appreciate the replies XDA! Thanks.
I just replaced SuperSU with Magisk in my Galaxy S4. So, to answer your questions.
You'd have to replace SuperSU with MagiskSU in order to enable the hide feature. I don't think Towelroot is usable with Magisk, and since there is no CF-Autoroot for Magisk you'd have to install a custom recovery, which will - if I'm not mistaken - trip Knox. At this point in your Note 3's lifespan, the last thing I would be worrying about is Knox, as your warranty on the device is no longer extant.
So using the Magisk Manager app to install Magisk while on my rooted device without a custom recovery will not work and itself replace SuperSU with MagiskSU while keeping knox 0x0?
I was under the impression if you were pre-rooted u could use Magisk Manager, and it would replace the current root with Magisks. And also that it detects if you have a systemless root or not. Installing itself into the system if that's the type of root you had, otherwise systemlessly.
While yeah my device is no longer under warranty, It's just my own personal preference to preserve it.
custom recovery will trip knox... Magisk needs a custom recovery to install the framework as mentioned
i do understand your preference about maintain knox untripped...
do you really use it? (knox app... It was discontinued .... Samsung official press release ... and I did received a email about it)
or intend further sell your device as "original" at eBay? it's a joke...
imho ... knox at this point is a good security sandbox.... but there is alternative ways to secure your apps and personal/professional data...
If install a custom rom nougat flavour and Magisk performance device will increase It... lookup at note 3 devs thread
best regards
Enviado de meu Lenovo A7010a48 usando Tapatalk
Alrighty thanks for the info!
I do not currently use it, but I also don't use Samsung Pay ... and don't really *need* to play Pokemon go, or Super Mario Run... I'll keep my phone rooted, xposed framework, latest firmware, knox 0x0 for now and possibly consider tripping the knox flag at a later time. Assuming no new "root hide" work-around becomes available and based on future safetynet blocked apps.
The SM-N900T is still a very great device... Additional SD Card slot, removable battery, 3 gigs of ram, 32 gigs space, 2.3GHz Quad-Core CPU, 1080p 5.7" Full HD Super AMOLED® screen.
I see no reason yet to upgrade the phone even being about 4 years old now.
I do remember something like a "safe" custom recovery was for the note 3 line, I have used it on my note 3 from Verizon when I had it.
Just see if you can use it, and flash Magisk with it, unless it is obsolete as it may be was replaced by flashfire?
Sent from my Nexus 6P using XDA Labs
Strephon Alkhalikoi said:
I just replaced SuperSU with Magisk in my Galaxy S4. So, to answer your questions.
You'd have to replace SuperSU with MagiskSU in order to enable the hide feature. I don't think Towelroot is usable with Magisk, and since there is no CF-Autoroot for Magisk you'd have to install a custom recovery, which will - if I'm not mistaken - trip Knox. At this point in your Note 3's lifespan, the last thing I would be worrying about is Knox, as your warranty on the device is no longer extant.
Click to expand...
Click to collapse
Which Custom Rom do you use? I currently cant find a good one to root with magisk (also S4)
Well, my S4 isn't my daily driver anymore, so I threw a stock-based ROM on it: MachineX. That ROM however uses MicroG, so I had to modify an OpenGApps package to remove the MicroG components and replace them with proper Google ones.
If you're still using your S4, use an AOSP 7.1.2 ROM instead. Less hassle, and runs better.
Magisk hide hides the KNOX status. Simply replace SuperSU to MagiskSU.
Deic said:
Magisk hide hides the KNOX status. Simply replace SuperSU to MagiskSU.
Click to expand...
Click to collapse
That it does but I've yet to see anyone successfully use S Pay/Pass after tripping Knox, with or without Magisk.
Strephon Alkhalikoi said:
and since there is no CF-Autoroot for Magisk you'd have to install a custom recovery, which will - if I'm not mistaken - trip Knox.
Click to expand...
Click to collapse
Sure, CF Autoroot does not trip Knox?
But Chainfire says so here: "If you have a KNOX-enabled device, using CF-Auto-Root will trip the KNOX WARRANTY VOID status !" :crying:
@ThemGo: You got me. I must have been drinking when I mentioned CF AutoRoot. The point I was trying to make to the original poster about Knox was that there was no way to keep it at 0x0 if installing Magisk.
But, were you that bored that you had to hunt through a five month old post?
I rooted, just the Magisk patched boot image, nothing more. Installed adaway, which is the reason for rooting.
I marked Google Pay as hidden in Magisk hide. That was all it took on the OG Pixel XL. Not so with the 4 XL.
Any thoughts on how to get Google Pay to step in line?
Ivanstein said:
I rooted, just the Magisk patched boot image, nothing more. Installed adaway, which is the reason for rooting.
I marked Google Pay as hidden in Magisk hide. That was all it took on the OG Pixel XL. Not so with the 4 XL.
Any thoughts on how to get Google Pay to step in line?
Click to expand...
Click to collapse
Search for the Gpay Magisk patch. There is actually a couple methods that get you there but the patch is the most automated.
Thanks! I was able to make that work. Appreciate the help.
Updated to Android 12 and now the GPay doesn't work.
Stock ROM, Cleanslate kernel, no root. Is there a fix? Or do I need to relock the bootloader?
Hi! You will need to root with Magisk and use safetynet fix module. I am affraid that other way doesn't exist with unlocked bootloader...
This doesn't work with the new google pay. For the official android 12 you have to use magisk canary and there is no more magisk hide. They've gone to whats called the deny list. There isn't even a section to view safety net status on the new magisk canary build. I'm on a rooted pixel 4 with official android 12 and I can get every other banking and money app i use to work fine but just not google pay. Google is looking for disabled verity and verification and for unlocked bootloader status. Even if you don't have root, just the fact your bootloader is unlocked will not let google pay to work.
Magisk alpha on T
It works with Pixel 3XL on Android 12. Root / install Magisk, enable SafetyNet (https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/), add Google Pay to deny list and that's it. No SQL hack required...
Search 'google pay' within thread in the link if you're unsure how to set everything up.
This fixed my 4 XL which is running Android 12 November 2021. Been racking my brain the past two days trying to figure out how to get GPay working since upgrading two A12. I NEVER carry my cards, I'd die without GPay.
All I needed was Canary, the newest SafetyNet and to hide GPay.
No SQL hack BS required here either.
Side note, A12 sucks. The layout looks like it was designed for a 70-year-old that has bad vision. I see I'm not the only one that shares these thoughts though, Google's forums and Reddit are littered with people complaining about the same thing.
This may be the first time in history and I'd been a Nexus and Pixel owner for years, I may downgrade back to a previous version of Android, it's THAT bad.
.
updated Android 12 on motorola edge 20 .. rocks .. all smooth good experiance
google pay DOWN
unlocked bootloader .. my OEM UNLOCKINg is greyed out so i didnt root
researched SHIZUKU but doesnt allow me to (use google pay)
strange thing . BANK MILLENIUM has activated my NFC functionality so i can pay in store
WE DONT NEED GOOOGLE PAY ... i just need to get REVOLUT WORKING SAME WAY
The new Magisk is here and with it some major changes. One of the most important is the removal of support for "MagiskHide". There are many advanced users who have figured this all out already and few (maybe more) like me who are just kind of lost not knowing what should be exactly done to be able to update and be able to use Magisk as they were, before the update.
I was hoping that a kind soul would put up an easy step by step guide to help these users and at the same time it will avoid a lot of repetitive questions on the main thread. I personally spent a long time reading many pages and was not able to fully understand what should be done.
In my case all I want to achieve is to update and be able to hide Magisk like it was in the previous version. Should I start by un-hiding it first before doing the update?
(what and how and from where) should I add something that will replace the hiding function? Viola! these are the kind of simple questions that will help some of us get going
I hope that someone will bring his precious help
Yeah I unfortunately did my upgrade and fought with the whole process for 6 hours straight (lol) and I still don't know what I did exactly to even begin to write any instructions - other than 6 hours straight of reading and trying and hoping .....
Not sure if you have been able to refer to this which helped me.... But, I also have an very basic understanding of how my device (OnePlus 7T) works with Magisk... Hope this helps. May be see if your specific device has the instructions already posted in the device specific forum here?
Installation
The Magic Mask for Android
topjohnwu.github.io
I've not used the Magisk hide cause I haven't needed it - BUT, it's still available in the latest Magisk Manager (24.1) in the Magisk Manager settings. I'm only using the systemless hosts module (included in Magisk manager settings) for Adaway, and the universal safety net fix to get Google Play store to say my device is certified.
But I don't know what device you have nor do I know the specific ROM you are using.
Sounds like you have root already so I'm thinking that's the worst of this behind you if you've already done that much yourself. Sounds like it's a basic case of update the Magisk Manager app from itself then determine the method appropriate for root to update which could be through the Manager app or like I chose to use the boot IMG then patch that then install since my device has no working TWRP. That, and once I updated the manager app and panicked so I uninstalled it to try and downgrade to v23 .... Good luck and may be just don't update just yet if there is no specific need to at this time. Take your time and read and proceed when comfortable.
Please:
Start with your preferred method of backing up everything first.
Also, may be consider if it's necessary to update and why??? I'm on stock Andriod 11 and this Magisk update make me think it's intended to be more for those on Android 12 - but I could also assume wrongly.
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
That's the thread I'm reading now...
Thanks a lot for your reply wugga3. I also on my side found two very helpful posts. They explain the basics (just to get started) and to make the update . I hope with the information gathered I will be able to do the update without messing things up!
[Discussion] Google Pay Magisk Discussion Thread
This thread is inspired by the PoGo Magisk discussion thread. It's meant to keep the clutter of "Google Pay doesn't work" posts out of the main Magisk threads. Please use this to discuss issues with Google Pay and possible solutions. There's a...
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Good and good luck...
One problem and probably the only problem I really had was self inflicted for not following the instructions properly and that was to uninstall any Magisk modules first or at that the appropriate step.
Other than that... still don't know your device or rom etc. Your device specific or rom specific forums may be able to provide you with much better assistance from members that have the same rom/device as you.
wugga3 said:
Good and good luck...
One problem and probably the only problem I really had was self inflicted for not following the instructions properly and that was to uninstall any Magisk modules first or at that the appropriate step.
Other than that... still don't know your device or rom etc. Your device specific or rom specific forums may be able to provide you with much better assistance from members that have the same rom/device as youI
Click to expand...
Click to collapse
I am using LineageOS 18.1 Android 11 for Samsung Galaxy Note 3 and I have twrp as recovery. Magisk 2.30 is already installed and device is rooted. I have no modules installed and in Magisk settings I have only MagiskHide enabled. All other settings are set to default. On Samsung Note3 forum there is no talk about this (understandable as the device is very old).
Ok great and is there any discussion for lineage 18.1 and root/update?
Since it's lineage 18 and based on Andriod 11 - I have to wonder if there is even the need to update Magisk as my limited understanding is that the Magisk update is aimed at Andriod 12? Other than that... I should expect from my prior understandings of Samsung that nothing much has changed with respect to root and updates of Magisk. Not much help but hopefully enough. May be best to wait until for now and usually I do also wait until all the facts are in and the bugs are sorted out (if any...) before I update if unnecessary.
Thanks wugga3,
I disabled "Check for updates" in Magisk app and decided to keep the older 2.30 version for now. Everything is working fine and so there is no reason to fix something which is not broken. The only reason I thought That I should update was a real advantage over the older version or a security weakness being fixed in the new one.
I am even seeing some people asking for help on how to downgrade! Anyway as you said wisely, it;s not after all a bad idea to wait a little to see how things work out for those who have upgraded and have new issues fixed before taking the jump.
Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot (Magisk) to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want
mingkee said:
Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want
Click to expand...
Click to collapse
Thanks a lot for your post mingkee,
I am sure many like me will be happy and appreciate reading this instead of having to go through many pages and still not be totally sure what to do
Allow me to just ask one question as I did not understand the second option of your instruction:
I update Magisk from the application itself. Once updated what do you mean by update boot to 24.1? This is to be done in Magisk itself?
rezpower said:
Thanks a lot for your post mingkee,
I am sure many like me will be happy and appreciate reading this instead of having to go through many pages and still not be totally sure what to do
Allow me to just ask one question as I did not understand the second option of your instruction:
I update Magisk from the application itself. Once updated what do you mean by update boot to 24.1? This is to be done in Magisk itself?
Click to expand...
Click to collapse
After updated app to 24.1, you will see another update on top of the app (Magisk). Direct install would be the simplest method
mingkee said:
Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot (Magisk) to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want
Click to expand...
Click to collapse
this should be pinned somewhere, very simple and worked fine on my Poco F3 using miui.eu & android 11
thanks a lot
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!