Cheers and thanks to Rolo42 for making this original guide for everyone!
-SA
This guide contains soup-to-nuts step-by-step procedures for rooting and/or flashing your Verizon Samsung Galaxy SIII (SCH-I535). If you follow these instructions precisely, everything should work fine. If it doesn't, report precisely what you did and precisely what the outcome was as well as any other relevant information--help us help you.
The usual disclaimer: You are responsible for your actions and the consequences.
Firstand foremost, to get your phone to talk to your PC, you will need the Samsung drivers for Windows:
1. Download: Link
2. Install
3. Reboot
4. Plug your phone into your PC, let it find/configure drivers
5. Test: open Windows Explorer, click on "Computer" to see if your phone is listed as a device; browse it
Rooting
There are two methods to root your phone. The first method involves no flashing and uses Android Debugging Bridge (ADB) to root and install the requisite superuser app. This method does not require clearing caches or resetting and it leaves everything intact.
Method 1 (no flash)
1. Ensure aforementioned Samsung USB drivers are working properly
2. Download Noxious Ninja's DebugFS root tool from here: Link
3a. If you do not have ADB installed (from Android or mini SDK--if you don't know what this is, you haven't installed it; cf. http://androidforums.com/faqs/443072-adb-guide-updated-12-05-2011-a.html), extract DebugFS root tool into its own folder (i.e. "C:\root"); I like 7-zip archive program
3b. If you have already installed ADB or the Android SDK, extract DebugFS root tool into your ADB folder but do not replace any files!
4. Open Windows Explorer, browse to your newly extracted DebugFS folder (i.e. "C:\root")
5. Double-click on "RootDebugfs.bat" and follow the directions
6. After the batch file completes, open the Superuser app; set your options per your preference. You now have root access.
The second method is flashing an already-rooted stock ROM. This method is useful when wiping your phone (to install a new custom ROM perhaps) and for updating your firmware to VRALG1**. Additionally, this method eliminates the "Custom" unlocked lock icon boot screen ("tripwire"). **Update: VRALG7 is current version via OTA; rooted ROM download and procedures are here: Download Verizon Galaxy S3 VRALG7 OTA Update, already rooted and deodexed!
Method 2 (flash)
1. Ensure aforementioned Samsung USB drivers are working properly
2. If you do not have a torrent client installed, download/install one now; I like Tixati
3. Download VRALG1 full firmware from this post: Link
4. Double-click the .torrent file you downloaded in step 3; your torrent client should search/download the ROM (.tar.md5 file)
5. Unplug the phone from the PC and power it off
6. Download, install and run Odin: Link
7. Put the phone in download mode: press and hold volume down, home, and power buttons until the screen displays a prompt
8. Press volume up to continue
9. In Odin, verify the "ID:COM" section shows a COM port (the first rectangle)
10. It doesn't because I forgot to tell you to plug in the phone
11. Plug the phone into the PC
12. Now verify the "ID:COM" section shows a COM port connected
13. Click "PDA" and select the VRALG1 firmware (.tar.md5 file)
14. After Odin verifies MD5 hash, press Start button; if MD5 check failed, delete the file, re-download it and try again. You are now rooted.
15. Optional: Install EZ Recovery from the play store. Flash a custom recovery of your choice (I like TWRP2.2)
16. Reboot into recovery (if you didn't install EZ recovery or don't have an app to reboot into recovery, power off; then hold volume up, home, and power keys to boot into recovery)
17. Clear cache and Dalvik cache.
18. Reboot & enjoy! NOTE: The first boot after any wipe takes a long time; be patient.
Unlocking the Bootloader
Unlocking the bootloader does three things:
- Enables you to flash custom kernels without kexec workarounds
- Clears the "Custom" unlocked padlock notification on boot
- Decreases boot time since it no longer performs security checks
NOTE: This is not required for either rooting or flashing a kexec kernel/ROM or the aforementioned VRALG1 ROM in Method 2.
1. If you do not have root access, root your phone per above procedure
2. Install EZ-Unlock app from the Playstore: Link
3. Run the app, press the Unlock button
4. Reboot to ensure all is well!
- Built off Stock ROM (USB Kies and everything else works from stock)
- Jelly Bean Boot Animations
- Google Now
- Speed tweaks for WiFi
- Power saving features
- Graphic acceleration for your photos/videos
- Deodexed/Zipaligned
- SuperSU
- More coming soon! (Let me know what you really want!)
- I left all bloatware on for now (slowly removing one by one, please tell me which one you think absolutely isn’t needed)
*Based Off A System Dump Provided to me by invisiblek of the latest OTA
*100% Deodexed including SMS app and Visual Voicemail. Access you SMS app from the lockscreen again.
*Rooted with latest Superuser.apk and SU Binary. Also Latest busybox installed.
*100% Zipaligned
*Only thing removed is the guide videos as that saved 80MB and I doubt anybody even knows they exist.
Rooted
Deodexed
Bashed
Busybox
Zip aligned
Extended Reboot Menu
Disabled Scrolling Cache
Disabled Increasing Ringtone
Jelly Bean Animations
Google now
Init.d Support
Speed Tweaks
Ram Optimizations
Build.prop tweaks
Sony Bravia Engine
xLoud
Battery tweaks (Battery should be amazing !!!)
Sd card sped up
Memory optimized
Smooth scrolling tweaks
Touch responsiveness
Gps lock
Custom notification 15 toggles mod
Data speed tweak
White themed systemui ,framework.res
White themed phone and dialer
White themed contacts
White themed notifications and toggles
Fast Smooth Stable
Im sure Im missing some things
-Ziggy / Mr.X kernel coming soon!!
-ICS 4.0.4 - Latest I535VRALG1 Base
-Fully Deodexed, Zipaligned, Busybox, Superuser
-Debloated
-Team Synergy's custom init.d scripts for insane performance
-Blocked Samsung’s "root checker" service (We killed it so well that Device Status shows "Not -available" rather than "Modified")
-EXT4 performance tweaks for moar speed
-Be gone ongoing WiFi connect notification. Nobody likes you. (Won't take effect until after first reboot)
-15 notifcation toggles
-4-in-1 reboot menu
-Jelly Bean Animations
-Fully working Google Now with Jelly Bean voice search and offline dictation
-4x5 Launcher with up to 9 homescreens
-Sony Bravia Engine
-Hold volume to skip tracks when screen is off
-WiFi Tether working right out of the box. Just tap and go. (Note: This refers to the app named -WiFi Tether, not Mobile Hotspot as the latter is a subscription VZW service)
-Customized mounting scripts (see Q&A)
-I9300 boot animations with disabled sound
-4G and WiFi speed tweaks
-Verizon OTAs blocked
-Synergized build.prop
-Unlocked settings for camera, browser, and Find my mobile
-Exchange policy disabled (your IT policy may prohibit this, if so flash this in recovery to get back to stock)
-Fully integrated search (The newer VZW GS3 base removes this thanks to yet another lawsuit from Apple, so we retained the old search)
-Ability to set WiFi transmit power (see Q&A)
-Tons more tweaks and enhancements
Author(s): Euroskank
Home Thread: [CM10][Jellybro] D2VZW Nightly Kangs - xda-developers
ROM Status: Nightly Builds
About: Based on CM10 but incorporates the latest fixes/mods/features/patches/etc that may not have been approved for release in the official CyanogenMod releases
Author(s): Invisiblek
Home Thread: [Rom][Unofficial] JellyBean (CM10) VZW (Updated Nightlies) - xda-developers
ROM Status: Semi Nightly Builds
About: Based on CM10 but incorporates the latest fixes/mods/features/patches/etc that may not have been approved for release in the official CyanogenMod releases. Invisiblek has abandoned nightly builds since CM10 has gone official, but from time to time if a major improvement is made, but not yet approved for official release he will create a build
Kernels
The kernel is low-level software that controls the communication between the operating system and hardware; custom kernels can improve performance.
Unnecessary components removed for lean and fast kernel.
Compiled using latest Linaro compiler with additional optimizations.
Latest Linux updates applied (currently up to 3.0.41).
Ramdisk optimizations.
OC'ed to 1.9Ghz (limited to 1.51Ghz at boot, use an app to change max freq), and all frequencies undervolted
SIO I/O scheduler default
Fast Charge (toggle via the "ffc" script - open terminal, type ffc then enter, plug in phone via USB)
On-demand governor backported from Linux 3.5
InteractiveX V3 - optimized for S3, screen_off_maxfreq sysfs interface (default set to 810Mhz). (Note: I didn't change the name to interactivex in the kernel this time)
Auto-brightness tweak - slightly brighter than stock kernel in some instances where it gets too dark.
Fixed governor switching bug where switching from ondemand to another governor could keep cpu1 offline until you switch back.
Unnecessary components removed for lean and fast kernel.
Compiled using latest Linaro compiler with additional optimizations.
Latest Linux updates applied (currently up to 3.0.41).
Some commits from latest CM10 kernel cherry-picked and merged.
Ramdisk optimizations.
OC'ed to 1.9Ghz (limited to 1.51Ghz at boot, use an app to change max freq), and all frequencies undervolted
SIO I/O scheduler default
Fast Charge (toggle via the "ffc" script - open terminal, type ffc then enter, plug in phone via USB)
On-demand governor backported from Linux 3.5
InteractiveX V3 - optimized for S3, screen_off_maxfreq sysfs interface (default set to 810Mhz). (Note: I didn't change the name to interactivex in the kernel this time)
Auto-brightness tweak - slightly brighter than stock kernel in some instances where it gets too dark.
GPU OC'ed to 480Mhz (credit faux)
Fixed governor switching bug where switching from ondemand to another governor could keep cpu1 offline until you switch back.
The CPU comes clocked at normal Samsung specs of 384MHZ low and 1.5GHZ high. You will need an application like System Tuner or Set CPU to overlcock it. This can also be modified by advanced users in the init.rc but is not recommended or supported. See first two blocks of init.rc for details.
GPU Overclocked at 300/500 MHZ
Under-volted just a few milli-volts to help save battery.
There are no fancy governors or other such things. Its a modified stock kernel, plain and simple.
This kernel should be compatible with any VRAGL1 based ROM such as (of course) CleanROM and Nosympathy's stock rooted base. Good chance it will work well with Team Synergy's ROM too but I have not tested that ROM but its a VRALG1 Based ROM.
If your ROM has non Samsung Boot Animation you will more than likely loose it! This WILL be the case for Synergy ROM!
This kernel will NOT work with any AOSP, AOKP, CM9, CM10, etc based ROMS! If the ROM is not a based on official Verizon VRAGL1 ROM then dont flash this kernel!
ZiggyKernel (TouchWiz)
**Only Available as part of SynergyROM**
It contains the G1 kernel and modems as well--the complete package.
oooo i like! that file should be THE de-facto suggestion for getting root IMO then as i still prefer the ODIN flash to the no-flash method for various reasons
I like it for completely wiping (I mean the Sodom and Gomorrah wipe: formatting everything) and then flashing w/Odin.
I'm glad someone posted it because I didn't have a stock G1 ROM (I don't count NoSympathy's since it triggers the "Custom" boot screen...odd that). I don't know if its hosted anywhere other than torrent (I'll keep seeding it until it is).
I like it for completely wiping (I mean the Sodom and Gomorrah wipe: formatting everything) and then flashing w/Odin.
I'm glad someone posted it because I didn't have a stock G1 ROM (I don't count NoSympathy's since it triggers the "Custom" boot screen...odd that). I don't know if its hosted anywhere other than torrent (I'll keep seeding it until it is).
i think the Custom boot screen is kinda wonky in and of itself...root66 never tripped it for me...except for once i rebooted the phone for something or another and it tripped it...
i didn't know that NoSymp's tripped it as well...ive been running Synergy for a little over a day now and that trips it (as expected)
also...as i suggestion...i would also include CWM in your guide...since it really goes hand in hand with root...personally i suggest for EVERYONE i speak to to use EZ Recovery and always flash CWM 6.0.1.0...
i know there are other options out there (esp Team Win) but i think with Kexec looking more and more like its going to be THE way to seriously mod our phones i personally feel there should be a consensus on the advice being given out...and CWM 6.0.1.0 is the kexec/kernel/auto-flash friendly option
I will expand the guide but I wanted to keep it basic and complete so anyone--especially those who've never done this before--can just follow it and be rooted. (and to cut down on the recurring common questions)
I did notice that the "Custom" screen does not trigger on the next boot but on the second subsequent boot, implying that the trigger occurs sometime after loading and not during bootstrap.
Synergy never triggered "Custom" for me but NoSympathy's did (but Synergy is based off of it!)
Installing the "blueui" using metamorph app (it changes the stock notification toggles to ICS blue) did trigger it on the stock rooted ROM. AFAIK, it just modifies System.apk--but Synergy has an entirely different set of notification toggles (and I assume System.apk).
It makes me wonder if something is indeed broken or not following syntax properly which triggers "Custom".
1.How can I tell if I have ADB or not?
2. What is the real difference between method 1 and 2? (As I am not looking to replace the default ROM that came with the phone)
Last edited by sideout; August 12th, 2012 at 10:37 AM.
I am almost done with the questions. I finished steps 1-12 (Method 2), but here is where I still need some help. (SEE RED)
13. Optional: Install EZ Recovery from the play store. Flash a custom recovery of your choice (I like TWRP2.2)
(Where do I find TWRP2.2?)
(What is a recovery?)
14. Reboot into recovery (if you didn't install EZ recovery or don't have an app to reboot into recovery, power off; then hold volume up, home, and power keys to boot into recovery)
15. Clear cache and Dalvik cache. Enjoy! (the options I have are: Wipe date/factory reset or "wipe cache partition"
I also installed CWM as suggested by Metfanant…what next?
At what point should all apps/pictures/everything be backed up and how?
Last edited by sideout; August 12th, 2012 at 01:47 PM.
It says it is 15.5 KB on my destop it shows this file name: VRALG1-Full.tar.md5.torrent I tried using that Tixati, but Im lost with it. Any advice would be greatly appreciated. Thanks.
The EZ Recovery app lets you flash recovery ROMs: TWRP or CWM
Quote:
Originally Posted by sideout
(What is a recovery?)
That is a part of the ROM you can boot into to perform low-level functions such as clear cache, format, factory reset, create/restore NANDroid backups. Think of it like booting into Windows Recovery Disc.
Quote:
Originally Posted by sideout
(the options I have are: Wipe date/factory reset or "wipe cache partition"
I'm pretty sure (but haven't confirmed yet) that the Dalvik cache is on the /cache partition, so clearing/formatting /cache will also wipe Dalvik
Quote:
Originally Posted by sideout
I also installed CWM as suggested by Metfanant…what next?
At what point should all apps/pictures/everything be backed up and how?
CWM is a recovery ROM; there's no need to install another recovery unless you wish to change it to a different one.
Use CWM (or whichever recovery) to create a NANDroid backup (preferably to an external SD card if you have one installed). These are great for when something goes wrong or for whatever reason, your phone is borked, you can wipe and revert to a known good backup from recovery or from switching between custom ROMs.
I think I have it now....the main concern I have for my sons phone is loosing all the apps/texts/pictures he has on there. He basically wants to keep all of that, just root to get rid of the Verizon apps. I thought that Titanium backup was for that.
It says it is 15.5 KB on my destop it shows this file name: VRALG1-Full.tar.md5.torrent I tried using that Tixati, but Im lost with it. Any advice would be greatly appreciated. Thanks.
Ah! I see. The .torrent file is a torrent file, used by torrent clients to download. Blame Lars Ulrich for making it complicated.
1. Install Tixati (or whichever torrent client you like, Vuze, uTorrent, etc.).
2. Double-click VRALG1-Full.tar.md5.torrent file; your torrent client should begin searching/downloading the ROM.
I'll update the procedure to be more clear/complete.
You have helped a ton....Now I need to get an external SD card.
thats what we are here for...there is a lot of stuff that i don't know...and these are not always the most TECHNICAL forums...so i go to xda or rootzwiki for some of that...
but the reason i still use these forums is they are def the most noob friendly forums there are...i started here and feel that i can help a lot of people like i was helped
I just want to see what the preferred recovery is for loading this one?
IMO the preferred recovery for our phones is CWM 6.0.1.0 because it supports everything you can possibly want to do with our phones including Kexec Kernels...so IMO using anything else just adds one more potential step to the process if you eventually want to start messing with Kexec...
im all about ease of use...and personally CWM 6.0.1.0 does that the best...i really see little to no reason to use anything else
admittedly i dont have ANY personal experience with TWRP other than some basic fact gathering...so i don't know exactly how well it functions with kexec...but i do know how well CWM 6 works with kexec and autoflashing the kernel and its as easy as can be...
Last edited by Metfanant; August 13th, 2012 at 02:17 PM.
I don't know if it is easier w/kexec or not; I haven't tried. I have used CWM, CWM touch and neither even come close to ease of use and functionality of TWRP2.
The thread I linked has a kexec-compatible TWRP img.
OK...I rooted it per Method 2 and wanted to give you feedback for others out there.
1. When I opened ODIN and went to PDA to get the file, once I clicked on it ODIN came up and said "not responding". Don't panic, just let it sit for a few minutes and it will work fine.
2. Once you start the process, sit back and grab a book. It took me about 20 minutes for it to all go through
3. Once done, at the top of ODIN you will see a box that says "RESET". Don't do anything...you can think it is telling you to click it or reset...
4. If you decide to install EZ Recovery, here is a helpful hint. Once it pops up on your phone, swipe to the right to see the instructions. I figured it would be on the main screen and got confused.
The Following User Says Thank You to sideout For This Useful Post:
I don't know if it is easier w/kexec or not; I haven't tried. I have used CWM, CWM touch and neither even come close to ease of use and functionality of TWRP2.
The thread I linked has a kexec-compatible TWRP img.
if Imoseyon uses CWM 6.0.1.0 personally then its good enough for me
Good thing you didn't get too far with the "flashing" section...because that is going to be all FUBAR over the next few days...and prepare for a boatload of "OMG IM BRICKED" posts from people unlocking their bootloaders and crack flashing without reading
Good thing you didn't get too far with the "flashing" section...because that is going to be all FUBAR over the next few days...and prepare for a boatload of "OMG IM BRICKED" posts from people unlocking their bootloaders and crack flashing without reading
Did I miss something? nevermind I don't even know what to do with a unlocked bootloader
Last edited by alexander323bc; August 15th, 2012 at 10:09 PM.
Just took the liberty of trying to help out with this a little bit...feel free to use it or not if you choose...i tried to mimic your chosen format as close as possible
Recovery
Recovery is special bootable partition that is a part of every Android phone. It is designed to allow the repair (or "recovery") of the current installation of Android, or to install official (signed) updates to the phone. In the root world we install a custom version of recovery that allows more control over the users data, and to install customized versions of Android (ROMs) or modifications to the OS (Mods).
There are many methods, and different versions of custom recoveries for our devices, but this forum recommends the following method (must be rooted):
1. Download EZ Recovery for VZW Galaxy S3 (Link)
2. Open EZ-Recovery
3. Allow Superuser access
4. Check Recovery (not Hybrid or Stock)
5. Choose a recovery
- Either CWM 6.0.1.0 or TWRP 2.2.0 are recommended
6. Click Flash
You now have replaced your stock (limited) recovery with a customized version to allow you to install customized ROMs and Mods.
Just trying to help again...as you can guess im bored as hell...figured this could go after we get instructions for flashing in
ROMs
A ROM is a customized version of Android built by a developer. They can be A. Based on pre-existing version of Android or B. Based from Android Source code (AOSP or Android Open Source Project).
Custom ROMs often contain features not found in the version of Android that cones pre-installed on your device, and often strip out some (or all) of the carrier specific apps (commonly known as "bloat") that come pre-installed (such as VZ Navigator).
Here you will find custom ROMs specifically made for the VZW Version of the Samsung Galaxy S III with a breif synopsis of the ROMs features, as well as a link back to the developer's "home thread" because very few developers will be posting their ROMs here directly and you can go to A. Download the ROM and B. Get support straight from the developer.
*The order does not indicate any sort of preference or endorsement by Android Forums or the thread author, I simply started at the XDA Forums and went down the forum in order of threads with most recent post.*
*Download links are not provided on purpose. Many devs like to keep "official" threads for their ROMs to keep things easier for them*
The ROMs (A Work in Progress)
***PLEASE read each specific ROMs instructions for installation! Not all ROMs are created equal, and not all ROMs share the same instructions. For the safety of your phone and your sanity, READ the instructions and TAKE YOUR TIME!***
TouchWiz Based ROMs
Here you will find ROMs based on Samsung's TouchWiz framework. They will include many of the features that you will find in the stock build of Ice Cream Sandwich (ICS) that was factory installed. They will often include additional features, themed appearances, performance tweaks, and the removal of "bloat."
These ROMs are generally more user friendly and easier for people to become accustomed to.
-Ziggy / Mr.X kernel coming soon!!
-ICS 4.0.4 - Latest I535VRALG1 Base
-Fully Deodexed, Zipaligned, Busybox, Superuser
-Debloated
-Team Synergy's custom init.d scripts for insane performance
-Blocked Samsung’s "root checker" service (We killed it so well that Device Status shows "Not -available" rather than "Modified")
-EXT4 performance tweaks for moar speed
-Be gone ongoing WiFi connect notification. Nobody likes you. (Won't take effect until after first reboot)
-15 notifcation toggles
-4-in-1 reboot menu
-Jelly Bean Animations
-Fully working Google Now with Jelly Bean voice search and offline dictation
-4x5 Launcher with up to 9 homescreens
-Sony Bravia Engine
-Hold volume to skip tracks when screen is off
-WiFi Tether working right out of the box. Just tap and go. (Note: This refers to the app named -WiFi Tether, not Mobile Hotspot as the latter is a subscription VZW service)
-Customized mounting scripts (see Q&A)
-I9300 boot animations with disabled sound
-4G and WiFi speed tweaks
-Verizon OTAs blocked
-Synergized build.prop
-Unlocked settings for camera, browser, and Find my mobile
-Exchange policy disabled (your IT policy may prohibit this, if so flash this in recovery to get back to stock)
-Fully integrated search (The newer VZW GS3 base removes this thanks to yet another lawsuit from Apple, so we retained the old search)
-Ability to set WiFi transmit power (see Q&A)
-Tons more tweaks and enhancements
*Based Off A System Dump Provided to me by invisiblek of the latest OTA
*100% Deodexed including SMS app and Visual Voicemail. Access you SMS app from the lockscreen again.
*Rooted with latest Superuser.apk and SU Binary. Also Latest busybox installed.
*100% Zipaligned
*Only thing removed is the guide videos as that saved 80MB and I doubt anybody even knows they exist.
- Built off Stock ROM (USB Kies and everything else works from stock)
- Jelly Bean Boot Animations
- Google Now
- Speed tweaks for WiFi
- Power saving features
- Graphic acceleration for your photos/videos
- Deodexed/Zipaligned
- SuperSU
- More coming soon! (Let me know what you really want!)
- I left all bloatware on for now (slowly removing one by one, please tell me which one you think absolutely isn’t needed)
Rooted
Deodexed
Bashed
Busybox
Zip aligned
Extended Reboot Menu
Disabled Scrolling Cache
Disabled Increasing Ringtone
Jelly Bean Animations
Google now
Init.d Support
Speed Tweaks
Ram Optimizations
Build.prop tweaks
Sony Bravia Engine
xLoud
Battery tweaks (Battery should be amazing !!!)
Sd card sped up
Memory optimized
Smooth scrolling tweaks
Touch responsiveness
Gps lock
Custom notification 15 toggles mod
Data speed tweak
White themed systemui ,framework.res
White themed phone and dialer
White themed contacts
White themed notifications and toggles
Fast Smooth Stable
Im sure Im missing some things
Android Open Source Project (AOSP) Based ROMs
Here you will find ROMs based on Google source code. These ROMs strive to provide an experience close to that found on the Nexus Family of devices. This is commonly known as Vanilla, or simply AOSP.
Some of these ROMs will provide a version of Android built exactly as intended for the Nexus devices, while others will take what Google has done and attempt to improve on it by adding features and performance optimizations.
These ROMs are often in experimental states and are not always in stable form. Take caution when installing these ROMs and pay attention to if they are labeled as "stable builds" or "nightlies" as "nightlies" include the latest changes to the code, and can cause stability issues.
Author(s): Euroskank
Home Thread: [CM10][Jellybro] D2VZW Nightly Kangs - xda-developers
ROM Status: Nightly Builds
About: Based on CM10, but incorporates the latest fixes/mods/features/patches/etc that may not have been approved for release in the official CyanogenMod releases
Author(s): Invisiblek
Home Thread: [Rom][Unofficial] JellyBean (CM10) VZW (Updated Nightlies) - xda-developers
ROM Status: Semi Nightly Builds
About: Based on CM10, but incorporates the latest fixes/mods/features/patches/etc that may not have been approved for release in the official CyanogenMod releases. Invisiblek has abandoned nightly builds since CM10 has gone official, but from time to time if a major improvement is made, but not yet approved for official release he will create a build
We should add guide/links to flashing the radios and kernel separate from the img. I was rooted before LG1 and would rather just flash what I need. I doubt I'm alone.
Metfanant.....great information. Question though, why is CM10 not listed under the ROM's? I am new so I am sure I am missing something.
One more question. Is there a certain sequence to all of this? Here is what I mean. I know you root the phone first, then do you install the ROM, then the NANDROID backup then, then the bootloader?...etc?
THanks
Last edited by sideout; August 23rd, 2012 at 09:05 AM.
First ima Noob.
I rooted with Odin(Fairly sure if this)
I haven't flashed a phone before so if I do, do i really want any updates from VZW if they come out? (Since I'm using a 'better' version of the OS it seems like I won't need to worry about VZW.)
If yes, I will need to flash back to stock before installing VZW update, right?
How do I keep the VZW update from updating?
If I don't want to flash a custom ROM but just remove some bloat wear, where do I read about just doing that?
Can someone refer me to where to read about saving a file for recovery? I have titanium back up but i don't understand where the files are? And I always have a 'didnt back up completely' message in the morning as the schedule is set for 2am.
Uuugh, so much to learn but I'm searching, reading, and watching YouTube vids as I don't want you guys to link me to that noob video I once saw.
i apologize for not seeing some questions since the thread got stickied lol
Quote:
Originally Posted by sideout
Metfanant.....great information. Question though, why is CM10 not listed under the ROM's? I am new so I am sure I am missing something.
CM10 isn't listed because i started with the TouchWiz based ROMs...
i did this for a few reasons
1. they are more user friendly
2. currently there are some issues with AOSP based ROMs that our guide is not quite setup to help with yet...i will however take some time tomorrow and edit my "ROMs" section to include them
Quote:
Originally Posted by sideout
One more question. Is there a certain sequence to all of this? Here is what I mean. I know you root the phone first, then do you install the ROM, then the NANDROID backup then, then the bootloader?...etc?
THanks
ok here is the BASIC order at which you should probably go...id like to get a chance to talk with Rolo about formatting this thread in the best way possible but here goes...
**Now while this is a general rule of thumb that you can follow for any Android phone, always make sure you read directions for specific devices as things can change..but this is the "path" i would send a VZW SGS3 owner on**
1. Root:Many different ways to do this now...i suggest the pre-rooted G1 ODIN Flash because it includes the new baseband as well
2. Recovery: Many ways to do this as well, EZ Recovery is still the easiest
2b. Make a stock Nandroid in case anything goes wrong and you want to get back to stock(i dont make Nandroids and have never used them...but you really should)
3. Unlock Bootloader: many ways to do this, but i suggest the 1-click tool at this point especially for noobs
4. Flash (ROMs, MODs, Kernels etc..)
4b. Make a Nandroid: if everything is working right its nice to have a clean install of your new ROM handy in case anything goes wrong later
Quote:
Originally Posted by Captain Brick
First ima Noob.
I rooted with Odin(Fairly sure if this)
well the program is called ODIN so you cant miss it
Quote:
Originally Posted by Captain Brick
I haven't flashed a phone before so if I do, do i really want any updates from VZW if they come out? (Since I'm using a 'better' version of the OS it seems like I won't need to worry about VZW.)
No, you generally do not want any of the updates from VZW...
ESPECIALLY now that we have our unlocked bootloader...there is a VERY GOOD chance that whenever an OTA comes out for our phones (i would say 99.9% chance with the JB update) that VZW will sneak a new bootloader into the update...its VERY LIKELY that installing said bootloader will completely brick our device..
Quote:
Originally Posted by Captain Brick
If yes, I will need to flash back to stock before installing VZW update, right?
well here is the beauty of being a root user...i have not taken an OTA from VZW since the Froyo update on the Droid X in September of 2010..let me explain...
1. new versions of OS's are often leaked out...developer builds, carrier rejected builds etc...these often find their way into the hands of developers who get them on our phones...
this happened with the Droid X Gingerbread builds like crazy...us rooted users were running OFFICIAL Moto/VZW builds of GB something like 6+ months before it went public
2. official OTA updates ALWAYS go out to soak testers before it goes live...at that time developers will be looking to get copies of the soak test updates from testers...in the case of our phones we will likely get either a pre-rooted ODIN file, or a pre-rooted .zip within a day or two of the soak test starting, and we will have official JellyBean before it goes live
Quote:
Originally Posted by Captain Brick
How do I keep the VZW update from updating?
often custom ROMs have the files needed to even download the OTA removed...so your phone will never know there is an update...
Quote:
Originally Posted by Captain Brick
If I don't want to flash a custom ROM but just remove some bloat wear, where do I read about just doing that?
you can read about it right here..questions that you guys ask make these Guide Threads easier...because we know what to put in the threads...
Quote:
Originally Posted by Captain Brick
Can someone refer me to where to read about saving a file for recovery? I have titanium back up but i don't understand where the files are? And I always have a 'didnt back up completely' message in the morning as the schedule is set for 2am.
recovery and titanium are two different animals...so we need some more info as to what youre trying to accomplish
Quote:
Originally Posted by Captain Brick
Uuugh, so much to learn but I'm searching, reading, and watching YouTube vids as I don't want you guys to link me to that noob video I once saw.
ask away...thats what these threads are for
Edit: added a section to my above post differentiating between the TouchWiz ROMs and the AOSP ROMs...i will start to add the AOSP ROMs tomorrow when i have some time
Edit 2: added a few AOSP ROMs to the list and updated the "home thread" input for the TouchWiz ROMs as well...MUCH more is needed to be explained about the AOSP ROMs and potential risks associated with them, but no fear we will get there!
Last edited by Metfanant; August 24th, 2012 at 04:20 AM.
was bored again...so i got to typing...
Kernels
The kernel is what allows your phone's hardware to communicate with installed software and vice a versa. Because of this many performance increases can be had by installing custom kernels
***only VZW based kernels are currently posted. In theory, with our now unlocked bootloader kernels designed for other variants of our phone should work, but they can introduce problems as well***
Unnecessary components removed for lean and fast kernel.
Compiled using latest Linaro compiler with additional optimizations.
Latest Linux updates applied (currently up to 3.0.41).
Ramdisk optimizations.
OC'ed to 1.9Ghz (limited to 1.51Ghz at boot, use an app to change max freq), and all frequencies undervolted
SIO I/O scheduler default
Fast Charge (toggle via the "ffc" script - open terminal, type ffc then enter, plug in phone via USB)
On-demand governor backported from Linux 3.5
InteractiveX V3 - optimized for S3, screen_off_maxfreq sysfs interface (default set to 810Mhz). (Note: I didn't change the name to interactivex in the kernel this time)
Auto-brightness tweak - slightly brighter than stock kernel in some instances where it gets too dark.
Fixed governor switching bug where switching from ondemand to another governor could keep cpu1 offline until you switch back.
Unnecessary components removed for lean and fast kernel.
Compiled using latest Linaro compiler with additional optimizations.
Latest Linux updates applied (currently up to 3.0.41).
Some commits from latest CM10 kernel cherry-picked and merged.
Ramdisk optimizations.
OC'ed to 1.9Ghz (limited to 1.51Ghz at boot, use an app to change max freq), and all frequencies undervolted
SIO I/O scheduler default
Fast Charge (toggle via the "ffc" script - open terminal, type ffc then enter, plug in phone via USB)
On-demand governor backported from Linux 3.5
InteractiveX V3 - optimized for S3, screen_off_maxfreq sysfs interface (default set to 810Mhz). (Note: I didn't change the name to interactivex in the kernel this time)
Auto-brightness tweak - slightly brighter than stock kernel in some instances where it gets too dark.
GPU OC'ed to 480Mhz (credit faux)
Fixed governor switching bug where switching from ondemand to another governor could keep cpu1 offline until you switch back.
The CPU comes clocked at normal Samsung specs of 384MHZ low and 1.5GHZ high. You will need an application like System Tuner or Set CPU to overlcock it. This can also be modified by advanced users in the init.rc but is not recommended or supported. See first two blocks of init.rc for details.
GPU Overclocked at 300/500 MHZ
Under-volted just a few milli-volts to help save battery.
There are no fancy governors or other such things. Its a modified stock kernel, plain and simple.
This kernel should be compatible with any VRAGL1 based ROM such as (of course) CleanROM and Nosympathy's stock rooted base. Good chance it will work well with Team Synergy's ROM too but I have not tested that ROM but its a VRALG1 Based ROM.
If your ROM has non Samsung Boot Animation you will more than likely loose it! This WILL be the case for Synergy ROM!
This kernel will NOT work with any AOSP, AOKP, CM9, CM10, etc based ROMS! If the ROM is not a based on official Verizon VRAGL1 ROM then dont flash this kernel!
ZiggyKernel (TouchWiz)
**Only Available as part of SynergyROM**
As I read & benefit from/thru the boring life of Mefanant....
(said with a grin)
I ask if there is any issue with matching Kernals to ROM. We have 5 or 6 of each so how does someone know not to use "this" Kernal if you are using "that" ROM?
Edit: I've noticed that some Kernals give a short disclaimer about what it should not be used with. I'm guessing after that matching is trial and error?
Last edited by Captain Brick; August 24th, 2012 at 08:14 AM.
As I read & benefit from/thru the boring life of Mefanant....
(said with a grin)
I ask if there is any issue with matching Kernals to ROM. We have 5 or 6 of each so how does someone know not to use "this" Kernal if you are using "that" ROM?
Edit: I've noticed that some Kernals give a short disclaimer about what it should not be used with. I'm guessing after that matching is trial and error?
never flash an AOSP Kernel with a TW ROM and vice versa
1. Download EZ Recovery for VZW Galaxy S3 (Link)
2. Open EZ-Recovery
3. Allow Superuser access
4. Check Recovery (not Hybrid or Stock)
5. Choose a recovery
- Either CWM 6.0.1.0 or TWRP 2.2.0 are recommended
6. Click Flash
You now have replaced your stock (limited) recovery with a customized version to allow you to install customized ROMs and Mods.
Metfanant, Before I start installing ROMs & Kernals, I'd like to keep a backup of my stock software before the experimenting, although I'll probably just try one or two. It sounds like the EZ Recovery will keep one for me? if not, how do i save one?
For choosing the recovery in step 5, is it an option in the EZ Recovery App or is this something I have to get elsewhere?
It also sounds like I am not using or connected to my PC if I'm going to Play store for the EZ App.
Great help Metantfan...but can you elaborate a little more on the Nandroid backup? You list it twice so just want to make sure I am doing it right.
the second Nandroid is just a backup of the newly installed ROM in a "virgin" state...nice to have in case you mess something up...you dont have to go all the way back to stock...
the second Nandroid is just a backup of the newly installed ROM in a "virgin" state...nice to have in case you mess something up...you dont have to go all the way back to stock...
I went into EZ Recovery and picked the CWM and then hit the REBOOT NOW. Once to the main screen I picked the backup. Is this what's considered as the Nandroid backup?
On a side note, when I go to pick the Synergy ROM...it takes me to a page and I can pick a .zip file or a .zip.md5 file. What's the difference?
Last edited by sideout; August 25th, 2012 at 08:16 PM.