Related
I've S-Off'd (goldcard + AlphaRevX) my phone and used several custom ROMs for quite some time until a few minutes ago I decided to go back to stock ROM. The last custom ROM I used was CyanogenMod v7.1.0
I'm from Malaysia, so I downloaded the Asian RUU (RUU_Vivo_Gingerbread_S_hTC_Asia_WWE_2.12.707.5_Radio_20.2805.30.085AU_3805.04.03.27_M_release_190036 _signed.zip) and ran the .exe and went along with the step by step update, which I think I shouldn't have done. At the last part of the update there's an error saying that the installer could not update my phone. Now my Incredible S is back to S-On, but it's ROM-less; I can only go into fastboot.
Any way that I can bring my phone back to life?
Nicheuji said:
I've S-Off'd (goldcard + AlphaRevX) my phone and used several custom ROMs for quite some time until a few minutes ago I decided to go back to stock ROM. The last custom ROM I used was CyanogenMod v7.1.0
I'm from Malaysia, so I downloaded the Asian RUU (RUU_Vivo_Gingerbread_S_hTC_Asia_WWE_2.12.707.5_Radio_20.2805.30.085AU_3805.04.03.27_M_release_190036 _signed.zip) and ran the .exe and went along with the step by step update, which I think I shouldn't have done. At the last part of the update there's an error saying that the installer could not update my phone. Now my Incredible S is back to S-On, but it's ROM-less; I can only go into fastboot.
Any way that I can bring my phone back to life?
Click to expand...
Click to collapse
Does you bootloader say "security warning"?
neo-X said:
Does you bootloader say "security warning"?
Click to expand...
Click to collapse
Yes, it does.
Nicheuji said:
Yes, it does.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=16684717#post16684717
Basically, you stuffed up your mainversion, you need to find out what it currently is and install the stock ruu corresponding to your current version.
neo-X said:
http://forum.xda-developers.com/showthread.php?p=16684717#post16684717
Basically, you stuffed up your mainversion, you need to find out what it currently is and install the stock ruu corresponding to your current version.
Click to expand...
Click to collapse
I just read that post and I'm stuck at the part where I have to run the commands for fastboot (2nd option of fix). I don't know how to run the commands.
I tried the first option of fixing it. I tried a few RUUs with higher mainversion (current image version on my phone is 2.32.1010.1) but I get errors like "ERROR [130]: MODEL ID ERROR" from WWE_2.33.669.2, "ERROR [132]: SIGNARURE ERROR" from WWE_3.02.605.1.
How do I run these commands?
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <path to zip>
Nicheuji said:
I just read that post and I'm stuck at the part where I have to run the commands for fastboot (2nd option of fix). I don't know how to run the commands.
I tried the first option of fixing it. I tried a few RUUs with higher mainversion (current image version on my phone is 2.32.1010.1) but I get errors like "ERROR [130]: MODEL ID ERROR" from WWE_2.33.669.2, "ERROR [132]: SIGNARURE ERROR" from WWE_3.02.605.1.
How do I run these commands?
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <path to zip>
Click to expand...
Click to collapse
You need setup your fastboot environment to run this.
Check this thread:
http://wiki.cyanogenmod.com/wiki/Fastboot
Are you using a goldcard?
neo-X said:
Are you using a goldcard?
Click to expand...
Click to collapse
Yes, I am.
Nicheuji said:
Yes, I am.
Click to expand...
Click to collapse
WWE_2.33.669.2 and WWE_3.02.605.1 are for Sasktel and Verizon that's why you are getting those errors, i remember there was a way to change id's so that you could install these ones but not sure where that thread is.
There is however this ruu...
RUU_Vivo_W_CT_Gingerbread_S_HTCCN_CHS_CT_3.06.1401 .0_Radio_1_01_50_0817_NV_MFG_CT_2.71_release_21041 8_signed
from here http://forum.xda-developers.com/showthread.php?t=1033922
with a higher mainversion but im not sure about this one as i haven't used it before.
You could also contact a John Anderton on these forums, he's very good when it comes to this problem.
Regards
Hi!
I have had some serious issues with my USB-port and am looking to send the phone back for warranty. Since the problem is the USB isn't working that well I have some issues regarding unrooting..
I found my RUU and extracted the rom.zip which I renamed to PG32IMG.zip and placed on my phone. Fastboot foudn it and started flashing and everything. But I've read that since I can't upgrade Hboot (I used Revolutionary to gain S-off) the phone won't start.
My question is: What should I do to get that working? The only thing I can do as far as I can see, is placing files on the SD-card named for auto-flashing in fastboot..
Any advice? Am I screwed? Profit?
BloomTwig said:
Hi!
I have had some serious issues with my USB-port and am looking to send the phone back for warranty. Since the problem is the USB isn't working that well I have some issues regarding unrooting..
I found my RUU and extracted the rom.zip which I renamed to PG32IMG.zip and placed on my phone. Fastboot foudn it and started flashing and everything. But I've read that since I can't upgrade Hboot (I used Revolutionary to gain S-off) the phone won't start.
My question is: What should I do to get that working? The only thing I can do as far as I can see, is placing files on the SD-card named for auto-flashing in fastboot..
Any advice? Am I screwed? Profit?
Click to expand...
Click to collapse
Which RUU did you use? Is there a comparable Android 2.3.3/Sense 2.1 that you could use instead?
Ok, I can't help meddling in this. I have managed to re-flash CWR and restore my old backup of my old 2.3.3/2.1 stock rom. I have also gotten the ADB set-up and if only I could get that rom.zip file from my RUU I will flash stock HBoot..
I used RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed since that was the one that my phone tried to download and install by it self. But when I run it, and enter my temp folder to get the rom.zip it isn't there (only an older version that isn't posible to open..)
advice?
EDIT: would this work instead? RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed
BloomTwig said:
Ok, I can't help meddling in this. I have managed to re-flash CWR and restore my old backup of my old 2.3.3/2.1 stock rom. I have also gotten the ADB set-up and if only I could get that rom.zip file from my RUU I will flash stock HBoot..
I used RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed since that was the one that my phone tried to download and install by it self. But when I run it, and enter my temp folder to get the rom.zip it isn't there (only an older version that isn't posible to open..)
advice?
EDIT: would this work instead? RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed
Click to expand...
Click to collapse
Copy the rom.zip file out of your temp dir and then open it with a 3rd party zip program (not default windows zip program)
The ruu in your edit will not have boot 2.0 although I'm not understnding why you don't just run the sense 3 ruu, after using the downgrade method in the s-on thread.
Yeah, that was the problem. Was trying to open the zip-files with windows zip-program. with that I also realized that using the first RUU would be better... I have, however, some trouble getting the downgrade thingie to work. It asks for root, it asks for gold card and it reboots in to recovery. But when it's at "checking version - main" it just gets stuck at "waiting for device"..
EDIT: sorry, I completly missed the fact that I need to create a gold card... sorryf or being a noob... will get back soon..
Communication breakdown. I was referring to the revert to s-on thread http://forum.xda-developers.com/showthread.php?t=1359555
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
Newbie alert again!,
I have identified a few roms I want to test out and my phone is currently operating on the following,
Stock 4.2.2
sense 5.0
software 2.24.161.1
Super cid 11111111
Hboot 156
S-off
Latest trwp recovery.
hypothetically if I was to choose one of the latest ARHD roms (which I would like to consider) could I flash it with my current firmware?
I looked for older versions of ARHD roms to see if there were versions that could avoid me flashing new firmware but there only seems to be the latest update and a Google edition so I am guessing there may be a performance/compatability issue without a newer firmware?
The Rom and Firmware guides appear to be handled separately (which is understandable) but doesnt help a newbie like me make an educated decision,in terms of what firmware to go for...or not to update it at all?
Many guides ignore the firmware side of things or there are suggestions that you can do before or after flashing a rom??but not a joined up part of the process (again I understand the principal of why this is like it is ).
Being seperate threads or processes it is sometimes hard to align forum postings with each other to manually put the process in a list in my mind that is consitent, in date and current.
Cutting to the chase....do I just bite the bullet and upgrade to the specifically associated firmware to the android os/rom build I am going to flash?.?or dont worry about it too much initially?
If i am Supercid... do i only match the phone model number when choosing firmware as I am technically regionally/carrier unlocked?(picking the right one probably troubles me more!)
With s-off as there is no margin for error using the wrong firmware,whereas I have recovery and back ups for the rom side of things.
For me its a bit like riding a bike...i need my stablisers to get my confidence...once i have tried a few solo runs ..i will be fine.. I am sure you have all worn your L plates sorry to burden you with mine...but this forum seems like the safest place to learn !
Shepps
shepppster said:
Newbie alert again!,
I have identified a few roms I want to test out and my phone is currently operating on the following,
Stock 4.2.2
sense 5.0
software 2.24.161.1
Super cid 11111111
Hboot 156
S-off
Latest trwp recovery.
hypothetically if I was to choose one of the latest ARHD roms (which I would like to consider) could I flash it with my current firmware?
I looked for older versions of ARHD roms to see if there were versions that could avoid me flashing new firmware but there only seems to be the latest update and a Google edition so I am guessing there may be a performance/compatability issue without a newer firmware?
The Rom and Firmware guides appear to be handled separately (which is understandable) but doesnt help a newbie like me make an educated decision,in terms of what firmware to go for...or not to update it at all?
Many guides ignore the firmware side of things or there are suggestions that you can do before or after flashing a rom??but not a joined up part of the process (again I understand the principal of why this is like it is ).
Being seperate threads or processes it is sometimes hard to align forum postings with each other to manually put the process in a list in my mind that is consitent, in date and current.
Cutting to the chase....do I just bite the bullet and upgrade to the specifically associated firmware to the android os/rom build I am going to flash?.?or dont worry about it too much initially?
If i am Supercid... do i only match the phone model number when choosing firmware as I am technically regionally/carrier unlocked?(picking the right one probably troubles me more!)
With s-off as there is no margin for error using the wrong firmware,whereas I have recovery and back ups for the rom side of things.
For me its a bit like riding a bike...i need my stablisers to get my confidence...once i have tried a few solo runs ..i will be fine.. I am sure you have all worn your L plates sorry to burden you with mine...but this forum seems like the safest place to learn !
Shepps
Click to expand...
Click to collapse
You are s-off and super cid. Nothing much to worry about here. I'm assuming you are not sprint or verizon. Just get the newest firmware and flash it. If something isn't working right for you flash old firmware. You are not locked down to anything. Here is the newest firmware that will work fine unless you are sprint/verizon/ or dual sim model
https://www.androidfilehost.com/?fid=95897840722644637 - Thanks to LIabtoofer
BACKUP FIRST
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip <--it will say flash again and take longer the second time
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Load newest twrp -http://techerrata.com/browse/twrp2/m7
fastboot flash recovery twrp.img
fastboot erase cache <-- may fail since we wiped cache once already, no biggie
Load twrp "which mounts automatically now" put your rom on phone
wipe, advanced, cache-dalvik,system,data - Wipe <---cache may fail
install new rom. This lollipop firmware works fine with kitkat roms too
an0ther said:
You are s-off and super cid. Nothing much to worry about here. I'm assuming you are not sprint or verizon. Just get the newest firmware and flash it. If something isn't working right for you flash old firmware. You are not locked down to anything. Here is the newest firmware that will work fine unless you are sprint/verizon/ or dual sim model
BACKUP FIRST
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip <--it will say flash again and take longer the second time
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Load newest twrp -
fastboot flash recovery twrp.img
fastboot erase cache <-- may fail since we wiped cache once already, no biggie
Load twrp "which mounts automatically now" put your rom on phone
wipe, advanced, cache-dalvik,system,data - Wipe <---cache may fail
install new rom. This lollipop firmware works fine with kitkat roms too
Click to expand...
Click to collapse
Really appreciate this response and I am not sprint/verzion or dual sim so got that covered.
Just to clarify the rest....
The process of flashing the firmware will completely wipe the phone?
Flash TWRP recovery (i already have this but if the above assumption is correct ,understood!)
Install the new rom...or could I flash my back up (which I have via a OTG lead and memory stick)?
or would the new firmware be incompatible with my old JB 4.2.2 and cause problems?
The only reason I ask is that I could take a breather until I make my decision regarding a new rom.
However u pro's might think just go for it in one its no biggie lol?
Many thanks
Sheppps
shepppster said:
Really appreciate this response and I am not sprint/verzion or dual sim so got that covered.
Just to clarify the rest....
The process of flashing the firmware will completely wipe the phone?
Flash TWRP recovery (i already have this but if the above assumption is correct ,understood!)
Install the new rom...or could I flash my back up (which I have via a OTG lead and memory stick)?
or would the new firmware be incompatible with my old JB 4.2.2 and cause problems?
The only reason I ask is that I could take a breather until I make my decision regarding a new rom.
However u pro's might think just go for it in one its no biggie lol?
Many thanks
Sheppps
Click to expand...
Click to collapse
I do not recommend you just grab the latest firmware update and flash it to you phone, There is a very good chance you will brick your device with a firmware incompatibility
As your on 2.xx firmware jumping strait to 6.xx or 7.xx is a big jump and skipping firmware updates should never be recommended.
To safely update your firmware you need to flash 3.xx, 4.xx, 5.xx and so on untill your updated to the latest firmware. I was able to find the 5.xx and 6.xx firmwares for your device here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/161/ but you will still need to find 3.xx and 4.xx. ALternativly because your s-off with super cid you could switch to a different firmware brand HTC 401 for example. all of which can be found here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
you will need to flash atleast these 4 updates to get to the latest safely
3.62.401.1
4.19.401.11
5.11.401.10
6.09.401.12
On the other hand if your not comfortable flashing firmware you could just install a Guru Reset rom then update your phone through OTA updates although that will take much longer than flashing the firmware manually. This reset rom will give you stock with working OTA's if installed with the following options http://www.htc1guru.com/dld/guru_reset_m7_2-24-161-1-zip/
Stock Recovery = Yes
Stock Radio =Yes
Root = No
Thanks for that advice,
it did cross my mind that it was a bit of a leap.
If I went back to restoring the stock reovery I know i would lose root and custom recovery and the unlocked status.
Would I have to return to S-on and lose supercid?
TBH getting to s-off was a bit of a nightmare and took a number of tries so I would hate to go through that again?
I might try a phased firmware update unless you recomend a custom rom that will work comfortably with my current firmware?
I prefer the stock look of the ARHD roms...but older versions dont see to be around anymore.
I shall dwell on the situation!
Shepps
shepppster said:
Thanks for that advice,
it did cross my mind that it was a bit of a leap.
If I went back to restoring the stock reovery I know i would lose root and custom recovery and the unlocked status.
Would I have to return to S-on and lose supercid?
TBH getting to s-off was a bit of a nightmare and took a number of tries so I would hate to go through that again?
I might try a phased firmware update unless you recomend a custom rom that will work comfortably with my current firmware?
I prefer the stock look of the ARHD roms...but older versions dont see to be around anymore.
I shall dwell on the situation!
Shepps
Click to expand...
Click to collapse
NEVER EVER GO S-on ... no matter who says it .. NEVER GO S-on
clsA said:
NEVER EVER GO S-on ... no matter who says it .. NEVER GO S-on
Click to expand...
Click to collapse
Heeding your words clsA... I dont want to go through that headache again ..it took me 3 days to get it off with rumrunner (mainly down to the PC's i was using rather than the software) but i dont intend to go back Jack!
clsA said:
NEVER EVER GO S-on ... no matter who says it .. NEVER GO S-on
Click to expand...
Click to collapse
^^^Wise Words^^^ going back to s-on always causes more problems than it solves. Never ever go back to s-on
shepppster said:
Heeding your words clsA... I dont want to go through that headache again ..it took me 3 days to get it off with rumrunner (mainly down to the PC's i was using rather than the software) but i dont intend to go back Jack!
Click to expand...
Click to collapse
You shouldn't shy away from updating your firmware it's really not that scary and perfectly safe as long as you do it correctly. You can even flash modified firmwares. So if you wanted to flash a firmware without losing your custom recovery and boot.img just open the firmware.zip and delete the recovery and boot.img then flash.
below is the basic procedure for flashing a firmware.zip with s-off.
Download the firmware.zip and put it in your fastboot folder on your pc. Boot your phone to the bootloader and connect fastboot usb. In the command window use the following commands to flash the firmware.
Code:
fastboot erase cache
fastboot oem rebootRUU
--- case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update and will appear to fail. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Danny201281 said:
^^^Wise Words^^^ going back to s-on always causes more problems than it solves. Never ever go back to s-on
You shouldn't shy away from updating your firmware it's really not that scary and perfectly safe as long as you do it correctly. You can even flash modified firmwares. So if you wanted to flash a firmware without losing your custom recovery and boot.img just open the firmware.zip and delete the recovery and boot.img then flash.
below is the basic procedure for flashing a firmware.zip with s-off.
Download the firmware.zip and put it in your fastboot folder on your pc. Boot your phone to the bootloader and connect fastboot usb. In the command window use the following commands to flash the firmware.
Code:
fastboot erase cache
fastboot oem rebootRUU
--- case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update and will appear to fail. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks for this,I need a bit more clarity.
Delete the two files as described from the zip file,re-zip (package will have hboot,radio,adsp etc).
Flash firmware (do I refer to it by zip name eg3.62.401.1.zip or just as described firmware.zip,although i am guessing one wouldnt actually do anything)
Reboot ,go to recovery (which will be my TWRP) full wipe and flash my back up (or will this revert to my current firmware?) or flash a new rom?
If still using my JB 4.2.2 work with newer firmware? or do I need to start matching the o/s revisions for example 4.3 for the 1st upgrade...move onto the 4.****** firmware next one etc Kit kat rom ?
As I am supercid like you said ,is the alternative firmware ok with my device are these versions just different carrier versions or unsigned or whatever and would there be an isue if i moved to this branch of firmware?
All I really want to do is get my phone to a Kit Kat position...the Guru /ota route seems too convoluted and I am comfortable using fastboot commands but like to have the whole process as water tight as I can get it!
Clearly after the work I gone to to get in a total unlocked state I definitely dont want to go back!
Just to confirm flashing any firmware would not overide my S-off settings that would have to be physically done by command using the appropriate software?
Sorry if you guys are repeating something like this over and over again... best safe and not sorry imo!
Thanks Again
Shepps
shepppster said:
Thanks for this,I need a bit more clarity.
Delete the two files as described from the zip file,re-zip (package will have hboot,radio,adsp etc).
Flash firmware (do I refer to it by zip name eg3.62.401.1.zip or just as described firmware.zip,although i am guessing one wouldnt actually do anything)
Reboot ,go to recovery (which will be my TWRP) full wipe and flash my back up (or will this revert to my current firmware?) or flash a new rom?
If still using my JB 4.2.2 work with newer firmware? or do I need to start matching the o/s revisions for example 4.3 for the 1st upgrade...move onto the 4.****** firmware next one etc Kit kat rom ?
As I am supercid like you said ,is the alternative firmware ok with my device are these versions just different carrier versions or unsigned or whatever and would there be an isue if i moved to this branch of firmware?
All I really want to do is get my phone to a Kit Kat position...the Guru /ota route seems too convoluted and I am comfortable using fastboot commands but like to have the whole process as water tight as I can get it!
Clearly after the work I gone to to get in a total unlocked state I definitely dont want to go back!
Just to confirm flashing any firmware would not overide my S-off settings that would have to be physically done by command using the appropriate software?
Sorry if you guys are repeating something like this over and over again... best safe and not sorry imo!
Thanks Again
Shepps
Click to expand...
Click to collapse
When you flash the firmware.zip the command ends with the actual name of the zip so if the zip is named 3.62.401.1.zip then the correct command would be
Code:
fastboot flash zip 3.62.401.1.zip
The firmware packages are basically the same
3.xx.502.x is AT&T
3.xx401.x is HTC or
3.xx771.x is H3G
and so on, The 3 digit number in the middle is as you suggested just a carrier identifier. Flashing firmware or RUU's will not change your s-off status only you can do that with a very specific fastboot command the chances of it happening accidentally are very slim unless you do it with a toolkit.
So to get to kitkat simply flash the 3.xx 4.xx 5.xx and 6.xx firmware you do not need to flash a matching rom for each firmware version just fastboot reboot-bootloader after each firmware zip the go right to flashing the next one. Once there all done the phone should boot right up regardless of what rom you currently have installed (Provided you removed the boot.img and recovery.img from the zips before flashing) or you can go right to flashing a kitkat based custom rom of your choice if you haven't already. :good:
Danny201281 said:
When you flash the firmware.zip the command ends with the actual name of the zip so if the zip is named 3.62.401.1.zip then the correct command would be
Code:
fastboot flash zip 3.62.401.1.zip
The firmware packages are basically the same
3.xx.502.x is AT&T
3.xx401.x is HTC or
3.xx771.x is H3G
and so on, The 3 digit number in the middle is as you suggested just a carrier identifier. Flashing firmware or RUU's will not change your s-off status only you can do that with a very specific fastboot command the chances of it happening accidentally are very slim unless you do it with a toolkit.
So to get to kitkat simply flash the 3.xx 4.xx 5.xx and 6.xx firmware you do not need to flash a matching rom for each firmware version just fastboot reboot-bootloader after each firmware zip the go right to flashing the next one. Once there all done the phone should boot right up regardless of what rom you currently have installed (Provided you removed the boot.img and recovery.img from the zips before flashing) or you can go right to flashing a kitkat based custom rom of your choice if you haven't already. :good:
Click to expand...
Click to collapse
Great I get that and it makes sense now..but it always pays to check and double check.
My last question is the zips contain radio too,clearly this may or may not be an issue but i would predict they are desgined for certain carriers.The 401 branch I would assume are generic HTC international ones and shouldnt raise an issue unless I went for AT&T whiich is American...and I am in the UK perhaps.
Shepps
shepppster said:
Great I get that and it makes sense now..but it always pays to check and double check.
My last question is the zips contain radio too,clearly this may or may not be an issue but i would predict they are desgined for certain carriers.The 401 branch I would assume are generic HTC international ones and shouldnt raise an issue unless I went for AT&T whiich is American...and I am in the UK perhaps.
Shepps
Click to expand...
Click to collapse
Yeah the HTC 401 firmwares are WWE or World Wide English :good: the radio's shouldnt cause you any problems. And don't worry about asking questions Better to ask before you try. Preventing a brick is easier than fixing one :good:
Danny201281 said:
Yeah the HTC 401 firmwares are WWE or World Wide English :good: the radio's shouldnt cause you any problems. And don't worry about asking questions Better to ask before you try. Preventing a brick is easier than fixing one :good:
Click to expand...
Click to collapse
Well with that invite to ask at least one last question.... I saw the collection of ARHD drivers on this forum state the following? (cant post the link sorry)
"Firmware package from 2.17.401.1 RUU
There are new touch panel drivers inside this firmware that breaks touch in custom recoveries. You can flash it and use only hardware keys in custom recovery or you can remove tp_SYN3202.img from inside the package before flashing."
I would be jumping straight to the 3.******* and upwards but would the same apply delete the same throughout? If it only breaks the custom recovery touch panel I could use a mouse and OTG cable as I assume they are fine in O/S or best to remove the file throughout as it is no big deal.
Finally if there was a beer icon u would get it +thanks.
If you ever need gardening advice just Holla its all i can offer in return for your help and everyone else in this thread lol!:good: (why u might need I dont know ,but u never know lol)
shepppster said:
Well with that invite to ask at least one last question.... I saw the collection of ARHD drivers on this forum state the following? (cant post the link sorry)
"Firmware package from 2.17.401.1 RUU
There are new touch panel drivers inside this firmware that breaks touch in custom recoveries. You can flash it and use only hardware keys in custom recovery or you can remove tp_SYN3202.img from inside the package before flashing."
I would be jumping straight to the 3.******* and upwards but would the same apply delete the same throughout? If it only breaks the custom recovery touch panel I could use a mouse and OTG cable as I assume they are fine in O/S or best to remove the file throughout as it is no big deal.
Finally if there was a beer icon u would get it +thanks.
If you ever need gardening advice just Holla its all i can offer in return for your help and everyone else in this thread lol!:good: (why u might need I dont know ,but u never know lol)
Click to expand...
Click to collapse
You'll be fine the touch screen drivers problem only affects the lower end firmwares. Nothing in the 3.xx upwards to worry about. :good:
Danny201281 said:
You'll be fine the touch screen drivers problem only affects the lower end firmwares. Nothing in the 3.xx upwards to worry about. :good:
Click to expand...
Click to collapse
Thanks again out of curiosity the boot img ,that i would delete from the firmware zip, what does it actually do?
Does it fire up the o/s in the order it needs to launch the phone and as a stock file would expect to see the related o/s system infront of it and flashing a new rom would create a new image for the new set up?
I understand the reason for deleting the recovery file .
and one other thing whilst I intend to use one of the latest customs...if I had problems and flashed my nandroid back up from TWRP would it work using JB 4.2.2? and or would it restore the firmware to the old one too or just restore the o/s so effectiveley i could use my old rom while i looked for another newer one or tried again?
I know my old rom wouldnt optimise the new firmware ,but it would give me time inbetwen tasks if I wanted to do the next step later too.
making mistakes is much easier to resolve the better you understand the logic of the engine so to speak.
Shepps
shepppster said:
Thanks again out of curiosity the boot img ,that i would delete from the firmware zip, what does it actually do?
Does it fire up the o/s in the order it needs to launch the phone and as a stock file would expect to see the related o/s system infront of it and flashing a new rom would create a new image for the new set up?
I understand the reason for deleting the recovery file .
Click to expand...
Click to collapse
You hit the nail on the head there the boot.img is a Rom specific boot launcher if you like. Or otherwise known as the Kernel. If you have a custom Rom and flash a stock firmware the custom boot.img is replaced with the stock boot.img so your custom Rom won't boot. Simply flashing the boot.img from your custom Rom would fix it and all your data will remain in tact but it's just easier to avoid it :good:
and one other thing whilst I intend to use one of the latest customs...if I had problems and flashed my nandroid back up from TWRP would it work using JB 4.2.2? and or would it restore the firmware to the old one too or just restore the o/s so effectiveley i could use my old rom while i looked for another newer one or tried again?
I know my old rom wouldnt optimise the new firmware ,but it would give me time inbetwen tasks if I wanted to do the next step later too.
making mistakes is much easier to resolve the better you understand the logic of the engine so to speak.
Shepps
Click to expand...
Click to collapse
Yes you can downgrade your Rom but keep your newer firmware. It shouldn't cause any major problems. You may find things like reduced no mobile or WiFi signal. Capacitive buttons not working as expected and such but usually everything works ok :good:
Danny201281 said:
You hit the nail on the head there the boot.img is a Rom specific boot launcher if you like. Or otherwise known as the Kernel. If you have a custom Rom and flash a stock firmware the custom boot.img is replaced with the stock boot.img so your custom Rom won't boot. Simply flashing the boot.img from your custom Rom would fix it and all your data will remain in tact but it's just easier to avoid it :good:
Yes you can downgrade your Rom but keep your newer firmware. It shouldn't cause any major problems. You may find things like reduced no mobile or WiFi signal. Capacitive buttons not working as expected and such but usually everything works ok :good:
Click to expand...
Click to collapse
I think this is my final question ...I know this has ended up a tutorial but the thread provides good advice to noobies.
I intend to flash the ARHD 84. once i reach the latest firmware.
Will flash each firmware up to 6.09.401.12 deleting the boot img and the recovery in each package.
When I get to firmware 6.09.401.12 I see the rom uses the official firmware so at this point I only need to delete recovery? ...the boot img should be fine for the rom?
Or do I delete the boot image as before as the flash process creates a new boot img.
or I flash the boot img from the custom zip usiing fastboot?(as there is a boot img file in the HD84 zip file)
That is it and sorry for turning this ino a saga,but I think this is a good reference thread in the long run
Shepps
shepppster said:
I think this is my final question ...I know this has ended up a tutorial but the thread provides good advice to noobies.
I intend to flash the ARHD 84. once i reach the latest firmware.
Will flash each firmware up to 6.09.401.12 deleting the boot img and the recovery in each package.
When I get to firmware 6.09.401.12 I see the rom uses the official firmware so at this point I only need to delete recovery? ...the boot img should be fine for the rom?
Or do I delete the boot image as before as the flash process creates a new boot img.
or I flash the boot img from the custom zip usiing fastboot?(as there is a boot img file in the HD84 zip file)
That is it and sorry for turning this ino a saga,but I think this is a good reference thread in the long run
Shepps
Click to expand...
Click to collapse
you don't have to delete anything from the firmware's just flash them sequentially till you get to the last one
then just flash TWRP and your rom to the phone
shepppster said:
I think this is my final question ...I know this has ended up a tutorial but the thread provides good advice to noobies.
I intend to flash the ARHD 84. once i reach the latest firmware.
Will flash each firmware up to 6.09.401.12 deleting the boot img and the recovery in each package.
When I get to firmware 6.09.401.12 I see the rom uses the official firmware so at this point I only need to delete recovery? ...the boot img should be fine for the rom?
Or do I delete the boot image as before as the flash process creates a new boot img.
or I flash the boot img from the custom zip usiing fastboot?(as there is a boot img file in the HD84 zip file)
That is it and sorry for turning this ino a saga,but I think this is a good reference thread in the long run
Shepps
Click to expand...
Click to collapse
If your intention is to flash a rom directly after flashing the firmware then you don't need to worry about the boot.img, the correct boot.img will be flashed with the rom.
It's a good idea to have the rom in your internal storage before you start though so you won't need to boot to android to copy the rom after flashing the firmware or use adb push to get the rom to the phone.
Danny201281 said:
If your intention is to flash a rom directly after flashing the firmware then you don't need to worry about the boot.img, the correct boot.img will be flashed with the rom.
It's a good idea to have the rom in your internal storage before you start though so you won't need to boot to android to copy the rom after flashing the firmware or use adb push to get the rom to the phone.
Click to expand...
Click to collapse
I already have it on my internal memory and also on a USB stick via OTG lead,and in my Fastboot folder (so 3 options).
I Will have to re-install/flash img of TWRP again (if i didnt delete the recovery in the firmware zip files and,as the firmwares will give me stock recovery)- reboot into bootloader launch TWRP recovery find the rom on SD or push in adb or flash from memstick...but job done!
Any issues installing TWRP over an old one? (I intend to use the same version as I have now) I assume it will see the old TWRP folder and old bkup in the SD card too? if not I am goin for it!
Shepps
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.