Database Users

Arabic support on nand based roms!

Guys I've tested many arabic enabling files nonetheless it resulted not booting andriod or after booting most of the apps force closed do you guys have any trick for it?

same here....grscipt did not work....libskia replacement halted nand on reboot & even hard reset was not actually done so I had to installed stock rom & redo nand process

I did not try any NAND version yet, but you might want to try Arabic fonts and libs from this site http://ardoid.com/ give it a try if you did not.
It has different versions, so be certain that the libs are for Desire HD or Nexus,...etc

How use files ?
there are to folder META-INF and system
i replace files in folder system with root explorer but faild and roms does not boot again after reboot

Please keep this ALIVE any one found a SOLUTION please SHARE

-deleted useless post-

Solution
Any ideas guys ?

well you can already install a NAND arabic enabled rom like this one http://forum.xda-developers.com/showthread.php?t=782301 (get a keyboard from the market)
also the recovery image for HD2 was just released http://forum.xda-developers.com/showthread.php?t=898913 . this will probably make it easy to easy to use the arabiser for Desire or DHD from
http://ardoid.com/
will give it a try later

keep an eye on this thread http://forum.xda-developers.com/showthread.php?t=899203

thanx for post

Kernals, Nand, full functioning Android?

I gave my Dad my old blackstone when my Desore turned up.
He has winged that he can't get the marketplace and about all those general WinMo issues that people have (it dead etc)
I can't find a clear message on the status of NANDROID for blackstone.
TIAD8s site has NAND versions that are missing bluetooth or other funcitons
It appears there are basic functions that are lost according which kernal is being run.
I'm willing to do one completely convoluted install just to get Froyo style on my dads phone but only once. I never have trouble with new flashing procedures (slow and steady wins the race) but I don't want to hand him back the phone broken especially as he uses hands free in the car
So - can anyone say categorically that a NAND version work fully?

Categorically: Not yet. Wondering if ever...

Forget it...

Think Tiad8 only has test team working on a NAND build anyway?
Not seen it in action yet

Kernals?! ....

I find deliberate typos (NOT TEXT SPEAK) can get people to engage.

olly230 said:
I find deliberate typos (NOT TEXT SPEAK) can get people to engage.
Click to expand...
Click to collapse
Is that also why you called it a "Desore" instead of Desire?
lol, you made a typo or you just didn't know. No need to try and rationalize it .

t8 let people wait and wait.
though it's good to try, we don't know whether he really works on it as he start many threads to other device besieds HD.

arrrghhh said:
Is that also why you called it a "Desore" instead of Desire?
lol, you made a typo or you just didn't know. No need to try and rationalize it .
Click to expand...
Click to collapse
Desore was a proper typo, I'll put my hands up to that

Tiad8's just kidding us, it will send to test team files from NVIDIA Tegra device. Only RUU_signed is working, but I think it's my modded LK Bootloader from Rhodium (with modified mtype). Something's wrong with this nand.
I have runned this but touchscreen not working properly and I don't have GSM.

MietasSR said:
Tiad8's just kidding us, it will send to test team files from NVIDIA Tegra device. Only RUU_signed is working, but I think it's my modded LK Bootloader from Rhodium (with modified mtype). Something's wrong with this nand.
I have runned this but touchscreen not working properly and I don't have GSM.
Click to expand...
Click to collapse
I thought you were part of his developer team because he now give credits to you for your ruu and recovery.img (at last he ist starting to do this: giving credits) in the NAND download post.
With your post here I had to smile a little: now your name is connected to the "null nands" for many consumers in tiad8's forum. Even I thought you're part of it now and that's why I tried the build yesterday again: Boot partition to small and Kernel not working.
I think now it's getting to the critical point in the NAND experiments: correct or good partition sizes for NAND (some members there startet to change partition values in the image files with a hex editor) and more important: building a working kernel with modules for Blackstone NAND.
Until now all experiments reached a few preparing goals: getting a working .nbh for starting into fastboot, getting a recovery.img for a working CWM etc.
But now (if I am completely wrong please correct me, I really want to know) you have to change partition and ram parameters in clk and hope you will spare the protected parts.
And after that: Kernel and Modules for Blackstone on Nand. I am starting to believe here would be the real point for developers.
I started to build Kernel and Modules, a Boot Environment (initrdgz) from git and packed them with changed parameters in a Tinboot-Package. I can flash with the .nbh, I can boot, I got a lot of errors in init first, but I succeeded in running and loading the kernel, I get access to the changed mtd partitions etc. Debugging on Blackstone with Echo "" ist quite funny.
I got stuck when I tried to cp files from SD card to the /system partition (which is mounted r/w) - I can cp files from / to /system anyway. Big ?? for me. But I like to play with it a little more, because I learned a lot.

