Related
Okay. I have read quite a bit on this forum regarding the ROMs and CWM. I have rooted my phone and am looking to add Gummy Charge. I have never done this with a phone and the rooting process was nerve racking knowing what could be the consequences. I use this phone for work, but would like to enjoy it while I have it.
As I said, I have read quite a bit, but am still confused. I have a few questions:
1) Define flash.
2) I have dowloaded the following files:
- GummyCharged_FE_1.9.1_FullOdin.tar.md5.7z
- 0817_charge_recovery.tar.md5
- Voodoo-stable-5.5-Froyo-GT-I9000-odin-pda.tar
Are these the files I need for this process?
3) What order to add these to the phone through Odin?
4) Once these are added, do I start up after each install?
I think this will cover it for now.
I appreciate everyone's time and hope this is not a repeat series of questions. I really appreciate all developers and the time they have spent putting all this together for our benefit.
Scott
K so forget the i9000 file all together. Actually just delete it before you really screw something up.
Flashing is the act of overwriting system partitions with alternate firmware. Thats my best shot at a clear def.
On to the rest. Be sure youve got odin set up properly drivers and all.
Now all youve got to do is flash the gc1.9 odin package. Let boot. Go back to download mode then flash recovery in odin and let the phone boot.
Ps you may not need to flash the recovery in odin but i can't remember if that gc package includes one do you might as well just do it....
Also I believe that package includes a voodoo kernel so it could take quite a while to boot up the first time..
Happy flashing my friend!
Sent from my Gummy Charged GBE 2.0 using XDA App
Thank you for your quick response.
I'm assuming I have all the drivers for Odin since I used it for the rooting process.
If there is something I may be overlooking please let me know.
You mention:
Now all youve got to do is flash the gc1.9 odin package. Let boot.
Click to expand...
Click to collapse
Is this what I use Odin for or is Odin only used to "place" the file in the phone? Are there steps that I need to do to "flash" the phone or do I just boot up and I'm now running Gummy Charge.
TacticalMonk said:
Thank you for your quick response.
I'm assuming I have all the drivers for Odin since I used it for the rooting process.
If there is something I may be overlooking please let me know.
You mention:
Is this what I use Odin for or is Odin only used to "place" the file in the phone? Are there steps that I need to do to "flash" the phone or do I just boot up and I'm now running Gummy Charge.
Click to expand...
Click to collapse
all you need to do is get the phone into download mode and connect it with Odin open on your pc, press PDA (NOT PHONE) and browse for the Gummy odin package ending in .tar.md5, place the battery back in and press start then let Odin flash the rom to your phone... when its finished unplug your phone and remove battery, then put it back in and boot the phone up (first bootup may take a while so bear with it) then enjoy your rooted and custom rom'd phone... using ClockWorkMod that installs with the rom you can then flash anything you want in the future like newer kernels or different roms
blazing through on my 4G Droid Charge
First, great work by all.
I see this on a few other Samsung devices which takes a long time and makes it more difficult to flash.
Why not just make a CWM ODIN file for the first time flash?
The Cdn phone is different from ATT so that option does not work and neither does the Unbrickable ROM btw.
It just seems from my experience flashing all these different Samsung phones to just have a CWM ODIN file and in 2 steps the person is done.
Is this possible?
Please leave in Dev area.
droiduzr2 said:
First, great work by all.
I see this on a few other Samsung devices which takes a long time and makes it more difficult to flash.
Why not just make a CWM ODIN file for the first time flash?
The Cdn phone is different from ATT so that option does not work and neither does the Unbrickable ROM btw.
It just seems from my experience flashing all these different Samsung phones to just have a CWM ODIN file and in 2 steps the person is done.
Is this possible?
Please leave in Dev area.
Click to expand...
Click to collapse
Not sure exactly what you are asking, but I think that it has something to do with 3e recovery. And this does NOT belong here, in the Dev thread.
The 3e Mod recovery is not working.
signature verification failed
I tried it a few times.
Let me try to explain another way.
1. got new phone
2. use an ODIN file to flash a kernel with CWM
3. put new ROM on phone or external sd
4. reboot into CWM and install rom
5. done!
Agreed this is not development related. And the last thing anyone needs it foe things to be any easier then they already are. Even as simple as things are people still don't do the needed research and end up with bricks.
Thread closed
Hi. I am having trouble finding the clockwork mod for this device on this forum. I found some instrucions on the cyanogen mod forum with an oficial rom from them. Which one anyone suggest me? roms from the forum or cyanogens 7. im searching for an ics rom..
Sent from my SAMSUNG-SGH-I897 using Tapatalk 2 Beta-5
The hard way is usually what new owners of the Captivate learn, and fast, like I did over the past week or so. I ended up:
- getting the i897uckk4 Odin One Click - Stock ROM and flashing that so it was fully updated (at least as far as the AT&T stock stuff is concerned)
- located the Odin3 v1.85 flasher
- flashed the captivate-recovery-cwm5-kernel.tar onto the Captivate (it's the stock KK4 kernel with CWM 5 ready to go)
- then used CWM to update/upgrade from a bunch of ROMs, currently using Doc's Master beta v9, but I've tried about 10 ROMs in the past few days, this one is working fine at the moment aside from some ROM Control FC issues, but it's beta obviously
That should get you going. Found all the files here by searching, use the names I just mentioned above to locate them as I didn't save individual links, sorry.
Hope this helps...
Thank U Very Much
br0adband said:
The hard way is usually what new owners of the Captivate learn, and fast, like I did over the past week or so. I ended up:
- getting the i897uckk4 Odin One Click - Stock ROM and flashing that so it was fully updated (at least as far as the AT&T stock stuff is concerned)
- located the Odin3 v1.85 flasher
- flashed the captivate-recovery-cwm5-kernel.tar onto the Captivate (it's the stock KK4 kernel with CWM 5 ready to go)
- then used CWM to update/upgrade from a bunch of ROMs, currently using Doc's Master beta v9, but I've tried about 10 ROMs in the past few days, this one is working fine at the moment aside from some ROM Control FC issues, but it's beta obviously
That should get you going. Found all the files here by searching, use the names I just mentioned above to locate them as I didn't save individual links, sorry.
Hope this helps...
Click to expand...
Click to collapse
Thank U Very Much, Your guild is awesome worked the 1st time, I been trying for 3 days NOW, THANK U SO Much.
Clockwork mod is a recovery kernel replacement which allows flashing of unsigned zip files. You flash or "reinstall packages" as an update.zip from the original recovery. This roots the phone and installs Clockwork recovery.
Flashing roms without knowing the three button method to get into recovery or the button combo to get into download mode could spell trouble for people who are just learning about rom flashing.
It takes a few months of reading threads until a level of understanding is reached where you can flash roms and get out of trouble on your own.
br0adband said:
The hard way is usually what new owners of the Captivate learn, and fast, like I did over the past week or so. I ended up:
- getting the i897uckk4 Odin One Click - Stock ROM and flashing that so it was fully updated (at least as far as the AT&T stock stuff is concerned)
- located the Odin3 v1.85 flasher
- flashed the captivate-recovery-cwm5-kernel.tar onto the Captivate (it's the stock KK4 kernel with CWM 5 ready to go)
- then used CWM to update/upgrade from a bunch of ROMs, currently using Doc's Master beta v9, but I've tried about 10 ROMs in the past few days, this one is working fine at the moment aside from some ROM Control FC issues, but it's beta obviously
That should get you going. Found all the files here by searching, use the names I just mentioned above to locate them as I didn't save individual links, sorry.
Hope this helps...
Click to expand...
Click to collapse
Thanks alot..im going to try that now and se how it goes
Sent from my SAMSUNG-SGH-I897 using Tapatalk 2 Beta-5
askpcguy said:
Clockwork mod is a recovery kernel replacement which allows flashing of unsigned zip files. You flash or "reinstall packages" as an update.zip from the original recovery. This roots the phone and installs Clockwork recovery.
Flashing roms without knowing the three button method to get into recovery or the button combo to get into download mode could spell trouble for people who are just learning about rom flashing.
It takes a few months of reading threads until a level of understanding is reached where you can flash roms and get out of trouble on your own.
Click to expand...
Click to collapse
Ive been flashing for a while now. I have a galaxy fit rooted and with clockwork..i was just asking because i want to now if i do this will it take away my currently settings..since i network unlocked it and am currently using it with claro.. Im on stock rooted 2.3.5 uckk4 unlocked network
Sent from my SAMSUNG-SGH-I897 using Tapatalk 2 Beta-5
br0adband said:
The hard way is usually what new owners of the Captivate learn, and fast, like I did over the past week or so. I ended up:
- getting the i897uckk4 Odin One Click - Stock ROM and flashing that so it was fully updated (at least as far as the AT&T stock stuff is concerned)
- located the Odin3 v1.85 flasher
- flashed the captivate-recovery-cwm5-kernel.tar onto the Captivate (it's the stock KK4 kernel with CWM 5 ready to go)
- then used CWM to update/upgrade from a bunch of ROMs, currently using Doc's Master beta v9, but I've tried about 10 ROMs in the past few days, this one is working fine at the moment aside from some ROM Control FC issues, but it's beta obviously
That should get you going. Found all the files here by searching, use the names I just mentioned above to locate them as I didn't save individual links, sorry.
Hope this helps...
Click to expand...
Click to collapse
Soooo sorry to bother, but I'm at my wits end trying to root and remod my new captivate. The last one crapped out on me, so I was able to get a replacement, but I don't remember flashing it being this hard 6 months ago...lol! Anyway, here's my current stats and what I'm looking for:
Firmware: 2.3.5
Baseband: I897UCKK4
Kernel: 2.6.35.7-I897UCKK4-CL614489
Build: Gingerbread.UCKK4
I can if need be flash it back to 2.1 with Odin, but I followed your instructions, and now I'm stuck. I can't for the life of me find the captivate-recovery-cwm5-kernel file anywhere, on here or elsewhere. I don't even think the phone is rooted now, which is very strange because I was able to flash it, but anyway...any help would be greatly appreciated! Thanks in advance!!
I can't upload the Odin One Click ROM, it's too much for my current situation, but here's the captivate-recovery-cwm5-kernel.tar file:
http://dl.dropbox.com/u/19019338/captivate-recovery-cwm5-kernel.tar
MD5: 8464e7cee89c7364d62b760c28a4ca73
File size: 6,359,040 bytes
and here's Odin v1.85 if you don't have it:
http://dl.dropbox.com/u/19019338/Odin3_v1.85.zip
MD5: 9a81990a61454402e8714f494bb4eb68
File size: 204,173 bytes
Now, the basics are thus so pay attention:
Since Samsung is never going to release a proper ICS build for us, from what I understand - let me repeat that: from what I understand everything is working with Gingerbread bootloaders, so that's the important aspect. Before you go flashing anything, you'll need to get the Captivate OFF Froyo of any version if you're still using it. So, update that thing using Samsung Kies to the latest version which is that KK4 ROM - that's all that's required.
Once you're done that, and you're "stock" then you would flash the captivate-recovery-cwm5-kernel.tar kernel using Odin (run Odin with Admin privilege, put the Captivate in download mode, connect it, when detected, click the PDA button in Odin to load that captivate-recovery-cwm5-kernel.tar file, then Start to flash it). Once that's done you have the same kernel for KK4 but with CWM ready to go when you are with a proper GB bootloader and you're set.
The only reason I mentioned the Odin One Click above was because I did a few things that "pooched" my Captivate and soft-bricked it at one point but recovered it with Odin and the One Click when Kies couldn't do anything at all. There's a thread around here with all the Odin One Click ROMs, that's where I got mine from.
tl;dr version:
- if you're running any Froyo anything, use Kies to do the upgrade to Gingerbread, NOT the Odin One Click. Kies will update the bootloader from Froyo to GB as required (the Odin One Click was part of what caused my soft-brick, so I learned from the experience)
- if you're already running any Gingerbread ROM, you already have the GB bootloader, so you can use the Odin One Click to go to a pure stock AT&T basic clean ROM as mentioned above
- once you're "stock" use Odin v1.85 to flash the captivate-recovery-cwm5-kernel.tar so you get the same stock kernel but CWM as well
- use CWM to install whatever ROM you want from that point on making sure the ROM archive(s) and any updates or whatever are copied to the internal storage
Personal suggestion: remove the microSD card from the Captivate before doing any flashing at all. Yes it's possible to read from that device (called the external SD in CWM), I simply don't recommend it, ever.
That's about it. The Odin One Click KK4 is not rooted, iirc, I can't say for certain at this moment either way. I only used it a few times to "save" me from the soft-brick. Now that CWM is in there, I've jumped from ROM to ROM over the past week or so but Doc's Master v8 is my fall back stable one so far. Obviously when you load a ROM, look at the Apps and if you don't see SU or SuperUser, it's not rooted.
br0adband said:
I can't upload the Odin One Click ROM, it's too much for my current situation, but here's the captivate-recovery-cwm5-kernel.tar file:
http://dl.dropbox.com/u/19019338/captivate-recovery-cwm5-kernel.tar
MD5: 8464e7cee89c7364d62b760c28a4ca73
File size: 6,359,040 bytes
and here's Odin v1.85 if you don't have it:
http://dl.dropbox.com/u/19019338/Odin3_v1.85.zip
MD5: 9a81990a61454402e8714f494bb4eb68
File size: 204,173 bytes
Now, the basics are thus so pay attention:
Since Samsung is never going to release a proper ICS build for us, from what I understand - let me repeat that: from what I understand everything is working with Gingerbread bootloaders, so that's the important aspect. Before you go flashing anything, you'll need to get the Captivate OFF Froyo of any version if you're still using it. So, update that thing using Samsung Kies to the latest version which is that KK4 ROM - that's all that's required.
Once you're done that, and you're "stock" then you would flash the captivate-recovery-cwm5-kernel.tar kernel using Odin (run Odin with Admin privilege, put the Captivate in download mode, connect it, when detected, click the PDA button in Odin to load that captivate-recovery-cwm5-kernel.tar file, then Start to flash it). Once that's done you have the same kernel for KK4 but with CWM ready to go when you are with a proper GB bootloader and you're set.
The only reason I mentioned the Odin One Click above was because I did a few things that "pooched" my Captivate and soft-bricked it at one point but recovered it with Odin and the One Click when Kies couldn't do anything at all. There's a thread around here with all the Odin One Click ROMs, that's where I got mine from.
tl;dr version:
- if you're running any Froyo anything, use Kies to do the upgrade to Gingerbread, NOT the Odin One Click. Kies will update the bootloader from Froyo to GB as required (the Odin One Click was part of what caused my soft-brick, so I learned from the experience)
- if you're already running any Gingerbread ROM, you already have the GB bootloader, so you can use the Odin One Click to go to a pure stock AT&T basic clean ROM as mentioned above
- once you're "stock" use Odin v1.85 to flash the captivate-recovery-cwm5-kernel.tar so you get the same stock kernel but CWM as well
- use CWM to install whatever ROM you want from that point on making sure the ROM archive(s) and any updates or whatever are copied to the internal storage
Personal suggestion: remove the microSD card from the Captivate before doing any flashing at all. Yes it's possible to read from that device (called the external SD in CWM), I simply don't recommend it, ever.
That's about it. The Odin One Click KK4 is not rooted, iirc, I can't say for certain at this moment either way. I only used it a few times to "save" me from the soft-brick. Now that CWM is in there, I've jumped from ROM to ROM over the past week or so but Doc's Master v8 is my fall back stable one so far. Obviously when you load a ROM, look at the Apps and if you don't see SU or SuperUser, it's not rooted.
Click to expand...
Click to collapse
Thanks dude... I only have one question in all this. I network unlock my phone when it was on eclair, i updated to ginger via kies and it stayed unlock will i loose the unlock if i installed cmw and any rom?
Sent from my SAMSUNG-SGH-I897 using Tapatalk 2 Beta-5
Jose0726 said:
Thanks dude... I only have one question in all this. I network unlock my phone when it was on eclair, i updated to ginger via kies and it stayed unlock will i loose the unlock if i installed cmw and any rom?
Sent from my SAMSUNG-SGH-I897 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Can't say on that respect, mine is not even being used as a phone, actually - it's basically a DAP/PMP/PocketPC for me.
Still can't find a service provider with a decent plan that I'd be willing to fork over some money for so, until I find one (if I ever do), this Captivate of mine won't even have a SIM in it.
You won't loose network unlock ever unless your EFS gets modified in anyway...
Sent from my SGH-I897 using xda premium
br0adband said:
I can't upload the Odin One Click ROM, it's too much for my current situation, but here's the captivate-recovery-cwm5-kernel.tar file:
http://dl.dropbox.com/u/19019338/captivate-recovery-cwm5-kernel.tar
MD5: 8464e7cee89c7364d62b760c28a4ca73
File size: 6,359,040 bytes
and here's Odin v1.85 if you don't have it:
http://dl.dropbox.com/u/19019338/Odin3_v1.85.zip
MD5: 9a81990a61454402e8714f494bb4eb68
File size: 204,173 bytes
Now, the basics are thus so pay attention:
Since Samsung is never going to release a proper ICS build for us, from what I understand - let me repeat that: from what I understand everything is working with Gingerbread bootloaders, so that's the important aspect. Before you go flashing anything, you'll need to get the Captivate OFF Froyo of any version if you're still using it. So, update that thing using Samsung Kies to the latest version which is that KK4 ROM - that's all that's required.
Once you're done that, and you're "stock" then you would flash the captivate-recovery-cwm5-kernel.tar kernel using Odin (run Odin with Admin privilege, put the Captivate in download mode, connect it, when detected, click the PDA button in Odin to load that captivate-recovery-cwm5-kernel.tar file, then Start to flash it). Once that's done you have the same kernel for KK4 but with CWM ready to go when you are with a proper GB bootloader and you're set.
The only reason I mentioned the Odin One Click above was because I did a few things that "pooched" my Captivate and soft-bricked it at one point but recovered it with Odin and the One Click when Kies couldn't do anything at all. There's a thread around here with all the Odin One Click ROMs, that's where I got mine from.
tl;dr version:
- if you're running any Froyo anything, use Kies to do the upgrade to Gingerbread, NOT the Odin One Click. Kies will update the bootloader from Froyo to GB as required (the Odin One Click was part of what caused my soft-brick, so I learned from the experience)
- if you're already running any Gingerbread ROM, you already have the GB bootloader, so you can use the Odin One Click to go to a pure stock AT&T basic clean ROM as mentioned above
- once you're "stock" use Odin v1.85 to flash the captivate-recovery-cwm5-kernel.tar so you get the same stock kernel but CWM as well
- use CWM to install whatever ROM you want from that point on making sure the ROM archive(s) and any updates or whatever are copied to the internal storage
Personal suggestion: remove the microSD card from the Captivate before doing any flashing at all. Yes it's possible to read from that device (called the external SD in CWM), I simply don't recommend it, ever.
That's about it. The Odin One Click KK4 is not rooted, iirc, I can't say for certain at this moment either way. I only used it a few times to "save" me from the soft-brick. Now that CWM is in there, I've jumped from ROM to ROM over the past week or so but Doc's Master v8 is my fall back stable one so far. Obviously when you load a ROM, look at the Apps and if you don't see SU or SuperUser, it's not rooted.
Click to expand...
Click to collapse
Thank you SO much for the links and all the time you put in to the explanation. I followed your suggestions, and now I'm running ICS Cyanogenmod 9 in dazzling full color!! You've made what could potentially be a very complicated process extremely easy...I wish I could thank your post 10-fold!! How is your ROM on battery life, btw? I was running CM 7 on my other Captivate, and it wasn't all that great on the battery...waiting to see how 9 works, but my girlfriend still insists it was because I had "too much junk" on the phone...lol! Thanks again!!
Battery life using Doc's Master v8 is as expected, didn't do any extended testing with the CM9 nightly, but then again I'm on the original Samsung stock battery too so, it doesn't hold a full charge anymore like a brand new one would.
I'm hoping to get some cash together soon to get that Anker 2-pack w/charger on Amazon (the 1800 mAh batteries that everyone raves about). I thought about getting the 3500 mAh monster extended on off eBay but, as I'm still trying to locate that Trident Cyclops case (which you just sent me 2 PMs about, thanks), I figure having 2 batteries instead of one would still be a more efficient solution while still being able to keep the Captivate in a nice protective case.
Maybe I need to do some guides for people and put up a donate button to get me some batteries and that case, who knows.
Glad the instructions proved useful.
br0adband said:
Battery life using Doc's Master v8 is as expected, didn't do any extended testing with the CM9 nightly, but then again I'm on the original Samsung stock battery too so, it doesn't hold a full charge anymore like a brand new one would.
I'm hoping to get some cash together soon to get that Anker 2-pack w/charger on Amazon (the 1800 mAh batteries that everyone raves about). I thought about getting the 3500 mAh monster extended on off eBay but, as I'm still trying to locate that Trident Cyclops case (which you just sent me 2 PMs about, thanks), I figure having 2 batteries instead of one would still be a more efficient solution while still being able to keep the Captivate in a nice protective case.
Maybe I need to do some guides for people and put up a donate button to get me some batteries and that case, who knows.
Glad the instructions proved useful.
Click to expand...
Click to collapse
Could any one give me a link to the cm9 ics. I recently flashed aokp and dark night but couldnt use my phone as i got a no network message and when try to ad apns settings were not saving :/
Sent from my SAMSUNG-SGH-I897 using Tapatalk 2 Beta-5
http://goo.im/cm/captivatemtd/nightly
Bottom of the list, and apparently a new nightly was just posted a short time ago (20120412) so... time for a backup and a flash to see what's changed.
And also remember to get the latest Gapps from that site as well when flashing CM (which is 20120317)
http://goo.im/gapps
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'm going to start collecting the various little tid-bits of information that we have scattered across the threads here to hopefully compensate without having a dedicated forum. Eventually I'll add some other guides and such from personal experience, if you know of any Relay related threads or other information located on the interwebs, please drop a link here!
Standard Disclaimer: I am not responsible for what you do to your phone. The information contained in this thread is here to help you do [anything] correctly. If you follow the instructions listed there-in you will be fine, and ask questions if you don't understand something. I am not responsible for what you do with and/or to your phone. If you are unsure about a procedure's outcome, do not proceed with the procedure.
(1)
How to Get Into Download Mode:
1. Hold Power, Vol Down, and Home button simultaneously
2. When "Samsung" appears on the screen let go of the power button but keep the other two pressed down
3. Voila!
Click to expand...
Click to collapse
ROMS:
[CM9][ALPHA]Galaxy S Relay 4G [12/8]
(Use the updated link below instead.) Stock + Odin Flash (+ Rooted System Img File)(Simplified Instructions)
Updated Stock ROM (Has LH1 flash-able via ODIN) Post + tested Tethering Fix(1)
How I reverted my phone to stock + root.
Update from LH1 to LMA2 On Stock ROM w/ preserved root (doesn't remove if you have root, but doesn't give you root) (Untested)
Update from LJ1 to LMA2 on Stock ROM w/ preserved root (doesn't remove if you have root, but doesn't give you root) (Untested)
Root:
[root]\{cm9} samsung galaxy relay 4g (updated 11/19)
General Discussion:
Galaxy S Relay 4G Development Thread
Miscellaneous Information:
Keyboard Customization:
Dillalade's Explanation on How To Set Custom Key Mapping(1)
jarrodlombardo's Key Mapping (Follow Dillalades's guide first)
orange808's Key Mapping
Unsorted, Need to Organize and Determine Relevance (If still applicable or OLD information) or Flesh out supporting information:
nopty's Hiemdal Method (Need to use Heimdal 1.41RC1 or Higher from This Post) (gee ones building heimdal for ubuntu 12.04)
AndriodForums Relay Forum
Sim Unlocking (Need to Verify - Unknown Method) (Sorta Verified)
Nardholio's Links to Create an Odin Flashable Image
NV Dump Backup (Important in case of corrupted IMEI)
Nardholio's Flash Counter Information
gee one dive's into nard's stock rooted img in response to Qualcomm secure boot
nopty's CWM recovery post (10-11-201) Odin Flashable of nopty's CWM Recovery
kornyone's introduction
How to change/remove startup/shutdown sounds
dillalade has issue with 64gb card w/ resolution to issue
fantomex's Andriod WPA2 PSK Authentication issue and resolution
Skinomi Skins for the Relay
gee one fixes his bootloop
gee one's list of bloatware Bloatware gee one was able to remove
Sim Unlocking for those who purchased Retail (no contract)
dillalade's guide to getting Google Now to work on the stock ICS Rom
Nardholio's Untested Tethering Fix
T-mobiles KIES LH1 Update Support Page
gee one investigates the efs partition on the relay Nardholio's response
CWM-Only Flash-able LJ1 Modem
Some changes from stock LH1 to LJ1
Reserved
Reserved 2
Just in Case
how about a link to the original factory rom to restore back to before CM9 ?
Kaczman said:
how about a link to the original factory rom to restore back to before CM9 ?
Click to expand...
Click to collapse
I found one that might work for you, update the OP with the info.
I've got to flash my relay to stock and when I do I'll create a small guide. For now I found an older flash that could be used then KIES could update this ROM to the current LH1 (Need to verify build number).
I need a stock rooted rom, while traveling through the mountains the switching in CM9 isn't working correctly (phone constantly looses service when switching from 4g>3g>Edge frequently).
Here's another sim unlock. I can verify this one as working since I am now using my phone with Solavei. I purchased my phone directly from t-mobile (no contract). I used an AT&T sim to do this method.
http://forum.xda-developers.com/showpost.php?p=36400199&postcount=783
Sent from my SGH-T699 using Tapatalk
Spoxy said:
Here's another sim unlock. I can verify this one as working since I am now using my phone with Solavei. I purchased my phone directly from t-mobile (no contract). I used an AT&T sim to do this method.
http://forum.xda-developers.com/showpost.php?p=36400199&postcount=783
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
Thank you!
Update OP. It's still in the unorganized section, but it's there!
Thank you, is a very useful guide ! :good:
You should post your first post from this thread in the request thread to show everything going on. Should work better than just posting "Samsung Relay, please"
That's the plan after I get it organized. I'm also going to follow the instructions given by kinfauns.
It's a start.
Never really notice that many steps when you go through it quickly, but this is the process that I used to revert my CM9 + CWM recovery to Stock rom + Stock Recovery. I don't know if it was supposed to happen that way, but it did. After flashing the stock PDA file (via odin) I was able to flash the CWM recovery again while adding root to the stock rom.
All of the items talking about (roms, odin, root, ect) except a program to unzip the files can be found in links in the thread in my signature. For reference, I use 7zip and just rightclick>7zip>extract to folder.
How to go Back to stock w/root from CM9:
Download stock rom (newest is the LJ1 tar.rar).
Download Odin
Unzip LJ1 into it's own folder. Navigate to where you unzipped the file.
Rename unzipped file to remove .md5 so it ends in ".tar" instead of ".tar.md5"
Unzip Odin (into it's own folder, navigate to the folder)
Put phone in download mode (Instructions are quoted in the OP of the thread in my sig)
Start Odin (assuming that you have already plugged the usb cable into your computer)
Connect phone (that's in download mode) to computer via USB cable.
ODIN Will have blue "Added!" box after it's recognized the phone (2nd box from the top left)
In ODIN, click the "PDA" Box and select the .tar for LJ1 (the file you unzipped and renamed)
Uncheck the "auto-restart" radiobox under "Added!". Then Click Start.
Wait for odin to finish. Do not touch your phone or click any buttons in the odin program. After It's done, reboot the phone.
Go into recovery mode on the phone (Vol Up Instead of Vol Down)
Wipe SDCard and cache
Reboot phone. It may take a few minutes to pass the samsung screen. The phone will vibrate briefly as is finishes booting
Sign into the phone (google, facebook, ect...this is probably a skipable step).
Turn off phone. Reboot into download mode (Vol Down)
Download nopty's CWM recovery
Unzip file (into it's own folder, navigate to it), removing the .md5 like the file above
Connect phone to computer, after ODIN recognizes ("Added!") it click the PDA button
Navigate to the unzipped and renamed (".tar") CWM file and select it.
Unceck "Auto-Reboot". Click start
Wait to finish, then power off and reboot phone
After phone has re-booted connect to computer
After connected to computer, transfer SuperSU zip(CWM Flashable) to SD card (You'll need to download this too, can be found in the Updated Stock Roms link)
After that's transferred, reboot phone into recovery mode. (Vol Up)
Use CWM to flash the SuperSU zip
Reboot phone
Congrats, you now have a stock rooted phone!
Just the basic frame for the guide, will update with links and what little troubleshooting I know and add guide to OP after it's finished.
Working with you guys is awesome.
Anyways, you guys know the drill.
New Device Request Forum
I may be naive, but I would like to equivocate a thanks with a "signed" on the post above.
PM'd kinfauns, lets hope that he can help us get to the right people!
thanks
thanks
So, has anyone else gotte the software update notification and felt brave enough to run it? I don't want to have what happened with the G2 with their first update and lose root.
Also, the damn notification icon won't go away despite postponing the update.
zakiancel said:
thanks
Click to expand...
Click to collapse
your welcome
mikeybot said:
So, has anyone else gotte the software update notification and felt brave enough to run it? I don't want to have what happened with the G2 with their first update and lose root.
Also, the damn notification icon won't go away despite postponing the update.
Click to expand...
Click to collapse
Not yet for me. I'm playing around with a stock rooted (debloated) rom that gee one made right now, I didn't get the OTA update message though. If you do "update" you should still be able to flash CWM and enable root/superuser again. Keep up updated!
Help
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?
tany.jags said:
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?
Click to expand...
Click to collapse
Broken compass?
I remember seeing a few posts about it too, but I didn't flag them unfortunately. Post the question in the Development thread and we may be able to get you an answer quicker :good:.
tany.jags said:
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?
Click to expand...
Click to collapse
Broken? No, but on occasion, it does momentarily glitch up, but once you start moving it clears itself up. Nothing like what would happen with the G2. (I do also have GPS Status installed as well)
I did run the update after taking a look through the zips and deciding to take the plunge and see; and it does reflash the recovery, and while I do have Odin, I have as yet been unable to flash any CWM again. There are no errors, it just doesn't work. I am as yet hopeful though and will report my progress. I didn't see anywhere in the update where it updated the bootloader, so flashing should still work.