Related
Has anyone tried using the i9000 Froyo rom (like this) with the new Froyo kernel? Could I try it, using the following procedure? I would like to try it, but don't want to brick my phone.
1) Remove SIM and MicroSD
2) Open Odin, load the i9000 Froyo PDA file and the i9000 Froyo CSC file.
3) Leave auto reboot checked and repartition unchecked.
4) Boot the phone into download mode.
5) Flash.
6) After reboot, get back into download mode.
7) Reopen Odin and load the stock Captivate kernel (From this thread) in the PDA box and a pit file (which one???).
8) Ensure auto reboot is checked and repartition is not checked.
9) Flash.
Would this work? Also, what if any PIT file would I use?
Thanks in advance
I'm trying this now. First attempt from the Cappy leaked Froyo failed. I just flashed back to JF6. Gonna try above with the I9000 pit and see what happens.
If it was that easy we wouldn't have needed xcaliburs reorient kernel Unless Samsung made some major changes under the hood your probably stuck with one ROM+kernel or the other for right now.
TMC_Sherpa said:
If it was that easy we wouldn't have needed xcaliburs reorient kernel Unless Samsung made some major changes under the hood your probably stuck with one ROM+kernel or the other for right now.
Click to expand...
Click to collapse
but i dont think the reorient kernel was NEEDED. i ran the i9000 with stock captivate kernel (as instructed in that post) for a week or 2 and didnt have any problems whatsoever.....BT and HSUPA didnt work, but small price to pay
now that we have a kernel from 2.2 build, we should be able to apply 2.2 captivate kernel with JPK and run it...
i think i will give it a shot today
I just tried it using the steps I outlined above. I would *not* reccomend doing it; it didn't work for me. Once I flashed the kernel, the phone would get stuck at the AT&T "World Phone" screen (formerly the i9000 splash, but I guess the kernel changes that). Being stuck at this screen, it would intermittently vibrate 1-buzz, 2-buzzes, and repeat about every second. I assume that's some sort of error message? After trying to reboot it a few times, I eventually got the "phone-!-computer" screen, and was only able to successfully reflash it by removing the battery, holding volume down, and plugging in USB, and was able to get into download mode to flash with Odin. Heads up.
Didn't work for me either....and, the usual method to get in to download mode (off and plugged in to PC with battery charge icon showing, holding down vol up/down and then power and the release power at black screen) did not work. Had to power off, remove battery & SIM, then hold down vol up/down and plug USB in and then release vol up/down.
boomerod said:
Didn't work for me either....and, the usual method to get in to download mode (off and plugged in to PC with battery charge icon showing, holding down vol up/down and then power and the release power at black screen) did not work. Had to power off, remove battery & SIM, then hold down vol up/down and plug USB in and then release vol up/down.
Click to expand...
Click to collapse
Basically, same here. I guess we'll have to wait for someone to figure this out.
well damn....thats lame. how come the i9000+cap kernel worked great in 2.1?
Pirateghost said:
well damn....thats lame. how come the i9000+cap kernel worked great in 2.1?
Click to expand...
Click to collapse
2.2 and 2.1 are different software so its easily possible that Samsung changed whatever allowed it to work.
Sent from my SAMSUNG-SGH-I897
the 2.2 leak is basically an i9000 rom, its not fully tweaked to ATT wants yet... thankfully
yeah I can't understand why on earth you would want to run an i9000 firmware which is at least just as buggy but not designed for your device at all... JPK (latest i9000) was built the same day as JI6...
Speaking for myself, I just want Bluetooth voice controls, which work on the I9000 Froyo but not on this leaked Cappy Froyo. I confirmed that again today by flashing to I9000 (most recent release on Samfirmware) - BT voice commands worked perfectly.
boomerod said:
Speaking for myself, I just want Bluetooth voice controls, which work on the I9000 Froyo but not on this leaked Cappy Froyo. I confirmed that again today by flashing to I9000 (most recent release on Samfirmware) - BT voice commands worked perfectly.
Click to expand...
Click to collapse
I was running i9000 ROM as well with captivate Froyo kernel (in which I noticed a slight increase in performance) but there was no voice while calling only a hiss. I installed the modem.bin from Captivate froyo and it worked.. for 10 sec and then I got reboot loop and decided to go to stock froyo. Wondering if there is a possibility to make it work with a modem from 2.1, but I believe is highly improbable.
Now I am back at the AT&T build but I must say that there are few things which I really don't like. Like the lag when changing home screens. If I go to 7 and press home button it takes 1-2 seconds to get back to the main one.
I indeed found it much faster in opening gallery and loading the thumbnails plus very good results in Linpack. Quadrant still doesn't give me more than 985 which is half of 2.1 with lag fix but that's not relevant.
I want to run i9000 rom because I am from Europe and I would like to have Swype in Romanian for example + that the i9000 rom doesnt mind if I have the "Use wireless networks" On or Off, GPS will still connect in less than 10 sec, thing impossible to achieve with ATT ROM (from my experience).
the reason why i want i9000 froyo with 2.2 capt kernel is because i really like 'euro stock' rather than 'US stock,' which is edited after the carriers mess with it. i know u can erase those and stuff, but i prefer using a clean rom, and adding my own configurations with an update.zip.
han.azuki said:
the reason why i want i9000 froyo with 2.2 capt kernel is because i really like 'euro stock' rather than 'US stock,' which is edited after the carriers mess with it. i know u can erase those and stuff, but i prefer using a clean rom, and adding my own configurations with an update.zip.
Click to expand...
Click to collapse
same here....i hope someone takes on this task soon...i would love i9000 froyo on my captivate
Pirateghost said:
same here....i hope someone takes on this task soon...i would love i9000 froyo on my captivate
Click to expand...
Click to collapse
+2 I love the i9000 rom and I'm not sure I'll update to 2.2 until we get one. I had Froyo on my N1 so I've used it before but after getting rid of the stock rom I don't want to go back. I don't want to update just to update.
Quite an adventure
OK, so even though this is embarrassing at some level, I'm still going to share this experience with the forum (just in case someone else does this to themselves).
So, as the OP posted (had been thinking about it since 3AM this morning after I found that this leaked Cappy Froyo does not have BT voice commands implemented) I decided to try out the I9000 Froyo (most recent posted on samfirmware.com) and then try flashing the Cappy Froyo kernal to see if I could get a working combo. Well, I never got as far as the OP in that I was never able to successfully flash the Cappy kernal.
I ended up stuck (for most of the day) with a very unstable combo: I9000 Froyo with Cappy JF6 baseband. Originally, the problem was I could not get in to download mode using all the normal, well-know methods. I was then able to - see my earlier post - but was unable to get past File Analysis in Odin. I then tried rebooting and then was not able to get back in to download mode to save my life, not even using the method that originally worked for me. So, here is the lesson I learned (other than not screwing around too much with my phone):
It seems that I needed a download mode method for the I9000. I got to battery charge screen with phone connected to PC, then held down ONLY the volume down button and the power butting and presto, download mode.
I still had issues getting past File Analysis; what ultimately worked was JF6 on-click solution. So, after all day screwing around with this, including trying to get into download mode through adb (to no avail), I've learned my lesson. I'm back to where I've been for the past month: really thinking about abandoning AT&T and this crappy, broken GPS, slow to get Froyo Cappy (which otherwise I like very much) and switching to Sprint and the Evo. Sigh...I'm under contract and don't want to pay a cancellation fee, damn!!
Here's a snipped from logcat while the phone is stuck at the AT&T logo. If anyone knows what to do about this...
http://pastebin.ubuntu.com/504711/
boomerod said:
It seems that I needed a download mode method for the I9000. I got to battery charge screen with phone connected to PC, then held down ONLY the volume down button and the power butting and presto, download mode.
Click to expand...
Click to collapse
I had to do the same, except that when I did it, I was getting the Phone-!-Computer screen.
damis648 said:
I had to do the same, except that when I did it, I was getting the Phone-!-Computer screen.
Click to expand...
Click to collapse
Did you ever get back to stock? I think we had a good thought...
I guess I have to admit that I like to tinker. What I need to do is get another phone that I leave alone so I don't loose my communication to the world.
-Edit-
Back at the leaked Cappy Froyo...guess I'll just live with this until we finally get a fully functional Froyo.
So i decided to go on a Flashing spree today for no reason, i just felt like it..
I started out by flashing 2.2 on my 2.1 phone, that all worked out quite well, but for some reason i could not root it. ( I used http://forum.xda-developers.com/showthread.php?t=845558) It all worked out nicelly but since i could not root it, i just game up on it.
After searching i found http://forum.xda-developers.com/showthread.php?t=734475 to revert my phone back to its original firmware. I have a Galaxy s Vibrant, so i thought it was the correct thing. But since i installed it i have alot of problems.
First of all, when i plug it into my USB the phone auto turns off. And it will not charge when the usb is in.
I have rom manager installed, but when i try to run a rom, i keep getting the error (status = bad ).
Also the phone wont recognise my SimCard so i cant stay with this firmweare anyways.
flash back to a stock Froyo
then boot into the Recovery Mode
then wipe data, and wipe cache
see if that helps
Do you know the best place where i can get a stock froyo rom ?
amnoric said:
So i decided to go on a Flashing spree today for no reason, i just felt like it..
I started out by flashing 2.2 on my 2.1 phone, that all worked out quite well, but for some reason i could not root it. ( I used http://forum.xda-developers.com/showthread.php?t=845558) It all worked out nicelly but since i could not root it, i just game up on it.
After searching i found http://forum.xda-developers.com/showthread.php?t=734475 to revert my phone back to its original firmware. I have a Galaxy s Vibrant, so i thought it was the correct thing. But since i installed it i have alot of problems.
First of all, when i plug it into my USB the phone auto turns off. And it will not charge when the usb is in.
I have rom manager installed, but when i try to run a rom, i keep getting the error (status = bad ).
Also the phone wont recognise my SimCard so i cant stay with this firmweare anyways.
Click to expand...
Click to collapse
It looks like you flashed the actual "Vibrant" (T-Mobile US) type firmware onto your Bell i9000M phone... I dont know if you can flash back as the Download and Recovery modes for the actual Vibrant are different than the i-9000 model phones...
@Allgamer, can you be of any further help?
btw i really hate Samsung right now, why would you release a phone called a i-9000m Vibrant, then release a phone under the brand name vibrant
amnoric said:
btw i really hate Samsung right now, why would you release a phone called a i-9000m Vibrant, then release a phone under the brand name vibrant
Click to expand...
Click to collapse
I agree with you on this man. How confusing could they make it? I guess they did it to sort of distinguish our model of i9000M from the International version but couldnt they at least give a different name from the U.S. model?
They even look identical except for the fact that the U.S. Vibrant has 4 soft keys at the bottom where we have the 2 soft and 1 hard key...
Well now that my panic attack is over and my phone is back to normal after Flashing 2.2 on it ( FOR I-9000m even ).
I have another random question..... what is the best way to root 2.2.. since the whole point of the **** up was because i would not root it
amnoric said:
Well now that my panic attack is over and my phone is back to normal after Flashing 2.2 on it ( FOR I-9000m even ).
I have another random question..... what is the best way to root 2.2.. since the whole point of the **** up was because i would not root it
Click to expand...
Click to collapse
I recommend the app called z4root by RyanZA. You can find it on the Market. It is a one click root that requires no flashing of any kind.
You may have to start the app and if it seems to hang for a while just perform a reboot and run the app again and it will root within 30 seconds. Also be weary in the Market as someone has stolen the icon and everything from RyanZA and the "rip off" app is NOT complete. Make sure the one you download states it is from RyanZA...
So apparently the official 2.2 Froyo is rolling out. I haven't checked yet but I will when I get home. I have some newb questions.
I got my phone and haven't touched a thing to it. Just added lots of apps. No root. No lag fix. Nothing.
My question is, if I upgrade this officially via Kies:
1) Do I lose my contacts / stuff ?
2) Do I lose my apps ?
I heard people saying that once you upgrade to do a hard reset of the phone -- why ? What happens if you don't ?
With this in mind, how and what is the best way to back up all my apps ? I haven't rooted but i DO have Titanium Back up. Would Z4root work for i9000m ? can anyone confirm ?
Funkadelick said:
So apparently the official 2.2 Froyo is rolling out. I haven't checked yet but I will when I get home. I have some newb questions.
I got my phone and haven't touched a thing to it. Just added lots of apps. No root. No lag fix. Nothing.
My question is, if I upgrade this officially via Kies:
1) Do I lose my contacts / stuff ?
2) Do I lose my apps ?
I heard people saying that once you upgrade to do a hard reset of the phone -- why ? What happens if you don't ?
With this in mind, how and what is the best way to back up all my apps ? I haven't rooted but i DO have Titanium Back up. Would Z4root work for i9000m ? can anyone confirm ?
Click to expand...
Click to collapse
1) no
2) no
3) hard resets are only if you experience a ton of lag while operating the phone
4) z4 does not work on jk4
BlackDino said:
1) no
2) no
3) hard resets are only if you experience a ton of lag while operating the phone
4) z4 does not work on jk4
Click to expand...
Click to collapse
how do you root jk4 then ? 2.1 eclair on bell i9000m
1. Phone is currently rooted. Do I have to unroot it before applying the firmware upgrade from Kies?
2. Do I have to perform a factory reset before applying the firmware upgrade?
Why is this stupid update corrupting internal SD's left and right? Bell better get me a new phone! Cause this one is bricked(I think) it goes up til "S" logo and then nothing but blank screen. If I touch the button, they light up but still nothin on the screen.
I should have gotten a different phone to begin with, but too bad Canada doesn't have all the good phones US has like D2 DX HTC Evo etc. Going up to Bell tomorrow for an exchange.
rajesh26e4u said:
Why is this stupid update corrupting internal SD's left and right? Bell better get me a new phone! Cause this one is bricked(I think) it goes up til "S" logo and then nothing but blank screen. If I touch the button, they light up but still nothin on the screen.
I should have gotten a different phone to begin with, but too bad Canada doesn't have all the good phones US has like D2 DX HTC Evo etc. Going up to Bell tomorrow for an exchange.
Click to expand...
Click to collapse
A lot of people have been complaining that their SD cards have been screwed. Luckily mine went through without any problems and hasn't given me any trouble so far.
Froyo is insane tho, before the phone used to lag a bit, now the moment i touch it it opens. No need for lag fix in my opinion, everything works blazing fast as is.
One thing to watch out for is the WIFI. It was working normally at the beginning but after 3 hours it just disconnected for no apparent reason and has trouble connecting back.
Good luck
rajesh26e4u said:
Why is this stupid update corrupting internal SD's left and right? Bell better get me a new phone! Cause this one is bricked(I think) it goes up til "S" logo and then nothing but blank screen. If I touch the button, they light up but still nothin on the screen.
I should have gotten a different phone to begin with, but too bad Canada doesn't have all the good phones US has like D2 DX HTC Evo etc. Going up to Bell tomorrow for an exchange.
Click to expand...
Click to collapse
Don't panic yet...
Try this
Volume UP/Power/Home(middle button)
Factory reset/Wipe
urfase said:
1. Phone is currently rooted. Do I have to unroot it before applying the firmware upgrade from Kies?
2. Do I have to perform a factory reset before applying the firmware upgrade?
Click to expand...
Click to collapse
1. NO
2. Good idea to factory reset before and after. Can't hurt and any noncompatible
programs and data will be gone.
Videonut said:
1. NO
2. Good idea to factory reset before and after. Can't hurt and any noncompatible
programs and data will be gone.
Click to expand...
Click to collapse
1) but will it erase root upon upgrading?
bimmerboii said:
1) but will it erase root upon upgrading?
Click to expand...
Click to collapse
Yep, but for optimised result, this is a must do!
You can probably have it work without doing a factory reset, but you can encounter weird behavior, bugs and stuff!
Anyway, you might end up doing it anyway to solve the firts boot issue
I'm one of the users who upgraded to Bell Froyo (from stock FW with root and lagfix - undid the lagfix before upgrading) and then encountered the broken internal SD card issue. I ran Volume UP/Power/Home(middle button) to reformat everything and it is up again. Inside the OS, I ran the internal factory reset again. So far so good. *crossing fingers*
I updated mine last night. However I've had major problems since. Initially it would just freeze up randomly and require removing the battery to get it back up and running.
Today I decide to reset it to defaults which seemed to go fine, although shortly after getting it all setup again, some Samsung app of sorts came up with an error and had to be forcefully closed. Then I was left with a black screen and only the notification bar.
Powered off the phone and went to turn it back on, and now it just loops through the Samsung GT i9000 screen (white writing). Not even the colourful S logo comes up.
I'm able to get it into Download Mode but not Recovery Mode. I'll have to do some reading about this Odin stuff tonight. Hopefully I can revive it, otherwise I guess I'll had to send it in for repairs. No idea if Virgin Mobile repairs will go through Bell or if I take it to them directly.
This is my first Android phone and I've only had it for just over a week. I thought I was making a good decision, but now I see it has quite a defect with the internal SD card failing.
Slow after upgrade
I upgrade my phone last night ( as per bell and Samsung) It is now slower than before. Quadrant Standard has it under 900.
Any ideas how to fix it?
bimmerboii said:
1) but will it erase root upon upgrading?
Click to expand...
Click to collapse
Just use SuperOneClick after you upgrade to Froyo, I've tested and have root on JK4
http://forum.xda-developers.com/showthread.php?t=803682
I have an unlocked phone from Bell that I already upgraded to the international (or European?) JPP/JPO 2.2, what is the best way to downgrade or restore back to default firmware before using Kies to get the official update? Does factory reset restore stock firmware?
I upgraded to official Bell froyo last night ..thn rooted.But how can i Unlock now? i tried using SGS unlock app it says no unlock codes found?? Please help
God damn samsung and bell!
it seems like they're giving defected phones to their costumers!
I have the corrupted sd card too, took it to guarantee now it takes more than 1 month to fix this!
this is f-ing xmas for god's sake. i want my phone
Same problem here!
I do have 2 good samsung galaxy s vibrants from Bell, however when i got the second one i upgraded to Froyo and now i cant unlock it because i cant read the stupid file inside the phone so,
How can i go back to my previous JH2 baseband?
Or
How can i unlock JK4?
I did my unlock on the other Galaxy using the script you donwload from somewhere in this website and then connecting the phone via usb cable with debugging on and mounting sd but with froyo i dont even know where my USB settings went!!!
Thanks for your help, greatly appreciated.
ciudadbonita said:
I do have 2 good samsung galaxy s vibrants from Bell, however when i got the second one i upgraded to Froyo and now i cant unlock it because i cant read the stupid file inside the phone so,
How can i go back to my previous JH2 baseband?
Or
How can i unlock JK4?
I did my unlock on the other Galaxy using the script you donwload from somewhere in this website and then connecting the phone via usb cable with debugging on and mounting sd but with froyo i dont even know where my USB settings went!!!
Thanks for your help, greatly appreciated.
Click to expand...
Click to collapse
Have you found any solution yet?? I am thinkin to flash back orignal samsung firmware using Odin n then unlock..atleast i will be able to use the phone then
Videonut said:
Don't panic yet...
Try this
Volume UP/Power/Home(middle button)
Factory reset/Wipe
Click to expand...
Click to collapse
what if after this, it's still stuck after the s logo boot up?
does this mean i have a broken internal sd?
Hello
I had some trouble with a bricked SGS for about 3 weeks ago but got it on the run again with some flashing help.
Now i have this strange problem. If i turn it off or if it just goes black out, which it has begun to do after i flashed it, then it can't turn on, it just show the sun looking loading icon and then a empty battery icon and then turns off.
I can't load recovery mode with the combo, but i can make the download mode combo work.
But if i connect the phone with the charger/usb i recognize it and show that it charging up. Now it boot and shows the Galaxy I9000 model no. image.
Had tried flashing newer versions From XXJPO -> XXJPY -> XWJS3 and both with and without pre-partition and it still occur.
Now the question: Does any of you experienced people know this problem and can it be fixed somehow ?
Thank you in advance
First i would liik to charge phone for 24 hours and also check with another battery .
jje
JJEgan said:
First i would liik to charge phone for 24 hours and also check with another battery .
jje
Click to expand...
Click to collapse
The battery don't seem to be defected. Once the phone is booted with a cable connected, it goes without problems. It just will not boot without a charging signal.
Bump - Still actual
Try using Block 2 Odin method here to go back first to Eclair and if that works test phone then upgrade to Froyo .
jje
JJEgan said:
Try using Block 2 Odin method here to go back first to Eclair and if that works test phone then upgrade to Froyo .
jje
Click to expand...
Click to collapse
That happened to me a while back and I couldn't find a fix for it. Ended up doing the above and it resolved it.
Z3icon said:
Hello
I had some trouble with a bricked SGS for about 3 weeks ago but got it on the run again with some flashing help.
Now i have this strange problem. If i turn it off or if it just goes black out, which it has begun to do after i flashed it, then it can't turn on, it just show the sun looking loading icon and then a empty battery icon and then turns off.
I can't load recovery mode with the combo, but i can make the download mode combo work.
But if i connect the phone with the charger/usb i recognize it and show that it charging up. Now it boot and shows the Galaxy I9000 model no. image.
Had tried flashing newer versions From XXJPO -> XXJPY -> XWJS3 and both with and without pre-partition and it still occur.
Now the question: Does any of you experienced people know this problem and can it be fixed somehow ?
Thank you in advance
Click to expand...
Click to collapse
i agree wiv the suggetions frnds given.galaxy is hard to brick.i did all sort of unusual things an even uptodate lol.don worri m8 jus flash to older stock and hard reset.check the connectivity pins,to b clean even the battri pins.somtimes its best u format ur eternal xd on pc an format.and giving another hard rest makes things better.i had once formated my int sd on pc and the phone had emptied,then i flashed and things worked fine.personally sticking to stock rom is better if u dont wan troubles,cause every custom rom has som drawback an needs a lil knownledge to tweak it up.check kies if ur on it,i recomend download the recovery driver in it.hope u get some help.cheeeerzzzz
Same here...
Hello everyone,
I too have the same issue as stated in the first post.
I even had issue sometimes that when boot up.
The USB notification icon wouldnt turn off even if i wasn't connected.
Some threads suggested that I clean the USB port, which i did and nothing changed, even if it looked a little bit dirty in there (Hard to say since it is really small).
Now the USB port looks just as new but same issue: I cant power on the unit witout having it connected with a power cord.
Also, when offline in download mode, Odin detect the unit and I can flash my device (Which I did yesterday by flashing UGJH2 re-partition and UGJL2 not re-partition) but when boot up, I can't make it to sync up with the computer. No sync possible (Also now I'm not rooted anymore).
The unit is under warranty but since it is unlocked with a tool that needed rooting to lock back, abviously I would need to be rooted again but to do it, I need to be able to sync it with my PC (No cant do here).
I have some engineer at work that offered me to check it out for me, they think it is related with the USB port, but I'm worried about the warranty seal. I found how to disasemble it but does anybody knows where it could be located on the I9000M from bell (Vibrant)? Does it have one?
Anybody have any better suggestion or a second opinion, please?
Its my 3rd Galaxy S from Bell and Samsung is now the last company I would think when buying a new mobile.
EDIT: Did the Block 2 Method and now it doesnt even want to boot at all (Did the JPY_JPY_JPY.tar part), now it shows the loading sign even faster and the battery doesnt even show it self at all.
Hello again people!
Got my friend engineers to open the phone and they didnt find anything that would cause my issue (Also no warranty label...).
Does anybody knows how to root a Galaxy S with Froyo without a PC?
I want to return my phone to Bell Canada under warranty but my phone is unlocked and I want to lock it back before sending it back and I need to be rooted to do so...
Thanks for your help!
I got the same problem here. Could someone tell me more on this. What is this Block 2 ODIN method?
this problem can be caused by water or sweat that got inside the case of your sgs.
the biggest hole in the case is micro-usb port) i think condensation accumulated there and locked some contacts.
try to disassemble the phone and carefully clean and dry it.
this helped me.
It's obvious that these Bell i9000m GXS phones are messed up with their faulty SD cards.
It's been reported the Nexus S will be coming to Bell (and later on the SGS2)
Should I try and sell my phone via craigslist / Kijiji when the Nexus S comes out ? or should I wait for the SGS 2 ?
What are you guys thinking?
These faulty SD cards are a joke of a phone, only slightly less embarrassing than the support/software
I've been trying to upgrade by 2.1 eclair to 2.2 froyo for over a month now -- tried everything and no luck. This is a f*cking joke since my old palm pre could even do OTA upgrades
Funkadelick said:
I've been trying to upgrade by 2.1 eclair to 2.2 froyo for over a month now -- tried everything and no luck.
Click to expand...
Click to collapse
Thousands of people on this forum flash to a different ROM everyday. Explain how you have tried to upgrade, maybe we can see if you are doing something wrong.
As for getting a different phone, the only differences in specs between the SGS and the Nexus S is the lack of a SD card on the Nexus S and it will have Gingerbread. The Nexus S works on HSDPA 1700, the SGS on HSDPA 1900
http://www.gsmarena.com/compare.php3?idPhone1=3620&idPhone2=3115
Ian
w98seeng said:
Thousands of people on this forum flash to a different ROM everyday. Explain how you have tried to upgrade, maybe we can see if you are doing something wrong.
As for getting a different phone, the only differences in specs between the SGS and the Nexus S is the lack of a SD card on the Nexus S and it will have Gingerbread. The Nexus S works on HSDPA 1700, the SGS on HSDPA 1900
http://www.gsmarena.com/compare.php3?idPhone1=3620&idPhone2=3115
Ian
Click to expand...
Click to collapse
Well I have been following Kies "fixes" for a month and a half now, and trust me, there isn't anything I haven't read. Nothing works. I've done the 16 character deletion fix, nothing. I've uninstalled Kies and the drivers and done registry hacks, etc. for days and days. Rebooted about 500 times. Reinstalled software. Nothing.
It says everything is connected and working fine - but when I connect my phone to the USB cable KIES (2.0) just says "connecting" with an never ending loop.
I think it's a crying shame this software sucks so bad.
As stated, I may need to resort to using ODIN and flashing, which I don't want to do (because of warrenty issues)
What's the best ROM to use? I want something fast and stable. Are people flashing Gingerbread ROMS ?
Atrix
I agree that Kies is an awful program. There's just too many tweaks that you have to do just to attempt to get your phone connected.
I'd suggest getting the Motorola Atrix 4G. It's already announced on Bell and it's by far the most interesting phone yet.
I do not use Kies V2, I hate it. It also does not try to update my phone, it gets to the update window but then it freezes. I still use Version 1.5.3.10103_102 of Kies. I also use the registry patcher with 1.5.3. it works great.
Here is Kies and the Registry Patcher I use.
What version of Android are you running at the moment?
Funkadelick said:
Well I have been following Kies "fixes" for a month and a half now, and trust me, there isn't anything I haven't read. Nothing works. I've done the 16 character deletion fix, nothing. I've uninstalled Kies and the drivers and done registry hacks, etc. for days and days. Rebooted about 500 times. Reinstalled software. Nothing.
It says everything is connected and working fine - but when I connect my phone to the USB cable KIES (2.0) just says "connecting" with an never ending loop.
I think it's a crying shame this software sucks so bad.
As stated, I may need to resort to using ODIN and flashing, which I don't want to do (because of warrenty issues)
What's the best ROM to use? I want something fast and stable. Are people flashing Gingerbread ROMS ?
Click to expand...
Click to collapse
I wouldn't worry about "waranty" issues personally just do your research before flashing is all.
Samsung S2 S3 S4 no thanks the first samsung and no more
w98seeng said:
Thousands of people on this forum flash to a different ROM everyday. Explain how you have tried to upgrade, maybe we can see if you are doing something wrong.
As for getting a different phone, the only differences in specs between the SGS and the Nexus S is the lack of a SD card on the Nexus S and it will have Gingerbread. The Nexus S works on HSDPA 1700, the SGS on HSDPA 1900
http://www.gsmarena.com/compare.php3?idPhone1=3620&idPhone2=3115
Ian
Click to expand...
Click to collapse
juinny said:
I agree that Kies is an awful program. There's just too many tweaks that you have to do just to attempt to get your phone connected.
I'd suggest getting the Motorola Atrix 4G. It's already announced on Bell and it's by far the most interesting phone yet.
Click to expand...
Click to collapse
But I heard the Atrix is coming with a bootloader locked and you can't mess around with it etc.
w98seeng said:
I do not use Kies V2, I hate it. It also does not try to update my phone, it gets to the update window but then it freezes. I still use Version 1.5.3.10103_102 of Kies. I also use the registry patcher with 1.5.3. it works great.
Here is Kies and the Registry Patcher I use.
What version of Android are you running at the moment?
Click to expand...
Click to collapse
Stock vanilla 2.1, no root, no OCLF, never touched it
I9000UGJH2
Funkadelick said:
But I heard the Atrix is coming with a bootloader locked and you can't mess around with it etc.
Click to expand...
Click to collapse
As per Moto they might change that
http://androidcommunity.com/motorol...eir-statements-on-bootloader-policy-20110120/
Funkadelick said:
Stock vanilla 2.1, no root, no OCLF, never touched it
I9000UGJH2
Click to expand...
Click to collapse
Install the Kies I uploaded and plug in your phone. If you still 2.1 on your phone, it should upgrade it to JL2. If you are still having trouble, download this JL2 here. This is the stock JL2 ROM
Use Odin to flash it, it's super easy.
Uncompress the JL2 file you downloaded
In Odin, click on PDA and choose the uncompressed JL2 file.
Nothing else gets ticked in Odin.
Plug in your phone and when Odin recognizes the phone click on start.
I have noticed that sometimes there is a fail on the first attempt, but I close Odin, unplug the phone, restart Odin, plug the phone back in and try again and it always works on the second attempt.
Ian
w98seeng said:
Install the Kies I uploaded and plug in your phone. If you still 2.1 on your phone, it should upgrade it to JL2. If you are still having trouble, download this JL2 here. This is the stock JL2 ROM
Use Odin to flash it, it's super easy.
Uncompress the JL2 file you downloaded
In Odin, click on PDA and choose the uncompressed JL2 file.
Nothing else gets ticked in Odin.
Plug in your phone and when Odin recognizes the phone click on start.
I have noticed that sometimes there is a fail on the first attempt, but I close Odin, unplug the phone, restart Odin, plug the phone back in and try again and it always works on the second attempt.
Ian
Click to expand...
Click to collapse
When he says the uncompressed file hes talking about the JL2 Tar file so there's no confusion and when he says plug in your phone and when it recognizes your phone click start your phone has to be in Download Mode. To get into download mode turn the phone off then press and hold Vol Down,Home and power.
Nexus S is a big disappointment
definitely not recommended if you are coming from a SGS
might have better luck wiht SGS v2.0 if they ever release it
Funkadelick said:
It's obvious that these Bell i9000m GXS phones are messed up with their faulty SD cards.
It's been reported the Nexus S will be coming to Bell (and later on the SGS2)
Should I try and sell my phone via craigslist / Kijiji when the Nexus S comes out ? or should I wait for the SGS 2 ?
What are you guys thinking?
These faulty SD cards are a joke of a phone, only slightly less embarrassing than the support/software
I've been trying to upgrade by 2.1 eclair to 2.2 froyo for over a month now -- tried everything and no luck. This is a f*cking joke since my old palm pre could even do OTA upgrades
Click to expand...
Click to collapse
Personally I'm really happy with my I9000m. I did fall victim of the sd card failure but when this phone works it's awesome, Im not running stock roms though. So far I only had minor problems with my replacement.
Its nice and snappy very little lag with no lag fix 150+ apps and with super curio's latest voodoo sound it's an amazing mp3 player.
I just like to point out as well that my i9000 plays flash 10x better then my ps3. I wish it had hd out though that just be amazing. As I watched quite a few movies using rogers ondemand online and the ability to stream the movies would be awesome although they are wathable on this screen . Oh yea and my 2 year daughter loves it as well . , load up some toopy and Binoo for those long car rides
Sent from my I9000m using XDA's app.
Samdroid_G_S said:
Personally I'm really happy with my I9000m. I did fall victim of the sd card failure but when this phone works it's awesome, Im not running stock roms though. So far I only had minor problems with my replacement.
Its nice and snappy very little lag with no lag fix 150+ apps and with super curio's latest voodoo sound it's an amazing mp3 player.
I just like to point out as well that my i9000 plays flash 10x better then my ps3. I wish it had hd out though that just be amazing. As I watched quite a few movies using rogers ondemand online and the ability to stream the movies would be awesome although they are wathable on this screen . Oh yea and my 2 year daughter loves it as well . , load up some toopy and Binoo for those long car rides
Sent from my I9000m using XDA's app.
Click to expand...
Click to collapse
curio's latest voodoo sound? explain please
Samdroid_G_S said:
When he says the uncompressed file hes talking about the JL2 Tar file so there's no confusion and when he says plug in your phone and when it recognizes your phone click start your phone has to be in Download Mode. To get into download mode turn the phone off then press and hold Vol Down,Home and power.
Click to expand...
Click to collapse
Thanks, I can't believe I forgot the download mode part.
Ian
You complain about the SD cards but it sounds like your real problem is Kies. Yes Kies is junk, couldn't get it to recognize the phone at all on my laptop but my desktop was randomly fine.
The SD card issue actually seems mostly resolved. Not sure if it is the new JL2 bootloader or the new hardware (new phone or new PBA like I got) but I'm not seeing many reports of SD cards dying lately.
As far as Kies I'm not letting it anywhere near my phone now. Odin'd a new kernel and now flashing ROMs is dead easy just put them on the SD card and install in recovery mode.
Yes the SD card issue was disappointing, I was without my phone for 4 weeks, but these things happen the important thing is that we get a proper fix and it seems we did. Otherwise I'm very happy with the phone, JL2 stock was good and custom ROMs are even better.
I don't see Nexus S as a good choice for SGS users even if you really hate the SGS. Not really an upgrade while the lack of microSD and video recording are downgrades. The S2 looks awesome, we'll see how the moddability and reliability are. Myself I think I will wait for the next Google-branded phone which should deliver both next-gen hardware and no-holds-barred customization.
Funkadelick said:
curio's latest voodoo sound? explain please
Click to expand...
Click to collapse
Yes Voodoo Sound Voodoo App (from the market) + Power Amp = Amazing sound quality.
Check it out here.
http://forum.xda-developers.com/showthread.php?t=806195
w98seeng said:
I do not use Kies V2, I hate it. It also does not try to update my phone, it gets to the update window but then it freezes. I still use Version 1.5.3.10103_102 of Kies. I also use the registry patcher with 1.5.3. it works great.
Here is Kies and the Registry Patcher I use.
What version of Android are you running at the moment?
Click to expand...
Click to collapse
I had flashed to a version of 2.2 but then flashed back to JH2 after my phone acting strange. (Already had it replaced once for corrupt SD). I had thought I had official Bell (BMC) version of firmware on the phone but Kies was still recognizing it as (KOR) and would not upgrade me to JL2. Anyway, thank's to your Reg Patcher I am currently getting JL2.
Many thanks
i sent my second 9000m back for repair (they replace motherboard) but on stock jl2 it was terribly laggy.. gallery would not open fc's and other apps would fc'''... and when they put in new motherboard they forgot to reflash the imei.. ..
hopefully can get a replacement.. to another phone.. my i9000t on the otherhand has been steller with no issues whatsoever..