Database Develop

SD Card Unmounting-CM-4.1.11.1 :)

I installed Win 7 Ultimate version on my system, these past couple of days.
I am having an issues mounting my G1.
It mounts for like 15 seconds and unmounts itself.
I have the 1.6 drivers, installed.
ADB works fine.
Is there a special trick to getting this mounted with Win7.
I didn't have issues with XP.
Thanks for an help

Mikey1022 said:
I installed Win 7 Ultimate version on my system, these past couple of days.
I am having an issues mounting my G1.
It mounts for like 15 seconds and unmounts itself.
I have the 1.6 drivers, installed.
ADB works fine.
Is there a special trick to getting this mounted with Win7.
I didn't have issues with XP.
Thanks for an help
Click to expand...
Click to collapse
im using Win 7 Prof and I keep getting an message that tells me that I could have errors so to scan it but I just choose to continue without scanning and it mounts alright, so no special trick here sorry

I have the same problem on windows 7.
when it does it leave the phone plugged in.
safely remove hardware from within windows.
unplug the phone
plug it back in
wait 20 secs
mount

I get that error message as well.
Edit: Off-Topic.......
What's with win7 wanting to back up everytime i plug in my phone???
Anyone getting that as well?

For the error make sure the partition table of the card is "msdos"
You can check by going to recovery console and typing the following
Code:
parted /dev/block/mmcblk0 print
No idea about win7 wanting to backup

Fingerlickin said:
For the error make sure the partition table of the card is "msdos"
You can check by going to recovery console and typing the following
Code:
parted /dev/block/mmcblk0 print
No idea about win7 wanting to backup
Click to expand...
Click to collapse
yea my partition table is msdos ... dont know why i get that error :\

I just got word from a fellow XDA member:
yea google probably wont make win 7 drivers until win 7 is officially released
Click to expand...
Click to collapse

Yea. No official windows 7 drivers so you should expect problems

alritewhadeva said:
Yea. No official windows 7 drivers so you should expect problems
Click to expand...
Click to collapse
Deja Vue

Well you can backup everything and repartition the card.
Post 3 HERE has a script that will help. Follow instructions in the post and do options 9, 1, backup to pc, 11, 10 in that order. You won't loose your apps but you will loose your dalvik-cache so the first boot will take up to 15 mins. If you don't already have your card partitioned then you can just do 1, backup to pc, 11.

I guess i'll be using aFile more often till they push the drivers out.

[VIDEO] 10min Root complete Guide

NEW 10MIN VIDEO, I show two different methods to getting adb recovery and i show wifitether working
Complete stock at startup i go through installing htcsync, android-sdk, copy files to sd card, got root, superuser.apk working and wifitether in under 10mins!!!!
This is for complete Noobs,
YouTube - Root Droid Incredible in 10mins
files:
MyHost Direct Download
Mirror #1
Mirror #2
Used method on both a Win7 64Bit Computer and WinXP 32Bit computer, perfect on each computer

Follow the steps in this video.
Before you plug in your usb you can also.
Hold the volume down button then click power.
Highlight Recovery as soon as possible.
Plug in your usb and click the power button at the same time. (To go into Recovery mode)
Follow the steps in this video.
Worked for me.
Thanks for posting!

So I already have sdk intalled but I installed yours anyway and placed it on the c-drive. But for some reason you get an error when you go through sdk setup, I don't. I wants to intall the 15 drivers that I already have installed at the other sdk location. Any clue way I don't get the error you do?
Also when I'm in the cmd prompt I don't get the error message you do either. I just get "error: device not found"

blw1230 said:
So I already have sdk intalled but I installed yours anyway and placed it on the c-drive. But for some reason you get an error when you go through sdk setup, I don't. I wants to intall the 15 drivers that I already have installed at the other sdk location. Any clue way I don't get the error you do?
Also when I'm in the cmd prompt I don't get the error message you do either. I just get "error: device not found"
Click to expand...
Click to collapse
how about trying my method on a computer you havnet tried on yet. one you havent installed android adk and htcsync
If you can get a windows 7 x64 system since thats the one i use

