Jump to content


Photo

i910 Bricked Omnia Observations

- - - - -

  • Please log in to reply
26 replies to this topic

#1
somedude

somedude

    Diehard

  • Members
  • PipPipPipPip
  • 326 posts
Fellows omnians, If you bricked your verizon omnia, like me, maybe we can help others from doing the same by getting to the root cause of what may have went wrong.

First, the machine that i attempted to flash was windows xp, (no service packs though, maybe that could be a reason?)

Second, i dont think my phone was charged enough. I had attempted the flash at around 7pm, and i had not charged my phone since around 7am.

Third, i notice a error message when i opened the UMDL file. I can no longer reproduce this, and i forgot what the error said. But once i clicked okay on the message box, the program opened fine.

Fourth, I had followed directions to a t, installed all drivers, unchecked usb connection, im not a nood at this...But yet i could never get past 48% when i tried to download EBOOT. Finally, out of frustration, i resetted my phone while the EBOOT was stuck at 48%, then, once my phone loaded up again, the EBOOT loaded to 100% very quickly, shut the phone off, and killed it.


I also had the SCH-i910 || (WM6.1)[DPRAM] as a platform.

  • 0

#2
krelvinaz

krelvinaz

    Weather Dude...

  • Members
  • PipPipPip
  • 219 posts
  • Gender:Male
  • Location:Mesa, AZ
  • Devices:Droid Incredible - Kindle Fire
Sounds like you might have used the wrong button and some other possible problem stuff.

I did a hard reset of the phone itself (not the memory storage) before starting this. Don't know if this is needed, but I did it to be safe.

Your phone should be fully charged, and turned OFF. Not just the display, press and hold the power button and turn it off.
Your computer should be doing nothing else.

When using the UMDL_OMNIA app, the only button you should be pressing is the "Unified Image File (*.img)" button.

The PDF calls this button the "EBOOT+PDA+PHONE(+CSC)" button, which is the same button, but it is labeled differently on the newer version of the UMDL app.

After you press the DETECT button, you need to plug in your (turned off omnia) and then turn it on.

You should not do anything else while this process takes place.

Don't browse, use other programs, that could interfere with the transfer.

It takes a while to do all of the updates.

Attached Files


Edited by krelvinaz, 10 April 2009 - 07:41 PM.

  • 0

#3
NewKlNGjames

NewKlNGjames

    Regular

  • Members
  • PipPip
  • 79 posts
  • Gender:Male
  • Location:bend oregon
pretty much the same thing happened to me. My phone was turned off all the way. the only buttons that I pushed were to load the image and detect. I forgot to mention in the other topic that it had locked up the first time. Got a checksum error while downloading the eboot file. nothing was installed and it booted up fine so I forgot about it. I am using a vista machine and had installed the usb driver and rebooted. I also disabled usb through windows mobile device center.

Edit:
A weird thing that I noticed was that the Backlit power button only turns red when on battery only. if I hook the phone up to a power cord or to the computer, then I get nothing at all.... weird.

Edited by NewKlNGjames, 10 April 2009 - 07:53 PM.

  • 0

#4
somedude

somedude

    Diehard

  • Members
  • PipPipPipPip
  • 326 posts

i would just do it in store...

did you guys happen to hard reset the phone?
Did you have any of the boxes checked?
How many times did you try to flash it?



I did not do a hard reset.

Whatever boxes that were checked by default were the ones that were checked. I did not check any boxes on my own.

I tried to flash at least 6 or 7 times.

  • 0

#5
NewKlNGjames

NewKlNGjames

    Regular

  • Members
  • PipPip
  • 79 posts
  • Gender:Male
  • Location:bend oregon

I would just do it in store...

did you guys happen to hard reset the phone?
Did you have any of the boxes checked?
How many times did you try to flash it?


I hard reset the phone a few days ago... only put on one app, so I didn't even think about it.
I did not check any of the boxes that weren't on the guide.
tried twice. second time it said that it was successful and bricked my phone.

  • 0

#6
dwallersv

