Related
Installing Cyanogenmod From another ROM
For all the people who have a stock/stock based ROM and want to move to Cyanogenmod!!!
Note: You must have a rooted phone with an unlocked bootloader for this. Search for threads on guides for rooting and unlocking bootloader and finish that first. Try using flashtool for both. Its the easiest method. Search for Flashtool guide.
You are probably still on the Stock Sony Ericsson ROM if you have just unlocked your bootloader. If not, then its best to revert to the stock SE ROM before installing a Cyanogenmod simply because many custom ROMs change the device name, model name etc. found in you device's build properties file (build.prop) Cyanogenmod requires it to be an X10i or X10a.
IF NOT ON STOCK ROM:
Using SEUS/PC Companion
To get back to the SE 2.3.3FW, install SEUS, connect your phone to your PC and once it detects your phone, click on the update software/"your phone is already up to date" or whatever that is shown at the top. If it says it is up to date, click on "repair" and follow the instructions.
You can also edit the build.prop file in /system instead of using SEUS.
Using the build.prop edit method: (MIGHT NOT WORK. I REQUEST SENIOR DEVELOPERS TO VERIFY IF THE METHOD WORKS AS I HAVE NOT TRIED IT MYSELF)
Download Root Explorer or any other File manager that lets you browse root with RW permissions.
Go to /system using the file manager and create a backup of the "build.prop" file by simply copying it and pasting it on your sd card. Now open the original "build.prop" file with a text editor (Included in all ROMs)
Edit the following properties: ro.product.name, ro.product.model, ro.product.device to look like:
ro.product.name=X10i
ro.product.model =X10i
ro.product.device=X10i
or X10a as per your location.
Restart the phone, go to settings and check the model in about. It should show X10i/X10a depending on the changes you made.
ENSURE THAT YOU HAVE THE FOLLOWING REQUIREMENTS:
Stock SE ROM and kernel
Rooted
Unlocked Bootloader
next step:
Installing Cyanogenmod
1. Download the CM7/CM9 zip file from the CM thread.
a. Extract the kernel.sin from the CM zip file to any folder on your PC.
b. Open flash tool and under the advance tab, select bundle creation.
c. Now in the box that comes up, navigate to the folder where you extracted the kernel. Select the kernel.sin file shown in the lower left part of the window and click on the "-->" icon.
d. Fill up the device version, branding etc. and click ok. Now it will ask you the device model and then the boot loader status. Select the X10 as device model and click ok. Then select unlocked bootloader click ok.
e. The kernel ftf file has been created and stored in flashtool's default folder.
2. Put the CM7/CM9 zip file as it is onto your sd card along with any appropriate fixes and addons provided on the CM thread.
for example:
a. FXP122_update-cm-9.0.0-RC0-es209ra-UNOFFICIAL-signed
b. gapps-ics-20120317-signed
3. Flash the ftf file that you bundled earlier to your phone using flashtool.
4. Disconnect your phone and switch it on. Press the back button when the purple light comes on.
5. In CWM, format:
a. System (not necessary as the installation is set to do this anyway)
b. Data
c. Cache
and then mount them (MOUNT SYSTEM, MOUNT DATA, MOUNT CACHE) (not necessary to mount system as the installation is set to do this anyway)
if successful, these options should change to:
UNMOUNT SYSTEM
UNMOUNT DATA
UNMOUNT CACHE
(Leave them mounted)
6. Go to Install custom zip and browse down to the ROM file (for example FXP122_update-cm-9.0.0-RC0-es209ra-UNOFFICIAL-signed) and install it.
7. Reboot System. Then play around with the settings for a while and then reboot the phone and get back into recovery mode.
8. wipe cache partition. wipe dalvik cache and then install the fixes/addons.
9. Swtich on the phone and ENJOY!!!!
FAQ:
Q : Why do I need to revert to stock or change the build.pro to X10i / X10a
A : CM needs to recognize your phone as an X10i / X10a.
Q : Can I restore apps with Titanium Backup?
A : Yes you can, but some of the apps may not be supported on ICS.
Q : Can I restore contacts and message?
A : Yes, you can use apps such as My Backup/SMS Backup & Restore etc to do this.
Q : Can I use Cosmic Flow Live Wallpaper?
A : Yes. Someone has posted a working version. Search
Q : Is the ROM Smooth?
A : It is smooth. But it might not be as smooth as some ROMs running on overclocked kernels as the CM kernels aren't overclocked that much.
Q : Is everything working in Cyanogenmod?
A : Check the CM threads for info. As of now Camera is not working on CM9 (ICS) as the sources are not available. No third party app will be able to access camera either.
I request developers to verify my guide and let me know if any step is wrong.
Thank you . Nice way better then my one cuz my is only for Ferlab v20 Unlimited .
thanks. If u notice someone having installation errors could u guide them here plz?
It would be better if the developer's pages r not filled with guides hehe..
Also if u can add tags for this guide it would be gr8
Sent from my Xperia X10 using XDA
Installation aborded.
6. Go to Install custom zip and browse down to the ROM file (for example FXP122_update-cm-9.0.0-RC0-es209ra-UNOFFICIAL-signed) and install it.
Click to expand...
Click to collapse
Hi, when I try to do this on my xperia x10, CWM cannot find E:res/keys files.
--Installing: /sdcard/FXP124_cm-9-20120609-UNOFFICIAL-es209ra.zip
Finding update package...
Opening package...
Epening /res/keys: No such file or directory
E:Failed to load keys
Installation aborded.
Click to expand...
Click to collapse
Same problem
Zekke95 said:
Hi, when I try to do this on my xperia x10, CWM cannot find E:res/keys files.
Click to expand...
Click to collapse
Hi, i've had the same problem trying to instal "update-cm-7.1.0-X8-signed" on a Sony xperia X8. Were you able to solved the issue?
please help me to resolve x10 flashing issue
--> Xperia x10, flashed with 2.3.3
--> Rooted , installed xrecovery
--> Locked boot loader
Steps followed to install FeraLab v29
-------------------------------------------
1. Booted into xRecovery
2. Install custom ROM
3. Chosen FeraKernel.zip
Failed on certification issue
then Installed CMW recovery, Could not flash ferakernel
Tried to flash Feravolt v29 ROM it works, but stays in SE logo in 1st reboot..
Please help me...
Error while trying to flash kernel
Hi,
I keep getting an error when trying to flash a kernel, see down:
21/002/2013 10:02:38 - INFO - Device connected in flash mode
21/002/2013 10:02:38 - INFO - Opening device for R/W
21/002/2013 10:02:38 - INFO - Reading device information
21/002/2013 10:02:38 - INFO - Phone ready for flashmode operations.
21/002/2013 10:02:38 - INFO - Current device : X10i - CB511NEUQW - 1235-7836_R1C - 1227-4612_3.0.1.G.0.75 - WORLD-1-4-8_3.0.1.G.0.75
21/002/2013 10:02:38 - INFO - Processing loader.sin
21/002/2013 10:02:38 - INFO - Checking header
21/002/2013 10:02:38 - INFO - Flashing data
21/002/2013 10:02:42 - INFO - Loader : S1_Loader_Root_f851 - Version : R4A024 / Boot version : R8A013 / Bootloader status : UNROOTABLE
21/002/2013 10:02:42 - INFO - Start Reading unit 00000851
21/002/2013 10:02:42 - INFO - Reading TA finished.
21/002/2013 10:02:42 - INFO - Ending flash session
21/002/2013 10:02:42 - INFO - Waiting for device to reboot
21/002/2013 10:02:42 - INFO - Waiting for device
21/002/2013 10:02:42 - INFO - Device connected in flash mode
21/002/2013 10:02:43 - INFO - Device disconnected
21/002/2013 10:02:44 - INFO - Device connected in flash mode
21/002/2013 10:02:54 - INFO - Selected x10 / 0.2 / Somc Debrand Engine v0.2
21/002/2013 10:02:54 - INFO - Preparing files for flashing
21/002/2013 10:02:54 - INFO - Please connect your device into flashmode.
21/002/2013 10:02:55 - INFO - Opening device for R/W
21/002/2013 10:02:55 - INFO - Reading device information
21/003/2013 10:03:00 - INFO - Unable to read from phone after having opened it.
21/003/2013 10:03:00 - INFO - trying to continue anyway
21/003/2013 10:03:00 - INFO - Start Flashing
21/003/2013 10:03:00 - INFO - Processing loader.sin
21/003/2013 10:03:00 - INFO - Checking header
21/003/2013 10:03:05 - INFO - Ending flash session
21/003/2013 10:03:05 - ERROR - Error in processHeader : 995 : Der E/A-Vorgang wurde wegen eines Threadendes oder einer Anwendungsanforderung abgebrochen.
21/003/2013 10:03:05 - ERROR - Error flashing. Aborted
21/003/2013 10:03:05 - INFO - Device disconnected
21/003/2013 10:03:06 - INFO - Device connected with USB debugging off
21/003/2013 10:03:06 - INFO - For 2011 devices line, be sure you are not in MTP mode
21/003/2013 10:03:21 - INFO - Device disconnected
21/003/2013 10:03:25 - INFO - Device connected with USB debugging off
21/003/2013 10:03:25 - INFO - For 2011 devices line, be sure you are not in MTP mode
21/003/2013 10:03:39 - INFO - List of connected devices (Device Id) :
21/003/2013 10:03:39 - INFO - - USB\VID_0FCE&PID_E12E\CB511NEUQW Driver installed : true
21/003/2013 10:03:39 - INFO - List of ADB devices :
21/003/2013 10:03:39 - INFO - - none
21/003/2013 10:03:39 - INFO - List of fastboot devices :
21/003/2013 10:03:39 - INFO - - none
There it says:
ERROR - Error in processHeader : 995 : Der E/A-Vorgang wurde wegen eines Threadendes oder einer Anwendungsanforderung abgebrochen
I have no clue about the reason. Can sombody hint me, why it happens?
What is worng here, is the ftf damaged?
I would appreciate any help, even more detailed questions.
Alexej
fastboot is only enabled when the bootloader is unlocked.
ask installCM 11
can I use android system recovery for installing cyanogenmod 11 zip file?
failed to load keys
how to fix this thanks
Finding update package...
Opening package...
Epening /res/keys: No such file or directory
E:Failed to load keys
Installation aborted.
zakkymoy said:
how to fix this thanks
Finding update package...
Opening package...
Epening /res/keys: No such file or directory
E:Failed to load keys
Installation aborted.
Click to expand...
Click to collapse
What kernel do you use ? If you want to install Cyanogenmod's kernel, you should have a FTF file in the root of the zip. Extract the FTF and flash it to your phone with Flashtool and retry.
How to get rid of the "E:Failed to load keys" error.
For those who may be wondering how to get rid of the "E:Failed to load keys" error feedback, just disable the key verification through "toggle signature verification", in "advanced", via Recovery Mode. Sorry for replying to an old topic, but in my opinion it's for a great reason.
Zip files
acaciosc said:
For those who may be wondering how to get rid of the "E:Failed to load keys" error feedback, just disable the key verification through "toggle signature verification", in "advanced", via Recovery Mode. Sorry for replying to an old topic, but in my opinion it's for a great reason.
Click to expand...
Click to collapse
Hi, do you happen to have any of the zip files mentioned in this thread --- Especially CM11, if possible?
Force-Encrypt Toggler
Disclaimer: I have no experience in Android/ROM development. This is the first time i decided to share something (that i initially made for myself). Flash at your own risk. I am not responsible for boot loops, unexpectedly encrypted partitions, data loses, etc. Make sure you have a backup first!
Click to expand...
Click to collapse
Now that CyanogenMod developers stated that they are going to follow Google's guidelines about forced encryption in their ROM for Nexus 9, those of us who want their tablets unencrypted will have to flash a modified boot image every time they update CM. I hate doing such things manually every time, so i created a patch that disables forced encryption the right way - flash once and forget forever.
force-encrypt-toggler reads and unpacks your boot image, patches the ramdisk, creates a new boot image and flashes it back to the boot partition. And all that is done right on your tablet. Than it uses CM's addon.d framework, so that each time you flash a new CM zip, force-encrypt-toggler is invoked automatically to patch the newly flashed boot image. Thus, you can just upgrade through CM's built-in updater and everything will be patched automatically every time . Also, the script itself can be used on any Linux computer to patch (probably) any boot.img you have.
Thus far i have used it on my Nexus 9 to stay unencrypted starting from 20150216 through 20150224 nightlies. It seems to be quite stable, i believe . See some notes in the second post.
Download
force-encrypt-toggler-1.1-flounder.zip : https://goo.gl/bw7YDq
force-encrypt-toggler-1.1-flounder-dbg.zip : https://goo.gl/95JN34 - this one creates log files in /cache every time
force-encrypt-toggler-1.1-linux.tar.gz : https://goo.gl/3PF6ru - to be used on a desktop to patch arbitrary boot.img
old versions (for CM12): https://goo.gl/125eey
Sorry, it looks like i can not post clickable links yet. Remove space between "https" and colon.
Compatibility
I have tested this script only on my Nexus 9 Wi-Fi with TWRP recovery and CM stock boot image. However, i believe that it should be possible to make it work on other devices (e.g. Nexus 6) by just changing a few constants at the beginning.
Version 1.1 requires TWRP version >= 2.8.7.1 and a CM13 nightly >= 20160110. Version 1.0 will work for CM12.x (but not for recent CM13 nightlies).
Known issues
The addon.d script uses a dirty hack to trick the recovery. While this never happened to me, if you ever encounter a strange recovery behavior regarding installation or backup of boot images after flashing CM zip over CM with this mod, this might be it. Just reboot and it should be ok. See the second post for more info.
If CM changes something in their updater or if something changes in the recovery, this mod may easily break due to the hack mentioned above. Read the disclaimer.
Each time you flash a CM zip over a CM installation with this mod installed, TWRP recovery will hang for 5-10 seconds after reporting successful completion and before showing buttons at the bottom (or before rebooting in case of open recovery script execution). It is possible to fix this easily, but than this mod might be much easier to break.
Installation
First, you should read the disclaimer above and backup your data. Than you just have to flash the zip you downloaded with TWRP recovery. CyanogenMod must be installed first. If your /data is currently encrypted, you will have to do a full factory reset to decrypt it (backup your data first!).
Your current boot image will be patched during installation process (it should not hurt, if it's already patched). In case if something goes wrong, installation script will tell you. In any case you can get force-encrypt-toggler debug output by something like:
Code:
adb pull /tmp/fet.log
Be sure to do this before you reboot, because that file is created in the RAM.
Removal
In order to remove force-encrypt-toggler you have to delete the following files from your /system partition:
Code:
/system/xbin/mkbootimg (v1.1)
/system/xbin/unpackbootimg (v1.1)
/system/bin/force-encrypt-toggler
/system/addon.d/90-force-encrypt-toggler.sh
/system/bin/mkbootimg (v1.0)
/system/bin/unpackbootimg (v1.0)
And than restore your original boot image. You can also just format /system and flash CM again, but that is such an overkill .
Usage
Normally you will not need to run force-encrypt-toggler yourself, but in case you need, you should be able to run it both in Android and in recovery via adb shell. Just run it with --help option to see what it can do. In case you will have to debug some glitches, this command may be useful:
Code:
force-encrypt-toggler --set-not-forced --debug --dry-run --no-cleanup
If you use it on a Linux computer, this is what you will probably need:
Code:
sudo ./force-encrypt-toggler --set-not-forced [ --input path/to/boot.img --output path/to/new/boot.img ]
Note that Android and computer versions are functionally equivalent, so you can theoretically patch boot images for one Android device on another one...
Changelog
Code:
v1.1
+ use toybox instead of busybox because CM now ships only the later
+ mkbootimg and unpackbootimg are now installed to /system/xbin
+ the --help option can now be used without root privileges
v1.0 - initial release
Credits
mkbootimg is built from AOSP source
unpackbootimg is taken from this GitHub page: https://github.com/Dees-Troy/unpackbootimg
update-binary is taken from a CM zip
There is one problem with patching the new boot image from an addon.d script: CM's updater-script flashes boot image after it invokes all addon.d scripts. Therefore at a time, when the script is called, it is possible to patch only the old boot image, and than it will still be overwritten anyway. In order to overcome this, i used a very dirty hack. In short, i replace the device node with a fifo and let the updater write new boot image into it, and than... Ok, so, i think there must be a cleaner solution, so i will appreciate if a more experienced developer takes a look at my code and proposes a better solution.
As for the 5-10 second hang, it is (unexpectedly) caused by that line with "sleep 15" at the end of addon.d script. If it really annoys you, you can comment it out along with the line, where force-encrypt-toggler is called directly (not through the helper script). Updating will be a bit faster than, but if CM devs ever decide to flash boot image prior to calling addon.d scripts, you /data will be silently encrypted.
Download :: For the lazy
force-encrypt-toggler-1.0-flounder.zip : http://goo.gl/N4rZDk
force-encrypt-toggler-1.0-flounder-dbg.zip : http://goo.gl/4nXmkD - this one creates log files in /cache every time
force-encrypt-toggler-1.0-linux.tar.gz : http://goo.gl/hDFNOY - to be used on a desktop to patch arbitrary boot.img
While there was zero discussion in this thread, goo.gl tells me that there was some downloads, so someone might be actually using my small mod. If so, they might notice that it got broken around one month ago. So i decided to share a fixed version. See updated links in the description (links in the USBhost's post above are for the old version, if you wonder).
If you currently have v1.0 installed, you can just flash v1.1 over it. Note however, that if you was flashing recent nightlies while using v1.0, you /data probably have been silently re-encrypted. Also, if you current boot image is patched by v1.0, the initial patching by v1.1 during zip installation will fail, but it should work during system updates afterward. Flash stock boot image and try again if you want to be sure.
The reason for v1.0 malfunction was that around a month ago CM13 stopped shipping busybox in favor of toybox. New version is only compatible with CM nightlies >= 20160110. Also you need TWRP >= 2.8.7.1.
I never took notice to this thread before until your post in the FED thread. I am going to keep an eye on it as I have been issued lately with the FED patch saying that my device is not supported (Nexus 9 Wi-Fi). Hopefully I will have better luck with this. Thank you for sharing your.
TWRP for Z1c amami & Z1 Honami
Thanks to @funiewski who inspired me/ teached me how to repack Z2 twrp to work with z1 and z1c.
This ain't my work! I've just been cooking with projects made by others. Thank TeamWin, [NUT], creator of Android Image Kitchen, and others
Use at your own risk!
Download:
TWRP_v2.8.6.0_amami-f2fs_from_cm12.1_150423.img 11.6 MB - https://mega.co.nz/#!3gRwGZiK!sXMsMx1GGwUVkTCCsr8ntZekCE-o-hB4DDp6wlhVQqA
TWRP_v2.8.6.0_honami-f2fs_from_cm12.1_150423.img 11.6 MB - https://mega.co.nz/#!qkp0jDRR!cqRQ-8CkfFmR6SJyGMCtWr2Rn89FTRl3dUNxluUWDxs
What is this?
This is a repacked TWRP from Z2 sirius, where I have:
- Replaced "default.prop" and "res"-folder to one from [NUT] dual recovery for Z1/Z1C
- Added f2fs support by adding mkfs.f2fs from CM nightly dated the day I cooked the recovery.
- Shrinked images in twres/images folder. It wouldn't boot otherwise.
More info? See recepy down below
Works for?
ONLY: Unlocked bootloader, AOSP based ROMs with support for booting a recovery from the FOTA partition.
Stock ROM, locked or unlocked bootloader: See [NUT]s project: http://nut.xperia-files.com/
How to install?
There are many ways in doing so. Fastboot: "fastboot flash recovery nameofrecovery.img" is the easiest IMO
Bugs?
Me and others have tested it, only bug atm seems to be:
- Can't adjust screen brightness in TWRP
Report if you find anything
Can you fix bugs?
Most probably not. If you find bugs regarding layout, images and stuff like that: Maybe.
This is not compiled for Z1, this is just repacked using Android Image Kitchen.
Bugs in this recovery will most probably be bugs that all TWRP builds share.
Recepy
Just repacking the Z2 recovery won't make it boot on Z1/Z1c. I believe this is due to some limitations regarding size or something.
In order to get the file size down I made a new, simple "curtain.jpg". Plain black with the text "TWRP". Kind of clean and simplistic when I think about it And I found out that these PNGs can be compressed without getting grapchical glitches:
Code:
- file.png
- folder.png
- keyboard (all)
- medium-button.png
- menu-button.png
- slideout.png
- slider-touch.png
- slider.png
- unlock.png
How I did it:
- DL TWRP for Z2 (sirius), [NUT]s lates flashable build for Z1c, Z1, and Android Image Kitchen
- Unpack TWRP for Z2 with Android Image Kitchen
- Take default.prop and "res"-folder from [NUT]s latest build, for your respective phone (z1/z1c), and copy this to the place you unpacked the Z2 recovery (inside ramdisk folder)
- Change images in "twres/images" with these (they are compressed. Unless you use them the img won't boot: https://mega.co.nz/#!e9g1TRCI!vmGsPqVdqSnpcW6G8PC_saLLyyfqTL-1FhjQmggVvxA)
- Repack with "Android Image Kitchen".
Add F2FS support:
- DL lates CM nightly
- Unpack boot.img from it, using Android Image Kitchen.
- Use 7zip to open sbin\ramdisk-recovery.cpio. Get the "mkfs.f2fs" from sbin folder.
- Add this to your project: Copy mkfs.f2fs to ramdisk\sbin
- Repack your recovery with "Android Image Kitchen".
If you want to manually edit default.prop:
Z1 Info: http://www.gsmarena.com/sony_xperia_z1-5596.php - Honami, C6902, DPI: 480
Z1c Info: http://www.gsmarena.com/sony_xperia_z1_compact-5753.php - Amami, D5503, DPI: 342
Z2 Info: http://www.gsmarena.com/sony_xperia_z2-6144.php - Sirius, D6503, DPI: 424
Guides:
Migrate to f2fs: http://forum.xda-developers.com/showthread.php?t=3004755
How to use f2fs on Sony Devices: http://forum.xda-developers.com/showthread.php?t=3056740
It's said that CM12 supports f2fs now. I haven't tested myself yet, so can't confirm.
it works great for me.nice work
Perfect exacly what i am looking for...
Flashed it and works nice, hope to see also updates in future.
Thank you :good:
How to enter in recovery?
nArdow said:
How to enter in recovery?
Click to expand...
Click to collapse
On sony logo at boot, press volume up. Led will turn from indigo/violet to orange.
Introduction & Notes
Hello, I have created flashable zips containing the stock things for use with our Xperia SP. I used @MrSteve555's antique tutorial on how to package an ftf file into flashable zips.
I also made other might be useful zips that have each of their own purposes for those who wants it. Those zips are listed in the Addons Zip post.
As usual, I am not responsible for any damages caused on your SP. Flashing these are completely your choice and did I even forced you to do so? If you need help, just reply in the thread. :angel: As much as this might scare you, don't worry, it should work fine on your device
All zips are taken from FTFs that are not carrier-locked (thus the name Customised). Since the C5306 is a quite rare variant, the only version I can find that is not carrier-locked is the .205.
Steps
What you should do is choose the respective components that you want to flash to your phone. This will ultimately replaces the old one. Say for example, if you want to have the stock fotakernel, all you need to do is to flash the "fotakernel" zip. This will override any previous modifications that you have made on that partition such as custom recoveries.
Done.
Notes & Warnings
Warning!
The files are exclusive for its Xperia SP model. Do not attempt to take the risk in flashing other version for your Xperia SP model.
The stock kernel is not to be flashed if you are running a custom ROM! (yes, you can still safely flash FOTAKernel and RIL components without any harm)
Note!
Flashing the zips via Cyanogen Recovery is now possible. The zips are signed.
Requirements
Knows how to flash ZIPs via recovery
Knows what to flash
Acknowledged the disclaimer above
Components
These are the partitions that I have extracted:
boot
fotakernel
elabel *
modemst1 *
modemst2 *
fsg *
I didn't include the "system.img" of the stock ROM. If you intent to use Stock ROM, please consider FlashTool method instead.
* I have combined these 4 components in a single zip as they serve the same purpose: RIL (network)
Purpose of each zip files
c530x-stock-fota.zip - This will replace your current fotakernel partition with the stock one. Any custom recoveries that you have flashed using Rashr will ultimately gone.
c530x-stock-kernel.zip - This will replace your current boot partition and the kernel with the stock one. Any custom kernel that you hace flashed will be replaced.
c530x-stock-ril.zip - This will flash the stock RIL components.
Choose your Xperia SP model
This will bring you to the respective posts that contains respective files for your respective model of your Xperia SP.
C5303
C5302
C5306
Alternative install method for terminal enthusiasts
You can extract the zip and "dd" the img to the respective directories in /dev. This section is for terminal enthusiasts so I assume that you guys know where is this located and also knows what the hell is "dd". I suggest for the "dd" to use read block of 4096 for faster flashing process.
Example terminal command:
Code:
dd if='Kernel.elf' of='/dev/block/platform/msm_sdcc.1/by-name/Kernel' bs=4096
Here is the list for reference:
Kernel.elf ----> /dev/block/platform/msm_sdcc.1/by-name/Kernel
FOTAKernel.elf ----> /dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
LTALabel.ext4 ----> /dev/block/platform/msm_sdcc.1/by-name/LTALabel
modemst1.img ----> /dev/block/platform/msm_sdcc.1/by-name/modemst1
modemst2.img ----> /dev/block/platform/msm_sdcc.1/by-name/modemst2
fsg.img ----> /dev/block/platform/msm_sdcc.1/by-name/fsg
Click to expand...
Click to collapse
One small request from me
If this in some ways helped you, consider thanking this main post Your thank can hugely motivates me in contributing more!
C5303
This section is for the the C5303 model only
NOTES
Please read the main post if you haven't read them!
For this model, I have used Customised Singapore 12.1.A.1.207 / R2B CDA 1272-4881
Whole Folder [Google Drive]
FOTAKernel c5303-stock-fota [Download]
Kernel c5303-stock-kernel [Download]
elabel, modemst1, modemst2, fsg combined c5303-stock-ril [Download]
C5302
This section is for the the C5302 model only
NOTES
Please read the main post if you haven't read them!
For this model, I have used Customised Singapore 12.1.A.1.207 / R2B CDA 1272-3116
Whole Folder [Google Drive]
FOTAKernel c5302-stock-fota [Download]
Kernel c5302-stock-kernel [Download]
elabel, modemst1, modemst2, fsg combined c5302-stock-ril [Download]
C5306
This section is for the the C5306 model only
Please read the main post if you haven't read them!
NOTES
Please read the main post if you haven't read them!
For this model, I have used Customised US 12.1.A.1.205 / R3B CDA 1272-4529
Whole Folder [Google Drive]
FOTAKernel c5306-stock-fota [Download]
Kernel c5306-stock-kernel [Download]
elabel, modemst1, modemst2, fsg combined c5306-stock-ril [Download]
Addons Zip
Unrelated flashable zips that might be useful
Folder for Downloads
AdAway Generated Hosts [4.1+] *
[ Download ] Replaces the standard hosts file in /system/etc/hosts with the one generated by AdAway. Could ease your life and save yourself a reboot if you flash this after flashing an update to your ROM. This zip file will get updated when there is a new hosts file update by AdAway. You can check by looking at the text file's name from within the zip file).
ViPER4Android [5.0+] *
[ Download ] This will flash ViPER4Android as a system app. It doesn't end there, it will also push an supolicy that enables you to use V4A with an Enforcing SELinux, it will install the drivers automatically for you, it will remove AudioFX, and all of these will persist on a ROM update (aka dirty flash)! Thanks to the help of @Tomoms, @Arvind7352, @shavendum, @Zenith and @akashsaini7 . Without their help this wouldn't probably happen at all
Android N Emojis [5.0+] *
[ Download ] This will flash the Android N emoji support to your current Andorid version. Note, you can only display the new unicode 9 emojis on the device (no more squares), to actually write them, you will need a keyboard that can already write the new emojis (which most still aren't). Should be compatible with Lollipop and newer, and not for KitKat and below. Tested on Marshmallow.
Remove AudioFX [5.0+] *
[ Download ] Removes AudioFX from your CM-based custom ROM to make way for your preferred sound mod. No more hassle to freeze AudioFX using TiB (or any other freezing tool)
Persisting Walkman [5.0 - 5.1] *
[ Download ] This will flash a file into addon.d folder to make sure that your Walkman and sound effects stays on the ROM when you dirty flash an update. This flashable zip however only compatible with [port][LP] Xperia Sound enhancement by @ankurjn364. Note that this port is only for Lollipop ROMs.
Xperia SP Boot Animation [4.1+] *
[ Download ] Get yourself the original Xperia SP Boot Animation!
Xperia Z5 Boot Animation [4.1+] *
[ Download ] Get yourself an Xperia Z5 Boot Animation! Thanks to @xkeita for porting the Xperia Z5 Boot Animation, especially for creating it for the 720p screen! Please leave a thank to xkeita on the original thread: Xperia Z5 bootanimation for Xperias!
Xperia X Boot Animation [4.1+] *
[ Download ] Get yourself an Xperia X Boot Animation! Thanks to @chitshiv for porting the Xperia X Boot Animation, especially for creating it for the 720p screen! Please leave a thank to chitshiv on the original thread: [MOD] Xperia X Series Bootanimation
* Note
The addons with the star means that the zips will push a backup script into the addon.d folder. This means the files flashed onto the system will survive a dirty flash, granting your modifications to the system persisting.
This will not work if you wiped your /system partition. If you did that, you will need to flash the zips again.
If you dislike this, you can simply delete the scripts that starts with "ts-" located in "/system/addon.d/".
Cool! I added a link to this thread in Tangerine's 1st post. It might be useful for those seeking for a stock FOTAKernel
Tomoms said:
Cool! I added a link to this thread in Tangerine's 1st post. It might be useful for those seeking for a stock FOTAKernel
Click to expand...
Click to collapse
Thank you so much for that! :highfive: :victory:
Update!
All models' respective files are now available
Update!
Now all zips can be flashed on CyanogenRecovery! Thank you so much for @Tomoms in helping me to sign the zips
Update!
All stock components updated with a new supposedly "output design"
Nothing is changed in the original files, it is just that I have changed the log output of the flashable zips so it looks pleasing to the eyes. Also I am now able to make use of the TWRP progress bar thanks to my brain for finally understanding the "set_progress()" Edify syntax
Two new zips added in the Addons zip section
adaway.zip
stock-rom-bootanimation.zip
[ Head on directly to the #5 post ]
Update!
New file name prefix for the Addon zips
Some zips now have the "ts-" prefix in their names
Two new zips added in the Addon zips section
Persisting Walkman
Persisting Xperia Keyboard
[ Head on directly to the #5 post ]
Backup scripts for persistence on ROM update!
AdAway Generated Hosts
Remove AudioFX
Persisting Walkman
Persisting Xperia Keyboard
These flashable zips now have a backup script included with them. This will make the modification on your system stays when you dirty flash a ROM update. Really useful if you prefer having a shorter time on flashing a new update for your current ROM
Update!
New zip added in the Addon zips section!
Xperia Z5 Boot Animation
[ Head on directly to the #5 post ]
New console output design
Well, when you flash a zip, there will be output texts on the screen. I changed the design a bit lol
No more pause
ZIPs will flash instantaneously as "sleep()" functions has been removed in all ZIP's updater-script. This is not really a new change, as I have silently removed it weeks ago. But I think it would be good to write it here
Updated hosts file for AdAway Generated Hosts
Also for those who uses this zip, I always update this zip whenever there is an update from the AdAway app.
Announcement
Currently the files are unaccessible due to CubeServer went off from the face of the Internet. I will upload to another cloud storage soon after collecting all the FTFs and extract them all.
Still can't download, can you solve please?
VladHD said:
Still can't download, can you solve please?
Click to expand...
Click to collapse
I am currently dealing with this. Expect them files available soon. I will edit this post when it is done
EDIT: Now all are updated
Update!
New Xperia Keyboard!
Also included is the Xperia X boot animation.
Updated all mirrors, now on Google Drive
I am very sorry for being very late in updating those mirrors. A few days or so before CubeServer went down, I also did something very irreversible on my HDD, thus making me lost all of the files. Since I only have a local backup of those stock components, this render me unable to mirror it instantly. And about those other remaining lost time, I think everyone can guess that lel. Anyway enjoy, for those who needs them
I'm using CM13 ROM, does these stocks give better performance?
Can anyone explain the benefits of using them? especially ' stock RIL components ' I don't know what is this.
parkavenu said:
I'm using CM13 ROM, does these stocks give better performance?
Can anyone explain the benefits of using them? especially ' stock RIL components ' I don't know what is this.
Click to expand...
Click to collapse
Hmm i should update the OP soon to explain more about using the zips while being on a custom ROM.
This thread is made to cater all my other personal flashable zips that I share, while also focusing on stock components as a main objective of the thread. These so called "stock components" are only for stock ROM with the exception of the RIL components.
Now to answer to your question
The FOTA is useful if you have a some sort of "ritual" and prefer stock FOTA partition when you want to wipe your TWRP recovery. Adrian provided a FOTA eraser that fundametally write zeros to the FOTA partition. That's the difference between this stock FOTA and Adrian's FOTA cleaner. This does not improve or make your experience on CM worse.
The stock Kernel is strictly for stock ROMs. Flashing on another ROM that doesn't depend on stock ROM will make the ROM unbootable. This makes your experience on CM worse.
The RIL components will flash the network-related things to your system. This might be useful for someone who requires baseband (elabel) without needing to use the FlashTool. This may improve your network experience, as it really did for me.
Disclaimer:
Our tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tool, you must agree that you using our tool on your own risk, I am not responsible if you brick your device or anything else!
What is this for:
This tool converts xperia sin file and directly create flashable.zip for use to flash your android device with recovery.
Changelog:
- version 1. (missing selinux label generator)
- version 2. (implemented selinux label generator tool. Missing static busybox)
- version 3.
- version 4. some small corections, added missing update-binary
- version 5. some improvements, new sin unpack tool
How to use:
Extract sin2zip.rar archive & simple run CONVERT.bat & chose system.sin image , tool will produce flashable.zip
What you need to check or probably modify in generated flashable.zip:
1. busybox I have used is 32bit, it will work on 64bit too (not busybox.exe !!), I not recommend to change busybox, but before you go for busybox replace make sure it is STATIC busybox and have working (chcon and chown) with -h parameter!
2. check updater-script e.g. first 3 lines and last 2 lines!
3. this -> https://forum.xda-developers.com/showpost.php?p=80593639&postcount=7
Source code:
modified ext4_read tool is in attachment. Original ext4_read is here, many thanks to author! I have notified Igor, hope we see selabels listing integration in 7z without need for hackish ext4_read
sony dump tool -> https://github.com/munjeni/anyxperia_dumper
munjeni said:
This tool converts xperia sin file and directly create flashable.zip for using with recovery. 75 percent is done. 25 percent of the things is missing, selinux related things. I need help for implement selinux to the 7z to list selinux labels from ext4! Here is work in proogress
Click to expand...
Click to collapse
Maybe @SuperR. of SuperR's Kitchen fame HERE could give you some pointers on this. :fingers-crossed:
Maybe you could work together to integrate some of your great Sony specific tools into the Kitchen
That kitchen do not have anything related to our tool. I have done some progress in extracting selabels from ext4 by searcing with inode number \0/
Right now tool is able to extract selabels by inode number pointing
So you are on the drawing board again! Cool... :highfive:
About what you wrote in the j4nn's thread (1. to make fota unpack tool), count on me if you need help, ok!
If I'm not mistaken, I sent you a ota update_package file from my x performance some time ago, but if I am, here it goes again.
Cheers.
serajr said:
So you are on the drawing board again! Cool... :highfive:
About what you wrote in the j4nn's thread (1. to make fota unpack tool), count on me if you need help, ok!
If I'm not mistaken, I sent you a ota update_package file from my x performance some time ago, but if I am, here it goes again.
Cheers.
Click to expand...
Click to collapse
Thanks! I will look into ota package till after I finish our tool
Almost done! New version v2 is out! Made small tool to read ext4 image and print selabels to updater-script, it look like this:
if regular file or folder:
Code:
run_program("/tmp/busybox", "chcon", "u:object_r:location_exec:s0", "/system/bin/xtwifi-inet-agent");
if symlink:
Code:
run_program("/tmp/busybox", "chcon", "-h", "u:object_r:vendor_file:s0", "/system/bin/xxd");
Tool is curently 95 percent done, not realy ready for flashig produced flashable.zip , need to implement 5 percent of the things. You can try but plese do not try to flash with recovery it will not work corectly!
Version 3 done! Before you flash flashable.zip please check updater-script first 3 lines and last 2 lines! Do in mind our tool didn't include the rest of firmware like kernel, vendor...etc, tool only convert one sin file to flashable.zip, if you need the rest of firmware run CONVERT.bat and chose another sin file, do merges in zip by hand and do merges-modification in updater-script by hand too. Not recommended for newbies! I can't tell you if produced flashable.zip is working I'm not tried to flash flashable.zip, but I think it going work. Important thing is initial tool is done and somebody need to test. Let me know Enjoy!
Version 4 done. Enjoy!
@serajr here is some info https://forum.xda-developers.com/showpost.php?p=80599561&postcount=1330 , your file is the same format as j4nn
Version 5 done.