Database Develop

[ROM] 5faif ROM v1.5- Now with apps on SD, swap activated and other features.

Hello everybody!
I'm trying to build my own custom ROM for my HTC Tattoo. It is a personal rom just to test and LEARN. The aim of this project is not to be a ROM for daily use, but to test new things and learn.
{
"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"
}
Features in v1.4:
It is based on RUU Click HTC WWE 1.67.405.6.
It formats SYSTEM and DATA partitions first.
Removed HTC Footprints and config files.
HTC Sense UI removed (you have and update to install it: http://uploadmirrors.com/download/S0FGXKJC/update-5faif-ToPutSenseUI-signed.zip).
Added su and flash_image from devs of this forum.
Added boot image version 2 from mainfram3 with some personal changes.
Removed example images.
Busybox in /system/bin/.
Google apps not deleted as this is a PRIVATE rom for testing.
Google Maps updated.
Added JavaBOX app and library.
Added SoundManager.
Added Astro File Manger.
Added Advanced Task Manager.
Added WIFI Tethering.
Market now shows all the apps.
Apps now are installed and executed from SD!!! (You MUST create a "app" folder in your sdcard BEFORE flashing).
Dalvik cache moved to /data.
Swap activated.
If you want to try this ROM, please do this first in order to be able to recover your Tattoo in case something goes wrong:
1. Make a Goldcard: http://forum.xda-developers.com/showthread.php?t=603286
2. Install Custom Recovery from mainfram3.
3. Do Backup from Custom Recovery.
4. Create a folder in your sdcard called "app"
5. Now you are able to flash this ROM through update.zip. ¡ALL DATA AND APPLICATIONS WILL BE REMOVED!
If you don't know how to follow these steps or you don't have root yet, follow this howto (thanks Zecanilis!): http://forum.xda-developers.com/showthread.php?t=645742
Download links:
v1.2 with Sense:
http://uploadmirrors.com/download/6TQVEDK7/5faifCustomROMv1-2-signed.zip
v1.3b:
http://uploadmirrors.com/download/VSY4TSQH/5faifCustomROMv1-3b-signed.zip
v1.4:
http://uploadmirrors.com/download/ER5TW2WQ/5faifCustomROMv1-4-signed_1.zip
v1.5:
http://uploadmirrors.com/download/1DQOGCVG/5faifCustomROMv1-5-signed.zip
Update to install Sense UI AFTER flashing one of the ROMs above):
http://uploadmirrors.com/download/U8UALOA0/update-5faif-ToPutSenseUI-signed.zip
Click to expand...
Click to collapse
Thanks a lot for your attention! And thank you to all the devs in this forum. All my knowledge about Android come from this great forum and its users!
Special thanks to: mainfram3, chusen, coburn, 5[Strogino], moneytoo
[UPDATES]
08/March/2010: update-script renamed to updater-script (thanks coburn). ROM uploaded again (v0.2).
09/March/2010 v1.2: updater-script completely changed. ROM uploaded again (v1.2). Wifi not working. Fix it with : chmod 755 /system/etc/dhcpcd/dhcpcd-run-hooks
09/March/2010 v1.3b: Sense UI completely removed. WIFI fixed.
10/Marzo/2010: Pequeña actualización a v.3c para usuarios actuales de v.2 o v.3b. Widget problems solved: http://forum.xda-developers.com/showpost.php?p=5845000&postcount=56
17/March/2010 v1.4: Execution and installation of applications on SD. Some programs added. If you want to install Sense after flashing it: http://uploadmirrors.com/download/S0FGXKJC/update-5faif-ToPutSenseUI-signed.zip
24/March/2010 v1.5: Dalvik cache moved and swap memory activated. Thanks to fyodor and lgstoian
17/May/2010 Reuploaded version 1.5 and SenseUI patch.

Looking good. I might snip parts of your mods for use with AzusaROM. I'm not too sure about the update-script syntax, the custom recovery we got uses updater-script. More info later...

Ok, but now try to make update without wipe, without formating system and data.
If you want to add/delete some few things - no need to format whole device)

5[Strogino] said:
Ok, but now try to make update without wipe, without formating system and data.
If you want to add/delete some few things - no need to format whole device)
Click to expand...
Click to collapse
Ok! Thanks! I'll try... but.. if I want to remove "things"...I will have to write the proper commands to do so in the update-script, haven't I?
So do you think that this ROM could work? Do you recommend to try to flash it [before creating a goldcard in case something bad happens, of course xD]??
Any ideas for the show_progress command? What does the following numbers mean?
Coburn64 said:
Looking good. I might snip parts of your mods for use with AzusaROM. I'm not too sure about the update-script syntax, the custom recovery we got uses updater-script. More info later...
Click to expand...
Click to collapse
Yeah, that's true. In the hello-world example it is named as updateR-script. Thank you for that tip!

step by step guide
could you please post the istructions you're following to create a custom ROM ?

suoko said:
could you please post the istructions you're following to create a custom ROM ?
Click to expand...
Click to collapse
Of course! I'm going to bed now, so tomorrow I will post all the links I extract the information from. If you can't wait: all the posts are from this forum.

I'm working on a custom rom for tattoo too, but i don't know how to flash un update zip, what's the command? Can you help me?

you need a custom recovery by mainfram3 zip yor rom and copy to sd, rename update.zip, restart the tattoo in recovery mode (home+power) and select "apply sdcard:update.zip"

mikifafi said:
Ok! Thanks! I'll try... but.. if I want to remove "things"...I will have to write the proper commands to do so in the update-script, haven't I?
So do you think that this ROM could work? Do you recommend to try to flash it [before creating a goldcard in case something bad happens, of course xD]??
Click to expand...
Click to collapse
Commands to remove something:
Code:
delete SYSTEM:lib/libA2DP.so
delete SYSTEM:build.prop
delete SYSTEM:xbin/bb/busybox
delete DATA:app_s/MarketEnabler.apk
Creating goldcard is to avoid region (customer id) check ONLY.
But goldcarding keeps company with way to get new ROM - this thing confuse all often)
If you have modified recovery, doesnt matter what CustomerID do you have.

