Database Info

Does my 2.2 O3D really think it has gb?

I have a stock O2 UK O3D. LG website says update available, phone says I have the latest version (v10k) which is 2.2 so I run LG updater on the laptop and click its update history tool which says "s/w v21a" as if it thinks I have gb.
I cannot find who provides my updates, it's definitely not O2, maybe if I rooted it I could find who supplies them via a config file or else I will be stuck with Froyo forever
Dave

mistermentality said:
I have a stock O2 UK O3D. LG website says update available, phone says I have the latest version (v10k) which is 2.2 so I run LG updater on the laptop and click its update history tool which says "s/w v21a" as if it thinks I have gb.
I cannot find who provides my updates, it's definitely not O2, maybe if I rooted it I could find who supplies them via a config file or else I will be stuck with Froyo forever
Dave
Click to expand...
Click to collapse
If you are operator locked and in the UK you will get the update december 5th.

It is due 5th of December in UK. However, you can flash the official ROM, see development forum.

According to the operator (O2) my phone is not supported by them for updates, and the phone seller has no idea who sends them. Will wait for december and see.
Thanks
Dave

I am with O2 but didn't get my O3D from them. Up until I flashed it last night it was still on 10D!
So nobody from O2 updated my handset.

I have to wait as if flash phone and mess it up cant replace it
Dave

You can try removing your sim card and selecting another country in the LG updater if your phone is not simlocked by O2.
Flashing the official rom isn't that hard either. I can't get the update either so I just followed the tutorial for kdz flashing and had GB on the phone in about 15 minutes without losing apps and messages/contacts etc.
If you're not sure about flashing then it's probably best to just wait. The update will be provided by LG themselves eventually through the update utility.

Think I will wait, have flashed phones before (put gb on my gt540) but knowing what cwn go wrong I daren't risk a contract phone as got two years til can replace it.
Dave

Same problem
I have an open phone in sweden. When uptating my phone i got v10k and i cant get v21a. Every check i updater and outside shows no possible update, but v10k. If i check update history in the updater it says v21a.
It is now a matter for the support and in the hands of the mobile phone expert. They have to solve the problem under the sales contract.

I got mine from a company that sells lots of different phones with various providers contracts so although my sim contract is with O2 in the UK the updates are not and the seller doesn't push ota updates so I have no idea how to find out where they come from.
Although I have rooted the phone now so if anyone knows a system file that stores details of where the update check connects to and replies with it I can check that
Dave

[Q]

Hello all,
!st time poster here. Hopefully I'm in the right place.
I have a rogers Galaxy s2 lte that came to me rooted. I flashed it back to stock using the steps here: http://forum.xda-developers.com/showthread.php?t=1342348
It all worked extremely well, phone boots and runs great, has all the rogers bloatware on it.
Only problem is, when I plug into Kies it tells me "Your device does not support software upgrading via Kies"
Current firmware version shows: I727RUXKJ7/I727RRWCKJ7/I727RUXKJ7/I727RUXKJ7 (ATT)
Any suggestions would be appreciated, thanks

Hey and ya your in the right place. You make sure you downloaded the i727R file not the i727. And also make sure you have the drivers installed on your computer for the phone

Use the sammobile tar and it will fix that. The i727r one

ROLLBACK FROM 7.0 TO 6.0.1 (G920F - ThreeUK)

