Flashtool 0.9.13.0 - Xperia Arc Android Development

Flashtool 0.9.13.0 - Xperia Arc Android Development

This is the latest Flashtool 0.9.13.0:
Download here: Mod edit - links removed
Flashtool is a S1 flashing software that works for all Sony phones from X10 to Xperia Z Ultra. They all use the S1 protocol for flashing firmwares.
This program was originally made to flash sin files downloaded by SEUS or PCC. From time to time, sin files have been bundled into what is now well known FTF (Flash Tool Firmwares). That is the core of Flashtool and the reason of its name.
Flashtool can also easily unlock the bootloader of the phone using the BLU icon as far as the bootloader of your phone is unlockable
The flashing feature as well as bootloader unlock feature are available whatever the phone is recognized or not by the application. What is only mandatory for flashing is to own the FTF file according to the device you want to flash it on.
Why should I use flashtool ?
Once bootloader unlocked, official sony tools do not work anymore.
Using official sony tools, you can only upgrade. No downgrade possible.
Using flashtool, you can choose what to flash and what not to flash. This said, many rooting scenarios are available implying kernel only downgrade to retrieve a patched rooting exploit and then flash back the right kernel.
You said unlocking bootloader ?
This process gives you the opportunity to flash custom roms such as CyanogenMod ROMs.
I invite you to visit the FXP Project that brings CM to xperia devices.
Many other features have been built-in so that Flashtool can also be used to (as far as the phone is recognized by Flashtool) :
Root your phone
Install recovery, busybox, custom kernels
Clean your rom (remove /system/apps apps of your choice) (Be careful, unless you really know what you do, do not modify the default list. This can make your phone stuck at the SE Logo)
Clear dalvik cache
Optimize (install of JIT v2) (plugin for 2.1 phones only from 2010 line)
Customize (installs apps found in the custom/apps folder of the flashtool)
Edit any text file on the device
Rebrand your device

Hi.... what different with this http://www.flashtool.net/index.php
sorry confused for this thread....

this thread should be reported and deleted... nothing new about flashtool. he just uploaded the .exe file to uploaded server and uploaded pays some money to the uploader for each download.
this user posted exactly this in a spanish forum...
if you look for flashtool in google you can find the original web and links in download section

There is a topic about Flashtool already as well. http://forum.xda-developers.com/showthread.php?t=1000012

Thread closed for the following rule violations:
12. Using the work of others.
If you are developing something that is based on the work of another Member, you MUST first seek their permission and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails, you may then contact a Moderator and provide clear evidence that the work was created by you.
Convincing evidence will result in the copied work being removed. If there is no clear evidence that it was you who created the work, then in the spirit of sharing, all work will remain posted on the forums.
As an addition, developers have the right to hold exclusivity over their work for as long as it is deemed necessary by that developer. However, if the work is claimed as exclusive, it must remain as such. No selective sharing will be allowed (ie, allowing certain people to use it and not others). Should the developer decide to start sharing the work with others, the work automatically becomes fair game for all to use, albeit with the relative credit displayed.
In regard to permissions, the same rules apply for this but if permission was already given and unless there is a very valid reason, it cannot be revoked (same applies to major updates on the work). Under that same premise, permissions cannot be denied unless the work is exclusive or under extreme circumstances.
In plain English: If you want to keep your work exclusive, go for it. However, if you are going to share your work, do it fairly.
These rules apply to all software posted on XDA (including but not limited to ROMs, RUUs, apps, games, kernels, themes, icons, etc) unless that software comes with a license that waives these rules.
Click to expand...
Click to collapse
13. Advertising and Income Generation
Commercial advertising, advertising referral links, pay-per-click links and other income generating methods are forbidden. Do not use XDA-Developers as a means to make money.
Click to expand...
Click to collapse

Related

Frequently Asked Questions: Google Nexus 6

