Database Info

[Q] Disabling Stock Apps on MT4G?

I picked up a G2 yesterday, played with it, used the G2 Forum here to get the steps to disable a bunch of stock apps, and am now pretty sure I am going to go swap it out for a MT4G (the hinges are way to loose).
My question is can I follow the same steps for disabling some of the same stock apps on the MT4G as I did on the G2?
The steps were root the phone, launch a terminal, and just type in pm disable followed by the package name.

I have not tried that yet. Am hoping this will work the same - they is a lot of TMo junk on this device.
Will be trying it on Monday, and if no one else posts on it before then, will do so.

Read the threads before posting, your answer is here already.
Sent from my HTC Glacier using XDA App

Yes you can. I did the same steps and got the same results. Only difference is the app list between the two devices.

Elfabaa said:
I picked up a G2 yesterday, played with it, used the G2 Forum here to get the steps to disable a bunch of stock apps, and am now pretty sure I am going to go swap it out for a MT4G (the hinges are way to loose).
My question is can I follow the same steps for disabling some of the same stock apps on the MT4G as I did on the G2?
The steps were root the phone, launch a terminal, and just type in pm disable followed by the package name.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=829662

Mr Bill Florida said:
http://forum.xda-developers.com/showthread.php?t=829662
Click to expand...
Click to collapse
That thread refers to how to "force remove" apps via Titanium, which is NOT the same thing as using the pm commands referred to by the OP. Using pm commands manually is the same thing as using Titanium's freeze function, and will allow you to receive OTA updates. "Force removing" apps on the other hand will not allow you to receive OTA updates, in which case, according to that thread at least, you would need to get a ROM that would allow you to flash back to stock. And, as far as I'm aware, this is not possible on the MT4G, as system writes are not possible. So, if I understand things, I wouldn't go the route of "force removing" apps, but rather, stick with "freezing" them with Titanium or using the pm command.

floepie said:
That thread refers to how to "force remove" apps via Titanium, which is NOT the same thing as using the pm commands referred to by the OP. Using pm commands manually is the same thing as using Titanium's freeze function, and will allow you to receive OTA updates. "Force removing" apps on the other hand will not allow you to receive OTA updates, in which case, according to that thread at least, you would need to get a ROM that would allow you to flash back to stock. And, as far as I'm aware, this is not possible on the MT4G, as system writes are not possible. So, if I understand things, I wouldn't go the route of "force removing" apps, but rather, stick with "freezing" them with Titanium or using the pm command.
Click to expand...
Click to collapse
Is freezing them with titanium permanent? Or does this have to be done at every boot?

Beast84 said:
Is freezing them with titanium permanent? Or does this have to be done at every boot?
Click to expand...
Click to collapse
Freezing is not permanent, as in it can't be undone. But, it does survive a reboot, even with fastboot turned off. The reason is is that the changes are written to the data partition, not the system partition.

floepie said:
Freezing is not permanent, as in it can't be undone. But, it does survive a reboot, even with fastboot turned off. The reason is is that the changes are written to the data partition, not the system partition.
Click to expand...
Click to collapse
And freezing will allow me to still get the OTA? I deleted a bunch of apps & couldn't get the update so I reverted back to stock but I still wanna get rid of the bloat. I figure freezing is safer than deleting anyway...

Beast84 said:
And freezing will allow me to still get the OTA?
Click to expand...
Click to collapse
Yes (I need a 10 character reply.)

which ROM for as close to stock android as possible for SM-G930F

I see a lot of custom ROMs on https://forum.xda-developers.com/galaxy-s7/development but I am not sure which to use. My main goal is to remove all the builtin Samsung apps that I cannot disable/uninstall like Calendar and Internet. I started looking at SuperMan but then saw it has a lot of other enhancements too. I also want to avoid my device being rooted because I have to install apps that won't install if my phone is rooted (GFE/BlackBerry Work).

LineageOS or Resurrection Remix.

Just disable the Samsung apps you don't want. That's the only remedy for you.

