Database Users

Update issues?

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

[Q] Questions about rooting, region locks, efuse

I have a few general questions I hope some people can answer to help me understand these topics better, numbered it for ease of replying.
1) For unlocked stock firmwares, what is the point of Samsung having multiple firmware files for different countries/regions? If you go to sammobile's website, you can see what I mean. I understand having different firmwares for different providers as they have their own bloatware/branding. But unless the unlocked firmware files contain different languages for different countries/regions, what is the reason for multiple unlocked firmwares? Gets confusing when choosing a firmware to flash your unlocked device (if I should choose UK or Germany, for example - and I'm sure both would contain the English and German languages anyway).
2) Is region locking now a non-issue ever since CF's region lock away solution? I'm assuming if I had an unlocked phone with original firmware that was not region-locked, that I shouldn't have to worry about upgrading to another unlocked firmware (that does contain region-locking) since CF's solution works? Or should I be worried about upgrading into a firmware that does have region locking?
3) Do all firmwares that contain Knox have the potential efuse trigger? And if so, what actions trigger that efuse? I gather from reading the forums that normal rooting triggers it (the DLV method excepted). But what if I wanted to flash my unlocked device with another stock firmware from another region (because I liked that firmware better) - would that trigger the efuse as well? Any other conditions/activities that would trigger the efuse?
Thanks in advance for helping me out with these n00bish questions.:good:

Anyone want to take a crack at these questions? Thanks!

s2kdriver80 said:
I have a few general questions I hope some people can answer to help me understand these topics better, numbered it for ease of replying.
1) For unlocked stock firmwares, what is the point of Samsung having multiple firmware files for different countries/regions? If you go to sammobile's website, you can see what I mean. I understand having different firmwares for different providers as they have their own bloatware/branding. But unless the unlocked firmware files contain different languages for different countries/regions, what is the reason for multiple unlocked firmwares? Gets confusing when choosing a firmware to flash your unlocked device (if I should choose UK or Germany, for example - and I'm sure both would contain the English and German languages anyway).
2) Is region locking now a non-issue ever since CF's region lock away solution? I'm assuming if I had an unlocked phone with original firmware that was not region-locked, that I shouldn't have to worry about upgrading to another unlocked firmware (that does contain region-locking) since CF's solution works? Or should I be worried about upgrading into a firmware that does have region locking?
3) Do all firmwares that contain Knox have the potential efuse trigger? And if so, what actions trigger that efuse? I gather from reading the forums that normal rooting triggers it (the DLV method excepted). But what if I wanted to flash my unlocked device with another stock firmware from another region (because I liked that firmware better) - would that trigger the efuse as well? Any other conditions/activities that would trigger the efuse?
Thanks in advance for helping me out with these n00bish questions.:good:
Click to expand...
Click to collapse
1. The different firmwares have variations on carrier specific bloatware and/or regional basebands that could impact your connection, although in reality, I've never had any problem using other modems on various Samsung devices in my region. This tends to vary quite a bit by region, so sometimes it matters, othertimes, it does not.
The general rule is to stick with your region if possible, but otherwise, if you want to avoid bloat, any firmware is possible as long as you make sure it's for your specific variant. That's the biggest caveat.
2. CF Region unlocking only works for the 9005, so Exynos based International models are not supported. Ony time will tell how long the exploit CF has found will actually be viable in future firmware updates. Things could change overnight.
3. Firmware versions beginning with J3 and above have the Knox bootloader, as far as anyone can tell at this point. I used to care about the Knox trigger, and it really pissed me off with the S4, but I've come to accept it as a price one must pay. In reality, all major players are working toward this "safety" goal. LG has their own version of a locked bootloader, etc. What triggers the Knox eFuse is custom ROM/Kernel/Recovery. Rooting alone isn't really enough to do it.