[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Google Nexus 6[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: I'm new to Nexus 6, where do I find a thread with guides and useful information?[/SIZE]The sticky roll up thread in the general forum has all of the guides and important information. You can find that HERE.
[SIZE=+1]Q2: Where can I find tools such as USB drivers[/SIZE]You can find the universal Google driver inside of the Android SDK found HERE. Or you can install ADB/fastboot and universal drivers from HERE.
[SIZE=+1]Q3: What does "flashing" my phone mean?[/SIZE]Well, there are a couple of meanings here. "Flashing" a custom ROM means to overwrite your current OS with a new one. "Flashing" can also mean, changing from a carrier to a pre-paid carrier. Example: I need to flash my phone from AT&T to Cricket.
[SIZE=+1]Q4: Bootloader.. What is this?[/SIZE]For an easy explanation of what a bootloader is, look HERE.
The most recent bootloader and radio can be found here : Here is a recovery flashable zip of the 6.0.1 bootloader and 32r radio

[SIZE=+1]Q5: How do I root my device?[/SIZE]There are a few options. The most recommended way is to unlock your bootloader, flash custom recovery, flash superSU zip, install superSU app. Also there are more automated methods, such as toolkits and auto root. HERE is a great place to get that information.
[SIZE=+1]Q6: What is a factory image?[/SIZE]A factory image for Nexus devices is provided directly from Google. They are used to return your device to the state it was in when it was put in the box. They can be found HERE.
Most recent is 6.0.1 (MMB29Q)
[SIZE=+1]Q7: How do I backup my device in case I bork it?[/SIZE]TWRP recovery has the feature of allowing you to backup your device. It is highly recommended to backup your stock image after installing TWRP and before flashing anything else. Simply use the backup option in TWRP. Think of this as a restore point to go back to when things get borked. Also, you can backup all of your files to your PC before beginning the root process because unlocking your bootloader will wipe your device. There are also apps available that will back up your apps and app data Titanium Backup is a great choice if you already have root. Helium is an option for non-rooted users.
Latest recovery is [RECOVERY][shamu] TWRP 3.0.0-0 touch recovery [2016-02-06]
[SIZE=+1]Q8: How do I flash a factory image?[/SIZE]Flashing a factory image is a fairly easy process. You can use the fastboot method or a toolkit. Toolkits can be found in the development section and an excellent guide to the fastboot method can be found HERE.
[SIZE=+1]Q9: Do the carrier versions matter in deciding on root or ROM?[/SIZE]No. there are no carrier specific ROMs or root methods. There are only two versions of the Nexus 6, Domestic (XT1103) and international (XT1100). Device wiki can be found HERE.. Bootloader unlock method is universal as well.
[SIZE=+1]Q10: What is encryption and should I disable it?[/SIZE]First off, to best answer the "what is" question, look HERE. Now, whether or not to disable it, is entirely up to you. For the most part, the benefits are dependent on your usage. HERE is a thread discussing encryption on 5.1 so please check it out.
[SIZE=+1]Q11: What are fastboot and ADB and should I learn how to use them?[/SIZE]You should absolutely have at least some knowledge of fastboot and ADB. These simple yet powerful tools can save you from trouble and do wonders for your device. The basic principles and commands are extremely easy to learn and thankfully, there are plenty of guides that will help you understand and learn how to use them. Fastboot and ADB aren't exclusive to Nexus either, you can use them with Android as a whole. You can find my favorite guide to using fastboot and ADB right HERE.
[SIZE=+1]Q12: Can I install an OTA if I'm rooted/unencrypted?[/SIZE]No. Since the onset of lollipop, absolutely no system or boot img modifications can be present in order for the OTA to flash. HERE is a thread dedicated to OTA related Q&A and instructions for sideloading. HERE is a thread for OTA files available for sideloading.
[SIZE=+1]Q13: What is a toolkit and should I use one?[/SIZE]First, a toolkit is a program that auto runs and makes changes to your android device. Those changes can be very significant and difficult to recover from when things go wrong. With a toolkit, you can obtain root, return to stock, flash recovery, etc. However, once you start to run the program, you have no idea what is happening to your device. It comes highly recommended to have the basic knowledge of ADB and fastboot even if you are using toolkits. So, should you use one? Sure! No one will tell you not to try, just know what you're getting into and that most experienced users will not use them at all. Therefore, you are more likely to get helped quickly if you have a basic understanding of fastboot, and a tested and working fastboot/ADB environment on your PC, should an issue arise where you need help. Toolkits are absolutely awesome and highly useful in some situations, so don't underestimate their usefulness. It is just that with a Nexus, and a few simple fastboot commands, you can obtain root, return to stock, flash recovery, etc. While typing those commands, you can be 100% certain of what is happening to your device.
[SIZE=+1]Q14: What is CMTE(cyanogenmod theme engine?[/SIZE]Here is a better explanation here And please take note, This is only supported by ROMS that has already adopted CMTE instead of Layers.
[SIZE=+1]Q15: What is Layers (RRO)?[/SIZE]Layers is a extension of runtime resource overlay.
RRO is a framework created by sony for use as a way for them to create xperia themes but also for internal quick prototyping. More explaination from the original thread here. And take note, this is only going to work with ROMs that has adopted to use layers instead of CMTE. Stock roms natively support layers. Just need to download necessary apps and your good to go.
[SIZE=+1]Q16: Systemless Root?[/SIZE]A new way of getting root without modifying /system. More news here.
[SIZE=+1]Q17: Android Pay?[/SIZE]If your running stock and not rooted, no doubt its gonna work out of the box. There was a previous discussion on how to run the feature on rooted devices. It was fun while it lasted. And here is the latest story about android pay.
[SIZE=+1]Q18: I'm trying to search for something specific but I'm having trouble. How do I use XDA Search?[/SIZE]Look HERE for a detailed guide on how to use XDA Search to it's fullest capabilities.*
And here are some terms to ponder
ADB - "Android Debug Bridge" a system that can be accessed using a computer where you can manage the device from. You need the Android SDK to use it.
AOSP - "Android open source project" a project by Google Inc. to give android to developers and manufactures for free.
APK - "Android Package" an Android application
Bloatware - Software or 'apps' that you don't need, but come preinstalled to a device's /system partition, meaning that you cannot remove them unless the device has been rooted. Usually, these are apps are sponsored by a company and included by a carrier for profit
CDMA/GSM - A type of network communication between phones and carriers. GSM phones normally are included with SIM Cards that authorize them onto the network. CDMA have this authorization built in and do not need a sim card.
Custom recovery - A modified version of stock recoveries that allow you to do more things in the recovery mode.
Cyanogenmod (CM) - A free open-source project based on the AOSP. It is a modded version of the Android firmware
Dalvik-Cache - Holds all of the pre-compiled .dex files created from installed apps. These files are static and do not change unless the app is updated.
Deodexed - Where ODEX files are moved into the actual applications modded) version of the Android firmware.
Developer - A man or woman who has created (developed) software.
Firmware - a piece of software to make hardware function correctly. This can refer to Radio Firmware, but is normally used as another name for ROM.
Governor - A system embedded into the kernel to automatically change the current working CPU frequency depending on the workload. It would only go up to what it is overclocked (or underclocked) to, this is called the maximum frequency. It would not drop below the minimum frequency.
KANG - The process of creating a code based of someone else's code.
Kernel - An important part of all operating systems that handles the CPU and other vital components. A modded kernel may be used for overclocking.
Logcat - A logging system built into the ADB
Mod - A modification to a part of the phones software. It is also POSSIBLE to mod the phones hardware but is not recommended.
OTA - "Over the air" a term used to indicate software that was sent to phones directly through the internet to their phones.
Open-source - (not to be confussed with free) A peice of software that is free to edit, use, distribute and share with no charge.
Overclock - To exceed the default maximum CPU speed. This could make a phone more powerful but may cause damage. Although no damaged has been reported so far it could still drain battery life.
Radio Firmware - A type of software that allows correct communication with the radio and the operating system. A newer firmware would normally improve battery life and call quality. The radio firmware only applies to the CDMA/GSM radio.
Radio - (not to be confused with Radio Firmware) A piece of hardware that allows communication. There are 3 main radios in your phone. Bluetooth, WiFi and GSM/CDMA.
ROM -
1. A modified version of the Android operating system operating system.
2. Read Only Memory, a place where information is stored and can not be destroyed, modified or written to.
Stock - An unchanged version of something. Example: I just flashed stock sense.
Underclock - To change your phones maximum frequency to LOWER than the default to attempt to extend the phones lifespan and battery.
WIP - "Work In Progress"
Zipalligned - An archive alignment tool that provides important optimization to Android application (.apk) files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Specifically, it causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries. This allows all portions to be accessed directly with mmap() even if they contain binary data with alignment restrictions. The benefit is a reduction in the amount of RAM consumed when running the application.
INTL - International
Odex - Files that are collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application.
Recovery Mode - A special environment that you can boot into for troubleshooting and upgrading purposes
Thanks to @benjamingwynn for the glossary of terms
Click to expand...
Click to collapse
Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
A special thanks to everyone who contributed to the production of this FAQ
This thread is an ongoing process. This will be a WIP for a period of time
Click to expand...
Click to collapse

This is not intended to be a Q&A help thread. Please only post suggestions for content that should be added to the OP. Post the relevant links to accompany your request.
If you need help or have a general question, consider using these links:
Ask any question/Noob friendly: http://forum.xda-developers.com/nexus-6/help/noob-friendly-qa-help-thread-t3068327
General question and off topic: http://forum.xda-developers.com/nexus-6/general/google-nexus-6-t3077130
Otherwise, create a new post here: http://forum.xda-developers.com/nexus-6/help

A suggestion. Maybe have some info on encrypted vs decrypted, what it is how it works,how to decrypt and stay that way. This thread has a file that you flash in recovery to make sure encryption does not get forced while flashing a ROM or kernel (don't know if I broke any rules by linking without permission if I did let me know this is NOT my work all credit goes to the dev) http://forum.xda-developers.com/showthread.php?t=3000788. Also maybe a link to the noob question thread (though it looks like it's one post above for now) thanks for this thread always nice to just read something to find an answer and not have to make a useless post.

elevatorguy said:
A suggestion. Maybe have some info on encrypted vs decrypted, what it is how it works,how to decrypt and stay that way. This thread has a file that you flash in recovery to make sure encryption does not get forced while flashing a ROM or kernel (don't know if I broke any rules by linking without permission if I did let me know this is NOT my work all credit goes to the dev) http://forum.xda-developers.com/showthread.php?t=3000788. Also maybe a link to the noob question thread (though it looks like it's one post above for now) thanks for this thread always nice to just read something to find an answer and not have to make a useless post.
Click to expand...
Click to collapse
Excellent suggestion, I will get something together tomorrow. Thank you.

"is there a thread with links to important guides and information ?"
"yes, general > sticky roll-up"
Or maybe reword question 1 a little so people know that's where guides are.

rootSU said:
"is there a thread with links to important guides and information ?"
"yes, general > sticky roll-up"
Or maybe reword question 1 a little so people know that's where guides are.
Click to expand...
Click to collapse
Done. Thanks!

elevatorguy said:
A suggestion. Maybe have some info on encrypted vs decrypted, what it is how it works,how to decrypt and stay that way. This thread has a file that you flash in recovery to make sure encryption does not get forced while flashing a ROM or kernel (don't know if I broke any rules by linking without permission if I did let me know this is NOT my work all credit goes to the dev) http://forum.xda-developers.com/showthread.php?t=3000788. Also maybe a link to the noob question thread (though it looks like it's one post above for now) thanks for this thread always nice to just read something to find an answer and not have to make a useless post.
Click to expand...
Click to collapse
Done, thanks again.

rootSU said:
One day we'll rebel
Click to expand...
Click to collapse
Question 18 added to build the rebel forces.

Question 19 added.

Question 20 seems to be a frequent flyer.

Thread has been cleaned per OP request.
Please only post questions with answers, you feel would help your fellow Nexus 6 user.
All other conversion... please bring to a new thread or the lounge:good: Keeping in mind this is not a Q&A thread.
Thank you @Evolution_Tech for continued updates.

Questions 21 and 22 added since we have a new update.

Question 23...toolkits.

Post #2 updated with links to general help threads.

cam30era said:
@Evolution_Tech,
While responding to a thread this morning, I was "asked" to change to the New 2015 XDA thread view (web view). Not sure I like it, but that's not why I'm here. What's the difference between "commenting" on a post and "posting a reply"?
Update: Weirder still, some on the comments aren't even viewable in the XDA Premium app. Just shows a web link....... @danarama 's Black Screen thread.
Click to expand...
Click to collapse
I specifically chose a new template for that thread which allows answers to be "up voted" as you may have seen on many technical sites, most prominently, Microsoft technet.
The apps can't handle it so they make you use a browser.
Reply is an answer or solution. Comments are to a particular answer, so for example, I can say "tried that" without creating a response that is seen as a votable answer.

Question #24 added. How to use XDA Search.

updates coming.. stay tuned

Hey guys I'm new here and hope this is the correct forum. I recently purchased a nexus 6 off amazon and when it arrived I was surprised to find it had been rooted already. I want to set it back to original stock image but I'm not sure which version to download. I don't know which provider it was originally on. It is on Verizon now. Can I just download mmb29q and expect it to work? System info says I have mmb29u but there is no option for that version. Thank you.

Any version will work but all marshmallow builds are unified and 29q is the latest factory image

MassiveDynam1c said:
Hey guys I'm new here and hope this is the correct forum. I recently purchased a nexus 6 off amazon and when it arrived I was surprised to find it had been rooted already. I want to set it back to original stock image but I'm not sure which version to download. I don't know which provider it was originally on. It is on Verizon now. Can I just download mmb29q and expect it to work? System info says I have mmb29u but there is no option for that version. Thank you.
Click to expand...
Click to collapse
this is not q&a thread. this is for the most common FAQ's..
but to answer ur question. go with 29q. this is the latest stock firmware .
how did u ever got 29u as a stock rom? thats the latest aosp. nexus 6 never had a 29u stock firmeware

DOCOMO XPERIA A (Japanese ZR, aka SO-04E) - UPDATED ROOT AND CUSTOM ROM TUTORIAL

[NOTE as of July 2016: the below is provided as-is. I'm no longer watching this thread and I don't provide support for this. You do this at your own risk.]
This is an updated tutorial (as of Oct 2015) to root and upgrade the Japanese Sony Xperia A (SO-04E, Android 4.1.2 or 4.2.2) to Android 4.4.4 and then to Android 5. The Xperia A is the Japanese version of the globally released ZR. In terms of hardware there are two differences: the Xperia A has 32GB internal memory; and its NFC chip set is different from the one in the ZR - which is why NFC applications such as digital wallet (osaifu-keitai) will not work after going through the below steps. The Xperia A has a locked bootloader that cannot be unlocked.
I did not come up with the most important moves here. That was done by others in this thread and this one, notably aperception and mgg4000 (a big thanks to those two!). I only updated some steps that no longer work due to DoCoMo updating their firmware and closing the loopholes exploitable in earlier versions, files getting lost, software features changing etc. I also broke this down into more detail for people who are less familiar with the process of rooting and installing unauthorized ROMs. I have to warn that this will take an inexperienced person at least a few hours, possibly a full day. With complications arising, it could be more.
Also, you need an extra (external) microSD card in your phone for this to work. If you don't have one, you can buy one at convenience or electronics stores. Min 4GB should be fine but more is better considering future need for nandroid backups etc.
Anyway, here we go. In case a file linked to in the tutorial is missing, please see if it's among those I backed up in a Mega account, list at bottom of post.
1. Be sure you have an external SD card as per the comment in the above preamble. Note that at various points in the process the phone will ask you whether to install the Sony PC Companion link. Always skip this.
2. Write down all APN settings of your phone – you will need to manually enter them later.
3. Make sure your phone’s Developer Options are enabled, USB debugging is enabled, and Installing from Unknown Sources is enabled (google if you don’t know this stuff).
4. Install the minimal ADB and Fastboot tools from here: http://forum.xda-developers.com/showthread.php?t=2317790
5. Install Flashtool from here: http://www.flashtool.net/downloads.php . Watch this tutorial to do this and the next steps right: https://www.youtube.com/watch?v=ZfD9kT1DVz0
6. Power down your phone, hold down the Lower Volume key and connect phone to PC via USB cable. Flashtool will now show your phone as connected in Flashboot mode.
7. Using Flashtool, flash this to your phone: https://www.dropbox.com/s/p0m8fzv22m..._Hong_Kong.ftf
(or another C5503 Android 4.2.2 firmware – find one on XDA) . In the Flashtool settings, make sure you wipe the APPS_LOG and USERDATA
8. Disconnect and reboot.
9. You should now have a clean install of a Sony C5503 stock firmware. Confirm this in /Settings/About Phone.
10. If you check your Storage now, you will see only 4.59GB available internal memory, even though the Xperia A has 32GB total. To fix this, use Flashtool to flash back one part of the original SO-04E firmware here:
https://ftf.あんどろいどのこと.みんな/
I used 10.3.1.B.2.13 which worked fine. When flashing this, you must wipe the APPS_LOG and USERDATA again, and exclude EVERYTHING except PARTITION. In other words, all items in the Exclude list must be checked, except PARTITION.
11. When this is done, reboot once more and check your storage again. You should now see ~25GB of usable internal space. Yay!
12. Now make sure you have wifi or phone network access. Wifi is easiest. For 4G/LTE you will need to manually enter the APN settings from Step 2 above first. Just one of them, the one you usually use is fine (in the case of DoCoMo, the most common one is moperaU)
13. Once your phone has mobile network (or wifi) access, go through the process of enabling Developer Options, USB Debugging and Installing from Unknown Sources again.
14. Log into the Google Playstore and install SuperSU
15. Now root your device with this: http://rootkitxperia.com/
16. Start SuperSU and set it up. Grant permissions as requested. If the installation is succesful, you have root.
17. Now install custom recovery. Get the latest dual recovery for ZR (installation file, not flashable file) from here: http://nut.xperia-files.com/). With the phone connected, run the English language install .bat
18. When done, power down device. Power it back up. As soon as the LED lights up (in other words, when the Sony logo appears) and until after you feel a brief vibration press any button on the phone repeatedly (e.g. the volume buttons) to enter recovery. The Recovery service will boot up.
At this point, if you haven’t yet, you need to familiarize yourself with Clockwork Recovery.
Wipe the cache partition, the dalvik cache (under Advanced), and wipe data/factory reset.
19. Reboot, connect USB cable and place the following file on your external SD card
https://mega.co.nz/#!4o0jlQ6b!ZVxOj-...9paCqsR1EQBlGU
20. Boot into Recovery, go to the Wipe options and Clean To Install New ROM. Then install the above file from the external SD card (the device has two SD cards, one external and one internal). This will install Android 4.4.4. Once done, choose the option to reboot the device. (When I did this the first time, Recovery warned that Root may be lost and asked whether to fix this. I chose “Yes, fix it” and rebooted. The good news was that Android 4.4.4 was installed correctly. The bad news was that Root was lost. WTH??? You may want to try NOT fixing it, see if that goes any better. The second time I went through these steps with someone else's Xperia A, this problem did not occur.) When the device has rebooted (and root was not lost), SuperSU should be present which means that you still have root. You can also double-check with an application called "Root Checker" from the Playstore. You may also want to check if Recovery is still on the phone and working (by rebooting the phone and pressing the volume keys when the Sony logo appears.) If Recovery is no longer present, go back to step 17 and repeat. Then come back here. If you have both root and Recovery, you can now skip to step 22.
[21. ONLY if you have lost root like I did, follow these instructions to regain Root (the root kit from step 15 will no longer work on this new version you now have; you can use the Flashtool we installed in step 5, no need to download the official Sony one)
http://techbeasts.com/2014/09/18/how-root-sony-xperia-z-zr-zl-1051a0283-android-444-locked-unlocked/
After flashing the two firmwares and rebooting, each time a “repairs in progress” type of screen appeared and shortly thereafter the phone seemed to power down. I had to remove the battery each time to get the thing started again. Also, while on the Nordic firmware, the phone kept vibrating for no reason. This problem disappears when flashing back the second firmware from the above instructions.]
22. You now have a rooted Android 4.4.4. Presumably you will want to move on to the very latest Android version which is Android 5.1.1. Keep in mind that the Xperia A has a locked bootloader so only ROMs that are designed for a LB will work. I installed this one, works perfectly except for NFC:
http://forum.xda-developers.com/xperia-zr/development/rom-purex-z-v1-0-port-rajeev-t3215063
That’s it. Unfortunately, links included in this tutorial are liable to go dead after a while. Here are the ones likely to vanish, duplicated in a Mega account I set up for this.
Step 7: C5503 HK firmware (C5503_10.3.1.A.2.67_Hong_Kong.ftf):
https://mega.nz/#!R1p2wKII!rs9UFrMHN-nAnaROy-xe5gu1Zt52ipk-451sZEpzv34
Step 10: SO-04E firmware (10.3.1.B.2.13):
https://mega.nz/#!UwgHTT7Z!kKHlcPyPOH-mHcuDHXB6ZVWkf5xTl5op1IOFZ8fUGIU
Step 19: Pre-rooted 4.3.3 (C5503_10.5.1.A.0.283_NCB_PRE-ROOTED_PRFCreator.zip):
https://mega.nz/#!8tQEEJxY!Xd7HoRwWTe_XKPdL6COlS43xZo9TG2b_LFXsZWRLgBM
Step 21: Nordic firmware (C5503_10.5.A.0.230_Nordic NCB.ftf):
https://mega.nz/#!koIiRISS!fUH-OWT4s26wWgcdJ_HYQ9ctJun48m6N_rSzm9o_m64
Step 21: C5503 Kitkat (C5503_10.5.1.A.0.292_RU.ftf):
https://mega.nz/#!pw4jmIhL!ClHKkkSX1seeB13nb9kwlgpeF-LVVKr9IDfhyiqDT9g

Thanks buddy! You meticulously wrote and setup everything. Hope people will be benefited

Thank for the tutorial
axel007 said:
This is an updated tutorial (as of Oct 2015) to root and upgrade the Japanese Sony Xperia A (SO-04E, Android 4.2.2) to Android 4.4.4 and then to Android 5. The Xperia A is the Japanese version of the globally released ZR. In terms of hardware there are two differences: the Xperia A has 32GB internal memory; and its NFC chip set is different from the one in the ZR - which is why NFC applications such as digital wallet (osaifu-keitai) will not work after going through the below steps. The Xperia A has a locked bootloader that cannot be unlocked.
I did not come up with the most important moves here. That was done by others in this thread and this one, notably aperception and mgg4000. I only updated some steps that no longer work due to DoCoMo updating their firmware and closing the loopholes exploitable in earlier versions, files getting lost, software features changing etc. I also broke this down into more detail for people who are less familiar with the process of rooting and installing unauthorized ROMs. I have to warn that this will take an inexperienced person at least one full day, and possibly more. You may want to plan two full days. If you are one of the totally clueless you might save yourself the trouble and simply buy a newer phone.
Also, you need an extra (external) microSD card in your phone for this to work. If you don't have one, you can buy one at convenience or electronics stores. Min 4GB should be fine but more is better considering future need for nandroid backups etc.
Anyway, here we go. In case a file linked to in the tutorial is missing, please see if it's among those I backed up in a Mega account, list at bottom of post.
1. Cancel all your appointments, hire a dog walker and tell your wife she had best stay with some friends this weekend.
2. Write down all APN settings of your phone – you will need to manually enter them later.
3. Make sure your phone’s Developer Options are enabled, USB debugging is enabled, and Installing from Unknown Sources is enabled (google if you don’t know this stuff).
4. Install the minimal ADB and Fastboot tools from here: http://forum.xda-developers.com/show....php?t=2317790
5. Install Flashtool from here: http://www.flashtool.net/downloads.php . Watch this tutorial to do this and the next steps right: https://www.youtube.com/watch?v=ZfD9kT1DVz0
6. Power down your phone, hold down the Lower Volume key and connect phone to PC via USB cable. Flashtool will now show your phone as connected in Flashboot mode.
7. Using Flashtool, flash this to your phone: https://www.dropbox.com/s/p0m8fzv22m..._Hong_Kong.ftf
(or another C5503 Android 4.4.2 firmware – find one on XDA) . In the Flashtool settings, make sure you wipe the APPS_LOG, and check none of the Exclude items; if after this process the phone keeps rebooting, flash the same thing again, this time also wiping USERDATA)
8. Disconnect and reboot. If any trouble, see my comment above in brackets (under point 7).
9. You should now have a clean install of a Sony C5503 stock firmware. Confirm this in /Settings/About Phone.
10. If you check your Storage now, you will see only 4.59GB available internal memory, even though the Xperia A has 32GB total. To fix this, use Flashtool to flash back one part of the original SO-04E firmware here:
https://ftf.あんどろいどのこと.みんな/
I used 10.3.1.B.2.13 which worked fine. When flashing this, you must wipe the APPS_LOG (and maybe USERDATA) again, and exclude EVERYTHING except PARTITION. In other words, all items in the Exclude list must be checked, except PARTITION.
11. When this is done, reboot once more and check your storage again. You should now see ~25GB of usable internal space. Yay!
12. Now make sure you have phone network access. For 4G/LTE you will need to manually enter the APN settings from Step 2 above first. Just one of them, the one you usually use is fine (in the case of DoCoMo, the most common one is moperaU) (Or, instead of messing around with the LTE and APN settings - which takes time and will need to be repeated several more times if you want to use your mobile network connection for downloads - enable Wifi; this will usually be easier.)
13. Once your phone has mobile network (or wifi) access, go through the process of enabling Developer Options, USB Debugging and Installing from Unknown Sources again.
14. Log into the Google Playstore and install SuperSU
15. Now root your device with this: http://rootkitxperia.com/
16. Start SuperSU and set it up. Use a root checker from the Playstore to confirm it’s done.
17. Now install custom recovery. Get the file from here:
https://onedrive.live.com/?id=D419E7...&action=locate (or presumably the latest dual recovery for ZR from here will also work fine: http://nut.xperia-files.com/). With the phone connected, run the English language install .bat
18. When done, power down device. Power it back up. As soon as the LED lights up (in other words, when the Sony logo appears) and until after you feel a brief vibration press any button on the phone repeatedly (e.g. the volume buttons) to enter recovery. The Clockwork Recovery service will boot up.
At this point, if you haven’t yet, you need to familiarize yourself with Clockwork Recovery.
Wipe the cache partition, the dalvik cache (under Advanced), and wipe data/factory reset. Once you reboot, you will once again need to reestablish Playstore access etc.
19. Now place the following file on your external SD card
https://mega.co.nz/#!4o0jlQ6b!ZVxOj-...9paCqsR1EQBlGU
20. Boot into Recovery, wipe cache and do a factory reset. Then install the above file from the external SD card (the device has two SD cards, one external and one internal). This will install Android 4.4.4. Once done, power off the device using the according command in Recovery. When I did this, Recovery warned that Root may be lost and asked whether to fix this. I chose “Yes, fix it” and rebooted. The good news was that Android 4.4.4 was installed correctly. The bad news was that Root was lost. WTH??? You may want to try NOT fixing it, see if that goes any better. Anyway, install SuperSU and the root checker from the Playstore and see if you have root or not. If yes, skip to step 22.
21. ONLY if you have lost root like I did, follow these instructions to regain Root (the root kit from step 15 will no longer work on this new version you now have; you can use the Flashtool we installed in step 5, no need to download the official Sony one)
http://techbeasts.com/2014/09/18/how...cked-unlocked/
After flashing the two firmwares and rebooting, each time a “repairs in progress” type of screen appeared and shortly thereafter the phone seemed to power down. I had to remove the battery each time to get the thing started again. Also, while on the Nordic firmware, the phone kept vibrating for no reason. This problem disappears when flashing back the second firmware from the above instructions.
22. You now have a rooted Android 4.4.4. Presumably you will want to move on to the very latest Android version which is Android 5.1.1. Keep in mind that the Xperia A has a locked bootloader so only ROMs that are designed for a LB will work. I installed this one, works perfectly except for NFC:
http://forum.xda-developers.com/xper...ajeev-t3215063
That’s it. Unfortunately, links included in this tutorial are liable to go dead after a while. Here are the ones likely to vanish, duplicated in a Mega account I set up for this.
Step 7: C5503 HK firmware (C5503_10.3.1.A.2.67_Hong_Kong.ftf):
https://mega.nz/#!R1p2wKII!rs9UFrMHN...pk-451sZEpzv34
Step 10: SO-04E firmware (10.3.1.B.2.13):
https://mega.nz/#!UwgHTT7Z!kKHlcPyPO...5op1IOFZ8fUGIU
Step 19: Pre-rooted 4.3.3 (C5503_10.5.1.A.0.283_NCB_PRE-ROOTED_PRFCreator.zip):
https://mega.nz/#!8tQEEJxY!Xd7HoRwWT...2b_LFXsZWRLgBM
Step 21: Nordic firmware (C5503_10.5.A.0.230_Nordic NCB.ftf):
https://mega.nz/#!koIiRISS!fUH-OWT4s...m6N_rSzm9o_m64
Step 21: C5503 Kitkat (C5503_10.5.1.A.0.292_RU.ftf): https://mega.nz/#!pw4jmIhL!ClHKkkSX1...Kr9IDfhyiqDT9g
Click to expand...
Click to collapse
2 things:
1. What is the "decryption key" for the mega links?
2. I flashed my so-04e previously in a similar procedure, but SOMEHOW corrupted my TA partition. I think it's the TA because the phone will not acquire a signal and when reflashing in flashtool one of the rolling messages is something about TA I never saw before. I'm wondering if maybe I'm bricked. I think it happened with I wiped the data partition in order for the phone to recognize the extra internal memory.

jatyeo said:
2 things:
1. What is the "decryption key" for the mega links?
2. I flashed my so-04e previously in a similar procedure, but SOMEHOW corrupted my TA partition. I think it's the TA because the phone will not acquire a signal and when reflashing in flashtool one of the rolling messages is something about TA I never saw before. I'm wondering if maybe I'm bricked. I think it happened with I wiped the data partition in order for the phone to recognize the extra internal memory.
Click to expand...
Click to collapse
Jatyeo,
Regarding the second question, I have no idea. I am not technically informed, I just hammered together the tutorial based on what I could find here and there and made it consistent.
Regarding the first question, I did not realize that Mega downloads require a decryption key. Can you please try the following link and let me know if this works? The key is part of the link. This is the HK firmware.
https://mega.nz/#!R1p2wKII!rs9UFrMHN-nAnaROy-xe5gu1Zt52ipk-451sZEpzv34

This link works now, can you fix the rest?

All links updated, pls confirm back that they work for you.

All working

Nice work bro. Keep up the good work..

Any chance you speak Japanese?

By the way, the "above instructions" in 21 don't exist because the link is dead, I see you appended the file at the end of the description but there are no instructions.

jatyeo said:
By the way, the "above instructions" in 21 don't exist because the link is dead, I see you appended the file at the end of the description but there are no instructions.
Click to expand...
Click to collapse
I have no idea what you mean by this.
To answer your other question: yes, I speak Japanese.
And to answer your question from the other thread: as you can see, I am being very detailed with this tutorial. If there were any special points to keep in mind with the PureX ROM I link to in step 22, I would mention them. That is, as far as I know. I had no problems with it. It installed flawlessly and works great.

axel007 said:
I have no idea what you mean by this.
To answer your other question: yes, I speak Japanese.
And to answer your question from the other thread: as you can see, I am being very detailed with this tutorial. If there were any special points to keep in mind with the PureX ROM I link to in step 22, I would mention them. That is, as far as I know. I had no problems with it. It installed flawlessly and works great.
Click to expand...
Click to collapse
You were very detailed, thx (+Thx button =) )... but you've had to repost the many of the links because of issues and I'm saying 21 is no different; the link goes to a 404 error page.
The reason why I asked about Japanese is because there are some articles on fast tracking to lollipop I was curious to know your thoughts about...
http://doroid.org/2015/09/12/xperia-so-04ezr-c5503-5-1-1-根付いた/

jatyeo said:
You were very detailed, thx (+Thx button =) )... but you've had to repost the many of the links because of issues and I'm saying 21 is no different; the link goes to a 404 error page.
The reason why I asked about Japanese is because there are some articles on fast tracking to lollipop I was curious to know your thoughts about...
http://doroid.org/2015/09/12/xperia-so-04ezr-c5503-5-1-1-根付いた/
Click to expand...
Click to collapse
Now I get it. I don't know why these links become garbled like this. I tried to fix it, can you please check if it works for you now?
Regarding the Japanese link you gave above, I have no experience with this method. I am not sure he went to 5.1.1 from 4.2.2 directly.
I really don't have any particular technical knowledge. I'm just some guy who collected information from here and there, checked if it works (and it did for me) and summarized the steps he took. Half of the time I don't understand what I'm doing!

