Tag Info

Hot answers tagged

7

Your question does not match up with my experience using Ubuntu in regards to phones (and I have had a few). Ubuntu understands and recognizes foreign filesystems (ie. NTFS, FAT and many more) and will let you use them. If a storage medium has a valid filesystem on it Ubuntu will be happily to use it OR error out if it is an unknown or a broken filesystem. ...


2

That message you're getting is the network boot option that most BIOSes have. It's usually the last entry in the boot order, so it means your hard drive isn't being seen. The clicking sound and this boot problem lead me to believe that your hard drive is dead. You're almost definitely going to have to take it in to have the drive cloned or the data taken ...


1

I think i have guessed the reason now. Last night i opened my valuable harddisk filled with memories of people i may never meet again.. the last voices.. the first interactions... expressions... copies of important documents.. programs.. and plans... etc. But they are best left inside my mind. May be i was mad too and went crazily daring. Took as much ...


1

Likely the filesytem your external drive came with did not store additional file system details or recovery partition tables to ease recovery. Therefore, once the partition table, or the file allocation tables where overwritten by zeros I see little to no chance to recover these. Therefore you are faced with the cumbersome task to manually rename files ...


1

You may try using PhotoRec with your corrupt image file. It can recover a lot of file types, not just photos as the name may imply. Reference http://unix.stackexchange.com/questions/17811 PhotoRec download here


1

Boot into recovery mode, and enter the following: sudo apt-get clean sudo apt-get autoclean sudo apt-get -f install sudo dpkg --configure -a and sudo apt-get -f install followed by sudo apt-get upgrade sudo apt-get update sudo apt-get dis-upgrade Should work now...


1

The output of adb indicates it doesn't have permissions to do what it's trying to do. In this case list all connected devices. To fix it you should do adb kill-server followed by sudo adb devices Basically you're killing the adb server and then starting it with sudo privileges to access usb devices. After that there is no need to issue adb commands with ...



Only top voted, non community-wiki answers of a minimum length are eligible