donalgodon said:
1. The different firmwares have variations on carrier specific bloatware and/or regional basebands that could impact your connection, although in reality, I've never had any problem using other modems on various Samsung devices in my region. This tends to vary quite a bit by region, so sometimes it matters, othertimes, it does not.
Click to expand...
Click to collapse
Not bloatware no, more carrier information, APN - http homepage/email set up etc. Unless it is a carrier's firmware rather than an unbranded firmware (unlocked)
donalgodon said:
The general rule is to stick with your region if possible, but otherwise, if you want to avoid bloat, any firmware is possible as long as you make sure it's for your specific variant. That's the biggest caveat.
Click to expand...
Click to collapse
Agreed. But you can install another region firmware if you wanted faster updates, or an update which is region specific

radicalisto said:
Not bloatware no, more carrier information, APN - http homepage/email set up etc. Unless it is a carrier's firmware rather than an unbranded firmware (unlocked)
Agreed. But you can install another region firmware if you wanted faster updates, or an update which is region specific
Click to expand...
Click to collapse
Right. I just meant to say that some firmwares are carrier firmware and others are open and tend to have less carrier branding and bloat in them.

Wow thanks guys for your detailed replies, much appreciated.
1) Yea, regarding the multiple firmware choices, I understand the need for separate firmware files depending on carrier-specific requirements. However, for a specific model of an unlocked/unbranded phone (say, the GT-I9505), the hardware should be identical regardless of where it's originally sold in the world. So it looks like the only reason for having multiple firmware files for say an unlocked GT-I9505 would be to include different languages. Why not just have one firmware file for a given unlocked phone and just include all languages? Unless I'm missing something here. A little confusing when I go to download a firmware file for my unlocked phone and have to wonder which choice contains the "best" upgrades.
2) So from what you say, as of right now, the N9005 version of the Note 3 is susceptible to CF's region lock away solution, which is great. Is this also true for all other Snapdragon-equipped models like the Galaxy S4?
3) So the Knox efuse becomes an issue only if you seek warranty work, correct? It doesn't actually hinder or restrict your ability to mod the phone even after the efuse is triggered?

s2kdriver80 said:
Wow thanks guys for your detailed replies, much appreciated.
1) Yea, regarding the multiple firmware choices, I understand the need for separate firmware files depending on carrier-specific requirements. However, for a specific model of an unlocked/unbranded phone (say, the GT-I9505), the hardware should be identical regardless of where it's originally sold in the world. So it looks like the only reason for having multiple firmware files for say an unlocked GT-I9505 would be to include different languages. Why not just have one firmware file for a given unlocked phone and just include all languages? Unless I'm missing something here. A little confusing when I go to download a firmware file for my unlocked phone and have to wonder which choice contains the "best" upgrades.
Click to expand...
Click to collapse
Yup different languages and region specific updates (Poland tend to update before UK for example)
2) So from what you say, as of right now, the N9005 version of the Note 3 is susceptible to CF's region lock away solution, which is great. Is this also true for all other Snapdragon-equipped models like the Galaxy S4?
Click to expand...
Click to collapse
It seems it works yes, a few conflicting reports, but 9 out of 10 seem to be ok, as for other models I'm not sure
3) So the Knox efuse becomes an issue only if you seek warranty work, correct? It doesn't actually hinder or restrict your ability to mod the phone even after the efuse is triggered?
Click to expand...
Click to collapse
Well yes and No.
Samsung are honouring some warranty work with 0x1 and sometimes they are not.
As for things working correctly, once tripped to 0x1 you cannot use KNOX functions, encrypt your containers etc. - Possibly be one or two other things you can't use that may not have been found yet(?)
But no it doesn't restrict anything once triggered bar what I posted about.

Will ChainFire's Region Lock Away TRIP Knox...if rooted with Knox not tripped?.

[Q] Help me! (firmware, modem, etc.)

