Database Users

X10 crashed with no access to google - am I that f*cked?

Greetings fellas,
I'm having big problems with my SE Xperia X10. After installing some Apps the phone got stuck and is unable to boot up - all I can see is a nice SE logo. Good Job Sony so far! Well lucky we have an update service that provides us with the newest firmware updates - oh wait, it just told me I do have the latest version - goodbye.
There is no f*cking option to re-install? Are you kidding me? WTF is wrong with guys over Sony F*ckinson? I don't have any option to visit a service provider as I'm not in the country where I have purchased the phone. So I decided to give it a shot and called the hotline - just to get some f*cktard telling me I should visit a local service point. After I told him that my f*cking service point is almost 4000 miles away from ma' current location he said I'd have to wait for a firmware update then.
Seriously f*ck this. What is wrong with this company? No hard reset available? Jesus f*cking christ. Is there ANY chance to get this phone back to live? Or do I have to buy a decent phone because Japanese Swedish Whateverdaf*cktards are unable to provide me with decent support.
This is so weird.

ckx2 said:
Greetings fellas,
I'm having big problems with my SE Xperia X10. After installing some Apps the phone got stuck and is unable to boot up - all I can see is a nice SE logo. Good Job Sony so far! Well lucky we have an update service that provides us with the newest firmware updates - oh wait, it just told me I do have the latest version - goodbye.
There is no f*cking option to re-install? Are you kidding me? WTF is wrong with guys over Sony F*ckinson? I don't have any option to visit a service provider as I'm not in the country where I have purchased the phone. So I decided to give it a shot and called the hotline - just to get some f*cktard telling me I should visit a local service point. After I told him that my f*cking service point is almost 4000 miles away from ma' current location he said I'd have to wait for a firmware update then.
Seriously f*ck this. What is wrong with this company? No hard reset available? Jesus f*cking christ. Is there ANY chance to get this phone back to live? Or do I have to buy a decent phone because Japanese Swedish Whateverdaf*cktards are unable to provide me with decent support.
This is so weird.
Click to expand...
Click to collapse
boot into the safe mode, uninstall ur apps or do a full factory reset...
shld work..
to boot into safe mode
Turn the phone off
Power the phone back on
When it vibrates, press and hold the left menu button until it boots up and says SAFE MODE in the bottom left corner of the screen

repair the phone by running pc companion

tnx fellas will try that! excuse my language, kinda pissed off.

PC companion does not recognize my phone, no matter what I do.
Safe Mode does'nt work, it wont boot.
FFS I just wanna re-install the current firmware, is it so hard Sony Tardisson?

when the update service says there is no update you can click continue, it will allow you to restore the phone

No.
The only option is "Quit".
Nothing more nothing less, just "Quit".

thats strage.
you may want to follow the debranding process it will at least help you get your phone started.

don't follow a debranding process.
use SEUS instead of PC companion. see if that helps.

Usng SEUS should be possible, I think there's an option just to install everything again, even if it says you had the latest software.
Tried that yesterday on mine and it works..

SEUS does not allow me to reinstall the firmware again, it just detects the latest software and that it's, just a "quit" button and nothing else to choose. PC Companion doesn't work aswell.
So debranding might be the only option?

ckx2 said:
SEUS does not allow me to reinstall the firmware again, it just detects the latest software and that it's, just a "quit" button and nothing else to choose. PC Companion doesn't work aswell.
So debranding might be the only option?
Click to expand...
Click to collapse
On my version of the SEUS there is a 'repair' function on the front page, does yours have this ? It can run this even if I have the latest version installed...

No repair option, latest SEUS version.

having the same problem now. except it an warning sign and a picture of the sony x10.

seus update issues

Hi to all I thought I would post this purely because I am stumped and need some input please
I have an x10 i that I have been updating ota without issue for quite a while.I think(but am not sure) that I updated all the way from 16 to 23 or 24 not sure which.My phone is on the giffgaff (O2 subsidiary) network and my updates have always been prompt and ota.I originally bought the phone locked to Orange uk.The phone shows no signs of any branding at all and after a bit of research I couldnt find out how to view the phones CDA.
Anyway back on topic I was prompted at the end of last week that an update was available for my x10i.I had always used ota wifi for update.However the notification this time told me I would need to use seus or se pc companion.So I downloaded seus and attempted to update.All seemed well throughout the process.Until it finished and I checked my phone info to see I was back on R2BA20!? I have since tried to debrand and roll back with no success.Everytime I connect seus it tells me that I have the latest software.
Please does anyone have any similar problems or similar input?My phone has never been rooted.I am absolutely stuck with this

