WP 8.1 not supporting AWS? - Windows Phone 8 Q&A, Help & Troubleshooting

Hi,
I have a L920, originally Rogers (CA) ROM. I flashed it into Euro Dev a long time ago, and it worked just fine until yesterday on my AWS provider (Mobilicity).
As with previous OTA updates, carriers started to deploy theirs, and I didn't get a notification for mine until yesterday. Did the OTA and as soon as phone started with 8.1, I was showing 'No service'. If I did a manual search, neither Mobilicity nor Wind would show, only CDN Roaming (Rogers), and Bell.
After a few hours with the (un)support of both MS and Nokia, I gave up and decided to flash back. I flashed it back to Rogers WP 8.1, and same thing. I reflashed it to the previous OS I had (Euro Developer, 8.0 GDR 3) and same thing.
My guess is that the AWS frequency is now somehow lost, since the previous Euro version had it and now it doesn't.
Anyone has heard anything about this? And, more importantly, anyone has any idea how to get my AWS back?
Your help is greatly appreciated. Thanks!

Just checking so that smarter folks can help you: Did you by any chance do a factory reset at any point post-update?
Also, please post your OS and FW numbes, just in case.

BrotherFidelis said:
Just checking so that smarter folks can help you: Did you by any chance do a factory reset at any point post-update?
Also, please post your OS and FW numbers, just in case.
Click to expand...
Click to collapse
Thanks for your reply.
Yes, I've done several hard resets, and nothing changed. I have flashed it with several FWs, even the ones I previously had, but no luck. Rogers Portico is as far as I could go, because I can't find Pre-Portico. Here's the FW history:
- Rogers Pre-Portico (factory installed)
- Euro Dev GDR1 (flashed)
- Euro Dev GDR2 (OTA)
- Euro Dev GDR3 (OTA)
- Euro Dev WP8.1 (OTA) - this is when the frequency got messed up
I then flashed these, which I had kept the FWs just in case, but no luck in getting the frequency back:
- Euro Dev GDR3
- Euro Dev GDR2
- Rogers GDR3
- Rogers Portico
Right now it's with 1232.5957.1308.0000.
Hope it's clearer now. And if someone knows where to get Rogers Pre-Portico (or Apollo), I'd appreciate it. That's the only hope I have left at the moment,because both Nokia and WP support proved to be incompetent and unwilling to help in this case.
Thanks again.

Hmm...smarter folks have no yet weighed in, I'm afraid! Most likely they are thinking about your problem and/or working on other stuff.
So, my thought is that somewhere along the line, you debranded your phone - disconnecting the provisioning somehow - by doing factory resets (which is, after all, a normal course of action from troubleshooting techs at MS/Nkoia/wherever).
I (and others) had a similar thing happen with my ATIV Neo S - although I never lost the ability to make calls. After manually programming the cell data provisioning, I'm still unable to send/receive MMS. The newest version of 8.1 I have at least now allows me to make and retain some changes (##3282#), but not others (such as MMSC URL).
Have you compared your current provision settings with those from your carrier (or those originally with the phone)? Can you do a PRL update? If not, what error does it throw?

The most importing thing to note as you are flashing is if the firmware of the radio is changing. This is shown in the "Settings -> About" page. Make sure that after you are done flashing the different FFUs, that the "Radio Software Version" is changing. My guess is that since you changed ROMs, an OTA update was delivered to the radio as part of the Windows Phone update. It accidentally ran on your phone because the CID that the phone reported from the radio firmware matches a Rogers update. Now that this has been updated, the radio version isn't downgrading. (That is just my guess). Make sure that the radio firmware is changing as you apply FFUs and post back.

Related

Struggling with Cappy. Help Please.