AFAIK and also mainfram3 can back me up on this, is that updater-script uses a 1.6 syntax like ui_write(), format(MTD,'system') etc unlike 1.5 which uses a basic format, with format SYSTEM: etc etc.
This leads us into the grey area, what commands do we have? Is there some that will damage the device? What does update-binary do exactly (I know it updates the ROM, dur , but what exactly).
Unless we can back port 1.5 script syntax to work with mainfram3's custom recovery, it looks like we're limited to trial and error.

Update-binary
These are the functions available in update-binary, through the use of the updater-script:
Code:
void RegisterInstallFunctions() {
RegisterFunction("mount", MountFn);
RegisterFunction("is_mounted", IsMountedFn);
RegisterFunction("unmount", UnmountFn);
RegisterFunction("format", FormatFn);
RegisterFunction("show_progress", ShowProgressFn);
RegisterFunction("set_progress", SetProgressFn);
RegisterFunction("delete", DeleteFn);
RegisterFunction("delete_recursive", DeleteFn);
RegisterFunction("package_extract_dir", PackageExtractDirFn);
RegisterFunction("package_extract_file", PackageExtractFileFn);
RegisterFunction("symlink", SymlinkFn);
RegisterFunction("set_perm", SetPermFn);
RegisterFunction("set_perm_recursive", SetPermFn);
RegisterFunction("getprop", GetPropFn);
RegisterFunction("file_getprop", FileGetPropFn);
RegisterFunction("write_raw_image", WriteRawImageFn);
RegisterFunction("write_firmware_image", WriteFirmwareImageFn);
RegisterFunction("apply_patch", ApplyPatchFn);
RegisterFunction("apply_patch_check", ApplyPatchFn);
RegisterFunction("apply_patch_space", ApplyPatchFn);
RegisterFunction("ui_print", UIPrintFn);
}
Attached to this post you'll find the source to update-binary, from the Android 1.6 SDK.
Hope this helps!

Thank you very very much mainfram3.
With this information I think I would be able to build a update.zip with a working ROM (finally!!).
I will upload it.

Can't get the download links to work... Page cannot be found

Hey mikifafi, how about a tutorial about how did you do this rom customization??
Thanx in advance

¿A new working ROM?
Finally I was able to upload the version 1.2 of this ROM.
I have changed the updater-script, so it must flash now. If it does, you will have a bit faster rom than the original without the slow Sense UI.
You can download it from the first post of this topic: forum.xda-developers.com/showthread.php?t=643368
Please, if someone tries it, post your results
P.S.: Dropping my "favourites" about rom cooking into a text file to post it here later.

Downloading right away Will post back with results.
Btw. Love your new uploading page
thanks for your work!

worked!!! i go to test,after i publish my comments
Thanks for you work

Works here too!
Seems fast at first sight. Will test more and return