SuperMan is probably the closest you'll get to stock. If that's too far off, I'm not really sure of any other options. You could temporarily root and try removing the offending apps, I'm not sure how much the system depends on them.
There's also the option of Magisk (Systemless) root, which shouldn't effect root-adverse apps.

I have rooted stock G930F rom with Magisk and removed close to a 100 system apps. No bugs, no crashes, and it is the best rom there is, if you tweak it right. Btw, you can hide root with Magisk and install your apps.

Memovic said:
I have rooted stock G930F rom with Magisk and removed close to a 100 system apps. No bugs, no crashes, and it is the best rom there is, if you tweak it right. Btw, you can hide root with Magisk and install your apps.
Click to expand...
Click to collapse
This is awesome. Any details/links/help on how to install remove those 100 system apps? I I see lots of articles on how to install Magisk so I can probably figure that out but not sure about how to install the system apps.

imthenachoman said:
This is awesome. Any details/links/help on how to install remove those 100 system apps? I I see lots of articles on how to install Magisk so I can probably figure that out but not sure about how to install the system apps.
Click to expand...
Click to collapse
Please take my advice:
Do NOT root your device.
Cause that has some side effects and nearly no benefits:
You won't be able to encrypt your phone again.
You'll have to install magisk to get some things to work
Do NOT install an AOKP based ROM cause there are severe bluetooth bugs.
Just install "BK Package Disabler (Samsung)" on stockrom and get rid of Samsungs bloatware.
PS:
I'm back to stockrom after installing LOS and I regret that step, cause it tripped the knox-bit.
Perhaps the BT bugs will be fixed in future; then I'll give LOS another shot.

Lol @ this lad above, get your facts straight.
On-topic: I followed root instructions from galaxys7root. For the debloating part, there is a topic called "Debloat your S7" or something like that, which helped me uninstall most of the apps, and the other ones I just uninstalled cause I didn't need them.

Memovic said:
Lol @ this lad above, get your facts straight.
Click to expand...
Click to collapse
Laughing isn't very polite.
On-topic:
How did you get your phone encrypted again?
What are the benefits of being rooted nowadays?
OK, TB would be one thing for me.
And... tinkering.

Do some Google-ing, should get the answers.

Memovic said:
Do some Google-ing, should get the answers.
Click to expand...
Click to collapse
Thanks for sharing your limitless wisdom :good:

if you want a rom as close to perfect, try helios 7.22.1

sammydoro said:
Please take my adviceo NOT root your device.
Click to expand...
Click to collapse
Everything I have read says that there are no issues rooting. Lots of folks have done it w/o issues. Maybe yours was a one-off?
Memovic said:
On-topic: I followed root instructions from galaxys7root. For the debloating part, there is a topic called "Debloat your S7" or something like that, which helped me uninstall most of the apps, and the other ones I just uninstalled cause I didn't need them.
Click to expand...
Click to collapse
Thank you! I will give it a shot.

imthenachoman said:
Everything I have read says that there are no issues rooting. Lots of folks have done it w/o issues. Maybe yours was a one-off?
Click to expand...
Click to collapse
Rooting went flawlessly.
I took the TWRP / Magisk way.
OK, loosing all the data is quite normal, when formating data, to get rid of the encryption.
But it trips your knox-fuse with the following consequences:
S-Health does not work anymore. OK, there is a build.prop hack to get it working.
OTA updates will not work anymore.
S-Pay (and others) is said to not work anymore.
Encryption does not work or is risky (look at Chainfires post):
forum.xda-developers.com/showpost.php?p=72204306&postcount=978
No one knows, how long safetynet will be covered by Magisk. Btw.: Magisk is great!
If I am wrong at any point, pls correct me.
I only rooted to use LOS. But there are too many errors atm.
So I returned to stock and have to live with these issues.
So it depends on your usecase.
If you just want to debloat your stockrom, use BK- disabler.
If you want more, root it.

sammydoro said:
If you just want to debloat your stockrom, use BK- disabler.
Click to expand...
Click to collapse
Can BK disabler disable or uninstall some of the built-in apps like Calendar and Contacts?