Hi, all XDA users.
I've been waiting to post my problems here and tried a few things I could to fix then with no success.
Here's what happened.
I bought a Captivate in february in an eletronics store in Miami, and since I am from Brazil, at the time my only concern was to make sure the device was unlocked, so I tested my sim card and was OK.
So my problems started as I went back to my country, the phone works good, but some issues appeared and they are kind of major for a device like that. Here they are:
I can't download from the market ever since I bought the phone. From a wifi conection or 3G . That was disturbing me so I did the factory reset and that allowed me to use the market for a while, something like 10 minutes maybe, before started giving me the "download was unsuccessful" error. And I did the factory reset a few times . But that was only a taste .
I also can't update my phone from the 2.1 eclair to 2.2 froyo or whatever is available, through Mini Kies, always getting the "unregistered device" message, before anyone asks I tried that in a Win XP and a Win 7 64 .
I tried to do the update several times but I was never able to enter download mode on the phone.
I installed some apps using the Sideload Wonder Machine, since I wasn't able to do it using SDK tools . Perhaps because of the Win 7 64?
So I decided to leave the IPhone for this device for its greater hardware capacity and because of the Android OS overall improvement, but I can't do much with it now, and since I am totally noob, I don't really know if my device was rooted before I bought, I don't know If the best thing to do is to flash stock and start over.
Didn't flash because I am afraid of bricking it.
The one thing I know is that I was able to get rid of all the crap from AT&T and nothing changed in my phone, and I heard that I needed to be rooted to be able to do what I did.!?! Is that true? Please help.
Here are some info about my phone.
Firmware version: 2.1 update 1
Kernel version : 2.6.29
Samsung SGH-I897
Baseband Version : I897UCJF6
Thanks all for your time .
Kies Mini is for US updates. Did you try the full version of Kies? Might work for you there.
Mobile Phone's Software & Manual
Will flashing a new modem help? Did you check network settings? Call company and switch to that region. I don't know. Just some suggestions.
Sent from my SGH-I897 using XDA App
Download one click odin flash the stock jf6 and master clear.this will do a full factory reset.
Sent from my GT-I9000 using XDA Premium App
cappysw10 said:
Kies Mini is for US updates. Did you try the full version of Kies? Might work for you there.
Click to expand...
Click to collapse
I did try the full version, but I will do it again in a XP version of windows and tell what happens .
I am downloading it from the brazilian samsung domain (.com.br) .
I tried again to use the regular Kies but didn't work.
It kept saying my device is not supported .
Funny thing is that in the Kies website, as you change the country flag in the bottom of the screen, the supported devices also changes, and in Brazil there is only a "Wave" called line of devices, while seems that the cappy I can only find in Canada. My point is that the Captivate IS supported.
I had a similar problem when a bad ROM flash borked my IMEI and product code. Chances are good that whoever unlocked your phone ended up screwing this up. Check out this guide to restore a specific IMEI to the device.
Also, you won't find the Captivate supported outside of the US or Canada, since it is only sold under that name by a few specific carriers (in the US, only AT&T carries it). Outside the US, Samsung mostly pushes other Galaxy S phones. Still the same "family" of phones, but there are differences between them.
yourname146 said:
I had a similar problem when a bad ROM flash borked my IMEI and product code. Chances are good that whoever unlocked your phone ended up screwing this up. Check out this guide to restore a specific IMEI to the device.
Also, you won't find the Captivate supported outside of the US or Canada, since it is only sold under that name by a few specific carriers (in the US, only AT&T carries it). Outside the US, Samsung mostly pushes other Galaxy S phones. Still the same "family" of phones, but there are differences between them.
Click to expand...
Click to collapse
Thank you so much. When I first had the problem I figured this was one possibilitie, but the salesguy assured the phone was "factory unlocked", so no one could've laid their hands on the device to screw it up like that. Your info was very valious, I will try to do the restore and let you know.

[Q] Unrooting HTC One running 3.04.651.2 with hboot 1.55

