Related
Hi all!
I am writing some instructions for newbies like me that wish to root their Xperia Tablet Z. I spent a lot of hours trying to understand how things work and I try to fill this gap with this post. If anybody knows, I would like to have an answer on the DRM, and model type questions that I have colored red in the text.
I was a "proud" owner of Sony Xperia Tablet Z WIFI 32GB (SGP312) that I bought from northern Europe last September. It was my first Android device and I consider myself super newbie on this "sport". Since my last official Sony system upgrade ~1-2 months ago I had sound problems with skype. I could not make a call without a handset and also my sony speakers refused to reproduce any youtube video. Nonetheless, the alarm was working fine! I was disappointed and after a factory reset the sound problems persisted. Thus, I decided to delve into the rooting world.
So long story short, we can install whichever stock/original firmware we want if it is designed for our devices consulting the precious links in xda-developers.com forums. Then we can either stay with this or install custom "ROMs" having our tablet "rooted".
My first goal is to fix the sound problem so I tried following the stock firmware route.
I flashed the firmware(s) with the quite intuitive Flashtool. Beware that I had already installed the required Google's Android SDK/ADT kit in my windows machine, although I performed every task in my linux machine in order to have working fastboot and adb commands with the minimal fuss installation-wise. To flash the stock firmwares, or the so called FTF files, I was entering the flash mode holding/pressing down the Volume Down key while connecting the device with the USB to my PC. I note that holding down the Volume Up key, instead, connects the tablet in the fast boot mode
After/Before every firmware flashing I was trying not to forget to:
Enable the USB Debugging mode
Trust installation from unknown sources (this probably is redundant) and
Use massive storage instead of MTP in my USB connection options.
Then, I tried to unlock my bootloader (for experimenting purposes) following the official SONY instructions. I successfully did (fastboot was saying OK!), without keeping any DRM keys, since I guess I do not need them, right? However with some FTF stock firmwares my screen was freezing while booting and showing the "flying colors" and then it was eternally rebooting again and freezing again and so on. I tried this and verified it with a couple of FTF stock firmwares. The one was for sure the SGP312 Global Xperia Tablet Z WiFi 32 GB - 10.4.1.B.0.109, I do not remember the others. This 10.4.1.B.0.109 was working fine but not with the bootloader unlocked. I found out that I could break the boot/freeze loop by entering flash mode (Volume Down while connecting the USB) just after it was turned off after the "flying color" freeze.
So I tried with this stock firmware: SGP312 10.4.B.0.577 (UK version 32GB WIFI Unbranded) and after using my tablet for ~30mins I can say that I did not encounter any problems.
But I wanted to view the rooting world, so to do this I found out that installing a Recovery Software would help.
So I installed XZDualRecovery. I followed the instructions and downloaded TabZ-lockeddualrecovery2.7.123-BETA.installer.zip and also the *flashable.zip from the same site.
Before starting to implement the instructions, the same XZDualRecovery post was mentioning I should install a 10.3.1.C.0.136 firmware and so I did, getting the SGP312 10.3.1.C.0.136 VMo EU4 firmware. This 10.3.1.C.0.136 was also working quite well, and after unlocking the bootloader (I do not know if I have to do unlock the bootloader everytime I flash a stock FTF) it was botting properly and my speakers were working fine.
I runned the install.sh for linux (install.bat for windows). I noticed that the third option was "3/ Attempt installation on unrooted device" which I tried and was successful, since then, the "Root Checker" app was saying that my tablet was rooted. That was really cool!
I wanted to enter the recovery mode so I turned on my tablet and when the "SONY" letters appeared (or a bit earlier) I started pressing multiple times the Volume Up key and a nice purple screen (like this) with the recovery appeared. There, I chose Wipe Data/Factory Reset (it was quite fast) and then Install multiple Zip files from the SD card.
The Zips I had in my card were the Cyanogen Mod, the Google Apps and the XZDualRecovery:
I downloaded Cyanogen Mod, pollux_windy for our devices, from here. I chose the latest stable version, cm-10.2.1-pollux_windy.zip 2014-02-01 01:07:05, but I hope another one will see the light soon.
I also installed the latest google apps that for today are these and the latest versions can be found here.
The TabZ-lockeddualrecovery2.7.123-BETA.flashable.zip metnioned above. I am not sure if this is really needed but I think I read somewhere that I should included or else I would not be able to Reboot to Recovery after flashing.
The problem with the pollux_windy zip was that I panicked since the recovery zip installation stopped with the error: assert failed [...] status 7 and I was pretty sure I had an SGP312 device!!! So I deleted the first line in the cyanogen zip file:
Code:
/META-INF/com/google/android/updater-script
like it appears here or here. This forum post says I should not extract the zip, but I did and it worked.
After all the above steps I booted my tablet and everything seems almost ok so far. I say almost because:
I notice that my device, according to the settings is now the "SGP311" and not the SGP312 (how could I change that?), but in my free space I still see 25+GB (although I am still using only ~3GB).
Also, some times while I am scrolling e.g. in Play Store I see infinitesimal freezes in the movement of the webpage (AnTuTu benchmark returns a rating of ~19800-20118).
Moreover, I have installed ~30 apps, but the installing procedure seems somehow slow, and the last ~10 apps I tried to install have not been installed "due to an error 495". The above was "fixed" after a reboot, but I must say I never encountered this problem with my stock firmware.
To the first question in red: DRM keys are needed for Playstation Mobile, Video and Music Unlimited, I think something regarding Screen Mirroring and, until Android 4.3, no Bravia Engine 2. With 4.4, it works again.
About the 311 and 312 thing, it is because you flashed a firmware that wasn't specifically for your device. You can go into build.prop file, and change every SGP311 you find to SGP312.
Nevertheless, awesome guide
Sent from my LT26i using Tapatalk
Thanks for the time to share
Hi all,
I have the SGP312 but it's not the "global" version (I noticed one of the stock firmware used was the UK one). I have the US/Canadian/North American version.
Would I brick my device if I flashed with the UK firmware? I haven't for the life of me found any guides/threads for my device.
I know it's the "pollux windy" (wifi 32gb) but I'm...afraid.
Thanks!
UberBaumer said:
Would I brick my device if I flashed with the UK firmware? I haven't for the life of me found any guides/threads for my device.
Click to expand...
Click to collapse
no.
Just dropping this here since I didn't see anything for an US version.
My thoughts on MM: fast, lots little Sony bugs were fixed (double tap for example), reception seems to be better and doze works very well. However, I feel that when the screen is on, it drains faster than LP.
Disclaimer: This worked for me. I provide no support for this. Do a TWRP backup.
FW info:
Device: Xperia Z3 (D6603)
CDA: 1288-7827
Market: USA
Operator: Customized US
Network: GLOBAL-LTE
Release: 23.5.A.0.570 / R4D
Link to my pre-rooted flashable zip: D6603_23.5.A.0.570_1288-7827_R4D_US_CUST_-RecRoot_v3-SuperSU_2.71
PRFC settings:
FW: D6603_23.5.A.0.570_1288-7827_R4D.ftf
SuperSU: BETA-SuperSU-v2.71-20160331103524.zip
Recovery: RecRootV3_combined.zip
Check: Kernel, Modem, LTALabel, Legacy Mode
Other zips and files:
Xposed: xposed-v81-sdk23-arm.zip, XposedInstaller_3.0_alpha4.apk, xposed-uninstaller-20150831-arm.zip (handy)
Modules: App Settings, GravityBox [MM]
Programs: TitaniumBackup 7.3.0.2 (restore data only)
Debloat by @frixed: Slimcore Debloat Script and I also deleted all the Google apps from the backup folder, saved additional 400mb.
Things that did not work:
- Xposed v82 kept getting deactivated on me. There is a v83 that came out over the weekend.
- Xposed modules: APM+ does not boot into recovery and @serajr modules don't work at all unfortunately
- Location Based Wifi port by @niaboc79
Things to test:
- Stereo sound mods, hopefully there's one out there that will allow louder output as well
- Gap Fix, messed up the phone
- Replacing the bootanimation, worked
Thanks for the pre-rooted file. Just wanted to know thougts from others that have tried this version and if it's safe to dirty flash over other region Lollipop.
chepeliyas said:
Thanks for the pre-rooted file. Just wanted to know thougts from others that have tried this version and if it's safe to dirty flash over other region Lollipop.
Click to expand...
Click to collapse
I'm going to say do a TWRP backup first and try a dirty. A few others in the MM Recovery thread had done that and worked out fine.
I would not personally do this though. I also highly advise against it if you have Xposed installed. You will bootloop for sure.
Cow07 said:
I'm going to say do a TWRP backup first and try a dirty. A few others in the MM Recovery thread had done that and worked out fine.
I would not personally do this though. I also highly advise against it if you have Xposed installed. You will bootloop for sure.
Click to expand...
Click to collapse
Perfect, thanks!
1) Thank you very much for putting together this pre-rooted ROM; you're the real MVP.
2) I am having issues getting NFC to work. When I first clean install this zip (wipe EVERYTHING -> install) and boot, NFC tries to update its firmware and then returns Failed (-1). I reboot, and I am then unable to toggle the NFC on switch it settings. Has this happened to anyone else? Any thoughts on what to do next in order to troubleshoot it? I've run into this issue with both this US rom and an AU version as well.
You need previous nfc firmware to make it work again. So follow this steps :
1. Flash 5.1.1 rom trough flashtool with any customization and be shure to tick all wipes in flashtool
2. After first boot you will see nfc update dialog but this time success (so you repaired the NFC)
3. Root the phone and install recovery (i am sure you know how)
4. Flash this prerooted firmware withouth wiping anything.
5. NFC update dialog will popup but should be success again.
6. Done!
Odoslané z D6603 pomocou Tapatalku
NetSkill said:
You need previous nfc firmware to make it work again. So follow this steps :
1. Flash 5.1.1 rom trough flashtool with any customization and be shure to tick all wipes in flashtool
2. After first boot you will see nfc update dialog but this time success (so you repaired the NFC)
3. Root the phone and install recovery (i am sure you know how)
4. Flash this prerooted firmware withouth wiping anything.
5. NFC update dialog will popup but should be success again.
6. Done!
Odoslané z D6603 pomocou Tapatalku
Click to expand...
Click to collapse
Thank you for your input!
I followed your steps but unfortunately at the first boot of 5.1.1 the NFC update failed (-1) once again, and flashing the pre-rooted firmware overtop did not fix it. I'm also having issues with NFC not being enabled on a 4.4.4 stock rom that I have tried. Could this be a sign of a bigger issue? I only just purchased this (new) phone the other day, but who knows what might have happened to it. I'm just not sure how else to diagnose it :-/
mishicki said:
Thank you for your input!
I followed your steps but unfortunately at the first boot of 5.1.1 the NFC update failed (-1) once again, and flashing the pre-rooted firmware overtop did not fix it. I'm also having issues with NFC not being enabled on a 4.4.4 stock rom that I have tried. Could this be a sign of a bigger issue? I only just purchased this (new) phone the other day, but who knows what might have happened to it. I'm just not sure how else to diagnose it :-/
Click to expand...
Click to collapse
I had my z3 that was from KK to LP to MM and never had issues with the NFC through the various boots. I'd try a stock KK firmware (no root, nothing) and see if it runs fine? and the go through the entire process of getting root then up to LP and then to MM?
Cow07 said:
I had my z3 that was from KK to LP to MM and never had issues with the NFC through the various boots. I'd try a stock KK firmware (no root, nothing) and see if it runs fine? and the go through the entire process of getting root then up to LP and then to MM?
Click to expand...
Click to collapse
I did just that cow07, and unfortunately I get a failure at all steps/stages/etc.
Upon performing a diagnostic NFC test from the Services menu, I get the error message "The NFC device cannot be used" (in all versions of the firmware, KK -> MM).
Sony support asked me to try and run their repair tool using the PC companion software, but that keeps failing as well. I think at this point I may just try to send it back for a replacement, as it is still under my seller's warranty.
Thank you for the help, I'll be coming back here soon enough! This wound up being a hardware issue; after contacting my seller and getting a refund, I purchased another and had no issues using the aforementioned procedure. Thank you for your work!
Hi guys,
I've been searching all over the show but can't seem to find leaked Nougat firmware for my device :/ it's a C183 released in New Zealand. Anyone know if there was actually firmware leaked for the C183 region?
cheers
gymfreak7855 said:
Hi guys,
I've been searching all over the show but can't seem to find leaked Nougat firmware for my device :/ it's a C183 released in New Zealand. Anyone know if there was actually firmware leaked for the C183 region?
cheers
Click to expand...
Click to collapse
I purchased the 2 degrees stock firmware for NXT-L09_C183B130_Firmware_New Zealand_Brightstar NZ Limited_Andriod 6.0_EMUI 4.0_05013NLM
Link is here https://drive.google.com/file/d/0B3pCekrpvWeaNk5meFMtR1dadms/view?usp=sharing
I have that version, I updated to B330 and my cust get broke (C900), but the system with EMUI 4.1 works fine, I tried to update to nougat but the system does not allow with C605 and C432. Maybe with other version work the update.
Yeah I also purchased through 2degrees. Unfortunately it seems firmware for this region hasn't been released still... I was expecting an update back in Feb. Frustrating.
Iv'e still seen nothing
I remember when I was using the Mate2, there were countless debates if/when LL5 was going to be released.
Huawei stated by the first half of 2015. It was released I think it was JUNE 30TH...the "last" day of the first
half of 2015.
If that holds true this time, then they announced Nougat 7 for the Mate 8, "by the end of the 1st quarter of 2017"
would mean...by March 31st. Just something to think about.
Personally, I'm holding off. I can wait. I use a BT headset for the phone, and use it A LOT. The past 4 phones I've
had, I've never used it by holding the phone to my ear, only through the headset. I've seen scattered reports of
issues (not just the Huawei phones), of glitches with bluetooth on nougat.
Marshmellow for me, on the mate8 is VERY stable, so it's a choice. If you gotta have the latest/greatest, there are
sources you can find to download it, but, if you want stable, you might want to wait a while.
p51d007 said:
I remember when I was using the Mate2, there were countless debates if/when LL5 was going to be released.
Huawei stated by the first half of 2015. It was released I think it was JUNE 30TH...the "last" day of the first
half of 2015.
If that holds true this time, then they announced Nougat 7 for the Mate 8, "by the end of the 1st quarter of 2017"
would mean...by March 31st. Just something to think about.
Personally, I'm holding off. I can wait. I use a BT headset for the phone, and use it A LOT. The past 4 phones I've
had, I've never used it by holding the phone to my ear, only through the headset. I've seen scattered reports of
issues (not just the Huawei phones), of glitches with bluetooth on nougat.
Marshmellow for me, on the mate8 is VERY stable, so it's a choice. If you gotta have the latest/greatest, there are
sources you can find to download it, but, if you want stable, you might want to wait a while.
Click to expand...
Click to collapse
Nope still no sign of c183 nougart firmware and now it's may. I am beginning to believe that Huawei are not going to release firmware for this region. It may be potentially due to the poor sales of the device in the region. Who knows. I have not been able to find a single other firmware variant that will flash to the phone. It's disappointing that we've been let down like this with it being a flagship device.
Does anyone have the backup of the cust for this region firmware? I will Rollback my update from 330 (Where I lost my cust), and I will try to change the region, Does anyone tried to change the region to get updates?
mmc00 said:
Does anyone have the backup of the cust for this region firmware? I will Rollback my update from 330 (Where I lost my cust), and I will try to change the region, Does anyone tried to change the region to get updates?
Click to expand...
Click to collapse
Here is Cust Backup .tar.gz
https://drive.google.com/open?id=0B3pCekrpvWeaUzNHTWkxOUs1LWs
Here is Cust Backup .img
https://drive.google.com/open?id=0B3pCekrpvWeaN0dLaEhKVy1yN3ce
these were taken from partition backup manager a few months ago ...these are from NZ L09-C183B150 EMUI 4.0
I have managed to upgrade to Nougat EMUI 5 using firmware finder without root or unlocking boot loader....following L29-636 Starting from file from B180 I didn't change cust but after first update it changed to L29 636 and has had no problems at all
The B585 is smooth and I have had no issues with batter drain or restarts at all...very happy with this after 3 weeks no problems at all.
The only issue was that after B330 which updated successfully, I did discover that my bootloader did get unlocked so I used DC Unlocker to re lock again which cost me 6 credits....now unrooted and bootloader locked.
image1
https://drive.google.com/open?id=0B3pCekrpvWeaeS1PYUg2dFVNRHM
image2
https://drive.google.com/open?id=0B3pCekrpvWeaWUhnWWZDZ0hEVG8
I want to upgrade my Mate 8 too. Are you able to provide the steps you took to upgrade to N?
What information do you need regarding my device?
Model: HUAWEI NXT-09
Build: NXT-L09C183B130
EMUI version: EMUI 4.0
Android version: 6.0
Hardware version: NEXT_L09_VN2
Bootloader: NXT-C900B180_FASTBOOT
Kernel: NXT-C900B191_BOOT
AP version: NXT-C900B130_SYSTEM
Parameter: CVersion:C183 DVersion001
P-00.00.000 G-16.00.004 E-40.01.000
brockles said:
I want to upgrade my Mate 8 too. Are you able to provide the steps you took to upgrade to N?
What information do you need regarding my device?
Model: HUAWEI NXT-09
Build: NXT-L09C183B130
EMUI version: EMUI 4.0
Android version: 6.0
Hardware version: NEXT_L09_VN2
Bootloader: NXT-C900B180_FASTBOOT
Kernel: NXT-C900B191_BOOT
AP version: NXT-C900B130_SYSTEM
Parameter: CVersion:C183 DVersion001
P-00.00.000 G-16.00.004 E-40.01.000
Click to expand...
Click to collapse
This is not for the faint hearted , You need to make sure you have backups of oem.info and cust for for the NZ model.
Also have the NZ firmware update app if needed, here on my google drive....unzip and place extracted update.app onto your SDCARD in dload folder
https://drive.google.com/file/d/0B3pCekrpvWeaNk5meFMtR1dadms/view?usp=sharing
Using HCU Client read phone info take a a screen shot with repair UMTS with of your serial number, imei number, & sub imei, WIFI & bluetooth MAC vendor etc...store this on your PC because you may need these settings if you lose modem settings after unbricking from DC Phoenix
I then would recommend that you have DC Phoenix on stand by and bookmark this link
https://forum.xda-developers.com/mate-8/help/nxt-c900b180-to-nxt-l29c432b330-easily-t3611500 even though its for 432 it will still get you unbricked if it all goes sour.
Now....just to clarify I was on stock firmware L09C185B130 same as your model (shared from link above)with locked bootloader and no root make sure you have developer mode enabled and OEM unlock enabled.
If any of the above is confusing then I would recommend that you go no further.
1st Install Firmware finder and and Firmware finder proxy. enable proxy port in wifi settings ie localhost port 8080
2nd Open FF go to settings and enable USE PROXY TO INSTALL disable SHOW PACKAGES FROM CURRENT REGION
3rd Open go back to FF start and type in NXT-L09636 and click search go to the first and lowest firmware which is B170 download and then install via proxy thru normal update it will show up in Phone settings system update if it doesn't then go back into FF settings and tell it to use proxy to install and then push system update to detect.
This should install without any hitches but you will notice now your firmware will be c900b170
goto FF again and choose the next firmware which is 180 then 193 then 211 etc etc when you get to 330 you will have to trial and error which file will work, I started with the largest full OTA but I dont remember in the end which one worked I think I had 3 or 4 goes if it fails it will stop at 15% and then stop you will have to force reboot thru holding power key but it should boot to normal and then just try another firmware of the same number.
when you get to b330 you should find you have changed to L29636B330 but you will now have unlocked bootloader? not sure why? anyway....keep trial and error updates until you get to B585
Hope it works good luck
Mickie.C said:
This is not for the faint hearted , You need to make sure you have backups of oem.info and cust for for the NZ model.
Also have the NZ firmware update app if needed, here on my google drive....unzip and place extracted update.app onto your SDCARD in dload folder
https://drive.google.com/file/d/0B3pCekrpvWeaNk5meFMtR1dadms/view?usp=sharing
Using HCU Client read phone info take a a screen shot with repair UMTS with of your serial number, imei number, & sub imei, WIFI & bluetooth MAC vendor etc...store this on your PC because you may need these settings if you lose modem settings after unbricking from DC Phoenix
I then would recommend that you have DC Phoenix on stand by and bookmark this link
https://forum.xda-developers.com/mate-8/help/nxt-c900b180-to-nxt-l29c432b330-easily-t3611500 even though its for 432 it will still get you unbricked if it all goes sour.
Now....just to clarify I was on stock firmware L09C185B130 same as your model (shared from link above)with locked bootloader and no root make sure you have developer mode enabled and OEM unlock enabled.
If any of the above is confusing then I would recommend that you go no further.
1st Install Firmware finder and and Firmware finder proxy. enable proxy port in wifi settings ie localhost port 8080
2nd Open FF go to settings and enable USE PROXY TO INSTALL disable SHOW PACKAGES FROM CURRENT REGION
3rd Open go back to FF start and type in NXT-L09636 and click search go to the first and lowest firmware which is B170 download and then install via proxy thru normal update it will show up in Phone settings system update if it doesn't then go back into FF settings and tell it to use proxy to install and then push system update to detect.
This should install without any hitches but you will notice now your firmware will be c900b170
goto FF again and choose the next firmware which is 180 then 193 then 211 etc etc when you get to 330 you will have to trial and error which file will work, I started with the largest full OTA but I dont remember in the end which one worked I think I had 3 or 4 goes if it fails it will stop at 15% and then stop you will have to force reboot thru holding power key but it should boot to normal and then just try another firmware of the same number.
when you get to b330 you should find you have changed to L29636B330 but you will now have unlocked bootloader? not sure why? anyway....keep trial and error updates until you get to B585
Hope it works good luck
Click to expand...
Click to collapse
When you converted your L09 to L29 did u get dual sim menu in Settings?
I want to crossflash my L09C432 to L29C432 so i can use dual sim function.
It works on Mate 9 and P10 singel sim when crossflash.
Just want to check if it is the same on Mate 8?
Sent from my LON-L29 using XDA Labs
I change the region and the model to L29C636, thanks to Mickie's helps, my steps:
1. I install the B330, wich a get from the Firmware official thread, and I used the 3 button method.
2. With SRK Tool, unlok the bootloader and get root .
3. Again with SKR Tool, change the region, (Change oeminfo and custom bin) to Asia (C636) and model (L29).
4. Donwload and Install the L29C636B330 (3 button method), I have to make a Factory Reset, with this firmware I lost the root and get locked the bootloader.
5. When I start normally, automatically get the update by OTA to L29C636B563.
mmc00 said:
I change the region and the model to L29C636, thanks to Mickie's helps, my steps:
1. I install the B330, wich a get from the Firmware official thread, and I used the 3 button method.
2. With SRK Tool, unlok the bootloader and get root .
3. Again with SKR Tool, change the region, (Change oeminfo and custom bin) to Asia (C636) and model (L29).
4. Donwload and Install the L29C636B330 (3 button method), I have to make a Factory Reset, with this firmware I lost the root and get locked the bootloader.
5. When I start normally, automatically get the update by OTA to L29C636B563.
Click to expand...
Click to collapse
Did u get dual sim settings when u crossflashed? Did u have L09 before crossflash?
Sent from my LON-L29 using XDA Labs
Hello,
atm i dont use my Xc, but i want to update it to oreo, maybe then use it. In the past i bought a branded phone. I flashed Costumized fw from Xperifirm, getting latest updates OTA.
Now, when i am checking "support" "update" in phone, a message apears "There are no newer version planed for this device".
I checked xperifirm, downloaded singapore costumized, and thainland normal versions, create .ftf .
Then start flashing in flashtool. Flash starts and stops at message "reading device information".
So, is it not possible to update from nougat to oero by flashtool or do i something wrong?
Greetings Kullino
kullino said:
Hello,
atm i dont use my Xc, but i want to update it to oreo, maybe then use it. In the past i bought a branded phone. I flashed Costumized fw from Xperifirm, getting latest updates OTA.
Now, when i am checking "support" "update" in phone, a message apears "There are no newer version planed for this device".
I checked xperifirm, downloaded singapore costumized, and thainland normal versions, create .ftf .
Then start flashing in flashtool. Flash starts and stops at message "reading device information".
So, is it not possible to update from nougat to oero by flashtool or do i something wrong?
Greetings Kullino
Click to expand...
Click to collapse
- restart pc and/or phone and try again
- update Flashtool
- double check drivers, etc
- make sure cable is good
Should be OK...
Edit: I worked out my issues, I'll leave this here in case others have similar trouble:
I needed to manually add in the RAW F53XX files from the github (https://github.com/Androxyde/devices/tree/master/F53XX), this allowed Flashtool to correctly detect the type of phone and apply the fsc. I was then able to flash my desired firmware, I chose the 6.0.1 release for Journalists to begin with as a test. This confirmed my suspicion that it was a software update issue causing the proximity sensor to malfunction (stuck on) and also fixed up the FACTORY STARTUP SERVICE-POWER OFF bug and the Warrantytimeservice permanent notification. I can now look at updating to later versions of Android and find the latest version before I have issues again.
---
tl;dr - I need a guide that actually works on downgrading the F5321 to a specific stock Android version with a locked bootloader.
I recently received a new, old stock version of the X Compact (F5321) that appears to be a HK variant as it started up with the Chinese language selected.
It was initially stock Android 6.0.1 with no apparent problems. After OTA updating all the way through to 7.1.x and onward to the latest 8.0, I now receive the "FACTORY STARTUP SERVICE" problem. Even if I'm quick enough to disable the service for the service flag, the proximity sensor does not work as well after updating, making phone calls impossible. I believe the issue is all related to software, not hardware. I want to downgrade to 6.x and go from there before I have to send it back for another replacement.
I'm having trouble with getting Flashtool to correctly detect and identify the firmware files that I want to flash. I want a completely stock version of Android, so keeping the bootloader locked is fine for me.
After downloading the firmware that I want to try, XperiFirm will close and Flashtool will successfully build the FTF. After clicking the lightning bolt > flashmode > the firmware list is blank.
I'm using Flashtool 0.9.26 (I have tried older versions as well with the same problems) with driver signature enforcement disabled and correct drivers installed to detect the phone.
The last time I used Flashtool was to flash my older Z5 Compact, I didn't have any issues then and it was all done within 10 minutes. I've already spent more than 5 hours on this phone and would appreciate any help.
I seem to have the exact same problem with a Hong Kong-sourced X Compact. I am familiar with Flashtool, and have used it for basic flashing of firmware. This time, however, I am experiencing the dreaded "FACTORY STARTUP SERVICE" problem. Was wondering if Flashtool could be used to circumvent the problem. I simply want the USA Android 8.0 firmware on the phone. I am not familiar with the various options that Flashtool offers. I note that you mention a specific script(?) that can be installed. Do you have any advice? Thanks
pseudonym58 said:
I seem to have the exact same problem with a Hong Kong-sourced X Compact. I am familiar with Flashtool, and have used it for basic flashing of firmware. This time, however, I am experiencing the dreaded "FACTORY STARTUP SERVICE" problem. Was wondering if Flashtool could be used to circumvent the problem. I simply want the USA Android 8.0 firmware on the phone. I am not familiar with the various options that Flashtool offers. I note that you mention a specific script(?) that can be installed. Do you have any advice? Thanks
Click to expand...
Click to collapse
The "FACTORY STARTUP SERVICE" and to a lesser extent, "Warrantytimeservice" problems surface only in the later version of Android. The only way I could remove them was by staying on 6.0.x only. Anything higher, and the problems show up again. It seems to be a byproduct of upgrading the HK variant that wasn't designed to actually be software upgraded - you won't be able to have the US 8.x firmware on the phone.
Sorry to say, but you'll be stuck on 6.0.x if you want a usable phone. I should mention that I was never able to maintain a newer firmware on that particular phone.
I've since sent the Compact X back (it was meant to be a gift) and replaced it with a Samsung A20.
h
I'm using SO-O2J and a sim card not docomo. Use the "Repair" in Xperia Companion and it auto flash Android 7.0
..
PioneerSeeker said:
Try different region's roms on www.xperiablog.net and I hope you'll be successful to find nougat or oreo at last for your phone.
Remember xperia devices do not need to unlock bootloader for downgrade...
Click to expand...
Click to collapse
Thanks; I was able to obtain an X Compact originally for the UK market, and was able to successfully flash the US Oreo firmware. All seems to be in order.