Related
I'm currently running ViperRom which is pretty nice, but I've been wanting to flash a modified kernel. I need to update radio before flashing a new kernel tho. And I think I need S-Off in order to update radio. I also read new recovery is needed for new firmware, but not sure if I need new firmware. If I need new firmware, should I use full firmware or w/o hboot, boot, recovery?
I don't fully understand the purpose of each part, so not sure what order to update things in. My plan is to do the following in order: S-Off first with firewater, update firmware (not sure which one tho), then update radio, then recovery, then kernel. Should that work?
zaner123 said:
I'm currently running ViperRom which is pretty nice, but I've been wanting to flash a modified kernel. I need to update radio before flashing a new kernel tho. And I think I need S-Off in order to update radio. I also read new recovery is needed for new firmware, but not sure if I need new firmware. If I need new firmware, should I use full firmware or w/o hboot, boot, recovery?
I don't fully understand the purpose of each part, so not sure what order to update things in. My plan is to do the following in order: S-Off first with firewater, update firmware (not sure which one tho), then update radio, then recovery, then kernel. Should that work?
Click to expand...
Click to collapse
That should work (same procedure as you described worked for me)
I used the firmware.zip from this thread (the modified one, with removed hboot etc.): http://forum.xda-developers.com/showpost.php?p=53007098&postcount=2
and the latest radio from here: http://forum.xda-developers.com/showpost.php?p=44634436&postcount=1
I was able to S-Off fairly easily, but having issues updating firmware now. Getting a "Device Failed Enumeration" error since I'm on ****ty Windows 8.1. No USB 3.0 so no easy solutions.
Is there any benefit to installing updated firmware? Can I just skip that and install radio/kernel/etc?
zaner123 said:
I was able to S-Off fairly easily, but having issues updating firmware now. Getting a "Device Failed Enumeration" error since I'm on ****ty Windows 8.1. No USB 3.0 so no easy solutions.
Is there any benefit to installing updated firmware? Can I just skip that and install radio/kernel/etc?
Click to expand...
Click to collapse
Try looking at this thread: http://forum.xda-developers.com/showthread.php?t=2646453 and if that doesn't work then try borrowing a windows 7 PC.
I found a Windows 7 PC to use, so now I can use fastboot fine. Now I'm running into new issue:
After performing "fastboot rebootRUU" I try command "fastboot flash zip firmware.zip" and I get error "error: cannot open 'firmware.zip' "
The command window is open from within the folder containing ADB/fastboot/firmware.zip so I cannot figure out what the problem is.
zaner123 said:
I found a Windows 7 PC to use, so now I can use fastboot fine. Now I'm running into new issue:
After performing "fastboot rebootRUU" I try command "fastboot flash zip firmware.zip" and I get error "error: cannot open 'firmware.zip' "
The command window is open from within the folder containing ADB/fastboot/firmware.zip so I cannot figure out what the problem is.
Click to expand...
Click to collapse
Make sure it named firmware.zip and not .zip.zip
BD619 said:
Make sure it named firmware.zip and not .zip.zip
Click to expand...
Click to collapse
That was the problem! Finally got it to work.
zaner123 said:
That was the problem! Finally got it to work.
Click to expand...
Click to collapse
Cool enjoy
Please read and understand the guide and accompanying links in their entirety before beginning.XDA and I am not responsible for anything you do to your phone.
This guide should work for anyone trying to RUU their phone, but let me give you my background on this first.
While trying to run an RUU to reset my phone, I kept running into an issue: "htc_fastboot.exe has stopped working". I could get my phone to restart, but the RUU would not run successfully. I searched this site and the internet for an answer, but could not find anything that worked for me. Also, a lot of people in Q&A tend to have issues getting the RUU to work. That's why I'm writing this guide. Hopefully someone who is having trouble will search and stumble across it. I tried everything I could find - Windows 7, 8.1, different RUUs, etc and this is how I finally fixed it. I am s-off by the way and did this in Windows 8.1 Update so the guide is written from that perspective.
Steps:
1. Make sure that your computer can see your phone when you boot into fastboot. It should say Fastboot in red that changes to Fastboot USB when plugged into your computer. There are guides that help with this, so I'm not going to go into much detail. Basically you install HTC Sync to your computer and then uninstall it but leave the drivers.
2. Get a copy of fastboot and ADB. The easiest way is to get the SDK from Google (tools only) as it also includes drivers, but you can get just fastboot and adb from here (I did not use this tool personally).
3. To verify that your phone and computer are talking, open a command prompt window (I always open as administrator) and go to the folder that contains fastboot. Type "fastboot devices" (no quotes) and it should list your phone. If it does not, something did not work right with steps 1 and 2.
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes).
5. Download the Full Firmware from RUU here. While you're there, get the RUU as well. Make sure to get the one that is not decrypted (first link). Copy both into the folder with fastboot.
6. Flash the firmware file using fastboot following the directions in the OP from where you got it. To summarize, rename the firmware zip file to firmware.zip. Then at a command prompt, type "fastboot oem rebootRUU". When the phone shows a black screen that says HTC, type "fastboot flash zip firmware.zip". The command prompt window will show a bunch of stuff as it does its thing. When you get back to the command prompt, it's finished. At this point, type "fastboot reboot-bootloader" to restart back into the (hopefully now stock) bootloader. Personally, I had to repeat the last command again because it failed the first time.
7. At this point, you should be in the stock hboot. It should say fastboot USB in red. Now time to RUU.
8. The current RUU is an exe so run the RUU you download before (if you have a zip file, unzip the RUU and run ARUWizard.exe). I personally ran it as an administrator just to make sure limited privileges didn't cause an issue. Read each screen and keep clicking next. Eventually it will do its thing. It takes about ten minutes and sometimes seems to be frozen. Have patience grasshopper.
And that's it. I'm now running pure stock (not for long I'm sure), still s-off. If you are s-on, you will have to unlock your bootloader again.
Good luck!
I'll be the first to troll post in this guide
Nice work brother.
I've noticed the newer RUU's (M7 and M8) require you to have the matching hboot to run correctly even if your device is s-off.
I didn't know what it meant in step 8 to "unzip the RUU" since my RUU was an EXE file that could not be unzipped. After step 7, I just ran the RUU executable and it ran as expected. I was able to run everything else just like the steps say, but for step 8 I just ran the RUU executable I had downloaded for my Sprint HTC One.
Thanks for the guide!
kushanson said:
I didn't know what it meant in step 8 to "unzip the RUU" since my RUU was an EXE file that could not be unzipped. After step 7, I just ran the RUU executable and it ran as expected. I was able to run everything else just like the steps say, but for step 8 I just ran the RUU executable I had downloaded for my Sprint HTC One.
Thanks for the guide!
Click to expand...
Click to collapse
You're welcome. Glad it helped. Also, thank you for the heads up about the RUU being an exe now. It was a zip file when I wrote the guide. I've fixed the guide to reflect the change.
Dude...
I was soft bricked for about an hour until I found this. It seems fairly obvious to me now, but for some reason I had thought that only flashing the full_firmware zip in fastboot would suffice. I guess the tiny file size (80MB unzipped???) should have tipped me off.
Regardless, I'm back up and running. Thanks, coal.
i am getting error bootloader signature failed how to fix please
rajnshubham said:
i am getting error bootloader signature failed how to fix please
Click to expand...
Click to collapse
I'm guessing you are s-on. If so, you cannot flash the firmware file (I'm s-off and wrote the guide from that perspective). You most likely can just skip that step and run the ruu.exe.
coal686 said:
This guide should work for anyone trying to RUU their phone, but let me give you my background on this first.
Good luck!
Click to expand...
Click to collapse
Thanks for your guided I was able to fix an old One that I had laying around, thanks again
coal686 said:
I'm guessing you are s-on. If so, you cannot flash the firmware file (I'm s-off and wrote the guide from that perspective). You most likely can just skip that step and run the ruu.exe.
Click to expand...
Click to collapse
i think the problem was due to same hboot error. i get to know this thing few days back. anyway thanks coal686. now i updated with the ruu having hboot 1.56 and now i m on kitkat 4.4.2 stock. i can update now to higher ones. thanks buddy
I want to make sure I understand something in the steps. I know the first step is to fastboot the full firmware ruu but then comes something I'm not sure about. Do I follow that up with the. exe file?
I am s-off with 1.60.
Sent from my HTCONE using XDA Free mobile app
biker57 said:
I want to make sure I understand something in the steps. I know the first step is to fastboot the full firmware ruu but then comes something I'm not sure about. Do I follow that up with the. exe file?
I am s-off with 1.60.
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for using my guide!
The first step is to flash the "full firmware from RUU" (it's actually labelled that way in the OP of the linked post). It's only the firmware, not the full RUU. Then, follow that up with the .exe file which is the entire RUU. For some reason, the RUU wouldn't run for me without flashing the firmware first.
Since you are already on hboot 1.6, you probably don't have to flash the firmware first, but I'd do it just to be safe.
I normally think of a. exe file as executable. Is this something I can run or need to fastboot?
Sent from my HTCONE using XDA Free mobile app
biker57 said:
I normally think of a. exe file as executable. Is this something I can run or need to fastboot?
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Just run it. Fastboot flash the firmware then just run the RUU exe.
Just wanted to report that I had the same problem with htc_fastboot.exe stopped working error and I was stuck on 3.22.1540.1 JB and there was no way on upgrading my software because OTAs would download but I would get a red mark when installing. So I skkipped most of your steps because I was not rooted or unlocked, I was all stock but reflashed the same software I was on, 3.22.1540.1 zip and did it twice since first time I got FAILED message in ADB. Once my phone restarted I tried flashing a newer RUU and still got htc_fastboot.exe error on KK and LP RUUs so just for luck tried downloading OTA from the phone but this time it DID install. So I upgraded to 4.15.1540.9 and currently downloading 4.19.1540.4. Hopefully everything goes right and I can get LP running on my phone.
cowboysgz said:
Just wanted to report that I had the same problem with htc_fastboot.exe stopped working error and I was stuck on 3.22.1540.1 JB and there was no way on upgrading my software because OTAs would download but I would get a red mark when installing. So I skkipped most of your steps because I was not rooted or unlocked, I was all stock but reflashed the same software I was on, 3.22.1540.1 zip and did it twice since first time I got FAILED message in ADB. Once my phone restarted I tried flashing a newer RUU and still got htc_fastboot.exe error on KK and LP RUUs so just for luck tried downloading OTA from the phone but this time it DID install. So I upgraded to 4.15.1540.9 and currently downloading 4.19.1540.4. Hopefully everything goes right and I can get LP running on my phone.
Click to expand...
Click to collapse
.
Thanks
Device not recognized
Whenever I plug in my device and go to fastboot, my computer tells me "USB Device not recognized". I've installed the drivers from HTC, I even went to Decide manager on my PC to see if the device appears at all. It shows on the top under "Android USB Device" and it's labeled "My HTC" but it has the error symbol on it, so o deviced to unistall the driver and install it manually. It said that I already had the correct driver.
The reason I'm trying to do all this is, back in 2013 I had put Viper ROM on my device, it worked great, I also installed cyanogen mod as well and that worked great, at the time I wanted to have the double tap to wake feature, so I installed a custom Kernel to allow that. When I had booted up my phone the HTC logo didn t go away, then the lock screen showed up, I unlocked my phone, the HTC logo was still there, then my home screen finally opened and some apps wouldn't open. Then it would restart, so I rebooted it and it would do the same thing, turn on, show the HTC, start then restart. I could go into recovery fine, Install updated version of rom, and the same problem persists
Is there any reason the RUU exe file would stop working only two screens in? I basically run it, accept the terms, click next... then nothing....... what SHOULD it be doing? Best, Rich
krakora said:
Is there any reason the RUU exe file would stop working only two screens in? I basically run it, accept the terms, click next... then nothing....... what SHOULD it be doing? Best, Rich
Click to expand...
Click to collapse
I meant to add this to my guide and didn't get around to it. You're missing a Visual C++ 2008 runtime. See this thread:
https://forum.xda-developers.com/sprint-htc-one/help/solved-ruu-starts-disappears-accepting-t3224469
coal686 said:
I meant to add this to my guide and didn't get around to it. You're missing a Visual C++ 2008 runtime. See this thread:
https://forum.xda-developers.com/sprint-htc-one/help/solved-ruu-starts-disappears-accepting-t3224469
Click to expand...
Click to collapse
Thanks so much Coal, that absolutely worked. The RUU exe runs for me, but getting 155 unknown error. Evidently its not the right RUU for my device. My bootloader is "relocked" already, S-on. So confusing. When I was following the directions on the guide, when flashing the firmware, I was getting the 12 missing signatures error also, I'm assuming its not reading it as an HTC signed firmware. Any ideas on my next direction? Best, Rich
Hi.
I should start by saying that I am completely new to rooting phones. I think it's fair to say that I am in over my head!
I am attempting to return my HTC One M7 back to stock. I have relocked to bootloader but am unable to find a RRU that is compatible with my device. I basically want my phone as it was (able to receive official OTA's etc). My phone is S-on and hasnt been S-off. I'm not confident enough to go S-off.
My phones details are shown in the attached photo. My CID is ORANG001 (UK EE).
I have been through the extensive list but none are compatible with my device.
Any assistance offered would be appreciated. Remember - speak slowly!
Thanks.
IchiKiriyama said:
Hi.
I should start by saying that I am completely new to rooting phones. I think it's fair to say that I am in over my head!
I am attempting to return my HTC One M7 back to stock. I have relocked to bootloader but am unable to find a RRU that is compatible with my device. I basically want my phone as it was (able to receive official OTA's etc). My phone is S-on and hasnt been S-off. I'm not confident enough to go S-off.
My phones details are shown in the attached photo. My CID is ORANG001 (UK EE).
I have been through the extensive list but none are compatible with my device.
Any assistance offered would be appreciated. Remember - speak slowly!
Thanks.
Click to expand...
Click to collapse
Restore you stock backup .. their is no files available for your phone
Thanks.
How would I go about that?
IchiKiriyama said:
Thanks.
How would I go about that?
Click to expand...
Click to collapse
do you have custom recovery ?
IchiKiriyama said:
Thanks.
How would I go about that?
Click to expand...
Click to collapse
just on a side note, please tell us you DIDNT re-lock your bootloader with a cutom recovery on your phone like TWRP or CWM ?
sorry to butt in @clsA just had to ask as I wouldnt know what to do for him if there is no files availble.
I had attempted to install a custom rom but the installation failed and it factory reset my phone. Basically, I appear to be using my stock RUU but ota is appears to be disabled. I attempted to install this rom, followed these instructions: http://forum.xda-developers.com/showthread.php?t=2189373
IchiKiriyama said:
I had attempted to install a custom rom but the installation failed and it factory reset my phone. Basically, I appear to be using my stock RUU but ota is appears to be disabled. I attempted to install this rom, followed these instructions: http://forum.xda-developers.com/showthread.php?t=2189373
Click to expand...
Click to collapse
Ok that's fine
you need to unlock the bootloader now at htcdev.com so you can flash the correct recovery to you phone
download TWRP 2.8.5.0 here > http://techerrata.com/browse/twrp2/m7
flash it
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
enter recovery and copy your rom to your phone again and install it again
no need to wipe again / theirs no RUU for your phone so no need to relock the bootloader any more
Very helpful. Thanks.
I'm sorry to cause further frustration, but could you give me simpler instructions? I don't want to make my situation any worse!
As I said above, I'm in way over my head.
IchiKiriyama said:
Very helpful. Thanks.
I'm sorry to cause further frustration, but could you give me simpler instructions? I don't want to make my situation any worse!
As I said above, I'm in way over my head.
Click to expand...
Click to collapse
Humm that's as simple as it gets
go to http://www.htcdev.com/bootloader
follow the instructions to unlock the bootloader
when it's done download TWRP 2.8.5.0 and Flash it same as you did the unlock token above, in a command prompt from the folder with fastboot in it.
when you get to the TWRP recovery screen copy your rom to the phones storage and then click install it in TWRP
choose your file you just copied and let it install
the first reboot to lollipop will take a long time ...be patient
actually your not on 7.x firmware .. you need to flash an older rom
Use this one >> https://www.androidfilehost.com/?w=files&flid=22071
it matches your firmware better
Thanks. And that'll return my phone to stock?
I have been running this rom for quite some time and I wanted to know the procedures while being s on to upgrade the entire phone. I'm also enclosing a screenshot of my current firmware and ROM. Any help would be greatly appreciated I haven't done this since I first got my m8
Download the most recent RUU from the thread linked below to your computer:
http://forum.xda-developers.com/showthread.php?t=2729173
Make sure your phone has a full charge. Reboot your device to the bootloader and connect your phone and computer via USB cable. Select the fastboot option from the menu and you should show that you're connected via fastboot USB mode. Open up a command window with ADB and type the command "fastboot oem lock". Press enter. This command will re-lock your boot loader. Now, double-click the RUU file you downloaded to start the installer. Be patient, as it may take a few minutes for the installer to start. Once it starts, follow the prompts on your computer screen. Once the RUU completes you can disconnect your phone from your computer and reboot your phone. The RUU will wipe the internal storage on your phone, so make a back-up and store it on your computer or your external SD card, if applicable.
Can i unlock the bootloader again after doing all this by typing fastboot oem unlock in adb?
I just wanna make sure I update everything correctly and get set up for a new Rom. I'm not getting all my calls or texts. So I am guessing the radio is too outdated
Is there a way to just get an image that will bring my phone back to stock so I can upgrade everything all at once
honorlost84 said:
Is there a way to just get an image that will bring my phone back to stock so I can upgrade everything all at once
Click to expand...
Click to collapse
RUU
Alright and that won't screw up the recovery I have installed correct so I can just flash a new rom even with a locked bootloader or do I have to go through all the stupid steps to unlock it again
honorlost84 said:
Alright and that won't screw up the recovery I have installed correct so I can just flash a new rom even with a locked bootloader or do I have to go through all the stupid steps to unlock it again
Click to expand...
Click to collapse
The stock recovery will be installed. Additionally, you'll need to use HTC Dev to unlock your phone again. That's the best way to update being S-on.
So there's no way to just update the firmware and radio without having to go through the rest of that?
Actually I just looked up how to get s off on my phone I'm going to use the fire water tool and then I'll use that link to get the firmware and flash that with the fuu
honorlost84 said:
So there's no way to just update the firmware and radio without having to go through the rest of that?
Click to expand...
Click to collapse
Without being S-off, no.
honorlost84 said:
Actually I just looked up how to get s off on my phone I'm going to use the fire water tool and then I'll use that link to get the firmware and flash that with the fuu
Click to expand...
Click to collapse
Firewater has been discontinued. You have to use the Sunshine exploit for S-off.
Got a link?
honorlost84 said:
Got a link?
Click to expand...
Click to collapse
Sunshine
Sloth you deserve some Rocky road buddy
And this is what I get. I suppose nothing is simple. I got no clue what is wrong.
Kernel info
Flash a stock rooted ROM from the RUU thread I mentioned previously, then try it again.
I locked boot. Ran a ruu from boot and destroyed my os and it took me all night to recover. Can you please show me how to restore to stock? I'm kinda over it
Now that you've run the RUU, go ahead and run the Sunshine exploit. Afterwards you can go about installing recovery and flashing a new ROM, if you'd like.
Not paying 25 bucks. I'm just wanting stock. My phone got too close to getting the hammer. I'm just gonna go stock. Don't know how
Huge amount of frustration with trying to deal with my phone
I soft bricked my HTC One M8 HK not too long ago, and had left it sitting in the dust for a while as I had no options of fixing it because I wiped the memory on accident (how I did, I don't know. Guess I'm dumb. That's not the point though). It's been sitting on my dresser for about 2 months being unused as I had no microSD cards in hand. All it had was an unlocked bootloader and working TWRP.
As of right now, I've tried to install 4 ROMs. All 4 did not work. I followed the instructions and unlocked my bootloader and did all other essential things. I installed ViperOneM8 before being ignorant that my WiFi wouldn't work. It was the only ROM I installed that actually booted properly. The only issue was that I had no WiFi. Had it worked, I wouldn't be making this thread. Then I got Android Revolution HD, installed it and it installed properly. I booted it into system, and it brought me to bootloader. This was the same issue I had while trying to install my first ROM, and still happens. Then I got CyanogenMod, and it didn't even install. TWRP told me it failed right off the bat. Same thing with whenever I tried to install a stock firmware recovery of the variant I have, HK Sprint.
Right now, I'm getting the 4.2.5 HK RUU in hopes that it works. I tried it previously, and it was a literal waste of time. I've been here for 5 hours trying different ROMs and to no success. I was very faithful I would get to use my phone again, although unless this RUU actually works, I don't have a lot of positive faith for my phone.
Are there any fixes for getting something like CyanogenMod to work? I actually really wanted this ROM after I remembered it, and was quite let down after it failed to work. Also, is there anything I should do with the phone before I go farther with anything?
Thanks for any help you all can give, I would greatly appreciate it. Sucks not having a phone, so I'll take any help I can get. Thanks once again!
EDIT: The RUU did not work. It failed to update. Waiting for answers I guess..
F0rZ3r0 said:
I soft bricked my HTC One M8 HK not too long ago, and had left it sitting in the dust for a while as I had no options of fixing it because I wiped the memory on accident (how I did, I don't know. Guess I'm dumb. That's not the point though). It's been sitting on my dresser for about 2 months being unused as I had no microSD cards in hand. All it had was an unlocked bootloader and working TWRP.
As of right now, I've tried to install 4 ROMs. All 4 did not work. I followed the instructions and unlocked my bootloader and did all other essential things. I installed ViperOneM8 before being ignorant that my WiFi wouldn't work. It was the only ROM I installed that actually booted properly. The only issue was that I had no WiFi. Had it worked, I wouldn't be making this thread. Then I got Android Revolution HD, installed it and it installed properly. I booted it into system, and it brought me to bootloader. This was the same issue I had while trying to install my first ROM, and still happens. Then I got CyanogenMod, and it didn't even install. TWRP told me it failed right off the bat. Same thing with whenever I tried to install a stock firmware recovery of the variant I have, HK Sprint.
Right now, I'm getting the 4.2.5 HK RUU in hopes that it works. I tried it previously, and it was a literal waste of time. I've been here for 5 hours trying different ROMs and to no success. I was very faithful I would get to use my phone again, although unless this RUU actually works, I don't have a lot of positive faith for my phone.
Are there any fixes for getting something like CyanogenMod to work? I actually really wanted this ROM after I remembered it, and was quite let down after it failed to work. Also, is there anything I should do with the phone before I go farther with anything?
Thanks for any help you all can give, I would greatly appreciate it. Sucks not having a phone, so I'll take any help I can get. Thanks once again!
EDIT: The RUU did not work. It failed to update. Waiting for answers I guess..
Click to expand...
Click to collapse
Flashing RUU requires locked bootloader.
Alright, I'm seriously about to just throw this thing in the dumpster. I've been here another 2 hours trying to get Cyanogen to work, and I figured out the issue with it. The updater script file wasn't accepting m8_whl. I'm still unaware how in the Mod Edit I'm supposed to put m8_whl into the script for it to be accepted.
To be more specific, the actual updater script has m8whl, while my phone recognizes as m8_whl. It denies it.
I thought I put it into the script correctly, although it is not accepting it. I found a quote not saying the location, and I assumed in the latest release of Cyanogen 12 for M8s, it was in /META-INF/google/android/updater-script
Please, someone help me before I have an anger episode. This thing has literally wasted my whole Mod Edit day.
F0rZ3r0 said:
Alright, I'm seriously about to just throw this thing in the dumpster. I've been here another 2 hours trying to get Cyanogen to work, and I figured out the issue with it. The updater script file wasn't accepting m8_whl. I'm still unaware how in the Mod Edit I'm supposed to put m8_whl into the script for it to be accepted.
To be more specific, the actual updater script has m8whl, while my phone recognizes as m8_whl. It denies it.
I thought I put it into the script correctly, although it is not accepting it. I found a quote not saying the location, and I assumed in the latest release of Cyanogen 12 for M8s, it was in /META-INF/google/android/updater-script
Please, someone help me before I have an anger episode. This thing has literally wasted my whole Mod Edit day.
Click to expand...
Click to collapse
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
dopy25 said:
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
Click to expand...
Click to collapse
Alright, doing this now. I'm a lot calmer today, so I can do this.
dopy25 said:
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
Click to expand...
Click to collapse
Didn't work, the RUU gave me the same error as last time, it tells me its the wrong RUU. Got both the stock RUUs just to see if I got it wrong about HK, both failed. Please help...
F0rZ3r0 said:
Didn't work, the RUU gave me the same error as last time, it tells me its the wrong RUU. Got both the stock RUUs just to see if I got it wrong about HK, both failed. Please help...
Click to expand...
Click to collapse
[Mod hat on] I know it can be frustrating at times but please take it easy with the swearing. [/Mod hat off]
You might try flashing the Full firmware that matches the RUU that you are trying to flash, the past couple updates require hboots to match on both your device and the RUU or you will get an error.
Sloth said:
[Mod hat on] I know it can be frustrating at times but please take it easy with the swearing. [/Mod hat off]
You might try flashing the Full firmware that matches the RUU that you are trying to flash, the past couple updates require hboots to match on both your device and the RUU or you will get an error.
Click to expand...
Click to collapse
My apologies for the swearing, was angry at the time.
Also, my hboot version seems to be 3.18. Not sure what to do in order to be able to flash firmware. My OS version seems to be 2.16.651.4 as well if that helps.
What would I have to do in order to install a ROM and how?
If you are not flashing the full firmware to begin with, that's the issue. From your OP it looks like you only have an unlocked BL and had TWRP.
You must relock the BL and then run the full RUU, you can get it in the thread here, or get it from HTC. Either way you need the full one, it flashes the FW and Software as well as bootloader and radios.
HTC: http://dl3.htc.com.s3.amazonaws.com..._NV_SPCS_1.52_003_release_446220_signed_2.exe
Thread with all and modified FW
http://forum.xda-developers.com/showthread.php?t=2729173
Are you S-Off or On? If you are running the *.651* then that's the non HK version. It's ok if you flashed a modified stock, but if you got that from an RUU, that would be what the issue is. I think
dopy25 said:
If you are not flashing the full firmware to begin with, that's the issue. From your OP it looks like you only have an unlocked BL and had TWRP.
You must relock the BL and then run the full RUU, you can get it in the thread here, or get it from HTC. Either way you need the full one, it flashes the FW and Software as well as bootloader and radios.
HTC: http://dl3.htc.com.s3.amazonaws.com..._NV_SPCS_1.52_003_release_446220_signed_2.exe
Thread with all and modified FW
http://forum.xda-developers.com/showthread.php?t=2729173
Are you S-Off or On? If you are running the *.651* then that's the non HK version. It's ok if you flashed a modified stock, but if you got that from an RUU, that would be what the issue is. I think
Click to expand...
Click to collapse
I believe I'm S-OFF.
F0rZ3r0 said:
I believe I'm S-OFF.
Click to expand...
Click to collapse
look in bootloader it will tell you if you are s-off or s-on.
Sloth said:
look in bootloader it will tell you if you are s-off or s-on.
Click to expand...
Click to collapse
Never mind, S-ON.
F0rZ3r0 said:
Never mind, S-ON.
Click to expand...
Click to collapse
Ok re-lock your bootloader if you have not already.
Flash this for Non HK 4.25.651.18 Full Firmware
Flash this for HK 4.25.654.18 Full Firmware
Instructions:
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Once done flash the latest Non HK or HK RUU found here... http://forum.xda-developers.com/showthread.php?t=2729173
Then unlock your bootloader again using the unlock code you got from HTC.
Re-flash the latest TWRP found here... https://dl.twrp.me/m8/
This will give you a fresh start then you can try to flash the rom you want.
Sloth said:
Ok re-lock your bootloader if you have not already.
Flash this for Non HK 4.25.651.18 Full Firmware
Flash this for HK 4.25.654.18 Full Firmware
Instructions:
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Once done flash the latest Non HK or HK RUU found here... http://forum.xda-developers.com/showthread.php?t=2729173
Then unlock your bootloader again using the unlock code you got from HTC.
Re-flash the latest TWRP found here... https://dl.twrp.me/m8/
This will give you a fresh start then you can try to flash the rom you want.
Click to expand...
Click to collapse
Umm...I don't have anything called SDK :/
What do I do then?
F0rZ3r0 said:
Umm...I don't have anything called SDK :/
What do I do then?
Click to expand...
Click to collapse
If you have a platform-tools you can use that or use the folder attached.
Unzip it and copy the files to a folder.
Sloth said:
If you have a platform-tools you can use that or use the folder attached.
Unzip it and copy the files to a folder.
Click to expand...
Click to collapse
Alright, I did it all, but it doesn't seem to be changing once I send over the zip. Is it meant to take a while or is there something wrong?
EDIT: 20 minutes later and still at the sending. Something probably went wrong.
EDIT 2: 30 minutes later, still sending.
F0rZ3r0 said:
Alright, I did it all, but it doesn't seem to be changing once I send over the zip. Is it meant to take a while or is there something wrong?
EDIT: 20 minutes later and still at the sending. Something probably went wrong.
EDIT 2: 30 minutes later, still sending.
Click to expand...
Click to collapse
Should only be a few seconds.
Sloth said:
Should only be a few seconds.
Click to expand...
Click to collapse
Not sure what the issue here is then. As I write this, it is still sending. I'm not sure what the issue is...
Check PM.