Database Develop

[Q] Converting my ONE into a GE Android

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!?

elfrisi said:
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!?
Click to expand...
Click to collapse
If you've still got s-off and can use fastboot, you could just change your CID and install a GE ruu.

davewuvswaffles said:
If you've still got s-off and can use fastboot, you could just change your CID and install a GE ruu.
Click to expand...
Click to collapse
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:

Try a different USB cable, or port, or a different computer..
Your phone says Fastboot or Fastboot USB?

Remove unneeded drivers
elfrisi said:
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:
Click to expand...
Click to collapse
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.

elfrisi said:
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!?
Click to expand...
Click to collapse
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

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

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.

[Q] Can't use adb/fastboot while in bootloader, after flashing failed.

Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated

TomFader said:
Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated
Click to expand...
Click to collapse
I haven't use Windows 8, but so far I don't have any problem with Windows 7. I assume have already install the HTC driver. If not, you can install the HTC syn which comes with the driver.

rocktv88 said:
I haven't use Windows 8, but so far I don't have any problem with Windows 7. I assume have already install the HTC driver. If not, you can install the HTC syn which comes with the driver.
Click to expand...
Click to collapse
Yes, I already installed the HTC drivers (htc sync +d rivers, then uninstalled htc sync, as it get's annoying while plugin on off of the phone)
My biggest problem is that, now fastboot is not running in bootloader mode, so I can't even flash an image or change back the settings i did.
(And of course seems like in bootloader mode, that windows can't find the phone).
So my Idea would be to flash a Zip.rom, like the over the air updates using the recovery option. It's just that i changed the CID to GOOGLE001. :/

TomFader said:
Yes, I already installed the HTC drivers (htc sync +d rivers, then uninstalled htc sync, as it get's annoying while plugin on off of the phone)
My biggest problem is that, now fastboot is not running in bootloader mode, so I can't even flash an image or change back the settings i did.
(And of course seems like in bootloader mode, that windows can't find the phone).
So my Idea would be to flash a Zip.rom, like the over the air updates using the recovery option. It's just that i changed the CID to GOOGLE001. :/
Click to expand...
Click to collapse
Yes, you can uninstall it or use MSCONFIG to remove it on start up. : )
ok, have you try boot the phone in fastboot mode and type "fastboot devices" in command prompt?

rocktv88 said:
Yes, you can uninstall it or use MSCONFIG to remove it on start up. : )
ok, have you try boot the phone in fastboot mode and type "fastboot devices" in command prompt?
Click to expand...
Click to collapse
Jep, so what i do is, i power the phone on, it boots into stock android --> adb devices works and retunrs my phonenumber (also the windwos driver is fine while in stock android)
i do adb reboot-bootloader and it starts into the bootloader (fastboot is turned off in the settings)
and then I'm stuck, Windows can't find the phone (get a bunch of errors with unsopoorted usb device)
also adb devices and fastboot devices is not working, so i tried to execute different commands like flashing or oem unlock,
but all i get is the message<waiting on device>

TomFader said:
Jep, so what i do is, i power the phone on, it boots into stock android --> adb devices works and retunrs my phonenumber (also the windwos driver is fine while in stock android)
i do adb reboot-bootloader and it starts into the bootloader (fastboot is turned off in the settings)
and then I'm stuck, Windows can't find the phone (get a bunch of errors with unsopoorted usb device)
also adb devices and fastboot devices is not working, so i tried to execute different commands like flashing or oem unlock,
but all i get is the message<waiting on device>
Click to expand...
Click to collapse
Are you on S-off?
Anyway, I would do the RUU. restore your phone and try again with a good custom ROM. Did you check MD5 with the rom you download? You still can connect your phone with ADB. That mean your phone is not brick yet. : )

TomFader said:
Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated
Click to expand...
Click to collapse
windows 8.1 will not work on hboot below 1.54.000 (the only 1.54 that works is from the new GPE 4.4 update).
your going to need access to a windows 7 PC long enough to update your hboot to 1.55 to be able to use fastboot with your phone again. This usually only happens while flashing a RUU not A Rom. Flashing a rom will not affect your version of hboot

clsA said:
windows 8.1 will not work on hboot below 1.54.000 (the only 1.54 that works is from the new GPE 4.4 update).
your going to need access to a windows 7 PC long enough to update your hboot to 1.55 to be able to use fastboot with your phone again. This usually only happens while flashing a RUU not A Rom. Flashing a rom will not affect your version of hboot
Click to expand...
Click to collapse
You are right, i can confirm hboot 1.54.0000 - i was flashing the RUU to convert my HTC ONE toa Google Edition.
So all I need is a windows 7 or lower pc to get fastboot running again?
That's good news, I would have searched for ages.

Yeah it's frustrating I know
If you use the 1.54.000 from the 4.4 GPe update it works also
Sent from my HTC One using Tapatalk

[Q] Trouble with s-off HBoot 1.55

Whats up guys
I am having one hell of a time trying to get s-off on my sprint htc one m7_wls running 4.3. Hboot 1.55. I've tried revone and no matter what I do the command ./revone -P always fails. Then I tried rumrunner and that got to the point Where it passed the two tests then after fixing some skunky rum when it boots me back into fastboot for the 2nd time i get the error FATAL Download updated version from ww . rumrunner. us The only thing i havent tried yet is charging my phone to 100% and trying rumrunner. it was at about 75% the two times i tried it. SO anyway, if anyone here can help me to get one of these programs to work for me or just point me in the right direction I would very much appreciate that.
Thanks Fellas

Check PM

roffo4One said:
Whats up guys
I am having one hell of a time trying to get s-off on my sprint htc one m7_wls running 4.3. Hboot 1.55. I've tried revone and no matter what I do the command ./revone -P always fails. Then I tried rumrunner and that got to the point Where it passed the two tests then after fixing some skunky rum when it boots me back into fastboot for the 2nd time i get the error FATAL Download updated version from ww . rumrunner. us The only thing i havent tried yet is charging my phone to 100% and trying rumrunner. it was at about 75% the two times i tried it. SO anyway, if anyone here can help me to get one of these programs to work for me or just point me in the right direction I would very much appreciate that.
Thanks Fellas
Click to expand...
Click to collapse
Here's what I did:
1) Loaded the @benny3 stock, odex 4.3 ROM ;
2) Booted that ROM up, (and after my first run of rumrunner failed) updated the superSU binary (open superSU and it'll tell you to update, let your recovery do it);
3) When rebooted, I tested adb to assure it works (you need that for sure);
4) I then ran "adb shell" so I could "su" once -- that let me 'grant' access to su so rumrunner won't need to wait for superSU;
5) Rebooted into bootloader ( fastboot (usb) ) so I could test fastboot working "fastboot devices better return good info";
6) ran fastboot reboot to reboot normally;
7) ran rumrunner -- no issues, just anxious waits through the many minute process and reboots.
Hope that helps -- I run linux, so much easier from a driver perspective, but make sure your HTC drivers work and you DO NOT HAVE HTC SYNC installed. Use just the naked USB drivers.

