Anyone w/ an htc one m8 windows phone ever successfully booted a andriod rom on one of these phones?
This past Friday windows pushed out an update that put my phone in a boot loop. I've tried using the Windows Device Recovery Tool to no avail.
For me it is the last straw with Microsoft. Naturally AT&T store wasn't much help either. They were pushing me to buy a new phone and i'm not even done paying this one yet.
Needless to say i'm very irritated and will be moving over to t-mobile next chance i get. Any help about properly attempting to install an Android ROM on this phone would be great. I used to do it years ago but I forgot what software is needed to do a PC to Device boot.
It won't work. You can't flash Android on the Windows version of this phone.
Sent from my Redmi Note 2 using Tapatalk
Related
My vibrant got soft bricked yesterday, I am able to get it into download mode and I have ODIN all lines up to revert to stock, but windows 7 64bit says USB device not recognized. I have tried everything to get it to read. I have tried installing every driver i could get my hand on and i just cannot get the computer to recgnize my phone! Any help would be greatly appreciated.
I have the exact same problem. I updated my Vibrant using Kies Mini for windows 7 64bit. After the installation, my phone restarted, the welcome logo and S came up. After that the screen went black and it vibrated every 5 seconds. The 4 touch controls lit up if i touched them and they stayed lit.
I got into recovery mode and clear all data and format my microUSB as well but it wouldn't solve the problem.
I got into download mode but my Windows said USB device not recognized CODE 43. I tried to manually install Samsung Android USB driver but I got error code 10.
so I couldn't ODIN it back.
Can anyone help?
You're both sure you're using the right Odin (for 64)?
This is weird.
I Just tried again today and my computer recognized it instantly. I was able to flash to stock 2.1
What I did was insert my sim card in the phone today. Yesterday I didn't put my sim card in.
Another way to do it I've realized is to try to use a computer with xp on it and odin 1.7 (I believe). The newer windows vista, 7, etc. Are a lot more picky and difficult to work with sometimes.
Sent from my SGH-T959 using XDA Premium App
Make sure you installed the Samsung driver that is for 64 bit.
Then, make sure you have admin rights, sometimes depending on how the computer was set up you may not be high enough on the root directory. This is especially true when one family is using the same computer and all have their own personal account/profile. If both of those things are ok and you are sure, Then:
Install this This is what i am using on my win7 64 pro i know it works. So, if this does not work then I would guess it is your users rights you haven't resolved yet.
Good luck
Yeah I tried 3 different computers. 2 with xp and the original one in my post, nothing worked. I figured i was screwed so i just went to use the insurance i had on it but they wouldn't let me because it isn't broken lost or stolen. They told me to contact tmobile. So I did. I went onto tmobile.com and chatted with someone who had me try to get it into the recovery screen that a previous poster said he was able to do but i couldn't get into it so he said we could exchange it. I gave him all the info and he sent one out.
steven1193 said:
Yeah I tried 3 different computers. 2 with xp and the original one in my post, nothing worked. I figured i was screwed so i just went to use the insurance i had on it but they wouldn't let me because it isn't broken lost or stolen. They told me to contact tmobile. So I did. I went onto tmobile.com and chatted with someone who had me try to get it into the recovery screen that a previous poster said he was able to do but i couldn't get into it so he said we could exchange it. I gave him all the info and he sent one out.
Click to expand...
Click to collapse
I've done the same with my phone. Talked to a TMobile rep, they diagnosed it as a USB port issue. New phone on the way.
I had the same issue on my computer with any of my USB 2.0 ports. Thought what the hell, I'll try plugging into my USB 3.0 port and BAM! It worked.
Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
ichihaifu said:
Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
Click to expand...
Click to collapse
Sounds like the cable is faulty. Borrow a new one to test or get a cheap one off eBay.
flumpster said:
Sounds like the cable is faulty. Borrow a new one to test or get a cheap one off eBay.
Click to expand...
Click to collapse
While I find that unlikely, I will try to look for a new one. But meanwhile lets assume that its not indeed the case, is there anything I could do at that point?
ichihaifu said:
While I find that unlikely, I will try to look for a new one. But meanwhile lets assume that its not indeed the case, is there anything I could do at that point?
Click to expand...
Click to collapse
Why do you find that unlikely?
There are cases exactly the same as yours all over this forum where the cable can charge the prime but cannot be used to install drivers etc.
http://forum.xda-developers.com/showpost.php?p=37662700&postcount=539
http://forum.xda-developers.com/showthread.php?p=39303129&highlight=cable#post39303129
flumpster said:
Why do you find that unlikely?
There are cases exactly the same as yours all over this forum where the cable can charge the prime but cannot be used to install drivers etc.
http://forum.xda-developers.com/showpost.php?p=37662700&postcount=539
http://forum.xda-developers.com/showthread.php?p=39303129&highlight=cable#post39303129
Click to expand...
Click to collapse
Hmm, alright. Just because I havent really roughed up the cable at all and everything worked fine until the said date.
But for now theres no way to try another cable, I'l look for new one next week.
ichihaifu said:
Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
Click to expand...
Click to collapse
I gained root on 4.1.x via twrp and supersu, just after unlocking it. I am not shure if reinstalling 4.1.was really useful...but I did.
Today I got the HTC One from a guy that works at a T-Mobile store. The phone came rooted but I wanted to unroot it. We went into TWRP and touched wipe. We wiped out everything including the operating system. I tried connecting the phone to my computer but it wouldn't recognize it. I'm not sure if its because of my laptop which is a windows 8 or because the phone might have USB debugging disabled. I have absolutely no experience in this and I have no idea what to do. :/ Any advice would be nice Thank you!
So wait, can you access recovery? I haven't gotten around to rooting mine yet so not 100% the process for the one but if you can access recovery you should be able to mount usb storage then the computer will pick it up.
Sent from my HTC One using xda app-developers app
do you have the necessary drivers?
Sent from my SGH-M919
people have had issues with adb and windows 8. search the international thread for a solution.
I was working on restoring my HTC one to stock since my SIM slot happened to break. In the process I must have messed something up and I can no longer get into any version of android, I am stuck at the bootloader screen.
My thinking is that if I run the RUU I will be able to kick myself out of this and have a functioning device, my problem is that I can't get windows 8 to identify my phone in fastboot to run the RUU.
Has anyone had any luck with wine on OS X or is there another way I can flash a firmware to my phone?
broopa said:
I was working on restoring my HTC one to stock since my SIM slot happened to break. In the process I must have messed something up and I can no longer get into any version of android, I am stuck at the bootloader screen.
My thinking is that if I run the RUU I will be able to kick myself out of this and have a functioning device, my problem is that I can't get windows 8 to identify my phone in fastboot to run the RUU.
Has anyone had any luck with wine on OS X or is there another way I can flash a firmware to my phone?
Click to expand...
Click to collapse
VMWare or Virtualbox works far better on OSX and I'd trust that vs Wine any day of the week. Got an old windows xp disc laying around?
I don't think XP would work since I have USB 3 drives on the MBP, but if it would thats an easy fix. I think I can find one laying around my house.
I have searched (I have 12 tabs open as I type) these forums. I see a few similar cases but I am not finding a solution. I have use CMHENDRA's guides but I am having no luck. (It is my daughters phone so I will give you what information I know) BTW, I contribute in the Note II galleries, I have rooted and flashed HTC One X, Several Nexus 7's, my Note II, Galaxy SII, Galaxy S, HTC Sensations, Nexus 4 and a few older ones. I can currently see all those phones on my laptop. Not the L9.
I believe my son tried to flash CWM for my daughter. She is notoriously rough on phones and he was trying to make sure she was protected. The phone boots into the LG Security Error screen. I can get it to boot into S/W Upgrade mode. I have completed or can complete all the steps to most of the guide. I CANNOT get my Win8.1 laptop or my sons Win7 laptop to recognize the phone to complete any of the guides. B2C, Fastboot, etc. I can see various entries in the Device Manager, I uninstall and reinstall with Driver Signing turned off. I have now reached the point where I have done so many things that I have probably confused myself.
When it did get the security error, the software had been set to USB Debugging and Unknown Sources was allowed. The firmware was 20H. B2C cannot get the phone information (I know it is probably the drivers as is everything else).
Any help, ideas, etc. would be great. I would love to be a hero for my daughter.
dsore1218 said:
I have searched (I have 12 tabs open as I type) these forums. I see a few similar cases but I am not finding a solution. I have use CMHENDRA's guides but I am having no luck. (It is my daughters phone so I will give you what information I know) BTW, I contribute in the Note II galleries, I have rooted and flashed HTC One X, Several Nexus 7's, my Note II, Galaxy SII, Galaxy S, HTC Sensations, Nexus 4 and a few older ones. I can currently see all those phones on my laptop. Not the L9.
I believe my son tried to flash CWM for my daughter. She is notoriously rough on phones and he was trying to make sure she was protected. The phone boots into the LG Security Error screen. I can get it to boot into S/W Upgrade mode. I have completed or can complete all the steps to most of the guide. I CANNOT get my Win8.1 laptop or my sons Win7 laptop to recognize the phone to complete any of the guides. B2C, Fastboot, etc. I can see various entries in the Device Manager, I uninstall and reinstall with Driver Signing turned off. I have now reached the point where I have done so many things that I have probably confused myself.
When it did get the security error, the software had been set to USB Debugging and Unknown Sources was allowed. The firmware was 20H. B2C cannot get the phone information (I know it is probably the drivers as is everything else).
Any help, ideas, etc. would be great. I would love to be a hero for my daughter.
Click to expand...
Click to collapse
I can't get mine to work either. Closest thing I've gotten is using omap4boot-for_optimus-v1.21
its different from some of the others, in that its a blue background and it doesnt actually list the p769. However, after selecting option 5, and following onscreen instructions, I was able to get my front capacitive buttons to light up, but nothing else. I can't enter S/W upgrade mode, I can't get LG recovery tool to recognise my phone, I am absolutely **** out of luck. I dont know if using omap4boot-for_optimus-v1.21 will help or hurt you, but im just explaining my experiences.
Have you installed the omap driver for fastboot?
Thanks for your replies. Windows 8.1 is installing the OMAP driver and when I try to update it, Windows says it has determined that I have the best one installed already or some BS like that. That seems to be the last piece of the puzzle. I am not getting it to use the fastboot commands and when I am in the LG upgrade thing, it cannot connect on the first of the three calls so it says to check the USB cord and connection. ( I have tried 5-6 cords including the OEM cord ).
Thanks again for your help. I will uninstall the OMAP drivers when I get home and see if I can't get the ones I downloaded to install.
I don't have Windows 8.1 so I'm not sure how to address the driver issue. I reer as wel.commend you uninstall the driver, both of them. The one under Android Phone in the device manager and the one called TI Boards in the device manager.
1. Uninstall all OMAP drives (Two of them)
2. Disconnect from the internet (to preventing Windows update from selecting its own driver.
3. Follow steps to fastboot. When connecting your phone have device manager open and right click the device that is flashing on and off (you will see the device manager refreshing and stuffs. It will dissappear after about two seconds but if you get the right click in and the option to install the driver, do it, point to the fastboot driver.
4. Disconnect phone after driver install and pull the battery.
5. Fastboot again, using option 1.
6. Quickly install same driver on the new device in device manager. Be quick.
7. Disconnect, Pull battery
8. Fastboot again
9. Flash ICS U and X
10. Make sure your LG drivers are installed.
11. Reboot PC.
12. Now you should be able to get into SW UPGRADE MODE with the plugging in of the USB
Should not lock up at 15%, make sure you have drivers installed for this.
13. Should work and reboot to home screen automatically.
14. If you really must, fastboot again and install JB U and X
dsore1218 said:
Thanks for your replies. Windows 8.1 is installing the OMAP driver and when I try to update it, Windows says it has determined that I have the best one installed already or some BS like that. That seems to be the last piece of the puzzle. I am not getting it to use the fastboot commands and when I am in the LG upgrade thing, it cannot connect on the first of the three calls so it says to check the USB cord and connection. ( I have tried 5-6 cords including the OEM cord ).
Thanks again for your help. I will uninstall the OMAP drivers when I get home and see if I can't get the ones I downloaded to install.
Click to expand...
Click to collapse
I've heard fastboot (and several other programs) aren't working on Windows 8. You need windows 7
Sent from my LGMS769 using XDA Premium 4 mobile app