OK guys, I've got a slight dilemma, I'll try and keep it short as possible but I cannot find any solution online as of yet..
I have been trying to resolve an issue with my partners S6 (G920F on ThreeUK) in which it keeps randomly freezing then rebooting (sometimes not rebooting!). At least 15-20 times a day.
It's already been repaired once by Samsung because of main board failure, and that was an absolute nightmare.(.basically took 2months and WE had to chase them up for it!)
Anyway, I've done all the noob stuff (factory reset, ALL WIPES, Odin flash the original FW it came with which I got from Sammoble..)
Correct me if I'm wrong but if it was software issue causing these hard reboots/freezes I'm sure one of the above processes would've eliminated it?
So. Last option was to flash Nougat via Odin, although it wasn't the Three branded one but the XEU UK one, I really had hoped this would've sorted it.
Nope.
Still freezing. Defo hardware yeah?
So now she wants to send it for second repair.
My concern is that I've flashed a non-brand FW on it, and it ODIN won't let me flash the original 6.0.1 back!!! (Locked bootloader I'm guessing???)
I really need to make sure (by Tues) that the phone is back to how it came as if they see that the FW doenst match up (also, the Three branded 7.0 hasn't been released yet!)
I've seen about an 'OEM UNLOCK' option in some S6 FW's..which would technically enable me to roll back....but XEU doesn't have this in dev options.
I hope someone can help. Sorry for the long post but I feel the details are necessary.
match

match_stick said:
OK guys, I've got a slight dilemma, I'll try and keep it short as possible but I cannot find any solution online as of yet..
I have been trying to resolve an issue with my partners S6 (G920F on ThreeUK) in which it keeps randomly freezing then rebooting (sometimes not rebooting!). At least 15-20 times a day.
It's already been repaired once by Samsung because of main board failure, and that was an absolute nightmare.(.basically took 2months and WE had to chase them up for it!)
Anyway, I've done all the noob stuff (factory reset, ALL WIPES, Odin flash the original FW it came with which I got from Sammoble..)
Correct me if I'm wrong but if it was software issue causing these hard reboots/freezes I'm sure one of the above processes would've eliminated it?
So. Last option was to flash Nougat via Odin, although it wasn't the Three branded one but the XEU UK one, I really had hoped this would've sorted it.
Nope.
Still freezing. Defo hardware yeah?
So now she wants to send it for second repair.
My concern is that I've flashed a non-brand FW on it, and it ODIN won't let me flash the original 6.0.1 back!!! (Locked bootloader I'm guessing???)
I really need to make sure (by Tues) that the phone is back to how it came as if they see that the FW doenst match up (also, the Three branded 7.0 hasn't been released yet!)
I've seen about an 'OEM UNLOCK' option in some S6 FW's..which would technically enable me to roll back....but XEU doesn't have this in dev options.
I hope someone can help. Sorry for the long post but I feel the details are necessary.
match
Click to expand...
Click to collapse
All international (g920F) variants have their bootloaders unlocked, so you don't need to go through any process for that. What I will say though is newer bootloaders, Samsung implement something in them that prevents downgrade from one os version to another.
But alas as aslong your knox counter is intact (meaning you haven't rooted) having a different firmware on there shouldn't stop them from attempting to repair the phone.
P.s try installing the 3 branded nougat firmware.

sofir786 said:
All international (g920F) variants have their bootloaders unlocked, so you don't need to go through any process for that. What I will say though is newer bootloaders, Samsung implement something in them that prevents downgrade from one os version to another.
But alas as aslong your knox counter is intact (meaning you haven't rooted) having a different firmware on there shouldn't stop them from attempting to repair the phone.
P.s try installing the 3 branded nougat firmware.
Click to expand...
Click to collapse
Ah ok. Unfortunately I am unable to roll back meaning the phone is stuck with an international unbranded firmware, which I'm hoping Samsung will not pick up on...another big giveaway is that there is no '3' logo boot animation as you would get with the 3 branded FW.
If only the 3 Nougat was out that would be my next step but typical of Three, they take the longest to release the newest update...so unless they release it before Tues morning then the phone will be sent off with the unbranded FW. hopefully you are right in saying that it shouldn't effect any warranty issues etc...

match_stick said:
Ah ok. Unfortunately I am unable to roll back meaning the phone is stuck with an international unbranded firmware, which I'm hoping Samsung will not pick up on...another big giveaway is that there is no '3' logo boot animation as you would get with the 3 branded FW.
If only the 3 Nougat was out that would be my next step but typical of Three, they take the longest to release the newest update...so unless they release it before Tues morning then the phone will be sent off with the unbranded FW. hopefully you are right in saying that it shouldn't effect any warranty issues etc...
Click to expand...
Click to collapse
If it's going straight to Samsung then aslong as knox is intact they won't care it has an unbranded firmware, the only thing that would stop them would be a phone which has been rooted, so I'm sure there shouldn't be any issues with this.

sofir786 said:
If it's going straight to Samsung then aslong as knox is intact they won't care it has an unbranded firmware, the only thing that would stop them would be a phone which has been rooted, so I'm sure there shouldn't be any issues with this.
Click to expand...
Click to collapse
Knox is intact, all legit apart from the one time ODIN flash of XEU.

So you mean if I flash a different stock nougat on a g920t1 it will continue to boot up even with frp lock on? This prevents the phone from booting up witj official metro pcs nouhgat

sofir786 said:
If it's going straight to Samsung then aslong as knox is intact they won't care it has an unbranded firmware, the only thing that would stop them would be a phone which has been rooted, so I'm sure there shouldn't be any issues with this.
Click to expand...
Click to collapse
Ok. Took phone into Samsung Support shop to see if they can repair...
Half hour we get phone call saying to come back as they have discovered 'some interesting things..' (me, sh*tting myself...)
The tech guy says that the phone has the wrong software on
(me looking shocked..)
After explaining that the phone has been previously repaired by Carphone Warehouse, the tech guy said ' they shouldn't have taken it for repair as it was a 3UK branded phone, so they've obviously replaced mainboard and installed unbranded FW instead of 3 brand...
So. Don't think that they overlook anything like This, they knew exactly what happened. Odin flashing does void warranty.

match_stick said:
Ok. Took phone into Samsung Support shop to see if they can repair...
Half hour we get phone call saying to come back as they have discovered 'some interesting things..' (me, sh*tting myself...)
The tech guy says that the phone has the wrong software on
(me looking shocked..)
After explaining that the phone has been previously repaired by Carphone Warehouse, the tech guy said ' they shouldn't have taken it for repair as it was a 3UK branded phone, so they've obviously replaced mainboard and installed unbranded FW instead of 3 brand...
So. Don't think that they overlook anything like This, they knew exactly what happened. Odin flashing does void warranty.
Click to expand...
Click to collapse
No way really? I've had phones repaired from them before with different firmwares and it's been fine, I suppose it depends on the tech who's looking at it. What was the end result? Was they not willing to repair it?

sofir786 said:
No way really? I've had phones repaired from them before with different firmwares and it's been fine, I suppose it depends on the tech who's looking at it. What was the end result? Was they not willing to repair it?
Click to expand...
Click to collapse
End result is we've taken it back to Carphone Warehouse for second repair, which was recommended by Samsung guy as he believes they were the ones who flashed unbranded FW after main board replacement (even tho it was me but no one needs to know that lol)
If CarphWhs come back saying "can't touch it as FW doesn't match" then obviously we can argue that the phone came back with that FW from first repair...I can't imagine they will.suspect that my misses has Odin flashed her phone with odd FW...
Lesson learnt - I will not intervene or use ODIN unless it's on MY PHONE.
Ultimately I tried to fix it with Nougat flash, thinking that I could revert back to 6.0.1 three brand FW if that didn't fix issue.
It's funny to see the Samsung guy baffled at how this FW ended up on the phone, Carphone Warehouse can be the scapegoat for my errors hopefully

Phone came back. Fixed and with UNBRANDED nougat lol
Win win.

Wow I remember this problem lol

*UPDATE* Bootloader v3

Just FYI, it appears with the new Blv3 firmwares, the device will only accept official firmware. Meaning, no more flashing U1 firmware on the carrier models, or vice versa. No more flashing U or U1 firmware to the Canadian W models. Flashing between carrier firmwares is fine as long as it's on a carrier branded device (running TMB on a VZW device, etc). But running 950U firmware on a 950U1 will result in a brick, that is this far unrecoverable.
If your currently are running U1 firmware on a U device, vice versa, or running W firmware on a U or U1 device, or vice versa, you need to flash back to the firmware version that shipped with your device BEFORE you accept any OTAs that take you up to Blv3. Currently the S series is still on BlV2, but may go to Blv3 like the Note series just did.
This has been tested and confirmed.
Credit goes to @me2151, @FatalONEM8 for discovering this and warning people. I didn't find the issue or test, it just passing on the info to hopefully save some bricks.
Update from @mweinbach:
"EDIT: After being tested by XDA Senior member me2151, it turns out cross region flashing does work. Prince Comsy Odin is working, but we can not test if the factory binary flashing will hard brick your phone. So flashing US unlocked onto a US carrier device should work."
To expand a bit on what @mweinbach*just said, @me2151*did some more testing, and he was able to successfully carrier switch from a 950U to 950W using Comsey ODIN. So it looks like Comsey ODIN is not patched as we originally thought. Not sure exactly what caused the tester's phone to brick, but it HARD BRICKED and had to be RMA'd at his expense. So we jumped on the forums here to warn others until more testing could be done. @mweinbach*wrote the article and @xdanilvaand I began posting here.*
We may have overreacted, but wanted to err on the side of caution to protect people from hard bricks.*
The Blv3 factory binary has not been tested, so still unsure if/how we will be able to use it, or if it will cause issues.*
For now, carry on as usual, but understand we still don't know the full implications of the Blv3 patches. One person has already HARD BRICKED, and @me2151*almost hard bricked testing all of this for us.

There is currently a group working on a fix for bricked devices, but for now consider it a hard brick. Don't chance it.

Is Oreo for the S8/S8+ a Blv3 firmware or is it BLV2?
just curious as I flashed my Verizon branded GS8 to U1 firmware to take the Oreo beta..

So If I own a Sm-G950U1 but I have been running G950U Tmobile Oreo beta and upgrade to the stable oreo I'll brick my phone? In order to prevent this I'll have to first go back to G950U1 on nouget and then go up to oreo?
I don't really want to do this because I am loving using the T-Mobile variant because it gives me multiuser (digits) since it's built in.

Does the same apply to exynos devoces?

As far as I know, if you are on the Oreo beta, at least on the Snapdragon US variant, you are still on v2 (the number after the U in the build number is the bootloader version). Do not accept any OTAs and only update if you are completely certain you want to be stuck.

ironbesterer said:
As far as I know, if you are on the Oreo beta, at least on the Snapdragon US variant, you are still on v2 (the number after the U in the build number is the bootloader version). Do not accept any OTAs and only update if you are completely certain you want to be stuck.
Click to expand...
Click to collapse
Does this mean that we can update to a build with Bootloader v3, but don't expect to be able to change carriers afterwards? For example, I switched my S8 from ATT to XAA to get rid of the bloat. Should I restore to ATT on Nougat or can I stay on Oreo beta on the unlocked U1 firmware?

vimerate said:
Does this mean that we can update to a build with Bootloader v3, but don't expect to be able to change carriers afterwards? For example, I switched my S8 from ATT to XAA to get rid of the bloat. Should I restore to ATT on Nougat or can I stay on Oreo beta on the unlocked U1 firmware?
Click to expand...
Click to collapse
You can stay on the unlocked firmware for now, but once you switch to one of the carrier firmwares with v3, you cannot go back to anything other than a carrier firmware with v3. You should be ok for now, but just be sure that the next time you update that it is not on v3 or you'll be stuck permanently or until a fix is found.

ironbesterer said:
You can stay on the unlocked firmware for now, but once you switch to one of the carrier firmwares with v3, you cannot go back to anything other than a carrier firmware with v3. You should be ok for now, but just be sure that the next time you update that it is not on v3 or you'll be stuck permanently or until a fix is found.
Click to expand...
Click to collapse
My question is I have an ATT unlocked device on Cricket Wireless running the oreo beta since I flashed it to unlocked firmware. Should I revert back to Nougat before the final oreo build or just stick with it?

Mr. Orange 645 said:
If your currently are running U1 firmware on a U device, vice versa, or running W firmware on a U or U1 device, or vice versa, you need to flash back to the firmware version that shipped with your device BEFORE you accept any OTAs that take you up to Blv3.
Click to expand...
Click to collapse
So what you're saying is, I'm running U1 on my Note8, if I take an OTA with BL3, it will brick?

raduque said:
So what you're saying is, I'm running U1 on my Note8, if I take an OTA with BL3, it will brick?
Click to expand...
Click to collapse
Yes I believe so. We are still looking into it. It may just be flashing with Comsey ODIN does it.

Mr. Orange 645 said:
Yes I believe so. We are still looking into it. It may just be flashing with Comsey ODIN does it.
Click to expand...
Click to collapse
Honestly, I think that the latter is what does it. Are y'all flashing from a fully OTA'd BLv3 Carrier FW to the BLv2 U1 FW using Comsey?
There isn't a U1 FW with BLv3 yet, right?

raduque said:
Honestly, I think that the latter is what does it. Are y'all flashing from a fully OTA'd BLv3 Carrier FW to the BLv2 U1 FW using Comsey?
There isn't a U1 FW with BLv3 yet, right?
Click to expand...
Click to collapse
There is not.
And I haven't personally tested it, but Comsey is required to flash U1, so we know it will brick the phone once it does reach Blv3.

Mr. Orange 645 said:
There is not.
And I haven't personally tested it, but Comsey is required to flash U1, so we know it will brick the phone once it does reach Blv3.
Click to expand...
Click to collapse
So somebody flashed a full Odin U/carrier FW onto an actual U1 device and it bricked?

raduque said:
So somebody flashed a full Odin U/carrier FW onto an actual U1 device and it bricked?
Click to expand...
Click to collapse
No on a U1. They tried to carrier switch on either a U or a W.

Ok... so they tried to go from a device running a Carrier fw on blv3 to... what? A carrier fw on blv2?

I know this is still early, but the more questions and answers I see, the more confused I am.
Do we know if all of these scenarios will have the same result?
a) I have a AT&T (950U) branded device. I flashed it to become unlocked software (950U1). The device currently updates OTA with unlocked updates. A BLv3 OTA will brick the device. True/false/not yet known?
b) I have a AT&T (950U) branded device. I flashed it to become unlocked software (950U1). The device currently updates OTA with unlocked updates. Assuming a) is FALSE. Device will operate as normal U1 phone, but I will never be able to put 950U carrier branded software on it (via modded Prince Comsy), because that will brick it. True/false/not yet known?
c) I have a AT&T (950U) branded device. I flashed it to become TMobile (950U) device. It now get updates via Tmobile. Future OTAs will continue as normal and I can even use Odin to flash other carrier software (950U), but I can NEVER use modded Odin to flash unlocked software (950U1)? True/false/not yet known.
Based on what I've read right so far. It seems that the answers all remain theoretical, thus not yet known, but based on the Note8 update, the answers would be a) False. b) True. c) True.
Am I far off base???
The thing right now that I understand the least is the scenario a). I don't understand why if I have a phone that was 950U but is now 950U1, why it would get bricked. I do understand that attempts to change it once BLv3 hit are currently DOA, but that's different than simply keeping your phone in the stream that it is currently.

There are some good questions in this thread, I realize that its an evolving situation... So I have to ask directly... I have a Verizon branded 950U that I followed https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817 to switch to XAA and flash the U1 firmware, and I have taken part in the Oreo beta.
Currently my phone has Baseband Version G950U1UEU2ZRA8. There is an OTA update pending right now that is G950U1EUE2ZRAE/G950U1OYM2ZRAE/G950U1UEU2ZRAE. From what I understand, and what I am reading about this BLV2 vs BLV3 issue, based on the numbers in this, if I take this update, I'll still be BlV2, and be ok? If I should want to return to stock Verizon firmware, I can still do it safely?
What I am unsure of is.. If the phone gets updated to BLV3 while I have the XAA/U1 setup on my Verizon branded 950U phone, will I still be able to flash back to stock Verizon, then just not change to anything else? or once I get on BLV3 I am stuck with whatever firmware I have on the phone? Or is that part still unknown for sure?

KidJoe said:
What I am unsure of is.. If the phone gets updated to BLV3 while I have the XAA/U1 setup on my Verizon branded 950U phone, will I still be able to flash back to stock Verizon, then just not change to anything else? or once I get on BLV3 I am stuck with whatever firmware I have on the phone? Or is that part still unknown for sure?
Click to expand...
Click to collapse
I am basically the same as you except AT&T beginning rather than Verizon. I currently have the ZRAE Oreo beta software running on my phone. Based on everything said so far, there is no danger yet in downloading that OTA because it is still BLv2. The danger would be if the final Oreo version drops with BLv3 and you apply it. Then we're left with these different scenarios that are still being figured out.

Absent any concrete info, I'm going to just avoid the Jan security patch on my Note8.
If I have to flash back the Verizon software to have a non-brick device, well I'll just sell this thing and buy a cheap unlocked phone with microsd, wireless charging and a nice screen.

Unlocked AT&T Galaxy S7 Active to Verizon

So, these past couple of days I've been trying to find a way to get my unlocked ATT Galaxy S7 Active to work with Verizon.
Well, I have read and read and can't seem to get it done. I just realized that it was an "active" which means its not a normal galaxy S7, I guess. I have read that flashing with the U firmware would be best, but every time I've found one that I thought would work it never has. I've tried both on a mac using the ported version of odin for mac which I couldn't get to work at all. I have also tried going with the Oreo OS as well as the one before it, but the U versions firmware, and trying to install them with the Odin 3.13 software using Vmware and it just constantly fails. is it even possible to flash the firmware on this model?
I have he ATT Galaxy S7 Active Model number: SM-G891A

NeedAMonitor said:
So, these past couple of days I've been trying to find a way to get my unlocked ATT Galaxy S7 Active to work with Verizon.
Well, I have read and read and can't seem to get it done. I just realized that it was an "active" which means its not a normal galaxy S7, I guess. I have read that flashing with the U firmware would be best, but every time I've found one that I thought would work it never has. I've tried both on a mac using the ported version of odin for mac which I couldn't get to work at all. I have also tried going with the Oreo OS as well as the one before it, but the U versions firmware, and trying to install them with the Odin 3.13 software using Vmware and it just constantly fails. is it even possible to flash the firmware on this model?
I have he ATT Galaxy S7 Active Model number: SM-G891A
Click to expand...
Click to collapse
This is why i never buy branded phones!
The rubbish ATT&T active is on a GSM baseband and Verizon use CDMA so your phone won't work on Verizon until you unlock the CDMA radio software on the phone.

Finally got my g891a on verizon with stock rom and root

I would be really interested to see how you did it. I'm in that situation now. I have the G891A and my carrier is switching from running on ATT network to Verizon. I like this phone (I know it is getting some age on it) and it still does all I need/want and I really don't want to give it up.