Database Users

Changing the default font of your Aria

Changing the default font of your Aria
After trying without success different methods to change the fonts in my Aria, I decided to write the results of my experiences (when I was finally able to achieve what I wanted) in order to help others that my be trying to do so.
As always, before even trying to do any mod to your precious Aria, DO A NANDROID BACKUP!
Disclaimer: Try this under your own risk, I can not be held responsible for anything that can happen to your phone.
1.- You need to have your Aria rooted because these fonts are stored inside the Dalvik file system and by having “root” access, you can access these files in read-write mode.
2.- On your PC , download any True Type Font (files with extension .ttf) of your choice , you need two variants of these fonts “Normal” and “Bold”. You can browse and download fonts for free from the web.
3.- I, personally like CaviarDreams (Normal type) and CaviarDreams-Bold (Bold type).
4.- In your PC's main unit (in most cases, it would be C:\), create a folder and name it androidfonts, then, save the fonts you just downloaded in that folder.
5.- Whichever fonts you choose, you will have to rename them as DroidSans and DroidSans-Bold respectively.
6.- Turn your phone off. Enter recovery mode by holding "volume down" and "power" buttons at the same time when you turn on your phone. Keep holding for about 10 seconds. You are now in recovery mode if it says "clockwork" at the top.
7.- On the phone's recovery menu, navigate to Partitions, once there, select “mount system”, that will allow you to access files in read-write mode and make the desired changes.
8.- Now, you can connect your phone to the computer through the USB cable.
9.- In your computer, using adb* tool, write the following commands:
C:\Android\tools
adb push c:\androidfonts\xxxxxxxx.ttf /system/fonts/DroidSans.ttf
The above command will copy the new font.
Repeat this command to overwrite DroidSans-Bold.
Remember: xxxxxxxx.ttf are the fonts you previously downloaded and renamed.
10.- In your computer, type exit to exit adb.
11.- Do not disconnect your phone yet.
12.- On your phone's partitions menu, unmount your system.
13.- In the phone's recovery menu, go back and select reboot system.
You can now unplug your usb cable to disconnect your phone from the PC.
*You enter adb by launching Command Prompt aka as cmd prompt on your computer (better if you launch it as Administrator by right clicking on it)
Once you've launched cmd prompt, write in the cmd prompt box the following commands:
C:\Android(or whatever name you gave to your sdk file)\tools
Enjoy your new font.

If you search for fonts on the forums you can find a link to dozens of font packs that can be flashed from recovery the same way you flash a rom. You don't even need to clear any caches just flash the zip.
Sent from my Liberty using XDA App

hungmung said:
If you search for fonts on the forums you can find a link to dozens of font packs that can be flashed from recovery the same way you flash a rom. You don't even need to clear any caches just flash the zip.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Thanks for your comment.
The reason I started this thread is because none of those fonts were of my liking, as I stated, I just wanted to share my experience in changing the font to one I really want and like.
Besides, by doing this, helps anyone practice their modding skills.

http://www.xda-developers.com/android/type-fresh-change-fonts-on-your-rooted-android-device/

Thanks for taking the time to write out this tutorial, I appreciate your efforts!
churapa said:
9.- In your computer, using adb tool, write the following commands:
Click to expand...
Click to collapse
I'm sure I can find it and right after I post this, I will start looking, but you might want to provide a link or a description on where to find "adb tool". That's the only part of your instructions that I don't think are crystal clear.

911jason said:
Thanks for taking the time to write out this tutorial, I appreciate your efforts!
I'm sure I can find it and right after I post this, I will start looking, but you might want to provide a link or a description on where to find "adb tool". That's the only part of your instructions that I don't think are crystal clear.
Click to expand...
Click to collapse
Updated instructions on first post. Also, remember post #235 from The Homescreen Snapshots thread?, there I linked what adb is.

hungmung said:
If you search for fonts on the forums you can find a link to dozens of font packs that can be flashed from recovery the same way you flash a rom. You don't even need to clear any caches just flash the zip.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
The thing about this is they are font PACKS...what if you don't want all those extra fonts? That's just wasted space IMO. Hence why churupa's way of doing this is better, though it may be a little more time consuming

I think you misunderstand there are dozens of separate packs you can download and each one is only for one font it just makes the process faster because you can just go into recovery and flash the zip
Sent from my Liberty using XDA App

So I found a font I like, but it's just slightly larger than the default font which causes some various issues with text not fitting like it should in Widgets. Is there a setting somewhere that we can access to adjust the font size a notch or two?

You can see what I mean in these screen caps. Notice on the home screen how the line coming down from SimiClock no longer has an even gap to run through in the weather widget and between the battery and data widgets. The only other problem I ran into was in the various settings menus for widgets where there is a numeric setting box, the font in those boxes is so large you can only see the bottom half of the numbers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

So I found a better match size-wise, it's not quite as cool of a font, but it still has some style. This one is Ubuntu and is available free here:
http://www.fontsquirrel.com/fonts/ubuntu
I used Ubuntu Regular for both Clockopia.ttf (LockScreen) and DroidSans.ttf
and I used Ubuntu Bold for DroidSans-Bold.ttf

