yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] ilangoadigal:
This was not written by me. It was written by Ayman al-Sanad, username UAE (I believe), who has been working for some time to create workable libraries for so Android devices can properly display Arabic. Oddly there was no thread posted here that I can find so I'm going to go ahead and post it, since I know this is a much-desired feature for many people and at least some people will find it over Google or the like.

As Google has yet to add native support for Right-To-Left languages like Arabic, Persian and Urdu (despite it being the top feature request) Ayman stepped in and created libraries for our usage.

The downloads page is available here: http://ardoid.com/?page_id=5. I'm assuming the libraries will work with any Froyo install. Put the library zip on your SD card, flash it. Reboot will take some time on a black screen.

Big thanks to Ayman for his great work. Evo libraries are also available on his page.
[Droid Incredible Android Development] iakamand:
this is the best news yet!!! i will try right now and report back
[Droid Incredible Android Development] iakamand:
Works Perfect !!!!! i can't believe it's finally happening. thank you very much for posting
[Droid Incredible Android Development] amjz:
Dose this works with WebOS (Palm Pre) ?
[Droid Incredible Android Development] todd3835:
Really? Your in a forum for an ANDROID device, and if that wasn't enough of a hint, the OP says "ANDROID" in the first line.
[Droid Incredible Android Development] Weazol:
works perfectly, Thanks for the heads up
[Droid Incredible Android Development] shamidude:
Problem with ROM updates

The ZIP files on the ardoid.com site worked perfectly with my phone. This was when Verizon rolled out the Froyo update, and i was able to use the same ZIP files for both a stock ROM as well as a custom one.

But couple weeks ago, Verizon rolled out a minor update to Froyo (2.2.1 I think), and it was also picked up by some developers of custom ROMs. Once I applied any of these updates, I am unable to use the Arabic ZIP file anymore.

Here is what I usually do:

- Use the ROM Manager to download the new ROM.

- Reboot to recovery mode and apply the ROM (done automatically by the ROM Manager).

- Verify the ROM is working correctly.

- Download the Ariabic ZIP file from ardoid.con.

- Reboot to Custom Recovery, and manually apply the Arabic update.

- Reboot the phone one last time.

- The phone remains stuck in the HTC Incredible splash screen.

The only way out is to remove the battery, boot into recovery mode, and do a restore.

I tried this approach with the Virtuous ROM 3.1 and the CyanogenMod 6.1. In both cases, I was trying "froyo_incredible_libs_arabic_android_plus_signed.zip".

I also tried the following ZIP files, and they both failed (didn't expect them to work anyway):

- froyo_stock_generic_signed.zip

- froyo_cm_n1_6_1_1_stable_arabic_android_plus_signed.zip

The questions that I have are:

- Is there a dependency for the ZIP file on the actual system image? Does this mean that there has to be a new ZIP file for the 2.2.1 release?

- Is there another preferred way for applying the ZIP file? (I am using ClockworkMod Recover 2.5.0.5).
[Droid Incredible Android Development] shamidude:
Quick update

I would like to add one little detail: using CyanogenMod 6.1, most apps have decent Arabic support by default (for example, tweetdeck or facebook). Unfortunately, the browser doesn't know how to join the Arabic letters correctly (doesn't matter if I am using the stock browser, or Dolphin).
[Droid Incredible Android Development] shamidude:
I tried pushing the libwebcore.so and libskia.so files from the Desire HD ZIP from http://ardoid.com/?p=176

I copied the files to the SD card, then copied them over the original files using ADB. After the reboot, the phone got stuck in an endless loop, and here is what I saw repeated when doing "adb logcat":

W/dalvikvm( 1311): ERROR: Unable to find decl for native Landroid/webkit/BrowserFrame;.clearNativeCache ()V

E/JNIHelp ( 1311): RegisterNatives failed for 'android/webkit/BrowserFrame'

E/webcoreglue( 1311): WebFrame registration failed!

W/dalvikvm( 1311): JNI_OnLoad returned bad version (-1) in /system/lib/libwebcore.so 0x0

W/dalvikvm( 1311): Exception Ljava/lang/UnsatisfiedLinkError; thrown during Landroid/webkit/WebViewCore;.<clinit>

E/Zygote ( 1311): Error preloading android.webkit.WebViewCore.

