Database Users

[Guide] Ultimate Guide to the Xperia Z3

@mods May I request that you pin this thread? Thanks
To the XDA Community and readers alike,
Welcome to the Xperia Z3 reference guide aimed at compiling all of the most useful and most effective methods and tips to guide you through using you Xperia Z3. In this guide, I will try my best to cover all of the topics needed to get you started with your Xperia Z3 endeavors both Advanced and Basics. If you feel you want to contribute, then please place what you feel should be added in the thread. I will ensure you’re properly credited for your contribution . This guide utilizes the same format in this guide by XDA Recognized Developer @DooMLoRD and has been modified to suit the Xperia Z3 community.
To start off, let me introduce myself. People refer to me as Furrydaus and I am a developer, contributor and a person whom people look for if they have queries for their Xperia SP who's 15 Years old. (Yep you heard that right!). (I do not have the Recognized Contributor Tag but I don't actually bother much. The community is far more important than those tags ) I help out projects and also create projects for the community. I mainly develop for the Xperia series and the Xperia SP is my third device that I owned under the Xperia Series. The Xperia Z3 is my fourth device that I own. I help with creating Firefox OS, CyanogenMod 11s, Z3Perience and other mini mods for the Xperia SP. So with that silly introduction of myself out of the way :silly:, let’s get started with the guide shall we?
The Contents Covered in this guide:
The Basics
• BootModes
• Information Concerning your device
Advanced Information
• FlashTool
• Root
• Bootloader Unlock
• Recovery
• Flashing Custom Kernels
• Flashing Custom ROMs
Click to expand...
Click to collapse

