Hello,
After some troubles I've converted my S-OFF x.xx.410.xx phone to a dev edition 2 weeks ago by reading a lot on this forum. I believe I did the following:
- flash 0PJAIMG nougat.zip from bootloader mode / SD
- run 4.14.617.6 RUU after flash
This worked for perfectly for a time.
On 1-1-2017 I got the 4.19.617.1 OTA notification which I accepted as I did not modify the system in any way. OTA completed succesfully however after OTA the phone lost mobile reception. In Android IMEI was not visible. In fastboot I saw IMEI with "fastboot getvar all".
Re-flashing RUU 4.14.617.6 worked to regain mobile reception however OTA nofication would of course still appear. Today I retried but with the same results -- no mobile reception after OTA.
To confirm with the new RUU available I ran the 4.19.617.1 RUU to re-flash phone and indeed no signal at all.
Then I ran the 4.14.617.6 RUU and signal again.
I read this in the FAQ:
"Q1: Everytime I flash a custom rom I lose my IMEI, my mobile reception and my phone stops recognizing my sim card. What's the reason for this?
A: You probably flashed a custom rom that is based on firmware 3.35.x although the firmware of your phone is 3.y (with y being any other number than 35). The boot image of 3.35.x based roms is not compatible with your firmware version. The solution of the problem depends on the question whether you are trying to install a Sense-based rom (like ICE or ViperOneM9) or a non-Sense-based rom (like CM): For Sense-based roms you just need to re-flash the stock boot image of your current firmware version."
This seems like my problem except I run RUU directly from HTC. Any idea on what I can do to accept OTA / reflash phone with 4.19.617.1 RUU ?
Thank you!
Was the phone rooted at the time of accepting the ota?.
There is a thread somewhere that explains how to fix the no signal issue on nougat dev edition.
I don't see the point in risking a brick for a beta firmware (dev edition is the beta to carrier versions) which is not necessarily a better firmware.
Also, make sure the rom and firmware you flash IS GSM and NOT CDMA.
Beamed in by telepathy.
@Fritti: The error that is described in the FAQ only appears if you flash a custom rom while using an incompatible firmware. You've used a RUU and are using the stock rom that got flashed by the RUU. That means firmware and rom are matching. Unfortunately, that means that I have no clue why you're facing this issue. There's no reason why you should lose your reception since all GSM versions are more or less the same if you compare their hardware. As far as I know only the LTE bands of the GSM versions differ.
shivadow said:
Was the phone rooted at the time of accepting the ota?.
There is a thread somewhere that explains how to fix the no signal issue on nougat dev edition.
I don't see the point in risking a brick for a beta firmware (dev edition is the beta to carrier versions) which is not necessarily a better firmware.
Also, make sure the rom and firmware you flash IS GSM and NOT CDMA.
Beamed in by telepathy.
Click to expand...
Click to collapse
If the phone was rooted the OTA wouldn't have been installable.
And please stop posting things that aren't true. The dev firmware is not a beta version. It's the US equivalent of the European 401 firmware or the Asian 708, 709 or 710 firmware. Beta firmwares look like this one: 2.10.401.180. They have three numbers behind the last dot. If you compare the 3.x firmware of SKU 401 and 617 you'll notice that 3.35.401.12 and 3.35.617.12 are almost exactly the same except for some contintent-specific tweaks.
It is true that the dev edition is not necessarily better than the 401 one. However, it's up to every single user to choose whether he or she wants to wait until the latest update gets released for his/her SKU or whether they want to convert to the dev edition which receives all updates first (in case of the M9).
Flippy498 said:
@Fritti: The error that is described in the FAQ only appears if you flash a custom rom while using an incompatible firmware. You're used a RUU and are using the stock rom that got flashed by the RUU. That means firmware and rom are matching.
Click to expand...
Click to collapse
Yes, that's what I thought.
Unfortunately, that means that I have no clue why you're facing this issue. There's no reason why you should lose your reception since all GSM versions are more or less the same if you compare their hardware. As far as I know only the LTE bands of the GSM versions differ.
Click to expand...
Click to collapse
Exactly. I don't understand either. Something get's flashed by the 4.19 RUU that messes up the IMEI detection? Is it possible to extract system.img from 4.19 RUU and just flash that to check whether that works?
If the phone was rooted the OTA wouldn't have been installable.
Click to expand...
Click to collapse
Indeed, phone was not rooted. I used 4.14 RUU and then no other flashes/mods.
And to be clear, for now it seems that I can repeat this -- run 4.19 RUU and no signal, run 4.14 RUU and signal again. If there is some radio partition and/or radio data partition that I can dump to check hex diffs I could try.
Fritti said:
Yes, that's what I thought.
Exactly. I don't understand either. Something get's flashed by the 4.19 RUU that messes up the IMEI detection? Is it possible to extract system.img from 4.19 RUU and just flash that to check whether that works?
Indeed, phone was not rooted. I used 4.14 RUU and then no other flashes/mods.
And to be clear, for now it seems that I can repeat this -- run 4.19 RUU and no signal, run 4.14 RUU and signal again. If there is some radio partition and/or radio data partition that I can dump to check hex diffs I could try.
Click to expand...
Click to collapse
You could use the decryption tool that is linked in the readme thread for extracting the system image and the firmware files.
Hi,
I'm facing the same issue - I think. I'm currently using a 4.14 original RUU ROM from HTC without modification.
When I accept the 4.19 OTA I lose connectivity in a most peculiar way: there are still signal bars and the phone confirms a LTE connection.
But there are no more APN options and no data. Also when I place a call the phone claims I'm out of service area.
One other thing I noticed is that the dialer shows a different number format when entering a phone number. With 4.14 I have the normal DUtch standard for dashes and area codes. With 4.19 I have a US standard. Could it be that the phone thinks I'm in the US and would a edit to the build.prop help?
I hope someone has some advice.
Gawain1986 said:
Hi,
I'm facing the same issue - I think. I'm currently using a 4.14 original RUU ROM from HTC without modification.
When I accept the 4.19 OTA I lose connectivity in a most peculiar way: there are still signal bars and the phone confirms a LTE connection.
But there are no more APN options and no data. Also when I place a call the phone claims I'm out of service area.
One other thing I noticed is that the dialer shows a different number format when entering a phone number. With 4.14 I have the normal DUtch standard for dashes and area codes. With 4.19 I have a US standard. Could it be that the phone thinks I'm in the US and would a edit to the build.prop help?
I hope someone has some advice.
Click to expand...
Click to collapse
Yes, that sounds like the same issue. You can actually edit the settings in the phone to disable the US international prefix. However it does not help for the out of service issue.
I have not yet had the time to try and flash only the firmware / recovery / system from 4.19, I will report back once I have tried.
Fritti said:
Yes, that sounds like the same issue. You can actually edit the settings in the phone to disable the US international prefix. However it does not help for the out of service issue.
I have not yet had the time to try and flash only the firmware / recovery / system from 4.19, I will report back once I have tried.
Click to expand...
Click to collapse
I have some news. I took the 4.19 No-Wipe firmware and flashed it by putting it on my SD card as 0PJAIMG.zip. It flashed and now I'm working on the 4.14 ROM with 4.19 firmware. All is working wel, most notibly making calls and using data.
This leads me to believe there is something in the Kernel/ROM of 4.19 that breaks our calling and data.
Does anybody have any other ideas to make 4.19 work?
The plot thickens .
I installed ICE ROM 4.19 after flashing firmware 4.19 and I had the same problem back, out of service area.
So I started comparing the build.prop files in the 4.14 ROM from HTC and the 4.19 ICE ROM. Then I changes a few lines to these values and I was able to call:
ro.ril.hsxpa=4
ro.ril.hsdpa.category=14
ro.ril.hsupa.category=6
ro.aa.rid=115
To get data (and be able to log in to a google account) I did another thing. I used the dialer to call *#*#4636#*#* and set the phone to WCDMA preferred and I had data.
The only thing left is to be able to use LTE/4G but that's for another time, I can finally use my phone on this firmware!
Gawain1986 said:
The plot thickens .
I used the dialer to call *#*#4636#*#* and set the phone to WCDMA preferred and I had data.
The only thing left is to be able to use LTE/4G but that's for another time, I can finally use my phone on this firmware!
Click to expand...
Click to collapse
Now try switching it back to LTE/WCDMA/GSM.
I had the same with S.Rom and after getting it to connect the way you did, switching back to auto gave me 4G again
bonesy said:
Now try switching it back to LTE/WCDMA/GSM.
I had the same with S.Rom and after getting it to connect the way you did, switching back to auto gave me 4G again
Click to expand...
Click to collapse
No such luck for me... As soon as my phone sees LTE, the phone force closes and aftter I have no Data and I'm out of service area again.
So I know this is nearly a necro but I wanted to give an update that I cannot try this anymore -- shortly after the failures started my phone got stuck in a bootloop. This had to be hardware error as it simply started one morning while I did not change anything. The Vodafone shop I brought it to agreed and send my unit in for (warranty!) repairs. I've since got it back with Android 7.0 on version 4.28.401.3, so there is no need for me to switch to dev edition now. I cannot say whether the signal issues were a symptom or a cause for my unit to fail.
Hoping that Gawain1986 has fixed his issues as well!
Related
For some reason, every time I try to install a sense based rom, it never boots.
I'm fairly new to flashing, and have flashed 4 or 5 aosp roms. Every time I install one of those, it always works correctly, no issues.
I have tried to flash several Sense based roms, such as ARHD 20.1, Insert Coin, and nv, and each time, it never works. I always do a factory wipe beforehand as well as a wipe in the aroma installer. It will go thru the process and install, and then prompt me to reboot, which it does. Once the screen comes back onm however, it just hangs on the white htc screen with the red development text. When i get back to the hboot, itll show nothing for os.
I thought the issue may be that i dont have the latest firmware, but even people that dont have the latest firmware still are able to boot into the rom. Also, I just tried the NV rom which is based off my firmware, and it still gives me the same trouble. Does anyone know what I'm doing wrong?
I'm running an ATT Htc One m8, rooted, unlocked, s-off with sunshine, twrp recovery
mattprice86 said:
I thought the issue may be that i dont have the latest firmware, but even people that dont have the latest firmware still are able to boot into the rom.
Click to expand...
Click to collapse
Give the ROMs about 10 minutes, and I bet they will boot. The extremely long boot time, and lack of boot animation (another symptom of this issue) makes a lot of folks believe the phone is stuck/frozen, when in fact its just taking a reeeeeally long time to boot.
If its true that the ROMs in fact never boot, it might just be an issue with your recovery. fastboot erase cache and either re-install recovery, update to the latest version, or try another recovery (Philz).
Even if the Sense ROMs boot, you might find some serious things are broken with your outdated firmware, such a broken WiFi. So I suggest either update your firmware or stick or ROMs based on your present firmware.
Ok thanks, i will try again. Ive read a bunch of threads about updating my firmware but couldnt find an answer to a question I have about it.
If I upgrade my firmware to the latest WWE 3.28.401.6, will it mess up my ATT settings like the bands? Also, will it erase my internal sd card?
mattprice86 said:
If I upgrade my firmware to the latest WWE 3.28.401.6, will it mess up my ATT settings like the bands? Also, will it erase my internal sd card?
Click to expand...
Click to collapse
Firmware includes the radio baseband, so it may cause issues with reception on AT&T. It seems at least a couple folks have been flashing the 3.28 firmware, but I haven't seen enough reports to give me a warm and cozy feeling. With S-off (which is required to flash the firmware, anyway) you can always revert. But still, basic reception is more important to me than a couple updated features. Personally, I'll probably wait until the 3.x firmware specific to AT&T starts rolling out.
It seems like the M8 is radio agnostic like the Nexus 5 based on my experience.
I am on Rogers and flashed the latest firmware and my LTE works no issues.
The latest firmware is supposed to be EU so technically those North American bands are not supported but it works no issue.
Leads me to believe that the radio does not matter like the N5 where the 820 and 821 radios were interchangeable.
HTC One M8
Thanks redpoint, you were right, I gave it some time and it did come on. You always seem to be the one answering my questions, I appreciate it.
As for the new fw, I was thinking that would happen too from what I've read, I just needed someone more experienced to confirm that. I think I'll wait as well.
Thanks again
Elisha said:
It seems like the M8 is radio agnostic like the Nexus 5 based on my experience.
I am on Rogers and flashed the latest firmware and my LTE works no issues.
The latest firmware is supposed to be EU so technically those North American bands are not supported but it works no issue.
Click to expand...
Click to collapse
On the 2.x firmware, some folks in North America (I can speak mostly of AT&T specifically, although there are a lot of network similarities with Rogers) had varying degrees of issues with the "international" firmware. For some, the reception was worse, and others had NO SIGNAL whatsoever. Probably depended on what bands AT&T was using in their specific market.
Can't say whether 3.x firmware is the same way. But in my experience (or at least, reading reports by others here), I would have to disagree this phone is in any way "radio agnostic", at least from a software perspective (as the hardware is common among at least GSM versions, and baseband software is the only difference - but that is a slightly different topic).
So what is the latest firmware I can flash that's been known to work? I've seen that viper one is based off the 2.xx fw so do you know of anyone who's flashed it with att variant without any problems?
mattprice86 said:
So what is the latest firmware I can flash that's been known to work? I've seen that viper one is based off the 2.xx fw so do you know of anyone who's flashed it with att variant without any problems?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
No probs.
redpoint73 said:
On the 2.x firmware, some folks in North America (I can speak mostly of AT&T specifically, although there are a lot of network similarities with Rogers) had varying degrees of issues with the "international" firmware. For some, the reception was worse, and others had NO SIGNAL whatsoever. Probably depended on what bands AT&T was using in their specific market.
Can't say whether 3.x firmware is the same way. But in my experience (or at least, reading reports by others here), I would have to disagree this phone is in any way "radio agnostic", at least from a software perspective (as the hardware is common among at least GSM versions, and baseband software is the only difference - but that is a slightly different topic).
Click to expand...
Click to collapse
For the record, I have an AT&T model and am using the 3.xxx.xxx.6 firmware with absolutely Zero issues as far as signal. I get the exact same reception I did stock, and Very, Very similar reception to what my old Optimus G did in the same locations.
This indicates that there must be either a difference in hardware revisions (related to how some M8's can be firewater'd, whereas others need Sunshine), Or, the int'l radio firmware may not support the bands that are used on some towers in some locations. I'm leaning toward the former. For the record, my M8 is a "whelp", and I had to pay for Sunshine.
OMGMatrix said:
For the record, I have an AT&T model and am using the 3.xxx.xxx.6 firmware with absolutely Zero issues as far as signal. I get the exact same reception I did stock, and Very, Very similar reception to what my old Optimus G did in the same locations.
This indicates that there must be either a difference in hardware revisions (related to how some M8's can be firewater'd, whereas others need Sunshine), Or, the int'l radio firmware may not support the bands that are used on some towers in some locations. I'm leaning toward the former.
Click to expand...
Click to collapse
My guess would be the former as well. Keep mind that AT&T uses five different bands for LTE depending on your market region. Also keep in mind that travelling to another location may result in losing LTE reception (when you otherwise would have LTE on a AT&T specific radio).
Although none of this explains why I've seen some folks get NO SIGNAL whatsoever on AT&T's network after flashing the international firmware (2.x version, haven't seen any complaint yet on 3.28). Even if no LTE, those folks still should have been able to get HSPA and/or GSM since those AT&T bands appear to be supported by EMEA specs. So it leads me to believe there is something else going on aside from just band compatibility. Such as the network not falling back properly to HSPA/GSM.
I certainly don't have an issue if folks want to experiment with the 3.28 firmware on the AT&T network (as long as you know what you are doing, and are aware of the possible issues). Its certainly tempting with the 3.x based custom ROMs coming out. I might even experiment myself if I free up some time. But that spare time is a bit of a premium for me right now; and I also can't really afford ATM to have the possibility of reception issues or no service.
I was able to successfully upgrade my firmware to the 2.xxx by using skull dreams' method. As soon as my rom loaded, however, WiFi and data weren't working. I read through the thread and found that clearing cache and dalvik would fix it, so that's what I did and it worked. (initially I tried to wipe both at the same time, but it gave me errors; further reading showed I needed to wipe cache first and then dalvik).
I would now like to upgrade to the 3.xxx fw so I can install arhd 20.3, but want to know, if I upgrade my fw and it messes up, can I just do the same renaming and putting it on ext SD card to downgrade back to the 2.xx fw?
mattprice86 said:
I was able to successfully upgrade my firmware to the 2.xxx by using skull dreams' method. As soon as my rom loaded, however, WiFi and data weren't working. I read through the thread and found that clearing cache and dalvik would fix it, so that's what I did and it worked. (initially I tried to wipe both at the same time, but it gave me errors; further reading showed I needed to wipe cache first and then dalvik).
I would now like to upgrade to the 3.xxx fw so I can install arhd 20.3, but want to know, if I upgrade my fw and it messes up, can I just do the same renaming and putting it on ext SD card to downgrade back to the 2.xx fw?
Click to expand...
Click to collapse
You could always restore the backup you should be making before you do any mods on your phone. That would be the safest way.
So if I upgrade my fw then restore a backup, I will lose my fw changes?
I make nandroid backups before I do any, so I have approximately 60gb of backups on an external HD, and I always keep 1 or 2 on my internal and external storage
Decided to go back to my S-oFF Sprint htc one m8 from over a year ago.
First thing I did was update my firmware only, no recovery no boot, firmware only. I upgraded firmware to 6.20.651.3 using this link: http://forum.xda-developers.com/showthread.php?t=2729173
I then updated my twrp from 2.8.50 to 3.0.2-0.
after I try any rom, even sprint roms, I can't get passed the hands free activation and prl update screen. It will reboot before the phone boots up. I have tried a few gpe roms and it wont get past the boot screen.
I tried loading up a nandroid i made over a year ago and its a lollipop rom that works, but still wants to go through handsfree activation. I am able to turn it off there, but want to get back to marshmallow and newer roms. I called sprint support and they said it shows as fully activated on their end.
What else should I try? Should i upgrade firmware, recovery and boot?
I hate bumping, but im out of options here. Any advice?
memekmek said:
I hate bumping, but im out of options here. Any advice?
Click to expand...
Click to collapse
I've gone through countless threads like these: http://forum.xda-developers.com/showthread.php?t=2716834
my situation seams to be unique, where my phone will actually reboot right after hands free activation, thus rendering it useless. I've been able to mount the system in twrp and delete the htc service apk, but on the marshmallow roms, i can't get LTE to work.
Im stumped. :crying:
So I've managed to read through threads and turn off hands free activation by:
1. Using wifi at initial setup (this helps get passed the initial hands free activation)
2. Mounting system in twrp, then deleting htcservice apk in twrp (this helps getting past the initial setup if its a problem)
3. freezing vdm client in titanium backup to avoid having the hands free activation keep popping up.
However, even though I made sure to upgrade my firmware in steps I am not sure if i properly have the latest firmware installed correctly. Is there a way to check? I have LTE on 5.0 roms, but cannot get LTE to work on 6.0 roms. Even 3g data toggles on and off on 6.0 roms.
Any help on the LTE and firmware issues would be very much appreciated!
memekmek said:
However, even though I made sure to upgrade my firmware in steps I am not sure if i properly have the latest firmware installed correctly. Is there a way to check? I have LTE on 5.0 roms, but cannot get LTE to work on 6.0 roms. Even 3g data toggles on and off on 6.0 roms.
Click to expand...
Click to collapse
On the bootloader screen, the OS number indicates the firmware version. Alternately, if you do fastboot getvar all, the firmware number is shown as "version-main". So you will want to see 6.20.651.3 there for Marshmallow firmware (6.20.654.3 for HK Edition).
Additionally, if the OS number is red on the bootloader screen, or a 2nd number is shown in parenthesis (usually in red) it means there is an issue with the firmware not properly installed (partially installed).
redpoint73 said:
On the bootloader screen, the OS number indicates the firmware version. Alternately, if you do fastboot getvar all, the firmware number is shown as "version-main". So you will want to see 6.20.651.3 there for Marshmallow firmware (6.20.654.3 for HK Edition).
Additionally, if the OS number is red on the bootloader screen, or a 2nd number is shown in parenthesis (usually in red) it means there is an issue with the firmware not properly installed (partially installed).
Click to expand...
Click to collapse
Then I appear to be stuck as to why data does not work on my 6.0 roms. I am a Sprint user, tested the stock rooted rom from OMJ's thread, tried insert coin rom, viper rom. None of the 6.0 roms have data working properly.
memekmek said:
Then I appear to be stuck as to why data does not work on my 6.0 roms. I am a Sprint user, tested the stock rooted rom from OMJ's thread, tried insert coin rom, viper rom. None of the 6.0 roms have data working properly.
Click to expand...
Click to collapse
Only thing I can think of, is do full RUU (will wipe the phone) instead of just the firmware, and see if that helps.
redpoint73 said:
Only thing I can think of, is do full RUU (will wipe the phone) instead of just the firmware, and see if that helps.
Click to expand...
Click to collapse
Does the bootloader need to be relocked? if not, can i rename the ruu as 0P6BIMG.zip and update through fastbook in the bootloader?
memekmek said:
Does the bootloader need to be relocked? if not, can i rename the ruu as 0P6BIMG.zip and update through fastbook in the bootloader?
Click to expand...
Click to collapse
Since you are s-off, you do not need to relock the bootloader to RUU.
Yes, you can use the SD card method (rename RUU to 0P6BIMG.zip, put on SD card, and reboot into bootloader).
redpoint73 said:
Since you are s-off, you do not need to relock the bootloader to RUU.
Yes, you can use the SD card method (rename RUU to 0P6BIMG.zip, put on SD card, and reboot into bootloader).
Click to expand...
Click to collapse
Welp, did the RUU last night. It changed nothing, and did nothing for me other than making it a pain to reinstall twrp and get my nandroid back up. booo
lte and data is still spotty on 6.0 roms. The only other possible reason i think this could be happening is because i tried to carrier unlock this phone a few months ago, but i downloaded sim card info app, and it all appears to be ok.
Hi,
After doing some reading on here I am a little unsure on the best way to back up my HTC One M9 (GSM) stock recovery/system. My software number is 3.50.710.1 (Android 6.0) and it came from Optus (Australia). I cannot seem to find an RUU file for this firmware anywhere online; only earlier versions are available. My understanding of this is that I need an RUU file for my specific firmware as a fail-safe in case I mess something up and need to return to stock?
My questions are:
1) Can I get my phone back to the current complete stock firmware and be able to receive future OTA updates without turning s-off and without copying anything from my phone before I flash TWRP and a custom ROM?
2) If not is there anyway that I can back up my phone it its current stock state that will allow me to go back to this state if I want to go back to my stock Optus firmware or to install OTA updates? (Including the stock radio/recovery)
3) Reading this post as well as others leads me to believe that I may stop my mobile radio working by flashing a custom ROM (especially as the linked post has the exact same firmware as me). How can I avoid this, or fix it if it happens to everyone?
I am ideally looking for a custom ROM which improves over the stock firmware. My priority is maximum battery life, with customisation and HTC 10 system UI/apps a secondary focus. Any recommendations would be great, as well as tweaks and kernels which help give the maximum battery life.
Cheers!
You can't backup your firmware (and that includes your radio). However if you read my google sheet you'll find instructions for backing up your current boot.img, your system and the stock recovery. If you do it correctly those files will suffice for recovering the ability of installing OTAs. No personal data will be backed up so maybe you want to share your backup with us afterwards.
There is a custom kernel for CM/AOSP roms which is said to repair the signal problems. As far as I read some sense rom users reported that flashing the stock boot.img recovered their signal. However this doesn't seem to work for every user. So you'll need to try by yourself.
Flippy498 said:
You can't backup your firmware (and that includes your radio). However if you read my google sheet you'll find instructions for backing up your current boot.img, your system and the stock recovery. If you do it correctly those files will suffice for recovering the ability of installing OTAs. No personal data will be backed up so maybe you want to share your backup with us afterwards.
Click to expand...
Click to collapse
Thank you so much! I have managed to find the guide you mentioned to backup the stock boot image, system image and recovery. By the looks of it the tab to the right is the guide to return my phone to its original state, which is good. I'm more than happy to share the backup once I do it.
Flippy498 said:
There is a custom kernel for CM/AOSP roms which is said to repair the signal problems. As far as I read some sense rom users reported that flashing the stock boot.img recovered their signal. However this doesn't seem to work for every user. So you'll need to try by yourself.
Click to expand...
Click to collapse
Okay, well I am planning on keeping s-on at this stage, so I'm left with Sense based ROMs I believe? I have read that LeeDroid is the best for battery life, does this sound right? If so I am unsure if I can flash it as it says "Please make sure you have the latest HTC Hima 3.35.XXX.XX Marshmallow firmware installed prior to installing this ROM" because my software number is 3.50.710.1?
Thanks again!
Da Doom Lord said:
Okay, well I am planning on keeping s-on at this stage, so I'm left with Sense based ROMs I believe? I have read that LeeDroid is the best for battery life, does this sound right? If so I am unsure if I can flash it as it says "Please make sure you have the latest HTC Hima 3.35.XXX.XX Marshmallow firmware installed prior to installing this ROM" because my software number is 3.50.710.1?
Click to expand...
Click to collapse
I've read that several times in the near past and I actually don't understand it. You never needed S-OFF for flashing none-sense based roms as long as I started using Android/HTC phones and that was back in 2012. Why do so many people think they need S-OFF for AOSP?
I personally prefer the Viper rom. But taste differs and in the end the best advice I can give is try it out by yourself. Everyone has different needs and is using his/her phone in a different way. The best rom for person a might be an awful choice for person b since he/she has completely different needs.
I can't tell you whether you can use Leedroid. Test it and report back. That's how xda works. You might be able to use it after you flashed your stock boot.img but I don't know whether you really are or not. The warning is written so that people don't start flashing that rom with a lower firmware version. On older HTC phones flashing an "older" rom has never been an issue on newer firmware versions whereas flashing a newer rom on an older firmware never goes well (even on the M9). However many things have changed since the M9. There is no hboot anymore, the Download Mode got introduced, google changed the way OTAs are checking whether your system is modified, and so on. (Just to mention a few changes.) Those issues with the lost signal didn't even exist on pre-3.x firmware versions of the M9. Therefore users like you who use a not so common firmware (in comparison to the user numbers of the most common firmware bases: international, taiwanese and the developer firmware) have no other choice but trying out by themselves or getting S-OFF and changing to a more common firmware.
Flippy498 said:
I can't tell you whether you can use Leedroid. Test it and report back. That's how xda works. You might be able to use it after you flashed your stock boot.img but I don't know whether you really are or not. The warning is written so that people don't start flashing that rom with a lower firmware version. On older HTC phones flashing an "older" rom has never been an issue on newer firmware versions whereas flashing a newer rom on an older firmware never goes well (even on the M9).
Click to expand...
Click to collapse
I have followed your guide and now have the latest stable LeeDroid ROM installed and TWRP. Just as I predicted the radio was not originally working. When I restored my stock boot.img from the original backup I performed it began to work. Thanks so much for your help! I'll upload the backup to cloud storage when I get access to a decent internet connection and then I'll share it to help others out.
I didn't root HTC's android 7.0 but unlocked it from htcdev's site, was able to push on TWRP 3.0.2.0 and can boot into it, backed up HTC's ROM and tried flashing on several ROMs but in each case the cellular radio is inactive (can't even do a #*#*4636*#*# -- dialer numbers are grey) even after letting the phone sit for an hour, rebooting a few times.
I restore HTC's ROM and the cell radio is all good. If I wipe DATA and setup the M9 from scratch, the cell radio is still good.
Any ideas?
If the roms aren't based on nougat you'll have problems. The rom MUST match the firmware.
Beamed in by telepathy.
shivadow said:
If the roms aren't based on nougat you'll have problems. The rom MUST match the firmware.
Click to expand...
Click to collapse
They all were/are based on nougat.
I tried to install leedroid oreo and after installing it went to the HTC logo then a black screen then the htc logo again on a loop . so i decided to install another 8.0 ROM i use (Purefusion os) and now my sim card is not being detected (ive tried it in another phone and it works) ive tried resetting and tried many different roms and also ive tired to restore to original os using the RUU exe tool but i keep getting the error 132 .. can somebody PLEASE help ?
BoganRabbit said:
I tried to install leedroid oreo and after installing it went to the HTC logo then a black screen then the htc logo again on a loop . so i decided to install another 8.0 ROM i use (Purefusion os) and now my sim card is not being detected (ive tried it in another phone and it works) ive tried resetting and tried many different roms and also ive tired to restore to original os using the RUU exe tool but i keep getting the error 132 .. can somebody PLEASE help ?
Click to expand...
Click to collapse
Same Problem My HTC 10 (US Unlocked) seems to be no longer recognizing the cellular radio I was switching between ROMs and I received an error when Android booted saying that decryption was unsuccessful and I had to factory reset the device. After performing the factory reset I was unable to connect to the mobile network, when I looked into the settings the IMEI was listed as Unknown. I have advance wiped data in TWRP by formatting everything on the phone and trying to reinstall Viper 10 (with encryption disabled) Restored the matching firmware and reinstalled Viper 10 with encryption disabled and even flashed the most recent stock RUU. I have never tried switching between US and EU firmware, From other treads I've noticed people had problems with their HTC 10's service by trying to switch from Sprint to Unlocked US.
Three things
1. LeDroids 8.0 requires 8.0 firmware
2. Purefusion os not sure why but I have signal
3. You maybe able to flash the ruu for your phone to recover.
As above... HTC Oreo firmware is required to run a HTC based Oreo ROM.
As noted in my opinion, once you upgrade to Oreo you cannot go back to N, you will loose cell service.
So next steps... Flash Oreo firmware.. flash Oreo ROM & profit.
You may need to do a full /data format prior to flashing.
You may also have to go into the *#*#4636#*#* menu and change the preferred network type there depending on your carrier, I have Verizon and I have to do that when I restart the phone.
lightweaponx said:
You may also have to go into the *#*#4636#*#* menu and change the preferred network type there depending on your carrier, I have Verizon and I have to do that when I restart the phone.
Click to expand...
Click to collapse
I would say that could possibly work but my phone doesn't even know what my IMEI number is won't read a SIM card
steezee said:
I would say that could possibly work but my phone doesn't even know what my IMEI number is won't read a SIM card
Click to expand...
Click to collapse
If you installed the Oreo Firmware you have to stay on an Oreo ROM right now. Make sure you have the latest TWRP, wipe everything, format data (not wipe) then reinstall Lee's ROM.
LeeDroid said:
As above... HTC Oreo firmware is required to run a HTC based Oreo ROM.
As noted in my opinion, once you upgrade to Oreo you cannot go back to N, you will loose cell service.
So next steps... Flash Oreo firmware.. flash Oreo ROM & profit.
You may need to do a full /data format prior to flashing.
Click to expand...
Click to collapse
Do you mean flashing the stock firmware RUU file ? ..because when i download the exe i use from HTC i recieve a 132 error
BoganRabbit said:
Do you mean flashing the stock firmware RUU file ? ..because when i download the exe i use from HTC i recieve a 132 error
Click to expand...
Click to collapse
I assume they are mentioning 3.xx.xxx.xx firmware but I can't find any 3. firmware that will flash (I'm looking for [617] US Unlocked)
lightweaponx said:
If you installed the Oreo Firmware you have to stay on an Oreo ROM right now. Make sure you have the latest TWRP, wipe everything, format data (not wipe) then reinstall Lee's ROM.
Click to expand...
Click to collapse
where can i download the oreo firmware ?
BoganRabbit said:
where can i download the oreo firmware ?
Click to expand...
Click to collapse
what model of the HTC 10 do you have?
I found The following
WWE Oreo 3.16.401.2 firmware
US Unlocked Oreo 3.16.617.2 firmware
steezee said:
I would say that could possibly work but my phone doesn't even know what my IMEI number is won't read a SIM card
Click to expand...
Click to collapse
sad thing is that that did't work for me on Tmobile with Pure Fusion Os 8.0 or any other non Sense based rom
Im having the same issue. Mistakenly updated with the latest Leedroid without flashing OREO first. It wasnt ovbious from the Leedroid.co.uk page. Now after reflashing several RUU my IMEI is showing as unknown. I have S-OFF now so hopefully there's some way of fixing my screw up.
acs111 said:
Im having the same issue. Mistakenly updated with the latest Leedroid without flashing OREO first. It wasnt ovbious from the Leedroid.co.uk page. Now after reflashing several RUU my IMEI is showing as unknown. I have S-OFF now so hopefully there's some way of fixing my screw up.
Click to expand...
Click to collapse
Flash the Oreo RUU for your CID/MID and you should get it back
or
Flash the Oreo firmware (That matches your CID/MID) that I linked for your phone above (might as well just use the wipe one which is what I used to get my phone back)
Flash TWRP (if you used the fullwipe without TWRP, if not skip to the next step)
Install an Oreo based Rom (You can't go back to N or before)
Thanks, that worked
How do you flash the oreo firmware? with fastboot or through twrp? I did the same thing, now I'm stuck trying to fix my phone. I tried download mode through fastboot and through twrp, neither worked for me.
acs111 said:
Thanks, that worked
Click to expand...
Click to collapse
What do you mean? Can you do phone calls?. Please tell us, what did you do? Step by step
Are you s-on or s-off? Please, be gentle with us.. Regards..
CarlosRDonXDA said:
What do you mean? Can you do phone calls?. Please tell us, what did you do? Step by step
Are you s-on or s-off? Please, be gentle with us.. Regards..
Click to expand...
Click to collapse
He did as the post before his suggested. (and many other posts here on XDA regarding Oreo update)
You have to install Oreo RUU or Oreo firmware + Oreo rom.
It's as simple as that.
Since I have no clue what variant/model of HTC 10 you have from what little you posted, I can't/won't direct you to a specific RUU or firmware.
But the info needed to determine that, has been posted many times.
santod040 said:
He did as the post before his suggested. (and many other posts here on XDA regarding Oreo update)
You have to install Oreo RUU or Oreo firmware + Oreo rom.
It's as simple as that.
Since I have no clue what variant/model of HTC 10 you have from what little you posted, I can't/won't direct you to a specific RUU or firmware.
But the info needed to determine that, has been posted many times.
Click to expand...
Click to collapse
Thanks santod040, the same happens to me with piranya ROM.
Hope your help... My device is htc 10, Cid htc__332 latín América, 2PS650000, pmewl. No sim detected, no imei, no base band. Need I to be s-off?. Thanks in advance...
Excuse me... I have been playing with ROMs trying solve my problem, actually have installed crdroid nougat 7.1.2, and time ago, my daughter erase original system twrp backup.
CarlosRDonXDA said:
Thanks santod040, the same happens to me with piranya ROM.
Hope your help... My device is htc 10, Cid htc__332 latín América, 2PS650000, pmewl. No sim detected, no imei, no base band. Need I to be s-off?. Thanks in advance...
Click to expand...
Click to collapse
You need Oreo firmware to run an Oreo rom.
Paste the output of the following command from Download mode:
fastboot getvar all
Remove your serial and IMEI from the output before posting.
Sent from my HTC6545LVW using Tapatalk