Hi All ,
My apologies if there is a solution to my problem in another thread. I have spent countless hours looking for a way to unroot my Sprint HTC One because the Sprint network can't seem to activate it until I do. Or I need to figure out a way to force the Sprint network to accept my MDN and MSID which can "sometimes" be problematic with rooted devices. It might be easier to just unroot and see if that helps getting the phone to properly activate.
Other than the network connectivity issues, the phone is fully functional. Just cant make calls or send texts.
I am running this ROM based on benny's system dump: http://forum.xda-developers.com/showthread.php?t=2467607 so my device information is:
Android version - 4.3
Sense version - 5.0
Software version - benny's 4.3
Kernel version - [email protected] #1 SMP PREEMPT
Baseband version - 1.00.20.0913_3
Build number - 3.04.651.2 CL251863 release-keys
I've tried everything I can think of to get my device unrooted, but none of the RUUs work due to being on hboot 1.55 s-on or having an older firmware version (1.29.xx or 1.39.xx.)
Is there any method I can use to get completely back to un-rooted stock rom with, relocked boot loader (know how to do that part), stock recovery, etc?
I've looked at so many different threads and google searches and all say you need to be s-off and run RUUs of versions that will either cause my touch screen to not work or worse. If anyone can help me it would be amazing and I would be much obliged.
I am having similar issues. I'm about to try this method - http://forum.xda-developers.com/showthread.php?t=2470569&page=3 Read OP and see post#27
jharre08 said:
I am having similar issues. I'm about to try this method - http://forum.xda-developers.com/showthread.php?t=2470569&page=3 Read OP and see post#27
Click to expand...
Click to collapse
Ah yes! The 3.04 version wasn't available the last time I read that post! I can confirm that the other that using the 1.29 and 1.31 versions caused serious issues for me and my phone. This post is actually what led me to learn about the issues due to different firmware and file structure between new and older versions.
I'm downloading now. Let me know how it goes!
tuckprodigy said:
Ah yes! The 3.04 version wasn't available the last time I read that post! I can confirm that the other that using the 1.29 and 1.31 versions caused serious issues for me and my phone. This post is actually what led me to learn about the issues due to different firmware and file structure between new and older versions.
I'm downloading now. Let me know how it goes!
Click to expand...
Click to collapse
Also, check this out - http://qbking77.com/development/how-to-unrootunbrick-the-htc-one-to-stock-2/
It's a bit dated, but I am going to try this method if I can find a 3.04 RUU. Note, he is doing this to an S-On phone, which is what we have. So it SHOULD work:good:
Nothing against the first method I posted, but I'd much rather do a RUU and get a clean slate...
There is no RUU for 3.04 yet ( that I know of)...
this is your best (and pretty much only) option: http://forum.xda-developers.com/showpost.php?p=46565593&postcount=27
Did you ever find a way to resolve this issue? Also did this start after flashing Cyanogenmod? I have the exact same issue and it seems I have exhausted all available resources. Currently have the following setup:
Android version - 4.3
Sense version - 5.0
Software version - 3.04.651.2
Kernel version - [email protected] #1 SMP PREEMPT
Baseband version - 1.00.20.0913_3
Build number - 3.04.651.2 CL251863 release-keys
Noticed that the phone is unable to update PRL correctly. Version will switch from 00000 to 1 to 55016. I am also unable to commit changes to any EPST settings (which is the first thing sprint tried to do). MDN and MSID both currently say 'no' and I can't update.
I'm having the exact same issue with everything working fine but no calls/texts.
I flashed the Guru reset for 3.04 but still no calls/text.
Any other solutions?
kindabizzie said:
I'm having the exact same issue with everything working fine but no calls/texts.
I flashed the Guru reset for 3.04 but still no calls/text.
Any other solutions?
Click to expand...
Click to collapse
Try the following:
Full wipe. Flash the newest stable CM.
Go into Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription:
Confirm the following settings:
Network mode = LTE/CDMA/EvDo
CDMA subscription = NV
After you confirm these settings, switch the network mode to CDMA/EvDo only and then back to LTE/CDMA/EvDO.and give it a minute or so, you should see 3G/Phone availability come back. You can test this by dialing a number. You should be able to make a call, or at least get the default Sprint "device is not activated" recording. After confirming this, you can do another wipe and flash back to a stock ROM. You should now have mobile network connectivity back. You may need to Activate the phone again and update the profile/PRL to get back to 100%.
jjmckaskie said:
Try the following:
Full wipe. Flash the newest stable CM.
Go into Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription:
Confirm the following settings:
Network mode = LTE/CDMA/EvDo
CDMA subscription = NV
After you confirm these settings, switch the network mode to CDMA/EvDo only and then back to LTE/CDMA/EvDO.and give it a minute or so, you should see 3G/Phone availability come back. You can test this by dialing a number. You should be able to make a call, or at least get the default Sprint "device is not activated" recording. After confirming this, you can do another wipe and flash back to a stock ROM. You should now have mobile network connectivity back. You may need to Activate the phone again and update the profile/PRL to get back to 100%.
Click to expand...
Click to collapse
Didn't work man, thanks though. My data is fine, I just can't call/txt...it's really bizarre...
kindabizzie said:
Didn't work man, thanks though. My data is fine, I just can't call/txt...it's really bizarre...
Click to expand...
Click to collapse
Hmm. That's pretty much the issue that I had except 4G/Wifi was working and 3G/Call/Text didnt seem to be. You might try switching the CDMA mode to SIM and then back to NV to make sure the setting takes. I know CM can be really finicky with network changes.
tuckprodigy said:
Hi All ,
My apologies if there is a solution to my problem in another thread. I have spent countless hours looking for a way to unroot my Sprint HTC One because the Sprint network can't seem to activate it until I do. Or I need to figure out a way to force the Sprint network to accept my MDN and MSID which can "sometimes" be problematic with rooted devices. It might be easier to just unroot and see if that helps getting the phone to properly activate.
Other than the network connectivity issues, the phone is fully functional. Just cant make calls or send texts.
I am running this ROM based on benny's system dump: http://forum.xda-developers.com/showthread.php?t=2467607 so my device information is:
Android version - 4.3
Sense version - 5.0
Software version - benny's 4.3
Kernel version - [email protected] #1 SMP PREEMPT
Baseband version - 1.00.20.0913_3
Build number - 3.04.651.2 CL251863 release-keys
I've tried everything I can think of to get my device unrooted, but none of the RUUs work due to being on hboot 1.55 s-on or having an older firmware version (1.29.xx or 1.39.xx.)
Is there any method I can use to get completely back to un-rooted stock rom with, relocked boot loader (know how to do that part), stock recovery, etc?
I've looked at so many different threads and google searches and all say you need to be s-off and run RUUs of versions that will either cause my touch screen to not work or worse. If anyone can help me it would be amazing and I would be much obliged.
Click to expand...
Click to collapse
You may need to flash a stock rom and manually enter you MDN and MSID using the epst menu
no luck
At this point I have not had any luck solving this issue. I used Guru's reset tool as well and believe the problem is the radio firmware. I spent a good deal of time on the phone with Sprint support and with a surprisingly competent technician in the store. He tried to work with multiple different systems they have available to get the phone to recognize the Sprint towers with no success.
He said that the phone just isn't recognizing them in any way and commented that a phone that isn't activated will still show bars of service because the phone gets the signals from nearby towers, but just doesn't know what to do with the signal until activated. In my case, all I see is the "X" above the signal bar graphic.
If you're experiencing the same issue as me, there is nothing Sprint can do to make the phone recognize their towers based on the conversations I've had. I saw my options as:
1. Wait for an RUU to come out or something like that
2. Try out different ROMs - jjmckaskie suggested the newest CM, but I would think others might be worth trying as well. Basically anything that uses different radio firmware
3. Get a new phone - This is the option I've gone with. Since my phone is running a stock ROM and the guy at Best Buy where my insurance is from, didn't check the bootloader (would have said "tampered" and "unlocked"), he assumed I never voided my warranty and sent out for a refurb. This may not work if your insurance is through Sprint though. I'm not sure how thorough they are.
tuckprodigy said:
At this point I have not had any luck solving this issue. I used Guru's reset tool as well and believe the problem is the radio firmware. I spent a good deal of time on the phone with Sprint support and with a surprisingly competent technician in the store. He tried to work with multiple different systems they have available to get the phone to recognize the Sprint towers with no success.
He said that the phone just isn't recognizing them in any way and commented that a phone that isn't activated will still show bars of service because the phone gets the signals from nearby towers, but just doesn't know what to do with the signal until activated. In my case, all I see is the "X" above the signal bar graphic.
If you're experiencing the same issue as me, there is nothing Sprint can do to make the phone recognize their towers based on the conversations I've had. I saw my options as:
1. Wait for an RUU to come out or something like that
2. Try out different ROMs - jjmckaskie suggested the newest CM, but I would think others might be worth trying as well. Basically anything that uses different radio firmware
3. Get a new phone - This is the option I've gone with. Since my phone is running a stock ROM and the guy at Best Buy where my insurance is from, didn't check the bootloader (would have said "tampered" and "unlocked"), he assumed I never voided my warranty and sent out for a refurb. This may not work if your insurance is through Sprint though. I'm not sure how thorough they are.
Click to expand...
Click to collapse
Dang, and I was gonna go to a Sprint store after work. *Sigh* guess I have NO CHOICE but to get a Nexus 5 now, lololol
kindabizzie said:
Dang, and I was gonna go to a Sprint store after work. *Sigh* guess I have NO CHOICE but to get a Nexus 5 now, lololol
Click to expand...
Click to collapse
As a last resort you could also try the hard reset code from your dialer by entering ##72786# . You will need to be on a stock rom. You will also need your MSL code (you can usually get this from Sprint support). This will reset EVERYTHING so be mindful. It will also force a hands free activation/Profile/PRL update after the phone reboots which is sometimes useful.
jjmckaskie said:
As a last resort you could also try the hard reset code from your dialer by entering ##72786# . You will need to be on a stock rom. You will also need your MSL code (you can usually get this from Sprint support). This will reset EVERYTHING so be mindful. It will also force a hands free activation/Profile/PRL update after the phone reboots which is sometimes useful.
Click to expand...
Click to collapse
I still took it to Sprint just to see and they fixed it. Downside is my GPS and LTE is messed up again (Me trying to fix those things is the reason all this happened in the first place) but I'd rather not have GPS than not have phone capabilities on my phone (And LTE in Los Angeles is garbage anyway). I think I'm gonna leave my phone alone for a while tho, lol.
jjmckaskie said:
As a last resort you could also try the hard reset code from your dialer by entering ##72786# . You will need to be on a stock rom. You will also need your MSL code (you can usually get this from Sprint support). This will reset EVERYTHING so be mindful. It will also force a hands free activation/Profile/PRL update after the phone reboots which is sometimes useful.
Click to expand...
Click to collapse
Looks like I am going to go this route. I hit ##72786# and it takes me to SCRTN screen. I'm guessing I just hit menu in the top right, then reset? Then it will prompt me for my MSL code?
jharre08 said:
Looks like I am going to go this route. I hit ##72786# and it takes me to SCRTN screen. I'm guessing I just hit menu in the top right, then reset? Then it will prompt me for my MSL code?
Click to expand...
Click to collapse
Yup. I actually dont remember if it does a full wipe, or just forces an activation/profile/PRL update. But either way it's worth a shot.
tuckprodigy said:
At this point I have not had any luck solving this issue. I used Guru's reset tool as well and believe the problem is the radio firmware. I spent a good deal of time on the phone with Sprint support and with a surprisingly competent technician in the store. He tried to work with multiple different systems they have available to get the phone to recognize the Sprint towers with no success.
He said that the phone just isn't recognizing them in any way and commented that a phone that isn't activated will still show bars of service because the phone gets the signals from nearby towers, but just doesn't know what to do with the signal until activated. In my case, all I see is the "X" above the signal bar graphic.
If you're experiencing the same issue as me, there is nothing Sprint can do to make the phone recognize their towers based on the conversations I've had. I saw my options as:
1. Wait for an RUU to come out or something like that
2. Try out different ROMs - jjmckaskie suggested the newest CM, but I would think others might be worth trying as well. Basically anything that uses different radio firmware
3. Get a new phone - This is the option I've gone with. Since my phone is running a stock ROM and the guy at Best Buy where my insurance is from, didn't check the bootloader (would have said "tampered" and "unlocked"), he assumed I never voided my warranty and sent out for a refurb. This may not work if your insurance is through Sprint though. I'm not sure how thorough they are.
Click to expand...
Click to collapse
Sounds like you solved your issue, but for anyone else having trouble....
I re-tried GURU's reset and it worked. The first time I downloaded it over the 4G network. I also downloaded the OTA over the 4G network. My radio has been giving me fits ever since. Finally, I downloaded GURU's reset over WIFI, then made sure the OTA downloaded over WIFI, and my phone is like new again! No radio issues, everything is perfect. Hope this helps some people...

