Question How to completely remove stock launcher - Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40

As the titles says, I want to completely remove the stock launcher (like it never existed) and install some other launcher (as if this was the only and stock launcher).
Bascially, This thread explains the problem in details.
I am on custom rom and rooted so I want to know how to make any launcher (lets say Lawn chair 2) stock/native from scratch and completely remove the stock one.

regedit12345 said:
As the titles says, I want to completely remove the stock launcher (like it never existed) and install some other launcher (as if this was the only and stock launcher).
Bascially, This thread explains the problem in details.
I am on custom rom and rooted so I want to know how to make any launcher (lets say Lawn chair 2) stock/native from scratch and completely remove the stock one.
Click to expand...
Click to collapse
That is actually very hard, I personally like the pixel launcher on my custom roms and sometimes it doesn't work right. I always recommend switching first to see if the launcher works fully. Than since your rooted use magisk system debloater module off the manager. If you're on Android 11 than I don't know normally it doesn't read the partition layouts properly and doesn't work but you can try it. They need to update it for Android 11 but with the super partitions it makes it very difficult.

regedit12345 said:
As the titles says, I want to completely remove the stock launcher (like it never existed) and install some other launcher (as if this was the only and stock launcher).
Bascially, This thread explains the problem in details.
I am on custom rom and rooted so I want to know how to make any launcher (lets say Lawn chair 2) stock/native from scratch and completely remove the stock one.
Click to expand...
Click to collapse
Yeah you could get rid of it via Root. There is a good app on the Play Store called something like System App Remover/Uninstaller? You could also try Magisk Modules!

dreamytom said:
Yeah you could get rid of it via Root. There is a good app on the Play Store called something like System App Remover/Uninstaller? You could also try Magisk Modules!
Click to expand...
Click to collapse
That app doesn't work right anymore at least not on Samsung one ui. I don't know on Chinese manufacturers like Xiaomi. But everything with the system partition is different now. It basically doesn't matter if you're rooted you can't touch otherwise it bootloops. I would recommend making a twrp backup first than try whatever you like.

what about using adb? have you try using adb to uninstall it?

I someone managed to uninstall the stock launcher and install lawn chair 2 as native but in the process, i lost home navigation gestures, 2 button and 3 button navigation options.
Had to reinstall the rom all over again

regedit12345 said:
I someone managed to uninstall the stock launcher and install lawn chair 2 as native but in the process, i lost home navigation gestures, 2 button and 3 button navigation options.
Had to reinstall the rom all over again
Click to expand...
Click to collapse
Yikes. Yeah yesterday I was almost going to say, be careful when uninstalling system apps. Its worth mentioning that the latest MIUI doesn't support Gestures on Third-Party Launchers, but you probably already know that.
Instead of clean-flashing, It may have been possible to dirty-flash the same ROM (with same version), to get Stock Launcher back without losing /data

dreamytom said:
Yikes. Yeah yesterday I was almost going to say, be careful when uninstalling system apps. Its worth mentioning that the latest MIUI doesn't support Gestures on Third-Party Launchers, but you probably already know that.
Instead of clean-flashing, It may have been possible to dirty-flash the same ROM (with same version), to get Stock Launcher back without losing /data
Click to expand...
Click to collapse
I did dirty flash first. Neither the launcher came back nor the gestures. Then google kept crashing since I didn't flash gapps knowing it is dirty flash so i don't need to flash gapps. All gapps started crashing and didn't work. So I flashed gapps but they still kept crashing so I said "fk it, i'll clean everything".

You have to systemize the app (you need root to do this). I wouldn't recommend deleting the stock launcher just incase your new launcher breaks

Try oneplus launcher magisk module.
Works well, looks well.

ptr21 said:
Try oneplus launcher magisk module.
Works well, looks well.
Click to expand...
Click to collapse
Wait, does it work on MIUI? Does it include "Recents"?

No luck with MIUI, gestures wont work.
It includes recents. Lots of settings.

Related

Not able to disable the Google search bar

