Related
can someone please tell me the steps tp a succesful rom flash. i cannot seem to get it right. and if it helps im trying to flash hibbys rom 1.6. i have the rom downloaded and have the romupdateutility software. what next???
did you unlock your phone yet?
http://forum.xda-developers.com/showthread.php?t=410150
after you unlock
download RUU (rom update utiliti)
download rom you want.
extract both.
put rom into RUU folder, and run RUU.exe utililty)
There are 3 roms that can be flashed
The first is the bootloader. This is whats called hardspl. You need to flash the hardspl first, then you can flash the other roms.
The other ROMS are the Operating System, and the Radio (phone software)
They both use the same ruu software, but you put in different files to flash different things.
First thing, flash the spl to unlock the phone! http://forum.ppcgeeks.com/showthread.php?t=42503
Can someone clarify this for me:
1) After I unlock the phone (with CDMA SPL), can I use any Touch Pro ROM, or do I need a Sprint/CDMA version of the ROMs?
2) Does changing ROM and/or SPL void sprint warranty? Will they be able to tell?
Thanks, I think these answers should be Sticky+Wiki because I cant find reliable info anywhere...
Thanks!
ethanpil said:
Can someone clarify this for me:
1) After I unlock the phone (with CDMA SPL), can I use any Touch Pro ROM, or do I need a Sprint/CDMA version of the ROMs?
2) Does changing ROM and/or SPL void sprint warranty? Will they be able to tell?
Thanks, I think these answers should be Sticky+Wiki because I cant find reliable info anywhere...
Thanks!
Click to expand...
Click to collapse
Yes CDMA and yes always flash back to stock if you have to take it in...at this time there is no signed version though...
Everything you need to do step by step:
http://forum.ppcgeeks.com/showthread.php?t=43266
Just don't forget to unlock before you begin....
Also be sure to NOT use a GSM ROM (Fuze). You need CDMA if your with sprint.
I am new to this ROM issue but what's the deal with changing the ROM?
mmotown said:
I am new to this ROM issue but what's the deal with changing the ROM?
Click to expand...
Click to collapse
There are a couple different reasons to change your ROM. When you get right down to it, its just personal preference.
1) To help speed the device up. This is done my tweaking the ROM and removing or adding programs to your taste. Personally, I don't flash my rom to increase speed, my sprint TP is actually very stable and fast out of the box. There was however lots of bloatware I would never use.
2) To totally customize your phone to the way you want it. You can do this without a ROM, but when its in the rom if you hard reset, the device is back to the same as when you first flashed. (you wouldn't have to fool with putting on or taking off all the programs and tweaks to suites your needs)
When I flash and find a rom I like, if I end up hard resetting my phone it take me less than 10 min to get me up and going good as gold. (I grab my contacts and e-mail strait from my exchange server)
I'm sure there are other reasons, if so someone can chime in.
Hope this helps.
flyers2114 said:
Yes CDMA and yes always flash back to stock if you have to take it in...at this time there is no signed version though...
Click to expand...
Click to collapse
How can I flash back to stock? I haven't modified my tp2 yet...teach me how to start from square zero!
jane
Hi!
I flashed my phone a month ago and have ever since then desperately trying to find help. No luck so far.
I installed 2.3.4 because it wasnt realesed here in sweden. but then the phone became russian and i couldnt use 3g anymore. i went to samfirmware.com and tryed out like every firmware but nothing worked, i tried updating via kies but most of the time it would say that my phone does not support updating via kies, but once it worked and it update back to the russian 2.3.4 firmware, i dont know what to do! please help me.
Are you using a small regional type cell carrier? A friend of mine had a issue much like this before where they rooted their phone and installed CM7 which changed the radio(baseband) and they lost MMS and some other features because the small carrier was not supported. The only way we could get it back was by taking a nandroid backup of same model device from the same carrier that hadn't been touched other than root and restore that onto their phone and that resolved the issue. Not sure if this helps you or not.
adammwhiles said:
Are you using a small regional type cell carrier? A friend of mine had a issue much like this before where they rooted their phone and installed CM7 which changed the radio(baseband) and they lost MMS and some other features because the small carrier was not supported. The only way we could get it back was by taking a nandroid backup of same model device from the same carrier that hadn't been touched other than root and restore that onto their phone and that resolved the issue. Not sure if this helps you or not.
Click to expand...
Click to collapse
Well it helped a luttle, but what do you mean with small carrier and such? i am not very good at english so i dont understand alot. is there a copy of a untouched ace???
What I mean by small carrier is that in the US we have Verizon, AT&T, T-Mobile etc. but we also have small carriers like Bluegrass where I live at. With these small carriers if your radio gets updated from a ROM install then it is very hard to find a replacement radio to flash back onto the phone. If this is the case in your scenario then you will need to find someone on the same carrier with the same model phone that has not installed a customer ROM but has rooted their device to make a nandroid backup then restore that to your phone.
adammwhiles said:
What I mean by small carrier is that in the US we have Verizon, AT&T, T-Mobile etc. but we also have small carriers like Bluegrass where I live at. With these small carriers if your radio gets updated from a ROM install then it is very hard to find a replacement radio to flash back onto the phone. If this is the case in your scenario then you will need to find someone on the same carrier with the same model phone that has not installed a customer ROM but has rooted their device to make a nandroid backup then restore that to your phone.
Click to expand...
Click to collapse
well..... **** -.-
Thanks dough!
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
seattleboi1982 said:
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
Click to expand...
Click to collapse
Yeah, just don't flash any odin files.
aooga said:
Yeah, just don't flash any odin files.
Click to expand...
Click to collapse
can you clarify please?
seattleboi1982 said:
can you clarify please?
Click to expand...
Click to collapse
Not sure what you mean. You can flash any rom from any variant of the S5 (obviously not the exynos variant, but there's hardly anything for it anyway). When I say rom, I mean a zip that's flashable in cwm or twrp. NOT the files that you flash in ODIN (tar, md5). DON'T flash those files from any other phone except the G900T.
seattleboi1982 said:
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
Click to expand...
Click to collapse
Well yes, but the way it works may not be quite the way you picture it. If you flash your phone to TMobile it isn't a 100% change over to TMobile as you probably assume it would be. Picture your phone as having two parts.. a baseband + ROM. The baseband is basically just the bootloader and modem. It's very hard to change the baseband and it's hardly ever done. So your baseband will more than likely remain ATT forever no matter what you do.
But that isn't likely to be a problem either. The baseband is compatible between ATT and TMobile and pretty much any other GSM system too. Otherwise you wouldn't be able to roam on other systems. You can change the ROM part to TMobile and your phone will act, smell and behave like a TMobile phone in pretty much every way that is likely to matter to you. The only obvious snag is that automatic OTA updates may or may not work, if that matters to you.
The customary way to change your phone to TMobile would be to root it, install a custom recovery e.g. TWRP. Then flash a TMobile ROM (or custom ROM if you want to) from TWRP. Note that installing a custom recovery like TWRP will change your Knox warranty bit. That might have warranty implications if your phone is still under warranty. Some carriers don't care about Knox - you can check the ATT forum to see how ATT handles warranty claims.
Alternately, if Knox matters to you, you may be able to flash a full stock TMobile image to your phone with the Odin program. This works for some carriers and not others. I don't know how ATT's locked bootloader would react to that. It's just a possibility that you could investigate if Knox and warranty are an issue to you. It would probably mean using a newer root method that doesn't trip Knox, then flashing a full TMobile firmware image, along with the correct TMobile PIT file. Hopefully Odin would just ignore the baseband and just write the ROM, while preserving the Knox bit. But you'd have to confirm that the ATT bootloader won't go bananas over the attempt i.e. search the forum to find out what happened when other people tried it.
.
fffft said:
Well yes, but the way it works may not be quite the way you picture it. If you flash your phone to TMobile it isn't a 100% change over to TMobile as you probably assume it would be. Picture your phone as having two parts.. a baseband + ROM. The baseband is basically just the bootloader and modem. It's very hard to change the baseband and it's hardly ever done. So your baseband will more than likely remain ATT forever no matter what you do.
But that isn't likely to be a problem either. The baseband is compatible between ATT and TMobile and pretty much any other GSM system too. Otherwise you wouldn't be able to roam on other systems. You can change the ROM part to TMobile and your phone will act, smell and behave like a TMobile phone in pretty much every way that is likely to matter to you. The only obvious snag is that automatic OTA updates may or may not work, if that matters to you.
The customary way to change your phone to TMobile would be to root it, install a custom recovery e.g. TWRP. Then flash a TMobile ROM (or custom ROM if you want to) from TWRP. Note that installing a custom recovery like TWRP will change your Knox warranty bit. That might have warranty implications if your phone is still under warranty. Some carriers don't care about Knox - you can check the ATT forum to see how ATT handles warranty claims.
Alternately, if Knox matters to you, you may be able to flash a full stock TMobile image to your phone with the Odin program. This works for some carriers and not others. I don't know how ATT's locked bootloader would react to that. It's just a possibility that you could investigate if Knox and warranty are an issue to you. It would probably mean using a newer root method that doesn't trip Knox, then flashing a full TMobile firmware image, along with the correct TMobile PIT file. Hopefully Odin would just ignore the baseband and just write the ROM, while preserving the Knox bit. But you'd have to confirm that the ATT bootloader won't go bananas over the attempt i.e. search the forum to find out what happened when other people tried it.
.
Click to expand...
Click to collapse
actually its T-mobile S5 flash to to make it like ATT S5. Samsung is a differant beast for me as i am usually a HTC or Moto user.
seattleboi1982 said:
actually its T-mobile S5 flash to to make it like ATT S5.
Click to expand...
Click to collapse
Your original post stated the opposite. Unintentionally I'm sure, but it goes to show that clarity counts.
It's much easier to go in that direction because the 900T uses an unlocked bootloader and TMB is generally less restrictive.
So yes, you can install an ATT (or other custom ROM) onto a 900T.
Keep in mind that it is not necessary to do so. The 900T will work fine on ATT with it's original firmware. But you can change the ROM to ATT if you want to for some reason. The proper way to do so is to find an ATT PIT file, then flash a full stock ATT firmware + PIT to your 900T. Most people don't bother with the PIT file and occasionally that leads to bootloops and soft bricking.
Anyway, go ahead and flash it if you want. Odin won't change the baseband, but everything else (ROM) will transition to ATT. FWIW, I think that a custom (debloated) ROM e.g. Phoenix ROM (which is not branded for ATT or TMB) is a nicer experience and better performance than using the ATT ROM. But up to you of course.
There is a XDA thread on S5 PIT files that has the 16 GB version of the ATT PIT if you need it.
.
fffft said:
Your original post stated the opposite. Unintentionally I'm sure, but it goes to show that clarity counts.
It's much easier to go in that direction because the 900T uses an unlocked bootloader and TMB is generally less restrictive.
So yes, you can install an ATT (or other custom ROM) onto a 900T.
Keep in mind that it is not necessary to do so. The 900T will work fine on ATT with it's original firmware. But you can change the ROM to ATT if you want to for some reason. The proper way to do so is to find an ATT PIT file, then flash a full stock ATT firmware + PIT to your 900T. Most people don't bother with the PIT file and occasionally that leads to bootloops and soft bricking.
Anyway, go ahead and flash it if you want. Odin won't change the baseband, but everything else (ROM) will transition to ATT. FWIW, I think that a custom (debloated) ROM e.g. Phoenix ROM (which is not branded for ATT or TMB) is a nicer experience and better performance than using the ATT ROM. But up to you of course.
There is a XDA thread on S5 PIT files that has the 16 GB version of the ATT PIT if you need it.
.
Click to expand...
Click to collapse
Odin will change the baseband. There's no need at all do do anything with ODIN. All it does is cause more problems if he does something wrong. I would just use TWRP and flash a stock ATT rom.
aooga said:
Odin will change the baseband. There's no need at all do do anything with ODIN. All it does is cause more problems if he does something wrong. I would just use TWRP and flash a stock ATT rom.
Click to expand...
Click to collapse
Installing a custom recovery like TWRP will trip Knox. That probably isn't an issue as TMobile doesn't care about Knox and virtually everyone says that it does not affect how TMobile handles warranty claims. But the OP should still know about Knox in advance in case it is an issue for him somehow.
I agree that a flashable zip is easier than Odin if the ROM that he wants exists in that form. Specifically, I don't know if anyone has repackaged an ATT ROM into a zip format. If someone has, then i agree with your approach. If not, he would have to use Odin.
IMO, the OP would do best to install something like the unbranded Phoenix ROM via TWRP.
Odin will not usually a foreign baseband to be flashed. Not that he necessarily has to try. You can use Odin to flash AP, CP, and CSC, but not the BL. Only when the constituent components are unavailable do you need to use the full OEM Odin image.
.
OP: Why do you need an ATT rom anyway? If you tell us what part you actually need, it might be easier than flashing an entire rom, either with odin or twrp.
fffft said:
Installing a custom recovery like TWRP will trip Knox. That probably isn't an issue as TMobile doesn't care about Knox and virtually everyone says that it does not affect how TMobile handles warranty claims. But the OP should still know about Knox in advance in case it is an issue for him somehow.
I agree that a flashable zip is easier than Odin if the ROM that he wants exists in that form. Specifically, I don't know if anyone has repackaged an ATT ROM into a zip format. If someone has, then i agree with your approach. If not, he would have to use Odin.
IMO, the OP would do best to install something like the unbranded Phoenix ROM via TWRP.
Odin will not usually a foreign baseband to be flashed. Not that he necessarily has to try. You can use Odin to flash AP, CP, and CSC, but not the BL. Only when the constituent components are unavailable do you need to use the full OEM Odin image.
.
Click to expand...
Click to collapse
How would someone deal with tmobile warranty without a tmobile account?
Is that possible at all?
Like via prepaid or something? Just wondering..
I would trip knox if I knew I had something to fall back on.
Lostatsea23 said:
How would someone deal with tmobile warranty without a tmobile account?
Is that possible at all?
Like via prepaid or something? Just wondering..
I would trip knox if I knew I had something to fall back on.
Click to expand...
Click to collapse
No, you need to be a tmobile customer with a postpaid account.
aooga said:
No, you need to be a tmobile customer with a postpaid account.
Click to expand...
Click to collapse
Well. Theres my options lol
aooga said:
No, you need to be a tmobile customer with a postpaid account.
Click to expand...
Click to collapse
Do you have a source or even solid rationale for that? I don't disagree that TMB, like pretty much any carrier treats current, postpaid customers better. But I have not seen any written policy or even credible assertions that TMB disavows their warranty for prepaid or ex-customers. AFAIK, if you bought the phone from TMB, postpaid or prepaid, you have a warranty through TMB. The obvious impediments being a stolen phone or account in serious arrears.
Discretionary powers exist, so it's sometimes difficult to distinguish between common practice or what they can be persuaded to do versus actual policy. Policy is a definite advantage in negotiations, so if there is anything written that says prepaid or ex-customers must deal with Samsung directly, I'd like to see that.
Everything in my direct experience is to the contrary. TMB honours warranty and doesn't care about Knox. They do have less respect for prepaid customers. But the few prepaid TMB customers that I know still had TMB handle their warranty claims.
.
fffft said:
Do you have a source or even solid rationale for that? I don't disagree that TMB, like pretty much any carrier treats current, postpaid customers better. But I have not seen any written policy or even credible assertions that TMB disavows their warranty for prepaid or ex-customers. AFAIK, if you bought the phone from TMB, postpaid or prepaid, you have a warranty through TMB. The obvious impediments being a stolen phone or account in serious arrears.
Discretionary powers exist, so it's sometimes difficult to distinguish between common practice or what they can be persuaded to do versus actual policy. Policy is a definite advantage in negotiations, so if there is anything written that says prepaid or ex-customers must deal with Samsung directly, I'd like to see that.
Everything in my direct experience is to the contrary. TMB honours warranty and doesn't care about Knox. They do have less respect for prepaid customers. But the few prepaid TMB customers that I know still had TMB handle their warranty claims.
.
Click to expand...
Click to collapse
Source would be experience. When you call, you cannot speak to a warranty rep unless you have a tmobile account. They ask for the phone number and last 4 of your ssn. Maybe you can convince them to make an exception, but when I tried with ATT, they told me since you're not a ATT customer, we can't help you.
aooga said:
Source would be experience. When you call, you cannot speak to a warranty rep unless you have a tmobile account.
Click to expand...
Click to collapse
All right. Your experience is completely contrary to mine. With no evidence of that being policy, I can only assume that you've encountered less helpful CSRs. Anyone finding themselves in a similar position may well prevail if they try talking to different CSRs.
.
fffft said:
All right. Your experience is completely contrary to mine. With no evidence of that being policy, I can only assume that you've encountered less helpful CSRs. Anyone finding themselves in a similar position may well prevail if they try talking to different CSRs.
.
Click to expand...
Click to collapse
Have you actually done an exchange with a carrier that you don't have service with? Just think about it...they don't have any of your info. CC, ssn, email, even your full name. If for some reason the customer doesn't ship the defective phone back, they can't charge you. If tmobile has a way of doing this for non-customers, I'll gladly shut up
aooga said:
...
Click to expand...
Click to collapse
I already expressed my opinion on this. If you disagree, so be it. And it's tangential and off topic in this thread.
Getting back on topic, the OP asked if he can flash an ATT "ROM" onto his TMB 900T phone.
Yes he can. We agreed that the easiest way to do so is to use TWRP, provided that he does not mind Knox being tripped. And of course, assuming that someone has repackaged an ATT ROM into a flashable zip format.
The alternative is a traditional Odin flash. He can flash ATT firmware onto his TMB 900T phone. It should be done in conjunction with the appropriate ATT PIT file. But those who are impatient or don't know about PIT files, usually don't run into problems eschewing the PIT. I won't advise that approach though.
Two last considerations. There isn't necessarily a good reason to do any of this in the first place. A TMobile S5 can roam on or use an ATT SIM directly. And without missing out on anything that the average user would notice. But it is possible to so for sundry reasons. As one way of changing the CSC and opt into an automatic OTA update scenario. To gain carrier specific ATT apps and so forth.
There is a lot of confusion regarding the mechanics of transitioning a phone from TMB to ATT for these sundry goals. A phone has a ROM, which is the apps and most of the system files. That can certainly be changed.
And then there is the low level baseband. The baseband can be updated with something newer from the same carrier that the phone originated from. But it is difficult and hard to find a good reason to change the baseband to a different carrier. To be more specific the baseband represents the bootloader and modem. A modem from one carrier works just fine on another carrier 99% of the time. So pragmatically, the best approach is to simply update the modem to a newer version from the original carrier, regardless of what carrier you actually use the phone on. There is rarely something carrier specific in a modem module.
If you enjoy fighting with Odin, you can flash some modems from foreign carriers. It will also sometimes brick your phone. And Odin often refuses to proceed with the flash for various reasons. So again, not recommended. Nor necessary in most cases.
The bootloader is exponentially harder to change to another carrier. Not to mention almost pointless except for cosmetic reasons and involves having Odin jump through a lot of hoops. Difficult enough to do that it isn't inaccurate to say it can't be done. It can't be done by most people. And it would be rare to hear a reason with merit for doing so.
.
.
seattleboi1982 said:
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
Click to expand...
Click to collapse
Why would you want to run an att rom, no wifi calling? lol, anyways, what rom are you trying to run?
i would like to run as close as possible to an AT&T ROM as im an ATT subsciber with a T-mobile phone. especially now with VoLTE.
Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
homthtrnut said:
Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
Click to expand...
Click to collapse
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Just need to dig in and get it done!
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I can do anything that is new to me with good instructions. I WAS able to unlock, root, and flash a ROM with good success following the steps. What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk. Before I started anything , I backed it up using HTC SYNC on my laptop. Is that useful in returning it to stock? Or is that just for media and texts and such? Maybe what I should do is check the forum where the Revo users are and see what they say. Sorry if it sounds like Im thinking out loud but Im a noob at forums and flashing. And Im getting burnt out on having a phone that doesnt receive calls properly. Not to mention burnt out from working all day and coming home to try and solve this mystery. OK I wont mention it. Thanks to those who have attempted to give me input here to try to figure this thing out.
Just a lil something to think about...,youll not have dialer, vvm messages,contacts integrated,signal will probably be not as good,and no VoLTE when using euro ROM's. Stand alone vvm app may or may not install from playstore if you use it. My suggestion,flash back to stock,wait alil while and get an official Lollipop release from ATT.
Flash a twrp backup of latest 4.4.4
Flash stock recovery from latest 4.4.4
Steps above will put you back to as close to stock as possible,without relocking bootloader and reflashing the exe ruu file.
homthtrnut said:
What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk.
Click to expand...
Click to collapse
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Flashed firmware successfully.........darn .zip.zip tricksters!!!! Anyway!
redpoint73 said:
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Click to expand...
Click to collapse
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done. Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do. I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious. Now to see if I can receive calls again. Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
homthtrnut said:
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done.
I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious.
Click to expand...
Click to collapse
Do yourself a huge favor, and turn off the Windows option (if you haven't already) to hide known file extensions. The option is usually enabled by default. I suspect its mainly meant to prevent non-tech savvy PC users from deleting or modifying file extensions and rendering files unusable (or at least not associated with a program to open it).
For most folks who are going to be messing with things like modding phones, and even halfway familiar with the file extensions, the option to hide them is counter-productive and confusing.
The recommendation to rename the file to firmware.zip is valid. This is done since the files are often named things like 4.16.401 to differentiate the firmwares from each other (such as in firmware collections). Technically, you didn't rename the file to firmware.zip (although Windows make it look like you did), you actually named it firmware.zip.zip, even though Windows didn't display it that way.
homthtrnut said:
Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do.
Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
Click to expand...
Click to collapse
To unlock the bootloader again, simply go through the HTCDev.com process to get another unlock bin token, then run the fastboot command with that token again (like you did the first time).
On past devices, it was sometimes possible to reuse the original token (run the fastboot command with it). But an XDA user commented that doesn't work on this device (and that you need to get a new token). But you can always try it, if you want.
Flashed firmware and now stuck in HBOOT! I REALLY NEED HELP NOW
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258 and after numerous attempts to flash I finally got it to go by getting rid of the renamed .zip at the end. ( It was already a zip file) I think a lot of people have had that problem. Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again. Can anyone point me? I'll buy you a beer! or 12
homthtrnut said:
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258
Click to expand...
Click to collapse
401 firmware is Euro based firmware. AT&T is 501.
homthtrnut said:
Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again.
Click to expand...
Click to collapse
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
hboot and radio numbers currently on m8
redpoint73 said:
401 firmware is Euro based firmware. AT&T is 501.
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
Click to expand...
Click to collapse
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
That is the Android 4.4.4 radio. Meaning the 401 firmware you linked and tried to flash didn't take. And it won't with s-on, unless its signed and hacked to accept AT&T's CID (which I don't think there is any 401 firmware that meets those requirements).
Agree with the above response, in that the easiest way to get the phone up and running again is relock the bootloader and RUU to stock.
Since your device is hboot 3.19, you are stuck with s-on and that means you are stuck on KitKat firmware until AT&T releases Lollipop officially.
That also means you can only run ROMs that support 4.4.4 firmware (no LP based Sense ROMs), otherwise you will run into various serious bugs like the call issue on ARHD (or broken WiFi). There are some LP GPE and AOSP ROMs that support the 4.4.4 firmware, if you want to go that route.
Was just starting out, not enough experience.
bford152 said:
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
Click to expand...
Click to collapse
The above phone was eventually returned. Now I have an unlocked, s off M8. With help from PearlyMon I was able to do it all about a month ago. Now I'm just waiting to work up the nerve to flash a customer Rom and also add in the H/K sound feature. Really liked the HD Revolution Rom, I just didn't have the wherewithall to find and install the proper firmware. This time around will be better. On third M8 now. First one, brand new slipped out of workshirt pocket and faceplanted on a tile floor. First damn day! Didn't have the otter box defender case like I should've. 2nd and 3rd ones have been refurbs. So who knows how much use the battery saw before? So I'd like a nice Rom that has built in low battery drain. Every day it seems to drain off a little sooner. Went to black background today to help it out a little. Anyway, haven't been on this forum much since the above problem and thought I'd touch base with you and say thanks. Have a nice one.
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
jon145 said:
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
Click to expand...
Click to collapse
Some folks have been having issues with "international" based custom ROMs on AT&T's LTE network. It seems that AT&T has been making some changes to LTE, possibly in preparation for Voice over LTE (VoLTE, which AT&T calls "HD Voice"), that are messing up voice calls on "international" ROMs.
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
You might try WNC's ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Its based on the Lollipop Developer's Edition ROM, which is intended for use on AT&T's network. He's working on a version based on the AT&T 4.28 update, but its still in testing and not posted yet.
Yeah I've been running the SD 9.0 for several days and no love here in Dallas ... I could speculate for days since D is AT&T's home city.
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
jon145 said:
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
Click to expand...
Click to collapse
He has a beta in testing right now. Just ping him, and he will probably send you a link to the test build. Probably the only reason he would say "no" is if he is going to release soon anyway.
redpoint73 said:
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
Click to expand...
Click to collapse
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
rhughes93 said:
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
Click to expand...
Click to collapse
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
redpoint73 said:
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
Click to expand...
Click to collapse
So I re-flashed SkyDragon, and I think I was not understanding the difference between AROMA installer and the software itself. When I did it the first time, I think I did select T-mobile with wifi calling in AROMA, but AT&T within the software SIM setup. It did not work. Now after getting the stock ROM working, I re-flashed, chose the Other GSM/WWE/whatever option within AROMA, AT&T within the software, and all is right in the world. I may also try the same with Venom this weekend now that I have good restore options, though I don't recall if it had similar options in AROMA or not.
Hello everyone
I am making this post because from reading discussions, there seems to be a large degree of confusion circulating regarding the differences between Verizon branded HTC 10 and the unlocked edition HTC 10, and what software can be used on either and what works on the Verizon network and doesn't. None of the information below is officially endorsed or supported, and I make no guarantees that it will work on your device-- can only vouch what works on mine.
Firstly...if you own an HTC 10 and are a Verizon customer, and your device is S-OFF, this applies to you. Whether it was purchased as an unlocked edition or a Verizon branded edition, the hardware is identical (as far as I understand), and if your device is S-OFF then you can put any software on the device as you so desire. This means when you travel, you can flash GSM firmware, then buy a cheap local prepaid SIM card in your destination country. Or if you get tired of Verizon, you can switch to ATT or TMobile-- or, vice versa, you can switch to Verizon from AT&T or TMobile.
When we get to the subject of firmware, the waters start to get muddy. Generally you are told that if you are on Verizon's network, you must flash only Verizon firmware or your device will not work on their network. This kinda sucks for us Verizon customers, because Verizon is known to be painfully slow at rolling out updates, and there could be serious security holes that are left unpatched while waiting for them to come through.
*However*, I have found that this device runs perfectly fine on Verizon's network with the unlocked-edition firmware (which is significantly more up-to-date as the Verizon firmware), as long as your RADIO partition is flashed with Verizon-specific radio firmware. But aside from the radio partition, none of the software on the other partitions need be Verizon-specific software. This is the method I use for updating to the latest unlocked firmware and Verizon radio (S-OFF requred):
--to update to the latest Verizon radio, flash the latest Verizon firmware-- just search for Verizon htc 10 firmware updates downloads, and you should be able to find it.. I will update this post later with a direct link to that thread..
--next step-- copy your radio partition to a disk image file. boot into recovery, then from adb shell run :
dd if=/dev/block/mmcblk0p30 of=radio.img
exit the shell, use adb pull to pull the radio.img file onto your PC
--step 3. flash the newest firmware for the unlocked-edition...
--step 4. flash the radio.img that you extracted earlier. Fastboot flash from bootloader mode (not RUU mode, not download mode-- just regular bootloader mode with the white screen and the tiny menu). 'fastboot flash radio radio.img'
And that's it.. you're good to go.. again, these instructions assume you are S-OFF and are familiar with the basic procedures for flashing firmware. If you wish to do this, it is done at your own risk.
Happy to answer any questions...hopefully some folks here will find this useful .
Well written, appreciate the info. [emoji106]
Sent from my HTC 10 using Tapatalk
Excellent guide, especially for those of us on Verizon who might want to test the waters with other 10-based ROMs. Since Verizon disables certain functions on its own devices (e.g. "Powersaver," SystemUI Tuner), one might want to look at the unlocked ROMs for full features. Thanks.:good:
I'm googling like crazy how to do the ADB Pull part up. lol I'm in bootloader with CMD promt open and i dont know what to type to ADB pull (never attempted this before).
EDIT: So apparently you need supercid to do this and when i try to modify the cid through "htc_fastboot oem writecid 11111111" it fails and I cannot continue. Anyone have luck doing this?
EDIT2: After a reboot, it allowed me to changed the CID. I tried to flash the firmware first (which crashed and I wasn't able to) so that must have caused the inability to change CID.
Answer to my Question by user @sbong
To Backup your Radio:
1. adb shell
2. su (if needed to get a #)
3. dd if=dev/block/mmcblk0p30 of=/sdcard/radio.img
4. exit
5. You'll find the radio image on the internal sd card
Flashing Latest unlocked firmware WIPED my ROM so just a heads up to anyone trying this.
I ran through these steps and flashed the international firmware version 1.95.401.4 and then flashed the radio I had while still on my VZW firmware. I did have to change my MID and CID before the firmware would flash but after I did it flashed successfully. Then I went back to bootloader (white screen with options) and flashed the radio.img file. After doing that and rebooting I am now sitting at the HTC splash screen with the white background and the red text saying this build is for dev purposes only. Any idea what to do at this point? Thanks!
EDIT: I am trying in TWRP to wipe system, data, and boot and then restore my ROM from a TWRP backup. Will post if it boots after doing this.
EDIT 2: Wiping my partitions in TWRP and the doing a restore allowed me to boot...interesting to note I got my firmware from here: https://docs.google.com/spreadsheets/d/1EdAHLDDxqf9jH65me_8bY9oXdaYusI0eedpwO6yUY2s/pubhtml under the NoWipe section so it shouldn't have messed with my ROM.
I'm hoping this helps with battery life as previously I was on old VZW firmware but my ROM was running a newer FW base. I heard that could cause battery drain. Now my phone FW matches the FW my ROM was based off of.
Unlocked software doesn't support Verizon advanced calling features. Which is a pretty big no for perfect. Just saying...
Sent from my HTC6545LVW using Tapatalk
dottat said:
Unlocked software doesn't support Verizon advanced calling features. Which is a pretty big no for perfect. Just saying...
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
I'm running unlocked US firmware version 1.95.401.4, but what I did do was extract the radio.img from my VZW firmware first, flashed the US unlocked, then flashed the VZW radio.img and booted up. My HD and WiFi calling is activated and working.
pettigrew95 said:
I'm running unlocked US firmware version 1.95.401.4, but what I did do was extract the radio.img from my VZW firmware first, flashed the US unlocked, then flashed the VZW radio.img and booted up. My HD and WiFi calling is activated and working.
Click to expand...
Click to collapse
You still didn't say what rom/software you are running. You can run the firmware from unlocked minus radio while on a Verizon rom and still have these features (why one would do this I have no clue). The unlocked os itself does no have advanced calling built in for Verizon unless it's a custom ROM like what @santod040 built where he added those features back in.
Sent from my HTC6545LVW using Tapatalk
dottat said:
You still didn't say what rom/software you are running. You can run the firmware from unlocked minus radio while on a Verizon rom and still have these features (why one would do this I have no clue). The unlocked os itself does no have advanced calling built in for Verizon unless it's a custom ROM like what @santod040 built where he added those features back in.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
The reason I flashed the US unlocked 1.95.401.4 is because I am running LeeDroid 2.7.0 which is based off of that firmware. I wanted the FW my ROM was based off of to match the firmware my phone was running. Also, VZW is way behind on FW updates for the 10 and I like to be somewhat up to date on the latest security patches from Google.
pettigrew95 said:
The reason I flashed the US unlocked 1.95.401.4 is because I am running LeeDroid 2.7.0 which is based off of that firmware. I wanted the FW my ROM was based off of to match the firmware my phone was running. Also, VZW is way behind on FW updates for the 10 and I like to be somewhat up to date on the latest security patches from Google.
Click to expand...
Click to collapse
Those security updates will be covered on the os side. While leedroid may be based off a 401 build make no mistake that most ril functions required for it to work on Verizon have been carved in from an actual Verizon rom. So in a sense, the parts that actually matter for connectivity are still going to interface best with Verizon firmware.
Sent from my HTC6545LVW using Tapatalk
dottat said:
Those security updates will be covered on the os side. While leedroid may be based off a 401 build make no mistake that most ril functions required for it to work on Verizon have been carved in from an actual Verizon rom. So in a sense, the parts that actually matter for connectivity are still going to interface best with Verizon firmware.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Thank you for that info. So is there any benefit then to what I did? Is anything broken in my phone that I don't know about? I have heard that if the FW a ROM was based off didn't match the FW your phone was running it could be a rogue battery drainer, is this true?
pettigrew95 said:
Thank you for that info. So is there any benefit then to what I did? Is anything broken in my phone that I don't know about? I have heard that if the FW a ROM was based off didn't match the FW your phone was running it could be a rogue battery drainer, is this true?
Click to expand...
Click to collapse
I would say likely not. As to whether anything is broken... if it's working it hasn't broken anything yet. You have to be careful though when running bits and pieces of mixed firmware because partition structure of the phone can change on htc phones based on aboot/hboot. So you can run into a scenario where a phone might not be partitioned to allow certain size images to flash successfully. Me personally, I would run one or the either. In this case, while on verizon, I would use the verizon firmware even if on a custom based rom. The one exception to this would be a built from the ground up rom like CM or AOSP. Some of these were developed to work solely on specific firmware.. One such variant of this in the htc m8 days was super popular. It was also the number one killer of m8's due to the specific/custom firmware flashing that was recommended in the OP. I can't tell you how many users i attempted to help fix their phones that either would not boot at all or that the phone itself was in a full write protected state.
When we get to the subject of firmware, the waters start to get muddy. Generally you are told that if you are on Verizon's network, you must flash only Verizon firmware or your device will not work on their network. This kinda sucks for us Verizon customers, because Verizon is known to be painfully slow at rolling out updates, and there could be serious security holes that are left unpatched while waiting for them to come through.
Click to expand...
Click to collapse
I find this statement sort of funny. Since we are talking firmware and not OS here it's not muddy at all. Verizon is behind on OS updates. Yes they toss in the HTC provided firmware updates as HTC requires.. but make not mistake the OS itself carries the security patches. So thinking you've somehow patched yourself by flashing firmware only is false re-assurement.
If somehow this statement refers to flashing the entire unlocked RUU/ROM/firmware all together and flashing the verizon radio by itself then i stand by my original note that this will get you the latest OS/firmware from HTC which will likely have the best chance at patching security flaws overall.. but the trade off will be advanced calling which is huge for most users.
dottat said:
I would say likely not. As to whether anything is broken... if it's working it hasn't broken anything yet. You have to be careful though when running bits and pieces of mixed firmware because partition structure of the phone can change on htc phones based on aboot/hboot. So you can run into a scenario where a phone might not be partitioned to allow certain size images to flash successfully. Me personally, I would run one or the either. In this case, while on verizon, I would use the verizon firmware even if on a custom based rom. The one exception to this would be a built from the ground up rom like CM or AOSP. Some of these were developed to work solely on specific firmware.. One such variant of this in the htc m8 days was super popular. It was also the number one killer of m8's due to the specific/custom firmware flashing that was recommended in the OP. I can't tell you how many users i attempted to help fix their phones that either would not boot at all or that the phone itself was in a full write protected state.
I find this statement sort of funny. Since we are talking firmware and not OS here it's not muddy at all. Verizon is behind on OS updates. Yes they toss in the HTC provided firmware updates as HTC requires.. but make not mistake the OS itself carries the security patches. So thinking you've somehow patched yourself by flashing firmware only is false re-assurement.
If somehow this statement refers to flashing the entire unlocked RUU/ROM/firmware all together and flashing the verizon radio by itself then i stand by my original note that this will get you the latest OS/firmware from HTC which will likely have the best chance at patching security flaws overall.. but the trade off will be advanced calling which is huge for most users.
Click to expand...
Click to collapse
When you say:
"If somehow this statement refers to flashing the entire unlocked RUU/ROM/firmware all together and flashing the verizon radio by itself then i stand by my original note that this will get you the latest OS/firmware from HTC which will likely have the best chance at patching security flaws overall.. but the trade off will be advanced calling which is huge for most users."
Is this correct? I thought flashing the VZW radio.img would enable advanced calling features to work? I am on a US unlocked FW with VZW radio.img flashed and my advanced calling features are functional on LeeDroid 2.7.0.
pettigrew95 said:
When you say:
"If somehow this statement refers to flashing the entire unlocked RUU/ROM/firmware all together and flashing the verizon radio by itself then i stand by my original note that this will get you the latest OS/firmware from HTC which will likely have the best chance at patching security flaws overall.. but the trade off will be advanced calling which is huge for most users."
Is this correct? I thought flashing the VZW radio.img would enable advanced calling features to work? I am on a US unlocked FW with VZW radio.img flashed and my advanced calling features are functional on LeeDroid 2.7.0.
Click to expand...
Click to collapse
Again,, I will restate it. You are NOT on unlocked. You have pieces of the firmware and a custom rom. That custom rom was based off international rom ( Not even the unlocked version as 401 is international and 617 is the actual unlocked variant).
Don't believe me this is a result of custom rom work and not firmware? Flash the unlocked RUU and then the verizon radio to get service. You will notice that advanced calling doesn't exist in the menu for you.
dottat said:
Again,, I will restate it. You are NOT on unlocked. You have pieces of the firmware and a custom rom. That custom rom was based off international rom ( Not even the unlocked version as 401 is international and 617 is the actual unlocked variant).
Don't believe me this is a result of custom rom work and not firmware? Flash the unlocked RUU and then the verizon radio to get service. You will notice that advanced calling doesn't exist in the menu for you.
Click to expand...
Click to collapse
Ok, sorry if my confusion is frustrating ...So basically my advanced calling features are operable due to my ROM and not the fact that I flashed a VZW radio.img on top of the non VZW firmware I flashed? In a nutshell...Is what I have done beneficial in any way or should I just flash back to the VZW 1.85 FW? Thank you for the help here, it is much appreciated!
pettigrew95 said:
Ok, sorry if my confusion is frustrating ...So basically my advanced calling features are operable due to my ROM and not the fact that I flashed a VZW radio.img on top of the non VZW firmware I flashed? In a nutshell...Is what I have done beneficial in any way or should I just flash back to the VZW 1.85 FW? Thank you for the help here, it is much appreciated!
Click to expand...
Click to collapse
Not frustrating at all. Don't take my responses as that way and certainly don't stop asking questions because of it. I'm still waking up here today so it's probably how i'm writing my responses lol. Personally I would just run the stock verizon firmware and enjoy your custom rom.
Your advanced call features are working due to leedroid splicing in the functional pieces of the advanced call features from the current verizon rom. I remember using an earlier version of his rom that lacked this feature set. I bailed on his rom pretty quickly when that was the only offering available as i needed advanced calling. A month or so later he added it to the rom later. @santod040 is one verizon dev who can comment here further when he sees this to attest to the fact the only way advanced calling works on verizon while on a non-verizon rom is that the DEV must enable it.
On the CM side of the house i have been involved in tracking down pieces of volte/advanced calling even back on the m9 in order to get it functional and I can tell you there it's not easy. So if you're on a non-vzw based rom and have advanced calling... make sure you thank the guys who baked your rom.
dottat said:
Not frustrating at all. Don't take my responses as that way and certainly don't stop asking questions because of it. I'm still waking up here today so it's probably how i'm writing my responses lol. Personally I would just run the stock verizon firmware and enjoy your custom rom.
Your advanced call features are working due to leedroid splicing in the functional pieces of the advanced call features from the current verizon rom. I remember using an earlier version of his rom that lacked this feature set. I bailed on his rom pretty quickly when that was the only offering available as i needed advanced calling. A month or so later he added it to the rom later. @santod040 is one verizon dev who can comment here further when he sees this to attest to the fact the only way advanced calling works on verizon while on a non-verizon rom is that the DEV must enable it.
On the CM side of the house i have been involved in tracking down pieces of volte/advanced calling even back on the m9 in order to get it functional and I can tell you there it's not easy. So if you're on a non-vzw based rom and have advanced calling... make sure you thank the guys who baked your rom.
Click to expand...
Click to collapse
Ok awesome, that pretty much sums up what I needed to hear! My last question, I have heard in the past that if the phone FW does not match the ROMs FW base it could be a rogue battery drainer, is this true? Part of the reason of me flashing the matching FW that LeeDroid 2.7.0 runs is in case mismatched ROM FW and phone FW does cause some kind of battery drain. I have to say, my phones battery is pretty pathetic even with Amplify, Greenify, Power Nap, etc. Thanks again!
Wow. I don't think I could be more confused. I'm humbly asking for clarity
I've got a Verizon 10 that is s-off, rooted, unlocked and running LeeDroid. The download screen shows 1.19 for the OS and @60504 for the radio. If I don't care about preserving the contents of the internal card, what's the simple path to get the fw/radio updated (looks like 1.85.605.8) and back to LeeDroid? If extracting the radio.img is a requirement, usually that kind of file is linked inline with the threads to root or update the fw. It's not, so alarms are going off in my head that there is a reason a flashable radio isn't right next to the RUU which would be next to the instructions for going from a custom rom like LeeDroid or Viper -> update fw/radio -> back to custom rom.
It took me an hour of reading, and not working, just to figure out I have an old fw/radio and one wrong move would commit myself to a day of reading and trying random things.
I can't stress the humble position I'm in and I did search and try to find the clear path, but I can't see it. Help?
jimbob_sf said:
Wow. I don't think I could be more confused. I'm humbly asking for clarity
I've got a Verizon 10 that is s-off, rooted, unlocked and running LeeDroid. The download screen shows 1.19 for the OS and @60504 for the radio. If I don't care about preserving the contents of the internal card, what's the simple path to get the fw/radio updated (looks like 1.85.605.8) and back to LeeDroid? If extracting the radio.img is a requirement, usually that kind of file is linked inline with the threads to root or update the fw. It's not, so alarms are going off in my head that there is a reason a flashable radio isn't right next to the RUU which would be next to the instructions for going from a custom rom like LeeDroid or Viper -> update fw/radio -> back to custom rom.
It took me an hour of reading, and not working, just to figure out I have an old fw/radio and one wrong move would commit myself to a day of reading and trying random things.
I can't stress the humble position I'm in and I did search and try to find the clear path, but I can't see it. Help?
Click to expand...
Click to collapse
For you just flash the custom firmware zip for Verizon that's been posted. You want the one without stock recovery and bootloader.
Going that route updates your phones firmware and saves you from wiping and flashing.
Sent from my HTC6545LVW using Tapatalk
Thank you! Now to figure out which thread has the file you're referring to. I've looked at them all and I can't tell which one does what you're saying.