Hi, I just go back from getting my new 3D, and while the sprint rep was activating it and making sure it worked, he mentioned it would take a minute to update.. But then later mentioned it would take quite awhile to update and showed me where to download the updates.
Whats the none updated software version? :[
It really depends on how new the phone is, its most likely 2.08.651.3.
Dont update if you want to root it
Any new EVO 3d (not refurbished) will " likely " have firmware newer than 2.08.651.2 and Hboot 1.50/S-On (bootloader). The latest fw is 2.17.651.5 which got.a new radio than the others. The new base requires roms that use the same base/kernel. Kernel source isn't released so there are only some minor tweaks for it (freeza's kernels are updated).
If you have the above setup, you can certainly go ahead with the update. You have to use HTC's half-assed Unlock method and do most of your flashing via fastboot command prompt.
See the top link in my signature for details.
Sent from my PG86100 using Tapatalk
Related
I flash one of the new ICS roms and it cant load into it. it boots up properly and everything and when it reaches the lockscreen it freezes and reboots. and it keeps doing that. Whats going on id really like to switch over to ICS already. Im on my 3VO CDMA with Hboot 1.50 S-ON unlocked via HTC. and im currently using Meanrom 4.2 as my daily. if that means anything.
Sinerr said:
I flash one of the new ICS roms and it cant load into it. it boots up properly and everything and when it reaches the lockscreen it freezes and reboots. and it keeps doing that. Whats going on id really like to switch over to ICS already. Im on my 3VO CDMA with Hboot 1.50 S-ON unlocked via HTC. and im currently using Meanrom 4.2 as my daily. if that means anything.
Click to expand...
Click to collapse
lots of discussion about this
for your phone to boot a REAL linux 3 kernel, your ADSP firmware needs to be updated.
you can try just flashing ADSP via hboot (AT YOUR OWN RISK)
there are firmware packages around that are for virgin mobile. some people have problems with it, some dont - i personally didnt.
you can try to delete everything from the firmware zip except adsp... (again AT YOUR OWN RISK)
it is unknown if ADSP itself needs the other firmware to be updated or not.
it is also unknown if the rom itself is dependent on the other firmware images inside the zip.
search around here, you cant miss the discussions about the this firmware package - since ur flashing a virgin mobile firmware package onto a sprint phone..there "may" be issues. research, and flash at your own risk.
what i do know for 100% is this:
adsp.img is a md5 match for what is on my sprint phone that i did not flash the virgin mobile firmware on - so adsp is good for sprint
i cant repeat this enough: i DO NOT KNOW if adsp will require, want, or need any, some, or all of the other firmware images in the zip file.
I have a rooted and S-on Evo. The RUU keeps failing, even after I unrooted via the Superuser app.
Keep getting “ERROR [155]: UNKNOWN ERROR” and then it says it can not update the phone.
And then “Please get the correct ROM update utility and try again.”
I am definitely using the correct RUU version. 1.22.651.3.
Also I have tried two different computers and two different USB cables.
Does anyone know how to get this thing working?
if you updated to the latest OTA update; that usually updates your radios and your Hboot which means the old RUU won't work because it has an OLDER HBoot and radios. Your gonna have to wait till the new OTA becomes available as an RUU to be able to go back to stock.
if you didn't take the OTA 2.13 and you are still on 1.22 then try putting your phone on Fastboot and try it that way.
Edit: Ok so it looks like the latest RUU has been uploaded. Look here http://www.filefactory.com/f/b6eb73c80cc97030/
Thanks, I will try fastboot.
However, as I said in the OP, I am on the same version (1.22.651.3) as the RUU I am using...
ronnienyc said:
I have a rooted and S-on Evo. The RUU keeps failing, even after I unrooted via the Superuser app.
Keep getting “ERROR [155]: UNKNOWN ERROR” and then it says it can not update the phone.
And then “Please get the correct ROM update utility and try again.”
I am definitely using the correct RUU version. 1.22.651.3.
Also I have tried two different computers and two different USB cables.
Does anyone know how to get this thing working?
Click to expand...
Click to collapse
I ran into the same error 155 issue.
I found the solution and it's quite simple. In the instructions to unroot, they forget to mention that you MUST relock your bootloader (instructions below). Once you relock it, then you can run the RUU for 1.22.651.3.....after that, take the stock OTA update.
http://www.theandroidsoul.com/how-to-re-lock-htc-one-x-bootloader/
It helps to have HTC Sync installed too
Sent from my EVO using Tapatalk 2
Is there another site with the new ruu?
Sent from my EVO using Tapatalk 2
running "fastboot oem lock" yields "waiting for device," and this stays on the screen forever. It doesn't work...
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Hypeo said:
It helps to have HTC Sync installed too
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Correct - this is an important step too. HTC Sync must be fully installed, drivers and all.
---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------
ronnienyc said:
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Click to expand...
Click to collapse
Congrats!
That's my plan, except I'm keeping the stock ROM. If you find a way to Root, let me know - I tried RegawMOD, but I could not get it to work
ronnienyc said:
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Click to expand...
Click to collapse
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
ronnienyc said:
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Click to expand...
Click to collapse
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
Rxpert said:
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
Click to expand...
Click to collapse
I suggest no OTA as well!
Rxpert said:
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
Click to expand...
Click to collapse
That's not always true, and almost all new major releases come with a new hboot. In fact I can't remember any updates on my 0g evo, evo 3d, and evo LTE, that didn't come with a new hboot. The fact of the matter is, people that are s-on and hboot 1.15 won't be able to upgrade their radios and firmware unless they take the ota or run the ruu. This update makes the phone fly and is worth it.
On the other post, regaw mod does work with unlocking and installing twrp, you will have to install a rooted rom afterwards though because regaw mod fails at the rooting step.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
The fact of the matter is, people that are s-on and hboot 1.15 won't be able to upgrade their radios and firmware unless they take the ota or run the ruu. This update makes the phone fly and is worth it.
On the other post, regaw mod does work with unlocking and installing twrp, you will have to install a rooted rom afterwards though because regaw mod fails at the rooting step.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
Sweet this is actually the point where I'm at. HTC Dev unlocked, s-on, hboot 1.15 and rocking twrp. I've been trying to parse through all of the numerous posts on a method to go ahead and install the ota updates. I actually believe I'm 2 down as I haven't updated ever and I got the phone @ launch. I recall reading somewhere that just going back to the stock recovery is a viable option if I want to go w/ the ota updates. I don't really have any interest in different ROMs (I scratch that itch w/ my evo 3d).
tl;dr Whats the least painful way to install the OTA updates post HTC Dev unlock, s-on, twrp recovery, and hboot 1.15?
I have a new HTC One that doesn't have the August OTA update. I've used revone for S-OFF and unlock (agian, unlock from revone, not htcdev.com) and am getting ready to root and apply a custom ROM.
But, before I do that, I want to find out how I can get the most current firmwares/radios/etc from the OTA update, without sacrificing root/unlock capability. I'm not sure the best way to do it given that I have S-OFF and unlock via revone, and what files I need to get, beyond the radio.
^^^
Bump. I'm perm rooted, unlocked, s-off with custom recovery but still on hboot 1.44 and software is 1.26.502.12. I'd like to update my firmware too. Is there a suggested RUU or stock ROM for the m7att?
edditnyc said:
^^^
Bump. I'm perm rooted, unlocked, s-off with custom recovery but still on hboot 1.44 and software is 1.26.502.12. I'd like to update my firmware too. Is there a suggested RUU or stock ROM for the m7att?
Click to expand...
Click to collapse
I might be able to help you here. I went through all of this yesterday.
DISCLAIMER: IF YOU BREAK YOUR STUFF, IT'S NOT MY FAULT AND I PROBABLY WON'T BE ABLE TO HELP YOU FIX IT. DO ANY OF THIS AT YOUR OWN RISK AND DO YOUR OWN RESEARCH I still consider myself and Android newb (big time) as this is only my 3rd day into modding.
Go to this post: http://forum.xda-developers.com/showthread.php?t=2365506
Halfway down the first post is the "Firmware Flashing" section where you can download all the bases. Note that 3.06.1700.10 is the GE base and 3.09.401.1 is an early leak of the 4.3 base expected with the 4.3 Sense release . All but the GE one are labelled custom although I don't know what's custom about them to be honest. Also there is a link to HBOOT 1.44, get that.
I flashed all of them in order, except the (GE one) like this: 2.17.401.1-> 2.24.401.1 -> 2.24.401.8 -> 3.09.401.1
Why did I skip the GE one? Solely because the .ZIP didn't say "custom". I have no idea what is custom on it. There really shouldn't be anythin gin that GE base that would do anything bad, and thus probably no reason to not flash that one before 3.09.401.1, but I didn't, so just telling you my experience as it occurred.
!!! This will upgrade HBOOT as you go if you use the files as-is !!! (As I recall, 2.24.401.1 went to HBOOT 1.44 and 3.09.401.1 to HBOOT 1.55)
Since you are S-OFF, you can just downgrade back to HBOOT 1.44. Or, to prevent the upgrade in the first place, you can extract each zip and replace the hboot_signedbyaa.img from within each .ZIP with the HBOOT 1.44 download. Then just re-zip the file and flash it. I ended up downgrading back to HBOOT 1.44 because you can S-OFF it if you need to set yourself S-ON again for some reason.
!!! Also important, this process made my touchpanel stop working on the JB 4.1.2 stock ROM !!!!! I believe this is because the touchpanel update included in 2.24.401.1 requires JB 4.2.2, which AT&T has not pushed out for the HTC One, but it is available on International models. So, if you have no intention to put on a custom ROM that is 4.2.2 (even the international one) or 4.3, then you need to remove the touchpanel update file (tp_SYN3202.img) from all of the firmware.zip before flashing.
If you already have a 4.2.2/4.3 ROM, then leave the touchpanel file in there.
If you are JB 4.1.2 and plan to immediately go to JB 4.2.2 or 4.3, then you can update the touchpanel even though it will make it not work in JB 4.1.2. Why? When you boot into custom recovery, the touchpanel itself will work (at least with TWRP 2.6.1.0, which is what I have running). I don't know if CWM Touch will work in this scenario, but you can use the physical keys for that one. But anyway, the point here is that you can update the touchpanel then immediately flash a new ROM and the touchpanel will work again. This saves you a step of having to update the touchpanel after the new ROM.
Something else to keep in mind is Radio's. The Radio's will upgrade with these bundles and you will end up with a radio different than AT&T's newest radio. My personal opinion is to stick with the newest AT&T release radio, which you can download here: http://forum.xda-developers.com/showthread.php?t=2419699 - The one labelled AT&T latest is a flashable .ZIP you can load in custom recovery. Or you can extract the ZIP and copy radio.img over to your firmware bundles if you want it to just put in the latest radio with the rest of the firmware. You can also flash radio.img in fastboot with "fastboot flash radio radio.img".
Some people are saying the 3.09.401.1 is a little buggy. I'm not actually using my HTC One for anything but playing with ROM's right now. I'm using another phone as primary device still, so I can't provide any comments. You may want to stick with the 2.24.401.8 base which is the latest for 4.2.2 builds. That base will work fine with a 4.3 based ROM.
As for me, I currently have the 3.09.401.1 base but with the latest AT&T release radio and HBOOT 1.44 in place of what's in the original bundle download.
Greetings,
I apologize if this is dumb, but I have been away a while, and am fairly new to this scene as is.
A few months ago, I flashed my EVO 4G LTE to 1.13.651.1 710 RD with root s-off and HTC sense. Since that time, Sprint has released OTA updates that flash the phone to the most recent HTC rom (3.16.651.3 I believe).
I would like to upgrade, even if I have to lose root, but naturally a full featured solution is better.
I can't OTA update, and that just puts me into TWRP, not to surprising. I would like to know how to get the latest update without bricking anything. As it's been almost 8 months since 3.16.651.3, you can sort of tell how cautious I am.
I wouldn't say no to a non Sense (pun not intended, but kept) rom, but I have heard those cause issues with various parts of the EVO 4G LTE's hardware, and I would like the phone to remain fully functional.
What is the best option. I'm leaving this fairly open for everyone's superior expertise.
IF you are indeed S-OFF and just HTC-Dev unlocked you can update your firmware manually then flash whatever rom you wish.
And you're gone lol
Whoops. Nevermind the s-off.
I'm tampered unlocked and "JEWEL PVT SHIP S-ON RL" with
HBOOT 1.12.0000
Radio 1.02.12.0427
OpenDSP-v25.1.0.32.0405
I'm still looking for the safest way to get to the latest HTC sense, or any android version that won't reduce functionality of my phone hardware. My brother tried Cyanogen on his phone a while back, but he went back to sense after issues with his voicemail.
If you want the latest firmware you'll have to go back to stock using RUU or get S-OFF and manually flash the latest firmware. With your setup I would go for S-OFF and manually flash the latest firmware. You can find three different ways to get S-OFF in the HTC EVO 4G LTE Original Android Development section (they're stickied at the top). A little reading should tell you which version will work best for your setup between Moonshine, Facepalm, and DirtyRacun.
Once you're S-OFF you can update your firmware on your own. Captain_Throwback has a link to the zip file in his signature (It's the link for the Evo 4G LTE Baseband: 1.12.11.1210).
You'll be S-OFF with the latest firmware and you'll be ready to flash any of the latest ROMs.
Best thing to do is get S-off, as stated above. You can use Facepalm or Dirty Racun to accomplish that. Facepalm is the easier of the two and takes about five minutes or so from start to finish. After that you can update your firmware and flash a JB ROM. If you click on the link in my sig you'll find instructions on how to update your firmware, as well as a link to Captain Throwback's firmware thread.
I have a rooted and soff EVO LTE and in wanting to up to 4.3 ROM I understand I need to update my bootloader. When I try loading a couple 4.3 roms my phone starts ups but reboots after displaying the HTC white logo screen.
I currently have hboot 1.19.0000 and if I understand correctly I need to update to 2.10 It also has Team Win Recovery 2.2.1 which I'm not sure if that needs updating or not.
It has been awhile since I rooted or updated anything and when I did in the past I followed instructions for the entire root process so I'm a little stuck in getting things patched up.
Can anyone offer me the path to proceed? I'm only messing with my old phone as I plan to reactivate it as I'm having terrible issues with my new HTX M8 in not having any data nor able to make calls (due to the Spark support in my local towers throwing chucks since Sprint doesn't have their towers upgraded yet.
Perhaps I should ask, am I on the right path in needing to update my hboot to update to 4.3?
eBoyDog said:
I have a rooted and soff EVO LTE and in wanting to up to 4.3 ROM I understand I need to update my bootloader. When I try loading a couple 4.3 roms my phone starts ups but reboots after displaying the HTC white logo screen.
I currently have hboot 1.19.0000 and if I understand correctly I need to update to 2.10 It also has Team Win Recovery 2.2.1 which I'm not sure if that needs updating or not.
It has been awhile since I rooted or updated anything and when I did in the past I followed instructions for the entire root process so I'm a little stuck in getting things patched up.
Can anyone offer me the path to proceed? I'm only messing with my old phone as I plan to reactivate it as I'm having terrible issues with my new HTX M8 in not having any data nor able to make calls (due to the Spark support in my local towers throwing chucks since Sprint doesn't have their towers upgraded yet.
Perhaps I should ask, am I on the right path in needing to update my hboot to update to 4.3?
Click to expand...
Click to collapse
I think never mind, after more reading I believe my problem is I don't have s off which appears to be required, let me get that done and I will see were I'm at......
You can run the RUU for the latest update (Android 4.3). That will get you the latest bootloader and put you on the new partition layout, also. You will only be able to flash ROM's based on the new layout. You'll need to update your recovery version, also. For the RUU click the top link in my sig and scroll down to the bottom of the first post. You'll need to relock your bootloader to run the RUU. Running the RUU does not require S-off and there are instructions in the post I mentioned that detail how to run the RUU.
You should also read the first several posts in the thread linked below:
http://forum.xda-developers.com/showthread.php?t=2639180
Sent from my HTC M8