News + Articles
Sign In
Create Account
3
Please read this new note before proceeding to read the rest of the post, as the situation has changed, and I would hate for someone to have to read through the whole topic just to get the story:
So, basically, I tried flashing the firmware from a desktop computer, usb 2, using UMDL. It failed, as did every other attempt I made from that same computer, weather in Windows xp or 7 (which was REALLY strange), even with a special driver that someone pointed out in the posts had no effect. Basically, at that point it wasn't "bricked" yet, seeing as it would still accept firmware, but it would fail part of the way through at flashing. I was going to visit someone else the next day (possibly) who had a computer that I know had USB 2 plugs on the front, so I would just load up the driver, plug in the machine, and be all set. Only, this was not how it went. My curiosity got the best of me, and I saw an old hp pavilion zt1250 laptop sitting in the corner, and I said "well hey, maybe the computer's usb plugs are messed up, maybe if I tried a different computer..." (out loud). But that was about to become a HUGE mistake. I loaded up the driver on the laptop, and put UMDL and the stock i910 cf03 rom on a USB drive, and proceeded to connect the unit. Hit power, the system recognized it, found the drivers I had installed, and started flashing. It went at a slow, but steady pace, and on its first try went all the way to the end. The little blue highlight in UMDL indicated that it was done and safe to unplug the player, so I reset it and unplugged it and... here we are - bricked. How could a successful flash brick a music player just like that? My explanation is that it had something to do with the fact I was using USB 1 instead of USB 2. If I had waited just that extra day, I would have most likely not been in this situation. Later, I did read that there were some people who had trouble flashing with usb 1 also, and after looking up the symptoms (now unofficially known as the Omni Red light of Death, I have discovered that the only means of repair now to fix a damaged bootloader is by finding a JTAG adapter, or a motherboard from another i910 Omnia. For more details on my findings in JTAG and such, please go to the third page of this topic, at the top. That is our current situation.
Below is my original post from before all this, here for archival purposes:
Hello everyone here on the forum, this is 2 Bunny.
I thought I might finally "give in" (LOL!) and register here because there seem to be a lot of handy download tools and because I have a very important question for the community: Why am I having such difficulty "unbricking" my Samsung Omnia i910 (Verizon Branded)?
Obviously, I will share some background first: So, I bought the machine used with nothing but a battery. No stylus, no charger, no headphones. So, up until today (coincidentally, my birthday) the thing was completely useless. I knew long before that that it would be a significant advantage to upgrade the firmware to one of the famous "hacked" versions. Well, I flashed the wrong one, and it got stuck a little bit through the upgrade. So, I popped the battery off, and back on again, and plugged it back in once again to see the little "recharging" icon. If you turn it on not plugged in, the Samsung omnia logo and progress bar appear, and the progress bar moves twice, and then freezes until the battery pack is removed and reinserted again. The good news is that it will still take a firmware upgrade, but it does the same stupid thing, every single time: Freezes part of the way through. And the interesting thing is, no matter if you try to flash the same rom, or a different one, it freezes at a completely random interval, but almost always at less than forty percent. I'm using the UMDL for Omnia version 2.3, and have got the stock image file for the cf03 update that I am currently working on so that I can get that, and then go from there. It always freezes at a random interval during the "writing image" stage. I even downloaded a different cf03 stock update from this thread at samsung-omnia.org just to see if it was the rom I was using, but still the same results, despite a slightly different file size.
So, what do I have to flash to get it to start completely over? Surely I could put something on it to make it run seeing as it will always get through part of its firmware flashes all right!
Thanks in advance already!
- 2 Bunny
So, basically, I tried flashing the firmware from a desktop computer, usb 2, using UMDL. It failed, as did every other attempt I made from that same computer, weather in Windows xp or 7 (which was REALLY strange), even with a special driver that someone pointed out in the posts had no effect. Basically, at that point it wasn't "bricked" yet, seeing as it would still accept firmware, but it would fail part of the way through at flashing. I was going to visit someone else the next day (possibly) who had a computer that I know had USB 2 plugs on the front, so I would just load up the driver, plug in the machine, and be all set. Only, this was not how it went. My curiosity got the best of me, and I saw an old hp pavilion zt1250 laptop sitting in the corner, and I said "well hey, maybe the computer's usb plugs are messed up, maybe if I tried a different computer..." (out loud). But that was about to become a HUGE mistake. I loaded up the driver on the laptop, and put UMDL and the stock i910 cf03 rom on a USB drive, and proceeded to connect the unit. Hit power, the system recognized it, found the drivers I had installed, and started flashing. It went at a slow, but steady pace, and on its first try went all the way to the end. The little blue highlight in UMDL indicated that it was done and safe to unplug the player, so I reset it and unplugged it and... here we are - bricked. How could a successful flash brick a music player just like that? My explanation is that it had something to do with the fact I was using USB 1 instead of USB 2. If I had waited just that extra day, I would have most likely not been in this situation. Later, I did read that there were some people who had trouble flashing with usb 1 also, and after looking up the symptoms (now unofficially known as the Omni Red light of Death, I have discovered that the only means of repair now to fix a damaged bootloader is by finding a JTAG adapter, or a motherboard from another i910 Omnia. For more details on my findings in JTAG and such, please go to the third page of this topic, at the top. That is our current situation.
Below is my original post from before all this, here for archival purposes:
Hello everyone here on the forum, this is 2 Bunny.
I thought I might finally "give in" (LOL!) and register here because there seem to be a lot of handy download tools and because I have a very important question for the community: Why am I having such difficulty "unbricking" my Samsung Omnia i910 (Verizon Branded)?
Obviously, I will share some background first: So, I bought the machine used with nothing but a battery. No stylus, no charger, no headphones. So, up until today (coincidentally, my birthday) the thing was completely useless. I knew long before that that it would be a significant advantage to upgrade the firmware to one of the famous "hacked" versions. Well, I flashed the wrong one, and it got stuck a little bit through the upgrade. So, I popped the battery off, and back on again, and plugged it back in once again to see the little "recharging" icon. If you turn it on not plugged in, the Samsung omnia logo and progress bar appear, and the progress bar moves twice, and then freezes until the battery pack is removed and reinserted again. The good news is that it will still take a firmware upgrade, but it does the same stupid thing, every single time: Freezes part of the way through. And the interesting thing is, no matter if you try to flash the same rom, or a different one, it freezes at a completely random interval, but almost always at less than forty percent. I'm using the UMDL for Omnia version 2.3, and have got the stock image file for the cf03 update that I am currently working on so that I can get that, and then go from there. It always freezes at a random interval during the "writing image" stage. I even downloaded a different cf03 stock update from this thread at samsung-omnia.org just to see if it was the rom I was using, but still the same results, despite a slightly different file size.
So, what do I have to flash to get it to start completely over? Surely I could put something on it to make it run seeing as it will always get through part of its firmware flashes all right!
Thanks in advance already!
- 2 Bunny
Edited by 2 Bunny, 16 March 2010 - 10:40 PM.
Back to top
