Hey all, was wondering if the m8 has some version of 1 handed mode (like the gs5) either stock or included in Roms.
(Somewhat hard to reach the far end of the screen when I tried a demo model & I text very frequently )
If not, has anyone tried http://www.phonearena.com/news/How... handed mode tried it again and it fits fine.
Also a bit curious about what the deal with having a developer edition to convert to is,
Does this mean that we can get new updates from HTC before att adds in their bloatware?
Or does it mean something else significant?
I read the other thread relating to it but wasn't sure
The_Zodiac said:
Also a bit curious about what the deal with having a developer edition to convert to is,
Does this mean that we can get new updates from HTC before att adds in their bloatware?
Click to expand...
Click to collapse
Yup, that's pretty much spot-on. No bloat or carrier branding. Updates come faster. The DE already had the 4.4.3 OTA rolled out maybe 2 weeks ago or so. AT&T OTA is supposed to be "soon", but who knows when?
redpoint73 said:
Yup, that's pretty much spot-on. No bloat or carrier branding. Updates come faster. The DE already had the 4.4.3 OTA rolled out maybe 2 weeks ago or so. AT&T OTA is supposed to be "soon", but who knows when?
Click to expand...
Click to collapse
Thanks for the info! Nice seeing you around again man. ( nice to hear that esp. Because att tends to drag its feet on upgrades)
Next question is that there are separate Roms based on which version your on?
Do either cross over? Meaning if u switch to gpe base can I use normal Roms or vice versa?
Im not sure which viperone is? Assuming standard at version but not sure.
The_Zodiac said:
Thanks for the info! Nice seeing you around again man. ( nice to hear that esp. Because att tends to drag its feet on upgrades)
Next question is that there are separate Roms based on which version your on?
Do either cross over? Meaning if u switch to gpe base can I use normal Roms or vice versa?
Im not sure which viperone is? Assuming standard at version but not sure.
Click to expand...
Click to collapse
& are there any disadvantages to switching to gpe?
(I wouldn't think their would be due to identical hardware, but thought id ask just in case)
AT&T wont be for awhile....soon = months
redpoint73 said:
Yup, that's pretty much spot-on. No bloat or carrier branding. Updates come faster. The DE already had the 4.4.3 OTA rolled out maybe 2 weeks ago or so. AT&T OTA is supposed to be "soon", but who knows when?
Click to expand...
Click to collapse
---------- Post added at 09:53 AM ---------- Previous post was at 09:52 AM ----------
No no advantages at all...unless you want plane jane android...
The_Zodiac said:
& are there any disadvantages to switching to gpe?
(I wouldn't think their would be due to identical hardware, but thought id ask just in case)
Click to expand...
Click to collapse
The_Zodiac said:
Thanks for the info! Nice seeing you around again man. ( nice to hear that esp. Because att tends to drag its feet on upgrades)
Next question is that there are separate Roms based on which version your on?
Do either cross over? Meaning if u switch to gpe base can I use normal Roms or vice versa?
Im not sure which viperone is? Assuming standard at version but not sure.
Click to expand...
Click to collapse
Good to see you here, too.
Any ROM meant for the GSM version should be compatible (stay away from the CDMA Sprint/Verizon specific ROMs). Although I'd exercise some common-sense caution and check the specific ROM thread to make sure AT&T is supported, or at least confirmed in the thread by AT&T users to work.
If you look at the ViperOne thread in this (AT&T) forum, the download section just links to the "main" thread in the "international/generic" M8 forum anyway. Which then links to the Venom Team download page, where you will see there is just one version for all GSM M8 versions.
GPE can mean one of 2 things, either just flashing a GPE-based custom ROM, or doing a "full conversion" which entails flashing a special RUU. The full conversion changes the partitioning on the device, and the only real advantage is a full GPE "stock" experience, which also means official GPE updates. If you don't care about that, and just want to try out the GPE experience, I'd suggest flashing a GPE-based custom ROM, which does not require changing the partitions.
redpoint73 said:
Good to see you here, too.
Any ROM meant for the GSM version should be compatible (stay away from the CDMA Sprint/Verizon specific ROMs). Although I'd exercise some common-sense caution and check the specific ROM thread to make sure AT&T is supported, or at least confirmed in the thread by AT&T users to work.
If you look at the ViperOne thread in this (AT&T) forum, the download section just links to the "main" thread in the "international/generic" M8 forum anyway. Which then links to the Venom Team download page, where you will see there is just one version for all GSM M8 versions.
GPE can mean one of 2 things, either just flashing a GPE-based custom ROM, or doing a "full conversion" which entails flashing a special RUU. The full conversion changes the partitioning on the device, and the only real advantage is a full GPE "stock" experience, which also means official GPE updates. If you don't care about that, and just want to try out the GPE experience, I'd suggest flashing a GPE-based custom ROM, which does not require changing the partitions.
Click to expand...
Click to collapse
Thanks for all the specific info, exactly what I was looking for.
Just got my device & I love it so far.
The last question I've got at the money is, I've heard some devices can't get bootloader unlocked through normal means , and have pay for the exploit,?
How do you know which version you have? (is it a certain hboot or something
Or do you just have to try the normal exploit & see if it works?
The_Zodiac said:
The last question I've got at the money is, I've heard some devices can't get bootloader unlocked through normal means , and have pay for the exploit,?
How do you know which version you have? (is it a certain hboot or something
Or do you just have to try the normal exploit & see if it works?
Click to expand...
Click to collapse
I think its just Verizon that blocks bootloader unlock, and S-off is required to get custom recovery on it. Bootloader unlock is not an issue with the AT&T version though "normal" means (HTCDev.com), regardless of software version, hboot, etc.
S-off is another issue. Firewater works for some older AT&T M8's, but not on newer ones. Its not definite whether its software number, hboot, etc. that determines this. Just try firewater, and if it doesn't work you will have to pay $25 for sunshine if you want s-off.
Related
Hey, Seems like Videotron is lazy when it comes to updating their user to the latest OS.
My friend has this phone and since I know a lot when it comes to do simple things like flashing roms and kernel, he wanted me to help him to update his phone. Thing is, I can't get, for the love of Morgan Freeman (AKA god), to S-Off his Amaze 4G. So I'll try the alternative since he doesn't need anything fancy other than the regular stuff.
I know that I can flash manually the OTA for carriers that has it but I don't know if I should try a Telus, T-Mobile rom and so on.
So what can I do about that?
And something else too, the last time I updated from OTA, it was when I received my Nexus S so I don't know if it factory resets and I need to create some backup in case.
You will HAVE to s-off if you want to update via another carriers ICS rom file, it's not possible with s-on, check the pin hole on his amaze, you may have to take a sharp pin and dig inside of it a bit, there seems to be a plastic covering it at times. Try s-off again after that, use a a paper clip with some tape insulating it, it works really great compared to wires. S-offed an evo 3d on the very first try today using one.
Okay, cool. Thanks for tips I will try it out.
Sent using Kirby's Warp Star.
qu3becker said:
Okay, cool. Thanks for tips I will try it out.
Sent using Kirby's Warp Star.
Click to expand...
Click to collapse
You're welcome, nice Kirby avatar, used to love that game back on my GBA.
i tried with a wire for almost an hour. first try with the paper clip and i got it. very easy to do
qu3becker said:
I know that I can flash manually the OTA for carriers that has it but I don't know if I should try a Telus, T-Mobile rom and so on.
Click to expand...
Click to collapse
This part is still unanswered and as I am in the same situation I ask the same question
I don't think the phone carrier matters once s-off since we usually don't flash the radio but especially for OTA upgrades maybe you have to be superCID and/or use a carrier that uses the same frequencies, 1700/2100 in Videotron's case?
Are there any other crucial differences than the radio between one carrier and another? Do we absolutely need to go by the OTA of another carrier to get to ICS or is there a way to flash any ICS based ROM and fix it manually after? I searched that but I can't even find the question asked... If we can't, then why? What are the modified parts from stock GB to stock ICS on the same carrier?
Maybe should I start a new question thread... Does xda uses that one question per thread rule? Don't remember to have seen it in the rules.
Thanks in advance!
johnride said:
This part is still unanswered and as I am in the same situation I ask the same question
I don't think the phone carrier matters once s-off since we usually don't flash the radio but especially for OTA upgrades maybe you have to be superCID and/or use a carrier that uses the same frequencies, 1700/2100 in Videotron's case?
Are there any other crucial differences than the radio between one carrier and another? Do we absolutely need to go by the OTA of another carrier to get to ICS or is there a way to flash any ICS based ROM and fix it manually after? I searched that but I can't even find the question asked... If we can't, then why? What are the modified parts from stock GB to stock ICS on the same carrier?
Maybe should I start a new question thread... Does xda uses that one question per thread rule? Don't remember to have seen it in the rules.
Thanks in advance!
Click to expand...
Click to collapse
All amaze devices basically have the same band, all the carriers we have here use the same band, so the choice of software is upto you since they basically have the same options, the only exception being T-Mobile, they are the only carrier that add in their own apps and modify a few things about the firmware and thanks to the htc/apple issue they changed the app association as well, so if you want the pure software with everything stock HTC the way it would be on an international version, then the Telus option would be best for you.
Good for the carrier specific software. Or in this case the absence of specificity
One detail is that Videotron installs a single app it's called "Portail Videotron" for renting and stream movies over the 4G network, a good way to have users using an enormous amount of data. But as long as the radio that comes with the Telus ROM is the same this app wich I don't even use I really don't care.
Will start a new thread for the other questions. Or won't if you think it won't be useful.
qu3becker said:
Hey, Seems like Videotron is lazy when it comes to updating their user to the latest OS.
My friend has this phone and since I know a lot when it comes to do simple things like flashing roms and kernel, he wanted me to help him to update his phone. Thing is, I can't get, for the love of Morgan Freeman (AKA god), to S-Off his Amaze 4G. So I'll try the alternative since he doesn't need anything fancy other than the regular stuff.
I know that I can flash manually the OTA for carriers that has it but I don't know if I should try a Telus, T-Mobile rom and so on.
So what can I do about that?
And something else too, the last time I updated from OTA, it was when I received my Nexus S so I don't know if it factory resets and I need to create some backup in case.
Click to expand...
Click to collapse
Videotron already started on july 1 there ics update. It's a question of time that all the servers have the update. Some already have it.
johnride said:
Good for the carrier specific software. Or in this case the absence of specificity
One detail is that Videotron installs a single app it's called "Portail Videotron" for renting and stream movies over the 4G network, a good way to have users using an enormous amount of data. But as long as the radio that comes with the Telus ROM is the same this app wich I don't even use I really don't care.
Will start a new thread for the other questions. Or won't if you think it won't be useful.
Click to expand...
Click to collapse
You started asking here, so ask all others here to save threads.
---------- Post added at 12:03 PM ---------- Previous post was at 12:02 PM ----------
rouiz said:
Videotron already started on july 1 there ics update. It's a question of time that all the servers have the update. Some already have it.
Click to expand...
Click to collapse
If someone from videotron can pull the OTA file from their device he can update manually.
Dark Nightmare said:
You started asking here, so ask all others here to save threads.
---------- Post added at 12:03 PM ---------- Previous post was at 12:02 PM ----------
If someone from videotron can pull the OTA file from their device he can update manually.
Click to expand...
Click to collapse
Ok so my questions are basically already in my first post. It is not that I don't understand the procedure to upgrade to ICS by dl the OTA, rename it to PH85IMG.zip and let hboot do the rest, it is just that I would like to be free to go back and forth between GB and ICS as I have always did with other phones. I can't see wich part of the system can be modified only by the OTA and not manually.
Edit: one may find it useless, it is just that I dislike much to be dependent on the OTA's
johnride said:
Ok so my questions are basically already in my first post. It is not that I don't understand the procedure to upgrade to ICS by dl the OTA, rename it to PH85IMG.zip and let hboot do the rest, it is just that I would like to be free to go back and forth between GB and ICS as I have always did with other phones. I can't see wich part of the system can be modified only by the OTA and not manually.
Edit: one may find it useless, it is just that I dislike much to be dependent on the OTA's
Click to expand...
Click to collapse
Due to signatures and encryption and in the cases of the things we just don't wanna touch like the radio, it's risky to mess with things like the radio and since we don't have a PH85IMG for every carrier like we do for tmobile we have to depend on the OTA files, in order for you to switch between GB and ICS as you wish you will have to s-off, that's the only way. Once you're s-off and super cid, you can upgrade, downgrade, swap hboots, swap roms, try out other carrier roms, all without restrictions.
Ok I tried to flash ICS EnergyRom with s-off, now that I am supercid I try once again.
johnride said:
Ok I tried to flash ICS EnergyRom with s-off, now that I am supercid I try once again.
Click to expand...
Click to collapse
Make sure you update your device to ICS first before you flash a custom rom, certain background files like radio, hboot etc have to be the ICS version for it to work.
That is what I don't like... But just to make it clear, with ICS version of hboot radio etc both GB and ICS are supported while with GB version ICS is not?
For now I feel a bit lazy so I will use the usual way and will look back at this at some moment.
Thanks
johnride said:
That is what I don't like... But just to make it clear, with ICS version of hboot radio etc both GB and ICS are supported while with GB version ICS is not?
For now I feel a bit lazy so I will use the usual way and will look back at this at some moment.
Thanks
Click to expand...
Click to collapse
If you still need the update :
d-h.st/VMk
OTA_RUBY_ICS_35_S_Videotron_CA_2.14.1530.6-1.46.1530.1_R2_release_2630972v8tnj4gaksgm0w5
original rom
Hi there,
is someone can help me out? I need an original HTC Amaze videotron ROM. I tried the RUU.exe, but it's not working. I can't install the .exe, even if I'm in recovery mode.
Thanks!
Clouter said:
Hi there,
is someone can help me out? I need an original HTC Amaze videotron ROM. I tried the RUU.exe, but it's not working. I can't install the .exe, even if I'm in recovery mode.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=25761360
The Videotron RUU is supposed to work. You have to be in the bootloader wich you can access by removing your battery and then vol-down + power, relocked (not in recovery). I don't know if it has to be stock CID, don't think so.
johnride said:
http://forum.xda-developers.com/showthread.php?p=25761360
The Videotron RUU is supposed to work. You have to be in the bootloader wich you can access by removing your battery and then vol-down + power, relocked (not in recovery). I don't know if it has to be stock CID, don't think so.
Click to expand...
Click to collapse
That RUU is GB, not ICS since nobody every pulled the ICS OTA file, I don't have an amaze anymore to pull it so if any of you are on GB, kindly pull the file for other users.
Updating hboot only
How can I update only the hboot? And would an hboot from a different Canadian carrier still work? e.g. hboot from Telus and rom from Wind Mobile...
Thanks in advance...
Is the ATT One, locked down like they did to their version of the Galaxy S4 ?
Or can the ATT One, be rooted and flash ROM's and kernels with CWM or TWRM ? I used to have the One X, and that thing sucked for flashing, due to being S-On, and having to use the bootloader and boot.img to flash with Command prompt stuff, etc... really sucked. Would like to have no S-On crap and have to flash through the bootloader,
I just like to reboot to the Recovery only, flash the zip, and be done. Can that be done with the ATT One, or would I need he "Developer Edition" only to do that ?
Zorachus said:
Is the ATT One, locked down like they did to their version of the Galaxy S4 ?
Or can the ATT One, be rooted and flash ROM's and kernels with CWM or TWRM ? I used to have the One X, and that thing sucked for flashing, due to being S-On, and having to use the bootloader and boot.img to flash with Command prompt stuff, etc... really sucked. Would like to have no S-On crap and have to flash through the bootloader,
I just like to reboot to the Recovery only, flash the zip, and be done. Can that be done with the ATT One, or would I need he "Developer Edition" only to do that ?
Click to expand...
Click to collapse
/smh
yes it can just get att one
UMGixxer said:
yes it can just get att one
Click to expand...
Click to collapse
Thanks, was thinking on possibly getting the ATT One, and hopefully we will get a port of the "Google Edition" ROM shortly after it's release next month ? And would like to flash it through recovery, not having to go through the command prompt and need a boot.img file, and all that crap.
Zorachus said:
Thanks, was thinking on possibly getting the ATT One, and hopefully we will get a port of the "Google Edition" ROM shortly after it's release next month ? And would like to flash it through recovery, not having to go through the command prompt and need a boot.img file, and all that crap.
Click to expand...
Click to collapse
Flashing works just as you described ..very simple, boot image gets flashed along with the rom
clsA said:
Flashing works just as you described ..very simple, boot image gets flashed along with the rom
Click to expand...
Click to collapse
Thanks, so basically, we could turn our ATT One, into a "Google Edition" One with a ported ROM this Summer, and it should be near identical to the real deal G.E. version then ?
Zorachus said:
Thanks, so basically, we could turn our ATT One, into a "Google Edition" One with a ported ROM this Summer, and it should be near identical to the real deal G.E. version then ?
Click to expand...
Click to collapse
Scotts Clean rom DE is already pretty close to the google edition
here >> http://forum.xda-developers.com/showthread.php?t=2262234
clsA said:
Scotts Clean rom DE is already pretty close to the google edition
here >> http://forum.xda-developers.com/showthread.php?t=2262234
Click to expand...
Click to collapse
Thanks, looks pretty interesting. But sadly he stopped development on it, moved on the S4. Seems like the Galaxy S4 will have a larger development community than the One ?
clsA said:
Scotts Clean rom DE is already pretty close to the google edition
here >> http://forum.xda-developers.com/showthread.php?t=2262234
Click to expand...
Click to collapse
Stuffing AOSP apps and removing Sense apps, while still keeping the Sense frameworks, is far from AOSP, the reason the GE is coming out is ppl want the option of pure AOSP on it without any trace of Sense.
When face palm just doesn't do it enough justice...
Sent from my HTC One using xda app-developers app
Confused
I also am curious if the At&t HTC One bootloader is unlockable through htcdev. I have read conflicting reports about it. can anyone clear it up? I am hoping to unlock the bootloader on my At&t HTC One but I want to know if it's ok to do. I bought my phone two weeks ago and I don't want to brick it.
Zorachus said:
Thanks, looks pretty interesting. But sadly he stopped development on it, moved on the S4. Seems like the Galaxy S4 will have a larger development community than the One ?
Click to expand...
Click to collapse
no idea .. I would not own another Samsung device
Zorachus said:
Thanks, looks pretty interesting. But sadly he stopped development on it, moved on the S4. Seems like the Galaxy S4 will have a larger development community than the One ?
Click to expand...
Click to collapse
The S4 will have a bigger dev community simply due to the fact Samsung is a bigger/more popular manufacturer...but theres still plenty of devs for the One from what I've seen.
ahab4000 said:
I also am curious if the At&t HTC One bootloader is unlockable through htcdev. I have read conflicting reports about it. can anyone clear it up? I am hoping to unlock the bootloader on my At&t HTC One but I want to know if it's ok to do. I bought my phone two weeks ago and I don't want to brick it.
Click to expand...
Click to collapse
bootloader unlock works fine ...theirs no conflicting reports
clsA said:
bootloader unlock works fine ...theirs no conflicting reports
Click to expand...
Click to collapse
I found this "The interesting thing is that these instructions work fine only for the international version of HTC One, and if you have the AT&T variant, the official method won’t work, since AT&T didn’t allow that (carriers do that, don’t they?). That’s rather odd and annoying, because the official bootloader unlock worked on the AT&T variant as well until the device actually hit the shelves and AT&T forced HTC to go back to a more closed approach. Of course, there would be other, unofficial unlock methods coming out pretty soon, but until they do, AT&T users are out of luck." on Redmond Pie "How to Unlock HTC One" page. (Can't post link)
I interpreted this as saying that I am out of luck.
Was I wrong?
ahab4000 said:
I found this "The interesting thing is that these instructions work fine only for the international version of HTC One, and if you have the AT&T variant, the official method won’t work, since AT&T didn’t allow that (carriers do that, don’t they?). That’s rather odd and annoying, because the official bootloader unlock worked on the AT&T variant as well until the device actually hit the shelves and AT&T forced HTC to go back to a more closed approach. Of course, there would be other, unofficial unlock methods coming out pretty soon, but until they do, AT&T users are out of luck." on Redmond Pie "How to Unlock HTC One" page. (Can't post link)
I interpreted this as saying that I am out of luck.
Was I wrong?
Click to expand...
Click to collapse
Theirs no evidence of that story being correct here
go to htc dev and try it
ahab4000 said:
I found this "The interesting thing is that these instructions work fine only for the international version of HTC One, and if you have the AT&T variant, the official method won’t work, since AT&T didn’t allow that (carriers do that, don’t they?). That’s rather odd and annoying, because the official bootloader unlock worked on the AT&T variant as well until the device actually hit the shelves and AT&T forced HTC to go back to a more closed approach. Of course, there would be other, unofficial unlock methods coming out pretty soon, but until they do, AT&T users are out of luck." on Redmond Pie "How to Unlock HTC One" page. (Can't post link)
I interpreted this as saying that I am out of luck.
Was I wrong?
Click to expand...
Click to collapse
I have no idea why he wrote that, because it is most definitely wrong. I followed the official instruction to unlock bootloader from htcdev website for my AT&T One without a problem.
djkinetic said:
Stuffing AOSP apps and removing Sense apps, while still keeping the Sense frameworks, is far from AOSP, the reason the GE is coming out is ppl want the option of pure AOSP on it without any trace of Sense.
Click to expand...
Click to collapse
I didn't say it was exact but it gives you the idea
I hate ASOP myself would much rather have a sense rom ..that's why I bought the One
clsA said:
I didn't say it was exact but it gives you the idea
I hate ASOP myself would much rather have a sense rom ..that's why I bought the One
Click to expand...
Click to collapse
I know you didn't say it was exact, but Sense as you know is far different from AOSP, and the GE will have straight AOSP with no Sense, basically Vanilla (Nexus type) Android.
is the search button flipping broke ?
Hi, I'm new to this device, as a matter of fact I don't have it yet, its in the mail....I purchased an HTC ONE Google Edition At&t phone and am going to use it on Straight Talk. I had a HOX+ but couldn't get WiFi tether to work and tried multiple Roms and other advice. Anyway, I was encouraged to get the ONE because there is a lot more development on it. I was wondering if I first UNLOCK the device from its carrier and ROOT it and get S-OFF, could I install an "International" RUU and firmware to get rid of any preconfigured settings to At&t and not COMPLETELY RUIN my device and still have LTE ?
devo3d said:
Hi, I'm new to this device, as a matter of fact I don't have it yet, its in the mail....I purchased an HTC ONE Google Edition At&t phone and am going to use it on Straight Talk. I had a HOX+ but couldn't get WiFi tether to work and tried multiple Roms and other advice. Anyway, I was encouraged to get the ONE because there is a lot more development on it. I was wondering if I first UNLOCK the device from its carrier and ROOT it and get S-OFF, could I install an "International" RUU and firmware to get rid of any preconfigured settings to At&t and not COMPLETELY RUIN my device and still have LTE ?
Click to expand...
Click to collapse
yes you can just make sure you read and are comfortable with doing it because if you do it wrong you can brick your phone
jerrycoffman45 said:
yes you can just make sure you read and are comfortable with doing it because if you do it wrong you can brick your phone
Click to expand...
Click to collapse
Are there any Custom Roms already made from the Internation Build?
devo3d said:
Are there any Custom Roms already made from the Internation Build?
Click to expand...
Click to collapse
you can use all of these
http://forum.xda-developers.com/htc-one
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 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.