imthenachoman said:
Can BK disabler disable or uninstall some of the built-in apps like Calendar and Contacts?
Click to expand...
Click to collapse
Yes. That is the purpose of the app.
And, in my opinion, it works reliable and comfortable.

sammydoro said:
Rooting went flawlessly.
I took the TWRP / Magisk way.
OK, loosing all the data is quite normal, when formating data, to get rid of the encryption.
But it trips your knox-fuse with the following consequences:
S-Health does not work anymore. OK, there is a build.prop hack to get it working.
Click to expand...
Click to collapse
I rooted, but my S Health is still working
sammydoro said:
OTA updates will not work anymore.
[/QOUTE]
Yes, that's good, so Samsung won't remove my root or any system apps I am using or adding system apps I removed.
sammydoro said:
S-Pay (and others) is said to not work anymore.
[/QOUTE]
S-Pay doesn't work in our country, so what? It's a fail project anyhow.
sammydoro said:
Encryption does not work or is risky (look at Chainfires post):
forum.xda-developers.com/showpost.php?p=72204306&postcount=978
No one knows, how long safetynet will be covered by Magisk. Btw.: Magisk is great!
[/QOUTE]
sammydoro said:
If I am wrong at any point, pls correct me.
[/QOUTE]
done
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Trying To Root Pixel 2

Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,

bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.

l7777 said:
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.
Click to expand...
Click to collapse
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!

bluh5d said:
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!
Click to expand...
Click to collapse
The similarities are only on the surface my friend. When dealing with computers, similar and close is rarely good enough. You need exact.

bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.

evilwombat said:
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.
Click to expand...
Click to collapse
Can I root with latest supersu without recovery ?

Someone's bound to hose up their phone. Wondering where factory images are?

Born<ICs said:
Someone's bound to hose up their phone. Wondering where factory images are?
Click to expand...
Click to collapse
Yes. I agree. Might be me right. I wasn't planning on flashing recovery though just booting it.

If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.

If your bootloader is unlocked and you want root.
Try installing Chain fire's Supersu from the play store or install the apk.
I do not have my P2 yet to try.
Sent from my Nexus 5X using Tapatalk

me_droid said:
If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.
Click to expand...
Click to collapse
I think this may be a waste of time because it was modded to work on Oreo. They have already released a version that works on Oreo 3-1-1 that I already tried it wouldnt boot it. I will probably just wait even though i want to play. So i guess I can just say yep I have a pixel 2 with the bootloader unlocked and thats about it.

