Ive managed to get the debian shell working under term emulator and have made a decent size img file for everything i need. Im trying to install tightvncviewer and icewm. when i apt-get install (either package), apt-get cant find certain files, causing them to not work. i did the fix-missing but same thing, didnt work. Is their anyway to upgrade apt-get's package list so it actually downloads all the required packages for tightvncviewer and icewm or what, im all out of ideas. ive tried apt-get -u upgrade, apt-get upgrade, and apt-get dist-upgrade.
thanks for any help
So here's what i have been tinkering and i might share it as well here..
so its basically a back port of MTP support from the latest Ubuntu releases..you just have to update the GVFS(GNOME virtual file-system) of the Ubuntu Precise Version so it can recognize and mount the Nexus 4..so far its been good and stable for me..i am using a 32bit installation..
so here's what you just have to do..
Add the backport repository for MTP support in GVFS.
Code:
sudo add-apt-repository ppa:langdalepl/gvfs-mtp
then
Code:
sudo apt-get update
you will see stuff getting queued from ubuntu servers and other repositories
Then, upgrade the system, you should see many GVFS packages in the list.
Code:
sudo apt-get upgrade
you will be prompted that the GVFS will be updated with a new one..just proceed and wait for the update to Finish
And then, reboot via sudo command on the terminal or manually and you’re done! Plug your Nexus 4 and see it poppin!
**if ever this has been posted kindly delete the thread MODS..TIA!!
Thank you....
--=={BSnapp}==--
Hi
I've been at this for a few hours now and I'm just getting nowhere. I know this is a common issue but I assure you I have read every other thread and tried everything I have seen.
I have a HTC One M7 on the UK network Three with CWM recovery. Previously it was running Android Revolution HD, I tried to install the other Android Revolution HD Google Edition and right at the very end when I was asked to install Superuser is where I started running into problems. As it stands, my device is in a bootloop. If I'm careful I can time it right and boot into bootloader. From here, trying to enter recovery just puts me back into a bootloop.
All my HTC Drivers are installed fresh as of today. If I run erase cache, get var or anything along those lines all I get is <waiting for device>. When plugged in the device displays in Device Manager with the following details. I'm on Windows 8.1.I can't post a screenshot so it's text.
Unknown USB device (device failed enumeration)
Device status: Windows stopped because this device has reported problems (code 43)
I can't even find a RUU for my device, if it would even help at this point. Here's a transcript of my bootloader info.
*** TAMPERED ***
*** RELOCKED ***
M7_ UL PVT SHIP S-OFF RH
CID-H3G_001
HBOOT-1.44.0000
RADIO-4A.13.3231.27
OpenDSP-v26.120.274.0202
eMMC-boot
Where do I go from here? Bootloader factory reset does nothing, trying to flash a ROM doesn't work because the device isn't recognised, etc. I'm totally lost. The only suggestion I've even found is that I might have more luck in Windows 7, but I only have one system which will take 8-9 hours to back up to an external HD and unless it was a 90%+ shot I want reinstalling Windows 7 to be an absolute last ditch attempt.
Is there anything I'm missing?
Adb n fastboot drivers won't work with Windows 8.1 unless you are on hboot 1.55 or higher
You can try Windows 8 or Windows 7 but if you have ubuntu live cd
Try using it to sideload or push a rom
Sent from my HTC One using Tapatalk
Harish_Kumar said:
Adb n fastboot drivers won't work with Windows 8.1 unless you are on hboot 1.55 or higher
You can try Windows 8 or Windows 7 but if you have ubuntu live cd
Try using it to sideload or push a rom
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I've never used Linux but I'll make a live usb stick and try to work it out.
toyfights said:
I've never used Linux but I'll make a live usb stick and try to work it out.
Click to expand...
Click to collapse
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"
Harish_Kumar said:
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"
Click to expand...
Click to collapse
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.
toyfights said:
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.
Click to expand...
Click to collapse
Cool
Sent from my HTC One using Tapatalk
Harish_Kumar said:
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"
Click to expand...
Click to collapse
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.
How can i mount htc one in ubuntu with mtp mode
I tried
Code:
sudo apt-get install mtp-tools mtpfs
but its not working. pls tell me how can I mount it?
optimus0208 said:
How can i mount htc one in ubuntu with mtp mode
I tried
Code:
sudo apt-get install mtp-tools mtpfs
but its not working. pls tell me how can I mount it?
Click to expand...
Click to collapse
co-ask...
Installing the tools alone is not enough, I think, but it was more than a year ago, I last used linux.
You might find this useful:
http://ubuntuforums.org/showthread.php?t=2154543
http://www.webupd8.org/2012/12/how-to-mount-android-40-ubuntu-go-mtpfs.html
I've got 2 linux boxes sitting on my desk, one is running Arch the other Ubuntu 14.04. Both machines are able to detect fastboot mode if I boot it using the stock recovery but neither is able to connect using ADB when booted to system or recovery unless sideload is enabled.
I've seen plenty of posts of people using adb in linux so I'm just trying to figure out what I'm missing. Thanks
For adb when you're fully booting into stock or a rom, do you have adb enabled in developer options?
Sblood86 said:
or recovery unless sideload is enabled.
Click to expand...
Click to collapse
That is how it is suppose to behave. Adb is not active until you select the adb sideload option.
I'm on linux.
Sblood86 said:
I've got 2 linux boxes sitting on my desk, one is running Arch the other Ubuntu 14.04. Both machines are able to detect fastboot mode if I boot it using the stock recovery but neither is able to connect using ADB when booted to system or recovery unless sideload is enabled.
I've seen plenty of posts of people using adb in linux so I'm just trying to figure out what I'm missing. Thanks
Click to expand...
Click to collapse
You can dissect the Linux VM I'm using for adb.
i386 VM http://tinyurl.com/zok3o93
amd64 VM http://tinyurl.com/j75g5ju
It's a bare bones install. Installed only 2 packages, android-tools-adb and android-tools-fastboot, and grabbed the skia tar for adb 1.0.32.
I am running as root when I use adb.
If you happen to be using an x64 kernel, I saw mentioned for adb 1.0.32. One would need to grab the following packages for it to work.
dpkg --add-architecture i386
apt-get update
apt-get install libc6:i386 libstdc++6:i386 libncurses5:i386
thekrakah said:
You can dissect the Linux VM I'm using for adb.
i386 VM http://tinyurl.com/zok3o93
amd64 VM http://tinyurl.com/j75g5ju
It's a bare bones install. Installed only 2 packages, android-tools-adb and android-tools-fastboot, and grabbed the skia tar for adb 1.0.32.
I am running as root when I use adb.
If you happen to be using an x64 kernel, I saw mentioned for adb 1.0.32. One would need to grab the following packages for it to work.
dpkg --add-architecture i386
apt-get update
apt-get install libc6:i386 libstdc++6:i386 libncurses5:i386
Click to expand...
Click to collapse
Long story short I wound up bypassing the need for ADB in the first place. Sorry to have bothered people
I expect it was the fact that I hadn't actually found the option to enable ADB in the settings however.