[Q] Samsung GT-i9000B - camera 'die' after firmware update - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi,
I´m reading for hours some (why not say many) threads here in this forum regarding camera firmware update and camera that doesn´t work anymore after that. So, I have some questions:
- Is there a way to came back the camera to work?
- Why some users say 'go to dealer/carrier service team'? What this guys do that we cannot to do?
- Why the 'firmware update' button is available since it kills the camera??? It´s a guilty of Google/Android or Samsung?
- After read, I´m not sure but seems that this issue affect not only the 'Galaxy S GT-i9000' but other models also, is correct?
* I work with IT for 20 years and I like to have my systems updated with the last firmware/patches that in 99,9% of time fix some bug/issues - I never saw that kind of issue - only for cases where you run the firmware update file for a incorrect device/model. But what to say to a button that - supposedly - try to get your device model and then check for new firmware version????
Today my camera show the following info after press *#*#34971539#*#* and choose the first option "Phone/CAM FW Ver Check":
[SESBEDI07:
SESBEDI07:
NONE]
tks,
Renato P
PDA: I9000BVJJW4
Phone: I9000BVJJW2
CSC: I9000BZTAJW2

If you mean the update on Samsung apps store, thats for SGS2.
Sent from my GT-I9000 using Tapatalk

At this situation (camera crashes after ugdate) samsung replace camera to new one. I had same problem.
Wysłano z GT-I9000 z użyciem Tapatalk

jr3151006 said:
Hi,
I´m reading for hours some (why not say many) threads here in this forum regarding camera firmware update and camera that doesn´t work anymore after that. So, I have some questions:
- Is there a way to came back the camera to work?
- Why some users say 'go to dealer/carrier service team'? What this guys do that we cannot to do?
- Why the 'firmware update' button is available since it kills the camera??? It´s a guilty of Google/Android or Samsung?
- After read, I´m not sure but seems that this issue affect not only the 'Galaxy S GT-i9000' but other models also, is correct?
* I work with IT for 20 years and I like to have my systems updated with the last firmware/patches that in 99,9% of time fix some bug/issues - I never saw that kind of issue - only for cases where you run the firmware update file for a incorrect device/model. But what to say to a button that - supposedly - try to get your device model and then check for new firmware version????
Today my camera show the following info after press *#*#34971539#*#* and choose the first option "Phone/CAM FW Ver Check":
[SESBEDI07:
SESBEDI07:
NONE]
tks,
Renato P
PDA: I9000BVJJW4
Phone: I9000BVJJW2
CSC: I9000BZTAJW2
Click to expand...
Click to collapse
Basically, you have two types of cameras in SGS. Easy to recognise looking on the lens: green(worse) violet(better).
I have green one, I did exactly what you have done: I killed cam totally by firmware upgrade.
Yes, I found solution, here. But: it was related with hours of digging, flashing and manual files replace with ghost commander.
So: no, going to service is LAST option, but I do not remember now what I did... most likely: I found somewhere OLD firmware file, and I replaced it. If I remember good, I followed: http://forum.xda-developers.com/showthread.php?t=1263151 --> http://forum.xda-developers.com/showthread.php?t=1032437 and it was ended with success. BUT: you need root, file manager, busybox and... your cam firmware will be downgraded.
So, search xda SGS after camera firmware... or go to service.

