[SOLVED]Any hope?

Search This thread
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?
 
Last edited:

clsA

Senior Member
Aug 28, 2010
9,912
3,535
Central Florida
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?

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

http://xdaforums.com/showthread.php?t=2358738 this was the guide *Remove red warning from boot screen + custom hboot: http://xdaforums.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.
 

clsA

Senior Member
Aug 28, 2010
9,912
3,535
Central Florida
http://xdaforums.com/showthread.php?t=2358738 this was the guide *Remove red warning from boot screen + custom hboot: http://xdaforums.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.

you should check this post before going any further
http://xdaforums.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://xdaforums.com/showthread.php?t=2477792


3. - Second Lock the bootloader. Instructions are in this thread

http://xdaforums.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.********
 
Last edited:
you should check this post before going any further
http://xdaforums.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


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
 

clsA

Senior Member
Aug 28, 2010
9,912
3,535
Central Florida
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

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
 

clsA

Senior Member
Aug 28, 2010
9,912
3,535
Central Florida
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

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!

Taken for here >> http://xdaforums.com/showthread.php?p=49131915

It Works I been using it for over a year
 

Uzephi

Inactive Recognized Contributor
Apr 20, 2012
3,439
1,892
Phoenix
Google Pixel 3a
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
 
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

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
 

clsA

Senior Member
Aug 28, 2010
9,912
3,535
Central Florida
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

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 ..
 
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 ..

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
 

clsA

Senior Member
Aug 28, 2010
9,912
3,535
Central Florida
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

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.
 
Last edited:

Top Liked Posts