Help please - JASJAR, XDA Exec, MDA Pro ROM Development

So heres the story :
(Im Using windows 7)
My SPV is stuck in bootloader mode, I downloaded the 'UNI_exitbootloader.exe' file but I get the error 'Cannot Open USB Port', Although in Windows Mobile Device Center, I have unticked the 'Allow USB Connections' Box but no avail, Can someone please help?
And also, The Tomal v7.7 I downloaded contains one .EXE file, do I just run that while the device is powered on and plugged in?
P.S-(I'm New to this device and the forums, sorry if questions are stupid)

Related

Computer wont reconigize my G1

I am using Windows Vista Ultimate. Everytime I hook up my G-1 it shuts off my internet connect and it gives me an error message at the bottom right about it not reconigizing the device. It will allow me to charge it but I can't access the sd card or use my internet when connected. please help. P.S. I can take it to anyone elses computer and it works just find (XP & Vista).
cyanogen 4.2.3.1
Welcome to forums
Have a look here:
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream
Hope it helps,
check out for the program 'USBdeview' and run it. It allows to correctly unistall any previous driver, then reboot, connect the g1 with the cable, choose 'manual install' and put on those, they will do the job fine
make sure USB Debugging is enabled (Useful for ADB Commands)

need help in T-moble HTC PU10 stuck on boot loader screen

i just tried to update my HTC PU10 windows mobile 5 to WM6 but then the screen got blank and now i think its in boot loader screen as i read in most of the forums. i read most of the forums abt this for 7hrs now and still stuck coz im new to these.
im using windows 7 on my pc so i cant use Activesync so im using windows mobile device center to connect
i tried connecting to mtty1.42 but my MDA dosnt detect in USB as most of the forums say but when i connect to the pc my MDA screen gose serial to USB v1.01 it mean im in the boot loader screen am i right ? so please tell me wht to do next
thanks in advance
Mudith
Welcome to forums
Have a read on the Wiki here:
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial
Hope it helps,
ok i got my MDA working have to use Windows XP. ROM Update Utility dosnt detect the MDA from USB on Windows7
Windows XP is the best
thanks guys for ur support
hy mudith
i have the same problem with my pda...so please tell me what to do next...i read on forums but my pda doesn't connect on my pc....!!! i don't know what should i do..!!!
Belated Help
Firstly, remove both the SIM card and any memory card. Make sure your battery is charged as well. Can you get into the bootloader (Light button, on/off button and reset button all at the same time)?
If so then your screen should be showing 'Serial' at the top and a number at the bottom. Plug the cable into the XDA and into your PC (it IS a PC and not an iMac I'm assuming?). What OS are you using? XP, Vista or 7?
You need to ensure that 'connect via USB' is DE-SELECTED in either activesync or Windows mobile device centre.
With the cable plugged in, the 'serial' should change to 'USB'. If so all is good. If not, try another cable!
You may also need to ensure you have the correct drivers loaded for Vista and Win 7. I can't get it to work under Win 7 but I can under Vista. XP is preferred for stability for me though.
Now, assuming you have USB on the XDA screen, run mtty (attached to this post) and select usb as the connection type.
Then press enter and you should get a 'USB>' command prompt in the window on the PC. Type (not copy paste) the following:
set 14 0 <press return - don't type this bit obviously!>
Task 28 55aa <press return - don't type this bit obviously!>
Allow each to finish before typing the next and allow the command prompt to appear before exiting.
Then exit mtty and flash a good ROM, I use VNInt with HomeScreenPlus.
Good Luck!

who can help me to solve the problem "unknown device error"

So depressed, this morning, when my phone is in syncing I answered a phone and the mobile synchronous interrupted, Ijoined it to my again, the pc shows"unknown device",
I tried to updated drivers, but no use
I reboot my Touch PRO,the PC also shows "unknown device",
I reflashed a new rom to my phone , the pc shows as the same""unknown device",
I connect my colleagues' HTC C720 and an imate PPC to my PC ,they could be activesynced with my pc. My touch pro also could be synced with their PC
who can help me.It makes me crazy.
Simple mistake. It's possible that everyone may have had this problem before.
It's a Device Partnership Error.
I'll help you with the easiest way to fix this(in my opnion).
1.) Unplug your Device from your PC
2.) Download & Install CCleaner HERE
3.) Uninstall Windows Mobile Device Center/Active Sync from your PC
4.) Run CCleaner (Run the Windows Cleanup & Registry Cleanup [FIX EVERYTHING])
5.) Restart your computer
6.) Download & Install Windows Mobile Device Center/Active Sync
7.) Soft-Reset your phone
8.) Plug in your Phone during its boot-up
Reply with results.
Agent Zach
I followed your instruction
but it's no useful
thanks all the same

