Database Develop

[Q] I made my HTC ONE a brick :(

Hi, i did not find a solution anywhere so i trust on you guys I have HTC ONE, and it is rooted and i also have TWRP v2.6.3.0. Then i was trying to update to Android 4.3 and Sense 5.5...it did not work...so i tried to unroot it...then i messed up the phone no i can only go to recovery mode, or twrp...that´s it...how i can make it functional again ? I just wanted it back to original, no need to root anymore...

sandelin85 said:
Hi, i did not find a solution anywhere so i trust on you guys I have HTC ONE, and it is rooted and i also have TWRP v2.6.3.0. Then i was trying to update to Android 4.3 and Sense 5.5...it did not work...so i tried to unroot it...then i messed up the phone no i can only go to recovery mode, or twrp...that´s it...how i can make it functional again ?
Click to expand...
Click to collapse
Use USB-OTG and flash a ROM using that.

If u can get to the bootloader try flashing a new recovery. fastboot flash recovery recovery.img
Sent from my HTC One using Tapatalk

sandelin85 said:
Hi, i did not find a solution anywhere so i trust on you guys I have HTC ONE, and it is rooted and i also have TWRP v2.6.3.0. Then i was trying to update to Android 4.3 and Sense 5.5...it did not work...so i tried to unroot it...then i messed up the phone no i can only go to recovery mode, or twrp...that´s it...how i can make it functional again ? I just wanted it back to original, no need to root anymore...
Click to expand...
Click to collapse
Or else sideload a rom.zip

Sorry, i am kinf of a newbie with those kind of stuff But when i go to fastboot/bootloader, my computer does not work with it, i have tried many different drivers...so i can´t put any files in it anymore...

So you can get into recovery? Have you tried wiping it yet?
Sent from my HTC One using Tapatalk

sandelin85 said:
Sorry, i am kinf of a newbie with those kind of stuff But when i go to fastboot/bootloader, my computer does not work with it, i have tried many different drivers...so i can´t put any files in it anymore...
Click to expand...
Click to collapse
Use windows 7/8 with the latest HTC drivers, it doesn't work with 8.1.

instigator008 said:
So you can get into recovery? Have you tried wiping it yet?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
yes, i can go to twrp v2.6.3.0...then i try to install: OTA_M7_UL_JB43_SENSE55_MR_HTC_Europe_3.62.401...then it says: no md5 file found, no file_contexts --> failed...so i think that i have delete the whole OS...it says also: No OS installed...ups :/

Have you tried wiping through twrp?
Sent from my HTC One using Tapatalk

sandelin85 said:
yes, i can go to twrp v2.6.3.0...then i try to install: OTA_M7_UL_JB43_SENSE55_MR_HTC_Europe_3.62.401...then it says: no md5 file found, no file_contexts --> failed...so i think that i have delete the whole OS...it says also: No OS installed...ups :/
Click to expand...
Click to collapse
Looks like your system partition is empty, so you'll have to install a whole rom ,an OTA won't help an empty system

n1234d said:
Looks like your system partition is empty, so you'll have to install a whole rom ,an OTA won't help an empty system
Click to expand...
Click to collapse
Okey, could you please tell me (like for a child), how to do that ?

sandelin85 said:
Okey, could you please tell me (like for a child), how to do that ?
Click to expand...
Click to collapse
Okay, do you have any rom(eg. ARHD).zip on your phone? If you do, flash that via twrp, and you're done
If you don't, copy a rom to a USB flash drive and connect it to your phone with an OTG Cable, and flash it via twrp
If you don't have an OTG cable, try this to sideload a rom to your internal sd card http://teamw.in/ADBSideload

n1234d said:
Okay, do you have any rom(eg. ARHD).zip on your phone? If you do, flash that via twrp, and you're done
If you don't, copy a rom to a USB flash drive and connect it to your phone with an OTG Cable, and flash it via twrp
If you don't have an OTG cable, try this to sideload a rom to your internal sd card
No, i don´t have any rom in the phone...i´m now trying the last option...the sideload-thing...my other computer is very slow...so it will take while...but how i can get the phone like it was when i bought it ? So no root access and stock rom and so on ???
Click to expand...
Click to collapse

sandelin85 said:
n1234d said:
Okay, do you have any rom(eg. ARHD).zip on your phone? If you do, flash that via twrp, and you're done
If you don't, copy a rom to a USB flash drive and connect it to your phone with an OTG Cable, and flash it via twrp
If you don't have an OTG cable, try this to sideload a rom to your internal sd card
No, i don´t have any rom in the phone...i´m now trying the last option...the sideload-thing...my other computer is very slow...so it will take while...but how i can get the phone like it was when i bought it ? So no root access and stock rom and so on ???
Click to expand...
Click to collapse
Boot your phone into bootloader-fastboot
Connect it to your pc so it shows fastboot-usb
then open cmd in the folder containing adb.exe (press shift+right click>open command prompt window here) and type fastboot getvar all
Post results after removing IMEI and serial no.
Click to expand...
Click to collapse

n1234d said:
sandelin85 said:
Boot your phone into bootloader-fastboot
Connect it to your pc so it shows fastboot-usb
then open cmd in the folder containing adb.exe (press shift+right click>open command prompt window here) and type fastboot getvar all
Post results after removing IMEI and serial no.
Click to expand...
Click to collapse
Now my computer with newest drivers and windows 7 would not even recognice the phone...damn, i´m stuck...again ! Samsung S4 was much easier...i made it a brick, then i connect to safe mode, and samsung kies rescue everything
Click to expand...
Click to collapse

sandelin85 said:
n1234d said:
Now my computer with newest drivers and windows 7 would not even recognice the phone...damn, i´m stuck...again ! Samsung S4 was much easier...i made it a brick, then i connect to safe mode, and samsung kies rescue everything
Click to expand...
Click to collapse
When your phone is in fastboot, type
fastboot devices
Does it list your phone?
If it doesn't, try changing USB ports/cord, and also try uninstalling and then fresh installing new drivers after restarting your pc, then connecting your phone.
Sent from my iPod touch using Tapatalk
---------- Post added at 12:26 AM ---------- Previous post was at 12:22 AM ----------
And what happened to the sideload? Did the rom zip get copied?
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse

How are you getting on? You most likely haven't bricked your ONE
Sent from my HTC One using XDA Premium 4 mobile app

When your phone is in fastboot, type
fastboot devices
Does it list your phone?
If it doesn't, try changing USB ports/cord, and also try uninstalling and then fresh installing new drivers after restarting your pc, then connecting your phone.
Now it finds it again
nd what happened to the sideload? Did the rom zip get copied?
Sideload would not connect, it fails all the time...
How are you getting on? You most likely haven't bricked your ONE
I have tried all things that you guys have suggested...i can´t get any of them to work, for now...So hard find all the right links and so on...i´m not great with android...is there any video or story, how to do that ? I suck My english also, i´m from Finland

It's definitely NOT bricked. I'll keep an eye on this thread, you're getting great help but if you don't end up getting it fixed send me a PM, I sometimes forget about a thread I need to check back in on. It's for sure fixable and there's great advice in here.
Edit I somehow missed your last post before posting this. Send me a PM, and I'll help you get it fixed up after work.

sandelin85 said:
When your phone is in fastboot, type
fastboot devices
Does it list your phone?
If it doesn't, try changing USB ports/cord, and also try uninstalling and then fresh installing new drivers after restarting your pc, then connecting your phone.
Now it finds it again
nd what happened to the sideload? Did the rom zip get copied?
Sideload would not connect, it fails all the time...
How are you getting on? You most likely haven't bricked your ONE
I have tried all things that you guys have suggested...i can´t get any of them to work, for now...So hard find all the right links and so on...i´m not great with android...is there any video or story, how to do that ? I suck My english also, i´m from Finland
Click to expand...
Click to collapse
ok so fastboot is working, as suggested before post a "fastboot getvar all" (remove IMEI and s/n).
If sideload isn't working you can use "adb push", but first thing is to reflash custom recovery just in case it's corrupted.
so download CWM or TWRP (from the threads in xda), then
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
then
adb push <name of rom>.zip /sdcard/ (this will take anywhere between 5 to 15minutes and not show progress, eventually it should come back with "success")
then
install zip in recovery, and choose the <name of rom>.zip and install it.

HELPPP deleted my internal storage

Ok guys I went to wipe my htc one using twrp and I accidently wiped my internal storage so there nothing on my device to boot up I can get into twrp but I dont have any zips on there to flash I also tried to sideload but adb wont recognize my device which is weird because fastboot works fine I went to bestbuy Walmart radioshack to by an otg cable and try it with flash drive but no one has one so I ordered one from ebay but it will take a week to get it can someone please help with any other sugestions please pleasee I need my phone back

You may have to switch recoveries to TWRP 2.6.3.3 OR 2.6.3.0, and use a windows 7 machine.

SaHiLzZ said:
You may have to switch recoveries to TWRP 2.6.3.3 OR 2.6.3.0, and use a windows 7 machine.
Click to expand...
Click to collapse
What will switching recoverys do?

Did you try "adb push rom.zip /sdcard/rom.zip" while you were on the home screen of the recovery?

Novasunshine said:
Did you try "adb push rom.zip /sdcard/rom.zip" while you were on the home screen of the recovery?
Click to expand...
Click to collapse
No I tried it while in bootloader mode also I just check I am running twrp 2.6.3.4

maxtcee said:
No I tried it while in bootloader mode also I just check I am running twrp 2.6.3.4
Click to expand...
Click to collapse
Try it in recovery and also check to see if the device is being detached while in recovery by typing in "adb devices" in the command prompt.

Nope
If I use htc one toolkit while in bootloader and I fastboot I get my device show up but when I do adb I get nothing

maxtcee said:
Nope
If I use htc one toolkit while in bootloader and I fastboot I get my device show up but when I do adb I get nothing
Click to expand...
Click to collapse
So when you type in "adb devices" while in recovery it shows nothing? No device attached? Also what version of windows are you on?

Yea it shows nothing I'm using windows vista

maxtcee said:
Yea it shows nothing I'm using windows vista
Click to expand...
Click to collapse
So no adb in recovery, but fastboot working hmm. So adb devices shows nothing?
Your device is obviously being detected to have fastboot working.
Try adb kill-server to reset adb and then check if it's detectable in recovery, also make sure to mount the data.
Use a different computer if available
Make sure you don't have any tethers installed that would ruin adb like easy tether
Try downloading and reinstalling the adb universal set up drivers.
Try running a RUU if you can
Sorry if i'm not much help I'm still noobish to all this still

Novasunshine said:
So no adb in recovery, but fastboot working hmm. So adb devices shows nothing?
Your device is obviously being detected to have fastboot working.
Try adb kill-server to reset adb and then check if it's detectable in recovery, also make sure to mount the data.
Use a different computer if available
Make sure you don't have any tethers installed that would ruin adb like easy tether
Try downloading and reinstalling the adb universal set up drivers.
Try running a RUU if you can
Sorry if i'm not much help I'm still noobish to all this still
Click to expand...
Click to collapse
ok so i updated my adb drivers and i can get adb to recognize i used htc toolkit and adb pushed the the on my revocery but not sure how long it takes for the zip to transfer cause i tried to flash the rom and it says fail cannot open zip
do you know how long it takes to push a rom onto phone?
nevermind i got it flashing rom as we speak thanks for all your help dude

maxtcee said:
ok so i updated my adb drivers and i can get adb to recognize i used htc toolkit and adb pushed the the on my revocery but not sure how long it takes for the zip to transfer cause i tried to flash the rom and it says fail cannot open zip
do you know how long it takes to push a rom onto phone?
Click to expand...
Click to collapse
Takes about 1 - 5 minutes depending on rom size also adb wont say anything till its finished
---------- Post added at 05:21 AM ---------- Previous post was at 05:16 AM ----------
maxtcee said:
ok so i updated my adb drivers and i can get adb to recognize i used htc toolkit and adb pushed the the on my revocery but not sure how long it takes for the zip to transfer cause i tried to flash the rom and it says fail cannot open zip
do you know how long it takes to push a rom onto phone?
nevermind i got it flashing rom as we speak thanks for all your help dude
Click to expand...
Click to collapse
Your welcome glad its working finally

[Q] Stuck in bootloader, bricked?

Hey guys! I'm kinda stumped here. :crying:
I wanted to restore my phone back to the stock developer edition RUU (Brightstar US) but it threw an error 155. So I tried the Google Play Edition RUU but I guess I should of downloaded a newer version because mine was on 4.3. As usual it asked to flash the file again but it didn't work. (waiting to device)..
The GPE bootloader was already flashed with the OS: coloured red. Fastboot commands wouldn't work so I boot up into Android and I thought of flashing the ENG HBOOT via ADB. Which worked. Alas fastboot commands still won't work and I can't get my device to boot into anything else except into the bootloader.
If you need more information just ask. Any help is greatly appreciated! :fingers-crossed:

squabbi said:
Hey guys! I'm kinda stumped here. :crying:
I wanted to restore my phone back to the stock developer edition RUU (Brightstar US) but it threw an error 155. So I tried the Google Play Edition RUU but I guess I should of downloaded a newer version because mine was on 4.3. As usual it asked to flash the file again but it didn't work. (waiting to device)..
The GPE bootloader was already flashed with the OS: coloured red. Fastboot commands wouldn't work so I boot up into Android and I thought of flashing the ENG HBOOT via ADB. Which worked. Alas fastboot commands still won't work and I can't get my device to boot into anything else except into the bootloader.
If you need more information just ask. Any help is greatly appreciated! :fingers-crossed:
Click to expand...
Click to collapse
Hi, can you enter to recovery ? Try to install clockworkmod, then press "adb sideload" and try to flash that rom: "Guru_Reset_M7_2.24.163.2", It helps me yesterday to wake up my htc with just bootloader and with fautly recovery.

deejay89 said:
Hi, can you enter to recovery ? Try to install clockworkmod, then press "adb sideload" and try to flash that rom: "Guru_Reset_M7_2.24.163.2", It helps me yesterday to wake up my htc with just bootloader and with fautly recovery.
Click to expand...
Click to collapse
Thanks for helping me out. I couldn't enter recovery before. But I may be able to get the fastboot drivers working and flash CWM. :highfive:
I'll let you know how it goes. :good:

squabbi said:
Thanks for helping me out. I couldn't enter recovery before. But I may be able to get the fastboot drivers working and flash CWM. :highfive:
I'll let you know how it goes. :good:
Click to expand...
Click to collapse
Have you got Windows 8.1 or USB 3.0?
Sent from my HTC One using Tapatalk

n1234d said:
Have you got Windows 8.1 or USB 3.0?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I have Windows 8 and USB 3.0. But I did try using the USB 2.0 Ports. I have another laptop with Windows 7 without the HTC Drivers installed and it seems to work.

[Q] HTC One (M7) Bricked???

Hello. I have the following problem. I friend of mine that I've sold him my old rooted Htc One tried to make 4.4. kitkat
He tried to install
Android_Revolution_HD-One-53.0zip
BUT I don't know how he managed to stuck his phone.The problem is when I am power on the phone it shows the white HTC screen with the red letters "this build is for development purpose only..." after a while reboots in TWRP v2.5.0.0
And that's it , I cannot do anything because my PC won't recognize it via USB cable.
Any suggestions?
(excuse me for my English, with love from Greece )

As long as it boots into Recovery its not bricked. Do you have the HTC Driver installed on your computer?
Android Revolution HD 53 requires min. TWRP 2.6.3.3. Your version is too old.

foxgre said:
Hello. I have the following problem. I friend of mine that I've sold him my old rooted Htc One tried to make 4.4. kitkat
He tried to install
Android_Revolution_HD-One-53.0zip
BUT I don't know how he managed to stuck his phone.The problem is when I am power on the phone it shows the white HTC screen with the red letters "this build is for development purpose only..." after a while reboots in TWRP v2.5.0.0
And that's it , I cannot do anything because my PC won't recognize it via USB cable.
Any suggestions?
(excuse me for my English, with love from Greece )
Click to expand...
Click to collapse
From recovery go to fastboot connect phone to pc.
It must be recognized.
Then flash boot.img which is in the Revolution.zip.
Then install the rom via recovery.
Remember for unlock and not s-off users the boot.img must be flashed befor flashing a rom.zip.
Sent by myself, without help )

