Database Info

Restriced Access Changed

Need help! I'm on Movistar Argentina with my Moto G, and twice a day I get Emergency Calls Only and a notification that says Restricted Access Changed, Service is Blocked. When I reboot the phone it ceases, but after some hours it comes back.
Running Stock ROM and Kernel, with Locked Bootloader and without root.

LittleConfucy said:
Need help! I'm on Movistar Argentina with my Moto G, and twice a day I get Emergency Calls Only and a notification that says Restricted Access Changed, Service is Blocked. When I reboot the phone it ceases, but after some hours it comes back.
Running Stock ROM and Kernel, with Locked Bootloader and without root.
Click to expand...
Click to collapse
I have the same issue on T-Mobile. Unlocked boot loader, root, faux kernel and stock 4.4.2 ROM. Reboot has been the only solution so far. Have you changed your APN? My problem started after I did that.
Sent from my XT1034 using Tapatalk

Changing the e3s bootloader unlock allowed from no to yes

So I have spent hours on this.. I've Already rooted my phone via the guides (thanks so much guys) but was gutted on seeing bootloader unlock allowed was still no
I've checked everywhere and I haven't found anything on the Internet specific to the e3 so I've decided to ask the developer community on Xda to see what comes up
Has anybody come up with anything? Or heard anything. I really want to be able to flash custom roms. Thanks for your time

Dannysharks said:
So I have spent hours on this.. I've Already rooted my phone via the guides (thanks so much guys) but was gutted on seeing bootloader unlock allowed was still no
I've checked everywhere and I haven't found anything on the Internet specific to the e3 so I've decided to ask the developer community on Xda to see what comes up
Has anybody come up with anything? Or heard anything. I really want to be able to flash custom roms. Thanks for your time
Click to expand...
Click to collapse
Generally by making your phone sim-unlocked you change this from NO to YES, but from past experience, locked phones by Movistar in Spain remain with with a NO even after sim-unlocking it. If after sim-unlocking it it still says NO, I'm afraid it will stay that way.

PJMOR said:
Generally by making your phone sim-unlocked you change this from NO to YES, but from past experience, locked phones by Movistar in Spain remain with with a NO even after sim-unlocking it. If after sim-unlocking it it still says NO, I'm afraid it will stay that way.
Click to expand...
Click to collapse
I did see that coming, I'll definitely unlock my sim card anyways. Hopefully it will work. If not, would I be able to use custom roms? Or would I be stuck with the stock rom as a base

If it says bootloader unlock allowed no then it can never be unlocked it's as simple as that unfortunately. Sim unlocking had nothing to do with the bootloader and is for unlocking your phone from one network to be able to use it on any other network. If you buy a sim free network unlocked device then the bootloader unlock allowed will usually say yes. It's the networks that change it to a no
D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.

XT1032 ROM on XT1033 without Dual-SIM functionality

My dad recently upgraded to a new phone, so his old 1st gen Moto G is just lying around now.
However, it's an XT1033 (Dual-SIM) variant.
What I want:
-Unlocked Bootloader
-Root
-TWRP
-CM12.1
-No Dual-SIM functionality (so basically I want my phone to be an XT1032)
The phone has a locked bootloader right now, running on stock 4.4.4 (Asia Retail) and is unrooted.
My main question is, can XT1032's TWRP work on an XT1033?
Second question, can I flash the 'falcon' builds from the CM website on my phone, or is there something else I have to do?
Any help will be greatly appreciated.

murtaza02 said:
My main question is, can XT1032's TWRP work on an XT1033?
Second question, can I flash the 'falcon' builds from the CM website on my phone.
Click to expand...
Click to collapse
Yes, and yes.

lost101 said:
Yes, and yes.
Click to expand...
Click to collapse
This requires no special modification right? Just root, and an unlocked BL.
When I flash it, I'll just lose Dual-SIM, but everything else will work, right?
Sent from my D6503 using Tapatalk

