Anybody know how I can get the black swype like the commercials??

Sent from my T-mobile G2 using XDA App

I just made a script for swype to restore itself (actually it's gscript restoring it) and then reboot the phone, assuming you have the files on your sdcard and also assuming you are using the Nexus S 4G swype.

If you are using a different version of swype, just edit the script to how you need it. This approach takes less time and only one reboot.

Here it is...

You can run this one of 2.5 ways...

Through Gscript, you will create the script with "Needs su" checked

mount -o remount,rw /system
cp /sdcard/Nexus-S-4G/Swype.apk /system/app/Swype.apk
cp /sdcard/Nexus-S-4G/libSwypeCore.3.25.91.30637.so /system/lib/libSwypeCore.3.25.91.30637.so
chmod 644 /system/app/Swype.apk
chmod 644 /system/lib/libSwypeCore.3.25.91.30637.so
sync
reboot

Through adb, put the script on the root of your sdcard

adb devices
adb shell
su
sh /sdcard/Sywpe-Restore.sh

You will follow the same steps for adb if you want to use the terminal on your device.

Hope this helps!

No methods have worked for me

---

Since upgrading to CyanogenMod 7.1.0 for the G2 I have been unable to get swype back. I used to be able to use the swype restore. Now it tells me I do not have the file in any of my nandroids. So tried manually. Keep getting error that its for another device and will only work with limited functionality, basically allowing me to only type direct words and no swype. Tried restoring from old TitaniumBackup files, and nandroid backups. Went so far as to dl stock G2 rom extract and try manually installing still same error. Tried everything listed here so far. Really don't like the beta version but it seems to install and work without issue. Any other suggestions on how I could go about installing the older version again?


---------------

found my answer in post 123. Ended up having to dl stock rom for G2, manually extract files, place files on phone, set permissions, edit build.prop file to T-Mobile G2 from the one that CM has listed. Also used same procedure on wife's G2x to recover its lost swype.

Hope this helps other people.

German layout?

---

Hello

Yesterday my SGS (DarkyRom9.5) didn't boot, so I decided to switch to CyanogenMod7 today. All works fine and fast. But I missed Swype, so I tried RestoreSwype.
It works too, but one thing I'm missing!

How can I get the german keyboard-layout? There's only english layout - also in settings!

btw: I tried SwypeBeta, but this hangs up with errors, so I deinstalled it.

Is there anybody who knows a way to getting german layout to swype (restored by RestoreSwype)???

Thanks
EnzephaloN

Odd. I've got a CWM backup from before I upgraded to CM, but the SwypeRecover app can't find Swype inside it. Does the recovery App also work on a Galaxy Ace? or is it phone specific?

Guaranteed Swype Fix

---

You have to make changes to your build.prop in order for Swype to recognize your device as a valid host. In particular, make note of the elements below that identify T-Mobile and the model ID:

ro.com.google.clientidbase=android-tmobile-us
ro.com.google.clientidbase.vs=android-hms-tmobile-us
ro.com.google.clientidbase.ms=android-hms-tmobile-us
ro.product.model=T-Mobile G2
# begin build properties
# autogenerated by buildinfo.sh
ro.aa.maincid=T-MOB010
ro.aa.cidlist=T-MOB010
ro.aa.project=Vision_Gingerbread_S
ro.aa.modelid=PC1010000
ro.build.host=AA125
ro.product.brand=tmobile
ro.product.name=htc_vision
ro.product.device=vision
ro.product.board=vision
# end build properties
#
# system.prop for mahimahi
#


#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-tmobile-us
ro.com.google.clientidbase.vs=android-hms-tmobile-us
ro.com.google.clientidbase.ms=android-hms-tmobile-us


Make these changes in addition to adding the apk and the two Swype-related so files and you'll be golden.

Cheers

Does this recover your custom dictionary also?

Sent from my HTC Vision using xda premium

Custom Dict Recovery ...

---

Originally Posted by Critical Jeff

Does this recover your custom dictionary also?

Sent from my HTC Vision using xda premium

Not that I'm aware of ...

Swype from SGSII TW Android to CM7.1

---

Thank you guys for all your help! With your advices, I just managed to get my swype copy from Samsungs original TW bloated Android to CM7.1 on my Samsung Galaxy S2 and I want to give a brief description of the procedure for newbies like me to do it. Maybe this is not the right threat, but it's the one google gives you asking for problems like this...

So after following the first steps of the CM guide on how to get CM onto the SGSII, I created a backup of my TW Android copy. Using unyaffs, to get the TW Android and CM accessible on my PC, I extracted the two files (.so and .apk) necessary to get swpye to work and copied them into the appropriate places of my CM copy.

Next, you need to edit build.prop of your CM copy, as swype apparently checks some parameters (don't know which actually) to identify your phone and see if its supposed to run on it. If you don't adjust build.prop, swype will have limited functionality which means it works just like a regular keyboard:/

I changed the following parameters of CM's build.prop to the values given in TW Android:

ro.build.version.release
ro.build.date
ro.build.date.utc
ro.product.device
ro.product.locale.language
ro.product.locale.region
ro.build.product
ro.build.description
ro.build.description
ro.build.fingerprint
ro.com.google.clientidbase

Also, I added the following samsung specific properties to the CM copy of build.prop:

# Samsung Specific Properties
ro.build.PDA
ro.build.hidden_ver
ro.build.changelist
ro.tether.denied
ro.flash.resolution

After that, just re-zip your modified CM copy and install it following the official CM update guide. I am not sure (in fact I highly doubt that all these parameters are necessary for swype to work or whether some of the changes will cause problems with other apps... However, it works for me for a few days now and I am really glad for the advice of you guys here.

Hope this helps someone...

Cheers!

Originally Posted by robtopSGSII

Next, you need to edit build.prop of your CM copy, as swype apparently checks some parameters (don't know which actually) to identify your phone and see if its supposed to run on it. If you don't adjust build.prop, swype will have limited functionality which means it works just like a regular keyboard:/

I changed the following parameters of CM's build.prop to the values given in TW Android:

ro.build.version.release
ro.build.date
ro.build.date.utc
ro.product.device
ro.product.locale.language
ro.product.locale.region
ro.build.product
ro.build.description
ro.build.description
ro.build.fingerprint
ro.com.google.clientidbase

Thanks for your research into this. We're referring to the file "/system/build.prop". You can remount your partition as read/write and save the file (then reboot) instead of inserting it into your Cyanogenmod installation file and re-installing.

Mainly, you need to ensure that the product identifiers match from the old to the new. I'm not sure which one exactly Swype will check, but I copied:

ro.product.model
ro.product.brand
ro.product.name
ro.product.device
ro.product.board