dwallersv

    Addict

  • Members
  • PipPipPipPipPip
  • 901 posts
  • Devices:Omnia

Fellows omnians, If you bricked your verizon omnia, like me, maybe we can help others from doing the same by getting to the root cause of what may have went wrong.

First, the machine that i attempted to flash was windows xp, (no service packs though, maybe that could be a reason?)

Second, i dont think my phone was charged enough. I had attempted the flash at around 7pm, and i had not charged my phone since around 7am.

Third, i notice a error message when i opened the UMDL file. I can no longer reproduce this, and i forgot what the error said. But once i clicked okay on the message box, the program opened fine.



Whoah, don't remember you posting this in the other thread (not that you didn't, just don't remember seeing it).

This, to me, is a major stop sign. When I pressed the "unified image" button and then selected the image downloaded from MegaDownload, the program clearly did some sort of verification on the file and the parts therein, probably some checksums and other stuff, then was ready. No warning dialogs.

It's not completely batsh!t that a few people could have ended up with corrupt downloads. It happens, not because of anything nefarious, just imperfect technology.

  • 0

#7
Chugworth

Chugworth

    Regular

  • Members
  • PipPip
  • 131 posts
  • Devices:Samsung Omnia i910 (Verizon)
Does the MD5SUM of your image match the one below?

664555509f821556775dc6f9222f4502 *i910WM6.1.REV10.CC20.VZW.img

I suspect that either your image was corrupt, or something interfered with the USB ports during your upgrade. I also doubt that your Omnia is truly "bricked." Usually these devices always have some way to allow re-flashing if the image is corrupt.

When you send it to Verizon, they will re-flash it, clean it off, and then give it as a replacement to someone else.

  • 0

#8
avluis

avluis

    Newbie

  • Members
  • Pip
  • 49 posts
  • Devices:Samsung Omnia i910
Is anyone around at this time, maybe I can help you guys out if I can get some information about your phones.

  • 0

#9
bigdaddykane

bigdaddykane

    Regular

  • Members
  • PipPip
  • 111 posts
  • Location:DFW
  • Devices:i910
Hi My Name is Bigdaddykane and I too have bricked my most valuable possession.......but the new on will be in the mail Monday

  • 0

#10
somedude

somedude

    Diehard

  • Members
  • PipPipPipPip
  • 326 posts

Hi My Name is Bigdaddykane and I too have bricked my most valuable possession.......but the new on will be in the mail Monday



I thought a microphone was your most valuable profession? :excl:

Are you going to flash your replacement? I know i am, i dont care, if it bricks again, so be it.

  • 0

#11
DenaeNo9

DenaeNo9

    Newbie

  • Members
  • Pip
  • 2 posts
  • Devices:Omnia
I also got an error when starting the UDML program, but I continued on and it flashed correctly. I did DL the .img file a few times until I got a transfer rate higher than 500k, seems the higher the transfer rate the fewer corrupt files I get. I also thought it done a checksum when loading the .img file, but maybe not.

  • 0

#12
pylesw

pylesw

    Newbie

  • Members
  • Pip
  • 10 posts

Does the MD5SUM of your image match the one below?

664555509f821556775dc6f9222f4502 *i910WM6.1.REV10.CC20.VZW.img

I suspect that either your image was corrupt, or something interfered with the USB ports during your upgrade. I also doubt that your Omnia is truly "bricked." Usually these devices always have some way to allow re-flashing if the image is corrupt.

When you send it to Verizon, they will re-flash it, clean it off, and then give it as a replacement to someone else.


Having also bricked my phone, I am also leaning towards the belief that the USB ports were the issue. I have a lot of external devices connected via USB (drives, DVD-ROM, printer, etc) and the image file was on the external USB drive when I was flashing. It's possible that reading from the USB drive while writing out another USB port (connected to the phone) made the installation unstable. It's the only thing I can think of. I followed the directions to the letter. My PC is using Windows XP with all the latest service packs and hotfixes. ActiveSync was v4.5 with USB connections disabled. Samsung drivers were the correct version as stated in the documentation. Both the PC and the phone were booted/soft reset prior to install.

