Related
if the camere dosen't work how we know that the software or the hard ware that dosen't work???
Not to sound rude, but please, use Google Translator.... www.translate.google.com
If its hardware, it (your camera lens) may make more than the usual three click metallic noise when you open the camera app, but the best way to know if its software is to check your roms developer page, in the event your running stock, (meaning you haven't rooted yet) it likely isn't software related, though it may be if you recently let it ota upgrade. In any event, if you can't find documentation, take it to your verizon store, they may not know how to fix it, but they know how to get you a new one, or god willing an upgrade (btw if your able to upgrade, I recommend the Samsung Fascinate, if only because it can be overclocked to 1.6ghz.)
hey guys im new on this wp8 forum (old android user) i bought an ativ S from a dude i met once... i knew this had a problem with the camera, i just realized that the back camera is the only one with the problem, ive been reading posts and i tried everything to make it work, but i allways got the same, it doesnt start correctly, i press the camera button or use the camera icon, but its allways the same, the 1st start its like it close so quickly at the 2nd try it keep the screen black, i only see the icons, and an arrow to swipe and see the pics i toke (with the front camera and a 3rd party app) but it close in around 10 seconds... idk what to do... i tought maybe was something about and update (a past one) but few days ago i got an update (not grd2, a minor one) but nothing... i still have the problem... what do you guys think... its a hardware problem or maybe software?... ireally love this cellphone and i dont wanna stop using it
If third-party apps can use the main (rear) camera, then it's not a hardware problem; you could try hard-resetting the phone and seeing if that helps.
If even third-party apps can't use the rear camera, it's either a hardware or firmware problem. Since this is the first I've heard of you particular issue, and since an update didn't fix it, that suggests a hardware problem (it *could* be firmware if you have some weird non-stock firmware on there; what version info do you have in settings->about->more info?). If it's a hardware problem, replacing the phone (or just living with the meh but usable front-facing camera, I guess) is your only real option.
GoodDayToDie said:
If third-party apps can use the main (rear) camera, then it's not a hardware problem; you could try hard-resetting the phone and seeing if that helps.
If even third-party apps can't use the rear camera, it's either a hardware or firmware problem. Since this is the first I've heard of you particular issue, and since an update didn't fix it, that suggests a hardware problem (it *could* be firmware if you have some weird non-stock firmware on there; what version info do you have in settings->about->more info?). If it's a hardware problem, replacing the phone (or just living with the meh but usable front-facing camera, I guess) is your only real option.
Click to expand...
Click to collapse
thank you for your answer, =)
uhmmm, as you say i only can use the back camera with an 3rd party app, because when i try to open the pre installed camera app it close...and the camera icons appera in a gray color... except the arrow to see the taken pics, that appear in white...
i discovered some other ppl who had the same problem, :/
oh oh ok. my telephone info is...
Os version: 8.0.10327.77
firmware:2212.13.6.1
hadware: 15.3.1.0
trans soft: 2212.13.6.1
trans hardw: 0.0.0.0
(i actually dont know how to translate this from spanish): 13.04.19.21
SOC chip version: 1.5.32
this is the info i got, before uodating it, the number were almost the same :/
mmmm i remeber when the update was almost ending it was like 1/5 complete... then 2/5 complete... and after that the phone started...what i mean is that there was no 3/5 4/5 or 5/5 steps...
man so you are telling me i wouldnt be abble to replace just the camera, if is a hardware problem??? oh jesus =( i really love this cellphone i dont wanna lose it =(
thank you for your answer my friend =)
First of all: you have GDR2 and the most current firmware that I know of for the SGH-T899M. The line you couldn't translate is "bootloader" (the code that starts, or "boot-straps", the operating system). Your version numbers are identical to mine.
My rear camera works fine, though. Since third-party apps also work, you either have bad firmware somehow (doubtful, especially after the update) or there's something wrong with the Camera app on the phone (more likely). Unfortunately, the only way I know of to fix the latter problem is to re-install the OS (which a hard reset will, or at least should, do).
Replacing just one component, like the camera, is very difficult on a compact device like a modern smartphone. It might be possible, but the cost might not be worth it. On the other hand, if the phone is still under warranty, you should be able to replace for free.
GoodDayToDie said:
First of all: you have GDR2 and the most current firmware that I know of for the SGH-T899M. The line you couldn't translate is "bootloader" (the code that starts, or "boot-straps", the operating system). Your version numbers are identical to mine.
My rear camera works fine, though. Since third-party apps also work, you either have bad firmware somehow (doubtful, especially after the update) or there's something wrong with the Camera app on the phone (more likely). Unfortunately, the only way I know of to fix the latter problem is to re-install the OS (which a hard reset will, or at least should, do).
Replacing just one component, like the camera, is very difficult on a compact device like a modern smartphone. It might be possible, but the cost might not be worth it. On the other hand, if the phone is still under warranty, you should be able to replace for free.
Click to expand...
Click to collapse
GDR2??? are you sure my friend?? ive reading and that update come with the Radio app, some camera features and other... but nothing :/ i just got some options in settings and that was all, i even cant download or instal Ativ beam (i dont find it on the store, and when i try to do a manual install it say that is not compatible) and i heard that app is only for the last update
my cellphone is canadian i think, because the company is ROGERS, and i live in peru, so i cant use the warranty or something
i will try to save some of my info, and i will do another hard reset
Do you think there would be a tool for a diagnosis?? i mean conecting my cellphone to a PC in DOWNLOAD MODE or something???
i swear i wont rest till i fix it :'(
again, thank you very much for your time.
P.D: let me show you what the camera looks like for a while
Yes, build 10327.77 is GDR2. Your phone is a SGH-T899M, same as mine; GDR2, along with an interim update ("Amber" maybe?) and a Samsung firmware update, was pushed out to all Canadian SGH-T899M handsets (including those operating in other countries, like yours and mine) a couple days ago.
ATIV Beam installs fine for me; it's probably a region lock and not a matter of device compatibility.
Samsung is reported to have cheapened out on the radio chips for the SGH-T899M, and not included the one needed for FM.
Data Sense (assuming your carrier offers it) is supposedly included, but due to <REDACTED>-up update process, you have to hard-reset to use it (how the *HELL* did that make it through testing? That's supposed to be exactly the sort of BS that those months-long and tens or hundreds of thousands of dollars of testing per-update are supposed to find! Bloody incompetents...)
There's an app called Diagnosis embedded in your phone's firmware; you can install and launch it by typing either ##634# or ##3424# (MFG or DIAG) into the phone's dialer. Check the relevant thread here about dialer codes and diagnosis apps for some examples of things you can do with it (among other things, test the cameras). However, if the camera is working in third-party apps, I doubt that test will find anything. As I said, that indicates a software problem. Hard reset is the only really likely fix for that, if you can't get Samsung to service it. Flashing a stock ROM would probably work too, but I don't know that we have either the ROM nor the flashing tool needed for doing that.
GoodDayToDie said:
Yes, build 10327.77 is GDR2. Your phone is a SGH-T899M, same as mine; GDR2, along with an interim update ("Amber" maybe?) and a Samsung firmware update, was pushed out to all Canadian SGH-T899M handsets (including those operating in other countries, like yours and mine) a couple days ago.
ATIV Beam installs fine for me; it's probably a region lock and not a matter of device compatibility.
Samsung is reported to have cheapened out on the radio chips for the SGH-T899M, and not included the one needed for FM.
Data Sense (assuming your carrier offers it) is supposedly included, but due to <REDACTED>-up update process, you have to hard-reset to use it (how the *HELL* did that make it through testing? That's supposed to be exactly the sort of BS that those months-long and tens or hundreds of thousands of dollars of testing per-update are supposed to find! Bloody incompetents...)
There's an app called Diagnosis embedded in your phone's firmware; you can install and launch it by typing either ##634# or ##3424# (MFG or DIAG) into the phone's dialer. Check the relevant thread here about dialer codes and diagnosis apps for some examples of things you can do with it (among other things, test the cameras). However, if the camera is working in third-party apps, I doubt that test will find anything. As I said, that indicates a software problem. Hard reset is the only really likely fix for that, if you can't get Samsung to service it. Flashing a stock ROM would probably work too, but I don't know that we have either the ROM nor the flashing tool needed for doing that.
Click to expand...
Click to collapse
incompetents!!! hell yeah!!! !
my friend are you some kind of wizard or something??, while you were writting it, i was doing a hard reset, and now i have data sense... and oh thats why i cant have ativ beam (NFS in WP devices suxs ass hell, i cant send anything) and... Doesnt have a FM radio???!!! SAMSUNG are you serious?!?!?!?...
i did the ##364# and i got the diagnosis item, thats how i noticed that the front cam worked fine and the "megacam" (front one) doesnt work... (i used the *#0*# code) plus the camera LED doesnt work either
oh well , after the hard reset i just got all my data lost n_n; , but you know... the frontcamera still doesnt work... tell me truth im already FU*beeeep*d ,am i?
i really want to believe that this have a solution...at least a non invasive solution...
I actually have the same issue. Before installing the updates from MS and Samsung the camera worked perfectly. When I updated my phone and did the hard reset, the camera behaves like you say, either a black screen or back to home screen. I called Samsung and they say it is most likely that the update did not install correctly. Though they talk rubbish sometimes as they also told me to update through zune........that doesn't even support WP8..
So flashing a stock rom "might" fix the issue. :fingers-crossed:
Hi there. I'm looking to replace my Xperia X Compact as it does not support t-mobile WiFi calling. I'm looking to purchase an xz1 compact as I absolutely hate Sony's new childish, rounded handset look. However I'm very concerned that I will be able to get all the features working that I require, especially with the latest firmware. I would appreciate some up to date information as well as any links to guides to accomplish all of my requirements.
What I require:
1. Root is a must. I do a lot of automation with Tasker and want to have full access to my device. Obviously I'd also like to install recovery and ensure that the camera and all apps and features are fully functional.
2. Fingerprint scanner functionality is required. I use a password manager and have no desire to ever be without this feature.
3. I live in an area with mediocre coverage and frequently visit places with minimal coverage. Thus I have realized that I have need of T-mobile us WiFi calling, band 12 support, VO-LTE, etc.
I have read that with some minimal editing of the firmware files you can flash a modified UK firmware to allow both the fingerprint scanner and WiFi calling but I'm concerned that I might lose one or both if rooted. Furthermore I'm concerned that with the latest OTA I won't be able to accomplish all three. I'm obviously not willing to lose any of these features.
I'd appreciate any updated information and would love if you could point me to any guides.
Thanks in advance.
POMF2K said:
Hi there. I'm looking to replace my Xperia X Compact as it does not support t-mobile WiFi calling. I'm looking to purchase an xz1 compact as I absolutely hate Sony's new childish, rounded handset look. However I'm very concerned that I will be able to get all the features working that I require, especially with the latest firmware. I would appreciate some up to date information as well as any links to guides to accomplish all of my requirements.
What I require:
1. Root is a must. I do a lot of automation with Tasker and want to have full access to my device. Obviously I'd also like to install recovery and ensure that the camera and all apps and features are fully functional.
2. Fingerprint scanner functionality is required. I use a password manager and have no desire to ever be without this feature.
3. I live in an area with mediocre coverage and frequently visit places with minimal coverage. Thus I have realized that I have need of T-mobile us WiFi calling, band 12 support, VO-LTE, etc.
I have read that with some minimal editing of the firmware files you can flash a modified UK firmware to allow both the fingerprint scanner and WiFi calling but I'm concerned that I might lose one or both if rooted. Furthermore I'm concerned that with the latest OTA I won't be able to accomplish all three. I'm obviously not willing to lose any of these features.
I'd appreciate any updated information and would love if you could point me to any guides.
Thanks in advance.
Click to expand...
Click to collapse
All good questions. I was kind of in the same boat, although in the end, I sacrificed root access and settled on only having fingerprint and TMo VoLTE/WiFi calling (mostly because I didn't have the guts to unlock the bootloader with only a questionable DRM fix method available).
I used the information in this thread to get fingerprint and TMo stuff working together. It was pretty simple, and worked great the first time. However, I'm pretty sure OTA updates will break that functionality and you'll have to go through the process again if you want to update the OS and keep fingerprint/TMo stuff working.
As far as root, you will need to unlock the bootloader, and then you will need some sort of DRM fix to keep the camera working. There are a few methods in this forum scattered around, but none of them had enough positive results reported back for me to feel confident in trying them. Remember, once you unlock your bootloader, there is no going back, so you're stuck with a non-working camera until you can find a DRM fix method that works. The most widely used root / DRM fix method that I know of currently is Xperifix, although since it is a paid for tool, there is no dedicated thread here on XDA. There are some discussions on xperifix.com, and a lot of people have had success using this. However, a lot of people have struggled with this as well, so I didn't feel confident enough to try it.
As far as how the DRM fix works with the cobbled together firmware for TMo/fingerprint, I can't say, and I don't think I've read of anyone reporting that here on the forums. I suspect everything would work together just fine, but can't say for sure.
Good luck, and if you do end up getting everything working together with root, please do report back here, I would definitely be interested in hearing about it.
camaro322hp said:
All good questions. I was kind of in the same boat, although in the end, I sacrificed root access and settled on only having fingerprint and TMo VoLTE/WiFi calling (mostly because I didn't have the guts to unlock the bootloader with only a questionable DRM fix method available).
I used the information in this thread to get fingerprint and TMo stuff working together. It was pretty simple, and worked great the first time. However, I'm pretty sure OTA updates will break that functionality and you'll have to go through the process again if you want to update the OS and keep fingerprint/TMo stuff working.
As far as root, you will need to unlock the bootloader, and then you will need some sort of DRM fix to keep the camera working. There are a few methods in this forum scattered around, but none of them had enough positive results reported back for me to feel confident in trying them. Remember, once you unlock your bootloader, there is no going back, so you're stuck with a non-working camera until you can find a DRM fix method that works. The most widely used root / DRM fix method that I know of currently is Xperifix, although since it is a paid for tool, there is no dedicated thread here on XDA. There are some discussions on xperifix.com, and a lot of people have had success using this. However, a lot of people have struggled with this as well, so I didn't feel confident enough to try it.
As far as how the DRM fix works with the cobbled together firmware for TMo/fingerprint, I can't say, and I don't think I've read of anyone reporting that here on the forums. I suspect everything would work together just fine, but can't say for sure.
Good luck, and if you do end up getting everything working together with root, please do report back here, I would definitely be interested in hearing about it.
Click to expand...
Click to collapse
At this point it's pretty much a gaurantee that you can root and add the DRM fix easily. But now I'm hearing something about the pictures will still not be the same quality???
I'm curious how do you keep the device from getting OTA updates without root access?
I'm really not okay with having a device without root access. The ability to make my own recovery images is an absolute must. I'm also too invested in tasker automation to stop now.
POMF2K said:
At this point it's pretty much a gaurantee that you can root and add the DRM fix easily. But now I'm hearing something about the pictures will still not be the same quality???
Click to expand...
Click to collapse
No, has nothing to do with picture quality. The camera either works or it doesn't. When you unlock bootloader, the camera stops working (solid green pictures). When you apply DRM fix, it starts working again as it did originally.
POMF2K said:
I'm curious how do you keep the device from getting OTA updates without root access?
Click to expand...
Click to collapse
I disabled the update centre and update service using this method - no root required.
Does anyone know if this method to keep the wifi calling and fingerprint reader simultaneously active works after recent ota updates?
Still searching for someone on T-mobile US with this device that can verify that I can achieve all 3 at once (Root, Fingerprint Sensor, T-mobile Wifi Calling).
Please help.
If you're in US and using XZ1c, which carrier are you with? I'm interested in carriers that work for docomo/SO-02k models as well as G8441; whether data, or calls, or both work properly.
Not sure of any that work with the docomo, I think there is a thread here for those. But for the g8441 models, T-mobile and Verizon in that order. Used to work great on ATT but they added a whitelist for devices sadly so doesn't work on there anymore. T-mobile works more than fine. Verizon, will take some time getting on it. You need to change your modem and have the sim provisioned for an LTE only device. So far I have gotten data working on it but nothing further. Someday Ill get around to badgering verizonn support more and get it worked out.
I'm pretty sure you won't be able to get it working on Verizon. It supports the AT&T bands, but they've not whitelisted it, as you say.
But Verizon uses entirely different LTE bands, which the XZ1C doesn't have.
Or maybe that's what you mean by "change your modem", but I'm not sure how you've done that, as it's a hardware thing, not software.
tonsofquestions said:
I'm pretty sure you won't be able to get it working on Verizon. It supports the AT&T bands, but they've not whitelisted it, as you say.
But Verizon uses entirely different LTE bands, which the XZ1C doesn't have.
Or maybe that's what you mean by "change your modem", but I'm not sure how you've done that, as it's a hardware thing, not software.
Click to expand...
Click to collapse
Nope, it supports all the verizon bands now since 3G was sunset there. You can use it on Verizon as an LTE only device. You initially gotta get a phone with LTE only provisioned on the network and then switch sims to the xz1c. A guy already got it working and I did have data working too.
No the modem is a software thing. I'll do a write up someday. Actually I use the ir51_ir92 modem for T-Mobile too.
Oh, interesting. That's good to know. I've been having issues with T-Mobile lately, less LTE (more Edge) even though the XZ1c should do LTE. Perhaps Verizon would be better for me.
I'm definitely interested in the other modem software if it has a chance of improving things. Make sure to include steps to roll back, please!
Try the modem. Download quick selector from the play store, then make a new widget from it and select "modem switcher". Make sure debug = true in the build.props. Then from the modems select ir51_ir92_ims. It should help getting more LTE from T-Mobile from my experience.
I'm not seeing an app by the name "quick selector". Can you give me an id/link?
What is it doing? Is it installing something, or changing some configuration on my phone? How can I be sure this modem option won't break something?
tonsofquestions said:
I'm not seeing an app by the name "quick selector". Can you give me an id/link?
What is it doing? Is it installing something, or changing some configuration on my phone? How can I be sure this modem option won't break something?
Click to expand...
Click to collapse
QuickShortcutMaker - Apps on Google Play
Create shortcuts quickly and launch your favorite actions quickly.
play.google.com
Opens an activity. No it won't, I've done this on two phones, it just changes the modem.
I'm feeling more at a loss today time than usual, probably because I'm misunderstanding something key, or because of our ROM differences.
I've installed the app, but the search (which doesn't work on normal mode) doesn't have anything under "modem" or "switcher".
I've added debug=true to my build.props, but I'm guessing there isn't actually a top-level one, and that you wanted a more specific one ... but I'm not clear which.
What am I missing?
Also, to be clear: Is this something to be done once, or on every boot? I'm assuming the former. It seems like there should be another way of getting to the configuration, rather than having to install apps to trigger specific intents.
tonsofquestions said:
I'm feeling more at a loss today time than usual, probably because I'm misunderstanding something key, or because of our ROM differences.
I've installed the app, but the search (which doesn't work on normal mode) doesn't have anything under "modem" or "switcher".
I've added debug=true to my build.props, but I'm guessing there isn't actually a top-level one, and that you wanted a more specific one ... but I'm not clear which.
What am I missing?
Also, to be clear: Is this something to be done once, or on every boot? I'm assuming the former. It seems like there should be another way of getting to the configuration, rather than having to install apps to trigger specific intents.
Click to expand...
Click to collapse
What rom are you using? Just once it has to be done.
I'm running an older Oreo AEX rom - this one, to be precise. https://forum.xda-developers.com/t/aospextended.3859655/
I know it's pretty old, but any upgrade path will require a fair amount of backup/reconfiguration - not to mention experimentation to figure out which new ROM to use. I've had a lot on my plate for a while, and this is my daily driver.
tonsofquestions said:
I'm running an older Oreo AEX rom - this one, to be precise. https://forum.xda-developers.com/t/aospextended.3859655/
I know it's pretty old, but any upgrade path will require a fair amount of backup/reconfiguration - not to mention experimentation to figure out which new ROM to use. I've had a lot on my plate for a while, and this is my daily driver.
Click to expand...
Click to collapse
Strange, I'm running https://forum.xda-developers.com/t/g8441-xz1c-8-1-resurrection-remix-v6-2-1-oreo.4085427/ so that shouldn't be a problem. Try "CustomizationSelector" and then under it select the one with "Modem Switcher"
Do you mean this Sony app? I don't have it on my phone. The rom didn't come with it, and I'm not able to install it (really, the older version that's compatible with Oreo).
If I try (via a terminal, to see the error), I get the following message:
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY: Package couldn't be installed in /data/app/com.sonymobile.customizationselector: Package com.sonymobile.customizationselector requires unavailable shared library semc_bootinfoif; failing!]
Click to expand...
Click to collapse
and I'm not sure where I'd even find that, let alone properly install it on the rom. Maybe via Magisk?
Any other ideas or suggestions on things to try? I feel like there should be some way to do ti.
It might be that one. Um, have to install that shared library, whatever it is. Maybe I could even just copy it and share it with you.
I have the G8441 (with US ROM oem.sin) on both MetroPCS and T-Mobile.
If your running the US stock sony rom on latest Pie:
T-Mobile works very well, both LTE and VoLTE. No problems.
Same used to work for me also on MetroPCS, but now VoLTE does not work on their network right now. IMS Registration: Not Registered. Looks like Metro now 'tricks' the phone to use the default non-tmobile modem. This happened just recently. Should be (fairly) easily fixable if I can gain temproot and force the t-mobile MVNO's modem config id.
If your running a stock non-US rom (specifically non-US oem.sin), LTE will work but poorly, and VoLTE will not work at all on both MetroPCS and TMobile.
The phone should work equally well on Mint Mobile too, unless they are playing tricks like Metro.
tonsofquestions said:
I'm not seeing an app by the name "quick selector". Can you give me an id/link?
What is it doing? Is it installing something, or changing some configuration on my phone? How can I be sure this modem option won't break something?
Click to expand...
Click to collapse
Flash the latest Pie US sony stock rom on it. Tick the 'IMS' APN, restart the phone twice, wait a half hour, and you're LTE will work like a champ on T-Mobile.
Once on the US rom:
Dial '*#*#7378423#*#*' and click Service info > Software info > Scroll all the way to the bottom and you'll see 'Current Modem Config'.
The correct modem config for TMobile with LTE and fully functional VoLTE will read exactly /system/etc/customization/modem/amss_fsg_lilac_tmobile_us_ims_tar.mbn
The incorrect (default) firmware (likely) will read /system/etc/customization/modem/amss_fsg_lilac_tar.mbn. This modem config will not work correctly on TMobile. You'll get poor signal and performance on LTE, and VoLTE will not work at all.
eparr said:
If your running the US stock sony rom on latest Pie:
Flash the latest Pie US sony stock rom on it. Tick the 'IMS' APN, restart the phone twice, wait a half hour, and you're LTE will work like a champ on T-Mobile.
Click to expand...
Click to collapse
Did you see my comment half a dozen posts back where I said I _wasn't_ running stock, or Pie?
I'm not going to flash that to get this to work - I need other features. And while I'm willing to upgrade, I can't spend the time to do go through that right now since I have some personal stuff going on. But I'm still not going to a stock rom.
I cannot use that service code because I don't have the APK that powers it - it's again dependent on a stock rom. There was a separate discussion about that here.
I don't even have a /system/etc/customization/ folder, let alone any mbn files in it.
I would happily install some extra software (a magisk module, perhaps?) to get it. Do you have the mbn files anywhere, or know where I could obtain them?
tonsofquestions said:
Did you see my comment half a dozen posts back where I said I _wasn't_ running stock, or Pie?
I'm not going to flash that to get this to work - I need other features. And while I'm willing to upgrade, I can't spend the time to do go through that right now since I have some personal stuff going on. But I'm still not going to a stock rom.
I cannot use that service code because I don't have the APK that powers it - it's again dependent on a stock rom. There was a separate discussion about that here.
I don't even have a /system/etc/customization/ folder, let alone any mbn files in it.
I would happily install some extra software (a magisk module, perhaps?) to get it. Do you have the mbn files anywhere, or know where I could obtain them?
Click to expand...
Click to collapse
I did. My post #15 you have quoted wasn't to you. That is a response to the OP 4qx.
My second post #16 was to you.
In reading thru dev notes on the custom roms (Havoc mostly, but lineage too), it seems the devs say the device has to be wired up and running on the correct modem firmware and with VoLTE fully functional on stock before installing their custom roms. That seems counterintuitive to me, but thats what I get from their posts.
You can obtain the stock Pie roms with Xperifirm. Which contain the modem files. Finding older Oreo ones will require a bit of internet digging.
Do you know if you can force a new modem onto your custom rom and it will work? I've looked for a clear answer to that myself and still question what i have read.
If you can force the correct .mbn, would you need the modem from Oreo or from Pie? Oreo's modem is named kudo (if i remember right). Pie's is Lilac (T-Mobile's VoLTE is exactly named amss_fsg_lilac_tmobile_us_ims_tar.mbn). Then Maple and Poplar too which is 10 and 11 (i think). I have the sony stock Pie US rom here unsin'ed and in apktools right now, so i could probably find the lilac modem for you if thats the one you need. Let me know and i'll see if i can extract it.
I know the stock Pie 9.0 amss_fsg_lilac_tmobile_us_ims_tar.mbn works 100% with T-Mobile VoLTE. I bought a T-Mobile sim this week specifically to check it. I'm trying to get this same modem running on a T-Mobile MVNO in Pie. But in my case, i have the modem files in place, but Sony didn't add the code to specificically enable the modem config id's for T-Mobile MVNO's, so im trying to write it in, than inject it into an unrooted pie while retaining bootlock..
There is a catch i noticed, and it might throw you when you install the correct modem. When I put in a TMobile sim into the phone, it takes up to around 20 minutes for T-Mobile to provision VoLTE to the device. IMS Registration status will say 'Not Registered' (on stock) until T-Mobile triggers the provisioning, which seems to happen on some sort of schedule. They are probably checking to see who is running a proper modem before enabling VoLTE provisioning to the device. Its not instant. When you believe you have the correct config and modem files, and think it should work, i'd give TMobile a solid 20 minutes before assuming it's not working.
Here you go.
From US Pie stock rom, the modem files are in the system_X-FLASH-ALL-C93B.sin file. I used unsin to extract them to .ext4. Then used 7zip to extract the .mbn files from the .ext4 file. The mbn files are found in the directory \etc\customization\modem\. If you need the .mbn files from other versions, they probably will be in the same location.
There were 3 Pie modem files related to T-Mobile. Attached in the zip below. The ims one is T-Mobiles VoLTE for Pie.
Yes, the one I quoted was unattributed, but in the other post (#16) you specifically said to flash PIE, which had been talked about.
I suspect it depends a little on what kind of ROM it is and what it builds on under the hood. I thought mine had the right stuff initially, but it was a long time ago.
Do you know if you can force a new modem onto your custom rom and it will work? I've looked for a clear answer to that myself and still question what i have read.
Click to expand...
Click to collapse
I have no idea about this. I'm happy to try and see what works, but I've likewise found little in the way of instructions - even where the files would go. Again, I don't have that /system/etc/customization/ folder, and I believe some kind of overlay/binaries needs to exist to pick it up. I suspect just adding the files won't work.
As far as I understand it, the codenames are not related to OS version but rather which model of phone it is.
Poplar is the XZ1, and Lilac is the XZ1C. A search shows that Maple is the XZ Premium.
I can't find any information about a 'kudo' (it's also not a type of tree).
There's a Kumano platform, analagous to Yoshino (XZ*), but I don't think that's what you mean, either. I would hope the modem files are independent of OS vesion. I do have an Oreo sin somewhere around on an older drive that i could dig up to compare.
But the challenge remains that I still have no idea what to do with them...
I appreciate your copy of them, though. Any other thoughts?
Hey anyone else with this phone to start testing new stuff on it?
Got the Chinese version. Flashed the global firmware and changed the channel to reteu with working OTA's.
Will write a guide in the coming days, feel free to ask me about anything you want to know.
I just received the phone, seemed like a store here had a issue allowing me to get the phone early.
If you've got questions, let me know. I do seem to notice a bug with the screen refresh rate set to "auto". It wont go up to 144hz by itself and at low display brightness it seems to stay on 90. Forcefully setting it to 144hz does work wonderfully though.
xJustHinnie said:
I just received the phone, seemed like a store here had a issue allowing me to get the phone early.
If you've got questions, let me know. I do seem to notice a bug with the screen refresh rate set to "auto". It wont go up to 144hz by itself and at low display brightness it seems to stay on 90. Forcefully setting it to 144hz does work wonderfully though.
Click to expand...
Click to collapse
Do you have the global version? Would be great if you could take three pictures in pro mode with everything set to auto and DNG enabled. (One from each lens). My model produces weird raw results for the main camera, I just want to make sure that it is software related.
You can also see in the viewfinder that the main camera seems to be way less contrasty and saturated than the other lenses.
Also: what's your build number / software version?
Killuminati91 said:
Do you have the global version? Would be great if you could take three pictures in pro mode with everything set to auto and DNG enabled. (One from each lens). My model produces weird raw results for the main camera, I just want to make sure that it is software related.
You can also see in the viewfinder that the main camera seems to be way less contrasty and saturated than the other lenses.
Also: what's your build number / software version?
Click to expand...
Click to collapse
Mine is the Chinese version atm but in pro mode I can't take 200Mpx pics
Killuminati91 said:
Do you have the global version? Would be great if you could take three pictures in pro mode with everything set to auto and DNG enabled. (One from each lens). My model produces weird raw results for the main camera, I just want to make sure that it is software related.
You can also see in the viewfinder that the main camera seems to be way less contrasty and saturated than the other lenses.
Also: what's your build number / software version?
Click to expand...
Click to collapse
Yes I have the global version; Motorola Edge 30 Ultra. I can try the photo situation when it's light again. My build number is S3SQ32.16-16-28.
Killuminati91 said:
Got the Chinese version. Flashed the global firmware and changed the channel to reteu with working OTA's.
Will write a guide in the coming days, feel free to ask me about anything you want to know.
Click to expand...
Click to collapse
Does Google Pay and NFC work correctly? Is the chinese hardware exactly the same as Global this time?
Killuminati91 said:
Got the Chinese version. Flashed the global firmware and changed the channel to reteu with working OTA's.
Will write a guide in the coming days, feel free to ask me about anything you want to know.
Click to expand...
Click to collapse
Will be great to have your guide, how do you unlock it?
TF1920 said:
Will be great to have your guide, how do you unlock it?
Click to expand...
Click to collapse
Just checking resellers. You can get the chinese version flashed with global rom already on Aliexpress for £599 for 256gb. Cheapest you can get chinese version that you will need to flash yourself is £530 and that's 128GB only. So might be better to buy it already flashed. Moto UK you can get 10% of for official version which is £675
Hi
I recive today my Global Edge 30 Ultra
Working ok ( first 1-2 hours test )
I find boot.img for root, where i can find firmware ??
Maybe working boot.img from chinese version, i can try use command:
fastboot boot patched_boot.img ( not flashing... )
But where i can find this file or from global version ?
wildlime said:
Does Google Pay and NFC work correctly? Is the chinese hardware exactly the same as Global this time?
Click to expand...
Click to collapse
NFC is toggleable and Google Wallet opens without a problem. As I have never used Google Pay before I dont know how to test it.
I would not buy a flashed version to be honest. If you want a converted phone you should do it yourself to learn what you are doing and maybe be knowledgable enough to handle problems when they arise.
onken said:
Hi
I recive today my Global Edge 30 Ultra
Working ok ( first 1-2 hours test )
I find boot.img for root, where i can find firmware ??
Maybe working boot.img from chinese version, i can try use command:
fastboot boot patched_boot.img ( not flashing... )
But where i can find this file or from global version ?
Click to expand...
Click to collapse
You can get your firmware from Lenovos / Motorolas Rescue and Smart Assistant:
Rescue and Smart Assistant (RSA) - Lenovo Support DE
support.lenovo.com
Use the rescue function with your phone plugged in, start the download and you can unplug the phone.
Firmware can be found at "C:\ProgramData\RSA\Download\RomFiles" after the download.
Would be great if you could share the zipped Firmware with us. Maybe on Google Drive or mega.
These zips dont contain any personal information.
Killuminati91 said:
NFC is toggleable and Google Wallet opens without a problem. As I have never used Google Pay before I dont know how to test it.
I would not buy a flashed version to be honest. If you want a converted phone you should do it yourself to learn what you are doing and maybe be knowledgable enough to handle problems when they arise.
You can get your firmware from Lenovos / Motorolas Rescue and Smart Assistant:
Rescue and Smart Assistant (RSA) - Lenovo Support DE
support.lenovo.com
Use the rescue function with your phone plugged in, start the download and you can unplug the phone.
Firmware can be found at "C:\ProgramData\RSA\Download\RomFiles" after the download.
Would be great if you could share the zipped Firmware with us. Maybe on Google Drive or mega.
These zips dont contain any personal information.
Click to expand...
Click to collapse
Thanks
I send in moment software.
I can update manual this file from telephone ( i need use Magisk )
Killuminati91 said:
Do you have the global version? Would be great if you could take three pictures in pro mode with everything set to auto and DNG enabled. (One from each lens). My model produces weird raw results for the main camera, I just want to make sure that it is software related.
You can also see in the viewfinder that the main camera seems to be way less contrasty and saturated than the other lenses.
Also: what's your build number / software version?
Click to expand...
Click to collapse
Can confirm that for me the main camera also produces weird results in pro mode with raw output. The output also seems to be way more dull than what the view finder suggests.
New full software Motorola Edge 30 Ultra
EQS_G_S3SQ32.16_16_28_subsidy_DEFAULT_regulatory_DEFAULT_cid50_CFC.xml
3.3 GB file on MEGA
mega.nz
How i can update this firmware if i have installed Magisk ( root )
_Hinnie_ said:
Can confirm that for me the main camera also produces weird results in pro mode with raw output. The output also seems to be way more dull than what the view finder suggests.
Click to expand...
Click to collapse
Okay thats good for all of us imo. I already contacted Motorola's camera team about the issue, hoping they'll fix it.
@onken: Thanks for the upload! I am not 100% sure but in theory:
1. Patch the new boot.img from the new firmware via magisk on your phone.
2. Put it into your new firmware folder and name it boot_magisk.img
3. Open the flashfile.xml and copy paste the contents into this website.
4. Reboot to fastboot, open a cmd window in your firmware folder and use the fastboot commands from the website but SKIP "fastboot erase userdata".
5. Reboot into fastboot and flash boot_magisk.img to keep root.
Maybe you need to skip the other "erase" commands as well, not quite sure.
Does anyone happen to know why oem unlocking in developer options is greyed out?
Might be related to your purchase date. I've read that sometimes people need to wait 7 days before it is available on other Motorola phones. Might also be available after factory reset.
I think must wait 96h, about 5 days
Possible work fasted if reset to factory ?
Killuminati91 said:
Might be related to your purchase date. I've read that sometimes people need to wait 7 days before it is available on other Motorola phones. Might also be available after factory reset.
Click to expand...
Click to collapse
Damn, that's ridiculous. I guess I have to wait for a little while, already tried factory resetting twice.
_Hinnie_ said:
Damn, that's ridiculous. I guess I have to wait for a little while, already tried factory resetting twice.
Click to expand...
Click to collapse
I think its related to "Widerrufsrecht" or whatever its called in other EU countries. You could unlock, decide that you dont like the phone and just return it and noone would probably check if the warranty is void.
Here is an official Motorola post on the issue. Sometimes takes up to a week.
Edit: But on the other hand, unlocking your bootloader can not void your warranty in the EU afaik.