Tag Info

New answers tagged

0

The custom recovery .IMG is corrupted and you should go download a different one. In the error you received DTB stands for Device Tree Blob. The device tree blob is a default mechanism to pass low-level hardware information from the bootloader to the kernel.


0

Assuming that your contacts are synced to some service like Google or your mobile carrier, you should be able to do that right through their website (or Gmail, if all of your contacts are synced with your Google account). Any changes you make in your account on a PC, including contacts, will automatically sync to your device.


0

Download stock boot.img for your phone and flash it using same command


0

I had to connect as a camera (i.e. pick "PTP" from the item in the drop-down menu option you get when a phone is connected) to get the device to show up in Device Manager (it showed up near the top under Android Devices). From that point, it was standard: right click on the entry under Android Devices, select "Update Driver Software", click "Let me pick ...


0

Apologies for putting this on an old thread, however having spent a week paining over how to do this if your screen is locked and totally broken. Buy a USB OTG cable from Amazon (they're quite cheap), plug a USB keyboard into this and then plug that into your phone. You should be able to type the PIN to unlock it if this is what you have, then you can use ...


1

For the RSA verification that you asked to bypass, I don't know whether it would work in your device, but it worked in my little experiment. In Lollipop, the ADB keys (after authorization) are saved in /data/misc/adb/adb_keys. Your private key is saved in computer. In Linux the directory location is $HOME/.android/. On Windows that usually translates to ...


5

I got it to work :) NOTE: This also requires your device to be rooted. (Thankfully, mine was rooted) Connect the device to Mac or PC in recovery mode. (I had to map the process in my mind as the screen was broken). Now open terminal/CMD in computer and go to platform-tools/. type and enter ./adb devices to check if the device is connected in recovery ...


0

You should be able to just type: setprop persist.service.adb.enable 1 This will enable USB debugging on the device and persist across reboots.


0

Since your device has been factory reset, you should go through the set up steps which will prompt you to sign in with your Google account. Once you are successfully signed in, you will be able to install a launcher from the Google Play Store from your PC, and this will prompt the application to be installed on your device. If the launcher doesn't get ...


1

Hope your device is connected to your google account. if so you can install you can install third-party launcher from play store from any system you have access to. just login on web using same google account and it will display your device when you try to install an app from play store. you may additionally like to install something like quick setting.


1

Preferably without turning on the debug mode? Sorry! I don't have a solution that doesn't require USB debugging as of now. A workaround is to use a rooted device and run ssh server on Wi-Fi. Anyhow, if the device has been connected to PC using USB, then it must have drawn some power, miniscule and momentarily it may be. Setup adb in PC, turn on USB ...



Top 50 recent answers are included