Related
This is the ROM i use myself, but I post it here in case other people also want a clean (almost) stock ROM with root and recovery. It works for me, but I provide no guarantee that it will work for you. That said, these ZIP files and procedures have been tested by myself and a few others and seem to work quite well.
FLASH THIS AT YOUR OWN RISK.
Requirements:
Sony Xperia Z.
Only tested on LB, but should also work on UB.
Ability to flash ZIP files via recovery.
Features:
Based on Xperia Z_10.1.1.A.1.307_Unbranded BE.ftf (file uploaded by Psicao).
Removed bloat and other apps you can download from Google Play.
Installed CWM recovery 6.0.2.8 for locked bootloaders v4.
Odexed and zipaligned.
No reboots when mounting system r/w.
Pre-rooted with Koush's Superuser App.
Busybox v1.20.2 installed.
Call recording.
18 Toggles.
36 dpi softkeys.
Changelog:
v8
Added 18 Toggles.
Switched to 36 dpi softkeys.
v7
Added WeatherWidget back due to popular demand.
More robust and less intrusive way to ensure that mounting system r/w doesn't cause a reboot.
v6
Based on 10.1.1.A.1.307
Removed 18 Toggles since it is not compatible with 1.307 yet.
Delete the ric daemon early in the boot process.
v5
Added 18 Toggles.
Applied a few WiFi tweaks to get a (hopefully) more stable WiFi connection.
v4
Removed duplicate notification sound 'vega' (bug in original ROM).
Increased volume a bit.
v3
Created all symlinks found in the original FTF file.
Changed all file and directory permissions to match those in the original FTF file.
Added a more robust script to stop ric.
v2
Fixed reboot issue when mounting system r/w.
Added Notes and NoteWidget back.
Reodexed and zipaligned.
v1
Initial release.
Installation:
Enter recovery.
Flash C6603_10.1.1.A.1.307_DEBLOAT.zip.
Clear user data OPTIONAL STEP - SEE BELOW.
Reboot.
Reboot again once NFC firmware has been upgraded (only needed if upgrading from 1.434 or earlier).
Note regarding unlocked bootloaders: This ROM is designed for LB. If using this on UB flash the following ZIP after installation to remove the CWM recovery for LB: C6603_10.1.1.A.1.307_UBPATCH.zip
Clear data?
If NFC is not working and you're upgrading from a 1.434 ROM, I recommend that you clear your userdata by flashing C6603_10.1.1.A.1.307_ClearData.zip.
You do NOT need to clear user data if you are already running a ROM based on 1.253 or 1.307 and everything is working fine.
MD5 hashes:
2f8fe013da90987447a04c0e5f405998 (C6603_10.1.1.A.1.253_DEBLOAT.zip)
3bba6ffb3cd9bdf7535c5e4b722223d5 (C6603_10.1.1.A.1.253_ClearData.zip)
b889d474290d9b924acbf011277d58e3 (C6603_10.1.1.A.1.307_UBPATCH.zip)
Upgrade kernel and baseband:
Once the ROM is working you might want to flash kernel and baseband from the original FTF via Flashtool in order to get the full 1.307 experience.
Preventing reboots when mounting /system read-write
This ROM uses my own little utility called RICHunter to prevent reboots when mounting /system read-write. If you want to use it yourself in your own ROM you can download it here:
0c766dc58cc909693f5d669264d78f4a (richunter.zip)
Included in the ZIP file is a README.txt that explains how to use it, but you can also read it here:
RICHunter by Carceri @ XDA
1. What is this?
On the Xperia Z Sony have added a small program called ric which
monitors mount options on filesystems and reboots the system if
they deviate from their default values. This causes the system
to reboot e.g. when the /system partition is mounted read-write.
In short, this programs stops this daemon and replaces it with a
dummy version that doesn't do anything, thereby disabling ric.
2. How do I use it?
Just put the file richunter somewhere on your system, for example
/system/bin/richunter, make it executable (chmod 755) and run it
as the root user. This needs to be done every time the system is
restarted.
This can be achieved by putting the following lines in a file
called /system/etc/install-recovery.sh:
#!/system/bin/sh
exec /system/bin/richunter
Another way is to make a wrapper to /system/bin/ctrlaltdel and
call richunter from there:
#!/system/bin/sh
exec /system/bin/richunter
exec /system/bin/toolbox ctrlaltdel "${1}" "${2}" "${3}" "${4}"
Choose either one, or a 3rd solution to automatically run it.
Remember to make the files executable.
3. How does it work?
On the latest kernel, the ric daemon is restarted whenever it
is killed. Therefore the following steps are taken by this
program to stop it without giving it time to reboot the system:
1) The programs runs as a daemon waiting for up to 60 seconds
for ric to start.
2) It detects which CPU ric was last scheduled on, and forces
ric to always run on that CPU in the future.
3) It forces itself to run on the same CPU as ric and sets its
scheduling priority to real-time. This prevents anything
in that CPU from running, including ric.
4) It mounts the rootfs read-write and replaces ric with a
dummy version that just sleeps forever. Finally it kills
the ric process and remounts rootfs read-only.
5) The daemon now exits. When ric is restarted the dummy
version is started instead.
4. What about unlocked bootloaders and custom kernels?
On custom kernels ric has either been removed or not installed
at all. Therefore this is only needed on locked bootloaders.
5. Can I use it in my own ROM?
Sure. Use it as you want.
6. How do I compile it?
You need to have the Android NDK installed. Then set the
correct paths in the included Makefile and run:
1) make prep
2) make
That's it. When you want to recompile you can skip step 1).
7. What license is this released under?
It is UNLICENSED software. See http://unlicense.org/
Hi, i have not tested this exact zip, but the rom i am using now is based on a previous version you posted in another thread.
There is a little issue with your "debloating", you removed "Notes" app, so when you go to "small apps" drawer and choose notes or voice recording, an error pops out, so you have to remove the icons and forget about stock notes or voice recording as they are apps not available on the market to download separately.
As i said, this happens on the first zip you uploaded, i don't know if this was already solved on newer versions.
If NFC is not working, there is still hope to keep user data intact, just delete /data/usf on your phone, take usf folder from your userdata.tar, and put it in your phone in the same place where the older was with same permissions. This step could also be added to the main flash script, no user data is lost and i think all NFC related problems would be gone
Thanks for sharing your work.
RoberM said:
There is a little issue with your "debloating", you removed "Notes" app, so when you go to "small apps" drawer and choose notes or voice recording, an error pops out, so you have to remove the icons and forget about stock notes or voice recording as they are apps not available on the market to download separately.
Click to expand...
Click to collapse
I have added the Notes app back in this zip.
RoberM said:
If NFC is not working, there is still hope to keep user data intact, just delete /data/usf on your phone, take usf folder from your userdata.tar, and put it in your phone in the same place where the older was with same permissions.
Click to expand...
Click to collapse
That was actually the first thing I tried and it didn't work for me. It might work for some and if someone is interested I'll be happy to provide a zip file that just restores this directory and keeps everything else under /data intact.
How do you enable call recording btw? Thanks.
Sent from my C6603
The link is down!! :crying:
mandarjoshiin said:
The link is down!! :crying:
Click to expand...
Click to collapse
Link is back up. I were just in the process if uploading v2
vibranze said:
How do you enable call recording btw? Thanks.
Click to expand...
Click to collapse
Press the menu button during a call.
Carceri said:
This is the ROM i use myself, but I posted this in case other people also want a clean (almost) stock ROM with root and recovery. It works for me, but I provide no guarantee that it will work for you, so FLASH THIS AT YOUR OWN RISK.
Requirements:
- Sony Xperia Z with locked bootloader.
- Ability to flash ZIP files via recovery.
Features:
Based on the first version of the ZIP posted by wawyed on this thread.
...which was based on C6603_Unbranded_10.1.1.A.1.253.ftf (original file uploaded by prakka).
Removed bloat and other apps you can download from Google Play.
Installed CWM recovery 6.0.2.8 for locked bootloaders v4.
Odexed and zipaligned
Pre-rooted with Koush's Superuser App.
Busybox v1.20.2 installed.
Enabled call recording.
Changelog:
v2
Fixed reboot issue when mounting system r/w.
Added Notes and NoteWidget back.
Reodexed and zipaligned.
v1
Initial release.
Installation:
Enter recovery.
Flash C6603_10.1.1.A.1.253_DEBLOAT.zip.
Clear user data OPTIONAL STEP - SEE BELOW.
Reboot.
Say not to "Disable recovery flash" if asked.
Possibly reboot a second time once NFC firmware has been upgraded.
I had problems with NFC not working if I didn't clear user data the first time I upgraded from a version < 1.253. In order to clear user data follow this step:
Flash C6603_10.1.1.A.1.253_ClearData.zip.
These ZIP files and procedures have been tested by myself and a few others and seem to work. However, some people have also experienced issues, but since I don't know their exact setup it is impossible for me to pinpoint the source of these errors. FLASH THIS AT YOUR OWN RISK.
Upgrade kernel and baseband:
Once the ROM is working you might want to flash kernel, fotakernel and baseband from the original FTF via Flashtool in order to get the full 1.253 experience.
Click to expand...
Click to collapse
hello I used your guide and everything works to perfection thanks:laugh:, I invite other people to use this guide to those who want to update your phone with the root installed.:good:
ps. sorry if I use a translator.
ciao ho usato la tua guida e funziona tutto alla perfezzione grazie, invito altri utenti ad usare questa guida per chi vuole aggiornare il telefono con il root installato.
Great, this is the first one deodexed and zipaligned, i am sure a lot of people will be interested.
EDIT: Ok, i didn't read well, it says Re-Odexed
Sorry, i'm a little confused, is this rom odexed or deodexed?
Sent from my C6603 using Tapatalk 2
secondkai said:
Sorry, i'm a little confused, is this rom odexed or deodexed?
Click to expand...
Click to collapse
In changes for version 2 reodexed is written. Attentively read an original post.
Carceri said:
Press the menu button during a call.
Click to expand...
Click to collapse
Thanks, but what I meant was how to incorporate call recording into the ROM, is it something that can be done easily, e.g. editing build.prop, etc or any other method?
Cheers.
Update: I got the answer. Thanks.
picasa album sync is missing in google accounts and album view, is this due to bloat removal ?
jimsey said:
picasa album sync is missing in google accounts and album view, is this due to bloat removal ?
Click to expand...
Click to collapse
I don't think so. Is that feature available on a normal Xperia Z stock ROM?
I think that the original Gallery app installs the required sync adapter. Also if you have Google+ installed it is replaced by Photo Sync.
hello Carceri would like to upgrade to v4 there some procedure to be performed?
fabbiotto said:
hello Carceri would like to upgrade to v4 there some procedure to be performed?
Click to expand...
Click to collapse
If you have installed this ROM before you just need to flash the new ZIP file to get the latest version.
Carceri said:
If you have installed this ROM before you just need to flash the new ZIP file to get the latest version.
Click to expand...
Click to collapse
s now the v2 if I install the v4 just that I do not clear user data to not lose my data?
fabbiotto said:
s now the v2 if I install the v4 just that I do not clear user data to not lose my data?
Click to expand...
Click to collapse
Just flash the new ROM. No need to clear data.
Carceri said:
Just flash the new ROM. No need to clear data.
Click to expand...
Click to collapse
thank you very much:good:
hello v4 does not work well with the DoCoMo Status Bar and the Task Switcher sony disappears, you can take a look please?
by the time I come back to v2
Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the third version of the program.
Source (GITHUB SOURCE https://github.com/aToxyD/android_boot_image_manager_apk).
WHAT'S NEW
- Some optimization.
- Add new Text Editor with high syntax.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* Modding.MyMind, for his heavily modification of boot.img tool.
* Tah Wei Hoon, for TextWarrior.
* Dmytro Tarianyk, for Android Floating Action Button.
* Anthony Restaino, for Grant.
IMPORTANT
- Root is only necessary for Unpacking boot patched by "superSu or Magisk" and Backup/Flash Operations, so if you want to unpack stock boot or you have your favorite flasher apk like "Rachr", if so you dont need to check "Root Access" in settings menu.
- Please uninstall any previous version of ABM before installing the newer.
I do not like people to coming here and take what they wanted and leave like a thief , at least leave a comment. . .
This work is for all, so help your self.
atoxyd said:
Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the second version of the program.
WHAT'S NEW
- Corrected some bugs related to compatibility with Android 6.
- Use xiaolu mkbootimg tools (GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools)
TODO
- add support to x86, mips arch.
- add support to put files to unpacked folder.
- add support to combinedboot , in Xperia device recovery ramdisk is combined with system ramdisk.
IMPORTANT
- The apk need root access to work.
- Note that make change by adding files to unpacked folder with root explorer, the owner will be root and the apk will not work, if you do this you must change the owner to ABM apk.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* modding.MyMind, for his heavily modification of boot.img tool.
* @bigsupersquid for his support and motivate from the beginning.
Click to expand...
Click to collapse
mtk support?
lixia1998 said:
mtk support?
Click to expand...
Click to collapse
Certainly I am working on this , but you should help me.
New version won't install on Kit Kat
PiggyFlooper said:
New version won't install on Kit Kat
Click to expand...
Click to collapse
Okay my friend, try to uninstall the old version, and tell me.
atoxyd said:
Okay my friend, try to uninstall the old version, and tell me.
Click to expand...
Click to collapse
You were right, I'll start project tonight editing ramdisk on my LG Volt
Are extracted files accessible in file system? I can't find them
levone1 said:
Are extracted files accessible in file system? I can't find them
Click to expand...
Click to collapse
Unpacked to /data/local/ABM
PiggyFlooper said:
Unpacked to /data/local/ABM
Click to expand...
Click to collapse
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.
atoxyd said:
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.
Click to expand...
Click to collapse
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?
levone1 said:
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?
Click to expand...
Click to collapse
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
That was my original thought, so I wiped data and tries again, but no different... I'll just uninstall and reinstall, and probably be fine. Thanks
atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
Same thing after reinstall. I tried with twrp file again, and works fine, but with kernel file, error msg...
It seems that the image you want to unpack it is not an android image.
atoxyd said:
It seems that the image you want to unpack it is not an android image.
Click to expand...
Click to collapse
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Try to edit devices.xml in /sdcard/ABM directory and backup kernel using ABM app, after try to unpack boo.img backed up, you find it in /sdcard/ABM/backup directory.
levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, try to delete space in the name of image.
Linux ..........img will be
Linix_..........img
levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img
Well my friend @levone1, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img
Hey friends! I was looking at this thread: http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307 and I decided to create my own thread about the same topic, however this thread is much more simplified and is for those people who are new to rooting Xperia smartphones.
So without further ado here are the steps
Part One: downloading prerequisites
in order to flash .ftf firmware files to downgrade your phone to lollipop for TA backup you will need.
1. Java JDK :
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
2. XperiFirm(not neccesary if you plan to stay on LP)
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
3. Flashtool
http://www.flashtool.net/downloads.php
4. Android SDK
http://developer.android.com/sdk/index.html#downloads
5. iovyroot(not necessary if you do not want to backup DRM)
http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
other prerequisites:
Patience
Mountain Dew or Starbucks
A small bit of knowledge on command line interfaces
Part Two: Downloading firmware
1. Open up XperiFirm
2. Select your device from the list
3. Select your model number(can be checked in Settings > about phone > Model Number
4. Pick your country and carrier(does'nt really matter, best firmware to use is UK customised and Singapore customised)
5. Click the latest release in 'available releases'
6. A dialogue should pop up, tick 'automatic unpack'
7. Wait for download to complete
Part 2.5: Creating FTF
Open up Flashtool
1. Click on tools > bundles > Create
2. Select the firmware folder
3. Double click on the Device section and select your device
4. Type in the firmware build number(at the end of the folder name) as for branding type in the country and carrier from which you downloaded the firmware from.
5. Go to file explorer and delete 'fwinfo.xml' from the firmware folder
6. IMPORTANT DO NOT TRANSFER THE FILES WITH A .TA FILE EXTENSION IT WILL BRICK YOUR DEVICE with that disclaimer out of the way go back to flashtool, transfer all the files using the arrows (except those with a .ta file extension)
7. Click create, you should be able to sit back and relax while it does its thing
Part Three: Downgrading firmware
Download the firmware here: http://www.xperiablog.net/forum/resources/xperia-z5_e6653_32-0-a-6-152_central-europe-5_generic.477/
1. Place the file in c: Users/*account name*/.flashtool/firmwares
Open up Flashtool
2. Press the lightning bolt icon
3. Choose Flashmode and click ok
4. choose the firmware you downloaded(Do not choose the one you created)
5. Tick "user data" in the box at the top right hand corner
6. Press flash and wait
Part Four: DRM backup and unlock
1.Extract iovyroot
2. make sure USB debugging and unknown sources are enabled
3. Open up backupdrm.bat and wait
4. make sure there are no errors before proceeding(this usually takes a couple of tries)
5. IMPORTANT keep a safe online backup of your DRM keys.
6. Open up flashtool
7. click on BLU
8. Go to http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
9. Select your device and follow the instructions
9. after getting the unlock key, paste it inside the BLU dialogue in flashtool
10. wait, then profit!
11. now flash the .FTF that you created
12. boot your device into fastboot(plug in power cable and press vol down when your phone is switched off)
13. Download androplus kernel v23 and above from here: https://kernel.andro.plus/
14. Extract boot.img and put it in the android SDK inside of 'platform-tools'
15. Press shift+right click inside of the same folder
be sure to install xperia z5 fastboot drivers)
16. click 'open command window here'
17. run fastboot devices and make sure it detects your device
18. run this command here : fastboot flash boot boot.img
19. Reboot and DONE
Just a quick note, from my experience with downgrading in the past, you MUST wipe your user data, the phone won't boot else. This happened on multiple Sony phones with multiple different firmware versions.
gamer649 said:
Just a quick note, from my experience with downgrading in the past, you MUST wipe your user data, the phone won't boot else. This happened on multiple Sony phones with multiple different firmware versions.
Click to expand...
Click to collapse
I just corrected it, thanks for the quick note. Btw my z5 booted with minor issues when downgrading without wiping userdata
_LLJY said:
I just corrected it, thanks for the quick note. Btw my z5 booted with minor issues when downgrading without wiping userdata
Click to expand...
Click to collapse
Every other Sony phone I've owned (M, Z1 compact, Z2) refused to boot after a downgrade. The main thing to remember when downgrading is to take a backup before doing so to prevent data loss, I've experienced it myself firsthand so I know how stressful it can be.
In the TA backup part you should add a step to make sure the script actually worked and didn't stop with an error, before proceeding on to unlocking BL. I had to reboot my phone & run the script several times before successfully pulling it off.
Hello!
I'm new to the Sony family as you can see in my signature and I wouldn't call myself n00b, but the whole procedure with the extra partitions is so confusing! Thank you for trying to break it down!
the usual 3 step way (1 unlock bootloader, 2 flash recovery, 3 flash SuperSU) is still present but there are some other steps before them.
As i can understand, all the hassle is just for the backup of the TA partition.
I think that we must start with your step 3, just to avoid confusion such as the step 3.4. Please post a direct link to the firmware you suggest, I can't download it because it requires me to register there too.
Also, you should break the part 4 at the step 11. If I'm not mistaken, the order should be 1, 3, 4 (1-10), 2 , 2.5, 4 (11-19).
In the guide, restoring DRM keys also should be added. ?
Nice guide mate.
Sent from my E6683 using Tapatalk
DeathStroke said:
In the guide, restoring DRM keys also should be added. ?
Nice guide mate.
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
Latest andro kernel have drm keys intergrated bro
working for e6633 dual ?
I had a doubt! On Part Three, can I use the given E6653 ftf for my E6683? Or I should download the .152 ftf for my exact device model i.e. E6683?
Help me bro @_LLJY
good guide
easy follow
had overheat problem i need help...!
any one please ?
updated from support ( device no pc)
after update full overheat on camera use
Can you guys please help me?
My friend got a 5803, I backed up his DRM keys and unlocked the bootloader but can't root it.
If someone could be so kind to help us it'll be great, I did it to my 6653 but for some reason I can't root this one.
Sent from my E6653 using XDA-Developers mobile app
i am trying to downgrade my z5 from 6.0.1 to a 5.1.1 ftf...but when i begin to flash it stops ERROR - processing of loader.sin finished with errors....please someone can help me?
feesta said:
i am trying to downgrade my z5 from 6.0.1 to a 5.1.1 ftf...but when i begin to flash it stops ERROR - processing of loader.sin finished with errors....please someone can help me?
Click to expand...
Click to collapse
Unpack firmware Ftf file with flashtool and see is there file called FWINFO.Delete this file and pack Ftf using Ftool and you will not have peoblems with flash.
Sent from my Sony Xperia Z5
Here is a stupid question, what now that i have don all steps? i still dont have cmw or root?
feesta said:
i am trying to downgrade my z5 from 6.0.1 to a 5.1.1 ftf...but when i begin to flash it stops ERROR - processing of loader.sin finished with errors....please someone can help me?
Click to expand...
Click to collapse
I did two things to try to fix this:
1: Use the previous version of flashtool (0.9.18.6) instead of the current one
2: Use the Software Repair function of Sony's Xperia Companion application
I don't know which of these helped (it might have been neither, actually) but in the end I was able to flash Lollipop 5.1.1 onto my Z5 and use iovyroot to back up the TA partition.
Hi, this is kind of off-topic but this is the best thread for this question I could find.
I was in a hurry to get rid of the bloated, horrible stock rom, and I did not back up my DRM keys. I did patch my current kernel with the DRM fix from another thread here at XDA. Now my question is:
What kind of functionality did I lose from this, except not being able to restore to stock and relocking bootloader?
klemen241 said:
Here is a stupid question, what now that i have don all steps? i still dont have cmw or root?
Click to expand...
Click to collapse
Hello, look at this video:
h**ps:.youtube.com/watch?v=dTlosea6SJE
But at first, i installed at my Z5 the latest Kernal v36 and then i installed the TWRP 2.8.7.0, but i think you can install the newest TWRP too.
At last you install the SuperSu with TWRP, than you have full root!
Creating FTF not possible
hej,
i have a problem creating the FTF as described in Part 2.5:
-i downloaded the latest version via xperifirm (E6653_Customized DE_1298-3675_32.2.A.0.253_R3C)
-i deleted the fwinfo.xml & all .TA files from the folder
-flashtool is hanging here now:
-05/016/2016 09:16:25 - INFO - Streaming from file : C:\Users\hek\Desktop\Sony Xperia Z5\E6653_Customized DE_1298-3675_32.2.A.0.253_R3C\boot\boot_delivery.xml
05/016/2016 09:16:25 - INFO - Adding rpm_S1_Boot_MSM8994_LA1_2_2_40_AID_1_KITAKAMI-TEST-HWID009400E1-SWID0A-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
05/016/2016 09:16:25 - INFO - Adding Sumire_S1BootConfig_MiscTA.ta to the bundle
-tried it with singapore customized and german customized (¬ deleting the .TA-files & manually unselecting all TA files in flashtool)
what could be the issue here or is there another way to get the latest version on the phone after unlocking it?
or is it safe just to install the latest version as described here without deleting the .TA-files? (http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224)
thanks for any input!
--
Part 2.5: Creating FTF
Open up Flashtool
1. Click on tools > bundles > Create
2. Select the firmware folder
3. Double click on the Device section and select your device
4. Type in the firmware build number(at the end of the folder name) as for branding type in the country and carrier from which you downloaded the firmware from.
5. Go to file explorer and delete 'fwinfo.xml' from the firmware folder
6. IMPORTANT DO NOT TRANSFER THE FILES WITH A .TA FILE EXTENSION IT WILL BRICK YOUR DEVICE with that disclaimer out of the way go back to flashtool, transfer all the files using the arrows (except those with a .ta file extension)
7. Click create, you should be able to sit back and relax while it does its thing
I used iovyroot and it created taxxxxxx.img that it has 2mb. I think so I read so time ago that taxxxxx.img had 500kb... Is it my ta wrong?? Or it's normal??
Thanks!
Enviado desde mi Z1 mediante Tapatalk
hello friends, i'm having trouble for my root and twrp because i have so-02j version.
I've followed the guides trying the genesis kernel, but it just makes a stop in the sony logo when booting.
does my device have a chance to root twrp and anymore?
my step was successful until unlock bootloader
tumincm said:
hello friends, i'm having trouble for my root and twrp because i have so-02j version.
I've followed the guides trying the genesis kernel, but it just makes a stop in the sony logo when booting.
does my device have a chance to root twrp and anymore?
my step was successful until unlock bootloader
Click to expand...
Click to collapse
What's fw version?
levone1 said:
What's fw version?
Click to expand...
Click to collapse
Nougat SO-02J 34.2.B.0.290 , only one available for japan version on xperiafirm , I've tried some other firmware versions, but it does not work
tumincm said:
Nougat SO-02J 34.2.B.0.290 , only one available for japan version on xperiafirm , I've tried some other firmware versions, but it does not work
Click to expand...
Click to collapse
Seems like custom kernel for f5321 probably wouldn't work for that. Maybe try rootkernel?
levone1 said:
Seems like custom kernel for f5321 probably wouldn't work for that. Maybe try rootkernel?
Click to expand...
Click to collapse
can it show me what kind rootkernel ? I did not find the genesis kernel other than the Standart and noDRM fix, and both of them I tried, kept showing until the sony logo,
tumincm said:
can it show me what kind rootkernel ? I did not find the genesis kernel other than the Standart and noDRM fix, and both of them I tried, kept showing until the sony logo,
Click to expand...
Click to collapse
Rootkernel is a tool. You can use it to disable built-in Sony security features in stock kernel, so you can modify system, etc. You will need the stock kernel.elf file from your ftf. Default format is .sin, I think, so you need to use Flashtool to dump kernel.sin from ftf, then use sin editor to get kernel.elf. Then you can use rootkernel tool to patch kernel.elf and output boot.img, that you can flash in recovery.
levone1 said:
Rootkernel is a tool. You can use it to disable built-in Sony security features in stock kernel, so you can modify system, etc. You will need the stock kernel.elf file from your ftf. Default format is .sin, I think, so you need to use Flashtool to dump kernel.sin from ftf, then use sin editor to get kernel.elf. Then you can use rootkernel tool to patch kernel.elf and output boot.img, that you can flash in recovery.
Click to expand...
Click to collapse
ok thanks for your response, i will try to learn, i am very noob with this, is there any guidance in forum x compact.
tumincm said:
ok thanks for your response, i will try to learn, i am very noob with this, is there any guidance in forum x compact.
Click to expand...
Click to collapse
Use 7zip, and go to ftf file and select 'open archive'. Find the file inside called 'kernel.sin', and extract /copy it somewhere. Then open Flashtool. in top dropdown menus, click 'sin editor', and navigate to the kernel.sin file, select it and choose 'extract data'. It will dump a file called 'kernel.elf'. Then download rootkernel tool, and extract to a folder, and put your kernel.elf fokder into the rootkernel folder. Then open a command prompt in the rootkernel directory, and type 'rootkernel kernel.elf boot.img'. If it works, it will create a boot.img that can be rooted.
issues/questions:
- I have only done this on Oreo. Serajr made an unofficial rootkernel specifically for Xperia Oreo. I have no way to know if it will work for a Nougat Docomo device. I know rootkernel has had several versions/releases, and does work on Nougat, but I don't know for sure which one, if any will work for you. Search these links:
https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
https://forum.xda-developers.com/showpost.php?p=75505302&postcount=2973
- flashing the modded boot img does not make you rooted, it just makes you rootable. You still have to flash whatever su you want, etc., and consider your ta backup, (which maybe is not an issue anymore, since you already unlocked bl...)
levone1 said:
Use 7zip, and go to ftf file and select 'open archive'. Find the file inside called 'kernel.sin', and extract /copy it somewhere. Then open Flashtool. in top dropdown menus, click 'sin editor', and navigate to the kernel.sin file, select it and choose 'extract data'. It will dump a file called 'kernel.elf'. Then download rootkernel tool, and extract to a folder, and put your kernel.elf fokder into the rootkernel folder. Then open a command prompt in the rootkernel directory, and type 'rootkernel kernel.elf boot.img'. If it works, it will create a boot.img that can be rooted.
issues/questions:
- I have only done this on Oreo. Serajr made an unofficial rootkernel specifically for Xperia Oreo. I have no way to know if it will work for a Nougat Docomo device. I know rootkernel has had several versions/releases, and does work on Nougat, but I don't know for sure which one, if any will work for you. Search these links:
https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
https://forum.xda-developers.com/showpost.php?p=75505302&postcount=2973
- flashing the modded boot img does not make you rooted, it just makes you rootable. You still have to flash whatever su you want, etc., and consider your ta backup, (which maybe is not an issue anymore, since you already unlocked bl...)
Click to expand...
Click to collapse
https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
only rootkernel that talks about nougat, but i am failing on tools rootkernel v5.23 v5.11 v4.31 can not open exe or cmd inside folder,
I have sequence with:
1. Retrieve the kernel.sin file from ftf nougat fw so-02j using 7zip, and extrack sin to elf using flashtool.
2. i extrack the rootkernel tool folder and input the kernel.elf into the rootkernel folder. (here I am having problems, opening cmd or exe does not affect anything2)
for other versions i see for oreo, with certain version is there any possibility for nogat?
tumincm said:
https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
only rootkernel that talks about nougat, but i am failing on tools rootkernel v5.23 v5.11 v4.31 can not open exe or cmd inside folder,
I have sequence with:
1. Retrieve the kernel.sin file from ftf nougat fw so-02j using 7zip, and extrack sin to elf using flashtool.
2. i extrack the rootkernel tool folder and input the kernel.elf into the rootkernel folder. (here I am having problems, opening cmd or exe does not affect anything2)
for other versions i see for oreo, with certain version is there any possibility for nogat?
Click to expand...
Click to collapse
Not sure what you mean... If you have rootkernel folder, open command prompt, and 'cd /(whatever)/(whatever)/rootkernel', (meaning navigate to wherever the rootkernel folder is), then type 'rootkernel'. What is output?
levone1 said:
Not sure what you mean... If you have rootkernel folder, open command prompt, and 'cd /(whatever)/(whatever)/rootkernel', (meaning navigate to wherever the rootkernel folder is), then type 'rootkernel'. What is output?
Click to expand...
Click to collapse
oh I know,my error is not doing it on comandprompt
- Unpacking kernel
Found elf boot image
Kernel version: 3.10.84-perf-g9430b0a
Found appended DTB
- Detected vendor: somc (Sony), device: kugo, variant: dcm
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 7.0
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] N
- Sony RIC is enabled. Disable? [Y/n] N
- There is no TWRP template for kugo. Install anyway? [y/N] N
- DRM fix is unsuppported/untested for model kugo. Install anyway? [y/N] N
Skipping drmfix
- Install busybox? [Y/n] N
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
now is it correct? all options No?
tumincm said:
oh I know,my error is not doing it on comandprompt
- Unpacking kernel
Found elf boot image
Kernel version: 3.10.84-perf-g9430b0a
Found appended DTB
- Detected vendor: somc (Sony), device: kugo, variant: dcm
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 7.0
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] N
- Sony RIC is enabled. Disable? [Y/n] N
- There is no TWRP template for kugo. Install anyway? [y/N] N
- DRM fix is unsuppported/untested for model kugo. Install anyway? [y/N] N
Skipping drmfix
- Install busybox? [Y/n] N
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
now is it correct? all options No?
Click to expand...
Click to collapse
- Dm-verity is a security feature which will prevent system mods. You should select 'yes' to disable it
- Sony RIC: ditto
- Not sure about TWRP msg. just leave it 'no'. You can flash TWRP later.
- If you don't have ta backup, you might want drm fix. It theoretically improves camera performance if you're missing ta. Since it says unsupported, maybe if you get bootloop with new kernel, try again with 'no'.
- Why not install busybox? Many or most root apps need it.
levone1 said:
- Dm-verity is a security feature which will prevent system mods. You should select 'yes' to disable it
- Sony RIC: ditto
- Not sure about TWRP msg. just leave it 'no'. You can flash TWRP later.
- If you don't have ta backup, you might want drm fix. It theoretically improves camera performance if you're missing ta. Since it says unsupported, maybe if you get bootloop with new kernel, try again with 'no'.
- Why not install busybox? Many or most root apps need it.
Click to expand...
Click to collapse
it's work , no stuck logo sony again ,
my opsi
- Unpacking kernel
Found elf boot image
Kernel version: 3.10.84-perf-g9430b0a
Found appended DTB
- Detected vendor: somc (Sony), device: kugo, variant: dcm
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 7.0
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] Y
- Sony RIC is enabled. Disable? [Y/n] Y
- There is no TWRP template for kugo. Install anyway? [y/N] N
- DRM fix is unsuppported/untested for model kugo. Install anyway? [y/N] N
Skipping drmfix
- Install busybox? [Y/n] Y
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
for next
whether it can be in the root? or install twrp? i have TWRP-3.0.2-3-F5321.img
tumincm said:
it's work , no stuck logo sony again ,
my opsi
- Unpacking kernel
Found elf boot image
Kernel version: 3.10.84-perf-g9430b0a
Found appended DTB
- Detected vendor: somc (Sony), device: kugo, variant: dcm
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 7.0
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] Y
- Sony RIC is enabled. Disable? [Y/n] Y
- There is no TWRP template for kugo. Install anyway? [y/N] N
- DRM fix is unsuppported/untested for model kugo. Install anyway? [y/N] N
Skipping drmfix
- Install busybox? [Y/n] N
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
for next
whether it can be in the root? or install twrp? i have TWRP-3.0.2-3-F5321.img
Click to expand...
Click to collapse
Next would be to flash the new boot img, (if you didn't yet). It might be a good idea to clean flash firmware first, but might not be necessary. If you do a clean fw flash first, don't turn on the phone when done flashing. Just unplug, then reconnect in fastboot, and flash boot.img. After you flash the new boot img, if everything boots ok, then flash TWRP, then flash root, (Magisk, e.g.).
Kugo has official TWRP now, but don't know if it will work with Docomo. Seems like it should... Latest version is 3.2.2. There's also unofficial 3.2 versions in the development forum here. If you have any TWRP that has worked on your phone before, maybe just stick with that one for testing.
levone1 said:
Next would be to flash the new boot img, (if you didn't yet). It might be a good idea to clean flash firmware first, but might not be necessary. If you do a clean fw flash first, don't turn on the phone when done flashing. Just unplug, then reconnect in fastboot, and flash boot.img. After you flash the new boot img, if everything boots ok, then flash TWRP, then flash root, (Magisk, e.g.).
Kugo has official TWRP now, but don't know if it will work with Docomo. Seems like it should... Latest version is 3.2.2. There's also unofficial 3.2 versions in the development forum here. If you have any TWRP that has worked on your phone before, maybe just stick with that one for testing.
Click to expand...
Click to collapse
yey it's work , now my x compact use TWRP 3.2.2 and superSU normaly
it's just that my DRM is not fixed yet, but I have TA backup via TA_2 bakcup at my position before UBL
can i use it?
tumincm said:
yey it's work , now my x compact use TWRP 3.2.2 and superSU normaly
it's just that my DRM is not fixed yet, but I have TA backup via TA_2 bakcup at my position before UBL
can i use it?
Click to expand...
Click to collapse
You can try ta-poc by munjeni. That's the only ta restore I've ever used. Or, if you made a TWRP backup of your rom before unlocking bl, TWRP might do it. I've heard about other methods, but never tried.
how did you unlock the bootloader? i thought it was impossible on newer jp devices
levone1 said:
You can try ta-poc by munjeni. That's the only ta restore I've ever used. Or, if you made a TWRP backup of your rom before unlocking bl, TWRP might do it. I've heard about other methods, but never tried.
Click to expand...
Click to collapse
ok problem fix all everything is in accordance with my wishes, I am very grateful to you :good: :angel:
dnar said:
how did you unlock the bootloader? i thought it was impossible on newer jp devices
Click to expand...
Click to collapse
not 100% jp version lock bootloader ,i ordered from seller for ubl yes and i get spesial price hehe
this is just a matter of luck
Backup TA Partition
tumincm said:
yey it's work , now my x compact use TWRP 3.2.2 and superSU normaly
it's just that my DRM is not fixed yet, but I have TA backup via TA_2 bakcup at my position before UBL
can i use it?
Click to expand...
Click to collapse
Hello @tumincm I want to ask you which SO-02J firmware you used before for backup your TA Partition? I'm using 34.1.B.0.336 version but not success. I want to backup my TA partition because I have SO-02J with Bootloader Unlock Allowed: Yes. Please reply my question. Thank you so much.
I DID NOT CREATE THIS ROM OR THE RECOVERIES OR FLASH TOOLS LINKED, I ONLY MODIFIED THE SYSTEM UI AND SETTINGS AND BUILD PROP ZIPS BELOW.
I am not responsible for any damage (if any) to your device, data, life, job or anything else you'd care to think of.
ANY QUESTIONS, PLEASE ASK IN THE THREAD AS EVERYONE BENEFITS, PM'S WILL MOSTLY BE IGNORED.
IF YOU DON'T HAVE AN UNLOCKED BOOTLOADER YOU MUST FIRST UNLOCK IT.
Download all files you want/need to your PC/External SD before starting...just saying.
[/CENTER]
Step One
Flash stock firmware for your device that the rom is based off. Readily available from Xperifirm (attached to flashtool - Bonus!), or XDA. Flash via Flashtool or Newflasher. Again, there's plenty of guides on using flashtool and newflasher, i'm not covering that here.
Step Two
Once flashing has completed, turn the device on and allow it to fully boot. Complete the setup process, and log in to your google account. Move the ROM file you already (hopefully) downloaded to internal storage (IMPORTANT STEP: I had symlink errors flashing the ROM from the External SD Card). I normally disable auto-updates in the Play Store/Whats New apps and then let it rest for 5 minutes.
Step Three
Turn your device off, boot into FASTBOOT MODE, and flash TWRP (fastboot flash recovery TWRP/ATWRP.img). If you don't know how to fastboot, see above re: XDA/Google. Unplug your device, wait 10 seconds, then boot into recovery (Hold power and volume down together, release both at at the vibration). Tick the checkbox then swipe right, and the first thing you SHOULD do is go to settings and turn the damn vibration off. :laugh:
Step Four
DON'T WIPE ANYTHING!!! You are installing on top of an already clean installation, its pointless. Press Install, select the XPERIA_PIE_XZP_1.0.zip file you downloaded earlier, and swipe right to install that sucker. Don't freak out when it takes 5 to 8 minutes for the recovery screen to change, its doing its thing, trust me. Once you get the all clear and the button down the bottom says reboot, that's pretty much all that's left to do.
Step Five
Once the phone reboots, let it settle again for a while, and deny all the requests the Chinese apps throw at you. After a few minutes, go into the root explorer app, allow root permissions when it requests it, then go to system/priv-app and delete any app starting with TG. Unless you really like Chinese bloat, in that case, proceed to set up your phone as usual.
The ROM is pretty basic at the moment but given time and based off the Oreo series, more System UI mods will become available with later versions.
CREDITS: @machao44 @uditrawat @Myself5 @Androxyde @munjeni @Ticklefish @Pandemic
@fOmey[/SIZE]
DOWNLOAD LINKS
M-ROM P v1: BASED ON 306 FIRMWARE https://drive.google.com/file/d/1eOWzREBPehv8QoCFYQfPdF4yqKH2NdB1/view
M-ROM P v1.1: BASED ON .33 FIRMWARE
https://mega.nz/#F!MNYGhKhR!OtCS6j-YBXaxcDI1sa7FlQ
Thanks to @sam.foro for uploading.
M-ROM P v1.2: BASED ON .41 FIRMWARE
https://drive.google.com/open?id=1ZX...ixVN09Ry_vVhDf
Thanks to @Yanun
https://drive.google.com/file/d/14K-...ew?usp=sharing
Thanks to @karrouma
M-ROM P v1.3: BASED ON .41 FIRMWARE
https://drive.google.com/open?id=10l...uGinaYCEzy-vt_
Thanks to @Yanun
TWRP: https://dl.twrp.me/maple/
Aroma TWRP: https://mega.nz/#!TdxmiaLb!FYBet5eRYHGqiLT0niRH9F90Ts_QeRdfkOfPWOAgQCM
Flashtool: www.flashtool.net/
Newflasher: https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
M-Rom P v1.6 - BASED ON 10.28 FIRMWARE - Thanks to @karrouma for uploading and sharing
https://drive.google.com/file/d/1pNsIaGR2_r74INyH8p053bQStiruPEWd/view?usp=sharing
M-Rom v1.6 - English Translated
https://mega.nz/#!6ExSGYQZ!HD0YM_Sypeu5h-6K4vhKT9NkiQn_63PZG0ZPwf_kRmY
M-ROM 1.6 aroma add-on.
M-ROM v1.6 aroma add-on - contains .25 animation mod, font picker and fonts, xperia 10 boot animation, double tap to wake kernel selection (g8141/g8142), and magisk 18.1/19.0 selection.
Enjoy.
https://mega.nz/#!nZpihCqK!TvB0_-w0cdTWFBKylPUk5Da3YdLAJCc_vk5d8XNDySc
Beetle84 said:
ADD-ONS
And now we have a few add-ons. You don't really need any of these, but its XDA and if you've come this far you obviously like flashing stuff so here we go...
The Modified Animation Values zip has one extra setting added in developer options, to the animation duration settings. .25 duration has been added (extra fast). Theres no real point to this other than making things seem quicker, but this zip has the added bonus of having the XZ3 Settings.apk included. (Stock XZ3 settings.zip also supplied) FLASH IN RECOVERY
Modified Settings: https://mega.nz/#!qF4gBazC!R4hoXd_1fEOCxwrrttpXRR0CBCO9A3L8QZq3y3A-NEY
Stock Settings: https://mega.nz/#!HQwSSCAC!T3rPbcPLCCVVcMVCZGk3cDKp6DreHtjVYxEcRer3ORQ
The Rounded Recents zip has a modified SystemUI.apk that has (surprisingly) rounded recents modified into the apk. I have also pushed all the right side status bar icons across a little and shortened the space between the data icon and the battery (stock SystemUI.apk zip supplied). FLASH IN RECOVERY
Modified System UI: https://mega.nz/#!iQ4URIzJ!ssb0Wn7rXfqdU9ll3PWGp6Ba7Qx7rfnzH_QxHocEOV4
Stock System UI: https://mega.nz/#!qEpQwIYT!6QDuEWPHiWT111ah2X39z2UzcXvpmEqO2KlAnNpnA_E
The G8141 build prop zip has a build prop modified to say G8141 for those picky (like me) and don't like seeing G8142 in about phone. If you have a G8142, ignore this whole bit about build.prop. Unzip the file and move the file with a root explorer to /system and apply R-W-R-R permissions and reboot.
G8141 Build.prop: https://mega.nz/#!WBwklSCZ!3AfXbN6JmsE0eihgx8Rn7O7deEnbz2KW048WLUm4Grc
MAKE A BACKUP FIRST MAKE A BACKUP FIRST MAKE A BACKUP FIRST
Last but not least, is the Deodex patch (COMING SOON - UPLOADING) for this ROM. Expect lengthy boot time first go, and then longer than usual every time after that. If you flash this zip, your keyboard will be removed, unless you have a keyboard already installed from the Play Store. YOU WILL HAVE NO KEYBOARD AFTER FLASHING THIS ZIP UNLESS YOU ALREADY HAVE ONE INSTALLED FROM THE PLAY STORE! YOU HAVE BEEN WARNED! TWICE!!!
Deodex Patch:
Enjoy
Click to expand...
Click to collapse
Thank you my friend
Great job
Nice
Thanks for this
Nice bro
Keep it up ^^
Added Patched Services.jar Magisk Module to Post 3.
I wonder if the uploaded file is not damaged.
I downloaded twice, filesize reached 1.52 GB at 100%. But the zip file fails to open. Can not be extracted as well
Therefore I did not try it in TWRP.
hasaan6545 said:
I wonder if the uploaded file is not damaged.
I downloaded twice, filesize reached 1.52 GB at 100%. But the zip file fails to open. Can not be extracted as well
Therefore I did not try it in TWRP.
Click to expand...
Click to collapse
Its not a new upload so I wonder what is happening. It is the same link available from the Oreo M-ROM thread, just copied and pasted.
Are you downloading from your device or from a PC?
Removed
link opened fine. and the file is fine opened normally . no problem
Beetle84 said:
ADD-ONS
And now we have a few add-ons. You don't really need any of these, but its XDA and if you've come this far you obviously like flashing stuff so here we go...
The Modified Animation Values zip has one extra setting added in developer options, to the animation duration settings. .25 duration has been added (extra fast). Theres no real point to this other than making things seem quicker, but this zip has the added bonus of having the XZ3 Settings.apk included. (Stock XZ3 settings.zip also supplied) FLASH IN RECOVERY
Modified Settings: https://mega.nz/#!qF4gBazC!R4hoXd_1fEOCxwrrttpXRR0CBCO9A3L8QZq3y3A-NEY
Stock Settings: https://mega.nz/#!HQwSSCAC!T3rPbcPLCCVVcMVCZGk3cDKp6DreHtjVYxEcRer3ORQ
The Rounded Recents zip has a modified SystemUI.apk that has (surprisingly) rounded recents modified into the apk. I have also pushed all the right side status bar icons across a little and shortened the space between the data icon and the battery (stock SystemUI.apk zip supplied). FLASH IN RECOVERY
Modified System UI: https://mega.nz/#!iQ4URIzJ!ssb0Wn7rXfqdU9ll3PWGp6Ba7Qx7rfnzH_QxHocEOV4
Stock System UI: https://mega.nz/#!qEpQwIYT!6QDuEWPHiWT111ah2X39z2UzcXvpmEqO2KlAnNpnA_E
The G8141 build prop zip has a build prop modified to say G8141 for those picky (like me) and don't like seeing G8142 in about phone. If you have a G8142, ignore this whole bit about build.prop. Unzip the file and move the file with a root explorer to /system and apply R-W-R-R permissions and reboot.
G8141 Build.prop: https://mega.nz/#!WBwklSCZ!3AfXbN6JmsE0eihgx8Rn7O7deEnbz2KW048WLUm4Grc
MAKE A BACKUP FIRST MAKE A BACKUP FIRST MAKE A BACKUP FIRST
Last but not least, is the Deodex patch for this ROM. Expect lengthy boot time first go, and then longer than usual every time after that. If you flash this zip, your keyboard will be removed, unless you have a keyboard already installed from the Play Store. YOU WILL HAVE NO KEYBOARD AFTER FLASHING THIS ZIP UNLESS YOU ALREADY HAVE ONE INSTALLED FROM THE PLAY STORE! YOU HAVE BEEN WARNED! TWICE!!!
Deodex Patch: https://mega.nz/#!mdhmnKwS!POI9MLzZRH9g4isgy0XCZLIhYmu6pUAnZwlXcgaM2xM
And a Patched Services.jar Magisk Module. Flash in Magisk and reboot.
306 Patched Services.jar.zip: https://mega.nz/#!LYpyHQyD!Ka21OVx-yWIM1WUb-WQLoLoJEGOZItz7V_BQMz6fbsk
Enjoy
Click to expand...
Click to collapse
can you explain the step how to deodex the pie ??
rizky_zulfikar said:
can you explain the step how to deodex the pie ?
Click to expand...
Click to collapse
All is explained here brother
https://forum.xda-developers.com/android/general/toad-source-android-deodexer-t3848307?nocache=1
Beetle84 said:
All is explained here brother
https://forum.xda-developers.com/android/general/toad-source-android-deodexer-t3848307?nocache=1
Click to expand...
Click to collapse
i've tried that tool, but my priv-app and framework fail to deodex there still odex and vdex file, only my app ?
Hey just downloading, what rom is this or based on what rom, deodexed xperia rom or custom rom, which kind, sory missed this, thank you
stipi69 said:
Hey just downloading, what rom is this or based on what rom, deodexed xperia rom or custom rom, which kind, sory missed this, thank you
Click to expand...
Click to collapse
Its a slightly modified stock rom, based on .306 dual sim Pie firmware. The rom is odexed.
I have it flashed root working, looks nice, refreshing and snappy, i guess xzp does not have hardware side sensors but you can still tap on edge of screen and bring side menu out , nice!!!
I love new camera look, huge icons in pull down menu.... not so much, haha , it is a matter of gettin use to it i guess
Great work, thanks
If you cannot flash 47.2.A.0.306 via flashtool and get same error as i did below download and copy next file:
downloaded "47.2.fsc" file to: username/.flashtool/device/G81XX, delete 47.1.fsc
https://drive.google.com/file/d/1hZR...w?usp=drivesdk (not my work in this link, credits to xda user xrenoix)
Hi, i get error in flashtool, somoene else same error?
28/048/2018 13:48:07 - INFO - Start Flashing
28/048/2018 13:48:07 - INFO - Parsing boot delivery
28/048/2018 13:48:07 - INFO - Found a boot delivery
28/048/2018 13:48:07 - ERROR - No flash script found. Flash script is mandatory
28/048/2018 13:48:08 - INFO - Sending Sync
28/048/2018 13:48:09 - INFO - Sync status : OKAY
28/048/2018 13:48:09 - INFO - Sending powerdown
28/048/2018 13:48:09 - INFO - powerdown status : OKAY
28/048/2018 13:48:11 - INFO - Device disconnected
old .270 rom flashes with no problem
XZ3/XZ2 systemui.apk Sony Loops Clock/ Ambient/ Night Mode port to XZ3 All functions
You need several attempts. I know the description is not simple. Try! All functions currently work Only not double tap to wake
Thanx for http://bbs.gfan.com/android-9527088-1-1.html
https://forum.xda-developers.com/xp...enz-pie-v1-0-0-26-11-18-t3871854/post78281536
OneHand/Night Mode and XZ2 premium systemUI in zip XZ3 systemUIS has rounded corners It looks weird Better XZ2
Indashio said:
XZ3/XZ2 systemui.apk Sony Loops Clock/ Ambient/ Night Mode port to XZ3 All functions
You need several attempts. I know the description is not simple. Try! All functions currently work Only not double tap to wake
Thanx for http://bbs.gfan.com/android-9527088-1-1.html
https://forum.xda-developers.com/xp...enz-pie-v1-0-0-26-11-18-t3871854/post78281536
OneHand/Night Mode and XZ2 premium systemUI in zip XZ3 systemUIS has rounded corners It looks weird Better XZ2
Click to expand...
Click to collapse
Does it work for XZ1?
Thanks
unless we get gravitybox (from xposed) features, like in Resurrection Remix, i'm not moving to Pie.