Related
strangest thing, i confirm the update and it closes and thats it. It doesnt show a download in the status bar or anything. any ideas?
Mine still says it is already upto date even though I know the 2.3.3 update is out for almost everyone else?!?
FK1983 do you have an o2 branded phone? (with o2 crap installed on/o2 boot up screen?) If so then you are probably waiting for o2 to ok the actual update as well as installing all their extra crap onto 2.3.3 before they let you update
Same probably for magicriggs and anyone else that has not recieved their updates yet. The update you are seeing will be the generic 2.3.3 update you have to wait for verizon to ok the update first then customise it with all the crap/restrictions they want on it.
Mozza2k11 said:
FK1983 do you have an o2 branded phone? (with o2 crap installed on/o2 boot up screen?) If so then you are probably waiting for o2 to ok the actual update as well as installing all their extra crap onto 2.3.3 before they let you update
Same probably for magicriggs and anyone else that has not recieved their updates yet. The update you are seeing will be the generic 2.3.3 update you have to wait for verizon to ok the update first then customise it with all the crap/restrictions they want on it.
Click to expand...
Click to collapse
It's on Virgin Mobile, must be why?
FK1983 said:
It's on Virgin Mobile, must be why?
Click to expand...
Click to collapse
It doesn't matter which network the phone is on. If you got it direct from virgin or it has the virgin boot up screen then its virgin "branded". Until virgin or any other network decides to ok the update (and make any modifications they want) unfortunately you will be waiting. Unless you unlock your boot then you can flash the generic 2.3.3 that people with unbranded phones got.
P.s i said o2 since the o2 logo is under your name
Would that be the same case with me? I originally got my XP from my carrier but I had already network unlocked it with a code that I purchased from Theunlock.ca and de-branded it with a generic R800i UK firmware where mines was originally a R800a.
Flava0ne said:
Would that be the same case with me? I originally got my XP from my carrier but I had already network unlocked it with a code that I purchased from Theunlock.ca and de-branded it with a generic R800i UK firmware where mines was originally a R800a.
Click to expand...
Click to collapse
No this only applies to people with a branded phone and a locked bootloader. If you unlock your boot which you have done you can do as you did and flash the generic fw (without extra branded crap on just standard bloat) From now on you will just update using the fw posted here instead of waiting for rogers.
Cool, thanks for clearing that up a bit!
But I didn't unlock my bootloader, I can't because it came from my carrier. What I unlocked was the network and now I can use another SIM card from a different carrier on it if I wanted to. But I guess it's still the same since I was able to flash it with a generic fw already.
I had no issues with the updating itself.
But I noticed that the standard music player sometimes doesn't play sound at all. I first have to kill it with a program like 'Advanced Task Killer' and then it works again. Anyone else has this problem?
My Unlocked XP can download the update but fails on the install, its attempts to install, resets, unpacked update, then attempts to update (icon on screen goes from two dots and openbox icon, to three dots and phone with arrow above) then screen goes blank, phone boots as normal (takes about 2-3mins) then warns that update was unsuccessful after pincode entry.
Thought it might due to lack of internal space, so cleared 80 megs on application space and still no luck.
Sent from my R800i using XDA App
Bricked after OTA update
My husband's Xperia play got bricked today after an OTA update. It had no customized software, just an unlocked bootloader.
Looks like this issue it's just affecting those ones with an unlocked one.
I just checked for the update manually on my PLAY earlier today and it was able to find the update. But I'm not going to install it until you can root v2.3.3 on a locked bootloader.
ritap said:
My husband's Xperia play got bricked today after an OTA update. It had no customized software, just an unlocked bootloader.
Looks like this issue it's just affecting those ones with an unlocked one.
Click to expand...
Click to collapse
If you unlock your bootloader you cannot use SEUS or OTA to update your phone anymore. You will have to flash the lastest fw onto the phone. See here to 2.3.3 firmware http://forum.xda-developers.com/showthread.php?t=1097591 also if you flash the first one you can then flash the rooted 2.3.3 http://forum.xda-developers.com/showthread.php?t=1098736 Same goes for Da22a since your XP is unlocked
So still no way to root 2.3.3 on a locked bootloader yet, only with an unlocked bootloader at the moment? Because it's not possible for my to unlock my bootloader on my PLAY because it was originally from my carrier.
Mozza2k11 said:
If you unlock your bootloader you cannot use SEUS or OTA to update your phone anymore.(snip)
Click to expand...
Click to collapse
I see you're right and i wish i had my husband have a look here before even thinking about it.
The problem is: while SEUS prevents you from unintentionally doing that, which i regard as fair, OTA just bricks your phone without further notice.
We've taken it to SE for repair, which they should do for an amount of euros they still haven't notified us (you see, it's out of warranty). Easy money, then: tell people how to unlock their phones and then spread some code which bricks unlocked phones .
I don't think SE speculated in making money here. It's a more like a 'here you go' now you have control over your phone to do almost what you like. The main target here I think is devs and flashaholics and such. There's always a risk involved with unlocking your bl and changing the S-ON to S-Off and such things. Ofcause you loose your warranty otherwise every john/jane does would come back and reclaim a new device when they bricked there phone. This comes from a demand within the android community that this is an option.
Further more I don't think SE knew about this. The .img to flash is not comming from We but from this community so they can't be held responsible for putting out an OTA that bricks your phone cause of what people might flash onto there phones. I hope that they will make some kind of check in the software updater similar to SEUS in the future or the ones who make flasheble .imgs will be able to disable OTA in the .imgs to come or upload a new one for people to use.
Regards Dousan...
ritap said:
I see you're right and i wish i had my husband have a look here before even thinking about it.
The problem is: while SEUS prevents you from unintentionally doing that, which i regard as fair, OTA just bricks your phone without further notice.
We've taken it to SE for repair, which they should do for an amount of euros they still haven't notified us (you see, it's out of warranty). Easy money, then: tell people how to unlock their phones and then spread some code which bricks unlocked phones .
Click to expand...
Click to collapse
Im not sure SE will repair your phone. I have read other people on here have sent it in for repair and got it back the same. Today a fix for bricked phones has come out http://forum.xda-developers.com/showthread.php?t=1126354. I would suggest getting your phone back from SE and fixing it yourself. Since the above thread's fix is free (you could always donate to Bin4ry & Blagus, dont know who else helped?)
I also agree with Dousans comments. Below a quote from http://unlockbootloader.sonyericsson.com/
Therefore, you should only unlock the boot loader of your phone if you are an advanced user with good knowledge of the technology and risks involved. We strongly recommend that standard users NOT unlock the boot loader, as it is not needed
Click to expand...
Click to collapse
Also not sure how long this has been posted on the site but se knows now and it working on a fix to stop it.
Note: We have seen in some forums that customers unlocking the boot loader on their phones have experienced problems when they accept a FOTA (Firmware upgrade Over The Air) update. The issue has been reproduced and we are working on a solution. For customers that have unlocked the boot loader please do not accept the Firmware upgrade OTA.
Click to expand...
Click to collapse
Rogers official one comes July 1st. (Canada Day)
Mozza2k11 said:
Im not sure SE will repair your phone. I have read other people on here have sent it in for repair and got it back the same. Today a fix for bricked phones has come out http://forum.xda-developers.com/showthread.php?t=1126354. I would suggest getting your phone back from SE and fixing it yourself. Since the above thread's fix is free (you could always donate to Bin4ry & Blagus, dont know who else helped?)
I also agree with Dousans comments. Below a quote from http://unlockbootloader.sonyericsson.com/
Also not sure how long this has been posted on the site but se knows now and it working on a fix to stop it.
Click to expand...
Click to collapse
You and Dousan may be right but indeed after unlocking the BL we didn't flash it; moreover, after that the phone has been working perfectly for more than a month, since the ota update of course: so it's their software which has bricked the phone, not us.
Moreover, it's true that we lost our warranty, and it's fair that those Johns/Janes won't get a new phone for free, but this doesn't allow then to spread around dangerous software and allowing free repair only to "warranty" customers.
I've already had a look at the fix described in this forum but it didn't fit, Blagus told me there was no solution, the payservers were down so i took the Play to SE...
Anyone know how to get flashtool to recognize the play? The only options are arc x10 x8 etc.
Same as this guy:
how did you guys even get the flashtool to work with the play? ive got the latest version and i keep getting an error saying it cant identify my device and the only options are for x10, x10 mini, x10 mini pro, x8 and arc, just curious
Click to expand...
Click to collapse
Hi Guys,
I was just in the process of setting up drivers and such on my Win 8 Machine for Flashtool to install the UK Unbranded .453 onto my 3 Branded Device and what pops up in the Background... Sony Companion with .253...
Updating right now!
So 3UK Users go and have a peek!
Enjoy!
still no update here.
uk handtec unit on rogers Canada network.
I have an unbranded rom but am on O2 in the UK. No update here. Seems strange that they will update different networks at different times in the same country. Sure there is a method to their madness but frustrating!
Yes..
Couldn't wait any more for unbranded update, so flashed my 3 handset back to 3 ROM and update came in straight away, yippee..
Nice to have stock browser back, but lost "my files" file explorer? can any one post this please, downloaded a few of market but nothing compares to this.
Overall awesome update, very quick and responsive, menus and screens seem allot blacker now as well.
I'm on 3 UK and don't have any update notification either on sony companion or OTA
Edit: Oh maybe because i flashed an unbranded rom. I take it this update isn't 4.2?
Edit 2: Eh, i just manually updated to a non-branded version. Seems way smoother so far and loving the colour adjustments.
any news guys for the UK unbranded
ron3000 said:
any news guys for the UK unbranded
Click to expand...
Click to collapse
As everyone everywhere on every network seems to think they're first to announce the update, keep an eye out for a new thread to tell us.
Hi guys just recieved my s4 today in the uk.
Its locked 2 three i dont like it branded.
can anyone tell me which firmware i should flash to
sim free version uk
And the newest 1 plz
Tbh don't bother unbranding it, if you want updates quick then your better off staying with the 3 firmware you have already got installed.
Updates on Simfree are painfully slow, compared to the networks we are still waiting for the update that 3 got a month ago.
If you still want to go ahead and unbrand your S4 then there are guides on here to help you do it, first of all though before you can install a unbranded firmware, I think you gonna need to have to unlock it first before you can do anything else.
yea thats fine i know how to do all of that
i just would like to know which firmware i need for the UK simfree i9505 version just so i know im flashing the right 1
can anyone guide me to the right 1.
theres so many im confused
This one
http://www.hotfile.com/dl/209462137/82c78b1/I9505XXUAMDM_I9505OXXAMDB_BTU.zip.html
But you already have the more up to date one on your phone already.
Join us other UK peeps here
http://forum.xda-developers.com/showthread.php?t=2191766&page=240
Ixon2001 that file is rather huge lol.
is that defo the latest unbranded firmware for uk sim free
Yip that the latest and yes they huge files for the S4.
ok cheers much appreciated
Hello guys, I have a Galaxy Note 3 SM -9005 not branded
and I'm still not receiving the update via OTA. I also tried Kies but that didn't help me. Does someone know how to get the update without flashing?
I'm in Germany and the KitKat update is already available (since one month now)
PS. Knox counter is 0x0
N79 said:
Hello guys, I have a Galaxy Note 3 SM -9005 not branded
and I'm still not receiving the update via OTA. I also tried Kies but that didn't help me. Does someone know how to get the update without flashing?
I'm in Germany and the KitKat update is already available (since one month now)
PS. Knox counter is 0x0
Click to expand...
Click to collapse
If you were rooted, then dat would explain why you didn't get OTA notification.
But anyways, as far as I know, only VD2 - Vodafone, VIA - O2 and DTM - Tmobile are available for Germany now and unless your phone belongs to one of these categories or should i say regions, then maybe you shouldn't actually get KK officially yet. Dial *#1234# to check.
And even if you fall into one of the above, you can still jst flash it in ODIN, Kn0x should stay at 0x0 as long as you do not root.
Cheers.
As far as I know the update should already be available, is getting March by now. I'm with O2. But anyway thanks for your reply
Have O2 actually pushed the update? OR are you referring to the Unbranded Kitkat that has been pushed? -- cause both are very different. - Also If O2 is anything like it is in the UK they're slow as hell to push out updates. Often last and very late.
I have a unbranded Note 3, but I'm using a O2 Sim card. I was referring to the unbranded update but I think since I'm using O2 it's recognized as a O2 phone, even in play store it shows my Note 3 as: O2 SM -9005
It should still register as an unbranded model due to your firmware. -- Mine is unbranded also and in play store I have O2 Appspace / O2 SM-N9005 like you. - Could try grabbing the actual unbranded ROM from Sammobile and flash it via Odin.
DBT unbranded just confirmed now.
Yep, update started here too
Lol. That escalated quickly!
Hey everyone, I'm not necessarily new to the rooting/custom rom scene, I spent hours messing around with my Note 2, but I've got a quick question because I can't find a straight forward answer.
Basically I'm Australian and I own the SM-N910G variant of the phone, it's NOT locked and I have no logo on my boot screen. The 5.0.1 update for the 910G was released today, hazzah! But that's only on the non-carrier OTA, Vodafone has just stated "Failed testing, contacting Samsung" now due to both Vodafone AND Samsung being slow in nature, this could take weeks. I'm also SICK of Vodafone's bloatware and extreme delay with updates (over a year for the Note 2's 4.4.4), and I'm not willing to do any extreme modifying to this phone unlike my Note 2 because I'm still paying this phone off on my contract, last thing I need is to be left with a bricked or unsatisfactory phone when I'm still paying off.
Now for anyone who doesn't want to read all that,
MY QUESTION: Am I able to flash the stock SM-N910G 5.0.1, and change any future OTA's to be the ones straight from Samsung without voiding my warrenty or increasing my flash count or voiding my future OTA updates. And if I can, what's the best way to go about it?
Because I'm sick of waiting 6 months for Samsung to bring updates to Australia, then another 6 months for Vodafone to finish "testing" it.
Also I originally posted this in the wrong section, which I apologize for.
I upgraded to the indian 910g non branded 5.01 lollipop a week ago and had no problems whatsoever. My phone was unlocked and originally optus.
Debranding
I recently this something you want. I debranded my Note 4 taken from Orange România. My phone was locked and with a rom full of Orange blotware. I've downloaded the unbranded German rom, installed with Odin, and so far no problems. Knox counter it's 0x0, the new CSC it now the German unbranded. Nothing wrong happened. I don't know about carrier lock but I was not interested in that.
As long as it is the same model number there should be no problem. But carrier lock will still be there. Good luck