yashsingh1/xdaforums huggingface dataset:
[Sony Xperia T, TL, TX, V] matt4321:
Hey guys, Curiosity got the better of me and I did some research into unlocking the bootloader when it says no.

I remember from the Xperia U forums that XperianPro was looking at this and got people to back up there ta partition and view it in notepad++, this is shown in a hexadecimal format which is difficult to edit.

I took a new approach and decided to use the adb command

dd if=/dev/block/mmcblk0p1 of=/mnt/sdcard/ta.img

to get a .img of the ta partition which is loaded to mmcblk0p1 (on the T anyway)

when I opened this in notepad++ I found a whole lot more of human readable stuff in the ta partition.

I did find

ROOTING_ALLOWED="0"

As I recall. from XperianPros thread they did see this, and AFAIK some tried changing it to 1 and it caused a hard brick. but from using my method I think I found something else that will lead to the solution.

I found a Signature Value section

<SignatureValue>Uf7ztzGcQiKz5ivqLEG0Emxhh/9L0C0doeq1HlJIIamuyLiU8kmHxfxytPlzCVYC68jz0WWdRVsL
jaN62bvED6ZmUDETiUQa/mlytNFv2n8Ffv7ihXMay9uebxnme77JzThpWOrSXGP1odiMhvgft3xq
k9tAZKqAzChvy8LYruPXVB8dL1hl0wN3MrPrD4Dd+1WvTeXiTPJMmbftzLYy+HOaJw5oKmamHJRb
U6ejjC4eBgORvdmMddekkSd5JMMZ4ki6CBWU8SPK7eAebxUUXs1vT19gzjEIxiVt3fRnw680D4Fv
5zNB7Wy++y1dcqYyBEPEq9jVGwamcintj/fI9A==</SignatureValue>

I believe this is the signature of the file and changing the value of rooting allowed to 1 would obviously change the signature of the file, and I don't think they recalculated a signature in the other thread. from what I can gather from my ta.img is that it uses a sha1 key verification method (I think)

Sooooo.... Any help or insight would be great

I'm going to keep looking at this for the next few days and see what I find.

I don't think this has been covered regarding looking into an unofficial unlock, If it has then I must have missed it haha, and I'm probably barking mad. I also wanted to keep this separate from the bounty thread as that's about a bounty
[Sony Xperia T, TL, TX, V] Galcactus:
If I remember correctly, however I may be wrong, but that signature is an SHA hashed version of the unlock code provided by Sony. Not sure which version of SHA, also may be salted. But do check/find out more, I may be wrong.
[Sony Xperia T, TL, TX, V] kxf41:
Thanks for looking into this for us people not allowed to unlock our bootloaders!

I believe if u crack this the bounty would rightfully be yours? I certainly would gladly give you my donation if you crack it.

Good luck
[Sony Xperia T, TL, TX, V] DS-1:
Very intresting thread. I hope this is the right way to unlock bootloader even for those who can't.
[Sony Xperia T, TL, TX, V] gregbradley:
No.

This has been tried before and it results in a hard brick.

Simply changing a value from 0 to 1 is way to simple.
[Sony Xperia T, TL, TX, V] matt4321:
that's why I think this Signature Value has something to do with it
[Sony Xperia T, TL, TX, V] gregbradley:
Well, best of luck with that ;)
[Sony Xperia T, TL, TX, V] Galcactus:
On the one hand, bear in mind that kexec is being developed (on and off development, really). I'd suggest that you get your unlock code from Sony, and the original one for the ta you got unlocked and start finding out what the various hashes of it are, might be you end up with one that matches that section, then hash your code with the same way, then do some magic the ta area :)

Just a thought.
[Sony Xperia T, TL, TX, V] peetr_:
Maybe simlock.ta, could be helpful.

There were some cases, when rooting allowed changed to yes after update.

It probably flashes only with the right values or what?

Simlock.ta in HEX -

// [SIMLOCK S1]
02