E/Zygote ( 1311): java.lang.ExceptionInInitializerError

E/Zygote ( 1311): at java.lang.Class.classForName(Native Method)

E/Zygote ( 1311): at java.lang.Class.forName(Class.java:235)

E/Zygote ( 1311): at java.lang.Class.forName(Class.java:182)

E/Zygote ( 1311): at com.android.internal.os.ZygoteInit.preloadClasses(ZygoteInit.java:302)

E/Zygote ( 1311): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:589)

E/Zygote ( 1311): at dalvik.system.NativeStart.main(Native Method)

E/Zygote ( 1311): Caused by: java.lang.UnsatisfiedLinkError: Library webcore not found

E/Zygote ( 1311): at java.lang.Runtime.loadLibrary(Runtime.java:461)

E/Zygote ( 1311): at java.lang.System.loadLibrary(System.java:557)

E/Zygote ( 1311): at android.webkit.WebViewCore.<clinit>(WebViewCore.java:61)

E/Zygote ( 1311): ... 6 more

E/Zygote ( 1311): setreuid() failed. errno: 17

D/AndroidRuntime( 1311): Shutting down VM

W/dalvikvm( 1311): threadid=1: thread exiting with uncaught exception (group=0x4001d7f0)

D/skia ( 1311): purging 6K from font cache [1 entries]

I/ServiceManager( 105): service 'media.audio_flinger' died

I/ServiceManager( 105): service 'media.player' died

I/ServiceManager( 105): service 'media.camera' died

I/ServiceManager( 105): service 'media.audio_policy' died

I/ ( 1312): ServiceManager: 0xaec8

I think the root cause is "JNI_OnLoad returned bad version (-1) in /system/lib/libwebcore.so 0x0", but I am not sure what this means, or how to fix it.
[Droid Incredible Android Development] shamidude:
It finally worked!

I downloaded the ZIP file for the Cyanogn Nexus 6.1.1 from http://ardoid.com/?p=21 (I was starting from a CyanogenMod 6.1 for HTC Droid Incredible).

I repeated the same steps as before, but with the following exceptions:

- I copied the "libwebcore.so" file alone (didn't update the libskia.so).

- I rebooted the phone as usual rather than via ADB.

I am not sure which step made the difference, but at least my phone can boot, and most importantly, I can now see proper Arabic text in the browser. Other apps looks fine as well (tweetdeck, reader, etc.). I was even able to enter Arabic text using the browser (in Google search) and everything looked perfect.

I don't know what I might be missing by not updating ibskia.so, but things look really nice already.

Thanks Ayman for helping me out (via Twitter)!!!
[Fascinate Android Development] tats_06:
This is going to be simply a collection of links with important points...Please read ALL directions and comments carefully...as no one is responsible for any damage to your phone.

NOTE 1: IF YOU ARE UNROOTED AND ALREADY UPDATED WITH OTA, YOU CAN STILL USE THE PROCESSES BELOW TO ROOT AND FLASH RECOVERY.

>> Rooting Samsung Fascinate

>> Flashing Clockwork Recovery

NOTE 2: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.

If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock

If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image

NOTE 3: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.

If you want to stop the OTA update notification, use this file which provides simple edits...but be careful as it may make further updates more difficult >> SCH-I500.DI01 Update

UPDATED:

OTA Update with Root and Busybox >> DH12 to DI01 update with root and busybox

Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
[Fascinate Android Development] jatilq:
My path.

1) Stock with root mentioned in this dev section

2)restored CW backup

3)used CW to install the update mentioned in this thread.

No problems so far.

After reading this thread again I went to stock and stock kernel. Rooted and gold again.

I think that CPU Scale app causes the Fascinate to shut down, so if you use it and getting them.... remove the app or let me know if you fixed.
[Fascinate Android Development] tats_06:
Thanks!!!

Now, here is something I didn't try yet. I am still stock (not rooted), ran the OTA...and with all people having issues, I am scared to root. I want to try but I think I will wait and see if anyone else does this. :)
[Fascinate Android Development] taypotts:
I thought the post about doing the OTA manually would allow you to keep root, seeing that it's a stripped down version.
[Fascinate Android Development] tats_06:
Let me clarify that. If that's the case, I can update the OP. :)
[Fascinate Android Development] pospower:
Restored, updated and Rerooted