Hi,
can someone tell me if I did something wrong? I already have root access and removed 4 files from /system/app as 'theosos' from that article (http://forum.xda-developers.com/showthread.php?t=1263151) and expand the file 'camera.rar' for replacement >>>> no luck!
I used the 'Check Fus Downloader' from the that article (http://forum.xda-developers.com/showthread.php?t=1032437) to download, decript and then send to my phone using ODIN >>>> no luck also!
* I also tried to run these .APK files but during install show an warning msg that it 'is not installed'.
** Can be it related with Android versions? Like I´m trying to copy camera.apk from 'froyo 2.3.4' to my system running '2.3.3'?
*** My camera is 'green' lens.

Now my phone info changed to:
PDA: I9000BVJJW4
Phone: I9000BVJJW2
CSC: I9000BZTOJW4

CAMERA FIRMWARE INFO
[CAM FW(05.15)PRA(05.15)AF(35.34)HONE FW(05.15)PRA(05.15)AF(35.34)]
PHONE FW Version
[SESBEDI07]

I found similar issue, I tried to replace .bin files but still no luck
http://www.samsunggalaxysforum.com/firmware-problems/camera-fail-error!-please-help!/45/

after access screen test menu (*#*#0*#*#*), my front camera works fine but the back camera shows only colored lines:
gray
yellow
cian
green
purple
red
blue

after service mode (*#197328640#)
My HD ver: MP 0.600
FTA SW ver: I9000B.010
FTA HW ver: rev1.0
CL NUMBER: 1006697

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
problem fixed
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I downloaded firmware files for SamsungWave and reflash from phone to CAM and now works fine!!!!!!!!!!!!!!!!!!!!!!!!!
* I followed instructions from that article: http://www.samfirmware.com/apps/for...000-camera-failed-after-phone-to-cam-fw-write
* both Front and Back Camera works fine.

Related

Camera Fimware Menu (Who has the latest one so we all flash it!)

To enter the Camera Firmware menu, in the dialer press:
*#34971539#
This are the options displayed:
- Phone/CAM FW Ver Check
- Phone to CAM FW Write
- ISP Ver Check
- FW Write Count
- CAM FW Cal Check
- CAM to Phone FW Dump
This is what comes when i click on Phone/CAM FW Ver Check
[ SESBDE14:SESBi?27:NONE]
ok seems i downgraded with the new JP2... cause i flashed (Using phone to cam fw write) and now reads (camera still works!):
[ SESBDE14:SESBi?14:NONE]
i made a dump before, gonna look where is it stored
PS: im not responsible for any kind of damage to your phones, so be careful!
So far then (thanx for the collab):
JM5 : SESBDE14:SESBi?27:NONE
JM6 : sesbde14:sesbde14:none
JP2 (New) : SESBDE14:SESBi?14:NONE
JPC : SESBDE14:SESBi?14:NONE
JF3 : SESBDE14:>?SBi?07:NONE
JH2 : SESBDE14:SESBDE27:BDE
So far Its clear it begins with SESBDE14... then there's the BDE and Bi? with a number, and one finishes with BDE
need more info for more insights
Maybe posting the build date of the roms?
If this is like old Samsung were... like D600... E900, then each firmware has their Camera Firmware included, but it's not flashed automatically...
i'd like to know about other Galaxy S users... maybe we can get to determine which fw has the better CAM FW
Camera is pretty ok.. but they need to add image stabilization
JP3 phone fw
FW CAM [SESBDE14:>?SBi?07:NONE]
ISP [NEC CE147]
hi,
on jm5 you get
SESBDE14:
SESBDE27:NONE
Cheers,
anthony
On JH2, you get
SESBDE14:SESBDE27:BDE
BackfireNL said:
Camera is pretty ok.. but they need to add image stabilization
Click to expand...
Click to collapse
is image stabilization not anti-shake?
regards
Jm6 sesbde14:sesbde14:none
I upgraded to the new JP2 and I still get SESBDE14:>?SBi?07:NONE like in the JP3
i suppose we need to dump those fw's and compare
make a cam fw to phone dump, it takes approx 2min and label it, then you can upgrade to newer ones with phone to cam fw write, but we should check what's really inside before blind flashing that I suppose.. otherwise SESBDE14:SESBDE27:BDE is prolly "newest" oO
JM1 REV 3:
sesbde14:sesbde14:none
Bell Stock JG9
SESBDE14:SESBDE27:NONE
bilboa1 said:
I upgraded to the new JP2 and I still get SESBDE14:>?SBi?07:NONE like in the JP3
i suppose we need to dump those fw's and compare
make a cam fw to phone dump, it takes approx 2min and label it, then you can upgrade to newer ones with phone to cam fw write, but we should check what's really inside before blind flashing that I suppose.. otherwise SESBDE14:SESBDE27:BDE is prolly "newest" oO
Click to expand...
Click to collapse
yeah if you have not flashed it via this menu, you'll have the camera firmware of the phone firmware it came with originally
What will flashing the newest one improve?
Image quality?
Pictures are pretty blend...especially in low-light conditions (artificial lighting present)
here's mine
JG4 :SESBDE14:SESBDE14:NONE
I9000DTJG4 gives 'SESBDE14:SESBDE27:NONE'
I've done a firmware dump... but am unsure as to where it created the dump file(s).... any insight?!
Don't know if it's firmware or hardware, but my Camera don't work correctly, after some Odin Flash and some Camera FZ Flash.
Any ideas?
JPC = SESBDE14:SESBi?27:NONE
[SESBDE14:SESBDE14:NONE]
my firmware = ECLAIR.ZSJH1
Sent from my GT-I9000 using XDA App
JPC
ISP = [NEC CE147]
Camera firmware info= [SESBDE14:
SESBi?14:
NONE]
Check cal status
AF(35.34)
SHA(02.16)(02.119)
SHU(NONE)

Omnia7 no brand no logo firmware update

Hey guys, i'm receiving official firmware update(i think because it's called samsung update) via zune just right now. I didn't even expect it!
updating................
Uploaded with ImageShack.us
you are on Mango relase, correct? .... maybe InternetSharing update
Normaly before ZUNE install the update, the make a Backup to restore the pre relase.
If yo unsure, try this backup solution here
[APP] simply 100% BACKUP your phone - to 100% RESTORE over ZUNE
and try this update ......
finished, rebooted, then downloading another update, when rebooted the 1st time remained at least 2 minutes stuck at samsung omnia7 boot logo, if you are scared go have a walk in other rooms of your house, do your bed, clean up the mess, it worked for me
Uploaded with ImageShack.us
please let us know the firmware, bootloader radio version when its done plz!
Updating my phone right now !! Unbranded, dev/intertop unlocked omnia 7. will post updates shortly.
yes mirolg, i'm on mango, and i hope it is
and yes, zune did a backup before proceding! no worries, I hope i'm safe
thanks
and for the others, yes, i'm waiting it to finish to see what happens and post here the chnges
thanks for replies and happy updating
ok, done but no internet sharing, no option in settings
firmware is 2424.11.9.2 and before i was 11.8.5
hardware 3.15.0.4
radio software 2424.11.9.1
hardware radio 0.0.0.800
bootloader 5.9.0.6 i think it changed this also
SOC 0.36.2.0
that's it guys!
DJBlaster-303 said:
ok, done but no internet sharing, no option in settings
firmware is 2424.11.9.2 and before i was 11.8.5
hardware 3.15.0.4
radio software 2424.11.9.1
hardware radio 0.0.0.800
bootloader 5.9.0.6 i think it changed this also
SOC 0.36.2.0
that's it guys!
Click to expand...
Click to collapse
very confused over this update practice
I have ever thought a un-braded ROM are the better choice ....
My Omnia 7 is a t-mobile "light" branded device. before come the officially MANGO i have it flash it with a un-branded ROM. But it had a older firmware + no InternetSharing.
so i have few weeks ago my device flash with the t-mobile ROM. I`M now pleased with it and happy over the InternetSharing function ...
I have few WiFi only (tablet) devices and wouldn be without this great future .......
yes the T-mobile ROM KH2 posted on mobiletechworld will persuade Zune to upgrade it to
radio 242.11.9.1
firm 242.11.9.4
bootloader 5.9.3.0
internet sharing & compass works perfectly now !
I had issues with the Data connection on Orange UK , but used the Samsung app "network profiles" to switch from T-mob de and it's all good.
I think the reason that the non-branded ones are lacking is, that not all carriers want internet sharing enabled.. so the generic one doesn't get it.. also I suppose the cost of testing it has to be paid by someone.. T mobile in this case
johnny.g said:
radio 242.11.9.1
firm 242.11.9.4
bootloader 5.9.3.0
internet sharing & compass works perfectly now !
Click to expand...
Click to collapse
hi , i have the same relase as you, but i have no good working compass
which compass you use?
cheers, miro
my version with diagnosis now:
PDA: I8700XXKI2
Phone: I8700XXKI1
CSC: I8700ITVKI2
and btw if you really need internet sharing you could enable it using diagnosis on a unbranded phone
just follow this guide on mobiletechworld and keep in mind you have to revert to zune sync when you want to use zune again
thanks
Just recieved these updates too, no Interner Sharing either.
In fact I see no difference other than build numbers?
Ex UK T-Mobile Omnia 7
Sim Unlocked
Un-Branded
Before:
PDA:I8700XXKH5
Phone:I8700XXKG2
CSC:I8700XEUJL3
OS:7.0.7720.68
Firmware:2424.11.8.5
Radio Software:2424.11.7.2
Bootloader:5.8.1.9
After:
PDA:I8700XXKI2
Phone:I8700XXKI2
CSC:I8700XEUKI2
OS:7.0.7720.68
Firmware:2424.11.9.2
Radio Software:2424.11.9.1
Bootloader:5.9.0.6
I am wondering why my phone version is ki1 and not ki2 could someone enlighten me, please?
Hmm well, my Omnia 7 differs from all of yours.
Seems like you are struck without Internet Sharing and on Mango 7720.
Ever though about flashing the firmware to a newer version? Or using a ROM from another carrier?
Mine is a Omnia 7 with T-Mobile Germany Branding and I had received Internet Sharing together with Mango 15 days ago.
I even received a few hours ago another new update, which changed the OS version to Mango 7.10.7740.16.
I already announced it on forums here (screenshot and version numbers there):
http://forum.xda-developers.com/showthread.php?t=1349495
the thread title is "omnia7 no brand no logo firmware update" how did u understand your t-mobile germany omnia7 is different from ours???
thank you for the completely off topic post, we are able to read the forum I think
I successfully set up connection from my laptop with my unbranded omnia7 and found a little error on mobiletechworld guide using it
so here's step by step for my case: samsung gt-i8700 and wind ITA carrier with windows7 home premium x64
phone version:
PDA: I8700XXKI2
PHONE: I8700XXKI1
CSC: I8700ITVKI2
1:dial ##634# and press call to enable diagnosis menu
2: in diagnosis menu dial*#7284# and select the middle option: Modem, Tethered Call, and reboot phone as asked
3: Download and install http://www.multiupload.com/GH391NDSY1 and don't mind the Verizon branding on install wizard
4: connect the phone with usb cable to the laptop and wait for driver install, and check in device manager; you should see Samsung mobile modem
Uploaded with ImageShack.us
you could also double click and go in properties --> diagnostics --> and press query modem to se if replies correctly
5: now go to http://www.2shared.com/file/_Ty7WFZ7/WINDEasyConnect_20100111.html and download wind easy connect and install; be sure to not select any drivers during installation
6:wind easy connect then will detect the omnia7 and asks if he should use it, say yes and voilà, you can now use the auto-configurable dialer to connect with omnia7 and surf happily
Uploaded with ImageShack.us
be sure to check if you have a data plan that permits the use of cell phone as a modem(i asked call center) i'm not responsible if you don't check and have then to pay a lot of phone bill
and remember that omnia7 is not officially supported by wind ita
sorry for my bad english
hi guys n gals,
received official open market phone 7740.16
fw: 2424.11.9.2
hw: 3.15.0.4
radio sw: 2424.11.9.1
radio hw: 0.0.0.800
bootloader: 5.9.0.6
diagnosis version is the same
didn't notice improvements yet...
ttyl
DJBlaster-303 said:
hi guys n gals,
received official open market phone 7740.16
fw: 2424.11.9.2
hw: 3.15.0.4
radio sw: 2424.11.9.1
radio hw: 0.0.0.800
bootloader: 5.9.0.6
diagnosis version is the same
didn't notice improvements yet...
ttyl
Click to expand...
Click to collapse
Just received the update. Developer unlocked, unbranded Omnia 7. No internet tethering :-?? I don't see any improvements either.
i noticed that battery now lasts longer, and phone seems smoother and quicker, not bad!!

Tab 8.9 P7300 terribly messed up - Sort of urgent help neede (someone kill me now)

Hello,
I am not new to flashing stuff on android devices, but new to dealing with this tablet.
I was looking to find an old firmware that would support GSM voice calls as seen on that well-known gsmarena.com video that shows it.
I was running the latest available Clockworkmod recovery as found in the development section and on top of that - [4.1.1][PORT][P7300/P7310] AOSP Android 4.1.1 Stable[11-08-2012]
So I fired up Odin 1.85 and downloaded the oldest available Open Europe firmware (Honeycomb 3.1) available on sammobile.com
The result was the tablet's screen would not light up but it would still have the Samsung boot sound and the short vibration that notifies of the OS startup. The display is black, nothing shows up but the tablet is indeed running.
I am still able to enter Bootloader/Download mode by guessing the time it takes to get there but flashing more recent firmwares from sammobbile is not helping. Still no display.
Any ideas on how badly I managed to f*ck this up?
Edit: Could an old firmware version have fried the display? nothing I manage to flash gets it running... this is so bad.
Edit: Oh wait, the display actually works, but only displays distorted images, a pile of pixelated garbage.
zohmygoodness
Edit: Really, would someone please try and dump their bootloader using ADB shell?
The Open Europe region firmware I flashed and caused the problem has a bootloader in the package so this must be the reason the display is not properly initialized.
Could someone knowledgable enough please provide an ODIN flashable 3.2 bootloader for Tegra 2 P7300 - I do not know if it is possible to dump it from a device. I really need your help.
I am currently downloading almost every 3.2 ROM available on sammobile.com in search of a bootloader.
RESOLVED
Okay, I managed to bring the tab back to life - it only cost me a one month subscription to Hotfile Premium in order to be able download all available firmwares from sammobile.com and search for one that comes with a bootloader.bin.m5
The solution came with Hong Kong. The following firmware release contains a working 3.2 bootloader for the Galaxy Tab 8.9 GT-P7300: should someone ever (and I hope they never) end up in the same situation as me:
Cant post links just yet. Simply visit sammobile.com, do a search for P7300 and download the 3.2 firmware for Hong Kong

[Q] Ativ-S - DP - Still on old firmware?

Hi,
Device is Ativ-S i8750 bought through Handtec. Operating on GiffGaff UK PAYG.
OS 8.10.14203.306
FW: 2424.13.10.1
CSC : XEF
I've searched around and found a little info about the problems with my camera since installing the 8.1 update through developer preview. Apparently it's fixed in firmware update 2424.14.9.3 which came out around October last year.
While my phone has picked up OS update, I don't seem to have picked up any firmware updates four months down the line.
I've have searched to find out what to do next but I am a bit stuck and unsure what to do next. So hope this community can help. Is there anything I should be doing to get this update other than just waiting?
Thanks!
Smoothound said:
Hi,
Device is Ativ-S i8750 bought through Handtec. Operating on GiffGaff UK PAYG.
OS 8.10.14203.306
FW: 2424.13.10.1
CSC : XEF
I've searched around and found a little info about the problems with my camera since installing the 8.1 update through developer preview. Apparently it's fixed in firmware update 2424.14.9.3 which came out around October last year.
While my phone has picked up OS update, I don't seem to have picked up any firmware updates four months down the line.
I've have searched to find out what to do next but I am a bit stuck and unsure what to do next. So hope this community can help. Is there anything I should be doing to get this update other than just waiting?
Thanks!
Click to expand...
Click to collapse
rather annoyingly the only way I got it was to flash back to GDR2 and work upwards. Royal pain in the arse if im honest but I got there in the end, I believe it was disabled in some of the CSC images that were flashed because upgrading to it also disables some of the ability to unlock the device. As much as I liked the idea of it being unlocked I didn't make any real use of it so decided to bite the bullet and flash it back an upgrade, several hours later, back on DP with a working camera and a more stable Bluetooth stack!
___
dazza9075 said:
rather annoyingly the only way I got it was to flash back to GDR2 and work upwards. Royal pain in the arse if im honest but I got there in the end, I believe it was disabled in some of the CSC images that were flashed because upgrading to it also disables some of the ability to unlock the device. As much as I liked the idea of it being unlocked I didn't make any real use of it so decided to bite the bullet and flash it back an upgrade, several hours later, back on DP with a working camera and a more stable Bluetooth stack!
Click to expand...
Click to collapse
Thanks for the reply, man. Sorry for my slow response.
I was hoping there was another way around this. Thanks anyway!
Is there a total n00bs guide to flashing an Ativ-S back to GDR2?
EDIT : I found this : http://forum.xda-developers.com/showthread.php?t=2391138&page=11 - but looks like the ROMs are no longer up
I have the same problem, but am still on firmware 2212.13.11.2 (and hardware 15.3.1.0, bootloader 13.08.14.16). Phone is a SGH-T899M by the way. Because of PfD my OS is 8.10.14203.306, which is recent. Disabling PfD doesn't make my phone upgrade the firmware, nor did it when my OS was a few months older.
It might be that in this thread (http://forum.xda-developers.com/win...aylors-super-rom-tool-dump-sgh-t899m-t3037789) the solution can be found to downgrade but there's a bit too little step-for-step instructions for me to do it. If someone can give them to me (or a different solution to force my phone to upgrade firmware), then I'd be thankful!
EDIT: in the ATIV SE (thanks to the author) thread there's a how-to 'hidden' in the download. It goes as follows:
1. If you have not done so already, extract the .zip file that this is contained in and ensure that you are working from the unzipped folder
2. Install SamsungUSBDriver.msi and restart
1b. If you have Windows 8.1 x64 you need to disable driver signature verification first:
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
3. Extract the file SM-W750V_VRU0ANC2_R_signed_2.zip
4. Power off device (and leave it unplugged)
5. Open the file WP8_Binary_Downloader_Ver._3.54.exe
6. Click the yellow/orange folder and Open the file SM-W750V VRU0ANC2_R_signed.wp8
7. Click the green folder and Open the file SM-W750V_VRU0ANC2_R.csc
8. Boot into Download Mode (hold Vol. Up and Home buttons while device is powering on)
9. Plug in your phone
10. If it shows up in the Channel Information section and does not report an error, you are ready
11. Last chance to consider saving your data
12. Press start
13. Wait until it has completely finished and your phone has rebooted
14. Skip through initial setup, go to Settings > about, and reset your phone once before using it
15. Enjoy stock!
I guess this should be the same for other phones, but you have to exchange the file with the file for your phone as given in the taylors-super-rom-tool-dump thread. Ofcourse, no guarantees, this is what seems logical with my limited knowledge
Hi Guys,
Just to let you know - I managed to flashed with GDR2 - file GTi8750-OXABME1_R.
It wouldn't update to 8.1 until I changed CSC from XEF to ATO, then it picked up the new firmware and 8.1. It just finished installing a few moments ago.
So I am now on :
Software: Windows Phone 8.1 Update
OS version: 8.10.14157.200
Firmware: 2424.14.9.3
I have tried checking for more updates and now I am getting error 80072f8f, which apparently it time related, even though time is correct. Same after a reboot. So not sure if I'll get any futher updates till I can work around this.
How far am I off the most current OS version for ATIV?
EDIT : Took a punt that it was the CSC that was causing the time problem. So switched CSC to BTU (which apparently is UK. British Telecom maybe?) - and it's now saying it's downloading updates!! \o/
EDIT : The phone reinstalled, did the gears. But OS version is unchanged. I do however have a newer firmware still: Firmware revision number: 2424.15.3.2

Can't Update System Software

I just got brand new Xperia X Performance that came with 6.0.1, and I'm trying to figure out why I can update it. It's unlocked but not rooted, basically right from the factory as far as I know.
When I go into Software Update in the phone's settings, it says "Your device already has the latest available system updates."
When I use the Sony app on my PC it says my system software is up to date.
I actually can't find anything about this issue, anybody here have any ideas?
Thanks!
try downloading and running xperifirm, find out if your region has the update at all, you should be able to update atleast to 7 anyway
There are a few variants that are considered as internal units or something like that and they don't get OTA updates, also HK units were stuck on 7 for some reason last time I checked. Mine is a french model, and yesterday I received the april security patches while the global variant got it two months ago
st3ch said:
try downloading and running xperifirm, find out if your region has the update at all, you should be able to update atleast to 7 anyway
There are a few variants that are considered as internal units or something like that and they don't get OTA updates, also HK units were stuck on 7 for some reason last time I checked. Mine is a french model, and yesterday I received the april security patches while the global variant got it two months ago
Click to expand...
Click to collapse
Thanks for the reply.
Here's a screenshot of Xperiafirm. https://ibb.co/dUCN3T
I'm in Canada, though I'm on Freedom Mobile, not Rogers or Bell. I don't think my carrier ever sold this phone, and I'm not sure what would happen if I flashed 8.0 made for Bell or Rogers phones.
Ideally I'd like 7.1.1 Canadian generic for Xperia X Performance, but I can't seem to find that anywhere.
I've also never done this so I don't really know what I'm doing, and don't want to void my warranty!
Thanks for you help!!
Good the ROMs that you see for Canada are all latest 8.0 with May security patches and maybe your phone is one of these and the updates just got stucked for some reason.
First you have to check what kind of model you have to check this, to do so you should open the dialler and type
*#*#7378423#*#*
From the service menu you should select -> Service Info -> Software Info and look for Customization Version:
As I said mine is a french model so it states 1302-9342_R2E your should be something different but only the first 8 numbers matter
then look this number in Xperifirm if yours is everything different from Internal Unit (second column from the screenshot) then there is a easy way to try and update without loosing your warranty
First there is always a risk! But I have done this a few times for my Xperia U and Xperia M5 and had no problems at all.
Do a backup - contacts...everything you need as it will delete them
charge the phone to at least 80%
then you should go to the Xperia Companion and do a software repair, not update but repair
It should install the latest version for your phone but it shows the version it installed only when it's finished...
Even if it has not installed the latest update then just connect the phone to your wifi/LTE and try the OTA updates again (could take up to an hour)
This is the safest way that will not void your warranty in any way but will delete your info (contacts, pics..etc. ) so do a backup prior
And if possible use a laptop with a working battery as even a 1 second glitch in the grid could cause the phone to get bricked
And if your phone is imported from China and the customization number is considered as an Internal Unit the only way you could get 7.0 or 8.0 is by flashing and another ftf file as the ones for Bell Canada or Rogers, there are actually some ROMs uploaded in XperiaBlog
there could be some in XDA but I have not search for any
st3ch said:
Good the ROMs that you see for Canada are all latest 8.0 with May security patches and maybe your phone is one of these and the updates just got stucked for some reason.
First you have to check what kind of model you have to check this, to do so you should open the dialler and type
*#*#7378423#*#*
From the service menu you should select -> Service Info -> Software Info and look for Customization Version:
As I said mine is a french model so it states 1302-9342_R2E your should be something different but only the first 8 numbers matter
then look this number in Xperifirm if yours is everything different from Internal Unit (second column from the screenshot) then there is a easy way to try and update without loosing your warranty
First there is always a risk! But I have done this a few times for my Xperia U and Xperia M5 and had no problems at all.
Do a backup - contacts...everything you need as it will delete them
charge the phone to at least 80%
then you should go to the Xperia Companion and do a software repair, not update but repair
It should install the latest version for your phone but it shows the version it installed only when it's finished...
Even if it has not installed the latest update then just connect the phone to your wifi/LTE and try the OTA updates again (could take up to an hour)
This is the safest way that will not void your warranty in any way but will delete your info (contacts, pics..etc. ) so do a backup prior
And if possible use a laptop with a working battery as even a 1 second glitch in the grid could cause the phone to get bricked
And if your phone is imported from China and the customization number is considered as an Internal Unit the only way you could get 7.0 or 8.0 is by flashing and another ftf file as the ones for Bell Canada or Rogers, there are actually some ROMs uploaded in XperiaBlog
there could be some in XDA but I have not search for any
Click to expand...
Click to collapse
Thanks so much for the reply...I discovered the version of Android installed on my phone is a version meant for Journalists/Reviewers/Commercial use, and can not be updated. I just got a refund for the 3-year warranty portion of my purchase after pointing this out to them. So after the 90 day warranty that came with it runs out, I'll be able to do anything I feel like with this device.
I'll be looking for a safe way to install 7.1.1 hopefully, and if not then 8.0. There seem to be less issues with 7.1.1, but there's really only one way to find out: when I start using it.
I'll definitely need a point in the right direction when it comes to that though. I understand Sony has an official flashing tool, and you have to unlock the bootloader (which is supported on my phone even with this version). But I haven't done it before and don't know how.

Categories

Resources