Can't Update System Software

I just got brand new Xperia X Performance that came with 6.0.1, and I'm trying to figure out why I can update it. It's unlocked but not rooted, basically right from the factory as far as I know.
When I go into Software Update in the phone's settings, it says "Your device already has the latest available system updates."
When I use the Sony app on my PC it says my system software is up to date.
I actually can't find anything about this issue, anybody here have any ideas?
Thanks!
try downloading and running xperifirm, find out if your region has the update at all, you should be able to update atleast to 7 anyway
There are a few variants that are considered as internal units or something like that and they don't get OTA updates, also HK units were stuck on 7 for some reason last time I checked. Mine is a french model, and yesterday I received the april security patches while the global variant got it two months ago
st3ch said:
try downloading and running xperifirm, find out if your region has the update at all, you should be able to update atleast to 7 anyway
There are a few variants that are considered as internal units or something like that and they don't get OTA updates, also HK units were stuck on 7 for some reason last time I checked. Mine is a french model, and yesterday I received the april security patches while the global variant got it two months ago
Click to expand...
Click to collapse
Thanks for the reply.
Here's a screenshot of Xperiafirm. https://ibb.co/dUCN3T
I'm in Canada, though I'm on Freedom Mobile, not Rogers or Bell. I don't think my carrier ever sold this phone, and I'm not sure what would happen if I flashed 8.0 made for Bell or Rogers phones.
Ideally I'd like 7.1.1 Canadian generic for Xperia X Performance, but I can't seem to find that anywhere.
I've also never done this so I don't really know what I'm doing, and don't want to void my warranty!
Thanks for you help!!
Good the ROMs that you see for Canada are all latest 8.0 with May security patches and maybe your phone is one of these and the updates just got stucked for some reason.
First you have to check what kind of model you have to check this, to do so you should open the dialler and type
*#*#7378423#*#*
From the service menu you should select -> Service Info -> Software Info and look for Customization Version:
As I said mine is a french model so it states 1302-9342_R2E your should be something different but only the first 8 numbers matter
then look this number in Xperifirm if yours is everything different from Internal Unit (second column from the screenshot) then there is a easy way to try and update without loosing your warranty
First there is always a risk! But I have done this a few times for my Xperia U and Xperia M5 and had no problems at all.
Do a backup - contacts...everything you need as it will delete them
charge the phone to at least 80%
then you should go to the Xperia Companion and do a software repair, not update but repair
It should install the latest version for your phone but it shows the version it installed only when it's finished...
Even if it has not installed the latest update then just connect the phone to your wifi/LTE and try the OTA updates again (could take up to an hour)
This is the safest way that will not void your warranty in any way but will delete your info (contacts, pics..etc. ) so do a backup prior
And if possible use a laptop with a working battery as even a 1 second glitch in the grid could cause the phone to get bricked
And if your phone is imported from China and the customization number is considered as an Internal Unit the only way you could get 7.0 or 8.0 is by flashing and another ftf file as the ones for Bell Canada or Rogers, there are actually some ROMs uploaded in XperiaBlog
there could be some in XDA but I have not search for any
st3ch said:
Good the ROMs that you see for Canada are all latest 8.0 with May security patches and maybe your phone is one of these and the updates just got stucked for some reason.
First you have to check what kind of model you have to check this, to do so you should open the dialler and type
*#*#7378423#*#*
From the service menu you should select -> Service Info -> Software Info and look for Customization Version:
As I said mine is a french model so it states 1302-9342_R2E your should be something different but only the first 8 numbers matter
then look this number in Xperifirm if yours is everything different from Internal Unit (second column from the screenshot) then there is a easy way to try and update without loosing your warranty
First there is always a risk! But I have done this a few times for my Xperia U and Xperia M5 and had no problems at all.
Do a backup - contacts...everything you need as it will delete them
charge the phone to at least 80%
then you should go to the Xperia Companion and do a software repair, not update but repair
It should install the latest version for your phone but it shows the version it installed only when it's finished...
Even if it has not installed the latest update then just connect the phone to your wifi/LTE and try the OTA updates again (could take up to an hour)
This is the safest way that will not void your warranty in any way but will delete your info (contacts, pics..etc. ) so do a backup prior
And if possible use a laptop with a working battery as even a 1 second glitch in the grid could cause the phone to get bricked
And if your phone is imported from China and the customization number is considered as an Internal Unit the only way you could get 7.0 or 8.0 is by flashing and another ftf file as the ones for Bell Canada or Rogers, there are actually some ROMs uploaded in XperiaBlog
there could be some in XDA but I have not search for any
Click to expand...
Click to collapse
Thanks so much for the reply...I discovered the version of Android installed on my phone is a version meant for Journalists/Reviewers/Commercial use, and can not be updated. I just got a refund for the 3-year warranty portion of my purchase after pointing this out to them. So after the 90 day warranty that came with it runs out, I'll be able to do anything I feel like with this device.
I'll be looking for a safe way to install 7.1.1 hopefully, and if not then 8.0. There seem to be less issues with 7.1.1, but there's really only one way to find out: when I start using it.
I'll definitely need a point in the right direction when it comes to that though. I understand Sony has an official flashing tool, and you have to unlock the bootloader (which is supported on my phone even with this version). But I haven't done it before and don't know how.

