I have - stupidly enough - updated my android phone to the newest 5.0 Lollipop. The update went bad and many hours later the phone is still unresponsive. I can only enter in a recovery mode. I have seen in forums that many other users had the same problem and it turns out that the only way out is factory reset of the phone. This means total loss of phone data. As I have no backups (as far as I am concerned) I was wondering if there is a simple way to transfer the data from phone to computer (Ubuntu) while phone being in recovery mode.
This is what I tried already:
started the phone in recovery mode
selected the 'apply update from ADB' (as this is apparently the only way computer sees the phone through $ adb devices)
I type
$ adb devices
List of devices attached
02452a1acc14c9d4 sideload
and then
$ adb backup -apk -shared -all
adb: unable to connect for backup
My phone was not rooted, but I am pretty sure the USB debugging was activated. Any ideas? Is it possible at all to backup phone in recovery mode?
Thanks in advance.
Helps to know what phone you have. You could look for the key sequence needed to boot into recovery mode. I'd look into flashing Clockwork Mod recovery which can mount the phone over USB while in recovery. There you could copy a new ROM zip to flash over the messed up Lollipop rom.
All you have to do is format /system and install a known working ROM. Also, Clockwork mod recovery can make a nandroid backup which can be looked at using Titanium Backup so you can extract your data that way.
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 using Xiaomi Mi4i device and the other day it fell down and the screen broke. It's all blacked out now and the touch is not working. The device is rooted and running stock MIUI ROM. I want to mirror the display onto my computer so that I can take a backup of important files (like contacts and SMS) from my PC. I tried editing some of the .prop files and settings.db using ADB while in TWRP recovery but nothing worked. I think the steps to be followed for Mi devices are slightly different. Can someone guide me through it?
I am using a Windows 8.1 PC
"adb devices" from cmd lists the device in recovery mode
Thanks!
My question is that is there any chance that any command in adb can damage (both hardware and software) my android phone (my phone is not rooted) and if software can it be recovered by factory reset? It is Micromax A120 and runs on android 4.4.2.
Yes, you can easily mess up your phone if you mess with ADB and don't know what you are doing. This is particularly true if you are using the 'Recovery' options (flashing new software to your device) in particular, if don't do this correctly, there are opportunities to mess things up (particularly if you are not patient, and don't wait for all operations to complete).
For the most part ADB is just a communication mechanism, and if you are careful to do only things you are confident are safe, there is minimal risk.
Bottom line, there is nothing specific about ADB that is risky, but it is a tool, and if mis-used could cause issues. Use it carefully, and you should be fine.
With adb you can delete and copy data on your mobile phone. So you can loose data or damage the Android System. However you have every time the chance to go into fastboot mode and flash a new Android ROM using the fastboot tools. You only can damage your Android device if you flash a corrupted bootloader using fastboot.
So in short form:
ADB: You can delete data but you have everytime the chance to recover your system. (However you can loose all your data!)
Fastboot: You can destroy your Android device if you flash a corrupted bootloader. It's irreparable.
I have a Nexus 4. I accidently wiped system and tried to restore it unsuccessfully.
I did have adb before I wiped the system. Now I can only get into recovery mode. When I use Nexus root toolkit it recognizes the device only in bootloader but it can't recognize it as adb device. I thought maybe now that Android is not installed USB, debugging is disabled as default.
Do I have a way to enable it or do you have any other solution? I can't use the device. Do I have any other way to install Android without adb?
adb isn't required (adb is only one of the ways to do it. As long as you still have access to recovery mode, you're golden).
Just get the zipped image you want to install (a modded one, or the official one). You should be able to get the official one from google since it's a Nexus 4. Do not unzip it.
Connect your phone to your computer as a usb drive. Copy the zip file to the root of your internal sdcard on your phone.
Reboot your phone into recovery mode. Then navigate the menu on the phone with the sound rocker and the power key to tell it where to find the new location of the new image.
Then reboot normally. I'm writing this from memory. If you want more specific instructions, I can provide them if you want.
the camera of my mobile (running Eclair-update1) keeps being non-responsive in 90% of the time, so I assumed a hardware defect at first. After whiping the cache and the phone user data sereval times it worked again. At least for a while. Now it stopped working again.
Browsing the net I found quite some users who experience the same problem and had a hard time after whiping their user data off the device.
So my question would be: how close can I get to the hardware with the SDK? I'd like to write an app to influence hardware states (e.g. re-initializing the camera, remounting the SDcard aso.), but I'd prefer doing it - if possible - with the SDK instead of NDK.
Thanks in advance!S.
It's not a question of sdk vs. ndk, but of underlying operating system level permissions preventing ordinary (aftermarket vs. manufacturer/carrier installed) android applications in general from doing raw hardware access.
Download Android SDK to your computer
Boot device to recovery
Connect USB cable to PC
Run adb shell then
umount /data
umount /system
e2fsck -fv /dev/block/stl9
e2fsck -fv /dev/block/stl10
Taken from forum.xda-developers.com/showthread.php?t=1396366