[Q]Help me with SEUS

now i'm using SE X2, but i got a big problem with SEUS when i wanna update my X2. After i had connected my x2 with SEUS successfully, finished downloading the new rom for X2 through SEUS, then it stoped, it didn't install new rom into my phone with the notice that the services was failed. I tried to reinstall seus but it still didn't work
Anyone helps me plz. thanks!

what windows do you use. is your pc strong enough to run SEUS, minimum specs are listed on the SE site? is your phone battery above 50%. test the usb cable if it works by transfering some data...

whoami9999 said:
now i'm using SE X2, but i got a big problem with SEUS when i wanna update my X2. After i had connected my x2 with SEUS successfully, finished downloading the new rom for X2 through SEUS, then it stoped, it didn't install new rom into my phone with the notice that the services was failed. I tried to reinstall seus but it still didn't work
Anyone helps me plz. thanks!
Click to expand...
Click to collapse
I have 2 PC's: 1 is a tablet laptop from HP (Vista 32bit), 1 is a desktop from Acer (Vista 64bit). The HP is high-usage, all sorts of crap on it. The Acer is low-usage, Media PC.
First few times I tried upgrading firmware (or reloading after a phone-hangup), I had to use the Acer, because every time I tried updating via the HP, ...it would run the progress bar ALL the way through the process to the end (right side of the bar), then give an error stating that the update failed.
A couple weeks ago, I did a reload again, and thought I'd give the HP a shot at it one more time. This time, it failed exactly the same way, but for some reason, I accidentally booted the phone.....and it was fine (did the whole new-setup as expected).
So, moral of the story:
--If the SEUS site isn't working for you, try another PC.
--If you have no other PC and the SEUS site is saying it's not working, don't believe it and try booting your phone anyway.
(I have a feeling that it never updates the bootloader, and that's in a separate memory space. So, you'd probably have to go out of your way to corrupt the phone so bad that you wouldn't be able to hook-up the bootloader with the SEUS site and try again.)

Hi whoami9999,
Just try it once again after stopping / disabling your anti virus and firewall.. And one more thing, don't forget to re-enable it after checking!
Regards,
Sujith

[HELP ]x10 not detected by seus...

Hi
I'm having some issues with seus and pcc, seus can't locate a new fw and repair :S
pcc is giving a message that it can't detect the phone's software
not sure what the problem is but besides these stuffs the phone is restarting, the only way I can install a fw is using flashtool but is not what I need for the moment
what can i do??

758 posts means uve been here some time and yet this Question was in general.

Sony Emma is an odd bird

(Apologies if this isn't the right forum...it's the only one I found that seems to deal in topics that are universally applicable to the entire Xperia line-up.)
For the entire time I've been using Xperia phones, I've always used the third-party "Flashtool" by Androxyde to flash my phones, and "XperiFirm" by Igor Eisberg to source my Sony ROMs from Sony servers. Both tools have proven to be extremely flexible and powerful, so why waste time with the first-party tools which don't give you much say or control over the process?
I also just recently realized that I had an inaccurate understanding of at least one of the first-party Sony tools: what Sony calls "Flash tool" on their developers site, but which calls itself "Emma". Based on posts I had read by others (esp. surrounding the bootloader upgrades for Z1/Z3 series that enable using the FOTAKernel partition to store and boot from a standard recovery image), I came away with the conclusion that the ROMs that Emma downloads are *different* than the ones that Xperia Companion downloads...that Sony tailor-made ROM releases specifically for users who had unlocked their bootloaders, and Emma was the distribution mechanism for those.
Maybe this was already obvious to everyone else and I'm just late to the party, but I recently decided to play with both Emma and the current iteration of Xperia Companion, and discovered this isn't the case.
The firmwares Emma downloads are *identical* to the firmwares Xperia Companion does. Assuming you can get both Emma and Xperia Companion to download the same exact ROM version for the same exact phone model with the same exact regional or carrier customization, the pre-decryption FILE_######## filenames are the exact same, the file sizes are the exact same, and in fact the downloaded files from both tools are bit-for-bit identical with each other.
As far as my previous misconceptions go, it would also appear that the bootloader improvements that Sony made to earlier phone models were in fact released to the general public through standard channels: if you wanted a bootloader version that could treat the FOTAKernel partition as a Recovery partition instead, all you had to do was upgrade to the latest ROM for your phone (and then unlock bootloader & flash a recovery image of your choice using Fastboot afterward, naturally). It didn't *have* to be done through Emma: the upgrade would arrive OTA and/or through Companion just as well (or of course packaged in an FTF and then flashed by Androxyde's tool). And all subsequent phone models seem to just have these bootloader improvements incorporated straight from the factory...no need to get Emma involved whatsoever.
This to me raises the question: why 2 completely separate tools from Sony, anyway? Xperia Companion (and Sony PC Companion before it) *refuses* to work on phones with unlocked bootloaders, while Emma *refuses* to work on locked bootloaders. Since they are both dealing with the exact same ROM code, why do either of them give a crap what the state of the bootloader is? In the instance of Companion, I could see a case being made for refusing to do a firmware upgrade to a phone with an unlocked bootloader, for the same reason that unlocking the bootloader stops OTAs from working: an unlocked bootloader means you don't know & can no longer trust what the state of the /system partition is -- it could have been modified -- and so a differential upgrade could completely fail to apply and even make Android unbootable afterward. But that's no excuse for making Companion refuse to do a "software repair" (which wipes out all code and data) on a phone with an unlocked bootloader! And likewise there is no excuse for Emma refusing to "apply a service" to a phone with a locked bootloader!!
It gets even weirder when you look under the hood of both tools and realize that they both use the exact same core (Java) routines to download and flash ROM images from Sony servers to Xperia phones. There is thus ZERO reason to differentiate them based on bootloader lock status. I'm okay with Sony having a generally consumer-facing repair tool (Companion) and more power-user one (Emma), but they both should absolutely work regardless of the bootloader being locked or unlocked. That's a stupid and artificial restriction.
I get the impression that Emma is used by more than just users of unlocked bootloaders (or as Sony thinks of them, the "developer community"). I think this might also be the same tool that they distribute to their Sony service partners for phone repair. This would explain why early versions downloaded from developer.sony.com would pop up a login screen unless/until you edited some .INI file that pre-populated it with credentials to enable "Sony developer world" mode. This means Emma is also PERFECTLY CAPABLE of "applying service" to phones with locked bootloaders anyway. It just chooses not to if you aren't an authorized Sony service center.
The final observation I'll make here is that Emma, at least while in "developer world mode", does often allow you to download and apply older ROMs for your phone. This logically must mean that all of the past ROM versions still exist on Sony firmware update servers and can still be downloaded from them. So my question in light of this is, why can XperiFirm only ever download the latest versions?
Tangentially related, anybody have a clue what the decision-making process is behind which ROMs Emma will offer to you for the phone that you have plugged in? I have a couple of Z5 Compacts: a U.S. model E5803, and an E5823 of unknown origin, and they both give different -- and equally weird -- results.
When I plug the E5823 in and put it in flash mode, Emma gives me like 5 different ROMs to choose from: a Lollipop 5.1.1 ROM, a Marshmallow 6.0 ROM, a Marshmallow 6.0.1 ROM, a Nougat 7.0 ROM, and a Nougat 7.1.1 ROM...and all of them are of NOBA customization. But the Nougat 7.1.1 ROM that it offers to me is 32.4.A.0.160, and not the very last/latest 32.4.A.1.54 release. Why the heck is that? I can download 32.4.A.1.54 for NOBA region from XperiFirm just fine, and if I try to do "software repair" to the phone from Xperia Companion, it also downloads 32.4.A.1.54.
When I plug the E5803 model from the U.S. in and put it in flash mode, Emma gives me exactly one option and one only: a very old Lollipop release (32.0.A.6.200) for "MY" (Malaysia) customization. THAT'S IT. No Marshmallow, no Nougat, and no other customization options. This is despite the fact that at the time I plugged the phone in, it was already loaded with and running a "US" customization ROM!
One might wonder if, say, my "U.S." phone is in fact NOT a true U.S.-released phone, and was perhaps flashed with Customized US firmware before it got into my hands. Well, from looking at the upgrade logs in the TA partition, that doesn't appear to be the case: it clearly started life as a U.S. model. And just in case there was some point at which I flashed Customized MY to it without remembering, I restored an old backup of the TA partition (which has nothing but Customized US firmware entries in it!), had Emma check it again, and SAME THING. So from this I can only conclude that it's basing the ROM offering off of the serial or IMEI of the phone?? Even so, where is it coming up with this Customized MY firmware, and why is it ONLY offering me Lollipop?