000007DA 0146 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 02 00 05 0A 02 00 00 00 0A 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 02 00 00 00 0A 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 47 4F 50
5F 49 44 3D 22 31 38 37 22 3B 4F 50 5F 4E 41 4D
45 3D 22 4F 72 61 6E 67 65 20 50 4C 22 3B 43 44
41 5F 4E 52 3D 22 31 32 36 38 2D 33 31 36 34 22
3B 52 4F 4F 54 49 4E 47 5F 41 4C 4C 4F 57 45 44
3D 22 30 22 3B 00 00 00 09 00 07 30 30 31 30 31
2D 2A 00 00 00 00 00 0B 00 07 32 36 30 30 33 2D
2A 00 00 00 00 00 00 00 00 02 00 00 00 0A 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 02 00 00 00 0A 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00
00 0A 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 02 00 00 00 0A 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00

Simlock.ta in ASCII -

// [SIMLOCK S1]
02

(symbol)2010 (+)326(symbols) something...GOP_ID="187";OP_NAME="Orange PL";CDA_NR="1268-3164";ROOTING_ALLOWED="0";00101-* 26003-*...something

Just some idea. ;)
[Sony Xperia T, TL, TX, V] Dr.htc:
is it reliable?
[Sony Xperia T, TL, TX, V] izuall187:
Looks promising. But like@gregbradley said this is too risky. Unless someone is willing to make a sacrifice for it. But come to think of it it had sone potential for bootloaders not allowed for unlocking.
[Sony Xperia T, TL, TX, V] LaZiODROID:
I'm down to use my prototype Xperia T LT30a as a guinea pig for this experiment, but obviously only if some advancement is made to the current theory (Signature verification relationship, etc.). If the dev is somewhat confident/comfortable, then so am I. I have my Xperia L as a backup unit if my T gets destroyed.
[Sony Xperia T, TL, TX, V] matt4321:
this is good, I'm still looking into the relationship between unlock keys, signature value and other things
[Sony Xperia T, TL, TX, V] peetr_:
Ok. I just tested one thing. The same way, I can relock bootloader, I can also reunlock bootloader, using the unlocking number from Sony in hex format.

Anyone tested to get the number from Sony site and flash it with preset.ta?

This is preset.ta for reunlocking - replace ** with hex symbols of your unlocking number

// [ReUnlock bootloader]
02

000008B2 0010 ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **

This is simlock.ta, which can be theoretically renamed to preset.ta and flashed, but who knows what happens.

Weird is, that each simlock.ta has different number of symbols.

HEX:

// [SIMLOCK S1]
02

000007DA 0141 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 02 00 05 0A 02 00 00 00 0A 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 02 00 00 00 0A 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 4D 4F 50
5F 49 44 3D 22 38 32 34 32 22 3B 4F 50 5F 4E 41
4D 45 3D 22 43 75 73 74 6F 6D 69 7A 65 64 20 43
45 31 22 3B 43 44 41 5F 4E 52 3D 22 31 32 36 38
2D 33 31 39 34 22 3B 52 4F 4F 54 49 4E 47 5F 41
4C 4C 4F 57 45 44 3D 22 31 22 3B 00 00 00 09 00
07 30 30 31 30 31 2D 2A 00 00 00 00 00 00 00 00
00 00 00 00 02 00 00 00 0A 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00
00 00 0A 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 02 00 00 00 0A 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 02 00 00 00 0A 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00

ASCII:

something...OP_ID="8242";OP_NAME="Customized CE1";CDA_NR="1268-3194";ROOTING_ALLOWED="1";...something
[Sony Xperia T, TL, TX, V] matt4321:
I found that they use some of these algorithms: http://www.w3.org/TR/xmlsec-algorithms/ to make the ta secure.

So I'm thinking we try do it in reverse with an unlocked ta and key then we would know what to do in the correct order....? thoughts?

There are some from this signed info bit but there are a few more lurking around