[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"

[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"
Hello
The situation:
I'm trying to relock the bootloader and flash RUU, so that I can get rid of the tampered flag and start over.
I'm trying to use Hasoon2000's Toolkit to do this, but I'll try any method that sounds reasonable.
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
EXTRA INFO:
I didn't use Hasoon's toolkit to unlock the bootloader, I actually used the platform-tools from the SKD bundle thru the terminal on a mac pc. Then I flashed CWM onto the One S using "./fastboot flash recovery recovery_thefilename.zip". Then I reloaded bootloader, selected Recovery, then my phone's screen went black, turned back on, and I saw the Red Triangle with the Exclamation mark. According to a "How to" blog, which I didn't read until after the fact, I was supposed to hold down the power button and volume button at that point in time, but I didn't. I had no idea what was going on. I pressed the power button and my phone restarted, and now every time I reboot to recovery mode, it just restarts the phone and says "This build is for development purposes only. Any redistribution will result in legal action." or something like that.
OK THAT'S ALL.
I appreciate any help!
jire
The text in red is normal if you have a custom recovery.
Just get the device in fastboot USB mode.
Check with command: fastboot devices
To see if it is connected. I should return you sn number.
(Since you manually unlocked, this should be easy for u.)
Then manually flash a correct recovery (or use the toolkit with the custom option). Reboot in recovery. Flash ROM.
Verstuurd van mijn One S met Tapatalk
Can you try to execute fastboot oem lock command on Windows OS which have hTC drivers installed? I guess that you using Linux OS now... Just install Windows in VM and hTC drivers, adb and fastboot you can download on htcdev.com or from android bundle package... I'm pretty sure that you have problem with your drivers...
Sent from quietly brilliant HTC One S
USB 3.0 might be the issue
Hey guys, thanks for trying to help me out here, I appreciate it a bunch!
Before I go any further. I think I've learned what the problem is. Well, first of all, if you didn't catch it, I've been working thru this on both win and apple computers.
Hasoon's toolkit is only available for windows. Therefore, if I said/say I did something with his toolkit, that means I was using my win computer, which is actually a Surface Pro, which has USB 3.0 === THE PROBLEM
According to this: http://forum.xda-developers.com/showthread.php?p=29286429
Unfortunately, I haven't been able to test this hypothesis, yet, because I first need to find a win pc with USB 2.0. [Fact: I couldn't get androidfiletransfer.app to recognize my htc one S on my mac. Coincidence?]
real187: When you say to install a "correct" recovery, are you implying I currently have an incorrect recovery on my phone?
mikronac: I have virtually no experience with command prompt. I just got my Surface Pro last week :laugh: and I'm geeking out...So, what I'm saying is I don't know how to do "fastboot oem lock command" ... The htc drivers are installed, up-to-date and operating without a hitch.
It can't be problematic your usb 3.0.
Please deinstall your phone drivers and install them again...
If you know how to navigate to platform tools folder in Windows Explorer, only what you need to do is to hold shift key on keyboard and right click on mouse and select option open command prompt here. Than you type :
Adb devices
Response should be serial number of phone
Adb reboot bootloader (uab debugging must be enabled)
When it reboot in fastboot, type in cmd:
Fastboot oem lock
Sent from quietly brilliant HTC One S
I can confirm: It is USB 3.0
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
maatriks said:
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
Click to expand...
Click to collapse
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
No USB 2.0
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
dsuresh89 said:
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
Click to expand...
Click to collapse
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
dsuresh89 said:
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
Click to expand...
Click to collapse
hey
there is no driver for 3.0 USB xtensible host controller for windows 8
and I already have a usb 2 but I have the same problem
I think that it came from windows 8
Thanks in advance
Unable to fastboot in Windows 8.1
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hey Bro,
I am facing the same issue. Unfortunately I don't have a USB 2.0 port in my computer. Im struggling to flash the boot file.
Please help
jire0006 said:
Hello
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
jire
Click to expand...
Click to collapse
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that has a value of 1 to the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\usbflags\vvvvpppprrrr
(where vvvv is the device's Vendor ID, pppp is the device's Product ID, and rrrr is the device's Revision number. You can get the VID/PID/REV numbers from the device manager's details tab. This number is encoded in the HardwareIDs of the device)
1. Click Start, click Run, type regedit in the Open box, and then click OK .
2. Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags
3. On the Edit menu, point to New, and then click Key.
4.Type the name of the new key in the following form:
vvvvpppprrrr
where
vvvv is a 4-digit hexadecimal number that identifies the vendor (idDevice from the USB Deviceescriptor),
pppp is a 4-digit hexadecimal number that identifies the product (idVendor from the USB Device Descriptor)
rrrr is a 4-digit binary-coded decimal number that contains the revision number of the device
(bcdDevice from the USB Device Descriptor).
5. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
6. Type SkipBOSDescriptorQuery for the name of the DWORD Value, and then press ENTER.
7. Right-click SkipBOSDescriptorQuery, and then click Modify.
8. In the Value data box, type 1 , and then click OK.
9. Exit Registry Editor.
10. Unplug and re-plug the device for the workaround to take effect.
Click to expand...
Click to collapse
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
windows 8 have a issue with ville fastboot... please make you sure you have a fix
zoodles said:
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
Click to expand...
Click to collapse
THANK YOU SO MUCH. Fixed for me on HTC Magic
..
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows.
---------- Post added at 10:41 PM ---------- Previous post was at 10:17 PM ----------
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows. Btw, I tried all methods in forums and in YouTube too (updating USB Root Hub drivers). Nothing helps, just "Failed device enumeration". Windows 10.. I will go back to Win7, fortunately I don't have license for 10.. Pray about these who has...
Bruh, this worked like magic on my HTC One X+ !!!
Using Windows 10 Enterprise Build 17134 by the way
Thanks a lot!
Thank you very much bro. HTC One V good working.

HTC Pico "Fastboot USB" Issue On Windows 10 (x64)

Hi To All Members. My HTC Explorer is unable to communicate with Windows 10 (64 Bit) in Fastboot Mode. Although i have installed the propers drivers for my Pico. In Device Manager, HTC Explorer is recognized as "ADB INTERFACE DEVICE" but whenever i connect it in FASTBOOT MODE. My PC says"Device Not Recognized" . I am using Windows 10 (Enterprise) and tried different USB CABLES. Also, whenever i connect it to install applications with APK INSTALLER. It Says "Connection Exception". .
Any help would be appreciated
help me tooo
My HTC sync is not recognising my device
Although the phone shows fastboot usb the computer doesnot recognise it
i am trying to unlock my bootloader but in cmd after the "fastboot oem get_identifier_token" command
I only see "<waiting for device>''
plZ HELP!!!!!!!:crying::crying::crying:
Hi their seems to be an error with usb registry since Windows 8 so some devices are not being recognised properly, thankfully their is a fix that works for Windows 8/8.1/10 right click on the attached Fasdtboot.txt file and "save target as" change the drop down option from "text" to "all files" then change the file extension from .txt to .reg (Fastboot.reg) so it can be added to your registry, once done simply double click on it and add it to your registry, then installed your drivers via device manager for fastboot and adb.
anonymous-user said:
Hi their seems to be an error with usb registry since Windows 8 so some devices are not being recognised properly, thankfully their is a fix that works for Windows 8/8.1/10 right click on the attached Fasdtboot.txt file and "save target as" change the drop down option from "text" to "all files" then change the file extension from .txt to .reg (Fastboot.reg) so it can be added to your registry, once done simply double click on it and add it to your registry, then installed your drivers via device manager for fastboot and adb.
Click to expand...
Click to collapse
Tried It. Same issue persists
syedbilal07 said:
Tried It. Same issue persists
Click to expand...
Click to collapse
Should work, just make sure your manually adding the drivers back in device manager one for adb and one for fastboot. (right click on unknown/malfunctioned device update driver, point to drivers)
I have manually added registry key and also installed drivers but it says, windows has determined the best driver for you and it is up to date. Feeling hated with windows 10
Try to update your windows ...
Fastboot working fine in my window 10..PC..
I am using enterprise edition.
Please can you properly guide me about every step with screenshots. I am trying to solve it since many days but now frustrated. Please, i will be thankful to you @vaibhav1

Categories

Resources