Welcome T959W users. This guide and package should help you either root your 959W, get it back to (almost) stock, get you out of a boot loop, or get you on your way to installing one of the variations of Ice Cream Sandwich.
The T959W is hardware wise 100% identical to the T959V but there are a few small stock software differences that cause problems using some of the initial T959V tools. Though risking my own phone and the help of I think just about all the Team Acid members, I have learned a lot and gotten a close to a stock dump as possible.
As of now, there is no 100% back to stock package for our phones. I have tried without success in getting a stock image from Wind or Samsung. They have both told me to ask the other one. Maybe someone can try Mobilicity or try Wind again and see what they say. It would greatly help me make a fully stock package, and understand any of the small differences. The T959V users got the phone when it came with Android 2.2 and an update was released to 2.3 for them, thus giving them the ability to have a stock image as it was provided. The W variant comes with 2.3 stock, so therefore no upgrade package exists for us and leaves us without a way to return to fully stock.
If you messed up your phone trying a different package, I can help get it 99% stock, or rooted and get you setup to install other ROM’s.
With that said, the standard disclaimer applies.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or
* unfulfilled sexual partners. Please do some research if you have any
* concerns about features included in this ROM before flashing it! YOU are
* choosing to make these modifications, and if you point the finger at me
* for messing up your device, I will point that finger back at you and laugh.
* Then I will put it in your eye.
*/
By using the ROM you agree with the above terms!
First, I will assume some things as this is not a tutorial thread.
You can get your phone into download mode.
You have the Samsung drivers installed.
You can follow basic step by step instructions.
1) Download Heimdall 1.3.1 SUITE for the OS you are using from HERE Don't use 1.3.2 or any other versions, 1.3.1 works, so why screw with stuff and try something I don't recommend? Make sure to get the suite or the full package and not just the command line. Make sure you have the C++ libraries installed for Windows users. It's right underneath the download link I linked below.
This is the one for Windows, which I assume most users will be using. Others, download the suite for your OS
{
"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"
}
2) Download my package HERE. DO NOT UNCOMPRESS IT, LEAVE IT AS IS.
3) Unzip/uncompress the Heimdall package to a folder on your pc/mac
4) Put your phone into download mode
5) Startup the Heimdall-Frontend program with your preferred method depending on your OS (run that program)
6) Click on the utilities tab and click on the Device Detected button. If it shows device detected, proceed to the next step. If it doesn’t find your device and you are in download mode, it’s a drivers issue and read HERE for instructions on how to get the proper drivers working using the Zdiag software included with the Heimdall package. Ignore the 1click part of the linked thread, but follow the rest. you will have to run Zdiag manually from the "drivers folder" of the Heimdall suite.
7) Only process to this step when have determined that your device is detected by Heimdall.
8) Click on the first Tab in Heimdall Frontend that says Load Package. Click on the browse button and load up the T959Wpackage you downloaded in step 2. It may take up to 10 minutes for your PC to uncompress the files depending on the speed of it. Don’t rush it, waiting till all the messages are gone and the LOAD/CUSTOMIZE button is active, click on that button
9) This will bring you to the FLASH tab. Make sure repartition is CHECKED (it should) and don’t touch anything else. Finally, click on the START button at the bottom. Let it do it’s thing, it will take about 5 mins and then your phone will reboot. It will take another few minutes here before your phone fully boots and you are at the Google Setup screen.
10) Made it this far? Great, now you have saved your phone from a brick, but there are a few things that aren’t working yet, so don’t panic that you have no signal yet or no wifi, etc. We can fix those things fairly easily IF YOU CAN FOLLOW INSTRUCTIONS AND READ AND NOT RUSH. If you start whining you have no signal after step 9 and don’t read anymore or follow my instructions on how to flash the proper modem, I’ll ignore you. These are all proven steps, tested by thousands of people on these forums that aren’t impatient and do what they are told.
Now, the 3 choices you have.
1) Flash to an Ice Cream Sandwich Variation. If this is the case , Download the ROM you want to your SD card, reboot your phone into recovery and flash according to the directions given by the ROM you want to flash. I won’t answer questions why you can’t flash XXX ROM, your phone will be rooted with recovery using my method, and the rest of the information is out there.
2) Return to the 99% stock option (this will bring the phone exactly how you got it BUT will say T-mobile when you first boot it up. I have no way to fix this currently as I have no stock kernel to use. (hint, bug Wind or Mobilicity for the package and get it to me) Will work on this part.
3) Keep the phone rooted with recovery on Gingerbread. The kernel included in this is Blastoff kernel, which wifi doesn’t work off the start, so you can go to the Blastoff thread HERE and learn how to fix wifi, flash Antonx’s Basic with a Twist HERE or another compatible GB kernel, all from recovery. You will also need to flash a modem. I suggest the LB6 modem that came stock on our phones from, available HERE for GB and ICS, pick the correct one. Again, I provide no support for Blastoff or Basic with a twist or flashing them or something.
So to summarize, this will get your T959W with a rooted kernel and CWM version 5.2.something. Wifi will not work and there is no modem flashed, so read the above step if you want to fix those, read how to do that yourself, etc. I don't want any questions about CM9 or Blastoff or Heimdall or Jelly Bean or anything here. The above steps works if you're not all OCD and rush through and read my steps. I have tested them and the package probably 50 times and I'm doing it again right as I finish typing this all out, so it works. If you still have trouble, and explain in a detailed way what didn't work, I may help. If you SPAZ out that something didn't work and don't explain the steps and demand help, you will be ignored. You risk doing damage to your phone anytime you flash it and void warranties, so that is the risk and I assume none. This package works, the steps I have tried to detail in as much detail as possible including screen shots and everything and have spent hours making and testing the package, taking screenshots, detailing all this, all for the benefit of others as my phone works fine and I never bricked it because I took the time to read, so please read this thread 3 times over before you proceed.
Anyways, hope this helps, give me a Thanks if it does and a Thanks to any Team Acid members posts you see, as they have helped me get to this point.
Now we need to get you on the one click bandwagon and we'll be set for Linux and OS X users
FBis251 said:
Now we need to get you on the one click bandwagon and we'll be set for Linux and OS X users
Click to expand...
Click to collapse
Soon as Heimdall can flash the modem properly, I will. lol. It fails, git issue opened on it, gave Heimdall dude all my logs, so we'll see. Also, since most people get bootlooped and mess up the param, and other files trying to flash everything under the sun, this package was the best way to do everything in 1 step.
The package though will work for linux/osx, etc, just use that Heimdall version. I just have Windows directions as I assume most people will be on Windows. You can load the gz though into any Heimdall and flash it.
getochkn said:
Welcome T959W users.
*********
Great Job man.
That was just awesome and a single click did the trick.
As instructed , i installed an ICS and that took care of the modem & signal as well.
Thank you so much.
Click to expand...
Click to collapse
Was it necessary to quote the entire post?
Hi getochkn,
Thanks for this very informative guide.I seriously thought my son's phone was bricked, but after following your instructions, everything was restored perfectly.The only hiccup I had was, at step #6 Heimdall showed the device as detected, but when I went to flash it, it said that it couldn't detect the device.So I installed the drivers manually through Zdiag and it was smooth sailing from there.
I then flashed CM9 and noticed in your sig that you are running RemICS Rom so I flashed that and everything is looking great so far.
Thanks for taking the time to make this guide for those on the T959W
Glad it worked for you and you saved the phone.
getochkn said:
Welcome T959W users. This guide and package should help you either root your 959W, get it back to (almost) stock, get you out of a boot loop, or get you on your way to installing one of the variations of Ice Cream Sandwich.
The T959W is hardware wise 100% identical to the T959V but there are a few small stock software differences that cause problems using some of the initial T959V tools. Though risking my own phone and the help of I think just about all the Team Acid members, I have learned a lot and gotten a close to a stock dump as possible.
As of now, there is no 100% back to stock package for our phones. I have tried without success in getting a stock image from Wind or Samsung. They have both told me to ask the other one. Maybe someone can try Mobilicity or try Wind again and see what they say. It would greatly help me make a fully stock package, and understand any of the small differences. The T959V users got the phone when it came with Android 2.2 and an update was released to 2.3 for them, thus giving them the ability to have a stock image as it was provided. The W variant comes with 2.3 stock, so therefore no upgrade package exists for us and leaves us without a way to return to fully stock.
If you messed up your phone trying a different package, I can help get it 99% stock, or rooted and get you setup to install other ROM’s.
With that said, the standard disclaimer applies.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or
* unfulfilled sexual partners. Please do some research if you have any
* concerns about features included in this ROM before flashing it! YOU are
* choosing to make these modifications, and if you point the finger at me
* for messing up your device, I will point that finger back at you and laugh.
* Then I will put it in your eye.
*/
By using the ROM you agree with the above terms!
First, I will assume some things as this is not a tutorial thread.
You can get your phone into download mode.
You have the Samsung drivers installed.
You can follow basic step by step instructions.
1) Download Heimdall 1.3.1 SUITE for the OS you are using from HERE Don't use 1.3.2 or any other versions, 1.3.1 works, so why screw with stuff and try something I don't recommend? Make sure to get the suite or the full package and not just the command line. Make sure you have the C++ libraries installed for Windows users. It's right underneath the download link I linked below.
This is the one for Windows, which I assume most users will be using. Others, download the suite for your OS
2) Download my package HERE. DO NOT UNCOMPRESS IT, LEAVE IT AS IS.
3) Unzip/uncompress the Heimdall package to a folder on your pc/mac
4) Put your phone into download mode
5) Startup the Heimdall-Frontend program with your preferred method depending on your OS (run that program)
6) Click on the utilities tab and click on the Device Detected button. If it shows device detected, proceed to the next step. If it doesn’t find your device and you are in download mode, it’s a drivers issue and read HERE for instructions on how to get the proper drivers working using the Zdiag software included with the Heimdall package. Ignore the 1click part of the linked thread, but follow the rest. you will have to run Zdiag manually from the "drivers folder" of the Heimdall suite.
7) Only process to this step when have determined that your device is detected by Heimdall.
8) Click on the first Tab in Heimdall Frontend that says Load Package. Click on the browse button and load up the T959Wpackage you downloaded in step 2. It may take up to 10 minutes for your PC to uncompress the files depending on the speed of it. Don’t rush it, waiting till all the messages are gone and the LOAD/CUSTOMIZE button is active, click on that button
9) This will bring you to the FLASH tab. Make sure repartition is CHECKED (it should) and don’t touch anything else. Finally, click on the START button at the bottom. Let it do it’s thing, it will take about 5 mins and then your phone will reboot. It will take another few minutes here before your phone fully boots and you are at the Google Setup screen.
10) Made it this far? Great, now you have saved your phone from a brick, but there are a few things that aren’t working yet, so don’t panic that you have no signal yet or no wifi, etc. We can fix those things fairly easily IF YOU CAN FOLLOW INSTRUCTIONS AND READ AND NOT RUSH. If you start whining you have no signal after step 9 and don’t read anymore or follow my instructions on how to flash the proper modem, I’ll ignore you. These are all proven steps, tested by thousands of people on these forums that aren’t impatient and do what they are told.
Now, the 3 choices you have.
1) Flash to an Ice Cream Sandwich Variation. If this is the case , Download the ROM you want to your SD card, reboot your phone into recovery and flash according to the directions given by the ROM you want to flash. I won’t answer questions why you can’t flash XXX ROM, your phone will be rooted with recovery using my method, and the rest of the information is out there.
2) Return to the 99% stock option (this will bring the phone exactly how you got it BUT will say T-mobile when you first boot it up. I have no way to fix this currently as I have no stock kernel to use. (hint, bug Wind or Mobilicity for the package and get it to me) Will work on this part.
3) Keep the phone rooted with recovery on Gingerbread. The kernel included in this is Blastoff kernel, which wifi doesn’t work off the start, so you can go to the Blastoff thread HERE and learn how to fix wifi, flash Antonx’s Basic with a Twist HERE or another compatible GB kernel, all from recovery. You will also need to flash a modem. I suggest the LB6 modem that came stock on our phones from, available HERE for GB and ICS, pick the correct one. Again, I provide no support for Blastoff or Basic with a twist or flashing them or something.
So to summarize, this will get your T959W with a rooted kernel and CWM version 5.2.something. Wifi will not work and there is no modem flashed, so read the above step if you want to fix those, read how to do that yourself, etc. I don't want any questions about CM9 or Blastoff or Heimdall or Jelly Bean or anything here. The above steps works if you're not all OCD and rush through and read my steps. I have tested them and the package probably 50 times and I'm doing it again right as I finish typing this all out, so it works. If you still have trouble, and explain in a detailed way what didn't work, I may help. If you SPAZ out that something didn't work and don't explain the steps and demand help, you will be ignored. You risk doing damage to your phone anytime you flash it and void warranties, so that is the risk and I assume none. This package works, the steps I have tried to detail in as much detail as possible including screen shots and everything and have spent hours making and testing the package, taking screenshots, detailing all this, all for the benefit of others as my phone works fine and I never bricked it because I took the time to read, so please read this thread 3 times over before you proceed.
Anyways, hope this helps, give me a Thanks if it does and a Thanks to any Team Acid members posts you see, as they have helped me get to this point.
Click to expand...
Click to collapse
This was amazingly simple. My phone has been really messed up and I've tried everything to restore it and failed until today. Believe me when I tell you that my phone was a lost cause until I went through these steps even though they aren't for my phone but it still worked. I finally got it to flash something and work, lol.
Do you by chance have this same type of file for the US version? Any help is much appreciated. Thank you.
kdkd008 said:
This was amazingly simple. My phone has been really messed up and I've tried everything to restore it and failed until today. Believe me when I tell you that my phone was a lost cause until I went through these steps even though they aren't for my phone but it still worked. I finally got it to flash something and work, lol.
Do you by chance have this same type of file for the US version? Any help is much appreciated. Thank you.
Click to expand...
Click to collapse
You flashed this on a t959v? With bootloaders? And it works?
TwitchyEye said:
You flashed this on a t959v? With bootloaders? And it works?
Click to expand...
Click to collapse
No bootloaders in my package. For some reason the "W" model, it's impossible to flash the bootloader, the modem and EFS partition (I think it's that, been a while since I played with it) from Heimdall or Odin, so it's sort of impossible to brick them as you can never flash those items. Worst you can do is flash the param from the "V" to the "W" and it corrupts the bootup image but works fine otherwise.
Oh I see. Thanks for clearing that up, I've been wondering for a while what would happen.
Hi, I just needed to root my phone. I had previously tried SuperOneClick, for some reason it always fails because of some driver issue. However after I installed your ROM, the root works.
But now that I got your ROM, I cannot detect my SIM card.
I'm wondering if this issues is expected, and is it possible to fix it?
Thanks.
noobishuser said:
Hi, I just needed to root my phone. I had previously tried SuperOneClick, for some reason it always fails because of some driver issue. However after I installed your ROM, the root works.
But now that I got your ROM, I cannot detect my SIM card.
I'm wondering if this issues is expected, and is it possible to fix it?
Thanks.
Click to expand...
Click to collapse
Did you flash a modem? Heimdall can't flash the modem and it's has to be flashed with one of the ones I listed above.
getochkn said:
Did you flash a modem? Heimdall can't flash the modem and it's has to be flashed with one of the ones I listed above.
Click to expand...
Click to collapse
Thank you very much, I thought I broke my phone.
Do you have instruction on how to flash a modem?
The link you provided only gives a file, I'm not sure how to flash it.
I also looked for instruction here:
http://forum.xda-developers.com/showthread.php?t=1001759
but got stuck on step 7 as the file provided does not have a .tar file.
That is a very old thread. FBis251 has a thread with all the modems and you just have to flash them via recovery. Ill look for the thread link and post it back.
This is it here.
http://forum.xda-developers.com/showthread.php?t=1192436
Hi, after spending the past several hours reading/flashing I think I've finally understand most of what's going on.
I was able to successfully some modems. However none of them work perfectly for Mobilicity.
The call/text works fine, but there's no data.
I'm wondering if there is a modem that works for Wind mobile modem with data.
Since I'm planning to switch to Wind mobile anyways later.
noobishuser said:
Hi, after spending the past several hours reading/flashing I think I've finally understand most of what's going on.
I was able to successfully some modems. However none of them work perfectly for Mobilicity.
The call/text works fine, but there's no data.
I'm wondering if there is a modem that works for Wind mobile modem with data.
Since I'm planning to switch to Wind mobile anyways later.
Click to expand...
Click to collapse
It's more than likely your APN's aren't set and that's why you're not getting data. you can look online on what the mobilicity ones are and can through settings, mobile data, mobile networks or something like that, and either enter them manually or scan to force it to try and pick them up. If calls/txt work, data should work. It's on the network. Try and google what to figure out to change. If you can't pm me and I'll try and help.
getochkn said:
It's more than likely your APN's aren't set and that's why you're not getting data. you can look online on what the mobilicity ones are and can through settings, mobile data, mobile networks or something like that, and either enter them manually or scan to force it to try and pick them up. If calls/txt work, data should work. It's on the network. Try and google what to figure out to change. If you can't pm me and I'll try and help.
Click to expand...
Click to collapse
Omg thank you very much! I've successfully got data working now.
Now i feel like an idiot in the past 2 hours trying out every modem I can find...
noobishuser said:
Omg thank you very much! I've successfully got data working now.
Now i feel like an idiot in the past 2 hours trying out every modem I can find...
Click to expand...
Click to collapse
Good stuff. The LB6 modem seems to be the most liked for the most part and is the one I got from my Wind phone. Works good for me.
getochkn said:
Good stuff. The LB6 modem seems to be the most liked for the most part and is the one I got from my Wind phone. Works good for me.
Click to expand...
Click to collapse
Q here, does this modem support the 850mhz frequency and can I flash it to a T959V
Forgot to say it's the wcdma band
I'm new to this phone, exchange an IPhone 3GS for this one.......
Sent from my XT925 using xda app-developers app
Related
Hi, i just bought a samsung infuse and i was looking for an ICS rom and i found the cm9 unofficial http://forum.xda-developers.com/showthread.php?t=1601844 this one
and i flashed like the thread says and everything went good, ics started like a charm but then i turned off my phone to get into the recovery but i found out to be in a huge problem
My phone wont boot, it goes directly to the recovery (cwm 5.5.0.4) and it looks like a broken screen (sort of, rainbows) its usable but it wont boot, i even tried to reflash it
Would somebody help please?
riikiiee said:
Hi, i just bought a samsung infuse and i was looking for an ICS rom and i found the cm9 unofficial http://forum.xda-developers.com/showthread.php?t=1601844 this one and i flashed like the thread says and everything went good, ics started like a charm but then i turned off my phone to get into the recovery but i found out to be in a huge problem My phone wont boot, it goes directly to the recovery (cwm 5.5.0.4) and it looks like a broken screen (sort of, rainbows) its usable but it wont boot, i even tried to reflash it Would somebody help please?
Click to expand...
Click to collapse
Well I guess you didn't read all the way til post 3 of the thread where you pulled the CM9 unofficial ROM...BTW your probable gonna get flamed since you also didn't make a run thru the the Q&A...since this has been address, well I ran out of fingers and toes to count how many times...but
Go back the op [Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G... go down to post 3, and do a little reading, maybe you should of did some more homework before jumping in, but hey good on you for just jumping and not looking where you might land...
If you require more reading (i suggest) see my links below...ok,
Good luck
yes i know i will get flamed, and i did read the 3rd post about the bootloaders
but i just wanted to know if there is another way to do it, and since English is not my native language, i don't understand everything very well, but thanks
riikiiee said:
yes i know i will get flamed, and i did read the 3rd post about the bootloaders but i just wanted to know if there is another way to do it, and since English is not my native language, i don't understand everything very well, but thanks
Click to expand...
Click to collapse
Ok understood, just relax and re read it again, and go thru the Q and A seciton.
What part are you having trouble understanding...?
---------- Post added at 11:17 PM ---------- Previous post was at 11:10 PM ----------
What I suggest is start over:
Use the one click back to stock and then use the one click to install CWM...which is what you need to get CM9 ics ok,
so first one click back using qkster method:
http://forum.xda-developers.com/showthread.php?t=1524081
1. Put your phone into Download Mode.
2. If you have not used Heimdall, you will need to set up the driver for device recognition.
3. Once your device is connected, the DEVICE STATUS should show: CONNECTED. The long FLASH bar will also turn on for flashing.
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
5. Once it has completed, your phone will reboot. You will hopefully see the ATT logo and reboot into STOCK UCLB3.
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked. This is more likely if you never had proper Gingerbread bootloaders on your phone, if you are coming from FROYO or if you never had Odin a Gingerbread leak to get your bootloaders.
Then use one click from same op, qkster method:
http://forum.xda-developers.com/showthread.php?t=1524081
post 2... After you have flashed the UCLB3, some of you may want to have Red ClockWorkMod (CWM) recovery to flash another ROM.
Put your phone back into DOWNLOAD mode after your phone has booted up.
Then reinstall the cm9 zip, once you reach this stage, you will have to flash it twice..ok this file...
Cwm9 is the devil! Everyone who had tried to use it for anything except putting itself on the phone has had one problem after another. Call it experimental or call it in alpha.. Whatever call it as it is a bricking virus. Just cause it was all good through ginger bread doesn't mean it will be the best forever. Pull it off the site already. it affects all phones that use it. I have an epic 4g and it nearly bricked mine about 3 months ago. Check out some.of the other forums that this alpha virus had spread to. Nearly every brick had cwm9 mentioned in it.
timmetal6669 said:
Cwm9 is the devil! Everyone who had tried to use it for anything except putting itself on the phone has had one problem after another. Call it experimental or call it in alpha.. Whatever call it as it is a bricking virus. Just cause it was all good through ginger bread doesn't mean it will be the best forever. Pull it off the site already. it affects all phones that use it. I have an epic 4g and it nearly bricked mine about 3 months ago. Check out some.of the other forums that this alpha virus had spread to. Nearly every brick had cwm9 mentioned in it.
Click to expand...
Click to collapse
Yes and No...
It is a step up for the infuse, well it will be...
The problem is people are not doing their homework, and have never flashed a ROM, much less know what the letter ICS or CM9 even are, and yes it has brought some challenges but for those of us that have installed and ran it on this phone and other phones, I don't mind assisting others, but they have to do the reading and homework for them self's...
Yes you have your opinion and I don't disagree or agree, but I do hope the ROM with be brought up fully functionally, and it will with the Developer we have working it and others who are "testing" it, the ones who are familiar with...
Alright thanks mate, right now im installing the driver for heimdall, I already read everything you said and the links you shared
Thanks again, you just saved another noob
When your up and running for good, let us know, and don't forget to thank the Dev that provided you with the tools you needed...not me...just pointed you there...
Yes I will
timmetal6669 said:
Cwm9 is the devil! Everyone who had tried to use it for anything except putting itself on the phone has had one problem after another. Call it experimental or call it in alpha.. Whatever call it as it is a bricking virus. Just cause it was all good through ginger bread doesn't mean it will be the best forever. Pull it off the site already. it affects all phones that use it. I have an epic 4g and it nearly bricked mine about 3 months ago. Check out some.of the other forums that this alpha virus had spread to. Nearly every brick had cwm9 mentioned in it.
Click to expand...
Click to collapse
No one who actually FOLLOWED THE INSTRUCTIONS has had an issue.
I challenge you to find ONE person who has bricked an Infuse with CM9. The only time in the CM9 flashing process one might brick is when flashing the bootloaders to get rid of rainbows - and I have PLENTY of warning that flashing bootloaders is a dangerous and risky process.
Similarly, no one has bricked an I9100 flashing CM9 either, unless the recovery they were flashing away FROM was defective (such as the initial I777 UCLD3 recovery repacks) - but that same defective recovery caused hardbricks for people flashing even rooted stock with no CM9 involvement.
Task650 was right when he replied to you in the I777 thread - he contributed more to XDA when he took a dump this morning then when you spread your bull****.
Thank You "E"....well put...:thumbup: :thumbup:
I hate it when jokers like that guy pipes in, when trying to help others...the op admits to not to be good at his English...
hey, i downloaded everything that i needed
and even a little bit more
but i haven't been able to start OneClick
put my phone into download mode, install drivers for heimdall
I tried with heimdall frontend in the flash tab, just like the tutorial
add every partition, and then when i click Flash
this is what it says
"Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12"
any idea?
ok I am not trying to insult you just wanna ask a few question ok,
{
"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"
}
You sure your in Download mode...does it look like this your phone?
I go into download mode like this: I take out my battery, plug in the cable while holding both volume buttons i pop my battery in...bamm download mode...
you will see the pic above....
But once it does go into dl mode carefully place the phone down with still connected to the cable then...
if so then you click the one click to open it and you see the word "connects"..in green, click the button below it flash...
and then it should run thru you will see the blue line go across your phone will lots of remarks running thru on the screen in the one click window....ok
dont worry, but yes i know how to put it into download mode
but the thing is that i downloaded oneclick but i cant run it
riikiiee said:
dont worry, but yes i know how to put it into download mode but the thing is that i downloaded oneclick but i cant run it
Click to expand...
Click to collapse
1) ok, have you tried different usb port and or cable...
2)re-download the one click file again...here is a link
http://db.tt/Y2XEPwGv
3) And this the link to give you CWM, you run this after you have install above and you will have to put into download mode for this....and you will hear the lady voice talking that means it is installing cwm...ok but first do the above
http://db.tt/WEJyXywV
riikiiee.....status check my friend...
elostish venus.
Hey BigJoe
the problem was my computer, i used other one I have here, and now Im good and running GB I really appreciate your time and your help.
From now and on I will read everything I have to read
And thanks again mate, you really helped
riikiiee said:
Hey BigJoe
the problem was my computer, i used other one I have here, and now Im good and running GB I really appreciate your time and your help. From now and on I will read everything I have to read
And thanks again mate, you really helped
Click to expand...
Click to collapse
No problem....glad you found out what the real problem was...
Any time ...:thumbup:
goritat the
Yeah, now back to ICS again
the right way now
[size=+2] Windows ODIN (Samsung Flashing Application)[/size]
{
"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"
}
All latest versions and download links are below! of course courtesy of samsung-updates.com portal!
[size=+2]Odin (v3.07) is HERE [/size]
[size=+1]Odin (v3.06) is HERE [/size]
[size=+1]ALWAYS DO BACKUP OF PRECIOUS DATA BEFORE FLASHING!! IM NOT TAKING RESPONSIBILITY FOR DATA LOSS!
FLASHING CUSTOM ROM WILL TOP UP YOUR CUSTOM ROM COUNTER!!
FLASHING ROMS MAY (OR NOT) CAUSE DATA LOSS (SMS, CONTACTS, SETTINGS , APPS) - YOU HAVE BEEN WARNED![/size]
Enjoy!
Watch us on twitter for latest updates! @SamsungUpdates !
Custom Rom Counter?
Hey everyone!
I am new to samsung phones...coming from a Droid x2 and wanted to get some clarity on what the Custom Rom Counter is.
So is it a setting that verizon can check to see if you have ever flashed a custom rom on top of your stock rom?
keatond said:
Hey everyone!
I am new to samsung phones...coming from a Droid x2 and wanted to get some clarity on what the Custom Rom Counter is.
So is it a setting that verizon can check to see if you have ever flashed a custom rom on top of your stock rom?
Click to expand...
Click to collapse
It increments each time a custom rom is flashed. They will know if you void your warranty, unless you reset it. There will be ways to reset this once we have devs cracking open the phone
cmg5461 said:
It increments each time a custom rom is flashed. They will know if you void your warranty, unless you reset it. There will be ways to reset this once we have devs cracking open the phone
Click to expand...
Click to collapse
That similiar to the HTC dev unlock thing?
Sent from my vivow using Tapatalk 2
No, odin is a flashing program not unlocking program
So to flash anything must Odin be used? We can't just download a kernel or Rom via phone, boot into cwm and flash the kernel or Rom through there?
Sent from my vivow using Tapatalk 2
yes you can. But your recovery MUST be CWM then. Also you cant back to stock using CWM cause CWM is no stock
I see your're new to this things, and i can assure you. You will be using ODIN as your daily driver
I'm 100% New to Samsung. I have had the dinc and dinc2. The only time I ever used a pc was to load a new bootloader and soff. Everything else was dine via phone. Even stock, I just flash the pb32img and boom, run revolutionary s on and no worries. 100% back to stock.. after my dinc I didn't even use cwm, I used 4ext recovery.. 1000x better... I need to fond me a noon Samsung forum because I know I'm going to get annoying quick. And I hate it when people don't read up on vivow forums moat of the time.
Sent from my vivow using Tapatalk 2
I am glad to see that odin is going to be used for this phone. Still don't quite get ADB and whatnot. For those not familiar with Odin it is pretty much your best friend. Odin allows for flashing of factory images along with radios and clockwork mod recoveries.
I will use my Fascinate as an example. If i want to flash back to stock i have a stock odin file that will to go to Eclair,Froyo, or Gingerbread. Any and all modifications go back to stock at that point so bootloaders, radios, and obviously the rom itself and the kernel. Odin then also allows for you to switch radios. Again the Fascinate for example, the fascinate has 6 over all radios give or take. One is designed for Elcair, one or two for Froyo and the rest for Gingerbread. With there being more then one option for certain android operating systems you can use the one which is best for you. If you flash the wrong modem the phone will still work and what not but might not properly call or send and receive txt msgs. Last but not least you can use Odin to flash recoveries. When going to any ICS rom on the fascinate you actually have to flash a recovery that allows for you to install the appropriate files. This is done through Odin. So in a lot of major cases you go back to Odin. Flashing new roms and kernels are still done via the phone in recovery.
The flash counter thing i will admit is new to me. I heard about it on some of the newer Samsung phones but i never heard or encountered it with the Fascinate
We also should sooner or later have a mobile odin available to us if not already. Pretty much what this means is that all the things i described above can be done from your phone independently without the use of a computer from a mobile version of odin. So you can fix things on the go.
EDIT***** Forgot another cool feature of Odin. Custom Odin files. So try to follow me. So as I mentioned you can through Odin go back to a factory image. What you can create on your own though is a custom image to go back to. So again to go from Stock Eclair,Froyo or Gingberbread to ICS on the Fascinate requires 2 flashes through odin and 3 reboots technically. Instead of going through all that i can create my own custom Odin file that will have me right back to the latest and greatest, So straight to a ICS rom with the proper kernel,bootloaders & radio. So no need for a step by step process to get you back to where you were you can just flash through Odin. I have yet to do this and really see how it works but the ability to do something like this is pretty awesome.
All in all the Samsung experience is a very unique one and what i would like to say is the best. You don't have to worry about s-off and hboots and locked bootloaders and what not. Its straight and to the point. Hope this was of more help to better understand Odin and its uses.
Aali1011 said:
I am glad to see that odin is going to be used for this phone. Still don't quite get ADB and whatnot. For those not familiar with Odin it is pretty much your best friend. Odin allows for flashing of factory images along with radios and clockwork mod recoveries.
I will use my Fascinate as an example. If i want to flash back to stock i have a stock odin file that will to go to Eclair,Froyo, or Gingerbread. Any and all modifications go back to stock at that point so bootloaders, radios, and obviously the rom itself and the kernel. Odin then also allows for you to switch radios. Again the Fascinate for example, the fascinate has 6 over all radios give or take. One is designed for Elcair, one or two for Froyo and the rest for Gingerbread. With there being more then one option for certain android operating systems you can use the one which is best for you. If you flash the wrong modem the phone will still work and what not but might not properly call or send and receive txt msgs. Last but not least you can use Odin to flash recoveries. When going to any ICS rom on the fascinate you actually have to flash a recovery that allows for you to install the appropriate files. This is done through Odin. So in a lot of major cases you go back to Odin. Flashing new roms and kernels are still done via the phone in recovery.
The flash counter thing i will admit is new to me. I heard about it on some of the newer Samsung phones but i never heard or encountered it with the Fascinate
We also should sooner or later have a mobile odin available to us if not already. Pretty much what this means is that all the things i described above can be done from your phone independently without the use of a computer from a mobile version of odin. So you can fix things on the go.
EDIT***** Forgot another cool feature of Odin. Custom Odin files. So try to follow me. So as I mentioned you can through Odin go back to a factory image. What you can create on your own though is a custom image to go back to. So again to go from Stock Eclair,Froyo or Gingberbread to ICS on the Fascinate requires 2 flashes through odin and 3 reboots technically. Instead of going through all that i can create my own custom Odin file that will have me right back to the latest and greatest, So straight to a ICS rom with the proper kernel,bootloaders & radio. So no need for a step by step process to get you back to where you were you can just flash through Odin. I have yet to do this and really see how it works but the ability to do something like this is pretty awesome.
All in all the Samsung experience is a very unique one and what i would like to say is the best. You don't have to worry about s-off and hboots and locked bootloaders and what not. Its straight and to the point. Hope this was of more help to better understand Odin and its uses.
Click to expand...
Click to collapse
The fact of not worrying about the unlocked bootloader and soff seems really nice, otherwise like I said everything else was done right via my phone. It does help me understand it 100x better though. I really appreciate you taking the time to break it down
Sent from my vivow using Tapatalk 2
check out this guide i made for the fascinate below...the sgsIII flashing methods should be very similar. i plan on creating a similar guide soon as devs get working on it.
http://forum.xda-developers.com/showthread.php?t=1238070
Odin has been my friend many times with my charge ....
SENT FROM THE DOG POUND
droidstyle said:
check out this guide i made for the fascinate below...the sgsIII flashing methods should be very similar. i plan on creating a similar guide soon as devs get working on it.
http://forum.xda-developers.com/showthread.php?t=1238070
Click to expand...
Click to collapse
Wow I have to say that is beyond a thorough and very well explained guide I look forward to it here and you answered a lot of noobish questions to without freaking out lol
droidstyle said:
check out this guide i made for the fascinate below...the sgsIII flashing methods should be very similar. i plan on creating a similar guide soon as devs get working on it.
http://forum.xda-developers.com/showthread.php?t=1238070
Click to expand...
Click to collapse
Boy am i glad to see you here. But yes droidstyle's guide is a good illustration of how odin is very much so integrated in conjunction with the phone.
Aali1011 said:
I am glad to see that odin is going to be used for this phone. Still don't quite get ADB and whatnot. For those not familiar with Odin it is pretty much your best friend. Odin allows for flashing of factory images along with radios and clockwork mod recoveries.
I will use my Fascinate as an example. If i want to flash back to stock i have a stock odin file that will to go to Eclair,Froyo, or Gingerbread. Any and all modifications go back to stock at that point so bootloaders, radios, and obviously the rom itself and the kernel. Odin then also allows for you to switch radios. Again the Fascinate for example, the fascinate has 6 over all radios give or take. One is designed for Elcair, one or two for Froyo and the rest for Gingerbread. With there being more then one option for certain android operating systems you can use the one which is best for you. If you flash the wrong modem the phone will still work and what not but might not properly call or send and receive txt msgs. Last but not least you can use Odin to flash recoveries. When going to any ICS rom on the fascinate you actually have to flash a recovery that allows for you to install the appropriate files. This is done through Odin. So in a lot of major cases you go back to Odin. Flashing new roms and kernels are still done via the phone in recovery.
The flash counter thing i will admit is new to me. I heard about it on some of the newer Samsung phones but i never heard or encountered it with the Fascinate
We also should sooner or later have a mobile odin available to us if not already. Pretty much what this means is that all the things i described above can be done from your phone independently without the use of a computer from a mobile version of odin. So you can fix things on the go.
EDIT***** Forgot another cool feature of Odin. Custom Odin files. So try to follow me. So as I mentioned you can through Odin go back to a factory image. What you can create on your own though is a custom image to go back to. So again to go from Stock Eclair,Froyo or Gingberbread to ICS on the Fascinate requires 2 flashes through odin and 3 reboots technically. Instead of going through all that i can create my own custom Odin file that will have me right back to the latest and greatest, So straight to a ICS rom with the proper kernel,bootloaders & radio. So no need for a step by step process to get you back to where you were you can just flash through Odin. I have yet to do this and really see how it works but the ability to do something like this is pretty awesome.
All in all the Samsung experience is a very unique one and what i would like to say is the best. You don't have to worry about s-off and hboots and locked bootloaders and what not. Its straight and to the point. Hope this was of more help to better understand Odin and its uses.
Click to expand...
Click to collapse
Chainfire has a Mobile Odin on Google Play. Used it on my 7.7 and ..wow! Way too cool. Got real familiar with ADB with the TF (necessity!) but you;re right...ODIN is slick! Not sure if Chainfire's Mobile Odin will work for the SGSII (getting mine from VZW next week) but if it does it'll be more than welcome!
Odin method is far better than the CWR (clockwork recovery) method. I never understood exactly why, but if you load your software using Odin, it will work really well every time assuming you don't mess up. Clockwork Recovery flashed roms tend to be a bit hit or miss, they tend to have more incomplete flashes....it just doesn't seem to do as thorough a job as Odin.
I always choose the Odin method given the choice. I will wait until I get around a pc to do this, would really rather not be sitting somewhere flashing in clockwork and get a bad flash and end up without a phone until I can get back to a pc with Odin to fix it.....
jamesnmandy said:
Odin method is far better than the CWR (clockwork recovery) method. I never understood exactly why, but if you load your software using Odin, it will work really well every time assuming you don't mess up. Clockwork Recovery flashed roms tend to be a bit hit or miss, they tend to have more incomplete flashes....it just doesn't seem to do as thorough a job as Odin.
I always choose the Odin method given the choice. I will wait until I get around a pc to do this, would really rather not be sitting somewhere flashing in clockwork and get a bad flash and end up without a phone until I can get back to a pc with Odin to fix it.....
Click to expand...
Click to collapse
I couldn't agree with more...
SENT FROM THE DOG POUND
jamesnmandy said:
Odin method is far better than the CWR (clockwork recovery) method. I never understood exactly why, but if you load your software using Odin, it will work really well every time assuming you don't mess up. Clockwork Recovery flashed roms tend to be a bit hit or miss, they tend to have more incomplete flashes....it just doesn't seem to do as thorough a job as Odin.
I always choose the Odin method given the choice. I will wait until I get around a pc to do this, would really rather not be sitting somewhere flashing in clockwork and get a bad flash and end up without a phone until I can get back to a pc with Odin to fix it.....
Click to expand...
Click to collapse
I agree with this too but I don't think we are going to see many roms come in a Odin package. Regarding the Fascinate I think we mainly had stock system packages. In the beginning of development for the phone on a lot of the Touchwiz based roms we had Odin packages too IIRC. When it progressed to CM7 & CM9 it was all done through the phone. Its all up to our developers. That is my main concern for this phone. Time will only tell who we will see but from the looks of it thanks to Verizon's ploy to destroy unlimited data a lot of people seem to be hopping on the bandwagon.
With talks already of having developers from all carriers having a "Kitchen" of sorts where we can get roms and maybe kernels from say the AT&T version or Sprint version that work with our phones, things are looking good and I hope to have a repeat of the experience if not better then what I had with the Fascinate. The devs MADE that phone what it was and I thank them wholeheartedly.
This is very interesting (coming from rooting on a Droid X)
I was watching videos of people using Odin on Youtube and heard about that counter in the phones, got really nervous until I read that they can be reset. Very excited.
so noone still has the verizon phone version ?
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
This may not be a traditional Q&A format, but I really wanted to make sure that the plan I have in mind is going to work out for me.
Hi! I'm a noob. I want to flash my first ROM ever after having gotten frustrated beyond belief with how often my Infuse crashes (every few hours I get the triple vibrate to crash). I've already rooted the Infuse and installed CWM though it seems that it was pointless for me to do both of these things as the steps I'm to follow seem to install the both of 'em.
Phone: Samsung Infuse
Carrier: AT&T
Current Firmware version: 2.2.1
Baseband version: I997UCKH1
Kernel version: 2.6.32.9
Build number: FROYO.UCKH1
ROM I want to install: Unofficial CM10
Steps I intend to take:
Back up with Titanium Backup (Free) - Done as according to ctkatz's thread.
I did not do a launcher backup, mostly because I don't know what it is and I don't believe I have one I'm interested in keeping. Also, I didn't use Rom Manager to make a nandroid backup since in the threads I've read the general consensus seems to be Rom Manager is REALLY AWESOME at bricking phones, but not so good for much else.. Rather, I booted into CWM and told it to make a backup. I'm under the impression this made a nandroid backup. If this didn't, please somebody let me know.
Install 2.3.6 Gingerbread via jscott30's thread and installing option D. And for some reason, this is the only step that requires me to use Odin. I'm not really sure why, if anybody wants to clear that up it'd be great!
Use Qksters EFS backup script to ensure that if I somehow mess things up, I can still save my phone! And to run this I just "flash" it like I would a ROM. Which is by selecting the install zip from sdcard option.
Follow Entropy's CM9 guide to go from GB to ICS And this is just because you can't jump from GB to JB? I'm assuming it's something along those lines. Either way, his guide seems straightforward enough. Also during this step, put the ROM, Overclock Kernel, and Gapp files for CM10 on my internal SD card.
Wipe in CWM
Flash the ROM in CWM
Flash Overclock Kernel in CWM because if I'm going through all this trouble to doctor my Android, I may as well give myself the ability to overclock it
Wipe Cache Partition in CWM I don't really know what this does, but I'm assuming it doesn't wipe anything I care about
Advanced/Wipe Dalvick Cache Same as the previous step. I don't know what it does, but I'm following instructions.
Reboot And I'm supposed to understand this first reboot will take like 5-10 minutes and I shouldn't run around my house crying that my phone broke when it takes a long time to reboot.
Wait 15 minutes and reboot a second time
Log into google account And this gets my contacts back
Restore user app data This gets my apps and my 3 starred all angry birds levels back?
CAREFULLY restore some system data that is green
And after that, I get to play around with my brand new shiny OS and enjoy my phone!
I apologize that this is not a very concise accumulation of questions, but there's not really a single guide that goes step by step through this ENTIRE process of going from Froyo to a customized jellybean OS while making sure you don't lose any app data. It's taken me about ~5 hours of reading through a number of topics and my brain is starting to feel fuzzy, so I really just wanted some of the more experienced members of the community to doublecheck my planning.
Thank you guys so much! Everybody in this community is just awesome for dumbing this process down for those of us who do not understanding the inner workings of a computer : ). I'm very appreciative!
You have pretty much the right idea.
There's a few pointer i would suggest. Back up your contacts to google. Save all your photos to your PC.
When you are making the move from 2.2.1 to 4.1.2 or 4.2, I would start it all new. I would not restore anything you had in froyo (2.2.1) to 4.1.2.
With that in mind, put your phone into download mode, flash jscott's gb with bootloaders.
Flash cm9 and then cm10 as instructed on their ops or andros's write up.
Also I noticed you have a step about flashing the OC kernel, but OC has now been integrated into the kernel that comes with the build.
And as qkster stated, avoid restoring data. If there is something essential you do not want to lose you may restore data for that specific app and in case you start having issues, you know what to blame.
Sent from my SGH-I997 using xda app-developers app
qkster said:
You have pretty much the right idea.
There's a few pointer i would suggest. Back up your contacts to google. Save all your photos to your PC.
When you are making the move from 2.2.1 to 4.1.2 or 4.2, I would start it all new. I would not restore anything you had in froyo (2.2.1) to 4.1.2.
With that in mind, put your phone into download mode, flash jscott's gb with bootloaders.
Flash cm9 and then cm10 as instructed on their ops or andros's write up.
Click to expand...
Click to collapse
Luckily, the guide I read on backing up suggested both of those things, so I've done those.
I'm underway! I managed to successfully install the option D from jscott, but I'm a little confused on how to flash the bootloaders. Do I need to put my phone back into download mode to use Odin again? I tried that, and Odin doesn't seem to want to recognize my phone.
And sadly, I can't skip out on the bootloaders as I'm sure you guessed. Upon trying to go to CM9 I failed miserably due to rainbows. I actually used your guide to get back to well, stock UCLB3, and from there I've been trying to get the bootloaders on by putting my phone in download mode.
With no luck, sadly. Odin just doesn't want to show my phone as connected. Kinda stuck at the moment!
EDIT: I re-read the guide of yours I followed and saw that all I had to do was flash the thing a second time with the install bootloaders box checked. Unfortunately, I've done that, and I can clearly read the words "Uploading SBL...SBL upload failed!" on my screen.
Doesn't take much of a genius to figure out that the BL likely stands for bootloaders, so now I'm slightly freaking out. Heimdall One-click is currently trying to end the session. I'm of course going to let it go as long as I can hoping that it ends things nicely as I'm terrified to try turning anything off at this point. Hopefully I didn't just permanently destroy my phone =\
Andros: Oh thank you for saving me from the OC mishap. I suppose there's some good in me not having gotten that far yet due to problems!
EDIT 2: I can see the light at the end of the tunnel! I swapped my USB ports around a bit and kept trying with your Heimdall One-click stuff and finally got the bootloaders in! Once that went through the rest was easy as pie : ) Everything's going smooth, I'm currently installing JB Gapp stuff, then I'm going to follow the rest of my ROM guide and I don't forsee any issues. Thank you guys again, both of your guides and your responses were very helpful!
I want to thank YOU arguro. If everybody had the patience and intelligence to so thoroughly research what they wanted to do there would be so many less help I bricked my phone threads and a whole lot less irritated developers.
You went into the process with the right amount desire / fear. Glad you made it and welcome to jellybean!
Sent from my SGH-I997 using xda app-developers app
Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Please read forum rules before posting.
Questions and request for assistance go in the Q&A section.
Thread has been moved.
Thank you for your future attention to this.
Have a great day!
dfarquhar said:
Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
Click to expand...
Click to collapse
Look here for 1.3.1.
dfarquhar said:
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Click to expand...
Click to collapse
Nope, not a CWM issue. Ever since TeamAcid and I started on CM9 (and I believe the last few CM7 builds) added support for T959W. Almost everyone (thankfully! ) has kanged those device trees and also support T959W. I'm sure other T959W users will chime in to tell you that 97% of all roms here work on T959W. (GB and forward)
dfarquhar said:
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
Click to expand...
Click to collapse
Crazy mount setups shouldn't matter anymore. That was an oldschool Froyo/Early GB thing. Almost all new CWM install scripts do the right thing now.
dfarquhar said:
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
Click to expand...
Click to collapse
I like the long posts! Especially when then they contain more detail for me to help you figure out your problem with. I'm also partial to the short posts that include logs!
TwitchyEye said:
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
@TwitchyEye you're right That is the heimdall oneclick that should be used.
@dfarquhar I think using the heimdall oneclick that @getochkn made should be the right path for you. Make sure you use the right version of heimdall. Make sure you completely remove the old version (software and drivers), use zdiag to make absolutely sure!
If all else fails, post here again! (maybe with logs )
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
dfarquhar said:
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
Click to expand...
Click to collapse
Sometimes, it's just the output you see on your screen is a good enough log
bhundven said:
Sometimes, it's just the output you see on your screen is a good enough log
Click to expand...
Click to collapse
Got it working! Heimdall 1.3.1 was the key. I then turned around and flashed Slim ICS since I had it on the SD card already, and it worked. I'm debating whether to move on to Slim Bean, but maybe I need to leave well enough alone for a few days now that I have a working phone.
Thanks again,
Dave