Beta code is supposed to be a bit buggy. Bricked phones would be commonplace if we were official alpha or beta testers for Verizon. Hopefully, Verizon will work out the kinks by the time the official version is released.

Contact customer support, tell them the phone won't start and they'll mail you a replacement. You'll need to mail back your original phone when the replacement arrives.

  • 0

#13
pylesw

pylesw

    Newbie

  • Members
  • Pip
  • 10 posts

I thought a microphone was your most valuable profession? :excl:

Are you going to flash your replacement? I know i am, i dont care, if it bricks again, so be it.



Rumor has it that the official Verizon release will be in May. Having flashed it correctly the first time, I need my phone and can live without GPS for another month. I'm not going to flash the replacement phone until Verizon releases the official version and then, I'm going to use another PC to flash it. Something caused it to fail the first time, and trying to flash it again exactly as i did before will likely cause the replacement to also get bricked.

  • 0

#14
somedude

somedude

    Diehard

  • Members
  • PipPipPipPip
  • 326 posts

Rumor has it that the official Verizon release will be in May. Having flashed it correctly the first time, I need my phone and can live without GPS for another month. I'm not going to flash the replacement phone until Verizon releases the official version and then, I'm going to use another PC to flash it. Something caused it to fail the first time, and trying to flash it again exactly as i did before will likely cause the replacement to also get bricked.



This time im going to try vista. I bricked using xp. I wouldve used vista, but i got a error while the program attempted to find my device. I think maybe because i didnt have activesync 4.5 installed? I didnt think that was necessary because vista uses WMDC.

  • 0

#15
dwallersv

dwallersv

    Addict

  • Members
  • PipPipPipPipPip
  • 901 posts
  • Devices:Omnia

This time im going to try vista. I bricked using xp. I wouldve used vista, but i got a error while the program attempted to find my device. I think maybe because i didnt have activesync 4.5 installed? I didnt think that was necessary because vista uses WMDC.



Not necessary. In fact, you can't install ActiveSync on Vista.

I did it from vista, exactly as the instructions said. You do have to have WMDC installed, and be sure the Connect via USB is unchecked.

  • 0

#16
Chugworth

Chugworth

    Regular

  • Members
  • PipPip
  • 131 posts
  • Devices:Samsung Omnia i910 (Verizon)

Not necessary. In fact, you can't install ActiveSync on Vista.

I did it from vista, exactly as the instructions said. You do have to have WMDC installed, and be sure the Connect via USB is unchecked.

Right. I flashed mine from Windows 7. I did not need to install any extra drivers. Just unchecked that "Connect via USB" setting, and it worked fine.

  • 0

#17
bigdaddykane

bigdaddykane

    Regular

  • Members
  • PipPip
  • 111 posts
  • Location:DFW
  • Devices:i910

I thought a microphone was your most valuable profession? :excl:

Are you going to flash your replacement? I know i am, i dont care, if it bricks again, so be it.


yes but i will wait a month or so.... i want to watch the forums more carefully and see if there is anything i can do differently... or maybe verizon will pull their head out of their ass and unlock it already

  • 0

#18
aceofrazgriz

aceofrazgriz

    Enthusiast

  • Members
  • PipPipPip
  • 250 posts
  • Gender:Male
  • Location:Liverpool, NY USA
  • Devices:HTC Incredible, Omnia i910
just wanna put it out there that a hard reset isnt needed before hand. i didn't do one, no problems.

  • 0

#19
DeepBlueEditor

DeepBlueEditor

    Enthusiast

  • Members
  • PipPipPip
  • 179 posts
  • Gender:Male
  • Location:Ohio
  • Devices:i910

just wanna put it out there that a hard reset isnt needed before hand. i didn't do one, no problems.


FYI, I didn't do a hard reset either. Active Sync back up and total SPB backup but no hard reset.

S

  • 0

#20
somedude

somedude

    Diehard

  • Members
  • PipPipPipPip
  • 326 posts
hmmmm... You know what, the computer that i flashed on only had USB 1.1. I thinking could that have been a possible reason?

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users