Related
Now that the tablet z is launching worldwide, what would be the chances of being able to debrand the docomo version of the TZ?
I'm just wondering as I'm not sure how good docomo is at releasing updates.
First we need the SGP321 Firmware.
At the moment there is only the docomo FW available and the WiFi only version.
Maybe someone with a SGP321 device could provide it....
electric0ant said:
Now that the tablet z is launching worldwide, what would be the chances of being able to debrand the docomo version of the TZ?
I'm just wondering as I'm not sure how good docomo is at releasing updates.
Click to expand...
Click to collapse
Im with you, I have DoCoMo and I just want to load the stock firmware.
But I found out the bootloader is set to no so cant unlock yet.
Do you know once we get a stock firmware will that unlock the DoCoMo sim lock?
shaun.s said:
Do you know once we get a stock firmware will that unlock the DoCoMo sim lock?
Click to expand...
Click to collapse
I don't think there is a simlock
electric0ant said:
I don't think there is a simlock
Click to expand...
Click to collapse
my Xperia Tablet z DoCoMo branded device does, when I put in a sim it asks for network unlock code...
shaun.s said:
my Xperia Tablet z DoCoMo branded device does, when I put in a sim it asks for network unlock code...
Click to expand...
Click to collapse
Strange, I got mine from a dealer here in Hong Kong who never mentioned about any unlock and my local sim works in it fine, also xperiax10.awesome said a friend helped him buy his one from japan directly from docomo and didn't have to unlock it either.
some sites do seem to be offered sim unlock but it's rather pricy:
http://www.worldgsmcodes.com/sony/Sony-Xperia-Tablet-Z-LTE-network-unlock/
electric0ant said:
Strange, I got mine from a dealer here in Hong Kong who never mentioned about any unlock and my local sim works in it fine, also xperiax10.awesome said a friend helped him buy his one from japan directly from docomo and didn't have to unlock it either.
some sites do seem to be offered sim unlock but it's rather pricy:
http://www.worldgsmcodes.com/sony/Sony-Xperia-Tablet-Z-LTE-network-unlock/
Click to expand...
Click to collapse
Not sure about others but mine is locked. I can pay $30 to DoCoMo to unock it for me tho.
In my service menu there a X next to network lock so hoping a non DoCoMo firmware will mean an unlock
shaun.s said:
Not sure about others but mine is locked. I can pay $30 to DoCoMo to unock it for me tho.
In my service menu there a X next to network lock so hoping a non DoCoMo firmware will mean an unlock
Click to expand...
Click to collapse
Unfortunately, I'm pretty sure firmware and sim unlocks are seperate.
electric0ant said:
Unfortunately, I'm pretty sure firmware and sim unlocks are seperate.
Click to expand...
Click to collapse
Really? What locks in the simlock then?
I was reading that the boot loader doesn't contain the sim lock so I assumed it was firmware based.
shaun.s said:
Really? What locks in the simlock then?
I was reading that the boot loader doesn't contain the sim lock so I assumed it was firmware based.
Click to expand...
Click to collapse
Yes, SIM-Lock is not dependent on Firmware
This is why you can flash different FW Versions to mobiles/tablets without any problems.
As from my knowledge the SIM-Lock is like a DRM-Key which is stored in the TA (TrimArea).
If you want to unlock your device you have to write the correct unlock code in the dialer, after this with an algorythm the DRM-Key is generated and stored in the TA.
To avoid any problems with SIM-Lock the Flashtool never flashes the simlock.ta file which is in some FTF Files.
The file is skipped
UserX10 said:
Yes, SIM-Lock is not dependent on Firmware
This is why you can flash different FW Versions to mobiles/tablets without any problems.
As from my knowledge the SIM-Lock is like a DRM-Key which is stored in the TA (TrimArea).
If you want to unlock your device you have to write the correct unlock code in the dialer, after this with an algorythm the DRM-Key is generated and stored in the TA.
To avoid any problems with SIM-Lock the Flashtool never flashes the simlock.ta file which is in some FTF Files.
The file is skipped
Click to expand...
Click to collapse
interesting.
If the key is stored in the TA and you unlock your bootloader the TA partition is removed on unlocking of bootloader, people are recommending to backup the TA partition to retain BRAVIA 2..so once you have the backup you could remove the any signs on the sim lock and once you restore it should be unlocked? hah
that's just my thinking....
shaun.s said:
interesting.
If the key is stored in the TA and you unlock your bootloader the TA partition is removed on unlocking of bootloader, people are recommending to backup the TA partition to retain BRAVIA 2..so once you have the backup you could remove the any signs on the sim lock and once you restore it should be unlocked? hah
that's just my thinking....
Click to expand...
Click to collapse
I think here is an answer from a developer the best solution
You are right in theory, but I think when you remove the signs on the sim-lock the TA is not signed correctly anymore and it will not work. But this is just my thinking...
So for a correct answer we need a real DEV like DooMLooRD or Bin4ry or ....
UserX10 said:
I think here is an answer from a developer the best solution
You are right in theory, but I think when you remove the signs on the sim-lock the TA is not signed correctly anymore and it will not work. But this is just my thinking...
So for a correct answer we need a real DEV like DooMLooRD or Bin4ry or ....
Click to expand...
Click to collapse
Hmm interesting.
thanks for your reply.
Online unlocker
do you think the online sites that promise to give unlock codes for docomo tablet z's legit?
yellowpants said:
do you think the online sites that promise to give unlock codes for docomo tablet z's legit?
Click to expand...
Click to collapse
Yes, Worldgsmcodes.com sent me the unlock code for my SO-03E in 72 hours.
Don't choose Xperia tablet z, choose tablet S, then the support will contact you to give them the IMEI of your XTZ and then they will send you the unlock code.
Works perfectly.
The Unlocking bootloader service sent me a code to unlock the bootloader, ( my XTZ says : Bootloader unlock allowed : No ), i tried this :
In the cmd windows type in fastboot.exe -i 0x0fce getvar version
If a value is returned (it will return 0.5), it means the phone is correctly connected
Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which u received earlier.
You're device should now be bootloader unlocked
it's not working....
K4HD said:
Yes, Worldgsmcodes.com sent me the unlock code for my SO-03E in 72 hours.
Don't choose Xperia tablet z, choose tablet S, then the support will contact you to give them the IMEI of your XTZ and then they will send you the unlock code.
Works perfectly.
The Unlocking bootloader service sent me a code to unlock the bootloader, ( my XTZ says : Bootloader unlock allowed : No ), i tried this :
In the cmd windows type in fastboot.exe -i 0x0fce getvar version
If a value is returned (it will return 0.5), it means the phone is correctly connected
Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which u received earlier.
You're device should now be bootloader unlocked
it's not working....
Click to expand...
Click to collapse
Hey,
did you unlock bootloader? did you lose your DRM keys/Bravia???
SIM unlock
K4HD said:
Yes, Worldgsmcodes.com sent me the unlock code for my SO-03E in 72 hours.
Don't choose Xperia tablet z, choose tablet S, then the support will contact you to give them the IMEI of your XTZ and then they will send you the unlock code.
Works perfectly.
The Unlocking bootloader service sent me a code to unlock the bootloader, ( my XTZ says : Bootloader unlock allowed : No ), i tried this :
In the cmd windows type in fastboot.exe -i 0x0fce getvar version
If a value is returned (it will return 0.5), it means the phone is correctly connected
Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which u received earlier.
You're device should now be bootloader unlocked
it's not working....
Click to expand...
Click to collapse
Thanks man, bit the bullet and ordered an unlock code. Hope this works on my docomo tablet z too.
After getting my unlock code, my SIM was already identified.great. Just a quick question, am I stuck with the R (roaming) logo? Im getting 3g signal and 3g working but the logo still stays at R.
Hello!
At the entrance I will add that I have a locked bootloader, and that I have "bootloader unlock alloved no".
Yesterday I've downloaded flash tool and it was there I began the whole story.
- I'm one Unlock the bootloader (via flash mode only), and so it's a total nothing could.
-I have flash the file simlock.ta with firmware T-mobile (simlock.ta i rename to "preset.ta" )
And now this happens:
Phone works normally, but after entering the pin code says that the code has been adopted, then the sim card is not known.
Of course, other phones working fine.
I'll tell you this: I am a developer but sim locks, and so is the case for mne strange thing.
I received from a friend that kind of partition TA was damaged hence this problem and I do not have a copy of the TA.
Any advice besides the service?
Thnaks
Hi everyone,
I have recently bought a locked Huawei Y600-L01 (3 Ireland) because I was desperately in need of a phone (my own became hard-bricked without any reason apparently ). It worked only with a 3 Ireland sim I had bought previously, but not with my own Italian sim card. Since the phone asked me the unlock code and I didn't know it (I didn't even know it was a thing, since my previous phone was bought unlocked), I simply inserted my sim code ten times and successfully locked the sim on the phone.
Now, when I insert the Italian sim on the phone, it simply says that the sim is locked (despite not being actually locked, since I tried that sim on another phone and it worked perfectly).
As you may now think, I need this phone to be unbranded. The instruction for that phone are really hard to find, though.
While I installed successfully a stock Huawei V100R001C577B040 firmware version + kernel (phone still locked anyway), I can't seem to unlock the bootloader in order to unbrand the phone (at least that's what I understood it has to be done... or not? ).
I tried both with adb/fastboot and DC Unlocker
1 - adb successfully sees the device. If I type first adb reboot bootloader the phone gets stuck on the first boot screen without actually entering the fastboot mode. If I type fastboot oem unlock in this state it says that the operation has failed because the phone is locked.
The only way to turn back to normal is to remove the battery, wait some seconds and then put it back into the phone.
If I don't try to enter in bootloader mode and I just type fastboot oem unlock, <waiting for device> appears and nothing else happens.
I also tried fastboot -w, but <waiting for device> appeared even in that case.
I tried to apply for the code from the Huawei site, but a) when I dial *#*#1357946#*#* for the product number it doesn't appear anything and b) when I tried the Huawei Product ID generator no ID generated would work.
2 - DC Unlocker doesn't even recognize the phone
What should I do?
PS: I would rather not pay for the unlock code, and I also need to use the "locked" sim on the Huawei phone
_______________________________________________
EDIT: Phone can also go back to normal mode by typing fastboot reboot on PC
Hello my good fellows!
Basicly is there a chance to unlock sim card via some software tools? and here is some of the stuff I've arleady tried to do
- Phone is locked to operator T-Mobile and I have a Vip sim card so First thing it come into my mind is to try and flashing the frimware of the phone to Vip operator while deleting userdata, didn't do anything except removed the T-Mobile logo on the startup
- Bootloader is locked by phone, have thought about it but didnt make sence because of step 1
- Trowing it out of the window (still alive)
So if you Know a way to unlock or atleast reseting the counter because I've recieved a code and tried it but its pointless because of 0 attemptes
Any help would matter to me greatly and thank you in advance for your time.
EDIT : Forgot to mention the program that I used is called "Sony Mobile Flasher by Androxyde"
Hi guys, so I seem to have scewed up my phone quite badly. I tried to deodex running the new nougat firmware (with drm-fix and ric-off) by flashing a zip in the nougat firmware thread. Somehow I ended up with not being able to fastboot anymore.
I found out that my bootloader seems to be locked again. Thus I am not able to approach the fastboot mode, but failed to do any flash, as it says [FAILED (remote: not allowed)].
I checked the service menu and found the [Bootloader unlock allowed:no] and [Remote Lock State: Locked] after reflashing the nougat firmware.
So I wanted to unlock the device, how ever I ended up with flashing back to Lollipop and the device boots and then power off after a few seconds of use.
Could this due to "remote lock state: not allowed"?
Try relocking via flashtool?
So. Tried to lock and relock via flashtool. Checked drivers which are working fine.
I was trying to relock and then unlock again using flashtool after updating to .305 Marshmallow firmware . However this does nothing to the bootloader states. The weird thing is that there are no errors showing up in flashtool when unlocking/relocking. I can't even unlock via OEM because when I tick OEM unlock in the developer options this doesn't do any change (Rooting status: Bootloader unlock allowed : No, Remote Lock State: Locked). My DRM keys are gone as well. However I do have a TA Backup but can't restore because after downgrading to lollipop the device shuts down after 30 seconds.
I'm really annoyed because I bought the device with an locked bootloader (without carrier costumizations) and unlocked it via OEM unlock then updated to . Is there any chance to unlock the device again? Restore TA? Any recommendations what I could have done wrong would be helpful.
iArvee said:
Try relocking via flashtool?
Click to expand...
Click to collapse
[solved ] Bootloader is now sucessfully relocked andBootloader states are back to [Bootloader unlock allowed: Yes] and [Remote Lock State: UnLocked].
I need to mention that I bought a phone without carrier lock with [Bootloader unlock allowed: Yes].
So, for anyone who is interested or might face the issue in the future, here's what I did.
You will need your backed up TA-Partition-Image to restore via iovyroot:
1. Downgrade to Lollipop (32.0.A.6.200 / R2B (STOREFRONT GENERIC)) using Flashtool .
->Therfore select/tick everything in the wipe section when selecting the Lollipop-tft
2. Unmount your SIM, reboot the device
3. Skip everything on the welcome/configuration screen as fast as you can to get beyond the Android configuration screen
(skip wif config, Google-Account setup, untick myXperia services! etc.)
The phone might power off only after a few seconds because of the downgrade. So be fast!!!
4. Once you end up on the home screen, unlock developer options, and activate ADB debugging, grant ADB access (check via cmd: fastboot devices)
again: be fast! --> Don't worry if the phone shuts down again. Just reboot if you were not fast enough.
5. Download iovy.root ( iovy.root. Place TA-backup.img in the iovyroot-folder.
Then I modified "tarestore. bat" to save some time regarding the shutdowns. I used notepad++:
...
set response=
set /p response=Type "y" if you want to restore this file:
if "%response%" == "y" (
echo Starting restore
echo.
adb push "root/iovyroot" "/data/local/tmp/iovyroot" > NUL 2> NUL
adb push "root/restore.sh" "/data/local/tmp/restore.sh" > NUL 2> NUL
...
5. Run CMD as admin. CD to Iovyroot folder.
Restore using tarestore.bat (tarestore.bat TA-2016-xxx.img) as soon as your device boots up to home screen and seems to be connected as ADB device.
( I checked this by running the windows device manager simultaniously)
Wait to end the process.
-->When the restore was sucessfull, the device shouldn't shutdown again.
6. Reboot. Your bootloader is now locked again (but able to unlock via OEM unlock). DRM keys/functionality is restored.
I have the same problem (after i had nougat working incl drm fix and root, also the deodex, tried flashing lower ftf files too when i got this problem, noticed the rebooting, which it does not do at 305 kernel or higher..
I would have hope in your solution, if I could find my ta backups (i have from some other phones, this one, may have been on a crashed laptop, already searched through old hdds)
Could this be because of fastboot flash recovery twrp.img (cause that is something i never done before on the z5c.)
If anyone has a solution other than restoring the ta partition, i would like to know. Because i am very uncertain that i can find those files again...
Same case here z5c unlocked since +/- 1 year and I don't have any TAbackup too
I will try to downgrade to .200 But with bootloader unlock allowed : no ... I don't have much hope
edit : no chance, I tried .200 but without tabackup, I can't do nothing
When I faced this problem I noticed it happened because I wiped TA options with Flashtool. Never do that if you don't want to lose TA partition and all other things connected to it. I could fix it only by flashing TA backup even though I hadn't the timing issue zegovernator had for flashing back TA.
I actually wonder why Flashtool allows to wipe these critical partitions/options
ric69 said:
Same case here z5c unlocked since +/- 1 year and I don't have any TAbackup too
I will try to downgrade to .200 But with bootloader unlock allowed : no ... I don't have much hope
edit : no chance, I tried .200 but without tabackup, I can't do nothing
Click to expand...
Click to collapse
I'm sorry for you. I would recommend updating back to MM since LP gives you immediate shut downs when recognising that your TA is lost/wiped. It's sometime a pain in the ass that stuff gets posted before testing. Nonetheless, you could still try to send in your device back to Sony Costumer Service if you are under warranty (after flashing .200, say that it is "broken" and keeps crashing). However, I would not trust on them sending you a new device.
jutphaas said:
I have the same problem (after i had nougat working incl drm fix and root, also the deodex, tried flashing lower ftf files too when i got this problem, noticed the rebooting, which it does not do at 305 kernel or higher..
I would have hope in your solution, if I could find my ta backups (i have from some other phones, this one, may have been on a crashed laptop, already searched through old hdds)
Could this be because of fastboot flash recovery twrp.img (cause that is something i never done before on the z5c.)
If anyone has a solution other than restoring the ta partition, i would like to know. Because i am very uncertain that i can find those files again...
Click to expand...
Click to collapse
I sorry to say that, but if you lost your TA-backup or didn't even back it up before unlocking the bootloader there is no hope at the moment. You simply can't fastboot because of the Remote State: Locked. It keeps you from accessing the bootloader.
I found my iovyroot TA-backup.img file, I did have a .200 storefront ftf and tried it on that one, which was very anoying as it wants to start a demo , i found an other .200 ftf online which I tried, and the iovyroot seems to work, at that time no reboot, in service menu, the drm keys now seem fine there, Bootloader unlock allowed : No, Remote Lock State: unLocked , fastboot boot or oem unlock still seemed not working well i think that is what it said, (flashtool unlock always seems to, i did try) now i flash a new ftf and try my luck there with the unlock status.
flashing ftf 5.11 flashtool says
03/005/2017 05:05:49 - INFO - Loader : S1_Root_f936 - Version : MSM8994_50 / Boot version : S1_Boot_MSM8994_LA1.2_119 / Bootloader status : ROOTED
And now in 5.11 it also says bootloader unlocked : Yes Lost my drm again
So I am back in flashing and rooting (with drmfix etc) Android 7 again Thanks for sharing this solution!!
So you confirm that TA backup is the only solution to solve the "unlock allowed" bad state, don't you?
This is good for other people because when I faced the problem I was really scared to have messed up my phone!!!
i want to confirm the solution here
i had the same problem and the only way back of it was to downgrade to Lollipop and restore the TA-Partition
i dont think there is a solution if you did not backup your TA and have an image of it.
Yes, the TA restore is the only known solution, and I am glad Zegovernator shared his solution here