Hi everyone, I'm Josh and I'm a long time reader of XDA. I'm really struggling with the next steps on my HTC one despite reading ton's of information on XDA and many other sources. I could use some help / clarification.
I recently purchased an HTC One m7 ATT version. I've rooted, installed SuperSU, TWRP and unlocked the phone. I was stuck on choosing a rom but I've hit a new snag. I was going to try ViperOne but noticed they insist you install the latest firmware updates first. Here's where I'm lost. I'm running the stock version that came with my phone when it was locked.
Kitkat 4.4.2, Sense 6
FW# - 5.12.502.2
Hboot - 1.57
Radio - 4m.27.3218.14
I can't seem to get the OTA's, how do you get OTA's, do you have to run official att service sim like gophone? Or can you use straight talk like I currently have? Or do you not even need a sim for OTA's? I don't currently have a sim in the phone, was waiting to get all this sorted first. Will OTA's break root? Would it be beneficial to turn the phone into international version to get OTA's faster and would I lost the 4g lte abilities of phone if I did this?
How do I go about putting these firmware updates on, is s-off required even if you use a signed RUU from "androidruu dot com" for example?
I would like to get the latest official firmware releases on the phone and get it updated to kitkat 4.4.4 from the official releases and then put a custom rom on of my choice.
Is any of this even necessary? Are firmware updates included with the Rom's? How is an RUU different than a rom?
Someone, if possible please help me get this all sorted out, I'm so confused, it would be very much appreciated. Thanks!
jpcreativeimagery said:
I recently purchased an HTC One m7 ATT version. I've rooted, installed SuperSU, TWRP and unlocked the phone. I was stuck on choosing a rom but I've hit a new snag. I was going to try ViperOne but noticed they insist you install the latest firmware updates first. Here's where I'm lost. I'm running the stock version that came with my phone when it was locked.
Kitkat 4.4.2, Sense 6
FW# - 5.12.502.2
Hboot - 1.57
Radio - 4m.27.3218.14
I can't seem to get the OTA's, how do you get OTA's, do you have to run official att service sim like gophone? Or can you use straight talk like I currently have? Or do you not even need a sim for OTA's? I don't currently have a sim in the phone, was waiting to get all this sorted first. Will OTA's break root? Would it be beneficial to turn the phone into international version to get OTA's faster and would I lost the 4g lte abilities of phone if I did this?
Click to expand...
Click to collapse
You wont get OTA's unless you are stock, you can use this to get back to stock: http://forum.xda-developers.com/showthread.php?t=2775650 to be able to receive OTA updates.
jpcreativeimagery said:
Are firmware updates included with the Rom's? How is an RUU different than a rom?
Click to expand...
Click to collapse
No firmwares are never included in ROMs, and RUU reset your phone (both firmware and ROM) to fully stock, but you would need an RUU with same or higher version that you are on now. (with S-ON)
what is latest att firmware
@clsA, nkk71 and I have been talking on the #AndroidRevolution irc channel, we/I am trying to get this resolved to figure out if I need s-off in order to grab latest firmware's before I apply a custom rom because it seems att is way behind everyone else since the rest seem to be 6.0.something. Can you confirm what latest att firmware # is for htc one via their software update on the phone? I have reset phone to stock but it's still stuck on 5.12.xxx.xx (whatever the # is, don't remember right now) and claiming it's up-to-date, trying to figure out if boot-loader also has to be locked in addition to stock rom and stock recovery and root removed (cause I did all that but left bootloader unlocked), I've been reading that it does, but neither of us can confirm this. And do you need official att sim/service to do the updates? Additionally, could you direct to a list of signed firmware updates for flashing with s-on if this is not the latest firmware. Thanks!
clsA, just fyi, he used your Guru Reset ROM 5.12.502.2
but doesnt get any OTA updates
I tried it, but since i'm not on ATT, it doesnt even accept my device
nkk71 said:
clsA, just fyi, he used your Guru Reset ROM 5.12.502.2
but doesnt get any OTA updates
I tried it, but since i'm not on ATT, it doesnt even accept my device
Click to expand...
Click to collapse
@jpcreativeimagery
Well that may be because their have been no updates since that release
http://www.htc.com/us/support/htc-one-att/news/
clsA said:
@jpcreativeimagery
Well that may be because their have been no updates since that release
http://www.htc.com/us/support/htc-one-att/news/
Click to expand...
Click to collapse
aha :laugh:
quick question though.... seems ATT has it's own software update "solution"? flashed your Guru Reset ROM, and gave me "Device not provisioned" (or something like that), and the system update is not the usual htc system updated... weirdish (well, at least for me)
thanks bud
nkk71 said:
aha :laugh:
quick question though.... seems ATT has it's own software update "solution"? flashed your Guru Reset ROM, and gave me "Device not provisioned" (or something like that), and the system update is not the usual htc system updated... weirdish (well, at least for me)
thanks bud
Click to expand...
Click to collapse
Yes they do and you have to be on their network to even download the update on Wifi
clsA said:
Yes they do and you have to be on their network to even download the update on Wifi
Click to expand...
Click to collapse
nasty
nkk71 said:
nasty
Click to expand...
Click to collapse
Well their are enough working RUU + OTApkg.zip you don't really miss much
latest firmware
clsA said:
Well their are enough working RUU + OTApkg.zip you don't really miss much
Click to expand...
Click to collapse
@clsA, do you know of thread that list the latest firmware updates for flashing to an ATT M7_UL with s-off? I'm going to s-off the phone and bite the bullet with sunshine so i can take advantage of the latest firmware with a custom rom since ATT is so slow/behind with the software/firmware updates.
Thanks again for all your help and let me know.
jpcreativeimagery said:
@clsA, do you know of thread that list the latest firmware updates for flashing to an ATT M7_UL with s-off? I'm going to s-off the phone and bite the bullet with sunshine so i can take advantage of the latest firmware with a custom rom since ATT is so slow/behind with the software/firmware updates.
Thanks again for all your help and let me know.
Click to expand...
Click to collapse
Sure ... I recommend converting to the Developers edition for the most updates
after your s-off Change your CID fastboot oem writecid BS_US001
then flash this RUU >> http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353887_signed_3.exe
And then you can take OTA updates up to the current 6.07.1540.2 (3 updates I think)
I'm uploading the file's I used Here >> https://www.androidfilehost.com/?w=files&flid=24178
Their is also a RUU now from HTC >> http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe
bricked / boot hang / fixed with reset
clsA said:
Sure ... I recommend converting to the Developers edition for the most updates
after your s-off Change your CID fastboot oem writecid BS_US001
then flash this RUU >>
And then you can take OTA updates up to the current 6.07.1540.2 (3 updates I think)
I'm uploading the file's I used Here >>
Click to expand...
Click to collapse
@clsA, thank you so much for that, I actually ended up following @vomer 's guide and turning it into super CID because it seemed that the firmware updates were newer than the developer ones oddly enough, 6.0.9 and 6.0.9.xxx.10 and then there's 6.0.9.xxx.11 and .12 but this is where i hit a snag, all went smoothly using vomers firmwares up till 6.0.9.xxx.10 but then i tried to flash the .11 and .12 from ARHD and the device bricked/ hangs on boot....ended up having to use adb push to get your reset on there and reset the device, flash the original firmware etc...phone is working again (I was tempted to panic but maintained control ;P) but ultimately means i wasted a bunch of time only to have start over again....for now I've left it 5.12 and stock....maybe you could help figure out what went wrong when you get a chance.
Thanks.!
i left recovery and root on during the reset just in case it didn't work but did flash back the stock radio for that rom as well
jpcreativeimagery said:
i left recovery and root on during the reset just in case it didn't work but did flash back the stock radio for that rom as well
Click to expand...
Click to collapse
Theirs nothing wrong with the Stock 5.12.502 firmware from AT&T in fact it's one of the most stable. You can flash mostly any rom you want with that firmware installed. The reason I recommend the Developer edition right now is because Lollipop+Sense is due out any day now on that model.
how to proceed
clsA said:
Theirs nothing wrong with the Stock 5.12.502 firmware from AT&T in fact it's one of the most stable. You can flash mostly any rom you want with that firmware installed. The reason I recommend the Developer edition right now is because Lollipop+Sense is due out any day now on that model.
Click to expand...
Click to collapse
@clsA, I was bent on the firmware update to take advantage of latest enhancements with ARHD and they recommended at least v6 xxx .11 eventhough the rom is based on v6 xxx.12, viperone also strongly advised latest firmware updates....does the developer versions you sent me have the calling fix for when the audio in the call was lost because of google update? Also, quick question, why did you include the 4 xxx something base firmware...i can just proceed with the CID change and start at the 6 series firmwares because I'm already at later version with att stock 5.12 right?
Any idea what happened the other night with the bricking - would boot, hang on black screen after first htc logo on white background and then just have the hardware touch buttons lit....was it because the firmwares ARHD posted required the bootloader to be re-locked? (failed to notice this until after I had semi-bricked it)
Also, what backup app would you recommend? looking to restore all my apps and settings after these wipes etc...getting tired of redoing it all again each time.
Thanks!
jpcreativeimagery said:
@clsA, I was bent on the firmware update to take advantage of latest enhancements with ARHD and they recommended at least v6 xxx .11 eventhough the rom is based on v6 xxx.12, viperone also strongly advised latest firmware updates....does the developer versions you sent me have the calling fix for when the audio in the call was lost because of google update? Also, quick question, why did you include the 4 xxx something base firmware...i can just proceed with the CID change and start at the 6 series firmwares because I'm already at later version with att stock 5.12 right?
Any idea what happened the other night with the bricking - would boot, hang on black screen after first htc logo on white background and then just have the hardware touch buttons lit....was it because the firmwares ARHD posted required the bootloader to be re-locked? (failed to notice this until after I had semi-bricked it)
Also, what backup app would you recommend? looking to restore all my apps and settings after these wipes etc...getting tired of redoing it all again each time.
Thanks!
Click to expand...
Click to collapse
The Developers Edition 4.x RUU is the last RUU .. then it's 3 updates and your at the current version and ready for the Lollipop update
The ARHD International firmware needs the MID changed to work, You can eather edit the android_info.txt or change you MID to make them work
clsA said:
The Developers Edition 4.x RUU is the last RUU .. then it's 3 updates and your at the current version and ready for the Lollipop update
The ARHD International firmware needs the MID changed to work, You can either edit the android_info.txt or change you MID to make them work
Click to expand...
Click to collapse
@clsA, hmm, did not see that anywhere in the post...def. did not change MID...but they did specify needing locked bootloader, any idea why? will either of those cause the boot problem I described? Or can the firmware after 6.xxx.10 be incompatible with the att stock rom and i actually needed to flash a rom before proceeding?
When you said earlier "And then you can take OTA updates up to the current 6.07.1540.2 (3 updates I think)" you mean flash them or can take them via the OTA update service....in the dev edition does the built in OTA update service work with unlock and root?
what version does .401 mean, is that international? I know the .1540 designates developer edition.
What backup for settings and apps would you recommend, would titanium suffice?
Thanks again for all the help.
jpcreativeimagery said:
@clsA, hmm, did not see that anywhere in the post...def. did not change MID...but they did specify needing locked bootloader, any idea why? will either of those cause the boot problem I described? Or can the firmware after 6.xxx.10 be incompatible with the att stock rom and i actually needed to flash a rom before proceeding?
When you said earlier "And then you can take OTA updates up to the current 6.07.1540.2 (3 updates I think)" you mean flash them or can take them via the OTA update service....in the dev edition does the built in OTA update service work with unlock and root?
what version does .401 mean, is that international? I know the .1540 designates developer edition.
What backup for settings and apps would you recommend, would titanium suffice?
Thanks again for all the help.
Click to expand...
Click to collapse
Lollipop is coming in the next few days. Just go back to post #11 and flash the RUU and the OTA updates
I gave you the link to all the file's I used. Your S-off no need to lock the bootloader and you flash the OTA updates from stock recovery yourself
just download them all to your phone sdcard and flash them in order.
I use HTC Backup is all I need. And google keeps my contacts and calender
clsA said:
Lollipop is coming in the next few days. Just go back to post #11 and flash the RUU and the OTA updates
I gave you the link to all the file's I used. Your S-off no need to lock the bootloader and you flash the OTA updates from stock recovery yourself
just download them all to your phone sdcard and flash them in order.
I use HTC Backup is all I need. And google keeps my contacts and calender
Click to expand...
Click to collapse
@clsA: What bout with:
** Tampered **
** unlocked **
M7_UL PVT SHIP S-OFF RH
HBOOT-1.56.0000
RaDIO-4T.24.3218.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014, 09.32.41.0
Should I follow the same procedure? I want to try out the GPE Lollipop. Just wondering which firmware I should flash?
fc3211 said:
@clsA: What bout with:
** Tampered **
** unlocked **
M7_UL PVT SHIP S-OFF RH
HBOOT-1.56.0000
RaDIO-4T.24.3218.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014, 09.32.41.0
Should I follow the same procedure? I want to try out the GPE Lollipop. Just wondering which firmware I should flash?
Click to expand...
Click to collapse
Depends on what you mean "Try Out " ? you aether convert to Full GPe or you flash a rom.
If you convert, you simple change your CID and flash the RUU.
If you want to just see if it's for you, flash the rom .. I like this one >> http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
But it does require the latest firmware so yes post #11 would get you to the newest firmware
Related
I can get back into recovery but ever since I've attempted to flash a costum rom such as Viper or Revolution it gets stuck in the splash screen.
I'm not sure whats going on but I can boot into AOKP. If someone can help me out with the appropriate steps to take to flash one of those roms OR to flash back to stock I'd really appreciate because I've been at this for a couple of hours now and my head is starting to hurt :/
You need to update your firmware to run a Sense 2.22 based ROM: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
From the linked post:
The issues you will see without the new firmware include long boot times with no boot animations and some users on 9.1 reported wifi and bluetooth issues.
redpoint73 said:
You need to update your firmware to run a Sense 2.22 based ROM: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
From the linked post:
The issues you will see without the new firmware include long boot times with no boot animations and some users on 9.1 reported wifi and bluetooth issues.
Click to expand...
Click to collapse
I see you helping a lot people here redpoint so first of all thanks.
I just used the RUU.exe to return to at&t stock software number 1.58.502.1
I've read exactly what you said about being on Sense 2.22 but that's where I'm not sure what to do since AT&T hasn't release 4.4.3 yet and theres nothing for me to update to.
Do I have to S-off to obtain Sense 2.22? And also how difficult is it to S-ON? Again thanks so much.
afrojoc said:
I just used the RUU.exe to return to at&t stock software number 1.58.502.1
Click to expand...
Click to collapse
Kind of did things the hard way, although you are back up and running. Now you will need to unlock the bootloader and install custom recovery again, to get back to where you were.
All you really needed to do was either restore your nandroid (you should always make one before flashing anything) or get a different ROM (Sense 1.xxx base) onto the phone and flash it.
Also, the phone was likely not really "stuck", just taking a REALLY LONG time to boot, like 10 minutes.
afrojoc said:
I've read exactly what you said about being on Sense 2.22 but that's where I'm not sure what to do since AT&T hasn't release 4.4.3 yet and theres nothing for me to update to.
Click to expand...
Click to collapse
The post I linked previously includes the specific firmware package for US users, and a link to detailed instructions. 2.22.1540 is what you want to use, its pulled from the US Dev Edition OTA. While its not the "official AT&T" firmware, the DE is identical to the AT&T version in everything except AT&T branding (band support, etc.) and designed specifically for use on AT&T. Users here (including myself) can confirm it works seamlessly on the AT&T version.
2.22.1540 is also specifically advocated for use on the AT&T version in the following ROM post, along with great instruction (this is personally the one I used). Although you have to download the whole ROM, as the firmware is packed with it:
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
afrojoc said:
Do I have to S-off to obtain Sense 2.22?
Click to expand...
Click to collapse
To update the firmware as I've described, yes. Reason being, the partitions that need to be updated by the firmware (radio, hboot, etc.) can't be modified without either S-off, or "official" update meant for your version.
The other option is to remain S-on and wait until AT&T releases the OTA. But who knows when that will be . . .
afrojoc said:
And also how difficult is it to S-ON?
Click to expand...
Click to collapse
S-on isn't really necessary. As long as you understand the implications of s-off, its usually better to be s-off. More freedom, and more options to recover if you have issues.
Also, AT&T doesn't care about s-off in terms of warranty service. They only care about physical damage or water damage.
afrojoc said:
Again thanks so much. I see you helping a lot people here redpoint so first of all thanks
Click to expand...
Click to collapse
No problem at all. I've benefited a lot from XDA, and its my way of contributing.
I have an HTC One M8 AT&T Branded but it has 4.4.2 on it and i wanna flash viperrom 3.2.1 but it requires androids 4.4.4 software. im S-ON, 3.16 Bootloader with 1.58.502.1 Software number. Baseband Version is 1.16.21331931.LA11G_20.31A.4145.02L. im just looking to Update from 4.4.2 to 4.4.4 but i cant seem to find out how. Any help would be great.
Perfect.
Unlock your bootlooader if you haven't already, fastboot flash recovery (TWRP/PHILZ),root using the chosen custom recovery,make a backup before or after root.
Go here http://theroot.ninja/ for Sunshine
S-OFF cause that's what your going to need to update as far as 4.4.4
Orrrr just wait a few days for the ATT 4.4.4 build to be released (ETA 29th) and then youll have 4.4.4 without having to do anything.
Wonders_Never_Cease said:
Orrrr just wait a few days for the ATT 4.4.4 build to be released (ETA 29th) and then youll have 4.4.4 without having to do anything.
Click to expand...
Click to collapse
That's a better idea for sure.
I haven't noticed if Sunshine has an update that works with 4.4.4 yet.
Are you S-OFF ?
What are the advantages/disadvantages of S-OFF so the OP knows what he might be missing.
Do you know when the Sunshine update will be?
Yup,no [email protected],[email protected],there are plenty of posts about advantages and disadvantages...my point of view is simple,it is not needed for the novice,ive seen too many mess things due to lack of knowledge. My usage of it is for switching between att and developer ROM's to get latest updates. Outside of that I dont mess with conversions,to risky for a 6-700 device. My advice is stick to htc dev unlocked bootloader and wait for official update.
jball said:
That's a better idea for sure.
I haven't noticed if Sunshine has an update that works with 4.4.4 yet.
Are you S-OFF ?
What are the advantages/disadvantages of S-OFF so the OP knows what he might be missing.
Do you know when the Sunshine update will be?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Yup,no [email protected],[email protected],there are plenty of posts about advantages and disadvantages...my point of view is simple,it is not needed for the novice,ive seen too many mess things due to lack of knowledge. My usage of it is for switching between att and developer ROM's to get latest updates. Outside of that I dont mess with conversions,to risky for a 6-700 device. My advice is stick to htc dev unlocked bootloader and wait for official update.
Click to expand...
Click to collapse
Cool thank you
Im not S-OFF but hell ill wait for the 29th to roll around and see if i have an update. Can you link me to the info stating its around the 29th?
darkninja908 said:
Im not S-OFF but hell ill wait for the 29th to roll around and see if i have an update. Can you link me to the info stating its around the 29th?
Click to expand...
Click to collapse
I didn't Google for to long but I haven't found concrete links that state the exact date .how many times have we been promised a date and watch it pass by anyways.
May I ask if you've modified any other device before this one?
I'm not trying to push,but S-OFF might be in your future and will not halt an OTA from installing.
The version your on is easily exploitable using "Sunshine" unless you take the soon to be 4.4.4 update.
Nobody knows when Sunshine will have an update even with the team working on it as we speak.
Wont be much on Google @date,came from somewhere else. And nothing is ever "concrete" with software,especially with carrier branded software.
jball said:
I didn't Google for to long but I haven't found concrete links that state the exact date .how many times have we been promised a date and watch it pass by anyways.
May I ask if you've modified any other device before this one?
I'm not trying to push,but S-OFF might be in your future and will not halt an OTA from installing.
The version your on is easily exploitable using "Sunshine" unless you take the soon to be 4.4.4 update.
Nobody knows when Sunshine will have an update even with the team working on it as we speak.
Click to expand...
Click to collapse
jball said:
I didn't Google for to long but I haven't found concrete links that state the exact date .how many times have we been promised a date and watch it pass by anyways.
May I ask if you've modified any other device before this one?
I'm not trying to push,but S-OFF might be in your future and will not halt an OTA from installing.
The version your on is easily exploitable using "Sunshine" unless you take the soon to be 4.4.4 update.
Nobody knows when Sunshine will have an update even with the team working on it as we speak.
Click to expand...
Click to collapse
I have Rooted, and flashed multiple ROMS to my old M7 before. Nothing crazy.
I as well have the same build, unlocked bootloader, flashed custom recovery. Will I have to return to stock recovery using 1.58.502.1 RUU and to get the OTA update to 4.4.4??
I'm trying to get the latest Android Revolution ROM for 4.4.4 but realized I was in a bit of a pickle. I'd like to take the path of least resistance on this one - any advice would be super appreciated. Thanks!
pmoser16 said:
I as well have the same build, unlocked bootloader, flashed custom recovery. Will I have to return to stock recovery using 1.58.502.1 RUU and to get the OTA update to 4.4.4??
I'm trying to get the latest Android Revolution ROM for 4.4.4 but realized I was in a bit of a pickle. I'd like to take the path of least resistance on this one - any advice would be super appreciated. Thanks!
Click to expand...
Click to collapse
I'd say wait till tomorrow to see if an OTA update will roll out.
Or if you just can't wait for the ability to flash what you desire than I would go S-OFF and flash a non At&t firmware that you need to allow a smooth function of mentioned ROM.
Im restoring back to default AT&T ROM and such and will post weather the update has been pushed or not. i sure hope it has
**Update** Still no update, i got the " Current Software is up to date, You may check again in 23 Hours 59 Mintues.
darkninja908 said:
Im restoring back to default AT&T ROM and such and will post weather the update has been pushed or not. i sure hope it has
**Update** Still no update, i got the " Current Software is up to date, You may check again in 23 Hours 59 Mintues.
Click to expand...
Click to collapse
You can check as many times as you like by setting your time manually ahead and your phone/device won't know the difference.
Check as many times as you like but it will remain the same,you should get a notification when it's time
So if you don't have s-off you can't update to 4.44 Sense ROMS with AT&T? I'm on Slim Rom and sound quality stinks. I want the new Android Revolution but i've read wi-fi and such doesn't work. Clarification plz?
war eagle said:
So if you don't have s-off you can't update to 4.44 Sense ROMS with AT&T? I'm on Slim Rom and sound quality stinks. I want the new Android Revolution but i've read wi-fi and such doesn't work. Clarification plz?
Click to expand...
Click to collapse
Correct .
S-OFF allows you to change your CID witch will allow you to ruu Dev Edition 4.4.4 so everything runs smoothly
I've not looked on this thread in a while. I am S-off and unlocked and my cid is 11111111 but I have never updated firmware so that I can run a 4.4.4 rom. Is it correct that I flash a RUU (guess it's not called flashing when it comes to a RUU). How do I know which RUU to post - I found this one here: http://forum.xda-developers.com/showthread.php?t=2757462 (http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe)
Will I loose root or anything (other than wiping my data) when running the ruu.
jball said:
Correct .
S-OFF allows you to change your CID witch will allow you to ruu Dev Edition 4.4.4 so everything runs smoothly
Click to expand...
Click to collapse
karatche said:
I've not looked on this thread in a while. I am S-off and unlocked and my cid is 11111111 but I have never updated firmware so that I can run a 4.4.4 rom. Is it correct that I flash a RUU (guess it's not called flashing when it comes to a RUU). How do I know which RUU to post - I found this one here: http://forum.xda-developers.com/showthread.php?t=2757462 (http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe)
Will I loose root or anything (other than wiping my data) when running the ruu.
Click to expand...
Click to collapse
I'll just say that if it's a stock ruu than it's most likely without root and it will wipe as if it came out of the box.if its a full ruu than it will come with the updated firmware as well witch should allow you to flash 4.4.4 Roms and still run smoothly.
What I did around 5:00am this morning was restore my Dev edition backup I had along with the stock recovery so I could take the Dev edition lollipop official update and now I have lollipop firmware to use with my stock GPE 5.0.1 lollipop ROM/backup .
Sweetness
karatche said:
I've not looked on this thread in a while. I am S-off and unlocked and my cid is 11111111 but I have never updated firmware so that I can run a 4.4.4 rom. Is it correct that I flash a RUU (guess it's not called flashing when it comes to a RUU). How do I know which RUU to post - I found this one here: http://forum.xda-developers.com/showthread.php?t=2757462 (http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe)
Will I loose root or anything (other than wiping my data) when running the ruu.
Click to expand...
Click to collapse
Yes, running/flashing the 4.4.4 Dev Edition RUU will update you to that appropriate firmware. But, what you linked is not Dev Edition, its a stock AT&T RUU. And its not 4.4.4 either, its 4.4.2, which is probably where you already are.
What you want is the 3.28.1540 RUU linked here: http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
RUU will wipe the phone, install stock ROM (meaning root will be lost) and stock recovery.
But I also think its overkill to run an RUU just to update firmware, if that is the intent. My suggestion is to just run the firmware linked in the following post (which also has great instructions for doing so): http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
The above method shouldn't overwrite the current ROM and user data. But backup anything important before flashing firmware, just in case.
Side note, "flash" is a fairly generic term, and as the RUU flashes stock ROM among other things, the term "flash" is appropriate IMO.
So can I just load the firmware file and flash thru fastboot? Is it This one?
3.28.1540.5 Firmware only unmodified (Latest 4.4.4 Update,S-OFF REQUIRED)
http://goo.gl/tyhRRZ
redpoint73 said:
Yes, running/flashing the 4.4.4 Dev Edition RUU will update you to that appropriate firmware. But, what you linked is not Dev Edition, its a stock AT&T RUU. And its not 4.4.4 either, its 4.4.2, which is probably where you already are.
What you want is the 3.28.1540 RUU linked here: http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
RUU will wipe the phone, install stock ROM (meaning root will be lost) and stock recovery.
But I also think its overkill to run an RUU just to update firmware, if that is the intent. My suggestion is to just run the firmware linked in the following post (which also has great instructions for doing so): http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
The above method shouldn't overwrite the current ROM and user data. But backup anything important before flashing firmware, just in case.
Side note, "flash" is a fairly generic term, and as the RUU flashes stock ROM among other things, the term "flash" is appropriate IMO.
Click to expand...
Click to collapse
Hello,
I'm looking for some guidance on trying to install CM12 on HTC One (M8) with HBOOT 3.16.0.0000. Currently, when I try to flash the firmware in TWRP, I get a message that says HBOOT 3.18 or 3.19 is required. I do have S-OFF. Other information: CID-CWS__001. I'm not sure of the next steps to take.
Thanks!
When you say flash firmware are you talking about the cm12 ROM zip?
You flash firmwares in hboot/bootlooader.You will want to have Supercid for it to flash.
jball said:
When you say flash firmware are you talking about the cm12 ROM zip?
You flash firmwares in hboot/bootlooader.You will want to have Supercid for it to flash.
Click to expand...
Click to collapse
Yes, my mistake. I want to flash the CM12 ROM and I can't seem to do that because I (apparently) need a newer version of HBOOT.
My question is what is the next step? If I get supercid, will the CM12 ROM install or is there another intermediate step (upgrading HBOOT? How do I do that?).
Thanks!
poguemahone1976 said:
Yes, my mistake. I want to flash the CM12 ROM and I can't seem to do that because I (apparently) need a newer version of HBOOT.
My question is what is the next step? If I get supercid, will the CM12 ROM install or is there another intermediate step (upgrading HBOOT? How do I do that?).
Thanks!
Click to expand...
Click to collapse
Yes another step is needed,
Because your S-OFF,Supercid you can flash other firmwares to your device that will allow anything based on 5.0.0-5.0.1 and still run smoothly.
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
I even recommend converting to Dev edition fully and once fully converted it will OTA to the latest firmware for you .once your up to date you just use twrp/philz recovery and flash away
jball said:
Yes another step is needed,
Because your S-OFF,Supercid you can flash other firmwares to your device that will allow anything based on 5.0.0-5.0.1 and still run smoothly.
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
I even recommend converting to Dev edition fully and once fully converted it will OTA to the latest firmware for you .once your up to date you just use twrp/philz recovery and flash away
Click to expand...
Click to collapse
Thanks jball. I ended up doing something very similar (http://intoandroid.com/turn-gsm-htc-m8-google-play-edition/). Worked flawlessly and now I'm running Lollipop.
poguemahone1976 said:
Thanks jball. I ended up doing something very similar (http://intoandroid.com/turn-gsm-htc-m8-google-play-edition/). Worked flawlessly and now I'm running Lollipop.
Click to expand...
Click to collapse
Your welcome
I came from that very conversion but what I don't like about the full conversion is the system is full to the max .
Now by converting to Dev edition and flashing the ROM instead I have all this system left cause of the Sense partition table
I'm still on GPE conversion...I had thought about switching to Dev edition though...which firmwares have y'all used ? I was thinking 3.28.1540.5...
Well I was going to screenshot boot loader,but I forgot the key combo for boot loader screenshots. Here's what I with
Hboot: 3.19
Cid : 11111111
Mid: OP6B17000
FW : 3.11.1700.5
Im using graffixnyc's android l firmware
jxcorex28 said:
I'm still on GPE conversion...I had thought about switching to Dev edition though...which firmwares have y'all used ? I was thinking 3.28.1540.5...
Well I was going to screenshot boot loader,but I forgot the key combo for boot loader screenshots. Here's what I with
Hboot: 3.19
Cid : 11111111
Mid: OP6B17000
FW : 3.11.1700.5
Im using graffixnyc's android l firmware
Click to expand...
Click to collapse
You would want to use the 3.28.1540.***** cause if you did the earlier ruu you won't be able to OTA unless you change your CID
jball said:
You would want to use the 3.28.1540.***** cause if you did the earlier ruu you won't be able to OTA unless you change your CID
Click to expand...
Click to collapse
Here's what I have:
Hboot: 3.19
Cid : 11111111
Mid: 0P6B12000
FW : 3.11.1700.5
You think it makes sense to upgrade FW to 3.28.1540? Are the OTA updates the main benefit to upgrading?
poguemahone1976 said:
Here's what I have:
Hboot: 3.19
Cid : 11111111
Mid: 0P6B12000
FW : 3.11.1700.5
You think it makes sense to upgrade FW to 3.28.1540? Are the OTA updates the main benefit to upgrading?
Click to expand...
Click to collapse
No not the only benefit,
Stability when flashing the most recent Roms is another reason.
When flashing lollipop Roms it helps to be as up to date as you can in my opinion.
I found that when I flashed a lollipop firmware and then flashed a lollipop ROM it basically converted me to full GPE and left me with the system being about 200kb chey of having no space left (just like taking the OTA to GPE lollipop does)
jball said:
I came from that very conversion but what I don't like about the full conversion is the system is full to the max .
Now by converting to Dev edition and flashing the ROM instead I have all this system left cause of the Sense partition table
Click to expand...
Click to collapse
Why would this matter? It allows you to go back to Sense ROMs. But aside from that, I don't think that having system storage available yields any benefit. Or am I missing something?
redpoint73 said:
Why would this matter? It allows you to go back to Sense ROMs. But aside from that, I don't think that having system storage available yields any benefit. Or am I missing something?
Click to expand...
Click to collapse
It mattered when I tried to move an 815kb file to "system/bin" when there was only 225kb of system left.
It's a known issue ,
So I went back to Sense and flashed the stock GPE 5.0.1 ROM and have over 1.5g of extra space (not that I could soak up that much space)
jball said:
It mattered when I tried to move an 815kb file to "system/bin" when there was only 225kb of system left.
Click to expand...
Click to collapse
Ah, I see. So obviously if you try to add something to the system partition, and its maxed out, then that is a problem. Figured I was missing something.
Hello guys
I have HTC one m8 att
Running 4.4.4
I can't access recovery mod and I can't do a factory rest
Hmm
No update available in the setting
I should find lollipop update
Tried setting rest
And hard rest
Can U help?...
Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
AT&T HTC One (M8)
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
AT&T One (M8) Q&A, Help & Troubleshooting
Good luck!
alajrami said:
Hello guys
I have HTC one m8 att
Running 4.4.4
I can't access recovery mod and I can't do a factory rest
Hmm
No update available in the setting
I should find lollipop update
Tried setting rest
And hard rest
Can U help?...
Click to expand...
Click to collapse
What happens when you boot into bootloader and select recovery?
Lollopop has not been released yet for AT&T version. 4.4.4 was just released a couple weeks ago.
It boot back into Bootloader
alajrami said:
It boot back into Bootloader
Click to expand...
Click to collapse
Is the phone modded or not (bootloader locked or unlocked, custom recovery, root, etc.).
Are you trying to access stock recovery or custom recovery?
I bought the device with stock ruu
Then I unlocked the Bootloader
Suddenly every thing went bad like I mentioned
Now the Bootloader is relocked
I want to instale a stock Rom
The phone won't even do a factory rest
alajrami said:
I bought the device with stock ruu
Then I unlocked the Bootloader
Suddenly every thing went bad like I mentioned
Now the Bootloader is relocked
I want to instale a stock Rom
The phone won't even do a factory rest
Click to expand...
Click to collapse
Run the RUU. This should fix whatever is going on with recovery (assume you want stock recovery, as you haven't specified) as well as get you back on stock AT&T ROM.
My guess is that you just have a custom recovery install gone bad. Since you unlocked the bootloader, assume you tried to install custom recovery (as there would be no other reason to unlock the bootloader).
I tried to install the ruu but the phone doesn't accept it
Tried using adb to install it..
alajrami said:
I tried to install the ruu but the phone doesn't accept it
Click to expand...
Click to collapse
What error code?
Make sure its an RUU meant for AT&T. Hboot version of the RUU must be equal or greater than what is on the phone (no "downgrading" allowed unless you are s-off).
Tell me you hboot number, and I can tell you what AT&T RUU to use.
How did you update to 4.4.4?
I tried the same ruu on mobile 4.4.4
Even tried official lollipop from HTC site
Means no downgrading attempt
Anyway adb gives me 12 something error
About the ruu version error
But am sure am using the right ruu
alajrami said:
I tried the same ruu on mobile 4.4.4
Click to expand...
Click to collapse
That means nothing to me. What do you mean "same ruu". What is the file name exactly?
alajrami said:
Even tried official lollipop from HTC site
Click to expand...
Click to collapse
There is no Lollipop RUU for AT&T. You can't run another carrier's RUU (unless you have s-off and change CID). So that means you are running the wrong RUU.
alajrami said:
But am sure am using the right ruu
Click to expand...
Click to collapse
From the previous comment, I'm not so sure that is the case.
You didn't answer my question about what hboot number is on the phone currently.
You also did not answer my question on how you updated to 4.4.4.
Hboot 3.19.0.0000
The 4.4.4 has been auto updated before I unlocked the Bootloader
alajrami said:
Hboot 3.19.0.0000
The 4.4.4 has been auto updated before I unlocked the Bootloader
Click to expand...
Click to collapse
If you are s-on, this is the only RUU that will work: http://dl3.htc.com/application/RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2.exe
Thanks a lot I will try it and give u feed back about it
Error (132): signature error
Device information
alajrami said:
Device information
Click to expand...
Click to collapse
That is not a valid AT&T 4.4.4 software number. Are you sure you have the AT&T version? It has the AT&T "globe" logo on the back; and all the stock AT&T ROMs similarly have the AT&T logo on the boot screen.
You should also do adb getvar all, and post the output (be sure to delete IMEI and serial numbers, as there are personal info and should not be posted on a public forum);.
That's a euro build, not sure of the local of it, anything .401 is euro, .502 would be AT&T. I believe your in the wrong section for your device. I would check in euro/international forum for the M8 for possible rom match.
i wanna get an s-off with sunshine and install arhd rom after but my firmware isnt up to date so i was told to get a stock rom and update there.
Any suggestions on where i start and how to do it please?
Thanks
dimakiller3 said:
i wanna get an s-off with sunshine and install arhd rom after but my firmware isnt up to date so i was told to get a stock rom and update there.
Any suggestions on where i start and how to do it please?
Thanks
Click to expand...
Click to collapse
I can't make sense of your post so I can't help you. Maybe you could reword what your trying to do because firmware has nothing to do with a stock ROM.
basically i installed a new custom rom ARHD and my wifi doesnt work there. After searching on the web apparently it's a firmware problem. I was told that if i install a stock rom and update the firmware there and reinstall the ARHD again my wifi will work.
dimakiller3 said:
basically i installed a new custom rom ARHD and my wifi doesnt work there. After searching on the web apparently it's a firmware problem. I was told that if i install a stock rom and update the firmware there and reinstall the ARHD again my wifi will work.
Click to expand...
Click to collapse
OK so you need the latest firmware are you S-Off? If so You need to download your device latest firmware an fastboot it. I would try that before I reflashed ROM..if you still don't have WiFi then I would a restore a stock backup you should have made or go to the development section an find an flash a stock rom
dimakiller3 said:
basically i installed a new custom rom ARHD and my wifi doesnt work there. After searching on the web apparently it's a firmware problem. I was told that if i install a stock rom and update the firmware there and reinstall the ARHD again my wifi will work.
Click to expand...
Click to collapse
No, for the AT&T version that actually will not work. OTA will only update you to 4.4.4, and current ARHD is 5.0 (assume current Lollipop based ARHD is what you want).
Further, if you update to 4.4.4 OTA, this will break sunshine, and you won't be able to get s-off. So you will be essentially stuck on 4.4.4 firmware until AT&T releases Lollipop.
If you want to run Lollipop now (and any current ROM based on it, like ARHD) my advice is to s-off now. Then update to LP firmware manually.
redpoint73 said:
No, for the AT&T version that actually will not work. OTA will only update you to 4.4.4, and current ARHD is 5.0 (assume current Lollipop based ARHD is what you want).
Further, if you update to 4.4.4 OTA, this will break sunshine, and you won't be able to get s-off. So you will be essentially stuck on 4.4.4 firmware until AT&T releases Lollipop.
If you want to run Lollipop now (and any current ROM based on it, like ARHD) my advice is to s-off now. Then update to LP firmware manually.
Click to expand...
Click to collapse
I have 4.4.4 and don't know the firmware number (because of the known bug in a previous version of TWRP).
You've probably described why I can't get S-Off with Sunshine to flash the latest AT&T rom so I can know my firmware number.
I need to know it so I can flash stock backup & recovery and then viper.
Any recommendations? My thanks in advance!
Wombat Pete said:
I have 4.4.4 and don't know the firmware number (because of the known bug in a previous version of TWRP).
Click to expand...
Click to collapse
Look at your hboot number in bootloader.
3.16 = 1.x software (Android 4.4.2)
3.17 = 2.x (4.4.3)
3.19 = 3.x (4.4.4)
Lollipop (Android 5.0) also uses hboot 3.19. But as already mentioned, AT&T hasn't released an offiicial LP update yet. So this can't be the case for you.
Wombat Pete said:
You've probably described why I can't get S-Off with Sunshine to flash the latest AT&T rom so I can know my firmware number.
Click to expand...
Click to collapse
If you are hboot 3.19, sunshine won't work. Any earlier hboot, and it should work. If you updated to 4.4.4 by official means (OTA or RUU) then you have hboot 3.19, and sunshine won't work.
Wombat Pete said:
I need to know it so I can flash stock backup & recovery and then viper.
Click to expand...
Click to collapse
I don't understand what you hope to accomplish by flashing stock back and recovery. Neither will affect your firmware.
If you want to run any Lollipop based ROM (including current Viper) you need to update firmware, and on the AT&T device that means you need s-off. At least until AT&T releases LP officially.
So no, what you suggested won't work.
redpoint73 said:
I don't understand what you hope to accomplish by flashing stock back and recovery. Neither will affect your firmware.
If you want to run any Lollipop based ROM (including current Viper) you need to update firmware, and on the AT&T device that means you need s-off. At least until AT&T releases LP officially.
So no, what you suggested won't work.
Click to expand...
Click to collapse
What I'm trying to do is simply what is described on this page: http://venomroms.com/viperonem8_3-0-0-requirements/
Am I misunderstanding it? I also felt there's something odd there - or, at least, I don't understand WHY flashing the stock back-up and recovery would be necessary to flash Viper. But isn't that what it says?
I would LOVE to understand the process - what's described in that process - better!
Any guidance will be greatly appreciated.
Wombat Pete said:
What I'm trying to do is simply what is described on this page: http://venomroms.com/viperonem8_3-0-0-requirements/
Am I misunderstanding it? I also felt there's something odd there - or, at least, I don't understand WHY flashing the stock back-up and recovery would be necessary to flash Viper. But isn't that what it says?
Click to expand...
Click to collapse
You're missing a key step(s): its restore stock ROM and stock recovery for the purpose of then updating via OTA. Reason for this, is that the OTA will update your firmware (for most carriers, that means updating firmware to Lollipop).
This won't work for you (having the AT&T version), since you appear to already be on the most current AT&T OTA (4.4.4). That means you are on KitKat firmware, but need Lollipop firmware to run any LP based Sense ROMs.
Also note that the page you linked is outdated, as it refers to 4.4.4, since that was what ViperOne was based on at the time (but its been updated to LP for a while now).
I have just read that sunshine has been updated to work on 4.4.4. I think this has literally happened just on the last day or so. So your options are to sunshine s-off and update your firmware. Or else wait for AT&T to release LP, and update by official OTA or RUU.
redpoint73 said:
You're missing a key step(s): its restore stock ROM and stock recovery for the purpose of then updating via OTA. Reason for this, is that the OTA will update your firmware (for most carriers, that means updating firmware to Lollipop).
This won't work for you (having the AT&T version), since you appear to already be on the most current AT&T OTA (4.4.4). That means you are on KitKat firmware, but need Lollipop firmware to run any LP based Sense ROMs.
Also note that the page you linked is outdated, as it refers to 4.4.4, since that was what ViperOne was based on at the time (but its been updated to LP for a while now).
I have just read that sunshine has been updated to work on 4.4.4. I think this has literally happened just on the last day or so. So your options are to sunshine s-off and update your firmware. Or else wait for AT&T to release LP, and update by official OTA or RUU.
Click to expand...
Click to collapse
Redpoint, thanks! As posted on the other site, the new Sunshine option worked perfectly - I now have S-Off. Very, very cool.
So I'm on to your option one - update firmware so I can get viper on the device. Is there a recommended firmware update? How would I find this myself the next time?
Wombat Pete said:
So I'm on to your option one - update firmware so I can get viper on the device. Is there a recommended firmware update? How would I find this myself the next time?
Click to expand...
Click to collapse
The "right" firmware is a tricky question. I'd start with the 4.16.1540 firmware posted along with the ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
This is US Dev Edition firmware, which is specifically intended for AT&T's network.
Now whether it plays well with Viper or ARHD, is another question. Or whether those ROMs play well on AT&T's network is also another complicated question. AT&T does some annoyingly unique things to their network, that doesn't always play well with the "international" based ROMs. In particular, AT&T's LTE seems to be playing havoc on some "international" ROMs; possibly due to AT&T beginning implementation of HD Voice (Voice over LTE or VoLTE).
Trial and error is the best you can do. Start with the 1540 firmware I suggested, and your desired ROM, and see how it goes. But WiFi will be fixed, I can tell you that.
Also, the ROM included on the link I provided is intended specifically for use on AT&T (one of the few current ROMs that is). So if you want a LP ROM that will work seamlessly on AT&T's network, flash WNC's ROM and the 1540 firmware.
redpoint73 said:
The "right" firmware is a tricky question. I'd start with the 4.16.1540 firmware posted along with the ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
This is US Dev Edition firmware, which is specifically intended for AT&T's network.
Now whether it plays well with Viper or ARHD, is another question. Or whether those ROMs play well on AT&T's network is also another complicated question. AT&T does some annoyingly unique things to their network, that doesn't always play well with the "international" based ROMs. In particular, AT&T's LTE seems to be playing havoc on some "international" ROMs; possibly due to AT&T beginning implementation of HD Voice (Voice over LTE or VoLTE).
Trial and error is the best you can do. Start with the 1540 firmware I suggested, and your desired ROM, and see how it goes. But WiFi will be fixed, I can tell you that.
Also, the ROM included on the link I provided is intended specifically for use on AT&T (one of the few current ROMs that is). So if you want a LP ROM that will work seamlessly on AT&T's network, flash WNC's ROM and the 1540 firmware.
Click to expand...
Click to collapse
Perfect, that's all helpful and good to know.
For full disclosure: I'm on T-Mobile; it's the same network, I believe, so that probably doesn't change anything, but I mention it just in case.
So the process I'm planning to do it:
1.) Flash the ATT_4_16_1540_8_M8_Lollipop_Firmware and ROM
http://goo.gl/iumj9r
2.) Flash the latest Viper ROM.
3.) If it gives me trouble, flash firmware & from 1., above, to go back to that.
Does that sound right?
Also, do people restore s-on when they have their desired setup, or just leave the phone S-off?
Wombat Pete said:
For full disclosure: I'm on T-Mobile; it's the same network, I believe, so that probably doesn't change anything, but I mention it just in case.
Click to expand...
Click to collapse
T-Mobile and AT&T are not even remotely the same network. I know for a fact, the 1540 firmware I previously suggested (thinking you were on AT&T) does not include the AWS band that T-Mobile most commonly uses for 3G. And T-Mobile uses some different bands for LTE than AT&T.
T-Mobile has deployed 1900 MHz 3G band in select markets, in hopes of luring AT&T users (without having to swap devices). But only in certain cities.
Its best you flash T-Mobile firmware, for use on T-Mobile's network.
Wombat Pete said:
Also, do people restore s-on when they have their desired setup, or just leave the phone S-off?
Click to expand...
Click to collapse
Typically, no. In fact, if you ever want to s-off again, I believe you have to pay the $25 for sunshine again.
For the most part, there is no real downside to staying s-off, in my opinion. Just be careful that you only flash anything meant specifically for the M8 (and the GSM version, at that, nothing for the CDMA). As s-off means many checks are bypassed, and you can accidentally flash something meant for another device that bricks the phone, if you are careless. But always be careful about what you flash, and staying s-off is fine.
redpoint73 said:
T-Mobile and AT&T are not even remotely the same network. I know for a fact, the 1540 firmware I previously suggested (thinking you were on AT&T) does not include the AWS band that T-Mobile most commonly uses for 3G. And T-Mobile uses some different bands for LTE than AT&T.
T-Mobile has deployed 1900 MHz 3G band in select markets, in hopes of luring AT&T users (without having to swap devices). But only in certain cities.
Its best you flash T-Mobile firmware, for use on T-Mobile's network.
Typically, no. In fact, if you ever want to s-off again, I believe you have to pay the $25 for sunshine again.
For the most part, there is no real downside to staying s-off, in my opinion. Just be careful that you only flash anything meant specifically for the M8 (and the GSM version, at that, nothing for the CDMA). As s-off means many checks are bypassed, and you can accidentally flash something meant for another device that bricks the phone, if you are careless. But always be careful about what you flash, and staying s-off is fine.
Click to expand...
Click to collapse
Understood. Is there a similar link to recommended firmware for T-Mobile?
And then the main thing - is the process I suggest right? 1.) Flash new LP firmware; 2.) Flash the latest viper ROM; 3.) If I have trouble with viper that I can't solve, flash a ROM made for T-Mobile. Does that sound right? If so, i just need to determine the best firmware choice... and what are criteria might I use for that?
Wombat Pete said:
Understood. Is there a similar link to recommended firmware for T-Mobile?
Click to expand...
Click to collapse
I can't actually find the Lollipop T-Mobile US firmware at first glance. The firmware collection is below (with instructions how to flash). But if you go to the firmware collection link (531 folder under HTC M8 is for T-Mobile) it only has 3.x firmware (Android 4.4.4):
http://forum.xda-developers.com/showthread.php?t=2696282
I'll look some more, but you can search as well.
Now, if I understand you have the AT&T version (please confirm)? If so, flashing T-Mobile firmware (once we find it) is a little more complicated than flashing AT&T firmware on an AT&T device. You will need to change your CID and MID to T-Mobile's, in order to flash the T-Mobile firmware.
The following guide shows how to change the CID and MID. But you will need to find the T-Mobile US CID. I don't know if off hand (or where to find it quickly), so you might do your own research on that one. Keeping in mind that T-Mobile is also a carrier in Europe, so make sure is the T-Mobile US CID.
http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
Wombat Pete said:
And then the main thing - is the process I suggest right? 1.) Flash new LP firmware; 2.) Flash the latest viper ROM; 3.) If I have trouble with viper that I can't solve, flash a ROM made for T-Mobile. Does that sound right? If so, i just need to determine the best firmware choice... and what are criteria might I use for that?
Click to expand...
Click to collapse
I don't think T-Mobile is nearly as troublesome as AT&T (although you might check the T-Mobile M8 forum section on that, or the Viper thread). I have a feeling that once you are on the T-Mobile firmware, and flash Viper, you will be fine.
redpoint73 said:
I can't actually find the Lollipop T-Mobile US firmware at first glance. The firmware collection is below (with instructions how to flash). But if you go to the firmware collection link (531 folder under HTC M8 is for T-Mobile) it only has 3.x firmware (Android 4.4.4):
http://forum.xda-developers.com/showthread.php?t=2696282
I'll look some more, but you can search as well.
Now, if I understand you have the AT&T version (please confirm)? If so, flashing T-Mobile firmware (once we find it) is a little more complicated than flashing AT&T firmware on an AT&T device. You will need to change your CID and MID to T-Mobile's, in order to flash the T-Mobile firmware.
The following guide shows how to change the CID and MID. But you will need to find the T-Mobile US CID. I don't know if off hand (or where to find it quickly), so you might do your own research on that one. Keeping in mind that T-Mobile is also a carrier in Europe, so make sure is the T-Mobile US CID.
http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
I don't think T-Mobile is nearly as troublesome as AT&T (although you might check the T-Mobile M8 forum section on that, or the Viper thread). I have a feeling that once you are on the T-Mobile firmware, and flash Viper, you will be fine.
Click to expand...
Click to collapse
Confirming: I am using T-Mobile as the carrier, but the device was made for AT&T.
Is this what we're looking for? http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
And, if so... as I'm S-off, I don't need to go through the stock ROM/stock recovery steps, and there's also no need to re-lock, RIGHT? I'd like to be as sure as possible that I'm doing the right steps in the right order.
Wombat Pete said:
Is this what we're looking for? http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
And, if so... as I'm S-off, I don't need to go through the stock ROM/stock recovery steps, and there's also no need to re-lock, RIGHT? I'd like to be as sure as possible that I'm doing the right steps in the right order.
Click to expand...
Click to collapse
You are correct. RUU will give you a complete stock T-Mobile image, not just the firmware you want, but also stock T-Mobile Lollipop ROM, stock recovery, etc. Its a bit of a nuclear option, if the main intent is to just update firmware and install Viper. But it will get the job done.
Also correct that there is no need to relock bootloader to RUU, since you are s-off. But you need to change to T-Mobile CID and MID to run the RUU.
What you will have after changing CID/MID and running the T-Mobile RUU is essentially a T-Mobile M8, in everything except the stupid AT&T logo on back of the phone!
If you want to install a custom ROM after that, just flash TWRP back onto the phone, and flash the desired ROM.
redpoint73 said:
You are correct. RUU will give you a complete stock T-Mobile image, not just the firmware you want, but also stock T-Mobile Lollipop ROM, stock recovery, etc. Its a bit of a nuclear option, if the main intent is to just update firmware and install Viper. But it will get the job done.
Also correct that there is no need to relock bootloader to RUU, since you are s-off. But you need to change to T-Mobile CID and MID to run the RUU.
What you will have after changing CID/MID and running the T-Mobile RUU is essentially a T-Mobile M8, in everything except the stupid AT&T logo on back of the phone!
If you want to install a custom ROM after that, just flash TWRP back onto the phone, and flash the desired ROM.
Click to expand...
Click to collapse
OK... so I think this makes sense. Is this the process, then?
1.) I change to T-Mobile CID and MID
2.) Then... to run the RUU, do I need to be in fastboot? Just have the phone plugged in? Run it from the fastboot directory? Put it in the phone memory?
I'd be running THIS, I gather: RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2.exe
Wait... that can't be right, given that the name includes "ATT" and "Cingular". I suppose they mean I have to find it myself... here? http://www.htc.com/us/support/htc-one-t-mobile/news/ Yes, the download at the end of this page, right? And it won't brick the phone so long as I'm S-off...
...does that seem right?
3.) Then I flash VIPER over that. If I have any problems with VIPER, I should be able to run this RUU again? Is that the best approach, do you think?
---------- Post added at 12:36 AM ---------- Previous post was at 12:24 AM ----------
Two additional things:
First, HTC (not surprisingly) refuses to say whether the RUU will work, even with S-off.
Second, a note from the chat, which I post for common interest here:
ME: T-Mobile and AT&T are the same, physically, right? Only SOFTWARE differences, right? Not hardware differences, right?
HTC Agent: Almost everything is the same. But the frequencies of the antenna are different.Don't know whether this affects our process here, but thought it might be interesting.
Also, after the RUU I'd be S-Off, but locked? Unlock again? Not that that should be difficult...
Wombat Pete said:
OK... so I think this makes sense. Is this the process, then?
1.) I change to T-Mobile CID and MID
2.) Then... to run the RUU, do I need to be in fastboot? Just have the phone plugged in? Run it from the fastboot directory? Put it in the phone memory?
I'd be running THIS, I gather: RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2.exe
Wait... that can't be right, given that the name includes "ATT" and "Cingular". I suppose they mean I have to find it myself... here? http://www.htc.com/us/support/htc-one-t-mobile/news/ Yes, the download at the end of this page, right? And it won't brick the phone so long as I'm S-off...
...does that seem right?
3.) Then I flash VIPER over that. If I have any problems with VIPER, I should be able to run this RUU again? Is that the best approach, do you think?
Click to expand...
Click to collapse
1) Correct
2) Normally, you just have the phone booted; and the RUU will reboot the phone to fastboot automatically. There are a few instances where some folk have to put the phone into fastboot mode manually. But it will normally work the way the instructions tell you.
Run the RUU executable from your PC. It doesn't matter where the file is located.
Use the RUU linked at the bottom of the HTC support page for the T-Mobile version.
3) After RUU, you will need to flash TWRP again; as RUU write stock recovery over whatever was there before (TWRP in your case). After flashing TWRP, then you can flash Viper.
Yes, if Viper give you trouble you can always use the RUU again.
Wombat Pete said:
Two additional things:
First, HTC (not surprisingly) refuses to say whether the RUU will work, even with S-off.
Click to expand...
Click to collapse
They won't say that the T-Mobile RUU will run on the AT&T version, if that is what you asked them. HTC doesn't want you "converting" the device from one carrier version to another; since it contrary to what the carriers want.
Similarly, they won't want to acknowledge s-off since they don't like the mod community hacking/exploiting s-off in the first place.
Wombat Pete said:
Second, a note from the chat, which I post for common interest here:
ME: T-Mobile and AT&T are the same, physically, right? Only SOFTWARE differences, right? Not hardware differences, right?
HTC Agent: Almost everything is the same. But the frequencies of the antenna are different.Don't know whether this affects our process here, but thought it might be interesting.
Click to expand...
Click to collapse
I think that agent is simply wrong here. Snapdragon 801, band support is software based, for all but CDMA bands (which require different hardware).
If you search the forums, I'm pretty certain there are other users on these forums that have done exactly what you are proposing: converting the AT&T version to T-Mobile. I may have even helped one or 2 users do it.