jatyeo said:
You were very detailed, thx (+Thx button =) )... but you've had to repost the many of the links because of issues and I'm saying 21 is no different; the link goes to a 404 error page.
The reason why I asked about Japanese is because there are some articles on fast tracking to lollipop I was curious to know your thoughts about...
http://doroid.org/2015/09/12/xperia-so-04ezr-c5503-5-1-1-根付いた/
Click to expand...
Click to collapse
Now I get it. I don't know why these links become garbled like this. I tried to fix it, can you please check if it works for you now?
Regarding the Japanese link you gave above, I have no experience with this method. I am not sure he went to 5.1.1 from 4.2.2 directly.
I really don't have any particular technical knowledge. I'm just some guy who collected information from here and there, checked if it works (and it did for me) and summarized the steps he took. Half of the time I don't understand what I'm doing!

axel007 said:
Now I get it. I don't know why these links become garbled like this. I tried to fix it, can you please check if it works for you now?
Regarding the Japanese link you gave above, I have no experience with this method. I am not sure he went to 5.1.1 from 4.2.2 directly.
I really don't have any particular technical knowledge. I'm just some guy who collected information from here and there, checked if it works (and it did for me) and summarized the steps he took. Half of the time I don't understand what I'm doing!
Click to expand...
Click to collapse
Thx
What do I exclude when upgrading to 5.1.1, are there any other tips?
This part is where I messed up y last phone, Thx

