Related
OK. I'm a little bit lost in the HTC world!
I've had a Samsung Galaxy Note II for the last year and have just replaced it with the HTC ONE (M8). I found the whole rooting and ROM procedure relatively straight forward with the Note II. In a nutshell you:
1) Rooted with a Windows based application
2) Installed / Flashed a recovery system
3) Flashed a custom ROM using a Windows based application called ODIN
And that was that. Pretty straightforward. Having had a nose around the HTC forum it's awash with clever folk using abbreviations and acronyms like CID, RUU and S-OFF...!
My M8 is on EE network in the UK which I know is CID ORANG001. What I would like though is to convert my M8 to a generic European M8 so I can receive the latest HTC updates rather then await EE to push out their version. This therefore prompts me to ask the following questions:
1) Is this something we will be able to achieve?
2) What is the (potential) process to achieve this (assuming something similar for the M7 already exists)?
2) Will over the air updates work?
I've read numerous posts which seem contradicting. Some talk about a simple change of the CID others mention S-OFF as the GOD of everything related to the subject. If I were to guess, changing the CID seems too simple, but I'm guessing once changed to a generic EU CID it's possible to receive HTC's OTA updates? Or am I wrong there? Or having another guess I would assume I'd need to go down the lines similar to Samsung process of rooting or S-OFF (security off?) and flashing a generic stock EU ROM?
So what CAN currently be achieved and what CAN'T currently be achieved?
I guess I could do with a little background on these processes and the terminology used.
Any help, greatly appreciated.
Can :
Unlock the bootloader and flash a custom recovery to install a custom rom based on the latest firmware. You are depending on rom updates from the dev if he updates it to the latest software/firmware
Can't :
S-off
Change cid
Get ota via another rom
Run a ruu because they are simply not available
So to receive ota you need your original stock rom. And before you start messing around please make a stock nandroid backup and store it !
http://forum.xda-developers.com/showthread.php?t=2701376
Chris_c81 said:
OK. I'm a little bit lost in the HTC world!
I've had a Samsung Galaxy Note II for the last year and have just replaced it with the HTC ONE (M8). I found the whole rooting and ROM procedure relatively straight forward with the Note II. In a nutshell you:
1) Rooted with a Windows based application
2) Installed / Flashed a recovery system
3) Flashed a custom ROM using a Windows based application called ODIN
And that was that. Pretty straightforward. Having had a nose around the HTC forum it's awash with clever folk using abbreviations and acronyms like CID, RUU and S-OFF...!
My M8 is on EE network in the UK which I know is CID ORANG001. What I would like though is to convert my M8 to a generic European M8 so I can receive the latest HTC updates rather then await EE to push out their version. This therefore prompts me to ask the following questions:
1) Is this something we will be able to achieve?
2) What is the (potential) process to achieve this (assuming something similar for the M7 already exists)?
2) Will over the air updates work?
I've read numerous posts which seem contradicting. Some talk about a simple change of the CID others mention S-OFF as the GOD of everything related to the subject. If I were to guess, changing the CID seems too simple, but I'm guessing once changed to a generic EU CID it's possible to receive HTC's OTA updates? Or am I wrong there? Or having another guess I would assume I'd need to go down the lines similar to Samsung process of rooting or S-OFF (security off?) and flashing a generic stock EU ROM?
So what CAN currently be achieved and what CAN'T currently be achieved?
I guess I could do with a little background on these processes and the terminology used.
Any help, greatly appreciated.
Click to expand...
Click to collapse
Also not familiar anymore with HTC. After reading and reading and still not finding the exact answers to my questions, so I simply (after unlocking and flash TWRP recovery and backing up) tried to flash Virtuous ROM (1.54.401.5) over my German o2 device (1.12.206.17, CID O2___001). Everything worked except WiFi, so I tried a last call with mikes ARHD Rom 3.1, before going back to stock. And this ROM works brilliantly!
But I would also be happy if the OP questions could be answered...
@Mr Hofs
1. the WiFi problem discribed above could be firmware related?
2. When my Provider o2 brings out an update with firmware, can I simply relock bootloader and push the (perhaps) available firmware.zip it to the device via fastboot like mike explains in his firmware thread?
Edit :
Well that would be weird as both roms the OP flashed are based on 1.54.401 so i would say no.....
Mr Hofs said:
Can :
Unlock the bootloader and flash a custom recovery to install a custom rom based on the latest firmware. You are depending on rom updates from the dev if he updates it to the latest software/firmware
Can't :
S-off
Change cid
Get ota via another rom
Run a ruu because they are simply not available
So to receive ota you need your original stock rom. And before you start messing around please make a stock nandroid backup and store it !
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
OK thanks. Few more questions if I may.
So from the "can't" list, IF we can get the ability to change CID and have S-OFF in the future, would it provide the ability to receive OTA updates when HTC push them out, or are OTA updates simply out of the game entirely?
Sent from my HTC One_M8 using Tapatalk
Yes that should be possible , all you need then is
Changed cid
Stock rom
Stock kernel
Stock recovery
Or the ruu (if available)
Then the phone is ready for ota updates.
Mr Hofs said:
Yes that should be possible , all you need then is
Changed cid
Stock rom
Stock kernel
Stock recovery
Or the ruu (if available)
Then the phone is ready for ota updates.
Click to expand...
Click to collapse
Great thanks. Last question then, what is RUU?
I'll keep your thread bookmarked and attempt to get a backup in there.
Sent from my HTC One_M8 using Tapatalk
A ruu is a Rom Update Utility and it contains the rom, kernel, firmware, recovery (and some more stuff). When a ruu is installed its like the phone is factory stock.
Mr Hofs said:
A ruu is a Rom Update Utility and it contains the rom, kernel, firmware, recovery (and some more stuff). When a ruu is installed its like the phone is factory stock.
Click to expand...
Click to collapse
OK brilliant thanks. Really appreciate your help.
Sent from my HTC One_M8 using Tapatalk
Need to take my Verizon One M7 in for a replacement. Reception is killing me (keep dropping to 1X or weak 3G in outlying areas), calls drop more than they don't, and even getting mms generic errors. Tried multiple ROM's, multiple radios, stock recovery/ROM/reset, new SIM card...nothing works.
I did notice something though - when I first got this phone, they had trouble initializing the SIM in the store...thought nothing of it until I went to the corporate store for a replacement SIM and they couldn't get the replacement to activate from the phone...I am thinking I have bad hardware.
The guy was cool (he looked my stats up and was shocked at the dropped calls) but made a point to tell me it was likely behaving badly due to being rooted...would rather walk in with a plain vanilla phone and let them replace it or let me out of my extension and I will go back to my trusty ReZound, because this thing is useless as a phone as-is.
How do I get back to pure stock so I can take this in for a replacement?
ROM is NuSenseSIX-KitKat_m7vzw_RC7.4_071714
Radios from 4.10.605.3_NoBootImg_firmware
TWRP 2.7.08
Rooted (and hboot) using Firewater (have the red warning 'this is only for internal HTC use..." on the boot splash screen)
the_Damaged_one said:
Need to take my Verizon One M7 in for a replacement. Reception is killing me (keep dropping to 1X or weak 3G in outlying areas), calls drop more than they don't, and even getting mms generic errors. Tried multiple ROM's, multiple radios, stock recovery/ROM/reset, new SIM card...nothing works.
I did notice something though - when I first got this phone, they had trouble initializing the SIM in the store...thought nothing of it until I went to the corporate store for a replacement SIM and they couldn't get the replacement to activate from the phone...I am thinking I have bad hardware.
The guy was cool (he looked my stats up and was shocked at the dropped calls) but made a point to tell me it was likely behaving badly due to being rooted...would rather walk in with a plain vanilla phone and let them replace it or let me out of my extension and I will go back to my trusty ReZound, because this thing is useless as a phone as-is.
How do I get back to pure stock so I can take this in for a replacement?
ROM is NuSenseSIX-KitKat_m7vzw_RC7.4_071714
Radios from 4.10.605.3_NoBootImg_firmware
TWRP 2.7.08
Rooted (and hboot) using Firewater (have the red warning 'this is only for internal HTC use..." on the boot splash screen)
Click to expand...
Click to collapse
fastboot ruu would be the easiest way.
once ruu is complete you can write secure flag back to s-on and it will be 100% stock.
synisterwolf said:
fastboot ruu would be the easiest way.
once ruu is complete you can write secure flag back to s-on and it will be 100% stock.
Click to expand...
Click to collapse
Thanks synisterwolf...two questions:
1 - I assume one of these would be what I want for a full RUU (not 100% sure which one)?
(from http://forum.xda-developers.com/showthread.php?t=2485319)
2.10.605.1 Decrypted RUU
2.10.605.1 Signed RUU
Odexed Full Rom (4.10.605.3 4.4.2 Sense 6.0)
2 - I found this guide...if I use the updated RUU, is the rest of this process still valid?
http://forum.xda-developers.com/showthread.php?t=2475216
the_Damaged_one said:
Thanks synisterwolf...two questions:
1 - I assume one of these would be what I want for a full RUU (not 100% sure which one)?
(from http://forum.xda-developers.com/showthread.php?t=2485319)
2.10.605.1 Decrypted RUU
2.10.605.1 Signed RUU
Odexed Full Rom (4.10.605.3 4.4.2 Sense 6.0)
2 - I found this guide...if I use the updated RUU, is the rest of this process still valid?
http://forum.xda-developers.com/showthread.php?t=2475216
Click to expand...
Click to collapse
guide is correct but use this link for RUU:
http://forum.xda-developers.com/showthread.php?t=2765784
the one you posted is a rom that you flash in recovery and not a full RUU
Be sure to follow the "lock bootloader" instructions before you ruu. There is a command either done in adb with root or recovery flashable zip to get "locked" instead of "relocked". As you see above, it requires you to either be rooted our have custom recovery, so do it before ruu and s-on after ruu completes.
Side note: ruu will wipe the whole phone, so be sure to copy your pictures, music, etc to a PC before ruu.
Edit: I recommend the signed 2.x.x.x ruu as it is fully stock. The new one linked above is rooted, so you would have to unroot and all that after you ruu.
Sent from my HTC6500LVW using XDA Free mobile app
Thanks guys...any chance one of you has a link to the signed fully stock RUU?
edit: (or is that the one I found above on santod's thread that says it's signed? I am guessing signed means fully stock, not rooted, etc?)
the_Damaged_one said:
Thanks guys...any chance one of you has a link to the signed fully stock RUU?
edit: (or is that the one I found above on santod's thread that says it's signed? I am guessing signed means fully stock, not rooted, etc?)
Click to expand...
Click to collapse
Correct, the one from santods thread. Signed
means it has been signed and encrypted by HTC.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Correct, the one from santods thread. Signed
means it has been signed and encrypted by HTC.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Makes sense...never needed to use an encrypted one before on my DINC or ReZound, so I wasn't up to speed on the differences. Appreciate the guidance on this.
Will also give it a day on stock (keeping s-off) to see if it actually helps...though I suspect it won't.
the_Damaged_one said:
Makes sense...never needed to use an encrypted one before on my DINC or ReZound, so I wasn't up to speed on the differences. Appreciate the guidance on this.
Will also give it a day on stock (keeping s-off) to see if it actually helps...though I suspect it won't.
Click to expand...
Click to collapse
You don't "need" to, but it is always the better option if it is available.
Sent from my HTC6500LVW using XDA Free mobile app
Thanks for the help...
I did get the stock (signed, encrypted) RUU to load...had to back-rev my firmware using santod's post first, but otherwise all went as expected.
After a few updates OTA, I have been on the 4.4.2 for a couple of days - still cruddy signal at my house, so I plan ot s-on and head into the local corporate store to see what's next.
Will post on the other thread for the folks looking for the right RUU link.
Uzephi said:
You don't "need" to, but it is always the better option if it is available.
Click to expand...
Click to collapse
Speaking of better option...want to make sure I avoid a "tampered" issue...
I left my One s-off after the RUU, and updated OTA to latest to see if that helped my issue (it did not).
To go s-on, am I ok to do it now, or do I need to flash back to an older RUU first? Not sure if Verizon built something into a newer update that may catch the flag change.
No. Verizon has no control on that deep of the inner workings of an HTC. Only way to trip a "Tampered" state is messing with the system partition, radio, etc without being s-off. Turning s-off to s-on with everything stock will not trip that flag.
Edit: in my experience with HTC bootloaders, (I have had an Inc, Rezound, DNA, and this m7) they all are different in certain ways. The Inc never had a "Tampered" tag, to my knowledge. The Rezound had "tampered" tripped when a custom recovery was flashed while s-on. We had a special way of utilizing "fastboot boot recovery" command to prevent the tampered from ever being tripped. I didn't have my DNA long enough to worry about "tampered". And to get bootloader unlock for this phone, it did s-off so tampered wasn't tripped for me.
So how are HTC bootloader different by device? When my Inc had to be rooted, it didn't have a "locked" or "unlocked" flag, only s-on/off. The Rezound had to be s-off if you wanted to flash everything of a Rom in recovery (or utilize HTC dumlock or "fastboot boot recovery" command from bootloader) otherwise after a Rom install, tampered would trip and the boot.img wouldn't be flashed and you would have to go to bootloader to flash the boot.img or do the workaround in parentheses... For the DNA and m7, you don't need s-off to flash boot.img in recovery. I do notice on stock bootloader (I have the faux hboot) it will check if radio, hboot, and recovery are stock or not and I think this is what s-on checks for when tripping tampered. (Before I flashed the faux hboot it showed everything green except recovery since I have TWRP and not stock)
For any inaccuracies you can correct me and I will fix. This is from my own experiences with these devices and how they work.
TL/DR: all HTC model bootloader are different, but one thing never changes, if you are completely stock s-off and run the command "fastboot oem writesecureflag 3" it will not trip tampered.
Sent from my HTC6500LVW using XDA Free mobile app
Hi, I bought an unlocked htc one m8 but i recieved the indian version (m8q) and I'm not from india, Everything works fine and I called htc and they told me that I shouldn't have a problem since the indian verison comes with international warrenty.
The only thing I'm worried about here is compatibility with the stuff here on xda, will i be able to flash roms without probelms and will i be able to convert it to a gpe device if i wanted to.
The Cid is HTC__038, the model id is 0P6B65000 the software version i have currently is 1.56.720.6 and the product name (from the getvar all command) is m8_ul. Is the hardware incompatible with roms made for the international gsm version (with the sku 401) or can i just change the cid/mid or make it supercid to use it with any of the guides hosted here.
I havent been able to find anything so i would really appreciate any help.
I own the same device and to be true, the Indian Variant lacks support for all Sense based ROMs as they are based on different model with different CID and MID number. Custom ROMs work fine.
If you are very proficient with flashing stuff in HTC devices then you can use firewater to S-OFF on 4.4.2 . Ver. 4.4.3 has patched some vulnerabilities that do not allow firewater S-OFF to work nor the sunshine one.
I had already updated to 4.4.3 due to which now it's currently impossible for me to obtain S-OFF.
Also Indian Variants have yet not received the latest updates i.e. 4.4.4
Mayank7795 said:
I own the same device and to be true, the Indian Variant lacks support for all Sense based ROMs as they are based on different model with different CID and MID number. Custom ROMs work fine.
If you are very proficient with flashing stuff in HTC devices then you can use firewater to S-OFF on 4.4.2 . Ver. 4.4.3 has patched some vulnerabilities that do not allow firewater S-OFF to work nor the sunshine one.
I had already updated to 4.4.3 due to which now it's currently impossible for me to obtain S-OFF.
Also Indian Variants have yet not received the latest updates i.e. 4.4.4
Click to expand...
Click to collapse
Thanks for the reply, but are you saying that If i can acheive s-off and change the cid and mid will that make the device compatible with the roms or will flashing them brick my device? Also, do you have any idea about compatibilty with gpe based roms?
tinclan said:
Thanks for the reply, but are you saying that If i can acheive s-off and change the cid and mid will that make the device compatible with the roms or will flashing them brick my device? Also, do you have any idea about compatibilty with gpe based roms?
Click to expand...
Click to collapse
This is my first HTC device and the first expensive one that I bought so I am being really cautious about tampering my phone.
Yes, if you achieve S-OFF, then you can change your CID. Don't know about MID (I have yet to know more about it). Then flashing other Sense-based ROMs should be fairly easy.
But after you achieve S-OFF, you need to be more cautious while flashing anything as the security would have been totally put off and whichever file you flash will be flashed without any error and may result in your device getting bricked if a wrong file is flashed.
It will be really great to backup the important partitions like recovery, boot, system etc. if you are still stock (not bootloader unlocked and not rooted)
To backup important partitions, visit this thread for instructions. (Be sure to backup your stock recovery as it will be needed to receive OTA updates) - http://forum.xda-developers.com/showthread.php?t=2701376
IMPORTANT: Read the Question "How do i backup the stock HTC recovery ?" and the procedure below that in the provided thread properly to successfully backup your device's partition.
~~Other Helpful threads which needs a reading~~
♦ HTC One M8 F.A.Q's
♦ HTC ONE M8 Repository
Mayank7795 said:
This is my first HTC device and the first expensive one that I bought so I am being really cautious about tampering my phone.
Yes, if you achieve S-OFF, then you can change your CID. Don't know about MID (I have yet to know more about it). Then flashing other Sense-based ROMs should be fairly easy.
But after you achieve S-OFF, you need to be more cautious while flashing anything as the security would have been totally put off and whichever file you flash will be flashed without any error and may result in your device getting bricked if a wrong file is flashed.
It will be really great to backup the important partitions like recovery, boot, system etc. if you are still stock (not bootloader unlocked and not rooted)
To backup important partitions, visit this thread for instructions. (Be sure to backup your stock recovery as it will be needed to receive OTA updates) - http://forum.xda-developers.com/showthread.php?t=2701376
IMPORTANT: Read the Question "How do i backup the stock HTC recovery ?" and the procedure below that in the provided thread properly to successfully backup your device's partition.
~~Other Helpful threads which needs a reading~~
♦ HTC One M8 F.A.Q's
♦ HTC ONE M8 Repository
Click to expand...
Click to collapse
This is my first htc phone too, actually this is my first high end android phone. I am just as paranoid about doing anything as you, i just wanted to make sure i'm not stuck forever, because i it was impossible to change the software of this phone i would've just sold it from now, purely because imo new software adds the most value to smartphone these days. I am a bit confused, but for now i decided to not install any updates until i figure out whats possible to do without screwing up myself
tinclan said:
This is my first htc phone too, actually this is my first high end android phone. I am just as paranoid about doing anything as you, i just wanted to make sure i'm not stuck forever, because i it was impossible to change the software of this phone i would've just sold it from now, purely because imo new software adds the most value to smartphone these days. I am a bit confused, but for now i decided to not install any updates until i figure out whats possible to do without screwing up myself
Click to expand...
Click to collapse
That's a good decision for now..
I did the mistake of not backing up recovery partition after I updated and instantly unlocked and rooted my phone but luckily I got the stock recovery from another thread.
tinclan said:
This is my first htc phone too, actually this is my first high end android phone. I am just as paranoid about doing anything as you, i just wanted to make sure i'm not stuck forever, because i it was impossible to change the software of this phone i would've just sold it from now, purely because imo new software adds the most value to smartphone these days. I am a bit confused, but for now i decided to not install any updates until i figure out whats possible to do without screwing up myself
Click to expand...
Click to collapse
Mayank7795 said:
That's a good decision for now..
I did the mistake of not backing up recovery partition after I updated and instantly unlocked and rooted my phone but luckily I got the stock recovery from another thread.
Click to expand...
Click to collapse
Thanks for all the help. I have one last question if you wouldnt mind answering, are all the gpe based rooms compatible with our version of the device, and can i flash the gpe ruu without bricking the thing if i got s-off.
tinclan said:
Thanks for all the help. I have one last question if you wouldnt mind answering, are all the gpe based rooms compatible with our version of the device, and can i flash the gpe ruu without bricking the thing if i got s-off.
Click to expand...
Click to collapse
Sorry but I seriously don't know because I never took an interest in converting my device to GPE.
I like the stock look.
Hi there.
So In short I'm a Nexus 5 user and as you can imagine unlocking that phone is literally 2 minutes at most using fastboot.
I got myself a brand spanking new HTC One m8 on Vodafone UK, however I hate Sense UI and would love to "transform" my phone to GPE edition.
I have few questions hopefully easy to answer. reading through the forums gives me a headache.
1. Do I need a S-Off if I want to convert my GSM to GPE? Thought its just a matter of flashing a rom? (I do know the answer to this but just cant believe it)
2. My phone is network locked, should I unlock it first and than run sunshine or the other way around (I've heard people having problems when they try to unlock after sunshine)
3. Do I need to backup my stock Vodafone Image if I want to return to stock at some point? I had HTC Desire/HD and returning back to stock was matter of flashing RUU back in the days (these seem to be provided on HTCDev now). But it looks like a lot has changed since then.
4. What order of operations? Please correct me if I'm wrong: Unlock Bootloader (Any other way than HTC Dev?) --> TWRP-->Root-->Sunshine-->Backup Image-->Convert to GPE
I'm absolutely fine with using fastboot etc (no toolkits for the wicked ) although most guides involve Windows and im on Mac... Anyone had any issues ?
Appreciate any help
Thanks
Nexus phones are designed to be developer phones, so they make it as easy as possible. (Though, and this is an important note, they still keep secure boot enabled...) The HTC One, like most consumer oriented devices, isn't quite the same.
First off, yes, you will need to S-off your phone to do a complete version change. You will also need to change your CID/MID if you want OTA updates. None of this has anything to do with SIM locking, though there is a thread you might consult once you are S-off. It may or may not work with HBOOT 3.19, but once you are S-off, you can downgrade to an older HBOOT that does fully support SIM unlocking.
If you want to ever go back, you will also need to install TWRP or CWM like always and make a nandroid backup. You don't have to be S-off to do this, but Sunshine unlocks your bootloader in the process, which you WILL need to do.
If your device is supported (because some newer firmware versions aren't) I would suggest using Sunshine S-off to unlock your bootloader and S-off your phone. At that point, flash over a custom recovery and backup your current install. Then, use the instructions here to switch your CID/MID and install the appropriate GPE version. Note! You *CAN* use a GPE RUU, but that will change the partitioning on the device making it very hard to go back.. I would strongly recommending using using a GPE backup and leaving the partition tables alone, but that's just me.
jshamlet said:
Nexus phones are designed to be developer phones, so they make it as easy as possible. (Though, and this is an important note, they still keep secure boot enabled...) The HTC One, like most consumer oriented devices, isn't quite the same.
First off, yes, you will need to S-off your phone to do a complete version change. You will also need to change your CID/MID if you want OTA updates. None of this has anything to do with SIM locking, though there is a thread you might consult once you are S-off. It may or may not work with HBOOT 3.19, but once you are S-off, you can downgrade to an older HBOOT that does fully support SIM unlocking.
If you want to ever go back, you will also need to install TWRP or CWM like always and make a nandroid backup. You don't have to be S-off to do this, but Sunshine unlocks your bootloader in the process, which you WILL need to do.
If your device is supported (because some newer firmware versions aren't) I would suggest using Sunshine S-off to unlock your bootloader and S-off your phone. At that point, flash over a custom recovery and backup your current install. Then, use the instructions here to switch your CID/MID and install the appropriate GPE version. Note! You *CAN* use a GPE RUU, but that will change the partitioning on the device making it very hard to go back.. I would strongly recommending using using a GPE backup and leaving the partition tables alone, but that's just me.
Click to expand...
Click to collapse
Thanks a lot for that.
Could your please clarify your last 2 sentences. This is first I hear about. If I use GPE backup will I be able to get OTA updates? Where can I find GPE backup rather than RUU. I think most here are RUU's.
Or do you mean GPE ROM vs GPE RUU?
MattSkeet said:
Thanks a lot for that.
Could your please clarify your last 2 sentences. This is first I hear about. If I use GPE backup will I be able to get OTA updates? Where can I find GPE backup rather than RUU. I think most here are RUU's.
Click to expand...
Click to collapse
The partition sizes are different between GPE and Sense, with Sense having a much larger /system partition than GPE. If you convert from Sense to GPE fully (using an RUU), then you will have to use an RUU to go back to Sense or the /system partition won't be large enough. If you just restore a nandroid backup of GPE to a Sense partitioned device, it will still work fine and you can revert back without any special effort.
S-off yes carrier unlocking yes and I'm an ex nexus 5 user as well
Sent from my HTC One_M8 using XDA Free mobile app
MattSkeet said:
3. Do I need to backup my stock Vodafone Image if I want to return to stock at some point? I had HTC Desire/HD and returning back to stock was matter of flashing RUU back in the days (these seem to be provided on HTCDev now). But it looks like a lot has changed since then.
Click to expand...
Click to collapse
I don't believe HTC posts RUUs to HTCDev.com any longer. There is a RUU floating around for the "generic" WWE version, but for Vodaphone or other carrier branded versions outside the US, you probably won't find any RUUs.
Therefore, its always good to at least make a nandroid before making any other changes. Or you can find the stock nandroid for your CID here:
http://forum.xda-developers.com/showthread.php?t=2701376
MattSkeet said:
4. What order of operations? Please correct me if I'm wrong: Unlock Bootloader (Any other way than HTC Dev?) --> TWRP-->Root-->Sunshine-->Backup Image-->Convert to GPE
Click to expand...
Click to collapse
I believe you can temp root, sunshine s-off and use sunshine to unlock the bootloader and bypass HTCDev.com. But I haven't done it that way personally, so I'm not 100% on that.
redpoint73 said:
I don't believe HTC posts RUUs to HTCDev.com any longer. There is a RUU floating around for the "generic" WWE version, but for Vodaphone or other carrier branded versions outside the US, you probably won't find any RUUs.
Therefore, its always good to at least make a nandroid before making any other changes. Or you can find the stock nandroid for your CID here:
http://forum.xda-developers.com/showthread.php?t=2701376
I believe you can temp root, sunshine s-off and use sunshine to unlock the bootloader and bypass HTCDev.com. But I haven't done it that way personally, so I'm not 100% on that.
Click to expand...
Click to collapse
http://www.htcdev.com/devcenter/downloads/P00 there are RUU's here which is very strange and makes it confusing in regards to backing everything up if its there
MattSkeet said:
http://www.htcdev.com/devcenter/downloads/P00 there are RUU's here which is very strange and makes it confusing in regards to backing everything up if its there
Click to expand...
Click to collapse
The only RUU there is T-Mobile US. All the rest are kernel source (and a couple framework support) files. Keep in mind, the RUU is something like 1.6 GB.
Note that there are other RUUs, they just aren't posted there. The Developer Edition has an RUU, and there is an older one for AT&T floating around somewhere as well.
I really don't understand why HTC doesn't make these more available, as they are a great way to reset a phone short of warranty service. I would think they would want people to have these as an option.
jshamlet said:
Note that there are other RUUs, they just aren't posted there. The Developer Edition has an RUU, and there is an older one for AT&T floating around somewhere as well.
Click to expand...
Click to collapse
Yes, in fact AT&T has RUUs for every major OTA build its released so far. Sprint and T-Mobile US also have RUUs. Of the major US carriers, only Verizon does not have RUUs.
I haven't seen any official RUU releases outside the US. I know there is a WWE 3.28.401 RUU think is being linked lately, but I don't know if that is a leak, or something more official. But otherwise, RUUs don't exist outside the US (or only as leaks). What makes the US so special, I don't know.
jshamlet said:
I really don't understand why HTC doesn't make these more available, as they are a great way to reset a phone short of warranty service. I would think they would want people to have these as an option.
Click to expand...
Click to collapse
I don't get it either. On past devices, I've seen specific reports of HTC support directing folks to RUU when they have software issues (after the "usual" solutions like factory reset didn't help).
Hey M8 forums,
My S4 recently self destructed and I'm jumping ship to the M8 for T-Mo USA, I have a couple questions to prepare for it's arrival.
I'm coming off the S4 CM12 nightlies, are the M8 builds unified? As in, I can flash the standard CM release on my T-Mo variant?
And can I please get a link to the unlocking and rooting thread? The one I found has a method, but for s-off, the link seems to be down.
Thanks and greetings!
Most info can be found here,
http://forum.xda-developers.com/showthread.php?t=2711073
?
As far as CM goes, I'm not familiar with T-Mobile variants... Sorry. ☺
As of now the M8 in cyanogenmod is unified, all the GSM variants are just labelled as "m8". and the CDMA variants have other names like cm-20140120-m8vzw for verizon.
Onto the rooting and unlocking, you can unlock using HTC Dev but S-OFF might be a little impossible if you get the m8 pre-installed with 4.4.4.
Honestly, to root all you need to do is unlock using the HTC Dev site and flash a custom recovery from TWRP or CWM.
then flash SuperSU not all that different from a Nexus.
Darth said:
Most info can be found here,
http://forum.xda-developers.com/showthread.php?t=2711073
Click to expand...
Click to collapse
Thanks for the dump, lots of good info in there.
i4GS said:
As of now the M8 in cyanogenmod is unified, all the GSM variants are just labelled as "m8". and the CDMA variants have other names like cm-20140120-m8vzw for verizon.
Onto the rooting and unlocking, you can unlock using HTC Dev but S-OFF might be a little impossible if you get the m8 pre-installed with 4.4.4.
Honestly, to root all you need to do is unlock using the HTC Dev site and flash a custom recovery from TWRP or CWM.
then flash SuperSU not all that different from a Nexus.
Click to expand...
Click to collapse
I bought it off a guy that bought it a few weeks ago I believe, I haven't gotten it yet to see. It was my understanding that SunShine works on all M8's up to Lollipop. Is that not the case?
And what is a firmware? I keep seeing around to flash the Lollipop firmware, is that just the radio.img file or the whole RUU or what?
A firmware could be reffered to a whole RUU , because the ZIP that updates from 1.x to 3.x is a firmware.
Essentially a Firmware contains the essentials for a basic update (HTC version) , Radio, boot, Kernel, Bootloader, modem, etc.
An Update Firmware or RUU will contain all the partitions ,
boot, system, bootloader,hboot,modem,radio, cache, recovery , and so on.
And to some sunshine will work and to some it might not, it's a risk you're going to have to take, (to get s-off) worth it.
Though we shouldn't have to go through all these cracks and breaks to get it.
I used an older method and it worked for me, never had to use sunshine.
i4GS said:
A firmware could be reffered to a whole RUU , because the ZIP that updates from 1.x to 3.x is a firmware.
Essentially a Firmware contains the essentials for a basic update (HTC version) , Radio, boot, Kernel, Bootloader, modem, etc.
An Update Firmware or RUU will contain all the partitions ,
boot, system, bootloader,hboot,modem,radio, cache, recovery , and so on.
And to some sunshine will work and to some it might not, it's a risk you're going to have to take, (to get s-off) worth it.
Though we shouldn't have to go through all these cracks and breaks to get it.
I used an older method and it worked for me, never had to use sunshine.
Click to expand...
Click to collapse
I was told that the older method ceased to work because it required a server connection to complete that is no longer up. And would using a RUU to get to Lollipop put the system back to S-On?
Flashing anything won't touch the S-OFF. You'd have to manually set that back to S-ON (but why would you want to do that!)