tdhite said:
Here's what I did:
1) Loaded the @benny3 stock, odex 4.3 ROM ;
2) Booted that ROM up, (and after my first run of rumrunner failed) updated the superSU binary (open superSU and it'll tell you to update, let your recovery do it);
3) When rebooted, I tested adb to assure it works (you need that for sure);
4) I then ran "adb shell" so I could "su" once -- that let me 'grant' access to su so rumrunner won't need to wait for superSU;
5) Rebooted into bootloader ( fastboot (usb) ) so I could test fastboot working "fastboot devices better return good info";
6) ran fastboot reboot to reboot normally;
7) ran rumrunner -- no issues, just anxious waits through the many minute process and reboots.
Hope that helps -- I run linux, so much easier from a driver perspective, but make sure your HTC drivers work and you DO NOT HAVE HTC SYNC installed. Use just the naked USB drivers.
Click to expand...
Click to collapse
I had the drivers installed but since I am s on when I uninstall HTC sync when the phone reboots after the rumrunner tests it's reinstalled. Does thst affect the process at all?

roffo4One said:
I had the drivers installed but since I am s on when I uninstall HTC sync when the phone reboots after the rumrunner tests it's reinstalled. Does thst affect the process at all?
Click to expand...
Click to collapse
I guess I'm not helping you anymore?

roffo4One said:
I had the drivers installed but since I am s on when I uninstall HTC sync when the phone reboots after the rumrunner tests it's reinstalled. Does thst affect the process at all?
Click to expand...
Click to collapse
Well -- I'm not sure all that makes sense. But if @bigdaddy619 is helping you, you don't need to look further for help. You're in the exact right hands. I'll follow his lead from here.