<SignedInfo>
<CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
</CanonicalizationMethod>
<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1">
</SignatureMethod>
<Reference URI="#node">
<Transforms>
<Transform Algorithm="http://www.octopus-drm.com/octopus/specs/cbs-1_0"></Transform>
</Transforms>
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1">
</DigestMethod>
<DigestValue>axQveCiPf9Q7wn958RRi5ohD130=</DigestValue>
</Reference>
</SignedInfo>

[MENTION=3110233]peetr_[/MENTION]

Yeah my simunlock.ta looks different, I'm confused between the connection (if any) of these.

I also have a different OP_ID="8242" to you, mine is 24, not sure of the significance of that.....

EDIT: It also seems they are using the W3 digital signature initiative: http://www.w3.org/PICS/DSig/RSA-SHA1_1_0.html
[Sony Xperia T, TL, TX, V] peetr_:
I guess that the signature is unbreakable. These signature things in TA has probably something to do with drm keys, and other similar things. System takes it from here.

I think the only way to get somewhere, is finding some workaround or hole, using sony way of changing things in TA partition. But maybe, some of these parts could be never changed. Who knows?
[Sony Xperia T, TL, TX, V] peetr_:
Well. Changing rooting status with preset.ta is nothing special. It is possible. You only need good nerves. :) And dump of whole 7DA adress from your TA.

I just changed 1 to 0.

Side effect is no mobile service. I guess you have to choose - unlocked bootloader without mobile service or locked bootloader with mobile service.

Changing 0 to 1 makes service available again.

As you can see, I tested it on already unlocked bootloader (locking it permanently). So I don't know if it works backwards. But I do not see any reason, why not.

You only need another tester. I did all I could.

And it would be good, if someone with unlockable bootloader dumps his 7DA before first unlock and compares it with 7DA after unlocking. Or compare with restored not unlocked TA.

And yes, with rooting allowed 0, fastboot and custom kernels are no longer working for me, even if I flash my unlocking number with preset.ta.
[Sony Xperia T, TL, TX, V] matt4321:
If changing it looses mobile service, would changing it to unlock and then restoring after bring back mobile service. Thoughts?
[Sony Xperia T, TL, TX, V] peetr_:
Yes, but you will be locked again.

Btw. if nothing, you can at least root and test things this way. I think this procedure is not for everyone, but once you make your unlock and lock ftf, you can change your device's state very easily.

Comparison between 7DA before and after first unlock would be better, just to be sure.

But if you have your TA backed up, to change it back to previous state, I think there's nothing to break.

And one more thing. It looks to me that flashmode cannot be broken. Am I right? So you can always flash something.
[Sony Xperia T, TL, TX, V] matt4321:
I seem to recall in the Xperia U forum that some bricks were made from tampering with the TA, if a bad/corrupt TA is flashed then you can't get into flashmode. That's what was established from the U forums
[Sony Xperia T, TL, TX, V] NuriJ:
In flashtool? How do you change it?
[Sony Xperia T, TL, TX, V] peetr_:
Look at some simlock.ta (Nurij - from V!) this is how should look your preset.ta. Dump your TA with flashtool, find 7DA (don't know if it's the same for V! - it must be the same adress like in simlock.ta) adress in the dump and copy whole content to your preset.ta, edit it, to look like simlock.ta (number after 7DA is number of symbols - check it). Better check if whole 7DA is corresponding with whole TA partition dump (find this sequence of symbols, it is not real 7DA adress from whole partition). Find the "1" symbol (next to rooting allowed sequence of course) in the dump and change it to "0".

Save preset.ta and flash it with relock bootloader ftf for example.
[Sony Xperia T, TL, TX, V] peetr_:
So, after some more testing, I can say that flashing 7DA with whatever, is completely safe. It rearranges TA partition (TA begins then at 128KB and first part is swapped with second part), but nothing bad happens (if you have your TA backup for reverting the changes).

I guess the same rearrangement happens, when you relock bootloader with relock.ftf.

But I found, that any change I do in 7DA unit makes my bootloader unlock not allowed and mobile service unavailable, until I change it back again.

Neither trying to use 7DA unit from different unlockable device doesn't work (still bootloader unlock not allowed). Thanks Timin8r.