murtaza02 said:
This requires no special modification right? Just root, and an unlocked BL.
When I flash it, I'll just lose Dual-SIM, but everything else will work, right?
Click to expand...
Click to collapse
There is a possibility some ROMs may refuse to install because the Developer has written the install script to fail if 'XT1033' is detected - but I doubt that is very common.
Unlock Bootloader, 'rooting' is rarely something you need to do separately - more often part of the ROM zip. Everything should work apart from the 2nd SIM slot.

lost101 said:
There is a possibility some ROMs may refuse to install because the Developer has written the install script to fail if 'XT1033' is detected - but I doubt that is very common.
Unlock Bootloader, 'rooting' is rarely something you need to do separately - more often part of the ROM zip. Everything should work apart from the 2nd SIM slot.
Click to expand...
Click to collapse
That's awesome.
Thanks man.
Sent from my D6503 using Tapatalk

[Q] Regarding what to flash and what not to.

The title says it all, I'm very hesitant to flash anything to my Xperia M2, even FTFs! I'm scared to death one day my sim card functionalities will cease to work (cannot call, no data, only emergency calls, etc). I am aware that the only way that can happen from an ftf is if I flash the simlock.ta by accident, but my question is this: Is there any way to lose sim-card functions, by flashing too many ROMs or FTFs (upgrading, downgrading)?

Naa man, feel safe to flash. I've flashed my M2 like around 20 times with out any issues. But, i screwed my sim functionality because when flashing a lollipop ftf i didn't excluded simlock.ta. Other than that, everything is perfect. So when ever flashing a rom, just see if it has a simlock.ta, and make sure you exclude it. In my case, i have ftf for JB, KK and L, and only the one for L has a simlock. So just make sure you don't flash the simlock.

Sidow said:
Naa man, feel safe to flash. I've flashed my M2 like around 20 times with out any issues. But, i screwed my sim functionality because when flashing a lollipop ftf i didn't excluded simlock.ta. Other than that, everything is perfect. So when ever flashing a rom, just see if it has a simlock.ta, and make sure you exclude it. In my case, i have ftf for JB, KK and L, and only the one for L has a simlock. So just make sure you don't flash the simlock.
Click to expand...
Click to collapse
Huh, I'll always check for a simlock.ta! Thanks for the clarification!

Sidow said:
Naa man, feel safe to flash. I've flashed my M2 like around 20 times with out any issues. But, i screwed my sim functionality because when flashing a lollipop ftf i didn't excluded simlock.ta. Other than that, everything is perfect. So when ever flashing a rom, just see if it has a simlock.ta, and make sure you exclude it. In my case, i have ftf for JB, KK and L, and only the one for L has a simlock. So just make sure you don't flash the simlock.
Click to expand...
Click to collapse
I don't have simlock on my Xperia M2 but I will ask anyway, is there any way you can back-up that simlock.ta file ?

It's only included on carrier ftf's I think as my m2 is a sim free network unlocked device and I've never removed it from customised ftf's
D2303 5.1lollipop customised NCB LB rooted Nuts t2u dual recovery bravia engine 2+x-reality debloated viper audio

