Jump to content

Most Liked Content

#862890 [GApps] 4.1.2-485486 JZO54K GApps Package 10/12

Posted by Formula84 on 01 August 2012 - 11:19 AM

Mod Type:: GApps

Difficulty:: Very Easy

Mod Base:: AOSP

Mod Status:: Stable

Apply In:: CWM Recovery

Requires Root:: Yes

Here is a package I personally put together for myself, figured others may want this. I also wanted to get the attention of ROM Devs so maybe they will incorporate these versions into their build if bundled or recommend these to be flashed with their ROMs .

I noticed all of the existing GApps packages floating around all used the leaked 4.1 GApps and not the updated ones from the official 4.1.1 Image from Google. So I compiled a new zip that has the exact file structure as the 7-26 Goo.im (CM Promoted) gapps package but used all files from the official 4.1.2 JZO54K release.

Archived original OP on 8/31 to post #3 -If anyone wants to read more on original ranting that made me create these packages in further detail.

There are two GApps pacakges available, use one or the other, both include all needed gapps and services that are required to run Google software....only one small difference - Camera and Gallery app.

Both Include: Calendar Sync, Bookmarks Sync, Face Detection, News & Weather, Google Backup/Restore, Contacts Sync, Sound Search, GoogleTTS, Google Now w/English Installed, Play Store, Talk, Voice Search

Pick one only, use the explanations of each below to determine which version is best for you. These should be compatible with any JB based rom.

gapps-jb-20121012-JZO54K-Formula84 | This version is for users that want to keep the Roms custom camera options (Power Shutter, ISO changes, etc.) only issue is that this has a trade off, you wil not be able to use Google Picture Sync.

gapps-addon-JZO54K-Picasa-Sync | This is an addon for users that want to use Google Picture Sync and get the experience Google intended.

Note: Some Factory Shipped GApps have not been inlcuded due to newer versions being available on the Play Store for download. Also available via Addon zips -See this post for explanation of addon zips or Click on the name/links to take you to installs for each (GMail, Youtube, Maps / street view, Google +, Music, etc.)

Recent Changelog:
10/12: See this post
9/29: See this post
9/19: Updated stand-alone wallet zip to 9/5/12 Version.
8/31: Updated to JRO03O build, Reorganized OP for a simpler explanation.
Full Changelog: See Post #3 for Details

*** LiquidJB-GApps folder is for Liquid ROM only, (Liquid Users See this Post for more info)
Primary - New 10/12 Files Available!
Goo.im Link -Donate to Goo.im at least once if you can
Secondary - Only 8/31 Files for now below
MediaFire Link to Folder
Google Drive Link to Folder
Box.net Link to Folder

Installation Tip:
I have only tested these with installing in the same recovery session as the Rom. Not sure if that matters or not, but I have been doing that since the Nexus S GApps Wallet issues back in the day. Thats how I would recommend this be installed.

Google Wallet Installation:
Only thing I can see people having issues with on Play Store may be Google Wallet. I know that when you search on PC not even signed in Wallet does not come up in results, its almost Like Google is Hiding it. So here is the link I used to install it properly, also had another Liquid user test in IRC successfully.
From you phone click this link, https://play.google....letnfcrel&hl=en, if asked which to open with use Play Store...You should be directed to the Wallet App and have the option to install.

Alternate Google Wallet Install:
I have made a flashable install for the latest 9/5/12 wallet since it seems to be a mixed bag of results using the link.

The link worked for me prior then after my phone got wiped and I setup from scratch I found the link did not work for me either.

So anyone that wants wallet check out the "Addon Pacakges" folder in the JZO54K Gapps folder from any of the links in the OP.

Edit: Oh and forgot to say if you found this useful don't forget to grow my internet-peter-meter by hitting "Like" - also some people respond to this topic so it doesn't get buried in the multitude of Rom threads

#303884 Android Open Kang Project - toro - build 25

Posted by roman on 18 December 2011 - 10:13 PM

Posted Image

Posted Image

Newest change logs are available at the AOKP site
Posted Image

  • Make sure you're on the latest CWM


  • wipe data/factory reset in recovery

  • flash ROM

  • flash Gapps

  • reboot
Posted Image
Find all builds and milestones at the AOKP site. If unsure hit the "Releases" tab and you'll find them ordered by latest release!

Posted Image
We spend countless of hours doing this for next to nothing. Posts, views, and donations encourage me, and everyone else who helps out.

Donate to me
Donate to Whitehawkx
Donate to Jonathan Grigg
Donate to Zaphod-Beeble
Donate to ProTekk

Donate to CyanogenMod

Every donation is cherished and loved.

If you'd like to help contribute by writing code, feel free to stop by IRC and talk to us!
Posted Image
Check out the ROM source on github. Open source, in the spirit of community kangage.

If you'd like to help with AOKP, please don't hesitate to contact me. I'd love to get as many developers in on this as possible!

Best way to help out or contact us is via IRC.

#768327 [ROM] JDX v15.2 - 09/05/2013 - [JB 4.3][AOSP+] - It's all about the butte...

Posted by jakeday on 29 June 2012 - 12:41 PM

4ndr01d presents


"Android the way it should be" for the VZW Galaxy Nexus [toro]


AOSP+ (always latest)
always based on latest AOSP
VZW binaries (always latest)
expanded desktop (with option to keep status bar)
long press back to kill app
skip tracks with volume buttons
custom lockscreen targets
quick reply for messaging
AVRCP 1.3 (music meta-data over bluetooth)
bluetooth MAP support (need to rework for bluedroid)
reboot menu (reboot, recovery, bootloader, safe mode)
group messaging with stock messaging app
emoji icons with stock messaging app
long press volume buttons to skip audio tracks

clear all recents menu button
improved 3G, 4G, and WiFi connections
rooted (with SuperSU)
optimized for performance
tweaked for speed
first rom separated from gapps (proper)
focused on stability
properly functioning Google services (location, now, etc)
proper booting
works with all recoveries
buttery smooth


changelog entries available here


Click here for more info (more info, additional download links, further support)

You will need both the ROM and GApps. This is the first build to separate them!

Gapps - Use my latest on the link above (or mirrored below).

Note: ALWAYS use the latest GApps!


ROM - http://4ndr01d.com/repos/toro/jdx/

Gapps - http://4ndr01d.com/repos/gapps/

Click here for Mirrors

1. wipe data (if coming from ANY other rom)
2. wipe cache
3. flash ROM
4. flash GApps
5. let phone sit for a few minutes once booted to settle (a lot is done of first boot)

Keep in mind that the first boot can take up to 10 minutes and may seem to hang on either the Google logo or the Boot Animation. Just give it time, it will boot.

Need quick support? You're best bet is on IRC. Connect to irc.freenode.net and join #4ndr01d for the best support.

Google - for Android!
You guys - for all your support and feedback!

Donations Appreciated!


#320079 [Kernel][jb43] [v8.3, FINAL] Leankernel: Minimalistic Kernel

Posted by imoseyon on 23 December 2011 - 07:12 PM

This is a minimalistic Galaxy Nexus kernel. My philosophy is to keep the kernel as lean and stable as possible, at the same time to keep the kernel as modern and close to latest mainstream linux as possible. You will see that my kernels will lack some of the bells and whistles from other kernels.

  • Terminal Emulator not finding my scripts? Read this post.
  • Patched to latest in Linux 3.0.x branch.
  • All unnecessary kernel components removed to make kernel lean and fast!
  • OC to 1.65ghz. Boot speed is maxed at 1.2ghz within kernel (in addition to ramdisk) for stability.
  • User voltage control
  • InteractiveX V2 (screen-off hotplug of cpu1) added. Select it using setcpu if you want to use it.
  • Ramdisk tweaks (sysctl, vm, filesystem speed, etc.)
  • SWAP & zram (next generation compcache) support. Run "zram enable" in terminal.
  • init.d support in ramdisk.
  • lk.conf for basic kernel configuration.
  • HotplugX governor (Hotplug optimized and modified for screen-off suspend).
  • wakelock tweaks for wlan and lte modem
  • lkflash - script to flash latest versions of leanKernel from Terminal (type "su" without quotes, hit enter, then type "lkflash" without quotes and then hit enter)
  • checkv - voltage checking script (for custom undervolting) - detailed at bottom of this post.
  • checkt - script that displays 1) your current temp, 2) # of times you were throttled due to temp "recently", 3) CPU trim type, and 4) CPU silicon type, etc. (sample output)
  • Fast USB charge (by chad0982) and "ffc" toggle script by me. (Open terminal, and type "ffc" without quotes then enter)
  • ColorControl from both CM9 and Ezekeel (compatible with all ROMs). Helpful posts: 1and 2.
  • TempControl - sysfs interface to control the CPU temp threshold. Read these two posts: 1 and 2.
  • Variable GPU OC - sysfs interface to select GPU max speed between 307MHz (stock), 384MHz and 512Mhz. The changes take effect immediately. Check FAQ for more info and how to use it.
  • Custom SR Tuning - override kernel default minimum voltage for SR calibration. More info here and here. V2
  • SoundControl
  • Gamma Control
  • ROW scheduler v4

Uh.... flash the zip in clockworkmod.