Considering Sony's Flash Tool a.k.a. "Emma" comes from a more "internal" background, it isn't hard to imagine it looking up unique serial numbers (such as the IMEI, as you had guessed) instead of more general information such as device model numbers and customization variants.
The supply chain game is prone to all sorts of mistakes and your particular phone might just have been filed in the wrong place. For instance, I've found one HP laptop whose serial number is not recognized by the manufacturer's customer support website nor the more involved services used for looking up spare parts and replacement accesories (called "PartSurfer"). I've also come across a bunch of Samsung phones which wouldn't upgrade via OTA nor using Kies, but ODIN did the job just fine.
As for the locked/unlocked bootloader restrictions, it might have to do with how the different tools do data preservation (or how they don't). As far as I remember, there were serious pitfalls when flashing unlocked devices with official tools which sometimes led to a hard bricks. "Find my Xperia" on unlocked bootloaders comes to mind. I guess Sony just doesn't want to be liable for data loss and decided to proceed with this ham-fisted approach.
As for XperiFirm, yeah, I was sad when I found out you could no longer download older firmware releases with it.

Pixelado said:
Considering Sony's Flash Tool a.k.a. "Emma" comes from a more "internal" background, it isn't hard to imagine it looking up unique serial numbers (such as the IMEI, as you had guessed) instead of more general information such as device model numbers and customization variants.
The supply chain game is prone to all sorts of mistakes and your particular phone might just have been filed in the wrong place.
Click to expand...
Click to collapse
Theory makes sense on the surface, but I keep running across weird oddities with every phone I've tried to have Emma look up. In my experience it is MORE rare for Emma to return what I would expect to be the proper firmware list for a specific Xperia phone than it is for it to return something that doesn't exactly match, which seems VERY common. In addition to the phones I talked about in my original post, I have also tried seeing what Emma thinks about the 2 Z3 Compacts I bought that are clearly U.S. models & NOT AliExpress counterfeits. They both had U.S. customization firmware loads on them, but Emma wants to download Malaysia firmware for both of them.
Pixelado said:
As for the locked/unlocked bootloader restrictions, it might have to do with how the different tools do data preservation (or how they don't). As far as I remember, there were serious pitfalls when flashing unlocked devices with official tools which sometimes led to a hard bricks. "Find my Xperia" on unlocked bootloaders comes to mind.
Click to expand...
Click to collapse
I'll have to look this up as I'm not familiar with the pitfalls you're talking about or with the specific Find My Xperia example you cite. But so far I have yet to run across a scenario *when flashing official Sony firmware images* where it makes a difference whether the bootloader is locked or unlocked. I've flashed various Xperias with the third-party Flashtool a zillion times, both locked and unlocked with the exact same FTFs. There's no difference I can see. And also both Emma and Xperia Companion download the *exact same firmware files* from the Sony update servers. So the Sony decision to make Emma ONLY work with unlocked and Xperia Companion to ONLY work with locked strikes me as completely arbitrary and nonsensical.
Pixelado said:
As for XperiFirm, yeah, I was sad when I found out you could no longer download older firmware releases with it.
Click to expand...
Click to collapse
My point here was more that the XperiFirm author, as I recall, claims it is impossible to download older firmwares from Sony servers because Sony deletes them. Emma, however, seems to disprove this claim. So it would be *nice* if we could figure out what exact query Emma is running in order to find the older firmware files that OBVIOUSLY still exist, and then replicate that outside of Emma.

Sony Emma
https://software.sonymobile.com/emma/doc/emma_user_guide.pdf (manual)
Sony Emma is an internal tool to flash and repair phone softwares for authorized Sony personnels only. It can do anything, from customization change, sim unlock, thief protection unlock,....So Sony make Emma very secure and therefore have many restriction in "public" mode. About the firmware question, it uses the internal server, not the public one for Xperia Companion (and XperiFirm). The firmware on both servers is the same generally, but the public one are subject to end of life policy, the one not available are the ones Sony dont support anymore.