What's a known, working procedure for flashing a different firmware on my X10a? Currently it's got an AT&T R2CA016 firmware on it and I want to debrand the phone.
I've went through numerous guides, using the PC Companion and Update Service to replace files, problem is, the software tells me my phone is up to date, additionally there's no "Re-install" button on this software, so using the SE software seems useless.
I also looked at XS++ which couldn't connect to my phone. If anyone has an AT&T phone and has debranded it in the last month, please let me know which procedure you used.
FYI, I've backed up my APN using APN Backup & Restore.
Thanks.
aln688 said:
What's a known, working procedure for flashing a different firmware on my X10a? Currently it's got an AT&T R2CA016 firmware on it and I want to debrand the phone.
I've went through numerous guides, using the PC Companion and Update Service to replace files, problem is, the software tells me my phone is up to date, additionally there's no "Re-install" button on this software, so using the SE software seems useless.
I also looked at XS++ which couldn't connect to my phone. If anyone has an AT&T phone and has debranded it in the last month, please let me know which procedure you used.
FYI, I've backed up my APN using APN Backup & Resture.
Thanks.
Click to expand...
Click to collapse
I was stuck on 020 for ages, the old method (replacing the files) no longer works and if it does it complete luck. the method i used to debrand can be found at this thread http://forum.xda-developers.com/showthread.php?t=683793
download the version for your region, country or whatever. follow the instructions to install the 026 generic firmware and viola its debranded with the latest firmware
vengeance1990 said:
I was stuck on 020 for ages, the old method (replacing the files) no longer works and if it does it complete luck. the method i used to debrand can be found at this thread http://forum.xda-developers.com/showthread.php?t=683793
download the version for your region, country or whatever. follow the instructions to install the 026 generic firmware and viola its debranded with the latest firmware
Click to expand...
Click to collapse
Thanks, I'll give it a try later this afternoon. I just reading up on the Omnius method? It seems to rely on decrypted ROMs, which contain "phone.zip" and "android_xxx.zip". Any particular page to start reading the relevant information on? There's a 103 pages in that thread!
aln688 said:
Thanks, I'll give it a try later this afternoon. I just reading up on the Omnius method? It seems to rely on decrypted ROMs, which contain "phone.zip" and "android_xxx.zip".
Click to expand...
Click to collapse
Not to familiar with that method i dont think, i didnt read much into though (as i was getting ready for the 2.1 update)
the one i used was easy enough to use, basically click the exe which brings up a command prompt file, connect your phone in flash mode, hit any key and let it do its thing, worked perfectly first time after trying the switch the files method about 12 times
http://forum.xda-developers.com/show...49#post8170549
use the firmware files on there instead of the other one, thats the one i used
vengeance1990 said:
Not to familiar with that method i dont think, i didnt read much into though (as i was getting ready for the 2.1 update)
the one i used was easy enough to use, basically click the exe which brings up a command prompt file, connect your phone in flash mode, hit any key and let it do its thing, worked perfectly first time after trying the switch the files method about 12 times
Click to expand...
Click to collapse
I don't see any firmware links on that page, it's actually on the next page, page 43. A generic X10a R2BA026 firmware is listed there. I might give that a go, either way, SEUS of PC Companion is out in regards to flashing my phone, they won't work.
I was able to debrand the phone by flashing with a generic X10a R2BA026 using EXploid one click guide, however it is still locked to ATT. Anyone knows how to unlock the phone? Thanks.
Deadx10 said:
I was able to debrand the phone by flashing with a generic X10a R2BA026 using EXploid one click guide, however it is still locked to ATT. Anyone knows how to unlock the phone? Thanks.
Click to expand...
Click to collapse
What guide did you use to debrand your phone? Can you give me a specific link?
I'm not bothered if it's locked to AT&T, I just want the AT&T garbage removed from it, I thought rooting would do that, but rooting just gives me super-user access to muck up the phone by deleting crucial system files!
UPDATE: I used the Grospolina method, here. So far so good, at least my phone boots! This method worked fine.
Deadx10 said:
I was able to debrand the phone by flashing with a generic X10a R2BA026 using EXploid one click guide, however it is still locked to ATT. Anyone knows how to unlock the phone? Thanks.
Click to expand...
Click to collapse
If you're trying to use it on a different GSM network, You can Always go to one of the unlocking companies on the net...They use your IMEI number to unlock the phone.
OTHERWISE, If you're with AT&T, You CAN call customer care, Tell them you're traveling over-seas with your cell phone and you need it to be unlocked to use one of the UK's GSM Sim cards...
That's how I would do it personally
aln688 said:
I also looked at XS++ which couldn't connect to my phone. If anyone has an AT&T phone and has debranded it in the last month, please let me know which procedure you used.
FYI, I've backed up my APN using APN Backup & Restore.
Click to expand...
Click to collapse
You SHOULD be good to go! Once you Root it with the generic firmware...If not, I'm CONFIDENT you can find someone to help ya on here with reflashing it to AT&T's Stock Firmware. I went through the entire root, rebranded mine (since I was talking about taking it back to AT&T for the Captivate) And have re-rooted it again without a hitch
I followed this guide, as posted by Grospolina, and it worked perfectly, flashing it to a R2BA026 ROM. The root option also worked, and I installed the Market fix. In general, this IS how I want my phone, no AT&T garbage-ware installed. I'm content with this.
I tried other flashing guides, involving SEUS and PC Companion, all of them were a waste of time, due to a) The software kept telling me my phone was "up to date", and b) There was no "re-install" button to re-install the ROM on the phone. I WAS going to try Omnius which I suspect is a "pay-for" option, but this Grospolina guide worked 1st time. Many thanks to you Grospolina!
Now I can be busy re-installing some apps I wanted, and possibly restoring my APN file, I'm unsure if I need to at this point.
Diesel984 said:
If you're trying to use it on a different GSM network, You can Always go to one of the unlocking companies on the net...They use your IMEI number to unlock the phone.
OTHERWISE, If you're with AT&T, You CAN call customer care, Tell them you're traveling over-seas with your cell phone and you need it to be unlocked to use one of the UK's GSM Sim cards...
That's how I would do it personally
Click to expand...
Click to collapse
I called AT&T and they said that under some policies between AT&T and Manufacturer, they can't release the code. They asked to have the original owner of the phone to call in since I don't have the account with AT&T. I got this phone off Ebay, so I can't have the original owner to call in. I wonder if there is any other way to unlock it, because it is dead to me now since I can't use it under any other network....
Related
So i received a x10a as a xmas present. After doing much research i decided to debrand this phone by following the direction from this video:
http://www.youtube.com/watch?v=wacg-dsx9ew
I downloaded the GENERIC 2.1 x10a firmware from this thread
http://forum.xda-developers.com/showthread.php?t=825201
after i was done flashing, i noticed that my camera wasn't working anymore...it would boot into a black screen and after a while i received a forced close message. Then if i try to access the camera with the camera button, it shows a message "camera not available" so i tried to flash it with multiple different versions of generic 2.1 firmware with no luck.
After reading many post about the camera not working i believe it's a defective camera,this is when i decided to flash it back to the original at&t firmware (so i can take it back to the store and get a new phone with a working camera) using the files provided from this link:
http://forum.xda-developers.com/showthread.php?t=872298
now when i boot up my phone i all i see is a ! inside a triangle and the phone icon...what should i do???
thanks for all the help in advance
edit: finally was able to flash it back to AT&T with a rather strange procedure. I used the non-gui flasher to first flash in the 1.6 AT&T firmware but with no luck booting up. Then I flashed in the generic 1.6 firmware, surprisingly, when it booted up i saw the AT&T logo and all the AT&T app was in there. camera still didn't work, so i just took it back to the store and got a new unit. I flashed it again with GUI flasher, and now im running on nordic 2.2 generic firmware with all the features.
PS. does it matter if I am using a x10i firmware on a x10a phone? i did some research and only got mixed response, some say it doesnt make a difference some say 3G is affected. which one is correct????
I could be wrong but it sounds like you've bricked your phone. I haven't heard of issues (going through the forum) of people having camera issues using bin4ry's rom. Its most likely from debrnding it and then the multipile flash attempts.
You're going to need some time and patience to fix it. Have you tried the repair function on the SE PC Companion software yet?
Sent from my X10a using XDA App
e3jeremey said:
I could be wrong but it sounds like you've bricked your phone. I haven't heard of issues (going through the forum) of people having camera issues using bin4ry's rom. Its most likely from debrnding it and then the multipile flash attempts.
You're going to need some time and patience to fix it. Have you tried the repair function on the SE PC Companion software yet?
Sent from my X10a using XDA App
Click to expand...
Click to collapse
yes i just used the repair function, now im back on x10a 2.1 firmware, but still no camera...everything else works
Flash back to AT&T and return the phone as it's obviously defective, pain in the ass, but only option by the sound of it.
XperiaX10iUser said:
Flash back to AT&T and return the phone as it's obviously defective, pain in the ass, but only option by the sound of it.
Click to expand...
Click to collapse
as i said before, i tried to flash it back to at&t and it just ended up bricking my phone...am i doing something wrong?
jvx300 said:
as i said before, i tried to flash it back to at&t and it just ended up bricking my phone...am i doing something wrong?
Click to expand...
Click to collapse
Not sure, has your phone changed to an "i"? Do a full flash with seus, then use THIS to get back to AT&T
Hello everybody!
I am starting this new thread to try compile a simple to follow and reasonably written complete guide for rooting an Xperia Neo 2.3.3. I am doing this because, although there are enough information and software on this forum and on the internet in general, these are not really structured and gathered in a way that a non-experienced user (a.k.a. "noob") can easily manage, and the process of rooting 2.3.3. is a bit more complicated than 2.3.2 with Gingerbreak for instance.
This guide is for Xperia Neo running Android 2.3.3 with locked bootloader. Other devices with 2.3.3. might be rooted in a similar fashion.
Update: 2.3.4. for the Neo is out. Everything here still works as described with the difference that you get the latest 2.3.4 when updating OTA.
WARNING: some users reported that after downgrading from 2.3.4 to 2.3.2 in order to root, the battery meter showed 0%. I am not yet aware of a solution to this problem. So beware if your Neo already has the latest version.
Warning: Neither myself, nor anyone else but YOU is responsible if you damage your phone in any way or lose any information after trying to root your phone by folowing this guide! Also note that your warranty will expire when you root. However, unrooting should be possible, in principle.
--- Guide start ---
1. Back up your data. You could do this using an app called Backup Master from the Android Market. Additionally, I had my contacts and calendar synchronized with my Google account. SMS messages were not properly backed up, but I didn't care about them anyway. If you do care, you might want to save them to your SD card, using the built-in option or just use another app. Also make sure your battery is at least half charged before starting.
2. Download FlashTool from here or directly here. Install it by simply unpacking it somewhere.
3. Download the generic firmware 2.3.2 from here or directly here. You do this because Gingerbreak (will come to that) uses a security vulnerability to gain root rights in 2.3.2. that has been fixed with the new 2.3.3. Extract the .ftf file from the .rar archive you just downloaded to the sub-folder "firmwares" of your Flashtools installation from step 2. (You might need WinRar for extracting)
4. Go to your Flashtool installation to the folder "drivers" and install ggsetup-2.2.0.10.exe. Download the USB drivers for your Neo from here. Unpack the contents of the archived folder "amd64" (if on Windows 64) or "i386" (if on Windows 32) to the folder "amd64" or "x86" respectively of the installation folder of Gordons Gate. The path might be something like "c:\Program Files (x86)\Sony Ericsson\Gordons Gate\". Run DPInst.exe to install the drivers.
Alternatively to this step, I think you could install the drivers by just installing PCCompanion and plugging in your phone, but I did it the hard way.
5. Run the file X10FlashTool.exe; click Flash; you should see the firmware you downloaded in step 3 in the appearing window if you extracted it correctly; click OK (I recommend you leave the option "wipe data" checked, although some users reported that it worked for them even without wiping the data); follow the instructions (note that the back button on the Neo is on the other side as pictured); the flashing should take no more than a couple of minutes; start your phone - this will take a bit longer the first time. If after the reboot the battery meter is showing 1%, shut down and take out the battery for a minute, then boot up again.
6. Get Gingerbreak from here of directly here. This is the exploit that actually roots the phone. Copy it to your phone and install. You can do this a number of ways. For example: install ES File Explorer from the Android Market, access your PC via WLAN with it and install it directly from there. You will be prompted to change the setting to allow the installation of apps from unknown sources in case you didn't change it already. Also allow USB-debugging in the same settings menu under "developer".
7. Run Gingerbreak and tap "root device". This shouldn't take more than a couple of minutes, although some users reported it taking hours. If it is taking very long, you might want to try inserting another SD card and repeating the attempt. When it's done, it will reboot. Now you have a rooted 2.3.2. You can check this by installing the app "root checker" from the Android Market. When you start "root checker" you will be asked by an app called "superuser" if you want to grant root access to this program. This "superuser" app was installed by Gingerbreak after rooting and manages which program has root permissions.
8. Now before doing anything, go to settings>info>software update> update now and get the new Android 2.3.3 OTA (= over the air, i.e. via WLAN or 3G). Do not do this via your PC, because you will unroot the phone. There have been a lot of problems reported with this step. If right after you tap "update now" you get the message "unable to connect" try shutting down, waiting a minute and booting up again or also try setting the date and time to the correct values, in case you have something like 01 Jan 1980. Other users said, it just took a lot of attempts before it worked and that the problem might be with the SonyEricsson servers... If after the update was downloaded you get some kind of error message like "cannot update" it might be because you did some changes to system files or possibly you used a non-original firmware in step 3.
After the update was done, check again for root access with the "root checker"
9. Restore the data you backed up in step 1 and enjoy.
Update: I managed to update to 2.3.4. Unfortunately I could not simply update OTA from my rooted 2.3.3. I kept getting an error message after downloading the update, probably because I had changed system files. So I did all the above steps again, with the difference that in step 8 I got the 2.3.4. from the SE server.
--- Guide end ---
Please click the Thanks button and/or reply to this post and write your own experience or suggestions/corrections.
A similar guide/tutorial/how-to has been posted before (Here). Perhaps not as detailed as yours but nonetheless, it's been done. And do give credit to the necessary people.
But good job on taking the time and writing this up. I'm sure a lot of Neo users will appreciate it.
Cheers!
xtacy! said:
A similar guide/tutorial/how-to has been posted before (Here). Perhaps not as detailed as yours but nonetheless, it's been done. And do give credit to the necessary people.
!
Click to expand...
Click to collapse
Actually, I did link directly to the thread you wrote, because it was one of my starting points. And to be rigorous, the steps enumerated there are from here, but with the firmware for Neo. The real credit goes to the programmers of Gingerbreak, Flashtool etc.
Like I said, I was just gathering information and detailing them, I don't take credit for anything other than taking the time to write the post.
Yup, I had actually included that initially i.e. that most of us already know these steps from the original thread but then wanted to give you credit for doing what you did.
And when I said give credit where it is due, I meant the actual people behind the programs and kistigun for his tutorial.
guys after i root my neo according to this guide the ota firmware i get will be unbranded? right?
By the way thanks for the guide, i might use it one day after i gain more knowledge about those things...
If you've flashed the generic firmware, then yes, you would be unbranded BUT you will still be locked to your network until you purchase the unlock key.
Unbranding would remove all your network specific apps (part of bloatware).
marcindpol said:
guys after i root my neo according to this guide the ota firmware i get will be unbranded? right?
By the way thanks for the guide, i might use it one day after i gain more knowledge about those things...
Click to expand...
Click to collapse
An OTA update won't remove the branding, but flashing will. It's what I describe in step 5.
I was just like you a couple of days ago, but I managed to learn all this over the weekend and did all I described here. (and a few things more ) Don't rush into it. Read everything coherent and helpful you can find first.
xtacy! said:
If you've flashed the generic firmware, then yes, you would be unbranded BUT you will still be locked to your network until you purchase the unlock key.
Click to expand...
Click to collapse
Thanks for the info. I didn't have any network locks or branding on mine, but it's good to know that for future reference.
Vorsprung said:
An OTA update won't remove the branding, but flashing will. It's what I describe in step 5.
I was just like you a couple of days ago, but I managed to learn all this over the weekend and did all I described here. (and a few things more ) Don't rush into it. Read everything coherent and helpful you can find first.
Click to expand...
Click to collapse
ok i think i understand now, but just to clarify:
if i flash generic (unbranded?) and then do the OTA or Pc Companion update, the update i get will also be unbranded?.
also will all the future updates be unbranded too?
Another question: since my neo is Irish Vodafone branded phone, which generic software i should flash in step 5?
Thanks a lot for help and please do not get annoyed by my questions as i am totally noob when it comes to those things, also sorry for my poor English...
marcindpol said:
ok i think i understand now, but just to clarify:
if i flash generic (unbranded?) and then do the OTA or Pc Companion update, the update i get will also be unbranded?.
also will all the future updates be unbranded too?
Click to expand...
Click to collapse
The answer should be yes to both questions. Once you've debranded your phone, it will not get "rebranded" (except if you flash it with a branded firmware). The generic firmware linked here is of course without any branding.
marcindpol said:
Another question: since my neo is Irish Vodafone branded phone, which generic software i should flash in step 5?
Click to expand...
Click to collapse
You could use the generic one, but you will lose the branding. I'm guessing you don't have a problem with that.
marcindpol said:
Thanks a lot for help and please do not get annoyed by my questions as i am totally noob when it comes to those things, also sorry for my poor English...
Click to expand...
Click to collapse
You're welcome! I'm not exactly experienced myself, so I don't guarantee that my answers are 100% accurate and correct...
I don't think your English is bad at all. Don't you speak English in Ireland?
Can anybody give more details on the branding issue?
Vorsprung said:
The answer should be yes to both questions. Once you've debranded your phone, it will not get "rebranded" (except if you flash it with a branded firmware). The generic firmware linked here is of course without any branding.
You could use the generic one, but you will lose the branding. I'm guessing you don't have a problem with that.
You're welcome! I'm not exactly experienced myself, so I don't guarantee that my answers are 100% accurate and correct...
I don't think your English is bad at all. Don't you speak English in Ireland?
Can anybody give more details on the branding issue?
Click to expand...
Click to collapse
Thanks a lot for the answers
hehe yes people in general speak English here in Ireland but lets not forget there are thousands of emigrants from around the world living here too, i am one of them
Can you please also write which generic firmware should i flash, UK, World or any other? (perhaps there is IE one?), and will it affect the frequency of getting future official updates from SE? (yes i want to get rid of Vodafone from my phone and stay with a 100% SE official firmware).
Thanks
Once you flash a generic firmware, future updates will all be generic updates as well.
Some of the plus points that I can see of having a generic firmware is that
a) updates are rolled out faster (as compared to branded firmware).
b) you get rid of a lot of junk that network providers seem to put in i.e. bloatware.
OK I am now on generic, unbranded Global International 1247-0875_R11C , of course 2.3.3, however I did not root my phone and used SEUS instead OTA.
Thanks a lot Vorsprung and others for help
I just flashed my Xperia Neo 2.3.2 global, applied Gingerbreak, and updated OTA to the last 2.3.3 firmware (4.0.A.2.368)
I confirm I kept root!
Kalram said:
I just flashed my Xperia Neo 2.3.2 global, applied Gingerbreak, and updated OTA to the last 2.3.3 firmware (4.0.A.2.368)
I confirm I kept root!
Click to expand...
Click to collapse
Same here
I follow this guide and got my Xperia Neo rooted! Thanks Vorsprung!!!
I wanted it root to install Google Talk with video! It works very well!
Now I want a way to unlock the bootloader, as I want to run Cyanogen mod
Ask the Admin for your own forum section about the Neo, all this OTA-root with the latest firmware just making me jealous.
flashmode
Hi guys!
well I just can follow till step 5. Opening the "X10FlashTool.exe" --> Click On flash. that's it. It tells me to enter the flash mode but how? I pressed&hold the menu button before plugging the usb cable onto my PC. Instead entering the flash mode it only starts charging my battery. Can somebody help ?
thanks a lot !
i was clicking the wrong button
I have rooted 2.3.2 (checked with rootchecker) but when I try to update OTA it says "Your phone already has the latest software".. Please help!!
Edit: Even says up to date using pc companion.
Any ideas on how to fix my Xperia Ray? HELP..
Quick backstory - my Xperia Ray won't read my SIM card anymore. It doesn't even ask for my PIN number, it just boots as normal (after asking me to pick a language) but I have no connection to any network. I've tried using the SIM card in another phone and it works fine, therefore the problem is with the phone itself.
I'd recently had my phone network & bootloader unlocked by wotanserver using the test point method - because of this I thought the DRM keys would be fine (e.g. TrackId & Timescape still worked). However, when I was updating from GB .42 to .62 OTA (to flash a GB ROM) my phone bricked! (Does this mean the DRM keys weren't intact? Confused.)
So, I searched for a solution and ended up using s1tool to relock the bootloader. Then I used flashtool to flash a stock ICS ftf file. It seemed to work (the phone rebooted) but it was then I noticed that the SIM card wasn't being recognised. Also, in the Flashtool log I noticed that a blue line was there saying 'this file is ignored simlock.ta'.
Anyway, my real dilemma is - which of the Available Omnius Operations for the Xperia Ray (see link: http://www.omnius-server.com/phone?id=20… should I pick to fix this?
Backup TA
Flash
Identify
Live boot
Repair S1-boot
Restore TA
Revive phone after OTA flash
Unlock bootloader
Unlock network lock by certificate replacement
Repair S1boot? Restore TA? I really don't know. Would really. really appreciate someone's help - I need my phone back urgently!
Updating via OTA on an unlocked bootloader does lead to a bricked Phone, which just requires THIS to fix it.
XperienceD said:
Updating via OTA on an unlocked bootloader does lead to a bricked Phone, which just requires THIS to fix it.
Click to expand...
Click to collapse
Hi, thanks for your reply! I'm not sure what you mean though - the link provided in the first post on that thread took me to a dodgy website to download a file called 'downloadmanager
_setup' All that did was install crap like 'Zoomdownloader' and other non-android related rubbish on my computer. So I'm not best pleased about that...
Anyhoo, my phone isn't really bricked - it works fine apart from the SIM problem. I was asking what fix in the Omnius list of options applied to my situation. Do I need to Repair S1-boot? Do I need to 'Restore TA?' I really don't know to be honest.
All I really need to know is what option from Omnius's list applies to my situation...
seamo123 said:
Hi, thanks for your reply! I'm not sure what you mean though - the link provided in the first post on that thread took me to a dodgy website to download a file called 'downloadmanager
_setup' All that did was install crap like 'Zoomdownloader' and other non-android related rubbish on my computer. So I'm not best pleased about that...
Click to expand...
Click to collapse
Just checked the link myself, as it didn't skip the ad and asked you to download something else instead, that should have rang alarm bells. This is what you should have downloaded - FlashTool_0.2.9.1_FOTAUnbrick
seamo123 said:
Anyhoo, my phone isn't really bricked - it works fine apart from the SIM problem.
Click to expand...
Click to collapse
Your Phone was bricked in the first place due to an OTA update, and should actually state in what ever thread you used to unlock not to use the OTA feature after doing so, the attachment normally fixes that, given that you've re-locked using S1Tool then you may have done more harm than good. If I knew what option to suggest I would have done so, so unless anyone else does then it's trial and error I'm afraid.
Is it too late for me to give the link you gave me a shot then? Or might it do more harm than good at this stage? Thanks for your help btw, I appreciate it.
seamo123 said:
Is it too late for me to give the link you gave me a shot then? Or might it do more harm than good at this stage? Thanks for your help btw, I appreciate it.
Click to expand...
Click to collapse
You could try to unlock the boot loader again, flash stock ICS and kernel and try again to connect the sim card...
Or have you tried PC companion to fix your phone? Try this first!
But I can't promise anything, maybe you will end up in a bigger problem than now
Sent from my Nexus 7 running Android 4.2.1
Since it looks like I can't unlock the boot loader on my model I am thinking about returning my tablet and getting a different model or looking into warranty options. In either case I would need to have unrooted the tablet. The problem is that nothing I try seems to work. A factory reset doesn't unroot it. SuperSU unroot option doesn't work. Universal Unroot Tool doesn't work either.
I was partially rooted with Towel Root and then fully Rooted with Easy Root. What are the steps I can take to reverse it?
Elliander said:
Since it looks like I can't unlock the boot loader on my model I am thinking about returning my tablet and getting a different model or looking into warranty options. In either case I would need to have unrooted the tablet. The problem is that nothing I try seems to work. A factory reset doesn't unroot it. SuperSU unroot option doesn't work. Universal Unroot Tool doesn't work either.
I was partially rooted with Towel Root and then fully Rooted with Easy Root. What are the steps I can take to reverse it?
Click to expand...
Click to collapse
Just flash your stock firmware via latest Flashtool or Sony pc Companion.
kulvertti said:
Just flash your stock firmware via latest Flashtool or Sony pc Companion.
Click to expand...
Click to collapse
Not possible. First of all, I am on stock firmware, and second of all the Sony PC Companion doesn't work with SGP561. It specifically tells me to use the "Verizon Software Update Tool", but Verizon refuses to tell me where this is because I am not a customer and none of the old versions I could find work. Since I couldn't use Sony PC Companion I couldn't create a TFT image to begin with and although I can use Flashtool I would need one of the stock firmware SGP561_17.1.D.0.417 that is also Verizon locked or it will fail, but since I can't create a TFT image with Sony PC Companion the likelihood of finding one that works is low. Hypothetically though if I could find that exact stock firmware I could flash it and everything would go back to normal. (Unbranded firmware fails, BTW, and since the bootloader can't be unlocked on my model custom firmware isn't possible either)
I called Sony to find out where the required Verizon Software is located and they said it will take a day or two for researching the problem. No one seems to know anything about it.
Elliander said:
Not possible. First of all, I am on stock firmware, and second of all the Sony PC Companion doesn't work with SGP561. It specifically tells me to use the "Verizon Software Update Tool", but Verizon refuses to tell me where this is because I am not a customer and none of the old versions I could find work. Since I couldn't use Sony PC Companion I couldn't create a TFT image to begin with and although I can use Flashtool I would need one of the stock firmware SGP561_17.1.D.0.417 that is also Verizon locked or it will fail, but since I can't create a TFT image with Sony PC Companion the likelihood of finding one that works is low. Hypothetically though if I could find that exact stock firmware I could flash it and everything would go back to normal. (Unbranded firmware fails, BTW, and since the bootloader can't be unlocked on my model custom firmware isn't possible either)
I called Sony to find out where the required Verizon Software is located and they said it will take a day or two for researching the problem. No one seems to know anything about it.
Click to expand...
Click to collapse
I could do it for you if you wish. Do you really want 417 ftf or newer 437 ftf file?
kulvertti said:
I could do it for you if you wish. Do you really want 417 ftf or newer 437 ftf file?
Click to expand...
Click to collapse
Before you go through that trouble wait a bit.
Since the Verizon tool I could find failed - rendering it half bricked waiting for a proper update - and since neither Sony nor Verizon knows anything about the tool I am required to use they are willing to accept the warranty service on it. I am fortunate that because the failed update wiped the data there is no evidence of it ever being rooted and since this model's boot loader can't be unlocked even if it is fried there is no evidence of me doing anything wrong with it. And it was Verizon's tool that did it, so it's an honest case.
Anyway, I sent them a screenshot from last night proving this tablet hasn't been unlocked and I am on the phone with Sony on hold to see if they would be willing to sell me an International version right now and then refund me when they receive it. Since I need it for college on the 25th (textbook replacement) and I have no problems paying upfront they seem to think it should be possible, but they are all sort of talking with each other about it to see if it really can be done. If they can I will be able to get rid of the Verizon mess permanently.
If not, getting that firmware update from you would be greatly appreciated. I'll edit this post when I know what's going to happen.
Elliander said:
Before you go through that trouble wait a bit.
Since the Verizon tool I could find failed - rendering it half bricked waiting for a proper update - and since neither Sony nor Verizon knows anything about the tool I am required to use they are willing to accept the warranty service on it. I am fortunate that because the failed update wiped the data there is no evidence of it ever being rooted and since this model's boot loader can't be unlocked even if it is fried there is no evidence of me doing anything wrong with it. And it was Verizon's tool that did it, so it's an honest case.
Anyway, I sent them a screenshot from last night proving this tablet hasn't been unlocked and I am on the phone with Sony on hold to see if they would be willing to sell me an International version right now and then refund me when they receive it. Since I need it for college on the 25th (textbook replacement) and I have no problems paying upfront they seem to think it should be possible, but they are all sort of talking with each other about it to see if it really can be done. If they can I will be able to get rid of the Verizon mess permanently.
If not, getting that firmware update from you would be greatly appreciated. I'll edit this post when I know what's going to happen.
Click to expand...
Click to collapse
Okey buddy. However I allready make ftf file for your but it is Verizon 417 stock. Let me know if you need Verizon 437 firmware.
Here is the link need it or not:
https://mega.co.nz/#!UJJEAR5B!tK7pQEeppCmTQKxSA0tEL5_W3A7o_q6dsn3FXh43LYA
kulvertti said:
Okey buddy. However I allready make ftf file for your but it is Verizon 417 stock. Let me know if you need Verizon 437 firmware.
Here is the link need it or not:
https://mega.co.nz/#!UJJEAR5B!tK7pQEeppCmTQKxSA0tEL5_W3A7o_q6dsn3FXh43LYA
Click to expand...
Click to collapse
Thanks. At the very least that will help the next person with a problem.
Sony was willing to sell me an SGP512 model and is going to process a refund for what I paid on the SGP561. That's a better solution anyway since I'm not on Verizon's network - especially since Verizon doesn't support it. I paid for expedited shipping so I will get it in 2 days and I won't need to deal with any Verizon apps. I paid for 3 year extended warranty as well which covers all damage so as long as I dont't mess with the boot loader I shouldn't have any problems with it.
To anyone else reading this: Avoid the factory unlocked SGP561! It's a nightmare!
kulvertti said:
Okey buddy. However I allready make ftf file for your but it is Verizon 417 stock. Let me know if you need Verizon 437 firmware.
Here is the link need it or not:
https://mega.co.nz/#!UJJEAR5B!tK7pQEeppCmTQKxSA0tEL5_W3A7o_q6dsn3FXh43LYA
Click to expand...
Click to collapse
I wanna return it to stock and unroot it how do i know if i need 417 or 437?
I own a registered (with Xperia Care [warranty]) Z5C E5823 phone. This phone was purchased from eBay US, but I believe the phone came from China as I had to manually switch from Chinese to English during the first initialization. Although at the time I got this phone (mid 2016), several build and android version updates existed, mine never updated. It is still stuck with Android 5.1.1, build 32.0.A.4.11, kernel 3.10.49-perf-g6b847e2. The phone, PC companion and everything else claims it's the latest update/version for the E5823.
I wanted to know what is happening and how to solve this. The phone is completely stock. Never rooted.
Thank you.
Thats why i payed extra 300$ to Sony
(my previous SONY was from alternative store, although the phone still was real and not fake replica it didnt get OTA updates so i had to used flashtool to update)
anyway you dont lose much.. wait for android 7 and update from flashtool
you can try use sony site to see if you supposed to get update
http://support.sonymobile.com/global-en/xperiaz5/software/
Superrman said:
wait for android 7 and update from flashtool
you can try use sony site to see if you supposed to get update
http://support.sonymobile.com/global-en/xperiaz5/software/
Click to expand...
Click to collapse
I've noticed something strange... I went to the link provided and inserted my IMEI number. The website claimed I have the latest version of everything, "as usual". But it showed the following message: "Your Xperia™ Z5 is up to date! 32.0.A.7.3.
That's not my build number and it also claims my phone as a Z5 and not Z5C. I don't know if this is relevant or not, but definitely strange.
Anyways, I believe that to use this flashtool I would have to root the phone. In this case I'm a bit concerned as the first android I ever tried to root was bricked instead. So I try to stand clear of doing that as I've been traumatized by my experience hahahahahaha. Well, unless there is a step-by-step-foolproof-recipe solution, I don't want to risk bricking my phone or voiding warranty (still in effect) if an update to marshmallow is not all that great.
l_abaurre said:
I've noticed something strange... I went to the link provided and inserted my IMEI number. The website claimed I have the latest version of everything, "as usual". But it showed the following message: "Your Xperia™ Z5 is up to date! 32.0.A.7.3.
That's not my build number and it also claims my phone as a Z5 and not Z5C. I don't know if this is relevant or not, but definitely strange.
Anyways, I believe that to use this flashtool I would have to root the phone. In this case I'm a bit concerned as the first android I ever tried to root was bricked instead. So I try to stand clear of doing that as I've been traumatized by my experience hahahahahaha. Well, unless there is a step-by-step-foolproof-recipe solution, I don't want to risk bricking my phone or voiding warranty (still in effect) if an update to marshmallow is not all that great.
Click to expand...
Click to collapse
As long as you are flashing an official ROM with flashtool, you don't need to root your phone.
I was sick of waiting for my Z5 compact to get the OTA for whatever firmware I initially had, so I just flashed unbranded Nordic with no problem without being rooted.
There are a few threads here on XDA that will explain what you need to do to use flashtool.
The wrong IMEI and Chinese first boot screen suggests your phone came from shady sources, otherwise there's no reason for the discrepancy. Did you check and see if the IMEI number matches the one on the box?
If I were you, I'd seek out the ebay seller and ask for an explanation and refund or replacement, fraudulent IMEI's are no joke, I mean what if the IMEI is reported stolen? You'd probably get tracked down and paid a visit by unpleasant people or something. Sure, you'd likely be able prove your innocence, but not worth the risk or hassle IMO. Then again, you have been using it for half a year already, chances are nobody's going to bother you, ever.
It's possible that the mismatch is the reason why you never got an OTA update notice. Like other members have suggested, you can use flashtool to flash the latest firmware, but it's certainly not as easy and painless as an OTA update. Going down the road, I don't think you'll ever get to update OTA with your device, so if you want to hang on to it and keep it up to date, learn how to download official firmware using xperifirm, convert to FTF and flash using Flashtool .
Next time, buy from credible and reputable vendors.
Thanks for the reply guys. Unfortunately, there was no suspicion at the time about the phone being "fake" or something like that. But after this IMEI situation and this problem as well (worth checking), I'm kinda suspicious. I don't have the box with me, I'll only be able to compare this in february, as I'm abroad. But I've registered my phone with Sony and I didn't have any problems. I even have the limited warranty available.
By the way, can this warranty be used to replace the phone in a case like this? Even considering the LED issue mentioned in the link above?
I guess I'll have to educate myself about flashing firmware with flashtool. I don't mind the extra hassle, as long as I don't brick the phone.
l_abaurre said:
Thanks for the reply guys. Unfortunately, there was no suspicion at the time about the phone being "fake" or something like that. But after this IMEI situation and this problem as well (worth checking), I'm kinda suspicious. I don't have the box with me, I'll only be able to compare this in february, as I'm abroad. But I've registered my phone with Sony and I didn't have any problems. I even have the limited warranty available.
By the way, can this warranty be used to replace the phone in a case like this? Even considering the LED issue mentioned in the link above?
I guess I'll have to educate myself about flashing firmware with flashtool. I don't mind the extra hassle, as long as I don't brick the phone.
Click to expand...
Click to collapse
You can't go to Sony and ask them to replace it. Ok, you can always try, but based on normal warranty, they won't replace it.
In your case, it's up to the dealer/store to fix your problem with IMEI, maybe a faulty ROM and so on. Or you can flash the update yourself
--jenana-- said:
You can't go to Sony and ask them to replace it. Ok, you can always try, but based on normal warranty, they won't replace it.
In your case, it's up to the dealer/store to fix your problem with IMEI, maybe a faulty ROM and so on. Or you can flash the update yourself
Click to expand...
Click to collapse
It's been a while since I've bought the phone, so I don't believe the vendor will do much.
I've read about the process of flashing the firmware. The only thing I did not understand is about the selection of the firmware itself. I'm presented with a list of firmwares of various countries (market) and carriers (operator) in XperiFirm. How do I know which one to select? A natural choice would be to select one from my region/carrier, but I can't find any or both for my phone. The guides I found doesn't elaborate on this.
Another thing. Will a simple backup with Xperia Companion or Factory Reset (from the phone itself) revert to the original firmware? Do I need to create a backup firmware?
Ahh, so the weird LED color thingy was you too. Your phone is off the charts fishy.
Your vendor should definitely be held accountable, try negotiating first. If things go sour, threaten to sue and see if they change their tune.
You select the firmware from your region, and don't select the carrier branded firmware, they're for locked phones sold by carriers, one normally wouldn't want to use that.
If I'm not mistaken, what you're trying to ask is if you're currently on firmware version A and flash version B, could you revert back to version A using Xperia Companion or via the factory reset, correct? The answer is no. You can however use Flashtool to flash version A regardless of what version firmware is currently installed on your phone, but I'm not sure if it's advisable to retain user data when you downgrade firmware.
Usually there's no need to make a backup of the original firmware. The factory reset function is basically just a data wipe, firmware version doesn't change. You should always backup your personal files before attempting to flash a firmware just in case. Personally I use Sony's preinstalled Backup and Restore app, it works for me - don't backup apps though it's pointless, takes up too much time and free space and is basically redundant. If you want to make a backup of the entire phone including the firmware, you will need a custom recovery solution like TWRP, but in your case I don't think you'll need to go that far, it's more stuff to learn and potentially go wrong.
mhaha said:
You select the firmware from your region, and don't select the carrier branded firmware, they're for locked phones sold by carriers, one normally wouldn't want to use that.
Click to expand...
Click to collapse
By region you mean the region I live or the region of the original firmware? I matched the CDA of the one that shows on the cellphone with one on the list of available firmwares. Not surprisingly, it shows that it is from Hong Kong and "customized HK" as operator. Intuition says I should try and flash that one...
So, usually backing up your current firmware is not needed/common?
Depends on what you're doing, because you're just upgrading and not messing with custom ROMs or kernels or whatever, then yeah you don't need to backup the entire phone/firmware, just backup your data.
I suggest picking the region you're living in, although it doesn't really matter since you can always change your language and uninstall/disable any localized apps. For example if you're in Russia, then you'd probably prefer the default search engine set to Yandex and local Russian apps preinstalled; or if you're in China, then you'd want Baidu instead and Chinese specific apps... etc. Or another possibility, US-based firmware may have the DST setting enabled by default, but nothing you can't change afterwards.
mhaha said:
I suggest picking the region you're living in, although it doesn't really matter since you can always change your language and uninstall/disable any localized apps.
Click to expand...
Click to collapse
I live in Brazil but I travel to the US all the time. I didn't find any firmware from these locations for my phone. So judging from what have I read so far, I can pick whatever as long as it's not carrier locked or something like that.
So I guess I'll pick whichever firmware is the most recent from the list and cross my fingers...
Just to give an update to whomever it may concern. I've decided to flash an Australian firmware (I belive it was the most recent one) after some more reading.
Although flashtool failed to flash the first time, I just repeated the process step by step and it worked like a charm the second time.
Although my backup didn't do much (I've deleted EVERYTHING from my phone, as recommended) everything worked and the phone is up to date.
Now I'm waiting for the Nougat!