I had "adb backup" working correctly on my Sprint S8+. However, once I install the "Play Cardboard" app, my phone no longer responds to "adb backup" (no prompt is shown to encrypt/initiate the backup process).
This is the command I use to configure the "Play Cardboard" app without root:
adb shell dpm set-device-owner com.kunkunsoft.cardboardappforgearvr/.receiver.DPMReceiver
I'm fairly certain this is what is causing "adb backup" to no longer work. To test the situation, I factory reset my phone. I used "adb backup" and my phone responded. However, once I installed the "Play Cardboard" app, used the above referenced "adb shell" command, and restarted my phone, it would no longer respond to the "adb backup" command; there was no longer a screen to encrypt/initiate the backup process.
I just confirmed that it must be something with the "Play Cardboard" app. As soon as I uninstalled the app, "adb backup" worked again; I received a prompt to encrypt/initiate the backup process.
Can someone tell me why this breaks "adb backup"? Is there some way to play Google Cardboard apps on GearVR without this happening?
If you need more information, please let me know. Thanks!
Related
I had a problem where my Showbox app will consistently display "No connection error", there was also a problem where I couldn't even download to my internal storage using any download program(eg. ttorent, vuze, etc) and would say "invalidate service".
I found this fix through here on xda, but was intended for Galaxy Note 3, but also worked well on my Canadian Galaxy s4. Credit goes to Khizar, bigbiff, and daxgirl for this.
You'll need root, and a terminal emulator(I recommend Jack Palevich's version from Google play) but any version should do.
1)Open up the terminal emulator
2)type "su" ~without quotes~, hit enter
3) Now type this command, "restorecon -v -R /data/media" ~without quotes~
hit enter
4)Restart your phone, now you should be able to download to your internal storage, and use your Showbox app.
Hi,
My kids accidentally locked the phone with a password that he cannot recall after locking it.
Now the phone is password locked. Is there any way to unlock it? I was informed by Samsung Service Center that only way is to format the phone to factory default but all data will be lost which I have pictures in the phone which has not been back up.
Any suggestion to get the phone unlock?
Unlock your phone
You can do a factory reset in the recovery, trust me, your data like photos and musics ... (external and internal memory) won't be deleted but your apps will (data apps too like saves in the games). I hope that I helped you.
Bye
playnote said:
You can do a factory reset in the recovery, trust me, your data like photos and musics ... (external and internal memory) won't be deleted but your apps will (data apps too like saves in the games). I hope that I helped you.
Bye
Click to expand...
Click to collapse
Internal memory will be wiped completely (apps, their data, settings and all files on the internal storage). External storage (microSD) will not be touched.
I have no suggestion about the password though. I am not sure about password, but PIN security does have the option to unlock via Google account if certain wrong guessing threshold is reached.
Yes you can !
I already did it after i forgot my PIN on the Lockscreen. You just need to wipe the lockscreen-options .config file with adb
Try to google this keywords
If you have USB debugging enabled its possible yes
Hook up your phone to your computer, after you've downloaded and installed the "Samsung USB Drivers for Mobile Phones.exe". Download adb.exe and call it from your command prompt/console, like this:
Code:
cd c:\adb-fastboot
adb devices
If it shows a device with a long ID attached to it, you're in luck!
If you are rooted, you can bypass the screen lock.
If you are not rooted, you can still copy your photos.
To get the photos, use the "ls" command and "adb pull" to browse through your device and copy files and pictures back to your computer. Instructions for that
You can also use "adb backup" to retrieve all files, all app data, and even apks from the phone.
If you don't have the long ID, try rebooting to recovery mode and run "adb devices" again. Otherwise try another computer.
To bypass the lockscreen, use this command:
Code:
adb shell
rm /data/system/gesture.key
If you still can't get your computer to connect (USB Debugging disabled), you're still in luck if you have a Google account linked on the phone and an Internet connection. Download this Play app to your phone from a desktop to transfer your pictures to external storage. You'll need your notification drawer accessible I believe.
Hello,
I very recently had to remove the FRP lock on a client's Motorola G4 Plus because he had forgot his email and password (EXTREMELY common with old people getting smartphones). I have some experience with dirtycow, Samsung modem commands injection (using Realterm) and other bypass methods. Dirtycow was not working since this phone had security update from December 2016 so I had to use an online service with remote USB support. This service required me to enter Motorola's "Factory Mode" from the boot menu.
My question is: does anyone has experience with this special mode? Is there some literature regarding special commands, COM port settings or else when in this mode, or is everything kept private by the people who provide the service? Any basic information on what it does/how it works?
For what its worth, here's how the process went:
-Connected remotely with USB Redirector
-Booted into bootloader and activated "Factory Mode". Phone boots into OS but seems to operate in a special mode.
-Technician does something. I reboot into bootloader and boot again in factory mode.
-Technician somehow is able to enable ADB in 2nd "Factory Mode" boot. (this was not possible when I had access to Settings menu through "Talkback hack")
-Reboot again in normal mode and FRP seems to be removed. Setup has been bypassed, phone boots directly to Google Now Launcher.
What did he do? What does this "Factory mode" unlocks that permits him to enable ADB and completely bypass the Setup and Google Account verification? Did he erase the PERSIST partition? Did he inject app data from an already finished Setup?
Anyways, I am currently looking into it and will open another thread when I have more information.
Thank you!
If the technician used ADB it's likely you can Google whatever command he could have used. My guess is that he either wiped a file that concerns the Setup and Google Account Verification. Maybe he completely removed GApps remotely using ADB?
Sent from my Moto G (4) using Tapatalk
ironman38102 said:
If the technician used ADB it's likely you can Google whatever command he could have used. My guess is that he either wiped a file that concerns the Setup and Google Account Verification. Maybe he completely removed GApps remotely using ADB?
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
But these Apps are system apps, which would require ROOT to uninstall... Phone did not seemed rooted and bootloader was still locked after the procedure. I would think that finding a way of disabling the Setup/Google Services apps, and then re-enabling them, you would still be stuck when trying to add a Google Account afterwards since it will check for the PERSIST/FRP lock partition. Can the PERSIST partition be wiped through ADB without ROOT? Even then, how was ADB enabled in the first place? Some special AT command?
daveribss said:
But these Apps are system apps, which would require ROOT to uninstall... Phone did not seemed rooted and bootloader was still locked after the procedure. I would think that finding a way of disabling the Setup/Google Services apps, and then re-enabling them, you would still be stuck when trying to add a Google Account afterwards since it will check for the PERSIST/FRP lock partition. Can the PERSIST partition be wiped through ADB without ROOT? Even then, how was ADB enabled in the first place? Some special AT command?
Click to expand...
Click to collapse
Actually now that I think about it, you're right you can't remove GApps without root and you can't wipe Persist partition without root. I suppose he enabled ADB because that Factory Mode maybe has some special sort of commands, but even then what use is ADB when you don't have root?
Sent from my Moto G (4) using Tapatalk
This is the command that he uses in adb:
Code:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
sachingodishela said:
This is the command that he uses in adb:
Code:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
Click to expand...
Click to collapse
does anyone know the command to use in Factory Mode to enable ADB?
daveribss said:
But these Apps are system apps, which would require ROOT to uninstall... Phone did not seemed rooted and bootloader was still locked after the procedure. I would think that finding a way of disabling the Setup/Google Services apps, and then re-enabling them, you would still be stuck when trying to add a Google Account afterwards since it will check for the PERSIST/FRP lock partition. Can the PERSIST partition be wiped through ADB without ROOT? Even then, how was ADB enabled in the first place? Some special AT command?
Click to expand...
Click to collapse
Just to shed some light, adb does allow you to remove system apps or for that fact google apps without root
A tad late to the party but I'll give you a hint on the ADB enabling thing for Moto's.
Before he got ADB he probably set the device into 'factory' mode. This mode lets you send bytes to a certain TCP port via USB that sets system props. One of them is ADB enable.
There's similar tools on Youtube for repair and FRP removal like motoservice.exe
I myself reversed this years back and even found a few bytes that weren't used in the app but able to inject to change device properties.
Anyway, read this wanted to share. Motorola still has this mode, but now some devices won't let you boot factory mode.
Booting in factory mode exposes CQATest. They are using it to run shell commands, in this case to enable adb.
I followed the instructions on this site to uninstall a program (really just disable it) without root. I use ADB on the command line to do it. However, I get an error and nothing happens. When I follow the directions, it says to type "adb devices" to connect your phone. So I do that and my phone connects. Then it says type "adb devices" again to list your devices. It lists two attached devices: My phone and "emulator". Sooooo, when I try to delete an app, I get an error message that I have multiple attached devices and it doesn't delete the app. I used the adb detach command to try to detach an advice. Doesn't work.
Any advice?
Thanks
Why don't you root and finish the job? You can uninstall after root without any problems. I've never heard that someone is able to uninstall application if the root is needed for uninstalling.
Root is the way to go but it's much easier with the Tmobile version and it's a must these days with the Gogole app being a mandatory update with the new Play Store layout.
Hello
According to the forum research if i
- perform factory reset then the previously debloated apps will be reinstalled
- they can be reinstalled by adb command adb shell cmd package install-existing com.android.something without needing to factory reset.
- disabled (frozen) apps can be enabled through adb pm enable <packagename>
I have tried al three but it does not work. the commands were correctly used.
- If i perform factory reset (tried only through twrp recovery clearing cache, dalvik,data) then after initial setup the previously debloated apps are not back (i did not try factory reset through system settings yet because i dont know how it affects magisk)
Edit: only Kids mode got reinstalled. strange!
- If i use adb command adb shell cmd package install-existing com.android.something the terminal gives back that "the app was succesfully installed to user 0" but after checking the tablet the app is nowhere. I have tried it using the newest adb fastboot toolkit which has a nice terminal UI so i can reinstall all apps at once- which apps should be present on the tablet they give back "the app was succesfully installed to user 0" (they were uninstalled from user 0 so installing to user 0 should be fine) but they are not reinstalled.
- Titanium backup had accidentally frozen two apps, one is smart things, the second it android system webview- i cannot defrost them through titanium backup. I have tried several apps but none of them defrosts back. I have tried adb command pm enable <packagename> which gives me message "package succesfully enabled" but after checking state through adb pm list packages -d or tablet app setting they are still frozen.
My samsung tablet is rooted (at least i believe rooting was succesful because root checker says that) and on stock ROM.. It is strange that none of these commands are effective.
Does anybody have any clue why?
Thank you