i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly

SAME problem (or pretty similar) here
foxgre said:
i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly
Click to expand...
Click to collapse
SAME problem (or pretty similar) here, trying to instal ARHD61.1... I don't know how did I screw up this so much...
My bootloader is TAMPERED, UNLOCKED, S-On. Recovery TRWP (2.7) launches but... many things don't work.
First thing I have to mention is that I didn't forget to enable debugging before all this started (and now I can't launch android to do it).
My HTC drivers should be up-to-date, as I installed yesterday HTC sync 3.00.52...
In bootloader, if I type "fastboot devices" I get "FA34HW903605 fastboot", and "fastboot reboot.bootloader" does what it is expected to do...
In recovery, "adb push" tells me "error: device not found".
Can someone help me? If you need more details, just ask. Thanks

foxgre said:
i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly
Click to expand...
Click to collapse
Duwie_80 said:
SAME problem (or pretty similar) here, trying to instal ARHD61.1... I don't know how did I screw up this so much...
My bootloader is TAMPERED, UNLOCKED, S-On. Recovery TRWP (2.7) launches but... many things don't work.
First thing I have to mention is that I didn't forget to enable debugging before all this started (and now I can't launch android to do it).
My HTC drivers should be up-to-date, as I installed yesterday HTC sync 3.00.52...
In bootloader, if I type "fastboot devices" I get "FA34HW903605 fastboot", and "fastboot reboot.bootloader" does what it is expected to do...
In recovery, "adb push" tells me "error: device not found".
Can someone help me? If you need more details, just ask. Thanks
Click to expand...
Click to collapse
can you guys check out FAQ #2 in my guide: http://forum.xda-developers.com/showthread.php?t=2541082 if that's the problem you have