Thank you
tdhite said:
Here's what I did:
1) Loaded the @benny3 stock, odex 4.3 ROM ;
2) Booted that ROM up, (and after my first run of rumrunner failed) updated the superSU binary (open superSU and it'll tell you to update, let your recovery do it);
3) When rebooted, I tested adb to assure it works (you need that for sure);
4) I then ran "adb shell" so I could "su" once -- that let me 'grant' access to su so rumrunner won't need to wait for superSU;
5) Rebooted into bootloader ( fastboot (usb) ) so I could test fastboot working "fastboot devices better return good info";
6) ran fastboot reboot to reboot normally;
7) ran rumrunner -- no issues, just anxious waits through the many minute process and reboots.
Hope that helps -- I run linux, so much easier from a driver perspective, but make sure your HTC drivers work and you DO NOT HAVE HTC SYNC installed. Use just the naked USB drivers.
Click to expand...
Click to collapse
thank you so much for your help

xbdarkfox said:
thank you so much for your help
Click to expand...
Click to collapse
What version of software were you on when this was successful? I am on 3.05.651.6 and understand it is necessary to downgrade to be able to use rumrunner successfully.
Thanks!

Docarut said:
What version of software were you on when this was successful? I am on 3.05.651.6 and understand it is necessary to downgrade to be able to use rumrunner successfully.
Thanks!
Click to expand...
Click to collapse
Sprint_HTC_One_m7wls 3.04.651.2 I had flashed an unsupported ROM and used Sprint_HTC_One_m7wls_3_04_651_2_RUU to flash back to stock. Rumrunner takes a few times just be patient

[SOLVED]Any hope?

So i was trying to get my at&t htc one back to 100% stock so i could send it in for warranty. I got my replacement htc one, but while in the process of going back to stock something happened the phone wont load into recovery, when it boots into the os it stays at the htc screen but plays the at&t boot animation sound, and to top it off the old phone wont connect properly through usb (the new one will just fine). So i am stuck in bootloader anyone have any ideas?

crazyvash1 said:
So i was trying to get my at&t htc one back to 100% stock so i could send it in for warranty. I got my replacement htc one, but while in the process of going back to stock something happened the phone wont load into recovery, when it boots into the os it stays at the htc screen but plays the at&t boot animation sound, and to top it off the old phone wont connect properly through usb (the new one will just fine). So i am stuck in bootloader anyone have any ideas?
Click to expand...
Click to collapse
what guide are you using to get to stock ?
how far did you get ? are you s-off ?
what was the last version OS on the phone ? What hboot ?

clsA said:
what guide are you using to get to stock ?
how far did you get ? are you s-off ?
what was the last version OS on the phone ? What hboot ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2358738 this was the guide *Remove red warning from boot screen + custom hboot: http://forum.xda-developers.com/showthread.php?t=2316726 thats where things got messed up i pushed the FUU and flashed it thats where things got messed up. the phone is s-off Hboot-1.55.0000 and the os-1.20.401.1(3.10.502.2)
im guessing i screwed up and rushed things i just figured i would post as a last resort and get outside input before i decided if i should send it in as is send the new one back or what lol i appreciate any help.

