Related
So I was really dumb and tried to factory reset my phone while I was on a custom rom and now am stuck in a boot loop. I have been googling around to try and figure out what to do but nothing seems to work. When I try and Hboot an RUU stock file it gets stuck at UserData. I also cannot get into recovery only Hboot.
I am relocked and S-On. Don't know what else to do. Is it beyond repair?
Ok when you run the ruu are you selecting fastboot in the hboot screen ? Does it say USB after fastboot when connected ?
Bigtjmc said:
Ok when you run the ruu are you selecting fastboot in the hboot screen ? Does it say USB after fastboot when connected ?
Click to expand...
Click to collapse
When i hold down power and volume down it goes to the Hboot screen and it automatically looks for the PH39IMG.zip file so no I am not running fastboot but when I do select fastboot it only says fastboot no USB (i do not have it plugged into PC btw).
When you select fastboot , then plug it in the pc and it should go USB , if not you need to install the drivers
If you need the drivers you dl htc sync manager , or dl the toolkit in the dev forum and install them that way .
Fastboot USB is showing up but HTC Sync is saying there are no devices connected, not sure if thats a problem.
Ok did you do this when you ran the ruu ?
brandork said:
Fastboot USB is showing up but HTC Sync is saying there are no devices connected, not sure if thats a problem.
Click to expand...
Click to collapse
HTC sync looks for devices that are powered on...just try and run the ruu..listen to bigtjmc
AND DON'T UNPLUG ONCE IT'S GOING, THE PROCESS TAKES A WHILE...
Sent from my HTC PH39100 using Tapatalk 2
Well I was actually extracting the RUU image from my PC's temp folder then placing it on my phone to allow Hboot to find it. I am now running the actual RUU software on my PC and it seems to be working. I will update when its finished. Thanks so much for your help.
Right on ,
Let us know what happens .
The ruu is stuck at 34%...I have it plugged in still not sure what to do from here
How long has it been stuck?
Don't unplug it...just let it sit...
Sent from my HTC PH39100 using Tapatalk 2
sorry guys I was in class and couldnt respond. so right now i went through the RUU recovery steps and it allowed me to re-do the RUU setup. I just redid it thinking my PC may have messed up but I am stuck at 34% again. Any suggestions for what I should do after I recover it again?
edit: forgot to mention that I left it for a few hours while in class and it took me to the recovery setup
Can you get into recovery when it sends you there ?
no I cannot get into recovery. All i can do is get into fastboot.
Right but what recovery setup you mentioned earlier ? Maybe you got a bad ruu download try and re dl it or try a different version.
Sorry the recovery I mentioned was a recovery process the RUU takes you through when an update fails. I also have tried about 4 different downloads to no avail. I have been using this file here
Ok , what Rom did you have on the phone ?
I couldnt tell you for sure I installed it pretty quickly after the ICS update was available. I want to say I installed one of the HTC Holiday or Raider ICS roms because that was available before the Vivid one. Once that was installed I rooted.
Ok one last thing and I will see what I can come up with , the ruu screen when it stopped at 34% what was it trying or waiting on ?
After only four day of having this phone i managed to brick it. I would really like to know if its fixable or if i have a really nice paper weight. Im stuck on a boot loop, I was half way through flashing a rom when it suddenly shut off. Now it will not boot up. I can load into the bootlader but when i try to go into recovery it just sends me to fastboot. When i restart the phone i can see the old recovery (TWRP)for just an instant but then the screen goes completely black. If i plug in to my pc, nothing happens my computer detects it but it says y device is damaged nd it cant identify it. PLEASE HELP Am i out of luck?
Ive looked around but i couldnt seem to find anyone with the same problem as me (Sprint Variant)
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
There's a Sprint One forum as well, so hopefully you found a ROM on there!
http://forum.xda-developers.com/forumdisplay.php?f=2215
jaythenut said:
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
Click to expand...
Click to collapse
I really hope so because on a college budget i cant afford another phone D:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
wnp_79 said:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
Click to expand...
Click to collapse
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
i suggest you contact with HTC customservices to repair this problem.
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
DynamicRam said:
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Click to expand...
Click to collapse
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
dont give up
Sent from my HTC One
Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
Edit: Just got done typing the stuff below and saw you can't connect to your device in fastboot? What do you mean by re-installed driver?
Don’t worry, as long as you can still get into hboot your phone is not completely bricked!
The fastboot commands I referred to need to be carried out on your laptop/pc when you phone is connected in fastboot.
Can I assume that as you have already unlocked bootloader and flashed a custom recovery you are already familiar with this and have your computer set up for fastboot commands?
(Apologies if you already know some of this, best not to skip parts out though!)
I’d start with downloading a fresh version of your chosen recovery, and place it in your fastboot directory ready. I’d also do the same with your ROM.
Like you have already done, boot into fastboot. Connect your phone to your pc, and the red text should change to ‘Fastboot USB’.
Then open up command prompt and get to your fastboot directory. (On Windows 7 you just find that folder in Explorer, hold shift and right-click, then choose ‘Open command window here’.)
To check your pc is talking to your phone, type ‘fastboot devices’. You should get a device serial number back if all is well.
Then type ‘fastboot erase cache’ and hit enter.
Then type ‘fastboot erase recovery’ and hit enter.
Then type ‘fastboot flash recovery [name of recovery].img’ and hit enter.
Then type ‘fastboot reboot recovery’ and hit enter.
Hope fully you should successfully boot into recovery now. Once in recovery, mount USB storage and copy over your fresh ROM. Choose to do a full wipe including cache and dalvik, then reflash your ROM.
Reboot.
Let me know how this goes.
cronus101 said:
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
Click to expand...
Click to collapse
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Muquita said:
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Click to expand...
Click to collapse
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
wnp_79 said:
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Click to expand...
Click to collapse
(Win8 but the procces is identical.) All my drivers are up to date. Still no love.
On the dev forum is a thread that includes all the latest drivers (including an app to remove older drivers.)
Find that thread, download the drivers and bmp and driver removal tool. Remove drivers with tool, install the new drivers, reboot, connect phone and see if 'adb devices' finds anything.
Also make sure you're using the latest adb.
Sent from my HTC One using xda app-developers app
thneed said:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Click to expand...
Click to collapse
This actually sounds really similar to my situation.. Would you care to be a little more specific on the procedure? noob here.
Tabtoub said:
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
Click to expand...
Click to collapse
My pc will not recognize my phone. The drivers are up to date but when i plug it in it says something malfunctioned ?
I was trying to unroot my HTC ONE but i didn't do it right and now i'm in a mess my phone is relocked it still says tampered and it's s-on every time i try to flash a ota form bell even if i unlock it again it stops the green progress bar right at the end and i have to unplug it and restart it and now it's showing me a black screen with a android label and it stays stuck on that screen plz help i've been searching for hours to know how to fix it. plz help me anyone it's from bell mobility and i'm in Canada i can't find a ruu so that's why i tried to flash the ota...
danskins31 said:
I was trying to unroot my HTC ONE but i didn't do it right and now i'm in a mess my phone is relocked it still says tampered and it's s-on every time i try to flash a ota form bell even if i unlock it again it stops the green progress bar right at the end and i have to unplug it and restart it and now it's showing me a black screen with a android label and it stays stuck on that screen plz help i've been searching for hours to know how to fix it. plz help me anyone it's from bell mobility and i'm in Canada i can't find a ruu so that's why i tried to flash the ota...
Click to expand...
Click to collapse
are you flashing a rom.zip in fastboot RUU mode (fastboot oem rebootRUU) ? if so it's normal for the green bar to stop just short, and the command window should say flash completed.
just type fastboot reboot-bootloader and then fastboot erase cache
followed by fastboot reboot your phone will take about 3-5 min to boot up the first time
to fix the relocked just unlock again with the .bin file you got the first time you unlocked
you'll also need to reflash a custom recovery and root if you so desire
clsA said:
are you flashing a rom.zip in fastboot RUU mode (fastboot oem rebootRUU) ? if so it's normal for the green bar to stop just short, and the command window should say flash completed.
just type fastboot reboot-bootloader and then fastboot erase cache
followed by fastboot reboot your phone will take about 3-5 min to boot up the first time
to fix the relocked just unlock again with the .bin file you got the first time you unlocked
you'll also need to reflash a custom recovery and root if you so desire
Click to expand...
Click to collapse
can you give me a step by step lol i'm on a mac so it's a bit different i'm guessing
danskins31 said:
can you give me a step by step lol i'm on a mac so it's a bit different i'm guessing
Click to expand...
Click to collapse
No it's not that different. Just use the terminal app and follow the instructions to unroot it. Make sure you have the htc drivers installed
Ktan188 said:
No it's not that different. Just use the terminal app and follow the instructions to unroot it. Make sure you have the htc drivers installed
Click to expand...
Click to collapse
can someone send me a link to a good one or give me steps because i'm a noob
danskins31 said:
can someone send me a link to a good one or give me steps because i'm a noob
Click to expand...
Click to collapse
You can still search it for yourself, even if you are a noob. But here is a link : http://www.ibtimes.co.uk/articles/4...ot-official-firmware-android422-jellybean.htm
help me
i don't know what is the right ruu to use or ota all of the one's i try fail and i know i have to see my version i did it's BM_001
and my i read also that i need a ruu that has 666 in the middle for bell but still no luck
danskins31 said:
i don't know what is the right ruu to use or ota all of the one's i try fail and i know i have to see my version i did it's BM_001
and my i read also that i need a ruu that has 666 in the middle for bell but still no luck
Click to expand...
Click to collapse
I really don't know how to say it any better
go back to htc-dev and unlock your bootloader - http://www.htcdev.com/bootloader/
re-flash TWRP recovery - fastboot flash recovery TWRP.img
and re-flash a rom (if you don't have a rom on your sdcard you'll need to push or sideload a rom to your phones SDcard
the command is adb push name of rom.zip /data/media/0 change the name of coarse
here is the Nandroid Backup CID BM 001 3.23.666.1 for your phone
http://www.htc1guru.com/dld/m7-twrp-nandroid-backup-cid-bm___001-3-23-666-1-zip/
You will extract the Backup to your fastboot folder (make a folder called backup in fastboot) and then push it to your phone while it's booted to Recovery
adb push backup /data/media/0/TWRP/BACKUPS/Your phones Serial number/backup
you get your phones serial number by typing adb devices
C:\fastboot>adb devices
List of devices attached
HT343******* recovery
C:\fastboot>adb push backup /data/media/0/TWRP/BACKUPS/HT343*******/backup
push: backup/firmware_3.62.401.1.zip -> /data/media/0/TWRP/BACKUPS/HT343*******/
backup/firmware_3.62.401.1.zip
1 file pushed. 0 files skipped.
3881 KB/s (28795564 bytes in 7.245s)
Click to expand...
Click to collapse
a full backup will take much longer to transfer (4-5min maybe more)
plz help
i can't get adb working on my mac but fastboot works fine and i looked at tons on ways to get it to work but it still doesn't show me my devices listed and without that i can't go forward with the process
danskins31 said:
i can't get adb working on my mac but fastboot works fine and i looked at tons on ways to get it to work but it still doesn't show me my devices listed and without that i can't go forward with the process
Click to expand...
Click to collapse
adb works in recovery, not in fastboot usb
have you unlocked the bootloader and flashed the recovery ?
clsA said:
adb works in recovery, not in fastboot usb
have you unlocked the bootloader and flashed the recovery ?
Click to expand...
Click to collapse
thank you so much for everything it worked out great and i got the google edition rom its really neat thanks again for all of ur guys help!
Hi xda!
I recently got a HTC One from a friend, as my old phone was worn out. It turned out he had rooted it, tampered with it, the whole nine yards. I was not told he had rooted it, so I accepted a prompt asking me to update the phone to what I believe was 4.4.2, KitKat. I now realize that should not have been done. When the phone restarted it went to the HTC startup logo, into a kind of blue screen (not the BSOD), the Google logo flashed on the screen for 0.5 seconds, and then it got stuck on this weird blue/turqoise screen. Nothing happened.
I called my friend, he told me he rooted it etc., and that I should try a factory reset, and if that didn't work, complete reset (including the system folder wipe). That obviously didn't work, but I didn't know any better as I have never touched a rooted phone in my life, and I'm thus a complete noob when it comes to terminology, what steps to take and so on.
Now I have a phone with no OS, stuck at the HTC logo when I start it normally, and all I can do is boot up into bootloader. I can also access TWRP. I have installed HTC Sync on my laptop, but the phone is not detected properly (meaning, the "device connected" sound is played, and I can find "Android device" in device manager, but the HTC Sync can't find the phone) when connected through a USB. It is not the USB that came with the phone. I also installed Squabbi's HTC One toolkit, which basically is the one-click interface of pushing revone etc. to the phone. Problem is, "error, device not detected".
I've browsed around for a good six hours without any luck, other than that I've started to understand how this is all connected.
Phone is
*TAMPERED*
*UNLOCKED*
M7_UL
S-ON
HBOOT 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
I pray to the mighty tech gods of xda to help me out. I looked for similar threads, couldn't find any that were simple and similar enough for me to understand. I must admit I'm very keen to learn this, so if someone know of any place where basic terminology is explained, I'd really appreciate that. Other than that, a step by step instruction on how to proceed from this cluster**** would also be highly appreciated (what I need installed on my laptop, where I can find ROM's, what flashing means etc.).
Thank you in advance!
PrimalMK said:
Hi xda!
I recently got a HTC One from a friend, as my old phone was worn out. It turned out he had rooted it, tampered with it, the whole nine yards. I was not told he had rooted it, so I accepted a prompt asking me to update the phone to what I believe was 4.4.2, KitKat. I now realize that should not have been done. When the phone restarted it went to the HTC startup logo, into a kind of blue screen (not the BSOD), the Google logo flashed on the screen for 0.5 seconds, and then it got stuck on this weird blue/turqoise screen. Nothing happened.
I called my friend, he told me he rooted it etc., and that I should try a factory reset, and if that didn't work, complete reset (including the system folder wipe). That obviously didn't work, but I didn't know any better as I have never touched a rooted phone in my life, and I'm thus a complete noob when it comes to terminology, what steps to take and so on.
Now I have a phone with no OS, stuck at the HTC logo when I start it normally, and all I can do is boot up into bootloader. I can also access TWRP. I have installed HTC Sync on my laptop, but the phone is not detected properly (meaning, the "device connected" sound is played, and I can find "Android device" in device manager, but the HTC Sync can't find the phone) when connected through a USB. It is not the USB that came with the phone. I also installed Squabbi's HTC One toolkit, which basically is the one-click interface of pushing revone etc. to the phone. Problem is, "error, device not detected".
I've browsed around for a good six hours without any luck, other than that I've started to understand how this is all connected.
Phone is
*TAMPERED*
*UNLOCKED*
M7_UL
S-ON
HBOOT 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
I pray to the mighty tech gods of xda to help me out. I looked for similar threads, couldn't find any that were simple and similar enough for me to understand. I must admit I'm very keen to learn this, so if someone know of any place where basic terminology is explained, I'd really appreciate that. Other than that, a step by step instruction on how to proceed from this cluster**** would also be highly appreciated (what I need installed on my laptop, where I can find ROM's, what flashing means etc.).
Thank you in advance!
Click to expand...
Click to collapse
well a lot of the work seems to already be done
your unlocked / rooted which means you should have a custom recovery installed.
boot the phone by holding the power + volume down
this will bring up the bootloader. use the volume key to choose recovery aand hit the power button. when you boot into recovery come back and report the name and version of recovery. I.E. Teamwin recovery 2.5.0.0 or clockworkmod 6.0.3.1 ...I'll be here the next couple hrs
clsA said:
well a lot of the work seems to already be done
your unlocked / rooted which means you should have a custom recovery installed.
boot the phone by holding the power + volume down
this will bring up the bootloader. use the volume key to choose recovery aand hit the power button. when you boot into recovery come back and report the name and version of recovery. I.E. Teamwin recovery 2.5.0.0 or clockworkmod 6.0.3.1 ...I'll be here the next couple hrs
Click to expand...
Click to collapse
Version of TWRP is 2.5.0.0. Currently trying to re-install an OS. Need one that the current version of TWRP can flash to the phone, as flashing a new version of TWRP does not work. I have no preferences when it comes to OS's. A stock OS (is OS and ROM the same thing?) would be fine.
Also, found out that doing stuff on a Windows 7 laptop was easier than on my own Windows 8. The phone is at least detected on the Windows 7, which means I will be able to flash stuff to it through cmd, something I wasn't able to do from the Windows 8.
PrimalMK said:
Version of TWRP is 2.5.0.0. Currently trying to re-install an OS. Need one that the current version of TWRP can flash to the phone, as flashing a new version does not work. I have no preferences. A stock OS (is OS and ROM the same thing?) would be fine.
Click to expand...
Click to collapse
Well your going to need adb / fastboot on your PC
use mine here >> https://www.dropbox.com/s/0wzwt8843zx27nh/Fastboot.zip
and install the HTC Drivers here >> http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
unzip that to c:\ so you have c:\fastboot in windows explorer
now inside the folder you shift + right click / command prompt here
now you have a command prompt window type
fastboot getvar all
and post the result here / minus your serial number and IMEI
then i can find you the correct recovery and rom for your phone
---------- Post added at 08:04 PM ---------- Previous post was at 08:02 PM ----------
PrimalMK said:
Also, found out that doing stuff on a Windows 7 laptop was easier than on my own Windows 8. The phone is at least detected on the Windows 7, which means I will be able to flash stuff to it through cmd, something I wasn't able to do from the Windows 8.
Click to expand...
Click to collapse
yes window 8 will be a problem till you get another hboot above 1.44/1.54
hboot 1.55 has no problem on windows 8 ( I use windows 8.1)
clsA said:
instructions
Click to expand...
Click to collapse
Downloaded fastboot, unzipped in c:
Drivers from that link are classed as malware. Trying to find earlier drivers/other mirror.
Find attachment.
Still looking for drivers. Apparently "every" browser blocks exe-files from being downloaded. Changed settings, managed to download it, run as admin. No response.
PrimalMK said:
Find attachment.
Still looking for drivers. Apparently "every" browser blocks exe-files from being downloaded. Changed settings, managed to download it, run as admin. No response.
Click to expand...
Click to collapse
this will work fine
just put TWRP and the Rom in the fastboot folder
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
clsA said:
this will work fine
just put TWRP and the Rom in the fastboot folder
Click to expand...
Click to collapse
error: cannot open 'openrecovery.......img'
What to do?
PrimalMK said:
error: cannot open 'openrecovery.......img'
What to do?
Click to expand...
Click to collapse
is it in the fastboot folder ?
clsA said:
is it in the fastboot folder ?
Click to expand...
Click to collapse
Yes, see screenshot.
PrimalMK said:
Yes, see screenshot.
Click to expand...
Click to collapse
is the command window in c:\fastboot ?
did you copy paste the command or try and type it ?
clsA said:
is the command window in c:\fastboot ?
did you copy paste the command or try and type it ?
Click to expand...
Click to collapse
My bad. Managed to run it, but then it crashes straight away. Can that have anything to do with the driver not installed?
PrimalMK said:
My bad. Managed to run it, but then it crashes straight away. Can that have anything to do with the driver not installed?
Click to expand...
Click to collapse
fastboot crashes ?
no if fastboot getvar worked it will all work
it's only 4 commands and your phone will be working
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
adb sideload rom.zip
sideload takes about 8 min
calculation icatkg
clsA said:
fastboot crashes ?
no if fastboot getvar worked it will all work
Click to expand...
Click to collapse
Restarted a couple of times etc. It worked. Will do the ROM thing now.
PrimalMK said:
Restarted a couple of times etc. It worked. Will do the ROM thing now.
Click to expand...
Click to collapse
great your about done ...your phone will be android 4.3 when it finishes
don't take any updates to the OS
cmd said it sent the ROM to the phone. I was in the TWRP adb sideload on my phone when it was transferred. Then that was it. 100% on cmd. Phone shut down. Suddenly discovered I had to install on the phone. WAT. I do so, then wait until completion. I anxiously restart the phone. It's alive again!
Really, thanks so much clsA! You made me a very happy person! :victory:
PrimalMK said:
cmd said it sent the ROM to the phone. I was in the TWRP adb sideload on my phone when it was transferred. Then that was it. 100% on cmd. Phone shut down. Suddenly discovered I had to install on the phone. WAT. I do so, then wait until completion. I anxiously restart the phone. It's alive again!
Really, thanks so much clsA! You made me a very happy person! :victory:
Click to expand...
Click to collapse
no problem, hit the thanks button
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