Related
i successfully got into adb in recovery mode fairly easily on my ubuntu 10.4 laptop using the following method-
this should also work for a linux live boot from a usb flash drive
in one terminal tail and follow log messages
~$ tail -f /var/log/messages
in another terminal run the loop
then
1. plugin usb and keep it plugged in
2. remove battery, eject sd card.
3. put battery in
4. press vol- and power
5. after around 6 seconds, your terminal with the log will show something like "new high speed USB..."
6. press vol- to select recovery
7. press the power button
8. IMPORTANT- as soon as you see a new log entry (something like "USB disconnect"), pop in the sd card
check your loop terminal for adb. if it doesn't work, repeat at step 2
hope this may be helpful to some
blaksplash said:
i successfully got into adb in recovery mode fairly easily on my ubuntu 10.4 laptop using the following method-
in one terminal tail and follow log messages
~$ tail -f /var/log/messages
in another terminal run the loop
then
1. plugin usb and keep it plugged in
2. remove battery, eject sd card.
3. put battery in
4. press vol- and power
5. after around 6 seconds, your terminal with the log will show something like "new high speed USB..."
6. press vol- to select recovery
7. press the power button
8. IMPORTANT- as soon as you see a new log entry (something like "USB disconnect"), pop in the sd card
check your loop terminal for adb. if it doesn't work, repeat at step 2
hope this may be helpful to some
Click to expand...
Click to collapse
Awesome Post! you win the most helpful post of root!!... well over exaggerated but you get the point. Thank you.
blaksplash said:
in one terminal tail and follow log messages
~$ tail -f /var/log/messages
Click to expand...
Click to collapse
Great tip, thanks for knowing bash much better than I do
This ought to be quite a bit more useful than my previous method of running an lsusb loop, and definitely more useful than waiting for Win7's boo-boops, which like all Windows notifications is prob ~1s after the bus event is completed--I NEED MORE TIME(ING), so thanks!
Kulaa said:
Awesome Post! you win the most helpful post of root!!... well over exaggerated but you get the point. Thank you.
Click to expand...
Click to collapse
rynosaur said:
Great tip, thanks for knowing bash much better than I do
This ought to be quite a bit more useful than my previous method of running an lsusb loop, and definitely more useful than waiting for Win7's boo-boops, which like all Windows notifications is prob ~1s after the bus event is completed--I NEED MORE TIME(ING), so thanks!
Click to expand...
Click to collapse
Thanks guys
I also forgot to add that Windows users could easily try ubuntu or a Linux distro by booting a live session from usb disk.
blaksplash said:
Thanks guys
I also forgot to add that Windows users could easily try ubuntu or a Linux distro by booting a live session from usb disk.
Click to expand...
Click to collapse
I'm not sure a livecd on usb will work unless persistence is enabled, if one's concerned about setting up a 51-android.rules in /etc, but I have my doubts that a dedicated driver is necessary for work in adb with linux.
rynosaur said:
I'm not sure a livecd on usb will work unless persistence is enabled, if one's concerned about setting up a 51-android.rules in /etc, but I have my doubts that a dedicated driver is necessary for work in adb with linux.
Click to expand...
Click to collapse
i just tried it on a live boot of mythbuntu 10.4 and it worked on my first try. i think if you sudo ./adb shell you shouldn't have add the usb rule. no drivers, no path changes
open a terminal-
[email protected]:~/Downloads$ wget http(colon)//dl.google.com/android/android-sdk_r06-linux_86.tgz
[email protected]:~/Downloads$ tar -zxf android-sdk_r06-linux_86.tgz
[email protected]:~/Downloads$ cd android-sdk-linux_86/tools/
[email protected]:~/Downloads/android-sdk-linux_86/tools$ sudo ./adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Can windows show the log of USB connection?
Cool! I tried to do it but didn't quite get it on my first try (although I don't even want to root right now).
Thanks for the share!
Booker-T said:
Can windows show the log of USB connection?
Click to expand...
Click to collapse
i'm not sure. here is link for tail for windows. you might be able to open C:\WINDOWS\system32\config\SysEvent.Evt or some other log file the might keep track of hardware events
sourceforge.net/projects/tailforwin32/
x.v_ said:
Cool! I tried to do it but didn't quite get it on my first try (although I don't even want to root right now).
Thanks for the share!
Click to expand...
Click to collapse
so did you get it in another try?
I for the life of me can not get adb to run on this phone. I know adb and used it back when I had windows and use it currently on Ubuntu 10.04 with my Nexus One without any problems. I keep getting the device not found... How do I loop "adb shell"?
i got it on the first try with ubuntu live usb, once i got the error and i was in recovery, i went to go do the update.zip and i press power too fast and it ended up going to system reboot and i havent been able to get in since then
InsightGoalie said:
I for the life of me can not get adb to run on this phone. I know adb and used it back when I had windows and use it currently on Ubuntu 10.04 with my Nexus One without any problems. I keep getting the device not found... How do I loop "adb shell"?
Click to expand...
Click to collapse
are you able to get into adb normally with the phone set to "HTC Sync"?
here's how to make the loop
echo 'while true; do /ADB_DIRECTORY/tools/adb shell; done' > script_name
chmod +x script_name
./script_name
if you need root privileges to adb-
sudo ./script_name
socalracer said:
i got it on the first try with ubuntu live usb, once i got the error and i was in recovery, i went to go do the update.zip and i press power too fast and it ended up going to system reboot and i havent been able to get in since then
Click to expand...
Click to collapse
i've had the same thing happen to me. i left the battery out a little longer before my next attempt and that helped- maybe for a minute or 2.
i got it first time 2 times yesterday, my trick i think format sd card as ubuntu live
usb
Any idea if there is a USB log for OS X? Looking through var/log now and I cant seem to find much.
Hello, this is not another boot-loop brick issue as many of you are having. I have no adb access and no fastboot. I am stuck trying to do whatever NVflash will allow. I desperately need some information from the next post if anyone can help.
I may need to redefine the partitions but I will need info from someones device. If someone could PLEASE do the following. It will not overwrite anything on your device.
Download this file and put it in your nvflash directory and boot your device into boot-loader mode (Hold Vol up + down and insert USB)
http:/illdill.org/streak7/files/bootloader.bin
in NVFLASH use the following command:
Try this without the bootloader file, it may still give results:
nvflash --getpartitiontable partitiontable.txt
If not:
nvflash --bl bootloader.bin --getpartitiontable partitiontable.txt
Please send me, or post the outputed txt file.
Also, I will need the partition img files for 2 through 7 if anyone would please be so kind.
nvflash --read x part-x.img (where x is the partition number so you will have to run the command for each partition 2-7)
Thanks in advance!
illdill said:
Hello, this is not another boot-loop brick issue as many of you are having. I have no adb access and no fastboot. I am stuck trying to do whatever NVflash will allow. I desperately need some information from the next post if anyone can help.
Click to expand...
Click to collapse
where do I get nvflash program
If you could help with this lou0611, I would be forever indebted. Here is nvflash with the boot-loader drivers:
http://illdill.org/streak7/files/nvflash3.zip
Holding down Volume Up & Down while plugging in the usb will get you into APX mode. Your computer should recognize an APX device (your screen will remain blank). Choose to manually install the drivers from the bootloader-drivers folder in the zip file.
Thank you, thank you, thank you!
illdill said:
If you could help with this lou0611, I would be forever indebted. Here is nvflash with the boot-loader drivers:
http://illdill.org/streak7/files/nvflash3.zip
Thank you, thank you, thank you!
Click to expand...
Click to collapse
Where was u 2 weejs ago lol I couldnt get nvflash to work because of the lack of the correct bootloader...glad to see some one knows a little about nvflash
Sent from my Dell Streak 7 using XDA Premium App
I got it from the Tegra 250 Froyo developer download from NVIDA's website.
illdill said:
I got it from the Tegra 250 Froyo developer download from NVIDA's website.
Click to expand...
Click to collapse
i cant get to download mode
Power off the device, disconnect USB, hold down vol up & down then plug device into USB
illdill said:
Power off the device, disconnect USB, hold down vol up & down then plug device into USB
Click to expand...
Click to collapse
it takes me to apx mode, I cant find the drivers
thatruth132 said:
Where was u 2 weejs ago lol I couldnt get nvflash to work because of the lack of the correct bootloader...glad to see some one knows a little about nvflash
Sent from my Dell Streak 7 using XDA Premium App
Click to expand...
Click to collapse
You have only yourself to thank for that, your the one that suggested I look into NVFlash. Thanks, by the way
lou0611 said:
it takes me to apx mode, I cant find the drivers
Click to expand...
Click to collapse
They are in the bootloader-driver folder in the zip file. Should be NvidiaUsb.inf
http://illdill.org/streak7/files/nvidiausb.zip
illdill said:
I may need to redefine the partitions but I will need info from someones device. If someone could PLEASE do the following. It will not overwrite anything on your device.
Download this file and put it in your nvflash directory and boot your device into boot-loader mode (Hold Vol up + down and insert USB)
http:/illdill.org/streak7/files/bootloader.bin
in NVFLASH use the following command:
Try this without the bootloader file, it may still give results:
nvflash --getpartitiontable partitiontable.txt
If not:
nvflash --bl bootloader.bin --getpartitiontable partitiontable.txt
Please send me, or post the outputed txt file.
Also, I will need the partition img files for 2 through 7 if anyone would please be so kind.
nvflash --read x part-x.img (where x is the partition number so you will have to run the command for each partition 2-7)
Thanks in advance!
Click to expand...
Click to collapse
this is what i got
C:\Documents and Settings\media\My Documents\Downloads\NVFlash>nvflash --bl bootloader.bin --getpartitiontable partitiontable.txt
Nvflash started
Try pulling out the USB, powering off (reset pinhole by sd card) and going back into APX mode again, this usually happens when it isn't comming with the device properly, may need to restart computer as well.
And again, thanks so much for your help with this.
illdill said:
Try pulling out the USB, powering off (reset pinhole by sd card) and going back into APX mode again, this usually happens when it isn't comming with the device properly, may need to restart computer as well.
And again, thanks so much for your help with this.
Click to expand...
Click to collapse
I am in apx mode
What does the device show up as? Right-click Computer>Manage>Device Manager>Universal Serial Bus Controllers
Should say NVIDIA USB boot-recovery driver
illdill said:
What does the device show up as? Right-click Computer>Manage>Device Manager>Universal Serial Bus Controllers
Should say NVIDIA USB boot-recovery driver
Click to expand...
Click to collapse
yes it does
Try the command without the bootloader:
nvflash --getpartitiontable partitiontable.txt
illdill said:
What does the device show up as? Right-click Computer>Manage>Device Manager>Universal Serial Bus Controllers
Should say NVIDIA USB boot-recovery driver
Click to expand...
Click to collapse
C:\Documents and Settings\media\My Documents\Downloads\NVFlash>nvflash --getpar
itiontable test.txt
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x027c10034280b157
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
command failure: no bootloader was specified
Ok, try again with the bootloader You may have to exit and re-enter apx mode.
nvflash --bl bootloader.bin --getpartitiontable partitiontable.txt
Also, don't put a space in the output filename, it may not work.
illdill said:
Ok, try again with the bootloader You may have to exit and re-enter apx mode.
Click to expand...
Click to collapse
C:\Documents and Settings\media\My Documents\Downloads\NVFlash>nvflash --getpart
itiontable partitiontable.txt
Nvflash started
it just sits there
Tested and works (thanks jnl) I'm posting a link to CG61.img for easy loading extracted from 1FF-olympus_hktw-userdebug-2.3.4-4.5.2A-5_OLH-3-110614-test-keys-Retail-05.sbf
Download moto-fastboot for your os from http://forum.xda-developers.com/showthread.php?t=1138092
CG61.img Link - MD5 = 9151fca5183b85953d7afed83364802a
https://www.rapidshare.com/files/4119742271/CG61.img
Steps I followed on OSX:
Download CG61.img (placed in same directory as moto-fastboot)
Place your device in fastboot mode via the volume-down then volume-up procedure and verify it exists with ./moto-fastboot devices
./moto-fastboot flash webtop CG61.img
./moto-fastboot reboot
You might have to reboot the device 2X after this is complete before the webtop option shows up when docked
----=== NO NEED TO FOLLOW THE BELOW STEPS UNLESS YOU EXTRACT FROM THE SBF ===----
Below is from JNL:
Since I have the lapdock and did not want to revert to Froyo, I thought I'd give a more detailed explanation than the hint I worked from to re-enable webtop (with firefox 4.0.1!):
Download the leaked HK/TW sbf file and the 'sbf_flash' for linux (I did this under 32-bit ubuntu).
use sbf_flash -x 1FF-olympus_hktw...sbf
This will extract a collection of .img files.
Place your device in fastboot mode via the volume-down then volume-up procedure and verify it exists with:
sudo ./moto-fastboot32 devices
Then:
sudo ./moto-fastboot32 flash webtop CG61.img
This will run a 3-step flashing process. Once completed, do:
sudo ./moto-fastboot32 reboot
Voila. Webtop works and actually seems faster.
Hope this helps.
mburlingame said:
Steps I followed:
Download CG61.img
./moto-fastboot devices
./moto-fastboot flash webtop CG61.img
./moto-fastboot reboot
Click to expand...
Click to collapse
actually, just to clarify... is that in cmd on windows you're talking about? Where do we put the CG61.img?
s1mpd1ddy said:
actually, just to clarify... is that in cmd on windows you're talking about? Where do we put the CG61.img?
Click to expand...
Click to collapse
I ran this from OSX using the commands I listed jnl ran it from 32-bit ubuntu it looks like via the commands he posted
I placed the image in the same directory as moto-fastboot
Looking at the commands, it is for Linux. Get a Ubuntu LiveCD, very useful tool to have around.
Sent from my MB860 using XDA App
sifon187 said:
Looking at the commands, it is for Linux. Get a Ubuntu LiveCD, very useful tool to have around.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I am guessing this should work in Windows as well I am currently installing Windows 7 under VMware Fusion on my mac to confirm.
confirmed I could run this from Windows and did not get any errors back so performing this via the windows moto-fastboot should work as expected
Updated CG61.img link from DropBox to RapidShare due to DropBox shutting the link down due to excessive downloads (according to them)
So, I did the 1st step and nothing happened.
Do I have to do the 2nd step? If yes, where I find "sbf_linux" and "1FF-olympus_hktw...sbf"?
brunnogama said:
So, I did the 1st step and nothing happened.
Do I have to do the 2nd step? If yes, where I find "sbf_linux" and "1FF-olympus_hktw...sbf"?
Click to expand...
Click to collapse
You only need to follow the first section (Download the img file and download moto-fastboot for your os)
Are you saying that after you download the img and run moto-fastboot devices you do not see your device listed?
Can you post exactly whats happening when you run moto-fastboot devices then try to load the image on your device via moto-fastboot flash webtop CG61.img (make sure CG61.img is in your moto-fastboot directory)
So, I did everything again, and it´s still doesnt working.
No one errors appears. But when a plug phone on lapdock, doenst show the webtop´s option. when I execute them, appears an error: "This app Webtop.... has stopped unexpctedly..."
My log:
brunnogama said:
So, I did everything again, and it´s still doesnt working.
No one errors appears. But when a plug phone on lapdock, doenst show the webtop´s option. when I execute them, appears an error: "This app Webtop.... has stopped unexpctedly..."
My log:
Click to expand...
Click to collapse
Are you running the HKTW 2.3.4 image? ( Image from the following thread http://forum.xda-developers.com/showpost.php?p=15020775&postcount=2 )
Yes! I do!
It isnt correct?
brunnogama said:
Yes! I do!
It isnt correct?
Click to expand...
Click to collapse
Hmm yes that is correct - Can you tell me what OS you are using? maybe try another USB port I will do an md5 checksum on the file and post it maybe a bad download?
MD5 = 9151fca5183b85953d7afed83364802a
Did everything correct... Pretty damn sure. Phone won't even power up now.
Pull battery, plug back in usb cable, get green light, it goes out. Got it to fire up once with no sim.
F*ck !
EDIT: Dumb ass. Don't know how battery drained like a MF. Powered up in wall jack.
So, I´m using Windows 7 32.
I tried another port, tried new flash and nothing.. I´still having the same error when I execute webtop.
:/
brunnogama said:
So, I´m using Windows 7 32.
I tried another port, tried new flash and nothing.. I´still having the same error when I execute webtop.
:/
Click to expand...
Click to collapse
Hmm I have not been able to duplicate this issue - Can you confirm the MD5 checksum? Has anyone else seen this issue with Windows 7 and trying to flash this?
does this fix multimedia dock too? i dont get clock option when my phone is on the dock.
So, I tried on Ubuntu and doenst change anything. I still havent the webdock.
I have the clock issue too. When I plug on lapdock, the clock doenst fit on horizontal position.
Does this work with hdmi cable without any dock?
xabierd said:
Does this work with hdmi cable without any dock?
Click to expand...
Click to collapse
No this requires the Media Dock or the Laptop dock in order to work
Any chance to get the Debian 0.2.5 Webtop back?
Cheers
I've been a lurker for the last few years; never thinking I would need any help or assistance .. but I have a situation ..
My Sprint HTC One was working better than I had ever seen it just last Thursday. I was running CM11, with ART. I had an old version of SuperOne (Sense 5) backed up with TWRP. I thought I'd go ahead and load the backup, and update all the apps and then make another more recent backup before returning to CM11. I got as far holding the power button and selecting recovery. The phone locked up at that point.
It took 10 minutes to get it back to the screen where you can select fastboot, factory reset, etc. Interestingly I couldn't get into TWRP. The screen read "entering recovery" and nothing. It would just hang there.
I read that erasing the cache with fastboot might work, and it did. But when I was able to enter recovery, instead of restoring CM11, I thought, "well, maybe now it'll work", so I just rebooted. Wrong. Wouldn't boot. And, now running fastboot cache erase (or erase cache) doesn't do anything.
Now, by pressing the power button alone and holding it in I'm able to get to the fastboot, factory reset, etc screen. Went to fastboot usb, and fastboot commands work but ADB doesn't detect the device. I can't send ADB commands, but I can send ONE fastboot command. After sending any fastboot command, the phone locks up. Nothing from that point.
I tried installing a RUU. The .exe file detected the version on my phone, and everything went great until the program said it was booting to the bootloader. Locked it up. Nothing from that point.
I need help.
Thanks.
I uninstalled the HTC drivers and reinstalled them. A suggestion since ADB didn't work. And I can't get into bootloader. No difference.
Any suggestions
Any suggestions at all. I'm desperate.
Ogre77497 said:
Any suggestions at all. I'm desperate.
Click to expand...
Click to collapse
You can get into fastboot correct?
Fastboot - Yes .. Sorta
I can get into fastboot, but I copy anything to the phone via fastboot. I'm told "unable to write". Thanks.
Ogre77497 said:
I can get into fastboot, but I copy anything to the phone via fastboot. I'm told "unable to write". Thanks.
Click to expand...
Click to collapse
Ok it's probably a problem with your USB cable or USB port. Try using another PC and another cable.
If this doesn't work read some guide to properly set up ADB, uninstall all HTC stuff and install only the "naked driver" and than run the LATEST ruu. Maybe you have upgraded your firmware and can't flash older ruu's.
Sent from my HTCONE using Tapatalk
Will Try
I'll give that a try. I really appreciate the help. I run my whole business on that phone.
Just make sure you follow my suggestions properly. It should be just the cable, and I think you don't have the right drivers for ADB. Stay calm your phone is just soft bricked. You only need to be patient and read. Naked driver here http://forum.xda-developers.com/showthread.php?t=2263822
Sent from my HTCONE using Tapatalk
elvisypi said:
Ok it's probably a problem with your USB cable or USB port. Try using another PC and another cable.
If this doesn't work read some guide to properly set up ADB, uninstall all HTC stuff and install only the "naked driver" and than run the LATEST ruu. Maybe you have upgraded your firmware and can't flash older ruu's.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
+1
I did the same thing a few weeks ago and lost recovery in the process. The naked driver did the trick. Also the thread about restoring after a gsm rom install is a great. It's not a loss. Not having an sd card in the one made things a little different for me, but I was able to get everything back. These drivers suck!
Progress
I've followed your directions. I downloaded the naked driver, and the minimal ADT. I found the correct RUU (3.04.651.2) I attempted to relock the bootloader, but I got a message .. " Status read failed <no such file or directory>" Went ahead and tried flashing the RUU (fastboot flash zip ruu.zip), and got the message "FAILED Remote: not allowed"
The phone is unlocked, CID SPCS_001, and HBOOT 1.44
I wasn't able to access TWRP recovery earlier, so I tried reflashing the img file. Failed remote: image update error. I tried erasing the cache .. "Failed remote erasing error", but now I can get into TWRP.
TWRP says I have "0" internal storage. I also can't mount system, data or cache. The choices are there but can't be selected.
I can't use ADB (device not found). and the phone isn't detected by windows. I had installed the HTC drivers, but couldn't uninstall them, so I install HTC Sync manager and then uninstalled it. The program deleted the HTC drivers when I uninstalled it. When I plugged in the HTC One (with a new cable) nothing happened, so I used the windows hardware wizard to install the naked driver. The phone still isn't detected, but again I can issue fastboot commands. Well, one fastboot command and then the phone freezes up.
If I use filemanager within TWRP there's no emulated sd card. I really think that's where my problem is. No partitions are available. And, when I use TWRP to shut down, it warns me that no OS is installed.
Any other suggestions?
I sure appreciate all your help. Thanks.
elvisypi said:
Just make sure you follow my suggestions properly. It should be just the cable, and I think you don't have the right drivers for ADB. Stay calm your phone is just soft bricked. You only need to be patient and read. Naked driver here http://forum.xda-developers.com/showthread.php?t=2263822
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Are you Linux savvy at all? All this crap is far easier on Linux. I guarantee the drivers are absolute cakewalk -- there isn't a specific driver at all, just a rule to tell the kernel about the device.
I can give you the udev rule for the phone if you are sick of trying to get Windows to work. The Android SDK is also quite easy to install.
If you want to try, just install Ubuntu 12.04 LTS. Later versions also work, but that version is the current stable release. I can help from there.
Try another cable maybe it's faulty. Uninstall all the HTC crap, run some cleaner app like ccleaner (maybe there are leftovers) and install only the naked driver. Your phone should be detected. Make sure you have the latest version of ADB. here's the latest http://click.xda-developers.com/api...n 1.1.3 Here&jsonp=vglnk_jsonp_13877458281136
The ruu is not to be flashed with fastboot commands, you must run the exe file
Here's the latest ruu
http://click.xda-developers.com/api....05.651 .5&jsonp=vglnk_jsonp_138775039936710
-extract zip to a folder on your pc
-using fastboot, type this cmd: fastboot oem lock this will relock the bootloader
-from pc, run ARUWizard.exe from the extracted folder. it will run the RUU utility & flash back to stock
Sent from my HTCONE using Tapatalk
Installing Ubuntu
Not Linux savy at all, but I'll install Ubuntu. I'll let you know when I'm able to boot into it. Thanks.
tdhite said:
Are you Linux savvy at all? All this crap is far easier on Linux. I guarantee the drivers are absolute cakewalk -- there isn't a specific driver at all, just a rule to tell the kernel about the device.
I can give you the udev rule for the phone if you are sick of trying to get Windows to work. The Android SDK is also quite easy to install.
If you want to try, just install Ubuntu 12.04 LTS. Later versions also work, but that version is the current stable release. I can help from there.
Click to expand...
Click to collapse
Ogre77497 said:
Not Linux savy at all, but I'll install Ubuntu. I'll let you know when I'm able to boot into it. Thanks.
Click to expand...
Click to collapse
When you get it installed, login and open a terminal windows (it'll install Unity by default, so click on the first button on the left sidebar and search for terminal, then click on it), then type exactly the following (cut/copy/paste should do it too) noting that the first command will make you give your password since sudo requests root level access:
sudo apt-get update -y
sudo apt-get install -y wget openjdk-7-jdk
wget http://dl.google.com/android/android-sdk_r22.3-linux.tgz
mkdir ~/bin
cd ~/bin
tar xvzf ~/android-sdk_r22.3-linux.tgz
cat >> ~/.bashrc <<EOF
if [ -d ${HOME}/bin/android-sdk-linux ]; then
PATH+=":${HOME}/bin/android-sdk-linux/tools"
PATH+=":${HOME}/bin/android-sdk-linux/platform-tools"
fi
export PATH
EOF
exit
That last command will exit the terminal. Start another and it'll read the .bashrc file and presto -- you have SDK access from everywhere.
Then, type this command:
android
That will bring up the SDK UI -- let it download/install all of the latest stuff (r22 of the tools and whatnot).
When done, close the android SDK window.
Type adb (bet it works), but fastboot will require root access (I'm not going to teach you how to get around that yet -- no problem, you just run sudo and I'll show that in a sec).
Finally, plug in your HTC One and type adb devices and let's see if it didn't just know it already.
Lemme know.
Ubuntu 12.04 LTS Installed
I have Linux running on my Dell laptop. No internet though. Something about installing broadcom drivers ..
What do I need to do, sir?
tdhite said:
Are you Linux savvy at all? All this crap is far easier on Linux. I guarantee the drivers are absolute cakewalk -- there isn't a specific driver at all, just a rule to tell the kernel about the device.
I can give you the udev rule for the phone if you are sick of trying to get Windows to work. The Android SDK is also quite easy to install.
If you want to try, just install Ubuntu 12.04 LTS. Later versions also work, but that version is the current stable release. I can help from there.
Click to expand...
Click to collapse
Ogre77497 said:
I have Linux running on my Dell laptop. No internet though. Something about installing broadcom drivers ..
What do I need to do, sir?
Click to expand...
Click to collapse
Check PM
bigdaddy619 said:
Check PM
Click to expand...
Click to collapse
@bigdaddy619 probably got you covered, but if not, let me know. Your friend for Broadcom chips on Dell boxes is here:
https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx
The gist is pretty simple. If you don't know which wireless you have, do this:
1) widen your terminal window so you have ample room (good and wide);
2) run sudo lspci -v
Hunt down the Broadcom info -- it'll say which device is your broadcom wifi. Just need the numbers.
Working ..
I feel like I'm making some progress here, but it's still not being recognized. Everything worked great up until ...
After closing the SDK window, I connected the HTC One, and "Fastboot USB" came up on my phone. I typed adb devices and got a line "List of Devices attached" by nothing was showing as being attached.
If I enter a fastboot command, it hangs saying "waiting on device".
tdhite said:
When you get it installed, login and open a terminal windows (it'll install Unity by default, so click on the first button on the left sidebar and search for terminal, then click on it), then type exactly the following (cut/copy/paste should do it too) noting that the first command will make you give your password since sudo requests root level access:
sudo apt-get update -y
sudo apt-get install -y wget openjdk-7-jdk
wget http://dl.google.com/android/android-sdk_r22.3-linux.tgz
mkdir ~/bin
cd ~/bin
tar xvzf ~/android-sdk_r22.3-linux.tgz
cat >> ~/.bashrc <<EOF
if [ -d ${HOME}/bin/android-sdk-linux ]; then
PATH+=":${HOME}/bin/android-sdk-linux/tools"
PATH+=":${HOME}/bin/android-sdk-linux/platform-tools"
fi
export PATH
EOF
exit
That last command will exit the terminal. Start another and it'll read the .bashrc file and presto -- you have SDK access from everywhere.
Then, type this command:
android
That will bring up the SDK UI -- let it download/install all of the latest stuff (r22 of the tools and whatnot).
When done, close the android SDK window.
Type adb (bet it works), but fastboot will require root access (I'm not going to teach you how to get around that yet -- no problem, you just run sudo and I'll show that in a sec).
Finally, plug in your HTC One and type adb devices and let's see if it didn't just know it already.
Lemme know.
Click to expand...
Click to collapse
Ogre77497 said:
I feel like I'm making some progress here ....
Click to expand...
Click to collapse
Hang in, writing you some instructions, just a few minutes -- just need to get a udev rule into place but I want to make it easy for you.
---------- Post added at 08:18 PM ---------- Previous post was at 07:50 PM ----------
tdhite said:
Hang in, writing you some instructions, just a few minutes -- just need to get a udev rule into place but I want to make it easy for you.
Click to expand...
Click to collapse
Actually -- let's walk before we run. I loaded up Ubuntu real quick to assure I can duplicate what I want you to see. So, do this:
1) connect (if not already connected) the HTC to the usb port so you get 'fastboot (usb)' as normal;
2) type the following:
sudo su
lsusb -v >/tmp/lsusb.txt
chmod 666 /tmp/lsbusb.txt
exit
Now, edit that file in the text editor (just search for 'edit' like you did for 'termina' and select the "Text Editor". When you get that open, have it "File | Open" the file above -- /tmp/lsusb.txt
Then look through for text similar to what I give below. If we get that -- I need the idVendor line -- it should read: "idVendor 0x0bb4 High Tech Computer Corp."
I copied some sample output from my own machine so you can see how it should look:
--------
probably a bunch of stuff we don't care about, then something like...
Bus 001 Device 005: ID 0bb4:0ff0 High Tech Computer Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0bb4 High Tech Computer Corp.
idProduct 0x0ff0
bcdDevice 1.00
iManufacturer 1 htc, Inc
iProduct 2 Android 1.0
iSerial 3 XXXXXXXXXXXX (I X'd this out -- it'll be your device serial id).
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
and a bunch more stuff...
If we don't see that, we got troubles. If we do -- we'll make a udev rule to load it up for adb and fastboot.
It appears he's bricked, when we first mounted the phone to the PC and it tried to install drivers we got QHSUSB_DLOAD which usually indicates a brick.
The strange thing was we could still access fastbootusb and the PC would recognize it being in fastboot. But any other command then fastboot devices would lock up the bootloader and fail.
Getting Closer
That's exactly it. "idVendor 0x0bb4 High Tech Computer Corp."
Finally, something worked. Thanks.
Now, edit that file in the text editor (just search for 'edit' like you did for 'termina' and select the "Text Editor". When you get that open, have it "File | Open" the file above -- /tmp/lsusb.txt
Then look through for text similar to what I give below. If we get that -- I need the idVendor line -- it should read: "idVendor 0x0bb4 High Tech Computer Corp."
In the past 3 months or so I noticed that my Mi5 3GB 32GB is not recognized by my PC anymore. I didn't care too much because I hardly connect my phone to PC.
I was running the lastest xiaomi.eu Rom unrooted.
So on Thursday, I deleted my OS by mistake, therefore I do not get past the Mi Logo.
I can boot into TWRP Recovery & Fastboot however, there is not code when using CMD adb/fastboot devices such as 1cwe3f23.
Also, I read about the EOL method aka test point method, to force a connection as Qualcomm driver with no success. Different PCS dont recognize any drivers.
The battery is not an issue because I can easily charge my phone to 100% and it can hold its charge, therefore I do not think it is a battery related issue.
What i did so far :
- used 3 differenct USB C cables and PC -> phone still not recognized
- Installed all lastest driver on Drivers -> phone still not recognized
- tried to use the test points method -> phone still not recognized
- tried Miflash tool -> phone is still not recognized
- tried Mi PC Guide -> didn't work either
Then I read somewhere that I can use a OTG cable with a pen drive
- OTG storage is not recognized in TWRP recovery and cannot be selected. [OTG STORAGE 0MB even if different pen drives are connected]
SO my Main problem is not the phone itself, it is that I cannot get any data onto the internal memory because I can't get past TWRP.
Please help me out since I really struggling with this problem for the past 7 days and I'm desperate now for any kind of help.
Greetings and thanks in advance.
amando1991 said:
SO my Main problem is not the phone itself, it is that I cannot get any data onto the internal memory because I can't get past TWRP.
Click to expand...
Click to collapse
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Hi bro
same as me, 4 days ago...
system, vendor error
flashing stock rom miui9 via twrp
although the error twrap will only provoke usb computer,
if it works usb computer, try flashing by using miflash...
goodluck
Sory bad englis
moo113 said:
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Click to expand...
Click to collapse
I did as you recommended and used Ubuntu. However also there the system didn't recognize the phone when plugged. It may because I am not fully familiar with Ubuntu. I would appreciate if you could point me in the direction of a tutorial.
same as me, 4 days ago...
system, vendor error
flashing stock rom miui9 via twrp
although the error twrap will only provoke usb computer,
if it works usb computer, try flashing by using miflash...
Click to expand...
Click to collapse
could you be more precise please? How did you overcome not having a PC conncetion?
Currently, I am not able to transfer any kind of data to the phone either by PC or OTG. Furthermore, the internal storage is completely empty after wiping everything by mistake.
I have twrp working fine, but without any data on the device, I cannot use it. Also, the device only stays in fastboot for roughly 20 secs before it turns off.
any help is welcomed. Thank you
EDIT : I got Ubuntu to work but its the same process. My phone is not recognized and running the command adb devices gives me
"list of devices" .... thats not! Nothing ! usally there is the code Phones ID but nothing there
amando1991 said:
EDIT : I got Ubuntu to work but its the same process. My phone is not recognized and running the command adb devices gives me
"list of devices" .... thats not! Nothing ! usally there is the code Phones ID but nothing there
Click to expand...
Click to collapse
A number of different issues could be here.
#1 Firstly, ensure you've installed openvm tools and reboot. This should enable things like hardware pass through.
$ apt-get install open-vm-tools open-vm-tools-desktop
$ sudo init 6
Then, follow these instructions for the pass through (may be slightly different, but very similar) https://forum.xda-developers.com/showthread.php?t=570452
#2 Type "adb" and see what version is in use in the first line of output. If it's 1.0.0.32 or older, it might be an issue. Try installing the following packages:
$ sudo apt-get install android-tools-fastboot android-tools-adb
You might need to find a newer version elsewhere, Ubuntu repos are often old. Google around for 1.0.36 or newer. This could solve your issue.
#3 Ensure you have the necessary rules for the Mi 5. There's a few different hardware models. The Arch Wiki can walk you through it better than I can: https://wiki.archlinux.org/index.php/android#Connect_device (ignore the package hyperlinks, they're arch-specific). Only do this if you've properly configured the pass through from #1. Do F"igure out device IDs" and then "Adding udev Rules". Instead of the "udevadm" command run
$ sudo service udev restart
If you're still not detected, no idea.
moo113 said:
A number of different issues could be here.
#1 Firstly, ensure you've installed openvm tools and reboot. This should enable things like hardware pass through.
$ apt-get install open-vm-tools open-vm-tools-desktop
$ sudo init 6
Then, follow these instructions for the pass through (may be slightly different, but very similar) https://forum.xda-developers.com/showthread.php?t=570452
#2 Type "adb" and see what version is in use in the first line of output. If it's 1.0.0.32 or older, it might be an issue. Try installing the following packages:
$ sudo apt-get install android-tools-fastboot android-tools-adb
You might need to find a newer version elsewhere, Ubuntu repos are often old. Google around for 1.0.36 or newer. This could solve your issue.
#3 Ensure you have the necessary rules for the Mi 5. There's a few different hardware models. The Arch Wiki can walk you through it better than I can: https://wiki.archlinux.org/index.php/android#Connect_device (ignore the package hyperlinks, they're arch-specific). Only do this if you've properly configured the pass through from #1. Do F"igure out device IDs" and then "Adding udev Rules". Instead of the "udevadm" command run
$ sudo service udev restart
If you're still not detected, no idea.
Click to expand...
Click to collapse
Thank you again for the help!
Unfortunately, it appears that my device is still not recognized by either Ubuntu or Win10.
I Have taken the necessary steps to install Ubuntu and update the adb drivers (1.0.39) but still no luck so far.
It really pisses me off since I was stupid enough to wipe the internal storage ☹ and not I am not able to transfer any data to the devices again.
Any other out of the box ideas?
amando1991 said:
Thank you again for the help!
Unfortunately, it appears that my device is still not recognized by either Ubuntu or Win10.
I Have taken the necessary steps to install Ubuntu and update the adb drivers (1.0.39) but still no luck so far.
It really pisses me off since I was stupid enough to wipe the internal storage ☹ and not I am not able to transfer any data to the devices again.
Any other out of the box ideas?
Click to expand...
Click to collapse
You configured the USB pass through to your Ubuntu host? Double check you followed #3, and then run sudo fastboot devices. That step is tricky for some.
Reconnect your phone to your Ubuntu host (in fastboot) and run "dmesg -T", see what errors are present. If you have no errors, I would image it's a configuration issue. Other than that I'm out of ideas.
moo113 said:
You configured the USB pass through to your Ubuntu host? Double check you followed #3, and then run sudo fastboot devices. That step is tricky for some.
Reconnect your phone to your Ubuntu host (in fastboot) and run "dmesg -T", see what errors are present. If you have no errors, I would image it's a configuration issue. Other than that I'm out of ideas.
Click to expand...
Click to collapse
OMFG!!! First of all, thank you for support and your patience. I really appreciate it.
HOWEVER, all it was is that the USB PORT was full of dust( literally tons!) which appears to have allowed to charge the phone but seemed to have cloaked up some part of the responsibile for a usb connection to a computer.
Stupid me should have known this because the usb port was kinda wobbly which I had mistaken for degradation using the phone for almost 2 years
MANY THANKS!
moo113 said:
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Click to expand...
Click to collapse
Hey , I was researching about my issue and came up to this. I'd be really glad if you can sort me out with this. I have the same mobile , by mistakenly wiped out the phone including the internal storage , my pc does not detect the device , and whenever i go to fastboot mode to try something like miflash , it goes back to twrp after 15 seconds. Also , i tried several OTG's but none of them get detected on TWRP , and I am stuck on this thing for almost a week now . Please guide me on how to sort this out . i basically just downloaded adb files , miflash , etc from the internet and never reinstalled them. also i used several usb c cables to connect to pc and even then device manager does not detect it . thank you . i would really appreciate your reply.