updating to Pie - how to tell / predict / force firmware region

I've got an unrooted xz1c that came with some sort of non-US stock firmware - which I know, because the fingerprint reader works. It's been nagging me to update it to Pie since I bought it, and I'm thinking I'd like to do it via the "official" (OTA) route, since it claims to be able to do it in-place, without having to reinstall apps, restore data, etc. What I want to avoid, though, is ending up with a US update, losing my fingerprint reader, and having to jump through hoops to get it back.
The build number in About Phone says 47.1.A.12.270. Is there some way of determining the current region, and confirming what region the update plans to install (without starting the update) - and/or forcing the region to match what I currently have? My google accounts, phone #, etc. are all US-based, if that makes any difference in terms of the update deciding what region is appropriate.
I was looking at a guide for installing specific region firmware via xperifirm/newflasher, but it indicated that the result would be a wiped phone, and I don't have time to deal with re-configuring everything from scratch right now.
Firmware customization does not change by applying OTA update. It will install the update of the same region that is already installed.
meeotch1 said:
I don't have time to deal with re-configuring everything from scratch right now.
Click to expand...
Click to collapse
In the past the OTA updates have famously locked thier owners out of thier phones by not regonising the unlock code that has been set, so make sure you disable it before you start.
Also, updating from 8 to 9 leaves some apps glitchy and there have been several reports of phone problems that can only be resolved by a full factory reset.
If you want the best experiance from your phone, wiping it would be the best option when upgrading.
Use Xperia transfer to back up apps/call history/contacts/text history. Then restore once you've wiped your phone.
@meeotch1 If you are happy with Oreo and without the latest security patches and updates, just let the phone OTA update it to the final Oreo version 47.1.A.16.20 and leave it there.
You can force close the Software update app from app settings to make it stop nagging about the update. And with adb you can even disable it permanently (and enable later if you wish to go for Pie).
Thanks for the advice. Good to know that the nag is disableable. So I take it that OTA upgrades *within* major versions (so Oreo 47.1.A.12.270 to 47.1.A.16.20) do not suffer the glitches mentioned by the first reply above?
Also, when I eventually go Pie, what's the least painful / most reliable restore method after wiping the phone? Is the built-in Xperia backup/restore available in Settings good enough? I'd prefer not to upload all my data to Google, unless there's some guarantee that it's encrypted. Don't need the NSA digging through my messages to radical terrorists and international drug lords.
To find out the customization, go to the service menu and select "Software Info".
You'll see an entry named "Customization Version" with a number like "1310-4371_R6C".
You can then look in XperiFirm at the column named "CDA".
On the example I gave, "1310-4371" corresponds in XperiFirm to "Customized US".
You can also look further down in the software info at "Current Modem Config" where the format will be something like:
/system/etc/customization/modem/amss_fsg_lilac_tmobile_us_ims_tar.mbn"
That tells me that my SIM card matched a mobile operator that is recognized as having a valid modem configuration file for my customization's region and, as such, loaded the correct modem file for that operator.
It also shows that I'm using T-Mobile US as my operator (tmobile_us) and I have some kind of VoLTE available (ims).