Exclude? This is a ROM that you flash in its entirety from your SD card. There are no options for exclusion...

What are Newest Xperia A Rom?

I am not sure I understand your question. DoCoMo only upgraded to 4.2.2. After that, you're on your own. That's what this tutorial is about. If you are asking what unofficial ROM is the latest, you can look that up for yourself over in the Xperia ZR development forum. But if you have no experience with custom ROMs, I would recommend you use the one I link to (PureX) as I can confirm that this is stable and works well.

Everything was going very well till step 20
my xperia just keeps on SONY logo screen
Edit/
now it goes till appears the XPERIA and reboot
cant acess the recovery mode

[FTF] C5503_10.7.A.0.222 Fix_for_ZRDocomo Android 5.1.1
[FTF] C5503_10.7.A.0.222 Fix_for_ZRDocomo Android 5.1.1
http://ouo.io/C0smHY
C5503_10.7.A.0.228_Fix_32Gb-ZRdocomo.ftf
http://ouo.io/C0smHY

How to force update to v. 47.2.A.2.33

Hi,
I have received an email notification from SONY stating that there was an update available for my device (v. 47.2.A.2.33) and described a few ways to proceed with the update - however, none worked. All methods stopped right in the beginning stating "no updates available".
SONY support could not help, either. They were asking me for patience until the update reaches me and I will be notified - but I had already been notified...
Anyway, is there a way to bypass the waiting line and force-get the version now, instead of waiting (who knows for how long)?
The device is an operator-free version, so I am not tied to any vendor mercy.
Thank you.
Kind regards,
Csani

