Samsung Galaxy S I9000

Forums › Android › Samsung Galaxy S I9000

1 | ... | 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | 254 | 255 | ... | 427

1376 posts

Uber Geek

Trusted

#428402 18-Jan-2011 12:44

Shrapnel: Success, booted up, now setting up. Will post reply soon about connectivity,
Edit: WOOO, it worked! Thanks everyone. Everything is connected! and FAST! I love you guys in non gay kinda way!:)

And how's the heart rate. I'm sure everyone's heart rate peaks a little while flashing, no matter how "old hat" you become ;-)

Nice job.

Samsung Galaxy S5 SM-G900I

defragger

268 posts

Ultimate Geek

#428417 18-Jan-2011 13:12

Congrats Shrapnel.

Imma try my first flash either tonight or tomorrow. Nervous but excited at the same time.

Neets

1376 posts

Uber Geek

Trusted

#428420 18-Jan-2011 13:15

@Damager: Did you see the Nexus S on sale on Geekzone? Weren't you interested?

Samsung Galaxy S5 SM-G900I

nofam

1094 posts

Uber Geek

#428424 18-Jan-2011 13:23

defragger: Congrats Shrapnel.

Imma try my first flash either tonight or tomorrow. Nervous but excited at the same time.

Another important point that is worth repeating again for 1st-time flashers:

If you're moving from a lagfixed ROM, it's VITAL that you undo the lagfix before flashing a new ROM.

Without going into the why's and wherefore's, essentially, the 'lagfix' usually involves converting the filesystems of the various partitions of the NAND (read:hard drive) from RFS to EXT4. This is all well and good, but the ROM you're about to flash gets VERY confused when it expects RFS and finds a filesystem it knows nothing about - it then can't really tell where one partition stop and another starts, and generally gets it's knickers in a knot in a big way.

The usual result is a soft-brick, where your phone will sit at the white Samsung boot screen. . . . .forever. I know all about this, as I managed to do this the first time I flashed, and ended up wiping my /efs directory, and losing my IMEI, which is rather serious (which is why rooting your phone and grabbing a copy of /efs is crucial).

So. . . .

1. Double/Triple check you've undone any lagfixes
2. Try to get Root and copy your /efs directory to your PC/USB stick/bank vault in Monaco
3. Make sure you can boot into recovery and download mode incase things go t*ts up

Neets

1376 posts

Uber Geek

Trusted

#428426 18-Jan-2011 13:40

nofam:

So. . . .

bank vault in Monaco

Damn! I thought I'd kept that quiet ;-)

Samsung Galaxy S5 SM-G900I

lofreq

334 posts

Ultimate Geek

#428428 18-Jan-2011 13:50

good point about disabling lagfixes, definitely something to pay attention to - i never used any lagfixes as the rebuilt roms were fast enough, but if you do dabble in it make sure to, um, un-dabble.

congrats shrapnel, easy as right. now u can do that sh1t all day. defragger youre up. get your i9000t's flashed and start posting your experiences with whatever build you decided to load, so i can bounce some ideas off ya's for the sake of getting the best out of our outcast telecom handsets! :)

Galaxy Note 3 SM-N9005, on Telecom 4G LTE. ROM: Stock Touchwiz, Android 4.3, XUDMJ6 MODEM: MJ4 Kernel: Stock (for now...:)

defragger

268 posts

Ultimate Geek

#428447 18-Jan-2011 14:34

nofam:
defragger: Congrats Shrapnel.

Imma try my first flash either tonight or tomorrow. Nervous but excited at the same time.

Another important point that is worth repeating again for 1st-time flashers:

If you're moving from a lagfixed ROM, it's VITAL that you undo the lagfix before flashing a new ROM.

Without going into the why's and wherefore's, essentially, the 'lagfix' usually involves converting the filesystems of the various partitions of the NAND (read:hard drive) from RFS to EXT4. This is all well and good, but the ROM you're about to flash gets VERY confused when it expects RFS and finds a filesystem it knows nothing about - it then can't really tell where one partition stop and another starts, and generally gets it's knickers in a knot in a big way.

The usual result is a soft-brick, where your phone will sit at the white Samsung boot screen. . . . .forever. I know all about this, as I managed to do this the first time I flashed, and ended up wiping my /efs directory, and losing my IMEI, which is rather serious (which is why rooting your phone and grabbing a copy of /efs is crucial).

So. . . .

1. Double/Triple check you've undone any lagfixes
2. Try to get Root and copy your /efs directory to your PC/USB stick/bank vault in Monaco
3. Make sure you can boot into recovery and download mode incase things go t*ts up

Cheers will do. I managed to soft-brick my phone when I got it by trying to apply a lag-fix to a temporary rooted phone. Bad idea haha but it all worked out since I recovered it back. Did a permanent root and lag-fixed it so all good. I usually remove the lag-fix when I wan't to sync it to Kies as it does not recognise the phone with it applied.

Very cautious to do anything now without reading up at least a novel on it.

GoodSync

GoodSync. Easily back up and sync your files with GoodSync. Simple and secure file backup and synchronisation software will ensure that your files are never lost (affiliate link).

nofam

1094 posts

Uber Geek

#428462 18-Jan-2011 15:22

. . . . . I usually remove the lag-fix when I wan't to sync it to Kies as it does not recognise the phone with it applied.

Hmmm I don't see how the two are related; Kies connectivity is driver-related - lagfixes are low-level filesystem conversions, so shouldn't affect this at all?

lokhor

2858 posts

Uber Geek

Trusted

#428464 18-Jan-2011 15:22

How much does a second hand SGS sell for these days? I'd really like to get a device that has better support and isn't made by Samsung.

All comments are my own opinion, and not that of my employer unless explicitly stated.

defragger

268 posts

Ultimate Geek

#428486 18-Jan-2011 15:52

nofam:
. . . . . I usually remove the lag-fix when I wan't to sync it to Kies as it does not recognise the phone with it applied.

Hmmm I don't see how the two are related; Kies connectivity is driver-related - lagfixes are low-level filesystem conversions, so shouldn't affect this at all?

My apologies I wasn't too clear. It recognises the phone, but not any files/data on it. I cannot access anything off it such as photos, contacts and messages or sync with Kies.

I'm assuming with the filesystem conversion run by the lag-fix, Kies cannot access the files in this new format. I could be wrong though.

However removing the lag-fix, I am able to 100% connect my phone to Kies, sync and access my data.

nofam

1094 posts

Uber Geek

#428502 18-Jan-2011 16:22

lokhor: How much does a second hand SGS sell for these days? I'd really like to get a device that has better support and isn't made by Samsung.

The problem is, what else do you go to? iPhone? Nexus S? Desire HD?

The Nexus S is the only real alternative, albeit an unproven one.
And to be honest, there's very little to fault with a proper implementation of Android (such as Doc's ROM!) on the SGS.

It is a shame though that the stock SGS is so crippled; I have a family member who runs a business, and she really needs a smartphone, but I can't bring myself to recommend the SGS even though she loves mine - it's just not good enough in vanilla form.

lokhor

2858 posts

Uber Geek

Trusted

#428503 18-Jan-2011 16:24

I was thinking the Motorola Atrix :D

All comments are my own opinion, and not that of my employer unless explicitly stated.

Shrapnel

260 posts

Ultimate Geek

#428504 18-Jan-2011 16:28

Things to note about the new firmware xxjpy is that straight away you can send txts and receive calls but I am needing to set APN's for data as I cannot connect without wifi, and don't expect your quadrant standard score to sky rocket, mine is about on par for 2.2 stock. Once in quite a while I did have a small lockup, but was more things loading than actually not being able to do anything.Could have been LP though. Also on first boot it asked me to type some stuff in as a "test" with swype, did so but the swype keypad wouldn't go away so I had to restart the phone and just ignored it then.

Galaxy S I9000T 8GB Kingston 8GB Class 4 Micro SD MIUI 2.3.5 V1.9.9 JL2 Modem

Shrapnel

260 posts

Ultimate Geek

#428507 18-Jan-2011 16:34

Neets:
Shrapnel: Success, booted up, now setting up. Will post reply soon about connectivity,
Edit: WOOO, it worked! Thanks everyone. Everything is connected! and FAST! I love you guys in non gay kinda way!:)

And how's the heart rate. I'm sure everyone's heart rate peaks a little while flashing, no matter how "old hat" you become ;-)

Nice job.

Well, I couldn't stand staring at Odin with its little green loading bar so I went for a bike ride, lol :D

Galaxy S I9000T 8GB Kingston 8GB Class 4 Micro SD MIUI 2.3.5 V1.9.9 JL2 Modem

lofreq

334 posts

Ultimate Geek

#428510 18-Jan-2011 16:41

Shrapnel: Things to note about the new firmware xxjpy is that straight away you can send txts and receive calls but I am needing to set APN's for data as I cannot connect without wifi, and don't expect your quadrant standard score to sky rocket, mine is about on par for 2.2 stock. Once in quite a while I did have a small lockup, but was more things loading than actually not being able to do anything.Could have been LP though. Also on first boot it asked me to type some stuff in as a "test" with swype, did so but the swype keypad wouldn't go away so I had to restart the phone and just ignored it then.

whats your reported quadrant score now? and what was it before?

Galaxy Note 3 SM-N9005, on Telecom 4G LTE. ROM: Stock Touchwiz, Android 4.3, XUDMJ6 MODEM: MJ4 Kernel: Stock (for now...:)

1 | ... | 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | 254 | 255 | ... | 427