crazyvash1 said:
http://forum.xda-developers.com/showthread.php?t=2358738 this was the guide *Remove red warning from boot screen + custom hboot: http://forum.xda-developers.com/showthread.php?t=2316726 thats where things got messed up i pushed the FUU and flashed it thats where things got messed up. the phone is s-off Hboot-1.55.0000 and the os-1.20.401.1(3.10.502.2)
im guessing i screwed up and rushed things i just figured i would post as a last resort and get outside input before i decided if i should send it in as is send the new one back or what lol i appreciate any help.
Click to expand...
Click to collapse
you should check this post before going any further
http://forum.xda-developers.com/showpost.php?p=47794190&postcount=3
I don't know what you mean by I pushed the FUU and flashed it. do you mean you flashed firmware?
If you flashed a custom hboot with no red text you will brick the phone when you lock the bootloader.
Don't lock bootloader !!
Use this tool to remove Tampered and set to Locked
Guru_Bootloader_Reset_1.0.zip
http://www.androidfilehost.com/?fid=23501681358538585
MD5: fdb8264a8f4741bae22939cd7734f7c2
at this point just flash the AT&T RUU
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
and see where your at.
From the Guide you linked
Before you can proceed with the 2 following threads for removing Tampered and then Locking you need to have Superuser installed. There are links to how to do this in each thread. You can also use this toolkit. Just remember to delete the SuperUser and busybox apk if installed before you return the phone.
2. - First remove the Tampered Flag. Instructions are in this thread
http://forum.xda-developers.com/showthread.php?t=2477792
3. - Second Lock the bootloader. Instructions are in this thread
http://forum.xda-developers.com/showthread.php?t=2475914
The older REVONE commands/instructions for Tampered and Locking:
Now since you had to install SuperUser to perform the previous 2 steps make sure you unroot by deleting the Superuser.apk and busybox.apk (If installed) from the /system/app folder and also the su binary from /system/xbin on your phone.
If you ran a RUU your systems firmware and software is all reset back to stock. If you restored via Stock ROM reset or Nandroid you should be running the stock software but it could be on non stock (version mismatch) firmware.
In either case your bootloader should display Locked and no Tampered just like out of the box. Now all that’s left is to S-On. To do that issue this fastboot command:
Code:
fastboot oem writesecureflag 3
Done - device should be just like it was out of the box with no indication of any modding.
*******I am not responsible for any problems you encounter. I am simply informing you of what is needed to complete a restoration to Stock. Read all steps and commands carefully and perform them in the correct order.********
Click to expand...
Click to collapse

clsA said:
you should check this post before going any further
http://forum.xda-developers.com/showpost.php?p=47794190&postcount=3
I don't know what you mean by I pushed the FUU and flashed it. do you mean you flashed firmware?
If you flashed a custom hboot with no red text you will brick the phone when you lock the bootloader.
Don't lock bootloader !!
Use this tool to remove Tampered and set to Locked
Guru_Bootloader_Reset_1.0.zip
http://www.androidfilehost.com/?fid=23501681358538585
MD5: fdb8264a8f4741bae22939cd7734f7c2
at this point just flash the AT&T RUU
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
and see where your at.
From the Guide you linked
Click to expand...
Click to collapse
the problem im having is the phone wont connect properly through usb to either of my computers ive tried different ports and different cables
This device cannot start. (Code 10)
A device which does not exist was specified.
thats the error i get in device status but my other htc connects perfect

crazyvash1 said:
the problem im having is the phone wont connect properly through usb to either of my computers ive tried different ports and different cables
This device cannot start. (Code 10)
A device which does not exist was specified.
thats the error i get in device status but my other htc connects perfect
Click to expand...
Click to collapse
are they both windows 8 computers ?
Windows 8.1 and hboot 1.44 don't get along
you'll have to use a driver hack to get it working

Both windows 8.1 like i said the weird part is one phone works perfect through usb the old one (the one i need to work) doesn't

crazyvash1 said:
Both windows 8.1 like i said the weird part is one phone works perfect through usb the old one (the one i need to work) doesn't
Click to expand...
Click to collapse
yeah .. here's the driver hack to make it work
Download
I repeat this is a REALLY DIRTY solution that may harm your system, personal data, hardware and/or cat.
Here are the steps:
0. Have a Linux or Windows LiveCD just in case something goes wrong
1. Download and extract files from attachment
2. Navigate to the folder corresponding to your system version (x86 = 32-bit, x64 = 64 bit)
3. Right-click franken-usb.bat and click "Run as Administrator"
5. Wait for it to finish and reboot the system. If everything went fine, you will boot your system successfully
6. Install ADB/Fastboot drivers just like on Windows 8
7. Connect your phone in Fastboot mode to your USB 2.0 port and check if it works
8. Enjoy and wait for official fix
How does it work:
It's not any kind of magic - it just replaces Windows 8.1's usbhub.sys and usbport.sys with Windows 8's ones.
Old files don't check for BOS descriptor so Fastboot can work.
Script updated - it should now actually copy the files but please double check if files were copied to C:\Windows\system32\Drivers!
Hope it helps you!
Regards!
Click to expand...
Click to collapse
Taken for here >> http://forum.xda-developers.com/showthread.php?p=49131915
It Works I been using it for over a year

Ok thank you very much i will try this when i get home from work tomorrow and hopefully its works for me then i can just follow the guide you posted to get back to stock then all will be good