Just use Xpericheck to download the firmware version you want. Then use NewFlasher to flash it.
No need to rooting, unlocked bootloader or anything fancy.

Csani said:
is there a way to bypass the waiting line and force-get the version now, instead of waiting (who knows for how long)?
Click to expand...
Click to collapse
Just upgrade it yourself, you won't damage the phone or change your warranty status.
Look on Xperiafirm and find a 47.2.A.4.45 buld that is for your region, although any EU region would be fine, US versions have fingerprint and VoLTE disabled for some reason. Customised version is a good option as doesn't contain any provider bloatware. My choice would be Customized DE.
Download Newflasher and put it in the same folder as the firmware you downloaded from Xperiafirm
Delete Userdataxxx.sin and files ending in .ta . This will ensure that you don't lose any personal data. Also delete persist*.sin to avoid losing android attest key.
Then start newflasher.exe and follow instrctions.
You might need a copy of the Sony driver
I would make a backup with Xperia transfer before you do anything, if the phone is glitchty after your rebuild, then factory reset it and then restore from the backup.

Can somebody tell me EXACTLY (or give me the link for it) the explanation of what's the difference between a regular stock rom and its Customised DE counterpart? It was my understanding deleting pre-installed apps like Facebook or Spotify (not just disable them) was impossible, flashing customised roms solves the problem?