mejdam said:
how about trying my method on a computer you havnet tried on yet. one you havent installed android adk and htcsync
If you can get a windows 7 x64 system since thats the one i use
Click to expand...
Click to collapse
I've tried on 3 seperate computers. One Vista x32 and two XP... who knows how fast they are, I don't have a sundial.

mejdam said:
NEW 10MIN VIDEO, I show two different methods to getting adb recovery and i show wifitether working
Complete stock at startup i go through installing htcsync, android-sdk, copy files to sd card, got root, superuser.apk working and wifitether in under 10mins!!!!
This is for complete Noobs,
can you say what brand , size and speed of sd card you are using and what format and type of files. Ie music/apps.... lots of file and or names. thank you
Click to expand...
Click to collapse

vapehooka said:
mejdam said:
NEW 10MIN VIDEO, I show two different methods to getting adb recovery and i show wifitether working
Complete stock at startup i go through installing htcsync, android-sdk, copy files to sd card, got root, superuser.apk working and wifitether in under 10mins!!!!
This is for complete Noobs,
can you say what brand , size and speed of sd card you are using and what format and type of files. Ie music/apps.... lots of file and or names. thank you
Click to expand...
Click to collapse
im running a class 6 16gb card. by trendmicro
Click to expand...
Click to collapse

full or not full, formatted to fat32 or fat? And does your drivers in windows say the phone is to storage drives after you get adb shell to work?
CAn you try this on a friends windows7 32bit and or ubuntu 10.3 or xpsp2 ?
Any help will be greatly appreciated .
Thank you
T

vapehooka said:
full or not full, formatted to fat32 or fat? And does your drivers in windows say the phone is to storage drives after you get adb shell to work?
CAn you try this on a friends windows7 32bit and or ubuntu 10.3 or xpsp2 ?
Any help will be greatly appreciated .
Thank you
T
Click to expand...
Click to collapse
haha. You sound like you are in the same boat as me... Everyone seems to say the $10 PNY card from Best Buy works so I went and got one, didn't work. Everyone trying the Droid's 16GB card gets it to work so I bit my lip and ask to borrow my ex's for a few minutes... no go.
Folks who are successfull using the PNY 2GB card from Best Buy, Which method are you using? (Volume Down + Power or Main Menu + Power)
Also, does it matter at what point you start running the adb shell loop and plug in the usb cable? I've tried all suggested methods and not a single thing is working.

Ive tried like 9 million ways before this. Has this failed for anyone? Im still doubtfull it will work. Im definately envious. Nice vid

i wont have access to a winxp computer till tonight when i go to work. I'll try it on a windows xp computer and let you know.

Rooted mine on 32 bit winxp

tried it, didnt work, tried about 5 reboots on 3 sd cards
im going to be the last person left on the planet to root

socalracer said:
tried it, didnt work, tried about 5 reboots on 3 sd cards
im going to be the last person left on the planet to root
Click to expand...
Click to collapse
lol I can't get it working either, on Vista 32 with several different methods and sd cards...

socalracer said:
tried it, didnt work, tried about 5 reboots on 3 sd cards
im going to be the last person left on the planet to root
Click to expand...
Click to collapse
You are not alone. I have used multiple computers. From Win2003 with Quad Xeon and 16gb RAM, Athlon 64X2 WinXP 64bit with 4GB RAM to P4 w/ht 1.6 ghz with 2 GB ram on WinXP 32bit.... 16gb DROID microSD or PNY 2GB from Best Buy (both confirmed cards). Not a single thing has given me even the glimmer of hope.

I have tried this using your methods but still a no go.
What do we think. is this a phone problem, sdcard problem or computer problem. I have used 4 different sdcards and I am Windows 7 64bit. Haven't tried a Win98 box. Anyone think that will make a difference?