Samsung SM-925A Updates and/or Custom ROM

I received a free Samsung S6 Edge from some friends. The phone had a busted battery which I fixed. The phone is still on the original 5.1.1 that the phone was released with.
When I try to do updates it says DM initialization not ready. Check network or SIM card. When I received the phone I was told it doesn't work with cell service. I checked to make sure and it definitely doesn't. There are no options for cell service in settings or the drop-down menu. This phone is missing IMEI numbers, IMEISV numbers, and baseband versions too. The only way I found out the IMEI number was it was printed on the back of the phone.
I am fairly certain the problems are software-based and not the motherboard but I don't know enough about phones to be sure. Do you guys know? I also want to remove AT&T from the phone to install a custom ROM on the device. (There is no OEM unlock in the developer options) Can I flash SM-925F firmware on the device to make it factory unlocked or will this brick the device? Will flashing the original SM-925A firmware fix the problems with the device? Please let me know if you need any more information to answer my question.
I found this: //G925A\\ Nougat 7.0.1 Latest Stock ATT Odin files G925AUCS7ERC1 | XDA Developers Forums (xda-developers.com) Should I flash this on my device? Will it fix any of the problems I had on it?
Can I flash the SM-925F firmware? Is the hardware of the factory unlocked phone and AT&T versions the same or will it brick this phone if I flash it?
Since the phone is AT&T you'll have to go through AT&T for the unlock codes before you can flash anything other than an AT&T ROM. To my knowledge there are no custom ROMS for the S6 Edge, but I could be mistaken.
skeltonh said:
Since the phone is AT&T you'll have to go through AT&T for the unlock codes before you can flash anything other than an AT&T ROM. To my knowledge there are no custom ROMS for the S6 Edge, but I could be mistaken.
Click to expand...
Click to collapse
I know this phone is old news however, I actually have the S6 and S7 edge lying around and so i got bored lol...here is my dilemma; Evidently the phone (S6 Edge G925A) had an abnormal factory reset, which is a load of BS, and now I can not get that security detail, which you know calling Samsung always ends to NO AVAIL!! I have flashed with Odin the firmware that my device is on the ERC1 firmware and still I get stuck @abnormal reset. I've searched numerous sites, different forums and still to no avail. Something told me inside that you was the man to drop a line to, any leads or info will be more than appreciated brother...Thanks for your time....
PSSS....
I got my unlock code from AT&T some time ago but the code is 16 digits long and code only takes 8 digits, and of course to hear AT&T tell it, " I simply must not putting the code in correctly"...lmao

Categories

Resources