Might be a noobish question but i cant seem to find anything, is there a root method for the latest firmware?
xblackvalorx said:
Might be a noobish question but i cant seem to find anything, is there a root method for the latest firmware?
Click to expand...
Click to collapse
You can use the latest SuperOneClick or you can flash a ROM/kernel that comes rooted. The latter of which can be found in the dev section. If you go that route, I highly recommend using one of bhundven's one-clicks to install 2.3.6 with CWM/root/voodoo lagfix. From there you can install a different custom ROM/kernel if you wish.
Or you can click on the first link in my signature and follow the guide.
stephen_w said:
You can use the latest SuperOneClick or you can flash a ROM/kernel that comes rooted. The latter of which can be found in the dev section. If you go that route, I highly recommend using one of bhundven's one-clicks to install 2.3.6 with CWM/root/voodoo lagfix. From there you can install a different custom ROM/kernel if you wish.
Click to expand...
Click to collapse
which superoneclick? the thread said something about modifying it, do you just download it and run or do i have to change something from the x10 options
http://forum.xda-developers.com/showthread.php?p=21954884
Look for rooting in this guide.
I also am trying to figure out how to root it. Most guides point to superoneclick, so I downloaded it, although on the shortfuse site there are plenty of complaints saying it is freezing at step 7. I read the guide and it says that since I'm already GB, I can install a rom/kernal combo that will root it in the process. I am wanting to run Valhall black and it doesn't say that a root is necessary in the directions, it just says place the .zip in the root of the SD folder.
Then I read in other places that superoneclick isn't necessary with stock GB, and point to Odin, and then some say Odin isn't necessary and point to "an easier way for stock GB" but then don't say what the easier way is.
The wiki says that one of the ways to root is to install a CWM voodoo lagfix kernel (which is included in Valhalla Black, I think) without needing to root.
Mindboggling
Follow the guide in the first link in my signature. It is very specific! If you have any questions let us know.
Root is necessary. You need to root, then follow the directions regarding SGS Kernel Flasher, then flash Valhalla Black. If you follow the guide you will be good. I tell you the version of SuperOneClick to use. It works. Don't worry about what ever else you read.
Thanks, so far so good. Kernel in progress.
This is for Lumin30
I clicked on your link and followed everything to the T but when it gets to step #7 on the oneclick, it sits an sits (which we wait and wait) but then the oneclick after about 15 minutes of waiting says not responding. Any help on that?
The link I posted? If so, close SuperOneClick and try it again. Make sure you have USB Debugging enabled. Let me know if you have any more problems.
Also, when you plug your phone is does your computer recognize the phone?
That would be the problem. When I plug my phone into the computer it doesnt read it when in debug mode, but if it isnt in debug mode I can as storage.
Sherbear said:
That would be the problem. When I plug my phone into the computer it doesnt read it when in debug mode, but if it isnt in debug mode I can as storage.
Click to expand...
Click to collapse
Open SuperOneClick - assuming you downloaded the version I recommended in the guide.
First thing to try is using a USB port you have not plugged your phone into yet that is directly attached to your computer - meaning no hubs or addon usb boards.
Try that. Let the computer install the drivers. It should say they installed and click Root.
Also - verify what you currently have on your phone before proceeding.
Lastly - you will need to refresh your browser to see my replies
That did it. Thank you so much. But now one last question. How do i find the IMEI to make sure it changed? It said rooted but everythings on my phones looks pretty much the same as it did before I rooted it. An also when it was rooting it said LOG: write failed (errno=14) alot. Does that matter?
Sherbear said:
That did it. Thank you so much. But now one last question. How do i find the IMEI to make sure it changed? It said rooted but everythings on my phones looks pretty much the same as it did before I rooted it. An also when it was rooting it said LOG: write failed (errno=14) alot. Does that matter?
Click to expand...
Click to collapse
Read this guide: http://forum.xda-developers.com/showpost.php?p=21953587&postcount=1
It will tell you how to find your IMEI and how to back up your EFS folder - which is VERY important. And you can go to Market, download 'Root Checker Basic' to verify you are rooted.
And hit thanks
---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------
If you do decide to use the guide above - please provide feedback if you think I left out any little steps, find anything not clear or have a suggestion to make the guide better.
OH HELL - YOU DO NOT WANT YOUR IMEI TO CHANGE. READ THE GUIDE!
I missed that part of your post!
Thanks for the help. I do have another question. If I want to change ROM's do I just flash them the same way or do I need to do something else first before I flash it? An by the way, the IMEI was still the same. I thought it was suppose to cahnge. Sorry this is my first time ever doing this.
---------- Post added at 04:16 AM ---------- Previous post was at 04:02 AM ----------
I just flashed a rom and now my phone is stuck omn the start up sceen and has been like that for 10 minutes now and doesnt do anything. It is stuck on the samsung Galaxy s screen. OMG
Uh oh. What were you on and what did you try to flash thag got you stuck?
Bionix_Frost_SGS4G
An used the sgs thing to flash
So you were on Bionic Frost? Or tried to flash Bionic Frost? I need to know what you were first on - then what ROM you tried to flash.
Tried to flash
Hehe. Ok. So you tried to flash Bionic Frost - a Froyo based ROM. And what were ROM were you using before you tried to flash Bionic Frost?
Sherbear
You are making me laugh. We will get this fixed. But I need to know what ROM you originally used. Or that can be said - what is the first ROM you flashed? I am assuming it was a GB based ROM but I was to confirm first before we proceed.
Hey everybody. I have a Samsung Captivate with CM7 installed. The other day it started bootlooping and I couldn't get it into recovery mode at all, so I ordered a Jig.
Now the Jig's here and I'm still not sure what I'm doing. I can't get into recovery with the button combos, so I'm kinda stuck. Any suggestions?
I would suggest that you use the jig to get into download mode, then do one of two things:
1. Flash a kernel that works with CM7 from Odin or Heimdall
2. Flash a stock rom from Odin or Heimdall, then reinstall CM7
You may want to try option 1 first, then option 2. If a bad kernel flash caused the issue in the first place, you might be able to save your installed programs & setup instead of having to wipe everything with a stock rom.
I've been trying unsuccessfully for the past couple of hours to flash back to stock. Odin keeps getting hung up on "Get PIT for mapping..." or the sbl.bin step. Maybe I'm doing something wrong or I have the wrong rom.
Anybody have a step-by-step? I'll owe you many thanks.
Otherwise I'll just have to go buy myself a Galaxy Note. Oh no.
See this Captivate Connection Issues and Download Mode Help
by jmtheiss
And u may need the Nexus drivers since u r on cm7 ??
ninja
Two things to try first:
1. Use a Heimdall-based one-click. There's one in my signature (if you were on Gingerbread bootloaders), or you can look in the Stock Rom collection in the Development section. Heimdall uses different drivers and interacts differently with the device.
2. Try a non one-click Odin setup. You'll need to get full Odin and then see if you can find a package to flash from inside of it. Do a little searching in the Development section and you should be able to find these items. Some newer Captivates don't respond well to the one-clicks.
If those don't work, look at the "Connection Issues" thread in my signature for more ideas (4-2ndtwin beat me to it. )
Hi guys I'm new to this flashing etc world. I used rom manager and installed the wrong clokworldmod and my phone only loads samsung galaxy s 4g screen. I saw the thread about not using rom manager but I already did yesterdey. I'm trying to gain access to download mode with odin but I'm not able to get in!
Drake316PR said:
Hi guys I'm new to this flashing etc world. I used rom manager and installed the wrong clokworldmod and my phone only loads samsung galaxy s 4g screen. I saw the thread about not using rom manager but I already did yesterdey. I'm trying to gain access to download mode with odin but I'm not able to get in!
Click to expand...
Click to collapse
yeah, ROM Manager is a bad thing when it comes to our phone.
ODIN does not put your phone in download mode. There are numerous ways to accomplish that and those are outlined in a few different posts here as well as the wiki.
Do you know if you were on Froyo or Gingerbread before you tried to flash something? Also, what ROM did you try to flash? Going from Froyo to Gingerbread, and vice versa, requires you to flash the proper boot loaders.
I suggest checking out Lumin30's [GUIDES] Fresh out of box Galaxy S 4G [SOLVED] | Heimdall One-Click For Dummies. Awesome guides and they should get you back to a working status.
Reply
I was on Gingerbread 2.3.6 something like that, I wanted to flash to Vahalla Black but didn't even get close to that process sorry for my english. I will check the guides thanks for the fast respond! Thanks again already on download mode!
No worries on the English; you did quite well
Let us know how it goes and if you need help. There are plenty of us here that can help. Once you get the one-click installed, you should be able to flash Valhalla Black with no problem.
Good luck!
Just fine I think
Sent from my SGH-T959V using xda premium
Thanks!!
Thank you very much!! Fixed my phone thanks to you and XDA! I will try to install a custom rom this time I hope to do it well thanks to the links you provided.
Question about flashing ROM
Hi, I fell I'm missing something I don't know where to start so I can flash my already rooted phone with Vahalla Black. Sometimes I read use CWM, other post dont use it,etc I feel lost here. Could you just let me know what I need to flash, software etc.
Drake316PR said:
Hi, I fell I'm missing something I don't know where to start so I can flash my already rooted phone with Vahalla Black. Sometimes I read use CWM, other post dont use it,etc I feel lost here. Could you just let me know what I need to flash, software etc.
Click to expand...
Click to collapse
Use the method in the guide in the first link of my signature. Look for Flashing Custom ROM's. You will be using CWM to get Valhalla Black on your phone. The guide has step by step directions.
Hello Canadian users with SGH-T959W!
I spent some time the last few days comparing the kernel source for SGH-T959W and SGH-T959V, and found they are exactly the same (plus a few fixes for us on SGH-T959V from the SGH-T959W source!)!
This is good for you, because we have unofficial cm7, cm9, aokp, et alii... ports for the SGH-T959V.
Maybe a forum admin could update the Samsung Galaxy S 4G forum to also say: SGH-T959V & SGH-T959W
Technically, the only real difference is that the stock roms for the SGH-T959W will have different pre-installed software. The hardware of the SGH-T959W is the same as the SGH-T959V.
Enjoy!
Read this stuff to continue:
http://forum.xda-developers.com/showthread.php?p=28566711#post28566711
BTW, if anyone has an odin or kies tarball, please PM me!
This way I can verify if the bootloaders are different or not, and if they are different, I can make you guys custom Heimdall OneClick and Odin packages.
bhundven said:
I spent some time the last few days comparing the kernel source for SGH-T959W and SGH-T959V, and found they are exactly the same (plus a few fixes for us on SGH-T959V from the SGH-T959W source!)!
Click to expand...
Click to collapse
Sorry to bump this thread, but out of curiosity, what were the fixes you were able to implement after seeing the kernel source for the 959W?
If it's something you'd rather not explain and will just be rolling out in future kernels, no big deal; just curious.
Thanks.
fingolfin14 said:
Sorry to bump this thread, but out of curiosity, what were the fixes you were able to implement after seeing the kernel source for the 959W?
If it's something you'd rather not explain and will just be rolling out in future kernels, no big deal; just curious.
Thanks.
Click to expand...
Click to collapse
The hardware is exactly the same. There is still a problem with the OTA Assert, meaning, how the rom knows if it is able to install on the phone or not during install from cwm. Also how it identifies itself to the play store.
I'm fixing this in the next cm9 unofficial release (coming soon, eta... a few hours, maybe).
The only real difference between SGH-T959V and SGH-T959W is the pre-installed/bundled software on the phone.
Everything else is one-to-one.
I'm still paranoid about bootloaders. So I'm still waiting for someone to post Kies or leaked tar.md5 for the SGH-T959W so that I can diff the bootloaders. If they are different, I will create new Heimdall OneClicks for SGH-T959W so that it is simple for you to go back to stock. See my current Heimdall OneClick thread to get an idea of what I mean.
On the other hand, we have some issues with our SGH-T959V bootloaders, and I have Unbrickable Mod on my phone. So, if the bootloaders are different, I would like to try flashing the SGH-T959W bootloaders to see if they work any better.
Also, there are a few fixes in the SGH-T959W kernel source that I will be incorporating into the current unofficial CM7 and CM9 ports I work on. Not having these fixes shouldn't have any negative impact on SGH-T959W.
I hope this info is informative. If not, ask more!
I have a SGH-T959W which seemed to have a bad flash already (from before.. and I am trying to revive it) on it (seems stuck on the cwm screen, and the system partition doesn't seem to have all the data that it needs to). Is there any way of getting the original ROM for this phone? Even if I install a cm build for the T959V, I don't get errors but its stuck in a cwm loop (keeps coming back to cwm).
When I try any of the one-clicks for the T959V, it succeeds on the kernel upload but always fails on the modem upload.
Where would you look for the Kies tar for this phone? Any possible way of getting the original ROM from a brand new phone? (any instructions for these would be great)
bhundven said:
The hardware is exactly the same. There is still a problem with the OTA Assert, meaning, how the rom knows if it is able to install on the phone or not during install from cwm. Also how it identifies itself to the play store.
I'm fixing this in the next cm9 unofficial release (coming soon, eta... a few hours, maybe).
The only real difference between SGH-T959V and SGH-T959W is the pre-installed/bundled software on the phone.
Everything else is one-to-one.
I'm still paranoid about bootloaders. So I'm still waiting for someone to post Kies or leaked tar.md5 for the SGH-T959W so that I can diff the bootloaders. If they are different, I will create new Heimdall OneClicks for SGH-T959W so that it is simple for you to go back to stock. See my current Heimdall OneClick thread to get an idea of what I mean.
On the other hand, we have some issues with our SGH-T959V bootloaders, and I have Unbrickable Mod on my phone. So, if the bootloaders are different, I would like to try flashing the SGH-T959W bootloaders to see if they work any better.
Also, there are a few fixes in the SGH-T959W kernel source that I will be incorporating into the current unofficial CM7 and CM9 ports I work on. Not having these fixes shouldn't have any negative impact on SGH-T959W.
I hope this info is informative. If not, ask more!
Click to expand...
Click to collapse
phaedrus81 said:
I have a SGH-T959W which seemed to have a bad flash already (from before.. and I am trying to revive it) on it (seems stuck on the cwm screen, and the system partition doesn't seem to have all the data that it needs to). Is there any way of getting the original ROM for this phone? Even if I install a cm build for the T959V, I don't get errors but its stuck in a cwm loop (keeps coming back to cwm).
When I try any of the one-clicks for the T959V, it succeeds on the kernel upload but always fails on the modem upload.
Click to expand...
Click to collapse
This is annoying, sorry you are going through this. It sounds like something dorked your param.lfs.
I've had this happen to me, and it always appends 'bootmode=2' to the kernel command line. Only way to fix it is to flash a new param.lfs from the stock image...
phaedrus81 said:
Where would you look for the Kies tar for this phone? Any possible way of getting the original ROM from a brand new phone? (any instructions for these would be great)
Click to expand...
Click to collapse
...which brings me to this part. Someone told me that they have this image, but when I asked them to post it somewhere, I got no response.
Bug Wind and Samsung for a kies mini or a stock image that you can flash to the phone. Samsung is probably not going to be as helpful as Wind, so I'd try bugging the crap out of Wind.
Hopefully someone will get me the tar.md5 soon, and we can get you guys a one-click with bootloaders (which includes the param.lfs).
If you feel bold/brave, you can try flashing the bootloaders from my Stock oneclick in my signature.
Since it should be the same hardware it should work the same. Granted after flashing your phone will now be a SGH-T959V and not an SGH-T959W.
I hold no guarantee that it will work, and/or that it won't try to shoot you at your favorite new 3d film. <.< ... >.>
Thanks for the info about what might be causing the cwm loop issue
I think I will the one-click with bootloaders a try (will update this thread with the results). At this point I think I have exhausted all other options to revive the device.
bhundven said:
This is annoying, sorry you are going through this. It sounds like something dorked your param.lfs.
I've had this happen to me, and it always appends 'bootmode=2' to the kernel command line. Only way to fix it is to flash a new param.lfs from the stock image...
...which brings me to this part. Someone told me that they have this image, but when I asked them to post it somewhere, I got no response.
Bug Wind and Samsung for a kies mini or a stock image that you can flash to the phone. Samsung is probably not going to be as helpful as Wind, so I'd try bugging the crap out of Wind.
Hopefully someone will get me the tar.md5 soon, and we can get you guys a one-click with bootloaders (which includes the param.lfs).
If you feel bold/brave, you can try flashing the bootloaders from my Stock oneclick in my signature.
Since it should be the same hardware it should work the same. Granted after flashing your phone will now be a SGH-T959V and not an SGH-T959W.
I hold no guarantee that it will work, and/or that it won't try to shoot you at your favorite new 3d film. <.< ... >.>
Click to expand...
Click to collapse
phaedrus81 said:
Thanks for the info about what might be causing the cwm loop issue
I think I will the one-click with bootloaders a try (will update this thread with the results). At this point I think I have exhausted all other options to revive the device.
Click to expand...
Click to collapse
Also, just to make sure you have tried different cables and computers.
Not being able to flash the modem sounds like a cable/computer issue.
If you have that issue while flashing bootloaders, you could hard-brick your phone.
The first time you flash with the oneclick, it will not flash bootloaders. The second time, the option to flash bootloaders opens up, but you still have to enable it.
Don't forget to read all the documentation in my thread before doing anything.
If you have any questions, ask before you do.
The Root Doesn't work. I follow the step and it damaged my phone! T959W
bhundven said:
Hello Canadian users with SGH-T959W!
I spent some time the last few days comparing the kernel source for SGH-T959W and SGH-T959V, and found they are exactly the same (plus a few fixes for us on SGH-T959V from the SGH-T959W source!)!
This is good for you, because we have unofficial cm7, cm9, aokp, et alii... ports for the SGH-T959V.
Maybe a forum admin could update the Samsung Galaxy S 4G forum to also say: SGH-T959V & SGH-T959W
Technically, the only real difference is that the stock roms for the SGH-T959W will have different pre-installed software. The hardware of the SGH-T959W is the same as the SGH-T959V.
Enjoy!
Read this stuff to continue:
http://forum.xda-developers.com/showthread.php?p=28566711#post28566711
Click to expand...
Click to collapse
I try your root process for my T959W now My phone Can't turn on . It turn on and off with the glaxy S 4G logo and T-Mobile . HELP PLS i tried to unroot It does work and It . PLS HELPPPP!!!!!
GMK63 said:
I try your root process for my T959W now My phone Can't turn on . It turn on and off with the glaxy S 4G logo and T-Mobile . HELP PLS i tried to unroot It does work and It . PLS HELPPPP!!!!!
Click to expand...
Click to collapse
Please be more specific as to which 'process' you followed and what you did.
Sorry I've been delayed in responding!
Again, if you can be more specific as to exactly what you did, I will be better prepared to help you.
It does look like it could be a cable/computer issue. I tried different cables and some of them didn't get as far as the modem (failed the kernel upload as well). Haven't got a cable which succeeds in the modem flash yet.
All of the driver stuff on windows makes me nervous though. Is there any way to flash this on linux. Does the one-click package work with fastboot or can fastboot be used to flash the individual pieces?
bhundven said:
Also, just to make sure you have tried different cables and computers.
Not being able to flash the modem sounds like a cable/computer issue.
If you have that issue while flashing bootloaders, you could hard-brick your phone.
The first time you flash with the oneclick, it will not flash bootloaders. The second time, the option to flash bootloaders opens up, but you still have to enable it.
Don't forget to read all the documentation in my thread before doing anything.
If you have any questions, ask before you do.
Click to expand...
Click to collapse
phaedrus81 said:
It does look like it could be a cable/computer issue. I tried different cables and some of them didn't get as far as the modem (failed the kernel upload as well). Haven't got a cable which succeeds in the modem flash yet.
All of the driver stuff on windows makes me nervous though. Is there any way to flash this on linux. Does the one-click package work with fastboot or can fastboot be used to flash the individual pieces?
Click to expand...
Click to collapse
These phones do not have fastboot, but they have download mode.
Yes, you can do this from: Windows, Linux, or Mac OS X
If you still have problems with multiple cables, I highly recommend trying a different computer. I've had this problem myself before. It drove me nuts until I got a friends laptop and everything worked perfectly. My laptop's usb ports had gone bad for some unexplainable reason.
Check out the wiki pages we have written:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
Steps I followed
managed to get my Wind SGH-T959W rooted and up and running with a unofficial CM9 build, but it took a bit of work.
Firstly, I tried just about every one-click solution out there, to no avail. It's possible SOC 1.7 with rattlethecage works, but I didn't have the patience to find out whether I simply had to wait a bit longer.
I followed this guide(whilst clenching every clenchable muscle I could consciously control):
http://www.galaxyforums.net/forum/of...ngerbread.html
The gist is, Odin 1.7, stock+voodoo for T959V, plus some update that I'm not qualified to describe. That should get you rooted and if that's all you're looking for, you'll have to suffer through a little T-Mobile branding on startup.
Once you got it all rooted, you'd think it'd be a good idea to toss sgs-ics on there, right? Well, no. After installing the 4G variant, it promptly set off into a boot loop which I'm again, unqualified to diagnose. The obvious solution was to try another team's version of ICS, which I indeed found here:
http://forum.xda-developers.com/show....php?t=1730954
Barring some missing features, it sounds like a good alternative to sgs-ics. Though I had to go through one additional step, which I really, honestly assure you I was under-qualified to execute. When I tried to load Team Acid's CM9 r3 it gave me an assert on the updater-script, since the hardware didn't match up. Easy. Unzip the package, open up META-INF/com/google/android/updater-script, remove the first check. You know it's the same hardware, you don't need some stinkin' script to tell you it won't work.
So all said and done, I now have a Wind Mobile SGH-T959W running ICS 4.0.4 courtesy of bhundven, the Odin folks, Team Acid, and likely a slew of other contributors.
Thanks folks, and enjoy!
PS, if you want that tarball bhundven, send me a PM with some brief instructions, and hopefully you can help my fellow Winders.
.......(---------THAT WHAT I FOLLOWED .
But I did the first part and They said i should get the stuff I store on my SD Card to pull out a file (``12) In CWM, use your volume up/down positions to navigate, scroll down to "Install Zip From SDcard". Select with a click of the power button. Navigate to where you put sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip (in the root of your SDcard) and select with the power button. Confirm you want to install.
``)
but it doesn't give me the option to go get it on my SDcard and Now my Phone just turns on and off with the samsung galaxy S logo plus T-mobile exclusive logo . The only possitive thing about all the damage is that I can still put my phone on dowload mode and I just think if someone knows how to get my phone back to it state they will need me to put it on download mode. :crying:
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Thank you in advance for your Help, for replying and offering to help.:highfive:
I appriciate it. My phone is Mobillicity carrier just like wind .
GMK63 said:
.......(---------THAT WHAT I FOLLOWED .
But I did the first part and They said i should get the stuff I store on my SD Card to pull out a file (``12) In CWM, use your volume up/down positions to navigate, scroll down to "Install Zip From SDcard". Select with a click of the power button. Navigate to where you put sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip (in the root of your SDcard) and select with the power button. Confirm you want to install.
``)
but it doesn't give me the option to go get it on my SDcard and Now my Phone just turns on and off with the samsung galaxy S logo plus T-mobile exclusive logo . The only possitive thing about all the damage is that I can still put my phone on dowload mode and I just think if someone knows how to get my phone back to it state they will need me to put it on download mode. :crying:
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Thank you in advance for your Help, for replying and offering to help.:highfive:
I appriciate it. My phone is Mobillicity carrier just like wind .
Click to expand...
Click to collapse
Ok, this is really simple. I've explained it in quite a few threads in the Galaxy S 4G forums in General, Q&A, and the Dev forum. I'm going to explain this, but in a way to be more general. So I'm being verbose in case anyone else with a T959W happens to run across this and has not tried anything yet.
Again, I'm not good with windows at all, and I prefer it that way.
If you're on windows, check out our wiki:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
There is tons of help there for setting up heimdall on windows with all the right drivers and such.
Once you have heimdall setup get AntonX's latest cwm zip for his kernel.
This kernel is a BML kernel, and this guide I am giving you right now will help you get cm9 installed which is an MTD kernel. You can find out more about BML vs. MTD here.
Once you have downloaded AntonX's kernel, extract the zImage from it and open up the terminal/cmd prompt and navigate to the directory you extracted the zImage to.
Put your phone into Download Mode and type the following in the command prompt:
Code:
heimdall flash --kernel zImage
The heimdall program will flash this kernel+initramfs to the kernel partition and reboot the phone. Do not unplug the usb cable until you see the "Galaxy S" screen. When you see that screen, unplug the usb cable and remove the battery from the back.
Assuming you downloaded CM9 and put it on your sdcard already, you can get into recovery by holding the vol+ and vol-, then pressing the power button to turn the phone on. When you see the "Galaxy S" screen, let go of the buttons, and you should be in the recovery now.
This is where things get a little tricky. If you have not tried to do anything to your phone yet. This would be a great time to use the "Backup and Recovery" menu on CWM. Do a full backup.
The "assert 7" error that the previous person got was because the cwm install script (the updater-script) checks the already installed /system/build.prop's data against the "to be installed" build.prop to verify this rom can be installed. If it doesn't exist, then it moves forward.
So the first order of business is to wipe the /system partition. Go to "Mounts and Storage" and format the system partition.
Now go back to the main screen and do "Factory Reset/Wipe Data".
Now go "Install zip from sdcard" -> "choose zip from sdcard" -> and use the volume keys to select the zip file.
After the rom is installed, navigate back to the main screen and "Reboot the system now" if it doesn't reboot by itself.
When the phone reboots, because it is going from BML to MTD, it obviously can't just install the files to what would be an MTD partition if the kernel knows nothing about MTD. So it boots into the newly installed MTD kernel and continues the installation, which in the end will also reboot again.
The first boot is very slow. It is building a cache of all the pre-installed system applications. Let it sit for a while. I know it's tempting to go play with your phone right away, but resist if you can.
The next CM9 release will be on a different kernel, and albeit a much better rom.
I will also be adding OTA Asserts for SGH-T959W so that you will not have to wipe /system before installing the rom, but I do that still just for good measure. But this also means that your phone will work properly with the google play store.
If this still does not work, please let me know what went wrong and I will be happy to assist!
-Bryan
Confused
bhundven said:
Ok, this is really simple. I've explained it in quite a few threads in the Galaxy S 4G forums in General, Q&A, and the Dev forum. I'm going to explain this, but in a way to be more general. So I'm being verbose in case anyone else with a T959W happens to run across this and has not tried anything yet.
Again, I'm not good with windows at all, and I prefer it that way.
If you're on windows, check out our wiki:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
There is tons of help there for setting up heimdall on windows with all the right drivers and such.
Once you have heimdall setup get AntonX's latest cwm zip for his kernel.
This kernel is a BML kernel, and this guide I am giving you right now will help you get cm9 installed which is an MTD kernel. You can find out more about BML vs. MTD here.
Once you have downloaded AntonX's kernel, extract the zImage from it and open up the terminal/cmd prompt and navigate to the directory you extracted the zImage to.
Put your phone into Download Mode and type the following in the command prompt:
Code:
heimdall flash --kernel zImage
The heimdall program will flash this kernel+initramfs to the kernel partition and reboot the phone. Do not unplug the usb cable until you see the "Galaxy S" screen. When you see that screen, unplug the usb cable and remove the battery from the back.
Assuming you downloaded CM9 and put it on your sdcard already, you can get into recovery by holding the vol+ and vol-, then pressing the power button to turn the phone on. When you see the "Galaxy S" screen, let go of the buttons, and you should be in the recovery now.
This is where things get a little tricky. If you have not tried to do anything to your phone yet. This would be a great time to use the "Backup and Recovery" menu on CWM. Do a full backup.
The "assert 7" error that the previous person got was because the cwm install script (the updater-script) checks the already installed /system/build.prop's data against the "to be installed" build.prop to verify this rom can be installed. If it doesn't exist, then it moves forward.
So the first order of business is to wipe the /system partition. Go to "Mounts and Storage" and format the system partition.
Now go back to the main screen and do "Factory Reset/Wipe Data".
Now go "Install zip from sdcard" -> "choose zip from sdcard" -> and use the volume keys to select the zip file.
After the rom is installed, navigate back to the main screen and "Reboot the system now" if it doesn't reboot by itself.
When the phone reboots, because it is going from BML to MTD, it obviously can't just install the files to what would be an MTD partition if the kernel knows nothing about MTD. So it boots into the newly installed MTD kernel and continues the installation, which in the end will also reboot again.
The first boot is very slow. It is building a cache of all the pre-installed system applications. Let it sit for a while. I know it's tempting to go play with your phone right away, but resist if you can.
The next CM9 release will be on a different kernel, and albeit a much better rom.
I will also be adding OTA Asserts for SGH-T959W so that you will not have to wipe /system before installing the rom, but I do that still just for good measure. But this also means that your phone will work properly with the google play store.
If this still does not work, please let me know what went wrong and I will be happy to assist!
-Bryan
Click to expand...
Click to collapse
I have Window 7 and I went on wiki. I don't know what rom or what I am suppose to download to get heimdall . Plus the steps is not for T959W.
GMK63 said:
I have Window 7 and I went on wiki. I don't know what rom or what I am suppose to download to get heimdall . Plus the steps is not for T959W.
Click to expand...
Click to collapse
:facepalm:
Then send your phone back to Mobillicity. Tell them that you don't know what a smart phone is and did something stupid to it. Go get yourself a nice clamshell phone.
I gave you explicit instructions that work for SGH-T959V and SGH-T959W. As a matter of fact, these instructions work on any "Galaxy S" phone, but you shouldn't flash just any other phone's rom to any other phone.
It just so happens that the SGH-T959V and SGH-T959W are the same exact hardware, just pre-packaged with different software and sold in different regions.
THEY ARE THE SAME PHONE!
With that, I am done with this thread. It was not meant for support! It was merely an announcement.
If you need any more help, please check out the Galaxy S 4G forums.
You can find plenty of directions that will work on either SGH-T959V or SGH-T959W on the wiki.
If you are looking for general information, look at the General forum.
If you need help or are asking a question, look at the Q&A (Questions and Answers) forum.
If you are looking to provide constructive feedback and/or logs to help development of ROMs and Kernels, check out the Developer forum. (Note, do not ask questions in the developer forum).
Don't forget the XDA Forum Rules
I followed the directions of this video on my SGS4G: http://www.youtube.com/watch?v=tR31U0KK2n8
I was trying to flash AOKP and everything went fine until it was finished but the phone went into a boot loop. I went back to "download mode" and attempted to try it again and it didn't work.
I could still get into download mode and flash anything but it wouldn't get past that. Then I decided to give up and I took out the battery and unplugged it (it wasn't downloading at the time). Now I can't even get into download mode, but the phone is would keep booting saying "Vibrant" and then it would go to a pixelated screen.
What should I do? Am I bricked? Can I fix this using Odin or something?
Thanks in advance
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Be mezmerized, and don't ever flash another rom besides the ROM's we have here.
The Vibrant IS NOT the SGS4G. The Vibrant is T959, the SGS4G is the T959V or T959W if you're in Canada. Hopefully 1-click will take you back, but if you flashed a Vibrant bootloader on your SGS4G, you may have bricked it. Hopefully someone with more knowledge can help you, because it seems you flashed the entirely wrong ROM to your phone because it's not for your phone and flashing the wrong bootloader is about the 1 thing that can really brick a phone good.
Looks like I did install the wrong boot loader for my phone which is the sgh-t959v, I used the vibrant instead...is there any way to fix this or am I filly bricked? I can't get into download mode, and the phone is in a boot loop
Try one of the one clicks here in this forum to bring you back to stock
Bhudven's Heimdall One Click and flash with bootloaders. Stay on stock. Read forums. Then keep being on stock ROM. JK... Then try eollie's Heimdall One Click or thomas' Odin Gremlin Remover. With these 2, you should be in a rooted stock ROM. When flashing a custom ROM, check the OP and read the instructions. Make sure it's for your phone.
*I'm tired of giving same instructions over and over again.
Solved
rbedell said:
Solved
Click to expand...
Click to collapse
Is there a tutorial anywhere I can use? Thanks in advance btw...
When I plug my phone into the computer I can get into download mode, I'm guessing from here you just flash back the stock Rom from Odin?
Also, when I use Odin to flash back to stock, do I need to download any other files other than the one specified in this link: http://forum.xda-developers.com/showthread.php?t=1353176
Thanks for everyone's help, I hate to be a bother
@ARsportsfan14
Use bhudven's Heimdall One Click. It's simpler.