All is well. No problems so far.
[Fascinate Android Development] namebrandon:
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.

If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.

Read before using, that's all I ask.
[Fascinate Android Development] tats_06:
Thanks for heads up...first post updated. :)
[Fascinate Android Development] wasupwithuman:
Bump.... Back to top till this gets stickied!
[Fascinate Android Development] tats_06:
Thanks! I just reported it too to request for sticky. ;)
[Fascinate Android Development] azalvarez03:
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
[Fascinate Android Development] tats_06:
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks. :)
[Fascinate Android Development] wasupwithuman:
I don't think the update blocks root. you should be able to install the OTA as long as your not rooted, then once it is installed go ahead and root your device.
[Fascinate Android Development] tats_06:
Ok...looks like root went thru...working on cwm recovery now. :p
[Fascinate Android Development] tats_06:
OK, recovery installed successfully...running a backup right now. :)

Should I test restoring? Or should I assume I am safe? :D
[Fascinate Android Development] lukaro:
Rooting after OTA update.

Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
[Fascinate Android Development] namebrandon:
If you have CWM installed, you always have root via adb, which means you can get your root apps working.

If you're not running CWM, I don't know. Someone who's tried rage.bin post-update could tell you.
[Fascinate Android Development] OneAn9ryN00b:
Yes you can root after update, I did it fine, but had to attempt it twice, the first try it hung, so had to do a battery pull, and then the second time it worked fine.
[Fascinate Android Development] chronster:
Nothing in the update seems worth it to return to stock (I've removed so many stock apps already.)
[Fascinate Android Development] crazyfool287:
I'm having the Force Close loop issue. My CWR seems to be missing, as all I can access is Android system recovery <2e> with the options of:

reboot system now

apply sdcard:update.zip

wipe data/factory reset

wipe cache partition

Using the Odin method didn't work for me, on multiple tries. My SD card appears to be wiped clean and I can't enter debug mode.

Is there anything short of a miracle that I can do to fix my phone? I've seen a few posts with people saying they had similar problems as mine, but there was never and explanation of how or if they fixed there phone.

Thanks in advance
[Fascinate Android Development] bendbowden:
Just got my fascinate today and the rooting, flashing recovery, update process was seamless thanks to this guide. Thanks to all the devs who made this happen! Come on custom ROMS. Missing Froyo which I had on the Eris. Not missing the Eris, however :)
[Fascinate Android Development] jorge3687:
How is ir working for you, I have my root and lag fix, but I am a little afraid to put the recovery
[Fascinate Android Development] dlongb13:
I have CWM, lag fix, and the rooted and busybox version of the update.zip installed and I am rockin in the free world with no errors or scares (so far). This phone makes my Moto Droid look like a Moto Razor, and it was far from stock.

EDIT: I highly recommend doing the CWM if you are going to tinker with the phone and deviate from the stock format, as you are going to want/NEED backups at some point in time, I can almost guarantee it.
[Fascinate Android Development] jorge3687:
So I should undo the lag fix and unroot before starting the process?
[Fascinate Android Development] destroyerbmx:
common feelings on the lagfix that I am finding is remove it anyway.
[Fascinate Android Development] destroyerbmx:
what did you change right before you got the force close loop?
[Fascinate Android Development] crazyfool287:
I was rooted and used Titanium backup to remove some bloatware. I then used Odin to go back to stock, as I didn't want to not be able to update due to the apps I had removed. Everything was fine until I did a factory reset. After that everything went waaay downhill.

I had flashed CWR, but when I went to reboot into recovery, there was no nandroid or anything. When I went back into android to reflash, force close loop city.

I made the mistake of wiping my micro SD card, thinking there was an issue there. I think that's where I really screwed myself.

The only thing I can think of to do at this point is see of there's a way to flash recovery to my phone without the OS (which I doubt) or wait until there's a signed update.zip.

Any insight after a little more detail?

Thanks
[Fascinate Android Development] vzw:
I am right there with you if you figure it out please let me know... All I know is if you go into the settings under application management and force close everything then your popups will slow down for a while.
[Fascinate Android Development] namebrandon:
What happens when you go to stock recovery and choose apply update.zip? That should be how you enter clockworkmod recovery from a cold start. If you've had other phones with CWM before, you may not be used to that step.
[Fascinate Android Development] crazyfool287:
I haven't been able to find that file, as mine is missing. If anyone could post theirs, that would be awesome.