911jason said:
You can see what I mean in these screen caps. Notice on the home screen how the line coming down from SimiClock no longer has an even gap to run through in the weather widget and between the battery and data widgets. The only other problem I ran into was in the various settings menus for widgets where there is a numeric setting box, the font in those boxes is so large you can only see the bottom half of the numbers.
Click to expand...
Click to collapse
What is that font?

Ummm... good question! Can't believe I left that out... I'm at work now, but I'll try to remember to post the name of the font later today.

Javi97100 said:
What is that font?
Click to expand...
Click to collapse
It is Sansumi.

911jason said:
It is Sansumi.
Click to expand...
Click to collapse
Um how did u install it cuz i tried flashing to through recovery and nothing happend? Any ideas

That zip file is just the fonts by themselves. You need to go to the first post in the thread and follow those instructions if you want to install the font on your phone.

What if you can't find the bold version of a font? Can I just rename a copy of the regular as bold?

tilt4life2 said:
What if you can't find the bold version of a font? Can I just rename a copy of the regular as bold?
Click to expand...
Click to collapse
sure, it just that text that should be bolded won't be bold.

kevina90 said:
sure, it just that text that should be bolded won't be bold.
Click to expand...
Click to collapse
I did everything here but I keep getting the following message:
cannot stat 'e:\androidfonts\DroidSans.tff': no such file or directory
E: is my main drive. I have SDK tools in F: drive. I even tried to move the androidfonts folder to Tools and then the font files to tools but I keep getting same message.
Edit: Problem was fixed thanks to DrSwattt's help.

Just found a font that is nearly perfectly equivalent to DroidSans in metrics: Leelawadee. It comes with Windows Vista/7. It's actually a Thai font but it has the complete latin character set. Using Leelawadee to replace DroidSans, you don't need to worry that the new font does not fit your theme. It's not fancy, but good enough for daily use.

Free 50Gb Online Storage before 31st December 2011

Hurry, whilst stocks last!
Get it here
Make sure you edit the lines of the build.prop exactly as they are shown in the above thread (or see post 6 below).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: I have decided to treat this as an IQ test. If it doesn't work for you, it means that you are incapable of reading, writing and thinking for yourself. You should reflect long and hard on your inability to perform basic tasks and should probably not post things such as 'it doesn't work!'. That is basically the same as admitting that you are dumb and admitting it in a public forum.

This works

trumpetboy101 said:
This works
Click to expand...
Click to collapse
I know. I wouldn't have posted it otherwise
Tell all your friends. It will work on any Android device.

Thank

This unfortunately does not work for me as I cannot get my phone model to show as VS910 4G.
Every time I edit my build.prop file (as stated in original post) it does not save any changes. Any ideas or clues as to what I could be doing wrong.
I am rooted on 2.3.5.

