Hello
My htc one m8 is the Asian version (HTC__044) , upon using getvar all, I noticed that my version-main was missing along with the os in hboot. If I were to flash a firmware, would I need to relock the bootloader? Would I lose my data on locking the bootloader? Also, im on base .401 , would I directly be able to flash a .707?
Thanks in advance.
wasdapple said:
If I were to flash a firmware, would I need to relock the bootloader?
Click to expand...
Click to collapse
If s-on, yes. Otherwise if s-off, no.
Also, be aware that with s-on you can only flash a firmware that is HTC signed/encrypted. Some are not, and require s-off.
wasdapple said:
Would I lose my data on locking the bootloader?
Click to expand...
Click to collapse
Yes.
wasdapple said:
Also, im on base .401 , would I directly be able to flash a .707?
Click to expand...
Click to collapse
How are you determining 401? From what I'm seeing, the stock software/firmware for your CID should be 707.
You should be able to flash 707 firmware (assume you want to update to Lollipop) on your version, provided the previously mentioned requirements are met.
redpoint73 said:
If s-on, yes. Otherwise if s-off, no.
Also, be aware that with s-on you can only flash a firmware that is HTC signed/encrypted. Some are not, and require s-off.
Yes.
How are you determining 401? From what I'm seeing, the stock software/firmware for your CID should be 707.
You should be able to flash 707 firmware (assume you want to update to Lollipop) on your version, provided the previously mentioned requirements are met.
Click to expand...
Click to collapse
Thanks for replying. I believe it may have been the rom ive installed that changed my firmware, along with the fact it writes .401 on my software information page. Yes the default firmware should be .707 which I believe is also the main cause of my inability to connect to 4g in my area.
So assuming I find a signed firmware for .707 I would simply be able to flash it on the .401? Or would I have to still relock my bootloader.
Also, would the empty os/ version-main be a problem and if so how do I fix it.
Thanks for replying as you've also helped me a great deal the previous time.
wasdapple said:
I believe it may have been the rom ive installed that changed my firmware, along with the fact it writes .401 on my software information page.
Click to expand...
Click to collapse
Flashing a ROM will not change your firmware. It does change software number, so if that is where you are getting 401 from, that is normal. Software number is just the base of your current ROM, not your firmware number.
Your firmware number is indicated on your bootloader screen under "OS" and also as "main version" when doing getvar all.
wasdapple said:
So assuming I find a signed firmware for .707 I would simply be able to flash it on the .401? Or would I have to still relock my bootloader.
Click to expand...
Click to collapse
Are you s-on or s-off?
If still s-on, there is no way you could have ever flashed a 401 firmware on your phone. I still think you are confused between software and firmware numbers, and I don't guess that you ever flashed a 401 firmware.
If you are s-on, I still think you are on 707 firmware, and there is some other factor causing your 4G problem.
Yes, you need to relock your bootloader to flash 707 firmware while s-on. If you are s-off, you don't need to relock the bootloader.
wasdapple said:
Also, would the empty os/ version-main be a problem and if so how do I fix it.
Click to expand...
Click to collapse
It shouldn't be a problem. It will be fixed if you flash a firmware.
This bug was caused by older versions of TWRP. If you flash a current version of TWRP after flashing firmware, the problem should not re-occur.
---------- Post added at 10:19 AM ---------- Previous post was at 10:17 AM ----------
wasdapple said:
Thanks for replying as you've also helped me a great deal the previous time.
Click to expand...
Click to collapse
We always like repeat customers, and satisfied ones.
So is it possible that I am actually on 707 but my rom is making it show 401? Im terribly sorry for my lack of understanding of this whole situation.
Would using the twrp app on the play store update twrp? It should fix the empty main-version ?
wasdapple said:
So is it possible that I am actually on 707 but my rom is making it show 401? Im terribly sorry for my lack of understanding of this whole situation.
Click to expand...
Click to collapse
I know in the past, folks have often used the word "firmware" to mean the same as the ROM. But you should probably erase that notion from your mind. On this device, the word "firmware" is used specifically to partitions that are not flashed when you flash a ROM, and include hboot, radio, WiFi, Bluetooth, and others.
Yes, your firmware may still be 707 (which can normally be found as OS number on hboot screen, or main version when doing getvar all); while your software (ROM) which is shown in Settings>About>Software information can be 401. Firmware and ROM are 2 completely different things.
I've asked twice now, are you s-on or s-off?
wasdapple said:
Would using the twrp app on the play store update twrp? It should fix the empty main-version ?
Click to expand...
Click to collapse
TWRP Manager app will update TWRP, yes.
You can also just download the latest version and flash with fastboot, which is my preferred method: https://twrp.me/devices/htconem8gsm.html
However, this alone won't fix the issue of main version missing, I don't believe. It will only stop if from re-occurring. But the only way to get the main version back is to flash a firmware. After that, having an updated TWRP will stop if from main version displaying "blank" again. If you use an old TWRP, it will blank out the main version again.
Get it?
I'm sorry I kept forgetting to reply to that, I am actually s-on.
So for instance I want to be back on 707 I should just revert to rooted stock?
wasdapple said:
I'm sorry I kept forgetting to reply to that, I am actually s-on.
Click to expand...
Click to collapse
Than its simply impossible for you to ever have flashed a 401 firmware. Some of the firmware partitions (hboot, radio) are write protected with s-on, and can only be flashed with your CID version firmware (707).
wasdapple said:
So for instance I want to be back on 707 I should just revert to rooted stock?
Click to expand...
Click to collapse
Yes, rooted or unrooted should be fine.
But you will want to make sure your firmware and software versions match up. What are your hboot and radio numbers? Do you remember if you were on Lollipop before unlocking the bootloader?
My hboot would be 3.19.0.0000 and my radio is 1.25.21331147A1.06G
Yep I was on lollipop before unlocking my bootloader.
wasdapple said:
My hboot would be 3.19.0.0000 and my radio is 1.25.21331147A1.06G
Yep I was on lollipop before unlocking my bootloader.
Click to expand...
Click to collapse
You can get the stock 4.19.707.2 nandrioid here (Post #2): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Keep in mind, this is a TWRP "nandroid" backup, not a flashable ROM zip. So follow the directions carefully to restore this stock nandroid.
Also note that this is the stock ROM, not the firmware.
Would I get back my 707 if I flashed this instead http://forum.xda-developers.com/htc...-sd-14-19-707-21st-android-5-0-sense-t3010391 ?
im seeing an Asian wwe base and it is 707.
Also I wouldn't be able to dirty flash a completely different rom right?
wasdapple said:
Would I get back my 707 if I flashed this instead http://forum.xda-developers.com/htc...-sd-14-19-707-21st-android-5-0-sense-t3010391 ?
Click to expand...
Click to collapse
Not sure what you mean by "get back my 707", and you need to explain more clearly.
If the intent is to return to 707 firmware, its not needed, I'm confidant you already are on current 707 firmware. And flashing a ROM does not change your firmware (as I've already explained multiple times).
If the intent is to make the main version appear again, flashing a ROM won't do that either. As mentioned, you can only make that reappear by flashing a firmware.zip (not a ROM.zip).
If the intent is to just return to a 707 ROM base, then yes the ROM you linked will do that. But the only reason I see for you to do so, is to see if it helps your network issue. Using ROMs of other bases will not normally affect network service (as long as your carrier's APN is correct). And I've already linked you to stock 707 nandroid, which is probably the best baseline to troubleshoot from. Or are you not comfortable with the nandroid restore process?
Again, you haven't really explained what you are trying to accompish; so its hard to answer the question.
wasdapple said:
Also I wouldn't be able to dirty flash a completely different rom right?
Click to expand...
Click to collapse
If the ROM is a similar enough base, it might be possible to dirty flash. But its not recommended, and still possible to have various severe bugs, or not even boot. Therefore, full wipe is normally recommended when moving between different ROMs (and often even major updates of the "same" ROM).
Any person flashing ROMs should know how to backup and restore their personal data (using Titanium Backup and/or other means) when moving between ROMs.
Sorry for my vagueness in my previous post. Currently in my phone settings, the build number is 4.26.401. , which is the base of my current rom? So supposedly if I flash an Asian wwe would I get my software base back to a 707 as in the link.
Also, you mentioned for me to flash my firmware as per my cid, which could be found in most firmware dumps? Would be it be possible to link one to me? And if I am in fact on a 707, do I still flash 707 firmware?
The reason why I an unwilling to go through with nandroid is that I am not exactly looking to restore to stock, I like to have customs roms and the root capabilities. My ultimate objective is to get back to 707, or at least get it to appear on my software information screen. To my knowledge, 401 is for the European countries and the basebands for 4g LTE is different, thus I am unable to find out why if I am s-on with my firmware and radio intact I could not connect to my local 4g LTE, and to my point of view, only through flashing a firmware affect everything.
Im sorry for this large amount questions and extremely grateful you have taken the time to tend to it. I sincerely apologise if I seem to keep insisting that my firmware has changed despite your reminders.
I've actually been trying to update the firmware on my M8 today as well, but when I go to "flashboot flash zip firmware.zip" I am returned the message "not enough space."
I've cleared the cache successfully, and that didn't open up enough space. I tried to delete userdata, but it wouldn't let me do it remotely.
So I'm a little confused as to my next move here...
and I've relocked my phone and s-on.
wasdapple said:
Sorry for my vagueness in my previous post. Currently in my phone settings, the build number is 4.26.401. , which is the base of my current rom? So supposedly if I flash an Asian wwe would I get my software base back to a 707 as in the link.
Also, you mentioned for me to flash my firmware as per my cid, which could be found in most firmware dumps? Would be it be possible to link one to me? And if I am in fact on a 707, do I still flash 707 firmware?
The reason why I an unwilling to go through with nandroid is that I am not exactly looking to restore to stock, I like to have customs roms and the root capabilities. My ultimate objective is to get back to 707, or at least get it to appear on my software information screen. To my knowledge, 401 is for the European countries and the basebands for 4g LTE is different, thus I am unable to find out why if I am s-on with my firmware and radio intact I could not connect to my local 4g LTE, and to my point of view, only through flashing a firmware affect everything.
Im sorry for this large amount questions and extremely grateful you have taken the time to tend to it. I sincerely apologise if I seem to keep insisting that my firmware has changed despite your reminders.
Click to expand...
Click to collapse
Yes. You will get your software number back if you flash a 707 based ROM, such as stock.
So, here we go.
Download this 4.19.707.2 RUU onto your PC
When the download is finished, plug your phone into your PC, double click on the downloaded file, and follow the prompts. This will update you to Lollipop and you will be on the stock ROM again.
Since you are S-On, you will first need to relock the bootloader.
In fastboot (obviously) fastboot oem lock before you proceed with this.
Also, THIS WILL WIPE YOUR PHONE, so be sure to backup anything that is important to you.
Is the ruu rooted, or purely stock pre-root?
Kindrex said:
I've actually been trying to update the firmware on my M8 today as well, but when I go to "flashboot flash zip firmware.zip" I am returned the message "not enough space."
I've cleared the cache successfully, and that didn't open up enough space. I tried to delete userdata, but it wouldn't let me do it remotely.
So I'm a little confused as to my next move here...
and I've relocked my phone and s-on.
Click to expand...
Click to collapse
What is your current OS number on the bootloader screen, and what firmware are you trying to flash?
---------- Post added at 10:53 AM ---------- Previous post was at 10:21 AM ----------
wasdapple said:
Sorry for my vagueness in my previous post. Currently in my phone settings, the build number is 4.26.401. , which is the base of my current rom? So supposedly if I flash an Asian wwe would I get my software base back to a 707 as in the link.
The reason why I an unwilling to go through with nandroid is that I am not exactly looking to restore to stock, I like to have customs roms and the root capabilities. My ultimate objective is to get back to 707, or at least get it to appear on my software information screen. To my knowledge, 401 is for the European countries and the basebands for 4g LTE is different, thus I am unable to find out why if I am s-on with my firmware and radio intact I could not connect to my local 4g LTE, and to my point of view, only through flashing a firmware affect everything.
Im sorry for this large amount questions and extremely grateful you have taken the time to tend to it. I sincerely apologise if I seem to keep insisting that my firmware has changed despite your reminders.
Click to expand...
Click to collapse
If the intent it to return to 707 based ROM to see if that helps your 4G issue, then yes the custom ROM you previously posted will do that. It will also make 707 appear for software number in the phone Settings.
wasdapple said:
Also, you mentioned for me to flash my firmware as per my cid, which could be found in most firmware dumps? Would be it be possible to link one to me? And if I am in fact on a 707, do I still flash 707 firmware?
Click to expand...
Click to collapse
I was more talking "if" you can find the 4.16.707 firmware. The main firmware collection I refer to doesn't have 4.16.707, just old 707 firmwares (which you don't want)]: http://forum.xda-developers.com/showthread.php?t=2696282
If the firmware can't be found, the RUU listed by xunxholyx is your best bet if you really want to flash the 707 firmware. But I really don't think this is needed. As I'm nearly 100% sure you are already on the current 707 firmware, and the only benefit of flashing the 707 firmware (by RUU) is to get the OS number to appear again on the bootloader screen and on getvar all (which is really not that important).
On the other hand, RUU to full stock may be a good way to troubleshoot your 4G issue, especially if flashing the 707 based custom ROM still doesn't fix the issue. RUU is not just a stock ROM, but a complete factory image, complete with bootloader, radio, etc.
---------- Post added at 11:08 AM ---------- Previous post was at 10:53 AM ----------
wasdapple said:
Is the ruu rooted, or purely stock pre-root?
Click to expand...
Click to collapse
It appears to be 100% official and stock (unrooted). It will also wipe your phone.
---------- Post added at 11:09 AM ---------- Previous post was at 11:08 AM ----------
xunholyx said:
Yes. You will get your software number back if you flash a 707 based ROM, such as stock.
So, here we go.
Download this 4.19.707.2 RUU onto your PC
Click to expand...
Click to collapse
Nice find. I didn't know Asia version had any RUUs.
redpoint73 said:
Nice find. I didn't know Asia version had any RUUs.
Click to expand...
Click to collapse
Yeah, they are hard to come by. I was helping a user here six to eight weeks ago, and told him I didn't know of any Asia RUUs. He came back the next day replying that he found one, so I asked for the link and gave it to Sneakyghost and Alex (from AFH) to upload to androidruu.com
They have a few that aren't common there, and are always looking for more hard to find ones. If you come across one, you could PM me or Sneakyghost to have it added. Always nice to have a good RUU repository to go to.
Hey everyone. I'm having a similar issue, and I don't want to start a new thread, so I'm going to add on to this one.
I've been on AOKP since it was released for this phone, so I've missed out on some OTA updates. Every time I try to flash a Lollipop ROM I get all these weird issues (WiFi not working, systemUI crashes, etc.), and after reading a few threads, I believe its an issue with the firmware.
I tried going back to stock, but the only Nandroid backup I could find for my phone isn't compatible with my firmware (WiFi refuses to work, only data). So I was wondering what else I could do to update the firmware. Reading this thread, it looks like the RUU is another method, but I'm not too sure how to get started with that, or which one to use, as my OS in the Bootloader and my version-main is blank.
Any advice is appreciated, please let me know if you need more info.
My Device:
Rooted
TWRP 2.8.7.0
S-Off
CID-TELUS001
watidk said:
I tried going back to stock, but the only Nandroid backup I could find for my phone isn't compatible with my firmware (WiFi refuses to work, only data). So I was wondering what else I could do to update the firmware. Reading this thread, it looks like the RUU is another method, but I'm not too sure how to get started with that, or which one to use, as my OS in the Bootloader and my version-main is blank.
Any advice is appreciated, please let me know if you need more info.
My Device:
Rooted
TWRP 2.8.7.0
S-Off
CID-TELUS001
Click to expand...
Click to collapse
What are your hboot and radio numbers?
Related
Hey guys, I'm running ViperOne 2.4.0. with TWRP recovery installed. For some reason when it boots up, the only thing it shows is an unusual HTC splash screen with red writing at the bottom, similar to if it were booting into recovery, but without the pink "entering recovery" message at the top. What is causing this, can it be changed by adding a new splash screen and/or boot animation? It just stays on this screen for a painfully long time, and then goes black. I tap the screen and it's on, and everything is fine. Thanks in advance.
chattguy said:
Hey guys, I'm running ViperOne 2.4.0. with TWRP recovery installed. For some reason when it boots up, the only thing it shows is an unusual HTC splash screen with red writing at the bottom, similar to if it were booting into recovery, but without the pink "entering recovery" message at the top. What is causing this, can it be changed by adding a new splash screen and/or boot animation? It just stays on this screen for a painfully long time, and then goes black. I tap the screen and it's on, and everything is fine. Thanks in advance.
Click to expand...
Click to collapse
I've got the same issue..... plz help.
Because you guys on the lower version firmware which is meant for 4.4.2
And the ROM requires a newer firmware for 4.4.3
ckpv5 said:
Because you guys on the lower version firmware which is meant for 4.4.2
And the ROM requires a newer firmware for 4.4.3
Click to expand...
Click to collapse
Okay.....so can I update the firmware? Do I have to be truly S-off to do that?
chattguy said:
Okay.....so can I update the firmware? Do I have to be truly S-off to do that?
Click to expand...
Click to collapse
You don't need S-Off to upgrade firmware with official untouched firmware.
With S-On you can't downgrade.
I believe your device is T-Mobile so grab the OTA.zip from T-Mobile section and extract out the firmware and use it.
Or.. do a proper OTA update.... or use the RUU ... all your answers are in T-Mobile section
---------- Post added at 12:24 AM ---------- Previous post was at 12:20 AM ----------
oogierule said:
I've got the same issue..... plz help.
Click to expand...
Click to collapse
And yours ... the same as above but the AT&T ones in AT&T section
ckpv5 said:
You don't need S-Off to upgrade firmware with official untouched firmware.
With S-On you can't downgrade.
I believe your device is T-Mobile so grab the OTA.zip from T-Mobile section and extract out the firmware and use it.
Or.. do a proper OTA update.... or use the RUU ... all your answers are in T-Mobile section
---------- Post added at 12:24 AM ---------- Previous post was at 12:20 AM ----------
And yours ... the same as above but the AT&T ones in AT&T section
Click to expand...
Click to collapse
Okay, and to find out the current firmware I'm running, that's listed as "Build Number" in settings, yes? It says I'm currently running 2.22.531.5 CL365360 release-keys. Is there a newer firmware than that? If so I'm not finding it.
chattguy said:
Okay, and to find out the current firmware I'm running, that's listed as "Build Number" in settings, yes? It says I'm currently running 2.22.531.5 CL365360 release-keys. Is there a newer firmware than that? If so I'm not finding it.
Click to expand...
Click to collapse
I never know a Viper ROM is based on 2.22.531.5 CL365360 release-keys Your OP is mentioning about Viper.
Firmware is what written on bootloader - OS : ?????????
In Build Number in settings is the ROM version.
Well I guess I need to stop responding to Q&A for devices which have their own specific forum ....
I know nothing when it comes to T-Mobile, AT&T, Sprint and Verizon ... sorry
users with specific device can understand better and offer a better help and advice.
always wondering why people with specific device with specific forum post in Int'l GSM forum
ckpv5 said:
I never know a Viper ROM is based on 2.22.531.5 CL365360 release-keys Your OP is mentioning about Viper.
Firmware is what written on bootloader - OS : ?????????
In Build Number in settings is the ROM version.
Well I guess I need to stop responding to Q&A for devices which have their own specific forum ....
I know nothing when it comes to T-Mobile, AT&T, Sprint and Verizon ... sorry
users with specific device can understand better and offer a better help and advice.
always wondering why people with specific device with specific forum post in Int'l GSM forum
Click to expand...
Click to collapse
First of all, this isn't an "international GSM" forum. It's an HTC One M8 forum. That to me, means that it's for all users of this particular phone. Second, there is nothing that explains in explicit detail how I can fix this particular problem, in the T-Mo specific forum. Anyway, thanks.
chattguy said:
First of all, this isn't an "international GSM" forum. It's an HTC One M8 forum. That to me, means that it's for all users of this particular phone. Second, there is nothing that explains in explicit detail how I can fix this particular problem, in the T-Mo specific forum. Anyway, thanks.
Click to expand...
Click to collapse
No problem about that ... it just me need to learn not to respond to specific device Q&A
Anyway ...about the firmware ... what is it ? Not the one written in build numbers ... what's the one written on bootloader ?
ckpv5 said:
No problem about that ... it just me need to learn not to respond to specific device Q&A
Anyway ...about the firmware ... what is it ? Not the one written in build numbers ... what's the one written on bootloader ?
Click to expand...
Click to collapse
Here's what it says:
HBOOT 3.16.0.0000
Radio-1.16.21331931.LA24G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
chattguy said:
Here's what it says:
HBOOT 3.16.0.0000
Radio-1.16.21331931.LA24G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Click to expand...
Click to collapse
That's what I'm trying to tell.
You do have a lower version firmware meant for 4.4.2 (the reason why it takes long time to boot and the black screen)
Firmware 4.4.3 has hboot 3.18.0.000 or greater than 3.16.0.0000
ckpv5 said:
That's what I'm trying to tell.
You do have a lower version firmware meant for 4.4.2 (the reason why it takes long time to boot and the black screen)
Firmware 4.4.3 has hboot 3.18.0.000 or greater than 3.16.0.0000
Click to expand...
Click to collapse
Do I flash this in Hboot? Do I need to be on a stock rom, or S-off? I'd rather not have to deal with that if I can help it.
chattguy said:
Do I flash this in Hboot? Do I need to be on a stock rom, or S-off? I'd rather not have to deal with that if I can help it.
Click to expand...
Click to collapse
There is no need to go for S-Off if you don't need it. The only thing is once you updated to 4.4.3, S-Off thru SunShine may not work too. (currently)
So it's all depends on what you want/prefer to do :
1. backup your current Viper ROM and revert to stock ROM and do normal OTA (no need to relock bootloader)
Once complete, reinstall TWRP and restore your Viper ROM backup (so no reinstalling hassle)
or
2. revert to stock ROM with RUU (you need to relock bootloader)
Once complete, you need to reunlock bootloader and install TWRP and restore your backup.
or
3. keep/backup your current setup of Viper ROM and flash only the HTC signed firmware either thru fastboot or use a external_sdcard method. Both way you need to relock bootloader and re-unlock again after complete. Always remember unlocking bootloader will wipe your data. So make a backup to PC first. And you need to reflash TWRP too. You can try without relock bootloader first and see as I can't remember whether it will work on an unlocked bootloader or not. If not working, then try again with relocked bootloader.
I guess you can have all the info and files needed in this thread : http://forum.xda-developers.com/showthread.php?t=2714456
ckpv5 said:
There is no need to go for S-Off if you don't need it. The only thing is once you updated to 4.4.3, S-Off thru SunShine may not work too. (currently)
So it's all depends on what you want/prefer to do :
1. backup your current Viper ROM and revert to stock ROM and do normal OTA (no need to relock bootloader)
Once complete, reinstall TWRP and restore your Viper ROM backup (so no reinstalling hassle)
or
2. revert to stock ROM with RUU (you need to relock bootloader)
Once complete, you need to reunlock bootloader and install TWRP and restore your backup.
or
3. keep/backup your current setup of Viper ROM and flash only the HTC signed firmware either thru fastboot or use a external_sdcard method. Both way you need to relock bootloader and re-unlock again after complete. Always remember unlocking bootloader will wipe your data. So make a backup to PC first. And you need to reflash TWRP too. You can try without relock bootloader first and see as I can't remember whether it will work on an unlocked bootloader or not. If not working, then try again with relocked bootloader.
I guess you can have all the info and files needed in this thread : http://forum.xda-developers.com/showthread.php?t=2714456
Click to expand...
Click to collapse
Okay thanks man. None of that sounds like something I feel like doing this weekend. I'll see how I feel Monday and attempt it. Many thanks for your patience.
Speaking personally, I would say if you currently have the ability to s-off you may as well do it and save yourself some headaches. Reason being, if you're s-off you can, for example, flash a modified firmware that doesn't erase your rom or bootloader, which to me, is a lot less confusing and troublesome. You can also do things like flash different radios, animations, etc without installing new roms and what not. Anyways, that's just my opinion and I don't claim to be an expert or anything, just another random user.
hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
thanks
Run the ruu for your cid and revert to stock
rpimentel1 said:
hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
Click to expand...
Click to collapse
Are you sure you updated the firmware? You're describing the bug that arises from running 1.40 roms on 1.32 firmware.
rpimentel1 said:
hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
thanks
Click to expand...
Click to collapse
You flashed firmware for your specific device in the firmware/RUU thread before clean flashing to the update on viper? Like iElvis said you are describing what some users have posted in a few threads where users checked the 1.40 kernel and 1.40 in base(I think, I haven't flashed viper), but didn't properly flash the firmware for their device via fastboot or RUU back to stock to get official OTA(if OTA was released from HTC for users specific device.). Hope you get it sorted out
Do you have a back up of your system before viper update? (1.90 or below) or back up ROM ?
---------- Post added at 11:05 PM ---------- Previous post was at 10:46 PM ----------
iElvis said:
Are you sure you updated the firmware? You're describing the bug that arises from running 1.40 roms on 1.32 firmware.
Click to expand...
Click to collapse
Correct me if I'm wrong, but I thought viper allowed user (sprint for example) to run their "1.40 base" on old firmware, they just had to select 1.32 kernel in aroma and would lose out on newer features
that's my main thing, I dont really know what my CID is because I superCID when installing the firmware..
iElvis said:
Are you sure you updated the firmware? You're describing the bug that arises from running 1.40 roms on 1.32 firmware.
Click to expand...
Click to collapse
im pretty sure, yes. Because It shows so in Download mode and in the about section of settings of my phone. I came across pre update error 1.90 and it fixed itself when the phone rebooted in downlaod mode.
Had this same issue, you just have to revert back to whatever firmware you were previously on,
No need to clean flash ROM again, just flash the previous firmware the same way you updated it
rpimentel1 said:
that's my main thing, I dont really know what my CID is because I superCID when installing the firmware..
Click to expand...
Click to collapse
You follow instructions and read the FAQ's posted in this thread? Your best bet is to check what firmware number is displayed on download mode, and I'm not familiar of going back to previous firmware on this device(make sure to read all info to prevent any adverse efftects), but I'd check this thread , see if your device is supported and then try restoring previous working backup if that is a plausible solution.
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
rpimentel1 said:
hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
thanks
Click to expand...
Click to collapse
Just flash rom and make sure your on 1.40 firwamre, DO NOT USE EX kernel, or you will have reboots.
If you want to use EX kernel, flash 1.32 firwmare.
EDIT:Are you on tmobile?Because than you need to flash back 1.32 firmware, as our installer will install older tmobile kernel in order for wifi calling to work, or you need to manual flash international boot.img if you want to keep 1.40 firmware.
BUBBA DUB'S said:
You follow instructions and read the FAQ's posted in this thread? Your best bet is to check what firmware number is displayed on download mode, and I'm not familiar of going back to previous firmware on this device(make sure to read all info to prevent any adverse efftects), but I'd check this thread , see if your device is supported and then try restoring previous working backup if that is a plausible solution.
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Click to expand...
Click to collapse
ivicask said:
Just flash rom and make sure your on 1.40 firwamre, DO NOT USE EX kernel, or you will have reboots.
If you want to use EX kernel, flash 1.32 firwmare.
Click to expand...
Click to collapse
kash20 said:
Had this same issue, you just have to revert back to whatever firmware you were previously on,
No need to clean flash ROM again, just flash the previous firmware the same way you updated it
Click to expand...
Click to collapse
Ok guys so up to now I've isolated the problem. Seems to be when I try to upgrade to 1.40 that the reboots start. I successfully fully wiped to 1.32.401.8 and the reboots stopped. Then I flashed the 1.40.401.8 nowipe firmware I got from https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml and the reboots started all over again. I must be missing something regarding the compatibility of the firmwares or which version to follow which. My phone is the unlocked version and the CID is 111111. Which nowipe zip should I flash having 1.32.401.8?
rpimentel1 said:
Ok guys so up to now I've isolated the problem. Seems to be when I try to upgrade to 1.40 that the reboots start. I successfully fully wiped to 1.32.401.8 and the reboots stopped. Then I flashed the 1.40.401.8 nowipe firmware I got from https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml and the reboots started all over again. I must be missing something regarding the compatibility of the firmwares or which version to follow which. My phone is the unlocked version and the CID is 111111. Which nowipe zip should I flash having 1.32.401.8?
Click to expand...
Click to collapse
Is your device Europe based 1.32.401.8? I think your official OTA is available (see link)
https://mobile.twitter.com/LlabTooFeR/status/608567895921160192?s=09
I'd say Flash the RUU (with red text) for previous firmware (if s off) reflash stock recovery and then let the device grab the official update to 1.40.401.8 and then reflash twrp and try flashing a ROM. I'm not 100% positive on these steps, maybe @LlabTooFeR can clear this up if he has a chance. Other than that stay with what works for now until someone else provides a definite solution.
Also check out this thread
http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
BUBBA DUB'S said:
Is your device Europe based 1.32.401.8? I think your official OTA is available (see link)
https://mobile.twitter.com/LlabTooFeR/status/608567895921160192?s=09
I'd say Flash the RUU (with red text) for previous firmware (if s off) reflash stock recovery and then let the device grab the official update to 1.40.401.8 and then reflash twrp and try flashing a ROM. I'm not 100% positive on these steps, maybe @LlabTooFeR can clear this up if he has a chance. Other than that stay with what works for now until someone else provides a definite solution.
Also check out this thread
http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
Click to expand...
Click to collapse
What I've done up to now is go back to stock on 1.32.401.8 and then flashed the 1.40.401.8, flashed in TWRP and installing right now VIPER2.30 I just noticed I've been checking TMOBILE as a carrier which automatically gets you back to the old kernel (Which seems like the most plausible explanation on why I've been getting the reboots) as of now the phone is first booting and I'll keep everybody updated. Thanks for the help man.
rpimentel1 said:
What I've done up to now is go back to stock on 1.32.401.8 and then flashed the 1.40.401.8, flashed in TWRP and installing right now VIPER2.30 I just noticed I've been checking TMOBILE as a carrier which automatically gets you back to the old kernel (Which seems like the most plausible explanation on why I've been getting the reboots) as of now the phone is first booting and I'll keep everybody updated. Thanks for the help man.
Click to expand...
Click to collapse
No problemo, I enjoy reading into all the various options (carrier/software) to see how they differentiate from one another on the same hardware of the m9. Also a shout out to @augie7107 @kash20 @iElvis @ivicask for their expertise and making it easier to pin point the issue at hand with hopes of resolving this issue. God speed Mr rpimentel1! :good:
BUBBA DUB'S said:
No problemo, I enjoy reading into all the various options (carrier/software) to see how they differentiate from one another on the same hardware of the m9. Also a shout out to @augie7107 @kash20 @iElvis @ivicask for their expertise and making it easier to pin point the issue at hand with hopes of resolving this issue. God speed Mr rpimentel1! :good:
Click to expand...
Click to collapse
just one quick question, my phone says 0PJA11000 in the MID instead of 0PJA10000. Which version is it???
rpimentel1 said:
just one quick question, my phone says 0PJA11000 in the MID instead of 0PJA10000. Which version is it???
Click to expand...
Click to collapse
Check out this link it might help , also in the first link I posted I think I saw someone reference what you are asking but I'm not 100% sure.
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
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
Greetings- I have an M8 running CM12 (nightly)
main 4.20.666.1
hboot 3.19.0.0.0000
S-On
CM12 nightly
twrp2.6
SuperSU
I'm hoping to restore to upgrade but the *$$*%*$ S-On issue won't allow me to. My original recovery is corrupt/gone and I just wonder if anyone has any (good) ideas?
Tried Firewater and got the PIE error.
You guys are doing a great job here- I've learned alot lurking and hope to continue...
cheerss
Superflous said:
I'm hoping to restore to upgrade but the *$$*%*$ S-On issue won't allow me to.
Click to expand...
Click to collapse
What exactly are you trying to do, that you think s-on is preventing? Unless I'm missing something, I don't think there is anything you are trying to do, that would be impeded by s-on.
Superflous said:
My original recovery is corrupt/gone and I just wonder if anyone has any (good) ideas?
Click to expand...
Click to collapse
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Superflous said:
Tried Firewater and got the PIE error.
Click to expand...
Click to collapse
Firewater was discontinued by the developer 6 months ago (online service, so no longer works).
Sunshine is the only current s-off method, if you really need s-off (not clear that you do).
redpoint73 said:
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Click to expand...
Click to collapse
Already moved my stock recovery collection to here : http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
All in one place and easier to find I guess.
ckpv5 said:
Already moved my stock recovery collection to here : http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
All in one place and easier to find I guess.
Click to expand...
Click to collapse
Certainly great to have it in one place, and thanks for doing so!
redpoint73 said:
What exactly are you trying to do, that you think s-on is preventing? Unless I'm missing something, I don't think there is anything you are trying to do, that would be impeded by s-on.
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Firewater was discontinued by the developer 6 months ago (online service, so no longer works).
Sunshine is the only current s-off method, if you really need s-off (not clear that you do).
Click to expand...
Click to collapse
tx for recovery link, sorry if it wasn't explained right but i want to restore my phone back to Bell firmware and lollipop . I spoke with the Root ninja via email ans Sunshine won't work on my phone(their words). I have tried to install the "firmware_M8SD_4.20.666.1_Modified_Bell_Canada.zip" but it fails and locks me up in the blue CM head until I reset, then reverts back to CM12. I'm just getting into this but if I understand correct you need S-off to flash firmware. If this isn't right I would sure appreciate the path to the correct way to put my phone back to original. Tx for you help
Superflous said:
I have tried to install the "firmware_M8SD_4.20.666.1_Modified_Bell_Canada.zip" but it fails and locks me up in the blue CM head until I reset, then reverts back to CM12. I'm just getting into this but if I understand correct you need S-off to flash firmware.
Click to expand...
Click to collapse
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.
redpoint73 said:
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.
Click to expand...
Click to collapse
'
so then I'm looking for a stock ROM from the carrier for firmware 4.20.666.1
tx again Redpoint
redpoint73 said:
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.
Click to expand...
Click to collapse
As a followup- tx for taking the time to explain- I have set the phone back to stock and happy to have learned some.
You are one of the good ones'
Cheers
Superflous said:
As a followup- tx for taking the time to explain- I have set the phone back to stock and happy to have learned some.
You are one of the good ones'
Cheers
Click to expand...
Click to collapse
You're very welcome. Glad to see it worked out well for you.
Please click the "Thanks" button for any posts you found helpful.
The latest HTC updates arrived this morning (Connect, Dot View, Lock Screen, Mail, MirrorLink), and my phone prompted me to restart to update the lock screen. I did, and now my wifi won't turn on.
I've tried restarting and turning on/off airplane mode, to no avail.
(Stock HTC One M8 running Android 6.0, Sense 7.0, software 6.12.111.4)
Any ideas, and/or is anyone else having this problem?
Edit: I tried Bluetooth in the meantime, and it's turning on but won't find devices/connect to existing ones, so it looks like that's shot too.
do you have telephone network working?
leecavturbo said:
do you have telephone network working?
Click to expand...
Click to collapse
Yeah, mobile data/calls work fine.
I was on to HTC Support earlier on and they suggested doing a hard reset, which I just did, and no luck.
It did say "Failed to load driver", so I'm wondering if I just got a bad driver in the update... Is there a way to check/fix it?
Kanhir said:
It did say "Failed to load driver", so I'm wondering if I just got a bad driver in the update... Is there a way to check/fix it?
Click to expand...
Click to collapse
If there is an RUU for 6.12.111.4, that is probably your best bet at this point.
redpoint73 said:
If there is an RUU for 6.12.111.4, that is probably your best bet at this point.
Click to expand...
Click to collapse
This is the bit where I admit my ignorance of what an RUU is.
I followed the instructions here to load a nandroid backup of 6.12.111.4, and it didn't fix the issue. Is this different to an RUU?
Edit: I did some internet hunting and found that RUUs for my SKU only go up as far as 4.19.111.2. Is it possible to use that RUU to install an older firmware, then search for OTAs on the phone and re-upgrade that way?
Kanhir said:
I followed the instructions here to load a nandroid backup of 6.12.111.4, and it didn't fix the issue. Is this different to an RUU?
Click to expand...
Click to collapse
A stock nandroid is just the system and boot partitions, where an RUU is a full re-write of all partitions. That's the main difference.
But restoring the stock nandroid was not a bad idea, to at least try. Of course, since it didn't fix the issue we'll have to keep looking for a fix.
Kanhir said:
Edit: I did some internet hunting and found that RUUs for my SKU only go up as far as 4.19.111.2. Is it possible to use that RUU to install an older firmware, then search for OTAs on the phone and re-upgrade that way?
Click to expand...
Click to collapse
You can't "downgrade" by RUU (run an older RUU) unless you have s-off.
Now, if you restored a 6.12.111.4 nandroid didn't fix the issue, and no corresponding RUU is available (did you do an XDA search, not just around the web via Google? - sometimes folks post the RUUs direct to this forum) that leaves us in a tough spot; and you may well have to resort to s-off ($25 by sunshine app).
Have you found a fix yet?
Im having the exact same issue, i've searched everywhere and cannot find a fix have you found one yet?
also having this issue, can't find a suitable RUU for S-ON.
wouldn't it be possible to do a 4.something stock nandroid restore and then use a RUU?
dx125 said:
also having this issue, can't find a suitable RUU for S-ON.
wouldn't it be possible to do a 4.something stock nandroid restore and then use a RUU?
Click to expand...
Click to collapse
I'm not clear what you are suggesting: RUU for your version, but older version 4.xx; or another versions (CID) RUU.
Either way, you can't do those with s-on.
redpoint73 said:
I'm not clear what you are suggesting: RUU for your version, but older version 4.xx; or another versions (CID) RUU.
Either way, you can't do those with s-on.
Click to expand...
Click to collapse
i was referencing the downgrading issue. if there is a RUU available for 4.9.111.2, you could do a stock restore to that version before.
doesn't help me though, can't find any suitable RUU for my CID.
dx125 said:
i was referencing the downgrading issue. if there is a RUU available for 4.9.111.2, you could do a stock restore to that version before.
doesn't help me though, can't find any suitable RUU for my CID.
Click to expand...
Click to collapse
As I already stated, you can't do it with s-on, even if there was a Lollipop RUU for your version.
You can't run a previous version RUU (downgrade) unless you have s-off.
ok i solved it for my case. the problem i had was an outdated firmware, as mentioned here: http://forum.xda-developers.com/htc-one-m8/help/wi-fi-wont-flashing-custom-rom-t3349613
so basically what i did was flashing the latest firmware i could find (4.19) an then installing a custom rom. i guess after flashing the firmware one could also just restore a nandroid backup
dx125 said:
ok i solved it for my case. the problem i had was an outdated firmware, as mentioned here: http://forum.xda-developers.com/htc-one-m8/help/wi-fi-wont-flashing-custom-rom-t3349613
so basically what i did was flashing the latest firmware i could find (4.19) an then installing a custom rom. i guess after flashing the firmware one could also just restore a nandroid backup
Click to expand...
Click to collapse
So you didn't have the same issue as the OP of this thread. Theirs was a completely different issue: official OTA caused WiFi broken vs. your case of a custom ROM with outdated firmware.
Its much easier to help folks when they describe the problem properly instead of saying "I have the same problem". Which from my experience its almost never the case where its exactly the same problem (and better to give specific details).
Next time, please provide more details in order for us to help you properly.
redpoint73 said:
So you didn't have the same issue as the OP of this thread. Theirs was a completely different issue: official OTA caused WiFi broken vs. your case of a custom ROM with outdated firmware.
Its much easier to help folks when they describe the problem properly instead of saying "I have the same problem". Which from my experience its almost never the case where its exactly the same problem (and better to give specific details).
Next time, please provide more details in order for us to help you properly.
Click to expand...
Click to collapse
i've had the issue after restoring a nandroid stock backup, which was also tried by others in this thread. but yes, maybe my problem was different.
Hi just bought a 32gb international version HTC One M8 that was converted into GPe. Then I reverted back using RUU and this firmware (1.54.401.5-W_Splash). Now that I've flashed a S-rom. Wifi isn't working. I asked the guy what was the original CID No. but he forgotten. So the question here is how do I find the right firmware?
pyrohalo90 said:
Hi just bought a 32gb international version HTC One M8 that was converted into GPe. Then I reverted back using RUU and this firmware (1.54.401.5-W_Splash). Now that I've flashed a S-rom. Wifi isn't working. I asked the guy what was the original CID No. but he forgotten. So the question here is how do I find the right firmware?
Click to expand...
Click to collapse
If "401" RUU worked before (Euro version), than another 401 (x.xx.401) RUU is what you want.
Try this RUU (6.12.401): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
redpoint73 said:
If "401" RUU worked before (Euro version), than another 401 (x.xx.401) RUU is what you want.
Try this RUU (6.12.401): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
I just solved my issue by finding out that my M8 is Dev Edition. So I flashed the latest firmware fw_6.12.1540.4 for the BS_US002, 0P6B12000. Wifi works like a charm now. Anyways thnks for your reply!