Related
I have built a Froyo ROM from source. I got the Captivate vendor files from Krylon360 over at Cyanogen, updated them, and built a ROM. I was able to get the leaked Froyo Captivate system.img and extract it so I could get the files required for our device. The ROM build cleanly and I was able to restore it to my device but since I have an Eclair kernel it will not boot. I actually read later in a forum that an Eclair kernel won't boot a Froyo system.
Anyway, I am looking for anyone who has a Captivate with the leaked Froyo build installed to try and restore my ROM. It will not brick your phone, I promise. I took a Nandroid backup before restoring and when I saw why it wasn't booting in logcat I booted into recovery and restored my last backup.
I just want to see if this guy will boot properly with a Froyo kernel and also see if I have all the device drivers working, etc.
Thanks!
Why would you go to all the trouble to build a Froyo ROM and then not flash Froyo to your phone and try it yourself?
You flashed it your phone with the 2.1 kernel, so why not install the leaked 2.2 and then flash your custom ROM.
Seems odd you are asking others to try what you will not.
Umm Odin is required to flash the leaked Froyo.
Odin requires Windows.
I am not and never have been a Windows user. I have no way to flash the leaked Froyo to my Captivate, otherwise I would.
Does that answer your question?
It does!
Thanks.
I've been busting my butt to create a stock ROM so that we Captivate users can get rid of AT&T's stupid add-ons. Everyone jumps up and down saying, when will Cyanogen come to the phone.. I actually started working on it... and spending more time than I should.. And I think I have something that will work.
I just need people to help me validate it. And remember, I did try flashing my phone with it so there is no unwillingness on my end.
you're better off with responses with this in the dev section of the forum.. and just post the link for everyone with a big RED SIGN WARNING SAYING DEVS ONLY.
I guess I'll give it a shot. Send me a PM or a link to your files and I'll try it out. I've bricked, unbricked, rebricked, and unbricked again, so I'm pretty confident in my skills lol.
Let me set it up on dropbox real fast. I will put the URL here soon.
Sounds good.
http://dl.dropbox.com/u/6995251/full_captivate.tgz
You should only need system.img. So basically, edit nandroid.md5 and strip out the checksums for the other two files. Then copy nandroid.md5 and system.img to your recovery directory. Mine is /sdcard/clockworkmod/backup.
Report back what you find.
great work gdanke, and looking forward to what vunut has to report back with. i'd vol myself but i've only flashed my phone twice and still feeling pretty awkward with it lol.
Pvster said:
great work gdanke, and looking forward to what vunut has to report back with. i'd vol myself but i've only flashed my phone twice and still feeling pretty awkward with it lol.
Click to expand...
Click to collapse
Had to hold off flashing for now, tried it real quick and got stuck at the white att screen, so flashed back to my normal setup. Follow the thread in the development section.
Sent from my back pocket, swyped with my left butt, cheek using XDA app.
I have been flashing my fascinate for a while now, looking to mod a captivate now. Im looking for something solid. Just looking thru your roms. I'm seeing that some people are having sleep of death on some roms. Also, I know nothing of your rom designations. Us on fascinate are on ec01 atm.. untill I'm more up to speed, what is a good, recent, official froyo, based rom? I prefer niceties, bln, voodoo stuffs, lockscreens, power options, acc batt, deodexed..
I will be doing more studys, but these 2 phones seem more diff than I thought they would be.. Voodoo and froyo are my bottom line..
Ps.. You guys are lucky to have so many custom roms.. I'm lost in your dev section.. however its a curse to new comers lol..
sent from my frozen yogurt filled fascinate!
Our official 2.2 is KB1, and as far as I know the only one that supports the noise cancellation hardware. Cog 4.3.1 is a kb1-based rom (and Torch may also be based on kb1, or I may have just been drunk when I read the description many moons ago).
Everything else seems to be based off of the international i9000 roms with reoriented kernels. Try Serendipity, it's pretty decent if you don't mind the i9000 lineage.
We also have MIUI and CM7. MIUI is based off of CM7, and CM7 is based off of the Nexus S source.
You can also check out FireFly, It's based of Rogers 2.2 and comes with the Speedmod Kernel which doesn't have the sleep death issues. It's solid and reliable annnd it's updated every thursdays..what more can you ask for
I believe Fusion is KB1 based as well. KB1 is the only official Captivate Froyo. Personally, I recommend an i9000 ROM, as they're all 2.2.1 based. I'm running Inception right now, and having great success with it. It's only two days old, though, so probably not something you're ready to flash. Very stable and popular i9000 ROMS that I recommend are Serendipity and Continuum. My personal favorite is Precision, but if you go that route, download version 3.5, not 4.0, as 4.0 is still in alpha stage and has a few bugs. I hope my suggestions have helped in any way and welcome to the Captivate community!
Thanks for the responses,
Are you using cwm 3? Were still on cwm 2.5 on the fassy.. I know there was issues with edify scripting.. I'm looking into your beginners guide when I get on my pc later to see the differences in flashing. I feel a good amount of studying will be needed.. Also, do you have all in 1 odin to stock? And odin to stock froyo? Incase I create a bootloop.
1 more question. being that this is a gsm phone.. Do you still odin radio? Or are they included in the roms? I noticed that many rom posts here don't tell what radio to use, or what is compatible.
Thanks I advance, and sorry for picking brains
sent from my frozen yogurt filled fascinate!
OBatRFan said:
I believe Fusion is KB1 based as well. KB1 is the only official Captivate Froyo. Personally, I recommend an i9000 ROM, as they're all 2.2.1 based. I'm running Inception right now, and having great success with it. It's only two days old, though, so probably not something you're ready to flash. Very stable and popular i9000 ROMS that I recommend are Serendipity and Continuum. My personal favorite is Precision, but if you go that route, download version 3.5, not 4.0, as 4.0 is still in alpha stage and has a few bugs. I hope my suggestions have helped in any way and welcome to the Captivate community!
Click to expand...
Click to collapse
Thanks for the feedback.
sent from my frozen yogurt filled fascinate!
neh4pres said:
Thanks for the responses,
Are you using cwm 3? Were still on cwm 2.5 on the fassy.. I know there was issues with edify scripting.. I'm looking into your beginners guide when I get on my pc later to see the differences in flashing. I feel a good amount of studying will be needed.. Also, do you have all in 1 odin to stock? And odin to stock froyo? Incase I create a bootloop.
1 more question. being that this is a gsm phone.. Do you still odin radio? Or are they included in the roms? I noticed that many rom posts here don't tell what radio to use, or what is compatible.
Thanks I advance, and sorry for picking brains
sent from my frozen yogurt filled fascinate!
Click to expand...
Click to collapse
I believe we're on CWM 3. something or other. Never had an issue with it.
We have an ODIN one click back to stock which is recommended to do before flashing and new ROM. As for the radio, I honestly have no clue about that.
neh4pres said:
Thanks for the responses,
Are you using cwm 3? Were still on cwm 2.5 on the fassy.. I know there was issues with edify scripting.. I'm looking into your beginners guide when I get on my pc later to see the differences in flashing. I feel a good amount of studying will be needed.. Also, do you have all in 1 odin to stock? And odin to stock froyo? Incase I create a bootloop.
1 more question. being that this is a gsm phone.. Do you still odin radio? Or are they included in the roms? I noticed that many rom posts here don't tell what radio to use, or what is compatible.
Thanks I advance, and sorry for picking brains
sent from my frozen yogurt filled fascinate!
Click to expand...
Click to collapse
yes modem is included in ROM package itself
modest_mandroid said:
Our official 2.2 is KB1, and as far as I know the only one that supports the noise cancellation hardware. Cog 4.3.1 is a kb1-based rom (and Torch may also be based on kb1, or I may have just been drunk when I read the description many moons ago).
Everything else seems to be based off of the international i9000 roms with reoriented kernels. Try Serendipity, it's pretty decent if you don't mind the i9000 lineage.
We also have MIUI and CM7. MIUI is based off of CM7, and CM7 is based off of the Nexus S source.
Click to expand...
Click to collapse
Torch is kb1 based, but not updated in awhile.
We call them modems, not radios.
You should look at the Onix kernel. It's great.
Continuum v4 unthemed looks alot like stock.
Good luck, and welcome to the captivate forums.
I seem to be hanging up on rooting using super 1 click.. Says waiting for device.. Thinking about odin to stock then trying again.. Unless someone has a better option.
sent from my frozen yogurt filled fascinate!
Thank you all..
sent from my frozen yogurt filled fascinate!
Are you trying to root so you can go to a custom ROM? If so, I wouldn't worry about rooting. I attached an update.zip that will get you CWM. Put the update.zip and the zip of whatever ROM you want to flash on your internal sdcard. Turn the phone off, hold both volume keys and the power keys. The AT&T logo should come up, keep holding the buttons. The logo should pop up again, now let go. it should go to recovery. Now select reinstall packages. The phone should reboot and go to recovery again. Select reinstall packages again and it should go to CWM. I'm assuming you should know how to flash a zip from here if you've had Fascinate experience. The flashing of the ROM will root your phone.
Hope this helps! If you have any questions, just ask.
Andromeda3 is based off the Georgio Armani Cappy. It's a 2.2 rom that has all the goodies you listed. The devs did a fantastic job on it. It's not updated very often because it doesn't need to be. It's fast, looks good, and has everything you want.
thanks... if i can get out of this fix im in ill do that... however i followed this post
http://forum.xda-developers.com/showthread.php?t=818439&highlight=odin+stock
and seem to be stuck at factory rfs.. dont dare unplug yet... i know on my fassy it would not be a big deal.. interrupt and try again.., but i dont know if i could lose download mode if i interrupt on this phone..
neh4pres said:
thanks... if i can get out of this fix im in ill do that... however i followed this post
http://forum.xda-developers.com/showthread.php?t=818439&highlight=odin+stock
and seem to be stuck at factory rfs.. dont dare unplug yet... i know on my fassy it would not be a big deal.. interrupt and try again.., but i dont know if i could lose download mode if i interrupt on this phone..
Click to expand...
Click to collapse
This has happened to me multiple times. Unplug, pull battery, restart ODIN, put battery in, and repeat the flashing process.
OBatRFan said:
This has happened to me multiple times. Unplug, pull battery, restart ODIN, put battery in, and repeat the flashing process.
Click to expand...
Click to collapse
got stuck on sbl bin that time... am i doing something wrong?.. im just opening odin 3, then place pit, place tar.. click start... should i also click partition? or maybe i have a corrupt copy... while i wait for a response ill re download..
thanks for being such a help
Most ROMs are not based on Captivate Froyo, because it sucks.
And Gingerbread ROMs are right around the corner. Just waiting on Samsung releasing the i9000 kernel source.
Sent from my Captivate
Try this version of ODIN: http://forum.xda-developers.com/showthread.php?t=731989&highlight=ODIN
One-click, so need need for PDA and such. That's what I use, but it all depends on whether or not you have three button combo working. If that version doesn't work, just keep trying on both versions, switch USB ports each time.
OBatRFan said:
I believe we're on CWM 3. something or other. Never had an issue with it.
We have an ODIN one click back to stock which is recommended to do before flashing and new ROM. As for the radio, I honestly have no clue about that.
Click to expand...
Click to collapse
we still use cwm 2.5.x.x because as was said 3.x.x.x have issues.
flashing to stock isnt needed anymore as all roms do a wipe, odin should only be used as a repair tool not a normal part of the process.
op just curious what was your phone running before you started odin? whoever posted the update.zip is right all this other stuff is just spinning your wheels. if it was on 2.1 then put that zip on the root of your sd reinstall packages twice and you will be in cwm, from there you can flash any rom. if you were on 2.2 then do a search for 3e recovery sighning and once you get that cracked follow the preceeding instructions
okay.. im all fixed now.. just to let everyone know, it was a computer issue (windows fail). and my usb was not talking correctly. a simple restart solved the issue.. i was worried i was in over my head, and i thank you all for helping. and i apologize for turning this page into a rescue center lol.
i will try that update zip now.. and im on my way to great roms im sure.. you are all a terrific bunch, and im glad to be a part of this forum
I've tried searching for the solutions to this, but some of them are difficult to search and I'm struggling to get relevant results. So I apologize if any of this has been covered elsewhere.
Anyhow, I just installed the ParanoidAndroid ROM last night, and it all went very smoothly, and I was pleased. But, there seem to be a couple issues that either I need to iron out, or that the devs need to. And I'm fully willing to believe it's an issue on my end and not theirs, so, here we go:
1) In CWM, the top half of the screen or so has the rainbow glitch going on and there's a de-centered kind of effect happening that makes it very difficult to use.
2) I'm unable to get my external SD card to mount. I've seen plenty of threads about this similar issue, and I've tried tweaking the build.prop entry regarding this, but nothing I'm doing is helping.
3) The flash only works once per boot, even with included flashlight app. I haven't tested the flash's functionality in the camera yet. But in the flashlight app, the flash will turn on, and when I turn it off, it won't come back on until after a reboot.
4) I now have two installations of the stock Gallery app (com.android.gallery3d and com.google.android.gallery3d). I'm sure I can just uninstall one, but is there one that would be wiser to uninstall?
Otherwise, everything else seems to be working just fine. Thank you all very much in advance.
I've since discovered and fixed a new problem. My phone was apparently not sending or receiving any MMS messages, over WiFi or otherwise. But the APNs described in this post fixed that entirely:
http://forum.xda-developers.com/showthread.php?p=23806717#post23806717
As problem #4 from above goes, I deleted the com.android.gallery3d app and kept the com.google.android.gallery3d app as there were internet and syncing features that were omitted or nonfunctional from the former one.
Just so you know, if you read through the paranoid thread in the dev section or any of the ics ROM threads actually, all of your questions r covered. I cangive you answered/jumping off points for your questions.
1. The rainbow distortion comes from having Froyo bootloaders instead of GB. To fix this you will need to use Odin or Heimdall to flash the GB bootloaders. Look in the ISET Super Everything thread that's stickied in the dev section. BE SURE to flash something else with Odin or Heimdall (whichever you choose) before you try flashing the bootloaders. If you lose your connection while trying to flash bootloaders, you can hard brick your phone which basically means you have a shiny coaster.
2. Your external sd card is found in the emmc folder on ics ROMs. You need a root enabled file explorer to open it.
3. Using your camera flash as a flashlight which I believe is referred to as torch is one of the few known remaining bugs on Infuse ics ROMs. The flashlight app that is included is currently the only way to get it working. The flashlight should turn on everytime you open the app but it won't turn back on if you turn it off while in the app.
4. MMS is an issue with the APN settings. Look at the last few pages in the dev section. I know it was recently covered on a couple different ics ROMs threads. To get to the APN settings, go through the following path in the settings.
More (under data usage) > Mobile Networks > Access Point Names, click on the AT&T listing, then change MMS Proxy to 66.209.11.32
I'm pretty sure that is all you have to do to fix MMS but read some dev threads for more info. I think you can also try to look in the Dev Tools app if it is included with the ROM. In the app, click connectivity then start MMS. Again, further reading should give you more info.
Boz™
Sent from my SGH-I997 using xda app-developers app
Yeah, the flashlight thing, I knew was a known bug. But the latest update claiming that "all bugs squashed" misled me, I guess. Because that bug obviously persists. But, c'est la vie.
As the rainbow glitch goes, I never installed Froyo on here, I went from stock to Gingerbread to... actually, here's specifically what happened:
•Initially, I installed 3e Recovery and CWM on my stock Android 2.2 per the instructions here, http://www.youtube.com/watch?v=Y09p-J_g_Rg, and everything went fine.
•Then I flashed Gingerbread UCLB3 per this thread, http://forum.xda-developers.com/showthread.php?t=1508619, but unfortunately, I made a dumb mistake. I neglected to disable Voodoo Lagfix first and softbricked my phone.
•So, I went back to the Infuse Super Everything Thread and found this fix, http://forum.xda-developers.com/showthread.php?t=1092021, brought my phone back to stock, just fine.
•Then I flashed to UCLB3 the same way as before, only this time disabling Voodoo and it all worked perfectly.
•Then I immediately flashed to ParanoidAndroid and everything went as described in the thread and now here I am with the CWM glitch.
So I've only been stock or Gingerbread ever before on my phone.
Anyone know how to simply change the font or install a new one?
Sent from my SGH-I997 using xda premium
I use ROM Toolbox Pro.
Edit: Check the Paranoid Android dev thread end of page 32 and beginning of page 33. The guy that maintains the PA port just posted a link and instructions for the fix to rainbow recovery.
I'm no expert so I may b wrong but I'm pretty sure that if you had a stock AT&T infuse then it most likely came with Froyo originally. Just bc you flashed a GB ROM doesn't mean you got the bootloaders. To get the GB bootloaders, you need to run Heimdall a second time with the "Install Bootloaders" checkbox checked. I'm not exactly sure how it works in Odin but I think you have to have a file in the PDA slot in order to get the bootloaders installed.
I do know that if you have rainbows, it is bc you have Froyo bootloaders. Our at least that is the only reason I've ever heard of and I've read of people with the issue numerous times. I would just read through some of the dev ics threads bc there have been a few times in the last week that I've seen people pay steep by step instructions explaining exactly which Heimdall or Odin to use. I just know that you have to take extra steps to install GB bootloaders. With Heimdall that means checking the flash bootloaders checkbox. They do this bc it can hard brick your phone so they don't want you to install them unless absolutely necessary.
Boz™
Sent from my SGH-I997 using xda app-developers app
Ah-ha! Very good, someone else is having my same problems, lol. I'll definitely be using Odin, as that's how I fixed my softbrick issue and I could never get Heimdall to install on my computer properly (Java issues or something, couldn't figure it out and Odin worked anyway).
Do you know if flashing the bootloader will cause any loss of information or settings? Or will it affect nothing else?
I'm not 100% sure on that one. When I did it, I was using Heimdall to fix my soft bricked phone at the same time so I was basically starting fresh. I'm not sure if it is possible to just flash bootloaders in the Odin PDA slot and keep everything else. I would assume that you would lose everything and have to reflash the ROM from recovery but that's just an assumption.
I would get titanium backup (if u don't already have it) and backup everything and sync with your Gmail account just in case. That way u can save it apps and their settings.
You may b able to ask that question on the PA dev thread and get a better answer.
Boz™
Sent from my SGH-I997 using xda app-developers app
There's an XDA Forum restriction on newbies. I can't post in any Dev forums until I've... done something, I forget. Ten posts or ten thanks. I forget what. Either way, I'm not allowed in there yet. lol
Anyhow, based on some threads I've found, it seems possible to flash only the bootloader in Odin. I'm still just waiting to find out how much information is lost in the process before I dive into it.
But yeah, I do have Titanium, and now that I have everything installed and set up just the way I like it, it is time for a backup anyway.
Supposing I need to, is there any problem restoring system apps and data once I do this? Because everything will be identical, minus the bootloader. I just know I've read enough about the dangers of restoring system data on the threads here to be cautious. Even though I'll just be going from ParanoidAndroid to the same flash of ParanoidAndroid, plus a new bootloader, but better safe than sorry.
Thanks for all your help, man.
Appears as though that question's already been answered here:
http://forum.xda-developers.com/showthread.php?t=1603220&page=5
Bottom of page 5 states somewhat affirmatively that no data will be lost. So, lovely. Now I've just got to flash the bootloader, and then work on my forum searching skills. I can never find ****, when clearly it's somewhere. lol
dstarr3 said:
2) I'm unable to get my external SD card to mount. I've seen plenty of threads about this similar issue, and I've tried tweaking the build.prop entry regarding this, but nothing I'm doing is helping.
Click to expand...
Click to collapse
Figured out the emmc part but how do you actually open the external SD on your pc?
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 have a samsung galaxy s 4g from t-mobile I was trying to upgrade from ginger bread to ice cream sandwich and now the phone keeps restarting. When it turns on it shows the samsung galaxy s 4g startup then it shows the ice cream sandwich i tried to download and it shows a progress bar when it gets to the very end it restarts and does the same process over and over again. I tried to plug into computer and the computer says my device is not recognized. I need help!! What do I do? If video is needed I will provide one
jeffreylin_ said:
There is no OTA update to ICS for this device. If you messed it up, you should use the one click back to stock, which will revert everything back to the way it was when you first got it.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I know but I saw a video on youtube about it so i tried it and it just keeps restarting. Would you mind explaining how to do that because it I can't connect my phone to the computer it turns off every 15 secs and I can't go into recovery mode either.
The good news is that it is nearly impossible to "hard brick" an SGS4G. That you are seeing it repeatedly trying to start up tells me that it's more that you just have improper firmware on your device.
Take a look a the heimdall "one-click" collection http://forum.xda-developers.com/showthread.php?t=1358498
@lumin30 has a great walk-through as well -- http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
The most difficult thing about using them is getting the right drivers installed on your computer for your phone (and ROM).
jeffsf said:
The good news is that it is nearly impossible to "hard brick" an SGS4G. That you are seeing it repeatedly trying to start up tells me that it's more that you just have improper firmware on your device.
Take a look a the heimdall "one-click" collection http://forum.xda-developers.com/showthread.php?t=1358498
@lumin30 has a great walk-through as well -- http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
The most difficult thing about using them is getting the right drivers installed on your computer for your phone (and ROM).
Click to expand...
Click to collapse
I can't do this because when i plug my phone in to the computer it says device not recognized and the phone restarts about every 15 seconds. If you need to see a video I can provide one. I need to fix it because i'm stuck with this phone for a few more months.
Google samsung usb download jig. You can buy one or make your own for just a few bucks. There is a thread or two on xda on making one. Couple of threads on how to get into download mode too.
Sent from my SAMSUNG-SGH-I547 using xda app-developers app
MuShRo0m said:
I can't do this because when i plug my phone in to the computer it says device not recognized and the phone restarts about every 15 seconds. If you need to see a video I can provide one. I need to fix it because i'm stuck with this phone for a few more months.
Click to expand...
Click to collapse
"Device not recognized" is Windows' polite way of saying that it can't make sense of drivers. I have a few polite things to say about Window's handling of drivers, but let's just say that it is tweaky, at best, and you apparently can only have one set of "similar" drivers installed at a time. You will have to work with the drivers once you get Download Mode under control.
That is is still rebooting seems to suggest that you don't have the power off / hold volup/vol dn / plug in USB sequence quite right.
jeffsf said:
"Device not recognized" is Windows' polite way of saying that it can't make sense of drivers. I have a few polite things to say about Window's handling of drivers, but let's just say that it is tweaky, at best, and you apparently can only have one set of "similar" drivers installed at a time. You will have to work with the drivers once you get Download Mode under control.
That is is still rebooting seems to suggest that you don't have the power off / hold volup/vol dn / plug in USB sequence quite right.
Click to expand...
Click to collapse
Thank you I just fixed it. I thought I was screwed thanks so much!! Do you know anything good to put on the device that is for the sgs4g because the last time I put the wrong ones and it ended up how it did. I tried valhalla final do you know any better ones.
I'm glad you got it going again! With luck, you won't have to try that again, but it is a great device to play around with as it is rather hard to get it to "hard brick" to the point where you can't get it into download mode and start again. Just keep lots of backups
There are lots of great ROMs out there for this device, in a few different flavors. You generally need to be careful how you upgrade between the flavors, especially as the big upgrade steps are often taken for granted by current ROMs
Froyo (I'll go out on a limb and say you don't want this)
Gingerbread, BML
Gingerbread, MTD
Ice Cream Sandwich (MTD only, I believe)
JellyBean (MTD only)
BML is the "stock" low-level disk routines used by Samsung ROMs, as well as some custom Gingerbread ROMs. MTD is an open-source alternative to BML that is popular with later Gingerbread ROMs, as well as probably all ICS and JB ROMs. If you are going to use an MTD ROM, you should find a solid MTD Gingerbread ROM to do the switch-over from BML to MTD to make sure it goes smoothly.
I can't really say which is "best" between all the ROMs. There are many good ones out there. A lot of people will have which ROM they use or like in their signature.
With any ROM, read the main thread to see what things might not work for you if you try the ROM.
Some of the general things that are pretty much universal are:
ICS
WiFi Calling doesn't work
Indicated WiFi signal level appears lower
JB
Built-in GPS doesn't work
WiFi Calling doesn't work
Indicated WiFi signal level appears lower
jeffsf said:
I'm glad you got it going again! With luck, you won't have to try that again, but it is a great device to play around with as it is rather hard to get it to "hard brick" to the point where you can't get it into download mode and start again. Just keep lots of backups
There are lots of great ROMs out there for this device, in a few different flavors. You generally need to be careful how you upgrade between the flavors, especially as the big upgrade steps are often taken for granted by current ROMs
Froyo (I'll go out on a limb and say you don't want this)
Gingerbread, BML
Gingerbread, MTD
Ice Cream Sandwich (MTD only, I believe)
JellyBean (MTD only)
BML is the "stock" low-level disk routines used by Samsung ROMs, as well as some custom Gingerbread ROMs. MTD is an open-source alternative to BML that is popular with later Gingerbread ROMs, as well as probably all ICS and JB ROMs. If you are going to use an MTD ROM, you should find a solid MTD Gingerbread ROM to do the switch-over from BML to MTD to make sure it goes smoothly.
I can't really say which is "best" between all the ROMs. There are many good ones out there. A lot of people will have which ROM they use or like in their signature.
With any ROM, read the main thread to see what things might not work for you if you try the ROM.
Some of the general things that are pretty much universal are:
ICS
WiFi Calling doesn't work
Indicated WiFi signal level appears lower
JB
Built-in GPS doesn't work
WiFi Calling doesn't work
Indicated WiFi signal level appears lower
Click to expand...
Click to collapse
Ok thanks for the suggestions but I have been looking at the tutorials on this and it says you need cwm but that isn't supported by this device sgs4g. What do i do? Here is what I am trying to install http://forum.xda-developers.com/showthread.php?t=2587589
MuShRo0m said:
...you need cwm but that isn't supported by this device sgs4g.
Click to expand...
Click to collapse
It is true that you can't install Clockwork recovery by itself on the SGS4G. However, the custom kernels have either CWR or TWRP "built in" to them. (On the SGS4G, kernel and recovery bound together and flashed as a single unit.)
Here is what I am trying to install http://forum.xda-developers.com/showthread.php?t=2587589
Click to expand...
Click to collapse
Well, that is quite a first ROM to try to flash! Let's see, it says "beta" in the header, it's been out for under 24 hours, people are reporting difficulties flashing it, it has a different partition structure than any other SGS4G ROM, oh, and it's the first KitKat ROM for the phone, so the Android part of the phone is very different and potentially still has major bugs. I think you're in for a world of hurt if you try something that hasn't stabilized to the point that people are generally successful with it, especially if you aren't comfortable with the whole flashing process yet.
I'd suggest one of the well-proven ICS ROMs as a start. The are relatively robust in their ability to install and generally perform very well on the phone. Take a couple weeks with it to know how it performs on the phone for you and then look again at what you might want to try out.
While you can generally upgrade your data from one Android release to the next using a tool like Titanium Backup, going back is dicey, at best. I didn't decide to upgrade my day-today phone from GB to ICS for quite some time after the ROMs were available for just that reason. I'd hate to find out that there was a show-stopper bug and I couldn't go back to GB without losing my data.
jeffsf said:
It is true that you can't install Clockwork recovery by itself on the SGS4G. However, the custom kernels have either CWR or TWRP "built in" to them. (On the SGS4G, kernel and recovery bound together and flashed as a single unit.)
Click to expand...
Click to collapse
I'm a noob when it comes to this stuff I have been looking around and I can't find any custom kernels that have it pre installed could you please help me on this.
jeffsf said:
Well, that is quite a first ROM to try to flash! Let's see, it says "beta" in the header, it's been out for under 24 hours, people are reporting difficulties flashing it, it has a different partition structure than any other SGS4G ROM, oh, and it's the first KitKat ROM for the phone, so the Android part of the phone is very different and potentially still has major bugs. I think you're in for a world of hurt if you try something that hasn't stabilized to the point that people are generally successful with it, especially if you aren't comfortable with the whole flashing process yet.
I'd suggest one of the well-proven ICS ROMs as a start. The are relatively robust in their ability to install and generally perform very well on the phone. Take a couple weeks with it to know how it performs on the phone for you and then look again at what you might want to try out.
While you can generally upgrade your data from one Android release to the next using a tool like Titanium Backup, going back is dicey, at best. I didn't decide to upgrade my day-today phone from GB to ICS for quite some time after the ROMs were available for just that reason. I'd hate to find out that there was a show-stopper bug and I couldn't go back to GB without losing my data.
Click to expand...
Click to collapse
That makes sense I'll wait for slim kat until the bugs have been fixed and until I get the hang of this.SO just to be certain I should start from ics then move up to jelly bean?
It's my personal opinion that the GB and ICS ROMs are the most stable and reliable for "daily driver" phones. Others like the JB experience. KitKat has a lot of potential, but I'd wait a bit until it settles down. The first few releases on any new Android version are generally a bit rough, even when from the best of devs.
The AntonX Basic kernel from the heimdall one-click thread should get you what you need to get started.
I'm a little puzzled though, how you flashed the first ROM if you didn't have CWR or some other recovery already installed. If it was ROM Manager that you used, it definitely would have caused problems (and will if you use it again).
jeffsf said:
It's my personal opinion that the GB and ICS ROMs are the most stable and reliable for "daily driver" phones. Others like the JB experience. KitKat has a lot of potential, but I'd wait a bit until it settles down. The first few releases on any new Android version are generally a bit rough, even when from the best of devs.
The AntonX Basic kernel from the heimdall one-click thread should get you what you need to get started.
I'm a little puzzled though, how you flashed the first ROM if you didn't have CWR or some other recovery already installed. If it was ROM Manager that you used, it definitely would have caused problems (and will if you use it again).
Click to expand...
Click to collapse
Ok I will try this right now see if I can even follow the tutorial and I got valhalla by using sgs kernel flasher which is an app on the marketplace.
jeffsf said:
It's my personal opinion that the GB and ICS ROMs are the most stable and reliable for "daily driver" phones. Others like the JB experience. KitKat has a lot of potential, but I'd wait a bit until it settles down. The first few releases on any new Android version are generally a bit rough, even when from the best of devs.
The AntonX Basic kernel from the heimdall one-click thread should get you what you need to get started.
I'm a little puzzled though, how you flashed the first ROM if you didn't have CWR or some other recovery already installed. If it was ROM Manager that you used, it definitely would have caused problems (and will if you use it again).
Click to expand...
Click to collapse
ok so I decided to go for slimkat 4.4.2 and I actually installed it correctly but I don't have the google play store and all that I tried to install gapps but not sure if I had the right version. When I was flashing them it said installation successful but when the phone rebooted it says the applications stopped working.
MuShRo0m said:
ok so I decided to go for slimkat 4.4.2 and I actually installed it correctly but I don't have the google play store and all that I tried to install gapps but not sure if I had the right version. When I was flashing them it said installation successful but when the phone rebooted it says the applications stopped working.
Click to expand...
Click to collapse
Hullo man (or mam) I'm the tooth cavity bringer as u can see (w kitkat or sth like that). For your issue, I think you first should get used to installing custom ROM on this phone first, with Recovery: backup & restore procedure, flashing zip,... and heimdall oneclick procedure as jeffsf has been avised you tho before installing kitkat. And yeah, a user got Playstore work out by heimdall oneclick back to stock, and follow my instruction in the slimkat thread again carefully (super clean install) so you can try if you know what you are doing then.
If you are feeling confused and frustrated w the instruction and bugs that might happen to your phone, you can/should flash sth considered stable first like ICS ROMs (that Jeffsf recommended) w Jeffsf's kernels as they are easier to flash and almost bug-free .
Sent from my GT-N7000 using Tapatalk 2
daothanhduy1996 said:
Hullo man (or mam) I'm the tooth cavity bringer as u can see (w kitkat or sth like that). For your issue, I think you first should get used to installing custom ROM on this phone first, with Recovery: backup & restore procedure, flashing zip,... and heimdall oneclick procedure as jeffsf has been avised you tho before installing kitkat. And yeah, a user got Playstore work out by heimdall oneclick back to stock, and follow my instruction in the slimkat thread again carefully (super clean install) so you can try if you know what you are doing then.
If you are feeling confused and frustrated w the instruction and bugs that might happen to your phone, you can/should flash sth considered stable first like ICS ROMs (that Jeffsf recommended) w Jeffsf's kernels as they are easier to flash and almost bug-free .
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
thanks for the suggestions I installed slimkat but I didn't have the play store because I forgot to flash the gapps now I finally got everything working it runs pretty smooth. I wanted to challenge myself so I chose the harder one and I did okay.