Database Users

Newbie guide for rooting SGP312 Sony Xperia Tablet Z

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.

[OTA] Yoga Tablet 2 830F - Android 5.0.1 - Lollipop ota update 2

Lenovo Yoga Tablet 2 830F - Android 5.0.1 - Lollipop ota update 2 from Lenovo (20/7/15)
Filename: YT2-830F_USR_S000195_1504220230_WW21_ROW_TO_YT2-830F_USR_S100067_1507101258_WW52_ROW.zip
Size: 1,15 GB
Link: https://drive.google.com/file/d/0B1j7Qr4n1Z15U3pXMTdNdHRfd1E
INFO !!!
My first update OverTheAir with this file was a fail. Only black screen after update and reboot.
(I think because i did not change the country code after flashing KitKat a few weeks ago)
(If the update stuck at 100% in recovery you also have to reflash KitKat ROM)
So i flashed original 830F KitKat ROM via "PhoneFlashTool" with this ROM / Tutorial:
https://cloud.mail.ru/public/Z2US9gd..._150422_ROW.7z
http://www.android-hilfe.de/thema/tutorial-wie-installiere-ich-das-kommende-update-wenn-es-nicht-funktioniert-fuer-alle-varianten.697884/
Changed the "Country Code Setting" via ContactApp ####6020# to "de" (select your language).
And do not update any app like Chrome etc. when it reboots again after.
Then download and start the Lollipop 5.0.1 Update.
Lollipop upgrade reboots into recovery and stays 5min. at 100%.
Then reboots into some intel-flash mode and stays for 4min.
After it reboots into Lollipop OS... :cyclops:
INFO 2 !!! (if you installed Lollipop update 1 first and now restoring/flashing of KitKat ROM fails)
matshias said:
I have the same problem, only that I had the first Lollipop version for 1050F with root and then got the new Lollipop update. The Kitkat version fails to flash. But here is what helped: Go to this post http://forum.xda-developers.com/thi...-8-10-13-3-t2930428/post60490907#post60490907
and download the LtoKKxml.7z and copy the files into the kitkat firmware folder and then flash using flash-LtoKK-PVT-810.xml
I had to remove the parts of the XML that erase and format data. Then it worked
After that I could flash KitKat!!
Click to expand...
Click to collapse
LOLLIPOP ROOT
So easy, follow steps 1-8: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
I download "IntelAndroid-FBRL-05-16-2015-PTR.7z" and "UPDATE-SuperSU-v2.46.zip" and it worked with Lollipop 5.0.1.
Make sure you have all the Android, Intel, ADB driver stuff installed (for me win7 installed another one at rooting?)
!!! USE OPTION T4 FOR LOLLIPOP ROOT !!!
.

