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.
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.
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.
I forgot my mobile pattern and now i wanna recover without factory reset of my device.
The developer options is turned off and I cannot turn on usb debugging as well.
How do I enable usb debugging and remove my pattern?
I cant even run adb commands, because when i run adb devices I don't see any devices listed there.
This is not possible, for security reasons - if it were possible, someone who had stolen your phone would be able to unlock it as well.
I don't think this is possible. Upon googling though, I found a link. I am not sure if it works but you can give it a shot.
https://technastic.com/usb-debugging-using-adb-command/
Please note that debugging must be enabled on your phone so that ADB can detect and communicate with it.
You can disable Developer options and USB debugging using the following commands respectively.
settings put global adb_enabled 0
settings put global development_settings_enabled 0
Try them and share if they work for you.
Here's a link.
I.e. go to About Phone in settings and tap the build number seven times.
I have a hobby android app idea that basically just uses Android's sensors and logs them long term for several days (external battery). The sensors needed are in $200 phones, and I can get ones for under $100 if the screen doesnt work.
My question is, is it pretty easy to make an app that starts and loads via debugging, keeps running when disconnected and when I connect I can extract the log file, or would this so be difficult I would be ahead just to spend the extra $100?
As mentioned, turning on USB debugging without the screen isn't possible. You can't enable USB debugging over USB for security reasons, so your only option would be to use hardware commands to put the device in firmware download mode (presumably it will have a way to do that), then load a custom OS which allows USB debugging by default.
Personally I think that's more than $100 worth of work, so I'd just go with the working device. Then you can use it for other stuff down the line.
Alternately, you can probably get a replacement screen for not too much, and for most devices changing the screen is relatively easy. I'd look into that option as well.
The first barrier you may find is that you must activate the Developer Options in the settings and the USB Debugging. And when you connect to the computer, you must accept that cumputer as the Debugger.
I don't know if it's possible to do it without a working screen.
App will keep running & yes you can can extract the log file when connecting again.
But the problem is in the first step. if your screen if not working, then how would you add your workstation as a trusted device in your "display not working device". I doubt if there is such way, because we need to do several things like switching on developer options, usb debugging etc.
I hope you got your answer.
I am trying to enable my generic android device to turn on when plugging in the charge cable. I have read that this is possible by changing the contents of playlpm to be a shell script with the reboot command inside. However, this device doesn't have this playlpm file.
A similar question was asked a while ago...
Altering Android offline battery charging display (playlpm), How to make Android device boot when power is plugged in?
I assume this is specific to a certain vendor, Samsung it seems? Not sure. When I plug in a usb cable, there is a battery animation but I have no idea what gets called to show the animation. I have only found the images related to the animation. Anyways, I was wondering if someone knew what file is actually used to start this animation.