Database Info

[ROM] Hellstra Skitzandroid Telstra-Cyanogen Mod

All,
This rom is a rebuilt version of the latest Telstra AU ROM with GPS fix ( RUU_Bravo_Telstra_WWE_1.16.841.1_Radio_32.30.00.28U_4.05.00.11_release_126124_signed ).
I have removed all of the Telstra crap and added some useful apps. I have deployed it to my unbranded phone and it is working fine.
Changes from the standard ROM include:
- Removed all of the Telstra apps (except whereis... maybe next version )
- Added root access, of course
- Apps2SD included but not functional (you can get it to work by issuing adb commands)
- WiFi Tethering included. Will probably remove from the next version as it's a bit flaky.
- Changed the boot animation to the Nexus One anim
- Some additional apps such as:
3D Gallery
Car Home
Navigator
Voice Dialer
Others I inevitably forgot
To do:
- Figure out how to add APNs to the ROM
- Fix A2SD
Download link is in the next post.
Credit to:
Cyanogen for the Kitchen
Paul OBrien from MoDaCo for making the kitchen available
FeaRThiS for hosting the ROM
Enjoy!

IMPORTANT: READ FIRST
Flashing ROMs in general is a risky business. If you've never flashed a non-standard ROM before, I suggest you read about and understand the method before you even consider downloading this. I take no responsibility for any issues that may be caused by this ROM. Use it at your own risk.
I also suggest you read here and note any known issues and changes for new versions.
You must have a rooted handset to be able to flash this ROM. Head over to MoDaCo, or search XDA for guides on how to root your phone.
To flash this ROM to a rooted handset, follow these instructions:
BEFORE YOU START
Copy the zip file to the root of your SD card.
Method A:
1a) Power on your phone, holding the VOLUME-DOWN button until you see the HBOOT menu
2a) Use the VOLUME buttons to navigate to the "Recovery" option and select it using the POWER button
....continue from step 3 below.
Method B (quicker but requires SDK)
1b) Boot up your phone and connect it to your PC via Micro-USB cable
2b) Execute 'adb reboot recovery' form the tools directory of the Android SDK
....continue from step 3 below.
3) Once you see the red triangle (of death ) connect your phone to your PC using the micro-USB cable
4) Go to the 'pushfiles' folder that came with the root-kit from MoDaCo.
5) Execute ./recovery-linux.sh (Linux), ./recovery-mac.sh (OSX) or recovery-windows.bat (Windows) and wait for the recovery menu to load.
6) Use the TRACKBALL to navigate to the Wipe option. Select Wipe by clicking the optical trackball. Do a System wipe, followed by a cache wilpe and finally a dalvik-cache wipe (each of the first three options). Once complete, press the VOL-DOWN button to return to the main menu.
7) From the main menu select FLASH ZIP FROM SDCARD, select the ROM zip file, confirm flash.
8) Once flashing is complete, select REBOOT from the menu.
9) Enjoy your uncluttered handset
DOWNLOAD HERE:
http://79.170.44.128/r3volutionary....ra-free-skitzandroid-signed_050610_214824.zip
Thanks to FeaRThiS for hosting!
Alternative downloads:
http://uploading.com/files/631d4617/hellstra-free-skitzandroid-signed_050610_214824.zip/
Thanks to lucus30
http://www.deswong.com/android/
Thanks to deswong

Changelog
=======================
Issues:
=======================
- Titanium Backup not working. Its not included in the ROM but just thought I'd mention it It complains about not being able to get root access whereas every other app that requires root access works fine so far. Downloading busybox through TB causes a FC.
- Some people are getting the A2SD infinite boot loop issue (next version will definitely not include A2SD as you can add it yourself if you want it).
You can get out of the loop by doing:
Code:
adb reboot recovery
from the SDK tools folder on your PC to get back to the recovery menu.
You can also do 'adb shell' and then issue the command 'a2sd' from the shell but I wouldn't advise it. It will boot up 'normally' but it's not a permanent fix.
==================
reserved for changelog

Uploading link
http://uploading.com/files/631d4617/hellstra-free-skitzandroid-signed_050610_214824.zip/

Nice one!!
I'm yet to root my phone and WILL get to it in good time.
When I do, I'll give this one a flash.
Thanks for your work.
Death to all the Hellstra visual bloatware scum that crapped up the original ROM (stupid splash screen Tel$tra ding noise especially)

new Link and I have PM'd you all of your FTP details

FeaRThiS said:
new Link and I have PM'd you all of your FTP details
Click to expand...
Click to collapse
Thanks FeaRThiS. Much appreciated!

I've also thrown it on my www as well.
http://www.deswong.com/android/