hey guys,
i recently traded my korean s4 lte-a phone for a galaxy note sm-n9005. i am not certain where it is from originally, as the guy who has the phone isn't very smart about phones.
my main question/concern is how can i upgrade to kit kat while making sure that it is compatible with the SK Telecom network in Korea? I am currently in Korea and would like to root and upgrade the ROM. Would I need to use the SK Telecom stock rom (it is a different model than what I have) and get it to work on my sm-n9005? Or would I need to mess with the settings on ODIN when I run the new stock rom through odin?
Here is some info about my phone. It DOES currently work with the Korean network, although the signal is weaker than my old S4.
basically, can someone tell me which country/network firmware i can use for roms and whatnot? do i have the option of both a korean firmware and foreign one?
thanks in advance!

skim234 said:
hey guys,
i recently traded my korean s4 lte-a phone for a galaxy note sm-n9005. i am not certain where it is from originally, as the guy who has the phone isn't very smart about phones.
my main question/concern is how can i upgrade to kit kat while making sure that it is compatible with the SK Telecom network in Korea? I am currently in Korea and would like to root and upgrade the ROM. Would I need to use the SK Telecom stock rom (it is a different model than what I have) and get it to work on my sm-n9005? Or would I need to mess with the settings on ODIN when I run the new stock rom through odin?
Here is some info about my phone. It DOES currently work with the Korean network, although the signal is weaker than my old S4.
basically, can someone tell me which country/network firmware i can use for roms and whatnot? do i have the option of both a korean firmware and foreign one?
thanks in advance!
Click to expand...
Click to collapse
A little search would have shown you some apps for that, for instance:
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
From your pics the main (and most pressing) advice I can give is to stop immediately any updates AND security updates - if you are MI2 you can probably root with URDLV and keep knox 0x0! Read more around about that.

xclub_101 said:
A little search would have shown you some apps for that, for instance:
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
From your pics the main (and most pressing) advice I can give is to stop immediately any updates AND security updates - if you are MI2 you can probably root with URDLV and keep knox 0x0! Read more around about that.
Click to expand...
Click to collapse
the problem is that i have no idea which versions of roms i can use that will be compatible with my network in korea.
this phone is unique. the corners aren't rounded- they are sharp corners. i got this phone from someone whose uncle is a samsung exec in london. i was told this phone was only given out to higher-ups at samsung.

skim234 said:
the problem is that i have no idea which versions of roms i can use that will be compatible with my network in korea.
this phone is unique. the corners aren't rounded- they are sharp corners. i got this phone from someone whose uncle is a samsung exec in london. i was told this phone was only given out to higher-ups at samsung.
Click to expand...
Click to collapse
Run the program linked in my post above. You might also want to post a picture of the phone itself just for the curiosity of seeing a rare model on Note 3.

xclub_101 said:
Run the program linked in my post above. You might also want to post a picture of the phone itself just for the curiosity of seeing a rare model on Note 3.
Click to expand...
Click to collapse
It says it's from France. So I can use a french modem (csc) and be ok in Korea?

I will post a pic of my actual phone when I have time to do it. It looks like a Sony Bravia because of the sharp edges.

