- Title: G4S AOSP 4.4.2 TF
- Listed: July, 2014
- Last modified: 08/01/2014 7:18 pm
- Version: 4.4.2
You must be logged for ROM download.
78024 total views, 19 today
257 Total favorites
DESCRIPTION
Overview: From the Team Force we bring this new ROM "AOSP 4.4.2 TF".
It is characterized, like all AOSP, being a pure Android version, without layers of customization. Enjoy the pure Android experience on your hands.
Name: AOSP 4.4.2 TF
Version: 4.4.2
Date Posted: 07/07/2014
Size: 382.6 MB
Apks included:
Busybox Pro
Fast FasterGPS.
Mobileuncle.
Download: From Mega
Changelog: AOSP 4.4.2 TF V1
Ported Lenovo S939.
Android 4.4.2 KitKat.
Autoroot
Added in Power Recovery Menu.
Density changed to 320.
Camera 13mpx.
Sound HD.
HD Video Recording.
Deleted the notice of non-SIM.
Write access to SD.
APN of Spain.
GPS lock faster.
Improved GPS positioning.
Spain GPS Settings.
Multilanguage.
Apex Launcher 2.4.1.
Android Keyboard L.
New Videoplayer.
Clock.
APK uninstallable:
Is Explorer.
Busybox Pro
FasterGPS.
Mobileuncle Tools.
Tweaks:
Proximity.
3G signal.
Scripts:
RAM.
Speed.
SQlite.
Customization
New logo for Team Force.
New bootanimation Force Team.
New Team Force padlock.
Changelog: AOSP 4.4.2 TF V2
BASE ROM: AOSP TF V1
INCLUDED UPDATE.1
NEW CAMERA FIX INCLUDED
ART DEFAULT
SD MEMORY LIKE HOME
CHANGED GPS
CHANGED GPS.CONFIG
CHANGED EPO
APN CHANGED SPAIN
CHANGED CONTACTS
CHANGED DIALER
CHANGED FLASHLIGHT
FIXED LOCATION EM
MEGABASS SOUND
SURROUND SOUND
Tweaks:
-3G tweaks
-Internet tweaks
-Improves performance touch
-Improved scrolling
-Improves Battery In Standby
Scripts:
-Loopy-Smoothness
-Optimize-Sqlite
-Speedy-Modified
APEX LAUNCHER PRO 2.5.0
APK uninstallable:
OPERA MINI
Installation
WITH 4.2.2
KITKAT STOCK ROM V.1 http://pan.baidu.com/share/lin…..1680007479
FIRST .. IF INSTALLING THIS ROM STOCK KITKAT V.1 (NEVER THE V.2 OF 24-7) BY SPTOOLS ..
AFTER INSTALLING RECOVERY FOR KITKAT ..
WITH 4.4.2
Format SD (micro SD). (RECOMMENDED)
Download ROM and copy it to SD.
Login Recovery.
Wipe Data.
Wipe Cache.
Wipe Dalvik Cache.
Format System.
Install ROM from SD.
Automatic restart.
Configure Wi-Fi.
Configure Google account.
Wait 5 min. A ROM that is stable.
Apk Update of Google.
Open the BusyBox apk.
We hope for it to load to 100% and activate AutoUpdater.
Install and chose Smart Install.
Reboot and you're ready.
UPDATE AOSP KITKAT
Latest Gapps
New Camera Jiayu ..HD VIDEO
Sound Pack. Clearmusic+Megabass.
Installation
Copy the zip in SD memory
Log in Recovery
Install zip from SD memory
No need wipes
reboot..fix root.
FLASH CTR RECOVERY 4.4 ZIP
EASY TO CHANGE FROM YOUR CURRENT RECOVERY RECOVERY.
JUST COPY THE CTR ZIP IN SD.
ENTER IN RECOVERY AND FLASH THE CTR ZIP
REBOOT
Your IMEI number is "Unknown" or "Invalid" ?
Try this method;
http://en.miui.com/thread-10061-1-1.html
Screenshot
|
|
|
Videoreview
※Please make a backup of your device before installing or updating ROM


Member Info






I did as described and now the phone shows the TF logo and doesnt wanna start keep repeating only!! Any help plz
For proximity sensor: I tested with mobile uncle tool and it work fine.
I got the problem with gesture and call. When calling the touch goes off only for 1 second and then again…
Some tips?
TRY DELETING"# Apaga la proximidad rapido despues de la llamada " OF build.prop
m.ali24
look for my previous posts.
same problems and now everything is ok
fagorn
I have read all the posts already, but I have a serius problem here. I hope you could help me with it. first, I installed MU Kitikat ROM to be able to install this ROM. I did exactly as in the steps, and I installed the ROM. Once done it only showed the logo and kept restarting. I tried to log into recovery manually Power+Volume down or up or all together; I have just tried everything but en vain. All what I got was a bootloop afterall!! I thought of intsalling the Kitkat ROM again since I install it vbia flashtool so no need to log into recovery, but also I got a BROM Error message. Now, the phone doesnt wanna operate at all. But when I remove the battery and plug it into the PC it gets connected. Someone told me to hlop vlume up before flashing, I did as I was told and the flashing started for about 10 Secs only then aborted with another error message. Now I donno if my phone is bricked or what. Please advice, cause I need to use the phone. Sorry for prolonging
BEFORE FLASHING THE ROM FOR SP TOOLS YOU NEED TO HAVE ADB INSTALLED THE DRIVER .. YOU ADVISE .. WINDOWS 7 AFTER NEXT STEPS TO INSTALL FROM SPTOOLS. DO NOT INSTALL THE LATEST VERSION OF JIAYU 4.4.2. AFTER RESTART WITH CHANGE THE STOCK RECOVERY VERSION .. AND FOLLOW THE STEPS OF INSTALLATION AOSP ROM
NEWTON
You mean I should install 4.2 ROM not KITKAT? Would it make a difference? And what AOSP ROM??
AOSP ROM must be logged into recovery to install it, right??? My phone doesnt operate at all!!! I need to install a ROM from SP Tools.. please clarify more
KITKAT STOCK ROM V.1 http://pan.baidu.com/share/lin.....8;uk=1680007479
FIRST .. IF INSTALLING THIS ROM STOCK KITKAT V.1 (NEVER THE V.2 OF 24-7) BY SPTOOLS ..
AFTER INSTALLING RECOVERY FOR KITKAT ..
AND NOW YOU CAN FOLLOW THE STEPS OF INSTALLATION POSITIONS IN THE POST.1 4.4.2 AOSP
I need help please to turn on my phone again. Now the phone don't turn on or making a bootloop anymore. It just doesn't turn on or charge!!! How can I install ROM via Sp Tools without this BROM ERROR I get.. please help
INSTALL ADB DRIVERS FOR WINDOWS 7 AND MAKE YOU EXPLAIN THE ABOVE
Hello, when I boot stock ROM I have black screen. After loading rom (~20 sec) I click power button then I have normall screen and I can use stock android 4.4 normally.. but when I boot to recovery I have the same problem with black screen and I can't do it something. Where is the problem? How to solve that?
I’ve a problem with whatsapp notification. In some moments system doesn’t notify messages. Why?
from NEWTON: TRY DELETING"# Apaga la proximidad rapido despues de la llamada " OF build.prop
NEWTON: thank you very much, but I got the problem also with gallery and images (doesn't work gesture), not only during call.
Ideas? Re-Thanks!
nothing to do, also after deleting # string the problem persist.
thanks.