Thanks to forum member maddler for providing file hosting: http://www.host4droid.com/

Donate to your favorite charity, or donate to me.

#761589 [ROM] ViciousMIUI-V4.1-JB TORO-2.10.26 (Android 4.1.2) 10/26/2012 - 10:45PM

Posted by DroidVicious on 27 June 2012 - 10:21 PM

Vicious Presents

****ViciousMIUI Android 4.1.2****

What's Working:
Data (Both 3G and 4G at boot with no tricks)
WiFi (Stronger WiFi signal now)
All market apps/gapps included in build no need to flash gapps
USB Storage
Internal Storage
Root/Superuser (Now built in and fixed open Superuser and update SU binary) (Thanks ChainFire)
Video Playback
Google Now
Google Talk

What doesn't work:
You tell me this bitch is golden so far!!!!

Installation Instructions:
Make a nandroid backup
Wipe data factory reset
Wipe cache partition
Wipe dalvik cache (Optional)
Flash JellyBean 4.1.2 to your Galaxy Nexus
Reboot and ENJOY JellyBean from me to you!!!!

Changelog: 10/26/2012
Fresh new build of ViciousMIUI Jelly Bean
MIUI has been updated to JZO54K Android version 4.1.2
Permissions Manager (MIUI Superuser App) working on first boot now (Thanks MIUI.us and rlasalle15 for the fix in "strings")
All builds are directly from MIUI China and deodexed and converted over to English and ported to the GNex by me..
Full changelog provided via video!! Press play and enjoy!!

MIUI Themes APP and Root Permissions APP working 100% on boot...

Please Read in Regards to Root Apps (THIS IS NOW FIXED)

This issue has been resolved you can now use the permissions manager app as you are normally suppose to with out any tricks right from the first boot.. Thanks hoppermi for the suggestion on what it was, and rlasalle15 for the fix in the MIUI.us version which is where I was able to decompile theirs to see what was done and it turned out to be just the change of 1 letter in "values/strings/" from a "d" to an "s" lolol... Hey that works for me!!! Thanks guys!!

Download Links:

If there are any issues while testing or using please contact me directly.. I was trying a few different things and I know there was some issues a few builds back with a couple apps and also last build had an issue with WiFi, that should all be fixed now.. Please again any issues contact me ASAP and I will fix it immediately!!! Thanks guys.............. Rock out with ya c**k out!!!! LOL


MD5SUM d225e26594c10a4e9b6b1e0d494595b5

MD5SUM bfbec00e736476f6987ad80b67235f40

MD5SUM 531cd3600fed38a880832334fafc08fb

MD5SUM bed416e3da66b0aae4a0a47ee714e39a

MD5SUM a3853d3a637dd08d69b50d90d5623ef9

MD5SUM d033eb2da91d39567cf0805b0b6b728e

MD5SUM 521d02693f0538e45790f727fddba72f

MD5SUM 92d30f0dace6e920cc08bc70c564890a

MD5SUM 72d4dfa9f977309db373f0029686b885

MD5SUM e8086565186ba42478483cf742e217d3

MD5SUM a58dd1758f93f96714c53ab9ea6ca603

MD5SUM ed48ae25d24928a16bdf114e3d7eb518



Credits to:
Google - AOSP
Xiaomi - MIUI

Donations are never mandatory and you shouldn't feel obligated to do so but if you do it is very much appreciated!!


Feel free to hit me on:

Twitter @Paullie_Vicious

GTalk & GMail - paullielaino@gmail.com


#305406 [KERNEL]GN-LTE[Hybrid-3.0.53]JB:Pre-UV,OC,TUN,CIFS,OTG,FIOPS(v024)[Nov-27]

Posted by faux123 on 19 December 2011 - 12:11 PM

Mod Type:: Kernel

Difficulty:: Very Easy

Mod Base:: AOSP

Mod Status:: Stable

Apply In:: CWM Recovery

Carrier:: Verizon

Optional:: Insecure Boot

Requires Root:: Yes

Optional:: Overclocked

Android Version:: 4.1.1 (JB)


NOTICE: This is COMPATIBLE with ALL Google Rooted Stock and Custom ROMs based on JellyBean (4.1x) and Ice Cream Sandwich (4.0.X)!

For frequency control use SystemTuner by 3C or SetCPU app by coolbho3k

Just a statement regarding kernel source: The Kernel Source is of course covered under GPL version 2. Free software does NOT mean no work or time was spent working on it. I have donated a large sum of my free time to hack this kernel. If you use my modified kernel source in parts or in its entirety, I kindly ask you mention its origins and to send me a github pull request or PM whenever you find bugs or think you can help improve my kernel hack further. This way the entire community will truly benefit from the spirit of open source. Thank you !

Hi RootzWiki members and fellow Samsung users:

This is my fourteenth kernel hack. I want to thank b16, and the entire RootzWiki Staff, and several others I cannot recall for inspiring me to venture into this unfamiliar territory for me.

What is a Kernel? The Kernel is the Foundation in which everything else builds upon in any software system.
[Car Analogy]: Kernel is like the Engine, Electrical system and the Transmission to a car. The Library, Framework and the Apps [AKA ROM] are the body frame and the rest of the Car.

Posted Image

THIS KERNEL is BASED ON Google Source Code. So it is COMPATIBLE WITH ALL AOSP ICS 4.0.1, 4.0.2 or 4.0.3 Builds.

DO NOT use any task killers, they DO NOT improve performance nor battery life. They INTERFERE with your phone's stability (more crashes) and App compatibilities (Forced Close).

Kernel Features:

So what type of kernel is this? Well, this kernel is based on Linux 3.0.y (says so from the version string) but it's really a hybrid between Linux 3.0.y and Linux 3.3+ due to many features introduced from Linux 3.3+ (for specific details on technologies, see 2nd post below!)
Features in Magenta are identical as the latest Linux 3.3-rc2