Hi,
I am on stock ROM with JB 4.1 and wanted to disable the Google search bar present in all the screens. I did a search and found that disabling it from "All Apps" removes it from the homescreen and so I tried that. What it does is removes the Google search bar, but the space occupied by it is still present with a rectangular patch and I cant place any widgets in that space. Can someone please tell me how to permanently remove the search bar.
P.S - My phone is not rooted!!!! Its new and I want to enjoy stock till I can...
Just root the phone and don't install a custom rom, thus you will still be stock except for the SU app. Then you can remove the search bar all together and gain that space back. This way you can enjoy the STOCK rom too. Although if you remove the search you technically aren't stock anymore.
G-Nexus Sent
Install nova or apex launcher, you can enable/disable the search bar or just have it only on one screen and not all.
peachpuff said:
Install nova or apex launcher, you can enable/disable the search bar or just have it only on one screen and not all.
Click to expand...
Click to collapse
I know I can do that..but isnt there a way to do it in Stock launcher itself...??its so smooth...i like it very much..!!!
ifly4vamerica said:
Just root the phone and don't install a custom rom, thus you will still be stock except for the SU app. Then you can remove the search bar all together and gain that space back. This way you can enjoy the STOCK rom too. Although if you remove the search you technically aren't stock anymore.
G-Nexus Sent
Click to expand...
Click to collapse
Hmmm..yes..thanks for that..But once rooted, i wont be able to resist the temptation to install a Custom ROM..thats why am avoiding it till now..
siddharthmani said:
I know I can do that..but isnt there a way to do it in Stock launcher itself...??its so smooth...i like it very much..!!!
Hmmm..yes..thanks for that..But once rooted, i wont be able to resist the temptation to install a Custom ROM..thats why am avoiding it till now..
Click to expand...
Click to collapse
Resistance is futile. Time for some BAMF! :victory:
ifly4vamerica said:
Just root the phone and don't install a custom rom, thus you will still be stock except for the SU app. Then you can remove the search bar all together and gain that space back. This way you can enjoy the STOCK rom too. Although if you remove the search you technically aren't stock anymore.
G-Nexus Sent
Click to expand...
Click to collapse
How do you do this?

Stock Lollipoop rooted with SuperSU - but it keeps resetting everything I do

see #5 for problem
Hi guys,
so after quite some time with custom Roms I decided to go stock again as somehow I don't need root at all. Well, that's not true. I miss AdAway.
As there is no possibility to root the stock rom, is there ANY AdBlocker that works on Lollipop? AdBlock Plus doesn't (yet).
Why did you say there is no possibility to root the stock rom ?
I'm running Stock ROM, rooted and AdAway running fine.
ckpv5 said:
Why did you say there is no possibility to root the stock rom ?
I'm running Stock ROM, rooted and AdAway running fine.
Click to expand...
Click to collapse
How do you root the stock rom? I couldn't find out how.
Can I root without losing my data?
fBx said:
How do you root the stock rom? I couldn't find out how.
Can I root without losing my data?
Click to expand...
Click to collapse
Flash twrp recovery and root through the recovery. It'll ask you when you reboot the system if you want to root it
Sent from my HTC One_M8 using XDA Free mobile app
Huh. Didn't know it was THAT straightforward and I've been flashing my phones for years.
Well. I flashed TWRP and SuperSU 2.46, succeeded. But Adaway and Adfree don't work correctly. They block the ads but only until you reboot, then it's reverted, kinda like with a tethered jailbreak on iPhones.
What am I doing wrong here? Also the block is not like on KitKat - there it was really blocked, really removed, here only the images of the ads are removed but you still see the space they were supposed to be.
I also used a system app removal tool that also didn't work although it shows success. It just removes the installed data like updates.
When I delete apps manually via ES Explorer, they just reappear at the next reboot.
Root Checker says root is fine but it isn't supposed to behave like that and undo my changes.
What's wrong? Do I need another kernel maybe? As I said I went back to stock completely and updatet through to L.
I believe I got whats causing the issue.
After deleting a system app and rebooting, I got a message saying that the phone was restored from an "unnormal behaviour". Does Lollipop bring some kind of system restore point that just automatically restores itself when "weird" things like host file alteration happens? If yes, how do I get rid of that?
This phone has always had system files protected since KitKat. You need a kernel mod to delete system apps.
Don't know why the ad blockers aren't working. Adaway is working fine for me on stock US Dev Edition rooted. You said you are using Adaway and AdFree? Are you actually using both at the same time? maybe they are interfering with each other?
No I meant it happens with both. Only use adaway now. They work but after a reboot the adblock is gone and I need to apply it again. In fact, AdAway says it's deactivated and AdFree says it's already up to date but ads show anyway and I need to install the fix again to get rid of them.
Can you maybe point me to a kernel mod? Would want to get rid of some bloatware.
Maybe I should try installing xposed and see if it's gone after a reboot.
fBx said:
Can you maybe point me to a kernel mod? Would want to get rid of some bloatware.
Click to expand...
Click to collapse
The thread is here: http://forum.xda-developers.com/showthread.php?t=2701816
But unfortunately, flar2 hasn't had the time to update for LP. A user posted the kernel module in Post #210, but a subsequent user said it doesn't work. Custom ROMs have write protection disabled, as does Dev Edition stock ROM.
fBx said:
No I meant it happens with both. Only use adaway now. They work but after a reboot the adblock is gone and I need to apply it again. In fact, AdAway says it's deactivated and AdFree says it's already up to date but ads show anyway and I need to install the fix again to get rid of them.
Click to expand...
Click to collapse
Odd, as mentioned, I've used AdAway for quite some time now, and don't have these issues.
Yes, very odd indeed. Well, if I don't get it sorted out somehow I might as well switch to Viper or some other close to stock custom Rom again, or make it Dev like you.
Things are getting worse, in 1 of 2 cases AdAway spits an error at me when trying to apply the fixes and the phone just reboots and undos everything. It's like some protection from rooting or changing anything although I am rooted. I don't understand it. I can't possibly be the only one having problems with root on Stock Lollipop
This is really annoying me. I think I'm better of just installing a custom rom and setting the phone up again, will cost me an hour but at least I'm done with the bugs.
Yup, decided to jump the gun, wipe and install ViperOne and now everything works as I wanted it to. AdAway stays active and working.
fBx said:
Yup, decided to jump the gun, wipe and install ViperOne and now everything works as I wanted it to. AdAway stays active and working.
Click to expand...
Click to collapse
Interesting. I wonder if Adaway is dependent on the system write protection being disabled. I wouldn't normally suspect that, and only thinking of it since you mentioned the system write protection issue as well.
On the other hand, its the only difference I can think of between my phone and yours that would matter. I am on stock rooted Dev Edition, which apparently does not have the system write protection enabled by default.
redpoint73 said:
Interesting. I wonder if Adaway is dependent on the system write protection being disabled. I wouldn't normally suspect that, and only thinking of it since you mentioned the system write protection issue as well.
On the other hand, its the only difference I can think of between my phone and yours that would matter. I am on stock rooted Dev Edition, which apparently does not have the system write protection enabled by default.
Click to expand...
Click to collapse
I also assume that's the reason. I've never been on a stock rom since I don't know when, but figured that actually I only wanted AdAway which would normally not require a custom rom per se... but as it didn't really work in the end (and also other root-requiring stuff), I went back to custom again. Well, it's not that it's that difficult to wipe the phone occasionally and set up a clean custom rom to get it back to perfect performance. Gonna go with it.

