So, about... 7 months ago, I installed ADBWireless onto my freshly-rooted Skyrocket running UCJK2. It, and all other root-related functions, have worked beautifully. That is, up until about a month ago, when I noticed an odd behavior occurring on the phone. Everything root-related was non-functioning. After popping open a terminal emulator and trying to hand-start su, I was greeted with a dead terminal and not a working root terminal. ^C-ing gave me a # terminal, which appeared to have root access. Chalking it up to a random glitch, I rebooted the phone and everything was fine once more. However, about 2 days ago, I tried using ADBWireless again, and noticed it was triggering this "lock" on su and was not working. Uninstalling and reinstalling the app did nothing. Using a different app did, once again, the same thing. Using setprop seems to still work when enabling WiFi ADB.
I really, REALLY don't want to reflash or do a factory reset.
What should I do?
Here's the deal, my moto G (XT1032) WAS working perfectly when Motorola was Google owned. After the first non Google update it started showing some problems. It is currently running on Android 4.4.2 and system version 174.44.1with NO hardware or software mods. The major issue now is that I can't uninstall ANY app, after I hit uninstall in the confirm window the phone reboots every single time, no matter what app. In addition to this, the same thing happens when you try to clear any apps data, also, you can't access the security settings as the settings app crashes every time you try to access security settings, and lastly, sometimes it reboots the phone says that it's optimizing one app of one, it freezes, crashes and reboots again until it is able to start.
THE MAIN ISSUE IS UNINSTALLING, and I have already heard that resetting to factory doesn't work.
Also trying to uninstall from the app launcher, play store or settings gives the same results.
After some fighting with my phone I came up with a solution.
1. Since the phone said that it was optimizing one app always, I assumed the problem was a single app. Then I deduced that app was Floatifications because it messed up with the phone security settings (for the notifications access) and was the most mod-heavy app I has installed lately. So I tried to uninstall it via ADB.
1.1 I had a second issue that the phone didn't recognized that it was connected to a computer. To circumvent this I booted into fastboot menu and I selected the BP tools option. When the phone booted up again with the service app activated it recognized the USB connection to the computer and turned on debugging mode.
2. I tried different commands to uninstall it via ADB, the one that worked was: adb shell pm uninstall -k <package name>
2.1 In this case of floatifications the whole command is 'adb shell pm uninstall -k robj.floating.notifications'
3. After a reboot everything was working normally. Including the USB connection.
For a final remark, I came up with this whole process by trial and error so maybe there is an easier way of doing all this stuff. I also uninstalled in the same process the lockscreen app "Cover" that also requested access to notifications but I don't think that app was the problem since the phone said it was optimizing one app and it isn't as muddy as Floatifications.
Hi there,
I am wondering how exactly Androids new permission system works when running apps that do not target API level 23 and above. In that case, one has to agree to all requested permissions when the app is installed, but can revoke permissions afterwards in the settings of that app.
I had expected that revoking a permission adds an entry to some sort of "blacklist", so whenever the app tries to do something that would require a revoked permission, this attempt would be blocked. It seems however that reality is more complicated, because I stumbled upon an app where revoking a permission fails.
I installed the latest version of the DJI Go app, which requests tons of permissions upon installation. I especially wanted to revoke the "phone" permission, as I don't see why the app should be able to dial phone numbers or redirect calls. Whenever I tap the appropriate slider of the phone permission group in the app's permission setting, the slider turns to the "off"-position, but as soon as I leave the settings and go back afterwards, the slider is automatically set back to "on" again.
It is the only permission of the DJI Go app where revocation fails, all other permissions can be permanently revoked without problems (apart from the app crashing after startup when launched with all permissions revoked ).
Does someone have an idea what might be going wrong there? I tried to figure out how revocation of permissions actually works, but found nothing that could explain this odd behavior.
I'm running Android 7.0 on a Nexus 6.
I'm not sure if I chose the right forum for this question. If not, perhaps someone could move it to a more appropriate one.
I have a Samsung S7 T-Mobile, G930TUVU4APK1. Nothing exciting right?
I received this phone from a moving sale and the people have since moved, and I've no idea who they were. The key guard was on, couldn't get in so I did a factory reset via recovery...well It is protected with Google Factory Reset Protection (FRP). I tried various things, RealTerm being one, and cannot unlock it. I downgraded the firmware to 6.0.1, and still can't get in. I tried to open a browser by copy/paste text, and I can sign into Google from the phone, but it's not a browser. I can only tap buttons and copy/paste items through the User Agreement browser. Chrome is installed as explained below. It will not sync.
So I thought i would try to unlock the bootloader by flashing it through Odin: Downgraded it from 7.0 to 6.0.1. in 'download' mode. Let it reboot when finished and powered it down. Loaded Odin again and flashed the AP part with Samsung_G930x_QC_Rooted_BOOT.tar. I then flashed SU from that link too. Success. It is rooted. I can get into a shell and perform shell commands and ADB commands. I can enable and disable packages, including Google packages. So i went in with ADB, disabled Google Play Services, cleared the data, renabled. Went and did that with the other 3 Google APKs hoping when you cleared the data, it cleared the account in FRP. I successfully bypassed FRP for a friend's LG phone by reading the User Agreement. It would open it in a Chrome tab and I could search 'settings' and get into the phone's apps and clear all the Google Apps data which would clear the account in FRP and allow it to be setup again with a new account.
Not this one. So I have full ROOT rights, the shell shows a '#', I can use full ADB, I can do everything except bypass FRP. I haven't found a package I can't disable, I just don't know which ones so I can to get rid of FRP, if able. I have no idea if the bootloader is unlocked or what the unlocked picture of a lock says "custom" means. Any help I can ge would be awesome!
Code:
adb shell
[email protected]:/ # pm list users
Users:
UserInfo{0:Jason S:13} running
That is my name. But I am not signed in? It says to have "owner of the device" to log in during setup.
Ok well...I'm inside the phone. I managed to flash root. I will try to post a step-by-step later, but right now I can install any APK, as long as it doesn't rely on Google Services. I did NOT bypass FRP yet. I have cleared data and or disabled all Google related services with no effect. I installed the SuperSU app but it says i don't have root. I just added a Samsung account I just created.
Like I can get into settings, disable apps, I even installed Nova Launcher. I just can't get past the FRP when I go to sign into any Google App.
Ok. I really didn't mean to have to start all over, at least not tonight, but I screwed up and well....anyway...Here is what i got so far.
I have not been able to yet bypass FRP. I have been able to root, and disable services of Samsung and Google, to gain main entry into the device.
1) Make sure phone is powered off.
2) Boot into 'download' mode by pressing and holding volume down+home+power. When the screen comes on, release the buttons then press the volume up button once.
3) Plug phone into Computer and launch Odin.
4) Download UFIRM_G930_Odin_Firmware.zip and unzip.
5) In Odin, add corresponding files to slots and click start.
6) Let it reboot, then power it down again. Reboot back into 'download mode'.
7) Went here and downloaded Nougat_S7_Edge_EngBoot.tar.md5.
8) In Odin, placed the above file in AP slot, and click start. Device is 'rooted.'
At this point, I am at the Welcome screen to select language. I don't do that. Phone is still plugged in, so I open ADB.
Code:
adb devices
List of devices attached
e436cea2 device
adb shell
heroqltevzw:/ #
heroqltevzw:/ # pm list packages com.sec
The shell command then pulls up all the packages related to setting up the device with their software. I disabled the Setup Wizard. I may have the exact package name a little off, as I am trying to do this post by memory. When you do this command, watch the screen.
Code:
heroqltevzw:/ # pm disable com.sec.android.app.setupwizard
(some amount of words followed by) disabled status: true
At this point you should see the stock Android setup wizard. I list the Google packages.
Code:
heroqltevzw:/ # pm list packages com.google
I disable the four Core packages, Play store, account manager, play services and the framework. I am using App Inspector on another Android device to get the core package names. When that's all done, I then go back, clear all the data from each disabled packages. Then I disable the stock Android setup wizard. When I do that, a pop up allows me to select a Samsung Launcher, I go with basic touch wiz. I now have access to the device in it's entirety. Then I install SuperSU APK and Nova Launcher via ADB. I set up Nova to make sure it is default. I power down the phone and reboot to 'download mode' again. Plug back into the PC. From here I get a script that will do the rest. When it reboots, tap on SuperSU app, done.
Now I have gone on and restored the Google play related apks, but even with the data cleared, it still reads FRP. So I can use this phone just like any other, just without using apps that rely on being signed into Google. I added my Samsung Account, but I just created it.
Ok so I rebooted this AM to try out something. I re-enabled Samsung's setupwizrd while leaving Android's disabled, along with the play services etc. I then downloaded and installed Samsung's official web browser 'internet'. This solved a lot of small issues. I couldn't use recent apps button so I was unable to swipe apps closed. Samsung wasn't syncing with my account. Other little annoyances. So I logged into my Google account through their browser. Google FINALLY recognized the phone. Before it would recognize it, but only as a new phone anytime I logged into Google. So 24 hours later (today) since I last tried to log in, I re enabled the Google services. It asked to update Google play (which I downgraded so it would have a harder time recognizing the previous account), and it updated. I went to settings, added my google account, FRP is GONE!
Since I logged into Samsung late last night, the phone synced with it's apps, my data/info and whatever else it needed to sync with. So I presume Google saw that today and was happy with it enough with the results, it released the FRP. The phone is officially working on all ends! Rooted and all
I am having issues with Microsoft Teams (may happen with other apps). I use it as a phone system using the Voice add-on (https://www.microsoft.com/en-gb/microsoft-teams/microsoft-teams-phone). I have it installed on my laptop and my phone, the laptop will ring but the phone will only work intermittently. I havent been able to figure this out. I get a missed call notification immediately after the person hangs up.
I have tried whitelisting using the command "adb shell dumpsys deviceidle whitelist +com.microsoft.teams", that didnt work so i also tried "adb shell dumpsys deviceidle disable". Both seemed to improve the amount of times i was able to answer calls on my phone but it still doesnt work 100%.
Just now i was active on my phone about 1minute before i got a missed call notification without it ringing. I am not always by my laptop so having the calls ring on my phone is extremely useful. After doing this i dont think it is doze mode thats causing the issue. Before trying to adb commands i disabled any battery optimisation for the app (which whitelisting the app using adb does the same i believe?). Is there anything else i can try?
Microsoft have no idea and have not been much help. I get notifications for all other apps like Gmail, Signal, WhatsApp, Messaging etc all immediately and the missed call/voicemail notification also comes through immediately, it is just the call ringing (no notification or anything on screen at all). It is almost as if Teams is completely closed on my phone.
It doesnt matter if Teams is open or closed on my laptop, or if my laptop is off.
My phone is not rooted and is up to date running android 12. It was happening before the update a few days ago. I've been using Teams since May with it happening since the start. I can try and capture a log when it happens again