pokemonGo not working after root - Google Pixel XL Questions & Answers

Hey does anyone know a way to make PokemonGo work after rooting the phone? Any help is appreciated

Sorry, but as soon as they blocked root, it became a dead game. I don't think root cloak even works nor does xposed framework. Also Nougat doesn't have xposed yet so yeah...

I haven't played PokemonGO in a long time however I'd suggest you try some of the following options:
1. Try toggling root off from SuperSU and see if it works
2. See if AutoMagisk can help if hiding root access of the app. There's plenty of tutorials out there on how to work with it.
3. You can wait until someone mods (unless someone has already done so) the .apk for use with root (and still have multiplayer / internet capabilities), which I highly doubt since the game is kinda dead.

I love how Pokemon go is "dead" already.
We have the attention span of a teaspoon

asaqwert said:
I love how Pokemon go is "dead" already.
We have the attention span of a teaspoon
Click to expand...
Click to collapse
I believe he was referencing that the game was dead to him since they blocked rooted users. It is dead to me as well, if they wouldn't have blocked root, then I still would be playing. My wife doesn't play anymore because I cannot play.

enmajo said:
I haven't played PokemonGO in a long time however I'd suggest you try some of the following options:
1. Try toggling root off from SuperSU and see if it works
2. See if AutoMagisk can help if hiding root access of the app. There's plenty of tutorials out there on how to work with it.
3. You can wait until someone mods (unless someone has already done so) the .apk for use with root (and still have multiplayer / internet capabilities), which I highly doubt since the game is kinda dead.
Click to expand...
Click to collapse
Supposedly Magisk works for hiding root from pokemon go however from what i have seen Magisk doesnt support the pixel yet because of the changes with the file system.

absolutely nothing can bypass this dame root detection of you have a unlocked bootloader! its annoying. i used to like this game but not i cant play. unless your talented on how to make a special boot.img you cant get around this

xdarkmario said:
absolutely nothing can bypass this dame root detection of you have a unlocked bootloader! its annoying. i used to like this game but not i cant play. unless your talented on how to make a special boot.img you cant get around this
Click to expand...
Click to collapse
Those posts were from November... It's easy to get around root detection now, and you don't need a "special boot.img."
A) suhide + Root Switch + custom kernel that hides unlocked bootloader flag. In fact, I have a whole write up on it here.
B) Flash the same ROM to both boot slots + only root one of them + custom kernel that hides unlocked bootloader flag. Enter TWRP to reboot to other slot when you want to switch.

fiveighteen said:
Those posts were from November... It's easy to get around root detection now, and you don't need a "special boot.img."
A) suhide + Root Switch + custom kernel that hides unlocked bootloader flag. In fact, I have a whole write up on it here.
B) Flash the same ROM to both boot slots + only root one of them + custom kernel that hides unlocked bootloader flag. Enter TWRP to reboot to other slot when you want to switch.
Click to expand...
Click to collapse
i have just realized that this forum is for the google pixel (i followed a link here) my phone is a xiaomi redmi 3s. But is some way i can maybe incorporate this to work for me?

xdarkmario said:
i have just realized that this forum is for the google pixel (i followed a link here) my phone is a xiaomi redmi 3s. But is some way i can maybe incorporate this to work for me?
Click to expand...
Click to collapse
This only works for us because of the pixels A/B partition layout. If you have multirom support you could probably do something similar though.

Related

Newbie! Zenfone 2 now rooted...now what!