Thank you very very very much chusen and whooper90 for trying it in your devices!!
I'm very happy of seeing that it works!!!
Now I notice that I forgot to completely remove Sense UI (it is just desactivated, isn't it?). I will change it and also will remove some not-free apps that shouldn't be there.
Can any of you try to run "busybox --initial" to install busybox, please?
Now, the list of links about cooking ROMs:
Code:
[HOWTO] Create your own boot/recovery images.
forum.xda-developers.com/showthread.php?t=641731
[GUIDE] How to create a your own ROM
forum.xda-developers.com/showthread.php?t=566235
Custom boot.img
forum.xda-developers.com/showpost.php?p=5784735&postcount=35
[How to] Rom cooking
forum.xda-developers.com/showthread.php?t=551711
[HOWTO] Rom cooking
htcpedia.com/forum/showthread.php?t=1404
All I ever wanted in life is to be able to cook an Android ROM -Part One-
androidspin.com/2010/01/27/all-i-ever-wanted-in-life-is-to-be-able-to-cook-an-android-rom-part-one/
Thank you all the people from xda-developers and htcmania that have been working on the tattoo. Without them, building a custom rom wouldn't have been posible. I have just followed their steps.

Thanks man for your links.
Now i'm going to download your rom.

[SCRIPT][Sybr.Lab] Sybr Kernel Cleaning Script Edition 1.1

The Sybr.KCS can thoroughly clean any residue of a kernel files stored on your phone.
{
"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"
}
Visit Sybr.Lab for more informations
Please pay a beer to Sybr.name if you like our work !​
This script is an archive flashable via the Recovery model of your Android phone, it will allow you to flash any kernel starting on a clean base.
This script will do cleaning your phone and remove any residue of previous kernels installed.
Instalaltion
- Put the file on your SD card
- Restart in recovery
- Flashing the script
- Flashing a kernel
- Restart
Download
Sybr.KCS : link
Changelog
More cleaning files for differents tweaks existed (Thunder, SuperCharger, Turbo...)
Changing nick for Sybr Kernel Cleaning Script

Bravo!
Top favorite zips

wooohooo! amazing! thank you!!

good work !

testing this one now, just in time, thanks!!!

I noticed some residue as well, but only the obvious Thanks for doing this to also clean out the other trash...
#Tapatalk #Galaxy Note

edit
Is this a joke? Zip is empty, ony system file. Please explain. Updater script and binaire are different than abyss zip?

Well it is "only" a script that clean (recursive delete):
- cache
- dalvik-cache
- some init.d scripts
- modules that might be left from older kernel
- cache
- dalvik-cache
So yes the system is empty because it is not to overwrite stuff with new things only to clean up some old stuff
BUT BE CAREFULL WITH IT AS IT CLEAN SOME INIT.D scripts THAT MIGHT OR MIGHT NOT BE USEFULL DEPENDING YOUR KERNEL AND THAT NEW KERNEL FLASH USUALLY ONLY WRITE THE KERNEL AND not the scripts from init.d.
So very good/usefull if your are sur/know your ROM and it custom init.d scripts (or backup your init.d scripts before doing it)
EDIT:
here a the init.d that this scripts try to remove
/system/etc/init.d/S70zipalign
/system/etc/init.d/S90scheduler
/system/etc/init.d/S99finish
/system/etc/init.d/89system_tweak
/system/etc/init.d/98system_tweak
/system/etc/init.d/S89system_tweak
/system/etc/init.d/S98system_tweak
/system/etc/init.d/S90screenstate_scaling
/system/etc/init.d/90screenstate_scaling
/system/etc/init.d/98screenstate_scaling
/system/etc/init.d/S98screenstate_scaling

Wow, thx bro

jayGGjay said:
Well it is "only" a script that clean (recursive delete):
- cache
- dalvik-cache
- some init.d scripts
- modules that might be left from older kernel
- cache
- dalvik-cache
So yes the system is empty because it is not to overwrite stuff with new things only to clean up some old stuff
BUT BE CAREFULL WITH IT AS IT CLEAN SOME INIT.D scripts THAT MIGHT OR MIGHT NOT BE USEFULL DEPENDING YOUR KERNEL AND THAT NEW KERNEL FLASH USUALLY ONLY WRITE THE KERNEL AND not the scripts from init.d.
So very good/usefull if your are sur/know your ROM and it custom init.d scripts (or backup your init.d scripts before doing it)
Click to expand...
Click to collapse
Great work, every kernel dev should use this sript in there fash zip.
---------- Post added at 03:32 PM ---------- Previous post was at 03:28 PM ----------
I never use init.d scripts, only 99complete. So again great work.

jblanc,
I don't get the follwing part:
ui_print("* Cleaning olds modules... *");
ui_print("*****************************************************");
package_extract_dir("script", "/tmp/script");
set_perm(0, 0, 755, "/tmp/script/cleaningmodules");
run_program("/tmp/script/cleaningmodules");
show_progress(0.100000, 70);
There is no script folder in zip file, so no reason for it...

The_Steph said:
jblanc,
I don't get the follwing part:
ui_print("* Cleaning olds modules... *");
ui_print("*****************************************************");
package_extract_dir("script", "/tmp/script");
set_perm(0, 0, 755, "/tmp/script/cleaningmodules");
run_program("/tmp/script/cleaningmodules");
show_progress(0.100000, 70);
There is no script folder in zip file, so no reason for it...
Click to expand...
Click to collapse
I was just about to post it.
The zip is missing the script folder, also the system folder can be deleted as it is of no use in the zip.
Sent from my GT-P1000 using xda premium

lol, i was so focused on the updater-scripts I did not notice the module cleaning scripts was missing from the zip.
He might just add the module script in the updater-scripts and do everythings from there.
OR
He could also make a "external" scripts for the init.d scripts so people/dev might tailor it to theirs needs/rom/kernel
Anyway a corrected update should come now that a few have spot those "issue"

jayGGjay said:
Well it is "only" a script that clean (recursive delete):
- cache
- dalvik-cache
- some init.d scripts
- modules that might be left from older kernel
- cache
- dalvik-cache
So yes the system is empty because it is not to overwrite stuff with new things only to clean up some old stuff
BUT BE CAREFULL WITH IT AS IT CLEAN SOME INIT.D scripts THAT MIGHT OR MIGHT NOT BE USEFULL DEPENDING YOUR KERNEL AND THAT NEW KERNEL FLASH USUALLY ONLY WRITE THE KERNEL AND not the scripts from init.d.
So very good/usefull if your are sur/know your ROM and it custom init.d scripts (or backup your init.d scripts before doing it)
EDIT:
here a the init.d that this scripts try to remove
/system/etc/init.d/S70zipalign
/system/etc/init.d/S90scheduler
/system/etc/init.d/S99finish
/system/etc/init.d/89system_tweak
/system/etc/init.d/98system_tweak
/system/etc/init.d/S89system_tweak
/system/etc/init.d/S98system_tweak
/system/etc/init.d/S90screenstate_scaling
/system/etc/init.d/90screenstate_scaling
/system/etc/init.d/98screenstate_scaling
/system/etc/init.d/S98screenstate_scaling
Click to expand...
Click to collapse
Here he explains wy he use system folder

Hi jblanc, what do you think of this post? Is he right?
http://forum.xda-developers.com/showpost.php?p=22022693&postcount=7073

robertberma:
Tx, but i am NOT Jblanc the creator of the scripts only some "guy" with linux knowledge and curiosity that wanted to have a look at it before using it.
So I could NOT explain with he has left the empty system directories. I have only look at the script and understand/try to understand what he was trying to achived with it.

Haha nice picture, is that you? Sorry for his spamming jblanc.

robertberma said:
Here he explains wy he use system folder
Click to expand...
Click to collapse
The system folder is not used in this case, the folder i the zip is for copying files over to system drive, and since no files are copied, it can be deleted.
As for the above lines, those are for deleting files present in the system drive.
In whatever case the system folder inside the zip is not required as of now.
Sent from my GT-N7000 using xda premium

jaiiscool said:
The system folder is not used in this case, the folder i the zip is for copying files over to system drive, and since no files are copied, it can be deleted.
As for the above lines, those are for deleting files present in the system drive.
In whatever case the system folder inside the zip is not required as of now.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Can paste in this zip zimage of every kernel i want to flash. Maby again a stupid quastion but than if i flash a kernel it will do all in one go.

this Zip Should be in developer section
thx Blanco

[Mod] init.d I9300 Installer

init.d for stock rooted Samsung based I9300 ROM without supported custom kernel or baked into rooted ROM
Tested on my device running wanamlite v4.2.1
Requirements
1. Rooted I9300 ROM with busybox
2. custom Recovery (CWM or touch)
3. No supported init.d kernel or ROM
Installation Instructions
1. Download init.d_I9300_ Installer.zip & place on internal sdcard
2. Flash in custom Recovery and reboot
Adding Scripts
a) Copy your favorite init.d scripts into system/etc/init.d folder, set permissions for those particular scripts and reboot OR
b) Flash your scripts packaged in a CWM flashable zip in Recovery and reboot
Set Permissions Example : using Root Explorer app from my own SGT-P6810 ROM
Mount system R/W
{
"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"
}
Long tap on script → set permissions → OK → reboot device
To check it's actually worked
Navigate with a root explorer :
1. data/local/tmp/init.d_log_test.txt
2. system/etc/init.d folder
3. system/etc/install-recovery.sh
4. system/bin/sysinit
If they're all there, all has gone well, and you're all set to go
You may delete #1 init.d_log_test.txt and 99test from inside init.d folder when done. It's just a way to confirm scripts will actually run on boot.
Above #2-4 are required to run your scripts, so don't mess with them!
But you can add / delete any "suitable" script inside the init.d folder though (as always, have a recent nandroid backup in safe place in case your device has any issues!)
Credits
DooMLoRD
.
.

