i've just bought a kaiser from ebay. it worked for a few days until i decided to instal wm 6.5 on it. but i couldn't go that far. what i did: i've flashed a new radio on it, it worked fine. the next step that i wanted to take was to hardspl my kaiser but it didn't worked because i couldn't connect it to my laptop or my computer. i have windows 7 on both of them.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Stuck_at_bootloader --> 1 and 2 steps didn't work because of the same problem, i can't connect the phone through usb.
how can i fix this?
in bootloader is on serial and when i plugin the usb cable it changes to usb and it starts charging. what can i do? except to try from win xp.
costyg said:
in bootloader is on serial and when i plugin the usb cable it changes to usb and it starts charging. what can i do? except to try from win xp.
Click to expand...
Click to collapse
Try this page, Bro: http://forum.xda-developers.com/showthread.php?p=3932827#post3932827
Goodluck.
drTaruna said:
Try this page, Bro: http://forum.xda-developers.com/showthread.php?p=3932827#post3932827
Goodluck.
Click to expand...
Click to collapse
Thank you but it doesn't work. I can't view my mobile in device manager so i can't update drivers. when i connect my mobile it says usb device not recognized, and i go in device manager and i try to update the drivers from the unknown device but it doesn't work.
is there another way to try to boot? without conecting the phone to the computer. can i use my micro sd card to do that? i think it doesn't work because i unchecked 'Allow usb connection' in device manager, and after that it's only in bootloader mode. it doesn't work if i check allow usb connection.
how can i do a hard reset? would that help?
now it works! i've just connected to other usb port. strange because yesterday i tried this thing without succes. but i still can't connect it to usb. i get this error: "The device cannot start. (Code 10)" it worked before with windows device center. what can i do to connect it to usb? is it safe to hardspl my phone from win 7?
On older pc's the front usb ports aren't always usb 2.0. A hard reset won't help you at this time. Unplug all your usb devices currently attached to your pc. Restart. Plug in your kaiser cable to a back port on the motherboard. Make sure in task manager, that all windows media device center entries are closed.
Does it still give a code 10 error after doing all this? If so then delete the USB host controller entries in device manager. Click start button in win 7 and type "device manager". Hit enter. Open up USB controllers tree. Right click and uninstall all host controllers. Reboot. Let it redetect everything. Now plugin your phone cable. If still getting code 10 error then you are either using a faulty usb cable or the wrong type of cable (usb 1 instead of 2).
costyg said:
now it works! i've just connected to other usb port. strange because yesterday i tried this thing without succes. but i still can't connect it to usb. i get this error: "The device cannot start. (Code 10)" it worked before with windows device center. what can i do to connect it to usb? is it safe to hardspl my phone from win 7?
Click to expand...
Click to collapse
Have you downgrade the driver with the attached one? And if we used 64bit system we should disable the driver enforcement as suggested.
It is wise to hardspl from XP if all the effort from win7 failed. Once it's done we could flash new rom through SD card.
stuntdouble said:
On older pc's the front usb ports aren't always usb 2.0. A hard reset won't help you at this time. Unplug all your usb devices currently attached to your pc. Restart. Plug in your kaiser cable to a back port on the motherboard. Make sure in task manager, that all windows media device center entries are closed.
Does it still give a code 10 error after doing all this? If so then delete the USB host controller entries in device manager. Click start button in win 7 and type "device manager". Hit enter. Open up USB controllers tree. Right click and uninstall all host controllers. Reboot. Let it redetect everything. Now plugin your phone cable. If still getting code 10 error then you are either using a faulty usb cable or the wrong type of cable (usb 1 instead of 2).
Click to expand...
Click to collapse
i've installed win xp and i couldn't sync it so it's not a problem with the usb ports on the computer. the usb cable is fine. a few days ago i could sync the device with the same usb cable. now it's showing that is charging so it shouldn't be a cable problem.
drTaruna said:
Have you downgrade the driver with the attached one? And if we used 64bit system we should disable the driver enforcement as suggested.
It is wise to hardspl from XP if all the effort from win7 failed. Once it's done we could flash new rom through SD card.
Click to expand...
Click to collapse
no, i didn't do anything. it just worked. i did a reset and it passed the bootloader, it wasn't the first reset, it was strange but it worked. now i made a change on my device: start->settings->connections->usb to pc->and i unticked the 'enable advanced network functionality'. with this option i see "mobile devices->htc usb" sync in device manager but still i can't sync it. what can i do?
could this be related to the radio i've flashed? here is the rom and radio that i have. i don't know what radio i had before.
costyg said:
i've installed win xp and i couldn't sync it so it's not a problem with the usb ports on the computer. the usb cable is fine. a few days ago i could sync the device with the same usb cable. now it's showing that is charging so it shouldn't be a cable problem.
no, i didn't do anything. it just worked. i did a reset and it passed the bootloader, it wasn't the first reset, it was strange but it worked. now i made a change on my device: start->settings->connections->usb to pc->and i unticked the 'enable advanced network functionality'. with this option i see "mobile devices->htc usb" sync in device manager but still i can't sync it. what can i do?
Click to expand...
Click to collapse
We should downgrade the driver with the one attached in the linked site above and do as suggested, or the pc won't recognize the device in bootloader. Pls read and do as suggested. It won't spent more than 10 minutes to try.
drTaruna said:
We should downgrade the driver with the one attached in the linked site above and do as suggested, or the pc won't recognize the device in bootloader. Pls read and do as suggested. It won't spent more than 10 minutes to try.
Click to expand...
Click to collapse
well the device it's not in bootloader anymore. now the problem is that i can't connect it to the computer through usb. which radio would be good for my rom? radio is the problem?
So you are no longer getting the code 10 error, now you have installed XP?
costyg said:
could this be related to the radio i've flashed? here is the rom and radio that i have. i don't know what radio i had before.
Click to expand...
Click to collapse
Failure to connect with pc is not related to the radio rom. Ur radiorom is alright. The latest one is 1.71.09.01. It give a little possitive change in connection performance in GPRS/3G and GPS and change in battery drain depend on the signal in our country. Unmatched radiorom may cause bad signal and bad battery drain. Sometimes the camera will fail to start. U could search for the topic later. Goodluck.
costyg said:
well the device it's not in bootloader anymore. now the problem is that i can't connect it to the computer through usb. which radio would be good for my rom? radio is the problem?
Click to expand...
Click to collapse
We SHOULD download this driver: http://forum.xda-developers.com/attachment.php?attachmentid=194418&d=1244659513 and installed them to our PC (not ppc) as suggested HERE: http://forum.xda-developers.com/showthread.php?p=3932827#post3932827 !!!
The mean of this is to DOWNGRADE the wceusbsh.sys of Win7 or Vista so it could connect to the ppc through bootloader.
If u fail to force ur device to bootloader through hardbutton, try to copy and unzip the attached file (enterbootloader.exe) into ur sd-card through the cardreader and run.
stuntdouble said:
So you are no longer getting the code 10 error, now you have installed XP?
Click to expand...
Click to collapse
no, i don't get the code 10 error anymore but its still not working. there's an exclamation point on windows mobile based device.
drTaruna said:
Failure to connect with pc is not related to the radio rom. Ur radiorom is alright. The latest one is 1.71.09.01. It give a little possitive change in connection performance in GPRS/3G and GPS and change in battery drain depend on the signal in our country. Unmatched radiorom may cause bad signal and bad battery drain. Sometimes the camera will fail to start. U could search for the topic later. Goodluck.
Click to expand...
Click to collapse
thank you. i don't what to do. i wanted to make a upgrade to wm 6.5 but if i can't sync my mobile. it's good that i'm not stuck in bootloader anymore.
if i couldn't sync my mobile after a fresh install of win xp with active sync 4.5, what can i do? the cable is fine, the mobile wasn't damaged.
costyg said:
no, i don't get the code 10 error anymore but its still not working. there's an exclamation point on windows mobile based device.
thank you. i don't what to do. i wanted to make a upgrade to wm 6.5 but if i can't sync my mobile. it's good that i'm not stuck in bootloader anymore.
if i couldn't sync my mobile after a fresh install of win xp with active sync 4.5, what can i do? the cable is fine, the mobile wasn't damaged.
Click to expand...
Click to collapse
Here is the guide for upgrading our device: http://forum.xda-developers.com/showthread.php?t=433835
Follow the suggestion carefully after a careful reading. Goodluck.
drTaruna said:
Here is the guide for upgrading our device: http://forum.xda-developers.com/showthread.php?t=433835
Follow the suggestion carefully after a careful reading. Goodluck.
Click to expand...
Click to collapse
i know the guide but i can't apply it because i can't hardspl my phone. that's why i want to fix the sync problem.
costyg said:
i know the guide but i can't apply it because i can't hardspl my phone. that's why i want to fix the sync problem.
Click to expand...
Click to collapse
OK, post #14 is a guide if u use vista or Win7. Goodluck with XP and activesync 4.5
drTaruna said:
OK, post #14 is a guide if u use vista or Win7. Goodluck with XP and activesync 4.5
Click to expand...
Click to collapse
thank you, i hope i will fix it.
Related
Hi my Qtek 9000 doesn't work anymore after installation of Ranju_v77_WM61_19900_19900_1_0_2.
it never finished it.
but when i try to recovery on qtek or with the pc, with the Ranju installation program.
it also said don't look weird if you only got usb with the version number on your pda screen.
that window comes after if the installation failed, but when i try to back it up the program stops working.
so now i can't use my pda please help me.
Greetz, (n00b)
pommie said:
Hi my Qtek 9000 doesn't work anymore after installation of Ranju_v77_WM61_19900_19900_1_0_2.
it never finished it.
but when i try to recovery on qtek or with the pc, with the Ranju installation program.
it also said don't look weird if you only got usb with the version number on your pda screen.
that window comes after if the installation failed, but when i try to back it up the program stops working.
so now i can't use my pda please help me.
Greetz, (n00b)
Click to expand...
Click to collapse
Hi,
The answers you seek are in the WIKI.
Hold the backlight + power button whilst resetting the device. This will put you back into bootloader mode, you can then reflash the Rom.
I would also advise that you SuperCid your device before flashing any Roms, if you haven't done so already.
Again this is documented in the Wiki.
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
Cheers,
Beasty
my screen show me serial v1.01 and if i put the usb cable in it shows me usb v1.01
on my pc it installed as microsoft usb sync, but it won't connect on windows mobile device center.
so i can't use mtty even if i unselect usb in windows mobile device center i still can't select usb in mtty ive tried few times to delete and reinstall on my pc but still does not work.
pommie said:
my screen show me serial v1.01 and if i put the usb cable in it shows me usb v1.01
on my pc it installed as microsoft usb sync, but it won't connect on windows mobile device center.
so i can't use mtty even if i unselect usb in windows mobile device center i still can't select usb in mtty ive tried few times to delete and reinstall on my pc but still does not work.
Click to expand...
Click to collapse
The problem is Vista!
Search the forum and you will find a post with a fix (old drivers) for Vista, or just use a Windows XP or previoous MS OS to flash your device.
I would suggest XP if you plan to keep flashing in the near future
do i need to super cid my htc universal in order to upgrade to ranju v77. my universal is branded dopod 900 and can use with any simcard. thanks
lucky for me, i also got a pc with xp sp2 but my pda works with ranju v77 thnx man.
only from nokia phones i can't send file with bluetooth, phones like samsung works fine
My Dear Samaritans,
IMPORTANT:
- My SD/Memory card is removed
- My Sim card is removed
I was upgrading to Tomal v8.9 on a vista 64 system via a virtual machine XP SP2. Update failed and I got stuck in bootloader.
Tried reflashing but got an error and the flash failed... also the program crashed during recovery.
Tried using v8.71 still crashed without any luck.
Moved to a pure XP SP3 desktop...
When I connect the device to the computer(s) "Serial" changes to "USB" but XP sees it as an unrecognized device.
Tried flashing again but same error as on the virtual machine.
Tried mtty (1.16 & 1.42) but neither give me the option of USB, only COM1 and COM2. And had already de-activated the USB connection in Activesync.
Have read through the forum but have had no luck. Everyone's issue is resolved as soon as they remove their SD or SIM, but I have neither and am also using XP with activesync's USB disabled.
Tried UNI_ExitBootloader but that does not find/recognise the device either.
If it helps -- My device is/was an O2 XDA Exec (Stock) which I had previously flashed with Tomal's v8.5
I am ready to try anything, please help!
P.S: The error is Error 112
Did you install ActiveSync on xp pc?
If not, do it now and try again.
I had similar problem. Had corrupted DOC sector
and MTTY was the only solution, but although the Serial changed to USB, I got 'unrecognised' message and Mtty didn't give USB as an option. At some point it occured to me that it was my computer's USB port, for some reason the device was recognised by 1 in 4 ports only, So I just tried my USB cable in different ports until the 'device unrecognised' messaged stopped appearing. Finally, after I was ready to cry in frustration, it just worked. Don't give up.
I heard it mentioned somewhere that the device that went through Mtty will be recognised only by the port used in Mtty procedure.
That... or your device's USB is no longer properly attached to the mainboard.
tomal said:
Did you install ActiveSync on xp pc?
If not, do it now and try again.
Click to expand...
Click to collapse
Already have activesync 4.5 installed with USB connection disabled...
Thank you so much for the prompt response and helpful thought!
enigma1nz said:
and MTTY was the only solution, but although the Serial changed to USB, I got 'unrecognised' message and Mtty didn't give USB as an option. At some point it occured to me that it was my computer's USB port, for some reason the device was recognised by 1 in 4 ports only, So I just tried my USB cable in different ports until the 'device unrecognised' messaged stopped appearing. Finally, after I was ready to cry in frustration, it just worked. Don't give up.
I heard it mentioned somewhere that the device that went through Mtty will be recognised only by the port used in Mtty procedure.
That... or your device's USB is no longer properly attached to the mainboard.
Click to expand...
Click to collapse
Thank you for the ray of hope! Will keep trying every hourly reboot in every USB port (4 in all).
Weird thing is I never had to go through mtty before so this is my first need for it.
Got the physical connection checked and it is supposedly OK...
Thank you for the prompt help...
Don't worry
I had exactly the same problem. First I tried this and it worked but still no connection via mtty. On that evening I disconnected and connected a lot and I removed the battery for a long time (one night). Later I could connect but I don't know why. Maybe these two things were the solution. Mtty showed "usb>" and I've done a DOC format...
If nothing works I would create a rom-image (on sunday or monday) for your sd-card like it's written in the service manual.
blingin said:
Thank you for the ray of hope! Will keep trying every hourly reboot in every USB port (4 in all).
Weird thing is I never had to go through mtty before so this is my first need for it.
Got the physical connection checked and it is supposedly OK...
Thank you for the prompt help...
Click to expand...
Click to collapse
No need for hourly reboots, just get into Bootloader, connect USB to your device and try different ports on computer with a few seconds in between to ensure no 'unrecognised device' message popping up. Once you'll get a connection - go for Mtty facility, the USB is the last on the list of ports.
330e said:
I had exactly the same problem. First I tried this and it worked but still no connection via mtty. On that evening I disconnected and connected a lot and I removed the battery for a long time (one night). Later I could connect but I don't know why. Maybe these two things were the solution. Mtty showed "usb>" and I've done a DOC format...
If nothing works I would create a rom-image (on sunday or monday) for your sd-card like it's written in the service manual.
Click to expand...
Click to collapse
There was no SD card when I began the initial flash but it still got stuck. Been trying without the SD and SIM but to no avail...
Thank you for the manual, downloading it now, will keep everyone posted in case anyone else is suffering from the same thing...
enigma1nz said:
No need for hourly reboots, just get into Bootloader, connect USB to your device and try different ports on computer with a few seconds in between to ensure no 'unrecognised device' message popping up. Once you'll get a connection - go for Mtty facility, the USB is the last on the list of ports.
Click to expand...
Click to collapse
Still trying, will keep you posted and thank you for the responses!
I think you understood me wrong. When your device is still unusable, I would create the files you need to do the steps in point 8.3 (Use Pre-loaded SD card to Re-flash Unit) in the service manual.
Sorry for my bad english
330e said:
I think you understood me wrong. When your device is still unusable, I would create the files you need to do the steps in point 8.3 (Use Pre-loaded SD card to Re-flash Unit) in the service manual.
Sorry for my bad english
Click to expand...
Click to collapse
It's the thought that counts not the language, thank you so much for your help!
I created succesfully a pre-loaded sd card, flashing via this sd works. But I can't copy the files. When I want to open the drive it says, that I have to format the sd card. Is there a special tool to copy the files? Or you find someone near you with a universal.
your need to format your SD after flashing.
330e said:
I created succesfully a pre-loaded sd card, flashing via this sd works. But I can't copy the files. When I want to open the drive it says, that I have to format the sd card. Is there a special tool to copy the files? Or you find someone near you with a universal.
Click to expand...
Click to collapse
tomal said:
your need to format your SD after flashing.
Click to expand...
Click to collapse
Tried the SD image method with a 128MB SD but didn't work. Maybe because I have a G4 and the method is for G3
managed to get a connection finally and ran MTTY, after "task28 55a" it just hung for a long time so I disconnected.
Tried running UNI_ExitBootloader.exe and now can get in and out of Bootloader but still cannot flash or connect...
Any suggestions welcome...
Try this....
This might sound silly but it's worked for me in the past.
1. Go into bootloader (without mem card or sim)
2. Plug-in the USB cable
3. Hold the buttons to go into bootloader again whilst plugged in.
4. DOC Format
5. Flash ROM
My Universal had loads of problems but that is how i fixed it, tried everything else like you, when i first plugged it in on the bootloader nothing happened until i pressed and held the buttons whilst it was plugged in, then windows made the usb connected sound so i quickly mtty'd! lol
Hope this helps, Good luck!!!
martinbrettphilo said:
This might sound silly but it's worked for me in the past.
1. Go into bootloader (without mem card or sim)
2. Plug-in the USB cable
3. Hold the buttons to go into bootloader again whilst plugged in.
4. DOC Format
5. Flash ROM
My Universal had loads of problems but that is how i fixed it, tried everything else like you, when i first plugged it in on the bootloader nothing happened until i pressed and held the buttons whilst it was plugged in, then windows made the usb connected sound so i quickly mtty'd! lol
Hope this helps, Good luck!!!
Click to expand...
Click to collapse
Thank you...
Xda2 stuck in bootloader screen after failed flash in vista
blingin said:
My Dear Samaritans,
Tried reflashing but got an error and the flash failed... also the program crashed during recovery.
When I connect the device to the computer(s) "Serial" changes to "USB" stuck within the bootloader screen
Tried mtty (1.16 & 1.42) but neither give me the option of USB, only COM1 and COM2. And had already de-activated the USB connection in Activesync.
Have read through the forum but have had no luck.
I am ready to try anything, please help!
P.S: The error is Error 112
Click to expand...
Click to collapse
Hi i have had similar problems also i have an XDA 2 pda originaly had wm2003 on it (tried to flash it to wm2003se ) can someone help me also im realy at a loss =C many thanks in advance (i will give more detail if someone actualy) replys to me
Wrong forum
Welcome to the forum
Universal does not means all devices, actually is a model
Please enter into the right section of the forum
Goos luck,
Can you Help?
I have an XDA II was on O2 uk network. I used to flash it all the time and knew my way around. however recently i flashed it in vista without thinking.. and as i upgraded the rom from wm2003 to wm2003se about 25% of the way through vista disconnected the device then it was unrecognised usb.. then vista started installing new drivers that recognised the device... however this then crashed flashing the rom onto the pda..
It wont soft or hard reset, i took the battery out for 24 hours and tried again and nothing.. the only thing on screen is that it says serial on the top of the screen (which changes to usb when connected but get error 101 when trying to reflash/ no activesync connection and am confused my mtty as when it does connect i cant type into the text area only paste)
on the bottom of the screen is v1.06 (which before the flash crash was V1.0 something lower than v1.06)
basicaly is the device recoverable as long as i have this serial / usb recognition by the device????? (using mtty i cant connect through ports or usb but thats because i dont seem to understand how to use it)
the other question is is there any other way to get a rom back onto the device without mtty or activesynch..
I pray that ysomeone will respond .. i miss my pda dearly
a thousand thanks in advance
Hello guys!
I've got a bit of a problem here, because now my mobile refuses to connect with activesync and therefore making it impossible to flash it.
I read the readme in the cid bypass folder, and didn't quite understand it, but as keen as I was on getting a new rom I did it all wrong.
I actually copied the cid bypass folder to my sd-card and ran haret.exe from the phone. A friendly penguin appeared along with some green text, and it rebooted and went black. I waited for a while, but had no patience so I rebooted it again. But after this it has been impossible to connect it with activesync! I've tried hard reset and different computers but nothing works!
I'm hoping someone on this forum can help me!
best regards
Try this.
turn your phone off and press the camera button in then plug it into the USB port
you should get a multi color screen. If you do then you can flash.
But go here http://forum.xda-developers.com/showthread.php?t=330909
Go to where it says EDIT and follow what it says.
Oh and when a dos box opens up and ask you things just press the return key each time.
good luck
hey man, I tried reflashing the original rom to my vox, with the manualstyle sd card flash. So now it's flashed with the original rom, but still activesync doesn't work! anybody have an idea on how to make this right?
somebody tried running haret.exe from their phone, then flashing the Uspl with ruu flasher and then flash the new cooked rom?
My phone is not able to connect for flashing while in black state (after running harET), is it stupid of me to reboot it and start it by holding camera button while plugging it in to the computer? and then flash it with the ruu?
somebody please help me?
go into settings then connections then more till you see USB to PC
in there un-tick the box which says enable advaned network.
zipuz said:
somebody tried running haret.exe from their phone, then flashing the Uspl with ruu flasher and then flash the new cooked rom?
My phone is not able to connect for flashing while in black state (after running harET), is it stupid of me to reboot it and start it by holding camera button while plugging it in to the computer? and then flash it with the ruu?
somebody please help me?
Click to expand...
Click to collapse
I am confused..is it working or not? one post you say it is but you cant sink..then you say its not.????
and dont use the flash off the mem stick..use windows..
ok, sorry for making confusing posts! I'm just excited about getting it to work.
So here's the situation:
From stock phone used with exchange (turned off the exchange part before doing anything)
1. I ran haret.exe from my phone, and it rebooted into a "black state" after which I rebooted it again
2. I tried to connect it to my computer using activesync, to be able to flash, but it wouldn't connect. Activesync doesn't respond to my phone.
3. I flashed the shipped rom to my phone from my sd-card in good hope that it would reset the whole process, but it still won't connect to activesync.
So here's my problem; I want to flash a cooked rom to my phone, but I'm unable to connect it to my computer via activesync, what to do?
deuse said:
go into settings then connections then more till you see USB to PC
in there un-tick the box which says enable advaned network.
Click to expand...
Click to collapse
tried with both ticked and unticked, still nothing
Turn off your phone then keep the camera button pressed in at the same time plug it into the usb port
your should show diff colors on the screen..if so follow what it says in this link.
http://forum.xda-developers.com/showthread.php?t=330909
and do it from the pc not your mobile...
it's restored, but no activesync still
Is the cable you are using ok? or is it a new one you just got.
does windows see it when you plug it in? if so un-install active sync then reinstall it.
I'm having the same issue with Windows Mobile 6.5 ROM, activesync simply doesn't work ;/
ivanek666 said:
I'm having the same issue with Windows Mobile 6.5 ROM, activesync simply doesn't work ;/
Click to expand...
Click to collapse
Have you been into settings and un-ticked the box in USB to PC?
Also if you are trying to sync to office you must create a new partnership
google is your best friend.
I have no problems with sync in XP/Vista?windows 7 and office 2007
I am using FMs 1.1 WM 1.1
deuse said:
Is the cable you are using ok? or is it a new one you just got.
does windows see it when you plug it in? if so un-install active sync then reinstall it.
Click to expand...
Click to collapse
Windows notices my mobile (installs new drivers), but activesync doesn't register the device.
zipuz said:
Windows notices my mobile (installs new drivers), but activesync doesn't register the device.
Click to expand...
Click to collapse
Do the Hard reset .Then connect it to your machine.I hope this time it will work smoothly.
zipuz said:
Windows notices my mobile (installs new drivers), but activesync doesn't register the device.
Click to expand...
Click to collapse
Try this
open sync then at the top chose files then click on DELETE MOBILE DEVICE
see what happens..but post back if you fix it to help other people
yogusmilu said:
Do the Hard reset .Then connect it to your machine.I hope this time it will work smoothly.
Click to expand...
Click to collapse
I failed to mention that I've tried the hard reset as well, no luck.
I thought about the same thing Deuse, but there's no mobile device registered, so I'm not able to delete it.
It seems that you have tried every possible method! Anyway, my suggestion is install activesync in some other PC (friend's) and connect your phone there. See if it registers the phone. If it does then it is problem with the PC and not with phone. In that case, connect phone to PC and open controlpanel>System (icon)>Hardware tab>Device Manager Button in your PC. Unfold Network adapters and see if your phone is detected properly or it is detected with an "!" mark in "Unknown/Other device". If so, delete the device and disconnect phone. Reboot PC, reboot phone connect again and let the PC reinstall your device and see if it recognises your phone.
One more way (I think you might have tried this)- Uninstall Activesync and reinstall and connect phone.
By the way if your phone is not recognised in some other PC then it seems trouble with the phone.
Thanks.
Looks like your cable is faulty. Try activesync connection through bluetooth (for testing, ofcourse you cant flash from bt ).
parthabhatta said:
It seems that you have tried every possible method! Anyway, my suggestion is install activesync in some other PC (friend's) and connect your phone there. See if it registers the phone. If it does then it is problem with the PC and not with phone. In that case, connect phone to PC and open controlpanel>System (icon)>Hardware tab>Device Manager Button in your PC. Unfold Network adapters and see if your phone is detected properly or it is detected with an "!" mark in "Unknown/Other device". If so, delete the device and disconnect phone. Reboot PC, reboot phone connect again and let the PC reinstall your device and see if it recognises your phone.
One more way (I think you might have tried this)- Uninstall Activesync and reinstall and connect phone.
By the way if your phone is not recognised in some other PC then it seems trouble with the phone.
Thanks.
Click to expand...
Click to collapse
It's marked with an "!", will try it on my own pc next time I have it, worked there last time! if not, I'll have to live with
Hey
A couple of days ago i tried to install the latest CM12 nightly. After updating it my phone crashed everytime it booted up. I did a factory reset and tried to flash older versions but nothing seemed to work so i went into CWM recovery 6.0.4.5 and pretty much formatted everything.
I still have access to the bootloader and recovery but my Windows 8.1 PC doesn't recognize my phone ("Unknown usb device" "Windows has stopped this device because it has reported problems. (Code 43)") I can't access my phone with adb or fastboot now. This looks like a driver problem but i tried a lot of different drivers on multiple PC's.
What can i do now?
Try this thread, could help...
http://forum.xda-developers.com/showthread.php?t=2588979
Darth said:
Try this thread, could help...
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
He said that he can't access his phone with adb or fastboot. Maybe he must try to resolve driver problems first?
zagorteney said:
He said that he can't access his phone with adb or fastboot. Maybe he must try to resolve driver problems first?
Click to expand...
Click to collapse
It's a driver issue likely. Starting from scratch in the thread I linked addresses drivers. Likely ones he hasn't tried.
Though, a few other ideas are trying another cable, another USB on the computer. And last... Try another computer. ?
Darth said:
It's a driver issue likely. Starting from scratch in the thread I linked addresses drivers. Likely ones he hasn't tried.
Though, a few other ideas are trying another cable, another USB on the computer. And last... Try another computer.
Click to expand...
Click to collapse
And in future: please, stay on stock.
No driver seems to work. Is it possible to install a zip from an usb flash drive with OTG?
dermaxe said:
No driver seems to work. Is it possible to install a zip from an usb flash drive with OTG?
Click to expand...
Click to collapse
Try this: http://nirsoft.net/utils/usb_devices_view.html
It helped me a few times.
I uninstalled everything from there that was android-related. After plugging in my phone (in bootloader mode) my PC detects it as " Google Nexus BootLoader Interface" but "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
dermaxe said:
I uninstalled everything from there that was android-related. After plugging in my phone (in bootloader mode) my PC detects it as " Google Nexus BootLoader Interface" but "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
Click to expand...
Click to collapse
Did you use USBDeview or you just manually removed all drivers that you saw?
I went into USBDeview and uninstalled everything that was android related
ummm why hasnt everyone mentioned the very basics? USB Debbugin enabled?
you already flashed and reset phone...
because after any reset, that will default back to unchecked and u wont be able to adb or fastboot until that is checked
How do i enable usb debugging without any os?
dermaxe said:
How do i enable usb debugging without any os?
Click to expand...
Click to collapse
chaco81 said:
ummm why hasnt everyone mentioned the very basics? USB Debbugin enabled?
you already flashed and reset phone...
because after any reset, that will default back to unchecked and u wont be able to adb or fastboot until that is checked
Click to expand...
Click to collapse
USB debugging enabled is only needed when using Adb from within the Android OS. It's not needed for adb use in recovery mode, and never needed for fastboot.
??
good to know
Okay so i don't have to do this but i still have that driver problem. It is recognized as Android Bootloader Interface but i still get "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
dermaxe said:
Okay so i don't have to do this but i still have that driver problem. It is recognized as Android Bootloader Interface but i still get "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
Click to expand...
Click to collapse
For me this sounds more like computer realted problem rather than device. If you can try all of those steps ( installign drivers, etc ) on another pc maybe this will solve your issue
Just tried it on a fresh installation of W7 but my device wasn't recognized and i couldn't install any drivers for it. How can it be a PC related problem if it doesn't work on so many different configurations?
If you run it on VirtualBox, see this answer (prepend http, I can't post links): superuser.com/a/887249/239087
To make it short, you need VirtualBox Extension Pack, and you need to configure the USB port to use USB 2.0 at least.
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
WhiteCoffeeCat said:
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
Click to expand...
Click to collapse
Thanks for the suggestion! I will attempt these. Fingers crossed
I have previously attempted to install adb driver but had some trouble. When installing using Device Manager, the locate .inf dialog refuses to accept my selection. I dont seem to be any error. When attempting to do so via the folder (and sub folders) it says no drivers found. Perhaps i'm doing this totally wrong?
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
eshlad said:
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
Click to expand...
Click to collapse
Put Windows into testing mode before installing drivers in Miflash, adb.. Run cmd prompt as admin and type bcdedit -set TESTSIGNING ON or bcdedit -set TESTSIGNING OFF for disabling testing mode.
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
how?
goila said:
how?
Click to expand...
Click to collapse
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
jholfran3 said:
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
Click to expand...
Click to collapse
Thanks, but that doesn't help, otherwise I've already done it. I had m1 mac and with parallel desktop only the possibility to install win 11.. win 11 sucks.. I installed win10 on an intel mac in parallel and that solved my problem
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
ItsmeeVishal said:
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
Click to expand...
Click to collapse
Have you tried to disable driver signature enforcement in windows 11.
istampal said:
Have you tried to disable driver signature enforcement in windows 11.
Click to expand...
Click to collapse
Yeah, i tried it.
Nothing happened.
ItsmeeVishal said:
Yeah, i tried it.
Nothing happened.
Click to expand...
Click to collapse
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
eshlad said:
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Click to expand...
Click to collapse
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
What VM were u using?
I'm using parallels Desktop 18
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
I tried to do what u said but don't know what to do next.
Plz see the attached video video and tell me what wrong I'm doing.
After clicking on legacy hardware, what are other steps......
And, thank you so much for reply!
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Titek said:
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Click to expand...
Click to collapse
Hi Tek,
I have had many issues with windows and fastboot,
some cables would work with some of the ports and then not.
My pc has 12 usb ports, yet it was still hit and miss whether fastboot would work on my Poco F3.
I tried your tip and after using a cheapy Targus 4 port usb adaptor, my "FASTBOOT PROBLEMS ARE NOW SOLVED"
now what am i going to do with my 7 surplus USB-C Cables
Many thanks for your TIP