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.

Latest Stock OS Download Available

If someone could,
It would surely be nice to know where a stock user can d/load the Latest Stock version in Zip Format that we could load our devices with... Either for the SD Card, or for the External Sd Card. There are sooooo many "update" info that it's very hard (unless you KNOW exactly where to look) but if it is posted as LATEST Stock d/l, That would surely make things a whole lot easier, and eliminate guessing games for us dummies...
I'd recommend NOT MIXING UP the OSes as well... Keep the SPECIFIC VERSIONS Separate and identifiable with the same nomenclature for each.
Just my 2 cents here....

That is what the stock updater does...it goes and gets it for you.

Yes I have problems with mine, and the "goes and gets it for you" says you have the latest.... That's one whole hell of a lot of help!

bobolinko said:
Yes I have problems with mine, and the "goes and gets it for you" says you have the latest.... That's one whole hell of a lot of help!
Click to expand...
Click to collapse
Then yours is the latest OR the VS OTA updater server is down. But in order to find the older ROM versions, the links are scattered in a few stickies, etc. For now, if you want the best stock rom, you want 3588, along with the gapps enhancement.
Here is a post that has the VS stock rom files too.
http://forum.xda-developers.com/showthread.php?t=842000

I heard reports that 4349 + data wipe = bricked. I'm seeing the same thing.
I could see them pulling 4349 for something this bad. Might explain why it disappeared on us this afternoon.
My guess, btw, is that there's something amiss in the ramdisk but I haven't tested it throughly.

Roe,
There is something wrong with the update. I can't explain it but I'm sure you'll find it
I would expected another update soon

I haven't had any time today to rip it apart - I haven't even compared it to 3991 (yet).
Going to do that over the weekend - just a heads up that today is probably the last day that I'm scanning this site heavily. This weekend I want to rip apart 4349, compare it with 3991 and see about the bugs (like the data wipe issue). If I can stabilize it, I'll still make a TwoTapsX 1.0 out of it.
As for TNT Lite 4.4.0 and gADAM 1.4.0, they will go into retired mode after this weekend - they will stay up here in XDA but I won't be developing them anymore. And the TwoTapsX .9 pre-release thread will also be retired and not developed further here. Again, I'm not permitted to link elsewhere, or so I've been told.

Remember the post from Adam about creating a developer area with them?
They do need help but don't know how to go about getting it without seeming having so many opportunities!
Or.......at least that is how it seemed.
He did ask what developers wanted or needed for a possible way to push the Gtab into the front of the tab race.

roebeet said:
I heard reports that 4349 + data wipe = bricked. I'm seeing the same thing.
I could see them pulling 4349 for something this bad. Might explain why it disappeared on us this afternoon.
My guess, btw, is that there's something amiss in the ramdisk but I haven't tested it throughly.
Click to expand...
Click to collapse
I had to reinstall 4349 several times yesterday after experimenting getting the Market working, and I data wiped after reinstalling 4349 each time. Mine never bricked. JFI..

just lou said:
I had to reinstall 4349 several times yesterday after experimenting getting the Market working, and I data wiped after reinstalling 4349 each time. Mine never bricked. JFI..
Click to expand...
Click to collapse
+1 mine didn't brick either.

TnT Build 1.2-4950 - UAT version, perhaps?

