Hi XDA,
As i'm reverting back to Stock, I decided to download the earliest release of the DHD rom I could find. I ended up downloading the '1.24.405.1' version of the software, and on flashing the RRU, rather than a picture of the phone appearing a message said 'For Testing Purposes Only, Not For Shipping' or something along those lines. After flashing I went to the OTA Update however there are no updates available for my device, which is odd as the ROM is from October 10, and there have been many OTA's since then? This is the file I downloaded.
RUU_Ace_HTC_WWE_1.24.405.1_Radio_12.27.60.14b_26.02.00.29_M4_release_151852_signed
I got it from Shipped-Roms, all help is appreciated.
Because it's a test rom, you should have chosen the 1.32... version from this thread
Hawks556 said:
Because it's a test rom, you should have chosen the 1.32... version from this thread
Click to expand...
Click to collapse
Thanks, solved.
Related
Just checking. I just went from MyFroYo6 to SlideM and I received a notification saying there is new firmware available.
Is this actually brand spankin' new firmware or was I not getting this notification because I was running MyFroYo6, Cyanogenmod, and Team Fenix?
Sleef said:
Just checking. I just went from MyFroYo6 to SlideM and I received a notification saying there is new firmware available.
Is this actually brand spankin' new firmware or was I not getting this notification because I was running MyFroYo6, Cyanogenmod, and Team Fenix?
Click to expand...
Click to collapse
No....You need to update to CR's OTA which is the latest..Slidemeroot is based off of a older version of the firmware.CR's OTA also has the newer radio(which may give better batt,signal,etc..)
I thought I had installed his OTA. Not the ROM but the essential files. Did I undo this by going back to SlideM?
Sleef said:
I thought I had installed his OTA. Not the ROM but the essential files. Did I undo this by going back to SlideM?
Click to expand...
Click to collapse
If you wiped I would say so. But shouldn't if you just flashed a nandroid backup.
But, my wife is running SlidemeRoot5 and received the update notification. We allowed it to update and it didn't really do anything, and she didn't lose root. But as usual, yymv.
Sleef said:
I thought I had installed his OTA. Not the ROM but the essential files. Did I undo this by going back to SlideM?
Click to expand...
Click to collapse
But you changed roms to an older ver, you still have the same radio but that roms is older. The tmo update server reads the phone as needing an update.
Right on! I was just revisiting the Sense apps. I missed the copy/paste feature and Dragon Dictation. Nandroided back to MyFroYo6 after getting a 281 benchmark score. (Yes, I also noticed the slowness myself.)
Thanks for the answers, y'all. Just saw Megadeth, by the way.
Had 4.1.1 rooted with CWM. Phone downloaded a 600MB update file. Got some sort of error part way through. Flashed stock recovery back. Let phone download OTA update. Stopped half way through the flash and aborted. No error, rebooted before I could see one - just said that it was interrupted or something after rebooting. Go to check for updates and it says the phone is up to date, however about shows 4.1.1! Kernel though is showing SMP Preempt Nov 20 date so that's go to be something new.
I noticed on Kies it says 4.1.1 is the latest version! I know 4.3 had a lot of bugs initially. Is AT&T still chickening out on this for now and all the msgs I see about 4.3 OTA update are before AT&T stopped it? Or somet issue with my phone.
I'm about to just do back to CWM, move to CM11 nightly and roll the dice on having to deal with bugs and other funky stuff. But then stability is my #1 priority so maybe just stay on 4.1.1. Can't be right as I thought there was a 4.1.2 even?? (I had the update app frozen via TI so I never bothered with the OTA updates.)
*** shoots straight into your head ***
Dead, yet ?
There's a flashable zip of the official 4.3 update in the development thread. I would recommend the no knox prerooted version though because the other version is apparently "unrootable" right now.
jazee said:
Had 4.1.1 rooted with CWM. Phone downloaded a 600MB update file. Got some sort of error part way through. Flashed stock recovery back. Let phone download OTA update. Stopped half way through the flash and aborted. No error, rebooted before I could see one - just said that it was interrupted or something after rebooting. Go to check for updates and it says the phone is up to date, however about shows 4.1.1! Kernel though is showing SMP Preempt Nov 20 date so that's go to be something new.
I noticed on Kies it says 4.1.1 is the latest version! I know 4.3 had a lot of bugs initially. Is AT&T still chickening out on this for now and all the msgs I see about 4.3 OTA update are before AT&T stopped it? Or somet issue with my phone.
I'm about to just do back to CWM, move to CM11 nightly and roll the dice on having to deal with bugs and other funky stuff. But then stability is my #1 priority so maybe just stay on 4.1.1. Can't be right as I thought there was a 4.1.2 even?? (I had the update app frozen via TI so I never bothered with the OTA updates.)
Click to expand...
Click to collapse
jukiewalsh said:
There's a flashable zip of the official 4.3 update in the development thread. I would recommend the no knox prerooted version though because the other version is apparently "unrootable" right now.
Click to expand...
Click to collapse
Jazee, I read your posts on why you chose to try 4.3. I did what jukiewalsh recommends & have 4.3 as a stable DD.
This only works if your bootloader remains on 4.1.2 or less!
Posted some detail in these 2 posts:
http://forum.xda-developers.com/showthread.php?p=48303313#post48303313 #264
http://forum.xda-developers.com/showthread.php?p=48550720#post48550720 #875
jukiewalsh said:
There's a flashable zip of the official 4.3 update in the development thread. I would recommend the no knox prerooted version though because the other version is apparently "unrootable" right now.
Click to expand...
Click to collapse
I took a quick look and qasn't sure what thread you are referring to?
I'm guessing this one:
http://forum.xda-developers.com/showthread.php?t=2498233
But aside from having a pre-root pre-no knox version how does this one compare to this one?
http://forum.xda-developers.com/showthread.php?t=2387423
Are both of these buggy and that's why AT&T stopped pushing out the update?
jazee said:
I took a quick look and qasn't sure what thread you are referring to?
I'm guessing this one:
http://forum.xda-developers.com/showthread.php?t=2498233
But aside from having a pre-root pre-no knox version how does this one compare to this one?
http://forum.xda-developers.com/showthread.php?t=2387423
Are both of these buggy and that's why AT&T stopped pushing out the update?
Click to expand...
Click to collapse
I'm pretty sure that is the difference, that it's pre-rooted and insecure. As the second one's title says it's a "one way road". If you have any plans on rooting or installing a custom rom in the future I wouldn't do the second one because currently I think it's hard to root. The other one is essentially like flashing a custom rom so you can still switch between other ones or flash a kernel if you ever decide to. And I haven't tried the 4.3 TW yet so I can't attest to the bugginess
Hi everyone!
I recently unlocked my bootloader and rooted my m8.
I tried using firewater to "s-off" my phone and unfortunately, it did not work out. The way I understand it, I cannot install stock ROMs (such as the 5.0.1 GPE) without "s-off." Now, I want to unroot my phone and stick to waiting for the OTAs to roll out instead.
I followed the instructions in the "returning to stock" thread and noticed that I have no version main (see attached image). I looked around the forums and saw that the advice was to flash the latest TWRP version. Since I'm stuck with a phone that I cannot update, I'm trying to be careful now. Can anyone please confirm if flashing the latest TWRP will bring my version main back?
The noob in me also has a few questions/requests as well:
1. Since my phone is rooted, I cannot receive OTA updates and upgrade to lollipop once these updates roll out?
2. Please tell me which files to download to return to stock. Just trying to be really careful this time around.
3. Lastly, is it also true that I can only install custom ROMs once have rooted? As to stock ROMs, I can't install them until I get "s-off"?
Thanks a lot, everyone! Cheers!
panchizzles said:
Hi everyone!
I recently unlocked my bootloader and rooted my m8.
I tried using firewater to "s-off" my phone and unfortunately, it did not work out. The way I understand it, I cannot install stock ROMs (such as the 5.0.1 GPE) without "s-off." Now, I want to unroot my phone and stick to waiting for the OTAs to roll out instead.
I followed the instructions in the "returning to stock" thread and noticed that I have no version main (see attached image). I looked around the forums and saw that the advice was to flash the latest TWRP version. Since I'm stuck with a phone that I cannot update, I'm trying to be careful now. Can anyone please confirm if flashing the latest TWRP will bring my version main back?
The noob in me also has a few questions/requests as well:
1. Since my phone is rooted, I cannot receive OTA updates and upgrade to lollipop once these updates roll out?
2. Please tell me which files to download to return to stock. Just trying to be really careful this time around.
3. Lastly, is it also true that I can only install custom ROMs once have rooted? As to stock ROMs, I can't install them until I get "s-off"?
Thanks a lot, everyone! Cheers!
Click to expand...
Click to collapse
Your firmware version: 3.32.708.4
I got it from your radio (baseband) number.
xunholyx said:
Your firmware version: 3.32.708.4
I got it from your radio (baseband) number.
Click to expand...
Click to collapse
Thanks for the reply!
Do I have to flash the latest TWRP version before proceeding?
Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376
jfreshh330 said:
Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376
Click to expand...
Click to collapse
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triangle deal.
So try and find one thats a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the T-Mobile files. As mentioned though, just make sure the stock recovery is from Android 4.4.X or 5.X.X and you will be fine.
flexfulton said:
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triange deal.
So try and find one that a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the AT&T files. As mentioned though, just make sure the stock recovery in from Android 4.4.X or 5.X.X and you will be fine.
Click to expand...
Click to collapse
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.
jfreshh330 said:
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.
Click to expand...
Click to collapse
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!
flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
Click to expand...
Click to collapse
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?
flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!
Click to expand...
Click to collapse
Awesome thanks so much!
jfreshh330 said:
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?
Click to expand...
Click to collapse
Sideload the latest recovery as found in the thread I linked to above. Reboot and the OTA should take no problems. It was downloading and everything fine for you before but was unable to flash because of an outdated recovery you installed.
So my recommened method to update OTA, is to follow the first route you were taking but with the newest recovery.img file in place of what you used in step 1.
If you already have the OTA downloaded on your phone, you shouldn't have to download it again either. It should see that it's already downloaded ready to be installed.
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
jfreshh330 said:
Awesome thanks so much!
Click to expand...
Click to collapse
No problem. Let me know how it turns out for you.
If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).
redpoint73 said:
If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).
Click to expand...
Click to collapse
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.
flexfulton said:
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Click to expand...
Click to collapse
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
flexfulton said:
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.
Click to expand...
Click to collapse
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.
redpoint73 said:
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.
Click to expand...
Click to collapse
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.
flexfulton said:
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Click to expand...
Click to collapse
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
flexfulton said:
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.
Click to expand...
Click to collapse
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.
redpoint73 said:
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.
Click to expand...
Click to collapse
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
I was trying to help out as I had the same issue when I went to update. I installed a recovery that was too old, determined that I needed to flash a recovery from either 4.4.X or lollipop and my OTA update was fine after that. Point being, I could go ahead and flash a newer recovery to get the OTA to download.
Anyway I applogize if I was in error in my help. No one else was helping and based on my own experiences it sounded like the same issue.
flexfulton said:
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
Click to expand...
Click to collapse
OTAs will normally only allow you to install from the immediate previous version (you cannot skip a version). Sometimes they are complete packages; but often they are not. Sometimes the OTA just contains what has been changed; basically a "patch". And for that reason, the updates need to be installed sequentially. In fact, I've seen folks brick due to unwittingly installing partial firmware packages from OTAs (with s-off, which bypasses such safety checks).
flexfulton said:
Anyway I applogize if I was in error in my help.
Click to expand...
Click to collapse
There's no need to apologize. As you are well aware, this is a self-supporting community that flourishes due to the contributions of its members. Your answers may not have been 100% correct. But it was well intended; and you answered to the best of your knowledge. At least you learned something and can pass it along now. I'm just a member who passes along what I've learned here also (don't have any specialized developer knowledge or anything); and I'm certainly not right all the time.
So the recovery 3.32.5312 will not work? And i apologize i am on 4.4.4 not 4.4.2
Hello,
I updated my HTC One M8 first time since I first buy the phone. My Original ROM was 4.4.2 and I updated to 4.4.4 (OTA update ATT). I rooted phone and did S-OFF. But recently I changed ROM back to 4.4.2 using hard reset and install back very first original factory ATT Rom (4.4.2). Now when try to update my ROM through ATT OTA, it gives me message to "Wait (24 Hrs)" I already wait for 4 days, clicking back on Software Update. Also my MMS service is not working ( My MMS service was working before with both 4.4.2 and 4.4.4).
My questions is " Is there anything which I have to wipe or clear to make it completely fresh like brand new first time OS ?"
Thank you so much for reading my post!
Since you have an AT&T branded M8, and are S-off, you can just use a RUU to switch versions. No need to take an OTA (other than to preserve data, but it sounds like that isn't an issue if you have already downgraded)
The most recent is here: http://www.htc.com/us/support/rom-downloads.html
Older versions are available, but I don't have a direct link for them.
jshamlet said:
Since you have an AT&T branded M8, and are S-off, you can just use a RUU to switch versions. No need to take an OTA (other than to preserve data, but it sounds like that isn't an issue if you have already downgraded)
The most recent is here: http://www.htc.com/us/support/rom-downloads.html
Older versions are available, but I don't have a direct link for them.
Click to expand...
Click to collapse
I would appreciate if you can attach link for 4.4.4 RUU file or .zip file(Install from TWRP). I dont like Marshmallow.
Check AT&T General section forum... it is available under stickied thread