Related
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 have LMY48M build number , anyone get it yet or am i better off flashing a stock image
I have a Nexus 6 on AT&T with the same build number as you. I haven't received the Android 6.0 Marshmallow update yet either. I'm new to Nexus, so I'm not sure how long it takes for AT&T accept the update. I would probably wait for about one more week and if it hasn't come to you by then, then yes, I would flash it.
colerollins said:
I have a Nexus 6 on AT&T with the same build number as you. I haven't received the Android 6.0 Marshmallow update yet either. I'm new to Nexus, so I'm not sure how long it takes for AT&T accept the update. I would probably wait for about one more week and if it hasn't come to you by then, then yes, I would flash it.
Click to expand...
Click to collapse
I was notified that the OTA was downloaded and ready to be installed this afternoon about 4:30 PM EDT. I haven't installed it yet, I'm still waiting to see how gaining root access plays out.
alryder said:
I was notified that the OTA was downloaded and ready to be installed this afternoon about 4:30 PM EDT. I haven't installed it yet, I'm still waiting to see how gaining root access plays out.
Click to expand...
Click to collapse
same as always. if you havd root, you can not apply an ota, it wint work. if you don't have root, you can take it, then root your n6 just like any other nexus ever. 1 unlock your bootloader, 2. fastboot flash twrp recovery, 3. flash supersu in your new recovery. that never changes on any nexus, since google makes it easy for us to root.
After further reading it looks like the update I have is to LMY48W, not MRA58K.
My dad has AT&T and is still waiting for the 6.0 update on his Nexus 5. He's still on LMY48M and it says his phone is up to date. He won't let me flash the factory image for him either....
I got my Nexus 6 from Amazon but I have AT&T. Do you guys have HD Voice/VOLTE enabled? I did a live chat with them yesterday and said because I don't get my updates from them, I can't use it even though it's in my area. I have the apn nextgenphone showing up, just not getting hd voice.
I am on LMY48M as well. I bought mine unlocked from Google but am running it on Cricket Wireless. Does carrier matter on how long it will take to get pushed out?
I'm on Cricket, got a new Nexus 6, it is still on Build number: LRX22C , 5.0.1
How on earth do I make it OTA update to something newer?
cz829x18 said:
I got my Nexus 6 from Amazon but I have AT&T. Do you guys have HD Voice/VOLTE enabled? I did a live chat with them yesterday and said because I don't get my updates from them, I can't use it even though it's in my area. I have the apn nextgenphone showing up, just not getting hd voice.
Click to expand...
Click to collapse
Not sure why they said that...the Nexus 6 isn't listed as one of their HD Voice capable phones. Until they get their act together with that, no one on AT&T will have HD Voice on the Nexus.
I got the MRA5BK update on my Nexus 5 on 10/8 on AT&T but am still waiting for it on my T-Mobile N6 and my N9.
Mine automatically updated to 5.1.1 when I first set it up.
I just made mine update by removing the Cricket (AIO) SIM.
Stopping the google framework, clearing the data.
Performing the CHECKIN.
Then is started to 5.1 and then to 5.1.1
Seems strange why it didn't start by itself.
And then to marshmallow? If so, could you elaborate on the ?
No, sorry, it stopped at a few variations of 5.1.1
Shucks
I to have a Nexus 6 on Cricket running 5.1.1 build number LMY48T. I got mine to update by pulling sim card and leaving WiFi on through the night. Update to 5.1.1 was ready that morning
skratch1702 said:
I to have a Nexus 6 on Cricket running 5.1.1 build number LMY48T. I got mine to update by pulling sim card and leaving WiFi on through the night. Update to 5.1.1 was ready that morning
Click to expand...
Click to collapse
They're talking about the update to 6.0, not to 5.1.1.
liquidzoo said:
They're talking about the update to 6.0, not to 5.1.1.
Click to expand...
Click to collapse
It is kinda connected though, as it looks like it depends which SIM you have inserted to whether an update happens.
The guy I was referring to said his was stuck on 5.0.1.
Hello guys. Just bought 2 days a go a new Nexus 6. Blue with 32Gb, unlocked.
Tottaly sealed, broke the seal myself, straight from Google.
But the phone says it is updated, and finds no new update. Im on LMY47D with Android 5.1 and I dont even receive 5.1.1
Tried factory reset without SIM Card, cleaning Framework and reboot without card, everything. To no avail.
Any idea what is going on? Shouldnt I get at least Android 5.1.1?
PS: I know I can sideload it, but still, something is clearly wrong, and I would like very much to sort it out.
Thank you very much.
Same issue here. Only I'm on 5.0 and can't find any update and I would prefer to not sideload already.
if you want your phone to check for an update, you have to be on WiFi. if in youre on network instead, itll always say up to date.
I'm on wifi. It still shows no update.
Same situation, on Wifi offcourse.
tryklon said:
Same situation, on Wifi offcourse.
Click to expand...
Click to collapse
Try a factory reset, then remove your carrier SIM and power up on WiFi. My bet is that your N6 will start churning through OTAs in sequence. Not sure that you will get all the way to Marshmallow 6.0, because that last OTA is still being rolled out.
Already did it... waste of time, no updates
If your not willing to simply download and flash the images from googles website, that is your choice... but there is nothing to do but wait.
Hi Guys I am in the same boat, brand new n6 on 5.0.1 and saying up todate . In uk and carrier is Virgin if that helps.
Mal
Something strange is definately happening with Google update servers...
same dilemma and same version as op..
Personally I was like you all. I got my nice shiny new n6 from verizon (free upgrade...) Got it home kept pressing check for updates. Tried all the clearing app data from frameworks and all that.
But in the end I sideloaded it. I documented it over on the OTA url post. It is not that hard, just need some time. If you don't want to wait it might be your only option.
Total time invested was probably 1.5 hours. Downloaded all the files to my laptop and started using WUGFresh.
Stop waiting and update manually? It's not difficult, you can even save your userdata by not flashing it. There are different (and possibly easier) ways to install an update other than sideloading. especially when you can skip all the OTAs and flash directly to 6.0.
No need for a tool kit and it won't take much longer than the time it takes for you to download the factory image and extract the files.
The point is that there might be something wrong with Google's OTA servers.
Or maybe something is wrong about these phones ?
Sent from my VS985 4G using Tapatalk
Thats my point exactly. What if theres something wrong with the phone?
Google should clarify why old updates are not being delivered... not even questioning 6.0, but 5.1.1
same issue on new nexus 6 of my girlfriend. I manually sideloaded up to 5.1.1 (it's the international version) and now she's waiting for 6.0
europeanpaul said:
same issue on new nexus 6 of my girlfriend. I manually sideloaded up to 5.1.1 (it's the international version) and now she's waiting for 6.0
Click to expand...
Click to collapse
Why not sideload 6.0
jdice said:
Why not sideload 6.0
Click to expand...
Click to collapse
Why is Google not delivering OTA updates to these N6 owners ?
Sent from my VS985 4G using Tapatalk
Because there were a couple of security updates between 5.1.1 and 6.0 (as far AS I remember on my N6) and because I want to be sure OTA works!
This issue is becoming more and more coomon. Lot's of people complaining on several forums about this issue.
At least its easy to see something is clearly wrong with the OTA's, since no one is getting any. There is people stuck on 5.0, 5.0.1, 5.1, etc whichever came preinstalled stays without updates.
Hi Guys,
I have a fully stock AT&T S6 Edge (G925A) and it is still running on Lollipop. The reason is that when I check for updates through the About section, it says my phone has the latest firmware, so it doesn't find the OTA for MM.
I even installed Samsung SmartSwitch on Windows and checked for updates using that but still it couldn't find any updates.
So the question is whether or not there is a safe method for flashing stock MM firmware manually (probably through ODIN) without bricking the phone?
I have another S6 Edge International model (G925F) and I update it manually every month through ODIN, but it is rooted and bootloader is unlocked. I am not sure how a similar method would work for a locked bootloader.
I appreciate your help
Any ideas?
I think happens is because we are outside the US .... I update it without problems with a guide here and works perfectly -> "flashing 6.0.1 encryption enabled"
Davis26 said:
I think happens is because we are outside the US .... I update it without problems with a guide here and works perfectly -> "flashing 6.0.1 encryption enabled"
Click to expand...
Click to collapse
Can you please provide a link?
I am actually using a VPN that uses US ip addresses. So I don't think that would be a problem.
alireza_simkesh said:
Can you please provide a link?
I am actually using a VPN that uses US ip addresses. So I don't think that would be a problem.
Click to expand...
Click to collapse
The issue is that we should be in US connected to an antenna AT&T
This is the Link:
http://forum.xda-developers.com/att-galaxy-s6-edge/help/flashing-6-0-1-encryption-enabled-t3372367
Davis26 said:
I think happens is because we are outside the US .... I update it without problems with a guide here and works perfectly -> "flashing 6.0.1 encryption enabled"
Click to expand...
Click to collapse
I have the same question. I have the same issue and I am in the US. I cannot get this phone to update past 5.0.2
c.lopez52577 said:
I have the same question. I have the same issue and I am in the US. I cannot get this phone to update past 5.0.2
Click to expand...
Click to collapse
You are with AT&T?
Davis26 said:
You are with AT&T?
Click to expand...
Click to collapse
Yes, I'm with AT&T
I just got one of the z2 force on the sprint deal, but am on t-mobile. I need wifi calling at work and abroad, so no wifi calling is a showstopper. I flashed a bunch of the "flashall" packages but kept getting issues like no wifi, no network, or on sprint no wifi calling. So I just tried frankensteining a package together, and miraculously it seems to be working!!
WARNING I have been using this for a couple days, everything seems fine, but your life is in your own hands.
We will basically be flashing the boot, oem, system, and system_b img files OVER a regular sprint flashall package.
I start with
unlocked bootloader
newest sprint flashall package, 27.109-48-6
newest tmobile package 27.109-51-7
(get these here: https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783)
extract the 2 packages
copy all system.img, system_b.img, boot.img, and oem.img FROM TMOBILE folder TO SPRINT folder
flashall the new franken SPRINT package
make sure you wipe (fastboot -w) before or after, however most scripts do this
Now you can root and sim unlock if you havent already done so. Hopefully this works for everyone like it has for me.
4g stays on during a call, this looks like volte and data works during the call
wifi calling works
I will be making a full package with all of this, but it'll take me a couple hours to compress and upload. Just got super excited because it seems lots of people are having this issue and there aren't any solutions.
this same concept can probably be used for other carriers, but I only have tmobile.
UPDATE got magisk working, turns out you ALSO need to move the boot.img from the Tmobile package, then just install magisk the way the other threads show. Changed instructions to match. **Updating package now!**
Here's the modified package, just extract and flashall.bat (including magisk fix, but not rooted on install)
https://mega.nz/#!6Z9T1TqC!gCwHX7NMXmZqq2NJ20MIgMNmIEYcZ9bDBG0xHgtAkm4
robertzas said:
I just got one of the z2 force on the sprint deal, but am on t-mobile. I need wifi calling at work and abroad, so no wifi calling is a showstopper. I flashed a bunch of the "flashall" packages but kept getting issues like no wifi, no network, or on sprint no wifi calling. So I just tried frankensteining a package together, and miraculously it seems to be working!!
WARNING I have been using this for half a day, you are taking your life into your own hands.
We will basically be flashing the oem, system, and system_b img files OVER a regular sprint flashall package.
I start with
unlocked bootloader
newest sprint flashall package, 27.109-48-6
newest tmobile package 27.109-51-7
moved all system.img, system_b.img, and oem.img FROM TMOBILE TO SPRINT
flashall the new franken SPRINT package
make sure you wipe (fastboot -w)
Now you can root and sim unlock if you havent already done so. Hopefully this works for everyone like it has for me.
I will be making a full package with all of this, but it'll take me a couple hours to compress and upload. Just got super excited because it seems lots of people are having this issue and there aren't any solutions. Please let me know if this works, and I'll try to steadily improve this post.
Click to expand...
Click to collapse
Question, why not just use tmobile or is there some issue with that. Anyway, does the end result still end with sprint bloatware?
xellos2099 said:
Question, why not just use tmobile or is there some issue with that. Anyway, does the end result still end with sprint bloatware?
Click to expand...
Click to collapse
The tmobile rom either has either broken wifi or network. There is no sprint bloat because it is using the tmobile system and oem images. You get some tmobile "bloat" but its pretty clean. I'm assuming that it ends up being virtually identical to a tmobile z2 force, but on a sprint z2 force, with everything working, as far as I can tell.
I recall someone on slickdeal mentioned this method. Can we get in trouble if tmobile detected this since our imei will not match their? Either i got both file already. Do i flashall first and then fastboot -w? or is it we go to boot loader, run fastboot -w and then we use the flashall.bat
xellos2099 said:
I recall someone on slickdeal mentioned this method. Can we get in trouble if tmobile detected this since our imei will not match their? Either i got both file already. Do i flashall first and then fastboot -w?
Click to expand...
Click to collapse
I can't imagine why t-mobile could/would possibly care enough to even expend the money to look, but I suppose anything is possible.
fastboot -w just clears the user data (factory reset), before or after is fine, most scripts do it anyways.
I saw the deal on slickdeals, but haven't seen anyone do this, if I am wrong I will certainly give credit where it is due. I just got the idea because I saw someone flashing just the NON-HLOS (LTE radio i think).
robertzas said:
I can't imagine why t-mobile could/would possibly care enough to even expend the money to look, but I suppose anything is possible.
fastboot -w just clears the user data (factory reset), before or after is fine, most scripts do it anyways.
I saw the deal on slickdeals, but haven't seen anyone do this, if I am wrong I will certainly give credit where it is due. I just got the idea because I saw someone flashing just the NON-HLOS (LTE radio i think).
Click to expand...
Click to collapse
It is a pretty interesting idea, flash mine using your method atm since a bit sick of sprint bloatware
---------- Post added at 06:15 AM ---------- Previous post was at 05:59 AM ----------
robertzas said:
I can't imagine why t-mobile could/would possibly care enough to even expend the money to look, but I suppose anything is possible.
fastboot -w just clears the user data (factory reset), before or after is fine, most scripts do it anyways.
I saw the deal on slickdeals, but haven't seen anyone do this, if I am wrong I will certainly give credit where it is due. I just got the idea because I saw someone flashing just the NON-HLOS (LTE radio i think).
Click to expand...
Click to collapse
I used your method but under software variant it is still sprint
xellos2099 said:
It is a pretty interesting idea, flash mine using your method atm since a bit sick of sprint bloatware
---------- Post added at 06:15 AM ---------- Previous post was at 05:59 AM ----------
I used your method but under software variant it is still sprint
Click to expand...
Click to collapse
Ok... Does wifi calling work? Does volte work? Do you just have the minimal t-mobile app package and no sprint garbage? If not, I uploaded a pre-hacked zip at the top post.
robertzas said:
Ok... Does wifi calling work? Does volte work? Do you just have the minimal t-mobile app package and no sprint garbage? If not, I uploaded a pre-hacked zip at the top post.
Click to expand...
Click to collapse
Updating. It still having the Sprint calling plus app and calling id.
I have looked all over XDA and tried multiple processes to get the Sprint branded Moto Z2 to work on T Mobile and this works perfectly. So far WiFi calling is working and the phone seems stable.
jajflash said:
I have looked all over XDA and tried multiple processes to get the Sprint branded Moto Z2 to work on T Mobile and this works perfectly. So far WiFi calling is working and the phone seems stable.
Click to expand...
Click to collapse
Does your software variant say tmobile or sprint now? for me maybe i did somethign wrong but mine still have callling plus and calling id and wificalling nto showing up
xellos2099 said:
Does your software variant say tmobile or sprint now? for me maybe i did somethign wrong but mine still have callling plus and calling id and wificalling nto showing up
Click to expand...
Click to collapse
It actually has the T Mobile branding and T Mobile apps. I even did a factory reset and the T Mobile apps remained. I was able to transfer the system.img files, system_b.img files and the OEM.img file. I used the NASH_SPRINT_OCX27.109-48 batch file to execute the update.
xellos2099 said:
Does your software variant say tmobile or sprint now? for me maybe i did somethign wrong but mine still have callling plus and calling id and wificalling nto showing up
Click to expand...
Click to collapse
Yea you def did something wrong, just download the package I uploaded and just run the flashall.bat in there
jajflash said:
It actually has the T Mobile branding and T Mobile apps. I even did a factory reset and the T Mobile apps remained. I was able to transfer the system.img files, system_b.img files and the OEM.img file. I used the NASH_SPRINT_OCX27.109-48 batch file to execute the update.
Click to expand...
Click to collapse
Since it seems like you are having success, I haven't been able to get magisk working on this, it keeps bootlooping. I could very well be doing something wrong.
robertzas said:
Since it seems like you are having success, I haven't been able to get magisk working on this, it keeps bootlooping. I could very well be doing something wrong.
Click to expand...
Click to collapse
I have not tried Magisk yet. I just installed TWRP and tested the phone on TMobile. I will try and see if it works.
robertzas said:
Since it seems like you are having success, I haven't been able to get magisk working on this, it keeps bootlooping. I could very well be doing something wrong.
Click to expand...
Click to collapse
Wait how did you unlocked the phone without magisk?
xellos2099 said:
Wait how did you unlocked the phone without magisk?
Click to expand...
Click to collapse
Unlocking the bootloader is one thing, rooting with magisk isnt inconsiderate "unlocking"
Sent from my SM-G965U using Tapatalk
shook187 said:
Unlocking the bootloader is one thing, rooting with magisk isnt inconsiderate "unlocking"
Sent from my SM-G965U using Tapatalk
Click to expand...
Click to collapse
I meant the sim unlock
robertzas said:
I just got one of the z2 force on the sprint deal, but am on t-mobile. I need wifi calling at work and abroad, so no wifi calling is a showstopper. I flashed a bunch of the "flashall" packages but kept getting issues like no wifi, no network, or on sprint no wifi calling. So I just tried frankensteining a package together, and miraculously it seems to be working!!
Click to expand...
Click to collapse
Any chance you have tried playing with the retail rom that can be found here : https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/?
shadowcliffs said:
Any chance you have tried playing with the retail rom that can be found here : https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/?
Click to expand...
Click to collapse
No, but I bet you can probably do the same thing. Start with newest Sprint package, copy over all the system.img, system_b.img, and oem.img from the retail rom the Sprint rom and flashall.
xellos2099 said:
I meant the sim unlock
Click to expand...
Click to collapse
Sim unlock and bootloader unlock persists through flashing. Since I can't get magisk working on this, I'll change the directions to reflect that.