Related
@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!
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
I just got an Xperia X Compact and haven't modified it yet. It has Build number 34.3.A.0.228 . I wanted to get a clean android system (ideally with root) and figured that flashing a ROM like OmniRom or ParanoidAndroid would be the best way to go. I was trying to figure out how to flash a ROM onto the X Compact. I saw this guide, but it appears to be about obtaining root on the stock ROM, including something about modifying the kernel... but it also tells me things about unlocking the bootloader, which many of these ROMs say they need.
What exactly do I need to do to get something like OmniRom or PA on my otherwise unmodified device? Do I just follow the instructions in that guide up to the point where I unlock the bootloader, then switch to the ROM instructions? Do I need TWRP? And what's all this about backing up and restoring DRM keys?
And all that said, what's the most reliable ROM out there for the Xperia X Compact? It seems to be PA, they have it on their official devices list, but I could be wrong.
The first thing you need to do is to backup your DRM key, because if you don't, it will be lost forever. For this you need to downgrade etc., so it will take some time, but if you follow the guide, you should be done in a couple hours. If you lose the key, you might be excluded from using services that utilize DRM, as well as enhanced algorithms by Sony (known is the camera app).
After you have your DRM backup, you can go back to business as usual with flashing ROMs etc. However note that for using the DRM key, you need a patched kernel. While the DRM key can be put back on the phone, it will now reside on a different location that the kernel needs to be aware of.
You can patch your own / ROM-provided kernel as to the guide but there is also pre-patched kernels floating around. You don't need to do this for testing ROMs as long as you don't need DRM functionality or use Sony's camera app (which provides better image quality with the key present!).
You will need TWRP sooner or later for the usual ROM flashing tasks, while flashing the patched kernel can be conveniently done with fastboot. However you do not have to install TWRP, instead you can boot it from PC via fastboot whenever you need it.
The most reliable ROM right now is stock rom, however you can heavily modify it and strip stuff using Magisk etc.
While the phone is officially supported by Paranoid Android, people reported crucial hardware features to be missing and random phone reboots. Have a look at the corresponding thread if these issues have been solved yet.
Thanks for the help! I looked it up and the random phone reboots in PA have been solved. But for the other things... now I'm trying to figure out how to downgrade to back up the DRM keys. What kinds of "services" other than the high quality camera need the keys? Like Google Apps? or more obscure things?
Also is the flashtool.net FlashTool necessary to get a ROM onto the device? I'm kind of sketched out about letting a closed-source program tweak my phone firmware tbh.
You can get an older firmware via XperiFirm. It is a nice tool actually. Make sure you download the version specified and not just any old version to make the TA extraction work.
There are several ways to flash .ftf (official firmware) files, but the only two that I am aware of are the official Sony tool and FlashTool. Btw. in FlashTool you need to repackage (bundle) the FTF for flashing.
Services that need the DRM key include Google's SafetyNet, AFAIK.
Moto G5 Plus dead after the downgrade of stock rom from latest august security patch.LED Blinks . Also tried all blank flash files nothing works. HELP!! Thank you :crying:
Currently we don't have a leaked blankflash that's newer than the April 2017 Moto Z2 Play albus blankflash. (if you want the blankflash, here's one here https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M ). As such, we may not be able to rescue newer corrupted bootloaders (like yours, with a corrupted August 2018 bootloader - corrupted by flashing an old OTA update). Unfortunately, you may have to give your device to a service centre and may have to pay for a motherboard replacement (which are quite expensive). The alternative is to give up the device and buy another device and put this up to an expensive learning lesson - especially with Moto devices, do not use OTA updates when you've flashed older stock firmware, especially if that flash downgraded your stock firmware.
You may be lucky if someone decides to make a cloned image of a working G5 Plus and uploads that, in a similar process used to rescue G5/G5S devices : https://forum.xda-developers.com/moto-g5s/how-to/guide-how-to-create-mmcblk0-img-device-t3803176 https://forum.xda-developers.com/moto-g5s/how-to/blank-flash-montana-t3765150 However, that cloned image is a full copy of whatever device it came from, including IMEI, serials and any data left on it, so really it's only if someone wanted to give up their G5 Plus. If you really need a working device now, unfortunately you'll have to pay for the motherboard repair or buy a new device.
echo92 said:
Currently we don't have a leaked blankflash that's newer than the April 2017 Moto Z2 Play albus blankflash. (if you want the blankflash, here's one here https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M ). As such, we may not be able to rescue newer corrupted bootloaders (like yours, with a corrupted August 2018 bootloader - corrupted by flashing an old OTA update). Unfortunately, you may have to give your device to a service centre and may have to pay for a motherboard replacement (which are quite expensive). The alternative is to give up the device and buy another device and put this up to an expensive learning lesson - especially with Moto devices, do not use OTA updates when you've flashed older stock firmware, especially if that flash downgraded your stock firmware.
You may be lucky if someone decides to make a cloned image of a working G5 Plus and uploads that, in a similar process used to rescue G5/G5S devices : https://forum.xda-developers.com/moto-g5s/how-to/guide-how-to-create-mmcblk0-img-device-t3803176 https://forum.xda-developers.com/moto-g5s/how-to/blank-flash-montana-t3765150 However, that cloned image is a full copy of whatever device it came from, including IMEI, serials and any data left on it, so really it's only if someone wanted to give up their G5 Plus. If you really need a working device now, unfortunately you'll have to pay for the motherboard repair or buy a new device.
Click to expand...
Click to collapse
I had wondered about whether or not that approach would work, never had the inclination to try it. We do have to remember that essentially the block device is just a collection of filesystems, just like any other PC or laptop hard drive / SSD.
Just noting that the process could be adapted to skip the persist partition on restore, so that the existing persist could be preserved. The dd command allows you to skip a certain number of blocks, using either the skip or count options with a suitable block size. Would need someone to get their calculator out, and to take time to look at the partition layout. All the best to the OP if they can find someone who can help out.
Edit: Or it could be done partition by partition. That would hopefully work as well?
NZedPred said:
I had wondered about whether or not that approach would work, never had the inclination to try it. We do have to remember that essentially the block device is just a collection of filesystems, just like any other PC or laptop hard drive / SSD.
Just noting that the process could be adapted to skip the persist partition on restore, so that the existing persist could be preserved. The dd command allows you to skip a certain number of blocks, using either the skip or count options with a suitable block size. Would need someone to get their calculator out, and to take time to look at the partition layout. All the best to the OP if they can find someone who can help out.
Click to expand...
Click to collapse
Hmm, that's a possibility - since all we need is a cloned image to write to an SD card (effectively acting as a secondary flash storage), in theory you could skip the persist partition when making the original copy. Then, uploading it may not be as big a problem with regards to IMEI as the image wouldn't contain another device's persist partition for someone to copy.
Persist, as I understand it, wouldn't be affected on the original device since all we're using the cloned image for is to boot the original device - the cloned image's bootloader in theory should be able to load in the event the original device's bootloader is damaged (as in this case where an OTA update corrupted the original bootloader). Then, you'd re-flash the stock firmware and a working bootloader to the original device, leaving the original persist intact.
echo92 said:
Currently we don't have a leaked blankflash that's newer than the April 2017 Moto Z2 Play albus blankflash. (if you want the blankflash, here's one here https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M ). As such, we may not be able to rescue newer corrupted bootloaders (like yours, with a corrupted August 2018 bootloader - corrupted by flashing an old OTA update). Unfortunately, you may have to give your device to a service centre and may have to pay for a motherboard replacement (which are quite expensive). The alternative is to give up the device and buy another device and put this up to an expensive learning lesson - especially with Moto devices, do not use OTA updates when you've flashed older stock firmware, especially if that flash downgraded your stock firmware.
You may be lucky if someone decides to make a cloned image of a working G5 Plus and uploads that, in a similar process used to rescue G5/G5S devices : https://forum.xda-developers.com/moto-g5s/how-to/guide-how-to-create-mmcblk0-img-device-t3803176 https://forum.xda-developers.com/moto-g5s/how-to/blank-flash-montana-t3765150 However, that cloned image is a full copy of whatever device it came from, including IMEI, serials and any data left on it, so really it's only if someone wanted to give up their G5 Plus. If you really need a working device now, unfortunately you'll have to pay for the motherboard repair or buy a new device.
Click to expand...
Click to collapse
what about the JTAG method here in pune there is a service on JTAG method the said that they while recover my phone ??? website - http://mobileunbrick.com/ .......thanks for reply check that website
ruturaj0077 said:
what about the JTAG method here in pune there is a service on JTAG method the said that they while recover my phone ??? website - http://mobileunbrick.com/ .......thanks for reply check that website
Click to expand...
Click to collapse
You could give them a try, see if they can unbrick your device.
echo92 said:
You could give them a try, see if they can unbrick your device.
Click to expand...
Click to collapse
Thanks for the reply !! ok but when will latest blankflash will release any idea after the oreo update ??
ruturaj0077 said:
Thanks for the reply !! ok but when will latest blankflash will release any idea after the oreo update ??
Click to expand...
Click to collapse
I don't have any idea nor any guarantees that we'd even see one. Most of the blankflashes we have on XDA are leaked from the OEMs, so as such there may be no newer blankflash at all. OEMs see these blankflashes as internal development tools and releasing then may be a security risk. You may have a sympathetic engineer leak one, at the possible risk of their job, or see if the Motorola one gets a leaked blankflash (as it comes with a SD 625). However, i would not bet money on either outcome. If you want to get a working device now, you'll have to pay unfortunately, the cost of hardbricking any device, i guess.
ruturaj0077 said:
Moto G5 Plus dead after the downgrade of stock rom from latest august security patch.LED Blinks . Also tried all blank flash files nothing works. HELP!! Thank you :crying:
Click to expand...
Click to collapse
mine stuck in bootloader what to do now please help
zooreo said:
mine stuck in bootloader what to do now please help
Click to expand...
Click to collapse
bootloader ?? flash the stock rom with the help of adb commands ....fastboot method
[UPDATE]:
**********
I got sick of my phone telling me I needed to update but I couldn't because I'm rooted. So finally got around to patching the last full ROM today w/ the incremental.
This is the fastbootd w/ flash_all.bat script to update to 11.0.12.12.KB05AA. The package for KB05AA (Global/US) is not yet available, hence I'm still making it available here. Be sure to alter the flash script (remove the "rem" before boot.img and recovery.img if you DO NOT want to keep your custom kernel + TWRP) ****************
3.14 GB file on MEGA
mega.nz
THIS IS ONLY FOR 11.0.9.9.KB05AA, BUT READ IT ANYWAY!!!!: ***************
I think this is the first time anyone has actually made a working incremental update for a rooted OOS device, or any with a payload.bin update method that I know of. This method doesn't require any wiping and TWRP / rooted boot.img / custom OOS kernel can be installed right after the script finishes (or left on the device), and you don't even change your active slot (usually, incremental updates will flash to the inactive slot).
I won't get into that many specifics except it was EXTREMELY DIFFICULT, but it works now. Read here if you want to do it yourself in the future, or on another phone. Should work on just about any phone that uses payload.bin files https://forum.xda-developers.com/t/...11-0-9-9-kb05aa-posted.4314677/#post-85425949
You may have to edit the .bat file to pick your RAM type (the lp5 ones are for devices with LPDDR5; it is preset for most of the phones using the LPDDR4 RAM). On the Op8T at least you can do this from adb shell:
adb shell getprop ro.boot.ddr_type; where a 0 is LPDDR4 and 1 is LPDDR5 ram. If it's 1 returned, you need to flash the lp5 files instead of the same named otherwise files in the .bat file (so edit it).
That weird -cow stuff is temp files that prevented the update from working. Not documented anywhere I could find (well, minimally explained by Google), took hours to figure out they were filling the super partition up. I had to re-engineer a Linux project (linked above) to get this working, and have officially updated from 11.0.8.13 to 11.0.9.9 COMPLETELY now. While rooted, without switching slots, and TWRP installed.
You just have to ensure you're on the latest ADB and Fastboot tools and an adb reboot bootloader, followed by a fastboot reboot fastboot should get you there. You can check with: fastboot getvar is-userspace
If it says yes, you're in fastbootd. It actually will work with TWRP installed, I found out later, as long as you reboot in TWRP to fastboot and confirm with the command above you're in fastbootd.
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows/releases/tag/v1.7 has a script that will get you the Latest ADB and Fastboot and put it in a folder for you.
I uploaded it to Mega. Just use some common sense and look at the flash_all.bat file before flashing. I'd write more but I'm tired as hell from getting this working. Now we'll never have to wait for an incremental update while rooted again, at least in the foreseeable future.
I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145
g96818 said:
I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145
Click to expand...
Click to collapse
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....
nujackk said:
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....
Click to expand...
Click to collapse
It's good that you found a band-aid fix.
nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
Of course I tried that solution first, it didn't work on my device.
I'm glad it did on others' devices, kudos to you for posting it (and I DO appreciate your work), but this is the only one that worked on mine. Why? Who knows. I also followed another guide that didn't work. Or else I wouldn't have wasted all my time making this (it took many, many hours to assemble). I'm not saying it's the best solution (I really hope someone just uses what I put in the other thread and assembles it into an easier format for others to use), but I have a full time job (2 actually) so I can't work on it anymore. But it works, no data loss, and TWRP can be installed. Until the next incremental update comes out, then I'll post another version using the tools I used for this, if your build doesn't work on my device. But only when I have the time...
g96818 said:
It's good that you found a band-aid fix.
Click to expand...
Click to collapse
LoL band-aid fix... Call it whatever you want, it works.
It's actually a patched 11.0.8.3.KB05AA with the incremental update applied to it for 11.0.9.9.KB05AA. So it flashes to the active slot and TWRP / rooted custom kernel can all be installed at the same time, even while you are still rooted with Magisk, and even if TWRP is installed. No data loss. I never claimed perfection on this project, just that it works for me.
Keep doing what you're doing, I'll keep doing what I'm doing. We both just aim to help others anyway. I just couldn't get any other method to work so I came up with this one, extending on the incomplete / abandoned work of others. I didn't come up with Payload extraction. Never claimed to. I didn't come up with fastbootd flashing either.
All the forked and modified code is at my GitHub repo. The fork goes back to several other devs' forks (mine is the 3rd modified fork).
Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.
mslezak said:
Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.
Click to expand...
Click to collapse
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot
5star02707 said:
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot
Click to expand...
Click to collapse
I think maybe you misunderstood what I did in this thread. I patched a full ROM with the incremental update of 11.0.9.9.KB05AA. So while OnePlus does not have a full ROM available for download (yet), it is available for download here.
Yeah the method you propose is the "normal" rooted way, but if you're rooted already it forces you to full ROMs not OTAs. You'll be on 11.0.8.3.KB05AA. The goal here is to get on 11.0.10.10.KB05AA (someone NOT ROOTED could download the OTA update using Oxygen Updater and upload it here so I could make a patched version for those that want to keep their root / custom kernel / TWRP / etc and avoid the hassle of unrooting first, which wipes your data partition). At least my Oxygen Updater won't let me download incremental updates even with Magisk Images removed (don't try this unless you're on Op8 / Op8 Pro; some people are having big system update issues on Op8T incremental hence why this thread exists.) It jacked up my system pretty bad (Magisk images removed, Settings / System / System Updates method) until after a boot.img and super restore from TWRP. Not all devices were setup the same (mine is a US carrier converted to US KB05AA). To my knowledge, no direct download has been posted for KB05AA incremental update. Here or on TG. If you have found one, please post a link here. The only one out I've seen works on European ROMs. OnePlus always does KB05AA last for whatever reason.
11.0.10.10.KB05AA posted with caveats - please back up your data as suggested in case the Phone Services APK doesn't fix your SIM after a flash, and you end up formatting the data partition. You may want to try some other methods or just plan on restoring (not with TWRP Alpha in my experience).
mslezak said:
Guys, bad news. So 11.0.10.10.KB05AA incremental does something to the data partition and kills your SIM access.
...
Click to expand...
Click to collapse
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).
BillGoss said:
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).
Click to expand...
Click to collapse
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.
@mslezak, When I get an update I:
- use a terminal session (you could also use ADB) to restore the stock boot and recovery (this way I don't lose root yet)
- install the update but don't reboot
- copy the new boot image and patch it
- turn on airplane mode (to avoid SafetyNet and certification issues in the next step)
- reboot the phone and the updated system comes up
- flash the patched boot image and TWRP in fastboot/bootloader
- reboot and disable airplane mode
This is basically @osm0sis' process from https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
No, I'm not saying flash to both slots, because that will make it impossible to fall back to the current system if the update fails (though this is meaningless if you're manually flashing partitions).
I've got into the habit of syncing active to inactive (after I'm happy with the update) simply because it's required when going from OOS to a custom ROM (I use a shell script based on the LineageOS sync zip). And, after the sync, I can now access the data partition from the inactive slot (which wasn't the case just after the update due to the different keys).
mslezak said:
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.
Click to expand...
Click to collapse
Thats not very hacked/hacked at all, and quite a few use that setup
xstefen said:
Thats not very hacked/hacked at all, and quite a few use that setup
Click to expand...
Click to collapse
LoL I gave up fastbootd flashed to 11.0.10.10.KB05AA and formatted data, let Google download everything it backed up, and am back in business. Just have a lot of apps to login to / Magisk modules to add / etc.
So yeah my patched 11.0.10.10.KB05AA works but the data must be formatted or the SIM doesn't work (at least for me; I don't know if anyone else has tried it since I just posted it a few hours ago; it could be that it works for some without causing issues, I don't have any idea). The goal was to not have to mess up the data partition.... but I can't control what OnePlus does in their updates... Try what worked for others posted here first I'd suggest, or just make solid backups of everything knowing you're going to likely need to reinstall / re-login to everything and format the data partition. New pin, new fingerprint, etc. Re-login to your wifi blah blah.
It's still a full unreleased ROM so I posted it for those that don't mind taking backups (outside of TWRP) if they want to keep root & TWRP on the new release... Yeah a pain to setup if you aren't warned to use another backup method (maybe there is a better backup method, maybe Migrate (app store early access) is developed enough for easy transfer now, I know many people said it worked well in the past but haven't been following the updates. Still free).
It dawned on me later that since the only thing that didn't work using this method going from 11.0.9.9.KB05AA to 11.0.10.10.KB05AA was phone services, that I should just include the working version in this post. Since I already did it the hard way and restored everything back to normal. AS I SAID ABOVE, IF PHONE SERVICES ISN'T ENOUGH TO FIX THE ISSUE, PM ME AND I CAN EXTRACT MORE RELATED FILES UNTIL IT WORKS AGAIN. Unfortunately, I can't just downgrade to 11.0.9.9.KB05AA and keep trying fastbootd over and over again as I don't have the time.
g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
The whole point of this is to AVOID the unbrick tool, reinstalling an outdated version, updating each new ROM build since the brick tool was made, and starting over clean. I think... Have a hunch at least we're almost there on 11.0.10.10.KB05AA with an APK install... Although just backing up everything first will always work (if you don't mind formatting your data partition) just as it's posted here already. Always an issue for us rooted users (especially on Global) since we're always last in line to get a full ROM. This IS a full ROM, payload extracted and patched with incremental updates. Still not available from OnePlus Global (KB05AA) as I checked today, so still relevant.
Ladies and Gents,
I have removed some off topic posts from this thread because I believe we could express the same meaning in more civil words. Please try to do that from now on.
Thanks.
Jerry
FSM