Related
Hello all,
I seem to have quite a problem gaining s-off on my brand new HTC m8.
I've tried the firewater s-off method for which i unlocked my device.
Firewater just seems to give me the following message:
Code:
********** whelp, this sucks, firewater can not work on your device **********
********** no amount of reflashing, retrying, or ruuing will fix... **********
********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********
********** if we are able to fix this issue, it will be announced **********
********** bye bye.....sorry it didn't work out. **********
Followed all the instructions as posted on the firewater page, also disabled verify apps, just to be sure i disabled my virus scanner(making sure nothing interferes) but nothing seems to work.
This is my getvar output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH43MWM11546
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
If anyone could offer any help at all it would be very much appreciated, the firewater devs seem to be too busy to answer questions.
Thanks in advance,
Incapable
Some models just can't be s-offed yet. I'm sure eventually a working method will be released for those that don't work with the current method.
Sent from my HTC One_M8 using xda app-developers app
exad said:
Some models just can't be s-offed yet. I'm sure eventually a working method will be released for those that don't work with the current method.
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
I am aware of this, the weird thing is that i saw others with a m8_ul with cid htc__E11 that managed to get it working. Basicly, i'm wondering if there is something i missed
incapable said:
I am aware of this, the weird thing is that i saw others with a m8_ul with cid htc__E11 that managed to get it working. Basicly, i'm wondering if there is something i missed
Click to expand...
Click to collapse
No, that message is quite clear, you missed nothing, did nothing wrong. Your phone can not be s-offed. If you missed something firewater would have informed you. Beaups and the gang have been doing this a long time and their scripts will often detect and alert you if there's something you did wrong or missed.
Okay =) in that case I'll just be patient =)
incapable said:
Okay =) in that case I'll just be patient =)
Click to expand...
Click to collapse
You're not alone. I get the same message and I'm on Telus just like exad seems to be from his signature. So far there is no pattern as to which ones can or can't s-off (region, provider, etc)
Same boat
Yup I'm in the same boat
I'm on a Rogers HTC One M8 ... hopefully a way of getting s-off on these variants comes out. Me want GPE on me M8!!
5par7acu5 said:
Yup I'm in the same boat
I'm on a Rogers HTC One M8 ... hopefully a way of getting s-off on these variants comes out. Me want GPE on me M8!!
Click to expand...
Click to collapse
[Android][Unlock/S-OFF] SunShine for modern Motorola & HTC devices $25 only alternative
I'm on Telus and Sunshine worked no problem. ?
Sunshine worked for me as well.
It seems Sunshine is very choosy on which ROM it will run. If the ROM and kernel are not stock enough, Sunshine will fail.
I've tried to use Sunshine from Stock ROM with the ElementalX kernel, InsertCoin and ViperOne which all failed.
ARHD v11.1 was the one ROM on which Sunshine worked.
Sent from my HTC One_M8 using Tapatalk
Iceberger said:
Sunshine worked for me as well.
It seems Sunshine is very choosy on which ROM it will run. If the ROM and kernel are not stock enough, Sunshine will fail.
I've tried to use Sunshine from Stock ROM with the ElementalX kernel, InsertCoin and ViperOne which all failed.
ARHD v11.1 was the one ROM on which Sunshine worked.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I had the same problem and they said use a close to stock rom. To finally get sunshine to work I pushed a stock RUU and then ran sunshine and it worked for me. Now It was a biach because I by no means am a smart guy and had ot work with it, but, with all the time I've spent reading on this site and asking stupid questions I was able to do this myself. Do some reading and do a stock flash and then try sunshine. At worse you just have to unlock it again. Good luck.
myrmidon84 said:
I had the same problem and they said use a close to stock rom. To finally get sunshine to work I pushed a stock RUU and then ran sunshine and it worked for me. Now It was a biach because I by no means am a smart guy and had ot work with it, but, with all the time I've spent reading on this site and asking stupid questions I was able to do this myself. Do some reading and do a stock flash and then try sunshine. At worse you just have to unlock it again. Good luck.
Click to expand...
Click to collapse
Tried with Firewather and Sunshine but no luck.
Im on ViperS Rom, so do you have a link to the Rom you flashed and got S-Off on?
flash stock nandroid backup or arhd 11.1 and buy sunshine $25 .worked for me
AsmirGT said:
flash stock nandroid backup or arhd 11.1 and buy sunshine $25 .worked for me
Click to expand...
Click to collapse
I don't have nandroid of the stock Rom cos of a broken sd card, so il't try with ARHD.
jkolner said:
I don't have nandroid of the stock Rom cos of a broken sd card, so il't try with ARHD.
Click to expand...
Click to collapse
ARHD 11.1 worked for me. ViperOne not.
Sent from my HTC One_M8 using Tapatalk
Iceberger said:
ARHD 11.1 worked for me. ViperOne not.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
It's well known that you have to use a stock (or a very close to stock) rom. Viper is highly modified so indeed that it doesn't work !
This implies for everyone
jkolner said:
Tried with Firewather and Sunshine but no luck.
Im on ViperS Rom, so do you have a link to the Rom you flashed and got S-Off on?
Click to expand...
Click to collapse
I believe it was OMJ's thread in the sprint folder. I also went to the older ones and flashed the one that was the oldest. http://forum.xda-developers.com/showthread.php?t=2729173
Once I did that I was able to check and see if sunshine would work and it said it would then ran sunshine, flashed the updated firmware and that's where I am now.
Good luck
Hi,
I know Rogers doesn't have an RUU for the M8, but when I had my M7, I was using an RUU that was for Brightstar (decrypted) and it worked great. It turned my M7 into a WWE Dev Edition with Sense and the OTAs worked. All i had to do was change my CID to BS_US001 and RUU away. I needed to install a LOT of OTAs afterwards but who doesn't like updating, right?!
Would anyone know what RUU I could use on my Rogers M8 that would be the equivalent of that? Doesn't need to be rogers specific, it could be a world wide edition, I'd bu happy with that. I think that AT&T is the US carrier that uses the same type of network so I'm not sure if there is an AT&T RUU out there. Searched XDA and Google and I haven't found an RUU that I am confident would work.
Thank you.
This is the closest thing I could find and it looks like it could work, but it's an EXE RUU, I've never used that before.
http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
Nic2112 said:
This is the closest thing I could find and it looks like it could work, but it's an EXE RUU, I've never used that before.
http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
Click to expand...
Click to collapse
All "official" RUUs are released as Windows .exe files. If you used something else before (RUU that was not an .exe), it was modified by a XDA user.
---------- Post added at 10:25 AM ---------- Previous post was at 10:18 AM ----------
Nic2112 said:
I think that AT&T is the US carrier that uses the same type of network so I'm not sure if there is an AT&T RUU out there. Searched XDA and Google and I haven't found an RUU that I am confident would work.
Click to expand...
Click to collapse
Latest AT&T RUU:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Modified bootable (no PC required) version:
http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
I think you are right, that Rogers uses a similar or same network to AT&T. Rogers was in fact partially owned by AT&T at one point. But you should confirm the network is the same. Be aware that the radio is included on the RUU, so if there are any network differences, using the wrong RUU can impact reception.
In particular, the international WWE firmware/radio is known to not work well in North America. Although you won't find an RUU for WWE anyway. For the most part, only US carriers have RUUs.
Other than that, the RUUs I linked are fine. You will need to change CID (or s-off may be necessary) otherwise it will install fine. Hardware on all GSM M8s (but not CDMA versions) are essentially the same aside from some cosmetic differences. The RUU you posted is also fine, as the US Dev Edition is designed to support AT&T's network (and likely also Rogers).
EDIT: Fixed the link to bootlable RUU above.
redpoint73 said:
Other than that, the RUUs I linked are fine. You will need to change CID (or s-off may be necessary) otherwise it will install fine. Hardware on all GSM M8s (but not CDMA versions) are essentially the same aside from some cosmetic differences. The RUU you posted is also fine, as the US Dev Edition is designed to support AT&T's network (and likely also Rogers).
Click to expand...
Click to collapse
That is great information, thank you very much. I'm S-OFF with GOOGL001 as CID, all I need to do is change it to one that matches the text file in the RUU, or I think BS_US001 will work.
Thanks again!
redpoint73 said:
Latest AT&T RUU:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Modified bootable (no PC required) version:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Click to expand...
Click to collapse
Did you mean to link to the same file twice?
Interesting, I have 3 EXE RUUs and they all have the same behavior, I click them ,the installer starts, I accept the agreement, and then it closes completely.
I would like to know the outcome as well. I did the GPE conversion and now want to go back to stock Rogers or the Developers Edition Sense but can't find a Rogers RUU and the Dev one is an exe.
Sent from my HTC One_M8 using Tapatalk
Elisha said:
I would like to know the outcome as well. I did the GPE conversion and now want to go back to stock Rogers or the Developers Edition Sense but can't find a Rogers RUU and the Dev one is an exe.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I managed to get the RUU to go further but it tells me it can't update my device. Maybe I put the wrong CID or have the wrong MID
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: BS_US001
Try changing CID back to Rogers maybe?
Where did you get the RUU?
Sent from my HTC One_M8 using Tapatalk
Elisha said:
Try changing CID back to Rogers maybe?
Where did you get the RUU?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I don't remember what the original CID was. The RUU is the one from this thread.
You mean the Develepor edition one?
Elisha said:
You mean the Develepor edition one?
Click to expand...
Click to collapse
I tried both, none work. On my M7, I had a RUU in ZIP format and the CID I needed was BS_US001, but I tried that and BS_US002 and neither work.
Maybe my MID doesn't match but I don't know. It's easy with a ZIP, there is a text fire that tells you what it looks for but I never used an EXE before.
Nic2112 said:
I tried both, none work. On my M7, I had a RUU in ZIP format and the CID I needed was BS_US001, but I tried that and BS_US002 and neither work.
Maybe my MID doesn't match but I don't know. It's easy with a ZIP, there is a text fire that tells you what it looks for but I never used an EXE before.
Click to expand...
Click to collapse
That sucks. I kinda want to for back from Sense from my GPE conversion and can't find the proper RUU to flash via fastboot to get back to it.
The one linked in this thread is dead: http://forum.xda-developers.com/showthread.php?t=2733523
When I run the Dev RUU exe, it says do you want to update from a 2.X.X.X version to a 1.x.x.x. version which didn't make sense so I quit it.
Between the instructions here here, and then the HBOOT from here, the Brightstar RUU is installing.
I'll probably RUU back to GPE when it gets released for the HTC M8
Update: The Brightstar RUU worked but no APNs were discovered, had to configure one manually. Since Redpoint said that WWE editions don't work as well here, I'm giving the AT&T RUU a try right now. It's installing, I'm curious to see if it will set the Rogers APN automatically this time. It's also 4.4.3 instead of 4.4.0 so I might not need to download as many updates.
Update 2: AT&T is a bit worse, it's very AT&T flavored and seems even more out of place on Rogers. I think the only way would be to flash the HBOOT, then a custom recovery, restore a Rogers backup, set the CID and Recovery back to stock, and then factory reset.
I've decided to RUU back to GPE and stick to it. If L is released November 1st, it should be available as an OTA shortly after and I know that when that comes out, I'll want it so for a month's worth of usage, I'll stick to GPE.
Nic2112 said:
Did you mean to link to the same file twice?
Click to expand...
Click to collapse
Nope. My bad, bootable RUU is here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
---------- Post added at 12:01 PM ---------- Previous post was at 11:54 AM ----------
Nic2112 said:
Update 2: AT&T is a bit worse, it's very AT&T flavored and seems even more out of place on Rogers. I think the only way would be to flash the HBOOT, then a custom recovery, restore a Rogers backup, set the CID and Recovery back to stock, and then factory reset.
Click to expand...
Click to collapse
Yes, AT&T stock ROMs suck, with all the bloat and gimped features.
Really, if you decide you want a Sense experience, I would just recommend flashing a custom ROM of your choice and the radio that is friendly with your network.
The first link goes nowhere and the second one is one I was having trouble with as the 1.54.401.5-W_Splash.zip leads to a dead link as well.
Nic2112 said:
I don't remember what the original CID was. The RUU is the one from this thread.
Click to expand...
Click to collapse
ROGER001
Nic2112 said:
I managed to get the RUU to go further but it tells me it can't update my device. Maybe I put the wrong CID or have the wrong MID
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: BS_US001
Click to expand...
Click to collapse
Ok might be a bit outdate info seeing as you already decided to stick to GPE but yes the MID was wrong. MID for AT&T, Unlocked Version and Developer Edition are 0P6B12000 not 16000
BerndM14 said:
Ok might be a bit outdate info seeing as you already decided to stick to GPE but yes the MID was wrong. MID for AT&T, Unlocked Version and Developer Edition are 0P6B12000 not 16000
Click to expand...
Click to collapse
Thank you for the information. Since we might be a few short weeks from L, I figured no point in risking a brick at this time but I might change the MID anyways because I think the developer edition gets OTAs first.
Nic2112 said:
Thank you for the information. Since we might be a few short weeks from L, I figured no point in risking a brick at this time but I might change the MID anyways because I think the developer edition gets OTAs first.
Click to expand...
Click to collapse
Yeah they do, I also already downloaded all the necessary things to convert my device to a Developer Edition. :good:
I have never gotten my MMS to work on my Unlocked AT&T HTC One M8. I recently read that this is a problem because I'm not using a Tmobile branded M8, and that if I updated to a Tmobile ROM it would fix my MMS issues.
http://support.t-mobile.com/thread/66514
I have a solution that will work however I offer this with no-warranty and for a use at your own risk, however I can say I have done this for maybe about 60 T-Mobile customers who brought their HTC One m7 from AT&T. I have done this as well. HTC m7 phone are all built with the exact same parts, the only thing that makes the phone operate differently is the firmware for the baseband, and of course the rom. However HTC offer's a RUU (Rom Upgrade Utility) right on their support page. This reinstalls the android os, along with new baseband and firmware versions. All you have to do is run the T-Mobile HTC One m7 RUU that is on the HTC website. You can use the link here to download the RUU from the HTC website. It generally about 1GB in file size, as this is not just the Android OS, but this is the software for the phone's hardware to flash it from an AT&T HTC One to a T-Mobile HTC One.This will also enable your phone to receive Over-The-Air updates from T-Mobile as well. Again I and T-Mobile will not support this. However I can say from personal experience and also on behalf of the people I done this for that it works. *Also you will get to enjoy the T-Mobile Wi-Fi Calling as well. Your phone will act and perform just like the T-Mobile version will after this. After all they all have the exact same parts under the hood. Just different firmware, and operating systems. This converts it all over to T-Mobile
Click to expand...
Click to collapse
Relevant Info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I have since rooted my device, unlocked the bootloader, done S-OFF, and set CID to SuperCid.
I just wan't to confirm that I'm doing the right thing so I don't end up bricking my phone.
Do I need to change the MID or CID of my device?
Do I need to update through RUU to a Tmobile ROM in order to make make all the relevant firmware changes to convert my M8 into a Tmobile branded phone rather than AT&T or can I just flash through the the Recovery and flash a Tmobile ROM?
My understanding is that reinstalling the Tmobile ROM will keep S-OFF, SuperCid, and Unlocked Bootloader, but will NOT keep Root. Is this correct? Will it keep my custom recovery?
Sorry for all the questions. Thank you for your time!
NiklasK said:
I have never gotten my MMS to work on my Unlocked AT&T HTC One M8. I recently read that this is a problem because I'm not using a Tmobile branded M8, and that if I updated to a Tmobile ROM it would fix my MMS issues.
http://support.t-mobile.com/thread/66514
Relevant Info:
I have since rooted my device, unlocked the bootloader, done S-OFF, and set CID to SuperCid.
I just wan't to confirm that I'm doing the right thing so I don't end up bricking my phone.
Do I need to change the MID or CID of my device?
Do I need to update through RUU to a Tmobile ROM in order to make make all the relevant firmware changes to convert my M8 into a Tmobile branded phone rather than AT&T or can I just flash through the the Recovery and flash a Tmobile ROM?
My understanding is that reinstalling the Tmobile ROM will keep S-OFF, SuperCid, and Unlocked Bootloader, but will NOT keep Root. Is this correct? Will it keep my custom recovery?
Sorry for all the questions. Thank you for your time!
Click to expand...
Click to collapse
The information you quoted is incorrect. The AT&T and T-Mobile versions are two different hardware versions. AT&T M8 being m8_ul_ca and T-Mobile being m8_ul. They do not have the same network compatibility.
At&t - 0P6B1200 supported bands (in MHz):
3G=850, 1900, 2100
LTE=700, 850, 1700, 1800, 1900, 2100, 2600
T-Mobile - 0P6B1300 supported bands:
3G=850, 1700, 1900, 2100
LTE=700, 1700, 2100
As you can see, T-mobile has an extra HSPA band that AT&T doesn't support. This is also why the AT&T model does not support 42.2Mb per second HSPA+ downloads while the T Mobile version does. AT&T maxes out at 21.1Mb over HSPA. You'll also note that the AT&T version supports more LTE bands, however, those are bands that T-Mobile does not operate it's LTE network on so really it doesn't help. Long story short the devices are actually not the same.
Now, you can still operate an AT&T model on T-Mobile's network with a large degree of success depending on your coverage area and what network bands are currently being utilized. The 700MHz band has not been switched on everywhere for T-Mobile just yet so you would be limited to only two bands of LTE support.
All that being said, if you do flash a T-Mobile RUU, you will have wifi calling support you will have the correct device and network settings for T-Mobile, including MMS, and you may notice little to no loss of network performance on your device, however, you may notice significant loss of performance. It depends solely on the network in your area. After flashing a RUU, you will have the T-Mobile software & firmware as well as maintain your s-off status, but you will not effect supported network bands. Also, if you want to receive OTA updates you will need to change your model ID aka MID.
Behold_this said:
All that being said, if you do flash a T-Mobile RUU, you will have wifi calling support you will have the correct device and network settings for T-Mobile, including MMS, and you may notice little to no loss of network performance on your device, however, you may notice significant loss of performance. It depends solely on the network in your area. After flashing a RUU, you will have the T-Mobile software & firmware as well as maintain your s-off status, but you will not effect supported network bands. Also, if you want to receive OTA updates you will need to change your model ID aka MID.
Click to expand...
Click to collapse
Ok I understand. I wasn't aware that the AT&T model didn't go up to the same data rates as the Tmobile one. The only reason I bought the AT&T one was because I liked the color better
So as far as using the T-Mobile RUU, I'm set and don't need to make any further adjustments (ex: MID, CID, Bootloader Lock, or S-Off)?
If I want to receive OTA updates from tmobile after changing the MID do I need to get S-Off or relock the bootloader or change CID?
NiklasK said:
Ok I understand. I wasn't aware that the AT&T model didn't go up to the same data rates as the Tmobile one. The only reason I bought the AT&T one was because I liked the color better
So as far as using the T-Mobile RUU, I'm set and don't need to make any further adjustments (ex: MID, CID, Bootloader Lock, or S-Off)?
If I want to receive OTA updates from tmobile after changing the MID do I need to get S-Off or relock the bootloader or change CID?
Click to expand...
Click to collapse
You need to change your MID [how to] change your MID without an eng bootloader and then run the RUU. I don't think changing the CID is necessary but you can do that too if you want.
Once you're S-OFF you don't ever have to relock the bootloader for anything. Just leave it unlocked.
If you don't want to do RUU then just restore a stock T-Mobile nandroid, preferably an earlier version. That way you can see if your device does the OTA updates like it's supposed too. For me, I don't know if anyone else had the problem, I had to flash the first OTA manually and then the device did the rest automatically. This was with a conversion from International to Developer Edition.
So as far as Im reading I need to LOCK my bootloader in order to use the Tmobile RUU. Yet you say I just need to change my MID. Can you confirm that the RUU will still work on an unlocked bootloader?
Would I still need to change my MID if I just used Recovery to flash a Tmobile ROM?
EDIT:
Just changed my MID to 0P6B13000 (Tmobile USA)
Am I all good to go now to use the RUU without bricking?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
NiklasK said:
So as far as Im reading I need to LOCK my bootloader in order to use the Tmobile RUU. Yet you say I just need to change my MID. Can you confirm that the RUU will still work on an unlocked bootloader?
Would I still need to change my MID if I just used Recovery to flash a Tmobile ROM?
EDIT:
Just changed my MID to 0P6B13000 (Tmobile USA)
Am I all good to go now to use the RUU without bricking?
Click to expand...
Click to collapse
Yeah go for it. Shouldn't brick unless unforeseen connection issue with your PC.
*edit
Also keep in mind only HSPA+ speeds will be affected. If you are in an area with T-Mobile LTE support, speeds will not be affected. So you may be lucky and have no issues whatsoever.
Behold_this said:
Yeah go for it. Shouldn't brick unless unforeseen connection issue with your PC.
*edit
Also keep in mind only HSPA+ speeds will be affected. If you are in an area with T-Mobile LTE support, speeds will not be affected. So you may be lucky and have no issues whatsoever.
Click to expand...
Click to collapse
My area is predominately LTE =]
So I just downloaded this TMOUS-M8-3.32.531.2-Stock-TWRP.zip
However, I found this in a thread on xda:
3.16 hboot = 1.12 / 1.54 software
3.18 hboot = 2.22 software
3.19 hboot = 3.xx software
Click to expand...
Click to collapse
Since my hboot currently is 3.16 does that mean I can only flash 1.12/1.54? And not the 3.32.531.2 I downloaded since it corresponds to 3.19 hboot?
NiklasK said:
My area is predominately LTE =]
So I just downloaded this TMOUS-M8-3.32.531.2-Stock-TWRP.zip
However, I found this in a thread on xda:
Since my hboot currently is 3.16 does that mean I can only flash 1.12/1.54? And not the 3.32.531.2 I downloaded since it corresponds to 3.19 hboot?
Click to expand...
Click to collapse
Personally I would just flash the T -Mobile 3.32 RUU and be done with it
http://dl3.htc.com/application/RUU_...G_20.56.4198.02_F_release_394971_signed_2.exe
*edit
Well maybe not done with it, I'd still flash supersu, rw mod or custom kernel, and remove the bloat, but I think you get what I mean.
Behold_this said:
Personally I would just flash the T -Mobile 3.32 RUU and be done with it
http://dl3.htc.com/application/RUU_...G_20.56.4198.02_F_release_394971_signed_2.exe
*edit
Well maybe not done with it, I'd still flash supersu, rw mod or custom kernel, and remove the bloat, but I think you get what I mean.
Click to expand...
Click to collapse
Having so much trouble getting the RUU Installer to work. Tried it on 2 different Windows computers (8.1 and 7) with the installer always exiting. Does the RUU do anything special that flashing through cmd prompt or recoveries wont do? At this point I'd much rather do that.
NiklasK said:
Having so much trouble getting the RUU Installer to work. Tried it on 2 different Windows computers (8.1 and 7) with the installer always exiting. Does the RUU do anything special that flashing through cmd prompt or recoveries wont do? At this point I'd much rather do that.
Click to expand...
Click to collapse
Like I said previously, I'd personally go for an older version first. That way you can test to make sure the conversion is 100% by letting the device do the OTA updates. What's the point of converting straight to the latest version and leaving yourself unsure whether OTA will work once Lollipop comes out?
I'd go for one of the 1.xx.xxx.x versions and update it to the latest, but that's me...Just a thought/suggestion.
BerndM14 said:
Like I said previously, I'd personally go for an older version first. That way you can test to make sure the conversion is 100% by letting the device do the OTA updates. What's the point of converting straight to the latest version and leaving yourself unsure whether OTA will work once Lollipop comes out?
I'd go for one of the 1.xx.xxx.x versions and update it to the latest, but that's me...Just a thought/suggestion.
Click to expand...
Click to collapse
My apologies, I wasn't totally clear with my intentions. I just wanted to flash the stock latest ROM from T-mobile that I knew would fix my MMS issue. Then I would make a backup of that so I could always recover my phone to that point. I was always going to flash custom ROMs based off Tmobile base firmware, just wanted to have a fallback backup.
NiklasK said:
My apologies, I wasn't totally clear with my intentions. I just wanted to flash the stock latest ROM from T-mobile that I knew would fix my MMS issue. Then I would make a backup of that so I could always recover my phone to that point. I was always going to flash custom ROMs based off Tmobile base firmware, just wanted to have a fallback backup.
Click to expand...
Click to collapse
I know what the intention is, I'm just stating what I personally would have done. Like I said before, when I converted to Dev Edition I had to manually install the OTA and flash the firmware twice before my device picked up the newest OTA updates and installed it automatically. Don't know why this is...Which is why I personally go back at least 2 or so versions prior to the latest version available to test and make sure that my device can do the OTA updates. You don't have to do this, just figured it would be good to know all is in working order for when 5.0 launches, else you'd probably have to install/flash manually OR go back a version in order for it to update automatically. It's fine either way I suppose, no "biggie".
RUU is the easiest way to do it but you can also just head over to the collection thread, download the latest nandroid backup from there and restore it in TWRP. Then head over to the update thread you'll find a collection of OTA.zip files. Download the one for T-Mobile and install it. You can also extract the firmware.zip from the OTA.zip and flash that in RUU mode(Twice flash) just to make sure the firmware is all in place.
You'll also then have a downloaded backup for nandroid(2.22.531.5) and you'll also have the stock recovery(Which is available in the firmware.zip file) for future references.
Collection for stock nandroid backups Latest nandroid for x.xx.531.x T-Mobile is 2.22.531.5 So you'll have to do OTA's anyways if you want that one.
OTA Zip collection Yours will be under "branded"
Afterwards you can just flash custom recovery and make a nandroid backup of 3.32.531.x for T-Mobile then you're set. You don't have to worry about making a backup of stock recovery as it is in the firmware.zip file like previously mentioned.
All that said, like mentioned before, RUU is probably the easiest way. Try an older version, should be available in the T-Mobile section.
http://forum.xda-developers.com/tmobile-htc-one-m8
I know i need to pay for sunshine to get S-Off,i'm considering doing it sometime soon,but just asking,would firewater work if i flashed rom to earlier version of android,like 4.4.0 or so? Also would it need to be official or could costume rom work too? Sorry for another annoying S-Off question. :angel:
No does not work.
SynoX4 said:
Sorry for another annoying S-Off question. :angel:
Click to expand...
Click to collapse
It is annoying, since the exact same question was already asked (and answered) twice yesterday (and also easy to search and look for besides that) if you just scroll down on the first page of threads. It looks like you are new to XDA. But it would be your benefit to know that most every question you can think of about this device has already been posted, and the knowledge easily obtainable by just looking/searching. Only after doing your due diligence to search (and not finding anything) should you start a new thread.
Also, flashing different ROMs won't enable old s-off exploits that have since been patched by HTC. It doesn't work that way, HTC is not that stupid. The key is in hboot (not the ROM which can be easily changed) which cannot be "downgraded" unless you have s-off already.
In any case, firewater was an online service, so it doesn't work no matter what version hboot you have, since the dev stopped supporting firewater.
redpoint73 said:
It is annoying, since the exact same question was already asked (and answered) twice yesterday (and also easy to search and look for besides that) if you just scroll down on the first page of threads. It looks like you are new to XDA. But it would be your benefit to know that most every question you can think of about this device has already been posted, and the knowledge easily obtainable by just looking/searching. Only after doing your due diligence to search (and not finding anything) should you start a new thread.
Also, flashing different ROMs won't enable old s-off exploits that have since been patched by HTC. It doesn't work that way, HTC is not that stupid. The key is in hboot (not the ROM which can be easily changed) which cannot be "downgraded" unless you have s-off already.
In any case, firewater was an online service, so it doesn't work no matter what version hboot you have, since the dev stopped supporting firewater.
Click to expand...
Click to collapse
Alright,thanks,sorry for late reply. I've been going around xda forum and i saw that for some roms it says it requiers either htc dev unlocked or s-off. I can unlock phone with htc dev,does that mean i dont need s-off to flash rom,kernel and firmware?
SynoX4 said:
Alright,thanks,sorry for late reply. I've been going around xda forum and i saw that for some roms it says it requiers either htc dev unlocked or s-off. I can unlock phone with htc dev,does that mean i dont need s-off to flash rom,kernel and firmware?
Click to expand...
Click to collapse
You'll need S-Off to flash firmware. But there are other ways to update without flashing a firmware.zip, usually by going back to stock ROM and recovery, and taking the OTAs provided by your carrier or by running an RUU.
xunholyx said:
You'll need S-Off to flash firmware. But there are other ways to update without flashing a firmware.zip, usually by going back to stock ROM and recovery, and taking the OTAs provided by your carrier or by running an RUU.
Click to expand...
Click to collapse
I see. Well for RUU,can i get one with higher version than my phone version-main? Also i just got model id error 130 on ruu installation with only last number differing.
SynoX4 said:
I see. Well for RUU,can i get one with higher version than my phone version-main? Also i just got model id error 130 on ruu installation with only last number differing.
Click to expand...
Click to collapse
RUU stands for ROM Update Utility. So yes, since it's purpose is to update, it should be higher than your current firmware.
Error 130 is because you aren't running the right RUU.
Get into fastboot and do fastboot getvar all, then post the readout here minus your serial# and IMEI. I'll link you to the proper RUU.
xunholyx said:
RUU stands for ROM Update Utility. So yes, since it's purpose is to update, it should be higher than your current firmware.
Error 130 is because you aren't running the right RUU.
Get into fastboot and do fastboot getvar all, then post the readout here minus your serial# and IMEI. I'll link you to the proper RUU.
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.22.30306251.27G
version-cpld: None
version-microp: None
version-main: 3.33.401.6
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m8_dugl
platform: hTCBmsm8974
modelid: 0P6B64000
cidnum: HTC__032
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 4c3fbd70
hbootpreupdate: 11
gencheckpt: 0
It's dual sim. I know it says up there but just because you might skip it.
SynoX4 said:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.22.30306251.27G
version-cpld: None
version-microp: None
version-main: 3.33.401.6
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m8_dugl
platform: hTCBmsm8974
modelid: 0P6B64000
cidnum: HTC__032
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 4c3fbd70
hbootpreupdate: 11
gencheckpt: 0
It's dual sim. I know it says up there but just because you might skip it.
Click to expand...
Click to collapse
Here's the RUU you need. It'll bump you to Lollipop.
xunholyx said:
Here's the RUU you need. It'll bump you to Lollipop.
Click to expand...
Click to collapse
Awesome,thanks. I'll update when it downloads,shouldn't be too long.
xunholyx said:
Here's the RUU you need. It'll bump you to Lollipop.
Click to expand...
Click to collapse
Error 132 signature something... I did lock bootloader before doing it.
Will do nandroid recovery to android 4.4.3,lock again and try.
SynoX4 said:
Awesome,thanks. I'll update when it downloads,shouldn't be too long.
Click to expand...
Click to collapse
Wait. Dual sim? And I missed it anyways. lol. Hung over and just smoked a joint.
You'll have to change your MID as well.
You can find out how here.
I'm guessing this will work only, because I am unfamiliar with the dual sim. But since you are already running WWE firmware on your device, I think it will.
xunholyx said:
Wait. Dual sim? And I missed it anyways. lol. Hung over and just smoked a joint.
You'll have to change your MID as well.
You can find out how here.
I'm guessing this will work only, because I am unfamiliar with the dual sim. But since you are already running WWE firmware on your device, I think it will.
Click to expand...
Click to collapse
Thing is,that requires s-off which i don't have...
SynoX4 said:
Thing is,that requires s-off which i don't have...
Click to expand...
Click to collapse
Then you'll probably have to go back to stock to update via OTAs.
Go to this thread, and do a search for what it says in your version-main for a stock ROM backup (if you don't have one that you made yourself) and also for the stock recovery.
xunholyx said:
Then you'll probably have to go back to stock to update via OTAs.
Go to this thread, and do a search for what it says in your version-main for a stock ROM backup (if you don't have one that you made yourself) and also for the stock recovery.
Click to expand...
Click to collapse
I have stock ROM backup for version 4.4.3, but when i tried to update it just sent me into twrp,and i tried to install OTA from there but it just sent me some error. Do you suggest i move to 4.4.3,get stock recovery and then do OTAs? Also closest numbers to my main version in that thread are 3.32 and 3.34 for both ROM and recovery,if this doesn't work which one should i get?
SynoX4 said:
I have stock ROM backup for version 4.4.3, but when i tried to update it just sent me into twrp,and i tried to install OTA from there but it just sent me some error. Do you suggest i move to 4.4.3,get stock recovery and then do OTAs? Also closest numbers to my main version in that thread are 3.32 and 3.34 for both ROM and recovery,if this doesn't work which one should i get?
Click to expand...
Click to collapse
I am really unfamiliar with the dual sim, so your best bet would to be to ask in that thread.
xunholyx said:
I am really unfamiliar with the dual sim, so your best bet would to be to ask in that thread.
Click to expand...
Click to collapse
Alright,thanks for all your help.
Greetings to you all. Can someone please give me the best advice what is the best thing to do with my unit now. I only want to install and enjoy custom roms and kernel on my phone but I don't have a regular HTC 10.
Mine is m10h. It won't even allow me update to Nougat.
I just got it today from online selling.
My questions about this unit.
1. What is the difference of this model to regular HTC 10.?
2. Can I go ahead to usual way of unlocking bootloader, flash recovery and flash the custom roms I like ex. Leedroid, Viper, RR, Lineage.? Or I need to flash convert the firmware first or flash RUU.
I attached the system information of my phone on bootloader.
I'd appreciate any help. Please post links which you think will be helpful for me. Thank you.
conqueror_25 said:
Greetings to you all. Can someone please give me the best advice what is the best thing to do with my unit now. I only want to install and enjoy custom roms and kernel on my phone but I don't have a regular HTC 10.
Mine is m10h. It won't even allow me update to Nougat.
I just got it today from online selling.
My questions about this unit.
1. What is the difference of this model to regular HTC 10.?
2. Can I go ahead to usual way of unlocking bootloader, flash recovery and flash the custom roms I like ex. Leedroid, Viper, RR, Lineage.? Or I need to flash convert the firmware first or flash RUU.
I attached the system information of my phone on bootloader.
I'd appreciate any help. Please post links which you think will be helpful for me. Thank you.
Click to expand...
Click to collapse
What makes you think it's not "regular"?
It's just a WWE HTC 10 (pme_uhl) from Taiwan region.
Nothing different about it, that I can see.
Should be no problem to unlock it and flash custom roms for the HTC 10.
Hey @santod040. Thanks for paying attention to my concern. I've used your roms before on my M7. Haha.
I was also surprised to know about this model. Thought all HTC 10 are the same. When I check About Phone - Phone Identity says HTC_M10h.
I will unlock the bootloader now. But my I'm thinking with my current firmware if I'll be able to flash any roms here without facing any issues. Because it's stuck to Android MM. Won't let me update to Nougat.
Do I need to update the firmware first? Before flashing custom roms or my current firmware will be fine. Please advise.
Software version.
conqueror_25 said:
Software version.
Click to expand...
Click to collapse
I would first update to Nougat firmware for your variant, either by stand alone firmware zip or full RUU.
RUU you should be looking for:
2PS6IMG_PERFUME_[email protected]61226_79.07_F_release_509037_combined_signed_2_4
Sent from my HTC6545LVW using Tapatalk
Yes. That's exactly what I need to hear. Can you please post a link here on the file and instructions how to update my firmware. Please. My phone totally on stock right now. I'm sorry if I'm too much already to ask you for all this.
I really appreciate your help Sir! Thank you so much.
conqueror_25 said:
Yes. That's exactly what I need to hear. Can you please post a link here on the file and instructions how to update my firmware. Please. My phone totally on stock right now. I'm sorry if I'm too much already to ask you for all this.
I really appreciate your help Sir! Thank you so much.
Click to expand...
Click to collapse
Try this link: RUU
Download file
Rename to: 2PS6IMG.zip
Place in root of External Storage(SD Card)
Boot to Download Mode
Press volume+ up to proceed with flash
"should" update your device to Nougat and WILL wipe it as well.
So be sure to save anything that may be important to you (photos, etc) if that applies yet.
After the above process, you should be able to flash TWRP, followed by any current custom roms for HTC 10.
conqueror_25 said:
Yes. That's exactly what I need to hear. Can you please post a link here on the file and instructions how to update my firmware. Please. My phone totally on stock right now. I'm sorry if I'm too much already to ask you for all this.
I really appreciate your help Sir! Thank you so much.
Click to expand...
Click to collapse
I've already provided the link for that; and also instructions; in the other thread you were posting in.
https://forum.xda-developers.com/showpost.php?p=73904200&postcount=615
I guess its time to interrupt your conversation.
I'm having 2.41.401.41 pmeuhl. After some battery drain issues on venom rom, i did a nandroid restore to stock rom. But still i'm facing battery drain issues. There is one 2.41.401.41 link https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297in this thread.
But it failed with an error- HEADER_ERROR while doing the sdcard method.
Now i think i need the asian version since this phone is from UAE. so is there an asian version of 2.41.401.41 ??
Awesome! I have more confidence now to do this step because of your help guys..
So after I have updated to latest Nougat / flash RUU. I will then proceed to unlocking bootloader, flash recovery then roms etc. Am I correct?
And please take note that my phone is not S-OFF. The steps are still safe with S-On right?
Thank you very much for taking your time to help me out. :good:
conqueror_25 said:
Awesome! I have more confidence now to do this step because of your help guys..
So after I have updated to latest Nougat / flash RUU. I will then proceed to unlocking bootloader, flash recovery then roms etc. Am I correct?
And please take note that my phone is not S-OFF. The steps are still safe with S-On right?
Thank you very much for taking your time to help me out. :good:
Click to expand...
Click to collapse
Correct
Unlocked bootloader is sufficient
Sent from my HTC6545LVW using Tapatalk
santod040 said:
Correct
Unlocked bootloader is sufficient
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Do unlocked bootloader allows RUU zip to be flashed??
You're the best mate @santod040. Thanks a lot!?
$tark3 said:
Do unlocked bootloader allows RUU zip to be flashed??
Click to expand...
Click to collapse
As long as its for your variant and not a downgrade/lower version.
Sent from my HTC6545LVW using Tapatalk
santod040 said:
As long as its for your variant and not a downgrade/lower version.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Can you tell me the correct RUU Zip file for my version??
No idea what you have or what you've changed on it....
How about posting the output of:
fastboot getvar all
Then we can go from there.
Sent from my HTC6545LVW using Tapatalk
Figured it out. My SD card was corrupted. Used another SD and worked like charm
I've got the exact same phone (m10H) that I'm trying to work with, but in my case I'm trying to get it to work with Verizon. I'm hearing a lot of conflicting information, about installing radios, or using DFS to enable bands, to it being hardware locked from being on Verizon. I'm at wit's end trying to get this to work! Here's my Getvar All
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: FA67EBN02696
(bootloader) current-slot:
(bootloader) imei: 354261073374779
(bootloader) version-main: 2.51.617.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: 11111111
So how do I get Verizon on this thing? Any help would be appreciated.
Kreuzweir said:
I've got the exact same phone (m10H) that I'm trying to work with, but in my case I'm trying to get it to work with Verizon. I'm hearing a lot of conflicting information, about installing radios, or using DFS to enable bands, to it being hardware locked from being on Verizon. I'm at wit's end trying to get this to work! Here's my Getvar All
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: FA67EBN02696
(bootloader) current-slot:
(bootloader) imei: 354261073374779
(bootloader) version-main: 2.51.617.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: 11111111
So how do I get Verizon on this thing? Any help would be appreciated.
Click to expand...
Click to collapse
Verizon RUU
Sent from my HTC6545LVW using Tapatalk
Thanks for the quick reply! I took your advice and downloaded the Verizon RUU found here https://androidfilehost.com/?fid=24545065934258324 , which is DOTTAT_VZW10_1.19.605.9_s_on.exe . The problem is, the phone gets stuck on "Preparing your phone" during the initialization phase of startup. This is where I always get stuck. Here's my GetVar All
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) imei: 354261073374779
(bootloader) version-main: 1.19.605.9
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: 11111111
How can I proceed?
---------- Post added at 05:29 AM ---------- Previous post was at 04:52 AM ----------
It should be noted that this is the gold international one, I think. Model number 2PS6200. I think the bands aren't enabled by default, but is it possible to add them in with something like CDMA tools? I can't seem to find an answer online. Unfortunately I'm stuck with this phone one way or another, so if there's a way to make this work I'm all ears.