I used your info for the su install and wifi teathering, but the recovery method didn't work. I had to use the insert the card method. Woohoo I got wifi teathering workin'.

Anyone got root explorer working? It installs but then I get a force close when trying to open it.

Reddog80p said:
Anyone got root explorer working? It installs but then I get a force close when trying to open it.
Click to expand...
Click to collapse
The logcat should tell you why, but try this:
Code:
adb shell
$ su
# whoami
What do you get?

mejdam said:
NEW 10MIN VIDEO, I show two different methods to getting adb recovery and i show wifitether working
Complete stock at startup i go through installing htcsync, android-sdk, copy files to sd card, got root, superuser.apk working and wifitether in under 10mins!!!!
This is for complete Noobs,
after 3 days trying every method here. went to walmart got myself the 2 gig PNY card, FIRST shot worked flawless.
only on mine it did not stick had to use second method next try which wasn't difficult at all.. 1 minute tops and added the commands to allow the su to stick.
thank you for your video and time
Click to expand...
Click to collapse

[Q] no more adb ??

hi all i'm not new of this forum and i think i know much of this but in these days i'm having trouble with adb.
i'm not in my house (where it works perfect) but i'm in austria, where i live and have a job.
i'm trying to "install" adb in several pc, windows (xp, seven) and linux (both ubuntu desktop and netbook 10.10).
the error is ever the same:
1. i download the sdk from http://developer.android.com/sdk/older_releases.html
i prefer use the oldest release because i just use adb and nothing else.
2. in win7 the adb driver comes installed automaticaly as soon as i plug my phone to pc
in winxp not, but in sdk 1.1 r1 there are the usb drivers.. (that in my house with both 1.1 and 1.6 worked fine)
in linux i downloaded his right sdk and edited the 51-android.rules and add the executable permission.
(in my house i used ubuntu 8.04 and there wasnt need to edit this file..)
the problem is that when i do:
adb devices (or ./adb devices)
i can see: daemon start etc... list of deviced attached *empty*
there's nothing! i tried a lot of time, with xp, seven, ubuntu.. don't know what to do more.
what should i do?
htc dream - rooted - death spl and 2.22.23.02 radio - amon ra 170 - cm 508 (and also 601)
thanks

You've tried different methods and even different os's, seems to me your common factors are usb port and cable.
I use ubuntu 10.10 and setup fastboot just last week. I grabbed the small package (adb and fastboot binaries) rather than the whole sdk.
My first question is, what are the results of lsusb when g1 is connected running linux?
sent via XDA app on my G1/Dream Rogers
hboot-1.33.0013d
radio-2.22.27.08
update-cm-6.1.0-RC1-DS-2708port_S

phil_chetcuti said:
You've tried different methods and even different os's, seems to me your common factors are usb port and cable.
I use ubuntu 10.10 and setup fastboot just last week. I grabbed the small package (adb and fastboot binaries) rather than the whole sdk.
My first question is, what are the results of lsusb when g1 is connected running linux?
sent via XDA app on my G1/Dream Rogers
hboot-1.33.0013d
radio-2.22.27.08
update-cm-6.1.0-RC1-DS-2708port_S
Click to expand...
Click to collapse
thanks for have answered!
yes i've tried also in 3 different pc's, and my cable works good :/
lsubs can see my device, now i havent my ubuntu with me, but yes, it can see my device!
it's so strange because it never happened before, using xp, seven or ubuntu 8.04 in my house, it all worked fine since the first installation
Edit:
I added a screenshot to let you see it. yes i'm using a virtual machine but because i'm at work now.
in my pc with ubuntu netbook it's the same, and lsusb can see it too like here.
Edit 2:
I tried with backtrack 3 (from pendrive) and it works.. also without editing 51-android.rules ..... F**K

[Q] Help with bricked HTC One

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."

No OS on phone! OTG USB / conncetion to PC not recgonized! Seeking Help

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.