Memory Management subsystem:
-- feature SLQB allocator ( http://lwn.net/Articles/311502/ )
-- enabled memory control group (ultimate ONLY)
-- SLUB completed updated to Linux 3.3-rc2 (kernel 013+)
-- enabled KSM for CM9 Dalvik hack also completely updated to Linux 3.3-rc2 (kernel 013+)
-- vmalloc completely updated to Linux 3.3-rc2 (kernel 013+)
-- vmscan completely updated to Linux 3.3-rc2 (kernel 013+)
-- memcontrol completely updated to Linux 3.3-rc2 (kernel 013+)
-- memory compaction completely updated to Linux 3.3-rc2 (kernel 013+)
-- page writeback completely updated to Linux 3.3-rc2 (kernel 013b6+)
-- filemap completely updated to Linux 3.3-rc3 (kernel 013b8+)
-- swap/swapfile completely updated to Linux 3.3-rc3 (kernel 013b8+)
-- shmem completely updated to Linux 3.3-rc3 (kernel 013b8+)
-- memblock completely updated to Linux 3.3-rc3 (kernel 013b13+)
-- oomkill completely updated to Linux 3.3-rc3 (kernel 013b13+)

-- kernel init completely updated to Linux 3.3-rc3 (kernel 013b8+)

Core Kernel:
*** RCU:
-- completely updated to latest preemptive tree RCU to Linux 3.3-rc2 ( http://en.wikipedia....ead-copy-update )
*** Scheduler:
-- back ported select Linux 3.3+ cgroup (cpu control groups), threadgroup optimizations
-- cherry picked select NOHz optimizations from Linux 3.3+ ( http://www.phoronix....m=651&num=1 )
-- multi-threaded device initialization
-- cherry picked the new lockless list support from Linux 3.3+ ( http://lwn.net/Articles/423366/ )

Power Management:
-- cherry picked select PM optimizations from Linux 3.2+
-- cherry picked select CPUIDLE optimizations from Linux 3.3+
-- Added Two-Phase Power Savings to OnDemand Governor
-- Added screen off hotplug capability to Interactive (default), OnDemand and Conservative governors

File System:
-- DOS VFAT (read/write), NTFS (read/write), CDROM/UDF FS, CIFS+UTF-8 (windows share) all built-in
-- Filesystem writeback completely updated to Linux 3.3-rc2 (kernel 013b6+)
-- Asynchronous I/O completely updated to Linux 3.3-rc3 (kernel 013b6+)

Block I/O:
-- Deadline (default), No-op, FIOPS (back ported from Linux 3.3+), CFQ
-- Completely updated to Linux 3.3-RC3 (kernel 013b13+)
-- FIOPS version 2 (kernel 013+)

Kernel Features:
-- CleanCache Enabled ( http://lwn.net/Articles/386090/ ) (ultimate ONLY)
-- FrontSwap Enabled and updated to latest revisions slated for Linux 3.3+ (ultimate ONLY)

Device Drivers:
-- USB OTG (USB On-the-Go, aka USB Host-like support allows for external USB sticks, Keyboard/Mice)
-- DeviceMapper Cache capability ( http://sourceware.org/dm/ )
-- updated ZRAM / ZCache to latest Linux 3.3+ (compressed RAM devices) (ultimate ONLY)
-- Added Google's Snappy Compression support (alternative to LZO compression written by Google) (ultimate ONLY)
-- Patched OMAP4 Real-Time Clock with latest updates
-- Patched TWL6040 Codec with latest updates and optimization
-- ARM Berkeley Network Packet Filter Just-in-Time (JIT) compiler support ( http://en.wikipedia....y_Packet_Filter )
-- Added CM9 / Supercurio Color Gamma Hack (kernel 013b13+)

Library Support:
-- Optimized CRC32 and CRC32c with Sliced by 8 algorithm (used by TCP/IP and File Systems)
-- Optimized memcpy and string libraries (used by many things)
-- Updated IDR library to Linux 3.3-rc2 (kernel 013+)
-- more selective cherry picks from Linux 3.3-rc3 (kernel 013b8+)

ARM / OMAP architecture drivers:
-- Patched ARM VFP with latest updates (floating point optimization)
-- Patched ARM hotplug with latest updates (turning on/off CPUs)
-- Patched OMAP4 SmartReflex with latest updates (OMAP4xxx Hardware assisted Dynamic Voltage Scaler)
-- Patched ARM cache code with latest updates (L1/L2 Cache controls)
-- Asynchronous SMP initialization
-- CPU Overclocking to max 1.35GHz (with additional freq @ 1.06GHz, 810MHz and 525MHz)
-- GPU Overclocking to 384 MHz from 307 MHz (ultimate ONLY)

Kernel Tweaks:

Force USB (fast) charge profile:
echo 1 > /sys/kernel/fast_charge/force_fast_charge (enable)
echo 0 > /sys/kernel/fast_charge/force_fast_charge (disable)

Gamma Adjustments: (default 60 for all three)
echo xx /sys/class/misc/samoled_color/red_v1_offset
echo xx /sys/class/misc/samoled_color/green_v1_offset
echo xx /sys/class/misc/samoled_color/blue_v1_offset

Color Multiplier Adjustments:
echo xx /sys/class/misc/samoled_color/red_multiplier
echo xx /sys/class/misc/samoled_color/green_multiplier
echo xx /sys/class/misc/samoled_color/blue_multiplier

Original Color Multiplier values for reference just in case of accidents ;)
(use any file manager and view those files as text)

Installation Instructions:

*** JELLYBEAN 4.2.0 System Image ***
[ CFS ] (Mainline Edition - should work with ALL phones)
The File == Tuna JellyBean kernel == (GPU @ 384 MHz)

[ CFS ] (Mainline SmartReflex Edition - should work with ALL phones)
The File == Tuna JellyBean kernel == (GPU @ 384 MHz)

[ CFS ] (Ultimate Edition - should work with ALL phones but at a higher battery cost!)
The File == Tuna JellyBean kernel == (User UV Control, Enabled GPU Overclock to 512 MHz)

[ CFS ] (Ultimate SmartReflex Edition - should work with ALL phones but may require BootLoop Calibrations!)
The File == Tuna Jelly Bean kernel == (Enabled SmartReflex 1.5, Enabled GPU Overclock to 512 MHz)

*** JELLYBEAN 4.1.0 System Image ***
[ CFS ] (Mainline Edition - should work with ALL phones)
The File == Tuna JellyBean kernel == (GPU @ 384 MHz)

[ CFS ] (Mainline SmartReflex Edition - should work with ALL phones)
The File == Tuna JellyBean kernel == (GPU @ 384 MHz)

[ CFS ] (Ultimate Edition - should work with ALL phones but at a higher battery cost!)
The File == Tuna JellyBean kernel == (User UV Control, Enabled GPU Overclock to 512 MHz)

[ CFS ] (Ultimate SmartReflex Edition - should work with ALL phones but may require BootLoop Calibrations!)
The File == Tuna Jelly Bean kernel == (Enabled SmartReflex 1.5, Enabled GPU Overclock to 512 MHz)

*** ICE CREAM SANDWICH 4.0.3/4 System Image ***
[ CFS ] (Mainline Edition - should work with ALL phones! GPU Max Clock @307MHz)
The File == Tuna ICS kernel ==

[ CFS ] (Ultimate Edition - should work with ALL phones but at a higher battery cost!)
The File == Tuna ICS kernel == (Enabled Memory resource control, Enabled GPU Overclock to 384 MHz)

[ CFS ] (Ultimate SmartReflex Edition - should work with ALL phones but may require BootLoop Calibrations!)
The File == Tuna ICS kernel == (Enabled SmartReflex 1.5, Enabled Memory resource control, Enabled GPU Overclock to 384 MHz)

Here's a step by step instruction to install this kernel:

1. download the above file (via phone directly or to a PC)
2. copy the downloaded zip file to /sdcard/download/
3. Open ROM Manager and select "Reboot into Recovery" and select "OK"
4. Once in recovery, select "wipe cache partition", select "Yes", then select "advanced", then select "Wipe Dalvik Cache", then select "Yes" again. Once finished, click the back button to go back to the main recovery menu. On that menu, select "Install Zip From SDCad", then select "Choose zip from SDCard", then go to /sdcard/download and select the downloaded zip file and let it run its script.
5. Once the script is done, select "reboot system now"

Note: After FLASHING, the first reboot may take longer than usual, please be patient... After the first reboot, it may lag during initial load (let everything finish loading). Once everything is loaded and phone is ready for use, reboot the phone a 2nd time and the lag will be gone and everything should be silky smooth...

[ Advanced Users: ]

[ Optional: ]

If you encountered any funny / weird / strange issues coming from other than 100% pure stock ROMs or my kernels, the following "Reset Kernel" will restore the kernel to its Original Stock Settings.
After applying the reset kernel, then load my latest kernel again.

*** ICE CREAM SANDWICH 4.0.1 System Image ***
Upgrade to 4.0.2 image from Google (http://code.google.c...ages.html#yakju)

*** ICE CREAM SANDWICH 4.0.2 System Image *** (NOTE: Kernel 013 is the FINAL UPDATE for ICS 4.0.2)
Upgrade to 4.0.4 image from Google (http://code.google.c...ages.html#yakju)



*** ICS 4.0.2 -- RESET KERNEL ***

ICS 4.0.2 Reset Kernel

*** ICS 4.0.3 -- RESET KERNEL ***

ICS 4.0.3 Reset Kernel

*** ICS 4.0.4 -- RESET KERNEL ***

ICS 4.0.4 Reset Kernel

*** CM9 4.0.4 -- RESET KERNEL ***


[ For Kernel Devlopers ONLY: ]


Version 021 is OUT! With optional SmartReflex automatic UV!!!

Please don't hesitate to talk among yourselves and help each other out... The RootzWiki community is what inspired me to hack kernels for everyone since everyone here is nice and helpful to each other... Keep helping each other.... Famous proverb: It's better to give than to receive...




version 0.x.x -- more to come...


See Post below...

Standard Disclaimer: Not responsible for bricking your phone, voiding your warranty, or any other pain or suffering you may feel as result of using this kernel!!!

[b][b]My github Complying with GPL and RW rulez Posted Image

Follow me on Posted Image:

If you find this Kernel useful, feel free to hit the [Thanks] button below


#353859 [Recovery] Touch Based ClockworkMod Recovery

Posted by unstableapps on 04 January 2012 - 02:59 PM

Mod Type:: Recovery

Difficulty:: Moderate

Mod Status:: Stable

Apply In:: Fastboot

Carrier:: Verizon

Optional:: Custom Settings

Requires Root:: Yes

Optional:: Includes Recovery

A test version of a Touch Enabled ClockworkMod Recovery for the Nexus One is now available. Please note this is considered an beta build, so be kind. You can use both the hardware keys and gestures in this release.

Download CWMR Touch Installer from the Market

For LTE/CMDA Galaxy Nexus (toro):

For GSM Galaxy Nexus (maguro):

People involved in this little project:
Me - Donate
+Chris Ennis - Original concept and graphics as well as a few code tweaks
+Koushik Dutta - Well, CWM is kinda his baby. (This isn't his fault...don't bug him if something in it doesn't work right
+Drew Suarez - Helping with new maintenance and porting to more devices/customizations.


Youtube Link

To flash...

adb reboot bootloader
fastboot flash recovery whatever-the-file-name-is.img



Posted by jdkoreclipse on 27 June 2012 - 07:33 PM

Credit: Pete, Project FNV, koush, Mitch (optimal gps), chainfire, pawitp, nebcat

From the ashes of VanirBean comes a new AOSP experience. Welcome to NexusBean!

rooted with SuperSU
STOCK Kernel
98vanir Initd tweaks
build.prop tweaks
FastGlow softkeys
Menu button set to persistent
7 screen "smooth" launcher (credit to jdk and nebkat)
Max Volume raised (credit jdk and codeworkx)
All languages besides english removed
Stripped of unnecessary files
Mitch's optimal GPS.conf
Pawitp's Scrolling Cache optimization
Centered Lockscreen
Everything is fully functional
Other Various mods

Known Issues:
Market restore is hosed



v1: Initial release

DOWNLOAD ROM: http://goo.gl/0o9oJ
DOWNLOAD GAPPS: http://goo.gl/UG3Kk

Rom Mirror: http://buildbot.jdko...dk_v1_final.zip
Gapps Mirror: http://goo.gl/31fxw

Our IRC channel is #jdkoreclipse on freenode. Go there for the latest and greatest releases

Always accepted, never expected! Donation links:
Jdkoreclipse: http://jdkoreclipse.net/donate.html

#66896 [DEV_THREAD]DroidX CM7 with Gingerbread Kernel

Posted by RevNumbers on 20 August 2011 - 02:31 PM

For updated info and links on this rom, please go here http://rootzwiki.com...mbers-cm4dx-gb/

since cvpcs got 2nd init playing nice with the leaked gingerbread kernel, I started working on getting the libs and what-not straightened out.

You Must Be On the Gingerbread Kernel to Use

Currently here are the bugs include:

DSP Manager FCs
Camera freeze on zoom
(turn on zoom with volume keys, then use the volume up down to zoom)

Until I get my personal life straightened out, only builds with notable changes will be posted here.
You can always find the latest builds in ROM Toolbox available on the market :)
until they update the toolbox to work correctly with the latest versions of CWR, you can download the rom in the toolbox then manually install the zip found in /sdcard/romtoolbox/downloads/RevNumbers/

links to the builds:

MD5: 7ce6ab6fe373d4b0551a1144d819dfa5
720p Video record/playback now working (thanks DXC)
looks like on screen zoom is working again as well

MD5: c4f6a4e2de349ddf21df7d72ee906274

MD5: eab263f94224e867a61bdf46e7b6bcba

MD5: 7c4aaa7b4393cf856959f49b9a29ed56
(Includes MIUI Style Battery Bar)
(make sure to wipe CM Settings app data via app management in settings)

MD5: 1a03d8de90334123495f52a572b6a330

MD5: 5f43a9e87a3d97aa2c65d9188976653b

MD5: f4cc1ea0ae5c7556530ed2a01a27ad6c

correct fix for camera orientation (Thanks JCalvin!)
MD5: 4b8af051e9c58790c9647a9014ee5847

resolves camcorder freeze
fixes corporate email issues[/I]
MD5: c9a92c7a55eca77b6d53bf5e7dbe2f27

MD5: 6f9bfd5d4373d613df823f20bdb506ca
(Double plug in for USB should be fixed in this build)

MD5: 776e87bc927accf7b3e014af7b4f0d4d

The 1% battery increment "hack" doesn't work, so we've got to settle for 10% increments until we figure out what's up with charge_counter reporting random (ie -14768524) things.

New github for GB modifications


#404559 [ROM][AOSP]LiquidSmooth-ICS-v1.5mr1 ROM[07/10/2012]

Posted by liquid0624 on 20 January 2012 - 11:30 AM

Posted Image

Version 1.5mr1

Rom Features

  • Extremely responsive, slim, resource friendly UI
  • Backup/Restore Liquid Control configurations so you can reflash and retain your personal UI/ROM customizations (note this does not apply to any of the settings under the goodies section)
  • Liquid Control, allows for manipulation, customization, and optimization of nearly every area of this ROM.
  • Full screen mode (upper left of power menu birdie!)
  • More Incremental Navbar Heights to tweak the size just to your liking!
  • Now Includes 5 Lockscreen options
  • Customizable Navbar background color, button glow speed, colorkeys.
  • Center clock mod/customizable Color
  • Customizable battery icons
  • PropModder, a new convient way to edit your build.prop with the flick of a finger!
  • Quad/Octo Lockscreen with native/(now customizable) ICS icons
  • Native Overclocking/Undervolting Perfromance Utility
  • Native Gamma/Color Control
  • Uniform ICS theme throughout the rom...
  • And Much much more!


It is with great pleasure that we are here to announce the arrival of Liquid - Ice Cream Sandwhich (toro) V 1.5mr1. V1.5mr1 is without a doubt a Milestone release for us. It brings to the table unmatched customization & user- control, while providing excellent battery life, rock strength stability, & speed only a Liquid Smooth Rom could deliver. It truly marks a step towards the goal of our project *to bring slim & flawless firmware to the toro / maguro & to get the utmost out of your "phone!" A very big thank you to our beta testers & IRC channel community members / Liquid Smooth family, as well as all of you here at Rootzwiki! The entire Team is stoked about this release & we are certain that you'll love it, to! Please, enjoy! Also, stay tuned, as 1.X is in the works as I type...

Also, if you guys have a concern that we cannot adress here in the Rootzwiki thread, or youd like to contribute a great new idea for improving our project, we welcome you to join us @ IRC.FREENODE.NET; #LIQUIDS.

If you want video cam effects to work YOU MUST FLASH THE EXTRAS. Please do not report FC's about it until you flash the extras. If you want to use my verizon just download NFL mobile first and login over 3g/4g with their login client.

With that said,

Please note that this changelog was revamped by amp, hope you folks dig it

Click Here for all of the changes from our beta releases!










As usual there are thousands of other changes made, take a look at our commit history.

HUGE thanks to ejlax and liquid irc crew/donators for the dev phone and believing in team liquid and this project!




Liquid ICS v1.5mr1 (GalaxyNexus CDMA)


Size: 91.86 MB

MD5: 627e89ee9bfebe3dd1c86ee13b31033a




Mirror - v1.5mr1



Liquid ICS Extras (GalaxyNexus Both)

Size: 31.21 MB

MD5: ef032ab20c8ec9b0d692d3fad49d9859




watch our video changelog:


#280261 AOKP | maguro | JB 4.2 preview

Posted by roman on 08 December 2011 - 07:12 PM

Posted Image

Posted Image
  • wipe data/factory reset in recovery
  • flash ROM
  • flash Gapps
  • reboot
Posted Image

build dec 4, 2012 - 3a3d475826e874672520d51976b6ca94
gapps - November 30, 2012 - fda2660e94d9b9079b23e7b67ef012b0

These builds will be buggy. Do not expect a stable, bug-free AOKP experience on anything other than a milestone-labelled ROM.

Posted Image

Donate to Roman
Donate to Whitehawkx
Donate to Zaphod-Beeble
Donate to ProTekk
Donate to Sethyx
Donate to SteveSpear
Donate to MarcLandis
Donate to Sixstringsg
Donate to AdamtheCashew
Donate to Xoomdev
Donate to Birdman
Donate to Khas'Mek
Donate to Kwes1020
Donate to Nitroz
Donate to JustReboot

Donate to CyanogenMod

If you'd like to help contribute by writing code, submit to gerrit and feel free to stop by IRC and talk to us!
Posted Image
Check out the ROM source on github. We are open source, and always will be.

#1031981 [ROM][AOSP](8/9/14) Shiny ROM: OTA-Like, Stock Android [4.4.4] [KTU84P]

Posted by baldwinguy77 on 22 November 2012 - 06:33 PM

Shiny ROM: Android 4.4.4, KTU84P for VZW Galaxy Nexus (Toro)

Skip right to the downloads (if you dare ;))
Hello there RootzWiki community! I'll admit this is a pretty spontaneous post; I've been building ROMs from the Android Open Source (Project) for awhile now, but I've never "published" any of them. I myself own a Verizon Galaxy Nexus, so I've always built from AOSP to make sure I'm as up to date as possible. Well, that's a little background so let's get going with the overview of the ROM itself:

This ROM is Android KitKat 4.4.4, build KTU84P. The ROM is built directly from source, that is, the Android source code published by Google available for download to all of us developers. The reason I say the ROM is "OTA-like" is because I make VERY few modifications to it, aside from the things that it takes to get the ROM working. I'll go into detail about those things below, but basically I just want the ROM to make your phone feel stable and shiny and new as if it has just received a new OTA update. That being said, it's clear that the landscape of Nexus devices is changing as new ones are released. Therefore, the other primary goal of this ROM is to keep our Galaxy Nexus as close to the modern Nexus design as possible. This means that I will also add in features that will still be stock, but will also make our phones as close to a current Nexus as possible.

As for how I handle the forum side of things, I'm always open to comments, questions, suggestions, requests, etc. I know that most of those things will often be in the form of criticism, but it's okay, I think I can handle it :) That being said, I do also have a life and am a college student, so I may not get to come on here ALL the time. I will check back as frequently as possible, and I'm hoping that you guys will help each other out as much as possible! Keep it friendly! :) So now for the details...


  • Stock Android 4.4.4, build KTU84P
  • Source (AOSP) built kernel (boot.img)
  • Easily rootable (see information below)
  • G-Apps (GMail, Play Store, etc.) included in build along with Nexus apps
  • Stock browser replaced with Google Chrome
  • Shiny restart options - access them by holding down the power button and then long pressing on "Power Off"
  • All the crazy Google proprietary app stuff has been taken care off
  • Updated frequently
  • Everything works!

So what do I mean when I say "Everything works!"?
I'm sure by now you all know that when someone says that, it usually ends up not being true. This ROM is not an exception to that rule, but I can say that I've tested most of the things that would be expected to work in stock Android, such as...

  • WiFi Tethering (no subscription check)
  • Bluetooth streaming
  • Google account sign-in and auto-restore of apps and settings
  • Google Wallet
  • Location Services (pretty fast GPS lock in my area also)
  • Photosphere
  • Android beam
  • Photo editing with the new filters
  • Email
  • Exchange support
  • Like I said, the normal stuff (data, voice, hardware acceleration, etc.)
  • More things that aren't important enough to mention here - check out the changelog for a more comprehensive list

Possible Bugs
It's impossible for me to test for and notice EVERY single possible bug in the operating system, so as of right now I can't say that there are any, although I'm sure you will find some. If you do, report them here!

Other IMPORTANT Information
But wait, nothing in this post said anything about root!!!11!!1!1!!! That's right, my ROM does NOT have root built in! (I don't use any root apps, and it's important to the whole "OTA-like" theme). That being said, the ROM is easily rootable; I made sure of this because I know that many, many of you will use root for many useful purposes. If you want to root the ROM, it's as easy as installing Chainfire's new superuser control app/su with this ZIP file. More detailed information can be found in the "Installation Instructions" section. **NOTE** If you are rooted and upgrading to a new build, you should not have to reflash the rooting flashable ZIP because the ROM will keep root for you.

Now that the ROM has gotten to this stage, the update policy needs a bit of editing smile.gif Based on the stats I have access to from the website host and data that I collect myself, it seems like Shiny ROM is currently (as of May 27, 2014) stable for at least 80% of the users who have downloaded it. Based on this, and because the ROM is stock, Nexus-like, it doesn't really make sense to update the ROM as frequently as before. The ROM will still be updated as soon as possible after new versions of Android are released. In between Android versions, I will work on making things 100% stable, although that goal isn't always attainable with older devices and aging hardware support. If we decide to explore other paths for the ROM, you will see many more updates smile.gif If/when the time comes for me to stop updating Shiny ROM, I will let everyone know in a clear way.

This ROM will (most likely) work with any toro radios; however, I of course recommend using the most recent, Verizon-approved radios which are the FK01 and FK02 radios. My ZIP installation package for these radios can be downloaded here.

Once again, I'm assuming that this ROM will work with all tuna/toro bootloaders; BUT for optimal experience and performance, use the newest Google-approved bootloader, PRIMEMD04. My ZIP installation package for that bootloader can be downloaded here.

ClockworkMod Recovery
I personally recommend using ClockworkMod Recovery as it has always worked well for me with no quirks. Android 4.2 messed up a few aspects of recoveries because of its multi-user system. ClockworkMod Recovery has been updated to correct some of these issues, and I recommend updating to the most recent version, You can flash either the touch recovery or non-touch recovery image through fastboot OR you can download my flashable recovery update ZIP (touch/non-touch) and flash it in recovery. Check out the installation instructions for more details on this.

Some Other Not-so-important Information
Naming Conventions
All of my ROM ZIP files are automatically generated by my build computer. The file name for all builds up to and including the 11/10/13 build always begins with baldwinguy77_toro_aosp so you know that it's my build for toro. All builds after 11/10/13 begin with the prefix ShinyROM_toro_aosp. That prefix is always followed by the date in mmddyy format (e.g. 112212), a hyphen ("-"), and the time in 24-hour, hhmmss format (e.g. 153945). Finally, all builds end with the "signed" suffix - it just helps me know which packages have finished building and which have not. Hopefully this helps everyone to know which update is newest; I stay away from version numbers because I let Google do all of the version control.
In keeping with the spirit of open-source, all relevant Shiny ROM code can be viewed on Github. I'm not extremely experienced with Github, so bear with me as I learn! Thank you!

File Hosting
I've switched over from using Dev-host to a privately hosted site, graciously and generously given to me by RootzWiki user Goofball. Dev-host is still an amazing service, but it's much more convenient for me to use a privately hosted site, plus I get my own suburl and FTP access! HUGE thanks to Goofball, please check out his RootzWiki profile here! The private hosting will definitely help me deliver a better experience to you guys as far as downloading goes. You can view all of my uploaded, public files here: http://shinyrom.goofball.org/

Also, if anyone ever wants to mirror for me, please feel free so long as you keep the file name and the file itself intact. As for everyone who downloads from a posted mirror: BE CAREFUL! Always use a virus scanner and be careful with what you are putting on your device!

Installation Instructions (VERY IMPORTANT - Note: You can flash all of these ZIPs in CWM or TWRP*)
*Android 4.4 KitKat builds must be installed using the latest version of your preferred recovery!
1. Download the latest version of the ROM from the download post. (Also download any other files you will need to install, such as Chainfire's SuperSU Root ZIP, the radios installation ZIP, the bootloader installation ZIP, etc.)
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. If you want to be 100% sure there are no problems, wipe data. If you are coming from another ROM or Android version, wipe data. If you do not wipe data and something goes wrong, repeat this process but wipe data - this step is not necessary if you are simply upgrading.
10. If you are updating your radios, flash FK01_FK02_Radios-signed.zip
11. If you are updating your bootloader, flash PRIMEMD04-signed.zip
12. Flash the ROM (ShinyROM_toro_aosp...signed.zip)
13. If you are rooting, flash Chainfire's SuperSU ZIP file - this step is not necessary if you were rooted on the previous build and are simply upgrading.
14. Reboot your phone, and enjoy!

**Note: If you are simply upgrading to a new version of the ROM and want to keep root, follow the exact instructions above, and do not format /system. It really is not necessary to format /system at any time (unless specifically noted), as the ROM installer has this function built in.

1. Download the latest version of the mod(s) you wish to install from the download post.
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. Install the mod(s) you downloaded in step 1.
10. Fix permissions (not really necessary)
11. Reboot and enjoy!
**Note: You can remove all mods you've installed by dirty flashing the latest version of the ROM.

ClockworkMod Recovery (Fastboot method - must have an unlocked bootloader and fastboot in your path)
1. Download either the CWM touch recovery image or non-touch recovery image to your computer and rename it to "recovery.img".
2. Power off your phone.
3. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
4. Plug your phone into your computer using the standard USB cable.
5. Open the command prompt/terminal and navigate to the folder where your "recovery.img" is saved.
6. Type "fastboot devices" to make sure your phone is recognized; a serial number should show up on the screen.
7. Type "fastboot flash recovery recovery.img" and wait for the process to complete (should be quick).
8. You're done! Use the volume keys to select "Recovery" and boot into your new recovery!

ClockworkMod Recovery (Flashable ZIP method - easier)
If you are updating your recovery before flashing a ROM, these steps should ALL be completed PRIOR to flashing the ROM.
1. Download either the touch recovery flashable ZIP or the non-touch recovery flashable ZIP.
2. Place the ZIP file downloaded in step 1 on your internal storage/sdcard.
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Choose "Install update from sdcard"
7. Select "Choose file from sdcard"
8. Find the flashable recovery ZIP file you downloaded and install it
9. Back up to the root menu of recovery
10. Select "advanced"
11. Select "reboot recovery"
12. The phone should boot up into your new recovery!

As with most ROMs, I only did a small part to get everything together. Also, a note that should be made here is that when I am using someone else's file, I ALWAYS host files on the shinyrom server to ensure that I don't put any unnecessary stress on their servers. Any file, however, still belongs to and is accredited to its original creator as listed below:
Willyjay - For providing us with lots of amazing and innovative mods for the ROM! Check out his RootzWiki profile here!
Inmanster - Another great modder who we are fortunate to have here in the thread. He works in collaboration with Willyjay and his mods for many things, but also does some of his own unique mods! Check them out in the download post and check out his RootzWiki profile!
Chainfire - For their SuperSU app and su binary, as well as the convenient ZIP update package, which was previously used and recommended. Check out their website, http://www.chainfire.eu/
Groupers - My new buddy on RootzWiki who helped me out with a GPS issue that popped up in 4.2. Check out his RootzWiki profile!
Google - Without their amazing staff and willingness to share the source code of their operating system, I wouldn't have been able to build this ROM! Of course, all of the Google apps are theirs, along with the Play Store and system apps. They really are the true owners of all of this.
Samsung - We all may have some mixed feelings about them, but in the end they gave us the amazing, hackable phone that is the Galaxy Nexus.
RootzWiki - Their extremely innovative and supportive community helps myself as well as hundreds of other developers and thousands of users to thrive, and exemplifies the heart and soul of Android.
Dev-Host - The file-sharing service with virtually no limits on sharing - kudos to them and their hard work. d-h.st
Koush and the ClockworkMod/ROM Manager Team - They make the best recovery that's been around for longest, and their constant updates allow us to keep making ROMs! Also, Koush's recently released open source Superuser control app is the best available and the one linked to in the thread. Thanks Koush! clockworkmod.com
Kevdliu - Huge thanks to this dev and their amazing quick settings mod! Please check out their thread here!
The CyanogenMod Team - For a working implementation of DSPManager on Android which can be ported to any AOSP-based ROM! Without them and Bigwavedave25, the DSP manager mod would not be available! Be sure to thank them and to check out the CyanogenMod website! Also, for their feature-filled version of the stock Messaging app which is available as a mod for my ROM!
bouchigo - a Rootzwiki user who has helped to make the CM10 Messaging app available as a mod for my ROM in conjunction with Willyjay for bringing it to my attention. Check out his Rootz profile and be sure to thank him!
Schoat333 - A Rootzwiki user who helped out Willyjay with the bubble styled MMS mods. The credit for the screenshots to go along with the mods goes to him! Check out his thread and his RW profile, and be sure to thank him!
Yarly - The most experienced RootzWiki admin I've ever had the pleasure of talking with, who taught me some new debugging tricks and answered some of my questions.
Razorloves - Another RootzWiki admin who helped me out with a few problems and answered a lot of my questions!
Tiny4579 - A kernel dev here on RootzWiki who also took the time to talk with me and answer a few of my questions. Be sure to check out his RootzWiki profile and his kernel thread for the GNex!

Thanks to everyone for their hard work and sharing that work with others!

Come on guys, it's a Galaxy Nexus, to what extent could it really get messed up? Nonetheless, in case someone flashes this then puts their phone in the microwave or something and tries to blame it on me, I am not directly responsible for anything that occurs, either negative or positive, from flashing this ROM to your phone. Despite that, I am posting in the spirit of the Android community, a community that I have embraced and belonged to for several years, and I would never try to hurt any of your innocent, beautiful phones. Also, none of the original source for Android belongs to me, nor do any of Google's apps. All preinstalled applications are property of Google, Inc. and I make no claim of ownership to them.



#576627 Optimal GPS settings for Galaxy Nexus

Posted by mitch0115 on 26 March 2012 - 05:30 PM

Since my first android which was a fascinate i I have obsessed with The gps . Finally I managed to get the correct setting but it was time for an upgrade ..Out of the box I was very disappointed with the how long it took to get a GPS lock on my GN ..So after doing my homework and and trying out a few different apps and settings I Finally have it down to a science where I get almost and instant lock !. There is a handy little free app called "GPScompassMap" that you can get at the market . It is an accurate app that tells you how many satellites you are locked into . Before you change your Gps settings do a test and see how many satellites you are locked into .. If your not getting between 8/8 and 11/11 then this is for you !Of course make a backup .
The only settings that will be effected are your GPS settings .

Please click "Like" just so I can see how many people these settings are working for.
I am not sure what that "Vote" button is for but it wont hurt to click on the "Vote" button too ;)

By the way you will never have to purchase another GPS app again ;). I am not asking for donations ..Just click like or make a comment ..

For some reason for the most part "angy GPS" is not opening up for a lot of people .This app is not a necessity just a tool . you do not need any apps for this configuration to work . By the way people are reporting that this is working for everyone not just CDMA .. Once again make a backup and enjoy your tweaked out GPS settings !
Thanks ,


Here is the flashable zip file ! UPDATED ! AND YES IT WORKS ON JELLY BEAN 4.1 !

Attached Files


#313926 [Radios][VZW] All Radios in Flashable Zip [updated 28 Mar 2013]

Posted by razorloves on 21 December 2011 - 08:09 PM

Each of these zip packages contain an LTE and CDMA radio for the Verizon Galaxy Nexus.

They can be flashed in clockworkmod or TWRP recovery. No wiping or mounting necessary.

You can also flash radios using fastboot (no root or clockworkmod recovery required using the fastboot method). The files for the fastboot method are provided by here

Each have been tested and work on any rom.

NOTE: I STRONGLY suggest you verify the MD5 of your download to ensure file is complete before flashing. You can use Root Explorer or AFV on your phone to verify the MD5.

4.0.1 (ITL41D) radio package (from official 4.0.1 factory image provided by google)
CDMA Radio Version - EK01
LTE Radio Version - EK02
MD5: 3302017119dd24eaf99b2a6540ea3697

4.0.2 (ICL53F) radio package (from official 4.0.2 factory image provided by google)
CDMA Radio Version - EK05
LTE Radio Version - EK02
MD5: a12743e6d3b80734831f69502bdae29b

4.0.3 (IML77?) radio package (thanks to DroidHckr for this leak)
CDMA Radio Version - EK06
LTE Radio Version - EK04
MD5: c07f43102346b7e88ac30fe981dbbf2b

4.0.4 (IMM30B) radio package (from unofficial leaked 4.0.4 OTA rom update)
CDMA Radio Version - FA02
LTE Radio Version- FA02
MD5: bd63961006aa65e88100017bab2c7fbb

4.0.4 (IMM76K) radio package (from official 4.0.4 factory image provided by google)
CDMA Radio Version - FC04
LTE Radio Version- FC05
MD5: 498a0596e23a155e80676dbbd6ac426f

4.1.1 (JRO03O) radio package (from official 4.1.1 factory image provided by google)
CDMA Radio Version - FF02
LTE Radio Version- FG02
MD5: 089e215d0500261736549c0bb75f293c

4.2.2 (JDQ39) radio package (from official 4.2.2 factory image provided by google)
CDMA Radio Version - FK01
LTE Radio Version- FK02
MD5: b09b548d6f3255d6884f00f93aabbe5e

#381488 [ROM] BlackICE toro Kangorade 40.5 final fairwell to BlackICE (7-8)

Posted by travp624 on 13 January 2012 - 08:27 AM

Mod Type:: ROM

Difficulty:: Easy

Mod Base:: AOSP

Mod Status:: Stable

Apply In:: CWM Recovery

Carrier:: Verizon

Optional:: Custom Settings

Requires Root:: Yes

Optional:: Themed

Android Version:: 4.0.4 (ICS)

Source:: https://github.com/t...vendor_BlackICE

Posted Image

Posted Image

  • Fully built from AOKP source (source)(website and donate to aokp/teamkang)
  • Added Cyanogenmods FileManager! (CM)
  • Added DSPManager (CM)
  • Replaced Mms apk with hybrid CM9 combined with AOKP (me)
  • Custom DroidTh3ory "Gofaster" Butter (DroidTh3ory)
  • Custom MasturModsSettings Built-in (Mastur Mynd)
  • Custom Dark Ass theme (Me)
  • Imported handle_compcache latest from CM9 (CM)
  • Removed the Japaneses IME stuff (Me)
  • Removed status bar notification icons dimming effect (me)
  • Custom BlackICE boot animation (Kwesley1020)
  • All Inverted Gapps Gmail, Gtalk, etc. (Me)
  • Custom Toggles (AOKP)I just restored icon on/off state and other minor tweaks!
  • Theme Chooser (all credit to cyanogenmod)

Posted Image

Rom Downloads and Gapps can be found herePosted Image

Changelogs are now here

Posted Image
I will always recommend a data wipe and very important make a nandroid always!!
If you choose not to use my Gapps or follow instructions then you will need to ask yourself why isn't this or that working right!

1. Make sure your using latest cwm

2. These must be followed exactly

2. Download all 3 and place on phone

3. I recommend wiping data/factory reset (especially if on another rom)

4. Flash Rom

5. Flash stock gapps zip

6. Reboot go thru setup sign in to google account!

7. Get thru setup. (If you wanna let market restore your apps wait but try not to open market LOL)

7a. If you opened market before rebooting go into settings>apps>all apps and uninstall market updates!

8. Reboot back into cwr and flash Black_ICE-gapps zip

****Only for those who are updating from previous version of rom****

1. Make a back up (always a good idea)

2. Flash rom update.

3. Flash BlackICE_gapps*****.zip.

4. Reboot

This method works for me all the time only when testing and updating.

Posted Image
  • The entire team at teamkang without them the gnex plus many more devices wouldn't be so buttery smooth!
  • Xoomdev who without we wouldn't have most of the device tree we have to work with.
  • Zaphod-Beeblebrox for lots of general help!
  • The entire team at cyangenmod awesome source
  • Mastur Mynd for being awesome and for asking me to join mastur mods
  • Team gummy and liquid and all the others that open up there source edits for us all.
  • DroidTh3ory for his decision to help somewhat!
  • Google of course
  • Everyone in the community who helps in the spirit of open source
  • My Testers for helping out!
  • And anyone I forgot to mention or include
  • Also If I have used or borrowed from you please ask and I will definitely give full credit!
Usual disclaimer I nor anyone included with this project is responsible for what you do with your phone!

#200455 [ROM] CM9 / LiquidSmooth / AOKP / Random ICS

Posted by twistedumbrella on 29 October 2011 - 11:12 AM

This build won't have a name. It is not based on any one work alone.

The required credits will be listed at the bottom, but this is taking everything what everyone has put into numerous builds that mostly work to make a build that fully works.

* 12/06/2012 10:15PM EST *

Current Build Changes:
- Update camera hal parameters
- Restore kernel, custom in extras
- Restore Playground board config
- Fix compatibility mode logic
- Test legacy OMX board flags
- Support disable external cache

* Extras, Error Reporting, Etc *

Next Build Plans:

Extras Installation Options:
- S-Voice Application
- Samsung TTS Engine
(Not recommended)
- Jellybean 4.2 Camera
- Jellybean 4.2 Keyboard
- (On/Off)line Google Now
- Pre-Approved MovieBox
(Free on this build ONLY)
- No wipe fix CM7 -> CM9
- Remove Replaced Apps

Extras Pack Changes:
- Splash screen for better looks
- Better handling of compatibility
- Modification for ROM updates
(Reset radios without data wipe)
- Fixed selections display in popup
- Better preliminary disclaimer info
- Fix MovieBox pre-approval tiles
- Loading images during rendering
- Progress status output percents
- Fix corruption from faulty upload
- Remove MovieBox Application
(Still offered as part of this app)

Known Long-term Issues:
- Camcorder does not record video
- Netflix / streaming is only sound
- Some feeds become blanked out

Pre-Project Changelog:
- Updated All Apps to Latest
- Hopefully a netflix patch for future releases
- Full Ext 4 Support
- MMS Now Works
- Torch Is Fixed
- RIL/System Files Heavily Modified
- 1x/3G/4G Should Show correctly
- Updated/Tweaked the Menu Settings
- Now is REL, Fixes Google Music, etc

Liquid0624 (Working Telephony/Data/SMS/MMS)
[SP]JESTER (1x Data)
CyanogenMod (Build base and modifications)
AOKP (Extended options and modifications)
Aeroevan (Numerous updates and fixes)


#693732 This is why your Verizon Nexus signal "sucks"

Posted by yarly on 19 May 2012 - 02:44 PM

Originally posted here: http://rootzwiki.com..._30#entry692912

I will summarize why your signal "sucks" compared to other phones. This all based on facts--not guesses, speculation, or tests that depend on factors one cannot control. I am also mainly talking about how LTE on the Nexus mainly works and not 3G unless denoted.

First, just to be clear. If you have issues like dropped signal, static during calls, dropped calls or lots of time without a signal, this is not in reference to that. If you have those problems, your device is defective and I would seek out filing a warranty claim with Verizon for it. You unfortunately got the "luck of the draw" and pulled a lemon. People have reported those issues and swapping out for a new Nexus has helped them.

However...if that is not the case (or you just would like to read for the sake of information), read on :)

ALL other LTE phones (excluding the Nexus) are reporting the RSSI of the cdma 1x signal in android 2.3, NOT the LTE signal. Android 2.3 was not capable of properly reporting the LTE signal and support was added for it in ICS. The Nexus also uses RSRP to determine your signal. RSRP has a huge difference to RSSI (for example):

RSSI = -79 dBm, RSRP = -93 dBm

This is why a Razr or Rezound will show -79 dBm in the same spot a GNex will display -93 dBm. Go find someone with an ICS leak of one of those and check their signal next to a Nexus. Unless the OEMs kept doing what they were doing before (which sadly they might), they should show the signal to be nearly the same.

Also, the higher your ASU under settings the better. ASU or "Arbitrary Strength Unit" is an integer value proportional to the Reference Signal Received Power (RSRP) measured by the mobile phone. Basically the higher the number for ASU, the less interference you have between you and the towers. It varies by your current type of connection, but ASU a number in the range of 0 to 99 (99 means you basically have no signal [unknown] and closer to 0 means it's also bad).

Your ASU on LTE is basically your current signal + 140. So if you have a signal of -93, then your LTE based ASU is (-93 + 140 = 47). See picture below for example:

Posted Image

Technically, it'll never be 98 as it hits a ceiling of 97 if you were somehow able to get a signal of -43db (-43 + 140 = 97). If your signal is somehow worse than -140, then it will report zero, but that should also not be possible.

It's a little more complicated for CDMA ASU. On CDMA, it's some power of 2 up to 16 (1, 2, 4, 8, 16) with 16 being the best or 99 if it's unknown. It's also measured by not only your signal in db, but also by your your signal to noise ratio which is not shown to you.

↑↑↑ Source for that was SignalStrength.java under getLteAsuLevel() ↑↑↑

So, unless your data connection is dropping out constantly, it's just fine and not as bad as you think.

If you're wondering how the signal bars for the Nexus are computed here's some info on that. The bars are already just a relative measurement based on what we think is good or bad as we already knew. However, Google did adjust them to make them to look like you have a "better" signal in 4.0.4 though for LTE. If you mean adjust them back to 4.0.3 and before levels, that's also possible by undoing what they changed SignalStrength.java. Would be a small change that could be done by compiling the source or by a smali edit in framework.jar.


Shows how they were before/after 4.0.4. Mostly increased everyone's LTE bars in most cases by 1 bar.

They also use the signal to noise ratio to determine which one gets priority for showing the bars now. They take the one that looks better and use that for mapping to the bars as shown here: https://github.com/a...5a9b6889851d887

Signal To Noise ratio is just a computed number based on how much interference is in your connection. It's not exactly the best measure for data as it's just measuring interference.

Before you start comparing your signal to other phones not on ICS, at least read this and look at this link to the Android source for ICS:

Use LTE SNR and RSRP to set signal level bar.
The LTE signal strength level is the smaller one
between lte rsrp level and lte snr level if both
rsrp and snr are valid.

↑↑↑ Android ICS source even says it uses the RSRP for LTE. ↑↑↑

↓↓↓ THEN....if you look down at some of the code you see things like ↓↓↓:

	 * Get the CDMA RSSI value in dBm
	public int getCdmaDbm() {
		return this.mCdmaDbm;
	 * Get the EVDO RSSI value in dBm
	public int getEvdoDbm() {
		return this.mEvdoDbm;

↑↑ Which is what CDMA phones were using before ICS. ↑↑

If one is still in disbelief, then you can go back and look at the Android source for SignalStrength.java back in say like 2009/2010 and note that there is no mention of RSRP anywhere because it was not used yet (only mentions of RSSI are there).

Still don't believe me? Well go compile the source and change the following method in SignalStrength.java to return the cdma signal strength instead:

* Get LTE as dBm
* @hide
public int getLteDbm()
// return cdma signal being used instead (i.e. if evdo is -120db it's not being used, so look for which is closer to zero)
	 return this.mCdmaDbm > this.mEvdoDbm ? this.mCdmaDbm : this.mEvdoDbm;
// commented out below
// return mLteRsrp;

And then watch your signal get "better."

It is upsetting my wife's Charge gets a much better signal than my Nexus sitting right next to it knowing it has the same radios.

↑ It's not really "better." It's (the Charge) just measuring something different (the RSSI of the 3g connection) to obtain the signal which isn't even related to LTE. If you changed the above, the signal would probably be nearly the same. From my testing, my RSSI is nearly the same as what I got at my current location on my Thunderbolt (which everyone claims has amazingly better radios and Qualcomm chipset).



Reference signal received power (RSRP), is defined as the linear average over the power contributions in Watts of the resource elements that carry cell-specific reference signals within the considered measurement frequency bandwidth. Used to measure the signal of your LTE (GSM/4g) connection. In short, it's what's used to determine the best cell tower your LTE device can connect to at the given time. Anything below say -80db is considered pretty good and you're pretty close to a tower. -80db to -90db is average what you should expect most of the time. -90db or above and you're probably in an "extended network" area for LTE and getting close to a likely handoff. -105db and above you would be likely to see a handoff to 3G if your signal does not get better.

Throughput for your connection measured with LTE is estimated to decline between 30-50% if your signal goes from -75db to -90db for RSRP. Above -95db and your throughput dramatically drops. At around -108db and worse, your throughput for download drops to nearly 3G rates or worse. Note that this doesn't exactly represent how strong your signal is, just the potential of how efficiently it will send that data.

"But why can I have a super awesome RSRP signal and still my download/upload speeds are not that good (or why is it still sometimes good when RSRP is low)?"

Because it's only measuring the efficiency between you and the tower, not the rest of the network or the end source (the website). There are many network hops along the way to the destination and some may also handle connections inefficiently. The more hops, the slower the connection generally is.

However, it does also represent the greater likelihood that your connection will drop more packets of data that need to be retransmitted and thus not only slowing your connection but also causing it to have to work harder and draining more battery when it's actively downloading/uploading. That's why having it hand off is for the best than fighting it to stay on LTE. This is most likely why people always complained about the Thunderbolt having such poor battery life as no one ever saw what their RSRP was on it, only their RSSI like all other Gingerbread devices.

You can also consider RSRP the "absolute strength" of your current connection.


Received Signal Strength Indicator (RSSI), is the linear average of the total received power in Watts. This is used to measure the db signal for CDMA (3g/2g [2g being your 1x and voice]) signals and used in determining the "signal to noise ratio". It was what was shown on all devices as the "signal" under the Android settings before Android 4.0. Basically this is how much noise/interference is in your connection. Not so good for measuring the overall power of it. It should be in the range of like -58db and greater (like -32db). In other words, the closer it is to being positive, the better. If it's in the high 80s or 90s, your signal is probably starting to cause some slight battery drain when idle. RSSI has less to do with how great your network speeds are and more to do with how good your potential battery life will be.

SNR (Signal to Noise Ratio):

The higher your SNR, the more throughput (better download/upload speed) your connection will have. The lower the number, the worse it will be. The Nexus tends to have a lower SNR on average than phones with Qualcomm chipsets, such as the Galaxy S3. What does that mean? It means you are more prone to have interference on your connection to the towers when your signal is obstructed by scenery or the building you are currently located in. That means slower speeds and higher potential for unstable connections.

CQI (Channel Quality Indicator):

CQI is measured 0 to 15, with higher being better. It's a measure of how good the quality is for the current channel the cell tower has you on. CQI is derived from the SNR (signal to noise ratio) and the SINR (Signal Interferance Noise Ratio).

RSRQ (the overall quality of your signal in general) and SINR "Signal Interference Noise Ratio on LTE":

This is the great your connection is overall (the stability of it and how close it is to handing off to 3G). RSRQ ranges from -3db to -19.5db with a number closer to -3db being better. SINR is similar to RSRQ, but the measure may differ. I still need to verify which variable relates to SINR in the source (the RSRQ weirdly shows as positive in the Nexus SDK, which shouldn't be possible, but SINR can be positive so I'm not sure if they have it linked wrongly or what just yet). It takes in account of both your overall signal strength (RSRP) and the noise/interference in the connection (RSSI). Your phone is using this to determine when to hand off to 3G or go back to LTE. Reference Signal Received Quality (RSRQ) is defined for Verizon as 17db + (RSRP signal + | RSSI signal |) | | being absolute value. The graph below shows how RSRQ helps to determine when you it should hand off versus just RSRP alone:

Posted Image

From Verizon themselves :

The LTE SINR should be greater than 12.5db. The connection may drop to a 3G network with an SINR value of -6, resulting in slow speeds.

"Why does my Nexus not hand off exactly the same as <insert proprietary android os based phone here>?"

Because it goes back to what I already mentioned in that other OEMs don't measure the LTE signal with the same metrics as they do on the Nexus (it was only added to the Android source with ICS and before then each carrier just "rolled their own" thing probably using the RSSI of the LTE signal to handle when to hand off) so the phone thinks the LTE signal is also better than it actually is and so it's staying on what is really a *worse* LTE signal when it should be handing off to a better CDMA/3g signal. Also see the part about RSRQ above and the graph. It'll be far easier to tell what they're doing when they update to ICS though as we'll have access to more information.

RSSI is an okay metric to handle 3g/cdma, but it's not nearly as good for LTE as RSRP is or RSRQ. OEMs are still using it other than for the Nexus and it's those other phones hold LTE longer than they should in many cases as that was the metric they had to go on with Gingerbread and before RSRP became the standard measure of LTE signal for Android.

*You're welcome to question anything I stated above in the discussion as long as you do it in a constructive way that's not flaming. BUT if you do, please provide FACTUAL information from credible sources. That means things like "Well, I compared the Nexus to X phone and it didn't look as good" do not count as factual. Non factual posts will most likely be considered trolling or flamebait that's trying to derail this into another one of the typical "signal quality" discussions we have all seen before and be subject to removal (nothing personal, it's just you have to spend time on something if you want to disagree with it in public).

From a few tests of pulling the signal info out of my phone directly using the ICS source (I was in a crap signal area when I took them):

cdma db = -100
cdma ecio = -150
evdo db = -105
evdo ecio = -150
evdo snr = 1
lte sig strength = 10
lte rsrp = -109
lte rsrq = -8
lte snr = 10
lte cqi (channel quality indicator) = 7 (measured 0 to 15, higher being better)

cdma db = -100
cdma ecio = -150
evdo db = -105
evdo ecio = -150
evdo snr = 1
lte sig strength = 10
lte rsrp = -108
lte rsrq = -8
lte snr = -30
lte cqi = 7

You can caculate my RSSI from knowing the RSRP and the RSRQ:

rsrq = 17 + (rsrp + X)
-8 = 17 + (-108 + X)
x = -83db → my LTE RSSI

Conclusions thus far

It's actually a good thing it's handing it off and staying on 3g for most use cases. If it were me, I'd be more upset with it staying on it when it's eating battery or handing off and switching back constantly instead of staying on one or the other as that also drains battery. If you want to force it to stay on LTE, dial *#*#4636#*#* and tell it to stay on it. It may interfere with calls though and drain more battery, so just as a fair warning.

Additional Info/Further Reading:

http://www.scribd.co...353976/12/RSRQ? (probably the best reference on what RSRQ is and RSRP)



But...if one wants to believe whatever voodoo makes one signal "worse" than another then I guess that's everyone's right. I give up trying to convince -_-

NEXT UPDATE: add logging to the app and give stats on the signal logs taken (mean, median, standard deviation, variance, etc). Maybe a built in "speedtest" for your connection as well.

UPDATE (2012-11-12): Now added to the Android Market. Link is pending to when it gets added officially (day or two). The app on the market has ads to support my continued development, but the version below (scroll down) does not have them. Otherwise, they are the same.

UPDATE (2012-05-29): Created an app to test your signal. If you give out the link to the app, please link directly to the topic and not the apk/app itself so that people can read the topic before getting it. App signal readings update everytime the phone notifies of a signal change. So in other words, it updates as often as the signal does under settings → status. RSRP is the same signal you see under there if you wanted to match it up. Also added more to the definitions for the terms shown in the app in my post above so you can see how they equate to your signal quality. App should work on Android 2.2 and above and on any sort of carrier (including GSM), but it may not show everything for non-ics devices.

If anyone has any suggestions for things to add to it, feel free to let me know.

Posted Image

Market version with ads is located here. It's the same as the other version, but you'll get updates through the market + very small support for me to try to add more features in my free time.

Ad free version is available here

Changelog is available here.

Basic App Source (to prove data is legit): https://github.com/yareally/SignalInfo

Screen shot:

Posted Image
UPDATE (2012-05-18): Added in more explanation, another good reference and some clarification. Fixed a typo in RSRQ formula.

#851191 Tha New AOKP -icons-cases-t-shirts! [Cases Available!]

Posted by ThaPHLASH on 27 July 2012 - 09:12 PM

I have some really cool things right here! I know you all are gonna love this stuff as much as I do.
Tha AOKP t-shirts and cases are ready!
Posted Image

Posted Image
A big thanks to CruzerLite for pulling this off!

Take a look at those icon pack, each one is delivered in 4 styles or more, giving you the opputunity for infinite combos and available right away.

- Tha New AOKP (4 icon packs)

Posted Image
Posted Image
Posted Image
Posted Image

- Tha New AOKP Steel (4 icon packs)

Posted Image
Posted Image
Posted Image
Posted Image

- Tha New AOKP Color (5 icon packs)

Posted Image
Posted Image
Posted Image
Posted Image
Posted Image
Tha New AOKP Xtended (4 icon packs)
Posted Image
Posted Image
Posted Image
Posted Image

(hit that like button too dammit!)

#506669 AOKP | toro | JB Milestone 1

Posted by roman on 25 February 2012 - 04:42 PM

Posted Image

Posted Image

Newest change logs are available at the AOKP site
Posted Image

  • Make sure you're on the latest CWM


  • wipe data/factory reset in recovery

  • flash ROM

  • flash Gapps

  • reboot
Posted Image
Find latest releases here.

Build 5 here.

Posted Image
We spend countless of hours doing this for next to nothing. Posts, views, and donations encourage me, and everyone else who helps out.

Donate to Roman
Donate to Whitehawkx
Donate to Zaphod-Beeble
Donate to ProTekk
Donate to Sethyx
Donate to SteveSpear
Donate to MarcLandis
Donate to Sixstringsg
Donate to AdamtheCashew
Donate to Xoomdev
Donate to Birdman
Donate to Khas'Mek
Donate to Kwes1020
Donate to Nitroz
Donate to JustReboot

Donate to CyanogenMod

Every donation is cherished and loved.

If you'd like to help contribute by writing code, feel free to stop by IRC and talk to us!
Posted Image
Check out the ROM source on github. Open source, in the spirit of community kangage.

If you'd like to help with AOKP, please don't hesitate to contact me. I'd love to get as many developers in on this as possible!

Best way to help out or contact us is via IRC.

#794631 [Inverted] Inverted Apps (update 4-5 GoogleSearch/now2.4.10 GoogleMusic4.5.914)

Posted by travp624 on 09 July 2012 - 08:47 PM

Mod Type:: GApps

Difficulty:: Easy

Mod Base:: AOSP

Mod Status:: Stable

Apply In:: CWM Recovery

Optional:: Themed

Requires Root:: Yes

Optional:: Smali Edits

Android Version:: 4.2.2 (JB)


TeamBAKED is proud to give onto you a totally Inverted Google Apps experience!
Many have asked wheres the all in one. There is not an all in one I did this for simplicity. It is very easy to use 7zip and create your own all in one tailored just for you!
Any problems post here and I will try to help as best I can!
Thanks to B-boy for all his help!!
Have to give credit to tgwaste (not for help but for the modded Mms.apk to look thru)
for the divider removal! Where he got it I don't know!

Inverted Contacts This app is only tested working on the Gnexus as thats where its from.

Posted Image

Inverted Calendar

Posted Image

Inverted Email

Posted Image
Inverted Play Store
Posted Image
Inverted Talk

Posted Image

Inverted Mms

Posted Image

Download Links

  • Jelly Bean apps (4.2.2)
  • Contacts updated 10-8 (with t9search) just the contacts.apk now!
  • Calendar
  • Email
  • Talk updated 10-16 (from my single flash gapps package)
  • Mms updated 10-8 (still all the great features and now theme ability)
Install Instructions!!!
  • Place on sdcard!

  • Reboot into cwm or twrp recovery!

  • Flash downloaded zip file!

  • Enjoy!

Please enjoy!
Usual disclaimer applies! You break it its your fault not rootz or mine. However having said that I will help in whatever way possible!

If you feel the need to buy me a beer or soda it will be greatly appreciated!!!
It also would help pay the $9 monthly fee to mediafire so no one sees ads anymore!!!! :tongue2: Posted Image Posted Image