Develop Bugs

[q] • • • DONATING TO WHOEVER SOLVES MY PROBLEM • • •

[q] • • • DONATING TO WHOEVER SOLVES MY PROBLEM • • •
My device is stuck at Serial - v1.01 screen
• Bootloader mode (backlight+power+reset) doesn't work
• SOFT KEYS + RESET give 2 options (press 0 or X)
• My Windows 7 recognizes the device, although as an Unknown Device.
• I can enter MTTY through COM1 port but I can't type anything (ENTER key doesn't work, normal letters don't work, CTRL + V works, DELETE works - idk whats the problem).
• Can't flash - different errors occur (some ROMs give 101 connection error, some 112 error)
• I have browsed this forum for 4 days and found many tips - none of them worked
• Device starts blinking Serial/USB when entering USB cord (sometimes blinks and stays at USB)
PS: I found an interesting thread about win7 and its drivers - it was said to update my Mobile Device driver to XP one but the problem is, I don't see Mobile Device in my Device manager. I only see Unknown Device at Serial Bus Controllers.
WILLING TO DONATE TO THE ONE WHO SOLVES MY PROBLEM AND GETS MY DEVICE UP & RUNNING

Welcome to forums
I would suggest using a Windows XP machine to perform flashing and perhaps a Doc format
Good luck,

paulsrik said:
My device is stuck at Serial - v1.01 screen
• Bootloader mode (backlight+power+reset) doesn't work
• SOFT KEYS + RESET give 2 options (press 0 or X)
• My Windows 7 recognizes the device, although as an Unknown Device.
• I can enter MTTY through COM1 port but I can't type anything (ENTER key doesn't work, normal letters don't work, CTRL + V works, DELETE works - idk whats the problem).
• Can't flash - different errors occur (some ROMs give 101 connection error, some 112 error)
• I have browsed this forum for 4 days and found many tips - none of them worked
• Device starts blinking Serial/USB when entering USB cord (sometimes blinks and stays at USB)
PS: I found an interesting thread about win7 and its drivers - it was said to update my Mobile Device driver to XP one but the problem is, I don't see Mobile Device in my Device manager. I only see Unknown Device at Serial Bus Controllers.
WILLING TO DONATE TO THE ONE WHO SOLVES MY PROBLEM AND GETS MY DEVICE UP & RUNNING
Click to expand...
Click to collapse
When i am home i can help you!

d-two said:
When i am home i can help you!
Click to expand...
Click to collapse
My MSN - MOD EDIT: REMOVED EMAIL

orb3000 said:
Welcome to forums
I would suggest using a Windows XP machine to perform flashing and perhaps a Doc format
Good luck,
Click to expand...
Click to collapse
I have tried on 2 XP machines - laptop and PC both
Maybe the problem is that its COM1 port that works and mtty doesn't let me type anything.
How could I get USB port to work ?

paulsrik said:
I have tried on 2 XP machines - laptop and PC both
Maybe the problem is that its COM1 port that works and mtty doesn't let me type anything.
How could I get USB port to work ?
Click to expand...
Click to collapse
I am now Home but it is too late... Sorry, tomorrow i am back home earlier...

i wrote instruction here about flashing with windows 7. update your "unknown device" driver like it was described. do you have x86 or x64 edition? and have you removed sd and sim card?

Forgetting to remove the SD card is usually the problem. You really need to do that, it's not optional. If it's not the SD card, select the unknown device in device manager, right click, delete the device and reboot. Then try the usual instructions on flashing under Win7. Disable USB connections in WMDC. Put device in bootloader mode and connect it. When Mobile Device appears in device manager, update to the correct drivers. Try rebooting between steps if you get stuck. My drivers seem to get corrupted from time to time for whatever reason and this works for me. You need to see and select the USB option in mtty, it won't work otherwise.