>> The Basics
[Boot Modes]
Every new mobile device released under SONY has access to various boot modes that is able to handle different things. The 'Boot mode' is a form of interacting with higher level functions on your device such as the hardware
• Standard Boot Mode – This is the standard boot method used to start you device to its normal state. You are able to access the standard boot mode by pressing the power button on your device. (If you don't know this, then I have nothing else to say )
• Flash Mode – This is the mode used to flash official firmware to your device by using an .ftf file (Will cover more about .ftf's later). This mode is similar to what you use to flash firmwares in Samsung Devices through ODIN. To access Flash Mode, Press the volume down button while inserting the Micro USB Cable into your device
• Fastboot mode –This is the mdoe used to flash an official/custom kernel and system images. To access Fastboot, press the volume up button while inserting the Micro USB Cable into your device. This mode requires you to unlock your bootloader (Unlocking The bootloader is covered in the later parts of the guide)

>> The Basics
[Information that concerns your device]
Kernel:
A kernel is used as an interface to talk to your hardware and software. This can be reffered to as the MIDDLE MAN and plays a very important role in making your device function. It is VERY important to not flash the wrong kernel into your device.
Model numbers:
The Xperia Z3 is shipped worldwide in three different variants namely,
• D6653 (TD-LTE)
• D6603 (LTE-A)
• D6633 (Dual LTE-A)
The devices are equipped with everything from hardware to software but they differ in the network type each utilizes due to country specific radio
Android version: http://en.wikipedia.org/wiki/Android_(operating_system)
The Android Version determines whether your device is running the latest features and implementation in design and functionality by Google. It is recommended to always upgrade your android version officially to get the most out of your device. The Xperia Z3 is shipped with Android 4.4.4 Kitkat
Baseband version:
The Baseband is the software interface that communicates your radio to the networks available. A missing baseband=no network. This isn’t the full description but gives you the basic understanding to its use.
Build number:
The Build number is used to identify the firmware version for your device. For example, the Xperia Z3 is shipped with official firmware that is denoted as 23.0.A.2.93. The Firmware version determines whether you device is Up-To-Date. The build.prop in your device can also be tweaked to change the Build Number but we recommend that you do not do so to ensure you device gets the latest updates officially. Official Build Numbers and Firmware Versions can be found here
Firmware:
The firmware is a package containing all the official software for a particular build. It contains system, kernel and baseband files. Firmware is supplied mainly via the forums in an FTF package (a container file ending with .ftf) which can be flashed via FlashTool. Official Build Numbers and Firmware Versions can be found here
Here's the largest and the only .ftf thread containing all of the .ftfs for most devices: http://forum.xda-developers.com/z3/general/ftf-stock-firmwares-xperia-z3-models-t2886061
(I will be helping out the OP soon by providing 100's of ftf's for you guys )
What are the ways to update/repair firmware?
SEUS (Sony Ericsson Update Service) / PCC (PC Companion) / EMMA are all official ways to update to new or repair existing firmware on your device. SEUS/PCC are available to all users (consumers), EMMA is special and is only available to select individuals. This requires you to connect device to PC and then the software will check for updates and download them over the internet.
Updates can also be sent as FOTA (Firmware over-the-air)/OTA (over-the-air) updates where you can download and install the updates without the need to connect to PC/any software.

>> Advanced Information
FlashTool
Flashtool is an unofficial utility supplied by the community namely, AndroXyde. It is the most EASIEST way to flash official firmwares, kernels, custom kernels on both locked and unlocked bootloader devices to your needs. Firmwares that can be flashed via FlashTool is denoted with a .ftf at the end of the file. FlashTool can be used to flash both locked and unlocked bootloaders devices.
For Everything Flashtool,(download links, release notes, FAQ) Head right down to the Flashtool Homepage
Flashtool is also available on GitHub
~ [FLASHTOOL GUIDE] HOW TO for n00bies
Sony also provides an official FlashTool but it can be used only with unlocked bootloader devices.

>> Advanced Information
ROOT
The term root is defined as the way to indicate that your phone has access to higher privileges than standard mobile phones. It can be referred to as the Administrator Mode for Windows but on android instead. Obtaining root requires you to be extra careful as a certain tweak you do to your device might result in a faulty/non-working Z3 that you bought . But with root, you are able to do a world of things from changing the aesthetic look of your device to affecting the performance of your device by overclocking
To obtain root, we recommend you to read this;
CWM-Based Recovery 6.0.4.7 Recovery for Xperia Z3! [DooMLoRD]

>> Advanced Information
Bootloader Unlocking
SONY, Carriers and even other companies tend to lock their bootloaders as a way to force a user to stay with the current state of the device as a way to make sure that their hardwork isn't being replaced. SONY allows the bootloader to be unlocked but it comes with a hefty result for the Z3. Read on to find out why,
Before unlocking your bootloader, You might want to read this:
Extracted from Official SONY unlock bootlaoder site:
Code:
What is this?
By unlocking the boot loader, it’s possible to put custom ROMs on your Xperia™ device. However, we recommend standard users not to unlock the boot loader, as it is not needed. We are proud to deliver great software experiences through our rigorously tested and official software releases. If you are not familiar with the risks involved, you should not proceed further.
Voiding the warranty
If you unlock the boot loader, you may void the warranty of your device and/or any warranty from your operator. See your device’s warranty statement for details. Additionally, due to the modified device software, Sony’s repair network will likely have to replace key components before it can properly test, repair and verify your device using our repair tools and software. Consequently, if Sony performs a warranty repair, Sony will likely charge you a significant service fee for the additional costs caused by your modification of the software.
Risks
Please be aware that Sony cannot guarantee the full functionality, and will not be responsible, for any unsigned custom ROM being flashed to your device after the boot loader is unlocked. An unsigned custom ROM may not have gone through the thorough tests that we run for each device and software version that we release.
Also, a custom ROM might not work properly on your device, and certain functions and offerings may cease to work. The performance of the device might also be affected, and you may damage your device permanently. In worst case, unlocking the boot loader will cause physical injuries or material damage, for example, due to the device overheating.
Certain pre-loaded content on your device may also be inaccessible due to the removal of DRM security keys. For high-end devices running recent software versions, for instance Xperia Z3, the removal of DRM security keys may affect advanced camera functionality. For example, noise reduction algorithms might be removed, and performance when taking photos in low-light conditions might be affected. The secure user data partition may also become inaccessible, and you will not be able to get any more official software upgrades if you unlock the boot loader.
Click to expand...
Click to collapse
If you are sure you want to unlock, the we recommend you read this;
Guide [for beginners] – How to Unlock Bootloader via Flashtool [sid.8491]

>> Advanced Information
Recovery Mode
To learn more about recovery mode, we recommend you read this guide from addictive tips:
Complete Guide to CWM Recovery [Addictive Tips]
To obtain recovery, follow this guide we recommended earlier to obtain root;
CWM-Based Recovery 6.0.4.7 Recovery for Xperia Z3! [DooMLoRD]

>> Advanced Information
Flashing a Custom Kernel
Custom Kernels are mainly specific to the ROM that is being used, stock or custom and you must use the specified kernel with the specified rom to ensure things go smoother for you.
To flash a custom kernel, you can,
1. Flash via Flashtool using FastBoot Mode >>LINK TO GUIDE BY ANDROIDIZER
2. Flash via Recovery in an update.zip file (or in the rom zip itself)

>> Advanced Information
Flashing a Custom ROM
Custom ROMs provide you with possibly enhanced, more or better features than a stock ROM and it depends on the user itself if they want to flash a custom ROM. Most custom ROMs developers provie a .zip which can be used to flash through recovery as means to install the ROM. Usually ROM developers will place the specified steps to flashing the ROM so follow that instead. But if they don’t, this what you generally do,
1. Download the ZIP file and Save it on ur PC (you can also save it to your mobile)
2. Connect your device to the computer and save the .ZIP file on the SDCARD of your device
3. Disconnect the device from the computer upon completion of file transferreboot into recovery
4. Boot into your Custom Recovery and navigate through the menus to find and clear the Dalvik Cache, Cache Partition and System (Factory Reset)
5. Navigate around the recovery menu again to find for the .zip file transferred earlier and flash the .Zip file
6. After flashing is over, reboot device and you will be able to boot on the custom ROM. If not, contact the developer via PM or the Thread.
Click to expand...
Click to collapse

>> Changelog
The Changelog goes from the oldest to the newest changes (Bottom-> Top)
Code:
5 October 2014: Improved Thread, Added Changelog, Added new up-to-date information
5 October 2014: Release of the Guide

Any information you feel you want to add in?
Feel you should have been credited for something?
Then PM me or reply to the thread so I can handle the request! :good:

Updated the guide with many new pieces of information and also added a changelog to show what has been updated

[emoji1]

Nice guide you have there... Applies mostly to all xperia devices... =)

Hi
In deed i very nice work but for a newbee like my with a unlocked Z3... what do i need to have root in order to remove bloatware?
Regards

Mod, please sticky this!

Indeed a nice guide for newbees

bernardix said:
Hi
In deed i very nice work but for a newbee like my with a unlocked Z3... what do i need to have root in order to remove bloatware?
Regards
Click to expand...
Click to collapse
System App Uninstaller from the Google play store
Sent from my C5303 using XDA Premium 4 mobile app

Looks like great guide, i am going to read it tomorrow when my phone arrives.

Nice guide for newbies. Nice work!

[How-To] BLU Studio 5.0 C (D536U) – Rooting, Recovery Install, Flash Latest Stock Rom

Hello everyone on the XDA community.
This is my first post here ..!
To begin excuse my very bad English, I used a translator to do this. Second, moderators apologies if it is not the right place, I ask a little patience and if you need to edit or move the topic, are in every right to do so.
Thanks in advance.
WARNING: This method has been tested by me, but do not hold me responsible for lost data on their devices or if they suffer irreparable damage. The method should be used with caution, following the steps explained below and must possess knowledge of the use of the tools used. USE AT YOUR OWN RISK.
Tools to be used:
BLU Phone Drivers
Universal ADB Drivers
SP Flash Tools v5.1436.00.000
Studio C D536U V08 5.0 Generic Stock Rom
Kingo Root
Easy Magic TWRP Installer for MediaTek
The first step and most important is: BACKUP, support all device data if possible make a backup of the complete ROM Stock, since in case of a "sudden death" can use this to revive the device. In the XDA Developers forums are methods to do this kind of support.
Steps that I have followed for an update ROM Stock, rooting and subsequent installation of custom recovery:
If you have any drivers installed for your BLU device uninstall them before seeing step 2.
Install the device driver for BLU
ADB drivers installed Universal
Enable USB debugging on development options
Download and install the ROM Stock mentioned above using the following::
Open SP Flash Tool.
Click scatter-loading then select the scatter file inside the ROM you downloaded (must be unzipped of course).
Change "Download" to "Firmware upgrade" (under scatter-loading file).
Click in "Download" button.
Take battery out of your phone and insert it again. make sure your phone does not turn on (If phone has an internal battery then just make sure the phone is off).
Plug in your phone to your PC.
The green check mark means you're good to go.
After installing the new ROM Stock, or if you were already using that version of the ROM Stock must install the Kingo Root, then connect your device and the program will recognize it immediately. The whole process is very simple and takes very little time, stay tuned to the screen of your device for confirmations.
Already having installed and running ROM Stock and rooting and undamaged device, run the program TWRP Setup, this will create the MTK-TWRP folder on your desktop, in it we find the TWRP.exe program which execute and follow the steps described in THIS POST.
And with that we have our rooting device with a new version of ROM Stock and custom recovery.
FINAL NOTE: In my case after installing the new version of ROM Stock did a search for update from the device, and found a new version: BLU_D536U_V10_GENERIC. The downloaded and installed before proceeding with the routing and the installation of custom recovery.
I hope you can use this guide and is very useful for everyone.
Best regards.
New Link Added 16/04/2015https://mega.co.nz/#F!TplRURRI!LyAuAlNIBND_AOgu3bx6tQ

Thanks for the guide, but the rom Studio C D536U V08 5.0 Generic Stock Rom in the mega link, is not available, can you upload?

tttony said:
Thanks for the guide, but the rom Studio C D536U V08 5.0 Generic Stock Rom in the mega link, is not available, can you upload?
Click to expand...
Click to collapse
Hi.
The following directory on the website of Mega contains all the Stock ROM for BLU devices, look inside the folder named "STUDIO SERIES" the "STUDIO 5 C - D536" folder, there you can download the ROM Stock V8 Generic.
https://mega.co.nz/#F!TplRURRI!LyAuAlNIBND_AOgu3bx6tQ

BLU Phone Drivers [link broken]
SP Flash Tools v5.1436.00.000 [link broken]

I have a bricked BLU Studio 5.0 C D536L. Can I flash this rom and files?
I don't know if D536U and D536L are the same devices (maybe L and U only a local id).

I just got this phone from Walmart, even though I didn't use your method to root, as my rom is newer than the rom you provide, mine rom is BLU_D536U_V11_GENERIC seemed pointless to downgrade, I did download your Studio C D536U V08 5.0 Generic Stock Rom as it contained a file I needed to manually root my device.
I use Linux not windows, so the splash tool doesn't help, none the less I was able to root without any problems, using the one file from Studio C D536U V08 5.0 Generic Stock Rom.
Thanks
Vampirefo

Need a pointer or two.
vampirefo said:
I just got this phone from Walmart, even though I didn't use your method to root, as my rom is newer than the rom you provide, mine rom is BLU_D536U_V11_GENERIC seemed pointless to downgrade, I did download your Studio C D536U V08 5.0 Generic Stock Rom as it contained a file I needed to manually root my device.
I use Linux not windows, so the splash tool doesn't help, none the less I was able to root without any problems, using the one file from Studio C D536U V08 5.0 Generic Stock Rom.
Thanks
Vampirefo
Click to expand...
Click to collapse
Hello. I have the same phone and conundrum. Sure would appreciate any pointers you could throw my way about successfully rooting this critter. It's a BLU Studio 5.0 Ce D536 Unlocked Dual SIM 5.0 Phone Android KitKat CellPhone.
There was a sale on ebay selling this new for 68.00 so I bit the bullet and bought it. Sure would appreciate it. I use both Linux and windows so I can relate. Any pointers would be great,Thanks!

rwilcher said:
Hello. I have the same phone and conundrum. Sure would appreciate any pointers you could throw my way about successfully rooting this critter. It's a BLU Studio 5.0 Ce D536 Unlocked Dual SIM 5.0 Phone Android KitKat CellPhone.
There was a sale on ebay selling this new for 68.00 so I bit the bullet and bought it. Sure would appreciate it. I use both Linux and windows so I can relate. Any pointers would be great,Thanks!
Click to expand...
Click to collapse
Your device is different than mine, I don't know anything about your phone.
Sent from my BLU STUDIO 5.0 C using Tapatalk

rwilcher said:
Hello. I have the same phone and conundrum. Sure would appreciate any pointers you could throw my way about successfully rooting this critter. It's a BLU Studio 5.0 Ce D536 Unlocked Dual SIM 5.0 Phone Android KitKat CellPhone.
There was a sale on ebay selling this new for 68.00 so I bit the bullet and bought it. Sure would appreciate it. I use both Linux and windows so I can relate. Any pointers would be great,Thanks!
Click to expand...
Click to collapse
Post 3 seems to have files for your phone, should be able to use those files to root your device.
I had to build a custom recovery for my device, I built Carliv 3.3 recovery and TWRP 2.6.8.0 for my device.
Sent from my BLU STUDIO 5.0 C using Tapatalk

Root BLU Studio 5.0 C success
vampirefo said:
Post 3 seems to have files for your phone, should be able to use those files to root your device.
I had to build a custom recovery for my device, I built Carliv 3.3 recovery and TWRP 2.6.8.0 for my device.
Sent from my BLU STUDIO 5.0 C using Tapatalk
Click to expand...
Click to collapse
Thanks for that. Worked but was scary. Had to change shorts afterwards

Brick/Loop in Recovery.
Hey alakentu, thanks for this great thread. I have a problem at the moment: My, Studio BLU Studio 5.0 C (D536U), boots into the recovery and that is all. If I select Factory Mode it gets stuck on the BLU boot animation. I need to flash a new ROM through the original recovery and I need help with this. Can somebody help me ?

I'll give it a try
I have a 5.0C that has one SIM disabled. The SIM was filled with a platic blank that was glued down. I plan on backing up the custom Digicel ROM (D526 I think) and try to load the D536U stock ROM. I assume that if the hardware isn't customized, the stock ROM will have the code that enables and controls the two SIMS. :fingers-crossed:

I rooted and updated my previously locked phone to the V11 generic ROM. The generic ROM:
1. enabled the SIM that was blocked from the OEM.
2. unlocked both SIM slots.
The upgrade was well worth the trouble that I had with properly loading the USB drivers on my Windows 8 PC.

Same exact quandary here as @blackvitriol. My d536u (Studio 5.0 C) sticks at the Blu splash screen. Is there an RUU mode of sorts with this device? If so, how do I access it without being able to fully boot this device?
Sent from my HTC6535LVW using XDA Free mobile app

jmvaught said:
Same exact quandary here as @blackvitriol. Sticks at the Blu splash screen. Is there an RUU mode of sorts with this device? If so, how do I access it without being able to fully boot this device?
Sent from my HTC6535LVW using XDA Free mobile app
Click to expand...
Click to collapse
SOLVED!! (Not that this is an active thread or anything)
So, in ALL of my research I didn't find one single instruction to fix the bootloop, corrupted ROM issue I had. Many claimed to be able to fix this issue, but all fell short because of ONE SINGLE error in the command line. I know, that's all it takes, BUT it may be difficult to figure out (as it was for me). This is all assuming you have your drivers installed and at the very least Minimal ADB/Fastboot functioning.
1. download the factory image (zip, rar, whatever) and UNPACK it somewhere you can easily find in Windows.
2. place the boot.img and system.img files in the same folder as adb.exe and fastboot.exe
3. put your device in Fastboot by doing the following:
a. press and hold Vol Up AND Power until you see the LCD flicker dark (you'll know it when it happens about 3 seconds into holding. Nothing else will happen yet. Nothing will appear on your LCD.)
b. press Vol Up twice and then Vol Down
*you should see three lines pop up in white text on your screen and it should show Fastboot beneath that. If not, pop that battery out and start over. It may take practice to get it right.
4. open a command window in your adb/fastboot folder.
5. Type the following:
fastboot devices
(your device should show up after you hit enter)<---don't type this
fastboot flash boot boot.img
(you should get some action on your device showing it flashed OK as well as in your command window)<---or this
fastboot flash /system system.img
(you should see it working on your device's LCD counting up from 0% to 100%)<---or this
fastboot reboot
(now wait and watch your device come back to life)<---or this
So what's different here from the other instructions out there? You're flashing the system partition by typing "/system system.img" instead of "system system.img"
Any questions, feel free to ask. Have a good one and good luck.
If I've helped you in any way and you want to help support my kids' college fund, please consider buying me a cup of coffee.

jmvaught said:
Same exact quandary here as @blackvitriol. My d536u (Studio 5.0 C) sticks at the Blu splash screen. Is there an RUU mode of sorts with this device? If so, how do I access it without being able to fully boot this device?
Sent from my HTC6535LVW using XDA Free mobile app
Click to expand...
Click to collapse
i threw away that phone and bought a LG Tribute. Best decision ever. Also, thanks for teaching me this new word: quandary

jmvaught said:
SOLVED!! (Not that this is an active thread or anything)
So, in ALL of my research I didn't find one single instruction to fix the bootloop, corrupted ROM issue I had. Many claimed to be able to fix this issue, but all fell short because of ONE SINGLE error in the command line. I know, that's all it takes, BUT it may be difficult to figure out (as it was for me). This is all assuming you have your drivers installed and at the very least Minimal ADB/Fastboot functioning.
1. download the factory image (zip, rar, whatever) and UNPACK it somewhere you can easily find in Windows.
2. place the boot.img and system.img files in the same folder as adb.exe and fastboot.exe
3. put your device in Fastboot by doing the following:
a. press and hold Vol Up AND Power until you see the LCD flicker dark (you'll know it when it happens about 3 seconds into holding. Nothing else will happen yet. Nothing will appear on your LCD.)
b. press Vol Up twice and then Vol Down
*you should see three lines pop up in white text on your screen and it should show Fastboot beneath that. If not, pop that battery out and start over. It may take practice to get it right.
4. open a command window in your adb/fastboot folder.
5. Type the following:
fastboot devices
(your device should show up after you hit enter)<---don't type this
fastboot flash boot boot.img
(you should get some action on your device showing it flashed OK as well as in your command window)<---or this
fastboot flash /system system.img
(you should see it working on your device's LCD counting up from 0% to 100%)<---or this
fastboot reboot
(now wait and watch your device come back to life)<---or this
So what's different here from the other instructions out there? You're flashing the system partition by typing "/system system.img" instead of "system system.img"
Any questions, feel free to ask. Have a good one and good luck.
If I've helped you in any way and you want to help support my kids' college fund, please consider buying me a cup of coffee.
Click to expand...
Click to collapse
Question/Comment...& Thank you.. However I am attempting to sideload adb style ROM from my BLU 5.5 to another's BLU 5.0 C D536u. Any non USB, PC Solutions? Last night we attempted to back up my system to an SD but failed. Pls I've spent hours researching I've installed the Necessary apps (from what I've read), pls help. Thanks again tho for posting this very useful info

Ivy.Crystal said:
Question/Comment...& Thank you.. However I am attempting to sideload adb style ROM from my BLU 5.5 to another's BLU 5.0 C D536u. Any non USB, PC Solutions? Last night we attempted to back up my system to an SD but failed. Pls I've spent hours researching I've installed the Necessary apps (from what I've read), pls help. Thanks again tho for posting this very useful info
Click to expand...
Click to collapse
Why are you trying to put 5.5 rom on 5.0?
Sent from my Venue 8 3830 using Tapatalk

I'm trying to find the 5.0 stock ROM to download it to my SD so the other person can put it in that way.
Or if u can just help me figure out how to get the 5.0C out of bootloop using my phone? Pls
Sent from my BLU STUDIO 5.5 C using Tapatalk

Anyone install the new update? My phone shows v14 is available, date 9/9/2015.
Sent from my BLU STUDIO 5.0 C using Tapatalk

[Prerooted][flashable]zip[23.4.A.1.264][SGP521] Customized DE

Requirements:
Sony Xperia Z2 Tablet (SGP521) with root and recovery.
Instructions:
Download: SGP521_23.4.A.1.264_1282-2019_R3C_flashable-prerooted.zip ( 1.39 GB ):
cloud.mail.ru
mega
Copy zip-file on SDCARD.
Go to recovery.
Factory Reset (recommended).
Install zip-file.
Reboot the system.

Thanks @Bird40 once again anything new in this update or just bugs and security fixes

azeez77 said:
Thanks @Bird40 once again anything new in this update or just bugs and security fixes
Click to expand...
Click to collapse
Just a Full Stagefright fix...
http://www.xperiablog.net/2015/11/27/new-update-23-4-a-1-264-hits-the-xperia-z2-and-z2-tablet-with-full-stagefright-fix/

Thanks @Bird40 for on-time new updates!

Thank you good Sir
Excuse my ignorance as this is my very first Android device (working one that is)
Read quite a bit of articles & tuts Still afraid I'll mess up, so I have a few questions regarding above files & compatibility with my devices in it's current state
Currently at stock 23.4.A.1.264 (Netherlands Customized) updated via OTA from .200
"Bootloader unlock allowed = No", not rooted. Originally was on Croatia (VIP carrier, KitKat)
Am I good to go with such setup?
OR before doing steps above do I need to enable:
Debugging
Disabled apps (some google ones)
Format my SDXC card since I have a lots of things there, If so to which format since it's SDXC card
Backup my device to PC with Sony Software or any other method/tool
Reason I'm this scared is guy who owned it before me flashed it to another countrys ROM. I do not know which tool/method he used and in which way now does this effect doing step 4 If something goes wrong I have no idea how to take further actions.

Newbie seeks informations

Hi.. Im new here with this device i read almost every single post here but there are quite a few things that I don't get it..
What is bootloader? Should i unlock it before rooting the device? And recovery here is in Chinese so shall i get TWRP instead? Also about the flashing Roms issue that erase imei and SN.. why would that happen? And How can i take a backup for these in case i lose them.. Some people mentioned SN writing tools but some people says its not working so im abit confused.. And has anyone noticed that the flashlight of the mobile is actually yellow that affects camera's captures? I would be really grateful if someone helps

1. What is a Bootloader?
Hboot, or we may call it Boot-loader, is like BIOS to windows. It is the first thing that runs when you boot up your Android device. It packages the instructions to boot operating system kernel and most of them are specifically designed to run their own debugging or modification environment.
Every Android phone has a boot-loader that instructs the operating system kernel to boot normally. But you need to understand one thing here that as Android OS is an open source OS and is available on a variety of different hardware, every manufacturer has their own version of bootloader specific for the hardware present in it’s environment.
2. Should you unlock it before rooting the device?
It solely depends on you whether you want to unlock it or not. Unlocking bootloader will give you access to installing custom recoveries on your phone and also you can use custom kernels to boost up phone's performance or simply get more battery juice. Since our K4 note doesn't have any custom kernels so good luck with that.
Warning: Unlocking Boot-loader voids phone's warranty​
3. Why does IMEI/SN erases while flashing ROM's
People don't read the tutorial properly. They blame the OP instead when they do something wrong and loose their IMEI/SN.
What basically happens is, when flashing ROM's through SP flash tools, They should flash it in "DOWNLOAD" mode only and not in "Format ALL" mode. People who all lost their IMEI basically did this mistake.
4. How to Backup and Restore your IMEI/SN (NVRAM)
All the device specific details such as IMEI, SN, MAC addresses are stored in a partition called as NVRAM. So backing it up will indirectly be referring to backing up your IMEI/SN. Here is how you can do it.. LINK
5. How to install Recovery?
if you are on Marshmallow then you will be able to install recovery through this thread. LINK
6. Yellow Flashilight problem?
This bug is introduced in Android V6.0 that is marshmallow. Actually this is not truly a bug. Unlike on Lollipop which had only one LED light enabled during Camera operations, Lenovo decided to enable both of the LED's (That is white and yellow) to give the images a more true LIVELY appeal.
But terming this as bug here because nobody liked it and users were pissed off straightaway. Hopefully, Lenovo will fix it soon.
Hit Thanks if i helped..​

Krishnas096 said:
1. What is a Bootloader?
Hboot, or we may call it Boot-loader, is like BIOS to windows. It is the first thing that runs when you boot up your Android device. It packages the instructions to boot operating system kernel and most of them are specifically designed to run their own debugging or modification environment.
Every Android phone has a boot-loader that instructs the operating system kernel to boot normally. But you need to understand one thing here that as Android OS is an open source OS and is available on a variety of different hardware, every manufacturer has their own version of bootloader specific for the hardware present in it’s environment.
2. Should you unlock it before rooting the device?
It solely depends on you whether you want to unlock it or not. Unlocking bootloader will give you access to installing custom recoveries on your phone and also you can use custom kernels to boost up phone's performance or simply get more battery juice. Since our K4 note doesn't have any custom kernels so good luck with that.
Warning: Unlocking Boot-loader voids phone's warranty​
3. Why does IMEI/SN erases while flashing ROM's
People don't read the tutorial properly. They blame the OP instead when they do something wrong and loose their IMEI/SN.
What basically happens is, when flashing ROM's through SP flash tools, They should flash it in "DOWNLOAD" mode only and not in "Format ALL" mode. People who all lost their IMEI basically did this mistake.
4. How to Backup and Restore your IMEI/SN (NVRAM)
All the device specific details such as IMEI, SN, MAC addresses are stored in a partition called as NVRAM. So backing it up will indirectly be referring to backing up your IMEI/SN. Here is how you can do it.. LINK
5. How to install Recovery?
if you are on Marshmallow then you will be able to install recovery through this thread. LINK
6. Yellow Flashilight problem?
This bug is introduced in Android V6.0 that is marshmallow. Actually this is not truly a bug. Unlike on Lollipop which had only one LED light enabled during Camera operations, Lenovo decided to enable both of the LED's (That is white and yellow) to give the images a more true LIVELY appeal.
But terming this as bug here because nobody liked it and users were pissed off straightaway. Hopefully, Lenovo will fix it soon.
Hit Thanks if i helped..​
Click to expand...
Click to collapse
Ahaaaaa Thanks Alot now it get it all.. Hope they fix that soon.. And i read that some devs here is willing to make a custom kernel i guess.. thanks again and sorry for wasting ur time.. Btw have u noticed that the sound on headset and Bluetooth is also abit lower than other devices?

Lenovo A7010 - CM13.0 Android 6.0 on lenovo-forums.ru

Nubia 5s/5g android R or 11 chinese rom beta update

For Nubia RedMagic 5G/5S (NX659J/NX659J_V1S) ONLY!
Android R V912 - Public Beta (Chinese rom)
Only update through official updater. Wala munang OTA ng Android R. So only thru download at local update lng sa ngayon.
Precautions:
● Before upgrading, please make sure that the phone has sufficient battery power and back up the phone data (it is recommended to use the built-in backup software) to avoid loss of phone data during the upgrade process;
● Before upgrading, please cancel all screen locks. During the upgrading process, please be sure to lay the phone flat, and do not touch the screen at will, and follow the on-screen instructions
● If you have obtained the root permission, please remove the root permission, restore the normal version status, and restore the factory settings before upgrading, otherwise it will easily lead to the failure of the upgrade;
● Any problems encountered during use can be reported in the product feedback section of the forum.
Another Important Details:
1. For a better experience, it is recommended to update the third-party application to the latest version in the app store after the upgrade to avoid the adaptation problem of Android R due to the old third-party application
2. After upgrading from Q to R version, rollback to Q is not supported. If you forcibly roll back, it will cause data loss and bricking.
3. Due to the upgrade of the big platform, the original recorded one-click combo cannot be used in the Android R version, and it needs to be re-recorded to be used normally
Download link:
http://romdownload.nubia.com/红魔5G/V9.12/NX659J-update.zip
Source?
Official post by Nubia
https://bbs.nubia.com/thread-2609817-1-1.html

Officially Chinese variant phone ko tapos nag flash ako ng Global version neto, is it safe to flash this Chinese ROM na Android R ngayon?

Hi !
I would like to ask if I have NX659J_ENCommon_V7.07 on my phone, can I install this version directly on it?
Thanks

Failure at 25%
Hey! Can I get some help? I have tried to install this rom but it failure at 25 % anyone that know why and how to fix this?

salovapes said:
Failure at 25%
Hey! Can I get some help? I have tried to install this rom but it failure at 25 % anyone that know why and how to fix this?
Click to expand...
Click to collapse
i was actually wondering myself, seems the way to do it properly is migrating you 5S to the CN "android 10" rom then upgrade to android 11

When can we expect global rom

How can I flash the chinese rom on Nubia 5s, I'm already on EU version and when I try to flash any chinese rom using the usual method it shows me error at 25%.

Heshamvido said:
How can I flash the chinese rom on Nubia 5s, I'm already on EU version and when I try to flash any chinese rom using the usual method it shows me error at 25%.
Click to expand...
Click to collapse
Are you using an OTA to USB drive adapter? The formatted device needs to be some archaic format, I can't recall which one. FAT32 I think.
BTW I have an R A11 test kernel that is based on the Q vendor trees, I don't know if it works on 5S but it probably works on 5G, no one has tested it though. Runs at 900mhz max GPU OC https://github.com/mrslezak/RM5G_5S_R_MOD I'd appreciate it if someone could test it out. Just backup your boot.img first (which is in the ROM zip file, you can flash back the original to the device if any problems arise via: fastboot flash boot boot.img, and if you need to patch it put it on the phone and use Magisk Manager, transfer back to the PC, and then flash magisk_patched.img or whatever it's named instead.

mslezak said:
Are you using an OTA to USB drive adapter? The formatted device needs to be some archaic format, I can't recall which one. FAT32 I think.
BTW I have an R A11 test kernel that is based on the Q vendor trees, I don't know if it works on 5S but it probably works on 5G, no one has tested it though. Runs at 900mhz max GPU OC https://github.com/mrslezak/RM5G_5S_R_MOD I'd appreciate it if someone could test it out. Just backup your boot.img first (which is in the ROM zip file, you can flash back the original to the device if any problems arise via: fastboot flash boot boot.img, and if you need to patch it put it on the phone and use Magisk Manager, transfer back to the PC, and then flash magisk_patched.img or whatever it's named instead.
Click to expand...
Click to collapse
I'm just using the phone updater itself, with the OTA file on the root directory of the phone itself.