Scratch that. Since it's not signed, I don't think that will work.
[Fascinate Android Development] namebrandon:
What? This isn't making sense. CWM puts the update.zip file there for you to use. If you've flashed with CWM initially, it replaces the stock recovery binary with the CWM recovery binary. Just apply update.zip to get into CWM recovery.

If you haven't flashed CWM recovery, then you haven't installed it correctly.
[Fascinate Android Development] crazyfool287:
It says that file is not found on SD card
[Fascinate Android Development] namebrandon:
Oh, I see you somehow wiped your sd card.. interesting.

Anyway, here's the (CWM) file.
[Fascinate Android Development] crazyfool287:
You are the man! I had to use Odin and use the RWM .tar, but it worked like a charm. Hopefully the next step of flashing the stock nandroid file works.

I'll keep everyone posted, as I know there are others with similar problems.

Thanks!
[Fascinate Android Development] crazyfool287:
Everything is working - except my phone is stuck in airplane mode.

I went to about phone and it reads:

Hardware version - unknown

Model number - SCH-I500

Firmware version - 2.1-update1

Baseband version - Unknown

Kernal version - 2.6.29

Biuld number - SCH-I500.DH12
[Fascinate Android Development] wasupwithuman:
you flashed using "phone" instead of "pda" in odin.... you borked your radio/baseband... only fix right now is to take it to vzw. a few people have done it... a lot of dead phones....
[Fascinate Android Development] wasupwithuman:
Did you flash using the "PDA" option in odin or the "Phone"?
[Fascinate Android Development] crazyfool287:
I think I may have flashed the kernal .tar to phone
[Fascinate Android Development] namebrandon:
Yes, you did. If you see an unknown version on baseband, you overwrote modem.bin.

Time to do an exchange at the Verizon store. Sorry man. If you flash to "phone", there's no saving it, at least not currently.

Good news is you can blame it on the "update" that just went out. ;)
[Fascinate Android Development] wasupwithuman:
Thats exactly what i was thinking.... Go into the stor and say i installed the OTA and now my phone wont come out of airplane mode... Then drool.... :)
[Fascinate Android Development] ChadZ:
I have the Samsung Fascinate with default 2.1 android.

I rooted my phone using the one click method just fine. However, some problems:

The one click lag fix did not work for me on the version2 method, only version 1. I tried numerous times after rooting and rebooting the v2 method gave me this error:

Contact: Anonymous
Firmware: Unknown
Version: 2.0.4
Fri Sep 24 12:27:08 America/Detroit 2010: Enabling Flight Mode and killing all running apps.
Fri Sep 24 12:27:19 America/Detroit 2010: Initializing boot support
Fri Sep 24 12:27:20 America/Detroit 2010: Calculating sizes...
Fri Sep 24 12:27:20 America/Detroit 2010: Mounting RFS /data onto /dbdata/rfsdata
Fri Sep 24 12:27:20 America/Detroit 2010: Creating 724MB file to store data inside. This could take a long time...
Fri Sep 24 12:27:20 America/Detroit 2010: Running command: dd if=/dev/zero of=/dbdata/rfsdata/ext2/linux.ex2 bs=1M count=0 seek=724
Fri Sep 24 12:27:20 America/Detroit 2010: Hit an error, undoing lagfix!
Fri Sep 24 12:27:21 America/Detroit 2010: OneClickLagFix V2+ failed with error: Could not create /dbdata/rfsdata/ext2/linux.ex2 - dd: /dbdata/rfsdata/ext2/linux.ex2: No space left on device

I did the check space option, is was 1,300MB and I only set the option on v2 to about 700MB.

Also, I installed SetCPU, for some weird reason the "max" is only 1000MHz. Where is the overclock on this? The hardware cpu is already 1GHz anyway. Yes, superuser granted permission and all.

On my eris the setcpu had option way beyond its 512Mhz hardware.
[Fascinate Android Development] daavy:
we wont be able to overclock until we get some custom kernels.. so 1000mhz is stock...
[Fascinate Android Development] jorge3687:
I have Clockworkmod recovery!!