l2tp said:
i wrote instruction here about flashing with windows 7. update your "unknown device" driver like it was described. do you have x86 or x64 edition? and have you removed sd and sim card?
Click to expand...
Click to collapse
I only see Unknown device, not Mobile Device or something else.
Unknown device driver can not be updated.
I have removed both cards, SIM and SD.
onurdndar said:
Forgetting to remove the SD card is usually the problem. You really need to do that, it's not optional. If it's not the SD card, select the unknown device in device manager, right click, delete the device and reboot. Then try the usual instructions on flashing under Win7. Disable USB connections in WMDC. Put device in bootloader mode and connect it. When Mobile Device appears in device manager, update to the correct drivers. Try rebooting between steps if you get stuck. My drivers seem to get corrupted from time to time for whatever reason and this works for me. You need to see and select the USB option in mtty, it won't work otherwise.
Click to expand...
Click to collapse
Removed both cards, I've seen that tip around.
As I said my device stays at Serial/v1.01 screen when pressing BACKLIGHT+POWER+RESET. Only Soft buttons + reset work, brings 2-option screen with white background (0 and X).
As I also said, I have tried same thing over and over in 3 different computers: laptop with XP, PC with XP and another PC with WIN7(current).
Installed ActiveSync from original SPV M5000 CD to both XPs, still doesn't flash and mtty still opens only COM1 port (COM4 for laptop).
I think if I could get MTTY to work, I'd be okay. But how can I get USB port working ?

If you've done everything offered here, the remaining options are faulty USB cable and faulty USB socket.
By the way, this is not the kind of thing people donate for around here. I'm personally not trying to help for any theoretical reward.

onurdndar said:
If you've done everything offered here, the remaining options are faulty USB cable and faulty USB socket.
By the way, this is not the kind of thing people donate for around here. I'm personally not trying to help for any theoretical reward.
Click to expand...
Click to collapse
I am very frustrated and willing to do whatever it takes to save my device.
Now are you saying its both, USB cable and socket that are incorrect or just one of them. Please give me an example which cable do you use.
Thanks

If at the beginning you were able to see your device from W7,than your cable and every thing is ok.
your stock with a device with no rom,so i think this is why your W7 don't see your wince phone.(it could be to a rom error or fault of manipulation done by you!!!battery for example,etc...).
solution:
1)go to a close htc support technician close to you and he will load a Rom to your phone Board.
2) PM me to sell and chip you my HTC Universal,,

[Q] USB connection fails on 3 different PCs

I wanted to root my phone and flash a costum rom... unfortunately my DHD (2.2.1) is T-Mobile branded, so i had to create a goldcard in order to downgrade from 1.75.111.2 to 1.32. When it came to temproot it manually with cmd i had to plug my DHD into my PC in load only mode, usb debugging activated.
I knew already that my DHD wont recognize my PC or the other way round (i somehow broke it when i deleted the htcsync drivers.exe from my sd card), but i thought maybe it would somehow work in usb debugging mode.
Well, it didnt(phone not found).
i then focused on repairing my usb connection, so i tried it on 2 other pcs (mine is w7, the other ones are xp and win7) but it all failed
(xp asked for drivers, which i installed directly from htc.com today(on all pcs(plus i removed and reinstalled them all properly))/win7 did nothing/mine said that it fails to connect and that i should use a usb 2.0 port(well all ports are usb 2.0, i also tried usb3.0))
evertime i plugged my DHD in i was asked which connection i want to use, none worked, i also restarted my phone several times (usb connected and without) when i type in #7284# (or *#7284# i tried both) it says: connection failure or invalid mmi code
Finally i resetted my phone and did it all again! But it wont work!
please help me!

Hi...It looks like a driver issue...
If your drivers are installed correctly, in your win-7 Device manager it will show DHD.
I would suggest to Re-install HTC Sync from HTC website - Run it again and give it a try

doesnt work either.... win7 says the device does not run properly, my phone does nothin unusual...
i wonder if htc could fix the issue... this would be my last option
however i believe in you guys at xda!

