unlock android device manager remotely - android

Is there an option to remotely unlock the online Android Device Manager's lock feature if I have the password? I do not see an option to do this but have read a couple examples of entering code to do something similar:
Open your terminal and type:
adb shell
Now enter these commands:
su
rm /data/system/cm_gesture.key
reboot
If a lockscreen appears after reboot, it should accept any pattern.
I have read many answers in forums but I do not have my phone, it was stolen and I am desperate. Also, I have the Google Device Manager password I used to lock my Samsung Active S5 after it was stolen. Any help or suggestions would be greatly appreciated.

Try powering it off and powering back up again..
For me the screen for entering passcode came up after rebooting..
I was so scared too, it seems to be a bug..before rebooting I couldn't find anyway to bring up the password screen neither ..

i too had locked my nubia mini device through android device manager.
it can be bypassed by rebooting into recovery mode and you need to format /data and /cache.
after this restart your phone through recovery mode it may take 5 to 10 minutes to finally show "android is updating your apps " something like this.
this method worked on my nubia mini and i thing technically it might work on every android phone that is capable of booting into recovery mode.
this method would not delete your photos,music,etc.
only contacts and app data will be gone,i am sure that won't be an issue.

Related

ADB - Empty list of devices when running 'adb devices' command

I've a Honor 10 View Lite with a broken screen (it's not usable) and I would try to recover data from it.
Following some tutorials it seems possibile to do that with ADB and the phone in recovery mode (holding power button + volume up).
I've installed ADB drivers through UniversalAdbDriver.msi and Fastboot version 1.4.3 Portable on Windows 10.
Being the screen black it's difficult to understand if the phone reboot in custom recovery mode or in normal mode, but when I open shell on the same folder of Fastboot and type 'adb devices' no device is found. I've also tried connecting another phone in recovery mode (Huawei Mate 10 Pro perfectly working) but the problem is still the same, no device found.
What can be the problem? Some wrong or missing installations?
I also have to specify that both the phones have USB debugging disabled and I hope this is not a problem because in the broken phone it's impossible to find a way to enable it. That's also the reason why I'm trying to recover data through ADB and not through programs like FoneLab and so on that required USB debugging enabled.
I will also accept advices on solutions different from ADB to recover data in these conditions, if they exists.
Thank you
I don't think adb will work for this unless usb debugging is enabled. At least, the device might show up in "adb devices" list, but it would show up as "unauthorized" and you wouldn't be able to pull data off it.
What kind of data are you trying to retrieve? Don't suppose you have cloud backup?
If it's just the screen that's broken maybe you can find a way to mirror the screen onto an external display somehow.

How can i turn on the debugging? ADB if my phone is locked and i forgot the PIN

Im locked out of my phone and there are ways to bypass through ADB, but the ADB is not turned on and i know there should be a way to turn it on somehow.
Recovery the PIN through the FindMyDevice site. Log in select the device then chose to lock it. This will prompt you to enter new details i.e. a password or PIN to unlock the device with. All you should need is the associated Google account.
You most likely should be out of luck unless you got i.e. Device Manager enabled and can control your device from there. If not then maybe you are rooted or at least have bootloader unlocked? If so, then you can install i.e. TWRP and "tweak" your device from there disabling i.e. pattern or pin lock from its terminal. If not, then your chances are getting low, however in similar situation I faced once, I managed to exercise some desing bugs of android and get out of it. But that was years ago, so perhaps this is no longer the case, yet you may want to take a look at this post Unlocking pattern locked network-less LG G-Slate v909

Yureka Plus stuck on "Preparing to start.. Starting Apps" screen after flashing crDroid 6.0.1

I had rooted my Yu Yureka plus by unlocking the bootloader using adb fastboot method, then flashing the TWRP recovery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that.
But while playing a game the phone automatically rebooted and ever since have been stuck on "Preparing to start.. Starting apps.."
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls, but can't access anything
Any suggestions what I should do now?
I have tried doing a factory reset from recovery but the problem persists and none of the hardware buttons are working, had to remove battery to access the recovery (still cyanogen recovery is opening).
Please HELP!
you can us this tutorial to get back to stock rom
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/

Deleted OS OnePlus One

Last week, while updating my phone, something went wrong resulting in my phone not booting properly. When turning on the phone it got stuck on the OPO logo. Thus, I first tried to wipe cache, didn't work. Then I tried something else and accidentally deleted the "system" data. I was now looking for a way to put the OS back on my phone with terminal (I work on Mac). The problem is that my computer doesn't detect my phone (when typing "adb devices"), and I think it is because the ADB-debugging box in the developer tools isn't checked on my phone. The problem is that I cannot check that box because I can't boot my system.
Who has a suggesting for what to do?
Thanks in advance,
Gijs
There is a thing like ADB called Fastboot mode. Look up how to boot your oneplus into fastboot mode (it's just a key combo) and then you can do things that you could on ADB with fastboot like loading a new ROM.

Galaxy Note 1 not listed under adb devices

I just installed android sdk. And trying to follow these steps to detect my device. Because my phone was disconnected & dead during an unfortunate/accidental/unwelcome software upgrade.
It's frozen on Samsung start up screen. I was able to use volume + power + home buttons to get into another black screen with now send the package you want to apply to the device with adb sideload <file name>. But not sure how to sideload from adb when I can't even detect my device. All I want is to retrieve my data & start up my device as normal.
Within the Command Prompt under platform tools, I typed adb devices. But no device listed. I am currently installing the Samsung Galaxy Note MTB device driver.
Can someone please guide me to the correct steps? There has to be a way to retrieve the data from the internal memory right?
Edit 1:
According to this article, I am not sure if my phone is bricked or trap in a bootloop...First of all, lets get something straight. Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is actually bricked, you won't be able to fix it yourself (but there are things you can do—see the end of this article)
Edit 2:
PC specs : Win Vista, 32-bit
After installing MTP drivers I am at this point. However within adb devices command I only see <aserial number> recovery. It doesn't say <serial number> device
Do I still have a hope to get to my data?
Your phone may be stuck in a BootLoop It wont get detected using adb try using FastBoot if not you should contact your samsung service center to reload software . Your data is lost in this case.
UPDATE
try downloading sp flash tool check your phone is detected if so you can have some hope in data recovery

Categories

Resources