skim234 said:
It says it's from France. So I can use a french modem (csc) and be ok in Korea?
Click to expand...
Click to collapse
You might want to mask over the IMEI - I doubt it can be easily used but that is the normal way to do things here on XDA.
The results are a little fascinating - it looks like an early build - and the part that the knox warranty was not yet present is even more interesting - DEFINITELY do not upgrade anything for the moment! Also I would bet that you do not have any region lock, so I doubt that you have any major reason to upgrade in a hurry. Even if you DO upgrade at some point you should first save your (rare, non-knox) firmware/bootloader (that version is not listed for instance at http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=XEF#firmware and without saving it you might never be able to return to it). Also the bootloader might be interesting in the "fight against the knox warranty flag".
From what I know SK Telekom is using a model called here N900S and 2G and 3G should be perfectly compatible with the current modem that you have. For LTE the EU model is listed with 800/850/900/1800/2100/2600 while the N900S has 700/850/1800 - so except the 700MHz band it might still work on LTE with SK!
There is also a local thread for those original models from South Korea:
http://forum.xda-developers.com/showthread.php?t=2484602
If you have some time it might also be interesting to go in 'download mode" and get a picture from there - here is a picture on how it looks with bootloaders that have knox.

xclub_101 said:
You might want to mask over the IMEI - I doubt it can be easily used but that is the normal way to do things here on XDA.
The results are a little fascinating - it looks like an early build - and the part that the knox warranty was not yet present is even more interesting - DEFINITELY do not upgrade anything for the moment! Also I would bet that you do not have any region lock, so I doubt that you have any major reason to upgrade in a hurry. Even if you DO upgrade at some point you should first save your (rare, non-knox) firmware/bootloader (that version is not listed for instance at http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=XEF#firmware and without saving it you might never be able to return to it). Also the bootloader might be interesting in the "fight against the knox warranty flag".
From what I know SK Telekom is using a model called here N900S and 2G and 3G should be perfectly compatible with the current modem that you have. For LTE the EU model is listed with 800/850/900/1800/2100/2600 while the N900S has 700/850/1800 - so except the 700MHz band it might still work on LTE with SK!
There is also a local thread for those original models from South Korea:
http://forum.xda-developers.com/showthread.php?t=2484602
If you have some time it might also be interesting to go in 'download mode" and get a picture from there - here is a picture on how it looks with bootloaders that have knox.
Click to expand...
Click to collapse
The LTE IS working with SK, as well as the network. I'm just so lost about what kind of custom roms/kernels I can use that are compatible with my phone.
When you say backup my bootloader, how do I do that? EFS backup? Remember, my phone isn't rooted yet. Do you think I could use any N9005 4.3 root?

skim234 said:
The LTE IS working with SK, as well as the network. I'm just so lost about what kind of custom roms/kernels I can use that are compatible with my phone.
When you say backup my bootloader, how do I do that? EFS backup? Remember, my phone isn't rooted yet. Do you think I could use any N9005 4.3 root?
Click to expand...
Click to collapse
I am glad to hear about LTE! (it means that the 700MHz band is not that essential).
Custom ROMs might be a little further away (N9005 by the way, when done OK it might work with many N9005 ROMs), IMHO there are other things that can be done first that would make your phone better/faster.
If you want to root here is the sequence that I suggest:
- save everything that you have on the phone (if you have a LOT of stuff - to Google, Samsung, Samsung Kies or local with Helium)
- make certain that reactivation lock is OFF
- factory-reset the phone
- disable any update (say that you don't agree with the terms when asked) and disable any security update (that one is a separate setting in Security)
- use Saferoot first to try to root:
http://forum.xda-developers.com/showthread.php?t=2565758
- if it works the very next step after getting root is to save as much as possible from the original firmware (you might also need to install busybox before that):
http://forum.xda-developers.com/showpost.php?p=50011586&postcount=26
- if that succeeds and you have a 256MB debrick.bin please compress it (7z is pretty effective but ZIP will also be OK) and please upload it somewhere so that people that are trying to crack knox will have another thing to look at! :good:

skim234 said:
The LTE IS working with SK, as well as the network. I'm just so lost about what kind of custom roms/kernels I can use that are compatible with my phone.
When you say backup my bootloader, how do I do that? EFS backup? Remember, my phone isn't rooted yet. Do you think I could use any N9005 4.3 root?
Click to expand...
Click to collapse
Have you managed to do anything with the phone? Have you ever managed to enter download mode? How does that one look? (a picture would be great, and that way we would also see the unusual corners).

xclub_101 said:
Have you managed to do anything with the phone? Have you ever managed to enter download mode? How does that one look? (a picture would be great, and that way we would also see the unusual corners).
Click to expand...
Click to collapse
i've screwed with my phone too much and now it doesn't make phone calls consistently. =( do you have any idea how i can connect consistently with sk telecom in korea?

skim234 said:
i've screwed with my phone too much and now it doesn't make phone calls consistently. =( do you have any idea how i can connect consistently with sk telecom in korea?
Click to expand...
Click to collapse
What do you mean by that? What have you done?

skim234 said:
i've screwed with my phone too much and now it doesn't make phone calls consistently. =( do you have any idea how i can connect consistently with sk telecom in korea?
Click to expand...
Click to collapse
Very strange, your phone's Manufacturing date does NOT match with the Serial Number.

Can you post pictures of the phone itself?

Bootloader unlock allowed : no

As the title says, It seems the bureaucrats at EE UK network are using phones that cannot be bootloader unlocked, even if Sony do allow, albeit with some loss of features.
Considering I flashed a generic rom, and my important photos/whatsapp files got wiped (I forgot to backup) as it was stated with flashtool only account based user data will get wiped not data from internal memory/sd card, well that didn't work.
I needed to root to allow some recovery software get my photos/whatsapp files back.
Now finding that the booloader is unlockable . I just want to throw the phone at the kunts at EE management. " EE the UK's biggest and fastest growing, bunch of dicks!"
Is their anybody else on EE who's bootloader is unlockable?
I'm so depressed with this all.

You needed to root to recover deleted files that you deleted by rooting?

davestuarts said:
As the title says, It seems the bureaucrats at EE UK network are using phones that cannot be bootloader unlocked, even if Sony do allow, albeit with some loss of features.
Considering I flashed a generic rom, and my important photos/whatsapp files got wiped (I forgot to backup) as it was stated with flashtool only account based user data will get wiped not data from internal memory/sd card, well that didn't work.
I needed to root to allow some recovery software get my photos/whatsapp files back.
Now finding that the booloader is unlockable . I just want to throw the phone at the kunts at EE management. " EE the UK's biggest and fastest growing, bunch of dicks!"
Is their anybody else on EE who's bootloader is unlockable?
I'm so depressed with this all.
Click to expand...
Click to collapse
In Poland Orange locks bootloaders for good in SONY devices, as I know there are tricks to make it unlockable, but not sure if possible to do it at home.

adamk7 said:
You needed to root to recover deleted files that you deleted by rooting?
Click to expand...
Click to collapse
I have not rooted yet, have only applied a generic less bloated rom. But now I need to root, so I can use software like 'hexamob recovery' which needs root to access the internal memory.
Tbh, the photo's I took that got wiped are sentimentally so important, hence me getting so stressed about it.
rollesky said:
In Poland Orange locks bootloaders for good in SONY devices, as I know there are tricks to make it unlockable, but not sure if possible to do it at home.
Click to expand...
Click to collapse
Oh, so orange there do the same. Here its now T-mobile/orange joined together as EE.
There must be a way to change that Bootloader state to yes. I know Orange/EE won't do it. Many people have asked in their forums about similar devices.
Thx for the insight tho...

I'll be totally honest with you here & you wont like the answer...
...if it says "bootloader unlock allowed: no" it will most probably stay that way.
My last Sony phone was from O2 & it was the same story.
The history of Sony phones with that state have stayed that way, as far as I'm aware
This means, once (optimistic) we get root you will only be able to flash stock based roms
Considering rooting newer versions of android seem to be getting more difficult, finding a way to bypass the bootloader is going to be near impossible...never say never but don't hold your breath.
The only Sony phone I had where the bootloader got unlocked unofficially was the X10 mini pro (beast phone) & that is when they were still Sony Ericsson & over 2 years after release (luckily back then you could flash CM / AOSP etc with locked bootloader, not any more though!)
Best bet is, give the phone back & buy it from a reseller like Clove / Handtec if unlocking the bootloader is that important to you & its not a contract deal you're after (or get sim only contract or something...PAYG FTW)
Otherwise, remember this for next time...

davestuarts said:
I have not rooted yet, have only applied a generic less bloated rom. But now I need to root, so I can use software like 'hexamob recovery' which needs root to access the internal memory.
Tbh, the photo's I took that got wiped are sentimentally so important, hence me getting so stressed about it.
Oh, so orange there do the same. Here its now T-mobile/orange joined together as EE.
There must be a way to change that Bootloader state to yes. I know Orange/EE won't do it. Many people have asked in their forums about similar devices.
Thx for the insight tho...
Click to expand...
Click to collapse
phroenix said:
I'll be totally honest with you here & you wont like the answer...
...if it says "bootloader unlock allowed: no" it will most probably stay that way.
My last Sony phone was from O2 & it was the same story.
The history of Sony phones with that state have stayed that way, as far as I'm aware
This means, once (optimistic) we get root you will only be able to flash stock based roms
Considering rooting newer versions of android seem to be getting more difficult, finding a way to bypass the bootloader is going to be near impossible...never say never but don't hold your breath.
The only Sony phone I had where the bootloader got unlocked unofficially was the X10 mini pro (beast phone) & that is when they were still Sony Ericsson & over 2 years after release (luckily back then you could flash CM / AOSP etc with locked bootloader, not any more though!)
..
Click to expand...
Click to collapse
What phroenix said is true.
From Xperia T (2012) onwards, there's no chance to get the bootloader unlocked if you read "bootloader unlock allowed: no".
@davestuarts Your old customization was 1289-4465 (T-mobile/EE) so I'm making a new FTF for you with that old firmware, let's try this way

istux said:
What phroenix said is true.
From Xperia T (2012) onwards, there's no chance to get the bootloader unlocked if you read "bootloader unlock allowed: no".
Sony, will they ever learn. I'm glad I didn't get rid of my viper running One X yet.
Tbh, the Sony layer on kitkit is pretty good considering and I'm plenty happy keeping stock roms, My main things are to run exposed and xprivacy.
@davestuarts Your old customization was 1289-4465 (T-mobile/EE) so I'm making a new FTF for you with that old firmware, let's try this way
Click to expand...
Click to collapse
Thanks istux, appreciate the help and less stress feeling.
Tha

New firmware (23.0.1.A.3.12) releaed for Xperia Z2 + FTF

Somehow I have became the thread owner of this thread which was created by someone else. Locking the thread.

jst
jst

Oh wow, Only Taiwan gets it. Hope it fixes the bugs. Specially battery draining issue.

If anyone wants a prerooted & dual recovery installed flashable zip.. https://mega.co.nz/#!hYQjEaQR!psUF9q4OBo1nqZfkgdwv0Sk-HrFaBxjq-4gsF4xrf5U

What are the changes?Where can we find the change log?

If I flash that on my Xperia Z2 D6543 brazilian model, I will brick my phone, or it will work? Thanks.

It's quite clear that's carrier fw.
Nothing new in it...maybe only gew apps that we don't need.
Carrier fw are specific in some areas.
For example, in some countries it's illegal to disable camera sounds or you have extra settings in sms app (special character warning)...
So...It's still same fw only with few minor changes that rest of work actually don't need.
It should be posted in Mega collection for users who need it.

Customized TW - it doesnt sounds like carrier branded fw
Because there is no carrier name in it... By build number it seems like branded but doesnt sound like branded according to name Customized TW
Just saying...

funky0308 said:
It's quite clear that's carrier fw.
Nothing new in it...maybe only gew apps that we don't need.
Carrier fw are specific in some areas.
For example, in some countries it's illegal to disable camera sounds or you have extra settings in sms app (special character warning)...
So...It's still same fw only with few minor changes that rest of work actually don't need.
It should be posted in Mega collection for users who need it.
Click to expand...
Click to collapse
It IS posted in the mega collection, The Mod who I reported the thread to moved it over to the mega collection thread and some reason changed me as the thread owner LOL.