nkk71 said:
can you guys check out FAQ #2 in my guide: http://forum.xda-developers.com/showthread.php?t=2541082 if that's the problem you have
Click to expand...
Click to collapse
Let me try and I'll tell you later. I also think it's a matter of drivers, so I was downloading and re-installing it... Thank you for your help
-------------------------------------------------- UPDATE --------------------------------------------------------------------------------
Well, I followed your steps (LET ME THANK YOU FOR MAKING THAT GUIDE) and now the device is "My HTC" as you show.
Something has changed:
If I type "adb devices" (in PC) when phone is in fastboot, the listing is void (before I got "FA34HW903605 fastboot"), and if I do the same while phone is in recovery, I get the mentioned "FA34HW903605 recovery".
In Windows7 I don't see "My HTC" as a conventional USB storage or Memory of a Camera (should it be?)
I've managed to ADB PUSH a ROM (ARHD) in recovery, but now I get an error message: "Unable to mount '/data' " and "Unable to mount internal storage " then FAILED. Now I'll try flashing a new recovery...

WOW WOW WOW!! It was enough for me, sir
1st) Solve comunnication issues as shown in FAQ #2 here
2nd) Solve TWRP recovery mount issues by:
2.a) Installing any other (clockwork) in fastboot using One All In One Kit (eaaaasy)
2.b) Formatting cache, system, data partitions
2.c) Installing TWRP again using One All In One Kit (Android Revolution REQUIRES this recovery)
2.d) Sending the ROM ('adb push your_rom.zip /sdcard/wherever_you_want_it')
2.e) Installing it from TWRP recovery.
An that was all. THANKS A LOT nkk71; without your help I still would be here trying to figure out what's broken... Thanks.