Dany XP said:
Can somebody tell me EXACTLY (or give me the link for it) the explanation of what's the difference between a regular stock rom and its Customised DE counterpart? It was my understanding deleting pre-installed apps like Facebook or Spotify (not just disable them) was impossible, flashing customised roms solves the problem?
Click to expand...
Click to collapse
Customized DE is a regular stock rom. It just means that it's meant for the German market and not tied to any operator like Vodaphone etc. Customized UK would be for the UK market and so on.
There's not much difference between the customizations (although operator specific ones probably won't work with other ones and you shouldn't flash them). Some don't have all the features (US might not have fingerprint sensor enabled, some don't have VoLTE...). All have some preinstalled apps (or bloatware if you wish) mut the actual apps might vary - some have more, some less and some just ha e different useless **** instead of other.
So the "Customized xx" here refers to stock rom, not a custom rom. You can flash any Customized x for your phone even with a locked bootloader but "Custom ROM" like LineageOS or AOSPExtended would need an unlocked bootloader.
Also if you want to remove the bloatware completely you'll need root (and unlocked bootloader). But before you do that, please back up TA and read carefully about how it changes your phone in ways that can't be reversed.

Is there any other place to download the .ftf file?
Xpericheck.com redirects me to alfafile.net but I don't have premium account and cannot download the file

jelenn said:
Is there any other place to download the .ftf file?
Xpericheck.com redirects me to alfafile.net but I don't have premium account and cannot download the file
Click to expand...
Click to collapse
Pretty sure flashtool can make one from the files you download from Xperiafirm

Worked, thanks

vofferz said:
Customized DE is a regular stock rom. It just means that it's meant for the German market and not tied to any operator like Vodaphone etc. Customized UK would be for the UK market and so on.
There's not much difference between the customizations (although operator specific ones probably won't work with other ones and you shouldn't flash them). Some don't have all the features (US might not have fingerprint sensor enabled, some don't have VoLTE...). All have some preinstalled apps (or bloatware if you wish) mut the actual apps might vary - some have more, some less and some just ha e different useless **** instead of other.
So the "Customized xx" here refers to stock rom, not a custom rom. You can flash any Customized x for your phone even with a locked bootloader but "Custom ROM" like LineageOS or AOSPExtended would need an unlocked bootloader.
Also if you want to remove the bloatware completely you'll need root (and unlocked bootloader). But before you do that, please back up TA and read carefully about how it changes your phone in ways that can't be reversed.
Click to expand...
Click to collapse
So in customized I still have facebook, Spotify and all that crap? Too bad

Dany XP said:
So in customized I still have facebook, Spotify and all that crap? Too bad
Click to expand...
Click to collapse
Yes. And you probably have the "Customized xx" rom already on your device (unless you have an operator specific ROM).

Unofficial Unofficial TWRP and Gsi Android 11 or 12(kinda)

Hi guys. First post here and I'm not around my files so it will be a straight forward guide with no downloads right now, you're smart, you know where to source them...
Ok first and foremost, Unlock your bootloader, Motorola makes it easy and there are good guides on this site to do that.
Once your bootloader is unlocked your going to look for an Unofficial TWRP package for the Lenovo K12 Pro... "What?", You say... Yep K12 Pro. Download it and jump over to your boot loader and flash it or just boot to it through fastboot and now you have a way to install root permanently, or not if you would rather not, but you have that option now.
Next find the lastest Magisk apk and get that joker installed using TWRP. Now reboot into system and everything should load up as normal BUT now you have root with TWRP recovery. I have did this at least 100 times since figuring it out and sometimes I do this with a fresh factory flash and sometimes I do this as is without even wiping user data before or after. I'm no expert and I don't care to lose my files so on the rare occasion that I do have a boot loop or soft brick, I get myself into recovery and flash ANY of the cebu firmwares and do it all over again...
Ok, so now we know how to get root and custom recovery... Next find an AB version of Gsi 11 or "borrow" the latest system.img from an Android 12 update or firmware image and open up fastboot again and flash only the system.image to the system partition. Wipe or don't wipe, up to how lucky you're feeling, and then reboot to system... 11 will take 2-3 minutes to boot the first time and I had nearly all functionality when it did. 12, well, that's a little different, it took 3-4 minutes to boot to the setup screen and then lagged like crazy BUT it eventually started downloading a few files it was missing and got better. I couldn't get my calls or messaging to work right but I could hear my phone ring but it never called the phone app to open and let me answer... Weird stuff BUT FYI 12 is a pretty nice to look at OS and maybe one of you guys can take this to the next level and get some true usefulness out of it. I know it's not very technical but when one of you true geniuses try it and get it worked out please feel free to post a true guide with proper instruction and proper terms.
That's all I got guys. Thanks for reading this and ALSO if anybody has a complete list of fastboot and adb commands for the g9 Power or the K12 Pro please share them with me. I've gotten better at getting around but I'm not near as good as if like to be.

Obligatory safety PSA:
The Lenovo K12 Pro is just the Moto G9 Power sold under a different name, however, there could be minor differences that could cause problems.
Also, while searching for this unofficial TWRP build, I only found it on websites like unofficialtwrp.com, and the like. I couldn't find one on XDA. I was unable to find the device tree, or the kernel sources used by this website anywhere on the internet, and as such, the TWRP images provided on such websites are literal blackboxes.
TWRP images created and shared on XDA can be trusted, the source code used to create the image is displayed on the posts of the images, and XDA itself is a trusted site.
Here is what the official TWRP team have to say on the matter:
Unofficial TWRP Downloads
Like the TWRP team say, it is up to you to flash these images or not, but be careful.

mistersmee said:
Obligatory safety PSA:
The Lenovo K12 Pro is just the Moto G9 Power sold under a different name, however, there could be minor differences that could cause problems.
Also, while searching for this unofficial TWRP build, I only found it on websites like unofficialtwrp.com, and the like. I couldn't find one on XDA. I was unable to find the device tree, or the kernel sources used by this website anywhere on the internet, and as such, the TWRP images provided on such websites are literal blackboxes.
TWRP images created and shared on XDA can be trusted, the source code used to create the image is displayed on the posts of the images, and XDA itself is a trusted site.
Here is what the official TWRP team have to say on the matter:
Unofficial TWRP Downloads
Like the TWRP team say, it is up to you to flash these images or not, but be careful.
Click to expand...
Click to collapse
Agreed, I posted as a proof of concept so people with more know how could improve upon. Use this at your own discretion and have fun in doing so.

Is there a way you could post a detailed, step by step instructions of this, please?
I've found the unofficial twrp, but haven't rooted a phone in over 2 years, so I'm a bit rusty, plus things have changed a lot these last couple years.
I'd really appreciate if you could take your time for that.
Thanks in advance.

I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.

Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
That would be awesome mate!
I really appreciate that!
Thanks in advance.

Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
I was able to boot into TWRP but when I flash Twrp.img to recovery it won't stick, I always had to do fastboot into recovery if I try to boot into recovery it just reboots back into system, also can't remove any junkware from system, it always gives me error when I tried to remove it using root browser, im still on stock

zfk110 said:
I was able to boot into TWRP but when I flash Twrp.img to recovery it won't stick, I always had to do fastboot into recovery if I try to boot into recovery it just reboots back into system, also can't remove any junkware from system, it always gives me error when I tried to remove it using root browser, im still on stock
Click to expand...
Click to collapse
Check out https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-2-cebu.4279917/
for TWRP.
As for removing junkware, as you may or may not know, dynamic partitions is a thing since Android 10. In it, the /system, /product and /vendor partitions have been subsumed under a /super partition. And Google has conveniently used a type of ext4 filesystem for that /super partition, that is read-only.
TL;DR: You cannot modify Android using any sort of "root browser" or inside TWRP, for that matter, anymore.
Off the top of my head, the only way you can remove "junkware" is through some Magisk modules, and even they might not even work.

There are three ways to debloat AFAIK:
Magisk - this is my preferred method. You either replace apks you want removed or empty the /product/etc/nondisable folder so they can be disabled. Takes minimal effort to figure out how to make modules and no scripting knowledge required.
Cross-flashing - you can flash retail software, often including modem firmware, to most Moto phones. The result is a clean system with no carrier junkware.
System R/W Scripts - this is the most nonsensical of the options(IMO), but this option exists if you look around and want to experiment. The big drawback here is that you have to redo everything after every update.

Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
Hello. I know you're new and welcome. I just want you to know, being an unofficial twrp isn't necessarily bad by itself. It's that the sources can't be verified. Lots of devces don't have official TWRPs, yet still have a rockin development section with TWRP instructions, as long as it's shared on a trusted site (I only trust 1 other) and lists it's sources and, even then, it should have the warning. Lots of scam sites target root noobs, as you've probably noticed. I don't think sharing instructions would have been against the rules, but should include a warning to let people know it's a questionable twrp build and it poses a risk, but all of our phones are at risk anyway. We don't have to worry about it anymore though since we have an official and still we are at risk, just far less risk. It comes with the territory. On the other hand, I've been I've been doing this for a very long time with countless phones and I've never noticed any malicious activity on any on any of them.

Question Bootloader/Deeper functions access...

Ok... So while I acknowledge that this post isn't 100% about the OP 10pro ... It will have some impact if solved.
Basically I've found it... I've found out how Oppo is locking or removing the ability to unlock the bootloader of ALL of their phones that suffer from this. (Specifically the OnePlus 10T T-Mobile)
And realize that by helping solve this, I will be able to locate the file that is bricking all of our devices , when flashing different region fw.
(I said I wouldn't rest til I found it, and I have!).
They are simply appending the executable that launches the "Fastboot reboot bootloader" command, with an additional comment which adds another Reboot to the command.
So the phone basically receives "Fastboot reboot bootloader reboot" when we try to access it from adb.
(They made it so that simply invoking the word bootloader will trigger this to happen automatically and without any way to break the command up....)
^^ This function has a flaw though... Which is :. They put the instructions for where the command gets it's orders DIRECTLY into the android build properties. Which means it can be removed from the build prop and restore full functionality to the Fastboot protocol.
The problem lies in that there is no way to edit these properties without root access.... No bootloader means no root... And no root means no way to edit build properties .... This is something that I need your help with!
I know there are a plethora of devs and even tinkerers here who knows tricks to mitigate the security in order to write or amend the build.prop without having root ... I know that SOMEONE here might have a method that can do this. If someone is willing to offer that knowledge, they would be a god in my eyes and a savior to several ppl with an Oppo device that has no way to unlock the bootloader. I have checked several devices and this is the same method used on every one that has a "permanently locked" bootloader. It is just a few lines in the build properties that is disabling this.
Please help.... Pictures for proof of my discovery at bottom.
If you can find a way to edit these lines please dm me, or reply here... But please contact me!

Also be aware that Oppo has spies who pose as regular members on our site here, so if you are someone who might be interested in whatever solution comes about... I would highly recommend that you do not update your fw past the version you are on now. This goes for both Oppo and OnePlus users , because within 3 days of me revealing the method to switch region fw, OnePlus patched and removed the vulnerable rollback packages. So now that this has been brought to light, no doubt there will be a security update available within the next week or so, that has nearly nothing written in the changelog, but has the sole purpose of further hiding/blocking access to these settings.

This has ultimately been the reason I won't be purchasing the OnePlus 10 Pro, a Pixel is way superior at this point, however I will offer some advice.
Have there been attempts to use the QPST to overwrite partitions? I always thought that if someone made an MSM Tool with, for example, LineageOS in place of the partitions, that perhaps one wouldn't need to unlock their bootloader? Of course, the file would have to be encrypted the way that OPlus does it, but I thought it was plausible? I tried, but failed because the tool I was using kept not encrypting the files I was selecting, it only included a few in the final package.
I digress, I'm aware of someone saying that the partitions are different with the OnePlus 10 Pro, but would it be possible to kind of work backwards to reach the goal using Fastboot?

hammerhaigh said:
This has ultimately been the reason I won't be purchasing the OnePlus 10 Pro, a Pixel is way superior at this point, however I will offer some advice.
Have there been attempts to use the QPST to overwrite partitions? I always thought that if someone made an MSM Tool with, for example, LineageOS in place of the partitions, that perhaps one wouldn't need to unlock their bootloader? Of course, the file would have to be encrypted the way that OPlus does it, but I thought it was plausible? I tried, but failed because the tool I was using kept not encrypting the files I was selecting, it only included a few in the final package.
I digress, I'm aware of someone saying that the partitions are different with the OnePlus 10 Pro, but would it be possible to kind of work backwards to reach the goal using Fastboot?
Click to expand...
Click to collapse
well kind of... now i invite anyone to correct me here if i am stating something wrong, but it is my understanding that QPST/QFIL cannot write to individual partitions unless the instructions are defined in the rawpartition.xml, and patch.xml files.... because those are what the firehose loader parse to get the layout of what needs to be written to the phone. Like the partition tables are in the firehose i think, and the stuff that goes into each are in those xml files....
now if im correct then thats not the deal breaker... the deal breaker comes in the Firehose itself. ANY usage of a qualcomm flash tool, whether it be QFIL, QPST, MSM or any other, all require communication via a Sahara_Firehose... and in that sense, we dont have a Qualcomm Patched Firehose yet. So the firehose that comes in the fw packages has a security function called VIP mode built in, which performs some on board checks to validate the fw signature.
For this very reason, having Fastboot access sit on top of the throne for methods in which to mess with anything fw related.
Oxygen Updater - Has no direct flashing capability, only the ability to download any official OTA fw.
Local Update - Can flash pretty much anything, as long as it is in Payload.bin format, and the hash . . . . . . . .. . . . .. .. matches a valid package
System Update - will ONLY flash a package that is downloaded directly thru it, which eliminates customs.
Fastboot - Can flash payload.bin, or if the bootloader is unlocked it can flash individual .img files. Thus . . . .. . . . . . . .making it the most powerful tool we have at our FREE disposal.
With fastboot, and a flash of VBMeta, to disable Verity checks, along with "Unlock critical" , you can pretty much access every partition in the system without limits... and also this is the only way to gain root access, which as we all know is the MOST powerful of elevations, Writing anything TO the system partition requires a remount to R/W of the system partition, and that simply cannot be performed without Root.
So technically, fastboot access is the only thing we have that can give us a tool (root) with the freedom to make persistent changes to any partition on the device.

Database Develop

welcome