Hi all,
I have a zenfone 2 that I have just rooted....so now what?
Basically I wanted to optimise my phone so I am able to disable annoying notifications which are greyed out (although since rooting and checking this it still greyed out) I want to remove bloatware and I would actually like to customise my own android system, starting from a 'vanilla' base where I can build it up myself.
I have also read that I need to install a android recovery programme on asap after rooting.
So sorry about this but I really do need 'stupid' instructions as using hi tech words will just baffle me. lol
I have played around with computers in the past and learned about them so this is the phone stage now!
Thanks in advance and for your patience with this newbie!
Kerry
Yankeegal said:
Hi all,
I have a zenfone 2 that I have just rooted....so now what?
Basically I wanted to optimise my phone so I am able to disable annoying notifications which are greyed out (although since rooting and checking this it still greyed out) I want to remove bloatware and I would actually like to customise my own android system, starting from a 'vanilla' base where I can build it up myself.
I have also read that I need to install a android recovery programme on asap after rooting.
So sorry about this but I really do need 'stupid' instructions as using hi tech words will just baffle me. lol
I have played around with computers in the past and learned about them so this is the phone stage now!
Thanks in advance and for your patience with this newbie!
Kerry
Click to expand...
Click to collapse
Hi Kerry,
First thing you should now do after rooting your device would be flashing a custom recovery that is specific to your device (make sure your devices boot loader is unlocked first). This will allow you to make a backup of everything just in case anything were to go wrong, flash custom ROMs and useful zips. You can pick your favorite custom recovery such as Team Win Recovery Projects custom recovery (TWRP), Clock Work Mods custom recovery (CWM) or Philz Touch recovery based off of CWM although personally I would recommended twrp.
There are multiple ways to do this: Using the TWRP/CWM recovery installer from the play store or the more complicated way of flashing it from your computer. If you were to choose to install TWRP from their app on the play store (grant it root permission) you can select your device from the supported device section within the app, pick the latest recovery, hit the install button and let the app work its magic. If all works correctly you can now reboot to recovery and you will see TWRP is installed. Now you should create a backup to be on the safe side and you're good to go!
To best optimize your device I would recommend installing a custom ROM (look up custom ROMs for the Zenfone 2) and install the zip through recovery. (make sure to pick the right ROM for your device and version otherwise you may soft brick your smartphone) Now with a custom ROM you can better optimize your device and fully customize it to your liking. Make sure to look up custom ROM installation instructions for your device for better detail.
As far as removing system apps/bloatware you can use a "root app delete" tool from the play store but be careful what you remove as some applications are required!
Make sure to take your time and be careful when attempting any of these things and be careful what you modify! Just remember that no question is a stupid question as we all have to start somewhere!
Hope I was able to help you even if it was just a little, good look and have fun!
Rooted Droid Thanks you so much!!! First of all thanks for being so patient with me and secondly thanks for the useful (and easy to read) information.
I will go and install a back up on my phone from the ones you have suggested.
Hopefully you will be around over the next few days if I have more questions. Not planning on doing this all at once but rather taking the time and doing it right.
Thanks so much again!! :good::good::good:
Ooops sorry....how do I do this please?? ---> (make sure your devices boot loader is unlocked first)
Yankeegal said:
Rooted Droid Thanks you so much!!! First of all thanks for being so patient with me and secondly thanks for the useful (and easy to read) information.
I will go and install a back up on my phone from the ones you have suggested.
Hopefully you will be around over the next few days if I have more questions. Not planning on doing this all at once but rather taking the time and doing it right.
Thanks so much again!! :good::good::good:
Click to expand...
Click to collapse
Not a problem! I'm always happy to spread some knowledge and appreciate when people do the same to me! I also went ahead and checked the TWRP app and the Zenfone 2 is supported so it looks like your good to go. And yes absolutely, there's no rush so take all the time you may need and everything will go smoothly! I'm always around and will try my best to answer questions.
---------- Post added at 08:02 AM ---------- Previous post was at 07:41 AM ----------
Yankeegal said:
Ooops sorry....how do I do this please?? ---> (make sure your devices boot loader is unlocked first)
Click to expand...
Click to collapse
Check this site out:
http://myzen.asus.com/2015/10/13/official-bootloader-unlock-for-zenfone-2-is-now-available/
All devices have a different method for unlocking bootloader (some don't even have locked bootloaders) but this is an official bootloader unlocking method for the Zenfone 2 from Asus itself. I suggest following its directions and you should be able to unlock it this way.
Ok I followed the link but now I am confused. I have version ww_2.20.40.63_201......
Apparently I need a later version. What started off with just adding an APP means me doing other things before I even get to that point (hence the confusion! lol)
I never updated the phone via OTA as I was told it would invalidate my warranty and also I have killed a phone before using that so can you walk me through please...if you have the time....or could I just check if I have it unlocked already??
I haven't even gotten to the part where I create a backup...tee hee
Yankeegal said:
Ok I followed the link but now I am confused. I have version ww_2.20.40.63_201......
Apparently I need a later version. What started off with just adding an APP means me doing other things before I even get to that point (hence the confusion! lol)
I never updated the phone via OTA as I was told it would invalidate my warranty and also I have killed a phone before using that so can you walk me through please...if you have the time....or could I just check if I have it unlocked already??
I haven't even gotten to the part where I create a backup...tee hee
Click to expand...
Click to collapse
Hi sorry for the late reply, I'm in Canada so it was 2am when I was last talking to you so I went to bed haha. Anyway as far as unlocking the Zenfone 2's bootloader I wouldn't have experience unfortunately as I'm using a Nexus 5. The easiest way to go about this now would be to go to your device specific forum and find a way to unlock it there.
The following way to unlock the bootloader requires you have ADB installed on your PC. This is a guide for installation on Windows :
http://www.android.gs/install-android-sdk-adb-windows/
And here is a thread specific to unlocking the Zenfone 2 using adb:
http://www.xda-developers.com/asus-zenfone-2-bootloader-unlocked-without-asus/
BTW as you mentioned "updating may invalidate your warranty" things like rooting, installing a custom OS, unlocking the bootloader, installing a custom recovery and other things like that all (in most cases) void your warranty.
Sorry I can't personally help with the bootloader as I've not personally unlocked it on a Zenfone. Still feel free to ask any questions if you need to. Good luck!

any marshmellow roms?

i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
ncsuwolfs said:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
Click to expand...
Click to collapse
Sultanxda and Arter97 CM MM Roms are still up im sure you can find a few others too
Edit: Opps sorry thought was OP3 thread :laugh:
ncsuwolfs said:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
Click to expand...
Click to collapse
This phone launched with nougat. You can't run marshmallow on it.
liam_davenport said:
Sultanxda and Arter97 CM MM Roms are still up im sure you can find a few others too
Click to expand...
Click to collapse
where do i find those? (i have searched but can only find cm14 for pixel?
toknitup420 said:
This phone launched with nougat. You can't run marshmallow on it.
Click to expand...
Click to collapse
this is what i was afraid of....
ncsuwolfs said:
where do i find those? (i have searched but can only find cm14 for pixel?
this is what i was afraid of....
Click to expand...
Click to collapse
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
toknitup420 said:
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
Click to expand...
Click to collapse
I don't understand how it works but unless I misunderstood if you go to the official Magisk thread the creator claimed he was able to run Xposed with Magisk because his app prevented Xposed from needing to write anything to the system image. I supposed if you can't live without Xposed that would be worth looking into further.
There are no Marshmallow ROM's anywhere for this phone.
Never was, never will be.
Magisk isn't an Xposed replacement.
There is no replacement for Xposed.
Dammit, I miss my ~17 Xposed modules.
Most of which gave me options that you won't find on any custom Nougat ROM.
toknitup420 said:
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
Click to expand...
Click to collapse
It's a root option. As in you can run SuperSU or Magisk. Magisk has mods that can accomplish certain things that Xposed did but the majority of them don't work with the pixel so don't count on a suitable replacement.
jhs39 said:
I don't understand how it works but unless I misunderstood if you go to the official Magisk thread the creator claimed he was able to run Xposed with Magisk because his app prevented Xposed from needing to write anything to the system image. I supposed if you can't live without Xposed that would be worth looking into further.
Click to expand...
Click to collapse
The Magisk on pixel is supported by a guy that frequents the RR thread and he modded Magisk to work on the pixel so it's unofficial. Also there is NO Xposed for android n
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
CZ Eddie said:
Magisk isn't an Xposed replacement.
Click to expand...
Click to collapse
This isn't completely true. There are Magisk mods that overlap things that Xposed was capable of. So depending on what you are trying to do and IF mods even worked for the pixel. It could be a replacement for some.
The Magisk on pixel is supported by a guy that frequents the RR thread and he modded Magisk to work on the pixel so it's unofficial. Also there is NO Xposed for android n
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
Well that explains why on the official Magisk page the developer said he didn't know if there would ever be a working version for the Pixel phones but people are using Magisk anyway. Unfortunately Magisk seems to run into the same problems as SU on the Pixel in that it doesn't always install properly or maintain root if it does install--plus most Magisk modules don't work with the Pixel, which makes it much less functional than on other phones.
jhs39 said:
Well that explains why on the official Magisk page the developer said he didn't know if there would ever be a working version for the Pixel phones but people are using Magisk anyway. Unfortunately Magisk seems to run into the same problems as SU on the Pixel in that it doesn't always install properly or maintain root if it does install--plus most Magisk modules don't work with the Pixel, which makes it much less functional than on other phones.
Click to expand...
Click to collapse
I've been running magisk since 11.6 was dropped. I haven't had any issues keeping root or installing. Works every time and I flashing a new rom every 3 or 4 days.
Same with SU.
For magisk people keep leaving busy box in Magisk Manager turned on so it screws up root. It's in the magisk FAQ.
pcriz said:
I've been running magisk since 11.6 was dropped. I haven't had any issues keeping root or installing. Works every time and I flashing a new rom every 3 or 4 days.
Same with SU.
For magisk people keep leaving busy box in Magisk Manager turned on so it screws up root. It's in the magisk FAQ.
Click to expand...
Click to collapse
If you've been running SU for more than a few months on the Pixel then you know Google broke root on it and SU had to rewrite the app to fix the issue. That doesn't happen on other phones and is very likely intentional on the part of Google. At another point SU was suddenly causing problems and SU devs had to add a boot signature file to the flashing process. Again, this kind of thing doesn't happen with other phones. Pretending that SU and Magisk have always worked without problems on the Pixel is extremely misleading.
jhs39 said:
If you've been running SU for more than a few months on the Pixel then you know Google broke root on it and SU had to rewrite the app to fix the issue. That doesn't happen on other phones and is very likely intentional on the part of Google. At another point SU was suddenly causing problems and SU devs had to add a boot signature file to the flashing process. Again, this kind of thing doesn't happen with other phones. Pretending that SU and Magisk have always worked without problems on the Pixel is extremely misleading.
Click to expand...
Click to collapse
Lol why would I lie. I've been on magisk now since Feb. Tell me why I don't lose root?
Maybe you can't get it to work but that doesn't mean it doesn't work.
Also if you are following the evolution of things, signed builds are more secure. Root isn't broken you just have to resign the boot image because of HOW root is attained on the pixels.
Yes it only happens on the pixels because of the partition changes in the pixel. Since they have to be signed now with any bootloader from may and older, users need the verified boot signer.
But if you are paying five minutes worth of attention to all this you would know that all you have to do is flash the April bootloader and there is no longer a requirement for builds to be signed.
I've been through all this a million times. That said I'm still rooted like a champ.
Yeah for the pixel it's pretty straight forward, if you want to root use chainfire's zip it's 2.79 SR3, you're even advised on 2.82 that pixel users will not want to upgrade.
As far as the may bootloader situation, flash the april bootloader and you don't need to bother with the signing zip. Besides, I think dealing with knox was much worse
pcriz said:
Lol why would I lie. I've been on magisk now since Feb. Tell me why I don't lose root?
Maybe you can't get it to work but that doesn't mean it doesn't work.
Also if you are following the evolution of things, signed builds are more secure. Root isn't broken you just have to resign the boot image because of HOW root is attained on the pixels.
Yes it only happens on the pixels because of the partition changes in the pixel. Since they have to be signed now with any bootloader from may and older, users need the verified boot signer.
But if you are paying five minutes worth of attention to all this you would know that all you have to do is flash the April bootloader and there is no longer a requirement for builds to be signed.
I've been through all this a million times. That said I'm still rooted like a champ.
Click to expand...
Click to collapse
I've been paying a lot of attention to it actually. When you have to flash an old bootloader to prevent boot looping (which is what actually happens if you use the up to date bootloader) or you have to flash a boot signature file that wasn't previously needed then the flashing procedure suddenly changes again I wouldn't say it's easy to maintain root on a Pixel. I guess different people have different definitions for what easy is. As for Knox, I used to have many Samsung phones and once a procedure was figured out to get around it and root you were good for as long as you had the phone. With the Pixels Google seems to be actively trying to screw up apps that create root or bypass safety net via its monthly updates. It's a completely different situation in my opinion.
jhs39 said:
I've been paying a lot of attention to it actually. When you have to flash an old bootloader to prevent boot looping (which is what actually happens if you use the up to date bootloader) or you have to flash a boot signature file that wasn't previously needed then the flashing procedure suddenly changes again I wouldn't say it's easy to maintain root on a Pixel. I guess different people have different definitions for what easy is. As for Knox, I used to have many Samsung phones and once a procedure was figured out to get around it and root you were good for as long as you had the phone. With the Pixels Google seems to be actively trying to screw up apps that create root or bypass safety net via its monthly updates. It's a completely different situation in my opinion.
Click to expand...
Click to collapse
You went from saying "Magisk and SuperSU don't install properly or don't keep root" to talking about the changes to boot signing on newer bootloaders.
If you are going to share information at least try to be accurate. There is a whole slew of users in the development section running rooted ROMs just fine but if a new user reads your posts they will assume root is broken and flashing the pixel leads to boot loops.
You don't want to deal with the verified boot signer all you need to do is flash the april bootloader and reboot. It happens once. If that is too difficult then maybe those same people shouldn't bother flashing anything period.
No one said flashing and modding would be easy but flashing a bootloader ain't hard.
You might also want to take a look at the other threads in the Q&A which show people unable to flash TWRP, people boot looping when they flash TWRP, people unable to maintain root or flash custom Roms, etc. Even if you are able to maintain root like a pro there is plenty of very easy to find evidence from other people who don't have the same no problems experience as you.
jhs39 said:
You might also want to take a look at the other threads in the Q&A which show people unable to flash TWRP, people boot looping when they flash TWRP, people unable to maintain root or flash custom Roms, etc. Even if you are able to maintain root like a pro there is plenty of very easy to find evidence from other people who don't have the same no problems experience as you.
Click to expand...
Click to collapse
The only thing that proves is we have a ton of users that don't take the time to research.
You got users coming back from O that don't know they need an Android N bootloader in both slots to flash TWRP again.
You have users that are fastbooting ZIP files
You have users fastboot FLASHING TWRP
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. Welcome to XDA, it's the same on every device.
I guess all the guys that are rooted must full it. Or wizards or something.
I guess reading step by step directions makes me a wizard.
pcriz said:
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. QUOTE]
I answer these questions a lot and that is most certainly true.
Click to expand...
Click to collapse
pcriz said:
The only thing that proves is we have a ton of users that don't take the time to research.
You got users coming back from O that don't know they need an Android N bootloader in both slots to flash TWRP again.
You have users that are fastbooting ZIP files
You have users fastboot FLASHING TWRP
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. Welcome to XDA, it's the same on every device.
I guess all the guys that are rooted must full it. Or wizards or something.
I guess reading step by step directions makes me a wizard.
Click to expand...
Click to collapse
Actually that's absolutely not true. I came from a Nexus 6P. On the XDA threads for that phone there is an accurate, clear, up to date step by step guide on how to flash anything with that phone, including separate instructions for how to root, install a custom recovery, how to install a custom Rom and how to go back to stock. On the Pixels the threads are a complete free for all filled with confusing, contradictory and inaccurate information. I just read posts from earlier today from someone who is getting boot loops when flashing SuperSu. Not a single person responded by suggesting that he use the April bootloader. The suggested solution (which didn't work) was to flash the boot sig zip. How exactly is somebody supposed to research flashing on the Pixel when the XDA threads for this phone are a complete shambles? And since you are supposedly such an expert at flashing on this phone why don't you do something useful and help other people who are having problems instead of wasting everybody's time with your utterly pointless posts about how easy it is to flash on this phone and how people having trouble are idiots who didn't do their own research? You aren't simply part of the problem, dude--you are literally the personification of everything that is wrong with XDA.
jhs39 said:
.
Click to expand...
Click to collapse
This discussion ain't worth reading whatever it is you typed dude. I'm going to agree to disagree.
Sorry stable root is an unattainable unicorn for you. Sorry you're having such a difficult time. Sorry that making excuses for false information is a priority over finding out how it's actually done.
Happy flashing, best of luck to you sport.

What are my (best) options for root?

Hello,
I recently started using Moto G6 Play, and am wondering now what is the best and easiest option for root. I searched a bit on the forum and found one thread for root that includes unlocking bootloader and is more complicated than some info i have found on google - rooting with KingoRoot without pc (if that's even possible).
Device info: XT1922-3, 3/32gb
Build number: OPPS27.91-177-2
Android 8, latest security patches, available 9 Pie update.
Soo, my question is - Will methdos like KingoRoot work because that will suit just fine for me since i do not want to flash anything extra, but only debloat and optimize stock rom? And i suppose my bootloader is locked because when i power up with volume down + power it says oem_locked so thats another reason for pcless root.
Anyone can help?
petar_markovic said:
Hello,
I recently started using Moto G6 Play, and am wondering now what is the best and easiest option for root. I searched a bit on the forum and found one thread for root that includes unlocking bootloader and is more complicated than some info i have found on google - rooting with KingoRoot without pc (if that's even possible).
Device info: XT1922-3, 3/32gb
Build number: OPPS27.91-177-2
Android 8, latest security patches, available 9 Pie update.
Soo, my question is - Will methdos like KingoRoot work because that will suit just fine for me since i do not want to flash anything extra, but only debloat and optimize stock rom? And i suppose my bootloader is locked because when i power up with volume down + power it says oem_locked so thats another reason for pcless root.
Anyone can help?
Click to expand...
Click to collapse
DONT USE KINGO ROOT. For one you have to unlock the bootloader anyway so you can root please just use my guide https://forum.xda-developers.com/g6-play/how-to/guide-t3929928 to avoid screwing up your phone with any root like KINGO root. You have come on here asking what the preferred method is and over 5,000 people are using my guide lol so my guide is the preferred. You need all that in order to pass play store safety net if you even want be able to download alot of games or if you download the apks the game won't load and KINGO root 100% fails safety net checks to make sure your passing it
ninjakira said:
DONT USE KINGO ROOT. For one you have to unlock the bootloader anyway so you can root please just use my guide https://forum.xda-developers.com/g6-play/how-to/guide-t3929928 to avoid screwing up your phone with any root like KINGO root. You have come on here asking what the preferred method is and over 5,000 people are using my guide lol so my guide is the preferred. You need all that in order to pass play store safety net if you even wont be able to download alot of games or if you download the apks the game won't load and KINGO root 100% fails safety net checks to make sure your passing it
Click to expand...
Click to collapse
Hi, thanks for quick response,
Well yea, i gave up on KingoRoot after some researching that it might not be safest thing to use. But it seemed pretty handy for my situation. And yes i saw your guide and considered it as option but didnt really find any more reliable threads (maybe i didnt search long enough tho). Btw, as i noticed you method requires unlocked bootloader so if you have some thread available about it throw it here if you can, if not thanks anyways.
Regards
petar_markovic said:
Hi, thanks for quick response,
Well yea, i gave up on KingoRoot after some researching that it might not be safest thing to use. But it seemed pretty handy for my situation. And yes i saw your guide and considered it as option but didnt really find any more reliable threads (maybe i didnt search long enough tho). Btw, as i noticed you method requires unlocked bootloader so if you have some thread available about it throw it here if you can, if not thanks anyways.
Regards
Click to expand...
Click to collapse
The link for unlocking it is in the guide...... Just read the guide. And my guide is plenty reliable on here you just have to read it.....
petar_markovic said:
Hi, thanks for quick response,
Well yea, i gave up on KingoRoot after some researching that it might not be safest thing to use. But it seemed pretty handy for my situation. And yes i saw your guide and considered it as option but didnt really find any more reliable threads (maybe i didnt search long enough tho). Btw, as i noticed you method requires unlocked bootloader so if you have some thread available about it throw it here if you can, if not thanks anyways.
Regards
Click to expand...
Click to collapse
It's not an option, it's THE WAY. It's how to root.
Unlock bootloader, flash TWRP, use TWRP to flash encryption disabler and magisk.
Systemless root is the way now. Root is in the boot.img now. One click roots are dead.
The end
ninjakira said:
The link for unlocking it is in the guide...... Just read the guide. And my guide is plenty reliable on here you just have to read it.....
Click to expand...
Click to collapse
Ok, i will post an update on how it went if i actually decide to root.
madbat99 said:
It's not an option, it's THE WAY. It's how to root.
Unlock bootloader, flash TWRP, use TWRP to flash encryption disabler and magisk.
Systemless root is the way now. Root is in the boot.img now. One click roots are dead.
The end
Click to expand...
Click to collapse
Got it.

Trying to keep root features without root. (Hotspot)

When going to Android 11 I'd like to keep my device unrooted.
The only things I want to keep is vanced (will install the version w/I magisk) and my Hotspot. I know there's some play store Hotspot apks but I can never get them to work.
Last update the build.prop edit no longer worked, but i found a zip that enabled it from XDA. Believe it needed to be flashed in magisk but not sure.
I intend to try and flash the 11 OTA and just remove -w, hoping I'll keep the Hotspot modification.
If it matters, my SO wanted me to get back into pokemon go and I can't play on a rooted device. Tried magisk hide but that didn't work.
Any advice would be appreciated, cheers.
AlPoo said:
When going to Android 11 I'd like to keep my device unrooted.
The only things I want to keep is vanced (will install the version w/I magisk) and my Hotspot. I know there's some play store Hotspot apks but I can never get them to work.
Last update the build.prop edit no longer worked, but i found a zip that enabled it from XDA. Believe it needed to be flashed in magisk but not sure.
I intend to try and flash the 11 OTA and just remove -w, hoping I'll keep the Hotspot modification.
If it matters, my SO wanted me to get back into pokemon go and I can't play on a rooted device. Tried magisk hide but that didn't work.
Any advice would be appreciated, cheers.
Click to expand...
Click to collapse
You won't be able to keep any Magisk modifications without magisk. The way Magisk works is systemless so it needs to have the Magisk installed to mount the modules over the necessary directories. Also, for Pixels on Android Q and Android R you can't mount the system partitions to even modify them in the first place, so even if Magisk did directly modify the partitions they wouldn't work for devices with our logical partitions.
Pretty sure the way PoGo detects root is by searching for files/folders in your install storage called Magisk, twrp, or various other root names. So I'd suggest making sure those kinds of folders are cleaned out or renamed to something unrelated to root.
Also, Magisk doesn't support R yet so you won't be able to root yet even if you wanted to.
Sent from my Pixel 3a XL using XDA Labs
Skittles9823 said:
You won't be able to keep any Magisk modifications without magisk. The way Magisk works is systemless so it needs to have the Magisk installed to mount the modules over the necessary directories. Also, for Pixels on Android Q and Android R you can't mount the system partitions to even modify them in the first place, so even if Magisk did directly modify the partitions they wouldn't work for devices with our logical partitions.
Pretty sure the way PoGo detects root is by searching for files/folders in your install storage called Magisk, twrp, or various other root names. So I'd suggest making sure those kinds of folders are cleaned out or renamed to something unrelated to root.
Also, Magisk doesn't support R yet so you won't be able to root yet even if you wanted to.
Sent from my Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
Ah. So maybe I should keep the -w in the OTA to make sure to clean out some folder/files.
Didnt know R wasn't supported yet, kinda figured it wouldn't be since it just came out, but thanks for saving the hassle of finding out the hard way.
I've read going through threads here and saw that some people had lost root but kept some modifications after updating. Hoped that would have worked or there'd be able way without root out there that I was unaware of.
Anyway, thanks for the response!
AlPoo said:
Ah. So maybe I should keep the -w in the OTA to make sure to clean out some folder/files.
Didnt know R wasn't supported yet, kinda figured it wouldn't be since it just came out, but thanks for saving the hassle of finding out the hard way.
I've read going through threads here and saw that some people had lost root but kept some modifications after updating. Hoped that would have worked or there'd be able way without root out there that I was unaware of.
Anyway, thanks for the response!
Click to expand...
Click to collapse
Well I just installed PoGo real quick after checking my internal storage and renaming any file/folder with Magisk in the name to remove Magisk, and with Magisk hidden with a random package name and app name and PoGo hidden in magisk hide I was able to successfully log in without it detecting anything. So if you do wish to have modifications once Magisk supports R just make sure to keep an eye on your files/folder names and you should be all good :good:
As for the threads you've been reading, that's definitely curious. Do you know if they were pixel users? Or just people using a GSI or something?
Sent from my Pixel 3a XL using XDA Labs
AlPoo said:
Ah. So maybe I should keep the -w in the OTA to make sure to clean out some folder/files.
Didnt know R wasn't supported yet, kinda figured it wouldn't be since it just came out, but thanks for saving the hassle of finding out the hard way.
I've read going through threads here and saw that some people had lost root but kept some modifications after updating. Hoped that would have worked or there'd be able way without root out there that I was unaware of.
Anyway, thanks for the response!
Click to expand...
Click to collapse
OTA will not wipe your phone. I updated this way last night from Q, not rooted.
Just realize that the Android 11 developer release is not designed to be run as a "daily driver". It's a first alpha release and it is going to be full of bugs and incompatibilities.
There is zero reason to install this on anything but a spare phone that you develop on.
sic0048 said:
Just realize that the Android 11 developer release is not designed to be run as a "daily driver". It's a first alpha release and it is going to be full of bugs and incompatibilities.
There is zero reason to install this on anything but a spare phone that you develop on.
Click to expand...
Click to collapse
24 hours in. Absolutely zero issues so far.
poncespr said:
24 hours in. Absolutely zero issues so far.
Click to expand...
Click to collapse
Thanks for the progress report....
My comment was directed mainly at the OP. Somehow I don't think he is Google's target audience for the developer build and I am afraid he will be the type that complains or begs for help when things don't work right.
That being said, I am also surprised that the release is running so well......
sic0048 said:
Thanks for the progress report....
My comment was directed mainly at the OP. Somehow I don't think he is Google's target audience for the developer build and I am afraid he will be the type that complains or begs for help when things don't work right.
That being said, I am also surprised that the release is running so well......
Click to expand...
Click to collapse
No disrespect. Just commenting on my experience.
I am also surprised. Only weird thing was asking to register my sim. I'm guessing it was looking for an esim. Other than that, not a single force close or slow down. But to be honest it doesn't look like a big update as the version number suggest. Feels more like a little spit and polish. Like this should be Android Q 10.1.
I myself gave up rooting. The only two reasons I was rooting were adaway and viper.
poncespr said:
.But to be honest it doesn't look like a big update as the version number suggest. Feels more like a little spit and polish. Like this should be Android Q 10.1.
Click to expand...
Click to collapse
As with most major android updates since Oreo. Most visible changes now are slight UI revisions and some new features.
However, there are a load of under the hood changes being made. Some for the better, some for the worse.
Sent from my Pixel 3a XL using XDA Labs
Not to thread hijack, (which is what i am going to do anyway, but being POLITE about it ?), can anyone point me to a Hotspot solution for Sprint, without root? All the other various methods/tricks i used in the past that worked, like manually editing the LTE APN etc, just aren't working on this 3aXL.

Root oppo f1s 2021 One Click Root

Root oppo f1s marshmallow 6.0 on 2021 without TWRP or PC, ONE CLICK, read all the words i wrote here
Video tutorial :
WARNING : ur responsible on any damage you may cause while using root access ,
This is how you can root your oppo f1s with one click
-Install Mtk-easy from this link https://www.mediafire.com/file/uykcln2dgmqxkid/mtk-easy-su-v2.0.6.apk/file
-Click on the # button
-when you get the message , get ou of mtk-easy and wait until the "magisk" with default android image pop up on the apps list
click on it then update it and wait for the installation
And done, u can run magisk and manage root access
U NEED TO REPEAT THESE STEPS EVERY TIME U REBOOT YOUR PHONE
uninstall magisk when u turn off then on your phone next time, and use mtk-easy again to grant root access for u , it will install magisk again and u'll keep repeating these steps to never lose root access
Kinda easy , waited for years
Hear me out. Some people will be doing that and probably Safety net will be an issue, if it was that easy then why did I and many people as well write long tutorials that tell you how to root? It's for a reason that MTK phones are finicky with root and if you don't root them carefully it can become cumbersome and probably brick your device. I don't want to hurt your feelings, this is a great method, but it requires too much user interaction every time your phone reboots.
if anyone failed this even after turning on 64-bits on mtk-easy
Go to mobile data settings and get out google services and playstore from connecting to the Internet
uninstall magisk and mtk-easy then install only mtkeasy, open mtk easy then the method should be 100% working
muhammad42620 said:
Hear me out. Some people will be doing that and probably Safety net will be an issue, if it was that easy then why did I and many people as well write long tutorials that tell you how to root? It's for a reason that MTK phones are finicky with root and if you don't root them carefully it can become cumbersome and probably brick your device. I don't want to hurt your feelings, this is a great method, but it requires too much user interaction every time your phone reboots.
Click to expand...
Click to collapse
yeah i agree, but its better than getting up to the risk of changing the recovery with another one like TWRP which is the part that most users fail and end up with a bootloop on other previous methods that require 0 fails on the downloadtool usage
CESTRayCRYSTAL said:
yeah i agree, but its better than getting up to the risk of changing the recovery with another one like TWRP which is the part that most users fail and end up with a bootloop on other previous methods that require 0 fails on the downloadtool usage
Click to expand...
Click to collapse
These methods may be really good for devices that don't even have a custom recovery. As for us, we have CTR recovery which is really smooth and doesn't bug out unlike TWRP. So this method may not have any use because I also have a custom ROM coming up
muhammad42620 said:
These methods may be really good for devices that don't even have a custom recovery. As for us, we have CTR recovery which is really smooth and doesn't bug out unlike TWRP. So this method may not have any use because I also have a custom ROM coming up
Click to expand...
Click to collapse
Hey, do you have a link to any custom ROM for OPPO F1s? I am still stuck at 5.0 and many apps are no longer supported.

Categories

Resources