Duwie_80 said:
WOW WOW WOW!! It was enough for me, sir
1st) Solve comunnication issues as shown in FAQ #2 here
2nd) Solve TWRP recovery mount issues by:
2.a) Installing any other (clockwork) in fastboot using One All In One Kit (eaaaasy)
2.b) Formatting cache, system, data partitions
2.c) Installing TWRP again using One All In One Kit (Android Revolution REQUIRES this recovery)
2.d) Sending the ROM ('adb push your_rom.zip /sdcard/wherever_you_want_it')
2.e) Installing it from TWRP recovery.
An that was all. THANKS A LOT nkk71; without your help I still would be here trying to figure out what's broken... Thanks.
Click to expand...
Click to collapse
no problem, glad to be of help
remember for most 4.4 ROMs, (for m7_u/ul) TWRP 2.6.3.3 (or higher) is recommended at the moment.
though you should be good by downloading it, then checking MD5 to make sure the download isnt corrupt (that site doesnt work with download managers), then:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery and push the rom

Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:

foxgre said:
Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:
Click to expand...
Click to collapse
you're really not giving any details... so you hear a sound... what does Windows Device Manager show??

foxgre said:
Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:
Click to expand...
Click to collapse
It wont be so easy, I'm afraid. Even if comunication issues are solved, you won't be able to copy your ROM using windows file manager, opening the phone like a conventional drive...
You have to install "ADB" in your PC (search in HTC ONE subforums, there's a lot of info about ADB pusing (=copying) ROMS) and use it to copy your ROM. One advice: while "pushing" the ROM, be patient: it takes a long time. When your ROM is "pushed", just install it in recovery and... that's it!!
I think here you have a good starting point.

Duwie_80 said:
It wont be so easy, I'm afraid. Even if comunication issues are solved, you won't be able to copy your ROM using windows file manager, opening the phone like a conventional drive...
You have to install "ADB" in your PC (search in HTC ONE subforums, there's a lot of info about ADB pusing (=copying) ROMS) and use it to copy your ROM. One advice: while "pushing" the ROM, be patient: it takes a long time. When your ROM is "pushed", just install it in recovery and... that's it!!
I think here you have a good starting point.
Click to expand...
Click to collapse
Thanks again i am already looking for it.

AT LAST!!!
I've managed to push the rom.
Thank you very much for your help

foxgre said:
AT LAST!!!
I've managed to push the rom.
Thank you very much for your help
Click to expand...
Click to collapse
Hey, congratulations!! :good::good::good:

HTC One (M7) Sprint Might be Bricked Help?

Hello
Currently my phone is useless, I am blaming myself but somewhat of the ROM I used before this all happened.
For starters, my bootloader is unlocked and s-on. I successfully installed TWRP and rooted using SuperSU. I wanted to try out the custom ROM ViperOne. It installed perfectly fine without any errors. But when I rebooted the phone I am greeted with the lockscreen with no service (x by the bars) and when I go to unlock the phone it goes to a white screen with the HTC logo in the center. It will continue to stay at this screen till it reboots again and does the same thing.
At this point I am frustrated and followed this guide http://forum.xda-developers.com/showthread.php?t=2503646 to revert back to Stock. I was able to do every step correctly besides the flashing of the radio and pushing the Stock_Rom on the phone.
I was able to install the stock rom by putting it on my internal storage and flashing it that way, but still no luck with the radio. But now the Stock_Rom is doing the exact same thing as the Viper, Whitescreen with HTC. Plus it is constantly saying "Unfortunately Phone has stopped" making it unusable.
If someone could please help me out or direct me to another tut to follow I will appreciate it very much. Because at this point I am to believe that I bricked my device and I am unaware if I am able for an upgrade anytime soon.
Thank you for you time.

A little update.
I am not starting to think this whole problem has to do with my radio, simply I do not have 1. How do I get this working again?

Another update.
I tried to follow this guide http://forum.xda-developers.com/showthread.php?t=2250904 (Very helpful btw :good
But still no luck, it froze me at the black screen with HTC and no loading bar.
I just want to be able to use my phone again :crying:

Everything you need is in the first link you posted.

BD619 said:
Everything you need is in the first link you posted.
Click to expand...
Click to collapse
Thank you for your response.
Like I sad, I tried that link already but with no luck. I could be doing something wrong, but I am following word for word.

kavinsky_ep said:
Thank you for your response.
Like I sad, I tried that link already but with no luck. I could be doing something wrong, but I am following word for word.
Click to expand...
Click to collapse
Latest radio can be found HERE

BD619 said:
Latest radio can be found HERE
Click to expand...
Click to collapse
I've downloaded 1.00.20.1108 and I am trying to flash it using fastboot flash zip radio.zip (I renamed it to type it in easier).
But every time I press enter it does signature checking... then it says FAILD (remote: 12 signature verify fail)
Any ideas?

kavinsky_ep said:
I've downloaded 1.00.20.1108 and I am trying to flash it using fastboot flash zip radio.zip (I renamed it to type it in easier).
But every time I press enter it does signature checking... then it says FAILD (remote: 12 signature verify fail)
Any ideas?
Click to expand...
Click to collapse
Flash in recovery like the instructions say lol

BD619 said:
Flash in recovery like the instructions say lol
Click to expand...
Click to collapse
Ok, thank you again. I will try this. I hope to god it works

Sigh. Another problem
After performing the wipe with TWRP and then i type in the cmd adb push nameofrom.zip /sdcard/ but I get the following error in cmd.
adb server is out of date. killing...
* daemon started successfully *
I am confused by this because my drivers are up to date, unless this is a different problem. Any ideas?

kavinsky_ep said:
Sigh. Another problem
After performing the wipe with TWRP and then i type in the cmd adb push nameofrom.zip /sdcard/ but I get the following error in cmd.
adb server is out of date. killing...
* daemon started successfully *
I am confused by this because my drivers are up to date, unless this is a different problem. Any ideas?
Click to expand...
Click to collapse
It's normal for it to say that.
Do you get your serial number returned when you type
adb devices

BD619 said:
It's normal for it to say that.
Do you get your serial number returned when you type
adb devices
Click to expand...
Click to collapse
Hey! I fixed it, I was able to quickly put the radio.zip into my internal storage before the phone could freak out. Went into TWRP and flashed that *****! IT WORKS!
No more custom ROMS for me, I'll just stick to rooting and keeping stock rom.
I would like to thank you for helping me throughout this, I really appreciate this. :good:
btw, if I were unable to do it the way I did, how would I fix it to work with the adb push command?

kavinsky_ep said:
Hey! I fixed it, I was able to quickly put the radio.zip into my internal storage before the phone could freak out. Went into TWRP and flashed that *****! IT WORKS!
No more custom ROMS for me, I'll just stick to rooting and keeping stock rom.
I would like to thank you for helping me throughout this, I really appreciate this. :good:
btw, if I were unable to do it the way I did, how would I fix it to work with the adb push command?
Click to expand...
Click to collapse
Depends what is causing the adb to be wonky most likely it's a driver issue.
Drivers install while booted to OS,Recovery,and fastboot.
BTW when you were doing the adb push romname.zip /sdcard/ were you in recovery or OS?
You are very welcome btw

BD619 said:
Depends what is causing the adb to be wonky most likely it's a driver issue.
Drivers install while booted to OS,Recovery,and fastboot.
BTW when you were doing the adb push romname.zip /sdcard/ were you in recovery or OS?
You are very welcome btw
Click to expand...
Click to collapse
I was in my recovery, TWRP. and using my computer with the CMD. Or by OS do you mean my phone OS. Because I was unable to use my Phone due to the radio not being there.

kavinsky_ep said:
I was in my recovery, TWRP. and using my computer with the CMD. Or by OS do you mean my phone OS. Because I was unable to use my Phone due to the radio not being there.
Click to expand...
Click to collapse
Most likely the drivers were not installed properly while booted to twrp...there are instructions in my guide that will show you how to install them properly.
I was wondering if the phone was booted to OS.

Get yourself S-OFF, and many flashing woes disappear. I have soft-bricked my phone with a Viper myself. You have to be sure you install the correct carrier version and think twice about installing kernels in ViperHub (or whatever they call it). If you install a GSM anything to your Sprint phone, your radio will go away. An RUU will fix this though. Windows 8 does not play well with ADB on our phones, either.
Sent from my One using Tapatalk

I'm having the SAME exact problems as you. Went to flash Viper rom and just get stuck on the white screen with the HTC logo. Glad I'm not the only one!
Hopefully I'll be able to fix mine as well!