Looks to me like md5 of 7DA unit and rck_h code are somehow connected and checked somewhere.

It means that this won't work for unlocking.

But you can do some more testing even on not unlockable bootloader.

Maybe someone will come with some improvement.
[Sony Xperia T, TL, TX, V] Galcactus:
Haven't had the chance to look through all of this, but looks like it might have some relevant information:

http://xdaforums.com/showthread.php?t=1856327

I'm still quietly optimistic, keep on investigating!

Galcactus out.
[Sony Xperia T, TL, TX, V] bulanula:
What was original state of your device ?

Was it "Bootloader unlock allowed : NO" or "Bootloader unlock allowed : YES" when you bought it ?

I want to try this on my Xperia P. I don't care about modem so I don't mind if I lose it temporarily.

However, I think on devices that came with "Bootloader unlock allowed : NO" from factory you cannot even get into fastboot mode ???
[Sony Xperia T, TL, TX, V] peetr_:
It was unlock allowed YES. But I found later, that there is only one combination of hex characters, that make the bootloader unlockable. The stock one from my device. Everything else makes the bootloader not unlockable. Even if it's stock combination from different device.

You can't get in fastboot, but you can change TA, by flashing preset.ta. Even if you brake something, I believe that the flash mode is always available.

But you should know very well, what are you doing.
[Sony Xperia T, TL, TX, V] bulanula:
First of all thank you very much for answering !

So, after I modify the "ROOTING_ALLOWED=0" to "ROOTING_ALLOWED=1" and flash preset.ta, how can I unlock the bootloader without fastboot mode ?
[Sony Xperia T, TL, TX, V] peetr_:
If changing it to "1" would work (but I found that it most probably won't and your bootloader will stay locked), fastboot mode would be automatically working too.

Read each of my posts in this thread. Basically, I already wrote this.
[Sony Xperia T, TL, TX, V] bulanula:
I already read all of your posts in this thread 2-3 times.

So, no more flashing Sony unlock code through preset.ta file like in page 2 ?

I am not very sure what steps to follow exactly, even after reading all your posts.

Maybe you can make a clear step by step if you can sometime of exactly what you did ?
[Sony Xperia T, TL, TX, V] peetr_:
You can flash the unlock code, but it won't make any difference, unless you make the first part (rooting allowed) working. And it seems that it won't work without the proper rck_h code or maybe something else.

First make some dumps of TA in flash tool and with DD command and try to understand the structure. Compare TA with bootloader lock preset.ta and some simlock.ta. Then you can try to make some changes.

You need some hex editor with hex/ascii converter and some tool for comparing.
[Sony Xperia T, TL, TX, V] bulanula:
What would be interesting to see is a TA dump from a "virgin" device that has never had the bootloader unlocked but that has "Bootloader unlock allowed: YES" to see if the RCK_H code is present in that device TA dump.

I looked at my TA and there is no RCK_H code at all. I can post here what it looks like :

BASE 16 HEXADECIMAL

4F 50 5F 49 44 3D 22 32 31 22 3B 4F 50 5F 4E 41 4D 45 3D 22 33 22 3B 43 44 41 5F 4E 52 3D 22 31 32 36 31 2D 33 33 35 30 22 3B 52 4F 4F 54 49 4E 47 5F 41 4C 4C 4F 57 45 44 3D 22 30 22 3B 00 43 53 45 52 56 45 52 49 44 3D 22 62 6D 63 73 65 63 73 30 32 22 3B 41 55 54 48 43 45 52 54 3D 22 55 4E 4B 4E 4F 57 4E 22 3B

ASCII

OP_ID="21";OP_NAME="3";CDA_NR="1261-3350";ROOTING_ALLOWED="0";[0]CSERVERID="bmcsecs02";AUTHCERT="UNKNOWN";

As you can see, there is no value for RCK_H in my unmodified TA dump. So I need to know the procedure exactly that worked for you.

To get the 0 into a 1 I need to modify this portion "3D 22 30 22 3B" which is ZERO

to "3D 22 31 22 3B" which is ONE.
[Sony Xperia T, TL, TX, V] peetr_:
I've had the TA backup before unlocking from Timin8r. It is always there (rck_h), if bootloader is unlockable.

Exactly. That's the way, how to change it. You can try it, but I doubt it will make some difference.

Don't forget to backup your TA. It will be rearranged for some reason. Will be starting at 128KB.
[Sony Xperia T, TL, TX, V] am486:
Do you guys need more Backups for further research? I can send you my locked and unlocked bootloader.
[Sony Xperia T, TL, TX, V] Galcactus:
Yes please, before, after and also your unlock code that Sony emailed you if possible?
[Sony Xperia T, TL, TX, V] am486:
You got a PN ;)
[Sony Xperia T, TL, TX, V] manraj74:
my xperia miro st23i (factory unlocked) get simlocked due to this file.

