Database Info

[AT&T][2.3.6]Heimdall One-Click Back-To-Stock UCKJ4 + Easy CWM install

Introduction
This package will totally reset your Infuse 4G to UCKJ4 . This package is intended for use on AT&T, however it will work with any device if you reset APN.
This package includes:
Repartitioning: Repartition to stock KJ4
Reloading: IBL/PBL, PARAM, SBL, SBL2, Kernel, Recovery, FactoryFS and modem
formatting:Cache and DBdata
This package does not wipe:
EFS(Where your serial number and carrier information is stored)
Data(where your market apps are stored)
SDCard (where your pictures are stored)
You may use this code to reformat the Data and SDCard *2767*3855# There is no way to do this from Download Mode. The code will leave the EFS untouched.
Download:
Download Total Stock UCKJ4
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions:
Get the latest version of java here: http://java.com/en/download/installed.jsp
Put your phone into "Download Mode"
Run the program once, and if it does not work, then check the "Flash Bootloaders" checkbox and flash again
Your device will end up as it came from the factory. You will be asked to set your device up again.
If you would like to install CWM on your device to restore or flash a custom ROM, I have prepared LinuxBozo's Defuse 1.5 kernel in a One-Click package here:
Download Defuse 1.5
To flash this package, follow the directions above.
Please note, this may not boot your device, but it will allow you to use CWM recovery. Hold the 3 button combo without USB plugged in to activate CWM mode.
How I created these package:
I obtained the stock 2.3 bootloader from a link LinuxBozo gave me
The stock part.pit came from my device using Heimdall(Download Pit option)
Uploaded the UCKJ4 firmware to my device
Performed "wipe data" in recovery mode
Exploited the root prompt at the battery charge sequence using UART and grabbed the stock, wiped dbdata/cache partitions and params.lfs partition
Created a Heimdall tar.gz package using Heimdall 1.3
Finally, I used my Heimdall One-Click *BETA* packager to generate these one-clicks
This procedure can be reproduced for any custom ROM in the future by using the dd command to obtain the factoryfs and kernels from any device. Bootloaders may be obtained from within this package as it is an executable JAR file which can be unzipped.

Thanks
Cranky...

Nice, I'll be using this when needed.
Also, you have a typo in your title, it's 2.3.6. :]
Sent from my phone. :3

AdamOutler said:
This is the current version pushed out on new Captivate devices today.
Click to expand...
Click to collapse
Wait, Captivate devices got an official update today? Wow.

Any downsides we should be worried about?

I copied the first paragraph from another post I made. That was a typo.

You might want to put the defuse kernel in another thread. Don't want people flashing 2.2.1 kernels on 2.3.6
Also might want to make a Hellraiser kernel version for people that Odin'd the leak or Rogers users that want a quick root/cwm without Odin

Dani897 said:
You might want to put the defuse kernel in another thread. Don't want people flashing 2.2.1 kernels on 2.3.6
Also might want to make a Hellraiser kernel version for people that Odin'd the leak or Rogers users that want a quick root/cwm without Odin
Click to expand...
Click to collapse
This package is posted as a method to get your phone back to stock and the defuse kernel provides easy access to cwm.. I had it around and it works. I tested before posting. Its there because it will give CWM. I will probly post a new one later with a 2.3.6 kernel but for now, this is how you get CWM on your device from Linux or Mac with one click.

I needed to flash the bootloader in order to get mine to boot up, but its been running for ~1 hour now and looks pretty nice. Offhand, do you know if HDMI is working for you? I'll go ahead and test after posting and I'll include my results here.
Edit: Nevermind, found cross-post with the results I needed. Stock kernel, HDMI works, rooted kernel (Entropy, etc.) breaks HDMI as they're based on Rogers roms.

HOw TO ROOT THIS ROM

cookieboy said:
HOw TO ROOT THIS ROM
Click to expand...
Click to collapse
Use defuse kernel, boot into CWM, then flash a rooted CWM zip. This ROM is very new.

nice work!

Only thing i noticed is that their is no stock ringtones with this rom.
Sent from my SAMSUNG-SGH-I997 using XDA App

