Database Info

Use caution flashing your i920 from Verizon using the samsung update

I have read a few articles/post about flashing samsungs new udate from their website for the i920. I think the only thing the update does is patch the radio(qualcomm) for people who have been getting dropped calls or not receiving calls from time to time. After reading about some phones being bricked during the update, I decided to go ahead and try it myself as i have been having some minor issues with not receiving some calls.
Sure enough, during the update process the upgrade froze while at 31% during the update. I let it set for about 30 minutes and nothing ever happened so I had no choice but to unplug the usb cable and try to do a hard reset. My phone was totally bricked and I had to get a replacement today. I even tried flashing a custom rom to try and recover it and no luck.
It turns out that the upgrade provided by samsung is not an official one approved by verizon according to the VZW tech in the store. When I took my phone in I told them that it had just froze over night while I was charging it and that's how it was when I woke up in the morning, becuase I did not know if they were going to try and screw me over or not.
So I highly recommend that you stay away from this update if you can. IMHO it is not worth the trouble. Just wait for verizon to release an update.
I am sure this is posted else where but I wanted to have this in the CDMA section so that other users could easily see it, and they do not have to go through the trouble I did today.

I had no problems flashing the update. However, I also had no trouble with dropped calls BEFORE flashing the update, but started having dropped calls after the update.
So unless you are already having issues which need a fix, I would have to agree with das, and say wait. There is the bricking risk, plus it may cause more issues than it solves.

samsung has temporarily pulled the update from their site. Maybe they are fixing it so it does not screw up your phone...LOL..I hope so becuase usually when my wife calls me she has to do it twice as the call is dropped before I can answer it or my phone some times does not ring at all. It's not a constant problem but it is annoying.