ThaiDai said:
I thought you were part of his developer team because he now give credits to you for your ruu and recovery.img (at last he ist starting to do this: giving credits) in the NAND download post..
Click to expand...
Click to collapse
Me Too!! Does this mean you are working on different things?

LolBoot xD SGS2 dualboot - NEW 12.12.11: Easy-Setup App v2.51

(I wasn't really sure if this might fit into "Development", so I put it here, maybe a mod will move it, if it's a dev topic )
Anyways, here we go, I DUALBOOTED two different, independant ROMs on the S2
Video of dualboot in action: http://www.youtube.com/watch?v=l9-V_6Ua_D0
** THIS IS NOT (YET) COMPATIBLE **
** WITH ICS (ANDROID 4.0.x) ROMS! **
-- this goes for custom ROMs as well as stock ROMs --
Icey Sammich compatibility will be added once Sammy released their ICS kernel sources.​
!!! There now is an app for more convinient and easy setup of the dualboot !!!
(04.11.2011) DualBoot setup app v2.00: http://forum.xda-developers.com/showpost.php?p=19049047&postcount=94
(12.12.2011) App has been updated to 2.51, lot's of good new stuff! >> Free Version -- Donate Version <<
Click to expand...
Click to collapse
First off:
This is only a little experiment I did like "c'mon, has to be possible" - this is NOT (at least yet) tweaked for usability and anything the like, just a humble experiment.
That said, don't flame me if things are rather complexicated to do this ATM.
Maybe I'll come up with a more userfriendly way of setting this up, maybe someone else does, maybe no one does.
Also now that I found a base on what to do, there might be different ways (more easy ones maybe) to set this up, I'll keep toying around with it.
But let's cut to the chase, shall we
So, how was this set up? I'll give a brief rundown of what I did:
I edited a few .rc files in the initramfs of the kernel to make it actually perform a full boot when recovery mode was triggered and to fire up recovery mode when in battery-charging mode.
I also edited a few mounts in the boot .rc for the 2nd OS (in "recovery" mode) to use different partitions for /system and /data, so that we'd end up with really independant installs.
What partitions did I missuse for that:
partition 12 (mostly unused, only when installing a stock ROM AFAIK) for /system - that's a neat choice IMO as p12 is 512MB in size, just as p9 where /system usually sits on
partition 7 (which is usually /cache) for /data
gives us only 100MB of user data space, but for now that's OK, as said, it's only an experiment on how such a thing could be done.
with the original partition for /cache "gone", I mounted a tmpfs for it.
So the OS still has a usable /cache
Then I set up the two OSes:
(dualboot kernel not yet flashed)
Launchprep part 1:
I made a CWM backup of my normal installation I was running (stock XXKG6 at the time).
I installed DevNull-Test AOSP as to it's instructions
Some su'ed voodoo via a terminal while having the 2nd OS (the DevNull AOSP one, in this case) installed - best done in recovery mode via ADB:
rm -Rf /cache/*
cp -Rp /data/* /cache/
dd if=/dev/block/mmcblk0p9 of=/dev/block/mmcblk0p12 bs=4096
That did "set up" the 2nd OS to where it's supposed to go.
Launchprep part 2:
Then, "advanced restore" of the backup made a few minutes earlier:
- boot
- system
- data
Reboot
At this point OS #1 is running again and OS #2 is sitting in hiding, prepared to roll - so, let's roll:
Flashed the modified "dualboot kernel" (via an App or Odin or magic, doesn't matter).
---> DONE <---
reached the point to where everything works as shown in the video.
As said above already, yes it needs some manual work to set it up, yes there's a lot of things that might not work, yes there are other/better ways to set it up.
It's only a humble experiment - lot's of space for improvement.
Maybe you like it - for those who do, I wanted to share this
Attached to this post you find the modified kernel I used, it's based on my v1.20 custom kernel (see sig) but with the above mentioned changes.

I've seen the video m8, this is totally different approach, ur giving this device a new dimension. love u "in a straight way" hahaa

there currently an app called Bootmanager which also handle up to quadruple booting. But sadly currently only support HTC phones.
http://www.appbrain.com/app/bootmanager/com.drx2.bootmanager
well, one can hope!

Thanks OP this is an awesome concept! Very happy to see you posted it with a video! and nice boot animation!

sunwee said:
there currently an app called Bootmanager which also handle up to quadruple booting. But sadly currently only support HTC phones.
Click to expand...
Click to collapse
Yeah, that's the thing.... that app is HTC only.... but we have Samsung S-II and want dualboot as well.
I'm already brainstorming on how to enhance the actual usability of this, i.e. flashing a 2nd OS directely to it's place instead of first installing it to the main system partition. But there is problems when /data is not mounted to the original partition, at least stock doesn't like it on initial boot.... well, well....

That is great. Going to use this for sure. This should be in development for sure.
Congratulations already.
Sent from my GT-I9100 using Tapatalk

This is impressive bro sure will use it
but i want to ask one thing
SD card needed for this or not ?

That would be really cool (and definitely should goes to original development). Does it work with CM7/MIUI + custom rom?

vikas776 said:
SD card needed for this or not ?
Click to expand...
Click to collapse
No, so far this completely works with all internal storage.
But I have a few ideas I have yet to try to get mounted from other places - like images in /sdcard for example (I *so* hope that'll work.... )

Hi
Does this kernel include any of the Hellcat kernel tweaks or are they work in progress.
Sent from my GT-I9100 using Tapatalk

Tricky103 said:
Does this kernel include any of the Hellcat kernel tweaks or are they work in progress.
Click to expand...
Click to collapse
I made this build based on my v1.20 custom kernel, so it has everthing that one has - plus the touchfix already

exactly what i was hoping for.
great job - pls continue your work

Hi i tried this with instanity rom last night. When I use the three buttons to boot it just sits there not booting. My guess is the kernel is not compatible. Unless I made a mistake somewhere.
Sent from my GT-I9100 using Tapatalk

Hm, yah, might be that the kernel isn't fully compatible with that ROM, what kernel does the ROM usually use?
Did you boot it up fully at least once before copying /data to /cache ?

Yes I did fully boot up. But his kernel didn't have advanced activated in recovery so I flashed your kernel and moved the cache okay. But it said /data not found when I ran the 2nd command line.
I will flash aosp later. I like that rom.
I am not sure what kernel nitr8 uses. I think it is his own, Insane.tar would you like it to see if they can work together.
Sent from my GT-I9100 using Tapatalk

Tricky103 said:
But it said /data not found when I ran the 2nd command line.
Click to expand...
Click to collapse
Hm, yeah, that sounds like something didn't work.... make sure you run those commands as root, i.e. "su" as very first command (I'll add that to the first post).
Give me a direct link to the ROM and I'll try it.
Make take a few days though as I'm away from my computer a lot because of work the next two days, but I'll try once time permits.
Well yeah, and this still is in highly experimental stage, if I (or someone else) should ever get this to more stable and reliable state, I'll make an easy to use installer/setup tool
But I got a few other ideas on setting it up I have to try first....

http://goo.gl/2uZCh
This is the complete rom. Only 47mb. I thought you would like the whole rom

Tricky103 said:
Hi
Does this kernel include any of the Hellcat kernel tweaks or are they work in progress.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
May be someday WINDOWS Mo 7 and Android on our sweet beast

Hi
I tried again with Aosp Dev-null. I still get this error "cp: can't stat '/data/*': No such file or directory "
after running this command line " cp -Rp /data/* /cache/ "
Any Ideas ?
It still doesn't boot if I press 3 button it brings up the boot logo and then black screens until it boots to the 1st partition.

Thanks for the link, will download and try as soon as time permits.
Also, try this command sequence, I got an idea what the issue maybe might be, give it a shot:
Code:
su
rm -Rf /cache/*
busybox cp -Rp /data/* /cache/
dd if=/dev/block/mmcblk0p9 of=/dev/block/mmcblk0p12 bs=4096
(use "busybox cp" instead of plain "cp", maybe it helps)
And some update on my ongoing thoughts for those interested:
- got an idea on how to make a more easy to use App for prepping and setting up the dualboot environment
- managed to do a neat thing I didn't really think it would work: issued a "mount" command and the OS thought it was mounting a partition of the internal flash (/dev/block/mmcblk0p12 in this test, but was testing for later on actually doing it with p9 - you might see where I'm headed here ) but instead of the partition it actually mounted from an .img file! (loopback)
i.e. "mount /dev/block/mmcblk0p12 /somedir" actually mounted "/somepath/someimage.img" to "/somedir" instead of the partition from /dev/block/... (you just gotta love Linux and it's flexible way of handling things....)
NOW, imagine /dev/block/mmcblk0p9 (the partition carrying the system) and p10 (data) being (kinda) transparently mounted from an IMAGE FILE
I "only" have to find a way to sneak this in before init starts mounting stuff.
If there's a way to do THAT.... unlimited multiboot from OS images, anyone?
(so far this is kinda dreaming, but would be cool to get it working )

[ShellScript] AndroidFilesInstaller.sh by Adrian DC

Hi everyone !
There's now a lot of features.
Read the webpage to get more informations.
Would you like to install files on Android quickly and with securities? Then read this..
Here are some previews of an earlier version :
This script will run with SManager SManager (ScriptManager),
which is a free and easy to use application for Android.
Before doing anything to the Android system files,
it is obviously highly recommended and adviced
to have a backup in case the files aren't compatible.
Please see the recoveries softwares specific to your phone.
I cannot guarantee this script will work for everyone,
I even know it won't work for everyone because each phone is different
and given the various versions of android and custom roms,
the shell and busybox may not be the same.
You'll need the root permissions to run this script,
I avoided it to run unless it gets root permissions.
busybox also has to be installed (both often go together).
I use busybox 1.20 on my SONY ICS 4.0.3 ROM for the SE Xperia Arc S.
List of phones confirmed to be working with this script :
- Sony Ericsson Xperia S - Android ICS
You can download the script and get infos here :
> http://arcsgatebyadriandc.comze.com/androidfilesinstaller.html
You can find more on this thread of the french Android website and forum :
[Infos] Modifications de la ROM SONY ICS Officielle on PhonAndroid
Thanks for taking interest in this script.
You may contact me to report a bug or ask for a functionality,
or even to say it works fine xD
Have a good day !
Adrian DC

Nice to see you Adrian, I remember you from my LG Viewty days
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

Thanks a lot, that's very nice.
I'm happy to find people back from the old LG Viewty community
And by the way, Viewty's still not dead xD ! Still helping people with it,
using things, fixing others, and giving infos about ViewtyPlus mainly ^^.

Adrian DC said:
Thanks a lot, that's very nice.
I'm happy to find people back from the old LG Viewty community
And by the way, Viewty's still not dead xD ! Still helping people with it,
using things, fixing others, and giving infos about ViewtyPlus mainly ^^.
Click to expand...
Click to collapse
Lol is this a viewty reunion thread already lol good to see you again adc
Sent from my Wildfire S using Tapatalk 2

Nice to see you too man !
Was wondering when you'd see this
Could you guys test my AndroidFilesInstaller script?
I've got some people using it now, and they're all happy about it so far.
I added some nice features in the v7 :
- Automatic AndroidFilesInstaller.sh on sdcard search and replace to update quickly
- Some securities added to the transfert of files.
- Folders with spaces in the name now work too
I'm readapting ViewtyGate website to a new ArcSGate.
Easier to manager files, I'll use my direct files uploader scripts.
Bye !
ADC

Tried it on my wildfire s running cm7 and here's the results
\n AndroidFilesInstaller.sh v7 by Adrian DC\n
Running as Root !\n\n
mkdir: can't create directory '.AndroidFilesInstallerTemp': File exists
rm: can't remove '.AndroidFilesInstallerTemp/AndroidFilesInstaller.sh': No such file or directory
Updating AndroidFilesInstaller...
\n
By default, all files are going to be copied.
Press 'a' for auto-install, using folder name,
press 'b' to only backup those files,
press 'r' to restore those files with backups,
press 'u' to update each AndroidFilesInstaller,
press 'm' to be asked or a key to continue... u\n
/mnt/sdcard/SpeedSoftware/Extracted/AndroidFilesInstaller-v7/AndroidFilesInstaller/AndroidFilesInstaller.sh: 43: Syntax error: word unexpected (expecting ")")
Sent from my Wildfire S using Tapatalk 2

I was replacing the file with v7, you probably got an unfinished one.
Could you come on Messenger please?
I'd like to figure out what's wrong.. \n shouldn't show up, they're new lines...
See ya soon.

Adrian DC said:
I was replacing the file with v7, you probably got an unfinished one.
Could you come on Messenger please?
I'd like to figure out what's wrong.. \n shouldn't show up, they're new lines...
See ya soon.
Click to expand...
Click to collapse
Can't get on messenger I'm not at home at the moment and my data is nearly used up ill try and get on later
Sent from my Wildfire S using Tapatalk 2

Ok.
I've tried some things.. The \n should be gone.
But I'd like you to test it before.
Could you get online when you can, or send me a PM?
Thanks ! Have a nice day !
ADC
EDIT : So.. Did a lot of things on the script to make it even more clean.
\n are gone, that's sure. Other possible problems are gone too.
Many improvements and securities added.
I've put all user available variables at the beginning of the script.
It's all more dynamic and adaptive.
Works perfectly for me and a friend using other Android versions.
The script now also request SManager.
If SManager isn't detected or Root access not given,
you won't be able to run the script. It'll stop at the beginning.
This version 8 is online and available, let me know !
ADC

The v17 of AndroidFilesInstaller.sh will handle complete folders installation from the v16,
aswell as a new security to avoid installation if the file wasn't properly copied to the system,
for example when the available memory space is unsufficient.
Online tonight.

I always get the following error since a few days:
Copy starting...
Copying AndroidFilesInstaller.sh..
Error..
Only ..[AddToBackup], ..[AddToFile]
and ..[RestoreBackup] are accepted
by the script. Skipping..
Copying SystemUI.apk..
Error..
Only ..[AddToBackup], ..[AddToFile]
and ..[RestoreBackup] are accepted
by the script. Skipping..
Copy done !
Click to expand...
Click to collapse
I use the newest ScriptManger, busybox 1.20.2 (also 1.19.4) and I've root and mounted the /system as rw.

Daniel D. said:
I always get the following error since a few days:
I use the newest ScriptManger, busybox 1.20.2 (also 1.19.4) and I've root and mounted the /system as rw.
Click to expand...
Click to collapse
Hey !
The problem mainly comes from an incomplete linux shell,
and this comes because of an incomplete version of busybox and / or superuser.
Try updating the su binary, and using an other busybox, such as 1.19.4 (as you did, works great for me..).
Bye !

Hmm, SU is up to date. I re-installed Busybox three times with the app from the market. Hmmm...

The released online script didn't change for a while, therefore it can only be because of faulty busybox..
Various users had the problem, only answer I can tell is try to find a working busybox,
it would seem some are wrong or not entirely installed....

Strange, I installed my ROM hundred times. It worked always.

[Q] Building for N7100. Failed with "Don't have a product spec"

Hi all
Im trying to compile OmniRom for Galaxy Note 2 N7100.
Did everything as instructed.
When running "brunch n7100" I have an error:
=============================================
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/n7100/omni_n7100.mk]]: "vendor/samsung/smdk4412-common/common-vendor.mk" does not exist. Stop.
WARNING: Trying to fetch a device that's already there
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/n7100/omni_n7100.mk]]: "vendor/samsung/smdk4412-common/common-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'omni_n7100'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
=============================================
What should I do to fix it?
Thanks
EDIT: OK, "The Muppets", of cause. Not it builds...

sms2000 said:
EDIT: OK, "The Muppets", of cause. Not it builds...
Click to expand...
Click to collapse
First off, I'd use DonkeyCoyote instead of TheMuppets. Entropy said TheMuppets wouldn't work, but he might have been speaking about only one device. Still I'd use DonkeyCoyote instead.
Still not building?

PonsAsinorem said:
First off, I'd use DonkeyCoyote instead of TheMuppets. Entropy said TheMuppets wouldn't work, but he might have been speaking about only one device. Still I'd use DonkeyCoyote instead.
Still not building?
Click to expand...
Click to collapse
I'm using VM on Win7 8Gb machine so it's slow. Last time it stopped on Email right after successfully building boot.img.
Attempting to rebuild.
I'll try my next with DonkeyCoyote.

sms2000 said:
I'm using VM on Win7 8Gb machine so it's slow. Last time it stopped on Email right after successfully building boot.img.
Attempting to rebuild.
I'll try my next with DonkeyCoyote.
Click to expand...
Click to collapse
It didn't not stop...
Actually it is compiling libchromodium.so (forget how it spell), which is 1.2GB in size.
Just let it run for few hours, it will completed eventually.
PS: I'm using VM on Win8.1 4GB, no complain here.
Sent from Windows 98

Yep, it fails again and again on 'libwebviewchromium.so'. The well known 'Error 1' aka not enough RAM.
I recently built a dedicated computer (8Gb + Haswell 3220) just for ROM compiler but have no time to install it properly. Dealing with VMs is not good.
My VM has 4Gb RAM of total 8Gb installed. I know I need 8+ but have to wait till new RAM received.
For now the thread is on hold.
Thanks for all your help.
EDIT: Just for the small experiment I added a 8Gb 'swap' partition to VM and the following build succeeded using no more than 450Mb of it.
I think we need 6 to 8Gb of RAM for good.
Now the question is would it boot and run for good? But we will see...

Ya I did set the swap partition to 8gb... And it will boot nicely.
If it didn't boot, jus replace/delete the media_profiles.xml
Another note, my Bluetooth and hardware decoding /encoding fail... Pls test it on ur system too.
Sent from Windows 98

dynomist said:
Ya I did set the swap partition to 8gb... And it will boot nicely.
If it didn't boot, jus replace/delete the media_profiles.xml
Another note, my Bluetooth and hardware decoding /encoding fail... Pls test it on ur system too.
Sent from Windows 98
Click to expand...
Click to collapse
I indeed failed to boot. Just the black screen with nothing. I think it was a very bad idea to use TheMuppets with "jallybean".
And what is "media_profiles.xml" for? And where?

U r using jb blob?
i think OmniRom hv all the stuff u need
http://docs.omnirom.org/Samsung_Galaxy_Note_II
___
Btw did ur screen show omnirom animation?
If yes u r lucky, u need to enabled the ro.adb.secure=0 in ur build.prop, then only you can use adb without authorization to troubleshoot.
Type# adb logcat > logcat.txt
___
Google media profile...
Sent from Windows 98

dynomist said:
U r using jb blob?
i think OmniRom hv all the stuff u need
http://docs.omnirom.org/Samsung_Galaxy_Note_II
___
Btw did ur screen show omnirom animation?
If yes u r lucky, u need to enabled the ro.adb.secure=0 in ur build.prop, then only you can use adb without authorization to troubleshoot.
Type# adb logcat > logcat.txt
___
Google media profile...
Sent from Windows 98
Click to expand...
Click to collapse
Yes, if you can download the closed source parts from the phone itself. I cannot. Something wrong with switching 'adbd' to 'root'. It switches sort of but locks at the downloading (never finishes).
Currently I'm recompiling with 'DonkeyCoyote'.

'Nightly' build fails to pass boot animation
I downloaded and installed OmniRom Nightly. Not good.
It cannot pass the boot animation. The OMNI BA just loops across different colors for 15 minutes already.
As I remember the same problem I have with any AOSP or CM ROM. I suspect the problem is the boot loader related.
When I installed my first 4.3 ROM it required the latest BL and I flashed it. Should I downgrade now? Which version of BL works for sure and where can I find it?
Thanks.
EDIT: I verified. My Bootloader - MJ5. Is it OK?
EDIT 2: Downgraded to DMF2 and succeeded installing OmniRom Nightly. Testing...

glad that you able to solve the booting prob...
pls update the roms status after u done with your testing