Hi,
I was running cyanogenmod 11 nightly and I was trying to flash the stock HTC sense ROM on my phone, but I think I wiped the system and there is no OS installed.
I am on hboot 1.57 and S-On. I have tried several RUUs, but they can't detect my phone.
Please Help!
Your thread has been moved to the Q&A section. Please do not create new threads in the Development section, unless it is development. Please look through the XDA rules, once you have resolution to your issue.
Thank you.
htghd said:
Hi,
I was running cyanogenmod 11 nightly and I was trying to flash the stock HTC sense ROM on my phone, but I think I wiped the system and there is no OS installed.
I am on hboot 1.57 and S-On. I have tried several RUUs, but they can't detect my phone.
Please Help!
Click to expand...
Click to collapse
is your bootloader locked or unlocked? if unlocked, do you have a custom recovery installed? if you can access fastboot and s-on, you're almost certainly not bricked.
also, out of curiosity, what is the error you get when running the RUU exe when it says you can't detect your phone?
Vember31 said:
is your bootloader locked or unlocked? if unlocked, do you have a custom recovery installed? if you can access fastboot and s-on, you're almost certainly not bricked.
also, out of curiosity, what is the error you get when running the RUU exe when it says you can't detect your phone?
Click to expand...
Click to collapse
I have an unlocked bootloader and TWRP installed, but it can't mount the system to flash a ROM.
I think I was getting error 170 USB connection error.
htghd said:
I have an unlocked bootloader and TWRP installed, but it can't mount the system to flash a ROM.
I think I was getting error 170 USB connection error.
Click to expand...
Click to collapse
I was also getting error 170 just yesterday that the RUU couldn't detect the phone. it was happening for me with the bootloader locked (and unlocked too for that matter). i don't have an answer for that yet.
As for the system mounting, I was having the same problem . I went into TWRP, went to Mount and mounted data. I'm not sure if that step mattered. I then went into Wipe/Advanced Wipe and wiped everything (except usb-otg), which I believe formatted system and data properly, but cache was still a problem. I then used "adb push" to push a ROM to internal storage and flashed it. At this point, everything was working except cache was still not able to mount. When I hit the wipe cache/dalvik button after flashing the ROM though it formatted cache properly (I had previously done fastboot format cache which made it unreadable). Basically, just wiping and flashing until I had it working again.
Let me know if this works for you too.
Thanks Vember31!
I'll try it tomorrow and i'll let you know if it works.
Hey Guys!
I was able to un-brick my phone with the correct version of the RUU. I don't know how I was able to fix the USB error, but my computer was able to recognize my phone. I am back on stock HTC Sense 6 with android 4.4.2 kit kat. I am going to put some sort of stock android ROM on it.
Are there any other ROMS other than cyanogenmod that you would recommend?
htghd said:
Hey Guys!
I was able to un-brick my phone with the correct version of the RUU. I don't know how I was able to fix the USB error, but my computer was able to recognize my phone. I am back on stock HTC Sense 6 with android 4.4.2 kit kat. I am going to put some sort of stock android ROM on it.
Are there any other ROMS other than cyanogenmod that you would recommend?
Click to expand...
Click to collapse
Which RUU did you use??
There are a handful of great AOSP roms out right now for m7spr. I'd check the Sprint HTC One Android Development threads. In terms of lollipop, we have CM12 (unofficial), liquid smooth, pac beta builds, unofficial aicp (new) and a couple of 5.0+ GE/Sense builds. There are no active roms in the Original Android Development threads at this time. I've tried all of the aosp builds and would say they're all comparable, though with some i've had "no sim card" issues
I used the Sprint HTC One M7 5.05.651.2 RUU
http://forums.androidcentral.com/ht...449708-ruu-sprint-htc-onem7-5-05-651-2-a.html
Hey Guys,
Here is a link to the latest 6.16.651.2 lollipop RUU for the Sprint HTC One M7
Related
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
mikhailov1 said:
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
Click to expand...
Click to collapse
try this http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
it worked for some users
Thanks. Will try when I get home. I was able to use my Win 7 computer at work to unlock the boot loader again, but I cannot get S Off. I ran rumrunner and it looked like it was working, but then said FATAL: download update. Is there no rumrunner for GPE?
Sent from my HTC One using Tapatalk
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Prash8429 said:
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Click to expand...
Click to collapse
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
mikhailov1 said:
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
Click to expand...
Click to collapse
you can still get OTA with a rooted phone, as long as you have stock recovery and flashed stock ruu.... tip if your having trouble with flashing ruu change the zip file name to something simple like ruu.zip worked for me.:good:
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Can you tell me if your bootloader was 1.54 or 1.55? I have been unable to get Windows 8.1 to recognize the 1.54 bootloader. It always says "device not recognized" If yours was 1.54.0000 I will try this fix. Thanks.
I am 1.54.
Sent from my Nexus 5 using Tapatalk
Thanks for this, helped me out alot
Sent from my HTC One using XDA Premium 4 mobile app
Hi, I was running the GPE Rom on my M7 and the 4.4 ROM became available OTA. I attempted to let it update but an error occured and now my device won't boot. Apparently there isn't a backup which I thought I had!
It's been a while since I did any of this stuff so need a bit of assistance.
What would be my first route as to getting my device up and running? I can get into ClockworkMod Recovery.
I'm guessing I have to use fastboot correct? Can I use Fastboot or ADB from within CWMR?
Rather than fire noob questions I'll await a response and go from there. Thanks in advance.
leecasey said:
Hi, I was running the GPE Rom on my M7 and the 4.4 ROM became available OTA. I attempted to let it update but an error occured and now my device won't boot. Apparently there isn't a backup which I thought I had!
It's been a while since I did any of this stuff so need a bit of assistance.
What would be my first route as to getting my device up and running? I can get into ClockworkMod Recovery.
I'm guessing I have to use fastboot correct? Can I use Fastboot or ADB from within CWMR?
Rather than fire noob questions I'll await a response and go from there. Thanks in advance.
Click to expand...
Click to collapse
stock GPE or custom rom?
you can use fastboot in bootloader
adb in cwm.
alray said:
stock GPE or custom rom?
you can use fastboot in bootloader
adb in cwm.
Click to expand...
Click to collapse
I believe it was the stock GPE (my HTC One was not a GPE just to clarify)
OK so I just pushed the MaximusHD rom to my device. Installed it but it continuously boots to recovery? Any ideas?
I'm downloading the stock ROM to hopefully at least get up and running again.
leecasey said:
I believe it was the stock GPE (my HTC One was not a GPE just to clarify)
OK so I just pushed the MaximusHD rom to my device. Installed it but it continuously boots to recovery? Any ideas?
I'm downloading the stock ROM to hopefully at least get up and running again.
Click to expand...
Click to collapse
did you:
Code:
fastboot erase cache
?
Hello guys Im having a problem with my vzw htc one and I know its my fault, I basically soft bricked the phone however it loads into currently installed rom (I had 3 and only one that would load) I have but reboots every few minutes with no access to the internal memory. I was trying to install Google play edition 4.4 kitkat however I forgot the radios are different for our phones and I installed the incorrect radio so now I am stuck only with the bootloader and CWM recovery but I cannot flash any files through fastboot because its apparently still locked (im getting the remote not allowed error) My phones is S off and rooted (I used rumrunner) . I have tried to mount usb storage in recovery with no luck and I have tried to flash a new rom and radio through boot loader but its locked and htc dev wont let you unlock our phones so im kinda stuck
If anyone has a solution to my problem I would really appreciate it I use my phone for a lot of stuff while deployed here in Afghanistan I use Roshan prepaid sim card works well.Thanks for any help and have a great day !
armyguy1989 said:
Hello guys Im having a problem with my vzw htc one and I know its my fault, I basically soft bricked the phone however it loads into currently installed rom (I had 3 and only one that would load) I have but reboots every few minutes with no access to the internal memory. I was trying to install Google play edition 4.4 kitkat however I forgot the radios are different for our phones and I installed the incorrect radio so now I am stuck only with the bootloader and CWM recovery but I cannot flash any files through fastboot because its apparently still locked (im getting the remote not allowed error) My phones is S off and rooted (I used rumrunner) . I have tried to mount usb storage in recovery with no luck and I have tried to flash a new rom and radio through boot loader but its locked and htc dev wont let you unlock our phones so im kinda stuck
If anyone has a solution to my problem I would really appreciate it I use my phone for a lot of stuff while deployed here in Afghanistan I use Roshan prepaid sim card works well.Thanks for any help and have a great day !
Click to expand...
Click to collapse
instructions to unlock are here ...you use revone (on hboot 1.44)
http://forum.xda-developers.com/showthread.php?t=2314582&nocache=1
Correction Below for hboot 1.54 use this >> http://forum.xda-developers.com/showthread.php?t=2470340
I also suggest update to TWRP if you want to flash the modern kit kat roms
http://techerrata.com/browse/twrp2/m7vzw
fastboot flash recovery openrecovery-twrp.img
fastboot erase cache
fastboot reboot-bootloader
clsA said:
instructions to unlock are here ...you use revone
http://forum.xda-developers.com/showthread.php?t=2314582&nocache=1
I also suggest update to TWRP if you want to flash the modern kit kat roms
http://techerrata.com/browse/twrp2/m7vzw
fastboot flash recovery openrecovery-twrp.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thank you so much clsA I will do this when I get off work im on a government computer, thanks again !
clsA said:
instructions to unlock are here ...you use revone
http://forum.xda-developers.com/showthread.php?t=2314582&nocache=1
I also suggest update to TWRP if you want to flash the modern kit kat roms
http://techerrata.com/browse/twrp2/m7vzw
fastboot flash recovery openrecovery-twrp.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
So revone will unlock my hboot ? Im already s-off but my problem is its saying it doesnt support hboot 1.54 and thats what I have
armyguy1989 said:
So revone will unlock my hboot ? Im already s-off but my problem is its saying it doesnt support hboot 1.54 and thats what I have
Click to expand...
Click to collapse
I think some functions like unlock still work. if not you'll have to flash a firmware to get back to 1.44 hboot
sorry try here >> http://forum.xda-developers.com/showthread.php?t=2470340
147
clsA said:
I think some functions like unlock still work. if not you'll have to flash a firmware to get back to 1.44 hboot
sorry try here >> http://forum.xda-developers.com/showthread.php?t=2470340
Click to expand...
Click to collapse
Im using my buddies laptop and 3g hotspot at work I just installed twrp it works fine I have the correct radio to load on my phone is there i way i can flash this new correct radio without unlocking the hboot ? Everything is erased but i still have carbon rom running so if i get the correct radio again i can just use the phone normally and install the rom using the computer. if that doesnt work can i use adb sideload or something in twrp recovery ? i tried to mount usb in twrp but still no go.
armyguy1989 said:
Im using my buddies laptop and 3g hotspot at work I just installed twrp it works fine I have the correct radio to load on my phone it has a boot img is there i way i can flash this new correct radio and a new rom without unlocking the hboot ? like using adb sideload or in twrp recovery ? i tried to mouunt usb in twrp but still no go.
Click to expand...
Click to collapse
you can download any flashable radio and replace the radio.img in the zip with yours and flash it in twrp.
here's one of mine >> http://www.androidfilehost.com/?fid=23501681358550122
Edit: and did you look at scotty's lock / unlock page ?
Also the Carbon rom could be part of your problem
try a normal Sense Rom - like http://forum.xda-developers.com/showthread.php?t=2693502
or
here>> http://forum.xda-developers.com/showthread.php?t=2485319
clsA said:
you can download any flashable radio and replace the radio.img in the zip with yours and flash it in twrp.
here's one of mine >> http://www.androidfilehost.com/?fid=23501681358550122
Edit: and did you look at scotty's lock / unlock page ?
Also the Carbon rom could be part of your problem
try a normal Sense Rom - like http://forum.xda-developers.com/showthread.php?t=2693502
or
here>> http://forum.xda-developers.com/showthread.php?t=2485319
Click to expand...
Click to collapse
I did see that and cool I will use yours. I guess I will try to unlock it in case this happens again but ill probably never mess with the radio again lol.
i wasnt using the carbon rom anymore i had 2 more roms on my sd card and when i flashed the incorrect radio the other two wouldnt even work. thescreen was black when it loaded. carbon rom is the only one that would load but it just reboots every few minutes i tried to copy the files on the sd card before it rebooted but wouldnt work
just out of curiousity how would i flash that with the bootloader locked. i really want to know incase something ever happens again. im still learning alot of this stuff lol
Im going to unlock the hboot real quick and see if that works. you should private message me your paypal im going to buy you dinner for all your help
btw this my current radio 4T.21.3218.21 im guessing it doesnt work with verizon htc one lol.
Never mind I found the donate button !
armyguy1989 said:
Never mind I found the donate button !
Click to expand...
Click to collapse
This is the newest Verizon radio
http://forum.xda-developers.com/devdb/project/dl/?id=6511
and in my dropbox as well >> https://www.dropbox.com/s/0yq7d3xnrni9hm3/Flashable-m7vzw_4.10.605.3_1.13.41.0421_Radio.zip
Thanks for the Dinner and Drink
clsA said:
This is the newest Verizon radio
http://forum.xda-developers.com/devdb/project/dl/?id=6511
and in my dropbox as well >> https://www.dropbox.com/s/0yq7d3xnrni9hm3/Flashable-m7vzw_4.10.605.3_1.13.41.0421_Radio.zip
Thanks for the Dinner and Drink
Click to expand...
Click to collapse
Well i feel like a dumbass right now unless its just a crazy stroke of luck. i had my usb plugged in to the ss 3.0 and when reading the instructions to setup up the adb it said to make sure you not using a 3.0 usb. so i switched and when i rebooted carbon rom becase it says i need usb debugging on but when i rebboted my internal sd popped up and i tried to move the files and it worked and then reboot lol. i went into recovery and flashed google play rom and its working however my Afghanistan roshan simcard isnt working now i set it back to global but no go. what radio should i flash now if yours works fine with verizon ill just use yours. which one should I use ?
armyguy1989 said:
Well i feel like a dumbass right now unless its just a crazy stroke of luck. i had my usb plugged in to the ss 3.0 and when reading the instructions to setup up the adb it said to make sure you not using a 3.0 usb. so i switched and when i rebooted carbon rom becase it says i need usb debugging on but when i rebboted my internal sd popped up and i tried to move the files and it worked and then reboot lol. i went into recovery and flashed google play rom and its working however my Afghanistan roshan simcard isnt working now i set it back to global but no go. what radio should i flash now if yours works fine with verizon ill just use yours. which one should I use ?
Click to expand...
Click to collapse
Did you set the APN setting on the new Rom ?
Setting/mobile data/access point name
Stick with the newest Verizon radio I posted above
No I havent done that yet i just installed your radio ill try that now.
Hi All,
I'm new here and I came here because of some verizon HTC One (M7, cid = vzw001) troubles.
Last year when I got the phone I was intent on making it like a Google play edition phone. I did rumrunner to get s-off and I unlocked the bootloader somehow (I don't remember) and rooted it. I tried flashing a GPE rom but being a noob, I flashed a GSM rom and it did not boot. In a frantic effort to make my phone usable I downloaded a deodexed verizon stock rom and flashed it, and thankfully it worked. I was able to get the Sense 5.5 OTA update after that. A little while later, I installed TWRP because I did not have a recovery at all. Now the Sense 6 update has been out for awhile now and I had tried updating to it but it would take me straight to TWRP and stop. Later on I read about how TWRP stops OTA updates so I installed a stock recovery. I also uninstalled root. Today I looked at my mom's HTC One, and I looked at her stats under Recovery Menu:
hboot: 1.57
radio: 1.13.41.0.421
OS: 4.10.605
I flashed a 1.13.41.0.421 radio and updated somehow the hboot got updated when tinkering and now all those specs match my Mom's, but it is obviously not the same OS. My phone from the settings says it is 4.4.2, 3.11.605.1.
What can I do to essentially return it to fresh out of the box state with restored ota capability? I want to be able to update normally like my Mom's phone and I don't care about root access. I'm not sending it in for warranty do I don't care about turning S-ON or dealing with tampered flags.
Also I'm sort of a noob. I only have a basic idea on how to use fastboot, so a step by step walkthrough would be helpful.
Thanks,
sugehtc
surgehtc said:
Hi All,
I'm new here and I came here because of some verizon HTC One (M7, cid = vzw001) troubles.
Last year when I got the phone I was intent on making it like a Google play edition phone. I did rumrunner to get s-off and I unlocked the bootloader somehow (I don't remember) and rooted it. I tried flashing a GPE rom but being a noob, I flashed a GSM rom and it did not boot. In a frantic effort to make my phone usable I downloaded a deodexed verizon stock rom and flashed it, and thankfully it worked. I was able to get the Sense 5.5 OTA update after that. A little while later, I installed TWRP because I did not have a recovery at all. Now the Sense 6 update has been out for awhile now and I had tried updating to it but it would take me straight to TWRP and stop. Later on I read about how TWRP stops OTA updates so I installed a stock recovery. I also uninstalled root. Today I looked at my mom's HTC One, and I looked at her stats under Recovery Menu:
hboot: 1.57
radio: 1.13.41.0.421
OS: 4.10.605
I flashed a 1.13.41.0.421 radio and updated somehow the hboot got updated when tinkering and now all those specs match my Mom's, but it is obviously not the same OS. My phone from the settings says it is 4.4.2, 3.11.605.1.
What can I do to essentially return it to fresh out of the box state with restored ota capability? I want to be able to update normally like my Mom's phone and I don't care about root access. I'm not sending it in for warranty do I don't care about turning S-ON or dealing with tampered flags.
Also I'm sort of a noob. I only have a basic idea on how to use fastboot, so a step by step walkthrough would be helpful.
Thanks,
sugehtc
Click to expand...
Click to collapse
Here is a step by step instructions for returning to stock. There is a Verizon HTC One Forum which has a ton of information much more than this forum. The Verizon phone is very different than the GSM version.
majmoz said:
Here is a step by step instructions for returning to stock. There is a Verizon HTC One Forum which has a ton of information much more than this forum. The Verizon phone is very different than the GSM version.
Click to expand...
Click to collapse
I read the thread but the link to the decrypted ruu was gone.
---------------------------------------------------------------------------------------------------------------------
I flashed a 1.44 hboot
and the did fastboot reboot-bootloader
it went to a bootloop and I cant use fastboot
When I plug in my phone to the computer
my phone never says fastboot usb
Windows also says "malfuctioning device"
When I press power on
It goes to boot loop
I can enter the recovery menu
I have no idea how to use adb.
I think I'm screwed.
surgehtc said:
I read the thread but the link to the decrypted ruu was gone.
---------------------------------------------------------------------------------------------------------------------
I flashed a 1.44 hboot
and the did fastboot reboot-bootloader
it went to a bootloop and I cant use fastboot
When I plug in my phone to the computer
my phone never says fastboot usb
Windows also says "malfuctioning device"
When I press power on
It goes to boot loop
I can enter the recovery menu
I have no idea how to use adb.
I think I'm screwed.
Click to expand...
Click to collapse
It looks like you got a corrupt hboot flash. I hope you got the hboot from the Verizon forum instead of this forum. This forum is geared to the GSM phones not the CDMA phones. You need to find a hboot for a Verizon phone in zip format to flash in recovery. The hboot controls the bootloader, so this could be the issue.
If you get that straighten out and you are able to use fastboot again, this post has a stock rom and firmware you can flash. Then you would have been back to stock. Spend time in the Verizon forum.
majmoz said:
It looks like you got a corrupt hboot flash. I hope you got the hboot from the Verizon forum instead of this forum. This forum is geared to the GSM phones not the CDMA phones. You need to find a hboot for a Verizon phone in zip format to flash in recovery. The hboot controls the bootloader, so this could be the issue.
If you get that straighten out and you are able to use fastboot again, this post has a stock rom and firmware you can flash. Then you would have been back to stock. Spend time in the Verizon forum.
Click to expand...
Click to collapse
I did get it from the verizon section.
But I have no custom recovery and no fastboot
I can't adb sideload either.
What should I do?
I have my Sprint HTC One m8 and I'd like to update to ViperOne ROM 3.1.0
I was using ViperOne 1.8.0, but to install the new version I need to get things back to stock so I can get all the OTA's up to the most recent update, and then flash the new ViperOne.
I've gotten this far and now I'm stuck...
Flashed Sprint_HTC_One_M8_1.54.651.8_RUU and now it boots into the stock no problem. Flashed the stock recovery here... http://forum.xda-developers.com/showthread.php?t=2736048 . When I start the phone it recognizes there is an update, but when it tries to install it, the process quits about a quarter of the way through, it gives off the red ! with triangle, then eventually reboots back into android. I feel like I'm missing a step here somewhere, not sure why the stock recovery doesnt work. I can flash back and forth from the stock recovery and twrp, and twrp works. I have access to fastboot if needed.
General specs of the phone as I believe they still are...
S-Off (htc unlock)
Rooted
1.54.651.8 Stock rom
hboot 3.16.00 (i flashed some mod a long time ago to hide the red development message you'd get)
Anything else you need?
Scrufdog said:
I have my Sprint HTC One m8 and I'd like to update to ViperOne ROM 3.1.0
I was using ViperOne 1.8.0, but to install the new version I need to get things back to stock so I can get all the OTA's up to the most recent update, and then flash the new ViperOne.
I've gotten this far and now I'm stuck...
Flashed Sprint_HTC_One_M8_1.54.651.8_RUU and now it boots into the stock no problem. Flashed the stock recovery here... http://forum.xda-developers.com/showthread.php?t=2736048 . When I start the phone it recognizes there is an update, but when it tries to install it, the process quits about a quarter of the way through, it gives off the red ! with triangle, then eventually reboots back into android. I feel like I'm missing a step here somewhere, not sure why the stock recovery doesnt work. I can flash back and forth from the stock recovery and twrp, and twrp works. I have access to fastboot if needed.
General specs of the phone as I believe they still are...
S-Off (htc unlock)
Rooted
1.54.651.8 Stock rom
hboot 3.16.00 (i flashed some mod a long time ago to hide the red development message you'd get)
Anything else you need?
Click to expand...
Click to collapse
delete the cache after flash stock recovery ? fastboot erase cache
dawexxl said:
delete the cache after flash stock recovery ? fastboot erase cache
Click to expand...
Click to collapse
did that, didnt help, but thx
does the phone have to be S-On with a locked bootloader to recieve OTAs?
Scrufdog said:
does the phone have to be S-On with a locked bootloader to recieve OTAs?
Click to expand...
Click to collapse
If you're S-off, no.
You might want to take a look at the thread in the link below. It pretty much covers what you have to do to take the OTA. Since you're S-off, why not install the firmware for the latest update and then flash a ROM based off the latest update? Much simpler than having to go through all the steps you're going through.
http://forum.xda-developers.com/showthread.php?t=2888993
yeah, i was trying to update via methods that were a couple weeks old, which of course are old.... lol
I installed the latest ROM from sprint, then install ViperOne on top of it, going through the install right now. Wifi is working so I guess the firmware updated correctly.
Thanks