Agreed on issues w/ ck24.
The update damaged my first i920 during flashing. Used Vista prem 32-bit following Samsung's official PDF and no SD card in unit. Doing some searching on the net shows that even if you follow the detailed instructions from Samsung's PDF, it may stick the phone @ 31%,. While not technically bricked, you'll have to use Octans (not mini) and Shemmy's help on Modaco, to get it back to OEM ROM. This happened to my first Omnia II (i920), VZW promptly gave me a replacement by just telling them the unit stopped working (which it did, after getting stuck @ 31%).
I originally flashed the first unit due to that unit not sending texts if a user leaves my local VZW cell tower (say like if they are in another state or out several cities away). The update fixes issues w/ the Qualcomm radio (secondary PDF stated this on Samsung's site, before they took it down). VZW's techs are completely unaware of the issue apparently, as they show/feign ignorance when asked about the update and the issues w/ the i920. This is unnacceptable on Samsung's part for not having better quality assurance before releasing it, and on Verizon's part for not having informed techs. The failure rate for the Samsung update is so bad, that as stated earlier, they temporarily removed the update from their site, do a search for the i920 on their site and scroll down to "software" at the bottom, then on "Install Guide, Others" and you'll see it's "temporarily unavailable". I'd wait till it's posted on VZW's official site for the phone @ supportdotvzwdotcom/clc search for "Omnia II." Just like they did w/ the i910.

I have successfully used Wozzer's Stock ROM to flash back to the original ROM via OCTANS. Found on the Modaco site.
Link to Wozzer's repackaged stock ROM 21863 (no changes made):
http://www.4shared.com/file/206401811/dae1c8b0/FlashRom.html

Robtao said:
I have successfully used Wozzer's Stock ROM to flash back to the original ROM via OCTANS. Found on the Modaco site.
Click to expand...
Click to collapse
Good job man, this is exactly to what I was referring to. I'm unable to post links until the noob lock is off, but I was referring to a specific post on Modaco under the i8000/i920 section. In it, Wozzer had done all the hard work w/ the stock ROM, and Shemmy successfully tested it to revert an update damaged i920 back to stock w/ Wozzer's ROM. I too can attest to successfully using Octans (not the mini one) to bring the phone back w/ this ROM. As long as the phone turns on (even to that "connect to PC" error screen), it'll work.
Getting the radio properly fixed however, that's another story. Will still wait for VZW to post the official Samsung (fixed) update on their i920 support section. Hopefully then I can get my Qualcomm radio working fine on this (my 3rd, and not by my hand) Omnia II.

[Q] Galaxy Rugby Pro LTE not turning on after custom ROM install failed

Hi all,
I bought a Samsung Galaxy Rugby Pro LTE SGH-i547C (the Canadian version, with Telus) about a month ago, but now it won't turn on (although I can get into Download mode).
Full story: Yesterday I decided to root it (after unlocking it through Telus), and today I wanted to install the Liquid Smooth ROM, as it looked pretty sweet, but that didn't go as planned. After following the steps the first time, nothing happened to the phone's interface, so I did it a second time. This time, when it rebooted at the end of the installation, It got past the first two screens (name of model, and just "Samsung"), then it turned off.
What I've tried so far: First I tried applying the stock images (about 10 Mb, from http://forum.xda-developers.com/showthread.php?p=34463311#post34463311) through ODIN, but that made no difference, except that in one of the boot modes, instead of the Clockwork interface I, get the default interface (the background having an Android alien on its back, and a red triangle with an exclamation point above it). In these interfaces, I also wiped pretty much all that I could wipe, but to no avail.
Next I tried applying two of the stock ODIN images (500-600 Mb, from the same link) through ODIN, but when it starts with the SMD, I get a message "SMD header check fail: boot.img" on my phone, and ODIN thinks for a while, then stops, saying 1 fails and 0 successes.
So here I am, asking for help. Would any of you have any ideas, or explanations (in layman's terms!) of what has happened / what I should do to get my phone useable again? Thanks in advance.
P.S. Also, I should mention I'm doing all the accessing through VMWare Fusion running Windows XP, on Mac OS 10.7.5

Just an update on the situation - Telus gave me a brand new phone (without me paying anything), same model, because I bought mine less than a month ago, and they provide all new phones with such a warranty. All they did was check it wouldn't turn on, and I was good to go.
That being said, I still would be interested to know how to solve my previous situation in general, as I plan to get more into this sort of stuff.
Also, I got into a detailed discussion on reddit about the situation and some experimentation, which might be useful in solving the situation. It's located at /r/AndroidQuestions/comments/1du4j8/galaxy_rugby_pro_not_turning_on_after_failed_rom/

5.1.1 OTA?

So today(5-15) I saw online that T-Mobile USA released the 5.1.1 OTA for there branded Galaxy S6/S6 Edge, so any info on when the Verizon branded version is coming out? I'm having multiply major bugs(wifi, memory, and lagging) across 3 different S6 devices(original device and 2 replacements) since launch day. Also, the Verizon Branded OTA that just came out brought me new bugs like with Google voice to text giving me 2 new bugs and making it unusable. Also, apps are freezing like crazy and ends up freezing the whole phone and when I try to lock the phone with the power button when an app is freezing it opens up the camera instead of locking the phone and most of the time I have to restart the phone when this happens and it happens quite often, but only started after the Verizon OTA. Also, from launch day(across all 3 devices) I been having memory issues with the phone, it tells me it has between 1GB-1.2GB of total memory on the phone and I only have 748MB total available with only very few apps on the phone at the moment, everything closed and all the bloatware gone off the phone. I herd that the Verizon OTA we just got was suppose to fix the memory issue, but apparently for me it did nothing at all with the memory on my phone. and lastly I'm having the major wifi bug a lot of us are having witch for me started on the 6th day after launch and never worked again even after I had 3 different devices and still the same thing is still ongoing, and in fact the Verizon OTA we just got made the wifi bug even worst then before.
So the 5.1.1 OTA is really needed for me to fix these ongoing and new bugs I'm having and after 2 months I'm getting sick and tired of waiting for patches to come out!

You probably should go into your system recovery and clear cache. That will probably help a majority of your bugs.

charlesvw9 said:
You probably should go into your system recovery and clear cache. That will probably help a majority of your bugs.
Click to expand...
Click to collapse
I already did that and nothing changed at all, and like I said I had 3 different devices and nothing changed at all. In fact the 3rd device I got which I still have was giving me problems from very first time I turned it on and during the initial setup as soon as I turned it on from the FedEx box and the keyboard was slow and not putting the letters I clicked in the box and to click next/skip, restart or power off I had to use my pointer finger and press multiple times and fast like a woodpecker would on a tree in order for those functions to respond, and before I can even finish the initial setup I had to already do a factory reset on the phone. Even typing right now in this box responding to you the phone is lagging just typing now.

Don't think Verizon has announced anything yet. The current G920VVRU1A0E2 works fine for me.

To help with keyboard lag - go into settings and make sure the proper language is intalled and updated. Have you tried different keyboards? Swiftkey?

krelvinaz said:
Don't think Verizon has announced anything yet. The current G920VVRU1A0E2 works fine for me.
Click to expand...
Click to collapse
Same here and I'm in no hurry to lose root.

krelvinaz said:
Don't think Verizon has announced anything yet. The current G920VVRU1A0E2 works fine for me.
Click to expand...
Click to collapse
Well 3 different phones since launch day have been giving me all different kinds of problems and never had a device with out a major problem in it and the new Verizon OTA that just came out in June made the phone even worst then before. The Build for the update is G920VVRU1A0E2, and in fact I even had problems getting the update on my phone because from launch day of the OTA-4days after it came out the OTA would not fully download and give me error code 503 and it wasn't until the 5th day that it worked and then when I finally got it installed on my phone it just brought more bugs to the phone like I talked about in the OP

bigj0110 said:
Well 3 different phones since launch day have been giving me all different kinds of problems and never had a device with out a major problem in it and the new Verizon OTA that just came out in June made the phone even worst then before. The Build for the update is G920VVRU1A0E2, and in fact I even had problems getting the update on my phone because from launch day of the OTA-4days after it came out the OTA would not fully download and give me error code 503 and it wasn't until the 5th day that it worked and then when I finally got it installed on my phone it just brought more bugs to the phone like I talked about in the OP
Click to expand...
Click to collapse
Have you tried using Odin to flash back to stock with the full tar file instead of the update? If not go here and give it a shot. If you use the OE2 one you will have to factory data reset to wipe your phone clean either after or before you flash.

charlesvw9 said:
To help with keyboard lag - go into settings and make sure the proper language is intalled and updated. Have you tried different keyboards? Swiftkey?
Click to expand...
Click to collapse
yea I tired that, but this started as soon as I turned on my phone for the very 1st time trying to do the initial set up, plus like I said even pressing next/skip, power off or reset in the initial setup was a hassle. I had to take my pointer finger and point it down and press fast and many times like a woodpecker in order for the buttons functions to work and I could not even finish the initial setup and had to already do a factory reset before the initial setup was even finished on the 3rd device I have now. The phone is so bad that even clicking the home button some of the apps, Google search and weather is not on screen right away and takes second or 2 to show up, its lagging to show up.

Misterxtc said:
Have you tried using Odin to flash back to stock with the full tar file instead of the update? If not go here and give it a shot. If you use the OE2 one you will have to factory data reset to wipe your phone clean either after or before you flash.
Click to expand...
Click to collapse
Thanks, but I already did that last night and still the same thing nothing different at all changed for me, it was a complete waste of time!

bigj0110 said:
Thanks, but I already did that last night and still the same thing nothing different at all changed for me, it was a complete waste of time!
Click to expand...
Click to collapse
That stinks, hopefully the next update will fix things for you. Mine has been running fine for the most part.

Misterxtc said:
That stinks, hopefully the next update will fix things for you. Mine has been running fine for the most part.
Click to expand...
Click to collapse
3 different devices and still the same exact major things plus new things on each device are going on with the phone. Switching out the device should fix it all, but I guess this is not the case here. Plus about the wifi issues I'm in a XDA forum 13 pages long about the phones wifi not working(I know it says edge, but it's the same problems with the S6 and S6 edge so no difference)
http://forum.xda-developers.com/galaxy-s6-edge/help/wifi-dropping-t3079504

I would not be surprised to see that the new upgrade to lollipop was to foil or prevent root. Kind of like the s4. screwed up everything now I have no root.
THANKS SAMSUNG !!!!!!

traco1 said:
I would not be surprised to see that the new upgrade to lollipop was to foil or prevent root. Kind of like the s4. screwed up everything now I have no root.
THANKS SAMSUNG !!!!!!
Click to expand...
Click to collapse
They already said that the new update(5.1.1) is taking away root

My 1st phone which arrived on Sat came with G920VVRU1A0E2 out of the box.
Other than normal setups, and uninstalling Google Play Services and Google Play it has not had any problems.
Perhaps you should go into a store and show them how it is not working?

traco1 said:
I would not be surprised to see that the new upgrade to lollipop was to foil or prevent root. Kind of like the s4. screwed up everything now I have no root.
THANKS SAMSUNG !!!!!!
Click to expand...
Click to collapse
Ya you're thanking the wrong company here. You need to thank Verizon...

krelvinaz said:
My 1st phone which arrived on Sat came with G920VVRU1A0E2 out of the box.
Other than normal setups, and uninstalling Google Play Services and Google Play it has not had any problems.
Perhaps you should go into a store and show them how it is not working?
Click to expand...
Click to collapse
I did on launch day, I went back to the same corporate store a few hours later and got into a fight with the sales rep who sold me the phone a few hours earlier and the store GM because they were Ignorant because my phone was hot as fuc k at 90F and hotter and they said nothing was wrong. On top of that they even lied to me about having the edge devices in stock on launch day and even pulled out the normal S6 trying to trick me and it was not until I said something did he say oh this is not an edge and then said there was no edge's in stock, but while I was waiting in line I asked him and 2 other reps and they all said they had the white 64GB edge in stock. They rather lie to there customers to make a sale then tell the truth(at least this corporate store location), and then when you have problems with the phone they don't care to help you at all. Even 611 said this was very wrong and made a complaint on mine and 611's behalf on the corporate store and the sales rep.

Misterxtc said:
Have you tried using Odin to flash back to stock with the full tar file instead of the update? If not go here and give it a shot. If you use the OE2 one you will have to factory data reset to wipe your phone clean either after or before you flash.
Click to expand...
Click to collapse
Here is an update, as of recently my phone is getting really really hot and temperatures of 120F+ and even Verizon technical support saw that through their diagnostic system as it was actually on those temperatures at that very moment when they were looking. Also, from me just being tech savvy and Verizon technical support confirming it as well this phone is also supposed to have a safeguard in the phone and if it gets too hot the device is upposed to power off on its own, but apparently the safeguard is not working because when the phone gets very hot the battery starts flashing and in the middle of the screen it tells me the phone is very hot and it only lets me click OK. If I'm charging the phone the battery flashes and say the same thing but just adds unable to charge, & I can unplug the charger and immediately plug it back in to the phone and it will start charging again and then a few minutes later it will give me the same message. When it's doing that its not supposed to tell me anything it's supposed to just shut off and its not doing so.
So there overheating policy states that I have to bring my phone too a corporate store and they're going to replace the device right on spot. So Sunday I went to the corporate store to do that, but for some reason their system wouldn't allow them to process this because it didn't have an option to do it and the general manager and the store representative we're booth trying together for at least 45 minutes. They ultimately ended up just sending me a replacement device via Fedex to my house and when the phone arrives today(7-2) I have to bring the overheating device that I currently have to the store so they can do what they need to do to send it back because by law I'm not allowed to send an overheating device back. Verizon corporate store processed my order on Sunday and I was supposed to get the device on Tuesday but I'm getting it today due to inclement weather at the FedEx Memphis Tennessee hub and so Fedex at the Memphis Tennessee hub was at a complete standstill and my package was part of it.
Once I get my 4th replacement device and start using it for a while I will let you know how it's working

Managed to Get Troublesome N915A to Work, How to Keep It From Updating?

So I'll try to keep this as short as I can. Basically, this is my gf's phone that she gave to me. Ever since it updated to 6.0.1, she's had nothing but problems with it. Constant freezing, lagging, restarts, SMS trouble, poor battery life, you name it. Recently AT&T rolled out an update and her phone upgraded automatically. After that it pretty much bricked. The update failed for some reason and the phone got stuck in Download Mode. And then it didn't turn on for almost a week. Since her phone is a couple months out of warranty, she was forced to upgrade to an S8, and she gave me this Note Edge.
Yesterday I spent a few hours trying to fix it. I finally managed to get it to power back on and flash a PIT file to it, then flashed a fresh install of 6.0.1 to it. It worked okay for maybe 10 minutes, but then it would reboot every time you tried to lock or unlock the screen, and was still super laggy. So I decided to to give it another try and I managed to downgrade it to 5.1.1. It seems to be working great at the moment (fingers crossed).
So after reading here in the forums, it seems that you can't root AT&T Note Edge's. Bummer. I was hoping I'd be able to disable updates on this phone, unlock it, and use it on a new carrier (I think Verizon is trying to kill my Note 4 now).
So my question is, is there any way that I can keep this phone on 5.1.1? I know this sounds stupid, but I'm not sure how AT&T updates work, if they're forced or you just get annoying pop-ups. Right now I'm reluctant to connect the phone to WiFi, and there's no SIM card in it. Either way I'd just like to disable updates.
I haven't messed with rooting since my S4, which was about 3.5 years ago, but if there's something I can do to keep this phone on 5.1.1, I want to try it. Thanks.

camismacho said:
So I'll try to keep this as short as I can. Basically, this is my gf's phone that she gave to me. Ever since it updated to 6.0.1, she's had nothing but problems with it. Constant freezing, lagging, restarts, SMS trouble, poor battery life, you name it. Recently AT&T rolled out an update and her phone upgraded automatically. After that it pretty much bricked. The update failed for some reason and the phone got stuck in Download Mode. And then it didn't turn on for almost a week. Since her phone is a couple months out of warranty, she was forced to upgrade to an S8, and she gave me this Note Edge.
Yesterday I spent a few hours trying to fix it. I finally managed to get it to power back on and flash a PIT file to it, then flashed a fresh install of 6.0.1 to it. It worked okay for maybe 10 minutes, but then it would reboot every time you tried to lock or unlock the screen, and was still super laggy. So I decided to to give it another try and I managed to downgrade it to 5.1.1. It seems to be working great at the moment (fingers crossed).
So after reading here in the forums, it seems that you can't root AT&T Note Edge's. Bummer. I was hoping I'd be able to disable updates on this phone, unlock it, and use it on a new carrier (I think Verizon is trying to kill my Note 4 now).
So my question is, is there any way that I can keep this phone on 5.1.1? I know this sounds stupid, but I'm not sure how AT&T updates work, if they're forced or you just get annoying pop-ups. Right now I'm reluctant to connect the phone to WiFi, and there's no SIM card in it. Either way I'd just like to disable updates.
I haven't messed with rooting since my S4, which was about 3.5 years ago, but if there's something I can do to keep this phone on 5.1.1, I want to try it. Thanks.
Click to expand...
Click to collapse
You should be able to turn off auto updates in the about phone area of the settings menu.
You might want to turn off the picture sync'ing in the settings area of gallery....three dots,top right corner.

GEAR S2 FIRMWARE FIXED!

I havent seen too many threads about the Gear S2s randomly stopping working and not being able to take updates on here, but the forums on Samsungs site is awash with them, so i figured id throw this out there for those who might stumble upon it.
For the last few months my sons Gear S2 hasnt been able to pair with any phone properly. It would initially connect, then say that a firmware updates was required in order to continue using the device and wouldnt let you just continue with the current firmware. I tried pairing it with my U1 S9, my fiancees 100% stock Cricket S9, my old A8, 2 old S5's, S7 and S7 edge both, S4 and finally a S3. All of them failed to update the firmware and there was a bevvy of Android OS versions that i tried, so that was effectively ruled out. No amount of facory resetting via the OS itself nor recovery changed it. I then went to the Samsung forums as a last hope and there were "certified Samsung tech"s replying stating that they were working on it.
Fast forward to yesterday (i have been dealing wit this since before Christmas) and th ekiddo asked if there was any progress. It had been about a week since i tried it, so i tried it with my U1 S9 again and to my UTTER SHOCK AND DELIGHT, it actually took the update this time! It installed, rebooted twice (as per normal) and paired 100% with my phone! I unpaired it and had the kiddo pair it to the A8. That worked too!
Moral of the story, if you have a Gear S2 sitting in a drawer that suffered teh same fate, try the update again. Its worth a shot!