Given the recent Facebook rants (including my own), I took out my script for the first time in a month to scan their site. And I found this:
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-4950-user.zip
This is not from a Hannspad script, this is a GTab script. ZIP is dated July 7th, and the internals are dated June 6th (I hadn't scanned this since ~June 22nd being that I had given up on them, tbh). It's a Froyo build.
I have not tested this yet, so the usual disclaimers of use at your own risk. But at least this shows that some work is actually being done, on their end. I'm pretty busy this week at work but I want to at least take a peek to see what's changed, if anything.
EDIT: High-def video is still broken (my MP4 test file, that works in 3588 but not 4349, does not work here either. That's my "litmus test" for high-def playback).

so this was found on a Viewsonic source? Then why is it, that when I asked VS tech support (a week ago) if they were working on a stock firmware, I got the runaround, redirected to US Merchants phone number, and received the response:
"I have no information regarding the Gtablet in my resources"
If they had ANYTHING in development, they could have just told me, right? I mean, I own one of these things, and in fact, the response I did receive just pissed me off...
Oh...and get back to your vacation, man, you deserve it...wuit worrying about us for a while...seriously, thanks for everything you do, you know I've always stood behind your work.

roebeet said:
EDIT: High-def video is still broken (my MP4 test file, that works in 3588 but not 4349, does not work here either. That's my "litmus test" for high-def playback).
Click to expand...
Click to collapse
What mp4 are you using? Is it 1080p? encoding details? Just curious...
Anyone know why HD playback broke in later builds? Is their 1.2 compatible kernel just incomplete?

It's not the kernel (I tried that a while back) - it's something in the framework that causes issues. I suspect it's fixable and I know that US Merchants is aware of the issue as I've called them several times about it. That's assuming they are informing the developers.....
I used an MP4 that I acquired many months back myself - it's a 1080p MP4 encoded AVC (main profile) with AAC file. This file works fine in stock 3588 and Brilliant Corners (the latter being 1.2 based), but not on builds 3991 / 4349, and now 4950.
TJEvans said:
so this was found on a Viewsonic source? Then why is it, that when I asked VS tech support (a week ago) if they were working on a stock firmware, I got the runaround, redirected to US Merchants phone number, and received the response:
"I have no information regarding the Gtablet in my resources"
If they had ANYTHING in development, they could have just told me, right? I mean, I own one of these things, and in fact, the response I did receive just pissed me off...
Oh...and get back to your vacation, man, you deserve it...wuit worrying about us for a while...seriously, thanks for everything you do, you know I've always stood behind your work.
Click to expand...
Click to collapse
This is right off the TapnTap site, and it's definitely a GTAB build. Since it's not being pushed down to devices right now, my guess is that it's a UAT build of some kind.
Back before April, I could call customer service and they would actually tell me if it was UAT or not, as well as an approximate on when GA (General Acceptance) release would arrive. But after customer service switched over, this new area doesn't seem to know anything at all. Basically they are useless.
As for my break -- work has filled that up right now. But a real vacation is coming soon, thank goodness! One week away from it all...

roebeet said:
It's not the kernel (I tried that a while back) - it's something in the framework that causes issues. I suspect it's fixable and I know that US Merchants is aware of the issue as I've called them several times about it. That's assuming they are informing the developers.....
I used an MP4 that I acquired many months back myself - it's a 1080p MP4 encoded AVC (main profile) with AAC file. This file works fine in stock 3588 and Brilliant Corners (the latter being 1.2 based), but not on builds 3991 / 4349, and now 4950.
This is right off the TapnTap site, and it's definitely a GTAB build. Since it's not being pushed down to devices right now, my guess is that it's a UAT build of some kind.
Back before April, I could call customer service and they would actually tell me if it was UAT or not, as well as an approximate on when GA (General Acceptance) release would arrive. But after customer service switched over, this new area doesn't seem to know anything at all. Basically they are useless.
As for my break -- work has filled that up right now. But a real vacation is coming soon, thank goodness! One week away from it all...
Click to expand...
Click to collapse
Thanks Roebeet, I'll sit back and wait until you have the time to let us know if it's worth updating. Enjoy your vacation!

From a comparison with 4349, the usual app and framework files have been touched. Also, libgps, one of the camera libs, libwebcore and gpio-keys.
Also, two new files added:
/bin/BTMacUpdate
/bin/ethdhcpd
The latter is likely dock related, and I see at least one dock setting in the "Settings" apk that I don't believe I've seen before. I know that the dock was something they were working on with 4349 so maybe they've improved on that.
Sleep is still broken, at least with limited testing (left it in sleep overnight, tried it this morning and I had to reboot it). But again it's limited testing. Not sure if I would integrate this with Mountain Laurel yet - I might wait until I return from vacation and, if there's no GA update by then, I might make a minor update there or possibly a mix of a new pershoot or Clem kernel to get it up to recent changes.

Now that is interesting; thanks for sharing the info.
I wasn't expecting anything new from Viewsonic at this point, so I'm pleasantly surprised someone is (or was) still working on the gTab.

Very nice find indeed.
Can't wait to see what it will bring to the table.

Bluetooth and Ethernet drivers for malata dock???

Not sure what that BT binary is, but the other things seem be better dock integration. And it's about time given that build 3588 is still their "latest", at least as per their OTA updater. That's assuming they release this ROM at some point.

is this a 1.2bl that can be flashed with the 1.2 cwm?

I retract my question because I found a more recent thread referencing a newer build.

[Q] Just got Shield (32GB), It has 4.4.2, says OTA "1.21" available...

Hi folks,
My Shield 32 GB just arrived and is charged up. I've signed on with a google account and done nothing else.
I will eventually root it but want to put it through its paces for a month or so first.
It arrived with KK 4.4.2 (wow! so old!) on it. It offers an OTA update from October 2014. Says it is OTA 1.21. I've seen LOTS of other OTA numbers much later around these forums. Do I have to take the 1.21 OTA before I can get to the more recent ones?
And, by taking the OTA, am I doing anything irreversible that I probably shouldn't do, since I'm eventually a rooting and maybe ROMing kind of guy?
Thanks. I've read up and it looks like I probably want to go all the way to the 5.1 release, once they sort out the speaker-killing bug. But for the moment I'd like to make sure I'm not missing anything before taking the OTA.
Thanks!
Marc

I decided to download the update after I successfully activated the device on AT&T's cellular network.
That was a bit of a hassle... couldn't do it from the device (the ATT app said something about incompatibility with the SIM card), the PC online web registration wouldn't accept it because NVidia Shield wasn't listed in the device types, and it took the efforts of 3 ATT folks to get me activated. First one passed me to the second one when he found out it was a device not purchased from ATT (but... dude... here's the SIM and IMEI number that's all you need...), the second one set me up and told me to call another number to accept terms and conditions. Did that, still no joy, found the default APN isn't set up right. Fixed that, still no joy, eventually talked to person 3 that found out they didn't attach a data plan to the device when they set it up... as part of my family shared data account. Duh.
Anyway, I applied the 1.21 and then it prompted me to download the 2.1 update to Android 5.01. It has downloaded. I think I want to copy it over to my PC before I let it apply.
Marc

Hmmm. Poked around and found the 1.21 update but not the 2.1 full LTE OTA. Perhaps I'd need root to get at the files. Oh well. I can always download it if I need it. Applying the 2.1 update now.

And I've made it all the way to the 2.2.1 hotfix. Seems stable enough for the moment.
I understand OTA 3.0 got pulled; so I guess I'll be staying on Lollipop 5.01 until they release the fix.
It's a bit surprising that I had to do all the updates sequentially and that there wasn't any direct-to-the-latest. But it didn't take long. I wonder if all these OTAs are clogging up my memory somewhere?
OK, on to exploration!
Marc

the update got pulled indeed, caused all kind of problems, including blown speakers
nvidia employee told us on nvidia forum they would release a new OTA 3.1, targeted end of june
lastest news: it's now targeted end of july....

Desperately in need of quick help with my OnePlus One.

I haven't used my OnePlus One in several months since I got my Nexus 6. I've been meaning to sell my OPO, but got lazy about it. Now I can't be, and I need money for rent. A friend/co-worker who's in serious (in my opinion) need of a new phone wants to buy it off me.
My OPO was on LiquidSmooth 4.4.4 but obviously it's out of date, so I tried to update it. I tried once before to update it with a 5.1 ROM, but it kept failing. I remember there was something about the firmware or baseband version that needed to be flashed to go from KK to LP, but it was several months ago, and I can't remember what exactly it was. And for the life of me, I can't find it.
I tried to find what it was, and in my searching I found that CyanogemMod Official 13 had a built-in baseband updater. So that's what I tried. TWRP version was/is 2.8.7.0. Maybe that was the problem?
Anyway, CM13 (the most recent snapshot) installed, seemingly fine, but it won't recognize my SIM card. I try reinstalling it, and it still won't recognize the SIM. Moreover, it doesn't even detect a cell signal (it should, as all cell phones in the US are required to have 911 emergency access, even if you're not actually paying for phone service). And then it starts rebooting. Not a bootloop, because it boots. Then a few minutes later, it reboots. Continuously.
So I try a different ROM. The latest Resurrection Remix (I have it on my Galaxy S4 and it works fine). Same thing.
The even weirder thing is that I figure I should just restore my latest nandroid, but it's not there. In fact, nothing's there. Nothing visible through TWRP's file manager or backups. Not even old pictures, which I didn't delete. I didn't delete any storage (because I wanted my backup, just in case, duh). But TWRP still shows that there's 26GB available. So obviously, there's something there. I just can't see it. My fault for not saving the nandroid elsewhere, but Humpty Dumpy has already fallen.
I have Wugfresh's toolkit (yeah, yeah, I know...), and tried restoring it to stock, and it won't do it.
I've used ADK in the past, but it has been way to long for me to remember specifics, and it has apparently been updated with the newer Android versions. Obviously, I've looked at the sticky thread about restoring your OPO to stock, but it hasn't been updated in a while. So I'm worried about using those instructions. I've looked up youtube videos, and they're all too old as well. I'm also worried that I'd be using the wrong version of ADK. I'm not scared of using ADK, as long as the instructions are correct and clear. I'd be using Windows 8, if that matters.
So what I'm asking (begging) for is instructions on how to make this phone work properly again. Quickly. I've tried doing the research myself, and haven't found my solution. I'd keep at it, but time is getting short, and I can't afford that. Literally. I can't afford the hours spent (it's 1am and my the office closes at 4pm), and I can't afford being late on my rent. A couple weeks ago I spent way too much up in Phoenix to go see Guns N' Roses (at least I got a kickass T-shirt). Entirely my fault. Also my fault for not realizing how desperate my financial situation was about to be, and for waiting to ask for help until now. And I'm not going to ask to borrow money. I just can't.
Finally, and I know it's taboo to ask "what's the best ROM?", because I've answered that question myself with "there isn't one - try them out for yourself and find which one's best for you". But as I said, I'm out of time., and I haven't been keeping up with what's going on with OPO's development. My friend is not like us. His phone's a LG cheapo POS from years ago that's on 4.1JB. He uses it for calls, texts, and podcasts. He doesn't need root, or even custom recovery for that matter. In fact, I'd prefer if it didn't have root (although custom recovery might be nice, just in case). So if I can get this damn thing working properly again, what'd be a good ROM for my firend? OPO's official Oxygen? Are they still updating it? Stability is the primary concern, but if there's something that gets regular (and stable) updates, that'd be good too. With an updater that's built-in, simple, and wouldn't need and XDA forumite to do it for him. Because it'd be nice that he could get updates with Google's security patches. But since he's still using a 4.1 phone, he's obviously not all that concerned about that issue. But still, that'd be nice.
Thank you (fingers crossed).