Hey guys,
Correct me if I'm wrong but for anyone with a Telstra set the problem is 2 fold?
1) we need to be able to Root the phone, Paul's latest 0800 root method will hopefully fix this
2) we need a ROM that incorporates the Telstra GPS fix whilst debloating the phone.
Does that mean that if we want to use GPS we are restricted to ROMs cooked with the GPS fix? or will any generic ROM do the trick (i.e. those from MoDOCO?

I am experiencing the pink AMOLED problem at low brightness and may have to replace the phone with another one. If I root the phone and flash this ROM, can I flash back the original ROM that I downloaded recently from HTC to restore it to the state it was when I bought it?

qubit76 said:
I am experiencing the pink AMBLED problem at low brightness and may have to replace the phone with another one. If I root the phone and flash this ROM, can I flash back the original ROM that I downloaded recently from HTC to restore it to the state it was when I bought it?
Click to expand...
Click to collapse
I dont think so. You could flash the original Telstra one back again but the recovery partition is wiped/messed around with as part of the rooting process. Have a look around Modaco and you'll find your answer - you're definitely not the first to ask.

negatron said:
Hey guys,
Correct me if I'm wrong but for anyone with a Telstra set the problem is 2 fold?
1) we need to be able to Root the phone, Paul's latest 0800 root method will hopefully fix this
2) we need a ROM that incorporates the Telstra GPS fix whilst debloating the phone.
Does that mean that if we want to use GPS we are restricted to ROMs cooked with the GPS fix? or will any generic ROM do the trick (i.e. those from MoDOCO?
Click to expand...
Click to collapse
The GPS issue was a software related bug from the shipped ROM, I read somewhere on here someone mentioning that they flashed the generic ROM and had GPS working before HTC/Telstra released the update

mwong1980 said:
The GPS issue was a software related bug from the shipped ROM, I read somewhere on here someone mentioning that they flashed the generic ROM and had GPS working before HTC/Telstra released the update
Click to expand...
Click to collapse
yeah the new Telstra ROM had the exact same GPS config as my unbranded one so the prolem was caused by Telstra meddling with things.... surprise surprise!

bcmobile said:
I dont think so. You could flash the original Telstra one back again but the recovery partition is wiped/messed around with as part of the rooting process. Have a look around Modaco and you'll find your answer - you're definitely not the first to ask.
Click to expand...
Click to collapse
Cheers bcmobile. So in your opinion am I correct in saying that it's better I wait until the screen problem is worked out (to return under warranty to Telstra from whom I bought it outright) before I go rooting the device?

well tried yrs BC
and now it boots to the htc logo ..and stays there
i've tried twice now.
i can get to recovery mode tho, something wrong with yr image maybe?
note in recovery mode ..down the bottom, it says " Build: not set"

note that i tried yrs after succesffulyy rooting via the latest method from paul, and, applying the radio update. neither got my gps working so i've tried yrs ..
http://android.modaco.com/content-p...h-hboot-0-80-and-os-to-1-21-support/page/340/

qubit76 said:
Cheers bcmobile. So in your opinion am I correct in saying that it's better I wait until the screen problem is worked out (to return under warranty to Telstra from whom I bought it outright) before I go rooting the device?
Click to expand...
Click to collapse
I've used three Desires and they all show the pink on low brightness so returning it under warranty won't help you.

ok, my phones working again, rerooted with pauls method.
but have no gps and i can't flash back to the telstra rom thanks to the radio updating my hboot to .80

same here guys. I rooted using Paul's latest method but gps stopped working. and when flashing this Rom it hangs at the white HTC screen. now back to Paul's rooted Rom. hope we fix the gps issue soon!

mitchello said:
I've used three Desires and they all show the pink on low brightness so returning it under warranty won't help you.
Click to expand...
Click to collapse
Thanks for your feed back. At the risk of hijacking this thread and double posting - My post on the AMOLED sticky.
In summary if you don't want to read my above post, I saw 2 phones 'in store' that did not have the pink issue.

* Definitive guide to Bricking *

- Introduction -
This is a primer on why phones get bricked, how to recover from a brick, and how to prevent bricking your expensive hardware. I wrote this because I noticed the same questions popping up over and over, perhaps due to an instant onset of panic, from people that bricked their phones and there doesn't seem to be a single stickied thread that is dedicated to bricks. Sorry for my inability to be brief, but I would still highly recommend that you read this article in its entirety.
- The Android Boot Process -
In order to get a good understanding of why phones brick, we must have a good understanding of the boot process. All android phones have a similar boot process, so most of this information should be applicable to the i897 and any other Android handset.
So, here is what happens when you press the power button on your phone.
1. BOOT ROM - Your phone waits for the power to stabilize, then runs a piece of code that is stored in permanent rom on your cpu called the Boot Rom. The main job of this code is to detect the boot media and load it into memory (in this case, it is the First Stage Bootloader). This code is hard wired and can never be overwritten.
2. First Stage Bootloader - Once the boot rom loads the boot media, it hands control over to the First Stage Bootloader (you may see this in some roms as boot.bin). The job of this bootloader is basically to "find more ram" and load the second stage bootloader into it. When computers first boot up (even PC's), the default memory model usually only allows for very tiny programs to be loaded into memory. For this reason, there is usually two bootloaders, the first of which detects and sets up external ram and loads the second stage bootloader into it. NOTE: The first stage bootloader can be overwritten! If you damage your bootloader, you will have a permanent UNRECOVERABLE brick at this point!
3. Second Stage Bootloader - The first stage bootloader hands off execution to the Second stage bootloader (you may see this in some roms as sbl.bin) once it is loaded into memory. The job of the SBL is to "set everything up" so the main kernel can take over. It is in charge of setting up the file systems, setting up any additional memory, setting up all the hardware, bringing up the modem cpu and setting any sort of low level security that may need to be set. Fun fact: This is where your 3 button combo and "download mode" is handled. Once the hardware is set up, the sbl will look for the kernel. NOTE: The SBL can also be overwritten, meaning if you damage your SBL, you can lose your ability to boot into download mode and thus have a permanent, unrecoverable brick!
4. Kernel - The kernel, if one were to put it simply, is essentially "the os". I know there is far more to it, especially in the case of Android with Dalvik providing most of the things we typically think of as "Android". But for all intents and purposes, the kernel is the core part of the OS that handles all of the hardware interrupts, memory management, memory protection, manages file systems and drivers, threading and access to the processor, and so forth. Once the kernel is loaded into memory, it sets up anything else that needs to be set up, loads Dalvik, and from there the rest of Android is brought up. Fun fact: This is where recovery resides. NOTE: You can still brick your device at this step, though it is only a soft brick and very recoverable - nothing to lose sleep over.
Now that you have a general understanding of how Android boots, let's move on.
- But my phone is bricked -
You probably arrived at this article because it's too late and you've already botched something. You've probably read through the first part and are thinking "Ok professor, that's all good and well, but my phone is dead. Do I have to shoot myself in the head now?" The short answer is "Maybe."
The most important part of analyzing a brick is to figure out what part of the boot procedure it crapped out on. Fortunately, most of the time this is pretty easy to figure out IF YOU REMEMBER WHAT YOU WERE DOING IMMEDIATELY BEFORE THE BAD THINGS HAPPENED. If you look at the previous section, you'll notice a color coding of the various boot steps.
The reason why bad things happen to good telephones is something bad is happening during the boot process, preventing successive stages from completing. If you were flashing a rom (either through CWM or Odin) that included bootloaders and you saw that it died somewhere around the part where it was flashing boot.bin or sbl.bin, you may have a hard brick. If you think about it, it makes sense logically. It's crapping out at the part (or before) where the code that handles the key combos for download mode is being set up. If you've damaged that part of the process, there aren't really any other (easy) alternatives.
Here is a good barometer for checking if you have a hard brick:: Does something show up on your screen when you press power? (This can literally be anything - error messages, boot loops, naked chicks, that infuriating AT&T logo). If it does, congratulations! You're probably in the orange section of the boot process and can recover your phone. If not, and no matter how many times you mash the power button it stays at a black screen, you probably messed it up somewhere in the red part of the boot process and have a hard brick.
- How to recover from a brick -
If you have a hard brick (Black screen, power button isn't doing anything, multiple battery pulls didn't get you anywhere), you're probably out of luck. Sorry, dude. You can still recover it, but it'll require some surgery on your part.. You'll have to order a riff box (http://www.jtagbox.com/), remove the motherboard, and connect it to the riff box and flash your two bootloaders back onto the rom chips directly. Or, you can just do what everyone else here does and mail it back to Samsung or AT&T, with some story about how kies wrecked your junk and you have no idea wtf.
If you have a soft brick (something shows up on your screen), it's just a matter of getting your phone into recovery or download mode. Basically, when dealing with a soft brick, you want to be as unintrusive as possible to NOT MESS IT UP WORSE THAN YOU ALREADY DID. So here are a few basic procedures.
1. Don't panic.
2. Can you get into recovery?
Pull the battery out.
Put the battery back in!
Press and hold Volume Up, Volume Down, and Power, and wait until something shows up on the screen.
Release power! Keep holding Vol up+Vol down.
Did it go into recovery?
If that worked, try flashing a different kernel from recovery. If it still doesn't work, it's probably not the kernel but something else in the rom, so flash a different rom altogether. NOTE: The key combo for recovery is different with the new 2.3 bootloaders! It is now Vol up+power instead of Vol up+Vol down+Power.
3. If not, boot it into download mode.
Pull the battery out and make sure the phone is NOT connected by a usb cable.
Put the battery back in!
Hold vol up+Vol down. DO NOT PRESS POWER.
Plug in the USB cable.
NOTE: The key combo is different with the new 2.3 bootloaders. It is now Vol down+Power. You no longer need to connect the usb cable.
The phone should boot into download mode. If it still does not, you can try using a USB jig. They are very easy to build - it is just a 301k resistance across pins 4 and 5 of the microusb slot. You can find plenty of instructions by searching the General section. You can also find a usb breakout board here: http://www.sparkfun.com/products/10031 and 100k (make sure it's 100k and not 100) resistors at radio shack. To use the jig, simply pull the battery out, put the jig in the microusb slot, DO NOT TOUCH THE JIG WITH YOUR FINGERS AS YOU MAY CHANGE THE RESISTANCE, and put the battery back in. It should kick you into download mode within 3 seconds.
Once you are in download mode, flash back to stock. Refer to the Odin guide at the end of this article for instructions. ***NOTE***: DO NOT FLASH A ROM THAT INCLUDES BOOTLOADERS - THIS INCLUDES THE ODIN ONE CLICK PACKAGE - IT IS AN UNNECESSARY RISK AS YOUR PHONE ALREADY HAS PROPER WORKING BOOTLOADERS
I actually don't like the one-click package very much in general, simply because there seems to be an element of randomness around it. It seems to work with a certain build of phone, and seems to cause problems with newer phones.
- You may have to flash bootloaders -
So you're probably thinking, "What if I don't have a working 3 button combo?" Someone correct me if I'm wrong, but to my understanding a certain batch of phones were shipped out with corrupt sbl's. If you're one of those unlucky folks that has a phone with a busted 3 button combo, you'll have to flash new bootloaders to fix it. There is a bootloader fix package you can flash somewhere in the dev section, and if I'm not mistaken, the Cognition rom also flashes properly working bootloaders.
You will also have to flash new bootloaders if you want to upgrade from 2.1/2.2 to the official Samsung 2.3 roms (or any custom roms based off of the official 2.3's). Don't try to flash these individually if you happen to find them somewhere. The best way to get the new bootloaders is to download the stock JVB rom from www.samfirmware.com and flash it using Odin3.
Be warned - by flashing bootloaders, you may brick your phone permanently. Remember, you're flashing the red part of the boot process at this point. If things go boom, your phone ends up in an unrecoverable state. The chances of it crapping out while flashing the bootloaders may be a million to one, but there's still a chance it might happen and I've seen people brick their phone from this several times.
Be warned #2 - If you've successfully flashed working bootloaders, don't flash other bootloaders for sport. There isn't any point to it and it doesn't give you anything "extra", and even though the chances of things going sour are slim, keep it up and sooner or later you'll end up with an unresponsive device.
Be warned #3 (for 2.3 people only): Do not flash roms or odin packages that include bootloaders. I'm not entirely sure why some phones are bricking when being flashed back to stock, but something tells me that some of the odin packages are only flashing the second stage bootloader instead of both the first stage and second stage. There is probably some major incompatibility between the 2.1/2.2 first stage bootloader and the 2.3 sbl (perhaps the 2.3 sbl has a different entry point?). Either way, I've noticed that some people have perma-bricked their devices trying to flash back to stock using some of the odin packages. Flashing back to stock using a package that contains both the main bootloader and sbl should be fine (in theory), but I have not tried it and don't know how things will end up. If someone has, let me know and I'll ad it to the guide! Also - there isn't much of a point of going back to the old bootloaders once you have the new ones. I tried flashing 2.1 (JH2) and 2.2 (Serendipity 6.3) roms with the new bootloaders and everything works as expected. I didn't experience any problems or instability with either rom, and was able to boot into download mode and recovery with both.
edit: Apparently some people are reporting success with Odin one-click (JF6). Dunno dudes! Flash at your own risk.
edit edit: According to TRusselo, the odin one-click downloader (JF6) flashes both bootloaders, so it should be fine to use it to flash back to stock. Keep in mind that the JF6 one-click downloader does not work with certain handsets, and if yours is build# 1010 or above (you can check your build number by removing your battery, it should be printed on a label in the battery compartment), you should refer to this guide for how to flash back to stock:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Also, I'm pretty sure the above guide will NOT flash new bootloaders. If for whatever reason you really really need the old bootloaders, I would suggest finding a package on samfirmware.com that flashes BOTH bootloaders.
- How to prevent perma-bricking -
Soft bricking is always going to happen. It's a minor software error that isn't a big deal, and common when we fiddle with our devices in ways the manufacturer never intended. The thing we worry about is hard bricking, which is fortunately for us, is easy to prevent!
Here are a few simple rules to help you avoid disaster:
Don't flash roms that flash bootloaders (sbl.bin)
Don't try to flash bootloaders individually.
If you have working bootloaders and can do the 3 buttom combo, don't use Odin packages that include bootloaders, they are an unnecessary risk.
Don't flash when you know your battery is low! Seriously, I see this happening all the time. We know you're excited about a new rom, but it can wait. Put your phone on the charger and let it sit there for a while until you have >50% charge.
Don't mess with your boot partition. I noticed CWM has an option to format your boot partition; I have no idea why.
- Odin guide -
You can find odin by searching the dev section. I use odin3 1.0 simply because that is what I have. I don't know if other versions are better or more stable, but it kind of doesn't matter if you aren't flashing bootloaders anyway.
There are a few videos in this thread: http://forum.xda-developers.com/showthread.php?t=919816 But I'll try to explain in text anyway.
So the first thing you need to do is DOWNLOAD THE DRIVERS! Odin won't recognize your phone in download mode if you don't have the proper drivers. You can find them here:
Windows 64bit: http://www.mediafire.com/?3dh4d6up72me9re
Windows 32bit: http://www.mediafire.com/?0b45zo7o75rc5d5
The next thing you want to do is find a rom to pop in to odin. There are a few in the dev section. There are also a lot of completely stock roms at www.samfirmware.com (WARNING: most of these include bootloaders). When I need to flash back to stock, I use this one: http://forum.xda-developers.com/showthread.php?t=751518 as it does not include bootloaders.
Open Odin and you'll notice a bunch of options. You can ignore most of them. Here is what you need to do: examine your rom package that you downloaded. If it was from samfirmware.com, just pick the files that correspond to the option name, ie if the file starts with PDA, put it in the pda slot. If it starts with CRC, put it in the CRC slot. If it's a rom you found on here, it should have come with instructions, so refer to those.
Choose a pit file. The rom should have come with a pit file, but if it didn't, you can use any pit file and it should work fine. Seriously dudes, the differences between the different pit files is negligible, there isn't any mysticism around how they work.
Unless otherwise noted, leave F. Reset Time and Auto Reboot checked. There isn't any need for repartitioning unless you are flashing back to stock from Cyanogenmod 7, in which case you NEED to select repartition.
The next thing you need to do is put your phone into download mode. Once it's in download mode and odin is set up properly, connect it to the computer. It should show up in odin under ID:COM. Once it's there, simply hit start and kick back for a while until it's done. It should reboot and you should be in Android 2.1 JH2.
*If you are using the Odin One-click downloader (JF6), the process is greatly simplified. Simply open odin, put your phone into download mode, connect it to the computer via usb, wait for odin to recognize it and hit start. Also, keep in mind that the one click downloader will flash bootloaders.
Edit: I just remembered something important. MAKE SURE YOU PLUG YOUR CABLE INTO A USB PORT THAT IS DIRECTLY CONNECTED TO THE MOTHERBOARD, OR ODIN WILL NOT RECOGNIZE IT. This usually means a usb port on the back of your computer. So, if you've installed the drivers and odin still isn't recognizing your phone, you might want to try different usb ports. If it's still not recognizing your phone, you might have a bad cable.
- Some additional ways to get into download mode or recovery -
Just thought I should point this out - you can get into both download mode and recovery through adb. You can download adb by downloading the android sdk at http://developer.android.com. It is in the 'platform-tools' folder.
To get into recovery, simply connect your phone and type 'adb devices' to make sure it is being detected. If it shows up in the list of devices, type 'adb reboot recovery'.
To get into download mode, do the above, but type 'adb reboot download' instead.
**Belatedly amending this document in lieu of old man Outler's unbrickable mod. Any place you see the word "unbrickable" in the article above, take it to mean "unbrickable (if the mod hasn't been applied)". - Jul 27 2012

Good read thanks
Sent from my GT-I9000 using XDA Premium App

Hmmm. About the 2.3 part and flashing back to stock.i am currently on the i9k gb and have flashed the bootloaders .and i also have flashed back to stock.no problems here. Any more info on that part?
Sent from my GT-I9000 using XDA Premium App

What did you use to flash back to stock?

very good read. Thank you

i used odin one click

bulletproof1013 said:
i used odin one click
Click to expand...
Click to collapse
Which one, jf6?
Edit: Nevermind, the only one I could find is JF6, I was under the impression that there were others. Weird! Thanks for the info, made a note of it in the article.

modest_mandroid said:
Which one, jf6?
Edit: Nevermind, the only one I could find is JF6, I was under the impression that there were others. Weird! Thanks for the info, made a note of it in the article.
Click to expand...
Click to collapse
Great read! Good stuff too, should be very helpful!
But im currently on Darky 10.0 RC5.3. With the stock JVB bootloaders. I have not had to flash back to stock with GB but in theory wouldnt this be the best way to flash back to stock with GB Bootloaders because it contains NO BOOTLOADERS, thus the only things that would be wrong when flashing back to stock are button combos, and the weird mix and different images at the boot up?
Here is the Odin Flash back to stock from icezar1:
http://forum.xda-developers.com/showthread.php?t=995143
Can anyone else comment on flashing back to stock with GB bootloaders? Im a build 1010 so I cannot use Odin One click or it just reboots the phone after a "Successful" flash and it flashes AT&T screen then turns off. So that makes me think if I were to do that let the phone "soft"-brick where it just flashes the AT&T screen. Boot it into download mode via. Jig and use this method to get back to stock: http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Any help is GREATLY appreciated

Well if you flashed back to stock from 2.3 without bootloaders you would still have the gb bootloaders installed .correct?
Sent from my GT-I9000 using XDA Premium App

bulletproof1013 said:
Well if you flashed back to stock from 2.3 without bootloaders you would still have the gb bootloaders installed .correct?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Ya thats why Im thinking the thing I posted above about flashing back to stock without bootloaders would be the safest way possible

Idk. It works fine for me.(one click stock)
Sent from my GT-I9000 using XDA Premium App

great work but a couple minor edits you refer to " other odin one-click packages " (eg 3button fix) there is only ONE "odin3 one-click downloader". The other odin3 is " odin3 flashing utility " and the packages for that would not be one click packages. it is these incorrect references everywhere that are confusing to the noobs.
also in the same paragraph in red, about gingerbread bootloaders, you CAN flash other bootloader packages (eg 3button fix) BUT ONLY AFTER "Odin3 One click". (the real one click) as it repalces BOTH bootloaders and 3 button fix flashes only the 2nd bootloader, but they are still compatible so it is all good. All the other "odin packages that cause problems, only flash 2nd bootloader as well, and you cant mix a 2.3 with a 2.1/2 bootloader. So ONE CLICK FIRST then you are back to stock, test if you have working 3 button, then if not flash that, or whatever other rom with bootloader.
to be extra safe on those other odin packages, open up the tar file and look for "sbl.bin" (Secondary Boot Loader) and remove it from the odin package... before flashing. but dont do this to the 3 button fix package, it would defeat the purpose
besides that Great article!
after you edit, ill edit this.
and you might want to link to my Rogers Stock rom thread in my sig, for those odin packages and super awesome instructions AND NO BOOTLOADERS!!! (bootloader version coming though)

Dlev7 said:
But im currently on Darky 10.0 RC5.3. With the stock JVB bootloaders. I have not had to flash back to stock with GB but in theory wouldnt this be the best way to flash back to stock with GB Bootloaders because it contains NO BOOTLOADERS, thus the only things that would be wrong when flashing back to stock are button combos, and the weird mix and different images at the boot up?
Click to expand...
Click to collapse
bulletproof1013 said:
Well if you flashed back to stock from 2.3 without bootloaders you would still have the gb bootloaders installed .correct?
Click to expand...
Click to collapse
Should work fine. I flashed the stock JVB from samfirmware.com, then flashed back to stock a few times using the JH2 firmware mentioned in the article. I didn't flash the old bootloaders and had no problems booting up 2.1 with the new 2.3 bootloaders. The only difference I saw was the i9000 bootup screen before the AT&T logo; other than that there was no problems with the functionality of the phone.
greentshirt said:
Also, why is this not a sticky?
Click to expand...
Click to collapse
Zelendel is busy enjoying his easter
TRusselo said:
great work but a couple minor edits you refer to " other odin one-click packages " (eg 3button fix) there is only ONE "odin3 one-click downloader". The other odin3 is " odin3 flashing utility " and the packages for that would not be one click packages. it is these incorrect references everywhere that are confusing to the noobs.
also in the same paragraph in red, about gingerbread bootloaders, you CAN flash other bootloader packages (eg 3button fix) BUT ONLY AFTER "Odin3 One click". (the real one click) as it repalces BOTH bootloaders and 3 button fix flashes only the 2nd bootloader, but they are still compatible so it is all good. All the other "odin packages that cause problems, only flash 2nd bootloader as well, and you cant mix a 2.3 with a 2.1/2 bootloader. So ONE CLICK FIRST then you are back to stock, test if you have working 3 button, then if not flash that, or whatever other rom with bootloader.
to be extra safe on those other odin packages, open up the tar file and look for "sbl.bin" (Secondary Boot Loader) and remove it from the odin package... before flashing. but dont do this to the 3 button fix package, it would defeat the purpose
besides that Great article!
after you edit, ill edit this.
and you might want to link to my Rogers Stock rom thread in my sig, for those odin packages and super awesome instructions AND NO BOOTLOADERS!!! (bootloader version coming though)
Click to expand...
Click to collapse
Thanks dude! I didn't get a chance to proof read what I wrote; had to go to the parents' house for dinner tonight. I'll give it a read and edit per your suggestions in a bit, after I take the dog out for a walk.

TRusselo said:
great work but a couple minor edits you refer to " other odin one-click packages " (eg 3button fix) there is only ONE "odin3 one-click downloader". The other odin3 is " odin3 flashing utility " and the packages for that would not be one click packages. it is these incorrect references everywhere that are confusing to the noobs.
also in the same paragraph in red, about gingerbread bootloaders, you CAN flash other bootloader packages (eg 3button fix) BUT ONLY AFTER "Odin3 One click". (the real one click) as it repalces BOTH bootloaders and 3 button fix flashes only the 2nd bootloader, but they are still compatible so it is all good. All the other "odin packages that cause problems, only flash 2nd bootloader as well, and you cant mix a 2.3 with a 2.1/2 bootloader. So ONE CLICK FIRST then you are back to stock, test if you have working 3 button, then if not flash that, or whatever other rom with bootloader.
to be extra safe on those other odin packages, open up the tar file and look for "sbl.bin" (Secondary Boot Loader) and remove it from the odin package... before flashing. but dont do this to the 3 button fix package, it would defeat the purpose
besides that Great article!
after you edit, ill edit this.
and you might want to link to my Rogers Stock rom thread in my sig, for those odin packages and super awesome instructions AND NO BOOTLOADERS!!! (bootloader version coming though)
Click to expand...
Click to collapse
So are you saying even for someone like me who uses the One-Click and it sends my phone into a boot loop of AT&T screen then off. I should use that because it replaced the bootloaders.
Then use either button combo or my Jig to boot it into Download mode and flash the JH2 Odin via Odin3 for Build 1010+?

Dlev7 said:
So are you saying even for someone like me who uses the One-Click and it sends my phone into a boot loop of AT&T screen then off. I should use that because it replaced the bootloaders.
Then use either button combo or my Jig to boot it into Download mode and flash the JH2 Odin via Odin3 for Build 1010+?
Click to expand...
Click to collapse
i didnt mention bootloop so slow down, boot-loaders.
you are wondering if? you used " Odin3 One-Click-Downloader " so you should use that?... - WHAT?
you shouldnt get boot loop,
everyone, including the OP says " Odin3 one click downloader " is THE WAY to flash stock. PERIOD.
after that it should boot.
THE ONLY REASON to flash ANY other stock is IF "3 button combo" doesnt work, or to flash my rogers stock. BUT ONLY AFTER one click.
thats what i said.
if you are in bootloop. try booting into recovery and doing facotry reset, clear everything. reboot.
if it doesnt work from there, try flashing one click again.
it works.
all else fails flash back to gingerbread with bootloaders, and flash back without bootloaders, using the many instructions above.

Edit dont mind me
Sent from my GT-I9000 using XDA Premium App

Been itching to flash a GB rom but scared of all the brick reports. So just to make sure, http://forum.xda-developers.com/showthread.php?t=731989&highlight=odin+click&page=178 This is the Odin One Click we should use to flash back to stock from a GB rom is that correct? Since it has both bootloaders?

There is only ONE odin one click. if that is it, that is it.
if you really want THE ONE. get it from THE GB INSTRUCTIONS!

TRusselo said:
i didnt mention bootloop so slow down, boot-loaders.
you are wondering if? you used " Odin3 One-Click-Downloader " so you should use that?... - WHAT?
you shouldnt get boot loop,
everyone, including the OP says " Odin3 one click downloader " is THE WAY to flash stock. PERIOD.
after that it should boot.
THE ONLY REASON to flash ANY other stock is IF "3 button combo" doesnt work, or to flash my rogers stock. BUT ONLY AFTER one click.
thats what i said.
if you are in bootloop. try booting into recovery and doing facotry reset, clear everything. reboot.
if it doesnt work from there, try flashing one click again.
it works.
all else fails flash back to gingerbread with bootloaders, and flash back without bootloaders, using the many instructions above.
Click to expand...
Click to collapse
Odin One Click puts my build 1010 into an AT&T screen then off bootloop. I can boot it into download mode.
So that's why I used the JH2 way to flash back to stock in the method above.
You don't understand what I'm trying to say, I CANNOT USE ODIN ONE CLICK.
I may just use the JH2 method and deal with the i9000 screen flashing and different button combos
Sent from my SGH-I897 using XDA App

so you went back to gingerbread bootloaders, then flashed stock without bootloaders, keeping gingerbread ones because odin one click gave you boot-loop.
see how easy that was to say and understand?
and that method is in POST 1...
if your ability to flash is anything like your ability to explain your situation... boot-loop un-avoidable
Almost everyone uses ONE CLICK. that is not my idea! read the first post (its not me!) then read my post again.
EVERYONE suggests it if you want stock bootloaders back.
its the only way and it is KNOWN to work.

[Q] Will this restore a CM7 i9020A back to 100% stock?

Hi,
- This is my first post on XDA forum.
- Before I ask this, I swear I've read 20+ pages on this forum.
- Before I read those 20+ pages, I know absolutely nothing about modding Android Phone.
- I saw some thread asking the same question as me, but I can't find a thread that sum this issue up in a 1 page step-by-step guide.
- I did my best, just need experts like you guys to confirm that I understand it right (before I brick my phone T_T...).
- I believe many people are also looking for answer to this question as well.
--- Situation ---
I bought a White Nexus S (it's i9020A) from ebay. It's modded with CM7. Actually it's not arrived yet. But I'm doing research while waiting for it.
--- My goal ---
Restore everything back to 100% stock. Be it 2.3.3 or 2.3.4 is fine, as long as it's official. (Well if it's 2.3.3 it'll get official OTA to 2.3.4 anyway)
I want the phone to be like it has never been modded at all.
I want to restore everything: the OS, the recovery image, the root access, ...
If I'm still missing something, please let me know.
--- Main Question ---
Does the following steps enough to achieve my goal?
1.Restore the recovery image to stock first. From what I read, the 'stock recovery' will not allow flashing of custom OS. So this will help confirm that the OS we're going to flash is also a 100% stock OS.
1.1 Find the stock recovery image for i9020A(still don't know where to download it)
1.2 "fastboot flash recovery my_finally_found_i9020a_stock_recovery.img"
2. Flash the stock Android 2.3.4 OS for i9020A downloaded from the first page of this thread:
http://forum.xda-developers.com/showthread.php?t=1056062
(the link that says Model: i9020A - GRI54 -> GRJ22: Released)
The flashing tutorial is also in that thread:
How to apply the update:
I will cover stock only, as those running Clockworkmod should already know how to apply an update zip.
Copy the update file appropriate for your model/build/modem to your Internal storage of your phone. Do not place in any sub-directory.
Turn off your phone.
While holding the volume up, press the power to turn on the phone
use the up/down volume to select recovery
press power to make the selection.
Your phone will now reboot into recovery.
When you see the little droid, while holding the power, press the volume up to bring up a menu.
Select "Apply update from /sdcard"
scroll down to the update file you downloaded it, make sure it's highlighted then press power to select
The update should go through
Click to expand...
Click to collapse
Is this all I need to do? Am I 100% stock now? (almost forgot to ask where to find the stock recovery image for i9020A? I can't find it in this forum)
Thank you in advance!

The link for the stock ROM is only update, not a full rom. You need a full rom in size about 80 MB.
In the stock rom there gonna be recovery.img - that is stock recovery. Extract it and flash with fastboot, then do the rest as you described.
Ask free if you need help.

Thank you for the info.
I found the stock rom(around 90mb in size) in this thread:
http://forum.xda-developers.com/showthread.php?t=1033269
but it doesn't contain the recovery.img
however, in page 4 of that thread, there's a stock recovery.img
So let me re-arrange the to-do list again:
1. use fastboot to install the stockrecovery.img
2. use stock recovery to flash the Full stock rom
well this should get me 100% stock, right?
(BTW, I wonder why people keep saying flash stock rom with CWM first, then fastboot recovery.img)
Thanks again!

You would need to do step 2 and then step one. You need Clockwork Recovery to flash the stock zip file and then flash the stock recovery using fastboot, if you do it the other way around the stock recovery won't let you flash the zip....not sure if it would cause any other problems though.
So it's
1. Flash stock zip using Clockwork Recovery
2. Use fastboot to flash stockrecovery.img
3. Then lock the bootloader using fastboot oem lock

hi
you can find all the samsung related stock firmware on samfirmware
please add www and com in the addres. i am not allowed to put the web address.
please check the website
cheers

zuvoke said:
hi
you can find all the samsung related stock firmware on samfirmware
please add www and com in the addres. i am not allowed to put the web address.
please check the website
cheers
Click to expand...
Click to collapse
That is for Odin which is might be more difficult than necessary.
EDIT: OP, have you seen this thread? http://forum.xda-developers.com/showthread.php?t=1033269&highlight=stock
I'm not sure if the radio is right for you. But maybe you can use it with another radio.

hey I am in the sort of in the same boat as lgmcben. I just purchased a nexus s and its on 2.3.4 rooted already. Not knowing anything about android and wanting learn the whole thing from scratch, i also want to reset my phone to factory setting. Now, not knowing how it was rooted orignially, i am having difficulty following a particular guide because they all at some point end mentioning about how the phone was originally rooted so i get confused whether i should follow that guide. Would i be able to follow same steps suggested by lgmcben. Also, my phone is unlocked for to be used with any carriers. would resetting it to factory setting lock it to the original carrier again? Any help is appreciated.

matt2053 said:
That is for Odin which is might be more difficult than necessary.
EDIT: OP, have you seen this thread? http://forum.xda-developers.com/showthread.php?t=1033269&highlight=stock
I'm not sure if the radio is right for you. But maybe you can use it with another radio.
Click to expand...
Click to collapse
Hi,
This should work. However, it's still an unofficial/unsigned rom. But it should work. Thank you. =)

forpulse said:
hey I am in the sort of in the same boat as lgmcben. I just purchased a nexus s and its on 2.3.4 rooted already. Not knowing anything about android and wanting learn the whole thing from scratch, i also want to reset my phone to factory setting. Now, not knowing how it was rooted orignially, i am having difficulty following a particular guide because they all at some point end mentioning about how the phone was originally rooted so i get confused whether i should follow that guide. Would i be able to follow same steps suggested by lgmcben. Also, my phone is unlocked for to be used with any carriers. would resetting it to factory setting lock it to the original carrier again? Any help is appreciated.
Click to expand...
Click to collapse
May be you can use the rom provided in this thread =)
http://forum.xda-developers.com/showthread.php?t=1033269&highlight=stock
About the step-by-step guide on how to use the ClockWorkMod, go here:
http://forum.xda-developers.com/showthread.php?t=1007782

lgmcben said:
May be you can use the rom provided in this thread =)
http://forum.xda-developers.com/showthread.php?t=1033269&highlight=stock
About the step-by-step guide on how to use the ClockWorkMod, go here:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
I am kind of not sure if I can use that ROM since its 2.3.3. I am on 2.3.4 at the moment so that would mean downgrading. If thats allowed then great, but i don't know if it is allowed. As for the clockworkmod guide, I am not going to be needing it now since for now I just want a normal factory resetted unrooted phone. Once I get to that stage I will look into that. But thanks for that guide. For now, I just want to unroot. I found this guide here on XDA, which I am not sure if I can use. would you be able to tell.
UNROOTING.........
Get files (can't post the link since i am new user but its 4shared links found in this forum)
-download and extract files, we will be using odin, the 3 tar files.
-extract tar files to desktop along with odin.
-run odin and in the files section select the boxes bootloader, pda, phone.
-click the buttons next to each and direct it to the .tar files we extracted to desktop, so....
click the bootloader box, direct it to sph-d720-bootloader.tar ...then..
click the pda button direct it toward the sph-d720-pda.tar....then..
click the phone button and direct it toward sph-d720-phone.tar....
-now turn off your phone, when off hold volume up and volume down buttons simultaneously, then quickly press the power button....a huge yellow triangle will pop up and say "downloading'.......
plug your phone via usb to computer....odin should automatically see it.....click the start button in odin and let it do its thing and bam...all set.
If you want stock recovery too place the recovery.img in tools folder, open command prompt..type the following command..
fastboot flash recovery recovery.img
Done.

How to root your samsung galaxy s3 (easily)

**** UPDATED 7-24-13 *****
Please read the tutorial now as I have added a new section on how to unlock the bootloader for your Verizon Samsung Galaxy S3. If you are not using a verizon SGS3
specifically model SCH-i535 then you do not have to worry about unlocking your bootloader as it comes unlocked by default. If you are using a verizon samsung galaxy s3 model sch-i535 and you do not fully unlock your bootloader you could run into problems when using certain root apps such as "mobile odin pro" or you could run into big problems when trying to flash custom roms such as cyanogenmod roms.
In this update I am adding one final step at the end of the root process to fully unlock the boot loader for the verizon samsung galaxy s3. There will be two ways to unlock the bootloader. One way will be to flash a final bootchain file with Odin, and the other will be to use an app to unlock the bootloader. Depending on what version of android you are using and your phones baseband version you will either need to use odin or you could use the application for any android version such as 4.1.1 or 4.1.2 and you can use the application for any baseband version your phone might be. I will leave the choice up to you, but I will show how to do it both ways.
Samsung users, don't forget if you plan on flashing a custom rom that with Samsung phones you could get the ugly yellow triangle warning. To get rid of this yellow triangle you can either go to google play store and get "yellow triangle away" app or go to this forum on this great xda developers site: http://forum.xda-developers.com/showthread.php?t=1494114
**NOTE** for those of you who would like to see a video of how to root your phone using these exact steps you can go to here: http://www.youtube.com/watch?v=K4b9hcWHrW8&feature=share&list=FL8Y3FM4mtznp0GQbwkkwaSg
A member on this thread gave me that link and it is a video by phone rebel and show you how to root your verizon SGS3 using the same steps i have outlined in this tutorial. Thank you so much for providing that link to my attention, I am sure it will help many users here!
Hello everyone,
Well this is one of my first tutorials for this forum on how to root your Verizon Samsung Galaxy S3.
I just recently got my Verizon Samsung Galaxy S3 and all of the tutorials I found were quite complicated and not very detailed so I thought that
I would write this tutorial and maybe it might help others out there....
Since the Galaxy S4 is getting ready to come out, the price has dropped considerably for the S3 and i believe more and more people will be getting this phone and wanting to root it.
Oh, and if you want an alternative guide you can use this very excellent tutorial from another post on this amazing forum:
http://forum.xda-developers.com/showthread.php?t=2046439
Here is the specs for the phone I am using and the step by step process I used to root it.
Verizon Samsung Galaxy SIII model I535 running Android 4.1.2
Okay step 1 you are going to need some files...
First thing you are going to need is the Samsung Drivers so you can connect your phone to your computer and your computer can recognize it.
All of the files you are going to need I am just going to reference the link from the other tutorial that I posted above, no sense in redoing work
that has already been done especially if it has been done well!
1. You can get the samsung driver files here: http://forum.xda-developers.com/showthread.php?t=2046439
click on the link that says samsung drivers
2. You are going to need Odin you can get it from the same link, click on the Odin Link
3. You are going to need the VRALEC BOOTCHAIN you can get it from the link I posted in step 1 make sure you get this file it is very
important.
Since I am using a Verizon Samsung Galaxy S3 the bootloader comes by default locked so we need this file to unlock the bootloader
so we can root the phone. If we were using any other phone besides Verizon we would not have to worry about this but since I have
Verizon I have to do this. IMPORTANT: if you are not using a VERIZON PHONE DO NOT download this file or use it in the step
process you do not need it.
4. Next you are going to need the exploit so that you can root your phone and you can grab that from a different website, here is the address:
http://autoroot.chainfire.eu/
This is the CF-AUTOROOT file and this is what roots your phone. If you have the same phone as me scroll down to the SCH-I535 link and
download that file.
Okay now that we have all of that downloaded lets get things moving...
First thing we are going to need to do is install the Samsung USB drivers, so do that.
After the drivers are installed plug in your phone and make sure that it connects to your computer correctly, after it connects disconnect
your phone from your computer.
Next thing we are going to need to do is extract the ODIN zip file and install the Odin executable.
Now we need to get to the critical stuff...
Step 1. Make sure that [USB Debugging] is enabled in your phone, if it is not go to Settings -> Developer Options and enable it.
Step 2. Put your phone in DOWNLOAD Mode. You do that by pressing Volume Down + Home + Power button and hold it down till you see
a warning screen. When you see the warning screen hit Volume Up to allow Download mode.
Step 3. Now that your phone is in Download Mode you are going to connect your phone to your computer with ODIN RUNNING if
everything connects correctly you will see ODIN highlight yellow (older versions of ODIN) or highlight blue (newer ODIN versions)
Step 4. Now this is where previous tutorials kind of messed up in my opinion (just my opinion). Now that your phone is in download mode
you need to only have the "auto boot" option selected in ODIN and click on the bootloader button and select the VRALEC file
you downloaded earlier. Every tutorial i read said to use this file with the PDA button/option but you need to use it with the bootloader
button/option in ODIN. Now that you have the VRALEC file selected under bootloader in ODIN select START. This will reboot your
phone and if everything goes correctly your phone's bootloader will be unlocked.
After reboot make sure to disconnect your phone from your computer.
Step 5. After your phone reboots from step 4 turn off your phone and then boot it back into DOWNLOAD mode. Vol Down + Home + Power
Step 6. Now that your phone is in Download Mode again (Reconnect your phone to your computer) and make sure ODIN is still running
Step 7. With your phone connected go to the PDA option/button and when you select it choose the CF-AUTOROOT file you downloaded earlier
Step 8. With your PDA option selected hit start. When this happens your phone will reboot and your will see a CUSTOM lock icon on your
screen don't worry it is okay. Now you will see some new text on your phone and if everything is working you will see things like
"Android is UPDATING"
Your phone is now rooted! but you are not done...
This is where all of the other tutorials I found also fell short...
Your phone is rooted but it will not work correctly without SuperSU
Step 9. Go to the Google Play Store and Download SuperSU. When the download is complete run SuperSU and now your phone is fully
rooted. You can test it by downloading Android Terminal and running the terminal and typing "su" or by downloading a root required
app Titanium Backup.
*****UPDATED STEP*****
IMPORTANT NOTE: i want to point that this step is completely optional. You do not have to unlock your bootloader but i would recommend it. If you just want to use a stock rom and have your phone rooted then you can ignore this last step. But...if you want to flash custom rom's or do any kind of serious customize your phone, then you will need to have your phones bootloader unlocked. Plus with the application I am going to show you further down this tutorial, it is so easy to unlock your bootloader, you might as well go for it.
Step 10. Okay now from the link that I gave you above: http://forum.xda-developers.com/showthread.php?t=2046439 you are going to need to download another bootchain file to fully unlock your verizon samsung galaxy s3 model sch-i535 phone.Go into your phone and under settings go into "about phone' and look at the section "baseband version". Now depending on what version of android you are using will determine your baseband version. On my Verizon SGS3 running 4.1.2 my baseband version is I535VRBMB1 the important part is -> "VRBMB1" now go to site i provided in this step and download the bootchain for your specific phone.
Since my phones baseband version is "VRBMB1" i will download that bootchain file obviously. VRBMB1 is for android 4.1.2
The other boothchain files are "VRBLK3" for android 4.1.1 and "VRBMD3" for android 4.1.2
Now take that bootchain file that you downloaded and load up Odin again. Connect your phone to your computer (MAKE SURE YOUR PHONE IS IN DOWNLOAD MODE -> VOL DOWN + HOME + POWER) and wait for Odin show a connection. Odin will show a blue light on newer Odin versions and a yellow light on older Odin versions.
When the connection is made hit the "bootloader" button and select the proper bootchain file for your specific phone. Before you hit start make sure that only "Auto Reboot" is selected on the left hand side.
Now go ahead and hit start and if all goes well your phones bootloader should be unlocked. You can tell that your phones bootloader is unlocked two ways.
One, when your phone reboots the Samsung Logo in white bold/block writing will disappear within 1-2 seconds. It will go by very fast.
Two, the custom lock icon that showed up after you ran the CF-AUTOROOT exploit will now disappear, if for any reason if you still see this logo then your phones bootloader is still locked and you can either try to flash the bootchain file again or use the application I am about to tell you about.
For my phone flashing this bootchain file worked fine, but for my brother's phone he has a verizon samsung galaxy s3 model sch-i535 this did not work and I had to use an application to unlock his bootloader.
****UPDATE UNLOCKING THE BOOTLOADER WITH EZ-UNLOCK*****
Okay so my brother who has a verizon samsung galaxy s3 model sch-i535 asked me to root his phone just the other day. I rooted his phone following all the same steps I have written above with no problems. His phone rooted perfectly, however his bootloader would not unlock. I believe that his bootloader would not unlock because he had an updated version. While his android version was the same as mine 4.1.2 he had a different baseband version.
His baseband version was "I535VRBMF1" the important part -> "VRBMF1"
Now i have been told that you can use the bootchain file VRBMB1 to unlock the bootloader for verizon SGS3 running android 4.1.2 baseband version "VRBMF1" but when i tried it, the bootloader staid locked. So i had to use an application to unlock his bootloader.
The application i used was "EZ-Unlock" which you can get here: http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
Now this application is SO EASY to use it is amazing. Just download the file, the author recommend version 1.2 as the most stable and that is version i used. To download this file make sure you have the option "Unknown Sources" check in your Settings -> Security menu.
Okay to unlock your bootloader with EZ-Unlock follow these easy steps:
Step 10A. Download EZ-Unlock version 1.2 from the link above.
Step 10B. Install the application and open it.
Step 10C. Once open click on the giant "Unlock" button. If all goes well you will hear "That was easy" from the application.
Once you have hit the unlock button on EZ-Unlock reboot your phone to see if the Samsung in bold/block white letters disappears within 1-2 seconds, and make sure the custom lock icon has disappeared.
Now the application EZ-Unlock is designed specifically for verizon samsung galaxy s3 phones, it does not matter what baseband version you use or android version you use. So this is a very appealing and easy way to unlock your bootloader. If you don't feel like flashing a bootchain file with Odin or if you are not sure what bootchain file you should use then using this application. NOTE: you do need root access to run this application.
And that is it! Your phones bootloader should be unlocked either with Odin or EZ-Unlock the choice is all up to you!
***LAST THOUGHT ON INSTALLING CUSTOM RECOVERY***
This rooting method does not install and kind of custom recovery manager on to your phone. If you want to install a custom recovery manager such as "ClockworkMod Recovery" you can do that very easily once your phone is rooted. Once your phone is rooted go to the google play store and download "Rom Manager". Once Rom Manager is installed open it up and give it root access with SuperSU. Once that is done go into the option to flash a recovery manager and follow the steps and the application Rom Manager will take care of that for you!.
Congrats on rooting your phone! I hope this tutorial has helped you and I want to thank all of the system administrators of this forum and all of
the great guys and gals that contribute to this place. You guys/gals are what makes the open source community great!
I thank you all...
Hope it helped!
-droidshadow

Thanks might have to do this on my wife's phone
Sent from my SCH-I535 using xda premium

kgirlx said:
Thanks might have to do this on my wife's phone
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I think that the easiest way to root any Samsung Devices - Samsung Toolkit

I'm not having any luck with this. I've followed the instructions step by step and when I flash a custom ROM, I get the dreaded yellow triangle of death apon rebooting. There were some other files mentioned in the links. Do I need to unzip those at some point?

sorry i have been away
Okay i am so sorry for the late response I have been away and very busy. This tutorial is how to root your samsung galaxy s3 (verizon) model sch-i535 because you need to unlock the bootloader for that specific model.
Now you mentioned that when you try to flash a custom rom you get a yellow triangle of death....
Have you unlocked the bootloader?
Is your phone already rooted? Are you trying to flash a custom rom or are you still trying to root your phone?
I hope you have already resolved your issue but if you haven't I would be more than happy to try and help you out.

How is it any easier then the other guides for jelly bean? Here you added the cf-auto root which is one extra step . Also with auto root there is a possibility of bricking the phone since it supports a lot of devices and as you are well aware that a lot of people new to flashing tend to flash the wrong files even if you give them a step by step guide. While this guide is helpful and does work it isn't as idiot proof as the other guide you linked on your post.

This does not work on my phone. When I try this, the phone boots normally. I have tried this several times and I get the same results. I can however hold the vol up button+the home button+the power button and get to stock recovery mode. I had an older S3 that this did work on but not my new one. I have read several threads here for rooting the S3 i535 with Jelly Bean 4.1.2 and this is supposedly the method but it will not work on my phone. What am I doing wrong? What am I missing? Please advise!

benbrown said:
This does not work on my phone. When I try this, the phone boots normally. I have tried this several times and I get the same results. I can however hold the vol up button+the home button+the power button and get to stock recovery mode. I had an older S3 that this did work on but not my new one. I have read several threads here for rooting the S3 i535 with Jelly Bean 4.1.2 and this is supposedly the method but it will not work on my phone. What am I doing wrong? What am I missing? Please advise!
Click to expand...
Click to collapse
This guide is different in that it uses cf-auto root so I highly doubt you even tried this method.

I finally did get it. All rooted now.
Sent from my SCH-I535 using Tapatalk 2

The easiest way to root is odin'ing Mr. Robinson's root injected tar and the unlock the bootloader. Done
Sent from my MIUI powered S3 thanks to StrumerJohn

maybe i should have been more clear...
faehsemc said:
The easiest way to root is odin'ing Mr. Robinson's root injected tar and the unlock the bootloader. Done
Sent from my MIUI powered S3 thanks to StrumerJohn
Click to expand...
Click to collapse
Hey everyone,
Well i guess everyone has their own favorite way of rooting their phone/device. I did not mean for this small tutorial to be the *absolute easiest* way to root a verizon samsung galaxy s3 model i535 i just thought that I could do people a favor by elaborating a bit more on certain steps to make the rooting process a bit easier.
On certain tutorials i found I didn't seem them clearly state that the VRLAC BOOTCHAIN file needed to go in the boot loader section of ODIN to unlock the phone's bootloader.
On other tutorials that show you how to use CF-AUTOROOT I didn't see any that told you that you needed to install SUPERSU from the google play store manually in order to fully utilize your phones rooted status.
Yes there are other ways too root a SGS3, the Samsung Toolkit is a good option, or using a custom root such as Cyanogenmod is another great option as well...
All of those options you will have to research for yourself and ultimately decide for yourself.
However, if you want to keep your phone's stock ROM and you just want to root your Verizon SGS3 model SCH-I535 then I like using ODIN + CF-AUTOROOT exploit.
All i wanted to do was assist and do my part on this great forum which has helped me so much in the past...
I hope it helped someone...
Thanks for everyone who replied and shared your thoughts on other rooting options.
-DroidShadow

droidshadow said:
Hello everyone,
Well this is one of my first tutorials for this forum on how to root your Verizon Samsung Galaxy S3.
I just recently got my Verizon Samsung Galaxy S3 and all of the tutorials I found were quite complicated and not very detailed so I thought that
I would write this tutorial and maybe it might help others out there....
Since the Galaxy S4 is getting ready to come out, the price has dropped considerably for the S3 and i believe more and more people will be getting this phone and wanting to root it.
Oh, and if you want an alternative guide you can use this very excellent tutorial from another post on this amazing forum:
http://forum.xda-developers.com/showthread.php?t=2046439
Here is the specs for the phone I am using and the step by step process I used to root it.
Verizon Samsung Galaxy SIII model I535 running Android 4.1.2
Okay step 1 you are going to need some files...
First thing you are going to need is the Samsung Drivers so you can connect your phone to your computer and your computer can recognize it.
All of the files you are going to need I am just going to reference the link from the other tutorial that I posted above, no sense in redoing work
that has already been done especially if it has been done well!
1. You can get the samsung driver files here: http://forum.xda-developers.com/showthread.php?t=2046439
click on the link that says samsung drivers
2. You are going to need Odin you can get it from the same link, click on the Odin Link
3. You are going to need the VRALEC BOOTCHAIN you can get it from the link I posted in step 1 make sure you get this file it is very
important.
Since I am using a Verizon Samsung Galaxy S3 the bootloader comes by default locked so we need this file to unlock the bootloader
so we can root the phone. If we were using any other phone besides Verizon we would not have to worry about this but since I have
Verizon I have to do this. IMPORTANT: if you are not using a VERIZON PHONE DO NOT download this file or use it in the step
process you do not need it.
4. Next you are going to need the exploit so that you can root your phone and you can grab that from a different website, here is the address:
http://autoroot.chainfire.eu/
This is the CF-AUTOROOT file and this is what roots your phone. If you have the same phone as me scroll down to the SCH-I535 link and
download that file.
Okay now that we have all of that downloaded lets get things moving...
First thing we are going to need to do is install the Samsung USB drivers, so do that.
After the drivers are installed plug in your phone and make sure that it connects to your computer correctly, after it connects disconnect
your phone from your computer.
Next thing we are going to need to do is extract the ODIN zip file and install the Odin executable.
Now we need to get to the critical stuff...
Step 1. Make sure that [USB Debugging] is enabled in your phone, if it is not go to Settings -> Developer Options and enable it.
Step 2. Put your phone in DOWNLOAD Mode. You do that by pressing Volume Down + Home + Power button and hold it down till you see
a warning screen. When you see the warning screen hit Volume Up to allow Download mode.
Step 3. Now that your phone is in Download Mode you are going to connect your phone to your computer with ODIN RUNNING if
everything connects correctly you will see ODIN highlight yellow (older versions of ODIN) or highlight blue (newer ODIN versions)
Step 4. Now this is where previous tutorials kind of messed up in my opinion (just my opinion). Now that your phone is in download mode
you need to only have the "auto boot" option selected in ODIN and click on the bootloader button and select the VRALEC file
you downloaded earlier. Every tutorial i read said to use this file with the PDA button/option but you need to use it with the bootloader
button/option in ODIN. Now that you have the VRALEC file selected under bootloader in ODIN select START. This will reboot your
phone and if everything goes correctly your phone's bootloader will be unlocked.
After reboot make sure to disconnect your phone from your computer.
Step 5. After your phone reboots from step 4 turn off your phone and then boot it back into DOWNLOAD mode. Vol Down + Home + Power
Step 6. Now that your phone is in Download Mode again (Reconnect your phone to your computer) and make sure ODIN is still running
Step 7. With your phone connected go to the PDA option/button and when you select it choose the CF-AUTOROOT file you downloaded earlier
Step 8. With your PDA option selected hit start. When this happens your phone will reboot and your will see a CUSTOM lock icon on your
screen don't worry it is okay. Now you will see some new text on your phone and if everything is working you will see things like
"Android is UPDATING"
Your phone is now rooted! but you are not done...
This is where all of the other tutorials I found also fell short...
Your phone is rooted but it will not work correctly without SuperSU
Step 9. Go to the Google Play Store and Download SuperSU. When the download is complete run SuperSU and now your phone is fully
rooted. You can test it by downloading Android Terminal and running the terminal and typing "su" or by downloading a root required
app Titanium Backup.
Congrats on rooting your phone! I hope this tutorial has helped you and I want to thank all of the system administrators of this forum and all of
the great guys and gals that contribute to this place. You guys/gals are what makes the open source community great!
I thank you all...
Hope it helped!
-droidshadow
Click to expand...
Click to collapse
Followed all instructions, and the phone never rebooted. Not its not turning on. Tried vol up+home+power, vol down+home+power, battery pull, holding down power for 2 minutes. . .
The only thing I can think of is that I possibly unplugged the phone before the reboot after Step 4, just as soon as the phone shut down and before the actual reboot.
Anything you can help me with? I''m going crazy here.
Thanks

Rooting and installation on S3 GTI9300
I rooted my S3 2 days back (i think so), now i want to install a custom rom (mostly xperia Z) and I am new to this world, so can you plz help me??
I followed your instructions there was no such msg as Andriod is Updating, and how should i do install the rom??
I wish to install from this http://forum.xda-developers.com/showthread.php?t=2174644

droidshadow said:
Hello everyone,
Well this is one of my first tutorials for this forum on how to root your Verizon Samsung Galaxy S3.
I just recently got my Verizon Samsung Galaxy S3 and all of the tutorials I found were quite complicated and not very detailed so I thought that
I would write this tutorial and maybe it might help others out there....
Since the Galaxy S4 is getting ready to come out, the price has dropped considerably for the S3 and i believe more and more people will be getting this phone and wanting to root it.
Oh, and if you want an alternative guide you can use this very excellent tutorial from another post on this amazing forum:
http://forum.xda-developers.com/showthread.php?t=2046439
Here is the specs for the phone I am using and the step by step process I used to root it.
Verizon Samsung Galaxy SIII model I535 running Android 4.1.2
Okay step 1 you are going to need some files...
First thing you are going to need is the Samsung Drivers so you can connect your phone to your computer and your computer can recognize it.
All of the files you are going to need I am just going to reference the link from the other tutorial that I posted above, no sense in redoing work
that has already been done especially if it has been done well!
1. You can get the samsung driver files here: http://forum.xda-developers.com/showthread.php?t=2046439
click on the link that says samsung drivers
2. You are going to need Odin you can get it from the same link, click on the Odin Link
3. You are going to need the VRALEC BOOTCHAIN you can get it from the link I posted in step 1 make sure you get this file it is very
important.
Since I am using a Verizon Samsung Galaxy S3 the bootloader comes by default locked so we need this file to unlock the bootloader
so we can root the phone. If we were using any other phone besides Verizon we would not have to worry about this but since I have
Verizon I have to do this. IMPORTANT: if you are not using a VERIZON PHONE DO NOT download this file or use it in the step
process you do not need it.
4. Next you are going to need the exploit so that you can root your phone and you can grab that from a different website, here is the address:
http://autoroot.chainfire.eu/
This is the CF-AUTOROOT file and this is what roots your phone. If you have the same phone as me scroll down to the SCH-I535 link and
download that file.
Okay now that we have all of that downloaded lets get things moving...
First thing we are going to need to do is install the Samsung USB drivers, so do that.
After the drivers are installed plug in your phone and make sure that it connects to your computer correctly, after it connects disconnect
your phone from your computer.
Next thing we are going to need to do is extract the ODIN zip file and install the Odin executable.
Now we need to get to the critical stuff...
Step 1. Make sure that [USB Debugging] is enabled in your phone, if it is not go to Settings -> Developer Options and enable it.
Step 2. Put your phone in DOWNLOAD Mode. You do that by pressing Volume Down + Home + Power button and hold it down till you see
a warning screen. When you see the warning screen hit Volume Up to allow Download mode.
Step 3. Now that your phone is in Download Mode you are going to connect your phone to your computer with ODIN RUNNING if
everything connects correctly you will see ODIN highlight yellow (older versions of ODIN) or highlight blue (newer ODIN versions)
Step 4. Now this is where previous tutorials kind of messed up in my opinion (just my opinion). Now that your phone is in download mode
you need to only have the "auto boot" option selected in ODIN and click on the bootloader button and select the VRALEC file
you downloaded earlier. Every tutorial i read said to use this file with the PDA button/option but you need to use it with the bootloader
button/option in ODIN. Now that you have the VRALEC file selected under bootloader in ODIN select START. This will reboot your
phone and if everything goes correctly your phone's bootloader will be unlocked.
After reboot make sure to disconnect your phone from your computer.
Step 5. After your phone reboots from step 4 turn off your phone and then boot it back into DOWNLOAD mode. Vol Down + Home + Power
Step 6. Now that your phone is in Download Mode again (Reconnect your phone to your computer) and make sure ODIN is still running
Step 7. With your phone connected go to the PDA option/button and when you select it choose the CF-AUTOROOT file you downloaded earlier
Step 8. With your PDA option selected hit start. When this happens your phone will reboot and your will see a CUSTOM lock icon on your
screen don't worry it is okay. Now you will see some new text on your phone and if everything is working you will see things like
"Android is UPDATING"
Your phone is now rooted! but you are not done...
This is where all of the other tutorials I found also fell short...
Your phone is rooted but it will not work correctly without SuperSU
Step 9. Go to the Google Play Store and Download SuperSU. When the download is complete run SuperSU and now your phone is fully
rooted. You can test it by downloading Android Terminal and running the terminal and typing "su" or by downloading a root required
app Titanium Backup.
Congrats on rooting your phone! I hope this tutorial has helped you and I want to thank all of the system administrators of this forum and all of
the great guys and gals that contribute to this place. You guys/gals are what makes the open source community great!
I thank you all...
Hope it helped!
-droidshadow
Click to expand...
Click to collapse
I ran ODIN with the bootchain, and that worked, but when i tried running it with PDA set to CF-autoroot file, I get SECURE CHECK FAIL

hello everyone
bgenchel said:
I ran ODIN with the bootchain, and that worked, but when i tried running it with PDA set to CF-autoroot file, I get SECURE CHECK FAIL
Click to expand...
Click to collapse
bgenchel: what kind of phone do you have? Are you 100% sure that you downloaded the correct CF-autoroot file for your specific phone model?

mlev1987 said:
Followed all instructions, and the phone never rebooted. Not its not turning on. Tried vol up+home+power, vol down+home+power, battery pull, holding down power for 2 minutes. . .
The only thing I can think of is that I possibly unplugged the phone before the reboot after Step 4, just as soon as the phone shut down and before the actual reboot.
Anything you can help me with? I''m going crazy here.
Thanks
Click to expand...
Click to collapse
Did you run the Odin with the VRLAC bootchain file then you unplugged your phone before a full restart could take place? This is a very sensitive issue because that bootchain file unlocks your bootloader on your verizon phone. Your bootloader is everything to your phone. It controls how your phone starts and your phone can not work correctly if your bootloader became compromised in any way. I really hope you figured it out, and if you didn't maybe you could call your insurance company (if you have one) and get a new phone. If you are worried about rooting your phone again you could look on craigslist, there are always people/professionals willing to do it for very reasonable prices $10-$20. Again i really hope you figured this out and if you give me some more details maybe we can figure this out together.

Phone Rebel Method
This is the same method that Phone Rebel has on his YouTube channel for rooting d2vzw. This tutorial is missing one step that Phone Rebel covers, after running CF Auto Root, he flashes the corresponding bootchain file that goes with whatever firmware your phone is running. When I rooted, I was running VRBMB1, so I flashed that boot chain following the other two odin flashes. http://www.youtube.com/watch?v=K4b9hcWHrW8&feature=share&list=FL8Y3FM4mtznp0GQbwkkwaSg
What I've learned is that CF Auto Root does not unlock the bootloader and trying to flash a custom ROM with result in the dreaded triangle message every time. I was given this method: http://droidviews.com/2013/root-and...erizon-galaxy-s3-sch-i535-android-4-1-14-1-2/
to try instead. In this method you flash the VRALEC, then CWM recovery, then you can flash SuperSU with an unlocked bootloader via CWM, then flash the final bootchain file depending on the firmware you're running. Method 3 contains the casual root tool, but I've seen mixed reviews for that one.
At the suggestion of someone on the Google+ community for the SGS3, I"m gonna attempt to root VRBMF1 (JB 4.1.2 w/multiwindow) via method 1 and then flash the VRBMB1 bootchain for the previous version and see what happens.

UPDATE
ohemetophobia said:
This is the same method that Phone Rebel has on his YouTube channel for rooting d2vzw. This tutorial is missing one step that Phone Rebel covers, after running CF Auto Root, he flashes the corresponding bootchain file that goes with whatever firmware your phone is running. When I rooted, I was running VRBMB1, so I flashed that boot chain following the other two odin flashes. http://www.youtube.com/watch?v=K4b9hcWHrW8&feature=share&list=FL8Y3FM4mtznp0GQbwkkwaSg
What I've learned is that CF Auto Root does not unlock the bootloader and trying to flash a custom ROM with result in the dreaded triangle message every time. I was given this method: http://droidviews.com/2013/root-and...erizon-galaxy-s3-sch-i535-android-4-1-14-1-2/
to try instead. In this method you flash the VRALEC, then CWM recovery, then you can flash SuperSU with an unlocked bootloader via CWM, then flash the final bootchain file depending on the firmware you're running. Method 3 contains the casual root tool, but I've seen mixed reviews for that one.
At the suggestion of someone on the Google+ community for the SGS3, I"m gonna attempt to root VRBMF1 (JB 4.1.2 w/multiwindow) via method 1 and then flash the VRBMB1 bootchain for the previous version and see what happens.
Click to expand...
Click to collapse
You can use method 1 outlined in the droidviews link i posted yesterday to root the phone and when you get to the point where you're flashing the second bootchain you can flash VRBMB1 instead of needing VRBMF1 and it will work just fine! I also believe this method will truly unlock the bootloader for flashing custom roms, to avoid the yellow triangle of frustration, but I have no oversight on this as it was not my plan to do so.

VRBMF1??
I must admit that I am new to rooting.
I just bought a new S3 i535 with 4.1.2 and would like to root it. In the link provided there are files to download. One of these files are the bootchain... When I look in my settings, I see VRBMF1 and in the link provided I see.............
For VRBLK3 (Jelly Bean 4.1.1) Link
MD5: E3A1CB07DE214ED8081ED9D42C9BAF4A
For VRBMB1 (Jelly Bean 4.1.2) Link
MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1
For VRBMD3 (Jelly Bean 4.1.2) Link
MD5: 9CB65EAE8784807349EC3D4FF3A0AAEF
I am confused on what to do. I would imagine that this instructional post was created before I got my phone (07/13/2013) and thus is the reason why it might be missing from the instructions. Please advise me.

BKSinAZ said:
I must admit that I am new to rooting.
I just bought a new S3 i535 with 4.1.2 and would like to root it. In the link provided there are files to download. One of these files are the bootchain... When I look in my settings, I see VRBMF1 and in the link provided I see.............
For VRBLK3 (Jelly Bean 4.1.1) Link
MD5: E3A1CB07DE214ED8081ED9D42C9BAF4A
For VRBMB1 (Jelly Bean 4.1.2) Link
MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1
For VRBMD3 (Jelly Bean 4.1.2) Link
MD5: 9CB65EAE8784807349EC3D4FF3A0AAEF
I am confused on what to do. I would imagine that this instructional post was created before I got my phone (07/13/2013) and thus is the reason why it might be missing from the instructions. Please advise me.
Click to expand...
Click to collapse
Yes, the instructional post was created prior to you getting an S3. So, if you got into Settings> About Phone and look at your baseband version you'll probably see I535VRBMF1 and you'll probably see it again in another field just below it. This indicates that you're running the VRBMF1 firmware. That is JB 4.1.2 with multi-window. When using the root process in the droidviews article it outlines flashing VRALEC, then CWM touch, then using CWM to flash the supersu file, then flashing either VRBLK3, VRBMB1, or VRBMD3. Since none of those bootchain files match your firmware and there is no VRBMF1 bootchain on the forums, I flashed VRBMB1 since it was the the bootchain from the previous firmware. It worked. I successfully achieved root with no problems. Hope this helps.

Full on Noob, need help if possible.

Okay so, I love my Infuse but getting really tired of not being able to download anything off the play store. Just tired of it's rather less than great performance right now as well. It's is running 2.3.6 GB and want to get this thing up to ICS if possible. Just something running 4.0 so I can use my phone for what I need too. It is not rooted, no cyanogenMod, NOTHING. As the title says, I'm a full on noob here and I apologize if all this is covered in other threads, however I have just gotten to the point where I have found myself even more lost than where I started on what I needed to do/get. If someone can, I will literally need this spelled out to me (no pun intended), in order of the steps I need to take with everything. I'm getting tired of confusing myself even more from all the different stuff I have seen all over the place and I know without some serious guidance, I will just brick my phone. Thanks for any help! :laugh:

I understand this community can be a bit unorganized and confusing so I'll give you my process for rooting and installing custom firmware (there are other ways, but this works for my AT&T Infuse 4G SGH-i997).
First of all, no one uses ICS on the Infuse. There is a ROM, but it's underdeveloped because JB came out so quick. You will need to flash it to get to higher operating systems, but it is by no means a daily driver. Even JB is a little buggy compared to KitKat on the Infuse these days.
The first thing you want to do is root your phone and get a custom recovery.
There are more than a few options for rooting, but I prefer using ODIN (as I understand it, this is the tool Samsung uses to restore soft bricked phones). So this is a good thing to know how to do, in case you ever do soft brick your phone, you'll know exactly what to do.
Read the ODIN instructions in full as I will only briefly explain.
You're going to have to install Samsung drivers.
You'll be using UCLB3_Unbrick_root_1.1.zip. If you used UCLB3_Unbrick_1.1.zip it would just get you back to stock GB with no root added.
To put your phone into download mode, first turn off your phone. Plug a usb cable into your computer. Then with the phone off, hold down both volume buttons and plug the usb cable into your phone. A warning will come up and you push volume up to accept, realizing that you can easily soft brick your phone if you loose power or unplug during a download.
Once downloading is done, the phone will reboot and you'll be disappointed to see that nothing has changed. Except one small thing, you are now rooted and you should have an application called SuperUser that will allow you to do nifty and also dangerous things.
Now follow this step in the ODIN instructions to add the custom recovery (CWM = Clock Work Mod):
The version with root works exactly like the above version, but adds root. To add CWM recovery to the rooted version, download a custom Gingerbread kernel from HERE or HERE and flash the zImage using SGS Kernel Flasher (found in the Play Store) on the phone. If you go this route for root and CWM, your Custom Binary Download counter will not show any custom binary activity.
Click to expand...
Click to collapse
If you follow the link in the second "HERE," you'll get the kernel I prefer since it was most recently updated. Scroll down the downloads section and grab "2013.04.30-CWM-Synthesis-1.2Ghz.zip." (1.2Ghz is stock for our processor, anything higher will be overclocked which I don't recommend).
Extract that and grab the zImage file in the update folder. You're going to copy this to your phone in a second.
But first you need SGS Kernal Flasher, you can get it off the playstore, but I despise having to log in to an OS I'm going to write over in less than a minute so I download the APK from here. Hopefully you know how to install APKs from your SD card and that you'll have to check install from unknown sources.
Now flash the zImage using SGS Kernel Flasher. Your phone will reboot and hang on the Samsung logo and a creepy voice is going to tell you about how she's partitioning your phone and installing Voodoo lag fix. This is normal. Eventually your phone will reboot back into GB and you'll be ready to flash any ROM of your choice by rebooting into recovery.
You reboot into recovery by holding the volume up and volume down button while powering on the phone. This is different than download mode and will take you do a new screen that you control with the volume keys.
You'll be using this to put new software on your phone.
Now you can bassically follow the instructions for getting to CyanogenMod 11 (Kit Kat) from GB.
The first bullet is what I just explained in detail.
Note that I didn't include the links in these instructions, just follow the link above to get to the original post.
Obtain CWM, this can be done using Jscotts Odin back to stock (Follow instructions and use SGS kernal flasher to obtain CWM)
Run Qksters IMEI backup script here
Make certain you are on ICS, this can be done by flashing Entropy's CM9
It is recommended now that you remove your SD Card
CWM: Wipe Cache / Factory Reset
Install ROM: Scroll down for downloads sectoion
... The package will start to install..
... Phone will reboot into the install screen again...
... Continue to install [Automatically] If not manually flash again
... Phone will reboot again and be at the recovery screen...
Install Gapps: Here - Working swipe!
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
Click to expand...
Click to collapse
To be clear, when you flash a ROM, it won't be like flashing the zImage (that was just to get custom recovery). To flash the CM9 ROM or Qksters IMEI backup script for example, you leave the rom in the .zip file and simply put it on your SD card. Once in the recovery screen, you select "Install Update from ZIP" and navigate to the particular ROM you wish to install.
Also after updating to a higher version of Android, your phone will sometimes hang on the install screen for a long time. If it does for more than five minutes, it's safe to pull the battery and try flashing again (and sometimes necessary).
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Lately I've been using CyanFox and I have to say, it's the most stable ROM I've used in a while.
If you have any questions about this, feel free to ask.
Best of luck and happy flashing,
~bokonon9

Thank you muchness!
Thank you very much for helping me in this mess! I greatly appreciate it. I love my Infuse and do not want to get rid of it quite yet so hopefully this will help! Once I get a new usb cord I will get on this. My toddler decided to get a hold of it and it has to set a certain way now and can't be moved. This, is no bueno! Anyways, THANKS AGAIN!!! :laugh:

Goodluck! :laugh: :good:

I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Click to expand...
Click to collapse
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!

wwr said:
I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!
Click to expand...
Click to collapse
i would say go back to stock gb with odin and basically start over but with ics i always let it reboot to get a "feel" for it then i reboot to recovery and wipe basically everything then flash the next level of android which should be cm 10 then i let that boot then repeat that to get to kitkat 4.4.3 CarbonRom....sometimes you have to flash the same rom twice to get it to flash tho

I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall

wwr said:
I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2091900&page=370
read the last post on that page by scmfxt