Related
So long story short, I messed up and wiped my OS off my phone via TRWP. After reinstalling and looking/asking around on the forums, I managed to reinstall it, but the WiFi is no longer working. Then after some more looking/asking, I gave up and sent in to a store for repairs. It came back and the guy said he couldn't do anything to fix it.
So... now I'm here asking again. Does anyone have any idea how to fix this?
Here's an image of my bootloader
http://imgur.com/SswEXd2
As you can see, the OS- is blank. I'm not sure if that's normal or not, but I'm 99% sure that there's supposed to be some code following OS-
You likely flashed a ROM that is a different version from what you had before, and does not match your firmware (hboot, radio, WiFi, etc. - modules that do NOT get updated when you flash a ROM).
Your hboot goes with Android 4.4.3, or software number 2.x. So flash a stock or custom ROM based on software 2.x, and WiFi should work again.
You likely flashed a ROM based on Android 4.4.4 or 5.0, and therefore no WiFi.
And no OS number listed on hboot screen is a common bug found on older TWRP versions.
Which ROM do you recommend?
Xenosaki said:
Which ROM do you recommend?
Click to expand...
Click to collapse
Most custom Sense ROMs based on software 2.xx should work.
You might also be able to use 1.xx software based ROMs, as well. Firmware is usually "backwards compatible" (with older ROMs) but never forwards compatible.
Also, next time make a backup of your stock ROM. One of the great things you can do once you have TWRP installed.
redpoint73 said:
Most custom Sense ROMs based on software 2.xx should work.
You might also be able to use 1.xx software based ROMs, as well. Firmware is usually "backwards compatible" (with older ROMs) but never forwards compatible.
Also, next time make a backup of your stock ROM. One of the great things you can do once you have TWRP installed.
Click to expand...
Click to collapse
I'm looking for a 2.xx rom right now.
Also, another question, could I update the firmware without flashing the ROM first? Or do I need to do that prior to updating the firmware?
EDIT: I'm unable to find a sense 2.xx for the HTC ONE M8. Or does the phone type not matter as long as it's a sense 2.xx?
What's your device CID & MID ?
ckpv5 said:
What's your device CID & MID ?
Click to expand...
Click to collapse
How would I go about finding it?
Xenosaki said:
I'm looking for a 2.xx rom right now.
Also, another question, could I update the firmware without flashing the ROM first? Or do I need to do that prior to updating the firmware?
EDIT: I'm unable to find a sense 2.xx for the HTC ONE M8. Or does the phone type not matter as long as it's a sense 2.xx?
Click to expand...
Click to collapse
No. You want to update the firmware first. You should also update your recovery before flashing the new firmware. Then your OS won't be blank anymore (after you flash new firmware).
If you want a 2.xx based ROM,. you could try ViperOneM8 2.5.0
It's a solid Sense based ROM with a lot of customization options.
---------- Post added at 05:12 PM ---------- Previous post was at 05:08 PM ----------
Xenosaki said:
How would I go about finding it?
Click to expand...
Click to collapse
Find it by hooking up to your PC, getting into ADB/fastboot and entering fastboot getvar all
The CID is listed as CID
The MID is listed as modelid
Xenosaki said:
I'm looking for a 2.xx rom right now.
Also, another question, could I update the firmware without flashing the ROM first? Or do I need to do that prior to updating the firmware?
Click to expand...
Click to collapse
You're talking about 2 different approaches now. You can either:
1) Flash a ROM that is supported by your (2.xx) firmware.
2) Update the firmware that matches your current ROM (but not sure what version that would be).
You don't need to do both (flash new firmware and flash a 2.xx ROM). Although you can, as long the ROM is supported by the firmware (otherwise you will still have broken WiFi and possibly other severe bugs).
Also, keep in mind that if you are s-on, you can only flash a firmware that is signed and corresponds with your CID.
Xenosaki said:
I'm looking for a 2.xx rom right now.
EDIT: I'm unable to find a sense 2.xx for the HTC ONE M8. Or does the phone type not matter as long as it's a sense 2.xx?
Click to expand...
Click to collapse
It absolutely matters. NEVER EVER EVER flash a ROM meant for another device. If you are s-on, it probably won't flash anyway. But if it does, it either won't work, or may even brick your device.
You likely just didn't browse back far enough (or didn't use the proper search string, if you used the XDA search function) to find a 2.xx based ROM for the M8. ROM base 2.xx is pretty old, so I see a couple started on Page 5 of 7 in the M8 Development section. What I see are:
http://forum.xda-developers.com/showthread.php?t=2702765
http://forum.xda-developers.com/showthread.php?t=2794008
redpoint73 said:
You're talking about 2 different approaches now. You can either:
1) Flash a ROM that is supported by your (2.xx) firmware.
2) Update the firmware that matches your current ROM (but not sure what version that would be).
You don't need to do both (flash new firmware and flash a 2.xx ROM). Although you can, as long the ROM is supported by the firmware (otherwise you will still have broken WiFi and possibly other severe bugs).
Also, keep in mind that if you are s-on, you can only flash a firmware that is signed and corresponds with your CID.
It absolutely matters. NEVER EVER EVER flash a ROM meant for another device. If you are s-on, it probably won't flash anyway. But if it does, it either won't work, or may even brick your device.
You likely just didn't browse back far enough (or didn't use the proper search string, if you used the XDA search function) to find a 2.xx based ROM for the M8. ROM base 2.xx is pretty old, so I see a couple started on Page 5 of 7 in the M8 Development section. What I see are:
http://forum.xda-developers.com/showthread.php?t=2702765
http://forum.xda-developers.com/showthread.php?t=2794008
Click to expand...
Click to collapse
Sorry if I'm asking too many questions. If I go with the updating the firmware route first, do I have to do anything specific? Like for example update from 2.x.x -> 5.0. Or does it not matter what version I'm currently on to update to 5.0. Also, I'm seeing a lot of issues concerning which carrier the phone is from. Is there a way to check that? I *think* mine might be some asian branded version, but I'm unsure.
Also, I'm checking the phone's firmware and it's saying that it's 4.4.4. http://imgur.com/rbLpjl1
All the pic info you provided not really can give proper help.
I'm asking again, maybe for the last time .. what's your device CID & MID ?
Xenosaki said:
Sorry if I'm asking too many questions. If I go with the updating the firmware route first, do I have to do anything specific? Like for example update from 2.x.x -> 5.0. Or does it not matter what version I'm currently on to update to 5.0. Also, I'm seeing a lot of issues concerning which carrier the phone is from. Is there a way to check that? I *think* mine might be some asian branded version, but I'm unsure.
Click to expand...
Click to collapse
It absolutely matters what firmware you pick and whether or not it corresponds to your CID. For one thing, with s-on, you can only flash the firmware for your CID, plus the firmware has to be signed.
Another thing, the firmware will update your radio baseband version. So if you flash firmware for a different CID, you may change the band support, and find you no longer have 3G or 4G connection (depending on what firmware you flash, what bands used by your local carrier, etc.).
Also, don't confuse software version with Android version (you've mixed the 2 together above). The Android version is Google's numbering scheme. Software number is HTC's numbering scheme.
Software version 2.xx corresponds to Android version 4.4.3.
Android version 5.0 (Lollipop) corresponds to software version 4.xx.
Its been requested a couple times now that you do adb getvar all to determine your CID and MID. We can't help if you are guessing or don't know the carrier version.
Xenosaki said:
Also, I'm checking the phone's firmware and it's saying that it's 4.4.4. http://imgur.com/rbLpjl1
Click to expand...
Click to collapse
The photo has nothing to do with your firmware number. The firmware number is best determined with adb getvar all, and is displayed as "main version".
What your picture shows simply means the ROM you flashed is based on Android 4.4.4, and software 3.28.401. The software number of the ROM is completely different from your present firmware number; and the very reason why your WiFi is broken.
I've already determined from the pic in your first post that your firmware is 2.xx (corresponding to Android 4.4.3). To get the more specific numbers (after the "2") you need to do adb getvar all.
Also, if you post the getvar output, be sure to delete your IMEI and serial number, as these are private info.
ckpv5 said:
All the pic info you provided not really can give proper help.
I'm asking again, maybe for the last time .. what's your device CID & MID ?
Click to expand...
Click to collapse
redpoint73 said:
It absolutely matters what firmware you pick and whether or not it corresponds to your CID. For one thing, with s-on, you can only flash the firmware for your CID, plus the firmware has to be signed.
Another thing, the firmware will update your radio baseband version. So if you flash firmware for a different CID, you may change the band support, and find you no longer have 3G or 4G connection (depending on what firmware you flash, what bands used by your local carrier, etc.).
Also, don't confuse software version with Android version (you've mixed the 2 together above). The Android version is Google's numbering scheme. Software number is HTC's numbering scheme.
Software version 2.xx corresponds to Android version 4.4.3.
Android version 5.0 (Lollipop) corresponds to software version 4.xx.
Its been requested a couple times now that you do adb getvar all to determine your CID and MID. We can't help if you are guessing or don't know the carrier version.
The photo has nothing to do with your firmware number. The firmware number is best determined with adb getvar all, and is displayed as "main version".
What your picture shows simply means the ROM you flashed is based on Android 4.4.4, and software 3.28.401. The software number of the ROM is completely different from your present firmware number; and the very reason why your WiFi is broken.
I've already determined from the pic in your first post that your firmware is 2.xx (corresponding to Android 4.4.3). To get the more specific numbers (after the "2") you need to do adb getvar all.
Also, if you post the getvar output, be sure to delete your IMEI and serial number, as these are private info.
Click to expand...
Click to collapse
Not sure if I got the right ones, but here you go. Let me know if I didn't do it right.
http://imgur.com/a/C8hcK#0
The first picture is getting the CID and MID by following some guide off of google, so I don't know if that's right or not.
The second and third picture are the adb getvar all that you suggested me doing.
See ... you're on T-Mobile network but your device is not a TMOB and not a EU but a TW device.
CID HTC__621
MID 0P6B11000
This is my suggestion to fix whatever problem you have currently (without S-Off).
1. Restore 2.22.709.3 TWRP backup as your device hboot is 3.18.0000
2. install 2.22.709.3 stock recovery after restore
3. do multiple OTA to the latest lollipop version : 2.22.709.3 --> 3.28.709.6 --> 4.16.709.9 --> 4.24.709.2
4. Then if you like to install custom ROM, install TWRP again and install any custom ROM that you like - now you should not have any wifi problem
All the needed files / how-to is here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You guys are absolutely amazing. Thank you so much for the help and patience. I followed all the steps (except for the multiple OTA updates, which I'm in the process of right now) and the wifi problem seems to be fixed.
On an off note, does it matter that in the bootloader, it says
*** Software status: Modified ***
*** UNLOCKED ***
?
And should I go through the process of S-Off-ing my phone? Does it benefit me to do it?
Again, thank you so much
Xenosaki said:
I followed all the steps (except for the multiple OTA updates, which I'm in the process of right now) and the wifi problem seems to be fixed.
On an off note, does it matter that in the bootloader, it says
*** Software status: Modified ***
*** UNLOCKED ***
?
Click to expand...
Click to collapse
UNLOCKED is fine. OTAs will install whether its locked or not. Better to leave it as-is (relocking only needed and recommended to run RUU or signed firmware zip).
The software modified flag is a bit puzzling. It usually indicated the ROM has been modified. If you installed the stock TWRP backup for your CID, it shouldn't say this. And software modified will prevent OTA from installing.
Are you sure you installed the stock TWRP backup (exactly correct software number) that ckpv5 indicated?
Xenosaki said:
And should I go through the process of S-Off-ing my phone? Does it benefit me to do it?
Click to expand...
Click to collapse
It depends on what you want to do with the phone. For most things (root, flashing custom ROMs, kernels, etc.), s-off is not needed. But it can be handy if you want to flash radios, modified hboots, convert to another CID or MID, and some other things.
---------- Post added at 10:22 AM ---------- Previous post was at 10:18 AM ----------
Xenosaki said:
The second and third picture are the adb getvar all that you suggested me doing.
Click to expand...
Click to collapse
The pics do not show the expected output for adb getvar all.
My guess is that you tried to run the commands same as the other (fastboot) commands, while in fastboot mode. adb commands can only be run while booted into OS (and with Debugging enabled in phone settings) or in recovery. Only fastboot commands work in fastboot mode.
redpoint73 said:
The software modified flag is a bit puzzling. It usually indicated the ROM has been modified. If you installed the stock TWRP backup for your CID, it shouldn't say this. And software modified will prevent OTA from installing.
Are you sure you installed the stock TWRP backup (exactly correct software number) that ckpv5 indicated?
Click to expand...
Click to collapse
That's the same as "TAMPERED" on hboot 3.18.0000 as seen on his first screenshot.
MODIFIED is on hboot 3.19.0000
That usually come after the bootloader is unlocked.
That can be change on S-Off device.
I installed the Venom ROM so that's probably the reason why it's showing that then. Thanks for everything guys
im new to all this.
im S-Off, and semi root, SuperSU doesn't really give half of my apps root acces for some reason.
i want to do a full reset to the phone (Return to 100% Stock)
i want just to clean it all out (which factor reset doesn't do that)
and update my softer from lolipop 5.0 to 5.1
i got HTC__621 (twiwan version)
software number 1.32.709.14
how to do all this? what i need to do?
(to flashout new TWRP2.8.7.0? then superSU 2.49 beta from the beginning?
and if i want to install Viper ROM, i need to do that after all?)
i hope to get explanation cuz i got lost on all the words (OTA - which i dont know yet lol, CID etc etc)
i got like 10 pages of guides open and yet i dont know what to do or what steps to follow.
As far as I know there is no RUU and no stock system backup for your firmware version. Nevertheless that's not a problem since you can always run RUUs that are newer than your firmware (even if you were S-ON you were able to do so). All you need to to is download the RUU.exe from here or here (it's actually the same file so it doesn't matter which link you choose). Then you need to boot to download mode and connect your phone with your pc. If you double click on the RUU.exe it may take some time till it starts but when it starts it will guide you through the rest of the process. During the flashing process your firmware will be updated to 1.36.709.3 but since you want update your firmware anyway I wouldn't consider this as an issue. Depending on your firewall and your antivirus software the RUU flashing might fail. If that's the case you should try again with disabled firewall and disabled antivirus software (I recommend disconnecting your pc from the internet before you do this).
Edit: Some vocabulary:
RUU = Rom Update Utility (a package leaked from HTC that can be used to get fully back to stock)
OTA (Update) = Over The Air Update (updates for your phone you can download via settings>about; some custom roms provide this feature, too)
CID = Customer ID (a combination of letters and numbers that tells you your phones country of origin and whether it is branded or not)
MID = Model ID (a combination of letters and numbers that identifies your phones model and its version; example: the international M9's MID is 0PJA10000 whereas the T-Mobile US version's MID is 0PJA12000)
Edit2: If you want to install the viper rom you don't need to root beforehand since that custom rom already is rooted.
Edit3: I just noticed that my signature isn't visible here. There is a newer version of TWRP at the end of the third post in this thread.
so if i install viper i just need to flash it in?
and what happen if i want to update to normal lolipap 5.1
cuz im at 5.0 and i always geting the update window and sick of it
want to update it alredy XD
The RUU is for restoring the ability of installing HTC's official OTAs. After you used the RUU you can update your phone using the OTA function in settings>about. After that you can reflash TWRP and install the viper rom. Since the viper rom is already rooted there is no need to flash supersu manually via TWRP.
I recommend you to read at least the whole first 3 posts in the TWRP thread I linked in my previous post. There you will find the information you need to create a backup of your stock system that is able to install future OTAs since the 2.10 firmware won't be the last one and you might face a similiar situation like this one in the future.
Edit: Although the RUU.exe will warn you, too: Using a RUU deletes all your data on the phone so back up everything that is important (contacts, messages, pictures, etc.).
Hi guys,
Verizon HTC One M8 rooted, S-off,with CWM, running the old digital high GPE 4.4.4.
HBOOT 3.16.0
RADIO 0.89.20.0321
10G storage
I did the firewater procedure when I first got the phone with no problems. Now I am trying to install the new LolliGPE on here and getting nothing but headaches. I have tried to install TWRP(different versions) via Flashify AND fastboot, but when it reboots, it stays on the white HTC One screen-"loading recovery". I have done this multiple times, and then adb reboot, install CWM via flashboot, and no problems. I don't know what else to do, and don't wanna mess my phone up especially as the next step is updating RUU, etc. I'm thinking I may have to update hboot, I just don't want to do anything un-neccesary to brick my phone. Any ideas? Thanks!!
Your older hboot requires an older version of TWRP. Plus, on older TWRP versions, depending on which TWRP version exactly, the CDMA M8 variants had a different TWRP recovery image (as recovery is stored on a different partition location for that version versus the "GSM" or non-CDMA M8). So you need to be really careful (I think a brick is even possible).
I'd suggest updating to the current Verizon Lollipop firmware before proceeding. Your hboot is ancient, and will cause all sorts of issues. After that, the current version TWRP 2.8.7 should install fine.
Thanks for the reply..
So update Hboot first, then install TWRP, then RUU, then ROM?
dl12458 said:
So update Hboot first, then install TWRP, then RUU, then ROM?
Click to expand...
Click to collapse
Shouldn't be a need to flash new hboot, RUU will do that.
Further, you don't want to install TWRP before the RUU; as RUU will wipe it out with stock recovery, anyway.
So in general, you want to:
1) Backup your personal data, RUU will wipe the phone including internal storage.
2) RUU
3) Install TWRP
4) Flash the custom ROM of your choice
Although it should be noted that some folks have had trouble installing TWRP after installing the OTA (the one with Stagefright fix in particular), at least on "GSM" versions of the M8. So you might research and see if VZN folks are having the same issue on the RUU with Stagefright fix that you linked in your PM to me. But at least in browsing the last few pages of the thread, I don't see any mention of TWRP issues (and some confirmations of TWRP working okay):
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Great, the update worked!!
I have one final question regarding the LolliGPE ROM (if you have any experience with it). Since I am now on 5.0.1, I tried installing the LolliGPE ROM, and once it is through with its inital bootup, Google prompts me to download a 600mb update. I allow to it to, but then it just gets stuck. It doesn't download anything, and I cannot procede any further. Do I need to flash the Verizon firmware listed, even though the RUU updated? I used the following to try and flash the VZN firmware 1. "fastboot oem rebootRUU" (Phone goes into RUU mode) 2."fastboot flash zip firmware.zip", but I get a response "cannot load firmware.zip" Any ideas?? Thanks again!!
Forum
http://forum.xda-developers.com/showthread.php?t=2716306
redpoint73 said:
Shouldn't be a need to flash new hboot, RUU will do that.
Further, you don't want to install TWRP before the RUU; as RUU will wipe it out with stock recovery, anyway.
So in general, you want to:
1) Backup your personal data, RUU will wipe the phone including internal storage.
2) RUU
3) Install TWRP
4) Flash the custom ROM of your choice
Although it should be noted that some folks have had trouble installing TWRP after installing the OTA (the one with Stagefright fix in particular), at least on "GSM" versions of the M8. So you might research and see if VZN folks are having the same issue on the RUU with Stagefright fix that you linked in your PM to me. But at least in browsing the last few pages of the thread, I don't see any mention of TWRP issues (and some confirmations of TWRP working okay):
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Click to expand...
Click to collapse
dl12458 said:
I tried installing the LolliGPE ROM, and once it is through with its inital bootup, Google prompts me to download a 600mb update. I allow to it to, but then it just gets stuck. It doesn't download anything, and I cannot procede any further. Do I need to flash the Verizon firmware listed, even though the RUU updated?
Click to expand...
Click to collapse
I don't use that ROM, or any GPE ROMs, for that matter. So I'll be of limited help on this one.
What I can say, I've seen another post or 2 reporting a similar issue: GPE or AOSP custom ROM installed, will prompt to download an update upon setup (with no option to do otherwise), then phone is stuck.
So you might check the ROM thread, to see if others reported this. Or other help threads, as I've mentioned, I know others have posted this same issue; and that thread(s) may have some insight on a fix.
This issue is pretty weird. You won't normally see a custom ROM accept any type of OTA update, and certainly not a "forced" one like this at startup. In general, custom ROMs won't play well with any type of official OTA update (and updates are often disabled for this reason). And it seems you had no choice to bypass it, which is also odd.
dl12458 said:
Great, the update worked!!
Do I need to flash the Verizon firmware listed, even though the RUU updated? I used the following to try and flash the VZN firmware 1. "fastboot oem rebootRUU" (Phone goes into RUU mode) 2."fastboot flash zip firmware.zip", but I get a response "cannot load firmware.zip" Any ideas?? Thanks again!!
Click to expand...
Click to collapse
Again, I'm not sure what is going on with the forced "update". But I doubt flashing firmware will fix anything.
The error "cannot load" when trying to fastboot flash a file, almost always means the file is not present (meaning not located where it should be, or named wrong). You need to have the desired firmware zip in the same folder where fastboot.exe is located (assuming you are using a PC). And for the command you listed, the firmware actually/literally has to be named "firmware.zip" (with no quotes). If the firmware file is named something else, you either need to rename the file to "firmware.zip" or use the actual exact file name in the fastboot command. Another common problem, is on Windows, folks often have the option enabled to hide file extensions (this is typically enabled by default, and I highly recommended you turn this off). So if you already renamed the file, it may actually be named "firmware.zip.zip" even though Windows will display it as "firmware.zip". If you see a lot of file types with not extensions at all, its very likely you have the option enabled to hide file extensions.
But again, I'm not sure that flashing the firmware is going to help.
If you can't find an easier fix for the "forced" update and stuck on boot screen; my thought would be to try flashing another ROM. Or at worst, RUU to stock again, and try another ROM.
Update- I was trying to install the 5.0.1 update, and when I tried the 5.1 it worked!! Thanks for your help.
redpoint73 said:
I don't use that ROM, or any GPE ROMs, for that matter. So I'll be of limited help on this one.
What I can say, I've seen another post or 2 reporting a similar issue: GPE or AOSP custom ROM installed, will prompt to download an update upon setup (with no option to do otherwise), then phone is stuck.
So you might check the ROM thread, to see if others reported this. Or other help threads, as I've mentioned, I know others have posted this same issue; and that thread(s) may have some insight on a fix.
This issue is pretty weird. You won't normally see a custom ROM accept any type of OTA update, and certainly not a "forced" one like this at startup. In general, custom ROMs won't play well with any type of official OTA update (and updates are often disabled for this reason). And it seems you had no choice to bypass it, which is also odd.
Again, I'm not sure what is going on with the forced "update". But I doubt flashing firmware will fix anything.
The error "cannot load" when trying to fastboot flash a file, almost always means the file is not present (meaning not located where it should be, or named wrong). You need to have the desired firmware zip in the same folder where fastboot.exe is located (assuming you are using a PC). And for the command you listed, the firmware actually/literally has to be named "firmware.zip" (with no quotes). If the firmware file is named something else, you either need to rename the file to "firmware.zip" or use the actual exact file name in the fastboot command. Another common problem, is on Windows, folks often have the option enabled to hide file extensions (this is typically enabled by default, and I highly recommended you turn this off). So if you already renamed the file, it may actually be named "firmware.zip.zip" even though Windows will display it as "firmware.zip". If you see a lot of file types with not extensions at all, its very likely you have the option enabled to hide file extensions.
But again, I'm not sure that flashing the firmware is going to help.
If you can't find an easier fix for the "forced" update and stuck on boot screen; my thought would be to try flashing another ROM. Or at worst, RUU to stock again, and try another ROM.
Click to expand...
Click to collapse
Hello guys,
I got One M8 GSM s-off, unlocked bootloader and supercid.
It is sense based variant, not GPE.
Can I flash any firmware now (GPE firmware over my Default Sense) ?
93boba said:
Hello guys,
I got One M8 GSM s-off, unlocked bootloader and supercid.
It is sense based variant, not GPE.
Can I flash any firmware now (GPE firmware over my Default Sense) ?
Click to expand...
Click to collapse
No.
GPE has different partition sizes and isn't compatible with Sense firmware. You can convert to GPE if you wish though. It's not that hard. Do a search here on XDA or on Google.
I have flashed successfully most if not all of the ROM's and firmware found here on page 1 and many from the subsequent pages.
Have flashed this GPE firmware and had some good fun with it. Any firmware by dottat found here is pretty solid as well.
Hope that helps.
kerryh said:
Have flashed this GPE firmware and had some good fun with it. .
Click to expand...
Click to collapse
That is not firmware, its a full RUU. Its important to realize the difference.
Its also important to not use the word "firmware" interchangeably with ROM or OS. Firmware means something very specific on this device (we are usually referring to firmware.zip when saying "firmware"). If you mean ROM, say ROM; if you mean RUU, say RUU. Keep it simple, and avoid unnecessary confusion.
---------- Post added at 12:56 PM ---------- Previous post was at 12:48 PM ----------
93boba said:
I got One M8 GSM s-off, unlocked bootloader and supercid.
It is sense based variant, not GPE.
Can I flash any firmware now (GPE firmware over my Default Sense) ?
Click to expand...
Click to collapse
Again, I don't think you really mean "firmware". I think you just mean a GPE ROM. Don't use the terms ROM and firmware interchangeably, they don't mean the same thing on this device.
You can just flash a GPE based custom ROM to your Sense partitioned phone. That is the easiest way to go GPE.
You can "fully convert" to GPE using the RUU the previous response linked. But keep in mind, this changes the partitioning, and renders your phone unable to run almost all Sense ROMs, since the system (ROM) partition on the GPE version is too small to accept Sense ROMs. This means, if you want to go back to Sense, you need to "convert" back. If the purpose is just to try out the GPE interface, just flash a GPE custom ROM, as I mentioned.
The only reasons to "fully convert" to RUU are:
1) Take advantage of the GPE partition scheme (smaller system partition makes the user accessible storage larger)
2) Get official OTA updates.
redpoint73 said:
That is not firmware, its a full RUU. Its important to realize the difference.
Its also important to not use the word "firmware" interchangeably with ROM or OS. Firmware means something very specific on this device (we are usually referring to firmware.zip when saying "firmware"). If you mean ROM, say ROM; if you mean RUU, say RUU. Keeps it simple, and avoid unnecessary confusion.
Click to expand...
Click to collapse
I stand corrected. Thank you for clarifying. Do you know where I can find any "literature" that goes in depth between the two. I see firmware amd RUU in (what seems to me) the same context. I am obviously mistaken and would like to know the specifics between the two. I know that ROM is referring to specifically the system files and not much, if anything, else. Does firmware have a specific partition it is associated with in the same way that a ROM is? (I see on some threads that there is firmware in the same discussion w ROM (the one that comes to mind is found here).
Thank you for stepping in and saying something. I hate speaking about a subject and having bad information thinking it is right. Much oblige.
kerryh said:
I stand corrected. Thank you for clarifying. Do you know where I can find any "literature" that goes in depth between the two. I see firmware amd RUU in (what seems to me) the same context. I am obviously mistaken and would like to know the specifics between the two. I know that ROM is referring to specifically the system files and not much, if anything, else. Does firmware have a specific partition it is associated with in the same way that a ROM is?
Click to expand...
Click to collapse
I don't know of any "literature" that quite explains what you are asking for, but the following threads explain firmwrae a bit: http://forum.xda-developers.com/showthread.php?p=52484527#post52484527
http://forum.xda-developers.com/showthread.php?t=2696282
Part of the confusion, is that in the past, lots of folks have used the word "firmware" interchangeably with ROM. The confusion comes in, here HTC started deploying very specific partition updates in a package named "firmware.zip" and therefore you have lots of folks calling those packages "firmware" and therefore at least for this device the most common (and IMO correct) usage of the word "firmware".
Firmware.zip specifically contains a number of partitions (hboot, radio, stock recovery, boot.img, Bluetooth, WiFi, Media, and some others). I don't know that exact number, maybe 10 partitions. But system (OS or ROM) is not one of those.
RUU is a complete stock image, and contains something like 41 partitions, including firmware, and system. RUU is something very specific, so its best to describe it as such "RUU".
To further add to the confusion, you can extract a ROM.zip from the RUU, which is actually all of the same (about 41) partitions.
But this isn't what folks are talking about when they say "ROM" here. Usually folks mean a custom recovery-flashable zip (made by the developer community here) that typically only contains system and boot.img partitions.
In all fairness, these terms are all a bit nebulous; at least in their origins. Technically, "firmware" just means some type of code that can be flashed to a device (or something to that effect). The term "ROM" itself is also antiquated, referring to "Read Only Memory" of the early computer days. Obviously, these terms take on somewhat different meanings as technology evolves; and depending on the devices being discussed. All the more reason to be specific as possible.
redpoint73 said:
I don't know of any "literature" that quite explains what you are asking for, but the following threads explain firmwrae a bit: http://forum.xda-developers.com/showthread.php?p=52484527#post52484527
http://forum.xda-developers.com/showthread.php?t=2696282
Part of the confusion, is that in the past, lots of folks have used the word "firmware" interchangeably with ROM. The confusion comes in, here HTC started deploying very specific partition updates in a package named "firmware.zip" and therefore you have lots of folks calling those packages "firmware" and therefore at least for this device the most common (and IMO correct) usage of the word "firmware".
Firmware.zip specifically contains a number of partitions (hboot, radio, stock recovery, boot.img, Bluetooth, WiFi, Media, and some others). I don't know that exact number, maybe 10 partitions. But system (OS or ROM) is not one of those.
RUU is a complete stock image, and contains something like 41 partitions, including firmware, and system. RUU is something very specific, so its best to describe it as such "RUU".
To further add to the confusion, you can extract a ROM.zip from the RUU, which is actually all of the same (about 41) partitions.
But this isn't what folks are talking about when they say "ROM" here. Usually folks mean a custom recovery-flashable zip (made by the developer community here) that typically only contains system and boot.img partitions.
In all fairness, these terms are all a bit nebulous; at least in their origins. Technically, "firmware" just means some type of code that can be flashed to a device (or something to that effect). The term "ROM" itself is also antiquated, referring to "Read Only Memory" of the early computer days. Obviously, these terms take on somewhat different meanings as technology evolves; and depending on the devices being discussed. All the more reason to be specific as possible.
Click to expand...
Click to collapse
Thank you for explaining that. You didn't have to yet you took the time anyways. Props to you kind sir.
I'm preparing to unlock/root my 10 and if I'm going to go S-OFF this would be the time to do it. I'm just trying to figure out how necessary it really is. Since my phone's CID is presumably something like HTC_001, that should be included in any OEM firmware updates that are released, right? Assuming the signed firmware updates are posted here when they are released, I can just flash them without issue as far as I understand it. So, why would I need to S-OFF if I'm on an unbranded device?
I believe, and someone correct me if I'm wrong, but one of the biggest advantages of S-Off'ing is being able to flash ROMs that can take more control over the ecosystem. You get more control over your phone basically. As long as you're smart about what you flash/install to your device, there's not really any downside as long as you're okay dropping the $25 for sunshine.
So some ROMs have features that require S-OFF? As far as I know, just being unlocked and rooted will allow you to fully take advantage of LeeDroid, for instance. I thought S-OFF just applied to flashing firmware.
goodtimes50 said:
So some ROMs have features that require S-OFF? As far as I know, just being unlocked and rooted will allow you to fully take advantage of LeeDroid, for instance. I thought S-OFF just applied to flashing firmware.
Click to expand...
Click to collapse
Correct rom-wise there is no real advantage. Everything will work flawlessly with s-on.
http://forum.xda-developers.com/showthread.php?t=1868181
http://www.androidbeat.com/2014/07/s-htc-device-mean/
The things you can't do without S-Off are:
*flash unsigned firmware packages
*flash firmware packages that don't match CID/MID
*flash RUUs that don't match CID/MID
*change CID/MID
*restore "locked" status (without you can only get "relocked" status)
*restore "software status: official" flag in bootloader (flag sets to "software status: modified" if you flash anything)
Want a custom splash screen? Need S-Off.
Want to get rid of the red text warning during boot? Need S-Off.
Want to flash a different radio? Need S-Off.
What you can do without S-Off:
*unlock bootloader (via HTCdev)
*flash recovery
*root (via superSU package or your favorite custom ROM)
*flash ROMs
Nosferatu. said:
Want a custom splash screen? Need S-Off.
Want to get rid of the red text warning during boot? Need S-Off.
Want to flash a different radio? Need S-Off.
Click to expand...
Click to collapse
Sure looks like a quote from a post I made a while ago ) Not sure if this is entirely accurate for HTC 10 either, I'm definitely not hex-editing the aboot before I know it's safe to do so.
Nosferatu. said:
The things you can't do without S-Off are:
*flash unsigned firmware packages
*flash firmware packages that don't match CID/MID
*flash RUUs that don't match CID/MID
*change CID/MID
*restore "locked" status (without you can only get "relocked" status)
*restore "software status: official" flag in bootloader (flag sets to "software status: modified" if you flash anything)
Want a custom splash screen? Need S-Off.
Want to get rid of the red text warning during boot? Need S-Off.
Want to flash a different radio? Need S-Off.
What you can do without S-Off:
*unlock bootloader (via HTCdev)
*flash recovery
*root (via superSU package or your favorite custom ROM)
*flash ROMs
Click to expand...
Click to collapse
Hey, this mixing of terminology is killing me
Isn't ROM and Firmware the same thing? If not then could you define both? I'm asking because to me those 2:
"flash unsigned firmware packages"
"flash ROMs"
look the same, no? Or by "firmware packages" you mean the images that are inside the zip package, like boot.img, recovery.img etc? But if so, then how can I flash the custom recovery (like TWRP) which I assume is not signed if I don't have S-off?
lukair1983 said:
Hey, this mixing of terminology is killing me
Isn't ROM and Firmware the same thing? If not then could you define both? I'm asking because to me those 2:
"flash unsigned firmware packages"
"flash ROMs"
look the same, no? Or by "firmware packages" you mean the images that are inside the zip package, like boot.img, recovery.img etc? But if so, then how can I flash the custom recovery (like TWRP) which I assume is not signed if I don't have S-off?
Click to expand...
Click to collapse
No, they're not the same. Think of the firmware as the level between the software (recovery/ROM) and the physical hardware. Firmware contains stuff like radios, CPU governors, camera drivers, etc.
I see. So when people receive OTA's they receive firmware ALONG with other stuff (boot, recovery, system images etc.) ?
lukair1983 said:
I see. So when people receive OTA's they receive firmware ALONG with other stuff (boot, recovery, system images etc.) ?
Click to expand...
Click to collapse
That's correct.
I see.
Alright, so to check on that I've downloaded one of the OTA's in the "[STOCK] Guides and Stock Backups/Recovery/OTA/RUU" thread and indeed there is firmware.zip inside. I assume that's what you guys meant. However I don't see there any boot.img, recovery.img etc. What am I missing here in my understanding?
Nosferatu. said:
The things you can't do without S-Off are:
*flash unsigned firmware packages
*flash firmware packages that don't match CID/MID
*flash RUUs that don't match CID/MID
*change CID/MID
*restore "locked" status (without you can only get "relocked" status)
*restore "software status: official" flag in bootloader (flag sets to "software status: modified" if you flash anything)
Want a custom splash screen? Need S-Off.
Want to get rid of the red text warning during boot? Need S-Off.
Want to flash a different radio? Need S-Off.
What you can do without S-Off:
*unlock bootloader (via HTCdev)
*flash recovery
*root (via superSU package or your favorite custom ROM)
*flash ROMs
Click to expand...
Click to collapse
This...
Except I haven't noticed red text on boot with this device.
Where you're going to really want s-off, is when Android N is released and you've got a carrier branded phone. Usually new Android versions require updated firmware to operate properly. If you're s-off, you can flash the first firmware that's available for the device. If not, you're stuck waiting for your carrier to update you. Real world example... AT&T JUST released marshmallow last week for the M9. With s-off, I've been on 6 since December. Otherwise I would have been stuck on lollipop.
To a slightly lesser degree is when HTC releases a major upgrade within an Android version. For example, there will probably be a 2.xx.xxx.x release that's still marshmallow. You could face issues trying to run a new base rom on older firmware, but sometimes it works fine. Having said that, you can always stay on the custom rom that's built on your base. Rom developers leave older versions available so you can find one that matches your device.
Basically, in a nut shell, s-on, you're tied to your carrier for firmware updates. S-off you're not.
---------- Post added at 09:17 AM ---------- Previous post was at 09:13 AM ----------
lukair1983 said:
I see.
Alright, so to check on that I've downloaded one of the OTA's in the "[STOCK] Guides and Stock Backups/Recovery/OTA/RUU" thread and indeed there is firmware.zip inside. I assume that's what you guys meant. However I don't see there any boot.img, recovery.img etc. What am I missing here in my understanding?
Click to expand...
Click to collapse
Those are inside firmware.zip.
Here is a link to the unsigned firmware.zip for us unlocked.
https://drive.google.com/file/d/0B8OH6sFjVE1ld1ptNTFEaEc3Rms/view?usp=drivesdk
Firmware was 80 something MB, entire ota was over 400, so there was a lot that was updated besides firmware.
Or, have the unbranded, unlocked version from HTC and not have to worry about too much.
Sent from my HTC 10 using XDA-Developers mobile app
jollywhitefoot said:
This...
Except I haven't noticed red text on boot with this device.
Where you're going to really want s-off, is when Android N is released and you've got a carrier branded phone. Usually new Android versions require updated firmware to operate properly. If you're s-off, you can flash the first firmware that's available for the device. If not, you're stuck waiting for your carrier to update you.
Click to expand...
Click to collapse
jollywhitefoot, what if you have unlocked phone bought direcly from htc? I assume at this point there will be no problem with Android N while being at the same time s-on, correct? (taking into account being unlocked and rooted and having custom recovery)
jollywhitefoot said:
Those are inside firmware.zip.
Here is a link to the unsigned firmware.zip for us unlocked.
https://drive.google.com/file/d/0B8OH6sFjVE1ld1ptNTFEaEc3Rms/view?usp=drivesdk
Firmware was 80 something MB, entire ota was over 400, so there was a lot that was updated besides firmware.
Click to expand...
Click to collapse
Thanks a lot for the image!
So, the thing that goodtimes50 said was not correct? Talking about a phrase: "No, they're not the same. Think of the firmware as the level between the software (recovery/ROM) and the physical hardware. Firmware contains stuff like radios, CPU governors, camera drivers, etc.". If the firmware contains the recovery, and clearly your image shows that, then the "firmware" can't be a bridge or a level between those things that goodtimes50 mentioned.
So would it be accurate if I said that firmware contains everything that doesn't have to do directly with the OS itself? Meaning, that when I say "ROM" I would think of a system image (being OS), maybe the data image as some additional applications etc?
The terminology is just crazy, somebody must do an encyclopedia for the Android terminology!
lukair1983 said:
jollywhitefoot, what if you have unlocked phone bought direcly from htc? I assume at this point there will be no problem with Android N while being at the same time s-on, correct? (taking into account being unlocked and rooted and having custom recovery)
Thanks a lot for the image!
So, the thing that goodtimes50 said was not correct? Talking about a phrase: "No, they're not the same. Think of the firmware as the level between the software (recovery/ROM) and the physical hardware. Firmware contains stuff like radios, CPU governors, camera drivers, etc.". If the firmware contains the recovery, and clearly your image shows that, then the "firmware" can't be a bridge or a level between those things that goodtimes50 mentioned.
So would it be accurate if I said that firmware contains everything that doesn't have to do directly with the OS itself? Meaning, that when I say "ROM" I would think of a system image (being OS), maybe the data image as some additional applications etc?
The terminology is just crazy, somebody must do an encyclopedia for the Android terminology!
Click to expand...
Click to collapse
What he said is correct and what you said is correct. Recovery and boot are always included in firmware packages but technically they're not firmware files.
As for us unlocked, you get updates directly from HTC, so you're not waiting for a carrier. The US unlocked version isn't always the first to get updated, though. A lot of times Europe and Asia get the update first.
Good thing I'm not in US then
(Just kidding I know it has to do with the phone version not a location)
Thanks a lot jollywhitefoot. I'm getting closer to grasping the whole HTC ecosystem. The last stop would be to understand what I will have to do to update my OS when next OTA's start appearing as I intend to unlock bootloader, flash TWRP and flash SU so that I get root. I do however intend to keep the s-on. From what I read s-off really is mostly used to change the cid, as almost everything else can be done with s-on (aside from messing with radio or splash screens but I don't care about that). Besides that s-on is more secure than s-off as I will not be able to brick my phone that way no matter what I do.
From my understanding I won't be able to update with OTA that easly afterwards. Well, I don't mind a bit of a hassle as long as I keep my OS setup, my apps, their settings and my data on internal storage. Is it possible that there will be a flashable zip's made by the scene that will do basicaly the same as the OTA, but I will not have to restore stock recovery, formware, flash the OTA, then reflash the TWRP as well as reroot or it's simply impossible to do and the "hassle thing" is unavoidable?
lukair1983 said:
jollywhitefoot, what if you have unlocked phone bought direcly from htc? I assume at this point there will be no problem with Android N while being at the same time s-on, correct? (taking into account being unlocked and rooted and having custom recovery)
Click to expand...
Click to collapse
That's basically what I'm trying to figure out. For an unbranded phone, wouldn't the signed firmware files get posted here as soon as they're available and we can just flash away?
lukair1983 said:
Is it possible that there will be a flashable zip's made by the scene that will do basicaly the same as the OTA, but I will not have to restore stock recovery, formware, flash the OTA, then reflash the TWRP as well as reroot or it's simply impossible to do and the "hassle thing" is unavoidable?
Click to expand...
Click to collapse
If you're S-OFF, yes. Otherwise, no.
Captain_Throwback said:
If you're S-OFF, yes. Otherwise, no.
Click to expand...
Click to collapse
Is that because when unlocked and s-on the only partitions I can modify are system, boot and recovery while the complete rom/ota might also contain other stuff like bootloader, radio, other firmare things etc. and those I will not be able to flash even in fastboot? Is that the reason?