Related
Hello,
Is there any one using the ATT GS5 on Tmobile network (obviously Tmobile SIM) with wifi calling working ? (Please..please.. I know ATT does not have wifi calling, But if you use a Tmobile Rom with Tmobile sim, you expect to have it working) !!
If yes, would you please share which ROM you are using ? Also if there is a trick to make it wok please share it?
Thanks
no luck so far
This is not a solution, I just wanted to report what I have tried so far.
I have a G900A with a t-mobile SIM card. I called TMO to make sure wifi calling was enabled on my line. I used towelroot + safestrap to install the t-mobile Alliance rom (B4), as well as the latest stock TMO rom. So far, wifi calling does not work. It is always stuck on "Enabling" in the calling options menu. VoLTE doesn't work either, but I wasn't expecting it to. My guess is that there is something in the TMO baseband that makes these things work and that ATT phones don't have.
Any hints and ideas would me much appreciated!
No solution yet...
Guillaume2x said:
This is not a solution, I just wanted to report what I have tried so far.
Any hints and ideas would me much appreciated!
Click to expand...
Click to collapse
JJ here,
I tried this ROM - [ROM] G900TUVU1BNH5 ported from TMobile, rooted, deodexed, no knox, Download Booster
... everything works, nice and smooth, but the Wifi Calling is stuck "Enabling"...
Same boat.
My att s5 is unlocked and on the tmobile network. Your telling me i can flash the tmobile stock rom? And everything will be working properly, except wifi calling?
chronichemp said:
My att s5 is unlocked and on the tmobile network. Your telling me i can flash the tmobile stock rom? And everything will be working properly, except wifi calling?
Click to expand...
Click to collapse
Yes. In particular, Mobile Hotspot will work.
Guillaume2x said:
Yes. In particular, Mobile Hotspot will work.
Click to expand...
Click to collapse
Will everything else work properly? I mainly need the t mobile stock rom to enable mobile hotspot, I have an ATT phone and do not wish to trip efuse. Thanks
does anyone know if the same issue will happen with the international version?
On a similar topic, my dad has a AT&T Samsung Galaxy S5 which was sold in Malaysia. And I found out that his phone was not able to hotspot. I have downloaded the official firmware of Samsung Galaxy S5 for Malaysia and was going to use Odin to flash the firmware into his phone. Does that work and not brick the phone? The phone seems to be unlocked as it can be used here except the firmware and the phone is AT&T barnded. Any advise? Thanks
Sent from my iPad using Tapatalk
It all works!
Guys, I have some great news. Both wifi calling AND VoLTE now work on my SM-G900A on the T-mobile network. Here is what I did:
I installed the latest ATT firmware (OA1), released earlier this February. OTA update did not work, so I had to flash the original firmware (ANCE) via Odin, and then flash the two subsequent updates using update.zip on the SD Card. This will remove safestrap and root, but fear not.
Once my phone had AO1 installed, I used this tutorial to root the phone again. It invonves temporarily flashing an earlier (ND3) kernel, using TowelRoot, and then reflashing the OA1 kernel
With my OA1 rooted, I installed safestrap. Make sure you install busybox first.
With safestrap, I installed the T-mobile Alliance Rom (build B4).
Seconds after booting, both Wifi Calling and Voice over LTE work!
Enjoy!
Guillaume
Hi Guillaume,
Have you tried just installing the stock T-mobile 5.0 firmware on a Att GS5 ?
I have my GS5 in ND3 rooted and I'm on Tmobile, but the procedure you have seems really long...
I really need wifi calling as I'm travelling a lot and it allows to call my wife when I'm back in France.
Thanks
Guillaume2x said:
Guys, I have some great news. Both wifi calling AND VoLTE now work on my SM-G900A on the T-mobile network. Here is what I did:
I installed the latest ATT firmware (OA1), released earlier this February. OTA update did not work, so I had to flash the original firmware (ANCE) via Odin, and then flash the two subsequent updates using update.zip on the SD Card. This will remove safestrap and root, but fear not.
Once my phone had AO1 installed, I used this tutorial to root the phone again. It invonves temporarily flashing an earlier (ND3) kernel, using TowelRoot, and then reflashing the OA1 kernel
With my OA1 rooted, I installed safestrap. Make sure you install busybox first.
With safestrap, I installed the T-mobile Alliance Rom (build B4).
Seconds after booting, both Wifi Calling and Voice over LTE work!
Enjoy!
Guillaume
Click to expand...
Click to collapse
Thanks as this is great news for us G900A users on TMO! Question though: After 0A1 installed/backedup and Alliance installed, did you use safestrap [TWRP] to restore your data from 0A1 install?
Geek007W said:
Thanks as this is great news for us G900A users on TMO! Question though: After 0A1 installed/backedup and Alliance installed, did you use safestrap [TWRP] to restore your data from 0A1 install?
Click to expand...
Click to collapse
Actually no; I had been using the t-mo alliance rom using safestrap for a long time (just with the old ATT modem and kernel), so I just restored the data associated with that.
Some more info after a day of tests:
You can also install the 5th build of Alliance Rom, it works too
The camera sometimes glitches a bit; toggling HDR on/off fixes it
Except for the camera glitch I'm pretty happy with it!
Jojososo said:
Hi Guillaume,
Have you tried just installing the stock T-mobile 5.0 firmware on a Att GS5 ?
I have my GS5 in ND3 rooted and I'm on Tmobile, but the procedure you have seems really long...
I really need wifi calling as I'm travelling a lot and it allows to call my wife when I'm back in France.
Thanks
Click to expand...
Click to collapse
I might to try to create a flashable zip from the latest t-mobile lollipop release, keeping only the /system files, and see how that goes. This is really a shot in the dark, hoping that the 4.4.4 modem and kernel from ATT somehow work well enough with the t-mobile lollipop rom. Damn you locked bootloader!
Guillaume2x said:
Actually no; I had been using the t-mo alliance rom using safestrap for a long time (just with the old ATT modem and kernel), so I just restored the data associated with that.
Some more info after a day of tests:
You can also install the 5th build of Alliance Rom, it works too
The camera sometimes glitches a bit; toggling HDR on/off fixes it
Except for the camera glitch I'm pretty happy with it!
I might to try to create a flashable zip from the latest t-mobile lollipop release, keeping only the /system files, and see how that goes. This is really a shot in the dark, hoping that the 4.4.4 modem and kernel from ATT somehow work well enough with the t-mobile lollipop rom. Damn you locked bootloader!
Click to expand...
Click to collapse
Agree with the last expletive.
I did install in alliance B4 in slot 1 of Safestrap and both wi-fi tether and calling worked well. However, my G900A would not reboot or shutdown (dark screen) without a battery pull. After power up...worked?!?!
Did you install as "Stock" or in a slot?
Also have a G870A (Active). Do you know of anyone attempting the 0A1 method and Alliance Rom with the s5 Active?
I might to try to create a flashable zip from the latest t-mobile lollipop release, keeping only the /system files, and see how that goes. This is really a shot in the dark, hoping that the 4.4.4 modem and kernel from ATT somehow work well enough with the t-mobile lollipop rom. Damn you locked bootloader!
Click to expand...
Click to collapse
What would happen if I odin a Stock T-mobile firmware and let T-mobile update it ?
Will it update the Baseband etc ?
Geek007W said:
Did you install as "Stock" or in a slot?
Click to expand...
Click to collapse
I only use the stock slot.
B4 seems a bit more than stable than B5 for some reason. I get some signal issues with B5, and the fingerprint scanner sometimes fails. (It works when I first install B4, use it for a while, and then upgrade to B5. But if I do a /data wipe on B5, these issues appear. I have no idea why).
---------- Post added at 06:15 PM ---------- Previous post was at 06:11 PM ----------
Jojososo said:
What would happen if I odin a Stock T-mobile firmware and let T-mobile update it ?
Will it update the Baseband etc ?
Click to expand...
Click to collapse
You can't do that, the bootloader is locked.
Guillaume2x said:
You can't do that, the bootloader is locked.
Click to expand...
Click to collapse
Okay thanks,
So I started the steps, I've Odin the original firmware and factory reset on but my baseband stayed ND3...
Tried the OTA update hoping that it would work, but as expected it did not.
So I guess I'm at step 1 of your step one.
Then you said you pushed the update via sd card, where did you find the updates ?
Then I'll do the other steps!
Baby steps by baby steps, F... it's been a long time since I rooted my ipod 1st gen to crack my ps3!
Jojososo said:
Okay thanks,
Then you said you pushed the update via sd card, where did you find the updates ?
!
Click to expand...
Click to collapse
They are in the post that I linked to, under the troubleshooting section. If you want to keep your user data, use adb sideload instead of recovery
Guillaume2x said:
I only use the stock slot.
B4 seems a bit more than stable than B5 for some reason. I get some signal issues with B5, and the fingerprint scanner sometimes fails. (It works when I first install B4, use it for a while, and then upgrade to B5. But if I do a /data wipe on B5, these issues appear. I have no idea why).
Click to expand...
Click to collapse
OK. Installed in stock slot but ROM behaved much differently.
1. Wifi sms/mms work both send/receive but erratically.
2. Outgoing calls connect then immediately drop with local "cancelled" within a few milli-secs with a partial ring at the far end.
3. Can't receive calls at all. TMO network thinks I'm offline even though can receive a text.
3. Phone App GUI stutters when making a call.
4. Camera is basically not usable.
Where there any special steps you took to get this working installed in the stock slot? Has your install remained stable? Thanks in advance.
Geek007W said:
OK. Installed in stock slot but ROM behaved much differently.
1. Wifi sms/mms work both send/receive but erratically.
2. Outgoing calls connect then immediately drop with local "cancelled" within a few milli-secs with a partial ring at the far end.
3. Can't receive calls at all. TMO network thinks I'm offline even though can receive a text.
3. Phone App GUI stutters when making a call.
4. Camera is basically not usable.
Where there any special steps you took to get this working installed in the stock slot? Has your install remained stable? Thanks in advance.
Click to expand...
Click to collapse
My phone is still working flawlessly. What your are describing is what happened to me during the short period I reverted to the NG3 kernel in order to use Towelroot. Did you make sure to reflash the OA1 kernel once you were rooted? (before installing safestrap and, within safestrap, installing the Alliance Rom). I have found Alliance B4 to be more stable, so you could try that. Finally, a factory reset (wipe option in safestrap). Beyond that, you could try the whole thing again: flash the "downgrade to NCE" rom, which will remove safestrap and clean everything up; and take the tutorial from there.
Guillaume2x said:
My phone is still working flawlessly. What your are describing is what happened to me during the short period I reverted to the NG3 kernel in order to use Towelroot. Did you make sure to reflash the OA1 kernel once you were rooted? (before installing safestrap and, within safestrap, installing the Alliance Rom). I have found Alliance B4 to be more stable, so you could try that. Finally, a factory reset (wipe option in safestrap). Beyond that, you could try the whole thing again: flash the "downgrade to NCE" rom, which will remove safestrap and clean everything up; and take the tutorial from there.
Click to expand...
Click to collapse
Thanks again Guillaume,
Was running OA1 prior to Alliance B3, so just wiped Dalvik and Cache again, rebooted and left phone for the night. By next morning all was well except for the camera HDR issue. Once toggled it is OK until closed and reopened. Haven't had the time to look into whether there are Alliance B4 options which may affect this.
Have run it a few days and have had zero issues with Wi-Fi calling or tethering or apps: a very smooth experience.
Thanks again for your contribution. Also muniz_ri will find a bottle of wine on the doorstep soon. :highfive:
I have a t-mobile purchases N6 that is running rooted stock. This morning I got the message that the 5.1.1 update was available and I let it download but since I am running TWRP, nothing happened at reboot which is what you would expect. Can I just install the rom that downloads? I know there is a rooted stock rom available but I sometimes use wifi calling. I don't care if I lose root but I want to make sure I don't brick my phone.
I think more than anything I don't want to keep looking at the notification that tells me there is a new version and it won't go away.
You won't be able to flash the OTA file since you made modifications to /system. It will just fail The OTA is just a patch and not a full image.
If you want to update to 5.1.1, you'll need to flash the image or a custom ROM.
Ok thanks! Other than losing WiFi calling, is there any issue with flashing the international ROM to a T-Mobile phone? I know T-Mobile has a weird band that isn't always connected with all radios, at least on other phones.
if you want wifi calling and 5.1.1, install the t-mobile specific rom here:
https://developers.google.com/android/nexus/images
richdaley said:
Ok thanks! Other than losing WiFi calling, is there any issue with flashing the international ROM to a T-Mobile phone? I know T-Mobile has a weird band that isn't always connected with all radios, at least on other phones.
Click to expand...
Click to collapse
You can install international versions and have it work on T-Mobile. If you want all the features, flash this latest version.
Since I first started down this Android path I've always brought my phones direct from big red which, for all the problems it created it did make life simple when it came to identify which ROM to download etc.
This week I broke tradition and dropped some money on Google's lap and picked up a Nexus 6 direct from them - no more locked down to VZW for me if I so choose.
Previously I had a Incredible, then a GS III then finally a M8 - all three rooted and unlocked\S-OFF'd so this isn't my first rodeo.
That said I'm also wanting to tread VERY VERY lightly here because time and time again I read the the biggest reason folk get bricks is because they assumed and didn't ask questions before they flashed.
So, all this aside, here I am with my now Unlocked 5.0 Non branded Nexus 6 with LNX07M with TWRP 2.8 latest as a custom recovery and, as of right now, no root (to help ease any upgrade).
I've found various Stock ROMS out there there would indicate I'd need to be however on 5.0.1 before I could sideload a 5.1.1. Is this true? If so, do I need to blow away TWRP before I do this because when I tried previously to take the update it dropped me into TWRP.
Is there any way I can avoid all this, wipe and flash a Stock 5.1.1 direct? Wiping the phone isn't an issue as there's nowt on it right now. And should I root now, while still on 5.0 or wait until 5.1.1 (because it'll require a factory reset). Would root even survive a 5.1.1 upgrade?
I'm nervous here because I keep seeing lines such as 'T-MOBILE only' and different code letters after the build name seemingly signifying the different vendors. Given that I got mine direct from Google though I'm unsure how I should proceed because I really don't want to be left with an unhappy 6 so soon after delivery.
Thanks in advance!
R
Rachel Ambler said:
Since I first started down this Android path I've always brought my phones direct from big red which, for all the problems it created it did make life simple when it came to identify which ROM to download etc.
This week I broke tradition and dropped some money on Google's lap and picked up a Nexus 6 direct from them - no more locked down to VZW for me if I so choose.
Previously I had a Incredible, then a GS III then finally a M8 - all three rooted and unlocked\S-OFF'd so this isn't my first rodeo.
That said I'm also wanting to tread VERY VERY lightly here because time and time again I read the the biggest reason folk get bricks is because they assumed and didn't ask questions before they flashed.
So, all this aside, here I am with my now Unlocked 5.0 Non branded Nexus 6 with LNX07M with TWRP 2.8 latest as a custom recovery and, as of right now, no root (to help ease any upgrade).
I've found various Stock ROMS out there there would indicate I'd need to be however on 5.0.1 before I could sideload a 5.1.1. Is this true? If so, do I need to blow away TWRP before I do this because when I tried previously to take the update it dropped me into TWRP.
Is there any way I can avoid all this, wipe and flash a Stock 5.1.1 direct? Wiping the phone isn't an issue as there's nowt on it right now. And should I root now, while still on 5.0 or wait until 5.1.1 (because it'll require a factory reset). Would root even survive a 5.1.1 upgrade?
I'm nervous here because I keep seeing lines such as 'T-MOBILE only' and different code letters after the build name seemingly signifying the different vendors. Given that I got mine direct from Google though I'm unsure how I should proceed because I really don't want to be left with an unhappy 6 so soon after delivery.
Thanks in advance!
R
Click to expand...
Click to collapse
The main reason that some users bricked their phone is that they wiped the OS and had a locked bootloader which leaves no possibility ro recover the phone
What carrier do you use?
T-Mobile would be the LYZ28E rom and ATT/USC/International devices would be LMY47Z and Verizon is LMY47E.
Look here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 and here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Unless something is special about the N6 that I'm not aware of, the OS you update FROM only matters if you're sideloading an OTA file. Flashing factory images, you could be coming from a custom ROM(I just took my old N4 from CM12.1 to stock 4.4 on Sunday).
The current build for VZW is 5.1 LMY47E. I think they are updating to 5.1.1 now(LMY47Z, which seems to be universal now except for maybe T-Mo). I flashed mine from E to Z on Saturday because I bought mine unlocked but it had the VZW build, and I'm on an AT&T MVNO.
gee2012 said:
What carrier do you use?
T-Mobile would be the LYZ28E rom and ATT/USC/International devices would be LMY47Z and Verizon is LMY47E.
Look here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 and here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Click to expand...
Click to collapse
Still with VZW for now, but, as I said, I didn't purchase the phone from them, I brought it from Google direct so it's carrier agnostic (well, in the US at least!) hence my confusion. The last thing I want to do is flash a ROM that's carrier specific but I don't know which one to take with this being the case.
As for the order, my M8 needed to go in two stages to jump from my old Venom build due to changes with the radio (I think) - hence my question there.
If you root, you'll.never get an OTA anyway, sonit doesn't matter which rom you flash aa you can flash any other rom.over it
None of the carrier specific roms will restrict anything, or add branding, so go for whichever.
Rachel Ambler said:
Still with VZW for now, but, as I said, I didn't purchase the phone from them, I brought it from Google direct so it's carrier agnostic (well, in the US at least!) hence my confusion. The last thing I want to do is flash a ROM that's carrier specific but I don't know which one to take with this being the case.
As for the order, my M8 needed to go in two stages to jump from my old Venom build due to changes with the radio (I think) - hence my question there.
Click to expand...
Click to collapse
Just flash the LMY47E rom and when its available you get the OTA to update or sideload the OTA from here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 when its available.
danarama said:
None of the carrier specific roms will restrict anything, or add branding, so go for whichever.
Click to expand...
Click to collapse
Really? Is there a reason why they exist then? Usually my understanding was that they contained carrier specific items including radios and bloatware.
Rachel Ambler said:
Really? Is there a reason why they exist then? Usually my understanding was that they contained carrier specific items including radios and bloatware.
Click to expand...
Click to collapse
There's no bloatware on these roms.
Verizon rom includes binaries that make VoLTE work properly on their network where as T-mobile adds a kernel fix to allow their wifi calling to work. And that's it...
gee2012 said:
Just flash the LMY47E rom and when its available you get the OTA to update or sideload the OTA from here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 when its available.
Click to expand...
Click to collapse
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
danarama said:
There's no bloatware on these roms.
Verizon rom includes binaries that make VoLTE work properly on their network where as T-mobile addsna kernel fix to allow their wifi calling to work. And that's it...
Click to expand...
Click to collapse
Interesting. So this would leave me to believe then that, should I decide one day to jump carriers, I'd be better off flashing a ROM for that carrier at the appropriate time?
This being the case, why would the phone come with no carrier specific software on board from Google? Wouldn't this mean I might get a degraded service?
Rachel Ambler said:
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
Click to expand...
Click to collapse
If you want to use T-Mobile in the future you just flash the LYZ28E rom.
Rachel Ambler said:
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
Click to expand...
Click to collapse
Well all Nexus 6 used to get the same updates but tmob and red, wanted approval on theirs - and now we know why.
Since google are still sending these updates and they update onto generic builds, they can only use your sim card as the identifier.
If you leave root out of it, the only way you can avoid the vzw update is to manually update to something else (something vzw updates won't work on). Each OTA looks for a specific build to flash on and won't flash on anything else.
If you do accept the vzw update, you'll never get away from them unless you manually flash a full factory rom.
Bringing root back into it, OTA will never flash anyway, so you'll have to either manually flash factory or flash rom.zips in TWRP
gee2012 said:
If you want to use T-Mobile in the future you just flash the LYZ28E rom.
Click to expand...
Click to collapse
This is already explaining a lot! So, given that, as I said, I'm not bog standard non-carrier specific 5.0 (and I've yet to even migrate my SIM over) the suggested action would be to download LMY47E 5.1 (as 5.1.1 is not yet out for VZW as they ALWAYS seem to be last to the party) and flash it via TWRP? And I can do that over my LNX07M build?
danarama said:
"Well all Nexus 6 used to get the same updates but tmob and red, ..."
Click to expand...
Click to collapse
Great info, very useful.
Rachel Ambler said:
Interesting. So this would leave me to believe then that, should I decide one day to jump carriers, I'd be better off flashing a ROM for that carrier at the appropriate time?
This being the case, why would the phone come with no carrier specific software on board from Google? Wouldn't this mean I might get a degraded service?
Click to expand...
Click to collapse
There were no carrier specific ROMs when Nexus 6 came out. Using any rom on any Nexus and they will all act the same, except you wont get improved volte or wifi calling on those carriers. Their changes will not prove detrimental on other carriers
danarama said:
Well all Nexus 6 used to get the same updates but tmob and red, wanted approval on theirs - and now we know why.
Since google are still sending these updates and they update onto generic builds, they can only use your sim card as the identifier.
If you leave root out of it, the only way you can avoid the vzw update is to manually update to something else (something vzw updates won't work on). Each OTA looks for a specific build to flash on and won't flash on anything else.
If you do accept the vzw update, you'll never get away from them unless you manually flash a full factory rom.
Bringing root back into it, OTA will never flash anyway, so you'll have to either manually flash factory or flash rom.zips in TWRP
Click to expand...
Click to collapse
Now the murky seas are de-murkyfing!
So go for the VZW build for now with the knowledge and understanding that if I ever decide to bid them a less than fond adieu, I'd be best at that point flash a factory image OR flash another carrier specific ROM once I've chosen the new carrier?
And should I root now, or post the 5.1 flash? I'm guessing post because I'd assuming flashing 5.1 would blow my root away.
I assume I can flash post VZW 5.1 because the boatloader is still all mine and the flash doesn't effect that. Right?
Rachel Ambler said:
This is already explaining a lot! So, given that, as I said, I'm not bog standard non-carrier specific 5.0 (and I've yet to even migrate my SIM over) the suggested action would be to download LMY47E 5.1 (as 5.1.1 is not yet out for VZW as they ALWAYS seem to be last to the party) and flash it via TWRP? And I can do that over my LNX07M build?
Click to expand...
Click to collapse
Depends how you do it.
Google factory images are flashed from a computer using fastboot.
You may be able to find a rom.zip of that version on xda that can be flashed via TWRP.
As long as you aren't flashing an incremental OTA, you can flash over anything. OTA actually patch files not replace them, so they can only be flashed on the rom they are intended for.
Rachel Ambler said:
Now the murky seas are de-murkyfing!
So go for the VZW build for now with the knowledge and understanding that if I ever decide to bid them a less than fond adieu, I'd be best at that point flash a factory image OR flash another carrier specific ROM once I've chosen the new carrier?
And should I root now, or post the 5.1 flash? I'm guessing post because I'd assuming flashing 5.1 would blow my root away.
I assume I can flash post VZW 5.1 because the boatloader is still all mine and the flash doesn't effect that. Right?
Click to expand...
Click to collapse
Why not go with a custom rom like chroma? Get 5.1.1 now and personally it works really well.
danarama said:
Depends how you do it.
Google factory images are flashed from a computer using fastboot.
You may be able to find a rom.zip of that version on sea that can be flashed via TWRP.
As long as you aren't flashing an incremental OTA, you can flash over anything. OTA actually patch files not replace them, so they can only be flashed on the rom they are intended for.
Click to expand...
Click to collapse
I'm sorry if that sudden flash of the light coming on in my head just blinded you, but that's what happens when things start to make sense!
OK, so, this all being the case, and that the OTA's are incremental, then in order to go 5.1 with the build from http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 then I WOULD need 5.0.1? Would that work though if I'm on a generic build since, if it's expecting to patch existing VZW files, wouldn't it fail because they're not there? Failing that I'd need to find a flashable 5.1 for VZW (if one even exists)?
endlessryan said:
Why not go with a custom rom like chroma? Get 5.1.1 now and personally it works really well.
Click to expand...
Click to collapse
But it wouldn't have the VoLTE improvements, etc, right? Besides, right now I'd like to stay as stock as possible as it's not just my phone I'm working on, both myself and my wife got one at the same time and I know she will most definitely NOT want anything other than stock.
I've got a S6 Active that when I received it was on Lollipop. I was able to flash MM (using thread here on XDA) to it before it was officially released from the carrier. Then I was able to flash back to stock Lollipop and then received the MM 6.0.1 update from the carrier. I wanted to flash back to Lollipop for testing purposes but was unable. I think it's because the bootloader is locked?
I've read a bunch of threads saying that the S6 active has nott been rooted? Has a locked bootloader? Can't run custom roms?
Can someone please give me the scoop on this. I'd like to go back to lollipop for testing but I don't think its possible. Is that the case? Thanks.
Roveer
roveer said:
I've got a S6 Active that when I received it was on Lollipop. I was able to flash MM (using thread here on XDA) to it before it was officially released from the carrier. Then I was able to flash back to stock Lollipop and then received the MM 6.0.1 update from the carrier. I wanted to flash back to Lollipop for testing purposes but was unable. I think it's because the bootloader is locked?
I've read a bunch of threads saying that the S6 active has nott been rooted? Has a locked bootloader? Can't run custom roms?
Can someone please give me the scoop on this. I'd like to go back to lollipop for testing but I don't think its possible. Is that the case? Thanks.
Roveer
Click to expand...
Click to collapse
hi
yes it's not possible to downgrade your rom or your bootloader because of the locked bootloader that prevents any try to modify the device...
is this typical of most phones? I've read of others frutrations about the S6 active still having a locked bootloader. Did I just pick a bad platform? Is S6 the same way? How about S7 series? Thanks.
roveer said:
is this typical of most phones? I've read of others frutrations about the S6 active still having a locked bootloader. Did I just pick a bad platform? Is S6 the same way? How about S7 series? Thanks.
Click to expand...
Click to collapse
Locked bootloaders are often the case for phones provided by carriers. While a phone purchased directly from the manufacturer is usually able to have its bootloader unlocked, carrier phones are locked by the carrier themselves, preventing any tampering by the end user. A custom ROM is any modified version of Android not developed by the company that made your phone. Think of it like a third party system. To get these custom ROMs onto your phone you must "flash" (simply, install) the ROM from your computer to your phone. However, a locked bootloader prevents this. While in some cases there are ways to get around carrier locked bootloaders, it is generally futile. If you purchased the S6 Active in hopes of tinkering around with custom ROMs, I'm afraid you have picked the wrong phone. The S6 Active, as of currently, is permanently locked to Samsung's and AT&T's "stock ROM"
EDIT: as for going back to Lollipop, the reason this is generally not possible is due to the fact that the Marshmallow update also updated critical parts related to the bootloader. It is impossible to roll back these changes once they have been made as they are strictly one way.
Thanks for the explanation. I didn't buy the phone for the express reason for changing android versions but rather to use as my daily driver. We are a BES 12 (Blackberry Enterprise Server) shop and I have found a bug that causes the VPN portion of the software to drop after an hour or so. Simply hitting the home button (waking the phone up re-establishes the vpn and mail flow continues). I'm working with BB to determine what's going on. I've disabled all power saving and doze settings yet still the problem. They are going to activate some other phones on my system to see if they see the problem. My reason for wanting to go back to lollipop is that I don't believe I saw this problem when I was on that OS so I was hoping to go back to confirm that behavior. I like the "active" phones for their ruggedness but don't have an unlimited budget to be buying handsets.
Roveer
roveer said:
Thanks for the explanation. I didn't buy the phone for the express reason for changing android versions but rather to use as my daily driver. We are a BES 12 (Blackberry Enterprise Server) shop and I have found a bug that causes the VPN portion of the software to drop after an hour or so. Simply hitting the home button (waking the phone up re-establishes the vpn and mail flow continues). I'm working with BB to determine what's going on. I've disabled all power saving and doze settings yet still the problem. They are going to activate some other phones on my system to see if they see the problem. My reason for wanting to go back to lollipop is that I don't believe I saw this problem when I was on that OS so I was hoping to go back to confirm that behavior. I like the "active" phones for their ruggedness but don't have an unlimited budget to be buying handsets.
Roveer
Click to expand...
Click to collapse
If the software you are referring to is something provided by blackberry, perhaps they need to patch their software for compatibility with Android Marshmallow. While not all software is broken by a major Android update, there are definitely some that are. Of course enterprise level software is entirely foreign to me (I'm only 17), so getting a second opinion on this issue would definitely be a good idea.
OK, I understand locked bootloader preventing from flashing any custom roms etc. Even preventing previous official android. Here's another question: Is there a way to flash current android version? I'm on G890AUCS4CPF3 which is an AT&T build. What is the carrier's method to reflash current OS when there has been some corruption to the version that is on the phone. Not just wipe, but reload entire android, re-create file system etc... That's what I want to try next. Blackberry has activated a Samsung S6 on my server and it (so far) is not exhibiting the same problem as my S6 Active. This leads me to believe that it my be a problem with my hardware. I want to do a reload at this point. Any ideas how I can do that? Odin flash? Is there a repository for the G890AUCS4CPF3 ROM?
Thanks,
Roveer
roveer said:
OK, I understand locked bootloader preventing from flashing any custom roms etc. Even preventing previous official android. Here's another question: Is there a way to flash current android version? I'm on G890AUCS4CPF3 which is an AT&T build. What is the carrier's method to reflash current OS when there has been some corruption to the version that is on the phone. Not just wipe, but reload entire android, re-create file system etc... That's what I want to try next. Blackberry has activated a Samsung S6 on my server and it (so far) is not exhibiting the same problem as my S6 Active. This leads me to believe that it my be a problem with my hardware. I want to do a reload at this point. Any ideas how I can do that? Odin flash? Is there a repository for the G890AUCS4CPF3 ROM?
Thanks,
Roveer
Click to expand...
Click to collapse
Carriers can tell if your Firmware is theirs or not because official Firmware is digitally signed by Samsung and AT&T.
As for using Odin, that would be your most viable option. However, I am not aware of any Odin images for the Marshmallow update on the S6A. As far as I know, Odin cannot get around the restriction of having a newer Bootloader, so you cannot flash down.
One thing you can try is to wipe cache partition. If that fails, factory reset from within the bootloader. Just make sure you've backed your data up.
EDIT: Take note that there is a difference in Firmware between the S6 vs the S6A.
EDIT 2: In your other thread you stated you can't flash back to lollipop due to a locked bootloader. This is actually due to, as stated before, the newest bootloader tha to the latest Android Marshmallow update.
FevenKitsune said:
Carriers can tell if your Firmware is theirs or not because official Firmware is digitally signed by Samsung and AT&T.
As for using Odin, that would be your most viable option. However, I am not aware of any Odin images for the Marshmallow update on the S6A. As far as I know, Odin cannot get around the restriction of having a newer Bootloader, so you cannot flash down.
One thing you can try is to wipe cache partition. If that fails, factory reset from within the bootloader. Just make sure you've backed your data up.
EDIT: Take note that there is a difference in Firmware between the S6 vs the S6A.
EDIT 2: In your other thread you stated you can't flash back to lollipop due to a locked bootloader. This is actually due to, as stated before, the newest bootloader tha to the latest Android Marshmallow update.
Click to expand...
Click to collapse
So I wiped the cache partition and factory reset within the bootloader and tried my app again. It continued to fail. I even found the MM image in the S6 Active MM thread and sideloaded it. It was only 400+ megs though. Still the app doesn't work so I'm starting to doubt that my problems are related to my particular S6 but its always a possibility. I'm trying to get Blackberry to dig up their own S6A and test on their own. They've been testing with a S6 for the past 2 days (on my BES server) and haven't seen the same problems, so it's either my device or a problem with the S6A (which as has been pointed out does use a different firmware version than the S6), but until I can get another S6 Active device to test I won't know.
Roveer
When I first got this Blu R1 HD Prime version I was able to remove the ads and such by using the SP tool and directions here: https://forum.xda-developers.com/r1-hd/development/blu-r1-hd-remove-amazon-ads-ota-updates-t3427303. It is currently on 6.5. I have never updated it since then because I did not want to deal with ads again. Now I am having issues with it not wanting to connect to any mobile data (wifi is fine though and the sim card works in another phone) I figured an update might not hurt things. So with all that said, what is the best way to get the phone updated without bringing the ads back and not losing any data/apps?
kameleon25 said:
When I first got this Blu R1 HD Prime version I was able to remove the ads and such by using the SP tool and directions here: https://forum.xda-developers.com/r1-hd/development/blu-r1-hd-remove-amazon-ads-ota-updates-t3427303. It is currently on 6.5. I have never updated it since then because I did not want to deal with ads again. Now I am having issues with it not wanting to connect to any mobile data (wifi is fine though and the sim card works in another phone) I figured an update might not hurt things. So with all that said, what is the best way to get the phone updated without bringing the ads back and not losing any data/apps?
Click to expand...
Click to collapse
Not knowing what is causing the data connection problems, it is not positive making update will help, but worth a shot.
I have posted updates that can be installed without being forced back into the ads system.
Will need to install TWRP recovery to install them.
Rooting the system is not needed to remove ads with twrp installed, if you do not want to have room rooted.
Since you are on 6.5 and not 6.6 you can use spft to flash recovery, or you can also use the dirty-cow method "tool" to unlock bootloader and then install recovery with fastboot(built into the tool )
If you don't have recovery then my opinion is use this to get recovery installed
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333
Then use twrp to install one of these ROMs (recommend v21)
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
in my case two amzn 8.7 will show that it recognize sim, but no service, would need root to try and change IMEI, probably these phones are from a batch reported lost or stolen, but to be blacklist even in my country, a bit farfetched.
Gizmosis350k said:
in my case two amzn 8.7 will show that it recognize sim, but no service, would need root to try and change IMEI, probably these phones are from a batch reported lost or stolen, but to be blacklist even in my country, a bit farfetched.
Click to expand...
Click to collapse
could just be an APN setting needs set to your carrier number/ settings.
Rebooting about a dozen times seems to have fixed it. I double checked the APN and everything but nothing worked. It just started working again. However I do still want to update it just to make sure it has more recent bug fixes. Thanks all.