I flashed the t-mobile flashall on my AT&T Z2 and attempted to return to AT&T stock. Now I have no wifi or cellular and fastboot shows "Baseband: <not found> and attempting to punch in the imei code in the dialer causes the app to crash. I can flash the tmo modem and get wifi back, but no cellular, rendering the phone useless. I've attempted to use the moto smart assistant app to run a rescue but that just breaks things again and makes wifi and cellular inoperable.
Is there any way to fix this?
ohht said:
I flashed the t-mobile flashall on my AT&T Z2 and attempted to return to AT&T stock. Now I have no wifi or cellular and fastboot shows "Baseband: <not found> and attempting to punch in the imei code in the dialer causes the app to crash. I can flash the tmo modem and get wifi back, but no cellular, rendering the phone useless. I've attempted to use the moto smart assistant app to run a rescue but that just breaks things again and makes wifi and cellular inoperable.
Is there any way to fix this?
Click to expand...
Click to collapse
I'm surprised it let you flash the tmo image. I guess as long as it's signed for an xt1789 device it doesn't care?
pitchdarkice said:
I'm surprised it let you flash the tmo image. I guess as long as it's signed for an xt1789 device it doesn't care?
Click to expand...
Click to collapse
It didn't exactly flash the whole image, just the bootloader and the modem. It booted into the AT&T rom with a T-Mobile splash screen.
My best guess is that because tmo is on a newer version of the modem package, downgrading to the older one on the att rom is causing my issue. I'm really frustrated because I've turned my brand new phone into a glorified ipod touch until I find a solution. Not to mention I discovered that att hasn't enabled wifi calling on the stock rom yet which renders the phone pretty-much useless for me anyway.
ohht said:
It didn't exactly flash the whole image, just the bootloader and the modem. It booted into the AT&T rom with a T-Mobile splash screen.
My best guess is that because tmo is on a newer version of the modem package, downgrading to the older one on the att rom is causing my issue. I'm really frustrated because I've turned my brand new phone into a glorified ipod touch until I find a solution. Not to mention I discovered that att hasn't enabled wifi calling on the stock rom yet which renders the phone pretty-much useless for me anyway.
Click to expand...
Click to collapse
I have an at&t z2 force that has the exact issue. Earlier this year I made a mistake and flashed the tmobile modem, tried going back to at&t and ended up with a tiny tablet like you. Every new security patch from at&t I try and flash, and every time the same result as yours - no baseband. Flash back to a tmobile modem for wifi and wait... Hopefully they get Pie and it will become a functioning phone once again.
I liked the phone so I ended up getting a sprint version (lesson learned about locked bootloaders), and the at&t mini tablet sits attached to my jbl soundboost for some sleeping white noise and alarm clock.
Not what you wanted to hear, but you're not alone. Maybe with the $99 sale recently on the at&t version increasing ownership someone will find a way past the locked bootloader and give us hope, but I'm not holding my breath.
cubalis said:
I have an at&t z2 force that has the exact issue. Earlier this year I made a mistake and flashed the tmobile modem, tried going back to at&t and ended up with a tiny tablet like you. Every new security patch from at&t I try and flash, and every time the same result as yours - no baseband. Flash back to a tmobile modem for wifi and wait... Hopefully they get Pie and it will become a functioning phone once again.
I liked the phone so I ended up getting a sprint version (lesson learned about locked bootloaders), and the at&t mini tablet sits attached to my jbl soundboost for some sleeping white noise and alarm clock.
Not what you wanted to hear, but you're not alone. Maybe with the $99 sale recently on the at&t version increasing ownership someone will find a way past the locked bootloader and give us hope, but I'm not holding my breath.
Click to expand...
Click to collapse
Just a heads up, but I turned my phone on today to see it trying to install updates. The update wouldn't complete, so I used the Moto Smart Assistant app to install the update and when I booted back into android I now have cellular service again and a new baseband version. Looks like att finally updated their baseband to a newer version than the tmobile one!
In summary, WOOHOO I didn't waste $100!
Ok, two years later, but I had the same problem today on my Moto Z2 Force XT1789-4 (AT&T).
After a a lot of reading, and a lot of failing, I realized that to correct this I have to flash NON-HLOS.bin and fsg.mbn from a NEWER ROM.
In the end I used the files from XT1789-05 Pie Rom, and my Baseband returned.
douglascs77 said:
Ok, two years later, but I had the same problem today on my Moto Z2 Force XT1789-4 (AT&T).
After a a lot of reading, and a lot of failing, I realized that to correct this I have to flash NON-HLOS.bin and fsg.mbn from a NEWER ROM.
In the end I used the files from XT1789-05 Pie Rom, and my Baseband returned.
Click to expand...
Click to collapse
I wouldn't recommend this to anyone. Once you flash a pie modem you can't go back, more so flashing a variant not intended for your phone is often the cause of these problems. ATT is a locked bootloader, so you're limited to what you can flash, and when things go wrong it is extremely difficult to solve those problems because of the locked bootloader, and most times it remains so. Not only that, you're not very specific as to what you're actually using, what your system is, and what carrier you're using. -05 covers a few different countries and modems and US modems tend to be very specific. Not trying to be an ass, but you need to offer a lot of info and specifics about your setup otherwise people might blindly flash some pie modem and that'll be the end of it.
douglascs77 said:
Ok, two years later, but I had the same problem today on my Moto Z2 Force XT1789-4 (AT&T).
After a a lot of reading, and a lot of failing, I realized that to correct this I have to flash NON-HLOS.bin and fsg.mbn from a NEWER ROM.
In the end I used the files from XT1789-05 Pie Rom, and my Baseband returned.
Click to expand...
Click to collapse
Can u update to android 10?
henrywhtin said:
Can u update to android 10?
Click to expand...
Click to collapse
Unfortunately, Motorola do not gave me an unlock code for my phone.
I'm pissed about this. I'm stuck to Android Oreo. My Moto G5 has Pixel Experience Android 10 rom, it's an amazing upgrade.
Related
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
GraphicsApathy said:
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
Click to expand...
Click to collapse
Can you go to your phone's settings => about device and check what the firmware settings are? Let's see what you have under firmware version, baseband version & build number. If possible, you may post a screen shot. Did you say you returned to stock by wiping your phone? Hardly seems likely and you would have probably needed to flash some firmware. Would you recall what you flashed?
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
GraphicsApathy said:
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
Click to expand...
Click to collapse
It's definitely on AT&T firmware. Apologies if I sound like I'm doubting you but are you certain it had T-Mobile firmware when you acquired it? I'd guess it was probably already an AT&T phone. If you bought it in the secondary market, there could have been some previous repairs involving parts swaps. Your safest bet may be to leave it as is and unlock for you use on T-Mobile. Trying to force on T-Mobile firmware now could result in a brick. As it is on 4.1.1, you can easily free unlock it by following the well tested method you'll find elsewhere in this forum.
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
GraphicsApathy said:
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
Click to expand...
Click to collapse
There could have been a previous JTag operation involving forced firmware installation on the MB. I've seen previous hybrid firmware involving one or other partition belonging to a different model - e.g. the modem, bootloader or something else but not the complete system.
Yes, that's the unlock method I was referring to. You won't get any confirmation that the process worked at the end. However, if you did it correctly, you would know it worked when you insert a non-compatible SIM card and it works. You should also be able to install T-Mobile apps especially the Wi-Fi calling app which is a really nice feature of T-Mobile.
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
UPDATE: Successfully obtained and installed T-Mobile microSIM. Still wish to replace AT&T boot animation and bloatware with T-Mobile's, though.
GraphicsApathy said:
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
Click to expand...
Click to collapse
OK. I'd be interested in knowing the outcome but I'll be surprised if it isn't unlocked already. Did some further research and there have been some reports of people successfully 'flashing' AT&T firmware on T-Mobile phones, and vice versa. Not sure why this should happen and conventional logic suggests the result should be a hard brick which is indeed the most common outcome. I'll also suggest you boot into download mode and see the information under bootloader. If the device has a T-Mobile bootloader, it may be possible to remove the OS via custom recovery and re-flash T-Mobile firmware.
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
GraphicsApathy said:
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
Click to expand...
Click to collapse
If download mode info shows secure bootloader enabled, the phone is, to all intents and purposes, now an AT&T phone. Attempting to flash T-Mobile firmware may likely result in a brick which would require a JTag fix. I was hoping download mode would show it still had a T-Mobile bootloader which could have allowed for safe firmware installation but this does not appear to be the case. Likely the motherboard was previously replaced or it suffered a brick and AT&T firmware was JTagged on. Either way, it would be safer to leave it as is.
Bummer. I'll leave it as is then. Thank you for all the help.
I decided to try the latest U-firmware on my G930V. I had issues with previous G930U builds having SMS/MMS issues. I gave PL2 a shot yesterday and I've been really happy with it. The phone is very snappy and everything works as designed. Verizon visual voicemail can't be used, but it's not a huge deal. VoLTE works well. You can download My Verizon from the Play Store. I'd highly recommend this firmware compared to the previous builds. Make sure to enable the Verizon APN in APN settings after install.
I'd like to note that my phone is completely stock at this point, NOT ROOTED, so I didn't need to apply any fixes to make things work. You should be able to root without issue if that's your thing.
Downloading the firmware from Sammobile takes FOREVER, so I uploaded it to my AFH account to cut down on that download time for you guys.
G930UUEU4APL2
Backup using Smart Switch, then use Odin and flash ALL 4 files. Do yourself a favor and don't use HOME_CSC. It'll make things much smoother if you don't.
Let me know if anyone runs into any issues. I know in the past, some have had great experience with the U-firmware and others had issues with no reception. I want to see if the same holds true for this build.
Is this update in January?
Update: Yup, I took it last month and everything was OK. I am on Verizon Rom now just expecting it receives Nougat earlier than U furmware, which updates quarterly.
https://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930uueu4apl2-sm-g930u-t3535230
torr310 said:
Is this update in January?
Update: Yup, I took it last month and everything was OK. I am on Verizon Rom now just expecting it receives Nougat earlier than U furmware, which updates quarterly.
Click to expand...
Click to collapse
I was hoping Verizon would see the official Nougat by this point. I liked the feel of the U-firmware, but reception was a problem for me on Verizon. I decided I'd give the latest U-firm a shot since waiting for official Verizon Nougat seems like a lost cause at this point. I'll stay with this until Nougat is officially released. This firmware is the December update, and since they update it quarterly, an update should be around the corner. Maybe the next U-firmware will be Nougat. I think Nougat-U would be damn near flawless lol.
I've been running it since beginning of January no Issues
What exactly are the benefits of flashing this? Do I get 7.0? How is the reception? What are the cons?
I have a pretty big problem. I attempted flashing the 4 files with Odin 3.09. After a couple of seconds the operation terminated and now my GS7 is stuck in a bootloop. Whats worse is that when i attempted to boot into recovery, now it shows a blue screen with the android logo that says "installing system update" for about 2 seconds then shuts off, then tries again. Does anyone know how to fix this, at least so I can flash stock back on it?
Update: Fixed it, was able to get into download mode and use odin to flash stock. The flash failed but it was able to trip the OS and recovery back to normal for some reason.
Nobiscis said:
What exactly are the benefits of flashing this? Do I get 7.0? How is the reception? What are the cons?
Click to expand...
Click to collapse
No carrier bloat and a very smooth OS. The reception is great. The cons are that you don't get any of the carrier features, like WiFi calling, visual voicemail, ect.
xlectik67 said:
I have a pretty big problem. I attempted flashing the 4 files with Odin 3.09. After a couple of seconds the operation terminated and now my GS7 is stuck in a bootloop. Whats worse is that when i attempted to boot into recovery, now it shows a blue screen with the android logo that says "installing system update" for about 2 seconds then shuts off, then tries again. Does anyone know how to fix this, at least so I can flash stock back on it?
Update: Fixed it, was able to get into download mode and use odin to flash stock. The flash failed but it was able to trip the OS and recovery back to normal for some reason.
Click to expand...
Click to collapse
Odin 3.9 might be too old. I've used Odin 3.11 or higher on the S7 and have never had any issues.
thanks to you it works perfectly but HOME_CSC failed and caused recovery bootloop after that i tried other CSC and it was successful. I've got very upset on V firmware because they deleted a lot of features on galaxy S7. they are worst
CVertigo1 said:
I decided to try the latest U-firmware on my G930V. I had issues with previous G930U builds having SMS/MMS issues. I gave PL2 a shot yesterday and I've been really happy with it. The phone is very snappy and everything works as designed. Verizon visual voicemail can't be used, but it's not a huge deal. VoLTE works well. You can download My Verizon from the Play Store. I'd highly recommend this firmware compared to the previous builds. Make sure to enable the Verizon APN in APN settings after install.
I'd like to note that my phone is completely stock at this point, NOT ROOTED, so I didn't need to apply any fixes to make things work. You should be able to root without issue if that's your thing.
Downloading the firmware from Sammobile takes FOREVER, so I uploaded it to my AFH account to cut down on that download time for you guys.
G930UUEU4APL2
Backup using Smart Switch, then use Odin and flash ALL 4 files. Do yourself a favor and don't use HOME_CSC. It'll make things much smoother if you don't.
Click to expand...
Click to collapse
I'm still having issues with this latest firmwire. I do get LTE but not network connection. I still have circle with a line through it indicating that I don't have service. the service will come on for a second and then cut out. Service is called "123456".
Did you choose the APN to use? If you are using a Verizon SIM card, then it should give you the option to use Verizon, but you need to select it.
CVertigo1 said:
Did you choose the APN to use? If you are using a Verizon SIM card, then it should give you the option to use Verizon, but you need to select it.
Click to expand...
Click to collapse
So there's APN settings and Network Operators. I'm actually using a verizon MVNO called boom mobile. If I selected "verizon" network, I get a notification that says " no service - selected netweork verizon not available". The other one's that show up from the selection are ATT, T mobile, and some 310830 thing. None of them work. I use automatic network detection.
As far as APN settings, I do use Verizon and I get LTE data from that. I just don't get the phone service connection.
matase said:
So there's APN settings and Network Operators. I'm actually using a verizon MVNO called boom mobile. If I selected "verizon" network, I get a notification that says " no service - selected netweork verizon not available". The other one's that show up from the selection are ATT, T mobile, and some 310830 thing. None of them work. I use automatic network detection.
As far as APN settings, I do use Verizon and I get LTE data from that. I just don't get the phone service connection.
Click to expand...
Click to collapse
Hmmm. This is passed my level of experience then. I'm only familiar with setting up and using authentic Verizon service. I can't speak for other services that use Verizon's network.
Install PL2 from PI3?
CVertigo1 said:
I decided to try the latest U-firmware on my G930V. I had issues with previous G930U builds having SMS/MMS issues. I gave PL2 a shot yesterday and I've been really happy with it. The phone is very snappy and everything works as designed. Verizon visual voicemail can't be used, but it's not a huge deal. VoLTE works well. You can download My Verizon from the Play Store. I'd highly recommend this firmware compared to the previous builds. Make sure to enable the Verizon APN in APN settings after install.
I'd like to note that my phone is completely stock at this point, NOT ROOTED, so I didn't need to apply any fixes to make things work. You should be able to root without issue if that's your thing.
Downloading the firmware from Sammobile takes FOREVER, so I uploaded it to my AFH account to cut down on that download time for you guys.
G930UUEU4APL2
Backup using Smart Switch, then use Odin and flash ALL 4 files. Do yourself a favor and don't use HOME_CSC. It'll make things much smoother if you don't.
Click to expand...
Click to collapse
Sorry for a newbie question. Can I install this firmware from a verizon PI3 firmware? Thanks in advance!
pboy said:
Sorry for a newbie question. Can I install this firmware from a verizon PI3 firmware? Thanks in advance!
Click to expand...
Click to collapse
Yes you can.
Thank you for sharing your experience. I was looking into flashing the U firmware for a while and I finally pulled a trigger after seeing this thread.
Everything works well on Verizon and it feels great to have a clean phone & freedom to switch. I think it's worth waiting a little more for Nougat.
p.s. Anyone has an idea on when official G930U Nougat will be released?
Will this work for my AT&T S7 on PJ4 firmware?
jOdin3
hey guys,
this is the first non-nexus phone i've used, and I am excited about flashing the U firmware to get a clean stock experience on my g930v. I was wondering what files i should input in jOdin under the PDA/Bootloader/CSC/Phone fields after I extract the zip file SM-G930U? I have searched tried to watch some insufferable youtube videos on the matter have had no luck finding an answer. Also since I'm asking, is it possible to flash this firmware with jOdin3, sorry for the newbie questions, didn't know where else to go.
Thanks in advance to any helpful replies.
Solved the above, no need for replies.
Next though is when I try and flash using Jodin3 the pit file is acquired, the phone reboots and then it stays disconnected and I am unable to start the process after the phone reboots. Any suggestions?
Solved the above by using heimdall to extact pit.
I am close to giving up and flashing anything via jOdin3 I have tried pretty much everything to flash new firmware with no success, latest error is that there is a corrupt file, need to use Odin file...
HAS ANYONE had success flashing a Verizon S7 on macOS? if so please tell me where to go.
How can I get 930u to 930v?
jerecole2378 said:
How can I get 930u to 930v?
Click to expand...
Click to collapse
Flash the Verizon firmware from the Verizon threads
Right now you can flash official T-mobile nougat rom for Verizon galaxy s7 (G930V). It's seem everything work fine. Here's how to do that:
- Download official T-mobile nougat rom from updato.com (search for T-mobile nougat rom by enter "G930T" in search field - sorry I cannot post link because of XDA's policies)
- Flash rom to galaxy s7 G930V with odin (like any other 6.0 roms)
Done! Now we have final Nougat on Verizon Galaxy S7 G930V
I've been seeing threads on this and the G930U firmware working as well. Has anyone else tried the tmobile rom this way? No root?
You can flash any rom to any snapdragon S7 as long as you match the correct model. ie don't flash Edge firmware on a regular S7.
Does LTE and VoLTE still work after flashing the tmo rom?
hiepcn said:
Right now you can flash official T-mobile nougat rom for Verizon galaxy s7 (G930V). It's seem everything work fine. Here's how to do that:
- Download official T-mobile nougat rom from updato.com (search for T-mobile nougat rom by enter "G930T" in search field - sorry I cannot post link because of XDA's policies)
- Flash rom to galaxy s7 G930V with odin (like any other 6.0 roms)
Done! Now we have final Nougat on Verizon Galaxy S7 G930V
Click to expand...
Click to collapse
I'm actually pretty excited about doing it this way... Are there any downfalls to flashing the T-Mobile ROM? LTE still working data working no dropped calls? Considering flashing over to this when I get off of work anyway just to try it out would like to know if anyone can confirm everything will still work
Don't we have to flash the verizon csc
If you flash the TMOBILE rom your phone will not work with Verizon and you most likely will not be able to flash back to Verizon until there is a Verizon nougat factory image. With the S7 you cannot flash back to an older bootloader and I would think the TMOBILE nougat rom has a newer bootloader.
nrage23 said:
If you flash the TMOBILE rom your phone will not work with Verizon and you most likely will not be able to flash back to Verizon until there is a Verizon nougat factory image. With the S7 you cannot flash back to an older bootloader and I would think the TMOBILE nougat rom has a newer bootloader.
Click to expand...
Click to collapse
I flashed t-mobile rom on my S7 G930V and seemed everything works fine. But I'm not in US to try some Verizon features. I then flashed back to G930U rom on my S7.
hiepcn said:
I flashed t-mobile rom on my S7 G930V and seemed everything works fine. But I'm not in US to try some Verizon features. I then flashed back to G930U rom on my S7.
Click to expand...
Click to collapse
Did it still show as verizon
---------- Post added at 03:10 AM ---------- Previous post was at 02:48 AM ----------
BigZ1990420 said:
I'm actually pretty excited about doing it this way... Are there any downfalls to flashing the T-Mobile ROM? LTE still working data working no dropped calls? Considering flashing over to this when I get off of work anyway just to try it out would like to know if anyone can confirm everything will still work
Click to expand...
Click to collapse
I was reading the s7 edge forum. They have a 5th file called boot recovery image file tar. Do we not need that one also. Just asking before I flash this
I think it might be helpful if I address a few things. After using this image for about a day, I decided to go back to the U firmware
- Cellular does not work (duh). Renders the "phone" aspect useless.
- The T-Mobile logo is sickening
- Reverting back to stock is very simple. Just flash the V or U firmware and you're good to go. Same process as flashing the T firmware.
Nobiscis said:
I think it might be helpful if I address a few things. After using this image for about a day, I decided to go back to the U firmware
- Cellular does not work (duh). Renders the "phone" aspect useless.
- The T-Mobile logo is sickening
- Reverting back to stock is very simple. Just flash the V or U firmware and you're good to go. Same process as flashing the T firmware.
Click to expand...
Click to collapse
Agreed. I flashed this last night, and I must say the official nougat really looks and feels a lot smoother and prettier than the beta. LOL but I agree to a certain point about the mobile cellular network not working only mine was working, I just had terrible cell signal... And only connected to 3G. No LTE. Also wasn't showing my network, network name was 12345678 lol moral of the story I reverted back lol.
On a side note yes you can flash back to the Verizon firmware. I flash back to the API3 and then back to the nougat beta from there. Smart switched everything back and it's like I never left. Lol
BigZ1990420 said:
Agreed. I flashed this last night, and I must say the official nougat really looks and feels a lot smoother and prettier than the beta. LOL but I agree to a certain point about the mobile cellular network not working only mine was working, I just had terrible cell signal... And only connected to 3G. No LTE. Also wasn't showing my network, network name was 12345678 lol moral of the story I reverted back lol.
On a side note yes you can flash back to the Verizon firmware. I flash back to the API3 and then back to the nougat beta from there. Smart switched everything back and it's like I never left. Lol
Click to expand...
Click to collapse
You see, I couldn't even use the Nougat Beta! My cellular doesn't work on the nougat beta for some reason
BigZ1990420 said:
Agreed. I flashed this last night, and I must say the official nougat really looks and feels a lot smoother and prettier than the beta. LOL but I agree to a certain point about the mobile cellular network not working only mine was working, I just had terrible cell signal... And only connected to 3G. No LTE. Also wasn't showing my network, network name was 12345678 lol moral of the story I reverted back lol.
On a side note yes you can flash back to the Verizon firmware. I flash back to the API3 and then back to the nougat beta from there. Smart switched everything back and it's like I never left. Lol
Click to expand...
Click to collapse
I just installed the t mobile firmware last night and everything worked fine since then, cellular signal strong, 4G data strong as usual, everythibg works smoothly than U firmware also debloat the t.mobile stuff and almost get a stock firmware. Give a try the T firnware.
albertordzcz said:
I just installed the t mobile firmware last night and everything worked fine since then, cellular signal strong, 4G data strong as usual, everythibg works smoothly than U firmware also debloat the t.mobile stuff and almost get a stock firmware. Give a try the T firnware.
Click to expand...
Click to collapse
Now that I think about it I didn't flash the CSC file because I read somewhere that it would not work with a Verizon (MNVO) sim
BigZ1990420 said:
Now that I think about it I didn't flash the CSC file because I read somewhere that it would not work with a Verizon (MNVO) sim
Click to expand...
Click to collapse
Not using verizon, i live in Mexico and using movistar i really love this nougat update and hope the U nougat be ready to stsrt roll out and no bloatware at all! xD
I wonder when/if the official update comes out, will it work with Gear VR? I understand the "betas" do not work with the Samsung Gear VR under Nougat. Just curious.
want to flash firmware on verizon s7 to enable Wifi Calling
albertordzcz said:
I just installed the t mobile firmware last night and everything worked fine since then, cellular signal strong, 4G data strong as usual, everythibg works smoothly than U firmware also debloat the t.mobile stuff and almost get a stock firmware. Give a try the T firnware.
Click to expand...
Click to collapse
Did you have Wifi Calling after installing new firmware? I got a S7 (SM-G390V) on verizon and switched carriers to tmobile, however i can't send/receive images in text. "wifi calling" has been disabled by evil verizon (doesn't appear)..... i want to flash the firmware to enable it to "hopefully" solve my issue. Just wondering if that will appear afterwards....
constructicon said:
Did you have Wifi Calling after installing new firmware? I got a S7 (SM-G390V) on verizon and switched carriers to tmobile, however i can't send/receive images in text. "wifi calling" has been disabled by evil verizon (doesn't appear)..... i want to flash the firmware to enable it to "hopefully" solve my issue. Just wondering if that will appear afterwards....
Click to expand...
Click to collapse
Hi, no wifi callig, and send /receive images in normal text not working also :/
need Wifi calling on verizon s7 (carrier tmobile)
albertordzcz said:
Hi, no wifi callig, and send /receive images in normal text not working also :/
Click to expand...
Click to collapse
ugh...ok. i thought that putting tmobile rom on verizon s7 would display/enable that feature (apps/setting/advanced calling)....need to find another solution for mms images
If i was one of you on the flat screen version i would flash the CSC file and the boot recovery image file from the S7 Edge setup and follow directions there. What can it hurt? If it doesn't work you just oden back to whatever you want. You cant use it as it is anyways as you have no real Verizon data with out those files. It's soo much better than the beta! Only thing i haven't got is WiFi calling and visual voice mail.
I have a Sprint Moto Z2F on Verizon network.
With the Sprint Firmware I’m roaming on VzW network
I can’t get any version of the VzW firmware past the set-up stage, (Set-up keeps closing)
I did get a mixed version of Sprint and VzW firmware to work and set-up but I have no WiFi.
All the System oem img (sparsechunk) files are VzW 9/1/2018 update and the rest of the firmware files are Sprint.
What firmware file controls the WiFi?
I'd like to get WiFi working again
ok this phone is crazy!!!!
I'm back on the Sprint firmware, which works fine its just roaming and that bugs me.
3 times now I did Flashall back to Sprint FW and take the July update. then I install TWRP and Root and I'm back on May 1 update. Crazy.
now I just booted the B slot and it is updated to July first...
I still want to get the Verizon firmware to work, I know others have.
I have tried a few Custom Roms, LOS and DU but can't get them to boot. I can get LOS to boot but I have no data.
TwoBuells said:
ok this phone is crazy!!!!
I'm back on the Sprint firmware, which works fine its just roaming and that bugs me.
3 times now I did Flashall back to Sprint FW and take the July update. then I install TWRP and Root and I'm back on May 1 update. Crazy.
now I just booted the B slot and it is updated to July first...
I still want to get the Verizon firmware to work, I know others have.
I have tried a few Custom Roms, LOS and DU but can't get them to boot. I can get LOS to boot but I have no data.
Click to expand...
Click to collapse
Flash all with sprint. Download latest Verizon flash all and just flash system, oem, and boot. Let me know how it works. I did that with the AT&T firmware and it runs great
Forgot the image. LTE. WiFi calling. Everything at&t works
OK, I got WiFi and VzW 4G LTE NOT ROAMING !!!
I flashall ‘d the Sprint FW, then I did a little edit on the Flashall.bat and just flashed the VzW OEM, Boot and System sparsechunk files, 11 files in all. So I didn’t have to take an update I used the Sept 1 VzW updated firmware. Now all I have to do is flash TWRP and root.
thanks
update: I've been using the phone as my daily for over a week and everything runs fine.
What are the chances that LOS could be made to work? I just bought a Verizon Z2 off eBay not realizing that the bootloader could not be unlocked. I've been on AT&T but their service isn't too great around here.
If there's a chance LOS could work I'll sell this phone on eBay and get a Sprint variant.
I always flash global image instead of Verizon due to bloat ware and stuff.. I did have a question would it be worth grabbing the Verizon radio images and flashing them as I'm on the Verizon network? Also do you flash them with adb or is there another method? So used to having TWRP.. Much appreciated.
I never flash the VZW image......but you can certainly try the radio as you suggest. Normally, I never see any difference, but curious if others see some....the radio is different in the current VZW image.
You would do "fastboot flash radio radio_imagefile_here"
stalls said:
I always flash global image instead of Verizon due to bloat ware and stuff.. I did have a question would it be worth grabbing the Verizon radio images and flashing them as I'm on the Verizon network? Also do you flash them with adb or is there another method? So used to having TWRP.. Much appreciated.
Click to expand...
Click to collapse
What bloatware (and stuff) are you referring to regarding the VZW image?
stalls said:
I always flash global image instead of Verizon due to bloat ware and stuff.. I did have a question would it be worth grabbing the Verizon radio images and flashing them as I'm on the Verizon network? Also do you flash them with adb or is there another method? So used to having TWRP.. Much appreciated.
Click to expand...
Click to collapse
The Verizon firmware isn't a "Verizon owned" firmware, it's just a variant that Google has released because when Google sent out the "global" firmware for testing Verizon reported issues with it, and it was too late to incorporate the fixes and send out another firmware to all carriers for testing.
The variants in firmwares have nothing changed in them other than the radio/modem/network files and maybe app versions if the variant had to be built at a later date and picked up a new app version in the build process. The firmwares are exactly the same. They don't come with any additional bloatware, because Verizon's networking specific apps are actually already included in the base firmware and are enabled/disabled on the presence of a Verizon SIM. The bloatware you are delivered is when setting up the phone and the setup wizard will offer the carrier bloatware to be installed depending on the carrier of the SIM.
Run the firmware designated for your carrier. You might have service issues if you don't, but it will run almost the same.
I ran the Verizon variant on my phone with T-Mobile and I got service just fine, however it appears that Verizon wanted the scaling for network strength to be changed because it reported 0 bars even though I had service. It also wanted to try really hard to latch onto mmWave, so it appears that Verizon wanted that and potentially more changed.
Just run the online flash tool from Google to get updated, or follow the tutorial threads in the help section.
cmh714 said:
I never flash the VZW image......but you can certainly try the radio as you suggest. Normally, I never see any difference, but curious if others see some....the radio is different in the current VZW image.
You would do "fastboot flash radio radio_imagefile_here"
Click to expand...
Click to collapse
You'll have to flash more. There's also the modem inside the image and there are also APNs and other files for networks on the system image or vendor image too, so it's really just best to take the whole firmware.
Ok so I should just flash over the global and so as usual then right?
stalls said:
Ok so I should just flash over the global and so as usual then right?
Click to expand...
Click to collapse
You mean flash the Verizon firmware over the global firmware you already have on your phone? Yes, it will be fine. You don't need to wipe the phone.