// [SIMLOCK S1]

02

000007DA 0141 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 02 00 05 0A 02 00 00 00 0A 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 02 00 00 00 0A 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 4D 4F 50

5F 49 44 3D 22 38 32 34 32 22 3B 4F 50 5F 4E 41

4D 45 3D 22 43 75 73 74 6F 6D 69 7A 65 64 20 43

45 31 22 3B 43 44 41 5F 4E 52 3D 22 31 32 36 36

2D 35 39 33 33 22 3B 52 4F 4F 54 49 4E 47 5F 41

4C 4C 4F 57 45 44 3D 22 31 22 3B 00 00 00 09 00

07 30 30 31 30 31 2D 2A 00 00 00 00 00 00 00 00

00 00 00 00 02 00 00 00 0A 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00

00 00 0A 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 02 00 00 00 0A 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 02 00 00 00 0A 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00

need help ASAP bro.
[Sony Xperia T, TL, TX, V] peetr_:
Restore your TA backup.
[Sony Xperia T, TL, TX, V] mpiekp:
Has anyone with a locked bl tried getting a code from Sony and adding it to the right area then flashing modified ta?
[Sony Xperia T, TL, TX, V] Blagus:
I was testing the same thing on Xperia Play. IIRC, RCK_H code is not present in allowed=0 phones and simply adding the code doesn't work. I'd have to dig out the files to be sure, though. I have backups of locked and unlocked TAs from a several phones, as well as non-unlockable phones.

