[Q] Converting my ONE into a GE Android

[elfrisi]

So, I unlocked my One, got the S-OFF (HBOOT 1.55), when I was pushing the zip file containing the stock GE ROM, it got stuck on "waiting for device". I've tried uninstalling the drives, and installing them again, but its not working. I can turn on the phone fine, but the Recovery is the Google Bootloader and I can;t seem to find a way to go back to the original HTC Bootloader since it wont let me push files while in the bootloader...

What can I do!?

 

[davewuvswaffles]

So, I unlocked my One, got the S-OFF (HBOOT 1.55), when I was pushing the zip file containing the stock GE ROM, it got stuck on "waiting for device". I've tried uninstalling the drives, and installing them again, but its not working. I can turn on the phone fine, but the Recovery is the Google Bootloader and I can;t seem to find a way to go back to the original HTC Bootloader since it wont let me push files while in the bootloader...

What can I do!?

If you've still got s-off and can use fastboot, you could just change your CID and install a GE ruu.

 

[elfrisi]

If you've still got s-off and can use fastboot, you could just change your CID and install a GE ruu.

I do have the S-OFF, however, once I enter the Fastboot menu, Windows wont recognize the device and wont let me push anything. It gets stuck in "Waiting for device". Ive installed the latest Google USB Device drivers using the SDK Manager and nothing has changed. :crying:

 

[SaHiLzZ]

Try a different USB cable, or port, or a different computer..

Your phone says Fastboot or Fastboot USB?

 

[debeliamark]

Remove unneeded drivers

I do have the S-OFF, however, once I enter the Fastboot menu, Windows wont recognize the device and wont let me push anything. It gets stuck in "Waiting for device". Ive installed the latest Google USB Device drivers using the SDK Manager and nothing has changed. :crying:

If Windows PC can see phone in normal working state ( like MTP device / Android ADB / USB disk ect ... ) mean - you no need to worry - HW is OK, then try to use a small free tool called DeviceRemover and just clean unneeded ( wrong / old / damaged / ect.. ) FastBoot driver(s) from your system and then try again to connect phone in fastboot mode. Hint - use last tab "Display Mode" to select "Hidden / Deattached" devices - these that not work for you.

 

[bobsie41]

So, I unlocked my One, got the S-OFF (HBOOT 1.55), when I was pushing the zip file containing the stock GE ROM, it got stuck on "waiting for device". I've tried uninstalling the drives, and installing them again, but its not working. I can turn on the phone fine, but the Recovery is the Google Bootloader and I can;t seem to find a way to go back to the original HTC Bootloader since it wont let me push files while in the bootloader...

What can I do!?

You'll have to use a different computer, one running a pre windows 8.1 os.
Windows 8.1 only recognises fastboot for 1.55 or greater bootloaders at the moment.
I had the same situation and had to re-install windows 8 which was a bit drastic but solved this problem

 

[Higgins12]

If you're having trouble with the connection in Windows 8.1 like that your Phone does not get recognised, easiest solution get a Linux Live ISO on a USB stick.

Get Universal USB Installer from here http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
Let it Download a UBUNTU Live ISO
Let the Programm install it on your USB stick and set the Persistent File Size to your liking
Boot from the stick
Open Terminal Window
Install "adb" and "fastboot" with .... sudo apt-get install android-tools-adb android-tools-fastboot

Connect the Phone and check if the Phone is recognised (fastboot devices or adb devices)
Do the update

 

[elfrisi]

Well, it was a driver issue. I did everything using the Mac OS X partition of my MacBook (for some odd reason I thought all this process was "exclusive" to Windows due to the exes and whatnot, but I was wrong). Now I am running the Stock Google Play Edition on my phone with no issues.