how did you reset your phone?
Did you install the android SDK? Does adb recognize your phone? (run "adb devices", if your device is listed, everything should be fine)
On my win7-machine, the HTC-Software gives me an error message (along the lines of "phone doesn't respond" or something like that) but adb works nonetheless.

thank you for your answer but im afraid it didnt work... i installed the usb driver pack on sdk but i couldnt find it under sdk/usb driver..., however i found some files -> android/android-sdk/extras/google/usbdriver/amd64 -> usbdrivercoinstall2.dll... i tried to install this driver in hardware manager, and i tried to install an adb.exe which i found in my downgrade folder as a driver. but win7 said no driver installation is necessary the "best" drivers are already installed (win7 aint gonna install anything)
also my dhd is found under unkown device, -this device is deactivated because it made errors- "Dieses Gerät wurde angehalten, weil es Fehler gemeldet hat. (Code 43)"
well i deinstalled it and searched for new hardware, he now says the drivers are installed properly please restart however i neither see my sd card nor my devices name (instead unkown device with this little yellow triangle)
btw. for reset i used my android reset (settings -> sdcard -> reset)

It is normal, the HTC Sync turns on the USB debug?

Have the same issue. My DHD can be connected to the PC no other way than charge mode, no matter is usb debugging turned on or off. Tried 2 PCs with W7 and 1 PC with Ubuntu 10.04. This trouble appeared several days ago. Wipe didn't help. Thinking of re-installing firmware, but it seems like hardware problem. An engineer in our service center said it might be motherboard malfunction.
Some ways of solving this problem are described here: http://goo.gl/2eMcP But none of those solutions helped me. If anyone can help, please advise.
UPD: re-installing the firmware had no success - connection with PC failed. 95% hardware problem, will take it to service center.

Guys I know it's a stupid advice, but I had same problems (suddenly my connection with pc didn't work anymore): did you try to change usb cable?

giegi_dc said:
did you try to change usb cable?
Click to expand...
Click to collapse
tried 3 cables and 3 PCs

i just found a solution for me : i tried a forth pc (win7) freshly installed htcsync + android sdk + !downloaded! (not properly installed) adb drivers (which i surprisingly did not need) well i plugged my DHD in and he installed all drivers, but never asked for an adb driver. instead he had problems installing 7 different bluetooth drivers for my DHD (???)^^
it just worked for me this way (also worked for debugging mode + load only mode (for radio s-off/hboot s-off))
:|)
well it's not exactly a permanent solution just a temporal way to root my phone, but in worst case i think its nessesary to reinstall win7 on your pc....

adb fastboot driver problem