Also want to add when you open facebook newsfeed, it wont let you select news, status updates, photos and etc. If you refresh the page while in app it will show you the list. Small bug i came acrossed. Let ya know if i find more.
Sent from my SAMSUNG-SGH-I997 using XDA App

After running stock UCKJ4 for a few hours, I seem to be having an issue where I get an error message saying my Google Talk authentication is not working, to make sure Chat is enabled on my account, as well as returning errors any time I try to install things from the Market. Anyone else running into this? Going to try removing and re-adding my Google account.
Edit: Crap, apparently you can't remove it without factory resetting. Damnsauce.

After factory resetting, things appear to be fixed. Thanks again for this package!
Sent from my SAMSUNG-SGH-I997 using xda premium

adalgiso said:
After factory resetting, things appear to be fixed. Thanks again for this package!
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
I had a similar problem. Downloading apps from market told me I had Insufficient space on the device. Clearing cache and Factory reset fixed the issue, Incase any others run into this.

Axiomkid said:
I had a similar problem. Downloading apps from market told me I had Insufficient space on the device. Clearing cache and Factory reset fixed the issue, Incase any others run into this.
Click to expand...
Click to collapse
Just to clarify, I was not receiving the insufficient space issue, I don't remember the exact wordage. 'There was an error' and nothing else.
---------- Post added at 12:30 PM ---------- Previous post was at 11:35 AM ----------
Attempting to root using zergRush exploit from here: http://forum.xda-developers.com/showthread.php?t=1321582
Will post results.
Edit: Check my thread here: http://forum.xda-developers.com/showthread.php?t=1332656

i was trying this everything seemed to work then it wouldnt boot so i did the flash bootloaders like it said, now nothing will work, not even the screen please help, im in dire need

steezinstangl said:
i was trying this everything seemed to work then it wouldnt boot so i did the flash bootloaders like it said, now nothing will work, not even the screen please help, im in dire need
Click to expand...
Click to collapse
oh boy, there is always a risk of permabricking when flashing bootloaders, (unless you did the unbrickable mod or have a jtag)
ok to start to see if you are actually permabricked;
1 pull your battery out
2 get a good micro usb cable, try this with more than one if you have to, if you had a problem flashing it may have been caused by the cable.
3 insert the cable into the usb port and into the computer.
4 hold both volumes with the phone face down, while the volumes are held slide the battery into position. see if the phone enters the download warning screen, it will ask you if you are sure you want to flash custom firmware, hit volume up. it may also go into a phone + computer screen or strait into download mode. all are good signs.
if you end up in download mode congrats! reflash!
if the screen is still black id recommend sending the device to connexion for jtag flashing or to adam if he is willing to repair it, these methods will void the warranty do to hardware modification (the repair may require soldering) . you may also atempt a warranty repair with samsung or insurance replacement with att but if they find that you are responsible samsung will charge you for the repair and im not sure what the insurance company will do.

Comparison of Clockworkmod recovery and TWRP