G3RV0 said:
I don't have simlock on my Xperia M2 but I will ask anyway, is there any way you can back-up that simlock.ta file ?
Click to expand...
Click to collapse
Ima be honest, i don't know much about "ta", i don't know if simlock.ta is on the TA partition (it might sound dumb but i don't know). I read a post about a guy explaining Sony's recurity system, that as of today no one can hack it. Simlock.ta is part of that security system(which means that there is no way to backup, as far as i know). So in my case i locked my device, and since there is no way to hack the sec system, i'm screwed (according to what that guy said). But one thing i'm sure about, just whenever flashing an ftf, if it has simlock.ta, exclude it. And even more because your phone doesn't have a simlock.
For example, i had an Xperia S, and whenever flashing ftf including simlock, it would just skip it because it was locked to an specific network. My M2 wasn't, so when trying to flash simlock, and succeded and i locked my phone. So as long as you exclude simlock.ta, you'll be safe.
About what i said about TA partition, and Sony's security system, that's what i've read. I might not be completly right.

Sidow said:
Ima be honest, i don't know much about "ta", i don't know if simlock.ta is on the TA partition (it might sound dumb but i don't know). I read a post about a guy explaining Sony's recurity system, that as of today no one can hack it. Simlock.ta is part of that security system(which means that there is no way to backup, as far as i know). So in my case i locked my device, and since there is no way to hack the sec system, i'm screwed (according to what that guy said). But one thing i'm sure about, just whenever flashing an ftf, if it has simlock.ta, exclude it. And even more because your phone doesn't have a simlock.
For example, i had an Xperia S, and whenever flashing ftf including simlock, it would just skip it because it was locked to an specific network. My M2 wasn't, so when trying to flash simlock, and succeded and i locked my phone. So as long as you exclude simlock.ta, you'll be safe.
About what i said about TA partition, and Sony's security system, that's what i've read. I might not be completly right.
Click to expand...
Click to collapse
I see, so this simlock file is somehow encrypted or lock I guess if it cannot be accessed by people like us. Anyway what would happen if I won't exclude it from a flashing ? My smartphone doesn't have any simlock since I bought it brand new in a shop.
I have a huge favour to ask if you don't mind me asking, I want to unlock my bootloader in Xperia M2 and flash it to a custom rom, I have posted it around two days ago and it has 61 views but no one posted anything. I will appreciate your help if you do. Link to my thread.
Thanks

Ta (Trim Area) can be backup and restored if you have root, but can't be modified. There's a thread in sony Cross device that explains a lot of it.
Sent from my D2303 using Tapatalk

G3RV0 said:
I see, so this simlock file is somehow encrypted or lock I guess if it cannot be accessed by people like us. Anyway what would happen if I won't exclude it from a flashing ? My smartphone doesn't have any simlock since I bought it brand new in a shop.
I have a huge favour to ask if you don't mind me asking, I want to unlock my bootloader in Xperia M2 and flash it to a custom rom, I have posted it around two days ago and it has 61 views but no one posted anything. I will appreciate your help if you do. Link to my thread.
Thanks
Click to expand...
Click to collapse
Your phone does not have a simlock, which means, that if you flash a simlock.ta, it's going to lock it. Just like it happen to me, with no way to fix it. And sure, i'll try to answer on your post.

Sidow said:
Your phone does not have a simlock, which means, that if you flash a simlock.ta, it's going to lock it. Just like it happen to me, with no way to fix it. And sure, i'll try to answer on your post.
Click to expand...
Click to collapse
lol, so it locks and you can never use your Xperia M2 ? Pretty lethal if you ask me until you have backup of the original file. Tho I have flashed few times back to KitKat and I don't think so KitKat TFT file has that file. Ok , I really appreciate it ! :good:

G3RV0 said:
lol, so it locks and you can never use your Xperia M2 ? Pretty lethal if you ask me until you have backup of the original file. Tho I have flashed few times back to KitKat and I don't think so KitKat TFT file has that file. Ok , I really appreciate it ! :good:
Click to expand...
Click to collapse
You're wlecome, but you can't backup the simlock file. Watch:
1-If you phone is already locked to a network, you can't remove it, not replace it. (You can unlock the phone with a code but that's another story). So if you try to flash an ftf with simlock, nothing will happen.
2-If your device is not locked to an specific network (doesn't have a simlock) and you flash an ftf with simlock, there's when you have screwed your phone.

T-Mobile D6616 Xperia Z3 - Are we completely stuck on the latest T-Mobile ROM?

Do us T-Mobile D6616 Xperia Z3 owners have any options to install a different Sony ROM from another variant that has a newer Android version (Marshmallow)? Our bootloader is locked but it's my understanding that the bootloader doesn't need to be unlocked to install another Sony Xperia ROM from the same variant. The question is: although it might be expected/understandable, what is the root cause as to why our D6616 soft bricks when trying to installing the ROM from another Z3 variant (eg. D6653)? Is there a certain piece of the ROM such as the baseband that causes the soft brick, in which case wouldn't it be possible to just remove the baseband from the ROM/FTF and it would work?
Are there any Devs willing to explore this or already know? I just want to know if us T-Mobile Xperia Z3 owners are completely screwed with no options?
By the way, Des from the product team at T-Mobile said that Sony dropped Dev support for the T-Mobile Xperia Z3... How lovely...

s1dest3pnate said:
Do us T-Mobile D6616 Xperia Z3 owners have any options to install a different Sony ROM from another variant that has a newer Android version (Marshmallow)? Our bootloader is locked but it's my understanding that the bootloader doesn't need to be unlocked to install another Sony Xperia ROM from the same variant. The question is: although it might be expected/understandable, what is the root cause as to why our D6616 soft bricks when trying to installing the ROM from another Z3 variant (eg. D6653)? Is there a certain piece of the ROM such as the baseband that causes the soft brick, in which case wouldn't it be possible to just remove the baseband from the ROM/FTF and it would work?
Are there any Devs willing to explore this or already know? I just want to know if us T-Mobile Xperia Z3 owners are completely screwed with no options?
By the way, Des from the product team at T-Mobile said that Sony dropped Dev support for the T-Mobile Xperia Z3... How lovely...
Click to expand...
Click to collapse
Without an unlocked bootloader, there's not really much to be done. You're at T-Mobile's mercy for updates. You cannot install a ROM for any other variant than the D6616. There is a check that happens in the bootloader when you turn the device on. If a non-D6616 firmware is detected, it will refuse to boot until it detects the correct one. This is easily bypassed with an unlocked bootloader, which is not available for the T-Mobile variant.
In short, yes, D6616 owners are indeed screwed. Don't buy carrier models whenever possible.

There are unlocked versions now available. I unlocked my version and tried to flash another room but didn't work.
I would love to know more specifics on how to bypass the check. Is part of it replacing the phone ID?
---------- Post added at 06:52 PM ---------- Previous post was at 06:06 PM ----------
Here is the partition files if that helps
https://docs.google.com/document/d/1Nl5Egwt4ubXDRpLNOEzVQRu0gNk2lxO2ad7nUkNTkD0/edit?usp=sharing

A quick note from the battlefront. Both Sony and TMO are pointing at eachother. The one constant is not owning up to orphaning the TMO variant less than a year into its product cycle. It's actually quite amusing to see the non-statements from both parties. A simple "It ain't happening" statement would shut the door.
Here's hoping someone with a lot of time on his/her hands can jailbreak the D6616 variant.

The partition layout is the same. If every partition was pulled from a D6603 with adb or fastboot. I theoretically should be possible to flash them one by one to a D6616 if done in the correct order. A jtag cable may be necessary.

So you are saying the only way to do it is getting a copy of someones phone partions and installing them individually?
/u/cajunflavoredbob @cajunflavoredbob Any further suggestion from your end?

odunke01 said:
So you are saying the only way to do it is getting a copy of someones phone partions and installing them individually?
/u/cajunflavoredbob @cajunflavoredbob Any further suggestion from your end?
Click to expand...
Click to collapse
The bootloader for the D6616 is not the same as on the other unlocked models. You can bypass the bootloader lock and write directly to the partitions using a jtag box or similar hardware, but there's a very real chance that it will still not boot up, since the bootloader checks for firmware verity on boot. As I mentioned before, take this as a lesson not to buy carrier branded models in the future, or at least those without a bootloader unlock method. I know the temptation is there to get the device cheaper through the carrier, but you're getting what you pay for.

@cajunflavoredbob the device I have is unlocked. It is not from tmobile directly.
When I purchased it the phone was branded as a D6603.
So with the knowledge that this phone does have an unlocked bootloader. Is there a non hardware related method?

odunke01 said:
@cajunflavoredbob the device I have is unlocked. It is not from tmobile directly.
When I purchased it the phone was branded as a D6603.
So with the knowledge that this phone does have an unlocked bootloader. Is there a non hardware related method?
Click to expand...
Click to collapse
You're in the wrong forum then. This is for the T-Mobile version (D6616). With an unlocked bootloader, you can pretty much flash whatever you want.

I am annoyed as when I purchased the phone it was branded as a D6603 (packaging and advertising) but is truly a D6616 as stated in the phones internals.
When I originally got the phone I upgraded it using xperia companion and it installed D6616 firmware, that was the first time i realised something was different with it.
The IMEI numbers match and sony recognises it as a proper IMEI.
I checked the bootloader status using *#*#7378423#*#* and it stated "Bootloader unlock allowed: yes"
I then proceeded to Sonys website to unlock the bootloader and it changed to "Bootloader unlocked: yes"
Flashing a normal d6603 firmware (rom or ftf) doesn't work, only d6616
There are also others who have stated that they have unlockable versions of the d6616, it isnt just me.
So repeating my question, is there something that can be done?

I think we need to try the Non-T-Mobile US Model (D6646) ROM. It's the closest to our T-Mo model.

Ok, so I tried again.
Checked my bootloader staus again, it still says unlocked:yes
Tried flashing niabocs existenz rom - > softbrick (blackscreen, no logo)
Reflashed the stock 4.4.4 FTF
Rooted, recovery etc.
rechecked bootloader, still unlocked: yes
Tried Slimm rom from Wajk - factory reset etc
- > softbrick (blackscreen, no logo)
What step am I missing?
Do i need to flash the D6603 FTF first?
---------- Post added at 09:44 AM ---------- Previous post was at 09:34 AM ----------
Ok, so that didn't work
03/041/2016 11:41:47 - INFO - Opening TA partition 2
03/041/2016 11:41:47 - INFO - Writing TA unit 00002774. Value : 01
03/041/2016 11:41:47 - INFO - Closing TA partition
03/041/2016 11:41:48 - INFO - Processing partition-image.sin
03/041/2016 11:41:48 - INFO - Checking header
03/041/2016 11:41:48 - ERROR - Processing of partition-image.sin finished with errors.
---------- Post added at 09:46 AM ---------- Previous post was at 09:44 AM ----------
Do I need to extract the files and create a PRF, leaving the bootloader from D6616 in it?

Screenshots to show it is a D6616 with an unlocked bootloader

@cajunflavoredbob Hate to bother you still, but you mentioned it was easy to bypass the check on boot.
I haven't been able to find that searching on XDA or google.
How would I got about it.
As you can see above, I DO have a D6616 and it has an unlocked bootloader.

As I mentioned, you can bypass the bootloader by writing directly to the partitions through a jtag box or similar. However, you would still likely have an issue when you reboot due to the bootloader verifying the system on each boot.
It seems like your device took the wrong firmware update, though. I have not come across any D6616 devices with an unlockable bootloader. If you say that the packaging labeled it a D6603, and it later turned into a D6616 with an unlockable bootloader, this backs up my theory.
You could try unlocking the bootloader and flashing whatever you want, but the issue now is that you have a D6616 bootloader looking for the same system image.
Long story short, it is easy to bypass the bootloader, but only if you have the hardware to do so. Honestly, I would argue that it's better to just pick up a new device at this point. The G4 can be had for under $200, for example, and that's about what a jtag box is going to cost you.
Unless someone creates a tool to unlock the D6616 bootloader or to replace it with one of another model, there's really nothing you can do. Carrier branded devices suck.

Ok, thanks mate. Thought you meant there was a software coded way of bypassing.
That sucks.
Oh well, no idea why it changed to a D6616 firmware, but i'm stuck with it now. Its still a good phone and I can do enough manually, it was just easier to use someone elses hardwork through an already modded rom.
Thanks for the reply.

@odunke01: I have D6616 with Bootloader unlock allowed: yes, same as yours. I think that like me, you purchase your phone from non-authorized distributor. I found that DRM Key has [Unknown error]. Though I do think that the phone originating US T-Mobile D6616 and has been modified (may be illegally). This modification is to unlock SIM card that allow the phone working with free SIM.

well if ur package labels as d6603 then u need to recover it to this version somehow else this mobile will be no fun for ya. miht an mod cn be done for an recovery to cheat on the kernel and insall the right kernel above it and sin error can apear when ur download have problems. ps if uinstall an costumrom then install one wich is ful and before that delete everything on ur phne except the fota partition. mch easier to avoid darkness of death. it should work.