Related
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.
TWRP v2.8.6.0 (fota) with F2FS for: Z1, Z1c, Z2, Z3, Z3c, TabZ3c(LTE&WIFI)
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!
Seems like fota TWRP for sirius (Z2) will boot on all these phones: Z1, Z1c, Z2 (offcourse), Z3, Z3c and TabletZ3c (both LTE and WIFI version)!
When repacked with res/ and default.prop from NUTs dual recovery, we got TWRP for each specific device.
Download folder:
Edit 25. september 2021: Please consider using newer recoveries than these old ones.
Officially supported Sony devices: https://twrp.me/Devices/Sony/
Includes Z1 (honami), Z2 (sirius), Z3 Compact (z3c), Z3 Tablet Compact Wi-Fi (scorpion_windy)
Unofficial
Z1 Compact (amami), by 115ek: https://forum.xda-developers.com/t/3960699/
Z1 (honami), by daviid99: https://forum.xda-developers.com/t/4316409/
If you are still interested in my old frankenstein builds:
MEGA.co.nz
https://mega.co.nz/#F!fh5hhL5L!xso7GESQ9AR556_nswFfTw
Google Drive
https://drive.google.com/drive/fold...ourcekey=0-0_o2xNplFlKcnt4IaxrUdg&usp=sharing
What is this?
This is a repacked TWRP from Z2 sirius, where I have:
- Added f2fs support by adding mkfs.f2fs and fsck.f2fs from blastagators TWRP.
- Shrinked images in twres/images folder. It wouldn't boot on my Z1c otherwise.
- Switched res folder and default.prop from respective ones from [NUT]s XZDualRecovery
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, this is just repacked using Android Image Kitchen.
Bugs in this recovery will most probably be bugs that all TWRP builds share.
f2fs does not work!!
Yes it does. The recovery will format any partition to f2fs for you. But you need a compitable kernel to use it. Don't ask me for compitable kernels, google it.
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
Recepy
Just repacking the Z2 recovery with f2fs-files will make a un-bootable IMG. 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), Android Image Kitchen, [NUT]s XZDualRecovery flashable for your device, and blastagators TWRP for LG G2
- Unpack blastergator TWRP with Android Image Kitchen. (drag'n'drop .IMG on to the "unpack.bat")
- In ramdisk/sbin "steal" these two files: mkfs.f2fs and fsck.f2fs. Store them some place safe.
- Cleanup Android Image Kitchen folder. (cleanup.bat)
- Open XZDualRecovery with 7zip. Go to system/bin. Open the twrp file. "Steal" the res/ folder and the default.prop file. Store it somewhere safe.
- Unpack TWRP for Z2 with Android Image Kitchen
- Change images in ramdisk/twres/images with these (they are compressed. Unless you use them the img won't boot: https://mega.co.nz/#!e9g1TRCI!vmGsPqVdqSnpcW6G8PC_saLLyyfqTL-1FhjQmggVvxA)
- Add mkfs.f2fs and fsck.f2fs to ramdisk/sbin.
- Replace res folder and default.prop with the ones from XZDualRecovery
- Repack with "Android Image Kitchen". (Double click on "repack.bat")
Links:
Z1 (Honami): Official TWRP - http://forum.xda-developers.com/showthread.php?t=3234877 | http://teamw.in/devices/sonyxperiaz1.html
Z1 (Amami) : Compiled TWRP with f2fs by hawkeyexp - http://forum.xda-developers.com/showthread.php?t=3173411
Z2 (Sirius): Official TWRP - http://forum.xda-developers.com/showthread.php?t=2772879 | http://teamw.in/devices/sonyxperiaz2.html
Z3c: Official TWRP - http://teamw.in/devices/sonyxperiaz3compact.html
Z3 Tablet (Scorpion_Windy): Official TWRP: http://teamw.in/devices/sonyxperiaz3tabetcompact.html
Do it Compiling by yourself and all will works like a charm.
You guys so funy use only ONE repacked images for all other devices which have different resolutions and different kernel base
UPDATE: Packed a individual recovery for each device, with /res folder and default.prop taken from [NUT]s XZDualRecovery. Installing amami CM with sirius recovery gets aborted..
Does this work with the Z3 tablet (scorpion-windy)?
Thanks
belrik said:
Does this work with the Z3 tablet (scorpion-windy)?
Thanks
Click to expand...
Click to collapse
It would probably boot, but installs of ROMs and similar would be aborted because device id on flashable zips would not match device id of recovery.
If you modify build.prop to fit your device, I bet it would work
EDIT: Made a img for tablet z3c. I believe both 4g and WIFI-version can use the same recovery (CM uses same device ID in their build.prop)
EDIT: Separate recovery.img is up for scorpion and scorpion_windy.
o-l-a-v said:
It would probably boot, but installs of ROMs and similar would be aborted because device id on flashable zips would not match device id of recovery.
If you modify build.prop to fit your device, I bet it would work
EDIT: Made a img for tablet z3c. I believe both 4g and WIFI-version can use the same recovery (CM uses same device ID in their build.prop)
EDIT: Separate recovery.img is up for scorpion and scorpion_windy.
Click to expand...
Click to collapse
could you build a second one for tabz3c with "scorpion_windy" device ID? the scorpion one does not flash cm12.1 on my SGP611.
2 Bugs I found:
-Inability to shut off the screen. Even happens when device displays the power (full screen picture of battery). This bug doesn't affect [NUT]'s recovery.
-TWRP crashes whenever you try booting to recovery via charging cable without the system attempting to boot to Android (in other words, turning on the phone with the power cable rather than the power button). The only way out is to hard reset.
Using Xperia Z1 (honami)
kentexcitebot said:
2 Bugs I found:
-Inability to shut off the screen. Even happens when device displays the power (full screen picture of battery). This bug doesn't affect [NUT]'s recovery.
-TWRP crashes whenever you try booting to recovery via charging cable without the system attempting to boot to Android (in other words, turning on the phone with the power cable rather than the power button). The only way out is to hard reset.
Using Xperia Z1 (honami)
Click to expand...
Click to collapse
Yep. Asked in the Z2 TWRP thread, Z2 owners don't have these bugs. Might be because we use z2 related stuff (kernel base) for other phones. If I learn to compile in future this should be fixed afaik. But as far as i know, there is nothing I can do (in regards of repack with other stuff) to fix these bugs.
o-l-a-v said:
Yep. Asked in the Z2 TWRP thread, Z2 owners don't have these bugs. Might be because we use z2 related stuff (kernel base) for other phones. If I learn to compile in future this should be fixed afaik. But as far as i know, there is nothing I can do (in regards of repack with other stuff) to fix these bugs.
Click to expand...
Click to collapse
I lack knowledge with TWRP+Recoveries+Pretty much a lot of things, but couldn't you repack NUT's recovery and try porting it to Lollipop? Maybe exclude Philz's version if it conflicts...?
Hi,
is it possible, to make also a Version for the Xperia ZL?
thanks for the scorpion_windy build! :good:
unlock with material theme has some troubles. i need to get the right line on the screen for wipe to work and also then it takes several tries.
TWRP 2.8.6.1 supposedly brings support for encryption (on bacon at least) [1]. Has anyone played with that on a sony device yet? Maybe created a first package to test?
[1] https://github.com/TeamWin/Team-Win-Recovery-Project/issues/333#issuecomment-105152622
can make a version for zr/zl/z? thx!
hi anyone : )
nostupidthing said:
can make a version for zr/zl/z? thx!
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-z/orig-development/recovery-teamwin-recovery-project-t2982889
Z already has TWRP with f2fs and stuff.
If you need it for zr or zl simply repack it with res/ and default.prop from the correct phone. Guide in 1st post.
Hi, does it work for scorpion_windy with lollipop? Thx.
v2.8.7.0 is up! I'm on stock ROM now, so please check if it works
http://forum.xda-developers.com/showthread.php?t=3098573
2.8.7.0 on sony z1 (honami) with cm-12.1 is botting, gui is ok, but internal storage and sdcard not present.
hawkeyexp said:
2.8.7.0 on sony z1 (honami) with cm-12.1 is botting, gui is ok, but internal storage and sdcard not present.
Click to expand...
Click to collapse
same on amami.
EDIT: fixed in yesterday build with z1c res and default prop! :good:
rzlatic said:
same on amami.
EDIT: fixed in yesterday build with z1c res and default prop! :good:
Click to expand...
Click to collapse
still not working on honami...
32.3.A.2.33 is being pushed to our devices
Didn't "see" it via phone settings, but immediately discovered via Xperia Companion.
the version 32.3.A.2.33 is 7.0 (Security Patch 1. March 2017)
Kernel 3.10.84-perf-g1016077
Firmware + rooted boot.img thanks to youvedone
how did you go? what has changed?
is it version 7.1?
redavenger said:
how did you go? what has changed?
is it version 7.1?
Click to expand...
Click to collapse
I do not think that it is 7.1. It might be just February security patches.
has to be more than security patches considering how screwed up the nougat release is.
Unfortunately, I'm still getting prepared for the update (backing the phone up, downloading the FW. My network connection isn't perfect at all for now).
I'll let you know as soon as I get any news
The update is quite large, so it might be 7.1 (but can't be sure.. the chance it's just bug fixing along with February security patches are very high)
Unfortunatly the rootkernel_v5.32 gives no twrp for this version.
So the version 32.3.A.2.33 is 7.0 (Security Patch 1. March 2017)
Kernel 3.10.84-perf-g1016077
But have to say again: My Z5 Compact was never as good as now with 7.0 (E5823_32.3.A.0.378_R3D_1298-7782_Customized-NOBA | with root)
---------- Post added at 10:37 AM ---------- Previous post was at 10:25 AM ----------
Here you can get my versions
E5823_32.3.A.2.33_R2D_Customized AU_1298-7260.ftf
rooted boot.img
Because of " No kernel modules for 3.10.84-perf-g1016077 available " I integrated superuser.zip.
Updated with TWRP but no superuser: boot_sc_v02.img
Normally I would flash SuperSu afterwards.
V01 - superuser / because no twrp
**************************
C:\Admin\android\xperia\Flashtool\_totalnewtry_32.3.A.2.33\rootkernel_v5.23_Windows_Linux>rootkernel.cmd kernel.elf boot_sc_v01.img
Rootkernel V5.23
- Unpacking kernel
Found elf boot image
Kernel version: 3.10.84-perf-g1016077
Found appended DTB
- Detected vendor: somc (Sony), device: suzuran (Xperia Z5 compact), variant: row
- 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
Disabling dm-verity
- Sony RIC is enabled. Disable? [Y/n] Y
Disabling Sony RIC
- Skipping TWRP recovery. No kernel modules for 3.10.84-perf-g1016077 available
- Found superuser.zip. Install? [Y/n] Y
# Make su permissive (Permits any action as su)? [Y/n] Y
Adding service entry for superuser
Adjusting SE Linux policy for superuser
- Install DRM fix? [Y/n] Y
- Install busybox? [Y/n] N
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
V02 - no superuser, but twrp
****************************
rootkernel.cmd kernel.elf boot_sc_v02.img
Rootkernel V5.23
- Unpacking kernel
Found elf boot image
Kernel version: 3.10.84-perf-g1016077
Found appended DTB
- Detected vendor: somc (Sony), device: suzuran (Xperia Z5 compact), variant: row
- 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
Disabling dm-verity
- Sony RIC is enabled. Disable? [Y/n] Y
Disabling Sony RIC
- Install TWRP recovery? [Y/n] Y
Installing TWRP
Compressing TWRP image
- Found superuser.zip. Install? [Y/n] N
- Install DRM fix? [Y/n] Y
- Install busybox? [Y/n] N
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
Click to expand...
Click to collapse
from what I've discovered: as soon as the phone is ready to play music in the head/earphones, it vibrates. I mean the regular corded 3,5mm ones.
Previous releases displayed emerging/disappearing audio icons in the top status bar multiple times and you had to pay attention to it, waiting for the "icons dancing" to stop - to be sure that audio will be played to the earphones.
Now, "icon dancing" is present no more It displays Smart Connect & Audio Parameters (with some delay between one another), and vibrates as soon as it's ready to play sounds via 3,5 audio port
youvedone said:
Unfortunatly the rootkernel_v5.32 gives no twrp for this version.
Click to expand...
Click to collapse
I was working on the Android Bootable Recovery with Rootkernel for the E5823, and I decided to check something and thought I'd see if Xperia Companion would detect and connect to my phone... it did, and that's how I found there was an update...
Also... just for giggles:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
# Chown audio.cal owner to audioserver
chown audioserver /data/misc/audio/audio.cal
This has been added to the init.sony.rc in the ramdisk of kernel hopefully they've fixed the audio problem
I'm gonna test it right away
EDIT: Added my own 32.3.2.33 MEA kernel with TWRP and busybox and DRM Fix and RIC disabled and dm-verity disabled ...
Another Edit: Confirmed! Audio playing loud and clear <3
sijav said:
Code:
# Chown audio.cal owner to audioserver
chown audioserver /data/misc/audio/audio.cal
This has been added to the init.sony.rc in the ramdisk of kernel hopefully they've fixed the audio problem
I'm gonna test it right away
EDIT: Added my own 32.3.2.33 MEA kernel with TWRP and busybox and DRM Fix and RIC disabled and dm-verity disabled ...
Another Edit: Confirmed! Audio playing loud and clear <3
Click to expand...
Click to collapse
could you possibly provide me with the MEA .ftf?
Just checked xperiFirm and looks like a staged rollout, as nothing in the UK yet
Sent from my E5823 using Tapatalk
Just checking xperifirm, I see previous Nougat software version dissappear, now I only see this one (32.3.A.2.33) and marshmallow one. Do you recomend updating to Nougat with this new version? Have bugs been squashed now?
PD. I'm still on mm v32.2.A.5.11
rolo143 said:
Just checking xperifirm, I see previous Nougat software version dissappear, now I only see this one (32.3.A.2.33) and marshmallow one. Do you recomend updating to Nougat with this new version? Have bugs been squashed now?
PD. I'm still on mm v32.2.A.5.11
Click to expand...
Click to collapse
I don't see much of a bug, battery life is much better than MM (in case of me)
Root97 said:
could you possibly provide me with the MEA .ftf?
Click to expand...
Click to collapse
You can get it yourself quite easily =)
You'll just need to get XperiFirm for that =)
As soon as you follow the original guide from the mentioned XperiFirm topic and download the desired firmware,
Gewiz said:
...However imo there is even an slightly easier way to do, just try it:
If you open Xperifirm through Flashtool(round button with "XF") and download a firmware, just close Xperifrim after the download is complete.
Afterwards Flashtool will automatically create an .ftf file.
Click to expand...
Click to collapse
Just use latest FlashTool (you can get it here, for example: Download the FlashTool folder contents )
sceryavuz said:
Detailed installation steps
1-) Install flashtool-0.9.23.1-windows.exe
2-) Copy x10flasher.jar file into "C:\Flashtool"
3-) Disable Driver Signature Verification
Windows 7 : Tap F8 while booting and select option
Windows 8, 8.1, 10 : Read This Instructions
4-) Install Flashtool-drivers.exe (flashmode, fastboot, z5)
Click to expand...
Click to collapse
Run the desired version of Flashtool (x32 or x64)
Select "Tools" -> "Bundles" -> "Create"
In the opened window:
1.Select the source folder (where you've downloaded the FW via XperiFirm, for example: "C:\FW\E5823_Customized_AU_1298-7260_32.3.A.2.33-R2D")
2.Double click the "Device:" selection field and select in the Device Selector window "E58XX Sony Xperia Z5 Compact"
3.in the Variant Selector window select the correct variant (for current example, the suitable one is "E5823")
4.Input the branding (for example: Customized_AU)
5.Input the version (for example: 32.3.A.2.33-R2D)
6.Select all the items that appeared in the "folder list" [bottom left part of the Bundler window]: click on the first item (be it folder or file), scroll the list to the bottom, press "Shift" + click on the last item
7.Click on the "->" button to move all files from the left part of the window to the right one
8.Press "Create" button
after several minutes, you'll see the line "created successfully" (or something similar meaning that the ftf file is successfully created).
sceryavuz said:
6-) Backup your Photos & Videos & Music etc. on Internal Memory to SDCard or PC
7-) Shutdown your phone
9-) Click Flash button then Ok button, select FTF on left side
10-) Select ALL wipe options if you wish to perform the CLEAN install | Or DON'T select ANY wipe options if you wish to keep all user data
11-) Click Flash button, wait 1 minute
12-) Push VOLUME DOWN button, then connect phone to pc (green led)
13-) When flashing done, disconnect and boot-up your phone
14-) If you want to ROOT your phone then continue otherwise flashing FTF process done.
Click to expand...
Click to collapse
As easy as that
Thanks to IgorEisberg for XperiFirm, Bin4ry & Androxyde for Flashtool, Gewiz for the heads-up, sceryavuz for the guide and the files and of course BIG THANKS to Sony Developers for the FW!
Hi. Did you try that ROM with another kernel? Maybe Zach or AndroPlus? Cose custom ROM with custom kernel sucks in my opinion. Thermal throttling is just too heavy for me.
What happens if update my phone via OTA update ?
(Rooted with rootkernel)
Can I do that ?
offtopic
can someone try flash this
https://forum.xda-developers.com/z5...nt-display-t3559115/post71090477#post71090477
and be sure to patch the service.jar
so i can update the guide
thanks
Hi,
Do you have kcal in this kernel? Or can you make one? Rootkernel could add it to the 378 kernel i don.t see rootkernel do it to the new .33 kernel...
sijav said:
Code:
# Chown audio.cal owner to audioserver
chown audioserver /data/misc/audio/audio.cal
This has been added to the init.sony.rc in the ramdisk of kernel hopefully they've fixed the audio problem
I'm gonna test it right away
EDIT: Added my own 32.3.2.33 MEA kernel with TWRP and busybox and DRM Fix and RIC disabled and dm-verity disabled ...
Another Edit: Confirmed! Audio playing loud and clear <3
Click to expand...
Click to collapse
jutphaas said:
Hi,
Do you have kcal in this kernel? Or can you make one? Rootkernel could add it to the 378 kernel i don.t see rootkernel do it to the new .33 kernel...
Click to expand...
Click to collapse
Oh? no I havn't add kcal ....
I can add the 0.376 from root kernel though ...
Can i flash the zip from before in the posts via twrp? Is the phone then still rooted?
Gesendet von meinem E5823 mit Tapatalk
xpericheck.com/device/E5803
any news on the changelog?
So far everything works well on 7.1.1 for me. Ran a graphic intensive game generating slightly less heat but the device is definitely a lot faster. The ram that the system takes up for me is about ~730 MB and I have about ~550 MB of ram free with my regular apps running. Only time will tell for the battery life. Cheers!
Steps I took before taking the update: Cleared cache by holding power + vol up before taking update, after taking update repeated process (hold power + vol up to clear cache again).
No changes except security patch update
Nothing stellar, could even be BS, apart the september security update (source, not Sony):
Android September Security patch.
Device Stability improvements
Bug fixes.
Performance improvements.
But at least it's good to still have some official updates including security patches.
Update
I have received the notification, but when a try to install, it just restarts the phone, is it because Im rooted?
Got it few hours ago. So far so good. No major changes I guess.
Download size was ~351MB.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Xperia Z5C : Tapatalk
as in other versions here a downloadable E5823_32.4.A.1.54_R3E_Customized_CH-1298-7257
PLEASE DO NOT INSTALL IF YOU DONT KNOW WHAT TO DO WITH THE FILES
TWRP can be used with pressing "volume up" at the amber light. If you use it a "thanks" would be nice
Code:
PS C:\Admin\android\sony\FW\rootkernel\rootkernel_v5.23_Windows_Linux> ./rootkernel.cmd kernel.elf boot_sc_v01.img
Rootkernel V5.23
- Unpacking kernel
Found elf boot image
Kernel version: 3.10.84-perf-g99119bc
Found appended DTB
- Detected vendor: somc (Sony), device: suzuran (Xperia Z5 compact), variant: row
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 7.1.1
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] Y
Disabling dm-verity
- Sony RIC is enabled. Disable? [Y/n] Y
Disabling Sony RIC
- Skipping TWRP recovery. No kernel modules for 3.10.84-perf-g99119bc available
- Found superuser.zip. Install? [Y/n] Y
# Make su permissive (Permits any action as su)? [Y/n] Y
Adding service entry for superuser
Adjusting SE Linux policy for superuser
- Install DRM fix? [Y/n] Y
- Install busybox? [Y/n] N
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
Download boot_sc_v01.img - rooted without twrp but phh superuser
Code:
./rootkernel.cmd kernel.elf boot_sc_v02.img
Rootkernel V5.23
- Unpacking kernel
Found elf boot image
Kernel version: 3.10.84-perf-g99119bc
Found appended DTB
- Detected vendor: somc (Sony), device: suzuran (Xperia Z5 compact), variant: row
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 7.1.1
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] Y
Disabling dm-verity
- Sony RIC is enabled. Disable? [Y/n] Y
Disabling Sony RIC
- Install TWRP recovery? [Y/n] Y
Installing TWRP
Compressing TWRP image
- Found superuser.zip. Install? [Y/n] Y
# Make su permissive (Permits any action as su)? [Y/n] Y
Adding service entry for superuser
Adjusting SE Linux policy for superuser
- Install DRM fix? [Y/n] Y
- Install busybox? [Y/n] N
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
Download boot_sc_v02.img - with twrp and phh
Code:
./rootkernel.cmd kernel.elf boot_sc_v03.img
Rootkernel V5.23
- Unpacking kernel
Found elf boot image
Kernel version: 3.10.84-perf-g99119bc
Found appended DTB
- Detected vendor: somc (Sony), device: suzuran (Xperia Z5 compact), variant: row
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 7.1.1
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] Y
Disabling dm-verity
- Sony RIC is enabled. Disable? [Y/n] Y
Disabling Sony RIC
- Install TWRP recovery? [Y/n] Y
Installing TWRP
Compressing TWRP image
- Found superuser.zip. Install? [Y/n] N
- Install DRM fix? [Y/n] Y
- Install busybox? [Y/n] N
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
Download: boot_sc_v03.img - with twrp but without phh superuser - so you can install e.g. supersu
---------- Post added at 10:04 PM ---------- Previous post was at 10:03 PM ----------
nestromc said:
I have received the notification, but when a try to install, it just restarts the phone, is it because Im rooted?
Click to expand...
Click to collapse
for me its not working since I've got an unlocked bootloader.
nestromc said:
is it because Im rooted?
Click to expand...
Click to collapse
Yes. You should have known that when you rooted. :/
hey @youvedone this will work for E5803? want to use a custom kernel with magisk, but i dont know where to start, can you guide me?
Nope sorry I'm not sure for E5803... And never used custom kernels (at least I don't call the modified stock custom - or magisk)
Gesendet von meinem E5823 mit Tapatalk
Deodex Patch, credits to @TexHuk 3
https://drive.google.com/file/d/0B9S0pQiEDghzNUJuekFkTkNKalE/view
robot.le said:
So far everything works well on 7.1.1 for me. Ran a graphic intensive game generating slightly less heat but the device is definitely a lot faster. The ram that the system takes up for me is about ~730 MB and I have about ~550 MB of ram free with my regular apps running. Only time will tell for the battery life. Cheers!
Steps I took before taking the update: Cleared cache by holding power + vol up before taking update, after taking update repeated process (hold power + vol up to clear cache again).
Click to expand...
Click to collapse
Worth upgrading from stock 6.0 to 7.1.1?
Homescreen icons are still very big?
XM1T said:
Worth upgrading from stock 6.0 to 7.1.1?
Click to expand...
Click to collapse
personally I think, there's no choice.
from 6.0 up to 7.1.1 (including the previous build 32.4.A.0.160 from sony) there are so much security holes in it. This alone is a very good reason.
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
cannn11 said:
Homescreen icons are still very big?
Click to expand...
Click to collapse
can't say.. using Nova Launcher since so long..
I was at the previous Nougat and downgraded to MM as the phone was running too hot.
With the Firmware the phone is very cool now and only warms up, would recommned it.
billbond4 said:
I was at the previous Nougat and downgraded to MM as the phone was running too hot.
With the Firmware the phone is very cool now and only warms up, would recommned it.
Click to expand...
Click to collapse
How's the battery life? Also does the fingerprint sensor work any better?
Idk man, I'm not happy with this update on my z5c. It is making the phone lag almost everywhere.
Yes I have cleared the cache amd disabled movie maker
Sent from my E5823 using Tapatalk
youvedone said:
as in other versions here a downloadable E5823_32.4.A.1.54_R3E_Customized_CH-1298-7257
PLEASE DO NOT INSTALL IF YOU DONT KNOW WHAT TO DO WITH THE FILES
TWRP can be used with pressing "volume up" at the amber light. If you use it a "thanks" would be nice
Code:
PS C:\Admin\android\sony\FW\rootkernel\rootkernel_v5.23_Windows_Linux> ./rootkernel.cmd kernel.elf boot_sc_v01.img
Rootkernel V5.23
- Unpacking kernel
Found elf boot image
Kernel version: 3.10.84-perf-g99119bc
Found appended DTB
- Detected vendor: somc (Sony), device: suzuran (Xperia Z5 compact), variant: row
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 7.1.1
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] Y
Disabling dm-verity
- Sony RIC is enabled. Disable? [Y/n] Y
Disabling Sony RIC
- Skipping TWRP recovery. No kernel modules for 3.10.84-perf-g99119bc available
- Found superuser.zip. Install? [Y/n] Y
# Make su permissive (Permits any action as su)? [Y/n] Y
Adding service entry for superuser
Adjusting SE Linux policy for superuser
- Install DRM fix? [Y/n] Y
- Install busybox? [Y/n] N
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
Download boot_sc_v01.img - rooted without twrp but phh superuser
Code:
./rootkernel.cmd kernel.elf boot_sc_v02.img
Rootkernel V5.23
- Unpacking kernel
Found elf boot image
Kernel version: 3.10.84-perf-g99119bc
Found appended DTB
- Detected vendor: somc (Sony), device: suzuran (Xperia Z5 compact), variant: row
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 7.1.1
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] Y
Disabling dm-verity
- Sony RIC is enabled. Disable? [Y/n] Y
Disabling Sony RIC
- Install TWRP recovery? [Y/n] Y
Installing TWRP
Compressing TWRP image
- Found superuser.zip. Install? [Y/n] Y
# Make su permissive (Permits any action as su)? [Y/n] Y
Adding service entry for superuser
Adjusting SE Linux policy for superuser
- Install DRM fix? [Y/n] Y
- Install busybox? [Y/n] N
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
Download boot_sc_v02.img - with twrp and phh
Code:
./rootkernel.cmd kernel.elf boot_sc_v03.img
Rootkernel V5.23
- Unpacking kernel
Found elf boot image
Kernel version: 3.10.84-perf-g99119bc
Found appended DTB
- Detected vendor: somc (Sony), device: suzuran (Xperia Z5 compact), variant: row
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 7.1.1
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] Y
Disabling dm-verity
- Sony RIC is enabled. Disable? [Y/n] Y
Disabling Sony RIC
- Install TWRP recovery? [Y/n] Y
Installing TWRP
Compressing TWRP image
- Found superuser.zip. Install? [Y/n] N
- Install DRM fix? [Y/n] Y
- Install busybox? [Y/n] N
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
Download: boot_sc_v03.img - with twrp but without phh superuser - so you can install e.g. supersu
---------- Post added at 10:04 PM ---------- Previous post was at 10:03 PM ----------
for me its not working since I've got an unlocked bootloader.
Click to expand...
Click to collapse
How did you solve "Skipping TWRP recovery. No kernel modules for 3.10.84-perf-g99119bc available"?
cannn11 said:
Homescreen icons are still very big?
Click to expand...
Click to collapse
Icon size can be adjusted in homescreen settings - Small or Large. Long-press a blank area on the homescreen to access its settings.
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.