Hi,
i tryed to get the Desire working with adb and everything works fine. I downloaded HTC Sync, installed only the drivers, and the adb interface worked with the Desire. But if i reboot in bootloader and use fastbootinterface it doesn't work.
fastboot devices get no result.
I downloaded unrevoke modified drivers, i also tryed to uninstall HTC driver and install only the modifed drivers. I also tryed to use this drivers:
http://forum.xda-developers.com/showthread.php?t=1161769
but always the same problem:
The device manager shows adb Intreface and there the HTC bootloader, but with and yellow !. properties of the Device shows me following error:
original Error log said:
Das Gerät kann nicht gestartet werden. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
Translation in my own words: said:
The devices can not be startet (Code10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
And i installed the drivers correctly. So with settings, reboot and tha with deactivate the driver signature.
I hope you can help me

You should uninstall everything and start from the beginning. HTC sync clearly messed something up.
First, try to reinstall hboot drivers.

allready tryed but i get the same error.

google "the devices can not be started (code 10)"
happened to me before, its a windows problem. u have to delete something , cant remember what tho.

i uninstalled every thing desire also the not shown devices in devices manager. than i connected the desire in fastboot with pc and the pc gets the driver from alone. But with the error.
Thanks for the tip with the delete something. but the only results i find are something about reinstall the driver, update the driver, uninstall the driver, ask the support of the device -.-
Do you know maybe a link word what i need to delete? is it a file, an old driver,...??

http://www.google.com/url?sa=t&sour...9oGABg&usg=AFQjCNH1CYaPX1ZheHJ-vYr2Y3GDNFFvWw
try here, the thing that worked for me was deleting somthing in the registry.

thank you very much i'll try it

Just found the time to read the link.
One question? I looked for the Device Class GUID for USB. But there is no lowerfilter and upperfilter. What class is the desire?

I got a similar problem on my workstation, I got an Android Phone in device manager and nothing else, I'm not able to connect and mount desires SD Card. Windows 7 x64, on my laptop (same os) everthing works fine. My PC recognizes desire only with drivers from Android SDK software.

i think your problem is a bit diferent. Do you have a custom ROM installed?
If you did and it is an android 4.x ROM there are many Problems with USB mount. Try an app to mount the SD Card.
Back to my problem. I readed all of the site from up to down and than i deletet the Keys. After Reboot 2 times i got the bluescreen -.- after that the autorepair startet it selfs. the first couldn't repiar the system, and the second couldn't either. So i needed to reinstll windows
The good thing with this is There is difently no HTC on the PC anymore. So in what order i need to install which drivers to get the Desire in Fastboot connected?

A the moment I'm using CronMode 2.1 (previous CM 2.0, SpazeDog ICS, BravoBCM). On previous roms (all ICS based on CM9) got same problem. Laptop - ASUS S6F, Windows 7 Pro x64 - phone recognized, usb mount working fine. Desktop - Gigabyte P55-UD3, Windows 7 Pro x64 - just got Android Phone in device manager and that's all.
What app do you mean?

Try Usb mass storage toggle form the market.

Not working... Also my PC doesn't mount SD as usb storage in recovery (4ext).

nonline said:
Not working... Also my PC doesn't mount SD as usb storage in recovery (4ext).
Click to expand...
Click to collapse
You may have a usb brick. Try the "usb unbrick" option in recovery

abaaaabbbb63 said:
You may have a usb brick. Try the "usb unbrick" option in recovery
Click to expand...
Click to collapse
So why other PC/Laptopts recognize my phone proper?

nonline said:
So why other PC/Laptopts proper recognize my phone?
Click to expand...
Click to collapse
Ok then... reinstall your OS on the PC. If your tried everything, it's the last solution I can think of.

You can first try to reinstall the Driver.
Back to my problem in what order do i need to install the drivers for fastboot?

I can't reinstal OS. It's my workstation... I work on it. I tried with a lot of drivers (even from SDK), same effect "Android Phone" or ADB Interface device.

nonline said:
I can't reinstal OS. It's my workstation... I work on it. I tried with a lot of drivers (even from SDK), same effect "Android Phone" or ADB Interface device.
Click to expand...
Click to collapse
Some firms disable this ability and also SD card reading for security purposes. That can be only reason i can think of.
Sent from my HTC Desire

I'm also a sysadmin of this machine, so you can belive me, just a build-in firewall and security essentials as antivirus protection software.
My wife's Desire S shows the same problem. I think it is a driver issue. Can someone recommend a single "htc desire driver" for Windows 7 64bit?

Tab 3 SM-T210(wi-fi) flash / odin issue

Hi all,
I got given this Tab3 because the smd power socket connection guts were physically broken inside socket.
Fitted new power socket (I'm an electronics repair engineer by trade) and checked all pcb (printed circuit board) tracks leading from new fitted socket to ensure there were no hidden breaks ...... new socket refit was 100% successful .....with no solder shorts / bridges and no broken tracks leading to mainboard.
I left Tab3 on charge overnight and next day switched Tab3 on only to be greeted with dreaded .PBL and .PIT failed issue.
After extensive (days!) research I gathered together all necessary firmware and tools and decided that its an easy firmware fix if flashed to an original Samsung SM-T210 UK firmware.
(Please note I dont know past history of this Tab3 .... I dont know if it was rooted / upgraded firmware etc ..... I doubt it though as it belonged to a 7 year old)
Big issue ..... Odin flash tool won't show coms port connection on PC via USB (have tried 3 different laptops one with XP, one with Win7 32bit and another with Win7 64 bit. I've installed / uninstalled / reinstalled multiple Samsung usb drivers that were verified to work with my Tab3 SM-T210 model on each PC .... no joy. Even installed / uninstalled / reinstalled Kies from Samsung .... still wont connect when Tab3 is in download mode. Have kept PC device manager open and nothing appears in device manager. Also have tried 6 different makes of Usb A to micro Usb cables. Have disabled all antivirus, UAC, firewall and Win defender etc ... still no go!
When I go into download mode (power + Vol- +Home buttons) a warning screen does appear BUT it only shows right hand side of graphic warning ..... left hand side is totally grey from top to bottom. (LCD screen is not faulty as it displays full screen info on failed .pbl / .pit flash memory checks) When I then select Vol+ this vertical half graphic info and half grey screen disappears just leaving the backlight on .... which I assume means Tab3 is in proper download mode?
I can go to all recovery modes which allows me to factory reset and delete user cache etc .... it seems to go through the proper routines of reset but upon restart .pbl and .pit failed error in red memory check list is still there.
I can also try and flash firmware file from external sd micro card .... Tab 3 recognises firmware OK and shows Install ..../SD, but then after approx 5 minutes it restarts to failed .pbl /.pit error list again.
Apologies for long post, but from reading above issues can anyone please confirm ....
1) Is half graphic normal when going into download mode? .... or does this point to a previous incorrect or unfinished flash issue?
2) I have downloaded proper .pit flash (LT02) file and original firmware flash for my Tab3 ..... can I flash this any other way other than using Odin ....eg is there any bdm flash method (direct hard wired) flash method to motherboard from external programmer ....like they use for car ecu flash recovery?
3) As I dont know exactly whether Tab3 was rooted / flashed with wrong firmware / incomplete flash upgrade, is there a software tool that can attempt to list what firmware is on my Tab3 at present?
4) I can get into ADB recovery within recovery mode but havent a clue how to use this method .... is this a possible recovery method to use, as I can see SMT210 ADB device in PC device manager when going into recovery mode?
many thanks in advance for help, :good:
Tab3SMD
OK all, here's more info .......AND another additional issue!
I got stuck back in again tonight because not knowing anything about Tab3 ADB recovery mode was bugging me, so here's what extra I've done so far
While "poking my nose" into tonnes more Xda forum troubleshooting guides I discovered I might need PitMagic tool to try and sort my .Pit partition error via ADB recovery mode.
I tried to find Pitmagic but discovered this is now part of EFS Professional, so downloaded EFS Pro and found this got me nowhere as I needed to also install Android SDK .... which also requires Java Development kit, so I downloaded the full Android Studio and Java JDK 8u91 and installed all (about 1.2Gb and requires ~ 4.2Gb hard drive space!)
Anyway, I now ran Android Studio and then ran EFS Professional, opened my Tab3 into ADB recovery mode and connected Tab3 and PC via usb .....
All looking good EFS reported
Initialising ADB server ..... Okay.
ADB server is running!
Searching for device..... OK
Connecting to device .....OK
Checking device status .....
THEN BAMMMM ....popup from EFS
Connected device is currently UNKNOWN
Please ensure ADB server has been authorised by the connected device by confirming your PC's RSA fingerprint, then press OK to continue
like, wtf! .... one step forward and 6 back!
Can anyone please tell me what this means or better still how to proceed from here?