This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(

The_Fuzz22 said:
This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(
Click to expand...
Click to collapse
Yeah, I take having root completely for granted. I guess I've never bought a phone right at the moment of release before. If I didn't really need a new phone, I suppose I would have waited. Anyway, I figured out that you can block ads, without root, with apps that run all your traffic through a vpn (that's really only running locally on the phone). The best options after much research seem to me to be Netguard and AdGuard (though I haven't tried them yet). They both also include a firewall (Netguard is primarly a firewall), which I want.
https://github.com/M66B/NetGuard/blob/master/ADBLOCKING.md
https://adguard.com/en/adguard-android/overview.html
DNS66 also seems to be higly regarded, but it doesn't include a firewall. There are other firewall only apps, which work with the VPN method, but you can only run one VPN on Android at a time, so if you want both functions, without root, you need an app that does both.
https://forum.xda-developers.com/android/apps-games/app-dns66-source-host-ad-blocker-root-t3487497
Anyway, that's my plan until root comes along. Then I will go back to AdAway and AFWall+.

There is no kernel source released for the Pixel 2/XL yet. It is based on the 4.4 kernel, this should make development very smooth.

https://forum.xda-developers.com/pixel-2/development/psa-fastboot-booting-bad-image-confuse-t3692932

Question Reasons not to root

Hi,
I've done a quick search but can't find anything definitive so a quick response on here would be greatly appreciated.
Are there any reasons not to root on a P7P? Like tripping Knox on Samsung devices? Basically, irreversible side effects of unlocking the BL or installing Magisk? I'm rooted on a Doogee S98 Pro, a Xiaomi MiPad 4 and a Samsung Tab S6 at the moment and I don't think I could go back to having no root. It's pretty much my main reason for not buying an S22 Ultra.

Hi
this is one of the major benefits of the P7P in my perspective: you can unlock, root, unroot, relock without any negative side effects. You don't trip any fuse or have other effects that cannot be undone by a simple reflash.
Plus, maybe due to this, the P7P is one of the phones where the dev community is still quite active.....
Sent from my rooted P7P

s3axel said:
Hi
this is one of the major benefits of the P7P in my perspective: you can unlock, root, unroot, relock without any negative side effects. You don't trip any fuse or have other effects that cannot be undone by a simple reflash.
Plus, maybe due to this, the P7P is one of the phones where the dev community is still quite active.....
Sent from my rooted P7P
Click to expand...
Click to collapse
Perfect answer, thanks!

Pretty hard to brick a Pixel.
Just make sure you don't relock your bootloader unless you're fully stock. I've seen a bunch of people doing that throughout these forums here for some reason.

Yup, if you want to unroot once you're rooted, it's absolutely imperative you flash full stock before toggling OEM Unlock and issuing any ADB commands to re-lock the bootloader. Do that without flashing back to factory stock and you end up with a phone that can't boot because the bootloader is locked with a non-stock build, you can't unlock the bootloader because the OEM is toggled, and you can't flash a stock build because the bootloader is locked. Brick time.
Other than that it's a fairly safe phone to play around with.
I strongly recommend Pixel Flasher, it makes the whole process easier, but make sure you read up on it before doing anything.
📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com

GrapheneOS also supports relocking the bootloader, although I can't think of a reason why you'd want to.

The best reason not to root is that it's not needed in 2022. I can't imagine "needing" to do something with root that cannot be accomplished without root. YMMV

jaseman said:
The best reason not to root is that it's not needed in 2022. I can't imagine "needing" to do something with root that cannot be accomplished without root. YMMV
Click to expand...
Click to collapse
Call recording, full backup and restore, hosts based ad blockers.

Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month. I've also had updates corrupt the A/B Partitions. The warning screen for unlocked bootloader alone is a nuisance. If you're ok with that, go right ahead.

Guyinlaca said:
disable all Magisk mods, run updates, then re-root every month
Click to expand...
Click to collapse
You're adding steps and no indication of why. Just install the update with modified boot.img and call it good.

96carboard said:
Call recording, full backup and restore, hosts based ad blockers.
Click to expand...
Click to collapse
I went 3 days before rooting my P7P since I was unfamiliar with the process. I was able to root OnePlus blindfolded, but the forums made Pixel seem difficult. It was the most miserable 3 days when everything I wanted to use/customize depended on root.

without root I could not even get 5G working. Furthermore the AOSP Mods on the stock ROM... Systemless Hosts AdBlocking, Re-Vanced, .......
I unlocked and rooted the phone before even booted it the first time

Guyinlaca said:
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month.
Click to expand...
Click to collapse
Updated to November, didn't disable any Magisk mods, no issues.
It's only some mods which cause issues. Not got them installed, you can perform the update without touching Magisk.

Guyinlaca said:
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month. I've also had updates corrupt the A/B Partitions. The warning screen for unlocked bootloader alone is a nuisance. If you're ok with that, go right ahead.
Click to expand...
Click to collapse
You don't have to disable all your Magisk Mods

K1nsey6 said:
I went 3 days before rooting my P7P since I was unfamiliar with the process. I was able to root OnePlus blindfolded, but the forums made Pixel seem difficult. It was the most miserable 3 days when everything I wanted to use/customize depended on root.
Click to expand...
Click to collapse
And wasn't it funny when you realized that root on Pixel is actually easier than everything else?

Hello , i need help for rooting my p7p. If have a video step by step its be very helpfull. Sorry for my bad english " Salut " from Romania thanks

ZoM4cs said:
Hello , i need help for rooting my p7p. If have a video step by step its be very helpfull. Sorry for my bad english " Salut " from Romania thanks
Click to expand...
Click to collapse
Here is a guide you can follow.

96carboard said:
Call recording, full backup and restore, hosts based ad blockers.
Click to expand...
Click to collapse
Umm that's illegal bro.

chivamex10 said:
Umm that's illegal bro.
Click to expand...
Click to collapse
Maybe where you are, but not here and not in most places. So keep your legal advice to yourself, BRO.

chivamex10 said:
Umm that's illegal bro.
Click to expand...
Click to collapse
Actually in most jurisdictions it's what's called a one party consent requirement wherein one of the parties involved must be aware and consent. In this case the person doing the recording qualifies as the consenting party. In other places two party or more consent is required but not everywhere

Could swapping Boot Partitions to run Door Dash Dasher app be possible?

Hello I have a question. I have a OnePlus 7 Pro rooted with Magisk and of course the Dasher app wont work properly. Could I simply flash back and forth from a Magisk boot partition to a non rooted boot partition in order for Dasher to work? I wanted to get some insight before I start flashing things..
Thank you

ben_deez said:
Hello I have a question. I have a OnePlus 7 Pro rooted with Magisk and of course the Dasher app wont work properly. Could I simply flash back and forth from a Magisk boot partition to a non rooted boot partition in order for Dasher to work? I wanted to get some insight before I start flashing things..
Thank you
Click to expand...
Click to collapse
Does the Door Dash app detect root? Chances are you just need to make sure you're passing Play Integrity BASIC and DEVICE verdicts. More information here
It's generally inadvisable to try swapping back and forth between the slots on A/B devices. They aren't meant to be swapped at will; the purpose of A/B slots is for seamless system updates, and you could very well render both slots unbootable by attempting to do so.

So I installed the above Integrity Checker and I failed all three. What if I leave the other slot alone and flash back and forth TWRP backups of the boot partition on my current slot? What would you recommend at this point?
Thanks again

V0latyle said:
Does the Door Dash app detect root? Chances are you just need to make sure you're passing Play Integrity BASIC and DEVICE verdicts. More information here
It's generally inadvisable to try swapping back and forth between the slots on A/B devices. They aren't meant to be swapped at will; the purpose of A/B slots is for seamless system updates, and you could very well render both slots unbootable by attempting to do so.
Click to expand...
Click to collapse
Are you a Marine? Me too. Former Marine that is. Ooh-Rah.... I understand if you need to delete this reply since it is off topic.. But I had to shout out.

ben_deez said:
So I installed the above Integrity Checker and I failed all three. What if I leave the other slot alone and flash back and forth TWRP backups of the boot partition on my current slot? What would you recommend at this point?
Thanks again
Click to expand...
Click to collapse
Read the post, please. The answers to your questions are there. Changing your boot image won't matter because your bootloader is unlocked, and that alone means you're going to fail all Play Integrity verdicts without using USNF.
ben_deez said:
Are you a Marine? Me too. Former Marine that is. Ooh-Rah.... I understand if you need to delete this reply since it is off topic.. But I had to shout out.
Click to expand...
Click to collapse
There's no such thing as a former Marine, you should know better, knucklehead! 2007-2016, 2844/2841/2862/8411
We have several other mods who are Marines: @Az Biker, @Clark Joseph Kent for example, we even have a few veterans from other countries.

V0latyle said:
Read the post, please. The answers to your questions are there. Changing your boot image won't matter because your bootloader is unlocked, and that alone means you're going to fail all Play Integrity verdicts without using USNF.
There's no such thing as a former Marine, you should know better, knucklehead! 2007-2016, 2844/2841/2862/8411
We have several other mods who are Marines: @Az Biker, @Clark Joseph Kent for example, we even have a few veterans from other countries.
Click to expand...
Click to collapse
We were told to use the term Former Marine in bootcamp... and never use the term "X Marine" Former means "The same but at a different time" 1993-1997 1391... I'm from the "old Corps"....
But yes I did read everything on the post.. Good info thank you. I'm just trying to find a solution to this without having to lock the bootloader.

ben_deez said:
We were told to use the term Former Marine in bootcamp... and never use the term "X Marine" Former means "The same but at a different time" 1993-1997 1391... I'm from the "old Corps"....
Click to expand...
Click to collapse
One of my younger brothers was a bulk fuel specialist in Okinawa, he just got out a few months ago
ben_deez said:
But yes I did read everything on the post.. Good info thank you. I'm just trying to find a solution to this without having to lock the bootloader.
Click to expand...
Click to collapse
Well, as mentioned in that thread, you should be able to pass BASIC and DEVICE integrity by installing USNF 2.4.0, which forces Play Integrity to use basic evaluation instead of hardware methods. Don't worry about STRONG integrity, I am not aware of any apps that require that attestation. The vast majority of Play Store apps only use the DEVICE label as this indicates that the device (and software) has been tested via Android CTS; those which require additional security use the BASIC label as well. There are a few apps that use their own root detection techniques such as the presence of a SU binary or the Magisk app, but these are few and far between, and I highly doubt that the Dash app would be one of these. I would think it's a safe assumption that it simply uses the DEVICE label, maybe the BASIC label as well. Since you were failing all 3 labels, this would make sense.
Install the Magisk module mentioned in the thread and reboot, then use Integrity Checker to verify you're passing BASIC and DEVICE labels. If Dash still doesn't work, force stop and clear app data.

I installed USNF 2.4.0 rebooted and still failed all 3 integrity checks including BASIC and DEVICE. The Dasher app will install and seems to work fine until I select "Go Dash" to start accepting deliveries. It just loops back to the sign in page. I've cleared the data and cache and uninstalled and installed many times.... I even tried using older versions of the app with no success. I've tried using Magisk Hide and Zygist to no avail. appreciate you taking the time for my questions.. Much appreciation

ben_deez said:
I installed USNF 2.4.0 rebooted and still failed all 3 integrity checks including BASIC and DEVICE. The Dasher app will install and seems to work fine until I select "Go Dash" to start accepting deliveries. It just loops back to the sign in page. I've cleared the data and cache and uninstalled and installed many times.... I even tried using older versions of the app with no success. I've tried using Magisk Hide and Zygist to no avail. appreciate you taking the time for my questions.. Much appreciation
Click to expand...
Click to collapse
What version of Magisk are you using?
I believe that since you're using a Chinese device you may still need to use MagiskHide Props Config to spoof a valid fingerprint.

V0latyle said:
What version of Magisk are you using?
I believe that since you're using a Chinese device you may still need to use MagiskHide Props Config to spoof a valid fingerprint.
Click to expand...
Click to collapse
25.2

ben_deez said:
25.2
Click to expand...
Click to collapse
I installed MagiskHide Props Config but I'm not sure which fingerprint to use.. Many selections... I selected the TMobile fingerprint since I have a GM1915 . I'm also still on 10.0.3.GM21AA So far it hasn't fixed the problem.

What about a Dual Boot system? Is it possible to have dual boot systems with one rooted and one thats not rooted? It still wouldn't hide that the bootloader is unlocked tho right? Because I got the app to work on my old LG V20. Apparently once the bootloader was unlocked on the v20 it couldn't ever be locked again because of using Dirty Santa to unlock it. My v20 was vs995 and I converted it to un996.. all I did to make the app work was do a factory reset. I didn't have to flash the original vs995 firmware. But I think the bootloader should still be unlocked on the v20 even after the factory reset... The app didn't work on my OnePlus 7 pro even after I did a factory reset. frustrating.

V0latyle said:
One of my younger brothers was a bulk fuel specialist in Okinawa, he just got out a few months ago
No Kidding? How cool is that? I was at Camp Hansen 9th ESB Bulk Fuel Co.. Before that I was Station Fuels at MCAS El Toro in 1996 running the Hot Pits. Small world
Click to expand...
Click to collapse