UpInTheAir said:
init.d for stock rooted I9300 ROM without supported custom kernel or baked into rooted ROM
Tested on my device running wanamlite v4.2.1
Requirements
1. Rooted I9300 ROM
2. custom Recovery (CWM or touch)
3. No supported init.d kernel or ROM
Installation Instructions
1. Download init.d_I9300_ Installer.zip & place on internal sdcard
2. Flash in custom Recovery and reboot
3. Place your favorite init.d scripts into init.d folder, set permissions and reboot
To check it's actually worked
Navigate with a root explorer :
1. data/local/tmp/init.d_log_test.txt
2. system/etc/init.d folder
3. system/etc/install-recovery.sh
4. system/bin/sysinit
You may delete the 99test from init.d folder when done............
Credits to DooMLoRD
.
.
Click to expand...
Click to collapse
Hi! I have a few questions.
In Installation Instructions...when you say "Place your favorite init.d scripts into init.d folder, set permissions and reboot"....with 'set permissions' do you mean the permissions to my personal files I'm adding to the folder?
If YES...which are the correct permissions for those files?
Other question but about the Checking if it's Working....must I execute the "install-recovery.sh" file after last reboot or what?
In case YES, what does it to?
What about the 'sysinit' file? Why is that file needed for adding the init.d folder support? Should I delete also that one once I've made all the tests?
Thank your very much.
Sent from my GT-I9000 using xda app-developers app

PIRATA! said:
Hi! I have a few questions.
In Installation Instructions...when you say "Place your favorite init.d scripts into init.d folder, set permissions and reboot"....with 'set permissions' do you mean the permissions to my personal files I'm adding to the folder?
If YES...which are the correct permissions for those files?
Other question but about the Checking if it's Working....must I execute the "install-recovery.sh" file after last reboot or what?
In case YES, what does it to?
What about the 'sysinit' file? Why is that file needed for adding the init.d folder support? Should I delete also that one once I've made all the tests?
Thank your very much.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Please re-read OP as some more info and screen-shots added.
Don't forget to nandroid in case you have any issues with your scripts!
You can write your own, search XDA and Google for many. But this thread isn't a tutorial on that, it's just a Mod................

UpInTheAir said:
Please re-read OP as some more info and screen-shots added.
Don't forget to nandroid in case you have any issues with your scripts!
You can write your own, search XDA and Google for many. But this thread isn't a tutorial on that, it's just a Mod................
Click to expand...
Click to collapse
Ok I understand it's a mod...but why is it needed to execute the ".sh" file?
Is it a one execution file that will be never executed again?
What does it do?
Just very curious and very interested in if that file and related binary are so important to remain in my phone if I will never run/use them again.
Thank you.
Sent from my GT-I9000 using xda app-developers app