Anyone?
Anyone??? .....Tab3 is still soft-bricked
I did figure out how to use ADB flash recovery mode using PC.
Unfortunately this also did not allow me to flash any firmware (original or custom) due to admin permissions
(I think this is due to USB debugging not activated within Developer options).
I'm sorta banging my head off the wall with this one .... a bit like what came first? egg or chicken?, because since Odin isn't being recognised by the PC, I cannot flash rom and even though the PC fully communicates with Tab 3 in ADB mode, it won't allow me permission to sideload any flash files because I reckon I need root based permissions, and since the darn thing isn't booting fully, I cannot manually change anything!
I then started thinking about trying to sneak around this permissions issue by flashing CWM or TWRP, but again flash fails due to no permission.
All in all, for me this has been a great learning experience tackling the multiple Android recovery modes, and since I feel so close to cracking this non boot issue, I hate to give up and bin it.
Perhaps someone with much more experience can please help me here?
Is there any way of forcing superuser status on this Tab 3 SM-T210, so as to allow me to flash stock rom via ADB recovery mode?
many thanks in advance for your help,
Tab3SMD

Help usb and fastboot not reconized

I am getting a Unknown usb device (device descriptor request failed) It keep telling me usb device not recognized while being plugged it. I have tried several things
1. another windows 10 computer worked the first time then same error as a laptop.
2. unintalled the driver and rebooted.
3. also used multiple usb ports
cant find anything after searching
pixel 2 xl 8.0 September update
rooted lastest magisk 15.3
latest twrp installed
stock kernel
recently a fresh install a few days ago because i got it to work somehow but not anymore what do i do?
adb, fastboot, and storage cannot be accessed