If you are a root user, you probably know what recoveries are, and you probably know what CWM and TWRP are. If you don't, please Google it, since this thread isn't about what recovery is...
I've been using CWM since my first Android device, Nexus S. However, after I switched to Galaxy Nexus, I've noticed this new recovery, which was TWRP, Team Win Recovery Project (Correct me if I'm wrong ).
Since I've used both as my daily recovery, I thought it'll be helpful for people to create a thread that compares these two
TWRP:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CWM:
These are version of recovery that I'm going to compare:
CWM version 6.0.1.0 Touch version for Galaxy Nexus
TWRP 2.2 for Galaxy Nexus
UI
Let's start with User Interface of these two recoveries. TWRP offers this fresh look that is not only easy to use, but also very intuitive. It has these big, yet polished buttons that makes using it a pleasure. I personally think that the UI is one of the strongest points of TWRP. CWM, on the other hand is just simple. It is just lines of options. For some, this might be great, but for a lot of people, including myself, it just not polished.
Navigation
Navigation is probably one of the most important elements of recoveries. TWRP offers really great navigation. Its "Swipe to Confirm" is one of my favorite, since this reduces the chance of flashing or wiping by mistake. It also offers this Back and Home button, which looks very familiar. CWM offers just easy-to-use navigation. That's it. Nothing too complicated. I find CWM to be just pick-it-up and flash kind of recovery.
Features
Now this is where TWRP shines big time. It offers soooooo many to the table than CWM. It has built in keyboard for naming backups and such. It has built in terminal, which can be pretty useful. It has built-in battery indicator and time, which is really handy. It also has built in file manager. It does all that with "basic features" such as flashing zip, factory resetting, mounting, and backup and restore. CWM just offers basic featues, nothing more. Of course, not a lot of people are gonna use terminal or file manager on recovery, but it is good to have a choice.
Compatibility
This is where CWM shines big time. Since, CWM was the only recovery until TWRP showed up, every mod and ROM is designed for CWM. Of course, since I am comparing Touch version, I have to mention that handful of mods doesn't work on CWM touch and only works on non-touch. This doesn't mean TWRP is only compatible with handful of mods. TWRP also works on most of the mods, but if there's a mod that you really want but only works on CWM, that can be a real pain in the rear end. Also I don't know if this also happens on other devices, but for Galaxy Nexus, if you want to flash stock ROM from Google developer site, TWRP won't let you.
Verdict
So which one is better? That's your personal opinion. Plus, I didn't create this thread to say which one is the best. I only created this thread so you guys know what each recoveries is right for you. I personally find CWM to be a little more stable and I find that CWM just works. However, TWRP offers these new and fresh features that advanced, and even just basic users and appreciate, but I still find that TWRP needs to work on some parts.
So which recovery do you use? I would like to know

I use TWRP for pretty much one reason only, it can mount through USB, which cwm can't do on the one s. Other than that I don't really find much difference in use, except that naming backups directly from recovery is nice
Sent from my HTC One S using xda app-developers app

Habarug said:
I use TWRP for pretty much one reason only, it can mount through USB, which cwm can't do on the one s. Other than that I don't really find much difference in use, except that naming backups directly from recovery is nice
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Oh there's no mount option on one s? You positive? Clockworkmod touch on galaxy nexus has that feature under mount I think. I can use adb to push files to the sdcard directory
Swyped on my Galaxy Nexus running AOKP nightly with Franco Kernel, overclocked to 1.4GHz

kyokeun1234 said:
Oh there's no mount option on one s? You positive? Clockworkmod touch on galaxy nexus has that feature under mount I think. I can use adb to push files to the sdcard directory
Swyped on my Galaxy Nexus running AOKP nightly with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
It's there, it's just that it does not work at least it did not work. I switched to twrp because of this and have never found a reason to switch back. On some units twrp also makes you able to flash boot through recovery (we don't have s off) but that doesn't work on mine.
Sent from my HTC One S using xda app-developers app

Habarug said:
It's there, it's just that it does not work at least it did not work. I switched to twrp because of this and have never found a reason to switch back. On some units twrp also makes you able to flash boot through recovery (we don't have s off) but that doesn't work on mine.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Haha ok
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

kyokeun1234 said:
I only created this thread so you guys know what each recoveries is right for you.
Click to expand...
Click to collapse
Should you not include 4EXT Recovery then also? That could be the right recovery for somebody.
kyokeun1234 said:
So which recovery do you use? I would like to know
Click to expand...
Click to collapse
Currently on 4EXT but wondering if I should go back to CWM.

Kavrocks said:
Should you not include 4EXT Recovery then also? That could be the right recovery for somebody.
Currently on 4EXT but wondering if I should go back to CWM.
Click to expand...
Click to collapse
Oops, I forgot 4ext :/ my apologies, but I never tried it, so I really can't give my opinion on it.
Swyped on my Galaxy Nexus running AOKP nightly with Franco Kernel, overclocked to 1.4GHz

Hello there !
I got question which could be silly for most of you but I really appreciate if someone would be nice to clear that for me.
When I want to do nandroid backup in clockworkmode recovery, everything is clean and simple. And backup folder is quite small. e.g. For Haier w910 that folder is about 25mb. And everything is saved. I can do wipe data formating and when I want back my earlier rom he is there with all settings and customisations.
When I try same thing to do through TWRP (on Huawei g510) I get few options for backuping. But if I want to backup all system and data and rom, TWRP shows me about 850mb.
Is there any options in TWRP to do nandroid backup of all system like in CWM Recovery ?
Thanks infront !

Good comparison.Anyway I love TWRP:laugh:

Another big plus for TWRP : its abitity to charge the battery.

MrAzerty said:
Another big plus for TWRP : its abitity to charge the battery.
Click to expand...
Click to collapse
Doesn't CWM do this as well? At least I've never noticed any battery drain when plugged in.

MattKneale said:
Doesn't CWM do this as well? At least I've never noticed any battery drain when plugged in.
Click to expand...
Click to collapse
Yup cwm also let the phone charge. Twrp just shows the battery percentage
Sent from my Nexus 4 using Tapatalk

Photon Q RSD Compatible FXZ

Thanks to Shabbypenguin for his fastbootable partitions of the Photon Q and thanks to mhous for modifying parts of the Atrix HD .xml file into the Photon Q.
This RSD Package contains 2 xmls for use, one standard one named after the build number, and one that does not flash the stock bootloader and is named as such. Put the one you want for use into RSD Lite and fire away. Have plenty of battery power (or use a Motorola Factory-Style cable or converter from Team Black Hat and you don't have to worry about that) and ALWAYS have your email from Motorola including the unlock code (UNIQUE_KEY) for your device backed up or saved somewhere. Just in case the fastboot locks it without you wanting it do, you'll have that code.
Use this file with Motorola's RSD Lite 5.7 or higher, and with the latest Motorola USB drivers.
Photon Q RSD Files / FXZ files: http://crackflasher.com/dev/mattlgroff/PhotonQ/7.7.1Q-6_SPR-89_ASA-36_SIGNED_CFC.zip
MD5: D864AB70881AF86EB225F0BF1D0A911B
RSD Lite 5.7: http://rootingmydroid.com/FILESYSTEM/DEVELOPMENT/UDPATES/-RSD-LITE/RSDLite57.zip
32 Bit Drivers (5.9): http://rootingmydroid.com/FILESYSTE..._End_User_Driver_Installation_5.9.0_32bit.msi
64 Bit Drivers (5.9): http://rootingmydroid.com/FILESYSTE..._End_User_Driver_Installation_5.9.0_64bit.msi
Happy flashing!

oh if you needed the xml i have that too. in fact i need to talk with you privately about some of the files. i posted up enough to fix anyones phone, but not everything in the zip

Do not flash this, it has bricked my phone... the MD5 for the system image is wrong, and even if you update that in the XML, it still fails to flash and remains stuck at fastboot flash failure. :crying:
Does anyone have the correct system image? I have sent shabbypenquin a PM trying to figure this out.

Gave this a try w the newest drivers & can't get past the system img. Tried several times, decrompressing new each time with no success. Even tried different cables & ports, still no luck.
Anybody have any thoughts on this?

bump...

thats teh word on the street. unfortunately the system.img is pulled from sprints files i dont know what else i could do to fix it

fallnSaint said:
Gave this a try w the newest drivers & can't get past the system img. Tried several times, decrompressing new each time with no success. Even tried different cables & ports, still no luck.
Anybody have any thoughts on this?
Click to expand...
Click to collapse
What state is your phone in? I can try to replicate as long as you're not soft-bricked.

shabbypenguin said:
thats teh word on the street. unfortunately the system.img is pulled from sprints files i dont know what else i could do to fix it
Click to expand...
Click to collapse
Well... $hit...
KitsunePaws said:
What state is your phone in? I can try to replicate as long as you're not soft-bricked.
Click to expand...
Click to collapse
Thanks KP, I'm not bricked; this is how I got into my "sticky" situation (pun totally intended). After system img failed, I was left in fastboot I flashed my recovery & restored. Other than the sticky fastboot, running fine. Well, I still haven't fixed my original problem but, that's for another thread.

Is this the same issue we are having w system.img?
http://www.xda-developers.com/android/swing-and-miss-motorola-razr-i-kernel-source-almost-here/
-Saint

any updates on a working rsd file?

Maxpowersxp said:
any updates on a working rsd file?
Click to expand...
Click to collapse
hopefully Motorola will release one. they said in the FAQs that they are choosing not to at this time, but hopefully they will at some point.
in the meantime, i wish we could make one. at this moment it seems we don't have any way of downgrading back to the original modem? (it was mentioned that there was a new modem in the update?)

Modified FXZ file
yogi2010 said:
hopefully Motorola will release one. they said in the FAQs that they are choosing not to at this time, but hopefully they will at some point.
in the meantime, i wish we could make one. at this moment it seems we don't have any way of downgrading back to the original modem? (it was mentioned that there was a new modem in the update?)
Click to expand...
Click to collapse
This package does not contain system.img!
This is here in case you break something that recovery does not touch.
If anyone has a problem with this being posted, let me know and I will pull the link. Props to mattlgroff for the original.
I edited the original file so that the broken system.img does not flash, everything else is unchanged. I tested this and it works fine.
I offer no support for this & it will wipe your internal sd card, you have been warned.
Modified 7.7.1Q-6_SPR-89_ASA-36_SIGNED_CFC.zip
md5: 851D8157D2A5ADE91E60ACCA0F04EA15

No problems whatsoever. I wanted to personally thank everyone on this forum for all of the dev help. When I unlocked my bootloader, I couldn't get CWM to flash properly, and I wound up erasing my ROM (don't ask lmao) and after 2 frustrating hours the posted boot.img & system.img files saved my phone. I am in everyone's debt, and I am willing to try out anything experimental for y'all now that I have TWRP and two good Nandroids. Thank u again for all of your help and hard work.
Sent from my XT897 using xda premium

I do have an issue each time i install the moto/sprint 77 update, my phone does nothing but reboot. I have a nandroid that is pre-update, but am I missing out on anything by not installing it? I rooted, installed arrgh's kernel and deodexed system before the update. Should i do an odexed system, stock kernel then update?
Sent from my XT897 using xda premium

I encourage all of you to
Sent from my XT897 using xda premium

drakeheart77 said:
I do have an issue each time i install the moto/sprint 77 update, my phone does nothing but reboot. I have a nandroid that is pre-update, but am I missing out on anything by not installing it? I rooted, installed arrgh's kernel and deodexed system before the update. Should i do an odexed system, stock kernel then update?
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
That's what I hear... You would probably get a better response and more help if you posted in the correct thread tho. The update thread is here: http://forum.xda-developers.com/showthread.php?t=1966998
-Saint

Ooops sorry thanks for the correction!
Sent from my XT897 using xda premium

fallnSaint said:
If anyone has a problem with this being posted, let me know and I will pull the link. Props to mattlgroff for the original.
I edited the original file so that the broken system.img does not flash, everything else is unchanged. I tested this and it works fine.
I offer no support for this & it will wipe your internal sd card, you have been warned.
Modified 7.7.1Q-6_SPR-89_ASA-36_SIGNED_CFC.zip
md5: 851D8157D2A5ADE91E60ACCA0F04EA15
Click to expand...
Click to collapse
This kind of worked for me. I was able to get out of the bootloader screen, but now it's stuck on the initial screen with just the red Motorola circle.
Any ideas on what I'm doing wrong?

Stefenatefun said:
This kind of worked for me. I was able to get out of the bootloader screen, but now it's stuck on the initial screen with just the red Motorola circle.
Any ideas on what I'm doing wrong?
Click to expand...
Click to collapse
Without more details as to what caused your problems originally I am kinda in the dark. I would guess that you have a problem with your system img, this RSD package should revert everything except system to stock. The bad news here is that if you did have a custom recovery, you don't anymore. If you have a good backup you will have to fastboot flash recovery again before you can use it. If you don't have a backup see here: http://forum.xda-developers.com/showpost.php?p=33391825&postcount=9
-Saint

fallnSaint said:
Without more details as to what caused your problems originally I am kinda in the dark. I would guess that you have a problem with your system img, this RSD package should revert everything except system to stock. The bad news here is that if you did have a custom recovery, you don't anymore. If you have a good backup you will have to fastboot flash recovery again before you can use it. If you don't have a backup see here: http://forum.xda-developers.com/showpost.php?p=33391825&postcount=9
-Saint
Click to expand...
Click to collapse
What I did was I went into the bootloader, flashed the zip, and rebooted after it finished. Now I am unable to access the bootloader, as the phone won't boot. By now, the battery's dead, anyways. Whenever I turn the device off, it turns on a couple seconds later. I would rather not take it apart, but if I have to, I'll do it.
The only thing I can access is the recovery, which just results in this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[GUIDE][ICS]How to root stock

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
presents....
A guide to root the new ICS UVLH5 firmware update.
This guide will try and make it very easy to root your stock firmware for those of you who are having
problems or don't want to wait for a stock rooted rom
anyways here goes the step by step assuming that you have a Samsung Galaxy S Blaze 4g T769 and are on ICS
UVLH5 firmware.
Before anything of course you'll need the files and here they are:
ClockWorkMod Recovery
Blaze Pit
Odin 1.8.5 Zip
SuperUser Zip
After downloading all the files first move the Superuser.zip to the root of your sdcard..not internal sdcard but the removable one. Then unzip the Odin zip and once unzipped:
Step 1:
Run Odin 1.85.exe, and prepare Odin:
Check "auto-reboot", and uncheck all other options.
Click PDA and select the TAR for clockworkdmod you downloaded. Click PIT and select the Blaze PIT your downloaded.
DOUBLE CHECK THAT YOU HAVE REPARTITION UNCHECKED
Step 2:
Connect the USB cable to your PC, but NOT your device.
Remove the battery.
Reinsert the battery.
Hold down Volume Up + Volume Down
Then while holding the voume keys plug in USB cable
You should now be in Download Mode
Step 3:
Make Sure repartition is still unchecked and click START in Odin.
Step 4:
When done the phone will reboot to the OS after this you have to reboot to recovery, here are a few ways.
1. adb command: adb reboot recovery
2. volume combo.
a. turn off phone.
b. hold volume + and volume -
c. while holding the volume buttons hold the power button for 10 seconds
d. after the 10 seconds release power button but keep holding volume buttons until you get into CWM recovery
Step 5:
Flash the SuperUser zip file
Step 6:
Reboot to System
Step 7:
Check whether root took or not.
Step 8:
If it did come back here and click thanks
Credits:
CWM (shabbypenguin)
Odin 1.8.5 (k0nane)
SuperUser (chainfire)
Hosting (gfx.myst)
TFQ ( cus we here to help )

Because I can lol

Do we need to update via kies first?
Sent from my SGH-T769 using xda app-developers app

Wait I did this a little earlier and I didn't flash the pit. Will this cause any problems down the road?
Sent from my SGH-T769 using xda app-developers app

shaikmonster said:
Do we need to update via kies first?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Yes or use the tar file a user uploaded around here a bit earlier.
KrimsonChin said:
Wait I did this a little earlier and I didn't flash the pit. Will this cause any problems down the road?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
If it flashed fine then I don't think it'll cause you any problems down the road.

Can I do this on Mac?
Sent from my SGH-T769 using xda app-developers app

Where in the process do we do the downloaded tar file?

im_awesome_right? said:
Can I do this on Mac?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
nope just for windows as Odin is only windows compatible
shaikmonster said:
Where in the process do we do the downloaded tar file?
Click to expand...
Click to collapse
the TAR file is the CWM recovery

im_awesome_right? said:
Can I do this on Mac?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I dont think there's a MAC version of Odin.... if you can somehow flash the CWM, you're golden. until then... ::shrugs::

Do I just drag the superuser zip to sd? gotta make sure..

erikmm said:
nope just for windows as Odin is only windows compatible
the TAR file is the CWM recovery
Click to expand...
Click to collapse
The ics tar file

Worked for me
Thanks erik! Looks like I've got root!

motez23 said:
Do I just drag the superuser zip to sd? gotta make sure..
Click to expand...
Click to collapse
you can. or download it. the important part is remembering whether its on your internal or external SD card when you go to flash it in CWM. as long as the MD5 is good, you're good as I figured out yesterday, my work computer messes with MD5's like a mutha******

I didn't expect to be able to do that so easily, but it all worked! Thanks much.

I had used the first stock root posted here, but didn't bother updating it to the minor patch that was released. I updated to ICS using Kies, knowing that I would lose root, and since my phone was rooted I was half expecting it to not work.
Well it did, and it almost worked too well. I was pleasantly surprised that I didn't even lose any apps or settings in the process. I lost root of course, although surprisingly superuser is still loaded on the phone. (I've confirmed the phone is not still rooted)
Anyways, my memory is a bit foggy, but doing this process is a total wipe on the phone right? I might even prefer that.

Cirkustanz said:
I had used the first stock root posted here, but didn't bother updating it to the minor patch that was released. I updated to ICS using Kies, knowing that I would lose root, and since my phone was rooted I was half expecting it to not work.
Well it did, and it almost worked too well. I was pleasantly surprised that I didn't even lose any apps or settings in the process. I lost root of course, although surprisingly superuser is still loaded on the phone. (I've confirmed the phone is not still rooted)
Anyways, my memory is a bit foggy, but doing this process is a total wipe on the phone right? I might even prefer that.
Click to expand...
Click to collapse
The first couple boots will be laggy. That's the nature with any rom
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

I'm rather confused by your quoting my reply, and not replying to it.

Cirkustanz said:
I'm rather confused by your quoting my reply, and not replying to it.
Click to expand...
Click to collapse
honestly, as am i, as my reply had nothing to do with your post perhaps a lack of sleep, perhaps a miss click, idk. but I guess we never will

I wish I read this thread sooner.
Here's my situation:
I had a rooted Gingerbread stock ROM that I upgraded to the official ICS update using Kies. I then used the same ODIN method to root the phone and now it won't boot up past the "Samsung Galaxy S" loading screen. Any ideas on where to go from here? I'm afraid if I do anything else haphazardly, I would only be digging myself deeper into this hole.
Thank you!

You flashed a GB kernel on ICS. If I were you, I would flash a GB .tar using Odin (unless you can find an ICS .tar somewhere?). Then, boot into recovery and wipe system and data, because you'll see a blue ICS menu flickering in the background upon booting up into the GB phone setup screen. At least, that is what happened to me. Then, upgrade to ICS using Kies.
Sent from my SGH-T769 using xda app-developers app

[Help] Phone Won't Leave Recovery

Hey guys. First I'd like to aplogize for posting so many help threads but I'm trying my best to figure it out on my own.
I was using one-click to stock when my mother dropped something and needed my help urgently, so I told my brother to start it up for me as my phone was already plugged in and connected. I am running the T959W rather than the T959V and my brother clicked on the option to flash bootloaders. The download was completed normally I think. However, my phone will not leave the recovery mode.
Could you guys please help? Thanks.
When flash bootloaders was hit on T959V back to stock, my brother said it said "MODEM UPLOAD FAILED ENDING SESSION". My guess is that it cleared my boot loader and then since it failed while trying to upload the modem, it ended the session without readding a boot loader? It continously says "MODEL UPLOAD FAILED" Whenever I attempt to use the T959V back to stock.
Edit:
I have tired the back to stock for T959W from: http://forum.xda-developers.com/showthread.php?t=1956025
However, I get these error messages.
Kernel is missing because I removed it out of the package hoping maybe it'd solve the problem since it was also failing, but so is recovery...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

WayTooGosu said:
Hey guys. First I'd like to aplogize for posting so many help threads but I'm trying my best to figure it out on my own.
I was using one-click to stock when my mother dropped something and needed my help urgently, so I told my brother to start it up for me as my phone was already plugged in and connected. I am running the T959W rather than the T959V and my brother clicked on the option to flash bootloaders. The download was completed normally I think. However, my phone will not leave the recovery mode.
Could you guys please help? Thanks.
Click to expand...
Click to collapse
Try instilling a new ROM
Sent from my SGH-T959V using xda app-developers app

Cooptx said:
Try instilling a new ROM
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I have tried installing AOKP Milestone 6 by team acid unofficial (ICS) and CM10 (JB) but the same thing keeps occuring.

I think you should look here if you haven't already
http://forum.xda-developers.com/showthread.php?t=1956025

TwitchyEye said:
I think you should look here if you haven't already
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
Yes I was trying that but for some reason it just kept failing "KERNEL UPLOAD FAILED" "RECOVERY UPLOAD FAILED"

WayTooGosu said:
Yes I was trying that but for some reason it just kept failing "KERNEL UPLOAD FAILED" "RECOVERY UPLOAD FAILED"
Click to expand...
Click to collapse
Sometimes heimdall is finicky so if you know for sure you got the drivers working and you followed instructions properly trying it a couple times in a row might do it....although I guess if you say it keeps failing that would imply more than once...

TwitchyEye said:
Sometimes heimdall is finicky so if you know for sure you got the drivers working and you followed instructions properly trying it a couple times in a row might do it....although I guess if you say it keeps failing that would imply more than once...
Click to expand...
Click to collapse
Yes it has failed every attempt (I''ve tried about 10 times).

At this point you should really start fresh maybe even a different computer and see if you get anywhere. Typically if it's not working it's a driver issue and you gotta get rid of all the drivers related to the phone and reboot, then re-install them using zadig...and maybe reboot again.

TwitchyEye said:
At this point you should really start fresh maybe even a different computer and see if you get anywhere. Typically if it's not working it's a driver issue and you gotta get rid of all the drivers related to the phone and reboot, then re-install them using zadig...and maybe reboot again.
Click to expand...
Click to collapse
I think the driver is being recognized fine because it is being recognized by ZDiag, T959V back to stock program, Hemidall. I am not quite sure what the problem is :|.

WayTooGosu said:
I think the driver is being recognized fine because it is being recognized by ZDiag, T959V back to stock program, Hemidall. I am not quite sure what the problem is :|.
Click to expand...
Click to collapse
Maybe the gods will chime in about now...?

I suggest using a new pc too. Sometimes its a simple conflict that is causing the problem and a different pc will fix it every time.

Try a different cable/port combo? Sometimes cables die at the worst times....
Sent from my SGH-T959V using xda app-developers app

eollie said:
I suggest using a new pc too. Sometimes its a simple conflict that is causing the problem and a different pc will fix it every time.
Click to expand...
Click to collapse
Hmm, I just tried it on my laptop, back to stock T959V flashs just fine however I still ahve the issue of being stuck in recovery mode but I can't get T959W to work still.

WayTooGosu said:
Hmm, I just tried it on my laptop, back to stock T959V flashs just fine however I still ahve the issue of being stuck in recovery mode but I can't get T959W to work still.
Click to expand...
Click to collapse
When flash bootloaders was hit on T959V back to stock, my brother said it said "MODEM UPLOAD FAILED ENDING SESSION". My guess is that it cleared my boot loader and then since it failed while trying to upload the modem, it ended the session without readding a boot loader? It continously says "MODEL UPLOAD FAILED" Whenever I attempt to use the T959V back to stock.

The problem is you are using the V HOC's there is a package for W phones on the forums.

eollie said:
The problem is you are using the V HOC's there is a package for W phones on the forums.
Click to expand...
Click to collapse
Yes I realize that however, I checked the T959W thread and they said there were no bootloaders. And that is likely the thing that is messed up right now. Thanks for your help!

I think there's no way to flash bootloaders on W's and the package that's specifically for the W was designed just for this purpose, to bring back a phone that's messed up from attempting to flash V bootloaders. Have you tried downloading it again? If that's the only one you have trouble with maybe it's just a bad download.
---------- Post added at 11:54 PM ---------- Previous post was at 11:52 PM ----------
Oh also you can go in and uncheck flash modem on the one-click and the rest of it should work just fine. I think.

TwitchyEye said:
I think there's no way to flash bootloaders on W's and the package that's specifically for the W was designed just for this purpose, to bring back a phone that's messed up from attempting to flash V bootloaders. Have you tried downloading it again? If that's the only one you have trouble with maybe it's just a bad download.
---------- Post added at 11:54 PM ---------- Previous post was at 11:52 PM ----------
Oh also you can go in and uncheck flash modem on the one-click and the rest of it should work just fine. I think.
Click to expand...
Click to collapse
How do you disable things from being flashed on the V back to stock?

WayTooGosu said:
How do you disable things from being flashed on the V back to stock?
Click to expand...
Click to collapse
This might help me just get the boot loaders fixed!

here is the deal unless you worked some weird voodoo magic you never flashed the V's bootloaders. There is a partition in there that will not allow it to work properly.
Rereading getochkn's instructions you should not be flashing the bootloaders as he DID NOT include them. Follow his directions to the letter. Dont use the one clicks for the V. I remember chatting with him in IRC while he was trying to figure this out and he could NOT flash a hoc for the V with bootloaders successfully I dont even think it worked without bootloaders.