I've tried upgrading win8 from win7 three times now. It pretty much gets through the install process, but after showing the beta fish I get a BSOD and an "inaccessible boot device" error. It then reverts me back to Windows 7.
I think that I'm going to disable AHCI in my BIOS and then try. I'm worried about losing data though.
Anybody else have this problem? Any suggestions?
On my Acer laptop I have a second hard drive instead of the customary dvd drive and I have to disable ahci to install windows at all.
Never managed to figure out what the issue is. I've even tried loading the ahci driver post install and then turn it back on in bios, but I get the same bsod.
Should note that I had the same issue with windows 7 so my experience may be irrelevant.
Related
Hey guys, for some reason I'm unable to perform a Task29 or flash anything from MAGLDR 1.13's USB flasher mode.
Here's what happened.
I was using CMYLXGO's stock Desire HD ROM and having data problems, so I tried to change my kernel to Tytung's using CWM. After I did that, Android stopped booting - kernel load fail. I don't know how to fix that, so I figured I'd just do a clean install.
When I tried to do a Task29 from the 3 color screen, I get stuck at "Verifying information from your PDA phone..." It then tells me it can't establish a USB connection. I ran the program as administrator.
Okay, I said to myself, I'll try reflashing CWM from MAGLDR's USB Flasher. I got "Wait USB... USB." and tried, but DAF.exe also told me it couldn't establish a USB connection.
I know the USB connection is working, because I've tried it with two different cords and reformatted the SD card through MAGLDR's USB mass storage mode, which still works.
Can anybody help me out? Currently I can't boot android, don't have windows mobile and am f**ked...
Thanks,
Zuka
I think I've solved it, if anyone else is having the same problem. I believe it's because I uninstalled Windows Mobile Device Center when I moved to android full time.
EDIT: That was in fact the problem. Hint: NEVER UNINSTALL MOBILE DEVICE CENTER
zukŠ° said:
I think I've solved it, if anyone else is having the same problem. I believe it's because I uninstalled Windows Mobile Device Center when I moved to android full time.
EDIT: That was in fact the problem. Hint: NEVER UNINSTALL MOBILE DEVICE CENTER
Click to expand...
Click to collapse
Yes WMDC and ActiveSync have the USB drivers for your HD2 will it is in bootloader, hence no connection via USB as you have no USB drivers for bootloader. Glad you figured your problem out and posted it back here for others to see. Too bad I did not see your threadcearlier as I may have been able to say you a little stress.
Haha, I appreciate it, but when I tried it on my housemate's computer and I saw "Windows Mobile Device Centre installing..." I knew how I'd messed up. Thanks anyway, hopefully this can serve as a reference thread if anyone googles and comes up short.
this driver problem is driving me crazy. it's the same story in XP as well.
i think it stems from the fact i've messed around with so many different drivers that my 7x64 and XP machines just don't know what to install anymore.
it has worked in the past. first time i rooted this phone i had to mess around with win7 drivers (to the point of almost giving up) to get windows to recognise the device at each stage of the root. this was done using a combination of HTCSync 2.0.33 and PDAnet's drivers.
since then i've had to flash to stock for an RMA, then went through the whole nightmare process again a second time. i mistakenly assumed that it would be easy the second time..
I've just accidentally flashed back to stock again, and this time it doesn't matter what i do, i just can't get these f*****g drivers working! same story on XP (which has also had numerous drivers installed over and over again).
i've even taken the phone apart to check nothing's damaged and tried a different usb cable, and un/modded google drivers.
one thing i noticed is that after rooted and flashing cymod, the previously working drivers no longer detect my phone.
has anyone had a similar experience?
Hey Guys, the other day I tried to transfer some video to a windows 7 pc.
I plug in my usb cable and windows will not recognize the device anymore.
I have tried 4 different machines
4 different sets of drivers, etc.
I just performed a system wipe in twrp and re-installed the os.
Still nothing..
The only acknowledgement windows gives me that it "sees" anything is when i reboot.
once I hit the boot animation i get a "device not recognized" error.
Anyone else experience this issue?
the next step to troubleshoot is to go back to real factory default and start fresh.
Thanks!
deathshead said:
Hey Guys, the other day I tried to transfer some video to a windows 7 pc.
I plug in my usb cable and windows will not recognize the device anymore.
I have tried 4 different machines
4 different sets of drivers, etc.
I just performed a system wipe in twrp and re-installed the os.
Still nothing..
The only acknowledgement windows gives me that it "sees" anything is when i reboot.
once I hit the boot animation i get a "device not recognized" error.
Anyone else experience this issue?
the next step to troubleshoot is to go back to real factory default and start fresh.
Thanks!
Click to expand...
Click to collapse
I am having the exact same issue!! Were you able to figure it out? I get the slow charging prompt but windows says Device not Recognized. Tried on two windows laptops, a machine with ubuntu install, and a mac.
On the linux machine I try the lsusb command and it does not list it there.
Thanks,
Dean!
Hey there. I exhausted all efforts to get it to work. I tried everything. I rarely used the port to but it was 100% dead. I ended up calling Verizon to have it replaced under warranty.
Sent from my VS980 4G using XDA Premium 4 mobile app
Ah well that sucks. Guess I'll be going to ATT to get mine replaced too!
Thanks,
Dean
So I updated all my devices to Windows 10 (PC, Laptop, Surface) and now I can't connect my note 4 to any of them while in windows, the connection was working good on win 8.1 but on win 10 just nope. I tried using different cables (including the original) and ports and always get the error "This USB Device has malfunctioned" (or nothing at all) and I have been on many different ROMs including android 5.0.1/5.0.2 TW, AOSP 5.1 and TW 5.1 so as I can't manage to fix it on my own would like to ask if anyone else is experiencing this and if anyone managed to fix it?
Also I do know that the USB connection is actually working as I have tested it on a Win 8.0 PC and it does work in Ubuntu on both my PC and Laptop. And I did install kies and even did a full wipe and re-install on my laptop (because I managed to break all the partitions somehow).
And an other question: is there any way to flash something to the device in Linux as for some reason even Odin doesn't see the device in download mode?
hmm sounds wired as i am on windows 10 too and i dont have any problems what so ever. I do not have kies and will never use that ****. I have the drivers installed. try uninstalling the kies bloatware and then get the drivers only and try.
If that dont work then i would say try and find a pc with win 8.1 and flash stock rom and try and see if that will work on win 10. Maybe try and use logcat and see what is going wrong when connecting. Also try installing ADB on pc and see if you can pull logs that way...
Zionator said:
hmm sounds wired as i am on windows 10 too and i dont have any problems what so ever. I do not have kies and will never use that ****. I have the drivers installed. try uninstalling the kies bloatware and then get the drivers only and try.
If that dont work then i would say try and find a pc with win 8.1 and flash stock rom and try and see if that will work on win 10. Maybe try and use logcat and see what is going wrong when connecting. Also try installing ADB on pc and see if you can pull logs that way...
Click to expand...
Click to collapse
Thank you but I installed kies only after I saw I couldn't connect and nope, adb does not connect also but I did pull logs in terminal emulator when both connecting to ubuntu and win 10 and they look exactly the same (except ofc some messages from apps) so probably the phone does the exact same thing but the Windiws OS just fails to connect for some reason.
The thing is I don't have a win8.1/older I could use to flash cause everyone in my familty did the exact same thing, I also need to flash the 5.1.1 bootloader and am stuck cause of the exact same reason.
Any other ideas?
Ask a friend to use there pc someone must have win 8.1 or win7 or a risky thing is use Linux and use odin via wine. If you can't figure it out go to your nearest phone repair shop.
My new HD10 tablet will not power on after I tried to downgrade it to 5.1.2 from what I believed was 5.1.4, but after hours of reading and tinkering I think it might have OTA to 5.3.1.0 without me realizing it.
Right now I cannot get the display to show anything at all. When i attach it to Windows 7 or Windows 10 PCs I have a device show up called "MT65XX Preloader" with no recognized drivers. I have downloaded and installed drivers for this but they are not being recognized for this device (disabled driver signing, told windows to install anyways, says successful but device manager still shows unknown device).
It appears for about 5 second then disappears for 5 and comes back repeatedly.
ADB and fastboot shows no devices being detected.
Does anyone have any suggestions on how I can recover from this? I'm going to setup a Ubuntu VM to see if Linux is any better with recognizing the device.
nockam said:
My new HD10 tablet will not power on after I tried to downgrade it to 5.1.2 from what I believed was 5.1.4, but after hours of reading and tinkering I think it might have OTA to 5.3.1.0 without me realizing it.
Right now I cannot get the display to show anything at all. When i attach it to Windows 7 or Windows 10 PCs I have a device show up called "MT65XX Preloader" with no recognized drivers. I have downloaded and installed drivers for this but they are not being recognized for this device (disabled driver signing, told windows to install anyways, says successful but device manager still shows unknown device).
It appears for about 5 second then disappears for 5 and comes back repeatedly.
ADB and fastboot shows no devices being detected.
Does anyone have any suggestions on how I can recover from this? I'm going to setup a Ubuntu VM to see if Linux is any better with recognizing the device.
Click to expand...
Click to collapse
If you can't boot into stock recovery there's nothing you can do to recovery it at this point. How new is it? Amazon has a 30 day no questions asked replacement policy. You can actually set it all up without even speaking to them usually. Plus they'll send you the new one right away and you have 30 days to return the broken one.