Questions about running stock rooted ROM / XPosed (Gravity Box) / Substratum

Hi guys,
After months of hesitation, I finally ordered a Pixel 2 XL. Now after a few years of running custom ROMs, I'm thinking of running the stock Google ROM with tweaks. But I haven't done that in a while so I have some questions, after rooting and installing TWRP:
- is it safe to install the latest Xposed framework beta? (bootloop/crashes)
- does Gravity Box work fine (no crash/bootloop)?
- can I apply Substratum themes on rooted stock?
- which kernel would you choose between Flash and ElementalX? I've been using the latter for a long time but curious about Flash.
- how do you handle monthly OTAs? Can they be installed running all of the above?
Thank you! :good:
Ghisy said:
Hi guys,
After months of hesitation, I finally ordered a Pixel 2 XL. Now after a few years of running custom ROMs, I'm thinking of running the stock Google ROM with tweaks. But I haven't done that in a while so I have some questions, after rooting and installing TWRP:
- is it safe to install the latest Xposed framework beta? (bootloop/crashes)
- does Gravity Box work fine (no crash/bootloop)?
- can I apply Substratum themes on rooted stock?
- which kernel would you choose between Flash and ElementalX? I've been using the latter for a long time but curious about Flash.
- how do you handle monthly OTAs? Can they be installed running all of the above?
Thank you! :good:
Click to expand...
Click to collapse
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
2 - gravity box works flawlessly for me and gives so many features. I had to support the dev and bought the unlocker!
3 - you can use substratum, but since the March update, you have to reboot after building overlays to see them in the overlay manager.
4 - I've tried almost all kernels available for our device, and I don't know why, maybe it's a placebo, maybe not, but Flash has been the best for me. Virtually no slowdowns in terms of performance, and solid battery life as well.
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Hope this helps!
rickysidhu_ said:
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Click to expand...
Click to collapse
Hi,
Thanks for the comprehensive reply, it's appreciated and it does help!
I'm not sure about your last answer about OTAs though. So we have to flash the whole factory image every month? Isn't it possible to sideload the OTA? And what about Magisk and Xposed, do they have to be flashed again every time? I guess Substratum themes have to be compiled again as well? I guess I've been so used to custom ROM and dirty flashing that I got somewhat lazy
Does the unlocker for Gravity Box add more options? Or is it just a way to donate money to the dev?
Thanks again.
Ghisy said:
Hi,
Thanks for the comprehensive reply, it's appreciated and it does help!
I'm not sure about your last answer about OTAs though. So we have to flash the whole factory image every month? Isn't it possible to sideload the OTA? And what about Magisk and Xposed, do they have to be flashed again every time? I guess Substratum themes have to be compiled again as well? I guess I've been so used to custom ROM and dirty flashing that I got somewhat lazy
Does the unlocker for Gravity Box add more options? Or is it just a way to donate money to the dev?
Thanks again.
Click to expand...
Click to collapse
Unlocker is to support dev as well as it unlocks the ultimate notification controls which has a trial period
Ota are fine but we all prefer to flash the whole image because it is recommended and hardly comes up with errors
If you install magisk module for xposed then you would only need to re install magisk zip and your previous modules would be still installed
For substratum you need to disable overlays before updating and just re enable them after updating to latest update
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs
rickysidhu_ said:
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
Click to expand...
Click to collapse
Hey,
I can't seem to be able to boot after flashing the xposed zip. My device shows a corrupted system error and boots back to the bootloader.
Is there anything I'm missing here?
Thanks!
Ghisy said:
Hey,
I can't seem to be able to boot after flashing the xposed zip. My device shows a corrupted system error and boots back to the bootloader.
Is there anything I'm missing here?
Thanks!
Click to expand...
Click to collapse
Which version of Xposed did you flash? And which version of the Xposed installer did you install?
rickysidhu_ said:
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
2 - gravity box works flawlessly for me and gives so many features. I had to support the dev and bought the unlocker!
3 - you can use substratum, but since the March update, you have to reboot after building overlays to see them in the overlay manager.
4 - I've tried almost all kernels available for our device, and I don't know why, maybe it's a placebo, maybe not, but Flash has been the best for me. Virtually no slowdowns in terms of performance, and solid battery life as well.
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Hope this helps!
Click to expand...
Click to collapse
Ditto.
rickysidhu_ said:
Which version of Xposed did you flash? And which version of the Xposed installer did you install?
Click to expand...
Click to collapse
I flashed xposed-v90-sdk27-arm64-beta3.zip. But I ended up installing XPosed through Magisk and it actuallly worked.
Are we not supposed to flash the .zip? It's what broke everything. I managed to flash the factory image and got my phone back to normal.
Ghisy said:
I flashed xposed-v90-sdk27-arm64-beta3.zip. But I ended up installing XPosed through Magisk and it actuallly worked.
Are we not supposed to flash the .zip? It's what broke everything. I managed to flash the factory image and got my phone back to normal.
Click to expand...
Click to collapse
Glad you got it working.
I downloaded the Xposed APK in the Magisk thread and installed Xposed within the app; after reboot everything seems to work normally for me.
The way you did it is also fine though:good:

Crashes caused by uninstalled Systemapps?

Hi together,
I tried to uninstall some bloat ware from my Moto G5. I tried some System App removers, but after an update some Apps (e.g. Chrome) appeared in my app drawer again...
Does anyone know, what causes this behavior?
After that I used a simple file browser to delete the Chrome folder and the Maps folder from the file system. I rebooted and Maps was still in my App drawer... But I was able to deinstall it. I was really happy until I tried to open Acrobat reader, because it crashed after a few seconds. Similar K9-Mail: It started properly, but if I tried to open a mail, the app crashed.
Could anyone explain this strange behavior?
Greetings
Cylone
PS: I have stock firmware with all security updates and Magisk v16
PPS: I restored my backup this day, what caused a bootloop. The only way I saw to fix this was to flash the stock firmware... Now I have back all my bloat Ware and Gapps
Just install a debloated stock rom, flash it as you would a regular rom: https://forum.xda-developers.com/g5/development/rom-debloated-optimized-t3722396
Exanneon said:
Just install a debloated stock rom, flash it as you would a regular rom: https://forum.xda-developers.com/g5/development/rom-debloated-optimized-t3722396
Click to expand...
Click to collapse
Well, that's it. First thing I read on this thread is: I left Chrome only because of WebView, if you delete it remember to download Android WebView, otherwise everything will crash.
As I wrote, I removed Chrome without installing Android WebView. This had to cause the crashes.
Thank you very much Exanneon!
You're welcome even though I'm not the one who suggested to install WebView, however I still do recommend installing a debloated stock rather than staying on regular stock, I mean you already have twrp so there's nothing to lose, you can always make a backup of your regular stock and try out the debloated one.
Exanneon said:
You're welcome even though I'm not the one who suggested to install WebView, however I still do recommend installing a debloated stock rather than staying on regular stock, I mean you already have twrp so there's nothing to lose, you can always make a backup of your regular stock and try out the debloated one.
Click to expand...
Click to collapse
I tried the debloated ROM and I really like it. Only a few Apps Further I removed Chrome, but WebView was disabled. I was not a able to find it in the Apps overview. So I was not able to activate it...
My quick and dirty solution was to delete WebView, install it from Playstore again and move it to system/app. Last step seems to be necessary.
So are you going to stick to the debloated option or just the regular stock?
Exanneon said:
So are you going to stick to the debloated option or just the regular stock?
Click to expand...
Click to collapse
Yes, I will keep running the debloated ROM. It's working without any problems :good:
Good choice ?