PIRATA! said:
Ok I understand it's a mod...but why is it needed to execute the ".sh" file?
Is it a one execution file that will be never executed again?
What does it do?
Just very curious and very interested in if that file and related binary are so important to remain in my phone if I will never run/use them again.
Thank you.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I'm not 100% sure, I've only adapted DooMLoRD's work for my P6810 ROM and I9300 Mod here, and then packaged into a CWM zip with correct system mount etc
I have deleted the data/local/tmp/init.d_log_test.txt, renamed both sysinit and install-recovery.sh (.bak) and rebooted. A new log file was present with "done". I suppose they are not possibly needed after flash (could be wrong), but I have not tested (and don't plan to) any further. In any case, the files are just a few bytes each.
Credit was given in Post #1, so as I'm not the original creator, maybe you could post your curiosity in his thread there ?
[ADDON][Xperia S] Generic startup/init.d scripts support for Stock ROM/Kernel
.
.

UpInTheAir said:
I'm not 100% sure, I've only adapted DooMLoRD's work for my P6810 ROM and I9300 Mod here, and then packaged into a CWM zip with correct system mount etc
I have deleted the data/local/tmp/init.d_log_test.txt, renamed both sysinit and install-recovery.sh (.bak) and rebooted. A new log file was present with "done". I suppose they are not possibly needed after flash (could be wrong), but I have not tested (and don't plan to) any further. In any case, the files are just a few bytes each.
Credit was given in Post #1, so as I'm not the original creator, maybe you could post your curiosity in his thread there ?
[ADDON][Xperia S] Generic startup/init.d scripts support for Stock ROM/Kernel
.
.
Click to expand...
Click to collapse
Thank you very much. Just asked
...but I think that it is better not to delete nothing except the 99 test file.
I'll let you know.
Sent from my GT-I9000 using xda app-developers app

PIRATA! said:
Thank you very much. Just asked
...but I think that it is better not to delete nothing except the 99 test file.
I'll let you know.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
No problem.
I agree to leave it alone.
The log and test script can be safely removed though.
Sent from my GT-I9300 using xda premium

This Mod is now featured on the Index of mods INDEX ALL IN 1
Any observation please send me PM

Will do tx
Sent from my GT-I9300 using xda premium

Thx so much.

[MOD] [KERNEL] [pollux_windy] ROMSwitcher [DUALBOOT]

{
"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"
}
Rom Switcher
This is a Mod which allows you to switching between Timescape and any AOSP based rom.
It's only for advanced users and I am not responsible if your device get bricked or transform into a monster and eat up your cat.
Before you install this, please read the whole post!
Your first rom is Stock Timescape and second rom is any AOSP rom.
The second rom is installed on the /cache partition.
/data and /cache folders for second ROM is in /data/dual/
This Mod switches between two kernels.
For Timescape you have to use my CWM kernel for Sony Rom, for AOSP you have to use my modified CM kernel which will be automatically downloaded by the app.
What is this project about?
Its about a dual boot implementation that is somewhat universal and supports a lot of device. We are the Rom Switchers.
Default kernel for Timescape is Stock Sony Kernel with CWM,
if you want to use another kernel, replace fiirst.img in /sdcard/romwitcher/ with your favorite kernel(must support the rom you are installing).
Sources:
Kernel Source
Dual Boot ramdisk
Currently only supports pollux_windy (might port to pollux if there is enough support)
How to install?
You can use any AOSP rom for second rom!
Needs Unlocked bootloader
First Install stock ROM .ftf
Install CWM kernel and root from HERE
Install BusyBox from HERE
Lazy Version
Open Your AOSP rom zip and copy this zip over it- LINK
Open Your Gapps zip and copy this zip over it- LINK
Long Version
Download any AOSP rom. Extract it and open META-INF/com/google/android/updater-script
replace this line
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
with this wherever u see it
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/cache", "/system");
then delete these lines
Code:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
and
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
and
Code:
assert(getprop("ro.product.device") == "SGP311" || getprop("ro.build.product") == "SGP311" ||
getprop("ro.product.device") == "SGP312" || getprop("ro.build.product") == "SGP312" ||
getprop("ro.product.device") == "pollux_windy" || getprop("ro.build.product") == "pollux_windy");
You will need Gapps
Get it here http://goo.im/gapps/
Extract it and open updater-script
and replace
Code:
run_program("/sbin/busybox", "mount", "/system");
with
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/cache", "/system");
Zip your rom and gapps.
Flash both in recovery. (first rom then gapps)
DO NOT WIPE ANYTHING
Reboot your phone and if you did all correct. You should boot into your Timescape Stock rom.
Now download and install the app
Download app here
Open ROMSwitcher and follow the instructions. It will fetch required files automatically
NOTE: Currently First Rom needs to be Sony and Second rom any aosp rom, you can manually replace the first.img with a stock cm kernel to dual boot 2 aosp roms (the folder is /sdcard/romswitcher/, this method should work but i have not tested it due to lack of time)
That's all have fun
​
XDA:DevDB Information
[MOD] [KERNEL] [pollux_windy] ROMSwitcher [DUALBOOT], a Kernel for the Sony Xperia Tablet Z
Contributors
bluefa1con, mithun46
Kernel Special Features:
Version Information
Status: Testing
Created 2013-09-05
Last Updated 2013-09-06

Reserved
Wipe data/cache on AOSP rom
Wipe data:
Delete /data/dual/2nddata
Wipe cache:
Delete /data/dual/cache
Install new AOSP rom
Wipe cache in recovery and delete /data/dual
then flash your new rom
Remove AOSP rom
Wipe cache in recovery and delete /data/dual
Currently Using a AOSP rom as first rom?
Here is a experimental method, try and report
copy your /data partition on sdcard (wipping data from flashtools deletes internal sdcard)
After following instructions and installing rom
Copy the /data backup to /data/dual/2ndromdata
Support us
Press Thanks
Press "Tip us?" above the OP
Rate this Thread with 5 Stars
Report bugs
Future Plans
An app to Install directly to second rom (already in development)
A recovery to manage RomSwitch project (talking to some recovery developers)
Share data between first and second rom to have a unique dual boot experience and share apps (already in development)
Devices ROMSwitcher Supports
Google Nexus 10 [manta]
Samsung Galaxy S4 [i9500]
Sony Xperia ZL [C6503]
Sony Xperia Z C6603​

Reserved
Credits
@Grarak - For Coming up with this amazing idea
@Jijonhyuni - using the same dualboot method as he does on Galaxy Nexus
@gokhanmoral - using some scripts of his Siyah Kernel
Paul O'Brian - for concept
@mithun46 - for core development of rom switch and helping me get fimiliar with Sony Devices
Changelog
5-09-2013
First Release
​

Thanks. Been waiting a long time for something like this. Downloading now. Thanks again

I have followed all the steps here indicated, like this:
Starting with a fresh flash of a Sony stock 4.2.2 firmware.
Flashing modified kernel and rooting.
Modifying PAC nightly (09.05) updater-script.
Modifying GApps updater-script.
Flashed them both, first ROM, then GApps.
Successfully booted stock.
Installed ROMSwitcher.
Opened it and it downloaded a download.zip.
After finishing downloading, re-opened ROMSwitcher.
It receives root permissions but then it's just a black screen, all I see is top and bottom bars.
I guess that when I open ROMSwitcher, it should show me a menu with both roms, right? What could I've done wrong? Should I flash that download.zip or something?
I'd appreciate any help Thanks in advance.

Shanliang- said:
I have followed all the steps here indicated, like this:
Starting with a fresh flash of a Sony stock 4.2.2 firmware.
Flashing modified kernel and rooting.
Modifying PAC nightly (09.05) updater-script.
Modifying GApps updater-script.
Flashed them both, first ROM, then GApps.
Successfully booted stock.
Installed ROMSwitcher.
Opened it and it downloaded a download.zip.
After finishing downloading, re-opened ROMSwitcher.
It receives root permissions but then it's just a black screen, all I see is top and bottom bars.
I guess that when I open ROMSwitcher, it should show me a menu with both roms, right? What could I've done wrong? Should I flash that download.zip or something?
I'd appreciate any help Thanks in advance.
Click to expand...
Click to collapse
How big is the size of download.zip? It should be in /sdcard/romswitcher
I assume you have installed busybox too
Sent from my GT-I9100 using Tapatalk 4

Can you tell me what did i do wrong?
after unpacking Gaaps + carbon AOSB based rom .. edited the update-script file.
flashed with cwm ..
installed RomSwitcher apk .waited for the Download.zip to finish downloading
Opened the app again .. selected 4.3 rom
the app get root permission ,. then restarting to the same stock rom.
download.zip size is : 20.39MB

What rom it supoted??
I instal whis cm-10.2-20130905-NIGHTLY-pollux_windy.zip
And after select Android open sourse project 4.3
i take rebut system only ((
Us I see you mistake. First and second img its one file. whis diferent name.

Half Alive said:
Can you tell me what did i do wrong?
after unpacking Gaaps + carbon AOSB based rom .. edited the update-script file.
flashed with cwm ..
installed RomSwitcher apk .waited for the Download.zip to finish downloading
Opened the app again .. selected 4.3 rom
the app get root permission ,. then restarting to the same stock rom.
download.zip size is : 20.39MB
Click to expand...
Click to collapse
xam1988 said:
What rom it supoted??
I instal whis cm-10.2-20130905-NIGHTLY-pollux_windy.zip
And after select Android open sourse project 4.3
i take rebut system only ((
Us I see you mistake. First and second img its one file. whis diferent name.
Click to expand...
Click to collapse
You guys didn't install busy box
Get it from playstore
Sent from my GT-I9100 using Tapatalk 4

bluefa1con said:
You guys didn't install busy box
Get it from playstore
Sent from my GT-I9100 using Tapatalk 4
Click to expand...
Click to collapse
No .. i did install busybox ... Twice

bluefa1con said:
You guys didn't install busy box
Get it from playstore
Sent from my GT-I9100 using Tapatalk 4
Click to expand...
Click to collapse
I have instaling busy box.
Us i right download.zip has two same img. file.
to 11 MB ich one.
Can you posted here corectly
Second.img???
Us i understend
first.img - its stock core.
second.img - must be moded core for pollux_windy roms.
But in folder we have same img. file

^
Yes it have the same size.. But If it's the same kernel I think when we switch to the AOSP rom we should get a bootloop !?
Or maybe that's how it works .. with the same modded kernels
...
I've deleted the RomSwitcher folder containing the two kernels and download.zip and give it another try.
Got the same result .. restarting to the stock rom. =/

Half Alive said:
I've deleted the RomSwitcher folder containing the two kernels and download.zip and give it another try.
Got the same result .. restarting to the stock rom. =/
Click to expand...
Click to collapse
I raplese core from
cm-10.2-20130905-NIGHTLY-pollux_windy.zip
to
RomSwitcher folder
and
raname it to second.img
After choose selected 4.3 rom
I see CM images.
But after black display and dont wont start ((
I flash my firmware againe.

^
Your fault .. We just have to wait for a response from the OP.

xam1988 said:
I raplese core from
cm-10.2-20130905-NIGHTLY-pollux_windy.zip
to
RomSwitcher folder
and
raname it to second.img
After choose selected 4.3 rom
I see CM images.
But after black display and dont wont start ((
I flash my firmware againe.
Click to expand...
Click to collapse
thats because the default cm image u used is not configured to boot second rom and its trying to boot sony files
what i think went wrong with your installs is busybox because busybox is supposed to change kernel from first.img to second.img
did u use smart install on that app?
i am uploading the same first.img and second.img to my host so u guys can try that too but i think the issue here is busybox if u already have working root and cwm

bluefa1con said:
thats because the default cm image u used is not configured to boot second rom and its trying to boot sony files
what i think went wrong with your installs is busybox because busybox is supposed to change kernel from first.img to second.img
did u use smart install on that app?
i am uploading the same first.img and second.img to my host so u guys can try that too but i think the issue here is busybox if u already have working root and cwm
Click to expand...
Click to collapse
I don't think it's busybox related.. I'm sure it's installed correctly.
When I tried to install busybox to another folder.. The device didn't reboot at all.
So I think rebooting the device means that busybox is working.
And you didn't tell us.. does the two. img files have the exact same size?

bluefa1con said:
thats because the default cm image u used is not configured to boot second rom and its trying to boot sony files
what i think went wrong with your installs is busybox because busybox is supposed to change kernel from first.img to second.img
did u use smart install on that app?
i am uploading the same first.img and second.img to my host so u guys can try that too but i think the issue here is busybox if u already have working root and cwm
Click to expand...
Click to collapse
I flash second.img from fasboot to my tablet, and after restart my tablet start in stock rom/
it means that you include to download.zip
the same core. this diferent name!

xam1988 said:
I flash second.img from fasboot to my tablet, and after restart my tablet start in stock rom/
it means that you include to download.zip
the same core. this diferent name!
Click to expand...
Click to collapse
oh God! derped really hard there, was really tired when i posted that
uploading the second.img again, will also update the app's links

updated files pushed
delete the files in /sdcard/romswitcher/ folder and let the app download it again

bluefa1con said:
updated files pushed
delete the files in /sdcard/romswitcher/ folder and let the app download it again
Click to expand...
Click to collapse
All Ok. Work perfectly.
SGP 311 STOK 4.2.2 + cm-10.2-20130905-NIGHTLY-pollux_windy.zip
Big senks for your work.
And sory for my English.
Sent from my SGP311 using xda app-developers app

[TUTORIAL]Super DUPER SwiftKey v3 - Add, Remove, Update SwiftKey Themes - MAY 8, 2015

Now, there was a lot of contention over this in the original SuperSwiftKey thread and I wanted to first apologize for the drama which I accidentally started - I was never intending to steal anybody's work and claim credit for it, nor did I intend to release other's work against their permission [I thought the project was dead]. In this thread, I will be teaching you (with pictures) how to create your very own hand-selected superswiftkey APK and update it immediately upon swiftkey updates, with minimal work! If you can use Notepad++ and Winrar and follow instructions, keep reading!
With that out of the way, thanks first to....
@jaggyjags - for his work on Themed SwiftKey V12
@sonnysekhon - for his work on SuperSwiftKey
@djdarkknight96 - the BOY!!!
Code:
Changelog:
v3 - Appended OP with instructions to remove spacebar logo and update to betas on your own
v2 - Updated December 5th, 2014 - How to do on mobile devices and how to update to newer SwiftKey.
v1 - Created on November 30th, 2014
MAY 8, 2015:
Update to guide:
Step 1: Pick your base apk (Stable or Beta) -- this is SUPERSWIFTKEY by Sonny and DJDarkKnight96
SuperSwiftKey-5.2.2.133.apk: https://www.androidfilehost.com/?fid=23991606952598509
or
SuperSwiftKey-Beta-5.3.0.77.apk: https://www.androidfilehost.com/?fid=23991606952598508
Step 2: Make sure you have 7-zip or WinRar installed if on a windows and open the apk as an archive, this is so we can access the Themes individually and choose which we want to include in our final signed apk. Now would be a good time to get an apk signing tool as well!
Step 3: Download your target. For me, it's the latest SwiftKey Beta (May 7th) and removing the logo from the keyboard. So here's how on a windows (or mac or unix, it's the same concept.)
SwiftKey Keyboard Beta 5.3.0.85: http://www.apkmirror.com/apk/swiftk...-keyboard-beta-5-3-0-85-android-apk-download/
Step 4: Open the latest apk target with 7-zip, and do the same with the super version, so you can extract the themes folders and json file.
Step 5: Delete everything in \assets\themes\
Step 6: Add your modified themes folder to your apk file instead, compression will take a little bit of time.
Step 7 (Optional): Remove SwiftKey logo from spacebar!
Navigate to: \res\drawable-YOURRESOLUTION\ and make branded_spacebar_logo.png a transparent image, once everything is appended, you need to sign the apk again and you're done.
If any of this is unclear then please read my full thread, this is simply an update!
-------------------------- PART 1 - CREATING CUSTOM APK ON A COMPUTER --------------------------
1) Pre-Requesite Files and Applications
Download our SwiftKey “base”- https://www.androidfilehost.com/?fid=95784891001615911
Apktool 2.0 RC2 (Not required, but useful for really decompiling and taking apart more of the apk) - http://forum.xda-developers.com/showthread.php?t=1755243
Some Sort of APK Manipulator:
APK Multi-Tool (To sign the final APK)
Windows: http://forum.xda-developers.com/showthread.php?t=1310151
Linux: http://forum.xda-developers.com/showthread.php?t=1808319
apk-signer - https://code.google.com/p/apk-signer/ (just a .jar, no bloat/extra tools)
In the following image you will see what the themeslist.json file looks like. It is found inside your swiftkey apk in /assets/themes/ We’re going to clean it up and get it ready to start hacking.
Code:
{
"themes": [
{
"formatVersion": 1,
"minorVersion": 6,
"id": "nickel",
"name": "Nickel"
},
{
"formatVersion": 1,
"minorVersion": 7,
"id": "cobalt",
"name": "Cobalt"
},
{
"formatVersion": 1,
"minorVersion": 4,
"id": "ics",
"name": "Holo"
},
{
"formatVersion": 1,
"minorVersion": 4,
"id": "dark",
"name": "Dark"
},
{
"formatVersion": 1,
"minorVersion": 6,
"id": "darkalt",
"name": "Forest"
},
{
"formatVersion": 1,
"minorVersion": 4,
"id": "default",
"name": "Light"
},
{
"formatVersion": 1,
"minorVersion": 4,
"id": "neon",
"name": "Neon"
},
],
"version": 1
}
Right, so this is my “stock” Default SwiftKey apk and contains 20 folders and 1 file, but for our purposes (using the stock SwiftKey straight updated from the play store) as our base, I will tidy the themes folder…. this is in preparation of adding the new files to it! This is themeslist.json, I edited it to remove some themes I found undesirable. It’s quite intuitive.
Also, make sure the last theme block doesn’t have a }, comma following the closing bracket! Every single one should except for the last.
2) Adding 3rd Party Themes to the Installed Themes List:
{
"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"
}
Example A.
Open your target apk. In our case, this is the newest swiftkey play store apk. In WinRar (I use winrar above in pic. A) but all you need to do is delete the contents of your themes folder in swiftkey.apk/assets/themes/* - the folders and .json go bye bye to be replaced with our work
Example B
In Example B, I show the edited apk’s contents of the themes folder. I want to keep Cobalt, Nickel, and some other stock themes so I kept those.
Open Notepad++ or your preferred text editor, and use some common sense to figure out how the JSON blocks are structured.
Code:
{
“formatVersion”; 1,
“minorVersion”; 4,
“Id”: “ics”,
“name”; “Holo”
},
Example C
In this picture, Example C, I point out the final part of the document and how it has to be formatted. Notice the last } for the individual themes has NO comma, and the rest of the document is standard.
Example D
3) Removing Stock Themes
In Example D, I demonstrate how to REMOVE themes that I don’t want (the stock ones for the most part, as well as to not have a SwiftKey with 125 themes...talk about useful! *sarcasam*
This is for you guys who want the most minimal apk possible. As you can see I include the entire block for each theme and also remove their corresponding theme folder from the apk.
Example E
In themeslist.json, select the blocks for the themes you wish to REMOVE and delete them.
Make sure to keep the file structure as it is.
If you guys have any questions on the process please ask, it's pretty straightforward so I figured I didn't need to go that in-depth about it.
ADDED FRIDAY, DECEMBER 05 2014.
HOW TO DO THIS ON A MOBILE DEVICE! ALSO, GUIDE TO UPDATING TO BETA APK AND KEEP UP-TO-DATE WITH SWIFTKEY!
-------------------------- PART 2 - CREATING CUSTOM APK ON AN ANDROID DEVICE --------------------------
Needed apps:
X-Plore File Manager (Play Store)
ApktOOl 4.6 - DOWNLOAD
Step 1: Set up X-Plore File Manager.
Open X-Plore File Manager and navigate in one of the panels to the Download directory of the edited swiftkey. It is recommended you make a directory to put your two apk files and extracted themes (more on this later).
Step 2: Extract the themes from SuperSwiftKey.
Within your SuperSwiftKey apk file, now opened up as a .zip within X-Plore, navigate to /assets/ and long press the folder /themes/. Make sure your SwiftKey FOLDER (not apk) is open in the 2nd panel, and copy the folder from the apk to the SD card. This will take a few minutes.
(for reference, these are the themes within the SuperSwiftKey apk file, much more substantial than the original SwiftKey)
Step 3: Remove the themes folder from the Original SwiftKey.
Now switch to your Swiftkey folder and long press the ORIGINAL (or target) apk file. Open it as a zip like the original, and navigate to /assets/ - long press the /themes/ folder and hit “delete” - this will take a few minutes for the apk to repack itself.
Step 4: Move themes folder to New SwiftKey apk.
Now, here’s the most important part. You need to have x-plore set up properly with both windows in order to execute this command properly. In one tab, have your target swiftkey apk opened as a zip file, and navigated to /assets/ directory.
Switch to the other tab, and long press the themes directory you’ve extracted before. Press “Copy” to copy it to the /assets/ folder IN the apk. It will take 5-10 minutes to pack.
If you wish to remove themes from SwiftKey, you can edit the themeslist.json file (read the main guide for that)
This is what your final apk should look like before we leave X-Plore file manager:
Step 5: Sign and Install the APK
Open ApktOOl on your phone and accept the license agreement.
Then navigate to your Swiftkey folder, in my case it is:
/storage/emulated/0/SwiftKey/Swiftkeyblahblah.apk
Long-press your newly modified apk and select the option to “Get root access permission”
Then, don’t long-press but rather single-tap your apk file that you just got root access for, and of the many many options select “Sign”
THIS IS THE NEXT THING THAT I SEE ON BOTH OF MY DEVICES:
DON’T WORRY! This is fine! Just leave your phone for 5-10 minutes, it will pop up a tiny toast message when completed, and create a new SwiftKey apk file with the suffix -sign.apk. This means you’re set! Verify the size, and you’re good to go.
Now, you’re ready to install. Enjoy!

Yay, So awesome!
Thank you!
Sent from my BlakKat CM11 powered OnePlus One "BACON"

You mentioned that this can be done on the phone? I am looking to delete unused themes. Thanks for the hard work and providing the tutorial!
Sent from my SM-G900A: NakedTouchwiz 3.1

Thank you man

@djdarkknight96 told me you won't require a pc :-/

Thanks for sharing this guide.
For people who want to edit Swiftkey apk from their phone you can sign your modded apk via ZipSigner app and use the key/mode testkey.
Happy theming guys

Primokorn said:
Thanks for sharing this guide.
For people who want to edit Swiftkey apk from their phone you can sign your modded apk via ZipSigner app and use the key/mode testkey.
Happy theming guys
Click to expand...
Click to collapse
Can you elaborate like what should I do with the original apk on my phone step by step

Aashuk Mehta said:
Can you elaborate like what should I do with the original apk on my phone step by step
Click to expand...
Click to collapse
The steps are the same. You can use Zarchiver app to open the original apk and modify the files. You also need an app if you want to change pictures. BTW Turbo Editor is a nice app to manage .json files.

err very noobish question. I extracted the apk n then edited a few files. how do I again make it an apk file? extracted the apk from my phone n edited it too. now I need to pack it to apk file but I don't know how. tried compressing the files into zip again n renamed it back to apk . lol. pretty sure I am doing some silly stuff.

murlidhar85 said:
err very noobish question. I extracted the apk n then edited a few files. how do I again make it an apk file? extracted the apk from my phone n edited it too. now I need to pack it to apk file but I don't know how. tried compressing the files into zip again n renamed it back to apk . lol. pretty sure I am doing some silly stuff.
Click to expand...
Click to collapse
With a PC you can simply drag & drop the new files to the original apk. On your left you have your windows explorer and on your right you open the apk with 7-zip for instance. Then sign the modded apk.
From a phone I think it's easier to modify the apk without extracting its content.

Primokorn said:
With a PC you can simply drag & drop the new files to the original apk. On your left you have your windows explorer and on your right you open the apk with 7-zip for instance. Then sign the modded apk.
From a phone I think it's easier to modify the apk without extracting its content.
Click to expand...
Click to collapse
that is what I am asking. how do I modify the apk from phone without extracting the contents?
[emoji16]
I have zipsigner installed already but need to have the edited apk first.

murlidhar85 said:
that is what I am asking. how do I modify the apk from phone without extracting the contents?
[emoji16]
I have zipsigner installed already but need to have the edited apk first.
Click to expand...
Click to collapse
I use xplore file manager and it has an option to open apk as zip, I use that feature to edit apks without extracting anything..

I will post a picture tutorial on how to do it without even a PC. Also, do you guys want a recorded voice-over video tutorial?

berryman13 said:
I will post a picture tutorial on how to do it without even a PC. Also, do you guys want a recorded voice-over video tutorial?
Click to expand...
Click to collapse
That'll work

I am posting a guide screenshotted from my phone on how to do this without a computer

berryman13 said:
I am posting a guide screenshotted from my phone on how to do this without a computer
Click to expand...
Click to collapse
Thanks :good:

Added a guide on creating the apk on mobile....
I am updated to swiftkey beta .71!

berryman13 said:
Added a guide on creating the apk on mobile....
I am updated to swiftkey beta .71!
Click to expand...
Click to collapse
You freaking rock man, totally awesome tutorial! [emoji106] [emoji106] [emoji106] [emoji106] [emoji106] [emoji106] [emoji106]
Sent from my BlakKat CM11 powered OnePlus One "BACON"

Do I really need x-plore file manager? Or with root Explorer is enough?

Tinchoska said:
Do I really need x-plore file manager? Or with root Explorer is enough?
Click to expand...
Click to collapse
I xplore is compulsory, bcoz it edits apks without unpacking it. Es can't do that as I see