And since the 7DA is signed, modifying it breaks the simlock stuff and there's no network, but yes, it allows BL unlock because S1Boot doesn't check signature of 7DA when checking for Rooting_allowed flag, at least not based on the data I have (but I think it's more than enough).
[Sony Xperia T, TL, TX, V] chadouming:
hey, i'm bringing back this thread alive cause i recently got a Xperia Z1 and bootloader is not unlockable. I'd be willing to make some test and drop stuff you want. You can hit me on freenode or on hangouts. I have a hard time right now with a phone that is not unlocked and not rooted.
[Sony Xperia T, TL, TX, V] Olivier:
Hi,

you could help with KEXEC for locked bootloaders.

Gesendet von meinem Xperia S mit Tapatalk
[Sony Xperia T, TL, TX, V] Galcactus:
You say that it breaks the SIM lock stuff but gets you BL unlock allowed? Then why not just just get your phone SIM unlocked and do that? Or am I missing the point here..?

Care to do any more investigating into this?
[Sony Xperia T, TL, TX, V] Blagus:
If it was that simple then everyone would know about it.

When I say simlock I mean the simlock area (7DA) on the phone which is signed with RSA key. If it's broken, network doesn't work, as I said in the previous post, and you can't recover it and keep BL unlocked.

What's a little bit strange is that S1Boot is made to ignore simlock if the BL is unlocked, but there's still no network, though I could be wrong, maybe it still performs the signature check and only ignores the valid signed simlock area, I don't have enough data to be sure.

The reason why the BL unlock works this way is because that signature is not checked when looking for rooting_allowed value, but it is when it comes to network - I guess they thought the mobile phone isn't worth that much without network regardless of the BL being unlocked, so they made it that way.
[Sony Xperia T, TL, TX, V] Olivier:
So to sum up - unofficial bootloader unlocking is something we can only dream of...? I mean there are not many people interested in it and all the devs have unlocked phones nowadays (I think it was different in X8/10 times)...

Gesendet von meinem Xperia S mit Tapatalk
[Sony Xperia T, TL, TX, V] Blagus:
Probably. Unless someone dumps and reverses S1Boot and finds some weakness there, or another QC bug is found.
[Sony Xperia T, TL, TX, V] chadouming:
https://www.codeaurora.org/projects...arsing-during-boot-image-authentication-leads

let's keep hope xD
[Sony Xperia T, TL, TX, V] matt4321:
I don't think this is any use as it involves Little Kernel (LK), which in itself needs the bootloader to be unlocked
[Sony Xperia T, TL, TX, V] Blagus:
No use, it's LK bootloader, and as I already said, Sony uses S1Boot.
[Sony Xperia T, TL, TX, V] bolillo:
In those times that was the only phone Sony had so it was the only phone to develop on, today there are just to many choices and since some of the phones come unlockable already the vas majority of UK phones are unlocked friendly but in the US all of then come locked to the teeth, when x10 was around I think all x10's were blocked no matter where you bought it from
[Sony Xperia T, TL, TX, V] killa92:
Did anyone have luck with this? I have removed my simlock and allowed root access. But now I want to flash third party firmware and it says it can't be unlocked. I still have an unlock code of Sony. Can't we force this code in?
[Sony Xperia T, TL, TX, V] matt4321:
Currently there is no way around it. Unfortunately we have to survive with stock based ROMs
[Sony Xperia T, TL, TX, V] talayy:
Hi there, can I know how did you remove simlock? if not officially.
[JASJAR, XDA Exec, MDA Pro General] dherrero:
Hi,

I have a Jasjar and i am going to travel to Bali and thailandia. I would like if my jasjar will work as phone is those countries (gsm band) and also if there will be GPRS/UMTS avability.

Thans
[JASJAR, XDA Exec, MDA Pro General] thaihugo:
Hi,

I'm sure you will enjoy thailand and bali. I'm not sure if you are on holliday that you really want your GSM to work. Sounds like a phone addiction to me ;-)

Anyway. You GSM band will work, and you will be able to send and receive phone calls. Roaming charge will cost you one or two lives, and I would'nt give my number to my best ennemy, as a simple phone call could cost you horrible charge.

For GPRS/UMTS, thailand and bali are third world country. You can find some wifi hotspots, but definitly no 3G. And GPRS is not hte main business feature there.

Funnily, you have a great 3G network in malaysia, which is in between. Guess you can't have the nice beaches and the network coverage ;-)

You have some prepaid card service but mostly expensive, and usually bundled with a phone.

Don't worry for electricity, don't bring your solar charger, except if you plan to go on a lonely island far far away. You always get a plug there. Take your plug convertor, it's dual round pin there.

Hope this help!
[JASJAR, XDA Exec, MDA Pro General] dherrero:
Sure, Thanks :D
[JASJAR, XDA Exec, MDA Pro General] surinamer123:
Hi

i went to Bali and Thailand several times.

And the GSM network their is in my opion one of the best!

You can buy an prepaid card in Thailand for around 200 Baht (4 us dollar). With this you get a phonenumber and some fee!

So you can call in the country very cheap because of the fact you have and number of Thailand. People that will call you also have no problem (you dont pay for their call!)

Ok so enjoy your stay! Which place do you go from Thailand?
[JASJAR, XDA Exec, MDA Pro General] dherrero:
Thanks. I go to Bangkok. Is there gprs?
[JASJAR, XDA Exec, MDA Pro General] noname_nick:
Thailand GPRS

Thailand has a great network. You can buy a 400 Baht sim card with gprs that costs 0.012 per KB (orange). Good coverage. Only GPRS though.
[JASJAR, XDA Exec, MDA Pro General] dherrero:
thanks :D