Worth Rooting?

Hi all,
Joining Team Pixel tomorrow after my debacle with the Huawei Mate 20 Pro and the green screen fiasco.
Just wondering if its still worth rooting the Pixel? If i do it i wanna do it straight away to save wiping my data again when unlocking the BL. My main reasons would be for Adaway, Removing the Nav Bar, Swift theme installer and Viper.
Most of these can be done via ADB now so is it still worth rooting?
Rooting this phone is pretty easy and it doesn't impact the updating process much if you know what you're doing, so I vote that it is definitely worth rooting.
I don't use a lot of root apps, but the two main ones are worth it to me. I use AdAway for ads (VPN ad blockers are slower and have several cons) and an app called Sa2ration to compensate for the screen's weak color.
I have everything working the way I want without any compromises. Very happy with my setup.
It's soooo easy to root, I'm not sure why anyone wouldn't. My main reason is viper 4 android, but adaway, pixel launcher mods (changes icons and has a system UI tuner), and sd maid pro having deeper access for cleanup as well.
I've always had an Android phone that has been able to be rooted. Adaway, V4A, Substratum, Sa2ration, Titanium Backup and removing the stock navigation buttons are the biggest things for me currently with the Pixel 3 XL.
I always recommend unlocking the bootloader right out of the box, even if you never plan to root. The sole reason for this is if at any point something goes awry and you end up in a bootloop or somehow end up soft bricked, with an unlocked bootloader you can be back up and running like new with a very quick flash-all script from the latest factory image on Google's support site. However, with a locked bootloader, if you find yourself in one of those bad situations, you're at the mercy of Google support to either get you a new device or go days without a phone while they try and fix it.
So, in my opinion, unlocking the bootloader is a no brainer on these phones, right from the get-go.
With that said, rooting is much more user preference. I found no reason to root my OnePlus 6. However, with the 3 XL my sole reason for rooting is to edit the build.prop to properly hide the nav bar at the system level, allowing me to use gesture controls without issue. You can use ADB commands to achieve this as well. But my experience in trying to hide the nav bar with ADB commands on this phone has caused some wonky things to happen, such as status bar notifications not going away and volume controls getting cut off when watching something in landscape mode. Rooting the phone and editing the build.prop was the only solution that worked for me to hide the nav bar without running into unforeseen issues.
If you are one to do other things like use Magisk modules and such, then rooting will be a no brainer for you. Also, as someone else mentioned, rooting this phone is the most straight forward/simple experience I've had rooting a phone in years.
Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one
Guitarfreak26 said:
Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one
Click to expand...
Click to collapse
Try this: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76 do #4 then #8 if you want root. Also, Prerequisites has a link to download SDK Platform tools r28.0.1, if it needs updating.
gettinwicked said:
It's soooo easy to root, I'm not sure why anyone wouldn't. My main reason is viper 4 android, but adaway, pixel launcher mods (changes icons and has a system UI tuner), and sd maid pro having deeper access for cleanup as well.
Click to expand...
Click to collapse
I'm perfectly happy with the stock experience on this phone. I have no need for anything that requires root. I've rooted a lot of phones in the past, but there's something about this one that I just feel no need to do so. To me that says a lot for how far Google has come.
I'm getting my pixel 3 xl in a few hours today and I've been up all night watching pixel 3 xl videos. I was just about to post a question like this, but thanks to you I don't have to! The wonders of searching.
Anyways, I agree for adway and maybe even mods.
What bothers me is if I decide to use Google pay, Pokemon go or using my bank app, because I was told rooting can stop them from allowing me to use them.
I also want to do it out the box.
Also don't know about the new gesture stuff, so if I don't like it, I'd probably want to mod it.
Guitarfreak26 said:
Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one
Click to expand...
Click to collapse
That is exactly what I did with both a Pixel 3 and a Pixel 3 XL. Just don't do a permanent install of TWRP on the XL unless you want to lose your touch screen in TWRP with no way out of TWRP when it boots back in there. I ended up having to hold the power button down until I forced the device off. Booted back into bootloader and ran the temp TWRP (which strangely works fine for touch) and then ran Magisk again to get back to the OS. Strange, the regukar Pixel 3 took permanent TWRP after Magisk, rebooted to TWRP was still able to use touch commands and ran Magisk again to get back to the proper boot image. I can even go to TWRP normally, and touch is functioning normally. I'll have to write the stock boot image when I get home today so I can get back to stock recovery until TWRP for XL is fixed.
GunToYoMouth123 said:
What bothers me is if I decide to use Google pay, Pokemon go or using my bank app, because I was told rooting can stop them from allowing me to use them.
Click to expand...
Click to collapse
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.
I've been learning to live with stock ROMS, BUT, I still need my root. Adaway, TiBu, Substratum, LMT Launcher. I can't give 'em up.
Sevael said:
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.
Click to expand...
Click to collapse
Ohh okay, thanks for that input !
My pixel 3 XL just got here !
Going to see what's up !
Sevael said:
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.
Click to expand...
Click to collapse
My banking apps work fine but i can't get google pay to work. Even with magisk hide still not work. "This account already exists on your device" wheni try to sign in
J32A said:
My banking apps work fine but i can't get google pay to work. Even with magisk hide still not work. "This account already exists on your device" wheni try to sign in
Click to expand...
Click to collapse
Not sure, I haven't encountered this.
I find that when an app has detected root, sometimes they retain this information even through reboots. In those situations, clearing all data from the app often fixes it.
Something else to be aware of is that if you have a widget for an app that detects root, it's not uncommon for the widget to load before Magisk finishes loading and hiding after a reboot. On my Pixel 2 I had one app where after each reboot it would load first (due to a widget being present) and would detect root and block itself. I had to remove the widget and just just use a normal shortcut to the app instead, as I would never manually open it before Magisk finished loading up fully.
I just got pixel 2 xl this thing is a beast came with 5g and unlimted data when I got tablets for kids literally no download it's all instant. every phone I have had b4 is rooted most still work. My question will I improve anything by rooting with this speed? I don't think a VPN blckr would slow it down. How hard is it to reverse root if I need warranty? Is this speed the 5g or just Google built a great product?
sn0warmy said:
I always recommend unlocking the bootloader right out of the box, even if you never plan to root. The sole reason for this is if at any point something goes awry and you end up in a bootloop or somehow end up soft bricked, with an unlocked bootloader you can be back up and running like new with a very quick flash-all script from the latest factory image on Google's support site. However, with a locked bootloader, if you find yourself in one of those bad situations, you're at the mercy of Google support to either get you a new device or go days without a phone while they try and fix it.
<snip>
Click to expand...
Click to collapse
Unlocking the bl is problematic in some instances. Detection for apps and things like that. Why would you just not check off the "allow the bootloader to be unlocked" option in OEM unlocking? Then you get to fastboot and can unlock if needed without actually being unlocked and compromised.
bobby janow said:
Unlocking the bl is problematic in some instances. Detection for apps and things like that. Why would you just not check off the "allow the bootloader to be unlocked" option in OEM unlocking? Then you get to fastboot and can unlock if needed without actually being unlocked and compromised.
Click to expand...
Click to collapse
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Sent from my Pixel 3 XL
Eudeferrer said:
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Click to expand...
Click to collapse
No I don't think so. If you bl unlock it will be detected. There are kernels that will fix that but stock unlocked is a trigger.
Eudeferrer said:
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Click to expand...
Click to collapse
Yes. As @bobby janow said, some apps treat bootloader unlock as having root. DirecTV Now is a prime example. Also, Netflix won't even appear in the app store and would have to be sideloaded. Although, all of those can be worked around it is sometimes a pain.

Categories

Resources