Related
USE THIS AT YOUR OWN RISK.
I am not installing this kernel on your device. I've even gone out of my way to not give clear directions on how to install it yourself. If you decide to install this kernel, you are assuming all risks involved with it.
WARNING: THIS KERNEL IS NOT FULLY COMPATIBLE WITH THE LA3 FIRMWARE UPDATE. USING THIS KERNEL WITH THE UPDATED VERSION WILL RESULT IN WIRELESS ETHERNET BEING DISABLED.
Welcome to my custom compiled kernel for the Samsung Galaxy Tab 7.0 (wifi only.) This kernel will ONLY work for the GT-P6210 model.
The kernel should be compatible with any stock firmware or anything custom that's derived from the stock firmware. (I refuse to call it a ROM. It's not Read Only.)
First, proper credit should go to Entropy512 and his SGH-i777 kernels. It's from that work I was inspired to do this, and from that work where I'm pulling ideas and changes (when compatible.) I'd give some credit to Samsung, but they only bothered to post partial source code, and didn't even bother to post it with the proper config flags.
The idea behind this kernel is and will be to make the device more efficient. Longer battery life while running more smoothly is a Good Thing. I don't care about benchmark scores. In case someone missed that, I DO NOT CARE ABOUT BENCHMARK SCORES. Anyone can tweak a system to get a better benchmark, but that doesn't mean it'll actually work better. Concern #1 is and should always be stability. While some tweaks will be added that allow a user to make the system unstable, they won't be the default.
Differences from stock currently include:
Very slight speed increase in bootup, possibly in other areas
Support for init.d script parsing on bootup
A real busybox (with proper links) installed to /sbin (and therefore available to the system)
Undervolting and minor overclocking support (via SetCPU)
android ram_console support (useful for post-mortem of crashes.)
standard boot animation support
quicker charging with iphone chargers
Voltage and Clock Adjustments:
If you choose to tinker with the processor voltages and/or clock speeds, there will be no support in this thread. None. Yes, I'm using it myself, but I won't even support myself if I screw things up. If you find an issue with this kernel, BEFORE you post about it here, re-test after reverting all the voltage and clock speeds back to default. If it works with the default clocks/voltages, then don't waste your time or mine by posting about it to this thread. It's not supported. You can destroy your tablet by messing with the voltages and clocks.
You'll need a separate tool for voltage and clock adjustments. The one I see most frequently used is "SetCPU" (http://forum.xda-developers.com/showthread.php?t=505419.) I'm in no way affiliated with the author of that tool. You should be warned that SetCPU does not seem to be fully compatible with our tablets: There seems to be no way to bring up the menu in the program. If the program is "honeycomb compatible", this is likely due to the author making assumptions about screen dimensions on tablet devices (fairly common error.) Don't tell me about it. It's not my program.
ToDo:
Find source for the ethernet module and replace it (which will also allow adding more generic optimizations to the kernel.)
ethernet adhoc support (not really kernel specific, but not possible without the ethernet module...)
Figure out what samsung changed in the LA3 kernel (and didn't publish) so I can get the kernel working with the firmware update.
Known Issues:
Probably not compatible with stock firmware updates. (won't fix.)
NOT COMPATIBLE WITH LA3 FIRMWARE UPDATE!!
Flashing Instructions:
This is being released as an installable "update.zip" style installer. Stick the .zip file on your device, reboot into recovery, and install it from there. If this isn't enough information, please search and read the forums before changing your device kernel. (Flashing a .zip in recovery is a very basic skill that should be mastered early.)
Firmware Developers:
If you want to use it, please link to this thread and give clear indication of which version of the kernel you are including.
Legal:
This is based on the linux kernel, and therefore I'm including links to the modified source for the kernel (https://github.com/garyd9/linux_kernel_GT-P6210) and contents of initramfs (https://github.com/garyd9/initramfs_normal_GT-P6210)
PLEASE DO NOT MIRROR THE DOWNLOADS. IF YOU WANT TO REFERENCE THE KERNELS, PLEASE ONLY LINK TO THIS THREAD.
Change Log
20120128:
Support for iphone charger detection - pull up to 750mA from detected iphone chargers (1500mA from the samsung charger, and 500mA from everything else including a computer USB port.)
Testing USB "high current" charging. This is currently not enabled by default (and until I'm happy that it's stable and safe, I won't be documenting it.)
20120123: (actually posted on the 24th)
Minor adjustments related to the MMC and SD card interfaces (which includes the wifi interface)
Starting to pull in mainline kernel fixes (including fixes for some kernel panics/reboots.)
20120107:
disable mali state tracking. Doesn't seem to have any actual impact, but should reduce a small amount of overhead
add support for "reboot bootloader." Actually, the support was already there if the command sent to reboot was "download", but several android tools (such as "Quick Boot") want to send the command as "bootloader." This is only useful if you have a desire to reboot your device into "Download Mode" (aka "ODIN mode")
Replaced samsung j4fs.ko binary module with one built from sources. No impact other than easier to maintain.
20120105:
added standard bootanimation support (if bootanimation.zip is found in /system/media, it's used. Otherwise, the default samsung animation is used. Standard samsung music is played either way.)
It's now possible to tweak the conservative governor sampling rate down to 50,000 (default is still 100,000.) If done, this may make the tablet more responsive in some situations (however, there may also be a negative impact to battery life - everything is a trade-off.)
20120102:
added android ram_console support. After installing this kernel, if you reboot/crash, it should leave a file in /proc called "last_kmsg" that will show the last several kernel messages from before the reboot/crash.
20120101:
undervolting and overclocking support (only up to 1.4GHz)
If you decide that you want to overclock or undervolt your tablet, you are 100% on your own. You can easily fry your tablet's processor by messing with voltages and clock speeds. If you have issues with this kernel, remove all overclocking and voltage adjustments before you even bother posting on this thread.
Use "SetCPU" to change voltages, clocks, and governors. SetCPU can be found on the market and on XDA at the following link: http://forum.xda-developers.com/showthread.php?t=505419 (I am in no way affiliated with the author of that program.)
20111231 (initial release):
build compatible with stock ar6000.ko module
init.d script support
busybox in /sbin
cleanup of kernel config to remove excess debugging (when possible)
Frequently Asked and Anticipated Questions
Q: Will this work with the GT-P6200, GT-P6200L, or SGH-T869?
A: No
Q: Can you make a kernel for the GT-P6200, GT-P6200L, or SGH-T869?
A: I probably could if I had the hardware to test with. Without a sample of hardware, I can't even begin to guess if what I've done already will work, or what it might take to make it work. If you really want me to do one of those devices, please feel free to send me one. (Making a recovery kernel is quite a bit easier as it doesn't have to work with the ethernet, sound, modem or any other drivers.)
Q: Why doesn't this kernel include CWM Recovery?
A: On the GT7+ devices, the recovery boots from a completely seperate partition than the normal boot. When the device boots recovery, the normal boot kernel isn't ever loaded (and vice versa.) Therefore, it doesn't make sense to package them together.
Q: Why is the sky blue?
A: Please refer to: http://www.sciencemadesimple.com/sky_blue.html
reserved for even more future use
Nice.... I installed just fine. Will Play around and let you know. Thanks further kernel....
Sent from my GT-P6210 using xda premium
Nice to see! Now have a good reason to install clockwork recovery! Thanks Gary!
PLEASE IGNORE THE SIGNATURE!
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
PLEASE IGNORE THE SIGNATURE!
Click to expand...
Click to collapse
Wow, that actually made me laugh out loud. (My wife just ran in to ask if I was alright.) Thank you.
I've got a new and improved signature modified especially for you! Glad to have made you laugh! Happy New year Gary and fellow community members! I wish you and your families happiness and good health!
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
I know kernels can have an effect on colors. Gary does your kernel improve color and if not could you possible hack that part of the kernel to improve in future releases, thanks
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
I'm updating my tab in kies rite now before I flash this kernel. Your kernel should work fine? I know we can't update in kies once clockwork recovery is installed but I was wondering if kies will still recognize that I have a firmware update? I know that we have to odin back before we can update in kies but not sure about the other two questions, any help would be appreciated, thanks
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
I'm updating my tab in kies rite now before I flash this kernel. Your kernel should work fine? I know we can't update in kies once clockwork recovery is installed but I was wondering if kies will still recognize that I have a firmware update?
Click to expand...
Click to collapse
Probably, but I didn't try it. Let us know how it works out.
Thanks Gary! Recovery is up and running and even made a nandroid. I located it to make sure everything worked (took a really long time). I see your framework zip wipes the dalvik cache and I was wondering if we have to wipe both caches before flashing the kernel? Thanks for your development! Much appreciated
Sent from my GT-P6210 using xda premium
Just flashed and it feels very smooth so far thanks!
Sent from my GT-P6210 using xda premium
mike216 said:
I see your framework zip wipes the dalvik cache and I was wondering if we have to wipe both caches before flashing the kernel?
Click to expand...
Click to collapse
What framework are you referring to? I try very hard to make the stuff I do "self contained", so if a cache should be wiped, it either gets wiped automatically, or there's a message displayed telling you to do it manually.
In context of this thread, there's no need to wipe any caches before installing this kernel.
Perhaps your question is in reference to something in another thread?
It was always a big suggested instruction on wiping both the cache and dalvik cache when installing roms and other things on my nexus s and vibrant so just thought it would be the same on my tablet
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
The framework zip I was talking about was the flashable zip you put together for the theme here in the development section.
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
It was always a big suggested instruction on wiping both the cache and dalvik cache when installing roms and other things on my nexus s and vibrant so just thought it would be the same on my tablet
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Click to expand...
Click to collapse
A kernel is not a ROM, two totally different things and you don't need to wipe to install one. An easy explanation of the difference is a kernel is what runs the hardware (cpu, memory, etc.) and a ROM is just a UI (user interface).
With ROMs the general concensus on wiping is you need to do a full system wipe as well as wipe the dalvik cache if you are switching between ROMs, say from ROM A to ROM B but do not need to wipe if it's just an incremental update say ROM A to ROM A.1 unless advised to do so by the dev.
Awesome work Gary. If I had the knowledge to do this I would. Tab feels great.
Just glad to see some little development finally kicking off.
Sent from my ICS'd themed Galaxy Tab 7+
Glad you finally got things working.
Closed-source modules piss me off... Module versioning enforcement can get even some of the best devs (netarchy and I kept missing each other on IRC, it took a week before we figured out why his Infuse kernels wouldn't boot.)
Samsung is good about releasing kernel source in a timely fashion, but they SUCK at fixing broken source releases.
(Edit: WTF? They included BCM4330 source code in your release but NOT the Atheros 6k drivers?)
Edit: This might be useful, not sure - http://linuxwireless.org/en/users/Drivers/ath6kl
After lots of testing I do find its a little quicker! Don't know if its placebo but it sure feels fast. Nice work Gary. Recovery working great but the only odd thing I noticed was how long it took to do a nandroid backup. For a minute there I thought it froze up. All is good thought
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Here is a guide I have put together for the VZW Samsung SCH-I535 Galaxy S3
------------------
This guide contains 7 sections:
Section 1: How to Root/Unlock bootloader/Flash CWM recovery coming from stock 4.0.4 ICS
Section 2: How to flash a Custom Touchwiz 4.0/4.1 rom
Section 3: How to flash a CM10/AOSP/AOKP JellyBean rom
Section 4: How to flash a Custom Kernel
Section 5: How to Odin back to Stock from any rom/recover from a soft brick/flash a stock radio
Section 6: Directory
Section 7: Glossary
-----------------
This Guide Is For The D2VZW SCH-I535 ONLY!! DO NOT ATTEMPT TO FLASH ANYTHING FROM THE I9300 International GS3 Or You Will Hard Brick The Device!!
-----------------
*I am not liable for what you do to your DEVICE!!
*I take no credit for links posted in this thread... This is just a guide or more so a collaboration of different guides all put into one thread!!
*This Guide will not trip your flash counter!! Flashing any custom software via odin will infact trip the flash counter!! Thats why I use these methods and the only thing I use odin is for flashing STOCK firmware Only!!!
-----------------
*** Before going any further I strongly suggest reading and performing this action before flashing any custom roms!!! ***
[HOWTO]Comprehensive IMEI/EFS Backup- http://forum.xda-developers.com/showthread.php?t=1852255
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Section 1: ( For Windows OS)How to Root/Unlock bootloader/Flash CWM recovery coming from Stock 4.0.4 ICS
*This works with all current Stock 4.0.4 ICS builds...VRALF2, VRALG1, VRALG7, VRALHD, and VRALHE.
*However RootdebugFS does not work for 4.1.1 JellyBean. If you want Stock rooted Jellybean then there are 2 options! .
*Option 1 is to proceed to section 5 and use odin to flash a Stock pre-rooted Jellybean rom. Then follow steps 8-12 from this section for unlocking and flashing a custom recovery.
*Option 2 is to complete this section 1, then proceed to section 2 and flash a Jellybean rom via CWM or TWRP recovery.
Step 1: Download these files to your pc:
Samsung Driver- http://tinyw.in/Fdoz
RootDebugFS- http://goo.im/devs/invisiblek/i535/Root%20Debug%20FS.7z
Step 2: Install samsung drivers to the pc and unzip the RootDebugFS tool to desktop.
Step 3: Connect the device with the oem usb cable to pc.
Step 4: On your device, Make sure USB Debugging(settings/developer options/usb debugging) and Install of Unknown Sources(settings/security/unknown source) is checked.(Also, make sure there are no other android devices, emulators, or any tethering programs running!!).
Step 5: From the PC, Open the Root Tool folder you downloaded in step 1 and Double click "RootDebugFS". press 1 then hit enter.
Step 6: Agree to all of the disclaimers by pressing Y after each one pops up.
Step 7: Once the root process starts DO NOT UNPLUG YOUR DEVICE until it completes!
*Congrats you should now be rooted! Continue following instructions for unlocking bootloader and flashing a custom recovery*
*TAKE NOTE THAT IF YOU EVER OTA UPDATE YOUR BOOTLOADER WILL BE LOCKED*
Step 8: Open up the SuperUser application from your app drawer and make sure the binaries are up to date! You can do this by sliding over to the info screen and selecting update binary.
Step 9: Download the EZ-Unlock app to your device from HERE.(Only use version 1.1 or 1.2 for now as the latest versions have issues!)
Step 10: Open the app and select unlock! Now your unlocked...yup its that easy!
Step 11: Download the EZ-recovery app to your device from HERE.
Step 12: Open app, select CWM recovery, tap the pulldown menu, choose CWM 6.0.1, select flash, then reboot recovery.
Step 13: Congrats you are now rooted, unlocked, and have a custom recovery installed!! If you want to flash a custom rom proceed to section 3 or 4.
*Credit goes to Adam Outler, Noxious Ninja, mmmeff, and all others involved!!!
*(Mac/Linux) users read HERE for Rooting!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Section 2: How to flash a Custom TouchWiz 4.0/4.1 rom from CWM recovery
**YOU MUST BE ROOTED AND HAVE BOOTLOADER UNLOCKED!**
Step 1: Download one of the roms below to the root of your internal sd card(/mnt/sdcard):
ICS 4.0.4
Bean's Custom Stock-http://forum.xda-developers.com/showthread.php?t=1768209
Rooted Stock VRALHD- http://forum.xda-developers.com/showthread.php?t=1911118
TW JellyBean 4.x
Incubus JellyWiz- http://forum.xda-developers.com/showthread.php?t=1853337
Eschelon's Synergy- http://forum.xda-developers.com/showthread.php?t=1792499
Scrosler's CleanRom- http://forum.xda-developers.com/showthread.php?t=1832070
Puremotives Galaxy Mod- http://forum.xda-developers.com/showthread.php?t=1953008
Beans JellyBeans- http://forum.xda-developers.com/showthread.php?t=1973982
Stock rooted VRBLK3 4.1.1- http://www.androidfilehost.com/?fid=9390214368362234071
Stock rooted VRBMB1 4.1.2- http://forum.xda-developers.com/showthread.php?t=2178482
Step 2: Download and install the EZ recovery App from HERE (If your coming from section 1 and already have a custom recovery, reboot recovery and skip to step 4).
Step 3: Open app, select CWM recovery, tap the pulldown menu, choose CWM 6.0.1, select flash, then reboot recovery.
Step 4: Perform a Nadroid Backup from the "back up/restore" menu(optional but recomended)!
Step 5: Wipe Data/Factory reset, then under the "mounts & storage" menu Format System.
Step 6: Navigate to "install zip from sdcard", then from there "choose zip from sdcard", and finally install the rom you downloaded in step 1.
Step 7: Reboot.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Section 3: How to flash a CM10/AOSP/AOKP Jelly Bean rom
**YOU MUST BE ROOTED AND HAVE BOOTLOADER UNLOCKED!**
Step 1: Choose and download one of the roms in part A and the file in part B to the root of internal sd card(/mnt/sdcard):
A.
CM11- http://forum.xda-developers.com/showthread.php?t=2558946
CM10.2- http://forum.xda-developers.com/showthread.php?t=2405425
Pac-Man http://forum.xda-developers.com/showthread.php?t=2028443
Eclipse- http://forum.xda-developers.com/showthread.php?t=1934572
B.
Kit Kat Gapps https://plus.google.com/107979589566958860409/posts/FYkuneXi3J7
JB Gapps- http://goo.im/gapps
Inverted JellyBean Gapps- http://forum.xda-developers.com/showthread.php?t=1797292
Step 2: Download and open the EZ recovery app from HERE (If your coming from section 1 and already have a custom recovery, reboot recovery and skip to step 4).
Step 3: Open app, select CWM recovery, then tap the pulldown menu, choose CWM 6.0.1, select flash, then reboot recovery.
Step 4: From CWM recovery, Perform a nandroid backup from the "backup/restore" menu(Optional but recomended).
Step 5: Wipe data/factory reset, then under the "mounts & storage menu" Format System.
Step 6: Navigate to "install zip from sdcard", from there "choose zip from sdcard", and finally install the rom you downloaded in step 1 part A.
Step 7: Again, Navigate to "install zip from sdcard", from there "choose zip from sdcard", and finally install the gapps package you downloaded in step 1 part B.
Step 8: Reboot.
*This same method can be of use to revert back to Touchwiz ICS or JellyBean aswell...no extra steps are needed. Simply wipe data in cwm recovery and flash rom or restore nandroid.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Section 4: How to flash a Custom Kernel
**YOU MUST BE ROOTED AND HAVE BOOTLOADER UNLOCKED!**
Step 1: Download one of these kernels to the root of your Internal SD Card(/mnt/sdcard):
-------------
TouchWiz ICS 4.0.4 Kernels
Imoseyon LeanKernel- http://rootzwiki.com/topic/31329-imoseyon-test-leankernel-tw-729-v111-kexec/
Scrosler's CleanKernel- http://forum.xda-developers.com/showthread.php?t=1850495&page=2 (DOES NOT work on BEANS)
Morfic's Trinity GST- http://forum.xda-developers.com/showthread.php?t=1874720 (Works on CM9 or TouchWiz)
--------------
ICS & JellyBean Kernels(CM9/CM10/AOKP/AOSP)
Imoseyon LeanKernel- http://rootzwiki.com/topic/32286-kernel-aosp-jb-leankernel-minimalistic-kernel-v02-beta-81312/
Ktoonsez KT747- http://forum.xda-developers.com/showthread.php?t=1853816
Faux (CM9/CM10/AOKP/AOSP)- http://forum.xda-developers.com/showthread.php?t=1905141
---------------
Step 2: Download the EZ Recovery app from- HERE (If your coming from section 1 and already have a custom recovery, reboot recovery and skip to step 4).
Step 3: Open app, select CWM recovery, tap the pulldown menu, choose CWM 6.0.1, select flash, then reboot recovery.
Step 4: From CWM recovery, wipe cache, then navigate to the "advanced" menu and wipe dalvik cache.
Step 5: Navigate to "install zip from sdcard" and then from there "choose internal sdcard".
Step 6: Install the kernel.zip that you downloaded in step 1.
Step 7: Reboot.
*Credit goes to Imoseyon, BMc08GT, Invisiblek and all other devs involved.
*These steps work for any .zip file such as themes, custom boot animations, and what not...just replace the .zip file in step 1 with the one your trying to flash!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Section 5: How to Odin back to Stock from any rom/recover from a soft brick/flash a stock radio
* If your device is currently running a 4.0-4.2 base and you forgot to unlock your bootloader before flashing a custom rom, you probably were greeted with the yellow triangle....Dont Panic! Simply power off the device and follow directions below. Odin will recover your device!! Make sure to only use a 4.0-4.2 Odin file to restore back to stock.
***NOTE*** If you did not take the 4.3 OTA then do not use the 4.3 files in link below. These will permanently lock your bootloader and you will be limited to using safestrap from here on out.
Step 1: Download and install these files to your pc:
Odin- http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443
Samsung Driver- http://forum.xda-developers.com/showthread.php?t=2038555
Step 2: Download one of the Factory Stock roms below to your PC:
*These are Official full wipe versions that will format the internal sd and lock bootloader!!
All Official Stock Builds- http://samsung-updates.com/device/?id=SCH-I535(Only use these files if you have a locked 4.3 bootloader.)
VRALG1 4.0 ICS-http://www.mediafire.com/download/kkhq5wtj4r3fpwf/COMBINATION_I535VRALG1_I535VZWALG1_743127_REV09_user_low_ship.tar.zip(Do Not use this if your device took the 4.3 OTA)
*In the link below are PRE-ROOTED full wipe versions that will lock the bootloader(Thanks Mr. Robinson!!) See section 1. steps(8-12) for unlocking and flashing a custom recovery.
http://forum.xda-developers.com/showthread.php?t=1984436
Please Remember to back everything up to a pc or external sd before flashing!!
Step 3: Power device off, hold the volume down/home/power keys until you see a yellow triangle, then press the volume up key to access "odin or download mode".
Step 4: Open odin and connect the oem usb cable from pc to device. There should be a "comport number" in upper left hand corner of odin indicating communication between the pc & device.
Step 5: Click on the PDA function of odin. Select the stock rom you downloaded in step 2, then select start. This operation should take less than 8 minutes before odin will say pass/reset and your device will reboot.
------------------
*Flashing a Stock Radio with Odin or a Custom Recovery
Download's:
Stock Radios- http://rootzwiki.com/topic/34053-officialmodems-vrlhd-verizon-sgs3-sch-i535-odin-or-recovery-flashable/
Odin Method:
Step 1: Download one of the files above to your pc.
Step 2: Power device off, then hold the volume down/home/power keys until you see a yellow triangle, then press the volume up key to access "download mode".
Step 3: Open Odin and connect the oem usb cable to pc & device, you should see a "comport #" in upper left hand corner of odin.
Step 4: Make sure auto reboot is checked.
Step 5: Click on the PDA function of odin and select the file you downloaded in step 1, select start, should take roughly 1min, then odin will say pass/reset.
Step 6: Your device should Reboot.
CWM or TWRP Recovery method:
Step 1: Download files A and B(optional) to the internal sd.
A) Choose a Recovery flashable radio- http://rootzwiki.com/topic/34053-officialmodems-vrli5-verizon-sgs3-sch-i535-odin-or-recovery-flashable/
B) RPM.zip(Optional)-
* A great explanation about RPM cand be found HERE
VRABLI5- https://app.dumptruck.goldenfrog.com/#p/_DeLB5rDRb
VRABLJ1- http://myandroidfiles.com/beanstown106/VRALJ1.rpm.zip
VRABLK1- http://myandroidfiles.com/beanstown106/VRBLK1.rpm.zip
VRABLK3- http://www.androidfilehost.com/?fid=9390214368362234078
Step 2: Reboot recovery via the power menu or power off and use the three finger method.
Step 3: Select install zip from sd and flash the radio.zip you downloaded in step 1A.
Step 4: Slect install zip from sd and flash the rpm.zip you downloaded in step 1B.
Step 5: Reboot.
Section 6: Directory
[APP][MOD] MOBILE ODIN- http://forum.xda-developers.com/showthread.php?t=1347899
[APP][MOD] SIII AOSP Camera- http://forum.xda-developers.com/showthread.php?t=1746611
[APP][MOD] AC!D Audio Technology | v4.0 (22.10.12)- http://forum.xda-developers.com/showthread.php?t=1883262
----------
[GUIDE] Unsure about your ROM choice- http://forum.xda-developers.com/showthread.php?t=1950824
[GUIDE] Verizon Galaxy SIII Downloads List- http://forum.xda-developers.com/showthread.php?t=1850506
[GUIDE] Set up Verizon Galaxy S3 as World GSM Phone (confirmed working)- http://forum.xda-developers.com/showthread.php?t=1809314
[GUIDE] Enable UMS Mode for External SD Card- http://forum.xda-developers.com/showthread.php?t=1785243
[GUIDE]Google Wallet - Everything you need to know before you flash or root- http://forum.xda-developers.com/showthread.php?t=1764428
[GUIDE] for dual booting CM9- http://forum.xda-developers.com/showthread.php?t=1774795
[GUIDE][HOW TO] Edit Earphones Connected-http://forum.xda-developers.com/showthread.php?t=1782155
----------
[HACK] for removing wifi reminder-http://forum.xda-developers.com/showthread.php?t=1770622
[HOW-TO] Unbrick your soft bricked Galaxy S III- http://forum.xda-developers.com/showthread.php?t=1840030
[How To] Backup and restore your IMEI / MEID / EFS Data- http://forum.xda-developers.com/showthread.php?t=1791291
[How To] invoke self hardware test-http://forum.xda-developers.com/showthread.php?t=1767247
[HOWTO]Comprehensive IMEI/EFS Backup- http://forum.xda-developers.com/showthread.php?t=1852255
----------
[MOD][VRBLK3] PDroid Privacy Protection- http://forum.xda-developers.com/showthread.php?t=2043699
[MOD]AOSP Lock Screen with Toggle- http://forum.xda-developers.com/showthread.php?t=2002620
[MOD]Super Simple 5 minutes Wireless Charging Mod for Samsung SG3- http://forum.xda-developers.com/showthread.php?t=1877191
[MOD]Enable wifi in notfication bar- http://forum.xda-developers.com/showthread.php?t=1775235
[MOD]App2ExtSD2 [Works for all U.S. Galaxy S3!]- http://forum.xda-developers.com/showthread.php?t=1849860
[MOD] Latest Google Wallet (10/23/12)- http://forum.xda-developers.com/showthread.php?t=1810040
[MOD]AGPS Patch Galaxy S III 3.1 & 2.2 | NEW SIII SPECIFIC BUILD | Tentative Support - http://forum.xda-developers.com/showthread.php?t=1880411
[MOD] OTA updates - keep root, custom recovery, unlocked bootloader and Google Wallet- http://forum.xda-developers.com/showthread.php?t=1964502
----------
[OFFICIAL] Tips and Tricks thread-http://forum.xda-developers.com/showthread.php?t=1732018
[OFFICIAL][MODEMS] Verizon SGS3 (SCH-I535)- http://forum.xda-developers.com/showthread.php?t=1788313
----------
[ROOT][TOOL] Root the Verizon GSIII without flashing-http://forum.xda-developers.com/showthread.php?t=1792342
[ROOT][TOOL][2012-09-12] SuperSU-Version_Debugfs: Root VZW SGS3 w/out Flashing ROM- http://forum.xda-developers.com/showthread.php?t=1883984
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Section 7: Android Glossary
Download Mode - This is a setting in which you will put your phone when using Odin. There are other ways, but most noobs will reach download mode by powering down, removing the battery, and holding volume down while plugging the factory usb cord into the computer and phone. Odin can only communicate properly with your phone if the phone is in download mode.
F. Reset Time - This is a check box in Odin. It's not clear that anyone knows the exact details of what it actually does, nor is it clear what will happen if you leave it unchecked vs checked. It seems to reset some arbitrary counter in your phone. As a general rule, you can either follow the instructions of whatever guide you're using or just leave the checkbox how you found it.
Fast Charge - This is a feature on some ICS ROMs that can be turned on or off. When enabled, it allows your phone to draw as much charge as possible regardless of the charging source. Without fast charge, your phone will place artificial speed limits on charging when plugged, for example, into the USB slot on your computer. Fast charge bypasses these limits, letting your phone believe it is always plugged into a wall charger. It is worth noting that your phone will not be recognized by your computer as a USB device when fast charge is enabled. It will only charge.
FC - Force Close - This is when an app stops working unexpectedly. This can happen to both rooted and unrooted phones. It doesn't cause any damage to the phone. In most cases, the app can just be opened right back up. It seems to depend on a lot of factors, including the quality of the app itself. ROMs and kernels that experience very few FCs are said to be "stable."
Flash - This is a term used to describe the installation of software onto your phone. It refers to fundamental changes in your phone's operating system. It is different from just installing an app from the Marketplace (Google Play). Commonly, people will flash ROMs, kernels, patches, and radios. There are basically two ways to flash new software onto your phone:
1. Odin
2. CWM Recovery (or a comparable recovery program)
Freeze - There are two meanings in general use. One might use this term to refer to his or her phone becoming unresponsive. More commonly, though, it refers to a special ability of a program called Titanium Backup. This program can be downloaded from the Android Marketplace (Google Play), but it requires a rooted phone to work. When Titanium Backup is used to freeze an app or process, that app or process is essentially gone from the phone. It won't show up in the app drawer, and it won't be running in the background. The difference between freezing and uninstalling, though, is that anything frozen can be quickly "thawed," also with Titanium Backup. With the touch of a button, the missing app or process is right back where it used to be. This is a convenient way for newly rooted users to test the waters of debloating.
Gapps - Google Apps - When flashing custom ROMs, the apps on the phone are usually deleted. As an alternative to going to the Marketplace (Google Play) and re-installing all the favorites (Google Maps, Google Talk, Google Voice, etc.), many devs have packaged these into a tidy zip file that can be flashed via CWM. Why don't they just put the Google Apps in the ROM, you ask? Custom ROMs and Google Apps get software updates at different rates, so keeping the two separate allows users to always have the most up-to-date version of each. On MTD ROMs such as CM7 or anything ICS, you generally must flash the gapps package to get the Android Marketplace (Google Play).
GB - Gingerbread - Android 2.3. Google likes to name its Android releases after sweet foods. Most of our stock phones are running on this release of Android. There are numerous ROMS and kernels compatible with Gingerbread. These are a good starting point for newly rooted users, as they will feel quite familiar.
Github - This is a web-based service where developers can post their code. Depending on the situation, their code can be accessed by other users, modified, or just shared with the world. The site encourages the kind of open source development for which Android is famous.
Governor - This refers to the type of logic your phone uses to control how fast its processor ramps up when needed or slows down when not. The choice of governor can influence overall performance and battery life. The governor can be selected using an OC/UV program such as Voltage Control or NS Tools. No one governor is right for everyone. The fun is in experimenting. Here are some examples and brief descriptions:
performance: Keeps the processor always ramped up to to maximum; useful for benchmarking
ondemand: Rapidly ramps up the processor when needed; gradually slows it down when not needed
conservative: Similar to ondemand, but ramps up more slowly
userspace: The user can define the parameters (for advanced users only).
lazy: This was developed specifically for Android by xda dev Ezekeel. He states it is an enhanced version of ondemand, tuned to our phones' capabilities. Don't be fooled by the name. He tested it with numerous processor-intensive applications.
interactive: Uses a logic to try to predict how quickly it needs to ramp up processor speed, attempting to balance battery life and performance
interactiveX: A tweak on interactive (by dev imoseyon), which locks the processor at the minimum speed when the screen is off
smartass & smartassV2: Modified interactive governors by dev erasmux, they use logic to determine how quickly to ramp up or slow down; designed to optimize battery life without sacrificing performance.
powersave: This keeps the processor always set at the minimum frequency. The name may be a bit misleading, as certain processes will just take longer, using up more battery.
Heimdall - This program is similar to Odin. It was created by an Australian software company called Glass Echidna. It can be used to flash files onto your phone. Some users prefer this program over Odin. Heimdall can be used with Mac computers, whereas Odin can not. Many high level users regularly use both Heimdall and Odin.
ICS - Ice Cream Sandwich - Android 4.0. Google likes to name its Android releases after sweet foods. It comes pre-installed on the Samsung Galaxy Nexus from Verizon. Several developers have created ways to install ICS on the Samsung Fascinate.
init.d - This is a type of script used by developers when they modify Android code. You hear the term a lot because modifications using this type of script have far-reaching effects in the overall performance of the phone. High level users (who aren't quite devs) can even insert bits and pieces of init.d scripts to make minor tweaks to their phones.
Inverted - By default, most Google apps consist of a white screen with dark lettering. Inverting changes this to a dark screen with light letters. There are several advantages to this. Beyond the aesthetic advantages, it tends to be easier on the eyes in low light situations and reduce battery consumption. Inversion is done by talented individuals called themers.
I/O Scheduler - This refers to the type of logic your phone uses to order and process read and write requests to your phone's hard drive. There are several types, which are listed below, but there is no magic bullet. The joy is in finding the one that works for you in terms of performance and battery life. It is worth noting, though, that certain schedulers were designed to be used with mechanical rotating hard drives, taking the drive's rotational position into account. This does not apply to our phones, which use solid state drive technology. A scheduler can be selected by using an OC/UV control program such as Voltage Control or NS Tools. Specific descriptions are beyond the scope of this glossary, but simple Internet searches can expand on any of schedulers listed.
Examples: noop, deadline, cfq, bfq, sio, vr, bfs
* In the absence of a dev's recommendation, if you don't feel like reading up on the subject, you can leave the scheduler at the default or choose noop or sio.
JB - Jelly Bean - Android 4.1. Google likes to name its Android releases after sweet foods. This is the latest version of Android to hit the streets, and devs are flocking to it , making all JB development new and exciting.
Jig - This is a tiny Frankensteinian device made of a small chip, a transistor, and the tip of the little micro-USB connector that you plug into your phone to charge it or attach it to your computer. When your phone will not go into download mode through normal means, putting a jig into the phone when the battery is in will make your phone go into download mode. You can make one yourself or buy one online for less than $10.
Kang - Generally used as a verb, this means to take bits and pieces of someone else's coding and to then integrate it into your own. Granted, noobs won't be doing this, but devs do it all the time. For the most part, this is considered a welcome practice among friendly devs, provided it is done correctly and politely. Kanging often serves to better the community as a whole. The key for devs is to give credit to the other devs from whom they have kanged.
Kernel - This is one of the two main components (ROM being the other) of the software running on an Android phone. It is the piece of software that connects the hardware (screen, softkeys, vibration, speakers, etc.) to the other software components. An unrooted phone comes with a stock kernel. It is stable but somewhat slow. Practically speaking, installing (flashing) a custom kernel will make your phone feel much faster and smoother as it moves through screens and opens apps. Generally speaking, installing a new kernel will not change the basic appearance of your phone or erase any of your phone's information. Custom kernels can also unlock several abilities of rooted phones. Examples include:
-wireless tethering (ignoring that pesky $30/month charge from Verizon)
-control over how and when the softkeys at the bottom of the screen light up
-overclocking/undervolting
-voodoo lagfix (This only applies to phones with BML-based ROMs. MTD ROMs don't need lagfix.)
-custom boot animations
Lean Kernel - Created by imoseyon, He intentionally leaves out a lot of the "bells and whistles" to keep the experience simple, smooth, and fast. Imoseyon works with several phones, so it is imperative that you have the correct version of Lean Kernel, the one appropriate for your phone.
Linaro - This is a team of software engineers developing open source software for numerous platforms, particularly as it relates to getting maximum bang for the buck from systems with memory and hardware limitations. For our purposes, many Linaro modifications are making their way into our custom ROMs, promising increased speed and responsiveness.
Logcat - This is a log of all of the processing activity your phone did over a certain period of time. This is useful for bug reporting, as devs can examine logcats and attempt to determine the source of the error(s). Many threads in the development forum request logcats to go alongside any bug reports. A logcat can be generated through adb, and there are also some apps that will do it for you. Random complaints aren't terribly useful for devs, but logcats generally are. This classic cartoon illustrates how many devs feel about disorderly complaints about their work, even though most are far too polite to say anything.
Milestone - Devs are always trying to incorporate the latest and greatest features into their ROMs. The add-ons are incorporated as parts of new releases, or "builds." This is what makes development exciting, but it also leads to bugs. Milestone builds occur when the devs sit back, roll up their sleeves, and work the bugs out of all the awesome features they've crammed into their work. The milestones are considered the relatively safe and stable builds. When installed correctly, they rarely experience major bugs.
MIUI - This term is a transliteration of a Chinese name for a special customization of Android actually developed in China. MIUI ROMs can be installed on the Fascinate. They change the look and feel of the Android system, moving it closer to something resembling iOS, the iPhone's operating system. A lot of custom development has been done with the software code from the MIUI system. Many devs will integrate bits and pieces of MIUI into their own ROMs. For example, the TSM Resurrection ROM allows you to use the MIUI battery indicator, which looks completely different from the standard battery indicator.
MTD - This is a technical term used by devs to describe the software organization in your phone, as it relates to things called partitions. The bottom line is that the stock organizational system, called BML, is somewhat fixed and limited, whereas MTD offers devs a great deal of flexibility. Heavily customized ROMs like those from CyanogenMod or anything MIUI rely on MTD file organization. All of our ICS ROMs use MTD. MTD ROMs, generally speaking, experience very little lag, as compared to BML ROMs. When returning to a normal BML ROM from an MTD ROM, special precautions need to be taken.
Nandroid - This is a backup of your entire phone as it stands at that moment in time (ROM, kernel, text messages, your Angry Birds progress, etc.). It is stored on your sd card, which is somewhat immune to your tinkering. A Nandroid backup is a good failsafe for the times when you might want to try out that new experimental kernel your favorite dev has been working on. The files can also be saved on a home computer/flash drive/etc. for safe keeping. Nandroid backups are created using a recovery program like Clockworkmod Recovery. CWM can also use old Nandroids to restore a phone to its previous condition.
Nightly - Nightlies - Some rooted users like the idea of having the most stable, tested, and reliable ROMs available. Others prefer the excitement of being on the cutting edge. Nightlies are the untested regular releases of whatever a certain dev happens to be working on at the time. They package them up, post them online, and let the discussions ensue. These are not for the faint of heart. They are for people who are comfortable addressing freezes, boot loops, and force closes.
Noob - If you have to ask what this means, this is what you are. It's a derivation of "newbie" or "newb," someone who's new to the activity at hand. In many ways, the noob is defined by his actions rather than by the amount of time he's spent rooting phones or posting on xda. Here are a few standard behaviors that will immediately brand someone as a noob:
-Posting new threads to ask questions that have been answered dozens of times. (Hint: It's best to search before posting)
-Posting ROM complaints (without logcat), beginner questions, and other non-development topics in the development forums (It has been theorized that this will ultimately be the end of xda)
-Diving in and flashing away without reading and then posting about your problems (Everyone needs to read the Guide.)
NSTools - This is an app that requires superuser permissions. It can be used to control a variety of the phone's features that are unlocked when running a custom kernel. It can enable fast charge, BLN, overclocking, and undervolting. It often comes pre-installed with ICS ROMs.
OC - Overclocking - Computer processors operate at a variety of speeds. When a manufacturer sells a product (like a phone) to the general public, they strictly limit the speed at which the built in processor can operate, even though the processor may be capable of more. This is to promote stability and reliability. Rooted users can overclock their phone's processor, raising the maximum speed at which it can operate. This can be done through various apps, including Voltage Control and NS Tools. Some ROMs even have the controls built into their settings. There are limits, though. Running a processor at too high a speed can cause overheating and/or glitches.
Odin - This is a program of seemingly mysterious origins that allows your home computer to communicate with your phone. You download it to your home computer. Good communication with your phone requires the installation of Samsung drivers on your computer as well as the use of the USB cable that came with your phone. Among other things, Odin can be used to root your phone, install CWM Recovery, install custom ROMs and kernels, and return your phone to stock after you've screwed it up.
*NEVER touch the "Phone" button on Odin. It should be labeled "Destroy your Phone"
OP - Original Post - This refers to the first post in any given thread, the one that started the thread in a discussion forum. A common noob mistake is to hop into a thread on page 27, read for 30 seconds, and then chime in with a question. He is often directed to the OP, which contains the answer to his question.
OTA - Over the Air - These are the official firmware upgrades that Verizon has released over the life of this phone. They were either pushed out to our phones in the middle of the night or offered up for us to download at our convenience. The latest one, EH03, came in December of 2011. Generally speaking, rooted users do not receive OTA updates. Also generally speaking, this doesn't really matter. The updates can be found on xda, and it is unlikely that the Fascinate will ever receive another OTA update.
Patch - This generally refers to a zip file that can be flashed using CWM. The file usually contains updates or small modifications to an existing ROM or kernel. A great example is the patch that reprograms the phone dialer's voicemail button to open Google Voice instead of the standard voicemail or Visual Voice Mail.
PDA Button - This is the button you will want to use when using the Odin program. You should always avoid the "Phone" button.
Pit file - This is a type of file used with Odin when returning your phone to stock. There is a "Pit" button on Odin you can push to enter the pit file you wish to use. An example of a pit file that you will probably use is Atlas_v2.2.pit. To return to stock, you would use a pit file along with a stock ROM, putting both into Odin at the same time. Droidstyle's guide provides detailed instructions.
Project Butter - This is a Google initiative, launched with Jelly Bean, aimed at reducing phone lag, both real and perceived. It involves research into human visual perception, the pairing of GPU and CPU, graphics buffering, and so on. It's purpose is to make your Android phone run "like buttah."
Radio - a.k.a. Modem - This generally refers to the software that manages the phone's connection to the outside world, not the physical device itself. Verizon would release new versions of this software from time to time in their OTA updates. The two most popular ones are currently EH03 (the latest) and EC09. Both of these work with Android 2.3 and the various Android 4.0 ROMs. The choice of radio can determine your 3g download speeds. It's difficult to say that one is better than another. Different users find good results with each one. Both radios are available as zip files that can be flashed in CWM.
Recovery - Your phone comes with a recovery program. You have to choose to boot it up as an alternative to booting up your phone's normal touchscreen interface. An ordinary phone user would probably never even see this program. It's not pretty. It's just functional. It is basically a list of commands and technical terms that you can navigate using the phone's softkeys, volume up & down buttons, and the power button (to select). Essential to rooting are the special recovery programs such as CWM Recovery. A special recovery program, which is flashed via Odin, will replace the stock recovery program for a rooted user.
Re-Partition - This is one of the check boxes in Odin. This box should be checked only when returning your phone to stock. Of Odin's various check boxes, this is the only one for which widespread agreement of its use exists.
ROM - This is one of the two main components (kernel being the other) of the software running on an android phone. It generally determines the overall appearance of your phone, including which apps are installed by default. The ROM that comes installed on your phone right out of the box is known as the stock ROM. Created by devs, there are numerous custom ROMs available for the Fascinate. Popular ROMs a newly rooted user might try are Superclean3, PWGB, and GeeWiz. The process of flashing a custom ROM to your phone will, generally speaking, erase everything on your phone. The most popular ROM for the Fascinate right now is probably the AOKP version of ICS.
Root - When you buy your phone from Verizon, Verizon still controls it. You are simply a user who is allowed to perform various Verizon-approved activities on it. Gaining root access to your phone grants you the control that Verizon had previously held. Rooting quite literally makes you the "Superuser," opening numerous possibilities for improvement, customization, and ruin. Root access is essential to having a fast, fully customized phone.
Root Explorer - This is an app downloadable from the Android Marketplace (Google Play). As it requires Superuser permissions, it is only functional for rooted users. Its abilities far exceed those of standard file management apps. For example, Root Explorer can copy .apk files directly into the system/apps folder in Android. It's a great way to get that obscure Samsung widget reinstalled on your phone after your favorite developer's ROM washed it away and called it bloat.
Samsung Drivers - This is a small piece of downloadable software that will need to be installed on your home computer before it will be able to communicate with your phone (via Odin or adb).
Skin - This is a program that a phone manufacturer creates with the goal of making its phones more user friendly. It is basically an interface that sits on top of the pure Android guts underneath, hence the term "skin." The skin that comes with Samsung phones is called TouchWiz. This is why our phones don't look quite the same as our friends' HTC or Motorola phones, even though they are all using Android. Some people love TouchWiz. Some people hate it. Some custom ROMs are designed to be used with TouchWiz. Others are designed to be rid of it.
SOD - Sleep of Death - This is when your phone goes into standby mode but then goes into a catatonic state somewhere between being asleep and completely powered down. Users report various degrees of SOD. Some ROMs and kernels have been associated with it, as have certain apps, certain radios, and certain SD cards. Experimenting with fringe OC/UV and didle settings are often responsible these days. Generally, a battery pull (or better, Volume Up + Power) will revive the phone. Once a phone experiences a SOD, it seems likely that it will happen again, so a fix will need to be instituted. A modification of OC/UV settings or a return to stock and clean installation of your ROM, kernel, and apps are recommended.
Superuser - A rooted phone will have a new icon in the list of apps called Superuser. This is what distinguishes a rooted phone from a non-rooted phone. There are numerous apps available on the web and Android Marketplace (Google Play) that require "Superuser permission" to do what they do. Common examples of these apps include NS Tools, Titanium Backup, Root Explorer, Voodoo Sound, NS Tools, and Voltage Control. When a rooted user first runs one of these special apps, the app will ask for Superuser permission. Since you are now the Superuser, you get to press the button that says allow or one that says deny.
S Voice - Korean Siri, courtesy of Samsung.
Swype Beta - One of the early perks of rooting, the latest version of Swype is not available to unrooted users because the Fascinate comes with a special pre-installed (and perhaps outdated) version of Swype. Upgrading gives a slicker version of Swype with a more advanced word selection logic. You must follow a few steps to do it correctly:
1. Change the input method to the Android keyboard (settings->language & keyboard).
2. Uninstall Swype using Titanium Backup.
3. Go to the Swype website, give them your email address, and then follow their lead.
*ICS ROMs don't contain any traces of Swype, so steps 1 and 2 can be skipped for them
.tar - This is the file extension for the files that get flashed via Odin. The file to install CWM, for example, is a .tar file. Another example is the file that returns your phone back to stock.
TB - TiBu - Titanium Backup - This is an app available on the Android Marketplace (Google Play). It is for rooted users only, and it requires Superuser permissions to operate normally. Its two main functions are:
1. Creating backups of your phone (or parts of it) in case you screw it up
2. Freezing or uninstalling apps and other stuff you don't want (i.e. debloating)
Thanks button - Once you have created an established account at xda and made a post or two, you will begin to see a button with a little thumbs up sign next to the word "Thanks." This can be found on the lower right corner of someone's post. Pushing this button lets the person who posted know that their work is appreciated. It is considered polite to thank anyone who has helped you, whether or not it was in direct response to your own question. It is always polite to thank the devs whose software you are using. Xda tallies these thanks and gives experienced users a quantifiable measure of their contributions to the community. You will see a thanks meter under other users' names. Helpful people and prolific devs can have hundreds or thousands of thanks.
Troll - This describes a person who attempts to transform a civil forum discussion into a battle of harsh words. They generally lure people into a massive argument by posting inflammatory remarks that are just slightly off topic. They then sit back and laugh to themselves as the argument develops into the nerd equivalent of a bar fight. To feed a troll and make him stronger, just respond to him. To weaken him, report his posts to moderators.
TW - TouchWiz - see "Skin"
TWRP - TeamWin Recovery Project - This is an alternative to the traditional recovery program. Rather than using the volume rocker, softkeys, and power button to interact with it, a touchscreen interface is used. While it offers some interesting potential, it is still under development in terms of compatibility with the Fascinate and our popular ROM/kernel setups.
UV - Undervolting - This is a means of attempting to reduce battery consumption when using custom kernels. Rooted users can accomplish this through one of several apps, with Voltage Control and NS Tools being common examples. The point of whether UV reduces battery consumption is highly contentious, but there does seem to be a theoretical basis for its validity, as well as a preponderance of anecdotal evidence.
Voltage Control - This is an app available on the Android Marketplace (Google Play). It requires root access (i.e. Superuser permissions). When used with compatible kernels, it allows you to overclock and undervolt your phone.
Voodoo - Project Voodoo is a collaborative software development effort started by dev supercurio back when Galaxy S phones first hit the market. Its goal was to optimize the Galaxy S, bringing it up to its full potential. Voodoo innovations have been used by countless rooted users. Voodoo features can only be used on compatible custom kernels. The project consists of three main branches:
1. Voodoo Color - optimizes screen images/video *Not really available in most modern Fascinate setups, but people still talk about how they miss it.
2. Voodoo Sound - optimizes sound quality for audiophiles *The Voodoo Sound app is available from the Marketplace (Google Play) to control settings.
Wipe x3 - This term refers to the act of wiping the slate clean on your phone. It removes all apps you have installed and any data associated with those apps. It will not erase Android, your ROM, your kernel, or anything on your sd card (your photos and videos are on your sd card by default). The Wipe x3 is often done before making major changes to your phone's system. The process is accomplished through a recovery program such as CWM. Here are the 3 commands (hence the "x3"):
1. wipe data/factory reset
2. wipe cache partition
3. wipe dalvik cache
*Note, performing a wipe data/factory reset will reportedly wipe the cache partition and the dalvik cache, so steps 2 & 3 may be redundant.
zip - For our purposes, this refers to the file type for files that can be flashed with CWM or other recovery programs.
*Credit goes to Jawman27 for a great glossary! I just edited a bit for the gs3!
did this man just collect the $1000 bounty?
Sent from my SGH-T999 using xda app-developers app
lol I wish I was that intelligent. This is merely just a guide of whats already posted in the dev section, just consolidated into one thread. I made a guide like this for the SCH-I500 Fascinate and was very popular because all the files and steps needed are in the op... No need to search for anything!!! Its pretty basic now, but once development takes off it should be benificial to new android users...should also help keep the bricks to a minimum.
This will definitely be useful to us first time Samsung peeps who haven't used Odin before. Thank you for taking the time to put this together!
Sent from my ADR6425LVW using Tapatalk 2
Marcismo55 said:
This will definitely be useful to us first time Samsung peeps who haven't used Odin before. Thank you for taking the time to put this together!
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Glad you like! Now all we need is for development to get rollin and more will be added. All in due time...guess Im a little anxious, since this is the first device that I purchased before actual release date :highfive:
Nice man! I have years of HTC experience behind me, but coming to Sammy is totally new with odin. Definitely using this guide on Thursday
Sent from my ADR6425LVW using xda premium
Do you think you could add the dialer programming codes? I'm coming from a Thunderbolt and was curious if *#*#4636#*#* worked or were there other codes I haven't come across yet?
Thanks for this my first time to a Samsung device coming from HTC gonna wait on rooting till the bootloader issue is resolved but nonetheless added this thread to my favorites list
Sent from my HTC ThunderBolt using xda premium
I have always been hesitant about rooting devices before the 1year Verizon warranty has expired, but I don't think I'll be able to make it that long with this phone. As such, I have two questions for y'all...
1.) Will following the return-to-stock instructions leave me with a device that is indistinguishable from one that had never been rooted at all? Will there be any way to tell that it had been rooted?
2.) While I understand that if you follow directions it's unlikely that you'll brick your device, it is still something that concerns me a little... I have heard that an unlocked bootloader is something that is required for moth methods of recovering from a soft brick. Is this true? If so, I assume that Verizon's bootloader would pose a problem in this regard?
I just want to understand the risks before I jump in. Thanks in advance.
Seems from experience with my phone, enabling root will not force custom screen at boot, installing custom recovery will. Idk if it ups the flash counter though. If you only root and one day revert back, I'd imagine it will be indistinguishable.
Sent from my rooted SCH-I535 using xda premium
Will this trip the counter? Also, is CWM in the first root?
Solar257 said:
Do you think you could add the dialer programming codes? I'm coming from a Thunderbolt and was curious if *#*#4636#*#* worked or were there other codes I haven't come across yet?
Click to expand...
Click to collapse
Ill look into it thx!
No this root method does not trip the counter....yes going back to stock erases all traces of being rooted. Thx to odin this device is damn near unbrickable.
droidstyle said:
No this root method does not trip the counter....yes going back to stock erases all traces of being rooted. Thx to odin this device is damn near unbrickable.
Click to expand...
Click to collapse
thanks for the detailed Guide I am sure this will help a lot of people out.
Section 1 updated with new root.img
Updated!! Consolidated the three sections into one and added section 2 for Recoveries.
Sorry if this is a total nub question:
Will flashing this cause my current data to be wiped?
I just got the phone how I like it, not complaining cause root>most things I can stock but I wanna plan for it just in case my apps/settings/contacts/etc. go bye bye.
voted to counter the trolls who think its funny to 1 star threads.
I made a clean ROM based on the factory ROM for the Lenovo A789, A660 and P700i
Cleaned up ROMs:
- A789_S227_cybermaus_V2 (below)
- A789_S228_cybermaus_V2.1 (further below)
Ported ROMs (ported from P700i):
- A789_ROW_S105_cybermaus_ICS_V3 (further below)
- A789_ROW_S106_cybermaus_ICS_V3.1 (Further below)(also for A660 and P700i)
- A789_ROW_S107_cybermaus_ICS_V3.2 (Further below)(also for A660 and P700i)
The current and advised rom to use is A789_ROW_S106_cybermaus_ICS_V3.21
Based on factory ROM A789_S227_120827, and located in my Dev-Host. It is as close to factory as possible, which I hope will be good for stability. It is a flash-utility ROM, because it also holds the latest preloader, uboot and recovery. Assuming those are OK, followup fixes will be update.zip style.
Summery of changes:
- Rooted the phone with Chainfire SuperSu
- Set to boot in US-english, changed name of ROM
- Added MoreLocale for extra languages in 3rd party apps
- Removed Chinese apps, incl Chinese keyboard, removed SmsReg.apk
- Left Lenovo Security (anti-malware) and Lenovo (Go) Launcher intact
- Added Google GAPPS, Play Store, Maps, etc
- Added MobileUncle toolbox, SManager (root explorer). Titanium backup (free version)
- Added fix for location services
- Added CWMT recovery image (modded from 593cn.com)
- Added Skype, Whatsapp, and some others, as auto-install into userdata upon wipe
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Replaced bootup animation with clean Lenovo butterfly
- Replaced all some audio files with english named ones (thanks mabuc)
- Caller ID bug still present, sorry
- Just as a reminder, these ROMS have English and Chinese only.
Instructions:
By default, the ROM will not overwrite USERDATA or FAT. If you want a clean slate, first extract empty.userdata.rar and/or empty.fat.rar
- Read bgcngm flash tutorial.
- Read it again
- Start Flash Tool (v3.1222, in my Dev-Host)
- Load scatter file
- Take out USB cable and replace battery
- Press the download button in the flash tool
- Connect the USB cable
- Wait for the flashing to complete
A789_S228_cybermaus_V2.1 (no longer current, Use V3 instead)
Based on factory ROM A789_S228_120913, and located in my Dev-Host. Similar to V2, but newer, and a few extra fixes. It should be noted that the S228 is listed to solve unexpected crashes, so an important update in itself.
I do not have a A789, so it is a blind build. Until I get positive feedback, consider untested. Don't be the first to try if you are not experienced.
Summery of changes:
- Same as on V2, and additional
- Removed 2 more chinese apps that I forgot last time
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Added a tweak so USB-Debug notification is no longer shown
- Added a tweak so Wifi works on all 14 international channels (rather than only the 11 US ones, may be undone if you set a different locale)
Instructions:
This is a update.zip type ROM. So you need the custom recovery, see post #3,
A789_ROW_S105_cybermaus_ICS_v3.03
Based on P700i_ROW_S105_120920, see this separate post.
A789_ROW_S106_cybermaus_ICS_v3.11
Based on P700i_ROW_S106_121001, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
A789_ROW_S107_cybermaus_ICS_v3.2
Based on P700i_ROW_S107_121221, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
Below:
Post #2: Small review and fix of location services
Post #3: Custom recovery image
Post #4: Root your phone / install GAPPS
Also, many issues for the A789 are similar to those of the A750, so if you have questions, do search that Lenovo A750 thread to.
Thanks
Also thanks to bgcngm for his help, and to jazzor for his help
=================
BTW: Due to new forum rules, resulting in a large number of people that cannot post into developer threads and that subsequently PM me, I open op a new Q&A thread.
I am not going to be policing, so you can post where you like, but I invite everyone to use this new thread for any Q&A, and this thread for ROM releases and deep development talk only.
Consequently, if you PM'ed me, look for your reply in this new thread
Thanks
====================
PS: do drop me a reply if you use or tried it! Or press the 'thanks' button.
So, I got my first glimps at the A789. So to speak. My colleague was holding it while we were audio-skype, so I did not actually see it.
His A789 came with a Etotalk ROM by Dean, which I now suspect is a reworked Smileyvvv ROM with Sony Experia interface. Not bad, but as you know, I am a 'factory ROM' guy. My colleague may also be, because he had already replaced the the SE launcher with GO Launcher, which is the default Lenovo one. Also my colleague said it jammed a few times, which it still has not done on my factory A750 ROM.
Most of the phone worked, but a few tips for others out there:
- The phone still has the Called-ID bug. Even though it is newer 4.0,4. I know some of you claim this is solved on ICS Mediatek, but I still claim it is solved in *some* of the cases, not all, it also depends on how your provider sends the caller ID info. Anyway, you can work around it with the prefixer app as reported before.
- It did not come with the MobileUncle tool, but with the Etotalk tool. Which was not updated for the new MT6577 chip, so it had no Engineer Mode. Install the latest MU tool (version 20120813v2.2.0 its in my Dev-Host), so you get one with MT6577 Engineer mode.
- Recovery Mode was hard to get into. Like the newest A750 preloader, you have to press the power putton *just before* you press both volume buttons. But it did came with the CWMR Touch, though its Touch function was broken, so buttons only. They probably simply tried recovery images of other models, and did not properly build one with the A789 kernel, but it does not matter, it works well enough.
- Location services did not work. Update the phone with the ICS_locationfix_v1.3 update using recovery mode. While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Lenovo A789 Recovery
I created a recovery image for the Lenovo A789 based on ClockWorkMod Touch 5.5.0.4. However, I do not own a A789, so until I have reports of it working, consider it untested. You can download it from my Dev-Host: File A789_S22x_recovery_cybermaus.rar
NOTE: It has come to my attention this recovery works well, except the nandroid backup function, which is broken. If you value nandroid backup, install the APKHOT one below.
While doing this, I also found a full APKHOT distro which had what seems to be a CLockWorkMod (non-Touch) recovery in it, so I extracted that and also uploaded it. That too you can download from my Dev-Host: File A789_S22x_recovery_apkhot.rar
Both of them you will have to flash using the flash tool, using bgcngm's excellent manual, and the V3.1222 of the flash utilities and drivers, also in my Dev-Host. If you flashed my V2 ROM, you do not need to do this, as the recovery is already part of that.
Once you have the recovery installed, you can enter it by pressing both VolumeUp/Down while booting the phone. Due to an issue with the preloader, it may be needed to press the power button slightly before both volume buttons. If the phone seems stuck, it means the preloader messed up, remove battery and try again.
Inside the recovery (the Touch variant) you can navigate not only by its physical buttons, but also by screen buttons, and by gestures: swipe up/down for up/down, left for back and right for enter.
The first few people using this, please report your findings, good or bad.
PS: As alwasy, thanks to bgcngm for his unpack utilities, which I used to modify the recovery.img
Lenovo A789 Root; GAPPS, Location DIY
Its been mentioned before, but if you have a working recovery (like above, hopefully), you can always yourself root your phone. Simply install (from inside the recovery) chainfire's "CMW installable ZIP"
Link to his post: (ignore his big red requires root warning)
The file you need is labeled "CWM installable ZIP" at the bottom.
Direct link to the file you need to install via recovery update.zip
And while you are at it: You probably also want to install the latest Google Mobile Services (better known as GAPPS) from CyanogenMod V9:
Explaining wiki from CyanogenMod
The file you need is called gapps-ics-20120429-signed.zip and can be found here
You probably also want to wipe your cache partition after doing this.
To complete this DIY of fixing factory ROM: On Chine phone typically the location services do not work. Update the phone with my A750 V1.3 update using recovery mode. (it works on the A789 because it is a minor update, but *DO NOT* any of the other A750 updates on the A789. I repeat, do *NOT* flash A750 on A789). While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Good luck
PS: If either update.zip refuses to install, remember to turn off the checksum and assert checks in the recovery.
And thanks to Chainfire for his work, and the team at CyanogenMod for theirs.
cybermaus said:
Before I can help, please provide some info:
Can you tell me what ROM you have?
Which flash tools did you use to root?
Also, do you have a working recovery?
Click to expand...
Click to collapse
hwonggc said:
I fix the proximity thingy. it's caused by my lousy screen protector. But i've got another bigger problem now. I've accidentally uninstalled the default system home screen. I cant assess anything now. I tried flashing a recovery inside but it still doesn't work as factory. I use SP flash tool v3.1.222.00
---------- Post added at 06:32 AM ---------- Previous post was at 06:18 AM ----------
dont think my recovery is working. Could you please provide me with a working recovery? =(
Click to expand...
Click to collapse
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my Dev-Host. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
EDIT: @ hwonggc : Please test recovery in post#3. Just update your post below with results, or PM me. I would like to avoid too many new posts on this while we are testing.
cybermaus said:
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my 4Shared. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
Click to expand...
Click to collapse
Yes yes. I had the factory rom. I got the phone just yesterday evening and this afternoon it's half dead already. I use smart phone flash tool to root using a file i got from http://www.fight.org.ua/publications...novo_A789.html. Everything was fine until I deleted the original home UI and the apex launcher also. So there isn't anything I can do. I'm downloading the S223 from some russian site and try, hopefully I can find some luck there. Downloading slowly~ sighhhh.
---------- Post added at 07:49 AM ---------- Previous post was at 07:40 AM ----------
BTW~ i'm willing to test out your rom too! I wouldn't want to sound too demanding, put please please put in the play store will ya?
I posted the custom build, see first post. It may take a while before I can get it uploaded, I am on a bad link.
Also, there have been 20 downloads on the recovery image. Come on guys, someone must be able to provide feedback about it working or not!
A789_S227_cybermaus_V2 ROM is working
Hello
Thanks for Your work.
Your A789_S227_cybermaus_V2 ROM is working.
Simple Flashing and start without problems. Now I must check some functions.
Thx again
basell
Edit:
The 3g connections don't work at first run. After restore they start but in My opinion with less sensitivity (compare to stock rom). It's look like A789 loose some frequency on witch can work.
Edit2:
And they have some strange behavior - After couple min of data connection (on 3G) they disconnect with information - "Restricted access changed" and the same is when I try to choose network manually. After that sometimes they login to 3G sometimes they change to EDGE.
In Stock version (S221) was not this kind of problems.
Edit3:
In place with good 3G signal I have no problem with data transfer.
How Can I check on witch frequency (2100,900,850) I have connected My data transfer?
Thanks for testing
Well, I definitely did not mess with any of the 3G stuff. So if it is true that 3G is less sensitive, then I would claim it is true for the factory S227 vs factory S221, and not directly related to my cleanup of it.
But (sorry to say so) I have learned to take claims of improved or degraded radio sensitivity with a grain of salt, even for the factory ones.
Having said that: Restoring S221 radio into S227 firmware is easy. The radio is separate firmware file, and I can extract the S221, S223 and S227 firmware in a separate file, so you can test. Were you actually using factory S221, or some other?
As to whether it is using 2100, 900 or 850: I can probably figure out how to get that info, *BUT* reality is that your provider most likely has only one frequency anyway. Most, pretty much all, EU providers are on 2100. The phone could not get to 900, simply because your provider does not have that frequency in the air (not for 3G anyway). And 850 is not supported at all on this phone.
Anyway, inside MU utility, engineer mode, bandmode, you can check/set the frequencies that are supported.
But please run a proper test if 3G is really degraded. As stated. it is so often a empty claim, I am somewhat careful to follow it. You want me to extract the 3 versions of firmware files in update.zip files?
Also, what country/vendor are you? please list the MMC and MNC from inside the APN settings.
Hi
If You will prepare this files I can test it tomorrow.
I'm from Poland and I have two frequency on data transfer - 2100 and 900. But I don't know if A789 use only one or change them. The place I'm test the signal is poor and I don't see if I work on 2100 or 900.
If You can, pleas tell me what kind of tests I can do to do that properly
Ok, here they are. update.zip type.
I only have S221 and S227, but the firmware files were indeed different, in more than just their timestamps. Of course, normally I would assume newer is better. So to make it clear: below files only replace the radio&dsp firmware, not the phone firmware.
Try to test honestly for yourself. Same conditions, same place, same time (because network load can make a difference)
It is possible that 3G really is degraded in S227, but as mentioned, I learned to not jump to conclusions just because the network is having a bad day.
WARNING: I retracted the two attachment, because I made a typo in the installer script. While the firmware is for the A789 (MT6577), the installer script is for the A750 (MT6575). Sorry. I will upload the correct ones in a moment.... Anyone that took a copy of these files before Oct 14, delete them!!!
I suspect the install would simply have failed, no harm done, but best to get rid of all copies anyway
BTW: basell, is that why you asked how to install? Really, if you ask for help, you should provide a bit more info. Anyway, I attached newer scripts, if you still want to try.
sorry for My question but :
How to install this firmware?
Like any update.zip on android. Go into recovery (see post #3) and apply the update.zip
i have the problem that the netlocation doesn't work with google maps, i flashed the cyber update 1.3, nothing changed, what should I do now?
And this is on what phone and ROM?
Anyway, to quote myself: "While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work."
many thanks, Cybermaus, netlocation works again after your instruction
Hi,
Thank you very much for building the ROM !!
I am using it for 3 days now and I am happy to report no problems with it. Everything works and most important: no more freezes !!!
my A789 came with the Etotalk by Dean ROM which was mostly OK, but was freezing from time to time (some days not at all, other days several times a day - most of the times when hanging up a call or, when trying to do wake it from standby: I was pressing the power button, but the screen would not light up).
Other things I like about this ROM:
- all phone functions work great
- Google Play works perfectly
- is rooted
- it has the Lenovo battery app, which is great! I am not 100% sure if this is the reason, but the battery life went from 1 day to 2 days
- I had no issues flashing it
- CWMT recovery works
Also, so far, I did not experience any 3G issues
I have written a small review of the Lenovo Security app, which you guys may want to put back on your phone if it was cooked out of it.
jman0 said:
Thinking it twice, I've remembered another reason. One of the things I like most about the apkhot rom I'm using is that the external sdcard is mounted on /sdcard and not /mnt/sdcard2, which avoids problems with many apps. I tried one of the newest apkhot roms, based on s227, and none of the tricks to exchange /sdcard and /mnt/sdcard2 worked with it.
Click to expand...
Click to collapse
Well, that is actually an easy change to perform, just change the /etc/fstab.vold
However, if you go into settings->storage, the first option is default write disk. Change it from USB storage(the internal SD) to SD (the external SD)
So no hacking is needed at all.....
I've been running your rom for around 6 hours now. Everything runs fine. The 3G connection worked without much trouble. The only thing I haven't been able to do is performing a backup with the CWM Touch Recovery. So, I've just flashed the recovery I had on the apkhot rom I was using, using Mobileuncle tools, and now I've been able to create a backup.
So far, so good, and I've noticed a slight performance increase, too.
Custom ROM Manager finds all the ROMs, GApps and other zip files that are downloaded on your device, lets you install or manage them easily. It also helps you visit official sites of some ROMs/GApps from where you can download them or see changelog.
NOTE: This app does not search the internet for ROMs, GApps and other mods for your device. You have to download them from their respective sites yourself to your device. Then this app will take care of the rest.
Screenshots
Check screenshots tab
Key Features
Finds all the zip files on your device - Custom ROM Manager features multiple file searching algorithms to find the zip files on your device. They are fast, customizable or both fast and customizable at the same time. Users can even choose their file searching technique to their liking.
Sorting and grouping of zip files - After zip files have been found, app sorts and groups them to their appropriate category, like detects which of them are ROMs, GApps etc. It can even detect the properties of a ROM/GApp, like their build dates, version, whether or not they are OFFICIAL builds and what not. The techniques used are efficient and smart.
Popular ROMs/GApps - The app shows list of popular ROMs/GApps. They are selected based on observations of the most popular and most user responded ROM threads across the XDA forums for top devices, and they are listed alphabetically in the app. App is also capable of detecting other ROMs, which will be listed in the "Other ROMs" category.
Official information for popular ROMs/GApps - For all the popular ROMs/GApps listed, you can even check their official information. Like their official sites, download pages etc. It can even check whether your device is officially supported or not, and depending on this, it will open download page for your device when you visit their download page.
Disclaimer - The app makes use of the information that is already available on the internet. It does not use any unauthorized or confidential data. The links are also opened in an external web browser of user's choice, not in some in-app browser or something like that.
Manage your ROMs/GApps - Under each popular ROM/GApp listing, you can see the builds present on your device listed their. Like all your LineageOS ROMs gets listed under "LineageOS" category. You can view them in any way, view them in sorted order based on their build dates or version, or see only unofficial ROMs, or official ROMs. You can delete them, view them etc.
Install them - And finally, you can select them for flashing/installation. This is arguably the most significant feature of the app. You can choose any number of zips for flashing, you can specify which partitions to be wiped before each zip is flashed. You can modify your selection in any way you want, like re-order your selection, delete any entry and what not. And finally, when you confirm, device will boot into (TWRP) recovery, flashing the zips in the very order you selected.
To see the complete feature list, visit the play store page or XDA Labs page.
Google Plus Community - https://plus.google.com/u/0/communities/109799614948604849024
Requirements
Root Access is must.
If you havent flashed custom ROMs before, this app is not for you.
Only TWRP is supported.
Download
Play Store
XDA Labs
XDA:DevDB Information
Custom ROM Manager, App for all devices (see above for details)
Contributors
corphish
Version Information
Status: Stable
Created 2016-07-22
Last Updated 2019-02-04
Sounds interesting.
I will give it a try when i get home and get my hands on my tablet.
@corphish
Cool
One request.
Can u recognise xpossed framework Zip and modules Zip ?? Like Roms and gapps?? It will be damm helpful for everyone ^~^ just a request
Sent from my sprout4 using XDA Labs
harsh. said:
@corphish
Cool
One request.
Can u recognise xpossed framework Zip and modules Zip ?? Like Roms and gapps?? It will be damm helpful for everyone ^~^ just a request
Click to expand...
Click to collapse
Well I am not much acquainted with Xposed and its modules coz I don't use it, but I remember they are .apk's.
Can you link me to those zip files which you are talking about, so that I can take a look and add it in next update?
http://dl-xda.xposed.info/framework/
This
And sorry I just forgot that modules are apk
And if there is way to get kernels differently, is also welcomed.
And sorry for making so many requests!
:fingers-crossed:
Sent from my sprout4 using XDA Labs
harsh. said:
http://dl-xda.xposed.info/framework/
This
And sorry I just forgot that modules are apk
And if there is way to get kernels differently, is also welcomed.
And sorry for making so many requests!
:fingers-crossed:
Click to expand...
Click to collapse
We will see about xposed.
And custom kernel support is not possible because various devices have various custom kernel, sorting them would be simply not possible..
corphish said:
We will see about xposed.
And custom kernel support is not possible because various devices have various custom kernel, sorting them would be simply not possible..
Click to expand...
Click to collapse
Its 10:30am in morning and I'm already out of thanks(8 are given idk where let me check)
So thank you.
Sent from my sprout4 using XDA Labs
Great app.
Very useful especially for beginners.
But I have 4 main requests that will improve the app :
1_it's really bothering that every time I want to launch the app it scans for zip files, it takes a lot of time especially for the low-end phones and for phones that have large Memory.
Maybe you should make it saves the path of the zips and names and add a refresh button in the AppBar in case we add new zip.
2_Add wipe davlik-cache,
It's really needed when flashing modes.
3_maybe in the future you should add an options to explore the zip and extract some files.
4_add a new layout for backup and restore specific files from system (build.prop_framework-res....etc) or the whole ROM and save it as a flashable zip in case the flashed ROM has bootloop or some problem you can restore it form recovery.
Sorry for asking a lot I know it's the first release and that is a lot to ask.
So far the app works great and the design is simple and beautiful as usual (I know from your previous apps)
Thanks for your hard work
Great app UI and Idea, but on my Nexus 6 XOSP 6.3, It doesnt detect anything. I give the root access and storage permission, but it stays at "uhh,nothing here". And thats really it. Any idea? Is there some folder i need to put my zips in?(like delta uses). Thanks!
Root Wizard said:
Great app UI and Idea, but on my Nexus 6 XOSP 6.3, It doesnt detect anything. I give the root access and storage permission, but it stays at "uhh,nothing here". And thats really it. Any idea? Is there some folder i need to put my zips in?(like delta uses). Thanks!
Click to expand...
Click to collapse
Same with me on my lenovo a7000 cm13 rom
Please reply if you want any logs. The idea is awesome and I will surely be gald to help
Root Wizard said:
Great app UI and Idea, but on my Nexus 6 XOSP 6.3, It doesnt detect anything. I give the root access and storage permission, but it stays at "uhh,nothing here". And thats really it. Any idea? Is there some folder i need to put my zips in?(like delta uses). Thanks!
Click to expand...
Click to collapse
anaandshailu said:
Same with me on my lenovo a7000 cm13 rom
Please reply if you want any logs. The idea is awesome and I will surely be gald to help
Click to expand...
Click to collapse
Sorry for late reply, I was busy in the mean time with M and N bringups for some devices.
In Marshmallow ROMs, there is a problem detecting internal storage, which will be fixed in next update, which will come very soon.
Edit: 1.5 is up, check labs
Update 2.5
With previous update (2.0 and 2.1), app was recoded from scratch, resulting in many optimizations and bug fixes.
For example, with 2.0, came better storage detection logic and faster file scanning algorithm, while 2.1 added more modern UI elements.
With 2.5 comes many of the requested features like Zip scan caching, separate option for dalvik cache, and new features like search, respective logos for popular custom ROMs etc.
Please refer to XDA Labs for full changelog.
And do rate and review .
Version 3.0 was released with many cool features.
- Zip selection for flashing was totally revamped. When you tap a card, it will now flip and you will see various partitions you can wipe. Select any if you want to and then tap the card back, it will flip back and notify that the zip has been selected for flashing. And now you can even update what you want to wipe by tapping one of the already selected card back and re-doing the drill. You can even remove it from the flash queue.
- The UI where you are shown what you are going to flash (i.e flash queue) is also revamped.
- Statistics section is also revamped, now shows total size each class of zip is consuming.
- You can also perform TWRP backup and restore operations from the app.
- Some SU related issues (especially on newer security models) were fixed.
- There are always under the hood performance improvements and cleanups.
And all this feature additions barely saw the app size rising. Do check the new screenshots under screenshots tab.
And btw, Custom ROM Manager was released in Play Store too, few days back.
Free version
Donate Version
I use yunicorn 5530 and I tried to search custom ROM for my device but didn't find anything... Do you guys can help me
A new and major version of 3.1.1 has been released.
Summary:
1. Quick selection for zips/backups for flashing/restoring.
2. Ability to delete files.
3. Completely revamped FlashQueue Interface.
4. Inbuilt troubleshooter.
Detailed changelog : Google+ Post
سامسونج s2
3.3 update
Released 3.3 update yesterday
Detailed changelog - Google+ Post
Version 4.0
Version 4.0 was released recently.
Detailed changelog - https://plus.google.com/u/0/+AvinabaDalal97/posts/Deqcbgpq8nJ
4.3
Version 4.3 was released few days back.
Thread updated.
corphish said:
Version 4.3 was released few days back.
Thread updated.
Click to expand...
Click to collapse
Maybe was i to lazy to find it, but it took already a lot of Time to find the "Custom ROM Manager". How can i add My LIGHT PATCH to the Patch Section of Your Project? I wold like to push Your App by default alongside with My Patch in the Future to use it as kind of OTA Updater. Maybe could You direct Me, or do i even have something new for You? (Checking build.prop for the Patch Version so the App can advise a Update if needed!?)
Would be cool to be Part of that! I'm really looking forward to contribute to it...
BR
ROM Ipioneer Slim 10c v0.1
A light, clean & faster rom!!!
Disclaimer:
/***
* Your warranty is now void (and I'm sure it was void before this process).
* I am not responsible for hard or soft bricked devices, boot loops, dead or corrupt sd cards, strange behavior or you getting a heart attack 'cuz your youtube app is not working properly.
* YOU and only YOU are choosing to make these modifications, do not blame on me.... I will just ignore you.
***/
iPioneer Slim 10c v0.1 is a light, clean and fast custom rom designed for the Lg G Pad X 8.0 (T-Mobile variant only) and it's aim is to become a replacement for the default system of this device.
iPioneer Slim 10c v0.1 it is light because it only takes 519.8Mb of disk space which is a big difference when you compare the 1.2Gb of a stock rom, it is clean because it only contains the essential apps to make it work properly and it is faster because the whole system have been 100% optimized.
iPioneer it have been designed with the User Freedom in mind, it only provides you with the basic OS so you can do what you need to do on top of that.
Features:
Based on stock (10c)
Rooted
Busyboxed
Init.d Support
Extremely debloated (very serious)
Deodexed
Zipaligned
Nova as default launcher
Installation instructions:
Download the rom to your desire location (link to download to the end of this post).
Boot into Twrp recovery and do a standard wipe (factory reset).
Install the downloaded rom .zip.
Reboot the device.
Be patient, is going to take more time than a regular stock rom to boot into the system, at first is going to be stuck at T-Mobile logo but after few seconds is going to enter into App Optimization mode and after that you will be able to setup your system.
Enjoy it.
First things to do after you install this rom:
Add your google account (if you didn't complete that step at the first setup).
Download your favorite app manager (Rom Toolbox, Titanium, etc.).
Freeze the application called App Updates in order to stop the system update beacon for OTA. I removed 3 core apps in order to stop OTAs but it seems to be very integrated with the system, there is no way I can remove it from the rom without breaking the system. This is the most practical way to my knowledge right now.
Optionals things to do after you install this rom:
You can uninstall Nova Launcher if you want as is not part of the system apps, but before you need to install your favorite launcher. If you don't install another launcher and remove Nova you will have a broken system and most likely you'll have to re-flash the rom.
On purpose bugs and missing options:
On purpose bugs are bugs that comes when you remove a functionality from the system but it can not be removed from a third party component, example: LG VPN app it has been removed but the options remains in the Settings of the device and when you tap that option you will provoke a crash event, the way to resolve this is to decode the third party component (very difficult) or reinstall the missing part (in this case the LG VPN app).
iPioneer Slim 0.1 it comes without some apps that can not be removed from the system setting options, this is like that because I believe that these apps are not necessary for all people, if someone need them they can be downloaded/replaced from the Play Store or I will provide a flashable file with these apps so you can install them.
On Purpose bugs (located at settings):
From the Share & Connect menu:
File Sharing that contains BLE and Android Beam doesn't work, package SmartShare it has been removed.
Media Server (DLNA) doesn't work, package SmartShare that also contains SmartShare.MediaServer it has been removed.
Lg Airdrive doesn't work, package LGAirDrive & LGAirDriveSettings were removed.
From More>VPN menu:
LG VPN doesn't work, package VpnClient_LG it has been removed. Basic VPN it works.
From Display menu:
Home screen doesn't work, packages LGHome, HomeSelector, LGHome_Theme_Optimus, com.lge.launcher3, com.lge.launcher2.theme.optimus were removed.
If you need these options to be available on your system just download these app on Play Store if they are available or just wait until I have ready the System Apps flashable zips.
Missing options (located at settings):
Smart Cleaning not present, package LGSpringCleaning it has been removed.
Cloud (cloud integration in settings) not present, package CloudHub (maybe dependant on SmartShare package) it has been removed, please also note that this cloud integration it was integrated on the stock File Manager, so... if you want a full integration of the Cloud service on settings maybe you will have to install the stock File Manager provided by LGFileManager package.
From Backup & reset menu:
LG Backup is not present, packages LGBackupLauncher and LGBackup were removed.
From About tablet menu:
Update Center and its content (App updates & System updates) is not present, packages com.lge.appbox.client (app updates), com.lge.updatecenter & LGUpdateCenter (main menu for updates) were removed.
If you need these options to be available on your system just download these app on Play Store if they are available or just wait until I have ready the System Apps flashable zips.Flashable zip with system apps:
Coming soon when I have a free time.
What to do if you get the OTA notification:
Freeze the app called App Updates with your favorite app manager.
With your favorite file manager go to /cache and delete the update.zip (the downloaded ota).
Tap on Restart & Install button on OTA pop-up, the pop-up it will start counting to 0 in order to restart but your device won't restart because there are 3 core apps removed from this rom plus 1 app that you just disabled (all these 4 app controls the OTA), the notification is just gonna disappear, push recent button and clear the ota pop-up window.
Bugs Report:
If you find a bug in this rom just notify me about that in this thread, please, just use the title as "Bug Report" so I can pay close attention to that, my time is very limited. Thank you.
Feature Request:
If you want a feature to be added into future revisions of this rom just notify me about that in this thread, please, just use the title as "Feature Request" so I can pay close attention to that, my time is very limited. Thank you.
More info:
-------------------------------------
Device: Lg G Pad X 8.0
Model: LGV521
Code Name: b3
Carrier: T-Mobile
Android version: 6.0.1
Security patch level: 2016-07-01
Software version: V52110c
Link: https://www.androidfilehost.com/?fid=385035244224403624
Screenshots:
Default View: (sorry guys, I was not able fix Nova in order to show an organized and clean layout by default).
Default App Drawer: remember this is an extremely debloated rom, only the most basic core apps remains.
Settings view, yes some options are not present, read above about this.
Software info.
Reserved 2...
For some reason this post doesn't show up on ET page: lg-g-padx
Too bad, a lot of people won't be able to see this rom, but I can do nothing.
If someone knows an admin who can fix this issue please make mention of this post to him. I would do it but I don't have the time to.
Thank you.
Some screenshots added on post #2...
How fast does it run compared to the stock rom?
Munns86 said:
How fast does it run compared to the stock rom?
Click to expand...
Click to collapse
How fast it can go is a subjective matter:
It will depend on hardware lifetime span (how you use it and how other people use this tablet).
It will depend how much apps and content you put in it (the more things you download the more slow android is gonna be, this is kind a Swap area).
I did not do a benchmark, when I declared that is faster than a stock rom is because that speed response enhacement it comes based on the Deodex and Zipalign process. It can be or maybe not noticeable to your eyes but based on deodex and zipalign process is for sure that is faster than an odex and not-zipaligned rom.
The best answer is that you need to try it on your own and see the difference.
Sent from my LG-H918 using Tapatalk
Poll added at the beginning (not visible in tapatalk or xda app).
Please only select the apps that you really need or you really think that should comes with the next revision of iPioneer Slim rom.
This will help me to build a better version with features that users needs.
C'mon guys... only 3 users have use the poll...
I need more data background in order to release a new version of the Slim line version (may be the last one).
All V521 users please contribute with this.
Right now I'm testing a new build that it seems to have success stoping ota download and notification & I have removed even more bloat background packages.
As of today I start the syncing process of CyanogenMod for our device, so all I ask is that V521 users vote in the poll so I can build and release what I think it would be the last Slim version (iPioneer Slim 0.2) based on users needs.
Once I start the developtment with CM I will not pay attentions to the Stock & Slim version until I finish with what is gonna become iPioneer CM 13.
Thank you for your attention guys.
BTW: sorry for my english, I try so hard to write all this in a good way. Arriba Mexico Papa!!!
xtremelora said:
C'mon guys... only 3 users have use the poll...
I need more data background in order to release a new version of the Slim line version (may be the last one).
All V521 users please contribute with this.
Right now I'm testing a new build that it seems to have success stoping ota download and notification & I have removed even more bloat background packages.
As of today I start the syncing process of CyanogenMod for our device, so all I ask is that V521 users vote in the poll so I can build and release what I think it would be the last Slim version (iPioneer Slim 0.2) based on users needs.
Once I start the developtment with CM I will not pay attentions to the Stock & Slim version until I finish with what is gonna become iPioneer CM 13.
Thank you for your attention guys.
BTW: sorry for my english, I try so hard to write all this in a good way. Arriba Mexico Papa!!!
Click to expand...
Click to collapse
The reason is that the xda app can't see the vote going on.
Personally, I will be excited to see a cm/aosp custom build, which will sure draw much more attention.
googlephone said:
The reason is that the xda app can't see the vote going on.
Click to expand...
Click to collapse
But it is visible and operable through a normal web browser in android: http://forum.xda-developers.com/lg-...ioneer-slim-0-1-lg-g-pad-x-8-0-t3513030/page1
Or the option LOAD IN BROWSER in xda app and WEB VIEW in tapatalk...
xtremelora said:
But it is visible and operable through a normal web browser in android: http://forum.xda-developers.com/lg-...ioneer-slim-0-1-lg-g-pad-x-8-0-t3513030/page1
Or the option LOAD IN BROWSER in xda app and WEB VIEW in tapatalk...
Click to expand...
Click to collapse
Another reason is not many users are interested enough in a slimmed stock rom. The benefits of a slimmed stock rom may include less system storage usage. But the free uped system storage is not accessible for users to use as data storage anyway. Speedwise, I wouldn't expect noticeable improvement from a slimmed stock rom. As a result, the benefits of a slimmed stock rom is not enough to draw users' attention or interest.
I am a flashholic but I actually not interested in slimmed stock at all because I already have root.
I personally advise you to not spend too much time on modified stock rom.
I appreciate your work and look forward to your future possible cm rom, which I will definitely try it out and will draw many g pad x users here. And don't forget there is a bounty for custom roms like cm.
googlephone said:
Another reason is not many users are interested enough in a slimmed stock rom. The benefits of a slimmed stock rom may include less system storage usage. But the free uped system storage is not accessible for users to use as data storage anyway. Speedwise, I wouldn't expect noticeable improvement from a slimmed stock rom. As a result, the benefits of a slimmed stock rom is not enough to draw users' attention or interest.
I am a flashholic but I actually not interested in slimmed stock at all because I already have root.
I personally advise you to not spend too much time on modified stock rom.
I appreciate your work and look forward to your future possible cm rom, which I will definitely try it out and will draw many g pad x users here. And don't forget there is a bounty for custom roms like cm.
Click to expand...
Click to collapse
You are right about working in a stock version. The reason why I'm doing this is because we all know that CM most of the time has bugs, bluetooh problems, camera issues, data conectivity troubles, etc...
Sooooo, if the version of CM I'm going to compile it results with many bugs there is gonna be the option to go back to stock slimed or stock bloated.
I can build a CM verion but Im not the kind of guy who inverts his time in CODE MODIFICATION, so hopefully the build it comes with no bugs at all or at least no major bugs.
The other alternative is that I can sync, compile and build and one more guys can do the bug fixes.
xtremelora said:
You are right about working in a stock version. The reason why I'm doing this is because we all know that CM most of the time has bugs, bluetooh problems, camera issues, data conectivity troubles, etc...
Sooooo, if the version of CM I'm going to compile it results with many bugs there is gonna be the option to go back to stock slimed or stock bloated.
I can build a CM verion but Im not the kind of guy who inverts his time in CODE MODIFICATION, so hopefully the build it comes with no bugs at all or at least no major bugs.
The other alternative is that I can sync, compile and build and one more guys can do the bug fixes.
Click to expand...
Click to collapse
That would be great! I think if you took a poll most people would prefer a CM build to a slimmed down stock build.
Munns86 said:
That would be great! I think if you took a poll most people would prefer a CM build to a slimmed down stock build.
Click to expand...
Click to collapse
Yeah, I know that. Wish me luck.
Right now I'm stuck trying to get the Blobs for this device and compiling the kernel so I can build the CM recovery, once I have the recovery done I can start compiling CM and start testing.
I'm trying to by pass the kernel (as is not need it right now to build the recovery) but for some reason the system is demanding an standard and working kernel... weird...
But honestly speaking is gonna take lot of time. So be patient guys.
xtremelora said:
Yeah, I know that. Wish me luck.
Right now I'm stuck trying to get the Blobs for this device and compiling the kernel so I can build the CM recovery, once I have the recovery done I can start compiling CM and start testing.
I'm trying to by pass the kernel (as is not need it right now to build the recovery) but for some reason the system is demanding an standard and working kernel... weird...
But honestly speaking is gonna take lot of time. So be patient guys.
Click to expand...
Click to collapse
There is already a TWRP recovery for v521. Why you need to compile cm recovery?
googlephone said:
There is already a TWRP recovery for v521. Why you need to compile cm recovery?
Click to expand...
Click to collapse
Ik, is just a prebuilt because our device doesnt have a device tree or structure already, so making this at first is gonna help me to buil the cm zip.
Is not need it if a device tree already exist but not in this case, just see it like a pretesting of code for this device.
When I try to compile this recovery things are gonna break so you get info of what is missing, what you need, log, etc... So you fix everything you can in this step and then you build the cm.zip in a better way (less issues).
Sent from my LG-H918 using Tapatalk
xtremelora said:
Ik, is just a prebuilt because our device doesnt have a device tree or structure already, so making this at first is gonna help me to buil the cm zip.
Is not need it if a device tree already exist but not in this case, just see it like a pretesting of code for this device.
When I try to compile this recovery things are gonna break so you get info of what is missing, what you need, log, etc... So you fix everything you can in this step and then you build the cm.zip in a better way (less issues).
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
https://github.com/Shabbypenguin/android_device_lge_b3
device tree has been around for a while, it obviously will need some renaming to work for cm source but its a good foundation to start with.
shabbypenguin said:
https://github.com/Shabbypenguin/android_device_lge_b3
device tree has been around for a while, it obviously will need some renaming to work for cm source but its a good foundation to start with.
Click to expand...
Click to collapse
These are your device tree for twrp 4 b3 right?
Let me see if I can work with that, I was almost done building the cm.recovery and fixing some boot.img issues but if I can take your files that would save time.
Did you forked that device tree or u just build it from scratch?
If you forked them, from what device?
I was thinking on pulling the v500 just to figure out some sort of missing info I havent been able to catch from ramdisk.
xtremelora said:
These are your device tree for twrp 4 b3 right?
Let me see if I can work with that, I was almost done building the cm.recovery and fixing some boot.img issues but if I can take your files that would save time.
Did you forked that device tree or u just build it from scratch?
If you forked them, from what device?
I was thinking on pulling the v500 just to figure out some sort of missing info I havent been able to catch from ramdisk.
Click to expand...
Click to collapse
i built it from scratch, id be careful looking too much at the v500, it's a snapdragon 600 SOC which is very old and is a quad core. the 615 in the g pad x is octacore and much newer. even the ramdisk is going to have big differences in how its handled.