OMG, I Just finished flashing clockworkmod recovery, without a glitch, I did my first backup, but there is no rom to install yet, I cannot wait, I miss froyo!!
[Fascinate Android Development] sic4672:
I agree. I still can't wrap my head around having amazing new hardware and antiquated software at the same time! stepping back from 2.2 and cm6 was tough, but with koush working on a port for the fascinate, it will eventually work out well.
[Fascinate Android Development] CrimsonKnight13:
This happened the exact same way for me after I updated to DI01... I guess we'll have to wait for a fix or custom firmware.
[Fascinate Android Development] DevinLeFevere:
Why is V2 any better?
[Fascinate Android Development] stayqued:
So I wanted to go back to bone stock, unrooted to exchange the phone.

Did factory reset- successful

then entered ADB to remove su, busybox, and superuser.apk.

removed su and busybox, but not superuser, and exited, not realizing I could not later delete Superuser.apk without root.

Root disabled on phone, but SU icon still present.

Attempted re-root with Dirrks One click V2 4 times in order to remove SU.apk, and get the same hang up and freeze each time.

Gets to the point where it says "unlock phone and wait"

Unlock phone

"Wait 3 minutes...etc."

And then the phone freezes at the lock screen at this point, and I have to pull the battery.

It does go beyond this point at the cmd prompt, however, all the way to the end, where it sayus "attempting to install perm. files..." but then gives me

device not found (five times)

and brings me to the "hit any button screen"

Please advise.
[Fascinate Android Development] koolnerd1:
So I wake up today to find out my phone auto updated and I lost my root.. what are the steps to re-root? also is there a way to stop the auto update

update: so i just ran the 1 click root method again and it worked fine error free
[Fascinate Android Development] tats_06:
You can just run the root process again and you will be good. ;)
[Fascinate Android Development] Crashspeeder:
You run the manual root method. You can start at the step after running rage.bin. I had the same thing happen to me.
[Fascinate Android Development] koolnerd1:
Thanks that's exactly what I did and it worked fine
[Fascinate Android Development] djsans23:
Rooting Issue

I have downloaded the 32-bit .exe file to root my fascinate, but its taking forever to install on my computer? Does it take a while to install or are the files potentially corrupt or is anyone else experiencing these problems?
[Fascinate Android Development] pattont:
What is the .apk name of the MobileIM. I can't seem to find it in the /System/App folder on my wife's phone. I swear I saw it on the first day I rooted, but I haven't seen it since, but it is constantly running.
[Fascinate Android Development] Daswolven:
Final_shci500 something I believe.
[Fascinate Android Development] Dnotez12:
I'm having so much trouble after installing the super clean rom I can not successfully get back to stock I tried everything I have been reading through every forum related can someone please step through this with me. I'm coming from a HTC phone and its a lot different! :confused:
[Fascinate Android Development] vashht:
Just use Odin and flash to the stock rom. Its pretty easy to do, just make sure you plug everything in in the right order.
[Fascinate Android Development] davewolfs:
If I've rooted my phone and have not yet accepted the update but would like to. What are the safest steps to follow in order to apply the update and regain root access?
[Fascinate Android Development] Gitykins:
You could just flash the clean + rooted DI01 on the first page.
[Fascinate Android Development] AtropineNa:
Hey guys, I'm in an ordeal. My goal is to restore root in my friend's phone.

My friend had Ryan's Lagfix installed and updated to DI01. Now, he doesn't have root access. He also did not install ClockworkMod so theres no nandroid backup.

I tried running the unlagme.bat (but you denied because you need root access).

Tried running the one click root (didn't work).

What can I do for him?

-Run Odin and flash CWM? (Don't you need root for that?) (What would I flash even after obtaining CWM with no nandroid?)

-Factory reset (that won't remove the lagfix though, right?)

Thanks for any responses.
[Fascinate Android Development] shauder:
Should be able to flash Clockwork using odin

then I would take Jt's super clean rom with root and flash it using clockwork

then run the bat then go back to stock if you can
[Fascinate Android Development] Daswolven:
+1 on this. This process worked with my first RyZa lag fix fail.
[Fascinate Android Development] Jeff5886:
i did this and am curious if we have a found a fix for it. i cant get to a verizon store for days. i will even paypay someone $$ for a fix.