im still getting the same issue with the drivers i made sure to manually install the files but still no luck.

Have you tried a Linux live boot disc? If you have troubles with Windows drivers, always fall back to Linux as it will always work if the device isn't faulty.
Sent from my HTC6500LVW using XDA Free mobile app

Uzephi said:
Have you tried a Linux live boot disc? If you have troubles with Windows drivers, always fall back to Linux as it will always work if the device isn't faulty.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
ive been trying with linux my issue now is just getting fasboot to work (as i have very little knowledge of linux) and still having no luck with windows im considering just sending the replacement they sent and then saving and buying a phone out right

crazyvash1 said:
ive been trying with linux my issue now is just getting fasboot to work (as i have very little knowledge of linux) and still having no luck with windows im considering just sending the replacement they sent and then saving and buying a phone out right
Click to expand...
Click to collapse
all you have to do is install the driver I linked reboot the pc
put the phone is fastboot USB mode and plug it into the pc.
if it's still not visible with fastboot devices
go to device manager find the failed driver / Unknown device
choose update driver / Browse for Driver / Let me Pick / uncheck show compatible hardware
Choose HTC on the left and My HTC Version 2.0.7.22 on the Right. ...Click next / click done ..

clsA said:
all you have to do is install the driver I linked reboot the pc
put the phone is fastboot USB mode and plug it into the pc.
if it's still not visible with fastboot devices
go to device manager find the failed driver / Unknown device
choose update driver / Browse for Driver / Let me Pick / uncheck show compatible hardware
Choose HTC on the left and My HTC Version 2.0.7.22 on the Right. ...Click next / click done ..
Click to expand...
Click to collapse
ok so i got it to work in fastboot now as for getting back to stock i am on hboot 1.55 and the os will not boot now i can flash the hboot 1.44 that you linked and i can use the gruu bootloader to get the tampered and set to lock (should i do this with having no working os on the phone?) and once you run the RUU.exe doesnt the phone need to be booted up and into the os? with usb debugging enabled or can i run it with it in the bootloader or fastboot? i just want to make sure im clear before i attempted to go through and do this again lol

crazyvash1 said:
ok so i got it to work in fastboot now as for getting back to stock i am on hboot 1.55 and the os will not boot now i can flash the hboot 1.44 that you linked and i can use the gruu bootloader to get the tampered and set to lock (should i do this with having no working os on the phone?) and once you run the RUU.exe doesnt the phone need to be booted up and into the os? with usb debugging enabled or can i run it with it in the bootloader or fastboot? i just want to make sure im clear before i attempted to go through and do this again lol
Click to expand...
Click to collapse
just do the steps in order
the RUU.exe step will put the OS back on the phone and your essentially done after that
From HTC ..ignore the t-mobile
Manual system update instructions:
If you are outside of T-Mobile/Wi-Fi coverage, or the update is not found, you may perform a manual system update. This process requires that you download and install HTC Sync Manager first in order to get the proper drivers. If you do not have HTC Sync Manager installed already, you may download the software from http://www.htc.com/www/software/htc-sync-manager/.
WARNING: Performing the system update manually will delete all information from the device. Ensure all information is backed up before proceeding. See the Help & How To section of this website for more information on backing up your device contents.
Performing the ROM Update:
1. Download and save the HTC One™ for T-Mobile ROM update to your PC.
2. Connect your device to your PC via the supplied USB cable.
3. If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
4. Once the device is properly recognized on the PC, locate the HTC One™ for T-Mobile ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
5. Follow all of the system update wizard instructions shown on your PC.
6. Once the update is complete, click Finish in the Wizard and the device will reboot.
7. Once the device reboots, the initial setup wizard will appear.
8. Once the initial setup process is complete, the device is ready for use.
Note: If the ROM update wizard fails to recognize the device, close the wizard and then follow the steps below:
· From a powered off state, hold VOLUME DOWN while powering on the device.
· Use the volume buttons to scroll to FASTBOOT and then press the POWER button to select it.
· Connect the device to the PC while in this state and attempt the ROM update again.
To exit FASTBOOT manually, use the volume keys to navigate to REBOOT and press the POWER button to select it.
Click to expand...
Click to collapse

Thank you so much for your help everything is stock and perfect its all set and ready to be sent back

crazyvash1 said:
Thank you so much for your help everything is stock and perfect its all set and ready to be sent back
Click to expand...
Click to collapse
Very good ...just hit the thanks button and change the thread title to [solved] if you get time

Cannot change CID back from SuperCid

Hi all, I have a tricky problem, I converted my M7 to GPE following this thread "[RUU] Google Edition Conversion. 5.0.1 RUU Zip pre-rooted/non-rooted + firmware ". All went fine but in the end the GPE lacks some stuff that I really like on Stock. Long story short I wanted to go back to stock, so I followed the part in the thread refffering to GPE => Stock
Prerequsites:
S-off
1.44 HBoot
RUU for your device (I used )
Ok I thought reversing since I had S-off would be a simple affair and maybe I took a misstep along the way but I got it done.
Here's what worked FOR ME.
1) set CID to superCID
2) install the 1.44 Hboot in RUU mode (thanks SneakyGhost) http://d-h.st/qfc
3) install the RUU for your phone/carrier
Click to expand...
Click to collapse
I just forgot before the last fastboot reboot to change the CID from 11111111 to my cid.
I flashed the 7.19.401.2-FULL_STOCK_WIPE.zip using 1.44 Hboot. Now it is stuck at the HTC logo afterwards and keeps rebooting, and ends up in stock recovery the phone with the red triangle and exclamation sign.
I did a factory reset from fastboot and now i get the phone with the red triangle. which means it is in the stock recovery but something is wrong. I can manage it to put it in fastboot, but that is all.
Windows each time I connect the phone is no longer recognizing the device so adb fails (I assume because it is the wrong CID). It just says waiting for device and nothing happens further.
How do I change the CID if I cannot connect the device? Tricky ... I tried several adb drivers (I use win 8.1) like "minimal_adb_fastboot_v1.2_setup" and "Universal_Naked_Driver_0.72" . The best I got is a driver installed and showing in device manager but with message " device cannot start. (Code 10)".
Any help is really appreciated.
Best regards

gmariust said:
Hi all, I have a tricky problem, I converted my M7 to GPE following this thread "[RUU] Google Edition Conversion. 5.0.1 RUU Zip pre-rooted/non-rooted + firmware ". All went fine but in the end the GPE lacks some stuff that I really like on Stock. Long story short I wanted to go back to stock, so I followed the part in the thread refffering to GPE => Stock
I just forgot before the last fastboot reboot to change the CID from 11111111 to my cid.
I flashed the 7.19.401.2-FULL_STOCK_WIPE.zip using 1.44 Hboot. Now it is stuck at the HTC logo afterwards and keeps rebooting, and ends up in stock recovery the phone with the red triangle and exclamation sign.
I did a factory reset from fastboot and now i get the phone with the red triangle. which means it is in the stock recovery but something is wrong. I can manage it to put it in fastboot, but that is all.
Windows each time I connect the phone is no longer recognizing the device so adb fails (I assume because it is the wrong CID). It just says waiting for device and nothing happens further.
How do I change the CID if I cannot connect the device? Tricky ... I tried several adb drivers (I use win 8.1) like "minimal_adb_fastboot_v1.2_setup" and "Universal_Naked_Driver_0.72" . The best I got is a driver installed and showing in device manager but with message " device cannot start. (Code 10)".
Any help is really appreciated.
Best regards
Click to expand...
Click to collapse
If you have flashed hboot 1.44 to your device then you'll need to get your hands on a windows 7 PC, ubuntu or Mac. Hboot 1.44 won't work with win8. Once done post the output of "fastboot getvar all"

alray said:
If you have flashed hboot 1.44 to your device then you'll need to get your hands on a windows 7 PC, ubuntu or Mac. Hboot 1.44 won't work with win8. Once done post the output of "fastboot getvar all"
Click to expand...
Click to collapse
Thanky you for your quick reply, I suppose it needs to be a real ubuntu machine, cannot use a vmware machine

gmariust said:
Thanky you for your quick reply, I suppose it needs to be a real ubuntu machine, cannot use a vmware machine
Click to expand...
Click to collapse
It will not work in a vm config but will work fine in live mode (you can use Ubuntu without installing it via a live usb or live cd option)

Cool man, this one worked, I managed to change the CID back to the original. I have flashed then, the recovery to twrp and installed the following Guru Reset file "Guru_Reset_M7_3.62.401.1.zip". Is a bit old but nothing that OTA will not solve. Thanks again! It's updating already!