ajoshi said:
This unfortunately does not work for me as I cannot get my phone model to show as VS910 4G.
Every time I edit my build.prop file (as stated in original post) it does not save any changes. Any ideas or clues as to what I could be doing wrong.
I am rooted on 2.3.5.
Click to expand...
Click to collapse
This does work. My screenshot proves it. I was waiting to see how long it took someone to screw up something this basic.
Did you actually read and follow the instructions?
OK, do this (by the way this is what is said in the thread I linked to)...
1. Make sure you are rooted
2. Open system/build.prop in a text editor
3. Change the lines in your build.prop that read
Code:
ro.product.model=GT-N7000
ro.product.brand=samsung
to read
Code:
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
4. Reboot (which I am guessing you didn't do)
5. Download the 'Box' app from the market and sign up for an account
6. Edit the build.prop back to its original state
7. Reboot again

If I only had seen before :'(
Sent from my Xoom on Tiamat

[David] said:
If I only had seen before :'(
Sent from my Xoom on Tiamat
Click to expand...
Click to collapse
What do you mean? It is available until the end of 2011.
You can do it now.

Like magic!
Thanks

Doesn't work.
Everytime i reboot the Galaxy Note, those lines are changed to original values automatically.
I am on 2.3.6 , looks like some more values needs to be changed.

bmunshi said:
Doesn't work.
Everytime i reboot the Galaxy Note, those lines are changed to original values automatically.
I am on 2.3.6 , looks like some more values needs to be changed.
Click to expand...
Click to collapse
Of course!!
Because you can't do it, there is obviously a problem!!
If you are rooted and can't edit the build.prop on your device, copy it on to your SD card and copy it to a computer and edit it using Notepad or Notepad++. Then copy it back to your SD card and then paste it back in to your system partion. Then reboot.
Next time try using some common sense and don't blame others for your own deficiencies.

Works fine, all done with ES explorer.
Make sure /system is mounted as writeable.
You get swype complaining about a licence issue but this goes away when you set the model and manufacturer back.

nobnut said:
This does work. My screenshot proves it. I was waiting to see how long it took someone to screw up something this basic.
Did you actually read and follow the instructions?
OK, do this (by the way this is what is said in the thread I linked to)...
1. Make sure you are rooted
2. Open system/build.prop in a text editor
3. Change the lines in your build.prop that read
Code:
ro.product.model=GT-N7000
ro.product.brand=samsung
to read
Code:
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
4. Reboot (which I am guessing you didn't do)
5. Download the 'Box' app from the market and sign up for an account
6. Edit the build.prop back to its original state
7. Reboot again
Click to expand...
Click to collapse
thanks for the trick. i was using my sister SG2 and i notice there's more free games in samsung apps than the one in SGN. can i use the same method to download games by tricking samsung apps 2? the SD data should be the same...would be great if you can tell me what is the exact code for SG2.

foochuangyeh said:
thanks for the trick. i was using my sister SG2 and i notice there's more free games in samsung apps than the one in SGN. can i use the same method to download games by tricking samsung apps 2? the SD data should be the same...would be great if you can tell me what is the exact code for SG2.
Click to expand...
Click to collapse
Before you try this, have a think for a second... What do you think the reason is for this difference in the number of apps/games? The SGSII has a smaller screen with different dpi settings. The apps that don't show for the Note will probably either not run, or are not compatible with it.
Anyway, if you want to try, change any reference to N7000 to whatever shows for your sister's SGSII (there are a few of these) and change the lines
Code:
ro.build.description=GT-N7000-user 2.3.5 GINGERBREAD XXKJ4 release-keys
ro.build.fingerprint=samsung/GT-N7000/GT-N7000:2.3.5/GINGERBREAD/XXKJ4:user/release-keys
to whatever shows in your sister's build.prop.
Make sure you backup your build.prop to your SD card (you can just copy it back when you have finished rather than editing it again). Just in case, also have a Nandroid backup to hand if you need it.

nobnut said:
Of course!!
Because you can't do it, there is obviously a problem!!
If you are rooted and can't edit the build.prop on your device, copy it on to your SD card and copy it to a computer and edit it using Notepad or Notepad++. Then copy it back to your SD card and then paste it back in to your system partion. Then reboot.
Next time try using some common sense and don't blame others for your own deficiencies.
Click to expand...
Click to collapse
OOps that's rude. Please dont assume others are stupid.
I am rooted and can edit the build.prop, after editing and saving if i reopen it shows the new value.
But once phone is rebooted it changes back to original value, that is what i meant.
BTW, just check your old updates, in first you asked to change the .Brand and then in the same thread asked to change back the .manufacture value. I am not blaming, it might be typo or something.
End result, still there are some more values needs to be changed.

bmunshi said:
OOps that's rude. Please dont assume others are stupid.
I am rooted and can edit the build.prop, after editing and saving if i reopen it shows the new value.
But once phone is rebooted it changes back to original value, that is what i meant.
BTW, just check your old updates, in first you asked to change the .Brand and then in the same thread asked to change back the .manufacture value. I am not blaming, it might be typo or something.
Click to expand...
Click to collapse
[mod edit]
I made no mistake. You have to change the lines from the first ones to the second ones. There are differences between the two manufacturers' build.props.
I am not blaming, I am just pointing out that people need to learn to read, think and comprehend.
End result, still there are some more values needs to be changed.
Click to expand...
Click to collapse
You are wrong. [mod edit]

Christmas is over then

Confirming, if you follow the basic instructions, this works PERFECTLY.
50GB available to me. Cheers OP.

straxusii said:
Christmas is over then
Click to expand...
Click to collapse
Oh man! Please don't introduce another concept such as Christmas to this thread. Some XDA users' heads will explode trying to grapple with that as well as editing two lines in a build.prop.
AdzUK said:
Confirming, if you follow the basic instructions, this works PERFECTLY.
50GB available to me. Cheers OP.
Click to expand...
Click to collapse
Hallelujah!!
EDIT: At the risk of causing severe haemorrhaging in some users... try this:
Once you have created your account, clear the 'Box' app data and cache in Settings and then using another email address, get another 50Gb. Repeat until you get bored.
Shabba!

Woking great!
Working great, and all i had to do was to change only 2 lines in buid.prop using ES File explorer with 2 options activated: Root Explorer and Mount File System.
1. Be sure that you have root
2. Install ES File explorer and Options and check this: Root Explorer and Mount File System
3. Navigate to /system. Long press on buid.prop , open as text.
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
Click to expand...
Click to collapse
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
Click to expand...
Click to collapse
5. reboot
6. install from market box (box.net)
7. Create the account. A confirmation message will appear that you have 50 GB capacity.
8. Again from EFS File Explorer navigate to /system. Check that you have a file named build.prop.bak and if so, delete buid.prop. Rename build.prop.bak into build.prop. Now you can disable from options : "Root Explorer" and "Mount File System"
9. Reboot
10. Enjoy your amizing phone
Note: I had done this on KL7 with stock kernel.

[MMS][MOD] Softbank Japan HTC Sense & Stock Mms app (updated 7 Nov)

These are confirmed working ONLY on the Android version listed below on the SOFTBANK network in JAPAN and requires ROOT ACCESS unless you are already on stock Android
SMS's and MMS's in Japan are called S'Mail. The main difference is this: You can either enter the phone number or the email of your recipient and any length of text or attachments can be sent (Works like emails, but it also uses phone numbers as an address). The problem is that unless your Rom or phone comes from Japan, you will be limited to SMS functionality only, if you are lucky.
The main problem is that the company requires a specific useragent to be specidied by the messaging app. I use Softbank here in Tokyo so I have made some tweaks get the apps to work for a few versions of Android that I have been using. I thought I would share them in the hopes of helping others out too.
ICE CREAM SANDWICH - Android 4.0.x
Stock / AOSP Android
View attachment Mms-ICS-4.0.4.apk - From stock Android 4.0.4 with only the user-agent changed. (Updated 20 Aug 2012)
View attachment Mms-ICS+Emoji.apk - Styled work from here, and useragent changed by Kremlin987(Updated 3 June 2012)
HTC Sense Instructions
I have finally found a way to get the stock Sense messaging app to work. It actually works much better than the stock android once you get it going. There is no app to install. Sense copies the UserAgent information from a default file into it's internal database the first time you boot your phone after a factory reset or new installation (data wiped). The Stock app reads the database to get the UserAgent. I created a recovery flash-able file to make it easier.
Flash View attachment SoftbankSenseUserAgent.zip (Taken from ARHD 4.1.1) or View attachment SoftbankSenseJBUserAgent31.zip (Taken from ARHD 31-4.2.2) after a full data wipe or after fresh install (FLASH BEFORE FIRST BOOT) - (Updated 4 Sep 2012)
After flash, boot device for first time.
Don't forget to add your Softbank APN details.
DONE
You can do this on your phone before you do a factory reset or edit a ROM.zip before you flash it. The IMPORTANT thing is that it's a factory reset or completely fresh (data-wipe) install. Once booted and your APN is entered the stock app should work nicely.
USEFUL TIP: Once you get this working once. Use Titanium Backup App to backup "Customization Settings Provider". Restore this on any sense ROM after this and your messages will work. This is handy if flash often and don't have time to unzip each new ROM.
JELLY BEAN - Android 4.1.x
Stock / AOSP Android
View attachment 1265527 - From stock Android 4.1.1 with only the user-agent changed. (Updated 20 Aug 2012)
HTC Sense Instructions
Exactly the same instructions as the above Sense Ice Cream Sandwich instructions, except please use this file: View attachment 1458044
INSTRUCTIONS FOR INSTALLING THE APPS:
Try this first - just download and install the apk. If the install has no errors this is the easiest way. Your good to go.
If you get an error message - (Your phone MUST have root access from here)
1. Delete the Message app from your /system/app folder (Could be Mms.apk or something different with other providers)
2. Copy and paste the downloaded MMS.apk into the system/app folder and change permissions to match the other apps in that folder
OR
2. Restart your phone and install the downloaded app as usual.

OMG, I have tried so many times with adb and apktool but just couldn't get it done!
Thanks!
Sent from my Galaxy Nexus using Tapatalk 2

Yeah it took many tries, but it worked when I changed the URL in the res/xml/config as well as the useragent.
Sent from my HTC Desire using XDA

thanks for the help..
i was using Softbank mail client before but it wont work in ICS..
this works..

i have an issue. I am not able to download attachments. if the mail dont have attachments, i can get it.. but if it have some images attached, it says downloading failed.. anything i should do?

fake_japanese_guy said:
i have an issue. I am not able to download attachments. if the mail dont have attachments, i can get it.. but if it have some images attached, it says downloading failed.. anything i should do?
Click to expand...
Click to collapse
Do you have a silver or black sim card? Which APN are you using? I can only vouch for the silver sim card with the "open.softbank.ne.jp" APN. This downloads pictures.
I don't think the MMS app was designed to be able to download other types of attachments like gmail. I'll look into it though.
Edit: looked into it. Only pictures as far as I can tell.

Here's my Mms.apk for ICS - I modified one that has Emoji support (and changed the UserAgent and URL for Softbank compatibility). Have tested receiving and sending MMS and it works fine.
It is styled after Sense and so has avatars and speech bubbles:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Brilliant thanks! I was going to do this for my new One X that arrives tomorrow. I'll put it into the first post with credits to you. Just let me know if this isn't ok.

That's fine by me. I can't take the credit for actually making the app, I got it from here, and modified the config files to use the correct user agent strings. I hope people find it useful.

I have unlocked and rooted the HTC One X (International) by All-in-One Root Tool. Still with stock ROM/Kernel, SuperSU v0.90 and CWM recovery v5.8.4.0.
But would you mind providing an instruction how to install the MmsEmoji.apk?
First rename it into Mms.apk, then use ES file explorer to install the downloaded apk, it says "an existing package by the same name with a conflicting signature is already installed".
Then try to mount system/app into R/W with the mount/system app from Google Play. Still cant copy the mms.apk into system/app folder.
PS. Watching Thunder vs Heat in the same time is not very productive
Kremlin987 said:
That's fine by me. I can't take the credit for actually making the app, I got it from here, and modified the config files to use the correct user agent strings. I hope people find it useful.
Click to expand...
Click to collapse

Changes?
What changes did you make to the source code?
I'd like to keep building this myself when versions get changed.
I did change the User Agent to iPhoneOS, but you are talking about some URL as well. What file is this, and what do i change it to?
Thanks!

@BrianInfo,
Sure. Your phone does need to be rooted, so you can remount /system/app read/write. I always do it from the bootloader, where my desire's system partition security is off. Then you can just
adb push EmojiMms.apk /system/app/Mms.apk and reboot.
You can probably do it from Android if your system partition is not security protected (S-OFF), by going to a shell, remount /system rw, and then deleting Mms.apk and putting the modified one in its place. You will need to reboot after that, though.
@viddy,
I used apktool to unpack the source code. The file you need to edit is res/xml/mms_config.xml.
Change the userAgent entry to
Code:
<string name="userAgent">iPhoneOS/3.0 (7A341)</string>
and then change the uaProfUrl to
Code:
<string name="uaProfUrl">http://www.google.com/oha/rdf/ua-profile-kila.xml</string>
I also had a problem where I could receive but not send due to the maxMessageSize being set too high. It's currently set at 307200, which is working fine. maxImageHeight is 768 and maxImageWidth is 1024, but you could probably play around with those if you wanted to see what the maximum allowed image dimensions/message size is according to Softbank. I pinched those values from dombayo's Mms.apk, and they work fine.
Then just rebuild it using apktool, and sign using jarsigner, after doing a zipalign. You're good to go!

With this it let's you be able to see emojis from iPhones? Or just allows you to send
Sent from my MB855 using XDA

Jaemo, it does both. You can also use emoji in your messages.

BrianInfo said:
I have unlocked and rooted the HTC One X (International) by All-in-One Root Tool. Still with stock ROM/Kernel, SuperSU v0.90 and CWM recovery v5.8.4.0.
But would you mind providing an instruction how to install the MmsEmoji.apk?
First rename it into Mms.apk, then use ES file explorer to install the downloaded apk, it says "an existing package by the same name with a conflicting signature is already installed".
Then try to mount system/app into R/W with the mount/system app from Google Play. Still cant copy the mms.apk into system/app folder.
PS. Watching Thunder vs Heat in the same time is not very productive
Click to expand...
Click to collapse
Go to the HTC MMS app with you root explorer. Rename to MMS.bak or delete the file. Then do either of these 2 steps:
Copy and paste the new MMS.apk into the system/app folder and change permissions to match the others in that folder OR
Restart your phone. After this just click MMS.apk and it should install normally.

will this work for Sprint?

none of these are working for me?!

Jaemo, what specifically isn't working? Emoji? Sending mms? These apks are made specifically for Softbank's network, and while they may work on sprint, we can't test that. You're probably better off getting one of the emoji-enabled mms.apk files linked from one of my posts on the first page, which is not modified to work with Softbank. But we'll need more info if we are to help you effectively. What have you tried?

Kremlin987 said:
Jaemo, what specifically isn't working? Emoji? Sending mms? These apks are made specifically for Softbank's network, and while they may work on sprint, we can't test that. You're probably better off getting one of the emoji-enabled mms.apk files linked from one of my posts on the first page, which is not modified to work with Softbank. But we'll need more info if we are to help you effectively. What have you tried?
Click to expand...
Click to collapse
it seems as if iPhone users still can't see the emoji i've sent.. I'm using jokersax's ics rom cm9 and i was able to send emoji but iPhone users still can't see it they say it gives them the box symbol.

it seems as if iPhone users still can't see the emoji i've sent.. I'm using jokersax's ics rom cm9 and i was able to send emoji but iPhone users still can't see it they say it gives them the box symbol.
Click to expand...
Click to collapse
Are you in Japan? Are you using Softbank? If yes, please write down the steps you took.
This won't work on sprint in the USA. Its only for Japan.

[Q] Lenovo IdeaPad S5000-H 3G call option

Hi,
I'd like to ask you, if is there someone who knows, how to make Lenovo S5000 3G (with SIM slot) calling?
Could it be similar like on >Lenovo A 3000< ??? Bcs I really hope so.. :angel:
Thanks to all for your answers!!!!!
:fingers-crossed:

pls help me..........
i need call option for lenovo S5000

The Chinese version has call option. but it doesn't have Google Apps and you can't install one. the international version on the other hand has gapps but only supports SMS and data connection.

Is there any workaround to add in the Gapps to Chinese ROM or add in the calling function from China ROM to international ROM?
IMO i think the baseband is the key point in this case.

--

lenovo s5000
Please help us to use our tablets with 3G calls options!
Thank you xdadevlopers.

here the link for calling feature for lenovo s5000-h + root + gapps 4.2.2
1.S5000_A422_004_082_140402_CN_3G.zip
Sp Flashing tool including in S5000_A422_004_082_140402_CN_3G.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i suggest before rooting the new firmware downloa in install Developer option .apk came from cm rom 4.2.2 to enable usb debug option
2 Rooting latest 3g cn version
SRoot1.7.7_fix1.rar
3 Gapps For android 4.2.2
manualy place all files inside the system folder
Gapps for 4.2.2 make sure your done rooting your lenovo s5000-h to manually install and set permission ing .apk file
SS below

sorry how i can install gapps
plz help​

Hi
I cant download rom from china site
Can you upload rom to mirror site such as mediafire or another site ?
And one question that this rom that you sugest was rooted and gapps are in it or no ? Please help me too add gapps to my tablet
Sent from my iPhone using Tapatalk

I followed and tried the instructions and it WORKED! Now I have the call feature of my Lenovo S5000 but I have hard time with the root or SUperuser in the S5000 since it is chinese. I checked my root (thru Root Checker) and it is rooted. If somebody knows the name or can change the language of the "Superuser" in the Screenshot, I really appreciate.

jayayuyang said:
I followed and tried the instructions and it WORKED! Now I have the call feature of my Lenovo S5000 but I have hard time with the root or SUperuser in the S5000 since it is chinese. I checked my root (thru Root Checker) and it is rooted. If somebody knows the name or can change the language of the "Superuser" in the Screenshot, I really appreciate.
Click to expand...
Click to collapse
USB driver you need for your Lenovo S5000
www(dot)dropbox(dot)com/s/ker4lntmk2pyhvy/USB_Drivers.rar
Steps in Updating USB driver of your Lenovo in your Windows PC:
1. Turn off your S5000, making sure that the USB Debugging is swith on in Developer Options in Settings.
2. Open Device Manager (you can type Device Manager in Search in Start Menu of your PC)
3. Plug to USB of your PC
4. In Device Manager Window, watch carefully the "Lenovo" to appear, it only appears for few seconds and it disappears. Right Click it and Update driver, then locate the file that you previously downloaded according to your PC version.
---------- Post added at 10:25 AM ---------- Previous post was at 09:58 AM ----------
arisoldier said:
Hi
I cant download rom from china site
Can you upload rom to mirror site such as mediafire or another site ?
And one question that this rom that you sugest was rooted and gapps are in it or no ? Please help me too add gapps to my tablet
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
All the links provided are active and alive. There's no problem in downloading.
The ROM is not rooted hence you need to root using the SRoot. SRoot is in chinese so just open the exe file, plug your device and click "ROOT". Just wait for the "confirmation" before unplugging your device. You can verify by Root Checker. The "SuperUser" used in the root is in chinese language, see my previous post and screenshots.
I can help you in adding Gapps.
1.Download and extract the GApps rar file.
2. After extracting you can see these: 2 folders and one file
Folder 1: META-INF
Folder 2: System
File: install-optional.sh
3. In your device, browse files using any File Explorer supporting Root, Let say "Root Explorer". Mount the "System" folder to RW so that you can copy the files in Step#2.
4. In copying the Files in Step#2, the "Root Explorer" app is very easy in doing these.
4.1 Copy the "META-INF" folder and paste directly to the "System" folder in your device.
4.2 Copy the "install-optional.sh" file and paste directly to the "System" folder in your device.
4.3 Open the folder "System" 5 subfolders namely: add-on, app, etc, framework, lib
4.3.1 Copy the "add-on" folder directly to the "System" folder in your device.
4.3.2 Copy the all the files from "app" folder and paste directly to the existing "app" subfolder in the "System" folder in your device.
4.3.3 Copy the all the files from "etc" folder and paste directly to the existing "etc" subfolder in the "System" folder in your device.
4.3.4 Copy the all the files from "framework" folder and paste directly to the existing "framework" subfolder in the "System" folder in your device.
4.3.5 Copy the all the files from "lib" folder and paste directly to the existing "lib" subfolder in the "System" folder in your device.
5. Reboot your device. You have now GApps.

help me
please show me how to use sp flash tool and change the superuser in English because I do not speak Chinese. thank's for your attention:angel:

63 496452
christoperari said:
please show me how to use sp flash tool and change the superuser in English because I do not speak Chinese. thank's for your attention:angel:
Click to expand...
Click to collapse
That is my problem too so what I did, I just guessed up the buttons I clicked. I just presumed that the buttons on right ride are the "OK" buttons, while left are "Cancel". And I ended an S5000 that has calling features. :victory:

bug
is there a bug in this rom?
---------- Post added at 08:18 PM ---------- Previous post was at 08:14 PM ----------
jayayuyang said:
That is my problem too so what I did, I just guessed up the buttons I clicked. I just presumed that the buttons on right ride are the "OK" buttons, while left are "Cancel". And I ended an S5000 that has calling features. :victory:
Click to expand...
Click to collapse
is there a bug in this rom?

christoperari said:
is there a bug in this rom?
---------- Post added at 08:18 PM ---------- Previous post was at 08:14 PM ----------
is there a bug in this rom?
Click to expand...
Click to collapse
The ROM is almost perfect. The only bug I found (or maybe not) is the poor reception of GPS signal when I installed the Sygic Navi, but I found solution to that. My battery lasts longer and a very heavy usage of the Tab, 3G data is on as well, about 60% left after the end of each day. Regular call functions also very clear especially when I updated the dialer. I applied the Galaxy Launcher and I really love it more that my Samsung GS4. Radio was also included (I don't know if the SMS-only ROM includes radio)

can't root use sroot
jayayuyang said:
The ROM is almost perfect. The only bug I found (or maybe not) is the poor reception of GPS signal when I installed the Sygic Navi, but I found solution to that. My battery lasts longer and a very heavy usage of the Tab, 3G data is on as well, about 60% left after the end of each day. Regular call functions also very clear especially when I updated the dialer. I applied the Galaxy Launcher and I really love it more that my Samsung GS4. Radio was also included (I don't know if the SMS-only ROM includes radio)
Click to expand...
Click to collapse
I can't root my device. I've used sroot but can't root access. please,,can you help me to show how to use Sroot. with a screenshot or video. so that I can easily understand. thanks before.

christoperari said:
I can't root my device. I've used sroot but can't root access. please,,can you help me to show how to use Sroot. with a screenshot or video. so that I can easily understand. thanks before.
Click to expand...
Click to collapse
This is the screenshot of SRoot. All you have to do is click "ROOT"and leave our device until a popup will come.
After doing this, install to your S5000 the Root Checker app to verify your root. Good luck.

can't root access
jayayuyang said:
This is the screenshot of SRoot. All you have to do is click "ROOT"and leave our device until a popup will come.
After doing this, install to your S5000 the Root Checker app to verify your root. Good luck.
Click to expand...
Click to collapse
I've done what you tell me. but I did not find popup. please show me a screenshot of the popup. I attach a screenshot which I have done. but still can not root access.
The popup do you mean?? look at a screenshoot.

christoperari said:
I've done what you tell me. but I did not find popup. please show me a screenshot of the popup. I attach a screenshot which I have done. but still can not root access.
The popup do you mean?? look at a screenshoot.
Click to expand...
Click to collapse
Unfortunately I cannot provide you the screenshot of the actual popup, coz I cannot risk the root my S5000 but it is really "popup". Had you tried to verify your root status using "Root Checker"?

jayayuyang said:
Unfortunately I cannot provide you the screenshot of the actual popup, coz I cannot risk the root my S5000 but it is really "popup". Had you tried to verify your root status using "Root Checker"?
Click to expand...
Click to collapse
I have verify with rootchecker. but says "Sorry this device does not have root access" and the top of the root checker says "will not root this device. will verify proper installation root".. please help me to get root access. so that I could install GAPPS.:crying:

OTA update could not verified

hi
i m in 14?4.A.0.108 second edition on z1 compact and root and cwm and xposed instaled
j ever do my update with ota but at this time after update my phone says " could not verified" and the new firmware 14.4.A.0.157 is not installed
my bootlooder is locked and j didnt understant what is the propleme !!!!!
can you please help
thank you

You need to go back to stock before the OTA will install.. That means no xposed and any apps that you've uninstalled that came with the ROM need to be installed again..
A factory reset could do it, but if you do that then you will lose all your user data.. So make backups of everything you want to save before you do that.
If that doesn't work then you'll have to completely reflash the stock ROM, then try to download the OTA.. But that would be senseless as you'd be saving yourself time and downloads by just flashing the updated stock ROM

did you deodexed your rom? i have xposed, SU, recovery installed, but got no problem update to 157 via OTA...

I had the same problem, just install the new update via PC companion, you won't loose any data. One thing you'll loose is root
Sent from my D5503 using XDA Free mobile app

My room is bot deodexed i understant nothing ????

Nobody know what is thé probleme with this update could not verified message.?

Hey i have the same problem! I just dont have high speed internett to figure out what it is. Or download ftf.

I have the same problem, some one with one solution, of any one knows if it worth it?
Sent from my D5503 using XDA Free mobile app

PC Companion is the Solution?
I recently had drama of a similar nature - used PC companion successfully as a workaround.

If is here someone, who still has this problem, look into /cache/recovery/fota/ and open "report" file. If you are not able to open this - it ends with error, just copy it into internal storage or SD Card.
First of all, you need to find a lines which looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The important part is rb_file_open[4]. If this line ends with "could not stat file" or someting like this, you need to download this zip https://drive.google.com/file/d/0B-79RLdvfasJMV9ZM2dfVEZtRnM/view?usp=sharing and copy/paste the missing file into your system. Don't forget to change permissions RW+R+R
If this won't help, you probably also have installed 4k mod and your "report" file looks exactly the same like the what I post above.
So, if yes, than download this zip https://mega.co.nz/#!QZYkGZZR!BL9dkTpPzPcClEz8our776jpXpia827mYEd5lCM3OvI and replace all files in your system with the files in this zip. Again, don't forget to change permissions RW+R+R and reboot your phone.
Now you should be able to update your phone with/over OTA. Thanks pcpepik from xperia.cz

Thanks play3man.
just by going through your post i was directed in the right way for resolve this issue. Though i did not follow the exact steps that you mentioned, but, the "rb_file_open[4]" really helped. Here is what i did:
1. Using ES File Explorer i navigated to /cache/recovery/fota/ and opened "report" file
2. Went all the way down (actually somewhere almost 3/4th down) and located the line rb_file_open[4]
3. This line actually said it is trying to open the Build.Prop file and mentions the size of that file in the end of that line.
4. I suddenly remembered that i had edited my Build.Prop file a few weeks back for some testing (ro.ril.enable.dtm=1) Like i said i was doing some testing. Though this setting does not work with my Mobile Service Provider (Airtel) here in India for 2G Networks. But I had kept the setting as it is and never bothered reverting it.
5. So what i did was, edited my build.prop file again and reverted that setting by deleting this line which i had added a few days back.
6. Rebooted my phone
7. Downloaded the OTA again, and tried installing it.
8. And it was a great success . LOL It Worked!!!!
So basically, this error, "Could not verify", could also simply mean that the System files are missing/corrupt or as simple as modified by the user and hence the verification could not complete. So people who have their Build.Prop file modified by one means or other (Manually, Scripted, or by Xposed) You may face this issue and may want to try this method and then make all those settings in build.prop file after installing the update. You could also temporarily revert the old build.prop file which you may have backed up somewhere before modifying it.
Hope this helps!!!

adarpatel said:
Thanks play3man.
just by going through your post i was directed in the right way for resolve this issue. Though i did not follow the exact steps that you mentioned, but, the "rb_file_open[4]" really helped. Here is what i did:
1. Using ES File Explorer i navigated to /cache/recovery/fota/ and opened "report" file
2. Went all the way down (actually somewhere almost 3/4th down) and located the line rb_file_open[4]
3. This line actually said it is trying to open the Build.Prop file and mentions the size of that file in the end of that line.
4. I suddenly remembered that i had edited my Build.Prop file a few weeks back for some testing (ro.ril.enable.dtm=1) Like i said i was doing some testing. Though this setting does not work with my Mobile Service Provider (Airtel) here in India for 2G Networks. But I had kept the setting as it is and never bothered reverting it.
5. So what i did was, edited my build.prop file again and reverted that setting by deleting this line which i had added a few days back.
6. Rebooted my phone
7. Downloaded the OTA again, and tried installing it.
8. And it was a great success . LOL It Worked!!!!
So basically, this error, "Could not verify", could also simply mean that the System files are missing/corrupt or as simple as modified by the user and hence the verification could not complete. So people who have their Build.Prop file modified by one means or other (Manually, Scripted, or by Xposed) You may face this issue and may want to try this method and then make all those settings in build.prop file after installing the update. You could also temporarily revert the old build.prop file which you may have backed up somewhere before modifying it.
Hope this helps!!!
Click to expand...
Click to collapse
Yes, if you have done some more changes in your system, you may have different "error"

play3man said:
If is here someone, who still has this problem, look into /cache/recovery/fota/ and open "report" file. If you are not able to open this - it ends with error, just copy it into internal storage or SD Card.
First of all, you need to find a lines which looks like this:
The important part is rb_file_open[4]. If this line ends with "could not stat file" or someting like this, you need to download this zip https://drive.google.com/file/d/0B-79RLdvfasJMV9ZM2dfVEZtRnM/view?usp=sharing and copy/paste the missing file into your system. Don't forget to change permissions RW+R+R
If this won't help, you probably also have installed 4k mod and your "report" file looks exactly the same like the what I post above.
So, if yes, than download this zip https://mega.co.nz/#!QZYkGZZR!BL9dkTpPzPcClEz8our776jpXpia827mYEd5lCM3OvI and replace all files in your system with the files in this zip. Again, don't forget to change permissions RW+R+R and reboot your phone.
Now you should be able to update your phone with/over OTA. Thanks pcpepik from xperia.cz
Click to expand...
Click to collapse
Thank you for your help
I didnt find this .....rb_file_open[4] in the report file
I have just rb_file_open[0] and [1]
Im rooted locked bootloader deoxd cwm
I have 4k and timeshift video
Sorry for my bad english

BASHARAWAD said:
Thank you for your help
I didnt find this .....rb_file_open[4] in the report file
I have just rb_file_open[0] and [1]
Im rooted locked bootloader deoxd cwm
I have 4k and timeshift video
Sorry for my bad english
Click to expand...
Click to collapse
The second line ([1]) ends with could not state file? If yes, continue from that line with steps from my original post
You have deodexed rom, so the phone is probably missing way more original files, so that's why it ends already on second line

For me OTA updater complains about
rb_file_open[4]: //system/priv-app/psmselfupdater.odex
and apk, but the system dump you provided doesn't have it.

kentaurest said:
For me OTA updater complains about
rb_file_open[4]: //system/priv-app/psmselfupdater.odex
and apk, but the system dump you provided doesn't have it.
Click to expand...
Click to collapse
I have the same error on a stock Z1C, only rooted. I think if we could get the file from somewhere we could drop it on and the OTA would complete, and we'd probably keep root ?

Thank you for the /cache/recovery/fota/report trick. It seems my phone was missing /system/app/SonyEntrance.odex and .apk - I am not sure how this happened or what those files are for.
Edit: Seems it's because I removed 'What's New' :cyclops: