Almost bricked my Galaxy SL while upgradsing to Jellybean

[paosuarez]

---

UPDATE! JUNE 13 2012

Sorry for the inactive-ness... I SUCCESSFULLY (salamatsalordjesuschrist) updated my phone to Jelllybean TTwTT So effing proud. Mods you can close and I apologize for the late updates and whatnot.


I have a Samsung Galaxy S1, but according to the model number (GT - I9003) it's a Samsung Galaxy SL (weird but whatevs)

Anyway, I'm currently on 2.3.4 build and my older brother told me that pwede siya ma upgrade to 4.0 or Jelly bean. I honestly dont like to upgrade kay I like it as is, but when I checked the UI sa Jellybean (and like a girl) na in-love so a UI

Being impatient and cheap, I decided to follow the advice of several seniors is XDA forums in upgrading to Jellybean.


Here's the part that makes you say WTF.

While updating it, the video tutorial said it might take a few minutes to update so I left the computer for a bio break and when I came back, my othero dler brother used the computer and na stop siya ug update.

After thirty-minute litany of nag-bwiset, I reformatted my phone and tried again. Now instead o updating, it comes up with an error message.


As I type this, I actually want to bring it to a shop to have it updated there na lang. But before I do that, is there anyway I can fix this hiccup before ipadala nako a shop? Any helpful suggetsions would be great.

PS> I was able to successfully root it now and before. It's just the updating na dili mu gana

[ongkal]

im not sure with samsung phones ha pero for nvidia chipset phones like lg p990, motorola atrix, etc, pwede ka muflash sa dead phone using the nvflash utility. you can flash a full OS, or a recovery image bisan patay na imong phone thats why those phone s are called software-unbrickable. i dont know if naay equivalent ana sa samsung galaxy s, im not familiar but if there is, sayon ra na marecover.

[ongkal]

ay wait. mugana pa ba imo phone normally? di lang siya kaupdate?

[janhenz1]

im guessing nga SuperNexus Rom?

not familiar w/ S1, pero if you can still access Download Mode,
dali rana.

[Agili]

^ yup, just get into download mode then flash a firmware using odin.

alternately, I can try to fix that for you for 300 contact 0933-325-3242.

[jeff_bonz59]

no need to fret.. i'd say.. get the latest version of ODIN.. download the custom ROM firmware in xda (for your specific device/model/make) tick usb debugging on your phone's setting then go to download mode and plug your phone into one of the usb ports of your laptop/pc. Initiate ODIN and go to the directory where you've saved your custom ROM (usually its a zip file extension) in your laptop/pc and click START.

wait until ODIN would finish... updating usually takes 20-40 mins.. depending on your laptop/PC performance.

Once its finish.. it will tell you to unplug your fone from the usb cable... phone would reboot.. and once that.. it'll go to the normal startup setup where you need to configure everything... eg.. language.. signin to google account and etc...

P.S. before you do all of these.. make sure you have made the necessary backups already in your device.

Cheers!

[Agili]

^ uhm, usually it'll be a .tar file divided into 3 parts, pda(code), phone(modem), and csc(csc). place each file in their respective slots and start.

[jeff_bonz59]

yeah hehe my bad.. its been ages i've cooked and flashed ROMS.. hehe its a tar file and the rest.. well its on the respective buttons in ODIN itself...


Cheers!

[Agili]

cheers!
goodluck TS, hope you fix it soon,

[janhenz1]

wala naman ni-update si TS,

hope fix na