5m00v3 said:
2 hours ago i`ve just received the new official Android Lollipop Update from Lenovo via System-Upgrade!
Filename: YT2-830F_USR_S000195_1504220230_WW21_ROW_TO_YT2-830F_USR_S100067_1507101258_WW52_ROW.zip
Size: 1,15 GB
Country: Germany
I have made a copy from the ZIP and can upload, if someone point me to an fast and simple upload-service...
I install now and report soon...
Click to expand...
Click to collapse
Yup I got the notice a few mins ago. I also got it many weeks ago when it bricked my yoga 2 8.3
Advice, when it says Updating....100%. Leave it alone. Last time I thought it was done since it said 100% for many many minutes. So i thought it was stuck or bricked. Just let it sit. It will reboot by itself and restart to the next phase.
It will also sit on the Lenovo android screen for quite a while before it goes to Android is upgrading.

Yes, i got problems too!
- It stays for 8min. at 100%. I leave it alone...
- Then 4 chinese Buttons showed up.
- I pressed the first (reboot i think)
- it reboots, it shows the white lenovo text, then black screen with background light on.
- i waited 10min., no change or start into OS.
- then i pressed 15sek power off, light goes off.
- if i power on, again white lenovo text, then black screen with background light on. nothing... ???
i reboot into recovery and wiped cache, nothing.
i think i will make update from SD card again... see if something happend

Update again from SD dont work! it says:
"/system/app/Chrome.apk" has unexpected contents...
E: Error in /sideload/package.zip

SUCCESS, LOLLIPOP IS WORKING!!!
I Have restored original KitKat ROM via "PhoneFlashTool" with this ROMs / Tutorial:
https://cloud.mail.ru/public/Z2US9gd6f2ei/YT2-830F_S0195_150422_ROW.7z
http://www.android-hilfe.de/thema/t...icht-funktioniert-fuer-alle-varianten.697884/
This time i´ve made the "Country Setting" via ContactApp ####6020# to "DE" befor download and upgrade!
And i have aborted the automatic PlayStore updates for Chrome etc...
Lollipop upgrade reboots into recovery and stays 5min. at 100%.
Then reboots into some intel-flash mode and stays for 4min.
After it reboots into Lollipop OS...

So can you boot back into android? Even after you wiped it? If not and you can't do anything, call Lenovo. I think only they can fix it.
If you can get back into android, I would suggest waiting for the System update notice. That's what showed up this morning for me. I didn't have any chinese buttons. I didn't have to touch anything, just wait for a really long time which is unnerving because I don't know status.

I flashed the KitKat Version again, changed country code, and installed the new Lollipop 5.0.1 update again.
This time there are no chinese buttons to press. (i think because changing the country code befor update).
Lollipop is great, the display is much faster while scrolling in chrome etc.

Interesting. I wonder what the difference between the versions of the country codes are. Mine bricked last time it was updated to lollipop. When I got the repair back, it was back to kitkat and I couldn't update until this morning.
Glad to hear you got it fixed. A few of my apps also stopped working and I had to clear the cache to get it working again after the update.

There are some differences in pre-installed apps. I did not changed the country code few weeks ago because there are some apps in german setup i do not want...
**** Edit *****
Added a Link on top
Added ROOT on top

mine is failing on Lenovo Recovery. It will go to 100% and failed. I had to reboot. FYI, mine is rooted.

sdho said:
mine is failing on Lenovo Recovery. It will go to 100% and failed. I had to reboot. FYI, mine is rooted.
Click to expand...
Click to collapse
You need to flash the stock kk firmware.
http://forum.xda-developers.com/showthread.php?p=61955463
From my LG-G3 running Jasmine8.0/Skydragon Kernel 4.2

Yes, It looks like I cannot just upgrade from rooted KK. I had to go back to stock kk firmware provided in the OP's link and follow step by step instructions using google translate. thanks workdowg and 5m00v3.

anyone missing 5GHz band Wi-Fi support with country code DE? I cannot seem to change the country code once it has been upgraded to Lollipop.

sdho said:
anyone missing 5GHz band Wi-Fi support with country code DE? I cannot seem to change the country code once it has been upgraded to Lollipop.
Click to expand...
Click to collapse
Lollipop does not longer provide the option to manual change band... it will auto connect to 5ghz if possible.
It has nothing to do with country code DE. You can check your connection 2,4/5ghz with the app "wifi band".
My YT2 connects automatic to my 5ghz. And i have 2 networks (2,4 + 5ghz) with same networkname.

Hi,
I have the same problem, black screen after OTA Update, but now, impossible to acces to recovery, dirrectly a black screen after "Lenovo" logo, have you an ideas ?
thanks
---------- Post added at 02:10 PM ---------- Previous post was at 01:58 PM ----------
Eagledig said:
Hi,
I have the same problem, black screen after OTA Update, but now, impossible to acces to recovery, dirrectly a black screen after "Lenovo" logo, have you an ideas ?
thanks
Click to expand...
Click to collapse
Okay, I found the solution ! Make the tablet totaly Off, press volume up and volume down, than press power bouton, you directly acces to fastboot mode, and here you can flash with Phone Flash Tool.

Hi,
thanks for the timming TIPs !!
I can't believe LENOVO dosen't take care of this basic things !!
Thanks to you Lollipop is running on my beloved Yoga.
A little tip while we are avaiting 5.1,
Go in Parameter
Activate DEV options : About this tablet, touch 7 times on "Build Version", it will activate the Developper Menu in parameters
Go to Developpers Option (in PArameter)
UNCheck NuPlayer in multimedia.
--> REBOOT your device
It will allow you to avoid Lagging into the UI and apps.
Note that in 5.1 NuPlayer has been replaced by a bugfree version.
Now my last issue is to root the Lenovo...
I tried the rooting method : http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
but aleas I'm stick with an ugly : E: failed to verify whole-file signature
when trying to apply latest SuperSu when in recovery mode...
Tried with stock 2.46 and BETA 2.49.... same result.
Your help is kindly requested to solve this....

pregis said:
Now my last issue is to root the Lenovo...
I tried the rooting method : http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
but aleas I'm stick with an ugly : E: failed to verify whole-file signature
when trying to apply latest SuperSu when in recovery mode...
Tried with stock 2.46 and BETA 2.49.... same result.
Your help is kindly requested to solve this....
Click to expand...
Click to collapse
Googling ”E: failed to verify whole-file signature" and each one talks about a corrupt download... They are old posts from 2013 or so but they could be right.
Try this version 2.40. You can update in the Play store once your rooted.
https://www.dropbox.com/s/0xbu7ve3haha8gw/UPDATE-SuperSU-v2.40.zip?dl=0
Sent from my YOGA Tablet 2-1050F

Thanks for your help.
I tried the 2.40 version triple check the zip file, aleas same error...
Also there are not only corruptions problems related... some are related to CMW version problem and lack of "unsign" option..
Again thanks for the 2.40 link. If you have any suggestion I'm all ears.

There is a new update, to yt2-830f_usr_s100191_1511230623_ww52_row
anyone tried it already?

Looks like it requires going back to stock KitKat again just to update it.
Can't really be bothered trying it.

"Software status: Modified" and the OTA updates...

Hi all,
I was running my stock 5.1.1 (LPD23.118-6.1) rom rooted for a long time and wasn't able to receive OTA updates due to the obvious reason about rooting and etc. My recovery wasn't changed. So, I saw the thread about that "flashable zips" about 6.0 roms and decided to test it. Due to some crashes and forced closes, I decided to back to my previous backup of rooted 5.1.1 stock rom. But now I want to have my phone stock as hell, and the first thing that I do was flash the most updated firmware that I found in here that was available to download. I flashed the whole LPD23.118-6.3 stock rom, a little bit newer than my old stock rooted rom. Everything working, everything fine, except...
In bootloader it says "Software status: modified", and when I try to manually check about updates, it says that my software is up to date, which I know isn't true, because OTA update of Android 6.0 is already available (i have a friend who got an X Play and he already received the ota).
How can I solve this?

Totemic_tHiRp said:
Hi all,
I was running my stock 5.1.1 (LPD23.118-6.1) rom rooted for a long time and wasn't able to receive OTA updates due to the obvious reason about rooting and etc. My recovery wasn't changed. So, I saw the thread about that "flashable zips" about 6.0 roms and decided to test it. Due to some crashes and forced closes, I decided to back to my previous backup of rooted 5.1.1 stock rom. But now I want to have my phone stock as hell, and the first thing that I do was flash the most updated firmware that I found in here that was available to download. I flashed the whole LPD23.118-6.3 stock rom, a little bit newer than my old stock rooted rom. Everything working, everything fine, except...
In bootloader it says "Software status: modified", and when I try to manually check about updates, it says that my software is up to date, which I know isn't true, because OTA update of Android 6.0 is already available (i have a friend who got an X Play and he already received the ota).
How can I solve this?
Click to expand...
Click to collapse
The force closes you got are completely normal and if you read the thread you will have found out you just need to reboot your phone until they go away.
The status modified just means your bootloader was unlocked and doesn't matter.
You have a few options, keep trying for OTA, flash another version and keep trying for OTA, sideload one of the available OTA zip files, or try a TWRP backup.

scottdanpor said:
The force closes you got are completely normal and if you read the thread you will have found out you just need to reboot your phone until they go away.
The status modified just means your bootloader was unlocked and doesn't matter.
You have a few options, keep trying for OTA, flash another version and keep trying for OTA, sideload one of the available OTA zip files, or try a TWRP backup.
Click to expand...
Click to collapse
Thanks for your reply. Actually i'm downloading the recently posted 6.0 firmware for the Brazilian/Latin American rom in firmware's thread. Unfortunately the download is very slow, but I guess I can surely update without losing anything. The only strange thing is that I didn't received any OTAs....

Totemic_tHiRp said:
Thanks for your reply. Actually i'm downloading the recently posted 6.0 firmware for the Brazilian/Latin American rom in firmware's thread. Unfortunately the download is very slow, but I guess I can surely update without losing anything. The only strange thing is that I didn't received any OTAs....
Click to expand...
Click to collapse
It's not necessary that if your friend has received the OTA then even you will receive it within few days. The OTA is rolled batch wise and no one knows which phone is in which batch except Moto of course. [emoji4]
Sent from my XT1562 using Tapatalk

Huawei P8Lite Notification/Double Tap problem

Hi there, I'm experiencing some issues with my new bought phone Huawei P8 Lite(ALE-L21 Single-Sim locked in Vodafone Romania).
The first issue and that's kinda important is the notification one; I won't receive for example Facebook's Messenger messages, when phone it's locked or often on home screen. I've given priority on that damn task killer, I did anything recommended on all forums and sites, even from WhatsApp's thread about receiving delayed notifications, I also installed that Push notifications app;
When I said I often receive notifications on my home screen it's beacuse they are delayed I think. I want to fix this so bad so I made a thread about this. Everything has priority, even networking apps, the lock screen has the default theme, I really don't know what to do anymore.
And the second one is about the common double tap execution when writing or tapping or anything else. I'm experiencing some troubles there too, especially when I'm writing, the phone is executing the second tap without my action and I don't know how to fix that.
I'll let some informations about my phone..
I've purchased this phone on 31th of May, 2016
The model number is ALE-L21/Single Sim
The build number is ALE-L21C02 B140
Android 5.0.1 with EMUI 3.1
Phone isn't rooted or modified, and I want to fix these without rooting if it's possible.

well .. you have 2 options:
1. Check notifications manager from notifications panel
2. Upgrade to marshmallow: upgrade to b170 then upgrade to b564 and hope this will fix your problem xD
About the double tap: that is an often problem on this huawei and you can fix that by upgrading to last version of marshmallow.

Can't find an notification manager, may you show me where it is?
And about the versions I found only b170 but it's from spain and I told you that I'm a little bit scared beacuse it's locked in Vodafone Romania

It doesn't matter from where it is, it's official from huawei. It doesn't matter if it's locked in vodafone romania, mine was also locked in vodafone romania, and i have b565 now
You won't brick your phone.
Here it's notification manager:
If you can't find notification, it means that this option is not available on 5.0

May you give me some links to the updates, please? I really don't want to f**k up the phone

Update via local update: make a folder named dload on your internal memory or sdcard an put the update.app inside of this zip
Then, update with the same procedure to 6.0 by installing update.app from this zip

ALE-L21C02 B140
It looks that Your phone is branded and I don't know if You will have balong bug after upgrading the system to B170 and upper. I recommend you to make a debrand process but it needs an unlocked bootloader. When You decide to do it remember to have done a backup of Your data!

Azaradel said:
ALE-L21C02 B140
It looks that Your phone is branded and I don't know if You will have balong bug after upgrading the system to B170 and upper. I recommend you to make a debrand process but it needs an unlocked bootloader. When You decide to do it remember to have done a backup of Your data!
Click to expand...
Click to collapse
Oups, didn't read c02 xD
But i don't think it's a big problem, even if he has balong, he can install vendor or change it.

Could you explain me what's "balong" and "vendor"; I'm sorry but I'm completely parallel with these kind of "deep" stuff in phones..

Balong is a bug that appears when you are installing a firmware that is not for your country and it's a problem with the version not showing properly. The vendor file will fix it.
Sent from my ALE-L21 using XDA-Developers mobile app

And where can I find the vendor file, to avoid the balong bug?
And also is it a problem if I update my One-Sim Phone with an Dual-Sim FW?

That's strange, why are you having b140 on single sim?
And why you want to update with a dual sim version on single sim?
Just install b171 first then install b551, at last install b565 via ota.
Vendor file is inside firmware archives.

Hi,
I bought this phone Huawei P8Lite (ALE-L21) without being connected to any network carrier.
Before I start to unlock bootloader, install TWRP and Root the phone, I checked the system version and EMUI and the rest of the information needed before update to Marshmallow 6.0.
Before I had the following info:
OS: Lollipop 5.0.1
EMUI: 3.0
(ALE-L21C432B200)
At this point I had no update via OTA - (to the Android 6.0 Marshmallow), and made only unlock bootloader
After several hours of searching, I found that I could do a local update (B560 Marshmallow Firmware [Europe] - Dual SIM) available by Huawei.
Link: http://www.carbontesla.com/2016/06/download-huawei-p8-lite-l21-b564-marshmallow-firmware-europe/
I checked Huawei PDF on how to do the update but does not mention Required Version and proceeded to local update.
So far so good, the phone did the update without any problem.
I checked OTA for new update and the phone made update for B564 - Also mentioned by Carbontesla.com
Link: http://www.carbontesla.com/2016/06/download-huawei-p8-lite-l21-b564-marshmallow-firmware-europe/
Phone did the update (B564) without any problem, then I proceed installing TWRP and then I root the phone.
All work beautifully, but I noticed that whatever the application I use both SMS, Facebook, Whatsapp, GMail, takes too long to receive notifications.
I do not know if he was already with this bug when the phone was with Lollipop 5.0.1 with (ALE-L21C432B200) and EMUI 3.0
I have not had time yet to reset the phone to factory settings and verify that fixed the bug, I will do this weekend week :fingers-crossed:
Can someone help me?

pedra3000 said:
Hi,
I bought this phone Huawei P8Lite (ALE-L21) without being connected to any network carrier.
Before I start to unlock bootloader, install TWRP and Root the phone, I checked the system version and EMUI and the rest of the information needed before update to Marshmallow 6.0.
Before I had the following info:
OS: Lollipop 5.0.1
EMUI: 3.0
(ALE-L21C432B200)
At this point I had no update via OTA - (to the Android 6.0 Marshmallow), and made only unlock bootloader
After several hours of searching, I found that I could do a local update (B560 Marshmallow Firmware [Europe] - Dual SIM) available by Huawei.
Link: http://www.carbontesla.com/2016/06/download-huawei-p8-lite-l21-b564-marshmallow-firmware-europe/
I checked Huawei PDF on how to do the update but does not mention Required Version and proceeded to local update.
So far so good, the phone did the update without any problem.
I checked OTA for new update and the phone made update for B564 - Also mentioned by Carbontesla.com
Link: http://www.carbontesla.com/2016/06/download-huawei-p8-lite-l21-b564-marshmallow-firmware-europe/
Phone did the update (B564) without any problem, then I proceed installing TWRP and then I root the phone.
All work beautifully, but I noticed that whatever the application I use both SMS, Facebook, Whatsapp, GMail, takes too long to receive notifications.
I do not know if he was already with this bug when the phone was with Lollipop 5.0.1 with (ALE-L21C432B200) and EMUI 3.0
I have not had time yet to reset the phone to factory settings and verify that fixed the bug, I will do this weekend week :fingers-crossed:
Can someone help me?
Click to expand...
Click to collapse
Check battery management and give access to work in the background for apps You need. Eventually check notification centre too.

Azaradel said:
Check battery management and give access to work in the background for apps You need. Eventually check notification centre too.
Click to expand...
Click to collapse
Yes, I've been checking battery management if everything with access to work in the background for apps, and it seems to be ok and notification center too.
It continues with the same delay / bug
I hope this weekend to reset the phone to factory settings and verify if it keeps the same problem.

Check Wi-Fi sleep, and set it to off from Power Saving tab
Sent from my ALE-L21 using XDA-Developers mobile app

Krokodillo said:
Check Wi-Fi sleep, and set it to off from Power Saving tab
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
I checked and is always on, no sleep.
Today is the day, I'm going to reset the phone to factory settings and then check if all is ok.
I'll be back once I have the result:fingers-crossed:

Before starting to reset the phone to factory settings, I made backup all my personal files and a recovery with TWRP if something wrong happened.
It seems to be all right after the whole process
I receive all notifications like any other phone in normal operation, no delay :good:
But before I celebrate, I will be alert to phone with daily use to make sure that everything continued well.
Thanks for all the help :good:

Need help downgrading stock Oreo to MM or Nougat (with locked bootloader)

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.