Google glass 2 stuck on the "Glass" screen, I tried restarting it, but it shows the logo and nothing changes.
I tried to make a factory reset - holding the camera button, clicking on the power button, and continue holding the camera button. I show me the recovery screen with options, but nothing is selectable, clicking on camera button won't let me select or click anything.
Is there any way to make a full factory reset to fix this "Glass" screen issue to make it working again?
As i am not allowed to put a comment i give you following answer....
Have you tried to do a factory reset with ADB as described here:
How can I do factory reset using adb in android?
How to factory reset android using adb
This is the factory reset commands with adb in your command line:
adb reboot bootloader //device will restart
fastboot devices //this will print a device code if it worked right
fastboot erase userdata
fastboot erase cache
Then manually reboot device. You'll need adb and fastboot.
If that doesn't fix the problem, and you don't care about keeping a warranty intact, you can re-flash the firmware. If you care about a warranty... use the warranty.
The firmware is available for the Explorer Edition here, if it's Enterprise E2 it'll be here. Enterprise E1 firmware isn't available freely as far as I know, so if it's EE1 you're out of luck.
The firmware files come with a text file which contains the adb commands you need to run. Run them all in the order they're written. The final one will restart your device. Voila. Clean slate.
If it still doesn't work after that, it's a hardware problem.
Related
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.
i am new in android app testing. i need to find the heap size and heap uses for a app. so i am doing this by using DDMS but there is a problem that, its not showing the running process of device.
Device .Nexus 6.0.1. Can you tell me please What am I missing here??
any help would be appreciated.
See circle in the screenshot where the device is appear but its process not displayed
I just solved the problem.
If you only want to show the information of your app, adding android:debuggable="true" in the corresponding Manifest.xml.
Otherwise, rooting the device and flashing a customized boot.img with "ro.debuggable" set to 1.
Why? Check out:
ro.debuggable
There are 3 possibilities:
Try to change another usb cable.
There are many cables only for charge, not for data connection. buy a cable with data connection maybe solve your problem.
Enable developer option
Go to the settings menu, and scroll down to "About phone." Tap it.
Scroll down to the bottom again, where you see "Build number." Tap it seven (7) times.
After the third tap, you'll see a playful dialog that says you're four taps away from being a developer.
Keep on tapping, you've got the developer settings back.
You dive into that menu to do things like enable USB debugging
Restart adb
adb kill-server
adb start-server
Here you can find step by step process for find the heap size.
Heap Viewer Walkthrough
Hope this will help you..
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.
I'm trying to set up 60 Galaxy Tab 2 devices, by flashing CyanogenMod and then gapps onto each one. Unfortunately, at the moment I need some manual intervention on each one, which is annoying.
I can programmatically turn each one on and boot it into recovery mode, and then flash the CM ROM. It then automatically reboots the tablet, though, and I can't touch it after that because the default bootup doesn't have adb debugging turned on. I thus have to turn it back off, or boot it into recovery mode manually, before the next step.
What I would really like to do is to use adb while it's in recovery mode to turn on USB debugging, so that when it reboots, I'll be able to get to it. Ideally I'd just change a setting (use SQLite3 to change something somewhere?), but I could if necessary rebuild the CM11 zip to incorporate the setting somehow. I think I will need to turn on debugging, and also add the computer's RSA fingerprint so that it's allowed to talk to the device.
Any idea on how I can do this?
I could if necessary rebuild the CM11
A possible way for this option is to set ro.debuggable=1 in build/core/main.mk even for user builds. However, please note that that could lead to security breach as USB debugging is not meant to be used by normal end users.
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