I currently have a m7 that is S-Off, mainly for the Google edition conversion. I'm thinking about upgrading to the m8, and if I do I will most likely have the latest firmware. Anyone know if the latest firmware of the phone can be S-Off'd? And yes I understand some phones are built differently, but as a whole has it been possible?
ADarkKnight said:
I currently have a m7 that is S-Off, mainly for the Google edition conversion. I'm thinking about upgrading to the m8, and if I do I will most likely have the latest firmware. Anyone know if the latest firmware of the phone can be S-Off'd? And yes I understand some phones are built differently, but as a whole has it been possible?
Click to expand...
Click to collapse
Firmware rev could vary slightly based on manufacture date. I got my AT&T M8 the end of June. I think I saw somewhere a manufacture date of 5/2014 (can't remember where). Mine came with 1.12.502.18 FW.
I Dev.Unlocked, installed TWRP and installed ARHD 8.1 Stock ROM. It ran well, but I had the sound problem with music. Sometimes it played, sometimes it didn't Not the ROM's fault AFAIK. Friends with the same hardware rev as me running the same ROM had (music) sound.
I S-OFF'ed with Sunshine - worked perfectly
I then flashed my hboot - no red text - worked perfectly
I went Super CID - easy too
Flashed my FW to 2.22.401.5 - found thread that allows you to flash without computer or adb - this was very cool
Installed ARHD 11.1, but omitted the H/K sound mod to see if boom sound would work - it did
I then flashed HK _v6 with ADSP update - worked great
I believe sound was likely fixed when I upgraded, but was tired of going through set up even with back ups. I never dirty flashed either.
So, get Sunshine for S-OFF. It just works. If you think spending $25 to have your phone properly S-OFF'ed is unreasonable, then you shouldn't be modding your phone. It takes 5 mins and was well worth the money IMO.
shadowsports said:
Firmware rev could vary slightly based on manufacture date. I got my AT&T M8 the end of June. I think I saw somewhere a manufacture date of 5/2014 (can't remember where). Mine came with 1.12.502.18 FW.
I Dev.Unlocked, installed TWRP and installed ARHD 8.1 Stock ROM. It ran well, but I had the sound problem with music. Sometimes it played, sometimes it didn't Not the ROM's fault AFAIK. Friends with the same hardware rev as me running the same ROM had (music) sound.
I S-OFF'ed with Sunshine - worked perfectly
I then flashed my hboot - no red text - worked perfectly
I went Super CID - easy too
Flashed my FW to 2.22.401.5 - found thread that allows you to flash without computer or adb - this was very cool
Installed ARHD 11.1, but omitted the H/K sound mod to see if boom sound would work - it did
I then flashed HK _v6 with ADSP update - worked great
I believe sound was likely fixed when I upgraded, but was tired of going through set up even with back ups. I never dirty flashed either.
So, get Sunshine for S-OFF. It just works. If you think spending $25 to have your phone properly S-OFF'ed is unreasonable, then you shouldn't be modding your phone. It takes 5 mins and was well worth the money IMO.
Click to expand...
Click to collapse
Thanks for the reply. When I get it I'll try firewater first and if not then sunshine. 25$ IMO is a little high, but still reasonable and well worth it over dropping 800$ on a Google edition version.
SunShine is definitely worth the money for sure.
AT&T HTC ONE M8 ,S-OFF
Related
I have been running MIUI for about a month as my daily driver. every few weeks i would try out a new MYN rom or a new Fresh Rom but it seems they always have the same issues. with any Sense Rom i run i get reboots every so often for no reason. also i get Forced closes on Google Music and Pandora. I am not a noob to flashing Rom's at all as i have been doing it sense the Hero days, but i am at a loss on this one. I am using CWM but have also used TWRP in there just to see if it made a difference and it hasn't. every time i flash i do a full wipe and then run the Warm Format All utility. I have tried out several of the ICS Rom's and haven't had any rebooting issues. I even updated all of the radios in an effort to resolve this but to no success. I love Miui but i would like a stable Sense Rom to go back to every now and again if i am going to be in an area with 4G and need to tether. or use my stereo Bluetooth headset.
ricersniper said:
I have been running MIUI for about a month as my daily driver. every few weeks i would try out a new MYN rom or a new Fresh Rom but it seems they always have the same issues. with any Sense Rom i run i get reboots every so often for no reason. also i get Forced closes on Google Music and Pandora. I am not a noob to flashing Rom's at all as i have been doing it sense the Hero days, but i am at a loss on this one. I am using CWM but have also used TWRP in there just to see if it made a difference and it hasn't. every time i flash i do a full wipe and then run the Warm Format All utility. I have tried out several of the ICS Rom's and haven't had any rebooting issues. I even updated all of the radios in an effort to resolve this but to no success. I love Miui but i would like a stable Sense Rom to go back to every now and again if i am going to be in an area with 4G and need to tether. or use my stereo Bluetooth headset.
Click to expand...
Click to collapse
Odd indeed. Perhaps a kernal issue? Are you on Hboot 1.4 or 1.5? Also, check out CleanROM as it is a VERY stable and fast rom. Little to no issues with it.
thanks for the advice. I got fed up today as the issue continued and even started happening with MIUI. I ran the latest RUU on the phone and took it to a sprint store and they ran a benchmark on it for about 30 min and nothing happened. They went ahead and ordered me another phone. Here is the strange bit. I ran the 2.08 RUU and i confirmed that it put HBoot 1.50 on the phone. when i got back to my office i ran the 1.13 RUU and it had HBoot 1.40 back on it. I then re-rooted with Revolutionary and i am finishing up with it now. I thought once you had 1.50 you were stuck with it no matter what.
ricersniper said:
thanks for the advice. I got fed up today as the issue continued and even started happening with MIUI. I ran the latest RUU on the phone and took it to a sprint store and they ran a benchmark on it for about 30 min and nothing happened. They went ahead and ordered me another phone. Here is the strange bit. I ran the 2.08 RUU and i confirmed that it put HBoot 1.50 on the phone. when i got back to my office i ran the 1.13 RUU and it had HBoot 1.40 back on it. I then re-rooted with Revolutionary and i am finishing up with it now. I thought once you had 1.50 you were stuck with it no matter what.
Click to expand...
Click to collapse
odd indeed. hope everything gets worked out for you. definitely check out CleanROM as it is a great stable rom when you want to go back to the stock sense look/feel and still have great performance.
I will give it a try. I have used it in the past. Thanks for your help.
ricersniper said:
thanks for the advice. I got fed up today as the issue continued and even started happening with MIUI. I ran the latest RUU on the phone and took it to a sprint store and they ran a benchmark on it for about 30 min and nothing happened. They went ahead and ordered me another phone. Here is the strange bit. I ran the 2.08 RUU and i confirmed that it put HBoot 1.50 on the phone. when i got back to my office i ran the 1.13 RUU and it had HBoot 1.40 back on it. I then re-rooted with Revolutionary and i am finishing up with it now. I thought once you had 1.50 you were stuck with it no matter what.
Click to expand...
Click to collapse
wait, so you can just RUU to an "outdated" stock ROM if you're stuck on hboot 1.5? that seems too easy to do, it's hard to believe that's not common knowledge. I would test this in a heartbeat myself if I wasn't one of the lucky ones who got a phone with hboot 1.3 when I bought my phone less than a month ago
i ran the 2.08 ruu went to sprint they booted into the bootloader in front of me and showed me what he was going to do. i looked and confirmed that it said hboot 1.5 it was still s-off and he didn't notice that i dont think. i got back to my office booted the bootloader and once again confirmed it was 1.50. i started looking for ways to downgrade. while i waited i installed the 1.13 ruu in the hopes it might do something and it did. I found the ruu here on XDA and it put me back to 1.4 with the .97 radio and everything. i ran revolutionary and re rooted and then restored the last backup i had and i am still using it now.
I have my LTE rooted with s-on and Hboot 1.12 I dont know if Dumlock is installed but I've seen before somewhere in the phonew. My problem is bluetooth. The ding dong I sent the phone to who rooted with s-on had flashed the htc viper rom- theres a warning under 'quietly brilliant' that says "not for use outside of htc without certain permission, doing so may result in legal action" or something to that effect. Anywhay, this was way back when the LTE came out and the bluetooth worked fine until 3 or so weeks ago. Thats about the time that the 2.13.651.1 or whatever it is came out. The bluetooth dropped and would not re-connect. Then unpairing, soft resets, safe mode reboots, factory resets, I have 3 bluetooth units and they all pair up to ther devices no problem. I flashed 2 other roms - mean rom which based on the 2.13.651.1 update as well as the Team win Venom Viper rom which is by far the best rom I've had. This rom is also based on the update. So I imagine I have it. The bluetooth none the less does not work. I found out yesterday that since the update there are a couple oither people with the bluetooth issue. Htc is aware oif the issue and is working on a fix which could take weeksI am perplexed as to wether this is the issue or the fact that I have s-on. I saw there was a download of that update for rooted users posted so I downloaded it and flashed it and my phone went into a bootloop-I almost didnt get it out but I did and dl'd the viper rom again and the phones working nice again- no BT and a couple custom features within the rom arent working but not a big deal. My guess is I need s-off - I dont think anyhting else will work until this is done. Are you aware of this bluetooth issue and would you be able to give me the proper steps in getting s-off on the phone?
Thanks very much for your time,
TJ
Son with unlocked does not affect anything in the os, soff gives you the advantage of direct access to the partitions on your phone. Unlocking the bootloader gives partial access, soff and hboot unlock only deals with the hboot, partitions, and access full read/write access through the fastboot command line
Don't see any way that s-off is going to help the bluetooth issue. Also the only way to get s-off requires the 1.13 software. I've heard that downgrading is not recommended and can cause issues. Better to stay s-on.
FrankthaTank said:
Don't see any way that s-off is going to help the bluetooth issue. Also the only way to get s-off requires the 1.13 software. I've heard that downgrading is not recommended and can cause issues. Better to stay s-on.
Click to expand...
Click to collapse
Toolkit for downgrade is being worked on now. Exciting stuff!
S-on or S-off, bluetooth the real issue
om4 said:
Toolkit for downgrade is being worked on now. Exciting stuff!
Click to expand...
Click to collapse
Hello I see you're a senior member and I'm wondering if you would read this and possibly shed any light on my problem, I’d be very grateful. First a little info on my phone and root:
In the bootloader it says ***TAMPERED*** ***UNLOCKED*** JEWEL PVT SHIP S-ON RL, HBOOT- 1.12.0000, RADIO-1.02.12.0427, Open-DSP-v25.o1.32.0405, eMMC boot. The rom that was loaded on the phone was an HTC build called Viper Rom. When the HTC 'quietly brilliant' screen comes up, underneath in red text it says "This build is for developement purposes only Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action." There were no issues with the bluetooth for months. My Bluetooth started disconnecting roughly 3 or 4 weeks ago and I have tried almost everything I can think of to try and fix it. First checking the three Bluetooth headset devices I use on other devices and they show up no problem. The perplexing thing that I recently found is when connectin via USB and opening all the files on the phone, there is no 'root' file that I can find anywhere. What I have tried:
1. Soft resets
2. safe mode restarts
3. factory resets
4. Bluetooth fix/ repair app
5. Change wifi frequency band from 'auto' to '2.4'
Now all of the 5 things above that I have tried worked one time and all stopped working within about 2 hours. Some almost right away the bt was disconnecting- even though it would re-connect, soon that stopped. From that point forward I have done the following:
1. Downloaded and flashed the 'Team Venom's version of Viper Rom 2.0.0.
The rom worked fine. but no BT. Another member on XDA suggested flashing the latest Mean Rom based on the HTC update 2.13.651.1. Did so, no BT. Then I flashed the latest Viper Rom 2.0.2 also based on the update and no BT. My next step was flashing a rooted version of that update that Max (Mikroms) posted on here. I did a factory rest, wipe cashe, wipe Dalvik cashe- six times before doing so. I Thought bricked my phone, it was bootlooping. I held down the power button for two full minutes then let go and then held down the power and vol down buttons and luckily the bootloader came up. I again did a factory reset, cashe and Dalvik wipe and reflashed the Viper Rom 2.0.2 again. which is the best rom I have ever used. This time some of the viper Tweak aren't working of available but everything else works fine except the BT.
I found out a couple of days ago there are a couple other people having a similar problem. I called HTC and they are aware theres a BT problem and are working on a fix which could take weeks. I dont know how I would get this fix since my phone is S-on. Another senior member has told me I can get S-off on the phone since I have 1.12 Hboot. I will be reading up on how to properly do that but was also told that that wouldn't have anything to do with the BT. I see it as being able to get updates, fixes and other stuff I have read about 'S-off'
After reading online, I found something about fixing bluetooth with logcat but didn't quite understand it. I do have an app on my phone now called aLogcat but do not know how to use it. I also went through the Play store and came across an app called 'rSAP- Bluetooth SIM Access Profile'. I then read the reviews and it sounded like the fix. Instead of spendingt the $12.49, I downloaded the trial version. An error came up "System file library not found. Is the an HTC/Samsung phone?" with no means to reply. The first clue about the problem is that the BT system files are not there, empty or blocked somehow. The only other things I can think of are:
Finding a stock rom, downloading/ flashing latest stock RUU.
Finding and copying the bluetooth system files from a friends evo 4G LTE phone that is a couple months newer.
I will be contacting my BT headset manufacturer and see if I can find out what should be on the phone for files since HTC wont or dosen't know what they are. Do you know how to access and copy the BT software on the phone or have any answers or suggestions moving forward???
Thanks in advance for any info,
TJ
So i just got my One yesterday and it still has the .7 firmware / rom on it. I am going to root it and s-off right now, but just wondering a couple things.
1. Can or should i use an ruu to update the firmware to the more recent versions?
2. If yes, will this make me lose root or s-off? (i would imagine root would be easy enough to get back as long as i still have s-off)
thanks!!
At the moment, unless the situation has changed, there isn't an RUU for the TMo HTC One. One was released the other day, but it didn't work and HTC pulled the download. For now, I'd wait a couple of days to see if they release a fixed version. Your only other option would be to flash the .ZIP with the updated radio after going S-OFF.
Sisyphus306 said:
At the moment, unless the situation has changed, there isn't an RUU for the TMo HTC One. One was released the other day, but it didn't work and HTC pulled the download. For now, I'd wait a couple of days to see if they release a fixed version. Your only other option would be to flash the .ZIP with the updated radio after going S-OFF.
Click to expand...
Click to collapse
Ah.. ok. That makes sense. I downloaded one that was labeled for TMO, but i will just wait until it all gets sorted out. I am not to concerned about the radio, those are always easy to flash. Was wondering if there was anything else in the firmware i needed (like when the one s got jellybean there was WIFI partitions that needed to get flashed for everything to work properly)
For anyone else that is searching for this answer, here is what i ended up doing and it worked well.
My phone came with the .7 build install (this was the very first build before any updates). I rooted, and went s-off BEFORE ANY OTA's we taken. At this point i still had the original stock rom, it was just rooted. Since I always like to at least try the newest firmware out (cause you never know what benefits it may have) I flashed the STOCK TMO recovery back onto the phone.
Now you can boot into your OS, and go through the normal OTA process that you would get in any unrooted rom. Once those updates are complete you will be on the latest firmware and ROM from TMO, but no root access. Since you still are S-OFF, you have no problems here, flash TWRP back on (or CWM, i prefer TWRP) and flash whatever you want.
Hope that helps someone else that may be looking for the same answers.
frettfreak said:
For anyone else that is searching for this answer, here is what i ended up doing and it worked well.
My phone came with the .7 build install (this was the very first build before any updates). I rooted, and went s-off BEFORE ANY OTA's we taken. At this point i still had the original stock rom, it was just rooted. Since I always like to at least try the newest firmware out (cause you never know what benefits it may have) I flashed the STOCK TMO recovery back onto the phone.
Now you can boot into your OS, and go through the normal OTA process that you would get in any unrooted rom. Once those updates are complete you will be on the latest firmware and ROM from TMO, but no root access. Since you still are S-OFF, you have no problems here, flash TWRP back on (or CWM, i prefer TWRP) and flash whatever you want.
Hope that helps someone else that may be looking for the same answers.
Click to expand...
Click to collapse
Would you mind linking the T-mobile stock recovery that you flashed? I'm in about the same situation you were in.
FYI, there is a working TMOUS RUU available now, you can download it through the following link. I downloaded it yesterday and used it last night, I can confirm it works.
http://forum.xda-developers.com/showpost.php?p=43963285&postcount=9
A few months ago I, posted a thread with a similar idea in mind however, the only answer I got was (I'm paraphrasing) "Why go back to stock,the custom ROMS are much better anyways". Well the time has come where I figure out the "why?". Yesterday I brought the phone into Wind for a check of why it's not sending MMS messages when the data is on (strangely enough it turns data on while sending the mms but, that's a story for another time). The people at Wind refused to look at my phone and told me to come back when it has stock firmware. (because, obviously I haven't returned to stock yet). Now from what I understand, from doing some research today on the forums, that the HTC Amaze (Wind Variant) has some weird software issues upon flashing a T-Mobile based ROM which I can link back to Speed Rom. So, I do the standard "Relock the bootloader and run the RUU.exe" and it just comes up with an error saying my hboot is the wrong version. The forums are pretty blank on ways to get around this (well besides going S-OFF which is a problem considering I need to bring my phone in to get the MMS issue checked. Also, I don't have that level of confidence in myself to insure I don't destroy my phone when going s-off). So, I was wondering if anyone has a fix for the issue. I'm confident that someone could possibly help me with my issue. (PS my current ROM is the latest Cyanogenmod 10 nightly, and I'm using 4ext recovery on the Amaze/Ruby).
Hope, I can get this issue resolved and thank you for helping me out with what ever problems I've had on my journey with this phone.
P.S: I didn't mean to double post the same question it's just I really needed this problem solved. I hope you can forgive me. (I fully understand if I can't return to stock under these circumstances.)
It's funny, I'm kind of in the same boat, except for 2 "minor" differences:
1) The "Smart Flash" on 4EXT never worked for me (and has consistently corrupted my internal SD card, but been able to fix it each time), so I have S-ON yet
2) I've rooted the phone itself and unlocked the bootloader, but the HBOOT is 1.93.0002, and from what I've seen, the latest firmware patch is .2222 although that really shouldn't matter
This is my 2nd HTC Amaze, and the first time I've gone through the rooting and that, took me at most an hour to complete, including time spent choosing a CMOD (I ended up with 7). This time around...I'm practically pulling my hair out because I cannot perform the S-OFF via Linux (LiveCD of course) nor starting from "square 1". I seem to be in limbo with 4EXT.
I installed Viper Amaze 1.7.2, but continually got stuck on the boot screen. Further investigation revealed that I needed to superCID the phone, which in turn would be to S-OFF first.
Additionally, I've downloaded and flashed the "stock ICS" ROM (since that was my stock ROM to begin with, naturally upgraded ICS), renamed to PH85IMG.zip yadda yadda. It recognizes and loads, but never "updates", more or less does anything after the loading bar on the bootloader.
So, just to try how much I've dug myself in with this, I've downloaded and tried 2 other ROMS, both saying "bad" (no status 7 error like the RUU flash).
I want to try out the Viper Amaze ROM since so much work and effort went into it, and it seriously looks awesome, but because my original tool that I used (HTC Super Tool) didn't require me all of these extra steps (and I didn't remember the program until now), I want to return back to stock so I can start over in a sense and complete those couple of steps that I inadvertently missed. I really feel like I'm missing something stupid.
Out of 7 Android phones that I've completed the custom ROM setup, it has to be this phone...
Anyways, tl;dr here's what I got:
Bootloader:
**Unlocked**
Ruby PVT SHIP S-ON RL
HBOOT 1.93.0002
eMMC-boot
Starting ROM: Wind Mobile ICS 4.0.3 Stock ROM
End ROM: Viper Amaze 1.7.2
Where I'm At: 4EXT, Status 7 error upon stock ROM flash. No other custom ROM works. PH85IMG.zip doesn't seem to do much upon loading via bootloader.
darkandshadow said:
Bootloader:
**Unlocked**
Ruby PVT SHIP S-ON RL
HBOOT 1.93.0002
eMMC-boot
Starting ROM: Wind Mobile ICS 4.0.3 Stock ROM
End ROM: Viper Amaze 1.7.2
Where I'm At: 4EXT, Status 7 error upon stock ROM flash. No other custom ROM works. PH85IMG.zip doesn't seem to do much upon loading via bootloader.
Click to expand...
Click to collapse
I actually have the same HBOOT version as you! I have never met a device which had more difficulties going back to stock than the Wind variant of the Amaze. Anyway best of luck on your issue, and just try to remember me if you find a way back to stock. I guess we are on the same boat and the Wind isn't helping us out *Budum Tssss* . (BTW if you manage to make it back to stock I suggest you use hasoon2000's toolkit for the Amaze. It's a good toolkit for the Amaze.)
Megapead said:
I actually have the same HBOOT version as you! I have never met a device which had more difficulties going back to stock than the Wind variant of the Amaze. Anyway best of luck on your issue, and just try to remember me if you find a way back to stock. I guess we are on the same boat and the Wind isn't helping us out *Budum Tssss* . (BTW if you manage to make it back to stock I suggest you use hasoon2000's toolkit for the Amaze. It's a good toolkit for the Amaze.)
Click to expand...
Click to collapse
I managed to install the Viper Amaze. I went back, relocked the bootloader, got a new
ID token unlock key, and reflashed (the hell out of) everything. It actually worked.
As for the Wind Rom push back, try the EXE found here on XDA:
http://forum.xda-developers.com/wiki/HTC_Amaze_4G/ROMs
darkandshadow said:
I managed to install the Viper Amaze. I went back, relocked the bootloader, got a new
ID token unlock key, and reflashed (the hell out of) everything. It actually worked.
As for the Wind Rom push back, try the EXE found here on XDA:
http://forum.xda-developers.com/wiki/HTC_Amaze_4G/ROMs
Click to expand...
Click to collapse
I tried, that EXE seems to only be for update from Gingerbread purposes or, was broke after I flashed a T-Mobile ROM on the device.
I recently purchased an Evo 3d off Ebay (and got a really good deal with many accessories included). The seller said they got it as a replacement from Sprint and Sprint told them it would be refurbished but it came packaged like it was from the factory (new box, all the accessories, ect.) and it looks like it is in mint condition. The seller claims they only used it a few weeks before they sold it. So the point is I don't know if it was refurbished or not. I do know it has hboot 1.58 on it (not sure if the original owner did the OTA update or it was sent to them like that). Here is what I want to do. First of all I am going to activate it on Net10 (like I did with my previous Evo 3D that has a bad touchscreen now). I will probably do that step last in case something bad happens to the phone during the rest of the process of what I want to do. I would like to have this phone rooted, unlocked, S-Off (from what I have been reading the most confusing part for me) then run a custom rom that optimizes the speed of the phone (possible overclocking). I also want USB OTG functionality eventually but that is not an immediate concern.
My old Evo 3D (and I do mean old) was purchased the day Sprint first released the Evo 3D and never saw an OTA update so rooting, unlocking and S-Off were not too difficult (think I used the Revolutionary method). That phone now has hboot 1.4 and I am not sure what rom because I installed it a long time ago and stuck with it since. Another thing I am wondering is if I can pull the motherboard from my old Evo and swap it into the new Evo without any hardware issues or if it would be easier to just work with the new motherboard (I would save $7 because I wouldn't have to pay a network access fee for Net 10).
What I would like from you guys is recommendations on the best way to root, unlock and s-off this new phone I have with hboot 1.58. I would also like some recommendations on what roms to try (fast, non bloated and preferably with some form of Sense is what I am looking for). I know there are a few options for getting the phone where I want it but I am unsure which is the safest and least complicated route to take that has the least risk of permanently bricking my phone. Some posts I read on different message boards say one method will work while other posts say it will not work for 1.58 so I am a little confused on this.
Well I bricked my phone. Don't worry though because I did it on purpose then I followed the instructions here (starting where it says "Downgrade/Unbrick") and that gave my phone hboot 1.4. From there I used the "revolutionary" method (took a few tries) and I now have S-Off. I am still looking for rom recommendations. Also I am wondering is there any way (or benefit) to going back to hboot 1.58 with S-Off?
xxxjdoggxxx said:
Well I bricked my phone. Don't worry though because I did it on purpose then I followed the instructions here (starting where it says "Downgrade/Unbrick") and that gave my phone hboot 1.4. From there I used the "revolutionary" method (took a few tries) and I now have S-Off. I am still looking for rom recommendations. Also I am wondering is there any way (or benefit) to going back to hboot 1.58 with S-Off?
Click to expand...
Click to collapse
Yes you can go back to 1.58. You just Need to flash it via the bootloader. I have a thread with info and downloads here: http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.hunk
You can also use an ruu: http://androidforums.com/cdma-evo-3...527-rom-update-utility-ruu-all-downloads.hunk
As for a rom recommendation, I was partial to pac rom: http://forum.xda-developers.com/showthread.php?t=2040832
I was in the same boat. Picked mine up for $30 on ebay and couldnt get htcdev.com unlock to work.
I did the brick/URT downgrade method with some help from Brian and mpgrimm2 but can also be done with the juopunutbear wire trick(which I am not familiar with).
If you are good at following instructions i put together a pretty simple guide through the user/unknownforce's ultimate recovery tool(URT) brick/downgrade method
http://forum.xda-developers.com/showthread.php?t=2794935
Negalite blurom would be a great ROM for you if you are looking for a sense rom
otto325 said:
Negalite blurom would be a great ROM for you if you are looking for a sense rom
Click to expand...
Click to collapse
That's funny you bring that up because that is the rom I chose to install and so far I'm liking it. I am still wondering if there is any advantage to going back to the 1.58 hboot though.
xxxjdoggxxx said:
That's funny you bring that up because that is the rom I chose to install and so far I'm liking it. I am still wondering if there is any advantage to going back to the 1.58 hboot though.
Click to expand...
Click to collapse
There's no advantage. All the bootloader upgrade really does is patch s-off methods.
You'll need 1.58 for most ics roms though. And 1.50 or below for jellybean roms.