Try these steps:
-uninstall previous version of SDK tools from PC
-download latest SDK Tools from HERE
-have a USB 2.0 cable available
-follow these steps to verify connectivity
see if these things help
Unless there is a specific reason you're still on Sept 8.0, I'd take this chance and upgrade to lasts 8.1 factory image.

evanxalmighty said:
I am getting a Unknown usb device (device descriptor request failed) It keep telling me usb device not recognized while being plugged it. I have tried several things
1. another windows 10 computer worked the first time then same error as a laptop.
2. unintalled the driver and rebooted.
3. also used multiple usb ports
cant find anything after searching
pixel 2 xl 8.0 September update
rooted lastest magisk 15.3
latest twrp installed
stock kernel
recently a fresh install a few days ago because i got it to work somehow but not anymore what do i do?
adb, fastboot, and storage cannot be accessed
Click to expand...
Click to collapse
I'm just spitballing here but....
With phone plugged in, on your pc, under device manage. When you open it up do you see unknown android device? That driver may need to be updated. Also, USB debugging is on, and the option to transfer files? Is your SDK platform-tools up to date?

I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.

I haven't seen it with this phone yet, but try changing the USB mode on your phone from the notification; I've had a few phones that refuse to work in specific modes.

evanxalmighty said:
I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.
Click to expand...
Click to collapse
Have you tried a different USB-C-A cable just for the heck of it. May have to factory reset and see if that solves it.

evanxalmighty said:
I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.
Click to expand...
Click to collapse
So your driver is messed up. Did you use the driver below?
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Sent from my taimen using XDA Labs

It won't let me install the driver I get some kind of error when selecting it. I was able to get it to work after plugging it in and out. Now that I updated to 8.1 everything was fine untill I got home. Now it's doing it again. I tried 2 different cables restarted my computer and laptop and can't figure out why it was working fine before without doing anything different.

Try this:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.

JimSmith94 said:
Try this:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
Click to expand...
Click to collapse
This definitely worked for me -- Thanks for posting!

I am having sort of the same problem. I was on Android 11 on my 2xl, rooted with fast boot boot twrp.Img and installed magisk and super super, all latest. I could not get gaps so I used Android flash tool to attempt to go back stock and it downloaded and flashed it but it is now stuck in loop, I reboot to recovery and it’s stock now and it will not be recognized by adb or fast boot,!0plesase help