I have a bricked HTC One. The phone boots into TWRP and boot loader. It appears to be flashed with 1.31.651.2 It has no OS installed.
From what I've read because there is no RUU setup.exe for this rom I am stuck at this rom. I cannot load any other roms from the sideload because they all fail verification. I have tried the .zip files of this update but each time it fails because its not encrypted.
If someone could please point me in the right direction it would be appreciated.
Thanks
ceralon said:
I have a bricked HTC One. The phone boots into TWRP and boot loader. It appears to be flashed with 1.31.651.2 It has no OS installed.
From what I've read because there is no RUU setup.exe for this rom I am stuck at this rom. I cannot load any other roms from the sideload because they all fail verification. I have tried the .zip files of this update but each time it fails because its not encrypted.
If someone could please point me in the right direction it would be appreciated.
Thanks
Click to expand...
Click to collapse
Odd, I had this same thing happen to me last night. My PC wouldn't recognize the phone in BL or TWRP so I was kinda freaking out. I put it aside and tried it on a different computer today and it was able to see it in both. I was able to sideload a ROM and all is well now. If you haven't tried a different computer, maybe a reboot of the PC would help.
erikivy said:
Odd, I had this same thing happen to me last night. My PC wouldn't recognize the phone in BL or TWRP so I was kinda freaking out. I put it aside and tried it on a different computer today and it was able to see it in both. I was able to sideload a ROM and all is well now. If you haven't tried a different computer, maybe a reboot of the PC would help.
Click to expand...
Click to collapse
I've tried on different computers. I can't get adb to work in the bootloader it doesn't show any devices listed when I do adb devices on either computer. I can fastboot etc. I'm stuck like chuck at the moment.
ceralon said:
I've tried on different computers. I can't get adb to work in the bootloader it doesn't show any devices listed when I do adb devices on either computer. I can fastboot etc. I'm stuck like chuck at the moment.
Click to expand...
Click to collapse
Are you S-OFF? I thought the RUU would work with S-OFF devices even if the firmwares didn't match up. I could be wrong on this as I was doing a little bit of panic-searching last night.
erikivy said:
Are you S-OFF? I thought the RUU would work with S-OFF devices even if the firmwares didn't match up. I could be wrong on this as I was doing a little bit of panic-searching last night.
Click to expand...
Click to collapse
It's not s-off... The guy who flashed it kinda killed it and im trying to rescue it.
ceralon said:
I have a bricked HTC One. The phone boots into TWRP and boot loader. It appears to be flashed with 1.31.651.2 It has no OS installed.
From what I've read because there is no RUU setup.exe for this rom I am stuck at this rom. I cannot load any other roms from the sideload because they all fail verification. I have tried the .zip files of this update but each time it fails because its not encrypted.
If someone could please point me in the right direction it would be appreciated.
Thanks
Click to expand...
Click to collapse
Did you try to flash a non Sprint rom?
bigdaddy619 said:
Did you try to flash a non Sprint rom?
Click to expand...
Click to collapse
I was able to flash Sprint_HTC_One_m7wls_1.29.651.7_encrypted_ROM.zip
I get the OS to load, but it reboots after being into the OS with no data / service.
So trying to get past that. I was able to do adb sideload from within recovery once I got the device to detect using different drivers.
What I meant did you try to install a non Sprint rom anytime in the past?
bigdaddy619 said:
What I meant did you try to install a non Sprint rom anytime in the past?
Click to expand...
Click to collapse
No clue... I got this phone as is ... it is all very well possible that the wrong rom was flashed. I am able to flash roms now, just the radio isnt working and the phone randomly reboots. I can't flash back using the RUU because its on 1.31.651.2
I got the phone yesterday and I'm trying to figure out how to repair / get working again as I bought it knowing it had issues.
ceralon said:
No clue... I got this phone as is ... it is all very well possible that the wrong rom was flashed. I am able to flash roms now, just the radio isnt working and the phone randomly reboots. I can't flash back using the RUU because its on 1.31.651.2
I got the phone yesterday and I'm trying to figure out how to repair / get working again as I bought it knowing it had issues.
Click to expand...
Click to collapse
There is a way to make the 1.29 RUU work
http://forum.xda-developers.com/showthread.php?t=2390821
bigdaddy619 said:
There is a way to make the 1.29 RUU work
http://forum.xda-developers.com/showthread.php?t=2390821
Click to expand...
Click to collapse
Ah yes.. saw that last night but couldn't figure out how to get adb to detect devices. I am trying now my only concern is it gave an error, but when I ran the RUU it did show the downgraded image....
C:\Users\stephen\Desktop\adt-bundle-windows-x86_64-20130911\sdk\platform-tools>a
db shell
~ # ←[6n
~ # ←[6n
~ # ←[6necho "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
warning: seek lseek64 failed
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.006592 seconds, 1.8KB/s
~ # ←[6nadb reboot bootloader
adb reboot bootloader
/sbin/sh: adb: not found
~ # ←[6n^C
C:\Users\stephen\Desktop\adt-bundle-windows-x86_64-20130911\sdk\platform-tools>a
db reboot bootloader
It says sending now... and its gone further than it has in the past...
EDIT
I am at the home screen wifi is working and so is data... So far all looks perfect. Thanks for your help!
Related
Im really frinking out my phone is stuck on Bootloader screen i root everything was good and for some stupid reason i decided to updated it to 4.3 and after i run it and it restart i just keep going back to bootloader screen try recovery but it will just got back to same screen when you plug into the computer it does detect ti just fine but i don't know what to do this is what is on my screen. i try RUU but is say i have the wrong version (31.1)
and the phone is like completely wipe out. some HELP ME PLEASE , I don't have insurance nor warranty and the phone is like 1 month old
Sprint HTC one
***tampered***
***Relocked***
M7_WIL PVT SHI P S-ON RH
HBOOT-1.44.0000
OpenDSP-v31.120.274.0617
eMMC-boot
Please help. Im in the same situtation
Same thing happened to me. PLS HELP
My phone is bricked and is stuck in a bootloop. When trying to unroot my device to get the new 4.3 update on my Sprint HTC One something went bad. I went to the twrp recovery and I accidentally swiped the system data. I’ve tried running the Sprint_HTC_One_m7wls_1.29.651.7_RUU but I get
Error: 140-------- S-ON is the problem is my guess
I also tried adb sideload, but whenever I try that the sideload gets stuck on 1%
Then tried flashing a stock ROM using USB-OTG in TWRP Sprint_HTC_One_1.31.651.2_Stock, it’ll come up with an unable to mount error. But I reformatted my flashdrive and it was able to actually flash the ROM, but the ROM just goes into a bootloop again.
Anything would be much obliged!!!!
I got mine fixed!!!
Followed Indirect's forum http://forum.xda-developers.com/showthread.php?t=2390821. Much love and thanks Indirect
blacky305 said:
Same thing happened to me. PLS HELP
My phone is bricked and is stuck in a bootloop. When trying to unroot my device to get the new 4.3 update on my Sprint HTC One something went bad. I went to the twrp recovery and I accidentally swiped the system data. I’ve tried running the Sprint_HTC_One_m7wls_1.29.651.7_RUU but I get
Error: 140-------- S-ON is the problem is my guess
I also tried adb sideload, but whenever I try that the sideload gets stuck on 1%
Then tried flashing a stock ROM using USB-OTG in TWRP Sprint_HTC_One_1.31.651.2_Stock, it’ll come up with an unable to mount error. But I reformatted my flashdrive and it was able to actually flash the ROM, but the ROM just goes into a bootloop again.
Anything would be much obliged!!!!
Click to expand...
Click to collapse
How did you resolve this, I am in the same boat.
when trying to ADB any image I get a signature verify fail error.
So far I haven't been able to send any image without getting that error.
I would be greatful for any help!
blacky305 said:
Followed Indirect's forum http://forum.xda-developers.com/showthread.php?t=2390821. Much love and thanks Indirect
Click to expand...
Click to collapse
i went there but tells me that i need to use ADB to do this
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
but i cant use ADB because it wont find my device and is probably bc debugging is not enable bu o cant enable it bc i can get out of bootloader is there a way e enable debugging from the bootloader??
Cubanflow2992 said:
i went there but tells me that i need to use ADB to do this
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
but i cant use ADB because it wont find my device and is probably bc debugging is not enable bu o cant enable it bc i can get out of bootloader is there a way e enable debugging from the bootloader??
Click to expand...
Click to collapse
in the same boat...
For me, it wouldn't find my device either for step 3"adb reboot bootloader", so I just rebooted through Twrp on phone. I'll explain my process a bit more below.
Cubanflow2992 said:
but i cant use ADB because it wont find my device and is probably bc debugging is not enable bu o cant enable it bc i can get out of bootloader is there a way e enable debugging from the bootloader??
Click to expand...
Click to collapse
When you restart your phone, like you would regularly, when it goes to a black screen you can use the top notification pull down thing to get into settings where you might me able to change the debugging.
---------- Post added at 03:46 AM ---------- Previous post was at 03:18 AM ----------
khigdon1 said:
How did you resolve this, I am in the same boat.
when trying to ADB any image I get a signature verify fail error.
So far I haven't been able to send any image without getting that error.
I would be greatful for any help!
Click to expand...
Click to collapse
I did a **** load of stuff to try to fix it, even let my roommate go at it for a day. Numerous things were done beforehand but I would often get the same error. The thing that did the trick was following Indirect's forum.
I had my phone unlocked, went in to recovery, the first two adb commands did some stuff. The third command I received an error however recognizing the command, I just rebooted the phone through the TWRP menu. I then went into fastboot where I relocked the phone. After locking the phone I ran Sprint_HTC_One_m7wls_1.29.651.7_RUU and my phone was fixed. Hopes this helps
Did you guy type exit after the echo command?
bigdaddy619 said:
Did you guy type exit after the echo command?
Click to expand...
Click to collapse
I closed out the window after the echo command. I later reopened a new command window to lock the phone in fastboot
blacky305 said:
For me, it wouldn't find my device either for step 3"adb reboot bootloader", so I just rebooted through Twrp on phone. I'll explain my process a bit more below.
When you restart your phone, like you would regularly, when it goes to a black screen you can use the top notification pull down thing to get into settings where you might me able to change the debugging.
is never goes to back screen when i turn my phone on like i would regularly it goes to the bootloader screen i select recovery and i goes to the TWRP ... i just bot a OTG USB cable and i place the custome rom the usb and plug ti into my phone but i will not load it
Click to expand...
Click to collapse
Otg cable must be a powered one.
Sent from my HTCONE using XDA Premium 4 mobile app
mrlakadaddy said:
Otg cable must be a powered one.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i got this one
eForCity Micro USB OTG to USB 2.0 Adapter compatible with Samsung© Galaxy S III / S3
Ok I tried everything I possibly could before posting for help. I installed SD v11.2 Ultimate and after installing I rebooted and my HTC One went into bootloader and its stuck there. I cant even get into recovery when I try it just goes back into bootloader. The only thing I have acces to is fastboot. ADB does not even work. I have tried factory reset and it does not work. I have tried reinstalling my recovery but I cant get past (remote access not allwed). Any time I use fast boot I get the remote access not allowed error, and every time I use the fastboot oem flash I get a (remote 32 header error).
I tired to flash a Sprint RUU and I get a Failed (remote:32 Header error). I have tried everything possible and nothing. Please help.
One thing I did notice on getvar all,is (version baseband is N/A)
My HTC One is
S-OFF
Super Cid
Rooted
Hmmm. So I saw that the ROM has Sprint support so my assumption is that while flashing it you chose the wrong phone model, not Sprint. This causes the partitions to go corrupt. You must use a RUU, follow this guide follow this guide http://forum.xda-developers.com/showthread.php?t=2460013 BUT instead of flashing the ruu posted there you need the latest ruu (cause you are on 4.3) http://forum.xda-developers.com/showthread.php?t=2508907
And BTW you should definitely get your CID back, it would have saved your ass from flashing the wrong model. SuperCID is used only in GSM variants to get faster updated, in our case it's useless
Sent from my HTCONE using Tapatalk
No luch...
elvisypi said:
Hmmm. So I saw that the ROM has Sprint support so my assumption is that while flashing it you chose the wrong phone model, not Sprint. This causes the partitions to go corrupt. You must use a RUU, follow this guide follow this guide http://forum.xda-developers.com/showthread.php?t=2460013 BUT instead of flashing the ruu posted there you need the latest ruu (cause you are on 4.3) http://forum.xda-developers.com/showthread.php?t=2508907
And BTW you should definitely get your CID back, it would have saved your ass from flashing the wrong model. SuperCID is used only in GSM variants to get faster updated, in our case it's useless
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Thanks for all your help elvisypi, I tried the above and nothing works. I cant seem to get my phone bootloader unlocked again, when I try I cant get passed remote access not allowed. I tried to flash OEM the RUU you tole me and I still get the remote 32 header error.
Is there a way to completly wipe out the phone and reinstall fresh?
arc209 said:
Thanks for all your help elvisypi, I tried the above and nothing works. I cant seem to get my phone bootloader unlocked again, when I try I cant get passed remote access not allowed. I tried to flash OEM the RUU you tole me and I still get the remote 32 header error.
Is there a way to completly wipe out the phone and reinstall fresh?
Click to expand...
Click to collapse
You clearly didn't read the thread. It doesn't state anywhere "unlock bootloader".
I'll quote it for you
Go to fastboot
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
You'll get an error. It's normal
Finally type exit
Than you can flash the ruu http://forum.xda-developers.com/showthread.php?t=2508907
Do exactly as I tell you.
Sent from my HTCONE using Tapatalk
Still stuck
elvisypi said:
You clearly didn't read the thread. It doesn't state anywhere "unlock bootloader".
I'll quote it for you
Go to fastboot
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
You'll get an error. It's normal
Finally type exit
Than you can flash the ruu http://forum.xda-developers.com/showthread.php?t=2508907
Do exactly as I tell you.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply agian elvisypi, but for some reason I may be doing this wrong when I type in adb shell it cant find the device. As of now my bootloader is locked.
elvisypi said:
You clearly didn't read the thread. It doesn't state anywhere "unlock bootloader".
I'll quote it for you
Go to fastboot
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
You'll get an error. It's normal
Finally type exit
Than you can flash the ruu http://forum.xda-developers.com/showthread.php?t=2508907
Do exactly as I tell you.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
well u tried, ha!!
arc209 said:
Thanks for the reply agian elvisypi, but for some reason I may be doing this wrong when I type in adb shell it cant find the device. As of now my bootloader is locked.
Click to expand...
Click to collapse
Than you have problems with your drivers or ADB folders.
First uninstall all the HTC drivers you have installed on your PC. Than install the "Naked driver" from here http://forum.xda-developers.com/showthread.php?t=2263822
Install tge android ADB from here http://forum.xda-developers.com/showthread.php?t=2263822
Than do the procedure I previously topd you
Sent from my HTCONE using Tapatalk
Ok, so I've been reading all the "Bricked" threads I could find but unfortunatly haven't been able to find one with a phone as bricked as mine...
At this moment I have no OS and when going into TWRP recovery ( thank god I have that ) I apparently also managed to wipe my entire phone memory.
When I go to "mount" it says: Internal storage (0mb)
I haven't been able to find an RUU for my S-On HTC One
I've been locking and unlocking my bootloader and tried every tip I could find but keep getting mount errors or signature errors
I've unistalled and installed all driver packs I could find
My computer does recognize my phone but I can't sideload
I really need help...:crying: or a new phone....
adb push romname.zip /sdcard/
Or the Sprint 3.04.651.2 can be found HERE
Nope...tried that...
=> I get "error: device not found" btw
When I do "c:\Anrdoid>fastboot devices" I do get "SH34FW900838 fastboot"
Elsitje said:
Nope...tried that...
Click to expand...
Click to collapse
You need to properly set up ADB to be able to sideload. Uninstall all the HTC stuff on your PC and install the driver from here http://forum.xda-developers.com/showthread.php?t=2513339
Sent from my HTCONE using Tapatalk
Elsitje said:
Nope...tried that...
Click to expand...
Click to collapse
The RUU will fix your problem
I haven't seen many true "bricked" threads, including this one.....flash a wrong or defective hboot & you'll see a true brick, lol
Ok, so I uninstalled everything, rebooted...downloaded the naked drivers, made sure my phone was visible again.
Then downloaded the RUU and it failed with a "132" signature error
MY PHONE WORKS AGAIN!!! WOOHOO!!!
How I did it?
I installed CWM recovery and suddenly couls sideload.
I then sideloaded the GURU RUU for my phone and voila!
Pfffff....that was the most horrible 20 hours EVER!
Elsitje said:
MY PHONE WORKS AGAIN!!! WOOHOO!!!
How I did it?
I installed CWM recovery and suddenly couls sideload.
I then sideloaded the GURU RUU for my phone and voila!
Pfffff....that was the most horrible 20 hours EVER!
Click to expand...
Click to collapse
Hey I am stuck on the same, would you be able to put in a noob instructions please?
Ok so how do I start this? Well I got an htc one for christmas and I wanted to root it. Everything was fine until I decided to flash a custom kit kat rom. The rom was stuck in a boot loop so I went back to twrp and flashed my recovery. I thought I fixed everything but then I stopped getting phone service. It kept saying looking for service. I thought it was a bad recovery so I downloaded cm from rom manager. While it was downloading, the phone just randomly rebooted. It kept doing this and still is.so then, being the idiot I am, flashed clockwork recovery to see if it would change anything. I tried downloading cm from rom manager again and finally finished downloading before it started rebooting again. I went into clockwork recovery and flashed cm and now it keeps rebooting and I have no phone service. I have no idea what to do. By switching from twrp to clockwork, I lost my recovery. Im totally screwed. I need help please!What do I do!!!!????
Run an RUU to fix and only flash roms that are made for Sprint or have Sprint support.
Sounds like you flashed a GSM rom that's why everything is jacked up.
BD619 said:
Run an RUU to fix and only flash roms that are made for Sprint or have Sprint support.
Sounds like you flashed a GSM rom that's why everything is jacked up.
Click to expand...
Click to collapse
Thanks a bunch! I'll check this out and see if it works
Rom Update Utility
It will get you back to 100% stock
If you need help PM me I'll be happy to help
roflcopter1212 said:
Ok so how do I start this? Well I got an htc one for christmas and I wanted to root it. Everything was fine until I decided to flash a custom kit kat rom. The rom was stuck in a boot loop so I went back to twrp and flashed my recovery. I thought I fixed everything but then I stopped getting phone service. It kept saying looking for service. I thought it was a bad recovery so I downloaded cm from rom manager. While it was downloading, the phone just randomly rebooted. It kept doing this and still is.so then, being the idiot I am, flashed clockwork recovery to see if it would change anything. I tried downloading cm from rom manager again and finally finished downloading before it started rebooting again. I went into clockwork recovery and flashed cm and now it keeps rebooting and I have no phone service. I have no idea what to do. By switching from twrp to clockwork, I lost my recovery. Im totally screwed. I need help please!What do I do!!!!????
Click to expand...
Click to collapse
Try this tutorial from BD619 http://forum.xda-developers.com/showthread.php?t=2503646&highlight=tutorial
roflcopter1212 said:
Thanks a bunch! I'll check this out and see if it works
Click to expand...
Click to collapse
I tried it with your tut. but when I try to reboot into RUU it says fastboot isnt a valid win. 32bit application. What now?
BD619 said:
Run an RUU to fix and only flash roms that are made for Sprint or have Sprint support.
Sounds like you flashed a GSM rom that's why everything is jacked up.
Click to expand...
Click to collapse
I put in the failed 90 hboot.... command and it says its an invalid command
roflcopter1212 said:
I put in the failed 90 hboot.... command and it says its an invalid command
Click to expand...
Click to collapse
You *have* to get your Android SDK setup properly. All the commands your run end up on "command not found" of "invalid exe" and that suggests a few things:
First -- make *sure* you install the correct SDK for your computer. If you can't find them, let us know what your computer is (32-bit, 64-bit, windows, etc.). Further, it seem possible:
1) You did not yet install the Android SDK (or ADT bundle if that's what you grab);
2) If just the SDK, you did not run the 'android' app and let it update all the platform-tools apps (that's adb, fastboot, etc);
3) You did not open a command shell in the <sdk>/platform-tools directory, or you did not add your <sdk>/tools and <sdk>/platform-tools to your path. Further:
Finally -- make sure you have your USB drivers loaded if you're using Windows.
Don't run 300 miles per hour trying to fix things -- it'll kill your phone. Relax, take a breath and get the SDK setup. That will solve most of your problems (if not all). At least that's what it looks like from afar.
Before you run any of the RUU, you should be able to type either of:
adb devices
or
fastboot devices
The latter works only when you are at the bootloader with your USB plugged in and you selected 'fastboot'; the former runs only when your phone is booted fully.
The Sprint 3.05.651.5 RUU is available here: http://www.htc.com/us/support/htc-one-sprint/news/ (Install at your own risk!)
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!